2.5.1.7. Section 7: Interoperability. Same as the regular CDD with the exception of the following.

2.5.1.7.1. The summary table for the Net-Ready performance attribute will be slightly different from that of a CDD since it will be quantified in terms of initial minimum values rather than threshold/objective values. To illustrate this, reference Figure B-13 below.

For reference or comparison, below is what the JCIDS Manual says for the DCR 2025 itself:

2.5.7. Section 7: (Joint) Interoperability.

2.5.7.1. The purpose of this Section is to specify how the individual system will interoperate within the joint environment, including any physical or Net-Ready interoperability effects on joint operations or operations with allies and partners. Additionally, Sponsors should include information that may enhance innovation, such as the use of MOSA to support future interoperability in development by using existing modular interface standards and to enable communication between such systems, platforms, and components. Any information on MOSA provided in this Section should be in-sync with Section 4 (Program Summary) of the IS-CDD and the PM's acquisition strategy, and briefly describe any considerations that may affect a future system or subsystem's interoperability with the base system (e.g., inclusion of system interfaces that support one or many consumer/producer systems and are compliant with consensus-based standards). As appropriate, AI capabilities should be considered.

2.5.7.2. If applicable, Sponsors will address intelligence interoperability requirements consistent with Annex G to Appendix G to this Enclosure.

2.5.7.3. Physical Interoperability. The Sponsor shall describe the physical aspects of joint interoperability that may impact the capability solution proposed. 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. The Sponsor should use this Section to describe any physical requirements (i.e., required landing space, runway length, etc.) that may impact the Joint Force. Additionally, the Sponsor should use this Section to describe any SoS or FoS considerations for the proposed capability solution.

2.5.7.4. Net-Ready Interoperability. Net-Ready shall be discussed as described in the Interoperability Guide, Annex A to Appendix G of this Enclosure. If applicable, Sponsors must include a NR Attribute table in Section 5 of the IS-CDD (Reference Paragraph 2.5.5.5. of this manual) that presents the Net-Ready performance attributes and their associated metrics in terms of a standardized framework and data sources to leverage when developing attributes and their threshold and objective values. Threshold and objective performance values should be represented in numerical form whenever possible to preclude subjective interpretation. Figure B-8 represents a format for the Net-Ready performance attribute source table for NR IS-CDD attribute development. Figure B-8 is an example of the Net-Ready Sources Table which shows from where each part of the Net-Ready data derives from/traces to. The NR Source Table is not required in the IS-CDD.

2.5.7.5. 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. JTTI is driven through the use of common technical standards and their employment across the Joint Training Synthetic Environment (JTSE) capabilities that support joint training. State the intent to design these systems to the JTSE technical standards, and include a discussion of all related technical approaches required to ensure technical interoperability. JTSE standards are maintained in the DoD IT Standards Registry (DISR) and continue to mature as the JTSE modernizes. Discuss any gaps in JTSE standards as applicable to the sponsor's program. The proponent for JTTI is the Joint Staff J7 Force Development & Design FCB.

2.5.7.5.1. Sponsors should consider the JS J7 tool to build a Standards Profile (StdV-1) for the Joint Training Synthetic Environment (JTSE) using the GTG-F tools. The tool is located at https://jasm.apps.mil/prweb/PRWebLDAP1. The StdV-1 is created for an existing system profile using the Actions dropdown menu. Instructions for creating the StdV-1 and -2 are available at https://jasm.apps.mil/prweb/PRWebLDAP1/app/gtgf_/PhFF9svb6aGqZSMHQjO_iaFP4yd_1acm*/!STANDARD.". "DoDI 8310.01, Information Technology Standards in the DoD" is the DoD issuance that governs Information Technology Standards and the DISR.

2.5.7.6. Artificial Intelligence.

2.5.7.6.1. For capabilities that may employ AI, Sponsors shall incorporate an assessment of alignment with the DoD's AI Ethical Principles into the AI system requirements, which should be repeated throughout the system's lifecycle, IAW References [4] and [179]. The DoD AI Ethical Principles build on and complement the existing ethical, legal, safety, and policy frameworks that are the hallmark of the Defense Department. They apply to all DoD Al capabilities, of any scale, including AI-enabled autonomous systems, for warfighting and business applications. The DoD AI Ethical Principles are:

2.5.7.6.1.1. Responsible. DoD personnel will exercise appropriate levels of judgment and care, while remaining responsible for the development, deployment, and use of AI capabilities.

2.5.7.6.2. Equitable. The Department will take deliberate steps to minimize unintended bias in AI capabilities.

2.5.7.6.2.1. Traceable. The Department's AI capabilities will be developed and deployed such that relevant personnel possess an appropriate understanding of technology, development processes, and operational methods applicable to AI capabilities, including transparent and auditable methodologies, data sources, and design procedure and documentation.

2.5.7.6.2.2. Reliable. The Department's AI capabilities will have explicit, well-defined uses, and the safety, security, and effectiveness of such capabilities will be subject to testing and assurance within those defined uses across Al capabilities' entire life-cycle.

2.5.7.6.2.2.1. Governable. The Department will design and engineer AI capabilities to fulfill their intended functions while possessing the ability to detect and avoid unintended consequences, and the ability to disengage or deactivate deployed systems that demonstrate unintended behavior.