1. Purpose. This instruction:

     a. Establishes policies and procedures for the J-6 interoperability requirements certification of mission need statements (MNSs), Capstone Requirements Documents (CRDs), and operational requirements documents (ORDs) required by reference a.

     b. Details a methodology to develop interoperability key performance parameters (KPPs) derived from a set of top-level information exchange requirements (IERs) as required by reference a and based on the format and content of the integrated architecture products described in the C4ISR Architecture Framework (reference h).

     c. Establishes policies and procedures for the J-6 supportability certification of command, control, communications, computers, and intelligence (C4I) support plans (C4ISPs).

     d. Establishes policies and procedures for the J-6 interoperability system validation.

2. Cancellation. CJCSI 6212.01A, 30 June 1995, "Compatibility, Interoperability, and Integration of Command, Control, Communications, Computers, and Intelligence Systems," is canceled.

3. Applicability

     a. This instruction applies to the Joint Staff, Services, unified commands, and those DOD field activities and Defense agencies supporting the defense acquisition responsibilities of the Chairman of the Joint Chiefs of Staff. This instruction also applies, in general, to other agencies preparing and submitting requirements IAW references b and c.

     b. Highly sensitive classified programs will comply with this instruction, but will be tailored to account for special security considerations (reference b, part I, paragraph 1.4, and reference c, page 2).

     c. This instruction does not preclude the need to refer to reference a, "Requirements Generation System," and the basic DOD 5000 series documents for guidance and direction on defense acquisition. All DOD components responsible for generating requirements documents will base their respective procedures for ACAT II and below programs on those contained in reference a.

     4. Scope. This instruction addresses the interoperability and supportability of new National Security Systems (NSS) and information technology systems (ITS) or modifications to existing systems regardless of ACAT. NSS and ITS are defined in Part II of the Glossary. Intelligence supportability is addressed in a separate, but related, process conducted by the J-2. This instruction considers automated information systems (AISs) to be an ITS.

5. Policy

     a. National Security Systems and Information Technology Systems Development

          (1) For purposes of interoperability and supportability, all NSS and ITS developed for use by US forces are for joint (references d and e), combined, and coalition use. Interoperability and supportability of NSS and ITS requirements will be determined during the requirements validation process and will be updated as necessary throughout the acquisition period, deployment, and operational life of a system (reference a).

          (2) The overall objective of this policy decision is to develop, acquire, and deploy NSS and ITS that (1) meet the essential operational needs of US forces; (2) are interoperable with existing and proposed NSS and ITS; (3) are supportable over the existing and planned global information grid; and (4) are interoperable with allies and coalition partners.

     b. J-6 Certification and Validation Process. Figure 1 below illustrates the two J-6 certifications and one J-6 validation discussed in the following paragraphs. J-2 certification of intelligence supportability related to, but has distinctions from procedures in this instruction.

          (1) J-6 Interoperability Requirements Certification. This certification occurs prior to each acquisition milestone (0, I, II, III).

               (a) The J-6 certifies MNSs, CRDs, and ORDs, regardless of ACAT level, for conformance with joint NSS and ITS policy, doctrine, and interoperability standards. The J-6 also certifies the interoperability KPP derived from a set of top-level IERs. As part of the review process, J-6 requests assessments from the Services, Defense Information Systems Agency (DISA), and DOD agencies.

               (b) CINCs are required to review and comment on ACAT I/IA and Joint Requirements Oversight Council (JROC) special interest requirements documents during the J-8 JROC formal review. CINCs are provided the opportunity to review and comment on ACAT II and below documents during the J-6 interoperability requirements certification process.

               (c) USJFCOM, as the joint force integrator, will review and confirm sufficiency of interoperability KPPs and IER matrices for all CRDs and ORDs regardless of ACAT.

               (d) The J-6 forwards interoperability requirements certification to the JROC for ACAT I/IA and JROC special interest programs or to the sponsoring DOD component for ACAT II and below programs. Also, J-6 forwards unresolved interoperability issues to the Military Communications-Electronics Board (MCEB) or Military Intelligence Board (MIB) for resolution.

               (e) The MCEB or MIB will return resolved interoperability issues to the lead DOD component so it may complete JROC approval process. The MCEB and MIB will ensure that unresolved issues resulting from interoperability assessments are presented to the JROC for resolution or further action (see Enclosure D, Figure D-1).

          (2) J-6 Supportability Certification. The J-6 certifies to ASD(C3I) that C4ISPs, regardless of ACAT, adequately address NSS and ITS infrastructure requirements, the availability of bandwidth and spectrum support, funding, personnel, and identify dependencies and interface requirements between systems. As part of the review process, J-6 requests supportability assessments from DISA and DOD agencies. CINCs are provided the opportunity to review and comment on documents, regardless of ACAT, during the J-6 supportability certification process. J-6 conducts a supportability certification for C4ISPs prior to Milestone I, II, and III for submission to ASD(C3I) as part of the C4ISP review process. In a separate, but related process, the J-2 provides an intelligence supportability certification.

          (3) J-6 Interoperability System Validation. The J-6 validation is intended to provide total life-cycle oversight of warfighter interoperability requirements. The J-6 validates that the interoperability KPP derived from the set of top-level IERs approved in the CRD (if applicable), ORD, and C4ISP was adequately tested and testing results certified during the DISA (JITC) interoperability system test certification. Fifteen days after receipt of the DISA (JITC) interoperability system test certification memorandum (described in paragraph c below), the J-6 will issue an interoperability system validation memorandum to the respective Services, agencies, and developmental and operational testing organizations.

     c. Interoperability Testing and Test Certification

          (1) All NSS and ITS, regardless of ACAT, must be tested and testing results certified by DISA (JITC). Testing may be performed in conjunction with other testing (i.e., DT&E, OT&E, early user test) whenever possible to conserve resources. Interoperability evaluation and testing will be conducted throughout the life cycle of NSS and ITS and interfaces. See Appendix B to Enclosure D for a description of the interoperability system test and certification process.

          (2) Interoperability testing and test certification must be addressed as an integral part of the requirements generation process prior to production and fielding approval (if not sooner) by the milestone decision authority (MDA) at all ACAT levels.

          (3) Standards conformance testing, as well as interoperability interface testing, will be planned and conducted during the development and acquisition of the system with the systems being certified in writing by DISA (JITC) prior to each program’s milestone decision.

          (4) Hardware and software modifications that affect interoperability of fielded NSS and ITS will require DISA (JITC) recertification before the modifications are fielded for initial operational capability (IOC).

     d. Interoperability Policy and Test Panel

          (1) MCEB Interoperability Policy and Test Panel (IPTP) resolves issues in joint testing and interoperability certification. Intelligence interoperability issues will be referred to the MIB.

          (2) A temporary waiver from interoperability system testing certification -- an Interim Authority to Operate (IATO) -- may be granted by the IPTP in special situations.

          (3) Submit requests for an IATO to the IPTP IAW reference f (or see the DISA (JITC)/IPTP website: http://jitc.fhu.disa.mil).

          (4) IATOs will not to exceed 1 year.

     e. Interoperability Testing and Test Certification Programming and Budgeting

          (1) CINCs, Services, and agencies (C/S/As) are generally responsible for funding interoperability testing for systems that have not reached IOC. Required interoperability testing and certification will impact schedule and program cost and will need to be added to POM and program cost estimates.

          (2) C/S/A may designate and fund another C/S/A test organization to conduct interoperability testing.

          (3) When DISA (JITC) is not the interoperability testing organization, interoperability test plans, test analysis, and test reports will be coordinated with and approved by DISA (JITC) to ensure sufficient information is available to allow DISA (JITC) to certify a system. Tests and certifications are scheduled by DISA (JITC), with a balance between the program manager’s schedule, DISA (JITC)’s available test resources, organizational priorities, and functional priorities.

     f. Interoperability Testing and Test Certification Prioritization. C/S/As will incorporate interoperability testing into their overall testing plans in coordination with DISA (JITC).

          (1) DISA (JITC) uses the following organizational prioritization for testing, assessing, and certifying interoperability: (1) joint NSS and ITS systems that support the unified commands, (2) joint NSS and ITS systems that are acquired by the Services, and (3) systems that are acquired by the Defense agencies.

          (2) The order for functional prioritization is: (1) tactical and strategic warning and communications that support the unified commands and the National Command Authorities (NCA); (2) C2 systems that support the unified commands; (3) intelligence systems that support the unified commands; and (4) combat service support systems that support the unified commands.

          (3) The proposed DISA (JITC) interoperability testing and test certification schedule will be submitted to the IPTP for review and approval. Any conflicts in schedules, testing resources, or priorities are resolved by the IPTP, if possible. Issues that cannot be resolved by the IPTP process will be brought to the attention of the MCEB for final resolution.

          (4) The interoperability test certification prioritization process is intended as a positive enhancement to overall system development and should not impede, delay, or restrict individual system milestone accomplishment as a result of a lack of testing resources. Should test delays occur as a result of the lack of tester resources, then test waivers should be submitted to the IPTP.

     g. Standardized Test Plans. DISA develops standardized test plans and procedures in coordination with the Services and agencies for conducting standards conformance testing, interoperability testing, and certification of specific categories or classes of NSS and ITS systems. The standardized test plans and procedures for conducting interoperability system test certification are available from DISA (JITC).

     h. Information Technology Standards. New or modified NSS and ITS systems should be standards-based. NSS and ITS must comply with applicable information technology standards contained in the current DOD Joint Technical Architecture (JTA) (reference g is available at http://www-jta.ncr.disa.mil).

     i. NSS and ITS System-specific Policies. Current and newly established interoperability related policies that impact J-6 certifications are detailed in Enclosure E.

     j. Interoperability Key Performance Parameter (KPP)

          (1) CJCSI 3170.01A (reference a) requires CRDs and ORDs to contain an interoperability KPP that is derived from the set of top-level information IERs that characterize the information exchanges to be performed by the proposed family of systems (FoS)/system of systems (SoS) or system.

               (a) For CRDs, top-level IERs are defined as those information exchanges that are between systems that make up the FoS or SoS, as well as those that are external to the FoS or SoS (i.e., with other C/S/A, allied, and coalition systems).

               (b) For ORDs, top-level IERS are defined as those information exchanges that are external to the system (i.e., with other C/S/A, allied, and coalition systems).

          (2) Top-level IERs are derived from a high-level operational concept graphic and a system interface description that illustrate the proposed system’s information exchange requirements for mission accomplishment.

               (a) Top-level IERs at the CRD level do not impose, nor should they be construed as imposing, any specific material solution. CRD top-level IERs are designed to identify the basic characteristics of the information that needs to be exchanged between C/S/A, allies, and coalition partners in order to accomplish the mission.

               (b) IERs are described in a matrix format.

               (c) CRD Interoperability KPPs, and hence the IERs that the Interoperability KPPs are derived from, will be measurable.

               (d) ORD Interoperability KPPs, and hence the IERs that the interoperability KPPs are derived from, will be measurable and testable.

          (3) The interoperability KPP, along with other KPPs and critical technical and operational issues, is used to develop the C4ISP and the test and evaluation master plan (TEMP). A methodology to develop CRD and ORD interoperability KPPs, based on the procedures described in the C4ISR Architecture Framework (reference h) is detailed in Enclosure B.

6. Implementation and Supplementation. This instruction will not be supplemented without the prior approval of the Vice Chairman of the Joint Chiefs of Staff or his delegated representative.

7. Abbreviations, Acronyms, and Definitions. See the Glossary.

8. Responsibilities. See Enclosure A.

9. Summary of Changes. Major changes reflect revisions to reference a.  A methodology to develop CRD and ORD interoperability KPPs required by reference a is detailed in Enclosure B.  MNS, CRD, and ORD assessment criteria matrices were updated, and C4ISP assessment criteria matrix were added.  J-6 assessment tool procedures, J-6 supportability certification, and NSS and ITS specific policies were added.  C4I for the Warrior was deleted.

10. Effective Date. This instruction is effective upon receipt.

11. Releasability. This instruction is approved for public release and distribution is unlimited.  DOD components (to include the combat commands), other Federal agencies, and the public may obtain copies of this instruction through the Internet from the CJCS Directives Homepage -- http://www.dtic.mil/doctrine/jel/cjcsd.htm.  Cpoies are also available through the Government Printing Office on the Electronic Library CD-ROM.

Eclosures:
A--Responsibilities
B--Interoperability Key Performance Parameters and Top-Level Information Exchange Requirements
C--J-6 Interoperability and Supportability Certification Assessment Criteria
         Appendix A - Requirements Documents (MNSs, CRDs, ORDs)
         Appendix B - C4I Support Plan (C4ISP)
D--Procedures
         Appendix A - J-6 Assessment Tool
         Appendix B - Interoperability Testing and Test Certification Process
E--NSS and ITS System Specific Policies
F--References
Glossary