2.5.7. Section 7: Interoperability (JPR/KPP/KSA).

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 incremental development. Any information on MOSA provided in this section should be in- sync with Section 4 (Program Summary) of the 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).

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. (Reference the Net-Ready Guide in Annex A to Appendix G to this enclosure). Net-Ready Interoperability shall be discussed as described in Annex A to Appendix G of this enclosure. If applicable, Sponsors must include a NR Attribute table in Section 5 of the 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-11 represents the required format for the Net-Ready performance attribute summary table for the CDD located in Section 5. Figure B-12 is the Net-Ready Sources Table which shows from where each part of the Net Read Table derives from/traces to.

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 Integration FCB.