Red Controls

This interface permits force player (i.e. Red player) control and monitoring of of Red assets. We should note that this is a force player control; the umpire has additional controls (e.g. Immediate kill and creation) options that logically are not something a force player has control over. And that he does not have access to when he initializes as a force player. Also note that some higher-level (group) Red controls are located under the "Ground Force" controls. Finally, it should be mentioned that because FORCES started as a one-sided wargame, some controls (notably of sensors) remain strictly on the blue side and during exercises these need to be run by an umpire node if required for Red. This just hasn't been changed because nobody's ever needed it in a Red cell.

Note: the simulation must be running to invoke any of these options. Until the "End of Initialization" message is received from the simulation these options will be unavailable because the interface will not have adequate information to identify scenario elements.

Quick Jump To:

Scramble Aircraft

This interface prompts the user to select the base from the map and then brings up an aircraft status board from which he can choose which aircraft (if any) to launch. The functionality is identical to the Blue Scramble controls.

Asset Controls

The Asset Controls Form interface permits a user to control an aircraft (or defined flight) in terms of:

The interface requires the user to select an aircraft. Once this is done the current status of the aircraft is displayed. The user can then select a motion change and then command it either for that individual aircraft or (by picking the "flight" option) for all aircraft in the same flight. The functionality of this interface is identical to Blue Aircraft Controls, described here .

Note - as is the case with the Blue Asset Controls, this interface is also used to direct naval vessels.

Define Flight

This tool allows the user to define the formation of the individual aircraft into a flight. The relative location of all aircraft can be specified. Once a flight is created, further flight and engagement command can be made once for the entire flights IF THE FLIGHT OPTION IS SELECTED of the aircraft control or engagement interfaces at the time the command is issued. Otherwise the commands are presumed to be directed at the specific chosen aircraft and it leaves the flight if required.

The functionality is identical to the Blue Define Flight interface, described here .

Engagement

The scenario must be running for this to work.

This is the basic interface for assigning, monitoring and controlling engagements versus air targets. This includes air-to-air, surface-to-air, and hypersonic air intercepts. It also includes both engagements directed in a perceived mode (appropriate to force players) and truth (appropriate to umpires). The interface changes according to the interceptor type (e.g. Aircraft or SAM) and the perception/truth mode. The interface changes and functionality is identical to the Blue Engagement Controls, described here .

Air-to-Ground

The scenario must be running for this to work.

This interface permits the user to select an aircraft (or flight) and direct it to fly to a location an perform an air-to-ground attack. The aircraft (or flight) will return to the origin base, assuming they where launched from one during the scenario. The functionality is identical to the Blue Air-to-Ground interface, described here .

Abort Mission

This interface is built around aborting a prescheduled mission and is left over from the days that FORCES was primarily a one-sided (Blue) exercise driver. Basically, when the user selects this option the Abort Control Form allows the user to confirm the end of the mission by clicking on the Abort Current Mission bar. Red aircraft that where launched from bases turn around and return home.

Drop Bomb

The Bomb Drop Controls Form interface permits the user to direct an aircraft to drop a specific bomb at a location. This interface differs from the "Air-to-Ground" interface, above, because it permits the user to select only one type of bomb to drop. The intent of this interface is to interactively control the dissemination of weapons of mass destruction; the Air-to-Ground interface was written with conventional munitions in mind.  Having said this, nobody has used this interface since the early 1990's, while the air-to-ground interface is used regularly and continues to evolve for most robust user needs, so I's suggest trying the "Air-to-Ground" interface whenever possible.

It should be noted that its unusual for interactive operators to use this command interactively. More commonly the WMD attacks are prescripted in the Mission Planner.

The Drop Bomb Controls Form presents the Bomb Drop Data when the user clicks on Select and then selects the aircraft from the screen.  This widget is the standard asset selection interface, and selecting an aircraft from the map cause the aircraft type, tail number, name and simulation ID appear on the form.

The operator also enters the bomb drop specifics:

The user also can also specify the type of Bomb Drop Type:

  1. Nuclear or
  2. Chemical.

After these are specified he can "Enter Command" to execute the command. The aircraft will proceed to the drop point and make the attack. Unlike the Air-to-Ground interface, the aircraft will not return to base but will instead loiter awaiting further instructions.

Escort Control

The scenario must be running for this interface to work.

This interface permits the user to direct an aircraft (or ship) to escort another asset of any type. The escortee and escort might have similar flight conditions (e.g. One aircraft escorting another) or not (e.g. An aircraft escorting a naval vessel in a Outer Air Battle picket location). For this reason it is required that the user control the escort's speed and altitude independently of this form; the escort will not inherit the escortee's speed and altitude.

This interface's functionality is identical to the Blue Escort control, described here .

Launch ASAT

The scenario running for this interface to work.

The ASAT Form interface permits the user to launch a notional ASAT versus an enemy satellite. This interface's functionality is identical to the Blue "Launch ASAT" interface, described here .

Red Status

These interfaces provide access to status boards for red assets. Many of these status boards were designed to emulate operational status boards in SOCCs and similar command centers.

Mission

This status board is designed to report the progress of a massive air strike against CONUS. When this is selected, the RED Mission Status Board Form appears with all Red missions listed.  The form has several columns with the pertinent mission data listed under them. This includes:

Worldwide Airbase Status

This selection, the WORLDWIDE AIRBASE STATUS Form , presents the airbase status of all bases worldwide.  It is identical to the World Wide Base list under Blue Status and described here . The form devotes a line for airbase with the following data:

Red Airbase Status

This selection provides a rundown on all red airbases in the scenario. Selecting this option will generate the RED AIRBASE STATUS Form , presenting the current airbase status of the Red bases in the current theater. The form devotes a line for airbase with the following data:

Note that a number of the fields in this status board are populated with information input when specifying the individual asset (airbase) in the Mission Planner. These include runway length, limiting factors and remarks. To access these info fields in the Mission Planner edit the specific airbase and then go to the "Special->Airbase Information " option. The appropriate fields will be displayed. Change the data and SAVE and the next time the scenario is run the new information will be presented.

Mission Status

This status board was tailored to monitor an air attack on CONUS. This selection, the RED MISSION STATUS Form , presents the airbase status of the Red bases in the current theater. The form devotes a line for airbase with the following data:

Note that a number of the fields in this status board are populated with information input when specifying the individual asset (airbase) in the Mission Planner. These include runway length, limiting factors and remarks. To access these info fields in the Mission Planner edit the specific airbase and then go to the "Special->Airbase Information " option. The appropriate fields will be displayed. Change the data and SAVE and the next time the scenario is run the new information will be presented.

               AD Kill Status

This status board was tailored to maintain a running summary of Air Defense Kills during an attack. The functionality is identical to the Blue Air Defense Status interface, described here.

Group Status

This is the basic interface for determining the status of specific groups. The functionality is identical to the Blue Group Status interface, described here.

Group Locations

The Group Locations Form presents all the locations of the Force B Groups along with the time of the report.  This interface's functionality is identical to the Blue "Group Locations" interface, described here .

Subsystem Status

The Subsystem Status Form presents a detailed status report for subsystems on a selected asset providing an interface for modifying the subsystem status. For the Red Force player the only modification option is to reset the on/off button. The umpire, however, can restock the subsystem or kill it outright through this interface.

This interface's functionality is identical to the Blue Subsystem Status interface, described here .

Jamming

This is a macro command to control jammers for all assets on a side. This option allows the user to select the type(s) of jamming desired.

This will affect sensor jammers. Thus it affects those jammers that operate to disrupt the enemy's surveillance picture. It has no effect on self-defense jammers versus fire control radars or armament; targeted assets are always assumed to use these if they're available. If you really want to turn these off during a scenario execution go to the " Subsystem Status" interface (described above) and turn off the jammer subsystem.

This also has no effect on communications jammers.

Individual Jamming

The operator may also tailor the type(s) of jamming required for a specific Jammer asset by using the Jamming Controls Form . This is useful for complex EW attacks against the enemy's surveillance picture. It has no effect on self-defense jammers versus fire control radars or armament; targeted assets are always assumed to use these if they're available. If you really want to turn these off during a scenario execution go to the "Subsystem Status" interface (described above) and turn off the jammer subsystem. This also has no effect on communications jammers.

The asset to perform jamming (or stop jamming) is selected through the standard asset selection widget at the top of the interface. After the asset is selected the operator then picks the type of jamming capability required for this asset by altering the operational capabilities of each or all the following buttons:

The command is automatically sent when the user clicks the button.

Midair Refueling

As with all these interfaces, the scenario must be running for them to work.

The Refuel Controls Form interface permits the user to select an aircraft to refuel and a tanker to refuel the aircraft. Then the user has to hit the "Enter Command" button to execute the command. This interface's functionality is identical to the Blue Refueling interface, described here .

Jettison

This is left over from the days when FORCES was a one-sided wargame modeling a massed air attack against CONUS. The intent was for a selected bomber to dump all of its ordinance at a point a return home. The interface is somewhat redundant with the Air-to-Ground interface.

The Jettison Controls Form allows the operator to choose a specific aircraft and command it to jettison its bombs at a specific latitude and longitude. The bomber is selected through the standard asset selection widget The user then types in the latitude and longitude and clicks on the Enter Jettison Command bar.