2018 Joint Capabilities Integration Development System JCIDS Changes

2018 Joint Capabilities Integration & Development System (JCIDS) Changes Rapid Deployment Training (RDT) Sources: • CJCSI 5123. 01 H, 31 August 2018 • JCIDS Manual, 31 August 2018 Eric Jefferies, DAU, DSMC, Professor of Requirements Management Center eric. jefferies@dau. mil (703) 805 -2381 11 October 2018 JCIDS Changes RDT

Senior Leader Guidance/Intent (Changes 1 of 2) • JCIDS Policy Changes: – Delegate authorities where appropriate to support a more streamlined and responsive system • Reduces number of Joint Staffing Designations from four to three: JROC Interest, JCB Interest, and Joint Information (deletes Joint Integration) • Delegates validation/certification/endorsement authority to the Sponsor unless there is clear joint interoperability or multi-service equities – Defines Joint Performance Requirements (JPRs) to include: • How the Joint Staff Gatekeeper will designate JPRs • How JPRs will be staffed for certifications/endorsements – Adds guidance to address joint interoperability • CDD Section added for joint interoperability that will include guidance on Modular Open System Approach 2

Senior Leader Guidance/Intent (Changes 2 of 2) • Minimizes touch points between Sponsor and the JROC – Reduces the number of capability requirements documents – CPD no longer required (Sponsors can update a validated CDD) • Addresses incremental/evolutionary acquisition – Evolving threat informed by military risk & maturity of technologies – Incremental or family of systems approach • Addresses intelligence supportability and system survivability requirements early in the process • Adds guidance on JROC support to the Secretary of Defense’s Investment Review Process 3

2015 JCIDS Policy/Guidance (3 Documents) CHARTER OF THE JOINT REQUIREMENTS OVERSIGHT COUNCIL (JROC) CJCSI 5123. 01 G (12 Feb 2015) JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM (JCIDS) CJCSI 3170. 01 I (23 Jan 2015) MANUAL FOR THE OPERATION OF THE JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM (JCIDS) (12 Feb 2015, including errata as of 18 Dec 2015) Implements the JROC as a statutory council to the Chairman of the Joint Chiefs of Staff (CJCS) Not intended to stand alone; synchronizes with JROC Charter and JCIDS Manual Procedural guidance for the JCIDS process as well as other requirements-related processes & activities 4

2018 JCIDS Policy/Guidance (2 Documents) CHARTER OF THE JOINT REQUIREMENTS OVERSIGHT COUNCIL (JROC) AND IMPLEMENTATION OF THE JOINT CAPABILITIES AND DEVELOPMENT SYSTEM (JCIDS) CJCSI 5123. 01 H (31 Aug 2018) Implements the JROC as a statutory council to the Chairman of the Joint Chiefs of Staff (CJCS) MANUAL FOR THE OPERATION OF THE JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM (JCIDS) (31 Aug 2018) Procedural guidance for the JCIDS process as well as other requirements-related processes & activities Not intended to stand alone; synchronizes with the JCIDS Manual New JCIDS Policy/Guidance effective 90 days after issuance 5

2016 NDAA Language SEC. 844. MANDATORY REQUIREMENT FOR TRAINING RELATED TO THE CONDUCT OF MARKET RESEARCH. (b) INCORPORATION INTO MANAGEMENT CERTIFICATION TRAINING MANDATE. —The Chairman of the Joint Chiefs of Staff shall ensure that the requirements of section 2377(d) of title 10, United States Code, as added by subsection (a), are incorporated into the requirements management certification training mandate of the Joint Capabilities Integration Development System. Change to JCIDS Manual: Added CLC-004 (Market Research) to the Requirements Management Certification Training (RMCT) Curriculum as a mandatory core plus course for those members of the Requirements Management (RM) workforce assigned to a market research team 6

RMCT Curriculum (Changes) Requirements Management Certification Training (RMCT) Curriculum Level A Certification Level B Certification Level C Certification CLR 101 RQM 110 RQM 310 Introduction to JCIDS Core Concepts for Requirements Management 4 - 6 hours online 18 - 24 hours online “Requirements Apprentice” • Requirements originators & support “Requirements Journeyman” • Requirements writers & developers Advanced Concepts and Skills for Requirements Management 1 -week classroom “Requirements Core Expert” • Requirements presenters & trainers Core Courses – Mandatory for RM Certification Level D Executive Certification RQM 403 RQM 413 Requirements Executive Overview Workshop Senior Leader Requirements Course 1 -3 star GO/FO, SES 4 -star GO/FO, Agency Head 1 -day Classroom Tailored Desktop Discussion “Requirements Validators & Prioritizors” • Make decisions • Set priorities • Approve & Validate JCIDS Documents Core Plus Courses (online) CLR 250 Capability-Based Assessments CLR 151 Analysis of Alternatives CLR 252 Developing Performance Attributes CLC 004 Market Research Core Plus Courses (aka “Just-In-Time”) -- Not Required for Cert Unless Directed by Component Learning and Development Support for All Customers - Military & Civilian, All Grades - Added in new JCIDS Manual 7

2017 NDAA Language • Title 10 U. S. Code Section 181 Joint Requirements Oversight Council, revisions: – Assessing joint military capabilities, and identifying, approving, and prioritizing gaps in such capabilities, to meet applicable requirements in the National Defense Strategy; – Review and validate whether a capability proposed…fulfills a gap in joint military capabilities; – Establishing and approving “joint performance requirements” that ensure interoperability or fulfill a capability gap of more than one armed force are necessary as designated by the CJCS – Input from Chiefs of Staff: JROC shall seek, and strongly consider the views from the Chiefs of Staff of the armed forces, in their roles as customers of the acquisition system, on matters pertaining to capability proposed by an armed force, Defense Agency, or other entity of the Do. D, and joint performance requirements – Changes composition of JROC moving Combatant Commanders from members to advisors and adding USD(I) as an advisor; 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. 8

2017 NDAA Language (Continued) Sec. 805 – Modular Open System Approach (MOSA) in development of Major Weapon System “A major defense acquisition program that receives Milestone A or Milestone B approval after January 1, 2019, shall be designated and developed, to the maximum extent practicable, with a modular open system approach to enable incremental development and enhance competition, innovation, and interoperability. ” 9

Deleted, Sec. 831, 2019 NDAA 10 USC 181 10

JROC Membership (Changes) JROC DECISION CHAIN JROC JCB or FCBs FCB WGs Owns JCIDS; Validates JROC Interest documents; final authority on requirements Validates JCB Interest documents; assists JROC Reviews documents; prioritizes within portfolio; makes validation recommendation to JCB/JROC Reviews documents & prioritizes prior to FCB review JROC: Joint Requirements Oversight Council JCB: Joint Capability Board FCBs: Functional Capability Boards (Force Support, Battlespace Awareness, Force Application, Logistics, Protection, C 4/Cyber. ) FCB WGs: FCB Working Groups JROC MEMBERSHIP Chair: VCJCS. Advises the CJCS Statutory Council Members: • Vice Chief of Staff, Army • Vice Chief of Naval Operations • Vice Chief of Staff, Air Force • Assistant Commandant of the Marine Corps Statutory Advisors: • USD (Policy) • USD (Intelligence) • USD (Research & Engineering) • USD (Acquisition & Sustainment) • USD (Comptroller) • Director, Cost Analysis & Program Evaluation • Director, Operational Test & Evaluation • Combatant Commands (CCMDs) (Commander or Deputy Commander) * * Non-statutory advisors: USD (Personnel & Readiness), Do. D Chief Information Officer, Deputy Chief Management Officer, others are required 11

JROC Functions (New) Joint Requirements Oversight Council (JROC) Support to Other Chairman of the Joint Chiefs of Staff (CJCS) Functions: Joint Capability Development - Identifies new joint military capabilities based on advances in technology and concepts of operation needed to maintain a technological and operational superiority of the Armed Forces and recommends investments and experiments in such capabilities to the Sec. Def. Comprehensive Joint Readiness. Evaluates the overall preparedness of the joint force and assesses the risks to United States missions, strategies, and military personnel that stem from shortfalls in military readiness. 12

Performance Attributes, KPPs, and Other Changes (Changes in Blue) 1 of 3 Performance attribute definitions remain unchanged: – Key Performance Parameters (KPPs) – Key System Attributes (KSAs) – Additional Performance Attributes (APAs) Key Performance Parameters (KPPs): – 2015 JCIDS Manual had six (6) mandatory KPPs: • Net-Ready, Training, System Survivability, Force Protection, Energy, and Sustainment – 2018 JCIDS Manual has four (4) statutory mandatory KPPs • System Survivability, Force Protection, Energy, & Sustainment Net Ready performance attribute still required, but sponsor determines level (KPP, KSA, APA) Training is/may be a DOTm. LPF-P non-materiel consideration – Aspects of training that require performance attributes may be addressed in a KPP, KSA, or APA Gatekeeping (as related to JPRs): Sponsor nomination; JS Gatekeeper & lead FCB determine JPR status Performance attributes designated as Joint Performance Requirement (JPR) will be upgraded to KPP – Joint Staff responsible for certification of JPRs Deletes requirement for Acquisition Category (ACAT) I programs automatically a JSD of JROC Interest – JROC Interest no longer tied directly to cost, instead tied to joint equities as defined under the JPRs 13

Performance Attributes, KPPs, and Other Changes (Changes in Blue) 2 of 3 Change to the Sustainment KPP (adds Maintainability Mandatory Attribute) The Sustainment KPP is derived from system availability requirements to support the required capability, assumptions for its design and operational use as specified in the CONOPS and/or OMS/MP tradeoffs between reliability, maintenance concepts, lifecycle cost, and the planned sustainment strategy • The Sustainment KPP is comprised of several mandatory components: Materiel Availability and Operational Availability, and three mandatory attributes (either KSAs or APAs): – Reliability – Maintainability – O&S Cost For more information see the Sustainment KPP Endorsement Guide: This guide provides procedures for the J-4/MMSD to review the Sustainment KPP during the staffing of a capability requirements document 14

Performance Attributes, KPPs, and Other Changes (Changes in Blue) 3 of 3 Change to the System Survivability (SS) KPP (adds Cyber Survivability) SS KPP is intended to promote the development of critical warfighter capability that can survive kinetic (i. e. , traditional, non-traditional, and CBRN) and non-kinetic (cyber and electromagnetic spectrum (EMS)) threats across domains and applicable environment including space. The SS KPP supports three system oriented objectives: prevention, mitigation in tactically relevant time, and recovery from threats and fires. The SS KPP has focus elements for endorsement: Kinetic Survivability, Cyber Survivability, and Electromagnetic Spectrum (EMS) Survivability Three (3) mandatory elements are included in the SS KPP regarding Cyber Survivability: 1. Cyber Survivability Risk Category (CSRC) identification 2. Exemplar language in the CDD (tailored for an IS-CDD); and 3. Cyber Survivability Pillars (Prevent, Mitigate, and Recover from Cyber Attacks) and associated Cyber Survivability Attributes (CSAs) For more detailed information pertaining to Kinetic Survivability, Cyber Survivability and EMS Survivability see the various Guidebooks/Implementation Guides via KM/DS 15

Cyber Survivability Endorsement • Added Cyber Survivability to the JCIDS System Survivability (SS) Key Performance Parameter (KPP) - Cyber survivability is now part of operational risk trade-space • CSE Implementation Guide: Joint Staff led effort with active participation from Do. D CIO, USD(A&S), USD(R&E), DOT&E, OUSD(I), DIA, and NSA - Provides cyber survivability exemplar statements - Includes cyber survivability attributes to aid requirement definition - Describes tailoring approach for CDD & production document requirements Design/build new weapon systems that are cyber survivable commensurate with a risk managed approach to counter a capable and determined adversary 16

Threat Summary Section Changes • Capability requirement documents: – The Threat Summary helps ensure that the requirements are valid given the context – The Intelligence Supportability section identifies intelligence dependencies and mitigation of shortfalls in intelligence support • Three main processes – Threat Assessment / Intelligence Supportability Certification – Critical Intelligence Parameter (CIP) Breach – Controlled Information Compromise Assessment (CICA) • Threat Assessment / Intelligence Supportability Certification – If JROC or JCB Interest, then Joint Staff will provide certification – document must have at least one Joint Performance Requirement – If Joint Information, Sponsor must provide certification For more information see: JCIDS Manual, Annex G To Appendix G To Enclosure B: INTELLIGENCE SUPPORTABILITY GUIDE 17

CDD Changes (New Section 7) • CDD (Section 7 – NEW!!!): – Modular Open System Approach (MOSA) • Synchronized with the Program Summary of the CDD (section 4) – Links to interoperability – Intelligence Interoperability (if applicable) – Physical Interoperability • Consistent with Do. DAF OV-2 (Operational Resource Flow Description) • Description of the physical aspects of joint interoperability – Net Ready Interoperability • Required (not mandated to be at the KPP level) • Sponsors must include a summary table in Section 5 of the CDD • Reference the Net-Ready Guide in Annex A to Appendix G – Joint Training Technical Interoperability • For systems with a mission solely focused on training, exercises, and/or mission rehearsal, specify how these systems will interoperate within the joint training enterprise 18

ICD and IS-ICD (In Blue) Format 2018 JCIDS Manual Change (In Red) • Cover page/Title *Add “Information Systems ICD for…” to title • Validation page • Waivers (if applicable) • Executive Summary • Document Body: 5 4 Sections/10 Pages (Max): – Operational Context – Threat Summary – Capability Requirements & Gaps/Overlaps *Include NR-attribute table (Initial min value) – Assessment of Non-Materiel Approaches – Final Recommendations *Add IT-Box construct (DOTm. LPF-P) recommendations added • Appendices (limited to 4 6): – References, Acronym List, Glossary, (optional) Classified Appendix – New: Cyber Survivability Risk Categories (CSRC); EMS Survivability Risk Category 19

CDD and IS-CDD Format 2018 JCIDS Manual Changes (In Red) • Cover page/Title *Add “Information Systems CDD for…” to title • Validation page • Waivers (if applicable) • Executive Summary • Document Body 12 13 Sections /45 Pages (Max): – Operational Context – Joint Interoperability – Threat Summary – Spectrum Requirements – Capability Discussion – Intel Supportability – Program Summary *Add IT-Box Parameters – Weapons Safety Assurance – Dev Performance Attributes *Initial min value – Technology Readiness – Other System Attributes – DOTm. LPF-P Considerations • Appendices (limited to 4 6) – Program Affordability *Funding Chart – References, Acronym List, Glossary, (optional) Classified Appendix – New: Annexes A-Z (Optional) Incremental Approach of Fo. S - May attach annexes to CDD 20

JCIDS Manual: (New: CPD No Longer Required) 2015 Guidance: - Utilized a CPD 2018 Guidance: - CPD no longer required - CDD can be updated - CDD can be Annexed to reflect individual programs within a Family of Systems (Fo. S), or incremental capabilities over time/block upgrades 21

CDD Annex (New) Annex Content Guide: Each individual annex will include the same sections as a CDD. Sections with no change to base document must be present but can state “No Change. ” Individual annexes are not to exceed 20 pages in length. In a Fo. S approach, the Sponsor shall develop a base CDD and concurrently staff annexes for individual systems within the family. The base CDD will specify attributes for the entire Fo. S and each annex will specify additional attributes for the individual systems. Section 1: Operational Context Section 8: Spectrum and E 3 Control Requirements Section 2: Threat Summary Section 9: Intelligence Supportability Section 3: Capability Discussion Section 10: Weapon Safety Assurance Section 4: Program Summary Section 11: Technology Readiness Section 5: Development of Performance Attributes Section 12: DOTm. LPF-P Considerations Section 6: Other System Attributes Section 13: Program Affordability Section 7: Joint Interoperability 22

Joint DOTm. LPF-P Change Recommendation (Joint DCR) JCIDS Manual, 2015 JCIDS Manual, 2018 “Little-m” materiel. Identify any previously fielded materiel required as part of the capability solution or as an enabler to allow the capability solution to be utilized to its fullest potential. Previously fielded materiel may be leveraged in either their original capacity or in an adaptation or repurposing not originally envisioned. Sometimes referred to as “little m” materiel, the materiel DOTm. LPF-P consideration is everything necessary to equip Do. D forces to operate effectively. The letter “m” in the acronym is usually lower case, since Joint DCRs do not advocate new materiel development, but rather advocate increased quantities or alternate applications of existing materiel to include Commercial Off-The-Shelf (COTS), Government Off-The-Shelf (GOTS), or Non-Development Items (NDI). 23

JCIDS Manual Process Lanes (2015 to 2018) 2015 Process Lanes 2018 Changes Normal to Deliberate Threat to Need Added Documents CDD Timeline Increased 24

Certifications and Endorsements (Changes in Blue) Certifications and Endorsements JROC/JCB Interest or Joint Information 1 NR Certification Sponsor (or Joint Staff if designated a JPR) FP KPP Certification Sponsor (or Joint Staff if designated a JPR) SS KPP Endorsement Sponsor (or Joint Staff if designated a JPR) Sustainment KPP Endorsement Sponsor (or Joint Staff if designated a JPR) Energy KPP Endorsement Sponsor (or Joint Staff if designated a JPR) DOTm. LPF-P Endorsement Joint Staff (delegated to Sponsor for Joint Information documents) Threat Assessment/Intelligence Certification Joint Staff (delegated to Sponsor for Joint Information Documents) Weapon Safety Endorsement Joint Staff (Only applicable for JROC/JCB Interest) Note: 1 Sponsors have certification and endorsement authority for all performance attributes which are not JPRs. The Joint Staff has certification and endorsement authority for all JPRs. All performance attributes (KPPs, KSAs, or APAs) designated as JPRs will be upgraded as KPPs. 25

Summary of Significant Changes • • Policy/Guidance documents: From 3 to 2 (Combines CJSCI 5123. 01 & 3170. 01) Key Performance Parameters (KPPs): – 2015 JCIDS Manual had six (6) mandatory KPPs: • Net-Ready, Training, System Survivability, Force Protection, Energy, & Sustainment – 2018 JCIDS Manual has four (4) mandatory KPPs • System Survivability, Force Protection, Energy, & Sustainment • SS KPP through 3 lenses (Kinetic, Cyber, and EMS) – Cyber Security Endorsement focus (CSE Implementation Guide) CPD no longer required CDD changes – New section 7: Interoperability (MOSA, Intel, Physical, Net Ready, Joint Training) Performance attributes designated a JPR (will be upgraded to KPP) Delegates Certification/Endorsement to match validation authority Adds Classified Information Compromise Assessment procedures VOLT replaces STAR 26

Clarification/Questions Contact: Eric Jefferies, DAU, DSMC, Professor of Requirements Management Center eric. jefferies@dau. mil (703) 805 -2381 27