TE-3 Rules and Work-Around FY 23.pdf

Contents UNCLASSIFIED 1

Contents UNCLASSIFIED 2

This Page Intentionally Blank

Contents UNCLASSIFIED 4

TABLE OF CONTENTS

SUMMARY OF CHANGES

CHAPTER 1 – INTRODUCTION & OVERVIEW

A. Purpose

B. WFX Overview:

C. Exercise Control Group (ECG):

Figure 1. Exercise Control Group Schematic

D. Simulation Control

E. Simulation Outages

F. Changes and Revisions

G. Violations

H. Approval

CHAPTER 2 – RULES

A. Purpose

B. Simulation Center (SIMCTR) Rules

C. General Rules

D. Operating Rules

E. Unit Icon Assignment Rules

Figure 3. Unit Icon Assignment Rules

F. Automated Unit (AU) Echelon and Management Rules

G. Decoy Operations

H. Functional Area Work Cell Rules

1. Intelligence

2. Maneuver

3. Protection

4. Fires

5. Rotary Wing (RW) Aviation

6. Fixed-Wing (FW) Aviation

7. CBRNE

8. Sustainment

9. SOF/SPF

10. EXCON

I. WARSIM Database Management

Contents UNCLASSIFIED 5

1. Parametric Database Changes

CHAPTER 3 – WORKAROUNDS

A. Purpose

B. General

1. MANEUVER

1.1 Low Strength / Destroyed Automated Units (AUs)

1.2 BLUFOR Command Post Overran or Destroyed

1.3 Amphibious Landings

1.4 Airlift, Air Assault, Airdrop, and/or Airborne Operations

1.5 Division and Above C2 Degradation

Figure 1.5-1 Division and above C2 Degradation Matrix

1.6 Deliberate Attack on BLUFOR Command Posts

Figure 1.6-1 Process: Deliberate Attack on BLUFOR Command Post

2. FIRE SUPPORT

3. PROTECTION

3.1 Persistent Chemical Attack and Operational Decontamination Procedures

Figure 3.1-1 Unit Operational Decontamination Times for Company-sized Units

Figure 3.1-2 Unit Operational Decontamination Worksheet

3.2 Assault Boat Crossing of a Wet Gap Operation

3.3 Heavy Assault Rafting

3.4 Counter-Rocket, Artillery, Mortar Capability

Results: Casualties are adjudicated

4. SUSTAINMENT

4.1 MCTP WFX Combat Power Adjustment (CPA) Battle Drill

4.2 Cannibalization ............................................................................................. Error! Bookmark not defined.

5. ROTARY WING AVIATION

5.1 Downed Aircraft/UAS/Aviation Equipment Loss

5.2 Air-launched SPIKE-NLOS (or other future air-launched NLOS weapons)

6. FIXED WING AVIATION

6.1 Special Munitions & Long-range Direct Fire Precision/Near-Precision-Guided Air-to-Ground Weapon Systems

6.2 Naval Aircraft Carrier/Marine Air Operations

6.3 Strike Reconnaissance and Coordination (SCAR) Missions

Contents UNCLASSIFIED 6

7. CA/PSYOP/SF/SPF

7.1 Civil Military Operations

7.2 Psychological Operations (PSYOP)

Figure 7.2-1 PSYOP Speaker and Leaflet Attrition Rates

Figure 7.2-2 PSYOP Attrition Matrix

Figure 7.2-3 PSYOP Attrition Worksheet

7-3 Special Forces (SF) Special Recon (SR) Missions

7.4 Special Forces Ambush

7.5 SF/SPF Detonate Target

7.6 Special Forces (SF) and SPF Special Recon Hide

7.7 SOF Resupply Workaround

8. INTELLIGENCE, ISR

8.1 MUSE UAS Shoot Down

8.2 Ground Move a UAS Platoon

8.3 GRAY EAGLE Capabilities for Simultaneous/Continuous Missions

Figure 8.3-1 Gray Eagle OPTEMPO

8.4 Grey Eagle transfer of control from CAB cell to MUSE cell

9. CONTEMPORARY OPERATIONAL ENVIRONMENT (COE)

9.1 OPFOR Civilians

9.2 OPFOR UAS Precision Attack

Figure 9.2-1 OPFOR Attack UAS Workaround Sheet

9.3 Decoy Operations

Figure 9.3-1 Decoy Employment Times

9.4 Enemy Prisoners of War Workaround

9.5 Underground Facilities (UGF) (HARTS) (TUF)

Figure 9.5-1 UGF Egress Time in Minutes

9.6 Electronic Warfare Effects (Air Platform EW Effect)

Figure 9.6-1 Electronic Warfare Effects

9.7 Hide/Shelter in Urban Areas

10. SENIOR CONTROL WORKAROUNDS

10.1 TBM Launch Preparation Workaround SS-1 type TBM (including NODONG)

11. EXERCISE CONTROL (EXCON)

11.1 OPFOR HIMAD Workaround

Contents UNCLASSIFIED 7

12. INFORMATION ADVANTAGE DIVISION

12.IAD1. Non-lethal Effects Adjudication Lifecycle Process

Figure 12.IAD1-1 Non-lethal Effects Adjudication Lifecycle Process

12.IAD2 Obtaining TACELINT

12.CY1 Integrated Air Defense Systems (IADS) Degradation (CYBER Effect)

12.CY2 Individual Radar Disruption (CYBER Effect)

12.CY3 Counter Fire Degradation (CYBER Effect)

12.CY4 Counter Unmanned Aerial System Attack (CYBER Effect)

12.CY5 Email Degradation Attack (CYBER Effect)

12.CY6 Web Redirection (CYBER Effect)

12.CY7 Social Media Suppression (CYBER Effect)

Appendix 12.CY-A: Summary of Cyber Effects

Appendix 12.CY-B: Cyberspace Adjudication Rules and Notes

12.EW1 Communications Jamming (EW Effect)

12.EW2 GPS Jamming (EW Effect)

12.EW3 DATA LINK JAMMING (EW EFFECT)

12.EW4 Radar Jamming (EW Effect)

12.EW5 Satellite Uplink Jamming (EW Effect)

Appendix 12.EW-A: Summary of Electronic Warfare Effects

Appendix 12.EW-B: Electronic Warfare Adjudication Rules and Notes

12.SP1 Space Signals Intelligence (TACELINT) (Space Data)

12.SP2 Space Multispectral Imaging (MSI) (SPACE DATA)

12.SP3 Space Overhead Persistent Infrared (OPIR) DATA (SPACE DATA)

12.STO Integrated Joint Special Technical Operations (IJSTO EFFECT)

Figure 12.STO-1 IJSTO Submission and Adjudication Flowchart

CHAPTER 4 – DEFINITIONS, ABREVIATIONS, AND ACRONYMS

Figure 4.1 OSC Nonlinear AOR Example

Figure 4.2 Sample Playbox

SUMMARY OF CHANGES

Contents UNCLASSIFIED 8

Revised Aviation ISR platform operations.

Changed responsibility for the P-CHEM overlay.

Updated Intel WARSIM functions.

Revised and updated all references to MCTP re-organization.

Contents UNCLASSIFIED 9

CHAPTER 1 – INTRODUCTION & OVERVIEW

A. Purpose To publish the Mission Command Training Program (MCTP) Warfighter Exercises (WFXs) WARSIM supported Rules and Workarounds. Rules are directives that govern the conduct of a MCTP training exercise. Workarounds are a functionality or military operation not modeled, or not adequately modeled, in the simulation(s). This document is universal and applies equally to Blue Force (BLUFOR), Opposing Force (OPFOR) and Exercise Control (EXCON) personnel. The intent of this document is to provide standard rules and workarounds to ensure a “level playing field” during Simulation driven exercises. Simply stated, both the BLUFOR and OPFOR have equal opportunity to gain advantage over one another by application of doctrine, tactics and force levels. The rules and workarounds apply equally, as appropriate, to both forces as they attempt to defeat one another in a competitive, free play environment.

MCTP recommends that all U.S. Army simulation centers using the MCTP Aggregate Constructive exercise models (WARSIM, etc.), federated or non-federated, use this book to enhance exercises, standardize rules and workarounds and increase the level of soldier understanding and confidence for MCTP exercises.

B. WFX Overview:

The WFX is a simulation-driven, MSEL supported, command post exercise (CPX) that allows the BLUE Training Audience commander to “fight” his organization and assess its training proficiency. The WFX Training Audience and its designated subordinate headquarters fight the battle from field command posts (CPs). Each field CP is represented by subordinate Role Player Work Cells in the Simulation Center (SIMCTR). In a like manner, the OPFOR, called the World Class OPFOR (WCOPFOR) establishes doctrinal CPs separate from the WCOPFOR Work Cells and fights the battle from the Fort Leavenworth National Simulation Center (NSC). The WCOPFOR higher headquarters control is provided by the MCTP S-33 Forward Control and Scenario Design work cells located in the MCTP operations center at the WFX site.

During the WFX, BLUFOR Role Players operate in SIMCTR work cells use the simulation to execute orders they receive from their field Training Audience CPs. The Training Audience commanders and staff make decisions based on simulated battle results provided by their SIMCTR work cells through doctrinal communications and simulation reports and unit SOP reports. A critical training enhancement to the field CPs is the role-playing of subordinate units and staffs in the SIMCTR work cells as they report information.

Through role-playing, the SIMCTR work cells translate the automated model outputs into tactical and/or SOP reports expected from units in the Operational Environment. As a result, the simulation becomes transparent or “real” to commanders and staffs in the field and the overall training experience is enhanced.

During the WFX, the Training Audience unit commanders and staffs receive several formal and informal After Action Reviews (AARS) that highlight areas for training sustainment and improvement. MCTP analysts process reports and data from the simulation to help in preparation of issues and graphics used in the AARs. From these AARS, the commanders can assess proficiency and establish future training priorities.

Contents UNCLASSIFIED 10

C. Exercise Control Group (ECG):

The Exercise Control Group (ECG) - Comprised of Decision Board members, Functional Cells, Syndicates and Observer Coach/Trainer (OC/T) representation, provides a centralized control environment to present a synchronized and realistic exercise to the Training Audience. The ECG ensures the simulation and scripted scenario events remain technically and operationally synchronized, as well as providing replication for functions, actions, responses and decisions of agencies external to the Training Audience. The ECG also provides and approves portrayal of the Operational Environment, to include initial and follow-on intelligence, scenario and information stimulus. Through OC/T representation, the ECG monitors and controls the exercise to ensure accomplishment of the training objectives.

The Exercise Director (JTF, Corps, Army Group, or Army Force Commander) controls the exercise by establishing the exercise starting conditions, writing the higher headquarters operations plans/orders. The Exercise Director controls both BLUFOR and OPFOR forces to ensure that the conditions are set for the unit to meet its training objectives. The MCTP Commander is the Deputy Exercise Director and is responsible for the SIMCTR operations, exercise control and AARS. The SIMCTR, its equipment, exercise personnel and all required support personnel are under the operational control (OPCON) of the MCTP Commander for the duration of the WFX preparation, exercise and close-down. MCTP Exercise Control (EXCON) work cells provide all WFX participants with a replication of operations, intelligence and combat information systems not modeled in the simulation, in addition to unit play outside the Competitive Zone. EXCON supports the WFX unit, OPFOR, higher headquarters and all OPFOR work cells. Figure 1 shows the current ECG organization.

Contents UNCLASSIFIED 11

Figure 1. Exercise Control Group Schematic

Contents UNCLASSIFIED 12

D. Simulation Control Simulation outcomes, Sharepoint (SIMLAN) based MSEL Tool activities, combined with role-playing, simulation controls and training objectives, drive the WFX. Although the simulation control mechanisms are structured for standardization, they are dynamic for different scenarios and training objectives.

MCTP employs Observer Coach/Trainers (OC/Ts) at field CP locations and MCTP Civilian Work Cell Instructor Controllers (WICs) working with Role Players in the SIMCTR work cells to simulate the Training Audience TOC, subordinate units and support teams for simulation management and mission command networks and systems analysis.

The following type Work Cells are normally employed at the exercise site SIMCTR representing administrative and Warfighting Functions (WfF):

Maneuver Sustainment Army Aviation Blue Operations Technical Support Team Fires Protection Air Force Fixed Wing Senior Control

COIC/S-33

Exercise Control: Intel, Maneuver Control, SOF, PAO, Blue Air (FW)

MCTP military and civilian personnel in the WCOPFOR CPs and work cells under the direction of the S-33 perform their duties at the Ft. Leavenworth SIMCTR. The following OPFOR work cells normally operate from Ft. Leavenworth:

Maneuver and Combat Support Integrated Fire Support (Indirect, RW, FW-ADA) Flanks, Follow-On Forces Material Support ISR / Intelligence Operations Infrastructure SPF/Commandos /Civilians OPFOR Senior Control Rear

The MCTP Digital Support Team (DST).

The DST supports Operations Groups A, B, C, and MCTP WFX exercises on a sustained basis. During C Team WFXs, DST provides and sets up the servers and clients for a digital HICOM with equivalent digital capabilities of a division headquarters.

MCTP operates the MCTP Digital Training Laboratory facility in the basement of Building 246 with selective Army Mission Command System (AMCS), namely MCS (CPOF), AMDWS, TAIS, JDOCS, AFATDS, Domain, Exchange and SharePoint.

DST digital analysts provide familiarization training to MCTP military and contractor

Contents UNCLASSIFIED 13 personnel concentrating on the AMCS systems.

Digital analysts provide assistance on any AMCS questions relating to the collection, storage, organization or display of digital information collected by them from WFX exercise unit TACLAN and their AMCS systems.

DST engineering personnel establish and maintain the collection network that harvests data from WFX exercise TACLAN for transmission to the WFX simulation center and finally to each analyst's ARCHER workstation.

DST provides direct support to WFX Operations in areas of training, Tactical Mission Command (TMC) equipment and TMC expertise.

The Mission Command Adapter (MCA) Web Server replaced the C2 Adapter to convert game messages into valid C4I messages and forward them to inject points that allow the unit to see the game. DST is responsible for the Mission Command Adapter that directly feeds the Training Audience GCCS-A, DDS, CPOF, AFATDS, and AMDWS.

The MCTP Simulation Support Team (SST).

During MCTP WFX exercises, the SST provides on-site support to the BLUE OPSGRP directing the WFX and to S-33 directing the WCOPFOR. This support includes functionality expertise and, in conjunction with the Parametric Data Base Team (PDT), parametric database technical support. The SST maintains fulltime oversight of the simulation game to facilitate analysis of reported problems and perceived game anomalies. This allows for quick analysis and identification of problems and assists in the isolation of the problem to database, code, or for documentation as a training issue. The SST can then develop and recommend an interim solution or workaround as required. The SST also maintains a test game workstation for use in troubleshooting and identifying problems, and solutions to those problems.

The SST receives reviews and documents all legitimate reported game deficiencies and all interim changes to the database for further resolution after the exercise. Problems that cannot be fixed on-site are documented and coordinated with the NSC for correction.

The SST also monitors the overall system performance during WFXs such as excessive memory usage during saves, game ratio difficulties, etc., and makes recommendations to overcome the difficulty.

Requests for SST testing that are not directly germane to the current exercise will be honored if they can be accomplished without interference with WFX duties, otherwise they will be deferred for testing at home station during non-WFX periods.

The MCTP Technical Support Team (TST).

TST personnel support MCTP exercises at the National Simulation Center (NSC) and McHugh Training Center at Fort Leavenworth, KS and forward Mission Training Complex(s) (MTCs) WFX SIMCTRs. This team is responsible for receiving MCTP exercise equipment at the exercise site IAW the WFX exercise Simulation Control Plan (SCP) and directions from government personnel and for configuring all WFX SIMCTRs work cells.

They are also responsible for operation of the WARSIM simulation and other simulation

Contents UNCLASSIFIED 14 software during work cell training and the WFX. In addition, the TST is responsible for setting up and staffing the Exercise Control Group (ECG), providing higher enclave intelligence products, managing the exercise databases, obtaining information from unit digital systems, and providing support for exercise AAR's. Following ENDEX, the TST is responsible for packing and redeployment of MCTP exercise equipment.

E. Simulation Outages Simulation outages will follow a modified notification procedure. The LOCOMs will notify EXCON if they suspect a simulation issue. EXCON will subsequently notify the MODs and SIMs POCs. The MODs and SIMs POC will notify WF6 NLT 30 minutes after notification and receive WF6 guidance. That guidance/notification will go back to EXCON to be logged in the WFX daily SIGACT to ensure that appropriate information is pushed out and across the MCTP Team. The S-33 EXCON will continue to get a voco notification and subsequent email update via NIPR NLT 0600 daily – the EXCON ACs will provide the daily summary of events to the S-33 and all Division Chiefs.

F. Changes and Revisions Users of this document are encouraged to submit recommended corrections, deletions and changes to the:

Commander, MCTP ATTN: ATZL-CTB (WARSIM Workgroups) Fort Leavenworth, KS 66027

Corrections or recommended changes should include a statement of the problem and the reason for the recommended correction or change. Submission should also state if the change is a fix to existing software or a suggested change for a future version of WARSIM.

G. Violations General. Violations of the rules and workarounds in this directive detract from the intent of the exercise and reduce WFX training opportunities. For the purpose of this directive, a violation is the willful circumvention or failure to apply or enforce the intent of the MCTP Rules and Workarounds.

Reporting. The first occurrence of a violation in the Work Cells will be discussed between the Work Cell OIC and the MCTP Work Cell Instructor Controller. The Cell WIC will report a second occurrence to the site Senior Control who will take the issue to the MCTP lead/site Training Operations Officer or EXCON. OPFOR will report violations to the MCTP S-33 Operations Center and the OPFOR Team Chief.

H. Approval Submission of all rules and workarounds will be through MCTP WARSIM Work Groups to the Commander, MCTP after approval by the MCTP Simulation Configuration Control Board Working Group for final approval.

Contents UNCLASSIFIED 15

CHAPTER 2 – RULES

To provide Rules for the conduct of constructive simulated tactical operations during War Fighter Exercises (WFXs) using WARSIM.

B. Simulation Center (SIMCTR) Rules

1. General.

a. The MCTP Commander is the SIMCTR Officer-in-Charge during an MCTP War Fighter Exercise (WFX).

b. Unit Role Players in the SIMCTR, all SIMCTR personnel, support personnel and equipment from the beginning of set-up through WFX ENDEX, Change of Mission and tear down, are OPCON to the MCTP Commander for the duration of the WFX preparation, exercise and close-down.

2. Coordination Rules.

a. Coordination between Work Cells in the SIMCTR will not take the place of coordination that normally occurs between Training Audience headquarters, nor will it circumvent coordination, which would normally be conducted using tactical/designated communications to the Training Audience.

b. Coordination normally required between units (i.e. aviation, maneuver, engineer units, etc.) will be subject to realistic time/distance delay. When liaison aircraft are used, the air mission will be flown in WARSIM before the coordination or liaison can begin.

c. Work Cells OICs and other Unit Role Players will not leave the SIMCTR for meetings, nor go to a Training Audience CP, except as in 2.d. and 2.e. below.

d. The MCTP Operations section will establish a liaison room in the BLUFOR SIMCTR for Training Audience Commanders or Staff to meet with their Work Cell OICs or Staff. All other contact between Training Audience members and Work Cell or Role Players will be through the SIMCTR message center. OPFOR brigade commanders will meet in the OPFOR division's CPs or in a designated liaison area.

e. Dual-hatted Work Cell OICs and staff officers are allowed to move between the SIMCTR and field CPs for professional purposes to accomplish the requirements of both positions. Approval for individuals, by name, using this rule will be made by the MCTP S- 33.

3. Access Rules. MCTP S-33 establishes SIMCTR access procedures. SIMCTR access is restricted and will be controlled by rosters and badges. Badges will be displayed at all times in the SIMCTR.

a. With the exception of the message center and liaison room, the SIMCTR is off limits to all Training Audience members. Commander, MCTP, will grant other exceptions on a case-by-case basis. OPFOR CP Players will not have access to OPFOR Work Cells. Work

Contents UNCLASSIFIED 16

Area Role Players will not have access to the OPFOR CP, except as noted in paragraph 2.d. above.

b. The MCTP Exercise Control (EXCON) Cells are off limits to all Role Players, without approval of an MCTP Exercise Control Work Cell Instructor Controller in the course of official business.

c. The MCTP OPSGP Operations work area is off limits to all Role Players.

d. Technical Control work areas are off limits to Role Players.

4. SIMCTR Role Player Rules.

a. Competitive Role Player Work Cells will configure as TOCs, and represent units and staffs subordinate to the appropriate exercised Training Audience unit headquarters and OPFOR Commanders. Role Player Work Cell personnel will implement the Training Audience commander's orders and intent, and report the results of actions professionally, realistically and fairly to the Training Audience.

b. Each BLUFOR Role Player and OPFOR Role Player operates, records and reports using unit SOPs and then communicates only realistic information to the Training Audience unit given the fog and friction of war.

c. If a BLUFOR C2 system is NOT federated with WARSIM, Work Cell personnel role-play to make the simulation invisible to the Training Audience commander and staff. Work Cells will not refer in their communications with the Training Audience to "WARSIM", "the simulation", the "game" or "the computer" or other inference/references to an artificial simulation or model.

d. If a BLUFOR C2 system is federated with WARSIM (when WARSIM reports and unit movements are visible to the Training Audience via the C2 system) in the event of a game stoppage, Work Cells will continue to role-play, unless directed otherwise by the Commander, MCTP.

e. Except as authorized by Commander, MCTP, no one will take WARSIM generated printed materials (printouts and/or graphics) from the SIMCTR to the BLUFOR LNO room, BLUFOR Training Audience CPs, TOCs, or the OPFOR headquarters CPs. WARSIM printed materials will not be Faxed or electronically transmitted to TOCs. If authorized, all personnel must ensure proper procedures are followed IAW the classification level of the material. NOTE: All printouts from WARSIM are considered classified requiring appropriate control and destruction.

C. General Rules

1. Role Player Work Cells will display only their portion of the Competitive Zone (CZ) on

Work Cell Battle Space Work Station (BSWS). Role Players will not subscribe to Situational Awareness (SA) feeds from aircraft/UAV systems unless they are actively participating in an “Aviation Precision Attack” operation unless specifically authorized to do so by Senior Control on approval of EXCON. An exception to this might be an Intel Role Player who would have doctrinal access to the information, which the SA function displays on the BSWS Map View he/she is operating. An example of this would be an Intel Role Player

Contents UNCLASSIFIED 17 collecting information for dissemination to subordinate units through a report or INTSUM would be appropriate.

2. Fires, maneuver and combat are not allowed outside of the CZ except as directed by Exercise Control (EXCON). The STARTEX MOI must detail the specific purpose and scope of flank Unit play (scripted, orchestrated units).

3. Icons will not be stacked on top of each other. (Exception: Units created using the Task Organization menus are initially stacked and must be tactically displaced following a Task Organization process.)

4. Role Players will not use inappropriate units (e.g., Refugees, EPWs, Aid Stations, Hospital elements, etc.) for scouting/intelligence/forward observer gathering activities by directing them to come in contact with or direct fire on enemy units.

5. Role Players will not use "Gamesmanship" to subvert or influence WARSIM outcomes.

Example: UAS aircraft flying beyond range limits and flight times which exceeds their known operational capabilities. Using the game’s merge capability to enable a unit’s safe crossing of obstacles and/or rivers is another example of gamesmanship.

D. Operating Rules The following rules apply to the use of WARSIM Senior Control.

1. Use of Senior Controller capabilities by a Work Cell during a WFX, other than BLUFOR Senior Control and OPFOR Senior Control Rear and any function requiring Senior Control Functionality on a BSWS, requires permission of the MCTP Operations/EXCON or OPFOR Control Rear. This applies to any BSWS logged in as Senior Controller during competitive exercise play. Exception is granted during non-competitive exercises during periods of Work Cell training, MINIEX and STARTEX Data Load.

2. Any BSWS logged in as Senior Controller has the ability to grant Magic capability to any other Role Player BSWS; however, the following specific rules apply:

a. Only OPFOR Senior Control Rear shall grant Magic to any Role Player BSWS.

Granting magic is only for a stated mission requirement. For example, during BLUFOR Work Cell set-up, Functional Training and MINIEX. Coordination between these two Senior Control position sites is required.

b. During competitive play, Magic to competitive Role Player BSWSs is unauthorized.

c. Functions using Senior Control may only collect data and reports, and will not give competitive commands affecting the exercise. These functions are normally found in non-competitive work areas in the Analyst, S-33 forward, BLUFOR Senior Control, OPFOR Senior Control Rear, and CIC. WIC leads in competitive (role player) work/response cells will have access to the Senior Control login to facilitate task organization changes; conduct adjudications forensics; assist EXCON directed reconstitution events when required; magic move low-strength units IAW Workaround 1.1; manage EXCON directed Rotary Wing Aviation glide path strengths such as Operational Ready Rates and weapons loads, execute simulation corrections IAW the DAM, and other specific actions as direct by WF6, Contents UNCLASSIFIED 18

EXCON and/or Senior Control.

d. Functions using Senior Control to control orchestrated units are subordinate to BLUFOR Senior Control Forward and OPFOR Senior Control Rear and will follow the procedures directed for these functions to achieve exercise objectives. These functions are normally found in EXCON’s Maneuver Control, OPFOR Air/BLUFOR Air, OPFOR/BLUFOR SOF Cells and INTEL cells. See Orchestrated Unit in chapter 1.

e. Only BLUFOR Senior Control and OPFOR Senior Control Rear may make game adjustments (adjudications/reconstitution) for competitive Role Player BSWSs during competitive play. BLUFOR Senior Control may grant WIC Leads this ability on a case-by-case basis based on load and time sensitive considerations. Coordination may be required with LOGFED when federated under Use Case 2.

f. Only BLUFOR Senior Control, in coordination with EXCON, and OPFOR Senior Control Rear will establish and control the exercise competitive “global” graphics and weather. During training Senior Control Forward will assign dedicated training areas to Role Player Work Cells.

g. Only BLUFOR Senior Control Forward will, in coordination with EXCON, confirm the establishment of the Sensing Zones at the beginning of training and during STARTEX Task Organization:

(1) EXCON, in coordination with Scenario Generation (Database), and the Lead Training OPSGRP; confirms the coordinates for the Play Box, provides the exercise Operation Order area graphics and exercise Weather Plan to Senior Control Forward.

(2) Scenario Generation inputs the play box and Sensing Zone coordinates into the SGEN Workbook.

h. All other WARSIM Senior Control functionalities are restricted to BLUE and Red Senior Control exclusively. BLUE and RED Sr. Control will maintain a written log of these actions taken for reference.

3. The following rules apply to all competitive Role Player Work Cells.

a. Role Players will not change Automated Unit (AU) names unless approved and coordinated by the Work Cell WIC through Senior Control, the Digital Support Team (DST) and LOGFED to ensure continuity of communications with the training audience.

b. Communications between SIMCTR Work Cells and the Training Audience CPs will:

(1) The MCTP Commander is the approval authority for use of other than doctrinal/tactical/designated communications.

(2) Use the reporting formats specified in the player unit's Standing Operating Procedures (SOP) and submitted per SOP schedules.

(3) Include only reasonably obtained combat information to include information provided to Work Cells by the Intelligence Control Elements through simulation communications and information obtained from JMSEL injects.

Contents UNCLASSIFIED 19

(4) Role Player Work Cells will not use the WARSIM Communications Network Manager Tool to establish or change the communications links between the Simulation and the C2 systems. These required links are set during database development prior to training and STARTEX and created through the scenario generation (SGEN) process. WICs will resolve any issues through Senior Control and Mission Command Adapter Web Server team for action. This rule does not apply/restrict changes for Sustainment Support Relationships (medical, maintenance, and supply).

d. Each Role Player Work Cell will function as a Tactical or Logistics Operation Center.

Work Cell personnel will maintain a situation map (i.e., CPOF) to post and report locations and other data to the Training Audience CPs. Each Role Player Work Cell will maintain a log, journal etc., as specified by the player unit’s SOP.

e. Role Players will not attack targets unless they are legitimately acquired.

f. Higher HQs (HHQ) (Battalion or Brigade) icons will not be lost in the simulation; their loss would affect the AAR process and production. Their Equipment Groups (EG) will never be merged into other/subordinate units. (See Workaround 1.2, Command Post Overrun / Destroyed.) Modify based on current FORSCOM guidance.

g. Merging will not be used to enable (gamesmanship) the crossing of obstacles and/or rivers.

h. Unit/Icon symbols. Armor, Mechanized and infantry, Brigade and Battalion will graphically display the appropriate headquarters symbol. Company and below (Light Infantry, Artillery, ADA, Chemical, Engineer, Reconnaissance units) will graphically display the symbol of their functional area or parent.

i. OPFOR ground scatterable mine laying systems are limited to emplacing 4000 linear meters of minefield per system per 24-hour period unless specified in the MCTP and Training Audience MOI or approved by EXCON.

j. Infrastructure map symbols developed and controlled by S-33 are represented in WARSIM by appropriate map symbols (Public Buildings, Water and Sewage Plants, Factories, etc.) and may be damaged competitively by air-to-ground fire, indirect fire and demolition. Senior Control may damage them as specified to support a scenario event.

(1) Damage done to combined target(s) and infrastructure will be adjudicated by EXCON in coordination with WSPMESII-PT to meet the scenario for the event. The target may be damaged or destroyed. The infrastructure will be rebuilt by magic to meet the scenario end state.

k. Role Players WILL NOT LOWER the "Default Automated Withdraw Behavior" setting below 30%, on any order/menu, unless directed by the Senior Player Commander (Corps, Division, Brigade, and OPFOR). Lowering the default will NOT be used as a tool for gamesmanship, thus misrepresenting doctrine.

l. Work Cell Instructor Controllers (WICs) and Role Players WILL NOT execute the DEAGG function in WARSIM 6.2.3 during a WFX unless specifically authorized to do so from Senior Control. This function has no application in a MCTP hosted federated WFX.

Contents UNCLASSIFIED 20

Using this function risks a multitude of subsequent AU functionality and task organization problems. Should someone in a Work or Response Cell execute this function, once discovered, they will notify one of their WICs who will execute the REAGG function to return the AU or EG to its original configuration and confirm its functionality. If a platform needs to be a separate AU such as a Dozer or other piece of specialized equipment, the WIC or Role Player will split the platform out with appropriate personnel or other associated equipment and promote it to AU status. Once the split platform AU is no longer need the WIC or Role Player will use appropriate procedures to return platforms contained therein to their task organization AU.

E. Unit Icon Assignment Rules

1. The following unit icon assignments for Work Cell control apply in the SIMCTR.

a. Mission Command Relationships.

(1) Units are assigned to work/response cells and placed on the Simulation Control Plan in accordance with the unit’s MTOE, and the troop list agreed to before STARTEX. The initial OPORD and FRAGORDs prior to STARTEX Load establish the task organization that will be in effect at STARTEX.

• Units that are organic, assigned, attached, OPCON, or TACON per that initial order are normally role played in the work/response cell of the BCT, FAB, DIVARTY, or MEB that the training audience OPORD placed them.

• Corps level Medical Air Evacuation units will be role played by MCC in a division WFX, or Medical Brigade Work Cell/MCC in a corps WFX.

(2) Units battalion in size or larger assigned, attached, OPCON, or TACON per the initial OPORD or subsequent FRAGORDs will generally be role played in the cell they originally occupy. This includes battalion and larger units from the Corps, which the MCC controls. However, under certain circumstances it would be preferable to role play the unit in the gaining work cell. Factors to consider include:

• Ease of directing the unit’s actions and battle-tracking (within the gaining cell, vs.

coordinating with a role player in another cell).

• The gaining cell’s ability to accommodate the unit within the cell (separate BSWS or adding to an existing unit role).

• The feasibility of the unit’s original role player transferring to the gaining cell if the gaining cell cannot provide a role player.

• Whether or not the gaining cell trained using this unit during a ramp-up exercise.

• The losing cell’s ability to role play the unit to the fidelity required for a competitive cell (i.e., a battalion coming from MCC). The gaining cell OIC’s preference.

(3) Units smaller than battalion in size assigned or attached per subsequent FRAGORDs will be role played in the gaining work/response cell in accordance with the Task Organization contained in the training audience FRAGORD and will be role player transferred to the gaining unit work/response cell. Units smaller than battalion in size that

Contents UNCLASSIFIED 21 are OPCON or TACON may be role played in either their existing Work Cell or the gaining unit Work Cell, depending on the needs of the training audience and the skill set of the receiving cell’s unit Role Players. Senior Control, with guidance from the CHOPS of the OPSGPs involved, will be arbitrator of this decision.

For example:

• A Multi-role Bridge Co (MRBC) is made OPCON per a Division FRAGORD to a BCT for a wet gap operation.

• The CHOPS of the OPSGP observing the Engineer BDE that owns the MRBC does not feel the BCT has the skill to control that unit and the wet gap mission is critical to their training of the ENG BDE.

• The CHOPS of the OPSGP observing the BCT concurs with the MRBC being controlled by the ENG BDE so the decision is made by Senior Control to leave control of the MRBC in the ENG BDE Work Cell.

• The MRBC is not role player transferred and the BCT response cell communicates all orders to the ENG BDE work cell via tactical comms with VOIP as a backup.

(4) Special Operations Forces Units (SF, Civil Affairs, PSYOP units), and Military Intelligence Units will be played from the SOF and Intelligence Work Cells regardless of their Command or Support relationships to other units. However, the role player ID of these units will be shared with the maneuver BCT or Battalion to which those assets have been task organized (use ADD rather than REPLACE during role player ID transfer). The SOF and Intelligence Work Cells will move and execute the mission tasks assigned from the maneuver headquarters. Sharing the role player ID will allow the maneuver units to maintain SA and unit location and status.

(5) TACON task organization for units below battalion will be played by Role Player ADD to the BCT, FAB, DIVARTY, or MEB. The receiving Role Player DOES NOT change the higher headquarters relationship.

(6) The assignment of units inside the SIMCTR should simulate/replicate unit relationships in the field environment, through either command and control or support relationships as specified in the current Appendix B, FM 6.0, May 2014 and JP 3.0.

Contents UNCLASSIFIED 22

Command Relationship

Actions in WS Remarks

Assigned/ Attached

Cut / Paste in Task Organization tree

Unit equipment and personnel are included in new parent LOGSTAT Unit is sustained by new parent Role in WS should automatically change to new parent EXAMPLE: a Combat Engineer company is attached to a BCT

OPCON Role-play transfer; unit remains under organic parent in Task Organization tree (see Notes 1 and 2)

ADD or REPLACE role, depending on circumstances (does losing unit desire to maintain visibility?)

Unit equipment and personnel are included in old parent LOGSTAT Unit is sustained by old parent EXAMPLE: a CHEM DECON unit is OPCON to a BCT

TACON ADD role player; unit remains under organic parent in Task Organization tree (see Notes 1 and 2)

Unit equipment and personnel are included in old parent LOGSTAT Unit is sustained by old parent EXAMPLE: an MRBC (engineer bridge) unit is TACON to a BCT for movement, but will be under parent Engineer work cell control to emplace bridges

NOTE 1: If the providing parent unit is non-competitive (i. e., an Avenger BN coming from an ADA BDE that is not being played from any work cell), it may be suitable to Cut / Paste in the Task Organization tree to ensure that the unit receives sustainment support.

NOTE 2: If the gaining work cell reports the status of the unit and it is not in the gaining Task Organization tree, a separate LOGSTAT must be produced.

Figure 3. Unit Icon Assignment Rules

Contents UNCLASSIFIED 23

F. Automated Unit (AU) Echelon and Management Rules

1. WARSIM is an aggregate level simulation. The greater the number of AUs assigned on a Battle Space Workstation (BSWS) the more difficult it becomes for a Role Player to control these units and slows the simulation down.

2. MCTP trains Corps, Division, and Brigade commanders and staffs. The Database team will build AUs during scenario generation as described below. Work Cell Controllers/Role Players must limit, as much as possible, the number of AUs and their respective echelons when they organize their units and WILL NOT execute the DEAGG/AGG function in WARSIM. The following guidelines apply by Work Cell or War Fighting Function task organization:

a. Brigade Combat Teams (BCT): Maneuver units are normally built in the database using company and specialty platoon level AUs. Specialty platoons, (Scouts, UASs and BN Mortars, should remain as AUs to perform their assigned tasks.

b. Fires: Artillery firing units are built at platoon-level, FIST teams and Radars at squad/section-level will be built as AUs and will not be “merged” into the AU they support.

Do not merge these AUs into other AUs as they will lose their C2 functionality in WARSIM.

d. Aviation: Normally, Attack Aviation units fight as platoon-level AUs. They can go down to section-level (2 aircraft) if the tactical situation dictates. Other Aviation units operate on a by-mission basis. With all FW and RW assets now built as air bases, Role Players will break out assets at the direction of their TOCs or OIC to accomplish assigned missions.

e. Protection:

(1) Engineers will be built at separate company or platoon-level AUs to do engineer tasks but can be merged into an AU that they are supporting to do engineering tasks (provided they possess the equipment). Do not merge if AU supports other AUs.

(2) Air Defense will be built at battery-level AU for HIMAD and at platoon-level AU for SHORAD. SHORAD AUs can be merged into their supported units. ADA radars will remain as AUs.

(3) Military Police will be built at squad/section-level AUs to perform MP missions.

(4) Chemical units will be built at platoon-AUs. Chemical recon units will be built at squad or section level. All Chemical units should operate as separate AUs to perform their appropriate tasks.

f. Special Operations Forces (SOF), (Rangers, Civil Affairs, and PSYOP) will be built at team level AUs.

g. Intelligence: Other Intel units should perform at section level AUs based on the Intelligence systems being employed. Currently Intelligence assets will not be merged, as they will lose their sensor linkage.

h. Sustainment: Sustainment units generally execute their functions at company-level

Contents UNCLASSIFIED 24

AUs with the exception of Transportation units which operate at platoon-level AUs.

G. Decoy Operations

l. BLUFOR use of decoys is only authorized with approval of WF6 or Chief

Controller in coordination with COG of the training OPSGP. If authorized EXCON will notify BLUE Senior Control to coordinate construction and placement. Additional instructions follow:

(1) The terms Decoy, MILDEC, Military Deception and Deception Operations WILL NOT be used interchangeably. DECOY is the only term to be used when referencing decoy operations.

(2) Decoy operations may be conducted by actual combat units, specialized engineer units, Information Warfare and signal deception units. Combat units may only portray similar units. C3D engineer units may deploy inflatable decoys for physical signature and provide radio signature of an actual unit. Fabrication engineer units may deploy inflatable decoys or construct decoys from plywood and fabric for physical signature and provide radio signature of an actual unit. Both engineer units can recover and deploy damaged hulks as additional decoys. Signal Deception units may portray specialized radio signatures, such as Radar emitters.

(3) No ACCM programs are authorized for any deception activities.

(4) BLUFOR pre-built decoy templates are located in BLUECMD/BLUE_DBA section of the Task Organization Manager Tool. Additional decoy templates, when required, will be built and placed within BLUE_DBA. This will prevent force strength reporting issues. Only BLUFOR SR Control is authorized to create BLUFOR Decoy units.

(5) Training units will submit Deception Operations Concept of Operations (CONOPs) for approval prior to the Warfighter Exercise. Submissions will occur along the following timeline:

W-45: Final copy of CONOP sent to the MCTP Information Advantage Division (IAD) POC for review W-28: Exercise Control (EXCON), Operational Contracting Support (OCS), Operations Group IO OC/Ts review CONOPs W-21: Brief MCTP leadership o/a W-21 for CONOPs Implementation Approval W-14: IAD briefs CONOPS summary at RED/BLU Sr. Ctrl Huddle

(6) For Decoy CONOPS submitted after STARTEX, BLUEFOR must submit a decoy plan to the IAD for approval prior to decoy emplacement (see WA 9.3 Decoy Operations for specific guidance). Training Audience will submit the plan through OC/T and OPS Group channels. Work Cells will submit the plan through their higher headquarters (a TA), who in turn will submit through OC/T and OPS Group channels.

(7) Supporting documentation to IAD must include:

• Task/Purpose/Intent for Deception operations

• Construction plan (to include time to construct)

• Transportation plan (to include unit(s) tasked to move/secure)

Contents UNCLASSIFIED 25

• Critical timings (displacement and repositioning)

• Emplacing unit plan (to include emplacement time)

(8) Movement of decoys

• There are NO magic moves

• TAs must submit Transportation plans by W-5 to IWD POC

• Use SIM distance plus employment timetable (next slide) before Decoy icons are available to unit (emplaced)

• IWD notifies EXCON of approval; EXCON notifies Senior Control

(9) If Unit has Radar Decoys on their MTOE (and decoy was included as part of FEP Db Scrub), BLUFOR is pre-approved for employment prior to STARTEX (during Db Upload). The same applies to other decoys approved prior to STARTEX.

(10) Decoy Magic Moves are not allowed. If a decoy is built on a transportation frame (i.e., LMTV), then it may move under its own power. Otherwise, positioning the unit must be included in the transportation and emplacement plans.

(11) Training Audience/Non-Training Audience Priorities.TA has priority of support and have may maximize decoy use in WFX, as long as they meet the approval timeline and requirements. Non-MTOE equipment decoys may only be employed after approval from FOSRCOM. Non-TA may still employ decoys, with the following limitations:

• The decoys must be from the RWA guidelines for BLUFOR DECOY list.

• Decoys may not move from initial place of emplacement (ex. Moved by engineers to OBJ X and emplaced. They will not have subsequent movements).

• Non-TAs will not exceed a quantity of 1 BN’s worth of any given decoy (ex. 1 BN of tank decoys OR 2 Companies of decoy arty and 2 troops of decoy tanks).

OPFOR Specific Rules:

(12) The OPFOR Deception Plan must be approved by the OPFOR Commander. The

OPFOR Deception Plan is included in the WCOPFOR Warfighter Exercise OPORD as Appendix 14 (Deception), to Annex C (Operations).

(13) Provide to EXCON the names of the actual and deception units, and the signatures that the decoys will depict (thermal, radar, visual, radio/electronic, hulks, etc.) so that the appropriate Intel models (WIM/MUSE) will portray the correct signatures.

(14) Include in the interim intelligence exchange indicators the WCOPFOR capability to use decoys.

(15) Include in the final intelligence exchange the names and locations of all decoy units for STARTEX.

(16) Ensure the Intelligence OTs are briefed at the Forward location on the WCOPFOR plan to use decoys just prior to STARTEX and updated as a function of the Daily OPFOR Synch or OT Azimuth Check.

Contents UNCLASSIFIED 26

H. Functional Area Work Cell Rules

1. Intelligence.

a. All simulation of air reconnaissance assets will be flown in the Multiple Unified

Simulation Environment (MUSE) or in WARSIM. A single air reconnaissance asset will not be flown in both MUSE and WARSIM simultaneously.

b. The RC/WC will control the AUs that are assigned or organic to the MI Company of the BCT. Additionally, any MI asset in Direct Support (DS) to a BCT will be controlled in that RC/WC. Transverse chat, email, or phone will be used to communicate sensor tasking to the IWC for input into WIM from the RC/WC. Database and classification constraints in WARSIM Intelligence Model (WIM) do not allow tasking from Lower Enclave Battle Space Work Stations (BSWS).

c. During the conduct of the exercise the Senior Control Intelligence Work Cell Instructor Controller (SCWIC) is responsible for supporting the RC/WC’s WIC with instruction of the INTEL BSWS operator, operational questions, and assist in trouble shooting any issues as directed by the IWC WIC’s or ICD.

d. USAF ISR platforms will be flown in WARSIM unless otherwise approved by WF6.

2. Maneuver.

a. All Work Cell activities and functions are based on orders received from the Training

Audience CPs. Work Cell activities and functions will not usurp the Training Audience commander and staff responsibilities and decision-making prerogatives.

b. Work Cell personnel must operate the simulation within the framework of the Training Audience commander's intent and orders.

c. Work Cell OICs conduct battle planning based on information that would realistically be available, not on all information available from WARSIM.

d. Non-Belligerent Units. Combatant units with non-belligerent status may be created during the pre-exercise database build as a separate side that is neutral or friendly to all other combatant sides. This will ensure that no direct fire engagements occur. This side will be defined in the STARTEX MOI.

(1) If units not originally identified at STARTEX are desired by EXCON to be non-belligerent, the unit air and ground ROE will be changed to “STOP.” Note that this will not prevent hostile side units from engaging them.

(2) If units from two hostile sides are required by EXCON to be within direct fire engagement range without firing at each other, operators will place both sides ROE to

“STOP.”

(3) No BLUFOR/OPFOR Work Cell operator will change a unit identity to become "non-belligerent" without the approval of EXCON. OPFOR Senior Control Rear will make these changes once EXCON approves them.

Contents UNCLASSIFIED 27

3. Protection.

a. Prior to STARTEX, only those engineer and artillery minefields, PDPs, point obstacles, bridges and anti-tank ditches approved by the MCTP EXCON will be allowed to be magically emplaced in WARSIM.

b. After STARTEX, engineer PDPs, bridges and obstacles must be emplaced with a properly competitively formed and executed engineer task, approved workaround or approved FASCAM fire mission.

4. Fires.

a. Field Artillery, FA, support relationships (i.e., DS, R, GSR, & GS) allow MNVR CDRS to quickly make tactical changes to FA assets without changing command relationships. As a general rule, MCTP does not change the original Simulation Center locations for these FA BNs based on field artillery support relationship changes. The training audience should make the appropriate adjustments in their TTPs and C2 systems to doctrinally reflect new Field Artillery support relationship doctrine. WICs will also coordinate any changes in relationships with MCWS personnel.

b. FISTs operate at squad/section-level. Do not merge the FISTs into their BCT supported units or change their unit names. If done, coordinate with MCWS Personnel in Tech Support. Otherwise, the link to AFATDS will be lost.

5.…