2장. 기동 및 전투지원

TRAINER REFERENCE GUIDE

VOLUME 2

MANEUVER/COMBAT SUPPORT

 

Prepared for:

NATIONAL SIMULATION CENTER (NSC)

Fort Leavenworth, Kansas

 

By

CUBIC APPLICATIONS, INC.                                                                                                               26 June 2004

Leavenworth, Kansas

 

 

 

CBS TRAINER REFERENCE GUIDE

                    VOLUME 2 MANEUVER/COMBAT SUPPORT

           

CBS TRAINER REFERENCE GUIDE

VOLUME 2

MANEUVER/COMBAT SUPPORT

TABLE OF CONTENTS

 

 Page

   1-1        SECTION 1:      UNIT ORGANIZATION                         

   2-1        SECTION 2:      UNIT MISSIONS

   3-1        SECTION 3:      SPECIAL MISSIONS                              

   4-1        SECTION 4:      AIR DEFENSE

   5-1        SECTION 5:      FIRE SUPPORT

   6-1        SECTION 6:      MOBILITY/COUNTER MOBILITY/SURVIVABILITY

   7-1        SECTION 7:      CHEMICAL

    A1         APPENDIX A: HANDS on TRAINING VOLUME 2

    A1-1      HANDS on TRAINING: UNIT ORGANIZATION                       

    A2-1      HANDS on TRAINING: UNIT MISSIONS                    

    A3-1      HANDS on TRAINING: SPECIAL MISSIONS 

    A4-1      HANDS on TRAINING: AIR DEFENSE

    A5-1      HANDS on TRAINING: FIRE SUPPORT

    A6-1      HANDS on TRAINING: MOBILITY/COUNTERMOBILITY/                                                                                            SURVIVABILITY

    A7-1      HANDS on TRAINING: CHEMICAL

    B1          APPENDIX B: SLIDES FOR VOLUME 2

                  SLIDES FOR SECTION 1: UNIT ORGANIZATION        

                  SLIDES FOR SECTION 2: UNIT MISSIONS  

                  SLIDES FOR SECTION 3: SPECIAL MISSIONS                         

                  SLIDES FOR SECTION 4: AIR DEFENSE

                  SLIDES FOR SECTION 5: FIRE SUPPORT

                  SLIDES FOR SECTION 6: MOBILITY/COUNTERMOBILITY/

 SURVIVABILITY 

                  SLIDES FOR SECTION 7: CHEMICAL                                                      

VOLUME 2

SECTION 1

UNIT ORGANIZATION

 

1.1        INTRODUCTION  (SLIDE M1-1) CBS orders enable maneuver controllers to task organize combat units, and to attach or detach units.

 

             GETTING STARTED  (SLIDE M1-2) Prior to beginning any exercise, obtain the OPORD for the units involved to learn how the commander has organized his forces to support the scheme of maneuver.  CBS permits task-organizing forces as they are in a real tactical situation.  This slide shows the topics explained in this portion of the document, which assist the controllers in task organizing forces in CBS.        

                

             LOGISTICS REPORT  (SLIDE M1-3) Examine the Task Organization Annex of the OPORD to see how the commander has organized for combat.  This examination of the Task Organization may lead to questions about the TO&E of a particular unit.  In the BSC, the controller may learn about the unit organization and equipment as it exists in the simulation by requesting a variety of CBS reports.  Seldom will the CBS unit organization completely conform to the unit’s actual TO&E as CBS simply does not model all of the equipment and personnel MOS and ranks that are contained in the unit.  The first report, the LOGISTICS REPORT provides the full TO&E of a unit as it is modeled in CBS.  This report is obtained by using the menu shown on this slide.  Type in the name of the desired unit in the UNIT NAME field.  UICs on Logistics reports will be discussed in a later section.  LOGREPs for up to four units can be requested simultaneously by entering the unit(s) name in the Unit Name field.  Leave the other fields blank if a complete LOGREP is needed.  If specific sections are desired, enter Yes in those fields

 

             This report provides the most current and accurate information available on the unit. 

 

             (SLIDES M1-4 - M1-7)  These slides show an example of the LOGISTICS REPORT.  For now, note the TOE column that shows the unit’s authorized combat systems and combat support systems.

 

             Personnel authorized are shown in the authorized column under the status of personnel block.  The supplies authorized for the unit are reflected in the Stockage Objective column of the report. 

 

             The READY column shows the systems that are available and crewed for combat and combat support systems.  The AVAILABLE column shows the personnel that are available in the unit while the on HAND column shows the supplies that are currently on hand in the unit.

 

             Note the consolidation of the personnel into groupings, which in CBS are called CMFs, and the consolidation of various light trucks, which are called LIGHT.TRUCK.4X4 in CBS.

 

             Further systems consolidations, crewing considerations and other details of the Logistics Report are discussed in Volume 4, Logistics, of this Guide. 

 

             SUMMARY REPORTS  (SLIDE M1-8) There are five reports available under the SUMMARY REPORTS menu shown on this slide.  The requested report is sent to the VT monitor and may be printed by pressing the PRINT key.

 

             These reports are SITUATION REPORT, QUICK LOOK REPORT, COMBAT POWER DISTRIBUTION REPORT, UNIT MOVEMENT REPORT and CONVOY MOVEMENT REPORT.  The first two of these are discussed below while the others are examined in a later section.  

 

             (SLIDE M1-9)  This slide shows an example of the SITUATION REPORT.  It provides detailed information about the status of the unit.

 

             The weapon radius shown is the range of the longest shooting weapon in the unit.

 

             Unit radius is the circular area, which contains the unit’s combat and combat support systems.

            

             The Military Load Classification (MLC) of the unit is shown.  The unit’s MLC is based on the MLC for the heaviest vehicle in the unit.

 

             Augmented status indicates whether the unit has been augmented with trucks using the Troop Lift function or not.

 

             The massing field indicates if the unit is part of a mass unit operation.  If the unit is part of the mass operation, the field shows the operation name and the effective time.  Otherwise, the field shows no.

 

             The other fields of this report are explained in other sections of this guide.

 

             (SLIDE M1-10)  This slide shows an example of the QUICK LOOK report.  This report provides information on combat systems, combat support systems and supplies that are ON HAND in the unit.  It also shows a list of all UICs associated with the unit.  (See discussion of UICs later in this section.)  It is usually accurate but the log report should be viewed if there is a question about the accuracy of the information contained in the Quick Look report.

 

1.2        UNIT ORGANIZATION  (SLIDE M1-11) The topics listed on this slide help the controller organize his units.

 

             (SLIDE M1-12 & 13)  CBS uses a unit name to identify a CBS unit and to control the unit’s actions.  Names should be easy to remember and should be associated with the mission or unit.  Generally, it is best to use standard Army procedures to name units.  Shown here as some examples of names that should be used in CBS.  Note that they generally follow the accepted naming conventions that are used for units in OPORDs and on operations maps.

 

1.3        SPLIT UNIT  (SLIDE M1-14) If a unit is to be detached from its parent unit, use the SPLIT UNIT order shown on this slide.  The fields for this order are:

 

             PARENT UNIT NAME: Use LIST NAMES or type in the unit name for the parent unit.

 

             The next fields should be filled out onLY if the characteristics for the PARENT UNIT need to be changed.  Generally, do not use these fields.  If used, use LIST NAMES to complete the SYMBOL and ECHELON fields and type in a new, UNIQUE name for the PARENT UNIT.

 

             The next fields apply to the NEW UNIT BEING FORMED.

 

                           UNIT NAME: Type in a UNIQUE name for the new unit being formed.

 

                           SYMBOL:  Use LIST NAMES to select the correct symbol for the unit being formed.

 

                           ECHELON:  Use LIST NAMES to select the correct echelon for the unit being formed.

 

                           100% EFFECTIVE: Controllers may split out a unit at 100 % from a very low strength unit.  Options are YES or NO with NO as the default.  If YES is used, all combat systems, combat support systems and personnel required by the template will come out at 100%.  The supplies split out will not be at 100%.  If NO is used, the combat systems, combat support systems, personnel and supplies will come out of the parent unit proportionally to each items ratio of ready to TOE.  This order prevents the controller from splitting out a unit if the action would wipe out the parent, make it incapable or create a unit that would be wiped out or incapable.

 

                           TEMPLATE:  Use LIST NAMES or type in the name of the template to be used to form the new unit.  Note that there is a mandatory entry on the right side of this order under this field.  This is used when cross attaching only one company (unit) to another unit.

            When detaching a second or third unit from a parent organization; e.g., a second and third company from a battalion, the battalion (parent unit) name should not be changed until the split for the last company is prepared.  At this time, use the UNIT NAME field on page one to change the name of the parent unit.

 

             BY UIC: See discussion of UICs later in this section.

 

1.4        MERGE UNIT To ATTACH units(SLIDE M1-15), or to reorganize and combine units, use the MERGE UNITS order. 

 

             (SLIDE M1-16)  This is the menu used to merge units.  Many of the fields should be familiar. 

            

             Units may not be merged across rivers and unbreached obstacles.

 

             (SLIDE M1-17)  The key points in using Split/Merge orders are shown on this slide. 

 

             Another technique for task organizing units is to place all units at the same point using GROUND MOVE or MAGIC MOVE, split out small units from each parent unit and then merge (use the NON-TEMPLATED UNITS field) the small units into other parent units as desired.

            

             Another limitation is that the TOE "templates" for units are already loaded into the database.  To split out a unit, for which a template does not exist, create a template or edit an existing template.

 

1.5        CREATE TEMPLATE  (SLIDE M1-18) This menu as shown on the slide, allows the controller to create his own templates.  Note that the template name must be unique, and that crewing must be IAW CS and CSS CMF requirements.  Once the order is completed and sent to the game, a recapitulation report of the template is generated automatically by the simulation and sent to the workstation.

 

             If an error has been made in creating the template an error report is sent to the workstation indicating what error(s) occurred and what corrective action should be accomplished to create a usable template.

 

             It is good idea to save the Create Template order when creating a new template.

 

             (Slide M1-19)  CREATE TEMPLATE FROM UNIT: This order allows the creation of a template from an existing unit without having to merge units to establish a template.  Enter the name of the unit.  The unit must be assigned to the workstation.  The template created is unlocked and may be edited.  No automatic template report is generated.  To confirm that the template has been created, obtain a unit template report.

 

             (SLIDE M1-20)  The UNIT TEMPLATE REPORT provides the TYPE (ground), SUBTYPE (Infantry), unit radius, weapons radius, and information on combat, CS, and CSS systems, supplies, infiltration capability and other information of a unit that is created by the template.

            

             (SLIDE M1-21)  Use the EDIT TEMPLATE menu to edit a template.  This permits the controller to recall an existing template at the workstation and create a modified version.  Certain templates may be locked so that they can not be changed by either the template editor or by templated marginal units in a merge without senior control permission. 

 

             To edit an unlocked template, fill out the BASE TEMPLATE NAME field and change the values for that template.  This will provide a template with the same old name but with new values for systems required by the template.

 

             To create a new template, fill out the BASE TEMPLATE NAME and the NEW TEMPLATE NAME fields on page one of the order and fill in the remaining pages with the values desired for the template.

 

             As shown on the slide, default values for the template may be entered.

 

1.5        CHANGE UNIT NAME/HHQ/WS  (SLIDE M1-22) Finally, to change a unit name, its higher headquarters, or transfer the control of a unit from one workstation to another, use the CHANGE UNIT NAME/HHQ/WS order.  It is found under Task Organization Orders.

 

1.6        TASK ORGANIZATION WITH UNIT IDENTIFICATION CODE (UIC) (SLIDE M1-23) The purpose of this section is to provide detailed information on task organization when the UIC function is enabled.  The purpose of using the UIC is to allow tracking of assets in units by any of the Army Tactical Command and Control Systems (ATCCS).  CBS provides information to a Run Time Manager (RTM) via a master Interface.

 

(SLIDE M1-24)  The ATCCS are composed of the following systems.

 

             MCS                                                          Maneuver Control System

             ASAS                                                        All Source Analysis System

             AFATDS                                                   Advanced Field Artillery Tactical Data System

             CSSCS                                         Combat Service Support Control System

             FAADC2I                                                  Forward Area Air Defense Command and

                                                                                Control Intelligence System

             AMDEWS                                                 Army Missile Defense Early Warning System

 

The ATCCS uses a UIC as the key field to track units and attributes associated with units.  Because the RTM obtains information from CSSTSS in linked exercises an implied task is to keep CSSTSS updated in a manner consistent with RTM.  The general guidelines are that information must represent ground truth as would be known by simulated units.  As well, information should only change in conjunction with actual changes as a result of operations, e.g., attrition, or operator decision e.g., cross leveling.

 

(SLIDE M1-25 & M1-26) Several definitions apply to the understanding of how UICs are used in tracking assets and units.  They are also important for the WS controller to understand in order to successfully work with the simulation when the tracking process is in use.

 

UNIT IDENTIFICATION CODE (UIC): A unique character string identifier specifying a set of assets of personnel, Class VII systems, supplies and/or aircraft.

 

UNIT:  An organization (ICON) with a unique name (Short Name) that has authorizations for and owns a specified set of assets (Stockage Objective) comprised of personnel, Class VII,supplies and/or aircraft.

 

             TASK FORCE: A temporary organization (ICON) with a unique name (Short Name)

             consisting of two or more units each with their own set of assets acting as a single force.

A Task Force must contain two or more UICs.  NOTE: A merge of two or more units with the same UIC results in a larger single unit with a single UIC.

 

             DATABASE UNIT: A unit that is read in from the database when the game is initialized.

 

NON DATABASE UNIT: An organization that is created in the course of the simulation.

 

             TEMPLATE:  A template specifies the structure to be contained in a non-database unit in

             terms of its authorized personnel, Class VII and supplies.  There are two “types” of      templates.

            

REF TEMPLATE (GENERAL): A template that is used to form a unit independent of UIC.

 

TFE TEMPLATE: A template that is used to form a unit that will have a Unit-UIC association (result of a merge of two or more units).

 

             INTEREST LEVEL: A UIC attribute that identifies how units may be tracked.  A

“interest level” of 0 indicates that U.S. Commanders are not interested in tracking the UIC, a level of 1 indicates U.S. Commanders are interested in tracking the UIC (usually with C4I devices).  An interest level of 2 is reserved for units that are neutral and which can be used either as 0 or 1.   NOTE:  The term “of interest to U.S. Commanders” is equivalent to “being tracked by unit C4I devices and/or CSSTSS and/or any ATCCS model interested in UICs”.  Interest levels may not be changed after initialization.

 

TASK FORCE STRUCTURE: A list of the Names and the Tic’s of the individual units that have been merged into a Task Force. Found on the Logistics Report.

 

(SLIDE M1-27 & M1-28)   The following concepts apply to tracking by UIC.

 

             -Tracking by UIC applies only to BLUFOR units.

 

-All BLUFOR units for which data is desired must be in the initial database.  A BLUFOR unit in the initial database is termed an “Original” or “Original Parent Unit” (OPU).  NOTE:  OPU identification numbers no longer appear on the Logistics Report.

 

             -All BLUFOR units in the initial database must have a unique UIC.  The UIC may be an

actual UIC or one that is developed for the unit.  Tracking of unit assets is then determined by its “interest level”.  

 

             -A unit may have only a single associated UIC

 

-A “Task Force” is the result of merging two or more units and must have two or more associated UICs.

 

             -UICs cannot be dynamically added or removed.

 

-Every UIC has one and only one reporting element.  A UIC will point to the unit that is its reporting element.  Example, a unit (one UIC) that is in the initial database is its own element.  If two such units are merged and then split, the child unit becomes its own reporting element.  In short, a unit that is an original unit remains the reporting element of resources associated with the UIC.

 

-If a unit that is the reporting element becomes wiped-out or a unit loses all resources of a UIC on which it was reporting, the reporting element is transferred to another unit that has resources provided by the involved UIC.  If no other unit has resources of the UIC, the reporting element remains with the unit that was the last to be wiped out.  A UIC list will remain associated with the wiped-out unit for the purpose of reconstituting the unit and UIC using magic supply.  

 

             -Units with different interest levels cannot be merged.

 

-In small standalone exercises or in an exercise where no UIC data is “of interest”, the UIC tracking can be disabled.  However, once it is turned off it cannot be turned back on.

 

-The reporting element may also be changed as a result of merge/split operations.  This will be discussed in detail later in this section.

 

(SLIDE M1-29) Tracked resources are divided into different elements.  All Resource Categories (RC) of BLUFOR units--personnel, class VII systems, consumable supplies and aircraft--will be tracked by UIC.

 

Logistics data is sent to the RTM by UIC via a Master Interface (MI).  The data sent consists of the following:

 

             UIC                                 The UIC owning the resource

             Resource Category          e.g. 155MM.HE.V

             On-Hand                         the on hand amount of a consumable supply.

For personnel, class VII and aircraft on-hand includes the persons/systems that will return from DS support facility.

                                                Operational              the number of systems ready in a unit. This value excludes systems/persons that are not ready due to being in a maintenance/medical facility.

 

(SLIDE M1-30) Gains and losses of unit assets are tracked by UIC.  The following changes will cause a unit’s assets to change.

 

             Split of a unit

             Merge of marginal unit(s) into a core unit

             Resupply gains

             Supply loss (from a supply center in an unlinked exercise)

             DS maintenance/medical gains and losses (in a unlinked exercise)

             Cross-leveling gains and losses

             Draw Supply gains

             Draw Supply losses (from a supply center in an unlinked exercise)

             Attrition losses

             Magic gains and losses.

 

If the unit whose assets are changing is associated with only one UIC, then the gains/losses are simple additions/subtractions.  If the unit is associated with more than one UIC, the gains/losses shall be prorated.

 

(SLIDE M1-31)  Because the RTM currently parses reports, and may continue to read CBS reports, UIC information must be included in selected reports.  As well, the RTM must be updated in a manner consistent with its updates.  Doing this will close the gap between the status of resources being reported by each of the systems.  It should help make unit status more real-time.  The following existing reports are affected:

 

             Split Unit Report

             Merge Unit Report

             Task Organization Report (This function is currently disabled)

             Returning Supplies to Furnishing Unit

             Unit Lift Request Report

             Fire Mission Target Report (UIC of firing unit)

             Logistics Report

 

(SLIDE M1-32)  For BIG BLUE type units, the following concepts apply:

 

Each BIG unit will have its own UIC.  Any pieces split from a BIG unit will keep that UIC but not be a reporting element.

 

             BIG units will be reported under their own UIC.  Data from Big units will not be passed             through the MI.

 

UICs split from a BIG unit may be reassigned to another UIC existing at initialization via the REASSIGN UNIT UIC order available on the Tech Control Workstation.

 

(SLIDE M1-33)  Unit structure may be changed via the Split order.  A Split must use a template to function.  There are two types of templates for this purpose.

 

TFE Template (Unit-UIC Template): A TFE Template has an associated UIC and is created through he execution of the work station menu order Merge Units with two units that have a single UIC.

 

General Template: A General Template does not have an associated UIC and is created by one of the following: 

 

                           REF Template (Database Generic Templates)

                           A template created using the Create Template order

                           A template created by the Create Template From Unit order

                           A template created using the Edit Template order

 

The most common exposure to the tracking by UIC function will be via the Merge/Split orders and the Logistics Report.

 

An additional order, the UIC Logistics Report, is new to the reports files and may be used to retrieve information of the logistics report type for specific UICs.

 

(SLIDEM1-34)  Merging units with UICs:

 

             -Results in creating a REF Template and TFE Template for the marginal units.

             -Establishes a Task Force.  The Task Force (core unit) will retain its UIC

and a Task Force Structure of all merging (marginal) units.  This structure appears on the logistics report of the task force.

-Merging units of the same UIC does not create a Task Force.  It creates a larger unit with a single UIC.

-Units must be of the same interest level to be merged.

             -Merging a unit into an existing Task Force adds to the Task Force and increases

             Task Force Structure.

             -Merging a Task Force into an original unit results in a new Task Force and the                                        Task Force Structure includes the name and UIC of the merging Task Force.

- Merging of two or more Task Forces results in a new Task Force with the combined assets of the merging Task Forces.   A Task Force Structure is created with the unit names and associated UICs of all involved units.

-Once a Task Force merges into another Task Force or unit, the merging Task force creates a TFE Template.  The Task Force Structure of the merging Task Force is inserted into the Task Force Structure of the core Task Force.  The component units in the Task Force Structure may be individually split out using their created REF Template if merged as an original unit or their TFE Template if a subordinate Task Force.

 

(SLIDE M1-35)  Merging UICs with an interest level of 0:

 

-A merge involving any combination of Task Force and/or units whose UICs have a level of interest of zero (0) results in a Task Force of the combined assets of all involved units/entities.  A Task force Structure will be developed.  WS controller should not experience any difficulties with this process.  There are no special restrictions with level 0 units since their resources are not tracked by UIC

 

-A unit whose UIC level of interest is zero (0) may be merged as a non-templated unit and will create a REF Template and TFE Template with a name of the merging unit.  Either template may be used to split out the merged unit using the appropriate split function.

 

(SLIDE M1-36)  The split of a CBS unit can be accomplished in one of five ways: 1) by proportion using a REF Template (general template), 2) using a Reference Template created via a merge, 3) by TFE Template for splits from Task Forces, 4) by a combination of Ref Template and TFE Template for splitting small elements from a Task Force and 5) by UIC.

 

The following concepts apply to splits of CBS units:

 

-Each unit split with a REF Template (general template) will generate a child unit with the parent units UIC.  Example, splitting platoons from a company.

 

-Each original unit split from a task force using the REF Template will have a single UIC derived from the resource categories allocated to that unit/UIC.  This REF template is the type that was created as a result of a merge.

 

-Splitting a task force using a TFE template will create the same unit as above for original units or it will split a subordinate TFE from a larger task force.  Example, when a merge occurs, both a REF and TFE template is created.  If the unit merged was a single UIC unit (original) it can be split using either the REF or TFE template field.  If the TFE template being used has subordinate TFEs, more than one UIC association, the TFE template may be used to split subordinate task forces from a larger task force by using the TFE template field.

 

-A split using both the REF and TFE template field is used to split small elements from an existing TFE.  Example, an Infantry company is merged into an Armor company.  This merge creates a REF and TFE template name.  If you want to split a platoon of infantry form the task force you use the combination for the split.  The REF template to use is a general template name, i.e., INF.PLT, and the TFE template name would be the name of the Infantry company merged into the Armor company.

 

-A “split by UIC” option is available on the Split Unit order.  If a valid UIC is entered in the “split by UIC” field, all of the parents resource categories provided by the UIC will be allocated to the child resulting from the split.  Example, splitting out a UIC of a merged unit from a Task Force.  This function must be treated with care.  Example, if you have split three STINGER Teams from an ADA unit and then merged them individually into a Task Force, a               “split by UIC” of these assets will cause all three teams to split out as an aggregate entity.  In a case when only one team is meant to be split, you can split by Name or Name and UIC.

 

-Splits may be rejected for all the normal reasons and in addition, when using the “split by UIC” function, the following will generate a rejection:

 

                           -Only one UIC exists in the unit

                           -The specified UIC does not exist

 

When a split is executed, the reporting element remains with the core unit involved with the split when the new child is an element of the original unit.  If the split involves two different UICs the reporting element reverts to the previous state.  Who becomes a reporting element is defined by the level the unit database was built at and what merges/splits are being conducted.  This relationship can be changed by executing the CHANGE UIC REPORTING ELEMENT order in the Task Organization orders tree.

 

(SLIDE M1-37)  Tracking resources associated with units/UICs and having an interest level of 1 are reported through the simulation to ATCCS by the unit that has status as a REPORTING ELEMENT.  If you are not sure of a unit’s status it can be found by requesting a UNIT IDENTIFICATION CODE LOGISTICS REPORT.  If a unit is built as part of the database with a UIC that has an interest level of 1 it will be a REPORTING ELEMENT. 

 

This REPORTING ELEMENT may be a company, battalion, etc.  Should this unit be merged into another, creating a Task Force, the core unit becomes the REPORTING ELEMENT. 

 

If the marginal unit is then split out, it will revert to being its own REPORTING ELEMENT.

 

Since most merges occur for task organization purposes the REPORTING ELEMENT concept is sound.  IF however, a non-original unit, i.e., one split from a BIG unit, merged into another and then split out, its reporting element would be the BIG unit.  The reporting element can be changed by executing the CHANGE UIC REPORTING ELEMENT order. Not keeping the reporting element structure aligned may cause some problems with which ATCCS boxes receive updates.  If, for instance, you merge an original unit into another thereby creating a Task Force and then split the marginal unit out, the reporting element will revert to the way it was at initialization.  If the split is to separate the units geographically but have them reported by the previous CORE unit, the CHANGE UIC REPORTING ELEMENT will have to be used.  There may be occasion that reporting elements are changed by split/merge operations or as a result of units becoming wiped out.  These specific cases will be discussed later.

 

(SLIDE M1-38 & M1-39)  These slides contain recommendations for SPLIT/MERGE operations in the workcell.  They may be attached to the WS wall or workstation table as a quick reference.  The recommendations apply to task organizing with elements less than the database unit level, i.e., platoons, sections and teams.  KEEP A RECORD OF WHAT YOU DO.  CONDUCT ALL POSSIBLE SPLITS/MERGES PRIOR TO STARTEX WHEN POSSIBLE.

 

(SLIDE M1-40)  This slide shows the format for the Split Unit order.  There are new entry fields for the section applying to TEMPLATE TO TRANSFER TO NEW UNIT.  The field titled REFERENCE TEMPLATE was previously known as TEMPLATE.  The REF template field is used to split out a small element from an original unit using a general template (database) or may be used to split an original unit from a task force.  The TFE TEMPLATE field is used to split a TFE from a task force. It can split an original unit from a task force or a subordinate task force from a larger task force.  BY UIC is used to split as assets of a single UIC from a task force. A combination of the REFERENCE TEMPLATE plus TFE TEMPLATE may be used to split a small element of a TFE from a task force.

 

(SLIDE M1-41 thru M1-47)  The following slides are examples of split operations using REFERENCE TEMPLATE to split small elements from original units.  This represents the first steps in task organization.  This is the simplest function to accomplish using the new Split Unit order.

 

(SLIDE M1-48 thru M1-56) The most common report you will encounter that will reflect UIC information is the Logistics Report.  The order has not changed since the last version but bears reviewing.  The following slides are examples of logistics reports.  Each set of slides reflects information for that particular logistics report request.

            

(M1-49 & M1-50) A standard log report for a battalion (original unit).  The UIC appears next to the unit name.  The unit asset status sections have not changed.

(M1-51 & M1-52)  A standard log report for a company (original unit).  The UIC appears next to the unit name.  The unit asset status sections have not changed.

(M1-53 & M1-54) A standard log report for a battalion (original unit) with BREAKOUT BY UIC.  The UIC appears next to the unit name.  Unit status sections have not changed.  The BREAKOUT BY UNIT IDENTIFICATION CODE section lists the UIC that is reported by this unit and the original unit name.  Unit status sections have not changed with the exception that DISMOUNTS do not appear as combat systems.

(M1-55 & M1-56) A standard logistics report on an original unit with breakout by UIC and rollup.  The unit UIC appears next to the unit name.  The asset status sections have not changed.  The asset status sections in the breakout by UIC section has not changed with the exception that dismounts are not shown as a combat system.  The rollup section of the logistics report reflects the unit type, subtype, location and UIC of the headquarters unit and its subordinates.

 

(SLIDE M1-57)  Merge operations with UICs will change the appearance of the logistics report and provide additional information about the units involved.  The MERGE order has not changed however, the TEMPLATED UNITS SECTION OF THE ORDER SHOULD NOT BE USED WHEN USING UICs.  In this example, A/2-73INF has been merged into its battalion, 2-73INF.

 

(SLIDE M1-58 & M1-59)  These slides depict the standard logistics report with breakout by UIC and rollup.  As a result of the merge A/2-73INF has created a REFERENCE and TFE Template Name.  A/2-73INF has become a TFE of 2-73INF.  The UIC of the core unit, 2-73INF, appears next to the unit name.  A new element has been created titled Task Force Structure.  This element replaces the previous element titled Unit List.  Note that the Task Force (TF) (Core Unit) name appears with its UIC and the merged unit is indented by two spaces, as it would appear on an OPORD reflecting the task organization.  The unit asset status sections have not changed.  The breakout by UIC section reflects the UIC of the TF headquarters unit, 2-73INF and the UIC of merged unit, A/2-73INF.  The rollup section has no changes.

 

(SLIDE M1-60 & M1-61)  These slides depict a standard log report on an original unit.  Again, with the exception of the UIC appearing next to the unit name there are no changes to this report.  There are no changes to the unit asset status sections.

 

(SLIDE M1-62  & M1-63)  This is another example of a standard logistics report on an original unit with breakout by UIC and rollup.  The information in the unit specific data section is the same as previous slides.  There are no changes tot he unit asset status sections.  There is not difference in the breakout by UIC section from other examples shown.  The rollup section is not changed except that the unit UIC appears next to the unit name.

 

(SLIDE M1-64 & M1-65)  These slides show additional merge operations as we continue to build a TF.  Again, each of the marginal units merged using the NON-TEMPLATED UNITS section will create both a REFERENCE and TFE Template.  The two platoons merged into B/2-73INF have become TFEs of this small TF.  Continuing to task organize, the small TF B/2-73INF is then merged into its battalion.  When this merge occurs, a TFE template is created for the task force that may be used to split TF B/2-73INF at a later time.  B/2-73INF CANNOT be split using a REFERENCE template as an original unit because he is a small TFE of the 2-73INF.  A REFERENCE Template (database template) TFE Template can be used to split a small element of B/2-73INF.  These splits will be discussed later in this section.

 

(SLIDE M1-66 & M1-67)  These slides reflect a standard logistics report on a TF.  Changes occur on a logistics report due to any merge operations.  The logistics report now shows additions to the Task Force Structure due to the last merge.  In this example, both A/2-73INF and B/2-73INF are TFEs of 2-73INF.  B/2-73INF also has subordinate TFEs that carry forward.  Note that the subordinate TFEs of B/2-73INF appear indented by two spaces in the Task Force Structure.  The unit asset status sections have not changed.  The breakout by UIC section now has an entry for each unit within the TF beginning with the core unit.  There are no other changes to the appearance of the logistics report in the rollup section.

 

(SLIDE M1-68 thru M1-70)  These slides are examples of continued task organization using the merge order.  First, a small TF is created by merging two (2) ADA sections and an MP platoon into a MECH platoon.  Each of these marginal units becomes a TFE of the created TF as a result of the merge.  Second, we merge TF 1/A/1-8MECH into B/2-72INF (an original unit) creating a larger TF.  This merge causes a TFE Template to be created for 1/A/1-8MECH that contains the assets of his task force.  Third, we merge TF B/2-72INF into TF 2-73INF.  This creates a larger TF 2-73INF as well as creating a TFE Template for B/2-72INF.

 

(SLIDE M1-71 & M1-72)  These slides reflect changes to the logistics report for TF 2-73INF resulting from the last merge operations.  Again, note the Task Force Structure has changed.  TF B/2-72INF appears as a TFE of TF 2-73INF.  Under B/2-72INF appears a subordinate TFE, TF 1/A/1-8MECH, previously merged into B/2-72INF.  Under TF 1/A/1-8MECH three subordinate TFEs appear.  TF B/2-72 has been indented by two spaces because it is a TFE of 2-73INF.  TF 1/A/1-8MECH has been indented an additional two spaces because it is a subordinate TFE of B/2-72INF.  The three units merged to create TF 1/A/1-8MECH have been indented two additional spaces because each is a TFE of TF 1/A/1-8MECH. The unit asset section has not changed.  The breakout by UIC section has changed to reflect new units in the task force.  The rollup section has not change from previous examples.

 

(SLIDE M1-73 & M1-74)  These slides depict merging two (2) ADA sections into the 500EN.BN (an original unit).  This results in the creation of TF 500EN.BN.  The two (2) ADA sections become TFEs of TF 500EN.BN as a result of the merge.  The second merge operation involves merging TF 2-73INF and TF 500EN.BN along with A/1-8MECH.BN and A/1-68AR.BN (original units) into 3BDE21.  You may recall that a platoon was previously split from the original unit A/1-8MECH.BN.  Although this split was executed, for purposes of merging and possibly splitting this unit out at a later time, it is still considered an original unit because it has only one associated UIC.  The second merge creates a larger TF.  The four (4) marginal units become TFEs of TF 3BDE21 and create different templates as a result of the merge.  The two (2) TF units create a TFE Template.  The two (2) original units create both REFERENCE and TFE Templates. 

 

(SLIDE M1-75 thru M1-77)  These slides will provide an example of changes to the logistics report as a result of the last merge operations.  Note that the changes to the Task Force Structure updates to include the new TF.  The two (2) original units and the two (2) Task Forces merged into the TF 3BDE21 are indented two (2) spaces.  They are TFEs of TF 3BDE21.  In the case of TF 2-73INF, the alignment of the subordinate TFEs has been changed.  Since TF 2-73INF and TF 500EN.BN ARE no longer TF headquarters, each of its subordinate TFEs and task forces has been indented an additional two (2) spaces.  The unit asset section has not changed from previous examples.  The breakout by UIC section has been updated to include the units now merged into TF 3BDE21.  The rollup section HAS changed as a result of this merge operation.  Note that all subordinate units of 3BDE21 are reflected in the rollup section.  As well, note the three (3) subordinate units of the 500EN.BN have also been added to the list of subordinates.  This change occurred when 500EN.BN merged into 3BDE21.  The units appear as subordinates of TF 3BDE21 but remain their own reporting elements.  As well, their maintenance ands medical support units do not change.  This may create confusion however because the assets of the three companies will appear in a rollup logistics report for TF 3BDE21.   Any user using a rollup log report for purposes of reporting unit status or requesting resupply and replacement personnel or equipment may have problems determining what is accurate.  In this case, the best action to take would be to request a UNIT INDENTIFICATION CODE LOGISTICS REPORT (UIC Log Report).

 

(SLIDE M1-78 & M1-79)  These slides are examples of a UIC Log Report.  The unit specific data section provides the same basic information as a standard log report.  The additional information pertaining to the reporting element is associated directly to the UIC.  For a report on an original unit, there are no changes to the unit asset section of the report except DISMOUNTS are not shown as a combat system.  This is consistent with a standard log report with breakout by UIC.  For purposes of understanding, the asset section is a rollup of all equipment associated with the UIC. 

 

(SLIDE M1-80 & M1-81)  These slides show a UIC logistics report with breakout yes.  Note the UIC belongs to a unit that was previously split.  Its child unit was merged into another task force and then the parent unit was merge into a task force.  The breakout section identifies what units have resources of the UIC.  Because the company is merged into the brigade, the brigade is reported as having the resources.  The platoon is reported because it is a TFE of a TF that is merged into the brigade.

 

(SLIDE M1-82 thru M1-84)  The following slides are examples of what changes when a split occurs from a task force.  In this case, A/1-8MECH.BN, an original unit at the time it was merged, is being split from the TF 3BDE21.  The logistics report for the unit after the split is straightforward and indicates the 3BDE21 as the senior headquarters, medical, maintenance and air maintenance support units are aligned with the senior headquarters as in any other split.  The UIC logistics report indicates the reporting element is the same as the senior headquarters.  This is due to a child unit of the UIC remaining in a TFE that is merged into 3BDE21. 

 

(SLIDE M1-85 thru M1-87)  The following slides are examples of what results from a TFE split.  In this case, B/2-72IN was a small task force that was merged into 3BDE21. Note that when using a TFE Template split function, the new unit’s name cannot be the same as an existing TFE Template name.  The logistics reports looks like any other except it has a task force structure of its own.  As indicated, the unit is still a task force with a TFE containing sub-TFEs.  The UIC logistics report indicates B/2-72IN is the reporting element for resources of A/1-8MECH.BN.   Since TF B/2-72IN was the last unit split from TF 3BDE21 and it has resources in its TF belonging to the UIC for A/1-8MECH.BN, it is now the reporting element for the UIC. 

 

(SLIDE M1-88 thru M1-90)  The following slides are examples of the result of using a combination REFERENCE and TFE Template to split a small element from a task force.  In this case we must specify both templates in the order.  The logistics report indicates the higher headquarters is the 3BDE21 even though it was split from a TFE B/2-73IN.  The TFE B/2-73IN was merged into 3BDE21.  The UIC logistics report for those resources reflect the same information.  3BDE21 is the reporting element.  Both the 3BDE21 and the new child unit contain resources of the UIC.

 

(SLIDES M1-91 thru M1-93)  The following slides depict the changes resulting from a split BY UIC operation.  Note that all resources belonging to the UIC will split into the new child unit with a new name.  The core unit will not have a task force structure after the split.  The unit logistics report looks as it would if it were an original unit.  The UIC logistics report indicates B/2-72IN as the reporting element.  This occurs because the split was the last action taken involving the UIC of the child unit.

 

(SLIDE M1-94)  Task organizing with aviation units is accomplished in the same manner as with any other maneuver unit.  When a unit owning aircraft is merged into another unit for any reason, the aircraft merge as part of the unit and are associated with the units UIC.  In such cases, the core unit becomes the home unit for purposes of creating teams and flying missions.  RW reports taken on the core unit will reflect the unit as not having any aircraft.  Logistics reports will contain an aircraft status section for the original owning unit.  UIC logistics reports will have an aircraft section for the original owning unit.  In some databases, the resources for FARPS are contained in the battalion.  If this is the case these assets will have to be split from the battalion before anything is merged in the battalion.  If this step is missed, the battalion can temporarily be merged into another unit and the FARPS can be split from the battalion using the REFERENCE and TFE Template process.  If this step is not taken, all units merged into the battalion will have to be split out before a split of the FARPS can occur.

 

If the original unit owning aircraft are split from the battalion the aircraft will split out  with the original owning unit based on UIC association

 

If an RW Subunit/team is created and sent to a forward operating location/farp, the aircraft can operate from that location.  If damage is taken the farp and pilots are lost while crewing is enabled and minor problem may occur if the team is cancelled for any reason.  When this occurs, those aircraft that can be crewed will return to their original home unit.  Those aircraft that cannot be crewed and any remaining pilots will become part of the farp and will appear on logistics and RW Reports.  Adding the quantity of crews that are short by a merge or by using the Change Auth/on Hand order will allow the operator to fly the aircraft from the farp and change their home unit to their original unit of ownership.

(SLIDES M1-95 & M1-96)  These slides are an example of a standard log report with breakout by UIC for an aviation unit.  Note that an additional section “Status of Aircraft” appears at the bottom of the logistics report.  No other changes appear in this report.

 

(SLIDES M1-97 & M1-98)  These slides are examples of a standard log report with a breakout by UIC after a merge has occurred.  Note that in this case the Status of Aircraft section still appears on the report for the UIC that has aircraft associated.  An RW Report on the core unit will not reflect any aircraft because they are not associated with the core units UIC.  An RW Report for the original unit will reflect the aircraft information.

 

(SLIDE M1-99)  SUMMARY.  In this section we have discussed unit organization, how to prepared for unit organization, the steps to use in both the standalone version and when using UICs and some peculiar anomalies for aircraft.

 

Complete the M1 HANDS on TRAINING section, which is designed to familiarize the user with using these orders.

 

VOLUME 2

 

SECTION 2

 

UNIT MISSIONS

2.1        INTRODUCTION  (SLIDE M2‑1) In order to execute player orders, workstation controllers are required to move and fight forces assigned to the workstation.  This section explains how to use the appropriate CBS orders to accomplish these tasks.

            

             (SLIDE M2‑2)  To this end, the following will be examined:

                                               

                                                GROUND MOVE

                                                STANDARD ROUTES

                                                UNIT MOVEMENT REPORT

                                                CHANGE UNIT SPEED/MOVEMENT ATTRIBUTES

                                                RECONNAISSANCE

                                                GROUND ATTACK

                                                MASS OPERATION/FIRE MORTARS

                                                CHANGE TACTICAL OPTIONS

                                                DEFEND

                                                COMBAT POWER DISTRIBUTION

                                                UNIT DEPLOYMENT

                                                COMBAT REPORT

                                                CONTACT REPORTS

                                                WITHDRAW

                                                OFF-LOAD SUPPLIES

                                                OCCUPY PDP

                                                ON ORDER OBSTACLE EXECUTION

                                                CHEMICAL

                                                CREATE MANEUVER AREA

                                                MANAGE MANEUVER AREA

                                                CHANGE MANEUVER OPTIONS

                                                DISPLAY LINE OF SIGHT

 

2.2        UNIT MOVEMENT  (SLIDE M2-3) A unit may be moved by using the GROUND MOVE order.  Units move in the simulation and on the monitor using short, incremental steps, called mini-steps, of a database defined length.  If the AUTOMATIC REFRESH is on, the units will move on the screen with each mini-step without a redraw of the screen being required.

 

             As the CBS orders are discussed, notice that many orders require the same information. Each field entry is discussed in detail the first time and then passed over when it appears again.

 

             The fields in the GROUND MOVE are:

 

            UNIT:  Enter the unit to be moved.  Use MAP INPUT, LIST NAMES, or FIELD HELP to complete the field.

 

           ADD on: Enter "yes" if this move is to be added to an existing move; "no" if this is a new move.  If "yes" is selected, ensure the new LOCATION LIST starts at a point beyond the last point in the unit's current LOCATION LIST.  If not, the unit may "back up."  While the order provides an option to ADD on to an existing move, its use is not recommended due to the potential for error.  One method is to fill out a completely new move order or change the parts that need to be changed and then send the order.  Another method which may be use is to send a DEFEND order to stop the unit and then issue a new GROUND MOVE.

 

            DIRECTED:  The default is "yes".  The unit will to use the most direct route between points on the LOCATION LIST if the move is cross-country.  If “on road” is selected, the unit will follow the road if all route points are on the road.

 

            POSTURE:  The choices are "Moving" and "Move To Contact."  Use "Move" for administrative moves or enter "Move To Contact" when the possibility of enemy contact exists.  While "Move" is faster and less vulnerable to indirect fire than "Move To Contact", you should select the posture that is consistent with your mission or the tactical situation to maintain realism.

 

            MODE OF MOVEMENT: Select either CROSS COUNTY or on ROADS to replicate the type move the unit is conducting.  ON ROADS is the default. 

 

            CBS models congestion.  A unit moving on ROADS will experience a congestion delay based on other road traffic, the throughput capacity of the type road and the presence/absence of an MP unit (traffic control point).  To eliminate the impact of congestion, stop all units in congestion and then restart the priority unit.  The presence of a traffic control point (MP unit) along the route (On Road movement only) will also facilitate unit movement by increasing road throughput.

 

            Units moving CROSS-COUNTRY do not congest each other nor does the presence of MP units influence the unit.  ON ROADS and CROSS-COUNTRY traffic will not congest each other.

      

            MARCH INTERVAL: Enter the meter interval between vehicles.  If you do not enter an interval, the database defined default interval is used.  The interval affects the speed the unit may obtain, congestion, and the unit’s vulnerability to blast munitions.

 

            MAXIMUM SPEED: The MAXIMUM SPEED at which a unit can move is determined by the speed of the slowest combat or combat support system in the unit and road and terrain conditions.  The MAXIMUM SPEED specified in the order acts as a speed limit, precluding the unit from moving faster than specified.

 

            START TIME: Enter the start time to schedule future moves.  If left blank, the unit will begin to move immediately.

 

            AVOID COMBAT: Check the box to place a unit in AVOID COMBAT (Unit background will turn yellow).  This option enables company size or smaller units to attempt to move past enemy units within weapons ranges while minimizing the probability of detection.  This capability may be used by units during reconnaissance missions or for units that are performing outpost type operations during which they do not intend to engage the enemy.

 

            The probability of detection of a unit is based on such factors as the sensors of the detector, the detectee’s unit type and subtype, posture, size, its avoid combat or infiltration status, the presence of vehicles, day/night conditions, terrain and distance.

 

            ROUTE RECON TYPE: HASTY ROUTE, ROUTE, HASTY MLC or MINEFIELD are the options.  The unit will slow down while conducting the recon.  (See discussion under the reconnaissance paragraph.)

 

            MOVE UNDER FIRE: The options are "yes" or "no" with yes (box checked) as the default.   If "yes" is entered, the unit will attempt to continue to move although it is taking fire from an enemy.  If "no" is entered (box not checked), the unit will stop and assume the Defend posture when it takes fire from an enemy.

 

            MOPP STATUS: Five choices are available. Use List Names to enter one of the choices. If left blank, the unit will remain in its current MOPP level.  MOPP levels are discussed in detail in the chemical section.

 

            HASTY BREACH: Allows the unit to conduct a breach of an obstacle without using the Engineer Task order.  The options are None, Bull Through (OPFOR only) or In Stride. 

                                                           

                                    MINIMUM LANES: Is used in conjunction with the Hasty Breach options and tells the unit the number of lanes to clear if it is to conduct breaching operations.  The default is one for IN STRIDE.  The more breaches that are cleared the faster the unit will pass through the obstacle.  However, the more breaches that are built, the longer it takes to emplace the breaches.

 

                                    ASSEMBLY AREA: Use Yes if the unit is to occupy an assembly area at the end of its move.  This field is used by OPFOR and is only necessary when TACSIM is used as the intelligence driver for an exercise.  The default is no.

            

             RECON RADIUS: Enter the radius to be used in recon in KM.

 

             DEPLOYMENT:  Options are vee, wedge, line, column and echelon left or right.  These options specify the template to be used to position the clusters of this unit for the purpose of detection of and by infiltrators and for the purpose of determining limits on unit speed due to terrain and obstacles.  There is no default for the field.

 

             FRONTAGE:  Specify the width of the unit in meters.  If deployment is column, the frontage is forced to a calculated frontage of       approximately 3 meters.

 

             DEPTH:  Specify the depth in meters.  If column is selected, the depth is calculated by the simulation.

 

             METHOD:  Select IMPLICIT or EXPLICIT with IMPLICIT as the default.  This selection determines which one of the two speeds is used to determine the speed of the unit.  (The two options are explained later.)

 

             BYPASS ECHELON:  The bypass echelon stipulated by a controller is the highest PE (Platoon Equivalent) echelon of enemy units that will be attempted bypass.

 

             BYPASS UPON DET:  If set to YES, unit will bypass detected units even if they are beyond the bypass radius.  Bypass radius in a database controlled distance.  The default setting is NO unless otherwise stipulated.

 

             LIMIT SHOOT-FIRST:  If  YES , the Controller wishes to hold fire until an enemy is within a certain distance.  The distance is in kilometers.  The default is set for NO if not otherwise stipulated.

 

             SHOOT-FIRST RANGE:  Is the range, in kilometers, at which the tasked unit will initiate combat, unless the enemy shoots first (in which case the unit will return fire).  A value of 0.0 means never shoot first.

 

             LOCATION:  Enter a grid location or standard route name.  Entries can be in UTM or LAT/LONG.  Use MAP INPUT to make entries.  Standard Routes are discussed below; however, Standard Routes can be used in lieu of UTM coordinates on any ground move.  

 

             USE MANEUVER POLYGON:  Enter YES or NO to specify whether the unit’s attempts to maneuver around enemies should be bounded by the maneuver area names selected.  A unit currently bounded can have those bounds removed by an entry of OFF.  It is important to note that created maneuver areas (discussed in detail later) do not have any affect on  a units movements if there is no enemy within bypass detection distance.  In other words maneuver areas only take effect when a unit is in an “automatic” motion in attempt to bypass enemy unit/s.  Otherwise the unit will move through maneuver areas as directed by the controller.

 

             MANEUVER AREA NAMES:  Is a list of name/s that define the polygon/s that bounds the movement of the unit when it is attempting to bypass an enemy. 

 

             (SLIDE M2-4)  The topics shown on this slide affect unit movement in CBS.

 

             Cross-country movement is affected by the type of movement and by the unit deployment.  The controller may specify either implicit or explicit movement with implicit being the default value on the menus.

 

             The polygons affect movement depending on whether the movement is cross-country or on roads.  For on ROADS, the trafficability polygons affect the speed along with the size of the road.

 

             On roads movement always defaults to column.  A good indicator that the unit is moving on roads is that no deployment should show graphically as the unit is moving.  If a deployment is showing, the unit is moving cross-country and not on roads.

 

             The military load class (MLC) function has been implemented.  Each vehicle and each bridge has an associated MLC.  A unit movement will be canceled if a unit attempts to cross a bridge with a vehicle with a MLC greater than the bridge MLC.

 

             Slope coupled with vegetation affects the speed of cross-country movement.

 

             Congestion may be a factor for units traveling on roads.

 

             (SLIDE M2-5)  Cross-country movement is affected by slope, unit formation, vegetation and urbanization.  The four types of vegetation are barren, sparse, moderate and dense.  The degree that vegetation and slope affects movement is determined in lookup tables in the database.  The tables contain speed reduction factors for troops, wheels or tracks based on the slope and level of vegetation.

 

             Slope is not displayed on the monitor.  To determine the slope in an area, use the Map Recon Trafficability report.  It will show the slope between two points that have been entered in the menu.  This report is discussed in the reconnaissance section.

 

             The presence of any level of urbanization slows a moving unit.

 

             There is no congestion associated with cross-country moves.

 

             Database values are used to compute speed based on the slowest moving vehicle in the unit and the above factors.

 

             (SLIDE M2-6)  As stated, there are two types of movement: implicit (the default) and explicit.  These are specified in the movement menu by the controller.

 

             Interactions with engineer obstacles are the same for both types.

 

             Unit speed calculations are different depending on the type movement selected.  In either case, the polygons and deployment have an affect on the speed on the unit.

 

             (SLIDE M2-7)  Unit deployment/formation affect the ability of a unit to move about the battlefield and the speeds that may be obtained.  Deployment is also used in the detection of and by infiltrators.

 

             Units may deploy in a selected formation with a user-specified frontage and depth.  CBS uses this information to affect movement.  It breaks the unit into three sub units or clusters for deployment purposes.  For example, a battalion is broken down into three deployed clusters that simulate the three deployed companies of the battalion.  Likewise, a company is broken down into 3 clusters that simulate the 3 platoons of the company.  As a unit moves, the clusters are used to determine what polygon is affecting the unit.  The direction toggle must be on to see the deployment graphics.  The deployment for a column is not displayed.

 

             COBRA does consider deployment and determines the degree to which a unit may be crowded.  This determination can affect the speed the attacking unit moves, its target acquisition capability and the amount of damage that may be assessed.  Thus it is wise to keep the frontage of a unit about twice the unit radius to preclude crowding.

 

             (SLIDE M2-8)  This slide shows a deployed unit moving cross country that has one cluster in moderate vegetation, one in sparse vegetation and one in water. 

 

             Accordingly, its speed for implicit movement is the average speed of the three clusters’ computed speeds or in this case, 23.3 KPH.  This is based on the assumption that the unit would not go into the moderate vegetation or the water.  Rather, it would skirt these obstacles, narrow down the unit frontage and proceed at a slower speed.

 

             The speed calculation for explicit is based on the speed calculated for the cluster in the slowest polygon.  In this case, the unit would stop since a cluster has encountered water.

 

             The speed of a unit is based on the maximum attainable speed of the slowest vehicle class in the unit and then reduced based on the other factors.

 

             (SLIDE M2-9)  Pucking for on road movement is critical and should be accomplished as show on this slide.  If the puck point is on the road, the grid location in the top right side of the TV screen will turn red.

 

       Puck the first location on the road very near the present unit location.

 

             It is advisable to puck between road intersections, but do not puck on a road intersection.

 

             Do not skip past a second road intersection.  If you do so the unit will move cross-country to the puck location.

 

             (SLIDE M2-10)  This slide illustrates how to move a unit on roads based on deployment of a unit.  Note how the deployment is affected as the unit moves on and off roads.

 

             (SLIDE M2-11)  This slide provides another example of on road movement.

 

       (SLIDE M-12)  This slide shows an example of a unit that encounters a bridge.  To use the bridge, the unit must have its center of mass within a database-defined distance of the bridge.

 

             (SLIDE M-13)  Units moving on a road may bypass a point obstacle in their path if there is passable terrain on at least one side of the road.  They suffer a delay to accomplish this maneuver.  If both sides of the road are impassable, and the unit has the capability to breach the point obstacle, it attempts to do so.  If unable to breach the obstacle, the move is canceled and a report is sent to the workstation.

 

             (SLIDE M2‑14)  There are serious constraints imposed on units in an AVOID COMBAT status.

 

             Avoid Combat is used for company or smaller size units only.  When in Avoid Combat, the unit icon background turns yellow, and the unit moves at a slower speed than normal.  The unit will also suffer higher fatalities than a similar unit that is not in AVOID COMBAT.

 

             A unit in AVOID COMBAT can not evacuate its wounded to a hospital (they die) or its equipment to maintenance (it is abandoned).

 

             If an AVOID COMBAT unit is detected, its background "goes white" just like any other unit in contact.  Its AVOID COMBAT status will be eliminated automatically and the unit will engage in combat as any normal unit. 

 

             (SLIDE M2-15)  Obstacles which are encountered may delay or stop a unit depending on the type move the unit is conducting. 

 

             Shown here is an example of a unit encountering an enemy minefield with in stride breach set to none.  Accordingly, the unit would stop.  Note that the minefield is multi-segmented but all that is seen on the monitor is a black dot surrounded by a circle.  A minefield reconnaissance must be accomplished to see the complete enemy minefield graphic.  (See minefield reconnaissance section)  (A friendly minefield will have the entire minefield shown when encountered by a friendly unit.) 

 

             If in stride breach is set to something other than none, the unit will conduct breaching operations (if capable) at the location that the cluster hits the minefield.  In this case, it would breach the width of the minefield.

 

            (SLIDE M2-16)  These are the results when breaching operations are selected:

 

                                    If In Stride is selected, the unit will immediately use its available assets to begin breaching the obstacle.  The unit will clear a lane(s) using whatever breaching assets it has available with the most efficient being employed automatically.  If no breaching assets are available, it will use a squad-size element to clear a lane by hand.  (See the Engineer Section in this volume for more details on breaching operations.)

 

             If Bull Through is selected, the unit will force its way through the obstacle, not clearing a lane as it does so and will suffer casualties in doing so.  Generally, this is not an option for a ground move.

 

             If None is selected, the unit will stop and report the obstacle when it encounters an obstacle.  The controller must then issue new orders for the unit. If a unit encounters a minefield, the unit will take casualties unless there are friendly lanes, the minefield is a surface laid AT or unless the unit is conducting a route recon of any type.

 

             STANDARD ROUTES  (SLIDE M2-17) This function allows the user to input routes which may be used as MSRs for ground workstations or as ingress and egress routes for TACAIR and ARMY AVIATION workstations.  Five STANDARD ROUTES orders are found under the STANDARD ROUTE ORDERS hierarchy.  These orders are: CREATE STANDARD ROUTE, DELETE STANDARD ROUTE, UPDATE STANDARD ROUTES, DISTRIBUTE STANDARD ROUTES, and STANDARD ROUTE REPORT.

 

             MP units may assist in the control of units/convoys moving throughout the battlefield by reporting units/convoys that pass through a specified checkpoint.  To use this capability, a standard route with established checkpoints must be used by the moving unit/convoy.  The MP unit must be within a database defined distance from the checkpoint.  If these conditions exist, the MP unit will send a report to the MP workstation and the unit/convoy workstation.

 

             Any workstation can be designated as a "global" workstation by the technical control staff.  Once designated, this "global" workstation can create, distribute and delete global routes.

 

             (SLIDE M2-18)  The CREATE STANDARD ROUTE and DELETE STANDARD ROUTE orders behave in much the same way as CREATE and DELETE LINES.  Enter the name of the route, the type of route: MANEUVER, TACAIR, or RW (rotary wing), and whether it is a LOCAL ROUTE, or if a SENIOR CONTROL workstation, a GLOBAL ROUTE.  Use MAP INPUT and create a line by "pucking" each UTM point along the desired route.  Remember, just as in CREATE LINES, the route is not created until the SELECT/SEND ORDER key is pressed. 

 

             Standard routes are type specific.  RW Standard Routes can only be used in pure Rotary Wing orders, TACAIR Standard Routes can only be used in pure TACAIR orders and Maneuver Standard Routes can only be used in pure Maneuver and Ground Logistics orders.

 

            BLUFOR workstation routes will be displayed in blue and OPFOR workstation routes will be displayed in magenta. 

 

             Whenever a standard route is created, a mirror image of that route is automatically created.  This mirror image is the exact reverse of the route created by the controller and can be used for egress by placing a minus (-) sign in front of the route name in the location field.  Multiple standard routes may be used in a move order (or any order allowing the use of standard routes); however, the combined number of route points cannot exceed 100. 

 

             Once a standard route has been created, it may be used in any order that allows the controller to choose the route.  The Standard Routes option can be used at any time within the route list.  For example, the first route point may be a grid coordinate and the second route point can be the name of a standard route.  The third route point, for example, could be another grid coordinate or it could be another standard route.  Remember, the unit will enter each route at the beginning and will traverse the entire length of the route and will exit at the end of the route.

 

             UPDATE STANDARD ROUTES has the same functionality as "refresh screen."  When new routes have been distributed by Senior Control, enter the STANDARD ROUTE type: MANEUVER, TACAIR, RW in the field and strike the SELECT/SEND ORDER key and the appropriate standard routes will be updated.

 

             (SLIDE M2-19)  This slide illustrates how to puck a standard route to ensure that the route follows the road.  If standard rules for pucking an on road route are used, the unit will follow the roads but the standard route will be drawn as a straight line between puck points.

 

             DISTRIBUTE STANDARD ROUTES is a SENIOR CONTROL or designated "Global" Workstation function only.  After Global Standard Routes have been distributed by a designated workstation, a message will appear across the top of each monitor in the workstation(s) that was designated to receive the Global Standard Routes asking for the controller to use the UPDATE STANDARD ROUTES order.  When the message is received, the controller should enter the UPDATE STANDARD ROUTES order, select the type of standard routes to be updated (TACAIR, RW or Maneuver) and send the order by pressing the SELECT/SEND key on the function keypad.

 

             The Senior Controller or the OIC of the designated global workstation should make an announcement on the loudspeaker that global standard routes have been distributed and that each controller should use the procedures outlined above. 

 

             STANDARD ROUTE REPORT allows the workstation controller to recall a STANDARD ROUTE for the purpose of reviewing the route points.  The type of route and the route name are entered in the appropriate fields and when the order is sent, the controller is able to see on his monitor the entire route list for the designated route.  Pressing the PRINT KEY on the function keypad may print the Route List.

 

             (SLIDE M2-20)  The MOUNT/DISMOUNT menu is used to dismount or remount dismounted troops for a mountable unit when the unit is not in conflict.  If the unit is ordered to mount while it is moving, the unit will experience a database-determined delay before it will move at mounted speed.

 

             Once a mount/dismount order has been sent to the simulation, a spot report is generated and sent to the workstations to verify the mount/dismount status.

 

             (SLIDE M2-21)  The SITUATION report shows the mount status of the unit.

 

             UNIT MOVEMENT REPORT  (SLIDE M2-22) once the unit is on the move, it is wise to get a UNIT MOVEMENT REPORT using the SUMMARY REPORTS order.

 

             The "Time" is the current game time.

 

             The "Actual Speed" is the speed that the leading element of the unit is traveling in KPH.  This speed is based on the unit, terrain conditions, presence of MPs, if applicable, and any congestion caused by moving units or convoys in front of the unit.  This speed can never exceed the Requested Highway Speed.

 

            The "Maximum Speed" is the speed requested by the unit commander and acts as a speed limit for the unit.

 

             "Sr. Cont. Maximum Speed" is a speed limit imposed by the Senior Controller on the unit.  The unit can not exceed this speed.

 

             “Sr. Cont. Minimum Speed” is a guaranteed minimum speed that is set by Senior Control.  This speed acts as a guaranteed minimum speed for the unit generally overriding all other speed constraints.

 

             This Unit Minimum Speed is the slowest speed the unit will move thus effectively removing the effects of terrain, road size, and congestion.  It takes effect the next instant the unit’s speed is calculated and applies only to the current move or to the next specified move if the unit is not moving when the Unit Minimum Speed is set.

 

             The Unit Minimum Speed will only last during the current move or for the duration of the next specified move if the unit is not moving when the Unit Minimum Speed is set.  A change to the unit posture from the current or next movement posture ends the Unit Minimum Speed.  Thus, if a unit is moving and receives a minimum speed change, it will have the minimum speed applied to its current move.  If the moving unit defends and then starts a new move, the minimum speed will not apply.

 

             “Requested Mode of Movement" indicates the mode of movement requested by the controller in the movement order.

 

 

             The "Last Reported Position" is the position of the leading element.

 

             The "Next Position" is the route point where the unit will move.

 

             The "Final Destination" is the last point specified in the movement order.

 

             The "Estimated TOA of Trailing Element at Location of Leading Element" indicates how far (in time) the trail element is behind the lead element.  Compare this time with the TOA at the last reported position to determine the amount of trail delay. 

 

             The unit icon represents the leading elements of a moving unit.  A unit may spread out over a long distance creating what is called "trail delay".  The Per Cent of Unit at Location of Leading Element is that portion of the unit that is located where the unit's symbol is located.  This data is found in the header section of the LOGISTICS REPORT.  For example, if the Per Cent of Unit at Location of Leading Element equaled "25", there would be 25% of the Light Trucks, 25% of the Dismounted Infantry, 25% of the ammo, 25% of the food, etc., located at the leading element’s location and 75% of the unit would be spread out in the trail element.  Depending on the march interval, this trail delay can spread over a long distance and thus generate congestion with follow on units.  Additionally, it affects how much of a unit is available for direct fire combat if a unit comes into conflict with an enemy.

 

             The "Estimated TOA At Last Reported Position" tells the controller when the lead element arrived at the Last Reported Position.

 

             The "Estimated TOA At Next Position" is an estimated time when the lead element will arrive at the Next Position.

 

             There is no movement completion report issued when a unit completes the move.  The unit will stop and assume the defend posture.

 

             Units may experience a delay (database defined) due to incoming artillery or because of an air strike.  This delay will cause the unit speed as reported on the movement report to be slower.

 

             CHANGE UNIT SPEED  (SLIDE M2-23) In order to facilitate coordinated movements among units, a unit's highway speed may be changed to allow the unit to travel faster or slower.  The CHANGE UNIT SPEED order is used for this.

 

             The order will not affect the current speed of a moving unit.  Upon its next mini step move, the unit will assume the new speed, if possible.

 

             CHANGE UNIT MOVEMENT ATTRIBUTES  (SLIDE M2-24) This order is used to change a unit movement attribute when that is the only unit characteristic that needs to be changed.  For units currently on the move, the change will take effect when the model next examines the unit for movement to a new position.

 

2.3       RECONNAISSANCE  (SLIDE M2-25) Reconnaissance is a critical component of virtually any tactical operation.  As shown on this slide, CBS provides multiple approaches to obtaining reconnaissance data.

 

             Each of these areas is discussed in the following paragraphs.

 

             MAP RECONNAISSANCE  (SLIDE M2-26) As the name implies, this order produces a Map Recon Report on a geographic area and contains information readily obtained from a detailed map inspection.

 

             This menu may be used to obtain map movement planning data which provides information on how long it should take to move from point “A” to point “B”.

 

             It may also be used to obtain trafficability information and the slope between two points.

 

             REPORT TYPE: The options are Map Recon, Map Movement Planning or Map Trafficability. 

 

                           Map reconnaissance provides information about terrain polygons, map road and river segments, bridges and runways which exist in the terrain database. 

 

                           The Map Movement Planning report provides a planned transit time for a specified route based on the mobility class and a max. attainable speed. 

 

                           The Map Trafficability report provides information on the polygons and the slope in the area.

 

             REPORTS DESIRED: Options are yes or no with the default as no for all fields except the ALL field, which defaults to YES.  At least one entry is required.  If ALL is selected, the other entries in this field are ignored.

 

             LOCATION:  Enter the desired location.  For all reports except the Map Movement Planning, at least one location is required.  For the Map Movement Planning, two locations are required so that slope may be computed.

 

             RADIUS:  Entered in KM to describe a circle about each listed point, which is searched for objects to report.  If left blank, only objects within a database-defined distance of each listed point are reported.  Because of the amount of computations that may be required, the database limit for radius has been set to 1 KM.  A larger number would slow the game.

 

             MODE OF MOVEMENT: Options are as shown on slide.  It defaults to blank but it is required for the Map Movement Planning report.

 

             MAX. ATTAINABLE SPEED: Enter a speed in KPH.  It is required for the Map Movement Planning report.

 

             MOBILITY CLASS: Choices are Troops, Trucks or Tracks.

 

             Use the MAP INPUT key to enter the grid location of the area

 

             (SLIDE M2-27)  Map recon terrain report provides information on the following: location of designated point, elevation, urbanization, urbanization extent, vegetation and extent, and trafficability and extent.

 

             Extent is defined by 4 values indicating the distance to the nearest edge of the polygon in the cardinal directions (or > a database defined distance).  The diagram is provided to help visualize the extent of the urban polygon described in the report.  (It is not provided on the actual report.).

 

             The other reports provide CBS information about the requested object that can be obtained from a detailed map inspection.

 

             (SLIDE M2-28)  Map recon road report provides information on the following: location of designated point, road type, azimuth, and length of segment, presence of fixed bridges, trafficability and urbanization.

 

             (SLIDE M2-29)  Map recon trafficability report provides information of the following: location, azimuth at designated point, slope (computed over one ministep in the specified direction) in designated direction, urbanization at designated point, vegetation at designated point in designated direction, and trafficability at designated point.

 

             The slope shown here is calculated for the first mini step in the direction from point 1 towards point 2.

 

             (SLIDE M2-30)  Map recon movement planning report provides information on the transit time for the mobility class over the route specified by the list points.

 

             TACTICAL RECON  (SLIDE M2-31) Tactical reconnaissance consists of Area recon, Route recon or Minefield recon.  These may be performed by using the new Tactical Recon order or other movement orders.

 

             TACTICAL RECON ORDER  (SLIDE M2-32) This is the Tactical Recon order that may be used to conduct the various type recons.  The fields in the order are:

 

             UNIT:  Use LIST NAMES or type in a unit name.

 

             ACTIVITY:  Options are ORDER or UPON REQUEST REPORT (UR).  Use the order option to create an order for the unit to conduct a recon. 

 

             Use the UR option at any time during the reconnaissance to obtain a report of what the unit has reconnoitered.  When this option is used, the recon unit issues a full recon report for each point reconnoitered up to the time of the request but does not report on an area around its present location until the recon time for that point has elapsed.

 

             RECON TYPE: Options are AREA, ROUTE, or MINEFIELD.  An Area recon is performed in a circle of a specified radius. 

 

             The Route recon is done over the specified route while the Minefield recon is done for all minefields found inside a circle of a specified radius.  Each type recon is discussed in detail later in this section.   

 

             HASTY RECON MLC: Options are yes or no with the default being no.  If yes is selected, the unit determines the military load classification (MLC) of every fixed bridge encountered, and experiences a time delay (database value) at each bridge.  Engineer bridge MLC is done automatically during hasty or deliberate route recon without a time delay.

 

             UC REPORT: Upon Completion (UC) report may be obtained.  Options are yes or no with no as the default.  If yes is selected, a full report is sent to the workstation at the end of the recon mission.  The UR report and the simulation generated reports sent to the workstation as the unit completes its recon at each route point tend to render unnecessary the UC report, since the report is merely a full recon report at the time the mission is completed.  For this reason, the UC Report field defaults to NO.

 

             LOCATION:  Enter a grid location.  The unit will recon this point and all objects within the circle described by a radius using this point as the center of the circle.

 

             RADIUS:  Enter in KM.  This defines the circular area to be reconnoitered.  The larger the radius selected, the longer it will take for the unit to recon.

 

             If a unit conducting a recon becomes incapable or is wiped out, no UR or UC report is issued.

 

             A unit may perform minefield recon while in combat but may not perform area recon in combat.

 

             AREA RECONNAISSANCE  (SLIDE M2-33) An Area recon is performed in an area defined by a circle of a specified radius.

 

             A unit conducting an area recon stops at each route point specified in the order to conduct the recon searching in the area described by the radius specified.

 

             The recon unit conducts a hasty route recon between the specified points as it moves from one recon location to the next recon location.

 

             (SLIDE M2-34)  The amount of time required to recon an area is dependent on the number of objects and the time to recon each of the objects in the area, the size of the unit, the recon area, the terrain, degree of urbanization, day/night conditions and avoid combat status.

 

             The SITREP shows the type reconnaissance the unit is performing.  It may show the unit in defend, recon as area while the unit movement report shows a speed of 0.  This will happen if the recon point is the last point on the route list.

 

             ROUTE RECON  (SLIDE M2-35)

 

             Route recon may be hasty or deliberate and may be performed during a ground move.

 

             The unit follows the route specified in the order and conducts the reconnaissance in an area equal to the unit radius of the unit (found in the unit SITREP).

 

             The unit experiences a speed reduction while performing route recon.  The reduction factor is dependent on the recon circle radius, and the size of the unit.

 

             For units performing deliberate route recon, there is a database defined time delay associated with reconnoitering certain objects such as obstacles, fixed bridges, runways and aircraft shelter clusters.  This delay is applied at the mini-step.

 

             Point obstacles recon reports describe the status of roadblocks as incomplete, bypass hard or bypass easy.

 

                           Incomplete means that the roadblock is under construction.

                           Bypass hard means that the terrain on both sides of the road is essentially no-go.

                           Bypass easy means that the terrain on at least one side of the road is passable.

 

             Hasty route recon reports are identical to area immediate reports.  Deliberate route recon reports are immediate reports with more detail for objects that cause delay.

 

             Route recon can not be performed while in combat.

 

             Again, the SITREP and Unit Movement Report may be confusing at the last route point.

 

             RECON REPORTS The simulation generates an immediate report upon detecting a particular event or object, such as a minefield or fall of shot at the recon point.  It reports only on triggering events, which are defined in the database.  It reports information on ATDs, displaced persons, fall of shot, enemy convoys, enemy unit and non-belligerents, minefields, ASCs, obstacles. bridges, on-order obstacles, runways, supply collections and PDPs.

 

             (SLIDE M2-36)  This is an example of an area recon incremental report.

 

             (SLIDE M2-37)  This is an example of a Tactical Recon Summary report.

 

             MINEFIELD RECON  (SLIDE M2-38) When a unit encounters an enemy minefield all that is seen on the graphics is a black circle as shown on this slide.  A friendly minefield is shown as it is in the simulation and as shown depicted on the bottom of the slide.  Once recon of the enemy minefield has been accomplished, it is shown as it is in the simulation and as indicated on the bottom of the slide.

 

             (SLIDE M2-39)  Recon of an enemy minefield may be accomplished using the Tactical Recon order, the Engineer Task order or by using the minefield recon option on the Ground Move/Withdraw order.  (Friendly minefields are shown correctly when encountered by a friendly unit.)

 

             Minefields are reconnoitered at the designated points from closest to farthest away, based on the shortest distance between the unit and the nearest edge of each minefield. 

 

             Recon of the minefield continues as long as the recon order is in effect and the recon circle overlaps the minefields being reconnoitered.  A capable unit, in or out of combat, can perform the minefield recon.

 

             The time to recon a minefield is dependent on the type of minefield, minefield area and number of people available to recon.

 

             If the minefield recon option is selected in the Tactical Recon order, only minefield recon is conducted at the designated points.

 

             If the unit is interrupted or a User Requested report is sent before completing the recon of a minefield, it reports on what it knows based on how long the unit has been performing the reconnaissance. 

 

             Minefield recon may also be accomplished by using the Engineer Task Order menu, the Ground Move menu or the Withdraw menu.  In all these cases, the same reports are generated.

             The bull-through or in-stride options may not be used in conjunction with the minefield recon option

            

             (SLIDE M2-40)  Minefield recon reports are generated in three stages.  This is an example of the initial stage report.

            

             (SLIDE M2-41)  This is an example of the intermediate stage.  At this time the true minefield graphics will show on the TV monitor.  It is now easy to decide how to breach the minefield.

 

             (SLIDE M2-42)  This is an example of the final stage report.

 

2.4        GROUND ATTACK  (SLIDE M2-43) When attacking in CBS, the attack is oriented on an enemy unit as opposed to an objective.  Establish an attack point on the enemy unit to ensure that the attack continues upon enemy contact.

 

             All combat related reports indicate edge to edge distances between units meaning that the distance between the two units is measured from unit radius to unit radius.  The unit radius will change as the unit loses or gains combat systems and can be found on the unit SITREP.

 

             As can be seen, several of the fields in this order are the same as for GROUND MOVE. There are a few new fields to discuss:

 

             DISMOUNT RANGE  (SLIDE M2-43) Allows the controller to select the range from the enemy at which the mounted infantry will dismount from their vehicles to continue the attack on foot. This option can be used with units that have dismounted troops and vehicles that can carry these dismounted troops (essentially all vehicles but designated in the database) as passengers.  The model will determine how many infantry are available to mount after crewing the unit's combat systems.  If one dismounted troop can not ride on or in a vehicle, the unit will walk.  Once mounted, the unit will move in the attack at the speed of a mechanized unit until the unit reaches the Dismount Range.  At this point, the infantry will dismount to continue the fight and the unit will move at the slower dismounted infantry speed.  

 

             The LOGREP and the SITREP show the mount/dismount status of the dismounted troops combat system. 

 

             (SLIDE M2-44, 45)  ATTACK WITH (AW), PROTECT WITH (PW), COVER WITH (CW) and SCREEN WITH (SW) are percentage values of combat power. 

 

             The ATTACK WITH entry is the percent of weighted combat power oriented in the attack direction if the sum of the AW, PW, CW and SW values total 100%. Otherwise, the values will be normalized. 

 

             If an attacking unit is itself attacked on the flanks or rear, the AW value is placed in the direction of the attack, the PW percentage value will be placed on each edge(s) to defend the unit against primary threats.  The CW percent is placed on each side(s) with a secondary threat.  The SCREEN WITH percentage value is placed on each side not under any type threat. 

 

             The information on this slide is found on the COMBAT POWER DISTRIBUTION report obtained using Summary Reports.

 

             (SLIDE M2-46)  The SUPPORT BY FIRE function allows a unit that is in a support by fire role to concentrate its fires against enemy units in a designated engagement area as depicted in this slide.  If there are no enemies in range inside its SBF EA, a unit in SBF reacts normally against enemy units in range while remaining ready to concentrate its fires whenever conditions permit, as long as it retains the SBF role.

 

             (SLIDE M2-47)  SBF RANGE is the Support by Fire Range.  Enter a distance from the unit to the center of the engagement area.  This denotes the range at which the unit is to stop its forward movement.  Upon reaching the SBF Range, the unit will change its posture to defend and will to support by fire until the unit is given a subsequent attack or defend order with the SBF Range field set to zero or left blank.

 

             A location and a radius are required to establish the engagement area.  If no value is entered in the radius field, a database defined default value will be used.  There is also a database defined maximum radius that may be used.

 

             There are two cases in which a support by fire unit may be forced to give up its SBF role by the presence of an enemy.  The enemy unit may be an attacking enemy or a close enemy.

 

                           ATTACKING ENEMY: If the edge to edge distance between the attacking enemy unit and the SBF unit is no more than a database defined range, and the platoon equivalents echelon of the attacking enemy unit is no more than the database defined platoon equivalents echelon smaller than the platoon equivalents echelon of the SBF unit, then the unit will lose its ability to support by fire.

 

                           CLOSE ENEMY UNIT: If the edge to edge distance between the close enemy unit and the SBF unit is no more than a database defined range, and the platoon equivalents echelon of the close enemy unit is no more than the database defined platoon equivalents echelon smaller than the platoon equivalents echelon of the SBF unit, then the unit will lose its ability to support by fire.

 

             The unit will lose its ability to support by fire if it breaches the defend to withdraw threshold.

 

 

             BYPASS ECHELON  (SLIDES M2-48)  The Bypass unit entry is made on the Ground Attack order field and is used to bypass enemy units to maintain the attack to a controller specified location.  An attacking unit with BYPASS ECHELON level given will attempt to bypass enemy units with PE echelon at this level or lower.  If the bypassing unit encounters an enemy with a higher PE echelon level, it will end the bypass attempt and go into combat.

            The situation report of a unit that is not ordered to bypass will indicate NOT BYPASSING.  Once a unit is given an order to bypass its situation report will initially indicate ORDERED.  This status will be indicated as long as the unit is moving along the attack route until the final objective is reached or until an enemy is detected along the route of movement.  When an enemy is detected and if the enemy is equal too or lower than the PE echelon directed the unit will automatically begin to bypass the enemy.  At this point the situation report will indicate BYPASSING.  The unit maintains its speed while bypassing and will be subjected to increased vulnerability with reduced tactical mobility as it attempts go around the enemy.                           Once the enemy has been bypassed the situation report will indicated PASSED and eventually continue the mission with the bypass ORDERED status.  If the enemy unit initially encountered has a higher PE echelon than indicated in the original ground attack order the unit will automatically be kicked out of the bypass ORDERED status and attack the enemy along the attack route.  The situation report as this occurs will change automatically for ORDERED to NOT BYPASSING. 

 

             CBS, using COBRA, provides for and rewards using sound tactics, techniques and procedures that adhere to current doctrine.  Attacking the enemy flanks or rear, using light infantry units in heavily wooded or urban terrain, employing armor and mechanized units in open, gently rolling terrain, using the terrain to provide good cover and concealment, using fresh forces and using avenues of approach which will support the size unit in the attack will result in higher attrition against the enemy.  Conversely, disregarding these factors could result in heavier losses for a unit.

 

             OVERRUN:  An attacking unit may overrun a detected enemy unit if, upon its next mini-step move, the range between the two units would be less than or equal to the database defined mini-step size.  At this time, an attacker/defender comparison is determined.  This comparison is based on extrapolations of current attrition rates, with the attacker and defender each represented by how long their longest-lived systems would survive if current attrition rates were to continue. This comparison of survival times is used to determine an overrun ratio.  The overrun ratio is used to ensure the existence of a large enough imbalance of forces in favor of the attacker.  If the imbalance is great enough, the attacking unit will overrun the enemy.  If the attacker/defender ratio falls below the overrun threshold, the attacking unit will remain at its current location and the attacking unit will attempt to overrun the enemy at a future time.  If an overrun occurs, the workstation that overruns a unit will receive a report stating that it has overrun the enemy.  It will also receive a report if the unit it is in contact with is wiped out.  The overrun or wiped out unit will also get a report stating that it has been overrun or wiped out.

 

             (SLIDE M2-49)  TACTICAL THRESHOLD.  Each unit has pre-set threshold values established in the database, expressed as a percentage of its total weighted combat power, at which the unit automatically changes from one posture to another; e.g., attack to defend, defend to withdraw, withdraw to incapable and incapable to wiped out.

 

             As can be seen, there are actually four levels.  The first two can change at a workstation by using the TACTICAL THRESHOLD order; the other two can be changed only by Senior Control.  These effectively set the bottom limit for the values that can be changed at a workstation.

 

             Default values are set in the database.  The ATTACK TO DEFEND and the DEFEND TO WITHDRAW values can be set to whatever values are reasonable for the tactical situation.  For example, both might set very high (99% and 98%) if the unit is not to become decisively engaged or very low for an all out attack or defense.  The values must, however, be in descending order.

 

             (SLIDE M2-50)  CHANGE TACTICAL OPTION: This is the menu that is used to set the tactical threshold for a unit or set Force Ratio Options. 

 

             ATTACK/DEFEND:  Is the weighted percent strength at which the unit changes automatically form ATTACK  to DEFEND posture.  This value must be larger than DEFEND/WITHDRAW threshold.

 

             DEFEND/WITHDRAW:  Is the weighted percent strength at which the unit changes automatically form DEFEND to WITHDRAW posture.

 

            USE ATTACK/DEFEND ADVANTAGES:  Indicates whether the unit, when in combat, should cease and attack, and begin to defend, when its advantage falls below a particular ratio.

 

             ATTACK/DEFEND WHEN ADVANTAGE BELOW  n TO 1 :  Indicates the unit-to-enemy combat power advantage below which the unit should no longer fight in attack posture.

 

             USE DEFEND/WITHDRAW DISADVANTAGE :  Indicates whether the unit, when in combat, should begin to withdraw when its disadvantage becomes significant.

 

             DEFEND/WITHDRAW DISADVANTAGE BELOW  n TO 1:  Indicates the unit-to-enemy combat power disadvantage at which the unit should withdraw rather than continue to fight. 

 

             (SLIDE M2-51)  COMBAT POWER DISTRIBUTION.  A unit’s operational combat systems produce its combat power, which is distributed among six directions for use in computing attrition.  Combat power distribution is controlled either automatically by the simulation, in response to the battle conditions as indicated above or manually.  A unit’s combat power distribution is evaluated before each attrition assessment and whenever the unit’s orientation is changed.

 

             The amount of combat power that is allocated to a directions is based on controller input established in an order, the type, size and number threat unit(s) on the side, and the activity and posture of the threats.

 

       Combat power distribution is also tied to unit deployment.  This slide depicts how each type formation has its combat power constrained on certain sides based on the formation.  In this example, the maximum combat power that can be placed on side 1 is 5 %.  This is also true for sides 2, 3, 4 and 5.  Accordingly, most of the combat power of the unit is allocated on side 0.

 

             (SLIDE M2-52)  This slide shows some of the other formations and their restrictions.

 

             It is generally a good idea to allow the simulation to Automatically set the combat power distribution.  However, the COMBAT POWER DISTRIBUTION order allows the controller to override this automatic feature.

 

             (SLIDE M2-53)  The COMBAT POWER DISTRIBUTION REPORT (one of the SUMMARY REPORTS) is shown on this slide.  The right hand column shows the unit's current TACTICAL THRESHOLDS.

 

             The report also provides MISSION, POSTURE, DEPLOYMENT, AZIMUTH and STRENGTH information that is also available on the SITREP.

 

             There is a graphic representation of the unit's current COMBAT POWER DISTRIBUTION.  The unit is oriented in the forward direction.  Note that the forward direction is tied to the azimuth shown at the bottom of the slide.  Thus, this unit is oriented to the south. 

 

             The numbers shown in percent represent the percent of combat power oriented in that direction.  Thus, in this case, 40% of 100% of the unit’s combat power is oriented in the forward direction.

 

             Notice the word "Automatic" in the center of the diagram.  This concept is discussed below.

            

             (SLIDE M2-54)  To manually change the combat power distribution of a unit, use the COMBAT POWER DISTRIBUTION menu.

 

             Enter "no" in the AUTOMATIC field to set the unit's Combat Power Distribution to manual.  Then enter values in the fields provided. They must add to 100%.

 

             If new values had been set but not implemented, they would appear in parenthesis below the current values shown in the combat power distribution report.  The new numbers are implemented just prior to the next combat assessment.

 

             To return to the AUTOMATIC mode, specify the unit and enter "yes" in the AUTOMATIC field.  No other entries are required.

 

             (SLIDE M2-55)  Key points to remember when using the COMBAT POWER DISTRIBUTION order include:

 

             The total for the six entries must equal 100%.

 

             Forward is the direction of the unit's azimuth, not necessarily North.

 

             When in the manual mode, the values will not change automatically due to proximity of threat units.  If the unit is attacked from a direction in which it has little strength, the model will make no adjustment regardless of the values in the GROUND ATTACK or DEFEND order.  For this reason, use the manual mode sparingly.

 

             When not in combat, the reorientation will occur immediately.  When in combat, the reorientation will occur over time in accordance with the attrition cycle or mini-steps when in the attack.

 

2.5        MANEUVER CONTACT REPORT  (SLIDE M2-56) There are a series of spot reports generated by CBS, using the SALUTE format, that provide information about detected enemy units.  As the units move closer together, more detailed information is provided to the workstation.  This slide provides a sample of one of these spot reports, the Maneuver Contact Report.  Another similar report, the Detected Enemy Report, is in the same format but with the banner of Detected Enemy Report replacing the Maneuver Contact Report banner.  If an enemy unit is detected but not engaged in conflict, the detecting unit receives the Detected Enemy Report.  If the detected unit and the detecting unit are engaged in conflict, the appropriate Maneuver Contact Report is generated based on the observation range (based on edge to edge distance between unit radii).  The amount of detail in both reports depends on the observation range (near, medium or far) with the near report providing the most accurate data as shown on this slide.

 

             (SLIDE M2-57)  The graphic representation of the enemy unit is tied to this report so that the two reflect the same information.  Thus, at the near range the size, type and strength of the detected enemy is shown but at the far range, only the basic symbol and direction arrow are shown graphically.

 

2.6        COMBAT REPORTS  (SLIDE M2-58) The SITREP provides information about a unit that is in combat.  It shows the unit in an attack, in combat, its support by fire status, its mount/dismount status and deployment.

 

             (SLIDE M2-59)  Once a unit has been given a ground attack and it is in combat (turns white), obtain a COMBAT REPORT. 

 

             This report shows all enemy units in combat with the unit, shows if the unit is being suppressed by incoming artillery fire, lists the combat set number, shows the percent strength of the unit on each side, lists the edge to edge distance between the units, provides information on the mount/dismount status of the unit and provides the approximate time in combat for the unit.  This information can be very useful in fighting units.  For example, if a unit has long range anti-tank weapons and the enemy does not, it might be wise to stop at long range so that it can bring these weapons to bear on the enemy and he can not effectively use his shorter-range weapons.  It also shows data from COBRA so the controller may better understand the affects of METT T on his unit.

 

             (SLIDE M2-60)  The EQUIPMENT LOSS REPORT is the first damage report received and lists the damage done to the unit.  The irreparable column shows those items of equipment that have broken down during the time period (not due to combat) and are not repairable.

 

             (SLIDE M2-61)  The COMBAT DAMAGE REPORT summarizes what has happened to a unit during the time period indicated on the report.  It is difficult to match up all the reports with what caused the damage whenever numerous types of attrition occur.

 

2.7        DEFEND  (SLIDE M2-62) The DEFEND order can be used to halt a moving unit or to change the unit’s attributes if it is already in the defend posture.  For example, UNIT AZIMUTH for a unit already in DEFEND can be changed. 

 

             A unit will automatically assume a defend posture if it is moving and reaches its destination as a result of GROUND MOVE, GROUND ATTACK, or WITHDRAW.

            

             Initially, units in a defend posture will be considered to be in a hasty defense.  As they remain in their position, their defensive posture will improve, increasing their ability to defend (suffer less attrition).

 

             If MOVE UNDER FIRE equals "No" in a GROUND MOVE order and the unit comes into contact with an enemy unit, it will stop and assume the defend posture.  If yes, the unit will continue to move.

 

             Most of the fields in this order have already been discussed.  The MODE OF MOVEMENT and the other fields (LOCATION, MARCH INTERVAL, LOCATION, etc.) normally associated with movement are provided so that where and how the unit will move if it breaches the defend to withdraw threshold can be specified.

 

             UNIT AZIMUTH  Used to redirect the primary orientation of the unit.  Recall the arrows seen on the unit symbol graphics when UNIT DIRECTION was toggled “on.”  Six options are available.  Use LIST NAMES to display.

 

             PROTECT WITH, COVER WITH and SCREEN WITH may be established in the DEFEND order.  When applying these values, the ATTACK WITH (from the Ground Attack order or the default in the database) and the PROTECT WITH values are added together and applied in the direction of a primary threat.

 

             If the values are left blank, the simulation will use default values set in the database for the unit or will use the last values associated with the unit using the previous GROUND ATTACK or DEFEND orders.

 

             IN-PLACE RECON Options are yes or no with no as the default.  If set to yes, the unit conducts in place recon.  This is an area recon without the unit moving to a specified location.

 

             RECON RADIUS: Enter a value in KM. The default is blank.  If in-place recon is yes and the unit is not in a PDP and the radius is left blank, the unit performs area recon of a circle of radius equal to the unit radius.  If recon radius has a value, the unit conducts recon inside a circle of radius equal to the specified valued up to a database defined maximum based on unit size.  If the unit is in a PDP, radius is ignored and the recon is performed inside the PDP.  The unit does not abandon the PDP.

 

             LOCATION LIST applies to the route the unit will use if it is automatically forced from DEFEND into the WITHDRAW posture.  If a route is not designated, the model will select one.

                                               

             AVOID COMBAT has the same penalties in the defense as elsewhere.  Use this field to take the unit out of AVOID COMBAT if desired.

 

             The rest of the menu items have already been discussed. 

 

2.8        MASS OPERATIONS  (Slide M2-63) This function allows a group of units, battalion size or smaller, to be identified with a massed unit operation, either defensive or offensive, focused on units in a specified engagement area.  The purpose of the function is to enable units to get the doctrinal firepower benefits of deliberate massing against an enemy without incurring the crowding penalties built into CBS against units that are too close together or that adopt a minimal unit frontage and thus become subject to self-crowding.

 

       Units benefiting from a massed unit operation may be more vulnerable to direct fire.  They will be more vulnerable to indirect fire and to area damage air to ground weapons.

 

             Enough units must be involved in the mass operation so that the combined number of units is at least equivalent to 2 battalions.

 

             (SLIDE M2-64)  The order used to create the massing operation is shown on this slide.

 

                           FUNCTION:  Options are create, change, delete, or report.

 

                                        The CREATE function allows a unique operation name to be created along with establishing other characteristics of the operation.  The name may be created with the other options being filled in later using the change option.  The center of the engagement area must be specified when using the create option.

 

                                        The CHANGE function allows the parameters of the engagement area, the expiration time and the list of member units of a named operation to be changed.

 

                                        The DELETE function deactivates the operation name, effectively deleting the operation and releasing all participating units.

 

                                        The REPORT function causes a report to be transmitted to the workstation giving the status of a named massed unit operation.  If the REPORT function is specified and ALL is specified instead of the name of a massed operation, the report will give the status of all massed unit operations currently active at the workstation.

 

                           OPERATION NAME: is a required field.  Enter a unique name for the operation.  Other workstations may use the same name.

 

                           CENTER OF ENGAGEMENT AREA: Enter a grid location.  It must be specified in order for member units to benefit from the massed unit operation.  It may be created by using the FUNCTION field to create an operation or to change an operation.

 

                           RADIUS OF ENGAGEMENT AREA: Enter a radius in meters.  This is the radius of the circle centered at the center of the engagement area that defines the EA.  If no value is entered, it defaults to a database number.

 

                           OPERATION START: Enter a start time for the operation.  If field is left blank or 0 is entered, the current time will be used.

 

                           OPERATION EXPIRATION: Enter the time for the operation to end.  If no value is entered the time period will default to a database defined time period.  If 0 is entered, the operation ends immediately.

 

                           UNIT:  Enter the name or names of units owned by the workstation that are to be included in the operation.

 

                           ADD/DEL: Used to add or delete a unit from the operation.  Used in conjunction with the create or the change function.  An activation delay for an added unit starts at the time the order is received

 

                           START:  the time a unit will join the massed unit operation.  This is used with the create or the change function. 

 

             (SLIDE M2-65)  This slide shows an example of a user requested mass operation report.

 

             (SLIDE M2-66)  A necessary condition for a unit to benefit from being a member of a massed unit operation is that the unit has completed an activation delay period (database value allowing for planning and coordination between units in the operation).  Activation of the clock starts at the unit start time. 

 

             If a new engagement area is defined, the clock is reset for all units in the operation.

 

            If a unit leaves the operation, its elapsed activation clock is destroyed.  If it rejoins the operation, a new clock starts.

 

             Engagement areas may not overlap.

 

             There is no restriction on the type of unit that may be included in a massed unit listing.  This includes RAT capable units.

 

             Note that the order allows for a massed operation to be established without specifying any of the particulars of the operation itself other than the name and the location of the EA and two units.  Other units may be added to the operation at a later time.

 

             SBF operations may be used in conjunction with massed unit operations.

 

             Units within or subject to join a massed operation may be split and merged.  If units are merged and the core unit has started its activation delay, the cumulative number of platoon equivalents added this way may not exceed a database parameter.  If it does, the core unit becomes deactivated and starts its activation delay over again.  This is to thwart circumvention of the unit activation delay.

 

 

2.9       UNIT DEPLOYMENT  (SLIDE M2‑67) This order is used to deploy a unit tactically or to change its deployment.  In addition to deployment being used for movement, it is used in the detection of and by infiltrators by placing out detection clusters in the deployment formation, frontage and depth specified.

 

2.10      WITHDRAW  (SLIDE M2-68) WITHDRAW causes a unit in contact with the enemy to conduct a withdrawal.  At the end of its withdrawal, the unit assumes a posture of DEFEND.  Fields within the order are similar to those seen previously.  WITHDRAW moves a unit at a faster rate of speed while the unit remains in combat.  Once out of combat, the unit will use normal movement speeds.       

 

             This order is for a planned withdrawal as compared to the automatic withdrawal caused by breaching the DEFEND:WITHDRAW threshold. 

 

             The same penalties apply in AVOID COMBAT as with any other order and route selection considerations should be the same as for any other move.

 

2.11      UNIT OFF LOAD SUPPLIES  (Show M2-69) This order allows a unit to off load excess supplies and create a supply collection.  Other units may be authorized access to the supplies. 

 

             Use the DRAW SUPPLY ORDER to up load the supplies.

 

             This may be used to lighten a load for infiltrators so that they may infiltrate.

 

2.12      FIRE SUPPORT See Volume 2 Section 5 for details on these Fire Support orders.

 

             (SLIDE M2-70)  Use this order to fire the mortars in a unit.

 

             (SLIDE M2-71)  This is an example of the report received at the workstation when a fire mission is scheduled.

 

             (SLIDE M2-72)  Units may employ smoke.  If used, it degrades movement speeds, reduces attrition and hinders the use of guided munitions.  Mortars and artillery may be used to fire smoke.  The number of rounds and other considerations for the employment of smoke are database derived and are detailed in the battlebook.

 

2.13      CHANGE MOPP STATUS  (SLIDE M2-73) MOPP status may be selected for a unit using one of the movement orders or by using the order shown on this slide.  The AUTOMOPP field provides the option of directing the unit to automatically go to MOPP 4 if the field is set to yes and the unit is hit by a chemical attack.  If set to No, the unit will retain in its current MOPP level until changed by a controller even if the unit is hit by chemicals.

 

             If a unit is hit by a chemical attack, it will receive a spot report indicating there is detection of an agent in the area and a CHEMICAL ALARM report.  If AUTOMOPP is set to no, these reports tell the controller that he should order his unit(s) to MOPP 4 immediately.  It takes about 8 minutes (database) to go from MOPP 0 to MOPP 4 so the unit will suffer casualties in this case.  If the unit were already at MOPP 2, it would take less time to go to MOPP 4 and the unit would suffer less attrition.  Remember, if the AUTOMOPP is set to Yes, the unit will automatically go to MOPP 4 when hit by chemical or smoke.

 

2.14      OCCUPY PREPARED DEFENSIVE POSITION  (SLIDE M2-74) CBS allows for a Prepared Defensive Position (PDP) to be built for a unit. 

 

             A unit must be ordered to occupy a PDP using the order shown on this slide.  This may be accomplished after the PDP is built or while it is under construction. 

 

             The unit must fit into the PDP.  That is, the PDP must have prepared positions for the combat systems, combat support systems and personnel operational in the unit.  Only one unit may occupy a PDP at any given time, and a unit may occupy only one PDP at any given time.  The unit must be in the defend posture and within a database defined distance from the center of the PDP.  There are three levels of PDPs modeled in CBS corresponding to the engineer survivability levels 1,3 and 5.

 

             A unit's benefit (protection from direct fire, indirect fire, and air to ground attrition) resulting from the occupancy of a PDP is dependent on the fractional capability of the PDP.  For example, the occupant of a PDP will not receive any protection from the PDP until the PDP has reached 100% fractional capability for level 1.  Once this stage is reached, the unit will continue to receive protection from the PDP until the fractional capability of the PDP, as a result of enemy fires, drops below a database defined value.  At this point, the unit will lose the protection benefit of the PDP.

 

             A unit ordered to occupy a PDP will not be permitted to occupy the PDP if, for each platoon equivalent type, the unit's number of platoon equivalents of the given type exceeds the PDP's number of platoon equivalents for the same type by a database defined number.

 

             The occupying unit will assume the primary orientation of the PDP.  The combat power distribution will automatically reflect the new orientation of the unit.

 

             If the combat power distribution of the unit occupying the PDP is changed so as to create a situation where the sum of the combat power along the prepared edges is less than a database defined value, then the occupant will automatically abandon the PDP.

 

             Friendly units are permitted to merge into a core unit occupying a PDP if the resultant unit meets the fit criteria.  If, as a result of a merge, task organization or the return of maintenance, the occupant of the PDP no longer fits in the PDP the unit is permitted to remain in the PDP with a lower protection value.  The simulation automatically develops a new PDP Plan based on the new unit showing what additional work has to be accomplished to provide protection for the new equipment.

 

             A unit will abandon the PDP if given a GROUND MOVE, an ATTACK, or a WITHDRAW order.  However, it will not automatically abandon the PDP if the unit breaches the DEFEND TO WITHDRAW threshold.

 

             Details on building a PDP are contained in the Engineer section of this volume.

 

2.15      ON ORDER OBSTACLE EXECUTION  (SLIDE M2-75) The on ORDER OBSTACLE EXECUTION order separates the demolition from the preparation of an obstacle. 

 

             Units may perform on order execution of a demolition that destroys a bridge (Fixed or Engineer) or creates a road crater.  The ENGINEER TASK order is used to rig the obstacle while the on ORDER OBSTACLE EXECUTION order is used to set up the mission parameters.  It may also be used to disable a prepared obstacle or to replace a previous on order mission.  In all cases, the executing unit must be within a database-defined distance from the rigged obstacle.

 

            OBSTACLE NAME: Enter the obstacle name that was established in the Engineer Task order.

 

            EXECUTING UNIT: Enter the name of the unit assigned to execute the demolition.  Only Senior Control or the workstation owning the current executing unit may assign a new executing unit.

            

            EXECUTING TIME: This is the time for executing the demolition.  If DANGER CLOSE is selected, this time becomes a no later than time.

 

             DANGER CLOSE: If YES is selected, the obstacle will be executed if a detected enemy unit moves within a database-defined distance from the obstacle.

            

             Key points concerning on ORDER OBSTACLE EXECUTION are shown here:

 

             Only one unit can be assigned to execute an on Order Obstacle.  However, a unit may have several on order missions assigned. The mission may also be transferred from one unit to another.

 

             If an obstacle is rigged and an enemy unit comes within a database-defined range of the obstacle prior to the obstacle being blown, the obstacle will be disabled (rigging removed).

 

             (SLIDE M2-76)  The on ORDER OBSTACLE EXECUTION REPORT provides additional information on the on ORDER OBSTACLE execution.

 

             (SLIDE M2-77)  The REPORT on ORDER OBS EXECUTION order is used to obtain information on the on order obstacle as shown on this slide.

 

            OBSTACLE NAME: If filled in, the simulation will provide information on the specific on order obstacle.

 

           EXECUTION UNIT: If filled in, the simulation will provide information on all on order obstacles assigned to that unit.

 

            LIST on ORDER OBSTACLES: For a workstation, the simulation will provide information on all of the specific type on order obstacles for that workstation.            

 

2.16      SUPPLY COLLECTION DEMOLITION  (SLIDE M2-78) A supply collection may be totally or partially destroyed by demolition.

 

             For a unit to destroy an enemy supply collection it must first detect the supply collection and it must not be in combat.  A unit may destroy a friendly supply collection if it is on the supply collection authorization list.

 

             To destroy a supply collection, the unit must be close to the supply collection and its area (radius) must overlap the supply collection.

 

             The order allows for setting a fusing delay.  This sets a delay time between the rigging and the actual demolition.

 

             (SLIDES M2-79,80&81  These spot reports show the sequence of activity associated with the demolition.

 

             (SLIDE M2-82)  The status of the mission can be obtained by using the SUPPLY COLLECTION DEMOLITION REPORT as shown on this slide.

 

             CANCEL SUPPLY COLLECTION DEMOLITION The mission may be canceled using this order.

 

             CREATE  MANUEVER AREA:  (Slide M2-83)This order allows a controller to create a maneuver area that will bound a unit’s movement around enemy units while conducting an actual bypass movement.  They have no effect on a unit unless the bypass option is activated and the unit movement has been taken over by the simulation to avoid or bypass an enemy in close proximity to the unit. 

 

             STAY IN or OUT:  The controller may stipulate whether the unit is to STAY IN or  STAY OUT of the named created area.  

 

             MANEUVER POLYGON:  Listing of points that describes the polygon.

 

             (Slide M2-84)  depicts the maneuver polygon as displayed on monitor screen.

 

             MANAGE MANUEVER AREA (Slide M2-85)  This new order gives the controller management options for previously created maneuver areas.