FORCES 101 Outline
Intro to JFORCES
Forces is a Simulation of:
- Military Systems (What they Are/What they Do/How)
- Groups (EG TO&E Elements)
FORCES Incorporates a Robust Environment
- Route Planning/Mission Planning
- C4ISR: Directing/Controlling Assets
Employs both Natural and Man-Altered Environment:
- Nuclear effects
- Data Analysis
- Other Interfaces
How to Login:
You should see Sun's Common Desktop Environment (CDE)
- CDE Layout Outline (Will be discussed in Class)
- Open A Terminal Window
- Start JFORCES
- Check for Ongoing Processes:
- Type "forces_status" - Will List Ongoing Processes
- Type "kill_all" or "kill_mmi" As Appropriate to Stop Ongoing Processes
- - Type "start" to start the JFORCES environment
- Basic JFORCES Environment has a Single Map Window and One or More Menu Windows.
- Use "Map Controls" to Control the Map
- The Most Used Functions Can Be Found Under the "Quick Point" Controls
- All Map Interfaces Use Common Techniques
Map Control Example
No Map Inputs Zoom In
One Map Pick Move Center
Map Area Pick Select Area
FORCES Mode Control
Start Scenario - Starts a scenario and optionally connects the
MMI (Man Machine Interface) to the run
Connect - Connects the MMI to an ongoing scenario on the
some computer or another Computer
Mission Planner - Starts a graphical tool used to set up scenarios.
- Typically Requires Additional Support from the "Scenario Generator" and
the Run Configurator to Create Complex Scenarios.
- Go to "System Controls" -> "DBA" -> "Plan Scenario" to start the Scenario Generator
- Go to "System Controls" -> "DBA" -> "Plan Run" to start the Run Configurator
- The JFORCES Environment must the killed and restarted between Mission Planner Sessions and Runtime Execution sessions
Example Scenario Generation Using the Mission Planner
Enter "System Controls" -> "Mission Planner"
When Queried for a scenario choose the "New" button
Use the "tactical" database and select a useful name
Note: The tactical database is an uncontrolled database. As such
the data is partial and questionable, but tends to be useful for
training and quick checkouts
Create Key Elements
Select a Map of the Region of Interest
Start creating Scenario Elements
Go to "Mission Planner" -> "Create/Edit…" ->"Individual Assets"
Pick "Red", "Air Base", "Red Primary AB"
As a general rule, Scenarios are easiest to control if the Bases are created first
Select "Location"-> "Pick from Map" and click on a Map Location to Place Base
Give the Base a Unique Name
- Must the Unique in the First 4 Characters
SAVE THE DATA!!!
- This is the most frequently committed error associated with the Process!!
Create Blue Airbase
- Pick "Blue", "Airbase", "Blue Primary AB"
- Pick "Location"->"Pick from Map" and select map location for blue airbase
- Give the airbase a unique name
Create Red and Blue Squadrons
- Close "Asset Definition" menu
- Pick "Mission Planner" -> "Add/Edit…"->Squadrons
- Pick "New", and Enter Name, Call Sign and Base for a Red and a Blue Squadron
- Don't worry about adding aircraft … Yet!
- Double Click on Each Squadron
- Select "Add New Asset By Type"
- Select aircraft Types
- Use MIG-29 for Red, F-16C for Blue
- Note that the Mig's are not as well defined as the F-16C's
- The MIGs will therefore perform better than they could in actuality
- FORCES uses date to realistically restrict the performance of assets
- This is useful for "Quick Look" Experiments.
- Use the Slider to Create 8 of each aircraft type.
- Save the Aircraft
- Without Sensors the Assets can't engage!
- Go Back to Asset Definition to create sensors
- Pick "Red", "Ground Sensor", "Red Eye" to create a red sensor.
- Locate Red sensor with a Map Pick.
- Pick "Blue", "Airborne Sensor", "awacs" to create a blue sensor
- Locate AWACS with a mouse pick (Note that it could have started at base)
Create a Route
- Click on Route Name in the AWACS definition
- A (Currently Empty) List of Defined routes will be presented for selection
- Enter "New"
- Note that Routes can be reused with time offsets.
- A route definition widget appears
- Enter "New Leg" to start the route
- Pick a "Direct" motion. Set the Altitude to 30000' and speed to 350 knots.
- Enter "Next Leg" to Go to the next leg.
- Change motion to "Station", leave altitude and speed as before. SAVE.
- Close route widgets
- SAVE AWACS definition - Otherwise the Route name will be lost.
Modify the Route of an Existing Aircraft
- Go back to "Mission Planner"-> "Edit/Add…" ->Squadron
- Double-click on a squadron
- Double-click on an aircraft type
- Double-click on a particular aircraft - the "Asset Definition" widget will appear
- Click on Route Name - create a new route as before
- New routes can be complex - create a circuit into a target area with a form-up delay.
- Because the "Mission Planner" is still under development, some options are not currently supported
- Example: You must use the "Scenario Generator" to actually Land the Aircraft.
- Close the Route definition widgets, SAVE the asset data, and close all widgets except the top-level controls
- Review the "Mission Planner"->"Summary"-> "Assets by Type" to verify that the desired players are defined.
- Enter "Kill MMI" to shut down the Mission Planner and make the actual Run.
Starting a Scenario Run
In addition to scenarios, there are Run Configurations
- Run configuration includes data on timing and data to be used.
Run Configurations Need to Be Created Only Once
To Create a Run Configuration:
- Enter "start" to restart the JFORCES environment
- Go to "System Controls" ->DBA-> "Plan Run" to start the run configurator
- Follow the directions to set up the configurator
- Note that this interface uses "hotkeys" to simplify setup.
- Proceed to "Maintain Run.."
- Create a new run configuration. Typically it is easiest to maintain run configurations if the scenario name is used as the run configuration.
- Review the configuration options. The details associated with each of these options can be set in the run configurator by going to "Associated Run…" instead of "Maintain Run…". We'll discuss one of these options in class
- (F1) - select "Tactical" and your scenario
- (F2) - select "default" for the timing record
- (F3) - select "allutils" for the utility file
- (F4) - select "c2-off" for the software configuration
- (F5) - select "readdb" for the replay configuration
SAVE, and then hit "end" for all menus to exit the Run Configurator
- Go to "System Controls"->"Start Simulation" to start a scenario
- Pick your run configuration (NOTE: NOT your scenario).
- For the most part the defaults are fine, but typically it is best to start the simulation monitor the first time you run a scenario
- Set up the map while waiting for the simulation to initialize (that is, load the data from the database into memory). The blue bar in the control widget will announce "Received End of Initialization" when the simulation is ready to start (Find this option under "System Controls" - Note that the System controls change according to the option you are in - this is common in JFORCES controls).
- Note that occasionally the "Received End of Initialization" message is missed while working with the maps. If the initialization seems to be taking too long and/or the simulation monitor stops updating, just hit "start" - it won't hurt anything
The runtime controls are best learned through freeplay. As an outline, we will introduce each of the following:
Collecting and Reviewing Data
Restart the simulation. To do this:
- Select "Kill MMI" from the "System Controls"
- Enter "kill_all" at the terminal prompt
- Enter "start" to restart the JFORCES environment
Set the Data Collection Options.
- Select "System Controls" ->DBA ->"Plan Scenario"
- The Scenario Generator will come up. Set it according to the instructions
- Note that the controls are similar to the Run Configurator
- Pick the Scenario Generator Option, Select the database and scenario that you created
- Go to "Data Collection…"
- Go to the "Data Collection Options" (Currently the fourth choice)
- Set data collection to "1"
- Set message sets to "allmsgson"
- Set Class sets to "allclasseson"
- Leave the Object set blank - note that EITHER the class or the object set should be set, not both.
- Set the collection frequency to 10. This will report updated locations every 10 occurrences for periodic reports (e.g. ongoing detections)
- Note that the message set and class options can be reviewed and edited by using the appropriate option on the "Data Collection" menu
- Run the scenario for a while (Until some interesting engagements occur)
- Load the data by selecting "System Controls" -> DBA -> "Scenario.." ->"Load Data for Analysis" and selecting "Load" on the presented widget
- Wait while the data loads - completion will be indicated in the blue bar on the control widget. The scenario can be restarted after the load is complete by selecting "System Controls"->Resume
- To check out the data select "System Controls" -> DBA -> "Scenario.." ->"Data Analysis". Select the current database and scenario first, and then the appropriate run ID.
- Note that this function can be run without an ongoing simulation - just start the JFORCES environment and go to the Data Analysis option.
- Likewise, run results can be loaded after a run is completed.
- If a "Broken Channel" error is received, restart the JFORCES environment (Connect to any ongoing runs, if required).
- Data analysis options will be reviewed during class time.