Military reference books and manuals (2009-2023, Volume 5)

CJCSM 3122.02B

25 May 2001

DISTRIBUTION

Distribution A, B, C, and J plus the following:

Copies

Secretary of Defense

…………………………

Commandant, US Coast Guard .…….……………………

Commander, US Element, NORAD

………………

Director, Central Intelligence Agency …..………………

Director, Federal Emergency Management Agency

…………..

Director, Joint Warfighting Center ….………………………..……

Commanding General, Marine Corps Combat

Development Center …..……..……………………………………

President, National Defense University

………………

President, Armed Forces Staff College .………………

CJCSM 3122.02B

25 May 2001

LIST OF EFFECTIVE PAGES

The following is a list of effective pages for this manual. Use this list to verify

the currency and completeness of the document. An "O" indicates a page in

the original document.

PAGE

CHANGE

PAGE

CHANGE

1 thru 6

E-1 thru E-10

i thru vi

E-A-1 thru E-A-2

A-1 thru A-4

E-B-1 thru E-B-2

B-1 thru B-6

E-C-1 thru E-C-2

B-A-1 thru B-A-2

E-D-1 thru E-D-2

B-B-1 thru B-B-2

E-E-1 thru E-E-2

B-C-1 thru B-C-2

E-F-1 thru E-F-2

B-D-1 thru B-D-2

F-1 thru F-4

B-E-1 thru B-E-2

G-1 thru G-4

B-F-1 thru B-F-4

G-A-1 thru G-A-6

B-G-1 thru B-G-2

H-1 thru H-4

B-H-1 thru B-H-2

H-A-1 thru H-A-14

B-I-1 thru B-I-2

H-B-1 thru H-B-10

C-1 thru C-2

H-C-1 thru H-C-4

D-1 thru D-8

H-D-1 thru H-D-2

D-A-1 thru D-A-2

H-E-1 thru H-E-2

D-B-1 thru D-B-2

H-F-1 thru H-F-2

D-C-1 thru D-C-2

H-G-1 thru H-G-4

D-D-1 thru D-D-2

H-H-1 thru H-H-2

D-E-1 thru D-E-2

I-1 thru I-6

D-F-1 thru D-F-2

J-1 thru J-2

GL-1 thru GL-24

iii

CJCSM 3122.02B

25 May 2001

ENCLOSURE A

SITUATION DEVELOPMENT AND CRISIS ASSESSMENT

1. General

a. Crisis Action Planning Procedures. This document describes in detail

the activities to be conducted in each CAP phase. However, in a fast-breaking

crisis, CAP procedures can be significantly compressed and steps overlapped.

Further, a crisis can be so time critical, or a single COA so obvious, that the

first written directive might be a deployment or execute order. In these cases,

the supported commander must ensure that all required actions from each

CAP phase are completed whenever possible. To prepare for such eventualities

within their area of responsibility (AOR), supported commanders should

prepare and publish AOR-specific supplemental instructions to the standard

TPFDD LOI (see Enclosure H) before the onset of a crisis to support assigned

military operations. This planning will ensure that a TPFDD can be developed

as rapidly as possible.

b. Deployment and Redeployment Operations. These are operational

imperatives that support the full range of military operations and are a

function of the joint force mission. The joint deployment process begins when

planning is initiated for force projection operations in response to an action or

event that requires protection of US national interests. Deployment operations

involve four phases:

(1) Predeployment activities; (2) Movement to and

activities at the port of embarkation (POE); (3) Movement to port of

debarkation (POD); and (4) Joint reception, staging, onward movement, and

integration (JRSOI) activities. Redeployment activities involve the transfer of

individuals, units/or material, but are not necessarily the reversing of the

deployment process. Redeployment may include movement of forces or

material from one area to another, to another location in the same area, or to

the zone of interior for further employment, or home. Redeployment operations

encompass four phases: (1) Recovery and reconstitution and pre-

redeployment activities, (2) Movement to and from activities at POE, (3)

Movement to POD, and (4) JRSOI. During deployment and redeployment

operations, the supported commander must build and validate requirements,

determine predeployment standards, and balance and regulate the

transportation flow. The supported commander performs these activities with

assistance from assigned supporting combatant commands, Service component

commands, Services, and combat support agencies.

A-1

Enclosure A

CJCSM 3122.02B

25 May 2001

c. The Supported Commander. In accordance with Joint Pub 1-02, the

supported commander is "The commander having primary responsibility for all

aspects of a task assigned by the Joint Strategic Capabilities Plan (JSCP) or

other joint operation planning authority. In the context of joint operation

planning, this term refers to the commander who prepares operation plans or

operation orders in response to requirements of the Chairman of the Joint

Chiefs of Staff." A combatant commander is usually designated as the

supported commander for an operation, but there are exceptions and

alternatives. If an operation is to occur within the area of operations of a

subordinate unified command, its commander is usually the supported

commander. If a joint task force (JTF) is preplanned in an operation plan

(OPLAN) or concept plan (CONPLAN) (with or without TPFDD), the CINC may

designate the commander of the JTF (CJTF) as the supported commander

responsible for all CAP and associated JOPES-required activities. The CJTF

will be provided with a SIPRNET capability and JOPES automated data

processing (ADP)-trained planners so information can be entered and ongoing

JOPES activities monitored. If the JTF is subordinate to a CINC, the CINC will

be the supported commander and be responsible for the required CAP/JOPES

functions. In any case, the CJTF will be provided with a SIPRNET capability,

including JOPES applications; access to additional GCCS databases such as

Common Operational Picture (COP), Global Status of Resources and Training

System (GSORTS), and others; and trained operators so that information can

be input and ongoing execution activities monitored using JOPES applications

and GCCS databases. See reference b for detailed JTF planning guidance and

procedures.

d. Inter- and Intratheater Lift Management. The deployment procedures

described in this manual apply to all modes and sources of transportation,

inter and intratheater, from origin to destination. The scheduling, validation,

and manifesting procedures described in Enclosures D, E, and F are applicable

for supported and supporting command movement control agencies and all lift

providers. Strategic lift assets may be under the control of the supported or

supporting commander and be used for both inter and/or intratheater

deployments. Additionally, even though USTRANSCOM is responsible for

intertheater deployment, the supported commander is responsible for

intratheater transportation to include JRSOI of forces, personnel, and material

from the POD to final destination. To fulfill his transportation responsibilities,

the supported commander has movement control agencies to manage

intratheater movement.

A-2

Enclosure A

CJCSM 3122.02B

25 May 2001

2. Phase I--Situation Development. During CAP Phase I, a combatant

commander may recognize an event or incident of national interest and report

the event or incident to the Chairman of the Joint Chiefs of Staff. The

combatant commander will provide an assessment report to the Chairman of

the Joint Chiefs of Staff detailing the nature of the crisis, the forces readily

available, major constraints to possible force employment, and actions taken, if

any, within existing ROE. The combatant commander’s report will contain a

discussion of various COAs under consideration. The Chairman of the Joint

Chiefs of Staff monitors the situation, evaluates the combatant commander’s

actions being taken under the ROE, orders additional intelligence gathering if

necessary, and advises the NCA as the situation develops. Appropriate

members of the JPEC in accordance with reference a, JOPES Volume I, initiate

procedures. No specific TPFDD procedures are required during this phase.

3. Phase II--Crisis Assessment. Phase II begins with a report from the

combatant commander and ends with a decision by the NCA to return to the

precrisis situation or to have military options developed for possible

consideration and possible use. Phase II is characterized by increased

awareness and reporting and intense information-gathering activity. The

supported commander will continue to evaluate the crisis and begin to review

current applicable OPLANs and CONPLANs.

a. Establish Newsgroup. The following preparatory actions are required to

use JOPES in support of CAP. The supported commander will establish an

operation newsgroup on SIPRNET, in accordance with required joint

procedures and the command’s Information Management Plan, and coordinate

with appropriate members of the JPEC to establish permissions as appropriate.

The supported commander will ensure the newsgroup is announced in the

standard JOPES paragraph to all JOPES orders (warning, planning, deploy,

execute, etc.). When established, the newsgroup is the primary means of

coordinating deployment or redeployment planning and execution. In crisis

situations involving more than one supported command, the Chairman of the

Joint Chiefs of Staff may establish a single newsgroup to coordinate TPFDD

development and deployment execution actions. During Phase II, the JPEC

members will enter the newsgroup(s) and monitor TPFDD development and

deployment execution information.

b. Permissions. JPEC members must obtain required user accounts and

permissions to participate in all phases of CAP and execution. Access

requirements include:

(1) JOPES database and database select (DBSELECT) capability at

primary and backup sites.

A-3

Enclosure A

CJCSM 3122.02B

25 May 2001

(2) Database server sites.

(3) JOPES software applications.

(4) OPLAN plan identification numbers (PIDs) (OPLAN series

permissions). OPLAN series are discussed in Enclosure B.

(5) Restricted-access PIDs (PID permissions) as authorized by supported

command’s functional manager. PID permissions are discussed in Enclosure

(6) Newsgroup access.

(7) GCCS databases such as COP, GSORTS, etc.

During the crisis assessment phase, functional managers should review the

lists of authorized GCCS users (includes JOPES, COP, GSORTS users) at their

database sites, verify that users have permissions necessary to accomplish

their assigned duties, and coordinate with other GCCS functional managers to

ensure site and GCCS (to include JOPES, COP, GSORTS, etc.) permissions are

available for designated users at alternate sites. JOPES functional managers

are to verify and/or obtain required access for crisis action participants at their

backup sites.

A-4

Enclosure A

CJCSM 3122.02B

25 May 2001

ENCLOSURE B

COURSE OF ACTION DEVELOPMENT

1. General. Phase III, Course of Action Development, begins with a decision to

develop possible military COAs, normally transmitted by a CJCS warning order

and ends when the Chairman of the Joint Chiefs of Staff analyzes the COAs

contained in the supported commander’s estimate and the COAs are presented

to the NCA.

2. Supported Commander

a. The Standard TPFDD LOI and AOR-Specific Supplemental Instructions.

During the COA development phase, the supported commander will implement

TPFDD development and execution procedures contained in the TPFDD LOI

contained in this document. The JOPES standard TPFDD LOI provides

procedures and direction to the supported commander and components,

subordinate joint force commanders (including the Theater Special Operations

Command (SOC)), supporting commanders, and other members of the JPEC

pertaining to the identification of force requirements, the sourcing of forces to

fulfill identified requirements, and the deployment and redeployment of those

forces. During the COA development phase, if time permits, the supported

commander publishes the AOR-specific supplemental instructions to the

standard TPFDD LOI. An electronic copy of the standard TPFDD LOI is also

located at <http://nmcc20a.nmcc.smil.mil/~dj9jfdbm.html>. These AOR-

specific instructions describe theater-specific force deployment planning and

execution procedures such as intratheater lift constraints, validation windows

that deviate from the standard TPFDD LOI for reasons such as overflight

clearance, APOE/D/SPOE/D requirements, additional validation procedures,

etc. The supported commander should publish these AOR-specific instructions

on the local JOPES webpage. Appendix E contains sample CINC/AOR-specific

supplemental instructions to the standard TPFDD LOI. Both the standard

TPFDD LOI and Appendix E are made available on the supported commander’s

home page in the area containing information relevant to the crisis. Adherence

to the standard TPFDD LOI and the CINC/AOR-specific supplement is key to

successful conduct of deployment and redeployment operations.

b. COA PID, Access, and Distribution. In JOPES, a PID is assigned to a

specific OPLAN option or COA supporting the OPLAN. Time permitting, the

supported commander will create or modify the JOPES database and assign

PIDs to represent the OPLAN or COA within that OPLAN. The supported

commander will post a newsgroup message to the gccs.jopes.fm newsgroup

B-1

Enclosure B

CJCSM 3122.02B

25 May 2001

requesting distribution of the PID. A sample request is contained in Appendix

A. Access to, and distribution of, a PID can be controlled and restricted in

various ways. When establishing the PID(s), the creator will determine the

extent of plan access (restricted or normal access) and distribution (local or

distributed) at the time of creation. Plan access can be expanded at any time.

Restricted access should be used only for highly sensitive operations when

further access will jeopardize national security and will not be used as a

routine procedure. To access a specific plan, the JOPES functional manager at

the primary JOPES database server site must first grant a user. If the plan is

not loaded at the local JOPES database server site, but a user still requires

access, then the user, in coordination with the JOPES functional manager and

GCCS Site Security Officer (GSSO), must acquire access at a site where the

TPFDD is available. If the TFPDD is restricted access, the user must acquire

permission for the TPFDD from the OPLAN originator as described in the

following paragraphs.

(1) Restricted-Access Distributed Plan. The supported commander

restricts access to a plan to specifically designated userids. GCCS-T will be

used for TOP SECRET planning as required. The plan originator is the only

person who can add or delete userid permissions for the plan. Only personnel

given special permissions by the site functional managers can create restricted-

access plans. A restricted-access distributed plan should be used in COA

development and deployment execution when other JPEC members are

required to participate in the COA development, but security considerations

require controlled access on a strict need-to-know basis. When other JPEC

members are required to participate in COA development, the plan status

should be changed to normal access and distributed to appropriate JOPES

database sites.

(2) Restricted-Access Local Plan. A user requires JOPES "create"

permission to create a restricted-access local plan for which access is restricted

by userid. The restricted-access local plan resides at only one JOPES database

server site but can later be distributed to other sites if required. In both cases,

plan access is restricted by userid. The creator of a restricted-access local plan

must notify the JNOCC Functional Manager to distribute the plan to other

JOPES database sites. Once a restricted-access local plan has been

distributed, the supported commander continues to control access to the

restricted-access PID; but because the JNOCC is sometimes the originator of a

distributed plan, the supported commander may have to direct the JNOCC

Functional Managers to change user access as required.

(3) Normal Access Local Plan. A normal access local plan is available to

all users with appropriate plan series access and host permissions at a single

host where the plan resides.

B-2

Enclosure B

CJCSM 3122.02B

25 May 2001

(4) Normal Access Distributed Plan. A normal access distributed plan is

available to all users with appropriate plan series access and JOPES database

site permissions at one or more JOPES database sites where the plan resides.

c. JOPES Plan Distribution. A plan can reside at any or all GCCS JOPES

database sites. JNOCC Functional Managers accomplish plan distribution in

coordination with the plan originator. The plan owner requests distribution

from the JNOCC via a message posted in the gccs.jopes.fm global newsgroup.

The JNOCC Functional Manager sets up a plan distribution table that results

in initial networking (replication) of plan data to selected GCCS JOPES

database sites. This distribution table allows JOPES to automatically forward

all data transactions for that plan to all other GCCS JOPES database sites on

distribution for the plan. A newly created restricted access or normal PID can

be networked before records are added or loaded. The Normal JOPES OPLAN

Distribution Matrix can be found at http://nmcc20a.nmcc.smil.mil/~dj9jfdbm

/Oplan_dist.html.

d. COA TPFDD Development Options. Supported commander planners

have two basic options, create a COA TPFDD by using or modifying an existing

TPFDD or developing a new TPFDD (no-plan scenario).

(1) Creating COA TPFDD Using Existing TPFDD. A TPFDD already

residing in the JOPES database may be modified, if required, to meet CJCS

warning order and supported commander requirements. The nonunit data

projections created during the deliberate planning process are available only for

COA planning and are not used for execution. Force modules (FMs) from

established OPLANs may also be used as a starting point for a new TPFDD.

(2) Developing a New TPFDD. Where no TPFDD exists, it will be

necessary to build a COA TPFDD from scratch. Planners can develop force

requirements from a variety of sources, including existing TPFDDs, FMs from

existing TPFDDs, on-line input, and Service-unique systems. Planners should

employ, when feasible, the Joint Flow and Analysis for Transportation (JFAST)

and the notional requirements generator in JFAST at this point in the process.

Time permitting, sustainment lift requirements may also be estimated using

the JFAST Sustainment Generator or other JOPES and Service-unique

software capabilities.

e. Creating Flexible Deterrent Options (FDO) as COAs. The supported

commander may wish to request the deployment of FDOs before execution of

the total OPLAN. To do so, the supported commander will identify FDOs

requiring deployment as FMs from a TPFDD. These options should be

constructed so that initiation of deployments is completed within the warning

B-3

Enclosure B

CJCSM 3122.02B

25 May 2001

time specified in the JSCP (or warning/alert order), without mobilization and

with apportioned lift. FDO FMs should also include Air Mobility Command

(AMC), Military Traffic Management Command (MTMC), and Military Sealift

Command (MSC) mission support requirements. Estimates of transportation

feasibility (including numbers and types of aircraft, utilization rates, and

critical assumptions) developed jointly by the supported commander and lift

providers, will be included in the description data of the force module. As part

of a request to deploy FDOs, the supported commander must copy the FDO FM

to the appropriate execution PID. Appropriate dates and routing data must be

changed, if required, to time phase the new PID to ensure requirements are

consolidated at appropriate ports. Any unique requirements not found in the

parent OPLAN should also be added at this time. Force enhancement (FE)

options will also need to be addressed. FEs are described as a subset of a

FDO. FEs are force improvements to military FDOs, designed to provide

increased ability to counter critical enemy capabilities and reduce in-place

vulnerabilities.

f. Entering Plan Information. As COA TPFDDs are developed and loaded

into JOPES, the supported commander must enter specific plan information

into each PID. Appendix B lists data elements that the supported commander

should enter or update.

g. Preparing COAs for Deployment Estimate. After COA TPFDDs are

created, the supported commander will notify the lift providers via the

operation newsgroup that the COA TPFDD is available for a deployment

estimate. Appendix C provides a sample newsgroup message. The supported

commander should make each COA TPFDD available as soon as possible and

not wait until all COA TPFDDs are completed. Appendix D lists COA TPFDD

data elements that may be included.

h. Developing Commander’s Estimates. The supported commander reviews

the deployment estimates, incorporates them as appropriate in the Commander’s

Estimate, and forwards the estimate to the Chairman of the Joint Chiefs of Staff

with recommended COAs in accordance with reference a.

i. TPFDD Time Standard

(1) The time standard shall be 72 hours from notification and receipt by

the supported commander to validation of TPFDD-level 4 detail-for the first 7

days of the mission. (Note: Based on supported commander guidance, assets

deploying from origin to destination on unit organic transportation may not

require level 4 detail.)

B-4

Enclosure B

CJCSM 3122.02B

25 May 2001

(2) The notification from which performance in meeting the time standard

can be tracked will be a duly authorized CJCS order (e.g., alert, deployment) after

the NCA approves a COA. The specific type of order will be situation dependent.

Regardless of the type of order, the coordination instructions within the order

will:

(a) Direct TPFDD development and unit sourcing to meet the approved

COA.

(b) Indicate the start of the 72-hour period to develop a level 4 TPFDD

and validate the first 7 days of the mission. Start time will be provided as a date

time group (DTG, xxxxxxZ MMM YR) to allow transmission and receipt of the

message by the supported commander prior to start of the 72-hour period.

Should a mission change occur requiring development and approval of a new

COA, the 72-hour requirement will be reset pending the supported commander’s

receipt of new COA.

supporting commanders, Services, and agencies) and their responsibilities.

Additionally, the message will authorize collaboration and coordination with these

organizations.

(d) Identify mission statement, COA, major force list, location forces will

be deployed to, timing for deployment, and anticipated duration of deployment.

(e) Provide a project code (as appropriate)

(f) Include the following statements:

Supported Commander: In conjunction with supporting

commanders, develop a TPFDD and validate the first 7 days of the

mission to level 4 detail within 72-hours of the following DTG

(xxxxxxZ MMM YR).

Supporting Commanders: Source and verify units and assist the

supported commander in developing a TPFDD with the first 7 days of

the mission to level 4 detail within 72-hours of the following DTG

(xxxxxxZ MMM YR).

C day/L hour will be defined in a CJCS Deployment or Execution Order.

3. Supporting Commanders and Service Components

B-5

Enclosure B

CJCSM 3122.02B

25 May 2001

a. COA TPFDD Development. Supporting commanders and components

will normally be requested to participate in COA TPFDD development. The

level of participation, access to the data, and control over input will be

determined by the supported commander. Close coordination is necessary

among the supported commander, supporting commanders, and their

components during TPFDD development.

b. Reviewing COA TPFDD to Determine Feasibility. When notified by the

supported commander that a COA TPFDD is available for review, the

supporting commanders and components review each COA to determine

supportability (e.g., force shortfalls, preferred POEs, and force availability

dates). The supported commander may request that supporting commanders

and components provide a feasibility assessment of the COA TPFDDs

(Commanders Evaluation Request, reference a, Enclosure Q). The COA PID or

FM is updated by supporting commanders as required in accordance with

supported commander guidance. Upon completion of the review, the

supporting commanders and components forward a supportability message to

the supported commander (See Appendix E).

4. Lift Providers. Lift providers will activate CATs (where appropriate); monitor

the operation newsgroup; evaluate COA TPFDD(s) under development;

consolidate deployment estimates; determine aerial, sea, rail, and inland

waterway POEs and PODs; determine preliminary transportation channels; and

develop deployment estimates and closure profiles for submission to the

supported commander upon request. Lift providers will advise the JPEC of

POEs and PODs to be used and preliminary airlift and sealift channels via the

operation newsgroup. If multiple COAs are to be assessed, the deployment

estimates for one COA will not be delayed pending completion of estimates for

any subsequent COA. Sample deployment messages are provided at

Appendixes G through I. Lift providers will ensure that each COA developed is

assessed for transportation feasibility and that transportation mission support

movement requirements are stated in the TPFDD and considered in the

deployment estimates

5. Services. The Services monitor the COA development process and take the

necessary action to support Service component commander requirements.

B-6

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX B TO ENCLOSURE B

COA INFORMATION DATA

During COA development, the supported commander provides the following

COA identification data (COA and OPLAN are synonymous below).

DATA

REQUIRED

ELEMENT

INFORMATION

1. Current Status

OPLAN Identification

of OPLAN.

OPLAN Date

OPLAN Security Classification

TPFDD Security Classification

2. Narrative Scope

OPLAN Title (Long Name)

and Concept.

Mission

As Required

OPLAN Objectives

Objective Area

Concept of Operations

Deployment Concept

Conditions for Execution

Assumptions

Critical Resources

Constraints

Unit Shortfalls

Resupply Shortfall

Personnel Shortfalls

Supporting OPLANs

Supporting CINCs

Major Forces in OPLAN

Plan Mobilization Required

Mobilization Lead Time

Appendix B

B-B-1

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX C TO ENCLOSURE B

SAMPLE DEPLOYMENT ESTIMATE REQUEST NEWSGROUP MESSAGE

FROM:

(SUPPORTED COMMANDER)

TO:

LIFT PROVIDER CAT

CLASSIFICATION

OPER/OPERATION NAME//

MSGID/GENADMIN/ORIGINATOR//

SUBJ/SUBJECT: DEPLOYMENT ESTIMATE ( )//

REF/A/TYPE OF REF/ORIGINATOR/DATE OR DTG/SERIAL #/SPECIAL

NOTATION//

AMPN/FREE TEXT TO EXPLAIN PRECEDING REF SET. (JNOCC MESSAGE,

JOPES DATABASE COA INITIALIZATION)//

POC/NAME/RANK-POSITION/LOC:NAME/TEL:NONSEC TEL

#/SECTEL:SECTEL #//

RMKS/MESSAGE TEXT OR COMMENTS.

( ) REQUEST CONSOLIDATED

DEPLOYMENT ESTIMATE NLT (DDHHMMZMMMYY) FOR EACH OF THE

FOLLOWING:

( ) COA 1.

(PID), (SHORT TITLE).

B. ( ) COA 2. (PID), (SHORT TITLE).

( ) COAS ARE AVAILABLE FOR JNOCC DISTRIBUTION TO THE

FOLLOWING COMMANDERS:

( ) COMMANDER A.

B. ( ) COMMANDER B.

NOTE: PARAGRAPH 2 NOT REQUIRED IF COA BUILT AS A NETWORK

PLAN.

Appendix C

B-C-1

Enclosure B

CJCSM 3122.02B

25 May 2001

NOTE: IF COA DATA NOT PROVIDED VIA JOPES, USE THE FOLLOWING

PARAGRAPH.

( ) REF REQUESTED PIDS FOR _____ COAS. THESE PIDS ARE NOT IN

JOPES BECAUSE (DESCRIBE PROBLEM). REQUEST USTRANSCOM

PREPARE A CONSOLIDATED DEPLOYMENT ESTIMATE USING THE

FOLLOWING AGGREGATED DATA:

COMMON-USER *EMBARK *DEBARK

PID

MODE REGION REGION PAX BULK

OVER OUT

TOTAL

COA 1

AIR

CEN-US SWA

###

COA 1

SEA

SE-US SWA

###

( ) PORT THROUGHPUT DATA:

( ) APOES

(1)

( ) APOE 1

(2)

( ) APOE 2

B. ( ) SPOES

(1)

( ) SPOE 1

(2)

( ) SPOE 2

* EMBARK AND DEBARK REGIONS ARE DESCRIPTIVE OF THE GENERAL

AREA OF OVERALL ONLOAD AND OFFLOAD.//

Appendix C

B-C-2

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX D TO ENCLOSURE B

COA DEVELOPMENT DATA

The supported commander is responsible for entry of the following data

elements during COA development (COA and OPLAN are synonymous) (See

Enclosure D, subparagraph 3b and Appendix C to Enclosure D for guidance on

sourcing):

DATA

REQUIRED

ELEMENT

INFORMATION

1. Required Forces

ULNs in OPLAN

a. Force Description 1/ ULN Description consisting of:

ULN

ULN UTC

ULN Unit Level Code (ULC)

ULN Providing Organization

ULN SERVICE

ULN DESCRIPTION

ULN Parent Indicator Code

ULN Force Indicator Code

FM ID

b. Movement Characteristics 2/-

ULN Authorized Personnel

ULN Personnel Requiring

Transport

ULN BULK CARGO, Short Tons

(STONs)

ULN BULK CARGO,

Measurement Tons (MTONs)

ULN OVERSIZE CARGO (STONs)

ULN OVERSIZE CARGO

(MTONs)

ULN OUTSIZE CARGO (STONs)

ULN OUTSIZE CARGO (MTONs)

Appendix D

B-D-1

Enclosure B

CJCSM 3122.02B

25 May 2001

DATA

REQUIRED

ELEMENT

INFORMATION

c. Routing Data 3/

Routing data consisting of:

ULN, POD, PREFERRED MODE

ULN, POD, PREFERRED SOURCE

ULN POD GEOLOC CODE

ULN DESTINATION GEOLOC

ULN DESTINATION PREFERRED MODE

ULN DESTINATION PREFERRED

SOURCE

ULN POD PRIORITY

ULN POD LOAD CONFIGURATION

ULN POD DISCHARGE CONFIGURATION

ULN DESTINATION LOAD

CONFIGURATION

ULN DEST DISCHARGE CONSTRAINT

d. Time Phasing 4/

Delivery estimates for:

ULN POD EAD

ULN POD LAD

ULN DESTINATION RDD

CINC RDD

1/ The user may select an FM or an OPLAN in JOPES. In this case, ULNs,

cargo increment numbers (CINs), and personnel increment numbers

(PINs), with descriptions, are provided.

2/ During COA development, level 2 data entry is sufficient detail to identify

requirements. Level 4 detail should be provided after the supporting

commander components have identified tasked units.

3/ Routing data are available for OPLAN’s FMs. The user must verify this

data is correct for the crisis. If SVC FMs are used, this data must be

entered. In most cases, adjustments are needed for this data.

4/ This data usually must be changed for a crisis.

Appendix D

B-D-2

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX E TO ENCLOSURE B

SAMPLE COA SUPPORTABILITY NEWSGROUP MESSAGE

FROM: (SUPPORTING COMMANDER OR SERVICE COMPONENT

HEADQUARTERS)

TO:

(SUPPORTED COMMANDER)

INFO: LIFT PROVIDERS CAT

SERVICE HEADQUARTERS

ALCON

CLASSIFICATION

SUBJECT: COA SUPPORTABILITY

REF: ( ) SUPPORTED COMMANDER MESSAGE, DATE-TIME GROUP (DTG),

EVALUATION REQUEST

( ) REF A REQUESTED EVALUATION OF (COAS NAMED BY PID).

( )

(COA #1) CAN BE SUPPORTED WITH AVAILABLE FORCES WITH THE

FOLLOWING CONSTRAINTS:

( ) LIST OF ASSUMPTIONS OR CONSTRAINTS.

B. ( )

(INCLUDE MOBILIZATION REQUIRED, LEAD TIMES).

C. ( ) RECOMMENDED POES, MODE, AND SOURCE TO POES, ETC., AS

REQUIRED.

( )

(COA #2) (SAME AS 2 FOR COA #2).

( ) LIST OF ASSUMPTIONS OR CONSTRAINTS.

B. ( )

(INCLUDE MOBILIZATION REQUIRED, LEAD TIMES).

C. ( ) RECOMMENDED POES, MODE AND SOURCE TO POES, ETC., AS

REQUIRED.

N. ( )

(COA #N).

DRAFTER/RELEASER

Appendix E

B-E-1

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX F TO ENCLOSURE B

SAMPLE DEPLOYMENT ESTIMATE NEWSGROUP MESSAGE

FROM: USTRANSCOM CAT/ OR OTHER LIFT PROVIDER

TO: SUPPORTED COMMANDER

INFO: SUPPORTING COMMANDERS AND SERVICE COMPONENT

HEADQUARTERS

AMC/MTMC/MSC

JOINT STAFF

SERVICE HEADQUARTERS

CLASSIFICATION

SUBJECT: DEPLOYMENT ESTIMATE ( )

REFS: A. WARNING ORDER ( )

B. SUPPORTED COMMANDER DEPLOYMENT ESTIMATE MESSAGE ( )

C. SUPPORTED COMMANDER TPFDD LETTER OF INSTRUCTION ( )

( ) REF A TASKED SUPPORTED COMMANDER TO PREPARE

COMMANDER’S ESTIMATE. REF B DEFINED COA DEPLOYMENT DATA AND

REQUESTED DEPLOYMENT ESTIMATE.

( ) THE DEPLOYMENT ESTIMATE FOR (COA PID) IS (DAY CXXX). AIR

LINES OF COMMUNICATION OPEN ON CXXX AND CONTINUE THROUGH

CLOSURE. SEA LINES OF COMMUNICATION OPEN ON CXXX FOR UNITS.

OCEAN LINER SERVICE FOR MOVEMENT OF SUSTAINMENT IS AVAILABLE,

AND CARGO CAN BE BOOKED IMMEDIATELY UPON RECEIPT OF A

DEPLOYMENT ORDER. BASED ON C-DAY/L-HOUR, FIRST COMMERCIAL

VESSEL CAN ARRIVE IN THE THEATER OF OPERATIONS ON CXXX.

Appendix F

B-F-1

Enclosure B

CJCSM 3122.02B

25 May 2001

( ) AIRLIFT

( ) AIRLIFT ASSETS REQUIRED TO SUPPORT THIS DEPLOYMENT

ESTIMATE FOLLOW. LIFT WILL BE ALLOCATED IN ACCORDANCE WITH

APPENDIX 4 TO REF C. (Lift provider should identify lift assets anticipated to

be available for execution and used in preparing the deployment estimate. This

will assist the supported commander in final prioritization of requirements

against available lift for execution.)

TYPE

TOTAL NUMBER REQUIRED TOTAL NUMBER AVAILABLE

C141

C17

CRAF WB

C130

B. ( ) ASSUMPTIONS

(1)

( ) AVAILABILITY IS BASED ON (PROPOSED OR ASSUMED)

C-DAY, L-HOUR OF (DTG).

(2)

( ) MAXIMUM ON GROUND (MOG) (LIST BY SPECIFIC LIMITING

FACTOR AT SPECIFIC LOCATIONS (GEOLOCS). (MOG OF RESPECTIVE

APODS INCLUDE CONSIDERATIONS OF TACAIR BEDDOWN AND RESOURCE

AVAILABILITY FURNISHED BY THE SUPPORTED CINC.)

(3)

( ) CONSTRAINTS (OVERFLIGHT, LANDING RIGHTS, EN ROUTE

SUPPORT, ETC.).

(4) ( ) SECDEF AUTHORIZATION TO ACTIVATE CRAF STAGE (I, II,

AND III).

(5) ( ) AIRLIFT TO SUPPORT MOVEMENT OF TCC MISSION

SUPPORT PACKAGES IS INCLUDED IN THIS ESTIMATE.

( ) SEALIFT

( ) STRATEGIC SEALIFT ASSETS REQUIRED TO SUPPORT THIS

DEPLOYMENT ESTIMATE FOLLOW. LIFT WILL BE ALLOCATED IN

ACCORDANCE WITH APPENDIX 4 TO REF C.

TYPE

TOTAL NUMBER REQUIRED TOTAL NUMBER AVAILABLE

FSS

Appendix F

B-F-2

Enclosure B

CJCSM 3122.02B

25 May 2001

RO/RO

LMSR (Large Medium Speed Roll-On/Roll-Off)

OTHER*

* INCLUDES BREAKBULK, LASH, SEABEE

B. ( ) ASSUMPTIONS

(1)

( ) AVAILABILITY IS BASED ON (PROPOSED OR ASSUMED)

C-DAY, L-HOUR OF (DTG).

(2)

( ) READY RESERVE FORCE ASSETS WILL ACTIVATE WITHIN

STATED READINESS STATUS.

(3)

( ) ALL CANALS AND CHOKE POINTS REMAIN OPEN.

(4)

( ) CONVOY OPERATIONS ARE NOT REQUIRED.

(5)

( ) UNITS ARRIVE AT SPOES AND ARE AVAILABLE TO LOAD AS

STATED IN (COA PID).

(6)

( ) SUFFICIENT ONLOAD AND OFFLOAD CAPABILITY IS IN

PLACE AT SPOES AND SPODS.

(7)

( ) THERE ARE NO DELAYS BECAUSE OF BUNKERING OR

CREW SHORTAGES.

( ) POC IS (NAME, RANK) AT (DSN, SECURE DSN, FAX, SECURE FAX, AND

E-MAIL).

Appendix F

B-F-3

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX G TO ENCLOSURE B

SAMPLE AMC NEWSGROUP COA DEPLOYMENT ESTIMATE MESSAGE

FROM: COM AMC

TO: USTRANSCOM CAT

CLASSIFICATION

SUBJECT: COA DEPLOYMENT ESTIMATE ( )

REF:

( ) THE DEPLOYMENT ESTIMATE FOR (COA PID) FOR AMC AIRLIFT IS

(DAY CXXX).

( ) ALLOCATION OF AIRLIFT FOR THIS ESTIMATE IS AS FOLLOWS:

TYPE

TOTAL NUMBER

C141

C17

CRAFWB

C130

( ) AIRLIFT AVAILABILITY IS BASED ON (PROPOSED OR ASSUMED)

C-DAY/L-HOUR OF (DTG).

( ) ASSUMPTIONS MADE FOR THIS ESTIMATE ARE:

( ) MOG (BY SPECIFIC LIMITING FACTOR AT SPECIFIC STATION.

B. ( ) CONSTRAINTS (OVERFLIGHT AND LANDING RIGHTS AND

CONSTRAINTS).

C. ( ) AIRCRAFT AVAILABILITY (GIVE REASONS).

D. ( ) OTHERS.

Appendix G

B-G-1

Enclosure B

CJCSM 3122.02B

25 May 2001

APPENDIX I TO ENCLOSURE B

SAMPLE MSC COA DEPLOYMENT ESTIMATE NEWSGROUP MESSAGE

FROM: COM MSC

TO: USTRANSCOM

CLASSIFICATION

SUBJECT: COA DEPLOYMENT ESTIMATE ( )

REF:

( ) THE DEPLOYMENT ESTIMATE FOR (COA PID) FOR MSC STRATEGIC

SEALIFT IS (DAY CXXX).

( ) ALLOCATION OF STRATEGIC SEALIFT FOR THIS ESTIMATE IS AS

FOLLOWS:

TYPE

TOTAL NUMBER

( ) STRATEGIC SEALIFT AVAILABILITY IS BASED ON (PROPOSED OR

ASSUMED) C-DAY/L-HOUR OF (DTG).

( ) ASSUMPTIONS FOR THIS ESTIMATE INCLUDE:

( )

(PORT DOCKING AND DISCHARGE PRIORITY RIGHTS AND

CONSTRAINTS.)

B. ( )

(SAILING TIMES BY TYPE SHIP.)

C. ( ) PORT LOAD AND DISCHARGE RATES (BASED UPON VALUES

PROVIDED BY THE SUPPORTED COMMANDER.)

D. ( )

Appendix I

B-I-1

Enclosure B

CJCSM 3122.02B

25 May 2001

ENCLOSURE C

COA SELECTION

General. Phase IV begins when COAs are presented to the NCA and ends when

a COA is selected. The primary activity in Phase IV rests with the Chairman of

the Joint Chiefs of Staff and the NCA following procedures detailed in reference

a. The supported commander continues to monitor the situation and to

prepare in-theater forces for preparatory moves. The supporting commanders

prepare to specify forces to support the COAs under consideration while other

members of the JPEC continue monitoring and coordinating activities of

previous phases.

C-1

Enclosure C

CJCSM 3122.02B

25 May 2001

ENCLOSURE D

EXECUTION PLANNING

1. General. Phase V, Execution Planning, begins when a planning or an alert

order is received and ends when an executable operation order (OPORD) is

developed and approved for execution on order. JOPES procedures supporting

the JPEC during CAP Phase V are extremely critical to successful execution

and must be accomplished in a timely and accurate fashion.

2. Supported Commander. The supported commander, upon receipt of an

alert order or planning order, converts the approved or selected COA into an

OPORD. This process generally includes the following steps.

a. Reviewing Warning, Alert, or Planning Order. The warning order, alert

order, or planning order normally establishes the proposed C-day and L-hour.

However, the actual C-day/L-hour may not be established until approval of an

execute or deployment order. The alert order may also give authority, if

appropriate, to pre-position strategic lift assets preparatory to deployment

operations for the selected COA. Coordinating instructions establish time

frames for each JPEC member to complete their assigned deployment execution

planning tasks. The supported commander reviews both messages and begins

detailed execution planning for the selected COA. (Note: FMs should be built

during execution planning to allow tracking of the commander’s designated

major force units. General guidelines are provided in the Standard TPFDD LOI.

The supported commander may further refine these guidelines in the AOR-

specific supplemental instructions.)

b. Review or Publish AOR-Specific Supplemental Instructions for the

Standard TPFDD LOI. A message in the crisis newsgroup will be used to

announce the availability of required revisions.

c. Review and Update the AOR-Specific Supplement to the Standard TPFDD

LOI. Changes required to CINC/AOR specific supplement to the standard

TPFDD LOI should be made and published on the supported commander’s

home page. A message in the crisis newsgroup will be used to announce the

availability of required revisions.

d. Adjusting COA/OPORD. The supported commander, in close

coordination with supporting commanders and Service components, reviews

force and sustainment requirements and makes adjustments to the COA as

required to meet alert or planning order guidance. Using the available

automated data processing systems the supporting commander adjusts

D-1

Enclosure D

CJCSM 3122.02B

25 May 2001

priorities and delivery time frames.

(Note: Nonunit requirements in this phase

are notional estimates and are used primarily to ensure available lift is

reserved for movement of actual resupply and/or replacements. The nonunit

portion of the TPFDD is not executable.)

e. Validation. The first deployment increment (usually the first 7 days of

airlift and ground movement and first 30 days of sealift) is validated for

movement scheduling by earliest arrival date (EAD). Validation is the

execution procedure used by supported commander components, supporting

commanders, and providing organizations to confirm to the supported

commander and lift providers that all validated TPFDD records contain no fatal

transportation pre-edit report errors and accurately reflect the current status,

attributes, and availability of unit requirements. Unit readiness, movement

dates, and passenger and cargo details are confirmed with units before

validation occurs. The supported commander’s validation of a requirement

indicates the force and the timing of its arrival/departure support the

operational mission. Any exceptions must be noted in the appropriate

newsgroup with supporting rationale. Failure to validate these details may

result in invalidation of the requirement(s) during the scheduling process. The

validation process, especially during a large multi-Service deployment, involves

close coordination among supported and supporting commanders, Service

components, and lift providers. Direct liaison among components of supported

and supporting commanders, the moving units, and lift providers is essential

for coordinating details of deployment. Supported commander directs

compliance with TPFDD validation process/procedures as outlined in the

Standard TPFDD LOI, including the CINC/AOR-specific supplement to the

standard TPFDD LOI. Validation of the TPFDD begins during the execution-

planning phase and continues into actual execution.

f. Scheduling and Assessing Deployment. Strategic and theater lift

providers notify the JPEC when schedules are loaded into JOPES. Lift

providers must understand the modes and sources of transportation entered in

the TPFDD as "preferred" (as per reference c) and are not final requirements of

the supported commander. Lift providers must coordinate all legs of movement

to provide the supported commander with the most efficient, effective lift

available. The supported commander’s movement control agencies and lift

providers begin to assess the deployment flow in theater, both in light of forces

moving from theater locations to elsewhere in theater and Joint Reception,

Staging, Onward Movement, and Integration of forces from outside the

supported commander’s theater.

D-2

Enclosure D

CJCSM 3122.02B

25 May 2001

3. Supporting Commanders and Service Components of the Supported

Commander. Upon receipt of the alert order or planning order, each

supporting commander, and the Service components of the supported

commander, review force requirements in the appropriate PID and FM for the

COA selected, source force requirements, adjust requirements to reflect actual

unit movement characteristics, and schedule or allocate organic movements for

the first increment of deployment. In addition, supporting commanders and

the Service components of the supported commander establish preparatory

and pre-positioning support and publish OPORDs to support the COA. In an

expanding operation, requirement identification and sourcing are continuous

actions during execution.

a. Review Supported Commander’s LOI. Each supporting commander

receives and reviews the supported commander’s AOR-specific supplemental

instructions to the standard TPFDD LOI. The Service components of the

supported commander source those requirements that can be filled by in-

theater assets (see Appendix C for required information). The supported

commander, generally through his Service components, then adjusts TPFDD

COAs and notifies supporting commanders and lift providers via the operation

newsgroup that the COA TPFDD is ready for sourcing (see Appendix B).

b. Source Force Requirements. Upon notification from the supported

commander that the COA TPFDD is available for sourcing, supporting

commanders begin specifying units to satisfy COA force requirements.

Supporting commanders enter required information (Appendix C) on specified

forces, including origin, unit identification code (UIC), unit name, ready to load

date/available to load date (RLD/ALD), mode and source to preferred POE, and

unit movement characteristics to the fourth level of detail (unless stipulated

otherwise by the supported commander). Level 4 detail enhances strategic lift

allocation and scheduling accuracy and efficiency. Automated interfaces

should be used to the maximum extent possible to provide actual unit

movement characteristics. During this process, the supporting commanders

identify force and sustainment shortfalls and coordinate resolution with the

supported commander. Supporting commanders will continue to coordinate

with the JPEC to update the JOPES database with changing requirements and

sourcing information, including any necessary POE adjustments. This may

require fragmentation (FRAG) and insert coding when large requirements are

split between multiple ports. When small units will be moved via crisis

channel airlift, APOEs and APODs will be changed to reflect channel routing

established by the supported commander and lift provider that establish

channels.

D-3

Enclosure D

CJCSM 3122.02B

25 May 2001

c. Hazardous Cargo. The lift providers require specific information on

hazardous cargo in accordance with reference d as specified by the Code of

Federal Regulations, title 49. The supported commander provides this

information through the use of specific crisis newsgroup. Standard TPFDD LOI

contains a sample message used to declare/coordinate hazardous material

(HAZMAT).

d. Additional Information Required for Lift Requirements. Unit movement

data entered into JOPES at the fourth level of detail and validated by the

supported commander will establish the movement requirement. When

additional information is required, lift providers will so indicate in the

appropriate newsgroup and coordinate with the supported commander for

incorporation into the supplemental instructions.

e. Schedule Organic Moves. Supporting commanders and Service

components of the supported commander will validate to the supported

commander that all sourcing is complete for the first increment of the

deployment flow (first 7 days for air and overland, 30 days for sea), and

schedule lift and allocate requirements for organic movements in JOPES.

4. Lift Providers. Based on the tentative or actual dates of operation contained

in the warning order, alert order, or planning order, lift providers will

coordinate an initial validation with the supported command. Where possible,

this date will be established 72-96 hours before the actual C-day. This lead

time is desired to prepare scheduling information with sufficient time available

to notify deploying units with port departure times.

a. Airlift

(1) Identify Validated Airlift Requirements. A sample validation message

is in Appendix E. Validated requirements are identified by the presence of "V"

in the Schedule Status Flag (SSF) as outlined in Section III of the Standard

TPFDD LOI. USTRANSCOM-validated requirements are identified by the

presence of "T" in the SSF. The supported commander, in coordination with lift

providers, will establish the number of days in advance of the EAD that ULNs

will be validated. Lift providers will advise the supported commander of the

number of days in advance that they can provide mission schedules. The

initial requirements pull will normally cover the first 7 days (LAD C000-C006)

of required moves.

(2) Develop and Enter Air Movement Schedules. Lift providers will enter

initial schedules into the JOPES database as soon as possible, but not later

than 36 hours after the initial validation, or ALD minus 3 days, whichever is

sooner. If the first 7 days or more of requirements are validated, lift providers

D-4

Enclosure D

CJCSM 3122.02B

25 May 2001

will enter the first 4 days of schedules. If fewer than 7 days are validated, lift

providers will schedule 4 days or the number of days validated, whichever is

less. Lift providers will notify the JPEC via the crisis newsgroup when the

initial schedules are entered. When a crisis channel has been established to

aggregate small unit movements, lift providers will provide the schedules in

JOPES.

(3) Adjust Air Movement Schedules. Lift providers are responsible for

maintenance of accurate schedule information in JOPES. Required schedule

data are listed in Appendix E.

(4) Report Preparatory Moves and Lift Pre-positioning. Based on receipt

of a CJCS deployment order or deployment preparation order, lift providers will

determine and position en route infrastructure forces to support air, land, and

sea movements in the COA TPFDD. Lift providers, including AMC/TACC, will

enter those forces in the appropriate PID for supported commander visibility

and validation. Validation of all movement prior to C-Day should follow normal

validation procedures and lead times. Requirements that must move without

normal lead times will be worked on a case-by-case basis.

(5) GO-PAX/Commercial Ticket Program (CTP). Movement under the

CTP is restricted to exercise movement requirements. AMC schedulers will

submit CTP movement recommendations to USTRANSCOM. The supported

commander is the approving authority for CTP movements recommended by

USCINCTRANS. The supported commander identifies ULNs approved for CTP by

recoding mode/source fields from A/K to A/L. Supporting commanders

coordinate with installation transportation offices to move personnel and

equipment between unit installations and commercial ports.

b. Sealift

(1) Identify Validated Sea and Inland Waterway Movement

Requirements. After validation of sea movement requirements by the

supported commander, sealift providers will commence scheduling actions. FM

(Appendix D) will identify validated requirements. Validated requirements are

identified by the presence of "V" in the SSF, as outlined in the standard TPFDD

LOI. USTRANSCOM validated requirements are identified by the presence of

"T" in the SSF. The TPFDD LOI and CINC/AOR specific supplement establish

the number of days in advance of the EAD that ULNs will be validated.

(Initially, the first 30 days of sealift requirements are candidates for validation

if no CINC-specific guidance are provided.) The initial validation increment will

normally cover the first 30 days of movement requirements (EAD of C029 or

less). Lift providers will validate, consolidate, and update seaports for

deploying forces in the JOPES database for the development of initial sea and

D-5

Enclosure D

CJCSM 3122.02B

25 May 2001

inland waterway lift schedules. Lift providers will then notify the JPEC via the

newsgroup of changes to SPOEs and ALDs. Supported and supporting

commanders will in turn notify deploying units.

(2) Allocate Movement Requirements to Sea and Inland Waterway

Carriers. At ports where MTMC operates the port cargo documentation system,

MTMC will allocate movement requirements in JOPES to sealift carriers. The

Navy component of the supported commander is responsible for allocating

requirements to MSC withhold ships. The theater common-user sea or inland

waterway carrier provider is responsible for allocating requirements to

common-user sea or inland waterway carriers. This procedure will begin as

cargo processing and prestow planning commence at the port. In all cases,

movement requirement allocations will be confirmed in the database 48 hours

before sailing.

(3) Schedule Sea and Inland Waterway Movement. Sea and inland

waterway lift providers will provide carrier itineraries and allocations within 36

hours of receipt of validated requirements. If no CINC-specific guidance is

provided in the TPFDD LOI supplement, 4 days of sea and inland waterway

schedules will be maintained in the JOPES database. Initial schedules will be

entered not later than 48 hours before a unit’s port call. Follow-on schedules

for requirements after the first initial increment will be entered 2 weeks before

a vessel’s arrival at the port. For strategic sealift dedicated (withheld) by the

supported commander for specific uses, MSC will identify ships by name, sail

them to SPOEs, and notify users of projected arrivals at SPOEs. Dedicated

sealift schedules will be entered by the supported command, normally through

its Navy component.

(4) Movement Procedures Guidance for Sealift Liner Service. To be

published.

(5) Unit Preparatory Moves. Unit preparatory moves in support of a

crisis will be reflected in the COA TPFDD as pre-C-day or N-day movement or

pre-positioning requirements in accordance with the standard TPFDD LOI and

CINC/AOR-specific supplement. If C-day has been declared and the

preparatory movement requirements are reflected as part of the JOPES

database, lift providers will schedule to meet these requirements as part of the

initial validation process. Procedures addressing how to move forces during

pre-positioning legally and ensuring costs are or will be covered by contingency

funds must be published in advance by the Joint Staff for moving forces

supporting a crisis operation for which no Joint Staff execute order or

deployment order has been issued.

D-6

Enclosure D

CJCSM 3122.02B

25 May 2001

c. Overland (Rail, Truck, Bus) Transportation

(1) Identify Validated Overland Movement Requirements. After

validation of overland movement requirements by the supported commander,

overland lift providers will commence scheduling actions. FM will identify

validated requirements. The initial validation increment will normally cover the

first 7 days of movement requirements. Overland lift providers will validate,

consolidate, and update railheads and marshalling areas for deployment forces

in the JOPES database for the development of initial overland lift schedules.

(2) Allocate Movement Requirements to Overland Carriers. At railheads

where MTMC operates the cargo documentation system, MTMC will allocate

movement requirements in JOPES to rail carriers. The theater common-user

overland transportation provider is responsible for allocating requirements to

common-user overland carriers. In all cases, movement requirement

allocations will be confirmed in the database 48 hours before movement

commences.

(3) Schedule Overland Movement. Overland lift providers will provide

carrier itineraries and allocations within 36 hours of receipt of validated

requirements. Normally, 4 days of overland schedules will be maintained in

the JOPES database. Initial schedules will be entered not later than 48 hours

before a requirement’s departure date (dependent upon movement leg for which

transportation is scheduled). Follow-on schedules for requirements after the

first 7-day increment will be entered 48 hours before a requirement’s departure

date.

5. Services. Upon receipt of the alert order or planning order, the Services

review guidance and coordinate adjustments to sustainment and determine

mobilization requirements accordingly. Additionally, the Services will review

the supported commander’s supplemental instructions to the standard TPFDD

LOI. Services confirm availability of sustainment requirements with the Service

component commander based on the latest CJCS guidance.

D-7

Enclosure D

CJCSM 3122.02B

25 May 2001

APPENDIX A TO ENCLOSURE D

STRATEGIC ORGANIC SCHEDULES AND MANIFEST DATA

The supporting commander enters the following strategic organic movement

schedule and manifest data in JOPES.

INFORMATION

REQUIRED

REQUIREMENT

INFORMATION

1. TPFDD Identification

PID

2. Carrier Identification

Organic Carrier Name

Carrier Type

Carrier Configuration

Providing Organization

3. Schedule

Schedule Departure Date

Schedule Arrival Date

Schedule Departure Time

Schedule Arrival Time

Intermediate Stop Location

Reason for Stop

4. Routing

On-Load Location

Off-Load Location

5. Manifest

Requirement to be Manifested

OPLAN

Type of Manifest

Bulk STONs for Carrier

Oversize STONs for Carrier

Outsize STONs for Carrier

Total STONs on Carrier

Total MTONs on Carrier

Passenger on Carrier

6. Carrier Capacity

Maximum Passengers

Maximum STONs

Appendix A

D-A-1

Enclosure D

CJCSM 3122.02B

25 May 2001

APPENDIX B TO ENCLOSURE D

SAMPLE REQUEST FOR SOURCING NEWSGROUP MESSAGE

FROM: SUPPORTED COMMANDER

TO: SUPPORTING COMMANDER A

SUPPORTING COMMANDER B

SERVICE HEADQUARTERS (OPTIONAL)

INFO: JOINT STAFF/J-4

CLASSIFICATION

SUBJECT: REQUEST FOR SOURCING ( )

REF: A. ( ) CJCS MESSAGE (MESSAGE DTG), ALERT ORDER FOR

(CRISIS NAME).

B. ( ) STANDARD TPFDD LOI AND SUPPORTED COMMANDER’S

SUPPLEMENTAL INSTRUCTIONS TO SAME.

( ) IN ACCORDANCE WITH REFS A AND B, COA(S) AND (PIDS) ARE

PROVIDED TO SUPPORTING COMMANDERS FOR SOURCING AND

SCHEDULING OF STRATEGIC ORGANIC MOVEMENTS.

( )

(OPTIONAL) REQUEST (SERVICE HEADQUARTERS NAMES)

DETERMINE SUSTAINMENT REQUIREMENTS AND NOTIFY J-4 OF

TRANSPORTATION ALLOCATION REQUIREMENTS.

( ) REQUEST SUPPORTING COMMANDERS IDENTIFY FORCE

SHORTFALLS AS SOON AS POSSIBLE.

DECL/CLBY:

;RES:

;DECLON:

DECL/DERFR:

;DECLON:

DRAFTER

RELEASER:

Appendix B

D-B-1

Enclosure D

CJCSM 3122.02B

25 May 2001

APPENDIX C TO ENCLOSURE D

SPECIFIED FORCE DATA

The supported and supporting commanders enter specified force data during

execution planning. Force data consists of the following:

INFORMATION

REQUIRED

REQUIREMENT

INFORMATION

1. Specify Forces to

UIC

Support OPORD Execution

Designated Unit Name

2. Unique Air Force, Army, Navy, Marine Corps and Coast Guard data

requirements:

a. Air Force

Air Force Component of Force

Air Force Major Command of Force

Air Force Force Designator

Air Force Designated Arm

b. Army

Initial Army Gaining Command

Army Unit Designated

Army Branch of Service

Combat Unit Designator

Short Name of Army Force

Army Component of Force

Army Standard Requirements Code

Troop Program Sequence Number

c. Navy

Indicator for Type of Navy Ship

Registration Number of Ship

d. Marine Corps

Initial Gaining Command

Specific Force Grouping

Unit Designator

Combat Unit Designator

e. Coast Guard

Indicator for Type of Coast Guard Cutter

Appendix C

D-C-1

Enclosure D

CJCSM 3122.02B

25 May 2001

INFORMATION

REQUIRED

REQUIREMENT

INFORMATION

3. Deployment Flow of

GEOLOC of Intermediate Location

Forces

Country Code of Intermediate Location

Preferred Mode of Transport to Intermediate

Location

Preferred Source of Trans to Intermediate

Location

Days Delay at Intermediate Location

Type of Delay at Intermediate Location

Where Intermediate Location Occurs

Loading for Del to Intermediate Location

Unloading Limits at Intermediate Location

4. Routing Data

GEOLOC of Origin

GEOLOC of Requested POE

Preferred Mode of Transport to POE

Preferred Source of Transport to POE

5. Time Phasing

Day Unit Ready to Load

Available to Load Day at POE

6. Movement

Actual Unit Data

Characteristics

Appendix C

D-C-2

Enclosure D

CJCSM 3122.02B

25 May 2001

APPENDIX D TO ENCLOSURE D

SAMPLE JOPES SCHEDULE REQUIREMENTS PULL NEWSGROUP MESSAGE

FROM: USTRANSCOM CAT

TO: AMC/MTMC/MSC

INFO: SUPPORTED/SUPPORTING COMMANDERS

CJCS

SERVICES

DEFENSE LOGISTICS AGENCY

CLASSIFICATION

SUBJECT: JOPES SCHEDULE (REQUIREMENTS PULL)

REF:

( ) THE JOPES TPFDD MOVEMENT REQUIREMENTS HAVE BEEN

VALIDATED FOR PULL AND SCHEDULING FOR THE PERIOD: (AIR

MOVEMENT: (EAD) THROUGH (LAD)) OR (SEA MOVEMENT: (EAD)

THROUGH (LAD)).

( ) FOR AMC: REQUEST DEPLOYMENT SCHEDULES FOR THE ABOVE

PERIOD BE DEVELOPED AND ENTERED IN JOPES AT THE EARLIEST

POSSIBLE TIME, BUT NOT LATER THAN __________________________.

FURTHER REQUEST YOU NOTIFY USTRANSCOM CAT WHEN SCHEDULES

FOR THE ABOVE PERIOD HAVE BEEN ENTERED IN JOPES.

( ) FOR MTMC: CONUS STRATEGIC MOVEMENT SCHEDULES MAY BE

ENTERED AT THIS TIME. ADDITIONALLY, REQUEST SPOE CONSOLIDATION

BE REFLECTED IN THE JOPES DATABASE NO LATER THAN

_____________________. NOTIFY MSC IMMEDIATELY UPON COMPLETION OF

PORT CONSOLIDATION.

( ) FOR MSC: REQUEST DEPLOYMENT SCHEDULES FOR THE ABOVE

PERIOD BE DEVELOPED AND ENTERED IN JOPES NO LATER THAN 48

HOURS FOLLOWING NOTIFICATION FROM MTMC OF PORT

CONSOLIDATION.

Appendix D

D-D-1

Enclosure D

CJCSM 3122.02B

25 May 2001

APPENDIX E TO ENCLOSURE D

LIFT PROVIDER SCHEDULE DATA

Lift Provider enters the following schedule data in JOPES during deployment

planning and execution.

INFORMATION

REQUIRED

REQUIREMENT

INFORMATION

1. Carrier Identifi-

Carrier Name

cation

Carrier Type

Carrier Configuration

Carrier Source

Carrier OPLAN

2. Carrier Capability

Maximum Passenger Capacity

Maximum STON Capacity

Maximum MTON Capacity

3. Carrier Itinerary

On-Load GEOLOCs

Off-Load GEOLOCs

Intermediate Stop GEOLOCs

Reason for Stop (Stop Code)

Planned Arrival Date at each GEOLOC

Planned Departure Date at each GEOLOC

Planned Arrival Time at each GEOLOC

Planned Departure Time at each GEOLOC

4. ULN Allocation to

ULNs Planned for each Carrier

Carriers

Appendix E

D-E-1

Enclosure D

CJCSM 3122.02B

25 May 2001

APPENDIX F TO ENCLOSURE D

MSC SCHEDULE DATA

MSC provides the following schedule data in JOPES during execution planning

and execution.

INFORMATION

REQUIRED

REQUIREMENT

INFORMATION

1. Carrier

Carrier Name

Identification

Carrier Type

Carrier Configuration

Carrier Source

Carrier OPLAN

2. Carrier Capability

Maximum Passenger Capacity

Maximum STON Capacity

Maximum MTON Capacity

3. Carrier Itinerary

On-Load GEOLOCs

Off-Load GEOLOCs

Intermediate Stop GEOLOCs

Reason for Stop (Stop Code)

Planned Arrival Date at Each GEOLOC

Planned Departure Date at Each GEOLOC

Planned Arrival Time at Each GEOLOC

Planned Departure Time at Each GEOLOC

Appendix F

D-F-1

Enclosure D

CJCSM 3122.02B

25 May 2001

ENCLOSURE E

EXECUTION

1. General. Phase VI, Execution, begins with the decision to execute an

OPORD, normally transmitted by a CJCS execute order, and continues until

the crisis end state is achieved. The execute order establishes a firm C-day

and L-hour for deployment and details any significant changes to warning

order and alert order guidance. Upon receipt of the CJCS execute order, the

supported commander issues an execute order to the subordinate

commanders. The JPEC then makes any required adjustments to its OPORDs

and updates movement requirements in the TPFDD if required by the latest

guidance. Supporting commanders and Service component commanders will

execute the deployment of the first increment of scheduled movement.

Scheduling and movement of subsequent increments of forces will continue for

the duration of the operation. At execution, visibility must be maintained over

the deploying force. Proper allocation of TPFDD requirements to carriers and

adjudication of planned versus actual lift are necessary to ensure a smooth,

controlled deployment in consonance with the supported commander’s

concept. To be successful in this task requires a coordinated effort by the

entire JPEC.

2. Supported Commander, Adjust Requirements and Deployment. The

supported commander monitors the deployment and adjusts force

requirements based on the employment situation. Adjustments to validated

requirements may have a significant impact on deployment flow and should not

be initiated without proper coordination. Such adjustments to the deployment

must be coordinated with supporting commanders and the supported

commander. Additionally, if the supported commander requires a change to

scheduled carriers, the lift provider must be notified via the operation

newsgroup to coordinate the change. In-the-window changes to validated

requirements which effect scheduled lift require GO/FO authority, documented

in the operation newsgroup, per the standard TPFDD LOI.

a. FDO Adjustments. IF FDO forces have deployed or are scheduled to

deploy, the supported commander must establish procedures to prevent

confusion with non-FDO forces in the same PID. This process may be

accomplished by moving FDO forces to a separate PID for execution using FMs

or other procedures coordinated between the supported commander and the lift

provider. If the parent plan is executed before completing the FDO deployment

within the same TPFDD, the following procedures may be used:

E-1

Enclosure E

CJCSM 3122.02B

25 May 2001

(1) The Chairman of the Joint Chiefs of Staff coordinates with lift

providers and the supported commander to establish C-day and L-hour for the

parent plan and issues an execute order.

(2) Lift providers, in coordination with their components, examine the

ongoing FDO deployment to determine which requirements have already been

considered for scheduling. Lift providers will then inform the supported

commander of any FDO deployment requirements that have not yet been

scheduled.

(3) If a separate FDO PID is used, the supported commander deletes

unscheduled requirements from the FDO PID and adjusts the time phasing for

the same requirements in the parent PID to reflect deployment priorities. The

objective is to complete FDO deployment and transition to execution of the

parent plan.

b. Monitor Arrival of Forces. The supported commander monitors arrival of

forces using the Global Transportation Network (GTN), the Scheduling and

Movement (S&M) or Rapid Query Tool (RQT) applications in JOPES. Utilizing

its movement control agencies and intratheater lift providers, the supported

commander receives, stages, onward moves, and integrates arriving forces from

PODs to destinations.

c. Validate Next Increment. Once the first increment of the deployment is

underway, the supported commander will normally validate subsequent

movement requirements in accordance with the schedule established in the

standard TPFDD LOI and CINC/AOR-specific supplement. In addition, the

supported commander will coordinate with lift providers to expand validation

submission days as the situation dictates. It is critical to lift providers that

this validation be as accurate as possible. If strategic lift is apportioned to

support the operation, all requirements eligible for strategic lift will be used to

build schedules within the supported commander’s apportioned lift.

Requirements added, deleted, or changed after validation to reflect changes in

force allocation, sequence, or the supported commander in accordance with the

standard TPFDD LOI must approve priority. When each increment of the

TPFDD has been validated for scheduling, the supported commander sends a

validation message to lift providers, with information copies to the supported

commander’s Service component commands and supporting commands and

agencies (Appendix A). This validation procedure continues every Monday,

Wednesday, and Friday until deployments are completed. When a 24-hour

increment has been validated for scheduling, the supported commander sends

a validation message to USTRANSCOM (Appendix A).

E-2

Enclosure E

CJCSM 3122.02B

25 May 2001

d. Allocation and Manifesting Procedures. Allocation and manifesting

procedures and responsibilities are described later in this enclosure and in

Enclosure F (In-Transit Visibility). Procedures are outlined in the standard

TPFDD LOI.

e. Noncombatant Evacuation Operations (NEO) and Medical Evacuation

(MEDEVAC). Supported commanders will enter or modify actual movement

requirements for NEO and MEDEVAC cargo and passengers returning from the

theater of operation. The supported commander will coordinate changes to

airlift and sealift ULNs with lift providers and allocate requirements to the

appropriate carriers. Lift providers will adjust stop codes in the scheduling

records to provide for new on-load and off-load locations. The supported

commander will not change timing or scheduled stop locations without

coordinating with lift providers.

3. Supporting Commanders. During execution, supporting commanders and

component commanders verify sourcing performed in execution planning,

ensure nonstrategic schedules are correct, and report movements and changes

required during deployments.

a. Request Validation for Sourced Requirements. Using the operation

newsgroup, supporting commander’s Service component commands request

validation of specified forces to the supported commander’s corresponding

Service component commands. Validation by EAD is for the first 7 days of air

movement (APOE to APOD)and the first 30 days of sea or inland waterway

movement (SPOE to seaport of debarkation (SPOD) for strategic sealift;

dependent upon leg of transportation to which lift has been allocated for other

sources of sea and inland waterway lift), and the first 7 days of overland

movement (point of origin (POO) to POE for MTMC provided rail transportation;

dependent upon the leg of transportation to which overland lift has been

allocated for other sources of overland lift). The validation window may be

expanded according to what is specified in the supported commander’s

standard TPFDD LOI, AOR-specific supplemental instructions. During

execution, forces are validated on Monday, Wednesday, and Friday of each

week (unless prescribed otherwise by the supported commander) in

preparation for incremental scheduling by lift providers.

b. Enter Organic Movement Schedules and Manifests. Supporting

commanders (or their Service component commands) enter organic movement

schedules and manifests in S&M and ensure the strategic leg of organic schedules

are in accordance with the execute order.

E-3

Enclosure E

CJCSM 3122.02B

25 May 2001

c. Reporting Actual Movements. Supporting commanders report actual organic

movements using the JOPES S&M application subsystem and the newsgroup or

other agreed upon method. Data to be entered are listed in Appendix B.

d. Continue to Allocate Requirements to Carriers. Lift providers will continue

to notify the supported command via the newsgroup when allocations are entered.

All movement requirements arriving at any route location that are not resident in

JOPES must be entered into the JOPES database by the providing organization.

The activity operating the embarkation facility will identify any such movement

requirements to the supporting commander for resolution via the newsgroup.

e. Reporting Changes to Validated Requirements. After validated

requirements have been scheduled and deployment activities have begun, the

supporting commanders will monitor the flow to ensure unit requirements are

deploying as planned. Request for changes to validated requirements will be

identified to the supported commander by the most expeditious means and

documented in the newsgroup. If approved by the supported commander,

changes will be accomplished by the supporting commander component

commander or supporting commander in accordance with supported

commander direction as indicated in the standard TPFDD LOI. When the

supporting commander or supported commander’s Service component requests

revalidation of requirements to which coordinated changes have been made,

those changes should be noted in the revalidation request message. The

supported commander will include the changes made to revalidated

requirements in the revalidation newsgroup message to the lift provider(s).

f. Reporting Insufficient Lift to Transport a Validated Requirement. If units

are not able to fully deploy on their designated lift, the supporting commander

will identify the lift shortfall and corresponding ULNs to lift providers through

the supported commander for resolution. If the lift is not sufficient because of

unplanned requirements arriving at the POE, the supporting commander must

investigate the reasons for excess requirements. If the excess requirement was

not previously validated, the requirement must be returned to origin. If the

excess requirement was validated, the supporting command will notify the

supported command that insufficient lift was scheduled against validated

requirements. The supported command will resolve the issue with the lift

provider. Supporting commands are responsible for ensuring that TPFDD ULN

data matches load plan data for their units.

g. Adjustments to Schedules. Supporting commands and nonstrategic lift

providers will enter changes to organic and nonstrategic lift schedules and

requirement allocations as they occur. TCCs will enter changes to strategic

schedules and requirement allocations as they occur. JOPES schedules will

reflect the latest itinerary, departure, and arrival times. This information is

E-4

Enclosure E

CJCSM 3122.02B

25 May 2001

required to keep the supported commander apprised of the total deployment

flow for force reception, staging, onward movement, and integration. When the

supporting commander or supported commander’s Service component requests

revalidation of requirements to which coordinated changes have been made,

those changes should be noted in the revalidation request message. The

supported command will include the changes made to revalidated requirements

in the revalidation newsgroup message to the lift provider(s).

h. Sourcing and Validating the Next Increment. Once movement has

begun, supporting commanders, agencies, and the supported commander’s

Service components will source and request validation of specified forces before

incremental scheduling. The sourcing may be completed for the entire

deployment flow, but validation requests will take place as prescribed by the

standard TPFDD LOI. Detailed validation procedures are covered by the

standard TPFDD LOI and expanded in AOR-specific supplemental instructions.

This recurring process continues until all sourced units are deployed.

4. Lift Providers. In conjunction with the supported commander, lift providers

will manage the deployment, direct required adjustments to schedules and

modes and sources of transport, and resolve airlift, sealift, and overland

transportation shortfalls. If required, lift providers will coordinate any

adjustments to deployment or other major changes to deployment parameters

with the supported commander. Lift providers will also provide the impact of

significant changes in the deployment and isolate deployment problems

affecting force closure. Lift providers will maintain accurate carrier schedules

in JOPES. The data to be reported for strategic lift carrier arrivals and

departures is reflected in Appendix E. The carrier itinerary and schedule will

be updated as changes occur to reflect the latest and most accurate mission

status. Carrier remarks will be used to maintain a history of schedule changes

with rationale. For USTRANSCOM-controlled ports, USTRANSCOM’s TCCs are

responsible for reporting actual cargo and passenger manifest information in

JOPES, including crisis channel manifests for unit moves.

a. Report Changes to Planned Deployment. In dynamic situations, changes to

deployment plans will be required regardless of the adverse impact on the overall

deployment flow. Maintenance of an accurate database that reflects actual

movements is essential to the utility of JOPES in deployment execution.

Accuracy of aircraft movement and manifest in JOPES is particularly critical.

Subsequent paragraphs describe procedures for reporting air carrier movements.

(1) Report Arrivals and Departures in JOPES. Airlift providers report

arrivals and departures via S&M. AMC will also report arrivals and departures

via GTN. If for any reason AMC is unable to report via an automated system,

carrier arrivals and departures will be reported by AMC using the on-line entry

E-5

Enclosure E

CJCSM 3122.02B

25 May 2001

functions of the S&M subsystem. If for any reason airlift providers are unable

to report via an automated system, they will request the supported commander

allow exception reporting via the newsgroup and provide an estimated time for

resumption of positive reporting. Changes that affect the scheduled or

previously updated arrival or departure time by greater than 2 hours will be

reported in JOPES as soon as possible. In cases where it is known that the

scheduled or previously updated arrival or departure of a carrier will exceed the

2-hour window, but a new firm arrival or departure cannot be established,

estimated time and remarks will be entered in JOPES to indicate that the time

entered is estimated. This estimate will be changed to actual once a mission

that qualifies for exception reporting departs APOE or arrives APOD or as soon

as firm arrival or departure is established. The manifesting agency, which is

the port operator, will ensure actual manifest information is available in JOPES

no later than 2 hours after aircraft departure from APOE.

(2) Reporting Diversion of Air Carriers and Changes to Schedules. Airlift

providers will notify the supported commander via the operation newsgroup

and enter all diversion or change information in JOPES if a carrier with

allocated requirements is diverted from a scheduled location in JOPES. JOPES

schedules will reflect the latest itinerary departure and arrival times. Carrier

remarks will be used to maintain a history of schedule changes with rationale.

Airlift providers will coordinate diversions or changes with the supported

commander and other appropriate members of the JPEC to determine the

impact to the deployment flow and any additional actions required. Required

data entry is at Appendix F.

(3) Adjusting Deployment Flow and Scheduling the Next Increment.

Adjustments or changes to the deployment flow requested by the supported

commander will be accommodated where possible. However, changes to

movement flow already scheduled may involve extensive manual intervention,

as will changes to requirements that have already been validated for

scheduling. Unless constrained by time-sensitive crisis events, the supported

commander will validate airlift requirements 7 days prior to EAD. Airlift

providers will ensure that 4 days of air schedules are maintained in JOPES.

During execution, airlift providers will monitor the operation newsgroup to

determine when subsequent increments of the TPFDD have been validated and

are ready for scheduling. Within 12 hours of receipt of each validated

increment, airlift providers will enter scheduling data into JOPES for the next

day of requirements to be scheduled. Allocations should consist of the ULN

and the allocated passengers and tonnage. All database changes affecting

validated requirements included in the 7-day window or that have airlift

scheduled against them will be made in accordance with the standard TPFDD

LOI (Enclosure H).

E-6

Enclosure E

CJCSM 3122.02B

25 May 2001

b. Overland Transportation Providers. During execution, overland

transportation providers schedule and allocate lift. MTMC schedules and

allocates CONUS-origin POE transportation to support POE-POD air and sea

flows. MTMC CONUS schedules, if entered in JOPES, will be adjusted by

MTMC as required to maintain visibility of movement requirements when

arriving at PODs. MTMC will notify the JPEC via the designated newsgroup if

delays of major units will preclude meeting carrier schedules. All overland lift

providers will enter schedules and allocations in JOPES.

c. Adjusting CONUS Origin/POE Schedules. CONUS schedules, if entered

in JOPES, will be adjusted by MTMC as required to maintain visibility of

movement requirements when arriving at PODs. MTMC will notify the JPEC

via the newsgroup if delays of major units will preclude meeting carrier

schedules.

d. Sealift and Inland Waterway Lift Providers. A recurring cycle of

incremental sealift scheduling is initiated by the execute order. Sea and inland

waterway lift providers consolidate SPOEs based on validated requirements

and coordinate lift at least 30 days prior to the EAD. For strategic lift, MTMC

consolidates SPOEs and notifies MSC to coordinate strategic sealift. Lift

providers continually update-scheduling information in JOPES, including

carrier arrivals and departures, changes to schedules, and carrier diversions as

they occur. This cycle continues until completion of the operation. For POE-

POD schedules, lift providers will identify to the supported commander specific

exceptions to capability to provide required schedules and manifests.

Additionally, lift providers will allocate requirements to sealift carriers to enable

tracking of the scheduled sealift. For strategic lift, MTMC will allocate

requirements to sealift carriers in JOPES. MSC will enter strategic sealift

schedules during execution planning for subsequent refinement as MTMC

identifies detailed requirements for movement.

(1) Allocating Requirements for Sealift and Inland Waterway Carriers.

Lift providers will allocate sea and inland waterway movement requirements

(mode code "S") for carriers. For strategic lift (M/S codes "S/E" and "S/W,"

MTMC will allocate sealift movement requirements at seaports where MTMC

operates the port cargo documentation system.

(2) Continuing Sealift and Inland Waterway Deployment and Reporting

Significant Discrepancies. Maintenance of an accurate database that reflects

actual sea and inland waterway movements is essential to the utility of JOPES

in deployment execution. Accuracy of carrier movements and requirements

allocation data is particularly critical. Lift providers will reconcile lift

allocations with actual lifted cargo and update JOPES with manifest

information reflecting the actual cargo lifted. Using the newsgroup, they will:

E-7

Enclosure E

CJCSM 3122.02B

25 May 2001

(a) Identify movement requirements received via the Defense

Transportation System and/or processed at the port that are not resident in

JOPES.

(b) Report when validated movement requirements received at the

port exceed the capacity of scheduled carriers.

portions of lifted movement requirements for the above scheduled carriers to

the supported commander for resolution (MTMC will report to USTRANSCOM

who will then report to the supported commander with resolution).

(3) Lift providers will coordinate with the supported commander and

resolve any sea or inland waterway lift shortfalls.

(4) Sea and Inland Waterway Lift Manifesting. The port operator is

responsible for manifesting sea and inland waterway lift. Manifest information

will be provided by the lift provider in JOPES no later than 24 hours after ship

departure from port or 48 hours before the ship arrives in port for each leg of

movement, whichever is first.

(5) Reporting Changes to Planned Deployment. In dynamic situations,

changes to deployment plans will be required regardless of technical

requirements and adverse impact. Maintenance of an accurate database that

reflects actual movements is essential to the utility of JOPES in deployment

execution. Accuracy of movement data and allocations to carriers is

particularly critical. Subsequent paragraphs describe procedures for reporting

sealift carrier movements.

(a) Lift providers will report actual departures and arrivals of strategic

common-user sealift carriers in JOPES.

(b) Lift providers will notify the supported command, via the

newsgroup, coordinate with the appropriate supporting command, and enter

information in JOPES when a diversion or change is required to a published

schedule. JOPES schedules will reflect the latest itinerary and departure and

arrival times. Carrier remarks will be used to maintain a history of schedule

changes with rationale.

(6) Adjusting Deployment Flow and Scheduling Next Increment.

Adjustments or changes to the deployment flow requested by the supported

commander will be accommodated where possible. Sea and inland waterway

lift is coordinated during execution planning for requirements during the first

E-8

Enclosure E

CJCSM 3122.02B

25 May 2001

30 days. During execution, lift providers following seaport consolidation will

pull increments of requirements beyond the first 30 days. Lift providers will

enter and maintain all scheduling information in the JOPES database for

carriers scheduled to meet validated requirements throughout the operation.

e. Services. After receiving the CJCS execute order, the Services direct

their major commanders to execute the supporting OPORDs, direct

mobilization activities, and direct their personnel and logistic centers to

support the deployment. Services continue to coordinate with personnel

centers and logistic agencies to identify and confirm sustainment requisitions.

E-9

Enclosure E

Military reference books and manuals (2009-2023, Volume 5) - page 16