ANALYSIS OF MOVEMENT REQUIREMENTS FOR UNIT EQUIPMENT SEPTEMBER 2000 CENTER FOR ARMY ANALYSIS 6001 GOETHALS ROAD FORT BELVOIR, VA

Similar documents
From the onset of the global war on

The Army Proponent System

A udit R eport. Office of the Inspector General Department of Defense. Report No. D October 31, 2001

Ballistic Protection for Expeditionary Shelters

In 2007, the United States Army Reserve completed its

White Space and Other Emerging Issues. Conservation Conference 23 August 2004 Savannah, Georgia

Battle Captain Revisited. Contemporary Issues Paper Submitted by Captain T. E. Mahar to Major S. D. Griffin, CG 11 December 2005

ORGANIZATION AND FUNDAMENTALS

DoD Countermine and Improvised Explosive Device Defeat Systems Contracts for the Vehicle Optics Sensor System

Report Documentation Page

Chief of Staff, United States Army, before the House Committee on Armed Services, Subcommittee on Readiness, 113th Cong., 2nd sess., April 10, 2014.

Required PME for Promotion to Captain in the Infantry EWS Contemporary Issue Paper Submitted by Captain MC Danner to Major CJ Bronzi, CG 12 19

Infantry Companies Need Intelligence Cells. Submitted by Captain E.G. Koob

Joint Committee on Tactical Shelters Bi-Annual Meeting with Industry & Exhibition. November 3, 2009

Using Spoken Language to Facilitate Military Transportation Planning

AMC s Fleet Management Initiative (FMI) SFC Michael Holcomb

The Army Executes New Network Modernization Strategy

MAKING IT HAPPEN: TRAINING MECHANIZED INFANTRY COMPANIES

Contemporary Issues Paper EWS Submitted by K. D. Stevenson to

terns Planning and E ik DeBolt ~nts Softwar~ RS) DMSMS Plan Buildt! August 2011 SYSPARS

Mobile Subscriber Equipment (MSE) Operations

SPECIAL REPORT Unsurfaced Road Maintenance Management. Robert A. Eaton and Ronald E. Beaucham December 1992

Blue on Blue: Tracking Blue Forces Across the MAGTF Contemporary Issue Paper Submitted by Captain D.R. Stengrim to: Major Shaw, CG February 2005

DoD Scientific & Technical Information Program (STIP) 18 November Shari Pitts

Determining and Developing TCM-Live Future Training Requirements. COL Jeffrey Hill TCM-Live Fort Eustis, VA June 2010

The Effects of Multimodal Collaboration Technology on Subjective Workload Profiles of Tactical Air Battle Management Teams

ASAP-X, Automated Safety Assessment Protocol - Explosives. Mark Peterson Department of Defense Explosives Safety Board

The Army s Mission Command Battle Lab

Shadow 200 TUAV Schoolhouse Training

DDESB Seminar Explosives Safety Training

TITLE: Vitamin D and Related Genes, Race and Prostate Cancer Aggressiveness

DANGER WARNING CAUTION

Independent Auditor's Report on the Attestation of the Existence, Completeness, and Rights of the Department of the Navy's Aircraft

NORMALIZATION OF EXPLOSIVES SAFETY REGULATIONS BETWEEN U.S. NAVY AND AUSTRALIAN DEFENCE FORCE

The U.S. military has successfully completed hundreds of Relief-in-Place and Transfers of

CONTRACTING ORGANIZATION: Landstuhl Regional Medical Center Germany

Incomplete Contract Files for Southwest Asia Task Orders on the Warfighter Field Operations Customer Support Contract

Acquisition. Air Force Procurement of 60K Tunner Cargo Loader Contractor Logistics Support (D ) March 3, 2006

CONTRACTING ORGANIZATION: Walter Reed Army Medical Center Washington, DC

Expeditionary Basecamp Passive

TABLES OF ORGANIZATION AND EQUIPMENT

Office of Inspector General Department of Defense FY 2012 FY 2017 Strategic Plan

Test and Evaluation Strategies for Network-Enabled Systems

Mission Assurance Analysis Protocol (MAAP)

Improving the Quality of Patient Care Utilizing Tracer Methodology

Training and Evaluation Outline Report

User Manual and Source Code for a LAMMPS Implementation of Constant Energy Dissipative Particle Dynamics (DPD-E)

Operational Energy: ENERGY FOR THE WARFIGHTER

World-Wide Satellite Systems Program

Training and Evaluation Outline Report

Afloat Electromagnetic Spectrum Operations Program (AESOP) Spectrum Management Challenges for the 21st Century

Defense Health Care Issues and Data

A Military C2 Professional s Thoughts on Visualization

Comparison of Navy and Private-Sector Construction Costs

For the Period June 1, 2014 to June 30, 2014 Submitted: 15 July 2014

Statement of Rudolph G. Penner Director Congressional Budget Office

Information Technology

Environment: Some iterations of this task should be performed in MOPP 4. This task should be trained under IED Threat conditions.

Office of the Inspector General Department of Defense

Evolutionary Acquisition an Spiral Development in Programs : Policy Issues for Congress

Cerberus Partnership with Industry. Distribution authorized to Public Release

Transportability and the Acquisition Process

at the Missile Defense Agency

Military to Civilian Conversion: Where Effectiveness Meets Efficiency

Where Have You Gone MTO? Captain Brian M. Bell CG #7 LTC D. Major

The first EHCC to be deployed to Afghanistan in support

Training and Evaluation Outline Report

CHAIRMAN OF THE JOINT CHIEFS OF STAFF INSTRUCTION

Software Intensive Acquisition Programs: Productivity and Policy

UNCLASSIFIED R-1 ITEM NOMENCLATURE

Impact of Corrosion on Ground Vehicles: Program Review, Issues and Solutions

Life Support for Trauma and Transport (LSTAT) Patient Care Platform: Expanding Global Applications and Impact

Capability Planning for Today and Tomorrow Installation Status Report

Obstacle Planning at Task-Force Level and Below

USMC Expeditionary Energy

Mission Task Analysis for the NATO Defence Requirements Review

Army Regulation Army Programs. Department of the Army. Functional Review. Headquarters. Washington, DC 12 September 1991.

Training and Evaluation Outline Report

Report No. D May 14, Selected Controls for Information Assurance at the Defense Threat Reduction Agency

U.S. ARMY AVIATION AND MISSILE LIFE CYCLE MANAGEMENT COMMAND

ACQUISITION OF THE ADVANCED TANK ARMAMENT SYSTEM. Report No. D February 28, Office of the Inspector General Department of Defense

PEO Missiles and Space Overview Briefing for the 2010 Corrosion Summit February 2010 Huntsville, AL

Cold Environment Assessment Tool (CEAT) User s Guide

Navy CVN-21 Aircraft Carrier Program: Background and Issues for Congress

United States Air Force 423 SCMS Hydraulic Actuator Chrome Replacement

Engineered Resilient Systems - DoD Science and Technology Priority

The Need for a Common Aviation Command and Control System in the Marine Air Command and Control System. Captain Michael Ahlstrom

ANNEX E MHAT SUPPORTING DOCUMENTS. Operation Iraqi Freedom (OIF) Mental Health Advisory Team (MHAT) 16 December 2003

Transportability and the Acquisition Process

Inside the Beltway ITEA Journal 2008; 29: Copyright 2008 by the International Test and Evaluation Association

The Affect of Division-Level Consolidated Administration on Battalion Adjutant Sections

Google Pilot / WEdge Viewer

Command and staff service. No. 10/5 The logistic and medical support service during C2 operations.

TARGET ACQUISITION TAB TO THE FIELD ARTILLERY SUPPORT APPENDIX AND THE RADAR DEPLOYMENT ORDER. Section I. TARGET ACQUISITION TAB DESCRIPTION

Tannis Danley, Calibre Systems. 10 May Technology Transition Supporting DoD Readiness, Sustainability, and the Warfighter. DoD Executive Agent

Perspectives on the Analysis M&S Community

The forces to deploy will include: 19 Light Brigade Headquarters and Signal Squadron (209) Elements of 845 Naval Air Squadron

Development of a Hover Test Bed at the National Hover Test Facility

The Fully-Burdened Cost of Waste in Contingency Operations

Program Management Office, Medical Support Systems

Transcription:

ANALYSIS OF MOVEMENT REQUIREMENTS FOR UNIT EQUIPMENT SEPTEMBER 2000 CENTER FOR ARMY ANALYSIS 6001 GOETHALS ROAD FORT BELVOIR, VA 22060-5230

DISCLAIMER The findings of this report are not to be construed as an official Department of the Army position, policy, or decision unless so designated by other official documentation. Comments or suggestions should be addressed to: Director Center for Army Analysis ATTN: CSCA-MD 6001 Goethals Road Fort Belvoir, VA 22060-5230

REPORT DOCUMENTATION PAGE Form Approved OMB No. 074-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE September 2000 3. REPORT TYPE AND DATES COVERED Final, Start date - September 2000 4. TITLE AND SUBTITLE 5. FUNDING NUMBER Analysis of Movement Requirements for Unit Equipment 6. AUTHOR(S) Mr. Giles D. Mills III 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Center for Army Analysis 6001 Goethals Road Fort Belvoir, VA 22060-5230 9. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) The Army G3 ATTN: DAMO-SSW 400 Army Pentagon Washington, DC 20310-0400 11. SUPPLEMENTARY NOTES 8. PERFORMING ORGANIZATION REPORT NUMBER 10. SPONSORING / MONITORING AGENCY REPORT NUMBER 12a. DISTRIBUTION / AVAILABILITY STATEMENT Approved for public release; dissemination unlimited A 13. ABSTRACT (Maximum 200 Words) This project focused on developing a methodology to conduct a deployment analysis at the line item number (LIN) level. Analysis could be done for future projects looking at the type of equipment required for deployment. The project used the results of the Total Army Analysis - 2007 (TAA-07) base case as a test bed for the prototype developed in this project. The process is very flexible and uses Access and Excel for its execution and output display. 14. SUBJECT TERMS Line item number (LIN), Total Army Analysis - 2007, standard requirement code (SRC), tactical assembly area (TAA), movement requirements, deployment profile, unit equipment, combat support (CS), combat service support (CSS) 15. NUMBER OF PAGES 16. PRICE CODE 17. SECURITY CLASSIFICATION OF REPORT UNCLASSIFIED NSN 7540-01-280-5500 Standard Form 298 18. SECURITY CLASSIFICATION OF THIS PAGE UNCLASSIFIED 19. SECURITY CLASSIFICATION OF ABSTRACT UNCLASSIFIED 20. LIMITATION OF ABSTRACT SAR

(THIS PAGE INTENTIONALLY LEFT BLANK)

ANALYSIS OF MOVEMENT REQUIREMENTS FOR UNIT EQUIPMENT SUMMARY THE PROJECT PURPOSE was to create an ability to analyze current deployment analyses at the line item number (LIN) level of detail in support of the Division Redesign. THE PROJECT SPONSOR was the US Army G3. THE PROJECT OBJECTIVES were to: (1) Develop an automated process to analyze deployment results at the LIN level of detail. (2) Create flexibility in the automated process for use in a variety of deployment analyses. THE SCOPE OF THE PROJECT (1) Use the Total Army Analysis - 2007 (TAA-07) base case as a data set in the development of the process. (2) Develop the process to expand a force list at the standard requirement code (SRC) level vice unit level. THE BASIC APPROACH used in this report was to develop a series of queries in Access to easily expand the deployment results. THE PRINCIPAL FINDINGS of the AMRUE Report are: (1) For TAA-07, trucks accounted for the largest short ton (STON) deployment requirements for both theaters. (2) The process is flexible and can be used for a variety of future projects. THE PROJECT EFFORT was directed by Mr. Giles D. Mills III, Mobilization and Deployment Division, Center for Army Analysis (CAA). COMMENTS AND QUESTIONS may be sent to the Director, Center for Army Analysis, ATTN: CSCA-MD, 6001 Goethals Road, Suite 102, Fort Belvoir, VA 22060-5230. i

(THIS PAGE INTENTIONALLY LEFT BLANK) ii

CONTENTS Page 1 INTRODUCTION...1 1.1 Background... 1 1.2 Purpose... 2 1.3 Objective... 3 1.4 Scope... 4 1.5 Data Requirements... 5 1.6 Methodology... 8 1.7 Environment... 9 2 ANALYSIS...11 2.1 Output Layers... 11 2.2 Output Data Matrix... 12 2.3 Output Data Matrix - Illustrative... 13 2.4 Output... 14 3 CONCLUSION...27 3.1 Summary... 27 APPENDIX A PROJECT CONTRIBUTORS... A-1 APPENDIX B REQUEST FOR ANALYTICAL SUPPORT...B-1 GLOSSARY... Glossary-1 FIGURES Figure 1. Background... 1 Figure 2. Purpose... 2 Figure 3. Objective... 3 Figure 4. Scope... 4 Figure 5. Data Requirements... 5 Figure 6. Data Requirements (cont)... 6 Figure 7. Data Requirements (cont)... 7 Figure 8. Methodology... 8 Figure 9. Environment... 9 Figure 10. Output Layers... 11 Figure 11. Output Data Matrix... 12 Figure 12. Output Data Matrix - Illustrative... 13 Figure 13. SWA STON and Quantities (C+250)... 14 Figure 14. NEA STON and Quantities (C+250)... 15 Figure 15. SWA Equipment Deployment Profile - STON... 16 Figure 16. SWA Equipment Deployment Profile - Quantity... 17 Figure 17. NEA Equipment Deployment Profile - STON... 18 Figure 18. NEA Equipment Deployment Profile - Quantity... 18 Figure 19. SWA UE Unit Type Breakout (STON)... 19 Figure 20. SWA Deployment Profile by Unit Type... 20 Figure 21. NEA UE Unit Type Breakout... 21 Figure 22. NEA Deployment Profile by Unit Type... 22 iii

Figure 23. SWA Army UE STON by Equipment Category... 23 Figure 24. NEA Army UE STON by Equipment Category... 24 Figure 25. SWA Truck and Combat Vehicle Profiles - Quantity... 25 Figure 26. NEA Truck and Combat Vehicle Profiles - Quantity... 26 Figure 27. Summary... 27 iv

1 INTRODUCTION 1.1 Background Combat vehicle structure has been the focus of the Chief of Staff of the Army (CSA) redesign initiative, and little analysis has been done on the other vehicle types Current deployment analyses give little visibility on pieces of equipment, instead focusing on unit type (SRC) Figure 1. Background Prior deployment analyses were done at the unit level of resolution; however, there was a need to have the ability to look at the deployment requirements at the line item number (LIN) level. With this capability, an analyst could gain insight to the types of equipment that are part of the requirement. The process should have the capability to aggregate similar types of equipment-- for example, trucks. A quick turnaround time was also recognized as a requirement. General Shinseki, Army Chief of Staff, has a vision that the Army should have brigades designed to be more deployable. AMRUE INTRODUCTION 1

1.2 Purpose To give an expansion to deployment results, the Director requested a count/ston/sq ft rollup for certain types of equipment (i.e., trucks, generators, etc.) This expansion would help in the current analysis of the Division Redesign Initiative Figure 2. Purpose A process should be developed to provide an expansion to the current deployment process. The process would be used to gain information for the analysis of redesigning the Army brigade structure. 2 INTRODUCTION AMRUE

1.3 Objective To develop an automated methodology to analyze deployment results at an equipment (LIN)-level resolution Figure 3. Objective A process should be developed to provide a quick turnaround capability for future analyses. The process should not modify any of the existing models used in the current deployment process, but should be a separate expansion to be executed when required. The process should use software that is easily obtained. Flexibility should be built into the process for use over a wide range of analysis. AMRUE INTRODUCTION 3

1.4 Scope Testbed database is the TAA-07 E/W Final Deployment Automated design for future databases Design will work easily for movement requirements (vice deployment results) Figure 4. Scope The Total Army Analysis - 2007 (TAA-07) base case was used while the process was being developed; however, the process is flexible enough to use in other analyses. Output from the AMRUE process using the TAA-07 base case was used to show the capability of the process. 4 INTRODUCTION AMRUE

1.5 Data Requirements Deployment results Time-phased by delivery day At SRC level with theater delivery, origin, POE, POD, destination LIN-level breakout for each SRC Gives qty, weight, and dimensional data Assumes cargo vehicles are loaded Rolls up all equipment less than 6 X 2 X 2 Figure 5. Data Requirements One input to this process is the standard deployment results which are converted from a text file to an Access database file. This file contains the list of units that are deployment requirements as well as other deployment information, such as required delivery date, origin, and destination. A second file is the LIN listing for each standard requirement code (SRC). The file contains a listing of the LINs and quantity associated with each SRC and the dimension and weight for each LIN. The caveat for this file is that no piece of equipment that is less than 6 feet x 2 feet x 2 feet is listed as a separate entry. AMRUE INTRODUCTION 5

Unit type file: defines the unit (SRC) with the following criteria: Combat: all units organic to a division, armored cavalry regiment (ACR), separate bde, corps assets CS: units in the following branches, not in the combat category (Aviation, Chem, Engineer, Field Artillery, Signal, Military Police, Special Forces, PSYOPS, Military Intelligence, Air Defense CSS: units in the following branches, not in the combat category (Medical, Ordnance, Quartermaster, Pers Serv Sup, Military History, Judge Advocate, Civil Affairs, Maintenance, Public Affairs, Headquarters, Transportation Figure 6. Data Requirements (cont) The process has many user-defined areas. Users have the ability to define the types of units they are interested in aggregating. This definition can go all the way down to the SRC level. The example that was used for developing the process is shown in Figure 6 above. 6 INTRODUCTION AMRUE

LIN category file (developed by user) Truck: cargo-carrying trucks Trailer: cargo-carrying trailers Generators: over 3 KW Combat: combat ground vehicles, artillery Combat Spt: armored carriers, recovery veh Engineer: bridging,construction vehicles Helicopters: all helicopters, including attack Aircraft: fixed wing aircraft Other: not in a category above Figure 7. Data Requirements (cont) Users also have the ability to define the types of LINs they are interested in aggregating. This definition can go all the way down to the LIN level. The example that was used for developing the process is shown in Figure 7 above. AMRUE INTRODUCTION 7

1.6 Methodology Unit Type List Time-phased Deployed/Req Army Units Equipment by Unit Deployed Army Equip (MTMC-TEA) A LIN Category List Cumulate Measures by LIN Type, etc. Cumulative Measures by Equip, Theater, Unit Type and Day, POD, TAA, OTHER A Create Tables for Analysis Figure 8. Methodology The flowchart in Figure 8 depicts the process that was developed at the highest view. The shaded boxes are input files to the process. The time-phased deployment requirements come from the Global Deployment Analysis System (GDAS) Model, and the equipment by unit comes from Military Traffic Management Command Transportation Engineering Agency (MTMC- TEA). The unit type list and the LIN category list are the user-defined files mentioned earlier. The whole process is done with Access using a series of queries. First, the time-phased deployment requirements and the equipment by unit are combined to produce a listing of the requirement at the LIN level. From here the aggregation begins; the user defines using the unit type list and the LIN category list to aggregate the requirement at whatever level is necessary for the project. 8 INTRODUCTION AMRUE

1.7 Environment PC-based Access - Data Manipulation Excel - Graphing Figure 9. Environment This process can run on a PC using Access for the data manipulation and using Excel to produce graphs for the output. AMRUE INTRODUCTION 9

(THIS PAGE INTENTIONALLY LEFT BLANK) 10 INTRODUCTION AMRUE

2 ANALYSIS This chapter discusses some analysis of the TAA-07 base case data that was used to create the process. 2.1 Output Layers Theater Location (POD, etc.) Unit Type LIN Type Measures Figure 10. Output Layers Figure 10 shows the different layers that can be used to aggregate the data. For example, once the user defines the aggregation at the theater level, then he/she defines the aggregation at the location level, etc. The user may also choose at any level not to aggregate. AMRUE ANALYSIS 11

2.2 Output Data Matrix Theater Location Unit type Equip type Measure SWA N/A Combat Truck Quantity NEA CS Trailer STON CSS Combat Veh Sq ft Combat Sup Cube ft Generator Engineer Helicopter Aircraft Other Figure 11. Output Data Matrix OR.. This is just one example of how a user may choose to aggregate; this is the aggregation scheme that was chosen to test the process. 12 ANALYSIS AMRUE

2.3 Output Data Matrix - Illustrative Theater Location Unit type Equip type Measure NEA Kimhae Hvy Div Truck Quantity Pusan Lt Div Cbt Enabler STON TAA1 Reserve Cbt Medical Sq ft TAA2 Field Arty Log Enabler Cube ft Ft Hood CS/CSS Generator HET MLRS Bottom Line: Very Flexible Figure 12. Output Data Matrix - Illustrative Figure 12 shows another aggregation scheme. TAA1 and TAA2 would be specific tactical assembly areas (TAA) located in a theater. Users may create their own unit types and equipment types, such as the logistic enablers. The user would have to specify the LINs that would be defined as logistic enablers. AMRUE ANALYSIS 13

2.4 Output TYPE STONS QTY AIRCRAFT 354 44 COMBAT VEH 155,178 5,285 COMBAT SUP 63,772 1,964 ENGINEER 124,040 5,705 GENERATOR 14,928 8,916 HELICOPTER 10,454 1,309 OTHER 607,048 174,756 TRAILER 247,610 37,044 TRUCK 567,433 43,855 TOTAL 1,790,817 Figure 13. SWA STON and Quantities (C+250) From the TAA-07 base case (Southwest Asia (SWA) portion), this is a summary of deployment requirements using the LIN types created for the prototype. OTHER includes all pieces of equipment not listed in the other categories. Trucks make up the greatest deployment requirement to SWA for all the named categories. To reduce the deployment requirement, one of the areas of concentration would be to review the truck requirement. 14 ANALYSIS AMRUE

TYPE STONS QTY AIRCRAFT 354 44 COMBAT VEH 110,009 4,001 COMBAT SUP 39,557 1,266 ENGINEER 88,205 4,437 GE NERATOR 10,225 6,400 HELICOPTER 6,701 978 OTHER 442,376 141,852 TRAILER 127,588 20,598 TRUCK 383,287 29,152 TOTAL 1,208,302 Figure 14. NEA STON and Quantities (C+250) Trucks also make up the greatest deployment requirement to Northeast Asia (NEA) for all the named categories. To reduce the deployment requirement, one of the areas of concentration would be to review the truck requirement. AMRUE ANALYSIS 15

STON 1,800,000 1,600,000 1,400,000 1,200,000 1,000,000 800,000 600,000 AIRCRAFT COMBAT VEH COMBAT SPT ENGINEER GENERATOR HELICOPTER OTHER TRAILER TRUCK TOTAL 400,000 200,000 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) Figure 15. SWA Equipment Deployment Profile - STON One of the other features of this process is the ability to analyze timing of the requirements. Figure 15 shows the LIN category STON buildup over time. Included in the figure is the total deployment requirement to give a relative percentage for each LIN category. This figure shows another way to graphically portray the greater truck deployment requirement compared to all other named categories. 16 ANALYSIS AMRUE

QTY 160000 140000 120000 100000 80000 60000 40000 AIRCRAFT COMBAT VEH COMBAT SPT ENGINEER GENERATOR HELICOPTER OTHER TRAILER TRUCK 20000 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) Figure 16. SWA Equipment Deployment Profile - Quantity Figures 16 through 18 show the LIN category quantity buildup over time. These figures show another way to graphically portray the greater truck deployment requirement compared to all other named categories. AMRUE ANALYSIS 17

STON 1200000 1000000 800000 600000 400000 AIRCRAFT COMBAT VEH COMBAT SPT ENGINEER GENERATOR HELICOPTER OTHER TRAILER TRUCK TOTAL 200000 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) Figure 17. NEA Equipment Deployment Profile - STON QTY 140000 120000 100000 80000 60000 40000 AIRCRAFT COMBAT VEH COMBAT SPT ENGINEER GENERATOR HELICOPTER OTHER TRAILER TRUCK 20000 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) Figure 18. NEA Equipment Deployment Profile - Quantity 18 ANALYSIS AMRUE

TYPE STONS (k) CBT 513 CS 477 CSS 801 TOTAL 1791 CSS (44%) CBT (29%) CS (27%) Figure 19. SWA UE Unit Type Breakout (STON) The breakdown shown in Figure 19 reflects the percentage of the deployment requirement generated by each of the unit types in SWA. As can be seen, combat service support (CSS) units generate the largest percentage of the deployment requirement. AMRUE ANALYSIS 19

STON 800000 CBT STON 800000 CS 700000 700000 600000 600000 500000 500000 400000 400000 300000 300000 200000 200000 100000 100000 0 0 1 0 20 30 4 0 5 0 60 7 0 80 90 DAY (C+) 100 110 120 CSS 1 3 0 140 150 0 0 10 2 0 30 4 0 DAY (C+) 5 0 60 7 0 80 AIRCRAFT 90 100 110 120 130 1 40 150 STON 800000 700000 600000 500000 400000 300000 200000 100000 COMBAT VEH COMBAT SPT ENGINEER GENERATOR HELICOPTER OTHER TRAILER TRUCK 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) TOTAL Figure 20. SWA Deployment Profile by Unit Type The graphs in Figure 20 provide a time-phased breakdown of the type LIN STON requirements by unit type for SWA. 20 ANALYSIS AMRUE

TYPE STONS (k) CBT 367 CS 366 CSS 475 TOTAL 1208 CSS (40%) CBT (30%) CS (30%) Figure 21. NEA UE Unit Type Breakout This breakdown reflects the percentage of the deployment requirement generated by each of the unit types in NEA. As can be seen, CSS units generate the largest percentage of the deployment requirement. AMRUE ANALYSIS 21

STON CBT STON CS 500000 500000 450000 450000 400000 400000 350000 350000 300000 300000 250000 250000 200000 200000 150000 150000 100000 100000 50000 50000 STON 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 500000 450000 400000 350000 300000 250000 200000 150000 100000 50000 DAY (C+) CSS 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) AIRCRAFT COMBAT VEH COMBAT SPT ENGINEER GENERATOR HELICOPTER OTHER TRAILER TRUCK 0 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 DAY (C+) TOTAL Figure 22. NEA Deployment Profile by Unit Type The graphs in Figure 22 provide a time-phased breakdown of the type LIN STON requirements by unit type for NEA. 22 ANALYSIS AMRUE

TYPE STONS (k) CO MBAT VEH 155 ENGINEER 124 TRUCK 567 TRAILER 248 OTHER 607 REM CAT * 90 TOTAL 1791 REM CAT * (5%) OTHER (33%) COMBAT (9%) TRUCK (32%) ENGINEER (7%) TRAILER (14%) * REM CAT includes AIRCRAFT, CBT SPT, AND HELICOPTERS Figure 23. SWA Army UE STON by Equipment Category Figure 23 shows the breakdown of the deployment requirement by LIN category for SWA. As can be seen, the truck STON requirements are the greatest of the named categories. AMRUE ANALYSIS 23

TYPE STONS (k) CO MBAT VEH 110 ENGINEER 88 TRUCK 383 TRAILER 128 OTHER 442 REM CAT * 57 TOTAL 1208 REM CAT * (5%) COMBAT VEH (9%) ENGINEER (7%) OTHER (36%) TRUCK (32%) TRAILER (11%) * REM CAT includes AIRCRAFT, CBT SPT, AND HELICOPTERS Figure 24. NEA Army UE STON by Equipment Category Figure 24 shows the breakdown of the deployment requirement by LIN category. As you can see, the truck STON requirements are the greatest of the named categories for NEA as well. 24 ANALYSIS AMRUE

QTY 50000 45000 40000 35000 30000 25000 20000 15000 10000 Truck Deploy Truck Req Combat Veh Deploy Combat Veh Req 5000 0 0 20 40 60 80 100 120 140 1 60 TIME (C+) Figure 25. SWA Truck and Combat Vehicle Profiles - Quantity 1 80 2 00 220 240 Figure 26 shows the lag in the deployment of trucks by quantity compared to the time they are required in SWA. By contrast, combat vehicles are deployed when they are needed. AMRUE ANALYSIS 25

QTY 35000 30000 25000 Truck D eploy 20000 Truck Req 15000 Combat Veh Deploy 10000 Combat Veh Req 5000 0 0 20 40 60 80 100 120 140 160 180 200 220 240 TIME (C+) Figure 26. NEA Truck and Combat Vehicle Profiles - Quantity Figure 28 shows the lag in the deployment of trucks by quantity compared to the time they are required. By contrast, the combat vehicles are deployed when they are needed. 26 ANALYSIS AMRUE

3 CONCLUSION 3.1 Summary Trucks account for 32% of STON of Army unit equipment required to be moved, larger than any other LIN group Process is automated for use in future projects involving deployment analysis; can be used for movement requirements Process is very flexible Figure 27. Summary The process was created for future deployment analysis or movement requirements analysis. The process is very flexible due to amount of control the user has in the process. Depending on the user s requirements, the user-defined input files will allow the process to create the data that is needed. AMRUE CONCLUSION 27

(THIS PAGE INTENTIONALLY LEFT BLANK) 28 CONCLUSION AMRUE

APPENDIX A PROJECT CONTRIBUTORS 1. PROJECT TEAM a. Project Director Mr. Giles D Mills III, Mobilization and Deployment Division b. Team Members Ms. Pinal Patel Ms. Keisha Dumas 2. PRODUCT REVIEW Dr. Ralph E. Johnson, Quality Assurance Ms. Nancy M. Lawrence, Publications Center Ms. Tina Davis, Publications Center AMRUE A-1

(THIS PAGE INTENTIONALLY LEFT BLANK) A-2 AMRUE

APPENDIX B REQUEST FOR ANALYTICAL SUPPORT P Performing Division: MD Account Number: 2000029 A Tasking: Verbal Mode (Contract-Yes/No): No R T Acronym: AMRUE-07 Title: Analysis of Movement Requirements for Unit Equipment 1 Start Date: 04-Nov-99 Estimated Completion Date: 31-Mar-00 Requestor/Sponsor (i.e., DCSOPS): DCSOPS Sponsor Division: SSW Resource Estimates: a. Estimated PSM: 2 b. Estimated Funds: $0.00 c. Models to be ADAPT Description/Abstract: The objective of this project is to characterize the movement requirements for both major theater wars by type of unit equipment (e.g., truck, trailer, combat vehicle, helicopter, engineer equipment, etc.). The project will examine the required force from TAA-07 and provide a data base to support future analyses. Study Director/POC Signature: Original Signed Phone#: 703-806-5447 Study Director/POC: Mr. Giles Mills III If this Request is for an External Project expected to consume 6 PSM or more, Part 2 Information is Not Required. See Chap 3 of the Project Directors' Guide for preparation of a Formal Project Directive. Background: P When deploying to a major theater war, much of the focus is on the movement of combat systems (e.g., tanks, artillery, helicopters, etc.) However, the Army deploys significant numbers of noncombat systems to the theater. This project will categorize the deployment of unit equipment, providing visibility to what is required for each theater. A R T Scope: Using the force structure requirements from the Total Army Analysis, determine in 10-day increments the numbers of different types of vehicles that the Army deploys to the major theater war--east and West. 2 Issues: Identify suitable classifications to group various types of vehicles. Determine numbers of vehicles in units based on approved modified tables of organization and equipment. Determine the flow of units into theater based on the Total Army Analysis deployment analysis. Milestones: Conduct IARB by the end of February. Deliver completed analysis to the sponsor on 31 March 2000. Signatures Division Chief Signature: Original Signed and Dated Date: Division Chief Concurrence: Mr. Franklin Mckie Sponsor Signature: Original Signed and Dated Date: Sponsor Concurrence (COL/DA Div Chief/GO/SES) COL Jerry Brown AMRUE B-1

(THIS PAGE INTENTIONALLY LEFT BLANK) B-2 AMRUE