CJCSI 3170.01 Revision Update CAPT Jeff Gernand, J-8 22 January 2003

1. CJCSI 3170.01 Revision UpdateCAPT Jeff Gernand, J-822 January 2003

2. 3170 Key Elements • Joint Capabilities Integration and Development System (JCIDS) • Coordinated with DoD 5000 series • Authorization Bill Section 803 language/Milestone A • Capabilities Based Methodology • Functional Capabilities Boards • Analysis done within a component, through FCB direction, or other (analytic agenda) • Documents - ICD, CDD, CPD, CRD

3. National Military Strategy Joint Vision Joint Concept of Operations So, What’s Different? Joint Capabilities Integration and Development System Requirements Generation System Integrated at Department Systems Requirements Joint Operating Concepts Joint Integrated Architecture Joint Capabilities Bottom up, stovepiped Top Down, Born Joint

4. JROC JROC JROC JROC JROC DAB/ Acq Exec DAB/ Acq Exec DAB/ Acq Exec DAB/ Acq Exec DAB/ Acq Exec Requirements Generation System Production and Deployment Concept and Technology Development System Development and Demonstration Determination of Mission Need MS A MS B MS C Full Rate Production Review ORD Update (If Reqd) Decision Review (If Reqd) CRD (If Required) ORD Update ORD MNS IOC MAA MNA LRIP AOA

5. Joint Capabilities Integration and Development System (JCIDS) 2 2 Overarching Policy NSS/NMS/Joint Vision ICD - Initial Capabilities Document CDD - Capability Development Document CPD - Capability Production Document Joint Concept of Operations Functional Area Analysis Functional Area Functional Concept Integrated Arch Feedback D O T M L P F Analysis of Materiel Approaches Materiel Process MS B MS C MS A DOTLPF Process FCB CDD CPD DAB JROC AoA Concept Refinement Technology Development ICD 1 DAB JROC Increment 1 IOC 3 Demo JROC DAB MS C MS B 1 - Concept Refinement Decision 2 - Critical Design Review 3 - Full Rate Production Decision 3 Demo Increment 2

6. FCB Responsibilities • Organization, analysis & prioritization of requirements within functional area • Develop and update functional concept • Ensure integrated architecture reflects the functional area • Ensure new capabilities are conceived and developed in joint warfighting context • Ensure JCIDS documents are consistent with integrated force, leverage abilities of the department, and contribute appropriately • Develop and maintain prioritized list of DOTMLPF requirements • Validate ACAT II and below Joint Impact proposals • JROC approves which FCBs exist, functional areas, lead organization to chair each FCB

7. 1 Service or Other Input to the FCB Input Source Overarching Policy NSS/NMS/Joint Vision ICD/CDD/CPD CDD CPD Joint Concept of Operations JCPAT Review FCB Functional Area Functional Concept Integrated Arch Functional Area Analysis Gatekeeper JROC Interest Joint Impact JROC Interest JROC/ DAB Functional Needs Analysis D O T M L P F Joint Integration Analysis of Materiel Approaches AoA ICD Materiel Process Alternative 1 Alternative 2 Independent DOTLPF Process Joint Impact FCB/ Component Interoperability Certification MDA ICD Source Requirements Process Additional FCBs 1 - Concept Refinement Decision

8. Dominant Maneuver Dominant Maneuver Architecture Architecture Precision Engagement Precision Engagement Architecture Architecture capability capability capability Full Dimensional Full Dimensional Protection Architecture Protection Architecture Focused Logistics Focused Logistics Architecture Architecture Joint Force C2 Joint Force C2 Architecture Architecture Intel, Surveillance, Intel, Surveillance, Recon Architecture Recon Architecture Strategic Deterrence Strategic Deterrence Architecture Architecture 2004 2006 2008 2010 2012 2014 2016 Proposed Methodology Concepts Architectures Assessment Joint Vision Dominant Maneuver Dominant Maneuver National Military Strategy Architecture Architecture Precision Engagement Precision Engagement DM DM task d task a Architecture Architecture task g task b task c task e task f Full Dimensional Full Dimensional Protection Architecture Protection Architecture Joint Concept of Operations system 1 Focused Logistics Focused Logistics Architecture Architecture system 2 Joint Force C2 Joint Force C2 Architecture Architecture system 3 Intel, Surveillance, Intel, Surveillance, Recon Architecture Recon Architecture Service Operating Concepts Joint Operating Concepts system 4 Strategic Deterrence Strategic Deterrence Architecture Architecture system 5 system 6 Resource Strategy Capability Roadmap sys 1 block upgrade new sys FOC sys 3 SLEP sys 2 end of svc life capability task a capability task b FEEDBACK task c 2008 2010 2012 2014 2004 2006 training change field new organization

9. ACQUISITION DECISION POINTSCOMBAT IDENTIFICATION (CID) B and C = AQ Milestones I = IOC F = FOC D = Disposal R = Restructure A - S USN/USMC Link 16 Poss Slip USAF F Link 22 F I F-16 25/30 TBD SADL D A-10 (IF JTRS WAIVER OK) TBD: 2017-2023 I D F C CSEL F I I TACP/MOD C TLDHS I F A - A/S - A NATO MODE 4 IFF USN/USMC B C MODE 5 IFF I F TBD USA I F USAF F I C PROGRAM TERMINATED S-S BCIS BCIS FOLLOW-ON (LEGACY FORCES) TBD BCIS F/O D TBD B C FCS I F C ICIDS PROGRAM TERMINATED LW B C I C B FBCB2 TBD C DACT I F B A MCTIS SERVICE: POM XX - YY FY-XX USA USAF USMC USN JOINT

10. RGS Requirements developed bottom-up CRDs integrate JROC for ACAT I/IA (SI) Components validate and approve the rest Self-policing for coordination Talks about evolutionary acquisition JCIDS Captures joint capabilities Architectures and common concepts set the stage All proposals screened for joint applicability regardless of ACAT FCB is responsible for coordination of functional area Implements evolutionary acquisition RGS versus JCIDS Some similarity in document content The difference is in how you get there

11. MNS Talks to mission need Looks at non-materiel and materiel alternatives Developed bottom-up Good forever ICD Captures the analysis Framed by common concepts What’s the desired capability? Insufficient analysis gets help Evaluates multiple materiel approaches Recommends a materiel approach Addresses a single capability Archived at MS-B ICD Versus MNS Some similarity in content The difference is in the analysis and the common joint picture

12. ORD Describes the materiel solution Attributes and KPPs CDD Describes the SDD effort to develop materiel solution for the increment Attributes and KPPs for the increment Describes the program to get to the complete solution Updated at prior to each Milestone B Incorporates lessons learned ORD Versus CDD Some similarity in content The CDD is focused on development and demonstration effort for the increment

13. ORD Describes the materiel solution Attributes and KPPs May be updated for MS-C CPD Describes the SDD effort to produce materiel solution for the increment Revised production attributes and KPPs for the increment Applies to a single production increment ORD Versus CPD Some similarity in content The CPD is focused on production of the increment

14. Development Threshold Development Objective A 10 1 Development Threshold Development Objective Optimum Optimum A 10 1 Post-Trades Performance Development Threshold Development Objective A 10 1 Production Performance Target Production Threshold Production Objective A 6 2 Thresholds and Objectives

15. Schedule 14-16 January Writing team final session 21 Jan - 12 Feb O-6 Staffing (22 days) 28 Jan JRP 29 Jan JRB TBD JROC 12 - 17 Feb Comment Resolution 18 Feb O-6 Comment Conference 20 Feb - 6 Mar Flag Staffing (15 days) 7 - 14 Mar Comment Resolution 17 - 18 Mar Flag Comment Conference 28 Mar Final Signature

16. Implementation • CRDs • JROC approved still current • Annual listing of effective CRDs and CRDs approved for development • MNS • No new MNS • No MNS over four two years old will support a MS-A or direct to MS-B or MS-C decision • Past MS-A, B or C no revision to ICD required • ORD • No ORDs six months after signature

17. Questions?

18. Service RGS Documents Processed by Year

19. Joint fire support Conventional attack execution Nuclear attack Joint targeting Joint munitions Suppression of enemy air defenses Alternative 2 Portfolios Force Application • Land combat ops • Air ops • Littoral warfare • Space ops • Joint urban ops • Computer network attack • Nuclear operations • Unconventional warfare • Military deception • Electronic attack • Special ops • Psychological ops

20. SIGINT OSINT MASINT IMINT HUMINT Combat ID Electronic support Alternative 2 Portfolios Battlespace Awareness Command and Control • Communications • Joint Force C2 including standing joint force headquarters • Communications and computer environment • Campaign planning • Knowledge management • Predictive analysis • Threat warning (Includes partial processing of intelligence data) J2 position

21. Deploy / redeploy Sustain Medical Mobility Logistics C2 Alternative 2 Portfolios Protection Logistics • Consequence management • Personnel and infrastructure protection • OPSEC • Computer network defense • Non-proliferation • Counter-proliferation • Missile defense • Electronic protection

22. Things to resolve - As of 10 Jan • FCBs - A cross-Service body engaged in each functional area is key to an effective JCIDS process • A finding of DPG Study 20 Group • Confirmed by CJCSI 3170 Writing Team • Historical throughput about 150 Service documents per year (all ACATS). • About 2500 Service acquisition programs. DJ-8 direction to send draft CJCSI 3170 to O-6 coordination and complete coordination on draft DoD 5000. Staffing initiated on 21 Jan.