Operational Training INDRA

Upgrade 0. Phase 1.
OPERATIONAL TRAINING
20th to 22tnd of March, 2015
INDEX
01 Introduction
02 Trajectory Computation (V. Split)
03 Graphical Route Modification (GRM)
04 Situation Data Display (SDD)
05 Flight Data Display (FDD)
06 Control & Monitoring (CMD)
07 Electronic Flight Strip (EFS)
08 Others
Upgrade_0, Phase 1. Operational Training.
| 2
INDEX
01 Introduction
08 Others
| 3
01 Introduction
INTRODUCTION
The software changes included in the Upgrade_0 contract are divided

into 4 phases:
Phase 1: 54 Software changes

Phase 2B: 4 Software changes
This training covers the 54 changes delivered in the Phase 1 that will
become operational when the new software will be installed in the
operational system (expected: before summer 2015).
The changes are divided into the following groups: Trajectory
computation (V. Split), Graphical Route Modification, Situation Data Display
(SDD), Flight Data Display (FDD), Control & Monitoring, Electronic Flight
Strip (EFS), Others.
| 4
INDEX
01 Introduction
08 Others
| 5
02 Trajectory Computation
TRAJECTORY COMPUTATION I.
NEW XFL MENU I.
A new pop-up menu has been introduced in the TDB with the nonstandard coordination levels (XX2/XX8) used for coordination
between the upper and lower sectors (V. Split).
To open the new menu, click and hold the XFL box in the TDB with
the Left Button of the mouse.
The levels presented in the pop-up menu are the offset (e.g. +/-2) of
the boundaries of all sectors combined in the current operational
sector.
The offset can be configured for different values (e.g. +/-2, +/-3, ...)
| 6
TRAJECTORY COMPUTATION I.
NEW XFL MENU II.
| 7
TRAJECTORY COMPUTATION II.

NEGOTIATION UPON VERTICAL ENTRIES.
Until now, the red/blue negotiation status in the XFL box was
triggered only if the level coordination was done T0 minutes to the
sector boundary, being T0 an adaptable parameter (configured to 5
minutes).
In the new implementation, ALL vertical sector entries trigger the
negotiation status.
There are 2 types of vertical sector entries:
From the top of the lower sector to the bottom of the upper sector (when
climbing)
From the bottom of the upper sector to the top of the lower sector (when
descending)
| 8
INDEX
01 Introduction
08 Others
| 9
Graphical Route Modification
GRM I.
INFORMATION ABOUT RANGE AND BEARING I
In GRM EDIT mode, information about the Range & Bearing is now
displayed.
The Range & Bearing is calculated from the Current Track Position
or Last Route Point introduced to the the Mouse Pointer
| 10
GRM II.
SCROLL IN ROUTE LIST FOR DCT
The system displays a list with All FP Route Points to be overflown

in the GRM DCT Selection Window.
The Selection Window shows a scroll bar when necessary and the
scroll is available with mouse scroll wheel.
| 11
GRM III.
TENTATIVE ROUTE
When opening the GRM DCT menu in the TDB of a track, a blue line
will display the tentative route from the Current Track Position to
the point selected with the mouse cursor.
The line will be displayed when passing the mouse cursor over the
DCT points available in the GRM menu
| 12
GRM IV.
COORDINATES ON GRM LIST
If there is a coordinate in the FP route, the system displays the full

name of the geodesic coordinates in the GRM point selection menu.
| 13
GRM V.
COLOURS IN ROUTE PRESENTATION I
In the previous implementation, the route colors were:
Route display mode:

GAT: Green
OAT: Purple
Edit display mode
GAT: Blue
OAT: Blue
In the new implementation, the route colors are:
Route display mode:

GAT: Green
OAT: Purple
Edit display mode

GAT: Blue
OAT: Orange New colour
| 14
GRM V.
COLOURS IN ROUTE PRESENTATION II
| 15
GRM VI.
NO HEADING AFTER DCT COMMAND
If a Heading is set in the TDB, and then a DCT Command is

performed from the GRM menu, the selected heading is removed.
| 16
GRM VII.
SELECTING SEVERAL CLOSE POINTS DURING GRM
In GRM EDIT mode, when clicking a point in the map, all points
contained in a configurable Window of Pixels will be displayed in
a pop-up menu.
: To choose a fixpoint, click in the fixpoint symbol (not in the
label!)
Details:
If there is no fixpoint in the Window of Pixels, the system will insert

the geodesic coordinate.
If there is only one fixpoint in the Window of Pixels, the system will
insert the fixpoint.
If there is more than one point in the Window of Pixels, the system will
show a menu with the points detected in the range
With a smaller zoom, more points will be detected in the Window

| 17
GRM VIII.
POINT OVERFLOWN DURING GRM
Previously, if during a Graphical Route Modification one route point

was overflown, the GRM was cancelled with a SYSMSG
Inaccessible Element
Also, the route after a GRM was composed by:
Current Track Position at the beginning of the GRM action

Rest of points inserted in the route
In the new implementation, GRM is accepted even if a point was
overflown in the meantime and the new route is composed by:
Current Track Position at the end of the GRM action

Rest of points inserted in the route
| 18
GRM VIII.
POINT OVERFLOWN DURING GRM
Example:
B
Original Route
ATCO Route Input
New Route
A
F
Original Route: A B C D E
When the track is between A and B the GRM menu is open to modify
the route to B F => go to B and then direct to F
The GRM command is executed after B was overflown, and the
system will modify the route to: A B track F
| 19
GRM IX.
DISCARD LAST POINT DURING GRM (UNDO)
The points inserted during a Graphical Route Modification can be

discarded.
To discard the last point introduced in the route, click the Central
Button of the Mouse.
Click the Central Button of the Mouse again to discard the previous
points consecutively.
| 20
INDEX
01 Introduction
08 Others
| 21
Situation Data Display (SDD)
SDD I. SORT LISTS IN REVERSER ORDER
It is possible to use Reverse Sorting in the following SDD tabular:

HOLD, LOST, CONFLICT , MSAW, APW, EXECUTIVE, PLANNER,
DEPARTURES, ARRIVALS, COORD IN, COORD OUT.
The sorting criteria can be changed by clicking the field in the header
of the tabular. The kind of sorting is displayed with an arrow in the
tabular field.
| 22
SDD II.
CFL IN FICTITIOUS TRACKS
FICTITIOUS Tracks now support CFL levels.
The CFL level can be input in the following ways:
Upon FICTITIOUS creation

From the TDB by clicking the CFL field
By Modify FICTITIOUS from the c/s menu in TDB
| 23
SDD III.
SQ/RO ALERTS PRIORITY
The priority for the RO (Route-OFF) and SQ (Squawk Change) alerts,

that share the same field in the TDB, has been modified in the
following way:
Old criteria:
Only Squawk alert ->

Only Route-OFF alert ->
Squawk & Route-OFF alerts ->
SQ
RO
RO
New criteria:
Only Squawk alert ->

Only Route-OFF alert ->
Squawk & Route-OFF alerts ->
SQ
RO
SQ
<- (new behaviour)
| 24
SDD IV.
UNCORRELATED 7000 TRACK COLOUR
For tracks with squawk 7000 and non-correlated, the track

presentation when Assumed will be as for the VFR traffic, ORANGE.
When the 7000 track is in transfer, the position receiving the transfer
will also see the track in ORANGE.
| 25
SDD V.
DELETION OF SYNTHETIC TRACK FROM TDB I
Synthetic Tracks can be deleted from the TDB in the following way:
Click in the callsign in the TBD of the synthetic track

-> callsign menu is opened
Click the DELETE SYNTH command

-> the Synthetic track is deleted
| 26
SDD V.
DELETION OF SYNTHETIC TRACK FROM TDB II
The system stores in the FP history which position perform the

synthetic track deletion command.
| 27
SDD VI.
STATUS FIELD IN SYNONYMS LIST
When a list of synonyms appears due to multiple Flight Plans with the
same callsign, the Flight Plan STATUS (INIT, PEND, NOTIF,
ACTIV, TERM) is displayed in the Synonyms tabular.
| 28
SDD VII.
RFL/ECL CHECKBOX
The RFL checkbox in the ECL menu in TDB is now enabled by

default.
| 29
SDD VIII.
STCA PRESENTATION I
Tracks in STCA conflict will be presented in the following way:
A Yellow/Red Frame around the Callsign

Track symbol in Yellow/Red colour
Speed Vector in Yellow/Red colour
Tracks involved in the conflict joined by a grey line
When a track in STCA is not focused, the TDB is NOT displayed in
Extended Mode
When a track in STCA is not focused, if there is a sector filled in
Line 0 or any alert (LB, SQ, RO...), Line 0 is also visible
| 30
SDD VIII.
STCA PRESENTATION I
| 31
SDD VIII.
STCA PRESENTATION II
If Heading, Speed or Rate is assigned to a track in STCA conflict, the

full TDB is displayed.
| 32
SDD IX.
ZONBLK NOTIFICATION
Colour of the ZONBLK button:
Yellow: When ACTIVE or CONFIRMED buttons are NOT enabled

White: When ACTIVE and CONFIRMED buttons are NOT enabled
The levels selected in the current altitude filter for restricted areas are
displayed in SDD MENU, above the ZONBLK button
| 33
SDD X.
FICTITIOUS FOR NON-ASUMED TRACKS
The creation of FICTITIOUS for tracks which are not assumed is

enabled.
| 34
SDD XI.
MODE S SELALT / CFL COHERENCE I
There is a new Coherence check between the MODE S

SELECTED ALTITUDE and the CFL, whenever the MODE S
SELECTED ALTITUDE data is Received and Valid.
When a level clearance is given to an aircraft, the pilot inputs this
level in the aircraft equipment and this value is transmitted by Mode S
(data visible in the ELW).
After a grace period (time for the pilot to input the level), a
discrepancy alert is displayed in the following ways:
The CFL box is underlined in Yellow in the TDB

The Yellow LB indication is displayed in the TDB
The SELALT in ELW is displayed in Yellow
| 35
SDD XI.
MODE S SELALT / CFL COHERENCE II
| 36
SDD XI.
MODE S SELALT / CFL COHERENCE III
This function has 2 configurable parameters in the system adaptation:
Time Threshold (Grace Period): Timer to let the pilot change the
SELALT value
Altitude Threshold: Altitude from which the Coherence check works
The configuration is done from the DBM position in path: SDP

ADAPTATION DATA -> DATABASE MANIPULATION -> SYSTEM
PARAMETERS
| 37
SDD XII.
MODE S SELALT IMPACT IN STCA PREDICTION ALGORITHM
In the previous software, CFL inhibited the STCA prediction when a

correct (safe) CFL was input.
E.g.: AIRCRAFT2 flying at FL360 and CFL=360, when AIRCRAFT1
(at FL380) starts to descend,
If AIRCRAFT1 has CFL=370, the STCA prediction is inhibited

If AIRCRAFT1 has CFL lower than 370, STCA prediction is triggered
In the new software, this behaviour is maintained but the MODE S
SELALT (if Received and Valid) has to match the CFL level. In the
previous example, one more case would trigger STCA prediction:
If AIRCRAFT1 has CFL=370, but SELALT does NOT match the CFL
value, STCA prediction is also triggered
| 38
SDD XIII.
HOLD AND TRANSFER STATUS WHEN LOOSING A TRACK
When a track in TRANSFER is LOST, and it is in HOLD, the

TRANSFER Status AND the HOLD Status is maintained.
If the track appears again, the TRANSFER Status AND the HOLD
Status is also maintained.
| 39
SDD XIV.
MANUAL CORRELATION IN MONO-RADAR MODE
It is possible to correlate a track with a Flight Plan in MONO-RADAR

Mode.
The correlation is done also in INTEGRATED Mode
| 40
SDD XV.
MODE S CALLSIGN
The MODE S Callsign is displayed in the ELW when it is Available.

If not available, the Flight Plan Callsign is displayed instead (as it was
until now).
If the MODE S Callsign does not match FP callsign it is displayed in
the ELW with a Red Colour.
| 41
SDD XVI.
LABELS FOR MODE S VALUES IN ELW
The SDD displays description labels for ModeS values in the ELW:
| 42
SDD XVII.
USER PREFERENCES
The SDD identify the maps in the USERPREF using descriptive
names.
Current
UPG0
| 43
INDEX
01 Introduction
08 Others
| 44
Flight Data Display (FDD)
FDD I.
TIMESTAMP FOR OLDI MESSAGES ARCHIVE
The FDD displays the timestamp of the OLDI archive entries in the
OLDI Archive window.
| 45
FDD II
LOGIN TIME USER INFORMATION
The standalone FDD (without SDD) displays the time of Login and
User at the top right corner of the screen.
| 46
FDD III.
NEW FDD FONT SIZE I
There are 3 different font sizes/type available in FDDs for the
following windows: FP Retrieval, Queue summary window, FP
template in FDD (not SDD), List of synonyms, Bottom bar, QNH, EST
window and FP History.
| 47
FDD III.
NEW FDD FONT SIZE II
| 48
INDEX
01 Introduction
08 Others
| 49
Control & Monitoring (CMD)
CMD I.
SECTORIZATION PLANS. DBM DEFINITION.
Sectorization Plan is a stored predefined sectorization with a Map of

Operational Sectors and control sectors.
Sectorization plans are defined in the DBM position with a limit of 500.
| 50
CMD II.
SECTORIZATION PLANS. CMD.
A new section appears in CMD Sectorization Window

All Operational Sectors contained in the Sectorization Plan must be
assigned to an UCS, otherwise, the CMD returns an error with the
OPS name which is not assigned and no changes are applied to
the existing sectorization.
If all Operational Sectors in the Sectorization Plan are assigned to

UCSs, the sectors in the Sectorization Plans are added to the existing
ones of each Operational Sector.
:: To assure the correct implementation of a Sectorization Map, all
sectors in the unit affected by the Map (GAT/OAT/APP/FIS), should
be included in the Sectorization Plan.
| 51
CMD II.
SECTORIZATION PLANS. CMD.
| 52
CMD III.
MOUSE CURSOR
The CMD mouse cursor is displayed in a bigger size.
| 53
CMD III.
DEFAULT SECTORIZATION .
OPERATIONAL SECTOR WITHOUT FREQUENCY.
The DBM allows the definition of Operational Sectors without

frequency assigned in the Default Sectorization table.
| 54
INDEX
01 Introduction
08 Others
| 55
Electronic Flight Strip (EFS)
EFS I.
-FREE- IN GATE FIELD WITH RIGHT BUTTON
Right Button click with the mouse in the "GATE" field of the EFS strip
opens free input text window .
| 56
EFS II.
ADEP ZZZZ IN LOCAL EFS
The ADEP field of a LOCAL EFS in the creation window is filled with
"ZZZZ" value by default.
| 57
EFS III.
ENTER ACCEPTS THE CONTENT OF FREETEXT
EFS stores the content of Freetext Field by pressing the

ENTER/RETURN key.
| 58
EFS IV.
LIMIT OF ENTRIES IN POP-UP MENUS
Capacities (number of entries):
GATE menu: up to 200
SID/STAR: up to 80
VFR Routes: up to 40
TAXI-TO: up to 120
LOCAL EFS CALLSIGN: up to 40
OBST. SYMBOL: up to 50
| 59
EFS V.
SID FIELD UPON RWY CHANGE I
After change in RWY, EFS updates or keeps the SID and highlights
it or not depending on where the strip is located (Below/Above
CLEARENCE RECEIVED line and on how the RWY is changed (FDD
RWY menu or EFS).
:See the table in the following slide.
The highlight of the SID field is removed only after LB click on the
SID field.
| 60
EFS V.
SID FIELD UPON RWY CHANGE II
SID EFS
SID/LEVEL
HEADING/
LEVEL
RWY EFS
RWY FP
SID FP
SID
Highlight
Manual Change of SID

from EFS
New
SID
New
SID/LEVEL
New HEADING/
LEVEL
No change
No change
New SID if valid

else
no change
NO
Manual Change of RWY

from EFS
SID2
New Runway New calculated

if valid else SID if any else
no change
no change
YES
The FP SID was changed

(route change, CHG
reception)
Strip above
CLEARANCE
upon runway change
Strip above
CLEARANCE
(route change, CHG
reception)
SID2/LEVEL
SID2 (orange)
RWY2
SID2
SID2/LEVEL
(new sid, old
level)
SID2 (orange)
No change
No change
SID2
YES
SID not
updated
SID not
updated
SID not updated
No change
RWY2
SID2
NO
SID2
SID2/LEVEL
(new sid, old
level)
SID2 (orange)
No change
No change
SID2
NO
SID2
SID2/LEVEL
(new sid, old
level)
SID2 (orange)
RWY2
RWY2
SID2
NO
Strip below
CLEARANCE
upon runway change
Strip below
CLEARANCE
| 61
EFS VI.
CTOT MAINTAINED AFTER EOBT CHANGE I
Upon reception of CHG and DLA messages, the FP Flow information

(e.g. SLOT time) will not be removed.
FP has CTOT information (CTOT=1000)

Note: CTOT field is orange due to the current time is
higher than the expected CTOT
FP receives a CHG message (changes the
STS/HEAD)
After CHG ack, the strip keeps the CTOT

information
| 62
EFS VI.
CTOT MAINTAINED AFTER EOBT CHANGE II
| 63
EFS VII.
DIRECT TRANSFER FROM DEL TO GND
Previous behaviour in DEL position:
New behaviour in DEL position:
Drag&Drop strip to GND: Moves the strip to "GND PDG List"

Drag&Drop strip to PDG: Moves the strip to "GND PDG List"
Drag&Drop strip to GND: Moves the strip directly to GND position

Drag&Drop strip to PDG: Moves the strip to "GND PDG List"
| 64
EFS VIII. ACT" BUTTON POSITION
EFS displays the "ACT" button in the left side of the following lists
(instead of the right side):
TWR ARR
GND DEP
Delivery Temporary
DE-ICING
BIN ("DEL" button is now in the right side of the BIN list instead of the
left)
| 65
EFS IX. INCREASE EFS FONT SIZE
The Font Size in EFS Lists is bigger:
| 66
EFS X. CNL BACKGROUND IN RED
The CNL message reception is indicated by highlighting the EFS

EOBT field in RED
After ACK, the EOBT field changes to the normal colour of the strip
| 67
EFS XI. TAXI TO FIELD UPON RWY CHANGE
Upon runway change, the TAXI-TO field is maintained
| 68
EFS XII.
TIME FIELD NOTIFICATIONS IN THE EFS LISTS I
The notifications, colours and messages in the TIME field in EFS lists
are the same as in the the Eletronic Flight Strips.
Colour notifications for CTOT validity in EFS lists are the same as in
the the Eletronic Flight Strips.
The notifications and messages in the TIME field in EFS lists can be
acknowledged just like in the Eletronic Flight Strips.
| 69
EFS XII.
TIME FIELD NOTIFICATIONS IN THE EFS LISTS II
CTOT=1010 => ACK CTOT => CHG MSG => ACK CHG
| 70
INDEX
01 Introduction
08 Others
| 71
Others
OTHERS I.
LOCAL CCAMS ADDRESS
The DBM defines a Local CCAMS address which is used as the

ORIGIN field of the COR messages.
In case the Local CCAMS address is not defined with DBM the COR
messages will be generated without the ORIGIN field.
| 72
Others
OTHERS II.
COR DELAY AFTER FSA
The DBM defines a time parameter from 0 to 180 seconds used to

delay the COR message sending after the FSA transmission.
| 73
Others
OTHERS III.
PROCESSING ROUTES COMPOSED BY TWO EXTERNAL
POINTS ONLY I
The system now processes routes that crosses the FIR but only
composed by two external known points or geodesic locations
defined inside the working area.
The system calculates the FIR Crossing points and insert these
Points into the route.
| 74
Others
OTHERS III.
PROCESSING ROUTES COMPOSED BY TWO EXTERNAL
POINTS ONLY II
| 75
Others
OTHERS IV.
LIMIT OF SID/STAR POINTS
The limit of points for one SID/STAR is increased to 12 points

(before 6).
The limit of Route points is 35

Both limits will be further increased in the folowing Phases of the
Upgrade_0 contract.
| 76
Others
OTHERS V.
FICTITIOUS TRACK OPERATIONS LOG
The system stores in the SNET log file, upon the manual
Creation/Modification/Cancellation of a fictitious track, the following
data: Action time, Working position, Squawk and Fictitious Callsign.
| 77
Others
OTHERS VI.
OLDI ACT SENDING TIME REVIEW
The coordination data will be displayed in the Planner List at least

One Minute before the ACT is sent, to allow the revision of the data.
Examples:
Departure flight close to the FIR boundary: If upon departure, the Flight
Plan is already within the time to send ACT, the ACT will be delayed by
one minute to allow revision of the coordination data (ref: EPSC).
Outgoing flight: If a flight plan modification (e.g. shortcut in the route)

implies an immediate ACT transmission, the ACT is delayed by one
minute to allow revision of the coordination data.
| 78
Others
OTHERS VII.
ELIMINATION OF RPL FUNCTIONALITY
The RPL functionally has been eliminated from the system and the
FDD buttons related to RPL functions have been removed.
| 79
Others
OTHERS VIII.
NEW FIS KRAKW AND GDANSK POSITIONS
New SDD59
New SDD60
| 80
Francisco Carlos Mrquez Casco

fcmarquez@indracompany.com
Al. Jerozolimskie 136
02-305 Warszawa
T +48 664 548 054
www.indracompany.com

Operational Training INDRA

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Operational Training INDRA

Hochgeladen von

Copyright:

Verfügbare Formate

Upgrade 0. Phase 1.

Upgrade_0, Phase 1. Operational Training.

Upgrade_0, Phase 1. Operational Training.

The software changes included in the Upgrade_0 contract are divided

Phase 1: 54 Software changes

Upgrade_0, Phase 1. Operational Training.

Upgrade_0, Phase 1. Operational Training.

Upgrade_0, Phase 1. Operational Training.

Upgrade_0, Phase 1. Operational Training.

TRAJECTORY COMPUTATION II.

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

The system displays a list with All FP Route Points to be overflown

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

If there is a coordinate in the FP route, the system displays the full

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

In the previous implementation, the route colors were:

Route display mode:

Edit display mode

In the new implementation, the route colors are:

Route display mode:

Edit display mode

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

If a Heading is set in the TDB, and then a DCT Command is

Upgrade_0, Phase 1. Operational Training.

Graphical Route Modification

If there is no fixpoint in the Window of Pixels, the system will insert

With a smaller zoom, more points will be detected in the Window

Graphical Route Modification

Previously, if during a Graphical Route Modification one route point

Current Track Position at the beginning of the GRM action

Current Track Position at the end of the GRM action

Graphical Route Modification

Graphical Route Modification

The points inserted during a Graphical Route Modification can be

Upgrade_0, Phase 1. Operational Training.

Upgrade_0, Phase 1. Operational Training.

Situation Data Display (SDD)

SDD I. SORT LISTS IN REVERSER ORDER

It is possible to use Reverse Sorting in the following SDD tabular:

Upgrade_0, Phase 1. Operational Training.

Situation Data Display (SDD)

FICTITIOUS Tracks now support CFL levels.

The CFL level can be input in the following ways:

Upon FICTITIOUS creation

Upgrade_0, Phase 1. Operational Training.

Situation Data Display (SDD)

The priority for the RO (Route-OFF) and SQ (Squawk Change) alerts,

Only Squawk alert ->

Only Squawk alert ->

<- (new behaviour)

Upgrade_0, Phase 1. Operational Training.

Situation Data Display (SDD)

For tracks with squawk 7000 and non-correlated, the track

Upgrade_0, Phase 1. Operational Training.