Joint Capabilities Integration & Development System (JCIDS)

1. Joint Capabilities Integration & Development System (JCIDS) Center for Program Management Defense Acquisition University October 2004

2. Joint Capabilities Integration & Development System (JCIDS) VCJCS/Service Chief Oversight Defense Acquisition System Planning, Programming, Budgeting & Execution Process (PPBE) Milestone Decision Authority (MDA) Oversight DEPSECDEF Oversight Three DoD Decision Support Systems

3. A Problem Statement

4. JCIDS RGS Integrated atDepartment JointVision National Military Strategy Systems Joint Concept of Operations Requirements Joint ConceptsIntegrated Architectures Joint Capabilities Top Down, Born Joint Bottom Up, Forced Jointness Transformation to the Joint CapabilitiesIntegration and Development System

5. JCIDS Provides • Early leadership focus on key decision points • Rigorous up-front analysis by functionally-focused teams • Early and continuous engagement of acquisition community • Joint visibility on all ACAT programs • Capabilities documents tailored to each phase of the acquisition process • Prioritization of joint warfighting capability gaps. • Improved prioritization of validated joint warfighting capability proposals. • Better definition of the DOTMLPF implications resulting from the development and fielding of a new capability. • Improved coordination with other USG departments or national agencies.

6. RGS: MNS ORD CRD Bottoms-up Service focus Evolutionary Acquisition minor role No construct for Joint Staff analysis Joint warfighting needs not prioritized Materiel solutions determined in acquisition process (concept exploration) JCIDS: ICD CDD at Milestone B CPD at Milestone C CRD Joint Capabilities Integration & Development System (JCIDS) vs. Requirements Generation System (RGS) • Top-down • Born joint • Evolutionary acquisition in sync with 5000 • Enhanced analytical process • Prioritized capability gaps and proposed solutions • Materiel solutions determined in JCIDS analysis; refined in acquisition process (concept refinement)

7. MS-A REFINE ANALYSIS JCIDS Ties to the DOD 5000 Series Strategic Policy Guidance ICD – Initial Capabilities Document CDD – Capability Development Document CPD – Capability Production Document Joint Operating Concepts Joint Functional Concepts Integrated Architectures Concept Decision MS-C MS-B REFINE ANALYSIS IOC JCIDS Analysis JROC DAB/ ITAB DAB/ ITAB JROC DAB/ ITAB JROC DAB/ ITAB JROC – Joint Requirements Oversight Council DAB – Defense Acquisition Board ITAB – Information Technology Acquisition Board

8. National Security Strategy (2002) National Military Strategy (2004) • One JIC draft, Aug 04 • Seabasing JCIDS Analysis Strategic Policy Guidance • Four draft JOCs, Sep 04 • Homeland Security • Stability Operations • Strategic Deterrence • Major Combat Operations • Five JROC Approved FC’s: • Joint C2 • Force Application • Focused Logistics • Protection • Battlespace Awareness Joint Operations Concepts Nov 2003 Functional Area Analysis Joint Operating Concepts Joint Functional Concepts Joint Integrating Concepts Integrated Architectures CPD Functional Needs Analysis CDD D O TMLPF analysis Alternative N Post Independent Analysis Ideas for Materiel Approaches Materiel Changes CJCSI 3170 process Analysis of Materiel Approaches ICD Alternative 2 Alternative 1 DOTMLPF Change Recommendation DOTMLPF Changes CJCSI 3180 Process Functional Solution Analysis Sponsor leads Sponsor. The DOD component responsible for all common documentation, periodic reporting, and funding actions required to support the requirements and acquisition process.

9. Top-Down Direction to Support JCIDS Analysis • Strategic Policy Guidance • National Security Strategy: (50 USC 404a) Issued annually; latest is Sep 2002. • National Military Strategy: (CJCSI 3100.01)Articulates the Chairman’s recommendations to the NCA on how the President should employ the military element of power in support of the President’s National Security Strategy. Published as needed; latest is 2004.

10. Top-Down Direction to Support JCIDS Analysis • Joint Staff Supporting Documents (CJCSI 3170.01D) • Joint Operations Concepts (JOpsC):Describes how the joint force intends to operate 15 to 20 years from now. • Joint Operating Concept (JOC):How the future joint force commander will plan, prepare, deploy, employ and sustain a joint force against potential adversaries’ capabilities or crisis situations. Guide the development and integration of JFCs to provide joint capabilities. • Joint Functional Concept (JFC):How a future joint force commander will integrate a set of related military tasks to attain capabilities required across the range of military operations. • Joint Integrating Concepts (JIC): Describes how a joint force commander integrates functional means to achieve operational ends. • Integrated Architectures:Consists of multiple views or perspectives (operational, systems, technical) that facilitates integration and promotes interoperability across family-of-systems and systems-of-systems and compatibility among related architectures.

11. JCIDS Analysis • Functional Area Analysis (FAA) • Identify operational task, conditions, and standards needed to accomplish military objectives • Result:Tasks to be accomplished • Functional Needs Analysis (FNA) • Assess ability of current and programmed capabilities to accomplish the tasks • Result:List of capability gaps • Functional Solutions Analysis (FSA) • Operational based assessment of doctrine, organization, training, materiel, leadership/education, personnel, and facilities (DOTMLPF) approaches to solving capability gaps • Result:Potential integrated DOTMLPF approaches to capability gaps • Post Independent Analysis • Independent analysis of approaches to determine best fit • Result:Initial Capabilities Document

12. Integrated Architectures FCB ensures they reflect the Approved Functional Concept (JFC ) • Functional Capabilities Boards (FCB) • Force Application • Force Protection • Focused Logistics • Command & Control • Net-Centric Operations • Battlespace Awareness • Integrated Architectures • Systems View • Operational View • Technical View Functional Concept User/ Joint Staff Lead operational view (OV) - A view that describes the joint capabilities that the user seeks and how to employ them. The OVs also identify the operational nodes, the critical information needed to support the piece of the process associated with the nodes, and the organizational relationships. systems view (SV) - A view that identifies the kinds of systems, how to organize them, and the integration needed to achieve the desired operational capability. It will also characterize available technology and systems functionality. AT&L Lead technical view (TV) - A view that describes how to tie the systems together in engineering terms. It consists of standards that define and clarify the individual systems technology and integration requirements. PM Lead

13. JCIDS Documents • Initial Capabilities Document (ICD) (replaced MNS) • Identifies a capability gap or other deficiency • Describes evaluation of DOTMLPF approaches • Supports Concept Decision, Analysis of Alternatives (AoA), Concept Refinement and Milestone A • Not updated once approved • Capability Development Document (CDD) (replaced ORD at Milestone B) • Identifies operational performance attributes of proposed system • System specific, applies to single increment (in an evolutionary program) • Results from Technology Development; supports Milestone B • Updated or rewritten for subsequent increments

14. JCIDS Documents (cont’d) • Capability Production Document (CPD) (replaced ORD at Milestone C and FRPDR) • Identifies production attributes for a single increment of a program • Prepared during System Development and Demonstration • Rewritten for each increment in an evolutionary program • Capstone Requirements Document (CRD) (no near-term change) • Describes overarching thresholds/goals and standards in functional areas • Useful for family-of-systems or system-of-systems approaches • Developed only at JROC direction • Eventually will be replaced by integrated architectures

15. Sponsor Responsibilities • Lead JCIDS analysis (FAA, FNA, & FCA) required to develop ICD. • Make affordability determinations in valuation of various approaches. • Develop JCIDS documentation & present it for review through KM/DS tool. • Resolve issues that arise during staffing, certification & validation. Unresolved critical comments briefed to JCB/JROC for decision. • When system contributes to FoS or SoS capabilities, coordinate with sponsors of related CDDs and CPDs to synchronize development & delivery of systems & required overarching DOTMLPF changes. • Present briefings to decision bodies, as required. • Coordinate/collaborate with non-DOD agencies & departments on development of interagency capabilities. • When sponsor disagrees with assigned JPD, appeal can be made to FCB or Gatekeeper. Enclosure B, CJCSI 3170.01D, 12 Mar 2004

16. JCIDS Gatekeeper (Deputy Director, J-8) • Perform initial review of all JCIDS proposals • Support provided by JFCOM, J6, J7, J8, FCB Working Groups • The Gatekeeper determines: • Joint Potential Designator • Lead and supporting Functional Capabilities Boards (FCB) • Lead and supporting FCB Working Groups

17. Joint Potential Designators (JPD) • JROC Interest • All ACAT I/IA and ACAT II and below programs where the capabilities have a significant impact on joint warfighting • CRDs, and DOTMLPF change proposals • Any other program so designated • JROC validates and approves • Joint Integration • Any ACAT II and below program without significant joint impact • Requires intelligence, munitions and interoperability certification • Sponsor validates and approves • Independent • Any program not meeting the above criteria • Sponsor validates and approves

18. JCIDS Document Flow Sponsor Responsibility Joint Staff Responsibility JCB/ JROC Validation/ approval JROC Interest JCIDS Analysis FCB review GATEKEEPER (Deputy J-8) All ACAT I/IA programs & ACAT II and below where capabilities have significant impact on joint warfighting JPD Decision ICD CDD CPD KM/DS J-2 J-4 J-6 Review* Acquisition Executive Joint Integration Sponsor Validation/ approval ACAT II & below without significant joint impact, but require joint staff certification Independent All other programs Final document to database Sponsor. The DOD component responsible for all common documentation, periodic reporting, and funding actions required to support the requirements and acquisition process. *Note: Also applies to Joint Interest/Joint Impact prior to FCB review J-2 – intel/threat validation J-4 – munitions certification J-6 – interoperability certification KM/DS - Knowledge Management/Decision Support Tool (virtual SIPRNET library for review, approval, and reference)

19. Chartered FCBs FCBs: • Milestone Decision Authority co-chairs • Brings all stakeholders together for common review and issue resolution • Prioritizes/assesses capability gaps and proposals The JROC: • Charters FCBs • Directs FCB efforts • Identifies the FCB lead Force Application J-8 Focused Logistics J-4 Net-Centric Operations J-6 Force Management J-1 Command & Control JFCOM Battlespace Awareness J-2 Force Protection J-8

20. Force Application Focused Logistics Force Management Net-Centric • Engagement-Kinetic • Conventional Attack • Nuclear Attack • Close Combat • Joint Fire Support • Engagement-Non- • Kinetic • Psychological Operations • Electronic Attack/ Directed Energy • Computer Network Attack • Maneuver • Land Combat Operations • Maritime Operations • Air Combat Operations • Space Combat Operations • Deployment & Distribution • Joint Deployment Process Owner • Unit Movement Systems • Mobility • Support Helicopters • Cargo Aircraft • Sustainment Ships • Sustainment • Industrial Base • Maintenance Equipment • Cargo Parachutes • Force Health Protection • Vaccines • Medical Equipment • Dental Equipment • Logistics C2 • GCSS • In Transit Visibility • Operational Engineering • Family of Loaders • Engineer Equipment • Deployment & Distribution • GIG Infrastructure & Services • Data Transport & Storage • Dissemination • Info assurance • SATCOM • Navigation, broadcast systems • Enterprise Services • Info Management • National to Tactical C4I Integration • Multinational Info Sharing • National & Strategic C2 Sharing • Horizontal C2 Integration • Cross-functional Net- centric Integration • Legacy Communications Systems • Readiness • Joint Manning • Global Posture • AC/RC • Force Generation • Command Relationships • Global Visibility of force structure issues • Force Management Data Construct • Building Global Force Management (GFM) Capability FCB Portfolios

21. Command & Control Battlespace Awareness Force Protection • Integrated JBMC2 • SFJHQ • DJC2 • JNTC • Integrated Joint Fires • Capabilities • Advanced C2 Concepts • Effects based planning • Effects based operations • Operational Net Assessment • Situational Awareness • (Red/Blue) • Combat Identification • Collaborative Information • Environment • Common Operational • Pictures • Adaptive Mission • Planning & Rehearsal • Command & Control of • Battlespace Awareness • Assets • Synchronize ISR operations • Task, dynamically re-task & monitor assets • Execute Collection • Persistent Surveillance • Cross cure • Employ human resources • Measure & monitor environmental conditions • Exploit & Analyze • Recognize targets • Distribute processing • Information fusion • Enable analyst collaboration • Defeat denial & deception • Model, Simulate, Forecast/ • Predict • Predictive analysis • Integrate adversary & friendly information • Manage Knowledge • Smart pull/push information • Share plan visibility • Content management • Personnel Protection • Anti-terrorism • Combat search & rescue • Explosive Detection & Defeat (EOD) • Insensitive Munitions & ordnance & weapons safety • Critical Asset Protection • Aircraft Defensive Systems • Ship Defensive Systems • Electronic Protection • Critical Infrastructure Protection • COG/COOP • Homeland Security • Air & Missile Defense • Ballistic Missile Defense • Air & Cruise Missile Defense • Interagency Homeland Air Security • Consequence • Management • Proliferation Control • CBRN FCB Portfolios

22. FCB Membership Principal Membership (O-6/GS-15 representatives) • Military Services • Combatant Commands • Joint Staff • USD for Acquisition, Technology, and Logistics • USD for Intelligence • USD Comptroller • ASD for Networks and Information Integration/DoD Chief Information Officer • USecAF (Space) • Defense Intelligence Agency • Director, Program Analysis & Evaluation • Mission Requirements Board Executive Staff Advisory Membership • FCB Working Group leads • J-6 rep (interoperability advisor) • J-8 Warfighting Concepts and Architectures Integration Division • DOD laboratories • Industry/corporate expertise (as required) • CJCS Legal Counsel (as required)

23. Functional Configuration Board Responsibilities • Coordinate, integrate & deconflict efforts of all DoD Components within assigned functional area(s) • Ensure DOTMLPF aspects of new capabilities are being appropriately considered in JCIDS documents • Assist in adjudication of comments received during staffing process • Evaluate & forward complete JCIDS documents designated JROC Interest to JROC for validation & approval • Recommend retirement of unnecessary JCIDS documents • Review & endorse prioritized list of DOTMLPF warfighting capability gaps within assigned functional area(s) • Ensure D, PA&E, USD(AT&L) and ASD(NII) have the opportunity to participate in or review the analysis conducted in support of ICD designated as JROC Interest. • When documents potentially impacting national intelligence capabilities come to the FCB for validation/approval, the FCB Chair will invite the MRB staff to send a representative to attend/co-chair the FCB meeting. • Ensure that JFC are developed & updated as required to accurately implement overarching DoD policies. Enclosure B, CJCSI 3170.01D, 12 Mar 2004

24. Functional Configuration Board Responsibilities (Continued) • Request DOD Components support FCB activities. Tasking issues that cannot be resolved between the FCB(s) & the Component(s) will be forwarded to the JROC (through the JCB) for resolution. • Ensure overarching joint DOTMLPF change recommendations are addressed through the CJCSI 3180.01 process. • Annually review the functional area portfolio of JROC Interest materiel proposals & DOTMLPF change recommendations for completeness & prioritization. • Ensure integrated architecture(s) are updated as required. • Evaluate assigned JPD of all initiatives & make a recommendation to Gatekeeper to change JPD as required. • If Lead FCB determines they are the inappropriate selection for a given document, coordinate with appropriate FCB & make a recommendation to Gatekeeper to reassign Lead FCB role. • When an FCB is designated as supporting, perform appropriate assessment/analysis of the capability & provide a summary of that assessment/analysis to Lead FCB. • Review & assess non-JCIDS documents & briefings as assigned by JROC & Gatekeeper. Enclosure B, CJCSI 3170.01D, 12 Mar 2004

25. FCB Working Group Responsibilities • Coordinate with & assist sponsor during JCIDS document development to ensure cross-Component harmonization of proposals, & that joint warfighting capability gaps are adequately addressed • Support Gatekeeper in determining the JPD & lead and/or supporting FCBs for each JCIDS document. • Lead Working Group will analyze JCIDS documents & coordinate with supporting Working Groups to ensure all joint warfighting aspects have been considered in the analysis. Provide context & a summary of the FCB Working Group’s independent assessment regarding JCIDS proposals to the FCB when considering capabilities documents. Enclosure B, CJCSI 3170.01D, 12 Mar 2004

26. FCB Working Group Responsibilities (Continued) • Supporting Working Group will coordinate with & support lead Working Group analysis. • Coordinate with sponsor to adjudicate any potential issues prior to or as a result of formal staffing. • Provide summary analysis & recommendation to FCB/JCB/JROC on validation and/or approval of JCIDS documents. • Continually review assigned functional area to identify capability shortfalls. • Develop prioritized lists of capability shortfalls & current JCIDS proposals within assigned functional areas. Enclosure B, CJCSI 3170.01D, 12 Mar 2004

27. AoA ICD CD Concept Refinement Joint Capabilities Integration & Development System (from FAA to Milestone A) Strategic Policy Guidance Joint Operations Concepts Functional Area Analysis Joint Operating Concepts Joint Functional Concepts Joint Integrating Concepts Integrated Architectures Feedback Functional Needs Analysis D O T M L P F analysis Analysis of Materiel Approaches Ideas for Materiel Approaches Materiel Changes CJCSI 3170 MS A Alternatives DOTLMPF Changes CJCSI 3180 Post Independent Analysis Functional Solution Analysis JROC DAB/ITAB/ DSAB

28. FRP DR FRP DR C B DRR DRR Join Capabilities Integration & Development System Milestone A to IOC To JCIDS Analysis process Feedback MS B MS C CDD MS A DAB/ITAB/ DSAB JROC CPD Technology Development DAB/ITAB/ DSAB JROC DAB Sys Dev & Demonstration Increment 1 IOC Demo Sys Dev & Demonstration Increment 2 Demo

29. One Last Thing What’s all this I’m hearing about Net-Ready & Net-Centric Information Environment? • Derived from recent CJCSI 6212.01C • Old Interoperability KPP now called Net-Ready KPP • C4I Support Plan renamed Information Systems Plan (ISP) • JCIDS Instruction revised to reflect that change So what is it?

30. Interoperability KPP Today Top-level IERs will be used as the basis to develop interoperability KPPs. The interoperability KPP definition will include that all top-level IERs will be satisfied to the standards specified in the threshold and objective values. Typically the threshold criterion for the interoperability KPP will be 100 percent accomplishment of the critical top-level IERs, and the objective criterion for the interoperability KPP will be the accomplishment of all top-level IERs. Interoperability KPP Threshold (T) Objective (O) All top-level IERs will be satisfied to the standards specified in the Threshold (T) and Objective (O) values. 100% of top-level IERs designated critical 100% of top-level IERs (CJCSI 6212.01B)

31. Problem: IER Scalability One-to-One Current Interoperability KPP centers around one DoD architectural view (OV-3) that contains “Information Exchange Requirements” (IERs) • One-to-one relationship (point-to-point) This example: 10 systems IERs 10(10-1) = 90

32. Solution: The Net-Ready Approach One-to-Many Net Ready approach centers on central network: • Focus on organizational contributions and consumption of information • One-to-network paradigm Network This example: 1 system has to deal with 1 interface

33. Additional Resources • DoD 5000 Resource Center, http://dod5000.dau.mil Includes: • Joint Capabilities Integration and Development System (JCIDS) Instruction (CJCSI 3170.01D) and Manual (CJCSM 3170.01A) Overview Video • Defense Acquisition System Directive (DoDD 5000.1) and Instruction (DoDI 5000.2) Overview Video Tutorial, Frequently Asked questions, Terminology Interactive DoD 5000 • Business Transformation Briefing (DoD 5000, JCIDS & PPBE) • Joint Staff’s Future Warfare Web Site, http://www.dtic.mil/jointvision/ • Joint Operations Concepts • Joint Operating Concepts • Joint Functional Concepts • Joint Integrated Architectures