7.3.4. Net-Ready Key Performance Parameter (NR-KPP)
7.3.4.1. Supporting Architecture Views and Compliance
7.3.4.2. DoD Net-Centric Data Strategy
7.3.4.3. Global Information Grid (GIG) Technical Guidance (GTG)
7.3.4.4. Compliance with DoD Information Assurance (IA) Requirements
7.3.4.5. Compliance with Supportability Requirements
7.3.4. Net-Ready Key Performance Parameter (NR-KPP)
The Net-Ready Key Performance Parameter (NR-KPP) has been developed to assess net-ready attributes required for both the technical exchange of information and the end-to-end operational effectiveness of that exchange. The NR-KPP replaces the Interoperability KPP, and incorporates net-centric concepts for achieving IT (including NSS) interoperability and supportability. The NR-KPP assists Program Managers (PMs), the test community, and Milestone Decision Authorities in assessing and evaluating IT (including NSS) interoperability.
The NR-KPP assesses information needs, information timeliness, Information Assurance (IA), and net-ready attributes required for both the technical exchange of information and the end-to-end operational effectiveness of that exchange. The NR-KPP consists of verifiable performance measures and associated metrics required to evaluate the timely, accurate, and complete exchange and use of information to satisfy information needs for a given capability. PMs will use the NR-KPP documented in Capability Development Documents and Capability Production Documents to analyze, identify, and describe IT (including NSS) interoperability needs in the ISP and in the test strategies in the Test and Evaluation Master Plan. The following elements comprise the NR-KPP:
- Supporting architecture products, including the Joint Common Systems Function List (JCSFL) required to assess information exchange and operationally effective use for a given capability;
- Compliance with DoD Net-centric Data and Services strategies, including data and services exposure criteria;
- Compliance with applicable Global information Grid (GIG) Technical Guidance, to include DoD IT Standards Registry-mandated GIG net centric IT Standards reflected in the Technical Standards View-1 and, Functional and Technical Implementation of GIG Technical Profiles necessary to meet the net centric operational requirements specified in the architecture system views;
- Verification of compliance with DoD IA requirements; and
- Compliance with Supportability elements to include Spectrum Analysis, Selective Availability Anti-Spoofing Module (SAASM), and the Joint Tactical Radio System (JTRS).
7.3.4.1. Supporting Architecture Views and Compliance
In accordance with the DoD 4630 Series, architecture products or views defined in the DoD Architecture Framework (and related discussion in DoD Instruction 4630.8) shall be used to assess information exchange and use for a given capability. The functional proponent, domain owner, Principal Staff Assistant, and PM use the supporting architecture products or views in developing the NR-KPP and preparing the ISP.
PM compliance with required supporting architecture views is demonstrated through inspection and analysis of developed architecture views to determine conformance with DoD Architecture Framework specifications and that all required views have been produced. CJCS Instruction 3170.01 and CJCS Instruction 6212.01 requirements apply.
7.3.4.2. DoD Net-Centric Data Strategy
Compliance with the DoD Directive 8320.02, "Data Sharing in a Net-Centric Department of Defense" and the DoD Net-Centric Data Strategy is an essential prerequisite of net-centric operations. For a program to gain Interoperability and Supportability Certification, program data and services must be "exposed" by making data elements and provided services visible, accessible, and understandable to any potential user with access to the GIG, both anticipated and unanticipated.
Verification of compliance with the DoD Net-Centric Data Strategy and DoD Net-Centric Services Strategy will be accomplished through the analysis of the sponsor-provided architecture and verification products with accompanying text detailing the program's compliance strategy. Documentation (via architecture products or other forms) must clearly identify all net-centric services and data as adopted from Universal Core, Domain Cores, and COIs.
- In addition to the architecture products, sponsors must complete Data and/or Service Exposure Verification Tracking Sheets to self-evaluate compliance with the direction in the exposure directives.
- The Data and/or Service Exposure Verification Tracking Sheets are required. The preferred method is to use the Enhanced Information Support Tool (EISP) to generate the tracking sheets. Otherwise, the tracking sheets must be filled out manually and submitted to JS J6.
- A guide for selecting which type of Tracking Sheet is required for each program and instructions for the completion of each type is located on the CJCSI 6212 Resource Page.
7.3.4.3. Global Information Grid (GIG) Technical Guidance (GTG)
The GTG is an evolving web enabled capability providing the technical guidance necessary for an interoperable and supportable GIG built on Net-Centric principles. The GTG provides a one-stop, authoritative, configuration managed source of technical compliance guidance that synchronizes previously separate efforts. The GTG is designed to enable users to decide which guidance is applicable and to find detailed information and artifacts needed to meet functional requirements (GIG features and capabilities), DISR-mandatory GIG net-centric IT standards, supporting GIG IT standards, and GIG Technical Profiles (GTPs).
The GTG is the source for all technology guidance and standards implementation information used in describing GTPs necessary to meet the net centric operational requirements specified in the system/service views of an architecture. The GTG contains a program characterization questionnaire and compliance declaration matrix that points to applicable GTPs. The GTPs are built from DISR-mandated IT Standards reflected in a standards profile and include associated implementation guidance, reference architecture and testing criteria necessary to meet all GIG-related requirements characterized in the architecture system/service views. GTG Content includes:
- The GTG is designed to enable users to decide which guidance is applicable and to find detailed information and artifacts on:
- Associated technical functional requirements (GIG features and capabilities);
- DISR-mandated GIG net-centric IT standards;
- Supporting GIG IT standards;
- Associated profiles;
- Reference implementations; and
- Test criteria.
- The GTPs are aligned with the DoD IEA and are determined based on if following criteria capability:
- Spans organizational boundaries;
- Is mandatory or mission critical across the GIG Enterprise;
- Can be characterized in a GIG Technical Profile;
- Is essential for resolving GIG end-to end interoperability issues;
- Enables net centric information sharing for multiple acquisition programs; and
- Is important from a security perspective.
PM compliance with applicable GTG is demonstrated through inspection of JCIDS documentation and test plans, and during Joint Interoperability Test Command interoperability certification testing (see CJCS Instruction 3170.01 and CJCS Instruction 6212.01 for detailed discussions of the process).
7.3.4.4. Compliance with DoD Information Assurance (IA) Requirements
DoD IA requirements, including IA certification and accreditation, are specified in DoD Directive 8500.01, DoD Instruction 8500.2, DoD Directive 8581.1, and DoD Instruction 8510.01. Satisfaction of these requirements results in system accreditation and the issuance of an authorization to operate. See section 7.5 for details.
7.3.4.5. Compliance with Supportability Requirements
A Program Manager must ensure compliance to spectrum utilization and information bandwidth requirements, Selective Availability Anti-Spoofing (SASSM) and the Joint Tactical Radio System (JTRS), as applicable. See section 7.3.5.5 for details.
DAG Tutorial 
