Importance of Interoperability

Interoperability within and among U.S. forces and U.S. coalition partners is an important goal for all systems so that the DoD has the ability to conduct joint (Army, Navy, USAF, Marines) and combined (multinational) operations successfully. Lack of interoperability among systems and forces causes our fighting units to be less effective in combat, and support of those forces will be degraded and less efficient.

Interoperability Requirements

During the Joint Capabilities Integration and Development (JCIDS) process, DoD Components work collaboratively to develop joint integrated architectures and joint concept of operations (CONOPs) for capability areas as agreed to by the Joint Staff. These joint architectures will guide the interoperability parameters for specific materiel solutions. These joint architectures and CONOPs will be reviewed on a regular basis to ensure capability needs and interoperability considerations remain current.

At the beginning of the JCIDS process, interoperability and information sharing needs shall be addressed as part of the Initial Capabilities Document (ICD). These constraints will then form the basis for the Capability Development Document (CDD) "Net-Ready" KPPs and interfaces to other systems.

Additionally, the Command, Control, Communication, Computers, and Intelligence Support Plan (C4ISP) documents interoperability requirements for a system's C4I. Recent changes to policy now require an Information Support Plan (ISP) which will replace the C4ISP. For non-information interoperability requirements, other integration plans will address interoperability. Although interoperability has been a required KPP, that the most recent release of CJCSI 3170.01 implements the use of "Net-Ready" KPPs. These Net-Ready KPPs (NR-KPP) are more focused on the information exchange requirements necessary to ensure specific capability needs are satisfied.

What is Interoperability?

Interoperability is the ability of systems or forces to provide and accept data, information, materiel, and services, enabling them to operate effectively together. For our forces, the most important areas for interoperability include language, communications, doctrine, and information exchange. From an acquisition perspective, we typically think of interoperability as weapon systems working together properly. Non-materiel aspects of interoperability must be considered throughout the process as well. The new DoD 5000 highlights the importance of considering interoperability throughout the acquisition process.

Acquiring Interoperable Systems

The acquisition strategy should reflect the interoperability planning accomplished during JCIDS process. Interoperability requirements established in the CCD and the C4ISP are then allocated to the individual sub-systems through the system engineering process. The MDA looks to the interoperability information contained in the acquisition strategy to make decisions on the system. These decisions should be made in the context of the joint integrated architectures and joint CONOPs, not just based on the needs of the particular system.

Architecture

Each integrated architecture shall have at least three views:

- Operational View to describe the joint capabilities that the user seeks and how to employ them.

- Systems View to characterize available technology and systems functionality and to identify the kinds of systems and integration needed to achieve the desired operational capability.

- Technical View consisting of standards that define and clarify the individual systems technology and integration requirements.

Interoperability Guidance

Testing & Evaluation

Interoperability and Net-Readiness must be considered during all test activities:

	Integrated test planning
	Early operational assessments
	Contractor test
	Development test
	Initial operational test and evaluation

Testers must use an integrated approach that ensures the flow of consistent and reliable data, information, and services among systems in the battlefield.