B.4. NRF Interface Profile Development

B.4.1. Approach

111. The approach used to develop these NRF Interface Profiles was based on the following considerations:

  1. Stand-alone Compendium to NISP,

  2. Linked to NISP Volume 1 relationship, Volume 2 standards,

  3. Enables transfer of lessons learned from exercises and deployments through NISP change proposal process (RFCPs),

  4. Leverages concept of Interoperability Points (IOPs),

  5. Applicable to various information exchange environments (NATO-NATO, NATO-Nation, Nation-Nation),

  6. Modular for use in pre-deployment lifecycle (CIS Planners) and operational command (NRF Commands) scenarios,

  7. Specify profiles across the network, services, and application layers,

  8. Support Open System concepts, technologies and standards, and

  9. Supports migration to NATO Net-Enabled Capability (NNEC).

B.4.2. Process

112. NRF Interface Profile initiatives are intended to link to the established processes undertaken during NRF planning.  This NRF Generic Profile serves as a guideline for development of a rotation specific NRF Interface Profile.  The steps in this process include:

  1. Initial Assessment

    1. Development of timeline of activities (up to 2 years prior to participation in an NRF rotation).

    2. Determine information exchange scenario (NATO/Nation).

    3. Identify list of information exchange services.

    4. Development of notional CIS architecture (systems, technologies, services).

    5. Review of NRF Generic Interface Profile for process, template.

    6. Initial review of NISP Volume 1 for relationships and processes.

    7. Review of NISP Volume 2 for list of currently available, mature, and preferred technologies and standards for CIS.

    8. Review of NISP Volume 3 and 4, as well as COI specific solutions for potential employment in an NRF.

    9. Development of draft Interface Profile as per generic template.

    10. Submission of RFCPs for NISP update to reflect rotation specific requirements.

  2. Pre-Deployment Planning

    1. Identification of NRF CIS test/evaluation opportunities (CWIX, Combined Endeavour, Steadfast Cathode).

    2. Contribution of draft rotation specific interface profile at Initial Planning Conferences.

    3. Test and evaluation of NRF CIS environment as per draft interface profile and test specific architecture/scenario.

    4. Lessons Learned and RFCP development/submission.

    5. Update of rotation specific profile.

  3. Operational Readiness

    1. Monitoring of new CIS requirements.

    2. Lessons Learned and RFCP development.

    3. Update of rotation specific profile as needed.

113. Upon conclusion of an NRF rotation, incorporation of lessons learned into the NISP and NRF Interface Profile Compendium ensures that future rotations benefit from the operational experiences of prior rotations.

B.4.3. NRF Interface Profile Template

114. Development of a timeline of activities allows harmonization of NRF Interface Profile documentation, with NRF CIS planning efforts, to ensure that mature capabilities are available for NRF employment during operational readiness.  Optimal timing initiates a planning and development cycle that starts two years prior to participation/command of an NRF component.

115. Identification of the Information Exchange Scenario focuses on profile development which is relevant to the interconnecting partners, whether NATO, National, or another community of interest.  This establishes the stakeholders and interdependencies for the NRF CIS participants, and allows full consideration for actual versus desired functionality.  Ideally a single interface profile would serve the majority of needs for the particular NRF environment however some modifications may be necessary to take advantages of more mature capabilities that may be available to a subset of participants.

116. Architecture development must be flexible to be initially based on the operational requirements, but must be continuously re-evaluated as operational and technological changes are introduced.  A diagram of core systems, technologies, and CIS services should be identified in the architecture must continue to be revised throughout the life cycle planning process.

117. Interface Profiles will be drafted in accordance with the NISP Profile Guidance.  This categorization of CIS parameters is intended to decompose the interoperability point between two interconnecting entities as per the defined information exchange scenario.  The interoperability point (IOP) is defined by the interfaces, standards, parameters, services, applications, numbering and protocols that exists at the meet-me point between two interconnecting CIS environments.