United States Marine Corps - Boot Camp & Military Fitness ...



United States Marine CorpsFindings and RecommendationsAnalysis of Combat Service Support (CSS) Requirements for Marine Corps Forces Special Operations Command (MARSOC)Submitted by:Analysis Branch, Operations Analysis Division27 January 2009INTENTIONALLY LEFT BLANKExecutive SummaryBackground and Purpose1. At the request of Marine Corps Forces Special Operations Command (MARSOC) a team from Operations Analysis Division, Marine Corps Combat Development Command (OAD MCCDC) conducted a study to determine the requirements for an expeditionary Combat Service Support (CSS) capability. The study, executed by OAD personnel with support from the Wargaming Division of the Marine Corps Warfighting Laboratory (MCWL), ran from June to December 2008.2. Now completing its third year of operation, the first MARSOC deployment occurred six months after stand up. Since August 2006:MARSOC companies have continuously deployed, primarily to Central Command (CENTCOM) Employment is directed by the Theater Special Operations Commander (TSOC)Support is provided through the Joint Special Operations Task Force (JSOTF)MARSOC teams (i.e., an element with 12-14 personnel) have deployed regularly to other theaters. Teams typically arrange for logistical support through contracts with local vendors. These contracts are coordinated with personnel at the appropriate US Embassy and contribute to mission success while minimizing the need for organic logistic support.Appendix A contains more detailed information on MARSOC, it’s constituent elements and descriptions of typical special operations missions3. Prior to commencement of this study, MARSOC conducted an internal re-organization, resulting in the transfer of a number of logistics billets from the Marine Special Operations Support Group (MSOSG) to the Marine Special Operations Battalions (MSOB). This led to a revised Table of Organization (T/O), and a new deployment model, for the Marine Special Operations Company (MSOC). The MSOC now deploys with its organic complement of 53 Marines and Sailors, supported by an enabling detachment of 31 Marines and Sailors. This organization is shown in REF _Ref219882578 \h Figure 1. Note that most of the MSOSG personnel provide operational capabilities, while most of the personnel from the MSOB provide logistics capabilities.Figure SEQ Figure \* ARABIC 1MSOC Deployment Model4. The Full Operational Capability (FOC) set for MARSOC includes deployment of, and operation as, a Marine Special Operations Task Force (MARSOTF). FOC entrains the requirement to provide logistical support to subordinate elements; a capability absent in the current MARSOC TO&E. This leads to the purpose of this study, identification of the requirements for an expeditionary CSS capability.Methodology and FindingsMethodology1. The study team used three operations research methods to identify, refine and analyze the required capabilities.Multi Objective Decision Analysis/Value Focused Thinking (MODA/VFT): a technique developed from decision support theory that allows an organization to:Identify the objective that, if achieved, brings the greatest value to the organization; in other words, the preferred end stateDetermine the functions and tasks the organization must execute to reach the desired objectiveDevelop functions that relate performance on metrics (e.g., miles per gallon, purchase price) to a consistent scale (i.e., utility)Assign weights to the utility functions, as a method to express the organization’s prioritiesGenerate and evaluate alternative solutions to the problem at handWargaming: the team used a multi-cell, one-sided game design. Each cell was presented with an overall scenario broken into a series of moves; their task was to develop solutions that satisfied the CSS requirements identified in each move. Discrete event simulation: a software program that allows a series of mathematical models (e.g., consumption of water, mission duration, combat losses) to interact while managing the forward movement of time. Since many of the underlying math models feature an element of probability the simulation software also manages the creation of random numbers. In a discrete event simulation, time advances in irregular steps; where step-size is based on the time to next scheduled event.2. To implement MODA/VFT process, the study team worked with the Study Project Officer (SPO) to schedule, develop and facilitate a series of Value Model Workshops; please see Appendix B for more details. Sessions were held during the summer of 2008 with participants drawn from the G-4 and G-3 sections of MARSOC. The Study Sponsor (MARSOC G-4) was briefed on the workshop products; with the diagram shown in REF _Ref220165960 \h Figure 2 as the primary focus. The numbers in the various boxes of the value model are the global weights assigned to them during the MODA/VFT process. As this model was used to design and focus the wargame, the 12 most valuable tasks are highlighted. Details of model development are found in Appendix B.Figure SEQ Figure \* ARABIC 2 Value Model used in WargamePlease note that the term ‘Perform FSC’, seen on one of the boxes in the far right column, is misleading. This task deals with the ability to call for air and surface delivered fires; not with the de-confliction of fires.3. Wargaming Division of MCWL led the effort to design and execute the wargame; details are found in Appendix C. During the game, three cells composed of MARSOC personnel were presented with information regarding the game scenario. Each cell independently developed a proposed Course of Action (COA) and briefed it to the Sponsor. The cells were trying to identify ways to overcome gaps in the expeditionary CSS capability of MARSOC; using the prioritized list of gaps developed in the VFT workshops. The primary objective was identification of the structure needed to achieve a desired level of performance (i.e., for those tasks in the value model listed under the heading of ‘Organic to MARSOC CSSE’). REF _Ref220170281 \h Figure 3 is an example of the products each cell developed during the game moves.Figure SEQ Figure \* ARABIC 3 Sample Player Cell Out briefAt the conclusion of the game, the study team was presented with three COA for bridging the gaps in MARSOC expeditionary CSS capabilities. Each COA consisted of a recommended T/O as well as a logistics concept for operations (CONOPS). 4. The study team took the three COA, analyzed them for overlap, compared them to the MARSOTF HQ value model, and then developed a representation of them in simulation software. A commercial product called ExtendSim () provided the necessary tools for simulating CSS operations in the wargame scenario. A screen shot from the tool is shown in REF _Ref220171883 \h Figure 4. Figure SEQ Figure \* ARABIC 4 Screen Shot from ExtendSimExperiments with the simulation were conducted to see the effect CONOPS, levels of staffing (numbers, MOS, rank), distance between supported & supporting units and road networks had on mission performance. In particular, the study team tracked system response in terms of CSS personnel utilization (e.g., how busy they were over the simulation run) and logistic readiness at the supported unit locations. Details on the simulation design, experiment parameters and results can be found in Appendix D.FindingsBased on the results of simulation runs, the study team developed a recommended T/O for the CSS Element (CSSE). This unit provides a robust logistics capability to the MARSOTF HQ while reducing the workload on supported units. The composition of the CSSE, shown in REF _Ref220383453 \h Table 1, consists of four functional groupings:HQ: to provide CSS C2 and 2nd/3rd echelon maintenanceJSOTF Liaison: to expedite intra-theater logistic supportConvoy Operations: to move personnel, supplies and equipment between the MARSOTF HQ location and the supported unitsCompany Support: to act as a logistics C2 node at the company level, as well as providing 2nd echelon maintenance for company equipment. Two notes on the Company Support groupTwo (2) MTVR are provided for moving personnel, equipment and material between the MSOC site and MSOT sitesThe MT Operators (line 42) are cross-trained to operate Material Handling Equipment (MHE)CSSE Personnel at MARSOTF FOB:LineNoBilletMOSRankMarOffMarEnlNavOffNavEnl1OIC0402Maj.122ICXXXXCWO13SNCOIC0491GySgt14MT Maint Chief3529SSgt15MaintMgmnt Clerk0411Cpl16MT Mechs3522Cpl-Sgt27HE Mech1341Cpl18HE Operator1345Pvt-L/Cpl29Electrician1141Cpl210Ord Maint Chf2112SSgt111Armorers2111Cpl-Sgt112Electro Optics Tech2171SSgt213CommElec Maint Chf2862SSgt114Ground Radio Repair284xL/Cpl-Cpl215Ammo Tech2311Cpl-Sgt216Supply Chf3043Sgt117Supply Admin3043Pvt-L/Cpl218Warehouseman3051Pvt-L/Cpl319Contract Specialist3044SSgt120Rigger0451Cpl-Sgt421Embark Specialist0431Pvt-L/Cpl222Generator Mech1142Cpl-Sgt223Engineer Squad Ldr1371Sgt-SSgt124Engineer Team Ldr1371Cpl-Sgt325Combat Engineer13xxPvt-L/Cpl9Subtotal: 24700CJSOTF LIAISON ELEMENTLineNoBilletMOSRankMarOffMarEnlNavOffNavEnl26Logistics Chief04xxSSgt-GySgt 127Supply Chief3xxxSSgt-GySgt128ClerkxxxxCpl-Sgt1Subtotal: 0300CSSE Personnel for Convoy Operations:LineNoBilletMOSRankMarOffMarEnlNavOffNavEnl29OIC0402Lt-Capt130Convoy Leaders353xSSgt331MT Mech3521Cpl-Sgt132MT Operator3531Pvt-L/Cpl933Wrecker Operator3536Cpl-Sgt134Field Radio Operator0621Pvt-L/Cpl335CorpsmanxxxxSN-PO23Subtotal: 11703CSSE Personnel at Company Sites (quantities for two (2) sites shown):LineNoBilletMOSRankMarOffMarEnlNavOffNavEnl36NCOICXXXXSgt237MaintMgmnt Clerk0411Cpl-Sgt238Warehouseman3051Pvt-L/Cpl239Electro Optics Tech2171Cpl-Sgt240Armorer2111Cpl-Sgt241MT Mech3521Pvt-L/Cpl242MT Operator3531Pvt-L/Cpl4Subtotal: 01600Total: 38303Table SEQ Table \* ARABIC 1 Recommended CSSE T/ONotes on Table 1:‘XXXX’ in the MOS column indicates that any logistics MOS is acceptableAt line 30, two of the Marines will lead convoys and one will handle dispatch dutiesAt line 32, the ratio of MT Operators to MTVR is 1.5:1 (i.e., 9 operators and six MTVR)Conclusions and RecommendationsConclusionsTo accomplish its mission, MARSOC requires an expeditionary CSS capability, which it currently lacks. This study developed a recommended T/O for a CSSE that can perform the most important logistic tasks facing the organization. It ensures continued, responsive support to units subordinate to the MARSOTF HQ while minimizing the demand on the JSOTF. The methodology was appropriate for the scale of the problem, the range of possible solutions and the study timeline. Each step in the process is transparent and traceable, allowing external agencies the chance to audit results and understand the numbers behind the study results.RecommendationsThe study team proposes two (2) recommendations for consideration by the Sponsor:Conduct a follow-on study to look at the use of air delivery options, with emphasis on production of air-delivered bundles and sortie allocationUndertake collection of detailed data on equipment performance and maintenance actions; use this information in the MARSOC CSS simulation to refine the recommended T/OINTENTIONALLY LEFT BLANKPurposeThe primary purpose of this study was development of the requirements for an expeditionary CSS capability for MARSOC. Once identified, solutions to satisfy the requirements were developed and analyzed for suitability. At the conclusion of the effort, the study team provided the Sponsor with a recommended T/O.Because the supporting material and final products associated with the MODA/VFT process and the wargame have been delivered to the Sponsor under separate cover, they will not be duplicated in this final report. Also, a run time version of the simulation will be delivered to the Sponsor for subsequent in-house analysis; MARSOC personnel will be able to change parameters and run the model but won’t be able to alter its underlying structure.Following development of the recommended T/O, the study team provided additional support to the G-4 section as they prepared to brief CG MARSOC. This support was primarily in the area of identifying existing sources for the T/O (e.g., looking at units in the MSOSG for the desired MOS/rank mix), mapping from source to sink and identifying T/O shortfalls. These shortfalls will become the subject of a request to the Marine Requirements Oversight Council (MROC) for end-strength growth.Execution of the Study PlanThe study was conducted as described in the executive summary. The study plan, found in Appendix E, was generally executed as written. However, there were three developments that deviated from the plan:Because of the current model for deploying MARSOC units (i.e., the companies rely heavily on the JSOTF for logistic support), there is little information on maintenance actions in Marine Corps systems (e.g., SASSY, MIMMS)An internal staff study on re-organization to create the CSSE was expected to provide alternative COA for study in the wargame. This staff study was cancelled, so the wargame shifted from analyzing the COA to developing the COAThe discrete event simulation was intended to support adjudication during the wargame. Because of the shift in game focus (i.e., from analyzing COA to developing COA), the simulation would have been out of place. Spreadsheet models were developed to provide the player cells with a reasonable logistic demand signalAnalysis Plan: OverviewThe Executive Summary section gives an overview of the study’s methodology, but is light on details of how the methods (MODA, wargame, simulation) are fit together. REF _Ref220387988 \h Figure 5 illustrates the approach used in this study; each step builds on the preceding, with upward movement options decrease, but clarity increases. The penultimate step is the application of military judgment, stepping in where other analysis techniques were inappropriate, inapplicable or unable to provide needed insight.Figure SEQ Figure \* ARABIC 5 Steps in the Analysis PlanMarine Corps Warfighting Publication (MCWP) 4-1, Logistic Operations, is the doctrinal basis for creating a CSS T/O. However, the breadth and depth of functions described in this document requires an organizational structure along the lines of the Combat Logistics Group (CLG). In defining the requirements for an expeditionary CSS capability, MARSOC leadership recognized two things:The MARSOC CSSE focus is primarily on tactical level logistics, and secondarily on the operational level; the CLG model would be much too largeMARSOC elements (both operational and logistical) work in a Joint world, so the ability to plug into an existing JSOTF is criticalThe preceding bullets suggest that the functions of the MARSOC CSSE are a subset of MCWP 4-1; the elements of that subset were defined through the process of building the value model ( REF _Ref220165960 \h Figure 2). The value model gave the study team three things:A prioritized, weighted list of tasks that the CSSE must performAn initial categorization of tasks (i.e., Organic to MARSOC, Sourced by Doctrine, Ad Hoc)A method for scoring the performance of alternatives on the tasksDuring the wargame, player cells concentrated on developing solutions (e.g., structure, equipment, CONOPS) that addressed tasks in descending order. In fact, they were asked to only consider the first twelve (12) tasks in their out briefs. As the game progressed, the cells adjusted their solutions in response to the moves, adding or subtracting elements as determined by their collective military judgment. Post-game analysis revealed a degree of commonality across the cells, indicating that some tasks should move from one category to another. REF _Ref220411747 \h Table 2 shows the migration of tasks from one category to another.Task NumberTaskPre-Wargame CategoryPost-Wargame CategoryComments1.1Order, store, distribute Class I-IXOrganicOrganic1.3Operate Logistic AISOrganicOrganic1.4Provide Level I & II health careOrganicOrganic2.1Maintain & repair equipmentOrganicOrganic4.1AT/FPOrganicDoctrine/policyAddressed with Request For Forces (RFF)4.4Provide CSS C2OrganicOrganic4.5Conduct convoy operationsOrganicOrganic2.2Construct FOBDoctrine/policyOrganic2.3Operate BOSDoctrine/policyDoctrine/policy3.1Move PAXDoctrine/policyOrganicDoes not include movement from APOD to FOB3.2Move Class I-IXDoctrine/policyOrganic4.2FSC (in reality execute calls for fire)OrganicDoctrine/policyAddressed with Request For Forces (RFF)Table SEQ Table \* ARABIC 2 Post-Wargame Analysis: Task MigrationNotes on Table 2:Though the MARSOC CSSE has an intrinsic ability to execute Task 4.1 (AT/FP) and Task 4.2 (FSC), it will supplement this with a RFF tailored to the operational environmentThe JSOTF typically makes extensive use of contracted logistics; the study assumes that JSOTF is responsible for the flow of sustainment from the JSOTF location to the MARSOTF HQ locationTask 2.2 (Construct FOB) is a necessary capability for expeditionary CSSTask 2.3 Operate Base Operations Support (BOS) refers to activities that are typically the responsibility of the Camp CommandantThe study team now had a set of nine (9) logistical tasks organic to the MARSOC CSSE, along with the outlines of an organizational structure (i.e., TO&E) that would have to accomplish them. While the solution space had narrowed, there was still some uncertainty; a combination of steps 3 and 4 (refer to REF _Ref220387988 \h Figure 5) led to the recommended CSSE T/O. Task NumberTaskEvaluation MethodComments1.1Order, store, distribute Class I-IXSimulation/Military Judgment (MJ)Distribution and storage simulated: MJ used for ordering/expediting activities1.3Operate Logistic AISMilitary Judgment1.4Provide Level I & II health careNot EvaluatedNo casualty stream available2.1Maintain & repair equipmentSimulation4.4Provide CSS C2Simulation/Military JudgmentC2 assets for convoy control simulated: MJ used for overall CSS C24.5Conduct convoy operationsSimulation2.2Construct FOBMilitary JudgmentAssisted by spreadsheet model 3.1Move PAXSimulation3.2Move Class I-IXSimulationTable SEQ Table \* ARABIC 3 Methods used to Evaluate CSSE T/O on Required TasksThe methods used to evaluate the CSSE T/O on the nine (9) required tasks are shown in REF _Ref220836528 \h Table 3; results of the evaluation process are discussed on page PAGEREF _Ref220414422 \h 24.Simulation Design and DevelopmentThe decision to use a discrete event simulation for this study was driven by three facts:There was very little experience with service as a MARSOTF HQ, as only a few field trials have occurred and they focused on C2 issuesData on equipment performance, maintenance actions and workload was not available from the normal Marine Corps resources. The Marines of 2nd MSOB generously gave of their time, but the study team was only able to collect anecdotal informationThere was a strong desire on the Sponsor’s part to make the CSSE just big enough; in other words, it should not be sized to meet every possible contingency, but it should be big enough to operate successfully in expeditionary situations.Simulation Development and UtilizationSimulation development began in earnest at the end of the MARSOC wargame, in the latter weeks of October 2008. The simulation design used the same scenario, and the elements to be represented were drawn from the player-developed COA.Baseline Scenario: The simulation is an abstract representation of the game moves, so certain steps were not treated explicitly. In particular, the actions of the engineers in Move 1 (i.e., development of the FOB) were not modeled, as they are deterministic. The simulation runs illustrate activities of the MARSOTF HQ and CSSE from approximately D+15 onward. REF _Ref220223736 \h Figure 6 shows the essential elements of the scenario. During the wargame, player cells used the values shown.Figure SEQ Figure \* ARABIC 6 Baseline ScenarioDuring a simulation run, each team is randomly assigned a mission type. Another random draw determines if the team expends all its ammunition during the mission. A final random variable determines mission duration. REF _Ref220226151 \h Table 4 shows the parameters used in the simulation experiments. Values in columns 1, 3 and 4 come from discussions with MSOC operators, conducted during the wargame. The values in column 2 are drawn from a NPS thesis (Army Special Operations Forces Logistics Planning Aid, LTJG Timothy S. Lanquist, USN, September 1998).Mission TypeP[Assignment]P[Ammo Expenditure]Mission DurationSR_20.2.0961-5 daysDA_60.2.3181-3 daysUW_70.2.3761-3 daysFID_80.4.4351-5 daysTable SEQ Table \* ARABIC 4 Mission ParametersOnce the simulated team completes a mission, the simulation calculates the proportion of time the team’s vehicles operated. The value for this random variable is drawn from a Uniform Real, and one value is drawn independently for each vehicle type. REF _Ref220226672 \h Table 5 shows the parameters used in the simulation. The values in the second column were developed during the wargame, from discussions with MSOC operators. The values in the third column are taken from a study conducted for the Operations Analysis Division of the Marine Corps Combat Development Command (MAGTF Logistics Planning Factors, Decision Engineering, 22 March 2006, Contract Number M00264-01D-0002, Delivery Order 0012). Vehicle Type% of Time in UseConsumption (GPH)GMV~Uniform Real (0, 0.7)6M1114~Uniform Real (0, 0.7)5MRAP~Uniform Real (0, 0.2)16Table SEQ Table \* ARABIC 5 Vehicle ParametersDuring the wargame, demand for Class I (water) was treated as a random variable, defined as (Number of Marines at site)*[(~Uniform (5.8, 9) +~Uniform (0.6, 3.2)]. The first random number represents potable water usage in an arid climate and the second represents non-potable water usage in an arid climate. The simulation used the expected value of each variable, multiplied by the number of personnel present at the site, to calculate water demand.Logistics Concept of Operations: The information in REF _Ref220836656 \h Figure 7 is generally self-explanatory. However, the last bullet is important for understanding the simulation results. During a simulation run, there are four (4) teams created at each site; the teams sit in a queue until assigned a mission. They execute the mission according to the parameters discussed above. Then the team goes into a two (2) day rest/refit period. During this period, their equipment is maintained and the team members only consume Class I items. In reality, the MSOC has only three (3) teams out conducting operations, with the headquarters element remaining at the FOB. So the demand signal for logistic support in the simulation is at least 130% of normal. This was a deliberate design choice, made to compensate for the limited operational data; with an expectation that the model will suggest a robust solution. Figure SEQ Figure \* ARABIC 7 Elements of Logistics CONOPSAssumptions: The assumptions used in the simulation based analysis portion of the study are shown in REF _Ref220423304 \h Figure 8 and REF _Ref220423316 \h Figure 9. Four items bear further discussion:In the simulation, the default vehicle for moving personnel, supplies and equipment is the Medium Tactical Vehicle Replacement (MTVR); the assumed payload is seven (7) tons and the vehicles operate on a road network REF _Ref219882578 \h Figure 1 shows the composition of the enabler package that accompanies each deploying MSOC. Since all of the logistics personnel are drawn from the MSOB, they are under control of the MSOC commander and are not available to assist the CSSE with its tasks. So, the simulation ignores their presence at the MSOC site; an issue relevant to modeling maintenance actionsJP-8 and water move through the system in SIXCON modules, and the transfer of liquids to bladders is treated implicitly. The modules are not tracked and are not considered a constraint on the logistics systemAt the end of each mission, equipment used by the MSOT is inducted into a maintenance cycle. If there is a 2nd echelon maintenance capability at the MSOC site (e.g., there is a 2111 at the site), then all the equipment is given a full LTI. Based on a random draw, some items of equipment will need repair:If the parts are available (another random draw) repairs are effectedIf the parts aren’t available, the equipment sits in a queue until the parts arriveIf 3rd echelon maintenance is required, then the equipment is evacuated to the MARSOTF HQ for repairNote: there are no communications/electronics technicians in the support element at the site, so any equipment needing repair goes directly to the MARSOTF HQFigure SEQ Figure \* ARABIC 8 Assumptions, Part IFigure SEQ Figure \* ARABIC 9 Assumptions, Part II REF _Ref220231151 \h Table 6 shows the type and quantity of equipment the simulation created at the end of each MSOT mission; an extract from the Hotel Company EDL. The equipment is routed to the proper queue for LTI/CM based on the TAMCN code. Note that the table reflects communications equipment; even though there are no communication technicians at the site, the simulation needs these values to evaluate if 2nd/3rd echelon maintenance is required.TAMCNTAMCNNOMENCLATUREQty TmEquip typeAA1260NAVIGATION SET,SATE DAGR AN/PSN-1329Comm otherAA8010TELEPHONE,SECURE UN STE OFFIC-4421Comm otherAA8025ELECTRICAL TRANSFER TSEC/KYK-132Comm otherAA8023TRANSFER UNIT,CRYPT AN/CYZ-10V33Comm otherAA0874IOW AN/UYQ-88(V)2 intel. computer1ComputerAA0904DIGITAL IMAGING SET (AN/PSQ-13)1ComputerAA2546LAPTOP,ULTRA PORT T2ComputerAA9003BLUE FORCE TRACKING2ComputerAA9300COMPUTER SYSTEM,DIG2ComputerAA0918RADIO SET, satellite AN/PSC-51RadioAA0067AN/VRC-111 (AN/MRC-148)4RadioAA0075Radio set, vehicle, HF, AC/VRC-1044RadioAA2079RADIO SET AN/PRC-119F1RadioAA2042RADIO,HF AN/PRC-1503RadioAA2068RADIO SET AN/PRC-117F4RadioAA2044MBITR MARITIME VERS AN/PRC-14829RadioDD0022TRUCK,UTILITY (D1152 based GMV)4VehicleDTRUCK,UTILITY (M114)3DMRAP1EE0994MACHINE GUN,GRENADE (Mk-19)0WeaponEE1760SHOTGUN,12 GAGE,RIO2WeaponEE0994MACHINE GUN, GRENADE (Mk-19)1WeaponEE0311RIFLE,7.62 MILLIMET2WeaponEE0890LAUNCHER,GRENADE,40mm, M792WeaponEE1761SHOTGUN,COMBAT, AUTOMATIC2WeaponEE0960MACHINE GUN,5.56 MI (SAW)3WeaponEE0980MACHINE GUN, .50 cal M24WeaponEE0892LAUNCHER,GRENADE, 40mm, M2035WeaponEE0989MACHINE GUN,7.62 MI (M240)7WeaponEE0190CARBINE,5.56 MILLIM19WeaponEE1460RIFLE,SNIPER M40A32WeaponEE1475RIFLE,SEMI-AUT,.50C SASR2WeaponOA2560TLDHS,AN/PSQ-19 tgt designator1OpticOE0006ILLUMINATOR,INFRARE2OpticOE1978VIEWER,NIGHT VISION (thermal, long range)2OpticOE1048LASER RANGE FINDER3OpticOE1162AV/PVS-17, 5.2X3OpticOE1154NIGHT VISION DEVICE AN/PVS-1411OpticOE1162NIGHT SIGHT VISION AN/PVS-17B12OpticOE0017SIGHT,BORE,OPTICAL19OpticOE1798ILLUMINATOR,INFRARE AN/PEQ-2A19OpticOEL001AIM POINT COM 219OpticOE1030LASER TARGET DESIG1OpticOE1976SIGHT,THERMAL (heavy HTWS) AN/PAS13D4OpticTable SEQ Table \* ARABIC 6 MSOT EDL in SimulationSimulation Output: ExtendSim can produce a variety of charts, tables and graphs, depending on the needs of the study. During the simulation runs, the study team tracked two (2) key metrics. One dealt with the utilization rate of CSSE personnel (e.g., drivers, maintainers) and the other dealt with the logistic readiness level at each site. This latter metric is displayed in charts similar to REF _Ref220423381 \h Figure 10. Unfortunately, due to file compression, it is difficult to read numbers from the figures in this section. REF _Ref220837555 \h Appendix D. Simulation Results, contains graphs that are easier to read. In these charts, the following conventions apply:The ammunition on hand, expressed in Days of Supply (DOS), is shown by the green trace, and uses the scale on the left side of the graphThe JP-8 on hand, expressed in gallons, is shown by the blue trace, and uses the scale on the right side of the graphThe water on hand, expressed in gallons, is shown by the red trace, and uses the scale on the right side of the graphThe horizontal axis measures time, expressed in daysOn Day 1, each MSOC site has:20 DOS of ammunition10K gallons of JP-810K gallons of waterFigure SEQ Figure \* ARABIC 10 Understanding Output from ExtendSimExample Results: All of the parameters discussed to this point define the context for running simulation-based experiments. Some of the parameters are deterministic (e.g., vehicle mix, fuel consumption planning factor) while others are stochastic (e.g., mission duration). Attention now turns to the experimental variables; these are factors the study team controlled in order to assess the response of the CSSE. Post game analysis led the study team to adopt the logistics CONOPS reflected in the recommended T/O for the CSSE; that is, a logistics organization of four elements, with one dedicated to sustaining the force (i.e., conducting convoy operations), one dedicated to maintaining the force (i.e., the support elements at each MSOC site), one dedicated to liaison with higher headquarters and one dedicated to CSS C2. The simulation represents the sustaining and maintaining tasks carried out by two elements of the CSSE. (NOTE: maintenance actions at the MARSOTF HQ (i.e., 2nd and 3rd echelon) were included in the simulation). The study team used three experimental variables:The number of trucks and drivers available for sustainment operationsThe number of maintainers at the MSOC siteThe type of convoy dispatch used; either a pull signal from the MSOC site or a push decision from the MARSOTF HQIn analyzing the results of simulation runs, the study team considered four metrics:Supply Readiness: the objective was to minimize the number of days the MSOC site fell below:10 DOS of ammunition5K gallons of JP-85K gallons of waterMaterial Readiness: the goal was to ensure that the average wait in any of the maintenance queues did not exceed two (2) days, as this was the rest/refit window for the MSOT before starting the next missionEquipment Utilization: the goal was to keep vehicle use below 40%, with a utilization rate of 33% being the objectivePersonnel Utilization: the goal was to keep personnel use below 40%, with a utilization rate of 33% being the objective. Note: by setting an objective of 33%, the study team could reasonable assume that the Marine would have enough time to eat, sleep and perform a range of extra duties (e.g., unloading supplies, standing guard, doing laundry) without having to account explicitly for each hour REF _Ref220423708 \h Figure 11 shows the results on one simulation run, representing 90 days of operations. In this example, there are six (6) MTVR available to support the two (2) MSOC sites, and re-supply convoys are dispatched in response to requests from the MSOC. The variation in on-hand water (the red trace) is a little more regular, because it is decremented equally each day. On-hand ammunition and JP-8 show a less regular pattern, as they are both subject to random consumption. While the on-hand levels for water and ammunition never reach the minimum, there are several days (vicinity of day 75-85) where the on-hand level of JP-8 dips below 5K gallons.Figure SEQ Figure \* ARABIC 11 Output for 90 Day Simulation Run, Log-PullIn contrast to the first example, the trace of supply readiness in REF _Ref220423726 \h Figure 12 shows much less variation in the on-hand levels of water and JP-8, with only one case (vicinity of Day 22) where JP-8 levels approached the minimum acceptable. In this simulation run, supply convoys are dispatched on a regular basis, while also responding to re-supply requests from the MSOC sites (triggered when water/fuel reach 7K gallons or ammunition reaches 12 DOS). In this case the supply readiness metric is at an acceptable level and, compared to Figure 11, the number of convoys is reduced.Figure SEQ Figure \* ARABIC 12 Output for 90 Days, Push & Pull Key Findings and Robustness: The simulation helped the study team identify bottlenecks and try alternate configurations of the CSSE. Because the experiment plan used just three variables, and the sustainment operations presented the noisiest demand signal, the study team worked first to identify the equipment and personnel needed to support the MSOC sites. From this point, it was possible to build in the needed CSS structure to support sustainment operations. There were some constraints on the size of the support element at the MSOC site (e.g., minimal logistics footprint at the sites so the benefits for the commander outweigh the cost of additional security measures). In this case, the study team reverse engineered the equipment failure rates and time to repair to meet the material readiness and personnel utilization metrics. In essence the simulation represents the worst case capability of the maintainers; if equipment fails at a higher rate, or repairs take longer than modeled, maintainers will work unacceptably long hours. This is the basis for recommending follow-on study of the maintenance process as it is actually practiced.Figure SEQ Figure \* ARABIC 13 Key Findings for Simulation RunsThe method for calculating fuel consumption in the simulation was also used in the wargame, and the players saw the figures (i.e., the demand signal) at several points in the game. However, the study team cannot state for certain that they are a reasonable model of reality. Further study of this aspect of logistics operations is needed, with an emphasis on collecting real world data for comparison.While the simulation treated logistics operations as being in a ‘steady-state’, player cells in the wargame considered other critical phases of the operation. In their out briefs, teams recommended varying numbers of mobility assets to move the MARSOTF HQ and MSOC to their operating bases. The study team recognizes this, and does not claim that the recommended T/E of six (6) MTVR could move the MARSOTF from the APOD to the FOB in a timely manner. The TO&E of the convoy operations element is designed to sustain, not mobilize. Because the recommended TO&E for the CSSE satisfied the four metrics used in the simulation, and the demand signal is larger than normally seen ( REF _Ref220423786 \h Figure 14 applies), it appears that MARSOC will have a robust expeditionary CSS capability.Figure SEQ Figure \* ARABIC 14 RobustnessExcursions and Recommendations: Due to the limited time allowed for this study, it was not possible to conduct a range of excursions. Some candidate excursions are shown in REF _Ref220423809 \h Figure 15. With the value model in place, and the discrete event simulation built, the study team can respond rapidly to requests from the Sponsor. Further, when the run-time version of the model is delivered, MARSOC personnel will be able to conduct their own ‘what-if’ analysis.Figure SEQ Figure \* ARABIC 15 Possible ExcursionsFindingsScoring the CSSE T/OThe recommended T/O (please refer to REF _Ref220383453 \h Table 1) for the CSSE consists of four elements:HQ: to provide CSS C2 and 2nd/3rd echelon maintenanceJSOTF Liaison: to expedite intra-theater logistic supportConvoy Operations: to move personnel, supplies and equipment between the MARSOTF HQ location and the supported unitsCompany Support: to act as a logistics C2 node at the company level, as well as providing 2nd echelon maintenance for company equipmentUsing the scoring functions from the MODA/VFT process (refer to Appendix B, Value Model Workshop, starting on page PAGEREF _Ref220414830 \h 32), the study team calculated the value accruing to MARSOC. These results are shown below.Task NumberTaskMeasureScoreUtilityWeightValue1.1Order, store, distribute Class I-IXP[CSSE Successfully Performs Task]Likely, by MJ0.750.080.061.3Operate Logistic AISP[CSSE Successfully Performs Task]Likely, by MJ0.750.090.071.4Provide Level I & II health care%Time Corpsmen BusyNot Evaluated0.00.090.02.1Maintain & repair equipmentAverage Daily R-Rating90%, by Simulation0.800.080.064.4Provide CSS C2P[CSSE Successfully Performs Task]Likely, by MJ0.750.080.064.5Conduct convoy operationsP[CSSE Successfully Performs Task]Likely, by MJ0.750.090.072.2Construct FOBDays to Construct5 Days, by Spreadsheet0.800.050.043.1Move PAX%Time MTVR Operators Busy40%, by Simulation0.50.070.043.2Move Class I-IX%Time MTVR Operators Busy40%, by Simulation0.50.070.04Total Value:0.43Table SEQ Table \* ARABIC 7 Scoring the CSSE T/ONotes on Table 7:For Tasks 3.1 and 3.2, the simulation used 12 drivers to operate the 6 MTVR, MJ reduced the number in the T/O to 9, leading to lower utility from these tasksThe scores for Tasks 2.1 and 2.2 are conservative estimates, assuming marginal conditions for both tasksRounding errors in Totals, due to use of two (2) decimal places in numbersTheoretically, if the CSSE T/O was without flaw, risk or shortfall, each Measure would achieve the maximum Score, and return a Utility of 1. As these nine (9) tasks carry 70% of the available weight (as shown in the Value Model, REF _Ref220165960 \h Figure 2), the maximum Total Value the CSSE T/O could provide is 0.7. As the actual Total Value is 0.43, this version of the CSSE T/O gives MARSOC about 61% of the theoretical Total Value.RecommendationsThe study team recommends that MARSOC undertake two follow-on studies; because they are intimately related to the current effort, they should begin as soon as possible.Air Delivery OptionOAD is currently conducting a study to see if it is feasible to support widely dispersed infantry units through aerial delivery. The scenario can be quickly modified to address MARSOC interests and the analytical tools will be in place to execute the study quickly. There are three factors that may be of interest to MARSOC:Throughput at the Rigging Shed: How many bundles of size X can Y riggers prepare in Z hours? Sortie Allocation: How many are needed to sustain the MSOC sites and how many would be available?Supported Unit Trade Space: Is precision delivery a critical enabling capability? Do the supported units need MHE at the drop zone? How does the air delivery option affect the security posture at the MSOC site?Maintenance ModelingAs noted at various points in Section 3, the modeling of maintenance activities at the MSOC sites lacks fidelity. In fact, the associated parameters reflect a worst case scenario for the maintainers; if the equipment fails more frequently, if repairs take longer, or if parts are harder to get, then the whole maintenance effort could grind to a halt. OAD recommends a study to look at these principle factors:A task analysis to understand the repair process for currently fielded equipment. What repairs are most commonly done? How long do they take? Does a particular repair item limit the repair process?Collect and analyze data from current MARSOC deployments, to complement and refine the data available in SASSY/MIMMS/MERITCalculate the total footprint of the maintenance personnel. What sets, kits and chests do they need? Do more tools mean better readiness? What should be the composition of the Class IX block? Quantity, weight, volume, cost to carryAppendix A. Acronyms and DefinitionsThe material in this section is provided to familiarize the reader with terms used throughout this document. Appendix B. Value Model WorkshopThis section contains slides used to brief the Sponsor on the final results of the MODA/VFT workshops. They provide dates for when the workshops were held, and the related work products. As the slides summarize work to date, they’re unable to give the detailed description of how the workshops were conducted. If there are questions about the supporting spreadsheets (pages 34-36, and 58-60), please contact the study lead at OAD, MCCDC.A discussion of the MODA/VFT methodology can be found in chapter 19 of Methods for Conducting Military Operational Analysis, Loerch, A.G. and Rainey, L.B. editors, Military Operations Research Society, 2007. The relevant chapter, Value-Focused Thinking, was written by Gregory S. Parnell.Appendix C. Wargame The following slides were used to brief the player cells on the MARSOC 08 wargame. At the end of each turn, cell leaders presented their COA recommendations to the Sponsor. All game-related materials, along with a quick look analysis report, were forwarded to MARSOC under separate cover.Appendix D. Simulation ResultsThe study team built a simulation of the CSSE that emerged from the wargame, as modified by military decision makers. Once the simulation logic was in place it was possible to input a range of values for the experiment variables and observe the system’s response. The analysis proceeded in three steps:Step 1: Vary the number of MTVR availableStep 2: Vary the logistics C2 and the number of MTVR availableStep 3: Conduct multi-run analysis on the most promising configuration to develop a confidence interval for system responseAs noted in the main body of the report, the number of maintainers at the MSOC site was constrained by expert judgment (i.e., don’t let the cost of protecting the support element outweigh the benefit of their presence). So there was not much room for experimentation on this aspect of the CSSE T/O. On average:Motor Transport Mechanics were busy ~29% of the timeArmorers were busy ~42% of the timeOptics Technicians were busy ~39% of the timeBecause the figures above are sensitive to assumptions about MTBF and MTTR, the study team does not make any strong claims regarding the veracity of the results. For this reason, a follow-on study of this issue is recommended.Step 1: Vary Available MTVR: Starting with fourteen (14) MTVR and a simulation run of 90 days; results for supply readiness at MSOC A are shown below.114300228600000 Figure SEQ Figure \* ARABIC 16 Logistics Pull, 14 Trucks, and 90 DaysThe red line in the graph indicates a value of ‘15’ on the left scale (measuring DOS of ammunition) and ‘5000’ on the right scale (measuring JP-8 (blue trace) and water (red trace)). As can be seen, there are several periods where the MSOC site has less than the minimum stock of JP-8. Pulling information from a dialog box in the simulation shows that an individual MTVR was used 13.71% of the time. This indicates that 14 is an excessive quantity of trucks. NOTE: in analyzing results, the study team looked at conditions at both sites. However, as the two sites are identical in operation, only one graph is shown for clarity.Using the same logistics C2 model (i.e., sustainment is only sent when the MSOC pulls from the CSSE) and ten (10) trucks, produces the response shown in REF _Ref220262839 \h Figure 17. Since this figure and the preceding one show just one run, there is little value in comparing them to each other. In the case of REF _Ref220262839 \h Figure 17, MTVR utilization rose to 18.82%228600240030000Figure SEQ Figure \* ARABIC 17 Logistics Pull, 10 Trucks, and 90 DaysWhen just six (6) MTVR are available, their average utilization is 30.95% and the system responds as shown in REF _Ref220263148 \h Figure 18. As in the previous figures, the red line is added for clarity, but there is no analytical basis for comparing the three cases. However, when there are six (6) MTVR in the CSSE, the utilization rate moves closer to the desired level.342900251460000Figure SEQ Figure \* ARABIC 18 Logistics Pull, 6 Trucks, and 90 DaysStep 2 Vary the Logistics C2 and Vary the MTVR: The scenario is run again, starting with fourteen (14) MTVR available to the CSSE. But now sustainment convoys are pushed to the MSOC sites on a regular schedule (NOTE: only fuel and water are pushed, ammo is still delivered on demand); and of course, the CSSE must have the ability to respond to re-supply requests from the sites. There is a large change in system response, and the red line in REF _Ref220263824 \h Figure 19 now indicates ’12.5’ and ‘5000’ on the left and right scales, respectively.228600331470000Figure SEQ Figure \* ARABIC 19 Logistics Push and Pull, 14 Trucks 90 DaysWhile a direct comparison to preceding figures remains invalid, the study team noted that the supply states for JP-8 and water seemed to vary less, and it is apparent that minimum levels are less frequently violated. With fourteen (14) MTVR available, the average truck is used 15.41% of the time.Reducing the number of trucks to ten (10) increases their utilization rate to 21.97% and results in the supply readiness shown in REF _Ref220264270 \h Figure 20.228600342900000Figure SEQ Figure \* ARABIC 20 Logistics Push and Pull, 10 Trucks, 90 DaysWhen the number of MTVR is reduced to six (6), the utilization rate rises to 32.79%. The supply situation shown in REF _Ref220264478 \h Figure 21 appears generally acceptable, though there are several days where the available fuel drops below 5K gallons. At this point, the study team determined that a reasonable stopping point had been reached; six (6) MTVR in the CSSE and a push/pull C2 model became the starting point to develop confidence intervals.228600320040000Figure SEQ Figure \* ARABIC 21 Logistics Push and Pull, 6 Trucks 90 DaysStep 3 Confidence Intervals: To develop the confidence intervals, the 30 replications of the simulation were run, each for 90 days. The resulting statistics are shown in REF _Ref220265443 \h Table 8. Supply CategoryMean-2*StdDevMeanMean +2*StdDevFuel (gallons)5162782010477Water (gallons)648082329984Ammo (DOS)141720 Table SEQ Table \* ARABIC 8 Confidence Interval for Supply ReadinessThe interpretation of the numbers is straightforward; for the given scenario, using six (6) MTVR and push/pull logistics C2, the CSSE can ensure that 95% of the time:The MSOC site will have at least 5,162 gallons of JP-8 on hand and that on average, there will be 7,820 gallons availableThe MSOC site will have at least 6,480 gallons of water on hand and that on average, there will be 8,232 gallons availableThe MSOC site will have at least 14 DOS of ammunition on hand and that on average, there will be 17 DOS availableBased on these statistics, the study team recommends the use of push/pull logistics C2 and the presence of six (6) MTVR in the CSSE. From this foundation, and using military subject matter experts, the remaining portions of the CSSE T/O were built. The final product can be seen at REF _Ref220383453 \h Table 1. Appendix E. Study PlanStudy Plan for the Analysis of Marine Corps Forces Special Operations Command Combat Service Support (MARSOC CSS)1. BackgroundBy assuming existing structure from 1st and 2nd Force Reconnaissance Companies, Marine Special Operations Command (MARSOC) initiated operational deployments of company-sized elements a little more than one year after establishment of the Command. In addition, deployments by the Foreign Military Training Unit (FMTU), re-designated as the Marine Special Operations Advisory Group (MSOAG) have continued and are increasing in terms of locations, duration and frequency. While supporting an ever expanding range of deployments, establishing the structure to recruit, screen, assess, select and train operators, MARSOC also confronted the challenge of developing an appropriate logistic capability. In the near term, this capability must support deployments of 14 to 54 operators, ranging from six weeks to six months, and respecting a 1:2 dwell time. In the longer term, in addition to the expeditionary logistics capability, MARSOC must provide small, tailored, mission-focused detachments, for limited deployment windows. An example might be a team of engineers to repair a village’s generator system, in the operating area of a MSOAG element.Though all SOF-specific equipment is supported by the Special Operations Forces Support Activity (SOFSA); the Marine Corps is required to support the forces and equipment it provides to Special Operations Command (SOCCOM).In less than two years, MARSOC will reach Fully Mission Capable (FMC) status. At that point, the Command must be able to support deployments of battalion-sized elements, organized to function as a Special Operations Task Force Headquarters (SOTF HQ). During the transition period from IOC to FOC, much of the operational effort will be focused on support to CENTCOM in OIF and OEF. After 2010, the proportion of deployments to austere theaters will increase; significantly increasing the demands on the Command’s organic logistics capability.2. ObjectiveAnswering the following questions is the study’s primary objective:What level of expeditionary logistics capability provides the greatest benefit, across the widest range of operational environments?Are there opportunities for MARSOC elements to leverage the logistical capabilities of deployed Marine forces, such as a MEU?If the capabilities (logistic and/or operational) of MARSOC elements are used in combination with those of expeditionary Marine force, what is the impact on the CJSOTF?Answers to the above questions support MARSOC submissions to the MROC, due in December of 2008. Developing these answers depends on several sub-objectives: Review of existing policy and doctrine governing logistical support provided to MARSOC by the Marine Corps, both the Operating Forces and the Supporting Establishment. Assessment of concepts for supporting MARSOC operations, considering their operational effectiveness and estimating their impact on expeditionary Marine forces. Analysis of alternative TO/E in terms of their capability to provide expeditionary logistics to deployed MARSOC elements. 2.1 Study Directions The study must consider the likely geographic dispersion of TSC missions, the challenges of synchronizing MARSOC deployments with the deployment cycle for expeditionary Marine forces, the execution of short-duration deployments by team-sized elements and the need for MARSOC logistics to act as a Joint Special Operations Task Force (JSOTF) enhancer. The study should consider operations in the 2010-2020 timeframe.Marine Corps participants in this study should include MARSOC, Marine Forces Command (MARFORCOM), Marine Forces Pacific (MARFORPAC,) Headquarters Marine Corps Plans, Policies and Operations (HQMC (PP&O)), Marine Corps Combat Development Command (MCCDC), the Marine Corps Warfighting Lab (MCWL) and Training and Education Command (TECOM). 2.2 ConstraintsSpecific direction by the study sponsor guides the efforts of the study team. This set of directions includes:Deployment tempo based on the FY10 Training and Exercise Employment Plan (TEEP) Operating environment: NE Asia, SW Asia and AfricaSize of deploying units: small teams (e.g., 14 Marines and Sailors) to MSOBLogistical requirements for deployed elements are based on:Marine Special Operations Company (MSOC) conducting Direct Action (DA) and Special Reconnaissance (SR) operations under the operating concept of Foreign Internal Defense (FID)Marine Special Operations Advisory Groups (MSOAG) Teams conducting FID operationsTheater Special Operations Commander (TSOC) directed support to other SOCCOM elementsForces available to generate required logistical capability include:Existing MARSOC structureProposed MARSOC structureMEU(SOC)Expeditionary Strike Group (ESG)JSOTFOther US agenciesHost Nation Support (HNS)Goods and services purchased from the local economyMarine Corps logistical functions are effected by on-going LOGMOD effortsMARSOC capable of 1st , 2nd and limited 3rd echelon maintenance for Marine Corps equipmentMEU(SOC) capable of 1st, 2nd and limited 3rd echelon maintenance for Marine Corps equipmentAnalysis of logistical support for Distributed Operations (DO) is applicable to MARSOF operations 3. Limitations and Assumptions3.1 Limitations The resources of the study team (e.g., time, tools, personnel), as well as the availability of data, place limits on the contents of the final report. To ensure a clear understanding with the sponsor, the following limitations on the study team’s capabilities are presented:Due to the relatively small number of MARSOC deployments to austere theaters, limited operational data existsDue to the compressed schedule for draft results, analysis will require the use of some planning factors, ratios, and SME input to supplement detailed process analysis. 3.2 AssumptionsTo fill information gaps (e.g., what operations MARSOC elements will execute in the out-years), the study team developed a set of assumptions. They are numbered to facilitate discussion during the first phase of the study effort. At the end of the study, some assumptions will become irrelevant, some will be replaced with actual information and some will be validated.Current operations (e.g., OIF, OEF) continue in their current form for the first two years of the study period. During the remainder of the study period, the operations will be balanced among FID, DA and SR LOGMOD will be fully implemented on schedule; the brief at pertains.TSOC Request For Forces (RFF) in the latter portion of the study period may include logistical support, sourced from MARSOC, for SOCCOM elements.The deployed MSOC has no organic aviation capability; transport, assault support and CAS are provided by CJSOTF or other TSOC assetsThe deployed MARSOC elements always tie into the CJSOTF for operational logisticsIf the deployed MARSOC element is serving as a SOTF HQ, it will have to provide life support services at the FOBIf the deployed MARSOC element moves into an austere area of operations, occupying a basic FOB, it will improve the FOB as indicated by METT-T4. Methodology and Tasks 4.1 Methodology The study uses three analysis techniques to support the MARSOC submission to the MROC:Decision analysis: Value model workshop, involving personnel from MARSOC G-3, G-4 and MSC, to do three things:Identify the desired capability for expeditionary logisticsSpecify the associated functions and tasksDetermine how to measure the capabilityWargamingUse of a seminar wargame, involving MARSOC, SOCOM and SOCENT personnel to identify solutions for creating the expeditionary logistics capability Simulation Evaluation of alternatives through the use of stochastic discrete event simulation Design of experiment (DOE) and sensitivity analysis to assess performance of recommended alternative across a range of operational settings Tasks To employ these techniques, the study team carries out the following series of tasks.4.2.1. Task 1 - Literature review of all relevant material relating to the logistic and operational capabilities of MARSOC and expeditionary Marine forces, as well as current logistics modernization initiatives. 4.2.2. Task 2 – Support development of the MARSOC value model through a series of internal workshops; OAD study team will facilitate discussions, record minutes, track action items and publish decisions. 4.2.3. Task 3 – Present the MARSOC value model to MARSOC personnel. The OAD study team facilitates the workshop to develop feasible alternatives that address the analytical questions outlined above. 4.2.4. Task 4 – Design a seminar wargame to assess issues identified in the alternatives development workshop. Identify and invite participants, distribute game materials and coordinate support for game execution.4.2.5. Task 5 – Support execution of the wargame, capture key observations and lessons learned. Participate in quick look analysis and contribute to the final report.Task 6 – Using a stochastic simulation of a deployed MSOC, analyze and score alternatives.Task 7 – Combine the results of the wargame and simulation runs to identify that alternative with best-value for MARSOC. Brief the Study Advisory Committee (SAC) on the combined output, solicit input and incorporate comments as appropriate.4.2.8. Task 8 – Prepare and deliver final report to the Study Sponsor with any information needed to finalize the Study Completion Letter (SCL). Be prepared to support the review process of the brief.5. PerformanceGeneral The study will be performed per the provisions of MCO 3902.1D, Marine Corps Studies System (MCSS). Additionally, this study may become a classified study or involve the collection and analysis of classified information. In this case, all personnel involved in this study will be required to have a current secret clearance. Time of Performance The study will be completed NLT 25 November 2008. In Progress Reviews (IPR) will include a brief of study progress to date followed by a working session to address the subsequent task. The following is the proposed timeline for the tasks: Task / DeliverableJunJulAugSepOctNovDecTask 1: Literature ReviewTask 2: Value Model WorkshopsTask 3: Alternatives WorkshopTask 4: Wargame DesignTask 5: Wargame ExecutionTask 6: Simulation RunsTask 7: Analyze ResultsTask 8: Prepare Final ReportOn-going SupportIPR 1XIPR 2 (brief preliminary results)X Brief Draft FinalX Deliverables General Deliverables will be provided according to the following schedules. All reports will be written unless otherwise stated.Deliverables ItemContentFormatDue DateIPR #1 Brief Tasks 1 - 3 Annotated MS Power Point file29 Sep 08IPR #2 BriefTasks 4 - 7Annotated MS Power Point file5 Nov 08Brief Draft FinalTask 8Annotated MS Power Point file14 Nov 08Final ReportTask 8MS Word file15 Dec 08Travel Trip #TravelersDurationFrom - ToPurpose1228-31 Jul 08Quantico toCamp LejeuneValue Model Workshops2225-27 Aug 08Quantico to Camp LejeuneAlternatives Workshop3229-30 Sep 08Quantico to Camp LejeuneBrief IPR #1425-6 Nov 08Quantico to Camp LejeuneBrief IPR #25213-14 Nov 08Quantico to Camp LejeuneBrief Draft FinalAdditional travel associated with Task 5, Wargame Execution, may be required, depending on the location of the game.Local Travel Local travel within the Washington Metropolitan area is necessary.ReferencesReferences: The study performer shall review the following references for applicability to completing this study. The study sponsor will provide these documents upon commencement of the study.Results of Emerald Express 06.Results of Expeditionary Warfare 04, especially Core Objectives 2 and A after action report on ‘Det One’CNA report on relation between deployed MARSOC elements and MEU(SOC)MARSOC Campaign PlanMARSOF TEEPArmy study on logistics reorganization for ARSOFAny SOCOM or DoD policy documents, directives, MOUs, or MOAs applicable to CSS support of MARSOCCoordinating InstructionsStudy Sponsor Col Pete Warker, AC/S G-4, MARSOC.Study Advisory CommitteeStudy Project Officer:Maj Charles M. Long, USMC G-4 Operations OfficerBuilding: H-1Floor: 1GSCamp Lejeune, NC 28542Phone: 910-451-3643Email: charles.long@usmc.mil Study Lead:Matt AylwardOAD, MCCDC3300 Russell Road Quantico, VA 22134Phone: 703-784-5989Email: matthew.aylward@usmc.milStudy Advisory Committee Membership:HQMC: DC P&RDC I&LDC M&RADC PP&OMCCDC:MAGTF Integration Division(C 11)Logistics Integration Division(C 13)C2 Integration Division(C 16)Total Force Structure Div(C 18)Training & Education Command(C 46)Marine Corps Warfighting Lab(C 52)MarCorLogCom:Operations Division Marine Forces:MarForPac: Attn: G-4 MarForCom: Attn: G-4MarCent:Attn: G-4MarSoc: Attn: G-3, G-4 SOCOM J-4 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download