0029200000000MA02_2-0_DBM-UM

Supply, Installation, Testing and Commissioning of Tower ATS Automation System Database Manager User Manual (DBM-UM) Edition: 2 Revision: 0

04 November 2010

Document Number: 0029200000000MA02

Prepared for: AIRPORTS AUTHORITY OF INDIA (AAI) Airports Authority of India, Rajiv Gandhi Bhawan, Safdarjung Airport, New Delhi - 110

Prepared by:

Indra Sistemas, S.A. Ctra. de Loeches, 9 28850 Torrejón de Ardoz Madrid, Spain Indra Proprietary Information This document contains proprietary data pertaining to items, or components, or processes or other matter developed or acquired at the private expense of the Indra Sistemas, S.A. and/or any other titular holder and is restricted to use only by Indra or the Customer under the terms of this Proposal. Neither said document nor said data shall be furnished or disclosed to or copied or used by other persons outside the conditions of this Proposal as applicable without the express written approval of Indra Sistemas and/or any other titular holder.

DOCUMENT Nº: 0029200000000MA02

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page ii






Page iv



PAGE EDITION AND REVISION RECORD

This document contains the following pages in the indicated editions and revisions PAGE

EDITION

REVISION

All

1

0

All

2

0


PAGE

EDITION REVISION

PAGE


EDITION REVISION

Page v






Page vi



REGISTER OF CHANGES TO THE DOCUMENT

EDITION

REVISION

DATE

AFFECTED PAGES

1

0

2010-08-04

All

First Edition

2

0

2010-11-04

All

Second Edition


REASON FOR CHANGE


Page vii






Page viii



Table of Contents 1

2

Introduction ........................................................................................................................... 1-1 1.1

Scope ............................................................................................................................. 1-1

1.2

Manipulation of tables from the Database ...................................................................... 1-2

1.2.1

Renaming an element from the Database. ............................................................ 1-3

1.2.2

Copying an element from the Database. ............................................................... 1-3

1.2.3

Deleting an element from the Database. ............................................................... 1-4

1.2.4

Creating an element from the Database. ............................................................... 1-4

1.2.5

Report concerning a table from the Database. ...................................................... 1-5

Main Functionalities .............................................................................................................. 2-1 2.1

2.1.1

Main Screen Exit (EXIT) ........................................................................................ 2-2

2.1.2

Backup (BACKUP) ................................................................................................ 2-2

2.1.3

Database Copy (COPY) ........................................................................................ 2-2

2.1.4

Data Removal (DESTROY) ................................................................................... 2-2

2.2 3

Main Screen actions ....................................................................................................... 2-2

Database Selection (SELECT) ....................................................................................... 2-3

Edit Adaptation Data ............................................................................................................. 3-1 3.1

FDP Adaptation Data. .................................................................................................... 3-1

3.1.1 Database manipulation. ......................................................................................... 3-1 3.1.1.1 AFTN Addresses ............................................................................................ 3-2 3.1.1.2 AFTN Circuits ................................................................................................. 3-3 3.1.1.3 Fixpoints ......................................................................................................... 3-5 3.1.1.4 Airways........................................................................................................... 3-7 3.1.1.5 Aircraft Groups ............................................................................................... 3-9 3.1.1.6 Aircraft Types ............................................................................................... 3-12 3.1.1.7 Wind Zones .................................................................................................. 3-14 3.1.1.8 Working Area ............................................................................................... 3-16 3.1.1.9 Airports......................................................................................................... 3-17 3.1.1.10 Approach routes ........................................................................................... 3-19 3.1.1.11 Control Centers ............................................................................................ 3-21 3.1.1.11.1 FMTP Options ....................................................................................... 3-25 3.1.1.11.2 Control Center Options .......................................................................... 3-27 3.1.1.12 Sectors ......................................................................................................... 3-29 3.1.1.12.1 Basic Sectors......................................................................................... 3-30 3.1.1.12.2 Subsectors ............................................................................................ 3-33 3.1.1.12.3 Control Sectors ...................................................................................... 3-36 3.1.1.13 Coordination Fix points ................................................................................. 3-39 3.1.1.14 External Regions .......................................................................................... 3-43 3.1.1.15 Routes.......................................................................................................... 3-44 3.1.1.15.1 Standard Routes.................................................................................... 3-49 3.1.1.15.2 Points Pairs ........................................................................................... 3-51 3.1.1.16 Geographic Zones ........................................................................................ 3-52 3.1.1.16.1 Geographic Regions .............................................................................. 3-53 Database Manager User Manual


Page ix



3.1.1.16.2 Entry points between regions................................................................. 3-55 3.1.1.16.3 Standard routes between regions .......................................................... 3-56 3.1.1.17 Pressure Zones ............................................................................................ 3-58 3.1.1.18 User Passwords ........................................................................................... 3-61 3.1.1.19 Meteo Messages Airports ............................................................................. 3-63 3.1.1.20 Destination Aerodromes ............................................................................... 3-64 3.1.1.21 SSR Codes .................................................................................................. 3-65 3.1.1.22 Route Conditions .......................................................................................... 3-73 3.1.1.23 AMC ............................................................................................................. 3-76 3.1.1.24 Aircraft Operators ......................................................................................... 3-82 3.1.1.25 UCS Strip Printers ........................................................................................ 3-82 3.1.2

Generation of FDP Adaptation Files. ................................................................... 3-84

3.1.3

SDD maps generation. ........................................................................................ 3-85

3.2

SDP Adaptation Data ................................................................................................... 3-86

3.2.1 Database Manipulation........................................................................................ 3-88 3.2.1.1 Radar Internal Config ................................................................................... 3-88 3.2.1.2 Radar External Protocol (RDCU 3) ............................................................... 3-89 3.2.1.3 Radars ......................................................................................................... 3-91 3.2.1.4 Directional Finders ....................................................................................... 3-95 3.2.1.5 MSAW .......................................................................................................... 3-96 3.2.1.6 STCA Parameters ........................................................................................ 3-99 3.2.1.7 System Parameters .................................................................................... 3-102 3.2.1.8 SDD Parameters ........................................................................................ 3-103 3.2.1.9 Profile Parameters ...................................................................................... 3-103 3.2.1.10 Profiles ....................................................................................................... 3-104 3.2.1.11 SDD Printers .............................................................................................. 3-106 3.2.1.12 Filter Code Ranges .................................................................................... 3-107 3.2.1.13 VSP ............................................................................................................ 3-109 3.2.1.13.1 FDP Parameters .................................................................................. 3-109 3.2.1.13.2 AMHS Parameters ............................................................................... 3-112 3.2.1.13.3 APW Parameters ................................................................................. 3-112 3.2.1.13.4 MTCD Parameters ............................................................................... 3-113 3.2.1.13.5 SDP Parameters.................................................................................. 3-114 3.2.2 3.3

Generation of Adaptation SDP files ................................................................... 3-116

ATG Adaptation Data ................................................................................................. 3-118

3.3.1 Database manipulation...................................................................................... 3-118 3.3.1.1 Holding Patterns ......................................................................................... 3-118 3.3.1.2 Instrumental Landing Procedures ............................................................... 3-121 3.3.1.3 Inter Approach Speed Area ........................................................................ 3-123 3.3.1.4 Aircraft Performances ................................................................................. 3-124 3.3.1.5 Aircraft Subtypes ........................................................................................ 3-128 3.3.1.6 Airports Runways ....................................................................................... 3-130 3.3.1.7 Arrival Procedures ...................................................................................... 3-132 3.3.1.8 Departure Procedures ................................................................................ 3-134 3.3.1.9 ADS VDL .................................................................................................... 3-137 3.4

BADA Adaptation Data ............................................................................................... 3-139

3.4.1 4

Generation of BADA Adaptation Files ............................................................... 3-139

Graphic Tool ......................................................................................................................... 4-1



Page x


4.1

5


Draw adaptation Data ..................................................................................................... 4-1

4.1.1

Fixpoints................................................................................................................ 4-2

4.1.2

Airports.................................................................................................................. 4-3

4.1.3

Airways ................................................................................................................. 4-4

4.1.4

Sectors .................................................................................................................. 4-5

4.1.5

SID & STAR .......................................................................................................... 4-9

4.1.6

Coordination points (COPS) ................................................................................ 4-10

4.1.7

Standard Routes (STD) ....................................................................................... 4-10

4.1.8

Radars ................................................................................................................ 4-11

4.1.9

Wind Zones ......................................................................................................... 4-12

4.1.10

MSAW ................................................................................................................. 4-13

4.1.11

Profiles ................................................................................................................ 4-14

4.1.12

CDRs .................................................................................................................. 4-15

4.1.13

QNH .................................................................................................................... 4-16

4.1.14

Restricted Areas.................................................................................................. 4-17

4.1.15

MAP .................................................................................................................... 4-18

Data Distribution ................................................................................................................... 5-1 5.1

Map Colours ................................................................................................................... 5-2

5.2

Generate All Data Files .................................................................................................. 5-3

5.3

Load Operational Generated Data .................................................................................. 5-3

Config_info.adap ..................................................................................................................... 5-6 Appendix A - Abbreviations .......................................................................................................... A-1



Page xi






Page xii



List of Tables Table A-1:

Abbreviations ........................................................................................................A-1



Page xiii






Page xiv



1 Introduction 1.1

Scope

The purpose of this tool is to be able to create, manage and remove databases using a friendly environment. In order to manipulate data, it is not necessary any previous knowledge of SQL language (Standard Query Language), this tool solves this difficulty. When the operator creates the group of adaptation data, it is not necessary to know the internal relationships between different database tables, this tool solves this problem internally. All modified or created data using this tool is checked in order to produce a coherent adaptation. When data creation or management is erroneous an “Error Window” appears indicating the type of error. In particular, if the error concerns a numeric value, the range of admissible values is displayed. This tool includes the whole Adaptation Process consequently it incorporates Database Creation and Adaptation Data Loading. Obviously, it allows successive Data Modification.



Page 1-1


1.2


Manipulation of tables from the Database

When the "DATABASE MANIPULATION" option is selected, the "FDP Adaptation” Table appears showing all the necessary Adaptation Tables concerning the FDP In this section we will learn how to modify, remove or rename a FDP Adaptation Table. All the actions described are identically feasible for all the Adaptation Tables. Tables within the “Adaptation FDP” table window are: The selection and on-screen display of a FPD table is performed by means of double click with the left button (LB) of the mouse. As a result of this operation, the selected FDP Table window appears. This table displays all the elements of the table and the main fields of each one of them. For example, if the “Airports” table is selected, its related Table window will be similar to the figure below: To modify one of the elements from the selected window, perform double click with the LB on its left

field (the element identification field, in this case, on the ICAO column). Doing this, its related “Modification” window will appear. For instance, if SKBO airport data needs to be modified, its corresponding “Modification” window will be: This “ Modification" window shows all the data referred to the selected Airport. Press the "Save" button to store changes into the FDP table. “EXIT” closes the window without changes. If some data has been modified and its value is not the correct one, an “Error Message” window will appear indicating where the error is and, in case of it being a numeric data, the range of potential values for this field.



Page 1-2



1.2.1 Renaming an element from the Database. To rename an element belonging to a selected table, press the "Rename" button on the table and, as a consequence, the “Rename” window will appear.

It is important to notice that this “Rename” window only allows access to the identifier field of the element. Other entries are not accessible. Once the new identifier has been introduced, press the "Save" button to store the new element in the Database. As usual, the “EXIT” button closes the window without performing any change.

1.2.2 Copying an element from the Database. To copy an element in the selected FDP table window, first select the element and then press the "Copy" button. As a consequence of these actions, the “Copy” window will appear. This is a useful tool to create a new element with similar characteristics to the other one but keep in mind that the identifier cannot be repeated. That is, this option demands to change the identifier field of the new element, if not, an "Error” window will appear indicating that a duplicated element has been detected. Once the new identifier and all the corresponding data has been modified, press the "Save" button to store this new element in the Database. As usual, the “EXIT” button closes the window without performing any change.



Page 1-3



1.2.3 Deleting an element from the Database.

To delete an element in the selected FDP table, first select the element and then press the "Delete" button. As a consequence of these actions, the “Delete” window will appear. For example, if the "SKBO" Airport must be deleted, first make use of the mouse or scroll bar in order to select this airport, then press the “Delete” button. As a consequence the following window will appear: Take into account that all the fields within this window are not accessible. To accomplish the delete process, it will be enough to press the “Save” button. The “EXIT” button closes the window without performing any action.

1.2.4 Creating an element from the Database. To create a new element in the selected FDP table, press the "Create" button. As a consequence of this action, the “Creating” window will appear. Notice that all the fields belonging to this window are accessible and they must be filled in. Once this is done, press the “Save” button. The “EXIT” button closes the window without performing any action.



Page 1-4



1.2.5 Report concerning a table from the Database. To carry out a Report, press the "Create" button in the selected FDP table. As a result a submenu will appear with two options:

 Report File (All the data are sent to a file)  Print File (All the data are sent to a printer) In case of sending data to a file, this one will be located in the following directory: /local/”Proj_NAME”/adap/exec/tcl-tk/databases/current_database/reports



Page 1-5






Page 1-6



2 Main Functionalities When "dbsman.tcl" application is executed, its main screen is displayed.

The main screen shows the whole set of operative system databases. Five buttons are displayed at the top of the main screen:

 EXIT Button: This button is used to shut-down the DBM.  Backup Button: This action makes a new copy from the selected database. This copied database will be saved in the same directory than the rest of databases. It is mandatory that the name of the copied database be different that the rest of databases.

 Copy Button: This function is used to copy a new database based on another selected database. When the process is finished the DBM will contain two identical databases with different names.

 Destroy Button: To erase the selected database. When the button is pressed, the system will show a confirmation window.



Page 2-1



 Select Button: This button is used to open a database previously selected by clicking with the left button of the mouse. This button shows all options for the selected database.

2.1

Main Screen actions

2.1.1 Main Screen Exit (EXIT) Select this button for leaving the application. Pressing the “ESC” key can also carry out this action.

2.1.2 Backup (BACKUP) Backup Icon. When this button is pressed, the DBM software makes a backup file for the selected database. It s possible to check that the next directory contains the backup file: /local/”PROJECT-NAME”/adap/exec/tcl_tk/databases/"DATABASE-NAME"/backup/ exist the file *.bck.

2.1.3 Database Copy (COPY) This button is used to copy a database that has been previously selected with the left button of the mouse. The result is a new database that is exactly the same as the original one. When this button is selected an edition screen appears for writing the new name corresponding to the new database.

Fill in with the name of the new database and press the "OK" button. When the OK button is pressed the new window appears to inform about the copy process.

2.1.4 Data Removal (DESTROY) This button is used to remove a database that has been previously selected with the mouse. In order to avoid possible undesired actions, a confirmation screen will be displayed asking for a confirmation.



Page 2-2


2.2


Database Selection (SELECT) To select a specific database, choose it by using le LB of the mouse and press the "Select" button on the main screen.

As a result of this action, the "Subsystems” Screen will appear containing all the Adaptation subsystems. DBM Subsystems FDP ADAPTATION DATA 1

AFTN Addresses

2

AFTN Circuits

3

Fixpoints

4

Airways

5

Aircraft Groups

6

Aircraft Types

7

Wind Zones

8

Working Area

9

Airports

10

Approach routes

11

Control Centers

12

Sectors 12.1

Basic Sectors

12.2

Subsectors

12.3

Control Sectors

13

Coordination Fix points

14

External Regions

15

Routes

16

15.1

Standard Routes

15.2

Points Pairs

Geographic Zones 16.1

Geographic Regions

16.2

Entry points between regions

16.3

Standard routes between regions

17

Pressure Zones

18

User Passwords

19

Meteo Messages Airports

20

Destination Aerodromes

21

SSR Codes 21.1

Destination Regions



Page 2-3



DBM Subsystems 21.2

Special Use Codes

21.3

Incoming Codes

21.4

Outgoing Assignable Codes

21.5

Outgoing Retainable Codes

22

Route Conditions

23

AMC

24

Aircraft Operators

25

UCS Strip Printers

SDP ADAPTATION DATA 1

Radar Internal Config

2

Radar External Protocol

3

Radars

4

Directional Finders

5

MSAW

6

STCA Parameters

7

System Parameters

8

SDD Parameters

9

Profile Parameters

10

Profiles

11

SDD Printers

12

Filter Code Ranges

13

VSP 13.1

FDP Parameters

13.2

AMHS Parameters

13.3

APW Parameters

13.4

MTCD Parameters

13.5

SDP Parameters

ATG ADAPTATION DATA 1

Holding Patterns

2

Instrumental Landing Procedures

3

Inter Approach Speed Area

4

Aircraft Performances

5

Aircraft Subtypes

6

Airports Runways

7

Arrival Procedures

8

Departure Procedures

9

ADS VDL



Page 2-4



DBM Subsystems BADA ADAPTATION DATA DRAW ADAPTATION DATA 1

Fixpoints

2

Airports

3

Airways

4

Sectors

5

SID & STAR

6

Coordination points (COPS)

7

Standard Routes (STD)

8

Radars

9

Wind Zones

10

MSAW

11

Profiles

12

CDRs

13

QNH

14

Restricted Areas

15

MAP

DATA DISTRIBUTION 1

Map Colours

2

Generate All Data Files

3

Load Operational Generated Data

The screen is divided into the following windows:

 General Information Window  Main Menu Window



Page 2-5



FDP adaptation data contains all the tables related to flight data processing. RDP adaptation data contains all the tables related to radar data processing. ATG adaptation data contains the table related to the simulator. DRAW adaptation data contains all related data used to display the geographical data for the database (Fixpoints, airways, airports, radars,…) Load adaptation data is used to load all the adaptation data into the system.



Page 2-6



3 Edit Adaptation Data The following paragraphs will show the existent subsystem screens.

3.1 FDP Adaptation Data. The "FDP ADAPTATION DATA" option is selected by performing double click with the LB of the mouse. Once it has been selected, the "FDP Options” Window appears and displays the following three options: ●

DataBase Manipulation: manipulate the adaptation data.

●

Generate Data Files: used to generate the adaptation data files.

●

Generate Map Files: used to generate the default maps for SDDs.

used

3.1.1 Database manipulation.

Data Base manipulation option shows the list of tables available to be modified or reviewed



Page 3-1

to



3.1.1.1 AFTN Addresses Description:

This table contains information to define the owner Control Center AFTN addresses used for received and sent AFTN messages.

Location:

FDP Adaptation Data. -> Database manipulation. -> AFTN Addresses

Capacity:

30 elements

Main Window:

Buttons:


●

EXIT: Exit from this table to the previous screen.

●

Report: Option to print the data from the visual window to a file or a pre-defined printer.

●

Rename: Change the name for the selected data.

●

Copy: Copy the selected data into the same table.

●

Delete: Erase the selected data from the table.

●

Create: Make possible to create a new data in the table with a blank template.


Page 3-2



Data window:

Buttons: List of Fields:

●


●

Save: Save all data into table.

●

IDENTITY: AFTN address for the entered defined categories.

●

CATEGORY: The different options are: a) Local AFTN Addresses: Own Control Centre direction. b) Destination Address of SVC Messages: AFTN direction to send the SVC messages. (Line 1 or Line 2) c) Identity Addresses of SVC Messages: AFTN direction for origin of SVC messages. d) Principal IFPS Addresses: Main IFPS (Bretigny or Haren) AFTN address. e) Secondary IFPS Addresses: Secondary IFPS (Bretigny or Haren) AFTN address. f) Information Message Address (INF): Address where to send the information messages. g) CFMU/TACT: AFTN addresses for the CFMU/TACT transmissions h) CPL Addresses INF: AFTN address for CPL transmission

3.1.1.2 AFTN Circuits Description:

This table contains information concerning channels transmission used for the headers of the transmitted and received messages. These headers must start with the code shown in the table, if not they will be refused, and showed in the AAI queue on the FDDs. This information will be used by the DBM software to create the Config_info.adap file (see appendix).

Location:

FDP Adaptation Data. -> Database manipulation. -> AFTN Circuits



Page 3-3


Capacity:


This table accepts up to one (1) element and two circuits

Main Window:

Buttons:

List Fields:

●


●

Save: Save all data into database.

●

Report: Option to print the data from the visual window to a file or a predefined printer.

●

AFTN Transmission Circuit 1: Key field in the header of a message transmitted through AFTN. (via circuit 1)

●

AFTN Transmission Circuit 2: Key field in the header of a message transmitted through AFTN. (via circuit 2)

●

AFTN Reception Circuit 1: Key field in the header of a message received through AFTN. (via circuit 1)

●

AFTN Reception Circuit 2: Key field in the header of a message received through AFTN. (via circuit 2)

●

LINE AFTN TYPE: These options allows to configure the format for the physical AFTN connection between RS-232, TCP/IP, AMHS_P3 and AMHS_P7

of



Page 3-4



●

AFTN over IP: In case of TCP/IP protocol is possible define the port, Ethernet card and hostname, as well as if it is considered as master or slave. For each TCP/IP connection.

●

AMHS Parameters: ○

AFTN Origin Line: Originator in X.400 format

○

AFTN Password Line: Password for the user

○

○

AFTN Ms Pa Line: String encoding of MS or MTA Presentation Address to contact. Example "3001" /Internet=amhs+3001 AIDC Origin Line: Originator in X.400 format

○

AIDC Password Line: Password for the user

○

AIDC Ms Pa Line: String encoding of MS or MTA Presentation Address to contact. Example "3001" /Internet=amhs+3001

3.1.1.3 Fixpoints Description:

This table contains all the necessary information for the definition of same fixpoints. These points are essential for the construction of airways, arrival procedures (STAR), departure procedures (SID) as well as coordination points. These points will be used to generate the route on the Flight Plans Creation window at the SDD/FDD.

Location:

FDP Adaptation Data. -> Database manipulation. -> Fixpoints

Capacity:

This table accepts up to four thousand (4.000) elements.



Page 3-5



Main Window:

Buttons:

●


●


●


●


●


●


Data window:



Page 3-6




●


●


●

FIX ID: Identifier of the significant point, up to six characters

●

STRIP PRINTING: To enable or disable the capacity to print the fix point on the strip.

●

MAP PRINTING: Possibility of displaying the Fix Points on the SDD.

●

FIX TYPE: Allows to the system to displays on a different Map Menus the different kind of Fix points

●

LOCATION: Geodesic position of the significant point.

●

○

Latitude DDMMSS (N or S)

○

Longitude DDDMMSS (E or W)

FIR SITUATION: Relative position of the significant point regarding the defined sectorization. ○

Internal: when the significant point is inside a sector classified as internal.

○

External: when the significant point is inside a sector classified as external.

3.1.1.4 Airways Description:

This table contains information concerning the definition of airways, with a superior and an inferior level, as well as the sequence of fixpoints that form these airways. In order to configure the route of a flight plan, the airways defined here can be used directly in the route field on the Flight Plans Creation window at the SDD or General FDD.

Location:

FDP Adaptation Data. -> Database manipulation. -> Airways

Capacity:

This table accepts maximum to five hundred (500) elements and up to twenty five (25) fixpoints per airway.



Page 3-7



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

Append: To append a new point at the end of the list, press the

Data window:

Buttons:



Page 3-8



“Append” button. As a result, an edit field will be displayed to allow the addition of the new point.

●

●

●

List of Fields:

○

OK: Confirm new Fixpoint

○

Forget: Cancel new Fixpoint and don’t introduce it.

Modify: For modifying a particular point, it will be enough to select it and press with double-click on the Fixpoint and press on Modify Button with the LB. As a result, the edit field will be displayed to allow the modification. ○


○


Insert: For inserting a particular new point, select the previous point with the LB, then insert the new one and press on Insert Button with the LB. ○


○


Delete: For eliminating a point, select it with the LB and press on Delete Button with the LB. As a consequence, the edition field will appear ○


○


●

AIRWAY NAME: Airway identifier, it accepts up to six characters

●

MINIMUM ALTITUDE: Minimum accepted Altitude using a particular airway. (Hf)

●

MAXIMUM ALTITUDE: Maximum accepted Altitude using a particular airway. (Hf)

●

PATHWAY POINTS: Set of points defining an airway. These points must be defined previously in the Fixpoints table, if not an “Error” window will appear.

3.1.1.5 Aircraft Groups Description:

This table contains information about the Groups of Aircrafts, including the performances like flight altitudes, speeds, etc. The aim of this table is to create groups of aircraft performance containing different aircrafts which characteristics are similar enough to be grouped. All information contained in these tables will be used by the FDPs servers to calculate the estimated time for each fixpoint of the route.

Location:

FDP Adaptation Data. -> Database manipulation. -> Aircraft Groups

Capacity:

This table accepts up to two hundred and fifty (250) elements and up to five (5) layers per aircraft group.



Page 3-9



Main Window:

Buttons:


●


●


●


●


●


●



Page 3-10



Data window:

Buttons:

●


●


●

Create: To create a new layer definition, press the “Create” button. As a result, an edit field will be displayed to allow the addition of the new layer.

●

●

○

OK: Confirm new Layer

○

Forget: Cancel new Layer and don’t introduce it.

Modify: For modifying a particular layer definition, it will be enough to select it and press with double-click on the layer definition and press on Modify Button with the LB. As a result, the edit field will be displayed to allow the modification. ○

OK: Confirm new layer definition

○

Forget: Cancel new layer definition and don’t introduce it.

Copy: For copying a particular new point, select the previous layer definition with the LB, then insert the new one and press on Insert Button with the LB. ○


OK: Confirm new Layer


Page 3-11


○

List of Fields:


Forget: Cancel new Layer and don’t introduce it.

●

Delete: For deleting an existing layer definition, select it with the LB and press on Delete Button with the LB.

●

GROUP NAME: Aircraft Group Identifier.

●

MAXIMUM ALTITUDE: Relative to operative altitude. For the Aircraft Group. (Hf)

●

MINIMUM SPEED: For the Aircraft Group. (Knots)

●

CRUISE SPEED: For the Aircraft Group. (Knots)

●

MAXIMUM SPEED: For the Aircraft Group. (Knots)

●

WAKE TURBULENCE: Wake turbulence produced for the Aircraft Group. Three levels of turbulence (Low, Medium and High).

●

LAYERS DEFINITION: These layers describe the behaviour of one of the aircrafts belonging to a particular group. Layers, which are defined using altitudes, describe this behaviour. ○

Upper Altitude: Maximum altitude concerning each layer. (Hf)

○

Climb Speed: Concerning a particular layer. (Knots)

○

Descent Speed: Concerning a particular group and for a specific layer. (Knots)

○

Climb Rate: Concerning a particular group and for a specific layer (ROC) Rate of climb (ft/min).

○

Descent Rate: Concerning a particular group and for a specific layer (ROD) ft/minutes

3.1.1.6 Aircraft Types Description:

This table contains the existent aircraft type identifiers and the group to which it belongs. The group to which it belongs must be previously defined using the Aircraft Groups Table.

Location:

FDP Adaptation Data. -> Database manipulation. -> Aircraft Types

Capacity:


This table accepts up to one thousand and five hundred (1.500) elements.


Page 3-12



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

AIRCRAFT TYPE: Aircraft Identifier

●

AIRCRAFT GROUP: Group Identifier

Data window:




Page 3-13



3.1.1.7 Wind Zones Description:

This table contains all the necessary information for the creation of Wind Zones. These Wind Zones will be used to compute the passing time related to fixed points.

Location:

FDP Adaptation Data. -> Database manipulation. -> Wind Zones

Capacity:

This table accepts up to eight (8) elements and up to four (4) points per Wind Zone.

Main Window:

Buttons:


●


●


●


●


●


●



Page 3-14



Data window:

Buttons:

●


●


●

Append: To add a new point, press the “Append” button. As a result, an edition window is displayed to allow the addition of the new point.

●

Modify: To carry out the operation of modifying, double-click with the LB on the point to be modified. As a result, this point will appear on the edition window. Once the modification has been done, press the "OK” button.

●

Insert: To carry out the operation of inserting, select the previous point, executing double click with the LB, and insert the new point on the edition window. Finally, press the “OK” button.

●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This point will appear on the edition window and just pressing the "OK" button will execute this action.

Rules:

Inside the working area is possible define maximum 8 wind zones.

List of Fields:

Are not possible overlapping between the deferent’s zones. ● Designator: Wind Zone Identifier. ●


Wind Zones Contour Points: Geodesic Coordinates concerning each point defining the limits (Contour) of the Wind Zone.


Page 3-15



3.1.1.8 Working Area Description:

This table contains all the necessary information for the creation of the horizontal and vertical limits of the Airspace. Likewise, it incorporates the Earth radius data to carry out later projections on a flat surface.

Location:

FDP Adaptation Data. -> Database manipulation. -> Working Area

Capacity:

This table accepts up to one (1) element.

Main Window:

Buttons:

List Fields:

of

●


●

Save: Store all data into database.

●


●

Tangency Point: Geodesic coordinates corresponding to the contact point between the conformal sphere and the stereographic projection tangent plane.

●

Tileset Origin: Geodesic coordinates corresponding to the origin of the “mosaic”. This “mosaic” will be used by the system to determine the sector where the flight is. It is useful too for detecting possible overlapping and uncovered areas. ○

Remark: “Mosaic” means the grid constituted by 4x4 nautical miles squares.

●

Earth Conformal Radius: Required Earth Conformal Radius for the stereographical projections.

●

Coordinates Origin: Necessary Geodesic coordinates to define an origin in the plane where all significant points of the system will be projected.

●

Latitude Dimension: Size of the working zone expressed in nautical miles. A South-North direction, starting in the Coordinates Origin explained above, is used.

●

Longitude Dimension: Size of the working zone expressed in nautical miles. A West-East direction, starting in the Coordinates Origin explained above, is used.

●

Ceiling Altitude: Maximum working value in hundred of feet.



Page 3-16


●


Magnetic Variation: Variation angle in degrees between the magnetic and geographic North.

3.1.1.9 Airports Description:

This table contains all the necessary information to define an airport (geodesic location, elevation) and the default ways in and out.

Location:

FDP Adaptation Data. -> Database manipulation. -> Airports

Capacity:

This table accepts up to two hundred (200) elements.

Main Window:

Buttons:


●


●


●


●


●


●



Page 3-17



Data window:



●


●


●

Airport Id: ICAO Airport identifier.

●

Associated Profiles: Flag that indicates if this airport has associate profiles for MSA areas. These profiles are defined in the Profiles Table of the SDP.

●

EFS: Electronic Flight Strip in the airport.

●

Location: Airport Geodesic location.

●

FIR Situation: Relative location of the airport regarding the defined sectorization. That is, if the airport is "Internal" it means that it is located within a sector defined as internal and if the airport is "External" it means that it is located within an external sector.

●

Altitude Level: Airport Altitude in feet.

●

Runways: Runways belonging to the airport.

●

Departure: Default Take-Off runway.

●

Arrival: Default landing runway.

●

Remark: This departure and arrival default runways are used by the system for the SID&STAR procedures. When the controller makes a flight plan, with one origin airport and other destination airport the system look for one departure procedure that belongs to the


Page 3-18



departure airport and the default departure runway and the same situation for the destination airport.

3.1.1.10

Approach routes

Description:

This table contains all the necessary information for the definition of the exit (SID) and arrival (Star) procedures from/to an airport. These procedures will be used later on by the system for the definition of the routes.

Location:

FDP Adaptation Data. -> Database manipulation. -> Approach routes

Capacity:

This table admits up to five hundred (500) elements, half of it for each type, it is 300 for exit (SID) and the other 300 for arrival (STAR). This table admits up to six (6) points per procedure

Main Window:

Buttons:


●


●


●


●


●


●



Page 3-19


Data window:


The next window is used to add new an modify SID or STAR procedure.

Buttons:

List of Fields:

●


●


●


●

Modify: To carry out the operation of modifying, double-click with the LB on the point to be modified. As a result, this point will appear on the edition window. Once carried out the modification, press the "OK” button.

●


●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This point will appear on the edition window and just pressing the "OK" button will execute this action.

●

Name: SID or STAR procedure identifier. It admits a maximum of seven characters.

●

Airport: Airport ICAO identifier for which the approach procedure is applicable.

●

Runway: Runway identifier for which the approach procedure is applicable.

●

Gatepoint: Connexion point between an airway and the approach procedure.

●


○

If the approach procedure corresponds to an arrival type (Star), this "gate point" will be the first point of the procedure and, at the same time, will also belong to the airway.

○

However, if the approach procedure corresponds to an exit type (Sid), this "gate point" will be the last point of the procedure and, as for the previous case, will also belong to the airway.

Kind : Flag that informs if the approach procedure is an arrival (Star) or an exit (Sid) type.


Page 3-20


●

3.1.1.11


Pathpoints: Sequence of sorted points forming the approach procedure. It is necessary that these points are also defined in the Fixpoints Kernel table. In a departure procedure the last Pathpoint must be the Gatepoint. In the opposite situation, in a standard arrival procedure, the first Pathpoint must be the Gatepoint.

Control Centers

Description:

This table contains all the necessary information to define a control centre, its classification, its AFTN address, as well as its OLDI communications with adjacent centres, for possible future coordination operations.

Location:

FDP Adaptation Data. -> Database manipulation. -> Control Cent

Capacity:

This table admits up to twenty (20) elements.

Main Window:

Buttons:


●


●


●


●


●


●



Page 3-21



Data window:

Buttons:


●


●



Page 3-22


List of Fields:


●

Name: Control Center Identifier.

●

Kind: It informs about the Control Center type (Foreign or Local).

●

Format: messages format (AFTN or ICAO)

●

AFTN Address: Control Center AFTN Address. It’s used to coordinate with a adjacent Control Center.

●

COMUNICATIONS:

●

●

○

CLASS: Flag that informs about the Control Center capacity to employ OLDI or AFTN communications.

○

FMTP OPTIONS (described below)

AIDC PARAMETERS: ○

AIDC Address: AIDC address from the Control Centre.

○

AIDC Type: Type of AIDC communication.

○

Retry: Number of attempts.

○

Dialogue mode: mode of dialogue (NONE, EST, CPL).

GENERIC COP: ○

AIDC Send Time: Time before the estimated coordination point fly over, the AIDC message is sent.

○

ETO DELTA: Minimum time before coordination point fly over for ABI message resend.

○

Init Time: Time before the estimated coordination point fly over, an EST or CPL message is sent.

○

Init Distance: Distance before the estimated coordination point fly over, an EST or CPL message is sent.

○

LAM Time: LAM (Logical Acknowledgement Message) message

timeout.

●


○

ACP Time: ACP (Acceptance) message timeout.

○

Renegotiation: Renegotiation waiting time.

○

Flight Level: Exit flight level for the coordination point.

OLDI PARAMETERS: ○

Behaviour: Parameter that’s defines the operative mode relative to the preference center in the OLDI connection.

○

Partners message format: message sent to a partner external center when another external center is co-ordinating a flight with us. Messages to sent to the partner center can be the original ones or INF messages with the data in the original message.

○

Local ATS Unit: Local address for the OLDI connection

○

Local ATS Phone Number: Local telephone number

○

Remote ATS Identifier: Partner Control Center Identifier. It refers to the centre with which communications are going to be established.


Page 3-23




○

Remote ATS Phone Number: Partner telephone number

○

Line Communication: Communication channel used to establish communications between the Control Center and the Adjacent Control Centre. (Attempting to the Communications Card port configuration)

●

PAC: Selection for the content of PAC messages between Estimated Take-Off Time or Estimated Data. It must be bilaterally agreed.

●

CONTROL CENTERS OPS


Page 3-24


List of Fields

AUTHORITY AND FORMAT IDENTIFIER (AFI): ● In case of Local kind:

●

3.1.1.11.1 Description:


○

Local Center Value: Local OLDI identifier number

○

Local Center Identifier: This field represents the ATC_ID value of the CALL_USER_DATA for our center. Used for the Call_Request Message in the OLDI dialog between centers.

○

Local Center Selector: This field represents the ATC_SELECT value of the CALL_USER_DATA for our center. Used for the Call_Request Message in the OLDI dialog between centers.

In case of Foreign kind: ○

Adjacent Center Value: Adjacent OLDI identifier number

○

Adjacent Center Identifier: This field represents the ATC_ID value of the CALL_USER_DATA for adjacent center. Used for the Call_Request Message in the OLDI dialog between centers.

○

Adjacent Center Selector: This field represents the ATC_SELECT value of the CALL_USER_DATA for adjacent center. Used for the Call_Request Message in the OLDI dialog between centers.

●

Time out expected Heartbeat: time to wait a expected Heartbeat message

●

Time out Sending Heartbeat: time to send a expected Heartbeat message

FMTP Options This window is acceded by clicking on “FMTP OPTIONS” in Control Centers Edit Window, and it configures the Flight Message Transfer Protocol (FMTP) parameters. FMTP is used in a peer-to-peer communications context, for the information exchanges between flight data processing system for the purpose of notification, co-ordination and transfer of flight between air traffic control units and for the purposes of civil-military co-ordination.

Location:

FDP Adaptation Data. -> Database manipulation. -> Control Centers-> FMTP Options

Capacity:

N/A



Page 3-25



Data window:


●


●




Center: Control Center ID.



Connection Type: o

X25: for X25 connection, the rest of the FMTP Option inputs won’t apply.

o

FMTP: FMTP connection requires the input of the following parameters: 


Role: 

TCP Client (Caller): server IP or hostname



TCP Server (Listener): ID of allowed client.



Port: port number to listen or send (depends if it is client or server)



NET. Interface: communication.



Remote Center (Hostname): Destiny Hostname for FMTP communication.



Local ID (FDP): Sender identificator



Remote ID (EXT): Destination identificator



Ti (s): Waiting reception.



Tr (s): Waiting time for message reception.



Ts (s): Waiting time for message sent.

Origin

time

net

for


card

for

identification

FMTP

message

Page 3-26



NOTE: Tr > Ts Timer_X parameters must be equals in Client center than in Server center. Host inputs must be previously defined in /etc/hosts or /etc/services


Control Center Options This window is acceded by clicking on “CONTROL CENTER OPS” in Control Centers Edit Window. This window sets the OLDI messages dialogue profile (from the predefined profiles included in the window, that also allows optional messages inclusion) Selected profile will apply in the coordination dialogue between the system center and the external control center.

Location:

FDP Adaptation Data. -> Database manipulation. -> Control Centers-> Control Center Options

Capacity:

N/A



Page 3-27



Data window:



●


●




Center: Control Center ID.



Dialogue Level: o

Basic No Dialogue: Basic message exchange without dialogue. Only ACT and LAM messages are exchanged. Optional messages that can be selected are: PAC, REV, MAC.

o

Extended No Dialogue: Extended message exchange without dialogue. ACT, LAM, COF and MAS messages are exchanged. Optional messages that can be selected are:


Page 3-28



PAC, REV, MAC.

3.1.1.12 Description:

o

Complete No Dialogue: Complete message exchange without dialogue. ACT, LAM, COF, MAS, TIM, SDM, HOP, ROF messages are exchanged. Optional messages that can be selected are: PAC, REV, MAC.

o

Basic Dialogue: Basic message dialogue. ACT, LAM, MAC, REV, RAP, RRV, CDN, SBY, ACP and RJC messages are exchanged. PAC message can be optionally selected.

o

Extended Dialogue: Extended message dialogue. ACT, LAM, MAC, REV, RAP, RRV, CDN, SBY, ACP, COF, MAS and RJC messages are exchanged. PAC message can be optionally selected.

o

Complete Dialogue: Complete message dialogue. ACT, LAM, MAC, REV, RAP, RRV, CDN, SBY, ACP, COF, MAS, TIM, SDM, HOP, ROF and RJC messages are exchanged. PAC message can be optionally selected.

Sectors To build the Sectors in the Database Management (DBM), we must do it in three steps: 1. BASIC SECTORS 2. SUBSECTORS 3. CONTROL SECTORS First we must make the basic sectors leaving a lower and upper altitude and the contour point, after this, in the second step, we must associate the new basic sector to a new subsector, It is possible to have several basic sectors belonging to the same subsector. The last step is to associate the new subsector to new Control Sector.

Location:

FDP Adaptation Data. -> Database manipulation. -> Sectors

Capacity:

N/A



Page 3-29



Main Window:

Buttons:

●


●

End: Exit from this table to the general screen.

●


Data window:

N/A

Buttons:

N/A

List of Fields:

N/A


Basic Sectors This is the main window of the Basic Sectors, in the first step of forming sectors. The Basic Sector is a basic volume. The creation of a subsector is performed by joining several basic volumes, taking into account that the subsector itself belongs to a sector. This table contains information about the basic elements concerning the creation of a specific sectorization. In this table we are going to define the contour, lower and upper altitudes of elementary volumes (Basic Sectors)

Location:

FDP Adaptation Data. -> Database manipulation. -> Sectors-> Basic Sectors

Capacity:

This table admits up to two hundred (200) elements and up to forty (40) points to define the contour of a basic volume.



Page 3-30



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●


●

Modify: To carry out the operation of modifying, double-click with the LB on the point to be modified. As a result, this point will appear on the edition window. Once carried out the modification, press the "OK”

Data window:

Buttons:



Page 3-31



button.

List of Fields:

Rules:

●


●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This point will appear on the edition window and just pressing the "OK" button will execute this action

●

Name: Basic volume Identifier. 4 Characters .

●

Lower Altitude: Basic volume lowers level.

●

Upper Altitude: Basic volume upper level.

●

Contour Points: Set of points defining the contour of the basic volume. Geodesic coordinates are used.

The sense of insertion of contour points must be same in all the basic sector, for example, if we have this basic sector:

We must maintain the same sequence for all the insertion. There is no need to repeat the last contour point with the first contour point since the DBM closes automatically the polygon. (In the example below the last contour point inserted must number 7, no need to insert number 1 again ). The lower altitude must be less than the Upper altitude. The maximum number of contour points by basic sector is 40. POSSIBLE MISTAKES In this part of the construction of sectors, it is possible to find several errors when we generate the adaptation. One of the most common errors is to have an overlapping or gap between two basic sectors, due to the fact that it exists two contour points shared for this two different basic sectors, the contours points belonging to two basic sectors must be the same.



Page 3-32



In this example there are two Basic Sectors : ●

B1formed by the contour points (1,2,3,4)

●

B2 formed by the contour points (1,2,3,4,5)

In this case due to the Basic Sector B1 not having contour point 5 , in the generation appears the overlapping or gap problem, because the boundary of this two basic sector is not the same.


Subsectors This is the second step of the sectorization, in this step we are going to assign the basic sectors to a subsector, this is used to join several basic sectors into the same subsector to obtain a complex volume. This table contains the necessary information for the definition of subsectors. To understand the existence of the subsector concept it is necessary to be able to sectorize complex volumes, because several previously-defined Basic Sectors can be associated to the same subsector. Later on, the subsector can be associated to a Control Sector. The existence of the subsectors is given by the necessity of building complex volumes.

Location:

FDP Adaptation Data. -> Database manipulation. -> Sectors -> Subsectors

Capacity:

This table accepts up to forty (40) elements and up to fifty (50) Basic Sectors per Subsector.



Page 3-33



Main Window:

Buttons:

●


●


●


●


●


●


●


●


Data window:


REMARK: Complement Name and Control Kind are not used in this system. ●


Identity name, Main name, Category and Properties are used to define the Multiple Use Airspace (MUA).


Page 3-34


Rules:


●

Basic Sector Assignment: Basic sectors with no assignation are located on the “UNSELECTED” column. To transfer one of them to the “SELECTED” column (it is, to assign a Basic Sector), choose it with the LB and press the "-->>" button.

●

The inverse process is also possible. To relocate a Basic Sector that is in the “SELECTED” column to the “UNSELECTED” one, select it with the LB and press the "<<--" button.

Imagine that we need to build one sector with this shape:

We need first split this complex volume in simple basic sectors , we call them S1 and S2, we build the basic sectors given the sequence of contour points and the lower an upper altitudes for each of them. See the picture: In this case we have two basic sectors ●

S1

●

( 1, 2, 3, 4, 5, 6, 7, 8 ) lower altitude 125 and upper altitude 240

●

S2

●

(A,B,C,D) lower altitude 0 and upper altitude 125

Our objective is to make one sub sector with this two elementary volume S1, S2, to do this we only need to go the subsectors table

After this we must select ¨Create¨ option then appears the creation screen, in the Basic sectors assignment appears on the left side the new basic sectors S1 and S2 Database Manager User Manual


Page 3-35



Then select with the mouse the basic sector S1 and press the button with the ¨->¨symbol to pass to the right side. With this operation we assign the Basic sector S1 to the sub sector, the same with the second basic sector s2. In the end, we will have one sub sector (SS) with two basic sectors.

3.1.1.12.3

Control Sectors

Description:

The third and last step is the Control Sector. This table contains all the necessary information for the definition of the Control Sectors. The last step for the creation of the sectorization is to assign the Subsector (made previously by joining Basic Sectors) to a Control Sector.

Location:

FDP Adaptation Data. -> Database manipulation. -> Sectors-> Control Sectors

Capacity:

This table admits up to forty (40) elements and up to one (1) subsector per Control Sector.

Main Window:

Buttons:


●


●


●


●



Page 3-36



●


●


●


●


●

Identity Name: Control Sector Identifier.

●

Identity Number: Key number of the Control Sector. It is mandatory to define first of all the internal Sectors with their serial identification numbers and, later on, the external sectors with their consecutive identification numbers. If it is necessary to insert a new internal sector then it will be necessary to increase in unit the identity of its number of the external sectors.

●

Identity groups: This entry is used to define the family of sectors. If you have two sectors with different families it is not possible to put them together in the same UCS by the CMD.

●

Sector type: This entry allows to select the type of the sector from OAT, VFR and GAT.

●

Kind: Flag that informs about the defined Sector Control type (Internal, External or Tower). If the Sector Control selected is a tower

Data window:




Page 3-37



then this sector contains any volume.

Rules:

●

Airport: Airport associated to a Control Sector. As a Control Sector can have no associated airport, this is not a mandatory field. ). Mandatory on the TWR kind).

●

Control Centre: Control Center associated to the Control Sector. The Control Center must be previously defined in the Control Centres table.

●

RVSM Coverage: This entry is used to activate RVSM capability for one specified sector (YES option). If the NO option is selected the RVSM capability is disabled.

●

DISABLE RAM: Allows deactivating the RAM Alert.

●

STCA IFR&IFR: The system process the STCA for IFR vs IFR (by default).

●

STCA IFR&IFR/ IFR&VFR: The system process the STCA between IFR vs IFR and IFR vs VFR.

●

FREQUENCY: Frequency associated to each sector assigned by the controller.

●

Subsectors Assignment :

●

This window allows the assignment of subsectors to the Control Sectors. On the left area (“UNSELECTED”) subsectors without assignment are displayed.

●

For the assignment of these subsectors, choose one of them with the LB and press the "-->>" button. As a result, the chosen sector will appear in the (“SELECTED”) area.

●

The opposite action is also possible, a subsector located in the (“SELECTED”) area can be chosen with the LB and sent to the ("UNSELECTED") area by pressing the "<<--" button.

●

Associated Sectors: When defining a MUA sector, this list of sectors represents the volume of the MUA sector.

The third and last step is the Control Sector, in this table we are going to assign our subsector (SS) to a new Control Sector, with the name SB for example. First we must go the Control Sectors Table, in this screen we select ¨Create¨ option. When we select this option it appears the creation screen



Page 3-38



In this screen we have on the left side the unselected subsectors and on the right side the sub sector belonging to the new Control Sector. We only need to select sub sector (SS) and assign with the button ¨>¨ to the right side. The identity number of the sectors must be sequential. First the internal sectors, after this all the tower sectors, and at the end, the external sectors. The control center must be the Local for internal control sectors and foreign for external control sectors. In TOWER Control Sector we must write the associated Airport and for this kind of control sector it does not exists volume associated then there is no need to select any subsectors.


Coordination Fix points This table contains all the necessary information to define the Coordination Fixpoints (Cops). The parameters defined here will associate a Fix to a Control Sector. Also, in order to activate Advanced Boundary Information, ABI, or Activation (ACT) messages, a set of time and distance parameters are defined.

Location:

FDP Adaptation Data. -> Database manipulation. -> Coordination Fix points

Capacity:

This table admits up to one hundred fifty (150) elements.



Page 3-39



Main Window:

Buttons:


●


●


●


●


●


●



Page 3-40



Data window:



●


●


●

Coor Fix: Fix ICAO identifier. It will be used as Coordination Fix. This Fixpoint must be defined in the Fixpoints table.

●

EST Time: Time, in seconds, before crossing the Coordination Fix at the moment when the EST message is sent automatically by the system.

●

REV MESSAGES: ○

Time Revision: the time in seconds of the variation of the original time to overflight the COP the system sends the REV message

○

Level Revision: the level of the variation of the original level to overflight the COP the system sends the REV message

○

Late Revision: Time, in seconds, before the estimated crossing the Coordination Fix for the last REV message; in the time segment from Late revision and estimated COP crossing time, no REV messages can be sent.

○

Transfer_Init: Time, in seconds, before crossing the Coordination Fix at the moment when the TIM message is sent automatically by the system.


Page 3-41


●


ABI MESSAGES: ○

ABI Time: Time, in seconds, before crossing the Coordination Fix at the moment when the Advanced Boundary message is sent automatically by the system.

○

Late Revision: Time, in seconds, before the estimated crossing the Coordination Fix for the last ABI message; in the time segment from Late revision and ACT time, no ABI messages can be sent.

●

LAM Time Cat 1 (sec): Time interval needed for the message reception reply (Logical Acknowledge Message), associated to OLDI cat 1 messages.

●


●


●

Ope Timeout (sec): Time interval needed for the message reply through the controller action (ACP, RJC, CDN messages).

●

ACT MESSAGES: ○

ACT Time: Time, in seconds, before crossing the Coordination Fix at the moment when an Activation message is sent.

○

ACT Display: Time when Advanced Boundary phase changes to Activation phase.

○

ACT Distance: Distance, in miles, when an Activation message is sent.

●

Flight Level: Exit flight level.

●

AIDC: ○

AIDC Send Time: Time before the estimated coordination point fly over, the AIDC message is sent.

○

ETO DELTA: Minimum time before coordination point fly over for ABI

message resend. ○

Init Time: Time before the estimated coordination point fly over, an

EST or CPL message is sent. ○

Init Distance: Distance before the estimated coordination point fly

over, an EST or CPL message is sent. ○

LAM Time: LAM (Logical Acknowledgement Message) message

timeout.

●

○

ACP Time: ACP (Acceptance) message timeout.

○

Renegotiation: Renegotiation waiting time.

CONTROL CENTERS ○


Control Center: Control Center associated to the Coordination Fix with the standard levels for the coordination.


Page 3-42


3.1.1.14


External Regions

Description:

This table contains the necessary information to define the external regions that are defined by means of an identifier and their distance to the FIR. This distance is used by the system to estimate the arrival time in the FIR.

Location:

FDP Adaptation Data. -> Database manipulation. -> External Regions

Capacity:

This table accepts up to five hundred (500) elements.

Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

Name: External Region Identifier.

Data window:

Buttons:

List of Fields:

○


Four different sets of characters:


Page 3-43



■

Four characters: It designates an airport.

■

Three characters: It designates a group of airports.

■

Two characters: It designates a country.

●

One character: It designates a group of countries.

●

Distance: Between the external region and the FIR. This data is used to estimate the arrival time in the FIR. The distance from the limit of our FIR to the external region.

REMARK: This table is used to estimate time of entry to over fix for an external flight. In this table there are defined the name and the distance and in the aircraft performance table we have the speed, so we know the estimated time to entry to over fix.

3.1.1.15

Routes

Description:

The user has to configure several options to define routes. These options are “Standard Routes” and “Point Pairs”. They will be explained in the following paragraphs.

Location:

FDP Adaptation Data. -> Database manipulation. -> Routes

Capacity:

N/A

Main Window:

Buttons:

Data window:

●


●

End: Come back to the previous menu.

●


N/A



Page 3-44


Buttons:

N/A

List of Fields:

N/A

RULES:

INTRODUCTION


The purpose of this text is to give a full explanation on the Standard Routes to use them later on in the FDP. To obtain the objective, we must insert information into several tables of the DBM. ●

GEOGRAPHIC REGIONS

●

STANDARD ROUTES

●

STANDARD ROUTES BETWEEN REGIONS

Afterwards, information can be inserted in “Points pairs” and “Entry points between regions” tables. First we will define the geographic regions, source region and target region, after this we will define one or several Standard routes, afterwards “Standard routes between regions” is completed. With this information we can put all together in the ¨ZONE PAIRS¨ table and can also be defined the gateways in “Entry points between regions”. This information is used when the controller fills the flight plan, when he puts the origin and destination, and anything about route, the system will give you a list of one or several Standard routes matching with the origin and destination, and the controller only needs to select one of them. At the same time this information is essential to process correctly all FPLs incoming from AFTN lines. GEOGRAPHIC REGIONS In this table we are going to define the original destination regions. If we write 4 letters it means one airport, three letters means several airports, two letters means one country and one letter one region. For example if we want to put all the flights that came from the mediterranean zone we only need to define one region called ¨L¨ .



Page 3-45



This is the main window for geographic regions, when we select ¨Create¨ option , it appears the following screen

It is possible to define several regions in the same pack, for example if we want to define one region for all the flights came from France, Spain and Germany, we define one region with these letters : *

LF LE ED

At this moment we have several regions, now the following step is to define the Standard routes between this geographic regions, we will do this through the Standard Routes Table. STANDARD ROUTES In this table we are going to build the Standard Routes, these Standard routes are only formed by fixpoints. The operator must check the continuity between pathpoints for each Standard route, it means that at least one airway is crossed by two consecutive points. The main screen for this table is the following:



Page 3-46



If the ¨Create¨ option is selected it appears the creation window :

On the left side it appears the fixpoints contained in the fixpoints table, and on the right side, it appears all the fixpoints that belongs to a specific Standard route. RULES : The operator must check the continuity between two consecutives fixpoints, that means that at least one airway is crossed by this two pathpoints. In the case of a Standard route being an overflight, the first fixpoint and the last fixpoint must be classified as External.



Page 3-47



In the case of the Standard route being an inbound flight (came from external region to an internal airport) the first fixpoint must be external, and the last fixpoint of the route must be also the first fixpoint of a Standard Arrival (STAR) for the destination airport, that will ensure its continuity. In the case of a Standard route being an outbound flight (starting in internal airport an going to an external region) the first fixpoint of the Standard route must be the last fixpoint of a Standard Instrumental Departure (SID) for the origin airport, and the last fixpoint it must be external. These rules are the same for the Points Pairs, but in this case the original destination regions are internal airports. At this moment we have two geographic regions defined in the geographic regions table, and one or several Standard routes defined between these two geographic regions, now it is the moment to join them together in one table for the system. STANDARD ROUTES BETWEEN REGIONS In this table we are going to join all the information defined before in the geographic regions and Standard routes. Its main screen is the following:

We must first define our origin and destination regions, after this we must define the gatepoints, the gate points are the external fixpoints before to enter in the FIR. And finally the DBM show you all the Standard routes, you must select least one.



Page 3-48




Standard Routes The Geographical Regions previously defined need to be connected through standard routes. This table contains the necessary information for the creation of these standard routes; a subsequent table is used to associate these standard routes to the geographical regions. These standard routes are achieved by using the Fixpoints defined in the Fixpoints table

Location:

FDP Adaptation Data. -> Database manipulation. -> Routes-> Standard Routes

Capacity:

This table accepts up to one thousand (1000) elements and up to twenty five (25) Fixpoints per Standard Route.



Page 3-49



Main Window:

Buttons:

●


●


●


●


●


●


Data window:



Page 3-50



3.1.1.15.2


●


●


●

Route Pathpoints: Set of sequential points that define the standard route.

●

To create these standard routes, first select, on the "FIXPOINTS" column, one of the points using the LB. Finally, press the "- ->>“ button and the selected point will be transferred to the “PAHTPOINTS” column.

●

The operator must be absolutely sure about the continuity between Fixpoints.

●

The opposite process is performed in a similar way. To remove a point from the “PAHTPOINTS” column, select it with the LB and press the "<<---" button.

Points Pairs

Description:

The Points Pairs table is used to relate the information contained in the Geographical Regions and the Standard Routes tables. This table is used to associate one or several standard routes to a couple of previously defined Geographical Regions. Additionally, the compulsory Gatepoints are also defined. Another way to use the Standard Routes is by linking a Pair of Points instead of a Pair of Zones. This table contains all the necessary information to link a standard route to a Pair of Points.

Location:

FDP Adaptation Data. -> Database manipulation. -> Routes-> Points Pairs

Capacity:

This table accepts: ●

Up to tree thousand (3000) Points Pairs

●

Up to two hundred (200) pairs of Geographical Regions.

●

Up to twenty (20) Standard Routes per pair of Geographical Regions.

●

Up to twenty-two (22) Gateways per pair of Geographical Regions.

Main Window:



Page 3-51


Buttons:


●


●


●


●


●


●


●


●


●

Initial: First Fix or airport on the route.

●

Final: Last Fix or airport on the route.

●

Start Fix / End Fix : When the "Start Fix" is filled-in, the Routes Window will display all routes containing this initial point.

Data window:


When the "Final Fix" is filled-in, the system will check the preceding routes and will remove those that does not contain this second point; in other words, the system will display the routes containing the Start Fix / and End Fixpoints.

3.1.1.16

Geographic Zones

Description:

Submenu used to perform the different regions and conditions for the routes. These options are “Geographic regions”, “Entrypoints between regions” and “Standard routes between regions”. They will be explained in the following paragraphs.

Location:

FDP Adaptation Data. -> Database manipulation. -> Geographic Zones

Capacity:

N/A



Page 3-52



Main Window:

Buttons:

●


●

End: Come back to the previous menu.

●


Data window:

N/A

Buttons:

N/A

List of Fields:

N/A

Rules:

See 3.1.1.15


Geographic Regions This chart contains the definition of the geographical regions. The geographical regions defined here will be connected through standard routes, which will be defined later on. These standard routes will be helpful in the definition of the route field of a flight plan in such a way that if the origin and destination airports are known and a standard route between them has been defined in the Adaptation, this standard route will be displayed to the operator at the SDD position for its possible use.

Location:

FDP Adaptation Data -> Database Manipulation -> Geographic Regions

Capacity:




Geographic Zones ->

Page 3-53



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

Zone: Identifier for each Geographical Region.

Data window:




Page 3-54


3.1.1.16.2


Entry points between regions

Description:

This chart contains the definition of the geographical regions. The geographical regions defined here are the different origin and destination zones to calculate the different ways of entry in the FIR.

Location:

FDP Adaptation Data. -> Database manipulation. -> Geographic Zones -> Entry points between regions

Capacity:

This Standard Routes table accepts ●

Pairs of zones up to 200 elements.

●

Fixpoints to entrance for each pair of zones up to 42 elements.

●


●


●


●


●


●


●


Main Window:

Buttons:

Data window:

Buttons: Database Manager User Manual


Page 3-55


List of Fields:


●


●

Append: To add a new point, press the “Append” button. As a result, an edition field is displayed to allow the addition of the new point.

●

Modify: To carry out the operation of modifying, double-click with the LB on the point to be modified. As a result, this point will appear on the edition field. Once carried out the modification, press the "OK” button.

●

Insert: To carry out the operation of inserting, select the previous point, double-click with the LB, and insert the new point on the edition field. Finally, press the “OK” button.

●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This point will appear on the edition field and just pressing the "OK" button will execute this action

●

Origin and destination Region: Alphanumeric Identifier for each origin and destination Region. To fill it click on the lower table.

●

Entry points between regions table will be used to define the different entry points for specified origin and destination region

New Window The difference between Modification window and create new Gate Points Data related to Window is that is necessary select the Origin and Destination Zones in the right Entry Routes: table. Obviously, the zones presented are zones not selected in other pairs of zones.

3.1.1.16.3

Standard routes between regions

Description:

This chart contains the definition of the standard routes between regions. This table shows how many routes are associated at the different origin and destination zones.

Location:

FDP Adaptation Data. -> Database manipulation. -> Geographic Zones -> Standard routes between regions

Capacity:

This Standard Routes table accepts up to 1000 elements.



Page 3-56



Main Window:

Buttons:

●


●


●


●


●


●


Data window:



Page 3-57




●


●


●

Origin and destination Zone: Alphanumeric Identifier for each origin and destination Regions.

●

Route Description: All routes defined in the Adaptation Data.

●

Direct and Reverse: Define the direction for the selected route. It is marked in the second column of Route Description.

●

Clear: Remove direction for the selected route. Of course, Clear option quit the selected Route for this Pair of Zones

New Window The difference between Modification window and create new Pair of Zones Data related to Window is that is necessary select the Origin and Destination Zones in the right Entry Routes: table. Obviously, the zones presented are zones not selected in other pairs of zones.


Pressure Zones This table contains all the necessary information to define the Pressure Zones, this pressure zones must be previously defined in “Meteo Messages Airports” table.

If the system receives a meteorological message and the Pressure Zone is defined in this table, automatically the QNH window, on the SDD, will be updated. In case of receive a GAMET message, the system needs that the sectors



Page 3-58



identifications of a GAMET FIR are defined. Is not needed define all sectors specified in the GAMET messages, only is necessary defined the interested sectors. All this information make a file “Config_info.adap” (see appendix) that is NECESSARY and MANDATORY to works correctly the FDPs servers and the rest of the system with the meteorological messages. Location:

FDP Adaptation Data. -> Database manipulation. -> Pressure Zones

Capacity:

This table accepts up to fifty (50) elements. Each Pressure zone accepts up to fifty (50) points.

Main Window:

Buttons:


●


●


●


●


●


●



Page 3-59



Data window:

Buttons:

Rules:

●


●


●

Append: To add a new point, press the “Append” button. As a result, an edition field is displayed to allow the addition of the new point.

●


●

Insert: To carry out the operation of inserting, select the previous point, executing double click with the LB, and insert the new point on the edition field. Finally, press the “OK” button.

●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This point will appear on the edition field and just pressing the "OK" button will execute this action

The next figure shows the general graphical description for the QNH, QFE and TL definitions:



Page 3-60


List of Fields:


●

All zones need to be defined with a minimal of 3 points and a maximum of 50 geodesic points. These zones are to be defined by a Transition Level (TL).

●

At the same time, this information will be processed by the FDP servers, the SDDs (to show at the controller the newest QNH values) and the SDP servers to process the Mode C.

●

When a track is inside a “Pressure Zone”, the system informs the controller with an “A” symbol in the Track label.

●

Identifier Name: Concerning the Pressure Zone (an Airport).

●

Transition Altitude: In which is changed from QNH to QFE.

●

QNH Zones Contour Points: Geodesic point coordinates that form the contour of the Pressure Zone around the airport.

●

MAP Colour displays the colour palette that allows to the user to define

the colour that shall appear on the Controller positions for each pressure zone.


User Passwords This table contains information about the system users as well as the access keys to the controller's positions (SDD) and the role and responsibility related to



Page 3-61



each one. Location:

FDP Adaptation Data. -> Database manipulation. -> User Passwords

Capacity:


Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

User: User identifier.

●

Password: User password.

●

Alias: User alias.

●

Roll: It informs about the kind of role assigned.

Data window:



○

Controller: Work at a UCS.

○

Assistant: Works at a Flow & AFTN position.

○

Technical Supervisor: Works as a technical supervision at a CMD.

○

Operative Supervisor: Works as a controller supervisor at a CMD.


Page 3-62


○

3.1.1.19


Technical Operative Supervisor: Works as a controller supervisor at a CMD.

Meteo Messages Airports

Description:

This table is necessary to define all airports that are expected to send meteorological messages to our Centre. At the same time they are used to define the GAMET zone. This table is needed for the FDPs Servers to process correctly all Meteorological messages. At the same time it is only possible to define one GAMET FIR zone in the system. If the controllers need the specified QNH values in the QNH window on the SDD, it is necessary to define these Aerodromes in the “Pressure Zones” table. All this information creates a file named “Config_info.adap” (see appendix) that is NECESSARY and MANDATORY so that the FDPs servers and the rest of the system work correctly with the meteorological messages.

Location:

FDP Adaptation Data. -> Database manipulation. -> Meteo Messages Airports

Capacity:

This table accepts up to sixty (60) elements.

Main Window:

Buttons:


●


●


●


●


●


●

Create: Make possible to create a new data in the table with a blank


Page 3-63



template. Data window:


3.1.1.20

●


●


●

NAME: Aerodrome name.

Destination Aerodromes

Description:

This table contains information about aerodromes with which AFTN communication is established.

Location:

FDP Adaptation Data. -> Database manipulation. -> Destination Aerodromes

Capacity:

This table accepts up to one thousand (1000) elements and up to fifteen (15) AFTN addresses per Aerodrome.

Main Window:

Buttons:


●


●


●


●



Page 3-64



●


●


●


●


●

Create: To add a new address, press the “Create” button. As a result, an edition field is displayed to allow the addition of the new address.

●


●

Copy: To carry out the operation of inserting, select the previous point, double-click with the LB, and insert the new address on the edition field. Finally, press the “OK” button.

●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This address will appear on the edition window and just pressing the "OK" button will execute this action

●

Name: ICAO Identifier concerning the airdrome to which the AFTN message is sent.

●

Addresses: AFTN address concerning the destination aerodrome.

Data window:

Buttons:

List of Fields:

3.1.1.21

SSR Codes

Description:

This table contains the necessary Transponder SSR codes for performing the necessary correlation between flight plans and radar data.

Location:

FDP Adaptation Data. -> Database manipulation. -> SSR Codes



Page 3-65


Capacity:


This table accepts up to thirty thousand (30.000) elements.  Destination Regions: up to five hundred (500) elements.   



Special Use Codes capacity: 24 non Assignable, 1 Domestic Basic, 1 Transit Basic and 1 Visual Basic Incoming Codes: 4096 codes for each Control Centres (20) Outgoing Assignable Codes: 4096 codes for each Control Centres (20) and per type of flight (subdomestic, domestic, superdomestic, transit, supertransit) Outgoing Retainable Codes: 4096 codes for each Control Centres (20) and per type of flight (subdomestic, domestic, superdomestic, transit, supertransit)

Main Window:

Buttons:

General Concepts:


●


●


●

Rename: N/A.

●

Copy: N/A.

●

Delete: N/A.

●

Create: N/A.

●

None-Assignable: Codes that cannot be assigned, for instance those reserved for "Communications Failure", "Hi-Jack", etc.

●

Domestic-Basic: Reserved code assigned when there are no more available codes for domestic flights. The system forces to define a single Domestic-Basic code.

●

Domestic-Assignable: Codes used for all flights where the destination is an internal airport.


Page 3-66



●

Domestic-Retainable: Codes reserved for incoming flights which destination is an internal airport, but their assignment has been performed by another controller. The system tries to retain the code.

●

SubDomestic-Assignable: Codes used for all flights where the destination aerodrome is one of another FIR in our country.

●

SubDomestic-Retainable: Codes reserved for incoming flights which destination airport is in another FIR in our country, but their assignment has been performed by another controller. The system tries to retain the code.

●

Superdomestic-Assignable: Codes used for all flights that arrive in an adjacent country but the distance is less than 60 NM.

●

Superdomestic-Retainable: Codes reserved for incoming flights which destination in an adjacent country with distance less than 60 NM, but their assignment has been performed by another controller (in another FIR).

●

Transit-Basic: Reserved code assigned when there are no more available codes for transit flights. The system forces to define a single Transit-Basic code.

●

Transit-Assignable: Codes used for all flights that’s the destination aerodrome is a country of Participating Area

●

Transit-Retainable: Codes reserved for incoming flights which destination aerodrome is a country from the Participating Area, but their assignment has been performed in another FIR.

●

SuperTransit-Assignable: Codes used for all flights which the destination aerodrome is out of the Participating Area.

●

SuperTransit-Retainable: Codes reserved for incoming flights which destination aerodrome is out of the Participating Area, but their assignment has been performed in another FIR.

●


●


●

OK: Inserts the introduced Region.

Destination Regions Window

Buttons:



Page 3-67


Functionality Special Codes


●

Forget: Cancels the action.

●

Delete: Deletes the previously selected Region.

This window will be used to define all kinds of Destination Regions, depending on the category of each flight.

Use

Buttons:

Functionality:

●


●


●

OK: Inserts the introduced Code.

●


●

Delete: Deletes the previously selected Range of codes.

This Table allows to define special use codes that cannot be assigned in further tables.



Page 3-68



Incoming Codes

Buttons

Functionality

●


●


●


●


●


This table will be used to define the range of codes for each control center situated in the left part of the image. These range of codes will be used to retain the code of an incoming flight.

Outgoing Assignable codes.

Buttons

Functionality

●


●


●


●


●


This window will be used for defining the range of codes that will be assignable depending on the category of the flight.



Page 3-69



Outgoing Retainable codes

Buttons

Functionality

Rules:

●


●


●


●


●


This table will be used to define the range of codes to retain the code of the flight depending on the category of the flight. The next picture shows the European Participating Areas: Code C1: Domestic code for PA Y (Local in STATE A - Local in STATE B) - these codes could be used in PA Z under the same condition of protection against the allocation in State B. Code C2: Subdomestic code for PA Y (Local in STATE A and STATE B) Code C3: Transit code for PA Y (STATE A) - in general such a code should be assigned to any aircraft originated in STATE A and leaving its boundaries, overflying STATE B or landing in B... - if C3 is planned for transit use from PA Y to PA Z it could be retained inside the whole PA Z. Code for Superdomestic flights: - in general this code may be changed at the entry in PA Z, but it could be retained for an arrival at an aerodrome close to the border and having a protection area of at least 60 NM against any other use in PA Z. Code C4: Supertransit code for PA Z (STATE C) - such a code will be assigned to any flight which code cannot be retained and overflies STATE C for a further destination in PA Z. Code C5: Transit code between STATE A FIR2 and STATE B FIR3



Page 3-70



- C5 should be simultaneously protected in the two FIRs though domestic for PA Y. Such an allocation has the advantage of avoiding assign a transit code for such short middle range flights. Code C6: Transit code for PA Y - the example given with C6 is a duplication where the directional assignment by STATE A gives a guarantee of no conflicts occurring with the following units. Code C7: Superransit code for use for PA Y (STATE A) and PA Z - C7 which is at least transit in PA Y and having no domestic use in PA Z will be retained in the two areas. REMARK: This information is referred from EUR REGIONAL NAVIGATION PLAN Supplement FASID

to

EUR

AIR ANP

ICAO

CAL Ed 2 May 2006

Illustrative diagram for general code allocation and assignment:



Page 3-71



Code C1: Domestic code for PA Y (Local in STATE A - Local in STATE B) - these codes could be used in PA Z under the same condition of protection against the allocation in State B. Code C2: Subdomestic code for PA Y Database Manager User Manual


Page 3-72



(Local in STATE A and STATE B) Code C3: Transit code for PA Y (STATE A) - in general such a code should be assigned to any aircraft originated in STATE A and leaving its boundaries, overflying STATE B or landing in B... - if C3 is planned for transit use from PA Y to PA Z it could be retained inside the whole PA Z. Code for Superdomestic flights: - in general this code may be changed at the entry in PA Z, but it could be retained for an arrival at an aerodrome close to the border and having a protection area of at least 60 NM against any other use in PA Z. Code C4: Supertransit code for PA Z (STATE C) - such a code will be assigned to any flight which code cannot be retained and overflies STATE C for a further destination in PA Z. Code C5: Transit code between STATE A FIR2 and STATE B FIR3 - C5 should be simultaneously protected in the two FIRs though domestic for PA Y. Such an allocation has the advantage of avoiding assign a transit code for such short middle range flights. Code C6: Transit code for PA Y - the example given with C6 is a duplication where the directional assignment by STATE A gives a guarantee of no conflicts occurring with the following units. Code C7: Superransit code for use for PA Y (STATE A) and PA Z - C7 which is at least transit in PA Y and having no domestic use in PA Z will be retained in the two areas. REMARK: This information is referred from EUR REGIONAL NAVIGATION PLAN Supplement FASID Data window:

EUR

ANP

ICAO

CAL Ed 2 May 2006

N/A

Buttons: List Fields:

to

AIR

of


●


●


●

Init Code: First Code to be introduced (octal format).

●

End Code: Last Code to be introduced (octal format)..

Route Conditions This table allows the definition of route conditions, that are established to



Page 3-73



automatically change the exit flight level of flights that fulfils them. Location:

FDP Adaptation Data -> Database Manipulation -> Route Conditions

Capacity:

This table accepts up to three hundred (300) elements.

Main Window:

Buttons:


●


●


●


●


●


●



Page 3-74



Data window:

●

Buttons:


●

List Fields:

Save: Save all data into table. Route Condition establish an exit level to flights that fulfils the defined conditions. of These conditions, defined in this window, can be one or some of the following ones: vertical restriction (defined by Minimum and Maximum RFL), flight departure/ arrival airport (some airports can be included in a restriction) and route restriction (up to last five points before COP and five points after the COP). When defined conditions match with a flight plan, its exit level is changed to “Crossing level” value. ●

Route Condition Name: Route Condition Identifier.

●

Minimum RFL: vertical low limit (only greater RFL values fulfil the condition)

●

Maximum RFL: vertical high limit (only lower RFL values fulfil the condition)

●

Crossing Level: level established when all the conditions are fulfilled.

●

AIRPORTS ORIGIN:

●


○

Buttons: CREATE, MODIFY, COPY and DELETE: to append, manage or delete airports in the Airports Origin list.

○

AIRPORT: Airport ID.

○

AIRPORT EDITION: Field to manage airports included in Airports Origin list.

○

Action Buttons: OK and Forget: to accept or cancel the action.

AIRPORTS DESTINATION: ○

Buttons: CREATE, MODIFY, COPY and DELETE: to append, manage or delete airports in the Airports Destination list.

○

AIRPORT: Airport ID.


Page 3-75


●

●



○

AIRPORT EDITION: Field to manage airports included in Airports Destination list.

○

Action Buttons: OK and Forget: to accept or cancel the action.

Coordination ○

Coordination Type: Field to select the type of coordination applied. It selects if flight is an exit from FIR flight (External) or an incoming to TMA flight (Internal)

○

Control sector: Only for Internal flights. It includes the control sector where the TMA is in.

Offset -X / … / COP / … / Offset X: fixpoints sequence condition, sequentially before and after the COP as is displayed in this window.

AMC This table includes the defined Conditional Direct Routes (CDR) and the Restricted Areas; and allow the creation, management and deletion of them. CDRs are defined to limit the traffic in a portion of an airway for a time period. This table also contains all the necessary information to define a restricted area, its form (circular or polygonal) and vertical limits. This Restricted Areas will be activated or deactivated and modified by AUP and UUP messages.

Location:

FDP Adaptation Data -> Database Manipulation -> AMC

Capacity:

Restricted Airspaces table accepts up to three hundred (300) elements. CDR table accepts up to a hundred and fifty (150) elements.

Main Window:

Buttons:

●




Page 3-76


●


END: Returns to previous screen

●

Report: Option to print the data from the visual window to a file or a predefined printer. RESTRICTED AIRSPACES Main Window

Buttons:

●


●


●


●


●


●




Page 3-77



Data window:

Buttons: List Fields:

of

●


●


●

Name: Restricted area identifier.

●

Matter Specifier: Free text about Restricted airspace information

●

Standing Purpose: Free text about the purpose of the restricted airspace.

●

Kind identifier: Free text about the kind identifier of the restricted airspace.

●

Lower Altitude: Minimum limit of height for the restricted airspace.

●

Upper Altitude: Maximum limit of height for the restricted airspace

●

Contour figure: ○

○

Circle: Restricted airspace with circular form ■

Circle Radius: Radius of circle.

■

Latitude: Latitude of the Radius of restricted airspace.

■

Longitude: Longitude of the Radius of restricted airspace.

Polygon: Restricted airspace with polygonal form ■

Latitude: Latitude of each point that forms the polygon.

■

Longitude: Longitude of each point that forms the polygon.

CONDITIONAL ROUTES



Page 3-78



Main Window:

Buttons:

●


●


●


●


●


●




Page 3-79



Data Window:

List Fields:

of

A CDR is defined to restrict the traffic in a piece of an airway. A CDR is a rectangular area defined by the start and end points of an airway, and the high and low levels. Inside this area, the traffic is restricted, and this restriction can be performed for a scheduled time, or can be defined as permanent. ● CDR NAME: CDR Identifier. ●

CDR LOW: CDR vertical low limit (below it, the restriction won’t apply)

●

CDR HIGH: CDR vertical high level limit (above it, the restriction won’t apply)

●

AREA CLASSIFICATION: type of area by restriction applied type:

●

○

Active: the CDR is active until it is inhibited.

○

Inactive: the CDR is defined, but inactive until it is activated.

○

Scheduled: the CDR is only active when the defined restrictions are fulfilled. Up to three schedules can be defined for each CDR.

SCHEDULE X: ○

START TIME: time when the restriction starts.

○

END TIME: time when the restriction ends.

○

WEEKLY ACTIVITY X: days when the restriction applies.

○

STATE: schedule status (enabled or disabled) in CDR.

○

LOW: CDR low level (below it, the restriction won’t apply). This value must

be higher than the CDR LOW value. ○

HIGH: CDR high level (above it, the restriction won’t apply). This value

must be lower than the CDR HIGH value.



Page 3-80


○


CATEGORY:

■

Category 1 – routes permanently available for flight planning. These routes are published in the relevant Aeronautical Information.

■

Category 2 – routes not permanently available for flight planning. The availability of these routes is decided on a shorter time scale, and therefore they cannot be filed in repetitive flight plans.

■

Category 3 – routes not available for flight planning. These routes are published in AIP (as Cat 1 or 2) but cannot be filed in flight plans. They are only available by controller clearance for a specific flight. In case an operator (controller or FDA) manually inserts an unavailable CDR or part thereof into a flight plan, a warning is returned to the entering position.

●

AIRWAY: Airway identifier where the CDR defined.

●

Start Point: fixpoint in the airway where the restriction starts.

●

End Point: fixpoint in the airway where the restriction ends.



Page 3-81


3.1.1.24


Aircraft Operators

Description:

This table sets description for each aircraft operator.

Location:

FDP Adaptation Data -> Database Manipulation -> Aircraft Operators

Capacity:

This table accepts up to 3000 elements.

Main Window:

Buttons:

●


●


●


●


●


●


●


●


 

ICAO-IATA: aircraft operator. Descriptor: aircraft operator descriptor.

Data window:


3.1.1.25

UCS Strip Printers

Description:

This table contains

Location:

FDP Adaptation Data. -> Database manipulation. -> UCS strip Printers

Capacity:


This table accepts up to two hundred (200) elements.


Page 3-82



Main Window:

Buttons:

 EXIT: Exit from this table to the previous screen.  Report: Option to print the data from the visual window to a file or a predefined printer.

 Rename: Change the name for the selected data.  Copy: Copy the selected data into the same table.  Delete: Erase the selected data from the table.  Create: Make possible to create a new data in the table with a blank template. Data window:

Buttons:


 EXIT: Exit from this table to the previous screen. Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page 3-83



 Save: Save all data into table. List of Fields:

 SDD: number of SDD identifier.  STRIP PRINTER PRIMARY: Primary strip printer identifier associated to the previous UCS.

 STRIP PRINTER SECONDARY: Secondary strip printer identifier associated to the previous UCS.

 TOWER: Toggle button to define if the printer is a tower printer.  AIRPORT: Airport associated to the tower.

3.1.2 Generation of FDP Adaptation Files. On the “FDP Options” window, select with the LB the "GENERATE DATA FILES" option. Once an environment has been created or modified in the Database, this option allows loading into the system.

Press the Start button to start the generation process. At the end of the process, a message will inform about the successful completion of the process or about possible mistakes. The exit button closes the window. If the process has been completed successfully, all the adaptation data will be located in the following directory: /… /adap/exec/exec/tcl_tk/databases/current_database/adap_files



Page 3-84



3.1.3 SDD maps generation. On the “FDP Options” window, select with the LB the "GENERATE MAP FILES" option. Once an environment has been created or modified in the Database, this option allows loading into the system.

Press the Start button to start the generation process. At the end of the process, a message will inform on the Generation window about the successful completion of the process or about possible mistakes. The exit button closes the window. If the process has been completed successfully, all the new maps will be located in the following directory: ./exec/tcl_tk/databases/current_database/map _files



Page 3-85



3.2 SDP Adaptation Data The " SDP Options" Screen appears when the "SDP ADAPTATION DATA" option is selected by means of double click of the LB. There are two options: ●

Data Base Manipulation

●

Generate Data Files



Page 3-86





Page 3-87



3.2.1 Database Manipulation When the "DATA BASE MANIPULATION" option is selected by means of double click of the LB, the " SDP Adaptation Table" window appears and shows all the necessary adaptation tables concerning the SDP (Radar Data Processing). This section w ill show how to rename, modify and remove an Adaptation SDP table. All actions described here are totally applicable to all Adaptation Tables.

The following figure shows the “SDP Adaptation Table” window with all its tables:

3.2.1.1 Radar Internal Config Description:

This table contains necessary information for RDCU specific tasks as radar messages recording on tapes (if available), radar messages coalescence and delay calculation enabling.

Location:

SDP Adaptation Data -> Database Manipulation -> Radar Internal Config



Page 3-88


Capacity:

This table accepts up to two (2) elements.

Main Window:

N/A

Buttons:

N/A


Data window:


●


●


●

RDCUx: RDCU Identifier.

●

DELAY USE: If we want to calculate the DELAY or not. If "YES" is selected, delay will be calculated for the radars with delay calculation enabled.

●

MAX BLANC: Maximum number of blanks allowed for a given package. Received radar frames will be merged together in a single package for the internal system LAN when it is reached the "MAX BLANC" radar frames number.

●

PACKING TIME: Maximum permitted time between packages. The radar frames received in this time lapse will be merged together in a single package for the internal system LAN.

REMMARK: A package is delivered to the internal system LAN when "MAX BLANC" or "PACKING TIME" conditions are met.

3.2.1.2 Radar External Protocol (RDCU 3) Description:

This window will define the external remote centres where send all radar information published in the internal system LAN.

Location:

SDP Adaptation Data -> Database Manipulation -> Radar External Protocol

Capacity:

This table accepts up to one (20) element.



Page 3-89



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

Shared SAC: Source Area Code (country identifier number) that RDCU will be identified with.

●

Shared SIC: Source Identifier Code (radar identification number) that

Data window:




Page 3-90



RDCU will be identified with. ●

External Center: Center name. For multicast send operation, it is required the port for UDP communication, the IP for multicast proposes and the IP address for RDCU. ● UDP Protocol Port: port (number) for UDP communication. ●

IP Multicast: IP address for multicast communication.

●

IP Interface: RDCU3 IP address.

3.2.1.3 Radars Descriptio n:

This table contains all the necessary information for the definition of the radars connected to the system. Refer to administration manual to declare a LAN connected radar in addition to the next information.

Location:

SDP Adaptation Data -> Database Manipulation -> Radars

Capacity:

This table accepts up to thirty five (35) elements.

Main Window:

Buttons:

●


●


●


●


●


●

Create: Make possible to create a new data in the table with a blank template and fill all the mandatory fields.



Page 3-91



Data window:

Buttons:

●


●




Page 3-92


List Fields:

of


●

LAN CONFIG RDCUX: Displays LAN Configuration Edit Window for RDCUX.

●

NAME (mandatory): Radar Identifier.

●

ORDER NUMBER(mandatory): number identification must be the same that alphabetical order. 1 character. Necessary manual input.

●

SAC(mandatory): Source Area Code (country identifier number).

●

SIC(mandatory): Source Identifier Code (radar identification number).

●

LOCATION(mandatory): a) Latitude / Longitude: Geodesic coordinates corresponding to the radar. b) Altitude: Radar altitude in feet. c) Correct Angle: Correction angle between magnetic and geographical north.

●

SILENT CONE (mandatory): a) Angle: This angle defines the silence radar cone. b) Height: Height of the silence radar cone.

●

TRANSPONDER(optional): used to calibrate the radar. a) SSR Code: transponder code. b) Latitude/Longitude: Geodesic coordinates of the transponder situation.

●

CHARACTERISTICS(mandatory): a) Scan Time: Scan period of the radar antenna, in seconds. b) Minimum Range: Referred to the radar, in nautical miles. c) Maximum Range: Referred to the radar, in nautical miles. d) Data Packet Format: Referred to the transmitted information.

●

DATA PACKET FORMAT(mandatory): Data format of the selected radar. a) ASTERIX ALENIA b) ASTERIX INDRA c) CD2 d) CDAMS. e) AIRCAT f) CCA_AR5

●

RADAR CHANNELS CONFIGURATION(mandatory): Port and RDCU number where each radar channel will be connected. If it is set "0" as the port number, the radar data reception will be done by LAN.

●

FILTER OPTIONS(mandatory): Radar messages filtering options. a) Delay calculation Select this toggle to calculate the delay from the RDCU message reception until the internal LAN message relay. The radar delay calculation will be carried out only if the "DELAY" radar internal config parameter is set to "ON". b) SIC SAC use When this toggle is selected, messages received from sources with SIC or SAC different from the configured ones will be discarded. c) PLOT Treatment When this toggle is selected, received plots will be processed.



Page 3-93



d) TRACK Treatment when this toggle is selected, received track will be processed. ●

NOISE TOLERANCE INFORMATION (mandatory): a) Range, Azimuth: Parameters used to define the noise in the radar line. b) Max Plot Retard: Maximum radar delay.

●

OTHER INFORMATION(mandatory): a) Test target SSR Code: test transponder code. b) Max Plot retard: The radar has a sector division for each rotation. If the transponder plot were detected in one sector and, in the next rotation, the radar detected the same plot in another sector, the system will compute the difference between the last rotation and the current rotation. If this computing is higher that the number indicated in this field, the plot will be discarded. c) Display: These fields indicate if the radar works in monoradar mode. The system allows 3 radars maximum to work in monoradar mode at the same time. ■

0 -> No monoradar.

■

1 -> This radar works either in monoradar mode or multiradar mode.

■

Of course, all radar work in By-pass mode.

●

SIMULATION: a) Primary Indicator: It informs about the existence of a primary radar. b) Secondary Indicator: It informs about the existence of a secondary radar. c) Weather Indicator: It indicates if the radar supplies meteorological information. d) Tracker Indicator: It indicates if the radar supplies tracking information. e) Primary Max Range: Referred to the primary radar. f) Secondary Max Range: Referred to the secondary radar. g) High Cut-off Angle: Maximum echo angle produced by the radar. h) Low Cut-off Angle: Minimum echo angle produced by the radar.

●

RHO-Theta Zones:

●

Zones which are applicable the plots filtering, Defined in the following order: a) Rho max: nautical miles. b) Rho min: nautical miles. c) Theta max: degree. d) Theta min: degree.

●


●


LAN Configurat ion Edit Window Data window: Buttons:



Page 3-94


List Fields:

of


●

RADAR (not available): Radar Identifier.

●

IP MULTICAST X (mandatory): IP multicast address the radar will use to send data to the LAN.

●

IP INTERFACE X (mandatory): IP address the RDCU will use to receive radar data.

●

Device Name X (mandatory): Identifier of the device of the RDCU used for radar data reception.

●

Port Number X (mandatory): Port number for defined device.

3.2.1.4 Directional Finders Description:

This table contains the necessary information to define Directional Finders. They are navigational helps used to identify communications with aircrafts.

Location:

SDP Adaptation Data -> Database Manipulation -> Finders

Capacity:

This table admits up to two hundred (200) elements

Main Window:

Buttons:


●


●


●


●


●


●

Create: Make possible to create a new data in the table with a blank


Page 3-95



template. Data window:


●


●


●

Identifier: Navigational help identifier.

●

Latitude / Longitude: Geodesic coordinates of the Directional Finder.

●

CHANNELS: Associated frequency to each channel.

3.2.1.5 MSAW Description:

This table contains the necessary information to state the MSA definition. Each area consists of a set of geodesic points describing the perimeter and a level that is determined because of ground obstacles. The areas defined here will guarantee the flight safety regarding the altitude and a MSAW alarm will be set off at the SDD position when the aircraft descends below this level.

Location:

SDP Adaptation Data -> Database Manipulation -> MSAW

Capacity:

This table admits up to hundred (100) minimum zones and up to twenty (20) elements points per each minimum zone.



Page 3-96



Main Window:

MSAW ZONES Main Window:

Buttons:


●


●


●


●


●


●



Page 3-97



Data window:

Buttons:

List of Fields:

●


●


●

Append: To add a new data, press the “Append” button. As a result, an edition field is displayed to allow the addition of the new point.

●

Modify: To carry out the operation of modifying, double-click with the LB on the point to be modified. As a result, this data will appear on the edition field. Once carried out the modification, press the "OK” button.

●

Insert: To carry out the operation of inserting, select the previous data, executing double click with the LB, and insert the new data on the edition field. Finally, press the “OK” button.

●

Delete: To carry out the operation of eliminating, double-click with the LB on the point to be eliminated. This data will appear on the edition field and just pressing the "OK" button will execute this action

●

Name: Minimum Zone identifier.

●

Altitude: Security Flight Level, in hundred of feet.

●

Minimum Zones Contour Points ○

●


Geodesic coordinates corresponding to the sequential points defining the perimeter of the area.

MAP Colour: displays the colour palette that allows to the user to define the colour that shall appear on the Controller positions for each pressure zone.


Page 3-98



MSAW PARAMETERS Data Window:

Buttons:

List of Fields:

●


●


●


●

Time to Prediction (sec): Value used to warn controllers that in ¨Time to prediction¨ time the alert will be set on.

3.2.1.6 STCA Parameters Description:

This table contains the necessary information to define the STCA parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> STCA Parameters

Capacity:

This table admits up to ninety nine (99) sectors

Main Window:

N/A

Buttons:

N/A



Page 3-99



Data Window:

Buttons:

Rules:

●


●


●


●

Append: To add a new data, press the “Append” button. As a result, an edition field is displayed to allow the addition of the new point.

●


●

Insert: To carry out the operation of inserting, select the previous data, double-click with the LB, and insert the new data in the edition field. Finally, press the “OK” button.

●


For the STCA parameters is necessary and mandatory to define ALL SECTORS with the corresponding horizontal separation. The next picture shows an example:



Page 3-100


List of Fields:



●

Minimum Altitude for STCA (Hf): This value represents the minimal value to start the STCA process.

●

Maximum Altitude for STCA (Hf): This value represents the maximal value to end the STCA process.

●

STCA Vertical Separation (min. to 290FL): This value represents the first layer to work with the specified STCA parameters.

●

STCA Vertical Separation (290 to 410FL): This value represents the second layer to work with the specified STCA parameters. For sectors without RVSM capability.

●

STCA Vertical Separation (410 to max. FL): This value represents the


Page 3-101



top layer to work with the specified STCA parameters. ●

STCA Vertical Separation (290 to 410FL): This layer works always with a RVSM parameter if the sector is defined with this performance.

●

Time to prediction: Value used to warn controllers that in ¨Time to prediction¨ time the alert will be set on.

STCA PARAMETERS EDITION: 2. SECTOR: The name of the sector where to apply the conditions. 3. DIST. (NM): The horizontal separation for the specified sector.

3.2.1.7 System Parameters Description:

This table contains information about The Temporary Parameters that affect to the correlation, de-correlation and transfer functions

Location:

SDP Adaptation Data -> Database Manipulation -> System Parameters

Capacity:

This table admits up to one (1) element.

Main Window:

N/A

Buttons:

N/A

Data Window:

Buttons:

List of Fields:


●


●


●


●

Decorrelated: Time to carry out a de-correlation of a flight plan.

●

Non-Correlated: Estimated time in which no correlation has taken place.

●

Lost: Estimated time in which a flight plan is lost.

●

Transference Temp: Time delay to perform a transfer between a


Page 3-102



Control Center and another Centre. ●

Alarm 8.33: This field means that every flight flying above this fly level without 8.33 flag in the navigation equipment will be alerted.

●

Heading Tolerance: Maximum deviation regarding to the airplane bearing.

3.2.1.8 SDD Parameters Description:

This table shows auxiliary parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> SDD Parameters

Capacity:


Main Window:

N/A

Buttons:

N/A

Data Window:

Buttons:

List of Fields:

●


●


●


●

FP Life Time: Time of life for the FPs. (hh:mm:ss)

●

Coast Life Time: Time to visualize the lost flight in the lost tabular. (hh:mm:ss).

●

Sound Level: Level of alert sounds for all SDDs.

3.2.1.9 Profile Parameters Description:

This chart contains the necessary global parameters for the definition of the Security Profiles. Security Profiles are defined as security air corridors. Inside one of these corridors an airplane flies in approach phase for a MSA. While the airplane does not leave these security corridors, the MSAW alarm will not be activated. Security air corridors or Security Profiles are defined as a volume.



Page 3-103



Location:

SDP Adaptation Data -> Database Manipulation -> Profile Parameters

Capacity:


Main Window:

N/A

Buttons:

N/A

Data Window:

Buttons:

List of Fields:

3.2.1.10

●


●


●


●

Heading Tolerance: Tolerance (deviation) in degrees concerning the “tunnel” at the header of the runway.

●

Altitude Tolerance: Altitude tolerance concerning the security corridor. This parameter applies to all Security Profile.

●

Distance Tolerance: Width tolerance at the header of the runway.

●

Airport Tolerance: A cylinder is defined in the surroundings of the airport and MSAW alarms are not going to be applied inside this cylinder. This parameter defines the radius of the cylinder.

Profiles

Description:

This table contains all the necessary data for the definition of the Security Profiles. These data are absolutely essential in order to associate the Security Profiles to a specific airport, at the same time it is necessary to activate the "Associated Profile" flag on the Airports Table.

Location:

SDP Adaptation Data -> Database Manipulation -> Profiles

Capacity:

This table admits:


●

Up to seventy (70) airports.

●

Up to six (6) runaways per airport.

●

Up to twenty five (25) points to define each Security Profiles.


Page 3-104



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

Append: To add a new data, press the “Append” button. As a result, an edition field is displayed to allow the addition of the new data.

Data window:

Buttons:



Page 3-105


List of Fields:

3.2.1.11


●


●


●


●

Name: Security Profile Identifier.

●

Airport: Airport associated to a Security Profile.

●

Runway: Runway belonging to the airport that has a Security Profile associated.

●

Runway altitude: Altitude for the runway

●

Runway location: Location of the runway.

●

Category: Different types of wake turbulence profiles.

●

Kind: Type of profile.

●

Parameters for profile design: ○

Name: Name of the profile.

○

Latitude and longitude: Geodesic position of all points used for building the profiles.

○

Half wide: It is the half wide for the corridor defined by the fixpoints sequence

SDD Printers

Description:

This table can be used to assign a laser printer to a SDD.

Location:

SDP Adaptation Data -> Database Manipulation -> Laser Printers

Capacity:

This table accepts up to twenty (200) elements.



Page 3-106



Main Window:

Buttons:

●


●


●


●


●


●


●


●


●

Name: Name of the printer

●

Ph Device: Physical name of the printer

●

CMD Display Number: Print identifier number. It is used as a unique identifier when naming the printer in the CMD graphical representation.

Data window:


The printer declared as CMD display number 0 is not monitored by the CMD, but it is selectable for printing in both, the CMD and SDD positions.


Filter Code Ranges These tables allows at the system to disable the different alerts (MSAW, STCA,



Page 3-107



APW) to de defined SSR codes Location:

SDP Adaptation Data -> Database Manipulation -> Filter Code Ranges

Capacity:

N/A

Main Window:

Buttons:

N/A

Data window:

Buttons:

List of Fields:


●


●


●


●

Alert Codes: MSAW, STCA and APW are the different alerts available for the SSR codes filtering.

●

INIT CODE: Initial code for filtering.

●

END CODE: Final code for filtering


Page 3-108


3.2.1.13


VSP

Description:

This table allows the modification of predefined values for system parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> VSP

Capacity:

N/A

Main Window:

Buttons:

List of Fields:

3.2.1.13.1

●


●


●


N/A

FDP Parameters

Description:

This table allows the modification of the FDP system parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> VSP -> FDP Parameters



Page 3-109


Capacity:


N/A

Main Window:

Buttons:

List of Fields:

●


●


●




Departure FP notification time: Time parameter before FIR Entry Time (HFIR) allowing a FP to pass from “passive” to “active” status. Flights in Active status have an assigned code and appear at appropriate time in the entry list sector. FP would appear in the Pending List of the first sector controlling the flight. Non active FP termination time: Time parameter allowing a FP to change from “active” or “passive” status to “terminated” status after estimated FIR exit time. It is not possible to modify or make other





Page 3-110



operations on Flights in terminated status, apart from viewing them. 

 

Active arrival FP termination time: (Only for not correlated FP) Time parameter allowing a FP to evolve from “live” to “terminated” status when the FP is a flight arriving at an internal airport but the system does not detect the flight arrival (after ETA).



Holding FP termination time: Time parameter after HOLD_TIME moment allowing a FP to evolve from “suspend” to “terminated” status. Controller may change FP status to “SUSPEND” if it is not entering when expected (delayed, or not entering the FIR or other reasons). If this action is not reverted by controller, the next state of the FP is “terminated” Terminated FP deletion time: Time parameter removing a “terminated” FP from the database. Once the FP is removed it is stored within historical. FP list removal time: Time parameter removing a FP from the FPs entry list once it has left the sector, after exit FIR time. If FP is terminated before, it disappears from the FPs entry list when it terminates. SFPL creation time from an RPL: Time parameter before FIR entry time to pass a Flight Plan from the RPL database to the FP database.





 

FP list presentation time: Time parameter forcing a FP the boundary between the two sectors, to be displayed in the Pending FPs entry list sector when it is coming from another internal sector.



Arrival tower no volume list present time: Time before the ETA that the flight plan has to be presented in the Tower List, when no volume is defined for Tower. When Tower has volume defined, FP List Presentation Time applies.



Departure tower no volume list deletion time: Time after the ATD that the flight plan has to be presented in the Tower List, when no volume is defined for Tower. When Tower has volume defined, FP List Presentation Time applies.



Next position report alert time: Time after expected overflown of a point by the flight to show alert PO in the label of an aircraft, when information (Position Report) has not been received. This parameter is active only and always that a POSITION REPORT action was carried out previously for a FP route point. Deviation time from strip reprint: Time before/ after ETO to strip reprint.




Active outbound termination time: (Only for not correlated FP)Time parameter allowing a FP to change from “live” to “terminated” status when the FP leaves the FIR (Outbound Flights). FPs are in live status when they are in the FIR, upon reception of AFTN EST/CPL messages or OLDI ACT message or the corresponding commands (EST, ACT, FP AFIL) from the controller workstations. Minimal FP termination time: Time of termination after creation of Minimal FP.


Page 3-111


     

3.2.1.13.2


Time before display CLD (pending): Time parameter before EOBT when the flight plan is presented in Tower CLD position. Enable Prewarning strips: Enable to print the prewarning strips. Enable Progression strips: Enable to print the progression strips. Enable Sector strips: Enable to print the sector strips. Pass RPL to FP: It actives/Inhibits the load of flight plans from RPL database to FP database. AFTN message status: It actives/ Inhibits each AFTN message type in the system.

AMHS Parameters

Description:

This table allows the modification of the AMHS system parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> VSP -> AMHS Parameters

Capacity:

N/A

Main Window:

Buttons:

●


●


●

Report: Option to print the data from the visual window to a file or a predefined printer. Delete after READ: Deletion of AMHS messages in the server after they were read. Delete after SEND: Deletion of AMHS messages in the server after they were sent. Erase SVC: Transmission of Service Messages.



List of Fields:

 

3.2.1.13.3

APW Parameters

Description:

This table allows the modification of the APW system parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> VSP -> APW Parameters

Capacity:

N/A

Main Window:



Page 3-112


Buttons:

●


●


●

Report: Option to print the data from the visual window to a file or a predefined printer. MIN. altitude: Flight level that defines the minimum altitude to carry out the APW function. It is, if the altitude value of the track is smaller than this particular value, the track is not going to be into account for the RAW function. MAX. altitude: Flight level that defines the maximum altitude to carry out the RAW function. So if the altitude value of the track is greater than this particular value, the track is not going to be into account for the RAW function. Alarm timeout: Remaining time, before violation of the special area, to activate the RAW alarm. APW status: status (actived, inhibited) for APW alarm.



List of Fields:



 

3.2.1.13.4


MTCD Parameters

Description:

This table allows the modification of the MTCD system parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> VSP -> MTCD Parameters

Capacity:

N/A

Main Window:

Buttons:

List of Fields:

●


●


●

Report: Option to print the data from the visual window to a file or a predefined printer. Level 1 (H1): Flight level that defines a horizontal division for the MTCD analysis. It defines the area between an altitude, equal or greater than the minimum altitude, and lower than H2. Level 2 (H2): Flight level that defines a horizontal division for the MTCD analysis. It defines the area between an altitude, equal or lower than the







Page 3-113














 

3.2.1.13.5


maximum altitude, and greater than H1. Standard vertical separation to H1: Minimum vertical separation between two allowed FPs, when they are in the area defined by minimum altitude (value defined in the parameters of the MTCD system) and H1, before considering the FPs in MTCD. Standard vertical separation H1 to H2: Minimum vertical separation between two allowed tracks, when they are in the area defined by H1 and H2, before considering the FPs in MTCD. Standard vertical separation from H2: Minimum vertical separation between two allowed tracks, when they are in the area defined by H2 and the maximum altitude (value defined in the parameters of the MTCD system), before considering the FPs in MTCD. RVSM standard vertical separation: Minimum vertical separation between two allowed FPs, when they are in the area defined by the altitudes of RVSM zone. Longitudinal separation (APP): Minimum horizontal (longitudinal) separation between two FPs (in APP area), before considering the tracks in MTCD. Longitudinal separation (ROUTE): Minimum horizontal (longitudinal) separation between two FPs (in route area), before considering the tracks in MTCD. Lateral separation: Minimum horizontal (lateral) separation between two FPs before considering the tracks in MTCD. MTCD Status: MTCD functionality ON/ OFF in the system.

SDP Parameters

Description:

This table allows the modification of the SDP system parameters.

Location:

SDP Adaptation Data -> Database Manipulation -> VSP -> SDP Parameters

Capacity:

N/A



Page 3-114



Main Window:

Buttons:

List of Fields:

●


●


●

Report: Option to print the data from the visual window to a file or a predefined printer. Weather cycle: Number of required radar rotations without receiving radar meteorological information that causes RDCU to send an order to SDD to delete weather map, as it is not updated. Scans change SSR to PSR track: Number of radar rotations to transit from a secondary track to a primary track. Scans change valid to invalid code: Number of radar rotations to confirm non-applicable modes. Cycles PSR initiation track required: Number of required radar rotations for creating a PSR track. Minimum speed initiation track required: It defines the minimum aircraft speed for the creation of a track so again, when the aircraft speed is lower than this parameter, no track is created. Maximum speed initiation track required: It defines the maximum aircraft speed for the creation of a track so, when the aircraft speed is greater than this parameter, no track is created.



   






Time PSR initiation track required: This parameter and the next one are only applicable when Auto PSR Track Initiation is deactivated, so PSR Track Initiation has to be carried out manually. A time window is defined a time before the activation time of the manual initiation (operator clicking) with this parameter. For all plots whose time is included in this time window and their position is inside the geographical window (see next parameter), the system will start their plot tracking.


Page 3-115








     






Distance PSR initiation track required: This value (distance), and the point (centre) selected by the operator when manual initiation of the PSR tracking is activated, defines a geographical window (a circle). Minimum altitude initiation SSR tracks: It defines the minimum altitude from which tracking starts so, when a plot altitude is lower than this parameter, the plot is not taken into account for the tracking function and, consequently, no track is created for this particular plot. Conformance altitude threshold: Maximum altitude deviation from the flight level (after being reached) allowed before activating the CLAM alert (Clear Level Adherence Monitoring). Discrepance distance: Separation of Discrepancy in miles. Present. Time of alarm by FOM decrem: Time of permanence of the alert by decreasing of Figure Of Merit. Manual creation PSR tracks: If this icon is selected, the manual creation of primary tracks is activated. Autocreation Synthetic tracks: If this icon is selected, the automatic creation of synthetic tracks is activated. Status Dynamic adjustment: If this icon is selected, the dynamic adjustment is enabled. STCA Status: Short Term Conflict Alert (STCA). When this function is activated data regarding every single plot is processed at the SDP position, and displayed at the SDD position, in order to verify the alert status. MSAW Status: It processes MSAW (Minimum Safe Altitude Warning) information. When this function is activated data regarding every single plot is processed in order to verify the alert status. CIN Status: Navigability Integrity Control (NIC). When CIN is selected, the parameters of SDP CIN are applicable for CIN alarms.

3.2.2 Generation of Adaptation SDP files The “Adaptation Generation” window is displayed when the “GENERATE DATA FILES” option is selected with the LB on the “SDP Options” window. This option is used both when an environment has been generated or when modifications have been carried out in the Database and these changes must be introduced in the system.



Page 3-116



To start the generation process, press the "Start" button. At the end of the process a message will inform on the generation window about the correct completion of the process or about possible mistakes produced. Finally, press “EXIT” to close this window. If the process has been accomplished correctly, all adaptation files will be placed in the following directory: ./exec/tcl_tk/databases/current_database/SDP_files



Page 3-117


3.3


ATG Adaptation Data

Select the “ATG ADAPTATION DATA” with the LB of the mouse, as a result the SIM Screen Options” window will be displayed. This window presents its Data Base Manipulation option.

3.3.1

Database manipulation

3.3.1.1 Holding Patterns Description:

This chart contains relevant information about the holdings that an aircraft must observe from a particular Fixpoint

Location:

SIM Adaptation Data -> Database Manipulation -> Holding Patterns

Capacity:

This table admits up to two hundred (200) elements.



Page 3-118


Description:


This chart contains relevant information about the holdings that an aircraft must observe from a particular Fixpoint

Main Window:

Buttons:

 EXIT: Exit from this table to the previous screen.  Report: Make report to print or in a file.  Rename: Change the name for the selected data.  Copy: Copy the selected data in the same table.  Delete: Erase the selected data from the table.  Create: Make possible create a new data in the table with a blank template.

Data window:

Buttons:

List of Fields:


 EXIT: Exit from this table to the previous screen. 




Holding Fixpoint: Point around which the holding is carried out.



Inbound Heading: Bound during the phase of moving to the fix.



Turn Direction: Sense of the holding.



Outbound Time: Lapse of time for the completion of every holding track. Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page 3-119


Description:


This chart contains relevant information about the holdings that an aircraft must observe from a particular Fixpoint 

Airport: Specific airport where the holding process is accomplished.



Runway: Specific runway where the holding process is accomplished.

Airport and Runaway are optional fields.



Page 3-120



3.3.1.2 Instrumental Landing Procedures Description:

This table contains information about the existing Instrumental Landing Systems (ILS) at a particular runway.

Location:

SIM Adaptation Data -> Database Manipulation -> Instrumental Landing Procedures

Capacity:

This table admits up to thirty two (32) elements.

Main Window:

Buttons:


Data window:

Buttons:

List of Fields:






Airport: Airport where the ILS is located.



Runway: Runaway where the ILS is located.



Glide Slope: Slope adopted by the aircraft for the case of an ideal Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page 3-121


Description:



This table contains information about the existing Instrumental Landing Systems (ILS) at a particular runway. trajectory. 

Outer Marker: Distance between the "Outer Marker" and the head of the runaway.



Elev. Angle: Elevation angle concerning the cone.



Horiz. Angle: Horizontal angle corresponding to the cone.



Capture Length: ILS capture angle.


Page 3-122



3.3.1.3 Inter Approach Speed Area Description:

When an aircraft comes into a specific volume it changes its speed and adopts the "inter approach speed (*)". This table contains information about this explicit volume. (*) In this System approach speed is defined in the aircraft performances table.

Location:

SIM Adaptation Data -> Database Manipulation -> Inter Approach Speed Area

Capacity:


Main Window:

N/A

Buttons:

N/A

Data window:

Buttons:

 EXIT: Exit from this table to the previous screen.  Report: Make report to print or in a file.

List of Fields:







Length: Length of this volume.



Height: Height of this volume.



Width: Width of this volume.



Angle: Angle of this volume.


Page 3-123



3.3.1.4 Aircraft Performances Description:

This table contains information about the different types of aircrafts. Due to the simulation process, more data are required here compared with those in the FDP area.

Location:

SIM Adaptation Data -> Database Manipulation -> Aircraft Performances

Capacity:

This table admits up to two hundred and fifty (250) elements and up to five (5) layers per Aircraft Performance.

Main Window:

Buttons:


Data window:



Page 3-124



Description:

This table contains information about the different types of aircrafts. Due to the simulation process, more data are required here compared with those in the FDP area.

Buttons:

 EXIT: Exit from this table to the previous screen.

List of Fields:






Create: To add a new data, press the “Create” button. As a result, an edition field is displayed to allow the addition of the new data.



Modify: To carry out the operation of modifying, execute double click with the LB on the point to be modified. As a result, this data will appear on the edition field. Once carried out the modification, press the "OK” button.



Copy: To carry out the operation of copying, select the previous data, executing double click with the LB, and insert the new data on the edition field. Finally, press the “OK” button.



Delete: To carry out the operation of eliminating, execute double click with the LB on the point to be eliminated. This data will appear on the edition field and just pressing the "OK" button will execute this action



Name: Identifier corresponding to the group of aircrafts.

STRUCTURE PERFORMANCES:




Kind: It indicates if the group is constituted with planes, helicopters with wheels or helicopters with skates.



Fuselage Length: Corresponding to the identified aircrafts group.



Wings Span: Span of the wings corresponding to the identified aircrafts Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page 3-125


Description:


This table contains information about the different types of aircrafts. Due to the simulation process, more data are required here compared with those in the FDP area. group. 

Landing Gear: It indicates if the landing gear is fix or retractable.



Nominal Height: Corresponding to the identified aircrafts group.



Wake Turbulence: It indicates if the wake turbulences are low, medium or heavy.

GROUND PERFORMANCES: 

Stand. Taxi Speed: Standard speed corresponding to the taxi phase.



Max. Taxi Speed: Maximum speed corresponding to the taxi phase.



Reverse Speed: Reverse Speed.



Touch Go Speed: "Touch and Go" speed.



Decision Speed: Decision Speed.



Stand. Taxi Accel: Standard acceleration corresponding to the taxi phase.



Stand. Taxi Decel: Standard deceleration corresponding to the taxi phase.



Emergency Decel: Emergency deceleration.



Takeoff Accel: Acceleration corresponding to the takeoff phase.



Landing Decel: Deceleration corresponding to the landing phase.



Minimum Turn Radius: Minimum turn radius corresponding to the identified aircrafts group.

GENERAL PERFORMANCES: 

Vertical Accel: Vertical acceleration.



ADS B Period: time period for ASTERIX Cat 21 sending.



Crossover: level that classifies the mode the aircraft is flying (IAS/ MACH). 

Below Crossover: IAS.



Above Crossover: MACH.

AIR OPERATION LIMITS:




Maximum Altitude: Maximum allowed altitude corresponding to the identified aircrafts group.



Minimum Speed: Minimum allowed speed corresponding to the identified aircrafts group.


Page 3-126


Description:


This table contains information about the different types of aircrafts. Due to the simulation process, more data are required here compared with those in the FDP area. 

Maximum Speed: Maximum allowed speed corresponding to the identified aircrafts group.



Max. Climb Rate: Maximum allowed climb rate corresponding to the identified aircrafts group.



Max. Desc. Rate: Maximum allowed descend rate corresponding to the identified aircrafts group.



Bank Angle: Inclination angle corresponding to the identified aircrafts group.

TAKEOFF APPROACH LANDING: 

Takeoff Speed: Takeoff speed corresponding to the identified aircrafts group.



Landing Speed: Landing speed corresponding to the identified aircrafts group.



Inter App. Speed: Speed relative to the "Inter approach" area and corresponding to the identified aircrafts group.



Final App. Speed: Final approach speed.

ILS DISTANCES: 

Outer Limitation: Maximum distance range corresponding to the ILS.



Final Point: ILS final point.

PITCH AND ROLL:




Takeoff Pitch: Inclination during the takeoff phase.



Landing Pitch: Inclination during the landing phase.



Climb Pitch: Inclination during the climb (ascent) phase.



Descent Pitch: Inclination during the descent phase.



Approach Pitch: Inclination during the approach phase.



Flapless Pitch: Inclination concerning flaps.



Pitching Rate: Inclination rate.



Rolling Rate: Rolling rate.


Page 3-127



3.3.1.5 Aircraft Subtypes Description:

This table contains a set of aircrafts to be associated to the aircrafts groups described above.

Location:

SIM Adaptation Data -> Database Manipulation -> Aircraft Subtypes

Capacity:

This table admits up to six hundred (600) elements.

Main Window:

Buttons:




Page 3-128


Description:


This table contains a set of aircrafts to be associated to the aircrafts groups described above.

Data window:

Buttons:

List of Fields:






Aircraft Subtype: Aircraft’s Name.



Aircraft Performance: Group of aircrafts to which the identified aircrafts belongs.


Page 3-129



3.3.1.6 Airports Runways Description:

This table contains information about the runways of the airports.

Location:

SIM Adaptation Data -> Database Manipulation -> Airports Runways

Capacity:

This table admits up to four hundred (400) elements.

Main Window:

Buttons:




Page 3-130


Description:


This table contains information about the runways of the airports.

Data window:

Buttons:

List of Fields:






Airport: Airport’s Name.



Runway: Name of the runaway belonging to the identified airport.



Latitude / Longitude: Geodesic coordinates concerning the identified runaway.



Altitude: Concerning the runaway.



Bearing: Angle between the runaway and the magnetic North.



Missed App. Range: Distance from the aircraft to the identified runaway to which the procedure of frustrated approach begins.



Missed App. Level: Level of the aircraft with regard to the identified runaway to which the frustrated approach procedure begins.



Miss Fix. 1 Name: Name of the first fix that makes up of the frustrated approach procedure.



Miss Fix. 1 Level: Mandatory Flight Level when the first fix that makes up of the frustrated approach procedure is reached.



Miss Fix 2 Name: Name of the second fix that makes up of the frustrated approach procedure.



Miss Fix 2 Level: Mandatory Flight Level when the second fix that makes up of the frustrated approach procedure is reached.


Page 3-131



3.3.1.7 Arrival Procedures Description:

This table contains information about the procedures used when arriving to a particular airport and runaway.

Location:

SIM Adaptation Data -> Database Manipulation -> Arrival Procedures

Capacity:

This table admits up to hundred (100) elements.

Main Window:

Buttons:




Page 3-132


Description:


This table contains information about the procedures used when arriving to a particular airport and runaway.

Data window:

Buttons:

List of Fields:

















Name: Procedure’s Name



Airport: Airport for which the procedure is applied.



Runway: Specific runaway for which the procedure is applied.



Arrival Pathway Points: Name and flight level when the aircraft reaches this point.

The first fixpoint of sequence of arrival pathway points must be belong to one airway at least



Page 3-133



3.3.1.8 Departure Procedures Description:

This table contains information related to Departure Procedures concerning a particular airport and runaway.

Location:

SIM Adaptation Data -> Database Manipulation -> Departure Procedures

Capacity:

This table admits up to two hundred (200) elements.

Main Window:

Buttons:




Page 3-134


Description:


This table contains information related to Departure Procedures concerning a particular airport and runaway.

Data window:

Buttons:

List of Fields:

















Name: Name of the departure procedure.



Airport: Airport for which the procedure is applied.



Runway: Specific runaway for which the procedure is applied.



Turning Parameters 1. Turning Direction: Initial turning direction regarding the departure procedure. It indicates the sense of direction. There are three options: right, left and economic. The last one is the sense of direction that allows to the aircraft to head its route in a minimum



Page 3-135


Description:


This table contains information related to Departure Procedures concerning a particular airport and runaway. time. 2. Turning Fixpoint: Fix where the initial turning manoeuvre takes place. 3. Distance Fixpoint: Radius of the sphere containing the fix. When the aircraft comes into this sphere it can start the turning process. 4. Turning Level: Required level condition to start the turning process. The turning process can start if this condition is observed by the aircraft before its introduction in the sphere around the fix. 

Departure Pathway Points: Name and radial corresponding to the set of points composing the identified departure procedure.

The last fixpoint of sequence of departure pathway points must be belong to one airway at least




When Fix is chosen, the airship will fly directly to the Fix one.



When Radial is chosen, the airship will perform this radial and, from it, will reach the Fix one.


Page 3-136



3.3.1.9 ADS VDL Description:

ADS-B Simulator stations definition.

Location:

SIM Adaptation Data -> Database Manipulation -> ADS VDL

Capacity:

This table admits up to ten (10) elements.

Main Window:

Buttons:




Page 3-137


Description:


ADS-B Simulator stations definition.

Data window:

Buttons:


List of Fields:


ADS VDL EDITION 

ID: Station name



Altitude: station altitude (in feet)



Min Coverage: minimum coverage (in kilometres)



Max Coverage: maximum coverage (in kilometres)

LOCATION




Latitude: station latitude coordinate



Longitude: station longitude coordinate



Bias Delay: time delay



Deviation Delay: noise delay



Prob Detection: detection probability

 

SIC: Source Area Code (country identifier number). SIC: Source Identifier Code (radar identification number).


Page 3-138



3.4 BADA Adaptation Data This window provides functionality to load predefined databases with aircraft types and their characteristics, defined by Eurocontrol. Loaded BADA data are charged in the following tables:  FDP Adaptation Data: Aircraft Groups and Aircraft Types;  ATG: Aircraft Performances and Aircraft Subtypes.

3.4.1 Generation of BADA Adaptation Files The displayed window by LB clicking in “GENERATE DATA FILES” option on “BADA Adaptation Data” window is used to import aircraft database from external files. This window includes an option to select the path where the Bada files are included through an explorer menu. This option is performed by LB click in “Choose a directory to Bada Files Path” button.



Page 3-139



To start the generation process, select Bada files to load, press the "Start" button. At the end of the process a message will inform on the generation window about the correct completion of the process or about possible mistakes produced. Finally, press “EXIT” to close this window.



Page 3-140



4 Graphic Tool 4.1 Draw adaptation Data The Draw Adaptation Data option is located on the main screen:

When the Draw Adaptation Data option is selected (see figure above), the Visual Data Interface window is displayed:



Page 4-1



This option allows visualizing Fixpoints, airports, airways, sectors, SID_STAR, COPS, STD, radars, wind zones, MSA, profiles, CDRs, QNH, restricted areas and MAP. The next points show examples of DRAW actions.

4.1.1 Fixpoints Select the Fixpoint icon to display the following window:



Page 4-2



4.1.2 Airports Select the Airports icon to display the following window that will present all the airports stored in the system:



Page 4-3



4.1.3 Airways Select the Airways icon to display the following window that will present all the airways introduced in the system:



Page 4-4



4.1.4 Sectors This option will display a group of sectors that will be selected by means of altitude filters:

Once the layer has been chosen, the system will present all the sectors matching with the selected filter.



Page 4-5



User can select one of these sectors laying the mouse on it and with the mouse buttons access to several actions:



Page 4-6



If user LB click the geodesic vertex are displayed (see the following figure).



Page 4-7



If RB is clicked, the vertex are deleted from the window and if CB is clicked on any sector the Basic sectors windows (from database) are displayed and the fields corresponding on the sectors can be modified.



Page 4-8



4.1.5 SID & STAR This option will present, in a new window, all the procedures SID-STAR of the airports included in the FIR. These procedures are the same ones than those stored in the database.



Page 4-9



4.1.6 Coordination points (COPS) This option will present, in a new window, all the Coordination points included in the FIR. These coordination points are the same ones than those stored in the database

4.1.7 Standard Routes (STD) This option will present, in a new window, all the Standard Routes included in the FIR. These standard routes are the same ones than those stored in database



Page 4-10



4.1.8 Radars By pressing the Radar icon the system will display a window that shows all the radars connected to the system:



Page 4-11



4.1.9 Wind Zones This option will present, in several windows, all the wind zones that have been stored in the Database.



Page 4-12



4.1.10 MSAW This option will present, in several windows, all the minimum altitude zones that have been inserted in the Database.



Page 4-13



4.1.11 Profiles This option will present, in several windows, all the profiles that have been inserted into the Database.



Page 4-14



4.1.12 CDRs This option will present, in several windows, all the CDRs that have been inserted into the Database.



Page 4-15



4.1.13 QNH This option will present, in several windows, all the QNH zones that have been inserted into the Database.



Page 4-16



4.1.14 Restricted Areas This option will present, in several windows, all the Restricted areas that have been inserted into the Database.



Page 4-17



4.1.15 MAP This option will present, in several windows, all the maps of the FIR that have been inserted in the Database.



Page 4-18





Page 4-19






Page 4-20



5 Data Distribution The DBM application shows the next options to load and generate all data.

  

MAP COLOURS GENERATE ALL DATA FILES LOAD ADAPTATION DATA



Page 5-1



5.1 Map Colours This option allows to the user to define the different colours for the different elements on the SDDs positions. The next figure shows the different options be able to be modified from the DBM:

When the user clicks on one of these options, the system displays a new window that gives the capability to perform the new colour:

OK: Save the data Cancel: Back to the previous window without saving data.



Page 5-2



5.2 Generate All Data Files On the “GENERATE ALL DATA FILES” window makes possible all data generation from all tables of the Database.

Press the Start button to start the generation process. At the end of the process, a message will inform about the successful completion of the process or about possible mistakes. The exit button closes the window.

5.3 Load Operational Generated Data The operation of loading Adaptation Data into the “Operational String” only needs to select the “OPERATIONAL” option in the “Load_adaptation” window, then the DBM will distribute adaptation data into the “Operational String”. In the DBM tool, select the option ¨LOAD ADAPTATION DATA”



Page 5-3



After this action appears the “LOAD ADAPTATION DATA” window:



Page 5-4



By selecting the LOAD ADAPTATION DATA with the LB in the Subsystems Screen, a Dialog Screen appears asking for a confirmation:

By pressing, “YES”, the loading data process starts and all the data will be loaded into the system. By pressing “NO”, the window is closed. And the system does not proceed.



Page 5-5



A Configuration files Config_info.adap # configuration file # #--------------------------------------------------# PARAMETER VALUE ADMITTED VALUES #--------------------------------------------------WARM_START : FALSE # FALSE, TRUE SVC_ADDRESS : UKDDADYF SENDER_SVC_ADDRESS : UKDVZRZB IN_CHANNEL_ID_1 : TIA IN_CHANNEL_ID_2 : TIB #### FIR name,AEROD 1, AEROD 2,...,AEROD 9 AIRPS_FOR_METEO : UKDV,UKCC,UKCM,UKCS,UKCW,UKDR,UKHS ############################################################ # IFPS ADDRESSES # Haren, Belgium IFPS_A_ADDRESS : UKDVZRZC # # Bretigny, France IFPS_B_ADDRESS : UKDVZRZD ############################################################



Page 5-6



Appendix A - Abbreviations Table A-1: Abbreviation

Abbreviations Definition

A AAI

FDD Message Queue

ABI

Advanced Boundary Information Message (OLDI)

A/C

Aircraft

ACC

Area/Airspace Control Centre

ACID

Aircraft Identification

ACK

Acknowledge(ment)

ACP

Accept message (OLDI)

ACT

Activation Message (OLDI)

A/D

Analog-To-Digital

ADA

Programming language

ADEP

Aerodrome of Departure

ADES

Aerodrome of Destination

ADEXP

ATS Data Exchange Protocol

ADS

Automatic Dependent Surveillance

AFIL

Aircraft Filed Flight Plan

AFTN

Aeronautical Fixed Telecommunications Network

A/G

Air/Ground, Air-To-Ground

AIC

Aeronautical Information Circular

AIDC

Air Traffic Services Interfacility Data Communications

AIP

Aeronautical Information Publication

AIRMET

Airman Meteorological Information

AIS

Aeronautical Information Service

ALT

Altitude/Alternate

AMC

Airspace Management Cell

ANS

Air Navigation Services

APP

Approach Centre

APW

Area Proximity Warning

ARR

Arrival Message

ARTAS

ATM Surveillance Tracker and Server

ASTERIX

All Purpose Structured Eurocontrol Radar Information Exchange

ATA

Actual Time of Arrival

ATC

Air Traffic Control

ATCAS

Air Traffic Control Automation System

ATCC

Air Traffic Control Centre

ATD

Actual Time of Departure

ATFM

Air Traffic Flow Management

ATIS

Airport Traffic Information System

ATM

Air Traffic Management



Page A-1


Abbreviation


Definition

ATS

Air Traffic Services

AUP

Airspace Usage Plan

AUX

Auxiliary

B BYP

By-Pass Mode of Operation

C CA

Conflict Alert (see STCA)

CAA

Civil Aviation Administration/Authority

CAD

Computer-Aided Design

CB

Mouse Central Button

CBA

Cross-Border Areas

CBT

Computer-Based Training

CCR

Communications Compressor Radar

CD

Compact Disk

CDR

Conditional Routes

CFL

Cleared Flight Level

CFMU

Central Flow Management Unit

CHG

Change Message

CIN

See NIC

CLAM

Cleared Level Adherence Monitoring Alert

CMD

Control and Monitoring Display

CNL

Cancellation Message

CNS

Communications, Navigation and Surveillance

COP

Coordination Point

COTS

Commercial Off-The-Shelf

CPL

Current Flight Plan

CSCI

Computer Software Configuration Item

CSSR

SSR Code

CTF

Common Timing Facility

CTOT

Calculated Take-off Time

CWP

Control Working Position

D DBM

Data Base Management

DCT

Direct Route Qualifier

DEP

Departure Message

DEP

Departure Aerodrome

DEST

Destination Aerodrome

DL

Data Link/Downlink

DLA

Delay

DRF

Data Recording Facility

E EET

Estimated Elapsed Time



Page A-2


Abbreviation


Definition

ENSI

Expected Sorted Number Input

ENSO

Expected Sorted Number Output

EOBD

Estimated Off-Block Date

EOBT

Estimated Off-Block Time

EST

Estimate

ETA

Estimated Time of Arrival

ETD

Estimated Time of Departure

ETO

Estimated Time Over a Fix

F FANS

Future Air Navigation Systems

FBS

Fallback System

FCON

Fixed Configuration

FDA

Flight Data Assistant

FDD

Flight Data Display

FDP

Flight Data Processing

FDPS

Flight Data Processing System

FIFO

First In, First Out

FIR

Flight Information Region

FIX

Fix Point

FL

Flight Level

FMU

Flow Management Unit

FP

Flight Plan

FPL

Flight Plan

FUA

Flexible Use of Airspace

G GAT

General Air Traffic

GByte

Gigabyte

GHz

Gigahertz

GPS

Global Positioning System

GRIB

Wind Meteorological Message

GUI

Graphical User Interface

H HCI

Human-Computer Interface

HDLC

High-Level Data Link Communication

HFS

Horizontal Future Situation

HMI

Human-Machine Interface

HOLD

Hold(Ing)

HWCI

Hardware Configuration Item

Hz

Hertz

I ICAO

International Civil Aviation Organization

IEEE

Institute of Electrical and Electronics Engineers



Page A-3


Abbreviation


Definition

IFPS

Integrated Initial Flight Plan Processing System

IFR

Instrument Flight Rules

ILS

Instrumental Landing System

INB

Inbound

INF

Information Message

INT

Integrated Mode of Operation

ISO

International Standards Organization

K Kb

Kilobytes

Kbits

Kilobits

Kbps

Kilobits per second

KBps

Kilobytes per second

KCAS

Knots Calibrated Airspeed

Kgls

Kinematics GPS Landing System

KHz

Kilohertz

KIAS

Knots Indicated Airspeed

Km

Kilometer

KPS

KB per second

Kt

Knots (NM/ hour)

KW

Kilowatts

L LAM

Logical Acknowledgement Message

LAN

Local Area Network

LAT

Latitude

LB

Mouse Left Button

LCD

Liquid Crystal Display

LMG

Local Maps Generation

LONG

Longitude

M M

Match/Meter

Mb

Millibars

Mbar

Milibar

MET

Meteorological Information

METEO

Meteorological

METAR

Meteorological Aviation Routine Weather Report

MHz

Megahertz

MM

Millimeters

MON

Monoradar Mode of Operation

ms

millisecond

MSAW

Minimum Safe Altitude Warning

MSB

Most Significant Bit

MSL

Minimum Sea Level



Page A-4


Abbreviation MTCD


Definition Medium-Term Conflict Detection

N NAV

Navigation

NE

Navigation Equipment

NIC

Navigation Integrity Control

NM

Nautical Miles

NOTAM

Notice To Airmen

O OAT

Operational Air Traffic

OLDI

On-Line Data Interchange

ORCAM

Originating Region Code Assignment Method

P PAC

Pre-activation Message

PCA

Prior Coordination Airspace

PLT

Pilot

POS

Position Report

PSR

Primary Surveillance Radar

PSR T

Primary Surveillance Radar Track

PTS

Panoramic Tower Simulator

Q Q

FDD Messages Queue

QFE

Atmospheric pressure at aerodrome elevation or at runway threshold

QNH

Altimeter sub-scale sitting to obtain elevation when on the ground

R RAD

Radar

RAM

Route Adherence Monitoring

RAW

Restricted Area Warning

RB

Mouse Right Button

RBL

Range Bearing Line

RCA

Reduced Coordination Airspace

RDCU

Radar Data Communication Processor

RDP

Radar Data Processing

RDPS

Radar Data Processing System

RETD

Revised Estimated Time of Departure

RFL

Requested Flight Level

RIE

Route Insertion Error

RISC

Reduced Instruction Set

RMCDE

Radar Message Conversion and Distribution Equipment

ROC

Rate of Climb

ROD

Rate of Decent

RPL

Repetitive Flight Plan

RVSM

Reduced Vertical Separation Minimum



Page A-5


Abbreviation RWY


Definition Runway

S SAM

Slot Allocation Message (CFMU Message)

SAR

Search and Rescue

SBY

Standby

SDD

Situation Data Display

SDP

Surveillance Data Processing

SFPL

System Flight Plan

SID

Standard Instrument Departure

SIGMET

Significant Meteorological Information

SIM

Simulator System

SMC

System Monitoring Computer

SPECI

Special Forecast

SPI

Special Position Identification

SQL

Structured Query Language

SSR

Secondary Surveillance Radar

SSS

Software System Specification

STAR

Standard Instrument Arrival Route

STCA

Short-Term Conflict Alert

ST-RAW

Short-Term Restricted Area Warning

T TACT

Tactical System

TAF

Terminal Area Forecast (ICAO)

TAIS

Total Aircraft Information System

TAS

True Airspeed

TCP

Transmission Control Protocol

TCP/IP

TCP/Internet Protocol

TMA

Terminal Maneuvering Area

TFL

Transfer Fly Level

TL

Transition Level

TOC

Top of Climb

TOD

Top of Descent

TRA

Temporary Reserved Area

TSA

Temporary Segregated Area

TSP

Technical Supervisor

TWR

Tower or Tower Control

U UAC

Upper Airspace Control Centre

UTC

Universal Time Coordinated

UUP

Updated Airspace Usage Plan

V VFS

Vertical Future Situation



Page A-6


Abbreviation


Definition

VFR

Visual Flight Rules

VSP

Variable System Parameter

W WAN

Wide Area Network

Wi-Fi

Wireless Fidelity

WWW

World Wide Web

X X.25

Standard Protocol In Telecommunications



Page A-7



This is the last page of this document



Page A-8

0029200000000MA02_2-0_DBM-UM

Recommend Documents