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’ll specify how the individual system will interoperate within the joint environment. This includes Net-Ready Interoperability, Physical Interoperability, and Joint Training Interoperability. ​

- Include information that may enhance innovation such as the use of a Modular Open Systems Approach (MOSA)* to support future incremental development. Make sure this is in-sync with Section 4 of your CDD as well as the PM’s acquisition strategy.​ (*Note: For information on MOSA see DoDI 5000.85, Major Capability Acquisition, page 27.)

- If applicable, address intelligence interoperability requirements (see Annex G to Appendix G to Enclosure B, JCIDS Manual​

Physical Interoperability. Describe the physical aspects of joint interoperability that may impact the capability solution. This description must be consistent with the OV-2 in describing resources flows to and from the proposed capability, and further described in the SV-1 to describe what enacts the OV-2 flow, now (as-is) or in the future. ​

- Describe any physical requirements (i.e., required landing space, runway length, etc.) that may impact the joint force. ​

- Describe any SoS or FoS considerations.

Net-Ready Interoperability. ​

- Discuss Net-Ready Interoperability as described in Annex A to Appendix G to Enclosure B, JCIDS Manual. ​

- The Net-Ready Performance Attribute table in Section 5 of your CDD presents the net-ready performance attributes and their associated metrics (Figure B-11, JCIDS Manual)​

- Net-Ready threshold and objective performance values should be represented in numerical form whenever possible to preclude subjective interpretation.

- See Figure B-12, JCIDS Manual, for the three Net-Ready development steps, with attribute details, measures, and sample data sources.

Joint Training Technical Interoperability (JTTI). ​

- For systems with a mission solely focused on training, exercises, and/or mission rehearsal, specify how these systems will interoperate within the Joint Training Synthetic Environment (JTSE), including effects on joint training operations with allies and partners.​

- State the intent to design these systems to JTSE standards and discuss technical approaches to ensure technical interoperability.

JTSE standards are maintained in the DoD IT Standards Registry (DISR) (CAC required)