Performance-Based Earned Value ®

PBEV = EVM + Quality
Home     New     Basic EVM     Advanced EV: PBEV     Dept of Defense     EV = Ponzi Scheme?     PBEV the Book     Consulting     PBEV Live Training     About us     Contact Us      
DOD Guide Matrix
Technical Performance
Technical Baseline
DoD EVM Implementation
DoD acquisition policy requires that weapons systems meet requirements of the technical baseline. The technical baselines, technical reviews, and Integrated Master Plan success criteria for those reviews are described in the Defense Acquisition Program Support Methodology (DAPS), V2.0 and the Interim Defense Acquisition Guide (DAG). An extract from DAPS and DAG follows.
 
 

Technical

Baseline

 

Source

Description

DAPS Review Milestone Criteria

Functional

Baseline

DAPS 4.3.1.C35

DAG

System functional requirements as captured in system specifications. All required system performance is fully decomposed and defined in the functional baseline.

Definition of the required system functionality describing functional and interface characteristics of the overall system, and the verification required to demonstrate the achievement of those specified functional characteristics. This baseline is derived  from the Capabilities Development Document (CDD) and normally includes a detailed functional performance specification for the overall system and the tests necessary to verify and validate overall system performance.

System Functional Review (SFR):

System's lower-level performance requirements are fully defined and consistent with the mature system concept and lower-level systems requirements trace to top-level system performance and the CDD.

Allocated

Baseline

DAPS 4.3.3.C4

DAG

Performance specifications for each configuration item (CI) in the system.

 

   Allocated Baseline—Definition of the configuration items making up a system, and then how system function and performance requirements are allocated across lower level configuration items (hence the term allocated baseline). It includes all functional and interface characteristics that are allocated from the top level system or higher-level configuration items, derived requirements, interface requirements with other configuration items, design constraints, and the verification required to demonstrate the traceability and achievement of specified functional, performance, and interface characteristics. The performance of each configuration item in the allocated baseline is described in its preliminary design specification as are the tests necessary to verify and validate configuration item performance. The allocated baseline is usually established and put under configuration control at each configuration item’s (hardware and software) Preliminary Design Review (PDR), culminating in a system allocated baseline established at the system-level PDR.

PDR:

1.    Each function in the functional baseline has been allocated to one or more system configuration items.

2.     System allocated baseline been established and documented to enable detailed design to proceed with proper configuration management.

3.     The software functionality in the approved allocated baseline is consistent with the updated software metrics and resource-loaded program schedule.

Product

Baseline

DAPS 4.3.1.C41,

3.2.2.Q78

DAG

Product specifications for each CI in the system

Product Baseline-Documentation describing all of the necessary functional and physical characteristics of a configuration item; the selected functional and physical characteristics designated for production acceptance testing; and tests necessary for deployment/installation, operation, support, training, and disposal of the configuration item. The initial product baseline includes “build-to” specifications for hardware (product, process, material specifications, engineering drawings, and other related data) and software (software module design— “code-to” specifications). The Initial product baseline is usually established and put under configuration control at each configuration item’s Critical Design Review (CDR), culminating in an initial system product baseline established at the system-level CDR.

CDR:

1.     Each product in the product baseline has been captured in the detailed design documentation.

2.     The software functionality in the approved product baseline is consistent with the updated software metrics and resource-loaded schedule.

Product

Baseline

DAPS 4.2.2.C18,

4.3.1.C49

 

Product specifications for each CI in the system

 

System Verification Review (SVR)/

Function Configuration Audit (FCA):

1.    System final product, as evidenced in its production configuration meets the functional requirements (derived from the CDD and draft Capability Production Document documented in the Functional, Allocated, and Product Baselines.

2.     All system performance specification qualification test requirements have been successfully completed, if applicable

 

(a) Defense Acquisition Program Support Methodology (DAPS) V. 2.0

 
Practical guidance and examples for linking EV to the technical baseline and to technical performance measures are provided in my book, 
 
Performance-Based Earned Value.