Implementing the

Net-Ready Key
Performance Parameter

presented by
Lesley Painchaud

INCOSE
Washington Metro Area
11 May 2010
Briefing Purpose

Provide an overview of the Net-Ready Key

Performance Parameter (NR-KPP)
Implementation Guidebook
 Background
 Approach
 Refined NR-KPP Compliance Statement
 4-Step Process

2
NR-KPP Implementation Guidebook
Background

Developed by
 Office of the Asst Secretary of the Navy (ASN) for
Research, Development and Acquisition (RDA) Chief
System Engineer (CHSENG), Oct 2009
Goal
 Clarify the NR-KPP in measurable-testable terms
Result
 Four-Step Process that Programs can use to meet
Interoperability & Supportability Requirements

3
 Decomposition of the Compliance Statement

Potential Net-Ready
Effectiveness and
Operational
Net-Ready Description Performance Measures

Potential Net-Ready
Compliance Measures

Program offices typically focus

here. Simply completing these
elements DOES NOT ensure the
KPP will be met.

An Interoperable System Must Address All 3 Components 4

 Overview of the Refined Compliance
Statement

Current NR-KPP Refined NR-KPP

Compliance Statement Compliance Statement

Clarification of Measures

Clarification of Measures

Clarification of Measures

Refinement Explicitly Highlights Effectiveness and Performance Measures

5
NR-KPP Guidebook 4-Step Implementation Approach

1. Mission Analysis NR-KPP operational requirements

 Mission threads and operational activities a system supports
 Associated effectiveness and operational performance measures
1. Information Analysis  information requirements
 Information exchanges and associated operational performance measures
1. Systems Engineering Process applied to NR-KPP
operational and information requirements
 Results in measurable and testable design and system solution
 Compliance measures are process constraints
1. Document outcomes of the SE process according to
engineering practices and compliance measures
 Architectures, Specifications, Traceability matrices, Test Procedures, etc.

Mission and Information Analyses Needed to Completely

Specify A System’s Operational Requirements

6
 Drawing Out Effectiveness, Performance, and
Compliance Measures

NR-KPP Description** Compliance

Measures*

Outcomes
- Missions supported by the system
Support Net Centric - Operational tasks for the mission
Military Operations* Inputs Mission

Constraints
Analysis Effectiveness and
Support Operational Performance Measures**
Activities* Step 1 - Effectiveness Measures for each
AV-1 mission
OV-1 - Operational Performance Measures
for each task
OV-4
OV-5
Inputs Systems Outcomes

OV-6c Engineering
NR-KPP Description**
Enter and Be Managed - Networks required for the mission Step 3
Outcomes
In the Network* - Information elements produced for SV-1
or consumed by each operational SV-2
Exchange Information*
Inputs Information task SV-4a
Analysis SV-5a
Performance Measures** SV-6/10c
Support Information Step 2 - Operational Performance Measures SV-7
Exchanges* OV-2 for network entry and management SV-11
- Operational Performance Measures
OV-3 for information element production
OV-7 and consumption Inputs

Documentation
* Elements from current NR-KPP Compliance Statement
** Elements from refined NR-KPP Compliance Statement in ASN (RDA) CHSENG’s NR-KPP Guidebook
Step 4
7
 Refined Compliance Statement

Net-Ready
Description Net-Ready
Effectiveness
and Operational
Performance
Measures

Net-Ready
Compliance8

Measures
 Summary
The NR-KPP Guidebook developed by ASN (RDA)
CHSENG proposes a 4-Step process to clarify
the NR-KPP in measurable and testable terms,
refine the NR-KPP Compliance Statement and
incorporate the requirements into system design

Mission Analysis 
Information Analysis 
SE Process 
Documentation

9
Questions?

10
Step 1. Mission Analysis
Constraints
- Missions and operational
tasks described in terms
the Fleet uses
- Measurable and testable
metrics

Inputs Mission Outputs

- JCIDS documentation
- ROC/POE
Analysis - Missions supported by
the system
- JMETLs and NMETLs - Mission effectiveness
- OPLANs, CONPLANs measures
- DPS - Operational tasks for the
mission
- Operational performance
measures for each task
11
 Step 1. Mission Analysis
Operational
Performance
measures are
needed for Effectiveness
each mission measures are
thread activity needed for
each mission
thread

*Slide from
NMETL
Program
Executive
Training, by
David Brown,
USFF N721B

Systems Engineering Requires Performance And Effectiveness Measures

12
 Sample Mission and Associated
Effectiveness Measure (From UJTL)
 OP 6.1.5 Conduct Joint Operations Area (JOA) Missile Defense
 To identify and integrate joint and coalition forces supported by national and theater
capabilities to detect and destroy enemy theater missiles directed toward the JOA in
flight or prior to launch. This task includes disrupting the enemy's theater missile
operations through an appropriate mix of mutually supportive passive missile defense,
active missile defense, attack operations, and supporting C4I measures. This task
includes providing early warning of theater missile attack to the JOA as well as
distribution of this warning to joint and multinational forces within the operational area.
The term "theater missile" applies to ballistic missiles, air-to-surface missiles, and air-,
land-, and sea-launched cruise missiles whose targets are within the joint force
commander’s operational area. (JP 3-0, 3-01.1, 3-01.5, 3-10.1, 3-12, 3-56.1) (JP 3-
01.1, 3-01.5, 3-10.1, 3-12.1, CJCSM 3500.05)

Effectiveness Measures Are Needed To Determine Mission Requirements

13
 Sample Operational Task and Associated Operational
Performance Measure (From UJTL)

 UJTL and UNTL provide a standardized list of

tasks with sample measures
 NTA 2.2.3.1.1 Provide Cueing.
 To provide cueing, early warning, or other initial data to assist
in detecting targets. (JP 2-0 Series, MCDP 2, MCWP 2-1,
NDP 2, NWP 2-01, NWP 3-01 Series, NWP 3 13, NWP 3-15
Series, NWP 3-15.20 Series, NWP 3-21 Series, NWP
3.51.1)

Operational Performance Can Be Decomposed Into System Performance

14
 METL Contains Performance Measures

Performance Measure: Is the Measure for the Task/Activity Satisfied?

15
Step 2. Information Analysis
Constraints
- Information Elements
described in standardized
terms

Inputs Information Outputs

- JCIDS documentation
- ROC/POE
Analysis - Networks required for
the mission
- Information elements
- JMETLs and NMETLs produced or consumed
- OPLANs, CONPLANs for by each operational
- DPS task
- Operational performance
- Outputs of Mission
metrics for network entry
Analysis and management
- Operational performance
metrics for information
16
element production and
consumption
 Step 2. Information Analysis

Information exchanges
and their performance
measures are needed
for each activity

*Figure from
the Universal
Naval Task
List Version
3.0

Information Requirements Can Be Produced In The Fleet’s Mission Analysis

17
Step 3. Systems Engineering
Constraints
- DOD EA
- Data and Service Strategies
- GTG and GESPs
- IA Requirements
- Supportability
Requirements

Inputs Systems Outputs

- Outputs from Mission
Analysis
Engineering - System requirements
• Technical
- Outputs from • IA
Information Analysis • Supportability
- Net-ready system
- Verification and
validation procedures
18
Step 4. Document
Constraints
- DoDAF
- Exposure Verification
tracking sheets
- GTG/GESP compliance
matrices

Inputs Outputs
- Outputs from Mission
Document - Operational requirements
Analysis - System requirements
- Outputs from - Traceability matrices
Information Analysis - Verification and
- Outputs from Systems validation procedures
Engineering

19
Documenting the SE Process
DoDAF Operational Views (OV)
OV-1, OV-4

Who are the

Bin the information each
players
player needs into 3
categories based on how
they use the data:
OV-2, OV-3
• View the data
What information • Publish the data
do they exchange • Process the data
(Operational IERs)
Categories determine the
OV-6c, OV-5 services, applications, and
hardware required at each
player
What they do with
the information

20
Documenting the SE Process
DoDAF System Views (SV)
SV-4, SV-5

What system
functions support
the mission thread Document the available
systems and characterize
them in terms of:
SV-1, SV-2
• Relation to mission
How are the • Connections
systems connected • Performance

Information can be used to

SV-6, SV-7 inform systems engineering
activities, build a system
spec, or to document the
How well do the
capabilities of an existing
systems perform
system

21