{From Annex G, Appendix G, Enclosure B}

3.3.2.3. Intelligence Interoperability Support.

3.3.2.3.1. The Intelligence Interoperability (I2) support category addresses a capability’s requirement to exchange (send or receive) intelligence with an organization outside of the Service developing the capability. Sponsors must document any external (IC, Service or Coalition Partner) intelligence requirements in Section 3 of an ICD or Section 9.4 of a CDD. Sponsors must define external intelligence interoperability requirements at the data, tool, process and organization levels. Data standards, activities and organizational relationships must be documented using DoDAF Standards View-1 (StdV-1), Operational View-4 (OV-4) and Operational View-5b (OV-5b) IAW Appendix H to enclosure B.

3.3.2.3.1.1. The I2 section must be consistent with the Operational Context, Capability Discussion, Performance Attributes, DOTmLPF-P, Joint Interoperability, of the requirements document and associated DoDAF artifacts.

3.3.2.3.1.2. Sponsors will document any external intelligence exchanges, to include data standards, activities and organizational relationships in accordance with Appendix H TO Enclosure B; “DoDAF PRIMER”. Any applicable intelligence interoperability exchanges must be documented in the StdV-1, OV-4 and OV-5b DoDAF views. Sponsors will also depict any related intelligence networks (i.e. JWICS) in applicable SV’s.

3.3.2.3.1.3. If no external intelligence interactions (input or output) is required by the capability developer, then the Sponsor must state there are no I2 dependencies.

3.3.2.3.2. Sponsors must collaborate with J-283/IRCO and the DoD Intelligence Functional Managers as required to assess Sponsor-submitted I2 information: Signals Intelligence (SIGINT), NSA; Human Intelligence (HUMINT), DIA; Measurement and Signature Intelligence (MASINT), DIA; and Geospatial-Intelligence (GEOINT), NGA.