Runtime Blue Controls

This interface permits force player (i.e. Blue player) control and monitoring of of Blue 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) Blue controls are located under the "Ground Force" controls.

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:

Operations Controls

These commands control the operations of assets in the scenario. At least that is the intent, but if you don't find the control you want of assets try the following options as well:

  1. Scenario Controls->Blue Controls->Sensors->Sensor Controls. This is used for specialized sensor site control and maintenance functions.
  2. Scenario Controls->Ground Force Controls. This is used for direct-fire ground combat, ground unit maneuvering, and air-to-ground controls.

Here are some quick links to help you navigate to the interface of interest

Scramble Aircraft

This is how aircraft are launched from a base. When the operator selects this option, they MUST also click on the base located on the map (screen) from which the scramble is to occur.  When this selection takes place, the Status Board Form appears with the current readiness status (the time in which specific aircraft are prepared to become airborne) of the aircraft stationed there displayed.  All aircraft currently stationed at that particular base are divided into types (e.g. B-52, F-16 etc.)

The operator then chooses the specific type of aircraft that is to be scrambled.  This activates the  Scramble A/C Form , which is used to select the number (quantity) of that type of aircraft which are to scrambled.  For most uses you can ignore the complex components of this interface.  Usually the user just has to set the number of aircraft to launch (ranging from 1 to 4) and click on the "Send" button.  The aircraft should show up heading northeast from the base in the next few sim updates.  At this point the user can choose to command the aircraft individually through the asset control interface, or group them into a flight through the "flight controls" and then control them as a unit.

The rest of this description will focus on advanced use of this interface.  This interface permits the user to specify flights from an airbase either immediately and with override, or on a as-available in accordance with an ongoing ATO plan.  Specific components of this interface include:

Asset Control

This interface provides both the primary means to control aircraft already in flight (use the Scramble Aircraft interface to launch them from bases) and a means to monitor their current status. Selecting this option will produce the  Asset Controls menu. First the user needs to select an aircraft for control by setting the selection filters (if desired, clicking on "Select" and then clicking on the icon on the map). For more information on the asset selection widget click here . After selection the data on the object (Type, Tail #, Call Sign, and Sim ID) appears on the  Asset Controls Form . In addition the current location, speed and heading is reported in the lower part of this widget.  Finally, there's a "Flash on Map" option that will indicate the asset's location on the map.   This is useful if the asset is either picked from the list or it's been a while since it was picked and you've lost track of it's position.

This should be all you need to do to use this interface for monitoring, but to use it to control an asset you'll need to pick a command. Select the control option on the  Select Motion Type portion of this form. The user may select one motion type from a list including:

Define Flights

This tool allows the user to define the formation (relationship of each asset from another asset of the same group or unit) of the individual aircraft (or ground vehicles) within a flight of aircraft (or group of ground vehicles).

The Define Formation Form appears.  The user indicates whether the assets are to be Air or Ground types by activating one or the other with the button on the lower portion of the form. The user then clicks on the Select Map Area bar and picks a map region (two opposite corners). 

The defined assets then appear on a grid included on the form as shown here .  Text identifying the assets is also included on the table on the lower portion of the form.  Each asset is listed by: Name , Type, Tail #, ID, X-Offset, and Y-Offset .   The representative size of the grid squares may be altered by clicking on either the Zoom In or Zoom Out buttons.  The size of the area on the form is indicated at the bottom of the block (e.g.500.0 Meters).

Elements on the grid may be moved (relocated) by utilizing the left mouse button to grasp the asset and dropping it on the desired location on the form. Alternately, they can be removed from this list by highlighting the line with their information and selecting "Remove Selected Asset From List". This will not eliminate the asset from the scenario, it will simply be removed as an element of the newly defined flight.

Data on each element may be called-up by clicking on it with the right mouse button.

Finally, none of this matters until the user clicks the "Accept" option.

Engagement Control

This is the master control option for air engagements. This includes air-to-air and surface-to-air (SAM) engagements. When selected a large Engagement Monitor Form appears with both the Blue and Red sides represented.  If the interface was called from the blue side blue (friendly) will be on the left, when called from the Red controls the red will be on the left. The consistent logic is the monitor on your asset is on the left.

This interface is a very powerful control interface for air engagements and as such has been used in variety of different uses. While most of these interfaces are similar enough that special attention is not required to the changes to the interface based upon the changes in calls, there is one important interface difference that umpire users will need to be aware of. There are two modes of calling this interface; in the first (and principle) mode is calling it while in perceived mode. In this case the interface will show "Track" options along the menu bar. In this case the intercept will be commanded against the sensor and/or interceptor perception of the situation. This means that the interceptor might not be doing what you think and you (as the controller) will need to pay close attention to the intercept - as a real controller would. The second option is available only to umpire users, and permits an intercept based on scenario "truth". In this case the menubar on the top of the interface will list "Target" and you'll be able to pick an actual target icon. After this the interface is much less demanding, you just have to verify that the interceptor is provided with intercept directions, rules of engagement, and adequate speed, altitude and missiles. And maybe some luck.

There'll be more on the specifics of how to handle the two different intercept modes (truth and perception) later. For now, let's focus on the common parts of this interface.

The first thing the user needs to do is select an asset to make the engagement. This is the interceptor(s) that will make the engagement or the SAM site. The commands to make this selection are found under the "Asset" option on the menubar. Options include:

Once the asset is selected the the menubar on the Engagement Monitor Form will change to reflect new options, as shown here . The user generally wants to create or update an engagement using this form. There are only two ways to make an assignment

  1. Pick a track (or a target in truth mode) and then use either "Command->Assign Target" or "ROE->Engage" to pair the interceptor (or flight) with the target. What is done from this point on depends upon the ROE and maneuver commands. The only legal tracks are the boxes drawn on the map display, like in this example . The track boxes in this example are yellow, indicating their IFFN status is unknown. The track boxes can also be white (friendly) or red (hostile). Any color track box can be engaged.
  2. Alternately, the user can command an engagement without a track (or target) being selected or go to "Command->Search". In either case the interceptor (or SAM) will engage any air targets that pass "close" to it. At this time close means that the threat must get within 20 miles. Digital intercept can not be used in this mode; the interceptor must be vectored in. This mode is very useful in an ECM environment where tracks might not be forming correctly, but is very dangerous in free fire because there's a possibility of fratricide.

In general, the first mode of engaging a specific track is selected, so the "Track" options will be discussed first.

Track Options:

These are the Track options when running in perceived mode (as force players must do). The user can choose to select a new track by clicking on that option and then clicking on the new track on the map. The information on that track will appear in the right of the Engagement Monitor. Note that this DOES NOT initiate an engagement; it's the user's responsibility to initiate the engagement from this point by clicking on either the "Command->Assign Target" or  "ROE->Engage" options on the Engagement Monitor. This is intentional so that the user can review the track states and range/bearing information from engagement options without committing the command until desired.

Alternately, the user can select the "Use Last Updated Track" if the interceptor has already assigned. This will go through the information on that interceptor and find the most current track information for tracks assigned to that interceptor (it's possible to have multiple tracks simultaneously assigned to a single interceptor or SAM site). The right side of the screen will then be updated with the most recent information. NOTE - this data might still be old, especially if the track is no longer active (e.g. It's terminated due to ECM or range limits). For this reason it's a good idea to check out the "Utilities->Highlight Assigned Track" option to highlight (on the map) where the interceptor "thinks" the track is. This could be different from the user's assumption because the interceptor model projects where the track should be based upon the last information provided to the interceptor and/or onboard avionics detections.

Finally the user can select "Next Track" . This (like the "Use Last Updated Track" option) assumes that the interceptor already has assignment(s) and retrieves track data from the interceptor assignment list. If there's a current track displayed that the interceptor is assigned to this process will bring up the information on the next track in the interceptor's track list. Alternately (if there's no information on the right side of the Engagement Monitor or the interceptor's not assigned to that track) the first assignment in the list is presented. All caveats in the "Use Last Updated Track" description apply and should be reviewed if questions arise.


These are commands for an interceptor. The "Search" and "Auto Intercept" options are not available for SAM sites since these involve interceptor maneuvering, but otherwise the commands are the same for SAM sites and interceptors.

ROE (Rules of Engagement)

These are alternate rules of engagement for the specific interceptor/target pair. Options are:

Just what the name implies. Options are:

Interceptor Maneuvering Controls

The Heading, Speed and Altitude interfaces on the Engagement Monitor Form are interactive interfaces. In normal mode ( example ) they report the current interceptor flight status. But when clicked an entry window appears in the left that permits the user to inputs a new value for any of these. Sample . Typing a <carriage return> after the value is entered causes the command to be sent.

The Lat and Long, Range and Bearing blocks indicate the geographical location, range and bearing of the target.

Options allow the user to specify the track that is to be monitored in the right part of the screen and MORE IMPORTANTLY the track that all subsequent assignment, Current ROE & update commands will reference.

Air to Ground

The Air to Ground Control Form is the interface for commanding an aircraft to bomb a ground target. The aircraft will then return to it's recovery base (if specified in the Mission Planner) or will circle at the weapons launch point and wait for the operator to pick it and send it on another mission (or, alternately, be shot down or run out of fuel).

The top part of this form is a standard asset selection widget (with controls defined here ) that is used to select an aircraft from the map. This is the aircraft that is to bomb the target. If you want every member of a flight to bomb the target click the "Flight Controls" checkbutton and then pick any aircraft of the flight. This assumes the aircraft are already in a flight. If not, form the flight using the flight control interface. When the aircraft is selected the Bomber  Type, Tail #, Call Sign, Sim ID # and Latitude and Aircraft Longitude lines are filled in.

Next the user needs to tell the bomber where to attack. He can either type in the lat/long or click on the Select Target Area From Map bar and then click on the area on the map. Controls of interest are:

The Range to Target (distance from bomber to target, e.g. 86.82 NM) and the Heading to Target (heading to target from bombers position, e.g. 331.2 degrees)  are updated when the target point is selected.

Finally, the user needs to click on the "Enter Command" button to execute the command. Notification that command was sent will appear in the Message Area of the FORCES Master Controls.

Midair Refueling

This Refuel Controls Form interface permits the user to select an aircraft and a tanker so that the tanker will refuel the aircraft. The aircraft selection widgets are standard asset selection interfaces. Both the aircraft to be refueled (Customer) and the Tanker are selected either from the Map or from the List by selecting the applicable buttons on the form and the Enter the Command bar is activated. After the aircraft & tanker are selected they will rendezvous and the tanker will refuel the aircraft according to the aircraft's max fuel load, the tanker's available fuel in the fuel bladder, and the throughput rate of the tanker subsystem as defined in database prototyping. This will happen as long as the aircraft to be refueled and the tanker or not otherwise directed before the refueling occurs, and they both survive long enough.

Escort Controls

This interface permits the user to specify that one asset should escort another. While logically simple, the interface is complex because the interface is designed to permit escort control across sides (e.g. A blue interceptor can be commanded to escort a red bomber or a drug runner) and across assets in different mediums (e.g. An interceptor can escort a naval vessel, as would happen when modeling the Outer Air Battle around a carrier group).

The top part of the interface has four options:

  1. Select Blue Escort
  2. Select Blue Escortee
  3. Select Red Escort
  4. Select Red Escortee

The operator must select an escort element and an escortee. The escort configures its flight path to escort the escortee. The escortee continues doing whatever else it was doing before or is subsequently commanded; it does not make any flight adjustments for the escort. Thus a carrier (as the escortee) would continue it's path while the F-14s on Outer Air Battle (the escorts) would maintain their relative location to the carrier.

When one of the options is selected (e.g. Select Blue Escort) the form expands the size of the blocks of the two Escortee options ( Select Blue Escortee and Select Red Escortee ).  This interface is the standard asset selection widget. The operator select one or the other of the escortee options - usually on the same side of the Escort (e.g. Blue Escort for Blue Escortee).

Finally, the relative geometry between the escort and the escortee as well as the escort flight conditions (altitude and speed) must be defined in the lower part of the widget ( Controls Form ). The relative geometry is identified in terms of bearing from the escortee to the escort (in degrees clockwise from North) and the Final range. These designate where the escort will try to maintain it's position relative to the escortee, assuming it can. The speed and heading entries are required and together support unusual escort situations (e.g. Aircraft escorting ships). Note that if the speed is too low the escort will aim for the escort point but never make it. If too high the escort will perform energy-wasting maneuvers as close to the designated escort point as it can achieve.

Set C2 Assignment Controls

The C2 Assignment Controls Form interface assigns an asset (e.g. Aircraft) to another asset  (e.g. C2 Site ) for the purpose of assigning Command and Control.  Again, the standard interface asset selection widget is used to permit the user to select both the asset being assigned and the controlling asset. Once these are selected from the screen and data for each (Type, Tail #, Call Sign, and Sim ID ) are presented on the C2 Assignment Controls Form . Then the user must click Accept. Note: this tool is most often used to assign airborne aircraft to specific C2 sites or airborne sensors. This is done either to reduce operator (man-in-th-loop) workload or to accommodate communications outages.


The ASW Controls Form interface provides the user with the capability to assign a specific naval asset (aircraft, ship, or sub) to setup an Anti-Submarine search area. The asset will perform a gird search of the area, dividing the selected region into search corridors of the specified size. The asset will move at the designated speed and altitude. Naturally platform restrictions will be observed, e.g. A ship will not be allowed to fly even if you put 100 ft here.

The Searcher (aircraft, ship, or sub) is selected either from the Map or the List (buttons) and the Type, Tail#, Call Sign and Sim ID will appear on the form. The area to search is defined by choosing the Pick Search Region From Map bar and clicking on opposite corners on the map causing the Lat and Longs to appear on the form. Search Width and Search Alt/Depth directions may be typed in the applicable lines.

Orders to either Localize Sub or Destroy Sub are activated via the buttons on the lower portion of the form.
Use negative values if the asset is to perform the search underwater (e.g. Submarines).

View Intel Reports

The Intel Reports Form interface allows the user to both review the intelligence reports just like the Intel Report interface under Umpire Control.

Set Safe Passage Corridor

The SAM Safe Passage Corridor Form interface allows the user to create one or more safe corridors for one or more SAM sites. These are corridors which aircraft can fly through without getting attacked by a specific SAM.

First, the asset (e.g. SAM_Sites) is selected through the standard asset selection interface (Map or List). This causes the Type, Tail #, Call Sign, Sim ID, SAM Latitude, SAM Longitude , and Current Time to appear. Then the following corridor and target definition parameters must be entered on the . These include:

Finally, the user may dictate whether IFFN Required by activating that button. Once the command is invoked SAMs will not initiate an attack against airtracks that fit all aspects of this corridor.

Launch ASAT

The ASAT Form interface allows the user to setup the launch of an ASAT to intercept a target satellite.  The standard asset selection widget at the top permits the user to designate the target. When the ASAT Class is queried, a drop-down window appears with a list of all ASAT classes. These classes are fixed and have nothing to do with the FORCES database. This is because the ASAT model is actually a standalone (non-FORCES) model that runs in a confederated mode. God save us from new programmers playing with asynchronous simulation confederation.

The general ASAT rules are:


Velocity (NM/Sec)

Max Range (NM)













Two other actions are required to complete this process: choice of the ASAT launch site (Pick Launch Location From Map) and the launching the ASAT (Launch ASAT).  The location may be selected from the map or manually entered by typing in the Lat and Long on the form.  Clicking on the Launch ASAT button launches the ASAT.

Evaluate Air Packages

This interface lets the user select and direct entire air packages on missions instead of controlling individual aircraft. While already powerful, this is a new work in progress and some interfaces are weak.

The air packages are defined in the "air_package" database table. Currently there is no Mission Planner interface to this table, but new packages can be defined via pg_access in this table and will appear next time the simulation is run. The idea is to define a package type in terms of the aircraft needed (or desired) and the role of each aircraft. The system will then list the mission in this interface next time and will list all airbases that can support the mission. Currently the system is not smart enough to combine assets from different bases into a single mission.

To manually load the data into the air_package table you need to fill in the following data:

Going back to the runtime interface , a top part of the widget presents the mission type (alternates can be selected by clicking on this button and picking another), the mission location (e.g. Where a CAP is to be placed or an air strike to attack) and package information (how many of what type of aircraft are required for what role). A list of the airbases that can support the mission is presented in the main body. The user can review this list and order the mission just by clicking the appropriate "Command" button. Note that the launch delays are notional at this time - they're still in progress, so the flight might launch sooner or later that that time.

Blue Status

The Status of all categories of Force A assets are included under this element.  These are all dynamic status reports available to the appropriate force commanders (Blue and Red) throughout the execution of a scenario. For the most part these are all developed around the same "status board" utility, which is intended to imitate the status boards maintained in ROCCs and SOCCs. They provide tabular status data on the current situation. They are populated when created and not updated dynamically, so it's important to know the age of any of these reports; if in doubt, request a new report.

Ground Stations

Selection brings up a list of all Ground Stations in the scenario.  Selection of an individual ground station from the list below causes a Status Board Form (similar for all stations) to appear.  Each such Board (e.g. US TACC Status) presents specific data for that class of station:

Status Boards available for the major C2 sites in the CONUS Air Defense scenario (these where all developed under the ADISC2 contract and therefore are CONUS air defense - centric):

C2 Sites

The Status of the C2 SITES includes specific C2 Sites in the scenario.   Selection of any of the individual C2 sites from the list below causes a Status Board Form (similar for all sites) to appear.   Each such Board (e.g. NE TACC Sites) presents specific data for that class of site:

Like the above status boards, these where all developed under the ADISC2 contract and therefore are related to CONUS air defense. It should be mentioned that it's very easy to generate new status boards as required to satisfy alternate exercise or study needs.


The SBR Status Form presents the Space Based Radar data for the selected SBR satellite. The standard asset selection widget is provided in the top of this interface to let the user select a satellite. Selecting the SBR Satellite from the screen places the applicable data (Type, Tail #, Call Sign, and Sim ID) for the satellite on the form.   The satellite can be selected either from the map or from a list, but from a practical standpoint users will generally find it easier to select the satellite from the list.  If you really want to try to pick the satellite from the map make sure you're in the orthogonal view on the maps.   It might also be easier to pick satellites if using the 2D (flat) projection instead of the 3D (default, spherical Earth) projection.  Go the map controls for more info.

Selecting a satellite will update two type of data.  First, the positional data (latitude, longitude and altitude) will be posted.  The altitude is in feet above the surface of the Earth.  In addition, if the sensor has any directives they will be reported as:

Not all satellites will have these limitations, in which case all values are 0.  To set these limits go to "Scenario Controls->Blue Controls->Sensors->Sensor Controls->SBR Controls.

Airbase Status Boards

This element reports the status of air force related assets for Force A.  Five options are available:

Aircraft Menu

After selecting this menu the user needs to select an airbase from the map. After selecting an airbase he'll be presented with the same status board that is used to scramble aircraft . Example . He can command aircraft launches from this interface.

Blue (Force A) Airbases

A list of all FORCE A airbases appear on the Status Board Form .  The data presented on the board in columns are:

Scramble Aircraft

When an airbase is selected from the map, the Status Board for the base appears where the aircraft to be scrambled is highlighted. This, in turn causes a small form (Select #) to appears where the quantity of aircraft to be scrambled is picked.  The details of this interface were described above (click here for more information).

Air Defense Mission

When running in perceived mode a Status Board Form with the current Air Defense status presented appears.

The data presented on the board in columns are:

Worldwide Airbases

The Status Board Form appears with a list of all FORCE A airbases worldwide along with their status.  The data presented on the board in columns are:

AD Kill Summary

This element reports the status of the air defense combat currently underway - specifically the kills (destruction of the hostile aircraft (usually a bomber type) by FORCE A interceptors.

The AIR DEFENSE KILL SUMMARY Form presents this summary on a board in columns under the following headings:

Group Status

The Group Status Form allows the user to learn the status of a specific group by querying its icon on the screen.  Initially the form might show less data; some fields are shown only after a legitimate selection has been made.  The data that appears on the form are:

A specific unit's status is displayed by the operator clicking on the Select Unit from Map bar and then clicking on the unit icon on the screen.  This action causes the data to be filled to the lines listed above.

Group Locations

The Group Locations Form presents all the locations of the Force A Groups WITH ALIASES along with the time of the report.  The name of the group (e.g. 555 th Squadron) is listed along with the locations that may be reported by Name (e.g. Peterson AFB, CO) or geographical location (in UTM).  Note that only those groups with defined aliases in the Mission Planner will appear on this form; if this form is empty it is probable that none of the groups in the scenario have defined aliases.

Subsystem Status

The Subsystem Status Form presents the status of any subsystem belonging to a Force A Asset.  Filter button allows the user to choose the type of asset (e.g. C2 Site) that hosts the specific subsystem.  This asset is then queried from the screen.  Asset data (Type:, Tail:, Call Sign: and Site ID: ) and subsystem information is then sent to the form. Sample . This interface has some active parts that are key. The force players (red and blue) can only change the On/Off flag for a subsystem for assets controlled by their side. The Umpire player(s), however, can change the Alive/Dead flag and the quantity currently onboard. This has proven a very effective umpire screen for updating and maintaining the scenario situation to the umpire's desires.


These are mutually exclusive options for displaying communications connectivity on a screen.  Most of these options are common with the Map Control options for displaying communications status, described here.

The only extra control is the "Communications Band Utilization" report.  When selected, the Scenario Comm Monitor Form of the communications and the relative degree of utilization for Force A.  All Bands are listed on the form along with any current updates.  The following specific items are reported the scenario and total utilization per comm band (as defined in the Mission Planner under "Scenario Defn->Communications"). Also reports the jamming effect at this time in terms of degradation.

Scenario Specific

This allows the user to select the Status Board Title for the scenario.


This menu lists permits control of both the sensor displays on the map as well as providing specialized operational control for modeled sensors. The controls are shared with the Red sensor controls; if you don't find required sensor controls under the Red Force controls try controlling the Red Sensors from these interfaces.

Sensor Displays

These options are described in the Map Control documentation.  Click here to jump to that documentation. 

Sensor Controls
These are the controls associated with controlling sensor operations and performance.  Options are described below.

RHAW Controls

This interface enables the user to sort and filter collected RHAW reports to geolocate and type threats from RHAWS reports.  A pretty complete description of this interface is described in the FAQ, available here.  The referenced description focuses on using empirical (i.e. real) data, but the reports from a simulated RHAWs sensor can be reviewed and analyzed identically (although the simulated sensor variations are less than seen in real life).  If you're using simulated inputs just start at step 11 of the referenced document.  

Troubleshooting Note - If you don't have any data you might not have any active RHAWS sensors in the scenario.  To see if this is the case return to the Mission Planner and go to Scenario Defn->Scenario Evaluation->Subsystem Evaluate By Type and see if any of the scenario assets with RHAWS sensors on board.  If you do (or are not sure), review the subsystem definition under Database Prototyping for this subsystem.  It must be defined as an RHAWS sensor reporting RHAWS message formats.  If the sensor is in the scenario and correctly defined (both in terms of type and message formating) verify it's active (e.g. airborne sensors are not active until the aircraft is flying), and in the right area.

SBR Controls

This interface allows the user to reset the area of view of a satellite. The SBR Controls Form presents Satellite Data which is displayed once the specific satellite is selected from the screen through the standard asset selection widget. Data includes:

The interface will then permit the user to specify right and left viewing limits for the satellite.

Note: This interface currently only works when the map is is 3D projection.

OTH Controls

This interface lets the user review the performance of Over the Horizon (OTH) radar sites and command barrier changes (i.e. Where the site should spend its time looking). The OTH Controls Form displays the Site Data of the Over the Horizon sensor which includes:

This data is displayed once this particular type of sensor is selected from the screen through the standard asset selection widget.

Once an OTH site is picked, the user may query the Request MUF Report bar on the form.  This will generate the current Maximum Usable Frequency report for the OTH site (a new one is generated every 15 minutes). The MUF is color coded green for where detections can be made (based on ionospheric bounce), yellow for marginal conditions, and red for outages. Sample . MUF Reports may be removed by selecting the Remove MUF Reports bar. Note that this report should be combined with the auroral cap overlay to determine where the OTH radar can actually see.

The coverage range of the OTH may be changed for scenario use by typing and entering the data in the Min. Range (NM) and Max. Range (NM) lines on the form and selecting the Enter New Coverage bar. These constitute a command to change the barrier of the OTH site, which should alter the site's detection performance.

Sensor Maintenance

This permits the user to take sites down for maintenance during routine operations or transition to combat. The Sensor Maintenance Controls Form displays the Site Data. The top part of this interface is the standard asset selection widget with the type, tail, name and sim ID information for the selected site (after it's selected)

The user may also dictate the operational status of the sensor by selecting either the Operational or Down button and entering the change (Enter Change bar). This will take the site down for maintenance. This will affect the likelihood it will fail after returning to service, but it will be unavailable until the maintenance is completed. The time to complete maintenance on the site is as defined for the sensor platform type in database prototyping.

Height Query

This interface allows the user to command a height finder radar in conjunction with a JSS or other raw radar site. This is modeled as a separate sensor at the same site working on different frequencies and more capable of differentiating the elements of a mass raid. Often this provides a viable interface for reducing jamming effects relative to a raid.

The Height Request Controls Form displays the Site Data once the operator selects it through the standard asset selection widget on the top. Information available after the site is selected includes the type, tail, name and simulation ID of the site.

On the Request Specs portion of the form the user receives data on the sensor site such as:

The location (lat and long) must be input into this interface for a legal height finder command. The range and bearing are computed from this. The user may call-up this data via the Select Lat/Long from Map bar and then clicking on the map at the target location.

On the lower portion of the form the Response: data will be reported. This includes:

This information is available only after the sensor site and target location are picked and the Command Height Request bar is selected. Then the update is delayed to reflect communications delays. Finally, the data is filled in.

ID Controls

Note:  This is a "shorthand" version of a more robust Track maintenance and Identification capability incorporated in the Radar Analysis Program (RAP).  If you are really intending to do a significant amount of track maintenance it's suggested that you change to the RAP interface (controls to do this are found under the "Scenario Controls" option) and use the RAP controls (documentation here).  Note that you can easily toggle back to the standard JFORCES controls from RAP.  The rest of this description will focus only on the stripped-down version available directly under the JFORCES controls.

This interface lets the user select track boxes from the screen and either review or update the information on these tracks. Originally developed for aircraft control, the Identification Controls Form lets the user identify a track existing on the scenario screen.  When a track is queried, the data available for that track is presented on the form. This data includes:

The Track Origin or type section allows the user to select between four options:

Four other functions are provided to the user on this form.

Start New Track

Allows the user to initiate a new aircraft track.  When a new track appears in the air defense system, it is initiated as an unknown temporarily until it can be identified.  This tool simply begins the identification procedure by putting the new track into the air surveillance system.  The New Track Input Form provides the user the means to manually select the new track via two picks from the screen.  Estimated track speed and heading along with Lat/Long are presented on this form.

View/Modify Existing Track

This tool allows the operator to view the particulars of an existing track.  When the track is selected - picked from the screen - the data related to it appears on the form.

Delete Existing Track

This tool allows the operator to delete an existing track by choosing it from the screen.

Perform FAA Check

This tool allows the operator to perform a check on an existing track.  The specific track's position, speed, heading, and altitude is the track data important to the FAA controllers.


Terrain Masking Display

The Terrain Masking Selection Form displays the Site Data (the standard asset selection widget) which allows the user to select the sensor site for the terrain report for the screen and then reports the site's type, tail number, name, and simulation ID. It's location is also reported in the lower part of the interface.

The Target Altitude is entered (typed) by the user in order to provide the system with terrain masking parameters. After filling this in the user can request the report, which should look something like this . Rays emanate every 2 degrees from the sensor site and terminate where they would be restricted from detecting a target at the specified distance. This can be used to determine where terrain (e.g. Hills) cause detection outages for the site.

Note: If the detection overlay is a circle, you might not be using DTED data. This could happen if :

  1. DTED data is not loading into the $DTED_DIR directory (generally /data/DTED) for this region, or
  2. You're not running the DTED model. To check this go to "Scenario Controls->DBA->Plan Run and follow these software model instructions .

Clear Corona Overlay

Allows the user to clear the Corona overlay hat was generated by the "Terrain Masking" option (above) when requested.

Sensor Tasking Status

The Sensor Tasking Status reports current sensor tasking, as defined for specific sensors during the Mission Planner. Sample .

Show Effects of RCS and Alt.

The Limited Sensor Coverage Form provides a quick graphical overlay on the map for typical radar coverage in this scenario against notional threats of the specified altitude and speed. This provides a planning tool for tasking mobile sensors (e.g. AWACS) to cover holes. The Limited Sensor Coverage Controls Form allows the user to insert data into two lines:

Graphical Controls

Note:  This is a stripped down version of a more robust Track and sensor display options available  in the Radar Analysis Program (RAP).  If you are really intending to do a significant amount of track maintenance it's suggested that you change to the RAP interface (controls to do this are found under the "Scenario Controls" option) and use the RAP controls (documentation here).  Note that you can easily toggle back to the standard JFORCES controls from RAP.  The rest of this description will focus only on the stripped-down version available directly under the JFORCES controls.

With  selection the Graphical Control Form appears with several options. The following controls support the types of data to be graphically displayed.   The operator chooses the applicable ones to be displayed by activating each on the form. The controls are more applicable to sensors providing raw radar returns in an air defense environment.

The operator selects one of three different modes: Mode 1, Mode 2, or Mode C.
The Send New Mode bar is used when one of the three Modes is changed.
The Sensor Display Controls Form allows the user to insert data into two lines:


Create Communication Links

This allows the user to create a new communications route built of distinct communications links between specific assets using specific communications suites. This is a very dynamic screen that will grow as sites are selected. Initially, the Communications Link Definition Form provides a standard asset selection widget permitting the user to select the communications source (or sink). Generally the communications direction is unimportant unless the communications suite as defined in database prototyping specifies the suite can not handle 2-way communications.

Once the communication source is identified, the interface displays the site type, ID, name and simulation ID. The user can then select the transmitter. When he does this the form changes to allow the user to select the next site in the communications route. The transmitter and receiver communications suites must be selected. The user can add more elements to the route ( example ) until the communications are complete to a C2 site. Then he needs to select the "Send Comm Route Defn" to activate the route.

Alert State

These permit the Blue player to reset the alert and readiness levels as desired and broadcast them to the automated modules and other players in the loop (on an exercise).

Wartime ROE (Off/On Button)

This control simply implements Wartime Rules of Engagement.  These rules eliminate most restraints imposed on the applicable FORCE A forces in regard to aggressively responding to the opposing forces.

Modify Blue Alert Status

Selection of this option allows the user to change the Alert Status of Force A forces.

Modify Blue DEFCON

Selection of this option allows the user to change the DEFCON of Force A forces.

The exact actions which each individual units of FORCE A implements when an increased DEFCON is declared are classified.  These actions differ according to the units mission, status, location etc.


These are NMD specific commands that reset the interface for Human Factors Experiments. The most useful option is "BMC3 NMD Screen - Option 1".  Note that these screens were constructed for use with limited NMD scenarios and their performance in other scenarios might be erratic.

ITWAA Screen

The large FORCES NMD BMC3 SCREEN Form is presented.  On this screen the user is presented with a wide array of information concerning the status of the Battle Management Command, Control and Communications.  This data is updated as the scenario is run. WARNING - the mission controls are NOT available in this mode. This is because this interface is intended to be connected with a distributed execution where another participant would have the umpire controls.

The screen displays:

A map of the world along with:

Assessment block:

CINC NORAD - This assessment may be set via a drop-down list of:

Radar Sys Validation Validation may be set via a drop-down list of: Valid or Invalid.

This indicates whether the FORCE A radar surveillance system is or isn't reporting the object of interest.  And, if the reports coincide/agree the other information being reported.

SBS Sys Validation Validation may be set via a drop-down list of: Valid or Invalid.

This indicates whether the FORCE A space based surveillance system is or isn't reporting the object of interest.  And, if the reports coincide/agree the other information being reported.

Sensors block:

The Status button presents a list of the sensors and their individual status.  The Sensors are listed by name (e.g. UEWR1) along with the status of each displayed in color (G, Y, R).

The Coverage button presents a list of the sensors and their individual coverage capabilities.

Events block:

The DEFCON button allows the user to set the desired DEFCON level via a drop-down list.

The ZULU button allows the time to be presented in either Zulu time or Local time.

At the bottom of the screen the Track Events data is displayed.

When the simulation is running the following track event data is displayed:

Original BMC3 NMD Screen

Please see the NMDUL End User HFE from Spring 2000.

BMC3 NMD Screen - Option 1

Please see the NMDUL End User HFE from Spring 2000.

BMC3 NMD Screen - Option 2

Please see the NMDUL End User HFE from Spring 2000.


Most of these utilities have been moved. Currently the only option left here is the ability to turn the automated air defense module on or off. WARNING: This will work only if the air defense rules are previously defined under the Mission Planner.

Air Defense Auto C2 (Off/On Button)

When activated, provides Automatic Command and Control of the combat assets (e.g. aircraft).  Once the interceptors and target have been designated and the ROE for the interception have been dictated by the operator, the simulation can automatically control the interception portion of the mission.  All interception rules and engagement factors are implemented just as a human controller would do.