4.3.18.13. Interoperability and Dependencies
4.3.18.13. Interoperability and Dependencies
Almost all DoD systems operate in a system-of-systems (SoS) context relying upon other systems to provide desired user capabilities, making it vital that interoperability needs and external dependencies are identified early and incorporated into system requirements. When identifying system requirements, it is critical to consider the operational and SoS context (see DAG section 4.2.1.2. Systems of Systems). These include, but are not limited to, physical requirements (e.g., size, power limits, etc.), electronic requirements (e.g., signature, interference, etc.) and information exchange/management (e.g., network, bandwidth, information needs, etc.). These also include interdependencies with other systems. For efficiency, systems often rely on either services provided by other systems during operations or reuse of system elements developed by other programs.
The Program Manager is responsible for ensuring that the operational and SoS context for the system are well understood.
The Systems Engineer has the primary responsibility for ensuring all interoperability and dependency impacts are analyzed and collaborated with the appropriate internal/external stakeholders and are translated into system requirements and design considerations.
Analysis conducted for the SoS contexts for the system -- where the system is dependent on other systems and where the system needs to interact with other systems – enables translation of I&D into system requirements. I&D requirements call for collaborative implementation approaches with external organizations, including identification, management, and control of key interfaces. Areas of dependency and interoperability should be reviewed for risks to the program and plans made to manage and mitigate those risks. This review includes system interdependencies (e.g., weapon may depend on new sensor capabilities provided by another system) and information exchanges with other systems required to support mission capabilities. For efficiency, systems may rely on system elements developed by others for key functionality, either through services (e.g., weather information) provided by other systems or through reuse of system elements (e.g., engines, radios) developed by other programs. These contexts are analyzed to identify system requirements and risks, including actions needed by external parties (e.g., other systems or infrastructure) for the system to meet user requirements.
Additional DoD policy and guidance regarding I&D, summarized below, are directed at ensuring that systems work effectively with other systems:
- Interoperability of information technology and National Security System (NSS) acquisition programs are required to comply with DoDD 4630.05, DoDI 4630.8, CJCSI 3170.01, the JCIDS Manual (requires Common Access Card (CAC) to access website), CJCSI 6212.01, Public Law 104-106, and section 3506 of title 44, United States Code.
- DoDD 5000.01, Enclosure 1:
- Ability of acquired systems to exchange information and services with other systems and to interoperate with other United States forces and coalition partners, and as appropriate with other United States Government departments and agencies
- Providing systems and systems of systems that are interoperable and able to communicate across a universal infrastructure that includes organizational interactions, other systems, networks, and information exchange capabilities
- DoDI 5000.02, Enclosure 2: An integrated system design that defines system and system-of-systems functionality and interfaces, and reduces system-level risk
- DoDI 2010.06: Pursuing opportunities throughout the acquisition life cycle that enhance international cooperation and improve interoperability
DAG Tutorial 
