Employ Automatic Rules

Air Defense C2 Options

This interface is intended to set up the automated rules to deploy and employ automated air defense rules over one or more protected regions.  The module performs tasks in 4 extensive categories, namely:

  1. Regionalizing tracks and detections against automated and manned command centers.  This includes dividing the workload between these centers
  2. Maintaining the command and control structure in the face of losses, shutdowns to enhance survivability, mobile asset support (e.g. AWACS taking over some or all of the workload in or across sectors)
  3. Performing command center sites, including
    1. Managing all aspects of the air war, including surveillance, identification and weapons control functions,
    2. Managing the antisubmarine warfare ( this was incorporated into this module to kill air-breathing cruise missions before they got launched)
    3. Maintain lateral, forward and backward tell networks
    4. Evaluate survivability and mitigate losses.
  4. Maintain CAPS and alternate command centers
A real description of module itself is outside the scope of inline documentation in of a sable user's manual,  so please go here for details.  The interface itself includes a checker the validate the input data; this checker will run when this option is selected and color-code verification results in red, yellow or green.  Clicking on any line of the results will give you more details and lead you to the appropriate interface to make required changes.  

On selection, the C2 Verification Form appears with the Air Defense Auto_C2 Data Check information on it.  Data is presented in the upper block on the form with different colors representing the criticality of the errors (Red - fatal errors; Yellow - possible errors).  C2 data for the Red and Blue forces are listed separately.  The same color coding is used for the Red Force and Blue Force text blocks.

Clicking on any line of text causes a form to appear with related data for that line (e.g.line " C2 Survivability Rules Found" causes the C2 Asset Survivability form to appear six elements listed - all of which may be modified).  When an explanation is required for a line, a small Help form appear with any additional explanation of the entry.

Auto Sensor_Roving Targets

This function was developed to autogenerate a patrol for unmanned ISR aircraft that would cycle through a list of target spots requiring regular monitoring (e.g. grave sites). For more information about the underlying algorithm, click here. The Rover Target Review Form appears listing the target sets defined.  Each target is listed with its:

Targets may be edited with a double left click or deleted with a double middle click.

A new target may be created by clicking on the Create New Target bar.  This action causes the Rover Target Definition Form to appear with the title: Define New Target.  Data provided include:

The Get Location from Map bar allows the user to select the targets' location (Lat/Long) directly from the map.

While this interface permits the user to create target lists, the ISR assets need to be assigned to the mission through the individual asset's operational task list.  Just edit the ISR asset, select the operational task button, select "New Operational Task" from the task list (assuming the task isn't already created), and then fill in the form with the appropriate target set to assign the asset to the ISR mission.

Auto Strike Targets (Blue Attack)

This interface populates a mission generator with specifications to automatically generate air or artillery missions against targets detected in a given area and during a given time.  NOTE:  This interface will ONLY work against targets detected by sensors using the "External" message format; internally detections of this type are routed through the automated mission planner for targeting consideration.

The "Spec Classes of Auto Strike Assets" option permits the user to assign entire classes of friendly assets to be considered for autostrikes.  Thus the user can specify that all F-16's can be assigned against missions of type 1.   This is a non-exclusive list, in that a single platform class (e.g. F-16's) can be assigned against missions 1, 2, and 4 (and so on).  In this case the aircraft would be assigned on an as available rate (hence the sortie and time-to-day inputs) against the targets according to the number of assigned targets and the mission priorities.

Not all assets of a type need to be assigned against these missions.  The "Operational Task" option under the individual asset edit form permits users to assign only specific aircraft out of a class against these missions.  In this case you would NOT want to list the asset class in general as available against these mission.

Note that either artillery pieces or aircraft can be assigned.  JFORCES will issue the correct orders during runtime.  However, JFORCES will only consider using artillery pieces within range of the target during the scenario execution; it will not move the artillery pieces to attack positions (naturally, it will fly aircraft out and back at need).

The "Auto Strike Targets" interface for either red or blue planning will bring up the Auto-Fire Target Review Form  with the title: Automatic Artillery and Air-to-Ground Targets data listed.  Each target is listed with its:

The Targets may be edited with a double left click or deleted with a double middle click.  When editing a target, the Auto-Strike Target Definition Form ,  labeled Edit Existing Target, is used.  The mission specs identified above are definable on this form.

Define High Value Immediate targets

Basically, this is a lot like the auto-strike rules, defined above) except the autostrike rules are based on an ATO generator that runs periodically (the user can define targeting cycles of between once an hour and once every few days.  This interface permits immediate targeting of a high value target when one is detected.  This is used to model Scud hunts from the first Gulf War.  There are two parts to defining these rules.  The ato_rules Form appears with the title Top Level Automatic High Value Immediate Response Targeting Rules data listed. On Recon Radius (NM For Assets Requiring Designation) the number of nautical miles is typed.  Then you need to declare the targets to be targeted and the weapons (as in aircraft, artillery is not allowed) to be considered for immediate assignment against these targets.  To do that you need to go the next section

Define High Value Immediate Response Targeting Rules

Please read the prior section to understand what this is and how it applies to the automated ATO generator.
The H.V.I.R. Target Review Form with the title Automatic # High Value Immediate Response Targeting Rules .  Each target is provided with the targeting rules.  In addition, data for each target includes:

The Targets may be edited with a double left click or deleted with a double middle click.  Add and reword later:  When editing a target a new form titled Auto-Strike Target Definition and labeled Edit Existing Target.  On this form are several items which must be provided:

A new target may be created by clicking on the Create New Target bar.  This action causes the H.V.I.R.Target Definition Form to appear with the title: High-Value Immediate Response Targeting Information .  Data to be provided corresponds to the mission fields described above.