Air Force Modeling and Simulation

Training Toolkit (AFMSTT)

Air Warfare Simulation (AWSIM) Synthetic Tracking Overview
AFMSTT Software Version 6.2.0.0

Contract No. FA8730-16-D-0001

CDRL No. A004

Document Number: AFMSTT-U-000337

Date December 23, 2019

Revision A

Prepared for: Air Force Materiel Command, USA AFLCMC/HBBC

11 Barksdale Street, Bldg. 1614 Hanscom AFB, MA 01731-2800

Prepared by: Cole Engineering Services, Inc. 12253 Challenger Parkway Orlando FL 32826

DISTRIBUTION STATEMENT D – DISTRIBUTION AUTHORIZED TO THE DEPARTMENT OF DEFENSE AND

U.S. DOD CONTRACTORS ONLY (OPERATIONAL USE) (MARCH 2016). OTHER REQUESTS SHALL BE
REFERRED TO (AFLCMC/HBBC).

WARNING – THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS RESTRICTED BY

THE ARMS EXPORT CONTROL ACT (TITLE 22, U.S.C., SEC. 2751, ET SEQ.) OR THE EXPORT
ADMINISTRATION ACT OF 1979, AS AMENDED (TITLE 50, U.S.C., APP. 2401, ET SEQ.). VIOLATIONS OF
THESE EXPORT LAWS ARE SUBJECT TO SEVERE CRIMINAL PENALTIES.
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Revision History

Revision Date Notes Section

Revision A 12/23/2019 Final version for AFMSTT 6.2.0.0 software release. All
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Table of Contents
1. Introduction ........................................................................................................ 1
2. Functional Overview .......................................................................................... 2
3. Configuration and Usage Overview .................................................................. 6
4. Adaptation Data (adaptation.data) File ............................................................. 8
5. Synthetic Tracking Configuration (synthetic_radars.cfg) File ........................... 13
6. Synthetic Tracking Characteristics (synthetic_radars.chr) File ........................ 17
6.1. Notes ..................................................................................................... 20
7. Secondary Channel Configuration (synthetic_radars_2.cfg) File ..................... 22
8. Runtime Considerations .................................................................................. 24
9. Notes on Current Usage ................................................................................. 25
10. Frequently Used Acronyms ........................................................................... 29

iii
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

List of Figures
1. Synthetic Tracking ............................................................................................. 4
2. Adaptation Data Excerpt ................................................................................... 8
3. Synthetic Tracking Configuration Data ............................................................ 13
4. Synthetic Tracking Characteristics Data ......................................................... 18
5. Synthetic Tracking Secondary Channel Data .................................................. 22

iv
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

List of Tables
4.1. Adaptation.Data Settings for Synthetic Tracking .......................................... 10
5.1. Synthetic Tracking Configuration Data ......................................................... 14
6.1. Synthetic Tracking Characteristics Data ...................................................... 18
7.1. Secondary Communications ........................................................................ 23
9.1. Recommended Settings ............................................................................... 25

v
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 1. Introduction
The purpose of this manual is to provide a description of the synthetic tracking
capability of AWSIM.

1
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 2. Functional Overview

The AWSIM synthetic tracking functionality of the DI provides the capability to
emulate operational radar report generation for certain ground-based surveillance
radars. The typical usage for AWSIM’s Synthetic Radar Reporting is Homeland
Defense personnel training and issues analysis. Using the Synthetic Radar
capability, AWSIM can “stand-in” for operational radars and provide the real-time
radar reports that fielded equipment would normally provide. Operational tracker/
correlator equipment is “stimulated” with realist radar target reports and military C2
personnel can respond to presented threat conditions on their operational display
equipment.

The types of surveillance radars AWSIM supports are F/TPS-43/59/65/75/117s,

ARSR 4, and ASR 8/9s. Each of these radars generates a variation of the CD-2
class of radar report formats. AWSIM supports skin-only, beacon-track and combined
reporting conditions. The emulation of the surveillance radars includes the time
spacing and ordering of radar reports reflecting when the radars “illuminate” various
targets in their scan cycle. AWSIM models the spacing by noting what azimuth
sectors targets appear in and adjusting the time the reports are provided during the
radar’s scan cycle.

The wargame function (WG) performs radar target detection processing based on
the AWSIM scenario (laydown) in the scenario database (flat file) independently of
the synthetic tracking function, but the wargame processing controls the operation
of synthetic tracking indirectly. That is, the wargame can generate and produce
detections and tracks, including TADIL tracks, without the synthetic tracking
functionality. But, the wargame detections gate (throttle or control) the synthetic
tracking functionality to generate synthetic radar tracks.

The wargame and synthetic tracking functionality each have an independent set
of parameters to control the radar simulations. This makes consistency in the
parametric data for the two functions essential for producing usable data for
radar data users (unless the intent is to inject inconsistencies to test correlation
capabilities).

2
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

When the wargame turns radars on or off, this information is sent to synthetic tracking
to start or stop radar message processing. When the wargame generates detections
these calculations are performed with original, coarse detection algorithms based
on target cross-section and situation geometry assuming 360 degree detection
capabilities. Synthetic tracking uses more detailed calculations to generate radar
tracks.

When the wargame starts or drops a track, an internal message is sent from the
wargame to synthetic tracking which establishes a detector/detectee pair. Synthetic
tracking uses this pairing to perform the needed calculations to generate radar
tracks. For each detector-detectee pair generated by the wargame, when synthetic
tracking is enabled, synthetic tracking determines the expected detection details,
computes the radar data for those detections, and interpolates the time of the
detection to synchronize the radar motion with the motion of the object. At the
predetermined detection times, radar return messages are generated appropriate to
the configured message format and transmitted to the configured receiver.

The synthetic tracking functionality is controlled through data in the AWSIM

adaptation data file, two radar communication configuration files and a radar
characteristics file. The adaptation data file contains the controlling data for
the synthetic tracking functionality as a whole. The other three files provide
the parametric data defining the communication paths and the performance
characteristics for each defined radar. These data files are described more fully in
other sections of this document.

The various possible uses of synthetic tracking are depicted in Figure 1. The current
typical usage for synthetic tracking is to output EADS/WADS/CADS Radar Messages
using IP to the destination C2 system (BCS-F). Another use was to output messages
to a Multi-Protocol Communications Server (MPS), which would retransmit the Radar
Messages using serial ports to replicate actual radar interfaces. AWSIM also has
the capability to output TADIL tracks corresponding to AWSIM flight objects over
an IP network. AWSIM can also generate returns reformatted as FAA Automated
Air Movement Data System (AAMDS) messages (for R/SOCC inputs, for example)
which are output via a serial port on the server. If synthetic tracking is enabled, radar
return data messages can be output via:

3
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

• IP network socket connections to receivers configured to communicate over the

IP network
• IP network connections to an MPS which retransmits via serial communication
• TADIL Tracks and AWACS Position messages via IP network sockets
• Serial communication (AAMDS only)

Figure 1. Synthetic Tracking

The MPS receives radar return data messages across a network connection and
outputs the data messages through one of eight WAN ports. This is a currently
unused capability to provide a realistic radar interface (for example, to a radar
tracking data correlator).

This synthetic tracking facility also provides a deprecated feature to output some
of the TADIL track messages for the same detections to the ADSI/TC for visual
correlation and situational displays. This rudimentary feature has been replaced by

4
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

higher fidelity TADIL message processing functionality which includes R2 (reporting

responsibility) processing and a richer TADIL message repertoire. Users are
cautioned to avoid this deprecated TADIL functionality and strongly urged to use the
new TADIL functionality vice this deprecated functionality.

5
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 3. Configuration and Usage

Overview
There have been several iterations of the synthetic tracking functionality to support
a series of needs. As each need is satisfied or superseded by another, a new layer
of control variables is introduced. The intent is to keep each capability while adding
the new capability and this results in a collection of control variables which must be
set as a group to expose and control the desired output.

The choices in configuring the synthetic tracking facility are many and must be
approached from a logical reference point based on the desired operation. The
configuration of the synthetic tracking functionality as a whole is done through
the adaptation data file. This file enables synthetic tracking and selects the
communication modes to match the set of radar return data message receivers that
are to be stimulated.

AWSIM is able to support most communication schemes required by the operational

equipment. The choice of communication configuration is most often dependent
on the opposite end of the communication link with AWSIM. When operational
equipment is the destination of the communication path, the operational equipment
would typically dictate the configuration settings. The choice of TCP versus UDP for
protocol, client versus server for determination of protocol setting in socket mode,
port numbers to be used, or socket versus serial for communication mode must be
determined by the networking and physical configuration. ASWIM is neutral with
respect to these decisions. The only caveat is that port numbers must be unique
among the hosts of a communication path (i.e., the /etc/hosts files on all hosts on a
network must be examined for used and available port numbers when the equipment
has been initialized and configured).

The AWSIM architecture enables multiple, independent DI processes to be used

based on the processing power of the hosting workstation and based on the
anticipated complement of radars and tracked objects. The current version of the
AWSIM software allows a maximum of 3 independent DI processes to be run. Each
DI performs the processing for a subset of the radar complement as configured using

6
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

the radar configuration and characteristics files. These files can be the same on all
workstations, but it is not required. That is, each DI must have its own copy of these
three files or a consistent version of the files to control the processing.

Some real operational radars utilize an IP capability to "broadcast" messages on a

network to multiple clients. AWSIM currently does not have a broadcast capability
implemented. To provide the capability to send the same radar return message
to multiple receiving hosts, AWSIM synthetic tracking has implemented a set of
"secondary channels" on which the same data is output to multiple receivers.

7
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 4. Adaptation Data

(adaptation.data) File
The adaptation data file is the master initialization file used by AWSIM. Some of
the adaptation.data parameters can be changed while the Wargame is running.
Some parameters require a READ order for the changes to take effect. Others
require restarting an executable for the change to take effect. For a more complete
discussion of the adaptation data file, see the user manual AWSIM Adaptation Data
User Manual. The following paragraphs provide information on the portion of the
adaptation data file used by the synthetic tracking functionality.

The data excerpt in Figure 2 is taken from the adaptation.data file shipped in
the release bundle and is used as an example for the explanation following the data
excerpt.

Figure 2. Adaptation Data Excerpt

8
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

The master control for the synthetic tracking functionality is the boolean variable
Enable_Synthetic_Tracking . By setting this boolean to True , the synthetic
tracking functionality of AWSIM is enabled. The rest of the variables in the file will
be used by the synthetic tracking functionality as parameters and will control the
synthetic tracking processing.

The TOI_Filtering_For_Synthetic_Tracks field in the adaptation.data file allows

the user to specify that only the radar detections for flights that are designated as
targets of interest (TOIs) will be transmitted. Although all of the detections in AWSIM
will continue and will be displayed on the ASTAB board, the CD2 data will not be sent.

If synthetic tracking is enabled, AWSIM will attempt to read three synthetic tracking
characterization data files. The names of the data files are assumed to be related
to each other by having a common leading root string. This common root for
the filename is provided in the adaptation data file using the parameter string
Synthetic_Radars_Data. This root string MUST be enclosed in double quotation
marks (for example, "synthetic_radars" ). The software extends this root with
.cfg, .chr, and _2.cfg to form the three file names actually used to retrieve
the performance characteristics and communication configuration data. Using
this root in the example, the file names would be synthetic_radars.cfg ,
synthetic_radars.chr and synthetic_radars_2.cfg .

The three output data modes are enabled by the adaptation data file
parameters "Syn_Tk_Enable_Socket_Output", "Syn_Tk_Enable_MPS_Output",
and "Enable_AAMDS". Note that the three output data modes may be enabled
independently. That is, any or all output modes may be enabled depending on the
desired output from AWSIM. These settings interact with further control settings in
the synthetic tracking configuration file as described in Section 5 of this document.

Socket output is used for radar message socket connections and is enabled by
setting the parameter Syn_Tk_Enable_Socket_Output to True . Socket output is
also used for TADIL messages to the ADSI/TC port. Note that the use of this
TADIL capability is not recommended as this feature has been deprecated by the
implementation of more realistic TADIL message processing.

Output through the MPS is enabled by setting the parameter

"Syn_Tk_Enable_MPS_Output" to True .

9
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Output to simulate the FAA AAMDS messages is controlled by the parameter

"Enable_AAMDS".

Note
AAMDS messages are only output for units with Mode 3 set to ON
as this is the operation of the system being simulated.

The following table describes the various data in the adaptation data file shown in
the data excerpt above.

Table 4.1. Adaptation.Data Settings for Synthetic Tracking

File Entry Meaning/Comment

(Variable Name)
Enable_Synthetic_ Master control for synthetic tracking functionality
Tracking (True/False).
Synthetic_Radars_Data Root string for communication configuration and
radar characteristics files. MUST be enclosed in
double quotes.
Syn_Tk_Max_Synthetic_ Integer value (no constraints).
Radars
Syn_Tk_Max_Secondary_ Integer value (no constraints).
Channels
Syn_Tk_Enable_Bin_ Boolean value to control logging of data (True/False)
Logging (fps_117 and tps_75 only).
Syn_Tk_Prob_Of_Ssr_ Probability of detection when IFF is on (0 ⇐ value ⇐
When_Iff_On 1.0).
Syn_Tk_Discard_Latent_ Boolean value to control blip data discarding (True/
Blip_Data False).
Syn_Tk_Discard_Latent_ Latency time beyond which blips are to be discarded
Blip_Threshold (with blip data discarding control) - Integer value.
Syn_Tk_Mode_3_ Boolean value to control putting track number into
Contains_Track_No Mode 3 ( True /False)

10
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Syn_Tk_Mode_3_Max_ Maximum number of IFF tracks for a blip - Integer

Tracks value.
Syn_Tk_Mode_3_Start_ Starting bit position for first IFF track for a blip -
Bit Integer value.
Syn_Tk_Enable_MPS_ Boolean value to control output via MPS to serial
Output ports ( True /False).
Dummy_MPS_Open Boolean value to control output via MPS to serial
ports (True/False).
MPS_Open_Bind_Delay Time to delay between open and bind for MPS socket
- Integer value.
MPS_Max_Retry_Count Maximum number of times to retry MPS open
procedure before aborting attempts - Integer value >
0.
MPS_Max_Frame_Size Maximum size of MPS (serial) message frame -
Integer value > 0.
MPS_Baud_Rate Baud rate at which to transmit MPS (serial)
messages - Integer value > 0.
FPS_117_Idle_Bits Not used (hard coded to 255 - hex 'FF')
TPS_75_Idle_Bits Not used (hard coded to 170 - hex 'AA')
Syn_Tk_Enable_Socket_ Boolean value to control output via IP network
Output (sockets) (True/False).
Syn_Tk_Socket_Protocol Type of IP protocol to use when socket mode is
enabled (UDP or TCP).
Syn_Tk_Socket_Mode Type of socket mode to use when socket mode is
enabled (Client or Server).
Syn_Tk_Receiver_Host Not used (not referenced by synthetic tracking code).
Enable_AAMDS Boolean value to control output of AAMDS messages
( True /False).
AAMDS_Device_Name Only read if AAMDS is enabled - name of device to
use for AAMDS serial output.

11
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

AAMDS_Baud_Rate Only read if AAMDS is enabled - serial comm

characteristic - baud rate.
AAMDS_Stop_Bits Only read if AAMDS is enabled - serial comm
characteristic -number of stop bits.
AAMDS_Parity Only read if AAMDS is enabled - serial comm
characteristic - parity.
AAMDS_Out_Control Only read if AAMDS is enabled - serial comm
characteristic - out control.
Debug_TZBZ_Message Only read if AAMDS is enabled - Boolean value to
control output of debug messages to log file (True/
False).

Note
The shaded areas of the table are relevant to capabilities which
were developed for one-off tests and are no longer intended to be
used. The code to use this data continues to be present, but has
not been maintained as there is no longer any anticipated need
for these capabilities.

See Section 9 in this document for current normal or expected

values.

12
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 5. Synthetic Tracking

Configuration (synthetic_radars.cfg)
File
Radar sites are defined in the scenario database (laydown). To generate synthetic
radar messages, the synthetic radar functionality must be enabled in adaptation data
and the radars must be appropriately defined in BOTH synthetic tracking data files
with unit names matching the name used in the laydown. The radar characteristics
are defined in the operational characteristics file as described in Section 6 of this
document. The network connectivity configuration file contains the physical location
(latitude and longitude) and the communication control parameters for each radar.
The data excerpt in Figure 3 is taken from the synthetic_radars.cfg file
shipped with the AWSIM release and is used as an example for the explanation
following the data excerpt. This file also contains data previously used by the
synthetic tracking TADIL functionality. This data must be present in the file to
preserve the format of the file, but this TADIL functionality should not be used.

Figure 3. Synthetic Tracking Configuration Data

13
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

The following table describes the meanings, usages, and constraints on the values
in the columns in the data excerpt. See the notes following the table body for more
explanations.

Table 5.1. Synthetic Tracking Configuration Data

File Entry Meaning Comment

(Column Name)
Unit Name Entity Name (Radar) MUST match name in
Entity Name (A/C) Scenario File (if radar).
a
MUST match
aircraft (if TADIL
generation for
track) .
MPS Server DI Correlation Identifier MUST be one of (mps1,
(MPS Server Host mps2 or mps3) where
b c
Name) , the digit is the same
as the DI number (ADI
identifier) for the server
running the synthetic
radar processing.
d
MPS Serial Port Serial port number in If used for MPS, port
MPS corresponding to number (0 to 7) on outer
this device side of MPS for this
message. Otherwise, 0
(don’t care).
e f
MPS IP Port , IP Port number for MPS If row is for comm
through MPS set to 0 (not
used/don’t care). If row is
to be used to for AWACS
position, must be greater
than or equal to 8 (flag to
indicate not MPS).

14
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

g
MPS Output MPS output control Boolean (True/False)
value to control output via
MPS to serial ports.
h
Socket IP Port Port to use for IP socket Part of destination
output identification
i
Socket IP Host Name Name of host to use for Part of destination
IP socket output identification
Socket IP AWACS Pos AWACS Position Output Port used to report
j
Port AWACS aircraft position
Socket Output Socket output control Boolean (True/False)
value to control output
using IP networking.
k
Unit Latitude Actual location of radar.
l
Unit Longitude Actual location of radar.
m
First Track Number
n
Raw or JREAP or MTC TADIL message wrapper
type
o
JU Number2 00000 indicates use
number from flight data.
a
Only used for output of TADIL to the ADSI (which is no longer used - see adaptation data for supported
TADIL facility).
b
Only used for output to MPS unit (which are no longer used).
c
When IP networking is used, the protocol (TCP or UDP) and the Mode (Client or Server) are controlled by
the variables "Syn_Tk_Socket_Protocol" and " Syn_Tk_Socket_Mode", respectively, in adaptation data.
d
Only used for output to MPS unit (which are no longer used).
e
Only used for output to MPS unit (which are no longer used).
f
When IP networking is used, the protocol (TCP or UDP) and the Mode (Client or Server) are controlled by
the variables "Syn_Tk_Socket_Protocol" and " Syn_Tk_Socket_Mode", respectively, in adaptation data.
g
Only used for output to MPS unit (which are no longer used).
h
When IP networking is used, the protocol (TCP or UDP) and the Mode (Client or Server) are controlled by
the variables "Syn_Tk_Socket_Protocol" and " Syn_Tk_Socket_Mode", respectively, in adaptation data.
i
When IP networking is used, the protocol (TCP or UDP) and the Mode (Client or Server) are controlled by
the variables "Syn_Tk_Socket_Protocol" and " Syn_Tk_Socket_Mode", respectively, in adaptation data.

15
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

j
Only used for output of TADIL to the ADSI (which is no longer used - see adaptation data for supported
TADIL facility).
k
Should only be different from scenario data (laydown) to induce errors between position data and
reported tracks. This field may be left blank to force use of the position in the laydown.
l
Should only be different from scenario data (laydown) to induce errors between position data and
reported tracks. This field may be left blank to force use of the position in the laydown.
m
Only used for output of TADIL to the ADSI (which is no longer used - see adaptation data for supported
TADIL facility).
n
Only used for output of TADIL to the ADSI (which is no longer used - see adaptation data for supported
TADIL facility).
o
Only used for output of TADIL to the ADSI (which is no longer used - see adaptation data for supported
TADIL facility).

Note
The shaded areas of the table are relevant to capabilities which
were developed for "one-off" tests and are no longer intended to
be used. The code to use this data continues to be present, but
has not been maintained as there is no longer any anticipated
need for these capabilities.

Radar messages are transmitted based on the settings in the connectivity

configuration file. The data in this file is used to determine the communication
characteristics and are valid in different combinations. See the data excerpt for
sample data.

Note
This functionality is also controlled by settings in the adaptation
data file as described in Section 4 of this manual.

To enable messages to be transmitted via an IP network, socket output must be

enabled in adaptation data and the column "Socket Output" must contain the value
True for the corresponding radar unit. The destination host and port are entered in
the columns "Socket IP Host Name" and "Socket IP Port", respectively.

To enable output of messages to the MPS, MPS output must be enabled in

adaptation data and the column "MPS Output" must contain the value True for
the corresponding radar unit. These messages are transmitted either via serial or IP
network connections, or both, as controlled by the output control variables.

16
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 6. Synthetic Tracking

Characteristics (synthetic_radars.chr)
File
Radar sites are defined in the scenario database (laydown). To generate synthetic
radar messages, the synthetic radar functionality must be enabled in adaptation
data and the radars must be appropriately defined in BOTH synthetic tracking data
files with unit names matching the name used in the laydown. The communication
characteristics are defined in the synthetic tracking configuration file as described in
the Section 7 section of this manual. The operational characteristics file contains the
performance parameters used to control the radars. These parameters are typically
used to control the behavior of the radar and the radar messages generated from the
generated detections. Some of the data in this file may be used to introduce known
errors or biases when driving external equipment such as during return correlator
testing. The data excerpt in Figure 4 is taken from the synthetic_radars.chr
file shipped with the AWSIM release. The data columns should be self-explanatory
and the values should be determined through experimentation, measurement, or
from equipment documentation. A table describing the meaning and usages of the
values in the columns follows the data excerpt.

17
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Figure 4. Synthetic Tracking Characteristics Data

Table 6.1. Synthetic Tracking Characteristics Data

File Entry (Column Name) Meaning/Comment

Unit Name Entity Name (Radar) - MUST match
name in Scenario File.
Radar/Msg Format (See Section 6.1 after the table)
Max Range Maximum detection range (nautical
miles). Objects will not be detected
beyond this value. If value is set to
-1, the value in the scenario database
(laydown) for the emitter associated
with the radar is used.
Antenna Height Antenna Height (feet). Height
above ground of radar for detection
calculations. If value is set to -1,
the value in the scenario database
(laydown) for the emitter associated
with the radar is used.

18
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Prob of Detect at max range Pd at Max Range (0…1). Probability of

detection at maximum range of radar.
This value is interpolated linearly from
Pd to 1 at Minimum Detection Range. If
value is set to -1, signal to noise ratios
for the target geometry are calculated
and used for determining detection.
Scan Rate Radar rotation period (seconds)
assuming a 360 degree radar sweep or
reporting period for non-rotating radars.
Max Elevation Maximum radar detection elevation
(degrees) for message generation.
Min Elevation Minimum radar detection elevation
(degrees) for message generation.
Start Azimuth Starting radar detection azimuth
(degrees) for message generation. 0 for
full rotation.
Stop Azimuth Ending radar detection azimuth
(degrees) for message generation. 360
for full rotation.
Platform Tilt Constant - Pitch Radar platform tilt constant (degrees)
for pitch to introduce misalignment
error.
Platform Tilt Constant - Roll Radar platform tilt constant (degrees)
for roll to introduce misalignment error.
Bore Error Constant - Azimuth Radar beam misalignment constant
(degrees) to introduce azimuth error.
Bore Error Constant - Elevation Radar beam misalignment constant
(degrees) to introduce elevation error.
Vol Error Standard Deviation - Range Standard deviation (1 sigma) for
normal distribution for slant range error
(nautical miles).

19
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Vol Error Standard Deviation - Azimuth Standard deviation (1 sigma) for normal
distribution for azimuth error (degrees).
Vol Error Standard Deviation - Standard deviation (1 sigma) for
Elevation normal distribution for elevation error
(degrees).
False Alarm Rate False alarms (0 to number) to generate
per scan.
Delay Processing delay (msec) to introduce
a realistic propagation delay between
detection and message generation/
transmission.
SR_SSR Az Delta Bias to add to azimuth (degrees) in SR
and SSR messages.

6.1. Notes
NOTE 1:
The currently valid values for the Radar/MSG Format column entries which will
generate correctly formatted messages at the receiver are:

• RRDL
• ASR_9
• ARSR_4

NOTE 2:
Although the following Radar/MSG Formats are valid values and the messages
are generated correctly internally, the receiver will reject the corresponding output
messages. These messages have not been transitioned to use the correct "endian"
routines to compensate for the re-porting of the code from Solaris to PC server
hardware.

• CD_2
• TPS_59
• TPS_75

20
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

• FPS_117

• ASR_8K

• TPS_65
• TPS_43

NOTE 3:
Selection of FPS_117, ASR_8K, TPS_65, and TPS_43 result in messages formatted
identically as they are generated by the same routines.

NOTE 4:
The following values are syntactically correct, but should not be used as this feature
has been deprecated by the actual TADIL simulation functionality. The suggested
functionality is described in the "AFMSTT TADIL J Communications" user manual.

• Tadil_A

• Tadil_B

• Tadil_J

• Disabled

21
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 7. Secondary Channel

Configuration (synthetic_radars_2.cfg)
File
Some real operational radars utilize an IP capability to "broadcast" messages on a
network to multiple clients. AWSIM currently does not have a broadcast capability
implemented. To provide the capability to send the same radar return message
to multiple receiving hosts, AWSIM synthetic tracking has implemented a set of
"secondary channels" on which the same data is output to multiple receivers. The
secondary channel configuration file contains the IP addressing information for the
additional recipients of the messages. This feature must be coordinated with the
receiving systems to ensure the receiving equipment is configured to receive on the
same IP addresses (port) and has the same host name configured. The data excerpt
in Figure 5 is taken from the synthetic_radars_2.cfg file shipped with the
AWSIM release and is used as an example for the explanation following the data
excerpt.

Figure 5. Synthetic Tracking Secondary Channel Data

22
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Secondary communications over secondary channels will occur only when the Unit
Name is valid (see previous sections).

Table 7.1. Secondary Communications

File Entry (Column) Name Meaning/Comment

Unit Name Entity Name (Radar) - MUST match
name in Network Connectivity
Configuration File
Socket IP Port <Secondary Destination IP Port>
Socket IP Host <Secondary Destination IP Host
Name>

23
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 8. Runtime Considerations

Synthetic tracking processing is performed by the deaggregated interface (DI)
process (di_exec) which is started through the AWSIM Model Control Startup
application. When the DI process is started, the DI window is opened on the
workstation starting the DI process. Refer to the AWSIM System Controller User
Manual for details on starting, controlling, and status tracking the synthetic tracking
process.

At startup, every radar will report 0 (zero) plots. When the radars have been
activated (typically by a Ctrl + F command script) and are detecting aircraft, the radar
detections will first be displayed on the Active Track Status ASTAB corresponding to
the Side and View of the detecting radars. Refer to the AWSIM ASTAB User Manual
for more details on the ASTAB displays. A cycle or so later, the Summary lines in the
DI window will report the number of plots generated for each radar. The number of
detections for some radars may not be the expected number. That is, a radar may
report more contacts than there are aircraft flying. This is usually due to a particular
radar having a scan rate that is faster than the default 10 second game cycle. Another
factor may be that the radar is generating false alarms in addition to its detections.

24
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 9. Notes on Current Usage

Synthetic Tracking has evolved over the years to provide a number of capabilities
for very specific testing support purposes. As each capability was added, the
legacy capabilities were never removed. This section attempts to present a concise
explanation for the current usage. Currently, synthetic tracking is being used to drive
the air picture to track correlators using an IP network.

For this current usage, the recommended settings of the control variables are:

Table 9.1. Recommended Settings

File Entry (Variable or Column Name) Recommended Value

Adaptation Data File ( adaptation.data )
Enable_Synthetic_Tracking True
Synthetic_Radars_Data "<file name root>"
Syn_Tk_Max_Synthetic_Radars User Determined
Syn_Tk_Max_Secondary_Channels User Determined
Syn_Tk_Enable_Bin_Logging User Determined
Syn_Tk_Prob_Of_Ssr_When_Iff_On User Determined
Syn_Tk_Discard_Latent_Blip_Data User Determined
Syn_Tk_Discard_Latent_Blip_Threshold User Determined
Syn_Tk_Mode_3_Contains_Track_No False
Syn_Tk_Mode_3_Max_Tracks Do not change from default (16)
Syn_Tk_Mode_3_Start_Bit Do not change from default (2)
Syn_Tk_Enable_MPS_Output False
Dummy_MPS_Open Do not change from default (False)
MPS_Open_Bind_Delay Do not change from default (.25)
MPS_Max_Retry_Count Do not change from default (5)
MPS_Max_Frame_Size Do not change from default (512)
MPS_Baud_Rate Do not change from default (2400)

25
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

FPS_117_Idle_Bits Don’t care - not read

TPS_75_Idle_Bits Don’t care - not read
Syn_Tk_Enable_Socket_Output True
Syn_Tk_Socket_Protocol User Determined
Syn_Tk_Socket_Mode User Determined
Syn_Tk_Receiver_Host Don’t care - not read
Enable_AAMDS False
AAMDS_Device_Name Don’t care - not read if AAMDS not
enabled
AAMDS_Baud_Rate Don’t care - not read if AAMDS not
enabled
AAMDS_Stop_Bits Don’t care - not read if AAMDS not
enabled
AAMDS_Parity Don’t care - not read if AAMDS not
enabled
AAMDS_Out_Control Don’t care - not read if AAMDS not
enabled
Debug_TZBZ_Message Don’t care - not read if AAMDS not
enabled
Synthetic Tracking Configuration File (<file name root>.cfg)
Unit Name (MUST match scenario database
(laydown))
MPS Server mps1 or mps2 or mps3
MPS Serial Port Do not change from default (0)
MPS IP Port Do not change from default (0)
MPS Output Do not change from default (False)
Socket IP Port <Destination IP Port>
Socket IP Host Name <Destination IP Host Name>
Socket IP AWACS Pos Port Do not change from default (0)

26
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Socket Output True

Unit Latitude Same as scenario database (laydown)
Unit Longitude Same as scenario database (laydown)
First Track Number Do not change from default (00000)
Raw or JREAP or MTC Do not change from default (raw)
JU Number Do not change from default (00000)
Synthetic Tracking Characteristics File (<file name root>.chr)
Unit Name MUST match <file name root>.cfg
Radar/Msg Format User Determined
Max Range User Determined
Antenna Height User Determined
Prob of Detect at max range User Determined
Scan Rate User Determined
Max Elevation User Determined
Min Elevation User Determined
Start Azimuth User Determined
Stop Azimuth User Determined
Platform Tilt Constant - Pitch Do not change from default (0.0)
Platform Tilt Constant - Roll Do not change from default (0.0)
Bore Error Constant - Azimuth Do not change from default (0.0)
Bore Error Constant - Elevation Do not change from default (0.0)
Vol Error Standard Deviation - Range Do not change from default (00)
Vol Error Standard Deviation - Azimuth Do not change from default (0.0)
Vol Error Standard Deviation - Do not change from default (0.0)
Elevation
False Alarm Rate Do not change from default (0)
Delay User Determined
SR_SSR Az Delta Do not change from default (0)

27
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Secondary Channel Configuration File (<file name root>_2.cfg)

Unit Name MUST match <file name root>.cfg
Socket IP Port <Secondary Destination IP Port>
Socket IP Host <Secondary Destination IP Host
Name>

Note
The shaded areas of the table are relevant to capabilities which
were developed for "one-off" tests and are no longer intended to
be used. The code to use this data continues to be present, but
has not been maintained as there is no longer any anticipated
need for these capabilities.

28
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

Section 10. Frequently Used Acronyms

Acronym Definition
A/C Aircraft
A-A Air-to-Air
AAA Anti-Aircraft Artillery
AAM Air-to-Air Missile
AAMDS Automated Air Movement Data System
AAR Air-to-Air Refueling / After-Action Report
AATK AWSIM Analysis Toolkit
ABC Airborne C2 Center (AWSIM mission)
ABL Airborne Laser
ABS Airbase Simulation (formerly LOGSIM)
AC Aircraft
ACE Air and Space Constructive Environment
ACE-CSI Air and Space Constructive Environment – Command
and Control System Interface
ACE-IOS Air and Space Constructive Environment -
Information Operations Simulation
ACI AWSIM to CTAPS Interface
ACM Air Control Measures (obsolete usage: ALSP Control
Module)
ACO Airspace Coordination Order
AD ASTAB Display (AWSIM Executable)
AD Air Defense (AWSIM mission)
ADA Air Defense Artillery
ADI Aggregated/Deaggregated Interface (AWSIM
Executable)
ADSI Air Defense Systems Integrator

29
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

AEW Airborne Early Warning (AWSIM mission)

AFAMS Air Force Agency for Modeling and Simulation
AFFOR Air Force Component Forces
AFMSTT Air Force Modeling and Simulation Training Toolkit
AFSC Air Force Specialty Code
AFSERS Air Force Synthetic Environment for Reconnaissance
and Surveillance
AFSOM AF Suite of Models
A-G Air-to-Ground
AGL Above Ground Level
AGM Air-to-Ground Missile
AI Air Interdiction (AWSIM mission)
AIM Air Intercept Missile
AIRLF Airlift (AWSIM mission)
ALCM Air Launched Cruise Missile
ALLRAD All Range Air Defense
ALSP Aggregate Level Simulation Protocol
AML Amphibious Landing (AWSIM mission)
AMRAAM Advanced Medium Range Air to Air Missile
AOC Air Operations Center
AOI Area of Interest
APC Armored Personnel Carrier
APS Automated Planning System
ARSR Air Route Surveillance Radar (FAA radar site)
AS ASTAB Processor (AWSIM Executable)
ASCCE Air, Space and Cyber Constructive Environment
ASCII American Standard Code for Information
Interchange, a standard text format

30
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

ASD/NII Assistant Secretary of Defense for Networks and

Information Integration
ASM Air-to-Surface Missile
ASOC Air Support Operations Center
ASR Airport Surveillance Radar
ASTAB Air Status Board
ASW Anti-Submarine Warfare (AWSIM mission)
AT Air Terminal
ATA Air-to-Air
ATG Air-to-Ground
ATI AWSIM/TBMCS Interface (obsolete name for ACE-
CSI)
ATI AWSIM TBMCS Interface
ATK Attack (AWSIM mission)
ATO Air Tasking Order
AWACS Airborne Warning and Control System
AWSIM Air Warfare Simulation
BAI Battlefield Air Interdiction (AWSIM mission)
BCS-F Battle Control System - Fixed
BDA Bomb Damage Assessment
BINGO AWSIM order which returns the designated aircraft to
the air base or carrier from which it was launched, or
to a designated alternate.
BLADE Ballistic Launch and Development Environment
(separate program which handles ICBMs trajectories
for AWSIM)
BLU Bomb Live Units
BLUEFOR Blue Force (Blue cell)

31
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

BT AWSIM orders keyword to indicate Break

Transmission
BTS Battlestaff Training School, Hurlburt Field, Florida
C2 Command and Control
C3 Command, Control, Communications
C3I Command, Control, Communications and Intelligence
C4I Command, Control, Communications, Computers,
and Intelligence
C4ISR Command, Control, Communications, Computers,
Intelligence, Surveillance, and Reconnaissance
CADS Canadian Air Defense System
CAFMS Computer Assisted Force Management System
CALCM Conventional Air Launched Cruise Missile
CAP Combat Air Patrol (AWSIM mission)
CAS Close Air Support (AWSIM mission)
CBS Corps Battle Simulation (Army simulation)
CBU Cluster Bomb Unit
CCB Configuration Control Board
CCPL Command and Control Product Line
cd Linux command to Change Directory
CD-2 Radar track format
CDT Common Data Translator (obsolete predecessor to
TADIL in AWSIM)
CENTCOM Central Command
CIB Controlled Image Base
CINC Commander In Chief
CIWS Close In Weapons Systems
CM Cruise Missile
COA Course of Action

32
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

COCOM Combatant Command

COI Community of Interest
COMM Communications Relay (AWSIM mission)
CONOPS Concept of Operations
CONUS Continental United States
COP Common Operating Picture
COTS Commercial Off The Shelf
CR Change Request
CRC Control and Reporting Center
CRGLF Cargo Lift (AWSIM mission)
CSAR Combat SAR (AWSIM mission)
CSC Computer Software Component
CSCI Computer Software Configuration Item
CSG Carrier Strike Group
CSM Common Sockets Manager
CSU Computer Software Unit
CTAPS Contingency Theater Automated Planning System
CWIC CTAPS Wargame Interface Controller
DB Database
dB Decibel
DCA Defensive Counter Air (AWSIM mission)
DEC Digital Equipment Corporation
DHS Department of Homeland Security
DI Deaggregated Interface (AWSIM Executable or
AWSIM Node)
DI Discrete Information
DII-COE Defense Information Infrastructure - Common
Operating Environment

33
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

DIS Distributed Interactive Simulation

DISA Defense Information Systems Agency
DM Data Management
DM DM – DI Monitor
DMOC Distributed Missions Operations Center
DMPI Desired Mean Point of Impact
DMQ DEC Message Queue (obsolete means of messaging
between AWSIM modules, replaced by sockets)
DMS Distributed Mission Services
DoD Department of Defense
DP DP – DIS Print
DR Dead Reckoning
DR Deficiency Report
DREN Defense Research and Engineering Network
DS Data Services (AWSIM Node)
DTED Digital Terrain Elevation Data
DWS Distributed Wargaming System
EADS Eastern Air Defense System
EC Electronic Combat
ECM Electronic Counter Measures
ECS 505th Exercise Control Squadron
EI External Interface CSCI
END AWSIM orders keyword to indicate Route End Time
EPU Explosive Power Units or Equivalent Payload Units
ESC Escort (AWSIM mission)
ESC Electronic Systems Center (former name of Air Force
LifeCycle Management Center)
ESG Environmental Scenario Generator

34
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

ESM Electronic Surveillance Measures (AWSIM mission)

EW Electronic Warfare (AWSIM mission)
FAA Federal Aviation Administration
FAC Forward Air Control (AWSIM Mission)
FAF Final Approach Fix
FEBA Forward Edge of the Battle Area
FLIR Forward Looking Infrared
FLT Flight
FOL Forward Operating Location
FPS Fixed-Site Search Radar
FPW Fixed, Position, World
FQR Formal Qualification Review
FQT Formal Qualification Test
FVW Fixed, Velocity, World
FY Ferry (AWSIM mission)
G Standard gravity
GBU Guided Bomb Unit
GC Great Circle
GCI Ground Control Intercept
GDS GENIS Data Server
GEG GPS Environment Generator
GENIS Data Server for GIAC
GFE Government Furnished Equipment
GIAC Graphical Input Aggregate Control
GIG Global Information Grid
GIPRADIUS Ground Impact Point Radius
GM Game Monitor (AWSIM Executable)
GMI GENIS Model Interface

35
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

GP General Purpose
GRWSIM Ground War Simulation
GUI Graphical User Interface
GWOT Global War on Terror
HARM High Speed Anti-Radiation Missile
HFDF High Frequency Direction Finding
HHQ Higher HeadQuarters
HIMAD High and Medium Range Air Defense
HLA High Level Architecture
HTACC Hardened Theater Air Control Center
HWCI Hardware Configuration Item
IADS Integrated Air Defense Simulation
IAF Initial Approach Fix
ICBM Intercontinental Ballistic Missile
ICD Interface Control Document
ID Identifier or Identification
IF Intermediate Frequency
IFF/SIF Identify Friend or Foe/Selective Identification Feature
IM Instant Messaging
IMCN Intelligent Mission Controller Node
INTREP Intelligence Report
IP Initial Point
IP Internet Protocol
IPT Integrated Product Team
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
IRS Interface Requirements Specification
ISR Intelligence, Surveillance, and Reconnaissance

36
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

ITO Integrated Tasking Order

J/CFACC Joint/Coalition Forces Air Component Commander
J2EE Java 2 Platform, Enterprise Edition
JAM GUI Jyacc Application Manager Graphical User Interface
(AWSIM Scenario Generation module)
JASSM Joint Air to Surface Standoff
JCAS Joint Command and Control Attack Simulation
JCATS Joint Conflict and Tactical Simulation
JDAM Joint Direct Attack Munition
JDBC Java Database Connectivity
JDLM Joint Deployment Logistics Model
JECEWSI Joint Electronic Combat - Electronic Warfare
Simulation (a module of ACE-IOS)
JFACC Joint Forces Air Component Commander
JFCOM US Joint Forces Command
JGG Joint Ground Game
JIS Joint Infrastructure Software
JLCCTC Joint Land Component Constructive Training
Capability
JLVC Joint Live Virtual & Constructive
JMBL Joint METOC Broker Language
JMS Java Message Services
JMTK Joint Mapping Toolkit
JNETS Joint Networks Simulation
JNTC Joint National Training Center
JP Jet Petroleum
JQUAD Suite of 5 constructive models (obsolete name of
ACE-IOS)
JREAP Joint Range Extension Application Protocol

37
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

JSAF Joint Semi-Automated Forces

JSIM Joint Simulation System
JSOW Joint Standoff Weapon
JSTARS Joint Surveillance Target Attack Radar System
JTC Joint Training Confederation
JTF Joint Task Force
JTIDS Joint Tactical Information Distribution System
JTLS Joint Theater Level Simulation
JTTI+K Joint Training Transformation Initiative plus Korean
Simulations
JU JTIDS Unit
KASC Korean Air Simulation Center
KRxx Key Resolve 20xx (example: KR13 = Key Resolve
2013)
KTAIP Korean TADIL Architecture Improvement Program
LAN Local Area Network
LANL Los Alamos National Laboratory
LAU Rocket Launcher
LG Logger (AWSIM Executable)
LLC Limited Liability Company
LOGSIM Logistics Simulation
ls Linux command to List Files
LS ACK LOGSIM Acknowledgement
LVC Live, Virtual, and Constructive
LZ Landing Zone
M&S Modeling and Simulation
MAGTF Marine Air Ground Task Force
MAJCOM Major Air Command

38
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

man Linux command to open manual listing for a Linux

command
MC Model Control (AWSIM Executable)
MH Message Handler (AWSIM Executable)
MICAP Mission Capable
MIDB Modernized Integrated Data Base
MISREP Mission Report
MP Maritime Patrol (AWSIM mission)
MPS Multi-Protocol Communications Server
MPW Mission Planning Workstation
MRL Multiple Rocket Launcher
MSCT Multi-Source Correlator Tracker
MSEL Master Scenario Event List
MSL Mean Sea Level
MSN Mission
MSN Mission
MSOA Minimum Safe Operating Altitude
MTBCF Mean Time Between Critical Failures
MTBF Mean Time Between Failures
MTC Multi-TADIL Capability
MTWS MAGTF Tactical Warfare Simulation
MUREP Munitions Status Report
MUSE Multiple Unified Simulation Environment
NAF Numbered Air Force
NATO North Atlantic Treaty Organization
NAWSIM Naval Warfare Simulation
NE NESI Enhancement
NESI Net-Centric Enterprise Solutions for Interoperability

39
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

NFS Network File System

NFZ No Fly Zone
NIMA National Imagery And Mapping Agency
nm Nautical Mile
NMAIR No Map Aircraft
NMBAS No Map Base
NMBOT No Map Boat
NMRAD No Map Radar
NMSAM No Map SAM Site
NMSHP No Map Ship
NMSSM No Map SSM Site
NMSUB No Map Submarine
NOOP Not Operational
NORAD North American Aerospace Defense Command
NSN National Stock Number
NTISR Non-Traditional Investigation, Surveillance, and
Reconnaissance
OAS Offensive Air Support (AWSIM mission)
OBS Order of Battle Service
OCA Offensive Counter Air (AWSIM mission)
OE Orders Entry (Air Terminal - AWSIM Executable)
OF Orders Files (AWSIM Executable)
OMT Object Modeling Technique
OO Object Oriented
OP Orders Parser (AWSIM Executable)
OPFOR Opposing Force (Red cell)
ORD Operational Requirements Document
PDU Protocol Data Unit

40
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

PEO C4I Program Executive Office for Command, Control,

Communications, Computers and Intelligence
PH Probability of Hit
PK Probability of Kill
POL Petroleum, Oil, and Lubricant
PPLI Precise Participant Location and Identification
PRISM Portable, Reusable, Integrated Software Modules
(replaced by CCPL)
PROBKILL Probability of Kill
PSI Pounds per Square Inch
PSM Portable Space Module
PTL Primary Target Line
PTT Part Task Trainer (Training)
PubSub Publish/Subscribe Service
QA Quality Assurance
QC Quality Control
R/SOCC Regional/Sector Operation Control Center
R2 Reporting Responsibility
REC Reconnaissance (AWSIM mission)
RECCE Reconnaissance
REINT Re-initialized
REPOL Report of Petroleum, Oil, and Lubricants
RESA Research, Evaluation, and System Analysis (US
Navy model, depicting surface, subsurface, and air
operations)
RM Resource Manager (AWSIM Executable)
ROE Rules of Engagement
RSC Rescue (AWSIM mission)
RTI Run Time Infrastructure

41
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

RTSMT Real Time Simulation Management Team

SAL Strategic Air Lift
SAM Surface-to-Air Missile
SAMOPS Surface-to-Air Missile Operations
SAMSITE Surface-to-Air Missile Site
SAMTDM Surface to Air Missile Target Difficulty Modifier
SAR Search And Rescue (AWSIM mission)
SC Scenario Control (AWSIM Node)
SCL Standard Conventional Load
SCOPES Squad Combat Operational Exercise Simulation
SCP Surface CAP (AWSIM mission)
SDP Software Development Plan
SEAD Suppression Enemy Air Defense
SFW Sensor Fused Weapon
SGD Sortie Generation Degradation
SHORAD Short Range Air Defense
SIDC Space Innovation and Development Center
SIMPLE Standard Interface for Multiple Platform Link
Evaluation
SIQT Site Integration and Qualification Test
SIT Systems Integration Test Lab
SITREP Situation Report
SLAMER Stand Off Land Attack Missile
SOA Service-Oriented Architecture
SOF Special Operation Forces
SOPD Standoff Outside Point Defense Missile
SoR Systems of Record
SOSI Service Oriented Scenario Injector

42
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

SPC Special Operations (AWSIM mission)

SPJ Self-Protection Jammer
SPOPS Special Operations
SSDD System Segment Design Document
ssh Linux command to remotely secure-login (Secure
Shell)
SSM Surface-to-Surface Missile
SSMSITE Surface-to-Surface Missile Site
SSS System Segment Specification
STOL Short Takeoff and Landing
STR System Trouble Report
STRCAP Strike CAP (AWSIM mission)
STRK Strike (AWSIM mission)
SURV Surveillance (AWSIM mission)
SWP Sweep (AWSIM mission)
TACREP Tactical Report
TACSIM Tactical Simulation Model
TADIL Tactical Data Information Link
TADP Tactical Airdrop (AWSIM mission)
TAL Theater Air Lift
TBD To Be Determined
TBM Theater Ballistic Missile
TBMCS Theater Battle Management Core Systems
TCP/IP Transmission Control Protocol/Internet Protocol
TMS Target Management System
TNK Tanker (air-to-air refueling) (AWSIM mission)
TOI Target of Interest
ToO Transfer of Ownership

43
 Air Warfare Simulation (AWSIM) Synthetic Tracking
Overview
AFMSTT-U-000337

TOT Time Over Target

TPS Ground-transportable Search Radar
TQ Track Quality
TRR Test Readiness Review
TTL Time To Live
UAV Unmanned Aerial Vehicle
UDP User Datagram Protocol
UFG Ulchi Freedom Guardian
UFL Ulchi Focus Lens
USAF United States Air Force
USAFE United States Air Forces in Europe
USMTF United States Message Text Format
UWG Users Working Group
VLAN Virtual Local Area Network
VoIP Voice over Internet Protocol
VTOL Vertical Takeoff and Landing
W Current Rules of Engagement
W3C World Wide Web Consortium
WADS Western Air Defense System
WAN Wide-Area Network
WG Wargame (AWSIM executable or AWSIM Node)
WM Wargame Monitor (text-based AWSIM executable)
WOC Wing Operations Center
WPC Warrior Preparation Center
WW Wild Weasel (AWSIM mission)

44