|
|
|
________________________________________________________________________________
FM 3-35.4
unique reports merging both requirements and scheduling information. The
JOPES Editing Tool (JET), a major application on GCCS, allows operators
and planners the ability to rapidly edit and analyze a TPFDD. The Joint
Flow and Analysis System for Transportation (JFAST), is a JOPES related
GTN application that allows planners to establish transportation feasibility
deployment data.
A-10. The GCCS provides a fused picture of the battlespace within a mod-
ern command, control, communications, and computers system capable of
meeting Warfighter needs into the 21st century. It incorporates the core
planning and assessment tools required by the combatant commanders and
their subordinate joint force commanders and meet the readiness support re-
quirements of the Services. GCCS is required to move the combatant com-
manders and subordinate joint force commanders joint command and control
support capability into the modern era of client/server architecture using
commercial, open systems standards for both commercial and government
off-the-shelf applications. The essential umbrella standards and unifying ap-
proach that GCCS brings to the ongoing DoD command, control, communica-
tions, computers, and intelligence system migration strategy for the Services
and agencies can successfully reduce the large number of systems in use to-
day.
GLOBAL COMMAND AND CONTROL SYSTEM-ARMY
A-11. The Global Command and Control System-Army (GCCS-A) is the
Army component system that directly supports implementation of the joint
GCCS and provides the echelons above corps (EAC) portion of the Army Bat-
tle Command and Control System. GCCS-A supports operations from peace
to war, including contingency and stability or support operations, and force
projection. It supports the Army component commands, combatant com-
manders, Army JTF commands and components, and HQDA. GCCS-Army is
tailored to Army-specific information management needs.
END-TO-END FORCE TRACKING
A-12. End-to-End Force Tracking (EEFT) is a GCCS-Army module that al-
lows the commander to visualize the flow of forces into a theater in accor-
dance with the TPFDD and to perform force tracking. This system is modeled
after the Standard Theater Army Command and Control System, an
USAEUR-unique command and control system.
GLOBAL DECISION SUPPORT SYSTEM
A-13. The Global Decision Support System (GDSS) is the worldwide com-
mand and control (C2) system for executing strategic lift and air refueling. It
contains essential information used to monitor and manage all operational
DoD air mobility missions in progress throughout the world. It provides
automated tools to track aircraft and aircrew movement.
A-4
_______________________________________________________________________________
Appendix A
COMBAT SERVICE SUPPORT CONTROL SYSTEM
A-14. The Combat Service Support Control System (CSSCS) provides force-
level commanders and planning staffs with an automated capability to gen-
erate a common picture of the battlefield, the CSS status, and courses of ac-
tion (COA) planning. The system products are tailored to the information
needs of the various force-level commanders. It facilitates the required data
flow from mobilization through deployment and redeployment to demobiliza-
tion.
A-15. Echelons Above Corps-Combat Service Support Control System
(EAC-CSSCS) applications will eventually be provided in the GCCS-Army.
They will provide commanders and planning staffs with automated capability
to generate a common picture of the battlefield, the CSS status, and COA
planning. EAC-CSSCS will also provide commanders and staffs with detailed
information on the mobilization, deployment, redeployment, and demobiliza-
tion status of specified units.
COMPUTERIZED MOVEMENTS PLANNING AND STATUS SYSTEM
A-16. Computerized Movements Planning and Status System (COMPASS)
is an Army command and control support system that uses evolving com-
puter technology with multiple system interfaces. It facilitates collection and
maintenance of UMD to support planning, strategic mobility analysis,
movement execution, and command and control for mobilization and deploy-
ment purposes. The Army uses the COMPASS to satisfy CINC, Army, and
joint staff UMD information requirements for deliberate, crisis action plan-
ning, strategic mobility analysis, and mobilization and deployment move-
ment execution. The COMPASS processed UMD is utilized within the
JOPES. The current COMPASS uses direct interfaces with the GCCS-Army,
Army Status of Operational Readiness and Training System (ASORTS), and
the Mobilization, Operations, Deployment, Employment and Execution Sys-
tem (MOB/ODEE), as its primary sources of unit movement data to satisfy
command information needs for deployment.
JOINT FORCE REQUIREMENTS GENERATOR
A-17. The Joint Force Requirements Generator (JFRG II) is an automated
computer-based planning tool designed to support the Services in the devel-
opment of both deliberate and crisis action plans. It supports tactical and
administrative planning by providing the following capabilities: import of
Service type unit characteristic (TUCHA) data, rapid force list creation, lift
analysis, TPFDD development/manipulation, and import/export to the
JOPES. JFRG II is an information system used to provide UDLs from units
through the Service’s logistics automation information systems (currently
TC-ACCIS for the Army and the Marine Air-Ground Task Force II system
(MAGTF II) for the Marine Corps) to JOPES.
WORLDWIDE PORT SYSTEM
A-18. The Worldwide Port System (WPS) is a single standard AIS desig-
nated to support the function of cargo documentation, accountability and
A-5
________________________________________________________________________________
FM 3-35.4
management at common user ocean terminals associated with MTMC, U.S.
Navy, USFORSCOM, active and USAR automated cargo documentation
detachments, transportation groups, battalions, and brigades. WPS supports
the operation of common user water terminals worldwide, during peacetime
and wartime operations. WPS automates the information management func-
tions of a military ocean port operation. It can document the import and ex-
port of military cargo and develop appropriate documentation. The WPS pro-
vides—
• The ability, at the ocean terminals, to document cargo moving through a
port (manifests, TCMDs, and customs documentation).
• The ability, at the ocean terminals, to account for and monitor the move-
ment of cargo through the port.
• The ability to supply terminal and regional commanders the information
necessary to manage the movement of ocean cargo.
• The ability to provide ITV information to other DoD systems.
• The ability to use GTN to supply ITV of unit equipment.
TRANSPORTATION COORDINATOR-AUTOMATED COMMAND AND
CONTROL INFORMATION SYSTEM
A-19. The Transportation Coordinator-Automated Command and Control
Information System (TC-ACCIS) is the current information management and
data communications system that Army units use to plan and execute de-
ployments. TC-ACCIS aids the processing of mobility requirements and the
flow of information to USTRANSCOM components. TC-ACCIS users include
commanders, ITOs, division transportation officers (DTOs), and unit move-
ment officers. TC-ACCIS is the United States Army's automated manage-
ment information system designed to support the deploying units and instal-
lation transportation offices in their efforts to provide timely and accurate
movement data to the joint deployment community. It has a direct interface
with FORSCOM’s COMPASS and through COMPASS to the JOPES. TC-
ACCIS also supplies information to the MTMC IBS for surface moves and to
the Logistics Support Activity's Logistical Intelligence File for in-transit and
total asset visibility of Army unit movements. TC-AIMS II will replace TC-
ACCIS as the primary interface for UMD data.
A-20. TC-ACCIS automates most transportation functions at the unit and
installation level. It supports the unit’s deployment mission by—
• Maintaining unit equipment lists.
• Maintaining UDLs.
• Preparing GBLs.
• Preparing vehicle load cards.
• Preparing vehicle/container packing lists.
• Preparing advanced TCMDs (DD Form 1384).
• Preparing convoy march tables.
• Preparing convoy clearance reports (DD Form 1265).
• Preparing special handling permits (DD Form 1266).
• Preparing unit equipment manifests.
• Preparing executable rail load plans.
A-6
_______________________________________________________________________________
Appendix A
• Maintaining blocking, bracing, packaging, crating and tie-down (BBPCT)
material requirements lists.
• Preparing rail load schedules.
• Interfacing with the AALPS.
TRANSPORTATION COORDINATORS' AUTOMATED INFORMATION
FOR MOVEMENT SYSTEM II
A-21. The Transportation Coordinators' Automated Information For Move-
ment System II (TC-AIMS II) will be the single DoD system supporting all
unit and non-unit installation deployments, redeployments, and retrograde
requirements, once fully fielded. TC-AIMS II interfaces with virtually all the
current and planned deployment support automated systems. It will be
fielded to units and installations worldwide and will perform two principal
functions: unit movement and ITO/transportation management office opera-
tions. Details on how TC-AIMS II will be employed by units will be in FM 4-
01.011 (55-65).
A-22. The TC-AIMS II program addresses a critical shortfall in the move-
ment of materiel and personnel in support of DoD transportation operations.
TC-AIMS II falls within the DoD mission area supporting mobility and
transportation of DoD personnel and cargo. TC-AIMS II provides UMOs, em-
barkation officers, ITOs and traffic management offices (TMOs) throughout
the DoD with a single, effective and efficient AIS to support transportation
management of unit movement, passengers, and cargo during day-to-day and
crisis operations within the DTS.
A-23. TC-AIMS II is the result of a joint effort of the U.S. armed forces and
the JPMO, headed by the U.S. Army as the executive agent. TC-AIMS II pro-
vides automated support to functions performed by UMOs and ITOs, who
previously used a variety of Service automated systems and manual proc-
esses. TC-AIMS II’s goal is to improve and expedite unit movements and
TCC actions, providing timely and accurate information for use at all joint
deployment community command levels in support of CONUS, OCONUS and
in-theater JRSO&I operations.
A-24. To support these wide-ranging missions, TC-AIMS II will be provided
to all installation transportation offices, nearly every battalion and separate
company, and almost all U.S. Army transportation units and staff elements.
Each of these organizations will use TC-AIMS II in the performance of both
daily operations and deployments. TC-AIMS is installed on Service-provided
hardware. It includes software and processes that support unit movement
and sustainment transportation functions, and it provides access to various
load-planning functions. These capabilities are available to the TC-AIMS II
user from a client/server network, or a stand-alone configuration, at the
unit/installation level. Whether in garrison or deployed using the ITV capa-
bility of GTN, decision makers at various command levels have the ability to
track and process data received from TC-AIMS II.
A-25. The Army’s goal for TC-AIMS II is to provide a system that supports
the information needs of deploying unit commanders and deployment man-
agers. TC-AIMS II will support these two key players in the Army’s critical
A-7
________________________________________________________________________________
FM 3-35.4
mission of deployment. Deploying commanders and their staff will use TC-
AIMS II to translate information about the mission into detailed and realistic
movement plans for the deployment. This translation occurs in a short time
frame—capturing the continual changes to available lift assets, mission de-
tails, and unit assets allocated to support the mission.
A-26. Deployment managers (acting for commanders) will use TC-AIMS II
to—
• Coordinate strategic lift missions via air and water.
• Schedule unit convoy movements.
• Schedule interrelated deployment events.
• Prepare load plans for vehicles, rail cars, aircraft or ships.
• Prepare DTR/Electronic Data Interchange (EDI) documentation.
• Account for equipment, personnel, and consumable supplies.
Deployment managers (acting for commanders) use TC-AIMS II for docu-
menting paper authorization to expend funds and validate services. This sys-
tem provides a common, accurate deployment picture to both elements and
includes software that has the ability to perform the following functions
when enabled by the appropriate permissions:
• Prepare load plans.
• Read/write AIT devices (for example, RF tags, MSLs, CACs).
• Order transport services.
• Coordinate convoy clearances.
• Produce passenger manifests (via interface with personnel management
systems and via manual means if interface not available).
• Account for the receipt and loading of unit equipment at marshal-
ling/assembly areas.
• Account for movement to ports of embarkation, unit loading on strategic
lift assets, reception at ports of debarkation, and onward movement to
staging areas and TAA.
• Create transportation control and movement document (TCMD) data.
• Create GBL and freight warrants.
• Manage the deployment schedule (planned versus actual event times).
A-27. Sharing information with both supporting and supported Army ele-
ments is an UMO responsibility usually considered an additional duty for the
officer or non-commissioned officer (NCO), rather than a documented unit
TOE position. TC-AIMS II provides the UMO with the integrated informa-
tion management tools needed to achieve success in this area. Functions that
the UMO accomplishes using TC-AIMS II include—
• Extracting unit personnel and equipment records from standard Army
systems.
• Preparing UDL identifying equipment, personnel and basic
load/sustainment items for deployment/movement.
A-8
_______________________________________________________________________________
Appendix A
• Planning convoy movements and proposing convoy routing for movement
to ports of embarkation.
• Preparing load plans and manifests for aircraft, rail, and barge move-
ments.
• Preparing individual vehicle load plans and generating approved load
cards for each vehicle.
• Creating DTR-approved shipping documentation, hazardous material
(HAZMAT) documentation and military shipment labels for all deploying
equipment.
• Preparing RF tags for major equipment items/containers.
• Developing an internal deployment schedule and recording deployment
events as they occur.
• Reporting unit-level deployment information to higher headquarters.
• Allowing merging of deployment information at higher headquarters
level.
• Requesting transport services from ITO or movement control personnel.
A-28. The basis of issue for TC-AIMS II hardware/software and AIT
reader/writer devices will be battalion and separate company level. The
headquarters and headquarters company/headquarters and headquarters
troop (HHC/HHT) at groups, regiments, brigades, and similar organizations
require the system to support the deployment of the headquarters elements.
Many units receive AIT devices in the form of reader/writers that support bar
code technology, RF tags, and optical memory cards. TC-AIMS II use com-
mercial off-the-shelf notebook computers to support the UMO mission. The
computers include Personal Computer Memory Card International Associa-
tion (PCMCIA) cards (PC cards) to support communications using modem
and connectivity to a local area network (LAN). The TC-AIMS II equipment
for separate companies and HHCs allocates to the Company Command Sec-
tions.
A-29. TC-AIMS II supports the UMO in managing deployment data, creat-
ing deployment plans and monitoring deployment status throughout all
phases of the deployment. The system supports daily operations in the instal-
lation and pre-deployment planning activities, actions needed to move the
unit increments to the POE or to exercise areas, and unit actions to move the
unit increments from the POD to the TAA. The TC-AIMS II notebook com-
puter gives UMOs the full capability on one system that they now must exe-
cute on separate AALPS and TC-ACCIS computers. The one system permits
the UMO to deploy the entire unit through multiple movements without hav-
ing to re-enter data for each new step in the deployment process.
A-30. The higher headquarters for a deploying unit provides guidance to
the deploying unit about the type mission it is to execute upon deployment.
Higher headquarters also provides guidance on the commander’s intent for
how that mission executes, and the factors considered in setting the deploy-
ment sequence/priorities. The headquarters staff develops, interprets and re-
lays this guidance and ensures it is followed. Although this discussion fo-
cuses on the operations officer (S3) and logistics officer (S4), it applies to the
entire staff. The headquarters is responsible for the successful deployment of
A-9
________________________________________________________________________________
FM 3-35.4
its subordinate units. While the headquarters itself may deploy, these actions
occur.
A-31. The staff elements served by TC-AIMS II deployment processing
software are the S3 and S4 staff. TC-AIMS II provide the tools to allow these
staff elements to—
• Accomplish the same tasks outlined for the battalion/separate company
UMO.
• Consolidate equipment/personnel and sustainment supply lists for all
subordinate and supporting units into a battalion, group, brigade, or task
force deployment plan.
• Review and direct changes to deployment plans created by subordi-
nate/task force units.
• Forward a consolidated battalion, group, brigade, task force or similar
deployment plan to the TC-AIMS II server at the division, COSCOM,
corps, or ITO where command/installation deployment managers can re-
view it, consolidate it with other plans, and procure transportation ser-
vices to execute the plans.
• Prepare a deployment schedule of events/flow table to use as a manage-
ment tool. The flow table establishes time frames for events to occur, re-
cord the times that events occur, and assess the deployment status.
• Receive TPFDD information from command/installation deployment
managers and record the information that completes the TPFDD.
• Maintain unclassified record copies of deployment plans for exercises and
contingencies. When the headquarters is alerted to deploy, review and
update these record copies to form a template for the deployment.
A-32. Each U.S. Army battalion and higher headquarters is required to re-
ceive TC-AIMS II software, two computers (S3 and S4), and AIT equipment.
The S3 staff is responsible for defining the deployable force and the se-
quence/priority for the deployment increments. This definition is an evolving
process, as more information is known about the mission parameters. The S3
staff must know what is happening with the deployment and must provide
new guidance approved by the commander when more is known about the
mission. The S4 staff is responsible for creating and executing a deployment
plan that meets the commander’s mission objectives. For complete success,
both the S3 and S4 staffs need to know the same things about the deploy-
ment at the same time.
AUTOMATED AIR LOAD PLANNING SYSTEM
A-33. The Automated Air Load Planning System (AALPS) is a computer-
ized system used to produce air manifests. UMOs, deployment planners, and
contingency planners/force designers use it to plan and execute air movement
as well as to design and analyze force packages. It operates with DEL data
from TC-ACCIS, (UDL data when AALPS is integrated with TC-AIMS), or in
a stand-alone configuration. AALPS can—
• Rapidly estimate airlift requirements for a given deployment list.
• Build, store, and maintain pre-planned contingency packages.
• Provide automated assistance to produce individual aircraft load plans.
A-10
_______________________________________________________________________________
Appendix A
A-34. AALPS allows military air load planners to quickly and efficiently es-
timate airlift requirements, plan force packages, and modify aircraft loads.
AALPS rapidly provides estimates of airlift requirements for a given list of
equipment and passengers and takes into account the unique loading re-
quirements for the delivery methods used on all U.S. military and Civil Re-
serve Air Fleet (CRAF) cargo aircraft. AALPS allows users to create and save
contingency force packages in advance of a mission. This saves time and
avoids input errors during deployment. The system has the capability to
print approved load plans as well as various load and movement reports.
AUTOMATED MOVEMENT FLOW TRACKING SYSTEM
A-35. The Automated Movement Flow Tracking System (AMFT) is an in-
stallation-level system that provides deploying unit commanders and staffs
with continuously updated deployment status. It provides a tool to plan
movements of unit equipment and personnel through the successive installa-
tion processing points to meet load-out schedules. AMFT provides the ability
to uniquely define critical deployment events, and timing parameters re-
quired by the installation in order to create schedules for critical movement,
coordination and notification events supporting large deployments and/or
daily missions. Through various system interfaces (AALPS, TC-AIMS-II, TC-
ACCIS and TPS), AMFT can also provide visibility of specific equipment and
personnel moving through the deployment process.
DEPARTMENT OF THE ARMY MOVEMENT MANAGEMENT SYSTEM
A-36. The Department of the Army Movements Management System
(DAMMS) Block III provides managers within the theater visibility of im-
port, export, and intra-theater cargo movements. It provides mode managers
asset accountability and asset visibility. Data provided to movement manag-
ers, mode operators, and materiel managers expedites the onward movement
of cargo and personnel.
A-37. The DAMMS Block II provides convoy planning and highway sched-
uling. DAMMS allows the user to create main supply routes (MSRs) and to
display map data in support of convoy planning and highway scheduling, us-
ing a Graphic Information System (GIS). Units create convoys and submit
requests for convoy clearance using the convoy planner. Requests are trans-
mitted to a highway scheduler for de-conflicting, scheduling, and approval.
TC-AIMS II shares the information.
JOINT FLOW AND ANALYSIS SYSTEM FOR TRANSPORTATION
A-38. The Joint Flow and Analysis for Transportation (JFAST) is a per-
sonal computer (PC)-based analysis tool for estimating transportation flows
of deployment/redeployment. JFAST provides a means of performing COA
development and analysis of deliberate planning, exercise, and real-world
transportation problems.
A-11
________________________________________________________________________________
FM 3-35.4
INTEGRATED COMPUTERIZED DEPLOYMENT SYSTEM
A-39. The Integrated Computerized Deployment System (ICODES) is a
shipload planning software application that uses artificial intelligence (AI)
principles and techniques to assist embarkation specialists in the rapid de-
velopment of cargo stow plans. It includes expert agents with knowledge in
specific domains (for example, hazardous material handling, trim and stabil-
ity, ramps, cranes, and internal access paths) to evaluate and propose loading
alternatives and recommendations. ICODES integrates with information
management and documentation systems such as WPS, TC-AIMS II, and IBS
to receive cargo lists and send completed load plans. IBS operates from a PC
and provides load-planning assistance to support deployment/redeployment
by vessel. The accuracy of ICODES depends on the accuracy of the UDL.
ICODES’ main functions are to calculate trim and stability; develop pre-stow
plans; prepare final stowage plans for cargo loading; develop load diagrams;
track cargo placement; prioritize discharge of cargo; and develop railcar, con-
tainer, and flatrack load plans.
INTEGRATED BOOKING SYSTEM
A-40. The Integrated Booking System (IBS) is the lead execution system of
the DTS for the booking of international surface cargo. The system supports
traffic management within MTMC, the greatest percentage of which is book-
ing non-unit peacetime cargo. IBS must also satisfy the MTMC mission to
execute the strategy developed in deliberate planning for international cargo.
In addition, the system is responsible for booking cargo during contingency
operations. IBS must respond to requirements of commodity managers and
war planners requiring continuous access to international surface cargo
movement. IBS is fielded to both CONUS and OCONUS booking locations. It
exchanges data with WPS and other systems. IBS consolidates the cargo
booking function into a single architecture and supports the function of book-
ing movement requirements for sealift against available ocean cargo vessels.
IBS supports the DTS in peace and wartime for deployments, redeployments,
and sustainment cargo bookings.
ENHANCED LOGISTICS INTRATHEATER SUPPORT TOOL
A-41. The Enhanced Logistics Intratheater Support Tool (ELIST) is a feasi-
bility planning and modeling system fielded by MTMC for deployment analy-
sis. The primary use of ELIST is to determine the feasibility of transporta-
tion options from the POD to the TAA. It analyzes effects of modernization
and new force structures and changes to the DTS.
CONUS FREIGHT MANAGEMENT SYSTEM
A-42. The CONUS Freight Management System (CFM) is a DoD freight
traffic management information system designed to provide a centralized da-
tabase of master reference files, freight tenders, domestic route order re-
quests, bill of lading shipment information, and carrier performance data.
The CFM interface provides timely accurate carrier costing data to the ITO
for bill of lading shipments. The CFM supports deployment, sustainment,
A-12
_______________________________________________________________________________
Appendix A
and redeployment operations by rating and routing cargo/freight to and from
ports in CONUS, and generating required movement documentation.
MOBILIZATION MOVEMENT CONTROL SYSTEM
A-43. The Mobilization Movement Control System (MOBCON) is a convoy
planning system, which schedules and coordinates convoys by allocating road
space. The system will interface with TC-AIMS II in the future. Deploying
units can use it to schedule and prioritize convoy movements over state
highways. The system can also assist units in identifying locations of military
support facilities along the convoy route.
GROUPS OPERATIONAL PASSENGER SYSTEM
A-44. The Groups Operational Passenger System (GOPAX) supports opera-
tional functions associated with arranging commercial group passenger
movement. The system aids in the timely movement of troops among CONUS
training bases, mobilization sites, APOEs, and destination APODs.
STANDARD INSTALLATION/DIVISION PERSONNEL SYSTEM 3
A-45. The Standard Installation/Division Personnel System 3 (SIDPERS-3)
provides a standardized personnel system for the Active Army in peacetime
and will support the total Army during mobilization, wartime, and demobili-
zation. SIDPERS-3 provides commanders and staffs at all levels with per-
sonnel information tailored to meet mission accomplishment needs. Included
in the system is a distributed processing capability, a relational database,
and a summary personnel interface to feed command and control systems.
SIDPERS-3 will also support personnel replacement operations. SIDPERS-3
is the primary system personnel managers use during deployments to focus
on—
• Accessing mobilizing USAR soldiers into the AC.
• Accounting for all assigned personnel.
• Reassigning non-deployable soldiers from deploying units and cross-
leveling personnel.
• Managing theater fillers and replacements.
A-46. SIDPERS-3 provides automated personnel service support for AC and
USAR soldiers. It supports strength accounting, personnel management, per-
sonnel actions, and exchange of information with other automated systems.
SIDPERS-3 is a tool commanders use to optimize allocation and use of per-
sonnel to meet peacetime, mobilization, and wartime personnel service re-
quirements.
STANDARD PROPERTY BOOK SYSTEM-REDESIGN
A-47. The Standard Property Book System-Redesign (SPBS-R), which is
migrating into a GCSS-Army module, is an automated system that provides
on-line management information and automated reporting procedures for
property book officers and produces company-level hand receipts. With TC-
AIMS II fielding, SPBS-R will interface and provide unit equipment list up-
date capability.
A-13
________________________________________________________________________________
FM 3-35.4
UNIT LEVEL LOGISTICS SYSTEM
A-48. The Unit Level Logistics System (ULLS) is an automated system that
processes PLL transactions into The Army Maintenance Management Sys-
tem and provides an automated interface with the Standard Army Retail
Supply System
(SARSS) and the Standard Army Maintenance System
(SAMS). ULLS will migrate into GCSS-Army and interface with TC-AIMS II
to support movement planning. The ULLS-S4 assists unit-level supply
rooms, as well as battalion and brigade level S4 staff sections in managing
logistics functions. It automates the supply property requests and other logis-
tical planning activities at various levels. These planning activities include
movement planning, unit load planning, movement requests, and movement
orders (MOs).
A-49. The ULLS-S4 interfaces with the SPBS-R and the Standard Army
Retail Supply System (SARSS). ULLS-S4 will migrate into GCSS-Army and
will interface with TC-AIMS II to support movement planning. It also re-
ceives and produces Army Materiel Status System (AMSS) reports generated
by ULLS-G systems or another ULLS-S4 system to provide commanders with
their equipment readiness status ad they prepare to deploy.
CARGO MOVEMENT OPERATION SYSTEM
A-50. The Cargo Movement Operation System (CMOS) is a combat support
system that automates and streamlines installation-level cargo movement
processes for both peacetime and deployment/contingency cargo. Work sta-
tions in ITO functional areas support one-time data capture for the prepara-
tion of documentation for all modes of shipment. The specific functional areas
supported are the receipt (inbound and outbound), preparation and move-
ment of cargo, the reporting of movement to command and control elements
for in-transit visibility (ITV), and military airlift passenger travel. The re-
ceipt function covers originating cargo destined for outbound shipment and
inbound cargo destined for local installation and onward movement. The
preparation function covers shipment planning, packing, packaging, and
preservation of material generated for the installation supply account or
other units for outbound movement. The movement function involves ship-
ment planning, loading cargo on the designated conveyance, generating the
required movement documentation, and furnishing movement data. The elec-
tronic reporting of cargo movement makes CMOS a vital component of the
logistics community's effort to provide in-transit asset visibility. Ultimately
the CMOS capabilities will migrate into TC-AIMS II and provide electronic
reporting of cargo movement at the installation level.
A-14
Appendix B
Time-Phased Force and Deployment Data Development
The TPFDD is the JOPES data-based portion of the operational plan; it contains
time-phased force data, non-unit related cargo and personnel data, and move-
ment data for the operational plan including:
•
In-place units.
•
Units to be deployed to support the operational plan with a priority indicating
the desired sequence for their arrival at the port of debarkation.
•
Routing of forces deployed.
•
Movement data associated with deploying forces.
•
Estimates of non-unit related cargo and personnel movements to be conducted
concurrently with the deployment of forces.
•
Estimates of transportation requirements, which are fulfilled by a common-user
lift resources, as well as those requirements that can be fulfilled by assigned or
attached transportation resources.
(Joint Pub 1-02)
B-1.
The Time-Phased Force and Deployment Data (TPFDD) is one of the
most vital elements of a major deployment. It is the database list of units and
sustainment requirements needed to execute the operation plan (OPLAN). It
phases them into the theater of operations at the times and places required
to support the concept of operations. Its development and refinement are
critical to achieving executable OPLANs and to developing executable opera-
tion orders when using an approved TPFDD in crisis action planning. The
TPFDD integrates force requirements, support requirements, and transpor-
tation requirements into a single process planning instrument. (For clarifica-
tion purposes, a TPFDL is the actual list generated by the TPFDD, when
queried).
B-2.
The supported combatant commander/JFC in coordination with the
Service component commands develop TPFDDs. The units necessary to meet
the required capabilities are provided by the force provider (any unified
commander providing forces to the JFC).
B-3.
Development of TPFDDs occurs through an iterative refinement
process. CJCS orders on behalf of the SECDEF provide the base documents
defining the approved forces to be sourced and entered in a TPFDD. The sup-
ported commander, in coordination with the supporting commander, defines
initial force requirements in terms of unit type codes (UTCs), unit line num-
bers (ULNs), and force modules. ULNs define a precise increment of capabil-
ity. The increments may be based on UTC, Service component (Army, Air
Force, and so forth) providing organization or time-phased data associated
with movement requirements. Force modules are groupings of ULNs used for
TPFDD analysis and force tracking. Typical force module categories include
B-1
________________________________________________________________________________
FM 3-35.4
force composition, functional composition (such as all medical units), geo-
graphical relationship (such as common POD), or time-phased relationships
(such as the latest arrival date (LAD)).
B-4.
Sourcing supported JFC TPFDD requirements begins as soon as sup-
porting commanders and Service chiefs identify specific units to satisfy them.
Normally, the first step is that supporting commanders source initial TPFDD
requirements upon receipt of the CJCS/supporting combatant commander’s
alert order, if there is one, prior to issuance of the deployment order. The de-
ployment order specifies a time for completing sourcing and requirements
validation. During the sourcing process, supporting commanders, normally
through their Service components, enter UICs, unit names, routing and time
phasing data associated with the origin and POE, tailored personnel and
cargo detailed information, and a unit POC.
B-5.
Periodically, during the TPFDD process, the supported commander
calls for a validation. Validation is an execution procedure used by combatant
command components, supporting combatant commanders, and providing or-
ganizations to confirm to the supported commander and USTRANSCOM that
all the information records in a TPFDD are error-free and accurately reflect
the current status, attributes, and availability of units and requirements.
The TPFDD elements scheduled for validation are normally those that fall
within a specific category, such as an echelons above division (EAD) range
(for airlift, sealift, or other surface movement). Supported command compo-
nent commanders review the ULNs within the specified range, and validate
those selected. Supported command component commanders coordinate with
supporting command counterparts to confirm that the ULNs are sourced,
that ULNs accurately reflect the current attributes and availability of each
force increment, that the force increments have been alerted for deployment,
and that the sourcing process has been coordinated with supported command
components. This process is frequent, as much as daily, during a deployment.
B-6.
Validation of the ULNs occur at the same time the supported com-
mander coordinates with air and sea lift providers to validate lift windows.
These validations are based on scheduling, contracting, lift positioning, and
execution timelines.
B-7.
As the time to move nears, and as more and more of the TPFDD re-
quirements become validated and “locked-in,” changes become ever more dis-
ruptive. Accordingly, changes to locked-in portions of the TPFDD must be
limited to those required to support operations or to respond to unforeseen
events. These changes normally fall into one of the following procedural cate-
gories:
• Changes that do not affect movement schedules generally correct ULN
information. They usually improve the accuracy of validated TPFDD in-
formation through minor adjustments to cargo or passenger information,
or they correct internal logic errors.
• Changes that require unlocking, correcting, and re-validating ULNs re-
quire significant effort. They must be coordinated with the supported
commander and specifically justified.
• Changes that affect movement schedules invalidate previously deter-
mined lift timelines. These changes are extremely disruptive, particu-
B-2
_______________________________________________________________________________
Appendix B
larly when they generate requirements for additional lift. Consideration
for approval of these changes occurs only when a component commander
identifies a clear, critical operational need. Justifications for these
changes usually require general/flag officer-level approval. (See CJCSM
3113.01A for more information on TPFDD development.)
B-3
Appendix C
Deployment Binders
In addition to the deployment SOP, units often prepare deployment bind-
ers for quick reference during deployments. These binders could contain,
but are not limited to:
•
Appointment orders and training certificates for unit movement officers
and alternates, load teams, and personnel qualified to certify hazardous
material.
•
A recall roster and instructions.
•
A listing of required references.
•
A list of major equipment shortage items.
•
A list of blocking, bracing, packing and crating materials (BBPCM), as
well as actions required to obtain materials not already on-hand.
•
A list of supplies by support activity, coordination requirements (lists of
personnel, transporting locations, and materials-handling equipment),
and prepared requisitions.
•
Coordination requirements for plan execution and a list of supporting
agencies and POCs.
•
A copy of the RSOP and extracts from the unit deployment plan detailing
initial actions to be taken during a deployment (the beginning of time cri-
sis planning (X-hour) and N-hour sequence).
•
A current copy of the OEL.
•
Copies of all load cards and container packing lists.
•
Prepared copies of transportation requests, convoy movement requests,
and special hauling permits.
•
Strip maps for each route of march the unit will take (see Appendix E for
convoy briefing outline).
•
Advance party composition and instructions.
•
Examples of forms required for personnel support during deployment (for
example, Adjutant General, Judge Advocate General, medical).
•
Transportation requirements for each mode (such as trucks or buses) that
are beyond the unit's organic transport capability. This includes POCs
and preplanned coordination channels for obtaining needed transport ca-
pability.
•
Rear detachment and family support group operations.
•
Other unit checklists or handbooks developed by the unit to assist in de-
ployment planning and execution.
•
Contact telephone numbers during off-duty hours for service organiza-
tions supporting deployment.
•
A list of trained rail load teams and air load teams.
C-1
________________________________________________________________________________
FM 3-35.4
• A list of individuals trained to sign HAZMAT documents.
• Prepared DA Form 2062 (Hand Receipt/Annex Number) for the issue of
small arms ammunition.
C-2
Appendix D
Deployment Planning
Effective deployment movement plans define responsibilities, functions,
and details for each part of a unit deployment from PPP/PSP to reception
in theater. They contain SOPs, OELs, and other annexes as directed by
the MACOM or the ASCC. Movement plans require substantial coordina-
tion and support from all levels in the chain of command. They incorpo-
rate lessons learned from previous moves and exercises that tested their
effectiveness. This appendix provides the unit deployment planner guid-
ance on developing a movement plan. The intent for TC-AIMS II is to
automate these functions. It broadens the operational movement planning
in Chapter 2. This section covers the UMO or UMNCO considerations
while the annexes discuss—
Annex 1 - Movement Planning Checklist
Annex 2 - Deployment Documentation Requirements
Annex 3 - Blocking, Bracing, Packing, Crating and Tie-down Materials
Following is a recommended process for developing deployment plans.
The following steps from FORSCOM/Army National Guard (ARNG) Regu-
lation 55-1 are generally applicable to all units with deployment missions.
Step 1. Identify what needs to be moved. Based upon mission require-
ments and command guidance, deployment planning must reflect per-
sonnel, equipment, and supplies to be deployed, and how the unit will ac-
complish the move.
Step 2. Identify equipment to accompany troops (TAT) (yellow TAT) and
equipment needed immediately upon arrival (red TAT). Yellow TAT must
accompany troops and be accessible en route. Examples include Class I
basic load items, unit records, and individual carry on baggage and weap-
ons. Red TAT must be available at the destination before or upon unit
arrival. This equipment may be sensitive cargo that requires special
security or handling at the POE or POD. Examples are individual bag-
gage, basic loads of supplies, and crew-served weapons.
Step 3. Identify hazardous cargo. Transport of HAZMAT requires proper
segregation, packing, marking and documentation. The HAZMAT Bulle-
tin Board System at http://www.afmc.wpafb.af.mil/Hazmat/ contains Air
Force Joint Manual (AFJM) 24-204 (TM 38-250), Preparing Hazardous
Materials for Military Air Shipments and other helpful HAZMAT site
links to include the Code of Federal Regulations (CFR) 49 - Transporta-
tion. If not available locally, the International Air Transportation Asso-
ciation (IATA) Dangerous Goods Regulation, the North American Emer-
D-1
________________________________________________________________________________
FM 3-35.4
gency Response Guidebook, and the International Maritime Dangerous
Goods (IMDG) Code may be purchased from: LableMaster, 5724 N. Pu-
laski Road, Chicago, IL 60646.
Step 4. Identify bulk cargo that needs to be moved and develop packing
lists. All consolidated cargo (boxed, crated, etc.) loaded in vehicles, con-
tainers, and on 463L pallets must display a separate packing list that
shows complete contents. A Department of Defense (DD) Form 1750 (Pac-
king List) or DA Form 5748-R (Shipment Unit Packing List and Load
Diagram), Packing List documents contents.
Step 5. Develop vehicle load plans for unit equipment. Vehicle load plans
are recorded on DA Form 5748-R (Shipment Unit Packing List and Load
Diagram) for organic vehicles and trailers carrying secondary loads.
Step
6. Identify blocking, bracing, packing, crating, and tie-down
(BBPCT) requirements. All crates containers, boxes, barrels, and loose
equipment on a vehicle must be blocked, braced, and tied down to pre-
vent shifting during transit. The POC for blocking and bracing require-
ments is normally the ITO or the installation director of public works.
FM 55-9 provides guidance for securing loads moving by air, and FM 55-
17 provides guidance for securing loads by other modes. (NOTE: FM 55-9
and FM 55-17 are scheduled to be incorporated in FM 4-01.011, Unit
Movement Operations.) Vehicle Preparation Handbook for Fixed Wing
Air Movements is another excellent source document.
Step 7. Document and report unit deployment requirements. Personnel
and equipment data are translated into transportation terminology as
unit movement data and recorded on the OEL. Units use TC-AIMS II to
update the OEL and create the UDL.
Step 8. Determine how personnel and equipment will move to the POEs.
In CONUS wheeled vehicles normally convoy when distances are less
than one day drive (less than 400 miles) with tracked vehicles moving via
military heavy equipment transporters (HETs) or commercial rail, truck,
or inland waterway. Unit personnel usually move to the POE by organic
vehicles or by military or commercial buses. Army rotary wing aircraft
normally self-deploy to the POE.
Step 9. Prepare the unit deployment plan. The administrative, logistics
and coordination requirements for the plan must be determined. Items
such as en route medical, feeding, and maintenance for deployment to
POEs must be coordinated and documented.
Step 10. Maintain the deployment plan. This includes updating the OEL
as changes occur in OPLANs, CONPLANs, unit equipment or com-
mander's intent. Upon mission execution, actual equipment weights and
shipping configurations must also be updated. The updating of the OEL
within TC-AIMS II to produce the UDL is critical. From this data, the
unit's equipment manifest and military shipping labels are produced. Er-
rors can result in the unit’s equipment being frustrated or delayed at the
POE.
D-2
_______________________________________________________________________________
Appendix D
Annex 1
Movement Planning Checklist
This movement planning checklist was adapted from FORSCOM/ARNG
Regulation 55-1 (1 March 2000). It provides a representative example of
what to consider when planning a move. However, it is not all-inclusive.
For example, Appendix K contains DD Form 2133, which is used for joint
inspections, but is still part of the movement planning process. TC-ACCIS
is the Army’s source to assist in movement planning until the fielding of
TC-AIMS II.
D-3
________________________________________________________________________________
FM 3-35.4
COMMANDER’S (UMO) CHECKLIST
YES
NO
NA
1. Have a unit movement officer and alternate been appointed?
2. Does the unit have the required publications to support unit
movement planning?
Does the unit have an approved mobilization (USAR only) and
deployment (AC/RC) movement plan? (USAR
MSC/STARC/installation approved).
3. Has the unit movement plan been prepared in accordance with
FORSCOM/ARNG Regulation 55-1?
4. Has the unit movement officer reviewed unit plans to ensure that
they conform to directives of higher headquarters?
5. Does the unit have established procedures for the following:
a. Identifying, packaging, loading, certifying, and transporting
hazardous cargo?
b. Marking of vehicles for convoy movement?
c. Loading and unloading of vehicles before and after
movement?
d. Maintaining equipment during convoy movement?
6. Have SOPs been reviewed and staffed to ensure conformity
with regulations?
7. Does the unit movement plan address the following:
a. Movement of the advance detachment to the mobilization
station (MS)/POE, if required?
b. Movement of the main body?
c. Movement of MTOE/CTA equipment from
HS/MATES/UTES/WETS/ECS?
8. Does the unit have the most current OEL report data?
9. Have the appropriate local forms and DD Form 1750 been
completed for each loaded vehicle and trailer?
9. For units with equipment which cannot be transported
organically, has the appropriate local form been completed?
10. Have blocking BBPCT materials been considered, requirements
identified, sources identified, and coordination made with
USPFO/SI/MS?
11. Have unit load teams been identified and trained?
12. For units that convoy, have convoy requirements been
identified, appropriate coordination and forms complete?
13. Has the unit properly marked vehicles for convoy movement?
D-4
_______________________________________________________________________________
Appendix D
CONVOY COMMANDER’S CHECKLIST
YES
NO
NA
1. Has the unit properly marked vehicles for convoy movement?
2. Has BBPCT material been considered; requirements identified, sources
identified, and coordination made with the USPFO/SI/MS?
3. Has a reconnaissance of the approved route been made and a strip map
prepared?
4. Have overweight, oversize, or exceptionally slow vehicles been identified and
provisions made for their movement?
5. Is there a listing of contacts, either telephone numbers or addresses,
available along the route in case of incident or accident?
6. Are specific provisions made to preclude the carrying of passengers in the
last vehicle of an element?
7. Are convoy identifying signs available and in good repair?
8. Are trucks that are to carry personnel equipped with first aid kits?
9. Do vehicles that are required to operate at night have the "L" shaped
reflective symbol in the lower left corner of the tailgate?
10. Are flags (BLUE for lead vehicle, GREEN for trail vehicle, and BLACK and
WHITE for the convoy commander) available and in good order?
11. Does each vehicle of the proposed convoy contain a basic highway warning
kit appropriate for the vehicle?
12. Do vehicles transporting compressed gases, explosives, or flammables have
flashing lanterns in lieu of flares or fuses?
13. Have HAZMAT been packed, marked, and placarded according to law and
regulation?
14. Has a properly trained individual certified packing, marking, and placards of
HAZMAT items?
15. Have provisions been made to pay for toll roads, bridges, or others?
16. Have possible rest stops or break areas along the route been identified on
strip maps?
17. Is a comprehensive checklist for the convoy available?
18. Have provisions been made for inoperable vehicle recovery?
19. Has a start point been identified?
20. Has the release point been identified?
21. Has the convoy movement order been reviewed to determine the route?
22. Can bridges and defiles safely accommodate all loaded or tracked vehicles?
23. Are critical points known and listed on strip maps?
24. Has the size of march units been determined?
25. Has the rate of march on the convoy movement order been verified?
26. Has the vehicle interval on open road been determined?
D-5
________________________________________________________________________________
FM 3-35.4
CONVOY COMMANDER’S CHECKLIST
YES
NO
NA
27. Has the type of column been determined?
28. Have provisions been made for refueling, if required?
29. Has a suitable bivouac site been selected, if required?
30. Have convoy clearances been obtained, if required?
31. Is an escort required and has it been requested?
32. Are spare trucks available for emergencies?
33. Are vehicles fully serviced, clean, and ready for loading?
34. Are loads proper, neat, and balanced?
35. Are drivers properly briefed?
36. Is the convoy marked front and rear of each march unit?
37. Are guides in place?
38. Are blackout lights functioning?
39. Are maintenance services alerted?
40. Is maintenance truck in rear?
41. Are medics in rear?
42. Is there a plan for casualties?
43. Are all interested parties advised of the estimated time of arrival (ETA)?
44. Is officer at rear of convoy ready to take necessary corrective action such as
investigating accidents and unusual incidents, and changing loads?
45. Has a trail officer been identified?
46. Is there a personnel/cargo loading plan?
47. Has a plan been made for feeding personnel?
48. Has time been established for formation of convoy?
49. Has time been established for releasing trucks?
50. Is a written operation order on hand, if required?
51. Will a log of road movement be required at end of trip?
52. Has weather forecast been obtained?
53. Do all personnel have proper clothing and equipment?
54. Is there a communications plan?
55. Are personnel prohibited from riding in the cargo compartments of vehicles
transporting ammunition?
Are drivers of ammunition briefed on accident emergency response procedures
and the required withdrawal distances in case of a fire?
(DD Form 836, Special
Instructions for Motor Vehicles Drivers)
56. Are the marshaling areas for ammunition or explosive laden vehicles
57.
58.
59.
separated from unrelated personnel, equipment, and facilities by the
appropriate distance?
D-6
_______________________________________________________________________________
Appendix D
LOGISTICS PLANNING CHECKLIST
Yes
No
NA
Supply
Unit Supply Operations
1. Is the unit prepared to deploy with current publications, plans, SOPs, or
pre-positioned documents?
2. Are required unit supply regulations/ publications on hand current?
3. Are maintenance/technical manuals for unit equipment on hand current?
4. Does unit have sufficient, up-to-date publications to execute its supply
operations in support of deployment and sustainment operations?
Ammunition Requirements
1. Is the ammunition basic load (ABL) listing current and available?
2. Is the ammunition basic load listing updated and signed by the
commander (required annually and after MTOE change)?
3. Are pre-positioned DA Forms 581 for requesting ammunition at the
supporting installation?
4. Are procedures for distribution of TAT ammunition and non-TAT
ammunition covered in the unit SOP?
5. Does the unit have a designated supporting ammunition supply point
(ASP) for issue of pre-positioned stocks?
6. Does the unit SOP contain a by-bunker breakout of the ammunition basic
load (ABL)?
7. Are blocking and bracing requirements for packing ammunition for
surface shipment identified and pre-positioned requests provided to the
DEH?
8. Are blocking, bracing, and tie-down materials included in the OEL?
Basic, Prescribed and Operating Loads or Classes I, II, III, IV, and IX
Requirements
1. Are computed stockage levels adequate to support the unit?
2. Are computation lists for unit basic loads (UBLs) on hand and current?
3. Has the unit included provisions for classes of supply in the OEL?
4. Have significant shortages been identified to higher headquarters and
supply support activities for fill upon deployment?
5. Are on-hand UBLs serviceable/deployable?
6. If required by the OPLAN, are the unit commander and supply personnel
aware of requirements, availability, and necessary quantities of
contingency stocks and equipment?
7. Are they aware of points of storage and pickup for these stocks?
8. Is the completed supply request for rations to be consumed en route on
hand and current?
D-7
________________________________________________________________________________
FM 3-35.4
LOGISTICS PLANNING CHECKLIST
Yes
No
NA
9. Does the unit have a plan (which is not dependent on meal, ready-to-eat
(MREs)) for feeding soldiers until deployment?
10. Has the unit correctly closed out their dining facility and provided
alternate meal facilities for their soldiers?
11. Does the unit SOP, or other standing guidance, include procedures for:
a. Organization and training of specialized teams such as load teams,
interim property book officer for rear detachment, and others?
b. Delineation of deployment preparation responsibilities for unit
members, for example, designation of person responsible for load
planning supply requirements?
c. Submission of pre-positioned supply requests (packing and crating
materials; Class I, V, VII contingency items)?
d. Reporting MTOE and CTA equipment shortages to higher
headquarters for assistance in obtaining needed equipment?
e. Reporting equipment requiring maintenance assistance to deploy?
CTA 50-900
1. Are A and B bags packed according to the SOP?
2. Does each soldier have required CTA 50-900 items? Are items in
serviceable condition?
3. Has the unit taken the necessary steps to see that soldiers have an
opportunity to draw central issue facility (CIF) items in serviceable
condition?
4. Does unit have list of required zone clothing for possible contingencies?
5. Does unit have list of sizes for all personnel?
Disposition of POVs, Privately Owned Weapons, and Pets
1. Does each company/battery-sized unit or detachment have an officer or
NCO appointed as POV receiver for their unit?
2. Are POVs requiring storage identified?
3. Are installation forms being used for POV storage?
4. Is POV turn-in included in the N-hour sequence or deployment SOP?
5. Are pilferable items removed before processing for storage?
6. Are privately owned weapons registered with the provost marshal?
7. Do soldiers and/or the unit have plans for disposition of pets?
NBC
1. Does the unit have a written plan showing distribution of nuclear,
biological, and chemical (NBC) equipment down to the soldier level?
2. Is the NBC hand receipt accurate in terms of authorized MTOE and CTA
items?
3. Does unit have on hand the required chemical decontamination
D-8
_______________________________________________________________________________
Appendix D
LOGISTICS PLANNING CHECKLIST
Yes
No
NA
equipment (CDE)?
4. Are there any valid document numbers for CDE shortages on requisition?
5. Does the unit have a list of battle dress uniform (BDU), overshoes, and
gloves requirements by size?
6. Does the unit have DA Form 2765-1 prepared and pre-positioned for the
CDE contingency items?
7. Does the unit have anyone on the signature card to pick up the Nerve
Agent Antidote Kit (NAAK) and Nerve Agent Pyridostigmine Pretreatment
(NAPP)?
8. Does the unit have a packing and loading plan for CDE?
9. Does the unit have a resupply and distribution plan for CDE?
10. (When directed for exercise or operation) Does the unit draw and/or load
the proper amount of CDE?
11. Does every soldier have a properly fitted and serviceable protective
mask?
12. Are the authorized quantities of MTOE and CTA items of NBC equipment
on hand?
13. Is NBC equipment serviceable?
14. If equipment is not serviceable, does the unit have a viable plan to
replace unserviceable equipment?
15. Does the unit maintain records and track individuals who require optical
inserts?
16. Are all pieces of CDE requiring calibration within prescribed timelines?
17. Does the unit maintain proper packaging and shipping placards for CDE,
which contain radioactive sources?
18. Does the unit maintain a record of lot numbers and expiration dates for
CDE?
19. Does the unit have a written plan on how they will draw, obtain, and ship
decontaminating solution #2 (DS2), supertropical bleach (STB), or other
decontaminating agents?
D-9
________________________________________________________________________________
FM 3-35.4
Annex 2
Deployment Documentation Requirements
PALLETS,
PERSONAL
VEHICLES(1)
CONTAINERS
CRATES,
BAGGAGE
CONEXES
ALL MODES
Warning Placards (when applicable)
X
X
X
(for hazardous cargo)
Signature and Tally Record (DD Form
1907) (when applicable) for sensitive
X
X
X
cargo accountability
Unit Identification Code (UIC) and
X(4)
X(5)
X
Shipment Unit Number (Stenciled)
Military Shipping Label (DD Form 1387)
X(3)
X(3)
X(3)
Packing Lists (DD Form 1750/DA Form
X
X
X
5748-R)
*Security Seal
X(2)
X
ALL MODES, REDEPLOYMENT ONLY
*Military Customs Inspection Label (DD
X
X
X
X
Form 1253) or Tag (DD Form 1253-1)
*U.S. Customs Accompanied Baggage
X
Declaration
+*Decontamination Tag (DD Form
X
X
2271)
+Commander’s Certificate (No
X
X
ammunition or body parts)
+Certificate of Registration (CF 4455 or
X
4457) (when applicable)
+Registration of War Trophy Firearms
X
X
(DD Form 603) (when applicable)
AIR ONLY
Passenger Manifest (DD Form 2131)
X
Cargo Manifest (DD Form 2130 Series)
X
X
X
Pallet Identifier (DD Form 2775) or
X
compatible form
Special Handling Data/Certification (DD
Form 1387-2) (for sensitive and
X
X
X
classified)
Shipper’s Declaration for Dangerous
Goods form Miscellaneous (MISC) Pub.
X
X
X
55-3 for hazardous, sensitive, and
D-10
_______________________________________________________________________________
Appendix D
Deployment Documentation Requirements
PALLETS,
PERSONAL
VEHICLES(1)
CONTAINERS
CRATES,
BAGGAGE
CONEXES
classified.
(This form number was
assigned to the Shipper’s Declaration
for Dangerous Goods.)
Advanced Transportation Control and
X
X
X
Movement Document (ATCMD)
SEA ONLY
Dangerous Goods Shipping
Paper/Declaration and Emergency
Response Information for Hazardous
X
X
Materials Transported by Government
Vehicles (DD Form 836)
RAIL/COMMERCIAL TRUCK ONLY
Government Bill of Lading (GBL)
X
X
Prepared by the ITO
CONVOY ONLY
Convoy Clearance Request (DD Form
X
1265 or DD Form 2777)
Special Handling Permit (DD Form
X
1266 or DD Form 2777, when required)
Motor Vehicle Inspection (DD Form
X
626) (when applicable)
Shipping Paper and Emergency
Information for Special Instructions For
X
Motor Vehicle Drivers (DD Form 836)
Notes:
X: Identifies documentation requirement
U.S. Customs or USDA inspection may substitute CF for DD Forms.
+
Wartime redeployment.
(1) Includes major weapon systems and aircraft.
(2) Seal affixed to all cargo access areas.
(3) For all vehicles and consolidated shipment units, (containers and 463L pallets), deploying
OCONUS or on Emergency Deployment Readiness Exercises (EDREs) or Sealift
Emergency Deployment Readiness Exercises (SEDREs), regardless of mode, military
shipping labels (DD Form 1387) will be utilized. For vehicles, labels are placed on the front
(driver's side) bumper and on the left (driver's side) door.
(4) Stencil the UIC and SUN on the front and rear bumpers in 2-inch lettering.
(5) Stencil/mark FORSCOM and unit-owned containers only.
D-11
________________________________________________________________________________
FM 3-35.4
Annex 3
Blocking, Bracing, Packing, Crating and Tie-down Materials
This annex describes the policy for obtaining and stocking blocking, brac-
ing, packing, crating and tie-down (BBPCT) materials and related railcar
loading equipment for all mobilizing and deploying units. "BBPCT in
Support of Full Mobilization" is the official, all-encompassing title for the
program. It includes all materials required to protect vehicles, equipment,
and other cargo from damage or loss during transit. Blocking and bracing
material (BBM) includes tie-down materials and is the term applied to
materials required for rail and truck movement but does not normally in-
clude packing and crating materials. It may also be referred to as "BBT"
(blocking, bracing, and tie-down) material.
STOCKAGE
D-3-1. Installations/activities centrally stock BBPCT material only when it is
not possible to get from local sources before the unit deployment date.
Enough BBPCT should be on hand to support rapid deployment units. (For
example, units that will deploy before getting additional BBPCT.) For USAR
units, materials required for movement from point of origin to MS is listed in
a separate section of the unit’s movement plan and procured by the unit from
predetermined commercial sources following receipt of the alert order and de-
termination of mode. USAR units identify BBPCT material on hand every
year and provide a copy of the inventory to the regional support command
(RSC)/ direct reporting unit (DRU) or the U.S. property and fiscal officer
(USPFO)/ director of logistics (DOL). The inventory includes the serviceabil-
ity of BBPCT. USAR units identify available vendors and include them in the
unit’s mobilization plan.
D-3-2. ARNG units receive assistance from the USPFO and STARC, for
equipment moves during mobilization from point of origin to MS. USAR
units identify BBPCT material requirements unobtainable at point of origin
to the RSC/DRU, STARC, and if assistance in sourcing is required, to the SI.
UNIT MOVEMENT PLANS
D-3-3. Unit movement plans contain a separate section on BBPCT material
requirements. Units determine the amount of pallets, containers, boxes,
banding material, crates, and any other material required to protect and
unitize the unit equipment and supplies during transit to the AO. Units re-
port these requirements to the activity having implementing responsibility.
List and record all BBPCT material required for movement on the appropri-
ate local form.
BBT MATERIALS DETERMINATION
D-3-4. Planners use the current Association of American Railroads (AAR)
Loading Rules to calculate BBT material. In the absence of AAR procedures,
D-28
_______________________________________________________________________________
Appendix D
they use MTMC Pam 55-19. TC-AIMS II will assist in calculating BBT mate-
rial.
D-3-5. The actual BBT requirement depends on the following:
• Size and type of unit to be loaded.
• Types of railcars available.
• Amounts of rail outloading required for different POEs and OPLANs.
D-3-6. Each installation DOL/ITO, in coordination with UMC, directorate of
plans, training, and mobilization (DPTM), DPW, and civilian railroad offi-
cials, identifies and programs BBPCT requirements for their individual in-
stallations and supported units and activities.
DEPLOYMENT INSTALLATIONS
D-3-7. Commanders of deployment installations provide all BBT material to
support deployment. Long lead-time items (items with a procurement time
more than 14 days) will be stocked in sufficient quantities to supply the first
30 days of deployment.
D-3-8. For movement from the installation/MS, AC/USAR units furnish their
total BBPCT material requirements to their MS unit movement coordinator
(UMC) on DA Form 4283 (Facilities Engineering Work Request). If the form
is unavailable, they submit the request in memorandum format. The unit
annotates the deployment C-Day on the request.
D-3-9. The UMC reviews the material list against the DD Form 1726
(CONUS Military Installation Material Outloading and Receiving Capability
Report) to determine if the unit’s out-load deployment data is within the
limitations/capabilities of the installation. When the review is completed, a
listing of the required material and the respective time frames are furnished
through the DPW or appropriate installation activity to the installation di-
rector of contracting (DOC) for local purchase review.
D-3-10. The installation DOC performs a local market survey to determine
which required items of BBT are readily available in the required quantities
from commercial sources. (Those items are not purchased and stocked unless
a subsequent market survey shows that the items cannot be acquired prior to
the unit out-load date.) The installation conducts the local market survey at
least annually due to the changeable nature of supply and demand in the
commercial marketplace.
D-3-11. The DOC annotates the materials list, indicating which items are not
readily available on the local market. The DOC also maintains the list of
readily available materials in a form and manner that expedites acquisition
upon deployment. The DOC only gets materials specified by the installation
UMC. (That is, the items not readily available and not on hand.)
D-3-12. The DPW/DOL ensures that supply and accountability procedures in-
clude control, storage, issue, turn-in, maintenance, and replacement of
BBPCT materials, railcar spanners, hand tool sets, portable end ramps, and
any other related rail loading equipment.
D-29
________________________________________________________________________________
FM 3-35.4
D-3-13. The DPW or DOL conducts an annual inventory of BBT material and
furnishes it to the installation UMC for review to determine adequacy. Addi-
tions or deletions to requirements are annotated on the listing and processed
through the installation DOC as necessary for inventory adjustment. The
annual inventory indicates the condition of the BBT and whether it is a can-
didate for rotation. The material is stocked separately from the stock fund
inventory as mobilization stockage. Due to shelf life consideration, materials
are rotated from the BBPCT inventory.
D-3-14. BBT is stripped from the equipment at the APOE/SPOE. The MTMC
port commander has first priority for using BBPCT removed at the SPOE.
Available transportation is used to return residual material to the respective
installations for possible reuse.
RAIL LOADING EQUIPMENT
D-3-15. Rail loading equipment includes (but may not be limited to) hand tool
sets, railcar spanners (or bridge plates), and portable end loading ramps (sin-
gle and multilevel).
HAND TOOL SETS
D-3-16. The DOL manages the inventory of BBPCT hand tool sets needed for
installing BBPCT material during mobilization. BBPCT hand tool sets may
be used for normal (non-mobilization/deployment) shipping activities. Instal-
lations ensure that accountability, control, maintenance, storage, and re-
placement procedures are clearly established to ensure sufficient hand tool
sets are on hand in case of mobilization/deployment shipping activities. To
calculate the number of hand tool sets required, divide by four the number of
rail flatcars that are expected to be positioned for a single loadout. Add five
percent for breakage and round to the nearest whole number. (If .4 or lower,
round down; if .5 or higher, round up. Example: 78 railcars divided by 4 =
19.5 x 1.05 = 20.475 tool sets, which rounds to 20.)
RAILCAR SPANNERS
D-3-17. Railcar spanners (bridge plates) may be used for normal peacetime
shipping activities. However, accountability controls, maintenance, storage,
and replacement procedures must be clearly established to ensure sufficient
spanners are on hand in case of mobilization. To calculate the number of
spanners required, figure one set (two spanners) for each rail flatcar expected
to be positioned for a single loadout. Add an additional set for each perma-
nent end ramp to be used for loading. Then add five percent for breakage
and round as in the above paragraph. (Example: 78 railcars loading at three
permanent end ramps: 78 + 3 = 81 x 1.05 = 85.05, which rounds to 85 sets of
spanners.)
PORTABLE END LOADING RAMPS
D-3-18. Portable end loading ramps may be single level (for standard flat-
cars) or adjustable multilevel (for loading bi-level railcars). They may be ei-
ther towed or self-propelled and are normally procured and managed as TDA
items. Like spanners, the ramps may be used for normal operational activi-
D-30
_______________________________________________________________________________
Appendix D
ties provided they are properly controlled and maintained or replaced if nec-
essary to ensure availability for mobilization. There is no formula to deter-
mine the number and types of portable ramps required. This can only be de-
termined by the ITO’s careful evaluation of the magnitude of the outload mis-
sion, compared to the physical facilities (permanent loading ramps/docks)
available. The DOL should initiate action to add to the installation TDA the
number and type of ramps required but not currently authorized.
D-31
Appendix E
Unit Movement Plan (Sample)
This annex provides ideas, data, and samples of many items that must be
considered in developing the unit movement plan. USAR units complete
one plan from point of origin to MS, and, if required, one from MS to
POEs. AC units prepare movement plans for deployment to the POEs.
The plan is written in operation order format according to FM 5-0 (101-5).
It becomes an order when adding required data and specific times. A unit
may have several plans, each one planning for a specific contingency. The
unit plans the move using the movement plan and executes the move un-
der an operation order. The movement plan contains all annexes and ap-
pendices. Those not used are marked “NA” so that later developing plan-
ning data may be added to the existing plan. The operation order has spe-
cific movement instructions and is dated and signed. The annexes contain
information required to support the plan.
E-1
________________________________________________________________________________
FM 3-35.4
UNCLASSIFIED
Classification
Copy no__of__copies
(Issuing Unit)
(Street Address)
(City, State, ZIP Code)
(Date of Plan)
MOBILIZATION MOVEMENT PLAN (Point of Origin to MS) (USAR Only)
DEPLOYMENT MOVEMENT PLAN (MS to A/SPOE) (AC) (USAR, if required)
References: FM 4-01.40 (55-30), STARC, RSC, Direct Reporting Unit (DRU), and Installation
Mobilization/Deployment Plan, (Any other maps, SOPs, manuals, etc.)____include dates of publica-
tions
Time Zone used Throughout the Plan: _____
Task Organization
HQ, HHC,___Bn_____,___
Co A _______,__
Co B _______,__
Co C _______,__
Co D _______,__
____Det_____,__
1. SITUATION: This should be a generalization of when/how the plan is to be implemented.
a. Attachments and Detachments: Listed with appropriate units or the word "none."
b. Assumptions: These are conditions a commander believes will exist at the time the plan be-
comes a movement order. Assumptions are clearly stated and address—
(1) Equipment serviceability.
(2) Availability of personnel for movement.
(3) MTOE supplies and equipment to be transported.
(4) Pre-positioned equipment, if applicable.
(5) Vehicles/equipment in maintenance.
(6) MS gate assignments/time to MS/APOE/SPOE.
(7) Use of modes to MS/APOE/APOE.
(8) Commercial movement.
E-2
_______________________________________________________________________________
Appendix E
The following are examples of some assumptions:
(1)
All unit equipment will be combat serviceable.
(2)
All unit personnel will be available for movement.
(3)
During a selected 200K call-up, cross-leveling of personnel and equipment will occur.
(4)
All (including excess) MTOE/TDA equipment and supplies will be transported to the MS
(USAR only).
(5)
All vehicles and equipment on job order or hand receipt will be recovered prior to depar-
ture from point of origin or arrangements will be made during Phase II for pick up by the
unit or to ship commercially directly to the mobilization station (MS) (USAR only).
(6)
MS gate assignments and arrival/departure times have been designated by the MS and
coordinated with the DMC.
(7)
Organic convoy movements from point of origin to the MS and subsequently to A/SPOE
will be administrative.
2. MISSION: A concise statement of what is to be accomplished and its purpose. It accomplishes
the following—
a. Identifies unit(s).
b. Identifies origin and destination.
c. Identifies date and time movement begins and ends.
d. Identifies methods of movement: organic/commercial, and mode: truck, rail, air, and sea.
e. Identifies reason for moving (OPLAN, etc.).
An example of a mission statement from a mobilization movement plan is—
The (issuing unit)___will move from point of origin to (MS)___to arrive not later than (date/time first
element arrives at the gate)___. Advance parties will depart not later than (date/time of earliest ad-
vance party departure)___. Commercial transportation consisting of
(trucks, buses, and/or
rail)___(will/will not)___ be used, but will not necessarily move with the organic convoys.
An example of a mission statement from a deployment movement plan is—
On order, the (unit name)______will establish staging/marshaling areas and deploy personnel and
equipment to perform operations in the designated area of operations. Units will deploy from (installa-
tion)_____via APOE______and SPOE. (Transportation motor pool (TMP)/commercial buses) will
transport personnel to the APOE. All roadable vehicles will be convoyed to the SPOE. Non-roadable
vehicles will go by rail or commercial truck to the SPOE. Movement will commence in accordance
with (IAW) the alert order and the N-hour sequence (Annex S). Movement will be by (organic assets
to the SPOE, or rail, or commercial truck)____. Order of march will be advance party followed by
main body. Unit will be prepared to deploy on other contingency missions.
3. EXECUTION: This paragraph addresses the necessary planning, coordination, and execution
functions that must take place in order to accomplish the mission. Specific tasks are given.
a. Concept of Movement: The concept clarifies the purpose of the plan. It addresses (point of
origin to MS and MS to A/SPOE)—
(1)
Receipt of movement orders.
E-3
________________________________________________________________________________
FM 3-35.4
(2)
Update and validation of OEL.
(3)
Recovery of equipment.
(4)
Commercial movement of personnel (by buses, and other modes).
(5)
Deadline to complete packing and loading.
(6)
Advance party composition.
(7)
Main body composition.
(8)
Order of march and convoy numbers for highway movement.
(9)
Shuttle of equipment (USAR only must obtain permission from the MS).
(10)
Commercial movement of vehicles/equipment.
(11)
Priority of support.
(12)
MO/ITO coordination.
(13)
ITO designated load dates and locations.
(14)
UMO duties and responsibilities.
(15)
Projected POEs.
(16)
Applicable OPLAN.
(17)
Actions at POE (reduction, receipt of cargo, and others).
Examples of Concept of Movement statements are—
(1)
Upon receipt of the alert notification, the first priority will be for the UMO to review the Re-
quest for Commercial Transportation and OEL.
(2)
To meet MS gate arrival/departure times, the unit will conduct simultaneous coordination,
processing, and loading operations using the unit’s N-hour sequence (Annex S).
(3)
Start point times are IAW DD Form 1265 (Request for Convoy Clearance) (Annex __).
(4)
Commercial transportation/support requirements are located at Annex ___.
(5)
All organic vehicles will have a driver and assistant driver.
(6)
The UMO will coordinate and confirm—
(a) Changes to DD Form 1265.
(b) Request for commercial transportation with transportation office NLT___.
(c) En route stops/halts with appropriate businesses.
(7)
Commercial buses will be used to transport personnel and baggage. A troop commander
will be designated for each commercial bus.
(8)
Supplies and equipment will be packed, cushioned, and/or crated, and loaded on organic
vehicles IAW current vehicle load cards no later than (number of hours)____prior to depar-
ture.
(9)
Advance party elements will be composed of personnel, equipment, and documentation
required to accomplish tasks identified by the MS and will move by organic convoy IAW
Annex ___. Vehicles will infiltrate to (consolidation point)____ where battalion advance
party convoy will form. The convoy number will be ___.
(10)
Main body organic convoys will depart point of origin/MS IAW Annex ___. Individual con-
voys will consolidate at (consolidation point)____.
(11)
Order of march and convoy numbers will be—
Unit___ Convoy Number ___
E-4
_______________________________________________________________________________
Appendix E
Unit___ Convoy Number ___
Unit___ Convoy Number ___
Unit___ Convoy Number ___
Unit___ Convoy Number ___
Unit___ Convoy Number ___
Unit___ Convoy Number ___
(12) Shuttle convoys (will/will not) be used.
(13) Unit supplies and equipment will be prepared for commercial movement by (rail, truck,
etc.)___ IAW the OEL in the unit load plan not later than (date/time)___.
b. Tasks to Subordinate Units/Elements: This paragraph clarifies and states tasks and timelines
in sufficient detail to ensure action by subordinates or platoons/sections within a company. It
addresses the following as relates to the actual move:
(1)
Company, platoon, or section tasks.
(2)
Maintenance.
(3)
Supply.
(4)
Food service.
(5)
Rear detachment.
(6)
NBC.
(7)
Loading teams.
(8)
Training.
(9)
Rail guards, convoy guides, supercargoes, etc.
Reports.
Examples of tasks listed in this section are—
(1)
Company, battery, or detachment advance party vehicles will convoy to consolidation point
at___(date/time).
(2)
Maintenance: date/time to stop repairs and load maintenance equipment.
(3)
Supply: date/time to complete issue and start loading.
(4)
Food service: date/time to close down food service operation, clean up, and load food ser-
vice section equipment.
(5)
NBC: CDE guidance--disposition of CDE, load on vehicle or issue to individual.
(6)
Load teams: date/time to complete loading of advance party, main body, commercial loads,
and others.
c. Coordinating Instructions: These list requires coordination for planning and executing phases
with—
(1)
Higher headquarters.
(2)
STARC/MUSARC/next higher headquarters.
(3)
Mobilization station/ITO.
E-5
________________________________________________________________________________
FM 3-35.4
(4)
Mobilization and training equipment site (MATES) and equipment concentration site
(USAR Only).
(5)
Transportation terminal nodes
(bus terminal, railhead, APOE, SPOE, MAs, STARC
movement control center (MCC) for highway movements).
(6)
Local agencies and businesses.
(7)
All elements internal to unit.
Example of coordination covered in this paragraph is—
Physical security officer will coordinate current information with local and state police NLT _______
days prior to movement.
4. SERVICE SUPPORT: This paragraph lists the support needed for the unit move. They must be
listed either in the basic plan or as annexes to the plan. As a guide, if the information for a sub-
paragraph will fit on one page, include it in the body of the plan. This makes your plan easier to
read and easier to use. If the information for a subparagraph is longer than one page, consider
placing it in an annex.
The following should be addressed—
a. Supply—
(1)
Class I (See Annex__). This annex/subparagraph should address subsistence for—
(a) Advance party.
(b) Main body.
(c) MATES/ECS recovery or load teams (if applicable).
(2)
Class II (See Annex__). This annex/subparagraph should cover any pertinent informa-
tion on organizational clothing and individual equipment (OCIE).
An example of an item in this subparagraph is— Due to movement being an administrative one, all
weapons, NBC equipment, and other non-combat OCIE will be packed, boxed, and moved adminis-
tratively.
(3)
Class III
(See Annex__). This annex/subparagraph should address—
(a) Topping off vehicles.
(b) Trail party requirements.
(c) En route refueling.
(d) Packaged requirements.
(e) Bulk requirements.
(f)
Motor fuels.
(g)
Aviation fuels.
Examples of items included in this subparagraph include—
(a) All vehicles will be topped off and will carry fuel cans strapped in the mounts. Units without a
fuel-dispensing facility will purchase from a local vendor using SF 44.
(b) The trail maintenance party will carry the minimum quantities of packaged POL supplies to
support the convoy as listed below:
E-6
_______________________________________________________________________________
Appendix E
48 qts
15W40 oil
15 gals
OE/HDO 30 oil (5-gal cans)
10 gals GO 80W09 oil (5-gal cans)
35 lbs
GAA grease (pail)
24 qts
Dextron II (trans fluid)
1 gal
Brake fluid (1-gal can)
5 gals
Cleaning solvent
1 bdl
Rags
(c) Refueling en route will be by (credit card, 5-gal cans, organic tanker, SF 44, or other).
(4)
Class IV (See Annex__). This annex/subparagraph should include BBPCT require-
ments and pre-positioned requests, along with construction materials.
Examples of items included in this subparagraph are—
(a) All barrier/construction materials will be shipped.
(b) The complete BBPCT list for the unit is in Annex __.
(5)
Class V (See Annex___). This annex/subparagraph includes guidance on the transpor-
tation of ABL.
(6)
Class VI (See Annex___). This annex/subparagraph should be included if directed by
OPLAN/OPORD.
(7)
Class VII (See Annex___). This annex/subparagraph should cover—
(a) Retrieval and commercial shipment procedures in MATES/ECS (USAR only).
(b) Procedures for loading and accounting for equipment moved by commercial rail or
truck.
(c) Civilian ambulances and medical personnel may be used for assistance and
evacuation.
An example of an item included in this subparagraph is: Major end items will be loaded IAW Annex
____. For USAR units, all excess MTOE equipment will be transported to the MS.
(8)
Class VIII (See Annex__). This annex/subparagraph should address—
(a) On-hand medical supplies transported to the MS/POE.
(b) Supplies for en route medical support.
Examples of items included in this subparagraph are—
(a) All vehicles/aidmen will move with authorized first aid kits.
(b) Medical emergencies en route will be evacuated to the nearest hospital.
(9)
Class IX (See Annex__). This annex/subparagraph should address—
E-7
________________________________________________________________________________
FM 3-35.4
(a) Combat Assigned or Authorized Stockage List (ASL)/PLL drawn from appropriate
source and loaded on organic vehicles.
(b) Trail party requirements.
Examples of items to be included in this subparagraph are—
(a)
Combat PLL will be loaded on organic vehicles.
(b)
All Class IX ASL/PLL will be packed, crated, and/or boxed to meet requirements of An-
nex__.
(c)
During the convoy, the trail party will carry, as a minimum, the items identified in Annex__.
(d)
Excess PLL will be transported to the MS and turned in (USAR only).
(10) Class X (See Annex__). This annex/subparagraph covers material to support nonmili-
tary programs such as agriculture and economic development (not authorized for mobi-
lization).
b. Maintenance:
(1)
Pre-movement support requirements (Annex __). This annex/subparagraph should in-
clude information on training, cleaning, and purging fuel containers and on priority of
maintenance support.
(2)
En route support requirements (Annex __). This annex/subparagraph contains informa-
tion on coordination for en route support (supporting facilities and POC names and
phone numbers), trail party requirements, and en route PMCS, if required.
Examples of the items contained in this subparagraph are—
(a) The trail party for the main body will consist of ____vehicles and ____personnel.
(b) En route PMCS will be performed at the halt number ____.
(c) If a vehicle fails, stops, or has an accident, only that vehicle will halt.
The maintenance trail party will provide assistance and keep the convoy commander informed.
c. Transportation:
(1)
Air.
(Annex ____, if required)
(2)
Convoy. (Annex ____, if required)
(3)
Rail.
(Annex ____, if required)
(4)
Commercial. (Annex ____, if required)
(5)
Unit movement data (UMD). (Annex ____)
d. Procurement
e. Facilities/Equipment
f.
Medical Evacuation Procedures
g. Personnel:
E-8
_______________________________________________________________________________
Appendix E
Examples of items contained in this paragraph are—
(1) Uniform for movement will be battle dress uniforms (BDUs) (combat boots and berets).
(2) All personnel accountability inspections and convoy briefings (Annex M) will be conducted
prior to movement (Annex S).
(3) Each individual is authorized a total weight of ___for personal baggage, ___duffle bags for
TA-50, and for clothing and comfort items. The unit’s scales will be used to confirm this.
h. Civil/Military Coordination, if required
i.
Other:
(1)
Points of contact. (Annex ____)
(2)
Coordinating instructions.
5. COMMAND AND SIGNAL.
This paragraph addresses—
a. Chain of command, to include convoy commanders, bus troop commanders, and others.
b. Personnel control (formations, briefings, safety, and such).
c. Command locations.
d. Signal instructions (telephone, radio, and such).
(1)
Commercial telephone.
(2)
Expedited movement reports procedures.
(3)
Radio procedures.
(4)
Current signal operating instructions.
e. N-Hour sequence (See Annex ____).
The commander or specifically authorized representative must sign the movement plan. If the signa-
ture is not reproduced or on subsequent copies, authentication by the appropriate coordinating staff
officer is required.
Annexes are used for those items that would require too much space in the basic plan. If an annex is
not necessary, or unused, type title and N/A.
E-9
________________________________________________________________________________
FM 3-35.4
ANNEX A - Procurement.
This annex includes sources for specific commodities and services.
ANNEX B - Class I - Subsistence.
This annex covers en route meals and gratuitous health and welfare items.
ANNEX C - Class II.
This annex covers all guidance on clothing, individual equipment, tentage, organizational tool sets,
NBC equipment, hand tools, electronics, administrative housekeeping supplies, and weapons.
ANNEX D - Class III.
This annex gives guidance for aircraft and surface vehicles, coolants, de-icing and antifreeze com-
pounds (together with components and additives of such products) and coal, hydraulic and com-
pressed gases and lubricants.
ANNEX E - Class IV.
This includes information on material for securing vehicle secondary loads and securing major end
items to transportation assets.
• Appendix 1 - BBPCT material for secondary cargo/loads in vehicles, trailers and containers,
dunnage/shoring for air deployment, and plastic pallet covers for 463L pallets.
• Appendix 2 - Required documentation. This includes work order requests or memoranda for
BBT. (Requisitions are used to order packing, crating, and plastic covers).
ANNEX F - Class V.
Class V includes ammunition of all types (including NBC and special weapons), bombs, explosives,
mines, fuses, detonators, pyrotechnics, propellants, and other associated items. This annex should
include the time and location of issue. This annex is not available for USAR mobilization movement
plans.
ANNEX G - Class VII.
Class VII includes final combinations of end products that are ready for their intended use (that is,
tanks, launchers, mobile machine shops and vehicles, MHE, compressors, and construction equip-
ment). The annex covers procedures for loading and accounting for equipment moved by commercial
truck or rail. It also includes the time major end items will be loaded on commercial assets (reference
- unit N-Hour sequence). It includes an equipment retrieval plan (USAR only).
ANNEX H - Class VIII.
Class VIII is medical material, including medical peculiar repair parts. In addition to Class VIII, this
annex covers en route medical support - first aid kits and medical support at SPOEs/APOEs.
ANNEX I - Class IX.
This annex covers guidance on repair parts (less medical peculiar repair parts and components), to
include kits, assemblies and subassemblies, repairable and non-repairable, required for maintenance
support of all equipment.
ANNEX J - Pre-movement Maintenance Support.
This annex covers such items as equipment status, contact teams, drivers’ licenses, PMCS, se-
quence of events for maintenance operations, non-repairable equipment, tow bars, and topping off
vehicles.
ANNEX K - Equipment Maintenance Support.
This covers maintenance during the actual move. It discusses abandoned vehicles, roadside repairs,
tow bars, contact teams, repair services/parts, and maintenance vehicles.
E-10
|
|