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.

In this section you will identify any other system attributes not directly quantified (as performance attributes) and traceable to operational performance, and not identified elsewhere in the document.​

Other system attributes may include the following:​

- Future integration platforms. Used in cases where integration on certain platforms is not currently planned or resourced, not already captured in the IOC and FOC definitions in the Program Summary Section (Section 4), but your team would like to preserve the option for future integration on additional platforms.​

- Embedded instrumentation, electronic attack, and wartime reserve mode (WARM) requirements.​

- Human Systems Integration (HSI) considerations that have a major impact on system effectiveness and suitability.​

- Natural environmental factors, including climatic design type, terrain, meteorological and oceanographic (METOC) factors, impacts, and effects.​

- Weather, oceanographic and astro-geophysical support needs throughout the program’s projected lifecycle, including data accuracy and forecast needs.​

- Transportability and deployability considerations (DoDI 4540.07)* will include how the capability solution and related materiel will be moved either to or within the theater and identify any lift limitations.​

- Space, Weight, & Power, and Cooling (SWAP-C) margin requirements and open system attributes, to ensure future flexibility and upgradability of systems and sub-systems to changing technologies and threats.​

- Derived system requirements to support systems that may be used in allied, partner-nation, coalition, or multinational operations relating to U.S.-ratified international standardization agreements.​

- Cybersecurity Risk Management for DoD IT Systems: In addition, the CDD should identify the system categorization for information systems and Platform IT (PIT) systems as a required capability — the potential impact (low, moderate, or high) resulting from loss of confidentiality, integrity, and availability if a security breach occurs.​

- In accordance with the Cyber Survivability Endorsement Implementation Guide, Cyber Survivability Attributes (CSA) associated with the mandatory SS KPP will be included in Appendix E.​

These are examples that may or may not apply to the system described in your CDD. Your Team should discuss these and any other important attributes not directly traceable to required operational performance and construct a table like the KPP, KSA, APA tables.