Capability Area Management

1

• Capability Area Management
• for the MHS

2
Agenda

• Background DoD management systems
• Capability Portfolio Management
• Capability Area Management
• Current Status
• What this means may mean for you

3
Background

• Old times were hard
• Revolutionary war cost 14.8 M
• (not adjusted for inflation)

4
Background

• Just as hard now
• 500B fy 09 DoD budget
• 70B additional for War on Terror (partial)
• How is such a huge organization managed?

5
Background

• History of the Department
• Service autonomy
• Inter-Service rivalry (bombers vs carriers)
• Inter-Service incompatibility
• Aided and abetted by Congress
• Kennedy (Robert McNamara)
• Planning, programming and budgeting system (PPBS)
• Reagan
• Packard Commission (acquisition reform)
• Goldwater-Nichols

6
Background

• DoD management, Planning, Programming and
  Budgeting System (PPBS, McNamara, 1962)
• Before
• Existing base incremental improvements
• Service dominant, OSD lesser role in budget
• After focus on
• Strategic objectives and how to achieve them
  (prev. programs reassessed)
• Procedure for distributing resources among
  competing programs across DoD
• Planning and budgeting linked by programming

7
Background

• Goldwater-Nichols improved OSD/JS control
• Vice-chairman Joint Chiefs of Staff
• Chair of JROC (Joint Requirements Oversight
  Council)
• Oversee requirements process for all major
  defense acquisition programs
• Vice chair of Defense Acquisition Board (advised
  the Defense Acquisition Executive, DAE)
• Packard Commission
• PEO (Program Executive Officer) system
• PM (Program Manager) to PEO to SAE (Service
  Acquisition Executive) to DAE

8
Background

• Requirements Generation System (RGS)
• Service initiated
• Bottom up
• Not joint
• Rumsfeld Joint Capabilities Integration
  Development System (JCIDS)
• Joint Staff initiated
• Top down
• Supports
• Commonality
• Interoperability
• Jointness

9
Capability Based MethodologyRGS
JCIDS
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
10
Capability Portfolio Management

• Joint Staff developed Joint Capability Areas (22)
• High level capability category
• Functional
• Enduring, cross cutting, enable military
  operations
• Joint Logistics
• Operational
• Specific to a particular type of military
  activity
• Link to Combatant Commands
• Domain
• Unique to land, air, sea, space, information
• Joint Air Operations
• Institutional
• Non-warfighting
• Joint Force Management

11
Capability Portfolio Management

• Portfolio Management Experiments
• Joint Logistics
• Joint Command and Control
• Joint Net Centric Operations
• Battlespace Awareness
• Portfolio manager
• Managed capability areas within portfolio
• Advocate balanced set of capabilities
• Defined resource constraint
• Guidance to Services and Agencies consistent with
  Departmental planning guidance

12
Capability Portfolio Management

• Joint Logistics
• Supply Chain Operations
• Operational Engineering
• Force Health Protection
• Logistics Services
• Contingency Contracting

13
Capability Area Management

• Force Health Protection (DASD FHPR)
• Casualty Management
• Patient Movement
• Medical Logistics
• Surveillance and Preventive Medicine
• Command and Control
• Human Performance Enhancement

14
Capability Area Management

• Patient Movement (test case)
• Defined patient movement process
• Goal 100 visibility for condition and location
• Mapped personnel and medical information systems
• Determined overlaps and gaps
• Produced a program change proposal to reduce
  overlaps
• Program change proposal accepted
• Now working to execute

15
Capability Area Management

• Redundancies found included
• Multiple inpatient record systems
• GEMS
• SAMS
• AHLTA-T
• Different modules and capabilities
• For test case, a program change proposal (proof
  of concept)
• Integration of inpatient record systems
• Problem plan for migration of additional
  capabilities

16
Capability Area Management

• Program Review
• Issue team AF, Navy agree in concept, but
  non-concur for legitimate reasons
• Program Analysis and Evaluation (PAE)
• Concept good
• Make funding/transition issues good
• Joint Requirements Oversight Council, Deputys
  Advisory Working Group approve
• Deputy Secretary signs
• Make it work

17
Current Status

• The Test Case is successful
• OSD decides to convert the 4 Test Case areas to
  Capability Portfolio Management
• JCAs re-baselined from 22 to 9 same system for
  OSD as Joint Staff
• CPM areas superset of JCAs
• FHP caught in transition
• Previously in Joint Logistics
• Slated for movement to Force Support CPM
• Force Support CPM not stood up

18
Current Status

• FHP CAM now in Logistics CPM and Logistics JCA
• If Force Support CPM stood up, FHP will
  transition there under Health Readiness
• CAM responsibilities still apply
• Force health protection capabilities across the
  Department
• Define risks and tradespace
• what are the options in a fiscally constrained
  environment
• what are the risks for each option
• What is the best joint solution?

19
Current Status

• Analyze Department wide FHP acquisition programs
• condense when possible thru business case
  analysis to Service or Agency
• Suggest/direct new programs when gaps are
  identified and risk warrants closure
• Suggest program change proposals when necessary
• Elevate to CPM if necessary
• FCB, JCB, JROC and DAWG
• Input to GDF (Guidance for Development of the
  Force, old Strategic Planning Guidance)
• Much more specific than in past
• Justification for Service Medical Department
  programs

20
Impact on you

• Legacy non-joint programs may be at risk
• Eliminate multiple programs with same function
• More centralized oversight of Service and Agency
  acquisitions
• Joint perspective at project initiation