ARTS equipment has no attributes that can be modified.

ATM equipment has no attributes that can be modified.

CFAF equipment has no attributes that can be modified. It is present in HCS version only

FDIO equipment has no attributes that can be modified.

NADIN equipment is generated based on the adaptation but may also be user defined. Adapted equipment appears LIGHT BLUE in list and cannot be deleted. Non-adapted equipment appears GREEN and may be modified and deleted.

NAS equipment has no attributes that can be modified.

A single NOTAM device is auto-generated by GSGT and it has no attributes that can be modified.

IOT equipment has no attributes that can be modified. It is present in HCS version only

KVDT equipment has no attributes that can be modified. It is present in HCS version only

READER equipment has no attributes that can be modified. It is present in HCS version only

A single SWIM device is auto-generated by GSGT and it has no attributes that can be modified.

A single WMSCR device is auto-generated by GSGT and it has no attributes that can be modified.

The sector number (or ID) is set by the adaptation used in the scenario. Only certain DS Sector Position information can be edited. To edit Sector Position double click on sector position name in the list of objects.

DS Equipment Editor is used for viewing M&C, AT Specialist and Sector equipment. All of the attributes of this type of equipment are adapted and my not be modified or deleted.

The Static Radar Message Editor dialog is used for editing static message overrides. To edit existing message double-clicked on particular message in Static Radar Messages list.

The Inhibit Time Interval Dialog is used to create and edit time intervals when static radar messages are disabled. This dialog is open when New Inihibit is selected from the right mouse click context menu on the Static Radar Message Inhibit Time Interval list.

The ModifyCD2 Time Interval Dialog is used to create and edit time intervals to change static radar messages. This dialog is open when New ModifyCD2 is selected from the right mouse click context menu on the Static Radar Message Active Time Interval list.

The ModifyASTERIX Time Interval Dialog is used to create and edit time intervals to change static radar messages. This dialog is open when New ModifyASTERIX is selected from the right mouse click context menu on the Static Radar Message Active Time Interval list.

Radar Events are created and edited using Radar Event Editor. This allows to define a wide range of events that can be applied to a radar to change its characteristics and behavior. Reference table below describing all available events.

Non-Radar Areas are created and edited using Non-Radar Area Editor. The non-radar area is a 3-dimensional shape defined by start and end azimuth (pie shaped) with start and end range and height limited by base and ceiling altitude. The area can be defined both primary and secondary radar sensors.

The Static ASTERIX Message Editor is used for new or editing of existing static message list.

The Inhibit Time Interval Dialog is used to create and edit time intervals for disabling static Service Volume messages. This dialog is open when New Inhibit is selected from the right mouse click context menu on the Static ASTERIX Message Overrides list.

The ModifyASTERIX Time Interval Dialog is used to create and edit time intervals to change static Service Volume messages. This dialog is open when New ModifyASTERIX is selected from the right mouse click context menu on the Static ASTERIX Message Overrides list.

Service Volume Events are created and edited using Service Volume Event Editor. This allows to define a wide range of events that can be applied to a service volume to change its characteristics and behavior. Reference table below describing all available events.

Service Volume Coverage Areas are created and edited using Service Volume Coverage Area Editor. The areas are defined as series of lat/lon points. Points are added using point and scroll mouse button click on any location on the map. individual points can be deleted and additional points can be added after current selection.

The Coverage Areas are previewed on the map while being edited. To aid with determining the location of the area, other tools can be displayed on the map, such as Service Volume AOI or Grid, as well as Service Volume Radio Stations (see Section 2.3.1, “Adaptation Window”)

The generic System Command can essentially be any message type. Messages that are properly formatted upon a subsequent editing are open in a default system command editor, such as Flight Plan, CMS, SWIM or SIGMET editors.

To create a generic System Command, right-click on the System Commands object label and select New from the context menu.

The Flight Plan Editor is the default message editor for FP messages. It allows user to change all attributes of a FP message.

To create a Flight Plan System Command, right-click on the System Commands object label and select New FP from the context menu. It is also used when New FP is selected in the Messages tab the Target Editor.

When GSGT is running in Terminal Mode, also there is a Terminal FP message available that is tailored for terminal systems. To create a Terminal Flight Plan System Command, right-click on the System Commands object label and select New Terminal FP from the context menu. It is also used when New Terminal FP is selected in the Messages tab the Target Editor.

A CMS system command is a CMS (Common Message Set)-formatted message that is not associated with a Target.

To create a CMS System Command, right-click on the System Commands object label and select New CMS Msg from the context menu.

A CMS system command has the same fields for Time, Source and RSI as a Generic system command, except the Text field is replaced with CMS fields definitions.

ATCoach TIME token substitution is performed for fields 86B, 92A and the time portion of field 0E. For the sequence number portion of field 0E, entering "$$$$" will generate the MSGSEQ token.

To create the SSPID token, enter "$$" in field 167A.

SWIM system command editor is formulated for editing SWIM messages, in particular flight create, modify and update message types. The fields contained in each of the SWIM message types are adapted in accordance with the WSDL specifications. Most of the fields in the dialog are limited to a valid range of values by drop down selection or by value limitations in the text fields, however, per design, the dialog allows to save the message with missing required fields, and values out of range.

SIGMET system command editor is formulated especially for editing SIGMET WMSCR messages. Other WMSCR messages are open using the Generic system command editor.

Most of the fields in the dialog are limited to a valid range of values by drop down selection or by value limitations in the text fields.

The Geographic Area field can be manually typed in or selected from the map similarly as route of the target by clicking on points on the map. The points in the filed will be separated by "ETC TO" element.

The general target's attributes are located on the Main tab of the Target editor. The attributes describe the target's characteristics such as aircraft dynamics, on-board navigation equipment and transponder types.

The Route tab of the Target Editor defines the path the target is flying in an airspace. A target's aircraft trajectory can be specified as a route with defined points, such as fixes and airports. Or it can be specified as an initial condition defined as initial position with heading or initial position with a join fix on a route.

When first and/or last element on the route is an airport, GSGT can model appropriate departure or arrival to an airport, including modeling of particular runways on the airport. The runways must be predefined using Runways site definition in order to be used in a target's route (see Section 4.9.4.4, “Runway (RW) Site Definitions Editor”)

Based on the target's route definition, GSGT generates radar and derives appropriate messages such as flight plans and handoffs (see Section 7.3, “Show Route Display” and Section 4.8.1.3, “Target Messages”)

The flight route can be entered in two ways, using the point and click feature of GSGT or by manually typing the flight route text in the dialog box. To use the point and click function, place the cursor over the desired element such as a fix or an airport and left-click the mouse. The element is added to the flight plan and displayed in the flight plan dialog box. As elements are added to the flight plan, fixes and airports are highlighted in BLUE, the flight route is outlined in RED between fixes and segments along airways are outlined GREEN).

Point and click adds new elements to the end of the flight plan. To add or remove an element in the middle of the route, manually modify the fix text in the flight plan dialog box or place the cursor after the element (before "." or "..") that you want to insert additional elements.

The Messages tab of the Target Dialog lists all non-radar messages associated with the target. The messages can be auto-generated (auto-derived) based on the route of the target or manually created. Messages are auto-derived only when Auto-generate msgs is selected.

When target is set to auto-generate message, GSGT will generate all appropriate non-radar messages such as flight plan, start tracking, and handoff control of the flight between controllers and/or facilities as needed.

Additionally parameters controlling the creation of auto-generated messages can be set in the scenario Preferences or Target Preferences (see Section 4.1, “Preferences” and Section 4.8.1.3.2, “Target Preferences”).

The Events tab of the Target Editor lists events that affect various aspects of the target.

Target Events allow to define a wide range of events that can be applied to a target to perform various tasks or change target's characteristics. Reference table below describing all available events.

The ATCoach tab of the Target editor provides ability to change ATCoach specific options and define Pre-Programmed Events and Pilot Prompts. Options and definitions contained in this tab are only exported in the SIME scenario (see Section 9.4, “SIME Export”)

The TGF tab of the Target editor provides ability to set/override any or all fields GSGT outputs in and exported TGF sim using TGF specific XML tags. Definitions contained in this tab are only exported in the TGF scenario (see Section 9.3, “TGF Export”) This tab is not available in SGET version.

The generic Site Definition can essentially be of any type. Definitions that are properly formatted upon a subsequent editing are open in a default site definition editor, such as Runway, Arrival Procedure or Published Holding Pattern editors, to name a few. The generic Site Definition Editor is simply an open text command editor that allows the user to define any site definition. GSGT does not provide any format guidance or does not validate the content of the site definition.

To create a generic Site Definition, right-click on the Site Definitions object label and select New from the context menu.

Point site definition editor defines a point in space that is any point within the viewing area to which an aircraft can navigate such as RNAV waypoints, runway thresholds, track drop points, handoff points, and points related to a traffic pattern. The editor allows the user to easily create a properly formated definition by validating content fields and providing a visual guidance on the GSGT map. A point is defined by three to nine character identifier and a lat/lon position.

To create a Point site definition, right-click on the Site Definitions object label and select New Point (PT) from the context menu.

Marco Route site definition editor defines a route of navigable flight path. They are identified by route segments such as navaids that include procedures (speed/altitude) and fixes. The editor allows the user to easily create a properly formated definition by validating content fields and providing a visual guidance on the GSGT map. The fixes can be manually typed in as text or selected by point and click form the GSGT map in a similar matter as in the route of the target (see Section 4.8.1.2, “Target Route”).

To create a Macro Route site definition, right-click on the Site Definitions object label and select New Macro Route (RT) from the context menu.

Runway site definition editor defines a runway that can be used for instrument approaches and departures. The editor allows the user to easily create a properly formated definition by validating content fields and providing a visual guidance on the GSGT map.

To create a Runway site definition, right-click on the Site Definitions object label and select New Runway (RW) from the context menu.

Departure Profile site definition editor defines a set of maneuvers the target will perform before turning to the first fix on its route. The editor allows the user to easily create a properly formated definition by validating content fields.

To create a Departure Profile site definition, right-click on the Site Definitions object label and select New Departure Profile (DP) from the context menu.

Non-ILS Arrival Procedure site definition editor defines a non-ILS approach that is in the format of an Instrument Approach Clearance-stockpile. The editor allows the user to easily create a properly formated definition by validating content fields and providing a visual guidance on the GSGT map. The fixes can be manually typed in as text or selected by point and click form the GSGT map in a similar matter as in the route of the target (see Section 4.8.1.2, “Target Route”). When a fix is selected a Value Editor is open for user to specify optional Altitude and Speed at the current fix. However, other conditions need to be manually typed in.

To create a Non-ILS Arrival Procedure site definition, right-click on the Site Definitions object label and select New Non-ILS Arrival Procedure (AI) from the context menu.

Missed Approach Procedure site definition editor defines a missed approach procedure for either all approach types or a specific approach type (e.g., GPS, VOR). The editor allows the user to easily create a properly formated definition by validating content fields and providing a visual guidance on the GSGT map. The fixes can be manually typed in as text or selected by point and click form the GSGT map in a similar matter as in the route of the target (see Section 4.8.1.2, “Target Route”). When a fix is selected a Value Editor is open for user to specify optional Altitude and Speed at the current fix. However, other conditions need to be manually typed in.

To create a Missed Approach Procedure site definition, right-click on the Site Definitions object label and select New Missed Approach Procedure (AM) from the context menu.

Published Holding Pattern site definition editor defines procedure that keeps an aircraft within specified airspace awaiting further clearance from Air Traffic Control. The editor allows the user to easily create a properly formated definition by validating its content fields.

To create a Published Holding Pattern site definition, right-click on the Site Definitions object label and select New Published Holding Pattern (AI) from the context menu.