4. NISP AND CONFIGURATION MANAGEMENT PROCESS
058. The NISP has to be periodically updated to account for enhancements in technology. Updates to the NISP are handled through Requests For Change Proposal (RFCP). RFCPs are usually reviewed at regularly scheduled NOSWG meetings. RFCPs deemed urgent are handled in an expedited manner, outside the normal meeting schedule of the NOSWG with a reply to the RFCP originator within two weeks. 059. The four volume paper version of the NISP and its supporting Rational Document will be submitted to the NC3 Board by 15 December of each year. The paper version is a snapshot in time of the status of standards and profiles. The NISP database of standards and profiles is the definitive source of the currents status of standards and profiles. The database will be updated as soon as the RFCP has been approved by the appropriate authority (NC3 Board).
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| NISP- Introduction and Management .pdf | application/pdf | 276.73 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
1. INTRODUCTION
1.1. BACKGROUND
1.1.1. NATO C3 Technical Architecture 001.
In December 2005 the NATO Open System Working Group completed version 7 of the NATO C3 Technical Architecture (NC3TA). In May 2006 the Information Systems Sub Committee (ISSC) approved version 7 of the NC3TA on behalf of the NATO C3 Board (NC3B). Due to the reasons described below, this was the last version of the NC3TA. In December 2006 The NOSWG completed the first version of the NATO Interoperability Standards and Profiles (NISP) which is the replacement for the NC3TA. The first version of the NISP was noted by the C3 Capabilities Coherence Sub-Committee. At its meeting on 28 September 2007, The NC3REPS agreed that they would, on behalf of the NC3B, approve future versions of the NISP.