1. 2018 Joint Capabilities Integration & Development System (JCIDS)
Changes
Rapid Deployment Training (RDT)
Eric Jefferies, DAU, DSMC,
Professor of Requirements Management
Requirements Management Center
(703)
11 October 2018
Sources:
CJCSI H, 31 August 2018
JCIDS Manual, 31 August 2018
2018 JCIDS Changes RDT

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

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

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

5. 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 H
(31 Aug 2018)
Implements the JROC as a statutory council to the Chairman of the Joint Chiefs of Staff (CJCS)
Not intended to stand alone; synchronizes with the JCIDS Manual
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
New JCIDS Policy/Guidance effective 90 days after issuance

6. 2016 NDAA Language
SEC 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

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

8. 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 DoD, 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.

9. 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.”

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

11. JROC Membership (Changes)
JCB
JROC
FCB WGs
FCBs
JROC DECISION CHAIN
JROC: Joint Requirements Oversight Council
JCB: Joint Capability Board
FCBs: Functional Capability Boards (Force Support, Battlespace Awareness, Force Application, Logistics, Protection, C4/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), DoD Chief Information Officer, Deputy Chief Management Officer, others are required
Owns JCIDS; Validates JROC Interest documents; final authority on requirements
Validates JCB Interest documents; assists JROC
Reviews documents & prioritizes prior to FCB review
Reviews documents; prioritizes within portfolio; makes validation recommendation to JCB/JROC or

12. 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 SecDef.
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.

13. 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 DOTmLPF-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

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

15. 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:
Cyber Survivability Risk Category (CSRC) identification
Exemplar language in the CDD (tailored for an IS-CDD); and
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

16. 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 DoD 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

17. 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)
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

18. 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 DoDAF 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

19. 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 (DOTmLPF-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

20. 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 Sections /45 Pages (Max):
Operational Context
Threat Summary
Capability Discussion
Program Summary *Add IT-Box Parameters
Dev Performance Attributes *Initial min value
Other System Attributes
Joint Interoperability
Spectrum Requirements
Intel Supportability
Weapons Safety Assurance
Technology Readiness
DOTmLPF-P Considerations
Program Affordability *Funding Chart
Appendices (limited to 4 6)
References, Acronym List, Glossary, (optional) Classified Appendix
New: Annexes A-Z (Optional) Incremental Approach of FoS - May attach annexes to CDD
System of Systems (SoS) - A set or arrangement that results when independent and useful systems are integrated into a larger system that delivers unique capabilities. SoS may deliver capabilities by combining multiple collaborative and independent-yet-interacting systems. The mix of systems may include existing, partially developed and yet-to-be designed independent systems. (Source: DoD, 2018, DAU Glossary)
Family of Systems (FoS) - A set of systems that provide similar capabilities through different approaches to achieve similar or complementary effects For example, the warfighter may need the capability to track moving targets. The FoS that provides this capability could include manned or unmanned aerial vehicles (UAVs) with the appropriate sensors, a space based platform or special operations capability. Each can provide the ability to track moving targets, but with differing characteristics of persistence, accuracy, timeliness, etc. (Source: DoD, 2018, DAU Glossary)

21. 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 (FoS), or incremental capabilities over time/block upgrades
- An ICD may lead to the creation of multiple CDDs to describe a System of Systems (SoS) approach or a single CDD with multiple annexes to describe a FoS approach or for incremental development.
- For an SoS, where a set of systems are integrated to deliver a unique capability solution, the Sponsors should develop individual CDDs for each system within the SoS.
- In an FoS, where similar capabilities are provided through different approaches to achieve similar or complementary effects, the Sponsor may choose to use CDD annexes to specify individual performance attributes for each individual system in the FoS. In this case, they can validate the base CDD and all CDD annexes at the same time.
- Sponsors may choose to develop capability in increments over time through the use of CDD annexes. In this case, they may validate a base CDD for the first increment, and then use annexes, separated by time, to validate subsequent increments of the capability.

22. 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 FoS 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 FoS and each annex will specify additional attributes for the individual systems.
Section 1: Operational Context
Section 2: Threat Summary
Section 3: Capability Discussion
Section 4: Program Summary
Section 5: Development of Performance Attributes
Section 6: Other System Attributes
Section 7: Joint Interoperability
Section 8: Spectrum and E3 Control Requirements
Section 9: Intelligence Supportability
Section 10: Weapon Safety Assurance
Section 11: Technology Readiness
Section 12: DOTmLPF-P Considerations
Section 13: Program Affordability

23. Joint DOTmLPF-P Change Recommendation (Joint DCR)
JCIDS Manual, 2015
“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.
JCIDS Manual, 2018
Sometimes referred to as “little m” materiel, the materiel DOTmLPF-P consideration is everything necessary to equip DoD 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).

24. JCIDS Manual Process Lanes (2015 to 2018)
Staffing Phases:
Initial Review (Joint Staff Gatekeeper and select stakeholders) (ICD, IS-ICD, or Joint DCR=4 calendar days; CDD/IS-CDD=10 calendar days).
Initiation. The deliberate staffing process begins when the Joint Staff Gatekeeper, after screening and review, submits the document into JCIDS. Initial review of the document(s) is conducted within 4 calendar days for an ICD, IS-ICD, or Joint DCR and 10 days for a CDD or IS-CDD.
2018 Changes
Normal to
Deliberate
Threat to
Need
Added
Documents
CDD Timeline
Increased

25. Certifications and Endorsements (Changes in Blue)
JROC/JCB Interest or
Joint Information1
NR Certification
Sponsor (or Joint Staff if designated a JPR)
FP KPP Certification
SS KPP Endorsement
Sustainment KPP Endorsement
Energy KPP Endorsement
DOTmLPF-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:
1Sponsors 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.

26. Summary of Significant Changes
Policy/Guidance documents: From 3 to 2 (Combines CJSCI & )
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

27. Clarification/Questions Contact:
Eric Jefferies, DAU, DSMC,
Professor of Requirements Management
Requirements Management Center
(703)