an explanation and an electronic copy of whatever alternative analysis has been performed will be made available or attached. 7. CPD Review and Approval. A CPD is written, validated, and approved to support the Milestone C decision for each increment. Unlike the CDD, the CPD is always specific to a single increment and is normally not updated. 8. CPD Publication and Archiving. Approved CPDs (SECRET and below), regardless of JPD, will be posted to the KM/DS tool so that all JCIDS documents are maintained in a single location. 9. System Capabilities. The CPD identifies, in threshold/objective format, the specific attributes that contribute most significantly to the desired operational capability. The focus of these attributes is fundamentally different from that of the attributes provided in the CDD. The CDD values were used to guide the acquisition community in making tradeoff decisions between the threshold and objective levels of the stated attributes. After critical design review, these tradeoff decisions have been made and a more precise determination of acceptable performance can be stated in the CPD. A range of expected performance, provided by the PM, is specified by the expected production threshold and objective value for each attribute or KPP. a. The production threshold and objective values specified for the attributes in the CPD may be refinements of the development threshold and objective values documented in the CDD. Each production threshold listed in the CPD represents the minimum performance that the PM is expected to deliver for the increment based on the results of critical design review. In operational test, a system is required to demonstrate that it can satisfy all KPP and KSA thresholds listed in the CPD for this increment. b. Each production threshold value may be adjusted, as required, to account for post-critical design review estimates and for manufacturing, technical, and other risks. KPP, KSA, and other performance attribute threshold values in the CPD are generally expected to be equal to or better than the corresponding CDD threshold values. However, there may be cases where CDD KPP, KSA, and/or non-KPP threshold values are reduced in a CPD. When this occurs, the following questions must be answered in the CPD: (1) Will the capability still provide sufficient operational effectiveness as defined in the source ICD? (2) If the new capability will replace a fielded capability, will it still provide equal or better overall operational effectiveness than the fielded capability?
an explanation and an electronic copy of whatever alternative analysis has been performed will be made available or attached. 7. CPD Review and Approval. A CPD is written, validated, and approved to support the Milestone C decision for each increment. Unlike the CDD, the CPD is always specific to a single increment and is normally not updated. 8. CPD Publication and Archiving. Approved CPDs (SECRET and below), regardless of JPD, will be posted to the KM/DS tool so that all JCIDS documents are maintained in a single location. 9. System Capabilities. The CPD identifies, in threshold/objective format, the specific attributes that contribute most significantly to the desired operational capability. The focus of these attributes is fundamentally different from that of the attributes provided in the CDD. The CDD values were used to guide the acquisition community in making tradeoff decisions between the threshold and objective levels of the stated attributes. After critical design review, these tradeoff decisions have been made and a more precise determination of acceptable performance can be stated in the CPD. A range of expected performance, provided by the PM, is specified by the expected production threshold and objective value for each attribute or KPP. a. The production threshold and objective values specified for the attributes in the CPD may be refinements of the development threshold and objective values documented in the CDD. Each production threshold listed in the CPD represents the minimum performance that the PM is expected to deliver for the increment based on the results of critical design review. In operational test, a system is required to demonstrate that it can satisfy all KPP and KSA thresholds listed in the CPD for this increment. b. Each production threshold value may be adjusted, as required, to account for post-critical design review estimates and for manufacturing, technical, and other risks. KPP, KSA, and other performance attribute threshold values in the CPD are generally expected to be equal to or better than the corresponding CDD threshold values. However, there may be cases where CDD KPP, KSA, and/or non-KPP threshold values are reduced in a CPD. When this occurs, the following questions must be answered in the CPD: (1) Will the capability still provide sufficient operational effectiveness as defined in the source ICD? (2) If the new capability will replace a fielded capability, will it still provide equal or better overall operational effectiveness than the fielded capability?
JCIDS%20Manual%20-13%20March%202009.docx