1 / 12

Acquiring Capabilities July 15, 2005

Acquiring Capabilities July 15, 2005. Dr. Glenn F. Lamartin Director, Defense Systems Office of the Under Secretary of Defense Acquisition, Technology and Logistics. Current Situation What We Need to Do Better. Requirements Adapting to changing conditions

aaralyn
Download Presentation

Acquiring Capabilities July 15, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Acquiring Capabilities July 15, 2005 Dr. Glenn F. Lamartin Director, Defense Systems Office of the Under Secretary of Defense Acquisition, Technology and Logistics

  2. Current SituationWhat We Need to Do Better Requirements • Adapting to changing conditions • Matching operational needs with solutions • Overcoming biases of Services and others • Moving to transform military Acquisition • Acquiring systems-of-systems • Making system decisions in a joint, mission context • Transitioning technology • Assessing complexity of new work and ability to perform it • Controlling schedule and cost • Passing operational tests • Ensuring a robust industrial base PPBES • Laying analytical foundation for budget • Aligning budgets with acquisition decisions Sustainment • Controlling O&S costs • Reducing logistics tails Personnel and Readiness • Treating people as a resource

  3. A Capabilities Approach to Acquisition • Extend focus beyond individual system acquisition • Apply a capabilities-based approach • Make decisions on systems within a capabilities context • Engineer the relationships across the set of systems that together satisfy the need • Synchronize the interaction among FoS/SoS to satisfy multiple capabilities • Influence other key Department processes • Shape strategic guidance • Inform development of joint concepts and requirements • Balance programming guidance

  4. DoD End-to-End Capabilities Based Planning Process Joint Staff / OSD Capability Area Reviews (CARs) • Refined concept • Analysis of Alternatives • Technology Strategy • Systems Engineering Plan • Strategic Planning Guidance • Defense Planning Scenarios • Family of Concepts • Transformation • Revise KPPs • Detailed design • System integration • DT&E/IOT&E • LRIP • IOT&E • FOT&E • Deploy-ment • Sustain-ment • Disposal • Affordable military-useful increment • Technology demonstrated • Initial KPPs Capabilities Based Assessment • Non-materiel solutions • Materiel solutions • S+T initiatives • Experimentation • Capabilities • Tasks • Attributes • Metrics • Gaps • Shortfalls • Redundancies • Risk areas • LRIP • FOT&E Full Rate Prod DR Concept Decision MS “A” MS “B” MS “C” Technology Development System Development Technology Development System Development Production CPD CDD Functional Area Analysis Functional Needs Analysis Functional Solutions Analysis Joint Concepts Analysis of Alternatives Technology Development Strategic Planning Guidance Develop Concept System Development CPD Production CDD ICD CPD CDD O&S Production Capability Based Assessment Incremental Development OSD (AT&L)- led Capability Roadmaps Army USMC Navy FCB Air Force COCOMs Services OSD/JCS COCOM OSD (AT&L) DIA OSD (PA&E) OSD (NII) SecDef OSD (AT&L, PA&E), Services and OSD (DOT&E), Joint Staff (JROC) Joint Requirements Oversight Council Opns & Spt Capabilities Definition Acquisition and Test Concept Refinement Strategy “as is” Roadmaps

  5. Acquisition Engagement Capability Based Acquisition Army Navy USMC FCB COCOMs Air Force OSD (AT&L) DIA OSD (NII) OSD (PA&E) Planning, Programming, Budgeting and Execution Capability Area Reviews (CARs) Full Rate Prod DR Concept Decision MS “A” MS “B” MS “C” Capabilities Based Assessment Technology Development System Development Technology Development System Development Production CPD CDD Functional Area Analysis Functional Needs Analysis Functional Solutions Analysis Strategic Planning Guidance Joint Concepts Analysis of Alternatives Technology Development System Development CPD Production CDD ICD O&S Production CPD CDD Incremental Development OSD/JCS COCOM Systems and Mission Integration Systems Acquisition Operational Support Capability Based Assessments (FAA, FNA, FSA) Demonstrate capabilities meet user needs Define Relationships with Related Capabilities, Architectures (e.g., GIG) Enterprise Assess portfolio performance (CAR) Identify alternatives; Trade cost, sched, perf SoS Integrate SoS; Assess Cost, Sched, Perf Determine system performance parameters and verification plans Assess system performance against capability needs System Components Identify incremental, system specifications Integrate and Test Develop, Test, and Assess Increments of Capability Systems Engineering

  6. Key Activity: Capability Area Reviews USD(AT&L), as DAE, leads reviews of select capability areas to: • Provide mission area context – from a top-down perspective • Implement capability-based methodology on provider side • Link policy, capability generation, acquisition, and budget processes • Identify joint solutions and added work to be done (across DOTMLPF) • Reveal need for management, engineering, and testing across an area • Help align individual program expectations • Provide basis to set metrics and gauge progress over time • Assess the cumulative effect of individual program decisions But…wide participation is essential

  7. Key Activity: Roadmaps and Roadmapping Roadmaps provide a framework for decision making – prompt discussion, inform decisions, and capture decisions made • Lay out Department’s strategic plan considering: • Materiel and non-materiel solutions • Capability that only exists at Family/System-of-Systems level • What to expect from each system • Cross-cutting management, engineering, and testing • Network enablers • Affordability • Nature of Roadmaps will vary by topic • Start with the “as is” and show where we want to go But… must balance decisions across capability areas

  8. Key Activity: System Decisions in Context Weapons: .50 cal/7.62 mm Guns 2.75” Rockets Hellfire Net Centric Warfare: IDM BFT Have Quick SATCOM SINCGARS JTRS (Cluster 1) Link-16 (w/JTRS) Supporting Platforms: C-17A C-130(J) C-5 Hosting Platforms LHA/D Replacing:OH-58D Air Complementary Platforms: AH-64 UH-60 CH-47 A2C2S Ground Complementary Platforms Land Warrior M-1 Tank M-2 Bradley Fire Support Stryker FCS ISR: JSTARS AWACS GPS AMPS ABCS DCGS-A GCSSA Armed Reconnaissance Helicopter Capability Area: FORCE APPLICATION Roadmaps: Army Aviation Modernization Plan MOSA Rating: Satisfactory Current schedule and performance support fielding Performance issues with interface Arrow to ARH denotes receiving other program’s technology or capability Arrow from ARH denotes technology or capability recipients from ARH Performance and schedule coordination required for future systems OSD DAES Rating: C S P Not Rated Fielded (Service rating *) SOLID DENOTES CURRENT SYSTEM DASH DENOTES FUTURE SYSTEM

  9. System-of-Systems (SoS) Systems Acquisition Functions • Align expectations of AT&L, the Joint Staff and the Services for joint capability to be fielded over time (requirements, etc) • Synchronize efforts/programs across the Services to produce the desired capabilities (e.g., development activities, testing) • Conduct systems engineering and integration across Service and joint programs to ensure interoperability • Develop and execute properly phased and focused test and evaluation plans for SoS components and overall joint capability • Establish mechanism for allocating resources among component programs and activities – including making needed tradeoffs • Coordinate activities in all the DOTMLPF areas, to create the enablers associated with fielding a capability in packages (hardware, software, training, spares, etc.) • Sustain capability over time

  10. SoS Example: Integrated Air and Missile DefenseChallenges 2010 Joint Engagement Zone • Single Integrated Air Picture • Combat ID • Integrated Fire Control • Automated Battle Management Aids

  11. SoS Example: Integrated Air and Missile DefenseRoadmap Capabilities Notional - for Illustrative Purposes Systems *Version 1

  12. Current Challenges • Plan for a budget constrained environment and impact on potential solutions – new vs. re-engineered vs. DOTMLPF • System complexity and interdependency is increasing – Family of Systems and System of Systems interdependencies • Balancing joint needs with cost and schedule • Demand for network centric capability drives higher levels of program coordination • Development of capabilities that do not fit well in current management structures • Effective application of systems engineering to streamline acquisition process and meet performance objectives • Maintaining an expert workforce, trained for the above challenges

More Related