Key Performance Parameter (KPP)

A Key Performance Parameter (KPP) is a threshold performance requirement in a defense acquisition program's Capability Development Document (CDD) that represents the minimum performance level a system must achieve to be considered operationally effective and suitable, failure to meet a KPP is a program-stopping deficiency.

What is a Key Performance Parameter?

KPPs are identified during the requirements development process and documented in the Capability Development Document (CDD) approved by the Joint Requirements Oversight Council (JROC). They represent the operational community's judgment that certain performance attributes are non-negotiable, if the system cannot meet these parameters, it does not deliver the required military capability regardless of how well it performs in other areas.

Each KPP has a Threshold value, the minimum acceptable performance level, and an Objective value, the desired performance level that the program should strive toward if cost and schedule permit. For example, a communications system KPP might have a Threshold of 99% message delivery rate and an Objective of 99.9%. A system that achieves 99.2% satisfies the KPP and is acceptable; a system that achieves 98.5% fails the KPP and is not operationally suitable.

KPPs are verified during Initial Operational Test and Evaluation (IOT&E) conducted by the independent Operational Test and Evaluation agency (OT&E). A system that fails a KPP during IOT&E cannot receive a favorable operational effectiveness and suitability determination, which is required for a positive milestone decision to proceed to full-rate production.

Beyond their role in acquisition, KPPs define what is technically important enough to warrant the highest priority and oversight attention throughout the development program. Technologies supporting KPP achievement receive the most rigorous Technology Readiness Assessments and have the lowest acceptable risk thresholds.

Why KPPs matter for government contractors

A contractor developing a system that is at risk of failing a KPP is in a contractually and programmatically precarious position. A KPP failure during IOT&E can halt a program, trigger government claims for cost growth, and severely damage the contractor's past performance record. Understanding which requirements are KPPs and ensuring KPP achievement is the highest priority throughout development is a fundamental program management imperative.

Example

An Army ground vehicle program has three KPPs: survivability (defined by specific armor protection standards against threat weapons), operational range (minimum 300-mile range without refueling), and communications interoperability (ability to connect with specified command networks). During developmental testing, the vehicle achieves the survivability and communications KPPs but range testing shows 285 miles, below the 300-mile threshold. The program manager escalates to the Army acquisition executive and initiates an engineering review that identifies fuel system efficiency improvements that restore range compliance before IOT&E begins.

Frequently Asked Questions

How many KPPs does a typical defense program have?

Defense acquisition policy discourages excessive KPPs because each one represents a potential program-stopper. Most programs have between 3 and 10 KPPs covering the most mission-critical performance dimensions. Additional performance parameters that are important but not system-critical are designated as Key System Attributes (KSAs) with lower consequence for failure.

What is the difference between a KPP and a Key System Attribute (KSA)?

KPPs represent non-negotiable performance requirements whose failure would make the system operationally unsuitable. KSAs are additional important parameters, failure to meet KSA thresholds is serious but does not automatically stop the program. Both are defined in the CDD, but KSAs have more flexibility in the government's decision about how to proceed.

Can KPPs be waived or modified?

KPP thresholds can only be changed through a formal requirement change process approved by the JROC, which sets KPPs in the first place. A program cannot simply decide to accept lower KPP performance, the operational requirements sponsor must validate whether the lower performance level still meets the mission need. KPP modifications late in development typically indicate fundamental program health problems.

How do KPPs relate to EVMS reporting?

Programs typically designate Technical Performance Measures (TPMs) in their EVMS that track progress toward achieving KPP threshold values. Negative TPM trends, where actual performance measurements fall below the plan toward the threshold value, are reported in EVM variance analysis and trigger early management attention to prevent KPP failure at IOT&E.