The purpose of the CDD Increment or Annex is to provide the Sponsor with flexibility to redefine

capabilities from a base document.

If there are no changes from the base document in a given section, simply annotate, “No changes.”

If you have updates or changes to a section, refer to the content below which guide a user in the generation an initial CDD as a start point for what a CDD Annex or Increment should cover.

This section ensures that capability solutions being developed to address the capability requirements and associated capability gaps are based on consistent threat environment information and references and includes the following elements.

- All acquisition programs or capabilities expected to operate in a threat environment (lethal or non-lethal) must be developed IAW the most current threat products from the DIE.

- Be Aware: In addition to the topics below, the content for this section of the CDD must be in sync with JCIDS Manual, Annex G, to Appendix G, to Enclosure B, section 3.2.4, Threat Summary Guide.

- Cite the latest approved threat products used to support this CDD.

- Update the threat summary from the validated ICD with current threat analysis from the DIE.

- As the threat environment may have evolved since the validation of the ICD, clearly identify threats that are consistent with factors used to determine the capability captured in the

- If new threats have emerged since the validation of the ICD, describe the threat capabilities as outlined for Section 2 of the ICD.

- Consider evolving threats to on-going and follow-on RDT&E, production, and O&M resulting from technology transfer, espionage, and other adversarial collection efforts.

- Include summaries of all applicable threats cited in the System Survivability (SS) KPP (i.e., Kinetic, CBRN, Space, EMS, and Cyber) if the operational context requires operation in such environments. These summaries will form the basis for a risk-managed approach to developing SS requirements.

- If the CDD is not based on a validated capability requirements document, provide the threat summary as outlined for Section 2 of an ICD.

Critical Intelligence Parameters (CIPs)

- CIPs are those key performance thresholds of foreign threat systems which, if exceeded, could compromise the mission effectiveness of the US system in development (DIAI 5000.002)

- DIA (or Service-level threat validation authority, as appropriate) will also evaluate the performance attributes that are potentially threat-sensitive or dependent.

- If CIPs are required, coordinate the CIP language with your supporting DIE element. Follow guidance in Annex G, to Appendix G, to Enclosure B, JCIDS Manual.

- CIPs will be included for capabilities in development that are threat-sensitive. Coordinate with DIA during the development of the CDD to determine whether CIPs are required.

- Summarize approved CIPs, that are applicable to the KPPs. These can be CIPs that are associated with intelligence production requirements assigned to DIE and/or proposed CIPs that are part of this CDD.

- Describe the relationship between the CIP and the supported KPP.

Cite the Community On-Line Intelligence System for End Users and Managers (COLISEUM) production requirement number, CIP number, and threat topic.