Chapter 2. Purpose of the NISP5. The NATO Interoperability Standards and Profiles (NISP) provides the necessary guidance and technical components to support project implementations and transition to NATO Network Enabled Capability (NNEC). Also the Combined Communications Electronics Board (CCEB) nations use the NISP to publish the interoperability standards for the CCEB under the provisions of the NATO-CCEB List of Understandings (LoU) detailed in Appendix A of this volume. In addition, in order to support the Prague Capabilities Commitment (PCC), more emphasis is placed on interoperability profiles to support the NRF and transition from today's legacy systems to NNEC. 6. The purpose of the NISP is to:
7. The stakeholders of the NISP are all NNEC stakeholders involved in development, implementation, lifecycle management, and transformation to an NNEC environment. 8. This document provide a general description of the current version of the NISP. Volume 1 of the six volumes deals with the NISP background, the structure and the process of collecting standards from stakeholders, including the configuration management and publication of the NISP. Volume 2 focuses on near-term implementation (i.e. present[1] to 2 years in the future), Volume 3 focuses on mid-term implementation (2 to 6 years in the future), and Volume 4 focuses on long term implementations (greater than 6 years in the future). Volume 5 contains a supporting Rationale that describes the rationale for the content of volumes 2, 3 and 4.; Volume 6 contains a number of appendices relevant to the NISP. 9. The mandatory standards and profiles in Volume 2 will be used in the implementation of NATO Common Funded Systems. Participating nations agree to use the mandatory standards and profiles included in the NISP at the Service Interoperability Points and to use Service Interface Profiles among NATO and Nations to support the exchange of information and the use of information services in the NATO realm. 10. A NISP Profile contains more than a technical standards profile with a protocol stack and implementation options and settings. It also includes a refined operational view depicting the placement of the profile and its relationships with other profiles; and a refined system view identifying the service components and their descriptions. |