Joint Capabilities Integration and Development System (JCIDS) 101

1. Joint Capabilities Integration and Development System (JCIDS) 101 Bob Schloss Joint Staff / J-8 Combat Capability Developer (CCD) robert.schloss@js.mil

2. Agenda • JCIDS Overview • CCD Requirements Management Process

3. Joint Capabilities Integration and Development System (JCIDS) • The Goal of JCIDS is to… • Provide the Joint Force with the capabilities needed to perform across the full range of military operations and challenges • Supported by… • Integrated, collaborative review process • Leveraged expertise of all government agencies • Joint Concepts JCIDSalong with theDefense Acquisition System and the Planning, Programming, Budgeting and Execution processes form the principal DOD decision support processes for developing capabilities required by the military forces to support the national military strategy and the defense strategy

4. JCIDS is… • A key supporting process for DoD acquisition and PPBE processes • That supports “the statutory responsibility of the JROC to validate joint warfighting requirements” • And supports the CJCS advising the Secretary of Defense in identifying, assessing and prioritizing joint military requirements • A Staffing method enabling the Joint Staff to ensure Sponsors’ needs meet the Chairman’s intent (Joint force needs) • JCIDS is not… the entire “Integrated Defense Acquisition, Technology, and Logistics Life Cycle Management System” Requirements (JCIDS) Acquisition Planning Programming and Budget Execution

5. CDD CPD MDD Production & Deployment O&S JCIDS and Acquisition Streamlined Staffing/JROC Validation DCR User Needs Full Rate Prod DR MS B MS C MS A Materiel Solution Analysis Engineering & Manufacturing Development ICD Strategic Guidance Joint Concepts Capabilities - Based Assessment TechDev AoA Incremental Development FCB COCOM OSD/JCS • Materiel Development Decision precedes entry into any phase of the acquisition framework • Entrance criteria met before entering phase • Evolutionary Acquisition or Single Step to Full Capability • JROC Approves all Joint DCRs and all ICD/CDD/CPD for JROC Interest Programs • Tradeoffs may occur during each stage; JROC will validate if the change relates to a KPP • Joint Staff/COCOMs maintain awareness of program trades through participation in IPTs/CSBs Pre MS-A Review/ Analysis

6. Three Requirements “Lanes” “Keep right, except to pass” • Deliberate Requirements • Service, COCOM or Agency Driven • Traditional route for capabilities that require significant tech development and/or are not urgent or compelling in nature • Emergent Requirements • COCOM Driven • Supports accelerated acquisition of capabilities needed for an anticipated or pending contingency operation • VCJCS verifies, DDR validates • Urgent Requirements • COCOM Driven • Urgent and compelling to prevent loss of life and/or mission failure during current operations • Require little tech development and can be resolved in less than two years • VCJCS verifies, DDR validates 0+ to 5 YRS 2-6+ YRS U R G E N T E M E R G E N T D E L I B E R A T E 0 – 2 YRS CONFLICT LANE ONLY POTENTIAL CONFLICT LANE

7. Acquisition (and/or DCRs) Sponsor Gatekeeper Termination Deliberate Requirements Staffing Process FCB Chair: Ready Validation Discussion? Functional Capability Board • SME inputs from DoD • Prioritization within this portfolio • COCOM Inputs • Allied/Partner Nation equity • Non-material recommendations JCB JROC Combined “Staffing” • A Staffing method for the Joint Staff: • …to ensure Sponsor’s military requirements meet the Chairman’s intent (Joint force needs) • …collaborative process to build/gain consensus on specific document • …that can last 4-6 months each time a Sponsor uses it for ICD, CDD, CPD, DCR validation Est. 21 days Commenting/30 days Adjudication/7 days to FCB Chair 4 days Est. 7 days to JCB/14 days to JROC Total: 83 days

8. Functional Capability Boards Force Support Battlespace Awareness C4/Cyber Logistics BGen Busby JS J-8 Mr. Westphal JS J-8 Mr. Hawkins JS J-4 Mr. Allen JS J-2 Additional JCAs Building Partnerships Corporate Management & Support Force Application Protection BGen Busby JS J-8 BG Polakowski JS J-8 FCB Membership: (O-6 level) Services Combatant Command Reps OSD (AT&L) OSD (I) USecAF (Space) ASD NII/ DOD CIO OSD(Comptroller) D, CAPE DIA Rep (Threat) ODNI/IRB Other DoD Agencies as necessary

9. FCBs Triages Requirement COCOM CoS Certifies Requirement JS J8/RMD Receives Requirement Warfighter Originates Requirement JS J8 DDR Validates Requirement as a JUON Services/Agencies Non C-IED Solutions • Joint Rapid Acquisition Cell (JRAC – includes COCOMs) • Determines Resourcing Strategy • Forwards JUONs to JIEDDO or Service/Agency Joint IED Defeat Office C-IED Solutions Joint Urgent Operational Needs & Joint Emergent Operational Needs • Urgent & Emergent Needs are worked through either Joint or Service processes (CJCSI 3170) • JCIDS Documentation determined by Sponsor support and development plans • Senior Integration Group (SIG) Chaired by DEPSECDEF provides oversight for Departmental Urgent Needs Warfighter Verification & Validation of Delivered Capability JCB or JROC Validates Requirement as a JEON Capability Delivery

10. JCIDS Review - Summary of Changes Consolidated four instructions into two and the JCIDS Manual Adjusted JROC to be more Tank-like where lead FCB briefs the topic vice the sponsor with a portfolio-level assessment Joint prioritization process whereby the FCB submits to the JROC a portfolio assessment of the requirement priority and presents it for JROC debate/decision Incorporated Special Access Program to comprehensively integrate requirements/capabilities and provide recommendations for JCB and JROC consideration Deactivated the BP FCB and the LOG JCB Incorporated a pre-MS A review of the Sponsor AoA study and results in support of providing cost, schedule, and performance recommendations to the MDA Clear requirements documents formats and page limits Streamline the Joint Staffing procedures and timelines to increase the effectiveness and responsiveness of the requirements development process

11. JCIDS Review - Summary of Changes (con’t) Requirements validation decisions consider and annotate cost, schedule, performance, and quantity targets in resulting JROCMs as appropriate; expanded tripwire process to review requirements that have deviated from schedule and quantity in addition to cost and performance Clarified the ability of the JROC to call for a review of previously validated requirements/programs through a “summons” JROCM Delineated a process to receive and distribute notifications of Sponsor studies, specifically CBAs, and maintain a repository of studies to inform future decisions Introduced CDTM tool for document generation to standardize and simplify the requirements generation process and creates date-centric documents in the CDTM database for follow-on staffing in KM/DS Standardized the role of the J-7 in the process to emphasize non-material solutions to capability gaps and highlight non-material aspects of new capabilities in development Require the original requirement sponsor and CCMD to conduct a MUA within 90 days of fielding urgent or emergent capability solutions to determine if the capability gap is being addressed as expected

12. Combat Capability Developer (CCD) • Joint Staff lead focused on capability needs and capability development/ integration (strategic-to-tactical) • Fills a voidfor joint capabilities normally addressed by the Service Headquarters -- requirements manager/sponsor, DOTMLPF capability developer, & integrator • DoD Capability Sponsorfor Global Command and Control System-Joint (GCCS-J), Joint C2 Capabilities, Objective Multi-National Information System (MNIS) and Global-Theater Security Cooperation Management Information System (G-TSCMIS) • Dynamic direct coupling of warfighter operational requirements/capability needs to capability material developer(s) • End-to-end, warfighter engagement (concept development through fielding & sustainment) • Active participation by: • Combatant Commands, Services, Agencies, OSD and Multi-National Partners • C2 Council of Colonels • JS J8 DDC4/CCD and JS J36 CSOD Engaged throughout the process 12 12

13. Joint C2 Capability Requirements Governance • Joint C2 Requirements Governance Charter • (25 June 2010) • Captures current processes; C/S/A/JS/OSD inclusiveness • “IT Box” (JCIDS) • Approved by JCB • Leverages: • Joint C2 requirements governance structure & forums • CJCSI 3265.01, C2 Governance & Management • CJCSM 3265.01, Joint C2 Capability Needs/Rqmnts Management Procedures Sustainment & Modernization Planning Warfighter Requirements Feed back Agile Process Capability Fielding Capability Development, Integration, Assessment & Testing Executing in-year, Planning for next year, Preparing for out-years 13

14. Joint C2 CDP / CP Update • Capability Definition Packages (CDPs) and Capability Packages (CPs) • Derived from the Joint C2 CDD • Incremental products articulating the joint warfighter’s validated operational decomposed requirements • Drive materiel capability development • Highlight requirements traceability to capability fielding • JROC-approved process; codified in Draft JCIDS Manual

15. Summary • JCIDS is one portion of the entire CBP process • Provides an enhanced methodology to identify and describe capability gaps and redundancies • Facilitates joint review of capability proposals independent of ACAT (Acquisition Category) • Engages the acquisition community early • Improves the identification of non-material alternatives • Improves collaboration with other departments and agencies • J8 CCD is on leading edge in executing streamlined JCIDS process

16. Questions