O
T
F
N
T
E
H
W
S
E
I
M
'
L
L
H
E
T
D E F E
T
N
D
A
R
R
A
P
M
E
Y
D


A
U
C
N
I
I
R
T
E
E
M
D
A
S
F
T
O
A
T
S
E

## Deployment And Redeployment Operations

10 January 2018

## Preface 1.  Scope

This publication provides joint doctrine to plan, execute, and assess deployment and redeployment operations.

## 2.  Purpose

This publication has been prepared under the direction of the Chairman of the Joint Chiefs of Staff (CJCS).  It sets forth joint doctrine to govern the activities and performance of the Armed Forces of the United States in joint operations, and it provides considerations for military interaction with governmental and nongovernmental agencies, multinational forces, and other interorganizational partners.  It provides military guidance for the exercise of authority by combatant commanders and other joint force commanders (JFCs), and prescribes joint doctrine for operations and training.  It provides military guidance for use by the Armed Forces in preparing and executing their plans and orders.  It is not the intent of this publication to restrict the authority of the JFC from organizing the force and executing the mission in a manner the JFC deems most appropriate to ensure unity of effort in the accomplishment of objectives.

## 3.  Application

a.  Joint doctrine established in this publication applies to the Joint Staff, commanders of combatant commands, subordinate unified commands, joint task forces, subordinate components of these commands, the Services, and combat support agencies.

b.  The guidance in this publication is authoritative; as such, this doctrine will be followed except when, in the judgment of the commander, exceptional circumstances dictate otherwise.  If conflicts arise between the contents of this publication and the contents of Service publications, this publication will take precedence unless the CJCS, normally in coordination with the other members of the Joint Chiefs of Staff, has provided more current and specific guidance.  Commanders of forces operating as part of a multinational (alliance or coalition) military command should follow multinational doctrine and procedures ratified by the United States.  For doctrine and procedures not ratified by the US, commanders should evaluate and follow the multinational command's doctrine and procedures, where applicable and consistent with US law, regulations, and doctrine.

For the Chairman of the Joint Chiefs of Staff:


                                                                                    KEVIN D. SCOTT
                                                                                    Vice Admiral, USN
                                                                                    Director, Joint Force Development


## Intentionally Blank Dated 31 January 2013

-
Refines the distribution process owner and Global Distribution Synchronizer
into the Joint Deployment and Distribution Coordinator role in accordance with the Unified Command Plan.
-
Refines Adaptive Planning and Execution (APEX) overview.
-
Refines the Secretary of Defense (SecDef) role in Global Force Management
Allocation Plan process.

-
Expands combatant commanders roll in execution sourcing under global
force management allocation process.

-
Updates the Joint Deployment and Redeployment Process figure to reflect the
deployment or redeployment as the initiation point.

-
Updates functional combatant commands to remove global synchronizer and
replace with coordinating authority.

-
Expands asset visibility capabilities to include Global Combat Support
System-Joint and Integrated Data Environment/Global Transportation Network Convergence as both providing in-transit visibility.

-
Clarifies Title 10, Unite States Code, Section 162, SecDef direction to assign
and allocate forces.
-
Updates Military Planning and Execution Process figure to incorporate
theater distribution campaign plan under planning products.

-
Refines the deployment/redeployment planning and APEX processes.
-
Refines the combatant command roles and responsibilities in the movement
phase of the joint deployment and redeployment process.
-
Updates port of embarkation to reflect Military Surface Deployment and
Distribution Command no longer has deployment support teams.

-
Refines integration overview to highlight the importance and ongoing nature
of integration with the joint, reception, staging, onward movement, and
integration phase of deployment.

## Intentionally Blank Executive Summary Commander's Overview

- Discusses the use of global force management to assign, allocate, and
apportion joint forces.
- Outlines the joint deployment and redeployment processes. - Identifies the deployment and redeployment responsibilities, roles, and
relationships of individuals, commands, Services and agencies.
- Describes the planning phase of the deployment and redeployment process. - Addresses the activities taken to prepare forces to execute a
deployment/redeployment operation before actual movement.
- Describes the movement phase of the joint deployment and redeployment
process.
- Presents an overview of the final phase of deployment and redeployment,
joint reception, staging, onward movement, and integration.

## Overview


The deployment and redeployment of US forces in support of combatant commander (CCDR) requirements are a series of operational events enabled by logistics.  These activities are planned and executed by the supported and supporting commands, Services, National Guard Bureau, and Department of Defense (DOD) agencies.

Adaptive Planning and Execution
The Adaptive Planning and Execution (APEX) enterprise integrates the force and joint planning activities of the joint planning and execution community (JPEC) and facilitates the transition from planning to execution.

The APEX enterprise, via the military planning and execution process, has four operational activities:
situational awareness, planning, execution, and assessment.  The members of JPEC are continuously performing the operational activities and iteratively linking those activities with the planning and execution functions.

Global Force Management Global Force Management allows the Secretary of Defense (SecDef) to strategically manage the employment of the force among CCDRs.  It aligns force assignment, allocation, and apportionment methodologies in support of the Defense Strategy Review, joint force availability requirements, and joint force assessments.

Joint Deployment and Redeployment Processes The joint deployment and redeployment processes consist of four phases:  planning; predeployment/preredeployment activities; movement; and joint reception, staging, onward movement, and integration (JRSOI).  These phases are iterative and may occur simultaneously throughout an operation.

## Responsibilities

Secretary of Defense SecDef provides directive authority to the CCDRs for the planning and execution of military operations, to include deployment and redeployment operations, as directed by the President.

Chairman of the Joint Chiefs of Staff Chairman of the Joint Chiefs of Staff's responsibilities most directly related to deployment operations include the following:

- Prepares
integrated
plans
for
military
mobilization.
- Establishes procedures for the submission of
movement requirements.
- Prescribes a movement priority system in
agreement with uniform materiel movement and issue priority system that will ensure responsiveness to meet the needs of the CCDR.
- Advises SecDef of mobility support force
capabilities and assesses their impact on CCDR and DOD component requirements.
Combatant Commanders and Force Providers Supported CCDRs have three major responsibilities relative to deployment operations:

- Build a time-phased force and deployment
data (TPFDD) based on the concept of operations
and,
subsequently,
validate
movement requirements in the TPFDD after the unit refined movement data has been entered;
- Determine predeployment standards; and
- Balance and regulate the transportation flow.

## Responsibilities Of **Supporting Ccdrs**:

- Supporting missions of the joint force could
include sponsorship of en route basing or intransit staging areas (SAs), or provision of sustainment from theater stocks;
- Regardless of the supporting mission, the
primary task for supporting combatant commands (CCMDs) is to ensure the supported CCDR receives the timely and complete support needed to accomplish the mission.
- In addition to the supporting CCDR
responsibilities described above, a CCDR may also have additional responsibilities as a force provider (FP) of allocated forces.

Functional Combatant Commands

Functional CCDRs provide planning and assessment support to geographic combatant commanders to ensure the alignment and harmonization of campaign plans across area of responsibility and functional boundaries.

Normally, several functional CCMDs are involved in every phase of a joint operation.  Three functional CCMDs involved in deployment of the joint force are: US Special Operations Command, US Strategic Command, and United States Strategic Command (USTRANSCOM).

Military Departments and National Guard Bureau

The Military Departments organize, train, supply, equip, maintain, mobilize, account for, and provide administrative and logistics support (including Service-organic transportation) for their respective forces.  When acting as an FP, the Secretaries of the Military Departments coordinate directly with CCMDs, joint FPs, and the Joint Force Coordinator to develop recommended global sourcing solutions.  Each Service is responsible for administrative support and performance of transportation operations assigned by CCDRs at either their local shipping installations or throughout the theater.

## Planning


Deployment planning activities include all actions required for the deployment of forces up to the point of their employment.  It involves planning to move, receive, and integrate forces from origin to final destination.  Under the execution function of APEX, forces are allocated, sourced, and mobilized using readiness analysis.  Sustainment is requisitioned or pre-positioned and forces scheduled in the TPFDD.

Considerations of Operational Requirements

When conducting deployment planning, the following operational requirements should be considered:

- Existing distribution plans. - Threat environment. - Communications systems supporting visibility
of deployment operations.
- Training. - Infrastructure assessment. - Host-nation support. - Operational contract support. - Seabasing.

Deployment/Redeployment Planning and Adaptive Planning and Execution

APEX leverages a number of tools and processes. Information technology tools enable planner collaboration and access to shared authoritative data.  Complementary tools of the overall planning process provide planners flexible analytical techniques for framing problems and logically developing plans or orders to accomplish missions and objectives, more specifically the deployment and redeployment operations.

## Predeployment And Pre-Redeployment Activities


Predeployment and pre-redeployment activities are the second phase in the joint deployment and redeployment process.  A majority of these functions are performed at the unit level, linking the installation/base/unit deployment/redeployment efforts to the overall strategic movement.

Deployment Prepare the Force Activities

Regardless of the deployment timeline, a myriad of predeployment activities must be accomplished to deploy the force with their required equipment and supplies. Deployment timelines will dictate available time to conduct prepare the force activities, which include: activating deployment and command and control (C2) support organizations, conducting movement and support meetings, developing unit deployment lists and identifying shipping/handling requirements, and conducting required training.

Schedule Movement for Deployment

Movement scheduling is an iterative process done at every level of supported and supporting commands to transport, move, or deploy the right forces (unitrelated personnel and equipment) and sustainment (non-unit-related personnel, supplies, and equipment) to the right place at the right time. Schedule movement consists of five activities:

- Receive strategic movement schedule. - Receive/assess movement and lift schedule. - Receive port calls. - Confirm movement clearances. - Build and publish schedule of events.

Assemble and Marshal Forces for Deployment

Assembly and marshalling involve bringing together personnel, supplies, and equipment in preparation for final movement to the port of debarkation (POD).  It comprises four activities:

- Assemble personnel and cargo. - Conduct unit inspection, load equipment, and
prepare.
- Sequence loads. - Establish support organization at the port of
embarkation (POE).

Redeployment Prepare the Force Activities

A successful redeployment requires the planning and execution of "prepare the force" activities similar to those used in deployments.  The execution of these pre-redeployment activities will not be identical to deployment activities due to the operational environment, available resources, and the force structure of the redeploying units.  As such, procedures and unit level activities may vary from those performed during a deployment but these activities require detailed planning for a successful redeployment operation.  Redeployment prepare the force activities also has a unique sixth activity, complete equipment disposition actions.

Schedule Movement for Redeployment The five schedule movement activities discussed for deployment are also applicable to redeployment.  Normally, notional redeployment TPFDDs are developed during redeployment planning and updated and refined during execution as the redeployment window approaches.

Assemble and Marshal Forces for Redeployment These redeployment activities are the same as those performed during deployment and may require additional time and locations.  There is also an additional redeployment activity: prepare and conduct customs/agricultural inspections.

## Movement


The movement phase of the joint deployment and redeployment process includes self-deploying forces and forces requiring lift support and is composed of movement from origin to POE, POE operations, and movement from the POE to POD. However, for joint deployment to produce a seamless, end-to-end deployment movement process, consideration should be given to movement that extends beyond the POD.

Movement Considerations During deployment or redeployment, forces requiring movement comprise three general categories: self-deploying forces, forces requiring intertheater and intratheater common-user airlift support, and unit movements involving a combination of self-deployment and common-user airlift support.

Movement Control Movement control coordinates transportation resources to enhance combat effectiveness and meet the deployment/redeployment and sustainment priorities of the supported CCDR.  Effective movement control during deployment operations provides the joint force commander (JFC) with the capability to monitor and manage movement execution and adjust the flow of forces and materiel as necessary.  It provides for mechanisms to coordinate and deconflict movements and priorities for limited road space, constrained common-user airlift assets, and cross boundary/activities.

Movement
Validated movement requirements developed during the deployment planning phase and scheduled for movement during predeployment activities phase are moved by some mode of transportation from point of origin to designated aerial port of embarkation (APOE)/seaport of embarkation (SPOE) (when not co-located).  The supported CCMD selects the APOE/SPOE as a part of the validation process in coordination with its components, USTRANSCOM, and FPs outside the continental US.  APOEs/SPOEs are selected by the supported CCMD in coordination with its components, FPs, and USTRANSCOM. Airlift and sealift schedules are prepared by USTRANSCOM and coordinated with the supported CCMD.
Force Visibility
Visibility of deploying forces and materiel is established through the logistics management construct of asset visibility (AV) and the Global Command and Control System-Joint (GCCS-J) common operational picture.  AV is possible through integration of the capabilities provided by automatic identification technology; in-transit visibility; and the information systems and decision support tools comprising the Integrated Data Environment/Global Transportation
Network
Convergence,
Global
Combat Support System-Joint, single mobility system, and the Web Scheduling and Movement subsystem of the Joint Operation Planning and Execution System.  Control of the deployment and redeployment processes is exercised through the C2 capabilities of GCCS-J.
Redeployment
Movement in support of redeployment relocates forces to support a new mission in another operational area (OA) or to return them to their home or demobilization station.

## Joint Reception, Staging, Onward Movement, And Integration


The JRSOI phase of the deployment/redeployment process facilitates the transition between the execution functions of deployment and employment.


The four segments of JRSOI are:
- Reception operations include all those functions
required to receive and clear personnel, equipment, and materiel through the POD.
- Staging assembles, temporarily holds, and
organizes arriving personnel, equipment, and materiel into forces and capabilities and prepares them for onward movement, tactical operations, or Service reintegration.
- Onward movement is the process of moving
forces, capabilities, and accompanying materiel from reception facilities, marshalling areas, and SAs to tactical assembly areas (TAAs) and/or OAs or onward from the POD or other reception areas to the home/demobilization station.
- Integration is the synchronized transfer of
capabilities into an operational commander's force prior to mission execution or back to the component/Service.
There are three overarching principles of JRSOI: unity of command, synchronization, and balance.

Principles of Joint Reception, Staging, Onward Movement, and Integration Elements of Joint Reception, Staging, Onward Movement, and Integration JRSOI relies on the essential elements of communication systems, force protection, and support organizations and structures to achieve unity of command, synchronization, and balance.

Reception Reception is the process of receiving, off-loading, marshalling, and transporting of personnel, equipment, and materiel from strategic and/or intratheater deployment phase to a sea, air, or surface transportation POD to the marshalling area.

Staging Regardless of where staging occurs, the activities associated with staging will generally include assembling, temporary holding, and organizing of arriving personnel, equipment, and materiel into units and forces and preparing them for onward movement and employment by the JFC.  During staging, deploying forces have limited mission capability and may not be self-sustainable.  The CCDR should provide facilities, sustainment, life support, and protection until deploying units regain their combat or mission capability.

Onward Movement Onward movement is the process of moving forces and sustainment from reception facilities and marshalling or SAs to TAAs or other operating areas.  Rail, road, inland or coastal waterway, and/or air can be used to accomplish this movement as may intra-theater lift.  Challenges associated with onward movement during a deployment or redeployment to a new OA may include establishing distribution networks, limited line of communications (LOC) capacity, degraded LOC conditions, the potential for enemy interdiction, and reporting and movement control procedures.

Integration During deployment or redeployment to a new OA, integration is the synchronized transfer of missionready forces and capabilities into the CCDR's force and, based on the complexity of the operation, may take hours or days to complete.  The complexity and time required for integration depends on the size, contingency conditions, coordination and planning, C2 communications, and security available to manage the deploying or redeploying force. Integration is complete when the receiving commander establishes C2 over the arriving unit and the unit is capable of performing its assigned mission.

## Conclusion This Publication Provides Joint Doctrine To Plan, Execute, And Assess Deployment And Redeployment Operations.


## Intentionally Blank Chapter I Overview 1.  Introduction

a.  The US employs the four instruments of national power (diplomatic, informational, military, and economic) to achieve national strategic objectives.  The military instrument's role increases relative to the other instruments as the need to compel an adversary through force increases.  Military efforts focus on fielding modular, adaptive forces that can be employed across the range of military operations.  Deployment and redeployment operations enable the projection of the military instrument of national power.  Joint forces deploy in support of ongoing operations and theater and functional campaign plan activities.
b.  The deployment and redeployment of US forces in support of combatant commander (CCDR) requirements are a series of operational events enabled by logistics. These activities are planned and executed by both the supported and supporting commands, Services, National Guard Bureau (NGB), and Department of Defense (DOD) agencies. The capability to deploy forces to the operational area (OA) and rapidly integrate them into the joint force, as directed by the joint force commander (JFC), is essential.  Mission requirements determine the scope, duration, and scale of deployment and redeployment operations.  These operations involve the integrated complementary efforts of numerous commands, Services, agencies, and processes, and as such, unity of effort is required for effective and efficient mission accomplishment.

## 2.  Adaptive Planning And Execution

The Adaptive Planning and Execution (APEX) enterprise (Figure I-1) integrates the force and joint planning activities of the joint planning and execution community (JPEC)
and facilitates the transition from planning to execution.  APEX operational activities and functions span many organizations at all levels of the chain of command.  Collaboration among the supported and supporting commands, Services, and other organizations is an essential element of APEX to achieve unified action.  APEX informs the entire chain of command, including the President and Secretary of Defense (SecDef), facilitating informed decisions on how, when, and where to employ the military.  APEX is applicable across the range of military operations to plan and execute military activities to achieve the policy objectives outlined in the National Security Strategy and National Military Strategy. APEX provides the process, structure, reports, plans, and orders that orchestrate the employment of the military instrument of national power.  In accordance with (IAW) SecDef directive, APEX is used for planning and executing all deployment and redeployment operations.

a.  The APEX enterprise, via the military planning and execution process (Figure I-2), has four operational activities: situational awareness, planning, execution, and assessment. The members of JPEC are continuously performing the operational activities and iteratively linking those activities with the planning and execution functions.  When performing the planning functions, JPEC may use problem-solving techniques adapted for

## Adaptive Planning And Execution Enterprise

Updates to Strategic Guidance based on common understanding of the dynamics of the situation, approach, resources, costs, and risks.

military planning and execution.  The joint planning process (JPP) is the technique used in performing APEX functions.  The JPP utilizes a specific framework to accomplish the common activities needed to plan missions across the range of military operations.  It

## Military Planning And Execution Process

identifies the required military capabilities and timelines that set the framework for deployment/redeployment planning.  It applies to both supported and supporting JFCs and to component commanders when the components participate in joint planning.  This facilitates interaction between the commander, staff, and subordinate headquarters (HQ) throughout planning.  The JPP helps commanders and their staffs organize their planning activities, understand the mission and commander's intent, and develop effective plans and orders.  This process applies to planning within the context of the responsibilities specified by Chairman of the Joint Chiefs of Staff Manuals (CJCSMs) 3122 and 3130 series. Furthermore, the JPP supports deployment and redeployment planning after the Chairman of the Joint Chiefs of Staff (CJCS), at the direction of the President or SecDef, issues the execute order.  In common application, the JPP proceeds according to planning milestones and other requirements established by the commanders at various levels.  However, the CJCSM 3122 and 3130 series specify JPEC milestones, deliverables, and interaction points for plans developed IAW APEX guidelines.
b.  The deployment and redeployment execution functions are linked to five other execution functions (allocation, mobilization, distribution, employment, and demobilization).  Layered across the planning and execution functions are the global force management (GFM) processes of assignment, allocation, and apportionment.  GFM provides the risk and resource informed distribution of forces to the CCDRs.
c.  APEX incorporates initiatives (i.e., levels of planning detail, the requirement for continuous and iterative informal dialogue between civilian and military leaders, continuous SecDef assessments, and the use of collaboration technology) to provide better options throughout planning and execution and promote increased agility throughout deployment and redeployment.

For more information on APEX, see CJCS Guide 3130, Adaptive Planning and Execution Overview and Policy Framework.

## 3.  Global Force Management

a.  GFM allows SecDef to strategically manage the employment of the force among CCDRs.  It aligns force assignment, allocation, and apportionment methodologies in support of the Defense Strategy Review, joint force availability requirements, and joint force assessments.

(1)  **Assignment.**  By statute, the Secretaries of the Military Departments assign forces to CCDRs as directed by SecDef to perform missions assigned to those commands. SecDef promulgates this direction via the assignment tables communicated in the Global Force Management Implementation Guidance (GFMIG) in even years and Forces For Unified Commands Memorandum ("Forces For") in odd years.  The Secretaries of the Military Departments then identify the actual units to satisfy SecDef's direction in the assignment tables.  Those forces henceforth become "assigned" to that combatant command (CCMD) and the CCDR exercises combatant command (command authority) (COCOM) over them.

(2)  **Allocation.**  SecDef has the authority to allocate forces between CCDRs.  The allocation process temporarily adjusts the distribution of forces among the CCDRs to meet force requirements in support of current operations and campaign plans to mitigate nearterm military and strategic risk.  SecDef publishes decisions to allocate forces in the CJCS annual deployment order (DEPORD) (i.e., the Global Force Management Allocation Plan
[GFMAP] and its associated annexes), as well as periodic modifications to the base plan.
CCDRs usually exercise operational control (OPCON) over allocated forces; however, SecDef will specify the command relationship the gaining CCDR will exercise and the losing CCDR will relinquish.
(3)  **Apportionment.**  Forces are apportioned quarterly by the CJCS to provide an estimate of the Military Departments' capacity to generate capabilities that can reasonably be expected to be made available along general timelines.  This estimate informs and shapes CCDR resource-informed planning but does not identify the actual forces that may be allocated for use if a plan transitions to execution.  Apportionment is dependent on the number of operational forces, the readiness and availability of the forces, and the number of forces employed globally and serves as the starting point for planning.
Further discussion of the GFM processes can be found in the GFMIG; CJCSM 3130.06, (U) Global Force Management Allocation Policies and Procedures; CJCSM 3122.02, Joint Operation Planning and Execution System (JOPES) Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution); CJCS Guide
3130, Adaptive Planning and Execution Overview and Policy Framework; and Joint Publication (JP) 5-0, Joint Planning.

b.  **Force Sourcing.**  Within GFM, there are three levels of matching forces to requirements, depending upon the end state required: identification of preferred forces, contingency sourcing, and execution sourcing.

(1)  **Preferred Force Identification.**  Preferred forces are forces that are identified as planning assumptions by the supported CCDR to continue employment, sustainment, and transportation planning and to assess risk.  Both preferred force identification and contingency sourcing are planning assumptions only and do not indicate that these forces will be contingency or execution sourced.

(2)  **Contingency Sourcing.**  Contingency sourcing entails the Joint Force Coordinator and joint force providers (JFPs) identifying forces that meet sourcing guidance for plans on a specific date, which provides a snapshot depiction of potential sourcing.  This informs senior leadership of the sourcing feasibility and enables further transportation feasibility.

(3)  **Execution Sourcing.**  Execution-sourced forces are identified and recommended by the JFPs, reviewed through the GFM allocation process, and become sourced when approved by SecDef for the execution of an approved operation or potential/imminent execution of an operation plan (OPLAN) or exercise.  CCDRs may task their assigned forces to execute missions in support of operations and other military activities the CCDR has authority to execute.  If additional forces are needed, CCDRs will request forces IAW the GFM allocation process.

## 4.  Joint Deployment And Redeployment Processes

a.  The joint deployment and redeployment processes consist of four phases:
planning; predeployment/pre-redeployment activities; movement; and joint reception, staging, onward movement, and integration (JRSOI).  Both processes are similar; however, each has unique characteristics.  See Figure I-3 for a depiction of the phases. These phases are iterative and may occur simultaneously throughout an operation.

## Joint Deployment And Redeployment Processes

(1)  **Planning** is the first phase of the process.  The planning phase occurs throughout the entire process and occurs during both the planning and execution functions of APEX.

(2)  **Predeployment activities** are actions taken by the JPEC, before movement, to prepare to execute a deployment or redeployment operation.  This includes training, organizing, and equipping the force to be able to perform the mission specified in the force requirement.

(3)  **Movement** includes the activities to physically move joint forces from origin to destination.  It includes movement from origin to port of embarkation (POE); activities at the POE; POE to port of debarkation (POD), including movement and transit through intermediate locations as required; and from POD to final destination.

(4)  **JRSOI,** the final phase, is the essential process that transitions deploying or redeploying forces, consisting of personnel, equipment, and materiel arriving in theater, into forces capable of meeting the CCDR's operational requirements or completes the redeployment of forces to home or demobilization station as a result of end-of-mission or rotation.

## B.  Deployment

(1)  **Deployment operations** are the activities required to plan, prepare, and move forces and materiel from home station to a destination to employ an operational capability required to execute a mission.  The focus of these operations is to globally position forces in time to conduct military activities, including campaigns and major operations, and to respond to other contingencies.
(2)  **Deployment planning and execution.**  Deployment planning and execution decisions are based on the anticipated operational environment (OE) to be encountered in the OA.  Understanding the OE helps commanders anticipate the results of various friendly, adversary, and neutral actions and how they impact operational depth and reach, as well as mission accomplishment.

## C.  Redeployment

(1)  Redeployment is the transfer of deployed forces and accompanying materiel from one OA to support another JFC's operational requirements within a new OA or home/demobilization station as a result of end-of-mission or rotation.  Similar to deployment operations, **redeployment operations** are the sum of activities required to plan, prepare, and move forces and accompanying materiel from origin to destinations within a new OA or to home station to achieve the operational status required to execute a mission or demobilize.

(2)  Redeployment planning and execution.  Like deployment operations, redeployment planning decisions are based on the OE at the time of redeployment.  The supported geographic combatant commander (GCC) is responsible for redeployment planning in the area of responsibility (AOR).  This planning should be considered at the outset of an operation and continually refined as the operation matures.  The individual activities within each phase of redeployment are similar to those described in the deployment process; however, significant differences may exist during the JRSOI phase. These distinctions and the command relationships during redeployment are addressed later in this publication.

## D.  **Strategic Mobility**

(1)  Strategic mobility is the capability to deploy and sustain military forces worldwide in support of national strategy.  Beyond the intrinsic capability of some US
forces to self-deploy, the bulk of our nation's strategic mobility requirements are met through common-user sealift, common-user airlift, and pre-positioned stocks, known as the strategic mobility triad shown in Figure I-4.

(2)  **Strategic Mobility Triad.**  Successful deployment and redeployment of forces and capabilities in military operations depends on sufficient port throughput capacity coupled with the availability of sufficient mobility assets to rapidly deploy operational forces, sustain them as long as necessary to meet US military objectives, and reconstitute and redeploy them to meet changing mission requirements or return to home and/or demobilization stations upon completion of their mission.  To meet this challenge, the

## The Strategic Mobility Triad

United States Transportation Command's (USTRANSCOM's) transportation component commands (TCCs) (Air Mobility Command [AMC], Military Sealift Command [MSC], and Military Surface Deployment and Distribution Command [SDDC]) exercise command and control (C2) of USTRANSCOM's assigned and allocated forces, coordinates transportation assets for use by all DOD elements and, as authorized, other United States Government (USG) departments and agencies or other approved users.  Deployment operations normally involve a combination of land (road and rail), sea (including inland waterways), and air movement augmented, as necessary, by pre-positioned assets. USTRANSCOM must balance cost-effective options with operational and strategic viability for the JFC.  Transportation solutions must be effective, ensuring on-time delivery of forces and materiel to the right place at the right time.

(a)  **Common-User Airlift.**  The pool of common-user airlift consists of designated airlift assets from some or all of the following sources:  Active Component and Reserve Component (RC), the Civil Reserve Air Fleet (CRAF) when activated, contracted commercial assets, and foreign military or civil carriers (either donated or under contract).
For more information on common-user airlift, see JP 3-17, Air Mobility Operations.

(b)  **Common-User Sealift.**  Sealift forces are those militarily useful ships available to DOD to execute the sealift requirements of the Defense Transportation System (DTS) across the range of military operations.  Also known as "common-user shipping," these ships transport cargo for one or more Services and other USG departments and agencies, as authorized, from one seaport to another, to a sea base, or to a location at sea in the OA pending a decision to move the embarked cargo ashore.  The sealift force is composed of vessels from some or all of the following sources:  MSC government-owned or -controlled vessels; government-owned reserve vessels from the Maritime Administration Ready Reserve Force (MARAD RRF); US privately owned and operated commercial vessels; US privately owned, foreign flag commercial vessels; and foreignowned and -operated commercial vessels, including ships made available through the Voluntary Intermodal Sealift Agreement (VISA) and through an allied agreement.  With respect to sealift, Commander, United States Transportation Command
(CDRUSTRANSCOM), is delegated authority to procure commercial transportation services and, with the approval of SecDef, to activate the MARAD RRF and all three stages of VISA.

For more information on common-user sealift, see JP 4-01.2, Sealift Support to Joint Operations.

(c)  Pre-positioned equipment and supply programs are both land- and seabased.  They are critical programs for reducing closure times of combat and support forces needed in the early stages of a contingency.  They also contribute significantly to reducing demands on the DTS.

For more information on pre-positioned stocks, see JP 4-01, The Defense Transportation System, *and JP 4-01.2,* Sealift Support to Joint Operations.

(3)  **Other mobility considerations.**  Other transportation resources may be available to a CCDR to support deployment operations that do not fit within the context of the strategic mobility triad.  As proven in operations in Afghanistan, land transportation may augment traditional strategic mobility capabilities.  Land transportation may include road and/or rail modes in areas where there is limited air or sea port infrastructure to meet the CCDR's requirements.  This intratheater mode may be effective in delivering forces and sustainment to support the CCDR's mission.
e.  **Force Visibility.**  Resetting the force with a focus on restoring contingency surge response readiness in a highly resource-constrained environment is an iterative process. DOD senior leaders make decisions that consider the demand for forces to achieve campaign objectives and the need to maintain a pool of ready forces to meet surge demand during crisis.  This requires a global view of the force that includes current force inventory and commitment, availability and readiness, and the ability to discern status changes. Force visibility provides the current and accurate status of forces at the strategic and operational level, their current mission, future missions, location, mission priority, and readiness status.  Force visibility provides information on the location, operating tempo, assets, and sustainment requirements of a force as part of an overall capability for a JFC. Force visibility integrates operations and logistics information, facilitates GFM, and enhances the capability of the entire JPEC to adapt rapidly to unforeseen events, to respond and ensure capability delivery.  Force visibility enhances situational awareness and is required to support force sourcing, allocation, and assignment of forces; force position; sustainment forecasting and delivery; and forecasting for future force requirements.  Force visibility is achieved through effective force and phase planning for contingencies and crises, detailed deployment planning, and sound reporting procedures.  Within force visibility are the following:
(1)  **Asset visibility (AV) is a component of force visibility.**  AV provides commanders and planners with timely and accurate information on the location, movement, status, and identity of units, personnel, equipment (maintenance and retrograde actions), and supplies by class of supply, nomenclature, and unit during deployment operations.  AV
capability is in the Global Combat Support System-Joint (GCSS-J) family of systems and the Integrated Data Environment/Global Transportation Network Convergence (IGC). Both include in-transit visibility (ITV) over equipment, supplies, or personnel.
(2)  **ITV is a subcomponent of AV.**  When applied to an operation, ITV provides visibility of deploying and redeploying forces, as well as sustainment en route to an operation or a unit.  ITV preserves the link between the in-transit force and that force's mission within an operation phase through the force requirement number.  ITV can be divided into levels of visibility:  force movements associated with a specific operation; force movements for a specific phase, mission, and OA/destination; the movements of a force or unit as a capability with a specific mission; visibility of a lift mission; and in the box or item visibility.  Movement of all non-unit personnel, equipment, and supplies, to include contractors authorized to accompany the force (CAAF) and other non-DOD lift requestors, and retrograde actions will generally not have transportation and item-level visibility unless they are included in time-phased force and deployment data (TPFDD). Patient movement ITV is documented utilizing the United States Transportation Command Regulating and Command and Control Evacuation System (TRAC2ES).
For more information on force visibility, see Chapter V, "Movement," and JP 4-01, The Defense Transportation System.

## Chapter Ii Responsibilities

"All over the ship the tension that had been slowly building up since our departure was now approaching its climax.  Even the Yellow Sea rushing past the ship's sides seemed to bespeak the urgency of our mission.  That night, about half past two, I took a turn around the deck.  The ship was blacked out from stem to stern. At their posts and battle stations the crew members were alert and silent, no longer exchanging the customary banter.  At the bow I stood listening to the rush of the sea and watched the fiery sparklets of phosphorescence as the dark ship plowed toward the target, the armada of other craft converging on the same area, all now past the point of no return.  Within five hours, 40,000 men would act boldly, in hope that 100,000 others manning the thin defense lines in South Korea would not die.  I alone was responsible for tomorrow, and if I failed, the dreadful results would rest on judgment day against my soul."

## 1.  General

a.  This chapter identifies the deployment and redeployment responsibilities, roles, and relationships of the individuals, commands, Services, and agencies involved in deployment and redeployment operations.

b.  Basic responsibilities for commands and entities involved in joint deployment operations are outlined in JP 1*, Doctrine for the Armed Forces of the United States;* JP
3-0, *Joint Operations;* and JP 4-01, *The Defense Transportation System.*  Clearly articulating responsibilities is the first step in fully synchronized and coordinated deployment operations supporting the range of military operations.

## 2.  Secretary Of Defense

Title 10, United States Code (USC), authorizes SecDef to act as the principal assistant to the President in all matters relating to DOD.  Under that authority, and with the authority of the President, SecDef provides directive authority to the CCDRs for the planning and execution of military operations, to include deployment and redeployment operations, as directed by the President.

a.  Under the authority of Title 10, USC, Section 162, SecDef directs the Secretaries of the Military Departments to assign and allocate specified forces under their jurisdiction to CCDRs or the Commander, United States Element North American Aerospace Defense Command, to perform missions assigned to those commands.  SecDef fulfills these responsibilities through procedures outlined in the GFMIG.
b.  Under Secretary of Defense for Personnel and Readiness (USD[P&R]).  Per Title
10, USC, Section 136, USD(P&R) is responsible, subject to the authority, direction, and control of SecDef, for the monitoring of the operating and personnel tempo of the US Armed Forces.  USD(P&R) establishes uniform standards within DOD for the terminology and policies relating to deployment of unit and personnel away from their assigned duty stations (including the length of time units or personnel may be away for such a deployment) and establishes uniform reporting systems for tracking deployments.

## 3.  Chairman Of The Joint Chiefs Of Staff

The CJCS functions under the authority, direction, and control of the President and SecDef.  The CJCS is the principal military advisor to the President, the National Security Council, the Homeland Security Council, and SecDef.  The CJCS heads the Joint Chiefs of Staff but does not exercise military command over them or any of the US Armed Forces.  The CJCS's responsibilities most directly related to deployment operations include the following:

a.  Prepares integrated plans for military mobilization.
b.  Establishes procedures (in coordination with the Deputy Assistant Secretary of Defense [Transportation Policy], the Secretaries of the Military Departments, and the Defense Logistics Agency [DLA]) for the submission of movement requirements by DOD user components to USTRANSCOM and for the submission of evaluated requirements and capabilities by USTRANSCOM and the TCCs to the CJCS.

c.  Prescribes a movement priority system in agreement with uniform materiel movement and issue priority system that will ensure responsiveness to meet the needs of the CCDR.

d.  Advises SecDef of mobility support force capabilities and assesses their impact on CCDR and DOD component requirements.
e.  Assigns movement priorities in support of DOD components based upon capabilities reported by USTRANSCOM.

f.  Serves as the joint deployment trainer through the Joint Deployment Training Center.  Develops, implements, monitors, and assesses joint education and training programs to improve deployment and redeployment planning and execution.

g.  Ensures deployment and redeployment planning and execution are assessed during all joint force operations, as well as CJCS- and CCMD-sponsored joint exercises.

## H.  Joint Staff (Js) Responsibilities:

(1)  The Director, Joint Staff (DJS), supervises and provides guidance to the directors of the JS directorates and ensures their effective coordination with the Office of the Secretary of Defense (OSD).  With respect to deployment and redeployment operations, DJS chairs the Global Force Management Board (GFMB).  The GFMB is a general officer-/flag officer-level body organized by the JS to provide senior DOD
leadership the means to assess operational effects of force management decisions and implement strategic planning guidance.

(2)  Joint Staff J-1 [Manpower and Personnel Directorate] validates CCMD joint manning documents joint individual augmentation requirements against criteria prescribed in the GFMIG and forwards the validated requirements to Joint Staff J-3 [Operations Directorate] for a sourcing solution development.

(3)  Joint Staff J-2 [Intelligence Directorate] provides direct intelligence support to satisfy SecDef and the CJCS's requirements.  JS J-2 leads the DOD-level intelligence planning process and its integration into APEX.  JS J-2 and the Defense Intelligence Agency (DIA) produce finished intelligence products in support of the joint intelligence preparation of the operational environment (JIPOE) processes.

(4)  JS J-3 assists the CJCS in carrying out responsibilities as the principal military advisor to the President and SecDef by developing and providing guidance to the CCMDs and relaying communications between the President, SecDef, and CCDRs regarding current operations, plans, and readiness.

(a)  Orders.  CJCS directs JS J-3 to develop, coordinate, and prepare APEX
or joint operation orders (OPORDs), to include warning orders, mobilization orders, planning orders, North Atlantic Treaty Organization (NATO) force preparation messages, alert orders, DEPORDs including the GFMAP, and execute orders.
Subsequently, JS J-3 prepares and coordinates the Secretary of Defense Orders Book (SDOB) to present recommendations to SecDef for decision.

(b)  Force requirement validation.  JS J-3 evaluates CCMD force requirements against criteria published in the GFMIG.  Validated force requirements are forwarded to the Joint Force Coordinator to develop sourcing recommendations.  JS J-3 is the staff lead for force requirement validation and the preparation and coordination of the SDOB.

(c)  Joint Force Coordinator.  During the GFM allocation process, JS J-3 (as the Joint Force Coordinator) develops recommended execution sourcing solutions for all validated force and individual requirements.  Per the GFMIG, the Joint Force Coordinator also performs the duties of the JFP for conventional forces and individual requirements responsible for identifying and recommending contingency and execution sourcing solutions in coordination with the Secretaries of the Military Departments, CCDRs, DOD agencies, other JFPs, and the joint functional manager for conventional force and individual requirements.

(d)   JS J-3 serves as the DOD joint deployment process owner (JDPO) and maintains the global capability for rapid and decisive military force power projection.
As the JDPO, JS J-3 leads collaborative efforts of JPEC to improve the joint deployment and redeployment processes, while maintaining the overall effectiveness of these processes so all supporting JFCs and supporting DOD components can execute military force power projection effectively and efficiently.

(5)   Joint Staff J-4 [Logistics Directorate] assists the CJCS by leading the joint logistics enterprise.

(a)  JS J-4 prepares the logistics supplement to the Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3110.01, (U) 2015 Joint Strategic Capabilities Plan
(JSCP) (commonly referred to as the JSCP), which provides logistic resource apportionment guidance to support CCDR planning.

(b)  JS J-4 prepares the joint logistics estimate, which provides an assessment of logistics support to existing OPLANs and concept plans (CONPLANs) with identification of resource shortfalls and risks.

(6)   Joint Staff J-5 [Strategic Plans and Policy Directorate] is the CJCS's principal staff office for the preparation and review of strategic guidance documents and campaign and contingency plans.  JS J-5 coordinates JPEC review of designated campaign and contingency plans.  JPEC review of a plan focuses on its suitability, acceptability, feasibility, completeness, and compliance with joint doctrine.

(7)  Joint Staff J-8 [Force Structure, Resources, and Assessment Directorate]
provides resource and force structure analysis and program advice to the CJCS.
Responsibilities include:
(a)  Preparation of the assignment tables in the GFMIG and Forces For Unified Command Memorandum ("Forces For"), which documents SecDef's direction to the Service chiefs via the Military Department Secretaries for the assignment of forces to the CCDRs IAW Title 10, USC, Section 162.

(b)  Quarterly preparation of the force apportionment tables, for CJCS
approval, documenting the number of forces the Services estimate can be reasonably made available to respond globally to inform CCMD planning efforts.

## 4.  Combatant Commanders And Force Providers

a.  A CCDR's joint planning responsibilities are described in the Unified Command Plan (UCP); JP 1, *Doctrine for the Armed Forces of the United States;* and JP 5-0, Joint Planning.  The deployment and redeployment responsibilities of CCDRs are described below.  Additionally, when in a supporting role, CCDRs may act as a force provider (FP). FPs are the Secretaries of the Military Departments, CCDRs with assigned forces, the United States Coast Guard (USCG), DOD agencies, and OSD organizations that provide force sourcing solutions to CCDR force requirements.  Due to the global and dynamic nature of operations, it is important to note that a CCDR may fill supporting and supported roles simultaneously when planning and executing operations.
b.  **Responsibilities of Supported CCDRs.**  Supported CCDRs are responsible for deployment and redeployment operations planned and executed during joint force missions.  This responsibility includes identification of the movement, timing, and sequence of deploying and redeploying forces in the TPFDD; reception and integration of units and materiel arriving in theater; and assisting these units as required.  Throughout this process, GCCs will compile and report personnel accounting and strength by location.  Working through the Department of State (DOS), supported CCDRs negotiate host nation (HN) diplomatic clearances and reception POD access, when required, for deploying forces.  For air movements, supported CCDRs must ensure overflight and landing clearances are secured prior to the departure of forces from aerial ports of embarkation (APOEs).  Additionally, the CCDR will establish and publish policies, procedures, and standards to maintain personnel visibility in their AOR.  Supported CCDRs have three major responsibilities relative to deployment operations:  build a TPFDD based on the concept of operations (CONOPS) and, subsequently, validate movement requirements in the TPFDD after the unit refined movement data has been entered, determine predeployment standards, and balance and regulate the transportation flow.

(1)  Build the TPFDD and Validate TPFDD Movement Requirements.
Force requirements are documented in a notional TPFDD and phased/sequenced during plan development to support the CONOPS.  The notional TPFDD sourcing is based on planning assumptions derived from preferred force identification or contingency sourcing.  The execution-sourced TPFDD depicts execution-sourced forces.  The TPFDD depicts force requirements and force flow for assessment purposes and is used to analyze sourcing and transportation feasibility.  If developed, the force list will be entered into the Joint Operation Planning and Execution System (JOPES) as the basis for this analysis. It is a tool used during planning and does not contain execution-sourced units.  After execution sourcing, the supported CCDR validates the TPFDD records.  Validation by the CCDR confirms the forces satisfy the concept of deployment and mission requirement, and are approved for deployment by the President and SecDef.  The supported CCDR does the following to support this process:
(a)  Designates earliest arrival date (EAD), latest arrival date (LAD), required delivery date, and commander's required date.  The supported CCDR specifies key employment information regarding when, where, and how forces will be employed by phase.
(b)  Publishes a CCDR supplement to the standing TPFDD letter of instruction (LOI) to provide specific guidance for supporting CCDRs, Services, and agencies.
(c)  During execution, may task their assigned forces to fill force requirements to perform authorized missions.  Allocated forces may be needed to supplement the CCDR's assigned forces to meet operational demand.

For additional information on the TPFDD development, see CJCS Guide 3122, Time Phased Force and Deployment Data (TPFDD) Primer, *and CJCSM 3122.02,* Joint Operation Planning and Execution System (JOPES) Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution).

(2)  **Determine Predeployment Standards.**  Supported CCDRs establish predeployment standards for forces, capabilities, and personnel supporting their operations.  Predeployment standards outline the training and unique equipment requirements necessary to prepare supporting personnel and forces for the tactical and environmental conditions, as well as potential or known health threats in the theater.  The Services', United States Special Operations Command's (USSOCOM's), and other FPs' role is to ensure designated forces for CCMDs are organized, trained, equipped, maintained, and ready IAW these predeployment standards.  Predeployment standards help ensure all supporting personnel and forces arrive in theater fully prepared to perform their mission.  Supported CCDRs may identify mission-specific training requirements supporting individuals or units must complete before operational employment of allocated forces.  These requirements are included in the force requests submitted in either the annual submission or in an emergent request for forces (RFF).  Preparation for deployment is primarily a Service or FP responsibility.  Specific responsibility for preparation for deployment rests with the deploying unit or Service in the case of individual augmentees, replacements, and CAAF.  For in lieu of and joint sourcing solutions, the resourcing of preparation and training will be IAW Service-to-Service memorandums of agreement.  Usually, the deploying unit commander acknowledges completion of specified preparation for deployment requirements to the supported command during predeployment activities.  In some instances, constraints may affect personnel readiness if specific training requirements have not been completed.  This training may be conducted at home station prior to deployment, en route to the OA, or at the intermediate staging base (ISB).
(3)  **Balance and Regulate the Force Flow.**  The requested start dates on the request for each individual force or capability must support the overall CONOPS. SecDef-approved ordered start dates also support the CONOPS while balancing operational risks.  To the maximum extent possible, the supported CCDRs should balance and regulate the flow of forces with the flow of sustainment.  The OE, available infrastructure, protection risk assessment, and CONOPS are major factors in determining how to balance the flow of forces and capabilities.  The supported CCDR manages the flow of forces via the TPFDD, supported by strategic, operational, and tactical movement control organizations, to ensure effective interfaces between intertheater and intratheater movements.  Balance is primarily a function of effective mission prioritization, alignment of forces, force composition, and force flow.  Consideration must also be given to planned theater distribution (TD) and JRSOI requirements and capabilities.  Force composition and transportation flow must accommodate mission requirements, providing the supported CCDR with the operational flexibility and freedom of action required for successful mission execution.
(4)  **Joint Task Force (JTF) Responsibilities.**  If the CCDR chooses to accomplish the mission with a JTF, careful consideration should be made with respect to JTF deployment and redeployment responsibilities.  Responsibilities will be delegated from the CCDR and their Service components to their counterparts in the JTF.  Careful analysis should be performed by the CCDR and JTF HQ to ensure the JTF and its components are appropriately equipped with trained personnel, equipment, and information systems to perform those responsibilities.

See JP 3-33, Joint Task Force Headquarters, for additional information.
c.  Responsibilities of Supporting CCDRs.


With respect to deployment/redeployment, supporting missions of the joint force could include sponsorship of en route basing or in-transit staging areas (SAs) or provision of sustainment from theater stocks.  Regardless of the supporting mission, the primary task for supporting CCMDs is to ensure the supported CCDR receives the timely and complete support needed to accomplish the mission.
d.  **Responsibilities of FPs.**  In addition to the supporting CCDR responsibilities described above, a CCDR may also have additional responsibilities as an FP of allocated forces.  FP missions during the deployment of the joint force include the deployment/redeployment of forces from the supporting FP to the supported CCDR.  FP
deployment responsibilities include source, prepare, and verify forces; ensure units retain their visibility and mobility; ensure units report movement requirements rapidly and accurately; regulate the support flow; and coordinate.  Oftentimes, these responsibilities are assigned to the Service components to plan and execute.

(1)  **Nominate Sourcing Solutions.**  FPs coordinate directly with CCMDs, JFPs and JS J-3 (as the Joint Force Coordinator) to develop recommended global sourcing solutions.  FPs may assist and advise CCMDs with identifying preferred forces.  They also provide recommended contingency sourcing solutions and submit execution sourcing nominations to the JFPs and Joint Force Coordinator.  For execution-sourced forces, the recommended sourcing solution is reviewed through the GFM allocation process and becomes ordered when approved by SecDef directing the FP to provide the forces in support of an operation.

(2)  **GFMAP Annex Schedules.**  GFMAP annex schedules are orders authorizing the allocation of forces between CCDRs and are published with GFMAP base order and SecDef approved modifications to the GFMAP.  GFMAP annexes are published by JS J-3 and contain all the information inherent within a written order and authorize JFPs to order forces in subsequent GFMAP annexes schedules.  USSOCOM and USTRANSCOM, in their JFP role, will publish JFP annex schedules.  For conventional and joint individual augmentee sourcing, the GFMAP annexes A and D
serve as the JFP schedule.

(a)  The JFP GFMAP annex schedules identify units and individuals in support of the approved force requirements and serve as the DEPORDs.
1.  The GFMAP provides SecDef direction to the JFPs, working with all FPs through their assigned Service component and combat support agency (CSA) to identify specific forces, units, and individuals for deployment in support of the GFMAP.

2.  The actual units sourced by the FP are not included in the GFMAP
annexes.  Execution unit sourcing is available in the JOPES information technology (IT)
systems.  Each unit line number (ULN) should reference the force tracking number (FTN)
and FTN line number to trace back the force requirement to the originator, as well as SecDef authority to allocate back through the JFP GFMAP annex schedule to the GFMAP annex.

(b)  FPs support JFP planning and deploy forces specified in the JFP
GFMAP annex schedules.
(c)  Any additional fiscal year annual forces, as well as emergent requirements, are ordered in subsequent modifications to the base GFMAP annex upon SecDef approval.

(d)  JFPs publish modifications as required to their respective GFMAP
annex schedules in their entirety and supersede previous versions.  This allows JPEC to reference one final order rather than having to put together the dozens of modifications to the GFMAP annexes.

(3)  FPs publish their own DEPORDs implementing the orders in the JFP
GFMAP annex schedules.  All orders, down to the individual level, that implement the GFMAP annexes will reference the FTN and FTN line number.  Individual Service members and DOD civilians deploying should be traceable to their DEPORDs back to the CCDR requirements via the FTN.  CCDRs will also issue DEPORDs for their assigned forces.  Supporting and supported CCDRs, Services, and DOD agencies use JOPES as the system of record for execution and to document the deployment plan and movement requirements.

For additional information, see the GFMIG and CJCSM 3130.06, (U) Global Force Management Allocation Policies and Procedures.

(4)  **Command Relationships.**  Supported CCDRs accept deploying forces and exercise the command relationship as designated in the appropriate order for the deploying force upon arrival in their AOR and relinquish that command authority of redeploying forces upon departure from their AOR.

## 5.  Functional Combatant Commands

Supporting CCMDs incorporate planning for integrated campaign planning functions into their theater and functional campaign planning across CCMDs, Services, and DOD agencies for designated plans as directed in the UCP, Guidance for Employment of the Force (GEF), and JSCP.  Functional CCDRs provide planning and assessment support to GCCs to ensure the alignment and harmonization of campaign plans across AOR and functional boundaries.  Normally, several functional CCMDs are involved in every phase of a joint operation.  Three functional CCMDs involved in deployment of the joint force are:  USSOCOM, United States Strategic Command (USSTRATCOM), and USTRANSCOM.

a.  **USSOCOM.**  The Commander, United States Special Operations Command
(CDRUSSOCOM), is assigned all special operations forces (SOF) in the assignment tables in the GFMIG or "Forces For."  Title 10, USC, provides the CDRUSSOCOM with authorities distinct from other CCDRs with "Service-like" responsibilities for the development, support, and administration of SOF.  This may include, with specific authorities granted by SecDef, deploying SOF to execute theater campaign plan events such as joint combined exchange training and counterdrug/counter narcoterrorism training.  As the JFP for SOF, the CDRUSSOCOM identifies and recommends force execution and contingency sourcing solutions in coordination with the Military Departments, CCMDs, DOD agencies, applicable joint functional managers, and other JFPs for all SOF and individual requirements.  On occasion, USSOCOM may require common-user transportation assets to deploy or redeploy SOF.  Compared to conventional force operations, SOF deployment operations are usually smaller in scale; however, deployment planners may need to consider conventional support requirements which may also accompany SOF.  Given the nature of most SOF missions, time constraints, planning considerations, or special mission requirements may place unique demands on common-user transportation assets used for deployment of SOF.
For additional information, see JP 3-05, Special Operations; *JP 3-13.2,* Military Information Support Operations; *or JP 3-57,* Civil-Military Operations.

b.  **USSTRATCOM.**  USSTRATCOM provides advisors upon request by the supported CCDR.  The advisor coordinates with the mission-planning facilities of USSTRATCOM for global strike, strategic deterrence, global missile defense, synchronization of planning for cyberspace operations, joint electronic warfare, and space operations.

c.  **USTRANSCOM.**  USTRANSCOM responsibilities include the following:
(1)  As the JFP for mobility force, CDRUSTRANSCOM identifies and recommends force execution and contingency sourcing solutions for mobility forces in coordination with the Military Departments, CCMDs, DOD agencies, applicable joint functional managers, and other JFPs for all force and individual requirements.

(2)  **Joint Deployment and Distribution Coordinator (JDDC).**  As the JDDC, USTRANSCOM oversees the overall effectiveness, efficiency, and alignment of DOD- wide distribution activities, including force projection (force movement), sustainment, redeployment, and retrograde operations and establishes the CONOPS frameworks relating to the planning and execution of DOD transportation operations.  The JDDC's span of influence (as distinguished from span of control) must incorporate the entire distribution pipeline from fort/factory/depot to point-of-need.

(3)  Provide, through its transportation component commands, common-user and commercial air, land, and sea transportation; terminal management at air and sea POE and/or POD for DOD; and aerial refueling support across the range of military operations.  Also provide air transportation to numerous other USG departments and agencies at the direction of the President or SecDef through the CJCS.

(4)  Exercise training and readiness oversight authority over assigned mobility RC forces when not mobilized or ordered to active duty for other than training.
(5)  Exercise responsibility for global air, land, and sea transportation planning. (6)  Act as the DOD focal point for items in the transportation pipeline.  Ensure effective interfaces between the IGC and JOPES IT leading to force ITV.

(7)  Provide ITV for all force and sustainment movements supported by DTS
activities.  This visibility requires integration among DOD components and industry partners that operate DOD's supply chain.  End-to-end visibility of assets, from origin to employment, and all points in between including the "point-of-need," is required to achieve a more seamless and effective DOD supply chain.  During operations, identify known ITV reporting interface issues between information management systems.  Report incorrectly prepared, delayed, or frustrated cargo and personnel to the Service and the CCDR to support operation decision making and ensure accurate corrections without loss of visibility.
(8)  Provide DOD global patient movement in coordination with GCCs through DTS.

(9)  Provide GCCs with coordinated transportation planning expertise required during the planning process.  This includes reviewing the JSCP tasking, analyzing supported CCDR requirements registered in the JOPES for transportation feasibility, and advising the CCDR of changes required to produce an executable force deployment concept.  In addition, provide plan maintenance support to the supported CCDR as required or directed by the CJCS.

(10)  Provide deployment lift estimates and total lift asset availability to the President or SecDef and supported CCDRs for development of alternative courses of action (COAs) and optimal flow of forces planning.  USTRANSCOM will also advise supported CCDRs and the CJCS concerning use of or changes to lift allocations.

(11)  Assist the supported CCDRs and ensure validated movement requirements are routed and scheduled IAW the CONOPS.  Recommend reallocation of strategic lift assets to optimize their use and support plan execution during deployment, employment, sustainment, reconstitution, and redeployment.

(12)  Provide Joint Distribution Enabling Team (JDET).  USTRANSCOM can provide a JDET to assist CCMDs in planning their expeditionary theater opening distribution and sustainment operations.  The JDET travels in a temporary duty status to the CCMD HQ and is comprised of members of the USTRANSCOM, DLA, and Joint Contingency Acquisition Support Office staffs.  Upon arrival, the JDET assists the CCMD's staff with distribution planning for their contingency plan (or other joint distribution planning) in support of the CCMDs establishment of their distribution/supply chain for the arrival of follow-on forces and joint sustainment in theater.  JDET assists planning to synchronize cargo movement and sustainment; match distribution requirements to theater capabilities; develop commercial solutions; and coordinate, share, and integrate expeditionary theater opening distribution information and analysis. Outcomes of JDET support to the CCMDs include expeditionary theater opening distribution/sustainment economies and efficiencies, additional multi-modal distribution options, and improved resource informed expeditionary theater opening distribution plans.  In addition, JDET inputs inform the subsequent JPP in the development of OPLANs and execute orders between the USTRANSCOM J-3 [Director, Operations and Plans] and CCMD J-3 deployment/distribution planning teams as the expeditionary theater opening process moves to the operational level.

(13)  Provide Joint Enabling Capabilities.  USTRANSCOM's Joint Enabling Capabilities Command can provide CCMD HQ with mission-tailored, alert-postured, surge planning, public affairs, and communications capabilities to accelerate the formation and increase the effectiveness of newly formed joint force HQ, meet emerging challenges, and bridge joint operational requirements.

(14)  Provide Single Port Management.  In addition to its other responsibilities, USTRANSCOM is designated by SecDef as the single worldwide manager for commonuser POEs and PODs.  Operational experience shows the single port manager (SPM) is necessary to improve the planning and execution of port management operations and ensure the seamless transfer of cargo and equipment in any given theater.  Under the SPM, USTRANSCOM, through AMC, operates strategic aerial ports in theaters.
Additionally, USTRANSCOM, through SDDC, manages seaports of embarkation
(SPOEs) and seaports of debarkation (SPODs) in any given theater.  Key aspects of the SPM construct are that SDDC will provide planners to supported CCMDs to develop seaport management and operations requirements; at the request of the supported CCDR, conduct seaport assessments, establish contact with local seaport authorities, and determine availability of host-nation support (HNS); and when required, act as seaport manager throughout the operation.
(15)  Provide liaison officers (LNOs) to all GCCs to assist in coordination of strategic mobility issues.  USTRANSCOM and its components may provide additional technical experts to facilitate planning and execution on an as needed basis as requested by the supported CCDR.
(16)  Provide deployment and distribution planning coordination through the theater distribution campaign plan (TDCP).  As directed by the JSCP, USTRANSCOM will promulgate a standardized format for GCCs' TDCPs.  A TDCP describes a theater's current deployment and distribution system, including personnel, equipment, material, and capabilities.  Based on forecasted requirements, the TDCP identifies limitations of the existing network and the actions to improve the deployment and distribution network's ability to close gaps, mitigate risk, and meet the CCDR's theater campaign plan objectives.

For additional information on USTRANSCOM's role, see JP 4-01, The Defense Transportation System.

## 6.  Military Departments And National Guard Bureau

The Military Departments organize, train, supply, equip, maintain, mobilize, account for, and provide administrative and logistics support (including Service-organic transportation) for their respective forces.  When acting as an FP, the Secretaries of the Military Departments coordinate directly with CCMDs, JFPs, and the Joint Force Coordinator to develop recommended global sourcing solutions.  The Military Departments and other DOD agencies may depend on common-user military transportation services for unit and individual deployment and redeployment operations between POEs and PODs.  When using common-user military transportation services, the United States Army (USA), United States Navy (USN), United States Air Force (USAF), United States Marine Corps (USMC), DLA, and other DOD agencies are all generically referred to as shippers.  Each Service is responsible for administrative support and performance of transportation operations assigned by CCDRs at either their local shipping installations or throughout the theater.  In addition to these responsibilities, logistic elements of the Services that provide key support and enable the operations staff to execute the commander's requirements for deployment operations are noted below.

## A.  Usa

(1)  The Department of the Army (DA) is responsible for the assignment, preparation, and support of Army forces necessary for employment across the range of military operations.  For deployment operations, DA mobilizes, organizes, administers, trains, and demobilizes Army forces.  The Army's ability to project the military instrument of national power, specifically land power capabilities from the US or another theater, in response to requirements for military operations or force projection encompasses the processes of mobilization, deployment, employment, sustainment, and redeployment.  DA also establishes policy and procedures to reconstitute the Army.  The majority of Army combat assets cannot self-deploy and must be transported by other DOD and contracted assets in support of joint force operations.  Army units and their sustainment requirements will be submitted by the Army Service component command (ASCC) for inclusion on the joint force notional TPFDD by supported CCMD planners for scheduling of common-user transportation assets.  However, certain quantities of Army pre-positioned stocks in unit equipment sets, sustainment stocks, operational projects, or war reserve stocks for allies may be available either shore-based or afloat to support Army component operations.

(2)  DA is responsible for making land transportation available in overseas areas
(normally under the GCC's Army Service component commander) for the other Services and for coordinating all planning and requirements for the use of DOD-controlled land transportation equipment and facilities.  In some areas outside the continental United States (OCONUS), the ASCC has been assigned common-user land transportation (CULT) responsibility for peacetime land transportation; the ASCC will normally designate the theater sustainment command to supervise and execute any common-user transportation requirements delegated to it.  Wartime CULT requirements are the responsibility of the CCDR, and normally the joint deployment and distribution operations center (JDDOC) or the component assigned the mission will consolidate planned wartime movement requirements of all component commands.  While DA is responsible for overseas land transportation, USTRANSCOM manages the continental United States (CONUS) land movements.

For more information on TD responsibilities, see JP 4-09, Distribution Operations.
b.  **USMC.**  For deployment operations, both the USMC component and Marine airground task force (MAGTF) have force deployment planning and execution officers, MAGTF
planners, MAGTF
planning specialists, mobility officers, and logistic/embarkation specialists who work as a team during the planning and execution of force deployment operations in support of the MAGTF commander or JFC.  Force deployment planning and execution officers and MAGTF planning specialists build the MAGTF's notional TPFDD within the guidelines set forth by the CCDR and to support the MAGTF commander's OPLAN.  During force deployment execution, force deployment planning and execution officers and MAGTF planning specialists ensure proper execution of intertheater and intratheater lift, and the strategic mobility officers coordinate USMC movement requirements with the supported GCC, JDDOC, and USTRANSCOM.  The Marine Corps activates a Marine air-ground task force deployment and distribution operations center (MDDOC) within theater to coordinate and provide transportation services to all land-based elements of the MAGTF.  As the Marine Corps primary movement control agency within the theater, the MDDOC is responsible for establishing liaison and communications with and forwarding all transportation shortfalls to the theater JDDOC or to the component commander.

## C.  Usn

(1)  The Navy component commanders provide USN theater deployment and logistics support.
(2)  The majority of USN forces self-deploy in support of joint force operations and will be documented in the TPFDD.  USN expeditionary forces which do not selfdeploy, including the naval construction force, coastal riverine force, expeditionary logistics group, and expeditionary medical facilities, are time-phased to support the JFC. The supported CCDR validates all forces for movement, which then move to meet the CCDR's deployment/redeployment timelines.

(3)  In large deployment scenarios, the USN may establish naval advanced logistic support sites (NALSSs) to serve as the primary shore-based reception and transshipment points for personnel, equipment, and materiel.  Based on the number of carrier strike groups, amphibious ready groups, other USN units ashore in the Navy component commander area of operations, and level of joint tasking, the NALSS may be staffed and equipped to perform both USN reception, staging, onward movement, and integration and limited JRSOI duties.

(4)  A naval forward logistic site (NFLS) is the forward-most land-based transshipment point that provides the bridge between the NALSS and forward operating units.  An NFLS is typically established at an airfield or seaport close to the main battle area.  Like the NALSS, the NFLS is task organized, staffed with whole or modular components of advanced base functional components, and enables USN and JRSOI
operations.

(5)  The size and composition of NALSSs and NFLSs are dependent upon the support required and are tailored by USN logistic planners for the specific operation or contingency.  In lesser mobilization scenarios, the Navy component commander may designate an established naval activity to act in this capacity.  In either scenario, the Navy component commander coordinates and monitors personnel deployment activities for units and individuals.

d.  **USAF.**  Some USAF mobility and SOF have a limited self-deployment capability.
USAF and USAF SOF may rely on common-user transportation to move forces and sustainment cargo.  Within the USAF forces component, the logistics directorate is the principal coordinator of USAF logistics.  When required, the director of logistics provides centralized direction and control of deployment, reception, integration, employment, and redeployment of logistic and support assets.  The Deliberate and Crisis Action Planning and Execution Segments (DCAPES) is the USAF's primary operation planning and execution automated data processing system and is used to manage TPFDDs in support of deployment and distribution operations.

## E.  Ngb

(1)  The NGB is a joint activity of DOD.  The Chief, NGB, is responsible for the organization and operations of the NGB.  The NGB is the focal point at the strategic level for non-federalized National Guard matters that are not the responsibility of the Secretary of the Army, the Secretary of the Air Force, or the CJCS, in law or DOD policy.

(2)  The NGB supports US Northern Command and US Pacific Command development of plans for homeland defense (HD) and defense support of civil authorities
(DSCA) by providing visibility of state use of National Guard forces, IAW policies prescribed by the CJCS, the Secretary of the Army, the Secretary of the Air Force, and the Under Secretary of Defense for Policy.  National Guard forces in Title 32, USC, or state active duty status may deploy at the direction of a state/territorial governor in support of domestic operations, under the C2 of the governor.  If federalized, National Guard forces are under the C2 of the GCC or, if established, the JFC.  The NGB monitors the status of state unit mobilization.  Coordination is made with the JS, OSD, and state/territory governments to ensure adequate resourcing, support, and transition of authorities.

## 7.  Department Of Defense Agencies

DOD agencies include the defense agencies, DOD field activities, and other DOD
components that are not in a Military Department/Service, CCMD, OSD, or the JS but may provide force sourcing solutions.  Each DOD agency operates under the authority, direction, control, and supervision of SecDef, through a designated civilian officer within OSD or the CJCS.  CSAs are a subset of defense agencies assigned combat support or combat service support functions.

a.  **DLA.**  DLA is a CSA under the authority, direction, and control of the Under Secretary of Defense for Acquisition, Technology, and Logistics.  DLA provides worldwide logistic support to the Services, CCMDs, and other DOD components.  DLA
also provides support to USG departments and agencies and, when authorized by law, state and local government organizations, foreign governments, and international organizations.  During deployment of the joint force, DLA requires common-user transportation to move, stage, and recover its logistic resources in support of joint force operations.  Supported CCMD planners are responsible for validating DLA movement requirements entered in the notional TPFDD for scheduling by USTRANSCOM.
b.  **DIA.**  The mission of the DIA is to satisfy the full range of foreign military and military-related intelligence requirements in support of joint military operations.  With respect to deployment/redeployment operations, DIA products are used to develop/refine the estimate of the OE.

c.  **Defense Information Systems Agency (DISA).**  DISA provides, operates, and assures C2, information-sharing capabilities, and a globally accessible enterprise information infrastructure in direct support to joint warfighters, national-level leaders, and other mission and multinational partners across the range of military operations. DISA core mission areas are communications, computer processing for combat support, cybersecurity, joint C2, and joint interoperability support.  It provides guidance and support on technical and operational communications and information systems issues affecting OSD, the Military Departments, the CJCS and the JS, the unified and specified commands, and other DOD components.  DISA maintains and ensures the interoperability of JOPES, the Global Command and Control System-Joint (GCCS-J), the defense communications system, theater and tactical C2 systems, NATO and/or allied communication systems, and those national and/or international commercial systems that affect the DISA mission.  In addition, DISA supports national security emergency preparedness telecommunications functions of the National Communications System.

d.  **National Geospatial-Intelligence Agency (NGA).**  NGA is a source for imagery intelligence and geospatial information during planning and execution of deployment operations.  It provides geospatial information and services support, including safety of navigation and safety of flight information; imagery and geospatial system technical guidance; and staff assistance to the Services, CCMDs, and DOD components, and is the focal point for imagery, imagery intelligence, and geospatial information.

For more information on the role of NGA, see JP 2-03, Geospatial Intelligence in Joint Operations, and *JP 2-01,* Joint and National Intelligence Support to Military Operations.

e.  **Defense Threat Reduction Agency (DTRA).**  DTRA supports deployment and redeployment operations by providing technical reachback support through the National Countering Weapons of Mass Destruction Technical Reachback Enterprise, a continuous weapons of mass destruction and chemical, biological, radiological, and nuclear (CBRN) national reachback and situational awareness support element, for all technical analysis support.

For more information on DTRA capabilities, see Department of Defense Directive
(DODD) 5105.62, Defense Threat Reduction Agency (DTRA).

## 8.  Other United States Government Departments And Agencies

a.  **Department of Homeland Security (DHS).**  DHS responsibilities include customs, aerial and seaport security, and infrastructure hardening and protection.  DHS
coordinates and leverages resources with different governmental jurisdictions at the federal, state, and local levels.  DHS coordinates the transition of multiple agencies and programs into a single, integrated agency focused on protecting the American people and their homeland.  A comprehensive national strategy seeks to develop a complementary system connecting all levels of government without duplicating effort.  The DHS agencies that impact DOD deployment/redeployment include:
(1)  **Federal Emergency Management Agency (FEMA).**  FEMA coordinates the execution of emergency preparedness and response actions of all USG departments and agencies.  Under Title 42, USC, Chapter 68, DOD may provide support at the request of FEMA in support of state and local response and recovery efforts when a Presidential major disaster or emergency declaration has been or may be issued.

(2)  **United States Customs and Border Protection (CBP).**  The Commissioner of CBP is responsible for maintaining surveillance of illegal goods entering the US through DTS PODs.  CBP is also responsible for guarding against potential plant or animal infestations entering the US through DTS PODs.  All forces and material redeploying to the US will require CBP agricultural inspections.

## (3)  **Uscg**

(a)  The USCG is at all times a law enforcement agency, a military Service, and a branch of the US Armed Forces.  As a law enforcement agency with primary responsibility for maritime security, the USCG is empowered with broad statutory authorities to ensure the safety and security of US ports and coastal areas and employs its legal authorities to provide waterside security for military outload operations in US SPOEs.  The USCG can also deploy adaptive force packages of littoral surface assets (e.g., patrol boats) and deployable specialized forces to be attached to GCCs to ensure security, freedom of navigation, and safety for strategic sealift vessels transiting into SPODs.

(b)  The USCG has the authority and responsibility to ensure port safety and security in designated SPOEs.  To support deployment operations, the local USCG captain of the port is authorized to:

1.  Ensure adequate security at strategic seaports.
2.  Establish and maintain security zones and safety zones to support
processing, loading, and movement of military cargo.
3.  Provide armed vessels and/or aircraft to enforce a moving security
zone, naval vessel protection zone, or escort strategic sealift vessels.
4.  Conduct harbor and offshore surveillance and deterrence patrols.
5.  Supervise and support rapid loading of cargo, including and other sensitive cargo (supervision will be conducted within provisions of US law and applicable Department of Transportation (DOT) regulations and exemptions).

6.  Enlist the aid and cooperation of other federal, state, county, municipal, and private agencies to assist in the provision of security measures.

7.  Inspect commercial port facilities leased by SDDC and coordinate with SDDC to implement necessary safety or security improvements to the facility.

8.  Ensure owners and operators of waterfront facilities enforce regulatory access control measures.
(c)  At SPODs outside of US territorial waters, USCG port security units
(PSUs) and other assets such as patrol boats may be allocated to the CCDR and operate under the C2 of the naval component to conduct harbor defense/port security operations independently or as part of an integrated task group composed of PSU assets and USN coastal riverine forces.
(d)  In addition to PSUs and patrol boats, the USCG may deploy other types of deployable specialized forces or cutters to operate under the C2 of the naval component.  Like USN ships, USCG cutters self-deploy, but PSUs and deployable specialized forces require USTRANSCOM transportation to the theater and sustainment support from in theater Service components.  PSUs, deployable specialized forces, and sustainment stocks must be time-phased to support operations and entered in the TPFDD. The supported CCMD planners and, when applicable, USTRANSCOM planners validate movement data of USCG units and sustainment stocks in the TPFDD. USTRANSCOM then schedules these requirements for movement on USTRANSCOM common-user transportation assets.

b.  **Department of Health and Human Services (DHHS).**  During natural disasters or civil emergencies, DHHS assists FEMA and other national agencies in caring for the affected personnel.  FEMA coordinates DHHS movement requirements and deployment and/or redeployment support.

For additional information, see JP 3-28, Defense Support of Civil Authorities.

c.  **DOT.**  During national defense emergencies, the Secretary of Transportation has a wide range of delegated responsibilities, including executive management of the nation's transportation resources in periods of crisis.  USG-owned, surge sealift, under COCOM of CDRUSTRANSCOM, may be ordered into service and placed under the OPCON of Commander, MSC, in support of US wartime, humanitarian assistance and disaster relief, or contingency operations to offset shortages of commercial US-flagged ships.  Surge sealift may also be used for routine operations such as sustainment and exercise support when commercial assets are not available.

d.  **DOS.**  DOS and DOD are responsible for the operation of the noncombatant evacuation operation (NEO) program.  Deployments executed as part of a NEO will require coordination with DOS representatives.  DOS representatives may have access to embassy evacuation, marshalling, and security plans for the objective country.  DOS embassy personnel should have an estimate of the number of US citizens in the country and their locations for NEO repatriation planning.  DOS coordinates foreign country overflight and landing rights, diplomatic clearances, and visa and/or passport requirements for all deployment operations.  Additionally, DOS may be required to negotiate (or support DOD negotiation of) international agreements required for deployment operations.

For additional information on international agreements, see CJCSI 2300.01, International Agreements, *and DODD 5530.3,* International Agreements.

e.  **US Postal Service.**  The US Postal Service supports joint force operations through movement of essential military mail, including small Class IX repair parts.
Depending on the scope of the deployment, it may require a significant amount of common-user airlift to support forward-deployed forces.

## 9.  Other Transportation Partners Or Providers

The DTS relies heavily on the commercial transportation industry to perform a multitude of strategic and theater services during deployment operations in peacetime and war.  These commercial source capabilities span all modes of transportation and may include the use of USTRANSCOM-contracted US or foreign commercial air and maritime assets, as well as HNS within a joint operations area (JOA).  Commercial rail, trucking, ITV assets, and other transportation services may also be contracted to support deployment and redeployment operations.  Deployment/redeployment planners should coordinate with USTRANSCOM during early planning activities to determine the availability and implications of employing commercial transportation services in any plan.

## Chapter Iii Planning

"To successfully fight and win wars, we must make war planning our central focus.  We will develop the best possible plans using the collective wisdom available among all military planning staffs.  The products of our planning efforts must be able to stand up to the strongest scrutiny, including the ultimate test: execution."

## 1.  General

a.  This chapter describes the planning phase of the deployment and redeployment process.  Planning occurs continuously throughout the APEX planning and execution functions (see Figure I-2).

b.  Deployment planning is initiated in the plan development function of APEX
and continues to be developed and refined during the execution function.  The purpose of deployment planning is to develop a distribution network that supports the full range of activities in supporting the movement of forces and materiel during deployment, sustainment, and redeployment/retrograde phases of an operation.  It is conducted iteratively with force and support planning and may identify additional forces necessary to execute deployment functions.  It is conducted at all levels of command by both supported and supporting commanders.  Deployment planning activities include all actions required for the deployment of forces up to the point of their employment.  It involves planning to move, receive, and integrate forces from origin to final destination. Under the execution function of APEX, forces are allocated, sourced, and mobilized using readiness analysis.  Sustainment is requisitioned or pre-positioned and forces scheduled in the TPFDD.
c.  Redeployment planning is similar to deployment planning with considerations given to the distinct requirements of the redeployment.  Redeployments may occur under several conditions:  the transfer of personnel, equipment, and materiel from one supported GCC's AOR to another supported GCC's AOR to meet new operational requirements (e.g., a naval force that deploys to provide multiple CCDRs with forward presence); the re-posturing of forces within the same theater; or the return of forces to home station for reconstitution or demobilization either at the conclusion of an operation or in support of a routine rotation of forces IAW Service policies.
d.  In redeployment operations involving further employment of the force in support of another JFC's operation, the planning is conducted by the gaining supported commander in the same way as deployment planning.
e.  For redeployment operations that return forces to home station or demobilization station, when operationally feasible, redeployment planning will be based on guidelines established for tour length, the transfer of authority between inbound and outbound forces, the recovery and reconstitution requirements of supporting commanders and parent Services, and the demobilization of RC forces.

For more information on joint planning, see JP 5-0, Joint Planning.

## 2.  Considerations Of Operational Requirements

When conducting deployment planning, the following operational requirements should be considered:

## A.  **Existing Distribution Plans**

(1)  The USTRANSCOM Campaign Plan for Global Distribution 9033 (CP-GD
9033) provides a baseline assessment of the global distribution network capabilities against current and emerging requirements.  It is synchronized with CCDRs' TDCPs and Service/posture plans by approaching distribution from a global perspective.

(2)  Planners should consider the current Campaign Plan for Global Distribution
9033 (CP-GD 9033) and applicable TDCPs at the onset of deployment planning.

## B.  **Threat Environment**

(1)  Deployment planners assess the OE and threats to the mission and the force.
JIPOE must address to what degree a potential threat can interdict, disrupt, or block deployment and redeployment operations.  Threats to the force also include risk of isolation and exploitation.  Consequently, force and facility protection is planned and resourced based upon the conditions of the OE generally described as:  permissive, uncertain, or hostile.
(a)  **Permissive Environment.**  A permissive environment is an OE in which HN military and law enforcement agencies have control, the intent, and the capability to assist operations that a unit intends to conduct.  In this situation, entry operations during deployment are unopposed and the HN is supporting the deployment.

(b)  **Uncertain Environment.**  An uncertain environment is an OE in which HN forces, whether opposed to or receptive to operations that a unit intends to conduct, do not have totally effective control of the territory and population in the intended OA.  In this situation, entry operations during deployment are generally unopposed but could be opposed at any point during the deployment by forces or individuals not under HN control.
(c)  **Hostile Environment.**  A hostile environment is an OE in which hostile forces have control, as well as the intent and capability, to effectively oppose or react to the operations that a unit intends to conduct.  In this situation, the deploying force must conduct forcible entry operations to secure a lodgment for reception of the joint force to provide for the continuous landing of forces and materiel and provide space for subsequent operations, such as onward movement and integration.  Should US forces be denied temporary physical access to a specific geographic location, the JFC should plan forcible entry operations from an existing forward operating site or consider the use/formation of an ISB or sea base near the objective area or forward deployed maritime forces.
For additional information on determining the state of the OE, see JP 2-01.3, Joint Intelligence Preparation of the Operational Environment.

(2)  Planning the proper balance between deploying the force rapidly with the right mix of combat power and materiel is crucial.  The JFC must develop a balance that provides protection, efficient deployment, adequate support, and a range of response options to enemy activity.

(3)  Protection resource limitations will probably mean the staff cannot plan to protect every capability; therefore, they will need to look at prioritizing protection for critical capabilities and developing overlapping protection techniques.  Additionally, protection requirements may iteratively produce force or support requirements that must be integrated into deployment planning and execution.

(4)  Information about the movement of forces may provide an adversary with critical insight they need to defeat a force even before it arrives in its theater of operations. It is crucial forces coordinate with their command's operations security (OPSEC) personnel to develop appropriate countermeasures to mitigate this potential vulnerability.

## C.  **Communications Systems Supporting Visibility Of Deployment Operations**

(1)  The supported CCDR exercises control of deploying forces and resources to support the planned CONOPS and adapt to changes.  As the deployment requirements of the supported CCDR change, those updated requirements must be effectively communicated to supporting and subordinate commands to optimally align their efforts.

(2)  To effectively manage deployment operations, supported and supporting commands must have visibility of assets moving through DTS or in support of DOD operations.  A rapidly changing OE may cause the commander to alter the planned arrangement of operations even as forces are deploying.  Therefore, ITV and theater AV are critical to maintaining situational awareness and supporting decision making by commanders at all levels.

(3)  Early on in joint planning, the supported CCDR, through the TPFDD LOI, provides operation-specific guidance for using the APEX processes and systems to provide force visibility and tracking.  The CCDR's staff, during staff estimate development, should identify and examine the feasibility of providing adequate communications systems support for tentative COAs.  The estimate should also address the adequacy and security of networks used to manage, store, manipulate, and transmit operational or sustainment data.  During deployment and JRSOI refinement, the supported CCDR ensures the force deployment plan provides for force visibility and tracking at all times.

(4)  Communications systems and bandwidth requirements may be a limited resource and will require detailed planning to provide the appropriate level of communications resource allocations to maintain ITV and AV.  Communication requirements may iteratively produce force and support requirements that must be planned for deployment.  Initial phases of a deployment may not have the robust communications network required for extensive use of information systems.  Phasing joint and Service communications systems into the force flow early provides a system that allows the JFC to take advantage of the automated tools available for force and sustainment tracking.

## D.  **Training**

(1)  As an element of force planning, the supported CCDRs may identify specific predeployment training necessary to meet mission requirements.
(2)  This training may be conducted at home station prior to deployment or in theater as a part of JRSOI.  Deployment planning should consider the required time and resources necessary to conduct and validate mission specific training.

## E.  Infrastructure Assessment

(1)  Understanding the capabilities and limitations of the theater infrastructure and the time when assets become available is crucial for planning and executing successful deployment operations.  The assessment serves as a basis to determine the forces, equipment, and materiel that must be deployed and the facility upgrades required to enhance operations. Infrastructure consists of the physical network and the resource network.

(2)  The physical network or transportation infrastructure strongly influences deployment operations.  A robust network of modern air and seaports, highways, railroads, petroleum distribution, and inland waterways greatly expedite the throughput of forces, equipment, and supplies.  A lesser-developed, austere, or damaged infrastructure impedes deployment operations; affects POD or POE alternatives; and may require an early deployment of support capabilities, such as joint task force-port opening (JTF-PO), joint logistics over-the-shore (JLOTS), or engineer units.

(3)  The resource network comprises personnel, organizations, materiel, and equipment operating within the physical network and enabling the deployment, JRSOI, employment, sustainment, and redeployment of the joint force.  A thorough assessment of the physical network will lead to better understanding of the OE and more effective planning for what is required in the resource network.

(4)  USTRANSCOM's En Route Infrastructure Master Plan (ERIMP) outlines the key en route locations and infrastructure required to enable deployment and redeployment operations.  Synchronized with the ERIMP, CCDR theater posture plans provide the detailed theater posture of forces, footprint, and agreements that can enable deployment and distribution.  Such information serves as baseline data for planning.  Figure III-1 provides some items for infrastructure assessment.

## F.  Hns

(1)  When available, HNS assists in executing deployment operations.  Provisions in an HNS agreement can potentially overcome logistical shortfalls and decrease the amount of equipment and cargo that has to be deployed.  Elements of the agreement could include basing rights, life support, transit authority, POD services, security, power requirement generation, transportation, and infrastructure.

## Example Of Infrastructure Assessment

Physical Network
Resources Network


Airports
Aircraft


Seaports
Ships


Highways
Trucks and rail equipment


Railroads
Lighterage


Bridges
Host-nation support


Tunnels
Contractors


Terminals
Materials handling


Inland waterways
equipment and cargo


Storage facilities
handling equipment


Pipelines
Civilian, government and military personnel


Communication systems
Automation

(2)  During the COA development and selection, the CCDR's staff examines existing HNS agreements to determine what infrastructure, logistics, capabilities, and procedures are available to support the deployment.  If HNS agreements do not exist, or offer limited capabilities, then the CCDR, in coordination with DOS, should start negotiating HNS agreements to obtain necessary support.

(3)  Maintaining current, comprehensive base support plans and conducting periodic site surveys are critical for validating HNS agreements required for implementing specific OPLANs and CONPLANs.

g.  Operational **Contract Support.**  The CCDR determines whether contracted support is warranted based on mission assessment, available forces, and operational objectives.  Factors that warrant consideration for the use of contracted support in contingency operations include the continual introduction of high-tech equipment, force structure and manning limitations, and high operating tempos.  These factors may require that military forces be significantly augmented with contracted support.  Accordingly, the supported GCC, subordinate JFCs and their staffs, and Service component commanders and their staffs must be familiar with how to plan for and integrate contractors and contracted support into deployment and redeployment operations.  This includes both the deployment of contractor personnel and equipment and the employment of contracted personnel and assets to facilitate deployment and redeployment operations.
For more information regarding operational contract support, see JP 4-10, Operational Contract Support.

## H.  **Seabasing**

(1)  Seabasing is the deployment, assembly, command, projection, sustainment, reconstitution, and reemployment of joint power from the sea, without reliance on land bases within the OA.  Seabasing accelerates the deployment and employment of naval power and provides JFCs with the ability to conduct select functions and tasks at sea without dependence on infrastructure ashore.  As such, it minimizes the need for stockpiles ashore while positioning joint forces for immediate employment.  Seabasing, from either a single ship or a task-organized mix of ships, is equally relevant in either irregular or traditional warfare.  Sea-based forces' ability to react to warnings, operate free from diplomatic constraints, maneuver across the maritime OA, and provide a secure base of operations with C2 capability while minimizing the force protection requirements ashore gives the JFC an initial port and airfield at sea to conduct strike, power projection, fires, and logistics support missions.

(2)  The scalable and distributed nature of seabasing provides a JFC with a means to escalate or de-escalate a conflict through the application of military pressure when and where required, independent of other basing concerns or limitations.  By employing seabasing, joint forces can assemble and integrate combat capabilities in theater without necessarily exacerbating or prematurely escalating a crisis.  Through seabasing, a JFC can rapidly build, integrate, and project combat power from over-the-horizon to support joint forcible entry operations, enabling a rapid transition to decisive operations.  In this context, seabasing provides a JFC with options to seize/make use of multiple entry points (e.g., improved and unimproved aerial ports of debarkation [APODs] and SPODs) to support both joint forcible entry operations and other contingency operations.

For more information, see Navy Warfare Publication (NWP) 3-62M/Marine Corps Warfighting Publication (MCWP) 13-10, Seabasing.

## 3.  Deployment/Redeployment Planning And Adaptive Planning And Execution

APEX leverages a number of tools and processes.  IT tools enable planner collaboration and access to shared authoritative data.  Complementary tools of the overall planning process provide planners flexible analytical techniques for framing problems and logically developing plans or orders to accomplish missions and objectives, more specifically the deployment and redeployment operations.  This section will present a framework for aligning the deployment and redeployment planning phase with APEX planning and execution functions.

For more information regarding APEX, see CJCS Guide 3130, Adaptive Planning and Execution Overview and Policy Framework.

## A.  Planning Function - Strategic Guidance

(1)  **Initiate Planning.**  Joint planning begins when an appropriate authority recognizes a potential for military employment in response to a potential or actual crisis and issues a planning directive, guidance, or order.  At this time, the JFC will normally issue initial planning guidance, which could include information on the OE and the operational approach for the campaign or operation.
(2)  **Abbreviated Procedures.**  During a rapidly emerging crisis, the authority to begin deployment may be executed based on verbal orders.  Verbal authority to deploy forces can be delegated from SecDef for specific operations and/or events.  The supported CCDR may relay deployment requirements by phone, e-mail, or other expeditious means. The JS may host conference calls or video teleconferences with the supported CCDR, JFPs, joint functional manager, and FPs to abbreviate the staffing process.  Verbal orders are followed by written orders that have been staffed through the GFM process as soon as practical.

(3)  **Receive and Assess Planning Guidance.**  The planning staff uses strategic guidance to initiate planning for deployment and redeployment operations.  Strategic guidance provides specific tasks and planning guidance.  Strategic guidance includes the UCP, GEF, National Military Strategy (including supplements), JSCP (including supplements), GFMIG, and force apportionment tables.  Commanders also issue planning guidance to assist in planning deployment and redeployment operations.
(4)  **Conduct Mission Analysis.**  Some of the key mission analysis outputs that affect deployment and redeployment are: operational approach; initial staff estimates; initial force identification; initial risk assessment; commander's critical information requirements (CCIRs); and the identification of tasks, limitations, and assumptions.

(a)  When an organization receives a planning directive, planners should start by attempting to answer the following questions:

1.  What deployment tasks must be performed for the mission to be
accomplished?
2.  What forces and capabilities are necessary to accomplish the mission? 3.  Are the required forces assigned, currently allocated, or readily
available on the required timeline?
4.  Have any limitations been placed on deploying the force? 5.  What are the command relationships?
(b)  During mission analysis, the JFC and the staff examine imposed operational limitations, forces (i.e., assigned, apportioned, and allocated), lift capacity, and restrictions that limit the JFC's freedom of action, such as diplomatic agreements.  For situations that require a quick response, planners conduct initial force analysis, reviewing what forces are assigned per the assignment tables in the GFMIG and what forces are allocated per GFMAP to the supported CCDR and comparing them to capabilities required to accomplish specified and implied tasks.  This effort will begin to produce the initial force list which is refined during COA development and deployment feasibility analysis. These may significantly affect the deployment scheme, and the staff must develop options to minimize the impact.  Deployment/redeployment planning should consider and document the assumptions, physical and information factors, and any predicted impact enemy/neutral forces may have on the ability to deploy to or redeploy from the OE.

(c)  To assist with mission analysis, the JFC develops CCIRs to facilitate timely decision making.  The JFC's staff can recommend deployment-related priority intelligence requirements about the OE that become CCIRs if approved by the JFC.

(d)  The JFC's planners, in coordination with their component commands, develop the sustainment and deployment functional perspectives to be included in the staff estimate during mission analysis.  This informs the commander, staff, and subordinate commands how the deployment scheme supports mission accomplishment and to support COA development and selection.  The estimate should identify a rough order of magnitude of the available transportation capabilities and coordination requirements to support the timephased deployment, employment, and sustainment of tentative COAs.  It should include requirements for intertheater and intratheater transportation assets and requirements to protect critical transportation nodes and lines of communications (LOCs).  Although mission analysis occurs at the early stages of planning, if known, consideration should be given to the requirement to document the transportation of contractor support equipment and the procedures to integrate movement details for these personnel and equipment into the force flow.

## B.  Planning Function - Concept Development

(1)  **Develop COAs.**  A deployment concept for each tentative COA should be developed to determine its feasibility.  The deployment concept in the COA should show the force buildup, sustainment requirements, and military-political considerations.  The possible use of war reserve materiel (WRM), pre-positioned stocks and equipment, and theaterprovided equipment should also be included.  COAs may include JTF-PO requirements (such as a contingency response group [CRG]) to augment or expand transportation infrastructure and/or airfield/seaport capabilities.  Primary questions to consider for each COA are:
(a)  Is the COA feasible (i.e., can the mission be accomplished within the established time, space, and resource limitations)?
(b)  Is the COA acceptable (i.e., does it balance cost and risk with the advantage gained)?
(c)  Is the COA complete (i.e., does it include who, what, where, when, how, and why)?

(2)  **Analyze and Wargame COAs.**  Deployment planners analyze each COA
separately with the objective of helping to answer the primary questions stated in the previous paragraph.
(a)  Wargaming is the primary means of analyzing one or more COAs and is performed using one of the following methods:  a simple, but detailed narrative; a more comprehensive "sketch-note;" or computer-aided modeling and simulation.  Each critical event within a proposed COA should be wargamed based upon time available using the action, reaction, and counteraction method of friendly and/or opposition force interaction.  This basic wargaming method (modified to fit the specific mission and OE) can apply to the deployment events in the COA.

(b)  Within the context of wargaming, planning assumptions are challenged, shortfalls are identified, and requirements to modify the COA are identified.

(3)  **COA Comparison and Decision.**  Planners identify criteria relating to deployment for COA comparison, particularly focusing on the ability to deliver forces in time to meet the commander's phasing and mission essential task schedules.
(4)  **Outputs.**  Outputs from this activity include a refined force list, TPFDD, selected COA, initial CONOPS, commander's estimate, and planning directive.

## C.  Planning Function - Plan Development

(1)  **CONOPS Refinement.**  The refined CONOPS details the arrangement of simultaneous and sequential actions and activities needed to accomplish the assigned mission and remain consistent with the approved COA.  This arrangement of actions dictates the sequencing of forces into the OA, providing the link between the CONOPS and force planning.  The refined CONOPS provides the basis for the development of the plan or order and its annex C (Operations).

## (2)  Conduct Planning

(a)  **Force Planning.**  The purpose of force planning is to refine the numbers and types of forces required to accomplish the commander's CONOPS.  Force planning is conducted iteratively and in parallel with support planning and deployment/redeployment planning.  The forces identified during force planning provide the basis for support and deployment/redeployment planning.  However, subsequent support and deployment/redeployment planning may identify additional force requirements to conduct those respective functions and add enabling force requirements such as combat support /combat service support (CSS) to force planning. Force planning consists of determining the list of required forces by operation phase, mission, mission priority, mission sequence, and operating area.  It includes major force phasing, integration planning, and force list development.  Force planning is the responsibility of the CCDR, supported by component commanders in coordination with the Joint Force Coordinator, JFPs, and FPs.
1.  Force planning, in a rough order of magnitude, begins early during CONOPS development and focuses on applying the right force to the mission while ensuring force visibility, force mobility, and adaptability.  The commander determines force requirements, provides guidance for development of a TPFDD LOI or supplement to the standing Joint TPFDD LOI specific to the OA, and plans force modules to align and time-phase the forces in the notional TPFDD IAW the CONOPS.  The TPFDD LOI provides operation-specific guidance for utilizing the APEX processes and systems to provide force visibility and tracking, force mobility, and operational agility through the notional TPFDD and validation process.  It provides procedures for the deployment, redeployment, and rotations of the operation's forces.  The TPFDD LOI provides instructions on force planning, sourcing, reporting, and validation.  It defines planning and execution milestones and details movement control procedures and lift allocations to the commander's components, supporting commanders, and other members of the JPEC.  A notional TPFDD must ensure force visibility, be tailored to the phases of the CONOPS, and be transportation feasible.  Proper force planning informs the commander of the quantity and readiness of major forces and elements available, depending on the context of the situation, from those listed as assigned, currently allocated, or in the apportionment tables.  They are included in the supported commander's CONOPS by operation phase, mission, and mission priority.  Service components then collaboratively make tentative assessments of the specific sustainment capabilities required IAW the CONOPS.
For more information regarding TPFDD LOI development, see CJCSM 3122.02, Joint Operation Planning and Execution System (JOPES), Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution).

2.  Upon direction to execute, the CCDR submits an RFF to the JS, initiating the allocation execution function within APEX.  After the CCDR has submitted the RFF, JS J-3 validates it and assigns it an appropriate priority based on the Force Allocation Decision Matrix in the GEF.  JS J-1 conducts a similar process for joint individual augmentation requirements.  Once force requirements are validated, the Joint Force Coordinator and JFPs/joint functional manager coordinate with the FPs and supported CCDR to evaluate sourcing options and risks and recommend a sourcing solution for each requirement.  The Joint Force Coordinator staffs the joint sourcing recommendations with the supported CCDR and FPs prior to forwarding to SecDef via the SDOB.
For a detailed explanation of the GFM allocation process, see CJCSM 3130.06, (U) Global Force Management Allocation Policies and Procedures.

3.  When planning during crisis, the supported commander may identify force requirements as operational capabilities in the form of force packages to facilitate sourcing.  A force package is a list (group of force capabilities) of the various forces (force requirements) that the supported commander requires to conduct the operation described in the CONOPS.  The supported commander typically describes required force requirements in the form of broad capability descriptions or unit type codes (UTCs), depending on the circumstances.  The supported commander submits the required force packages through the JS to the FPs for sourcing.  FPs review the readiness and availability posture of their available units before deciding which units to nominate to the supported commander's force requirements.  Services and their component commands also determine mobilization requirements and plan for the provision of individual augmentee sustainment. The supported commander will normally review the sourcing recommendations through the GFM process to ensure compatibility with capability requirements and CONOPS.

(b)  **Support Planning.**  The purpose of support planning is to determine and sequence logistics and personnel support IAW the CONOPS.  Support planning is conducted in parallel with other planning and encompasses such essential factors as essential information integration through communication synchronization, lead component identification, responsibility for base operating support, communications and network support, airfield operations, management of individual augmentees, health support, personnel service support, personnel management and visibility, financial management, handling of enemy prisoners of war and detainees, theater engineering policy, logisticsrelated environmental considerations, support of NEOs and other retrograde operations, and security cooperation.  Planners should also identify potential nonorganic (e.g., HNS or operational contract support) requirements.

1.  The GCC and their subordinate commanders review their inter-
Service support agreements.  The GCC must decide if they desire to delegate directive authority for a common support capability to a subordinate JFC or Service component commander and determine the function and scope of the specific authority.  The GCC must also decide whether to assign specific common-user logistics functions to a lead Service and what size, roles, and functions a JDDOC will have if a common-user logistics lead is assigned.  The GCC planning guidance must clearly articulate the degree of reliance on HNS, acquisition and cross-servicing agreement (ACSA), or contract support within each phase of operation.  Finally, the GCC may elect to control logistics through the logistics directorate of a joint staff, or the GCC may elect to assign logistics control to a subordinate Service component.

2.  Support planning is primarily the responsibility of the Service component commanders and begins during CONOPS development.  Service component commanders identify and update support requirements in coordination with the Services, DLA, and USTRANSCOM.  They initiate the procurement of critical and low-density inventory items, determine HNS availability, determine contractor support requirements and plans, develop plans for AV, and establish phased delivery plans for sustainment in line with the phases and priorities of the CONOPS.  They train for and develop battle damage repair plans, repairable retrograde plans, container and 463L pallet management plans, force and LOC protection plans, supporting phased transportation and support plans aligned to the CONOPS, and report movement support requirements.

For further information on planning for and management of intermodal equipment in theater, see Defense Transportation Regulation (DTR) 4500.9-R, Defense Transportation Regulations, *Part VI,* Management and Control of Intermodal Containers and System 463L
Equipment, *and JP 4-09,* Distribution Operations.

3.  Service component commanders develop and refine their mission support, movement infrastructure, sustainment, and distribution requirements as the force planning further identifies force requirements.  The Service components develop their support plans in conjunction with their corresponding Service HQ and DOD agencies.
During distribution planning, the supported CCDR, USTRANSCOM, and DLA resolve gross distribution feasibility questions impacting intertheater and intratheater movement and sustainment delivery.  If these feasibility questions identify shortfalls due to inadequate resources, then planners must address these shortfalls.

4.  USTRANSCOM and other transportation providers identify air, land, and sea transportation resources to support the approved OPLANs.  These resources may include assumed available intertheater transportation, GCC-controlled theater transportation, transportation organic to the subordinate commands, and contracted transportation.  USTRANSCOM and other transportation providers develop transportation schedules for movement requirements identified by the supported commander.  A transportation schedule does not necessarily mean the supported commander's TPFDD is transportation feasible; rather, the schedules provide the most effective and realistic use of available transportation resources in relation to the phased TPFDD.  See JP 4-01, The Defense Transportation System, for more detailed capabilities and roles and responsibilities of USTRANSCOM.

5.  Installation planners conduct a deployment analysis based on early information acquired to determine potential scenarios, mission requirements, and COAs. From those assessments, installation planners determine how to best support the deployment.

(c)  **Nuclear Strike Planning.**  Specialized planning is typically conducted by USSTRATCOM in coordination with the supported GCC.  Commanders should assess the military and strategic impacts these operations would have on operations to include deployment planning and execution.

(d)  **Deployment/Redeployment Planning.**  Deployment and redeployment planning is conducted on a continuous basis for all approved plans/orders and crises. Planning for redeployment should be considered throughout the operation and is best accomplished in the same time-phased process in which deployment is accomplished.  In all cases, mission requirements of a specific operation determine the scope, duration, and scale of both deployment and redeployment planning.  Unity of effort is critical, since both deployment and redeployment operations involve numerous commands, agencies, and functional processes.  Because the ability to adapt to unforeseen conditions is essential, supported CCDRs' deployment plans must be able to support global force visibility requirements.  When planning for operations that may be enduring, consideration is given to force rotations.  Units must rotate without interrupting operations.  Planning should consider JRSOI, turnover time, relief-in-place and transfer of authority, and time it takes for the outbound unit to redeploy.  This information is vital for the FPs, Joint Force Coordinator, and JFPs to develop force rotations in the GFMAP annex schedule if the operation is executed.

## (3)  Deployment And Redeployment Concept

(a)  Supported CCDRs develop a deployment concept and identify specific predeployment standards necessary to meet mission requirements.  The Services and supporting CCDRs ensure unit OPLANs/CONPLANs are prepared, forces are tailored and echeloned, personnel and equipment movement plans are complete and accurate, command relationships and integration requirements are established and identified, mission-essential tasks are rehearsed, mission-specific training is conducted, force protection is planned and resourced, and sustainment requirements are identified.

(b)  Careful and detailed planning ensures only required personnel, equipment, and materiel deploy; unit training is tailored; missions are fully understood; deployment changes are minimized during execution; and the flow of personnel, equipment, and movement of materiel into theater aligns with the CONOPS.

(c)  Supported CCDRs develop a redeployment CONOPS to identify how forces and materiel will either redeploy to home station or to support another JFC's operation.  Effective redeployment operations are essential to ensure supporting services and rotational forces have sufficient time to fully source and prepare for the next rotation.
(d)  CCDRs may not have all planning factors to fully develop the redeployment CONOPS.  However, by using their TDCPs as the best available information for redeployment requirements, timelines, and priorities, the efficiency and effectiveness of redeployment operations may be greatly improved.  Topics addressed in this early stage of a redeployment CONOPS may include a proposed sequence for redeployment of units and individuals, as well as retrograde of materiel.  The timing of redeployment operations should consider customs clearance requirements.  Responsibilities and priorities for recovery, reconstitution, and return to home station may also be addressed along with transition requirements during mission handover.  In the force deployment process, a unit deploys, and at the end of mission, redeploys.  If the mission is enduring, the incoming unit arrives and conducts JRSOI and transfer of authority, and then the outgoing unit redeploys. In the GFM allocation process, CCDRs manage force requirements.  No CCDR redeployment order is required to conduct a standard rotation or for a unit to redeploy at the end of a rotation ordered in the GFMAP.  When a unit or portion of a unit, is no longer required due to end of mission, the CCDR orders redeployment.  The redeployment order will notify the force providing community that the unit is no longer required.

(4)  **Plan Refinement.**  As planning is conducted, planners analyze the plans feasibility and identify shortfalls.  Planning continues to reconcile identified shortfalls in resources or authorities that impede plan feasibility.  Reconciliation is iterative between force, support, and deployment planning as planners attempt to satisfy or mitigate shortfalls or feasibility limitations.  Plan refinement is conducted by the supported CCDR in coordination with supporting CCDRs, Joint Force Coordinator, JFPs, applicable joint functional managers, Service HQ, FPs, USTRANSCOM (as both a mobility JFP and DOD single manager for transportation), and DLA.

(5)  **Plan Review, Approval, and Transition.**  When the plan or OPORD is complete, JS J-5 coordinates with the JPEC for review.  The JPEC reviews the plan or OPORD and provides the results of the review to the supported CCDR and CJCS.  The CJCS reviews and provides recommendations to SecDef, if necessary.

(6)  **Outputs.**  Deployment-related outputs from this planning activity include the completed plan or order, transportation feasible notional TPFDD, and transition products.

d.  **Planning Function - Plan Assessment.**  The purpose of this function is to measure a plan's effectiveness in accomplishing its prescribed objectives.  The results of a plan assessment may lead to a decision to pursue one of four outcomes for the plan: refine, adapt, terminate, or execute.

(1)  **Refine.**  Refining a plan's deployment and redeployment operations may be required due to a changing OE; evolving guidance or direction; or as a result of force, support, or deployment planning.  Refinement efforts for the deployment and redeployment operations may continue into execution.

(2)  **Adapt.**  A plan's deployment and redeployment operations may require substantial updates due to significant changes to guidance and direction or large changes in the OE.
(3)  **Terminate.**  When a planning requirement is terminated the deployment and redeployment operations associated with that plan are terminated as well.

(4)  **Execute.**  Planning of deployment and redeployment operations continues into the execution functions as execution of the deployment and redeployment occurs.
e.  **Planning during Execution.**  As deployment operations transition into execution, deployment planning continues to refine and implement current plans or else adapt to changes in the OE.

(1)  Movement planning during execution integrates the activities and requirements of units with partial or complete self-deployment capability, activities of units that require lift support, and the transportation of sustainment and retrograde.  Movement planning performed during this phase supports and enables the movement phase of the joint deployment and redeployment process, and is directly tied into the deployment, distribution, and redeployment execution functions.  Movement planning is collaborative and is enhanced by the coordinated use of simulation and analysis tools.  One of the products used to coordinate and document the movement planning is the TPFDD.  A
TPFDD is a documentation of the phased movement of forces and support pending execution sourcing.  Upon sourcing, FPs and Service components develop unit refined movement/embarkation data within the corresponding Service systems, creating their portion of the deployment and movement plan.  The unit-level deployment and movement data is consolidated and exported into JOPES IT.  FPs then verify their specific requirements indicating the execution sourcing and associated deployment data is accurate.

(a)  The supported command is responsible for movement control, including sequence of arrival, and exercises this authority through validation of ULNs in the TPFDD. While planning the force flow, the supported CCDR must carefully balance the force mix and arrival sequence of combat forces, CSS units, and contracted and HNS capabilities to ensure deployment support and throughput requirements can be met.  Supporting CCDRs and Service component commanders responsible for deployment operations refine and verify unit force and deployment data and validate and continuously review the TPFDD for changes that may occur.  As with any dynamic process, external changes in the OE, as well as those within the force, necessitate corresponding changes to the flow of forces
(personnel, equipment, and materiel).  During execution, the supported command may sequence movement within the limits of SecDef force allocation ordered in the GFMAP. The supported commander uses organic and nonorganic lift, common-user, and strategic lift resources.  Competing requirements for limited strategic lift resources, support infrastructure, and intratheater transportation assets will be assessed in terms of impact on mission accomplishment.  If additional forces/capabilities are required, the supported CCDR identifies the requirements and provides rationale for those requirements in an RFF.

(b)  The supported command planners prepare movement plans with consideration of operational priorities and any movement constraints (e.g., beddown, CBRN contamination of POE/POD, cargo, or lift assets).  The planners will consider en route staging locations and the ability of these locations to support the scheduled activity. This information, together with an estimate of required site augmentation, is communicated to appropriate supporting commanders.  USTRANSCOM, in consultation with the supported CCDR, conducts and assesses transportation feasibility analysis and develops recommendations on final POE selections for those units without organic lift capability. Movement feasibility requires current analysis and assessment of movement C2 structures and systems; available organic, strategic, and theater lift assets; transportation infrastructure; and competing demands and restrictions.
(c)  After coordinated review of the movement analysis by USTRANSCOM, the supported CCDR, in coordination with the JFPs and component commands, may adjust the deployment CONOPS to improve movement feasibility where operational requirements remain satisfied.  CDRUSTRANSCOM should adjust intertheater transportation assets to meet the supported commander's operational requirements.  If this is not an option due to requirements from other commanders, then the supported commander adjusts the force flow and the TPFDD requirements or is provided additional intertheater and intratheater lift capabilities using (but not limited to) CRAF and/or VISA capabilities as necessary to achieve end-to-end transportation feasibility.

(d)  Operational requirements may cause the supported commander and/or subordinate commanders to alter their plans, potentially impacting the deployment priorities or TPFDD requirements.  Planners must understand and anticipate the impact of change.  There is a high potential for a sequential pattern of disruption when changes are made to the TPFDD.  A unit displaced by a change might not simply move on the next available lift, but may require reprogramming for movement at a later time.  This may not only disrupt the flow, but may also interrupt the operation.  Time is also a factor in TPFDD and force flow changes.  Airlift can respond to short-notice changes, but at a cost in efficiency.  Sealift, on the other hand, requires longer lead times and cannot respond to change in a short period.  These plan changes and the resulting modifications to the notional TPFDDs must be handled during the planning cycles.

(2)  **JRSOI Planning.**  The supported CCDR conducts JRSOI planning to ensure deploying forces arrive and become operational in the OA as scheduled.  Establishing personnel visibility for force protection purposes is necessary for joint forces immediately upon their arrival in the OA, and plans to accomplish this task are issued by the GCC manpower and personnel staff.  Effective integration of the force into the joint operation is the primary objective of the JRSOI phase.

(3)  **Deployment and JRSOI Refinement.**  The supported command conducts deployment, JRSOI, and planning TPFDD refinement in coordination with the JS, JFPs, USTRANSCOM, Services, and supporting commands.  The purpose of the deployment and JRSOI refinement is to ensure the force deployment plan maintains force mobility throughout any movements, provides for force visibility and tracking at all times, provides for effective force preparation, and fully integrates forces into a joint operation while enabling unity of effort.  The refinement conference examines planned missions, the priority of the missions within the operation phases, and the forces assigned to those missions.  By mission, the refinement conference examines force capabilities, force size, support requirements, mission preparation, force positioning/basing, weapon systems, major equipment, force protection, and sustainment requirements.  The refinement conference should assess the feasibility of force closure by the commander's required delivery date and the feasibility of successful mission execution within the time frame established by the commander under the deployment concept.  The refinement conference should assess potential success of all force integration requirements.  Transition criteria for all phases should be evaluated for force redeployment including rotation requirements.

(4)  **Planning Changes.**  Tactical and intelligence considerations, force and nonunit cargo availability, availability of strategic lift assets, and POE and POD capabilities may necessitate changes to the original plan.

## Chapter Iv Predeployment And Pre-Redeployment Activities

"To a conscientious commander, time is the most vital factor in his planning.  By proper foresight and correct preliminary action, he knows he can conserve the most precious elements he controls, the lives of his men.  So he thinks ahead as far as he can.  He keeps his tactical plan simple.  He tries to eliminate as many variable factors as he is able.  He has a firsthand look at as much of the ground as circumstances render accessible to him.  He checks each task in the plan with the man to whom he intends to assign it.  Thenhaving secured in almost every instance his subordinates' wholehearted acceptance of the contemplated mission and agreement on its feasibilityonly then does he issue an order."

## 1.  General

Predeployment and pre-redeployment activities are the second phase in the joint deployment and redeployment process.  The activities are functions deployment and redeployment planners and unit commanders must accomplish to successfully complete their movement to the POE.  A majority of these functions are performed at the unit level, linking the installation/base/unit deployment/redeployment efforts to the overall strategic movement.  This chapter addresses the activities for deployment and redeployment taken to prepare forces to execute a deployment/redeployment operation before actual movement.

## 2.  Deployment Prepare The Force Activities

a.  Select forces may deploy within hours or days from receipt of a DEPORD while other units may deploy on a timeline of days to several weeks.  Regardless of the deployment timeline, a myriad of predeployment activities must be accomplished to deploy the force with their required equipment and supplies.  These actions range from the strategic to the tactical level.  At the strategic and operational levels, TPFDD sourcing/refinement and transportation feasibility may continue well into this phase.  At the installation and unit level, activities range from personnel and equipment status confirmed and upgraded to conducting required training.  Deployment timelines will dictate available time to conduct prepare the force activities, which include: activating deployment and C2 support organizations, conducting movement and support meetings, developing  a unit deployment list (UDL) and identifying shipping/handling requirements, and conducting required training.

(1)  **Activate Deployment and C2 Support Organizations.**  Commanders and their deployment planners at all levels must develop plans for the key activities that a deploying unit must perform to support their timely deployment.  These activities will vary based on unit location and deployment mode/node, but a key deployment enabler at all levels is the activation of **deployment C2 support organizations**.  These organizations play a major role in activating and synchronizing support activities for deploying units.
These support activities vary but may include medical and personnel support facilities; supply and maintenance activities; and critical deployment nodes to include railheads, airfields, and seaports.

(2)  **Conducting Movement and Support Meetings.**  Movement and support meetings are typically held at the strategic through tactical levels to discuss deployment planning and operations.  Identifying and resolving transportation shortfalls or limitations are key areas addressed during these meetings.  Transportation planners at the strategic level participate in the development of collaborative transportation solutions and offer alternate COAs if transportation feasibility analysis indicates transportation shortfalls and the desired CCDR deployment timelines cannot be met with existing strategic mobility triad assets. Resolving these **shortfalls** may require resolution at the JS level so identifying transportation shortfalls early is critical to obtaining a timely resolution.  At the tactical level, identifying and resolving transportation shortfalls and/or limitations must also occur early in these movement and support meetings.  Requesting and receiving additional transportation assets such as railcars and commercial heavy equipment transporters or containers may be time-consuming and should be done early on.  Another key interface required during these meetings is between the deploying units and the C2 elements of the APOEs and SPOEs.  A multitude of topics may be discussed and coordinated at these meetings.  Port support activity (PSA) requirements and availability of ITV infrastructure and processes to be used are two topics that require special consideration.  Transportation planners may also find it beneficial to conduct site surveys at the POEs prior to these support meetings.  Coordination with local, state, or HN authorities for movement permits for equipment being convoyed to the POEs is another separate but critical task that must occur.  Coordination done at these meetings with the POE C2 elements or local/HN authorities provides the foundation for a successful transition to the establishment of PSAs or arrival/departure airfield control group (A/DACG) during the **assemble and marshal** forces activities.

(3)  **Develop UDL and Identify Shipping/Handling Requirements.**  Developing the UDL and unit refined movement data, identifying shipping/handling requirements, and conducting required training are primarily the responsibility of the deploying unit.  Accuracy of the UDL is critical as strategic transportation planners commit USTRANSCOM lift assets based on the information within the UDL because incorrect data can lead to inadequate assets available to move deploying units.  Not identifying equipment in a timely manner could affect the JOPES validation process.

(4)  **Conduct Required Training.**  Commanders should ensure all required training is identified and planned for the deploying force.

b.  Deployment planners should account for concurrent sustainment activities in their overall plans.  Activities in the planning phase may capture the basic requirements for the movement of sustainment, but planners will have to finalize sustainment movement plans as part of their predeployment activities.  Conducting this planning in a collaborative environment allows USTRANSCOM to gain and maintain visibility on all known strategic movement requirements, facilitating responsive support by the strategic mobility triad.
Preplanned sealift that supports sustainment requirements is also a part of predeployment activities.
c.  The supported commander establishes the policy, procedures, priorities, and LOCs for sustainment activities.  Normally, the commander will immediately begin to submit demand-based or "pull" sustainment requirements for Services to resupply their forces in theater.  In the absence of the commander's specific guidance and requirements, each of the Services will sustain its forces using Service methodologies, which may include initially "pushing" sustainment to its forces.  Sustainment supplies do not always follow the designated deployment LOC since some supplies (petroleum, oils, and lubricants [POL]
and ammunition) require special handling facilities and could result in significant disruption of port activities.  Optimizing port throughput will be a primary factor in balancing pull and push sustainment procedures.

d.  Transportation planners must be aware that sustainment movement and its required intertheater lift is handled differently than deployment intertheater lift.  Time-phased deployment requirements are developed, sourced, refined, and validated in JOPES for USTRANSCOM movement scheduling.  Intertheater airlift for deployment operations is requested through JOPES.  Normally, some sustainment is planned as part of the deployment TPFDD developed in JOPES IT.  However, as the operation progresses, intertheater sustainment airlift becomes more requirements based.  Channel service or express service airlift is the normally planned method for the movement of sustainment by air.  This process involves sustainment moving on predetermined channels that are established IAW existing regulations.
e.  Supply and support requirements of deploying forces consist of two major categories:  unit-related supplies and equipment and non-unit-related supplies and equipment.

(1)  Unit-related supplies and equipment include a unit's organic equipment, basic load, and accompanying supplies.  Unit-related supplies and equipment are configured (palletized or containerized) and documented for deployment by the unit.  Unit planners enter movement data for unit-related supplies and equipment in the UDL and later into the TPFDD.

(2)  Non-unit-related supplies and equipment include all supply sustainment support requirements that are not identified for a specific unit.  They include pre-positioned war reserve stock, sustaining supplies, and resupply.  Non-unit-related supplies and equipment are configured and documented as cargo increment numbers for deployment by the sourcing organization and provided for distribution in theater by DLA and Service component logistic units.

f.  **Non-Unit-Related Personnel (NURP).**  NURP includes all personnel requiring transportation to or from an OA, other than those assigned to a specific unit (e.g., filler personnel, replacements, temporary duty or temporary additional duty personnel, civilians, medical evacuees, and retrograde personnel).  NURP are normally moved via commercial transportation from losing organizations to designated replacement locations.  The Services designate organizations to coordinate strategic lift requirements with USTRANSCOM for movement of NURP from designated origins into theater based upon deployment requirements incorporated into the notional TPFDD during planning.  Those requirements are integrated into transportation and reception plans and used to determine the number and location of US replacement centers and APOEs required to support the deployment.

For additional information on NURP, see JP *4-01,* The Defense Transportation System.

## 3.  Schedule Movement For Deployment

a.  Movement scheduling is an iterative process done at every level of supported and supporting commands to transport, move, or deploy the right forces (unit-related personnel and equipment) and sustainment (NURP, supplies, and equipment) to the right place at the right time.  Transportation planners should become familiar with JOPES and its Web Scheduling and Movement (Web SM) sub-system application, as this is the primary source for up-to-date scheduling movement data.  Schedule movement consists of five activities to include:

(1)  Receive strategic movement schedule.
(2)  Receive/assess movement and lift schedule. (3)  Receive port calls. (4)  Confirm movement clearances. (5)  Build and publish schedule of events.
b.  Supported and supporting CCDRs receive **strategic movement schedules** as they are scheduled and registered in JOPES and the Web SM application.  These strategic movement schedules provide critical information for deployment planners and, as such, planners should assess lift schedules to determine if these schedules support the overall operational timelines of the deployment.  Lift shortfalls and other scheduling discrepancies must be reconciled at the earliest opportunity with USTRANSCOM to prevent delays in the overall strategic deployment plan/operation.  Once the strategic movement schedules are published, supporting commanders and their units/installations will receive a port call message from SDDC, for surface movement.  Installations and commands at the tactical/local level should use the port call information to finalize movement planning and coordination.
c.  Movement control elements confirm diplomatic and ground movement clearances with HN, state, and governmental agencies.  This requirement may be a very simple one for local/tactical units involved in the deployment; however, it may also be a strategic-level task.  Strategic transportation planners may be required to request and confirm multiple HN road/rail and port clearances for ground deployments, as well as State Department coordination for obtaining diplomatic clearances for aircraft overflights.
d.  Movement instructions are published based on JOPES strategic lift schedules and the supported commanders' movement priority.  These detailed instructions allow for installations and commanders at all levels to build and publish a schedule of events for their own deploying timelines.  The schedule of events should be based on the date deploying units and equipment arrive at the POE on or before the scheduled available-to-load date (ALD) shown in JOPES.  All supporting commanders and deployment planners must realize their movement schedules are part of the overall time-phasing of forces and, as such, little or no deviation to the published schedule of events is allowed to complete the deployment in the timelines planned.

## 4.  Assemble And Marshal Forces For Deployment

a.  Assembly and marshalling involve bringing together personnel, supplies, and equipment in preparation for final movement to the POD.  It comprises four activities, to include:

(1)  Assemble personnel and cargo.
(2)  Conduct unit inspection, load equipment, and prepare. (3)  Sequence loads. (4)  Establish support organization at the POE.
b.  Establishing support organizations at the POE is an activity that is coordinated and planned in the earlier predeployment movement and support meetings.  Strategic and tactical interface occurs within this task as support units move to their designated POEs and begin the process of preparing to load cargo vessels and aircraft.  Also as part of this activity, units establish support functions such as movement to their POEs.
c.  Assembly and marshalling of forces are interrelated, and as such, may occur simultaneously.  A critical task for all units to accomplish within these activities is to ensure proper ITV occurs for deploying equipment and supplies.  This entails the writing of data-rich or license plate radio frequency identification (RFID) tags for deploying organizational equipment and multimodal containers prior to movement to the POEs; regardless of whether data rich or license plate RFID tags are used, shipment data is uploaded to the radio frequency ITV system server.  Timelines to accomplish this critical ITV task may vary, but for planning purposes, deployment planners should schedule this critical event prior to the completion of assembly and marshalling forces.  Commanders and deployment planners should refer to the DTR and internal Service policies for detailed instructions on RFID data requirements.  At a minimum, they should plan to provide content-level detail IAW the DTR RFID tag data standards.  Correct utilization of RFID tags (data rich or license plate) provides the entire DTS
the capability to have timely and accurate information on deploying and redeploying cargo movements.

d.  Correctly manifesting deploying personnel is also a critical task that requires planning and proper execution.  The DTR requires the manifesting of all deploying personnel.  For deployment by air, the passenger terminal or base operations at the POE and en route stops are normally responsible for passenger manifesting.  However, the aircraft commander is ultimately responsible for compliance with these procedures.  For unit moves, the respective Service deployment automated information system (AIS) will be the primary means to generate and transmit an electronic manifest.
For further information on passenger manifesting, see DTR 4500.9-R, Defense Transportation Regulations, *Part I,* Passenger Movement.

## 5.  Redeployment Prepare The Force Activities

a.  A successful redeployment requires the planning and execution of "prepare the force"
activities similar to those used in deployments.  The execution of these pre-redeployment activities will not be identical to deployment activities due to the OE, available resources, and the force structure of the redeploying units.  As such, procedures and unit-level activities may vary from those performed during a deployment but these activities require detailed planning for a successful redeployment operation.  Redeployment prepare the force activities also has a unique sixth activity, complete equipment disposition actions.  This activity is only done in the redeployment process and requires a detailed planning effort since this activity may significantly affect the amount of equipment that is redeployed.

b.  Within the redeployment activity, activate deployment and C2 support organizations; redeployment planners at the supported CCMD should establish clear C2 channels for redeployment operations.  The CCDR's JDDOC is an organization that may be capable of performing much of this mission, but planners must clearly identify the JDDOC role in redeployment operations.
c.  Planners and unit commanders will be required to conduct a multitude of movement coordination and support meetings as they plan redeployments.  Force protection is a topic that must be addressed throughout this activity and requires a significant amount of planning.
Contract or HN security may be used as forces reach staging bases and turn in their equipment and Class V.  If contract security is used, planners should work closely with the requiring activity, contracting officer, or contracting officer representative to establish the requirement and to ensure the capability is present throughout the redeployment process.  As redeployments continue, there will be fewer military personnel and equipment available to execute redeployment tasks.  Thus, planners should consider the use of HNS or contracted support to provide personnel or cargo handling equipment to resolve transportation shortfalls.  As part of this activity, a pre-redeployment site survey (the reverse of the predeployment site survey) may be required for any POE or staging base used.  Staging bases used for redeployment operations may be either a Service component operated base or a joint base with all Service units passing through.  Regardless of the organizational structure of the staging base, redeployment planners should coordinate support to assist units in SAs with actions such as:

(1)  Turn-in of excess supply stocks and pre-positioned equipment. (2)  Reconstituting and cross-leveling of supplies and equipment.
(3)  Identify requirements for loading on pallets, containers, and flat racks. (4)  Repacking and loading for movement.
d.  US customs and agricultural requirements are two areas that require special planning considerations and coordination during redeployment site surveys and support meetings.  Wash rack operations/facilities and secure equipment SAs at the POE are topics dealt with at the unit/tactical level but have a major impact on the overall joint deployment movement phase and movement schedules.
e.  The unique sixth activity done during pre-redeployment is complete equipment disposition.  Redeployment and sustainment planners must collaborate early in the redeployment planning phase to allow for a cohesive equipment disposition plan for excess materiel turn-in and a timeline to be developed and implemented.  Equipment earmarked for this disposition action or a foreign military sales (FMS) program is not included in the UDL or redeployment TPFDD.
f.  Redistribution and retrograde of supplies and materiel may play a major role in the activity complete equipment disposition.  Significant national resources are invested in supplies and materiel to support joint operations.  The following are some of the guidelines for redistribution:
(1)  Non-unit redeployed equipment and supplies are redistributed according to plans developed by the JS, DLA, and the Services with input from the CCDRs.

(2)  A significant amount of sustainment materiel may be in transit when a requirement is reduced.  This materiel must be diverted or redirected as required.  Discipline in maintaining ITV will facilitate this part of redeployment planning.  Forces waiting for redeployment should consume theater stocks and materiel.  Distribution management centers should cease requisitioning from outside the theater, to the extent possible.
(3)  Retrograde recipients may include other forces that are in the force generation cycle preparing for deployment, HNs, Service materiel commands, DLA, and General Services Administration distribution centers.
(4)  In the redistribution process, equipment may be available for FMS or grant programs, such as excess defense articles, to support national interests and policies.
(5)  The safe redeployment or retrograde of equipment with previous or residual contamination should be limited to critical items unless equipment has been assessed to be safe or meets clearance standards.  This information allows detailed planning for equipment consolidation sites and contamination mitigation assets required by the CBRN retrograde support element.  The safety of service and transport personnel is of foremost concern during the redeployment and retrograde of equipment with potential residual or low-level contamination.

For more information on retrograde considerations, see JP 4-09, Distribution Operations.

## 6.  Schedule Movement For Redeployment

a.  The five schedule movement activities discussed for deployment are also applicable to redeployment.  Normally, notional redeployment TPFDDs are developed during redeployment planning and updated and refined during execution as the redeployment window approaches. Redeploying forces are tailored and prioritized for redeployment based on the supported CCDR's intent expressed in the OPLAN or redeployment plan.  During redeployment preparations, it is a Service-/unit-level responsibility to update unit movement data to reflect changes to the UDL.  Subordinate organizations and component commands must verify unit movement data to the supported CCDR for redeployment TPFDD validation. USTRANSCOM develops the redeployment strategic movement schedule after receiving the validated TPFDD from the supported CCDR.

b.  The supported CCDR has the primary responsibility for redeployment planning and execution.  The redeployment plan will be the basis for movement schedule timelines for redeploying forces.  Similar to deployment, CCDRs and supporting Services will input their data into JOPES and the scheduling and movement application.  These schedules will provide dates for units to arrive at SPOEs and APOEs.  Planners should focus on units arriving at the POEs on the ALDs as they develop and publish their internal redeployment movement schedules.

## 7.  Assemble And Marshal Forces For Redeployment

a.  A successful redeployment also requires the planning and execution for all the assembling and marshalling forces activities.  These redeployment activities are the same as those performed during deployment and may require additional time and locations.  There is also an additional redeployment activity: prepare and conduct customs/agricultural inspections.
b.  Assembling and marshalling forces activities may begin at the tactical level with units withdrawing from OAs and moving to tactical assembly areas (TAAs) to begin their preparation for redeployment.  Units may then move to a staging base close to their POEs and then to the POE and its supporting marshalling areas.  Redeployment planners must plan for the establishment of support organizations at the POE.  However, planners must understand that redeploying units may not have the assets required to fully support this task or to prepare their equipment for redeployment.  Supporting unit assistance or contractor support may be required.

c.  The task of preparing and conducting customs/agricultural inspections is one that is uniquely linked to pre-redeployment operations.  Redeploying forces must meet US or HN customs and agricultural requirements before they can redeploy.  Supported commanders are responsible for establishing a military customs inspection program (MCIP) to ensure redeploying personnel, equipment, and materiel comply with customs and agricultural requirements for their redeployment destination.  An approved MCIP must be in place prior to redeployment to clear personnel, cargo, and battle-damaged equipment returning to the US for disposition.

(1)  US customs clearance and CBP inspection and wash-down of all personnel, equipment, vehicles, and retrograde cargo redeploying to the US is IAW DOD policy.
(2)  Customs/agricultural inspections requirements for forces returning to home station in a foreign country will be different from those for units returning to the US. Redeployment planners should determine these requirements in coordination with their HNs and coordinate inspections with the HN accordingly.

d.  Cargo documentation is one of the many activities that will occur during the last three activities of assemble and marshal forces for redeployment.  Commanders ensure cargo documentation follows existing Service and CCDR policies.  The rush to return to home/demobilization station may bring about severe problems unless command emphasis is placed on accurately marking and documenting redeploying cargo.  Unit movement data provided to TCCs must be correct to document cargo properly to prepare manifests for redeployment.  Transportation planners should strive to maintain unit integrity for redeployment as it is as critical to readiness as it is during deployment.



## Intentionally Blank Chapter V Movement

"The USTRANSCOM [United States Transportation Command] team's approach to building and providing winning logistics solutions starts always by building and leveraging a partnership with those that we serve."
US Transportation Command September 2008October 2011

## 1.  General

a.  This chapter describes the movement phase of the joint deployment and redeployment process.  During this phase, validated TPFDD movement requirements developed during the planning phase and scheduled for movement during the predeployment activities phase are physically moved from origin to the designated APODs/SPODs.  The movement phase of the joint deployment and redeployment process includes self-deploying forces and forces requiring lift support and is composed of movement from origin to POE, POE operations, and movement from the POE to POD. However, for joint deployment to produce a seamless, end-to-end deployment movement process, consideration should be given to movement that extends beyond the POD.
b.  This chapter discusses each of the deployment movement segments in greater detail, as well as tracking and controlling the movement of forces and materiel through the deployment and redeployment processes.  Movement control involves planning, routing, scheduling, and controlling common-user assets and maintaining ITV of forces and materiel executing deployment and redeployment operations.  Properly resourced and executed movement control assists commanders in force tracking and provides the capability to adjust the flow as necessary.  It enhances JRSOI of personnel, equipment, and supplies moving over LOCs IAW command directives and responsibilities.  This chapter also includes important movement reporting requirements to enhance ITV.  Force visibility provides AV for deploying units and supplies and allows for a more responsive supply system.  Lastly, when employment draws down, this chapter covers redeployment movement of personnel, equipment, and materiel to home and/or demobilization stations or transfer of forces and materiel to support operational requirements of another JFC.

## 2.  Movement Considerations

a.  **General.**  During deployment or redeployment, forces requiring movement comprise three general categories:  self-deploying forces, forces requiring intertheater and intratheater common-user airlift support, and unit movements involving a combination of self-deployment and common-user airlift support.  For example, USAF aircraft squadrons routinely require intertheater and intratheater common-user airlift support to deploy a majority of their ground support capability as the flight crews self-deploy.  Self-deploying forces, to include CAAF, may move directly from origin to a JRSOI or an employment location.  Self-deploying forces are reflected in the TPFDD to arrive at their designated location in theater based on the EAD/LAD.  Lift-supported movements may be divided into three segments:  movement from origin to POE (usually the responsibility of the supporting CCDR or Service with planning and coordination support from USTRANSCOM), POE operations, and movement from the POE to the POD.  Intratheater common-user airlift that occurs beyond the POD is the responsibility of the GCC or Service, but may be supported by USTRANSCOM using common-user airlift assets if available.
b.  **Management of Change.**  Effective deployment execution involves successfully coping with change.  More specifically, timely and responsive deployment and redeployment operations are a direct function of the executing command's ability to manage changes in joint force organization, phasing, employment sequence, or circumstance and maintain control of deployment execution.  Whenever possible, efficient use of scarce resources should be the objective.  Managing change in a dynamic environment is best accomplished in a collaborative manner.  Optimizing the deployment process is a combat multiplier that enhances joint force effectiveness.

c.  **Deployment and Redeployment Changes.**  TPFDD and movement schedule changes during deployment and redeployment execution are inevitable.  Authorities to make changes vary based on the number of days the movement schedule will be adjusted.
Both the GFMIG and CJCSM 3130.06, (U) Global Force Management Allocation Policies and Procedures, provide guidance on change authorities.  Changes in mission requirements, OE, or unanticipated circumstances may cause the JFC to modify the organization of forces, command relationships, phasing, or sequence of force employment. Late decisions or changes regarding transportation modes or routing, LOCs, POEs and/or PODs supporting deployment and redeployment may have a significant negative impact on the operation and may cause delayed satisfaction of requirements, delayed movements, bottlenecks at transportation nodes, and increased transportation costs.  More importantly, an impeded deployment may jeopardize mission success.

d.  **Managing the Impact.**  Since changes during deployment and redeployment execution are inevitable, the JFC's staff must anticipate adjustments and manage the impact of changes to avoid disrupting or impeding the force flow.  Prior planning is the key. Management of change is possible if changes are held to a minimum and require supported CCMD approval.  The JFC's staff also:

## Operation Joint Endeavor

"For the first few weeks of the deployment, the time-phased force deployment data changed an average of 14 times per day.  The result was confusion about what was to be loaded on the aircraft at the aerial ports of embarkation.  Army units showed up unexpectedly at the aerial port of embarkation for air transportation, and aircraft arrived at airfields for units that were not there."
Description and Lessons Learned
(Planning and Deployment Phases)

(1)  Should understand and anticipate changes;
(2)  Provides resources at critical sites to ensure timely reporting of changes;
(3)  Develops flexible, responsive steps, at all levels, to capture and properly document changes;
(4)  Synchronizes all aspects of the required change (e.g., adjusted force flow may require different staging or support); and
(5)  Ensures requested changes are consistent with the commander's intent and CONOPS.

e.  **Movement in Support of HD and DSCA.**  Deployment operations within the homeland follow the same processes as outlined in the preceding paragraphs; however, the timelines can be extremely compressed.  The national importance of these missions is reflected in the elevated movement priorities that can be invoked by the President or SecDef.  USTRANSCOM can quickly assemble aircraft and flight crews for operations where expedited passenger movement is required.  Surface transportation (commercial and organic) can be a viable option in those situations where the distance between the home station and the OA is relatively short.  Coordination with the NGB is essential when using Air National Guard/Army National Guard assets for support of HD or DSCA.  In some instances, state and federal forces may be in the same OA.  Coordination between state and federal forces should occur to achieve unity of effort.

For more information on deployment within the homeland, see JP 3-27, Homeland Defense; *JP 3-28,* Defense Support of Civil Authorities; *and CJCSI 4120.02,* List of Priorities-DOD Transportation Movement Priority System.

## 3.  Movement Control

a.  **General.**  Movement control involves planning, routing, scheduling, and controlling common-user assets and maintaining ITV of forces and materiel moving through the deployment and redeployment processes.  Successful employment of military forces depends on assured and timely deployment and support.  Movement control coordinates transportation resources to enhance combat effectiveness and meet the deployment/redeployment and sustainment priorities of the supported CCDR.  Effective movement control during deployment operations provides the JFC with the capability to monitor and manage movement execution and adjust the flow of forces and materiel as necessary.  It provides for mechanisms to coordinate and deconflict movements and priorities for limited road space, constrained common-user airlift assets, and cross boundary/activities.  In such conditions, the commander and staff should anticipate requirements to identify demands for joint support, prioritize among operations or force element, and communicate extensively with other affected components.  Visibility of deploying forces and materiel is established by AV systems such as IGC, Global Decision Support System (GDSS), Single Mobility System (SMS), and the common operational picture (COP) provided by GCCS-J and GCSS-J.  USTRANSCOM facilitates this effort by providing movement summaries of TCC and organic movements from departure to final destination in theater in coordination with the supported and supporting commanders. USTRANSCOM provides analysis of movement execution to the JS, supported CCMDs, and supporting commands and agencies.  This analysis includes progress reports, status, problems, port workloads, daily movement statistics, and resolution of problems encountered with intertheater and intratheater common-user transportation means.  In addition, movement control must be coordinated and synchronized with JRSOI and a TDCP that describes the in-theater network and system for distribution management. JRSOI focuses on building mission-capable forces as quickly as possible.  TD focuses on establishing a distribution management structure and battlefield architecture to maintain visibility and control over forces and materiel arriving for employment in theater.
b.  **Organization for Movement Control.**  The supported CCDR has a wide range of options for performing movement control.  These options include directing subordinate JFCs and Service component commanders to perform their own movement control or creating a fully integrated joint organization.  Regardless of the movement control option selected, the GCC should task organize the movement control function commensurate with the mission, scope of operations, and geography of the OA.  Normally, the GCC delegates OPCON of the various parts of the transportation system to the most capable Service components, but retains the authority to set priorities and distribute resources and makes the final determination of transportation mode and sources.  The GCC exercises this authority through a theater joint transportation board or JDDOC.  Alternately, the GCC may assign the responsibility to a staff element (normally the command's senior logistic staff officer) who coordinates closely with the operations staff.

c.  **Strategic Movement Control.**  Effective strategic movement control requires the coordinated efforts of USTRANSCOM, supporting CCDRs, FPs, the supported GCC, and their components.  Strategic movement control begins with identifying total joint force movement requirements and translating those requirements into logistic terms (e.g., barrels, short tons, square feet, passengers [PAX]).  These movement requirements are documented in the appropriate TPFDD and scheduled for movement in the sequence and priority validated by the supported GCC.  Planning focuses on time-phasing movements and assigning transportation resources to support operations for a set period.  In time constrained scenarios, early identification of the force and its movement requirements in a collaborative environment are key to rapid movement planning and execution.
(1)  USTRANSCOM uses the TPFDD to analyze the flow of forces and materiel from their points of origin to final destination in theater.  They distribute the strategic transportation resources and make adjustments, as necessary, to ensure the unimpeded flow of forces and materiel to the final destination in theater.  During this process, CDRUSTRANSCOM follows CJCS guidance and coordinates major decisions with the supported CCDR.

For additional information on TPFDD analysis and transportation planning, see JP 5-0, Joint Planning, *and CJCSM 3122.02,* Joint Operational Planning and Execution System
(JOPES) Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution).

(2)  USTRANSCOM Deployment and Distribution Operations Center
(DDOC).  The DDOC directs the global air, land, and sea transportation capabilities of the DTS to meet national security objectives provided by DOD.  The DDOC fuses capabilities of multimodal movement and distribution operations, intelligence, force protection, capacity acquisition, resource management, and other staff functions to collaboratively provide distribution options to the warfighter.  C2 of the majority of intertheater lift forces and logistic infrastructure is accomplished through the DDOC, which tracks the movement requirement from lift allocation and initial execution through closure at final destination through their support teams.  The support team construct provides better upfront planning through collaboration with the supported commander and other key stakeholders.  This allows the process to stay in step with commander's intent as the operation unfolds and increases visibility of all movement requirements. The geographical orientation of support teams enables a holistic view of all warfighter requirements, provides an opportunity to conduct a thorough transportation analysis, reduces correspondence management, leverages collaboration technologies, and enables aggregation of requirements within movement windows.

(3)  **JDDOC.**  The integration of intertheater and intratheater movement control is the responsibility of the supported CCMD and USTRANSCOM.  The JDDOC is a GCC movement control organization designed to synchronize and optimize national and theater multimodal resources for deployment, distribution, and sustainment.  The JDDOC is normally placed under the control and direction of the logistics directorate at the CCMD level, but may also be placed under other command or staff organizations.  The DDOC and JDDOC collaborate to link strategic deployment and distribution processes to operational and tactical functions in support of the warfighter.
(4)  **Joint Movement Center (JMC).**  The JMC may be established at a subordinate unified or JTF level to coordinate the employment of all means of transportation (including that provided by allies or HNs) to support the CONOPS.  This coordination is accomplished through the establishment of theater and JTF transportation policies within the assigned OA, consistent with relative urgency of need, port and terminal capabilities, transportation asset availability, and priorities set by a JFC.  The JTF JMC will work closely with the JDDOC.

(5)  **Theater Movement Control.**  The supported GCC controls intratheater movement.  Theater movement control plans should provide the supported GCC with the highest practical degree of influence or control over movement into, within, and out of theater.  The same movement control functions used for strategic movement control should be applied to perform theater movement control.  Regardless of the option selected, the theater movement control system must allow the supported GCC the capability to plan, distribute, coordinate, deconflict transportation requirements, and track the movement of forces and materiel in theater.  Moreover, the theater movement control plan must coordinate incoming strategic movements with the TDCP and theater JRSOI operations.
For additional information on theater movement control and TD, see JP 4-09, Distribution Operations.

## 4.  Movement A.  **Movement From Origin To Poe**

(1)  Validated movement requirements developed during the deployment planning phase and scheduled for movement during predeployment activities phase are moved by some mode of transportation from point of origin to designated APOEs/SPOEs (when not co-located).  The supported CCMD selects the APOE/SPOE as a part of the validation process in coordination with its components, USTRANSCOM, and FPs.
OCONUS APOEs/SPOEs are selected by the supported CCMD in coordination with its components, FPs, and USTRANSCOM.  Airlift and sealift schedules are prepared by USTRANSCOM and coordinated with the supported CCMD.  SDDC provides call forward instructions to the base/installation transportation or traffic management offices using a port call file message for deployment movements via sealift using procedures outlined in the DTR.
(2)  Equipment of deploying forces may either self-deploy or be transported to the POE by commercial rail, truck, or barge.  Using the planning factors developed in the earlier stages of the deployment process, the base/installation transportation office requests the necessary DOD and/or commercial transportation assets (e.g., railcars, trucks, containers) to meet validated movement requirements.

## (3)  **Surface Movement** (A)  **Military Convoy**

1.  Units may convoy to the POE.  The unit reviews policy and guidance for public highway use in CONUS and convoy procedures that apply during peacetime, mobilization, and deployment.  Procedures for highway movement OCONUS (to include Hawaii and Alaska) are found in local command regulations and policies.

2.  Organic convoy operations are not visible to USTRANSCOM
during peacetime movement.  US convoy movements are the responsibility of the respective Service or FP and must be scheduled consistent with SDDC call forward instructions or AMC published strategic lift schedules to ensure correct arrival times at assigned POEs.

For further information on organic convoy operations, see DTR 4500.9-R, Defense Transportation Regulations*, Part III,* Mobility.

(b)  **Rail.**  In the US, the deploying unit determines its movement requirements and submits them through command channels to the installation transportation officer (ITO) or traffic/transportation management office.  The ITO or traffic/transportation management office, in coordination with SDDC, can obtain both commercial and military rail assets based on unit requirements.  ITO or traffic/transportation office personnel validate railcar requirements based on unit rail load plans and the shipping configuration of the items to be deployed to maximize the available loading space to efficiently use rail assets and reduce the carrier's transportation charges.
(c)  Commercial Movement.  Unit vehicles and equipment that do not convoy to the POE using military transport typically move by commercial transportation.

1.  **Commercial Truck.**  The unit movement officer forwards requirements for commercial trucks to the ITO or traffic/transportation office who reviews the movement requirement and coordinates with SDDC for commercial transportation.

2.  **Barge.**  In some cases, unit equipment is moved to the POE by commercial barges operating over inland and coastal waterways.  The unit movement officer forwards requirements for commercial transportation to the ITO or traffic/transportation office who reviews the movement requirement, determines if barges are an option, and coordinates barge transport with SDDC.  Unit movement officers coordinate with SDDC (or its forward stationed elements) for specific requirements at the barge loading and discharge sites.

3.  **Commercial Vessels.**  All cargo authorized for movement in DTS is reported to USTRANSCOM and then routed to the appropriate component in SDDC who evaluates the cargo to determine the most cost-effective and expeditious commercial vessel options to use.  The Service components consider relevant factors such as vessel schedules, costs, and other customer requirements to determine the best vessel option. USTRANSCOM will consider vessels already under charter and activated sealift vessels. Should neither be available, USTRANSCOM will first offer cargo movement to commercial industry.  If commercial service is not available or there is documented negative critical mission impact, USTRANSCOM may offer the cargo to MSC for activation of additional government-owned assets to move the cargo.

For further information on commercial movement, see DTR 4500.9-R, Defense Transportation Regulations, *Part II,* Cargo Movement.

## B.  **Poe Operations**

(1)  **APOE.**  AMC is the DOD-designated SPM for all worldwide commonuser/commercial aerial ports.  APOE operations are divided into four areas: marshalling area, alert holding area, call-forward area, and ready line/loading ramp area.  Operating within these areas is the deploying unit; the A/DACG and mobility forces, to include the contingency response element; and the load teams.  Movement and documentation of equipment and personnel to the APOE may be in preparation for movement by commercial charter aircraft.  If this is the case, actions at the APOE will be IAW commercial carrier instructions and Joint Travel Regulations.
For further information on activities at the APOE, see DTR 4500.9-R, Defense Transportation Regulations, *Part III,* Mobility.

## (2)  **Spoe**

(a)  SDDC is the DOD-designated SPM for all worldwide commonuser/commercial seaports.  Units deploy equipment and supplies by sea through a port that is generally commanded or contracted by SDDC.  Where SDDC does not have a transportation terminal battalion or other contractual agreements, an SDDC support team may temporarily manage cargo at the SPOE.

(b)  USTRANSCOM directs the deployment of units and sustainment through SPOEs identified in the TPFDD.  The port call message identifies the earliest/latest dates the unit must arrive at the SPOE for movement processing and vessel loading and gives the unit special instructions for a successful movement to the SPOE.
USTRANSCOM's responsibilities include evaluate movement requirements and coordinate vessel selection between SDDC and MSC; prepare and issue port call messages;
receive PSAs and direct their activities; receive, stage, and transship unit equipment in the port; establish and direct port communications; enforce safety and physical security policies and procedures; develop stow plans; supervise vessel loading; inspect vessel readiness; and provide documentation.  The cargo manifest is documented in Global Air Transportation Execution System (GATES) so the receiving organizations at the SPOD and installation can be prepared to receive the equipment.  For movements originating in foreign countries, supporting commands and the Service transportation component coordinate with the JDDOC and SDDC forward operating elements to plan and execute the movement of forces to the POE.
For further information on sealift movements, see DTR 4500.9-R, Defense Transportation Regulations, *Part III,* Mobility, *and JP 4-01.5,* Joint Terminal Operations.

c.  Movement from POE to POD requires designated authorities.  From the APOE/SPOE, deploying forces move to the APOD/SPOD by obtaining a country clearance.  In situations that require rapid response or joint integration, traditional Service port opening/operating forces may not be sufficient.  While all Services have the organic capability to execute theater opening functions, USTRANSCOM's JTF-PO provides the supported GCC rapid port opening capability to facilitate crisis response in austere environments, and the Air Component Command manages APACS [Aircraft and Personnel Automated Clearance System] for the GCC.  The task force is designed to be in place in advance of a deployment of forces, sustainment, or humanitarian/relief supplies. JTF-PO deploys with seven days of supply.  APOD forces are ready to deploy within 12 hours, SPOD forces within 36 hours, and both are designed to operate for 45-60 days and then redeploy or be relieved by follow-on forces.  Transit times and other limitations associated with movement to POD differ by port, mode, cargo type, and diplomatic authorities.  Each has to be evaluated during planning and managed closely during execution.  A smooth and coordinated flow of requirements through ports is essential. USTRANSCOM can provide planning assistance for transload and transshipment operations and factors.

## 5.  Force Visibility

a.  The integrated use of C2 systems and IT makes force tracking through the deployment and redeployment processes possible.  The key data that enable force tracking are the FTN, transportation tracking account number (TTAN), and the ULN.  Visibility of deploying forces and materiel is established through the logistics management construct of AV and the GCCS-J COP.  AV is possible through integration of the capabilities provided by automatic identification technology (AIT); ITV; and the information systems and decision support tools comprising the IGC, GCSS-J, SMS, and the Web SM sub-system of JOPES.  Control of the deployment and redeployment processes is exercised through the C2 capabilities of GCCS-J.  See Figure V-1 on force visibility.
For additional information on the COP, see CJCSI 3151.01, Global Command and Control System Common Operational Picture Reporting Requirements.

b.  **Unit Movements.**  For non-self-deploying forces, unit moves involve various combinations of assets to transport personnel, unit-related supplies, and equipment.  Force tracking is focused on maintaining visibility of these separate unit shipments from origin to destination and through redeployment.  Force tracking includes monitoring the elements of a unit until they are reassembled under the commander's control as a mission capable force.  It continues until all units that constitute the specified force assemble and authority transfers back to the supported commander.  It further continues through redeployment.
The supported CCDR assigns each force requirement a unique FTN.
c.  AV.  AV provides the capability to determine the identity, location, and status of forces, equipment, and supplies by class of supply, nomenclature, and unit.  It includes the ability to determine the status of personnel and patients.  It provides visibility over equipment maintenance and retrograde actions.  It also includes the capability to act upon that information to improve the overall performance of DOD logistic practices supporting operations.  AV requires horizontal integration of supply and transportation activities and one-time data capture.  AV includes in-process, in-storage, and ITV.  The function of performing AV is a shared responsibility among deploying forces, supporting commands and agencies, USTRANSCOM, and the supported CCDR.  IGC provides the JFC the ability to make decisions based on actionable logistics information to ensure supply and in-transit data is shared and fused, resulting in a complete seamless picture for end-users. This includes deployment and sustainment operations.  Through AV, commanders and staffs can determine whether specific items of supply are readily available in the logistic system or must be deployed with the unit.  AV results from the integration of requirements and information systems from four areas: requisition tracking, visibility of assets in-storage or in-process, visibility of assets in-transit, and asset management within the theater of operations.  In each case, a specified "data repository" serves as a central hub for asset information and visibility.
(1)  **Requisition Tracking.**  The logistics online tracking system provides visibility over the status of requisitions.  This system also provides status information to IGC to enable it to provide accurate status information when a requisition is in-transit.

(2)  **Assets In-Storage or In-Process.**  The assets in-storage of each inventory control point will provide visibility of assets that are in-storage or in-process (assets being procured or repaired).
d.  **ITV.**  ITV, as a component of force visibility, preserves the link between the intransit force and that force's mission within an operation phase through the ULN.  ITV is the ability to track the identity, status, and location of DOD units, non-unit cargo (excluding POL), PAX, medical patients, and personal property from origin to consignee or destination across the range of military operations as part of AV.

(1)  The TTAN is a non-editable, 13-digit, random number generated by JOPES
and links unclassified transportation schedules, movement, and manifest information with classified force plans without compromising OPSEC.
(2)  IGC is the designated DOD system for ITV during the movement phase of deployment and redeployment.  IGC collects ITV information from distribution source systems, Service systems, and commercial systems and then distributes ITV information to customer, Service, and joint systems.  The provision of initial carrier manifest information is the responsibility of supported and supporting commands through their commanders of deploying and redeploying forces.  IGC provides this information to Web SM.  In conjunction with the use of force modules, this permits the JPEC to monitor and subsequently influence common-user and non-common-user lift as well as self-deploying units.  Data quality is directly linked to data collection and entry at the POE and POD and requires appropriate commander emphasis to ensure its accuracy.

(3)  A TPFDD identifies all the movements associated with a specific operation.
Operation/force ITV, phase and mission ITV, and force requirement visibility are provided by a well-structured TPFDD.  Structuring the TPFDD to provide ITV at this level is the responsibility of the supported commander.  This level of visibility is required to monitor and project force closure.  This level of visibility is enabled by accurate and timely movement reporting, compliance with transportation procedures and schedules, and properly prepared personnel/cargo accompanied by accurate shipping documents.
Effective interfaces between JOPES, Service deployment systems, and transportation systems are essential.  During execution of a deployment, all deviations should be reported to the Service, global force manager, and the supported commander immediately to minimize operation impact and to ensure rapid resolution of process, training, or interface failures.  See Figure V-2 on ITV.

(4)  **Accurate Data.**  Use of JOPES is directed.  ITV begins with the use of JOPES and depends upon accurate, disciplined adherence to TPFDD movement validation, allocation of scheduled lift, and manifesting procedures.  Deploying forces are responsible for confirming accurate force data via the TPFDD verification and validation process.  The supported CCDR ultimately validates those ULNs that require USTRANSCOM lift.  Shippers submit accurate and timely data for strategic lift IAW the DTR and GATES.  Accurate ITV is enabled by accurate movement reporting, compliance with transportation procedures and schedules, properly prepared personnel manifests, and

Operation/Force:
The ability to see all in-transit forces with
their combat support and combat service support that are tasked against an operation plan/order, while they are deploying, redeploying, or rotating and distinguish those forces from forces intransit to other operations.
Joint Phase/Mission:
Ability to distinguish all units/components aligned against a specific phase of an operation.
Unit/Force Requirement:
Ability to distinguish all parts of a force requirement/capability as an entity during movement.
Transportation:
Ability to track individual transportation/ movement missions from origin to destination.
In-the-Box:
Ability to identify the contents of a container in-transit and in port.

cargo accompanied by accurate shipping documents including TTAN and transportation tracking number.
(5)  **Movement Reporting.**  Accurate and timely reporting begins with the deploying force.  However, ITV involves many participants who must follow designated procedures to ensure accurate source data, timely updates, and shipment status information.  Those participants include, but are not limited to, deploying units, port operators, commercial transportation service providers, contractors, installations, depots, and contingency locations.  Each has a key role in ensuring relevant, accurate, timely, usable, complete, precise, and secure data is provided to support ITV.  Required data includes passenger, cargo, schedule, and movement information to IGC.  IGC receives movement data from various systems from the point of origin, through the POE and POD, within the US and theater.  Generation of DTR compliant deployment data is the unit responsibility.  GATES is the single POE and POD system for sealift and airlift manifesting.

(6)  **Force Tracking.**  Force tracking during deployment and redeployment is vital to overall joint force readiness.  Unit integrity should be maintained, to the maximum extent possible, and commanders must have the capability to determine the exact location of unit personnel, equipment, and materiel in the event the deploying or redeploying force must be diverted en route to another mission.  USTRANSCOM tracks forces and equipment embarked on common-user strategic lift using ULNs and transportation control numbers.  IGC is the central repository for visibility of assets intransit from origin to destination, including all military, government, and vendor documented shipments.  The IGC database contains shipment status information, booking information, passenger reservation information, aircraft and ship manifests, personal property data, medical patients' information, and vessel and aircraft scheduling data.  IGC integrates the automated movement control systems used by the Services, DOD agencies, and USTRANSCOM, providing the capability to track unit movements and sustainment operations globally.

e.  **AIT.**  AIT enables the capture of current and accurate source data through the use of various technologies such as: bar codes, RFID tags, and satellite/communication links. AIT integration with logistics information systems is key to the AV effort.

## 6.  Redeployment

Movement in support of redeployment relocates forces to support a new mission in another OA or to return them to their home or demobilization station.

a.  **Force tracking during redeployment operations** is vital to joint force readiness.
Redeployment is not complete until the joint force has completed movement through the redeployment pipeline and emerged at the prescribed destination.  Unit integrity should be maintained, to the extent possible, and commanders use their capabilities to determine the exact location of unit personnel, equipment, and materiel in the event the redeploying force has to be diverted en route for another mission.  Redeployment force tracking uses the same systems and procedures discussed for deployment operations.

b.  **Requirements Validation.**  Movement execution begins with validation of the movement requirements in JOPES.  Requirements validation for redeployment is conducted using the same process used during deployment operations.  Redeploying units confirm readiness, movement available dates, PAX, and cargo details to their higher commands that verify total unit movement requirements to the GCC.  The supported CCDR receives component redeployment data, merges this data into the redeployment TPFDD, and makes adjustments to the redeployment flow as necessary.  Once adjustments are complete, the supported CCDR validates the lift requirements within the specific TPFDD movement window for USTRANSCOM movement scheduling by confirming that the TPFDD accurately reflects current movement requirements.  USTRANSCOM conducts a transportation feasibility review and coordinates unresolved transportation conflicts with the supported CCDR for resolution.  The end result of this process is a supported CCDR approved redeployment TPFDD that units use to prepare for movement.

c.  **Schedule Movement.**  Movement scheduling is an iterative process conducted at every level of command with the objective of getting the right personnel, equipment, and materiel to the right place at the right time.  Once validated TPFDD requirements are received from the supported CCDR, strategic lift assets are scheduled and registered in JOPES.  These movement schedules are also utilized by commands supporting redeployment operations for movement planning, coordination, and execution.  After strategic lift schedules are developed, units and/or installations receive call forward messages from USTRANSCOM elements in theater directing movement to SPOEs in designated time windows.  Airlift schedules are published and are visible in JOPES, GDSS, and SMS.  Instructions are issued which generally require the redeploying cargo to arrive at the designated aerial port 24 hours prior to scheduled lift.  Redeploying commands assess their ability to meet strategic lift schedules, make adjustments, and plan unit moves accordingly.  Lift shortfalls and available lift are identified to the TCCs.  Prior to redeployment, movement control elements confirm movement clearances with HN agencies.

d.  **Redeployment movements** are governed by the supported CCDR's redeployment plan and policies and the theater movement control plan.  As with deployment, there are three distinct segments during the movement phase of the redeployment process.

(1)  **Movement to POEs.**  Some units may move to the POE with organic lift assets.  However, the majority of redeploying units may require a combination of organic and theater transportation assets.  Organic lift movements are normally coordinated by the redeploying unit and controlled by the established theater movement control organization.  The theater movement control organization is responsible for management of common-user movements to the POEs as well as synchronization and integration of intertheater lift with intratheater movements to ensure an optimum flow of forces and sustainment into and out of the theater.

(2)  **Conduct POE Operations.**  Activities at the POE focus on marshalling, capturing ITV data, and loading individuals, unit equipment, and materiel on designated transportation assets.  POE operations begin the strategic leg of the redeployment process and are managed by USTRANSCOM.  Essential actions are performed at the POE to complete unit movement responsibilities.  Unit personnel, equipment, and materiel are staged and sequenced in the unit marshalling areas.  Inspections are conducted in the alert holding area and/or call forward areas IAW the DTR and the redeployment plan.  Aircraft and vessels are loaded and manifests are documented in the appropriate automated system to allow receiving APODs, SPODs, and installations to prepare for their arrival.  Throughout the movement phase of the redeployment process, movement reporting is required and essential.
(3)  **Movement to PODs.**  Strategic movement from POE to POD for non-selfdeploying units is controlled by USTRANSCOM.  Force tracking during redeployment operations is vital to assessing joint force readiness.  If specified in the redeployment plan, unit integrity should be maintained to the extent possible and commanders should have the capability to determine the exact location of unit personnel, equipment, and materiel in the event the redeploying force needs to be diverted en route for another mission.  The tracking of units during redeployment uses the same systems and procedures discussed for deployment operations.

For more information on redeployment JRSOI, see Chapter VI, "Joint Reception, Staging, Onward Movement, and Integration."  For more information on redeployment responsibilities, see CJCSM 3122.02, Joint Operation Planning and Execution System
(JOPES) Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution).



## Chapter Vi Joint Reception, Staging, Onward Movement, And Integration

"As we have learned many times, the US [United States] can ship supplies and materiel to an objective area much more effectively and efficiently than the objective area can unload and distribute those supplies."

## 1.  General

a.  This chapter presents an overview of the final phase of deployment and redeployment, JRSOI.  The JRSOI phase of the deployment/redeployment process facilitates the transition between the execution functions of deployment and employment.  This chapter discusses the segments, describes the principles, and identifies the essential elements of JRSOI as they support and enhance the JFC's ability to achieve objectives.  JRSOI is a set of dynamic and complex activities involving numerous organizations requiring training, continuous coordination, and collaboration.  One common element of JRSOI is a change in command relationship.  During an initial deployment, responsibility for planning and executing JRSOI belongs to the supported CCDR.  During redeployment, the responsibility for JRSOI operations is determined by the post-redeployment mission of the redeploying force (forces may be redeploying to a new OA or returning to home/demobilization station).
(1)  Redeployment for further employment will involve JRSOI in the new OA.
During deployment or when a force is redeploying to support another JFC's operational requirement, the OPCON or tactical control (TACON) of the deploying force will change from the losing commander to the gaining commander.
(2)  When redeployment is to home station or demobilization station, the supported commander relinquishes OPCON/TACON to the supporting commander.  This supporting commander is typically the original parent (gaining) command for assigned forces or a Service for Service-retained forces.  Redeployment to home and/or demobilization station will involve POD JRSOI coordinated and executed by the Services and USTRANSCOM for common-user PODs and by the respective Service or unit for forces redeploying by organic assets to non-common-user PODs.

(3)  Process seams and friction may occur at functional or organizational interfaces when physical resources and information are transferred.  JRSOI, like the deployment process itself, requires continuous planning.  The JRSOI activities described in this chapter apply to both deployment and redeployment; however, there are significant differences depending on whether the force is deploying or redeploying into a new OA or redeploying back to home or demobilization station.
b.  **Segments of JRSOI.**  JRSOI is the essential process that transitions deploying or redeploying forces, consisting of personnel, equipment, and materiel into forces capable of meeting the CCDR's operational requirements or returns them to their parent organization or Service.  The four segments of JRSOI are described below.
(1)  **Reception** operations include all those functions required to receive and clear personnel, equipment, and materiel through the POD.
(2)  **Staging** assembles, temporarily holds, and organizes arriving personnel, equipment, and materiel into forces and capabilities and prepares them for onward movement, tactical operations, or Service reintegration.

(3)  **Onward Movement** is the process of moving forces, capabilities, and accompanying materiel from reception facilities, marshalling areas, and SAs to TAAs and/or OAs or onward from the POD or other reception areas to the home/demobilization station.

(4)  **Integration** is the synchronized transfer of capabilities into an operational commander's force prior to mission execution or back to the component/Service.

c.  The supported CCDR is responsible for JRSOI during deployment and redeployment, when the redeployment is to support another JFC.  This includes all actions required to make arriving units operationally ready and integrated into the joint force.  During redeployment to home station, the designated command, Service, or agency assumes responsibility for returning units and personnel when OPCON is relinquished IAW an appropriate order.  The receiving command then establishes the command relationships and plans and executes JRSOI.  The latter task is normally assigned to a Service component or the Service itself.
(1)  During JRSOI, the capability of strategic lift to move personnel, equipment, and materiel to reception points (e.g., POD) must be matched by the capability to receive and process the force.  The CCDR must have visibility of both deployment and redeployment flows to control the rate as well as the sequencing and processing of deploying and redeploying forces.
(2)  Although the supported CCDR is responsible for JRSOI and other facets of logistics support, this does not relieve supporting commanders of responsibility for detailed oversight of both the deployment and redeployment flow and coordinating changes with the supported commander, when appropriate.

d.  JRSOI is an integral part of an operation that enables the assembly of required capabilities for application by the JFC.  Successful JRSOI requires command emphasis in planning, training, and synchronization in a collaborative environment.  Even self-sustaining units that arrive in-theater are heavily dependent on external support until they are reunited with their equipment and become operational.  As deploying units assemble, efforts focus on preparing for future operations and integrating into the joint force.
e.  JRSOI provides a common framework to focus joint and Service component capabilities on land, at sea, and in the air into a coherent operation.  The context of each JRSOI process may vary, reflecting the nature of the operation; mission, enemy, terrain and weather, troops and support available-time available (METT-T); and civilian considerations. However, deploying forces or non-unit personnel, whether affiliated with a Service or CAAF, normally undergo some form of reception, staging, onward movement, and integration.  For example, a fighter squadron and other self-deploying forces may complete JRSOI in a few hours at the reception point or aerial port.  Other units may require days or weeks to complete the entire process.

## 2.  Principles Of Joint Reception, Staging, Onward Movement, And Integration

a.  There are three overarching principles of JRSOI: unity of command, synchronization, and balance.  These principles can assist commanders and their staffs in the planning and execution of JRSOI.  CCDRs should consider these principles when planning JRSOI operations.
b.  **Unity of command** ensures unity of effort under one responsible commander for every objective.  In the context of deployment and redeployment operations, this is the supported CCDR.  The CCDR adjusts resources based upon the deployment flow into the theater.  The CCDR also controls the movement of forces in the AOR, provides support to personnel arriving into the theater, and centrally coordinates the efforts of all other key players in the JRSOI process to include supporting CCDRs.

c.  **Synchronization** links deployed personnel, equipment, and materiel in a timely manner.  A well-synchronized flow expedites buildup of mission capability and avoids saturation at nodes and along LOCs, thereby enhancing survivability.  Synchronization requires detailed joint planning, intelligence driven situational awareness, timely and predictable airflow and seaflow, visibility of assets moving through the pipeline, and the ability to adjust movement schedules.  Synchronization occurs when the right units, equipment, supplies, and capabilities arrive in the correct order at the appropriate locations, and supporting activities are coordinated in such a fashion to operate in consonance with one another so the tempo of force deployment, planning, and execution is uninterrupted.  This enhances C2 and helps maintain unit integrity.  Managing the timing of the TPFDD flow up to the point of movement is a key activity for ensuring the arrival time of personnel, equipment, and materiel coincide.  Force planners and supporting TCCs must ensure unit integrity is a dominant consideration when planning unit and equipment deployment and/or movement increments to their supporting transportation load plans and movement schedules.
d.  **Balance** applies to managing the TPFDD flow.  Managing the TPFDD allows the supported CCDR to adjust the movement schedule for units as mission requirements or conditions change.  AV further provides users with timely and accurate information on the location, movement, status, and identity of units, personnel, equipment, and supplies. Balance is especially relevant to the relationship between deployment and TD.  To achieve balance, the flow through the intertheater pipeline and the intratheater network must be regulated and integrated to allow a continuous and controlled flow of forces and sustainment into and within the AOR.  Supported CCDRs regulate the transportation flow by ensuring adequate support and reception assets, effectively coordinated through a theater reception plan, are available or deployed early in the movement schedule to facilitate JRSOI.  Balance is improved by minimizing handling, the number of transfer points, and the number and variety of carriers.  Past experience shows the more points of entry into the OA, the more difficult it is to maintain accurate personnel accounting and strength reporting.  The JFC can avoid saturation, enhance survivability, and achieve balance by directing personnel, equipment, materiel, and information flow at a rate that can be accommodated at every point along the entire network, from origin to destination.  The OE, CONOPS, and available infrastructure are major considerations in determining how to balance the transportation flow and sequence the arrival of combat, combat support, and force sustainment assets in theater.

## 3.  Elements Of Joint Reception, Staging, Onward Movement, And Integration

a.  JRSOI relies on the essential elements in Figure VI-1 to achieve unity of command, synchronization, and balance.  These elements combine in various ways under differing circumstances to make the operations associated with JRSOI possible.
b.  Communications systems are the means by which the CCDR achieves unified action to balance and synchronize joint force activities and accomplish mission success.  Joint forces operate in diverse environments and conduct a variety of operations as part of multinational or interagency teams.  Rapid deployment, extended LOCs, and potential forcible entry prior to establishing operations in logistical bare-based areas require a communications system infrastructure (to include AV information) that is interoperable, flexible, responsive, mobile, disciplined, survivable, and sustainable.

(1)  JRSOI operations require effective communication systems with responsive leaders and managers.  Communication systems must link the supported CCDR, supporting CCDRs, Service components, deploying units, JRSOI support organizations, and the tactical commanders who will integrate the deploying forces and capabilities into their commands. Reporting and information systems must provide accurate, relevant, and timely information to the appropriate staffs and leaders to plan, integrate, direct, and execute their assigned part of the JRSOI operation.

For more information, see CJCSM 3122.01, Joint Operation Planning and Execution System (JOPES) Volume I (Planning Policies and Procedures).
(2)  Effective communication systems are responsive to the supported CCDR for deployment and JRSOI management.  The supported CCDR should be able to influence the outcome of the deployment.  To do this, the commander must know what force capabilities are available and what capabilities will be available in the future.  METT-T-

## Elements Of Joint Reception, Staging, Onward Movement, And Integration

| Essential Elements                   | Enabling Elements     |
|--------------------------------------|-----------------------|
|                                     |                      |
| Communication systems                | Host-nation support   |
|                                     |                      |
| Force protection                     | Multinational support |
|                                     |                      |
| Support organizations and structures | Contract support      |

influenced changes may cause certain units to be in high demand or needed for immediate employment.  Communication systems enable JRSOI C2 elements to locate these units and divert resources to expedite their onward movement.
For additional information on joint communication systems planning guidance, see JP 6-0, Joint Communications System.

c.  Commanders enforce requisite protection measures consistent with the threat.  For JRSOI, the challenge is to protect those forces configured for deployment that are geographically dispersed and possess limited self-protection capability.  Risk must be assessed and comprehensive protection plans developed to address vulnerabilities and to counter potential threats to forces, infrastructure, and information systems.  Effective and efficient JRSOI operations can reduce force vulnerability by ensuring units quickly complete the process.  Balance and synchronization ensure forces do not remain static in vulnerable situations and are facilitated by:
(1)  Achieving balance so personnel, equipment, and materiel arrive nearly simultaneously;
(2)  Minimizing the force footprint by time-phasing units so those elements required to conduct JRSOI deploy initially;
(3)  Synchronizing theater reception, staging, and onward movement capabilities to prevent bottlenecks;
(4)  Exercising the ability to control and adjust the TPFDD flow and movement schedules;
(5)  Coordinating with the commands' OPSEC personnel to develop appropriate countermeasures to protect the information related to the movement of forces;
(6)  Coordinating with the commands' current intelligence personnel to ensure timely situational awareness of enemy locations, movement, capabilities and intent; and
(7)  Maintaining flexibility and adaptability of forces by monitoring and maintaining awareness of the changing threat and OE.

For additional protection information, see JP 3-10, Joint Security Operations in Theater; JP 3-13.3, Operations Security; *and JP 3-07.2,* Antiterrorism.

d.  Elements of JRSOI can consist of one or more combinations of the following:  US
forces, HN forces, CAAF, or multinational forces.  These enablers are force multipliers because they provide the means to expedite buildup of forces in the AOR.  Normally, US forces are deployed to support JRSOI operations if the required capability does not exist in the AOR.  The necessity to deploy US forces may be reduced if reliable support can be obtained through one of the other sources.  To execute JRSOI operations, planners should be aware of the considerations associated with JRSOI support requirements shown in Figure VI-2, and integrate required forces and capabilities early into the deployment process.  As units arrive in the OA, they are in a deploying status with little or no operational capability and will most likely require support.  Their requirements should be met until the units assemble and become operational and have been integrated into the gaining command.  The list in Figure VI-2 is self-descriptive; however, other services encompass life support requirements, such as meals, water, shelter, sanitation, and trash removal, and support elements for operating marshalling areas and SAs, and reporting movements to the DOD ITV system.  Regarding ITV, the most critical is theater distribution (tactical movement and distribution).  It is the theater segment of asset visibility where resources, solutions, and efficiencies can produce the most improvement.  Support during JRSOI is provided by organizations such as USA
sustainment brigades, USAF aerial port squadrons and contingency response elements, MAGTF logistics combat element, USN advanced base functional components, DLA support teams, and/or contracted services or HNS.  Another important consideration is that organizations with JRSOI support functions may perform other functions simultaneously (e.g., sustainment, retrograde).

e.  **HNs can provide valuable resources to support JRSOI operations.**  HNS may include civil and/or military assistance at reception facilities, air and naval operating bases, staging facilities, and support areas.  Support may encompass a wide variety of commodities and services concerning supplies, medical, transportation, facilities, communications, petroleum, power and power generation, and civil labor.  HNS can reduce the need for early arriving forces and materiel to support JRSOI, shrink strategic lift requirements, and minimize the in-theater logistic footprint.  In addition to established HNS agreements normally limited to use in war, declared crisis, or emergency, support can also be arranged through existing ACSAs or, at the local level, by directly contracting for support and services.  Additionally, bilateral defense agreements are established where a permanent relationship and presence is established.
HN capabilities should be assessed and validated as early on in the deployment planning process as possible.  In contingency operations, an enormous saving in manpower, units, and equipment is possible by maximizing HNS.  This is particularly true in the areas of transportation, specialized equipment, and prepositioned stocks.  Standing technical agreements covering status-of-forces, land use, and basing access are crucial for reception and staging.

## Joint Reception, Staging, Onward Movement, And Integration Support Considerations

|               |                          |
|----------------|---------------------------|
| Supply         | Civil Engineering Support |
|               |                          |
| Maintenance    | Health Services           |
|               |                          |
| Transportation | Personnel Services        |
|               |                          |
| Security       | Other Services            |

f.  **Multinational support has been a traditional strong point for successful JRSOI.**
Historically, the US has relied upon its allies to assist during major worldwide contingencies and smaller regional emergencies.  Complementary and unique multinational capabilities should be considered during planning.

g.  Contracted support is another force multiplier and, like HNS, should be planned and coordinated in advance of an actual deployment.  Normally, HNS will be considered first before a decision is made to contract for required support.  The supported CCDR should ensure the early deployment of contracting, financial management, and legal personnel to enable necessary contracting actions.  In the context of JRSOI, contract support is the use of foreign or US civilian personnel and/or equipment to perform a function, such as off-loading vessels or transporting supplies forward.  Using contractor personnel reduces the need for US military personnel.

For further information on contracted support, see JP 4-10, Operational Contract Support;
JP 4-0, Joint Logistics; *and JP 4-08,* Logistics in Support of Multinational Operations.

## 4.  Reception

a.  This section describes reception operations at theater PODs and other reception nodes.  Reception is the process of receiving, off-loading, marshalling, and transporting of personnel, equipment, and materiel from strategic and/or intratheater deployment phase to a sea, air, or surface transportation point of debarkation to the marshalling area.
b.  Reception must be considered in the planning and CONOPS development.
Reception begins with the arrival of deploying forces and equipment into an OA.  During major strategic deployment, the preponderance of personnel arrive in-theater via intertheater airlift and most equipment and materiel arrives by strategic sealift.  Exceptions to this rule include time-sensitive equipment such as C2 assets and other items identified as critical combat capabilities.

## C.  Pod Operations

(1)  During deployments, or when a force is redeploying to a new OA, POD
operations will vary depending on whether the reception is occurring at an established APOD/SPOD within an OA.  Effective interface at the POD during reception is crucial to the overall success of the JRSOI process.  Forces are received; equipment, cargo, and vehicles are arranged at the POD and managed/marshalled in preparation for movement to the SA.  Ultimately, POD and reception activities are focused on rapidly moving the force from the port to the SA and eventually integrating them into the JFC's mission.  During redeployment to home station or demobilization station, POD operations will in most cases occur at a major port (APOD/SPOD) in either CONUS or OCONUS.  In either case, activities are focused on receiving personnel and equipment and returning them to their home stations or other facilities.
(2)  Overall reception capacity should include, at a minimum, personnel accounting capabilities, strategic lift and delivery capabilities, and the overall throughput capabilities of the port.  This enables the port to be cleared in an efficient manner.  The

## Desert Shield Reception

Although personnel were usually flown to the Gulf, most equipment and supplies were sent by sea.  Close coordination among the entire transportation network was necessary to ensure that airlifted personnel reached the theater near the date their equipment was scheduled to arrive. Arrival of personnel before their equipment would increase the burden on the Saudi infrastructure.  It also would expose troop concentrations in the port areas to possible enemy attack by ballistic missiles, aircraft, and terrorists.

## Source:  *Conduct Of The Persian Gulf War* Department Of Defense Final Report To Congress, April 1992

transition to theater responsibility can be facilitated by USTRANSCOM TCCs in conjunction with the Services and/or joint forces operating the air and sea PODs.  Although the primary focus of reception is to receive, off-load, marshal, and transport deploying forces, the reception process inevitably shifts from receiving sustainment materiel, replacement equipment, and personnel to ultimately supporting redeployment operations of in-theater forces.  At PODs, these activities may occur simultaneously with two-way traffic into and out of the theater.  In all cases, detailed planning, force tracking, and the principles of movement control as described in Chapter V, "Movement," are essential to the overall success of reception.

d.  **Command Relationships.**  During deployment or redeployment to a new OA, the supported CCDR is responsible for JRSOI planning and execution.  During redeployment to home station or demobilization station, the supported commander retains overall responsibility for the planning and execution of the redeployment operation.  However, supporting Services or Service components, in coordination with the supported commander, plan and execute the JRSOI phase.  The designated command, Service, or agency assumes responsibility for units and personnel when OPCON is relinquished IAW
an appropriate order.  Upon arrival at POD or other designated time and place, the unit changes OPCON to the designated commander.  The supported CCDR relinquishes the OPCON or TACON over to the deployed unit and the unit is transferred back to the designated command or Service.  The receiving command establishes the command relationships and plans and executes JRSOI.  The latter task is normally assigned to a Service component or to a Service itself.
e.  **Seaport and Aerial Port.**  Capacities and throughput capabilities significantly influence the speed with which forces can be deployed, the order in which forces must be deployed, and, to a large extent, the types of units that can be deployed.  Port efficiency or throughput is a function of the OE and the level of port modernization (developed versus undeveloped).  Some instances may necessitate improving or constructing port facilities to meet operational requirements.  In addition to the PODs and nodes, several other facilities and areas support the reception process.

f.  **Marshalling.**  Marshalling is an essential component of the reception process that facilitates port clearance.  The timely movement of personnel, equipment, and materiel to a common assembly or holding area, preferably outside the port, gives the commander the first opportunity to reassemble mission capability.  This very important task of assembling forces is often complicated by the fact that units may arrive in-theater at separate PODs and at different times.  To further enhance port clearance, the CCDR should designate marshalling areas that support unit reassembly without impeding the arrival ports for follow-on units.
g.  DOD uses the SPM approach for most APOD and SPOD operations.  As outlined in the UCP, USTRANSCOM provides worldwide common-user aerial and seaport terminal management and may provide terminal services by contract.  Thus, USTRANSCOM, through AMC and SDDC, will normally manage common-use aerial ports and seaports, respectively, for the CCDR.  In areas not served by a permanent USTRANSCOM presence, USTRANSCOM will deploy an AMC or SDDC mission support element including aerial port or seaport expertise.  If mobile C2 is also required, a mission support team or CRG will deploy, as well as the SDDC port management portion of JTF-PO to manage the ports in concert with the designated port operator. Based on availability of fixed-port terminals or OEs or requirement, the port manager may also serve as the port operator.

For more information on redeployment POD operations, see CJCSM 3122.02, Joint Operation Planning and Execution System (JOPES), Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution).

h.  **APOD Operations.**  The APOD serves as the primary port of entry for deploying personnel, as well as for early entry forces and capabilities airlifted into theater.  APODs may be operated in conjunction with the HN.
(1)  **APOD Functions.**  Numerous operational and support functions occur at the APOD.  Primary operational functions are to receive, off-load, marshal, provide essential field services, and transport deploying forces and capabilities.  Tasks include off-loading cargo (both equipment and materiel), arriving personnel in theater via personnel accounting systems, clearing personnel through air terminals, accomplishing movement control, and maintaining ITV.  In addition to operational functions, there are APOD support functions as listed in Figure VI-3.
(2)  **APOD Service Capabilities.**  Various organizations provide the operational capabilities needed for APOD reception.  For example, AMC, through its air mobility squadrons, aerial port squadrons/flight, and CRGs, provides much of the operational and logistic support needed to receive arriving aircraft.  USN overseas air cargo terminal units unload aircraft and operate air cargo and passenger airheads. Through its cargo transfer capability, the Army provides the required support to interface with the CRG and begins the staging and onward movement phases for the deploying personnel, equipment, and materiel.  When performing this mission, the Army element is often referred to as the A/DACG.  Marine Corps units may also be given the A/DACG mission.  In addition, HNS, provided under the provisions of an existing agreement or contracted port services, may be used to free up finite reception assets and minimize the logistic footprint at the APOD.  Close coordination with HNS activities is necessary to balance the operational requirements of all organizations competing for limited resources.

(3)  **APOD Infrastructure Optimization.**  Several factors can impede APOD
reception.  However, the overriding considerations for any airfield operation are parking maximum (aircraft) on ground (MOG) and working MOG.  Parking MOG is the number of aircraft that can fit, or be parked, on the ground at one time.  Working MOG pertains to how many parked aircraft can be worked on at the same time based on available personnel, materials handling equipment (MHE), and ramp space.  An airfield's MOG may not remain constant if it lacks a dedicated explosives pad.  In these cases, the parking or working MOG will decrease as otherwise available adjacent aircraft parking spaces are removed while explosive cargo is off-loaded from another aircraft.  Local commanders determine working MOG based on the most restrictive of multiple planning factors (e.g., manpower, servicing equipment) and notify appropriate C2 and planning organizations for dissemination.  Service and HN operators must ensure their activities do not reduce MOG capacities.
(4)  **APOD Joint Use.**  Another consideration is ownership and management of the APOD facility.  The APOD may be controlled and/or operated by various HN military and civilian organizations.  Additionally, other military and commercial activities may compete for limited facilities.  These competing requirements may complicate unity of command and may limit or reduce facility throughput capacities available for reception of forces.  To overcome this obstacle, clear C2 relationships must be established by the JFC for all APODs and JRSOI functions.

i.  **SPOD.**  Historically, 90 percent of a deploying force's equipment and materiel are delivered to the theater via strategic sealift.  Three types of seaports can function as a SPOD:  **fixed**, which are improved, world-class ports (i.e., Dammam, Saudi Arabia, and Pusan, Korea); **unimproved or degraded** ports (i.e., Somalia and Haiti); and bare beaches where fixed facilities are unavailable.

(1)  **SPOD Functions and Responsibilities.**  Responsibility for essential SPOD
functions is shared between HN seaport organizations and DOD organizations such as

## Aerial Port Of Debarkation Support Functions Support Functions At Aerial Port Of Debarkation

|                             |                             |
|------------------------------|------------------------------|
| Personnel                    | Hazardous cargo handling     |
|                             |                             |
| Airfield management          | Medical                      |
|                             |                             |
| Materials handling equipment | Transient aircraft servicing |
|                             |                             |
| Maintenance                  | Air defense                  |
|                             |                             |
| Transportation resources     | Command and control          |
|                             |                             |
| Security                     | Equipment refueling          |


MSC and SDDC, military terminal service units, and contractors.  Examples of SPOD functions are shown in Figure VI-4.
(2)  SPOD operations are normally conducted at established, fixed maritime terminal facilities, such as a sea or inland maritime port.  Pre-positioned port opening packages are an option available to the CCDR through the different Services' prepositioned equipment located either in-theater or afloat.  Pre-positioned port opening packages may be capable of operating a maritime terminal and providing the necessary capability to receive forces.
(3)  SPOD maritime terminals include both seaports and inland water facilities capable of receiving deep draft vessels, coastal vessels, and barges.  Many established terminals have a transportation infrastructure in place such as railways, highways, inland waterways, and adjacent airfields.  Although terminal facilities vary, many are already equipped to handle roll-on/roll-off vessels, containers, general and bulk cargo, and lighterage.

(4)  JLOTS is an option available to receive the force when debarkation at an established port is impractical or not available.  In addition, JLOTS may also provide increased capability to operational fixed ports.  In JLOTS, USN and USA logistics overthe-shore forces conduct operations together under a JFC.  JLOTS operations are conducted over unimproved shorelines, through fixed ports not accessible to deep draft vessels, and

## Seaport Of Debarkation Functions


Seaport management

Cargo offloading, documentation, and clearance

Berthing and chandler services

Ship arrival and departure coordination

Coordination for transportation for onward movement

Movement control from seaport of debarkation to marshalling area

Hazardous cargo handling

Port support activity

Transient ship services

Field services

Medical support

Contract and demurrage

Holding area operations

Maintenance and logistic support for arriving forces

Port security and force protection
through fixed ports that are inadequate without the use of JLOTS capabilities.  JLOTS operations should be considered when port throughput capacity or reception capability is inadequate to support planned joint force operations or to augment port reception capability to handle the surge of major combat forces during the early stages of deployment operations.  The magnitude of JLOTS operations extends from the reception of ships for off-load through the onward movement of equipment and materiel to inland marshalling areas and SAs.

For further information on JLOTS, see JP 4-01.6, Joint Logistics Over-the-Shore.

(5)  The SPOD will contain facilities and organizations, both military and civilian, to perform many of the APOD functions described earlier.  One of the key organizations for SPOD operations is the PSA and/or port operations group (POG).  It is a temporary organization that aids the port commander in receiving, processing, and clearing cargo.  The PSA is under the OPCON of the SPM at common-user seaports.  For seaports not designated as common-user seaports, the GCC designates the port manager, whereas the POG remains under the OPCON of the logistic combat element and/or landing force support party.  PSA and POG functions are shown in Figure VI-5.

j.  Transportation systems are crucial to the timely and efficient reception of deploying forces at the SPOD.  The supported commander should consider all available resources, geography, transportation capabilities, climate and seasonal changes, and distance between LOC nodes, as well as projected requirements for movement of the forces from the SPOD.  When selecting a SPOD, the supported commander should consider the transportation infrastructure, as well as the capacity of the port to handle potential throughput and surges of deploying forces.  A robust multi-modal system of inland transport options (i.e., rail, road, air, inland waterway) is vital in efficiently receiving and moving the force to SAs.
k.  **Reception Considerations.**  To support operations at the APOD and SPOD, conditions that support the JRSOI process should be considered.  The CCDR should determine the type of support units and the composition and/or method of sustainment

## Port Support Activity And Port Operations Group Functions


Receive and stage unit equipment in marshaling areas.

Correct configured equipment and cargo deficiencies.

Serve as vehicle operators.

Assist in the servicing of self-deploying aircraft.

Provide necessary maintenance and recovery capability.

Assist the port commander with cargo accountability.

Provide for security of sensitive and classified cargo.
support necessary to carry out reception.  The CCDR may consider the most capable Service or predominant user options when configuring the support structure.
(1)  **Economy of Resources.**  CCDRs should tailor their reception operations to provide efficiency and economy, as well as eliminate duplication of limited resources among the Services.  The decision by the JFC to establish a joint reception center maximizes use of scarce resources.  Efficient resource management of limited transportation assets and reception facilities assists in optimizing reception throughput.
Discharge workload should not exceed POD throughput capacity.  A time-phased buildup of reception capabilities may accomplish this.  At the same time, however, the JFC
must configure reception forces to handle potential surge capacities of strategic deployment and provide intermodal services for transshipment of arriving cargo and supplies.

(2)  C2.  C2 functions are essential to the successful reception of forces into an OA and are the responsibility of the supported CCDR.  Prior to commencement of deployment and reception operations, the JFC should develop an in-theater structure for executing C2 of JRSOI operations.  This structure must address the integration of USTRANSCOM assets into the overall C2 for JRSOI to be an efficient operation.  Some C2 assets may be pre-positioned in theater, geographically in close proximity to the region, or afloat on MSC or maritime pre-positioning force vessels.  Successful execution of a reception operation involves a centralized C2 structure (unity of command), decentralized execution, and disciplined (synchronized and balanced) movement control.
Monitoring and control of deployment operations will be ongoing throughout all segments of JRSOI and will involve joint and theater movement control organizations using joint ITV systems.  The following C2 functions (mission and situation dependent) are examples of what may be required to successfully execute reception functions at APODs and SPODs:

(a)  Maintain unity of effort for all primary and secondary LOC nodes.
(b)  Coordinate, control, and monitor US airlift and sealift operations into
APODs and SPODs.
(c)  Designate marshalling area.
(d)  Provide personnel and cargo clearance of arriving forces.
(e)  Provide for personnel, equipment, and materiel accountability.
(f)  Determine security risk. (g)  Provide movement control of arriving personnel, equipment, and
materiel.
(h)  Provide visibility over arriving and departing personnel and cargo by input of AV source data into appropriate AIS.

(i)  Liaise with HN military and civilian officials to obtain required clearances and support.

(j)  Coordinate and control loading and off-loading from aircraft and ships.
(k)  Coordinate and control personnel and cargo movements from PODs via surface and air to planned holding areas.

(l)  Monitor and manage the TPFDD. (m)  Coordinate and control movement of noncombatants.
(n)  Provide clearance for intratheater airlift cargo movements.
(o)  Provide distribution management for the theater and arriving unit command structures of all arriving personnel, equipment, and materiel.

(p)  Provide intermodal services for transshipment of arriving cargo and supplies.

(q)  Provide, coordinate, and control construction in support of personnel and cargo movement.

(r)  Provide life support facilities.
(3)  **Communications.**  Effective communications and collaboration, vertically and horizontally, is essential for JRSOI due to the complexity of the operation.  Timely and reliable communications should be continuous among all JRSOI participants, both supporting and supported.  The following communications functions may be required to successfully execute JRSOI operations:

(a)  Establish links between LOC nodes.
(b)  Use automation technology.  Communications should utilize advanced technologies that will be both an enabler and force multiplier of the reception process. The AISs and the COP described in Appendix A, "Information Technology Enabling Tools," are crucial to ensure the commander has access to interactive decision quality information (e.g., integrated, real-time, AV) on personnel, installations, finances, and equipment/materiel.  Through Global Combat Support System (GCSS)/IGC programs, commanders can obtain AV, as well as manage the flow of forces in-theater and through the numerous PODs.  Establishing a reliable network to disseminate this valuable information to all Services involved in the reception phase must be a priority for those units with GCSS and IGC capabilities.

(c)  Provide LNOs.  Effective liaison among the Service components and with HN agencies is paramount for effective communication to occur during the entire reception operation.

(d)  Monitor IGC and JOPES to provide real-time force tracking information of deploying forces and non-unit replacement personnel.  Monitor AV using IGC to provide near real time tracking of non-unit sustainment items for all organizations and activities.

(e)  Provide for reliable and compatible two-way communications between joint forces.

(4)  **Protection.**  Deploying forces, as well as intertheater airlift and sealift assets, may be the most vulnerable during loading or discharge.  The threat must be considered in light of the concentration of forces within the limited confines of a POD. As units move forward to secondary LOC nodes, they remain vulnerable until fully integrated into a mission-capable force.  Protection capabilities and/or measures should be integrated into the reception plan.  The CCDR is responsible for providing the assets needed to protect the force throughout the entire reception process.  Protection functions should:

(a)  Provide air defense. (b)  Maintain coastal, harbor, and inland waterway defense.
(c)  Provide APOD and SPOD facility defense. (d)  Provide military police support. (e)  Establish joint security coordination center for security oversight. (f)  Prepare for the effects of NEO on JRSOI operations.
(g)  Provide protection against CBRN threats. (h)  Protect LOCs. (i)  Provide a personnel recovery capability.
For further information on security operations, see JP 3-10, Joint Security Operations in Theater.

(5)  **Transportation.**  All three elements of a transportation system (mode operations, terminal operations, and movement control) should be integrated early into the TPFDD flow to provide adequate reception capabilities for the deploying forces.
These elements may be RC assets that must be mobilized and flow early in the TPFDD. Essential to any JRSOI mission is an executable plan that facilitates intratheater transportation between nodes.  The primary transportation nodes and the extended LOCs should be mutually supportive of the principle of unit integrity.  To transition from strategic intertheater deployment to in-theater reception, the following transportation functions may be required:
(a)  Place port-opening force packages at PODs providing hand-off of deploying personnel, equipment, and materiel.

(b)  Employ movement control principles.  Movement control coordinates all aspects of transportation: modes, nodes, and terminals.  It includes Service-organic capabilities, HNS, and supporting commands.

(c)  Have a support element for off-loading of arriving forces.
(d)  Provide intratheater air and surface transportation assets.
(e)  Manage and monitor the TPFDD.
(f)  Establish theater LOC nodes and links required to meet the anticipated transportation and throughput capacities.  Allow for sufficient coordination to ensure timely movement of cargo and equipment through the port to minimize port congestion.

(g)  Identify, assess, and provide for required physical transportation capacities and capabilities (ports, airfields, rail and road networks, littoral and inland waterways, and communications infrastructure).

(6)  **Supply and Services.**  Supply and services compete for limited strategic lift resources as the priority is on receiving and moving the force forward into the theater.
However, sustainment of the force while transitioning into the theater cannot be forgotten and neither can the resources that will be required to sustain reception.  The CCDR should provide arriving personnel, equipment, and materiel with required life support and field services until unit personnel are reunited with their supplies and equipment and become self-sufficient. These services may be RC assets that must be mobilized and flow early in the TPFDD.  The following are typical categories of support that may be provided to sustain newly arriving forces in-theater:

(a)  Field and life support services such as food, water, lodging, and sanitation.
(b)  Maintenance and operator support for deploying equipment, vehicles,
rotary-wing aircraft, fixed-wing aircraft, and tiltrotor aircraft.
(c)  Munitions storage and handling. (d)  Petroleum products storing and handling. (e)  Power and power generation. (f)  Medical support and evacuation. (g)  Mortuary affairs services. (h)  Frustrated cargo storing, handling, and processing.
(i)  Postal support.
(7)  HNS as a potential force multiplier should be planned and coordinated well in advance of an actual deployment.  This can best be accomplished through coordination with the US country team (ambassador and staff), if one exists within country.  The effect of a well-planned HNS agreement should be a reduction of the US military logistic footprint in-theater and a concurrent reduction in the need for early deployment of supporting units.  Some HNS considerations are to:
(a)  Augment reception capabilities early in the deployment cycle with dedicated units if civilian or military HNS are not available at APODs and/or SPODs to quickly throughput combat forces.

(b)  Analyze the PODs' and in-theater transportation infrastructure's
capacity.
(c)  Anticipate limited materiel, key services, and HNS in-country.
(8)  **Contractor support** for materiel requirements is another force multiplier and, like HNS, should be planned and coordinated in advance of an actual deployment. Normally, HNS will be considered first before a decision is made to contract for required support.  When contact support is anticipated, the following considerations apply:
(a)  The supported CCDR should ensure early deployment of contracting, financial management, and legal personnel to accomplish the contracting actions. Contracts will not be without cost, nor should deploying forces expect to have unlimited access to local facilities and resources.
(b)  In most cases, military forces will have to share and compete with HN
military, civil, and commercial operations for scarce resources and facilities.

(c)  CAAF and their equipment may be deployed with US forces on DOD-
provided lift, or they may deploy using commercial assets.

(d)  JFCs, Services, and CAAF must coordinate to ensure they are not competing for the same lift or space during JRSOI operations.

## 5.  Staging

a.  **General.**  This section describes the staging process and the activities that may be performed in theater SAs during deployments and redeployments to a new OA, or at SAs designated near CONUS or OCONUS PODs during redeployments to home or demobilization station.  Regardless of where staging occurs, the activities associated with staging will generally include assembling, temporary holding, and organizing of arriving personnel, equipment, and materiel into units and forces, and preparing them for onward movement and employment by the JFC.  Operability checks will need to be performed on equipment and vehicles to ensure their combat readiness, and loads will need to be sequenced and loaded in preparation for onward movement.  During staging, deploying forces have limited mission capability and may not be self-sustainable.  The CCDR
should provide facilities, sustainment, life support, and protection until deploying units regain their combat or mission capability.  Redeployment back to home or demobilization station will largely be a Service responsibility as forces and equipment are processed back into their respective Service and are reset.  Three essential force-related activities that occur during staging are depicted in Figure VI-6.

b.  During deployment or redeployment to a new OA, a major focus of JRSOI
specifically during staging is building capabilities required by the JFC.  Mission success requires actions to:

(1)  Determine combat capability. (2)  Determine logistic capability and sustainability.
(3)  Determine how to track and visualize combat power. (4)  Establish an incremental buildup of combat power. (5)  Prioritize and adjust the flow as needed. (6)  Manage and supervise the unit's progress.
(7)  Develop a complementary tracking system that applies to combat operations as well as JRSOI.

c.  **Deployment force tracking** aids in predicting the unit's arrival time in theater and incremental build of mission capability.  The supported CCDR's staff supports the operational commander in force tracking by providing visibility of deploying forces and materiel.  Force tracking includes the following steps:

(1)  Elements are monitored until they are reassembled. (2)  Unit commander reestablishes control of the unit.
(3)  Unit becomes capable of sustaining itself. (4)  Unit can perform assigned missions.

## Staging Force-Related Activities


Units assemble into a mission-capable force.

Units of the force prepare to conduct their missions.

The force prepares for onward movement (if required) and subsequent
integration into the theater operation.
(5)  Unit completes onward movement and integration.

d.  **SAs.**  SAs are specific locations along the LOCs.  The CCDR usually designates specific locations for staging to provide space and focus resources to support staging operations.  SAs provide the necessary facilities, sustainment, and other support to enable units to become mission-capable.  The size of the deployment or redeployment and location of the PODs and marshalling areas may necessitate multiple SAs.
(1)  In selecting the location of the SAs, the CCDR plans where forces will be strategically concentrated to enter the OA.  The CCDR evaluates the location of TAAs or OAs, geographic constraints, availability of organic and HN assets, transportation infrastructure, distance to the ports, and protection considerations.  These factors, along with the physical dimensions of the theater, ultimately determine the location of the theater SAs.

(2)  The size of the SA is influenced by numerous variables, including the anticipated flow of forces in theater, space available, and threat.  The TPFDD is an important tool for the CCDR to use in understanding the requirements for SAs.
(3)  **ISB.**  During deployment, the theater operational situation may necessitate the establishment of an ISB outside of the combat zone or JOA prior to inserting the forces. If established, the ISB is an initial theater staging facility.  Deploying forces debark from strategic lift, reassemble, and prepare to accomplish assigned missions.  The theater may not have the physical infrastructure to support JRSOI and will require the use of air and sea bases outside the region.  ISBs serve as a principal staging base to secure a lodgment to project the force for the rapid delivery of combat power to an AOR and can perform selected operational-level tasks.  In some instances, an ISB is also used to transition from intertheater lift to intratheater lift to increase the number of points of entry available to the force to mitigate antiaccess measures.
(4)  During redeployment to home or demobilization station, staging activities will be different.  Since forces and equipment are being staged in preparation to being assimilated back into their respective Services, these activities will focus on assembling and processing personnel, receiving WRM and other equipment and coordinating their onward movement, performing any necessary operation checks, and reporting status to facilitate ITV.

## 6.  Onward Movement

a.  **General.**  This section describes systems and processes for accomplishing the onward movement of deploying or redeploying forces.  Onward movement is the process of moving forces and sustainment from reception facilities and marshalling or SAs to TAAs or other operating areas.  Rail, road, inland or coastal waterway, and/or air can be used to accomplish this movement as may intra-theater lift.  Challenges associated with onward movement during a deployment or redeployment to a new OA may include establishing distribution networks, limited LOC capacity, degraded LOC conditions, the potential for enemy interdiction, and reporting and movement control procedures.  Onward movement

## Operation Joint Endeavor

"At the time of execution, the rail deployment plan was based on an invalidated deployment rate (20 trains per day).  At the planned rate of movement, the division could deploy the bridge opening package, open the ground lines of communications, accomplish the transfer of authority, and begin enforcement of the ZOS [zone of separation] by D+30.  As the deployment began, it rapidly became apparent that the rail LOC [line of communications] would only throughput about half of the planned deployment rate.  As a result, ad hoc force tailoring decisions had to be made to compensate for the reduced rail lift capacity."

## Source:  Initial Impressions Report Operation Joint Endeavor, 1995

during redeployment to home station or demobilization station will be planned and executed by the owning Service and focus on moving returning units from the POD. Transportation from the POD may be arranged for by a Service or USTRANSCOM depending on mode selected to move the returning forces.
b.  The deployment and redeployment processes share most of the activities associated with onward movement particularly during a redeployment into another GCC's AOR.  However, in the case of redeployment to home or demobilization station, efforts are largely focused on conducting movement control operations as units and equipment make their way to their destinations.  These destinations could be the home station or, in the case of equipment, a depot maintenance facility for refurbishment or remanufacture.  Some challenges to onward movement are establishing the distribution network, enemy interdiction, reporting procedures, and movement control.

c.  Efficient onward movement of personnel, equipment, and materiel requires a balanced, integrated system of node operations, movement control, mode operations, and cargo transfer operations.  The onward movement process encompasses support to all Service components of a joint operation, and often includes HNS.  As in all JRSOI activities, onward movement of personnel, equipment, and materiel is prioritized according to the CCDR's needs.  Onward movement is complete when force elements are delivered to the designated location at the designated time.

d.  **Enablers of Onward Movement.**  Key elements of the onward movement process are speed of movement and information flow.  Speed of movement is vital for protection and mission accomplishment.  Information flow encompasses locations and capabilities of forces, projected and actual arrival times at en route and final destinations, and component commands' ability to affect the movement.  Successful onward movement of deploying/redeploying forces can be viewed in the context of eight onward movement enablers as explained below.
(1)  **Movement Control.**  Establishing and maintaining effective movement control is essential during the onward movement segment.  JP 4-0, *Joint Logistics,*
describes a variety of options available to the CCDR to execute and control joint logistics to include coordinating and synchronizing movement control.  To ensure a fully integrated and responsive transportation system, the CCDR should consider assigning responsibility for theater transportation movement control to the JDDOC.  The JDDOC must be equipped with sufficient communication and automation capability to ensure adequate interface between strategic and theater transportation systems and the CCDR's staff.  Service components also have capabilities to coordinate and synchronize movement control.  The Army has various movement control organizations while the Marine Corps has movement control centers (MCCs) planned for all deploying units from the Service component level down to the battalion and squadron level.  They are the MDDOC, the MAGTF MCC, and the unit MCCs.
(a)  If a joint movement control organization is established using assets from multiple Services, then the CCDR conducts joint training to ensure personnel understand and can operate movement control equipment and C2 processes.  The CCDR should task-organize the movement control functions commensurate with the mission, size, and geography of the OA.

(b)  The ITV systems provide a capability vital to coordinated onward movement.  They provide a means to track units, personnel, equipment, and materiel en route from reception areas to SAs and forward to the assembly areas.  The physical capabilities and limitations of the distribution network, along with the effects of combat, can limit the ability to execute onward movement as planned.  Thus, connectivity is essential to provide ITV information to enable successful execution of onward movement to include location, characteristics, and capacities of roads, aerial ports, and rail lines, combined with current status of highway regulation, traffic circulation and surface distribution plans, and movement programs.
(2)  **Communications/Automation.**  Movement control elements should be equipped with sufficient communication and automated systems to ensure adequate interface between strategic and theater transportation systems and the CCMD's staff. They should be skilled in coordinating and directing theater transportation operations in support of unit movements and/or logistic resupply operations.
(3)  **Transportation.**  Nodes, main supply routes (MSRs), and HN assistance should be coordinated to maximize the speed of movement.  Close coordination is essential for minimizing congestion because in most cases the Services, multinational units, and HN populace will be using the same networks.  It is essential capacities and capabilities of the transportation network are balanced against the movement requirements so nodes and routes are neither saturated nor underutilized.  As previously explained, the designated movement control element is responsible for coordinating the use of all theater transportation resources with USTRANSCOM and its TCCs, other CCMDs, and the HN.
(4)  **Supply and Services.**  During deployment or redeployment to a new OA, en route support nodes along the theater LOCs provide security, life support, refueling, limited vehicle maintenance, and vehicle recovery.  The size of the support centers will be based upon the available facilities, length of route, and volume of equipment and personnel transiting the sites.  Various types of en route facilities that support onward movement include:

(a)  Aircraft en route support sites. (b)  Convoy support sites. (c)  Trailer transfer points. (d)  POL transfer points. (e)  Pre-positioned equipment sites.
(f)  Pre-stock supply points. (g)  Railheads.
(h)  Of the above listed facilities, convoy support sites are among the most critical and provide the bulk of en route support during onward movement.  Services provided by convoy support sites may be tailored based upon such factors as distance between LOC nodes; number and location of support bases; and MSRs' congestion, condition, and protection.  Convoy support sites usually provide support in the following areas:

1.  Administration and communications. 2.  Refueling. 3.  Dining and billeting. 4.  Latrines. 5.  Laundry and showers. 6.  Vehicle recovery and maintenance. 7.  Medical. 8.  MHE and cargo-handling equipment. 9.  Security (force protection).
(5)  Force **Protection.**  Protection is critical to onward movement because it minimizes enemy opportunities to inflict serious losses and delays.  The threat of enemy interdiction to onward movement of forces presents a special challenge to the commander.  The CCDR should assume interdiction of the LOCs will form an integral part of enemy strategy and should plan operations to preclude them from impacting onward movement.

(a)  GCCs are faced with many threats as their forces conduct tactical convoy operations.  Threats to operations range from vehicle-borne improvised explosive devices
(IEDs) to complex ambushes employing other types of IEDs, rocket-propelled grenades, CBRN hazards, and small arms fire.
(b)  Tactical convoys are combat operations.  Although contact with enemy organized/uniformed ground forces may not be anticipated, security against anti-US forces, enemy sympathizers, and IEDs must be maintained and the convoy must be prepared to take immediate action against an enemy threat.  To accomplish this, tactical convoys require additional planning and coordination beyond normal line-haul operations.  A main enemy tactic is to target the convoy LOCs, supplies, and other government resources.  To defeat this tactic, each tactical convoy must be prepared to take the necessary actions in the face of ambush and defeat enemy forces once contact is gained, thus retaining the initiative and deterring future attacks.

For further information, see Army Techniques Publication (ATP) 4-01.45/Marine Corps Reference Publication (MCRP) 4-11.3H/Air Force Tactics, Techniques, and Procedures (AFTTP) 3-2.58, Multi-Service Tactics, Techniques, and Procedures for Tactical Convoy Operations.

(c)  **Protecting the LOCs.**  The JFC is responsible for LOC security.  It may be necessary to commit combat capabilities to secure LOCs to ensure the incremental build of combat power is not interrupted.  In addition, alternatives such as rerouting or mode substitution may be required (i.e., air and sea LOCs to replace or supplement ground LOCs) if preventive and preemptive measures fall short.

(6)  **HNS resources and facilities** are important to the successful employment, deployment, and redeployment of forces.  HNs can often provide a variety of services through their national agencies and can support onward movement in a wide range of categories.  Some of these categories are shown in Figure VI-7.

(7)  **ACSAs** provide US pre-negotiated support for contingency operation potential war scenarios.  ACSAs provide the legal authority for the US military and armed forces of other nations to exchange logistic goods and services.  Transactions under this program require reimbursement, replacement in kind, or exchange for equal value, which may not always be the case with HNS agreements.  Legal advice should be sought before executing transactions with other nations for the exchange of goods or services.
(8)  **Operational Contract Support.**  Contractor support for onward movement is another force multiplier which should be planned and coordinated in advance of an actual deployment.  There are several benefits in relying on commercial industry to provide equipment and manpower to move unit equipment.  The redeploying unit does not have to convoy its equipment from the POD to its TAA/forward operating base, nor does it need to provide a PSA.  In addition, the theater requires fewer transportation units as transportation assets are provided by the commercial carrier.  This is a valuable service in cases where US forces are unavailable or may not be allowed entry into a country where US cargo must transit.  An example of this is the Afghanistan ground LOC operations.

## Host-Nation Support To Onward Movement


Combat service support (food, water, lighting, billeting, showers,
and latrines)

Security

Communications

Materials and cargo handling

Ground transportation (buses, line haul, and heavy lift)

Convoy, road, rail, and diplomatic clearances


## 7.  Integration

a.  **General.**  This section describes the integration process and key integration activities to successfully unite deploying forces into the theater command structure or return them to their home or demobilization station.  Effective integration is the key element and ultimate objective of JRSOI.  It is normally accomplished concurrently with other deployment and JRSOI tasks and occurs as soon as practicable along the JRSOI continuum.
b.  During deployment or redeployment to a new OA, integration is the synchronized transfer of mission-ready forces and capabilities into the CCDR's force and, based on the complexity of the operation, may take hours or days to complete.  The complexity and time required for integration depends on the size, contingency conditions, coordination and planning, C2 communications, and security available to manage the deploying or redeploying force.  Integration is complete when the receiving commander establishes C2 over the arriving unit and the unit is capable of performing its assigned mission.  Force tracking culminates in force closure as reported by the commander of the unit.  In deployment operations, force closure occurs when the supported commander determines the deploying force has completed movement to the specified OA/destination with sufficient resources and is ready to conduct its assigned mission.  In redeployment operations, force closure occurs when the designated commander or Service determines that the redeploying force has returned to home station or other follow-on destination.  The designated commander or Service will report force closure during redeployment to home/demobilization station or other follow-on destination based on Service guidelines.

(1)  During execution, the deploying force commander reports that the levels of readiness prescribed by the supported CCDR have been achieved and that integration into the higher HQ is imminent.  The supported CCDR is concerned with the following:

(a)  Location of the forces. (b)  Capability of the forces.
(c)  Projected and actual arrival time at destination. (d)  Commander's capability to affect the movement.
(e)  Additional transportation needed (modes, quantities).
(2)  During deployment or redeployment to a new OA, integration has two major prerequisites:  the unit must be mission-capable and must be integrated into the C2 processes of its higher HQ.  Deploying forces must be organized back into operational units, integrate their C2 systems and combat support systems with the supported command, conduct any final requisite training or mission rehearsals, confirm their mission readiness, and finally report force closure.

(3)  Tracking the components of building mission capability as a precursor to integration is essential for overall mission success.  To track mission capabilities, the components of mission capabilities must be known.
c.  Monitoring mission capability, early and continuous coordination, and planning can help reduce integration time.  Units can establish predeployment liaisons to exchange information, standard operating procedures (SOPs), and communication networks, as well as plan for and prioritize an in-theater incremental buildup of combat power.  Once established, the liaison is maintained to update information (intelligence, situation, mission, deployment timeline) to expedite the in-theater integration.

d.  **Integration Functions.**  Unlike the functions described in reception, staging, and onward movement, the emphasis during integration is on C2 and communications as personnel, equipment, and materiel enter the theater and prepare for integration.  Critical to this is the COP as described in Appendix A, "Information Technology Enabling Tools." Force tracking of mission capability components helps predict when integration can begin and how long it will take to complete.  Protection is still critical but may be easier as security forces reestablish their military capability during staging and onward movement. However, to accomplish integration of the force, the logistic support should be transferred from JRSOI supporting organizations to the gaining command.

(1)  Upon notification of deployment or redeployment, a liaison between the deploying/redeploying unit and receiving HQ should be established to enhance integration.
This liaison is conducted through formal liaison teams attached to the arriving and receiving HQ (the preferred method) or remotely through communication channels.  The size and makeup of the liaison teams are based on the mission and operational conditions.

(2)  Effective liaison enhances the commander's confidence in planning, coordinating, and executing integration.  Subordinate commanders may use an LNO to obtain necessary information such as common coordination measures; tactics, techniques, and procedures; SOPs; rules of engagement; terms; symbology; and exercises.



## Intentionally Blank Appendix A Information Technology Enabling Tools 1.  General

Commanders and staffs at the JTF level and above must have the capability to successfully conduct deployment and redeployment operations.  APEX provides planners with communications and automated data processing systems which possess the capability to generate, store, collaborate, share, and manage large quantities of data.

## 2.  Adaptive Planning And Execution Systems

The following paragraphs describe the primary joint and Service IT systems and their functionality:
a.  **Analysis of Mobility Platform (AMP).**  AMP analyzes throughput capabilities for air and sea ports in supported command plans and global en route infrastructure to determine capability requirements supporting global force projection.

(1)  Airport Simulation **Tool.**  The Airport Simulation Tool provides a graphical depiction of the process and capabilities for cargo and passenger handling to include flight line activities; aircraft parking; cargo yard; MHE; fuel reception, storage and delivery; and reception and onward movement.

(2)  Seaport Simulation **Tool.**  The Seaport Simulation Tool provides a graphical depiction of the process and capabilities for cargo and passenger handling at a single seaport to include dock activities, ship berths and unloading, cargo processing and handling, MHE (including crane usage and types), and onward movement of cargo (railheads and gateways).

b.  The **Army Sustainable Readiness Process** captures force requirements and sources joint and USA conventional force requirements.  It supports four major objectives for the USA:
(1)  Gathers all USA conventional force requirements worldwide in one location and reviews validated requirements over time,
(2)  Assesses the force inventory flowing through the force generation processes,
(3)  Sources force requirements with the available USA inventory to fulfill missions while complying with deployment policies for units, and
(4)  Models units' flowing through the force generation process to synchronize the key events required to optimize readiness for return to deployed status.

c.  **Agile Transportation for the 21st Century.**  This is an umbrella program and not a system per se with a collection of USTRANSCOM tools used to receive requirements, process for potential aggregations, and pass on to transportation component commands for execution.

d.  Automated Global Force Management Tool (AGT)/Collaborative Issue Resolution Tool (CIRT).  The AGT and CIRT applications automate tasks in the GFMIG cycle.  The AGT is a collaborative tool used principally by CCDRs with links to Service databases to automate annual requests for changes to the assignment of forces and apportionment of available forces.  CIRT is used to adjudicate issues and change requests initiated in the AGT.  Service and CCMD users have the ability to request changes, while the JS provides adjudication and confirmation of changes.

e.  The **Base Resource and Capability Estimator** is the planning tool to model military air terminal operations.  It simulates airfield on-loading, off-loading, en route, and recovery base operations, including ground activities such as cargo handling, refueling, maintenance, and aircraft parking.  The model can be used to estimate airfield throughput capability; estimate air, ground, and other resources required to support a given level of throughput at an airfield; and validate MOG values used in existing air transportation models such as the Joint Flow and Analysis System for Transportation.

f.  **Consolidated Air Mobility Planning System** is an airlift scheduling system supporting strategic and theater deployment, sustainment, redeployment, and retrograde movement requirements.

g.  **The Cargo Movement Operations System** is a combat support system that streamlines contingency and sustainment cargo and passenger movement processes.  It supports shipment planning through interfaces with GDSS, GFM, Integrated Booking System (IBS), and commercial carrier systems and load planning through an interface with Integrated Computerized Deployment System (ICODES).

h.  **The Coalition Mobility System** is a coalition scheduling and movement system hosted in a USG-approved commercial cloud enabling multinational forces participating in an operation to share force movement plans and execution information.
i.  **The Computer-Aided Scheduling System** is a Web-based deployment management and transportation system supporting deployment/redeployment of Active Army, Army Reserve, and Army National Guard units to and from their POE.  It is engineered as a strategic/operational repository for unit movement data (level IV), reads/writes unit movement data to JOPES/JPES [Joint Planning Execution Services], and generates and publishes USA's TUCHA [type unit characteristics file] and TEDRP [type unit equipment detail report] for the JPEC.

j.  **The Collection Requirements Analysis Tool for the Enterprise** enables users throughout the intelligence community to quickly research and identify collection requirements from an all-source perspective in a user-friendly environment.  The Intelligence Planner Tool is included in its suite of Web-based tools querying meta-data populated from national defense collection requirement systems.

k.  **DCAPES** provides near real time integrated C2, planning, and execution monitoring information to USAF functional users in operations, logistics, manpower, and personnel providing a single integrated planning environment.  The objective of DCAPES is to provide data and data manipulation capability to USAF planners and commanders to  perform rapid plan development; conduct feasibility and capability analysis; and support the mobilization, deployment, employment, sustainment, redeployment, and demobilization of USAF forces.  Throughout the entire planning and execution process, DCAPES provides users the capability to create and maintain unit processes and provide users the capability to create and maintain UTCs to support the build of a notional TPFDD for resource movement.

l.  **Defense Readiness Reporting SystemStrategic (DRRS-S).**  DRRS-S captures readiness metrics and supporting data from authoritative data sources in near real time.
It highlights deficiencies in training, personnel, equipment, ordnance, and supply.
Variations from standards are identified and assessed in terms of performing missionessential tasks and downgraded resource areas.  Readiness data is provided in the form of capability-based mission assessments and establishes a common language of tasks, conditions, and standards to describe capabilities.

m.  **Enhanced Logistics Intratheater Support Tool (ELIST).**  ELIST is a feasibility planning and modeling system for deployment analysis.  ELIST performs detailed intratheater deployment studies to analyze effects of force modernization, new force structures, and changes to DTS and to check transportation feasibility of contingency operations.  ELIST enables planners to explore and model the impact of theater infrastructure limitations (through combat loss, weather, or limited HN access) and make adjustments to infrastructure and assets at any point in time in the flow. Through ELIST, planners have the ability to accurately determine the infrastructure and consider the throughput capability available for a specific plan.

n.  **Fourth Estate Manpower Tracking System (FMTS).**  FMTS manages manpower and personnel information, to include force structure, positions, and associated manning information.  It functionally allows a CCMD, JTF, or component command to draft, review, and endorse joint manning documents, which are forwarded to the CCDR to review, modify, recommend, and approve each position.

o.  **GATES** provides USTRANSCOM, AMC, and commercial partners an automated management system to process and track cargo and passenger information. GATES provides ITV of arrival and departure data to IGC.

p.  **Global Command and Control System (GCCS).**  GCCS is a deployable C2
system supporting forces for joint and multinational operations across the range of military operations with compatible, interoperable, and integrated communications systems.  GCCS integrates planning, force deployment and employment, fire support, air operations, intelligence and force status.  It receives logistics information from IGC and provides a single integrated application environment on which JOPES resides.

q.  **GCSS-J** is an authoritative information technology application used to provide automation support to the joint logistician.  GCSS-J uses a service-oriented architecture to link the joint logistician to component, Service, multinational, and other agencies, allowing all concerned to use shared data to plan, execute, and control joint logistic operations to deliver visibility over resources, requirements, and capabilities.  It provides the terminal operator visibility of mobilization, deployment, employment, sustainment, redeployment, and demobilization information through the use of a portal and Web-based applications that deliver enhanced visibility and is available on both the SECRET Internet Protocol Router Network (SIPRNET) and Non-classified Internet Protocol Router Network.

r.  **GDSS** is the AMC's worldwide C2 system for mobility airlift and air refueling assets.  It provides aircraft schedules, arrival and/or departure, and aircraft status data to support ITV of all in-progress DOD air mobility missions throughout the world, including all active duty, Air Force Reserve, Air National Guard, and contracted commercial airline aircraft on AMC airlift missions, plus all operational DOD airrefueling missions.

s.  **The Global Force Management Tool Set** integrates authoritative data from Joint Capabilities Requirements Manager (JCRM), JOPES, DRRS-S, Global Status of Resources and Training System, FMTS, and Service systems to support GFM analysis. Users can determine which plan(s) a requirement (i.e., FTN) is associated with, the units sourced to fill that requirement, and the readiness ratings of those units.  The query and reporting tools within the Global Force Management Tool Set provide the user the ability to develop customizable views depicting force capabilities, structure, hierarchy, home and present locations, readiness, availability, employment, deployment, and historical information.

t.  **Global Status of Resources and Training System** is a legacy system currently being used to report readiness and training.  It has been the single automated system within DOD that functions as the authoritative central registry of US Armed Forces units and organizations, as well as certain foreign organizations.  DRRS-S is projected to assume this functionality after satisfying all security, interoperability, and operational testing requirements.

u.  The Global Theater Security Cooperation Management Information System is the overall collaborative tool and authoritative data source for DOD security cooperation planning, execution, and assessment.  It provides users with the ability to view, manage, assess, and report security cooperation activities and events.  Use of this system enhances visibility of the range of security cooperation activities (completed, planned, and on-going) across DOD components, facilitates tracking of resources spent on security cooperation, to include operation and maintenance, and promotes the exchange of best practices.

v.  IBS is the USTRANSCOM, SDDC execution system of the DTS for movement of military unit or sustainment cargo by surface overseas.

w.  **ICODES** is a decision support system for developing ship stow plans.  It assists in developing stow plans by matching vessel characteristics against cargo being offered for shipment.  ICODES develops stow plans for up to four specific ships concurrently and checks for access and hazard violations.  ICODES can automatically attempt to maintain unit integrity in stow plans it develops.  Once stow plans are completed, ICODES automatically generates ship manifests and templates cargo items onto ship drawings.  ICODES can produce customized reports which detail both the process of constructing stow plans and results of the process, and builds a database that provides details on the availability of external ship ramps and the facilities for ports around the world.

x.  IGC is the system of record for ITV and AV.  It integrates automated data processing and information systems, electronic commerce, and electronic data interchange to track the identity, status, and location of DOD unit and non-unit cargo; PAX; patients; forces; and military and commercial air mobility, sealift, and surface assets from origin to destination across the range of military operations.  IGC provides a single place of access for USTRANSCOM and DLA logistics and distribution data, integrating work from DLA's Integrated Data Environment and USTRANSCOM's Global Transportation Network.  The classified IGC home page is located on the SIPRNET at *https://www.igc.ustranscom.smil.mil/igc.*  The unclassified IGC home page is located at http://www.igc.ustranscom.mil/igc.

y.  **JCRM** is used to manage CCDR force requirements through the GFM allocation process (from RFF to GFMAP).  It enables CCMDs to draft, staff, store, and submit force requirements for contingency plans and operations worldwide.  It provides the capability for the JS to validate CCDR requirements, consolidate the entire demand on the force structure, record recommended sourcing solutions and risks, and prepare GFMAP annexes.
(1)  **The JCRM Operational Capability Package Module** generates, stores, and shares force requirements in support of plans, as operational capability packages, based on force structure from authoritative databases.  These packages can be transitioned to operational force requirements in the Requirements Module and can also be used to populate a JOPES database TPFDD with unit-level requirements if the plan were to be executed.

(2)  **JCRM Requirements Module.**  This module captures the operational force demand.  It enables CCDRs to electronically document emergent and annual operational force requirements and forward them to the JS J-3 for validation.

(3)  **The JCRM FP Module** enables the Joint Force Coordinator and JFPs to request and receive sourcing nominations and create sourcing recommendations to generate GFMAP annexes for SecDef approval.  It also enables CCDRs to generate DEPORDS based on the GFMAP annexes.

(4)  **JCRM Force Deployment Module** enables the JOPES TPFDD to be compared to the data in JCRM for the GFMAP annexes, based on the FTN entered in the ULN, to assist operators with verifying and validating the execution of the JOPES TPFDD requirements as authorized in the SecDef-approved GFMAP.

z.  **Joint Flow Analysis for Sustainment and Transportation** is an analysis tool that determines transportation feasibility of the TPFDD (from origin through arrival at the POD) and provides detailed estimates of resources required to transport military forces (including cargo, personnel, and sustainment).

aa.  **Joint Force Projection.**  Joint force projection retrieves and presents essential force projection information to support decisions of the JPEC throughout the force projection process.  Joint force projection provides read/view access to multiple systems enabling the end user to quickly grasp the status of requirements, deployment, TPFDD status, and reception, staging, onward movement and integration without having to log on to each system individually.

bb.  **Joint Force Requirements Generator II (JFRG II).**  JFRG II is the USMC
software application used to conduct force deployment planning and execution at the Service level.  It interfaces with JOPES IT to merge unsourced operational requirement information with USMC unit move and wholesale logistics planning information and then feed the sourced requirements back into JOPES IT.  The JFRG II program office is currently modernizing the application from a personal computer-based, client-only application to a Service-oriented Web application.

cc.  **JOPES.**  JOPES is a global C2 system used to plan and execute force deployment, redeployment, and high-value sustainment.  It uses a suite of applications and Web services to develop, exchange, validate, and maintain JOPES databases.

(1)  **Joint Operations Planning and Execution System Editing Tool (JET)**
provides the capability to create, add, modify, delete, and generate deployment-related information contained in a JOPES TPFDD.  It offers the ability to retrieve records using any characteristics that exist in the ULN details.  It can then perform TPFDD editing on multiple ULNs based on information retrieved.

(2)  **The Rapid Query Tool** is used to review records and prepare reports on data in the JOPES database without having to use JET.  This tool provides the ability to save the reports and format as a data file and be retrieved in another application or emailing it as a Word document, Excel spreadsheet, or ASCII [American Standard Code for Information Interchange] file.

(3)  **TPFDD Management Tool** allows JOPES functional managers the ability to create, manage, and delete TPFDDs within their assigned series.  The tool also provides copy file, download, and upload utilities to allow requirements to be transferred between various TPFDDs or from external systems.

(4)  **Web SM** provides the user the capability to add, review, update, and delete carrier information.  Carriers may be created and linked to TPFDDs complete with itinerary information, to include planned and reported arrival and departure times at itinerary routing locations.  Additionally TPFDD requirements may be allocated and manifested on carriers and linked with specific carrier on-load and off-load locations.

dd.  **Joint Training Information Management System** provides automated support to the four phases of the Joint Training System: requirements, plans, execution, and assessment.  It allows for the sourcing of forces to meet the joint exercise requirements.

ee.  **Logbook** provides a collaborative workflow of information management capability to the GFM community.  It furnishes real-time cataloging and sharing of data for users to record and reference staffing interactions when developing sourcing requirements.

ff.  The **logistics module** is a Web-based logistics planning program that resides on the USAF Portal and receives and maintains the cargo and personnel details for UTCs and taskings.  It maintains detailed cargo and personnel records and provides an installation-level C2 capability through the logistics module schedule.

gg.  **The Marine Air-Ground Task Force Deployment Support System** is a standalone system used by USMC operating forces to support force deployment planning and execution.  It is the database and interface hub for unit deployment.  Through the use of extensive reference files, the system provides actual data to JFRG II to create an executable TPFDD.  It reads/writes standard military shipping labels, and active RFID tags.  It collects and formats data for transmission to the ITV server and exchanges information with USMC, other service and joint logistics, movement and distribution systems.

hh.  **The Mobility Enterprise Information Service** provides interoperability between AMC capabilities/systems and all external domains (networks).  This enterprise messaging capability integrates information exchange architectures with minimal or no binary coding requirements.  It maintains both legacy and current business rules, manages versioning of services and supports multiple transport mediums.  This service provides a cloud composition that serves C2 data.  It provides the ability to track ITV and provide feasibility analysis.

ii.  **The Mobilization and Deployment Information System** is the USA's authoritative source of force mobilization, deployment, and rotation information.  It integrates CCMD requirements for USA forces with DA HQ sourcing, assignments, execute orders, mobilization orders, unit readiness information, unit rotation history, and official messaging traffic.  By merging CCMD requirements for forces to internal Army mobilization decisions and finally to major Army command resourcing decisions, this system provides the USA with end-to-end asset visibility for USA units.

jj.  **Preferred Force Generation (PFG).**  PFG automates the identification of preferred forces.  Prior to using PFG, the planner determines the capabilities required by UTCs and then creates a notional TPFDD in JOPES that contains the required types of forces by UTCs.  PFG offers the planner a ranked list of candidate preferred forces, by UIC [unit identification code], for each of the UTCs in the notional TPFDD.  The planner can evaluate the recommendations and accept the recommended unit for each requirement or select another unit from the list of candidates provided.  PFG provides consolidated readiness and availability data from authoritative joint and Service data sources for each unit in the list of candidates.  PFG provides the capability to export identified units selected as preferred forces into the JOPES notional TPFDD.

kk.  **The Port Simulation Model** is a time-stepped, discrete event simulation of SPOE and SPOD during a force deployment.  It provides scenario-specific, force clearance profiles and reports on the use of port assets and can determine a port's reception, staging, clearance, and throughput capabilities.  The model identifies systems or infrastructure constraints and provides port-specific, time-phased force clearance profiles.  The model interfaces with ICODES, calculates the impact of JLOTS, incorporates two- and three-dimensional visualization for training, and interfaces with ELIST to facilitate theater analysis.

ll.  SMS is a USTRANSCOM C2 system for execution of global distribution requirements.  It provides visibility of air, sea, and land transportation assets and provides aggregated reporting of cargo and passenger movements.  Provides requirements planners and unit scheduler's visibility of planned and scheduled air missions, MSC ship schedules, commercial liner service, seaport reference data, and movement of US security risk category cargo.

(1)  **Air Mobility.**  The air mobility phase of SMS is a Web-based tool that provides visibility of scheduled air mobility missions and requirements early in the planning process.  All command levels of all DOD units, wings, and HQ can use SMS as a tool to display missions.

(2)  **Sea Mobility.**  The sea mobility phase provides visibility over sealift requirements through SDDC's IBS and GATES, and MSC's Integrated Command, Control, and Communications reporting system.  SMS also offers a sealift assets database, voyage finder, port locator, and shipping cost calculator.

(3)  **Land Mobility.**  The land mobility phase provides visibility over hazmat.
The arms, ammunition, and explosives movement link in SMS allows access to the database that tracks and records positions for movement of high-risk cargo in the US, inclusive of arms, ammunition, and explosives.
mm.  **Slider.**  Slider is a desktop software application used by USN, USMC and USCG schedulers and force planners to construct future employment schedules for major units in their force structure and provide force availability into PFG.

nn.  **TRAC2ES** is an automated decision support tool that functions as a single C2
system that can be used in peacetime and contingencies.  It provides visibility of intheater patients requiring evacuation, available transportation assets, available hospital beds (by medical specialty), and patient ITV.  TRAC2ES accommodates three modes of operation: planning, forecasting, and reactive planning at both the intertheater and intratheater level.

oo.  Transportation Coordinators' - Automated Information for Movements System II is the USA's deployment and execution system that provides automated support to functions performed by a wide range of users from unit movement officers to installation transportation officers to mode managers responsible for transportation and distribution in support of the full continuum of operations.  Its two major modules are unit move and theater operations.  Unit move includes automated support to assist the unit commander to create, maintain, manage, and update unit equipment, personnel, and deployment information.  Theater operations enables movement control elements to manage and coordinate transportation services during JRSOI and sustainment operations.

pp.  **Transportation Visualizer** is a transportation requirements and plan analysis tool.  It can give users full access to real-time JOPES data and provide a graphic visualization of force and sustainment flows.  It enables planners to aggregate requirements to optimize lift capacity and make applicable modifications to JOPES requirement data.  It allows the transportation analyst to identify and address potential movement issues and enhances the validation and scheduling process by allowing sharing and manipulation of TPFDD data to aid in movement issue resolution and analysis.
qq.  **WebSked** [Web-Enabled Scheduling System] is a Web-based display and analysis application designed to facilitate USN planning and scheduling.  It can be used to import USN force availability into PFG.



## Intentionally Blank Appendix B Sample Time-Phased Force And Deployment Data Letter Of Instruction

See CJCSM 3122.02, Joint Operation Planning and Execution System (JOPES), Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution), for additional guidance on construction of a supplemental TPFDD LOI.

## 1.  Title

US<*CCDR Name*> Supplemental TPFDD Letter of Instruction

## 2.  References

a.  CJCSM 3122 series, Joint Operation Planning and Execution Systems (JOPES).
b.  JP 3-35, Deployment and Redeployment Operations.
c.  JP 5-0, Joint Planning.
d.  Global Force Management Implementation Guidance.
The supported CCDR may modify or add references as appropriate.

## 3.  Purpose

To provide standing supplemental TPFDD instructions specific to US <CCDR's Name>, <*operations, or specific purpose*> to its Service components, subordinate commands, supporting CCDRs and their components IAW reference (c).  Guidance in this LOI is effective immediately and supersedes previous editions.  Should a conflict arise between guidance contained in this instruction, subsequent operation-specific guidelines and reference (c) contact <*CCDR Name*> <*responsible code*> for resolution.  In operations or exercises where this command is a supporting CCDR, the guidance provided by the supported CCDR takes precedence over corresponding guidance in this publication.

## 4.  Table Of Contents

The supported CCDR shall provide an appropriate table of contents.

## 5.  General Information

a.  The following Websites support <*CCDR Name*> operations.
b.  The following Websites support <*CCDR Name*> exercises. c.  The following Websites support <*CCDR Name*> planning.
d.  The following Websites support <*CCDR Name*> <additional activity as appropriate>.

The supported CCDR shall provide appropriate Websites for reference and add or delete subparagraphs as appropriate.

## 6.  Additional Supplemental Time-Phased Force And Deployment Data Letters Of Instruction

Supplemental TPFDD LOIs which have bearing on this document are as follows: The supported CCDR shall provide a list of additional supplemental TPFDD LOIs either from the supported CCDR's own command or other commands and appropriate Websites for where they may be obtained.

## 7.  Points Of Contact

a.  The following personnel or offices provide <*CCDR Name*> operational support.
b.  The following personnel or offices provide <*CCDR Name*> exercise support.
c.  The following personnel or offices provide <*CCDR Name*> planning support.
d.  The following personnel or offices provide <*CCDR Name*> <additional activity as appropriate> support.

The supported CCDR shall provide appropriate points of contact and add or delete subparagraphs as appropriate.

## 8.  Plans, Operation Orders, And Time-Phased Force And Deployment Data

The OPLAN series assigned to <*CCDR Name*> is <*OPLAN Series*>.  PIDs for current
<*CCDR Name*> plans, OPORDs, and TPFDDs will be published on the <*CCDR Name*> <J
Code> Web site.  The supported CCDR shall provide or tailor this section as appropriate.

## 9.  Newsgroups

<*CCDR Name*> news server is <*address for news server*>.  Newsgroups serve as the formal medium for conveying TPFDD related requests, authorizations, verifications, validations, changes, or any general coordination.  Any coordination via telephone will be followed up with a newsgroup.  General service message traffic having bearing on TPFDD activities will be retransmitted in the appropriate newsgroup as well.  The following newsgroups shall be used for coordination on <*CCDR Name*> TPFDDs as follows: The supported CCDR shall provide or tailor this section as appropriate with a table of associated TPFDDs and newsgroups.

## 10.  <Combatant Commander Name> Unit Line Number And Force Module Assignments And Structure

<*CCDR Name*> component commands, subordinate commands, and supporting commands will adhere to the following directed ULN and force module structure when
<*CCDR Name*> is the supported commander.  The supported CCDR will specify ULN and force module assignments in tabular format.  Specific guidance on construct of force modules for validations may be published separately for each exercise or operation.

## 11.  <Combatant Commander Name> Time-Phased Force And Deployment Data Guidance

a.  **General Guidance.**  All planning, execution, and exercise TPFDD coordination and procedures will be accomplished IAW reference (c) unless modified below or amended by additional supplemental instructions.  The guidance in this LOI is directive.

The supported CCDR will specify additional general guidance as appropriate.

b.  **Planning.**  Planning procedures will conform to references (a) and (c) unless modified below or amended by additional supplemental instructions.

(1)  Use of JOPES is directed for TPFDD activities of record. (2)  Use of JCRM is directed to capture the contingency sourcing demand signal and assign FTNs to contingency sourcing requirements.

The supported CCDR will specify additional planning guidance as appropriate.

c.  **Planning for a Crisis.**  Planning procedures for a crisis will conform to reference
(a) unless modified below or amended by additional supplemental instructions.

(1)  Use of JOPES is directed for executing TPFDDs. (2)  Use of JCRM is directed to capture the initial and emergent force requirements and assign FTNs to the requirements.  FTNs will be entered in the FTN field of the appropriate JOPES FRN/ULN to ensure traceability of the requirement.

(3)  Upon allocation of the force requirement as documented via the GFMAP
annex, the appropriate providing organization will be entered in the associated JOPES
FRN/ULN to document the tasked force provider.

(4)  For deployment, supporting CCDRs and force providers will request validation of ULNs via a newsgroup validation request message.  For redeployment, Service components and subordinate commands will request validation of ULNs via a newsgroup validation request message.  Validation requests for more than five ULNs will be consolidated in a force module and the request message will provide the force module reference.  Validation requests will cite the legal authority to deploy referencing the order or vocal order authority.  In the case of verbal orders, the name, rank, and Defense Switched Network (DSN) number for the individual providing the authorization will be provided.
Validation requests must be submitted no later than <*time*>, requests posted outside normal timelines or working hours may be processed on the next business day unless phone notification is provided.  A sample is provided in attachment (1).

(5)  A 24-hour point of contact (POC) and contact phone number for load plan level of detail will be identified in the ULN POC field.

The supported CCDR will specify additional planning guidance as appropriate.

## D.  **Rotation Of Forces And Emergent Requirement Planning.**  Planning For Force Rotations And Emergent Force Requirements Will Conform To References (A), (C), And (F).

(1)  Use of JOPES is directed for executing TPFDDs; additional information technologies may be used to enhance the planning process.

(2)  Use of JCRM is directed to capture the rotational and emergent force requirements and assign FTNs to the requirements.  FTNs will be entered in the FTN field of the appropriate JOPES FRN/ULN to ensure traceability of the requirement.

(3)  Upon allocation of the force requirement as documented via the GFMAP
annex, the appropriate providing organization will be entered in the associated JOPES FRN/ULN to document the tasked force provider.

(4)  For deployment, supporting CCDRs and force providers will request validation of ULNs via a newsgroup validation request message.  For redeployment, Service components and subordinate commands will request validation of ULNs via a newsgroup validation request message.  Validation requests will cite the legal authority to deploy referencing the order or vocal order authority.  In the case of verbal orders, the name, rank, and DSN number for the individual providing the authorization will be provided.  Validation requests must be submitted no later than <*time*>, requests posted outside normal timelines or working hours may be processed on the next business day unless phone notification is provided.  A sample is provided in attachment (1).

(5)  A 24-hour POC and contact phone number for load plan level of detail will be identified in the ULN POC field.

The supported CCDR will specify additional force rotation and emergent force requirement planning guidance as appropriate.

e.  **Orders.**  The following paragraph shall be used as a standard paragraph in all
<*CCDR Name*> orders for TPFDDs in execution.  Modification is <authorized/not authorized> as appropriate.

THE USE OF JOPES IS DIRECTED. UTILIZE PID <*NUMBER*> FOR
DEPLOYMENT AND PID <*NUMBER*> FOR REDEPLOYMENT.  REQUIREMENTS
MUST FOLLOW PUBLISHED SUPPLEMENT TPFDD LETTER OF INSTRUCTION GUIDANCE AND BE VERIFIED AND VALIDATED IN JOPES ALLOWING USTRANSCOM TO PERFORM TIME-PHASED FORCE CLOSURE ANALYSIS WHEN COMPARED TO OTHER DEFENSE TRANSPORTATION SYSTEM REQUIREMENTS.

USE
NEWSGROUP
<NEWSGROUP
NAME>
<NEWS
SERVER>
FOR
COORDINATION AND VERIFICATION OF ALL JOPES TRANSACTIONS.  FOR EMERGENCY VALIDATIONS DURING NON-WORKING HOURS CONTACT THE
<*CCDR NAME*> JOPES DUTY OFFICER AT <*PHONE NUMBER*>.

In addition, a separate paragraph may contain guidance for ITV.

IN-TRANSIT VISIBILITY (ITV).  TO ENSURE ITV OF DEPLOYING AND
REDEPLOYING PERSONNEL, CARGO AND EQUIPMENT, DOD COMPONENTS, AGENCIES AND MILITARY DEPARTMENTS WILL CAPTURE, PROCESS AND TRANSMIT
SHIPMENT
INFORMATION
FOR
CARGO
EQUIPMENT
IN
ELECTRONIC FORMAT TO MAXIMIZE ELECTRONIC CAPTURE OF MOVEMENT DATA VIA AUTOMATED INFORMATION SYSTEMS FEEDING THE INTEGRATED DATA
ENVIRONMENT/GLOBAL
TRANSPORTATION
NETWORK
CONVERGENCE (IGC) IF UNITS DO NOT HAVE THE MEANS TO SUPPORT
AUTOMATED MANIFEST FEEDS TO IGC, UNITS MUST REQUEST SUPPORT THROUGH HIGHER HEADQUARTERS, MILITARY DEPARTMENT CHANNELS OR
USTRANSCOM.

SHIPPERS/UNITS MUST COMPLY WITH THE PROVISIONS OF DOD
REGULATION 4500.9 SERIES, DEFENSE TRANSPORTATION REGULATION (DTR).  THE ARRIVAL AND DEPARTURE OF UNIT PERSONNEL AND EQUIPMENT AT ALL NOTES FROM ORIGIN TO DESTINATION WILL BE VISIBLE
IN IGC WITHIN 1 HOUR OF THE MOVEMENT EVENT.

The supported CCDR may modify the above paragraphs as appropriate.

f.  **Protection of Movement Information.**  All personnel will comply with guidelines in reference (c) to ensure the proper safeguarding of plan and TPFDD information.

g.  **TPFDD Validation Windows.**  Validation windows specified in reference (c) will be observed with exceptions as noted below.

The supported CCDR will specify additional guidance on validation windows as appropriate.

h.  **Commercial Ticket Program.**  Personnel support exercises will be moved via strategic airlift from POE to POD if the distance between the origin and destination is greater than 300 miles.  If the distance is less than 300 miles, land transportation will be used.  Units with 100 PAX or more may be moved by strategic lift or commercial charter aircraft.  Units under 100 PAX will be considered for movement under the common ticket program.  Units with less than 30 PAX will be moved by the common ticket program.  Units with between 30 and 100 PAX will be considered to move under the Group Operational Passenger System. Individual units not meeting strategic lift minimums will be considered for aggregated lift if available.

The supported CCDR will specify additional guidance or modify this guidance on the commercial ticket program as appropriate.

i.  **Port Handling/In-Land Transportation (PHIT) Funds.**  Cargo moved via land mode in support of CJCS exercises are authorized joint funding called PHIT funds.  Units may use PHIT funds obtained through the exercise transportation account code for channel movements.  PHIT funds can only be used to move people and cargo between unit installations and channel commercial ports.  Component commands, organizations, and agencies will need to contact the appropriate component command operations directorate to receive PHIT funds.

The supported CCDR will specify additional guidance or modify this guidance on the PHIT as appropriate.

j.  **Hazardous Materials.**  Records containing hazmat must be explicitly identified in the validation request and coded with the proper cargo category code in the level II ULN
detail.  An aircraft diplomatic clearance worksheet for hazardous cargo is provided in attachment 2.  This document is unclassified when filled in, and must be submitted with the cargo load plan.  The foreign clearance guide available via NIPRNET at https://www.fcg.pentagon.mil/fcg.cfm or SIPRNET at http://www.fcg.pentagon.smil.mil provides details regarding country clearance, entrance and exit criteria.  Some country descriptions provide sensitive or hazardous cargo considerations.  Additionally USTRANSCOM provides hazmat guidance via their unclassified homepage at http://public.transcom.mil via navigation of the following links: Publications, DOC, DTR, Part II, Chapter 204 or via https://business.transcom.mil/customerportal/docs/splash html, DTR 4500.9, Part II, Chapter 204.  The sites also provide numerous links to other useful transportation Web sites.  Additional questions regarding hazmat can be directed either to the SDDC Operations Center, for surface movement (sealift, rail, and truck) or to the 618th Air Operations Center Tanker Airlift Control Center (618 AOC [TACC]), Aerial Port Control Center for airlift movement execution.

The supported CCDR will specify additional guidance or modify this guidance on hazmat as appropriate.

k.  **Load and Stow Plans.**  Component commands, subordinate commands, supporting commands and agencies will submit load plan information as soon as possible after USTRANSCOM acceptance of the validation request for lift allocation and within 48 hours of request from a lift provider.  Load plans will be submitted to HQ AMC/618 AOC (TACC)
for all airlift requirements and stow planning coordinated with HQ MSC and HQ SDDC for all sealift requirements.  Direct liaison authorized is granted to coordinate load and stow plans.  Hazmat requirements must be explicitly identified on all load and stow plans.

The supported CCDR will specify additional guidance or modify this guidance on load and stow plans as appropriate.

## L.  **Ustranscom Planning Factors**

(1)  For determining sealift movement days:
(a)  RLD to ALD business rule: 1 day for every 450 miles
(b)  ALD to EAD business rule: 25 days off the east coast and 15 days off the west coast
(c  EAD to LAD business rule: 7 days
(2)  For air movement loads:

(a)  C-5: 61 STONs (oversized and outsized) and 51 PAX (b)  C-17: 45 STONs (oversized and outsized) or 90 PAX (c)  C-130: 12.0 STONs (bulk) or 80 PAX (d)  Commercial: 130 PAX
(3)  For land movement days:
(a)  500 miles per day per driver (b)  Arrangements can be made for dual drivers to double the daily distance at a cost increase to the installation or service
(4)  For land movement loads:
(a)  Trucks: average loading capacity is 48 feet and 24 STONs
(b)  Truckload defined as:

(c)  60% length usage (d)  Over-dimensional height and width items
(e)  Overweight items (f)  Non-over-dimensional or overweight truck count based upon percentage of
24 STON weight limit
(g)  Cubic capacity based on over-dimension limits of 576 inches (length)
102 inches (width)  162 inches (height)
(5)  Permits:
(a)  Carriers obtain permits through permit agent or state DOT (b)  SDDC can expedite the state DOT permit process for shipment declared
"Essential to National Defense"

## Validation Request Message Format

From: <*Supporting component, command or agency*> <*Office Code*>
To: <*Supported CCDR*>
Info: <*Appropriate Commands*>
<*Classification*>
Subj: <*Supporting component, command or agency*> <*operation or exercise name*>
Validation Request Message <*number*> <*C-date*>, <PID>
Ref: (a) <*Legal authority to deploy (message, verbal orders)*> (b) <*Others as appropriate*>
1.  Per reference (a), the below ULNs in PID <PID> are forwarded for validation, or the following force module <*force module designation*> with a ULN count of <*number*> is forwarded for validation.

2.  The ULNs in paragraph 1 are free of fatal errors.  Changes are not authorized by providing organizations without prior coordination with the office via this newsgroup.

3.  Remarks. <*Additional remarks as appropriate*>
Drafted/Released: <*Name/Rank/DSN*> / <*Name/Rank/DSN*>
Classified by: <*Authority if classified otherwise not used*>
Reason: <*Reason code if above is used*>
Declassify on: <Date if above is used>

## Aircraft Diplomatic Clearance Worksheet For Hazardous Cargo

Purpose and Instructions: Coordinate aircraft diplomatic requests for missions with hazardous cargo between planners, booking agencies controllers, and international clearance specialists.  All blocks must be completed to ensure proper and timely coordination.  This is not a stand-alone form; it must be attached to the aircraft diplomatic clearance worksheet when submitted.

## Example

Proper Shipping Name
PCS
Gross WT
(LBS)
N.E.W. (LBS or KGS)
Class/Div
UN Shipping
Number
Rockets
2
1930
106.994 LBS
1.2E
UN1206
Small Arms Ammo
5
175
0.374 KGS
1.45
UN0012

Note: For ammunition, flares, and other cased items, put the number of boxes for PCS, not units.

## Hazmat For Uln/Mission Number:

Proper Shipping Name
PCS
Gross WT (LBS)
N.E.W. (LBS
or KGS)
Class/Div
UN Shipping
Number

Use additional sheets as required.



Intentionally Blank


## Appendix C References

The development of JP 3-35 is based upon the following primary references:

## 1.  United States Government Publications

a.  Title 10, USC. b.  Unified Command Plan.

## 2.  Department Of Defense Publications

a.  Global Force Management Implementation Guidance Fiscal Year 2016-2017.
b.  DODD 4500.09E, *Transportation and Traffic Management*.
c.  DODD 5100.01, Functions of the Department of Defense and its Major Components.

d.  DODD 5530.3, International Agreements.
e.  Department of Defense Instruction (DODI) 4140.01, DOD Supply Chain Materiel Management Policy.

f.  DODI 5158.05, Joint Deployment Process Owner. g.  DODI 5158.06, *Distribution Process Owner (DPO).*
h.  DTR 4500.9-R, *Defense Transportation Regulations,* Part I, *Passenger Movement*. i.  DTR 4500.9-R, *Defense Transportation Regulations,* Part II, *Cargo Movement*.
j.  DTR 4500.9-R, *Defense Transportation Regulations,* Part III, Mobility.
k.  DTR 4500.9-R, *Defense Transportation Regulations,* Part V, *Customs.* l.  DTR 4500.9-R, *Defense Transportation Regulations,* Part VI, Intermodal.

## 3.  Chairman Of The Joint Chiefs Of Staff Publications

a.  CJCSI 3110.01J, (U) 2015 *Joint Strategic Capabilities Plan (JSCP)*.
b.  CJCSI 3141.01E, Management and Review of Joint Strategic Capabilities Plan
(JSCP)-Tasked Plans.
c.  CJCSI 3151.01C, Global Command and Control System Common Operational Picture Reporting Requirements.

d.  CJCSI 3500.01H, *Joint Training Policy for the Armed Forces of the United States*.
e.  CJCSI 4120.02, *List of Priorities-DOD Transportation Movement Priority System.*
f.  CJCSI 5120.02D, *Joint Doctrine Development System*.
g.  CJCSM 3122.01A, Joint Operation Planning and Execution System (JOPES)
Volume I  (Planning Policies and Procedures).

h.  CJCSM 3122.02D, Joint Operation Planning and Execution System (JOPES)
Volume III (Time-Phased Force and Deployment Data Development and Deployment Execution).

i.  CJCSM 3130.03, Adaptive Planning and Execution (APEX) Planning Formats and Guidance.

j.  CJCSM 3130.06B, *(U) Global Force Management Allocation Policies and Procedures.*
k.  CJCSM 3150.16E, Joint Operation Planning and Execution System Reporting Structure (JOPESREP).

l.  CJCSM 3500.03E, Joint Training Manual for the Armed Forces of the United States.

m.  CJCSM 3500.04F, *Universal Joint Task List Manual*.
n.  CJCSM 5120.01A, Joint Doctrine Development Process. o.  CJCS Guide 3122, *Time Phased Force and Deployment Data (TPFDD) Primer.*
p.  CJCS Guide 3130, Adaptive Planning and Execution (APEX) Overview and Policy Framework.

q.  JP 1, *Doctrine for the Armed Forces of the United States*. r.  JP 1-0, *Joint Personnel Support*.
s.  JP 2-0, *Joint Intelligence*.
t.  JP 2-01, *Joint and National Intelligence Support to Military Operations*. u.  JP 2-03, Geospatial Intelligence in Joint Operations. v.  JP 3-0, *Joint Operations*.
w.  JP 3-05, *Special Operations*.
x.  JP 3-08, *Interorganizational Cooperation.*
y.  JP 3-10, *Joint Security Operations in Theater*.
z.  JP 3-11, *Operations in Chemical, Biological, Radiological, and Nuclear Environments.*
aa.  JP 3-13.3, *Operations Security*. bb.  JP 3-16, *Multinational Operations*.
cc.  JP 3-17, *Air Mobility Operations*.
dd.  JP 3-33, *Joint Task Force Headquarters*. ee.  JP 3-57, *Civil-Military Operations*.
ff.  JP 3-61, *Public Affairs*.
gg.  JP 4-0, *Joint Logistics*.
hh.  JP 4-01, *The Defense Transportation System*.
ii.  JP 4-01.2, *Sealift Support to Joint Operations*.
jj.  JP 4-01.5, *Joint Terminal Operations*.
kk.  JP 4-01.6, *Joint Logistics Over-the-Shore*. ll.  JP 4-02, *Joint Health Services*.
mm.  JP 4-05, *Joint Mobilization Planning*.
nn.  JP 4-09, *Distribution Operations.* oo.  JP 4-10, *Operational Contract Support.* pp.  JP 5-0, *Joint Planning*. qq.  JP 6-0, *Joint Communications System*.

## 4.  United States Army Publications

a.  ATP 3-35, *Army Deployment and Redeployment*.
b.  Field Manual (FM) 4-01, *Army Transportation Operations*.

## 5.  United States Marine Corps Publications

a.  MCWP 3-40F, *Transportation Operations.*
b.  Marine Corps Doctrine Publication 4, *Logistics*.
c.  Marine Corps Tactical Publication 13-10B, *Combat Cargo Operations Handbook.*

## 6.  United States Navy Publications

a.  NWP 5-01, *Navy Planning*.
b.  Navy Tactics, Techniques, and Procedures (NTTP) 4-01.1, Navy Advanced Base Logistics Operations.

c.  NTTP 4-01.5, *Strategic Mobility and Unit Movement Operations*.

## 7.  United States Air Force Publications

a.  Air Force Doctrine Document (AFDD) 3-17, *Air Mobility Operations*.
b.  AFDD 4-0, *Combat Support*.
c.  Air Force Pamphlet 10-1403, Air Mobility Planning Factors.

## 8.  Multi-Service Publications

a.  ATP 4-01.45 [FM 4-01.45]/MCRP 3-40F.7/NTTP 4-01.3/AFTTP 3-2.58, Multi-
Service Tactics, Techniques, and Procedures for Tactical Convoy Operations.

b.  Marine Corps Tactical Publication 13-10D (MCWP 3-32)/NTTP 3-02.3M, Maritime Prepositioning Force Operations.

c.  NWP 3-62M/MCWP 13-10, *Seabasing*.

## 9.  United States Transportation Command Publication

USTRANSCOM Campaign Plan for Global Distribution 9033 (CP-GD 9033).



## Appendix D Administrative Instructions 1.  User Comments

Users in the field are highly encouraged to submit comments on this publication using the Joint Doctrine Feedback Form located at:
https://jdeis.js.mil/jdeis/jel/jp_feedback_form.pdf and e-mail it to:  js.pentagon.j7.mbx.jeddsupport@mail.mil.  These comments should address content (accuracy, usefulness, consistency, and organization), writing, and appearance.

## 2.  Authorship

a.  The lead agent for this publication is the Director for Operations (J-3), Joint Staff.
The Joint Staff doctrine sponsor for this publication is the Director for Logistics (J-4).

b.  The following staff, in conjunction with the joint doctrine development community, made a valuable contribution to the revision of this joint publication: lead agent, Mr. Ara Manjikian, Joint Staff J-35, Future Operations Cell; Joint Staff doctrine sponsor, Lt Col Michelle Whitfield, Joint Staff J-4; Lt Col Nathan Maresh, Joint Staff J-7, Joint Doctrine Analysis Division; and Mr. Mitchell Johnson, Joint Staff J-7, Joint Doctrine Division.

## 3.  Supersession

This publication supersedes JP 3-35, *Joint Deployment and Redeployment Operations,*
31 January 2013.

## 4.  Change Recommendations

a.  To provide recommendations for urgent and/or routine changes to this publication, please complete the Joint Doctrine Feedback Form located at:
https://jdeis.js.mil/jdeis/jel/jp_feedback_form.pdf and e-mail it to: js.pentagon.j7.mbx.jeddsupport@mail.mil.
b.  When a JS directorate submits a proposal to the CJCS that would change source document information reflected in this publication, that directorate will include a proposed change to this publication as an enclosure to its proposal.  The Services and other organizations are requested to notify the JS J-7 when changes to source documents reflected in this publication are initiated.

## 5.  Lessons Learned

The Joint Lessons Learned Program (JLLP) primary objective is to enhance joint force readiness and effectiveness by contributing to improvements in doctrine, organization, training, materiel, leadership and education, personnel, facilities, and policy.  The Joint Lessons Learned Information System (JLLIS) is the DOD system of record for lessons learned and facilitates the collection, tracking, management, sharing, collaborative resolution, and dissemination of lessons learned to improve the development and readiness of the joint force.  The JLLP integrates with joint doctrine through the joint doctrine development process by providing lessons and lessons learned derived from operations, events, and exercises.  As these inputs are incorporated into joint doctrine, they become institutionalized for future use, a major goal of the JLLP.  Lessons and lessons learned are routinely sought and incorporated into draft JPs throughout formal staffing of the development process.  The JLLIS Website can be found at https://www.jllis.mil (NIPRNET) or http://www.jllis.smil.mil (SIPRNET).

## 6.  Distribution Of Publications

Local reproduction is authorized, and access to unclassified publications is unrestricted.  However, access to and reproduction authorization for classified JPs must be IAW DOD Manual 5200.01, Volume 1, DOD Information Security Program: Overview, Classification, and Declassification, and DOD Manual 5200.01, Volume 3, DOD
Information Security Program: Protection of Classified Information.

## 7.  Distribution Of Electronic Publications

a.  Joint Staff J-7 will not print copies of JPs for distribution.  Electronic versions are available on JDEIS
Joint Electronic Library Plus
(JEL+)
at https://jdeis.js.mil/jdeis/index.jsp (NIPRNET) and http://jdeis.js.smil.mil/jdeis/index.jsp (SIPRNET), and on the JEL at http://www.dtic.mil/doctrine (NIPRNET).

b.  Only approved JPs are releasable outside the combatant commands, Services, and Joint Staff.  Defense attaches may request classified JPs by sending written requests to Defense Intelligence Agency (DIA)/IE-3, 200 MacDill Blvd., Joint Base Anacostia- Bolling, Washington, DC 20340-5100.

c.  JEL CD-ROM.  Upon request of a joint doctrine development community member, the Joint Staff J-7 will produce and deliver one CD-ROM with current JPs.  This JEL CD- ROM will be updated not less than semi-annually and when received can be locally reproduced for use within the combatant commands, Services, and CSAs.


## Glossary Part IAbbreviations, Acronyms, And Initialisms

| ACSA          | acquisition and cross-servicing agreement           |
|---------------|-----------------------------------------------------|
| A/DACG        | arrival/departure airfield control group            |
| AFDD          | Air Force doctrine document                         |
| AFTTP         | Air Force tactics, techniques, and procedures       |
| AGT           | Automated Global Force Management Tool              |
| AIS           | automated information system                        |
| AIT           | automatic identification technology                 |
| ALD           | available-to-load date                              |
| AMC           | Air Mobility Command                                |
| AMP           | analysis of mobility platform                       |
| AOR           | area of responsibility                              |
| APEX          | Adaptive Planning and Execution                     |
| APOD          | aerial port of debarkation                          |
| APOE          | aerial port of embarkation                          |
| ASCC          | Army Service component command                      |
| ATP           | Army techniques publication                         |
| AV            | asset visibility                                    |
|               |                                                     |
| C2            | command and control                                 |
| CAAF          | contractors authorized to accompany the force       |
| CBP           | Customs and Border Protection (DHS)                 |
| CBRN          | chemical, biological, radiological, and nuclear     |
| CCDR          | combatant commander                                 |
| CCIR          | commander's critical information requirement        |
| CCMD          | combatant command                                   |
| CDRUSSOCOM    | Commander, United States Special Operations Command |
| CDRUSTRANSCOM | Commander, United States Transportation Command     |
| CIRT          | Collaborative Issue Resolution Tool                 |
| CJCS          | Chairman of the Joint Chiefs of Staff               |
| CJCSI         | Chairman of the Joint Chiefs of Staff instruction   |
| CJCSM         | Chairman of the Joint Chiefs of Staff manual        |
| COA           | course of action                                    |
| COCOM         | combatant command (command authority)               |
| CONOPS        | concept of operations                               |
| CONPLAN       | concept plan                                        |
| CONUS         | continental United States                           |
| COP           | common operational picture                          |
| CRAF          | Civil Reserve Air Fleet                             |
| CRG           | contingency response group                          |
| CSA           | combat support agency                               |
| CSS           | combat service support                              |
| CULT          | common-user land transportation                     |
|               |                                                     |
| DA           | Department of the Army                              |
|--------------|-----------------------------------------------------|
| DCAPES       | Deliberate and Crisis Action Planning and Execution |
| Segments     |                                                     |
| DDOC         | Deployment and Distribution Operations Center       |
| (USTRANSCOM) |                                                     |
| DEPORD       | deployment order                                    |
| DHHS         | Department of Health and Human Services             |
| DHS          | Department of Homeland Security                     |
| DIA          | Defense Intelligence Agency                         |
| DISA         | Defense Information Systems Agency                  |
| DJS          | Director, Joint Staff                               |
| DLA          | Defense Logistics Agency                            |
| DOD          | Department of Defense                               |
| DODD         | Department of Defense directive                     |
| DODI         | Department of Defense instruction                   |
| DOS          | Department of State                                 |
| DOT          | Department of Transportation                        |
| DRRS-S       | Defense Readiness Reporting System-Strategic        |
| DSCA         | defense support of civil authorities                |
| DSN          | Defense Switched Network                            |
| DTR          | Defense Transportation Regulation                   |
| DTRA         | Defense Threat Reduction Agency                     |
| DTS          | Defense Transportation System                       |
|              |                                                     |
| EAD          | earliest arrival date                               |
| ELIST        | enhanced logistics intratheater support tool        |
| ERIMP        | En route Infrastructure Master Plan (USTRANSCOM)    |
|              |                                                     |
| FEMA         | Federal Emergency Management Agency (DHS)           |
| FM           | field manual (Army)                                 |
| FMS          | foreign military sales                              |
| FMTS         | Fourth Estate Manpower Tracking System              |
| FP           | force provider                                      |
| FTN          | force tracking number                               |
|              |                                                     |
| GATES        | Global Air Transportation Execution System          |
| GCC          | geographic combatant commander                      |
| GCCS         | Global Command and Control System                   |
| GCCS-J       | Global Command and Control System-Joint             |
| GCSS         | Global Combat Support System                        |
| GCSS-J       | Global Combat Support System-Joint                  |
| GDSS         | Global Decision Support System                      |
| GEF          | Guidance for Employment of the Force                |
| GFM          | global force management                             |
| GFMAP        | Global Force Management Allocation Plan             |
| GFMB         | Global Force Management Board                       |
| GFMIG        | Global Force Management Implementation Guidance       |
|--------------|-------------------------------------------------------|
|              |                                                       |
| HD           | homeland defense                                      |
| HN           | host nation                                           |
| HNS          | host-nation support                                   |
| HQ           | headquarters                                          |
|              |                                                       |
| IAW          | in accordance with                                    |
| IBS          | Integrated Booking System                             |
| ICODES       | Integrated Computerized Deployment System             |
| IED          | improvised explosive device                           |
| IGC          | Integrated Data Environment/Global Transportation     |
|              | Network Convergence                                   |
| ISB          | intermediate staging base                             |
| IT           | information technology                                |
| ITO          | installation transportation officer                   |
| ITV          | in-transit visibility                                 |
|              |                                                       |
| JCRM         | Joint Capabilities Requirements Manager               |
| JDDC         | Joint Deployment and Distribution Coordinator         |
| (USTRANSCOM) |                                                       |
| JDDOC        | joint deployment and distribution operations center   |
| JDET         | joint distribution enabling team                      |
| JDPO         | joint deployment process owner                        |
| JET          | Joint Operation Planning and Execution System editing |
| tool         |                                                       |
| JFC          | joint force commander                                 |
| JFP          | joint force provider                                  |
| JFRG II      | joint force requirements generator II                 |
| JIPOE        | joint intelligence preparation of the operational     |
| environment  |                                                       |
| JLOTS        | joint logistics over-the-shore                        |
| JMC          | joint movement center                                 |
| JOA          | joint operations area                                 |
| JOPES        | Joint Operation Planning and Execution System         |
| JP           | joint publication                                     |
| JPEC         | joint planning and execution community                |
| JPP          | joint planning process                                |
| JRSOI        | joint reception, staging, onward movement, and        |
| integration  |                                                       |
| JS           | Joint Staff                                           |
| JTF          | joint task force                                      |
| JTF-PO       | joint task force-port opening                         |
|              |                                                       |
| LAD          | latest arrival date                                   |
| LNO          | liaison officer                                       | | LOC                      | line of communications                                   |
|--------------------------|----------------------------------------------------------|
| LOI                      | letter of instruction                                    |
|                          |                                                          |
| MAGTF                    | Marine air-ground task force                             |
| MARAD RRF                | Maritime Administration Ready Reserve Force              |
| MCC                      | movement control center                                  |
| MCIP                     | military customs inspection program                      |
| MCRP                     | Marine Corps reference publication                       |
| MCWP                     | Marine Corps warfighting publication                     |
| MDDOC                    | Marine air-ground task force deployment and distribution |
| operations center        |                                                          |
| METT-T                   | mission, enemy, terrain and weather, troops and support  |
| availabletime available |                                                          |
| MHE                      | materials handling equipment                             |
| MOG                      | maximum (aircraft) on ground                             |
| MSC                      | Military Sealift Command                                 |
| MSR                      | main supply route                                        |
|                          |                                                          |
| NALSS                    | naval advanced logistic support site                     |
| NATO                     | North Atlantic Treaty Organization                       |
| NEO                      | noncombatant evacuation operation                        |
| NFLS                     | naval forward logistic site                              |
| NGA                      | National Geospatial-Intelligence Agency                  |
| NGB                      | National Guard Bureau                                    |
| NTTP                     | Navy tactics, techniques, and procedures                 |
| NURP                     | non-unit-related personnel                               |
| NWP                      | Navy warfare publication                                 |
|                          |                                                          |
| OA                       | operational area                                         |
| OCONUS                   | outside the continental United States                    |
| OE                       | operational environment                                  |
| OPCON                    | operational control                                      |
| OPLAN                    | operation plan                                           |
| OPORD                    | operation order                                          |
| OPSEC                    | operations security                                      |
| OSD                      | Office of the Secretary of Defense                       |
|                          |                                                          |
| PAX                      | passengers                                               |
| PFG                      | Preferred Force Generation                               |
| PHIT                     | port handling/in-land transportation                     |
| POC                      | point of contact                                         |
| POD                      | port of debarkation                                      |
| POE                      | port of embarkation                                      |
| POG                      | port operations group                                    |
| POL                      | petroleum, oils, and lubricants                          |
| PSA                      | port support activity                                    |
| PSU            | port security unit                                     |
|----------------|--------------------------------------------------------|
|                |                                                        |
| RC             | Reserve Component                                      |
| RFF            | request for forces                                     |
| RFID           | radio frequency identification                         |
|                |                                                        |
| 618 AOC (TACC) | 618th Air Operations Center (Tanker Airlift Control    |
| Center)        |                                                        |
| SA             | staging area                                           |
| SDDC           | Military Surface Deployment and Distribution Command   |
| SDOB           | Secretary of Defense Orders Book                       |
| SecDef         | Secretary of Defense                                   |
| SIPRNET        | SECRET Internet Protocol Router Network                |
| SMS            | Single Mobility System                                 |
| SOF            | special operations forces                              |
| SOP            | standard operating procedure                           |
| SPM            | single port manager                                    |
| SPOD           | seaport of debarkation                                 |
| SPOE           | seaport of embarkation                                 |
|                |                                                        |
| TAA            | tactical assembly area                                 |
| TACON          | tactical control                                       |
| TCC            | transportation component command                       |
| TD             | theater distribution                                   |
| TDCP           | theater distribution campaign plan                     |
| TPFDD          | time-phased force and deployment data                  |
| TRAC2ES        | United States Transportation Command Regulating and    |
|                | Command and Control Evacuation System                  |
| TTAN           | transportation tracking account number                 |
|                |                                                        |
| UCP            | Unified Command Plan                                   |
| UDL            | unit deployment list                                   |
| ULN            | unit line number                                       |
| USA            | United States Army                                     |
| USAF           | United States Air Force                                |
| USC            | United States Code                                     |
| USCG           | United States Coast Guard                              |
| USD(P&R)       | Under Secretary of Defense for Personnel and Readiness |
| USG            | United States Government                               |
| USMC           | United States Marine Corps                             |
| USN            | United States Navy                                     |
| USSOCOM        | United States Special Operations Command               |
| USSTRATCOM     | United States Strategic Command                        |
| USTRANSCOM     | United States Transportation Command                   |
| UTC            | unit type code                                         |
|                |                                                        |

Glossary

| VISA    | Voluntary Intermodal Sealift Agreement    |
|---------|-------------------------------------------|
|         |                                           |
| Web SM  | Web Scheduling and Movement               |
| WRM     | war reserve materiel                      |
|         |                                           |
|         |                                           |

## Part IiTerms And Definitions

asset visibility.  Provides users with information on the location, movement, status and
identity of units, personnel, equipment, and supplies.  Also called AV.  (Approved for incorporation into the DOD Dictionary.)
cargo increment number.  A seven-character alphanumeric field that uniquely describes
a non-unit-cargo entry (line) in the Joint Operation Planning and Execution System time-phased force and deployment data.  (DOD Dictionary.  Source: JP 3-35)
deployment.  The movement of forces into and out of an operational area.  (Approved for
incorporation into the DOD Dictionary.)
earliest arrival date.  A day, relative to C-day, that is specified as the earliest date when
a unit, resupply shipment, or replacement personnel can be accepted at a port of debarkation during a deployment.  Also called **EAD.**  (Approved for incorporation into the DOD Dictionary.)
force closure.  The point in time when a supported commander determines that sufficient
personnel and equipment resources are in the assigned operational area to carry out assigned tasks.  (Approved for incorporation into the DOD Dictionary.)
force requirement number.  An alphanumeric code used to uniquely identify force entries
in a given operation plan time-phased force and deployment data.  Also called **FRN.**
(DOD Dictionary.  Source: JP 3-35)
force tracking.  The process of gathering and maintaining information on the location,
status, and predicted movement of each element of a unit including the unit's command element, personnel, and unit-related supplies and equipment while in transit to the specified operational area.  (DOD Dictionary.  Source: JP 3-35)
force visibility.  The current and accurate status of forces, their current mission, future
missions, location, mission priority, and readiness status.  (Approved for incorporation
into the DOD Dictionary.)
global force management.  1.  Processes that align force assignment, apportionment, and
allocation methodologies in support of strategic guidance. (JP 3-35)  2.  A process to align assignment, allocation, and apportionment of forces to combatant commanders in support of the national defense strategy and joint force availability requirements. (DODI 8260.03)  Also called **GFM.**  (Approved for incorporation into the DOD
Dictionary.)
intermediate staging base.  A tailorable, temporary location used for staging forces,
sustainment, and/or extraction into and out of an operational area.  Also called **ISB.** (Approved for incorporation into the DOD Dictionary.)
joint flow and analysis system for transportation.  None.  (Approved for removal from
the DOD Dictionary.)
joint reception, staging, onward movement, and integration.  A phase of joint force
projection occurring in the operational area during which arriving personnel,
equipment, and materiel transition into forces capable of meeting operational requirements.  Also called **JRSOI.**  (DOD Dictionary.  Source: JP 3-35)
latest arrival date.  A day, relative to C-Day, that is specified by the supported combatant
commander as the latest date when a unit, resupply shipment, or replacement personnel can arrive at the port of debarkation and support the concept of operations.  Also called LAD.  (Approved for incorporation into the DOD Dictionary.)
marshalling area.  A location in the vicinity of a reception terminal or pre-positioned
equipment storage site where arriving unit personnel, equipment, materiel, and accompanying supplies are reassembled, returned to the control of the unit commander, and prepared for onward movement.  (DOD Dictionary.  Source: JP 3- 35)
naval advanced logistic support site.  An overseas location used as the primary
transshipment point in the theater of operations for logistic support.  Also called
NALSS.  (DOD Dictionary.  Source: JP 3-35)
naval forward logistic site.  An overseas location, with port and airfield facilities nearby,
which provides logistic support to naval forces within the theater of operations during major contingency and wartime periods.  Also called **NFLS.**  (DOD Dictionary. Source: JP 3-35)
port operations group.  A task-organized unit, located at the seaport of embarkation
and/or debarkation that assists and provides support in the loading and/or unloading and staging of personnel, supplies, and equipment from shipping.  Also called **POG.**
(DOD Dictionary.  Source: JP 3-35)
port support activity.  A tailorable support organization composed of mobilization station
assets that ensures the equipment of the deploying units is ready to load.  Also called PSA.  (DOD Dictionary.  Source: JP 3-35)
reception.  1. All ground arrangements connected with the delivery and disposition of air
or sea drops.  2. Arrangements to welcome and provide secure quarters or transportation for defectors, escapees, evaders, or incoming agents.  3. The process of receiving, off-loading, marshalling, accounting for, and transporting of personnel, equipment, and materiel from the strategic and/or intratheater deployment phase to a sea, air, or surface transportation point of debarkation to the marshalling area.  (DOD Dictionary.  Source: JP 3-35)
recovery and reconstitution.  1.  Those actions taken by one nation prior to, during, and
following an attack by an enemy nation to minimize the effects of the attack,
rehabilitate the national economy, provide for the welfare of the populace, and
maximize the combat potential of remaining forces and supporting activities.  2.  Those actions taken by a military force during or after operational employment to restore its combat capability to full operational readiness.  (DOD Dictionary.  Source: JP 3-35)
redeployment.  The transfer or rotation of forces and materiel to support another
commander's operational requirements, or to return personnel, equipment, and materiel to the home and/or demobilization stations for reintegration and/or outprocessing.  (Approved for incorporation into the DOD Dictionary.)
staging.  Assembling, holding, and organizing arriving personnel, equipment, and
sustaining materiel in preparation for onward movement.  (DOD Dictionary.  Source: JP 3-35)
staging area.  1. Airborne - A general locality between the mounting area and the objective
of an airborne expedition, through which the expedition or parts thereof pass after mounting, for refueling, regrouping, and/or exercise, inspection, and redistribution of troops.  2. Other movements - A general locality established for the concentration of troop units and transient personnel between movements over the lines of communications.  Also called SA.  (Approved for incorporation into the DOD Dictionary.)
tactical assembly area.  An area that is generally out of the reach of light artillery and the
location where units make final preparations (pre-combat checks and inspections) and rest, prior to moving to the line of departure.  (DOD Dictionary.  Source: JP 3-35)
transportation closure.  None.  (Approved for removal from the DOD Dictionary.)
unit line number.  A seven-character alphanumeric code that describes a unique increment
of a unit deployment, i.e., advance party, main body, equipment by sea and air, reception team, or trail party, in the time-phased force and deployment data.  Also called **ULN.**  (DOD Dictionary.  Source: JP 3-35)
unit movement control center.  None.  (Approved for removal from the DOD Dictionary.) unit movement data.  A unit equipment and/or supply listing containing corresponding
transportability data.  Also called **UMD.**  (Approved for incorporation into the DOD Dictionary.)
unit type code.  A Joint Chiefs of Staff-developed and -assigned code, consisting of five
characters that uniquely identify a "type unit."  Also called **UTC.**  (Approved for inclusion in the DOD Dictionary.)
validation.  1. A process associated with the collection and production of intelligence that
confirms that an intelligence collection or production requirement is sufficiently important to justify the dedication of intelligence resources, does not duplicate an
existing requirement, and has not been previously satisfied.  (JP 2-01)  2. A part of target development that ensures all vetted targets meet the objectives and criteria outlined in the commander's guidance and ensures compliance with the law of war and rules of engagement.  (JP 3-60)  3. In the context of time-phased force and deployment data validation, it is an execution procedure whereby all the information records in the time-phased force and deployment data are confirmed error-free and accurately reflect the current status, attributes, and availability of units and
requirements.  (JP 3-35)  4. A global force management procedure for assessing combatant command requirements to determine viability, for sourcing, with respect to risk and prioritization between competing needs and the nature of the requirement.  (JP 3-35)  (Approved for incorporation into the DOD Dictionary.)

## Joint Doctrine Publications Hierarchy

after publication no later than 5 years after signature
 JSDS prepares JS staffing package  JSDS staffs the publication via JSAP for
signature
 Joint doctrine development
community (JDDC) submission to fill extant operational void
 Joint Staff (JS) J-7 conducts frontend analysis
 Joint Doctrine Planning Conference
validation
 Program directive (PD) development
and staffing/joint working group
 PD includes scope, references,
outline, milestones, and draft authorship
 JS J-7 approves and releases PD to
lead agent (LA) (Service, combatant command, JS directorate)
 LA selects primary review authority (PRA) to develop the first
draft (FD)
 PRA develops FD for staffing with JDDC  FD comment matrix adjudication  JS J-7 produces the final coordination (FC) draft, staffs to
JDDC and JS via Joint Staff Action Processing (JSAP) system
 Joint Staff doctrine sponsor (JSDS) adjudicates FC comment
matrix
 FC joint working group