2.5.1.5. Section 5: Performance Attributes (KPPs, KSAs, and APAs). Follows the same format as a regular CDD with the exception of the following:

2.5.1.5.1. Performance attributes may be quantified in terms of initial minimum values rather than threshold/objective values. As with regular CDDs, the performance attributes must reflect performance that satisfies the CRs identified in Section 3 of the IS-CDD. Reference Figure B-13 of this manual as an example of how to capture the Net-Ready performance attributes for an IS-CDD.

2.5.1.5.2. Mandatory KPPs/Attributes. The mandatory KPP/Attributes apply to an IS-CDD. The SS KPP and Sustainment KPP are required for the IS-CDD. The Interoperability Attribute, Joint or otherwise will also be addressed along with Exportability.

2.5.1.5.2.1. SS KPP. For an IS-CDD, the SS should focus on the ability of the system to operate in a cyberspace and EMS-contested environment as per Annex C to Appendix G of this Enclosure. The following shall be included under the SS KPP:

2.5.1.5.2.1.1. Identify the CSRC, EMS Survivability Risk Category, and how they were determined (for Cyberspace, specify if it was determined using the CSEIG-recommended approach);

2.5.1.5.2.1.2. Include tailored language for the CDD (tailored for an IS-CDD);

2.5.1.5.2.1.3. Address the Cyber Survivability Pillars (Prevent, Mitigate, Recover and Adapt to Cyber Events) and the associated Cyber Survivability Attributes (CSAs) (1-10), as applicable. This information can be provided in a table or as needed, in the associated narrative. For more information, see the CSE Implementation Guide under JROC Admin Guide tab, via KM/DS additional guidance.

2.5.1.5.2.1.4. For EMS Survivability, see Annex C to Appendix G of this Enclosure and the EMS Survivability Guidebook, via KM/DS (Reference [5]).

2.5.1.5.2.2. Sustainment KPP. For an IS-CDD the Sponsor should focus the Sustainment KPP on the operational availability of the IS solution as per Annex D to Appendix G of this Enclosure.

For reference or comparison, below is what the JCIDS Manual says for the DCR 2025 itself:

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 IS-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 IS-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 IS-CDD is describing a FoS solution as the base IS-CDD, it must describe the overall performance attributes for the FoS level of performance. Any unique performance attributes for each of the constituent systems will be documented in separate IS-CDD Annexes.

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 IS-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. The use of MOSA should allow sufficient trade space for increased capability in the future due to evolving technology, threat, or interoperability needs.

2.5.5.4. The Sponsor shall 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. Refer to Annex G of this Enclosure for guidance when writing mandatory attributes (as applicable). If "not applicable", the Sponsor must state why.

2.5.5.4.1. For the Interoperability performance attribute (JPR/KPP/KSA), it is required to be addressed in the Section 5 Table, as depicted in Figure B-6 along with the attributes for Net-Ready, Physical Interoperability, and Joint Training Technical Interoperability (JTTI), if applicable.

2.5.5.4.1.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-7.

2.5.5.4.1.2. Section 7 of a IS-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. As noted in the Interoperability Guide, MOSA should also be address in this Section to enhance interoperability overall.

2.5.5.4.1.3. The Net-Ready performance attribute will be captured in Section 5 (KPP, KSA, APA) as part of Interoperability Attribute.

2.5.5.4.2. For more information, see Annex A of Appendix G to this Enclosure.

2.5.5.5. For each mandatory KPP, provide attributes related to it that must be met.

2.5.5.6. Under the SS KPP, the sponsor shall include tailored language to address:

2.5.5.6.1. (1) Kinetic Survivability; (2) Cyber Survivability; (3) EMS Survivability; (4) CBRN Survivability, (5) Environmental Survivability, and (6) Space Concerns. 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. The sponsor shall address concerns for Kinetic Survivability, including Space Concerns and Environmental Concerns for design to the environmental/climatic conditions an equipment item is likely to encounter during its service life.

2.5.5.6.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. In accordance with the Cyber Survivability Endorsement Implementation Guide, Cyber Survivability Attributes (CSA) associated with the mandatory SS KPP shall be included in Appendix E: CSA Table (Figure B-10).

2.5.5.6.1.3. Identify the EMS Survivability Risk Category and how it was determined. Address the EMS Survivability Pillars (Prevent, Mitigate, Recover and Adapt to operating in congested and contested EMS environments) and the applicable EMS Survivability Attributes, Electronic Protection, Electromagnetic Mitigation, EMS Restoration, and EMS Evolution (KPP/KSA/APA). Provide threshold and objective KPP values for the associated EMS Survivability JCA in the KPP table. EMS Survivability information can be provided in an (optional) Appendix F to the IS-CDD. EMS dependent capabilities expected to operate in near-peer, high risk environments will be designated as JCB Interest to address interoperability and survivability requirements. Note: EMS Survivability KPP requirements in Section 5 of a IS-CDD are in addition to Spectrum Requirements in Section 8 of a IS-CDD.

2.5.5.6.1.4. The submitter should bring these concepts together into the Section 5, Performance Attributes of a IS-CDD. The EMS System Survivability attributes shall be addressed. The four EMS attributes are Electromagnetic Protection, Electromagnetic Mitigation, EMS Restoration, and EMS Evolution. See the EMS Survivability Guidebook, via KM/DS, Reference [5] for more information pertaining to EMS Survivability, threat methodology, EMS Survivability Risk Category, Example Language, and EMS Survivability Attributes. Although all EMS attributes are currently under the System Survivability mandatory KPP, the sponsor shall consider EMS interoperability. Note: EMS attribute requirements are in Section 5 of a IS-CDD and additional Spectrum and EMC Requirements are in Section 8 of a IS-CDD. Examples of IS-CDD Section 5 EMS Requirements Statements are in Table 5 of the EMS Survivability Guide.

2.5.5.6.1.5. Reference the Cyber Survivability Endorsement Implementation Guide and EMS Survivability Guidebook, via KM/DS under JROC Admin Guide tab under JROC Admin Guide tab, Reference [5], for more information.

2.5.5.6.2. 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). IS-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 [37]. 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.7. Exportability "Allied/Partner Interoperability and Coalition Use". As per the Conventional Arms Transfer Policy, the Exportability KSA is required to be addressed by the Sponsor in Section 5 Tables as depicted in Figure B-6. Exportability is comprised of two components: Differential Capability (scalability), and Anti-Tamper (safeguards). Refer to Annex I to Appendix G of this Enclosure for guidance when writing this mandatory attribute.

2.5.5.8. Neither the mandatory KPPs nor the Interoperability performance attribute are applicable to every IS-CDD. 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.8.1. Exclusion of a mandatory KPP or the Net-Ready Attribute Table (Figure B-7) 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. commended 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.

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

2.5.5.9.1. "X" 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.

2.5.5.10. Attribute Table. The Attribute tables were reduced to one table to group similar attributes together. To reduce the risk of exceeding maximum document page length, it is highly recommended that the attribute table be inserted as Landscape form to save document page space. If a mandatory attribute is not applicable, the Sponsor must provide rationale as to the reason why. NOTE: Table B-6 Attribute Table depicted is an example of Mandatory and other potential attribute grouped by association to each other. Numbering hierarchy is by grouping of either all KPPs, KSAs or APAs.

2.5.5.11. Rationale. Rationale in the document is not necessary to justify the attribute. The attribute table is the primary go to source for all attributes. Attribute paragraph text is not necessary. If for some reason, a Rationale is required to further explain in detail the attribute, it will follow the Attribute Table.