Notes on Reading In ATOs

JFORCES can accept ATOs written in the 1998 or 2000 format as inputs to initialize scenario aircraft. This is done within the Scenario Designer under the “Scenario Design->Design macros->Mass DB Updates->Read in ATO” GUI path. These are read in the native format, but there are some tricks to reading in the data. These are:

  1. This process assigns aircraft, but it does not create them. it's up to the analyst to create them. But as covered below it provides information to help populate the aircraft information correctly.

  2. This only needs to be done once, but can be run multiple times if required. It cleans out pre-existing air mission data at the beginning of the ATO read-in. This is a mixed blessing. It permits users to run this process multiple times and get the expected results. But it does wipe out any information on missions that were loaded using any other mechanism (e.g. through user specification. So run this process before assigning any air missions through specific operational tasking.

  3. The JFORCES' ATO only assigns aircraft to the “teeth” missions. These include: INT, FCAP, DCA, XDCA, ESC, EW, AEW, XEW, XAEW, XINT, XATK, XCAS, SEAD (the abbreviations are in accordance with USMTF standards).

  4. The ATO relies on having the key aircraft types, locations, airbases and squadrons. For this reason loading an ATO is generally not a one-time pass activity. Instead an ATO is read in, parsed, and any generated errors are rectified prior to actually executing the command to load the aircraft into the scenario. To do this use the GUI path specified above, select the source ATO file to read in, and review the resulting error report. A sample report follows:

The end of the report gives a synopsis of categorical problems, and generally these should be fixed before the small problems are addressed. But after these are addressed scroll up and consider all of the problems highlighted in red. Lines in green confirm that the mission specs have been loaded into the database.

  1. To fix common errors proceed as follow: