NATO Interoperability Standards and ProfilesNISP gives guidelines to capability planners, programme managers and test managers for NATO common funded systems in the short or mid-term timeframes.The NISP prescribes the necessary technical standards and profiles to achieve interoperability of Communications and Information Systems in support of NATO's missions and operations. In accordance with the Alliance C3 Strategy (ref. C-M(2014)0016) all NATO Enterprise (ref. C-M(2014)0061) entities shall adhere to the NISP mandatory standards and profiles in volume 2.Other activities, that assure interoperability within the alliance should list their profiles in the NISP.STANAG [is] NATO's abbreviation for STANdardization AGreement, which set up processes, procedures, terms, and conditions for common military or technical procedures or equipment between the member countries of the alliance.North Atlantic Treaty OrganizationNATO_4c62b5be-8b86-11e2-bbba-8b8d68e382cbC3B Interoperability Profiles Capability TeamNISP StakeholdersThe intended audience of the NISP are all stakeholders in the NATO Enterprise, and Allied and Partner nations involved in development, implementation, lifecycle management, and transformation to a federated environment.NATO EnterpriseAllied NationsPartner NationsNISP Stakeholder GroupsThere are specific viewpoints that are mapped to the NISP structure. NISP gives guidelines to:Capability Plannersinvolved in NDPP and NATO led initiativesProgramme Managersfor building NATO common funded systemsTest Managersfor their respective test events (such as CWIX, CIAV, etc.)National Initiative Managersnational planning and programme managers for their national initiativesNational Planning ManagersNational Programme ManagersNATO standardization OrganizationSTANAG's are managed by the NATO standardization Organization (NSO). NATOSTANAGS's that are promulgated shall be considered mandatory only for NATO commonfunded systems. If NISP references a STANAG, the obligation status for it is only informative. The NSO maintains the obligation status in their own process of standardization.NATO Common Funded SystemsThe mandatory standards and profiles documented 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.Interoperability among NATO's communications and information systems_49e3dfa6-8a53-11ea-98df-082c0e83ea00To prescribe technical standards and profiles in support of NATO's missions and operations_49e3e17c-8a53-11ea-98df-082c0e83ea00StandardizationStandards (their content) are defined and managed in their life cycle by standardization bodies with their own timetable. A standard may have life cycle status such as emerging, mature, fading, or obsolete. Different standardization bodies may use their own lifecycle status definitions. NISP takes lifecyle status of standards into account, but does not copy them into the NISP database. For aspects of obligation status for standards in planning and programmes, see the next paragraph.InteroperabilityProfiles define the specific use of standards at a service interoperability point (SIOP) in a given context. Profiles support prerequisites for programmes or projects and enable interoperability implementation and testing. Interoperability Profiles provide combinations of standards and (sub)profiles for different CIS and identify essential profile elements including:* Capability Requirements and other NAF architectural views,* Characteristic protocols,* Implementation options,* Technical standards,* Service Interoperability Points, and* The relationship with other profiles such as the system profile to which an application belongs.ObligationsThe NISP now defines the obligation status of profiles and standards as "mandatory" or "candidate".* Mandatory: The application of standards or profiles is enforced for NATO common funded systems in planning, implementing and testing. NATO STANAGS's that are promulgated shall be considered mandatory. Nations are invited to do the same nationally to promote interoperabilty for federated systems and services.* Candidate: The application of profiles and standards shall be planned for future programmes. The standard or profile is mature enough to be used in programmes in 1 to 2 years. This implies, that from a planning perspective, this standard or profile may become mandatory at the time, the programme starts. A candidate standard or profile shall stay in volume 3 no longer than 2 years, unless explicitly marked as an exception to this rule.DynamicsProfiles shall be updated if referenced standards change. Profiles are dynamic entities by nature. NATO captures this dynamic situation by updating profiles once a year in the NISP. Profile owners are responsible for the versioning of their profiles. Profile reviews are required every 2 years by their owners to ensure their accuracy and continued relevance.FlexibilityProposed profiles (and standards) can be accepted as candidates in order to follow their developments and to decide if they can be promoted to mandatory standards and profiles. In some cases proposed standards and profiles can be readily accepted directly as mandatory.RelationshipsInteroperability Profiles can reference other Interoperability Profiles to allow for maximal reuse.ReuseRelationshipsDocument relationships among NATO planning documents_49e3e2d0-8a53-11ea-98df-082c0e83ea001CREATING RELATIONSHIPS TO OTHER CONCEPTS AND PLANNING OBJECTS WITHIN NATO -- Different initiatives and organizations have developed new concepts to govern developments in the interoperability domain. These concepts have logical relationship to the NISP.Building BlocksDescribe each aspect of the overall model_49e3e410-8a53-11ea-98df-082c0e83ea001.1Architecture Building Block -- An Architecture Building block is a constituent of the architecture model that describes a single aspect of the overall model.CharacteristicsSpecify the characteristics of Architecture Building Block (ABBs)_49e3e53c-8a53-11ea-98df-082c0e83ea001.2ArchitectureCapture architecture requirements; e.g., business, data, application, and technology requirements_49e3e668-8a53-11ea-98df-082c0e83ea001.2.1SolutionsDirect and guide the development of Solution Building Blocks_49e3e794-8a53-11ea-98df-082c0e83ea001.2.2SpecificationsInclude the specified content_49e3e8c0-8a53-11ea-98df-082c0e83ea001.3Specification Content -- ABB specifications include the following as a minimum:Functionality & AttributesDocument fundamental functionality and attributes: semantic, unambiguous, including security capability and manageability_49e3e9e2-8a53-11ea-98df-082c0e83ea001.3.1InterfacesDocument interfaces: chosen set, supplied_49e3eb18-8a53-11ea-98df-082c0e83ea001.3.2Interoperability & RelationshipsDocument interoperability and relationship with other building blocks_49e3ec44-8a53-11ea-98df-082c0e83ea001.3.3Dependencies & InterfacesDocument dependent building blocks with required functionality and named user interfaces_49e3ed7a-8a53-11ea-98df-082c0e83ea001.3.4Entities & PoliciesMap to business/organizational entities and policies_49e3eeba-8a53-11ea-98df-082c0e83ea001.3.5NetworkingElevate the maturity of federated mission networking capabilities_49e3efdc-8a53-11ea-98df-082c0e83ea001.4FMN Spiral Specifications -- Federated Mission Networking (FMN) Spiral -- Specifications encompass "an evolutionary cycle that will raise the level of maturity of federated mission networking capabilities over time".The FMN spiral specification contain the following sections ...The Mandatory and Candidate FMN Spiral Profiles, in context for FMN Affiliates, are listed in the NISP Volumes 2 and 3.ArchitectureDocument the architecture_49e3f108-8a53-11ea-98df-082c0e83ea001.4.1InstructionsDocument instructions_49e3f25c-8a53-11ea-98df-082c0e83ea001.4.2ProfilesDocument the profiles_49e3f3a6-8a53-11ea-98df-082c0e83ea001.4.3RequirementsSpecify the requirements_49e3f4d2-8a53-11ea-98df-082c0e83ea001.4.4Systems & CapabilitiesReference NISP profiles for Common Funded Systems and Capability Packages_49e3f5f4-8a53-11ea-98df-082c0e83ea001.5Capability Packages -- Profiles will be referenced in the NISP for specified NATO Common Funded Systems or Capability Packages and may include descriptions of interfaces to National Systems where appropriate.OrganizationHighlight the structure of the NISP_49e3f70c-8a53-11ea-98df-082c0e83ea002ORGANIZATION OF THE NISP INFORMATION -- This chapter gives an overview of the new structure of all three volumes.UsageList and categorize the standards and profiles according to their usage in NATO_49e3f82e-8a53-11ea-98df-082c0e83ea002.1NISP STRUCTURE -- The structure of the NISP is organized to list and categorize the standards and profiles according to their usage in NATO. It contains three volumes ...Standards and Interoperability Profiles for programmes to start in 1 to 2 years.034. Volume 2 is normative for NATO common funded systems and Volume 3 is informative.Concepts & ManagementIntroduce basic concepts and provide the management framework for the configuration control of the NISP_49e3f9be-8a53-11ea-98df-082c0e83ea002.1.1Volume 1 - Introduction: This volume introduces basic concepts, provides the management framework for the configuration control of the NISP and the process for handling Request for Change (RFC). It includes also guidance on development of interoperability profiles.Standards & ProfilesList agreed interoperability standards and profiles_49e3faea-8a53-11ea-98df-082c0e83ea002.1.2Volume 2 - Agreed Interoperability Standards and Profiles: This volume lists agreed interoperability standards and profiles, mandatory for NATO common funded systems. These should support NATO and National systems today and new systems actually under procurement or specification.Near-Term ProgrammesProvide Standards and Interoperability Profiles for programmes to start soon_49e3fc84-8a53-11ea-98df-082c0e83ea002.1.3Volume 3 - Candidate Interoperability Standards and Profiles: This Volume provides Standards and Interoperability Profiles for programmes to start in 1 to 2 years.CapabilitiesSupport interoperability of capability planning systems_49e3fee6-8a53-11ea-98df-082c0e83ea003INTEROPERABILITY IN SUPPORT OF CAPABILITY PLANNING -- The following documents form the foundation to understand the embedding of NISP into NDPP and architecture work:* Document: Alliance C3 Strategy Information and Communication Technology to prepare NATO 2020 (7 March 2014) Document Reference: Alliance C3 Strategy Document Reference: C-M(2014)0016* Document: Alliance C3 Policy (25 April 2016) Document Reference: C-M(2015)0041-REV1* Document: NATO Defence Planning Process (NDPP) Document Reference: PO(2016)0655 (INV)Identification, Development & AcquisitionIdentify the required capabilities and promote their timely and coherent development and acquisition by Allies and Partners_49e40026-8a53-11ea-98df-082c0e83ea003.1The NATO Defence Planning Process (NDPP) is the primary means to identify the required capabilities and promote their timely and coherent development and acquisition by Allies and Partners. It is operationally driven and delivers various products which could support the development and evolution of more detailed C3 architecture and interoperability requirements. The development of NDPP products also benefits from input by the architecture and interoperability communities, especially the NISP, leading to a more coherent development of CIS capabilities for the Alliance...More information on how the NISP supports the NDPP can be found in Annex BStandardsSelect coherent sets of standards for profiles_49e40152-8a53-11ea-98df-082c0e83ea003.2The work on Enterprise, Capability, and programme level architecture will benefit from the NISP by selecting coherent sets of standards for profiles.ConfigurationManage configuration_49e402a6-8a53-11ea-98df-082c0e83ea004CONFIGURATION MANAGEMENTUpdatingUpdate the NISP annually_49e403e6-8a53-11ea-98df-082c0e83ea004.1The NISP is updated once a year to account for the evolution of standards and profiles.NISP SubmissionSubmit the revised NISP to the C3 Board_49e4051c-8a53-11ea-98df-082c0e83ea004.1.1Interoperability Profiles Capability Team (IP Cat)C3 BoardConsultation, Command and Control BoardNISP UPDATE PROCESS -- The new NISP version is submitted to the C3 Board by end of the year after internal review by the IP CaT. The version under review is a snapshot in time of the status of standards and profiles.DatabaseConsider the database maintained by the IP CaT as the definitive source of standards and profiles._49e4068e-8a53-11ea-98df-082c0e83ea004.1.2IP CaTThe database of standards and profiles maintained by the IP CaT is the definitive source of the current status of standards and profiles.ChangesProcess requests for changes_49e407e2-8a53-11ea-98df-082c0e83ea004.2IP CaTRequest for Change (RFC) to the NISP will be processed by the IP CaT, following the process in the graphic below:NISP ManagementInclude all information required for the NISP management_49e40922-8a53-11ea-98df-082c0e83ea004.2.1The RFC contains all information required for the NISP management by IP CaT; The detailed information about standard or profile is handed over as attachments to this form...RFC SubmissionSubmit RFCs to the IP CaT_49e40a80-8a53-11ea-98df-082c0e83ea004.2.2IP CaTThe primary point of contact for RFC submission is the IP CaT. RFCs may be submitted to the IP CaT via the Change web site or via email to the indicated email address with attachments.CoordinationCoordinate review of RFCs with the responsible C3 Board substructure organizations_49e40bd4-8a53-11ea-98df-082c0e83ea004.2.3Review of RFCs will be coordinated with the responsible C3 Board substructure organizations where appropriate.ReviewsReview submissions in dialog with national and international bodies._49e40d14-8a53-11ea-98df-082c0e83ea004.2.4The IP CaT reviews the submissions in dialog with national and international bodies. Based on that review, the RFC will be formally processed into the next version of the NISP; or returned to the originator for further details; or rejected. The IP CaT will attempt to address all RFCs submitted by 1 September into the next NISP release. RFCs submitted after this date may be considered for inclusion at the discretion of the IP CaT, or will be processed for the following NISP release.FormatsPublish NISP products in several formats_49e40e7c-8a53-11ea-98df-082c0e83ea004.3NISP PRODUCTS -- 047. The NISP is published in several formats:* Documentation in HTML and PDF Formats;* Website and searchable online Database;* Data export in XML format.CoordinationCoordinate national systems interoperability_49e40fda-8a53-11ea-98df-082c0e83ea005SMEsAs a result of the C3 Board substructure reorganization, participants in IP CaT are subject matter experts (SME) and are no longer national representatives. NATIONAL SYSTEMS INTEROPERABILITY COORDINATION -- Coordination of profiles and standards between Nations and NATO are critical for interoperability.Internal CoordinationCoordinate with national and C3 Board representatives_49e41124-8a53-11ea-98df-082c0e83ea005.1SMEsSME's should therefore coordinate with national and C3 Board representatives to ensure national perspectives are presented to IP CaT. As such, each of the IP CaT SMEs is responsible for:National SystemsCoordination standards and profiles with national systems_49e4128c-8a53-11ea-98df-082c0e83ea005.1.1Appropriate and timely coordination of standards and profiles with respect to interoperability with national systems;SME InputCoordinate SME input_49e413e0-8a53-11ea-98df-082c0e83ea005.1.2SMEsC3 Board Substructure GroupsCoordination of the SME input including coordination with national SMEs of other C3 Board substructure groups; andInformation & InsightProvide appropriate technical information and insight based on national market assessment_49e4152a-8a53-11ea-98df-082c0e83ea005.1.3Providing appropriate technical information and insight based on national market assessment.National CoordinationCoordinate interoperability technical standards and profiles at the national level_49e41688-8a53-11ea-98df-082c0e83ea005.2C3 BoardNational level coordination of interoperability technical standards and profiles is the responsibility of the C3 Board. When the NISP is approved by the C3 Board, it will become the NATO Standard covered by STANAG 5524 Edition 2. This STANAG contains the agreement of the participating nations regarding usage of the mandatory standards and profiles in the NISP.GuidanceProvide interoperability standards guidance_49e417d2-8a53-11ea-98df-082c0e83ea006INTEROPERABILITY STANDARDS GUIDANCEReferencesReference standards from different standardization bodies_49e41926-8a53-11ea-98df-082c0e83ea006.1Standardization BodiesThe NISP references Standards from different standardization bodies. In the case of a ratified STANAG, NATO standardization procedures apply. The NISP only references these STANAG’s without displaying the country-specific reservations. The country-specific reservations can be found in the NATO Standardization Organisation's NATO Standardization Document Database.PublicationPublish interoperability standards_49e41a98-8a53-11ea-98df-082c0e83ea006.2Combined Communications Electronics Board (CCEB)The Combined Communications Electronics Board (CCEB) nations will use NISP Volume 2 to publish the interoperability standards for the CCEB under the provisions of the NATOCCEB List of Understandings (LoU).TaxonomyOrganize the standards using NATO's C3 Taxonomy_49e41bf6-8a53-11ea-98df-082c0e83ea006.3The NISP organizes the standards using the structure of the latest approved baseline of NATO's C3 Taxonomy... a description of it can be obtained at: https://tide.act.nato.int/tidepedia/index.php/C3_Taxonomy. Currently, the standards only address a subset of the services in the taxonomy, mainly services in the group Technical Services. For some standards it is indicated that an appropriate mapping to the C3 Taxonomy could not yet be made.ContentInclude or reference standards or related documents that are generally available for NATO/NATO member nations/CCEB_49e41d5e-8a53-11ea-98df-082c0e83ea006.4In principle, NISP only contains or references standards or related documents, which are generally available for NATO/NATO member nations/CCEB.ExceptionsMake available a subset of documents to nations or organizations joining a specific missions or as members of special working groups_49e41f66-8a53-11ea-98df-082c0e83ea006.5However, a subset of documents may only be available for those nations or organizations, which are joining a specific mission or are members of a special working group. The membership in these activities is outside the scope of NISP.2018-08-032020-04-29https://nhqc3s.hq.nato.int/Apps/Architecture/NISP/pdf/NISP-v11-release.pdfOwenAmburOwen.Ambur@verizon.net