Upload
incosewma
View
119
Download
3
Tags:
Embed Size (px)
Citation preview
Implementing the Net-Ready Key
Performance Parameter
INCOSE
Washington Metro Area
11 May 2010
presented byLesley Painchaud
2
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
3
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
4
Decomposition of the Compliance Statement
Net-Ready Description
Potential Net-Ready Compliance Measures
Potential Net-Ready Effectiveness and Operational Performance Measures
An Interoperable System Must Address All 3 Components
Program offices typically focus here. Simply completing these elements DOES NOT ensure the KPP will be met.
5
Overview of the Refined Compliance Statement
Current NR-KPPCompliance Statement
Refined NR-KPP Compliance Statement
Refinement Explicitly Highlights Effectiveness and Performance Measures
Clarification of Measures
Clarification of Measures
Clarification of Measures
6
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
2. Information Analysis information requirements Information exchanges and associated operational performance
measures
3. 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
4. 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 CompletelySpecify A System’s Operational Requirements
7
Drawing Out Effectiveness, Performance, and Compliance Measures
SystemsEngineering
ComplianceMeasures*
Performance Measures**- Operational Performance Measures for network entry and management- Operational Performance Measures for information element production and consumption
MissionAnalysis
Support Net CentricMilitary Operations*
Support OperationalActivities*
InformationAnalysis
Enter and Be ManagedIn the Network*
Exchange Information*
Support InformationExchanges*
Documentation* Elements from current NR-KPP Compliance Statement** Elements from refined NR-KPP Compliance Statement in ASN (RDA) CHSENG’s NR-KPP Guidebook
Inputs
Inputs
Out
com
es
Inputs
Inputs
Out
com
es
Con
stra
ints
Outcomes
Step 1
Step 2
Step 3
Step 4
Effectiveness and Performance Measures**- Effectiveness Measures for each mission- Operational Performance Measures for each task
NR-KPP Description**- Missions supported by the system- Operational tasks for the mission
NR-KPP Description**- Networks required for the mission- Information elements produced for or consumed by each operational task
AV-1OV-1OV-4OV-5
OV-6c
OV-2OV-3OV-7
SV-1SV-2
SV-4aSV-5a
SV-6/10cSV-7
SV-11
8
Refined Compliance Statement
Net-Ready Description
Net-Ready Compliance Measures
Net-Ready Effectiveness and Operational Performance Measures
9
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
10
Questions?
11
MissionAnalysis- JCIDS documentation
- ROC/POE- JMETLs and NMETLs- OPLANs, CONPLANs- DPS
Inputs- Missions supported by
the system- Mission effectiveness
measures- Operational tasks for the
mission- Operational performance
measures for each task
Outputs
- Missions and operationaltasks described in termsthe Fleet uses
- Measurable and testablemetrics
ConstraintsStep 1. Mission Analysis
12
Step 1. Mission Analysis
*Slide from NMETL Program Executive Training, by David Brown, USFF N721B
Operational Performance measures are needed for each mission thread activity
Effectiveness measures are needed for each mission thread
Systems Engineering Requires Performance And Effectiveness Measures
13
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
14
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
15
METL Contains Performance Measures
Performance Measure: Is the Measure for the Task/Activity Satisfied?
16
InformationAnalysis- JCIDS documentation
- ROC/POE- JMETLs and NMETLs- OPLANs, CONPLANs- DPS- Outputs of Mission
Analysis
Inputs- Networks required for
the mission- Information elements
produced or consumedfor by each operationaltask
- Operational performancemetrics for network entryand management
- Operational performancemetrics for informationelement production andconsumption
Outputs
- Information Elementsdescribed in standardizedterms
ConstraintsStep 2. Information Analysis
17
Step 2. Information Analysis
Information Requirements Can Be Produced In The Fleet’s Mission Analysis
*Figure from the Universal Naval Task List Version 3.0
Information exchanges and their performance measures are needed for each activity
18
SystemsEngineering- Outputs from Mission
Analysis- Outputs from
Information Analysis
Inputs- System requirements
• Technical• IA• Supportability
- Net-ready system- Verification and
validation procedures
Outputs
- DOD EA- Data and Service Strategies- GTG and GESPs- IA Requirements- SupportabilityRequirements
ConstraintsStep 3. Systems Engineering
19
Document- Outputs from Mission
Analysis- Outputs from
Information Analysis- Outputs from Systems
Engineering
Inputs- Operational requirements- System requirements- Traceability matrices- Verification and
validation procedures
Outputs
- DoDAF- Exposure Verificationtracking sheets
- GTG/GESP compliancematrices
ConstraintsStep 4. Document
20
Documenting the SE Process DoDAF Operational Views (OV)
OV-1, OV-4
OV-2, OV-3
OV-6c, OV-5
Who are theplayers
What informationdo they exchange(Operational IERs)
What they do withthe information
Bin the information eachplayer needs into 3categories based on how they use the data:
• View the data• Publish the data• Process the data
Categories determine theservices, applications, and hardware required at eachplayer
21
Documenting the SE ProcessDoDAF System Views (SV)
SV-4, SV-5
SV-1, SV-2
SV-6, SV-7
What systemfunctions supportthe mission thread
How are thesystems connected
How well do thesystems perform
Document the available systems and characterizethem in terms of:
• Relation to mission • Connections• Performance
Information can be used toinform systems engineeringactivities, build a systemspec, or to document thecapabilities of an existingsystem