1. RQM 310 Developing Requirements KPPs and Performance Attributes

2. Lesson Objectives
Demonstrate the proper format of performance attributes and KPPs
Identify mandatory KPPs
Identify the characteristics of a well written KPP
Critique KPPs for clarity, achievability and resourcing
Evaluate examples of requirements creep
Explain the relationships of the KPPs and KSAs to Measures Effectiveness (MOEs), Measures of Performance (MOPs), and Measures of Suitability (MOSs)

3. KPP and KSA Development
Full Rate
Prod Decision
Review
Joint Concepts
Capabilities - Based Assessment
MS C
MS B
FCB
Strategic Guidance
Incremental Development
MS A
Technology
Development
Engineering & Manufacturing Development
Production & Deployment
AoA
Materiel
Solution
Analysis
Technology Opportunities & Resources
ICD
O&S
User Needs
MDD
CDD
CPD

4. DoD Definitions
User
Sponsor
Operating Command
Operator
Capability

5. JCIDS Definitions of Threshold vs Objective
Threshold — A minimum acceptable value considered achievable within the available cost, schedule, and technology at low-to-moderate risk. Performance below the threshold value is not operationally effective or suitable or may not provide an improvement over current capabilities.
Objective— is the desired operational goal achievable but at higher risk in cost, schedule and technology. Performance above the objective does not justify additional expense.
The difference between Threshold and Objective = “Trade Space”

6. Key Performance Parameter (KPP) Definition
Key Performance Parameters (KPP) – are performance attributes of a system considered critical or essential to the development of an effective military capability. They are measurable, testable and quantifiable. Failure of a system to meet a validated KPP threshold/initial minimum rescinds the validation, brings the military utility of the associated system into question and may result in a reevaluation of the program or modification to production increments
CJCSI 3170

7. Key System Attribute (KSA) Definition
Key System Attribute (KSA) – attributes or characteristics considered essential to achieving a balanced solution / approach to a system, but not critical enough to be designated a KPP. KSAs must be measurable, testable and quantifiable.
CJCSI 3170

8. Types of KPPs Each requirement should be: Customer/Operational
Functional
Performance
Design
Derived
Allocated
Each requirement should be:
Achievable
Measurable/Testable/Quantifiable
Unambiguous
Complete
Necessary
Prioritized

9. KPP Development Guidelines for Writing Quality KPPs
Questions to ask before a performance attribute is selected as a KPP
If an item does not meet the KPP definition, consider it for inclusion as a Key System Attribute (those issues that do not rise to the level of a Key Performance Parameter)
Key Performance Parameter (KPP) Steps

10. Mandatory Key Performance Parameters (KPPs) and Key System Attributes (KSAs)
Force Protection KPP (all manned systems)
Survivability KPP (all manned; may be applicable to unmanned )
Sustainment KPP (all ACAT I* )
Materiel Availability
Operational Availability
Supporting KSAs
Materiel Reliability
Operation & Support Costs
Net Ready KPP (all IS & NSS)
Training KPP (all ACAT I)
Energy KPP (all where provisions of energy impact operational reach, or protection of energy infrastructure or energy resources is required)
No change
All O&S costs now included
Major changes
No longer termed “selectively applied”. Detailed instructions added to Manual.
*ACAT II and below programs, must include the Sustainment KPP or Sponsor defined sustainment metrics.

11. Net-Ready KPP Elements Net-Ready KPP Attributes
Net-Ready KPP Changes
2012
Net-Ready KPP Elements
CJCSI E, 15 Dec 2008*
Net-Ready KPP Attributes
JCIDS Manual, 19 Jan 2012)
Compliant Solution Architecture
Compliance with Net-Centric Data & Services Strategies
Compliance with Applicable Global Information Grid (GIG) Technical Guidance (GTG)
Compliance with DOD Information Assurance (IA) Requirements
Compliance with Supportability Requirements to Include Spectrum Utilization & Information Bandwidth Requirements, Selective Availability Anti-Spoofing Module (SAASM) & the Joint Tactical Radio System (JTRS), as Applicable
Supports Military Operations
Is Entered and Managed on the Network, and
Effectively Exchanges Information
Three-Step Development Process
Step 1. Mission Analysis – Determines Attribute Details for Supports Military Operations
Step 2. Information Analysis – Determines Attribute Details for Entered & Managed on the Network, and Effectively Exchanges Information
Step 3. Systems Engineering & Architecture – Supports all 3 attributes
New CJCSI F, Interoperability, pending signature – will reflect these changes

12. Required Architecture Data To Support the Net-Ready KPP
CJCSI E, Dec 2008
DoDAF 1.5, 2007
JCIDS Manual, Jan 2012
DoDAF 2.02, 2010
ICD
CDD
CPD
ICD
CDD
CPD
OV-1
AV-1
AV-2
OV-1
OV-2
OV-3
OV-4
OV-5
OV-6c
SV-2
SV-4
SV-5
SV-6
TV-1
TV-2
AV-1
AV-2
OV-1
OV-2
OV-3
OV-4
OV-5
OV-6c
OV-7
SV-2
SV-4
SV-5
SV-6
SV-11
TV-1
TV-2
AV-1
AV-2
CV-2
CV-6
OV-1
OV-2
OV-4
OV-5a
AV-1
AV-2
CV-1
CV-2
CV-3
CV-4
CV-5
CV-6
DIV-2
OV-1
OV-2
OV-3
OV-4
OV-5a
OV-5b
OV-6c
PV-2
SV-1 or SvcV-1
SV-2 or SvcV-2
SV-4 or SvcV-4
SV-5a or SvcV-5
SV-6 or SvcV-6
SV-7 or SvcV-7
StdV-1 (TV-1)
StdV-2 (TV-2)
AV-1
AV-2
CV-1
CV-2
CV-3
CV-4
CV-5
CV-6
DIV-2
DIV-3
OV-1
OV-2
OV-3
OV-4
OV-5a
OV-5b
OV-6c
PV-2
SV-1 or SvcV-1
SV-2 or SvcV-2
SV-4 or SvcV-4
SV-5a or SvcV-5
SV-6 or SvcV-6
SV-7 or SvcV-7
StdV-1 (TV-1)
StdV-2 (TV-2)

13. Training KPP Applies to All ACAT I Programs
Attributes Include (among others): Proficiency Level; Time to Train; Training Retention and Associated Metrics
Intent is to Ensure that Training Requirements are Properly Addressed from the Beginning of the Acquisition Process and Throughout the Program’s Acquisition Life- Cycle.
J-7, in Coordination with USD(Personnel &Readiness), Assesses the Training KPP, or Sponsor Justification of Why the Training KPP is Not Applicable, for JROC or JCB Interest Programs

14. Energy KPP
Applies to Systems Where the Provision of Energy, Including Fuel and Electric Power, Impacts Operational Reach, or Requires Protection of Energy Infrastructure or Energy Resources in the Logistics Supply Chain
May be Expressed as Units of Energy Used per Period of Time (e.g. gallons per hour), or as Number of Refuelings Required (e.g. tankings per hour).
Logistics FCB, in Coordination With Joint Staff J-4 / Engineering Division (J-4/ED) and With Advice From the Defense Energy Board as Appropriate, Assesses the Energy KPP, or Sponsor Justification of Why the Energy KPP is Not Applicable, for JROC or JCB Interest Programs

15. Examples of KPPs Satellite System
The mission is to collect and disseminate other critical air, land, sea, and space environment data to support a broad range of national security users.
Sensing depth
Sea Surface Wind Speed

16. Examples of Operational KPPs
The root mission need of the Medium Armored Vehicle (MAV) was to provide a family of vehicles (FOV) that were air transportable anywhere in the world and support infantry operations.
Source: Equipment Sustainment Requirements for the Transforming Army, RAND, 2009

17. Examples of KPPs Four KPPs resulted from this definition:
Interoperability
Transportability
Carry an Infantry Squad
Destroy a standard infantry bunker
Source: Equipment Sustainment Requirements for the Transforming Army, RAND, 2009

18. Examples of Operational KPPs
The Coastal Ship KPPs for the Seaframe are
Sprint Speed
Endurance Range
Mission Package Payload
Draft
Core Ship Crew Size
What is the source of the values for the KPPs?

19. Affordability
Trade Space
Programs are only funded to KPP Thresholds
Analytical rigor

20. Requirements Creep
Requirements creep refers to significant additions or modifications to the requirements of a new system throughout the lifecycle, resulting in extensions to and alteration of the system’s functionality and scope

21. Examples of Requirements Creep FUTURE COMBAT SYSTEM (FCS)
FCS program requirements changed over the months and years, mainly from lessons learned in combat. While valid perhaps, these changes moved requirements from their initial, approved version.
From a clinical viewpoint, this may be perceived as 'requirements creep', or it could be 'necessary changes to requirements given new TTPs of enemy forces to reflect emerging realities’

22. Requirements Creep
The nature of the acquisition process - over years - will result in changes to the program
Some are new requirements being levied on a program
Some are derived or discovered during testing and development
Some or all of this can be considered 'requirements creep‘
Route the change requests to the appropriate authority for approval.
Requirements Managers must eliminate or deter requirements creep to the maximum extent possible
NOTE: Only the operational validation authority can approve changes to KPPs/KSAs

23. Remedies to Requirements Creep
Regular dialogue between the RM and PM!
Well-Written Original Requirements
Process Discipline
Configuration Steering Boards (CSB)

24. Configuration Steering Boards (CSBs)
CSBs meet at least annually
Reviews all requirements changes and significant technical configuration changes
Changes generally rejected, deferred to future blocks or increments
If approved, changes require identified funding and mitigated schedule impacts
The Program Manager (PM) (with the Program Executive Officer) identifies descoping options to reduce program cost or moderate requirements
The CSB recommends which options should be implemented
Final decisions coordinated with the Joint Staff and military department requirements officials
The Acquisition Executive of each DoD Component shall establish and chair a CSB with broad executive membership . . .
DoDI per Section 814, FY ’09 National Defense Authorization Act 24

25. Measures of Effectiveness and KPPs
Measure of Effectiveness (MOE)
Measure designed to correspond to accomplishment of mission objectives and achievement of desired results. MOEs can be assessed using two subsets; Measures of Performance (MOP) and Measures of Suitability (MOS)
In other words, “What do we want the system to be able to do?”
KPP
MOS
MOE
MOP
KSA

26. Measures of Effectiveness and KPPs - JSF Example
Measures of Performance (MOP)
Combat Radius - 3 Profiles by Service: USMC 450nm; USAF 590nm; USN 600nm
Radio Frequency Signature - (Stealth)
Interoperability – Meet 100% of critical Information exchange requirements: Secure Voice and Data
MOPs are found in KPPs
What operational capability does this system provide?
Mission related KPPs

27. Measures of Effectiveness and KPPs - JSF Example
Measures of Suitability (MOS)
Mission reliability - 95% USMC/USN; 93% USAF
Logistics footprint - <8 equivalent C-17 Loads (20 PAA USMC; 24 PAA USAF) ; <46,000 cu ft, 243ST USN
Sortie generation - 4 Surge/3 Sust USMC; 3/2 USAF and USN
MOSs are found in the KPPs
How reliable is the system?
Sustainment related KPPs

28. Lesson Review
The Requirements Managers represent the warfighters’ interests in the Acquisition process.
The RMs’ major purpose in the JCIDS and Acquisition process is to prevent unnecessary requirement changes (creep) and minimize negative influences (delays, cost increases) on their program.
Failure will result in delay and increased costs and may result in overall failure to complete the acquisition successfully…thereby failing the warfighter.

29. Lesson Review
Requirements Managers and Acquisition Professionals must both remain aware of the requirements to gain approval for every change to any KPP.
They both have a duty to inform the other, as well as their leadership, of changes (required or proposed) and establish a timeline to gain approval for these changes (may include a requirement to send an impact statement to decision making bodies in the chain of command).

30. Backups

31. Key Performance Parameter
Net-Ready KPP Example
Attribute 1. Support to Military Operations
NR-KPP Attribute
Key Performance Parameter
Threshold
Objective
Support to military operations
Mission: Tracking and locating (Finding, Fixing, Finishing) High-Value Target (HVT)
Measure: Timely, actionable dissemination of acquisition data for HVT
Conditions: Targeting quality data to the neutralizing/ tracking entity
10 minutes
Area denial of HVT activities
Near-real-time
HVT tracked, neutralized
Mission Activities: Find HVT
Measure: Location accuracy
Conditions: Individual differentiation
100 meter circle
Identify armed/ not armed
25 meter circle
Identify individual

32. Key Performance Parameter
Net-Ready KPP Example
Attribute 2. Enter and Be Managed in the Network
NR-KPP Attribute
Key Performance Parameter
Threshold
Objective
Enter and be managed in the network
Network: SIPRNET
Measure: Time to connect to an operational network from power up
Conditions: Network connectivity
2 minutes
99.8
1 minute
99.9
Network: NIPRNET
99.8
99.9

33. Key Performance Parameter
Net-Ready KPP Example
Attribute 3. Exchange Information
NR-KPP Attribute
Key Performance Parameter
Threshold
Objective
Exchange information
Information Element: Target Data
Measure: Dissemination of HVT biographic and physical data
Measure: Receipt of HVT data
Measure: Latency of data
Measure: Strength of encryption
Conditions: Tactical/Geopolitical
10 seconds
Line of Sight (LOS)
5 seconds
NSA certified type 1
Permissive environment
Beyond LOS
2 seconds
Non-permissive environment

34. Required Architecture Data To Support the Net-Ready KPP
All Viewpoint (AV):
AV-1, Overview & Summary
AV-2, Dictionary of Terms
Capability Viewpoint (CV)
CV-1, Vision
CV-2, Capability Taxonomy
CV-3, Capability Phasing
CV-4, Capability Dependencies
CV-5, Capability to Organizational Development Mapping
CV-6, Capability to Operational Activities Mapping
Data & Information Viewpoint (DIV)
DIV-1, Conceptual Data Model
DIV-2, Logical Data Model
DIV-3, Physical Data Model
ICD
CDD
CPD
AV-1 X X X
AV-2 X X X
CV-1 R X X
CV-2 X X X
CV-3 R X X
CV-4 R X X
CV-5 X X
CV-6 X X X
DIV-2 X X
DIV-3 X
R = Recommended
Blue = New
Program Responsibility
JCIDS Sponsor Responsibility
Joint Program/Sponsor Responsibility

35. Required Architecture Data To Support the Net-Ready KPP
Operational Viewpoint (OV):
OV-1, High-level Operational Concept Graphic
OV-2, Operational Resource Flow Description
OV-3, Operational Resource Flow Matrix
OV-4, Organizational Relationships Chart
OV-5a, Operational Activity Decomposition Tree
OV-5b, Operational Activity Model
OV-6a, Operational Rules Model
OV-6c, Event-Trace Description
Project Viewpoint (PV)
PV-2, Project Timelines
ICD
CDD
CPD
OV-1 X X X
OV-2 X X X
OV-3 X X
OV-4 X X X
OV-5a X X
OV-5b O X X
OV-6a X X
OV-6c X X X
PV-2 X
O = Optional
Blue = New
Program Responsibility
JCIDS Sponsor Responsibility

36. Required Architecture Data To Support the Net-Ready KPP
Systems Viewpoint (SV):
SV-1, Systems Interface Description
SV-2, Systems Resource Flow Description
SV-3, Systems-Systems Matrix
SV-4, Systems Functionally Description
SV-5a, Operational Activity to Systems Function Traceability Matrix
SV-6, Systems Resource Flow Matrix
SV-7, Systems Measures Matrix
Services Viewpoint (SvcV)
SvcV-1, Services Context Description
SvcV-2, Services Resources Flow Description
SvcV-4, Services Functionality Description
SvcV-5, Operational Activity to Services Traceability Matrix
SvcV-6, Services Resource Flow Matrix
SvcV-7, Services Measures Matrix
Standards Viewpoint (StdV)
StdV-1, Standards Profile
StdV-2, Standards Forecast
ICD
CDD
CPD
SV-1 or SvcV-1 X X X
SV-2 or SvcV-2 X X X
SV-4 or SvcV-4 X X
SV-5a or SvcV-5 X X X
SV-6 or SvcV-6 X X X
SV-7 or SvcV-7 R X X
StdV-1 (TV-1) X X
StdV-2 (TV-1) X X
R = Recommended
Blue = New
Program Responsibility
Joint Program/Sponsor Responsibility
JCIDS Sponsor Responsibility