AcqNote Description Area
The Critical Path Method (CPM) is a way to determine the critical path of a schedule. The critical path is the longest path of scheduled activities that must be met to execute a project. This is important for Program Managers (PM) to know since any problems on the critical path can prevent a project from […]
A Weapons Systems Specification (WSS) is a list of detailed requirements that are developed by the contractor during the development of a weapons system. It provides more detailed information about the weapon system than the government-provided Initial Capabilities Document (ICD) and Capabilities Development Document (CDD). The WSS is what’s actually used during the development, design,
Note: Technical Requirements Document (TRD) is no longer in use and was replaced by the System Requirements Document (SRD) A Technical Requirements Document (TRD) was a requirements document that was put together by the government that addressed technical level requirements for a system. It accompanied a Request for Proposal (RFP) and provided a better technical
The Total Allocated Budget (TAB) is the sum of all budgets allocated to a contract for authorized work but doesn’t include profit or fee. The TAB consists of the Performance Measurement Baseline (PMB) and all Management Reserve (MR). The TAB reconciles directly to the Contract Budget Base (CBB). If the TAB is greater than the
A Work Package (WP) is a natural subdivision of a Control Account (CA). A work package is simply a task/activity or grouping of work and is the point at which work is planned, progress is measured, and earned value is computed. It can be translated into different terms in different companies and functions. It can
The System Requirement Document (SRD) defines system-level functional and performance requirements for a system. The SRD is derived from the Capability Development Document (CDD), Concept of Operations (CONOPS), system-level performance metrics, mission threads/use cases, and usage environment and is developed by the program office. It should include a system-level description of all software elements required
Standardization is the process of developing and implementing technical standards. The process establishes a common agreement for engineering criteria, terms, principles, practices, materials, items, processes, and equipment parts, and components. An organization can benefit from standardization because it: [2,4] Enables mass production Enables customization Improves supplier coordination Improves quality Enables simplification Enables delayed differentiation Lowers
The To Complete Performance Index (TCPI) is a comparative Earn Value Management (EVM) metric used primarily to determine if an independent estimate at completion is reasonable. It computes the future required cost efficiency needed to achieve a target Estimate at Completion (EAC). TCPI Definition: The To Complete Performance Index (TCPI) is a measure of the
A Summary Level Planning Package (SLPP) is an aggregation of work for far-term efforts, not able to be identified at the Control Account (CA) level, which can be assigned to reporting level Work Breakdown Structure (WBS) elements (and is therefore not “Undistributed Budget”). [1] SLPP are used to establish high-level holding accounts for
Requirements Tracing is one of the processes in Requirements Management; documenting, analyzing, tracing, prioritizing, and controlling. Tracing is conducted throughout a system’s life cycle and confirmed at each technical review for all new and old requirements. The purpose is to assure that the requirements continue to meet the needs and expectations of its customers and Stakeholders.
The Performance Measurement Baseline (PMB) is an important tool in earned value management used by Program Managers and Systems Engineers in the Technical Assessment Process to appraise a program’s technical progress. It includes the undistributed budget, all summary level planning package budgets, and all control account budgets but does not include management reserve. It establishes
The purpose of the Validation Review is to conduct a formal assessment of a contractor’s proposed EVMS compliance with ANSI/EIA-748. Successful demonstration of the EVMS and completion of the review results in the validation of the contractor’s EVMS. The primary objectives of the VR are to: [1] Evaluate management system capabilities against ANSI/EIA-748 Assess the
One of the key assurance activities for any project is expert evaluation and assessment of the requirements. The requirements need to be evaluated by multiple people with varying expertise, in order to identify incorrect, ambiguous, and incomplete requirements. A System Requirements Review (SRR) is one way to accomplish this evaluation. A fundamental question for requirements
Figure: JCIDS Requirements Sequencing 1. The Initial Capabilities Document (ICD) is the most common starting point for new capability requirements. [1] Once validated, the ICD typically leads to an Analysis of Alternatives (AoA) and then the Capability Development Document (CDD) and Capability Production Document (CPD) for the development of a materiel capability solution. An ICD
The process of developing product requirements is known as requirements development. Creating a thorough checklist to ensure the quality of the criteria you’ve written is an important aspect of the process. Below is a basic checklist that can be used to determine whether a requirement is acceptable, needs to be modified, or eliminated. Checklist: Requirements
An Integrated Baseline Review (IBR) (FAR 34.202)is a joint assessment conducted by the government Program Manager (PM) and the contractor to establish a mutual understanding of the Performance Measurement Baseline (PMB). This understanding provides for an agreement on a plan of action to evaluate the risks inherent in the PMB and the management processes that
Earned Value Management Surveillance is required for all contract efforts that require the implementation of an Earned Value Management System (EVMS) compliant with the guidelines in ANSI/EIA-748, regardless of whether a formal system validation is required. For the life of the contract, surveillance will be conducted on a recurring basis and should evaluate both the
Requirements Allocation is the act of decomposing higher-level requirements and assigning them to lower-level functions. All requirements of the top-level functions must be met by the aggregate of those for all lower-level functions. Step 3, Functional Analysis and Allocation, of the Systems Engineering Process is where requirements allocation occurs. Requirements allocation is often difficult to
A requirement is a statement that identifies a product or process operational, functional, or design characteristic or constraint. Users, System Engineers, and Program Managers will have to develop several different types of requirements for an acquisition program through its life cycle. These requirements range from very high-level concept-focused to very specific for a part. The four
There are four (4) areas of a solicitation package that need to address EVM. Each is described in more detail below: Work Breakdown Structure (WBS) DFARS clauses Statement of Work (SOW) Contract Data Requirement List (CDRL) (1) Work Breakdown Structure (WBS) The WBS is the basic structure for EVMS data collection and reporting and should
The Program Manager (PM) should use Defense Federal Acquisition Regulation Supplement (DFARS) clauses 252.234-7001 and 252.234-7002 to place the Earned Value Management (EVM) Solicitation requirement in solicitations and contracts. There is a single set of clauses for Earned Value Management System (EVMS) compliance and determination, and a different set for EVMS compliance. See the figure below.
The Mission Requirements Board (MRB) manages the national requirements process that reviews, validates, and approves national requirements for future intelligence capabilities and systems. It is the senior validation and approval authority for future intelligence systems funded within the National Foreign Intelligence Program (NFIP), and provides advice and counsel on future requirements funded outside that
Modeling & Simulation (M&S) requirements specify the set of capabilities that a simulation needs in order to adequately serve all of its intended uses. Users rely on information from the three domains (Problem, User and Simulation) to develop a concise and consistent set of requirements for the simulation at hand. Users use this set
An Earned Value Management System (EVMS) can be defined as an integrated management system and its related sub-systems, which allow for: [1] planning all work scope for the program to completion assignment of authority and responsibility at the work performance level integration of the cost, schedule, and technical aspects of the work into a detailed
Contracts Less than $20M The application of Earned Value Management (EVM) is not required on cost or incentive contracts or agreements valued at less than $20M. The decision to implement EVM on these contracts and agreements is a risk-based decision, at the discretion of the Program Manager (PM), based on a cost-benefit analysis that compares the
