The Capability Development Document (CDD) specifies the operational requirements for the system that will deliver the capability that meets operational performance criteria specified in the Initial Capabilities Document (ICD). It outlines a militarily useful increment of capability with its own set of attributes and performance values (i.e., thresholds and objectives). The CDD is prepared during the Technology Maturation & Risk Reduction (TD) Phase to guide the Engineering & Manufacturing Development (EMD) Phase by defining measurable and testable capabilities.  The CDD supports and must be validated and approved before the Milestone B (MS B) decision at the Development RFP Release Decision Point .

 JCIDS Process Picture

 

Figure: CDD in the Acquisition/JCIDS Process

The CDD identifies operational performance attributes of the proposed system. The CDD is system specific and applies to a single increment of capability in an Evolutionary Acquisition program. Each increment of a program will either have its own CDD or a separate annex on a master CDD. Key Performance Parameters (KPP) are introduced in the CDD. Cost will be included in the CDD as Life-Cycle Cost (LCC) or, if available, Total Ownership Costs (TOC).

Guide: Capability Development Document (CDD) Writers Guide

Format: JCIDS Manual of Operations (Enclosure D)

 As the CDD is going through the Joint Requirements Oversight Council (JROC) approval process prior to Milestone B, the Test & Evaluation (T&E) Working-level Integrated Product Team (T&E WIPT) updates the T&E Strategy using the system-specific details in the CDD. The CDD provides the KPP and Key System Attributes (KSA) that provide a focus for the T&E program. The T&E strategy gains details (specific, desired, operational capabilities; T&E events (Developmental Test and Evaluation, Operational Test and Evaluation, and Live-Fire Test and Evaluation) adding to the broad, initial T&E Strategy; Critical Operational Issues (COI); refining the management structure and composition of the T&E WIPT; identifying resource requirements more precisely; etc.) that refines the scope and size of the planned T&E program, and permits a better estimate of the T&E resources and costs.

CDD Required Sections Per JCIDS Manual: [3]

  1. Operational Context
  2. Threat Summary
  3. Capability Discussion
  4. Program Summary
  5. Development KPPs, KSAs, and APAs
  6. Other System Attributes
  7. Spectrum Requirements
  8. Intelligence Supportability
  9. Weapon Safety Assurance
  10. Technology Readiness Assessment
  11. DOTmLPF-P Considerations
  12. Program Affordability

The Capability Development Tracking and Management (CDTM) tool is provided as a means to generate and submit ICDs, CDDs, CPDs, and Joint DCRs to the Knowledge Management/Decision Support (KM/DS) system.

REGULATORY: A draft CDD is required at Milestone A; a validated CDD is required at the Development RFP Release Decision Point and informs Milestone B. If there are no changes, a revalidated CDD may be submitted for the Capability Production Document (CPD) required at Milestone C. [2]

– See Requirements Document Sequence

AcqTips:

  • The CDD replaced the Operational Requirements Document (ORD) that was used under the old Requirements Generation System.
  • The format for the CDD is found at Appendix A to Enclosure H of the Manual for the Operation of the Joint Capabilities Integration and Development System, updated July 2012
  • Because the CDD normally is not approved until around the time of Milestone B, the T&E WIPT will most likely have to work from a draft version, to prepare the Test and Evaluation Master Plan (TEMP) prior to the Milestone B decision. (See the JCIDS Manual)

AcqLinks and Resources:

Updated: 6/01/2018

Print Friendly, PDF & Email