LESSON THREE
BRIEF ON THE STATUS OF MOBILIZATION STATION PLANS
OVERVIEW
TASK DESCRIPTION:
In this lesson, you will learn how to brief on the status of the chaplain portion of mobilization station plans.
LEARNING OBJECTIVE:
TASK: Describe the actions needed to brief on the status of MOB STA plans.
CONDITION: Given the subcourse material for this lesson and a training scenario.
STANDARD: The student will respond with 70% accuracy to the multiple choice subcourse examination requiring recall and application of instructions.
REFERENCE: The material contained in this lesson was derived from the following publications:
UMT Information Handbook on Mobilization
INTRODUCTION
In the event of mobilization, you will have to live with your plans; largely you will stay in place and implement your plans. You are the implementers. If your plans are not good ones, you are the ones who will bear the consequences. You cannot take the risk of a chaplaincy which doesn't know how to mobilize, which cannot perform its mission to support the Total Army at a time when it is most needed. In the event of mobilization, the Active Army deploys as do the most ready of Reserve and Guard Units. The rest of the force trains for deployment. You should remember that virtually all of the UMT assets go with the troops. Your mission at home is to the families of deployed soldiers but the UMT assets are with the troops.
1. Mobilization Stationing Planning System (MSPS) (Vol II - FORMDEPS).
a. The Mobilization Stationing Planning System (MSPS) is a FORSCOM unique computer subsystem designed to support mobilization stationing planning within the Joint Operations Planning System (JOPS). MSPS contains active TOE and TDA units and the mobilizing Reserve Component TOE and TDA units in FORSCOM and WESTCOM. The Mobilization Troop Basis Stationing Plan (MTBSP) is a product of the MSPS.
b. Operational Description.
(1) MSPS is compared against a master file of selected units for updating. The update consists of recommended additions, deletions and changes to units in the MSPS file. This data includes only unit status information.
(2) MSPS contains deployment data derived from selected Time Phased Force Deployment Data (TPFDD) files. Deployment data consists of ports of embarkation (POE) and debarkation (POD) in addition to arrival and departure requirement dates.
(3) MSPS provides mobilization stationing and RC unit ready (departure capability) to load date data to selected TPFDD's whenever mobilization is involved in the scenario.
c. System Management.
FORSCOM, DCSOPS-Plans (AFOP-OM).
d. Operating Cycle.
MSPS data is updated on a weekly basis.
e. Interface with other Systems.
(1) With a JOPS TPFDD on an as required basis.
(2) With JOPS/UNITREP for addition, deletions and changes to unit status information.
(3) Overlaid from the MSPS master file into OMNI.
f. System Products.
(1) Produces the annual Mobilization Troop Basis Stationing Plan (MTBSP), with various sort and subtotal formats.
(2) Exports data to HQDA on a monthly basis.
g. System Constraints.
The system is currently designed only for full mobilization. MSPS allows for only AC and RC units in- being and does not include units programmed for activation.
2. Mobilization Troop Basis Stationing Plan (MTBSP).
a. The MTBSP is a computerized output of the FORSCOM Mobilization Stationing Planning System (MSPS). This document is the key document for planning mobilization and deployment of forces. It is a complete listing of Active, National Guard and USAR approved force structure units. Mobilization plans are a useless endeavor if the information in this document is not understood and used. The data files provide:
(1) All active units in the Mobilization Stationing Planning System (MSPS).
(2) All AC and RC units which form the family of plans for each of these OPLANS.
(3) All RC units in the CONUS Support Base for the applicable OPLAN.
b. The current FORSCOM policy is to not publish any force listings in hard copy for distribution. A program has been formulated to allow specific headquarters to draw this document data from MSPS using WES terminals located at each activity. Controls will be established to preclude the withdrawing of MTBSP data from other than the particular headquarters' units affected. For example, a mobilization station can only withdraw unit data on those units shown to be assigned to that installation as a mobilization station. Instructions are contained in the hard copy document, Volume II, MTBSP, FORMDEPS.
c. MTBSP DATA Guidelines. The MTBSP data is separated by columnar heading for each unit listed beginning with the Unit Identification Code (UIC). Columns are outlined for:
Troop Program Sequence Number - TPSN.
COMPONENT - COMPO.
A Name - Unit Narrative Name.
Standard Requirements Code - SRC.
Home Location - HOLOCATION.
Structure Strength, Offices and Warrant Offices - STRUCOW.
Structure Strength, Enlisted - STRUCE.
Mobilization Command - MBCMD.
Assignment - ASGMT.
Mobilization Location - MBLOCATION.
Packaging - PKG.
Coordinating Installation Location - CILOCATION.
Mobilization Date - MDATE.
Deployment Area - DP Area.
Mobilization Origin Departure Date - MOBDD.
Mobilization Station Arrival Date - MBSAD.
Ready to Load Date - RDYLD.
Estimated Departure Date Surface - EDDS.
Estimated Departure Date Air - EDDA.
Surface Latest Arrival Date - SLAD.
Air Latest Arrival Date - ALAD.
d. Units are grouped by component.
(1) Units in the Presidential 200,000 Call-up and partial mobilization packages are shown in the packaging column heading of the MTBSP.
(2) For "full" mobilization, units which are required within the first 30 days (LAD 30) will be mobilized at active and semi-active installation in close proximity to their home stations.
(3) The NATO M+10 essential force (fourth ROBCO positions 1 through 6, G, J, & U) will be mobilized at active and semi-active installations in close proximity to their home stations and will be considered for direct and modified deployment whenever possible.
e. Guidelines Governing Mobilization Stationing.
(1) A unit will be assigned one mobilization station from which it will deploy for any assigned contingency.
(2) Mobilization stationing criteria/considerations will be applied to the maximum possible extent.
(3) Mobilization changes must be minimized to assure stability in mobilization planning and to alleviate distribution of unit and mobilization planning/coordination efforts.
(4) CONUSA will act as the focal point for coordination and mobilization station changes. The cut-off date for FORSCOM receipt of CONUSA coordinated mobilization station change requests is 30 April annually. The following guidance applies to processing changes:
a. MACOM may submit requests through the appropriate FORSCOM Staff office to AFOP-OM. These requests will be forwarded to the CONUSA for coordination. Other requests should be submitted through the TAG/RSC to the CONUSA with copies to NGB/OCAR, as appropriate.
b. After receipt of CONUSA coordinated requests and of NGB/OCAR concurrent concurrence, FORSCOM, AFOP-OM, will make changes in the MSPS and formally notify all parties concerned of the completed action.
(5) Assignment to units of mobilization date (MDATE), mobilization origin departure date (MBODD) and mobilization station arrival date (MBSAD) will be governed by the following:
(6) MDATE at home station is normally M-Day +3, recognizing that some units are required to be mobilized prior to M+3, and that some units need not be mobilized until after M+3.
(7) FORSCOM will assign these dates to new units entering the system.
f. Stationing Criteria.
(1) Deploying units will be stationed where they can be trained and readied for deployment. Some ARNG division elements will be mobilized separately from their parent division because of the absence of necessary ranges at the division stations.
(2) Units will be stationed close to home station and on their equipment when feasible. Ideally, unit mobilization station, annual training (AT) site, and equipment location will be the same.
(3) Roundout units will be stationed at sponsor unit's station when feasible.
g. Troop Housing.
(1) Basic trainees, receptees, OCS students and patients in barracks will be housed at not less than 72 square feet per individual.
(2) All other enlisted personnel will be billeted at not less than 54 square feet per individual.
(3) Installation commanders should review the MDATE, MBODD, and MBSAD contained herein, for units mobilizing at their installations and should provide proposed changes to the CONUSA, after coordination with the MACOM as appropriate. Changes will be coordinated with RSC/TAG and with mobilizing units where feasible. The changes will then be submitted by installation to headquarters, FORSCOM.
(4) Mobilization sites, not designated as a mobilization station, should submit changes through appropriate channels to the CONUSA.
(5) Mobilization station commanders are authorized to retain units at home station up to deployment dates provided such units are within commuting distance from the mobilization station. For example, it may be feasible for a unit located in Columbus, Georgia, whose mobilization station is Fort Benning, to be mobilized and remain at the unit armory or center and commute to Fort Benning for training and processing. The unit would then deploy from Fort Benning.
(6) Guidance for direct deployment and modified deployment of selected reserve component units from their home stations is contained in Volume III, Part 2 of FORMDEPs.
(7) Upon full mobilization, all installations now under DA control or subject to recapture will be available for army use.
h. Deploying and Nondeploying Units.
(1) All active and reserve component units located in CONUS, Alaska, Hawaii, Panama, Puerto Rico, Guam, and Virgin Islands are included in the MTBSP.
(2) Nondeploying RC units which will remain under FORSCOM/TRADOC control following mobilization are stationed at FORSCOM/TRADOC installations. Certain other nondeploying units have been assigned mobilization stations/sites as requested by the major commands to which they will be assigned/attached upon mobilization; for example, MTMC for transportation terminal units, Health Services Command for medical augmentation units, and deploying units with initial mission to support AMC depot operations. Other nondeploying units will be mobilized in place; for example, ARCOMs and state area commands (STARC). Mobilization sites, not designated as a mobilization station, arrange mobilization support by MOU or ISSA with the nearest active installation (supporting installation) as assigned by the coordinating installation (CI) IAW AR 5-9. Supporting installations will perform unit validation and other administrative actions outside the capability of these mobilization sites.
(3) Requirements for nondeploying general support forces beyond those shown in the stationing plan must be satisfied through selective expansion of installation TDA. Guidance for preparation/ update of MOBTDA expansion requirement is included in Annex V to the FORSCOM Mobilization Plan (FMP).
(4) Sustaining base units fall into two general categories: quick fix force (QFF) and "other sustaining base." These categories identify and alert deployable units that have an interim mission related installation support role. However, this identification method does not preclude the installation commander's using assets of other late deploying units, not identified as sustaining base, as support requirements are identified during execution of OPLANS.
(5) QFF units are "critical" sustaining base nondeploying and deploying units which received special priority resourcing plus full-time manning positions. QFF units have been assigned a RDYLD of 45 to ensure availability of QFF missions for 30-40 days. QFF units are identified with a third position ROBCO of 1 through 6. Deployable QFF units have a ROBCO third position of 4, 5, or 6. Ideally, no deployable units would be used in this category. Technically, component 1 units are not QFF; however, these and other RC TDA units are listed to show installation assets.
(6) "Other sustaining base" are late deploying units, whose deployment requirements permit them to be mobilized early and used in a mission related installation support role. Those late deploying units will not be especially resourced or fenced from OPLAN deployment requirements and will be identified in the data base using a third position ROBCO of 7. Deployable units in this category must be released from their installation support role in time to meet deployment dates which may change with revised versions of OPLAN TPFDDS ROBCO third position 8, other RC training base units, are included in this category.
(7) Engineer battalions have not been identified solely for installation support but may be utilized for mission related construction tasks incident to support of installation mobilization missions. Installations at which no engineer construction support units are stationed will request needed engineer unit support from the appropriate CONUSA.
(8) Available late deploying and uncommitted brigade, group and battalion HHC may be used as branch immaterial command and control elements for mobilized units.
(9) Training centers, other than current Active Army ATCs, will be activated normally only after full mobilization has been directed. Detailed trainee/student input projections are as shown in DA/TRADOC/HSC post-mobilization Army Program for individual training (MOB ARPRINT).
(10) The MTBSP portrays unit deployment requirements (reverse planning) vis-a-vis unit capability to deploy (forward planning). The following methodology is used to establish this relationship:
a. To determine unit deployment requirements, the DRL is determined by subtracting movement times to POE and POD from the EAD (earliest arrival date) to arrive at a worst case situation.
b. To determine unit deployment capability, the RDYLD is determined by adding alert/assembly, movement, training, and processing times.
c. The DRL and RDYLD are compared, and the EDD is selected from greater of the two values (RDYLD or DRL) in terms of time.
d. The EDDS and/or EDDA should be used to plan unit mobilization and deployment. However, unit preparation for deployment should be expedited to improve unit availability upon OPLAN execution.
(11) The following are clarifications of selected data field relationships which have created questions in the past:
a. If the EDD is greater than the LAD, this indicates that the unit is not capable of meeting deployment requirements and that the unit will arrive late in the theater of operations, unless accepted at lesser capability by the supported CINC.
b. If the MBSAD is greater than the RDYLD, but sufficient time is available to meet deployment, requirements, disregard RDYLD and use EDDS and/or EDDA to plan unit flow through the mobilization location.
c. If the RDYLD equals 45, the unit is a quick fix force (QFF); is fenced to perform "critical" interim mission related installation support and is available for deployment on day 45. These units must be prepared for deployment by the RDYLD or earlier if circumstances permit.
d. These data are machine generated based on planning models and OPLAN TFPDDs, therefore, elective changes cannot be made.
i. Clarification Guidance.
HQ FORSCOM is primarily interested in displaying unit stationing and mobilization data to facilitate mobilization planning at the various echelons of command. This classification guidance is not designed to restrict the flow of wartime information. Rather, it is to preclude unauthorized disclosure of U.S. Forces task organized to support specific wartime missions. It is the responsibility of all to safeguard this sensitive information and to limit disclosure on a need-to-know basis.
j. Specific Guidance.
(1) Basic Unit Identity Data derived from the UNITREP File is Unclassified when treated singularly or in list form.
(2) ROBCOs by themselves are not classified IAW 11-38. The classification of lists drawn from computer data bases using ROBCOs will be determined by the composition of the list of forces. The preparing headquarters will use AR 380-90 as a guide.
(3) General statements of deployment locations for USAR and ARNG unit (e.g., "TO EUROPE") are unclassified. Deployment locations for these units are unclassified if these locations are the current locations of their respective gaining commands. Information reflecting deployment locations of a USAR or ARNG unit that is not the same as the current location of the gaining commands will be classified secret. A deployment area identified with the related OPLAN is classified based on guidance in the OPLAN involved.
(4) MDATE, MBODD, and MBSAD are unclassified singularly or in list form.
(5) RDYLD, EDDS, and EDDA by themselves are unclassified. When groupings of units (Troop Lists) are created, they are treated IAW Paragraph 5A, AR 380-90.
(6) SLADs and ALADs are classified SECRET.
k. Additional Guidelines.
(1) Automated retrievals of information extracted from the WWMCCS requires a subjective review as to classification. A determination must be made on a case-by-case basis by the user.
(2) RSC and TAG/STARC should send separate unclassified mobilization data sheets to the units involved. Mobilization data sheets should be reviewed carefully for content before transmitted. Only minimum information, necessary for a subordinate unit to plan for mobilization, should be provided the subordinate. Information required only at higher levels of command should remain there. The purpose of this is not to restrict units from receiving information that they need, but to ensure that sensitive mobilization planning information is only handled by those commanders/ staffs with a need to know.
(3) Particular care should be exercised at conferences and workshops to properly safeguard classified information and material. Operations security (OPSEC) should be maximized to prevent unauthorized disclosure of both sensitive unclassified and classified information.
(4) As with all information dissemination, the final responsibility for classification rests with the originator. In each case, the amount of information released and accompanying verbage must be analyzed and common sense used in applying classification guidance. Storage requirements and personnel security clearances must be adjusted accordingly.
l. Schedule for Submission of MTBSP correction/update data.
(1) UNITREP Data - As required by FORSCOM/TRADOC Regulation 525-3.
(2) Deployment Data - As generated from OPLAN TPFDDs.
(3) Mobilization station changes from CONUSA to FORSCOM - 30 April annually.
(4) MDATE, MBODD, and MBSAD - 31 March annually.
(5) CI Location and MCMD - 31 March annually.
