2.5.5. Section 5: Performance Attributes. (KPPs, KSAs, or APAs)

2.5.5.1. The purpose of this section is to outline the performance attributes intended to satisfy the validated requirements and associated capability gaps.

2.5.5.1.1. Sponsors should avoid over specification or inclusion of technical specifications as performance attributes.

2.5.5.1.2. The narrative in this section is to be consistent with DoDAF CV-3, SV-7, and SV-8 generated during prior analysis, as modified for the scope and purpose of the CDD.

2.5.5.2. Correlate each performance attribute (KPP, KSA, or APA) to the operational attributes of the CRs defined in the ICD. The Sponsor should identify the lowest tier JCA possible for each attribute.

2.5.5.2.1. Ensure the parameters most critical to mission effectiveness are captured as KPPs.

2.5.5.2.2. If the CDD is describing multiple increments, clearly identify which performance attributes (KPPs, KSAs, or APAs) apply to each increment, and the development threshold/objective values for each. These may also be

specified in the annex for each increment.

2.5.5.2.3. If degraded levels of performance are acceptable under certain mission environments or conditions, articulate separate threshold and objective values for the affected performance attributes.

2.5.5.2.4. If the CDD is describing an FoS solution, it must describe the performance attributes for the FoS level of performance as well as any unique performance attributes for each of the constituent systems.

2.5.5.2.5. Identify all performance attributes that are threat-sensitive and dependent upon intelligence resources or support. For performance attributes (KPPs, KSAs, and/or APAs) which are dependent upon IMD to perform as specified, ensure identification of IMD dependent attributes and any schedule or cost considerations for IMD. Reference Annex G to Appendix G of this enclosure for detailed information on what is required to address intelligence supportability.

2.5.5.3. Present each performance attribute (KPP, KSA, or APA) in terms of parameters needed to address the validated requirements consistent with the DoDAF CV-3.

2.5.5.3.1. The performance attributes reflect Measures of Performance (MOPs) for the system being developed and not Measures of Effectiveness (MOEs) in conducting the mission. Ensure parameters chosen are technically achievable, quantifiable, measurable, testable, unambiguous, supported by documented trade-off analysis, and defined in a manner that supports efficient and effective T&E.

2.5.5.3.2. Provide threshold values for each performance attribute that represent the value below which performance would require reevaluation of military utility in the applicable CONOPS and/or Operational Mode Summary/Mission Profile (OMS/MP). Provide objective values in cases where the increased performance level of a parameter provides significant increases in operational utility.

2.5.5.3.3. Provide a range between threshold and objective values to allow trade space to explore during the TMRR and EMD phase of acquisition without having to revalidate the CDD to pursue different levels of performance. The PM may use this information to provide incentives for the development contractor or to weigh capability tradeoffs between threshold and objective values. Trade space should be sufficient to allow for increased capability in the future due to evolving technology, threat, or interoperability needs.

2.5.5.4. Address the mandatory attributes Energy KPP, SS KPP, Force Protection KPP, and Sustainment KPP, Interoperability JPR/KPP/KSA and Exportability KSA and provide all applicable Tables.

2.5.5.5. The Interoperability performance attribute (JPR, KPP, KSA) is required to be addressed by the Sponsor in Section 5 Tables as depicted in Figures B-8 through B-10 along with attributes for Net-Ready, Physical Interoperability, and Joint Training Technical Interoperability (JTTI) (KPP, KSA, APA) if applicable.

2.5.5.5.1. For Net-Ready, include the Performance Attribute Table that presents the Net-Ready performance attributes and their associated metrics in terms of a standardized framework and data sources to leverage when developing attributes and their threshold and objective values. The Net-Ready Attribute Table includes: Support of Military Operations, Entered and be Managed on the Network, and Exchange Information as depicted in Figure B- 11.

2.5.5.5.2. Section 7 of a CDD will describe all aspects of the Interoperability performance attribute in more detail consisting of Physical Interoperability, Net-Ready Interoperability, and Joint Training Technical Interoperability.

2.5.5.5.3. The Net-Ready Attribute Source Table will be captured in Section 7 of the CDD. The Net-Ready performance attribute will be captured in Section 5 (KPP, KSA, APA) as part of Interoperability Attribute.

2.5.5.5.4. For each mandatory KPP, provide attributes related to it that must be met rather than a generic statement that the certifications and/or endorsements will be obtained.

2.5.5.5.5. For more information, see Annex A of Appendix G to this enclosure.

2.5.5.6. Under the SS KPP, address:

2.5.5.6.1.1. (1) Kinetic Survivability; (2) Cyber Survivability; (3) EMS Survivability; (4) CBRN Survivability, and (5) Environmental Survivability. For each category deemed not applicable, provide rationale as to why that portion of the KPP does not apply.

2.5.5.6.1.1.1. Include tailored language for the CDD for both Cyber Survivability and EMS Survivability, as applicable;

2.5.5.6.1.1.2. Provide an associated narrative addressing the Cyber Survivability Pillars (Prevent, Mitigate, and Recover from and Adapt to Cyber Events) or, as needed, in a Table in Appendix E. Applicable Cyber Survivability Attributes (CSAs) (1-10), as applicable associated with the mandatory SS KPP will be included in Appendix E CSA example table (Figure B-14).

2.5.5.6.1.1.3. Address the EMS Survivability Pillars (Prevent, Mitigate, Recover and Adapt to operating in congested and contested EMS environments) and the applicable EMS Survivability Attributes, Spectrum Protection, System Adaptability, Spectrum Access Flexibility, Spectrum Efficiency, and Multi- Functionality. Note: EMS Survivability KPP requirements in Section 5 of a CDD are in addition to Spectrum Requirements in Section 8 of a CDD.

2.5.5.6.1.1.4. Reference the Cyber Survivability Endorsement Implementation Guide and EMS Survivability Guidebook, via KM/DS (Reference [4]), for more information.

2.5.5.6.1.1.5. CBRN Survivability Considerations. The sponsor shall clearly state whether the system will be required to operate in CBRN (including EMP) environments and ensure required CBRN operations are addressed in any follow-on AoA(s). CDDs require a "Mission Critical" determination; systems vital to essential defense missions that are required to survive and operate in CBRN environments will be designated "CBRN Mission Critical" per Reference DoDI 3150.09, Reference [77]. The sponsor must include rationale justifying why the system is not required to operate in CBRN environments when CBRN is a system threat. When designated CBRN Mission Critical, the system must consider all relevant CBRN environments (as indicated in the threat section), as well as operational and maintenance requirements relating to ensuring hardness against those CBRN environments.

2.5.5.6.2. Sponsors shall address Exportability "Allied/Partner Interoperability and Coalition Use" as per the Conventional Arms Transfer Policy in this Section. Standard Exportability language shall be addressed as a mandatory KSA.

2.5.5.6.3. Neither the mandatory KPPs nor the Interoperability performance attribute are applicable to every requirement. If the Sponsor determines that a mandatory KPP, the Interoperability Attribute or Net-Ready performance attribute is not applicable to their operational context, the Sponsor must articulate the reason(s) why.

2.5.5.6.4. Exclusion of a mandatory KPP or the Net-Ready Attribute Table (Figure B-11 is subject to the approval authority of the certifying or endorsing organization as identified in Enclosure A of this manual. Early coordination with the appropriate certifying or endorsing organization for proposals to exclude a mandatory KPP or the Net-Ready Attribute Table is essential to avoiding staffing delays.

2.5.5.7. Provide tables summarizing performance attributes in threshold and objective format, as illustrated in Figure B-8 through Figure B-10 with example attribute content. If detail associated with each performance attributes (KPP, KSA, and APA) cannot be adequately captured within the tables, additional detail may be provided in separate numbered subparagraphs.

2.5.5.7.1. Check the box for any KPPs recommended to be JPRs. The Joint Staff Gatekeeper will review all Sponsor recommended JPRs along with all other KPPs, KSAs, and APAs and will approve the designation of JPRs. This JS Gatekeeper's JPR designation will be strongly influenced by the recommendation given by the Sponsor, the Lead FCB, and other advisors such as the certification and endorsement organizations. The JROC approves final JPR designations provided by the Joint Staff Gatekeeper.