In this section you'll outline those performance attributes (KPPs, KSAs, or APAs) intended to satisfy the validated capability requirements and associated gaps.

- Avoid over-specification or inclusion of technical specifications as performance attributes.

- Ensure this section's narrative is consistent with the DoDAF CV-3, SV-7, and SV-8 generated during prior analysis, as modified for the scope and purpose of this IS-CDD.

- CV-3. Capability Phasing

- SV-7. Systems Measures Matrix

- SV-8. Systems Evolution Description

- Reminder: Like the other section of a IS-CDD, information in this section relies heavily on data provided by the PMO members of your IS-CDD Development Team.

Developing Performance Attributes - Other Job Aids: - RQM-2520, Developing Performance Attributes (DAU Online Training) - JCIDS Manual, Appendix G to Enclosure B - Provides definitions - Describes the six mandatory performance attributes - Force Protection (FP), mandatory KPP - System Survivability (SS), mandatory KPP - Sustainment, mandatory KPP - Energy, mandatory KPP - Interoperability Attribute - Physical Interoperability, Net-Ready Interoperability and Joint Training Interoperability (could be JPR, KPP or KSA) - Exportability Attribute, mandatory KSA - Provides guides for development of each mandatory performance attribute, and guidance for review and endorsement.

Correlate each performance attribute (KPP, KSA, or APA) to the operational attributes of the capability requirements defined in the ICD (your table in Section 3 did this).

- Identify the lowest-tier JCA possible for each attribute (KPP, KSA and APA tables discussed later).

- Ensure you capture as a KPP those parameters most critical to mission effectiveness.

- For multiple increments, identify which performance attributes apply to each increment along with their threshold & objective values. Could be specified in the annex for each increment.

- Articulate separate threshold and objective values for each affected performance attribute if degraded levels of performance are acceptable under certain mission conditions,

- If the IS-CDD describes an FoS solution, describe the performance attributes for the FoS level of performance as well as any unique performance attributes for each of the constituent systems.

- Identify all threat-sensitive performance attributes that are dependent upon intelligence resources or support. For those performance attributes that depend on Intelligence Mission Data (IMD) to perform as needed, ensure identification of IMD-dependent attributes and any schedule or cost considerations. (see Annex G to Appendix G of Encl B, JCIDS Manual)

Is My Program IMD Dependent?

- IMD is Intelligence and other data required to enable accurate characterization, identification, and response to the battlespace.

- Advanced weapons systems require significant amounts of intelligence data to be effective.

- A program is deemed IMD dependent if its sensor, platform, or information system relies on IMD for design, development, testing, training or operations of sensors, models, or algorithms for the purpose of combat identification; targeting; tracking; detecting and identifying activities, events, persons, materials, or equipment. Coordinate with your PM to:

- Evaluate the Key Performance Parameters, Key System Attributes, etc. for overall dependency

- Determine which processes or components may have IMD dependencies

- Determine what type of data may be required for the weapon system.

- Note: Life-cycle mission data plans (LMDPs) shall be established by the program office for each IMD-dependent acquisition program and effort beginning at Milestone A.

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

- Remember, your IS-CDD's performance attributes reflect system-level Measures of Performance (MOPs), NOT the mission-oriented Measures of Effectiveness (MOEs) operational attributes reflected in the ICD.

- Ensure all your performance attributes are SMART (Specific, Measurable, Achievable, Relevant & Testable...), unambiguous, and supported by documented trade-off analysis.

Important Definitions:

- Threshold: Provide threshold values for performance attributes 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).

- Objective: Provide objective values in cases where the increased performance level provides significant increases in operational utility.

- Note: Provide a range between your threshold and objective values to allow exploration of trade space during the TMRR and EMD acquisition phases. This also avoids having to revalidate your IS-CDD to pursue different levels of performance.

For each mandatory KPP, provide the related attributes that must be met.

- Under the SS KPP, address (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.

- Include tailored language in the IS-CDD for both Cyber Survivability and EMS Survivability, as applicable;

- Address the Cyber Survivability Pillars (Prevent, Mitigate, and Recover from and Adapt to Cyber Events), or in a table in Appendix E. Cyber Survivability Attributes (CSAs) (1 thru10), as applicable must be covered in Appendix E.. See the JCIDS Manual Systems Survivability Guide for details.

- 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 IS-CDD are in addition to Spectrum Requirements in Section 8 of a IS-CDD.

- For more information refer to the Cyberspace Survivability Endorsement Implementation Guide and EMS Survivability Guidebook, both posted to KM/DS.

- CBRN Survivability Considerations. 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 (see DoDI 3150.09).

- Net-Ready. Provide a Performance Attribute Table (Figure B-11, JCIDS Manual - illustrated later in this lesson) for the net-ready performance attribute, which depending upon the system can be a KPP, KSA, or APA. A net-ready attribute sources table is in Section 7, Joint Interoperability (Figure B-12, JCIDS Manual).

- Exportability KSA. 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. Other considerations include:

- Obtain the Milestone A ADM. How was this requirement addressed by the MDA?

- According to the JCIDS Manual, "Sponsors must establish performance attributes (KPPs, KSAs, and APAs) which 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."

- It is not clear how to write an Exportability KSA that meets the description in the JCIDS Manual, and DAU has not been able to obtain an example.

- Recommendation: Unless your organization has issued guidance on how to write an Exportability KSA, raise it thru your requirements chain of authority to your Service HQ - and to the Joint Staff if necessary, for guidance.

- Interoperability JPR/KPP/KSA. Physical Interoperability, Net Ready Interoperability, and Joint Training Technical Interoperability will be addressed in Section 7.

Joint Performance Requirements (JPRs)

- Public law (10 USC 181) requires the CJCS to establish and approve joint performance requirements that ensure interoperability and are deemed necessary by the CJCS to fulfill capability gaps.

- The term "joint performance requirement" means a performance requirement that is critical or essential to ensure interoperability or fulfill a capability gap of more than one armed force, Defense Agency, or other entity of the Department of Defense, or impacts the joint force in other ways such as logistics.

- The Joint Staff Gatekeeper, on behalf of the JROC, initially designates JPRs during the initial staffing phase in KM/DS. Final JPR designation will be made by the validation authority when the capability requirements document is validated.

- All performance attributes designated JPRs, if not already a KPP, will be upgraded to a KPP.

- JROC and JCB Interest documents will have at least one JPR. The JROC or JSB will validate the document but will delegate all non-JPR performance attributes for certification/endorsement and change authority to the Sponsor.

Final thoughts:

- Your team may determine one or more of the six mandatory performance attributes are not applicable to your IS-CDD's operational context. In each case, you must articulate the reason(s) why.

- Exclusion of a mandatory KPP or the net-ready summary table is subject to the approval authority of the certifying or endorsing organization as identified in Enclosure A of the JCIDS Manual. Early coordination with the appropriate certifying or endorsing organization for proposals to exclude a mandatory KPP or the net-ready summary table is essential to avoiding staffing delays.

- Certifying and Endorsement requirements and responsibilities are identified in the Submit to KM/DS step.