Joint Deployment Process Owner

1
Joint Deployment Process Owner (JDPO)
COL Stan Hoskin, Chief, JDPO Division, J42 2002
Division Transportation Officer Course 21 June
2002
2
Agenda

• U.S. Joint Forces Command Overview
• Joint Deployment Process Owner (JDPO) link to
  Transformation
• Joint Deployment Process Improvement
• Quick Look Focus Team OEF Observations
• Wrap-up/Final Thoughts

3
USJFCOM Mission
U.S. Joint Forces Command executes the land and
maritime defense of the continental United States
in support of Homeland Security and, as the Chief
Advocate for Jointness, maximizes the Nations
future and present military capabilities, through
joint concept development and experimentation,
recommending joint requirements, advancing
interoperability, conducting joint training, and
providing ready continental U.S.-based forces and
capabilities to support other Commanders in
Chief, the Atlantic Theater, and domestic
requirements including Military Assistance to
Civil Authorities.
Evolving Role in Homeland Security
4
JFCOM Service Components
1.1 Million Soldiers, Sailors, Airmen, and
Marines

• Working w/ West Coast Forces
• Navy Third Fleet (San Diego)
• USMC I MEF (Camp Pendleton)
• Army I Corps HQ (Fort Lewis)

Subordinate Units
5
US Joint Forces Command Evolution
A series of changes to the U.S. Unified Command
Plan have resulted in one unified CINC as an
advocate for jointness with responsibility for
leading the transformation of the U.S. Armed
Forces

• 1993 UCP
• COCOM of CONUS(-) general purpose forces
• LANTCOM to USACOM
• Joint Training
• 1995 UCP
• Joint Integration
• Caribbean region to USSOUTHCOM
• 1997 UCP
• Joint Force Provider
• MSCA and MACDIS
• 1999 UCP
• Joint Experimentation JTF - Civil Support
• Redesignate as U.S. Joint Forces Command
• South Atlantic to SOUTHCOM/EUCOM
• Retained North Atlantic AOR ACLANT
• 2001 (9-11)
• HLS (Land Maritime CS)
• 2002 UCP
• HLS ? NORTHCOM

• An Expanded Charter
• Joint Force Trainer
• Joint Force Interoperability
• Joint Force Requirements
• Joint Force Provider
• Joint Force Experimentation
• PLUS
• Homeland Security / Defense

JFCOM Mission
6
Why Transform?

Peace
Conflict
War

• Some of the spectrum all of the time
• All of the spectrum some of the time

How do we get to full spectrum dominance?
All of the spectrum all of the time
Transformation
7
USJFCOM is the DOD Transformation Agent
USJFCOM designated as Executive Agent for
Transformation
USJFCOMs JDPO is the JPECs JDPI Transformation
Agent
Dominant Maneuver
Precision Engagement
Information Superiority
Full Spectrum Dominance
DOTMLPF
Innovation
Focused Logistics
Full Dimensional Protection
Transforming the joint deployment process to meet
joint operational requirements
8
JDPO Responsibilities DODD 5158.5

• Assigns CINC JFCOM these Executive Agent
  responsibilities / authorities to
• Ensure proper coordination among the DoD
  Components during deployment and redeployment
  process improvement initiatives.
• Provide recommendations to the SecDef, through
  the CJCS, regarding deployment and redeployment
  process improvements.
• Issue directives to other DoD Components and
  take action on behalf of the SecDef concerning
  deployment and redeployment process improvement
  initiatives, as specifically authorized by the
  SecDef through the CJCS.

Lead the collaborative efforts of the joint
planning and execution community (JPEC) to
improve the joint deployment and redeployment
processes.
9
Joint Deployment Process
Dynamic and iterative with many stakeholders
Origin to POE Installations, Units, Service
Components Supporting CINCs, Services, Defense
Agencies
POE to POD USTRANSCOM, Self-Deploying Forces
POD to Destination Theater CINC Service
Components
STRATEGIC MOBILITY TRIAD
STRATEGIC
OPERATIONAL TACTICAL
10
Major Pieces of Joint Deployment Process
Joint Deployment Process Phases (IAW JP 3-35)
Responsible Stakeholders By Phase (Phases are
iterative)
Supported Supporting Cmds
Supporting Commands USTC
USTC
Supported Command
Move to POE Conduct POE Operations Track
operational capabilities
Conduct POD Operations Receive Stage
Forces Prepare the Force Conduct Onward
Movement Conduct TAA Operations Complete Force
Integration Determine Report Operational
Capabilities
Analyze Mission Structure Forces Validate
Deployment Data Prepare the Force for
Mvmt Schedule Movement Assemble Marshal
Forces

• During joint deployment operations
• Vertically organized stakeholders
• Execute a horizontal work flow
• Resulting in predictable process seams

Synchronize Seams Joint Interoperability
Challenges
11
Cycle of Joint Deployment Process Activities
Joint Force Projection is not a one-time sequence
of activities --- it is an iterative cycle of
activities conducted until mission completion.
DEPLOYMENT
EMPLOYMENT
REDEPLOYMENT
CURRENT PROCESS AND ENABLERS DO NOT SUPPORT THE
COMBATANT COMMANDER'S NEED FOR RESPONSIVE, TIMELY
AND EFFICIENT MANAGEMENT OF CHANGE
12
JDPI Overview

• Where we were (Pre-ODS to Joint Endeavor)
• No doctrinal Joint Deployment Process
• No designated POC to manage / integrate
  improvements
• Lessons documented / not learned and applied
• Where we are (1997 to present)
• Joint Deployment / Redeployment Doctrine
  approved
• JDPO established with JDPI actions and
  initiatives
• Transformation activities (not linked / poor
  baselines)
• Where we are going JV 2020 (JIMP- JII)
• Developing enhanced Joint Deployment Process
• Aligning Core Competencies / developing
  baselines
• Applying synchronized Transformation activities

13
Mission Focus Functional / Technical Integration

• Functional JDPI (process and procedures)
• Deployment Planning and Execution
• Throughput
• Management of change (responsive METT-TC
  dynamics)
• Technical JDPI (applications and tools)
• AIS / AIT
• Visibility / Visualization / Simulation
• Enablers for functional process and procedures
• Integration driven by application of existing
  policies / lessons learned and emerging concepts
  / experiments ...
• Joint Vision 2020 Implementation Master Plan
• CJCSI 3170.01, Requirements Generation System
• CJCSI 3180.01 (DRAFT), "JROC Programmatic
  Process"
• Joint Integration and Interoperability (JII)
• JDPI Strategic and Implementation plans

DOTMLPF
Joint Warfighter Focus - Today and Tomorrow
14
Where We Are - Setting Conditions for Change

• Designated Process Owner -- USJFCOM is JDPO but
  inhibited by authority / resources to coordinate
  and direct DoD-wide JDPI
• Defining joint deployment process -- Joint
  deployment operational architecture
  (strategic-national thru tactical) -- not
  complete
• Establishing performance measures / metrics
  engaged in coordinating deployment equities to
  establish / define joint core competencies (JOA -
  JOF- JMAs / and UJTLs)
• Determining process baseline across DOTMLPF--
  coordinating / developing baseline (e.g. Joint
  Deployment Systems CRD M lane)
• Identifying / Addressing roadblocks --
  technical and cultural... lack of enterprise
  interoperability (e.g. Data standardization and
  stovepipe systems)
• Gathering resources fighting internal
  external (JDPO/JPEC assets) resource battle ---
  personnel, funds command support/priorities

15
Millennium Challenge 02

• The Joint Force Capabilities Register (JFCR) is a
  listing of capabilities, supported by standard
  data, available to Supported/Supporting CINC
  and/or component planners for type force
  selection to fulfill a mission task in response
  to a crisis. More specifically, it
• Is based on Joint Pub 3-33, Joint Force
  Capabilities, missions identified in the most
  current Defense Planning Guidance (DPG) or as
  approved by the (NCA), President and Secretary of
  Defense
• Is built and maintained by Service Force
  Providers to show as a minimum capabilities for
  early deployers those forces to be moved by air
  or organic lift with an Available to Load Date
  (ALD) of seven days from the first movement
• Lists details of capabilities at Unit Type Code
  (UTC) and provides visibility of those
  capabilities to the JPEC
• Is designed for rapid selection of service
  capabilities required to accomplish a stated
  mission in response to a NCA desire for military
  options.

16
Joint Force Projection 2010 FY 03 ACTD Candidate
Objective To provide the joint warfighter with a
suite of functional tools and applications to
conduct end-to-end joint deployment planning,
analysis and execution during joint force
projection operations.

• JFP 2010 Road-Ahead
• JDPO continues garnering support from C/S/As for
  ACTD prior to JROC vote in early Jun 02.
• The DUSD(ASC) issuance of the implementation
  directive to begin the ACTD.

17
JDS CRD Data Standardization

• JDS CRD
• JROC Memorandum 183-01 (15 Nov 01) designated
  USJFCOM as lead for JDS CRD development efforts
• Mid-Point IPR to JROC in Jun 02
• Final working group will follow in Aug-Sep 02
  time frame
• CRD submitted for formal JROC staffing in Dec 02
  
• Data Standardization
• Provide support to DISA in identification of
  deployment systems and reference tables for data
  standardization

18
CRD Development Schedule
JROC IPR
Working Group
Working Group
Working Group
Operational Concept
Develop IER/KPP
Staffing Revision
JROC Process
IER Matrix OV1/SV1
Draft CRD
Jul 02
Jan 02
Dec 02

• Development timeline reflects an ambitious
  schedule
• Successful development requires participation by
  C/S/As

19
CRD Joint Deployment Information Systems
Improvement
Leveraging Current Capabilities Preparing for
Future Technological Advances
CRD FOCUS
SOURCE CJCSI 3020.01
20
TC-AIMS II in the Joint Deployment Process
21
Current Environment - Multiple Efforts Not
Linked
JROC Strategic Topics
JOF / JOA / JMA's
JDPI
Joint Experimentation
Improved Joint Deployment Process requires
integrated actions in Joint Force Readiness and
Effective, Efficient Planning and Execution
22
Where We Are Going Integration of Efforts
JROC Strategic Topics
JOF / JOA / JMA's
Enabled JDPI Process
Joint Experimentation

Improved Joint Deployment Process through
aligned integrated DOTMLPF actions that
enhance Joint Force Readiness, Planning and
Execution
23
Where We Were - Recurring Lessons / Problems

• Restore Hope - Somalia
• - inaccurate source data multiple
  uncoordinated changes
• Joint Endeavor - Bosnia
• - poor synchronization
• - notional data used causing disconnects
  between units lift
• Hurricane Mitch - Honduras
• - lift assets based on inaccurate late
  requirements
• - joint interagency concept planning time
  excessive
• (execution required prior to transportation
  integration)
• Desert Thunder - Saudi Arabia / Kuwait
• - validation process too slow for
  rapid requirement
• (no validated TPFDD for early flow resulted in
  no ITV)
• Joint Guardian - Kosovo -
• - significant delay (4-7 days) in validating
  TPFDD

Continued problems in deployment planning and
early execution...
24
Quick Look Focus Team OEF Observations

• Joint Deployment Process
• Early SPECAT planning and lack of adherence to
  JOPES Orders process precluded execution planning
  by Supporting Commands
• Multiple RFFs and DEPORDs complicated the
  process excessive coordination times resulted in
  20 of movements past LAD when DEPORD published
• Priorities were not clearly communicated and
  changed frequently
• Education and training --- deficiencies noted at
  all levels
• Lack of complete understanding of integrated
  joint deployment planning and execution from
  strategic to tactical levels
• Lack of adherence to JOPES, CAP, and TPFDD
  processes caused confusion and delays (e.g. JOPES
  orders process, unrealistic RDDs/LADs,
  aggregation of PAX/cargo) -- gave perception the
  TPFDD is broken
• Infrastructure and systems
• Limited SIPRNET bandwidth caused slow
  responses--delayed CINC / Component updates of
  critical data

Fundamentally, nothing new
25
Joint Deployment Process - Crisis Response
COMBAT POWER
The TPFDD is complete after forces have
Redeployed
JRSOI
Concurrent Collaborative
Scheduled lift Arrival at POD
Dynamic,
Schedule Lift and Aggregate
TPFDD
process
iterative
Validate Sourced Requirements
Source Requirements
Staff DEPORD
Identify force requirements (UTCs) in the TPFDD
JOPES

• Big JOPES - Process
• Little JOPES - System

Develop RFF
ID Force Requirements
Process starts with Senior Leader DECISIONS
Crisis Response
26
JDP and Performance Measure Timeline
COMBAT POWER
Threshold / Objective for each action
Collaboration
JRSOI
Scheduled Lift Arrival at POD
Schedule Lift and Aggregate
Validate Sourced Requirements
Source Requirements
Staff DEPORD
Develop RFF
ID Force Requirements
S SMALL DEPLOYMENT (lt 2000 PAX) M MEDIUM
DEPLOYMENT (2000 5000 PAX) L LARGE DEPLOYMENT
(8000 PAX)
Crisis Response
Takeaway These should be goals for joint
deployment execution during contingency operations
27
JDP - Major Pieces That Are Broken
Joint Deployment Process Phases
Major Process Problems
Joint Deployment Process / Adherence to JOPES
procedures
Joint Deployment Training / Cold Start Exercises,
Leader Education - Awareness
Systems Interoperability / Systems not responsive
during CAP Execution

• Aggregation of Forces at POE
• ITV / TAV
• Lack of specific TTP

• Force Closure vs
• Transportation Closure
• ITV / TAV
• No systems to plan / execute JRSOI
• Means to coordinate Host Nation support
• Interagency / NGO and PVO coordination

• Reqs Generation (Force Sustain Packaging)
• Task Organize (Sourcing / Tailoring)
• Means for Concurrent Collaboration
• OPSEC / INFOCON
• ITV / TAV
• Data Standardization
• Discipline of Process / Procedures

• ITV/ TAV
• Deconfliction of Transportation Priorities
• Multiple Operations Thru Supporting Nodes
• Transportation Closure Planned vs Actual and
  Scheduled vs Loaded/ Arrives

The nature of operations (GWOT) has changed
joint deployment deficiencies have not.
28
OEF Force Provider / JOPES Lessons Learned

• Apportioned Plans (Level 4 TPFDD complete)
  improve initial response time. Select different
  COA and accept a time penalty to deploy.
• SPECAT planning imposes a time penalty in
  deployment response time.
• Senior Leader Military and Civilian Official
  decisions and expectations are part of the Big
  JOPES process. They must be communicated
  clearly to the Joint Planning Execution
  Community (JPEC).
• Emergent Force Deployments of units (BN size and
  smaller) can reasonably be accomplished in 12-18
  days (OEF historical data for first 30 days.)
• Critical Force Deployments of units (BN size and
  smaller) can be accomplished in 2-4 days with a
  1A2 Airlift Priority. (Recent Apache Battalion
  Deployment.)
• Technical improvements to the overall JOPES
  process and hardware are necessary and required.
  They will make the entire process smoother, but
  they will NOT produce quantum improvements in
  time required to deploy forces.

29
Recommendations for the Way Ahead

• Complete JDPI Initiatives from OEF
• Institutionalize corrective actions and
  integrate efforts
• Complete and implement process baseline
• Align all levels of war via Joint Deployment
  Operational Architecture (JDOA) and Joint
  Deployment Systems Capstone Requirements
  Document (JDS CRD)
• Improve performance measures / metrics
• Better define joint deployment tasks (UJTLs) and
  link to Joint Mission Areas / JV 2020 Desired
  Operational Capabilities
• Reduce technical roadblocks to improvement
• Data standardization, systems interoperability
• Revise Joint Deployment Process
• Leverage joint experimentation and joint
  training, align / integrate complementary Service
  action for a revised interoperable joint
  deployment process

These actions require DOTMLPF solutions
30
Way Ahead Institutionalize Process Change
Aligned with JV 2020 and Service visions
Enabler for DODs Transformation Plan and
complementary Command Initiatives
ASSESS- RECOMMEND JDPI
ASSESS JDPI
Combatant Commands Military Departments Defense
Agencies
Combatant Commands Military Departments Defense
Agencies
INTEGRATE JDPI
USJFCOM
DOTMLPF is the integration model that provides
the structured format for integrating JDPI
DOTMLPF is the assessment model that provides a
cross-functional assessment of potential changes
JOINT DEPLOYMENT TRIAD
TRANSCOM
JOINT STAFF
Transform joint deployment through process
improvement
31
Wrap-UpFinal Thoughts
UNCLASSIFIED

• Focus Team Conference representatives identified
  numerous deployment problems--most are recurring
  lessons recorded
• JFCOM is leading and managing JPECs JDPI efforts
• Progress is tracked through the Joint Deployment
  and Distribution Process Improvement database
• Near-term initiatives provide immediate relief to
  mission deficiencies
• Long-term recommendations enhance the process to
  enable full-spectrum operations

UNCLASSIFIED
32
Questions??? JDPO web page
http//www.jfcom.mil/jdpo
33
BACK-UP SLIDES
34
Roles and Responsibilities --- DoD Dir 5158.5

• Lead JPEC collaborative efforts
• Justify lack of resolution of JDPI issues to
  SecDef
• Ensure deploy / redeploy processes are analyzed
• Promote acquisition of technology solutions
• Include in any JDPI initiative, the training
  necessary

TRIAD

• Provide guidance to JDPO
• Ensure JDPI support NMS
• Review / approve JDPI affecting operational
  issues
• Review / forward to SecDef JDPI affecting
  Department policy

• Review activities,identify issues
• Advocate changes
• Coordinate / implement approved changes
• Assess feasibility of JDPI

• Identify trans-related JDPI to JDPO
• Provide DTS expertise to assist JDPO
• Assist JDPO thru functional process
  improvement, DTS analysis, deployment training
• Provide appropriate support from JICTRANS, JTCC,
  and JDTC

35
Revise Joint Deployment Process (1 of 3)

• Revise Joint Deployment Process
• Task Revise (and where needed reengineer) the
  joint deployment process / systems to meet the
  operational requirements of the JFC
• Goal Improved joint deployment process /
  systems that meet operational requirements,
  ensure effectiveness, and promote efficiency
  during execution of force projection operations
• Support Required DoD-wide commitment to
  leverage joint experimentation (JE) / ACTDs /
  JTEs to revise (and when needed reengineer) the
  joint deployment process / systems
• Lead Agent JFCOM JDPO coordinate / integrate
  all joint deployment process improvement
  activities (JE / ACTDs / JTEs)
• OSD provide oversight and thru ACTD / JTE
  programs
• Joint Staff J3 / J4 provide SME input as
  required
• Combatant Commands provide support as required
• Services provide and SME support as
  required

36
Revise Joint Deployment Process (2 of 3)

• Agile Transportation 21 ACTD
• Task Apply best commercial supply chain
  practices and scheduling technologies to improve
  the management and efficiency of the Defense
  Transportation System (DTS)
• Goal Provide DTS global situation awareness and
  cost effective lift to the unified commands and
  Services through improved mode determination and
  asset scheduling
• Support Required On-going project. DoD-wide
  commitment to ensure USTC success
• Combatant Command Sponsor USTC
• Lead Service USAF
• OSD provide ACTD oversight / support
• Joint Staff J3 / J4 provide SME input /
  support as required
• Combatant Commands provide execution support
  as required
• Services provide and execution support as
  required

37
Revise Joint Deployment Process (3 of 3)

• Joint Force Projection 2010 ACTD
• Task Revise (and where needed reengineer) the
  joint deployment process / systems to meet the
  future operational requirements of the JFC
  specifically in the areas of requirements
  generation and JRSOI. Implied task link w/ AT 21
  ACTD
• Goal A persistent collaborative environment
  with interoperable,
• user-friendly decision support tools and
  applications that provide a JFC with global
  deployment situational awareness and an improved
  capability to manage change, assess risk, and
  make decisions
• during joint force projection operations.
• Support Required DoD-wide commitment to approve
  and resource this FY 03 ACTD nomination
• Combatant Command Sponsor USJFCOM
• Lead Service USA (proposed)
• OSD provide ACTD oversight / support
• Joint Staff J3 / J4 provide SME input /
  support as required
• Combatant Commands provide execution
  support as required
• Services provide and execution support as
  required