105. The open systems architectural concept is based primarily on the ability of systems to share information among heterogeneous platforms. It is a concept that capitalizes on those specifications and services that can support the effective design, development and implementation of software intensive system components. Within an open system, those products selected and utilized must first comply with the agreed upon architecture to be considered truly open. Furthermore, the functionality desired must adhere to specifications and standards in order to be structurally sound.  The challenge for NATO is to achieve interoperability where two or more systems can effectively exchange data: without loss of attributes; in a common format understandable to all systems exchanging data; in a manner in which the data is interpreted the same; and in an agreed common set of profiles.

106. The NOSWG developed the NISP to guide NATO development of open systems and foster interoperability across the organization.  This document provides a minimal set of rules governing the specification, interaction, and interdependence of the parts or elements of NATO Command and Control Systems whose purpose is to ensure interoperability by conforming to the technical requirements of the NISP. The NISP identifies the services, building blocks, interfaces, standards, profiles, and related products and provides the technical guidelines for implementation of NATO CIS systems.

107. Developing profiles enables interconnecting partners to rapidly engage at any stage of the NRF cycle.  These profiles will be consistent with the NNEC Generic Framework and included in the NISP.  Incorporation of Service Oriented Architectures (SOAs) and related architectural frameworks will drive the coherent development of NATO capabilities as well as the interoperability with national elements.

108. NISP Volume 1 linkages to stakeholders and processes, use of Volume 2 technologies and standards as the primary source for profile technologies and maturities, as well as use of the NISP Request for Change Proposal Process drive the NRP Profile development.

109. As the NISP impacts on the full NATO project life cycle, the user community of the NISP may be comprised of engineers, designers, technical project managers, procurement staff, architects and communications planners.  Architectures, which establish the building blocks of systems operation, are most applicable during the development phase of a project.  This formula becomes less apparent when applied to the dynamic NRF environment, where interoperability of mature national systems requires an agile approach to architectures.

110. The NOSWG has undertaken the development of NRF interface profiles in order to meet the need for implementation specific guidance at interoperability points between NATO and Nations.  As a component of the NISP, NRF interface profiles can have great utility for NRF standup and operations, using mature systems, at the deployment/operational stage.   Application of these documents also provides benefit to Nations and promotes maximum opportunities for interoperability.  Profiles for system development and operational use within an NRF enable Nations to coordinate their systems’ readiness and availability in support of NATO operations.