VIETNAM SIMULATOR OVERVIEW
The Vietnam Selex-ES Simulator system is composed by the following nodes:
JSI = PC Java Supervisor Interface
FDA = Flight Data Assistant position
PIL/SPV = Pilot Supervisor position (D01)
PIL’s = Pilot positions (D02, D03, …, D07)
CWP’s = CWP positions (D08, D09,…, D15)
I. SCENARIO DESCRIPTION
In the JSI position is possible to have up to 20 Scenarios.
Every Scenario is composed by two set of data:
1) GEOGRAPHICAL DATA:
FIX
AER (with runways)
SID + ICP + ICP/SID junctions
STAR + FAP + STAR/FAP junctions
The Geographical Data is imported to the JSI from FDP. Afterwards, the user, via the JSI
masks, can modify, update the Geographical Data or delete unwanted Data.
2) SIMULATED DATA:
SDR = Standard Routes (track trajectories)
HLD = pre-defined Holding fixes
MA = Missed Approach paths
GA = Go Around paths
VA = Visual Approach cones (used with the Visual Approach order)
MCF = Map Configuration File to set TCA (Term Conflict Alerts)
RAD = Radars
MET = Meteo
FRQ = Frequencies
APP = ILS cones (used with the Final Approach order)
RPL = Repetitive Plans (flights for the exercise)
The Simulated Data are relevant to the navigation of tracks, and they have to be inserted from
the beginning in the JSI, in order to prepare the exercises.
The simulated data fields are empty at the beginning. Then the user can insert all the needed
data, to navigate tracks during the exercise. See a detailed description of these data in the
following paragraphs.
II. PROCESSING PROCEDURES – JSI
1. DATABASE MANAGER
The first mask displayed on the screen is the Data Base Manager, by which the user can define
the scenarios and the exercise configurations.
User is enabled to select one of the following choices:
Scenario to select or create a scenario
Maintenance to copy/delete and to and to backup/restore scenarios
Exercise to create or modify the exercise configurations
Supervisor is the operative run-time, to send and monitor exercises
System to have information on Data Base Manager Version and System
2. SCENARIO MENU
A scenario is a set of data that allows the user, after the creation of plans of flight, to use the
simulation of flights.
The Scenario menu shows the following features:
New -> From FDP
List
Details (RPL group)
APD (Aircraft Performance Data)
A. From the New menu the order From FDP is available, to:
Import the Geography from the relative FDP scenario database
Import an Archived Flight Set.
B. From List the list of the Scenarios present in the JSI is visualized. Then clicking
on one Scenario is possible to enter it and manager its data.
Inside every Scenario, the toolbar on top visualize the Scenario name and the system centre.
The toolbar below the Scenario name show the following options:
Data Base Data Base masks, to insert/modify/delete data
List to visualize Data Base lists
Graphic Plane to visualize the Graphic Plane, and the selected data on the graphic
Window to arrange icons
For every item in the Scenario Database, from the Toolbar menu on top is possible to:
Add a new item
Modify
Save
Undo
Delete
Print
Visualize the List
RPL
In the RPL mask all the information concerned every flight of the exercise can be inserted,
modify or deleted. Moreover, only for this mask in the JSI database, is possible to use the button
Copy present in the Toolbar, to copy one RPL into a new one.
In the RPL mask, fields are the following:
Field Description
CS Call-sign
Other equipment
box
CPDLC Yes or No
Registration Num. Registration Number
Mode-S Yes or No
Transponder type E=Elementary H=enHanced
ADS-B Yes/No
RCS Received Call Sign
ICAO bit code Country, mark and flight id.
AFTN Equipment
box
FIELD-10a Field-10a of the flight plan
FIELD-10b Field-10b of the flight plan
FIELD-18 PBN Field-18, PBN, of the flight plan
FIELD-18 IFP Field-18, IFP, of the flight plan
Trajectory box
SID Track SID
DEP_RWY Track Departure runway
ADEP Departure aerodrome (for track and flight plan)
TRACK CRUISE SDR track trajectory or ATG route track trajectory directly inserted in
TRJ the RPL mask
STAR Track STAR
DES RWY Track Destination runway (for track and flight plan)
ADES Destination aerodrome
FDP ROUTE Flight Plan trajectory (i.e. field18 of the flight plan)
Auxiliary Info box
SCT Sector (owner sector of the flight plan, when the exercise is sent with
no FDP)
DLY Delay time of activation of the track
EET Track estimate time (automatically calculated by JSI)
Cinematic Data
box
RFL Requested Flight Level (value used only for the flight plan)
RTAS Requested TAS (value used only for the flight plan)
AFL Track Activation Flight Level
ATAS Track Activation TAS
CFL Track cleared flight level
CTAS Track cleared TAS
Pilot/group
assignment box
RPL group One or more RPL groups the RPL is belonging to. An RPL group is a
number (from 1 to 98). Number 99 is used for the Archived Flight Set.
PILOT ID. Pilot owner. Is possible to specify more pilot owners: the flight will
belong to the first available pilot in the exercise.
A/C Data box
SSR M/C SSR mode and code
AIRCRAFT TYPE Aircraft type
WTC Wake Turbulence Category
FDP/FPL box
FPL If Yes, for the current RPL the Simulator will generate not only the
track but also the flight plan.
EQP Flight Plan Equipment (not mandatory)
FDP ROUTE Standard ICAO route of the flight plan (field 18)
HOLDING If Yes, the track, when activated, will hold on the first fix of its
trajectory
RUL Flight plan rule
TYPE Flight plan type
Trajectory Fix List Track trajectory fix are automatically displayed here
RPL: every RPL is a flight (track and flight plan) to be generated for the simulation.
SID, SDR and STAR fields shape the track trajectory, while FDP ROUTE is just the
FDP route field of the correspondent flight plan.
AFL and ATAS (“Activation” TAS) are the values of level and speed of track when
appearing on GRP, at the delay time.
CFL and CTAS (“Cleared” TAS) are the values of level and speed that the track will
reach after the activation.
RFL is the Requested Flight Level that will be in the correspondent flight plan
RTAS (“Requested” TAS) is the Requested TAS that will be used in the associated flight
plan
FPL flag: when set to No, the flight plan is not generated
RPL group: an RPL can belong to one or more RPL group. An RPL group is a number
(1... 98)
Pilot id: an RPL will belong to the first available pilot described in the Pilot id boxes:
when the first chosen pilot id is not available, that track will belong to the next chosen
pilot id available. If no pilot id are present in the exercise, that track will belong to the
supervisor.
RPL other equipment: from this button is possible to open a mask, and set the
information relative to the Mode-S equipment and CPDLC equipment.
AFTN equipment: from this button is possible to open a mask, and set the information
relative to the AFTN equipment of the flight plan: field 10a, field 10b, field 18-PBN and
field 18-IFP.
Example of Group of flights inside one scenario:
Say SCE07 have some flights, and they belong to some different groups in the following
way:
flight F1 belongs to group 1 and group 80
flight F2 belongs to group 1 and group 80
flight F3 belongs to group 2 and group 80
flight F4 belongs to group 2 and group 80
flight F5 belongs to group 2 and group 80
flight F6 belongs to group 3 and group 80
flight F7 belongs to group 3 and group 80
Gr 1
F1
Gr 2
Gr 80
F2
F3
F4
Gr3
F5
F6
F7
This means that, for example:
the exercise characterized by SCE07, group 2, will display only the flights F3, F4 and F5.
the exercise characterized by SCE07, group 80, will display the flights F1, F2, .., F7.
C. From the Detail (RPLgroup) order all the group of flights are shown in the
“Scenario Detail” mask. Selecting one Scenario the RPL Groups associated are
visualized.
Then selecting a group number, all the RPLs associated will be shown in mask.
The Summary below indicates how many RPL groups are associated to the selected Scenario
Total RPL Groups associated; then selecting one RPL group, the corresponding RPL are shown,
and the Total RPL in Selected Group number is shown.
The detail of the RPL group is initially visualized in order of Delay Time, but clicking on the
column name, the user can sort the list by CallSign, ADEP, ADES, DLY, SID, SDR or STAR.
Clicking on the “Print RPL group” button, is possible to print the details of the selected group of
flights, and print the report on a printer, or save it on a pdf file.
III. EXERCISE MENU
By means of the Exercise menu, the user can store up to 200 exercises.
Every exercise is a set of data, where Scenario and group of flight are the main features to
identify one Exercise.
Every exercise can be recalled when the user Send one exercise.
The Exercise Configuration Mask is composed by the following data:
Exercise name name given to the exercise
Scenario scenario
Exe type normal or demo
Exe speed speed of the exercise (1/8, 1/4, 1/2, normal, x2, x4 or x8)
FDP presenceYes to have FDP processing
Radars radars present in the exercise
Start Time exercise start time (hhmm)
Max flight maximum number of flights to be present in the exe
RPL group group of flights
Speed Transition Level Transition Level in FL, above which speed will be displayed in
Mach
Meteo meteo used in the exercise
Via the buttons Create, Modify, Delete, List, Print is possible to manage this window, creating,
modifying or deleting exercises.
At the moment of the start of the exercise, in the Send Mask (see next paragraphs SUPERVISOR
MENU) the user is able to choose one of the exercises saved in the Exercise Configuration mask,
via the arrows buttons, of via the List option. Or the user can modify the last exercise sent
through the Modify button.