DoD now provides revised guidance to integrate Earned Value with Technical Performance. The guidance overcomes the "Quality Gap" in the EVMS Standard. EVMS requires measurement of only the quantity of work performed, not the Quality.
Technical Performance Measures (TPM) are described in the Defense Acquisition Program Support Methodology (DAPS), V2.0 and in the Interim Defense Acquisition Guide (DAG), as follows:
DAPS
TPMs report the degree to which system requirements are met in terms of performance, cost, and schedule (3.3.4.3.c1)
TPMs track the key indicators of system performance versus planned progress of Key Performance Parameters and other key effectiveness measures (5.1.1.c3)
In DAPS, TPMs flow down from the Capability Development Document (CDD) to the EVMS work packages, as follows:
| Capabilities Development Document (CDD): Identifies Key Performance Parameters (KPPs) (1.3) System Specifications: A linkage exists between measures of effectiveness (MOE), system requirements (CDD and specifications), test and evalution (T&E) and critical technical parameters (CTP) (5.1.1.C2). |
| Program Health Metrics: Identify and use TPMs that address KPPs and CTPs (3.3.4.3.C2) |
| IMP: IMP characteristic: linked to TPMs (3.31.C1b) |
| IMS: • Maintains consistency with the IMP (3.31.C2b) • Maintains consistency with the work package definitions and the EVMS |
| EVMS: • EVMS has no provision to measure quality (3.4.3.Q3) • Use TPMs to determine whether % completion metrics accurately reflect quantitative technical progress and quality toward meeting KPPs and CTPs |
DAG
At the start of a program, TPMs define the planned progress of selected technical parameters. The plan is defined in terms of expected performance at specific points in the program as defined in the WBS and Integrated Master Schedule, the methods of measurement at those points, and the variation limits for corrective action. During the program, TPMs record the actual performance observed of the selected parameters and assist the manager in decision-making (performance or resource tradeoffs) through comparison of actual vs. projected performance. TPM parameters that especially need to be tracked are the cost drivers on the program, those that lie on the critical path, and those that represent high technical risk items.
A well thought out program of TPMs provides an early warning of technical problems and supports assessments, and provides an assessment of the impacts of proposed changes in system performance. To accomplish this, the government and contractor both need to set parameters to be tracked. The government program office will need a set of TPMs that provide visibility into the technical performance of key elements of the work breakdown structure and the highest areas of cost, schedule, or technical risk. The TPMs selected for delivery to the government are expected to be traceable to the needs of the operational user and to the set of key performance parameters, key system attributes, and CTPs.
The contractor will generally track more items than are reported to the government, as the contractor needs information at a more detailed level than does the government program office. TPM reporting to the government is a contractual issue, and those TPMs on which the government receives reports are defined as contract deliverables in the contract data requirements list.
Document, Baseline, IMS, or EVM component | Technical Parameter |
CDD | Key Performance Parameter (KPP) |
Functional Baseline | Measures of Effectiveness (MOE) |
Functional Baseline | Measures of Performance (MOP) |
Allocated Baseline | TPM |
IMS | TPM Milestones and Planned Values |
Work packages | TPM-based % complete criteria |
Practical guidance and examples for linking EV to TPMs and to the technical baseline are provided in my book,
Performance-Based Earned Value.