Department of the Army 'FORSCOM Regulation

Department of the Army 'FORSCOM Regulation 55-2Headquarters, Forces CommandFort McPherson, Georgia 30330-60001 October 199-3

Transportation and TravelUNIT MOVEMENT DATA REPORTING AND SYSTEMS ADMINISTRATION

Summary. This regulation represents a major revision of policy, requirements, and procedures for unit movement data(UMD) maintenance and reporting. It supersedes all previously issued guidance pertaining to UMD maintenance andreporting. This regulation authorizes and directs the use of the Transportation Coordinator Automated Command andControl Information System (TC ACCIS), as well as coordinated and approved alternative automated means for continuingmaintenance of UMD and for reporting UMD to FORSCOM.Applicability. This regulation applies to the Active Component units assigned to Forces Command, the Army NationalGuard (ARNG), and the U.S. Army Reserve (USAR). Provisions of this regulation applies to all units reporting UMDto FORSCOM.Supplementation. Supplementation of this regulation is prohibited except as explicitly directed in specific sections ofthis document or unless written approval is obtained in advance from CDR, FORSCOM, ATTN: FCJ4-TRU (Systems),Fort McPherson, GA 30330-6000.Interim changes. Interim changes to this regulation are not official unless they are authenticated by the Director, Command.Control, Communications and Computers, J6, HQ FORSCOM. Users will destroy interim changes on their expirationstates unless superseded or rescinded.Suggested Improvements. The proponent agency of this regulation is Directorate of Logistics, J4, HQ FORSCOi.SUsers are invited to send comments and suggested improvements on DA Form 2028 (Recommended Changes to Publicationand Blank Forms) to CDR, FORS.COM, J4, Transportation and Services Division, ATTNi: FCJ4-TRU (Systems), FortMcPherson, GA 30330-6000.Restrictions. Approved for public release; distribution unlimited. Local reproduction is authorized.

FOR THE COMMANDER:

OFFICIAL: C. G. MARSHMaior General USAChief of Staff

GARY LUKEYColone, SADirector, Command. Control.

Communications and Cornuters, J6

DISTRIBUTION is Special for HQ FORSCOM, FORSCOM installations. FORSCOM units on non-FORSCOMinstallations, HQ CONUSA, HQ USARC, USAR, and ARNG, intended for command levels A, B, C, D, and E.

Copies furnished:HQDA(DALO. DAMO. DAIG). NGB. TRADOC, TRADOC installations. HSC, AMC, MD\M USAREUR and SeventhArmy. USARPAC, HQ USAISC. Eighth U.S. Arm, USASOC, HQ FORSCOM (FCJ6-OAP) (record set)

CONTENTSParagraph Page

Chapter 1GeneralPupOSC ........... .............. ..... ................................ 1-1 3References ................................................. 1-2 3Explanation of abbreviations and terms .................. ................... 1-3 3Scope ... ......................................... 1-4 3Concept of unit movement data reporting ................... 1-5 3Security of unit movement data............................................. 1-6 3Chapter 2Functions and ResponsibilitiesGeneral ........ 2-1 4U.S. Army Forces Command.............................................. 2-2 4U.S. Army Reserve Command.............................................2-3 4Continental United States Armies (CONUSA) ................................. 24 4U.S. Army Readiness Groups .............................................. 2-5 4State Area Cornmands (STARC)........................................... 6 2-

*This regulation supersedes FORSCOM Regulation 55-2., dated 1 November 1988.

FORSCOM Regulation 55-2

Major U.S. Army Reserve Commands (MUSARC) ..........................Installations.........................................................Units...... ........... ........... ...............................Inspections ........................... ... ......................Air Certification Procedures ............................................Chapter 3Computerized Movement Planning and Status System (COMPASS)

(RCS FCJ4165(R2) Unit Movement Data (UMD) ReportingGeneral ... ....................................................UMD Reporting Procedures ............................................UMD Update .......................................................UMD Update Remarks ...............................................UMD Reporting Requirements........................WWMCCS and Management Data Query (MDQ) Programs ...................

Chapter 4COMPASS ProductsCOMPASS Products................................................AUEL .........................................................Tailored Report ..... . . . . . . . . . . . . . . . . . . . . . . . . . .

Blocking and Bracing Material (BBM)......... """".........................COMPASS BR and BV Reports ........................................POMCUS UMD....... .. ......................................Type Unit Characteristics Data (TUCHA) ................................ .To Obtain Reports . .................................................Example Worksheets ..................................................Chapter 5Data Element DescriptionsG eneral .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Automated Unit Equipment List (AU EL) ..................................FORMAT .............................. ............................Unit Movement Data Reporting Structure .................................Basic luentifv Data Element File (BIDE)...................................Type Data Codes (TDC) ...............................................Report Type........... ..................................Special Instructions for MOB UMD Reporting..............................Special Instructions for POM UMD Reporting..............................Special Instructions for Tailored U MD Reporting ............................Unit Line Number....................................................Worksheets Data Elements .............................................

"A" Record - Header & Personnel Strength) .............................."D" Record - Vehicle Data ........................................... ."E" Record - Vehicle Load Data ........................................"F" Record - Special Handling Cargo................................... ."G" Record -Container Load Data ...................................."J Record - Rail, Truck & Bus requirement ............. ................."H0001" Record - CS RO Request.......................................H0002" Record - CSRO Request (continuation) ...........................

"HOO03" thru "9999" Record - Remarks Data ............................."B" Record - Deployment Data................... .................... .

Chapter 6Transmission of UMDG eneral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Submitting UMD via AUTODIN ........................................Submitting UMD via DDN.............................................Receivng AUEL and BBM Reports via AUTODIN ..........................Receiving AUEL, BBM. Tailored Reports via WWMCCS......................Transmitting COMPASS AUEL Error Listings via DDN ......................Chapter 7Systems AdministrationGeneral........................Purpose........................Responsibihites ..................Svstem Description ...............Coordination ....................Appendix: References..... .......... ................................Gloss. ..............................................................

2-72-82-92-102-11

41424-34-44-54-64-74-849

5-15-25-35-45-55-65-75-85-95-105-1 15-125-12a5-12b5-12c5-12d5-12e5-12f5-12g5-1 2h5-12i5-1 2j

6-16-26-36-46-56-6

Figure3-1

3-2

3-3

3-4

3-5

3-64-1

4-24-3

4-44-54-64-7

4-8

4-9

4-10

4-11

4-12

LIST OF FIGURESTitle

Unit Movement Data (UMD)Update ScheduleFlow of UMD updates from unitsto FORSCOMAUEL and ERROR listings -FORSCOM to UnitsAUEL/other reports from FORS-COM to UnitsAUEL/ POMCUS reports fromFORSCOM to UnitsExample of Movement ReportsAUEL Report Unit MovementData DetailAUEL Detail explanationAUEL Report Unit MovementData SummaryAUEL Summary explanationTailored ReportTailored Report explanationSample Rail BBM Material DetailListSample Rail BBM MaterialSummaryFORSCOM Form 900-R HData (RC)FORSCOM Form 900-1-Rcle Data (RC)FORSCOM Form 900-2-RRecord (RC)FORSCOM Form 900-3-R

eader

Vehi-

Load

Spe-cial Handling (RC)

4-13 FORSCOM Form 900-4-R Rail,Truck, Bus (RC)

4-14 FORSCOM Form 900-5-R CRSOand Remarks (RC)

LIST OF TABLESTable Title

5-1 Water Commodity Codes(WCOMMCDE)

5-2 Type Cargo Codes (TCC)5-3 Special Handling Codes (SHC)5-4 Mode to Port of Embarkation;'

Mode to Mobilization Station(MPE 'MMS) Codes (Old andNew)

5-5 Type Pack Codes5-6 Type Equipment Codes

Page7

8

9

10

11

1215

1618

19212223

24

25

26

27

28

29

30

Page45

464747

4849

Chapter 1General1-1. PurposeThis regulation prescribes policy and assigns responsibilitiesto units, installations, Major U.S. Army ReserveCommands (MUSARC), and State Area Commands(STARC) for reporting Unit Movement Data (UMD)governed by JCS Pub 6, the Army Mobilization Planningand Execution System (AMOPES), AR 10-42, AR 220-10,and the FORSCOM Mobilization and DeploymentPlanning System (FORMDEPS). Conflicts between thisregulation and FORMDEPS will be resolved by thisregulation.


1-2. ReferencesRequired references and related publications are listed inappendix.1-3. Explanation of Abbreviations and TermsAbbreviations and terms used in this regulation areexplained in the glossary.1-4. ScopeThis regulation applies to UMD reporting under allconditions:

a. Mobilization planning and execution.b. Deployment planning and execution.c. Directed, coordinated or other exercises, as

appropriate and temporary change of station (for disasterrelief, exercises, emergency or simulated emergencyconditions) or permanent relocation.1-5. Concept of Unit Movement Data ReportingUnit Movement Data (UMD) reflected in an AutomatedUnit Equipment List (AUEL) is the information of recordfor planning and executing movement of Army units (bothActive (AC) and Reserve (RC) Components).

a. All units have the primary responsibility for updatingunit movement data, ensuring this data is maintainedaccurately and reported to FORSCOM as prescribed bythis regulation.

b. Supporting installations/mobilization stations areresponsible for providing support to units in the updateand maintenance of unit movement data and for reportingUMD to FORSCOM.

c. The Transportation Coordinator Automated Com-mand and Control Information System (TC ACCIS) isthe means to be used at unit/installation level (for Active.Army National Guard and U. S. Army Reserve units) foraccomplishing unit movement data update and maintenanceresponsibilities. The Reserve Component AutomationSystem (RCAS), when fielded, will assume unit movementdata update and maintenance responsibilities for the ArmyNational Guard and U.S. Army Reserve units. Alternativeupdate and reporting processes may be employed asapproved by the Commander, FORSCOM. J4 Transpor-tation and Services Division, ATTN: FCJ4-TRU (Systems).

d. Several Type Data Codes may be needed. Thisapplies to RC units, Contingency Forces, early deployingunits, direct or modified deploying units, units designatedpropositioning of material configured to unit sets(POMCUS), and units troop listed on exercises.

e. For installations using TC ACCIS, Type Data Code(TDC) XA through XZ, YA through YZ and ZA throughZZ are assigned for local use as needed by the installationor supported units. These TDCs must be controlled bythe TC ACCIS System Administrator or installation UnitMovement Coordinator (UMC). All other TDCs will becontrolled, managed and assigned by HQ FORSCOM.1-6. Security of Unit Movement Data

a. Unit movement data is unclassified unless the missionor specific operational capability of the unit is indicated.UMD should be treated as sensitive unclassified. Whenset against a specific objective the UMD may be classified.Unit Movement Data for general planning purposes mav.require modification for a specific task mission.

b. Mobilization UMD not classified.c. Force size (e.g., division, corps, army, or total f rcc!

is not justification to classify data. UMD is unclassified


unless directed by HQ FORSCOM, however, precautionsshould be taken to protect movement data (e.g., lockedfile cabinets, desks, rooms, or safe) as much as possible.Chapter 2Functions and Responsibilities2-1. GeneralFunctions and Responsibilities will be as prescribed byFORSCOM Regulation 55-1 and as prescribed in thischapter2-2. U. S. Forces Command (FORSCOM)See FORSCOM Regulation 55-1.2-3. U. S. Army Reserve Command (USARC)See FORSCOM Regulation 55-1.2-4. Continental United States Armies (CONUSA)See FORSCOM Regulation 55-1.2-5. U.S. Army Readiness GroupsSee FORSCOM Regulation 55-1.2-6. State Area Commands (STARC)The Adjutant General will perform the functions as outlinedin F ORSCOM Regulation 55-1 and as follows:

a. Establish policies, procedures, maintain a suspensecontrol and assist assigned units in preparing UMD asprescribed by this regulation.

b. Ensure reporting of subordinate unit cargo andpersonnel. located on or originating from active or stateowned / operated installations requiring commercialmovement support. This includes subordinate detachmentsand ARNG cargo located in a Unit Training EquipmentSite (UTES), Week-End Training Site (WETS), Mobili-zation And Training Equipment Site (MATES), Organ-izational Maintenance Support Activities (OMS), or otherstorage sites.2-7. Major U.S. Army Reserve Command (MUSARC)Commanders, MUSARC, will perform the functions asoutlined in FORSCOM Regulation 55-1 and as follows:

a. Establish policies, procedures, maintain a suspensecontrol and assist assigned units in preparing UMD, asprescribed by this regulation.

b. Ensure reporting of subordinate unit cargo andpersonnel located on or originating ,rom active or reserveinstallations requiring commercial movement support. Thisincludes USAR cargo located in a Equipment Concen-tration Sites (ECS), Week-End Training Site (WETS), AreaMaintenance Support Activities (AMSA), Unit TrainingEquipment Site (UTES) or other storage site.2-8. InstallationsCommanders of active, semi-active and state-ownedinstallations will appoint an individual and an appropriatestaff to perform UMC functions as a primary duty asoutlined in FORSCOM Regulation 55-1. Installations aredesignated as Mobilization Stations (MS) for mobilizedRC units. All MS have the additional duty to provide forreception of mobilized RC units. The MS performs SupportInstallation (SI) duties for the mobilized RC units uponarrival at the MS. Installations will also:

a. Set up procedures for reviewing, validating,approving and coordinating UMD reporting to ensure dataaccurately represents movement requirements for mobil-ization (MOB UMD), for deployment (POM UMD) andjoint exercise!contingency moves.

b. Establish policies and procedures for UMDreporting using TC ACCIS or FORSCOM approvedalternative means.

(1) Ensure procedures are established for receptionof arriving mobilized units and for deploying units.

(2) Establish requirements for the use of TC ACCISfor reporting of unit movement data by units.

c. All MS/SI must provide for expedited collectionand reporting of POM UMD for mobilized RC units inaddition to UMD maintenance and update for supportedAC units.

d. Publish guidance applicable to commanders of ACand RC units, ECS, UTES, WETS, MATES, AMSA, andstorage sites directing which documents will be preposi-tioned with the installation UMC in preparation for unitmovements. See FORSCOM Regulation 55-1.

e. Maintain a suspense control system for assigned/supported units to ensure compliance with the reportingrequirements prescribed in this regulation.

f. Assist assigned/supported units in reporting UMD,and establish procedures for reviewing and validating UMDusing either automated (preferred) or manual (alternative)means.

g. Assist STARC and MUSARC in their areas ofsupport responsibility for reporting UMD. This will includetraining assistance, automated systems support for dataentry (UMD collection) and communications support (datatransmission) for preparation and submission of UMD toFORSCOM.

h. Establish procedures for reporting departure of unitsas provided for in this regulation (chap 3, para 3-5d), "B"Type Record). Departure reporting is included in TCACCIS Installation Situation Reporting (SITREP)capabilities.2-9. UnitsCommanders of intermediate level units (i.e., corps, division,brigade, support command, battalion, regiment, troops,companies, batteries, and separate detachments) will-

a. Develop, report and keep accurate UMD using TCACCIS or FORSCOM approves alternative means.

b. Ensure marking of vehicles to conform to jointmovements policy This involves adequate labeling ofshipment units (vehicles, containers, pallets, and unitimpedimenta) to correspond with MILSTAMP compliantMilitary Shipping Label complete with TransportationControl Number (TCN).

c. Ensure major subordinate commands (MSCs)through battalions have IC-UMOs that support theirsubordinate units.2-10. InspectionsReports required in the regulation will be an item of interestduring IG and annual inspections of AC and RC unitsand installations.2-11. Air Certification ProceduresMilitary Traffic Management Command TransportaionEngineering Acency (MTMCTEA) is the U.S. Army centralpoint of contact for obtaining vehicle/equipment aircertification from the U.S. Air Force Aeronautical SystemsDivision (ASD). U.S Army units requiring Air Forcecertification should:

a. Prepare worksheets in accordance with MTMCTEAPAM 700-1.

b. Forward the request (letter, worksheets, photographsand weight tickets) to Director, Military Traffic Manage-ment Command, Transportation Engineering Agency.ATTN: MTTE-OAR, 720 Thimble Shoals Boulevard,

Suite 130, Newport News, VA 23606-0276 with aninformation copy furnished Commander, FORSCOM,ATITN: FCJ4-TRU, Fort McPherson, GA 30330-6000.

c. MTMCTEA will forward request to HQ Aeronaut-ical Systems Division/ AMC to obtain certification/ waiver.

d. ASD/AMC will review request and approve ordisapprove. Results will be returned to MTMCTEA.

e. MTMCTEA will notify the unit of approval ordisapproval and forward information copy of the resultsto Commander, FORSCOM, ATTN: FCJ4-TRU.

'. FCJ4-TRU will notify all other FORSCOM unitswhen certification or waiver is granted.

g. Questions related to Air Certification or Waiversmay be resolved by contacting FORSCOM FCJ4-TRUor calling MTMCTEA DSN 927-5268.Chapter 3Unit Movement Data (UMD) Reporting [RCS FCJ4-165(R2)]3-1. GeneralForces Command uses the Computerized MovementPlanning and Status System (COMPASS) to satisfy CINC,Army and Joint Staff UMD information requirements fordeliberate and crisis action planning, strategic mobilityanalysis and mobilization and deployment movementexecution.

a. The COMPASS is a FORSCOM unique operatingsystem that uses evolving computer technology withmultiple system interfaces that facilitate collection andmaintenance of UMD to support planning, strategicmobility analysis, movement execution, and command andcontrol for mobilization and deployment purposes. TheCOMPASS maintains direct interfaces with the Status ofOperational Readiness and Training System (SORTS),Mobilization Planning Execution System (MPES) and theJoint Operational Planning and Execution System (JOPES)among other command systems. The COMPASS uses TCACCIS as its primary source of unit maintained andreported unit movement data. A comparable interface isplanned with the RCAS when fielded. TC ACCIS andRCAS are the objective source data automation systems(replacing manual UMD collection procedures) to supplyU MD to FORSCOM for CINC and Joint Staff informationrequirements.

b. The FORSCOM J4, Transportation and ServicesDivision, Strategic Mobility Branch, Systems Sectionmaintains and operates the COMPASS to accomplish thefunctions described in paragraphs 2-la through f.3-2. UMD Reporting ProceduresInstructions for preparing and editing UMD input (usingFORSCOM Form 900-R Series Worksheets) and guidancehow to read COMPASS generated reports are containedin chapters 4 and 5. Camera-ready copies of FORSCOMForms 900-R series are available for reproduction fromthe local forms management office.3-3. UMD Update

a. Forces Command deliberate planning requirementsdictate that UMD be maintained current and accurate atall times. This requires that UMD be validated by allCONUS based units (as defined in this regulation) andupdated whenever a significant change in transportationrequirements occurs. As a minimum, reporting of UMDwill be accomplished in accordance with the scheduleprovided in figure 3-1, this chapter.

b. UMD updates are managed by CONUSA geogra-phical area. The schedule outlines the mandatory minimum


reporting cycle. Updates must be received at FORSCOMin a machine readable format not later than the first workingday of the month. Updates may be submitted up to 90days in advance.

c. Units that have no changes to report during thescheduled update period must submit a NO CHANGEreport. This is done by submitting the unit's UIC, TDC,new submission date and transaction code in the formatof the header record (described in chap 4). The UMC willprocess the NO CHANGE report with other updates. Unitsparticipating in exercises WILL NOT SUBMIT NOCHANGE REPORTS.

3-4. UMD Update Remarks.UMD reported must reflect planned movement require-ments or actual movement requirements preciselycorresponding to what a unit plans to move or is movingand how it is to be prepared or is prepared for movement(i.e. if an item is to be shipped in its operationalconfiguration it should be reported as such). UMD mustbe maintained current and accurate. UMD must reflectall personnel to be moved as well as equipment.

a. A significant transportation change is defined as anyincrease or decrease in movement requirements that resultsin addition or subtraction of one or more rail cars, semi-trailers, trucks, passenger conveyances (buses) or requiresthe allocation of more (or less) aircraft or ship deck space.For example, an increase of one vehicle, conversion fromthe M60 to M series of tanks or upgrade from an M IAltank to an MIA2 tank is a significant change to a changereport.

b. UMD is used for deliberate planning, strategicmobility analysis and transportation lift allocation duringmovements execution. Strategic lift allocations and defenseprocurement decisions are based upon UMD reported forArmy units. The accuracy of UMD reported is ofparamount importance.

c. Figure 3-2 illustrates the flow of UMD updates fromunits to Forces Command.

d. Figure 3-3 illustrates the return flow of AUEL anderror reports from Forces Command to units during theupdate cycle.

e. Figure 3-4 illustrates the return flow of AUEL reportsfrom Forces Command to units after the update cycle isfinished.

3-5. UMD Reporting RequirementsThere are four basic types of UMD reported by units.These type data are described as follows:

a. Mobilization Unit Movement Data (MOB UMD)reflects all Unit assets that are to be moved from the unithome station, alternate site or storage site to themobilization station and unit equipment located at themobilization station. MOB UMD is reported by RC unitsthat must move to the mobilization station. MOB UMDmust reflect what is moving and how it is prepared tomove (i.e. reduced, operational, reduced for sealiftconfiguration, et cetera).

(1) A MOB UMD report is required for each RCunit that must move to its mobilization station uponactivation. MOB UMD will be reported using Type DataCode "S".

(2) A separate MOB UMD report is required foreach subordinate unit element (vehicles, equipment andpassengers not located with the parent unit).


(3) A separate MOB UMD report is required forvehicles and equipment, only, in a unit storage site, (i.e.ECS, MATES, UTES, WETS, AMSA, et cetera).

(4) USAR units should submit UMD through theappropriate Support/Coordinating Installation (S/CI)according to AR 5-9. UMD for storage sites will be reportedthrough the parent unit's S/CI (by the owning/reportingunit). NOTE: This does not negate the unit's responsibilityto coordinate mobilization movement with the storage siteAR 5-9 designated installation transportation office. Figure3-2 illustrates the flow of UMD updates from units toForces Command.

(5) UMD will be reported via a separate report forunit equipment located at a storage site maintained andmanaged for Army National Guard units.

b. Preparation for Overseas Movement Unit MovementData (POM UMD) reflects those movement requirementsfor deployment only. POM UMD represents what a unitwill deploy and how it is configured (loaded and secured)for movement overseas by surface or air.

(1) A POM UMD report is required for eachdeployable AC unit and each activated/mobilized RC unit.

(2) AC units will review and maintain POM UMDcurrent and accurate, reporting changes as appropriate.In addition, AC units will review and validate POM UMDat least annually using approved movement plans asprescribed by FORSCOM Regulation 55-1 and submitupdates to FORSCOM IAW the schedule (fig 3-1) in thisregulation.

(3) Once mobilized, RC units will report POMUMD.

(4) All units will report POM UMD using Type DataCode "D" unless otherwise directed by this headquarters.

(5) POM UMD is used primarily for planningpurposes. However, POM UMD is used/may be used toinitilize deployment UMD for contigency or crisis actiondeployment of forces.

(6) POMCUS UMD is a special type of POM UMDPOMCUS UMD is generated for both AC and RC unitsfrom the Preposition Equipment Requirements List(PERL). Updates to POMCUS UMD by units are notrequired unless directed by this HQs for mobilization.deployment or crisis action movements. Questionsconcerning differences of equipment on the POMCUSAUEL and your MTOE should be addressed through yourUMC to the FORSCOM, J4 Plans and Operation Division,EUROPE/FORSCOM Plans Officer, DSN 367-7651.Figure 3-5 illustrates the flow of POMCUS AUEL reportsfrom Forces Command to POMCUS Units afterCOMPASS generation of POMCUS TAT/NAP andSHORTFALL UMD.

c. Tailored Unit Movement Data may be used for any,ecial purpose plan, exercise or contingency. TailoredMD reflects all unit assets that are to be moved from.e unit home location to an objective area. Tailored UMDay be required for Joint Training Exercise (JTX UMD),

Command Post Exercises (CPX UMD), Sea EmergencyDeployment Readiness Exercises (SEDRE) or any specialmovement requirement (such as disaster relief or civildisturbance). Tailored UMD must reflect what is movingand how it is to be prepared for movement via air or surfacemeans.

(1) A Tailored UMD report is required for each unitparticipating in an exercise, CPX, SEDRE or contingencymovement.

(2) A separate report is required for each unit/element moving as a separate entity or from alternatelocations.

(3) The frequency of the report will be defined bythis headquarters in tasking directives or supplementalinstructions. Tailored UMD will be reported using the TypeData Code (TDC) assigned by this headquarters.

d. Deployment Unit Movement Data (DEP UMD)reflects all unit equipment moving from the SI/MS byall modes applicable (i.e. Organic Air, AMC Air, Rail,Commercial Truck or Trailer, Convoy, Barge or Water Way).DEP UMD also includes personnel deploying by anconveyance (such as AMC Air to the theater of operationsor Bus to the Seaport of Embarkation (SPOE).

(1) DEP UMD is used to allocate lift resourcesagainst a planned move and for scheduling strategicmovements via air and sea.

(2) A departure report based upon DEP UMD isrequired for each Unit participating in an exercise, CPXor Contingency movement as directed by FORSCOM.

(3) The installation UMC is required to submit thedeparture report through TC ACCIS for units that departby air within one hour of airlift (wheels up) and within12 hours of the units' departure via any surface means(convoy, rail, commercial truck, etc.).

(4) The frequency of the departure report will dependon how the unit is moving. The "B" type record will beused to report departure data. See chapter 5 paragraph5-12j. It must be understood that each report must containthe UIC, TDC, ECHELON (also referred to as MovementIndicator Code), if required, ULN and DEPLOYMENTINDICATOR "B". Examples of different departure reportsare listed at figure 3-6.

3-6. World Wide Military Command and Control System(WWMCCS) and Management Data Query (MDQ)ProgramsWWMCCS is a Top Secret access system with data basesthat contain actual and exercise Operation Plan (OPLAN)data. OPLAN data is available through a Time PhasedForce Deployment Data (TPFDD) report. The TPFDDcontains movement information on units. Unit LineNumbers (ULN), available on the TPFDD. typically sub-divide the unit by transportation mode, ports ofembarkation or debarkation, and dates. Dates correspondto the established C-day on the TPFDD. The unit is phasedby relative deployment days into Ready-to-Load Dates(RLD) at origin (origin representing installation for ACand mob station for RC), Available-to-Load Date (ALD)at the aerial/sea port of embarkation (APOE/SPOE), andEarliest/Latest Arrival Date (EAD-LAD) at the aerial/sea port of debarkation (APOD/SPOD). The Transpor-tation Component Commands (TCC) schedule lift for theULN to meet the EAD-LAD window. The TCC are theAir Mobility Command (AMC), the Military SealiftCommand (MSC) and the Military Traffic ManagementCommand (MTMC).

a. DEPLOYMENT DATA - TPFDD report and air/sealift schedules are available through WWMCCS for agiven OPLAN. Management Data Query (MDQ) programshave been established in WWMMCS on catalog "MC76/MDQ". Type: "CATA MC76/ MDQ,A,S" at the timeshar-ing (*) level on the FORSCOM WWMCCS host to viewavailable programs. These programs may be downloadedto individual CAT; FILE strings and modified for user

unique queries. Contact FORSCOM 3 Current OperationsDivision C2 Systems, FCJ3-OCC, for further assistance.

b. MOBILIZATION DATA - Planning and executiondata for mobilization may be retrieved for contingency andselected exercise scenarios. Type: "MPES" for theMobilization Planning and Execution System at thetimesharing (*) level on the FORSCOM WWMCCS hostand follow the provided menus. Contact FORSCOM J5Preparedness and Mobilization Division, FCJ5, for furtherassistance.


c. Access to Unit Movement Data/COMPASS - AirliftPlanning Requirements Data, TUCHA, UMD and Tailoredreports are available through WWMCCS. ManagementData Query (MDQ) programs have been established inWWMCCS at catalog "MCC/ MC76". Type: "LISTMCCO/ MC76" at timesharing (*) level on the FORSCOMWWMCCS host to view available programs. Programscan be run as listed using "MDQ O", user must createtheir own CAT/ FILE strings for the reports to write to.Contact FORSCOM J4 Strat Mob Branch, SystemsSection, FCJ4-TRU, COMPASS for further assistance.

CONUSAGeographical Region

I (MW)

AC Reports(POM UMD)

OCTOBER

JULY

SEPTEMBER

JULY

APRIL

USAR Reports(MOB UMD)

FEBRUARY

DECEMBER

APRIL

NOVEMBER

JANUARY

NG Reports(MOB UMD)

JULY

MAY

MARCH

APRIL

JUNE

UMD update schedule for the two divisions at Foot Hood listed below are as follows:

1st Cavalry Division

2nd Armored Division

15 DECEMBER

15 SEPTEMBER

UMD update schedule for USA Special Operations Command (USASOC) Reserve Component units(RC) will be as follows:

USA Civil AffairsPsychological OperationsCommand

Special Forces Command

JUNE

JUNE

Special Note: USASOC RC units will report their UMD updates through the appropriate supportinstallation IAW AR 5-9 based upon their home location.

Figure 3-1. Unit Movement Data (UMD) Update Schedule.


DDN

tLAUTQDIN

MUSARC

USAR UNIT

AUTQDIN

-- FOR-TC ACCIS

INPUT

ARNG UNIT

KEY_____PREFERRED DATA FLOW

-' - OPTIONAL DATA FLOW

Figure 3-2. Flow of UNID Updates Via DDN or AUTODIN from the Unit to FORSCOMJ/COMPASS.


iFORCES COMMAND

MAIL MAIL

S/C UMCS/CI UMC

I

MUSARC -

STATE AG/DMCSTATE AG/DMC

-1

MAIL

USAR UNIT ARNG UNIT

Figure 3-3. Flow of AUEL and ERROR listings from FORSCOM to units during update cycle period.

MAIL

AUTO

'II:

FORCES COMMANDor

PIN

ICONUSA/USAR(

----- IS/Cl UMC

MOB STATION

MUSARC

I

MAIL

77f NGB~ IMAIL__ _ _ _ _ _ _ _

STATE AG/DMCSTARC

4

ARNG UNIT

Figure 3-4. Flow of AUEL and other reports from FORSCOM to units, NGB, USARC and CONUSAupon completion of UMD update.


USAR UNIT

AUTDI ~FORCES COMMAND

AIO I

STATE AG/DMCS/Cl UMC

MUSARC

USAR UNIT ARNG UNIT

Figure 3-5. Flow of AUEL and POMCUS reports from FORSCOMI to POMNCUS units after COMR\PSSgeneration of POMCUS, TAT/NtAP and SHORTFALL tUMND.


MAIL


MovementMode

Organic Air

Equipment

10 Helicopters Unitflying Helicopters tothe Port.

AMC Air 3 Veh

AMC Air 50 Passengers

Rail

Comm Trl

Convoy

Bus

Barge

Water Way

10 Veh, 5 pcs miscEquip Will have thesame date time andcontrol number.

5 loaded that are leav-ing at the same time.Must use GBL # foreach trailer as controlnumber.

10 Veh, these 10 vehwill have the samedate time and controlnumber.

40 Pax. Do not reportbus for moving per-sonnel to air field formovement by air.

Veh and Equip

Veh and Equip

Figure 3-6. Examples of Departure Reports.

Date TimeGp

MPE ControlNumber

Bus AirPax Pax

Ship UnitNumbers

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No Yes Yes

Yes

Yes

Yes

Yes

Yes

Yes

Chapter 4COMPASS Products4-1. COMPASS ProductsCOMPASS is a FORSCOM unique data system whichprovides informational products to facilitate planning andexecution of unit movements for Active and ReserveComponents. This is achieved by maintaining a centralizeddatabase of detailed unit movement data. This data includesmovement characteristics and movement configurationuseful to both force planners and transportation agenciesalike.4-2. AUELThe AUEL is the most commonly used UMD report. TheAUEL contains a detail (fig 4-1) and summary (fig 4-3)listing of the units' UMD. The detail listing reflectsindividual pieces of unit equipment, the dimensionalcharacteristics of the equipment, the mode of transportationand square footage. The summary reflects the detailinformation by mode of transportation, tonnage/squarefeet of equipment reported, and total movement require-ments. Figures 4-2 and 4-4 provides a Data Reference Tablefor Detail and Summary AUEL reports with an explanationof key data elements.4-3. Tailored ReportTailored Report is a summarized listing of units. It identifiesthe units by type data code, geographical location alongwith a summary by short tons/measurement tons of UMDreported. This report is helpful to UMC's/ DMC's inmanaging the units. It can be produced in various wayssuch as support or MOB installations, ARCOMs, CycleID, and Unit Assignment Code. Figure 4-5 is an exampleof a Tailored Report. This report is provided to UMC's/DMC's, SCI semi-annually and available upon request.Figure 4-6 provides a data reference table for the TailoredReport with an explanation of key data elements.4-4. Blocking and Bracing Material (BBM)Rail blocking and bracing material (BBM) data is compiledby the MTMCTEA based on current Association ofAmerican Railroads (AAR) loading rules. This data ismaintained by COMPASS and can be provided uponrequest to units that expect a rail move. For guidanceregarding stockage of BBM see FORSCOM Regulation55-1.

a. BBM data is developed for vehicles only. In theabsence of an approved AAR procedure, an estimated billof materials is compiled based on procedures for a similarvehicle. In some instances, a bill of materials has not beendeveloped and the detailed material listing is annotated"no data available".

b. BBM data is based on the loading of one vehicleon wooden deck rail cars. This could result in anoverstatement of BBM material requirements, particularlywhen loading involves double-decking or nested cargo (i.e.,piggyback) with vehicles loaded on flat bed trailers, or whenusing TOFC, bi-level, tri-level or chain tie down rail cars.However BBM data for tanks and tank-mounted equip-ment, has been modified to show use of AAR rules fortransport by unit trains.

c. The COMPASS produced rail BBM summary anddetail listings provide planners with detailed rail BBMrequirements for open top rail cars. Requirements on thelistings have been approved by the AAR as minimumrequirements for securing equipment onto rail cars. Thesereports are available on request but will not be producedand distributed on a routine basis.

FORSCOM Regulation 55-:

d. BBM Detail list. Figure 4-7 is an example of a detaillist which list BBM requirements for one vehicle. Multiplythe number of vehicles times the BBM requirement toproduce the total requirement for types of vehicle by lineitem number.

e. BBM Summary list. Figure 4-8 is an example ofa summary list which summarizes the BBM requirementfor the unit based on what the unit has shown on theirAUEL report.

f. BBM reports will list only BBM requirements forvehicles listed on the AUEL report requiring railtransportation unless otherwise requested.4-5. COMPASS BR and BV ReportsThe "BR" and "BV" reports are detailed/consolidatedreports used for planning of ship loads and provided toMTMC Area Command and Task Force directoratesduring FORSCOM directed exercises.

a. The BR is a listing by individual UIC indicatingvehicles and equipment reported by section entry number,Line Item Number, description, quantity, dimensional datato include short tons, measurement tons, vehicle squarefeet and Cargo Category Code.

b. The BV is a consolidated listing of all equipmentthat is on the "BR" by Line Item Number (LIN), quantityper LIN, NSN, description, dimensional data to includetotal short tons, measurement tons and total square feet.4-6. Preposition of Material Configured To Unit Sets(POMCUS) UMD

a. The Prepositioned Equipment Requirements List(PERL) is an U.S. Army Material Command (USAMC)product produced from the Requisition Validation System(REQVAL) which includes Continuing Balance SystemExpanded (CBS-X) using the following source files: DA..POMCUS Authorization Document (PAD), CombatEquipment Group, Europe (CEGE) Common Table ofAllowance (CTA) file, CEGE Unit-City Cross ReferenceFile and FORSCOM Mobilization Station PlanningSystem (MSPS).

b. The PERL is the source file used by COMPASSto generate POMCUS UMD. The PERL Report identifiesthe following types of POMCUS UMD:

(1) Items To Accompany Troops (TAT).(2) Items Not Authorized Preposition (NAP).(3) POMCUS SHORTFALL (equipment that is not

in place and must be shipped).(4) NAP-Deferred (not required within first 30 days

of combat).c. POMCUS UMD. POMCUS UMD is generated

movement requirements as listed on the PERL for alldesignated POMCUS units. This data includes passengers,TAT and NAP items (generated as Echelon 01). Authorizeditems of equipment not preposition in the overseas theater(SHORTFALL) and items not required within the first30 days of combat (NAP-Deferred) (generated as Echelon02). Updates are not required Should any question ariseconcerning differences of equipment or the AUEL andyour MTOE, please notify your UMC who will contactthe COMPASS office.4-7. Type Unit Characteristics Data (TUCHA)TUCHA Data is the movement requirement of a type unitbased on JCS authorized level of organization ALO-Ipersonnel and TOE equipment authorizations. It appliesto units of battalion and lower organization levels, and


for organizations above battalion. TUCHA UMD isp;repared by COMPASS only on request and is used fordeliberate movement planning. TUCHA UMD representsthe following

a. Pe,.onnel. One hundred percent of the basic DATOE authorization at ALO-1.

b. Equipment. One hundred percent of the basic DATOE authorization at ALO-1. Models included are thoseidentified as "preferred model" in the DA master file ofstandard equipment transportability characteristics forArmy TOE equipment. No CTA items are included.

c.- Accompanying supplies and ammunition. Quantitiesof accompanying supplies are computed on the basis ofpounds-per-man consumption factors prescribed by DA.Ammunition is computed IAW FORSCOM Regulation700-3 based on the number of weapons authorized in theTOE.

d. Report Level. TUCHA UMD may be generated forany TOE organization level, providing a valid StandardRequirements Code (SRC) are in the DA TOE master file.

e. Shipping Configuration. Vehicles and equipment arereported min reduced configuration, unless the individualitem is not reducible.

f. Organic Vehicle Loading. TUCHA UMD isgenerated with loaded or unloaded vehicles, dependingupon the purpose. When vehicles are loaded, cargo consistsof miscellaneous TOE equipment items only. Large/ Heavyequipment which are not loaded on cargo vehicles are listedseparately in the UMD listing, as are computed quantitiesof accompanying supplies and ammunition.To obtain this report, a nine-position SRC or UTC isrequired.4-8. To obtain the above reports, the UMC may write toCDR, FORSCOM, J4, Transportation and ServicesDivision, ATTN: FCJ4-TRU (Systems), Bldg 200, RmB074, Fort McPherson, GA 30330-6000. The followinginformation must be provided.

(a) Requesting units UIC(b) Description and location of the requesting unit(c) Purpose of the request(d) POC and telephone number

4-9. Example worksheets (FORSCOM Forms 900-Rthrough 900-5-R) are at figures 4-9 through 4-14 whichdisplays examples for Reserve UMD inputs.

UPDATED 07 JUN 93 <AKYJ O

DATE PRINTED 07 JUN 93

UNCLASSIFIED PCN 0445A RCS 'FCJ4-165(R1)

FORCES COMMAND (SPECIFIED)+ Co *6UfREIZ~b I4OVEMENT PLAI1NIN6 ANb STATUS SYTEM _(tmPAStJ _i I

AEL REPORT - UNT NV E11TT 'ATA II- -- ________ ________

UIC- WP54o0 H1YPE DATA: HA UFUIT I?1E:Q1rWTe 1f3 b 6-- --- TIb N: NA3IL-SA A..- __;L DFICEZDDEI 8GAT

UNIT & 1 SHIPMENT UNIT / (INCHES) ITE LOADED / PCM P CGO'7-NUMBER ULN LIN 1140 DE CRTTIOII MODEL I LT DHHT on UF IL3 IL5EP U~~CT SO -W--

oboni 02 ~X60833 02 TRUCk blt11t 1.74 1oW F151A2 9 T 32- 64 117 39 "-547 - z 5U - 43U 1VO867Z9 I -OUT - -2:4 14-TBCAC (A ) LOAD: -RADIO L MOUNT PCs= 2 371 2380 T DX

D0003 02 T61562 04 IRK UTIL CG3/TRP CARR M1038 W/W-- -- TB B - -P

D0004 02TUC P

179 84 53 105 462 5230 EMPTY 3 VO 867Z9 F OVR 2.6

161562 04 TRK UTIL CG31TRP tARR Al 038 W74 179 34 .5.3 105 '462 5200 EMPTY 3'VO 867Z9 FOVA 2.6 12

00005 0? 161562 U4 TRK UTIL CG3/TRP CATR M1038 U/W 179 84 53 105 462 5230 EMPTY 3 VO 867Z9 R OVR 2.6 12TBCCC01 - -- -

T61l?l 02 TRUCK TRACTDR 8X6 M920 320 97 126 216 2300 30220 4 VO 882Z9 U OUT -15.1

00028 0? X62237 09 TRUCK VAN EXP 5 T (A) M934___

TRECC01

00043 02 X4000? 37 TRUCK CARLO 2 112 TON (434.

365 98 137 249 2336 27828 EMPTY 4 VO bb2Z9 R OUT 13.9

?62 8i; 105 161 1401 11775 EMPTY 3 VO 867Z9 U OVR 5.9

F0002 02 YAO158 03 CONTAINER 20-FOOTI BC CC01

ECH R COMM -- OIVEENTRY & S AREA PFE- EXT- EXT O R MNUMBER ULN 0 CODE FIX (.SN PREF ALT RDYLD RAIL HEAD TOWN

HOO0l 0? T_464 669 357 7823 179; [07b FT GEORGE GI BC CC 01

H0)03 02 TOCAC TH IS AUEL CREAILD FOR FOR SCONl 55-2 DISPLAY

Z? 96 96 160 12,30 14710

CX TIRY

ST WJ~idER

%' - NJ00

OR IGINPAIL CARRIER

SOUiTHERwV RR-

J YC 70019 R OVR 7.4

ORIGIN MOTORST RAM~P LOCATIJN

-- -FT GE0 --I -

MOTOR CARRIER

BILLER- TRUtk n6

PAGE 1UI:LAIIIFTrD

D0026 02TODCAC

58

71

35

33

FORSCOM

Key #1234

Station

State (ST)GBL Office Code (GBLOC)

Shipment Unit Number (SUN)

ECH

ULN

LIN

Index

Shipment Unit Description

ModelW/I

Dimension

SQ FTCU FTItem Wt Lbs

Planned Loaded WT

Type Equipment (T/E)

TP PK

COMM Code

MPE

Regulation 55-2

Data ElementUpdatedPCNDate PrintedUIC

Type Data Code

Unit Name

Figure 4-2. Data Element Reference Table for AUEL Detail Report.

DefinitionDate unit sent UMD to UMC.Production Control Number.Date report printed at FORSCOM.Unit Identification Code - A six position alpha numeric codethat uniquely identifies an organization. (SORTS input onFORSCOM BIDE File).A code assigned by FORSCOM which (TD or TDC) identifiesthe type of UMD on file for different movement plans.Unit identiy - unit number, branch, and description. SORTSinput on FORSCOM BIDE File.This is where the unit is located (origin station). SORTS inputon FORSCOM BIDE File. NOTE: Origin station for storagesites (that is type data code SI-S4, S6, S7) is generated bythe COMPASS office and not on BIDE File.Unit Home State. SORTS input on FORSCOM BIDE File.Code assigned and used by MTMC for the Installation thatissues the GBL. (AR 55-355)This refers to the record type and entry number. Input bythe unit.A 01, 02 or 03 is required in this field for RC MOB UMDreporting. This should will be blank for AC AUEL reports.Unit Line Number input by unit extracted from a Time PhasedForce Deployment List (TPFDL). This field should be blankexcept when use of the ULN is directed.Line Item Number is a 6 alpha/numeric code used to identifyequipment type. TB 55-46-1 contains approved LIN's thatmust be varified against the MTOE.Index Number of the LIN number which identifies the differenttype models or component items of the LIN. (The Index canbe found in TB 55-46-1).Description of the units equipment based on the reportedLIN/LIN Index.The model of the item reported based on the LIN index.An "X" indicates that the Height of the vehicle has beenchanged because a load has been placed on the vehicle causingthe Height to be higher than the Cargo Load Limit Heightfound in TB 55-46-1 and the Equipment Characteristics File.The actual shipping length, width and height in inches ofeach item reported.The square feet of the item reported.The cubic feet of the item reported.The weight of the item reported. For vehicles that are loaded,the weight of the load will appear below the vehicle weight.The gross weight of the item reported. For vehicles that containa load the Vehicle Weight plus the Load Weight equals thePlanned Loaded Weight.The Type Equipment code of the item reported. See table5-6.The Type Pack code of the equipment reported. See table5-5 and MILSTAMP DOD 4500.32-R.The Water Commodity and Special Handling Codes forequipment reported. See tables 5-1, 5-2, 5-3) and MILSTAMPDOD 4500.32-R.The Mode to Port of Embarkation/Mobilization Station(MPE MMS) Shipment codes that were determined andreported by the unit. See table 5-4.

1516

Key #26

RDYLD

Origin Rail Head

Origin Rail CarrierOrigin Motor Ramp

Origin Motor Carrier

Remarks

Data ElementCGO CAT

STON

MTON

Remarks

Contingency Stamdomg RouteOrder (CSRO)

Area Code

Commercial Prefix

DSNPhone Ext Pref

Phone Ext Alt

Figure 4-2. Data Element Reference Table for AUEL Detail Report (Continued).


DefinitionA Cargo Category Codes generated using the Second Positionof the Cargo Category Code listed in JCS Pub 6, volumeII, chapter 1, Part 5, as follows:NAT Not air transportableOUT Outsize will fly in C-5 only.OVR Oversize will fy in C-141 or C-5.BLK Bulk Cargo with dimensions less than oversized cargo.The weight in Short Tons of the item being reported. (STON2,000 pounds).

The Measurement Tons of the item being being reported.(MTON cubic feet / 40).Explanation, clarification or additional information requiredon the AUEL.If a CSRO is desired, a "Y" is reported indicating "yes". Ifso, data must be entered for data keys 31 through 40. If an"N" (indicating "No) is entered, then keys 31 through 41will be blank.The commercial telephone area code number of the ITO orSTARC office.The commercial telephone prefix number of the ITO orSTARC office.The DSN number of the ITO or STARC office.The preferred telephone extension number of the ITO orSTARC office.The alternate telephone extension number of the ITO orSTARC office.Ready to load date this is an estimate of the earliest datea unit is expected to be ready to move out from origin. Itcan be obtained from the Installation or TAG MobilizationPlanning Officer.The name of the Rail Head Town and State where theequipment may be loaded on Rail Cars.The Rail carrier that may be used to transport unit equipment.The name of the Ramp location and State which may beused to load unit equipment on trucks and trailers.The Motor Carriers name and State which may be used totransport unit equipment.This location on the report can be used to enter remarksthat provide explanation or clarification of additionalinformation about the unit.

UPDATED C? JUN 93 CAKYU U:L SI E C C46C1-0 p.PCN 4 43

DATE PRINTED 0? JUN 93 ©9 FORCES CO4MANJD (SPECIFIED)''*COMPUTERIZED MOVEMENT PLANJNINGAND6 STATUS SYSTEM (COM'PASS) R'. *

__ - - -- AUEL REPORT -UNIT MOVEMENT DATASUMMARY

UIC DAT UNIT NAME TPSN SRC UTC STATION ST AIR Sr SEA-EAST

WP5JD0 MM 0,~9 IN BN 03 CO D 03028U~j 78L00100 OAVNN MANSFIELD PA LA LEY VA NORFOLK

-MOBSTATIO -FTPICKET VA - SUPPORT/COORD INSTL: ANNVILLE PA. CYCID: USNG1 ASG C

(9 (o NITPASSENGERS. NO-ULN : 92 TOCCCOi: : TBCAC

OF EMBARKATION---------

ST SEA-SOUTH ST SEA-WEST ST

OD:PAl h-

TB6P iD

CARGO. (FOLLOWING SUMMARIESAPPLY T5 _ALL UNIT CARGO.)

BULK- V 1ESTON MTON OTT STON -MTON

.0 0 5 21.) 102

(8)lIEH ICLENON- S P

7 _ 045,1- - - .b

212 01000 0

VEHICLE TOTALSQTY SION MTON SQFT

7 45.1 212 1000

(C) (D) (E) (F)VEHICLE TAI:K ARTY ARTYTRACKED COKGAT SP II-SP

G 0 _0 0.0 G .0 .. .0

0' 0 0 0G 0I 0 0

OUTSIZE

OT/' STON MTON

3 30.2 142

NON-AIRQTY STON4 MTON

O .0 0

HAZARDOUSQTY STON NTON

U .3 . -._:

(G) (H) (I) NON ---------- MODE4CFT WATER VEHICLE VEHICLEVJSD CRAFT TOTAL TOTALS RAIL (R)- - - - -- (SUM A-H)----------- TRUCK (t)

O0_ 0 _7 1 INSTL (I).0 -. J-- 5 75 RGANIC (J)_0 0 212 32 ORG AIR (A)(0 0 1000 163 'lAC AIR (F)

RAI Lp COMMERCIAL TRUCK &I bUS RE~lUIREMINTS (I TO/STARC (STIHATFS).

RAIL - - - - - - - - - - --- - - - - - - - - - - - - - - -- :JM ,IEHCIAL TRUCK- - -

54' 5°,'

54' 60' 89' 11 PR Si' 65' Dook 0711( DPOPCTD CTD C TD TUFC COrE Liif 1i a I G040 GOND Hvy I4VY CidTUSF FRAME LUIFI

1 07 0 0 0 1 I I) 0 0 '3 ' 0

4.I' 45' 48'FLAT FLAT FLAT

UY BED I3ED BED

UNIT TOTALS

*- STON NTON

52.5 - 2146

TO POE SJMI4ARY--------OTY STON MTON

3 23.8 1140 .0 0

20'SEAVAN~

.0

.05.2

0

023

COM'L COM'L

TRUCK

EUSES TRACTOR

1 D _.

AIRLII1i 9EQUIREHINT fSTIAAlF.NO0I F

(DO NOT ORDER AIR CRtAFT I ASIL )I.THE St F ST IFIA1ES, JSE F OR PL 44I't-PURPOSES O'IY)

COMPASS CFrICE - AJ1OvON ,S-/'I'T

AIRFRAME RI Hit RtMEITSC-1 41

AT 34.9 STOI/1UISSION

FOR PASSENGERS a CARGOC- 5A

AT 08.9 STON/II1SSIOR

U'+:LA.i IEI 0PAE

(A)VEHICLE

SPTOTAL

QTYSTON

MT 0ONS QF T

UNLASSIFIED RCS FCJ4-165(A1)

PAGE 5

Key #1234

TEAM

ULN

ECH I

ECH2

ECH3Total Pax

Bulk

Data ElementUpdatedPCNDate PrintedUIC

Type Data Code (TD or TDC)

Unit Name

TPSN

SRC

UTC

Origin Station

STAir POE

Sea-East

Sea-South

Sea-West

MOBSTATION

Support/ Coord Installation

CYCID

ASG Code

Figure 4-4. Element Reference Table for AUEL Summary Report.


DefinitionDate unit sent to UMC.Production Control Number.Date report printed at FORSCOM.Unit Identification Code - A six position alpha numeric codethat uniquely identifies an organization. Must be in SORTS.If not, will not be entered in COMPASS data base.A code assigned by FORSCOM which identifies the typeof UMD on file for different movement plans.Unit identity - unit number, branch, and description. SORTSinput on FORSCOM BIDE File.Troop Program Sequence Number (used to group units bymission and type. See AR 18-190. SORTS input onFORSCOM BIDE File.Standard Requirements Code (a nine- position code thatidentifies a basic unit). See AR 310-49. SORTS input onFORSCOM BIDE File.Unit Type Code (A five position alphanumeric code developedby JCS which uniquely identifies a type unit). SORTS inputon FORSCOM BIDE File.Unit Home Station. Unit location. SORTS input onFORSCOM BIDE. NOTE: Origin Station for storage sites(that is with type data codes of Sl-S4, S6,S7) is generatedby the COMPASS office and not on the BIDE File.Unit Home State. SORTS input on FORSCOM BIDE File.Preferred Air Port of Embarkation. Managed and maintainedby FCJ5.Preferred East Sea Port of Embarkation. Managed andmaintained by FCJ5.Preferred South Sea Port of Embarkation. Managed andmaintained by FCJ5.Preferred West Sea Port of Embarkation. Managed andmaintained by FCJ5.Station where unit will deploy from. Managed and maintainedby FCJ5.The Installation that provides logistical Installation andadministrative support. See AR 5-9 for Installation areas ofsupport.A special purpose code assigned by FORSCOM for datamanagement.A special purpose code assigned by FORSCOM for datamanagement.A special purpose code assigned by FORSCOM indicatingthe FORSCOM Army Area manager responsible for thereport.Unit Line Number in put by unit extracted from a TimePhased Force Deployment List (TPFDL). This will beFORSCOM directed.RC personnel requiring commercial transportation from originstation to mobilization station. Input by unit.RC personnel moving from origin station to mob stationorganically Input by unit.Used as directed by FORSCOM.For AC this reflects aggregate strength. For RC this is computergenerated based upon the total pax that were reported inECH1 and, or ECH2.Total bulk cargo of unit.


Key # Data Element27 Oversize28 Outsize29 Non-Air30 Unit Totals31 Vehicle Totals

32 Hazardous

33 Vehicle SP

34 Vehicle Non-SP

35 Vehicle Tracked

36 Tank Combat

37 Arty SP

38 Arty N-SP

39 Acft NSD

40 Water Crft

41 Vehicle Total

42 Non Vehicle Total

43 Mode to POE Summary

Rail, Commercial, Truck,Bus Reqiurements

Air Frame Requirements

DefinitionCargo that can be transported in a C141 or and C5 aircraft.Cargo that can only be transported in a C5 aircraft.Cargo that cannot be transported in any aircraft.The total bulk, oversize, outsize, and non-air cargo.Number of vehicles on the detail report plus the STON,MTON, and Square Feet (SQ FT). SQ FT for all vehicles.Number of pieces of equipment on the detail report that arehazardous.Number of self-propelled vehicles on the detail report plusthe tonnages and SQ FT.Number of non self-propelled vehicles on the detail reportplus tonnages and SQ FT.Number of tracked vehicles on the detail report plus thetonnages and SQ FT.Number of tanks on the detail report plus the tonnages andSQ FT.Number of self-propelled artillery pieces on detail report plustonnages and SQ FT.Number of non self-propelled artillery pieces on the detailreport plus the tonnages and SQ FT.Number of non self-deployable aircraft on the detail reportplus tonnages and SQ FT.Number of watercraft on the detail report plus tonnages andSQ FT.Total pieces of all vehicles on the detail report plus tonnage-and SQ FTTotal pieces of equipment from the "F" entries on the detailreport plus tonnages and SQ FTThis is the total quantity and tonnage of equipment on thedetailed report indicated by the MPE/ MSS codes that arebeing shipped to the SEA-PORT or MOB-STATION. Seetable 5-4.Estimates reported by the ITO/ STARC. These estimates arefor planning purposes only and will not be used to ordertransportation.Estimated number of C-141/C-5 aircraft for Personnel andCargo. These estimates are for planning purposes only andwill not be used to order aircraft.

Figure 4-4. Element Reference Table for AUEL Summary Report (Continued).

DATE 03-2293O

DATE 03/22%93 QHDBL

UNCLASS IFIlED_______

EX-TALRD

FORCES COMMAND (SPECIFIED)__- - T COMPUTERIZEV7- UDVENI PNNTNrATD ST~iTUQSSTET 7COF1P5 WI --- .------- - _

- -- - - - -. FTLt L.S ANGFO FRS3M5= -

~J ~ 'ASG HOME- - UNIT DESCR IPTT1)N- - SRC -. --. TC --- S '-='"YCID--TATTOJ

(/3)SPT\COORD MOB

_BST "STATIOW -ST -sTATrom~ 53TSUBM

-- DATE FAX"_ST09 1 D~*-~-

LJABIAA L 01DI_ ABL.AB5AA L 0101 AD

CO 1

WACRO 1

T4F12TJ7 1

IWrFAA 1

LJI'rNAA1.IDL Jr1CI. DO-n4 I

WF?.-..1

tYGGl~uA I

EIJI" CF L

u-SLU032003200326

04260801Jul.. L HHL NV'JI I 3ZA4'4 L U V 73

0101

C, ' 17

01010129-0 3373-01 C1( '10502

HFTC HNC 02

EN 01B - 01

BN

FN

DN 09

COBN 08BR"ETTW-EN 07BN 01BN 03

A3SUT _UT b70O4L0O 0V327 05101 0V3 =9AASLT BD 67042L000

CO C 105 06707L000lOST- T 06705LO00CO B 08027J500CO B 42067L000CO B 43067L000

CBT AVN

SUIPPOR TTERMINALAV MNT CHH-D CORP

B C'J MIEDATK HELAASLT

5'I31LVVV

01 205L000634722L00556327L000019?-7LOOD63426L000

551 o,'7J10O013B5L20007055L000

0W322 05101

1V322 051011T322 05101

FXVVV 05101JE227-05101HJ222 05101

3P222NBF22UHF:NN36522N2 1VVTJuOT

UA33337422OE 222

05101

32441357260510131171

35 /

051010510105101

0V3 OV-93

VOV3

0V3flV3DV3

0VJOV30V3OV3OV 3

LIV 3

OV3

O'13OV 3

OV-Y3

OV -93OV- 73OV- 93

uV-93JOV-93OV-93OV-93OV- 93

OV-93OV-93OV -93

FT-CA PBL VKYFT CAMPBL'KY11 LAMPIL KYFT CAMPBL KYFT -A14FBL KYFT CAMPBL KYFT CAMPBL KVFT CAMPBL KY1-1 kiNQL.L NL

FT CAMPBL KYFT CAMPBL T<YFT EUSTIS VAFT CAMPBL KYFT CAMPEL KYFI BKA6l4 FI

FT CAMP'BL KYFT CAMPUL KYFT CAMPBL KY

FT CARPEL-7KY -FT- CA FPLRVFT CAMPBL KY FT CAMPBL KY

FT CAMPEIL KY FT -CAMPEIL KYFT CAMPBL KY FT CAMPBL KYFT -CAMPBL: KY FT -CAMPBL KYFT CAMPBL KY FT CAMPBL KYFT CAMPBL KY FT CAMPBL-KYFTB CAPBL FT CIAMPBL KY

FT CAMPBL KY FT CAMPBL KY

FT CAMPBL i<Y FT CANFEIL _RY,FT EUSTIS VA FT EUSTIS VAFT CAMPBL KY FT CAMPBL KYFT CAMPBL KY FT CAMPBL KY

I1KML.L

CAMPSLCAMPSLCAMPS.

-NC-FrRTuuFC'

KY FT CAMPBL KYKY 7T CAMPEIL KY

LKY FT CAMPBL KY

------- - - --~ - -- --.--

0BFEB93 44.6 YFRKLN I

08FEB9308FEB9308FEB9306FEB9308FEB93s~JMP4Y3 ~V.7 I

08FEB9308FEB9321JAN9308FEB9308FEB93

08FEB9308FEB93

133.6

33.687949.1

460.8 Y150 73.-5 Y

10 217.9 Y109.3 Y941.5 Y

218.1 YA4-.6 Y

193.8 Y

- -- - ----- -- - - -------.--- - - - - -- --- - _*- - FACPATF TTiAhESRRTT0NS:.- 37- 1T--- -

LISTING OF UNI1TS-. Ni.UiE:ER OF RECORDS-- -

END OF REPORT

PACE i OF i~ PACft

r~r ~f~rIT1HII l_ LASSIFIE1D

PU~IC D~

11I v ' ttrlr

r F?;rFn1114E II

/Ph A


Key # Data Element1 DATE2 UIC

3 TYP DAT

4 UNIT DESCRIPTION

5 SRC

6 UTC

7 TPSN

8 ASG CDE

9 CYCID

10 HOME STATION and State

11 SUPPORT STATION and State

12 MOB STATION and STATE

13 LAST SUBM DATE

14 PAX

15 STON

16 UMD

DefinitionDate report printed.Unit Identification Code. A six-position alpha numeric codewhich identifies a organization. Changes to UICs are donethrough SORTS and maintained on the BIDE File. NOTE:Last two positions of UICs ending with "ZZ" is COMPASSassigned and is not SORTS input.Type Data Code. A code assigned by FORSCOM whichdescribes the type of Unit Movement Data associated witha movement plan. It also enables a UIC to be placed onfile for different movement plans.Description of the unit by unit number, branch, and typeof unit. Changes to Unit description are done through SORTSand maintained on BIDE File.Standard Requirements Code. A nine-position code thatidentifies a basic unit See AR 18-190. Changes to SRCs aredone through SORTS and maintained on BIDE File.Unit Type Code. A five-position alpha numeric code developedby JCS which uniquely identifies a type unit. Changes toUTC are done through SORTS and maintained on BIDEFile.Troop Program Sequence Number. Used to group units bymission and type. See AR 310-49. Changes to TPSNs aredone through SORTS and maintained on BIDE File.Assignment Code. A special purpose code assigned byFORSCOM for data management. It may be used to identifyparticular groupings of units (i.e. assignment code of 5Crepresents 5th Army 102d USARCOM).Cycle Identification. A special purpose code assigned byFORSCOM for data management purposes. The code mayalso be used to identify components by Army Areas.Unit location. Changes to HOME STATION made throughSORTS and maintained on the BIDE File.The Installation that provides logistics and administrativesupport. See AR 5-9 for Installation areas of support. Changesto Support Station can be accomplished through FORSCOM.Station where the unit will deploy from. Managed andmaintained by FCJ5.Last Submission Date. This reflects the last date unit submittedUMD to FORSCOM. The submission date is updated throughunits input. NOTE: The word PARENT is also found in theLast Sub Date column, PARENT is placed on file byFORSCOM and not updated by units.Passengers. Total number of personnel requiring transporta-tion. PAXs are obtained from the units UMD submission.Changes to PAX is done through units submission of a Headerrecord.Short Tons. Information for STON is taken from theFORSCOM UMD Data Base where the units reported UMDresides.Unit Movement Data. A "Y" indicates that there is data onfile, a "N" indicates that there is no data on file. PARENTreports will always reflect "N".

Figure 4-6. Data Element Reference Table for Tailored Report.

UNCLASSIFIED

COMPUTERIZED MOVEMENT PLANNING AND STATUS-SYSTEM (COMPASS)RAIL BLOCKING AND BRnCING MATERIAL DETAIL LIST

*--- - PCN0493A- *-

DATE: 11 MAR 93

PREPARED FORT FOR FORSCOM REG 55-2 DISPLAY

(AAR = ASSN OF AMERICAN RAILROADS RULES FOR LOADING OPEN TOP CARS)

V EH4ICL E- LTN - IESCRIPTION--- - -_ - OTT -

EMPTYWT- (LB r- --- AAR R~EFERENCE- --OTHER REF - -uPFREF ERE~CE-- -

ENTRY MATERIAIL DESCRIPTIrON, AAR RULES -AND REMARKS - UANTI1TY -- ENGT'tNt---WEL~NT-t-- ---NO (EACH) (EACH) (EACH)

01 MAT RORD FOR 3-AXLE VEH

RL 1.2- 03 BLOCK PAT NO16 SEC 6 12tEFERENCEF-APPENDIX R TM 55°2200.001=12'

LUM8ER,6X6 IN:.(ROR FOR CONST OF BLOC( PATTERN --

05 NAIL,401) 60__ _ USI-I hATfRI~L.PAPER

*(REFERENCE APPENDIX M TM 55-2200-001-12t0? -- CUSHIONING MATERIAL;BJRLAP -- 6'

*~(SUBSTITUJTE ITEM FOR ENTRY NO 06)

08 BLOCK PAT N0.89,SEC 6 6

* (ROR FOR CONST OF BLOCK PATTERN10 -LUMtBER. 2X4 IN: -B 1

*(ROR FOR CONSI OF BLOCK PATTERN11 - NAIL-il2D - 30

(ROR FOR CONST OF BLOCK PATTERNt 12"f. 20b

(ROk FOR CONST OF BLrK PATTERN16 ---- META1L FILLER,1&CAUGEtIN 4

** (SUBSTITUTE ITEM FOR ENTRY NO 15)

17

18

19

WIRE ROPFILIPC 3/B 1-4.----- (Ott-Y FOR-VFP-i 1d~ Elritft-H;3S0O-T t-2Y00tBS

CLAMP,3.'? TN.

- * (ONLY FOR VEHICLES WEIGHING 8.500 Ti) 16,000 LBSTHIM-BL,-3/8 IN.

* (ON'LY FOR VFHrCfRf WE IGH-lN6 P., TO 160(10 t BS** (SS'j1I [rTr ITEM rOP ENTRr 14IS

120

1. DO NOT USE Dim). .~ye P4 I.O-tOfy~lltr ;-- (CMPI-ITING COSTS- LUMBER t. NAILS RFOLIIRFD FOR CONSTRUCTION ARE SEPARATELY IDENTIFIED.

?: S --- M- -? .. '. -l u -r f t + !',N -j- hE tirSE 0F--fHIF3-DE At IASTiNJ ALSO; i£CMNICAL--A5SiSTAMPE-IIAY-BE O8TAiVE-----F)rflM MTHC TF:FJ: EtjrErIr Af.Fir r r~n* £,.0- ~27,1. NEWFORT NEWS. VA 23n6 ( AJ1)OVON 927-5266 OR COMIL (804) 595-7972

IJNCLAS! ,1F E DPAE -

APPLIES TO

36

PAGE 1

UNCLASSIFIED

COPTRZDMVMN LNIGADSAU YTM(OPS)FAIL FLOCKING AND BRACING MATERIAL. SUMMARY DATE: 11 MAR 93

PREPARED FOP: FOR FORSCOM REG 55-2 DISPLAY

(COMPUTED BY PURCHASING AGENT)- - _- --- - -TOTAL -- -OA- - -TOTAL---- -- TOTAL -tOSTt -COST-"05O'S~tSTTAit_ _

MATERIAL DESCRIPTION QUANTITY LINEAR FT BOARD FT WEIGHT (LB) BD FT LB ITEM COST

BLOCK PAT NO.16,SEC 6 12

BLOCK PAT NO.89,SEC 6 6

CLAMP,3/8 IN. 20

LUMBER,2X4 IN. 18 36

LIJMBER,2X6 IN. 6 18

LUM-BER,6XB IN. 3 72

NAIL,* 20 30 1

NAIL, 20D 90 3

NAIL, 400 60 4

WIRE ROPE,IWRC 3/8 IN. 4 40

THIMBLF ,3/8 IN. 4

CUSHIONING MATERIAL.PAPER 6 12

NOTES:

1. DO NOT USE BLOCK PATTERN O"1ANTITY FOR COMPUTING COSTS: LUMBER &~ NAILS REQUIRED FOR CONSTRU.ITON ARE SEPARATELY IDENTIFIED.

?_ SEE - TM-5 ??00D-011 - FOR 'S P'crTIm IN THE USE OF THIS SUJMMARY LISTING. ALSO, TECHNICAL ASSISTANCE MAY BE OBTAINEDFROM MTMC TRANS ENGINEERING AGFN~i. P.O. BOX 6276. NEWPORTS NEWS. VA 23606 (AUTOVON)927-5627 OR COML (804)599-0161 - '

11HF: 0454 UNCLASSIFIED PAGE 3

ICOMPUTERIZED MOVEMENT PLANNING AND STATUS SYSTEM (COMPASS) JORqieet Ito~mufor,ioi6 UNIT MOVEMENT DATA WORKSH-EET Pag I ftequuvcmenii Coniiaitymha

KF Y PUNCH INSTRUCTIONS IFOR AUTODIN TRANSMISSION INSTRUCTIONS REPORTING UNIT INSTRUCTIONSPunch all preprinted entries for card columns 18 and 80 I (See instructions below) See Chapter 5, FORSCOM Reg 55-2 for instructions on

I completing header data entries.

Type Report Column 791IEADE RDATA (This data must be included with each UM0 report) "A' = Add, "C'= Change

C 01 02 03 04 05 06 07 08A E E E E f E l k Aii C' C C c ( C C C RD 44 R N N' ii 4 H H.. _

ldentifamn I neNoi S 5,bmn onDat i al l Echeion - (Echeion I. Echlion ( Echeion ( Echeo Li Ftihelon ( EChtiin ( EthteionC~i ID tUIN N P 1 .anle Strenit 0 Stirengthi 0 Strenlgthi 0 Stirength 0 Striength 0 .Strength 0 Strengith 0 Strength 0 StrengithinI 06) UN 87 N N N N* N N N N E

S1 4 Si I B 9 0 .I1 f3 4iS5611 1 II 1 13 4 5 6 78I 0 111343 IiA 91112414 a5 6Ji~ 4T Ja 41211T 1 S 6IJ S1~J R Ei14 0it 66 t,J A 6 0 I~ I jj~j J 67B ag u

INSTRUCTIONS f OR AUTODIN TRANSMISSIONS- Transmit to Forces Command, Routing Indicator RUCIBJA,

Send PRIORITY Precedence, UNCLASSIFIED, With one of the following Content Indicator Codes:

AGCA Will be used (fo XMissions from Installations and States in the First US Army Area

ALFA Witl be used for XMissions from Installations and Slates in the Second US Army Area including theCommonwealth of Puerto Rico and the US Virgin Islands

AIF8 Will be used tor XMissions from Installations and States in the fourth US Army Area including WesternCommand area including Hawaii and other Paulic~ Islands and Alaska

AGCB Will be used (or XtMissions from Installations and States in (he Filth US Army Area

AGCC W-11 be used for XMissions from Itnstallations and Slates in the Sixth US Army Area

AJEC Will be used lop XMissions from Installations and Stales participating in Exeicises

lf0RSC0Mio~m In-Is ifl(tIi6(II(N1 iniiUiiiR ii II , tMU~ XiAUStIii1" t

COMPUTERIZED MOVEMENT PLANNING AND STATUS SYSTEM (COMPASS) tqsmnCtoISmoFonn1 aIS UNIT MOVEMENT DATA WORKSHEET Page at i Pget1C3-16(R2) mo

IORSCOM Rr 52 (Use addomonal FORSCOM Forms 900.1 .A hould (ontunuant eneccuarKEY PUNCH INSTRUCTIONS REPORTING UNIT INSTRUCTIONS TRANSACTION CODE (TC) (Cohn 79)Duplicate data entered in columns 1-7 in all cards applicable to a report. Punch all See Chapter S, FORSCOM Reg 55-2 for instructions on completing A = Addpreprinted entries far card columns 58 and 80. vehicle data entries. C = Change

D = DeleteVEHICLE DATA ______ ___ ___________________________________

E C M CC A PA

0 aUt E Unt 3Line

Identifiation L ieUi7te n Ctodfe 0 ,n No Pte int- Nn Je , Height 1 DW10i SD (ULN) E No II N) No C C S I (inches) D

1 2 3 4 5 6 78 9 11121)4 15 16s 1 1 19 221 12223 2 25 262172 199 31 32 33 34 35 3 31 3 3914141 4243 04 4

S 4 c) 41495 51 52~ s3 55 S i 57 59 6 61 b261 6 65 6 67 6 69 7 1 3 7 5 1 1 7 ti

sTV A S1 I aD 14

sv &<sr w / 'Ti .Wirt 9 9'

S V i r

0 .: M

S a Q qF 3 a A T.0

i* sr v A - H6r-4 f kIf0

Ssn~.~ & 6usm ,VU x-er 4

ii. 4

7Q

!r

y

Iw

C7

0

C4

M

wt

f9!

G.

to

C

A

t j

FORSCOM FORM 900.1- , I IUNE B8 EUMUNIOE I0E18515nASOlt t

COMPUTERIZED MOVEMENT PLANNING AND STATUS SYSTEM (COMPASS) RqieeuCnrlSmoFumo6UNIT MOVEMENT DATA WORKSHEET PaZ __FC4tSC?

FOmof ORSCOM Re 5S-2 Use additional FORSCOM Porint 900.2-N should continuation be~ neces....g Of ____Pages ReuirestintSymbo

KEY PUNCH INSTRUCTIONS REPORTING UNIT INSTRUCTIONS TRANSACTION CODE (TC) (Colmr 79)Duplicate data entered in columns I17 in all cards applicable to a report. Punch all See ChapterS5, FORSCOM Reg 55-2 for instructions on completing vehicle A = Addpreprinted entries for card columns 18 and 80. load data entries. C = Change

D = DeleteVEHICLE LOAD DATA_ ____________________________

C CC A At

H D _

JdeSnfcauo L Uit SUN y Unit T Description Load0

(UJC) TD0 N (ULN) r No No Load Description Items E Pack (Pounds) CurFtD

I2I7Ij3tj- i 7En9011r1141516 2 8 9 2)2 2 2 2415162L8 2 3 34

3233343536576667686494 4 4546708 9 [0 1 7?5 5 7155 76016 346766689707 78171.16 92B 0ii I I I i~I 11111 Ill I I ii I SS IU5TTU

C-

0

n-

FORSCOM FORSM 900-2"R. I JUNE 88 I DITlON OF I OC T 85 IS 08SOLEIE

9j~ Ql

til 0urJH'l

'IitoIVI

;S u s o sJE qc. sc Eu ~P49 f

j 2 - I5V SFc o y Sc-51

COMPUTERIZED MOVEMENT PLANNING AND STATUS SYSTEM (COMPASS)A e CIFionniofs UNIT MOVEMENT DATA WORKSHEET Pag ______mmr6 (RZ symPges

rOASCOM Re 55.2 Useadtoa OSO om 903Aiol oulo e necessaryKEY PUNCH INSTRUCTIONS REPORTING UNIT INSTRUCTIONS TANSACTION CODE (TC) (Colmn 79)Duplicate data entered in columns 1- 17 in all cards applicable to a report. Punch all See Chapter 5. FORSCOM Reg 55-2 for instructions on completing special A=Add

printed entries for card columns 18 and 80 handling cargo data entries. C=ChangeD=Delete

SPECIAL HANDLING CARGO DATA (Other than vehicles and vehicle loads__________________C M C

EA PA( R F A

Unit Eidenticttaon L unit Line I Unit In. Water T' 5 M Individual T

Code 0 No a Entry Line item den COMM C C M Length Widlh Height ttemWeiqhu I Type Description of tem oIUICI TD N (LthI No No(LiNI No Code C H S (Inches) (Inches) (inches) (Pounds) E Pack

I 73 4S 7 91II1

13 [ tS~ t l 1 t? 2 2 2 5

2 272029 3 313233 335 3 371343914 41 4 43~ 4454647 449--------5 S 55961663166S 6 66 69 7 ,,77]2r 7,' 77 -

4r 2 rR~t _ F¢ 3 ¢ ' ' 9 P

sr s F. ¢. s1 PI-1 9

1

ses V/ S '.0 ~ q1 K ! f 77. P 9

S2 S /FI 00 L4 9

' / v f itC3 / :14

S 1V F 1 37q

y 9

9

9

9

65 5 OSO~t i

0

U,

0d

I0

C)

0i

Y7y.0

(-)

COMPUTERIZED MOVEMENT PLANNING AND STATUS SYSTEM (COMPASS) eumntonrlsblform ot 6 UNIT MOVEMENT DATA WORKSHEET Page .2L. of lA Pages F04.16S 82

FORSCOM~p 55-2

KEY PUNCH INSTRUCTIONS REPORTING UNIT INSTRUCTIONS TRANSACTION CODE (TC) (COM 79)Punci all preprinted entries for card columns 18 and 80 See Chapter 5. FORSCOM Req 55-2 for instructions on completing A = Add

Rail, Commercial Truck and Bus Requirements (ITO Estimates). C = ChangeD = Delete

RAIL COMMERCIAL TRUCK AND BUS RE UIREMENTS ITO ESTIMATES

[ A C - AC R AH 0 54 68' 8 0

Uni I Unit T53' 65' DOD DOD 0 40 4C4 o-40el'Oacn L ine 5. 4 60' 89 BI TRI Gon Con Hvy Hvy 0 F~tFa t 20 40' ach truck, (i(,ril 0 No (t CI tCI (t) 10 (0 Lev Lev do dio Dry Dry S RipLwled lied iid Sea Sea at flat 1 D

It ~ TD N JULNI t fat flat ilat r( rc el el la la Ft C t ran Eo Ill Ill 1i Van Van Bus iori

1 4 S6 I R 9 I it12 1 )1 4 tI 1611I i97~ 22121 )57 72 91311i 4131 153S 173 194 445535 474 57 x r66s64666 67686977170It11 75is'4i 177 iiiu

INSTRUCTIONS FOR COMPLETING CARD TYPE "J" AND "' FORSCOM FORMS 900.4-R AND 900.5-R WORKSHEET.

Card Types - I and "H Worksheets must be completed by the installatton/Slarc Transportation Officer/UMC prior to submitting initial or update data tof orces Command

USAR Units not assigned to their MUSARC's Support Coordinating Installation (SCI) must have their Card Type "1" and "H" Worksheets completed bythe Transportation OfficeriUMC of their assigned SCI prior to or alter the MUSnARC's update review cycle

On Card Type -)'enter a numeric value for the equipment required to assist in the move, (Example. if6 buses are required enter "06-under columns57 58) if no other equipment is required leave columns 19-56 blank

I f a Contingency Standing Rout Order (CSRO) is required column 23 of the HOOD00 - card must contain a "Y (meaning yes) and all columns on card typeHO40001' and "H0002- must be completed If a CSRD is not required enter an "N" (meaning no) under column 23 of the "H0001'- card and leave blank

columns 7S569 and the "H0002' card type

The Ready To Load Date (ROYI C)) (columns 47 50On card fype 10001 ") is an estimate of the earliest date a unit is expected to be ready to load out fromorigin This date can be obtained from the installation or TAG Mobilization Planning Officer (Example the RDVLO would be reportedas-COOS ")

Caid Type "H0003' may be used to provide explanation or clarification of information reported on the other card types Beginning in column 23. enter infree form the desired remark text The entry should be abbreviated where possible, and contain spaces between words and between numbers and words

F0RW0M IouM 900-4.R, I ucT BB ( DI IION Of f )fN 88 1S OBSOLF IF ArmyFIMcPMraanGo 44f49 real

COMPUTERIZED MOVEMENT PLANNING AND STATUS SYSTEM (COMPASS)form6of6 UNIT MOVEMENT DATA WORKSHEET Pg of Pg' Requisements CoR2o Symlbol

fORSCOM Re 55.? the arirronalFORSCOM omm 9gooSs hould continuatron be neressar C46512KEY PUNCH INSTRUCTIONS REPORTING UNIT INSTRUCTIONS TRANSACTION CODE (TC) Colmn 79Duplicate data entered in columns 1-17 inall cards applicable to areport. See Chapter 5, FORSCOM Reg 55-2 for instructions on completing (A' = Add. -C' = Change, "D' = Delete)Punch all preprinted entries for card columns 18, 19-22 and 80 header data entries.

REMARKS DATA

E AC RH D ITO ,TO

UaE( ITO ITO 170 STARC STAR(

ieti to Unt 7 Ui 5 STR STR STR Phn Phn Code 0 Lire No y Entry R Area Comm' Auto- Ea~t Eat 0(uIC) 1D N (U(N) No 0 Code P eli v on Pref All ROYLEI ORIGIN RAIL HEAD TOWN ST

jjt1j sj~ H II Ii Is IT r 21 ' ' 9 334 35 G37 31 47 49o o15r55 9 3 6 5 76 3 1 7 7

I3 5 7 9 I 1I5 7 191 3 2S 27 29 31 33 35 37 39 41 43 45 47 49j 53 53 55 57 59 63 63 65 67 69 71 73 75 7 79 t

luC RD N E

FO C) IDM905 N RBLN E oOII AI ARE T ORGNM O AM .OAIN STOII OO CRIRS

y10A

0

0

Cr0

NI


Chapter 5Unit Movement Data (UMD) Collection and Reporting Procedures for the Computerized Movement Planning and StatusSystem (COMPASS) (RSC FCJ4-165 (R2))5-1. GeneralThis chapter provides general instructions for UMD updates. It applies to POM UMD, MOB UMD, tailored UMDand DEP UMD. It also provides guidance for manual report preparation and for UMO's, UMC's and DMC's to reviewand validate reports prepared by units. UMD reported to FORSCOM will be updated in compliance with the proceduresoutlined in this chapter.5-2. Automated Unit Equipment List (AUEL)

a. The AUEL is an automated Summary and Detailed report of the unit's reported unit movement data. The AUELis used for planning and execution of unit movements, strategic mobility analysis, identification of commercial and organicmovement requirements, production of military shipping labels, and to generation other transportation related documents.

b. The AUEL is a primary document in the unit's transportation movement/deployment plan. It is important toknow and understand the AUEL in order to successfully maintain and report unit movement data. Updates to theAUEL must be accomplished in accordance the update schedule provided in chapter 3. Chapter 4 provides a sampleof the FORSCOM generated AUEL with key explanations.5-3. FormatThe format used for unit movement data reporting is designed to satisfy information needs for planning, executing movements/deployments and for compliance with established automated data processing and electronic transmission requirements.The simplified input format is based on an 80 character record. The format standards set forth by this regulation mustbe strictly followed by whatever process or automated system used by units and/or installations for updating unit movementdata. The worksheets (FORSCOM Forms 900-R through 900-5-R) represent the approved format for unit movementdata reporting. Sample worksheets are provided in chapter 4. Instructions for reporting unit movement data are keyedto the data elements as portrayed on the FORSCOM Form 900-R series worksheets.

a. The record type entry in position 18 of the worksheets identifies the basic grouping and dictates the type ofreport format to use. Following are record types, title and FORSCOM Form number and appropriate cross-referencedparagraph for preparation instructions.

Record Type Title Form Number ParagraphA Header and Strength Data 900-R 5-12aD Vehicle Data 900-1-R 5-12bE Vehicle Load Data 900-2-R 5-12cF Special Handling Cargo Data 900-3-R 5-12dG Container Load Data TBD 5-12eJ Rail, Truck, & Bus Requirements 900-4-R 5-12fH0001 Contingency Standing Route Order 900-5-R 5-12gH0002 Contungency Standing Route Order 900-5-R 5-12hH Remarks 900-5-R 5-12iB Departure Report TBD 5-12j

b. The following rules should be applied to prevent processing errors when entering data on the FORSCOM Form900-R series worksheets or using automated systems:

(1) The alpha letters I and O are not authorized data characters in the Unit Identification Code (UIC).(2) The alpha letter O can only be used in the description portion of the E, F, G, and H record type.

5-4. Unit Movement Data Reporting StructureCriteria for reporting UMD is based upon the planned organization of the unit for movement/deployment execution.Description and examples follows:

a. Battalions (AC and RC) with lettered companies will report their UMD at company and/or detachment levels.In this case, the battalion UIC (AA) will become a "parent report". No data will be reported at the "parent" level.For example:

UIC Unit Name Subordinate Report UMDWAF3AA 333 Sig Bn Parent NOWAF3A0 333 Sig Bn A Company YESWAF3B0 333 Sig Bn B Company YESWAF3CO 333 Sig Bn C Company YESWAF3TO 333 Sig Bn HHC YES

b. Companies (AC and RC) with detachments will report their UMD down to detachment level. The UMD forthe company (AA level UIC) will then be reported under the FORSCOM assigned derivative of "ZZ". The "ZZ" reportserves as the basic company report (less the detachment). No data will be reported at the "AA" company level. Forexample:

UIC Unit Name Subordinate Report UMIDWPQRAA 350 QM Co Parent NOWPQRAI 350 QM Co Det Al YESWPQRZZ 350 QM Co i'ES


c. Separate (AC and RC) companies and battalions without lettered companies or detachments will report theirUMD at the "AA" level. An example of separate companies or battalions with out lettered companies or detachmentsis provided as follows:

UIC Unit Name Subordinate Report UMDWDFGAA 555 MP Co None YESWQRXAA 222 JA None YES

d. MOB UMD for reserve component units (U. S. Army Reserve and Army National Guard) with vehicles andequipment that requires commercial transportation and located at a site other than the unit's home station will be reportedon a sub-report. Sub-reports will be distinguished by the use of a specified type data code (TDC) SI, S2, S3, S4,S6 or S7. UMC's/DMC's must provide their FORSCOM Army Area Manager with the location of the storage siteprior to transmitting UMD for assignment of the appropriate type data code. Storage sites may be located at installations,ECS, MATES, UTES, WETS AMSA or OMS (etc.). For Example:

UIC TDC Unit Name Location Report UMDWQRXAA S 222 JA Snellville, GA YESWQRXAA SI 222 JA Augusta, GA (Storage Site) YESWQRXAA S2 222 JA Athens, GA (Storage Site) YES

NOTE: Units' equipment stored at the mobilization station will not require a sub-report. The equipment located atthe mobiliz2tion station will be reported as "moving organically to the mobilization station" using Echelon 02.

e. Individual re ,rting of units facilitates FORSCOM automated system update. of Time Phased Force DeploymentData (TPFDD) for Operation Plans. The TPFDD update capability features the option of planning units at the parentlevel (with all associated UMD) or at the subordinate levels reported (company/detachment).

NOTE: Reserve Component Units Only: Storage site reports are not part of the TPFDD update process.

5-5. Basic Identify Data Element File (BIDE)The BIDE managed by FORSCOM contains key information regarding unit location and status. The BIDE includeskey reference data by UIC such as the units organization description, home location, UTC, TPSN and SRC. Whena unit reports unit movement data, the UIC is validated by use of the BIDE. If a unit's UIC is not registered or cannotbe validated on the FORSCOM BIDE, the unit movement data will not be processed. The force readiness reportingsystem, Status of Resources and Training System (SORTS) is the vehicle for update and maintenance of the BIDE.

a. UMC's/DMC's wishing to delete a deactivated unit or add/change any information pertaining to a unit (UIC)must contact their POC responsible for SORTS updates. Contacts for SORTS:

Active Components units - ITO or installation SORTS POCU.S. Army Reserve Units - Appropriate CONUSA HeadquartersArmy National Guard Units - The Adjutant General, State

b. If any problems persist or questions arise pertaining to entry of unit reports as described above, UMCs andDMCs are encouraged to contact their FORSCOM Army Area Manager for assistance.5-6. Type Data Code (TDC)Type data codes are assigned by FORSCOM. They represent the purpose or type of unit movement data report (i.e.,POM UMD, MOB UMD,POMCUIS, exercise UMD, DEP UMD et ectera). The following is a list of FORSCOMassigned type data codes and a brief description of the type of UMD reports they represent:

Type Data Code (TDC) DescriptionA POMCUS UMD /FORSCOM COMPASS GeneratedS MOB UMD/ MOB Requirements / Unit reportedS 1-S4, S6-S7 MOB UMD/MOB sub-reports / Unit reportedD POM UMD/Deployment / Unit reported

RequirementsJ POMCUS-TPFD UMD /FORSCOM COMPASS GeneratedX and N Notional UMD /FORSCOM COMPASS GeneratedXA-XZ, YA-YZ and ZA-ZZ Installation unique /For installation use only using TC ACCIS or

RCAS. Not Reported to FORSCOM.T and TA-TZ Test UMD /Reported to FORSCOM only for TC ACCIS

or automated systems communications testing.Other Type Data Codes to be / Unit reportedassigned by FORSCOM for JointTraining Exercise UMD

a. TDC A through Z, AA through WZ and 1 - 9 are reserved. They may be assigned for use by FORSCOMonly. TDC are routinely assigned by FORSCOM for exercises, special missions or contingencies as required.

b. TDC XA-XZ, YA-YZ and ZA-ZZ have been designated for exclusive use of AC and RC units (that use TCACCIS). These TDC are to be assigned and managed by the installation UMC or the TC ACCIS System Administratoras necessary for installation and/or unit purposes.

c. UMD transmitted to FORSCOM without an authorized assigned TDC will not be processed.


d. Units/Installations that choose to randomly use a TDC not assigned by proper authority run the risk of thatTDC subsequently being assigned for a specific operation. In that case, the workload on the unit and on the supportingUMC to comply with the UMD update using the assigned TDC is considerably complicated and time consuming. Unitsmust ensure the authorized TDC is employed when preparing an initial report or updating an existing UMD file.5-7. Report typeThere are two UMD report types applicable to unit submissions to FORSCOM: "Initial" and "Update" reports.

a. An initial report is applicable when UMD has not been submitted to the FORSCOM master unit movementdata base (maintained in COMPASS). Units must have a valid UIC established in the FORSCOM data base for aninitial report to be submitted and processed. To add a unit to the FORSCOM data base the following action shouldbe taken by the unit's supporting UMC:

(1) Submits a written request (via memorandum or message) through the appropriate chain of command to: CDR,U. S. Forces Command, Trans & Svcs Div, ATTN: FCJ4-TRU (Systems), Fort McPherson, Georgia 30330-6000. Therequest must contain as a minimum the following information:

(a) Unit Identification Code (UIC).(b) Name of the unit.(c) Location of the unit.(d) Reason for adding unit (such as activation or reorganization of the unit).(e) Unit level point of contact (for further coordination, if necessary, to clarify problems that may be encountered

when adding unit to the data base).(2) The FORSCOM, J4, Trans and Svcs Div, Strategic Mobility Branch, Systems Office will enter the new unit

on file.(3) The unit will prepare the UMD initial report transaction and submit the data to FORSCOM as prescribed

by this regulation.b. An update report is prepared when changing UMD on file (AUEL is on hand). This report type applies to

unit submissions to change MOB UMD, POM UMD, or tailored UMD (for exercise or contingency moves). An updatereport is also submitted for DEP UMD for reporting unit departure information.5-8. Special instructions for MOB UMD Reporting

a. MOB UMD is tailored to reflect the type of movement used to the mobilization station (i.e. commercial transportationversus organic movement from the home station (HS) to the MS). The movement ECHELON is used to reflect thetype movement. The ECHELON is used for MOB UMD to enable movement planners to readily identify the typeof inland transportation employed for moving from HS to MS. ECHELONS as applied to MOB UMD are definedas follows:

(1) ECHELON 01 - Used to report both personnel and equipment for which commercial transportation will berequired for the move from the HS or stroage site location to the MS.

(2) ECHELON 02 - Used to report both personnel and equipment which will move to the MS by organic meanswithout regard to origin (home station, storage site or other locations). Plus equipment that is already located at theMOB Station.

(3) ECHELON 03 - Used to report equipment and personnel on the parent report which requires commercialtransportation from a location other than origin/home station (i.e, storage sites).

b. ECHELON 01,02, or 03 will be used in the company's detailed UMD record depending of the type of transportationmovements required as defined above.

c. Equipment and personnel requiring commercial transportation from storage sites will reflect echelon 01 in thesub-reports (TDC SI through S4 and S6 through S7).5-9. Special instructions for POM UMD reportingThe ECHELON will not be used for POM UMD unless specifically directed by FORSCOM.5-10. Special instructions for Tailored UMD reportingThe ECHELON should not be used for Tailored UMD (exercise or contingency movements) unless specifically directedby FORSCOM.5-11. Unit Line Number (ULN)

a. The ULN in record column 11-17 consists of the ULN from a Time Phased Force and Deployment Data (TPFDD).b. The ULN will only be used when directed by FORSCOM.c. When directed to report ULN the following rules apply:

(1) If UMD is not on file or if UMD is on file, enter: UIC (record position 1-6), TDC (record position 7-8),ULN (record positions 11-17), "A" (record psn 18), DATE (record position 19-25) and transaction code "A9" (recordpsn 79-80) on FORSCOM Form 900-R.

(2) To add more than one ULN to a UIC, a header report is required for each ULN. Same format as describedabove.

(3) Each subsequent record must contain the ULN [i.e. Vehicle Data (FORSCOM Form 900-1-R), Vehicle LoadData (FORSCOM Form 900-2-R), Special Handling Cargo Data (FORSCOM Form 900-3-R), Container Load Data(FORSCOM Form TBD), ITO Estimates (FORSCOM Form 900-4-R), Remarks Data (FORSCOM Form 900-5-R),and Deployment data (FORSCOM Form TBD)].


(4) Echelons may be used with ULNs if required (or approved in advance) by FORSCOM.5-12. WorksheetsData elements of each worksheet are described below. The data must be entered in record columns 1-80.

a. The "A Record" (FORSCOM Form 900-R) "Header and Personnel Strength Worksheet" identifies the reportingunit and personnel strength. It indicates an "Add" or "Change" submission, for updates to the the unit data in FORSCOMData Base.

Data Element NameUnit identification

Type Data (TD)

Echelon (ECH)Unit Line Number (ULN)

Record TypeSubmission Date

Total Strength

Record Column1-6

7-8

9-1011-17

1819-25

26-29

NOTE: Echelons 01, 02, and 03 are used only for RC UNIT

Echelon-01

Echelon " 1" Strength

Echelon-02

Echelon "2" Strength

Echelon-03

Echelon "3" Strength

Echelon and Strength

Type Report

Transaction Code

30-3132-35

36-37

38-41

42-43

44-47

48-77

79

80

No Char Remarks6 Enter the UIC of the reporting unit. May not be blank.

Must not contain alpha I's or O's.2 Enter the TD assigned to the report. (The first PSN

will always be an Alpha Character. The second PSNcan be Alpha, Numeric or Blank).

2 Not Used on the "A" Record.7 Enter the ULN that was assigned by FORSCOM or

that which is on the AUEL. May not be blank ifrequired.

1 Entry is "A". May not be blank.7 Enter the date that the UMD is submitted. The date

1 JUN 93 would be entered as "01JUN93". May notbe blank.

4 For Units reporting Deployment Data (ActiveComponent) enter the unit's aggregate strength (e.g.required strength is 156 enter 0156). (For updatescomplete only to change strength on file). For ReserveComponent Units Reporting Mobilization Data leaveblank.

S Reporting "S" and "SI "- "S4" and "S6 - S7" Typedata.

2 Enter "01": May not be blank.4 Enter the number of personnel for which "commercial

transportation" will be required for the move from anylocation to the MOB station. (If Echelon "1" strengthis 50 enter as 0050). (For updating complete only tochange echelon "l" strength on file). May not be blank.If no Echelon "1" strength required, must be zero filled.

2 Enter "02": May not be blank.4 Enter the number of personnel which will move to the

MOB station by organic means. (If Echelon "2" strengthis 100 enter as 0100). (For updating complete only tochange echelon "2" strength on file). May not be blankif no Echelon "2" strength required, must be zero filled.

2 Echelon 03: Enter "03" if reporting equipment in astorage site.

4 Enter the number of personnel requiring commercialtransportation from storage site, Zero fill otherwise.

20 These data elements are reserved for future use.! Enter "A" to add data not on file or "C" to change

data already on file. May not be blank. (Example ifyou want to delete ECH "02" that has 83 passengersyou would enter 01 under colm 36-37 and 0000 under38-41 and "C" in colm 79).

1 The number "9" is preprinted on the form, is commonto all UMD report submissions. May not be blank.

b. The "D Record" (FORSCOM Form 900-1-R) Vehicle Data Worksheet is used to report vehicles. Vehicles includetrucks, trailers, semi-trailers, amphibious vehicles, tracked vehicles, tanks, artillery (self-propelled and towed), floatingcraft (self-propelled and towed), railcars, locomotives, aircraft (self and non-self deployable), wheel or track-mountedequipment, and containers mounted on axles. Vehicles are reported in a shipping configuration IAW FORSCOM Regulation55-1.


Data Element NameUnit identification Code(UIC)Type Data (TD)

Echelon (ECH)

Unit Line Number (ULN)

Record TypeUnit-Entry Number

Line Number (LIN)

LIN-Index Number

Type Cargo Code (TCC)

Special Handling Code(SHC)

ModeMMS)

Codes (MPE/

Waiver Indicator (W/I)

Record Column1-6

7-8

9-10

11-17

1819-22

23-28

29-30

34

35

36

37

No Char Remarks6 Enter the UIC of the reporting unit May not be blank.

Must not contain alpha I's or O's.2 Enter the TD assigned to the report. May not be blank.

(The first PSN will always be an Alpha Character. Thesecond PSN can be Alpha, Numeric or Blank).

2 Must be the appropriate Echelon Code assigned. Maynot be blank if required. For all change entries thisdata element may be blank unless it is the data elementto be changed.

7 Enter the ULN that was assigned by FORSCOM orthat which is on the AUEL report. May not be blankif required. For all change entries this data elementmay be blank unless it is the data element to be changed.

1 Entry is "D". May not be blank.4 For "initial" reports, begin with 0001 for the first vehicle

reported and consecutively number each additionalentry "0002", "0003", etc. For update reports use thesame entry number as that which currently identifiesthe vehicle record to be changed or deleted; or, if anew vehicle record is to be added, use the next numberin sequence or one previously assigned to a deletedrecord. May not be blank. Must be a numeric numberbetween "0001 and 9999". NOTE: The Record Typeplus the Unit Entry Number combine to make theShipment Unit Number (SUN).

6 Enter the LIN as it appears in the MTOE PropertyBook and TB 55-46-1. The LIN is required for all "Add"entries. May not be blank. For all change entries thisdata element may be blank unless it is the data elementto be changed.

2 Enter the LIN Index Number for the applicable modeland shipping configuration contained in TB 5546-1.For all add entries this data element may not be blank.For all change entries this data element may be blankunles it is the data element to be changed.

1 Leave blank (the code will be generated) if the vehicleis loaded with hazardous cargo this data element mustbe filled in with the proper Type Cargo Code fromtable 5-2. For change entries this data element maybe blank unless it is the entry to be changed.

1 Leave blank (the code will be generated) except asfollows. If anything loaded on the vehicle is classifiedor sensitive then this data element must be filled inwith the proper SHC from table 5-3. For change entriesthis data element may be blank unless it is the entryto be changed.

1 Enter the Mode Code to Sea Port of Embarkation(MPE) or Mode to Mobilization Station (MMS) fromtable 5-4. Must filled when submitting an addtransaction. For change entries this data element maybe blank unless it is the entry to be changed.

1 Follow instructions below for applying W /1. If a Waiveris not required, leave blank and go to Transaction Code,Column 78.

- Containers that are loaded can not be waivered and can not exceed the Cargo Load Limits contained in TB 55-46-1.

- Entering an "X" in column 37 indicates that a cargo vehicle has a load that exceeds the Cargo Load Limit Heightcontained in TB 55-46-1 and the Equipment Characteristic Data File (ECDF).

- When a cargo vehicle with a load does not exceed the Cargo Load Limit Height, do not enter a waiver indicator.Go to the "E" record and enter the load data. Leave this column blank.


- This entry may be blank for a change transaction. If a vehicle record has been established with a W/I, that recordcan be changed in an update report without completing this entry. When changing the Height, LIN or Index makesure the load is within the Load Limits of the new LIN IAW TB 55-46-1.

- To remove the W/I from an existing vehicle record enter a "R" in this position (37). This will delete the waiverindicator, the height and the load. The vehicle will remain on file and the computer will generate standard dimensionsfrom the ECDE An "R" in this position will also remove a load from a non waivered vehicle.

Data Element NameHeight

Type Report

Record Column38-41

79

Transaction Code

No Char Remarks4 Enter the height of the waivered vehicle in inches as

a 4-PSN number (e.g., if the load caused the vehicleto be "101" high, enter "0101"). Complete only for addtransactions when using a W/ I or to change the heightof a existing waivered record already on file. May beblank for "Change" transactions if this not the entrybeing changed.

I Enter "A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe blank.


c. The "E Record" (FORSCOM Form 900-2-R) "Load Data Worksheet" is used to report cargo loads assignedto specific vehicles or containers (a load data worksheet is required for all vehicles or containers carrying cargo). Theremust be at least one "E" record for each "D" record with a load. The following is the format for an "E" record:

Data Element Name

Unit Identification Code(UIC)Type Data (TD)

Echelon (ECH)


Record Type

Unit-Entry Number

Load Number

Load Description

Load Qty

Type Equipment(TI E)

Code

Type Pack Code (TI P)

Record Column

1-6

7-8

9-10

11-17

1819-22

23-24

25-49

50-53

54

55-56

No Char Remarks

6 Enter the UIC of the reporting unit. May not be blank.Must not contain alpha I's or O's.

2 Enter the TD assigned to the report. May not be blank.(The first PSN will always be an Alpha Character. Thesecond PSN can be an Alpha, Numeric or Blank).

2 Must be the appropriate Echelon Code assigned. Maynot be blank if required. Must be the same as thevehicle or container echelon. For changes this dataelement may be blank unless it is the entry to bechanged.

7 Enter the ULN that was assigned by FORSCOM orthat which is on the AUEL. May not be blank ifrequired. For changes this data element may be blankunless it is the entry to be changed.

1 Entry is "E". May not be blank.4 Must be the same Entry Number as that assigned to

the Vehicle Entry Number to which the Load applies(e.g. if vehicle entry number is 0014 and is loaded thenthe "E" entry number will be 0014). May not be blank.

2 Enter "A" for the first load entry, "B" for the second,"C" for the third, etc (thus allowing multiple loads onany vehicle). The letters "E" and "O" cannot be used.Must be left-justified and may not be blank.

25 Begin in column 25 enter a brief description of thecargo loaded. Mandatory for "ADD" transactions.

4 Enter the number of cargo pieces (number of items)loaded on the vehicle (e.g. if the quantity is "46" enter"0046". Mandatory for "ADD" transactions. May beblank on changes.

I Enter appropriate code from table 5-6. Mandatory forall "ADD" transactions. May be blank on changes.

2 Enter the appropriate code from table 5-5. Mandatoryfor "ADD" transactions. May be blank on changes.

Data Element NameLoad Description (Weightpounds)

Record Column57-62

No Char6


RemarksEnter the total weight in pounds of the cargo that isloaded on the vehicle. Mandatory for "ADD"transactions or to change the weight of a load alreadyon file. The weight must not exceed the Cargo LoadLimit Weight of the vehicle index as listed in TB 55-46-1.May blank on changes.

Load Description (Cubic 63-69 7 Enter the total cube (length x width x height in inchesFeet) divided by 1728). Cubic feet will be rounded up to

the next whole number. Mandatory for "ADD"transactions or to change the cube of a load alreadyon file. The cube must not exceed the Cargo LoadLimit Cube of the vehicle index listed in TB 55-46-1. May be blank on changes. If the vehicle has beenassigned a waiver indicator the cube can exceed the

) limit listed in TB 55-46-1. Containers can not bewaivered.

Type Report 79 1 Enter "A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe blank.

Transaction Code 80 1 The number "9" is preprinted on the form, is commonto all UMD report submissions. May not be blank.

d. The "F Record" (FORSCOM Form 900-3-R) "Special Handling Cargo Worksheet" (for Other Than Vehiclesand Vehicle Loads) is used to report large/heavy cargo items: cargo that is palletized, containerized, unitized, cratedor banded together; cargo that is security classified; cargo other than that which has been reported as loaded on vehicles.The following is the format for an "F" record:Data Element Name Record Column No Char Remarks


Echelon (ECH)



Line Item Number (LIN)

LIN-Index Number

1-6

7-8

9-10

11-17

1819-22

23-28

29-30

6 r Enter the UIC of the reporting unit. May not be blank.Must not contain alpha I's or O's.


2 Must be the appropriate Echelon Code assigned. Maynot be blank if required. For all change entries thisdata element may be blank unless it is the data elementto be changed.

7 Enter the ULN assigned by FORSCOM or that whichis on the AUEL. May not. be blank if required. Forall change entries this data element may be blank unlessit is the data element to be changed.

1 Entry is "F". May not be blank.4 For "initial" reports, begin with 0001 for the first entry

and consecutively number additional entries "0002","0003", etc. For update reports use the same entrynumber as that which currently identifies the entrynumber to be changed or deleted; or, if a new "F"record is to be added, use the next number in sequenceor one previously assigned to a deleted record. Maynot be blank. Must be numeric between "0001" and"9999". NOTE: The Record Type plus the Unit EntryNumber combine to make the Shipment Unit Number(SUN).

6 Enter the LIN as it appears in the MTOE PropertyBook and TB 55-46-1. The LIN is required for all "Add"entries and may not be blank. For all Change entriesthis data element may be blank unless it is the dataelement to be changed.

2 Enter the LIN Index Number for the applicable modeland shipping configuration contained in TB 55-46-l.For all add entries this data element may not be blank.For all Change entries this data element may be blankunless it is the data elerrent to be changed.


Data Element NameWater Comm Code (WCC)

Type Cargo Code (TCC)

Special Handling Code(SHC)

Mode Code (MPE/MMS)

Record Column31-33

34

35

36

No Char Remarks3 Enter the WCC code from table 5-1. Must be filled

in on "ADD" transactions. For Changes this dataelement may be blank unless it is the entry to bechanged.

1 Enter the TCC from table 5-2. Must be filled in on"ADD" transactions. For changes this data elementmay be blank unless it is the entry to be changed.

I Enter the SHC from table 5-3. Must be filled in on"ADD" transactions. For changes this data elementmay be blank unless it is the entry to be changed.

1 Enter the code for Mode to Sea Port of Embarkation(MPE) or Mode to Mobilization Station (MMS) fromtable 5-4. Must be completed for add transactions. Forchange entries this data element may be blank unlessit is the entry to be changed.

The remaining portion of the "F" record isthis section. If you have a vehicle without ainstructions.

Length (inches)

Width (inches)

Height (inches)

Weight (pounds)

Type Equipment Code

Type Pack Code

Description of Item

Type Report

Transaction Code

38-42

43-47

48-51

52-58

59

60-61

62-76

79

80

used for equipment that does not have a LIN. Do not report vehicles inLIN, contact FORSCOM Army Area Manager for assistance and further

5 The Length will be computer generated based on theLIN and LIN Index reported. If LIN is not availableenter the length of the item or cargo in inches. (Example"198" inches enter "00198"). Complete only for "ADD"transactions or to change the length of a item alreadyon file without a LIN.

5 The Width will be computer generated based on theLIN and LIN Index reported. If LIN Es not availableenter the width of the item or cargo in inches. (Example"98" inches enter "00098"). Complete only for "ADD"transactions or to change the width of a item alreadyon file without a LIN.

4 The height will be computer generate based on theLIN and LIN Index reported. If LIN is not availableenter the height of the item or cargo in inches. (Example"54" inches enter "0054"). Complete only for "ADD"transactions or to change the height of a item alreadyon file without a LIN.

7 The weignt will be computer generate based on theLIN and LIN Index reported. If LIN is not availableenter the weight of the item or cargo in pounds.(Example "1500" pounds enter "0001500". Completeonly for "ADD" transactions or to change the weightof a item already on file without a LIN Number.

1 The computer will generate the Type Equipment (T/E) based on the LIN and LIN Index reported. Leaveblank. If LIN is not available enter the appropriatecode from table 5-6. Complete only for "ADD"transactions or to change the T/E of a item alreadyon file without a LIN.

2 Enter the appropriate Type Pack (T/ P) code from table5-5. Complete only for "ADD" transactions or tochange the T/ P of a item already on file with or withouta LIN.

15 The description will be computer generate based onthe LIN and LIN Index reported. Leave blank. If LINis not available beginning in column 62 enter thedescription of the item in free form. Complete onlyfor "ADD" transactions or to change the descriptionof a item already on file without a LIN."Enter A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe blank.


e. The "G Record" (FORSCOM Form TBD) "Loadspecific containers (a load data worksheet is required fordirected by HQ FORSCOM, FCJ4-TRU. There must bea load. The following is the format for a "G" record:


Data Worksheet" is used to report cargo loads assigned toall containers carrying cargo). This record is to be used asat least one "G" record for each "F" container record with

Data Element Name


Echelon (ECH)



Load Number

Load Description

Load Qty

Type Equipment Code(TI/ E)Type Pack Code (T/P)

Load Description(Weight lbs.)

Load Description(Cubic Feet)

Type Report

Transaction Code

Record Column1-6

7-8

9-10

11-17

1819-22

23-24

25-49

50-53

54

55-56

57-62

63-69

79

80

No Char Remarks

6 Enter the UIC of the reporting unit. May not be blank.Must not contain alpha I's or O's.


2 Must be the appropriate Echelon Code assigned. Maynot be blank if Echelon is required. Must be the samecontainer echelon. For all change entries this dataelement may be blank unless it is the data elementto be changed.

7 Enter the ULN that was assigned by FORSCOM orthat which is on the AUEL. May not be blank ifrequired. For all change entries this data element maybe blank unless it is the data element to be changed.

1 Entry is "G". May not be blank.4 Must be the same Entry Number as that assigned to

the Container Entry Number to which the Load applies(e.g. if container entry number is 0014 and is loadedthen the "G" entry number will be 0014). May notbe blank.

2 Enter "A" for the first load entry, "B" for the second,"C" for the third, etc. (thus allowing multiple loadsin the container). The letters "E", "G" and "O" cannotbe used. Must be left-justified and may not be blank.

25 Begin in column 25 enter a bried description of thecargo loaded. Mandatory for "ADD" transactions.

4 Enter the number of cargo pieces (number of items)loaded on the container (e.g. if the quantity is "46"enter "0046". Mandatory for "ADD" transactions. Maybe blank on changes.

1 Enter appropriate code from table 5-6. Mandatory forall "ADD" transactions. May be blank on changes.

2 Enter the appropriate code from table 5-5. Mandatoryfor "ADD" transactions. May be blank on changes.

6 , Enter the total weight in pounds of the cargo that isloaded in the container. Mandatory for "ADD"transactions or to change the weight of a load alreadyon file. The weight must not exceed the Cargo LoadLimit Weight of the container index as listed in TB55-46-1. May be blank on changes.

7 Enter the total cube (length x width x height in inchesdivided by 1728). Cubic feet will be rounded up tothe next whole number. Mandatory for "ADD"transactions or to change the cube of a container loadalready on file. The cube must not exceed the CargoLoad Limit Cube of the container index listed inTB 55-46-1. May be blank on changes.Enter "A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe blank.The number "9" is preprinted on the form, is commonto all UMD report submissions.


f. The "J Record" (FORSCOM Form 900-4-R) Rail Commercial Truck and Bus Requirements (ITO Estimates)Worksheet" is used to report the Transportation Officer's estimate of transport equipment required to move the unitfrom origin, home station, or storage site to Port of Embarkation or Mobilization Station. Complete as follows:

Data Element NameUnit Identification Code(UIC)Type Data (TD)

Echelon (ECH)


Record TypeNR-54-ft-CTD Flat

NR-60-ft-CTD Flat

NR-89-ft-CTD Flat

NR-TRL-on Flat Car

NR-CTNR-on-Fat Car

NR-Bi-Level

N R-Tri-Level

NR-53-ft-Gondola

Record Column1-6

7-8

9-10

11-17

1819-20

21-22

23-24

25-26

27-28

29-30

31-32

33-34



(The first PSN will always be an Alpha Character. Thesecond PSN can be an Alpha, Numeric or Blank).

2 Must be the appropriate Echelon Code assigned. Maynot be blank on change transactions if Echelon isrequired.

7 Enter the ULN that was assigned by FORSCOM orthat which is on the AUEL. May not be blank onchange transactions if ULN is required.

1 Entry is "J". May not be blank.2 Enter 54 foot Chain Tie Down (CTD) rail car estimate.

Enter as a 2-PSN number (Example "I" will be enteredas "01"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter 60 foot Chain Tie Down (CTD) rail car estimate.Enter as a 2-PSN number (Example "1" will be enteredas "01 ). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter 89 foot Chain Tie Down (CTD) rail car estimate.Enter as a 2-PSN number (Example "1" will be enteredas "01"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter Trailer on Flat Car (TOFC) rail car estimate.Enter as a 2-PSN number (Example "1" will be enteredas "01"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter Containers on Flat Car (COFC) rail car estimate.Enter as a 2-PSN number (Example "1" will be enteredas "Ol"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter Bi-Level rail car estimate. Enter as a 2-PSNnumber (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter Tri-Level rail car estimate. Enter as a 2-PSNnumber (Example "I" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter 53-ft Gondola rail car estimate. Enter as a 2-PSNnumber (Example "I" will be entered as "Ol"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

Data Element NameNR-65-ft-Gondola

NR-54-ft-DOD-Hvy-Dty

NR-68-ft-DOD-Hvy-Dty

NR-Caboose

NR-Drop-Frame

NR-Lowboy

NR-40-Flatbed-Trl

NR-45-ft-Flatbed-Trl

NR-48-ft-Flatbed-Trl

NR-20-ft-Sea-Van

Record Column35-36

37-38

39-40

41-42

43-44

45-46

47-48

49-50

51-52

53-54


No Char Remarks2 Enter 65-ft Gondola rail car estimate. Enter as a 2-PSN

number (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter 54-ft Heavy Duty rail car estimate. Enter as a2-PSN number (Example "1" will be entered as "01").If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter 68-ft Heavy Duty rail car estimate. Enter as a2-PSN number (Example "1" will be entered as "0").If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter Caboose/ Guard Car estimate. Enter as a 2-PSNnumber (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter Drop Frame trailer estimate. Enter as a 2-PSNnumber (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter Lowboy or lowbed commercial truck estimate.Enter as a 2-PSN number (Example "1" will be enteredas "01"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

2 Enter 40-ft Flatbed trailer estimate Enter as a 2-PSNnumber (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter 45-ft Flatbed trailer estimate. Enter as a 2-PSNnumber (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter 48-ft Flatbed trailer estimate. Enter as a 2-PSNnumber (Example "1" will be entered as "01"). If noneare required leave blank. For update transactionsinvolving a change in an existing record, this dataelement may be left blank unless it is the entry to bechanged.

2 Enter 20-ft Sea Van or 20-ft Container estimate. Enteras a 2-PSN number (Example "1" will be entered as"01"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.


Data Element Name Record Column No Char Rem -ksNR-40-ft-Sea-Van 55-56 2 Ente J)-ft Sea Van or 40-ft Container estimate. Enter

as a 2-PSN number (Example "1" will be entered as"01"). If none are required leave blank. For updatetransactions involving a change in an existing record,this data element may be left blank unless it is theentry to be changed.

NR-Coach or Bus 57-58 2 Enter Coach or Bus estimate. Enter as a 2-PSN number(Example "1" will be entered as "01"). If none arerequired leave blank. For update transactions involvinga change in an existing record, this data element maybe left blank unless it is the entry to be changed.

NR-Truck Tractors 59-60 2 Enter Truck Tractor estimate. Enter as a 2-PSN number(Example "1" will be entered as "01"). If none arerequired leave blank. For update transactions involvinga change in an existing r-cord, this data element maybe left blank unless it is the entry to be changed.

Type Report 79 1 Enter "A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe ,lank.

Transaction Code 80 1 Th: number "9" is preprinted on the form, is commonto all UMD report submissions. May not be blank.

. The "H Record" (FORSCOM Form 900-5-R) "Remarks Data Worksheets" are used to provide explanation,clarification or additional information on the data reported. Complete as follows:

Data Element NameUnit identification Code(UIC)Type Data (TD)

Echelon (ECH)


Record TypeUnit-Entry-Number

Contingency StandingRoute Order (CSRO)

ITO-STARC-Area-Code

ITO-STARC-COM M-PrefixITO -STARC-DSN-number

ITO-STARC-Phone-Ext

ITO-STARC-Phone-Ext-Alt

Record Column1-6

7-8

19-10

11-17

1819-22

23

25-27

29-21

33-35

37-40

42-45





7 Enter the ULN that was assigned by FORSCOM orthat which is on the AUEL report. May not be blankon change transactions if ULN is required.

1 Entry is "H". May not be blank.4 Entry number is preprinted on the Form "0001". For

update reports use the same entry number. May notbe blank.

1 If CSRO is required enter "Y" for yes and completethe H0001 and H0002 record. If CSRO not requiredenter "N" for no. If you enter a "N" go to column79 and enter the Transaction Code and do not createthe "H0002 record. Must be a "Y" or "N". May notbe blank.

3 Telephone Area Code of the Installation TransportationOffice/ STARC. May not be blank.

3 Telephone Prefix number of the Installation Transpor-tation Office/STARC. May not be blank.

3 Enter the Telephone DSN Prefix number of theInstallation Transportation Office or STARC. May notbe blank.

4 Enter the Preferred Telephone number of theInstallation Transportation Office or STA RC. May notbe blank.

4 Enter the Alternate Telephone Extension number ofthe Installation Transportation Office or STA RC. Maynot be blank.

Data Element Name Record ColumnRLD 47-50

Rail-Head-Location 52-66

Rail-Head-St 67-68Type Report 79

Transaction Code 80

h. The "H Record" (Unit-Entry-Number "0002"),only if a CSRO is desired.


Echelon (ECH)



Rail-Carrier

Rail-Carrier-St

Motor-Ramp-Location

Motor-Ramp-Location-StateMotor-Carrier

Motor-Carrier-St

Type Report

Transaction Code

Record Column1-6

7-8

9-10

11-17

1819-22

23-37

38-39

40-54

55-56

57-71

72-73

79

80


No Char Remarks4 Enter the Ready to Load date (RLD). The RLD is

an estimate of the earliest date a unit will be readyto load at origin. This date can be obtained from theInstallation or TAG Mobilization Planning Office. Maynot be blank.

15 Enter the location of the Rail Head where rail carsmay be spotted for a rail move. May not be blank.

2 Enter State of the Rail Head. May not be blank.1 Enter "A" to add data not on file. A "C" to change

data or "D" to delete data already on file. May notbe blank.


is a continuation of FORSCOM Form 900-5-R. To be completed





7 Enter the ULN that was assigned by FORSCOM orthat which is on the AUEL. May not be blank onchange transactions is ULN is required.

1 Entry is "H". May not be blank.4 Entry number is preprinted on the Form. Uupdate

reports use the same number. May not be blank.15 Enter the name of the Rail Carrier that may be used

for a rail move. If carrier not selected, enter Ni A. Maynot be blank for Add Transactions.

2 Enter state of the Rail Carrier. If carrier not known,enter N/A. May not be blank for Add Transactions.

15 Enter the location of the Motor Ramp which couldbe used to load equipment on Commercial Carriers.If ramp not available, enter N/A. May not be blankfor Add Transactions.

2 Enter State of the Motor Ramp. If ramp not selected,enter N/A. May not be blank for Add Transactions.

15 Enter the name of the Motor carrier that could beused for a commercial truck move. If carrier not selectedenter N/A. May not be blank for Add Transactions.

2 Enter the State of the Motor Carrier. If carrier notselected, enter N/A. May not be blank for AddTransactions.

1 Enter "A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe blank.


i. The "H Record" (Unit-Entry-Number "0003 thru 9999"). These entries may be used to provide explanations orclarifications of additional information pertaining to the data reported.


Record Column1-6

7-8


Must not contain alpha I's or O's.2 Enter the TD assigned tp the report. May not be blank.

(The first PSN will always be an Alpha Character. Thesecond PSN can be an Alpha, Numeric or Blanfk).


Data Element NameEchelon (ECH)



Record Column9-10

11-17

1819-22

No Char Remarks

Text (Remarks) 23-76 54 Beginning in column 23, enter in free form the desiredremark text. Abbreviate where possible and includespaces between words and numbers. May be blank for"Changes" or "Deletes".

Type Report 79 1 Enter "A" to add data not on file. A "C" to changedata or "D" to delete data already on file. May notbe blank.

Transaction Code 80 1 The number "9" is preprinted on the form, is commonto all UMD report submissions. May not be blank.

j. "B Record" The Deployment Reporting Record. This record is used to report deployment departure. It is requireddurmg deployments and may be required to report exercise departures. This record is only reported by TC ACCIS.

Data Element Name Record Column No Char RemarksUnit Identification Code 1-6 6 Enter the departing unit's UIC.(UIC)Type Data (TD)

Echelon


Deployment Indicator

Entry Number

Date Time Group

Mode To POE or Modeto PODControl Number

Bus Pax

Air Pax

Type Report

9-10

11-17

1819-23

24-35

36

37-51

52-56

57-61

79

Transaction Code

2 Enter the TD assigned to the unit for the reportedmovement. May not be blank.

2 Enter the appropriate Echelon, if applicable, directedby FORSCOM.

7 Enter the ULN assigned by FORSCOM for reportedmovement.

1 Enter "B" ONLY.5 Enter the Entry Number that corresponds to the AUEL

and Barcode Label on the equipment for whichdeparture is being reported. Entry number can be10001 - D9999 or F0001 - F9999. May not be blank.

12 Enter the Date and Time that the unit equipment ("D"or "F" entry) departed the Installation or the AerialPort of Embarkation. Date and Time Group will bereported as "DDHHMMZMMMYY". DD DAY,HHMM Hour and Minute, Z Zulu, MMM Monthand YY Year. May not be blank.

1 Enter the Mode to POE or POD See table 5-4. Maynot be blank.

15 Enter the Control Number that is assigned to movementfrom the Installation (MOB Station). (Example ofmovements Organic Air, Bus, AMC Air, Rail, ComTrk, Convoy, Barge or Water Way.) May not be blank.

5 Enter the Number of Passengers on each Bus departingfrom the Installation. May not be blank if Passengersdeparted by Bus.

5 Enter the Number of Passenger on each Sortiedeparting the Aerial Port. May not be blank ifPassengers departed by Air.Enter "C" to add or change deployment data. Maynot be blank.The number "9" is preprinted on the form, is co;mmonto all UMD report submissions. May not be blank.


7 Enter the ULN was assigned by FORSCOM or thatwhich is on the AUEL. May not be blank on changetransactions if ULN is required.

1 Entry is "H". May not be blank.4 For "initial" reports, begin with "0003 for the first entry

reported and consecutively number each additionalentry "0004", "0005", etc. For update reports use thesame unit entry number that is being changed or deleted.If a new entry is being added, use the next numberin sequence or one previously assigned to a deletedrecord. May not be blank.


FORSCOM Unit Movement Data Reporting Water Commodity Codes and Special Handling Codes

1. General. Water commodity and special handling codes identify commodities for ocean manifesting, MSC billing,cost accounting, contractor payment, and special handling purposes. The codes are alphanumeric and consist of fivecharacters. They are used to describe or categorize the shipment unit reported. The codes in this regulation are extractedfrom MILSTAMP. They have been approved for unit:movement reporting purposes. For a the complete list of WaterCommodity Codes (WCC), Special Handling Codes (SHC) and Type Cargo Codes (TCC) see DOD Reg 4500-32.R,MILSTAMP.

a. Position one through three - numeric characters depicting the water commodity code.

b. Position four - alpha character depicting the type cargo code (TCC).

c. Position five - numeric character depicting the special handling code (SHC).

2. The WCC and SHC combine to describe the shipment unit itself. The only exception, however, deals with hazardousmaterials loaded on cargo carrying vehicles. In this case, the last two positions (TCC and SHC) describe the load ratherthan the shipment unit.

Table 5-1Water Commodity Codes (WCOMMCDE)

CategoryClass A Explosive

Class B Explosives

Code418

419

NOTE: The above two codes are not in MILSTAMPinclude the codes in MILSTAMP

Other Hazardous ItemsSmall Arms AmmunitionGeneral Cargo

Floating CraftArtillery, SPArtillery, TowedTank, CombatVehicles, Wheeled SPSedansVehicles, trackedVehicles, wheeled SP

Construction equipmentMaterials Handling

Equipment (MHE)Trailers, wheeledTrailers, wheeledAircraft

436680700

804813816864867879876882

885891

892893900

MeaningMass detonating items subject to instantaneous explosion ofthe entire quantity.Items which generally function by rapid combustion ratherthan detonation and include some explosive devices.

because they are general descriptions. Action is in progress to

Hazardous items not otherwise specified.Ammunition .60 caliber and smaller.Miscellaneous unit equipment not classified as hazardouscargo.Self/ non-self-propelled boats and barges.Artillery, wheeled or tracked that is self-propelled.Artillery, wheeled or tracked that is towed.Tank, combat.Wheeled vehicles, self-propelled, 2-1/,2 ton capacity or less.Sedans.Tracked or half-tracked vehicles.Wheeled vehicles, self-propelled, capacity greater than2-1 ' 2-tons.Construction vehicles.Vehicles designated for matenals handling, Includes mobilecranes.

Trailers and semi-trailers 2-1 2 ton capacity or less.Trailers and semi-trailers capacity greater than 2-1 2 ton.Rotary;Fixed wing aircraft - reduced or operationalconfiguration.


Table 5-1 (Cont'd)Water Commodity Codes (WCOMMCDE)

3. The type equipment code for a given item is directly related to the commodity code. The relationship is indic:tedbelow:

Commodity Code418419436680700804813816864867879876882885891892893900

Type Equipment CodeMNP

Q or R

L, S, T, U, V, Y or XGEFD

1 or 32C4

8 or 90 or 5

67

H, Jor K

MeaningExplosive Class C, UN Class I (Explosive C Label).Nonflammable Compressed Gases, UN Class 2 (Nonflammable. Gas Label except oxygenrequires an Oxidizer Label and florin requires poison and Oxidizer Labels)

Explosives Class A, UN Class I (Explosive A Label).Explosives Class B, UN Class I (Explosive B Label).Flammable Compressed Gas, UN Class 2 (Flammable Gas Label).

Flammable Liquids, UN Class B (Flammable Liquids Label).

Combustible Liquids (No Label).Miscellaneous Hazardous Material UN Class 9 (No Label).

Corrosive Materials, UN Class 8 (Corrosive Label).

Flammable Solids, UN Class 4 (Flammable Solid Label).

No Special Type of Cargo Code Applicable.

Table 5-2Type Cargo Code (TCC)

CodeFG

IJORUVWXZ


Table 5-3Special Handling Codes (SHC)

Code Meaning2 Classified Materials: Official information or matter in any form or of any nature which

requires protection in the interest of national security.4 Hazardous and Sensitive Cargo: Small Arms; ammunition; and explosives which are a

definite threat to public safety and can be used by militant, revolutionary, criminal or otherelements for civil disturbances, domestic unrest, or criminal actions. Also includes hazardousitems such as flammable liquids, radio active, and other like items.

9 No special handling required. All categories of equipment not defined above (as either2 or 4).

Table 5-4New Mode to Port of Embarkation (MPE) Mode to Mobilization Station (MMS) Shipment Codes

The MPE and MMS codes are going to change. These codes are being changed to coincide with the MILSTAMPregulation. A message will be dispatched to inform you when the change will take place. MPE/MMS codes presentlyin the FORSCOM data base will automatically be changed. No additional input will be required by the units.

New Code MeaningA MTMC Commercial Truck/Trailer load to the SPOE/ MOB Station.E Commercial BusF Deployment by AMC Air. Not a surface move.K Rail to the SPOE/ MOB station. Includes the contemplated use of either

commercial or military owned rail assets.O Organic Military Air Movement to the SPOEi/MS. Includes all

self-deployable Army aircraft.W Water1 Unit Organizational Transportation (convoy) to the SPOE/ MOB station.

Includes the use of unit organic transportation (single lift or shuttlemovement) assets, other than aircraft, and assets from other than theinstallation TMP that have been designated to provide lateral transportationsupport.

2 Barge9 Installation arranged transportation to the SPOE/ MS. Includes

ITO-arranged commercial truck, local rating and routing.

NOTE The MPE/ MMS code indicates the method of shipment used from the origin shipping location to the portof embarkation (for Deployment) or to the mobilization station (for RC-MOB reports). Transportation officersat installations and STARCs are authorized to change the mode codes requested by their supported units basedupon sound traffic management principles and local procedures.

Old CodeTBF


Table 5-5Type Pack Codes (TPC)

The type pack codes indicate the manner in which an item is packaged for shipment. The codes consist of two characters.

Code MeaningBD Bundle.BX Box.PC Piece. Describe the type pack of any item that does not meet the criteria of any other

type pack.PT Palletized unit load.VE Non fully operational aircraft or vehicles which are not self-propelled.VO Fully operational aircraft or self-propelled vehicles capable of being driven for short distances

(drivable vehicle).XX CONEX, Type I or Type II; or UDSC.YC MILVAN and other CONTAINERS.ZX SEAVAN.

Air Drop Packaging CodesW1 A22 Container.W2 40 X 48 standard pallet load.W3 54 X 88 (463L) palletized.W4 108 X 88 (463L) palletized.W5 Platform, 8 feet.W6 Platform, 12 feet.W7 Platform, 16 feet.W8 Platform, 20 feet.W9 Platform, 24 feet.WA Platform, other than above.WB Bundles rigged for airdrop.

codes can only be used with prior permission from the Systems! COMPASS Office, Forcesin connection with Type equipment (TIE) code "L"

NOTE: The above Airdrop

Command and only


Table 5-6Type Equipment Code (TE)

Code Meaning0 Vehicle, wheeled (not self-propelled) Materials Handling Equipment (MHE).I Vehicles, wheeled (self-propelled), 1/2 ton or less.2 Vehicles, wheeled (self-propelled), sedan.3 Vehicles, wheeled (self-propelled), 2-1/2 ton or less.4 Vehicles, wheeled (self-propelled), greater than 2-1/2 ton.5 Vehicles, wheeled (self-propelled), Materials Handling Equipment (MHE).6 Vehicles, wheeled (not self-propelled), 2-1/2 ton or less.7 Vehicles, wheeled (not self-propelled), greater than 2-1/2 ton.8 Vehicles, wheeled (self-propelled), construction equipment.9 Vehicles, wheeled (not self-propelled), construction equipment.C Vehicles, tracked or half-tracked except D or E.D Tank Combat.E Artillery weapon, self-propelled.F Artillery Weapon towed, not self-propelled.G Floating craft self-propelled or not self-propelled (boats and barges) except amphibious

vehicles that are included under the appropriate numeric code.H Aircraft, rotary wing (operational).J Aircraft, fixed wing (operational).K All aircraft in a reduced configuration (NOTE: Disassembled components must be reported

separately as "Special Handling Cargo').L Airdrop (NOTE: Equipment or supplies rigged or packaged for airdrop; must be reported

as "Special Handling Cargo').M Class A explosives.N Class B explosives.P Other hazardous items.Q Ammunition and explosives over .60 caliber.R Small arms ammunition .60 caliber and less (Small Arms Ammo).S Yellow TAT organizational equipment and supplies (NOTE: Must accompany troops and

be accessible during the travel; also includes such items as rigging materials or equipmentneeded for off-loading aircraft at destination).

T Red TAT organizational equipment, accompanying supplies and baggage (NOTE: Mustbe available to troops upon arrival at destination).

U Equipment other than vehicles (NOTE: NOT TAT includes equipment which need notbe available to troops upon arrival at destination).

X Red TAT Baggage (NOTE: Personnel "Hold"' Baggage such as footlockers).Y Yellow TAT personal "accompanying" baggage.


Chapter 6Transmission of Unit Movement Data (UMD)6-1. GeneralThis chapter provides explanation for transmitting UMDto FORSCOM via AUTODIN or DDN and for trans-mission of reports back to Installations, STARC orMUSCARC using AUTODIN or the World Wide MilitaryCommand and Control System (WWMCCS).6-2. Submitting UMD data via AUTODIN

a. Request for AUTODIN transmissions must besubmitted in accordance with local procedures. For UMDtransmissions to be received at FORSCOM the followinginformation must be included on the request fortransmission by AUTODIN:

(1) Precedence: Priority(2) Classification: Unclassified(3) Content Indicator Code (CIC) as follows:

CIC Submitted by Installations and States:(a) ACGA - In First U. S. Army East geographical

area.

(b) AJFB - In First U. S. Army Mid-Westgeographical area.

(c) AJFA - In Second U. S. Army geographicalarea, including the Commonwealth of Puerto Rico andthe U.S. Virgin Islands.

(d) AGCB - In Fifth U. S. Army geographical area.(e) AGCC - In Sixth U.S. Army geographical area.(f) AJFC - Participating in exercises.(4) Routing Indicator Code: RUCLBJA.(5) Text Message:

Column1-58-56

Entry"TXMSG"

"COMPASS Data via WWMCCS forFCJ4 through Fort McPherson

b. The data time group of when the data wastransmitted and routing indicator code of the originatingstation should be'obtained by the requestor in case a traceris required.6-3. Submitting UMD via DDN.TC ACCIS is (currently) the only automated systemauthorized to submit UMD via DDN (E-MAIL). The TCACCIS has built in features that allow the SystemAdministrator to select transmissions of UMD via DDNor AUTODIN. When transmitting data to FORSCOMvia DDN the CIC must be selected from those listed inpara 6-2a(3). Routine transmissions are normally receivedfor processing by FORSCOM in COMPASS within 12hours. During contingencies the time may be within onehour. The System Administrator should obtain the datetime group and line count of data transmitted in case atracer is required.6-4. Receiving COMPASS AUEL and BBM reports viaAUTODINDirect communications between FORSCOM Director ofInformation (DOIM) and TRADOC DOIM regardingAUTODIN transmission of COMPASS reports isauthorized. When possible, COMPASS reports aretransmitted by AUTODIN to installations; activity DOIMswith Standard Entry and Exit System (SEES) capabilityfor printing.

a. Traffic originates from the FORSCOM J6WWMCCS Division, Fort McPherson, Georgia.

b. CIC for these transmissions is: AHHEc. COMPASS System identifier code is: DKVd. To receive and process the DOIM must:

(1) Create the queue for content indicator code"AHHE" using U38ATP.

(2) Load the queue using U39ATP.(3) Transfer queue contents from disk to tape using

U71ATP.(4) If the U71ATP execution report indicates an

incomplete shipment, follow local procedures to requestAUTODIN service for missing messages/blocks of datato the incomplete queue.

(5) Print output using U44ATP on five-part paper(or as stipulated by the UMC).

(6) Notify installation UMC when output is readyfor pickup.

e. Installation UMC will distribute the outputaccording to local procedures.6-5. Receiving COMPASS AUEL, BBM and TailoredReports via WWMCCSThese reports are designed to be printed on a 132-characterprinter. Reports may be directed to a WWMCCS printeror sent to a file. Permissions must be granted for any filesthat have to be established in order to transmit the reports.Coordination between the UMC/DMC WWMCCSoperator and the COMPASS Army area manager mustbe established prior to any transmissions of reports. Theusers printer ID must be provided to COMPASS for directprint files.6-6. Transmitting COMPASS AUEL Error Listings viaDDNFORSCOM is exploring ways and means to transmit Errorlisting by DDN to TC ACCIS sites. When these proceduresare developed TC ACCIS will be furnished the information.Chapter 7Systems Administration7-1. GeneralThe Director of Logistics, J4, Transportation and ServicesDivision, Strategic Mobility Branch, Systems Section isthe office of primary responsibility for command oversightand staff management for transportation related automatedsystems.7-2. PurposeThis chapter addresses the DOL, J4, Transportation andServices Division, Strategic Mobility Branch, SystemsSection responsibilities in strategic mobility systemdevelopment, fielding and overall staff management, andprovides a brief description of current and developingsystems. These systems are addressed in the Departmentof Army Logistics Automation Master Plan (LAMP).7-3. ResponsibilitiesFORSCOM responsibilities include:

a. Maintenance of a standard unit movement data basefor planning and movement execution purposes. This isaccomplished through operation and maintenance ofCOMPASS.

b. Maintenance of the standard Department of ArmyEquipment Characteristics Data File (ECDF) of equipmenttransportability characteristics for Army table oforganization and equipment (TOE).

c. Maintenance of an automated interface through theWWMCCS for interface with the joint reporting structure(JRS) of the Joint Staff using the JOPES, the Global

Transportation Network (GTN) or the TransportationCoordinator Automated Information Management System(TC AIMS).

d. Staff management, development, testing and fieldingof strategic mobility systems and non-tactical transportationrelated systems.

e. Headquarters technical support and assistance forexisting transportation systems relating to strategic mobilityand installation support.

f. Review and analysis of Systems Change Proposals(ECP) for existing transportation systems and fortransportation applications suggested for automation orelectronic processing.7-4. Systems Description

a. Systems, processes and transportation applicationscurrently operating or under development are brieflydescribed below.

b. Transportation planning and strategic mobilitysystems include (but are not limited to) the following:

(1) The Automated Air Load Planning System(AALPS). AALPS is a Department of Army prototypesystem designed to produce accurate and detailed aircraftload plans. AALPS will become the resident airload moduleof TC ACCIS and will be portable for use in the field.

(2) The Computerized Movement Planning andStatus System (COMPASS). COMPASS is a U. S. ForcesCommand unique data system which is used to collectand maintain unit movement data to provide informationalproducts to facilitate planning and execution of unitmovements for the Active and Reserve Components. Thisdata includes movement characteristics and movementconfiguration useful to both force planners and transpor-tation operating agencies alike.

(3) Department of the Army Movement Manage-ment System - Redesign (DAMMS-R). The DAMMS-Rwill provide an automated and interactive transportationsystem in a theater of operations. It will support movementsmanagement, transportation operations and common usertransportation asset control functions. DAMMS-R willinterface with: the Department of Army Standard PortSystem - Enhanced (DASPS-E); the Standard ArmyAmmunition System (SAAS); the Standard Army RetailSupply System (SARSS); the Combat Service SupportControl System (CSSCS); and, the TransportationCoordinator Automated Command and Control Informa-tion System (TC ACCIS).

(4) Department of the Army Standard Port System- Enhanced (DASPS-E). The system automates portoperations documentation and accountability and includesthe use of LOGMARS technology. DASPS-E will bereplaced by the Worldwide Port System (WPS).

(5) Microcircuit Technology for Logistics Applica-tions (MITLA). Logistics Applications of Automated


Marking and Reading Symbols (LOGMARS). MITLA.and LOGMARS are not ADP Systems, but the barcodetechnology readily supports the productivity initiatives ofthe Department of Defense and source data automationinitiatives of the Department of Army. LOGMARSapplications will be integrated into the Defense Transpor-tation System interfacing with existing and currentlydeveloping systems.

(6) Mobilization Shipments Configured for Opera-tional Planning and Execution (MOBSCOPE). MOB-SCOPE is a FORSCOM initiative designed to satisfy DODrequirements for identification of the Army's commercialtransportation requirements for Reserve Component unitsmoving to the mobilization station. MOBSCOPE has twobasic parts: MOB (Mobilization Scenario Data) andSCOPE (Mobilization Unit Movement Data). SCOPE datais extracted from COMPASS maintained mobilizationUMD (reported by the units). MOB data is extracted fromthe MSPS (Mobilization Stationing Planning System). Thisdata is used for planning mobilization movements and forinitiating movements upon declaration of mobilization. Thisdata may also be used by MTMC Area Commands forissuing and maintaining Contingency Standing RouteOrders (CSROs).

(7) Transportation Coordinator Automated Com-mand and Control Information System (TC ACCIS). TCACCIS is the Army's automation initiative designed toaccomplish transportation functions at unit and installationlevel for mobilization and deployment purposes. Oneobjective of TC ACCIS is to satisfy source data informationneeds of the JCS TC AIMS requirements. TC ACCIS willprovide the installation and units (down to battalion andseparate companies) the capability to create, update ormodify unit movement requirements data and produce thenecessary transportation documentation and reports. TCACCIS will also support routine, day to day transportationoperations within the Installation Transportation Office.

(8) Worldwide Port System (WPS). The WorldwidePort System under development by MTMC standardizesautomated cargo documentation and accounting functionsat ocean terminals worldwide. This micro-computer basedsystem will replace DASPS-E and TERMS when fielded.7-5. Coordination

a. Problems with existing transportation related datasystems should be addressed to the system proponentagency for action IAW system documentation and usersmanuals.

b. Problems experienced with transportation relatedsystems (described in this chapter) that are beyond the scopeof the respective system documentation may also beaddressed to this headquarters.

c. Problems experienced with UMD submission maybe addressed to Headquarters. Forces Command, ATTN:FCJ4-TRU (Systems), Fort McPherson, GA 30330-6000.


Appendix:ReferencesSection IRequired PublicationsAR 220-10 Preparation for Overseas Movement of

Units (POM).FORSCOM Transportation and Travel, Unit Move-Reg 55-1 ment Planning.TB 55-46-1 Standard Characteristics (dimensions,

weight, and cube) for Transportabilityof Military Vehicles and Other Out-sized/Overweight Equipment (in TOELine Number Sequence).

Section IIRelated PublicationsAR 5-9

AR 10-42

AR 70-47AR 310-25

DA Pam 746-1FORSCOMReg 700-2FORSCOMReg 700-3MTMCTEAPam 700-1

TB 55-45

TB 55-46-2

TM 55-2200-001-12

GlossarySection IAbbreviationsAALPSAARACACLADPEAMCAMOPESAMSAAPOEASGD CDEASLARCOM

Intraservice Support Installation AreaCoordination.U.S. Army FORCES Command,Organization and Functions.Engineering for Transportability.Dictionary of United Stats ArmyTerms.Pallets for Army Use.FORSCOM Standing LogisticInstructions.Ammunition Basic Load.

Standing Operating Procedures forValidating Dimensions and Weight ofEquipmentCertification of Military Equipmentfor Transport in (microfiche) AMC/CRAF Aircraft.Standard Transportability Characteris-tics (dimensions, (microfiche) weight,and cube) for Military Vehicles andOther Outsized/Overweight Equip-ment (in NSN Sequence).Transportability Guidance for Appli-cation of Blocking, Bracing and Tie-down Materials for Rail Transport.

Automated Airload Planning SystemAssociation of American RailroadsActive ComponentAllowable cargo loadAutomatic data processing equipmentAir Mobility CommandArmy Mobilization Planning SystemArea Maintenance Support Activityaerial port of embarkationFORSCOM Assigned Codeauthorized stockage listUnited States Army ReserveCommand

ARNGAUELAUTODINBBMBBPCT

BIDECBS-XCCCCCMCEGECICICCOFCCOMPASS

CONEXCONUSCONUSA

CSROCTACTDCU FTCUBECYCIDDADDNDELDEMSTAT

DODXDOIMDMCECHECSEDDFCFORMDEPS

FORSCOMGB

GELOCGOCOM

GONGTNHDHSIC-UMO

INDX NOJCSJPEC

Army National Guardautomated unit equipment listautomatic digital networkblocking and bracing materialblocking, bracing, packing, cratingand tiedownbasic identity data elementsContinuing Balance System-ExpandedCargo Category Codecross country movementCombat Equipment Group Europecoordinating installationcontent indicator codeContainer on Flat CarComputerized Movement Planningand Status Systemcontainer expressContinental United Statesthe numbered Armies in the Continen-tal United StatesContingency Standing Route Ordercommon table of allowancechain tie downcubic feetcubic feetFORSCOM cycle identification codeDepartment of the ArmyDefense Data NetworkDeployment Equipment ListDeployment! Employment/ Mobiliza-tion Station Reporting SystemDepartment of Defense-owned rail carDirector of Information ManagementDefense Movement Coordinatorsmovement echelon (see terms)equipment concentration siteestimated deployment dateFORSCOM assignment codeFORSCOM Mobilization andDeployment Planning SystemUnited States Forces CommandArmy National Guard or "NationalGuard Bureau" assignment codegeographical location codeUnited States Army Reserve GeneralOfficer Commandgondola carGlobal Transportation Networkheavy dutyhome stationIntermediate Command Unit Move-ment Officerindex numberJoint Chief of StaffJoint Planning and ExecutionCommunity

JDSJOPES

JRSLAMPLINMATES

MEEMHEMICMILVANMMSMODE TO POE

MPEMPES

MSMTMC

MTMCTEA

MTOE

MTONMUSARC

NAPNAP-DNG

NGBNON-SPOHOMS

PCNPERL

PINPLLPODPOEPOMCUS

Preferred Ports

PSNQTYRCRCSRDYLDREQ-VA LRPTG

Joint Deployment SystemJoint Operations Planning and Execu-tion SystemJoint Reporting StructureLogistics Automated Master Planline item numbermobilization and training equipmentsiteminimum essential equipmentmaterials handling equipmentMovement indicator codemilitary-owned demountable containermode to mobilization stationMode of transportation to port ofembarkation or mobilization stationmove to point of embarkationMobilization Planning and ExecutionSystemmobilization stationMilitary Traffic ManagementCommandMTMC Transportation EngineeringAgencyModified Table of Organization &Equipmentmeasurement tonMajor United States Army ReserveCommandnot authorized prepositioningnot authorized prepositioning-deferredAssignment code meaning "NationalGuard" or "Guard Bureau"National Guard Bureaunot self-propelledon handOrganizational MAaintenance SupportActivityproject control numberPrepositioned Equipment Require-ments Listingplan identification numberprescribed load listport of debarkationport of embarkationPrepositioning of Materiel Configuredto Unit SetsThese are the Sea and Air Ports pre-ferred to be used for planning pur-poses designated by FCJ5positionquantityReserve Componentrequirement control symbolReady to load dateRequisition Validation Systemreporting

SCHSEDRE

SISORTS

SMCSPOESRCSTARCSTRSUN

S/ClTAT.TCTC ACCIS

TCCTCSTDT/ETEATOETOFCTPCTPFDDTPFDLTPSNTUCHAUICULNUMCUMDUMOURLDUSAMCUSARUSARCUTCUTESWCOMMCDE

WETSW/IWWMCCS

Section IITermsAccompanyingsupplies


Special Handling CodeSEA Emergency Deployment Readi-ness Exercisesupport installationStatus of Resources and TrainingSystemsite movement coordinatorsea port of embarkationStandard Requirement CodeState area commandpersonnel strengthShipment Unit Numbersupport/coordinating installationto accompany troopstransaction codeTransportation Coordinator Auto-mated Command and Control Infor-mation SystemType Cargo Codetemporary changing stationtype datatype equipment codeTransportation Engineering AgencyTable of Organization and EquipmentTrailer on Flat Cartype pack codeTime Phased Force Deployment DataTime Phased force Deployment Listtroop position sequence numbertype unit characteristicsunit identification codeunit line numberunit movement coordinatorunit movement dataunit movement officerunit ready to load dateU.S. Army Materiel CommandUnited States Army ReserveU.S. Army Reserve CommandUnit Type Codeunit training and equipment sitewater commodity and special handlingcode

weekend equipment and training sitewaiver indicatorWorldwide Military Command andControl System

Cargo, other than TOE/MTOE equip-ment items, which will accompany aunit when moving administratively ortactically. (See FORSCOM Regulation700-2 for specific guidance concerningsupplies authorized to accompanydeploying units.)


AUEL

Bulk Cargo

COMPASS

CSRO

DEL

ECH

Large/heavycargo item

MOB entity

Automated Unit Equipment List is aDetail and Summary list of a Unitsreport vehicles and equipment.Cargo which has individual hipmentunit dimensions not exceeding "104" X"84" X "96", and which is neitherInterst - Commerce Commission(ICC) .. assified "Dangerous andHazardous" (D&H), nor securityclassified.An information system and databaseproviding accurate and timely UnitMovement Data to DOD, JCS, HQDAand Army installations and units insupport of employment, deployment,mobilization planning and executionfor a wide range of military operations.Contingency Standing Rout Order isthe Transportation Officer's submisionof the J" Record to MTMC requestingadvance routing approval by providingadvance data before actual movementof equipment to the POE.Deloyment Equipment List producedby TC ACCIS for a unit that hasupdated for a exercise or deployment.The same as a AUEL report lessSummary report.Movement echelon. A data control fieldused to group equipment items withinthe unit movement data master file forsome specific purpose (dependent uponthe Type-Data code application).A container, box, crate, pallet, orindividual bare item of equipmentwhich exceeds "72" in length or width,"67" in height, or 5,000 pounds inweight. These criteria also apply to theterm "outsize/ overweight" and providea basis for identifying cargo withpotential transportability limitations.Applicable to USAR and ARNG only.The level of organization that mustreport UMD to FORSCOM. Generallythis means separate companies orbattalions Exceptions: ARNG units anddetachments subordinate to a separatecompany or battalion assigned toanother state, the subordinate unit isconsidered a MOB Entity. Also, USARand ARNG units having (vehicles andequipment not located with the parentunit) and (vehicles and equipment ina equipment storage site, ECS,MATES, UTES, WETS, AMSA,OMS, etc.) are sub units and areconsidered a MOB Entity.

NAT

Outsize cargo

Oversize cargo

Red TAT

ShippingconfigurationSignificant change

STONSRC

SRC STRUMD

UTC

YELLOW TAT

ZULU HOUR

'Z US GOVERNMENT PRINTING OFF CE 1993.- 7 3 3 _ 2 "E 2 - E s 9 C E

Any Individual cargo item too large tobe transported in a C-5 aircraft (exceeds"l1454" in length, "216" in width or "156"in height).Any Individual cargo item which maybe transported in a C-5 aircraft, butnot in a C-141 (exceeds "1090" in length,"111" in width or "103" in height).Any Individual cargo item which maybe transported in a C-141 aircraft (butnot necessarily in a C-130) exceeds"104" in length, "84" in width or "96"in height; but are less than the dimen-sions of "outsize cargo".Cargo which must arrive at the overseasdestination before or concurrently withtroops. If accompanying troops, neednot be accessible during the voyage.The manner in which an item isprepared for shipment.As applied to UMD, a significantchange is one which materially affectsthe movement problem or solution. Forexample, a change in either the originor destination of a movement willmaterially affect the movement prob-lem. Changes in either passengers orcargo which will increase or decreasethe need for transportation equipment(aircraft, rail cars, buses, trucks, etc.)will materially affect the movement.Short Tons (pounds divided by 2000).Standard Requirements Code (TOEplus year of issue plus variation).SRC (TOE) personnel strength.Unit Movement Data. A detail listingand summary of unit related informa-tion describing passenger and cargomovement requirements underAR 220-10 and AR 10-42.Unit Type Code. A JCS developed code,consisting of five characters whichuniquely identify a "Type Unit".Cargo which must accompany troopsand which must be accessible duringthe voyage. For personnel traveling viacommercial air, this is generally onlythat baggage that would fit under theseat.Is the time of day plus 5 hours if onEastern Standard Time. (Example 1300hrs would be 1800Z). Plus 4 hours ifon Daylight Savings Time (Example1300 hrs would be 1700Z).

Documents

Department of the Army 'FORSCOM Regulation