Critical Regions

FORCES uses similar region definition methods for the following key regions:

Friendly Airspace - Produces the Region Defintion form. This defines region(s) that we assume are friendly to our forces (friendly airspace is defined separately for Red & Blue). This information is used by the automated C2 module as a factor in determining whether a track is friendly. Typically, a track originating in a region defined as friendly is assumed friendly unless there are other issues, e.g. Jamming in the region. Region data can be reviewed via the Review Region Data bar. The Create New Region of this Type bar produces a blank Region Definition form on which the Latitudes and Longitudes are type and the side assigned. For more information see the ADISC2 Programmer's Manual, C2 Module from 1992.

ADIZ - Produces the Region Defintion form. This defines the Air Defense Interdiction Zone. This is the area the automated C2 module considers a key zone around an area it is defending. When a track enters this region the C2 module starts to take actions to determine whether it's friendly or not. A clock also starts and if the track determination is not made by the time that clock expires the track is assumed hostile until subsequently proven friendly. ADIZ data can be reviewed via the Review Region Data bar. The Create New Region of this Type bar produces a blank Region Definition form with ADIZ Definition on which the Latitudes and Longitudes are type and the side assigned.For more information see the ADISC2 Programmer's Manual, C2 Module from 1992.

Keep Out Zones - Produces the Region Defintion form. This defines key areas (e.g. Around the White House or key military installations) that need special protection by the automated C2 module. The C2 module is more likely to attack unknowns and hostiles in these regions and under some conditions might even attack assumed friendlies in these regions. Keep Out Zone data can be reviewed via the bar. The Create New Region of this Type bar produces a blank Region Definition form with  Keep Out Zone Definition on which the Latitudes and Longitudes are type and the side assigned.For more information see the ADISC2 Programmer's Manual, C2 Module from 1992.

C2 Areas of Responsibility (AOR) - Produces the Region Defintion form. Yet another automatic C2 module required region. This defines the region that the C2 module is to defend. These region(s) are assigned to C2 assets for protection. They in turn are responsible for maintaining the iar picture and engagement assets required to protect these areas. The automated C2 module will only defend these regions. The previous 3 regions are option; if the C2 AOR is not defined the C2 module WILL NOT ACT. The interface for these regions is slightly different from the the others in that the regions are not only defined but must be assigned to C2 assets.

C2 Threat Evaluation Values - Produces the Region Defintion form. Yet another region definition that supports the automated C2 air defense rules. The automated C2 assigns track values used for prioritizing the hostile and unknown tracks to defend against. This evaluation is based in part upon the values defined for each threat region. The interface for these regions includes not just the region definition (as defined below) but also a base factor for tracks flying in each of the four cardinal directions (North, East, South and West). For more information about the procedure for computing the track value and how it's used by the C2 module see the ADISC2 Programmer's Manual, C2 Module from 1992.

Terrain Clutter Data - Produces the Region Defintion form. The only non-automated C2 region definition in this list. This is used to define the clutter within a defined region. The clutter types can be any of the types defined in Database Prototyping ( click here for more info ).

In any of these cases the interface is basically the same. An initial interface, Friendly Airspace, to ask the user whether he wants to review the current region data or create a new one is presented ( example ). All of the C2 forms allow the user to specify whether the data is appropriate to Red or Blue Air Defense. If the user selects "Review Region Data " he will be prompted to select the region from the map. The currently defined regions are displayed on the map ( example ). If the user selects an area without a region defined he'll be presented with a warning dialog stating "No Regional Data Found at this Location". Otherwise data will be presented ( example ). The information on this interface can be edited and saved or deleted. An option also exist for redefining the regions via map picks.

Whether editing an existing region or defining a new one remember to hit the "Save" button. When you do the region should show up on the map. If it doesn't, you haven't saved your work. Also remember to click the "Create New Region of the Same Type" if you want to add a new rectangular subregion. If you don't the system presumes you are redefining the initial rectangular subregion and you'll find yourself redefining existing areas you didn't want to change instead of adding more areas.

Note that while each region is rectangular and defined only by opposite corners, an unlimited number of rectangular regions may be combined in one regional specification (e.g. Friendly airspace). This permits the definition of complex regions.

Regions with attributes have a few extra parameters but the regional controls themselves are identical. For example, here's a typical " Threat Evaluation Region " interface. Note the region controls are identical, there are just extra fields for defining the base track value for a track going in any of the four cardinal directions (plus or minus 45 degrees).

The only one that's a little different is the C2 AOR interface. Here's it's basic format . While this is fine for defining the region the user typically would like to add the ability to assign the region to C2 assets. To do this he can click on the "Review Region Assignments" button. The interface will then change (example ) to permit him to assign the region. In this case the user can click on the assignment button and a list of available C2 assets will be provided. At any time only one asset can control the region; the purpose to defining up to 4 assets is redundancy. If the primary asset is knocked out the secondary asset takes control, and so forth.

If you make any change in the C2 AOR Assignments in this interface be sure to click on the "Save AOR Assignments"!

Note: If you click on the Assignment button (e.g. Where "SOCC 12" is in the example) and the resulting list is empty you don't have any defined C2 assets in the scenario. C2 Assets are defined by having capabilities recognized by the automated C2 module. To define data for this module go to "Mission Planner->Employ Automated Rules->Air Defense C2 Options". This will give a review of all of the currently defined rules. You can either click on the "C2 Controller Types" and add informarion on a new controller type for the appropriate side (Red or Blue) that already exists in the scenario, ot you can just deploy an asset of a type already recognized by the C2 module (if any are).