UNITED STATES MARINE CORPS COMMAND ELEMENT

II MARINE EXPEDITIONARY FORCE PSC BOX 20080

CAMP LEJEUNE, NC 28542-0080

IIMEFO 3120.5D G-3/FDP&E

II MARINE EXPEDITIONARY FORCE ORDER 3120.5D 4 DEC 2015

From: To:

Subj:

Ref:

Encl:

Commanding General Distribution List

FORCE DEPLOYMENT PLANNING AND EXECUTION (FDP&E) STANDING OPERATING PROCEDURES (SOP) (SHORT TITLE: FDP&E SOP)

(a) MCO 3000.lBB, Marine Corps Force Deployment Planning and Execution (FPD&E) Manual

(b) CJCSM 3122.02C, Joint Operation Planning and Execution System (JOPES) Volume III (Crisis Action Time-Phased Force and Deployment Data Development and Deployment Execution)

(c) MCWP 5-1, Marine Corps Planning Process (d) Joint Pub 1-02, Department of Defense (DoD)

Dictionary of Military and Associated Terms (e) MCO 4470.lA, MAGTF Deployment,

Distribution Policy (MDDP) (f) CMC Unit Deployment Policy for Individual Weapons

(201959Z Sep 2010) (g) II MEFO 3100.6, Intentions Messages for

Deployments for Training (15 Jun 2015) (h) II MEFO 3000.15, II Marine Expeditionary Force Unit

Deployment Program Standard Operating Procedures ( II MEF UDP SOP)

(i) II MEF NIPR AMHS message 100022Z May 13, General Officer/Commanding Officer Endorsement Letter and G-3/S-3 Endorsement Letter Requirement for Changes to Time-Phased Force and Deployment Data

(j) CJCSM 3150.16E, Joint Operation Planning and Execution System Reporting (JOPESREP)

(k) MCWP 4-11.3, Transportation Operations

(1) FDP&E SOP

1. Situation. II Marine Expeditionary Force (MEF) Marine Air­Ground Task Forces (MAGTFs), units and individual augments are required to accomplish several tasks during planning and execution of deployments and redeployments. Crisis action and short-notice deployments limit the time available to accomplish

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors; For Official Use Only 13 Jun 2014. Other requests for this document will be referred to Commanding General II Marine Expeditionary Force.

IIMEFO 3120.5D

a and

The

these tasks and large-scale deployments are difficult for deploying MAGTF to accomplish alone. Centralized control coordination of FDP&E procedures simplifies that process. Time-Phased Force and Deployment Data (TPFDD) is a product of planning that provides visibility of the deployment and redeployment of forces as well as forces in place. Additionally, it is a product utilized for the purchase of air transportation, ground cargo transportation and buses. II MEF forces are typically required to deploy outside of their local area for unit training and strategic engagements. Such events require Commanding General, II MEF (CG, II MEF) to utilize significant funds in order to deploy and redeploy units. In order to maximize the use of transportation assets while minimizing excessive expenditure, CG, II MEF directs the verification of a TPFDD for Continental United States (CONUS) deployments for training that require the purchase of commercial airlift and/or commercial ground transportation. The end state is earlier and more accurately planned deployments that shall result in a cost savings.

2. Cancellation. IIMEFO P3120.5C.

3. Mission. To establish policy and procedures for the planning and execution of the FDP&E process within II MEF in support of the Marine Corps FDP&E process. As described in this order, the procedures guide II MEF staff, Major Subordinate Elements (MSEs), and Major Subordinate Commands (MSCs) through the FDP&E process.

4. Execution. In accordance with the references, utilize enclosure (1) for all FDP&E efforts and comply with this Order.

5. Administration and Logistics. Submit recommended changes concerning the contents of this manual via the chain of command to II MEF Assistant Chief of Staff G-3 (AC/S G-3).

6. Command and Signal. Omitted.

fL.A~ G. S. JOHNST N Chief of Sta f'

DISTRIBUTION: C

2

RECORD OF CHANGES

Log completed change action as indicated.

Change Date of Date Signature of Person Number Change Entered Incorporating Change

i Enclosure(l)

CHAPTER

1

2

3

4

5

6

ANNEX

A

B

C

D

E

F

G

H

I

J

CONTENTS

ORGANIZATION, DUTIES, AND FUNCTION

FORCE DEPLOYMENT PLANNING

FORCE DEPLOYMENT EXECUTION

TPFDD DEVELOPMENT

MOVEMENT CONTROL

FDP&E BUSINESS RULES (II MEF SPECIFIC)

DEPLOYMENT PLANNING FOCUS AREAS

FORCE DEPLOYMENT PLANNING MILESTONES FOR CONUS DEPLOYMENTS FOR TRAINING (DFTs)

DEPLOYMENT PLANNING CHECKLIST

EXAMPLE OF REQUEST TO DEPLOY OVER A HOLIDAY PERIOD

EXAMPLE OF REQUEST TO DEPLOY WITHOUT INDIVIDUAL WEAPONS

EXAMPLE OF THE CALLING MESSAGE FOR A SPECIAL MEETING OF THE DEPLOYMENT OPERATIONS TEAM (DOT)

EXAMPLE OF THE MESSAGE TO PUBLISH THE RESULTS OF THE SPECIAL MEETING OF THE DOT

EXAMPLE OF CONCEPT OF OPERATIONS (CONOPS)

EXAMPLE ENDORSEMENT LETTER

EXAMPLE OF A GROUPS OPERATIONAL PASSENGER SYSTEM (GOPAX) REQUEST MESSAGE

ii Enclosure (1)

CHAPTER 1

ORGANIZATION, DUTIES, AND FUNCTION

PAGE

GENERAL . . . . . . . . . . . . . . . . . . . . 1-1

ORGANIZATION ................. 1-2

DEPLOYMENT OPERATIONS TEAM. 1-4

DUTIES

INTEGRATION IN THE PLANNING PROCESS

iii

1-4

1-7

Enclosure (1)

CHAPTER 1

ORGANIZATION, DUTIES, AND FUNCTIONING

1. GENERAL. The FDP&E process is complex and must be understood and practiced consistently throughout II MEF. In order to maintain a high level of proficiency in planning for the deployment and redeployment of II MEF units, adhere to the guidance set forth in this order for each deployment. Whether Marines, Sailors, and civilian personnel are deploying as individual augments or as units, all abide by the same procedures and rules to efficiently deploy and redeploy II MEF forces.

a. Whether the deployment of forces supports Chairman of the Joint Chiefs of Staff (CJCS) directives, Global Force Management (GFM), adaptive planning (AP), crisis action planning, or exercises, the efficient deployment of forces from home station to a final destination is critical to any operation. The FDP&E procedures described in this order reflect the Joint Operation Planning and Execution System (JOPES) process, which includes utilizing the TPFDD as a source document as outlined in references (a) and (b). Follow the process in order to effectively and efficiently deploy forces.

b. Current Combatant Commander (CCDR) and Marine Corps requirements that mandate a FDP&E process include the following:

(1) Contingency Plans

(2) Contingency Operations (Major theater war or crisis response)

(3) Theater Security Cooperation (TSC) Events

(4) CJCS Exercises

(5) Service Requirements (Unit Deployment Program (UDP))

(6) Marine Expeditionary Unit (MEU) deployment

(7) Alert Forces: Global Response Force (GRF), Special MAGTF Crisis Response Africa (SPMAGTF-CRAF), Marine Corps Response Force - South (MCRF-S), and CONUS-Based Alert Force (CBAF) .

(8) Unit Deployments for Training (DFTs) and other training events (refer to Chapter 6). A TPFDD shall be required

1-1 Enclosure (1)

for a DFT that requires the purchase of corrunercial airlift and/or commercial ground transportation. The benefit is more focused deployment planning which results in the optimal use of funds.

2. ORGANIZATION. The success of the FDP&E process requires the active participation of several entities. Figures 1-1 and 1-2 provides a graphic portrayal of how these entities are organized.

II MEF FDP&E ORGANIZATION

Commanding General II Marine Expeditionary Force

I I I Commanding Officer Commanding General Commanding General

II MEF Headquarters Group 2D Marine Division 2D Marine Division

Commanding General Commanding General

20 Marine Expeditionary 2D Marine Air Wing

Brigade

Commanding Officer 220 Marine Expeditionary Unit

Commanding Officer 22D Marine Expeditionary Unit

Commanding Officer 220 Marine Expeditionary Unit

Commanding Officer SPMAGTF

(as required)

Figure 1-1

1-2 Enclosure (1)

I I

I

Deployment Operations Team

II MEF

Force Deployment Strategic Mobility Officer* Officer*

Plans Chief I Air Mobility Officer

FOP&E Chief I Air Mobility Chief

G-3 Future Surface Mobility Operations Officer

G-3 Current Surface Mobility Operations Chief

G-7 I MEF Movement Control Center Director*

G-1 Operations* G-4 Operations

MSEs/ MSCs

FDP&E/Plans/ Officers and Chiefs*

S-1/G-1

Embark/ Mobility

Officers and Chiefs*

* Denotes Core Members

CG II MEF

I

G-3 G-4

G-3 G-4

Future Operations

Operations

' ' Force Strategic

' Deployment Mobility

Officer Officer

Figure 1-2

1-3 Enclosure (1)

3. DEPLOYMENT OPERATIONS TEAM (DOT). The nucleus of the DOT is composed of the Force Deployment Officer (FDO), the Strategic Mobility Officer (SMO), and the MAGTF Movement Control Center (MMCC) Director. The DOT holds daily meetings to coordinate II

MEF force deployment efforts. The DOT's functions and responsibilities should not be confused with those of an Operational Planning Team (OPT). Where the OPT focuses on employment planning and execution, the DOT focuses singularly on deployment planning and execution (and redeployment when required). The DOT's primary functions and responsibilities for each deployment and redeployment are:

a. Conducting deployment problem framing.

b. Developing the deployment concept.

c. Preparing and disseminating deployment planning guidance.

d. Assisting in the preparation of Prepare to Deploy Orders (PTDOs), Execution Orders (EXORDs}, and Deployment Orders (DEPORDs}, and providing other deployment related direction and/or assistance as required.

e. Reviewing and verifying the TPFDD.

f. Reviewing allocations, load plans and manifests.

g. Effecting coordination between all supported/supporting organizations.

h. Maintaining a record of all directives, official correspondence, Automated Message Handling System (AMHS} messages (classified and unclassified}, newsgroups, Transportation Movement Requests (TMR}, Transportation Capacity Planning Tool (TCPT) requests, run rosters and actions pertaining to the deployment

4. DUTIES. Following are the specific duties of the key participants in the FDP&E process.

a. AC/S G-1

(1) Core member of the DOT.

(2) Provide clarity on the requirement for the deployment of individual augments in support of Joint Manning Documents (JMDs) and service requirements.

1-4 Enclosure (1)

(3) Ensure administrative message traffic is processed and routed to the appropriate levels that support operational deployment of personnel.

b. AC/S G-3

(1) Responsible for the discipline of the II MEF Force Deployment Process.

(2) Coordinates with counterparts at higher, adjacent, and subordinate headquarters, as required.

(3) Approves all General Officer Endorsements (GOEs).

c. G-3 Future Operations Officer (FOPSO)

(1) Supervises the Force Deployment Officer (FDO) and the DOT operations.

(2) Coordinates with counterparts at subordinate and higher headquarters as required.

d. G-3 Force Deployment Officer (FDO)

(1) Core member of the DOT.

(2) Chairs the daily DOT meeting (during which the DOT maintains scrutiny of all staff functional areas in support of deployments).

(3) Reports to the II MEF Future Operations Officer (FOPSO).

(4) As the G-3 direct representative for FDP&E, provides oversight of all aspects of deployment operations.

(5) Reviews and provides JOPES guidance for all TPFDD Letters of Instruction (TPFDD LOis), Force Requirement Numbers (FRN), available newsgroups, Deployment Orders (DEPORDs), Prepare to Deploy Orders (PTDOs), Execute Orders (EXORDs) and Exercise Tasking messages pertaining to II MEF units.

(6) Reviews TPFDD and deployment orders for compliance with established policies and regulations.

(7) Advises on Marine Corps and Joint policy, procedures, and processes.

1-5 Enclosure (1)

(8) G-3, FDP&E representative in Operation Plan (OPLAN) reviews.

(9) Provides oversight of OPLAN force deployment and deployment support activities.

(10) Coordinates with subordinate, higher, and adjacent Headquarters (HQ) as necessary, to include bases and stations.

e. AC/S G-7

(1) Core member of the DOT.

(2) Provide clarity on requirements for Service-directed training events.

f. AC/S G-4 Operations Officer. execution of logistics in support of

Provides coordination and FDP&E.

g. Strategic Mobility Officer (SMO)

(1) Core member of the DOT.

(2) Attends DOT meetings and addresses strategic transportation issues and schedules.

(3) Maintains a strategic mobility schedule of events.

(4) Reviews all TPFDDs prior to verification/ certification to higher headquarters.

(5) Publishes deployment and redeployment transportation planning guidance for strategic airlift and sealift movements.

(6) Develops and coordinates strategic transportation related portions of OPLANs and orders.

(7) Maintains operational relationships with Marine Corps Installations East for the FDP&E process.

h. MEF Movement Control Center (MMCC) Director

(1) Core member of the DOT.

(2) Attends DOT meetings and addresses ground transportation and movement control issues and schedules.

1-6 Enclosure (1)

(3) Validates ground transportation support requirements and maintains daily run roster and ground transportation order (GTO).

(4) Publishes deployment and redeployment ground transportation planning guidance in support of strategic airlift, sea and other unit movements.

(5) Develops and coordinates ground transportation related portions of OPLANs and orders.

(6) Conducts Movement Coordination Meetings (MCM) and Port Opening Meetings (POM) as required to support deployment and redeployment operations in order to establish support requirements and task elements of II MEF to provide required support.

i. II MEF MSE/MSC Plans Officers, Force Deployment Officers, Mobility Officers, Plans Chief, and FDP&E Chiefs

(1) Core members of the DOT.

(2) Provide input to force deployment operations on behalf of their commander and subordinate units.

(3) Develop, institute and enforce MSC FDP&E SOPs.

5. INTEGRATION IN THE PLANNING PROCESS

a. Integration of the FDP&E Process with GFM, AP and Marine Corps Planning Process (MCPP).

(1) Closely integrated FDP&E with GFM, AP and MCPP per reference (c). GFM integrates the three force management processes of assignment, apportionment, and allocation. AP is the Joint process to develop, maintain, assess and implement campaign plans, contingency plans and orders, supported by information technology (IT) tools. MCPP provides the foundation by which the Marine Corps shall conduct planning and operations within a complex and ever-changing environment. Do not treat FDP&E as an afterthought or an administrative function; it is a plans and operations function, which bridges the gap between planning and the conduct of operations.

(2) Achieving success within the FDP&E process requires a disciplined adherence to established procedures, the coordination of numerous staff functions, and the use of several activities. It is a certainty that the way we execute this process in peacetime is the way we shall execute it under the

1-7 Enclosure (1)

demanding conditions of war. With that axiom in mind, II MEF shall conduct FDP&E operations in peacetime in the same manner that we plan to conduct them in war.

b. The FDP&E Process. The FDP&E process occurs in two phases: force deployment planning and force deployment execution.

(1) Force Deployment Planning (FDP). Deployment planning often begins when a CCDR receives an initial notification or a warning order from CJCS to prepare for an operation that will require the employment of military forces. FDP activities include: receiving and analyzing the mission, developing the concept of operations, determining requirements, phasing force flow, and sourcing requirements. A typical overview of the process for II MEF is as follows:

(a) The supported CCDRs USMC Service Component conduct situation assessment and problem framing with the supported CCDR.

(b) When CG, II MEF is tasked to support a CCDR, Commander Marine Forces Command (COMMARFORCOM) shall direct CG, II MEF to report to the supported commander for planning of operations.

(c) The supported CCDR conducts his own detailed mission analysis, determines his concept of employment, and determines the requirements needed to accomplish the mission.

(d) When CG, II MEF is tasked to deploy forces in support of a supported CCDR, the AC/S G-3 supervises the planning and execution of the deployment. Under the direction of the AC/S G-3, II MEF staff sections plan and execute the deployment.

(e) Submit to COMMARFORCOM for global sourcing all identified shortfalls tasked to II MEF that it cannot source.

(f) If no organization can source the requirement, then it becomes a shortfall to the CCDR. In that case, the supported CCDR must conduct a risk assessment to determine if he can accomplish his mission without the requirement. If he cannot, he must revise his concept of operations to accomplish the mission with the forces available.

(g) Passed the sourced and tailored requirements are back up the chain, each echelon of the chain of command shall consolidate and verify the requirements are accurate and meet

1-8 Enclosure (1)

the supported CCDRs requirements. As necessary may be further tailor requirements to meet changing mission or lift requirements.

(h) The medium that details the prioritized, time­phased flow of sourced force and sustainment requirements for a particular operation or exercise is the TPFDD. The TPFDD is the supported CCDRs detailed concept of deployment.

(i) When sourcing and tailoring is complete, the TPFDD is verified by CG, II MEF to COMMARFORCOM and ultimately validated by the supported CCDR. For II MEF DFT's, the verification process ends at COMMARFORCOM (see Chapter 6).

(2) Force Deployment Execution (FDE). Force deployment execution is six closely related and integrated activities: tailoring and refining requirements, verifying movement requirements, marshaling and moving to the Port of Embarkation (POE), manifesting and moving to the Port of Debarkation (POD), Joint Reception, Staging, Onward movement, and Integration (JRSOI) to assembly areas or final destination.

c. Redeployment Planning and Execution

(1) Inherent in the deployment of forces and their sustainment is the requirement to return them to home station upon mission completion. Redeployment planning and execution requires the same focused preparation and intensity as deployment and employment operations. The redeployment process is merely deployment in a different direction.

(2) Redeployment planning and execution are rarely a CG, II MEF responsibility. When deployed in support of a CCDRs requirement, supported CCDR shall redeploy the unit and CG, II MEF shall provide reception. Only during cases where the deployment is not in support of a CCDR would II MEF be responsible for redeployment. Units may not have the same level of redeployment support that was available at its home station, which may complicate their redeployment. The DOT plays a key role in planning the reception phase of redeployment coordination.

1-9 Enclosure (1)

CHAPTER 2

FORCE DEPLOYMENT PLANNING

BACKGROUND.

OBJECTIVE OF DEPLOYMENT PLANNING

INITIATION OF DEPLOYMENT PLANNING.

CONDUCT OF DEPLOYMENT PLANNING

DEPLOYMENT PROBLEM FRAMING ..

CONCEPT OF DEPLOYMENT DEVELOPMENT.

REQUIREMENTS DEVELOPMENT AND REPORTING

SUSTAINMENT REQUIREMENTS DEVELOPMENT AND REPORTING . . . . . . ....

REQUIREMENT SOURCING AND TAILORING

2-1

PAGE

2-2

2-2

2-2

2-2

2-3

2-4

2-6

2-8

2-9

Enclosure (1)

CHAPTER 2

FORCE DEPLOYMENT PLANNING

1. BACKGROUND

a. Conduct force deployment planning in much the same manner as the development of an OPLAN. The degree and detail of deployment planning is proportional to the scope of the deployment and the time available for planning.

b. MCPP, as described in reference (f), provides a coherent decision-making methodology that can be adapted to deployment planning.

2. OBJECTIVE OF DEPLOYMENT PLANNING. The objective of deployment planning is to provide personnel, equipment, and sustainment when and where required by the supported commander as expressed in his concept of operations. Therefore, successful deployment planning depends on complete and detailed employment planning. Employment planning considerations that directly affect deployment planning include identification of force requirements, commander's intent for the deployment, time phasing of personnel, equipment, and material to support the mission and closure of forces to execute decisive operations.

3. INITIATION OF DEPLOYMENT PLANNING. In most instances force deployment planning actions originate with senior commanders and flow to subordinate commanders through operational channels. Exceptions to this normal sequencing may fall into one of two categories: logistics intensive operations that may originate and flow in logistics channels and exercises deployments that may originate with CG, II MEF MSC's/MSE's. When non-standard force deployment planning is initiated; it must be conducted under the cognizance of the G-3.

4. CONDUCT OF DEPLOYMENT PLANNING

a. Within II MEF, the AC/S G-3 is responsible for planning exercises, crisis action contingencies, and other operational deployments. Regardless of which staff section may have had the lead for planning a deployment, the AC/S G-3 is responsible to the commander for the execution of all deployments.

b. As mentioned in Chapter 1, the DOT is a standing working group which coordinates force deployment planning and execution. Representatives of the sourcing/deploying commander who shall deploy the force shall also participate in the FDP&E process.

2-2 Enclosure (1)

c. Occasionally, II MEF MSCs/MSEs become aware of Outside of the Continental United States (OCONUS) training opportunities. When those opportunities present themselves, the concerned commander must work his request for an overseas deployment order in his deployment planning through the AC/S G-3. He shall not pursue the request either on his own or, through another II MEF staff principle that has staff cognizance over his activities; e.g., the AC/S G-2 and Intelligence (Intel) Battalion relationships. Regarding OCONUS deployments, everyone involved with deployment planning must understand that Title 10 of the U.S. Code requires the Secretary of Defense to approve the transfer of forces assigned to one CCDR to another CCDR. This transfer includes deployments for exercises as well as operations. This requirement is Federal Law.

5. DEPLOYMENT PROBLEM FRAMING. Thorough problem framing is the critical first step in any successfully planned and executed deployment. In many cases, much of the essential information of a particular deployment will come from either COMMARFORCOM as a result of his initial assessment in mission analysis or from the operational commander who will employ the force. In much the same way COMMARFORCOM advises Headquarters Marine Corps (HQMC) during the commander's initial assessment of an operational mission or an exercise requirement, CG, II MEF (normally through coordination with the COMMARFORCOM staff) assists COMMARFORCOM with the following actions:

a. Identification and sizing of appropriate USMC forces for the deployment based on mission requirements.

b. Providing information on unit availability and recommendations on the sourcing of the units and/or MAGTF commander if one is required.

c. Recommending adjustment to or clarification of the mission.

d. Providing advice on logistics direction and support requirements.

e. command

Assisting with the definition or clarification of relationships.

f. In rapidly developing situations information may be communicated either in person, via telephone or via email. When command personnel pass information by these means confirm, all orders, directions, and coordinating instructions in AMHS message traffic and newsgroups. Then, in coordination with the designated operational commander and the OPT, the DOT completes

2-3 Enclosure (1)

its deployment problem framing by considering the following planning requirements and activities:

(1) Identifying movement/lift constraints, limitations, and assumptions.

(2) Determining potential personnel and equipment shortfalls.

(3) Developing a thorough understanding of the operational commander's concept of employment.

6. CONCEPT OF DEPLOYMENT DEVELOPMENT. Following the completion of the deployment problem framing, the DOT/OPT, in conjunction with the operational commander, develops the concept of deployment that answers the following:

a. Determine command relationships during the deployment.

b. Determine the organization for deployment. The organization for deployment must support the concept of employment, i.e., how the employing commander shall initially array his forces for operation. This means that the task organization for the deployment must reflect the way the force shall be time-phased into the area of operations. The employing commander determines time-phasing.

c. Determine time-phasing and prioritization of deploying forces. Based on the employing commander priorities and needs, the DOT, in conjunction with the OPT, must determine how to phase the forces into theater. In the case of a Joint Force Deployment, base time phasing on the employing commander concept of employment and service component requirements. Initial logistic support and security requirements require careful consideration to ensure the safety and well-being of the forces arriving in theater. In addition, the capability to time-phase the force into the area of operations in the most operationally desirable manner may be constrained by force and sustainment availability, lift availability, and port and base throughput capacity. In the event adequate strategic lift is not available to move forces en masse, planners must also determine what lift priority to assign forces needed in the Area of Operations (AOR) at the same time. In order to deconflict competing demands for lift, the supported commander may apportion lift to his component commander. The apportionment message should specify airlift priority, quantity of cargo and passengers per day, mode (air, sea, or land) and utilized ports. A similar message may be required for II MEF MSCs.

2-4 Enclosure (1)

d. When not directed, identify the means or method of deployment. Potential transportation means to consider are:

(1) Amphibious shipping

(2) Military Sealift Command (MSC) provided shipping (''Black Bottom Shipping''). MSC is the United States Transportation Command (USTRANSCOM) component commander for strategic and commercial sealift. CG, II MEF obtains MSC shipping to support CJCS directed operations and exercises by registering the lift requirement in JOPES. Shipping often falls in the category of Withhold Shipping. Withhold Shipping is a category of MSC provided shipping that is either apportioned to a CCDR for planning or allocated to a CCDR for employment which the CCDR authorizes as withheld from general use and for a specific purpose.

(3) Air Mobility Command (AMC) provided airlift. AMC is the USTRANSCOM component commander for strategic and commercially chartered airlift. Strategic lift of any type is that transportation used to deploy forces overseas either from CONUS, or between CCDRs AORs. CG, II MEF obtains AMC provided airlift for CJCS-directed exercises and operations by registering the lift requirement in JOPES.

(4) Commercial Ticket Program (CTP). The CTP is only used for CJCS exercises (not to be confused with the purchase of commercial tickets through DTS). CTP permits the purchase of individual commercial airline tickets in circumstances where strategic or commercial air charter is not an efficient or economical means of transportation. CTP tickets are initially unit funded, however the supported CCDR reimburses the funds provided the TPFDD verifies the movement. Only the supported CCDR may authorize CTP.

(5) Special Assignment Airlift Mission (SAAM). SAAM is an airlift requirement for special pickup or delivery by AMC at points other than those supported by channel routes, and/or that requires special consideration because of the number of passengers involved, the weight or size of the cargo, the urgency or sensitivity of movement, or other operational factors. II MEF primarily uses SAAMs to support en route Support to Transient Aircraft (ESTA) and deployment of UDP forces since these service directed rotations are not validated by the supported CCDR through the TPFDD. A SAAM is submitted to II MEF G-4/SMO through the web-based SAAM Request System (SRS), and further coordinated with AMC once validated by the service component (MARFORCOM). Under no circumstances should the data submitted in the TPFDD and the data submitted in the SAAM

2-5 Enclosure (1)

differ. If, due to a change in requirements, there are changes that must be made to the TPFDD or the SAAM, a coordinated G-3/G-4 message must be released by the MSC with detailed justification for the required changes. In order to save 10 percent on the SAAM (which typically falls between 50,000 and 100,000 dollars, it must be submitted no later than (NLT) the Available-to-Load date minus 30 days (ALD-30). This requires a significant planning effort and the operational chain (S-3/G-3) must approve the request so that it coincides with submission in the TPFDD.

(6) Commercial chartered aircraft commonly referred to as Group Operational Passenger System (GOPAX). II MEF deploys forces for CONUS DFT's by chartering entire aircraft by this primary method. GOPAX is a web-based system that allows for registering an airlift requirement with USTRANSCOM to move passengers within the CONUS. USTRANSCOM submits the GOPAX requirement to commercial industry for bids and provides the most cost effective bid that meets the deployment requirement. Upon acceptance of a bid, the U.S. Government has entered into a binding contract with private industry. Do not change requirements without coordination through contracting agents at TRANSCOM, as there are minimum Personnel Awaiting Transportation (PAX) requirements.

(7) Organic lift or transportation. Organic lift consists of aircraft/vehicles organic to the unit, not the command (i.e., VMGR has KC-130's in their inventory (unit) whereas a MEU or SPMAGTF does not have KC-130's in their inventory (command)).

(8) Regardless of method of deployment, use JOPES for all operations and exercises that require the purchase of airlift. JOPES provides secure In-Transit Visibility (ITV) for both common and non-common user transportation carriers, and provides greater visibility of II MEF force movement. In addition, JOPES ensures effective management of planning operations across the spectrum of mobilization, deployment, employment, sustainment, and redeployment.

(9) Delineated in Chapter 6 are the procedures for DFT and CONUS events.

7. REQUIREMENTS DEVELOPMENT AND REPORTING. Develop force and sustainment requirements following concept development. This action, which leads to the construction of the TPFDD, can only occur upon completion of the activities described Chapter 2, paragraph 6 of this document, Concept of Deployment Development.

2-6 Enclosure (1)

a. Force requirements are those capabilities the operational commander needs to accomplish the mission, defined by when, where, and how he needs them. A valid force requirement is as follows, per reference (d):

(1) Unit type (the capability required, for example, a reinforced infantry battalion).

(2) Earliest Arrival Date (EAD), the earliest time the force can be accepted in theater based on the Required Delivery Date (RDD), port throughput limitations, and distance to the final destination.

(3) Latest Arrival Date (LAD), the latest time it can be accepted in theater based on the RDD, port throughput limitations, distance to the final destination.

(4) The mode (air, sea, land) and source (who provides the transportation) (M/S) for the strategic and final "legn of the movement (movement from the POE to POD as well as the POD to Destination).

(5) Required Delivery Date (RDD), when the capability must be at the destination.

(6) Commander's Required Date (CRD), the date when a unit, a resupply shipment, or replacement personnel are to be complete with Joint Reception Staging Onward movement (JRSO) and ready to be integrated into the operation. Note that in deliberate 'planning, CRD may be used to indicate the desired readiness of the unit to be available for employment.

(8) The Port of Embarkation (POE) is the sea or air entry point in theater from where the force begins the strategic leg of its movement.

(8) The Port of Debarkation (POD) is the sea or air departure point in theater from where the force completes the strategic leg of its movement.

(9) Destination is where the capability needs to be at the commencement of operations.

b. The supported commander and the supporting commander (force provider) are jointly responsible to determine the force requirements, both as described above, and in relation to the organization for deployment, that supports the initial task organization and concept for employment. Specifically, the supported commander identifies:

2-7 Enclosure (1)

(1) The unit type, expressed as a Unit Type Code (UTC).

(2) Routing data from POE to Destination, to include the location of POD(s) and destination(s), and M/S to each of the locations.

(3) Associated time phasing of specified forces in theater, to include the EAD, LAD, RDD and CRD.

(4) The Force Requirement Number (FRN) to use when sourcing the TPFDD. A FRN is a field used to represent a requirement and is issued by the supported commander.

c. As a force provider, CG, II MEF helps determine (in coordination with COMMARFORCOM and HQMC):

(1) Routing data in CONUS, to include the Origin, POE(s), and M/S between the two locations.

(2) Time-phasing of forces from the origin to the POE(s).

d. Once the force requirement is determined, the sourcing commander communicates the force requirements to the MSCs and separate battalions for sourcing using JOPES.

8. SUSTAINMENT REQUIREMENTS DEVELOPMENT AND REPORTING

a. Sustainment has three elements. The first element is the prescribed loads, those supplies in which units are directed to deploy, such as food and water. These are reflected in the Unit Line Numbers (ULNs) representing each unit. The second element is accompanying supplies, the material that moves with and supports the deploying force for up to 60 days. The last element is resupply, normally for requirements beyond 60 days.

b. The deploying force commander, assisted by the II MEF Command Element (CE), calculates his sustainment requirements based on guidance from higher headquarters, the sourced Joint Forces Requirements Generator II (JFRG II) data and his concept for logistics support. The commander identifies the routing and phasing of sustainment by class and type of supply and enters the requirements as separate sustainment records in the TPFDD.

c. CG, II MEF sources that portion of the sustainment that can be satisfied from force held stocks. The unsourced requirements (shortfalls) are passed to COMMARFORCOM and then

2-8 Enclosure (1)

forwarded to the Commander, Marine Corps Logistic Command and the Commander, Marine Corps Systems Comrnand, for sourcing.

9. REQUIREMENT SOURCING AND TAILORING

a. The terms "sourcing" and "tailoring" describe TPFDD development actions, yet because they are not clearly defined in current Joint and Service publications, the terms are often misused and misunderstood.

(1) Reference (d) provides a Joint definition of "sourcing." From a CCDRs perspective, a force requirement that is developed is "sourced" when the providing organization places in the TPFDD the Unit Identification Code (UIC) and name of the unit filling the requirement.

(2) The TPFDD is subsequently "tailored" to reflect how the unit shall actually be composed for deployment, to include mobile loading of cargo, adjusting personnel numbers to reflect on-hand strength, and identifying advance and rear parties and/or other elements of the unit that deploy at different times or along different routes.

b. Force Requirement Sourcing

(1) Upon receipt of the operational commander's force requirements from CG, II MEF and the MSC commanders, determine which units shall support the mission and forward the force requirement for sourcing along with amplifying planning information determined by the MSC,

(2) In strict compliance with Joint and Service procedures, the battalion/squadron-level units use MAGTF Deployment Support System II {MOSS II) to build the Unit Density List (UDL) for its portion of the deploying force. The data is associated to the various ULNs that describe how each portion of the unit uniquely deploys (e.g., different routes or timelines). Units take into account any pre-positioned equipment that its forces may fall in on as it sources the complete requirement. The UDL is tailored to the precise requirement and configured as it will be embarked (palletized, containerized, or mobile loaded). If required, unit RBE data is captured separately to reflect any specific disposition decisions.

(3) The sourced MOSS II data is passed up the operational chain of command and imported into a JFRG II database at the regiment or group level. Groups, regiments, and separate battalions shall add movement detail to reflect accurately the movement of each ULN from origin to destination.

2-9 Enclosure (1)

JFRG II data is passed to the MSCs to be loaded in the assigned TPFDD.

(4) Shortfall identification and reporting. In the case of units that cannot source force requirements, the operational commander shall identify the requirements as un-sourced and pass notification up the chain for resolution. Requirements that II MEF cannot source shall pass to COMMARFORCOM for resolution.

2-10 Enclosure (1)

CHAPTER 3

FORCE DEPLOYMENT EXECUTION

PAGE

GENERAL. . . . . . . . . . . . . . . . . . . . 3-2

TPFDD VALIDATION, ALLOCATION, AND MANIFESTING PROCESS AND PROCEDURES 3-2

SCHEDULING 3-4

ALLOCATION 3-5

MANIFESTING. 3-5

3-1 Enclosure (1)

CHAPTER 3

FORCE DEPLOYMENT EXECUTION

1. GENERAL. This chapter describes those activities that occur during the execution of a deployment. They include JOPES actions (validation, scheduling, allocating and manifesting) and the movement control/development support activities occurring during the scheduling of transportation, marshalling of forces at their origin, and their movement to and departure from the POE(s).

2. TPFDD VALIDATION, ALLOCATION, AND MANIFESTING PROCESS AND PROCEDURES

a. Though it occurs during the final stages of planning, verification is the beginning of deployment execution. It is the procedure used to confirm to the supported commander that TPFDD records accurately reflect the current status, attributes, and availability of the specified forces, and that the data is free of errors. When a command verifies a TPFDD, it is communicating to the next higher headquarters how the deploying unit commander intends to deploy his force, to include dates for departure and arrival, ports to pass through, and transportation means for each leg of movement en route to the final destination.

b. Verification, certification and validation are often used inter-changeably. This causes confusion for planners as they have vastly different meanings. It is essential that everyone involved in the FDP&E process clearly understand what validation means because there is more to it than II MEF verifying that the information in the TPFDD is correct, accurate, and free of fatal errors.

(1) Verification is the deploying commander's (II MEF) submission to the employing commander that he is deploying his force into the area of operations or exercise area in the sequence specified and with the capabilities required by the employing commander. By verifying the TPFDD, the commander is verifying that he shall be ready to depart the origin on the Ready-to-Load Date (RLD), and the POE on the ALD.

(2) Certification is the sourcing commander's (II MEF) submission to the supported commander of a sourced requirement in a TPFDD. This certification indicates only a unit has been assigned for sourcing of a requirement, but is not currently scheduled to deploy in support of that requirement. Examples of

3-2 Enclosure (1)

forces that are typically certified are on-call and PTDO forces: the GRF, CBAF and MCRF-S.

(3) Validation is the Supported CCDRs acknowledgement that a requirement in the TPFDD meets his requirement for employment, both in capability and by time-phasing. Only a supported CCDR has the capability or authority to validate.

c. The supported commander determines the validation windows in coordination with USTRANSCOM.

d. USTRANSCOM schedules lift for a deploying force only after the supported CCDR validates the TPFDD. Because it takes time to schedule aircraft and ships (due to limited assets, maintenance requirements, crew concerns, and time needed to determine routes and contract commercial lift), timelines have been established for validating requirements in each of the supported commander supplements per reference (b). The timeline is the validation window, and it is expressed as a range of C­Days leading up to a deploying force's EAD. Validation is required prior to the validation window (also termed "outside"). When validation occurs "inside" the window (meaning within the specified range of C-days), USTRANSCOM may have difficulty or may be unable to schedule lift to meet the requirement. This could cause a requirement to miss the CCDRs ROD; therefore, in­the-window verifications require accompanying justification from the deploying commander identifying the reason for the late request. At a point determined by the Supported CCDR, this may require a General Officer Endorsement (GOE). This requirement differs by CCDR and guidance shall be provided accordingly.

e. CJCS and service directed exercises compete for transportation assets at a lower priority than operational requirements, have budget constraints, and depend heavily on contracted commercial assets, exercise validation windows are significantly longer than operational deployment windows. Airlift validation windows are 60 days prior to the first day of the month in which the exercise starts. Sealift validations are normally 100 days prior to the first day of the month in which the exercise starts. Actual validation windows or dates are published in the supported CCDRs exercise directive.

f. The primary medium for TPFDD coordination is JOPES newsgroups. Newsgroups are official message traffic, resident on the SIPRnet, which the entire Joint Planning and Execution Community (JPEC) monitors.

g. Re-verification guidelines.

3-3 Enclosure (1)

(1) Ideally, units only verify the TPFDD once. However, errors in previously verified data, caused by inadequate planning, data entry errors, or changes directed by higher headquarters (HHQ), may cause commanders to re-verify the TPFDD when a more accurate definition of the force requirement is available or do to the discovery of data errors. Since changes to verified data can disrupt lift scheduling, the only changes allowed are those required to support the operation or exercise.

(2) Commanders desiring to adjust the TPFDD must obtain approval beforehand. To do so, the commander submits a request up the chain of command via JOPES newsgroups. The request shall state which ULNs require adjustment, the requested changes, the reason for the changes, the impact the changes have on scheduling lift and the risk to mission accomplishment should the changes not be effected.

(3) Changes significant enough to affect movement schedules can have serious consequences and are only approved when there is a clear, critical operational need. Such changes are defined as those that invalidate movement schedules (e.g., shifting deployment dates or ports, or passenger/cargo changes that increase or decrease the planned lift, commercial contracts, charter aircraft, or diplomatic clearances). In such cases, a General Officer must endorse re-verification messages. In the case of units commanded by a Colonel or below, the Commanding Officer's endorsement is required.

3. SCHEDULING. Scheduling is the assignment of specific aircraft and ships (referred to as carriers) to transport a requirement based on the movement data and passenger/cargo detail in a TPFDD. USTRANSCOM schedules lift for deploying forces only after the supported CCDR validates the TPFDD. USTRANSCOM attempts to satisfy the deploying unit's EAD at the POD as much as possible.

a. USTRANSCOM enters the lift schedule in JOPES. The schedule shows the types of carriers, their planned arrival and departure at all stops enroute to the POD, and an initial assignment (allocation) of ULNs to each carrier. USTRANSCOM should place the lift schedule in Scheduling and Movement (S&M) at least seven days prior to deployment.

b. If the lift schedule does not meet the deploying commander's needs, whether the problem involves the dates, ports, or the carrier types, commanders can request changes through II MEF by placing the request in the appropriate newsgroup.

3-4 Enclosure (1)

c. If the deploying unit does not meet the minimums for strategic lift (strat mins), they must either request aggregation with other ULN's departing in the same window, or open the EAD/LAD window to allow TRANSCOM to seek aggregation for the unit. This task is imperative because it may allow the unit to deploy via strategic lift rather than commercial lift, this enabling significant cost savings to CG, II MEF.

d. For non-common user lift (lift not provided by USTRANSCOM in support of (ISO) a combatant commander), carriers shall be created, within the Scheduling and Movement (S&M) sub­system, by the lowest element with access to JOPES (i.e., Regt/Group/MEU).

4. ALLOCATION. Allocation, as stated above, is the assignment of ULNs to specific carriers.

a. For USTRANSCOM provided lift, USTRANSCOM shall allocate ULNs to carriers. Units shall ensure their entire lift requirement is accurately reflected and satisfied. Any lift shortfalls shall be reported utilizing JOPES newsgroups.

b. For non-common user lift, the unit responsible for creating the carriers shall also allocate them.

5. MANIFESTING. Manifesting is the entry in JOPES of the actual PAX and cargo short tons (STONS), by ULN, deploying on each carrier. Manifesting is the responsibility of the assigned liaison element. This element is assigned via AMHS message and is responsible to coordinate between the deploying unit and the Arrival/Departure Airfield Control Group (A/DACG), the port of embarkation/debarkation and the mobility force.

a. For aircraft, per reference (b), manifesting shall be accomplished no later than two hours after aircraft departure from the APOE. Due to personnel, Information Technology (IT) and security constraints, the following guidance is provided for manifesting II MEF forces: If manifesting within 2 hours of departure is not feasible due to manpower, security or information technology system availability at the APOE, aircraft shall be manifested in JOPES by 1200 the workday following departure. In the event of a holiday, or an ''act of God'' that prevents the normal conduct of business, the aircraft shall be manifested in JOPES by 1200 on the next full business day.

b. For sealift, per reference (b) manifesting shall be accomplished no later than 24 hours after departure from the Sea Port Of Embarkation (SPOE).

3-5 Enclosure (1)

c. On occasion, units arrive at the POE with numbers of pax and cargo different from the numbers in the TPFDD. These errors force delays in the deployment as load plans are adjusted, or in severe situations, cancellation of lift. Manifesting is the process that gives commanders, both supported and supporting, visibility into what each carrier is transporting. This provides a rapid means of communicating changes in lift requirements, and a means of recording the execution of the deployment plan.

3-6 Enclosure (1)

GENERAL ..... .

TPFDD DEVELOPMENT.

CHAPTER 4

TPFDD DEVELOPMENT

4-1

PAGE

4-2

4-2

Enclosure (1)

CHAPTER 4

TPFDD DEVELOPMENT

1. GENERAL. This chapter provides additional guidance regarding TPFDD development, TPFDD reports, and' JOPES newsgroups. The purpose of this chapter is to provide clarity into basic procedures. This chapter also assists subordinate commands by providing detailed procedures for TPFDD development.

2. TPFDD DEVELOPMENT. A TPFDD is a collection of records in a complex database that constitutes the detailed deployment plan of an operational plan or order.

a. Plan Identification {PID). The PID is the name of the TPFDD and it is a five-character code. The CCDRs determine the PIDs for their respective JOPES TPFDDs.

b. Force Module {FM). A FM is a means of grouping like requirements in a TPFDD. This allows the selection of records that are electronically grouped together to permit their manipulation as a single entity. CCDRs may direct force providers to establish specific FMs in the planning guidance for the OPLAN, operations or exercise.

c. The following describes selected fields of the TPFDD and shall assist with data input:

(1) Unit Line Number {ULN)

(a) This field uniquely identifies each requirement sourced in a TPFDD. ULN's are built from FRN's. The FRN (built by the supported commander such as Marine Forces Central Command (MARCENT)) identifies the requirement while the ULN {built by the supporting commander - II MEF) identifies the unit sourcing that requirement.

{b) Specific guidelines for developing a TPFDD's ULN structure are contained in the current version of reference {j), the Joint TPFDD LOI, and are expanded in detail in the supported combatant commander's TPFDD LOI. The following are some basic guidelines:

1. Fragmentation (FRAG) and Insert codes. The FRAG and Insert codes are used when a single unit is split during the deployment; i.e, it is not moving from the origin to the destination together for all legs of the deployment. Portions of the unit are either: moving via separate modes of

4-2 Enclosure (1)

transportation (except for a split shipment); moving along different routes, to include beginning or ending the deployment at different locations; or moving at different times. Fill the sixth and seventh ULN positions when splitting a ULN using both FRAG and Insert procedures. Any character or number is valid except the letters ''I'' and ''O'' (these letters can be easily confused with the numbers ''l'' and ''0'').

2. Parent ULNs, which are administrative ULNs without any unit data, are sometimes used to establish hierarchical relationships.

3. ULNs shall be structured hierarchically, based on the deploying forces' task organization for initial operations in the AOR. Submit requests for exceptions to this policy from CG, II MEF (AC/S G-3).

(2) Providing Organization Code (PROVORG). This data field identifies the CCDR, Service, or Department of Defense (DoD) agency that is providing the forces to be deployed. CG, II MEF forces shall use the PROVORG "M", which represents HQMC assigned forces.

(3) Unit Type Code (UTC). The UTC is a five-character code that identifies standard types of forces, and is used to relay the type of force required for a given operation, contingency or exercise. It is also used when a supported CCDR wants to identify to a supporting CCDR the additional forces needed for an OPLAN. When a UTC is inserted in a TPFDD, it automatically populates data that describes the standard unit from a built-in file called the Type Unit Characteristics (TUCHA) file. All valid UTCs are in the TUCHA file. As such

TUCHA generated forces are considered standard. When the TUCHA data is subsequently tailored, or the actual unit deploying is properly sourced, the data is then described as nonstandard.

(4) Force Description. This contains a free-form description of the identified force requirement. When a standard UTC is entered, the system automatically pulls up the associated description from Type-Unit Characteristics (TUCHA). When sourcing a TPFDD, II MEF units shall use the field to describe accurately the provided force exactly as described in Annex A of the OPORD or the Base Force List. Do not utilize actual unit names or other descriptors.

(5) Unit Identification Code (UIC) The UIC is a six­character code that identifies the actual unit filling the force requirement. The UIC for a detachment of a Defense Readiness Reporting System - Marine Corps (DRRS-MC) reportable unit shall

4-3 Enclosure (1)

be the same as the parent unit. The unit manually enters the UIC during sourcing.

(6) Unit Name. This is the actual name of the unit filling the force requirement. For example: Co A, 8th Engr Spt Bn, 2d MLG. The unit name is automatically loaded when the UIC is populated. Though the user can modify this after sourcing, CG, II MEF policy is to leave the system-generated name in place.

(7) Force Indicator Code (FIC). The FIC system is generated and identifies how the ULN was generated. A FIC of ''0'' indicates the force is exactly as contained in the TUCHA. Since units do not deploy as represented by their Table of Organization and Equipment (T/O&E), such data is unacceptable in a TPFDD submitted to support a deployment. Units shall submit data with a FIC of ''9'', reflecting properly sourced data. (Note: JOPES uses a "Standard Indicator Code" (SIC), similar to a FIC. SIC is an alpha-character where FIC, used by JFRG, is a numeric character.)

(8) Authorized Personnel (PERS). By definition, this numeric value identifies the personnel strength that satisfies the specific force requirement after arrival in the objective area. This definition may lead one to believe this field identifies the number of personnel the deploying unit plans to deploy, but it does not (the PAX field reflects this number).

(9) Personnel Awaiting Transportation (PAX). The PAX field indicates the number of personnel requiring transportation. It shall reflect the actual number deploying as part of the force identified in a ULN.

(10) Mode and Source Codes (M/S). These single character codes indicate the desired means of transportation for all legs of a deployment.

(11) Geolocation Code (GEOLOC)

(a) When specifying unit origins, ports of embarkation and debarkation, and destinations in the TPFDD, planners use a four-character code called a GEOLOC. All GEOLOCs are contained in a table accessible in JFRG and JOPES.

(b) Planners must ensure the correct code was selected to match the M/S requirement. For example, ensure a surface M/S was not selected for an aerial POE/POD.

(12) Date Format

4-4 Enclosure (1)

(a) TPFDDs contain date values that reflect a unit's deployment sequence. The values are based on the day the deployment for the operation officially begins (C-day). C-day is entered in the TPFDD as COOO. C plus five days (C+5) is entered as C005. The letter N is used for days prior to C-day. For example, C-5 is entered as N005.

(b) A TPFDD may or may not have a C-day established. A TPFDD without a C-day date established is used for OPLANs and contingency plans (CONPLANs). For any TPFDD in execution, there has been a date specified as C-day so that transportation can be arranged.

(13) Cargo detail

(a) Cargo data in a TPFDD has multiple levels of detail. There are five levels defined for JOPES TPFDDs (see reference (a), and JFRG II has a sixth. The level of detail determines how well the data describes the cargo. For example, if a TPFDD only has level one detail, the cargo data would simply be the total weight and square feet measurements. Specific items would not be listed, nor would the data indicate if the cargo is bulk, oversize or outsize.

(b) Reference (b) directs CG, II MEF to provide TPFDDs with level four detail. Level four is defined as "detail expressed as number of passengers and individual dimensional data (expressed in length, width, and height in inches) of cargo by equipment type by ULN." Also required is weight in terms of short tons or volume in terms of metric tons. Due to frequent misinterpretation of this definition, subordinate commands shall ensure cargo data provided to CG, II MEF is represented as follows:

1. Cargo detail shall reflect Principal End Items (PEis), ammunition, hazardous materials, and assets that indicate unit capabilities or generate sustainment (e.g., weapons, radios, generators, crypto devices). Other cargo (e.g., compasses, whistles) shall be deleted. Since these items take up space and add weight, the boxes or pallets they are loaded on shall be left in the cargo detail. Cargo descriptions shall be written as listed in the look-up file in MOSS II/JFRG II (Table of Authorized Materiel Control Number (TAMCN) followed by the item name). The cargo description for pallets and containers shall also identify the contents when possible (e.g., 463L pal tents; and C4433 quadcon). This task is most efficient when completed at the regiment/group level. Ensure the weights and dimensions of vehicles, trailers, containers and 463L

4-5 Enclosure (1)

pallets reflect the items stored on or in them by using the proper association functions in MOSS II.

2. Do not identify baggage pallets in the TPFDD. USTRANSCOM uses standard planning factors to calculate the quantity of baggage pallets. However, belly loadable cargo to accompany troops (commonly referred to as "belly TAT) is required to be reflected as cargo in the TPFDD.

3. Cargo Category Codes (CCCs). Cargo category codes help describe cargo by type; whether it is a container, rolling stock, ammunition or hazardous material (HAZMAT). Lift providers need accurate CCCs to determine the type of carrier required and any special handling equipment.

(c) A properly sourced TPFDD must originate with an accurate, well-maintained battalion or squadron MOSS II UDL. The sourced JFRG II plan is then forwarded up the chain of command for eventual import into JOPES to identify the actual requirement to USTRANSCOM. It is imperative that battalion and squadron UDLs are maintained in the most accurate state possible and that the data is verified during every step and at every level of within the chain of command, beginning at the battalion/squadron.

(14) Movement detail. This includes the fields required for movement planning; location fields indicating all waypoints en route to the theater, date fields associated with the locations, and M/S fields for each leg of movement (the latter are discussed in subparagraph 10 above).

(a) Location fields. These are the specific GEOLOCs discussed earlier. They are:

1. Origin. Identifies the location from which the unit begins deployment. II MEF forces normally begin their deployment from their home station.

2. POE. Identifies the Sea Port of Embarkation (SPOE) or Aerial Port of Embarkation (APOE) where the unit begins the strategic leg of the deployment. II MEF forces normally use Marine Corps Air Station (MCAS) Cherry Point, NC and MCAS Beaufort, SC as APOEs and the Ports of Morehead City and Wilmington, NC as the SPOEs.

3. POD. Identifies the Seaport of Debarkation (SPOD) or Aerial Port of Debarkation (APOD) where the unit ends the strategic leg of deployment.

4-6 Enclosure (1)

4. Destination. Identifies the location where the unit ends its movement and begins to prepare for operations. For combat and combat support forces, this is usually a tactical assembly area.

5. Intermediate location (ILOC). ILOCs represent any stop between the Origin and the Destination. Activated Selected Marine Corps Reserve (SMCR) units have an ILOC at their training locations for deployment and their demobilization stations for redeployment.

(b) Date fields

1. Ready to Load Date (RLD). The RLD is the day, relative to C-day, the unit is ready to depart from the origin.

2. Available to Load Date (ALD). The ALD is the day the unit is ready to depart from the POE. In most situations, the ALD shall be one day later than the RLD. Note the large window for reserve units, upon activation they move from their origin, but are not ready to move until their predeployment training is complete.

3. Earliest Arrival Date (EAD). Per the Joint TPFDD LOI, this is the preferred arrival date at the POD. For airlift, this date is normally one day after the ALD. For sealift, the EAD should account for two days to load the ship at the SPOE, the appropriate number of transit days, and two days for offload at the SPOD.

4. Latest Arrival Date (LAD). This is the latest date that the unit can be accepted at the POD. The Joint TPFDD LOI sets standard planning factors for the spread between the EAD and LAD, commonly referred to as the EAD/LAD window. For airlift, the window is EAD plus two days (e.g., C001-C003). For sealift, the window is EAD plus six days. For overland deployments, the window is EAD plus four days.

5. Required Delivery Date (RDD). This is the date the supported commander requires the unit be at its destination and capable of commencing operations. It must be equal to or later than the LAD. The number of days between the LAD and RDD is dependent on the transit time from the POD to the final destination. If the POD and destination are the same, the RDD must equal the LAD.

d. Reports. TPFDD reports can be either standard or ad hoc. Ad Hoc reports that pull only selected data can be

4-7 Enclosure (1)

requested from the MAGTF Planning Specialists; however, standard reports are usually sufficient. The three standard reports are:

(1) FllD. This report identifies the origin, POD, and destination, the EAD and LAD, and the PAX and short tons of each ULN.

(2) FllE. This report identifies complete movement detail, to include all locations, dates, and M/S codes for each leg of the deployment. The report displays the cargo either as short tons or as square feet broken down by bulk, oversize or outsize. This is a useful report when checking for deployment timeline and location errors and for determining airlift requirements.

(3) FllW. The most detailed and lengthy report, one is essential for verifying accuracy of cargo detail. provides complete visibility of each item's weight and dimensions, and summarizes data by CCC and ULN. The G-4 the MAGTF Planning Specialists closely check this report to verification.

this It

SMO and prior

4-8 Enclosure (1)

CHAPTER 5

MOVEMENT CONTROL

CONCEPT OF DEPLOYMENT SUPPORT .....

DEPLOYMENT SUPPORT ORGANIZATIONS.

DEPLOYMENT MODES.

MOVEMENT CONTROL.

MOVEMENT PRINCIPLES ...

MOVEMENT CONTROL DURING DEPLOYMENTS ...

MOVEMENT CONTROL ORGANIZATIONS ....

5-1

PAGE

5-2

5-2

5-3

5-3

5-4

5-4

5-4

Enclosure (1)

CHAPTER 5

MOVEMENT CONTROL

1. CONCEPT OF DEPLOYMENT SUPPORT

a. The MAGTF/unit commander providing forces to a supported combatant commander is responsible for planning and executing the deployment of his forces. The commanders of individual units and detached of the MAGTF/unit are responsible for preparing their units for deployment and deploying their units as directed by the MAGTF/unit commander.

b. Deployment support is provided to deploying commanders to facilitate the efficient and effective movement of forces from their Origin to POE and on to POD and their final destination. Deployment supports assists the deploying commander's requirement to marshal, stage, embark, deploy, debark, and successfully employ his command.

c. Deployment support planning encompasses deliberate planning in support of the OPLANs, crisis action driven deployments for which no specific contingency plans exist, other operation deployments, and finally deployments associated with directed exercises.

d. Deployment execution can encompass several phases, including preparation for movement; movement from unit areas to marshaling areas; movement from marshaling areas to staging areas at A/SPOE; movement from A/SPOE to A/SPOD; and movement from A/SPOD to tactical assembly areas in the objective area.

2. DEPLOYMENT SUPPORT ORGANIZATION

a. MAGTFs and individual units can deploy from either permanent installations or from forward-deployed sites from either directed exercises or combat operations. Designated transportation operating organizations are established to assist the MEF Commander with his requirement to control and coordinate the marshaling, embarkation, and movement of those forces.

b. External commands involve in providing transportation and other deployment support for MAGTF/unit deployments may include:

(1) The supported Combatant Commander.

(2) The supporting Combatant Commander.

5-2 Enclosure (1)

(3) The Fleet Commander.

(4) The U.S. Transportation Command and its Transportation Component Commands, i.e., Air Mobility Command (AMC), Military Sealift Command (MSC), and Surface Deployment and Distribution Command (SDDC).

3. DEPLOYMENT MODES

a. Transportation modes vary depending on the size of the MAGTF/unit deploying, the purpose and duration of the deployment, and anticipated employment. Deployments of the entire MEF or an individual Marine Expeditionary Brigade (MEB) generally require the use of all modes of transportation. II MEF shall rely on military and commercial trucks, buses, and rail from origins and POEs; amphibious and commercial ships from SPOEs to SPODs or destinations; and AMC or commercial charter airlift for personnel, supplies, and equipment from APOEs to APODs.

b. Funding and operational objectives determine whether Marine Corps owned or commercially procured transportation assets may be used for movement from origins and POEs. For many directed exercises and contingency operations, transportation funding is provided via reimbursable accounts from external commands or agencies. In these cases, using Marine Corps transportation assets could be fiscally counter-productive since their use would create a direct and unnecessary expense for II MEF.

4. MOVEMENT CONTROL

a. Reference (k) defines movement control as the planning, routing, scheduling, and control of personnel, supplies, and equipment movements over lines of communication. This is accomplished to support the deployment of forces and includes maintaining in-transit visibility of personnel and equipment to assist commanders and operational staffs in force tracking.

b. The deploying MAGTF or unit commander must plan, organize, and direct the deployment of his organization. During planning, he establishes the priority and sequence for the deployment of personnel, equipment, and supplies to meet operational objectives of the supported combatant commander, Joint Task Force (JTF) Commander, or other supported commander's deployment and employment plan. The deploying commander prepares specific ship and/or aircraft load plans that accurately reflect the verified TPFDD, and reconciles deployment

5-3 Enclosure (1)

priorities with ship and aircraft schedules. The deploying commander must be prepared to determine/revise ship and aircraft load priorities and configurations throughout his deployment. He also identifies locations and times that subordinate elements must be in place at POEs, PODs, and final destinations or Tactical Assembly Areas (TAAs) to meet scheduled lift.

5. MOVEMENT PRINCIPLES

a. Centralized Control. CG, II MEF centralizes control of movements at appropriate levels.

b. Regulation. II MEF Commander's movement control organizations assist him with his requirement to regulate and coordinate movements to prevent congestion and conflicting movements over lines of communication. Proper management of transportation assets and the transportation network is critical.

c. Flexibility. The mission of the transportation system is to provide an uninterrupted flow of traffic from the place of origin to the place of employment. It must also be able to adjust to changing requirements. CG, II MEF must use limited transportation and deployment capabilities effectively and efficiently. Subordinate commanders must be prepared to divert or reroute traffic to maintain the continuous movement of personnel, supplies, and equipment.

6. MOVEMENT CONTROL DURING DEPLOYMENTS. To provide complete and continued movement support to deploying MAGTF/unit commanders during the pre-deployment and deployment phases, CG, II MEF establishes control, coordination, and support organizations within and between existing commands and agencies. In some cases these are standing organizations such as the MAGTF Deployment and Distribution Operations Center (MDDOC), the MMCC and Major Subordinate Command (MSC) and Major Subordinate Element (MSE) Unit Movement Control Centers (UMCC), and others are activated as required such as Regiment Headquarters and below UMCCs, Port/Beach/Rail Operations Group (POG/BOG/ROG), air/surface liaison elements (ALE/SLE), arrival/departure area control group (AACG/DACG or A/DACG) and movement control teams (MCT) IOT assist the deploying MAGTF/unit commander in his efforts to prepare, pack-up, and move to geographically dispersed POEs for deployment.

7. MOVEMENT CONTROL ORGANIZATIONS

a. According to reference (e), peacetime movement control organization and their execution procedures are the same as

5-4 Enclosure (1)

those in wartime. Therefore, it is important that movement control organizations function in the same way during directed exercises as they do during contingency operations. During unit deployment, movement control organizations are established down to battalion/squadron levels. Movement control organizations are task organized from unit Tables of Organization (T/0} and Tables of Equipment (T/E). In smaller MAGTFs or units, the movement control organization may only consist of one personnel and limited assets. Figure 5-1 depicts the relationship between various commands, their movement control agencies, and supporting organizations during a MAGTF/unit deployment.

)GARRISON MODOC STRUCTURE TEMPLATE

MDDO l<z<s$1===H .... GH=E==R=H .... QT=R==S== ~= ~=i=;:_, ___ MD_D_O ___ T"!"l-,-'4)-0-0C .... CN,q .. -...... ---... _us ...... ~oc~u ~ Is~~

i--1 I I I

i I

~------ '

I 1-------1 r----· I

L.-----1 ..... _o_t__,

DlSTRIBUflOH MANAGEMENT

)µ~['

~~c

OPERATIONS

Figure 5-1

I IU.GTf PDIIIM I·····

lffffnn ... -11 .. ..-11 ···· IIJI :11111111

llPl'Clillf ·-- IIFf'IICO

L,111~ L, t:.i,:e POO

BOG

ROG

-Arthltf · 'ArliCO -AtliCO ·····A~CLOO -AIICU-0

b. This SOP establishes the guideline for the composition and procedures for movement control centers within II MEF. The following organizations support development:

(1) MDDOC. Located within the MAGTF Command Element, the MDDOC assumes the responsibilities of the Force Movement Control Center (FMCC). The MODOC shall conduct integrated planning, provide guidance and direction, and coordinate and

5-5 Enclosure ( 1)

monitor transportation and inventory resources as they relate to management of the MAGTF's distribution process.

(2) MMCC. The MMCC, a standing element of the MODOC, allocates, schedules, and coordinates ground transportation requirements based on the MAGTF Commander's priorities. The size and scope of the MMCC scales to meet mission requirements for the size of MAGTF in which it supports (MEF, MEB, MEU, and Special Purpose MAGTF (SPMAGTF)). The MMCC may require augmentation to execute movement command and control based on operational tempo. The MMCC supports the planning and execution of MAGTF movements and reports directly to the MODOC. The MMCC coordinates all MAGTF ground movement scheduling, equipment augmentation, transportation requirements, material handling equipment, and other movement support. In addition, it coordinates activities with installation operations, support groups, UMCCs, and coordinates the MAGTF priorities with the Terminal Operations Organizations (TOO) via the MODOC.

(3) Unit Movement Control Center (UMCC). UMCCs are standing organizations at MSC and established as required for MSE (Regiment and below). UMCCs shall serve as MSC, MSE and smaller unit transportation control measures.

(4) TOO. TOOs are integral to the deployment and distribution system by providing support at strategic, operational, and tactical nodes. Examples of TOOs are Arrival/Departure Area Control Group (A/DACG), Port Operations Group (POG), Beach Operations Group (BOG), and Rail Operations Group (ROG) Movement Control Team (MCT). TOOs are established by the MMCC as required and shall be task organized, manned by the Logistics Combat Element (LCE) and augmented by MSCs as required to perform the following tasks:

(a) Establish support and execute priorities as designated by the MODOC.

(b) Provide terminal operation support for various modes and sources of transportation.

(c) Comply with higher headquarters reporting requirements.

(5) Air Liaison Element (ALE), Sea Liaison Element (SLE), and Railhead Liaison Element (RLE)

(a) The MAGTF/unit commander establishes an ALE at each APOE/D to coordinate between the deploying MAGTF/unit and the A/DACG.

5-6 Enclosure (1)

(b) The MAGTF/unit commander establishes an SLE at each SPOE/D to coordinate between the deploying MAGTF/unit and the BOG/POG.

(c) The MAGTF/unit commander establishes an RLE at each railhead to coordinate between the deploying MAGTF/unit and the RHOG.

5-7 Enclosure (1)

CHAPTER 6

GENERAL.

DFTS

FDP&E BUSINESS RULES (II MEF SPECIFIC)

PAGE 6-2

TAD.

SUBMISSION OF OFT TRAINING INTENTIONS AND UNIT CONOPS ....... .

DEPLOYMENT WITH INDIVIDUAL WEAPONS.

DEPLOYMENT OVER HOLIDAY PERIODS

PRE-DEPLOYMENT TRAINING PROGRAM (FTP) AS IT RELATES TO THE FDP&E PROCESS ..

6-4

6-5

6-5

6-5

6-6

6-6

AUTHORITY TO VERIFY OR CERTIFY THE TPFDD 6-7

CARGO DESCRIPTIONS IN JOPES. . 6-7

DEPLOYMENTS THAT DO NOT REQUIRE CARGO .... 6-7

PERSONAL BAGGAGE POLICY. . 6-8

"ORDERED NOT USED" AIRLINE SEATS 6-11

SUBMISSION TIMELINES FOR REQUIREMENTS IN SUPPORT OF A CCDR.

COMMANDING OFFICER ENDORSEMENTS (COEs) AND GENERAL OFFICER ENDORSEMENTS (GOEs) FOR

. . 6-12

REQUIREMENTS IN SUPPORT OF A CCDR. . 6-14

S-3 ENDORSEMENTS AND G-3 ENDORSEMENTS FOR REQUIREMENTS IN SUPPORT OF A CCDR ..

SUBMISSION TIMELINE FOR CONUS DFT'S.

COMMANDING OFFICER ENDORSEMENTS (COEs) AND GENERAL OFFICER ENDORSEMENTS (GOEs) FOR

6-15

6-16

CONUS DFT'S ............. ,, .... 6-16

6-1 Enclosure (1)

S-3 ENDORSEMENTS AND G-3 ENDORSEMENTS FOR CONUS DFTs

SUBMISSION OF GOPAX FLIGHTS REQUESTS FOR EVENTS THAT DO NOT REQUIRE THE SUBMISSION OF A

6-17

TPFDD. . . . . . . . . . . . . . . . . . . . 6-17

6-2 Enclosure (1)

CHAPTER 6

FDP&E BUSINESS RULES (II MEF SPECIFIC)

1. GENERAL. In addition to supporting CCDR requirements, II MEF has additional FDP&E requirements that are specific to the conduct of DFTs because MSCs take advantage of training opportunities outside of the local area. In order to maximize airlift and ground transportation while minimizing excessive cost, II MEF directs the verification of a TPFDD that supports the CONOPS or exercise directive for several of these events. The below table provides clarity on operations, training and other events that typically require/do not require a TPFDD:

·•·•·······i•··,:•••····•·•" .. i·••··•::··••··?·Reciui•res·.·r.·.a:·. ··tt'pti)p/)i(:\. \\:i/t?(/T.I . :·.·u:·<•·!U:ht>P.e~·311Tq•-t ·:gequ:i.re • a:·siTPll'PP.•i> <: , .. CCDR requirements Conferences CJCS exercises Expos Global Response Force (GRF) Air shows CONUS-Based Alert Force (CBAF) Fleet Week Marine Corps Response Force Marine Week South (MCRF-S) MEU deployment MEU PTP events Unit Deployment Program (UDP) Type Commander's Amphibious

Training (TCAT) Crisis Response (CR) Force Deck Landing Qualifications Rotations {DLQ) Defense Support of Civil Naval Surface Fire Support Authorities (DSCA) {NSFS) Presidential Inauguration Flight in Support of Deployed

Unit (FISDU) State of the Union Address Capability Exercises (CAPEX) Republican National Convention Equipment testing Democratic National Convention Load sling certifications Nuclear Re-fuel/De-fuel (RFDF) Tactical Air (TAC AIR) missions exercises Tactical Air Integration (TAC Very Important Person Security AIR} deployment in support of Support Activity {VIPSSA) Expeditionary Strike Group Integrated Training Exercise Static Displays (ITX)

Weapons Tactics Instructor Well-deck Operations (WTI) support (does not include students that are temporary assigned duty (TAD) )

6-3 Enclosure (1}

CONUS Deployments for Training (DFTs) that require the purchase of GOPAX flights, commercial airline tickets and/or commercial ground transportation

DFT's where PAX deploy strictly via convoy

Separate DFTs that support WTI Landing Craft Utility (LCU) (i.e., EX BLUE AIR) Training I---'---'-------~-------------' Mountain Warfare Training Center (MWTC)

2. DFTs. DFTs conducted outside the local area often require coordination measures that are atypical to operational deployments. The general rule for the local area is defined as the local training areas respective to home station as follows: Marine Corps Base Camp Lejeune, Marine Corps Air Station, New River, Marine Corps Air Station, Cherry Point, and Marine Corps Air Station, Beaufort. The establishment of command relationships (specifically the assignments of units to a commander) for the DFT may not be required until the exercise or training event begins. Therefore, for many DFTs outside the local area the DOT shall hold a "Special Meeting of the DOT 11 •

a. The target date for a special meeting is 10 days prior to the verification of the TPFDD. It is subject to change, based upon the following factors:

(1) Submission of CONOPS to this headquarters as per the directed timeline (submission is required 60 days prior to training day one).

(2) Exercise and OFT tasking message release dates.

b. This meeting is announced during the daily DOT meeting and, when required, published via AMHS message.

c. Unit S-3 and S-4 representatives are expected to attend the special meeting in order to accurately define requirements, socials constraints, facilitate coordination between units and develop an understanding of MEF force deployment requirements.

d. The outputs of this meeting are utilized to consolidate unit deployment efforts in order to define the most cost effective means of deployment.

e. The information gathered in this meeting is published via AMHS message as per Annex G.

6-4 Enclosure (1)

3. Temporary Assigned Duty (TAD). Not every event shall require the submission of a TPFDD. Units shall be notified via PTDO, DEPORD, tasking message, or TPFDD LOI of the requirement for verification of a TPFDD for an event. If a unit is not required to submit a TPFDD, the trip is considered a TAD event (conferences, etc).

4. SUBMISSION OF DFT TRAINING INTENTIONS AND UNIT CONOPS

a. In order for a unit to train outside of the local area, CG, II MEF requires the submission of a OFT Intentions message, per reference (g), via UNCLASS AMHS message 120 days prior to training day one (TD 1). It shall be a coordinated message (S­sections and G-sections as required).

b. The submission of a DFT Intentions message is a "trigger" for deployment planning.

c. In accordance with (IAW) reference (g), CONOPS are required to this headquarters NLT 60 days prior to TD 1.

d. Once the CONOPS is received, AC/S G-3 shall publish JOPES guidance for the subordinate command(s).

5. DEPLOYMENT WITH INDIVIDUAL WEAPONS

a. Units are directed to deploy with individual weapons as per reference (f).

b. When a commander desires to have the requirement to deploy with individual weapons waived, a request for a waiver to deploy without individual weapons must be submitted via UNCLASS AMHS to this headquarters 10 days prior to the verification of the deployment TPFDD. This allows adequate time for the waiver to be routed. Not subject to delegation, Marine Forces (MARFOR) component level authority must approve all weapons waivers.

c. IAW reference (f), in order for a weapons waiver to be approved, an adequate force protection plan must be developed and implemented to mitigate risk. Submission of the force protection plan must accompany the request for a waiver to deploy without weapons.

d. Commandant of the Marine Corps (CMC) has determined that there are events that do not require the deployment with individual weapons because it is inconsistent with mission accomplishment (firefighting or humanitarian assistance/disaster relief). Also, there is the case of 2D MAW's training squadrons that do not maintain individual weapons for students, as well as

6-5 Enclosure (1)

personnel that are attending WTI in a student status. In these instances, a submission of a waiver is not required.

e. In other cases, deployment with weapons may be impractical or unfeasible due to administrative and/or logistical constraints. In these cases, weapons waivers must be submitted for approval. Weapons waivers are typically approved for CONUS community relations and strategic engagement events (Fleet Weeks, Marine Weeks, etc), except when required by

CONOPS.

f. An example of a unit request for waiver to deploy without individual weapons may be found in Annex E.

g. Verifications for units authorized to deploy without individual weapons shall include a statement identifying the approval. It shall be stated as follows (verbatim): "A WAIVER HAS BEEN GRANTED TO DEPLOY WITHOUT INDIVIDUAL WEAPONS (insert date time group (DTG) of II MEF AMHS message here)." If waiver approval has not been received by the verification due date, then the following statement shall be included in the newsgroup verification (verbatim): "A WAIVER REQUEST WAS SUBMITTED ON DDMMYYY BUT HAS NOT YET BEEN APPROVED. IF WAIVER REQUEST IS DENIED, WPNS SHALL BE HAND CARRIED." Verifications received without this statement or without the AMHS message identified shall be returned to the unit with no action taken.

6. DEPLOYMENT OVER HOLIDAY PERIODS. It is the policy of CG, II MEF that, when possible, units shall not deploy over a federal holiday period. This is to avoid unnecessary manpower requirements and excessive costs during designated periods of liberty. Understanding that many deployment dates are directed by higher headquarters based upon a myriad of factors, all efforts shall be made to adjust deployment dates around the holiday periods. When adjustments to deployment dates are deemed not feasible, a request for a waiver to deploy during a holiday period must be submitted to this headquarters via a coordinated G-3/G-4 unclassified (UNCLASS) AMHS message 7 days prior to the submission of the TPFDD for the deployment. If requesting to redeploy over a holiday period, the same rule applies. Requests shall include why deployment has to occur over the holiday period and specify the impact to mission if authority to deploy over a holiday period is not granted. An example of a unit request to deploy over a holiday period (with approval from II MEF) is located in Annex D.

7. PRE-DEPLOYMENT TRAINING PROGRAM (PTP) AS IT RELATES TO THE FDP&E PROCESS

6-6 Enclosure (1)

a. Not every area of operations (AOR) has a pre-deployment training requirement; however service requirements must still be met.

b. Where a PTP requirement exists, a PTP Certification or PTP requirement completion message must be released for deploying units. This shall be completed by II MEF G-7 and in coordination with II MEF FDP&E. A PTP certification message must also be released for individuals deploying apart from the main body of their unit. The TPFDD verification must reference this message.

c. If PTP has not been completed by the verification due date, then the following statement shall be included in the newsgroup verification (verbatim): "PAX ARE CURRENTLY EXECUTING PTP AND SHALL BE COMPLETED PRIOR TO RLD. IF PTP WILL NOT BE COMPLETED BY RLD, THIS HEADQUARTERS WILL NOTIFY CG, II MEF VIA NEWSGROUP AND THE PAX SHALL NOT DEPLOY."

d. Verifications received without this statement or without the AMHS message identified shall be returned to the unit with no action taken.

8. AUTHORITY TO VERIFY OR CERTIFY THE TPFDD. The authority to verify or certify a TPFDD lies with the commander. Understanding the limited availability of General Officers and Commanding Officers for this task, an officer on the MSC staff must approve the accuracy of the data and information contained within the newsgroup, JOPES and other files submitted to this headquarters. This approval shall be stated as the last paragraph of the verification. It shall be stated as follows (verbatim): "THIS NEWSGROUP AND ALL INFORMATION RELATED TO THIS ISSUE HAVE BEEN REVIEWED AND APPROVED BY (insert name of officer and their POC info here)." Verifications received without this statement shall be returned to the unit with no action taken.

9. CARGO DESCRIPTIONS IN JOPES. JOPES only allows for 14 characters for cargo description. Because of this system limitation, it is necessary for units to change that description after the upload of JFRG data is complete. The cargo description shall not read "QUADCON" or "PALCON". It shall identify the capability of the container (i. e, "NON-LETH WPNS", "MED SUPPLIES", "S-1 OFFICE", "DASC EQUIP", "MT TOOLS, "SATCOM EQUIP", "C4I EQUIP", "BN COC", etc). This task is most efficiently completed at the regiment/group level.

10. DEPLOYMENTS THAT DO NOT REQUIRE CARGO. There are instances when units will deploy without cargo. Due to the infrequency of

6-7 Enclosure (1)

this type of deployment, the verification must contain a statement that cargo is not required to accomplish the mission.

11. PERSONAL BAGGAGE POLICY. II MEF deploys forces worldwide in support of operations, exercises and other initiatives. The primary mode of transportation for the deployment, redeployment and rotation of II MEF forces is by strategic or commercial charter airlift. USTRANSCOM uses the DoD PAX weight/baggage allowances to generate lift requirements and assign aircraft. Lessons learned have provided data showing that units have experienced problems at the APOE. Specifically, these problems were due to deploying units not adhering to the DoD mandated PAX weight/baggage restrictions and the use of improper and/or unauthorized personal baggage for deployments. This resulted in units exceeding the maximum weight or cargo capacity of an aircraft.

a. Purpose. The policy established in this document helps to prevent possible mission failure due to personnel being separated from their baggage because of either "cubing-out" (exceeding the maximum cargo capacity of an aircraft), or "weighing-out" ( exceeding the allowable cabin load (ACL) ( or weight capacity of an aircraft), preventing the loading of all of the personal baggage. It is applicable to all training, UDP and operational deployments.

b. General Restrictions - In All Cases

(1) MSCs shall inspect all baggage in the unit marshaling area (UMA) to ensure compliance with weight, dimensions, type and quantity prior to movement to the APOE. Unauthorized baggage shall not be moved to the APOE.

(2) Baggage arriving at the APOE not in compliance shall not be loaded. This includes baggage in excess of authorized numbers identified for each deployment type above. Unit bags, fire team bags, etc. are not authorized and if required shall be coordinated as excess baggage.

(3) Checked baggage shall not exceed 70 pounds each or 62 linear inches (the sum of the length plus width plus height).

(4) Oversized baggage is prohibited and is defined as any bag exceeding 62 linear inches and/or 70 pounds. Examples include large parachute bags, oversized B-4 bags, duffel bags, large sea bags and large deployer bags.

(5) Civilian suitcases are not authorized.

6-8 Enclosure (1)

(6) Foot lockers are not authorized.

(7) Hand-carried items shall be no larger than 45 linear inches and must fit under the passenger's seat or in the overhead compartment.

c. Belly TAT

(1) Belly TAT must be identified in the TPFDD verification newsgroup.

(2) Cargo that is deemed belly TAT must have justification for the requirement to accompany the unit on an aircraft rather than deploy via other means (strategic, channel or commercial cargo modes of transportation).

(3) Belly TAT that arrives at the APOE that has not been verified in the TPFDD shall not be embarked on the aircraft.

d. Training Deployments

(1) Checked baggage shall be limited to any two of the following bags:

(a) Standard military issue sea bag

(b) Rucksack

(c) Improved Load Bearing Equipment (ILBE)/USMC pack

(d) VALPAC

(e) Parachute bag

(f) Authorized deployer bag

(2) Hand-carried baggage shall be limited to one small bag or back-pack, one personal item (brief case, computer bag) and individual weapon.

(3) PAX weight with baggage is 350 pounds per PAX.

e. UDP Deployments

(1) Checked baggage shall be limited to any two of the following bags:

(a) Standard military issue sea bag

6-9 Enclosure (1)

(b) Rucksack

(c) Individual Load Bearing Equipment (ILBE)/USMC pack

(d) Valpak

( e) Parachute bag

(f) Authorized deployer bag

(2) Hand-carried baggage shall be limited to one small bag or back-pack, one personal item (briefcase, computer bag) and individual weapon.

(3) PAX weight with baggage is 350 pounds per PAX.

(4) Personnel on active flight status are authorized an additional bag, not to exceed 55 pounds, for flight-related equipment. It shall be identified as pro-gear to account for the additional weight requirement. Once verified in the TPFDD, the additional baggage shall be handled and loaded as checked baggage. The additional baggage shall be properly identified in the TPFDD as "pro gear" as part of the unit To Accompany Troops (TAT) cargo, and requires justification in the TPFDD verification. Excess baggage/cargo on conunercial charter flights is limited to 800 pounds total per battalion/squadron­size unit, regardless of the number of aircraft allocated to flow the entire unit. Verified pro-gear does not count against the battalion/squadron 800 pound allocation for excess baggage/cargo.

f. Combat Deployments

(1) Checked baggage shall be limited to any three of the following bags:

( a) Standard military issue sea bag

(b) Rucksack

( c) ILBE/USMC pack

( d) VALPAC

( e) Parachute bag

( f) Authorized deployer bag

6-10 Enclosure (1)

(2) Hand-carried baggage shall be limited to one small bag or back-pack, one personal item (briefcase, computer bag) and individual weapon.

(3) PAX weight with baggage is 400 pounds per PAX.

(4) Personnel on active flight status are authorized an additional bag, not to exceed 55 pounds, for flight-related equipment. It shall be identified as pro-gear to account for the additional weight requirement. Once verified in the TPFDD, the additional baggage shall be handled and loaded as checked baggage. The additional baggage shall be properly identified in the TPFDD as ''pro gear'' as part of the unit cargo, and requires justification in the TPFDD verification. Excess baggage/cargo on commercial charter flights is limited to 800 pounds total per battalion/squadron-size unit, regardless of the number of aircraft allocated to flow the entire unit. Verified pro-gear does not count against the battalion/squadron 800 pound allocation for excess baggage/cargo.

g. Exceptions for Excess Baggage

(1) Excess baggage is baggage that exceeds the authorized number of checked bags per passenger as stipulated above.

(2) For personnel traveling via commercial ticket on civilian aircraft, excess baggage must be authorized in individual orders. This exception is not applicable to commercial charter aircraft.

(3) For unit move/deployment, excess baggage must be identified as unit cargo in the deployment TPFDD. Cargo deployment justification is required with the TPFDD verification. Excess baggage/cargo verification for movement on commercial charter flights is limited to 800 pounds total per battalion squadron size unit, regardless of the number of aircraft allocated to flow the entire unit. Verified pro-gear does not count against the battalion/squadron 800 pound allocation for excess baggage/cargo.

12. "ORDERED NOT USED" AIRLINE SEATS

a. Over the course of the past decade, II MEF has paid millions of dollars in ''ordered not used'' airline seats on commercially chartered aircraft. These airline seats were purchased based upon verified TPFDD requirements submitted to II MEF by the MSCs. The majority of these losses are directly attributed to the failure of units to properly plan their

6-11 Enclosure (1)

deployment and accurately reflect the requirements in the TPFDD. In today's fiscally constrained environment, and as a designated steward of these scarce resources, this is unacceptable.

b. Assignment of Responsibility for Payment. Waste resulting from passenger shortfalls on a commercially chartered aircraft (''Ordered Not Used'' airline seats), purchased with II MEF funds shall be charged to the responsible MSC for reimbursement from their respective budgets. Furthermore, if the unused seats would have resulted in a decrease in the overall contracted cost of the aircraft, the MSC shall be charged the difference.

c. Authorized Disparities. Certain operational and unforeseen events can certainly cause situations beyond a commander's control that result in a disparity between the TPFDD and the actual PAX and cargo manifested to the aircraft. For discrepancies greater than 2 percent of the data in the TPFDD (by ULN and by carrier), commanders may submit a letter to II

MEF G-4 requesting relief from fiscal charges. These cases shall be assessed and resolved on an individual basis. Examples of justifiable shortfalls include hospitalization, incarceration, or emergency leave within 24 hours of movement. Known variations in lift requirements based upon refined planning or operational events should be identified to the chain of command immediately to mitigate waste. While these occasions may be unavoidable, it remains incumbent upon commanders to register the change through the formalized FDP&E process as soon as it is known.

13. SUBMISSION TIMELINE FOR REQUIREMENTS IN SUPPORT OF A CCDR

a. Typical timelines for submission of a TPFDD in support of a combatant commander (whether for an operational requirement or an exercise) are due this headquarters:

(1) Northern Command (NORTHCOM): EAD minus 28 days

(2) Southern Command (SOUTHCOM): EAD minus 28 days

(3) European Command (EUCOM)

(4) Africa Command (AFRICOM)

EAD minus 28 days

EAD minus 38 days

(a) AFRICOM requires an extended timeline due to timelines associate with diplomatic clearances

6-12 Enclosure (1)

(b) Due date remains the same no matter the destination (i.e., SPMAGTF-Crisis Response Africa's destination is in Europe)

(5) Central Command (CENTCOM): EAD minus 28 days

(6) Pacific Command (PACOM): EAD minus 28 days

(7) Special Operations Command (SOCOM): EAD minus 28 days

b. It should be noted that the CCDR has the prerogative to require a TPFDD on an earlier timeline. In the past, there have been defined periods of time where a TPFDD was required a week earlier than usual. This was due to keen competition for commercial airlines that had less availability during the summer season.

c. CJCS directed exercises will typically have due dates far in advance of the standard timelines (sometimes due EAD minus 60 days) .

d. A TPFDD requiring the submission for a SAAM is due on an earlier timeline (not the "normal" TPFDD verification timeline of EAD minus 28 days). Examples of such situations are the UDP and contingency ESTA. In these cases where a SAAM request is required, the SAAM must be approved through the S-3/G-3 as well as the S-4/G-4 chain. In the case of UDP, Marine Forces Pacific (MARFORPAC) requires the submission of a SAAM. The SAAM is funded by MFP, therefore the timeline is theirs to dictate. There is no operational chain when submitting the SAAM like we have with a TPFDD verification (it is S-4/G-4 centric). Changes to the SAAM are authorized without General Officer involvement. The TPFDD is verified for visibility only in JOPES and does not affect the allocation of airlift. For this reason, the below business rules shall be adhered to for this specific deployment type. These business rules shall allow for maximum flexibility during the time period between the SAAM submission and an updated and more accurate verification of the TPFDD. This will help to ensure that the SAAM request and the TPFDD match and it allows for a commanders verification of the requirement through the established FDP&E process.

(1) The due date of the SAAM shall be in accordance with reference (h) (ALD-90 days) or as directed.

(2) The TPFDD and MDSS II data shall be due to II MEF at EAD-35 days.

6-13 Enclosure (1)

(3) If there is a difference between the TPFDD and MOSS II data, and the SAAM that was submitted, an updated SAAM shall be submitted NLT ALD-32 days so all data matches and to achieve the SAAM submission milestone of 30 days prior for a 10 percent cost savings.

e. The MOSS II data file (Level IV data), load plans and Hazardous Materials Diplomatic Clearance (HAZDIP) for the unit cargo (to include belly loadable TAT) must be submitted with the TPFDD verification. This ensures that the S-4/G-4 documentation and the TPFDD have been reviewed by the S-3/G-3 and S-4/G-4 for accuracy. Verifications that are received by the G-3 without the G-4 having received the S-4/G-4 documentation shall be returned with no action taken. The timeline for "simultaneous" receipt is 60 minutes.

f. Verification newsgroups shall have the following statement, "THE MOSS II DATA HAS BEEN SUBMITTED THROUGH THE S-4/G-4 CHAIN. THE MOSS II DATA MATCHES THE TPFDD."

14. COMMANDING OFFICER ENDORSEMENTS (COEs) AND GENERAL OFFICER ENDORSEMENTS (GOEs) FOR REQUIREMENTS IN SUPPORT OF A CCDR

a. CG, II MEF is required to submit a GOE to COMMARFORCOM based upon CCDR supplements to the Joint TPFDD LOI. The typical timeline for II MEF to submit a GOE is after EAD minus 26 days.

b. If a verification requiring strategic lift (AK) is submitted after the due date, the following shall be required:

(1) II MEF Headquarters Group: COE.

(2) 2d Marine Division: GOE.

(3) 2d Marine Aircraft Wing: GOE.

(4) 2d Marine Logistics Group: GOE.

(5) 2d Marine Expeditionary Brigade: GOE.

(6) Marine Expeditionary Unit: COE.

c. Unauthorized Deployment. PAX deploying in support of a CCDR require a validated ULN. This occurs at the CCDR level. There are three levels of command between the MSC and the CCDR, therefore the process takes time. Deployment without a validated ULN is considered an unauthorized deployment. Unauthorized deployments require a COE or GOE (as per paragraph 14) .

6-14 Enclosure (1)

d. II MEF is required to verify with a GOE. If II MEF is required to verify the TPFDD with a GOE, the MSC is required to verify with a COE (no matter the mode/source).

e. COEs and GOEs may be signed by personnel with authority to sign by direction for the Commanding Officer or Commanding General. The person signing must be added as a point of contact to the verification message.

f. COEs and GOEs are due to this headquarters within 3 working days after identification of the requirement for an endorsement. COE's and GOE's shall be submitted via Secure Internet Protocol (SIPR) newsgroup and Non-secure Internet Protocol (NIPR) Automated Message Handling System (AMHS). Guidance is provided in reference (i). An example of a COE may be found in Annex I. GOEs shall be submitted in the same format.

15. S-3 ENDORSEMENTS AND G-3 ENDORSEMENTS IN SUPPORT OF A CCDR

a. If a verification requiring channel or commercial lift is submitted after the due date, the following shall be required:

(1) II MEF Headquarters Group: S-3 Endorsement.

(2) 2d Marine Division: G-3 Endorsement.

(3) 2d Marine Aircraft Wing: G-3 Endorsement.

(4) 2d Marine Logistics Group: G-3 Endorsement.

(5) 2d Marine Expeditionary Brigade: G-3 Endorsement.

(6) Marine Expeditionary Unit: S-3 Endorsement.

b. S-3 and G-3 endorsements may be signed by personnel with authority to sign by direction for the S-3 or G-3.

c. S-3 and G-3 endorsements for PAX/cargo discrepancies are due to this headquarters within 3 working days after identification of the requirement for an endorsement.

d. S-3 and G-3 endorsements shall be submitted via SIPR newsgroup and NIPR AMHS. Guidance is provided in reference (i). An example of a COE may be found in Annex I.

6-15 Enc lo sure ( 1)

16. SUBMISSION TIMELINE FOR CONUS DFTs

a. CG, II MEF is not required to submit TPFDD verifications to COMMARFORCOM for CONUS DFTs. However, II MEF units shall utilize the FDP&E process for CONUS DFTs as directed to maximize the utilization of lift while minimizing cost. Annex A depicts force deployment planning milestones for CONUS DFTs.

b. MSE/MSC TPFDD verifications for CONUS DFTs are due to this headquarters EAD minus 28 days.

c. The MDSS II data file (Level IV data), load plans and Hazardous Materials Diplomatic Clearance (HAZDIP) for the unit cargo (to include belly loadable TAT) must be submitted with the TPFDD verification. This ensures that the S-4/G-4 documentation and the TPFDD have been reviewed by the S-3/G-3 and S-4/G-4 for accuracy. Verifications that are received by the G-3 without the G-4 having received the S-4/G-4 documentation shall be returned with no action taken. The timeline for "simultaneous" receipt is 60 minutes.

d. Verification newsgroups shall have the follo.wing statement, "THE MDSS II DATA HAS BEEN SUBMITTED THROUGH THE s-4/G-4 CHAIN. THE MDSS II DATA MATCHES THE TPFDD."

17. COMMANDING OFFICER ENDORSEMENTS (COEs) AND GENERAL OFFICER ENDORSEMENTS (GOE'S) FOR CONUS DFT'S

a. If a verification requiring any means of lift coordinated through USTRANSCOM (Example: Group Operational Passenger System (GOPAX)) (AL), is submitted after EAD minus 11 days, the following shall be required:

(1) II MEF Headquarters Group: COE.

(2) 2d Marine Division: GOE.

(3) 2d Marine Aircraft Wing: GOE.

(4) 2d Marine Logistics Group: GOE.

(5) 2d Marine Expeditionary Brigade: GOE.

(6) Marine Expeditionary Unit: COE.

b. COEs and GOEs may be signed by personnel with authority to sign by direction for the Commanding Officer or Commanding General. The person signing must be added as a point of contact to the verification message.

6-16 Enclosure (1)

c. COEs and GOEs are due to this headquarters within 3 working days after identification of the requirement for an endorsement. COEs and GOEs shall be submitted via SIPR newsgroup and NIPR AMHS. Guidance is provided in reference (g). An example of a COE may be found in Annex I. GOE's shall be submitted in the same format.

d. COEs and GOEs do not apply to training squadrons as changes to PAX numbers and cargo are fluid based upon Training and Education Command (TECOM) curriculum and qualification factors that are beyond the control of 2d MAW.

18. S-3 ENDORSEMENTS AND G-3 ENDORSEMENTS FOR CONUS DFTs

a. If a verification requiring strategic (GOPAX) or commercial lift is submitted after EAD minus 28 days, the following shall be required:

( 1) II MEF Headquarters Group: S-3 Endorsement.

(2) 2d Marine Division: G-3 Endorsement.

( 3) 2d Marine Aircraft Wing: G-3 Endorsement.

( 4) 2d Marine Logistics Group: G-3 Endorsement.

(5) 2d Marine Expeditionary Brigade: G-3 Endorsement.

(5) Marine Expeditionary Unit: 8-3 Endorsement.

b. 8-3 and G-3 endorsements shall be submitted via SIPR newsgroup and NIPR AMHS. Guidance is provided in reference (g). An example of a COE may be found in Annex I. 8-3 and G-3 endorsements shall be submitted in the same format.

c. 8-3 and G-3 endorsements do not apply to training squadrons as changes to PAX numbers and cargo are fluid based upon TECOM curriculum and qualification factors that are beyond the control of 2d MAW.

19. SUBMISSION OF GOPAX FLIGHTS REQUESTS FOR EVENTS THAT DO NOT REQUIRE THE SUBMISSION OF A TPFDD

a. Examples of events that do not require a TPFDD are aggregation of students to attend a course (WTI) and training squadron events. For example, students that attend WTI are in a student/TAD status and typically travel via DTS orders and on commercial aircraft. However, II MEF has found that there is

6-17 Enclosure (1)

the potential to aggregate PAX which results in cost savings to the government.

b. Staff coordination at II MEF and the MSC's is paramount for maximizing lift at minimal cost. However, a TPFDD cannot be mandated for these events due to the command relationship between II MEF, the units, and the training venue. In lieu of a TPFDD, units requiring GOPAX flights for lift for these types of events shall submit a coordinated G-3/G-4 message when requesting GOPAX flights. An example of such a message may be found in Annex J.

6-18 Enclosure (1)

ANNEX A

DEPLOYMENT PLANNING FOCUS AREAS

1. GENERAL. The DOT is decisively engaged in coordinating and executing worldwide deployments, however the deployment of forces requires the unit commander to ensure the accuracy of the data. This annex iqentifies the most common errors and oversights that require the commander's focus to improve efficiency of the FDP&E process. Due to operational requirements and training objectives, not every deployment is the same. However, there are common threads to the FDP&E process that guide planners.

2. COMMAND ATTENTION. The authority for the verification of the TPFDD lies solely with the commander. Planning the deployment requires the detailed attention of the commander and/or a designated staff officer at each level. Care must be taken in the delegation of the FDP&E process and approval authority at the unit level. Too often, commanders delegate this authority to the MAGTF Planning Specialist or Embark Specialist. This becomes evident when deployment data is late and/or inaccurate.

3. SUBMISSION OF AN INACCURATE TPFDD. The information for the TPFDD/deployment plan is required weeks prior to the actual deployment so that it can be approved at each level in the chain of command and ultimately submitted to the lift provider to schedule the lift of not only II MEF forces, but also service and Joint forces. This process requires early and accurate planning. As JFRG II plans are sourced directly from unit MOSS II databases, it is imperative that proper command attention be placed on the maintenance of MOSS II data. Continuous planning and ever-changing operational requirements mandate constant refinement of data. For example, the number of PAX may increase, or the short tonnage may decrease. Changes can and should be made, but by the time the unit's TPFDD is approved by the unit commander, it must be accurate and reflect the actual weights of cargo and number of PAX. As a MEF, we have experienced instances where strategic lift aircraft arrive to load the unit, and there were significant deviations from the load originally planned. Often errors in cargo data are discovered during review of load plans against a verified TPFDD. These discrepancies incur excessive additional costs and can result in de-allocation of lift.

4. TIMELY SUBMISSION OF THE TPFDD, MOSS II DATA AND AIRCRAFT LOAD PLANS. For the reasons outlined above, it is imperative that unit commanders approve their TPFDD prior to submission.

A-1 Enclosure (1)

CG, II MEF shall then verify the lift requirement to MARFORCOM per the suspense date directed by the CCDR. MSCs shall submit accurate, properly sourced load plans and hazardous material diplomatic clearances (HAZDIPS} in conjunction with MOSS II level IV data at time of verification which shall be verified by the II MEF SMO and forwarded to USTRANSCOM to secure airlift.

5. PRIORITY OF DEPLOYMENT MODE/SOURCE METHODS. The cost of airlift for II MEF deployments is extraordinary. With that in mind, we must consciously plan for the most cost effective means of deployment. The priority for mode/source (M/S} is: strategic airlift (AK}, channel airlift (AC}, and commercial airlift (AM). Note that II MEF gives the same M/S priority for GOPAX missions (AL) as is given strategic lift. Commercial tickets are to be utilized only when all other means are not available. If commercial tickets are the verified airlift choice, MSCs must provide full justification and risk to mission execution if forces do not flow within that M/S AM window.

6. SPECIFICS OF DEPLOYMENT VIA CHANNEL FLIGHT. Channel flights are contracted commercial aircraft that typically depart and arrive at civilian airports. Whether a channel flight departs or arrives at a civilian airport or military installation, all rules in the Defense Transportation Regulation (DTR) governing the deployment via commercial aircraft apply. There shall be a focus on prohibited items and the transport of weapons -specifically that weapons shall be transported in double-locked weapons cases.

7. SECURING SEATS FOR STRATEGIC LIFT AIRCRAFT AND/OR PURCHASING COMMERCIAL TICKETS AND THEN FAILING TO FILL THOSE SEATS. This wastes the tax payers' money in one case and is a misuse of valuable strategic airlift in the other. Once Marines and Sailors have been manifested for a flight or an airline ticket has been purchased, it is the commanding officer's responsibility to ensure these seats are filled.

8. MANIFESTING CARRIERS IN JOPES SCHEDULING AND MOVEMENT (S&M). Commanders are to manifest ULNs to carriers, in JOPES, specifying what assets have been loaded onto the transportation M/S. This report provides the theater commander visibility in JOPES of what shall actually arrive in his AOR to most accurately and efficiently coordinate intra-theater lift as required.

9. PROVIDING FLIGHT ITINERARIES. Commanders are responsible for submitting flight itineraries for M/S AM and AC flights once they are booked. These flights are to be booked in order to meet directed the required delivery date (RDD}. Failure to meet

A-2 Enclosure (1)

this timeline causes a delay in the manifesting process. If itineraries are not provided, carriers cannot be built in JOPES in order to execute manifesting in S&M.

10. ARRIVAL AT THE APOE FOR PAX AND CARGO. PAX shall arrive at the APOE NLT 4 hours prior to scheduled aircraft departure. PAX arrival times at the APOE are established in order to allow sufficient time to validate and correct manifests, affect final coordination with loadmasters, weigh PAX and baggage, and load the aircraft without encountering costly delays. Cargo shall arrive at the APOE and be introduced to the Ready Line in time to allow for the Joint Inspection (JI) to be completed NLT 24 hours prior to scheduled aircraft arrival. Flights scheduled over a weekend/designated liberty period or on the first work day after a weekend shall have JI's completed the day prior to the last work day. These timelines require detailed inspections to be conducted at all levels prior to arrival at the APOE and allows for enough time to coordinate changes to lift requirements or reconfigure loads if cargo is different than the data in the verified TPFDD.

11. PAX MOVEMENTS TO THE APOE. PAX movements must be choreographed to support the departure of aircraft. Buses for movement of PAX from unit marshaling areas (UMAs) to the APOE are contracted for a finite period of time that allows for loading PAX and baggage, transport to the APOE, and unloading. Units shall complete weapon withdrawals at unit armories, conduct family farewell events, and be arranged into bus teams prepared to board on arrival at the UMA prior to the arrival of the buses. This allows timelines to be met while not incurring additional costs for delaying buses beyond contracted time limits.

12. ACCURACY OF PAX/CARGO MANIFESTS. PAX and cargo manifests are another tool to provide theater commanders with in-transit visibility (ITV) of PAX and cargo entering the AOR. These manifests are uploaded to the Integrated Development Environment (IDE)/Global Transportation Network (GTN) providing near-real­time visibility of PAX and cargo on the strategic leg. Inaccurate PAX manifests can, and have, created delays in the loading process at the APOE. It is imperative that the unit S­l's assist in ensuring that PAX manifests are accurate.

A-3 Enclosure (1)

ANNEX B

FORCE DEPLOYMENT PLANNING MILESTONES FOR CONUS DFTS

The below table is not absolute and is often subject to changes due to operational requirements and planning occurring outside of this headquarters. The milestones should be utilized to shape force deployment efforts through requests for information and assignment of tasks. The below are also deadlines that are required for the most efficient utilization of resources.

Submission of CONOPS via TD-1 MINUS 60 DAYS (APPROX EAD-56) coordinated G-3/G-4 UNCLASS AMHS msg or receipt of tasking msg MEF publishes a TPFDD LOI EAD-50 Unit submits rail NLT 45 days prior to desired date of transportation request to movement MMCC TPFDD verified to MEF EAD-28 Approval of request to EAD-42 deploy equipment in excess of the requirement Unit submits request for NLT 20 working days prior to desired special hauling permit to date movement MMCC for oversize equipment movement ( DD1266) Unit submits TMR to MMCC NLT 15 working days prior to desired for TOT of superload cargo date of movement via TCPT Unit submits request for NLT 15 working days prior to desired convoy movement to MMCC date of movement (DD1265)

MEF G-4 requests Line of Upon verification of the TPFDD Accounting from funding authority MEF G-4 submits data in the NLT 10 working days prior to desired GOPAX web system for date of movement commercial flights Unit submits TMR to MMCC NLT 10 working days prior to desired for TOT of date of movement bonded/HAZMAT/oversize cargo via TCPT MEF MMCC submits for NLT 5 working days prior to desired transportation of non- date of movement bonded cargo Unit submits TMR to MMCC NLT 5 working days prior to desired for TOT of non-bonded and date of movement

B-1 Enclosure (1)

general cargo via TCPT Unit submits TMR to MMCC NLT 5 working days prior to desired for TOP via TCPT date of movement

B-2 Enclosure (1)

ANNEX C

DEPLOYMENT PLANNING CHECKLIST

This below table contains a list of documents, messages and data files in a rough "milestone" order. Not all documents will apply to each operation or exercise, but it may be used as a guide in planning and the construction of the TPFDD.

AOR: Event:

Event DTG/Date Complete PTDO DEPORD EXORD OFT Intentions Message submitted

(TD-1 minus 120 days) -~~~~~-+-~~~~~~~~~---~~~~~~~­CONOPS submitted (EAD minus 60 days) Weapons waiver submitted to II MEF Weapons waiver submitted to MARFORCOM Submission of force protection plan to II MEF Submission of force protection plan to MARFORCOM Approval of weapons waiver from MARFORCOM Approval of weapons waiver from II MEF Request to deploy over a holiday period submitted to II MEF Approval to deploy over a holiday period from II MEF Request to deploy over a holiday period submitted to II MEF Approval to redeploy over a holiday period from II MEF Feasibility of Support (FOS) from MARFORCOM to II MEF FOS from II MEF to MSE/MSC Response to FOS from MSE/MSC Response to FOS to MARFORCOM TPFDD LOI JOPES Guidance FRNs avail (MARFORCOM)

C-1 Enclosure (1)

II MEF TPFDD due to MARFORCOM FRNs avail {II MEF) MSE/MSC TPFDD due to II MEF Sourcing by MSE/MSC complete JFRG shell build complete JFRG export distributed to subordinate units MDSSII data associated with units in JFRG PTP msg released MSE/MSC TPFDD verification JFRG export submitted to II MEF (in conjunction with verification)

MOSS II data file submitted to II MEF (within 1 hour of submission of verification) Load plans/HAZDIPs submitted to II MEF (in conjunction with verification) Carriers created Carriers available Manifest carriers in JOPES Force Closure

C-2 Enclosure (1)

ANNEX D

EXAMPLE OF REQUEST TO DEPLOY OVER A HOLIDAY PERIOD ****************UNCLASSIFIED/**************** REQUEST WAIVER FOR DEPLOYMENT OF HMLA-167 FROM CHERRY POINT ISO ITX 1-13 DURING NEW YEARS DAY HOLIDAY PERIOD Originator: CG 2ND MAW G3(UC) DTG: 041411Z Dec 12 Precedence: Routine DAC: General To: CG II MEF G3(UC) CC: CG 2ND MAW G3(UC) CG 2ND MAW(UC) MAG 29(UC) HMLA 167(UC) UNCLASSIFIED/ MSGID/GENADMIN/CG 2ND MAW G3/DEC 12// REF/A/MSG/MAG 29/282135Z NOV 12// NARR/REF A IS MAG 29 WAIVER REQUEST.// POC/MARTINEZ, STACY/CAPT/CG 2ND MAW G3/FOPS/DSN:582-6409/COMM:252-466-6409/EMAIL:STACY.MARTINEZ@USMC.MIL// RMKS/1. 2ND MAW FORWARDS REF A, RECOMMENDING APPROVAL. 2. CLARIFICATION: RSOI 3-10 JAN 13, EXERCISE 11 JAN - 8 FEB 13. 3. REF A QUOTED BELOW.

QUOTE/ ****************UNCLASSIFIED**************** UNCLASSIFIED/ MSGID/GENADMIN/MAG-29 S3/NOV 12// SUBJ/REQUEST WAIVER FOR DEPLOYMENT OF HMLA-167 FROM CHERRY POINT ISO ITX 1-13 DURING NEW YEARS DAY HOLIDAY PERIOD// REF/A/MSG/CG II MEF G3/151814Z Jun 10// NARR/REF A IS CG II MEF POLICY DIRECTING THE CONDUCT OF DEPLOYMENT PLANNING// POC/TAYLOR, B.J./MAJ/MAG-29 S3/0PERATIONS OFFICER/DSN 752-5558// RMKS/1. PER REF A, CO MAG-29 IS REQUESTING A WAIVER TO DEPLOY HMLA-167 ON 2 JAN 13 DURING THE II MEF NEW YEARS HOLIDAY PERIOD. 2. EXERCISE DATES ARE 5 JANUARY - 11 FEBRUARY 2013. 3. UNIT HAS BEEN TASKED TO EXECUTE ITX 1-13 IN CONJUNCTION WITH SQUADRON PRE-DEPLOYMENT TRAINING BLOCK IV ASSESSMENT FOR UPCOMING OEF DEPLOYMENT. MAG-29 REQUESTS A WAIVER TO LIMITATIONS PLACED ON AIRLIFT REQUESTS DURING HOLIDAY PERIODS PER REF A. UNIT REQUIRES ADVANCED PARTY DEPLOYMENT VIA GOPAX DEPARTING FROM APOE AT MCAS CHERRY POINT TO MARCH AFB ON 2 JANUARY 2013. ADVANCED PARTY SHALL RECEIVE CARGO AND ESTABLISH SITE CAPABILITIES FOR A SUCCESSFUL EXERCISE AND ASSESSMENT. DELAYING UNIT'S ADVANCED PARTY DEPLOYMENT PAST 2 JANUARY 2013 SHALL HAVE A SIGNIFICANT IMPACT ON SQUADRON'S MISSION ACCOMPLISHMENT.// END QUOTE// BT//

D-1 Enclosure (1)

ANNEXE

EXAMPLE OF REQUEST TO DEPLOY WITHOUT INDIVIDUAL WEAPONS ****************UNCLASSIFIED/**************** Subject: 2D MAW ENDORSEMENT OF HMH-366 WAIVER REQUEST TO DEPLOY WITHOUT INDIVIDUAL WEAPONS Originator: CG 2ND MAW G3(UC) DTG: 091834Z Aug 12 Precedence: ROUTINE DAC: General To: CG II MEF G3(UC) cc: CG 2ND MAW G3(UC), MAG 29(UC), HMH 366(UC)

UNCLASSIFIED/ UNCLASSIFIED/ MSGID/GENADMIN/CG 2ND MAW G3/AUG 12// SUBJ/2D MAW ENDORSEMENT OF HMH-366 WAIVER REQUEST TO DEPLOY WITHOUT INDIVIDUAL WEAPONS// REF/A/MSG/MAG-29/081757Z AUG 12// NARR/REF A IS HMH-366 WAIVER REQUEST TO DEPLOY WITHOUT INDIVIDUAL WEAPONS.// POC/AAGAARD H/LTCOL/2D MAW G3 TRNG/EMAIL: HARALD.AAGAARD@USMC.MIL/COMM 252-466-4439 DSN 582// RMKS/1. 2ND MAW FORWARDS HMH-366'S REQUEST TO DEPLOY WITHOUT WEAPONS TO EDWARDS AFB FROM 8-21 OCTOBER 2012 ISO MRX RAVEN, RECOMMENDING APPROVAL. 2. REF A IS QUOTED BELOW.// ****************UNCLASSIFIED**************** UNCLASSIFIED/ SUBJ/MAG-29 ENDORESEMENT OF HMH 366 WAIVER REQUEST TO DEPLOY WITHOUT INDIVIDUAL WEAPONS FOR TRAINING TO EDWARDS AFB, CA// REF/A/MSG/CMC/150800Z NOV 00// REF/B/MSG/COMMARFORLANT/212300Z JUL 99// REF/C/MSG/HMH-366/0702036Z AUG 12// REF A AND REF BARE PROVIDED AS GUIDANCE FOR DEPLOYING WITH INDIVIDUAL WEAPONS.// POC/SPOJA/CAPT/COPSO/DSN 590-2665/MICHAEL.SPOJA@USMC.MIL// RMKS/ 1. THIS MSG ACCOMPANIES,REF C,THE HMH-366 DFT TO EDWARDS AFB, CA ISO MRX RAVEN CONOPS MESSAGE SUBMITTED VIA SEPCOR. PER THE REFS, HMH-366 REQUESTS WAIVER TO DEPLOY WITHOUT INDIVIDUAL WEAPONS ISO MRX RAVEN TO EDWARDS, AFB WITH JUSTIFICATION PROVIDED BELOW. 1.A. (U) THE SUPPORTED COMMAND HAS DETERMINED THAT T/0 WPNS ARE NOT EXPECTED, REQUIRED OR DESIRED FOR CONDUCT OF THE EXERCISE OR FOR USE IN DESIGNATED WORK AREAS. l.A.2. FORCE PROTECTION. THE EXERCISE SHALL BE CONDUCTED ABOARD A MILITARY INSTALLATION. A FORCE PROTECTION PLAN IS ATTACHED TO THIS MESSAGE.//

E-1 Enclosure (1)

ANNEX F

EXAMPLE OF THE CALLING MESSAGE FOR A SPECIAL MEETING OF THE DEPLOYMENT OPERATIONS TEAM (DOT)

****************UNCLASSIFIED/**************** CALLING MESSAGE FOR A SPECAIL MEETING OF THE II MEF DEPLOYMENT OPERATIONS TEAM (DOT) ISO ITX 3-13 Originator: CG II MEF G3(UC) DTG: DDTTTTZ Feb 13 Precedence: Routine DAC: FOUO To: CG 2ND MARDIV G3 (UC) CG 2ND MAW G3(UC) CG 2D MLG G3(UC) CC: CG 2ND MARDIV G4 (UC) CG 2ND MAW G4(UC) CG 2D MLG G4(UC) CG II MEF G3(UC) CG II MEF G4(UC) UNCLASSIFIED//FOR OFFICIAL USE ONLY// POC/HAMER/GS-13/CG II MEF G-3/COPS FDP&E/TEL: DSN 751-8860/COML: 910-451-8860/EMAIL: AARON.T.HAMER@USMC.MIL// POC/SEATON/GS-14/CG II MEF G-3/TRNG/TEL: DSN 751-8845/COML: 910-451-8845/EMAIL: VERNE.SEATON@USMC.MIL// POC/THOMAS/CW05/CG II MEF G-4/SMO/TEL: DSN 751-8413/COML: 910-451-8413/EMAIL: BRICE.THOMAS@USMC.MIL// POC/SWINK, R.D./GSll/MMCC DIRECTOR/-/TEL: COM 910-451-4690/ TEL: CELL 910-467-4189/ EMAIL: DALE.SWINK@USMC.MIL// RMKS/1. (U) OVERVIEW. THE PURPOSE OF THIS MESSAGE IS TO ANNOUNCE A SPECIAL MEETING OF THE II MEF DOT ISO ITX 3-13. 1.A. (U) A SPECIAL MEETING OF THE DOT SHALL BE HELD ON 22 MAR 2013 AT 1030 IN THE II MEF G-3 FDP&E CONFERENCE ROOM. ALL ATTENDEES ARE REQUIRED TO HAVE A SECRET CLEARANCE. VISITORS ARE REQUIRED TO REPORT TO THE MAIN ENTRANCE OF II MEF HQ (BLDG H-1, CAMP LEJEUNE) TO OBTAIN A VISITOR BADGE FOR THE MEETING. PLEASE ALLOW TIME FOR THIS REQUIREMENT. l.B. (U) THE TARGET AUDIENCE FOR THIS MEETING INCLUDES MEF G-3 FDP&E, MEF G-3 TRNG, MEF G-4 SMO, MSC G-3 AND G-4 REPRESENTATIVES, AND UNIT S-3 AND S-4 REPRESENTATIVES. REPRESENTATIVES ARE REQUIRED TO PROVIDE DETAILED INFORMATION REGARDING CONOPS, UNIT PAX, DESIRED DEPLOYMENT DATES, AND PAX AND CARGO MODES OF TRANSPORTATION. REPRESENTATIVES MUST BE AUTHORIZED TO MAKE DECISIONS REGARDING THE ESTABLISHMENT OF DATES THAT SUPPORT THE CONDUCT OF THE EXERCISE AND UNIT WHITE SPACE TRAINING. l.C. (U) SUBJECTS TO BE COVERED DURING THE SPECIAL DOT: l.C.1. (U) PAX DEPLOYMENT PLANNING l.C.l.A (U) ADVON DEPLOYMENT DATES l.C.1.B. (U) MAIN BODY DEPLOYMENT DATES l.C.2. (U) PAX REDEPLOYMENT PLANNING l.C.2.A. (U) ADVON REDEPLOYMENT DATES l.C.2.B. (U) MAIN BODY REDEPLOYMENT DATES l.C.3. (U) CARGO DEPLOYMENT PLANNING l.C.3.A. (U) DEPLOYMENT OF HAZARDOUS AND OVERSIZE CARGO l.C.3.B. (U) CARGO DEPLOYMENT DATES 1.C.4. (U) CARGO REDEPLOYMENT PLANNING l.C.4.A. (U) REDEPLOYMENT OF HAZARDOUS AND OVERSIZE CARGO

F-1 Enclosure (1)

l.C.4.B. (U) CARGO REDEPLOYMENT DATES 2. (U) PLANNING DATES (THESE SHALL BE CONFIRMED DURING THE SPECIAL DOT AND SHALL BE PUBLISHED VIA SEPCOR): 2.A. (U) II MEF PUBLISHES AN EXERCISE TASKING MESSAGE/DEPORD (TBD BUT PRIOR TO TPFDD LOI PUBLICATION) 2.B. (U) II MEF PUBLISHES THE TPFDD LOI FOR ITX 3-13: 08 MAR 2.C. (U) SPECIAL MEETING OF THE DOT: 22 MAR 2.D. (U) FIRST EQUIPMENT ARRIVES: 02 MAY 13 2.E. (U) ADVON PAX ARRIVE 30 APR - 01 MAY 13 2.F. (U) RSOI: 02-09 MAY 13 2.G. (U) MAIN BODY PAX ARRIVE: 06-09 MAY 2.H. (U) EXERCISE COMMENCES: 10 MAY 2.I. (U) EXERCISE CONCLUDES: 07 JUN 3. (U) II MEF G-4/MMCC DATA SUBMISSION REQUIREMENTS. 3.A. (U) DEPLOYMENT DATA (MDSS II AND TMR'S) SUBMISSION TIMLINES MUST BE ADHERED TO IOT MAXIMIZE THE USE OF AIRLIFT AND GROUND TRANSPORTATION ASSETS AT MINIMAL COST. FOR ALL REQUIREMENTS BELOW, THE DESIRED DATE OF MOVEMENT SHALL BE REFERED TO AS THE AVAILABLE TO LOAD DATE (ALD). 3.B. (U) II MEF G-4 SUBMITS REQUEST FOR GOPAX FLIGHTS: NLT 10 WORKING DAYS PRIOR TO ALD. 3.C. (U) UNIT SUBMITS TMR TO MMCC OVERSIZE CARGO: NLT 20 WORKING DAYS PRIOR TO ALO. 3.D. (U) UNIT SUBMITS TMR TO MMCC FOR BONDED CARGO: NLT 10 WORKING DAYS PRIOR TO ALD. 3.E. (U) UNIT SUBMITS TMR TO MMCC FOR NON-BONDED CARGO: NLT 5 WORKING DAYS PRIOR TO ALD. 3.F. (U) UNIT SUBMITS TMR TO MMCC FOR BUSES: NLT 5 WORKING DAYS PRIOR TO ALD. 4. (U) DECISIONS THAT ARE TBD BASED UPON AN ONGOING II MEF OPT. DECISIONS REGARDING THE BELOW TIMELINES SHALL BE PUBLISHED VIA SEPCOR. 4.A. (U) REQUEST TO DEPLOY CARGO IN EXCESS OF THE EEAP EDL: TBD BY MSC G3/G-4 4.B. (U) REQUEST TO DEPLOY ADDITIONAL PAX: TBD BY MSC G-3 4.C. (U) REQUEST TO DEPLOY ADDITIONAL UNITS: TBD BY MSC G-3 4.D. (U) AUTHORIZATION TO DEPLOY CARGO IN EXCESS OF THE EEAP EDL: TBD BY II MEF G3/G-4 4.E. (U) AUTHORIZATION TO DEPLOY ADDITIONAL PAX: TBD BY II MEF G-3 4.F. (U) AUTHORIZATION TO DEPLOY ADDITIONAL UNITS: TBD BY II MEF G-3 5. (U) USE OF JOPES. 5.A. (U) THE USE OF JOPES IS DIRECTED FOR THIS DEPLOYMENT. FURTHER GUIDANCE SHALL BE RELEASED VIA SEPCOR. 5.A.l. (U) TPFDD VERIFICATION TO II MEF FOR ADVON PAX: 02 APR 13 5.A.2. (U) TPFDD VERIFICATION TO II MEF FOR CARGO: 04 APR 13 5.A.3. (U) TPFDD VERIFICATION TO II MEF FOR MAIN BODY: 08 APR 13 5.B. (U) MDSS II DATA IS DUE TO II MEF G-4 04 APR 13 (CONCURRENLTY WITH THE TPFDD).

F-2 Enclosure (1)

5.C. (U) THE TPFDD AND MDSS II DATA SHALL MATCH PRIOR TO VERIFICATION OF PAX AND CARGO. 5.D. (U) THE TMR SHALL MATCH THE TPFDD AND MDSS II DATA PRIOR TO MMCC COORDINATING THE TRANSPORTATION OF PAX AND CARGO. 6. (U) FACTORS TO CONSIDER IN PLANNING: 6.A. (U} UNITS ARE REQUIRED TO SUBMIT TMR'S FOR BUS MOVEMENTS FROM ORIGIN TO APOE. 6.B. (U} UNITS ARE REQUIRED TO SUBMIT TMR'S FOR BUS MOVEMENTS FROM FROM APOD TO DESTINATION.

F-3 Enclosure (1)

ANNEX G

EXAMPLE OF THE MESSAGE TO PUBLISH THE RESULTS OF THE SPECIAL MEETING OF THE DEPLOYMENT OPERATIONS TEAM

****************UNCLASSIFIED/**************** RESULTS OF THE SPECIAL DEPLOYMENT OPERATIONS TEAM (DOT) MEETING FOR CLB-6 OFT TO FORT PICKETT 17-16 MAR 2013 Originator: CG II MEF G3(UC) DTG: 061628Z Feb 13 Precedence: Routine DAC: FOUO To: CG 2ND MAW G3(UC) CG 20 MLG G3(UC) CC: CG 2ND MAW G4(UC) CG 20 MLG G4(UC) CG II MEF G3(UC) CG II MEF(UC) More ... UNCLASSIFIED//FOR OFFICIAL USE ONLY UNCLASSIFIED//FOR OFFICIAL USE ONLY// POC/HAMER/GS-13/CG II MEF G-3/COPS FDP&E/TEL: DSN 751-8860/COML: 910-451-8860/EMAIL: AARON.T.HAMER@USMC.MIL// POC/SWINK, R.D./GSll/MMCC DIRECTOR/-/TEL: COM 910-451-4690/ TEL: CELL 910-467-4189/ EMAIL: DALE.SWINK@USMC.MIL// RMKS/1. (U) OVERVIEW. THE PURPOSE OF THIS MESSAGE IS TO ANNOUNCE THE FORCE DEPLOYMENT PLANNING REVIEW CONDUCTED FOR CLB-6'S OFT TO FORT PICKET 17-26 MAR 2013. l.A. (U) A SPECIAL DOT MEETING WAS HELD ON 05 JAN 2013 AT 1030 IN THE II MEF G-3 FDP&E CONFERENCE ROOM. IN ATTENDANCE WERE THE II MEF FORCE DEPLOYMENT OFFICER (MR. AARON T. HAMER), II MEF MMCC DIRECTOR(MR. DALE SWINK), 20 MLG PLANS (GYSGT SCOTT ROBBINS), 20 MLG G-3 EMBARK (CW03 JARED ELLIS), AND CLB-6 (CAPT JASON MOORE). 2. (U) PAX PLANNING FACTORS. 2.A. (U) THE FOLLOWING PAX DEPLOYMENT PLANNING DATES WERE PRESENTED BY 20 MLG AND CLB-6 2.A.1 (U) EXERCISE DATES: 17-26 MAR 2.A.2. (U) 15 MAR: ADVON DEPLOYS VIA 2.A.3. (U) 17 MAR: MAIN BODY DEPLOYS PAX VIA COMM BUS 2.A.4. (U) 17 MAR: MAIN BODY DEPLOYS PAX VIA KC-130 2.A.4. (U) 17 MAR: 2 X TACTICAL CONVOYS DEPLOYS 2.B. (U) THE FOLLOWING DEPLOYMENT PAX COUNTS WERE PRESENTED BY 20 MLG AND CLB-6 2.B.1. (U) TOTAL OF 25 CLB-6 ADVON PAX DEPLOYING VIA COMM BUS 2.B.2. (U) TOTAL OF 476 CLB-6 MB PAX DEPLOYING VIA COMM BUS 2.B.3. (U) TOTAL OF 90 MFR MB PAX DEPLOYING VIA COMM BUS 2.B.4. (U) TOTAL OF 159 MFR MB PAX DEPLOYING VIA KC-130 2.B.4.A. (U) THE PRO'S AND CON'S OF REQUESTING KC-130'S TO DEPLOY TO FORT PICKETT WERE DISCUSSED. 20 MLG AND CLB-6 STATED THAT THE COMMANDER'S DESIRE WAS TO REQUEST MOVEMENT VIA KC-130 DUE TO THE CONSTRICTED TIMELINE FOR THE MFR PERSONNEL TO COMPLETE CHECK-IN AND PREPARATION FOR DEPLOYMENT. 2.B.4.B. (U) THE AVAILABILITY OF KC-130'S TO SPT THIS DEPLOYMENT IS UNKNOWN AT THIS TIME. 2.B.4.C. (U) LIMITED AVAILABILITY OF COMMERCIAL BUSES DURING THE MONTHS OF MARCH THROUGH MAY (SPRING BREAK SEASON) WAS IDENTIFIED

G-2 Enclosure (1)

BY THE MMCC DIRECTOR. BECAUSE OF THE LIMITED AVAILABILITY DURING THIS TIME OF YEAR, THE COST OF BUSES REQUESTED ON A CONSTRICTED TIMELINE HAS THE POTENTIAL FOR SIGNIFICANTLY INCREASED COST AND REAL POTENTIAL FOR NON-SUPPORT. THE FORCE DEPLOYMENT OFFICER AND MMCC DIRECTOR ADVISED CLB-6 TO DISCUSS THE PLAN FOR UTILIZING KC-130'S FOR DEPLOYMENT AND HAVE A DECISION MADE PRIOR TO VERIFICATION OF THE TPFDD. 2.B.5. (U) TOTAL OF 100 CLB-6 PAX DEPLOYING VIA TACTICAL CONVOY 2.C. (U) REDEPLOYMENT PAX PLANNING DATES 2.C.1. {U) THE FOLLOWING REDEPLOYMENT PLANNING DATES WERE PRESENTED 2D MLG AND CLB-6 2.C.l.A. (U) 26 MAR: CLB-6 MAIN BODY PAX REDEPLOYS VIA COMM BUS 2.C.l.B. (U) 26 MAR: MFR MAIN BODY PAX REDEPLOYS VIA COMM BUS 2.C.l.C. (U) 27 MAR: REAR PARTY REDEPLOYS VIA COMM BUS 2.C.2. (U) THE FOLLOWING REDEPLOYMENT PAX COUNTS WERE PRESENTED 2D MLG AND CLB-6 2.C.2.A. {U) TOTAL OF 476 CLB-6 MB PAX REDEPLOYING VIA COMM BUS 2.C.2.B. {U) TOTAL OF 259 MFR PAX REDEPLOYING VIA COMM BUS 2.C.2.C. {U) TOTAL OF 100 CLB-6 PAX REDEPLOYING VIA TACTICAL CONVOY 2.C.2.D. (U) TOTAL OF 20 CLB-6 REAR PARTY PAX REDEPLOYING VIA COMM BUS 3. (U) BUS PLANNING FACTORS. SUBMITTED TO THE MEF MMCC NLT PICK UP DATE. 4. (U) CARGO PLANNING FACTORS.

BUS REQUESTS ARE REQUIRED TO BE 5 WORKING DAYS PRIOR TO REQUESTED

4.A. (U) 01 MAR: TMR'S FOR OVERSIZE AND BONDED CARGO ARE DUE TO MMCC. THESE ARE REQUIRED TO BE SUBMITTED TO THE MEF MMCC NLT 10 WORKING DAYS PRIOR TO THE REQUESTED PICK UP DATE. 4.A.1. (U) 15 MAR: OVERSIZE CARGO PICK UP AT CLNC 4.A.2. (U) 15 MAR: OVERSIZE CARGO DELIVERY AT FT PICKET 4.B. (U) IT WAS CONFIRMED THAT THERE SHALL NOT BE A REQUIREMENT TO TRANSPORT BONDED CARGO. IF BONDED CARGO IS IDENTIFIED AND REQUIRES COMM TRANSPORT, TMR'S ARE DUE TO MMCC NLT 10 DAYS PRIOR TO THE REQUESTED PICK UP DATE. 4.C. (U) 08 MAR: NON-BONDED/NON-OVERSIZE CARGO TMR'S ARE DUE TO MMCC 5. (U) CONVOY PLANNING FACTORS: ORGANIC SURFACE MOVEMENTS: CLB-6 PLANS TO CONVOY ON SUNDAY, 17 MAR. THERE ARE DEPARTMENT OF TRANSPORTATION (DOT) RESTRICTIONS REGARDING THE MOVEMENT OF OVERSIZE CARGO ON WEEKENDS AND HOLIDAYS AND TIME OF DAY RESTRICTIONS AS WELL (OVERSIZE CARGO CANNOT MOVE BEFORE SUNRISE OR AFTER SUNSET). AS THIS REQUIRES COORDINATION WITH BOTH THE NC AND VA DOTS THE MMCC REQUIRES AMPLE LEAD TIME. 6.B. (U) 15 FEB: DD FORM 1265 (REQUEST FOR CONVOY CLEARANCE) AND DD FORM 1266 (REQUEST FOR SPECIAL HAULING PERMIT FOR OVERSIZE VEHICLES AND VEHICLE AND LOAD COMBINATIONS) ARE REQUIRED TO BE SUBMITTED TO THE MEF MMCC VIA EMAIL TO THE SMB AT IIMEF MMCC@USMC.MIL. 6. (U) USE OF JOPES. 6.A. (U) THE USE OF JOPES IS DIRECTED FOR THIS DEPLOYMENT.

G-3 Enclosure (1)

6.B. (U) TPFDD VERIFICATION IS DUE TO II MEF 15 FEB. 6.C. (U) MDSS II DATA IS DUE TO II MEF G-4 15 FEB (CONCURRENLTY WITH THE TPFDD). 6.D. (U) THE TPFDD AND MDSS II DATA MUST MATCH PRIOR TO THE COORDINATION OF PAX AND CARGO MOVEMENTS. 6.E. (U) JOPES GUIDANCE WAS RELEASED VIA SEPCOR (SIPR NEWSGROUP) ON 29 JAN. THE GUIDANCE WAS BASED ON CLB-6 CONOPS SUBMITTED TO II MEF VIA NIPR AMHS ON 242030Z JAN. 7. (U) OTHER ISSUES IDENTIFIED. 7.A. (U) MFR PAX MAY ADJUST. CLB-6 STATED THAT THEY MAY NOT HAVE ACCURATE PAX COUNTS UNTIL MFR PAX COMMENCE ILOC. 7.B. (U) THIS DFT WAS IDENTIFIED AS A PTP CERTIFICATION TRAINING EVENT. IF MFR PAX DO NOT ATTEND THIS TRAINING, BUT CHECK-IN PRIOR TO DEPLOYMENT TO OEF, IT SHALL BE REQUIRED TO ADDRESS THE PTP TRAINING CERTIFICATION FOR THOSE PAX.

G-4 Enclosure (1)

ANNEX H

EXAMPLE OF CONOPS ****************UNCLASSIFIED/**************** 10TH MARINES ROLLING THUNDER 2-13 CONOPS Originator: CG 2ND MARDIV G3(UC) DTG: 241828Z Jan 13 Precedence: Routine DAC: General To: CG II MEF G3(UC} CC: 10TH MAR(UC) CG 2D MLG G3(UC} CG 2ND MARDIV COMPT(UC) CG 2ND MARDIV Gl(UC} CG 2ND MARDIV G3(UC) CG 2ND MARDIV G4(UC) CG 2ND MARDIV G6(UC} CG II MEF G4(UC) More ... UNCLASSIFIED/ MSGID/GENADMIN/CG 2D MARDIV G3/JAN 13// REF/A/DOC/CMC/15MAR07// REF/B/MSG/CG II MEF/170023ZMAY06// REF/C/MSG/CG II MEF/182302ZSEP08// REF/D/D0C/CMC/26SEP03// REF/E/DOC/JREGTO 3570.1D/15NOV11// NARR/REF A IS NAVMC 3500.7A ARTILLERY TRAINING AND READINESS MANUAL. REF BIS MOD TO CG II MEF OIF/OEF PTP GUIDANCE. REF C IS CG II MEF POLICY FOR THE USE OF ESTABLISHED JOPES PROCEDURES FOR II MEF DEPLOYMENTS, REDEPLOYMENTS, AND ROTATIONS. REF DIS OPNAVINST 5530.13C DON PHYSICAL SECURITY INSTRUCTION FOR CONVENTIONAL ARMS, AMMUNITION, AND EXPLOSIVES. REF EIS THE MARINE CORPS ARTILLERY SAFETY STANDING OPERATING PROCEDURES// POC/G.L. BENSON/MAJ/lOTH MARINES S3/TEL: DSN 751-6980/ EMAIL: GARRETT.BENSON@USMC.MIL// POC/J.T.WHITLEY/MGYSGT/lOTH MARINES S3C/TEL: DSN 751-3531/ EMAIL: JAMES.T.WHITLEY@USMC.MIL// 1. SITUATION l.A. GENERAL l.A.1. SUBMITTING UNIT: 10TH MARINES, 2D MARDIV. 1.A.2. SUBMITTING UNIT LOC: CLNC. l.A.3. INCLUSIVE EXERCISE DATES: 7 - 29 MARCH 2013. l.A.4. NAME/TITLE OF DEPLOYMENT FOR TRAINING: EXERCISE ROLLING THUNDER (RT} 2-13. l.A.5. LOCATION OF DEPLOYMENT FOR TRAINING: FT BRAGG, NC (FBNC}. l.A.6. BACKGROUND INFO: 10TH MARINES CONTINUES TO PROVIDE FORCES ISO MCO. CONCURRENTLY, THE REGIMENT SHALL CONDUCT SUSTAINMENT TRAINING OF THE M777A2, M327 EFSS, AND DEVELOP PROFICIENCY WITH THE REGIMENT'S UOC. EXERCISE ROLLING THUNDER SHALL FOCUS ON PRIMARY FIRE SUPPORT METS AND AFFORD THE REGIMENTAL AND BATTALION STAFFS AN OPPORTUNITY TO PLAN AND EXECUTE STAFF FUNCTIONS NOT ASSOCIATED WITH HOME STATION TRAINING. l.B. THREAT/RISK l.B.1. TERRORIST THREAT. DIA ASSESSES THE TERRORISM THREAT TO U.S. MILITARY INTERESTS IN THE UNITED STATES AS SIGNIFICANT. DEFINITION: ANTI-U.S. TERRORISTS MAY BE PRESENT IN COUNTRY AND

H-1

ATTACK PERSONNEL AS THEIR PREFERRED METHOD OF OPERATION, OR A GROUP USES LARGE CASUALTY PRODUCING ATTACKS AS THEIR PREFERRED METHOD, BUT HAS LIMITED OPERATIONAL ACTIVITY. THE OPERATING ENVIRONMENT IS NEUTRAL. l.B.2. DETAILED THREAT INFO IS AVAL VIA SIPRNET AT WWW.DIA.SMIL.MIL, WWW.NCIS.NAVY.SMIL.MIL AND WWW.ACIC.NORTH­INSCOM.ARMY.SMIL.MIL. l.C. FRIENDLY FORCES l.C.l. FORCE-LIST OF UNITS PARTICIPATING IN DEPLOYMENT FOR TRAINING: l.C.l.A. 10TH MARINES (-) l.C.l.B. 1ST BATTALION, 10TH MARINES (-). l.C.l.C. 2D BATTALION, 10TH MARINES (-). l.C.l.D. HEADQUARTERS BATTERY, 10TH MARINES (-). l.C.l.E. SUPPORT DETACHMENT, 2D SUPPLY BATTALION, CLR-25. l.C.2. DESIGNATED OFFICER CONDUCTING EXERCISE (OCE): COL B.L. HALL, COMMANDING OFFICER, 10TH MARINE REGIMENT. 2. MISSION. 10TH MARINES(-) DEPLOYS TO FT BRAGG, NC, ON 7 MARCH 2012 IN ORDER TO EXERCISE ITS ABILITY TO DISRUPT, DESTROY, OR NEUTRALIZE THE ENEMY BY CLOSE, CONTINUOUS, ACCURATE, TIMELY, MASSED CANNON AND EFSS FIRES, PROVIDE FIRE SUPPORT PLANNING AND COORDINATION IN SUPPORT OF 2D MARDIV. 3. EXECUTION 3.A. COMMANDERS INTENT 3.A.l. PURPOSE. THE PURPOSE OF RT 2-13 SHALL BE TO REINFORCE 10TH MARINES ABILITY TO CONDUCT ARTILLERY OPERATIONS BY TRAINING TOWARD CORE MISSION ESSENTIAL TASKS. THE REGIMENT SHALL FOCUS ON CONDUCTING TIMELY AND ACCURATE INDIRECT FIRES AND PROVIDING OVERALL COMMAND AND CONTROL TO INCLUDE COORDINATING A DAY/NIGHT REGIMENTAL MOVEMENT OF ALL ELEMENTS. SPECIFICALLY, THE REGIMENT SHALL HONE BATTERY EMPLACEMENT TIMES THAT ENSURE AN ACTUAL REAL TIME RAPID FIRING CAPABILITY UPON OCCUPATION AND EXPLOIT THE FULL CAPABILITIES OF THE UOC. 3.A.2. METHOD. CONDUCT TRAINING IAW T&R STANDARDS, REF (A), AND SAFETY STANDARDS, REF (E). DEVELOP FIRE PLANS TO EVALUATE THE REGIMENT'S ABILITY TO PROVIDE TIMELY AND ACCURATE FIRES. EVALUATE CANNON BATTERY OCCUPATIONS AND ENSURE THEY ARE PREPARED TO CONDUCT ACTUAL FIRE MISSIONS WITHIN T&R STANDARDS WITH SAFETY INCLUSIVE. ESTABLISH AND PROVIDE CSS IN ALL FUNCTIONAL AREAS VIA REGIMENTAL TRAINS AND EXTERNAL SUPPORTING AGENCIES. MOVE THE REGIMENTAL COMMAND POST (CP) AND PASS CONTROL TO THE ALTERNATE CP. ESTABLISH REMAIN BEHIND ELEMENT (RBE) IN CAMP LEJEUNE TO PROVIDE SUPPORT FUNCTIONS AND CONTINUE FORCE GENERATION SUPPORT. 3.A.3. ENDSTATE. THE REGIMENT TRAINED IN ITS CORE METS WITH SHORTFALLS IN TRAINING AND EQUIPMENT IDENTIFIED. LEADERSHIP PREPARED TO ADVANCE ARTILLERY OPERATIONS TO SUPPORT ACROSS THE RANGE OF MILITARY OPERATIONS. RT 2-13 SHALL END WITH THE

H-2

REGIMENT SAFELY RE-DEPLOYING ALL MARINES, SAILORS, WEAPONS, GEAR AND CLASSIFIED MATERIALS TO CAMP LEJEUNE. 3.C. TASKS TO EXERCISE UNITS 3.C.l. CONDUCT PLANNING AND PREPARATION FOR MOVEMENT TO FT BRAGG, NC IAW REF (C) . 3.C.2. PLAN, COORDINATE, AND EXECUTE INDIRECT FIRE SUPPORT

REF (A) . 3.C.3. PLAN, COORDINATE, AND EXECUTE LOGISTIC SUPPORT.

3.C.4. PLAN, COORDINATE, AND EXECUTE COMMAND AND CONTROL.

3.C.5. PLAN, COORDINATE, AND EXECUTE PTP TRAINING IAW REF

REQUIRED. 3. D. COORDINATING INSTRUCTIONS 3.D.l. TIMELINE 3.D.l.A. PHASE I: 3.D.l.B. PHASE II: 3.D.l.C. PHASE III:

ONGOING TO 0/A 06 MARCH. 07 MARCH TO 0/A 29 MARCH. 0/A 30 MARCH TO 08 APRIL.

IAW

(B)

3.D.2. SUBMIT MDSSII LEVEL IV DATA IAW REGT EMBARKATION SOP. 4. ADMIN AND LOG 4 .A. ADMIN 4.B. LOG 4.B.l. ALL MOVEMENT TO/FROM FT BRAGG SHALL BE ACCOMPLISHED VIA GROUND TRANS. LOGISTICAL SPT BEYOND ORGANIC MEANS IS PROVIDED BY GME AND/OR COMMERCIALLY-LEASED VEHICLES, OR VIA CONTRACTED SPT. CONVOY SERIAL MOVEMENTS TO AND FROM FT BRAGG FROM 7 - 29 MARCH SHALL BE COORD BY 10TH MARINES S-4 THROUGH 2D MARDIV G-4 AND II MEF LMCC. 4.B.2. REQUEST SUPPORT FROM CLNC TMO TO COORD COMMERCIAL TRANS OF REGIMENTAL ASSETS (ENGINEER TRACKED VEHICLES) FROM/TO CLNC AND FT BRAGG. 4.B.3. BILLETING/MESSING/LOCAL TRANS 4.B.3.A. BILLETING. BILLETING AT FT BRAGG SHALL BE IN A FIELD ENVIRONMENT.

IF

4.B.3.B. MESSING. MESSING SHALL CONSIST OF A COMBINATION OF MEALS-READY-TO-EAT (MRE) AND TRAY RATIONS (TRAT). MEAL PLAN IS TRAT-MRE-TRAT. MEALS SHALL ALSO INCL SUPPLEMENTAL A RATIONS. 4.B.3.C. LOCAL TRANSPORTATION. BOTH TACTICAL AND GME/COMMERCIAL VEHICLES SHALL BE USED FOR LOCAL TRANSPORTATION. TACTICAL VEHICLES SHALL BE UTILIZED FOR TRNG AND LOG PURPOSES. GME AND/OR COMM-LEASED VEHICLES SHALL BE UTILIZED FOR ADMIN AND NON-TRNG RELATED TASKS. 4.B.4. FUNDING. FUNDING SHALL BE SUBMITTED TO THE DIV COMPTROLLERS OFFICE FOR APPROVAL. CURRENT ESTIMATED COST OF OFT IS $550,000.00. 4.B.5. WEAPONS. T/0 AND CREW SERVED WEAPONS SHALL BE TRANS VIA INDIV MARINES. MOVEMENT OF WEAPONS SHALL BE ACCOMPLISHED IAW REF D. 4.B.6. ASP. 10TH MARINES SHALL ESTABLISH A FIELD ASP AT FT BRAGG. 5. COMMAND AND SIGNAL

H-3

5.A. COMMAND. CO 10TH MARINES IS THE OCE. NO CHANGE TO ESTABLISHED CMD RELATIONSHIPS. 5.B. SIGNAL. 5.B.l. COMMANDING OFFICER: COL B.L. HALL 451-6977. 5.B.2. EXECUTIVE OFFICER: LTCOL D.W. LUCAS 451-6978. 5.B.3. OPERATIONS OFFICER: MAJ G.L. BENSON 451~6980. 5.B.4. OPERATIONS CHIEF: MGYSGT J.T. WHITLEY 451-3531. 5.B.5. LOGISTICS OFFICER: CAPT C. SHORE 450-8253. 5.B.6. LOGISTICS CHIEF: J.G. SCHMIDT 451-6984 5.B.7. COMMUNICATIONS OFFICER: MAJ A. PREBE 451-5659 5.B.8. COMMUNICATIONS CHIEF: MGYSGT J.P. ROBERTSON 451-7700//

H-4

ANNEX I

Example Endorsement Letter

From: Commanding Officer, ( 22d MEU)

3000 S-3 14 May 13

To: Commanding General, II Marine Expeditionary Force

Subj: COMMANDING OFFICER ENDORSEMENT TO CHANGE TIME-PHASED FORCE AND DEPLOYMENT DATA (TPFDD) FOR (22D MEU) DEPLOYING ISO (CRISIS RESPONSE SPMAGTF)

Ref: (a) NIPR AMHS MSG 29 1632Z 13 "Improving Force Deployment Planning and Execution (FDP&E) Efforts Across II MEF

(b) II MEF FDP&E SOP (DRAFT) 03 Apr 13

1. On (20 APR 2013), Commanding Officer, (22d MEU) confirmed the accuracy of the PAX and/or cargo planned for deployment.

2. On (20 APR 2013), Commanding Officer, (22d MEU) verified the accuracy of the PAX and/or cargo planned for deployment. This verification was submitted via SIPR newsgroup (200340ZAPR13).

3. There is a requirement to make a correction to the verified TPFDD. The requested changes are as follows.

Unit: ULN:

22D MEU H5AA1Cl

Verified STONS: 17.3 Requested change to STONS: 20

Operational justification for change: Additional weight represents communication servers and miscellaneous communication equipment that is required for the SPMAGTF forward operations. The delta in weight resulted from a failure to communicate and coordinate as to when the containers were to be weighed for the final time.

Corrective action to be taken for future deployment planning: Upon final weigh in all containers shall be locked, bonded, and controlled by the CE S4. Any additions or subtractions of equipment shall be coordinated across staff sections.

4. Point of contact in this matter is (SSgt Hernandez, A.A. adrian.a.hernandez@usmc.mil; 910.451.0404).

F. M. LAST

ANNEX J

Example of a Groups Operational Passenger System (GOPAX) Request Message

UNCLASSIFIED/ REF/A/DOC/MCO 3500.109/16JAN07// REF/B/DOC/MAWTS 1/092057Z JUL 14 // REF/C/MSG/MAWTS l/172119Z JUL 14 // REF/D/MSG/2ND MAW/282003Z JUL 14 // NARR/REF A IS THE USMC AVIATION WTTP. REF BIS THE WTI 1-15 PLANNING GUIDE AND CONFERENCE RESULTS. REF C IS THE WTI 1-15 EXTERNAL AIR SUPPORT REQUIREMENTS MESSAGE. REF DIS THE 2D MAW INITIAL PLANNING GUIDANCE MSG// POC/SMITH, A.J./CAPT/2D MAW G3 PLANS/DSN:582-4579/EMAIL: ANDREW.SMITH@USMC.MIL// POC/JONES, W.D./MAJ/2ND MAW G4 MOBILITY OFFICER/DSN:582-4847/EMAIL: WINSTON.JONES@USMC.MIL// RMKS/1. (U) THIS IS A COORDINATED G-3/G-4 MESSAGE. 2. (U} PER THE REFERENCES, 2ND MAW WILL DEPLOY MAIN BODY PERSONNEL ISO WTI 1-15. 3. (U) 2ND MAW REQUESTS THE FOLLOWING GOPAX FLIGHTS TO BE SUBMITTED, 3.A. (U) APOE/ICAO: MCAS CHERRY PT/KNKT APOD/ICAO: MCAS YUMA/KNYL DATE NAME PAX 24-27 AUG MAG 14, 2D MAW 5 24-27 AUG MAG 26, 2D MAW 5 24-27 AUG MACG 28, 2D MAW 16 24-27 AUG MAG 29, 2D MAW 20 24-27 AUG MAG 31, 2D MAW 9 TOTAL 55 NOTE: MAG-31 PERSONNEL WILL BUS TO MCAS 3.B. (U) APOE/ICAO: MCAS CHERRY PT/KNKT APOD/ICAO: MCAS YUMA/KNYL DATE NAME PAX 30AUG-1SEP MAG 14, 2D MAW 17 30AUG-1SEP MAG 26, 2D MAW 32 30AUG-1SEP MACG 28, 2D MAW 0 30AUG-1SEP MAG 29, 2DMAW 30 30AUG-1SEP MAG 31, 2D MAW 9 TOTAL 88 NOTE: MAG-31 PERSONNEL WILL BUS TO MCAS 3.C. {U) APOE/ICAO: MCAS CHERRY PT/KNKT APOD/ICAO: MCAS YUMA/KNYL DATE NAME PAX 6-8 SEP MAG 14, 2D MAW 87

J-1

CARGO ST 0.0 0.0 0.0 0.0 0.0 0.0

CHERRY POINT

CARGO ST 0.0 0.0 0.0 0.0 0.0 0.0

CHERRY POINT

CARGO ST 0.0

Enclosure (1)

6-8 SEP MAG 26, 2D MAW 45 00 6-8 SEP MACG 28, 2D 7 0.0 6-8 SEP MAG 29, 2D MAW 131 0.0 TOTAL 270 3.D. (U) APOE/ICAO: MCAS BEAUFORT/KNBC APOD/ICAO: MCAS YUMA/KNYL DATE NAME 6-8 SEP MAG 31, 2D

PAX MAW 45

CARGO ST 0.0

TOTAL 3.E. (U) APOE/ICAO: MCAS CHERRY APOD/ICAO: MCAS YUMA/KNYL DATE NAME 14-17 SEP MAG 26, 2D MAW 14-17 SEP MACG 28, 2D MAW 14-17 SEP MAG 29, 20 MAW 15-17 SEP MAG 14, 2D MAW TOTAL

45 PT/KNKT

PAX 3 7 8 139 157

o.o

CARGO ST 0.0 0.0 0.0 0.2

0.0 NOTE: REQUEST FLIGHT ON 16 SEP PER WTI REPORTING INSTRUCTIONS 3.F. (U) APOE/ICAO: MCAS CHERRY PT/KNKT APOD/ICAO: MCAS YUMA/KNYL DATE NAME PAX CARGO ST 19-21 SEP MACG 28, 20 MAW 86 0.0 TOTAL 86 0. 0 4. {U) FURTHER MOVEMENT REQUIREMENTS WILL BE REQUESTED VIA SEPCOR.//

J-2 Enclosure (1)