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 Torrejn 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
DOCUMENT N: 0029200000000MA02
Page iv
DOCUMENT N: 0029200000000MA02
PAGE EDITION AND REVISION RECORD
This document contains the following pages in the indicated editions and revisions PAGE All All EDITION 1 2 REVISION 0 0 PAGE EDITION REVISION PAGE EDITION REVISION
Page v
DOCUMENT N: 0029200000000MA02
Page vi
DOCUMENT N: 0029200000000MA02
REGISTER OF CHANGES TO THE DOCUMENT
EDITION 1 2
REVISION 0 0
DATE 2010-08-04 2010-11-04
AFFECTED PAGES All All First Edition Second Edition
REASON FOR CHANGE
Page vii
DOCUMENT N: 0029200000000MA02
Page viii
DOCUMENT N: 0029200000000MA02
Table of Contents
1 Introduction ........................................................................................................................... 1-1 1.1 1.2 Scope ............................................................................................................................. 1-1 Manipulation of tables from the Database ...................................................................... 1-2 Renaming an element from the Database. ............................................................ 1-3 Copying an element from the Database. ............................................................... 1-3 Deleting an element from the Database. ............................................................... 1-4 Creating an element from the Database. ............................................................... 1-4 Report concerning a table from the Database. ...................................................... 1-5
1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 2 2.1
Main Functionalities .............................................................................................................. 2-1 Main Screen actions ....................................................................................................... 2-2 Main Screen Exit (EXIT) ........................................................................................ 2-2 Backup (BACKUP) ................................................................................................ 2-2 Database Copy (COPY) ........................................................................................ 2-2 Data Removal (DESTROY) ................................................................................... 2-2 2.1.1 2.1.2 2.1.3 2.1.4 2.2
Database Selection (SELECT) ....................................................................................... 2-3 FDP Adaptation Data. .................................................................................................... 3-1
Edit Adaptation Data ............................................................................................................. 3-1 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 Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page ix
DOCUMENT N: 0029200000000MA02
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 3.1.3 3.2 Generation of FDP Adaptation Files. ................................................................... 3-84 SDD maps generation. ........................................................................................ 3-85
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 4 BADA Adaptation Data ............................................................................................... 3-139 Generation of BADA Adaptation Files ............................................................... 3-139 3.4.1
Graphic Tool ......................................................................................................................... 4-1
Page x
DOCUMENT N: 0029200000000MA02
4.1
Draw adaptation Data ..................................................................................................... 4-1 Fixpoints................................................................................................................ 4-2 Airports.................................................................................................................. 4-3 Airways ................................................................................................................. 4-4 Sectors .................................................................................................................. 4-5 SID & STAR .......................................................................................................... 4-9 Coordination points (COPS) ................................................................................ 4-10 Standard Routes (STD) ....................................................................................... 4-10 Radars ................................................................................................................ 4-11 Wind Zones ......................................................................................................... 4-12 MSAW ................................................................................................................. 4-13 Profiles ................................................................................................................ 4-14 CDRs .................................................................................................................. 4-15 QNH .................................................................................................................... 4-16 Restricted Areas.................................................................................................. 4-17 MAP .................................................................................................................... 4-18
4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 4.1.10 4.1.11 4.1.12 4.1.13 4.1.14 4.1.15 5 5.1 5.2 5.3
Data Distribution ................................................................................................................... 5-1 Map Colours ................................................................................................................... 5-2 Generate All Data Files .................................................................................................. 5-3 Load Operational Generated Data .................................................................................. 5-3
Config_info.adap ..................................................................................................................... 5-6 Appendix A - Abbreviations .......................................................................................................... A-1
Page xi
DOCUMENT N: 0029200000000MA02
Page xii
DOCUMENT N: 0029200000000MA02
List of Tables
Table A-1: Abbreviations ........................................................................................................A-1
Page xiii
DOCUMENT N: 0029200000000MA02
Page xiv
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
Page 1-6
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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 2 3 4 5 6 7 8 9 10 11 12
AFTN Addresses
AFTN Circuits Fixpoints Airways Aircraft Groups Aircraft Types Wind Zones Working Area Airports Approach routes Control Centers Sectors 12.1 12.2 12.3 Basic Sectors Subsectors Control Sectors
13 14 15
Coordination Fix points External Regions Routes 15.1 15.2 Standard Routes Points Pairs Geographic Regions Entry points between regions Standard routes between regions
16
Geographic Zones 16.1 16.2 16.3
17 18 19 20 21
Pressure Zones User Passwords Meteo Messages Airports Destination Aerodromes SSR Codes 21.1 Destination Regions
Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page 2-3
DOCUMENT N: 0029200000000MA02
DBM Subsystems 21.2 21.3 21.4 21.5 22 23 24 25 1 2 3 4 5 6 7 8 9 10 11 12 13 AMC Aircraft Operators UCS Strip Printers Radar Internal Config Radar External Protocol Radars Directional Finders MSAW STCA Parameters System Parameters SDD Parameters Profile Parameters Profiles SDD Printers Filter Code Ranges VSP 13.1 13.2 13.3 13.4 13.5 1 2 3 4 5 6 7 8 9 FDP Parameters AMHS Parameters APW Parameters MTCD Parameters SDP Parameters Special Use Codes Incoming Codes Outgoing Assignable Codes Outgoing Retainable Codes
Route Conditions
SDP ADAPTATION DATA
ATG ADAPTATION DATA Holding Patterns Instrumental Landing Procedures Inter Approach Speed Area Aircraft Performances Aircraft Subtypes Airports Runways Arrival Procedures Departure Procedures ADS VDL
DOCUMENT N: 0029200000000MA02
DBM Subsystems BADA ADAPTATION DATA DRAW ADAPTATION DATA 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 1 2 3 Fixpoints Airports Airways Sectors SID & STAR Coordination points (COPS) Standard Routes (STD) Radars Wind Zones MSAW Profiles CDRs QNH Restricted Areas MAP Map Colours Generate All Data Files Load Operational Generated Data
DATA DISTRIBUTION
The screen is divided into the following windows:
General Information Window Main Menu Window
Page 2-5
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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.
used
to
Generate Data Files: used to generate the adaptation data files. Generate Map Files: used to generate the default maps for SDDs.
3.1.1 Database manipulation.
Data Base manipulation option shows the list of tables available to be modified or reviewed
Page 3-1
DOCUMENT N: 0029200000000MA02
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. FDP Adaptation Data. -> Database manipulation. -> AFTN Addresses
Location:
Capacity: Main Window:
30 elements
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
DOCUMENT N: 0029200000000MA02
Data window:
Buttons: List of Fields:
EXIT: Exit from this table to the previous screen. 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
DOCUMENT N: 0029200000000MA02
This table accepts up to one (1) element and two circuits
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into database. Report: Option to print the data from the visual window to a file or a predefined printer.
List Fields:
of
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
Page 3-4
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
Page 3-6
DOCUMENT N: 0029200000000MA02
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Append: To append a new point at the end of the list, press the
Page 3-8
DOCUMENT N: 0029200000000MA02
Append button. As a result, an edit field will be displayed to allow the addition of the new point.
OK: Confirm new Fixpoint

Forget: Cancel new Fixpoint and dont 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. OK: Confirm new Fixpoint
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. OK: Confirm new Fixpoint
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 OK: Confirm new Fixpoint
List of Fields:
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.
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Page 3-10
DOCUMENT N: 0029200000000MA02
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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 dont 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 dont 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
DOCUMENT N: 0029200000000MA02
Forget: Cancel new Layer and dont 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
List of Fields:
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. FDP Adaptation Data. -> Database manipulation. -> Aircraft Types
Location:
Capacity:
This table accepts up to one thousand and five hundred (1.500) elements.
Page 3-12
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. AIRCRAFT TYPE: Aircraft Identifier AIRCRAFT GROUP: Group Identifier
Page 3-13
DOCUMENT N: 0029200000000MA02
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. FDP Adaptation Data. -> Database manipulation. -> Wind Zones
Location:
This table accepts up to eight (8) elements and up to four (4) points per Wind Zone.
Buttons:
Page 3-14
DOCUMENT N: 0029200000000MA02
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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: List of Fields:
Inside the working area is possible define maximum 8 wind zones. Are not possible overlapping between the deferents 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
DOCUMENT N: 0029200000000MA02
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. FDP Adaptation Data. -> Database manipulation. -> Working Area
Location:
This table accepts up to one (1) element.
Buttons:
EXIT: Exit from this table to the previous screen. Save: Store all data into database. Report: Option to print the data from the visual window to a file or a predefined printer. 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.
List Fields:
of
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.
DOCUMENT N: 0029200000000MA02
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. FDP Adaptation Data. -> Database manipulation. -> Airports
Location:
This table accepts up to two hundred (200) elements.
Buttons:
Page 3-17
DOCUMENT N: 0029200000000MA02
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
DOCUMENT N: 0029200000000MA02
departure airport and the default departure runway and the same situation for the destination airport.
3.1.1.10
Description:
Approach routes
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. FDP Adaptation Data. -> Database manipulation. -> Approach routes
Location:
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
DOCUMENT N: 0029200000000MA02
Data window:
The next window is used to add new an modify SID or STAR procedure.
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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 carried out the modification, 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. 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.
List of Fields:
Kind : Flag that informs if the approach procedure is an arrival (Star) or an exit (Sid) type.
Page 3-20
DOCUMENT N: 0029200000000MA02
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.
3.1.1.11
Description:
Control Centers
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. FDP Adaptation Data. -> Database manipulation. -> Control Cent
Location:
This table admits up to twenty (20) elements.
Buttons:
Page 3-21
DOCUMENT N: 0029200000000MA02
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table.
Page 3-22
DOCUMENT N: 0029200000000MA02
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. Its 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 thats 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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
List of Fields
AUTHORITY AND FORMAT IDENTIFIER (AFI): In case of Local kind: 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
3.1.1.11.1
Description:
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
DOCUMENT N: 0029200000000MA02
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Center: Control Center ID. Connection Type: o o X25: for X25 connection, the rest of the FMTP Option inputs wont apply. 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. Origin net card for FMTP
Remote Center (Hostname): Destiny Hostname for FMTP communication. Local ID (FDP): Sender identificator Remote ID (EXT): Destination identificator Ti (s): Waiting reception. time for identification message
Tr (s): Waiting time for message reception. Ts (s): Waiting time for message sent.
Page 3-26
DOCUMENT N: 0029200000000MA02
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
3.1.1.11.2
Description:
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
DOCUMENT N: 0029200000000MA02
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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. 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
DOCUMENT N: 0029200000000MA02
PAC, REV, MAC. 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. 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. 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. 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.
3.1.1.12
Description:
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
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
EXIT: Exit from this table to the previous screen. End: Exit from this table to the general screen. Report: Option to print the data from the visual window to a file or a pre-defined printer.
Data window: Buttons: List of Fields:
N/A N/A N/A
3.1.1.12.1
Description:
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.
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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 carried out the modification, press the "OK
Page 3-31
DOCUMENT N: 0029200000000MA02
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 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.
List of Fields:
Rules:
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
DOCUMENT N: 0029200000000MA02
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.
3.1.1.12.2
Description:
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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.
Rules:
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 Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page 3-35
DOCUMENT N: 0029200000000MA02
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
Description:
Control Sectors
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
This table admits up to forty (40) elements and up to one (1) subsector per Control Sector.
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.
Page 3-36
DOCUMENT N: 0029200000000MA02
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:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
Page 3-37
DOCUMENT N: 0029200000000MA02
then this sector contains any volume.
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.
Rules:
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
DOCUMENT N: 0029200000000MA02
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.
3.1.1.13
Description:
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
DOCUMENT N: 0029200000000MA02
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.
Page 3-40
DOCUMENT N: 0029200000000MA02
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
DOCUMENT N: 0029200000000MA02
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. LAM Time Cat 2 (sec): Time interval needed for the message reception reply (Logical Acknowledge Message), associated to OLDI cat 2 messages. LAM Time Cat 3 (sec): Time interval needed for the message reception reply (Logical Acknowledge Message), associated to OLDI cat 3 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
DOCUMENT N: 0029200000000MA02
3.1.1.14
Description:
External Regions
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. FDP Adaptation Data. -> Database manipulation. -> External Regions
Location:
This table accepts up to five hundred (500) elements.
Buttons:
Data window:
Buttons:
EXIT: Exit from this table to the previous screen.

Save: Save all data into table.
List of Fields:
Name: External Region Identifier. Four different sets of characters:
Page 3-43
DOCUMENT N: 0029200000000MA02
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
Description:
Routes
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. FDP Adaptation Data. -> Database manipulation. -> Routes
Location:
N/A
Buttons:
EXIT: Exit from this table to the previous screen. End: Come back to the previous menu. Report: Option to print the data from the visual window to a file or a predefined printer.
Data window:
N/A
DOCUMENT N: 0029200000000MA02
Buttons: List of Fields: RULES:
N/A N/A 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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
3.1.1.15.1
Description:
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
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
Page 3-50
DOCUMENT N: 0029200000000MA02
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
3.1.1.15.2
Description:
Points Pairs
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
DOCUMENT N: 0029200000000MA02
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
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
Description:
Geographic Zones
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. FDP Adaptation Data. -> Database manipulation. -> Geographic Zones
Location:
Capacity:
N/A
Page 3-52
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
EXIT: Exit from this table to the previous screen. End: Come back to the previous menu. Report: Option to print the data from the visual window to a file or a predefined printer.
Data window: Buttons: List of Fields: Rules:
N/A N/A N/A See 3.1.1.15
3.1.1.16.1
Description:
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: Capacity:
FDP Adaptation Data -> Database Manipulation -> Geographic Regions This table accepts up to five hundred (500) elements.
Geographic Zones ->
Page 3-53
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Zone: Identifier for each Geographical Region.
Page 3-54
DOCUMENT N: 0029200000000MA02
3.1.1.16.2
Description:
Entry points between regions

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:
Page 3-55
DOCUMENT N: 0029200000000MA02
Save: Save all data into table. 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
List of Fields:
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
Description:
Standard routes between regions

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. FDP Adaptation Data. -> Database manipulation. -> Geographic Zones -> Standard routes between regions
Location:
Capacity:
This Standard Routes table accepts up to 1000 elements.
Page 3-56
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
Page 3-57
DOCUMENT N: 0029200000000MA02
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
3.1.1.17
Description:
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
DOCUMENT N: 0029200000000MA02
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: Main Window: This table accepts up to fifty (50) elements. Each Pressure zone accepts up to fifty (50) points.
Buttons:
Page 3-59
DOCUMENT N: 0029200000000MA02
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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, 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
Rules:
The next figure shows the general graphical description for the QNH, QFE and TL definitions:
Page 3-60
DOCUMENT N: 0029200000000MA02
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.
List of Fields:
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.
3.1.1.18
Description:
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
DOCUMENT N: 0029200000000MA02
each one. Location: FDP Adaptation Data. -> Database manipulation. -> User Passwords Capacity: Main Window: This table accepts up to five hundred (500) elements.
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. User: User identifier. Password: User password. Alias: User alias. Roll: It informs about the kind of role assigned. 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
DOCUMENT N: 0029200000000MA02
Technical Operative Supervisor: Works as a controller supervisor at a CMD.
3.1.1.19
Description:
Meteo Messages Airports

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
This table accepts up to sixty (60) elements.
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
Page 3-63
DOCUMENT N: 0029200000000MA02
template. Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. NAME: Aerodrome name.
3.1.1.20
Description:
Destination Aerodromes
This table contains information about aerodromes with which AFTN communication is established. FDP Adaptation Data. -> Database manipulation. -> Destination Aerodromes
Location:
This table accepts up to one thousand (1000) elements and up to fifteen (15) AFTN addresses per Aerodrome.
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.
Page 3-64
DOCUMENT N: 0029200000000MA02
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. Save: Save all data into table. 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. 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. 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.
List of Fields:
3.1.1.21
Description:
SSR Codes
This table contains the necessary Transponder SSR codes for performing the necessary correlation between flight plans and radar data. FDP Adaptation Data. -> Database manipulation. -> SSR Codes
Location:
Page 3-65
DOCUMENT N: 0029200000000MA02
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:
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: 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.
General Concepts:
Page 3-66
DOCUMENT N: 0029200000000MA02
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 thats 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.
Destination Regions 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. OK: Inserts the introduced Region.
Page 3-67
DOCUMENT N: 0029200000000MA02
Forget: Cancels the action. Delete: Deletes the previously selected Region.
Functionality Special Codes Use
This window will be used to define all kinds of Destination Regions, depending on the category of each flight.
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. OK: Inserts the introduced Code. Forget: Cancels the action. Delete: Deletes the previously selected Range of codes.
Functionality:
This Table allows to define special use codes that cannot be assigned in further tables.
Page 3-68
DOCUMENT N: 0029200000000MA02
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.
DOCUMENT N: 0029200000000MA02
Outgoing Retainable codes
Buttons
Functionality
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
Rules:
Page 3-70
DOCUMENT N: 0029200000000MA02
- 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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
(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: Buttons: List Fields: of N/A

AIR ANP ICAO CAL Ed 2 May 2006
to
EUR
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Init Code: First Code to be introduced (octal format). End Code: Last Code to be introduced (octal format)..
3.1.1.22
Description:
Route Conditions
This table allows the definition of route conditions, that are established to
Page 3-73
DOCUMENT N: 0029200000000MA02
automatically change the exit flight level of flights that fulfils them. Location: Capacity: Main Window: FDP Adaptation Data -> Database Manipulation -> Route Conditions This table accepts up to three hundred (300) elements.
Buttons:
Page 3-74
DOCUMENT N: 0029200000000MA02
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. Buttons: CREATE, MODIFY, COPY and DELETE: to append, manage or delete airports in the Airports Destination list. AIRPORT: Airport ID.
AIRPORTS DESTINATION:
Page 3-75
DOCUMENT N: 0029200000000MA02
AIRPORT EDITION: Field to manage airports included in Airports Destination list. Action Buttons: OK and Forget: to accept or cancel the action. 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.
Coordination
Offset -X / / COP / / Offset X: fixpoints sequence condition, sequentially before and after the COP as is displayed in this window.
3.1.1.23
Description:
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: Capacity: Main Window:
FDP Adaptation Data -> Database Manipulation -> AMC Restricted Airspaces table accepts up to three hundred (300) elements. CDR table accepts up to a hundred and fifty (150) elements.
Buttons:
Page 3-76
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
Data window:
Buttons: List Fields: of
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Page 3-79
DOCUMENT N: 0029200000000MA02
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 wont apply) CDR HIGH: CDR vertical high level limit (above it, the restriction wont 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. 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 wont apply). This value must
SCHEDULE X:
be higher than the CDR LOW value.

HIGH: CDR high level (above it, the restriction wont apply). This value
must be lower than the CDR HIGH value.
Page 3-80
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
3.1.1.24
Description: Location: Capacity:
Aircraft Operators
This table sets description for each aircraft operator. FDP Adaptation Data -> Database Manipulation -> Aircraft Operators This table accepts up to 3000 elements.
Main Window:
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. ICAO-IATA: aircraft operator. Descriptor: aircraft operator descriptor.
3.1.1.25
Description: Location:
UCS Strip Printers

This table contains FDP Adaptation Data. -> Database manipulation. -> UCS strip Printers
Capacity:
This table accepts up to two hundred (200) elements.
Page 3-82
DOCUMENT N: 0029200000000MA02
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
Buttons:

DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
Page 3-87
DOCUMENT N: 0029200000000MA02
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. SDP Adaptation Data -> Database Manipulation -> Radar Internal Config
Location:
Page 3-88
DOCUMENT N: 0029200000000MA02
Capacity: Main Window: Buttons: Data window:
This table accepts up to two (2) elements. N/A N/A
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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: Location: Capacity: This window will define the external remote centres where send all radar information published in the internal system LAN. SDP Adaptation Data -> Database Manipulation -> Radar External Protocol This table accepts up to one (20) element.
Page 3-89
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Shared SAC: Source Area Code (country identifier number) that RDCU will be identified with. Shared SIC: Source Identifier Code (radar identification number) that
Page 3-90
DOCUMENT N: 0029200000000MA02
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: Capacity: Main Window: SDP Adaptation Data -> Database Manipulation -> Radars This table accepts up to thirty five (35) elements.
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 and fill all the mandatory fields.
Page 3-91
DOCUMENT N: 0029200000000MA02
Data window:
Buttons:
DOCUMENT N: 0029200000000MA02
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.
List Fields:
of
Page 3-93
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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: Location: Capacity: Main Window: This table contains the necessary information to define Directional Finders. They are navigational helps used to identify communications with aircrafts. SDP Adaptation Data -> Database Manipulation -> Finders This table admits up to two hundred (200) elements
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
Page 3-95
DOCUMENT N: 0029200000000MA02
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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. SDP Adaptation Data -> Database Manipulation -> MSAW This table admits up to hundred (100) minimum zones and up to twenty (20) elements points per each minimum zone.
Location: Capacity:
Page 3-96
DOCUMENT N: 0029200000000MA02
Main Window:
MSAW ZONES Main Window:
Buttons:
Page 3-97
DOCUMENT N: 0029200000000MA02
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
List of Fields:
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
DOCUMENT N: 0029200000000MA02
MSAW PARAMETERS Data Window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. Time to Prediction (sec): Value used to warn controllers that in Time to prediction time the alert will be set on.
List of Fields:
3.2.1.6 STCA Parameters

Description: Location: Capacity: Main Window: Buttons: This table contains the necessary information to define the STCA parameters. SDP Adaptation Data -> Database Manipulation -> STCA Parameters This table admits up to ninety nine (99) sectors N/A N/A
Page 3-99
DOCUMENT N: 0029200000000MA02
Data Window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. 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, double-click with the LB, and insert the new data in 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
Rules:
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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: Location: Capacity: Main Window: Buttons: Data Window: This table contains information about The Temporary Parameters that affect to the correlation, de-correlation and transfer functions SDP Adaptation Data -> Database Manipulation -> System Parameters This table admits up to one (1) element. N/A N/A
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. 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
List of Fields:
DOCUMENT N: 0029200000000MA02
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: Location: Capacity: Main Window: Buttons: Data Window: This table shows auxiliary parameters. SDP Adaptation Data -> Database Manipulation -> SDD Parameters This table admits up to one (1) element. N/A N/A
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. 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.
List of Fields:
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.
DOCUMENT N: 0029200000000MA02
Location: Capacity: Main Window: Buttons: Data Window:
SDP Adaptation Data -> Database Manipulation -> Profile Parameters This table admits up to one (1) element. N/A N/A
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. 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.
List of Fields:
3.2.1.10
Description:
Profiles
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. SDP Adaptation Data -> Database Manipulation -> Profiles This table admits:

Location: Capacity:
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
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
Page 3-105
DOCUMENT N: 0029200000000MA02
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: 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
List of Fields:
3.2.1.11
SDD Printers
This table can be used to assign a laser printer to a SDD.
SDP Adaptation Data -> Database Manipulation -> Laser Printers
This table accepts up to twenty (200) elements.
Page 3-106
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
Data window:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
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.
3.2.1.12
Description:
Filter Code Ranges

These tables allows at the system to disable the different alerts (MSAW, STCA,
DOCUMENT N: 0029200000000MA02
APW) to de defined SSR codes Location: Capacity: Main Window: SDP Adaptation Data -> Database Manipulation -> Filter Code Ranges N/A
Buttons: Data window:
N/A
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. 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
List of Fields:
Page 3-108
DOCUMENT N: 0029200000000MA02
3.2.1.13
VSP
This table allows the modification of predefined values for system parameters. SDP Adaptation Data -> Database Manipulation -> VSP N/A
Main Window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer.
List of Fields:
N/A
3.2.1.13.1
Description: Location:
FDP Parameters
This table allows the modification of the FDP system parameters. SDP Adaptation Data -> Database Manipulation -> VSP -> FDP Parameters
Page 3-109
DOCUMENT N: 0029200000000MA02
N/A
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Report: Option to print the data from the visual window to a file or a predefined printer. 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
List of Fields:
DOCUMENT N: 0029200000000MA02
operations on Flights in terminated status, apart from viewing them. 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. 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.
Page 3-111
DOCUMENT N: 0029200000000MA02
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.
3.2.1.13.2
AMHS Parameters
This table allows the modification of the AMHS system parameters. SDP Adaptation Data -> Database Manipulation -> VSP -> AMHS Parameters N/A
Main Window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
This table allows the modification of the APW system parameters. SDP Adaptation Data -> Database Manipulation -> VSP -> APW Parameters N/A
Main Window:
Page 3-112
DOCUMENT N: 0029200000000MA02
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
This table allows the modification of the MTCD system parameters. SDP Adaptation Data -> Database Manipulation -> VSP -> MTCD Parameters N/A
Main Window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
List of Fields:
Page 3-113
DOCUMENT N: 0029200000000MA02
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.
3.2.1.13.5
SDP Parameters
This table allows the modification of the SDP system parameters. SDP Adaptation Data -> Database Manipulation -> VSP -> SDP Parameters N/A
Page 3-114
DOCUMENT N: 0029200000000MA02
Main Window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
List of Fields:
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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 SIM Adaptation Data -> Database Manipulation -> Holding Patterns This table admits up to two hundred (200) elements.
Location: Capacity:
Page 3-118
DOCUMENT N: 0029200000000MA02
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:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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.
List of Fields:
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
3.3.1.2 Instrumental Landing Procedures

Description:
This table contains information about the existing Instrumental Landing Systems (ILS) at a particular runway. SIM Adaptation Data -> Database Manipulation -> Instrumental Landing Procedures This table admits up to thirty two (32) elements.
Buttons:
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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
List of Fields:
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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: Capacity: Main Window: Buttons: Data window:
SIM Adaptation Data -> Database Manipulation -> Inter Approach Speed Area This table admits up to one (1) element. N/A N/A
Buttons:
EXIT: Exit from this table to the previous screen. Report: Make report to print or in a file. Save: Save all data into table. Length: Length of this volume. Height: Height of this volume. Width: Width of this volume. Angle: Angle of this volume.
List of Fields:
Page 3-123
DOCUMENT N: 0029200000000MA02
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. SIM Adaptation Data -> Database Manipulation -> Aircraft Performances This table admits up to two hundred and fifty (250) elements and up to five (5) layers per Aircraft Performance.
Buttons:
Data window:
Page 3-124
DOCUMENT N: 0029200000000MA02
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. Save: Save all data into table. 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.
List of Fields:
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
3.3.1.5 Aircraft Subtypes

Description:
This table contains a set of aircrafts to be associated to the aircrafts groups described above. SIM Adaptation Data -> Database Manipulation -> Aircraft Subtypes This table admits up to six hundred (600) elements.
Buttons:
Page 3-128
DOCUMENT N: 0029200000000MA02
Description:
This table contains a set of aircrafts to be associated to the aircrafts groups described above.
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Aircraft Subtype: Aircrafts Name. Aircraft Performance: Group of aircrafts to which the identified aircrafts belongs.
List of Fields:
Page 3-129
DOCUMENT N: 0029200000000MA02
3.3.1.6 Airports Runways

Description:
This table contains information about the runways of the airports. SIM Adaptation Data -> Database Manipulation -> Airports Runways This table admits up to four hundred (400) elements.
Buttons:
Page 3-130
DOCUMENT N: 0029200000000MA02
Description:
This table contains information about the runways of the airports.
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. Airport: Airports 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.
List of Fields:
Page 3-131
DOCUMENT N: 0029200000000MA02
3.3.1.7 Arrival Procedures

Description:
This table contains information about the procedures used when arriving to a particular airport and runaway. SIM Adaptation Data -> Database Manipulation -> Arrival Procedures This table admits up to hundred (100) elements.
Buttons:
Page 3-132
DOCUMENT N: 0029200000000MA02
Description:
This table contains information about the procedures used when arriving to a particular airport and runaway.
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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. 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. 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, 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: Procedures 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.
List of Fields:
The first fixpoint of sequence of arrival pathway points must be belong to one airway at least
Page 3-133
DOCUMENT N: 0029200000000MA02
3.3.1.8 Departure Procedures

Description:
This table contains information related to Departure Procedures concerning a particular airport and runaway. SIM Adaptation Data -> Database Manipulation -> Departure Procedures This table admits up to two hundred (200) elements.
Buttons:
Page 3-134
DOCUMENT N: 0029200000000MA02
Description:
This table contains information related to Departure Procedures concerning a particular airport and runaway.
Data window:
Buttons:
EXIT: Exit from this table to the previous screen. Save: Save all data into table. 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. 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. 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, 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: 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
List of Fields:
Page 3-135
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
3.3.1.9 ADS VDL

Description: Location: Capacity: Main Window: ADS-B Simulator stations definition. SIM Adaptation Data -> Database Manipulation -> ADS VDL This table admits up to ten (10) elements.
Buttons:
Page 3-137
DOCUMENT N: 0029200000000MA02
Description: Data window:
ADS-B Simulator stations definition.
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
User can select one of these sectors laying the mouse on it and with the mouse buttons access to several actions:
Page 4-6
DOCUMENT N: 0029200000000MA02
If user LB click the geodesic vertex are displayed (see the following figure).
Page 4-7
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
4.1.11 Profiles
This option will present, in several windows, all the profiles that have been inserted into the Database.
Page 4-14
DOCUMENT N: 0029200000000MA02
4.1.12 CDRs
This option will present, in several windows, all the CDRs that have been inserted into the Database.
Page 4-15
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
Page 4-19
DOCUMENT N: 0029200000000MA02
Page 4-20
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
After this action appears the LOAD ADAPTATION DATA window:
Page 5-4
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
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
DOCUMENT N: 0029200000000MA02
Appendix A - Abbreviations
Table A-1:
Abbreviation
A AAI ABI A/C ACC ACID ACK ACP ACT A/D ADA ADEP ADES ADEXP ADS AFIL AFTN A/G AIC AIDC AIP AIRMET AIS ALT AMC ANS APP APW ARR ARTAS ASTERIX ATA ATC ATCAS ATCC ATD ATFM ATIS ATM FDD Message Queue Advanced Boundary Information Message (OLDI) Aircraft Area/Airspace Control Centre Aircraft Identification Acknowledge(ment) Accept message (OLDI) Activation Message (OLDI) Analog-To-Digital Programming language Aerodrome of Departure Aerodrome of Destination ATS Data Exchange Protocol Automatic Dependent Surveillance Aircraft Filed Flight Plan Aeronautical Fixed Telecommunications Network Air/Ground, Air-To-Ground Aeronautical Information Circular Air Traffic Services Interfacility Data Communications Aeronautical Information Publication Airman Meteorological Information Aeronautical Information Service Altitude/Alternate Airspace Management Cell Air Navigation Services Approach Centre Area Proximity Warning Arrival Message ATM Surveillance Tracker and Server All Purpose Structured Eurocontrol Radar Information Exchange Actual Time of Arrival Air Traffic Control Air Traffic Control Automation System Air Traffic Control Centre Actual Time of Departure Air Traffic Flow Management Airport Traffic Information System Air Traffic Management
Abbreviations
Definition
Page A-1
DOCUMENT N: 0029200000000MA02
Abbreviation
ATS AUP AUX B BYP C CA CAA CAD CB CBA CBT CCR CD CDR CFL CFMU CHG CIN CLAM CMD CNL CNS COP COTS CPL CSCI CSSR CTF CTOT CWP D DBM DCT DEP DEP DEST DL DLA DRF E EET Estimated Elapsed Time Data Base Management Direct Route Qualifier Departure Message Departure Aerodrome Destination Aerodrome Data Link/Downlink Delay Data Recording Facility Conflict Alert (see STCA) Civil Aviation Administration/Authority Computer-Aided Design Mouse Central Button Cross-Border Areas Computer-Based Training Communications Compressor Radar Compact Disk Conditional Routes Cleared Flight Level Central Flow Management Unit Change Message See NIC Cleared Level Adherence Monitoring Alert Control and Monitoring Display Cancellation Message By-Pass Mode of Operation Air Traffic Services Airspace Usage Plan Auxiliary
Definition
Communications, Navigation and Surveillance Coordination Point Commercial Off-The-Shelf Current Flight Plan Computer Software Configuration Item SSR Code Common Timing Facility Calculated Take-off Time Control Working Position
Page A-2
DOCUMENT N: 0029200000000MA02
Abbreviation
ENSI ENSO EOBD EOBT EST ETA ETD ETO F FANS FBS FCON FDA FDD FDP FDPS FIFO FIR FIX FL FMU FP FPL FUA G GAT GByte GHz GPS GRIB GUI H HCI HDLC HFS HMI HOLD HWCI Hz I ICAO IEEE International Civil Aviation Organization Human-Computer Interface High-Level Data Link Communication Horizontal Future Situation Human-Machine Interface Hold(Ing) Hardware Configuration Item Hertz General Air Traffic Gigabyte Gigahertz Global Positioning System Wind Meteorological Message Graphical User Interface Future Air Navigation Systems Fallback System Fixed Configuration Flight Data Assistant Flight Data Display Flight Data Processing Flight Data Processing System First In, First Out Flight Information Region Fix Point Flight Level Flow Management Unit Flight Plan Flight Plan Flexible Use of Airspace Expected Sorted Number Input Expected Sorted Number Output Estimated Off-Block Date Estimated Off-Block Time Estimate Estimated Time of Arrival Estimated Time of Departure Estimated Time Over a Fix
Definition
Institute of Electrical and Electronics Engineers
Page A-3
DOCUMENT N: 0029200000000MA02
Abbreviation
IFPS IFR ILS INB INF INT ISO K Kb Kbits Kbps KBps KCAS Kgls KHz KIAS Km KPS Kt KW L LAM LAN LAT LB LCD LMG LONG M M Mb Mbar MET METEO METAR MHz MM MON ms MSAW MSB MSL Match/Meter Millibars Milibar Meteorological Information Meteorological Logical Acknowledgement Message Local Area Network Latitude Mouse Left Button Liquid Crystal Display Local Maps Generation Longitude Kilobytes Kilobits Kilobits per second Kilobytes per second Knots Calibrated Airspeed Kinematics GPS Landing System Kilohertz Knots Indicated Airspeed Kilometer KB per second Knots (NM/ hour) Kilowatts Instrument Flight Rules Instrumental Landing System Inbound Information Message Integrated Mode of Operation International Standards Organization
Definition
Integrated Initial Flight Plan Processing System
Meteorological Aviation Routine Weather Report Megahertz Millimeters Monoradar Mode of Operation millisecond Minimum Safe Altitude Warning Most Significant Bit Minimum Sea Level
Page A-4
DOCUMENT N: 0029200000000MA02
Abbreviation
MTCD N NAV NE NIC NM NOTAM O OAT OLDI ORCAM P PAC PCA PLT POS PSR PSR T PTS Q Q QFE QNH R RAD RAM RAW RB RBL RCA RDCU RDP RDPS RETD RFL RIE RISC RMCDE ROC ROD RPL RVSM Radar Route Adherence Monitoring Restricted Area Warning Mouse Right Button Range Bearing Line Reduced Coordination Airspace Radar Data Communication Processor Radar Data Processing Radar Data Processing System Revised Estimated Time of Departure Requested Flight Level Route Insertion Error Reduced Instruction Set FDD Messages Queue Pre-activation Message Prior Coordination Airspace Pilot Position Report Primary Surveillance Radar Primary Surveillance Radar Track Panoramic Tower Simulator Operational Air Traffic On-Line Data Interchange Navigation Navigation Equipment Navigation Integrity Control Nautical Miles Notice To Airmen Medium-Term Conflict Detection
Definition
Originating Region Code Assignment Method
Atmospheric pressure at aerodrome elevation or at runway threshold Altimeter sub-scale sitting to obtain elevation when on the ground
Radar Message Conversion and Distribution Equipment Rate of Climb Rate of Decent Repetitive Flight Plan Reduced Vertical Separation Minimum
Page A-5
DOCUMENT N: 0029200000000MA02
Abbreviation
RWY S SAM SAR SBY SDD SDP SFPL SID SIGMET SIM SMC SPECI SPI SQL SSR SSS STAR STCA ST-RAW T TACT TAF TAIS TAS TCP TCP/IP TMA TFL TL TOC TOD TRA TSA TSP TWR U UAC UTC UUP V VFS Vertical Future Situation Upper Airspace Control Centre Universal Time Coordinated Updated Airspace Usage Plan Tactical System Terminal Area Forecast (ICAO) Total Aircraft Information System True Airspeed Transmission Control Protocol TCP/Internet Protocol Terminal Maneuvering Area Transfer Fly Level Transition Level Top of Climb Top of Descent Temporary Reserved Area Temporary Segregated Area Technical Supervisor Tower or Tower Control Runway
Definition
Slot Allocation Message (CFMU Message) Search and Rescue Standby Situation Data Display Surveillance Data Processing System Flight Plan Standard Instrument Departure Significant Meteorological Information Simulator System System Monitoring Computer Special Forecast Special Position Identification Structured Query Language Secondary Surveillance Radar Software System Specification Standard Instrument Arrival Route Short-Term Conflict Alert Short-Term Restricted Area Warning
Page A-6
DOCUMENT N: 0029200000000MA02
Abbreviation
VFR VSP W WAN Wi-Fi WWW X X.25 Standard Protocol In Telecommunications Wide Area Network Wireless Fidelity World Wide Web Visual Flight Rules Variable System Parameter
Definition
Page A-7
DOCUMENT N: 0029200000000MA02
This is the last page of this document
Page A-8

0029200000000ma02 2-0 Dbm-Um

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

0029200000000ma02 2-0 Dbm-Um

Diunggah oleh

Hak Cipta:

Format Tersedia

Supply, Installation, Testing and Commissioning of Tower ATS Automation System

Database Manager User Manual (DBM-UM)

Document Number: 0029200000000MA02

Indra Sistemas, S.A.

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

PAGE EDITION AND REVISION RECORD

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

REGISTER OF CHANGES TO THE DOCUMENT

DATE 2010-08-04 2010-11-04

AFFECTED PAGES All All First Edition Second Edition

REASON FOR CHANGE

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 2 2.1

Edition: 2 Revision:0 Date: 04 November 2010

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

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

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

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

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

Manipulation of tables from the Database

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

1.2.1 Renaming an element from the Database.

1.2.2 Copying an element from the Database.

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

1.2.3 Deleting an element from the Database.

1.2.4 Creating an element from the Database.

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

1.2.5 Report concerning a table from the Database.

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

This page left intentionally blank

Database Manager User Manual

Edition: 2 Revision:0 Date: 04 November 2010

Database Manager User Manual