jcids overview 10 may 2005 l.
Skip this Video
Loading SlideShow in 5 Seconds..
JCIDS Overview 10 May 2005 PowerPoint Presentation
Download Presentation
JCIDS Overview 10 May 2005

Loading in 2 Seconds...

play fullscreen
1 / 17
Download Presentation

JCIDS Overview 10 May 2005 - PowerPoint PPT Presentation

Download Presentation

JCIDS Overview 10 May 2005

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Joint Capabilities Integration & Development System JCIDSOverview10 May 2005 Joint Staff / J-8 Capabilities and Acquisition Division

  2. Previous Requirements and Acquisition Process • As a rule, CONOPs and requirements were Service-focused • Analysis was primarily threat-based • Process lacked a construct for Joint analysis “up-front” • Systems integration tended to be forced in at end game • Duplication existed, particularly in smaller programs • Spiral acquisition was not well institutionalized • Joint warfighting needs were not prioritized

  3. Capability Based Methodology Requirements Generation System (RGS)- ~30 years of experiences Joint Capabilities Integration and Development System (JCIDS)- 1 year old Strategic Direction Partially Interoperable Capabilities Joint Warfighting Concept Development Late Integration Joint Experimentation, Assessment & Analysis,Validation, Selection of Solutions Services Build Systems Service Experimentation, Assessment & Analysis,Validation, Selection of Solutions Services, COCOMs Joint Capabilities Service Unique Strategic Visions and Requirements

  4. Desired Attributes of DOD Decision Process Responsive Flat Involve leaders “when it counts” Agree on facts New 3170.01D Top down Born “Joint” Tees up issues with wider input earlier in the process JROC Impact using JCIDS Personal time devoted to the process by leadership Ability to influence a business process (Avoid) (Embrace) Time Action Agent: Functional Capabilities Boards

  5. Initial Capabilities Document Functional Solutions Analysis Functional Solutions Analysis Functional Solutions Analysis Functional Solutions Analysis JCIDS Evolution – Concepts to Capabilities First order assessment using operational tasks and force elements Joint Concepts and MSFD scenarios Strategic Guidance Joint Operations Concepts DPS DPS Joint Operating Concepts DPS DPS Joint Functional Concepts DPS Joint Integrating Concepts SecDef Joint Chiefs of Staff Joint Requirements Oversight Council Provide DOTMLPF Solutions Operational Modeling to identify gaps and excesses Capability Roadmap & Resource Strategy Sys 1 Sys 1 Sys 3 Sys 3 Sys 2 Sys 2 New Sys New Sys Block Block SLEP SLEP End of Svc Life End of Svc Life FOC FOC Upgrade Upgrade capability capability Campaign Engagement Mission 2010 2010 2008 2008 2006 2006 2004 2004 2014 2014 2012 2012 Training Training Field New Field New Change Change Organization Organization Secretary of Defense Services Joint Requirements Oversight Council

  6. Army Navy USMC FCBs Air Force COCOMs OSD (AT&L) DIA OSD (PA&E) OSD (NII) The JROC Capability-Based Assessment Process Month 8 Month 10 Month 9 Month 7 Month 11 Month 6 Month 1 Month 4 Month 2 Month 3 Month 5 Joint Integrating Concept Development & Mission Analysis Capabilities-Based Assessment • FSA • Determine initial Non-materiel & Materiel Alternatives • Recommend a prioritized capability approach to meet the need, including initial TRL, sustainability, supportability, schedule of delivery, and affordability assessments • Assess operational risk of each approach • Consider S&T Initiatives • ID Experimentation needs • FAA • Capabilities • Tasks • Attributes • Metrics • FNA • Gaps • Shortfalls • Redundancies • Risk Areas Campaign-level Analysis Resourcing & TOR Development Experimentation Inputs/Recs • Concept Development • Tasks • Capabilities • Attributes • Metrics • Concurrent Development of DPS-based vignette • Solutions • Material • Non-Material SPONSOR COCOM or Service

  7. DOD End-to-EndCapabilities, Acquisition, and Test Process Technology Development System Development Technology Development System Development Production CPD CPD Production CDD CDD DAB Capability Area Reviews (CARs) • Refined concept • Analysis of Alternatives • Technology Development Strategy • SoS System Engineering • Affordable military-useful increment • Technology demonstrated • Initial KPPs • SEP • Strategic Planning Guidance • Defense Planning Scenarios • Family of Concepts • Transforma-tion • Revise KPPs • Detailed design • System integration • DT&E • LRIP • IOT&E Capabilities Based Assessment • LRIP • FOT&E • Non-materiel solutions • Materiel solutions • S+T initiatives • Experimentation • Capabilities • Tasks • Attributes • Metrics • Gaps • Shortfalls • Redundancies • Risk areas Concept Decision MS “A” MS “B” MS “C” activity Functional Area Analysis *Functional Needs Analysis *Functional Solutions Analysis Select a Joint Integrating Concept Develop Concept Analysis of Alternatives Technology Development System Development ICD Production CPD CDD Capability Based Assessment Evolutionary or Spiral Development OSD (AT&L)- led Capability Roadmaps Army Navy USMC FCB OSD/JCS COCOMs Air Force Services COCOM OSD (AT&L) DIA OSD (NII) OSD (PA&E) oversight SecDef OSD (AT&L, PA&E), Services and OSD (DOT&E) -- Joint Staff (JROC) Joint Chiefs of Staff & Joint Requirements Oversight Council Joint Staff / OSD Joint Staff (OSD) Capabilities Definition Acquisition and Test Concept Refinement Policy *“as is” Roadmaps

  8. New JCIDS Documents • Joint Capabilities Document (JCD) • Identifies capability gaps or other deficiencies • Supports development of one or more ICDs • Developed primarily by COCOMs and FCBs • Can be developed by a sponsor under certain conditions • Updated as required • Joint DOTMLPF Change Recommendation (DCR) • Identifies an approach to filling a capability gap through non-materiel changes • Developed primarily by COCOMs • Formerly described in CJCSI 3180.01

  9. Joint Capabilities Document (JCD) Purpose of the JCD: • Describes capability gaps as determined by the functional area and needs analyses • Identifies the relative importance/priority of the gaps • Highlights capability gaps that are important enough to justify pursuing a solution • Identifies gaps where risk may be taken` When is a JCD required? • COCOM generates based on emerging/changing missions or identified capability gaps • FCBs generate based on the results of a JIC • Sponsors may generate when pre-coordinated with COCOMs and FCBs

  10. JCIDS Gatekeeper • Perform an initial review of all JCIDS proposals • Support provided by JFCOM, J6, J7, J8, FCB WGs • The Gatekeeper will determine: • Joint Potential Designator • JROC Interest • Joint Integration • Independent • Lead and supporting Functional Capabilities Boards • Formal Staffing begins after Gatekeeper decisions

  11. Chartered FCBs FCBs: * Milestone Decision Authority Co-chairs * Bring all stakeholders together for common review and issue resolution * Prioritize/assess capability gaps and proposals JROC: * Charters FCBs * Directs FCB efforts * Identifies the FCB lead Command & Control Focused Logistics Force Management Battlespace Awareness Maj Gen Simpson JFCOM J-8 RDML Harnitchek JS J-4 Ms Disbrow (SES) JS J-8 Brig Gen Dettmer JS J-2 Force Application Joint Training Force Protection Net-Centric RADM Brown JS J-6 Maj Gen Scott JS J-8 Maj Gen Catton JS J-7 Tri-chair Dr. Fridling (SES) JS J-8

  12. Functional Capabilities Board Responsibilities: • Ensure new capabilities are conceived and developed in joint warfighting context • Ensure JCIDS proposals are consistent with integrated joint force • Organize, analyze & prioritize capabilities proposals • Oversee development and update of Functional Concept(s) • Ensure integrated architectures reflect the functional area • Leverage full resources of the Department

  13. Services DIA Representative (Intelligence Supportability) Services Combatant Commanders USD (AT&L) USD (I) USecAF (Space) ASD NII/ DOD CIO USD (C) D, PA&E DIA Representative (Intelligence Supportability) Mission Requirements Board Oversight Body Comparison Functional Capabilities Board (FCB) Joint Requirements Panel (JRP) Joint Requirements Board (JRB) Joint Capabilities Board (JCB) Joint Requirements Oversight Council (JROC) Joint Requirements Oversight Council (JROC)

  14. JROC Interest All ACAT 1/1A programs and programs designated as JROC Interest Sponsor Validates & Approves JCIDS Staffing/Approval Process O-6 & Flag Staffing Certification Staffing Joint Integration ACAT 11 ands below that need interoperability/intel/munitions certification GateKeeper JCIDS Documents Independent No joint force affect or need for certification Appropriate MDA Co-Chairs FCB Functional Capability Boards Services CoCom Reps USD (AT&L) USD (I) USecAF (Space) ASD NII/ DOD CIO D, PA&E DIA Rep (Intel Supportability) Mission Review Board Exec Sec’y Other DoD Agencies as necessary Joint Capabilities Board & JROC JROC Interest

  15. Conclusions on JCIDS • Provides an enhanced methodology to identify and describe capabilities gaps and redundancies • Helps to prioritize capability proposals • Facilitates broad review of capability proposals independent of ACAT (Acquisition Category) • Engages the acquisition community early • Improves the identification of non-materiel alternatives • Improves collaboration with other departments and agencies


  17. JCIDS Documents • Initial Capabilities Document (ICD) • Identifies a capability gap or other deficiency • Describes evaluation of DOTMLPF approaches • Supports AoA, Concept Refinement and Milestone A • Not normally updated once approved • Capability Development Document (CDD) • Identifies operational performance attributes of proposed system • System specific, applies to single increment (in an evolutionary program) • Results from Technology Development and supports Milestone B • Updated or rewritten for subsequent increments • Capability Production Document (CPD) • Identifies production attributes for a single increment of a program • Prepared during System Development and Demonstration • Rewritten for each increment in a evolutionary program