SRD Psi V03.X5.10

SACTA 3.
5 EXTENDIDA Software Requirements Description (SRD) for the control Monitoring and Display Position (PSI)
ID Doc: SPSIHMER3I.016 Edition: 3 / Revision: 0 Date: 22/10/07
Expt N: Exp Number LDEC N: Ldec
Prepared for: Aena Divisin de Automatizacin C/ Josefa Valcrcel, 30 28027 Madrid Prepared by: Indra Sistemas Ctra de Loeches, 9 28850 Torrejn de Ardoz Madrid
This document has been prepared by Indra Sistemas for within the framework of the dossier whose number is stated above and may not be used for purposes different to the established ones, neither total or partially reproduced, passed on or divulged to any person without the Indra Sistemas expressed authorization.
PROJECT: SACTA 3.5 EXTENDIDA
ID Doc: SPSIHMER3I.016
Ed.: 3
Rev.: 0
Date: 22/10/07
TITLE:
Software Requirements Description (SRD) for the control Monitoring and Display Position (PSI)
Indra Sistemas PREPARED BY Name/Date Signature Name/Date Signature Name/Date Signature Name/Date Signature Name and surname / AREA REVIEWED BY Name and surname / AREA
APPROVED / PROJECT GEST. Name/Date Signature APPROVED / CONFIGURATION GEST. Name/Date Signature Alfonso Martn Herrera Jess Fernndez Ocaa
APPROVED / QA Ana I. Moreno Alcntara
APPROVED Indra Name/Date Signature Jess Fernndez Ocaa Aena Jos Luis Meler Jordn
ID Doc: SPSIHMER3I.016
Edition: Revision:
3 0 22/10/07
PROJECT: SACTA 3.5 EXTENDIDA Date:
DISTRIBUTION SHEET
No. COPY 1 1 1
FIRM/ORGANIZATION
DEPARTMENT
NAME AND SURNAME
Aena Aena Indra
DIV. AUTOMATIZACIN DIV. AUTOMATIZACIN Programas Europeos ATM
Emilio Gmez Marcos Jos Luis Meler Jordn Jess Fernndez Ocaa
ATM DIVISION All efforts to guarantee this document accuracy have been carried out. If you have any comment, questions or ideas related to this document, please contact us. By e-mail to: atcdoc@indra.es Or by post to: Ana Isabel Moreno Ctra. de Loeches, 9 28850 Torrejn de Ardoz (Madrid)
III
ID Doc: SPSIHMER3I.016 PROJECT: SACTA 3.5 EXTENDIDA
Edition: Revision: Date:
3 0 22/10/07
PAGE EDITION AND REVISION RECORD
The pages of this document contain the following editions and revisions:
PAGE
EDITION
REVISION
PAGE
EDITION
REVISION
PAGE
EDITION
REVISION
III, IV y V i a iv 1-1 a 1-2 2-1 a 2-2 3-1 a 3-4 4-1 a 4-322 A-1 a A-2
3 3 3 3 3 3 3
0 0 0 0 0 0 0
B-1 a B-8 C-1 a C-2 D-1 a D-2 E-1 a E-2
3 3 3 3
0 0 0 0
DOCUMENT CHANGES RECORD
EDITION
REVISION
DATE
PAGES
REASON OF CHANGE
22/10/07
All
Baseline: 10.0 pb_03.02 Area: DOC Date: 15/10/2007 Prepared: Cecilia lvarez ------------------------------------------------------------------Description: V3.5X.10 Formal Delivery Software Requirements Description (SRD) for the control Monitoring and Display Position (PSI) Id. Doc: SPSIHMER3I.016 Ed./Rv.: 3/0 -----------------------------------------------------------------Content V3.5X.10: IV
- Formal review with AENA (SRD PSI V_3.5X_03.02_Comments_NEW ) - A#12852 - A#19914 - ASC#88 - ASC#1000 Content from previous versions: - ASC#526 (V3.5X.5) - Internal Review (Quality)
SACTA 3.5 EXTENDIDA SRD
Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07
INDEX
CHAPTER 1. INTRODUCTION................................................................................................................1 1.1. PURPOSE 1 1.2. SCOPE 1 1.3. DOCUMENT OVERVIEW.....................................................................................................................1 1.4. ASSUMPTIONS....................................................................................................................................2 CHAPTER 2. DOCUMENTS OF REFERENCE........................................................................................1 CHAPTER 3. COMPONENT GENERAL DESCRIPTION.........................................................................1 3.1. .GRAPHIC INTERFACE OVERVIEW...................................................................................................................1 3.2. SW ENVIRONMENT............................................................................................................................3 CHAPTER 4. REQUIREMENTS SPECIFICATION...................................................................................1 4.1. FUNCTIONAL REQUIREMENTS.........................................................................................................1 4.2. OPERATIVE REQUIREMENTS...........................................................................................................264 4.3. INTERFACE REQUIREMENTS............................................................................................................264 4.4. RELIABILITY / MAINTAINABILITY / AVAILABILITY REQUIREMENTS...............................................305 4.5. DESIGN REQUIREMENTS..................................................................................................................305 4.6. CAPACITY AND PERFORMANCES REQUIREMENTS......................................................................306 4.7. SECURITY / PRIVACY REQUIREMENTS...........................................................................................308 4.8. INSTALLATION REQUIREMENTS......................................................................................................309 4.9. ACCEPTANCE REQUIREMENTS.......................................................................................................309 4.10. HW REQUIREMENTS........................................................................................................................309 4.11. CONFIGURATION DATA...................................................................................................................310 APPENDIX A: DEFINITIONS....................................................................................................................1 APPENDIX B: ACRONYMS AND ABBREVIATIONS...............................................................................1 APPENDIX C: USE CASES......................................................................................................................1 APPENDIX D: REQUIREMENTS TRACEABILITY...................................................................................1 APPENDIX E: EVENT REPORTS.............................................................................................................1 APPENDIX F: WINDOWS DESCRIPTION................................................................................................1
INDEX OF FIGURES FIGURE 3.2-1 : SW ENVIRONMENT........................................................................................................3 FIGURE 4.1.4.1.1-2 : EDITION WINDOW.................................................................................................12 FIGURE 4.1.8.1.3-3 : PSI FUNCTIONS RELATED WITH AIR SURVEILLANCE ( INPUT RADAR CONFIGURATION)...................................................................................................................................118
INDEX OF TABLES Software Requirements Specification i
TABLE 4.1.4.1.1-1 : NOT MONITORIZED TYPE COLOUR TABLE.........................................................2 TABLE 4.1.4.1.1-2 : NOT CONFIGURABLE TYPE COLOUR TABLE......................................................2 TABLE 4.1.4.1.1-3 : CONFIGURABLE TYPE COLOUR TABLE..............................................................3 TABLE 4.1.4.1.1-4 : SPECIALIZED TYPE COLOUR TABLE...................................................................3 TABLE 4.1.4.1.1-5 : STAND-ALONE/POOL TYPE COLOUR TABLE......................................................4 TABLE 4.1.4.1.1-6 : TANDEM TYPE COLOUR TABLE...........................................................................5 TABLE 4.1.4.1.1-7 : WORKING CONTROL TYPE COLOUR TABLE.......................................................5 TABLE 4.1.4.1.1-8 : NOT CONFIGURABLE COLOUR TABLE................................................................6 TABLE 4.1.4.1.1-9 : CONFIGURABLE COLOUR TABLE........................................................................6 TABLE 4.1.4.1.1-10 : CONFIGURABLE RADAR LINK COLOUR TABLE...............................................7 TABLE 4.1.4.1.1-11 : SECTORIZATION ..................................................................................................8 TABLE 4.1.4.1.1-12 : UDDE ITEM COLOUR TABLE...............................................................................8 TABLE 4.1.4.1.1-13 : RADAR SEPARATION FOR TMA COLOUR TABLE.............................................9 TABLE 4.1.4.1.1-14 : RADAR SEPARATION FOR ENROUTE COLOUR TABLE...................................9 TABLE 4.1.4.1.1-15 : TIME SERVER COLOUR TABLE...........................................................................10 TABLE 4.1.4.1.1-16 : SUBSYSTEM COLOUR TABLE.............................................................................10 TABLE 4.1.4.1.1-17 : DYNAMIC ELEMENT COLOUR TABLE................................................................11 TABLE 4.1.4.2.1.3.1-18 : TIME SYSTEM .................................................................................................25 TABLE 4.1.4.2.1.3.1-19 : EXTERNAL SCV SYSTEM ..............................................................................25 TABLE 4.1.4.2.1.3.1-20 : EXTERNAL CCTV SYSTEM ............................................................................25 TABLE 4.1.4.2.1.3.1-21 : RADAR SEPARATION SYSTEM FOR TMA DEPENDENCIES .......................26 TABLE 4.1.4.2.1.3.1-22 : RADAR SEPARATION SYSTEM FOR EN-ROUTE DEPENDENCIES ............26 TABLE 4.1.4.2.1.3.1-23 : GPIV SUBSYSTEM .........................................................................................26 TABLE 4.1.4.2.1.3.1-24 : TCPV SUBSYSTEM ........................................................................................27 TABLE 4.1.4.2.1.3.1-25 : GSI SUBSYSTEM ............................................................................................28 TABLE 4.1.4.2.1.3.1-26 : SILV SUBSYSTEM ..........................................................................................28 TABLE 4.1.4.2.1.3.1-27 : SPV SUBSYSTEM ...........................................................................................29 TABLE 4.1.4.2.1.3.1-28 : SMDT SUBSYSTEM ........................................................................................29 TABLE 4.1.4.2.1.3.1-29 : SIS SUBSYSTEM ............................................................................................30 TABLE 4.1.4.2.1.3.1-30 : TLPV SUBSYSTEM .........................................................................................30 TABLE 4.1.4.2.1.3.1-31 : TDVM SUBSYSTEM ........................................................................................31 TABLE 4.1.4.2.1.3.1-32 : EADR SUBSYSTEM ........................................................................................32 TABLE 4.1.4.2.1.3.1-33 : TMA SS OR EN-ROUTE SS SUBSYSTEM .....................................................32 TABLE 4.1.4.2.1.3.1-34 : REM SS SUBSYSTEM ....................................................................................33 TABLE 4.1.4.2.1.3.1-35 : TWR SUBSYSTEM ..........................................................................................33 TABLE 4.1.6.1-36 : GIPV SCENARIO ELEMENTS..................................................................................38 TABLE 4.1.6.2-37 : TCPV SCENARIO ELEMENTS.................................................................................41 TABLE 4.1.6.3-38 : GSI SCENARIOS ELEMENTS..................................................................................44 TABLE 4.1.6.4-39 : SILV SCENARIOS ELEMENTS................................................................................47 TABLE 4.1.6.5-40 : SPV SCENARIOS ELEMENTS.................................................................................50 ii Software Requirements Description
TABLE 4.1.6.6-41 : SMDT SCENARIOS ELEMENTS..............................................................................53 TABLE 4.1.6.7-42 : SIS SCENARIOS ELEMENTS...................................................................................56 TABLE 4.1.6.8-43 : TLPV SCENARIOS ELEMENTS...............................................................................58 TABLE 4.1.6.9-44 : TDVM SCENARIOS ELEMENTS..............................................................................61 TABLE 4.1.6.10-45 : EADR SCENARIOS ELEMENTS............................................................................67 TABLE 4.1.6.11-46 : EN-ROUTE SS SCENARIO ELEMENTS.................................................................72 TABLE 4.1.6.12-47 : REM SS SCENARIO ELEMENTS...........................................................................74 TABLE 4.1.6.13-48 : TMA SS SCENARIO ELEMENTS...........................................................................77 TABLE 4.1.6.14-49 : TWR SCENARIO ELEMENTS.................................................................................79 TABLE 4.1.7.5.1-50 : STARTUP WITH CROSSED LAN SITUATION......................................................92 TABLE 4.1.6.10.1.3.3-51 : RADAR CONNECTION STATE......................................................................121 TABLE 4.1.8.1.8-52 : DESIRED CONFIGURATION PERFORMED FOLLOWING THIS TABLE..............125 TABLE 4.1.8.3.1-53 : CONFIGURATION FUNCTION..............................................................................174 TABLE 4.1.8.3.2-54 : PREVIOUS CLASSIFICATION SUMMARY...........................................................177 TABLE 4.1.10.1.5-55 : PSI FUNCTIONS RELATED TO AIR SURVEILLANCE (TDVM STATISTICS).....229 TABLE 4.1.10.1.6-56 : PSI FUNCTIONS RELATED WITH AIR SURVEILLANCE (SYSTEMATIC ERROR RADAR STATISTICS)..............................................................................................................................231 TABLE 4.1.10.1.11.1-57 : PSI FUNCTIONS RELATED WITH AIRE SURVEILLANCE(MONORADAR EADR STATISTICS)............................................................................................................................................244 TABLE 4.1.10.1.11.1-58 : LIST OF STATISTICS ELEMENTS OF A RADAR EMPLACEMENT IN NORMAL MODE.......................................................................................................................................................246 TABLE 4.3.4.18.14-59 : FUNCTIONALITIES ...........................................................................................315 TABLE 4-60 : ACRONYMS AND ABBREVIATIONS................................................................................7
Software Requirements Specification
iii
Page intentionally left blank
iv
Software Requirements Description
CHAPTER 1. INTRODUCTION 1.1. PURPOSE The current document constitutes the Requirements Specification of the Control Monitoring and Display Position, henceforth PSI. The aim of the PSI component is to arrange a Supervision Position with a user interface (HMI support) in order to operate the SPV middleware (supervision) and to give a response to the management needs, control and monitoring of the integrated in SACTA System services, on which it will be being incorporated action and management operatives, more efficient each time, being based on graphic interfaces of a quick interaction with the operator. The PSI component will incorporate the required functionality in order to support the management HMI, taking into account the characteristics, needs and functionality of the SACTA System, where it is integrated. The PSI is delimited in the Supervision system (SPV), within the SACTA system. The functional and operative requirements are described in order to design, to implement and to test the PSI. Each function is also depicted, as well as its own operational inputs and outputs. Likewise, the HW and SW components of the different Subsystem locations are described. Firstly, an overview of the concepts used in this document will be done in order to understand and locate them correctly. 1.2. SCOPE This document is applicable to: System: SACTA-III System version: 03.05X Partition: Operational Subsystem: PSI CSCI: Control, Monitoring and Display Position (PSI) NOTE: See document properties in SW support to see the DOORS baseline with which this document is produced.
1.3. DOCUMENT OVERVIEW The information provided in this document is structured in the following way: Chapter 1 is a general introduction Chapter 2 includes the reference documents Chapter 3 includes a CSCI's general description Chapter 4 includes all the requirements grouped according to their type. Some Appendixes are available with the following content: Appendix A: Definitions Appendix B: Acronyms and Abbreviations 1
Appendix C: Use cases Appendix D: Requirements Traceability Appendix E: Event Reports Appendix F: Windows Description
1.4. ASSUMPTIONS The values associated to the requirements mark the minimum threshold the system will provide.
CHAPTER 2. DOCUMENTS OF REFERENCE The following documents are applicable in the extension indicated in this document, except it is said otherwise: [1] Software Development Methodology (CMMI). Indra. Reference: MAN-ID-560 (Rev/Upd: 1/0). Date: 20/02/06. [2] Guide for the Requirements Specification. Indra. Reference: IP-ID-5610 (Ed/Rev: 1). Date: 01/02/06. [3] Standard for the Software Requirements Specification. Indra. Reference: IP-AT-5613 (Ed/Rev: 1). Date: 4/5/05. [4] Standard for System Subsystem Design Description (SSDD) / System Architecture & Requirements Allocation Description (SARAD). Indra. Reference: IP-ID-5612 (Ed/Rev: 1). [5] System Requirements Specification (SRS). Indra. Reference: SACTA3ER4I.294.
CHAPTER 3. COMPONENT GENERAL DESCRIPTION The PSI will constitute the SACTA System interface for the operator responsible of the supervision, that is, the HMI through what the operator interacts with the different systems, which compose the SACTA system, to which we will refer as components. In the Supervision Position it will be displayed all the information related with the anomalies, as hardware (HW) as software (SW) ones, occurred in the different scenarios which compose the subsystems, manufactured by the middleware which constitutes the SPV subsystem. The information received from the middleware, as processes tables, for instance, will be displayed in visualization screens, where the visualized scenarios inform about the current situation of the different subsystems and about the anomalies which are generated as alerts. From this HMI appropriate configurations actions will be able to be executed in order to give a response to the anomalies. The navigation through the scenarios will be intuitive, and it will be always possible to return to the main screen, which will summarize the different contemplated scenarios in the SACTA System, or it will be possible to access immediately to the scenario where the anomaly has been produced. Each scenario will represent the structure of a subsystem logical group accurately, which collaborate closely in order to provide a considered service as a unit. From the Supervision Position it will be possible to dialogue with the SACTA components through the middleware, in order to get information from the component or to interact for solving anomalies. According to the operative needs of each centre, the PSI can be configured in order to render service to the different kind of users. Each of these configurations is called profile. From the physical point of view, it will be able to exist up to 4 Control, Monitoring and Display Positions (PSI) according to that defined in the design document of the system. In whatever of them it will be able to execute any of the profiles loaded in it. 3.1. .GRAPHIC INTERFACE OVERVIEW Generally, the Graphic Interface will have the following advantages: Pointer device Menus operated by the pointer device.
Division of the Screen. Keeping in the centre of the screen the information depending on the scenario, and on the left, topside and underside of the screen, also the common information to the different scenarios is displayed. Graphic images representing infrastructure, state and, besides they will allow to know what the commanded instructions are doing. Multitasking which guarantee the processing in real time of all the information received from the different components, although it is represented in another scenario guaranteeing the information transference. Representative icons. Writing consistence in the different scenarios. Graphics and texts in actual mode.
Object-action interaction It will be able to handle the objects and the information in the screen so that: It provides interface elements as menus and dialogues. Visual response to the user actions 1
Graphic controls (widgests) exist for the selection and entering of the information.
It will allow the users to personalize the interface and the interactions As Interface Aimed to Objects, it will dispose of the following elements: Data Containers
Devices As relevant principle for the design and implementation of the Interface it will be considered the following ones: Anticipation Autonomy Colour perception Values by default Consistence
User efficiency Concerning to the Efficiency the following characteristics will be considered: Deployment time: The time in which the system displays the information requested by the user, will be the one of maximum efficiency. Response time: The time in which the system detects an anomaly and it replies with an action, will be the one of maximum efficiency. Availability: Every user will be allowed to use the system if desired. Security: The users not authorized to use the PSI will not have access to the system neither to part of it. Integrity: The displayed information will be true and the same one in all the positions. Standardization: The user interface characteristics will be common among the different scenarios and components. Integration: All the scenarios, components and interaction elements, will be easily accessible. Consistence: The visual support, the terminology and the commands will be the same in all the screens. The aim will be the following: Higher learning speed. Lower errors rate of the user Greater retention of the functionalities Satisfaction with the system
The heuristic in the assessment of the Interface will be the following: 2 System state visibility Similarity of the system to the world it represents. Control by user side Access security Information consistence through scenarios Errors prevention Acknowledgement of actions and options Flexibility and efficiency in the use Acknowledgement of anomalies, diagnostic and recovering Software Requirements Description
Colour Analysis. The colour will communicate information. The colour combinations searched for will be the suitable ones. 3.2. SW ENVIRONMENT This section depict the MwER facility context diagram representing the MwER environment. The interfaces represented in the context diagrams are external interfaces, with other CSCIs.
'ADAP-GV' FAST
OperationalSupervisor
CWP
TechnicalSupervisor
AMAN
GIPV
DMAN
DDVE
MTCD
SurveillanceDataAcquisition
ControlMonitoring
AirSurveillance
PSI
DistributedConfiguration
SurfaceSurveillance
Statistics
TILAIS
EventReports
TILMET
Recording
TIMDT
COM
TLPV
AFTNLinkManagement
Figure 3.2-1 : Sw Environment
CHAPTER 4. REQUIREMENTS SPECIFICATION 4.1. FUNCTIONAL REQUIREMENTS In this section the PSI Application Functions are depicted: Accessibility to the different functions shall be determined by the user profile PSI-3554 configured in each PSI.
It will allow to establish the start-up situation of each system. Once concluded this phase, we move to operating position. This phase is monitored by scenarios. The anomalies occurred or current will be able to be visualized by means of the event reports. The anomalies acknowledged as of special importance will become Alerts. Also it will allow to follow the support systems, as the Time System. Also radar information will be displayed. The necessary information for the monitoring of the different subsystems will be received from themselves. The different monitoring functions will be the following: System Start-up Scenarios System Event Reports Alarms Time System Radar Separation for TMA dependencies Radar Separation for En-route dependencies A#12845
4.1.1.
APPLICATION ACCESS
The access to the application by means of user/password (see security) shall PSI-1256 fix the application appearance for the aforementioned user.
In each centre so many profiles as kind of applications desired shall be PSI-1257 defined in order to be able to configure in the machines.
The access to the application shall be done from the access window which PSI-7075 will appear in the PSI when the application is stopped.
In this window, once the user (login) and password (password) have been PSI-7076 entered and everything have been correctly validated, the access to the application shall be allowed. (More details in the security section).
4.1.2.
COLOUR INFORMATION
A colour code shall be used to represent the state of the PSI application PSI-7149 elements listed below.
4.1.2.1. ELEMENT TYPES AND COLOUR TABLES Device Types: PSI-8422 See next table.
Physical States Device Element Type

Not Monitorized (Without Control) Abr . SC Description Uncontrollable Atrib. Grey
Logical and Other States

Abr. Description Atrib. -
Table 4.1.4.1.1-1 : Not Monitorized type colour table PSI-8423 See next table.

Abr . D Not Configurable (Basic) F SD R Description Available Failure Unknown Stand-by (only RANC) Atrib. Green Flashing Red Blue Yellow

Abr. Description Atrib.
Table 4.1.4.1.1-2 : Not Configurable type colour table NOTE:It is allowed the following state changes:: F-> ND -> D See next table. PSI-8424

Abr . D F Configurable ND SD DG Description Available Failure Not Available Unknown Atrib. Green Flashing Red Fix Red Blue

Abr. EU Description In Use (only DG) Atrib. Purple Frame
Degraded (Only for IFV: few paper Yellow left)
Table 4.1.4.1.1-3 : Configurable type colour table PSI-8425 See next table.

Abr . Description Atrib. Flashing Red Green Without Atrib.

NSZ Not Synchronized Specialized SZ SD Synchronized Unknown
Table 4.1.4.1.1-4 : Specialized type colour table Processor Types: PSI-8426 See next table.
Processor Element Type

Abr.
Physical States
Description Atrib.

Abr. SZ Description Synchronized Not synchronized Atrib. Clock not displayed Red Clock
Available
Green NSZ
Stand-Alone / Pool
F ND SD
Failure Not Available (Not for UDDE) Unknown
Flashing Red Fix Red Blue -
Table 4.1.4.1.1-5 : Stand-Alone/Pool type colour table PSI-8427 See next table.

Abr.
Physical States
Description Atrib.

Abr. SZ Description Synchronized Not synchronized Synchronized Not synchronized Synchronized Not synchronized Atrib. Clock not displayed Red Clock Clock not displayed Red Clock Clock not displayed Red Clock
Operative
Green NSZ SZ
Stand-by
Yellow NSZ
Tandem RND Stand-by Not Available
Flashing Yellow
SZ NSZ
ND SD F
Not Available Unknown Failure
Fix Red Blue Flashing Red -
Table 4.1.4.1.1-6 : Tandem type colour table PSI-8428 See next table.
Physical States
Abr . Description Atrib. Abr SZ

Description Synchronized Atrib. Clock displayed Red Clock not
NSZ Not synchronized Executive (Only ACC_CWP) Planner (Only ACC_CWP) Integrated (Only ACC_CWP) Normal (Only for CWP) Autonomous (Only for CWP) Profile (Only for PSI) Synchronized
for White (E)
P D Available Green I
for White (P)
for White (I) Without Frame Purple Frame Label Profile Name Clock displayed Red Clock not
N Working Control AU -Stand-by (Not Operative) (Only ACC_CWP) Failure Not Available Unknown SZ Yellow
NSZ Not synchronized Flashing Red Fix Red Blue -
F ND SD
Table 4.1.4.1.1-7 : Working Control type colour table Link Types: PSI-8429 See next table.
Physical States Link Element Type

Abr. C Not Configurable (Basic) NC SD Description Connected Not Connected Unknown Atrib. Green Flashing Red Blue Abr .

Description Atrib.
Table 4.1.4.1.1-8 : Not Configurable colour table NOTE:It is allowed to change a logic state independently from a physic PSI-8430 state. See next table.

Abr. Description Atrib. Abr . H C Connected Green NH H NH H SD Unknown Blue NH

Description Enabled Not Enabled Enabled Not Enabled Enabled Not Enabled Atrib. Without Frame Purple Frame Without Frame Purple Frame Without Frame Purple Frame
Configurable
NC
Not Connected
Flashing Red
Table 4.1.4.1.1-9 : Configurable colour table NOTE:It is allowed to change a logic state independently from a physic PSI-8431 state. See next table.

Abr. Description Atrib. Abr . H NH

Description Enabled Not Enabled Secondaries Deconfigured (RAD_DDE RAD_AST) Enabled Not Enabled Secondaries Deconfigured (RAD_DDE RAD_AST) Enabled Not Enabled Secondaries Deconfigured (RAD_DDE RAD_AST) Enabled Not Enabled Secondary Deconfigured Atrib. Without Frame Purple Frame S White with purple background Without Frame Purple Frame S White with purple and background Without Frame Purple Frame S White with purple and background Without Frame Purple Frame S White with purple background
Connected
Green
DS
and
H Non Connected Flashing Red NH
NC
DS Configurable Radar Link H NH
SD
Unknown
Blue
DS
DG
Degraded (only RAD_AST, RAD_SMR and RAD_SMM)
H Yellow NH DS
Table 4.1.4.1.1-10 : Configurable Radar Link colour table Other Element Types: PSI-8432
or O.R. Indicator colour table See next table.
Other Element Types

Abr.
Physical States
Description Atrib. Abr. SEC or CO NSEC or NCO

Description Sectorized or Configured Atrib. Dark Grey Background
Sectorization (in ACC) or O.R. Indicator (in TWR)
Not Sectorized or Light Grey Background Not Configured
Table 4.1.4.1.1-11 : Sectorization PSI-8433 See next table.
Other Element Types

Abr. O R UDDE Item F SD
Physical States
Description Operative Stand-by Failure Unknown Atrib. Green Yellow Flashing Red Blue -

Table 4.1.4.1.1-12 : UDDE Item colour table PSI-8434 See next table.
Other Element Types

Abr. Radar Separation (TMA)
Physical States
Description Atrib. Nominal NOM (at least one main radar Green is operative) DG Degraded Yellow (none main radar operative, at least one secondary radar operative) -

Abr. Description Atrib. -
Other Element Types

Abr. F SD
Physical States
Description Failure (None radar operative) Unknown Atrib. is Red Blue

Table 4.1.4.1.1-13 : Radar Separation for TMA colour table PSI-9155 See next table. A#12845
Other Element Types

Abr.
Physical States
Description Atrib.

Radar Separation (EnRoute)
Nominal (DTC for all sectors and ACC adapted to provide Separation Green NOM Reduced orTC for all sectors and ACC NOT adapted to provide Reduced Separation) Degraded (TC for all sectors and Yellow ACC adapted to provide Reduced Separation.) Failure (At least one without TC) Unknown sector Red Blue -
DG
F SD
Table 4.1.4.1.1-14 : Radar Separation for EnRoute colour table PSI-8435 See next table.
Physical States Other Element Types

Abr . SD Description Unknown Available (Fully Synchronized, both LANs) Degraded (Partially Synchronized, only by one LAN) Failure (Not Synchronized) Atrib. Blue Abr.

Description Atrib.
D Time Server DG
Green Yellow -
Flashing Red
Table 4.1.4.1.1-15 : Time Server colour table PSI-8436 See next table.
Physical States Other Element Types

Abr. O R Subsystem SD NO Unknown Not Operative Blue Fix Red Description Operative Stand-by Atrib. Green Yellow Abr.

Description Atrib.
Table 4.1.4.1.1-16 : Subsystem colour table PSI-8437 See next table.
10
Other Element Types

Abr.
Physical States
Description Scroll with operational configuration information. the Atrib. Abr.

Description Atrib.
Dynamic Element
OCI
Table 4.1.4.1.1-17 : Dynamic Element colour table
4.1.3.
WINDOWS GENERAL INFORMATION
4.1.3.1. SELECTION AND EDITION WINDOWS This kind of window shall allow the entering or selection of information by the PSI-7107 user.
Edition windows shall be moved around for all the screen.
PSI-7123
Any edition/selection of data will be performed under a delimited area, called window, and which characteristics are the following: They shall be displayed in the scenarios area after having selected a PSI-7111 function or sub-function. The windows shall appear delimited under a name which identifies PSI-7112 the option or action selected by the user. These windows will have at their disposal the following elements which will be able to be or not to be present. Edition fields: These fields are those existing areas within the window, PSI-7114 which allow to enter information. These fields shall allow one or another type of information, depending on the kind of parameter, that is, in case the field is numeric, numbers will only be allowed, if it is alphabetical, letters will only be accepted, etc. Non Edition Fields: Existing areas which shall display information of PSI-7115 the System. The operator won't be able to enter or modify information in these fields. Operation Buttons: They shall be displayed in the windows PSI-7116 associated with functions. There will exist 3 types:
11
"Execute" button. In case every changes and creations are PSI-7117 accepted, the modifications shall be kept. "Analyse" button. It shall perform an analysis of changes and any PSI-7118 change will be kept, that is, when existing from the function, we return to the immediately previous situation. "Exit" button. It shall return to the previous window without having PSI-7119 performed any modification. Whenever an internal operation is being performed, the mouse cursor shall PSI-7120 change to a "clock" indicating waiting to the operator, either it is an information recovering or a confirmation the entered data are correct. PSI-7121
S u be elem e nto a e lem en to S ub e p agina a pa gina S u be o B aja a vo lu ntad B aja pag in a a p ag in a ZO N A DE ED IC IO N P R ES EN T AC IO N Ba ja e lem e nto a e lem en to
ZO NA DE D E F IN IC IO N
Resectorizacinde informacinGrab ar Configuracin Configuracin de informacinacio C onfig uraci on d e laOperativa n a a grabar In form a grabar
E ditar
Conf. Fsica
Listar
ZO N A DE EJEC U C IO N
G en era r Ejecutar
M o dificar Analizar
B o rrar Salir
Figure 4.1.4.1.1-2 : Edition Window Each function window and its operation will be depicted in the corresponding section of this document. 4.1.3.2. CONFIRMATION AND ERROR WINDOWS Confirmation or error messages: A little window with the possible error PSI-7125 made by the operator shall be displayed, either during the entering of the parameters values, or during the selection of the actions to be performed with the already existing data. Also it could ask for confirmation of the performed action. The error message or confirmation request shall be self-explanatory and it will PSI-7126 be associated with the "OK" or "Cancel" button.
In case of errors, on clicking "OK" the mouse cursor shall be located on the PSI-7127 field where the error has been made.
The Error and Confirmation windows shall be moved around for all the PSI-7128 screen.
12
4.1.3.3. PRINTING ON SCREEN This function allows to print the current PSIs screen. PSI-3528
This function shall be executed by pressing the [PrintScreen] key.
PSI-3529
When pressing the print key [PrintScreen], an audio warning shall be PSI-3530 generated indicating that printing is going to take place, and the cursor image shall change to a clock one. The screen capture causes a moment of lack of response to the operator; when control is recovered, the cursor shall return to its normal image and the printing key shall be inhibited during a fixed amount of time (approx. 3 min).
4.1.3.4. PSI HELP Through this functionality it will be possible browse the window where the help of the PSI is displayed. This function shall be run clicking on the "F1" key PSI-6236
4.1.4.
MAIN SCENARIOS
After having been authorized, the user shall access to the main application PSI-7078 window.
4.1.4.1. UPPER AREA The Upper Area shall be located in the upper part of the monitor image. PSI-8443
The Upper Area consist of the following elements: 4.1.4.1.1. Profile Identification Bar
The Profile Identification Bar shall display the user profile used to launch PSI-7083 the application.
4.1.4.1.2.
Event Reports Bar PSI-7084
The Event Reports Bar that shall consist of the following elements:
13
Graphical buttons: When they are selected it shall display system PSI-7087 information in non-editing fields or open a window. It will display the following ones: The EVENT REPORT button shall display a window with the PSI-7088 last 100 event reports. On displaying the window, event reports will be showed with a letter font in red colour and others with white font. ER with red font They will be ER with automatic acknowledgement (they won't be displayed in the historical messages zone) or already read ER. They will have a permanence time for each profile in the configurable window. ER with white font. They will be unacknowledged ER, therefore without having been acknowledged. They could have a permanence time in a different window from the ones of automatic acknowledgement, and it will be configurable for each profile.
The NEXT button acknowledged Event Report.
shall
acknowledge
the
firs
non- PSI-8442
Non-editing fields: The operator shall not be able to enter or modify PSI-7085 the information in these fields. It will display the following one: The Event Reports visualization field. It shall display the first PSI-7086 non-acknowledged Event Report .
4.1.4.1.3.
System Time
The time synchronization function of the system will lean on the use of the standard NTP protocol. This protocol defines a client-server architecture with several levels (Stratum), where the servers of the highest level (Stratum 0) will be considered the providers of time information with the greatest accuracy. The SACTA system will use a single level architecture for the processors connected to the Radar Lan. In the remaining Lans, it will have two levels. As level 1 timeservers, 2 units connected to the Radar Lan will be used. They will be fed with GPS information and, in turn, they will spread the time reference obtained, to all the processors connected to such LAN. The Clock shall display the month, date, time and minutes. PSI-2502
The system time shall be displayed at every moment, in each of the PSI-3472 supervision positions, regardless of the scenario being viewed and the profile being performed.
14
The time displayed shall depend on the system mode, displaying the PSI-3473 simulated time when performing a simulation session.
The system time servers state shall be displayed through the Colours Code PSI-1577 corresponding to the Time Server colour table located in the Colour Information section of this document. The PSI shall be synchronized with the timeservers by using the standard PSI-1582 NTP protocol. The PSI processors shall perform the NTP client role through the Radar Lan. The PSI shall establish which is the best timeserver of all the ones received, PSI-2509 and it will synchronize with the selected one. (SACTA normally uses two timeservers) The PSI processors shall act as NTP servers for the remaining processors, PSI-2504 via LANs where PSI are connected to, whenever they are not radar Lan (Control Lan). The processors connected to the Control Lan shall receive NTP information from the PSIs. If in the start-up of a processor this is configured in order not to be PSI-2511 synchronized by the NTP, it shall communicate with the PSI as it were a synchronization loss (that is, with alarm and graphic symbol on the processor) and so, it will be generated the de-synchronization event report in the start-up No Synchronization The lack of synchronization of the processor shall be set by the time offset PSI-1581 between its timeserver and the processor in a parameter value.
The lack of synchronization of the processor shall cause the alarm generation PSI-2505 in the PSI
The processors of the different subsystems shall indicate their lack of PSI-2503 synchronization with a timeserver through a suitable writing (red hourglass) on the writing of the processor corresponding to the scenarios where they appear. An event report of non synchronization shall be generated in the processor PSI-2506 start-up. Synchronization Recovery The synchronization recovering of a processor shall cause the alarm PSI-2501 elimination.
The synchronization recovering of a processor shall cause the disappearance PSI-2500 of the writing (red hourglass). Software Requirements Specification 15
The synchronization recovering of a processor shall cause the generation of PSI-2507 an event report informing about the event.
At the moment the alarm is recognized by the operator it shall disappear PSI-2499 (moving along the alarm with the mouse pointer)
Although the alarm is recognized, the clock writing only shall disappear when PSI-2510 the synchronization is recovered.
4.1.4.2. CENTRAL AREA The Central Area shall be located in the central part of the monitor image. PSI-8444
The Blocks Diagrams shall represent the different subsystems and links, as PSI-7096 well as the state in what they are, through a colours code.
In case all the elements of a scenario do not fit in this zone, an horizontal PSI-7097 scrolling bar shall appear in the lower part of the scenario in order to visualize them.
4.1.4.2.1.
Links and System Information area
The links and system information area shall be located on the left side of the PSI-1625 main scenario.
This area is divided in the following parts:
PSI-1624
4.1.4.2.1.1. National Adjacent Centres Links The National Adjacent Centres links shall be displayed through the Colours PSI-8463 Code corresponding to the Configurable Link colour table located in the Colour Information section of this document. NOTE: The links state with national adjacent centres will monitor if it exists some started up PSI in the other centre, because this PSI will be considered the minimum element which is always started up in the adjacent centre. 4.1.4.2.1.2. Radar Separation for TMA dependencies PSI/PST of a control centre could be reached even by two events of radar state. 16 Software Requirements Description
These are the events with the state of a radar (Operative/Non Operative) from the adapted radars for a Dependency. They are susceptible of being consumed by PSI/PST and published by: SURV-A SURV-S SURV-A
From all this events susceptible of being received it will be used for every specified Local Dependency. Remote Dependency with SMDT. Remote Dependency without SMDT and adapted for receiving tracks from TDVM. Remote Dependency without SMDT and not adapted for receiving tracks from TDVM.
Local Dependency PSI-7004 The PSI (PSI of the centre of control RUTA/TMA) shall consume the periodic event EvtSurvA_RadarStatus published by SURV-A (Normal Mode which will run in the TDVM), to determine the operative state of the radars. Remote Dependency with SMDT PSI-7005 The PSI (PST of a centre of control of type TWR) with SMDT, shall consume the periodic event EvtSurvS_RadarStatus published by the SURV-S which will run in the SMDT, to determine the Operative state of the radars.
Remote Dependency without SMDT and adapted to receive tracks from the PSI-7006 TDVM The PSI/PST of a centre of control (remote TMA or in TWRs) without SMDT and adapted to receive tracks from TDVM shall consume the periodic event EvtSurvA_RadarStatus published by the SURV-A Remote Dependency without SMDT and NO adapted to receive tracks from PSI-7007 the TDVM The PSI/PST of centre of control ( Remote TMA or in TWR) without SMDT and no adapted to receive tracks from the TDVM shall consume the periodic event EvtSurvA_RadarStatus published by the SURV-A (Autonomous Mode for the Position of Control which will configure with that aim), to determine the Operative state of the Radars.
The adaptation file which shall be read by the PSI/PST with the main adapted PSI-7008 radars will be: SrvAdapgv_RadarDataDepen Where the dependency can be one of the following ones: Local Dependency: TMA and/or EN-ROUTE Remote Dependency with SMDT: TWR
Remote Dependency without SMDT: TMA (remote TMA) or TWR (with or without control from the APP) The adaptation file which shall read the PSI/PST where it shall be indicated if PSI-7009 a CCV (Dependency) shall receive or not tracks from the TDVM will be: Software Requirements Specification 17
SrvAdapgv_RemoteDistributionSurveillance
The radar quality element shall only be displayed in case the dependency PSI-1635 where the PSI is located has defined some main radar (adaptation datum) It shall be displayed only the element TMA separation radar if it is configured by profile of PSI and the centre of control where it the PSI is placed has some main radar defined ( adaptation data) for the dependencies: Local Dependency: TMA and/or EN-ROUTE Remote Dependency with SMDT: TWR
Remote Dependency without SMDT: TMA (remote TMA) or TWR (with or without control from the APP) The separation radar element shall show the different levels defined in the PSI-1665 operative state function of the radars for the TDVM or TDVM-A. The colours code used shall be the corresponding to the Separation Radar colour table located in the Colour Information section of this document. The calculation of the separation radar states shall be obtained as function of: PSI-7014 The operative state of the adapted radar for the dependency The main radars of the Dependency
If it is a remote dependency, this will receive surveillance information from the TDVM server or not. The following radar quality levels shall be considered: Nominal: When one of the main radars of the Dependency is operative. Degraded: When none of the main radars of the Dependency is operative and some secondary radar remains operative. Not applicable: When none of the radars of the Dependency is operative. The label of the Separation Radar element from the PSI/PST will be: Text "Separation Radar" and below the name of the dependency. "RADAR SEPARATION" "Dependency_Name" PSI-1664
The RADAR QUALITY element shall use the following legend: "Radar PSI-1634 Separation [Dependency name]. The following text will be included in the Radar Separation PSI's label with the purpose of indicating the source where it is obtained the Radar Separation state or the Mode of Tracking Operation in the PSI from CCV with TDVT . This text will follow "Radar Separation": Normal Mode: "Normal" Local Mode: "Local"
For the rest of PSI (centres with TDVM and CCVs without TDVT) the Mode of 18 Software Requirements Description
Tracking Operation will always be "NORMAL". The following ERs corresponding to changes in the Radar_Separation level PSI-3565 shall be generated, through the service SrvMwER_Generate, without indicating the initial level: Change to Degraded: PSIrad003 SSTrad003 (Only Tower) Change to Not applicable: PSIrad004 SSTrad004 (Only Tower) Change to Nominal: PSIrad005 SSTrad005 (Only Tower)
In the menus and windows of functions from PSIs/PSTs of the Remote PSI-7019 Control Centres from which the configurations are done, the word "Local" shall be replaced by the word "Normal" in the name of the functions opened by the left button and that are not modifiable by profile, just as the name of the functions which are accessible from the menu bar and which are neither modifiable by profile: Radar Treatment Configuration EADR Statistics Techniques TDVM Function Configuration
The text of the functions in the containers (menu bar and contextual menu), PSI-7020 both first and second level ( if it applies) shall be configurable by profile.
The titles of the windows of the PSI functions which are indicated in this PSI-7021 requirement shall contain the same text that appear in the menu ( menu bar) from which are accessible. If the function is of second level, the title shall be a chain of the first level text with the text of second level ( both if it selected from the menu bar or if it this done form the element of the scenario-access from BDR-). Note: In the access from the BDR, the title of the window take as reference the existence of the first and second level in the menu bar. Radar Treatment Configuration Radar Input Configuration Monoradar EADR Statistics TDVM Statistics Systematic Radar Error Statistics Software Requirements Specification 19
Air Surveillance Delay Statistics Operatives TDVM Function Configuration Techniques TDVM Function Configuration
4.1.4.2.1.3. Radar Separation for En-route dependencies En-route radar separation element shall be displayed if the following PSI-9176 conditions are fulfilled: It is configured by profile of PSI. PSI is located in a dependency defined as En-route (adaptation data) except for the ones that has, at least, one main radar defined by adaptation. A#12845
En-route radar separation monitoring function will analyse two levels of radar PSI-9148 coverage: Theoretical Coverage (CT) available in the control area Double Theoretical Coverage (DTC) available in the control area
A#12845
Note: DTC is considered when there is overlapped coverage of, at least, two radars in all the Control Area.
PSI shall received, through the service PSI-9149 SrvAdapgv_EnRouteRadarCoverageDepen, a table with the sectors associations that fullfil the conditions necessary for TC and DTC.
A#12845
PSI shall obtain if an ACC is adapted or not through the service PSI-9150 SrvAdapgv_TopologyResources.
A#12845
PSI shall periodically received, through the event EvtSurvA_RadarStatus, PSI-9151 the state of the radars (Operative, Non operative).
A#12845
PSI shall analyze the coverage with the adaptation table and with the PSI-9153 information of the radars states to obtain what kind of radar coverage is being fullfil.
A#12845
PSI shall analyze CT and DTC when there is a change in a radar state.
PSI-9152
A#12845
20
PSI shall send to MwREC, through the event PSI-9156 EvtPsi_EnRouteRadarSeparation, any update of the coverage availability (TC or DTC) in the ACC.
A#12845
The following radar separation states shall be considered: Nominal: DTC for all sectors and ACC adapted to provide Reduced Separation or TC for all sectors and ACC NOT adapted to provide Reduced Separation Degraded: TC for all sectors and ACC adapted to provide Reduced Separation. Failure: At least one sector without single coverage Unknown: There is no information of this item since it started up. Initial transient state.
PSI-9154
A#12845
4.1.4.2.1.3.1.
Event Reports A#12845
In an ACC adapted to provide reduced separation, when a sector with TC PSI-9141 loses DTC, the following ER shall be generated: PSIrad006
In an ACC adapted to provide reduced separation, when a sector with TC PSI-9142 recovers DTC and there is, at least, another sector without DTC, the following ER shall be generated: PSIrad007
A#12845
In an ACC adapted to provide reduced separation, when all sector recover PSI-9143 TC, the following ER shall be generated: PSIrad008
A#12845
In an ACC adapted or NOT to provide reduced separation, when a sector PSI-9144 loses DTC, the following ER shall be generated: PSIrad009
A#12845
In an ACC adapted or NOT to provide reduced separation, when a sector PSI-9145 recovers TC and there is, at least, one sector without TC, the following ER Software Requirements Specification
A#12845 21
shall be generated: PSIrad010
In an ACC adapted to provide reduced separation, when all sector recover PSI-9146 DTC, the following ER shall be generated: PSIrad011
A#12845
In an ACC NOT adapted to provide reduced separation, when all sector PSI-9147 recover TC, the following ER shall be generated: PSIrad012
A#12845
4.1.4.2.1.4. CCTV Link A single link with TV Camera System shall be displayed in the link and system PSI-6529 information area from the main scenario of PST.
The state of CCTV link of the Operative processor shall be sent to the PST PSI-6530 for being displayed in those positions,using the usual mechanism of sending the state of devices/link from TCEH. The displaying of the CCTV element shall be configurable by profile. PSI-6531
The CCTV Link state shall be displayed through the Colours Code PSI-6532 corresponding to the Not Configurable Link colour table located in the Colour Information section of this document. The maximum number of CCTV configured systems shall be 1. PSI-6533
4.1.4.2.1.5. SCV Link The SCV (Voice Communication System) element display shall be PSI-2512 configurable.
The SCV Link state shall be displayed through the Colours Code PSI-2514 corresponding to the Not Configurable Link colour table located in the Colour Information section of this document. 22 Software Requirements Description
It shall be displayed as many 'ENLACE_SCV' elements as SCV systems are PSI-6237 configured.
The label which appear in the small box shall be configurable, it can be PSI-6238 different to 'SCV' to identify in a proper way which is the link with every of the SCV System. The maximum number of configured SCV shall be 5 for PST (PSI in tower PSI-6239 environment)
The maximum number of configured SCV shall be 1 for PSI ( RUTA/ATM Acc environment)
PSI-6240
4.1.4.2.1.6. System Current Version On clicking with the left button of the pointer device on the SACTA icon PSI-1647 current version information of the system, patches and current adaptation data of the PSI shall be accessed.
4.1.4.2.2.
Subsystems Area
The subsystems area shall cover the rest of the main scenario non utilised by PSI-1649 the links and system information areas.
The subsystems blocks that comprise the system shall be located in the PSI-1655 subsystems area, by representing them.
The access to the detailed scenarios of each subsystem and the label PSI-1656 displayed in the element which represents each of the subsystems, shall be fixed by the user profile which is executed in the PSI. The Subsystems state shall be displayed through the Colours Code PSI-1654 corresponding to the Subsystems colour table located in the Colour Information section of this document. NOTE: A subsystems block is considered as: "Completely Operative". In case the operation capacity of the subsystem is complete. "Partially Operative". In case the operation capacity of the subsystem is not complete, nevertheless it provides the required functionality. "Non Operative". In case the operation capacity of the subsystem is not complete and it does not provide the required functionality. "Unknown". When the subsystem is not processing data. 23
*The elements states of a subsystem which are not considered for assessing the global operative state of the subsystem are depicted in the appendix. The subsystems area shall be divided in four quadrants, allowing to group the PSI-1661 subsystems into environments as listed below:
Central Environmental Subsystems shall be located in the inferior left PSI-1650 hand quadrant group the following subsystems: GIPV Scenario and TCPV Scenario . Local Environment Subsystem's shall be located in the upper left PSI-1663 hand quadrant group the following subsystems: GSI Scenario, SILV Scenario, SPV Scenario, SIS Scenario, TLPV Scenario, TDVM Scenario, EADR Scenario and SMDT Scenario. CWP Subsystems shall be located in the upper right hand quadrant PSI-1662 group the following subsystems: EN-ROUTE SS scenario, REM SS Scenario, TMA1 SS Scenario and TWR Scenario. Dynamic Simulation Subsystems shall be located in the inferior right PSI-4112 hand quadrant. Subsystem States in the Main Scenario Within the attached tables, the information associated to each scenario is described, indicating the states that the elements may potentially reach as well as the attributes identifying each state. In order to understand the following tables it is necessary to take into account: To look up States Tables. To look up the Elements Tables.
The State columns content are rules of the corresponding subsystem. Each line or sentence is a rule and the relation among rules is always a logical OR.
The rules will be described in the following way (the angles are used only to separate the fields): <Quantity><Elements Type><State> o Quantity. Elements Number. o Component Type. It indicates the type of element, such as CLAN (See component table). The character U can be used as prefix. It identifies a single unit of the tandem component. For instance: UGSI, USILV, USIS, UTCPV, UTDVM, UTLP and more. o State. It indicates the condition that component is in. For Instance: 0 USIS R. It means, Zero Units of the GSI tandem in Stand by. <Description>. It provides details about what something is like For Instance: All Not Sectorized SS to F. It means, All not sectorized SS to failure The Main Scenario Subsystem States Tables are the ones listed below: PSI-6942 See next table.
24
Main Scenario Subsystem Partially operational (Yellow) if Time System Lost of Redundancy: 1 NTPserver F or without tracking State Not operational (Red) if 0 NTPserver O or with tracking
Table 4.1.4.2.1.3.1-18 : Time System PSI-6929 See next table.
Main Scenario Subsystem Partially operational (Yellow) if External System SCV N/A State Not operational (Red) if SCV Link NC
Table 4.1.4.2.1.3.1-19 : External SCV System PSI-6930 See next table.
Main Scenario Subsystem Partially operational (Yellow) if External System CCTV N/A State Not operational (Red) if Every CCTV manager NC
Table 4.1.4.2.1.3.1-20 : External CCTV System PSI-6943 See next table.
Main Scenario Subsystem State
25
Main Scenario Partially operational (Yellow) if Radar (TMA) Not operational (Red) if Separation No Dependency radar to operative, and some No Dependency radar operative non-main radar operative
Table 4.1.4.2.1.3.1-21 : Radar Separation System for TMA dependencies PSI-9122 See next table. A#12845
Main Scenario Subsystem Partially operational (Yellow) if State Not operational (Red) if
Radar Separation At least one sector without double coverage At least one sector without simple coverage (En-route) but all sectors with simple coverage (ACC adapted to provide Reduce Separation)
Table 4.1.4.2.1.3.1-22 : Radar Separation System for En-route dependencies PSI-6928 See next table.
Main Scenario Subsystem Partially operational (Yellow) if GIPV Lost of redundancy: 1 CLAN F 0 GIPV R 1 Synchronizer NSZ Partial functionality: 1 SIST_EXT H and (NC or SD) Note: The links which has been for a long time with SD or NC state could be disable (NH) to avoid any impact in the general state of the sub-system. State Not operational (Red) if 0 GIPV O
Table 4.1.4.2.1.3.1-23 : GPIV Subsystem
26
PSI-6939 See next table.
Main Scenario Subsystem Partially operational (Yellow) if TCPV Redundancy lost: State Not operational (Red) if 0 TCPV O
0 TCPV R
1 PDV F 1 CLAN F 1 Synchronizer NSZ Partially functional: 0 PDVs D 1 AFTN H and (NC or SD) 1 ENL_TLPV H and (NC or SD) Note: The links which has been for a long time with SD or NC state could be disable (NH) to avoid any impact in the general state of the sub-system.
Table 4.1.4.2.1.3.1-24 : TCPV Subsystem PSI-6931 See next table.
Main Scenario Subsystem Partially operational (yellow) if GSI Lost of redundancy: 0 GSI R 1 CLAN F 1 Synchronizer NSZ Partial functionality: 0 DG D 1 ND or SD tape State Not operational (Red) if 0 GSI O
27
Table 4.1.4.2.1.3.1-25 : GSI Subsystem PSI-6935 See next table.
Main Scenario Subsystem Partially operational (Yellow) if SILV Redundancy lost: State Not operational (Red) if 0 SILV O SICV_MET H and (NC or SICV-AIS H and (NC or
0 SILV R 1 CLAN F 1 Synchronizer NSZ Partially functional:
SD) SD)
1 SMI H and (NC or SD) 1 ATIS H and (NC or SD) SICV_MET H and (NC or
SD)
SICV-AIS H and (NC or SD) Note: The links which has been for a long time with SD or NC state could be disable (NH) to avoid any impact in the general state of the sub-system
Table 4.1.4.2.1.3.1-26 : SILV Subsystem PSI-6938 See next table.
Main Scenario Subsystem Partially operational (Yellow) if SPV Redundancy lost: 1 PSI F 1 PSI CLAN F 1 Synchronizer NSZ State Not operational (Red) if 0 PSI D in the Operation Room (if it had been defined) 0 PSI D in the Equipment Room (if it had been defined) Some basic function is missing Note: There are TWR with only 1 PSI, and it should not be displayed the box for that subsystem like ND when it is only available this PSI.
28
Table 4.1.4.2.1.3.1-27 : SPV Subsystem PSI-6937 See next table.
Main Scenario Subsystem Partially operational (Yellow) if SMDT Redundancy lost: State Not operational (Red) if 0 SMDT O 1 ENL_TLPV_REM H and (NC or SD) in TWR with TPVT. 0 Multilateral and Surface Radars (SMM+SMR) H and C
0 SMDT R 1 CLAN F 1 Synchronizer NSZ Partially functional:
1 ENL_SILV_REM NC or SD
N of (SMM+SMR) H and C 50% Note : The link with SILV is not configurable
Table 4.1.4.2.1.3.1-28 : SMDT Subsystem PSI-6936 See next table.
Main Scenario Subsystem Partially operational (Yellow) if SIS Redundancy lost: State Not operational (Red) if 0 SIS O
0 SILV R 1 CLAN F 1 Synchronizer NSZ Partially functional:
1 SIS_EXT_SIS H and (NC or SD) Note: The links which has been for a long time with SD or NC state could be disable (NH) to avoid any impact in the general state of the sub-system.
29
Table 4.1.4.2.1.3.1-29 : SIS Subsystem PSI-6941 See next table.
Main Scenario Subsystem Partially operational ( Yellow) if TLPV Redundancy lost: State Not operational (Red) if 0 TLPV O
0 TLPV R 1 CLAN F 1 Synchronizer NSZ Partially functional: 0 S_PIVLs D 1 ENL_TCPV H and (NC or SD) 1 COL_NAC H and (NC or SD) 1 COL_EXT H and (NC or SD) Note: The links which has been for a long time with SD or NC state could be disable (NH) to avoid any impact in the general state of the sub-system.
Table 4.1.4.2.1.3.1-30 : TLPV Subsystem PSI-6940 See next table.
Main Scenario Subsystem Partially operational (Yellow) if TDVM Redundancy lost: State Not operational (Red) if
0 TDVM R 0 UAST R
1 UDDE F 1 CLAN F 1 Synchronizer NSZ Partially functional:
0 TDVM O 0 UAST O Number of radars (DDE+AST) H and C 50%
30
Main Scenario 0 UDDEs D Number of radars (DDE+AST) H and C 75%
Table 4.1.4.2.1.3.1-31 : TDVM Subsystem PSI-6927 See next table.
Main Scenario Subsystem Partially operational (Yellow) if EADR Centres with UAST: Redundancy lost: 1 UDDE F 1 CLAN F 0 UAST R 1 Synchronizer NSZ Partial functionality: State Not operational (Red) if Centres with UAST: 0 UAST R
Number of radars (DDE+AST) H and C 50 %
0 UDDE O
ENL_TDVM_REM H y (NC o SD) in remote dependency without SMDT (TWRs without SDMT or TACC Valencia). Number of radars (DDE+AST) H and C 75 % Note: The links which has been for a long time with SD or NC state could be disable (NH) to avoid any impact in the general state of the sub-system. Note: If there are not UDDEs defined the conditions referring to those processors will not be taken in account. TWR without UAST: N/A TWR without UAST:
ENL_TDVM H y NC
Note: In this scenario only appear the remote links with the TDVM. The subsystem shall be SD when the link is also like that.
31
Table 4.1.4.2.1.3.1-32 : EADR Subsystem PSI-6933 See next table.
Main Scenario Subsystem Partially operational (Yellow) if TMA SS or En-Route SS Redundancy lost: 0 POS D for all the Non sectorized SS (this is like saying that there are not any available stand-by SS). 1 POS F 1 IFV F 1 IFV DG in a sectorized SS 1 PTC F 1 RE F 1 CLAN F 1 Synchronizer NSZ Note: The IFV is a device with the possibility of Physical Configuration what means that for a non sectorized SS the state could be manually changed from F to ND for not impacting in the general state of the subsystem. State Not operational (Red) if POS_A D and POS_B D in sectorized UCS. POS_A MA and POS_B MA in sectorized SS. NOTE: D could mean the following states: ND, F or SD.
Table 4.1.4.2.1.3.1-33 : TMA SS or EN-ROUTE SS Subsystem PSI-6932 See next table.
Main Scenario Subsystem Partially operational (yellow) if REM SS Redundancy lost: 1 PCV F 1 CLAN F 1 Synchronizer NSZ NOTE: D could mean the following states: ND, F or SD. Partial functionality: State Not operational (Red) if
1 PCV F for sectorized REM_LOGICA
32
Main Scenario 1 IFV for sectorized REM_LOGICA and without TPVT. NOTE: The IFV is a device which allows the Physical Configuration, it means that for non sectorized towers the state could be manually changed from F to ND for not impact in the general state of the subsystem. This does not apply for the sectorized towers which are not 24 H and that by night switch off its printers (it will be like F).
Table 4.1.4.2.1.3.1-34 : REM SS Subsystem PSI-6934 See next table.
Main Scenario Subsystem Partially operational (yellow) if APP/TWR TWRs with TPVT: Redundancy lost: 0 Non sectorized POS O ( it means that there are not stand-by POS available) 1 IFV F 1 CLAN F 1 Synchronizer NSZ Note: The IFV is a device with the possibility of Physical Configuration what means that for a non sectorized UCS the state could be manually changed from F to ND for not impacting in the general state of the subsystem. TWRs without TPVT: Redundancy lost: 1 POS F 1 CLAN F 1 Synchronizer NSZ Note: IFV only will be displayed from PSI of ACC associated so that the POS_TOR scenario does not appear in the tower PSI. TWRs without TPVT: 0 POS D for a particular Dependency (TWR or APP) State Not operational (Red) if TWRs with TPVT: 1 sectorized POS D NOTE: D could mean the following states: ND, F or SD.
Table 4.1.4.2.1.3.1-35 : TWR Subsystem Software Requirements Specification 33
If in a subsystem every processor are SD then the colour of the subsystem in PSI-6946 the main scenario of PSI shall be also like SD, in spite of having devices or links with another different state. An example of the previous requirement: in the SMDT scenario the tandem also can be SD but the links with TLPV and the SILV can be C because that is directly monitorized by the PSI. 4.1.4.2.3. Alarms Area PSI-8461
This area shall be located in the top right part of the Central area.
Any element monitored by the PSI, which switches to failure state shall PSI-7142 generate an alarm which will be indicated with a red rectangle located on the top right side of the Central Zone delimiting the word Alarm and producing a beep. The acknowledge of and alarm shall be performed by locating the cursor PSI-7143 inside the Alarms Indicator zone. For each acknowledged alarm an informative window of the failure which has caused this alarm, will be displayed. The scenario where the element in failure is monitored shall be accessed PSI-1586 from the recognized alarm.
An alarm shall only be showed if the previous alarm has been acknowledged.
PSI-7145
An alarm shall not be considered as acknowledged unless it goes out the PSI-7146 Alarm window.
The alarms configuration shall be defined by the user profile.
PSI-7147
If so, it could shall defined if these alarms presentation is conditioned to the PSI-1589 presence of another user profile which is in execution of the system.
For profiles thus configured, every alarm shall cause an acoustic alarm which PSI-3563 will end when it is acknowledged or the element in failure state has been automatically recovered.
PSI shall have sound devices associated with the aim of generating acoustic PSI-5910 alarms.
34
The way of PSI for generating acoustics alarms shall be configure between: CPU Baffle Sound card
PSI-5911
The configuration file shall be fs_gen_def_entorno.local, through the context variable. The variable shall have one of the following values: SALIDA_AUDIO_ALARMA = ALTAVOZ_CPU SALIDA_AUDIO_ALARMA= TARJETA_SONIDO PSI-5915
The default value of the variable shall be: SALIDA_AUDIO_ALARMA = ALTAVOZ_CPU
A configuration file in version control c_psi_alarma.a which contains the PSI-5916 audible sound shall exist. The file format shall be AU ( sound file format of 8 bits of SUN), that sound shall be like 'alarm whistle'
4.1.4.3. LOWER AREA The Lower Area shall be located in the lower part of the monitor image. PSI-8445
Menus Bar: In the PSI it is available the only horizontal bar of menu which PSI-7101 compose the "Functions Bar". In the horizontal menus, the different operations to be performed shall be displayed grouped by containers. The number and names of the containers and its functions are configurable PSI-8967 by using the user profile.
There shall be a function included in the Menu Bar to let the user to exit the PSI-7079 application returning to the login window. Selecting a Function A container selection drops-down a vertical menu where the different PSI-7102 functions grouped under that container shall be displayed.
A function selection shall display an edition window which will guide us in its PSI-7103 execution, or a new vertical menu where the different existing sub-functions are displayed. A sub-function selection shall display an edition window which will guide us in PSI-7104 its execution.
35
4.1.5.
SCENARIOS NAVIGATION
For monitoring purposes, the system will be considered as comprised by a set of HW components. The state of the different system components will be shown by the corresponding graphic scenarios, gathered by functional areas. The scenarios will be structured in two levels; the first level will show the system general areas while the second level will show the components corresponding to these areas. The state of the different components will be shown through the corresponding attributes. Concepts: HW Component: A HW component will be a group of HW elements, considered for supervision purposes as a unit that will allow their state knowledge (for example, the LAN Controller component will include the LAN controller, the transceiver and the drop cable). Component Types, States and Attributes Table: For each type of component, the possible states they can assume are attributed to them, as well as the way in which the different states where they will be represented in the scenarios. Scenarios, Components and Types Table: The contents of the different scenarios will be described, as well as the components assigned to each area. The components will be classified in global types. States Transition Table: For each type of component, the potential causes of the state transitions will be described, making reference to the functions that will be described in the corresponding sections. A detailed monitoring of the external elements of the followings scenarios will be performed: TDVM with the aim of states radar presentation as well as their lines display. TLPV with the aim of presentation of the communication with the adjacent centres (national and international) and TLPV links. TCPV with the aim of presentation of the AFTN communication and TLPV links. SILV with the aim of the SMI and ATIS communication. GIPV with the aim of external users. SIS with the aim of external systems. SMDT with the aim of presentation of the link with TDVM, SILV and TLPV. EADR with the aim of states radar input data. PSI-7130
The scenarios navigation shall be performed in the Central Zone.
The state of the different subsystems and elements which compose them PSI-1621 shall be represented by means of a colours code. More details in the Colours and States section. The scenarios navigation shall be structured in two levels. PSI-7131
The first level shall display global information of the system. It will be called PSI-7132 Subsystem Area of the Main Scenario.
The first level shall be the level by default, and it will be accessed after the PSI-7133 access to the PSI authorization . 36 Software Requirements Description
The second level shall show detailed information of a certain scenario. It will PSI-7134 display the components which it integrates providing state information and management information. More details in section of scenarios description. It shall exist a main scenario which will display global information of the PSI-3558 system.
The second level scenarios shall be accessible by means of any of the PSI-1616 following ways:
It shall be accessible by clicking on the element of Subsystem Area of PSI-1615 the Main Scenario with left button of the pointer device, which represents the subsystem where we desire to access in the scenario of second level . It shall be accessible by means of the execution of some of the PSI-1617 functions concerning to an element included in this scenario. It shall be accessible by means of the acknowledgement of an alert PSI-1614 which involves some monitored element from that scenario. We shall return to the Subsystem Area of the Main Scenario by clicking with PSI-1618 the left button of the pointer device on the background of the second level scenarios. An emergent menu shall be dropped down after clicking with the right button PSI-1619 of the pointer device on some of the elements displayed on the scenario, giving access to the functionalities to be indicated in the corresponding sections. The emergent menu mentioned above shall only be displayed in case that the PSI-1620 corresponding user profile was configured to be able to do it.
The scenarios composition, for those units whose composition can be PSI-3559 variable, shall be determined by adaptation data. It shall also be determined by configuration (as for the UCSs with or without a slave clock).
The information shall be updated with the HW units real state, in all time.
PSI-3560
Browsing the scenarios structure shall be performed either by operator PSI-3561 requests or by the occurrence of failures causing the automatic display when alarms are acknowledged.
37
4.1.6.
SECOND LEVEL SCENARIOS
4.1.6.1. GIPV Scenario The GIPV scenario shall represent the HW and SW elements of the GPIV PSI-6132 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The GIPV scenario elements are the following ones: See next table.
GIPV Scenario Components

GIPV US-VLAN controller C-VLAN controller PIVC C-VLAN controller External Users Control VLAN (C-VLAN) Users VLAN (US-VLAN) Synchronizer
Type
Tandem Processor Not Monitorized Device Not Configurable Device Working Control Processor Not Configurable Device Configurable Link --Specialized Device
Max. Number of Elements

1 Tandem 1 per GIPV processor 2 per GIPV processor 3 2 per PIVC 15 2 1 1 per processor
Remarks
2 processors
1 per C-VLAN
1 per C-VLAN Connected to US-VLAN
Table 4.1.6.1-36 : GIPV scenario elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. 4.1.6.1.1. Accessible functionalities through drop-down menus
Each element (block) shall be associated with certain functionalities which PSI-1694 could be accessible after having configured the user profile.
A menu with the configured functionalities shall be displayed on clicking with PSI-1732 the right button of the pointer device on some of the elements (blocks) of the GIPV scenario, The distribution and grouping of desired functions is commented in the following sections. Later, the meaning of these functions will be described with detail. 38 Software Requirements Description
4.1.6.1.1.1. [Tandem switchover] On locating with the pointer device on the GIPV block and clicking on the RB, PSI-1715 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.1.1.2. [UGIPV Start-up Shutdown] On locating with the pointer device on the UGIPV block and clicking on the PSI-1716 RB, the associated functionalities menu where [UGIPV Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-1717 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-1718 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-1719 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up Stand by PSI-1720 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown Stand by PSI-1721 screen of the subsystem shall be displayed.
4.1.6.1.1.3. [Monitoring Start-up] On locating with the pointer device on the GIPV block and clicking on the RB, PSI-1722 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.1.1.4. [GIPV Statistics] On locating with the pointer device on the GIPV block and clicking on the RB, PSI-1723 the associated functionalities menu where [GIPV Statistics] could be selected, shall be displayed
4.1.6.1.1.5. [Processor Statistics] On locating with the pointer device on the GIPV block and clicking on the RB, PSI-1724 the associated functionalities menu where [Processor Statistics] could be Software Requirements Specification 39
selected, shall be displayed
4.1.6.1.1.6. [GIPV Configuration] On locating with the pointer device on the GIPV block and clicking on the RB, PSI-1725 the associated functionalities menu where [GIPV Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options On selecting the option [Keep FPs filters] the Keep FPs filters screen PSI-1726 shall be displayed. On selecting the option [Keep FPs formats] the Keep FPs formats PSI-1727 screen shall be displayed. On selecting the option [Configure Sending] the Configure Sending PSI-1728 screen shall be displayed. On selecting the option [Select Messages] the Select Messages PSI-1729 screen shall be displayed. On selecting the option [Configure External Systems] the Configure PSI-1730 External Systems screen shall be displayed.
4.1.6.1.1.7. [Enabling of External Systems] On locating with the pointer device on the EXTERNAL SYSTEM PSI-1731 (USU_EXTERNOS) block and clicking on the RB, the associated functionalities menu where [Enabling of External Systems] could be selected, shall be displayed
4.1.6.2. TCPV Scenario The TCPV scenario shall represent the HW and SW elements of the TCPV PSI-6133 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The TCPV scenario elements are the following ones: See next table.
40
TCPV Scenario Components

TCPV C-VLAN Controller PDV C-VLAN Controller IPDV
Type
Tandem Processor Not Configurable Device Working Control Processor Not Configurable Device Not Configurable Device

1 Tandem 2 per TCPV processor 6 2 per PDV 3 1 per IPDV 2 4 2 1 per processor
Remarks
2 processors 1 per C-VLAN Included M10 and CIC 1 per C-VLAN
IPDV C-VLAN Not Monitorized Device controller AFTN Lines TLPV Link Control VLAN (C-VLAN) Synchronizer Configurable Link Configurable Link -Specialized Device
Connected to C-VLAN
Table 4.1.6.2-37 : TCPV scenario elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. 4.1.6.2.1. Accessible functionalities through drop-down menus
Each element (block) shall be associated with certain functionalities which will PSI-1743 be able to be accessible after having configured the user profile.
On clicking the right button of the pointer device on some of the elements PSI-1744 (blocks) the TCPV scenario, a menu with the configured functionalities shall be dropped-down. The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described. 4.1.6.2.1.1. [Tandem Switchover] On locating with the pointer device on the TCPV block and clicking on the RB, PSI-1747 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
41
4.1.6.2.1.2. [UTCPV Start-up Shutdown] On locating with the pointer device on the UTCPV block and clicking on the PSI-1749 RB, the associated functionalities menu where [UTCPV Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-1751 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-1753 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-1755 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up stand by PSI-1757 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-1759 screen of the subsystem shall be displayed.
4.1.6.2.1.3. [Monitoring Start-up] On locating with the pointer device on the TCPV block and clicking on the RB, PSI-1761 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.2.1.4. [TCPV Statistics] On locating with the pointer device on the TCPV block and clicking on the RB, PSI-1763 the associated functionalities menu where [TCPV Statistics] could be selected, shall be displayed
4.1.6.2.1.5. [Processor Statistics] On locating with the pointer device on the TCPV block and clicking on the RB, PSI-1765 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed On locating with the pointer device on the PDV block and clicking on the RB, PSI-2559 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
42
4.1.6.2.1.6. [Printers Statistics] On locating with the pointer device on the IPDV block and clicking on the RB, PSI-2108 the associated functionalities menu where [Printers Statistics] could be selected, shall be displayed On locating with the pointer device on the IPDVG block and clicking on the PSI-2560 RB, the associated functionalities menu where [Printers Statistics] could be selected, shall be displayed
4.1.6.2.1.7. [AFTN Lines Configuration] On locating with the pointer device on the AFTN Lines block and clicking on PSI-2110 the RB, the associated functionalities menu where [AFTN Lines Configuration] could be selected, shall be displayed.
4.1.6.2.1.8. [Links Configuration] On locating with the pointer device on the TLPVs LINKS block and clicking on PSI-1779 the RB, the associated functionalities menu where [Links Configuration] could be selected, shall be displayed.
4.1.6.3. GSI Scenario The GSI scenario shall represent the HW and SW elements of the GSI PSI-6134 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The GSI scenario elements are the following ones: See next table.
43
GSI Scenario Components

GSI C-VLAN controller R-VLAN controller FAILOVER-VLAN controller US-VLAN controller Tapes DG unit Control VLAN C-VLAN Radar VLAN R-VLAN Failover VLAN FAILOVER-VLAN Users VLAN US-VLAN Synchronizer
Type
Tandem Processor Not Configurable Device Not Configurable Device Not Monitorized Device Not Monitorized Device Configurable Device Configurable Device ----Specialized Device

1 Tandem 2 per GSI processor 2 per GSI processor 1 per GSI processor 1 per GSI processor 2 1 2 2 1 1 1 per processor
Remarks
2 processors 1 per C-VLAN (No TWR) 1 per R-VLAN
(No TWR)
Table 4.1.6.3-38 : GSI scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. In the DG Recorder Device the number of tape shall be indicated. PSI-2114
4.1.6.3.1.
Accessible functionalities through drop-down menus
A menu with the configured functionalities shall be displayed.on clicking with PSI-1974 the right button of the pointer device on some of the elements (blocks) of the GSI scenario, The distribution and grouping of desired functions is commented in the following sections. Later, the meaning of these functions will be described with detail.
44
4.1.6.3.1.1. [Physical Configuration] On locating with the pointer device on the A or B block and clicking on the RB, PSI-2119 the associated functionalities menu where [Physical Configuration] could be selected, shall be displayed
4.1.6.3.1.2. [Tape Information Recovering] On locating with the pointer device on the A or B block and clicking on the RB, PSI-2117 the associated functionalities menu where [Tape Information Recovering] could be selected, shall be displayed
4.1.6.3.1.3. [Tandem switchover] On locating with the pointer device on the GSI block and clicking on the RB, PSI-1977 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.3.1.4. [UGSI Start-up Shutdown] On locating with the pointer device on the GSI block and clicking on the RB, PSI-1979 the associated functionalities menu where [UGSI Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-1981 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-1983 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-1985 screen of the subsystem shall be displayed On selecting the option [Stand by Start-up], the Start-up stand by PSI-1987 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-1989 screen of the subsystem shall be displayed
4.1.6.3.1.5. [Monitoring Start-up] On locating with the pointer device on the GSI block and clicking on the RB, PSI-1991 the associated functionalities menu where [Monitoring Start-up] could be Software Requirements Specification 45
4.1.6.3.1.6. [GSI Statistics] On locating with the pointer device on the GSI block and clicking on the RB, PSI-1993 the associated functionalities menu where [GSI Statistics] could be selected, shall be displayed
4.1.6.3.1.7. [Processor Statistics] On locating with the pointer device on the GSI block and clicking on the RB, PSI-1995 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.3.1.8. [GSI Configuration] On locating with the pointer device on the GSI block and clicking on the RB, PSI-1997 the associated functionalities menu where [GSI Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options On selecting the option [Users Conf.] the Users Configuration screen PSI-1999 shall be displayed On selecting the option [Information to be Recorded Conf.] the PSI-2001 Information to be Recorded Configuration screen shall be displayed. On selecting the option [Recording Enable/Disable] the Information to PSI-2003 be Recording Enable/Disable screen shall be displayed.
4.1.6.4. SILV Scenario The SILV scenario shall represent the HW and SW elements of the SILV PSI-4454 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The SILV scenario elements are the following ones: See next table.
46
SILV Scenario Components

SILV C-VLAN controllers Link with ICARO MET Link with ICARO AIS SMI Lines ATIS Lines Control VLAN C-VLAN Synchronizer
Type
Tandem Processor Non Configurable Device Configurable Link Configurable Link Configurable Link Configurable Link -Specialized Device

1 Tandem 2 per SILV processor 1 1 32 32 1 --
Remarks
2 processors 1 per C-VLAN Connected to C-VLAN Connected to C-VLAN Connected to C-VLAN Connected to C-VLAN
1 per processor
Table 4.1.6.4-39 : SILV scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. SMI and ATIS lines shall be displayed gathered in a 8 rows X 4 columns for PSI-5081 every kind of SMI and ATIS, respectively.
4.1.6.4.1.
On clicking the right button of the pointer device on some of the elements PSI-2125 (blocks) the SILV scenario, a menu with the configured functionalities shall be dropped-down. The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described 4.1.6.4.1.1. [Tandem Switchover] On locating with the pointer device on the SILV block and clicking on the RB, PSI-2128 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
47
4.1.6.4.1.2. [USILV Start-up Shutdown] On locating with the pointer device on the USILV block and clicking on the PSI-2130 RB, the associated functionalities menu where [USILV Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-2132 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-2134 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-2136 screen of the subsystem shall be displayed On selecting the option [Stand by Start-up], the Start-up stand by PSI-2138 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-2140 screen of the subsystem shall be displayed.
4.1.6.4.1.3. [Monitoring Start-up] On locating with the pointer device on the SILV block and clicking on the RB, PSI-2142 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.4.1.4. [Processor Statistics] On locating with the pointer device on the SILV block and clicking on the RB, PSI-2144 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.4.1.5. [Physical Configuration] On locating with the pointer device on the SMI elements the associated PSI-5913 functionalities menu where [SMI/ATIS Statistics] could be selected, shall be displayed On locating with the pointer device on the ATIS elements the associated PSI-5919 functionalities menu where [Link line] could be selected, shall be displayed.
48
On locating with the pointer device on the ATIS elements the associated PSI-5920 functionalities menu where [SMI/ATIS Statistics] could be selected, shall be displayed
4.1.6.5. SPV Scenario The SPV scenario shall represent the HW and SW elements of the PSI-6135 Supervision subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The SPV scenario elements are the following ones: See next table.
SPV Scenario Components

PSI R-VLAN controller
Type
Working Control Processor Not Configurable Device 8
Remarks
2 per PSI 2 per PSI 1 1 per PSA 2 per UCS 1 per UCS 2 per PSA 2 per CWP 1 per CWP 2 per PSA 1 per PTC 1 per SS 6 1 per IG 2 2 1 per processor
1 per R-VLAN 1 per CVLAN (No TWR) (No TWR)
C-VLAN Controller Not Configurable Device Non-Sectorisable Suite -(PSA) UCS C-VLAN controller I-VLAN controller CWP R-VLAN controller I-VLAN controller PTC I-VLAN controller Internal LAN (I-VLAN) IG Not Configurable Device Not Configurable Device Not Configurable Device Working Control Processor Not Configurable Device Not Configurable Device Not Configurable Device Not Monitorized Device -Not Configurable Device IG C-VLAN Not Monitorized Device controller Control VLAN C-VLAN Radar VLAN R-VLAN Synchronizer --Specialized Device
1 per CVLAN 1 per I-VLAN CWP A, CWP B 1 per RVLAN 1 per I-VLAN
1 per I-VLAN It connects both CWPs, the UCS and the PTC
(No TWR)
49
Table 4.1.6.5-40 : SPV scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. Within each available PSI the user profile which is being executed shall be PSI-2147 indicated in a frame.
4.1.6.5.1.
On clicking the right button of the pointer device on some of the elements PSI-1882 (blocks) the SPV scenario, a menu with the configured functionalities shall be dropped-down. The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described. 4.1.6.5.1.1. [Processor Statistics] On locating with the pointer device on the PSI block and clicking on the RB, PSI-2153 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed On locating with the pointer device on the CWP A/B block and clicking on the PSI-2555 RB, the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed On locating with the pointer device on the UCS Processor block and clicking PSI-2554 on the RB, the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.5.1.2. [Printers Statistics] On locating with the pointer device on the LP block and clicking on the RB, PSI-2151 the associated functionalities menu where [Printers Statistics] could be selected, shall be displayed
4.1.6.5.1.3. [CWP A/B Start-up Shutdown] On locating with the pointer device on the CWP A/B block and clicking on the PSI-1887 RB, the associated functionalities menu where [CWP A/B Start-up Shutdown] 50 Software Requirements Description
could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Computer Start-up], the start-up screen of PSI-1889 the EN-ROUTE, REM and TMA1 positions shall be displayed. On selecting the option [Computer Shutdown], the stop screen of the PSI-1893 EN-ROUTE, REM and TMA1 positions shall be displayed.
4.1.6.5.1.4. [Monitoring Start-up] On locating with the pointer device on the CWP A/B block and clicking on the PSI-1899 RB, the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed On locating with the pointer device on the UCS Processor block and clicking PSI-2557 on the RB, the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.5.1.5. [PSA UCS Start-up Shutdown] On locating with the pointer device on the UCS Processor block and clicking PSI-2155 on the RB, the associated functionalities menu where [PSA UCS Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Computer Start-up], the start-up screen of PSI-2157 the PSSE / PSSO UCS (PSA SS) shall be displayed. On selecting the option [Computer Shutdown], the stop screen of the PSI-2159 PSSE / PSSO UCS (PSA SS) shall be displayed.
4.1.6.5.2.
Display Radar Information
Optionally, the radar information display shall be done on the radar PSI-3510 information screen of a position associated to the PSI. The display shall have the same appearance and contents than the one corresponding to a controlling working position. It shall not be possible to sectorize the mentioned position nor it will allow to interact with the system. For the correct visualization of the degraded radar modes for Approach, the PSI-3512 PSI must fulfill the following requirements: It shall receive and process the radar operational capability event from the UDDE or UAST. Software Requirements Specification 51
4.1.6.6. SMDT Scenario The SMDT label placed in the main scenario shall allow access to the detail PSI-4455 scenario SMDT, keeping the other characteristics. Page's callsign for this subsystem will be P_SMDT.
The access to the detailed scenarios of each subsystem and the label PSI-4457 displayed in the element which represents each of the subsystems shall be fixed by the user profile which is executed in the PSI. The SMDT scenario shall represent the HW and SW elements of the SMDT PSI-6136 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The SMDT scenario elements are the following ones: See next table.
SMDT Scenario Components

SMDT R-VLAN controller VMS-VLAN controller SMR SMM TECAMS RTR RANC Tower TDVM Link SILV Link TLPV Link VMS VLAN VMS-VLAN Radar VLAN R-VLAN Synchronizer
Type
Tandem Processor Not Configurable Device Not Monitorized Device Configurable Radar Link Configurable RadarLink Configurable Radar Link Not Configurable Device Not Configurable Device Configurable Device Configurable Link Not Configurable Link Configurable Link --Specialized Device

1 Tandem 2 per SMDT processor 2 per SMDT processor 2 2 1 2 per TECAM 4 per TECAM 2 per TECAM 1 1 1 2 2 1 per processor
Remarks
2 processors 1 per R-VLAN 1 per VMS-VLAN Connected to VMS-VLAN Connected to VMS-VLAN Connected to R-VLAN
Connected to R-VLAN Connected to R-VLAN Connected to R-VLAN
52
Table 4.1.6.6-41 : SMDT scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. The VMS-VLAN controllers statistics shall not be available to be displayed. PSI-6536
If the VMS-VLAN controllers have no data flow, it shall not imply an automatic PSI-6537 processor shutdown. Possible SMDT Configurations: In the CCV's PSI with SMDT (TPVT+TDVT+SILVT), a second level PSI-5083 scenario with SMDT name, which shall contain its maximum configuration: SMDT Tandem and its CLANs TLPV_TOWER_LINK SILV_TOWER_LINK TDVM_REMOTE_LINK. Cat. 10 Sensors TECAMS
In the CCV's PSI with SMDT (TDVT+SILVT), a second level scenario PSI-5086 with SMDT name, which shall contain its maximum configuration: SMDT Tandem and its CLANs TLPV_TOWER_LINK SILV_TOWER_LINK TDVM_REMOTE_LINK. Cat. 10 Sensors TECAMS
4.1.6.6.1.
A menu with the configured functionalities shall be displayed on clicking with PSI-5964 the right button of the pointer device on some of the elements (blocks) of the SMDT scenario. The distribution and grouping of desired functions is commented in the following sections. Later, the meaning of these functions will be described with detail. Software Requirements Specification 53
4.1.6.6.1.1. Concerning to SMDT Servers 4.1.6.6.1.1.1. [Links Configuration]
On locating with the pointer device on the TLPV Link block and clicking on the PSI-5967 RB, the associated functionalities menu where [Links Configuration] could be selected, shall be displayed On locating with the pointer device on the TDVM Link block and clicking on PSI-5989 the RB, the associated functionalities menu where [Links Configuration] could be selected, shall be displayed
4.1.6.6.1.1.2.
[Tandem switchover]
On locating with the pointer device on the SMDT block and clicking on the PSI-5970 RB, the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.6.1.1.3.
[USMDT Start-up Shutdown]
On locating with the pointer device on the SMDT block and clicking on the PSI-5972 RB, the associated functionalities menu where [USMDT Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-5974 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-5976 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-5978 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up stand by PSI-5980 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown Stand by PSI-5982 screen of the subsystem shall be displayed.
4.1.6.6.1.1.4.
[Monitoring Start-up]
On locating with the pointer device on the SMDT block and clicking on the PSI-5984 RB, the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed 54 Software Requirements Description
4.1.6.6.1.1.5.
[SMDT Statistics]
On locating with the pointer device on the SMDT block and clicking on the PSI-5986 RB, the associated functionalities menu where [SMDT Statistics] could be selected, shall be displayed
4.1.6.6.1.1.6.
[Processor Statistics]
On locating with the pointer device on the GSI block and clicking on the RB, PSI-5988 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.6.1.2. Concerning to RDS servers 4.1.6.6.1.2.1. [Technical Vigilance Functions Configuration]
On locating with the pointer device on the SMDT block and clicking on the PSI-6026 RB, the associated functionalities menu where [Technical TDVM Functions Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options
On selecting the option [Autonomous TDVM] screen of the PSI-6028 Autonomous TDVM Functions Configuration shall be displayed.
4.1.6.6.1.2.2.
RDS Statistics
On locating with the pointer device on the GSI block and clicking on the RB, PSI-6030 the associated functionalities menu where [RDS Statistics] could be selected, shall be displayed
4.1.6.6.1.2.3.
[SMR Radar Entry Configuration]
On locating with the pointer device on the SMR radars block and clicking on PSI-4074 the RB, the associated functionalities menu shall be displayed, where [SMR Radar Entry Configuration] can be selected.
55
4.1.6.6.1.3. Concerning TPVT functionality 4.1.6.6.1.3.1. [TPVT Statistics]
On locating with the pointer device on the TPVT block and clicking on the RB, PSI-3956 the associated functionalities menu where [TPVT Statistics] could be selected, shall be displayed
4.1.6.7. SIS Scenario The SIS scenario shall represent the HW and SW elements of the SIS PSI-6137 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The SIS scenario elements are the following ones: See next table.
SIS Scenario Components

SIS C-VLAN controller US-VLAN controller External Users Control VLAN C-VLAN Users VLAN US-VLAN Synchronizer
Type
Tandem Processor Not Configurable Device Not Monitorized Device Configurable Link --Specialized Device

1 Tandem 2 per SIS processor 1 per SIS processor 8 2 1 1 per processor
Remarks
2 processors 1 per C-VLAN
Connected to US-VLAN
Table 4.1.6.7-42 : SIS scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. 4.1.6.7.1. Accessible functionalities through drop-down menus
On clicking the right button of the pointer device on some of the elements PSI-1836 (blocks) the SIS scenario, a menu with the configured functionalities shall be dropped-down. 56 Software Requirements Description
The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described. 4.1.6.7.1.1. [Tandem Switchover] On locating with the pointer device on the SIS block and clicking on the RB, PSI-1839 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.7.1.2. [USIS Start up-Shutdown] On locating with the pointer device on the SIS block and clicking on the RB, PSI-1841 the associated functionalities menu where [USIS Start up-Shutdown] could be selected, shall be displayed.
On selecting the option [Tandem Start-up] the tandem start-up screen PSI-1843 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-1845 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-1847 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up stand by PSI-1849 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-1851 screen of the subsystem shall be displayed.
4.1.6.7.1.3. [Monitoring Start-up] On locating with the pointer device on the SIS block and clicking on the RB, PSI-1853 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.7.1.4. [ DISPI Statistics] On locating with the pointer device on the SIS block and clicking on the RB, PSI-1855 the associated functionalities menu where [DISPI Statistics] could be selected, shall be displayed
57
4.1.6.7.1.5. [Processor Statistics] On locating with the pointer device on the SIS block and clicking on the RB, PSI-1857 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.7.1.6. [SIS Configuration] On locating with the pointer device on the SIS block and clicking on the RB, PSI-1859 the associated functionalities menu where [SIS Configuration] could be selected, shall be displayed
4.1.6.8. TLPV Scenario The TLPV scenario shall represent the HW and SW elements of the TLPV PSI-6138 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The TLPV scenario elements are the following ones: See next table.
TLPV Scenario Components

TLPV C-VLAN controller PIVL server C-VLAN controller IAMIS
Type
Tandem Processor Not Configurable Device Stand-Alone/Pool Processor Not Configurable Device Not Configurable Device

1 Tandem 2 per TLPV processor 1 2 per PIVL server 1 1 per IAMIS 1 12 12 1 2 1 per processor
Remarks
2 processors 1 per C-VLAN
1 per C-VLAN AMIS printer
IAMIS C-VLAN Not Monitorized Device controller UC Foreign Collateral Link National Collateral Link TCPV Link Control VLAN C-VLAN Synchronizer Not Monitorized Device Configurable Link Configurable Link Configurable Link -Specialized Device
Connected to TLPV processors Connected to UC Connected to C-VLAN
both
Table 4.1.6.8-43 : TLPV scenarios elements 58 Software Requirements Description
The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. The number of adjacent centres which appears in the scenario shall be an PSI-2230 adaptation datum.
The number of clients connected shall be indicated in the PIVL server.
PSI-2231
4.1.6.8.1.
On clicking the right button of the pointer device on some of the elements PSI-2202 (blocks) the TLPV scenario, a menu with the configured functionalities shall be dropped-down. The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described. 4.1.6.8.1.1. [Operative Configuration of Adjacent Centres] On locating with the pointer device on the FOREIGN ADJACENT CENTRES PSI-2239 or NATIONAL ADJACENT CENTRES block and clicking on the RB, the associated functionalities menu where [Operative Configuration of Adjacent Centres] could be selected, shall be displayed.
4.1.6.8.1.2. [Adjacent Centres Statistics] On locating with the pointer device on the FOREIGN ADJACENT CENTRES PSI-2243 or NATIONAL ADJACENT CENTRES block and clicking on the RB, the associated functionalities menu where [Adjacent Centres Statistics] could be selected, shall be displayed
4.1.6.8.1.3. [Links Configuration] On locating with the pointer device on the TCPV link block and clicking on the PSI-2237 RB, the associated functionalities menu where [Links Configuration] could be selected, shall be displayed.
4.1.6.8.1.4. [Printers Statistics] On locating with the pointer device on the IAMIS block and clicking on the RB, PSI-2235 the associated functionalities menu where [Printers Statistics] could be Software Requirements Specification 59
4.1.6.8.1.5. [Tandem Switchover] On locating with the pointer device on the TLPV block and clicking on the RB, PSI-2205 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.8.1.6. [UTLPV Start-up Shutdown] On locating with the pointer device on the UTLPV block and clicking on the PSI-2207 RB, the associated functionalities menu where [UTLPV Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-2209 of the subsystem shall be displayed On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-2211 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-2213 screen of the subsystem shall be displayed On selecting the option [Stand by Start-up], the Start-up stand by PSI-2215 screen of the subsystem shall be displayed On selecting the option [Stand by Shutdown], the shutdown stand by PSI-2217 screen of the subsystem shall be displayed
4.1.6.8.1.7. [Monitoring Start-up] On locating with the pointer device on the TLPV or PIVL block and clicking on PSI-2219 the RB, the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.8.1.8. [TLPV Statistics] On locating with the pointer device on the TLPV block and clicking on the RB, PSI-2233 the associated functionalities menu where [TLPV Statistics] could be selected, shall be displayed
60
4.1.6.8.1.9. [Processor Statistics] On locating with the pointer device on the TLPV or PIVL block and clicking on PSI-2221 the RB, the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.8.1.10.
[PIVL Start-up Shutdown]
On locating with the pointer device on the PIVL block and clicking on the RB, PSI-2245 the associated functionalities menu where [PIVL Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Computer Start-up], the start-up screen of PSI-2247 the computer shall be displayed. On selecting the option [Computer Shutdown], the shutdown screen PSI-2257 of the computer shall be displayed.
4.1.6.9. TDVM Scenario The TDVM scenario shall represent the HW and SW elements of the TDVM PSI-6139 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The TDVM scenario elements are the following ones: See next table.
Table 4.1.6.9-44 : TDVM scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. The ASTERIX Radars number shall be an adaptation datum PSI-2319
The UDDEs number shall be an adaptation datum
PSI-2321
61
4.1.6.9.1.
A menu with the configured functionalities shall be displayed on clicking with PSI-2274 the right button of the pointer device on some of the elements (blocks) of the TDVM scenario. The distribution and grouping of desired functions is commented in the following sections. Later, the meaning of these functions will be described with detail. 4.1.6.9.1.1. Concerning to the TDVM servers 4.1.6.9.1.1.1. [Tandem switchover]
On locating with the pointer device on the TDVM block and clicking on the PSI-2285 RB, the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.9.1.1.2.
[UTDVM Start-up Shutdown]
On locating with the pointer device on the TDVM block and clicking on the PSI-2287 RB, the associated functionalities menu where [UTDVM Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-2289 of the subsystem shall be displayed On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-2291 Processor1 / Processor2 screen of the subsystem shall be displayed On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-2293 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up stand by PSI-2295 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-2297 screen of the subsystem shall be displayed.
62
4.1.6.9.1.1.3.
On locating with the pointer device on the TDVM block and clicking on the PSI-2299 RB, the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.9.1.1.4.
[Technical TDVM Functions Configuration]
On locating with the pointer device on the TDVM block and clicking on the PSI-2329 RB, the associated functionalities menu where [Technical TDVM Functions Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options On selecting the option [Normal TDVM] screen of the TDVM PSI-2331 Functions Configuration shall be displayed. On selecting the option [Enroute Autonomous TDVM] screen of the PSI-2333 Enroute Autonomous TDVM Functions Configuration shall be displayed.
On selecting the option [TMA Autonomous TDVM] screen of the TMA PSI-2546 Functions Configuration shall be displayed, respectively.
4.1.6.9.1.1.5.
[Normal TDVM Statistics]
On locating with the pointer device on the TDVM block and clicking on the PSI-2301 RB, the associated functionalities menu where [Normal TDVM Statistics] could be selected, shall be displayed
4.1.6.9.1.1.6.
On locating with the pointer device on the TDVM block and clicking on the PSI-2303 RB, the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.9.1.2. Concerning to the UAST servers 4.1.6.9.1.2.1. [Tandem switchover]
On locating with the pointer device on the UAST block and clicking on the RB, PSI-2399 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
63
4.1.6.9.1.2.2.
[UAST Start-up Shutdown]
On locating with the pointer device on the UAST block and clicking on the RB, PSI-2401 the associated functionalities menu where [UAST Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-2403 of the subsystem shall be displayed. On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-2405 Processor1 / Processor2 screen of the subsystem shall be displayed. On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-2407 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up stand by PSI-2409 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-2411 screen of the subsystem shall be displayed.
4.1.6.9.1.2.3.
[Surveillance Delays Statistics]
On locating with the pointer device on the UAST block and clicking on the RB, PSI-2425 the associated functionalities menu where [Surveillance Delays Statistics] could be selected, shall be displayed On locating with the pointer device on the ASTERIX Radars block and clicking PSI-2553 on the RB, the associated functionalities menu where [Surveillance Delays Statistics] could be selected, shall be displayed
4.1.6.9.1.2.4.
On locating with the pointer device on the UAST block and clicking on the RB, PSI-2413 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.9.1.2.5.
On locating with the pointer device on the UAST block and clicking on the RB, PSI-2427 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed 64 Software Requirements Description
4.1.6.9.1.3. Concerning to the UDDEs servers 4.1.6.9.1.3.1. [Processor Statistics]
On locating with the pointer device on the UDDE block and clicking on the PSI-2430 RB, the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.9.1.4. Concerning to the Radars 4.1.6.9.1.4.1. [Radar Operation Configuration]
On locating with the pointer device on the Asterix Radars block and clicking PSI-2347 on the RB, the associated functionalities menu where [Radar Operation Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options On locating with the pointer device on the DDE block and clicking on the RB, PSI-2552 the associated functionalities menu where [Radar Operation Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options
On selecting the option [Normal TDVM] the Normal TDVM Radar PSI-2349 Operations Conf screen shall be displayed. On selecting the option [Enroute Autonomous TDVM] the Enroute PSI-2549 Autonomous TDVM Radar Operations Conf screen shall be displayed.
On selecting the option [TMA Autonomous TDVM] the TMA PSI-2548 Autonomous TDVM Radar Operations Conf screen shall be displayed.
4.1.6.9.1.4.2.
[Radar Entry Configuration]
On locating with the pointer device on the Asterix Radars block and clicking PSI-2550 on the RB, the associated functionalities menu where [Radar Entry Configuration] could be selected, shall be displayed On locating with the pointer device on the DDE block and clicking on the RB, PSI-2551 the associated functionalities menu where [Radar Entry Configuration] could be selected, shall be displayed
65
4.1.6.9.1.4.3.
[EADR Statistics]
On locating with the pointer device on the Asterix Radars block and clicking PSI-2434 on the RB, the associated functionalities menu where [EADR Statistics] could be selected, shall be displayed On locating with the pointer device on the DDE block and clicking on the RB, PSI-2547 the associated functionalities menu where [EADR Statistics] could be selected, shall be displayed
On selecting the option [Normal TDVM] screen of Normal Radar Emp PSI-2436 Statistics shall be displayed. On selecting the option [Enroute Autonomous TDVM] screen of PSI-2440 Enroute Autonomous Radar Emp Statistics shall be displayed. On selecting the option [TMA Autonomous TDVM] screen of TMA PSI-2438 Autonomous Radar Emp Statistics shall be displayed.
4.1.6.9.2.
Delays Monitoring
For a correct monitoring of the PSI Radar delays, the PSI must fulfil the following requirements: The Degradation and the Failure associated to any of the following PSI-3521 elements joined to the radar: DEM (delay), RED (redundancy), NRT (North) or PLT (plot), shall be displayed on the state of the current RADAR element, causing the display of the affected radar appears, in blinking RED (Failure) and YELLOW (Degradation) colour, respectively. That is, if one of them is in Failure state, the radar shall be in that state as well, and only when all are in their Nominal state shall the radar colour be GREEN. The radar processing, responsible of updating the states of the NRT and PLT PSI-3522 elements for the PSI shall be: For Local Control Centre: The TDVM (Normal mode) or, in case of unavailability, the TDVM-A (Autonomous mode) of each dependency declared in the centre. For Remote Control Centre: The TDVM-A.
The non-configuration of the secondary plots processing in the TDVM, in PSI-3523 Normal mode for the local centres, or in the TDVM Autonomous mode for the remote centres, for the Asterix or DDE, shall be displayed in the PSI, showing the S character over a PURPLE background in the item representing this radar.
66
4.1.6.10.
EADR Scenario
In the main scenario, in the local background subsystems area, the element PSI-5808 corresponding to the page identifier P_SDR to place the 'EADR' square to access to the detailed EADR scenario (Input Radar) shall be used, keeping the rest of characteristics in the graphic. The EADR scenario shall represent the HW and SW elements of the EADR PSI-6140 subsystem in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The EADR scenario elements are the following ones: See next table.
Table 4.1.6.10-45 : EADR scenarios elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. The ASTERIX Radars number shall be an adaptation datum PSI-3970
The UDDEs number shall be and adaptation datum
PSI-3971
Possible EADR Configurations: with SMDT In the CCV's PSI with SMDT (TDVT+SILVT), a second level scenario with PSI-5795 EADR name, which shall contain its maximum configuration: UAST and its CLANs UDDE and its CLANs ASTERIX RADARS DDE lines and channels UDDE box In the CCV's PSI with SMDT (TPVT+TDVT+SILVT), a second level scenario PSI-5796 with EADR name, which shall contain its maximum configuration: UAST and its CLANs UDDE and its CLANs ASTERIX RADARS DDE lines and channels UDDE box
67
without SMDT In the CCV's PSI without SMDT (TPVT+TDVT+SILVT), a second level PSI-5798 scenario with EADR name, which shall contain its maximum configuration: UAST and its CLANs UDDE and its CLANs ASTERIX RADARS DDE lines and channels UDDE boxes REMOTE_TDVM_LINK In the CCV's PSI without SMDT (TPVT+TDVT+SILVT), a second level scenario with EADR name, which will contain its maximum configuration: REMOTE_TDVM_LINK 4.1.6.10.1. Accessible functionalities through drop-down menus Each element (block) shall be associated with certain functionalities which PSI-6059 could be accessible after having configured the user profile.
A menu with the configured functionalities shall be displayed on clicking with PSI-6060 the right button of the pointer device on some of the elements (blocks) of the EADR scenario. The distribution and grouping of desired functions is commented in the following sections. Later, the meaning of these functions will be described with detail. 4.1.6.10.1.1. Concerning to UAST servers
4.1.6.10.1.1.1. [Tandem switchover] On locating with the pointer device on the UAST block and clicking on the RB, PSI-6089 the associated functionalities menu where [Tandem switchover] could be selected, shall be displayed.
4.1.6.10.1.1.2. [UGSI Start-up Shutdown] On locating with the pointer device on the UAST block and clicking on the RB, PSI-6091 the associated functionalities menu where [UAST Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Tandem Start-up] the tandem start-up screen PSI-6093 of the subsystem shall be displayed On selecting the option [Processor1/Processor2 Start-up] the Start-up PSI-6095 Processor1 / Processor2 screen of the subsystem shall be displayed
68
On selecting the option [Tandem Shutdown], the shutdown Tandem PSI-6097 screen of the subsystem shall be displayed. On selecting the option [Stand by Start-up], the Start-up stand by PSI-6099 screen of the subsystem shall be displayed. On selecting the option [Stand by Shutdown], the shutdown stand by PSI-6101 screen of the subsystem shall be displayed.
4.1.6.10.1.1.3. [Surveillance Delays Statistics] On locating with the pointer device on the UAST block and clicking on the RB, PSI-6103 the associated functionalities menu where [Surveillance Delays Statistics] could be selected, shall be displayed
On locating with the pointer device on the ASTERIX Radars block and clicking PSI-6104 on the RB, the associated functionalities menu where [Surveillance Delays Statistics] could be selected, shall be displayed
4.1.6.10.1.1.4. [Monitoring Start-up] On locating with the pointer device on the UAST block and clicking on the RB, PSI-6106 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.10.1.1.5. [Processor Statistics] On locating with the pointer device on the UAST block and clicking on the RB, PSI-6108 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.10.1.2.
Concerning to the UDDEs servers
4.1.6.10.1.2.1. [Processor Statistics] On locating with the pointer device on the UDDE block and clicking on the PSI-6111 RB, the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
69
4.1.6.10.1.3.
Concerning to the radars
4.1.6.10.1.3.1. [Radar Operation Configuration] On locating with the pointer device on the Asterix Radars block and clicking PSI-6114 on the RB, the associated functionalities menu where [Radar Operation Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options. On locating with the pointer device on the DDE block and clicking on the RB, PSI-6115 the associated functionalities menu where [Radar Operation Configuration] could be selected, shall be displayed, which will display in turn, a menu with the following options. On selecting the option [Autonomous TDVM] screen of the PSI-6117 Autonomous TDVM Radar Operations Conf shall be displayed.
4.1.6.10.1.3.2. [Radar Entry Configuration] On locating with the pointer device on the Asterix Radars block and clicking PSI-6119 on the RB, the associated functionalities menu where [Radar Entry Configuration] could be selected, shall be displayed. On locating with the pointer device on the DDE block and clicking on the RB, PSI-6120 the associated functionalities menu where [Radar Entry Configuration] could be selected, shall be displayed.
4.1.6.10.1.3.3. [EADR Statistics] On locating with the pointer device on the Asterix Radars block and clicking PSI-6124 on the RB, the associated functionalities menu where [EADR Statistics] could be selected, shall be displayed, which will display in turn, a menu with the following options On locating with the pointer device on the DDE block and clicking on the RB, PSI-6125 the associated functionalities menu where [EADR Statistics] could be selected, shall be displayed. On selecting the option [Autonomous TDVM] screen of the PSI-6127 Autonomous Radar Emp Statistics shall be displayed.
4.1.6.10.2. Delays Monitoring For a correct monitoring of the PSI Radar delays, the PSI must fulfil the following requirements: The Degradation and the Failure associated to any of the following PSI-8976 elements joined to the radar: DEM (delay), RED (redundancy), NRT (North) 70 Software Requirements Description
or PLT (plot), shall be displayed on the state of the current RADAR element, causing the display of the affected radar appears, in blinking RED (Failure) and YELLOW (Degradation) colour, respectively. That is, if one of them is in Failure state, the radar shall be in that state as well, and only when all are in their Nominal state shall the radar colour be GREEN. The radar processing, responsible of updating the states of the NRT and PLT PSI-8977 elements for the PSI shall be: For Local Control Centre: The TDVM (Normal mode) or, in case of unavailability, the TDVM-A (Autonomous mode) of each dependency declared in the centre. For Remote Control Centre: The TDVM-A.
The non-configuration of the secondary plots processing in the TDVM, in PSI-8978 Normal mode for the local centres, or in the TDVM Autonomous mode for the remote centres, for the Asterix or DDE, shall be displayed in the PSI, showing the S character over a PURPLE background in the item representing this radar.
4.1.6.11.
EN-ROUTE SS Scenario
The En-Route SS scenario shall represent the HW and SW elements of the PSI-6192 En-Route dependencies in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The En-Route SS scenario elements are the following ones: See next table.
71
EN-ROUTE SS Scenario Components

SS UCS IFV C-VLAN Controller I-VLAN Controller CWP RE R-VLAN Controller I-VLAN Controller PTC I-VLAN Controller Internal LAN (I-VLAN) Control LAN (C-VLAN) Fall-back LAN (R-VLAN) Synchronizer
Type
Sectorization Indicator Element Working Control Processor Configurable Device Not Configurable Device Not Configurable Device Working Control Processor Not Configurable Device Not Configurable Device Not Configurable Device Not Configurable Device Not Monitorized Device ---Specialized Device

31 1 per SS 1 per UCS 2 per UCS 1 per UCS 2 per SS 1 per SS 2 per CWP 1 per CWP 2 per SS 1 per PTC 1 per SS 2 2 1 per processor
Remarks
Connected to UCS 1 per C-VLAN 1 per I-VLAN CWP A, CWP B Connected to CWP A and CWP B 1 per R-VLAN 1 per I-VLAN Connected to I-VLAN
Table 4.1.6.11-46 : En-Route SS scenario elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. Each SS, in the writing, shall be delimited by a framework, which will be the PSI-2474 Sectoring Callsign.
The number of positions shall be obtained from adaptation data.
PSI-2671
The position identification label shall be obtained from the adaptation data.
PSI-2672
An horizontal scrolling bar shall be available in order to be able to move along PSI-2480 the scenario 72 Software Requirements Description
4.1.6.11.1. Accessible functionalities through drop-down menus Each element (block) shall be associated with certain functionalities which will PSI-2451 be able to be accessible after having configured the user profile.
On clicking the right button of the pointer device on some of the elements PSI-2452 (blocks) the EN-ROUTE SS scenario, a menu with the configured functionalities shall be dropped-down. The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described. 4.1.6.11.1.1. [Physical Configuration]
On locating with the pointer device on the IFV block when it corresponds to a PSI-2455 SS which has not been sectored, and clicking on the RB, the associated functionalities menu where [Physical Configuration] could be selected, shall be displayed
4.1.6.11.1.2.
On locating with the pointer device on the CWP block and clicking on the RB, PSI-2536 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.11.1.3.
On locating with the pointer device on the CWP block and clicking on the RB, PSI-2537 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.11.1.4.
[CWP A/B Start-up Shutdown]
On locating with the pointer device on the CWP A/B block and clicking on the PSI-2539 RB, the associated functionalities menu where [CWP A/B Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Computer Start-up], the computer start-up PSI-2541 screen shall be displayed.
73
On selecting the option [Computer Shutdown], Computer Shutdown PSI-2543 screen shall be displayed.
4.1.6.11.1.5.
[Enroute Autonomous TDVM Statistics]
On locating with the pointer device on the CWP A/B block and clicking on the PSI-2545 RB, the associated functionalities menu where [Enroute Autonomous TDVM Statistics] could be selected, shall be displayed
4.1.6.12.
REM SS Scenario
The REM SS scenario shall represent the HW and SW elements of the REM PSI-6193 dependencies in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The REM SS scenario elements are the following ones: See next table.
REM SS Scenario Components

Logical Remote IFV PCV COR TGC Physical Remote C-VALN controller Control V-LAN (C-VLAN)
Type
Sectorization Indicator Element Configurable Device Not configurable Device Not configurable Device configurable Device Stand Alone/Pool processor Configurable Link --
Number of Elements
32 1 per SS 1 per SS 1 per SS 1 per SS 16 2 per Physical Remote 2
Remarks
Logical Remote
4 Logical Remote CWP 1 per C-VLAN
Table 4.1.6.12-47 : REM SS scenario elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. Each logical Remote shall be delimited in the writing with a framework which PSI-2564 will be the Sectoring Indicator.
The number of logical Remotes shall be an adaptation data.
PSI-2565
74
Each Logical Remote shall have a Callsign associated which will be an PSI-2659 adaptation datum.
4.1.6.12.1. Accessible functionalities through drop-down menus Each element (block) shall be associated with certain functionalities which PSI-2585 could be accessible after having configured the user profile.
A menu with the configured functionalities shall be displayed on clicking with PSI-2586 the right button of the pointer device on some of the elements (blocks) of the REM SS scenario. The distribution and grouping of desired functions is commented in the following sections. Later, the meaning of these functions will be described with detail. 4.1.6.12.1.1. [Physical Configuration]
On locating with the pointer device on the COR block when it corresponds to PSI-2589 a sectored Logical Remote, and clicking on the RB, the associated functionalities menu where [Physical Configuration] could be selected, shall be displayed
4.1.6.12.1.2.
[Physical Configuration]
On locating with the pointer device on the FPSP block when it corresponds to PSI-2669 a non-sectored Logical Remote, and clicking on the RB, the associated functionalities menu where [Physical Configuration] could be selected, shall be displayed
4.1.6.12.1.3.
[Physical Configuration]
On locating with the pointer device on the TGC block when it corresponds to a PSI-2667 sectored Logical Remote, and clicking on the RB, the associated functionalities menu where [Physical Configuration] could be selected, shall be displayed
4.1.6.12.1.4.
[REM Processor Start-up Shutdown]
On locating with the pointer device on the REM block and clicking on the RB, PSI-2591 the associated functionalities menu where [REM Processor Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Computer Start-up], the computer start-up PSI-2593 screen shall be displayed. Software Requirements Specification 75
On selecting the option [Computer Shutdown], Computer Shutdown PSI-2595 screen shall be displayed.
4.1.6.12.1.5.
On locating with the pointer device on the REM block and clicking on the RB, PSI-2597 the associated functionalities menu where [Monitoring Start-up] could be selected, shall be displayed
4.1.6.12.1.6.
On locating with the pointer device on the REM block and clicking on the RB, PSI-2600 the associated functionalities menu where [Processor Statistics] could be selected, shall be displayed
4.1.6.13.
TMA SS Scenario
The TMA SS scenario shall represent the HW and SW elements of the TMA PSI-6194 dependencies in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The TMA SS scenario elements are the following ones: See next table.
76
TMA SS Scenario Components

SS UCS IFV C-VLAN Controller I-VLAN Controller CWP RE R-VLAN Controller I-VLAN Controller PTC I-VLAN Controller Internal LAN (I-VLAN) Control LAN (C-VLAN) Fall-back LAN (R-VLAN) Synchronizer
Type
Sectorization Indicator Element Working Control Processor Configurable Device Not Configurable Device Not Configurable Device Working Control Processor Not Configurable Device Not Configurable Device Not Configurable Device Not Configurable Device Not Monitorized Device ---Specialized Device

50 1 per SS 1 per UCS 2 per UCS 1 per UCS 2 per SS 1 per SS 2 per CWP 1 per CWP 2 per SS 1 per PTC 1 per SS 2 2 1 per processor
Remarks
Connected to UCS 1 per C-VLAN 1 per I-VLAN CWP A, CWP B Connected to CWP A and CWP B 1 per R-VLAN 1 per I-VLAN Connected to I-VLAN
Table 4.1.6.13-48 : TMA SS scenario elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. Each SS shall be delimited in the writing with a framework which will be the PSI-2613 Sectoring Callsign.
The number of positions shall be obtained from adaptation data.
PSI-2614
The label of position identification shall be obtained from adaptation data.
PSI-2670
An horizontal scroll bar shall be available in order to move along the scenario. PSI-2615 Software Requirements Specification 77
On clicking the right button of the pointer device on some of the elements PSI-2635 (blocks) the TMA SS scenario, a menu with the configured functionalities shall be dropped-down. The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described. 4.1.6.13.1.1. [Physical Configuration]
On locating with the pointer device on the FPSP block when it corresponds to PSI-2638 a non sectorized SS, and clicking on the RB, the associated functionalities menu where [Physical Configuration] could be selected, shall be displayed.
4.1.6.13.1.2.
4.1.6.13.1.3.
4.1.6.13.1.4.
[CWP A/B Start-up Shutdown]
On locating with the pointer device on the CWP A/B block and clicking on the PSI-2652 RB, the associated functionalities menu where [CWP A/B Start-up Shutdown] could be selected, shall be displayed, which will display in turn, a menu with the following options: On selecting the option [Computer Start-up], the computer start-up PSI-2654 screen shall be displayed. On selecting the option [Computer Shutdown], Computer Shutdown PSI-2656 screen shall be displayed.
78
4.1.6.13.1.5.
[Enroute Autonomous TDVM Statistics]
On locating with the pointer device on the CWP A/B block and clicking on the PSI-2658 RB, the associated functionalities menu where [Enroute Autonomous TDVM Statistics] could be selected, shall be displayed
4.1.6.14.
TWR Scenario
The TWR scenario shall represent the HW and SW elements of the TWR PSI-6195 dependencies in a detailed way. "Detailed means to represent all the relevant information that allows to evaluate the subsystem functionality. The TWR scenario elements are the following ones: See next table.
APP/TOR Scenario Components

UC CWP R-VLAN Controller IFV RE Scroll Radar LAN (R-VLAN) Synchronizer
Type
Sectorization Indicator Element Working Control Processor Not Configurable Device Configurable Device Not Configurable Device Dynamic Element -Specialized Device

50 1 per UC 2 per CWP 1 per UC 1 per UC 1 per UC 2 1 per processor
Remarks
1 per R-VLAN Connected to CWP Connected to CWP SS operational configuration data
Table 4.1.6.14-49 : TWR scenario elements The possible colours associated to each component can be viewed in the state's colours tables located in this document by means of the component type. The number of positions shall be obtained from the adaptation data. PSI-3874
An horizontal scroll bar shall be available in order to move along the scenario, PSI-3876 if need be.
79
On clicking the right button of the pointer device on some of the elements PSI-3889 (blocks) the TWR scenario, a menu with the configured functionalities shall be dropped-down The distribution and grouping of desired functions are commented in the following sections. Later, the meaning of these functions will be described 4.1.6.14.1.1. [Monitoring Start-up]
4.1.6.14.1.2.
4.1.7.
START-UP AND SHUTDOWN
This function will allow to start up and shut down system elements according to the characteristics we will describe in the following sections. There is a unique function (F_APAR) that will be used from all the start up/shut down possibilities listed below. The arguments passed to the function will determine the start up /shut down possible action. On selecting the Start up-Shutdown function, it shall be dropped down a PSI-2845 vertical menu whose options will allow us to monitor the starts up, start up/shut down the system and start up/shut down the physical computers involved in the scenarios. The operating system shall be launched before starting up a computer. PSI-4131
The Startup Request shall generate, through the service MwER_Generate, PSI-4298 the following ER : Code: PSIaso001 Code: SSTaso001 (Only Tower)
80
The Startup Request shall generate, through the service MwER_Generate, PSI-6479 the following ER : Request for a computer Startup Code: PSIaso003
Request for a stand-by computer Start up. Code: PSIaso005
Request for a CWP Start up Code: PSIaso009
Request for all CWP (CWP A and CWP B) Startup Code: PSIaso011
Request for Sector Suite/CWP startup Code: PSIaso013
*Where Identif_Proc will be the graphic name of the last or only message processor. Only tower: In every particular case, for tower the same event reports will be generated, with the same extended text. The Code will be SSTaso"number" instead of PSIaso"number".
The shutdown request shall generate the following ERs, through the service PSI-4310 SrvMwER_Generate, depending on the kind of computer: Computer: PSIoff003 Stand-by Computer: PSIoff005 CWP: PSIoff007 UCS: PSIoff011
Only tower: For tower the same event reports will be generated, with the same extended text. The Code will be SSToff"number" instead of PSIoff"number".
4.1.7.1. KIND OS START-UP CLASSIFICATION TO BEHOLD 4.1.7.1.1. START-UP WITH DATA IN DISC
The aim of this start-up character shall be to recover all the information from PSI-2811 the computer in the presence of: Software Requirements Specification 81
Failure or not controlled processor
shutdown of the last Tandem Operative
Tandem controlled shutdown of short duration due to support reasons, without representative changes in the rest of the System.
This option shall be enabled from the menu screen of individual or tandem PSI-2815 start up from the PSI functions bar, whose user profile has this function configured. This function shall be available to be selected for the tandems computers PSI-2814 TCPV, TLPV, SILV, SMDT.
The GIPV, the GSI and the TDVM shall be considered particular cases.
PSI-2812
The GIPV shall always start up with configuration data in disc and without PSI-2821 FPs.
The GIPV shall always start up with configuration data and data recorded in PSI-2820 shared disc.
4.1.7.1.2.
START-UP WITH STORED FPs
The aim of this start up character shall be to recover the existing FPs previous PSI-2823 to the TCPV tandem shutdown in the System, which were in pending or coordinated state, putting all of them in pending state.
4.1.7.1.3.
START-UP WITHOUT DATA IN DISC
The aim of this start up character shall be to start up without any stored PSI-2833 information although, in case any computer of its family had been started up, it will receive the periodical distribution data automatically.
From the function bar shall be possible access to this modalities through PSI-4438 'System Start-up', 'Tandem Start-up' and 'Ord1/Ord2 Start-up' whenever that the two tandem computers are stopped and that the profile has configured that functions. In case it be a tandem, if it is related to the second computer to be PSI-2834 started up, it shall receive the operative computer data. 82 Software Requirements Description
The execution of the command for the tandem individual start up Start up PSI-2835 Ord1/Ord2, shall start up from the computer 1/2 whenever the desired computer to be started up has launched the Operating system. In case we talk about the first computer of the tandem, it will be available the option start up with own data in disc (TCPV, TLPV, SILV, SMDT) and with own stored FPs (TCPV) In case it is not the first in starting up, the option Start up Ord1/Ord2 shall not be available.
The execution of the Start up Stand by command shall perform the Stand PSI-2842 by computer start-up. If the data taking is long (TCPV and TLPV), and if in a term of 30 minutes it is not completely initialized by the Operative, the Stand by will stop automatically. If the Operative crashes while the Stand by is in Start, the Stand by will stop immediately too.
The PIVL server start up shall always be individual.
PSI-2836
The UCSs and CWPs computers start up shall always be without data in disc. PSI-2838
The shutdown function shall be in charge of carrying out the shutdown in a PSI-2839 controlled way. It will be in charge of performing the selected computers shutdown, understanding as such, the application shutdown, being loaded the operating system.
The manual shutdown of a stop function processor shall be in charge of PSI-2844 carrying out the shutdown in a controlled way. It will be in charge of performing the selected computers shutdown, understanding as such, the application shutdown, being loaded the operating system.
Considerations: The processor shutdown due to the PSI could be performed in two different ways, manually or automatically. In case the shutdown is manual, a shutdown message shall be sent to the local supervisor of each affected processors, according to the performed order. This message will cause a shutdown procedure inside the processor. Besides, an event report will be sent to the PSI indicating the performed action. Software Requirements Specification
PSI-2840
83
In case the shutdown is automatic, the computer will send to itself a shutdown message causing the procedure similar to a manual shutdown. The automatic shutdown of a processor could be produced by: Failure in the LAN controllers. Depending on the kind of processor, the following cases will be able to appear: Failure in both controllers associated with the control LAN of any processor. Failure in both controllers associated with the radar LAN of the TDVM processors (UDDE, UAST, TDVM) and PSI. Repeated crashes of their critical processes. Failure in crossed LANs, in processors of type tandem; the tandem processor which has detected lastly the failure in the controller will be killed. Once determined the shutdown origin of the own processor, this one will be who sends a shutdown message to itself, activating the procedure similar to a manual shutdown. Besides, the following particular situations will exist: The UDDEs and rest of the processors similar to the devices type HW , won't be able to be stopped manually. In case of failure, they will be stopped automatically.
4.1.7.2. START-UP MONITORING Each processor which is starting up or which has aborted the start-up shall be PSI-1596 visualized.
When a processor startup is requested, a progression bar for its display shall PSI-4312 be displayed. The represented percentage shall be displayed on the total startup bar and shall depend on the processor startup phase. The startup progress bar shall be displayed meanwhile the processor startup PSI-4318 takes place.
The start-up initial time of each processor shall be visualized.
PSI-1603
84
In case the processor has aborted, it shall be able to be visualized the time PSI-1602 and the reason why the processor has aborted.
This screen shall visualize each processor which has been started up or PSI-2846 which had aborted the start up.
This function shall be activated by means of the menu, or with the right button PSI-4335 clicking of the pointer device, on the processor, whenever the processor could be started up individually as from a PSI whose profile enables it. The global monitoring startup function shall indicate, for each processor in PSI-4334 startup phase, its name, startup time, abort time, startup percentage with progression bar and reason of failure.
If the startup is not achieved, the following shall occur: The processor shall be in failure (blinking red). The progression bar shall disappear. An alarm shall be generated.
PSI-4316
It shall be possible to consult the reason why it did not startup through the PSI-4317 startup global monitoring function, when some of the system processes is in start up phase, or when some of them is in failure due to an unsuccessful start up. The percentage assigned to each startup stage shall be proportional to the PSI-4327 average time required to complete the stage, assigning a minimum percentage to each stage, so that, all stages can be appreciable. The startup progression display shall be linked to the PSI from which the PSI-4336 aforementioned startup was started, in such a way that: If the PSI from which the startup was generated is stopped, its monitoring shall be lost. While the PSI that generated the startup is available, the startup display, as progression bar on the processor, as in the monitoring function, shall be global to all PSIs. The PSI issuing the startup shall be in charge of distributing the startup state PSI-4321 of the processor to the other PSIs.
In the attached table of Appendix F shall be gathered the Start up PSI-2847 Percentages of the processors and the phases corresponding to each of them. The screen "Start up Monitor" shall consist of an operation button [Exit]. After PSI-2851 selecting it with the left button of the pointer device, the window will be closed. Software Requirements Specification 85
When startup is not achieved, the following ER, that is generated through the PSI-4329 service MwER_Generate shall indicate the start up has not been possible: Code: PSIaso012 Code: SSTaso012 (Only Tower)
4.1.7.3. SYSTEM START-UP This function shall achieve the complete system startup under certain PSI-2737 particular conditions. A window shall be offered to the operator for it, where the scope and the type of startup could be selected by him. The Startup window shall include: Key to be used for the system/tandem/sectorized SS shutdown. System/tandem/sectorized SS shutdown key confirmation PSI-2738
Version with what the system will be started up (the current one in the PSI which performs the start up). List of patches of the version with what the system will start up, separated for signs "+" (the current ones in the PSI). Adaptation data version existing in the PSI which performs the startup. It shall contain as complementary options: CENTRAL Subsystems start-up LOCAL Subsystems start-up PSI-2740 PSI-2739
It shall contain as excludible options: Stored FPs start up (TCPV Tandem) With data in disc for those computers which allow this possibility (TCPV, TLPV, SMDT and SILV tandems) Start up without data for the same computers (TCPV, TLPV, SMDT, and SILV)
The System Startup option shall be inhibited if any of the following systems is PSI-4290 started up: CENTRAL Subsystems LOCAL Subsystems
The startup option shall include several levels of patches associated to the PSI-4293 current system version. Previously, these patches shall be installed in the PSI from which the startup will be performed. Any startup performed from a PSI shall cause that the started up computers PSI-4294 are updated to the system version, to the system patches and to the 86 Software Requirements Description
adaptation version with the PSI installed in them, from where the startup is performed. Patches will be globally installed, even if they only affect to a specific part of the system. The UDDEs start up shall be performed in a manual way as from the PSI-2747 equipment console.
The System Start up by default, shall be with stored FPs for the TCPV, with PSI-2750 data in disc for MTCP and without data for TLPV, SMDT and SILV.
This window shall contain the following operation buttons: [Execute]: Besides performing the analysis it will process the system start up according to the configured options. Also: The devices states will be updated and the start up event reports will be generated. In case the password confirmation is not correct, the message "Error in Access password" will be displayed. If a start up is being achieved, the message "A system start up is already on" will be displayed. Once the order is completed, the message "System start up order done" will be displayed. [Analyse]: It will perform the edited data analysis. If the analysis is correct the message "Correct Analysis" will be displayed. [Exit]: It will shut the window without having performed the start up.
PSI-2745
4.1.7.3.1.
Central subsystems start up
The central subsystems start up shall be applicable in Madrid and Canaries PSI-2741 exclusively.
This option only shall be available when there are no computer of the PSI-2742 aforementioned started up Subsystem.
On enabling it the following computers shall be started up: TCPV Tandem, PSI-2743 GIPV Tandem, FDOs Tandem (with the profile configured by default) and GSI Tandem.
87
4.1.7.3.2.
Local subsystems start up
The local start up subsystems only shall be available when there is not any PSI-2748 computer of the aforementioned started up Subsystem (for such purpose the Continuous Systems won't be considered: GSI, UAST, UDDEs neither the Control Positions.
A start up of the following computers shall be performed: TLPV Tandem, SILV PSI-2749 Tandem, TDVM Tandem, PSA UCS, UCSs, Physical Remotes, CWPs, SIS Tandem, GSI Tandem, UAST Tandem, PIVL Server, SMDT Tandem, TWR CWPs, and PSIs.
4.1.7.3.3.
PSI Startup Strategy
From the point of view of the startup, the PSIs will have a mechanism similar to that in any system processor mechanism. The acquisition of the necessary data for the graphic display, such as the HW state, radar assignment, external centres state, etc, will be the only individual strategy. Each of the PSIs will need a series of data for the real system configuration at a certain moment. The PSI scenarios will start with the site maximum configuration, determined by configuration and adaptation data. Depending on the profile with which the PSI had been started up, the latter PSI-4303 shall need different configurations. For certain configurations, the PSI shall request a startup to the corresponding information server. As the information is being received, the functions associated with the aforementioned configurations will be enabled. During the temporary period in which the real state of each system PSI-4304 component is unknown, its graphic display shall show this lack of initialization with a colours code, linked to the Without Data or Without Information state, for the Subsystem case (blue colour). The subsystems will periodically deliver a message to all the PSIs containing the processor state and that of all the devices associated to it. 4.1.7.4. SYSTEM SHUTDOWN This function shall be in charge of carrying out the System shutdown in a PSI-2751 controlled way. It will be in charge of performing the selected integrating computers shutdown of the application, understanding for such, the shutdown of the application, keeping loaded the operating system. The following restriction to the System shutdown: PSI-4439 - For the shutdown of the system is necessary to enter a password in the Shutdown of the System. - For the shutdown of certain subsystems or Operative processors in any tandems a password of shutdown shall be required - Any shutdown shall ask for acknowledge from the operator. 88 Software Requirements Description
The shutdown window of the system shall contain the following: PSI-2758 System shutdown key (it will be entered in the startup and it will also be necessary in order to execute the shutdown) And the following complementary options: CENTRAL Subsystems shutdown LOCAL Subsystems shutdown CWP Tower Shutdown The enabling of the last option will allow, in turn, to configure the following options excludibles each other: shutdown all CWPs shutdown Non Sectorized CWPs
This action shall not stop the following computers which comprise the PSI-4307 Continuous Systems processors group: GSI Tandem UAST Tandem UDDEs Pool PSI from which the shutdown is executed
The system shutdown shall generate the following ER through the service PSI-4308 SrvMwER_Generate: PSIoff001 SSToff001 (Only tower)
This window shall contain the following operation buttons: [Execute]: Besides performing the analysis it will process the system start up according to the configured options. Also: The devices states will be updated and the shutdown event reports will be generated. In case the password confirmation is not correct, the message "Error in Access password" will be displayed. In case it is impossible to achieve the shutdown after a certain time, the message "There is not answer from the computer for the System Shutdown function" will be displayed. [Analyse]: It will perform an analysis about the edited data. [Exit]: It will shut the window without having performed the shutdown
PSI-2752
89
4.1.7.4.1.
Central subsystems shutdown
The CENTRAL subsystems shutdown shall be applicable in Madrid and PSI-2757 Canaries exclusively.
This option shall only be available when there is any started up computer of PSI-2756 the aforementioned Subsystems.
On enabling it the following computers shall be shut down: TCPV Tandem, PSI-2755 MTCP Tandem, GIPV Tandem, and FDOs Tandem.
4.1.7.4.2.
Local subsystems shutdown
The LOCAL Subsystems shutdown shall only be available when any PSI-2754 computer of the aforementioned Subsystem is started up (for such purpose the Continuous Systems won't be considered: GSI, UAST, UDDEs nor CWPs.
A stop of the following computers shall be performed: TLPV Tandem, SILV PSI-2763 Tandem, TDVM Tandem,UCSs, PSA UCS, Physical Remotes, CWPs, SIS Tandem, GSI Tandem, UAST Tandem, PIVL Server, SMDT Tandem, TWR CWPs, and PSIs.
The options of stopping SSs (all or the ones not sectorized) shall only be PSI-2753 accessible when Local Subsystems shutdown option has been selected.
4.1.7.5. TANDEM SYSTEMS START-UP / SHUTDOWN It shall affect to the following subsystems: PSI-2764 UTCPV, UGIPV, UTDVM, USNETS, UAST, UTLPV, USILV, UGSI, USIS, USMDT. In these systems we shall be able to Start up Tandem or each one PSI-2765 of the Computers in an individual way Start up Ord1/Ord2 as the operative one, and afterwards, the Stand by one Start up Stand by, Stop Tandem or simply, stop the Stand by one Stop Stand by and later the Operative one. These functions are detailed in the following sections:
Note: PSI-2766 The start up of the FDIs and PSIs shall be performed in a manual way from the login window. The UDDEs start up will be performed from the System operator menu. 90 Software Requirements Description
4.1.7.5.1.
SUBSYSTEM TANDEM START-UP
This function only shall be accessible in case any computer of the tandem is PSI-2769 started up .
This function shall be in charge of performing the start up of both tandem PSI-2770 computers, without setting which of them will be the Operative one, since the first operation of the start up will be to match both computers of the tandem with the one which was the last in operative state. Firstly, the one labeled shall be started up as Ord1, and it will be established PSI-2771 as the Operative one, except in case the GSI where the computer which will start up as Operative will be the one which has the Cluster configured. In the tandem start up, if a crossed LAN failure situation is detected, the PSI-2773 processor of lower order (order 1) shall be started up, except if the startup is performed with data in disc or with stored flight plans, that the processor which has the newest data will be the one which starts up. This mechanism is specified in the following table:
Processor 1 LAN1 OK OK OK OK OK OK OK LAN2 OK OK OK OK DOWN DOWN DOWN Processor 2 LAN1 OK OK DOWN DOWN OK OK DOWN LAN2 OK DOWN OK DOWN OK DOWN OK
Action Resulted Normal startup. Normal startup. Normal startup. Only Processor 1 shall statrt up, but there is not crossed LAN situation. Normal startup. Normal startup. Crossed LAN situation: Only Processor 1 shall start up or, in case of startup with data in disc of stored flight plan, the processor with the newest data. Only Processor 1 shall statrt up, but there is not crossed LAN situation. Normal startup Crossed LAN situation: Only Processor 1 shall start up or, in case of startup with data in disc of stored flight plan, the processor with the newest data. Normal startup Only Processor 1 shall statrt up, but there is not crossed LAN situation. Only Processor 2 shall statrt up, but there is not crossed LAN situation. Only Processor 2 shall statrt up, but there is not crossed LAN situation.
OK DOWN DOWN
DOWN OK OK
DOWN OK OK
DOWN OK DOWN
DOWN DOWN DOWN DOWN
OK OK DOWN DOWN
DOWN DOWN OK OK
OK DOWN OK DOWN
91
Processor 1 LAN1 DOWN DOWN LAN2 DOWN DOWN
Processor 2 LAN1 DOWN DOWN LAN2 OK DOWN
Action Resulted Only Processor 2 shall statrt up, but there is not crossed LAN situation. None of the processors shall start up.
Table 4.1.7.5.1-50 : Startup with crossed LAN situation. It shall only exist a kind of start up for the tandems, except for the following PSI-2774 ones:
For the TCPV we could: PSI-2775 [Enable/Disable] Start up with stored FPs. On locating the pointer of the device on this option, the left button shall be clicked in order to enable and disable. At the moment it is enabled the start up of the TCPV tandem with stored FPs will be performed.
For the particular cases of TCPV, TLPV, SILV, SMDT we could: PSI-2777 [Enable/Disable] Start up C/D (with data). On locating the pointer of the device on this option, the left button shall be clicked in order to enable and disable. At the moment it is enabled the start up of the tandem with data will be performed. [Enable/Disable] Start up without data. On locating the pointer of the device on this option, the left button shall be clicked in order to enable and disable. At the moment it is enabled the start up of the tandem without data will be performed.
Windows corresponding to the Tandem start up shall contain the following PSI-2776 operation buttons: [Execute]: The tandem start up request confirmation window shall be displayed, and if it is confirmed, the selected tandem start up will be processed, the states of the devices will be updated, and the start up event reports will be generated. If after a time the start up could not be executed, the message There is not response of the computer for the function: Tandem Start up Request will be displayed. [Exit]: It shall shut the window without having performed the start up.
The tandem start up petition shall generate, , through the service PSI-4396 MwER_Generate, the following ER: 92 Code: PSIaso007 Software Requirements Description
Code: SSTaso007 (Only Tower)
4.1.7.5.2.
SUBSYSTEM PROCESSOR1 / PROCESSOR2 START-UP
This function only shall be accessible in case any computer of the PSI-2779 tandem is started up .
This function shall be in charge of performing the individual start up of a PSI-2780 selected tandem computer.
Depending on the tandem, the start up options shall be showed on PSI-2781 keeping the data in disc or with the stored FPs. This option will only be available when both tandem computers are stopped.
It shall only exist a kind of start up for the tandems, except for the PSI-2784 following ones:
For the TCPV we could: PSI-2785 [Enable/Disable] Start up with stored FPs. On locating the pointer of the device on this option, the left button shall be clicked in order to enable and disable. At the moment it is enabled, the start up of the TCPV tandem with stored FPs will be performed.
For the particular cases of TCPV, TLPV, SILV, TPVT we could: PSI-2786 [Enable/Disable] Start up C/D (with data). On locating the pointer of the device on this option, the left button shall be clicked in order to enable and disable. At the moment it is enabled, the start up of the tandem with data will be performed. [Enable/Disable] Start up without data. On locating the pointer of the device on this option, the left button shall be clicked in order to enable and disable. At the moment it is enabled, the start up of the tandem without data will be performed.
Windows corresponding to the computer start up shall contain the PSI-2787 following operation buttons: [Execute]: The tandem start up request confirmation window shall be displayed, and if it is confirmed, the selected tandem start up will be processed, the states of the devices will be updated, and Software Requirements Specification 93
the start up event reports will be generated. If after a time the start up could not be executed, the message There is not response of the computer for the function: [computer name] Start up Request will be displayed. [Exit]: It shall shut the window without having performed the start up.
4.1.7.5.3.
SUBSYSTEM TANDEM SHUTDOWN
This function shall perform a shutdown of both Tandem computers or of the PSI-2790 operative one, if it is started up.
This action shall only be allowed with the entering of the access password PSI-2791 which has been chosen in the System start up.
In case of Tandem TCPV shutdown the Operative computer shall always PSI-2797 save the file of stored FPs.
Windows corresponding to the computer/tandem shutdown shall contain PSI-2796 the following operation buttons: [Execute]: The shutdown request confirmation password window of the computer/tandem shall be displayed. The states of the devices will be updated and the start up event reports will be generated. If the password is not correct the message Error in Access Password shall be displayed If after a time the shutdown could not be executed, the message There is not response of the computer for the function: [Tandem name] Shutdown will be displayed. [Exit]: It shall shut the window without having performed the shutdown.
The tandem shutdown request shall generate, through the service PSI-4309 SrvMwER_Generate, the following ER: 94 PSIoff009 SSToff009 (Only for Tower) Software Requirements Description
4.1.7.5.4.
SUBSYSTEM STAND-BY START-UP
This function shall perform the start up of the Stand by computer
PSI-2801
This action shall cause the start up without data in disc, and it will take PSI-2802 them from the Operative in order to keep the coherence of data with it.
The window corresponding to the start up shall contain the following PSI-2804 operation buttons: [Execute]: It will process the start up of the tandem computer which is not started up as Stand by. This fact will require that its partner is started up as operative. The states of the devices will be updated and the start up event reports will be generated. If after a time the shutdown could not be executed, the message There is not response of the computer for the function: [Processor name] Start up Request will be displayed. [Exit]: It shall shut the window without having performed the start up.
4.1.7.5.5.
SUBSYSTEM STAND-BY SHUTDOWN
This function shall only be accessible in case both tandem computers are PSI-2806 started up
This function shall be in charge of carrying out a tandem computer PSI-2807 shutdown whose actual state is Stand by, in a controlled way.
The window corresponding to the shutdown shall contain the following PSI-2809 operation buttons: [Execute]: It will process the shutdown of the tandem computer which is started up as Stand by. The states of the devices will be updated and the shutdown event reports will be generated. If after a time the shutdown could not be executed, the message There is not response from the computer for the Software Requirements Specification 95
function:System Shutdown [Processor name] will be displayed. [Exit]: It shall shut the window without having performed the stop.
4.1.7.6. TANDEM SWITCHOVER It shall allow to perform the available Tandems units switchovers in the centre PSI-406 from the following: UAST, UTDVM, UTLPV,UGSI, USILV, UTCPV, UGIPV, USIS, URDS, UTPLM.
On selecting this function a vertical menu shall be displayed with the following PSI-2708 selection options: UAST UTDVM UTLPV UGSI USILV UTCPV UGIPV USIS USMDT
On selecting on the options (select one of the units) the "Tandem Switchover" PSI-2709 screen shall be displayed on the scenario of the selected unit.
The Tandem Switchover screen shall display the current state of the tandem PSI-2710 computers.
The Tandem Switchover screen shall display if the switchover is allowed or PSI-2711 not.
In order to be able to perform a manual switchover, it shall be necessary a PSI-2712 tandem to exist and that this tandem is stable, that is, an Operative computer exists and an Stand-by computer exists.
The Tandem Switchover screen shall display the following operation PSI-2713 buttons: 96 Analyse Software Requirements Description
Execute Exit
In the tandem switchover screen shall be available a labeled button as PSI-2715 [Analyse], which will perform an analysis about the possibility of achieving a switchover. If the result of the analysis is correct the Correct Analysis message will be displayed.
In the tandem switchover screen it shall be available a labeled button as PSI-2714 [Execute], which besides performing an analysis about the possibility of achieving a switchover, it will process it, in case there are no errors.
The Tandem Switchover screen shall be displayed when the tandem PSI-2718 switchover is executed and it will display the following action buttons. OK: It will allow to confirm the switchover tandem Cancel: It will allow to close the confirmation window without performing the switchover.
If the switchover is confirmed, the correct switchover message shall be PSI-2719 displayed, and in the corresponding scenario will be updated the computers state which compose the tandem. The Operative computer (green) will switch to Not available (fix red) and the Stand by (fix yellow) will switch to Operative (green).
In the tandem switchover screen shall be available a labeled button as [Exit], PSI-2716 which will close the switchover tandem screen without performing any action.
4.1.7.7. CWPs, UCSs AND PHYSICAL REMOTES START-UP / SHUTDOWN The following second level scenarios will be affected: EN-ROUTE TMA REM TWR SPV
The CWPs, UCSs and Physical Remotes start up shall always be without PSI-2895 data in disc.
97
4.1.7.7.1.
EN-ROUTE and TMA Scenarios
4.1.7.7.1.1. Start-up in one EN-ROUTE/TMA SS This function only shall be available whenever the selected computer (CWP PSI-2882 A, CWP B, UCS) is not started-up.
The menu shall show the option (start up) of the different SSs.
PSI-2883
On selecting one of the SSs, the start up confirmation screen of the selected PSI-2897 SS shall be displayed.
With reference to any SS, it shall appear three selection fields, for those PSI-2898 which are not started up, as sensitive to selection: UCS Start up CWP A Start up CWP B Start up.
The window corresponding to the start up shall contain the following operation PSI-2885 buttons: [Execute]: It will display the start up confirmation screen with the following options: [Ok]: It will perform the start up of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the start up event reports will be generated. [Exit]: It shall shut the window without having performed the start up.
4.1.7.7.1.2. Shutdown in one EN-ROUTE/TMA SS This function shall be available whenever the selected computer (CWP, UCS) PSI-2887 is started up.
The menu shall show the option (shutdown) of the different SSs.
PSI-2899
On selecting one of the SSs, the shutdown confirmation screen of the PSI-2900 selected SS shall be displayed.
With reference to any SS, it shall appear three selection fields, for those PSI-9014 which are not shut down, as sensitive to selection: 98 UCS shutdown CWP A shutdown CWP B shutdown Software Requirements Description
The shutdown window shall contain the following operation buttons: PSI-2902 [Execute]: It will display the shutdown confirmation screen with the following options: [Ok]: It will perform the shutdown of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the shutdown event reports will be generated. [Exit]: It shall close the window without having performed the shutdown. In order to perform the shutdown it shall be necessary to enter the system PSI-9022 start up access password.
4.1.7.7.1.3. Start-up in all the EN-ROUTE/TMA SSs This function only shall be available when all the computers of aforementioned scenario (CWPs and UCSs) are shut down. the PSI-2857
In case of shut down SSs, in the "In all the SSs Start up" screen, it shall PSI-2858 appear three selection fields as sensitive to selection: UCS start up CWP A start up CWP B start up
The window corresponding to the start up shall contain the following operation PSI-2859 buttons: [Execute]: It will display the start up confirmation screen with the following options: [Ok]: It will perform the start up of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the start up event reports will be generated. [Exit]: It shall close the window without having performed the start up.
4.1.7.7.1.4. Shutdown in all the EN-ROUTE/TMA SSs This function only shall be available when some of the computers of the PSI-2867 aforementioned scenario (CWPs and UCSs) are started up.
In case of started up SSs, in the "In all the SSs Shutdown" screen, shall PSI-2871 appear three selection fields as sensitive to selection: UCS shutdown CWP A shutdown CWP B shutdown
99
4.1.7.7.1.5. Shutdown in all the EN-ROUTE/TMA Non Sectorized SSs This function only shall be available whenever any non-sectorized SS is PSI-2876 started up.
In case any non sectorized SSs are started up, in the "All the Non Sectorized PSI-2877 SSs Shutdown" screen shall appear three selection fields as sensitive to selection: UCS Shutdown CWP A Shutdown CWP B Shutdown.
4.1.7.7.2.
REM Scenario
4.1.7.7.2.1. Start up one Physical Remote This function only shall be available whenever the selected computer PSI-8984 (Physical Remote) is not started-up.
100
The menu shall show the option (start up) of the different Physical Remotes.
PSI-8985
On selecting one of the Physical Remotes, the start up confirmation screen of PSI-8986 the selected position shall be displayed.
4.1.7.7.2.2. Shut down one Physical Remote This function shall be available whenever the selected computer (Physical PSI-8996 Remote) is started up.
The menu shall show the option (shutdown) of the different Physical PSI-8997 Remotes.
On selecting one of the Physical Remotes, the shutdown confirmation screen PSI-8998 of the selected Physical Remote shall be displayed.
The shutdown window shall contain the following operation buttons: PSI-8999 [Execute]: It will display the shutdown confirmation screen with the following options: [Ok]: It will perform the shutdown of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the shutdown event reports will be generated. [Exit]: It shall close the window without having performed the shutdown.
4.1.7.7.2.3. Start up all the Physical Remotes This function only shall be available when all the computers of aforementioned scenario (Physical Remotes) are shut down. the PSI-8990
The window corresponding to the start up shall contain the following operation PSI-8993 buttons: Software Requirements Specification 101
[Execute]: It will display the start up confirmation screen with the following options: [Ok]: It will perform the start up of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the start up event reports will be generated. [Exit]: It shall close the window without having performed the start up.
4.1.7.7.2.4. Shut down all the Physical Remotes This function only shall be available when some of the computers of the PSI-9016 aforementioned scenario (Physical Remotes) are started up.
4.1.7.7.3.
TWR Scenario
4.1.7.7.3.1. Start up one TWR CWP This function shall be available whenever the selected computer is shut down. PSI-4115
The menu shall show the option (start up) of the different CWPs.
PSI-4116
On selecting one of the positions, the start up confirmation screen of the PSI-4117 selected CWP shall be displayed.
The window corresponding to the start up shall contain the following operation PSI-4119 buttons: [Execute]: It will display the start up confirmation screen with the options [Ok]: It will perform the start up of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the start up event reports will be generated. 102 Software Requirements Description
[Exit]: It shall close the window without having performed the start up.
4.1.7.7.3.2. Shut down one TWR CWPs This function shall be available whenever the selected computer is started PSI-4121 up.
The menu shall show the option (shutdown) of the different CWP.
PSI-4122
On selecting one of the positions, the shutdown confirmation screen of the PSI-4123 selected CWP shall be displayed.
4.1.7.7.3.3. Start up of the TWR CWPs This function only shall be available when all the computers of aforementioned scenario are stopped. the PSI-4129
4.1.7.7.3.4. Shutdown all the TWR CWPs This function only shall be available when some of the computers of the PSI-4134 aforementioned scenario is started up.
The shutdown window shall contain the following operation buttons: PSI-4138 [Execute]: It will display the shutdown confirmation screen with the Software Requirements Specification 103
following options: [Ok]: It will perform the shutdown of the selected devices [Cancel]: It will allow to perform a new selection The states of the devices will be updated and the shutdown event reports will be generated. [Exit]: It shall close the window without having performed the shutdown. In order to perform the shutdown it shall be necessary to enter the system PSI-4135 start up access password.
4.1.7.7.4.
SPV Scenario
4.1.7.7.4.1. Non-Sectorisable Suit (PSA) Start up This function shall be available whenever the Non-Sectorisable Suit is shut PSI-2904 down.
The start up confirmation screen of the selected Non-Sectorisable Suit shall PSI-2906 be displayed.
It shall appear three selection fields, for those which are not started up, as PSI-2907 sensitive to selection: UCS start up CWP A start up CWP B start up
4.1.7.7.4.2. Non-Sectorisable Suit (PSA) Shut down This function shall be available whenever the Non-Sectorisable Suit is started PSI-9036 up.
The shutdown confirmation screen of the selected Non-Sectorisable Suit shall PSI-9038 be displayed.
104
It shall appear three selection fields, for those which are not shutdown, as PSI-9039 sensitive to selection: UCS shutdown CWP A Shutdown CWP B Shutdown
4.1.7.7.5.
TLPV Scenario
4.1.7.7.5.1. PIVL Start up This function shall be available whenever the PIVL is shut down. PSI-9043
The start up confirmation screen of the selected PIVL shall be displayed.
PSI-9045
An action confirmation window shall be displayed with the following operation PSI-2913 buttons: [OK]: The window will be closed , accepting the PIVL start up. [Cancel]: The window will be closed, without starting up de PIVL.
4.1.7.7.5.2. PIVL Shutdown This function shall be available whenever the PIVL is started up. PSI-9044
The shutdown confirmation screen of the selected PIVL shall be displayed.
PSI-9046
An action confirmation window shall be displayed with the following operation PSI-9042 buttons: [OK]: The window will be closed , accepting the PIVL shutdown. [Cancel]: The window will be closed, without shutting down de PIVL.
105
4.1.8.
CONFIGURATION INFORMATION
All configuration changes performed, by manual action, in the PSI shall be PSI-9161 send to MwREC through the even EvtPsi_ConfigChangeRecording. Note: Changes performed through Distributed Tables will be send to recording by MwDC.
4.1.8.1. TECHNICAL CONFIGURATION The following functions of configuration will be able to be performed: 4.1.8.1.1. Links Configuration
4.1.8.1.1.1. Links TCPV-TLPV Configuration This function shall allow to configure the links between TCPV and TLPVs. PSI-404
On selecting this function a vertical menu shall be dropped-down with the PSI-2696 following options which could be selected: TCPV TLPV
[TCPV] option: On selecting the TCPV option shall be displayed the window of link with PSI-2695 TCPV.
In the link with TLPV window, the link with the FPs monitoring central PSI-2699 environment assigned to the FIR, from which the current centre depends on, shall be selected/non selected, through the clicking with the LB of the pointer device in order to enable and to disable. In the TCPV link screen a button labeled as [Execute] shall be available PSI-2700 and it will close the link with TCPV window by enabling the new configuration of Link with TCPV. In the link with TCPV window a button labeled as [Exit] shall be available PSI-2701 and it will close the link with TCPV window without performing any action.
[TLPV] option: This option shall only be displayed in TCPV centres PSI-4535
106
On selecting the TLPV option, the link with TLPVs windows shall be PSI-4534 displayed
In the link with TLPV window the link with the FPs monitoring local PSI-4532 environment assigned to the FIR, from which the current centre depends on,shall be selected/non selected, through the clicking with the LB of the pointer device in order to enable and to disable In the link with TLPVs window a button labeled as [Execute] shall be PSI-4543 available and it will close the link with TLPV window by enabling the new configuration. In the link with TLPVs window a button labeled as [Exit] shall be available PSI-4544 and it will close the link with TLPV window without performing any action.
4.1.8.1.1.2. VILMA link Configuration (F_CEVILMA) It shall be possible to enable/disable the links from PSI with VILMA: SICV_MET SICV_AIS ATIS SMI PSI-5770
The access to the configuration of the SILV links shall be performed from the PSI-5759 function bar.
If the function F_CEVILMA exists any of the other three functions (F_CESMI, PSI-5760 F_CEATIS, F_CEICA) which exist shall hang from this function
If the function F_CEVILMA does not exist any of the other three functions PSI-5761 (F_CESMI, F_CEATIS, F_CEICA) shall exist without need any group.
When PSI enables/disables a VILMA link (SICV_MET, SICV_AIS, ATIS PSI-5769 SMI) an event report from PSI shall be generated through the service SrvMwER_Generate: PSIcev001
Where the extended text which will be displayed depending on the type of configured lines (link with ICARO, ATIS lines or SMI lines). That is, if one text is displayed, the other ones cannot be displayed in an only action of configuration. In the 'Extended Text_2' and 'Extended Text_3' instead of appear 'ATIS_1', ... Software Requirements Specification 107
and 'SMI_1', ..., respectively, it shall appear the same name that the lines had in the SILV scenario ( name obtained, in ATIS as well as in adaptation data SMI).
ICARO link Configuration function (F_CEATIS): This window shall be displayed selecting it from the function menu. The PSI-5108 SILV scenario will be displayed if this window is requested to be opened from the function menu. This window shall be accessible from the SILV subsystem contextual PSI-5109 menu which display the link with ICARO.
The 'Link with Icaro' shall consist of the following elements: An only primary view frame Sensitive buttons 'Modify' and 'Close'
PSI-5110
This primary view frame will display: Two toggles, every one shall be compose by one non selective text PSI-5112 containing the name of the system linked, here 'SICV_AIS' and 'SICV_MET' respectively and the selective mark box. The link shall be displayed with 'Enable' state by default , it means with PSI-5113 the selective mark box marked.
Clicking the sensitive button 'Modify' an acknowledge window shall be PSI-5114 open. If the function in that window has run properly, the configuration becomes effective and the main window is closed. The sensitive button 'Close' shall cancel the action and close the window. PSI-5117
The information window associated to the 'Link with ICARO' main window PSI-5118 shall display the text 'DONE CONFIGURATION CHANGE LINK WITH ICARO'
SMI line link Configuration function (F_CESMI): It shall be possible to make the configuration of the elements if the PSI-5766 elements (links) are adapted and at the same time are declarated by the users in the SPV_TCEHR.CFG file of the SILV processor It shall not be displayed in the control list if the element is not in the PSI-5767 installation file
108
If an element is not adapted it shall not be displayed in the control list.
PSI-5768
This window shall be displayed selecting it from the function menu or from PSI-5135 the contextual menu of every component of the SILV subsystem which represent the link with every SMI line. The SILV scenario will be displayed if it is requested to open this window from the function menu. The 'Link with SMI' shall consist of the following elements: An only primary view frame Sensitive buttons 'Modify' and 'Close' PSI-5136
This primary view frame will display: A set of vertically organized toggles. Every toggle shall consist of a non PSI-5138 selective text and a sensitive box. The non selective texts will be respectively the SMI lines identifier adapted for that Centre (defined as adaptation data), it means, the OACI identifiers from every aerodrome where there are SMI lines coming. The link shall be displayed with 'Enable' state by default , it means with PSI-5142 the selective mark box marked.
Clicking the sensitive button 'Modify' an acknowledge window shall be PSI-5143 open. If it is confirmed in that window the function has run properly, the configuration becomes effective and the main window is closed. The sensitive button 'Close' shall cancel the action and close the window. PSI-5144
The information window associated to the 'Link with SMI' main window PSI-5145 shall display the text 'DONE CONFIGURATION CHANGE LINK WITH SMI'
ATIS line link Configuration function (F_CEATIS): It shall be possible to make the configuration of the elements if the PSI-5763 elements (links) are adapted and at the same time are declarated by the users in the SPV_TCEHR.CFG file of the SILV processor. It shall not be displayed in the control list if the element is not in the PSI-5764 installation file.
If an element is not adapted it shall not be displayed in the control list.
PSI-5765
109
This window shall be displayed selecting it from the function menu. The PSI-5122 SILV scenario will be displayed if it is requested to open this window from the function menu. This window shall be accessible from every element in the SILV PSI-5123 subsystem contextual menu which display the link with every ATIS line.
The 'Link with ATIS' shall consist of the following elements: An only primary view frame Sensitive buttons 'Modify' and 'Close'
PSI-5124
This primary view frame will display: A set of vertically organized toggles. Every toggle shall consist of a non PSI-6220 selective text and a sensitive box. The non selective texts will be respectively the ATIS lines identifier adapted for that Centre (defined as adaptation data), it means, the OACI identifiers from every aerodrome where there are ATIS lines coming. The link shall be displayed with 'Enable' state by default , it means with PSI-6215 the selective mark box marked.
Clicking the sensitive button 'Modify' an acknowledge window shall be PSI-6216 open. If it is confirmed in that window the function has run properly, the configuration becomes effective and the main window is closed. The sensitive button 'Close' shall cancel the action and close the window. PSI-6217
The information window associated to the 'Link with ATIS' main window PSI-6218 shall display the text 'DONE CONFIGURATION CHANGE LINK WITH ATIS'
4.1.8.1.1.3. TLPV link Configuration (F_CENL_TLPV_TOR) This window shall be displayed selecting it from the function menu. The PSI-5176 SMDT scenario will be displayed if this window is requested to be opened from the function menu. This window shall be accessible from the SMDT subsystem contextual menu PSI-5177 which display the link with every TLPV subsystem.
The 'Link with TLPV Configuration' shall consist of the following elements: An only primary view frame Sensitive buttons 'Modify' and 'Close'
PSI-5178
110
o In the first line a non selective text centered as title ('TLPV Link') PSI-5179 o The line shall consist of a non selective text and a sensitive box. The non selective text shall be the link identifier. The link shall be displayed with 'Enable' state by default , it means with the PSI-6224 selective mark box marked.
Clicking the sensitive button 'Modify' an acknowledge window shall be open. If PSI-6225 it is confirmed in that window the function has run properly, the configuration becomes effective and the main window is closed. The sensitive button 'Close' shall cancel the action and close the window. PSI-6226
The information window associated to the 'Sensors Configuration' main PSI-5184 window shall display the text 'DONE CONFIGURATION CHANGE LINK WITH TLPV'
4.1.8.1.1.4. SMDT link Configuration Links Monitoring The PSI which attend to a system of Tower with SMDT with the SILV PSI-5097 functionality shall have a new link ENLACE_TORRE_SILVT. This new link shall be included in the TCEH of PSI, and shall generate the ER associated with the change of physical state of links. The PSI which attend to Remote Vigilance Clients of Information Centre shall PSI-5099 have a new link ENLACE_TDVM_REMOTO. This new link shall be included in the TCEH of PSI, and shall generate the ER associated with the change of physical state of links. The PSI which attend to a system of Tower with SMDT with the TPVT PSI-5095 functionality shall control a new link: ENLACE_TORRE_TLPV. This new link shall be included in the TCEH of PSI, and shall generate the ER associated with the change of physical state of links. TLPV-Tower link Configuration: In a PSI which display the link ENLACE_TORRE_TLPV, the function PSI-5803 configuration of the logical state for this link shall exist. REMOTE TDVM link Configuration: In a PSI which display the link ENLACE_TDVM_REMOTO, the function PSI-5806 configuration of the logical state for this link shall exist. Surface sensors link Configuration: 111
In PSIs which attend to a Tower system, with SMDT with the TPVT PSI-5807 functionality and surface sensors, it shall exist the configuration function of the logical state of the SMDT Tandem link with the surface sensors SMR, SMM-A and SMM-S.
4.1.8.1.1.5. Surface Sensors Link Configuration (F_ENT_RAD_SUP) This function shall allow to configure the Surface Sensors link. PSI-5209
This window shall be displayed selecting it from the function menu. The PSI-5161 SMDT scenario will be displayed if it is requested to open this window from the function menu. This window shall be accessible from every element in the SMDT subsystem PSI-5162 contextual menu which display the link with every surface or multilateration sensor. The 'Sensors Configuration' shall consist of the following elements: An only primary view frame Sensitive buttons 'Modify' and 'Close' PSI-5163
This primary view frame will display: o In the first line a non selective text centered as title ('Surface Sensor') PSI-5166 o Next in the following lines, two toggles vertically arranged. Every line shall consist of a non selective text and a sensitive box. The non selective text shall be respectively, the identifier of adapted sensor devices. o In the next line a non selective title centered as title ('Multilateration Sensors') . The link shall be displayed with 'Enable' state by default , it means with the PSI-5167 selective mark box marked.
The information window associated to the 'Sensors Configuration' main PSI-5170 window shall display the text 'DONE SENSOR CONFIGURATION CHANGE'
112
4.1.8.1.1.6. TDVM link Configuration (F_CENL_TDVM_REM) This window shall be displayed selecting it from the function menu. The PSI-5190 SMDT scenario will be displayed if this window is requested to be opened from the function menu.
This window shall be accessible from the SMDT subsystem contextual menu PSI-5191 which display the link with every TDVM subsystem.
The 'TDVM link configuration' shall consist of the following elements: An only primary view frame Sensitive buttons 'Modify' and 'Close'
PSI-5192
This primary view frame will display: o In the first line a non selective text centered as title ('TDVM Link') PSI-5195 o The line shall consist of a non selective text and a sensitive box. The non selective text shall be the link identifier. The link shall be displayed with 'Enable' state by default , it means with the PSI-5196 selective mark box marked.
The information window associated to the 'TDVM Link Configuration' main PSI-5199 window shall display the text 'DONE CONFIGURATION CHANGE LINK WITH TDVM'
4.1.8.1.2.
Radar Process Configuration
By means of this function, each of the TDVM processes to be performed of PSI-2915 the information received by EACH RADAR shall be able to be configured. Normal Mode. This process shall be performed by the TDVM server directly. Autonomous Mode: This process shall be performed by the Route or TMA positions when they are configured in autonomous mode and when the radar is among the ones selected in this position. Both first and second level texts from the following tables are indicative ( it PSI-2931 shall be configurable by profile). Software Requirements Specification 113
PSI Functions related with Air Surveillance

1 Level Text Route / TMA TDVM Normal TMA Autonomous TDVM 2 Level Text No Local TMA TMA Autonomous TDVM TDVT TWR Normal TDVM Autonomous TDVM
Radar Process Configuration
The possible functions for the Radar Treatment Configuration, in function of PSI-7016 the different centres shall be: F_CTRAT_RAD (Function groping the rest of functions) F_CTRAT_RAD_NOR (Normal TDVM) F_CTRAT_RAD_RUTA (Route Autonomous TDVM) F_CTRAT_RAD_TMA ( Autonomous TMA TDVM) F_CTRAT_RAD_TOR ( Autonomous TDVM) If the function gathering the rest of the functions exists, the existing functions will hung up from that function. If that function gathering the rest of the function does not exist, any of those functions could exist without need any association. On selecting one of these options a menu with the suitable radars obtained PSI-2930 from the adaptation shall be dropped-down. On Selecting one of the radars which will appear in the dropped-down menu, the window will display: "Conf TDVM Radar processing for the Mode and selected Radars" For each radar, identified by its name, it shall be possible to visualize the PSI-4337 following information: Primary plots processing configuration state. Secondary plots processing configuration state. Meteorological plots processing configuration state. Manual correction value, range and azimuth, entered by the operator.
Automatic correction value, range and azimuth from the Systematic Error Correction Function. Systematic errors correction state: manual or automatic. Definition (maximum and minimum values) and activation state of the Rho-Zeta filters. The following items shall be able to be configured: - Secondariness Processing: Active/Non Active - Primaries Processing: Active/Non Active - Meteorological Processing: Active/Non Active - Adjustment correction: It could adopt one of the following three states: - 1. Manual: Enabled/Disabled - 2. Automatic: Enabled/Disabled 114 PSI-4402
- Rho-Theta Filters (up to 10): Active/Non Active. The following ranges shall be considered: AZIMUTH of Visual Ranging and Adjustment: They will be modified in case they are referred to the visual ranging and/or manual adjustment. They could include any value within the range -100...+100 (ACPs). RANGE of Visual Ranging and Adjustment: They will be modified in case they are referred to the visual ranging and/or manual adjustment. They could include any value within the range -50...+50 (hundredths of mile). RHO/THETA FILTER AREAS: They will be modified so that, for each area will correspond the following values: 1.Filter Enabler: It will indicate if the filter is Active/Non Active for this area 2.RHO MIN, RHO MAX: It will indicate the RHO values which will be included between 0-270 nautical miles. 3.Az MAX, Az MIN: It will be included between 0 and 360 degrees. The following validations shall be performed: PSI-4404 - The Primaries, Secondaries and Meteorological processing, could be found in any state. - All the Max values must be higher or equals the corresponding Min (except the Azimuth values) From PSI, it shall be possible to inhibit the false plots due to Reflection and PSI-4338 Split filtering functions. This new function shall not affect to the detection, which shall always be PSI-4339 active. A#12852
It shall be possible to disable/enable the filtering for each TDVM Mode, PSI-4340 separately, at two levels: -For each individual radar, from the Processing Configuration window. -Globally, from the technical TDVM Functions Configuration. The function shall be displayed as another option in the corresponding PSI-4341 window in the form of a check-box, allowing a simple enabling or disabling.
Two defined radars lists shall be displayed, grouped for type: DDE or PSI-4342 ASTERIX or SMR (in Tower).
For each DDE radar and for information purposes, the UDDEs and the PSI-4343 associated channels through which each line of the mentioned radar is received, shall be displayed. The PSI operator shall be able to enable or disable the following functions PSI-4344 within the system: AFTN automatic processing Automatic processing of AFTN messages with Route. 115
Automatic processing of AFTN messages without Route. Automatic processing of VFRs messages
The window shall be the same, regardless the selected monitoring. It will PSI-2929 show the following sections: Global filters section Systematic errors correction Geographical filters
This window shall include the following operation buttons: PSI-2927 [Execute]: It will request a confirmation by means of the message " Are you sure of doing this change?". Besides, it will analyse the configuration which has been performed and it will update the new one, in case there aren't any errors. If erroneous values are entered, the message "Edition error" will be displayed. [Analyse]: It will analyse the achieved configuration and if it is correct the message "Correct Analysis" will be displayed. [Exit]: Window will be closed. There will be a non selective text 'Systematic Error Corrections' as a title. On the left of the window a toggle shall exist with the non selective text 'Manual'. On the next horizontal, another toggle with the non selective text 'Automatic'. The state by default of this box 'Manual' shall be not enabled (without the PSI-5204 selective mark) and the state by default of the box will be enable (with selective mark) Both toggles shall be marked/demarked in an independent way. It means, it is PSI-5205 possible to have both box marked, only one or no one of them. PSI-5203
On the right of the window the information concerning to the 'Range (MN)' PSI-5201 shall be displayed, which will be the title of the non selective text which will be displayed in the same horizontal than the text field and both information view frame. The text field can be empty if there are no input value. Concerning to the information view frame, the first of them shall display the last value of the manually introduced range (despite not being selected the option manual ), therefore it will have as title the non selective text 'Man'. The second of them shall display the automatic range value, which will have as title the non selective text 'Auto'. On the next horizontal, it shall be displayed an structure similar to the above PSI-5206 described concerning to the values of 'Azimut()', which will be the title of the non selective text displayed on the horizontal. The text field can be empty if there are no input value. The information view frame shall display the same title of non selective text than the previous described paragraph 116 Software Requirements Description
The four information view frame shall be shaded in blue (different to colour of PSI-5207 the background of the window)
4.1.8.1.2.1. Global Filters section The following global filters for the radar shall be configured: Primary plots, Secondary plots and Meteorological Processing: Active/Non Active The non-configuration of the secondary plots processing in the TDVM in Normal Mode for the local centres, or in the TDVM in Autonomous Mode for the remote centres (without TDVM), for an ASTERIX or DDE radar, will be reflected in the PSI by showing the character "S" over PURPLE background, in the box which represents to this radar. Global filtered of: reflections and split: Active/Non Active. PSI-2928 A#12852
4.1.8.1.2.2. Visual Ranging Corrections Section Both states (manual, automatic) can be enabled/ disabled independently. It PSI-4545 means, we can find both enabled, only one or no one. That shall provoke the following options: - Manual: It will be displayed the correction with the values of range and azimuth entered by the operator. The admitted ranges for this fields will be defined in adaptation data. - Automatic: It will be displayed the correction with the automatically calculated values. - Not enabled: No correction will be displayed - Manual+ Automatic: It will be displayed the correction with the automatically calculated values as with the manually introduced by the operator values.
4.1.8.1.2.3. Geographical Filters Section They could be activated up to a maximum of 10 filters. Filter enabler: Enabled/Disabled Filters could be defined in adaptation data or in a manual way (they won't be kept in the presence of system shutdowns). In this last case, the operator shall indicate the minimum and maximum RHO values, which will have to be included between 0 and 270 nautical miles, and the maximum and minimum Azimuth values should be included between 0 and 360 degrees. PSI-2938
4.1.8.1.3.
DDE/ASTERIX and SMR Radar Input configuration
With this function the input of each defined radars shall be assigned/non PSI-2925 assigned, by means of adaptation data, as system radars. The SMR radars, only will be for premises with radars of surface. Software Requirements Specification 117
This operation shall be of logical type, an the availability of the PSI-2924 aforementioned radar will continue being monitored in the corresponding scenario. Both first and second level texts from the following tables are indicative ( it can be configurable by profile). PSI Functions related with Air Surveillance
1 Level Text Route / TMA Input Radar Configuration Asterix Radars DDE Radars 2 Level Text No Local TMA Asterix Radars DDE Radars Route / TMA Asterix Radars DDE Radars
PSI-2923
Figure 4.1.8.1.3-3 : PSI Functions related with Air Surveillance ( Input Radar Configuration)
The possible functions for the Radar Input Configuration shall be: PSI-7024 F_ENT_RADAR(function gathering the rest of the functions) F_ENT_RADAR_AST (Asterix radars) F_ENT_RADAR_DDE (DDE radars) If the function gathering the rest of the functions exists, the existing functions will hung up from that function. If that function gathering the rest of the function does not exist, any of those functions could exist without need any association.
4.1.8.1.3.1. DDE Radar Input Configuration Window With this function the input of each defined DDE radar shall be PSI-2940 enabled/disabled, by means of adaptation data, as centre radars. The possible options will be the following: [Line assignment in an individual way] PSI-2922 The operator shall be able to click the pointer device with the LB on the label "NON ASSIGNED" , which will be associated with one of the lines, and this one will switch to the "ASSIGNED" state. [Line non-assignment in an individual way] PSI-2921 The operator shall be able to click the pointer device with the LB on the label "ASSIGNED" , which will be associated with the radar or with one of the lines, and this one will switch to the "NON ASSIGNED" state.
[Radar assignment in an individual way] PSI-4415 The operator shall be able to click the pointer device with the LB on the label 118 Software Requirements Description
"NON ASSIGNED" , which will be associated with the radar, and this one will switch to the "ASSIGNED" state, which will imply the assignment of their two associated lines.
[Radar non-assignment in an individual way] PSI-4416 The operator shall be able to click the pointer device with the LB on the label "ASSIGNED" , which will be associated with the radar, and this one will switch to the "NON ASSIGNED" state which will imply the assignment of their two associated lines. [Assignment of everything] PSI-2920 All the radars input shall be enabled, which shall imply the assignment of their two associated lines for all the radars.. [Non-Assignment of everything] PSI-2919 All the radars input shall be disabled, which shall imply the non-assignment of their two associated lines for all the radars. This window shall include the following operation buttons. PSI-2918 [Execute]: Confirmation of the action to be performed will be requested by means of the message "are you sure of doing this change?". If confirmation is performed, it will be processed in case there are not errors, besides performing the analysis of the input assignment. The configured radars states will be updated with the assigned/non-assigned states (without framework/purple framework) in the TDVM scenario. [Exit]: Window will be closed without having processed the configuration.
4.1.8.1.3.2. ASTERIX Radar Input Configuration Window
ASTERIX Radar Input Configuration Window (only tower): With this function the input of each defined ASTERIX radar shall be PSI-2950 enabled/disabled, by means of adaptation data, as centre radars. The possible options will be the following: [Radar assignment in an individual way] PSI-2951 The operator shall be able to click the pointer device with the LB on the label "NON ASSIGNED" , which will be associated with the radar or with one of the lines, and this one will switch to an "ASSIGNED" state. [Radar non-assignment in an individual way] PSI-2952 The operator shall be able to click the pointer device with the LB on the label "ASSIGNED" , which will be associated with the radar or with one of the lines, and this one will switch to a "NON ASSIGNED" state.
119
[Assignment of everything] All the radars input shall be enabled. [Non-Assignment of everything] All the radars input shall be disabled.
PSI-2953
PSI-2954
This window shall include the following operation buttons. PSI-2955 [Execute]: Confirmation of the action to be performed will be requested by means of the message "are you sure of doing this change?". If confirmation is performed, it will be processed in case there are not errors, besides performing the analysis of the input assignment. The configured radars states will be updated with the assigned/non-assigned states (without framework/purple framework) in the TDVM scenario. [Exit]: Window will be closed without having processed the configuration.
ASTERIX Radar Input Configuration Window : With this function the input of each defined through adaptation data radar PSI-6842 shall be enabled/disabled.
The window shall consist of: A primary view frame Operation buttons: execute and exit
PSI-6843
The window shall be requested from the function menu.
PSI-6844
The window shall be requested from TDVM scenario elements which PSI-6846 represent the processors.
The window shall be entitled with the non selective text Input Radar PSI-6847 Configuration. Primary View Frame The first row shall display the non selective text Asterix Radars. PSI-6849
The rest of the primary view frame shall be arranged like a table with four PSI-6850 columns. The number of rows will be number of radars/2.
The first and third column shall display the name of the radars.
PSI-6851
120
The background for the square where the name of each radar is PSI-6852 displayed shall display the colour corresponding to the state of the radar.
The second and the fourth column shall display through a non selective PSI-6853 text the current state of the radar, through a combo-box.
The combo-box shall allow changing the current state, choosing between PSI-6854 the three possible states: Connected, Not Connected. The possible changes of state options will be the following: PSI-6855 See next table.
Table 4.1.6.10.1.3.3-51 : Radar Connection State [Status Change from Operational] ( Green ) PSI-6857 The operator clicking with the left button of the pointer device on Operational shall be able of change the state of the radar to Not Connected (Red). This window shall include the following operation buttons in the last row, PSI-6863 in the second and fourth column: [Execute]: Confirmation of the action to be performed will be requested by means of the message "are you sure of doing this change?". If confirmation is performed, it will be processed in case there are not errors, besides performing the analysis of the input assignment. The configured radars states will be updated with the assigned/non-assigned states (without framework/purple framework) in the TDVM scenario. [Exit]: Window will be closed without having processed the configuration.
4.1.8.1.3.3. SMR (Only tower) Radar Input Configuration Window With this function the input of each defined surface radars shall be PSI-4160 assigned/non assigned, by means of adaptation data, as centre radars. The possible options will be the following:
[Radar assignment in an individual way] PSI-4161 The operator shall be able to click the pointer device with the LB on the label "NON ASSIGNED" , which will be associated with the radar, and this one will switch to an "ASSIGNED" state.
121
[Radar non-assignment in an individual way] PSI-4162 The operator shall be able to click the pointer device with the LB on the label "ASSIGNED" , which will be associated with the radar, and this one will switch to a "NON ASSIGNED" state.
This window shall include the following operation buttons. PSI-4165 [Execute]: Confirmation of the action to be performed will be requested by means of the message "are you sure of doing this change?". If confirmation is performed, it will be processed in case there are not errors, besides performing the analysis of the input assignment. The configured radars states will be updated with the assigned/non-assigned states (without framework/purple framework) in the TDVM scenario. [Exit]: Window will be closed without having processed the configuration.
4.1.8.1.4.
Technical TDVM Functions Configuration
With this function, all the functions to be performed by each available TDVMs PSI-2958 in the centre environment (Normal and all the Autonomous ones) could be configured, in a global way, for all the radars: Normal Mode. This processing shall be performed by the TDVM server directly. Autonomous Mode. This processing will be performed by the EnRoute, or TMA or TWR CWPs when they are configured in autonomous mode. On selecting the Configuration function of Technical TDVM functions a menu PSI-2962 with the following options shall be dropped-down. Normal TDVM Route TDVM TMA TDVM PSI Functions related with Air Surveillance
1 Level Text Route / TMA Normal TDVM Configuration of Technical TDVM functions Route Autonomous TDVM TMA Autonomous TDVM TMA Autonomous TDVM 2 Level Text No Local TMA TDVT TWR Normal TDVM Autonomous TDVM
The possible functions for the Technical TDVM functions Configuration shall PSI-7032 be: F_TDVM_TEC (function gathering the rest of the functions) F_TDVM_TEC_NOR (Normal TDVM) 122 Software Requirements Description
F_TDVM_TE _RUTA (Route Autonomous TDVM) F_TDVM_TEC _TMA (TMA Autonomous TDVM) F_TDVM_TEC_TOR (Autonomous TDVM) If the function gathering the rest of the functions exists, the existing functions will hung up from that function. If that function gathering the rest of the function does not exist, any of those functions could exist without need any association. On selecting any of the menu options, a window where each process showed PSI-2959 below could be enabled/disabled in an independent way, shall be opened: Primary plots Processing Meteorological Processing Test Plots Visualization TF Exclusion for Systematic Errors Calculation Systematic Error Correction Global filtered of Reflections and Split Global filtered A#12852
From the corresponding TDVM startup, 500 multiradar updates shall be PSI-2964 necessary in order to dynamic adjustment information is displayed for each radar. This information will be calculated without taking into account the filter activation state of the dynamic adjustment. This window shall include the following operation buttons: PSI-2965 [Execute]: It will perform an analysis and will process the enabling/disabling , being applied to the available triads. If after a time the configuration it could not have been executed, the message "There is not response of the computer for this function: RDP Functions Configuration". [Exit]: It will shut the window without having processed the configuration.
4.1.8.1.5.
AFTN Automatic Process
It will allow to configure the process provided to the AFTN messages. On selecting this function, the following options shall be displayed: Automatic MSSGs AFTN Process with Route Automatic MSSGs AFTN Process without Route. Automatic VFRs Process PSI-2967
They could be enabled and disabled regardless, by clicking on each current PSI-2968 option by means of the left button of the pointer device. The enabling shall consist of performing the message processing, and the disabling will cause the opposite.
123
This window shall include the following operation buttons: PSI-2969 [Execute]: It will perform a configuration analysis and besides, it will update it in case there is not any error, by displaying the action confirmation window. If after a time, the configuration could not have been executed, the following message will be displayed: "There is not response of the computer for the function: TPV Functions Configuration". [Exit]: The window will be shut without having performed any configuration change.
4.1.8.1.6.
AFTN Lines Configuration PSI-418
It shall allow to Enable/Disable the input of each defined AFTN line.
The window shall be showed on the TCPV scenario.
PSI-2971
On selecting this function the following options shall be displayed: AFTN-1 Line AFTN-2 Line
PSI-2972
An AFTN Line shall be Assigned/Non assigned in an individual way by PSI-2974 clicking on the label "NON ASSIGNED"/"ASSIGNED" with the mouse LB, associated with the line and this one will switch to the "ASSIGNED"/"NON ASSIGNED" state. This window shall include the following operation buttons: [Execute]: It will perform a configuration analysis of the selected configuration and besides it will update it in case there is not any error, by displaying the action confirmation window. If after a time, the configuration could not have been executed, the following message will be displayed: "There is not response of the computer for the function: AFTN Lines Configuration". [Exit]: The window will be shut without having performed any configuration change. PSI-2973
4.1.8.1.7.
Repetitive Flight Plans Configuration
This function shall allow to load a new file of Repetitive Flight Plans in the PSI-420 system.
It shall allow to enable the repetitive FPs files previously configured as "OFF" PSI-2977 in the operator menu of the system.
124
It shall show an action confirmation window with the following options: PSI-2979 [OK]: It will shut the window having performed the RPL's change. If after a time, the configuration could not have been executed, the following message will be displayed: "There is not response of the computer for the function: RPLs Change". In case RPLs as "OFF" do not exist, the message: "There are not new RPLs files" [Cancel]: The window will be shut and the RPL's change will be rejected.
The PVRs change shall not generate any ER.
PSI-4345
4.1.8.1.8.
Physical Configuration PSI-422
This function shall allow configurable devices to switch to not/ available state.
This function only shall be accessible from the contextual menu which will be PSI-2983 displayed after clicking on a configurable device and selecting the function "Physical Configuration" with the RB. The window "Physical Configuration" shall be displayed with the name of the PSI-2984 device where we want to perform the action, the current state of it, and if the change is available. The desired configuration shall be performed: Available or Not Available. See next table. PSI-2995
Dispositivo Configurable
F, SD D F, ND
Control HW: Recuperacin Automtica Control HW: Fallo del Dispositivo PSI: Configuracin Fsica Manual PSI: Configuracin Fsica Manual
D F ND D
Table 4.1.8.1.8-52 : Desired configuration performed following this table. This window shall include the following operation window. PSI-2985 [Execute]: It will accept the new selected configuration, whenever the previous analysis to the execution has not found any error. [Analyse]: A new analysis of the physical configuration will be performed. [Exit]: It will shut the window Physical Configuration without having performed Software Requirements Specification 125
any configuration change. An IFV corresponding to a sectorized SS (CWP in case of TWR scenario) PSI-4440 shall not be allowed to change to Not Available
4.1.8.1.9.
Messages Sending to CFMU Configuration PSI-1385
This function shall allow to configure the kind of messages sent to CFMU.
The messages sent to CFMU shall be the ones whose destination is IFPS PSI-2989 or TACT. These are the following: FPL_AFIL, FSA, AFP, DPI and DEP.
The enabling/disabling of the sending shall be performed by activating or not PSI-2990 the kind of message corresponding to the window of messages sending to CFMU. This window shall include the following operation buttons: [Execute]: The window will be shut after updating the changes. [Exit]: The window will be shut without having performed any change. PSI-2993
4.1.8.2. OPERATIVE CONFIGURATION The following configuration functions could be performed: 4.1.8.2.1. Sectorisation
This function will allow to modify the assignment of responsibilities (sectors) to the centre UCSs as to the remote ones. A mechanism based on the "distributed tables" which will guarantee the correct distribution of this information will exist. When a sectoring is established, an update of the used distributed table will be generated in order to keep the sectoring information. There will be two sectoring ranges: - Global Sectoring, which will gather all sectors and positions of the centre. - Local Sectoring, which will gather sectors and positions belonging to centres defined by adaptation data as self-managing (BDAL.Maintain Centers). Local Sectoring could be performed from any of the positions belonging to the centre, defined as privileged position in adaptation data. Regarding Global Sectoring: PSI-4352 The function shall allow to select among three sectoring types: "Current", standard sectoring (those defined in adaptation) and stored sectoring (those 126 Software Requirements Description
that the PSI operator decides to store). The access to this function could be possible from two different menus which PSI-2998 shall be able to be in the same or in different containers. Current Sectoring: It will allow to modify the sectoring as from the one established in that moment. Other sectorings: they will allow to modify the sectoring beginning from some sectoring which has been previously kept, from the own PSI (kept sectorings) or in adaptation data (standard sectorings). A sectoring shall be characterized by its sectoring label. PSI-4353
Up to 20 standard sectorings could be defined, which shall appear at the top PSI-3000 of the menu, and the last 10 kept sectorings will be saved,and they will appear at the bottom On selecting the corresponding menus, identical windows shall be accessed PSI-3001 and they will show the following information: Name of the selected sectoring Kind of sectoring Configuration Switches: Physical Configuration Local Sectoring (switch and callsign)
When the current sectoring coincides with one of the standard ones, or with PSI-4354 one of the stored ones, its name shall be shown in the menu. When this sectoring is requested, the Type label shall show Current and the Name label shall show the name of the standard or stored sectoring with which it coincides. If the requested sectoring does not coincide with any other, "Current" will appear in the menu as in the Name label. In the Sectoring window the UCSs shall be sorted by centers and, within the same center, by alphabetical order. The centers shall be sorted by alphabetical order. There will be the following options: - The new sector implementation will be performed either respecting or without respecting the selfmanaging centers sectoring, as the operator decides. - It will be possible for the operator to implement the new sectoring by considering or not the physical state of the different critical elements composing the position, such as the support computer and the PDR in Enroute SSs, so that the correct state of these elements is a prior condition for implementing the sectoring. The analysis shall cause the following checkups: PSI-4408 - For a sector assigned to a position, sector and position should belong to the same centre. - An only sector could be assigned to a position. - Sectors must be defined in the current adaptation data. - Physical resources analysis, in case this option has been requested. Every execution will be involved in a previous analysis. Software Requirements Specification 127
Kind of sectoring: this kind of field shall appear when accessing by means of PSI-3005 standard and stored options. Otherwise it will be indicated like in use.
Physical Configuration: In case this field is enabled, previously to the PSI-3006 establishment of the sectoring, a checking of the state of the different critical elements which compose the position, as the support computer and the FPSPs, shall be performed, and a window with the non available UCSs will be displayed and we will be returned to the sectoring window, if it be the case. Local Sectoring: This switch shall be applied when self-manageable centres PSI-3007 and sectors belonging to them, provided by the adaptation data, exist. This switch will allow to modify the sectoring of the self-manageable centres. The self-manageable centres shall be identified and they will show the PSI-3008 Sectoring window through the @ symbol, located before the self-manageable centre name. (These self-manageable centres are configurable from a privileged remote FDD position or TWR POS with access to the sectoring function, allows a Local Sectoring). The sectoring performing shall be limited by the following rules, in the self- PSI-3010 manageable centres from the PSI: If the Local Sectoring callsign is enabled, on trying to execute, the message "Modifications won't be taken into account in privileged selfmanageable centres because of being ON the Local Sectoring. Are you sure of establishing the rest of the sectoring?" will be displayed. On clicking OK the sectoring change which does not affect to the self-manageable centre will be established. On clicking Cancel we will return to the sectoring window. On requesting the sectoring window, the callsign will appear as ON by default. If the Local Sectoring callsign is disabled (OFF) the changes which affect to the self-manageable centres will be executed. The Local Sectoring callsign change shall be performed by clicking on it with PSI-3009 the LB of the pointer device.
The information displayed in the Sectoring window, according to the UCS PSI-3013 shall be the following: POSITION: UCS name, provided in adaptation CENTRE where the POSITION established in adaptation belongs to. ASSIGNED SECTORS to the aforementioned POSITION.
In the sectoring window the UCS's shall be ordered in alphabetical order of PSI-3014 the centre, and within the same centre, they will be ordered in alphabetical order of the UCS order. The desired SECTOR-POSITION assignment shall fullfil the following: 128 For a sector assigned to a position: sector and position must belong Software Requirements Description PSI-3015
to the same centre. A sector only will be able to be assigned to a position. The sectors will be defined in the current adaptation data.
The sectoring information shall be shared with all the positions (PSI profiles PSI-3016 with this available function as PSSO and GLOBAL, or from a remote PCV.
While the sectoring window is opened the changes which could be produced PSI-3017 in the sectoring from another source shall not be updated. Nevertheless, the system will always have the more advanced sectoring established. Selected sectoring, either sector by sector, or all the sectors of a UCS shall PSI-3018 be modified, all at once. For that, the sector of the UCS line whose sectoring is desired to be modified with the LB of the pointer device must be selected. The sector or sectors of this position will be selected automatically. In case we click on each sector with the LB of the pointer device they will give up being selected. Once the desired sectors are selected, on selecting another UCS from the same centre, the assigned sectors will be assigned to this second UCS again. The available sectoring shall be able to be saved. PSI-3019
An option called "Save" shall be available.
PSI-3020
On selecting the Save option, an edition field shall be displayed in order to PSI-3021 enter the name of the sectoring. A sectoring won't be able to be saved with the "Current" name. The following operation buttons shall be available: PSI-3022 [Execute]: Besides performing the modifications analysis, it will process them if errors do not exist. In this case, the Modification Confirmation window will be displayed with the action button OK, which will close the Confirmation window. Immediately, the window of sectoring successfully performed will be displayed with the action button OK which will close it. [Analyse ]: It will perform an analysis of the selected sectoring. [Exit]: it will shut the window without having performed any modification. A message will be sent to be recorded in order to its future exploitation. 4.1.8.2.1.1. Delivery to SCV Sectorization information shall be sent by the Supervision Position (PSI) PSI-4357 towards SCV. This distribution shall be performed in three cases: System start-up 129
SCV start-up Sectorization modification
In case the SCV response of establishment is erroneous, the following ER PSI-4359 shall be generated through the service SrvMwER_Generate: SSTscv001
The use of several environments inside the SSD scenario will generate the need of a modification in the I/F SPV-ADP. At the moment the UCSs identification is a correlative number, but the fact of having several backgrounds and just one SCV forces to identify an UCS with the number of the background to which belong and the local index of the same, this way the SCV could identify without problems the affected UCS, because for this system the UCS of all the backgrounds belongs to the same operative scenario. In SSD backgrounds shall be used the following criteria for UCS enumeration PSI-4450 in the message of sectorization sent to SCV: N. UCS SCV = N.UCS SACTA + ( 100 * N. ENTORNO SSD) The PSI shall know to which background belong through a background PSI-4451 variable with the name ENTORNO_SIMULACION. This variable could have a numeric value between 0 and 2 matching with the number of possible backgrounds in SSD. If this variable is not defined, the UCSs numeration comparing with the SCV will remain like until the moment, it means, ENTORNO_SIMULACION equal to 0.
4.1.8.2.1.2. Operational Configuration The 'Operational Configuration' window shall be accessible just function bar through the "F_CONF_OP" option. from the PSI-6380
The Operational Configuration function identifier for the profile file shall be PSI-6562 F_CONF_OP.
The Operational Configuration function just shall be displayed in those PSI-6563 dependencies where a SMDT Server exist, besides of having the TPVT functionality configured. In a Tower environment PSI (PST) with TPVT functionality the responsibility PSI-6564 objets shall be configured in the same that the sectorization in a PSI window in the Control Centre environment. When the Operational Configuration window is requested the operational PSI-6565 configuration shall be displayed Effective for the Dependencies of Control, attended by PST. 130 Software Requirements Description
The Operational Configuration window shall display the following information PSI-6568 in the PSI: Function bar: it shall display the title of the menu through which it is possible to access to the operational configuration window. Embedded presentation area: it shall be always displayed, it shall display a tap with the name of the Dependency of Control whose operational configuration can be defined from PST. Establish button Close button
Inside the embedded presentation area there will be: PSI-6569 In the left side, Embedded presentation area controlled by the control list of the Available Configuration Area: it shall display the Type and Name of Configurations available for the Control Dependencies which is displayed in the current view (tap). The type available are Effective and Standar, ( the last one just if it has been defined in the Dependencies Areas). - Inside the presentation area in the upper area there will be: SACTA groups area (in the upper region of the area) associated to the Control Dependency displayed in the view (tap). With the no selective title SACTA GROUPS CHANGE MODE selection area shall be displayed in the right side of the presentation area SACTA GROUPS and it will be composed by two mutually excluding sensitive boxes. The title for this area shall be the no selective text CHANGE MODE The no selective text Automatic with an associated sensitive box. The no selective text Manual with an associated sensitive box For the Tower Groups SACTA the effective runway for the associated aerodrome to that SACTA Group (under the SACTA group area). It will be a no selective area titled Runways Configuration followed by the effective runways. In the presentation area in the Central Area there will be: Existing POS list area and state of that through a colours code. If the list were composed by a number of POS which does not allow to display the maximum size in the defined window area, a vertical scroll bar will be defined for that area. Responsibility objects (OR), assigned for every POS in the same horizontal than the POS. Current shall be the generic name given to the operational configuration of PSI-6570 the type Effective whenever that configuration fit with any of the standard ones.
131
Through the selection of the configurations displayed in the available PSI-6571 Configuration areas it shall be possible to modify the presentation in the operational configuration window. The selected configuration will be displayed in the corresponding view and if the available configuration area were stressed in the available Configuration area following the indicated criteria for the display control list. If it were done any manual modification allocating the Responsibility Objects PSI-6572 different from the operational configuration selected in the available configuration areas, that operational configuration shall not be selected. With the aim of identifying if a POS is available or not for being Operationally PSI-6566 Configured, it shall be monitorized using the background colour for the first column in the operational configuration window ( where the name of that POS appear) The possible status for that element (POS) shall be: * GREEN: POS available * RED: POS not available PSI-6567
On any Operational Configuration displayed it will be possible to modify PSI-6573 manually the following actions: It shall be possible to select any OR clicking on it with the left button of the pointer device, that will change to a yellow colour. To select the assigned OR to a position clicking with the left button on the position, all the OR in the position will change to yellow colour. To assign an OR or OR group to a position: 1. OR will be selected 2. The POS will select those OR which are going to be assigned. The Operational Configuration window shall display the following buttons: PSI-6574 Establish: the operational configuration shall establish the operational configuration window before testing that described in the following requirements Establish Operational Configuration. The execution of this function will display a previous informative window as indicated in the requirement Informative window Close: this button allow to close the operational configuration window without executing any action, this button shall be available always.
Operational Configuration Implementation When there is an attempt of implementing an operational configuration, it should be verified if it is feasible and, under certain circumstances, the operator shall generate an alarm in the shape of an acknowledge or error window. The text of the messages which shall be displayed can be found in the following situations: 132 Operational Configuration with Responsibility Objets
PSI-6575
assigned to any POS to failure ( in red colour): Clicking with the button Establish the following acknowledge window shall appear: One or some UCs has been included to failure in the operational configuration: <<(write the list)>> Do you wish to implement the operational configuration anyway? (Buttons: OK/Cancel) The option Accept (OK) will implement the configuration in SACTA and the selected operational configuration will be sent to the SCV. The Cancel Option will return to the operational configuration window. Operational Configuration with Responsibility Objects groups which does not constitute ECU: Clicking on the Establish button the following error window shall appear. Some Responsibility Objects groups or Operative Sectors set up does not constitute ECU This Operational Configuration will not be implemented (Button: OK (Accept)) The Accept option will return to the new operational configuration window. Correct Operational Configuration: Clicking on the Establish button the SACTA configuration shall be established and the selected operational configuration shall be sent to the SCV. Information Window PSI-6577 Once established the operational configuration an information window shall be displayed. Operational Configuration established successfully The Accept option (OK) shall close the window. The following ER shall be generated, through the service SrvMwER_Generate: SSTcop001
The operational configuration shall be established in SACTA independently of PSI-6578 the answer ( accepted/rejected/ without answer) from the system/s SCV or the state from the link/s with that/those system/s To avoid mistakes, if a new operational configuration which does not come PSI-6579 from modifications on the Effective has to be Establish it shall be indicated in the confirmation message that the established will substitute the Effective one. There will be two operatives for the CHANGE MODE: PSI-6580 1.- The MANUAL MODE or AUTOMATIC MODE could be selected ( it shall be named DUAL MODE). 2.- It just can be selected the AUTOMATIC MODE ( it shall be named SINGLE MODE). In this case the option Manual Mode could not be selected. The operative of the CHANGE MODE ( DUAL or SINGLE) in the PSI-6581 Operational Configuration shall be defined by the background variable Software Requirements Specification 133
PSI_CHECK_CONF_OP If that variable exists, we will have the DUAL MODE If the background variable does not exist, we will have the SINGLE MODE. DUAL MODE of CHANGE PSI-6582 In the operational configuration change ( In Tower), the operator shall have the option to chose if the new configuration is manual( the value by default) or automatic. SINGLE MODE of CHANGE PSI-6583 In the operational configuration change ( In Tower), the operator shall not have the option to chose ( the value by default and the only one will be automatic). DUAL MODE of CHANGE If the operator chose the automatic option, it will be verified that the OR groups are kept. If it is not fulfilled the operator shall receive an error and the change will not be allowed. It means, if in the new configuration, an OR is assigned to a position, then every OR in that position, in the previous configuration, also could be assigned to the same position ( although it were a different position in the new configuration), SINGLE MODE of CHANGE The option automatic will remain but it will not test if the OR groups are kept. PSI-6584
When the information with the new operational configuration is spread, it shall PSI-6585 be indicated also if it is manual or automatic .
4.1.8.2.2.
TDVM Functions Configuration
It will allow to configure functions concerning to the TDVM, as the conflicts alert or the automatic transfer. It shall allow to configure the following TDVM functions: Short Term Conflict Alert (STCA) Minimum Safe Altitude Warning (MSAW) Area Proximity Warning (APW) Automatic Hangovers (TA) FLAT Mode (FLAT) NTZ Alerts (NTZ) PSI-3024 A#17182
134
There shall be two possible states: Operative Non Operative
PSI-3025
They shall be included at the moment they are considered as OPERATIVE.
PSI-4405
The window shall consist of: A primary view frame Operation buttons: run, analyse and exit
PSI-6685
PSI-6686
The window shall be requested from TDVM scenario elements which PSI-6687 represent the processors.
The window shall be entitled with the non selective text TDVM function PSI-6691 configuration. Primary View Frame This primary view frame shall be shaped like a table with rows and columns. PSI-6693
For every row the first column shall display a toggle to enable or disable the PSI-6695 function.
The state of the AC, AMIN, AEP, TA, FLAT and NTZ is provided by the PSI-9121 service EvtMwDist_SNETSFuncConfigUpdate.
A#17182 ASC#1000
The first row shall display in the second column the non selective text AC.
PSI-6696
The scond row shall display in the second column the non selective text PSI-6698 AMIN.
The third row shall display in the second column the non selective text AEP. PSI-6699
The fourth row shall display in the second column the non selective text TA. PSI-9097
135
The fifth row shall display in the second column the non selective text PSI-9052 FLAT.
The sixth row shall display in the second column the non selective text NTZ. PSI-6694 The seventh row shall display two toggles, every one followed with a non PSI-6688 selective text. The first one Non Operative. The second one Operative. The following operation buttons shall be available: PSI-3026 [Analyse]: It will perform a change analysis, Operative/Non Operative, of the functions. In this case a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Run]: Besides performing the state change analysis, it will process it in case errors do not exist. In this case, the following window will be displayed: "TDVM Functions change confirmation" with the buttons "OK" and "Cancel", in order to process the change or to re-configure again. Once the change has been performed, a confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
A#17182 A#17182
4.1.8.2.3.
TDVT Functions Configuration ( only tower)
It will allow to configure functions concerning to the TDVT. It shall allow to configure the following TDVT functions: NTZ Alerts PSI-4255 A#17182
The possible states shall be: Operative Non Operative
PSI-4256
The following operation buttons shall be available: PSI-4257 [Analyse]: It will perform a change analysis, Operative/Non Operative, of the functions. In this case a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the state change analysis, it will process it in case errors do not exist. In this case, the following window will be displayed: "RDS Functions change confirmation" with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, a confirmation message will be 136 Software Requirements Description
displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window. The correct execution of the TDVM Configuration function shall generate the PSI-4258 following ER: SSTcfs001
4.1.8.2.4.
SA Configuration (Special Areas) PSI-5736
Special Areas Parameters Configuration From this function the PSI operator (in general, PSSO profile) can obtain information and modify the data corresponding to the special areas. The data that can be modified in an Special Area (Static and Dynamic) shall be: Activity Interval AC Function Configuration AEP Function Configuration. Altitude Limits (lower and upper) Suspended Intervals including De-Suspended
The data for a new creation Dynamic Special Area shall be: Area Identifier Clear AE Name Activity Interval AC Function Configuration AEP Function Configuration. Altitude Limits (lower and upper) Geography of the Area (Circular or Polygonal)
Modification Interval PSI-5737 The 'modification interval' is the period of time when it is allowed to modify configurations in the special areas scenario. The beginning of this interval shall be the current date-time, and the final the current date-time increased in N_DIAS_MODIF_AE days. It shall be considered that an SA has activity period in the 'modification PSI-5738 intervals' configured when at least one or a part of one of its activity period are included in the mentioned interval, it means: ( Date-Current Time) <= (Date- Period Initial Time) < (Date-Current Time+N) ( Date-Current Time) <= (Date- Period Final Time) < (Date-Current 137 Software Requirements Specification
Time+N) *N=N_DIAS_MODIF_AE The SA Configuration window shall consist of: Primary Control Display List where the identifier for every SA shall be displayed. This list will have two associated list with the title 'State' and 'Chronological Order' and it shall control the primary view frame. Sensitive buttons 'New', 'Delete','Close','Modify'. PSI-5210
This SA Configuration window shall be displayed selecting it from the function PSI-5211 menu. The SILV scenario will be displayed if this window is requested to be opened from the function menu. This SA Configuration window shall be accessible from the SILV subsystem PSI-5212 contextual menu .
When the SA Configuration window is requested the first special area PSI-5213 displayed in the control display list shall appear selected by default.
If the primary control display list were composed by a number of SA which PSI-5214 exceed the maximum size of the defined window, a vertical scroll bar shall appear. The information window associated to the 'Special Areas Configuration' main PSI-5248 window shall display the text 'DONE CONFIGURATION CHANGE IN SPECIAL AREAS'.
4.1.8.2.4.1. Primary Control Display List Special Areas Window PSI-5730 If the Special Areas Window is opened the identifier, the current area state and the number of order by activation hour for every Special Area identifier shall be displayed through the event EvtTilais_AllSpecialAreasList. Every existent area in the system will be displayed, independently of having or not the Activity Intervals inside the number of configured days to display the Activity Intervals, with the aim of performing modification over the interval if it were necessary. The SA identifier shall have a maximum of 13 characters ( for dynamics PSI-5688 areas it shall be received from SICV an identifier with more than 8 characters ), the state of SA could be L (Free)/O (Occupied)/S (Suspended)/P (Preactive) and the chronological order could be even 3 numeric characters. Over both related list the labels 'Identifier','State', and 'Activation Order' shall PSI-5731 be displayed, respectively. By clicking over one label the associated to the area identifier-state-order set will be arranged (chronological order of activity), 138 Software Requirements Description
as well as identifier ( alphabetical order), as by states, or by chronological order according with the label where we have clicked. The initial displayed order will be by identifier. The ordering by identifiers shall be just an ascending alphabetic ordination. The ordering by states shall display firstly the areas in the following order: occupied, preactive, suspended, free, displaying in every state area an ordering by chronological criteria, it means, those with priority will be first displayed. The chronological ordering shall refer to its first activity period, in the 'n' configured days; SILV will send the areas in an activation chronological order, starting by OCCUPIED. The chronological ordering will be different to that of the states, because the areas will be displayed by the previous chronological criteria, independently of the state which have, excepting the already occupied, which were the first displayed. When opening the window, the SA total charge service PSI-5689 (SrvTilais_RequestAllSpecialAreasList) shall be requested to SILV and SILV will send the following information through the event EvtTilais_AllSpecialAreasList: Activity chronological order associated to every Area (3 characters) Identifier of every Area (13 characters) State associated with every Area (1 character O / P / S / L.)
The area shall be composed by a list of sensitive box which contain the PSI-5732 identifier with all the SA existing in the system.
These sensitive box (all from SA) shall be initially arranged in alphabetic PSI-5226 order.
On the top as a title the non selective box with the name 'Identifier'. The PSI-5227 edition area shall be a text field
By clicking the 'Identifier' box the rows shall be alphabetically arranged. This PSI-5228 title box shall not be keep selected.
The PSI Operator shall be able, from the configuration window of Specials PSI-5733 Areas: Consult and modify the information from Static Special Areas described in this document. Consult, modify, create and delete, the Dynamic Special Areas described in this document. It shall be possible to do the operations of controlling the presentation copy PSI-5229 (selecting an SA and clicking with selective button 'New'), add, modify and delete, described for the display control list through the selective buttons 'New','Modify' and 'Delete'. Software Requirements Specification 139
The selective button 'Close' shall be always selective, and it will close the SA PSI-5230 Configuration window.
The selective button 'Delete' shall not be selective if the 'Type' (displayed in PSI-5231 the primary view frame) of the selected SA in the primary control display list corresponds to an 'Static' SA. The PSI operator shall be able to perform the following actions from the PSI-5692 Special Areas configuration window: To consult (EvtTilais_AllSpecialAreasList) and modify the Static Special Areas described in this document. To consult (EvtTilais_AllSpecialAreasList), modify (SrvTilais_SpecialAreaModification), create(SrvTilais_DynSpecialAreaCreation) and delete SrvTilais_DynSpecialAreaCancellation), the Dynamic Special Areas described in this document. The selective button 'Modify' shall always be selective. To be precise, the AC and AEP function shall be able to be enabled/disabled, as well as changes in 'Defined Periods' PSI-5232
4.1.8.2.4.2. Primary View Frame For every primary view frame it will exist an associated list with the primary control display list with the following columns: A first column shall consist of an information view frame containing the current PSI-5238 state of the SA with a sensitive box with title 'State', allowing arranging the SA depending on its state. The second column shall consist of an information view frame containing the PSI-5239 SA chronological order and with a sensitive box entitled 'Chronological Order', allowing arranging the AE depending on the chronological order provided by the SILV server. The primary view frame will consist of the next elements: On the left top a non selective title 'SA Name' along with a text field PSI-5217 (maximum number of specified characters) shall contain the name of the SA.
The selection of a displayed area shall cause the request to SILV of a charge PSI-5693 service (SrvTilais_RequestSpecialDeterminedAreaInformation) and SILV will send the following information corresponding to the selected area through the event EvtTilais_SpecialDeterminedAreaInformation:
A#19079
140
SA name- clear. Conflict Alert (Active/Inhibited). Dangerous Space Alert (Active/Inhibited). Day Activity Period (IA) State of the volume. Lower and Upper Levels. Type of Activity (ACT) (Active, Inactive) Information Source. NOTAM C or Supplement Suspended Period (IS) Geography of area that can be Polygonal or Circular.
Geography of the Area PSI-5695 After having requested the service of charge an Area it shall be displayed the geography of this Area, being this one defined by the data that are indicated from now on depending if it is a circular or polygonal area: Circle 1. Latitude-centre 2. Longitude-centre 3. Radium Polygon 1. Latitude POINT 1 2. Longitude POINT 1 3. Latitude POINT 2 4. Longitude POINT 2 5. Latitude POINT 3 6. Longitude POINT 3 7. .... That is all the points composing the Geography of the Area ( minimum number and maximum number of points defined in R-20)
IA-IS PSI-5696 After requesting the service of charge from an Area it shall be displayed: For every day in the "n" configured (N_DIAS_MODIF_AE): 1. Week day ( S,M,T,W,F,S,) (DAY) 2. Activity Interval ( IA-1,IA-2, ... until IA-15 ), for the N_DIAS_MODIF_AE 3. Period State 4. Flight Level ( lower and superior level) (ALT) for every interval 5. Type of activity period (ACT: I/A) 6. Information Source (FTE) for every interval 7. Source of the VILMA NOTAM (NOTAM/Sup) 8. Suspended Interval (IS-1, IS-2, ... , until IS-15 for an IA ) for the Software Requirements Specification
A#19079
141
N_DIAS_MODIF_AE
The edition area in the Special Areas window shall contain the parameters of PSI-5694 definition of an AE: - Special Area Name ( Name of the AE): Maximum of 40 characters. It can be filled if it is a creation (only Dynamic Areas), it could not be modified if it is a modification (of Static AE or Dynamic AE). This is an optional field. - Kind of AE: Dynamic/Static. It shall be always filled, the AE created from the PSI only could be Dynamics. - AC Configuration "Conflict Alert" (AC). It is toggle. The possible values are 'ACTIVE' or 'INHIBITED'. -AEP Configuration "Dangerous Space Alert" (AEP). It is a toggle. The possible values are 'ACTIVE' or 'INHIBITED'. -Geographic coordinates of Definition of Area , Circular (or geographic reference Centre-Radio Geography) or Polygonal. It shall be non modifiable fields in the action of modifying an AE. o Circular( Geographic Reference)-Centre and Radio(toggle): Centre Latitude: Composed by 6 numeric characters and a letter ("N" or "S" ) GGMMSSX, where GG are the degrees , MM are the minutes, SS are the seconds and X is "N" for North and "S" for South (with a precision of seconds). The precision for the geographic reference is fixed in minutes, but for polygonals in points; it could be necessary enlarge here to seconds. NOTE: Nevertheless SILV will have an intern precision until hundredth of seconds. Centre Longitude: Composed by 7 numeric characters and a letter ("W" or "E" ) GGMMSSX, where GG are the degrees , MM are the minutes, SS are the seconds and X is "W" for West and "E" for East (with a precision of seconds). NOTE: Nevertheless SILV will have an intern precision up to hundredth of seconds. Radio: Composed by 3 numeric characters RRR where RRR is the radio of the circumference which define the bound of the area in nautic miles. o Polygonal-points: Composed by at less 4 points (the last is equal to the first to close the bound). The maximum number of points which form the polygon is 20+1 (the last match with the first one). The position of those points is defined by: 142 Point Latitude: Software Requirements Description
Composed by 6 numeric characters and a letter ("N" or "S" ) GGMMSSX, where GG are the degrees , MM are the minutes, SS are the seconds and X is "N" for North and "S" for South (with a precision of seconds). NOTE: Nevertheless SILV will have an intern precision until hundredth of seconds. Point Longitude: Composed by 7 numeric characters and a letter ("N" or "S" ) GGMMSSX, where GG are the degrees , MM are the minutes, SS are the seconds and X is "N" for North and "S" for South (with a precision of seconds). NOTE: Nevertheless SILV will have an intern precision until hundredth of seconds.
Defined Periods. It shall be displayed just the activity period which have place inside the "modification interval" grouped by days of the week, and displayed by chronological order of IA (day-hour). The maximum number to display will be 20. NOTE: There may be no activity interval for the area, in which case the levels or the source, or any interval of suspension would not have sense. For every defined period there will be: o Day of the week (S, M,T, W, T, F, S). When a new IA is created by default the current day will appear by default. Always filled. o Activity Interval (IA). Format: Initial Time HHMM - Final Time HHMM. Where HH are hours and MM are minutes. o Lower and Upper Levels (ALT). Format: FIII-FSSS. Where III is the lower altitude and SSS is the upper, measured in hundred of foot. o Activity Interval Source (FTE of IA) Range of Values: PSI / AIP / NOTAM-SNNNN/YY (where S is the serie of the NOTAM, NNNN is the number of NOTAM and YY is the year). If the interval has been modified or created by the PSI the value shall be 'PSI'. o Suspended Intervals (IS). Format: Initial Time HHMM - Final Time HHMM. Where HH are hours and MM are minutes. The maximum number of suspended intervals by interval is N_MAX_INT_SUSP, defined by configuration.
In the same horizontal but separated by the previous elements there shall be PSI-5218 a non selective text 'Type' and, next an information view frame indicating the kind of selected area. Software Requirements Specification 143
In the next horizontal, a toggle shall be displayed with the non selective text PSI-5219 'AC', to information concerning the configuration of the function Conflict Alerts
Next to the previous toggle shall be displayed another toggle with the non PSI-5220 selective text "AEP", to information concerning the function of Dangerous Space Alert. Secondary Control Display List will control the secondary view frame. 4.1.8.2.4.3. Secondary Control Display List The list will consist of elements containing the different options in the configuration for every special area. These configuration options are: A non selective text "SA Geography" and an information view frame which PSI-5242 shall be empty or with a symbol similar to the one of the toggles. The existence of this symbol will indicate if there are an embeded presentation area containing information concerning to the SA geography. A non selective text "Defined Period" and a information view frame which PSI-5243 shall be empty or with a symbol similar to the one of the toggles. The existence of this symbol will indicate if there are an embeded presentation area containing information concerning to the activity period of AE. By default, when a box from the primary control display area is selected, the PSI-5244 box from the secondary control display area 'Defined Period' shall appear already selected, displaying its corresponding secondary control display area. On the secondary control display list it shall be possible to make the operation PSI-5245 of controlling the display.
4.1.8.2.4.4. Secondary view frame Next it will be displayed the associated design to the remaining sensitive box: 4.1.8.2.4.4.1. SA Geography
If 'SA Geography ' has been selected in the secondary control display list the PSI-5317 secondary view frame shall consist of: Terciary Control Display list controlling the terciary view frames Selective buttons 'Modify' and 'Empty'.
Terciary control display list The terciary control display list shall consist of sensitive box, with the options PSI-5319 'Circular' or 'Polygonal'.
144
With every sensitive box an information view frame shall be displayed, this PSI-5320 area could be empty or with an analogous symbol to the mark in the selective mark box. If an area is marked it means that the terciary view frame associated are or not completed with information. The symbol of marked (associated to the non selective text 'Circular' or PSI-5321 'Polygonal')shall be deleted not only with 'Empty' on the sensitive box associated, but also by the action 'Modify' on the sensitive box which exists on the list ( Note: The Static SA cannot change its geography). By creating a Dynamic SA from another of reference, if data are introduced in PSI-5697 the field corresponding to 'Geographic Reference-Activity Area' shall provoke the deletion of the data (in case of exist having it) from the field corresponding to 'Polygonal-Activity Area'. By creating a Dynamic SA from another of reference, if data are introduced in PSI-5698 the field corresponding to 'Polygonal-Activity Area' shall provoke the deletion of the data (in case of exist having it) from the field corresponding to 'Geographic Reference-Activity Area'. The selective box selected by default shall be the corresponding to PSI-5322 'Polygonal'. It will be possible to do the operations of controlling the presentation, modify and delete all the information associated to any of the two displayed options displayed in the terciary control display list. The modifications which shall be carried out on the terciary control display list PSI-5324 are specified in this document (see link). Circular-Terciary View Frame: This area shall consist of, a non selective text 'Circular Geography' as title PSI-5326 of the view frame.
This area shall consist of a non selective text 'Latitude-Centre PSI-5327 (GGMMSS)' as title and an associated text field containing information about the latitude of the centre (6 numeric characters) and, next, a combo box where select two options, "N" ( information for latitude concerning to the North) or "S" (concerning the South). This area shall consist of a non selective text 'Latitude-Centre(GGMMSS)' PSI-5328 as title and an associated text field containing information about the longitude of the centre (6 numeric characters) and, next, a combo box where select two options, "N" ( information for longitude concerning to the North) or "S" (concerning the South). This area shall consist of a non selective text 'Radio(MN)' as title and an PSI-5329 associated text field containing information about the latitude of the centre (6 numeric characters) and, next, a combo box where select two options, "N" ( information for latitude concerning to the North) or "S" (concerning the South). Software Requirements Specification 145
Terciary-Polygonal view frame: This area shall consist of, a non selective text 'Polygonal Geography' as PSI-5332 title of the view frame.
The area shall consist of a list composed by boxes with: A non selective text 'Latitude-POINTnum (GGMMSS)' (where num is numeric character)as title and an associated text field containing information about the latitude of the centre (6 numeric characters) and, next, a combo box where select two options, "N" ( information for latitude concerning to the North) or "S" (concerning the South). A non selective text 'Longitude-Centrenum (GGMMSS)' as title and an associated text field containing information about the longitude of the centre (7 numeric characters) and, next, a combo box where select two options, "W" ( information for longitude concerning to the West) or "E" (concerning the East).
PSI-5333
The list shall be arranged by box as follow: Latitude-POINT1, Longitude- PSI-5334 POINT1, Latitude-POINT2, Longitude-POINT2, ... Latitude-POINT2, Longitude-POINT20.
If the size of the list surpass the maximum size of the defined window, a PSI-5335 vertical scroll bar shall appear.
4.1.8.2.4.4.2.
Defined Period
If 'Defined Period ' has been selected in the secondary control display list the PSI-5337 secondary view frame shall consist of: Terciary Control Display list controlling the embeded view frame. Selective buttons 'New','Modify' and 'Empty'.
4.1.8.2.4.4.2.1. Terciary Control Display List This area will consist of the following elements: A non selective text as title 'Activity Intervals' and a list composed by the PSI-5703 following columns:
o the first column shall have the non selective text "DAY" and shall PSI-5342 consist of information view frame where is displayed the initial letter of the day in the week (S,M,T,W,T,F,S) to which the information associated to this row is referred. A combo box is the edition area associated to that column. 146 Software Requirements Description
When a new activity interval is created, the initial letter of the the current day PSI-5343 associated to the column 'DAY' shall be the option displayed by default in the combo-box. o the second column shall have the non selective text "IA" and shall consist PSI-5344 of sensitive box where is displayed the initial and final time which defined the activity interval (HH:MM(initial)-HH:MM(final). The edition area associated to that column shall consist of four spin-box. First spin-box: HH (initial), second spin-box: MM (initial), third spin-box: HH (final), fourth spin-box: MM (final). Between the spin-box we can find the necessary punctuation marks to express the schedule format as a non selective text, as displayed in the design of the window.
o the third column shall have the non selective text "STA" and shall consist PSI-9139 of non-sensitive box where is displayed the states of the volumes defined. Available states will be: Occupied (O) Preactive (P) Suspended (S) Free (F)
A#19079
o the fourth column shall have the non selective text "ALT" and shall consist PSI-5345 of information view frame containing the levels of lower and upper altitude (FIII-FSSS). The edition area associated to that column shall consist of two spin-box consecutive, the first containing the inferior altitude level (III, 3 digits) and next the second containing the upper altitude level (SSS, 3digits). Between the spin-box we can find the necessary punctuation marks to express the schedule format as a non selective text, as displayed in the design of the window. When the modification associated to the 'ALT' column are saved it shall not PSI-5346 be necessary to have values selected in the spin-box for this column. If any menu or both has not been selected, it shall be filled with FIII, FSSS or FIII and FSSS defined by default. o the fifth column shall have the non selective text "ACT" and shall consist PSI-9168 of an information view frame displaying the type of activity interval for the corresponding time period. The row will not have associated any edition area, due to the value taked will be Active (A) or Inactive (I). o the sixth column shall have the non selective text "FTE" and shall consist PSI-5347 of an information view frame displaying the source which has generated the activity interval (IA) defined to that row. Software Requirements Specification
A#19079
A#19079
A#19079
147
The row will not have associated any edition area, due to the value taked will be 'PSI' if the creation/modification is from PSI. o the seventh column shall have the non selective text "NOTAM/Sup" and PSI-9140 shall consist of an information view frame displaying the NOTAM C or Supplement that originates the VILMA NOTAM. The row will not have associated any edition area, due to the value taked will be empty if the creation/modification is from PSI. Format of the information contained in this field will have the following format: Cxxxxxxx for the NOTAMC C Identifier. SUPxxxxx for the Supplement Identifier. A#19079
The maximum number of rows in the list shall be defined by configuration.
PSI-5348
It shall be possible to do the operations of creating a new IA from zero (no PSI-5349 sensitive buttons "New"), creating a new IA from one already created ( IA selected and clicking the sensitive button "New"), modifying an IA ( IA selected and clicking the sensitive button "Modify") and deleting an IA ( IA selected and clicking the sensitive button "Delete"). The sensitive button "New" shall be selective only if the number of lines in the PSI-5350 terciary control display list is smaller than the maximum number of IA to display in the PSI. Parameters in the configuration file: N_DIAS_MODIF_AE: Number of days from current date/time in the system where the modifications of Special Areas ( Static and Dynamics) shall be displayed, the parameter shall indicate the number of days (Integer), it possible range shall be from 1 to 6 (included). The value by default will be 2 days. N_MAX_INT_SUSP: Maximum Number of suspended intervals for an Special Area ( Static and Dynamic) in busy state ( activity period) will be from 1 to 5 (included). N_MAX_PER_ACT_DIA: Maximum Number of activity period to display in the PSI, which can be defined for one day in a special, it possible range will be from 1 to 15. area The maximum number of total intervals by day will be of 20. If the total number of intervals tried to display at one surpass the number of 20, this fact will be remark in the AE configuration window, as specified on the link. Those parameters will be included in the configuration files (Under control version) 148 Software Requirements Description PSI-5701
A new activity period shall be created just if the maximum number of activity PSI-5702 periods defined in configuration by day for an Area (N_MAX_PER_ACT-DIA) has not been reached. PSI verify it. The sensitive button "Modify" and "Delete" shall be selective if there are any PSI-5351 IA selected.
If the terciary control display area shall be composed by a number of IAs PSI-5352 which is bigger than the maximum size of the defined window, a vertical scroll bar which affect to that area will appear, and its embeded presentation area is following described:
4.1.8.2.4.4.2.1.1. Embeded presentation area The embeded presentation area will consist of : A non selective text 'Suspended Interval' PSI-5355 A list with the same number of rows than the control display area which control it. Sensitive buttons "New" and "De-Suspended"
The list is composed by the following columns: the eighth and ninth columns shall have as title the non selective PSI-5357 texts "IS-1" and 'IS-2' and it will be composed by sensitive box with the initial and final time which define the suspended interval (HH:MM(initial)HH:MM(final)). This areas could also be empty but the columns 'IS-1' and 'IS2' will be always visible From a tenth to a twelfth column could exist (the number of existing columns PSI-5358 shall depend of the number of Suspended Interval configured). The format of the columns will be the same to the one described for the 'IA' column, and the titles with the non selective texts shall range from 'IS-3' to 'IS-5'. If all these columns are not visible in the width of window displayed, a horizontal scroll bar will appear, which will affect just the embeded presentation area. . A#19079
A#19079
The edition area associated shall be composed by four combo box containing PSI-5359 the values with the suspended intervals. It also shall contain the non selective texts displaying the punctuation marks to consider the schedule format. First combo box: HH (initial), Second combo box: MM (initial), Third combo box: HH (final), Fourth combo box: MM (final). The above mentioned edition area will be lightly separate from the list because it is not associated to any particular column in the same. It means, the action of create a new suspended interval is related with the
149
selection of an IA of the terciary control display area and clicking the sensitive button "New" from the embeded presentation area which is been here described. The first IS created shall place the first empty column associated to that PSI-5361 selected IA.
The operation of creating a new IS and delete an IS (IS selected and clicking PSI-5362 the sensitive button "De-suspended") shall be performed with the described procedure. The sensitive button "New" shall be selective just if the number of lines in the PSI-5363 embeded presentation area is smaller than the maximum number of IS defined for a IA, and also an IA has been selected. The sensitive button "De-Suspended" shall not be selective if it has not been PSI-5364 defined IS or any of the existing has not been selective. The terciary control display area and it embeded presentation area could be empty. It means, it is possible to create AE without IA associated. Modification of an AE: PSI-5739 In the modification of an AE the parameters of definition in an Area shall have the following properties: - Field 1: Name of the Area Non modifiable field - Field 2: AC Configuration Modifiable field: Enbable/Disable Initial Value: AC Configuration in the selected area - Field 3: AEP Configuration Modifiable field: Enbable/Disable Initial Value: AEP Configuration in the selected area - Field 4: Activity Area-Circular (Geographic Reference): Non modifiable field - Field 5: Activity Area-Polygonal Non modifiable field - Field 6: Defined periods o Day on the week Modifiable field. o Activity Interval IA: schedule interval which defined the activity period Initial-Time to Final-Time Modifiable field: activity interval period o State STA: state of the corresponding volume Non Modifiable field: Occupied (O), Preactive (P), Suspended (S), Free (F) o Interval of levels affected by that activity: Lower Level-Upper Level Non modifiable field. o Activity Interval Source: Non manually modifiable field; it will be modify automatically if the Activity interval is modified, because the source 150 A#19079
change to be 'PSI'. o NOTAM/Sup: Source of the VILMA NOTAM Non manually modifiable field; it will be modify automatically if a NOTAM is received'. o Type of Activity: Type of activity interval Non manually modifiable field; it will be modify automatically if a NOTAM is received'. o Suspended Intervals defined for that Interval: Non modifiable field. It is only possible to enter new Suspended Intervals.
Creation of an Dynamic Special Area 'from empty': PSI-5740 In the creation of an AE the parameters of definition in an Area shall have the following properties: - Field 1: Area Identifier Modifiable field Compulsory. Initial value: "PSImmmmmmmmmm", where the three first character will be fixed (PSI) and the rest will correspond to the Unix hour of the creation. - Field 2: Name of the Area Modifiable field Initial Value:"Empty" - Field 3: Kind of Area Non modifiable field Value: "Dynamic". - Field 4: Current State of the Area Non modifiable field Initial Value:"Empty" - Field 5: AC Configuration Modifiable field Initial Value: 'Inhibit' - Field 6: AEP Configuration Modifiable field Initial Value: 'Active' - Field 7: Activity Area-Circular (Geographic Reference): Modifiable field Initial Value:"Empty" - Field 8: Activity Area-Polygonal Modifiable field Initial Value:"Empty" - Field 9: Defined periods o Day on the week Modifiable field. Initial Value: Initial of the current day. o Activity Interval IA: Modifiable field Software Requirements Specification
A#19079
151
o Level
Initial Value:"Empty" State STA: state of the corresponding volume Non modifiable field: Initial Value: "Empty" Interval of levels affected by that activity: Lower Level-Upper
Modifiable field. Compulsory (if it is not filled, it had to be generated as 000 to 999) Initial Value:"Empty" o Activity Interval Source: Modifiable field o NOTAM/Sup: Source of the VILMA NOTAM Non manually modifiable field; Initial Value: "Empty" o Type of Activity: Type of activity interval Non manually modifiable field; Initial Value: "Empty" o Suspended Intervals defined for that Interval: Modifiable field. Initial Value:"Empty"
Creation of an Dynamic Special Area from a reference : PSI-5741 In the creation of an AE the parameters of definition in an Area shall have the following properties: - Field 1: Area Identifier Modifiable field Compulsory. Initial value: "PSImmmmmmmmmm", where the three first character will be fixed (PSI) and the rest will correspond to the Unix hour of the creation. - Field 2: Name of the Area Modifiable field Initial Value:"Empty" - Field 3: Kind of Area Non modifiable field Value: "Dynamic". - Field 4: Current State of the Area Non modifiable field Initial Value:"Empty" - Field 5: AC Configuration Modifiable field Initial Value: value (Enabled/Disabled) of the AC field of the selected area as reference. - Field 6: AEP Configuration Modifiable field Initial Value: value (Enabled/Disabled) of the AC field of the selected area as reference. - Field 7: Activity Area-Circular (Geographic Reference): 152
A#19079
Modifiable field Initial Value: Value of the position (latitude/longitude) of the centre (with accuracy of seconds) and the value of the radio ( in nautic miles) of the circle (Geographic reference) of the selected area as reference, it can be empty. Note: SILV will have an inner accuracy until hundred of second. The modification of any of this values will provoke the delete of the field 'Polygonal-Activity Area' - Field 8: Activity Area-Polygonal Modifiable field Initial Value: Value of the position (latitude/longitude) of the different points which form the polygon which define the selected area as reference (accuracy of seconds), it can be empty. Note: SILV will have an inner accuracy until hundred of second. The modification of any of this values will provoke the delete of the field 'Circular-Activity Area' - Field 9: Defined periods It is composed by the different periods of activity which were inside the 'modification interval' defined in the Selected Area as reference. The initial value for this field will be the activity period in the selected area as reference gathered by day of activity, and chronologically ordered by IA (day-time); the suspended interval will not be displayed, if the selected area had. It will be grouped by days, and for every activity period we will have: o Day on the week Modifiable field. o Activity Interval IA: Modifiable field Initial Value:"Empty" o Interval of levels affected by that activity: Lower Level-Upper Level Modifiable field. Compulsory (if it is not filled, it had to be generated as 000 to 999) Initial Value:"Empty" o State STA: state of the corresponding volume Non Modifiable field: Initial Value: "Empty" o Activity Interval Source: Modifiable field Value 'PSI' o NOTAM/Sup: Source of the VILMA NOTAM Non manually modifiable field; Initial Value: "Empty" o Type of Activity: Type of activity interval Non manually modifiable field; Initial Value: "Empty" o Suspended Intervals defined for that Interval: Modifiable field. Initial Value:"Empty"
153
When a Special Area is created or modified, besides the checking of the PSI-5742 format and range of every text field, several checkings detailed in the requirements shall be performed. If any checking is not fulfilled, an error message shall be generated informing about the situation and the impossibility to accept the change. Only Dynamic SA shall be able to be created or modified. PSI-5743
When a Dynamic SA is created, it shall be verified that the identifier does not PSI-5744 match with another that already exists
When creating a Dynamic SA, format (all fields filled with a numeric value) PSI-5745 and range (minutes and seconds ranging between 00 and 59, degrees ranging between 00 and 90 (N and S) for the latitude and between 000 and 180 (E and W) for the longitude) of Latitude, Longitude and Radio shall be validate by the PSI for the field corresponding to 'Circular Activity Area'. In the creation of a Dynamic SA, not only the format but also the range of PSI-5746 Latitude/Longitude of every point ( minutes and seconds between 00 and 59, degrees between 00 and 90 (N and S) for the latitude and between 000 and 180 (E and W) for the longitude) will be validate. Likewise, the number of points which define if the bound is equal or bigger than the minimum (4 points), and equal or smaller than the maximum (20 points), with the last point matching with the first. This point shall be introduced by the PSI operator. In PSI format and range are validated. SILV shall validate that the polygon is correct. In the modification of an SA / creation of a Dynamic Area, regarding to the PSI-5747 field initial time of an activity interval: If the interval is Active ( Date-Initial Time <= Date- Current Time <= Date- Final IA Time) it is not possible to change it DATE-Initial Time. (only in modification, yes in creation). PSI will validate it. PSI shall verify that (Date- New IA Initial Time) < (Date-Final IA Time) whenever 'Date-Final IA Time' is defined. PSI shall verify that. - if the interval is not Active, the New IA Initial Time shall be in the 'modification interval' so that ( Date- Current Time) <= (Date- New IA Initial Time) < ( Date- Current Time + N_DIAS_MODIF_AE) PSI shall verify if the interval of levels is defined, The overlap between Activity Intervals (IA) in the creation or modification of AE, it means it is not allowed to generate an overlap with one of the already existents, SILV will make this verification. Finally, if the Activity Period has defined any suspended interval it will be verify in (SILV) for every defined suspended interval if it is affected by the modification of the Date- Initial Time: - if ( Date-New IA Initial Time) >= ( Date - IS Final Time) the suspended interval will be deleted - if it is not that way, but ( Date-New IA Initial Time) > ( Date - IS Initial Time), the interval will be modified starting this at the same time the Activity Interval (Date-Initial IS Time)= (Date-New IA Initial Time) 154 Software Requirements Description
If the Initial Time is not defined the Final Time for the Activity Interval shall not PSI-5748 be defined. PSI will test it.
In the modification of an SA / creation of a Dynamic Area, regarding to the PSI-5750 field final time of an activity interval: It will be checked in PSI that ( Date-Initial IA Time) < ( Date- New Final IA Time). PSI shall verify that (Date- Current Time) < (Date- New Final IA Time) <= (Date-Current Time+ N_DIAS_MODIF_AE). PSI shall verify if the interval of levels is defined (if it is not filled the value will be 000-999). Finally, if the Activity Period has defined any suspended interval it will be verify in (SILV) for every defined suspended interval if it is affected by the modification of the Date- Final Time: - if ( Date-New Final IA Time) <= ( Date - Initial IS Time) the suspended interval will be deleted because it will not be effective in the next activity period. - if it is not that way, but ( Date-New IA Final Time) > ( Date - IS Final Time), the suspended interval will be modified ending this at the same time the Activity Interval (Date-Final IS Time)= (Date-New IA Final Time)
In the modification of an SA/ creation of an Dynamic SA, regarding to the PSI-5751 Lower Level and the Upper Level for an activity period. PSI shall test that (New Lower Level) < (New Upper Level). It will be verified that ( Current Time-Date) < (Date- New IA Final Time) <= ( Date- Current Time + N_DIAS_MODIF_AE) It will be verified if the activity interval is completely defined, that with the New Levels Interval there are not an overlap of the modified activity period with the rest of period with different levels defined. From PSI it shall be generated the levels 000-999 it those fields are not filled. If a new IS is inserted PSI shall verify: The maximum number of suspended interval by activity period (N_MAX_INT_SUP) defined by configuration. It shall be test that (Date- Current Time) <= ((Date-Initial IS Time)<(Date-Final IS Time)) It will be checked that the values are in the activity interval of the activity period selected in a way that: (Date-Initial IS Time) >= (Date-Initial IA Time), and (Date- Final IS Time) <= (Date-Final IA Time) It will be checked that values in the activity suspended interval are not overlap with the rest of defined suspended interval for that activity period. It will be checked for every suspended interval "i" already defined that: (Date- New Initial IS Time) >= (Date-Final IS i Time) or (Date- New Final IS Time) <= (Date-Initial IS i Time) Software Requirements Specification 155 PSI-5753
It is possible to deleted any Activity Interval which display in the window the PSI-5754 configuration of AE, independently of it source ( origen: AIP, NOTAM or PSI), and it elimination shall involve the deletion of that Interval of the window of AE Configuration It is not allowed to save (send to SILV) the change performed in an area if any PSI-5755 field is not defined ( excepting field 7 which can be empty if the field 6 is defined, or, the field 4 and the field 2- Clear Name of the Area). A message with the no defined field shall be generated. The manual configuration of the Special Area Parameters shall generate, PSI-5752 through the service SrvMwER_Generate, the following ER: PSIcae001 SSTcae001 (Only Tower)
4.1.8.2.4.4.3.
Message Windows
Associated Error Window If the operations described over the windows are done and it is necessary to PSI-5367 save it, the SILV server shall perform several verifications about the entered information in the windows, with the aim of avoid to save information with a format no valid, with empty field, with modification in field where that is not possible, etc. If the testing are not satisfactory an error window will be generated with information about the situation. An Error Window associated to the introduction of no valid information in any PSI-5368 field, due to an entered value which surpass the maximum or minimum in the range of this field or due to a no valid introduced format. This error message shall be associated to the text field in the windows and shall display the text 'Edition Error'. When the Error Window is accepted, in the AE Configuration window shall be reflected in any way the field where the error happened and had to be corrected. An Error Window shall be displayed associated to the attempt of introducing a PSI-5369 new IA or IS when the maximum defined ((IA+IA) = 20 for a day). The message will be 'The maximum limit of interval allowed for a day has been reached'. This message will be displayed just when the last IA or IS created make IA+IS=20. An Error Window associated to the attempt of modifying the geography of an PSI-5370 static or dynamic AE previously created ( it means, not new) shall be displayed. The message will be 'It is not possible to modify the geography of an AE already created'.
156
Acknowledge window associated An acknowledge window shall be associated if a new SA has been created PSI-5372 (from zero or with another SA as reference) and it is tried to close the selection of that SA whose field 'Name of the SA' has been filled. The acknowledge will be requested if the window has to be close without having filled that field. Associated Information Window. The Information Window associated to the main window 'Special Areas PSI-5374 Configuration' shall display the text 'DONE CHANGE IN SPECIAL AREAS CONFIGURATION' Another Information Window shall be open if a selected AE has more than 15 PSI-5375 activity periods defined in a day. The informative message shall be 'It is not possible display every IA in the selected AE'.
4.1.8.2.5.
Operative Configuration of Adjacent Centre
It shall allow to enable or disable the communication with each adjacent PSI-434 centre (dialogue via computer/computer).
This function shall allow to enable or disable the TLPV/TLPV dialogue (OLDI PSI-3034 messages), from the Control Centre with the Adjacent Centres (national and foreign). The Adjacent Centres which shall be displayed come provided by the PSI-3038 Adaptation Data according to the centre.
A adjacent centre shall be considered Operative when the dialogue with the PSI-3037 aforementioned adjacent centre is configured, and it will be considered Non Operative when the dialogue with this adjacent centre is not configured. The following operation buttons shall be available: PSI-3039 [Analyse]: A change of configuration analysis shall be performed. In this case a window which confirms the analysis correction shall be displayed. The button "OK" shall shut the window. [Execute]: Besides performing the change analysis, it shall be processed in case errors do not exist. In this case, a window of change confirmation shall be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, a confirmation message shall be displayed indicating the change has been performed. The button "OK" of this window shall close the window. [Exit]: It shall close the window.
157
4.1.8.2.6.
Aerodrome Parameters Configuration
This function shall allow to change parameters related to a specific Centre PSI-4423 Aerodrome.
The Aerodrome Parameters Configuration shall be performed according to PSI-4424 the existence of the adaptation data generated for the selected Aerodrome.
This function shall allow to show the parameters associated with the PSI-436 aerodromes, and also to configure the active runway.
It shall be possible to modify the Departure and Arrival runway fields, as PSI-4392 well as to enter a list of callsigns corresponding to flights affected by each modified departure runway. It shall also be possible to enter a list of flights which should NOT be affected. The following parameters shall be visualized: Aerodrome RUNWAYS CHANGE Departures 1/2 Arrivals 1/2 Flights affected by the departure runway 1 change (Coordinated) Flights affected by the departure runway 2 change (Coordinated) PSI-3040
And the operation buttons detailed further on will be available. In order to visualize the parameters the OACI callsign of he desired PSI-3042 aerodrome must be entered into the Aerodrome field, by means of the keyboard. Afterwards, Analyse or Execute buttons shall be selected. If the aerodrome callsign is accepted, their Departure and Arrival Runways will appear. Otherwise, the corresponding error message will be displayed and the Aerodrome field will have to be edited again. Departure and Arrival runways shall be modified taking into account the PSI-3046 indicated below:
The departure runways change shall only affect to flights in Pending PSI-3043 state. If it be tried some flight in Coordinated or Preactive state is affected, a new field callsign would be edited. "Flights Affected by the departure runway change". In order to fill in the Affected Flights field we could act in the following two ways: 158 Software Requirements Description
By editing the flights which are in Coordinated or Preactive state, and which will be affected by the departure runway change, separated by a blank. By writing the "T" symbol, a blank and the callsigns of the flights NON affected by the departure runway change. All the flights in Coordinated or Preactive state, except the ones already entered, will be affected by the departure runway change. The departure runways change shall be notified through the printing PSI-3045 of new coordination strips, for flights in Coordinated or Preactive state. The arrival runways change shall affect to all the flights which land on PSI-3047 the Aerodrome. This change will be notified through the re-printing of flight progression strips for flights in Active state.The FDD's whose strips have been nulled due to this modification, will be warned about this event by means of an EVENT REPORT message. The following validations shall be performed: The aerodrome must exist. The runways must exist. PSI-4425
Flights edited in Coordinated or Preactive state will be in that state. FPs must belong to such aerodrome. Both departure runways must not affect a FP.
The following operation buttons shall be available: PSI-3041 [Analyse]: An analysis of the modifications made in the selected aerodrome will be performed. In case an error exists, several messages will be displayed, depending on the error is an edition one, or if a flight entered as in Preactive state, was in a different state, etc. In this case a window which confirms the modification correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the modifications analysis, it will process them in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, a confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
The possible error message shall be the following: There is not response from TLPV for the function. This message will be displayed when the TLPV computer does not answer to the Position in the estimated time term. Hereinafter it will be showed: Software Requirements Specification
PSI-3048
159
Try the function again or abandon. Erroneous aerodrome Morphological error Semantic error Syntactic error Erroneous runway Affected non coordinated Preactive Flights Non affected FP FP does not exist Incoherence in affected flights Correct analysis Changed Aerodrome's Parameters
The Manual Aerodrome Parameters Configuration shall generate, through the PSI-4391 service SrvMwER_Generate, the following ER: PSIcpa001 SSTcpa001 (Only Tower)
4.1.8.2.7.
QNH Configuration
A new QNH Configuration window shall be available to change the QNH PSI-4624 value for an Aerodrome belonging to the SACTA region, provided that the current QNH value is out of date. Aerodrome QNH parameters Configuration PSI-5729 This function shall allow to the PSI operator (PSSO profile) to obtain information and to change the referred parameter (QNH) to certain Aerodrome assigned to the centre. The Aerodrome Parameters Configuration will be performed with the base of the existence of adaptation data generated for the choice Aerodrome. The QNH Configuration window shall consist of the following areas: Primary Control Display Area where the OACI code of available aerodrome shall be displayed and the primary embeded presentation areas shall be controlled. Sensitive buttons 'Modify' and 'Close' PSI-4625
The maximum size in the available aerodromes areas shall be adapted to the PSI-4626 size of the rest of the window. A vertical scroll bar for this area will appear if this limit is surpassed .
160
In the case of a PSI which attend to some control resources/responsabilities PSI-4627 from the SILV services, if a QNH Configuration window is requested from the function menu the SILV scenario shall be displayed In the QNH Configuration window shall appear selected by default the first PSI-4628 sensitive box in the control display list.
The window shall be accessible from the SILV processors contextual menu.
PSI-4629
If the window were opened, the displayed information shall be update with PSI-4630 every updating in the QNH information received from SILV. Primary Control Display List The primary control display list shall have the 'Available Aerodromes' and it PSI-4633 will consist of sensitive box containing the aerodrome OACI code for every adapted centre. These sensitive box from the primary control display list shall be PSI-5717 alphabetically arranged from top to down.
The colour for every sensitive box in the primary control display list shall PSI-5718 represent the QNH state associated to that aerodrome and which is the QNH information source associated to that aerodrome
Aerodrome Parameters PSI-5716 If the aerodrome is recognize (it exists in the adaptation data) the parameters which shall appear : - Aerodrome OACI Code, as configured in the adaptation data - QNH Value - QNH value state (effective/obsolete) - Information source (----,METAR/SMI/PSI) The operator could perform modification or consult functions * Note: '----' is the value which represent the users when the QNH information displayed were that by default. Effective State PSI-5714 The current QNH information for an aerodrome shall be in effective state when the Effective End Date has not been passed. NOTE: In the PSI a colour will be defined to identify the effective state Non Effective State PSI-5715 The current QNH information for an aerodrome shall be in effective state when the Effective End Date has been passed. Software Requirements Specification 161
NOTE: In the PSI a colour will be defined to identify the effective state If the QNH State is 'Non Effective' the colour in the sensitive box shall be red. PSI-4637
If the QNH source displayed is 'PSI' the colour in the sensitive box shall be PSI-4638 yellow.
If a coincidence between both situations would happen ( 'No Effective' state PSI-4635 and 'PSI' source) the colour in the sensitive box shall be the red.
The colour by default in the sensitive box ( when it is not displayed one of the PSI-4639 above mentioned colour) shall be such a way to indicate that this area in the window could change the colour to indicate an state. On the control display list it shall be possible to control the presentation, to PSI-4641 modify configurations ( associated to the 'Modify' button) and close the window (associated to the 'Close' button). The sensitive button 'Modify' could be selective or not in function of the PSI-4642 selected items in the primary control display list. The sensitive button 'Modify' shall be selective when, for a selected aerodrome, the QNH state were 'Non Effective' or when the information source of the QNH were the 'PSI'. Limits for modify the QNH from PSI The function of modify the QNH from PSI will be available just in the case of no existence of a effective QNH value in the system, effective date were expired or the effective value were from manual source (PSI) ( supervisor is able to modify a a value introduce by him ). This limit will take place in the PSI, trying to restrict some way the input of "critics" data, as the QNH, in the system if it is not necessary, when correct 'automatic' data are available QNH shall be able to be modified from PSI only if SILV/SMDT is operative. PSI-5720
QNH consult shall be always available
PSI-5719
If the QNH Configuration window is open and selecting a certain aerodrome, PSI-4643 the sensitive button 'Modify' shall change from selective to non selective or vice versa, according to the actualization in the presentation of the window when PSI receive an QNH information actualization from SILV (done by any subsystem involved in it ). Not modified value by receiving a valid QNH by another source PSI-5711 If while the aerodrome QNH value is being modify from PSI, the SILV value is received from SMI or METAR or another PSI, and this is validated by the QNH function (SILV), when the modification request from PSI were received 162 Software Requirements Description
that value shall not be modified advising to the PSI supervisor (PSSO) of change not done because the QNH were not effective. (it means, the presented to the supervisor values were obsolete in the modification moment ) In the TOWER environment, if while the PSI is being modified, it is received in SILV from SILV-t a QNH value to the aerodrome, that value shall not be modified advising to the supervisor to PSI of change not produced due to non effective QNH If while the 'Modify' action is running (QNH value for a determined PSI-4644 Aerodrome) and the SILV server modification is been validated, but the QNH value for that aerodrome were effective, it shall appear an error window indicating to the operator 'Impossible to modify QNH because Effective QNH exist' The QNH Configuration window shall need a password PSI-4646 (general password of the System) to be able of run a modification. So, clicking the sensitive button 'Modify' a second window asking for the password shall be open. A correct introduction of the password in that second window shall cause the PSI-4647 opening of an acknowledge window.
The Information Window associated with the main window of 'QNH PSI-4648 Configuration' shall display the text 'DONE QNH CONFIGURATION CHANGE' Primary view frame The primary view frame in the QNH Configuration window shall consist of the PSI-4645 following unitary components:
non selective text 'Aerodrome' and, next in the same horizontal, an PSI-4650 information view frame with the selected element in the primary control display list ( OACI code for the selected aerodrome) non selective text 'QNH value' and, next, a spin box for selecting the QNH PSI-4651 value or an information view frame according to the selected element in the primary control display list. It shall be an information view frame in case of, for a selected aerodrome in the primary control display list, the QNH value were 'Effective' and the QNH source were 'SMI' or 'METAR', since in that circumstances the QNH value cannot be modify. In the case of the selected aerodrome from the primary control display list the PSI-4652 QNH value shall be 'Obsolete' or the QNH source were 'PSI' or '----' ( source by default), a spin box shall appear because under this circumstances the QNH value can be modified. In the spin box the QNH value included between the minimum and maximum Software Requirements Specification 163
absolute value, can be selected or introduced. Those values are defined in the adaptation data with sault of an unit of millibar. non selective text 'QNH State' and, next in the same horizontal, an PSI-4653 information view frame with the possible texts 'Effective' and 'Obsolete'. The information view frame shall display the QNH state, it means, red colour if QNH state is "Obsolete". The colour by default in this area shall be in such way that, when the above mentioned state is not displayed,the PSI operator will be informed that this area of the window can change the colour to indicate the state. Note: QNH State associated to the case when the information source is 'by default' ('----') will always be obsolete non selective text 'Information source' and, next in the same horizontal, an PSI-4654 information view frame with the possible texts 'METAR', 'SMI','----' and 'PSI'. The information view frame shall display the QNH source through the colour code, it means, the yellow colour will be displayed when the QNH source is 'PSI' or '----' (source by default). The colour of the information view frame, with the non selective text 'Information source', by default will be in a way that, when the mentioned state is not displayed, the PSI operator will be informed that this area of the window can change the colour to indicate the state.
Validations The following validations shall be carried out: The allowed values belong to the absolute range of QNH for every aerodrome (defined by adaptation). Source If the QNH is modified by the supervisor the source shall be the PSI. NOTE: A colour shall be defined in the PSI to identify the source of the QNH.
PSI-5722
PSI-5723
QNH Value PSI-5724 PSI shall validate the QNH value introduced by the supervisor regarding to the Absolute range. In case of surpass that validation the aerodrome QNH value shall be introduced by the supervisor. The calculation of absolute range will be done checking that the introduced value are between a minimum and a maximum defined by adaptation. NOTE: the QNH values will be in millibar and will be integer number, it means, a precision of 1 mb. Distribution of operative SILV modification PSI-5725 When the supervisor from the PSI has introduced the new QNH value for an aerodrome, this shall be sent to a SILV for being processed. The configuration of the manual aerodrome QNH parameter shall generate, PSI-5726 through the service SrvMwER_Generate, the following ER: 164 Software Requirements Description
PSIqnh001
QNH Configuration (only for Tower) QNH shall be able to be modified from PSI in tower environment if SMDT is PSI-4168 operative and the link with the SILV of the corresponding ACC center is not available.
This window shall be displayed on selecting the "QNH Configuration" of the PSI-4169 management function bar, with the left button of the pointer device.
The following operation buttons shall be available: PSI-4172 [Analyse]: An analysis of the configuration change will be performed. If after a time it is impossible to execute the configuration, the following message will be displayed: "There is not response from the computer for the function: TDVT Functions Configuration. The button "OK" will shut the window. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
4.1.8.2.8.
DMAN Configuration
This function shall allow the operator to change parameters related to a PSI-4435 specific Centre Aerodrome.
For every Vigilance treatment, it shall be possible to perform the following PSI-4437 functions, in an indepent way: - Configure departure time ratio The Configuration window of DMAN parameters shall consist of the following PSI-4189 areas: Only display area Action buttons "Modify" and "Exit"
Display area PSI-4249 The display area shall consist of the following elements: - Text of impossible selection ' Ratius departure/time' - Hereinafter, it will exist as adjustable menus as Departure runways which Software Requirements Specification 165
have been configured in that instant for the aerodrome in question (two at the most, according to VIC-R05). Over each adjustable menu a text of impossible selection will exist 'N Departures', being N 1 or 2 and, a display area of the information with the Departure Runway callsign to which the selected value affects in the corresponding adjustable menu. The following operation buttons shall be available: PSI-4250 [Modify]: the button "Modify" shall allow to save the changes showed in the display area, after displaying the confirmation window. [Exit]: It will close the window. The correct execution of the DMAN Configuration function shall generate, PSI-4251 through the service SrvMwER_Generate, the following event report: SSTcfd001
4.1.8.2.9.
AMAN Configuration (F_CAMAN)
The AMAN Configuration function (F_CAMAN) will allow showing and configuring the AMAN A#18429 Runway Separation Rate (TSP) and configuring AMAN rules. Current data corresponding to Runways Separation Rate of each aerodrome PSI-9091 shall be obtained through the service SrvAman_TSPsRequest. Modification of TSP shall SrvAman_TSPModification. be performed through the service PSI-9092 A#18429
A#18429
AMAN Aerodromes shall be SrvAdapgv_AmanAerodromes.
obtained
through
the
service PSI-9093
A#18429
In order to specify the active Runways when starting up the PSI, PSI shall PSI-9094 send to TLPV the message PETICION_DE_PISTAS_ACTIVAS through the event EvtPsi_RequestTlpvActiveRunways.
A#18429
PSI shall be updated by TLPV, with the message PSI-9095 INFORMACION_DE_PISTAS_ACTIVAS, through the event EvtTlpv_ActiveRunwaysInformation every time any of active the runways of an Aerodrome is modified and when TLPV starts up.
A#18429
Rules corresponding to each aerodrome shall be obtained through the service PSI-9096 SrvAman_RulesForOptimumRunwayCalculationModification.
A#18429
166
The AMAN Configuration function (F_CAMAN) shall run in TLPV processors.
PSI-9069
A#18429 A#18429
The AMAN Configuration function (F_CAMAN) shall be disabled (grayed out) PSI-9070 when the processor (TLPV) where the functionality runs is shut down. The AMAN Configuration window shall be accessible from the contextual PSI-4592 menu of the processors where the AMAN functionality runs. The AMAN Configuration window shall be accessible from the function menu PSI-4593 bar.
A#18429
A#18429
When AMAN Configuration window is requested from the function menu bar, PSI-9071 the scenario where the AMAN functionality runs shall be displayed. The title of the AMAN Configuration window shall be configurable by profile, PSI-9072 being by default: "Conf. AMAN".
A#18429
A#18429
The 'AMAN Configuration' window shall comprise: Primary display control list Primary view frame Secondary display area- Runways Separation Rate Secondary display area- AMAN Rules Configuration Sensitive buttons 'Modify' and 'Exit'.
PSI-4590
A#18429
4.1.8.2.9.1. Primary Display Control List The maximum size of the primary display control list (available aerodromes) PSI-4591 shall be adapted to the size of the rest of the window. A vertical scroll bar for this area will be displayed if that limit is exceeded. A#18429
The primary display control list of the AMAN configuration window shall PSI-4598 comprise: Primary display control list comprising sensitive boxes containing the OACI code (AMAN Aerodrome List) for every aerodrome adapted to that functionality and for that centre, with the AMAN functionality configured, alphabetically sorted . Sensitive button 'Exit'. PSI-4597
A#18429
The primary display control list shall display the title: 'Available aerodromes '
A#18429
167
The sensitive button 'Exit' shall cancel the action and close the AMAN PSI-4602 Configuration window. The Information window associated with the 'AMAN Configuration' Changes PSI-5392 shall display the text 'AMAN Configuration Change Performed' When the AMAN Configuration window is requested the first sensitive box PSI-4594 shall be displayed as selected in the primary display control list, by default.
A#18429
A#18429
A#18429
Any change in the AMAN Configuration shall generate an ER reporting the PSI-9073 change performed. Any change in the AMAN Configuration shall generate a message towards PSI-9074 GSI, that will be recorded in the SPV group. That message will include detail information of the change performed.
A#18429
A#18429
4.1.8.2.9.1.1.
Primary view frame A#18429
Primary view frame shall comprise the secondary display control list with the PSI-9075 following options: Runways Separation Rate AMAN Rules Configuration
and the corresponding secondary display area. Secondary display control list shall not have any tittle. PSI-9076 A#18429 A#18429
When selecting a box from the display control area, the box 'Runways PSI-9077 Separation Rate' of the secondary display control list shall appear as selected, by default.
Controlling the display of the secondary display control list shall be available.
PSI-9078
A#18429
Secondary display area - Runways Separation Rate In the centre in the first horizontal the non selective text "Aerodrome:" shall be PSI-4596 displayed and, next, in the same horizontal an information view frame with the OACI code (4 alphabetic characters) selected in the primary control display list.
A#18429
168
In the next horizontal the non selective text 'Arrival runway 1', and next the PSI-4604 information display area containing the runway identifier (3 alphanumeric characters) that is configured as arrival 1.
The next horizontal shall contain the non selective text ''Separation rate of PSI-4605 Arrival Runway 1'and, next, two spin box and between them, with the non selective text ":"
The first spin box shall allow selecting the separation rate in minutes, the non PSI-4606 selective text ':' will indicate that the values of the following spin box are in seconds.
The first spin box shall be range between 0 and 10. PSI-4607 The second spin box will be able to range between 0 and 30 (The value 30 will not be allowed in the second spin box if the first spin box 'minutes' is 10). Note: The runway adaptation rate (time) shall range between 0 and 600 seconds, distributed in the two spin box.
The above described structure shall be repeated for those aerodromes with a PSI-4608 second runway 'Arrival 2' available.
For those aerodromes with two or more arrival runways, due to the runway PSI-4611 separation rate could not be modified for two or more runways simultaneously, it will be acted in the following operative mode: if the spin-box is modified for more than one runway, when clicking the action button 'Modify', an Error Window shall be displayed reporting that 'Runway Separation Rate cannot be modified for more than one runway simultaneously'.
By clicking the acceptation button in the Error Window, the control shall go PSI-4612 back to the 'AMAN Configuration' window, maintaining the TSP values which existed in the window before the menu modification. The CONFIGURATION performed will become effective by clicking the PSI-5391 sensitive button 'Modify' (if the function execution is confirmed in the Confirmation Window). The confirmation of the function execution shall not cause the shutdown of the Conf. AMAN window.
Only the Separation Rate of ACTIVE runways of the aerodrome shall be able PSI-9090 to be modified Software Requirements Specification
A#18429
169
Active Runways Determination Runway Acceptance Rate (time) shall be displayed for each aerodrome and PSI-9080 runway. It will range between 0 and 10 minutes in 30 seconds intervals. Runway acceptance rate will not be able to be modified for tow o more runways simultaneously.
A#18429 A#18429
Secondary display area - AMAN Rules Configuration When selecting the box 'AMAN Rules Configuration' in the secondary display PSI-9082 control list, the secondary display area shall comprise: Thirdly display control area controlling the embeded display area. Sensitive button "Modify".
A#18429 A#18429
Thirdly Display Control Area This area shall comprise a list with the following columns: First column, with the non selective text 'Activation State', will comprise editable areas where it shall be specified if the rule is active (selected area) or not active (not selected area). Second column, with the non selective text 'Priority', will comprise information display areas specifying which is the priority of the rule that is defined in the next columns of the same row. Information display areas will be empty when the activation state of the rule is not active. Information display areas will be filled with priority values ranging from 1 upwards when the rule activation state is active. Column 'Priority' will be updated when 'Activation State' of a rule is modified. Third column, with the non selective text 'Rule', will comprise non selective boxes where the corresponding rule is displayed. Fourth column, with the non selective text 'Rule Type', will comprise information display areas where the rule type, corresponding to the rule defined in the previous column, will be displayed. Fith column, with the non selective text 'Runway', will comprise a menu with the code of the runway assigned (4 characters, in case there is a runway assigned) Maximum Rules number shall be 512. If the number of the rules exceeds the PSI-9085 limit in the thirdly display control area, a vertical scroll bar shall appear in that area. Number of rules will be 10, by default. PSI-9084
A#18429 A#18429
A#18429
Rules types od the edition area associated to the third column (column 'Type') PSI-9086 shall be: 170
A#18429
Fixed Aircraft type STS Flight type Operation type Company Stand
Selecting any of the boxes of the drop-down menu of the 'Runway' assigned PSI-9087 to the rule, the corresponding runway assigned to the rule shall be able to be modified. This will be performed dropping down a list containing the adapted runways (active or not, due to it is possible to modify rules applied to runways that are not active in that moment). A Confirmation Window shall be displayed when clicking the sensitive button PSI-9088 'Modify'.
A#18429
A#18429
The CONFIGURATION performed will become effective by clicking the PSI-9089 sensitive button 'Modify' (if the function execution is confirmed in the Confirmation Window). The change in the Activation/Deactivation of a Rule will cause the Priority recalculation.
A#18429
4.1.8.2.10. MTCD Configuration (F_CMTCD) The Configuration function (F_CMTCD) shall allow to activate/deactivate the PSI-5377 MTCD function.
The 'MTCD Configuration' window shall consist of: A Primary view frame Sensitive buttons 'Modify' and 'Close'
PSI-5378
The MTCD Configuration window shall be accessible from the subsystem PSI-5379 contextual menu where the MTCD functionality runs.
This window shall be displayed selecting it from the function menu. The PSI-5380 scenario where the functionality of MTCD Configuration runs will be displayed if this window is requested to be opened from the function menu. When the MTCD Configuration window is requested the state of the PSI-5381 functionality shall be displayed, it means that the selective mark box will be marked if the functionality is enable or otherwise (it is disable) the selective Software Requirements Specification 171
mark box were not marked. The enable configuration shall be the one by default from the start up, it PSI-5386 means, the selective mark box shall be marked.
In the primary view frame a toggle which shall consist of a non selective text PSI-5387 'MTCD' and a selective mark box shall be displayed.
In the primary view frame the sensitive button 'Modify', which shall make PSI-5383 effective the CONFIGURATION and shall close the window ( if it is confirmed the execution of the function in the Confirmation window) shall be displayed. Clicking the sensitive button 'Modify' an acknowledge window shall be open. The Information Window associated with the 'MTCD Configuration' Window PSI-5384 shall display the 'DONE MTCD CONFIGURATION CHANGE' text.
In the primary view frame the sensitive button 'Close' which cancel the action PSI-5388 and close the window shall be displayed,
4.1.8.2.11. GAC Configuration The state of the link CCTV sent by the SMDT shall be displayed in the link PSI-6517 and system information area in the PST main scenario.
An associated to the configuration of CCTV function (F_CONF_CCTV: PSI-6518 "Television Cameras Configuration") shall be available in PST.
The current TV Camera Configuration shall be displayed after requesting the PSI-6519 CCTV Configuration function, for every existing position.
The TV Camera Configuration window shall be dynamically update after PSI-6520 receiving a modified TD.
The CCTV configuration window shall consist of the following information: 'Title bar': it shall display the title of the menu through which the operational configuration window is accessed. A Primary view frame which consist of rows and columns ( as many rows like existing PICT and five columns) Every row will display: the PICT with its 4 possible cameras. the columns The first row will contain the title of (PICT,VENTANA1,VENTANA2,VENTANA3, VENTANA4)
PSI-6521
The four columns where the cameras of the windows are displayed shall be in the same horizontal than the corresponding PICT, it will be displayed the Name of the TV cameras assigned to the PICT with its assignation type ( Predefined or Manual) represented through one colour. 172 Software Requirements Description
Sensitive button 'Close'
If the size of the window surpass the size of PST view frame a vertical scroll PSI-6527 bar shall be included.
The text of the button shall be white if any window would not have any PSI-6522 assigned camera. The order will follow the TD and the event EvtMwDist_CamerasAssignmentUpdate Camera 1 in Window 1 The possible colours assigned to the kind of assignation shall be: -YELLOW: Manually assigned camera. - BLUE: Predefined camera. From this configuration window the only permitted action shall be "close". PSI-6523
PSI-6524
The "close" button shall allow to close the CCTV configuration window.
PSI-6525
This function shall be accessible from the functions bar menu.
PSI-6526
4.1.8.3. DATA DISTRIBUTION CONFIGURATION Depending on the data type, two strategies can be followed for obtaining and maintaining configuration data: Periodic Distribution Data (Distributed Tables) Data without Periodic Distribution Periodic Distribution Data
4.1.8.3.1.
A series of data will be periodically distributed throughout a family of computers that share the data. It will be performed in a periodical way, each 30 seconds (non configurable), and in a punctual way, each time the information included in the table is modified. When the PSI is started up, these data shall not be requested. It will receive PSI-4287 them within the 30 seconds (non configurable) period, and in a specific way when modifications are achieved.
173
Modif. From AIG CMD CMD
Configuration Function Simulation Session State Configuration
Family Computers All
Radar Inputs Configuration ASTERIX and DDE CMD, UAST, UDDE, CWP FOCUS, Radars SDP QNH (VICTOR) Radar Processing Configuration Normal SDP CMD, ITCP, SDR
CMD
Radar Processing Configuration Enroute Autonomous Radar Processing Configuration TMA Autonomous
CMD, SDP, CWP FOCUS
CMD CMD CMD
SMR Configuration Sectorization Stored Sectorizations SDP Functions Configuration Autonomous TMA
CMD, SDR CMD, LFDP, SDP, Remote SCU Enroute/TMA, Remote FDD, S-PIVL CMD
CMD
SDP Functions Configuration Autonomous Enroute SDP Functions Configuration Normal Enroute
CMD, CWP FOCUS, SDP
CMD CMD CMD CMD CMD CMD CMD
SDP Functions Configuration (STCA, RAW, MSAW, CMD, SDP FLAT, TA) Adjacent Centres Configuration FDP Functions Configuration Access Code AFTN Messages Delivery Configuration Links Configuration AFTN Lines Configuration CMD, LFDP CMD, CFDP CMD CMD, CFDP CMD, CFDP, LFDP CMD, CFDP
Table 4.1.8.3.1-53 : Configuration function
4.1.8.3.2.
Data without Periodic Distribution
In this case, the data distribution will be performed by request. The PSI shall allow the operator to request information through the execution PSI-4288 of the configuration function. Data examples of this type could be: GSI User Configuration, GIPV User Configuration or Special Areas data. This information shall be requested to the server which is "owner" of these PSI-4289 data. This information won't be available if the computer is not available. The operator will make changes by dialoguing with the subsystem about the received information. Confirmation ACKs shall be expected. Similarly, the data present in the computers will be able to arrive from three different sources: 174 Software Requirements Description
Data stored in disc that can be recovered when starting up is achieved with data in disc. Periodic distribution data Data obtained when another computer is started up. Data FPs file FPs File in System Shutdown RPLs File (current and new) FDO, SUP, ABI Queues Last CRAM received message and Channel Last CRAM delivered message and Channel Last RPL awoken FP Events AFTN Event Report Functions Configuration TPV AFTN Stored in disc X X X X X X X X X X X X X X X X X X X X X X X X X X X TCPV X X X X X 175 TCPV (1 Periodic Distribution Requests loading to
Proc. TCPV
TLPV
Parameters Aerodromes Runways and QNH Parameters Aerodromes QNH FPs SSR Codes FP Events Tabulars Queues of Flight Plan Strips to Print Sectorization Adjacent Centres Configuration
SILV
Special Areas QNH ATIS Event
GIPV
External Systems Configuration FP Filters FP Formats Delivery Configuration External Systems Enabling TCPV FPs Fees Information Existing Messages Actions on FPs
GSI
Users and Recording Groups Configuration Tape in Use
Proc.
Data Recording State FTP and NFS Access
Stored in disc X X X X X
Periodic Distribution
Requests loading to
SIS TDVM
ES and DS DISPI Configuration Special Areas Entry/Leave Holding and Handovers in process States Automatic QNHs FPs Fictitious FPs Normal TDVM Radar Proc. Conf. Normal TDVM Functions Configuration Flight Manual Data Sectorization
MTLP (1)
TLPV TLPV X X X X X TLPV X X X X X X
PIVL
FPs Sets Filters Formats Queries Sectorization
PIVC UCS Normal TDVM Radar Proc. Conf. (3) Radar Input Conf. ASTERIX and DDE Radars (4) PSSO Normal TDVM Functions Conf. (5) (STCA, RAW, MSAW) Sectorization Automatic QNHs STCA/RAW/MSAW Inhibition State at UCS and at Individual Levels Adjacent Centres Configuration CWP (Focucs) Normal TDVM Radar Proc. Conf. (6) Enroute/TMA Autonomous TDVM Radar Proc. Conf. Radar Input Conf. Asterix and DDE Radars PSSE Enroute/TMA Autonomous TDVM Functions Conf. (Prim, Met, Dynamic Adjustment)
X X X X
X X X X X
176
Proc.
Data PSSO Normal (STCA, RAW, MSAW) and PSSO Enroute/TMA Autonomous TDVM Functions Conf. Autonomous TDVM MSAW Inhibition State Sectorization Adjacent Centres Configuration Automatic QNHs Autonomous TDVM Manual QNHs 24h Reproduction / PRAD-GRAF Files
Stored in disc
Periodic Distribution X
Requests loading to
X X MTLP
X X X X X X X X X X
UDDE UAST CMD
RIC Asterix and DDE radars RIC ASTERIX and DDE radars Normal TDVM RPC, Enroute/TMA Autonomous RIC ASTERIX and DDE Radars TPV AFTN Functions Conf. TDVM-Normal, Enroute/TMA Auto. Functions Conf. Sectorization TDVM Functions Conf. (STCA, RAW, MSAW, TA, FLAT) Adjacent Centres Configuration
(1)To the operative one and only when performing startup without data in disc.
Table 4.1.8.3.2-54 : Previous classification summary
4.1.8.4. MAINTENANCE CONFIGURATION The following configuration functions could be performed: 4.1.8.4.1. GSI Configuration
It shall allow to configure the users as the information to be saved, to enable PSI-440 the recording and to recover the information which has been recorded previously. It shall allow to recover from tapes the files belonging to old users in order to PSI-3697 make them available in the GSI Subsystem for all purposes.
We shall configure the following functions through this menu : Users Configuration
PSI-3049
177
Information to be Recorded Configuration Recording Enabling-Disabling
4.1.8.4.1.1. Users Configuration Each User shall be defined by the following elements indicated below: User (name) Group Processor PSI-3053 PSI-3050
The following actions shall make possible operating with this screen: In the "Edit" menu the action to be performed will be selected with the LB of the pointer device. The "Add" function, from the aforementioned menu, will allow to define a new user. The "Modify" function, from the aforementioned menu, will allow to modify an existing user. The "Delete" function, from the aforementioned menu, will allow to delete an existing new user. From the "List" menu could be dropped-down the information about the available "Groups" and "Processors", on selecting them with the pointer device. Both lists could be showed simultaneously. To select the user where the action is to be performed or to enter the data into the corresponding edition fields ("User", "Group" and "Processor") or through the selection in the displayed sub-windows. To select the associated communications protocol "None" or "FTP").
The following operation buttons shall be available: PSI-3056 [Analyse]: An analysis of the configuration change will be performed. In this case, a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
The possible error messages shall be the following: There is not response of the Computer for the function "Users Configuration Change Request ".This message will be showed when the 178
PSI-3057
computer does not response to the Position in the estimated time term. Afterwards, it will show: Try the function again or abandon. Are you sure of doing this change. Edition error: Invalid user name Edition error: User already exists Error: User to be modified has not been selected Edition error: Unknown User Edition error: Unknown Group Edition error: Unknown Host Error: Maximum number of user has been exceeded User Modification: Correct User creation: Correct User deletion: Correct
4.1.8.4.1.2. Configuration of Information to be Recorded In this window the information to be recorded for a GROUP will be configured or rejected. These GROUPS will be associated with the users, or they will be accessible to them. Different information groups shall be created and different users could be PSI-3061 associated with each group. In order to make easier the description of the desired information, below are shown these writings, which will serve as an example of description .
The desired functionalities and writings shall be similar to the ones enunciated PSI-3062 by the above figures. The following possibilities will be available (see example of Information to be Recorded Configuration window): Names of recording groups and associated comments will be showed. Adding, modifying and deleting groups will be allowed. Acquisition of data via FTP or Messages could be configured.
The following actions shall be allowed in order to operate with this window PSI-3070 (see example of Configuration of Information to be Recorded window) : In the "Edit" menu the action to be performed will be selected with the LB of the pointer device. The "Add" function, from the aforementioned menu, will allow to define a new recording group. The "Modify" function, from the aforementioned menu, will allow to modify an existing recording group. The "Delete" function, from the aforementioned menu, will allow to delete an existing recording group. From the "List" menu the displayed information could be modified, being possible to select between "Groups" and "Comment" (it will show the available groups and comments associated with them) or "Groups" and "Users" (it will show the groups and their associated users) on selecting them Software Requirements Specification 179
with the pointer device. It will allow to select the group where we desire to perform the action or to enter the data into the corresponding edition field. It will allow to modify or enter the Comment into the edition field "Group Comment" by means of the keyboard. If the action to be performed affects to an existing group, the display of the "Messages Configuration" and "FTP files Configuration" sub-windows will be the one configured for the aforementioned group. In case we want to modify this configuration, or we were creating a new group, we would have to select the corresponding buttons in order to display these sub-windows. The mode of use of each sub-window is depicted hereinafter.
4.1.8.4.1.2.1.
Messages Configuration / Files Configuration through ftp
This section is the continuation of the above one. The showed writings will serve as documentation for this section. This part is referred to the messages configuration for the recording and to the FTP Files configuration for sending and reception of files to the GSI, by authorized users. The desired functionalities and writings shall be similar to the ones enunciated PSI-3096 by the above figure, called "Example of Configuration of Information to be Recorded window with drop-down menus". The following possibilities will be available: Messages Configuration to be recorded: Add, Modify, Delete. Configured messages and their characteristics will be showed: Source, Type, Continuous Sampling/bursts per time or number of messages. Information concerning to the files will be showed: User File Sizes where the information is recorded, validity period of the file before having been deleted, type of recording. FTP Files Configuration: Identification, size, validity period of the FTP file, Recording Devices, type of recording. The following operation buttons shall be available: [Analyse]: It will perform an analysis of the configuration change. In this case a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to reconfigure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window. Messages Configuration Operative for the recording: The button "Add", shall allow to select the action to be executed among PSI-3099 the following: "Add", "Modify" and "Delete" on selecting with the LB of the pointer device. These options will act upon the window messages "Configured Messages". 180 Software Requirements Description PSI-3063
The option "Delete" shall be selected in order to delete a message. This PSI-3100 message could be selected in this window, and afterwards the button "Accept" of the aforementioned sub-window could be clicked. We shall "Add" or "Modify" a message using the displayed windows by PSI-3101 clicking the following buttons: [Type]: It will be the number Identifier of SACTA message. A window with the list of type of messages will be displayed. [Source]: It will be the alphanumeric Identifier of SACTA element. A window with the list of sources will be displayed. If "Source" is not specified, all of the sources belonging to the selected message will be taken into account.
The recording of messages with the same type and source could be PSI-3102 rejected. The following options shall be available from the "Continuous" menu: [Continuous]: In order to record all the messages of the defined type. [Per(sec)]: In order to record the message each certain number of seconds. [Per(mssg)]: In order to record the message each certain number of generated messages. In order to update these changes the button "Accept" of this subwindow must be clicked. The user files size where this information shall be recorded could be fixed PSI-3103 providing the following parameters: Byt: It will represent the maximum size in bytes in order to close the file. Mssg: It will represent the maximum number of messages in order to close the file. Tmp:It will represent the maximum recording time period in order to close the file (in days, time and minutes). These conditions will be affected by the OR operator. The validity period of the user file shall be edited. It is the time the file PSI-3104 keeps stored in disc available for the users before having been deleted.
A button shall be available in order to enable "Continuous Recording". PSI-3105 This button will drop-down the menu: ON/OFF. Once selected ON, the disabling of the recording of this group won't be allowed from the "Recording Enable/Disable" window. In this way, it will be indicated that this group records the selected information permanently for it, come from recording by number of messages, message generation frequency, or any other.
181
The Recording Device shall be selected (Rec Dev).
PSI-3106
NOTE: "Continuous Recording" button and the"Continuous" button must be distinguished. "Continuous Recording" will be applied to all the information which has been configured for the selected group, while "Continuous" is applied to one or several messages which have been selected by the computer. Files Configuration Operative through ftp: This section shall be applied to the FTP Files Configuration for the PSI-3109 sending and reception of the files to the GSI, by authorized users. In order to operate with this window the following actions will be allowed: Once selected the FTP Files Configuration, FTP files filters shall be PSI-3111 edited. Entering the "Identifier" which will form a characters string, so that the name of the file to transfer or to receive to/from the GSI must correspond to the "n" characters which have been edited in this field. Any other file won't be accepted neither for being transferred to the GSI nor for being recovered by the user. Entering the "Bytes Size" which will represent the maximum size of the permissible file in order to transfer, in bytes. Editing the " Validity period of FTP file" (in number of days) which will be the time the file will be kept stored in disc available for the user before having been deleted. Selecting the options "Rec Dev" (Recording Device) and "Cont Rec" (Continuous Recording) which will be managed in the same way that for the "Messages Configuration". The following operation buttons shall be available: [Analyse]: It will perform an analysis of the configuration change. In case the changes are not admissible, the corresponding error message will be displayed. If changes are admissible, a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window. PSI-3113 PSI-3112
The possible error messages shall be the following: There is not response from the Computer for the function "Data Request of Recording Configuration". This message will be showed when the computer does not response to the Position in an estimated time term. Afterwards, it will show: Try the function again or abandon. 182
Are you sure of doing this change. Edition error: Name of the invalid group Edition error: Group already exists Error:Group to be modified has not been selected Error: Any modification has been performed Edition error: Unknown group Error: Maximum number of groups has been exceeded Error: At least a Message must be configured
Error: At least one of the concepts Byt, Mssg or Tmp must be defined in the area: User File Size.
4.1.8.4.1.3. Enable-Disable Recording It will allow to enable/disable recording groups. On selecting this function a menu shall be dropped-down and it will show the PSI-3115 following elements: List of groups and Recording activation states. Modification options.
In the "List of Groups and Recording activation states" shall be allowed to PSI-3121 select the group to be enabled/disabled and to modify the following menus: For the Label Mssg. Rec(Message Recording) the menu: ON/OFF will be dropped-down. Select ON in order to enable the message recording. Select OFF in order to disable the message recording. For the "FTP Rec", the menu: ON/OFF will be dropped-down. Select ON in order to enable the FTP recording. Select OFF in order to disable the FTP recording.
Only the groups which haven't been defined as continuous recording shall be PSI-3116 allowed to be modified . They will be able to be modified by changing the recording conditions of this group in the "Information to be recorded Configuration" window. The following operation buttons shall be available: PSI-3117 [Analyse]: It will perform an analysis of the configuration change. In case the changes are not admissible, the corresponding error message will be displayed. If changes are admissible, a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will Software Requirements Specification 183
be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
The possible error messages shall be the following: There is not response from the Computer for the function "Activation Change Request of the Recording". This message will be showed when the computer does not response to the Position in an estimated time term. Afterwards, it will show: Try the function again or abandon. Are you sure of doing this change.
PSI-3118
4.1.8.4.2.
GIPV Configuration
It will allow to configure the information in mode and way of sending to the external systems which have been connected to the SACTA. The GIPV subsystem will send information from FPs, asked for external systems through formatted messages, by applying filters which serve as templates in order to select the information from its data base, which keeps updated through the TCPV permanently. The information sending configuration will be performed through the following sub-functions: 4.1.8.4.2.1. FPs filters support A function which shall allow to fix the FPs filters which will be included in the PSI-3123 sendings to external users of the GIPV will be available.
Up to 50 filters of Flight Plans shall be defined.
PSI-3144
On enabling this function, a window shall be displayed with the following PSI-3143 options: Existing filters: names and comments. Filters editor
The following Filter fields: Callsign, Origin, Destination, Routes, Sectors, New State, Old State. In order to operate with this window the following actions will be allowed: The following operations shall be allowed: "Add Filter", "Modify Filter" or PSI-3145 "Delete Filter"
The desired filter to be executed shall be allowed to be selected from the PSI-3149 "Existing Filters" zone.
184
In case a filter is being entered, a new name for the new filter shall be entered PSI-3150 (up to 20 alphanumeric characters).
For each filter, a comment composed of up to a maximum of 40 alphanumeric PSI-3151 characters shall be allowed to be added.
An area of "Filter Fields" shall exist, and for each field an activation indicator PSI-3152 shall be displayed together with the field name, which will indicate if this field has got content. The clicking of this indicator will cause the deletion of it when the field is active. Clicking on the corresponding field name the modification window of this field will be accessed. The fields modification window shall show the following options: PSI-3153
For the "Callsign"/"Origin"/"Destination" fields. All these fields shall be PSI-3148 selected. On selecting it the "Callsign/Origin/Destination Edition" window will be displayed. In this window: Up to 20 character strings shall be included, which shall contain the aforementioned fields in order to be included in the filter. A string shall be deleted. In order to delete it we must select it and clicking on the "Delete" button. In order to add a string we must enter it through the keyboard in the edition area and clicking on the "Add" button. The different strings will be linked by means the OR operator. Buttons Execute and Exit will be available.
For the "Route" field: This field could be selected. On selecting it the PSI-3155 window "Routes Selection" shall be displayed. In this window: This window will show the Existing Routes and the selected Routes. It will allow to include or exclude "Existing Routes" among the "Selected Routes". Up to 20 "Selected Routes" which will be affected by the OR operator could be defined. In order to modify the list of "Existing Routes" we could click on the "Edit Routes" button and the "Routes Edition" window will be displayed. Buttons Execute and Exit will be available.
In "Routes Edition" window: In this window ("Routes Edition") the support actions of the Routes information ("Add", "Modify" or "Delete") shall be selected. The route where the action will be performed shall be selected or we shall enter the name of the new route up to a maximum of 10 alphanumeric characters. The route will be defined by a maximum of 10 points. The points associated with each route will be considered as affected by the AND operator. Software Requirements Specification
PSI-3156
185
The overflights order must correspond to the definition order, although the points would be able not to be consecutive. For each point, the Upper and Lower Levels shall be defined in an optional way, in hundred of feet. The lack of any level will be understood as a restriction absence. In order to delete a point we will have to select it and clicking on the "Delete" button. In order to add a point it will be able to be entered through the keyboard in the edition area and clicking on the "Add" button. Buttons Execute and Exit will be available.
For the "Sectors" field. This field could be selected. On selecting it the PSI-3157 window "Sectors Selection" shall be displayed. In this window: This window will show the Existing Sectors and the Selected Sectors. It will allow to include or to exclude "Existing Sectors" among the "Selected Sectors" Up to 20 "Selected Sectors" which will be affected by the OR operator could be defined. In order to modify the list of "Existing Sectors" the button "Edit Sect" could be clicked and the window "Sectors Edition" will be displayed. Buttons Execute and Exit will be available.
In the window "Sectors Edition": In this window ("Sectors Edition") the support actions of the Sectors information ("Add", "Modify" or "Delete") shall be selected. The Sector where the action will be performed shall be selected or we shall enter the name of the new sector up to a maximum of 10 alphanumeric characters. Up to a maximum of 50 sectors shall be defined. Actually, these Sectors will be a set of up to 20 centre sectors.
PSI-3158
For each centre sector, the Upper and Lower Levels shall be defined in an optional way, in hundred of feet. The lack of any level will be understood as a restriction absence. In order to delete a centre sector we will have to select it and clicking on the "Delete" button. In order to add a point it will be able to be entered through the keyboard in the edition area and clicking on the "Add" button. Buttons Execute and Exit will be available.
For the "New State"/"Old State". All these fields could be selected. On PSI-3160 selecting it the New State/Old State shall be displayed. In this window we could select the following states: PENDING, ACTIVE, COORDINATED, TDVM HOLDING, PREACTIVE and TERMINATED. The operation button "Finish" will be able in order to indicate the action has been finished. 186 Software Requirements Description
The following operation buttons shall be available in the Keep filters of FPs. PSI-3161 [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
The following operation buttons shall be available in the Keep filters of FPs. PSI-3162 [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Print]: It will send the filter to the line printer. [Exit]: It will close the window.
4.1.8.4.2.2. Keep FPs formats It shall allow to define how will be the FP format which is sent to the external PSI-3140 users.
Up to 100 different sending formats shall be defined
PSI-3163
A delivery format shall consist of a subset or the entirety of the following fields PSI-4426 and subfields that shall be independently selected: CALLSIGN DEPARTURE 'DESTINATION' 'A ALTER' FIRT 'ETOT' 'ELDT' 'HTOT' 187
PREACTIVATION TIME SLC TIME' 'IOBT' 'EOBT' 'CTOT' 'HOBT' 'MOBT' 'AOBT' 'MTOT' 'MLDT' 'ALDT' 'REGULATION_CODE 'AIRCRAFTS NUMBER' 'AIRCRAFTS TYPE' 'AIRCRAFT GROUP' 'FLIGHT TYPE' 'FLIGHT RULES' 'NCA EQUIPMENT' 'SSR EQUIPMENT' 'IVWC' 'EVWC' 'SPEED' 'RFL' 'PFL ORIGIN' 'CFL ORIGIN' 'EFL ORIGIN' 'ORIGINAL ROUTE' 'SACTA ROUTE' 'ROUTE'
Segments. Segments shall be selected by a maximum of 3 identifiers. An identifier shall be either a number indicating the numerical order of the segment or a letter with the following meaning: T: all, U: last, P: penultimate, A: antepenultimate . For each segment: Segment state First sector Last sector First fix point Last fix point Assigned SSR code Previous SSR code Centre
Route Fix Points. Fix Points shall be selected by a maximum of 10 identifiers. An identifier shall be either a number indicating the numerical order of the fix point or a letter with the following meaning: T: all, U: last, P: penultimate, A: antepenultimate . 188 Software Requirements Description
For each fix point: Fix Point name X-Y coordinates Speed CAGE-CAMO identifier EFL PFL CFL Segment identifier Fix Point class VFR-IFR ETO ETO type
Sectors. Sectors shall be selected by a maximum of 10 identifiers. An identifier shall be either a number indicating the numerical order of the sector or a letter with the following meaning: T: all, U: last, P: penultimate, A: antepenultimate . For each sector: Sector name Entry level Exit level Entry time
'QUEBEC' 'SELCAL' 'RMK' 'OBSERVATIONS' 'IFP' 'IND MANUAL COORDINATED' 'IND ACT TDR' 'IND ABI RECEIVED' 'SID' 'STAR' 'TRANSITION FIX POINT' 'TRANSITION LEVEL' 'LEV2' 'REGISTER' 'SRC' 'OLD DEPARTURE 'ATOT' 'UOBT' 'IND CONFIRMED FP 'DEPARTURE RUNWAY 'ARRIVAL RUNWAY 'OLD DESTINATION' 'FP VERSION NUMBER' 189
'RVSM STATE' 'NUMBER OF SENT SEGMENTS' 'NUMBER OF SENT ROUTE FIX POINTS' 'NUMBER OF SENT OVERFLOWN SECTORS' CURRENT ASSIGNED SSR CODE CURRENT PREVIOUS SSR CODE CURRENT ASSIGNED SSR CODE OF PREVIOUS FP PSI-4427
The selection command shall determine the delivery order of the information.
On enabling this function a window shall be displayed and the following PSI-3164 information shall be showed: Existing formats: Name and Comments Formats editor: Format name and Comment name Time formats: DDMMYYYYTTMM or DDMMYYTTMM or HHMM.
Format fields: We will show them in an example of the desired window, in the following section. Format fields order: Name, ER and Indicator.
In order to operate with this window the following actions will be allowed: Selecting the operation we want to perform: "Add Format", "Modify PSI-3170 Format" or "Delete Format". Selecting the format where the operation shall be performed in the PSI-3173 "Existing formats" area. In case we were adding, a name should be entered for the new format (up to a maximum of 20 alphanumeric characters). For each format, it will be allowed to add a comment up to a maximum of 40 alphanumeric characters. Selecting a type DDMMYYTTMM or HHMM. or PSI-3172
of
"Time
format":
DDMMYYYTTMM
Each format would consist of a fields series. For each field an PSI-3174 activation indicator shall be displayed, which will indicate if the aforementioned field had been selected for the format. The Possible actions to be performed on these fields will be the following: Selecting any part of the field for a field which is active, being different PSI-3169 from "Route", "Sectors" or "Segments" or being in the activation indicator of these last fields. The content of the aforementioned field would be deleted and the "Format fields order" zone would be eliminated. Selecting one of the buttons disposed for every field previously shall be PSI-3176 defined in the delivery format, when they are not active the "Indicator of FieldER Printing" window will be displayed. 190 Software Requirements Description
PSI-3177 This window shall contain the text "Indicator of Field", which shall have an editable area which will allow to indicate when the selected field begins in the format. Besides this window will dispose of the event report Printing option. This window will consist of the "Execute" and "Exit" buttons.
On selecting the "Route", "Sectors" or "Segments" fields. On selecting PSI-3175 each one the window shall display "Route Indicator", "Sectors Indicator" or "Segments Indicator", respectively. These windows shall consist of the information: Sub-fields, Selected, PSI-3178 Indicators and Header These windows shall allow to include or to exclude "Sub-fields" PSI-3182 among the "Selected" ones through the sub-field selection from the following: name, position, speed, indicator GAT-OAT,ETO_Type ETO_Point, PFL, CFL, EFL, Section Indicator, Point Class, VFR/IFR. The multiple selection and the non selection shall be possible in the PSI-3181 windows "Sub-fields" and "Selected". It shall be allowed to include or exclude all the sub-fields, PSI-3183 respectively. For the selected sub-fields the headline could be modified individually by PSI-3185 selecting the aforementioned sub-field and clicking on the button "Header". Once entered the "Header" information, it shall be displayed in the PSI-3184 "Selected" area following the affected sub-field. In order to fix what route stretchs, what sectors or what segments PSI-3186 take part in the sending, it shall be allowed to enter up to 3 indicators which could be a number between 1 and 25 (which will indicate the numerical order) or a letter with the following meaning: (A: all, U: ultimate, P: penultimate, A:antepenultimate). The following operation buttons shall be available in the Keep filters of FPs. PSI-3166 [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. Software Requirements Specification 191
The button "OK" of this window will close the window. [Print]: It will send the filter to the line printer. [Exit]: It will close the window.
4.1.8.4.2.3.
Delivery Configuration be delivered to the External PSI-4429
Configurable Flight Plan information shall Systems with this function.
The window which enable this function shall dispose of the following PSI-3141 information: Existing Configuration. Name, Comment Configuration Editor: Add, Modify, Delete Configuration. Name of configuration, Comment of configuration The Configurations Edition will have associated: Events, Messages, Filters. Also it will be associated with a Time Threshold.
Up to a maximum of 50 sending configurations shall be defined.
PSI-3190
Each delivery configuration shall be identified with a maximum of 20 PSI-4428 alphanumerical characters. It shall be possible to associate to each configuration a comment text with up to 40 alphanumerical characters.
The configuration to be used shall be selected from the sending PSI-3187 configurations for each of the External Systems.
A configuration shall be composed, at least, of: The event which must be produced for the sending. The kind of message (FPs Format + code) and in an optional way. Filter to be applied for the sending.
PSI-3188
Each configuration shall have a maximum of 20 events, each of which shall PSI-4430 compulsory include a delivery message associated to it and, optionally, an FP filter. Failure to select an FP filter shall be interpreted as if all FPs are of interest.
The selectable events shall be the following: 192 Cross any fix point or certain fix points: The fix points shall be selected by their order number or by a
PSI-4431
positional reference for the last three ones U: last, P: penultimate, A: antepenultimate . It shall be possible to select up to three fix points. Entry into any sector or entry into certain sectors: The sectors shall be selected by their order number or by a positional reference for the last three ones U: last, P: penultimate, A: antepenultimate . It shall be possible to select up to 3 sectors. Any modification or specific modification of one of the following fields: CALLSIGN DEPARTURE DESTINATION FIRT 'EOBT' 'ELDT' 'CTOT' 'ETOT' ORIGIN ECL AIRCRAFT TYPE NUMBER SPEED ALTER A ORIGIN ROUTE RECEIVED ABI ROUTE ASSIGNED CSSR 'PREVIOUS CSSR 'STATE' 'FIRST POINT' 'LAST POINT' ETO ETO TYPE' ECL CROSS LEVEL DEPARTURE RUNWAY ARRIVAL RUNWAY SID' STAR 'FLIGHT TYPE' 'FLIGHT RULES' 'WAKE' 'IND ABI RECEIVED' CURRENT ASSIGNED SSR CODE CURRENT PREVIOUS SSR CODE
In order to operate with this window the following actions will be allowed:
193
Selecting the operation we want to perform: "Add Configuration", PSI-3189 "Modify Configuration" or "Delete Configuration". Selecting the configuration where it is desired to perform the operation of the "Existing Configurations" window. In case we were adding a new name should be entered for the new filter (up to a maximum of 20 alphanumeric characters). For each configuration it will be allowed to add a comment composed of up to a maximum of 40 alphanumeric characters. In order to add or modify some sending condition in the selected Sending the buttons "Add" or "Modify" will be clicked and the window "Sending Configuration Edition" will be displayed. The Sending Configuration Edition window shall dispose of the PSI-3192 information: Events, Messages, Filters. In order to operate with this window the following actions will be allowed: Each "Event" shall be able to be associated with a sending format PSI-3250 ("Message") compulsorily, and with a "FPs Filter" optionally. The non selection of the "FPs Filter" will be understood as if all the FPs are of interest. The events available for selection are the following: (they are listed by tab level): "Crossing fix" / "Crossing sector". Both events shall display the PSI-3253 "Configured Event" window. This window will allow to select up to three fixes/sectors. The "Configured Event" window shall display fixes/sectors and will allow PSI-3256 the following operations: To select up to three fixes/sectors. In order to delete a fix/sector it will have to be selected and click the "Delete" button. In order to add a fix/sector its indicator will be entered through the keyboard in an edition area and the "Add" button will be clicked. "Creation", "Coordination", "Preactivation", "Activation" or PSI-3254 "Termination" shall display the "Segments (Creation/Coordination/Preactivation/Activation/Termination)" window which will allow to identify complete CENTRES or SEGMENTS which will cause the sending. The "Segments PSI-3257 (Creation/Coordination/Preactivation/Activation/Termination)" window shall display as the existing as the selected centres and segments and it will allow the following operations: In order to select a CENTRE we must: mark the "CENTRES" indicator select the desired CENTRE from the available ones in the "Centres" area and 194 click the button of switch to the selected ones. Software Requirements Description
In order to non-select a CENTRE we must: select the centre in the "Selected" zone click the button "remove from selected". mark the "SEGMENTS" indicator,
In order to select a SEGMENT we must: enter up to a maximum of 3 indicators through the keyboard in the edition field, by its order number or by a positional reference for the las three ones (U: ultimate, P: penultimate, A: antepenultimate) Click on the "Add" button. select it in the "Segments" area and click on "Delete" button.
In order to delete a segment from the selected ones, we must:
"Modification" shall display the "Determining Fields of Sending by PSI-3255 Modification" window which will allow to select among the different fields. The "Determining Fields of Sending by Modification" window shall display PSI-3259 the modifying fields. The change between existence and non existence of the field will be considered as a field modification. Each format will consist of a fields series. For each field an activation indicator will be displayed and it will indicate if the aforementioned field is selected for causing the sending in case it has been modified. The possible actions performed in the fields will be the following. Any part of the field could be selected for an active field different from PSI-3193 "Assigned CSSR","Previous CSSR","State", "First Point", "Last Point", "Intention Code", "Route Point Name", "ETO", "ETO Type", "ECL", "RFL" or "Cross Level" or in the activation indicator of these last mentioned when they are enabled. On selecting it, the sending shall be disabled due to the modification of the aforementioned fields, and the content of this field will be deleted for these last ones. When they are not enabled, the following fields could be selected: "Callsign", "Origin", "Destination", HFIR, EOBT, ETA, ADT, PFL, "aircrafts Number/Type","Cruising speed", "Cruising Level", "Alternative Aerodrome", "Original Route", "Route", "Received ABI", Departure Runway" or "Arrival Runway" or the activation indicator of the "CSSR", "ETO" or "Step Level" fields when they are not enabled. On selecting it, the sending due to modification of the selected field will be enabled. The "Assigned CSSR","Previous CSSR","State", "First Point", "Last Point", "Intention Code" fields could be selected. On selecting it, the "Segment (Modification)" window already described in the current section. "ETO", "ETO Type", "ECL", "RFL" or "Cross Level" fields could be selected. On selecting it, the "Configured Element" window, already depicted above, will be displayed. It shall be possible to define a time threshold in minutes (max. 30 min.) that PSI-3260 will affect only fields related to FP times. Modifying a FP time field will raise the event, if the time difference between the current value and the value of the field when the last message was delivered exceeds the threshold: Creation in selected segments. 195
Coordination in selected segments. Preactivation in selected segments. Activation in selected segments. Termination in selected segments. Cancellation.
The following operation buttons shall be available in the Sending PSI-3195 Configuration window: [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Print]: It will send the filter to the line printer. [Exit]: It will close the window.
4.1.8.4.2.4.
Messages Selection
This window will allow to configure a sending message as from a format. The message shall consist of an initial code+format+final code. PSI-3261
The window which enables this function shall have available the following PSI-3263 information: Existing Messages: Name, Comments Messages Editor: Add, Modify, Delete Message. Message Name, Message Comment. Available Formats: Message code, End of Message code.
In order to operate with this window the following actions will be allowed: The desired option to be performed shall be selected: Add Message, PSI-3266 Modify Message or Delete Message. The message where the operation is desired to be performed shall be PSI-3270 selected from the "Existing Messages" window. If we are adding, a name will have to be entered for the new message (up to a maximum of 20 alphanumeric characters). For each filter, a comment composed of up to a maximum of 40 alphanumeric characters, is allowed to be added.
196
A format from the "Formats" window shall be selected.
PSI-3269
A message code shall be edited in the associated edition field. The message PSI-3268 code shall be defined with up to a maximum of 5 alphanumeric characters.
A final code could be edited in the associated edition field. The final PSI-3267 code shall be defined with a maximum of 4 alphanumeric characters. The following operation buttons shall be available in the Messages Selection PSI-3265 window: [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Print]: It will send the filter to the line printer. [Exit]: It will close the window.
4.1.8.4.2.5.
External Systems Configuration
This window will allow to discharge the External Systems in the GIPV. For every external system the following concepts shall be compulsory PSI-4432 defined: - Name ( 10 characters without white space) - IP Direction from the External System ( only if protocol is TCP/IP) - Associated Port to the External System (only if protocol is TCP/IP) - Configuration of Delivery The window which enables this function shall have available the following PSI-3273 information: Existing External Systems: Name External Systems Editor: Add, Modify, Delete External System. External System name, IP Address, port. Existing Configurations: Configuration Name.
In order to operate with this window the following actions will be available: The option we want to perform shall be selected: Add External System, PSI-3196 Modify External System or Delete External System.
External System where the operation is being performed could be PSI-3276 selected from the "Existing External Systems" window. In case we were Software Requirements Specification 197
adding, we shall have to enter a name for the new external system (up to a maximum of 20 alphanumeric characters) In order to enter a configuration, a configuration shall be selected from PSI-3275 the "Existing Configurations" window, an IP address and a port will be entered in the associated edition fields. It shall be verified that the associated IP address has a correct format and PSI-4433 that the associated ports are within a certain range (2001-3000).
The following operation buttons shall be available in the Messages Selection PSI-3272 window: [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Print]: It will send the filter to the line printer. [Exit]: It will close the window.
Implementing a configuration for an ES shall require the latter to be inhibited.
PSI-4434
4.1.8.4.3.
Enabling of ESs
This window shall allow to enable the information sending for an existing PSI-3277 ES already configured.
In case the ES is not configured, anything shall be sent.
PSI-3280
The window which enables this function shall have available the following PSI-3278 information: External Systems: Name State: Enabled/Disabled
In order to operate with this window the following actions will be allowed: It shall be able to allow to enable the information sending for an PSI-3197 existing ES already configured.
198
The selection could be modified.The drop-down menu associated PSI-3282 with each external system which shall have available the Enabled and Disabled states, will be used for this purpose. The following operation buttons shall be available in the Enable ESs window: PSI-3281 [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
4.1.8.4.4.
External Systems Configuration
This window will allow to enable and disable the external users of the SIS. The configured External Systems shall be defined through the adaptation PSI-3284 data, and in that window the following modifications could be performed:
The window which enables this function shall have available the following PSI-3285 information: External System: Name State: Enabled (Non Connected/Connected), Disabled. Minimum period of Information request: Value Maximum geographical Area
In order to operate with this window the following actions will be allowed: An External System shall be Enabled/Disabled. The steps to be PSI-3287 followed will be the indicated below: Selecting an external system Selecting from an associated drop-down menu the option "Enabled", in case it is Disabled or "Disabled" in case it is "Enabled". Minimum period of information request shall be modified. Steps to be PSI-3290 followed: Selecting an external system. An edition field associated with the period will exist. It will show the minimum period of current information request, in seconds. This field could be changed without restrictions.
199
An External System shall be Enabled/Disabled. The steps to be PSI-3291 followed will be the indicated below: Selecting an external system Selecting from an associated drop-down menu the option "Enabled", in case it is Disabled or "Disabled" in case it is "Enabled".
Maximum Geographic Area shall be modified. Steps to be followed: Selecting an external system. In the associated edition fields the geodesic coordinate of its centre shall be displayed as well as the sides dimensions. It will be checked that the rectangle centre position belongs to the monitoring area of the RDP (defined in the adaptation data: MSEG file).
PSI-3200
The following operation buttons shall be available: PSI-3288 [Analyse]: It will perform an analysis of the configuration change. In case the changes are not admissible, the corresponding error message will be displayed. If changes are admissible, a window which confirms the analysis correction will be displayed. The button "OK" will shut the window. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist. In this case, a window of change confirmation will be displayed with the buttons "OK" and "Cancel" in order to process the change or to re-configure again. Once the change has been performed, the change confirmation message will be displayed indicating the change has been performed. The button "OK" of this window will close the window. [Exit]: It will close the window.
The possible error messages shall be the following: There is not response from the Computer for the function "Edition Request of External System". This message will be showed when the computer does not response to the Position in an estimated time term. Afterwards, it will show: Try the function again or abandon. Edition of External Systems request. Are you sure of doing this change.
PSI-3289
4.1.8.4.5.
AFTN Messages Query
It shall be possible for the PSI operator to query all AFTN messages stored in PSI-3507 the GSI.
The AFTN Messages Query function shall allow to establish filters which PSI-3508 make possible an adequate extraction of the desired information. 200 Software Requirements Description
These filters shall be: Time lag composed of starting date-time and ending date-time. Up to 10 alphanumeric characters linked by the logical operators (&=AND, |=OR) in the editing field provided for this purpose.
4.1.8.5. SUPPORT CONFIGURATION This function will allow to perform the following functions of configuration: 4.1.8.5.1. Tape Information Recovering PSI-464
The window shall show the following information: Device List Group Selection Selected Groups
Time Interval Selection: Initial (dd-mm-yy.hh-mm-ss), Final (dd-mmyy.hh-mm-ss). Tapes Numbers Selection: from Number to Number.
The information displayed in this window shall be obtained using the PSI-4441 SrvMwRec_GetTapeContain service.
The following actions shall be allowed in order to operate with this window: To select a device of the list "Seleccin de Disp ("Device List"). In an optional way, we could select a group of the list "Selection of Groups". The name of the group will be displayed in the "Selected Groups" area.
PSI-3241
It shall be allowed to define filters which make easier the searching PSI-3406 conditions: Time period to be recovered, indicating date, month, year, time, minutes and seconds in the "Selection of Time Interval" window section, with the "Initial" or "Final" label. Initial and final number of tape, in the "Selection of Tape Numbers" window section, aside the "of Number" label. The filters "Selected Groups", "Temporary Interval" and "Number of Tapes" PSI-3405 shall be affected by the AND operator.
The following operation buttons shall be available: PSI-3402 [Analyse]: It will perform an analysis of the configuration change. In case the changes are not admissible, the corresponding error message will be displayed. If changes are admissible, the window "Files to be recovered from the tape" will be displayed. [Execute]: Besides performing the change analysis, it will process it in case Software Requirements Specification 201
errors do not exist. In case, there are not error messages the window "Files to be recovered from the tape" will be displayed, where the different files which fulfil the selection criteria are listed. [Exit]: It will close the window. The possible error messages shall be the following: There is not response of the Computer for the function "Information Recovering from Tape Request" Are you sure of requesting this information. Edition error in enabled field. Error: Incorrect dates or initial date higher than final date Error: Initial tape longer than final tape. PSI-3403
NOTE: In this functionality, as in Information to be Recorded Configuration, PSI-3242 the concept of SPECIAL group is applied. In this case, for these groups, the option of including a new searching for strings filter is provided. On selecting and clicking on this group within the window of Selected Groups, the following window which gives us this operative shall be displayed: (Catalogue a group as SPECIAL must be done by including it in a configuration file. It may be catalogued as SPECIAL for each of these two functions in an independent way).
Searching String Window: The window Searching String shall display the following information: String1 String2 String3 String4 String5 PSI-3407
Insert. It provides the option of including a new searching filter for strings.
Files to be Recovered Window: The window Files to be Recovered shall display the following information: PSI-3410 Files: Number of files, Name, Occupied space in KBytes (Total and individual), Number of Tape, Recording Device, Validity period in days. Wildcards: Select All, Unselect All
In order to operate with this window the following actions shall be allowed: PSI-3243 disc. 202 Selecting the file/files by clicking on it/them Validity Period: It is the number of days this file will keep in [Sel All]: Click it in order to select all the files displayed in the Software Requirements Description
window. [Unsel All]: In order to delete all the selected elements. PSI-3411
The following operation buttons shall be available: [Analyse]: It will perform an analysis of the configuration changes. In case the changes are not admissible, the corresponding error message will be displayed. [Execute]: Besides performing the change analysis, it will process it in case errors do not exist, making effective the recovering request of the selected files . [Exit]: It will close the window.
The possible error messages shall be the following: Error in Validity Period Entered Tape does not correspond to the requested one. Recovering performed successfully.
PSI-3412
Periodical Test Process to Disp. Grab.1 (Recording Device 1) running. (In this case we must wait for the aforementioned process finishes and do the request again). Recovering in process
In case the GSI is in SIMULATION MODE on selecting this functionality PSI-3415 the previous window "Sessions in Simulation Mode Selection" shall be displayed.
Sessions in Simulation Mode Selection Window: In simulation Mode, before of performing the filter of the files, a simulation session contained in a determined period should be choice. Sessions in Simulation Mode Selection Window shall display: Sessions Session Data, fields for filtering for: User, Adaptation, Exercise, Session, Adaptation Version, Start, End. Filters: Initial Date (dd-mm-yy), Final Date (dd-mm-yy) PSI-3417
The information displayed in this screen shall be obtained using the PSI-4442 service SrvMwRec_GetSimulationSessions.
In order to operate with this window the following actions shall be allowed: PSI-3413 The period of interest in recovering information will be selected. For it, the fields of initial and final date will be filled up indicating date, month and year. [Session request] will be clicked on with the LB of the pointer device. Then, [Sessions] the Sessions which have been recorded in this interval will be visualized in the field. [Execute] will be clicked on with the LB of the pointer device after selecting the session of interest displaying the window "Tape Software Requirements Specification 203
Information Recovering" depicted above. [Exit]: It closes the window displaying the Subsystem State Window.
4.1.8.5.2.
Flight Progression Strips Printing
This function shall allow to induce the advanced strips printing according to PSI-466 the time lag established by the operator.
A function which shall allow to request the generation of flight strips, in an PSI-4383 advanced way, will exist.
The request shall be defined by: Time lag, composed of HINI (Initial time) and HFIN (Final time). It shall define the FPs for which the flight plan strips shall be printed, according to the criteria defined further below. ENROUTE or TMA Position whose printer shall print the flight plan strips requested from the centre. Or the origin logical remote of the flight plan strips and their destination logical remote. The operator shall be able to perform the Analyse, Execute or Exit functions. All executions shall be preceded by an analysis.
PSI-4384
The following analyses shall be performed: Time lag shall be mandatory. If an Enroute or TMA Position is selected, the printer and position shall be available at the time of the request. If an origin logical remote is selected, it must be sectorized. And the printer of the destination logical remote must be available.
PSI-4385
The execution will imply generation and printing of flight plan strips according to the TPV subsystem criteria for the data entered. If no destination position is selected, the flight plan strips shall come out by PSI-4387 the corresponding positions according to current sectorisation. If a TMA or En-route UCS is selected, the flight plan strips generated at the centre for the selected time lag shall be printed in this UCS, regardless of whether it is sectorized or not. If a Logical Remote is selected as origin, another Logical Remote shall be selected as destination, fulfilling the requirements that the origin logical remote must be sectorized and the destination one must have its printer available. In this case, only the flight plan strips generated by the origin logical remote in the specified time lag shall be obtained at the destination logical remote. Printing will be performed according to the flight plan strip printing criteria, the current adaptation data and the state of the positions and printers, defined in reference document (3) SACTA System Specifications. The window shall show the following: 204 Two scale bars will allow to enter the time lag of strips printing (initial Software Requirements Description PSI-3419
and final time). A UCS field will allow to select the destination UCS of the strips. PSI-3418
The following strips shall be generated: Coordination strips which correspond to the flights whose FIRT is included in the interval [HINI,HFIN+parameters of automatic coordination]. Preactivation strips, for departure FPs, which correspond to the flights whose entry time to the current segment is included in the interval (HINI, HFIN+parametres of automatic coordination). Progression strips which correspond to the flights whose FIRT or EXTT is included in the interval [HINI,HFIN], independtly of the state. In order to operate with this window the following actions will be allowed:
An UCS which is destination of the strips shall be selected through PSI-3245 the clicking with the LB of the pointer device on a UCS field. The following options will be available: A Centre UCS (sectored or not) with available IFV, in which case the Centre UCSs strips will be printed in the aforementioned UCS, and the strips from the remotes ones, will be printed in the corresponding remotes. DISTRIBUTED, in which case the strips will be printed in the UCSs (Centre and remotes), which are controlling or are going to control the flight. In case a IFV is not available, the strips will appear in the alternative IFV which had that UCS already defined. A sectored REMOTE, in which case that remote strips will be printed in a remote of the same dependency (it could be itself), with available IFV, and which could be selected in the drop-down menu "Destination" which will appear on the right on selecting this option. PSI-3421
In order to select the Initial and final Time: The cursor shall be located on the sliding block of the corresponding horizontal scrolling bar. Keeping clicked the button, the pointer device will be moved from left to right, until the value showed on the right of the scrolling bar is the nearest value to the desired time. In order to get the exact time, we will click on the arrows of the extremes of the scrolling bars, with the LB of the pointer device.
If Initial Time is later than Final Time, it shall be considered that the interval is PSI-3423 extended until the following day.
The following operation buttons shall be available: PSI-3422 [Analyse]: It will perform an analysis of the entered interval and of the UCS of destination. In case the changes are not admissible, the corresponding error message will be displayed. In case changes are admissible, a window which confirms the correction of the analysis will be displayed. The action button "OK" will allow to close this window. [Execute]: Besides performing the change analysis, it will process the generation of strips if the time lag is correct. In case error messages do not exist, it will clear the way to the confirmation window which indicates the change has been performed. The action button "OK" will allow to close this Software Requirements Specification 205
window. [Exit]: It will close the window. The function execution shall imply the generation, through the service PSI-4389 SrvMwER_Generate, of the following ER: PSIgfi001 SSTgfi001 (Only Tower)
4.1.8.5.3.
Paper in Tower Strips Printing
This functionality can be applied just in the PST's of Towers where the TPVT PSI-6541 functionality is available.
It shall be possible to print in advance the strips according with the time PSI-6546 interval established by the operator
A function in the tower environment shall allow to request the generation of PSI-6547 the flight strips in advance,
The request shall be defined by: PSI-6548 - Time interval, composed by HINI and HFIN.According to the criteria expressed later. - Tower Position (PICT) over whose printer, the requested from the centre strips will be printed. The following analysis shall be carried out: PSI-6549 - The time interval shall be compulsory. -If a PICT is selected the printer and the position shall be also available at the time of making the request. If a PICT is selected the strip generated in the centre for the chosen time PSI-6550 interval shall be printed in that PICT, independently if that is sectorized or not.
The screen shall display: Two scale bar which shall allow to introduce the time interval of strip printing (final and initial time) A PICT field shall allow to select the PICT where the strips are addressed. The PICT shall be a configuration data taken from: SrvAdapgv_PictsDataDepen
PSI-6551
The PICT where the strips shall be addressed can be selected by clicking with PSI-6557 the left button of the pointer device on the PICT field. The available options shall be: 206 Software Requirements Description
A PICT from the Centre (sectorized or not) with available IFV, in which case the strips from the PICT from the Centre shall be printed in that PICT. DISTRIBUTED, in which case the strips which have control or are going to have control of a fly in the PICT's shall be printed. To select the Initial and Final Time: The cursor scrolling bar. shall be placed over the corresponding horizontal PSI-6558
The pointer device shall be moved from left to right without get free the clicked button, until that the value appear at the right side of the scrolling bar were the most close to the wanted time The exact time will be obtained by clicking with the left button of the pointer device on the arrows on the edge of scroll bar If the final time were smaller than the initial time it shall be considered that the PSI-6560 interval will be extended until the next day.
The following button shall be available: PSI-6561 [Analyse]: The inserted interval and the PICT where is addressed shall be reviewed. If the request weren't allowed the corresponding error message will appear. If the request were allowed, a window which will confirm the correction of the test shall be displayed. The action button 'OK' shall allow to close the window. In that case it is not try to make any change, but a request. If those PICTs which have the IFV associated to not available is not displayed any more on the list of the menu will seem that the only cause of error is not having a PICT available. TPVT will be the one with the criteria available. [Execute]: Besides of test the request, it shall process the generation of strips if the time interval is correct. If there are not error messages, an confirmation window with the change done shall be displayed. The action button "OK" shall allow to close that window. [Close]: The button will close the window. The following event report shall be generated, through the service PSI-6559 SrvMwER_Generate, after executing the function: SSTgfi01
4.1.8.5.4.
AFTN Messages Consult
It will allow to consult the event reports generated by the AFTN input. The window shall show: mm). Time Lag Delimiters: Start (dd-mm-yy.hh-mm), End (dd-mm-yy-hhPSI-3426
207
Text
The following actions shall be allowed in order to operate with this window: PSI-3424 It will allow to select the messages which include a text or texts connected by connectives (AND, OR, NOT, etc) within a Time Interval defined with the following format: START: DDMMYYYY, HHMM, the initial time will be 00:00 of the previous day, by default. END: DDMMYYYY, HHMM, the final time will be the current one, by default. The following operation buttons shall be available: PSI-3246 [Visualize]: It will display the "Event Reports Visualization". [Exit]: After selecting the "Exit" button, the window "AFTN Messages Consult" will be closed.
4.1.8.5.5.
Event Report Query
This function will allow to perform consults of the event reports generated by PSI-470 any processor.
The window shall show: Subsystems Processor Codes Filter: Subsystem, Function, Number Time Interval filter: Start (dd-mm-yy.hh-mm), End (dd-mm-yy-hh-mm). Characters string filter.
PSI-3427
In order to operate with this window the following actions shall be allowed: PSI-3428 The Historical Information Consult window will allow to establish the filters needed to extract the desired information appropriately. These filters will be: Original subsystem through a drop-down menu Processor of the chosen Subsystem.
Code of the historic through three edition fields composed of the characters according to the Subsystem (already filled up on selecting the drop-down menus). Function and Number of event report which will generate the subsystem function. Up to 10 alphanumeric characters according to the connectives (&=AND, |=OR) in the edition field for this purpose. Likewise, the event reports shall be allowed to be included within a time interval which consists of date-initial time and date-final time with the following format DDMMYYYY, HHMM. The filters composition shall be affected by the AND function by default. PSI-3429
208
The following operation buttons shall be available: PSI-3430 [Visualize] Besides performing an analysis about the time interval edition and about the type of edited characters, it will process the searching of event reports affected, by displaying the List of Filtered event reports window. In case of data in disc do not exist, or in case of exceeding the text limit (1 MB), it will generate, through the service SrvMwER_Generate, the ER PSIdis001. [Count] It will return the number of founded elements. [Exit] It will close the window by displaying the Subsystem State window.
In the GSI, in SIMULATION MODE, this function shall have a previous PSI-3248 window where the available sessions will be displayed for the Event Reports query. See Session Selection window in Simulation Mode.
4.1.8.5.6.
FVEs printing
This bid has as aim,to print under request from PSI at any moment, the PSI-6345 information about the order of FVEs for all the Positions, the PSI will have a new function "Print FVEs" (F_IMP_FVEs) for it. The accessibility to the function "Print FVEs" shall be determined by the PSI-6346 profile of user configured in every PSI. This function will be configurable just in the centre with TPVT available. The window "Print FVEs" shall be accessible from the function bar or from the PSI-6347 contextual menu of the processors displayed in the POS scenario. The request for opening the window from the function bar will display automatically the POS Control Scenario. The printer used to print shall be determined by the configuration file PSI-6348 "SPV_LP.CFG"
The "Print FVEs" window shall consist of: An only primary view frame Sensitive buttons 'Print' and 'Close'.
PSI-6349
In the primary view frame it shall be displayed: PSI-6350 o Sensitive button 'Print' which will run the print action and will close the window ( if the execution is confirmed by the acknowledge window) Software Requirements Specification 209
o Sensitive button 'Close' which cancel the action and close the window. Clicking the sensitive button 'Print' will open an Acknowledge Window.
Whenever the PSI start-up, this shall call to the charge service PSI-6352 (SrvCwp_LoadEfssSorting)
It shall be printed like text beginning by: PSI-6353 The first Position, the Window A, the first area in the window and beginning by the order in the area for every PV/PVA it will be printed: PV Id, Last request/authorization/notation, Last time request/authorization/notation, Kind of aircraft, Format to print: An report header, which will contain " NN Position and X Window"( where NN will be the number of the Position and X will be A or B) A line with the text Zone N (where "N" will be the numeric value which identify the area) Report Header: N Zone PV Id, Last request/authorization/notation, request/authorization/notation, Kind of aircraft, PV Id, Last request/authorization/notation, request/authorization/notation, Kind of aircraft, N Zone
Last Last
time time
This shall be the associated text to request: ATC..................................................SOLICITUD ATC PUESTA_EN_MARCHA.....................SOLICITUD PUESTA EN MARCHA RETROCESO....................................SOLICITUD RETROCESO RODADURA......................................SOLICITUD RODADURA DESPEGUE......................................SOLICITUD DESPEGUE DESHIELO.......................................SOLICITUD DESHIELO ATERRIZAJE.....................................SOLICITUD ATERRIZAJE
PSI-6365
This shall be the associated text to authorizations: PSI-6366 ATC.................................................AUTORIZACIN ATC PUESTA_EN_MARCHA:...................AUTORIZACIN PUESTA EN MARCHA RETROCESO...................................AUTORIZACIN RETROCESO RODADURA.....................................AUTORIZACIN RODADURA 210 Software Requirements Description
ALINEAR..........................................AUTORIZACIN ALINEAR DESPEGUE.....................................AUTORIZACIN DESPEGUE ESPERA_TIERRA.............................AUTORIZACIN ESPERA EN TIERRA DESHIELO.......................................AUTORIZACIN DESHIELO ATERRIZAJE.................................... AUTORIZACIN ATERRIZAJE EFRUSTRADA..................................AUTORIZACIN FRUSTRADA This shall be the associated text to notations: AIRE................................................ANOTADO AL AIRE TOMA..............................................ANOTADO TOMA ESTACIONADO:...............................ANOTADO ESTACIONADO ABORTAR_DESPEGUE...................ANOTADO ABORTAR DESPEGUE PSI-6367
4.1.9.
EVENT REPORTS AN CONTROL FUNCTIONS
4.1.9.1. EVENT REPORTS This function will display the event reports generated by the system. 4.1.9.1.1. Description
In general, any text whose purpose is to inform about the system performance and that is addressed to a PSI or to an associated printer, or to an event report, will be included within the event report concept. An event report will be composed of: Date and time when the event report was originated. Processor where the event report was generated, using the same names displayed on the PSI scenarios. event report Code. Fixed text of the event report, associated to the event report code. Extended text of the event report, which will provide detailed information.
The "fixed text" in the event report will have a maximum of 80 characters The "extended text" in the event report will have a maximum of 3950 characters. The processor name will have 5 characters and it will be obtained: Through adaptation Defined name by configuration in the file SPV_CONTROL_PROC.CFG Codification
4.1.9.1.2.
The event report code will be of the SSSfffnnn type, being: SSS: Subsystem/Position fff: Function or process (in lowercase letters) nnn: Correlative number within the function or process. The number will be variable between 001 and 999. The subsystems will be: Subsystem Description Software Requirements Specification 211
CPV FDO DDE AST FOR FOT GIPV GSI LFP LFIP SILV PPR PSI REM RDS SST TDR TEC UCR UCT UFR UFT TPVT DLS SIS IMS PVT
Central Flight Plan Data Processing Flight Data Position DDE data unit ASTERIX data unit Focus Position Enroute/Reproduction Focus Position TMA/Reproduction Flight Plan Information Manager Information Recorder-Server Local Flight Plan Processing Local Flight Information Position Local MET/AIS Tower Radar Display Screen Integrated Supervision Position (PSI) Remote Positions Radar Data System (RDS) Tower Supervision Subsystem Radar Data Processing (TDVM ) Tecams Conventional Enroute Sector Control Unit Conventional TMA Sector Control Unit FOCUCS Enroute Sector Control Unit FOCUCS TMA Sector Control Unit Tower Flight Data System Data Link System SACTA Information System Simulation Computers Tower Flight Plans Processing
4.1.9.1.3.
Generation
There shall be a function allowing applications to generate an event report. It PSI-3485 takes the following as arguments: Code Extended text
The event reports related to the state changes of all the monitored elements PSI-4104 shall be generated.
For each configuration action the change event reports of configuration which PSI-4105 are associated with the performed configuration shall be generated in PSI.
212
4.1.9.1.4.
Display
Event reports generated by the different functions will be displayed in the following ways: Automatically The PSI shall be the receiver of the event reports for its monitoring. This PSI-3487 function corresponds to the SPV.
Whether an event report may be automatically recognised or not shall also be PSI-4111 defined by configuration.
The entire event report text (fixed and extended) shall be printed by the PSI-3488 associated lists printer.
In the event report windows of the corresponding PSI, the fixed part of the PSI-3489 event report and the extended text that fits in the screen shall be displayed. It is possible to request the display of a full event report window in which the entire event report shall be displayed. The operator shall be able to recognise the event report; a mark will indicate PSI-3490 that it has been read. event reports shall remain in the window during a period no longer than T1 (min), if they are recognised, and T2 (min), if they are not recognised. Aforementioned mark shall be a font colour change of the ER, switching from PSI-3491 white font colour to red font colour. These configurable times will be associated with the SPV_HRT.CFG file, that is, the mentioned file will allow to configure the following parameters: *non_rec_time *rec_time It shall be possible to display directly an event report with the recognition PSI-3493 mark, in case it had been indicated in the corresponding configuration file with automatic recognition. Manually
An event report report shall be displayed on the requesting PSI through the PSI-3496 event report Management function. Once displayed, it shall be possible to print the report in the printer associated to the position. The requesting PSI shall be whatever including the above functions PSI-3497 configured in its user profile and following the priorities established for it. The report shall contain the entire information associated to the requested event reports. In order to perform the aforementioned query, the event report filter of interest PSI-3498 shall be defined. The filter shall be comprised by: Origin subsystem 213
Origin Processor Time lag. Event Report Code (Subsystem, function and number: SSSfffnnn) Text characters string (fixed and extended).
4.1.9.1.5.
Storage
The event report will be grouped in files of 24-hour intervals, different for each origin processor, with the aim of making easier the subsequent searches. For purposes of requesting reports from the PSI, at least, the information corresponding to the last 48 hours will be available, without harm of being available for the PSI users, according to the performed configuration. 4.1.9.1.6. Inquiry
The PSI operator shall be able to check all the Event reports stored in the GSI PSI-4270 which belong to the configured recording period.
The Historical Information Inquiry shall allow to establish the filters which PSI-4271 make possible to extract the desired information appropriately. These filters will be the following: Source Subsystem through a drop-down menu Chosen Subsystem Processor
Historical code through three edition fields composed by the characters concerning to the Subsystem (already filled-in on selecting in the drop-down menus), Function and Number of event report which generates the subsystem function. Time lag comprised by date - initial time and date - final time. Up to 10 alphanumeric characters interacted by the connectives (&=AND, |=OR), edition field for the purpose. The filter composition is affected by the AND function.
4.1.9.1.7.
Last Event Reports Window
The following operations shall be able to be performed in the window "LAST PSI-3866 EVENT REPORTS" : Event Report Acknowledge: It will allow to locate the mouse pointer on the event report to be recognized (read) and click the mouse left button. The event report will change the font colour and it will become recognized. Exit button selection: It will close the display
214
4.1.9.2. CONTROL FUNCTIONS The following control functions will be performed: 1. 2. 3. 4. 5. 6. 7. 8. 9. Links and Devices Control Computers Control Tandem Control Time Synchronization Control Computer Processes Control State Control of Remote Positions to Pool Computers Printing Control Recording Control Integrity Control of Adaptation Data
The control function will be performed by the logic in charge of the dialogue with the corresponding device. By means of this dialogue its mode of operation state will be known, allowing their failures detection, and their recovering, when they take place. The control function is developed by the supervision subsystem. In this section, will only be described the different states, the actions and the considered event reports, that the PSI displays. For detailed information, check the supervision subsystem specification. 4.1.9.2.1. Devices and Link Control
The links control will be in charge of the links state control associated with the components of type: Elemental Link and Configurable Link. It will act regardless of the link enabling state. It will be based on the dialogue maintained with the logical located on the other extreme of the link. A link shall be able to be in the following states and the following ER will be PSI-3796 generated through the service SrvMwER_Generate: Without Data (SD) When the link switches to Connected: PSIcen001 When the link switches to Not Connected: PSIcen002 Non Connected (NC) When the link switches to Connected: PSIcen001 Connected (C) When the link switches to Not Connected: PSIcen002
Only tower: In every particular case, for tower the same event reports will be generated, with the same extended text. The Code will be SSTcen"number" instead of PSIcen"number".
Each processor shall monitor its synchronization state with the local NTP PSI-3798 client. The monitoring shall be performed using the NTP protocol, asking its corresponding local client about the state of its synchronization. A non Software Requirements Specification 215
synchronized situation shall cause the following effects: An alarm shall be displayed on the PSIs scenarios. The symbol of a red clock shall be displayed on the processor display. Synchronization recovery shall cause the alarm and the clock symbol to PSI-3799 disappear.
4.1.9.2.2.
Computers Control
This function will allow to know the computers state. Periodically, all the system computers will delivery a message of presence indicating their state to the PSIs. Through the reception or absence of the message, and because of the content of it, this PSIs' function could know the state of every computer. A computer shall be found in the following states, and the following ER will be PSI-3643 generated through the service SrvMwER_Generate: Not Available (ND), Failure (F), Without Data (SD) When the computer switches to Available state: PSIcor001 Available (D) When the computer switches to Failure state: PSIcor002 Available (D) When the computer switches to Not Available state: PSIcor001
Only tower: In every particular case, for tower the same event reports will be generated, with the same extended text. The Code will be SSTcor"number" instead of PSIcor"number".
4.1.9.2.3.
Time Synchronization Control
The states transitions and the ER generated, through the service PSI-3660 SrvMwER_Generate, due to those transitions shall be the following: NSC / SP -> ST Code: PSIcen001 ST / NSC -> SP Code: PSIcen002 SP / ST -> NSC Code: PSIcen002 Software Requirements Description
216
Only tower: In every particular case, for tower the same event reports will be generated, with the same extended text. The Code will be SSTcen"number" instead of PSIcen"number".
4.1.9.2.4.
Printing Control
This function will control printing of information that can be printed from the PSIs, through the available printers management. In order to print any kind of information, there shall be a configurable printers PSI-3692 list where the printing shall be attempted. This list shall be defined in a configuration file where the list of physical printers associated to a logic shall be established by order of preference. A printer shall be assigned according to the above configuration, continuing to PSI-3802 the next in the list, if it were not available.
The file which shall connect the logical and physical printers shall be PSI-3694 SPV_LP.CFG.
4.1.10. STATISTICS This function will display the statistics information of the different subsystems in an integrated way, from a point of view of the system, in the positions where the user profile is defined for this function. The statistical items shall be of two types: Direct: these items shall take the value from the moment within each refresh, such as CPU occupation %. Accumulative: these items shall be increased with each occurrence, such as number of received messages". Counters associated to incremental type statistical items shall be reset every 24 hours, or whenever the operator requests so. The time instant of the last reset shall be displayed. Regardless of the refreshing period of each statistic items displayed on the PSI-3457 window, the display of statistics windows shall be refreshed each 5 seconds, except the ones with radars which will be refreshed according to the antenna period of each radar. The following configuration functions could be performed: PSI-3456
217
4.1.10.1.
FUNCTIONAL STATISTICS
4.1.10.1.1. SILV Statistics This window has been created to display the VILMA subsystem statistics, it PSI-5885 shall consists of: Primary Control Display Areas shaped like always visible horizontal taps. The sensitive box will contain the titles: 'MET/AIS Message' and 'Affected Items'. The window shall be requested from the function menu. PSI-5400
The window shall be requested from SILV scenario elements which represent PSI-5401 the processors.
The tap with the 'MET/AIS message' statistics shall be the one selected by PSI-5402 default when the window is requested.
The window shall just display information, with an updating period of 5 PSI-5405 seconds , independently of the period to update the contained data. Primary View Frame 'MET/AIS Message' The primary view frame associated with the information about MET/AIS message received by VILMA is composed by the following unitary components: At the right top the primary view frame shall show the non selective text PSI-5408 'Since' and below an information view frame showing the time when the last reset of the displayed statistics at the view frame was done.
Next, a set of information view frame arranged like two tables shall be PSI-5409 displayed. These areas will appear with a non selective text to identify the kind of information contained : In the first case information view frame with meteorological information shall PSI-5411 be displayed arranged like a eight rows with four columns table ( a row will have associated just an information view frame ). Every column will have a non selective text title, these titles from left to right will be: 'Effective','Non Effective','Total','Total Acum', the last one indicating that values in the same vertical in the information view frame are accumulative, and its will be associated to the 'Reset' sensitive button. The structure in the table will have a first row with the no sensitive text placed more at the left than the others no sensitive text indicating that next rows are displaying detailed information contained in this first row. The non selective text in the first row shall be 'MET Messages' and the four PSI-5412 information view frame associated will display the number of MET message which are effective, no effective, total number and total accumulated number 218 Software Requirements Description
(since last reset) in SILV, respectively for each column. The second row in the table shall have the non selective text 'METAR/SPECI'. PSI-5413 For the METAR/SPECI MET messages the value of effective, no effective number, total number and total accumulated number of message (since last reset) in SILV will also be displayed , respectively for each column. Next row in the table shall have the same structure than the previous one, PSI-5414 non selective text 'TAF' will be displayed, with effective, non effective and total TAF message number in SILV, the total value of received messages since the last reset was committed, respectively. Fourth row shall have the non selective text 'TAF LARGO'; this item will have PSI-5415 just one information view frame, displaying the total number of TAF LARGO messages received by VILMA, since last reset ( here it only applies the total accumulated number for this kind of messages ). Next row shall have the non selective text 'SIGMET' displaying its four PSI-5410 information view frame with the value of received SIGMET messages which are effective, no effective and totals, in the last area it will be displayed the total number of accumulated SIGMET message received in VILMA since last reset. Sixth row shall display the same data than the previous one but for the PSI-5404 'SIGMET SST' messages ( non selective text associated to that row).
Seventh row shall have the non selective text 'AIRMET', they are displayed PSI-5416 next the values for effective AIRMET messages in VILMA, current AIRMET messages in VILMA but no effective, total AIRMET messages in VILMA and the accumulated total for the referred messages since the last reset. Finally, last row in this first table shall have the non selective text 'GAMET' PSI-5417 with its four information view frame associated.
The next structure shaped as a table shall display information related to AIS PSI-5418 messages, with a distribution as information view frame in six rows and four columns ( it does not mean a 6x4 information view frame total due to every state in the VILMA message are not applied to every message). The non selective text associated to each columns are: 'Active', 'Inactive' ,'Total', 'Total Acum'. As in the previous case, the structure in the table will have a first row with the no sensitive text placed more at the left than the others no sensitive texts indicating that next rows are displaying detailed information contained in this first row.
First row in this second table shall have information related to 'AIS Messages' PSI-5419 (non selective text), total and total accumulated number of AIS message received in VILMA since last reset will be the displayed information for this item. So, the information view frame will be placed in the two last columns. Software Requirements Specification 219
Second row in the table shall have the non selective text 'Static AEs NOTAM PSI-5421 '. For the NOTAM message number which contain information about Static Special Areas it will also be displayed just the total and total accumulated number. The next row shall have the non selective text 'Dynamic AEs NOTAM' with PSI-5422 the same previous horizontal structure. Just like in the two previous cases it will be displayed only the total and total accumulated number of NOTAM messages related to Dynamic Special Areas. Next row shall have the non selective text 'Divers NOTAM' and its four PSI-5423 information view frames, containing the number of divers NOTAM messages which have active state in VILMA, number of NOTAM divers messages which have inactive state in VILMA, number of total divers NOTAM messages and total accumulated divers NOTAM messages which has been received in VILMA since last reset. Fifth row in this second table shall display the non selective text 'NOTAM PSI-5424 Atis' and its four information view frame with the value of active, inactive, total and total accumulated NOTAM Atis message. Finally, the last row shall display the same information than the previous one, PSI-5426 but for 'NOTAM Trigger' messages.
The sensitive button 'Reset' shall work for those accumulative values, which PSI-5427 are displayed in the last column in the two tables.
The sensitive button 'Close' shall close the window
PSI-5429
Primary View Frame 'Affected Items' The primary view frame associated with information about affected items received by VILMA is composed by the next unitary components: A set of information view frame shaped as a table. These areas shall PSI-5425 have non selective texts to identify the kind of information contained in every one of them: The table shall contain information related to the Special Area state PSI-5432 not only Static but also Dynamics, this will be marked with the non selective text 'SPECIAL AREAS' on the column which contains the non selective text with the kind of area. The information will be distributed in four rows and five columns. The columns will contain the non selective text 'Preactive', 'Suspended', 'Occupied', 'Free' and 'Total'. The first row shall display through the information view frame the number of PSI-5433 'Static' AE (non selective text) which will be in one of the four previous states (preactive, suspended, occupied and frees) and the total value in the last 220 Software Requirements Description A#19079
column. The second row shall display bulleted and through the information view frame PSI-9137 the number of 'Static' Subvolumes (non selective text) which will be in one of the four previous states (preactive, suspended, occupied and frees) and the total value in the last column. The third row shall display through the information view frame the number of PSI-5434 'Dynamic' AE (non selective text) which will be in one of the four previous states (preactive, suspended, occupied and frees) and the total value in the last column. The fourth row shall display bulleted and through the information view frame PSI-9138 the number of 'Dynamic' Subvolumes (non selective text) which will be in one of the four previous states (preactive, suspended, occupied and frees) and the total value in the last column. The selective button 'Close' shall close the window. PSI-5435 A#19079
A#19079
A#19079
4.1.10.1.2. ATIS-SMI Statistics This window has been created to display the statistics of SMI and ATIS lines, PSI-5889 it shall consist of: Primary Control Display Areas shaped like always visible horizontal taps. The sensitive box will contain the titles: 'SMI' and 'ATIS'. The window shall be requested from the function menu. PSI-5448
The window shall be requested from SILV scenario elements which represent PSI-5449 the ATIS and SMI lines.
The window with the tap of the selected element 'ATIS' or 'SMI' shall be the PSI-5450 one displayed when the window is requested from the elements which represent them in the VILMA scenario. The tap with the 'ATIS' lines statistics shall be the one selected by default PSI-5459 when the window is requested.
The window shall just display information, with an updating period of 5 PSI-5460 seconds , independently of the period to update the contained data. Primary view frame 'ATIS' The primary view frame associated with information about affected items received by ATIS lines is composed by the next unitary components: Software Requirements Specification 221
At the right top the primary view frame shall show the non selective PSI-5464 text 'Since' and below an information view frame showing the time when the last reset of the displayed statistics at the view frame was done.
Next, a set of information view frames shaped like a table shall be PSI-5465 displayed. These areas will appear with a non selective text to identify the kind of information contained : For each row it shall be displayed on the left side of the table a title of non PSI-5466 selective text . This title will be the identifier (defined in adaptation) for each ATIS line adapted for the centre to where the PSI attends, the identifiers are corresponding with OACI indicator for each aerodrome origin of this ATIS lines. In the last row of the table it shall be displayed as title the non selective text PSI-5467 'Total', indicating that every area in this row contains the count of the values in all the lines for each statistic item. The table shall display two levels on the titles. These two levels in the titles PSI-5468 will display (completely) for each column, the non selective text indicating which statistic item is being displayed. The first level of titles shall have: from the first to the third column as title the PSI-5469 non selective text 'Number of Messages'; on the fourth column as title the non selective text 'Number of Failure'; from the fifth to the seventh column the title as non selective text ' Number of Messages Accumulated ' and on the last column 'Number of Accumulated Failures'. The second level of titles shall display: in the first column the non selective PSI-5470 text 'ATIS' indicating that in this column it will be displayed the number of ATIS message for every line and the total (for all the lines in the last row) which are effective in SILV; In the second column shall be the non selective text 'ATIS DEP' to indicate PSI-5471 that the effective number of DEP ATIS messages in SILV which arrived by the line and the total (for all the lines in the last row) which are effective in SILV; In the third column we shall be find the non selective text 'ATIS ARR' with the PSI-5472 same information than the contained in the previous column but this time for ARR ATIS messages. In the fourth column it shall be displayed the non selective text 'ATIS' to PSI-5473 indicate that the number of current failures in the ATIS lines and the total (for all the lines in the last row) de number of failures are gathered.
222
In the next columns the same information than in the fourth previous shall be PSI-5474 displayed, but here they are accumulative values, so, from the fifth to the eighth column there will be the same non selective text 'ATIS', 'ATIS DEP','ATIS ARR' and 'ATIS' respectively. In the bottom of the window the selective buttons 'Reset' and 'Close' shall be PSI-5475 displayed.
The button of 'Reset' shall be applied on the accumulative statistics items PSI-5476 displayed in this primary view frame 'ATIS.'
The selective button 'Close' shall close the window of 'ATIS-SMI Statistics'
PSI-5478
As above mentioned, the window shall just display information, with an PSI-5479 updating period of 5 seconds , or by clicking with the selective button 'Reset'. Primary view frame 'SMI' The primary view frame associated with information about affected items received by SMI lines is composed by the next unitary components: At the right top the primary view frame shall display the non selective text PSI-5452 'Since' and below an information view frame showing the time when the last reset of the displayed statistics at the view frame was done. Next, a set of information view frames shaped like a table shall be PSI-5481 displayed. These areas will appear with a non selective text to identify the kind of information contained : For each row it shall be displayed on the left side of the table a non selective PSI-5482 text as title. This title will be the identifier (defined in adaptation) for each SMI line adapted for the centre to where the PSI attends, the identifiers are corresponding with OACI indicator for each aerodrome origin of this SMI lines. In the last row of the table it shall be displayed as title a non selective text PSI-5483 'Total', indicating that every area in this row contains the count of the values in all the lines for each statistic item. The table shall display two levels on the titles. These two levels in the titles PSI-5484 will display (completely) for each column, the non selective text indicating which statistic item is being displayed. The first level of titles shall have: in the first column the non selective text PSI-5485 'Number of messages' indicating that in this column it will be displayed the number of SMI messages for each line and the total that is effective in SILV.
223
In the second column shall be displayed accumulative values, so the non PSI-5486 selective text 'Number of Messages Accumulated', displaying the accumulated number of SMI messages which arrived by the line and the total (for all the lines in the last row). In the third column 'Number of Accumulated Failures', displaying the number PSI-5487 of accumulated failures in SMI which have been detected for every line as well as the total. In the bottom of the window the selective buttons 'Reset' and 'Close' shall be PSI-5488 displayed.
The button of 'Reset' shall be applied on the accumulative statistics items PSI-5453 displayed in this primary view frame 'SMI.'
The selective button 'Close' shall close the window of 'ATIS-SMI Statistics'
PSI-5489
As above mentioned, the window shall just display information, with an PSI-5490 updating period of 5 seconds , or by clicking with the selective button 'Reset'.
4.1.10.1.3. MTCD Statistics The Statistics MTCD window shall consist of: A primary view frame: Selective buttons 'Reset' and 'Close' PSI-5493
The MTCD Statistics window shall be requested from the function menu if PSI-5494 any processor is in OPERATIVE state.
The window if is kept open shall just display information, with an updating PSI-5495 period of 5 seconds , independently of the period to update the contained data. View frame The primary view frame will consist of the next unitary components: At the right top the primary view frame shall show the non selective text PSI-5498 'Since' and below an information view frame showing the time when the last reset of the displayed statistics at the view frame was done. On the middle of the window a set of information view frame shall be PSI-5500 displayed gathered like a table, with five rows and a column:
224
In the first row the non selective text 'Number of request 'what-if' since last PSI-5501 reset' and the corresponding information view frame above mentioned.
In the second row it shall be displayed the non selective text 'Minimum PSI-5502 horizontal distance average value of detected conflicts since reset' and the information view frame with that information. The third row shall display the non selective text 'Minimum vertical distance PSI-5504 average value of detected conflicts since reset' and the information view frame with that information. The fourth row shall display the non selective text 'Number of current FP' and PSI-5505 the information view frame with that information.
The fifth row shall display the non selective text 'Number of current conflicts' PSI-5506 and the information view frame with that information.
The selective button 'Close' shall close the window .
PSI-5507
The button of 'Reset' shall be associated with the accumulative statistics PSI-5508 items displayed in this window.
4.1.10.1.4. AMAN Statistics The AMAN Statistics window shall consist of A primary control display panel with non selective text title 'Aerodrome Available'. Selective button 'Close'. PSI-4980
From the primary control display panel the primary embeded presentation PSI-5510 areas shall be controlled.
The AMAN Statistic window shall be accessible from the contextual menu of PSI-5513 the tandem processors where the AMAN functionality runs, if there are any processor in OPERATIVE state. The AMAN Statistics window shall be requested from the function menu if any PSI-5514 processor is in OPERATIVE state.
The first box in the primary control display list shall be the one selected by PSI-5515 default when the window is requested from the contextual menu of the tandem processors or from the function menu. Software Requirements Specification 225
The maximum size in the available aerodrome areas shall be adapted to the PSI-5511 size of the rest of the window. If this limit were surpassed a vertical scroll bar will appear.
The window shall just display information, with an updating period of 5 PSI-5516 seconds, or clicking the 'Reset' button independently of the period to update the contained data. Primary control panel list The primary control panel list shall consist of sensitive box with the OACI PSI-5518 identifiers for every aerodrome with the AMAN functionality configured associated to this Control Centre ('AMAN Aerodrome List' adaptation )and, besides, the 'AMAN Global' sensitive box. The embeded information view frame which control the 'AMAN Global' box will be lightly different to the embeded information view frame controlled by box of aerodrome. By clicking the sensitive button 'Close' it shall be possible to close the AMAN PSI-5520 Statistics window. Aerodrome-Primary information view frame The primary information view frame will consist of the next elements On the right top of the primary view frame the non selective text 'Since' shall PSI-5522 be displayed, and following, an information view frame displaying the time when the last reset over the statistics displayed in the view frame where committed. In middle of the primary view frame, the non selective text 'Aerodrome:' shall PSI-5523 be displayed, and a information view frame with the OACI code selected in the primary control display list. Next, a set of information view frame arranged like a table with four rows and PSI-5524 the same number of column than arrival-runway had the aerodrome shall be displayed. These areas will appear with a non selective text to identify the kind of information contained : As title in the first column the non selective text 'Arrival 1' and, below an PSI-5525 information view frame associated with the runway identifier (adaptation) configured in this moment as arrival 1. If the selected aerodrome would have a second runway configured like arrival 2, the title in the second column will be the non selective text 'Arrival 2' and, below an information view frame associated with the runway identifier (adaptation) configured at this moment as arrival 2.
In the first row for every runway configured as arrival, the information PSI-5528 concerning with the 'Arrival/hour Ratio' (title as non selective text associated with this first row) shall be displayed. 226 Software Requirements Description
The second row shall have as title the non selective text 'Medium Flight PSI-5529 Delay' displaying, for every runway configured as arrival, the above mentioned information about delays. In the third row, for every runway configured as arrival, the information about PSI-5530 'Number of sequence flights' (title as non selective text) shall be displayed.
Finally, the title as non selective text 'Number of manual actions' shall PSI-5531 display the mentioned information in as many information view frame as arrival runways configured for the aerodrome would be. The sensitive button 'Reset' shall be associated with every accumulative item PSI-5526 that exist in the window. (Aerodrome-Primary information view frame) AMAN Global-Primary information view frame The primary information view frame associated to the 'AMAN Global' box will display little differences regarding with the aerodrome primary information view frame. The primary information view frame associated to the 'AMAN Global' box shall PSI-5536 display instead of the non selective text 'Aerodrome:' and the corresponding information view frame associated, the non selective text 'AMAN Global:' and a set of information view frame separates by commas. These information view frames will contain the identifiers of the aerodrome adapted to this centre and with the AMAN functionality configured for every one of them, the number of configured runways as arrival for this aerodrome will be displayed in parentheses. The primary information view frame associated to the 'AMAN Global' box, PSI-5537 shall be the set of information view frames shaped as a table, containing an only column with non selective text 'Global'
4.1.10.1.5. Notes:
TDVM Statistics
These statistical items will refer to the UPDRs with a specific radar associated to them, in both operative and stand by state. Therefore, any of them, when a radar is assigned to two UPDRs will have two values: that referred one to the UPDR in which the radar is operative, and that corresponding to the UPDR to which the radar is associated as stand by. (1)Filtering is performed when outside the working area or when inside a rho-theta filtering area. (2)Rejection takes place due to saturation or age. (3)These statistical items are supplied by the UDDEs present in the system.
(4)These items will be associated to an UCS which has this radar assigned to it. Therefore, the radar will have as many values as control stations receive information from it. In order to determine the item, the TMA UCS and the radar must both be selected. The data associated to a TMA UCS will be relative to the TDVM associated to the station from where the executive control is performed. (5)These items will be associated to a stations TDVM, so that, there will be as many values as control stations. To determine the item, the station must be selected. The data associated to a TMA UCS will be relative to the TDVM associated to the station from where executive control is performed. (6)Includes filtering by Tracking Area, rho/theta Areas, Maximum Range and Silence Cone. 227 Software Requirements Specification
For each radar, with a periodicity of 1 antenna scan, it displays statistical data PSI-5899 calculated in the SACTA system Radar LAN relating to the delay of ASTERIXSACTA messages received from the UAST and UDDEs in the SACTA system Radar LAN. These data are presented in units of seconds with 3 decimals. The delay values distribution is characterised by the average, the standard deviation (99th percentile, calculated as P99=mean+3*standard deviation) and the maximum value, as it closely approximates a Gaussian distribution. For data on plots (PLT in the window), the Asterix messages of Category 1 are used. They will be calculated with the samples taken during an antenna scan and will display: the number of accepted plots (ACEP), the percentage of plots filtered by time offset (FIL_HOR), the average delay, the P99 and the maximum delay. For data on North messages (NRT in the window), the Asterix messages of Category 2 (service) are used, which in the case of Spanish radars will be the North marker, and in the case of Portuguese and French radars will be sector 0 crossing messages. They will be calculated with the samples taken during an antenna scan and will show the following: the number of accepted plots (ACEP- usually 1 plot per antenna scan) and the delay of the North marker plot received. This statistic will not be shown for DDE radars as they do not emit North marker messages. A dark grey background will be used to highlight the fields that can present Degradation and Failure states; a yellow background will be used for the Degraded state, and a Red background for the Failure state. The following checks are performed on this window (relative to the elements associated to the NRT-North reception radar and PLT-Delay Radar LAN): State of the NORTH MARKER RECEPTION (NRT counter) - only ASTERIX radars. Checking the reception of North marker messages in the Radar LAN, scan by scan. Usually, one North marker message is received with each antenna scan. The window field that shows the Degraded state is the NRT counter (NRT-ACEP). The possible states of the NRT element will be Nominal, Degraded and Failure, corresponding to the Nominal, Degraded and Failure radar states. It is adimensional. State of the DELAY IN RADAR LAN (PLT_Delay) - ASTERIX and DDE radars. Checking that the PLT_Delay values are under the thresholds established in ADMS. The window field that shows Degraded and Failure states is the Category 1 PLT_Delay P99 (PLT-P99). The possible states of the PLT element will therefore be Nominal, Degraded and Failure, corresponding to the Nominal, Degraded and Failure radar states. The units used are seconds with three decimals. RADAR DATA FILTERING - ASTERIX and DDE radars. Checking that there are no plots filtered for time offset in the corresponding TDVM (TDVM or TDVM-A) scan by scan. The window field that shows Degraded and Failure states is the Percentage of filtered plots (PLT-FIL_HOR). The possible states of the PLT element will therefore be Nominal, Degraded and Failure, corresponding to the Nominal, Degraded and Failure radar states. The units used are seconds with three decimals. Both first and second level texts from the following tables shall be indicative PSI-3201 ( it can be configurable by profile). See next table. PSI Functions related with Air Surveillance
1 Level Text Route / TMA 2 Level Text No Local TMA TDVT TWR Simple TWR
228
Normal Route Autonomous TMA Autonomous
Normal Autonomous
TDVM Statistics
TMA Autonomous
Autonomous
Table 4.1.10.1.5-55 : PSI functions related to Air Surveillance (TDVM Statistics) The possible functions for the Monoradar EADR Statistics shall be PSI-7034 F_ETDVM (function gathering the rest of the functions) F_ETDVM_NOR (Normal TDVM) F_ETDVM_RUTA (Route Autonomous TDVM) F_ETDVM_TMA ( TMA Autonomous TDVM) F_ETDVM_TOR ( Autonomous TDVM) If the function gathering the rest of the functions exists, the existing functions will hung up from that function. If that function gathering the rest of the function does not exist, any of those functions could exist without need any association
Normal TDVM Statistics In the Normal TDVM Statistics window the values according to the Normal Mode will be displayed. This window will show the following statistics: Multiradar tracks number PSI-3296
Number of tracks per radar. This statistics shall be displayed PSI-3295 through bars. The values represented by the aforementioned bars could be visualized in a window by clicking on the desired radar area with the LB. This window will include the following information: Name of the radar Tracks PSI-3294
Accepted Primary, Secondary Plots and Meteorological
STCA and RAW alerts ( Not in TDVT TWR )
PSI-3293
NTZ alerts
PSI-9134
A#17182
Number of meteorological targets ( Not in TDVT TWR )
PSI-3297
229
Number (occupied) of static volumes
PSI-9136
A#19079
Number (occupied) of dynamic volumes
PSI-9135
A#19079
The existing FPs, in holding, in flat and automatically shall be cancelled, PSI-3298 in the TDVM. (In TDVT TWR only FPs)
This window shall be only a presentation one, and it will be updated each PSI-3299 5 seconds. It will be possible to operate in order to exit from it by clicking on the "Exit" button with the LB of the pointer device . The following operation button shall be available: [Exit ]: It will close the window. PSI-3301
Enroute Autonomous TDVM Statistics/TMA Autonomous In the Enroute Autonomous TDVM Statistics/TMA Autonomous window the values according to the Autonomous mode will be displayed. For these statistics we shall be able to select the position from what we PSI-3206 want to display statistics, from all the started up Route/TMA positions The following statistics will be displayed. Multiradar tracks number. PSI-3306
Number of tracks per radar, for each selected radar in autonomous radar PSI-3305 in that position. This statistic shall be displayed through bars. The visualized values could be represented by these bars in a window, by clicking on a desired radar area, with the RB. The aforementioned window consists of the following information: Number of tracks Accepted Primary and Secondary Plots and Meteorological.
Flight plans number for each radar associated with the position.
PSI-3304
This window shall be updated each 5 seconds.
PSI-3303
The following operation button shall be available: 230
PSI-3307 Software Requirements Description
[Exit ]: It will close the window.
4.1.10.1.6. Radar Systematic Errors Statistics (F_EERRAD) The window could be requested from the function menu. Both first and second level texts from the following tables are indicative ( it can be configurable by profile). PSI-5548 See next table. PSI Functions related with Air Surveillance
1 Level Text Route / TMA TMA Autonomous Normal TDVM TMA Systematic Error Radar Route Autonomous TDVM Statistics TDVM Autonomous Autonomous TDVM Normal TDVM Autonomous TDVM 2 Level Text No Local TMA TDVT TWR Simple TWR
Table 4.1.10.1.6-56 : PSI Functions related with Air Surveillance (Systematic Error Radar Statistics) The possible functions for the Monoradar EADR Statistics shall be PSI-7035 F_EERRAD (function gathering the rest of the functions) F_EERRAD_NOR (Normal TDVM) F_EERRAD_RUTA (Route Autonomous TDVM) F_EERRAD_TMA(TMA Autonomous TDVM) F_EERRRAD_POS_TOR ( Autonomous TDVM) If the function gathering the rest of the functions exists, the existing functions will hung up from that function. If that function gathering the rest of the function does not exist, any of those functions could exist without need any association
Example If the function gathering the rest of the functions exists F_EERRAD, the existing function (F_EERRAD_NOR, F_EERRAD_TMA, F_EERRAD_RUTA) will hung up from it. If that function F_EERRAD, gathering the rest of the functions (F_EERRAD_NOR, F_EERRAD_TMA, F_EERRAD_RUTA) does not exist, any function could exist without need any association. Radar Normal Systematic Error Statistics The window shall just display information, with an updating period of 5 PSI-6960 seconds , independently of the period to update the contained data.
231
The window shall consist of: A Primary control display panel which will contain the identifiers for adapted radar to this dependency to work in Normal Mode and will control the primary embeded presentation area. Selective buttons 'Close', which close the window.
PSI-6961
Primary Control Display Panel Entitle like 'Radars' shall consist of sensitive box with the identifier for every PSI-6963 adapted radar in this dependency to work in Normal Mode.
Display control and closing the window (associated to the 'Close' button) shall PSI-6964 be possible operations on the primary control display panel Embeded presentation area The unitary components displayed in the window will be the followings: First control display list In the first horizontal, lined on the left side in the window it shall be PSI-6967 displayed the non selective text 'Automatic Adjustment Calculation' to indicate that the following information displayed will concern to this functionality. Next horizontal shall display three non selective texts with the corresponding PSI-6968 information view frames. The texts will be: 'Range (MN)', indicating that the associated area will provide information about the range used for the automatic calculation; 'Azimuth ()' displaying in the associated area the azimuth value in the automatic calculation and 'Gain (%)' with the value of the gain used in the automatic calculation. These three information view frames shall display data according to the PSI-6969 specified format, with five digits: the first digits will have the sign ('+','-') indicating that the following is the decimal part and that the last two digits will be that mentioned decimal part. In the next horizontal the no selective text 'TF Data' and 'Application Time' PSI-6970 (HH:MM format) values shall be displayed in an information view frame.
Next, a non selective line shall be displayed as separation.
PSI-6973
Second control display list The first horizontal in the secondary embedded area shall contain as title the PSI-6982 no selective texts 'Fixed Transponder Monitoring' and information concerning to it will be displayed in the following horizontals: The non selective text 'Antenna Rotation Period', 'Received Plots' and PSI-6983 'Rejected Plots' shall be displayed in the three information view frames in the first horizontal.
232
In a second level a non selective text as title 'Real Coordinates' lightly PSI-6984 separate to the right shall be displayed. Next, the tree non selective text 'Rho (MN)', 'Theta()' and 'SSR' with its corresponding information view frames referring to the real coordinates rho and theta from the fixed transponder and the send SSR code. The accuracy will be of hundredth of M.n. and hundredth of degrees (XXX,XX). In the other horizontal, the title with non selective text 'Calculated Difference' PSI-6985 shall be displayed (in the same position than 'Real Coordinates'). The concerning information will be displayed in the next horizontal through two information view frame preceded by its non selective texts 'Range (MN)' and 'Azimuth()', which will inform about the difference between the real position of the transponder and the calculated by the system, in range and azimuth. The accuracy will be of hundredth of M.n. and hundredth of degrees (XXX,XX) and also a character for the sing (+/-). The following element shall be a non selective line which will act as a PSI-6986 separation. Third control display list A set of information view frames placed each next to the other. There shall PSI-6976 be as many areas as radar number configured for this function mode less one. Every area will contain information concerning to a pair of radars, the non selective text displayed under every one of them will identify every one of those radars. All the radars will be displayed, with the same order than the displayed in the secondary presentation control display panel less the selected radar in the mentioned list. For every pair of radars formed by the selected radar and the radar whose identifier will be displayed under this area in the information view frame if an enough number of samples for the calculation of the systematic errors estimation exist to the calculation of systematic errors estimation, through the values 'I' (insufficient), 'S' (sufficient) and 'NA' (not apply). Background colour for every area could change, exception made of 'TF PSI-6977 Data', so the colour by default in the information view frames shall be in a way to indicate to the operator that the PSI in that area of the window could change the colour to indicate a state. Under certain conditions the background colour in the above mentioned areas will change to yellow. Radar Autonomous En-Route/TMA Error Statistics The systematic errors statistics associated to the autonomous working mode PSI-6989 shall be displayed in an only window for every Autonomous mode. For instance, in a dependency with Autonomous Route and Autonomous TMA mode there will be the functions 'Radar Autonomous En-Route Error Statistics' and 'Radar Autonomous TMA Error Statistics', respectively. The non selective text 'Radar Autonomous/Route Systematic Error Statistics' PSI-6991 shall be displayed in the title bar in the window.
233
The window shall just display information, with an updating period of 5 PSI-6992 seconds , independently of the period to update the contained data.
The window shall consist of: A Primary control display panel which will contain the identifiers for Control Position working in autonomous radar mode and will control the primary embeded presentation area. Selective buttons 'Close', which close the window.
PSI-6993
The 'Radar Autonomous Error Statistics' window will be a 'multiple-request' window, the characteristics are described in the annexe 14 in this document. It is not possible to have more than 10 open windows simultaneously (information for 10 different position) , by the fact of being a multi-request window with processors in its control display list. Primary control display list Entitled 'Control Position', composed by sensitive box with the identifier PSI-6996 (according to that displayed in the PSI scenario and identifying the CWP A or CWP B, and UCS to which it belongs) of every Control Position which shall be in a state different to 'NO DATA' to the selected autonomous mode. For the Autonomous Mode Working Position, its sensitive box included in the PSI-6997 primary control display list shall be framed with a purple frame (analogous to the one for POS RUTA, POS TMA and TWR POS to indicate that a position is working in autonomous mode of surveillance.) If the size of the list surpass the maximum size of the defined window, a PSI-6998 vertical scroll bar shall appear.
Display control and closing the window (associated to the 'Close' button) shall PSI-6999 be possible operations on the primary control display panel Embeded presentation area The view frame associated shall be analogous to one in a Normal working PSI-7001 mode. The difference are that in the control display list ( that in the normal mode is primary but in the autonomous is secondary) will just contain the three radars selected by the position to work in autonomous mode. So, in the area of the window containing information about 'Sample indicator' it will just be displayed two information view frames with its non selective texts; being correspondent with the two pair composed between the selected radar in the control list with the other two radars.
4.1.10.1.7. Air Surveillance Delay Statistics The Air Surveillance Delay Statistics window shall consist of: An only primary view frame: Selective buttons 'Reset' and 'Close' PSI-5624
234
PSI-5625
The window shall be requested from the contextual menu in TDVM scenario PSI-5626 which represent the Asterix radar.
The window shall just display information, with an updating period of 5 PSI-5627 seconds, although data are updated every 50 cycles of radar for every radar (in function of the period for updating data, it means the period for each radar). View frame A list with a double number of rows that the Asterix radar is configured to PSI-5630 display information concerning to surveillance delays in the list. The list shall have the following characteristics: The first column shall consist of non selective text , which will be the identifier PSI-5631 for an Asterix radar and will embrace two rows.
The second column shall have as title the non selective text 'Redundancy (R) PSI-5632 Degrees' and will consist of an information view frames which also will embrace two rows every one of them. This information view frames will have a darkest background in the box, indicating that this areas can change the colour under certain criteria in function of the displayed redundancy degree . The third column in the list shall consist of non selective text. The odd rows PSI-5633 will have the text 'NORTH' and the evens rows 'PSR/SSR'.
The next column shall have as title the non selective text 'Media' and it will PSI-5634 consist of information view frame. The areas of even rows will display the average delay of the messages from the NORTH and will have a darkest background indicating that this areas can change the colour under certain criteria. The areas in the even rows will display the medium delay concerning to tracks-plots. The fifth row shall have as title the non selective text 'P99'. The information PSI-5635 view frame will display the 99th percentile for delays concerning to NORTH messages in the even rows and the 99th percentile for delays concerning to plots-tracks in the even rows; furthermore, the areas will have a darkest background indicating that can change the colour. The sixth column has as title the non selective title 'Mx' and shall consist of PSI-5636 information view frame for the maximum values in the delay of NORTH messages and the maximum values in the delay concerning plots-tracks. The consecutive column has the non selective title ' Delay Plots Number> PSI-5637 Critique' and this shall consist of information view frame with the number of NORTH messages and plots-tracks which has surpassed the critics delay Software Requirements Specification 235
( defined in DA), this information will be displayed in the odd and even rows, respectively. Over the titles from the fourth to the seventh column shall exist another title of PSI-5638 non selective text ' Delays in seconds' indicating that this four columns will display information concerning to Delays. Finally the eighth column shall have as title the non selective text 'Period of PSI-5639 Calcul (Number of Samples)'
Furthermore, the values to threshold in vigilance and critic delays defined in PSI-5641 DA shall be displayed with auxiliar combo box (accessible with BDR)
The auxiliar combo box will not hide, under no circumstances, the remaining PSI-5642 information presented in the 'Surveillance Delay Statistics' referred to the radar whose combo box is displayed. Furthermore, in the window a note shall be displayed to inform about the possibility to access to that information. The auxiliar combo box shall display the following information for every radar: PSI-5643 'Redundancy Degree' through the non selective text , and next an information view frame with the nominal redundancy value defined.
The auxiliar combo box shall display the following information for every radar. PSI-5644 ' Media Delay NORTH': through the Non selective text and the Non selective texts and information view frames following the previous text: o Synchronism Failure Threshold, this is not an adaptation data, because it is a fixed value; hence the Non selective text 'UF=0' will be displayed. o Non selective text 'UFF' and the presentation view frame with the value for End of Synchronism Failure Threshold (UFF), o Non selective text 'UD' and the associated presentation view frame with the value for End of Synchronism Degradation Threshold, o Non selective text 'UFD' and the presentation view frame with the value for End of Degradation Synchronism, o Non selective text NOM and the associated presentation view frame with the value for Media Category 2 Nominal Delay.
The auxiliar combo box shall display the following information for every radar. ' P99 NORTH': through the Non selective text and the Non selective texts and information view frames following the previous text: o Non selective text 'P99NOM' and the information view frame with the value of the 99 Percentile Category 2 Nominal, 236
PSI-5645
o Non selective text 'UFD' and the presentation view frame with the value of End of Threshold Degradation for Category 2 Vigilance, o Non selective text 'UD' and the associated presentation view frame with the value for End of Synchronism Degradation Category 2 Threshold, o Non selective text 'UFF' and the presentation view frame with the value for End of Failure Delay Category 2 Threshold, o Non selective text 'UF' and the information view frame containing the value for Critic Delay Category 2 Nominal.
The auxiliar combo box shall display the following information for every radar. P99 PSR/SSR: o Non selective text 'P99NOM' and the information view frame with the value of the 99 Percentile Category 1 Nominal, o Non selective text 'UFD' and the presentation view frame with the value of End of Threshold Degradation for Category 1 Vigilance, o Non selective text 'UD' and the associated presentation view frame with the value for End of Synchronism Degradation Category 1 Threshold, o Non selective text 'UFF' and the presentation view frame with the value for End of Failure Delay Category 1 Threshold, o Non selective text 'UF' and the information view frame containing the value for Critic Delay Category 1 Nominal.
PSI-5646
The previous information shall be displayed graphically: UF=0 Redundancy Degree:-NORTH Media Delay: UFF=-- UD=-- UFD=-- NOM= -UFF=-- UF=-UFF=-- UF=--
PSI-5640
P99 NORTH: P99NOM=-UFD=-- UD=- P99 PSR/SSR: P99NOM=-UFD=-- UD=-Selective buttons
The operation possible to do shall be 'Close' the window
PSI-5648
4.1.10.1.8. Surface Surveillance Delay Statistics The Statistics MTCD window shall consist of: An only primary view frame: Selective buttons 'Reset' and 'Close' PSI-5654
237
PSI-5655
The window shall be requested from the contextual menu in TDVM scenario PSI-5656 which represent the surface sensor.
The window shall just display information, with an updating period of 5 PSI-5657 seconds. View Frame A list with a double number of rows that the Asterix radar shall be configured PSI-5659 to display information concerning to surveillance delays in the list. The list will have the following characteristics: The first column shall consist of non selective text , which will be the PSI-5660 identifier for an Asterix radar and will embrace two rows. The second column will have as title the non selective text 'Redundancy (R) Degrees' and will consist of an information view frames which also will embrace two rows every one of them. These information view frames will have a darkest background in the box, indicating that these areas can change the colour under certain criteria in function of the displayed redundancy degree . The third column in the list shall consist of non selective text. The odd rows PSI-5661 will have the text 'SUC' and the evens rows 'Tracks'.
The next column shall have as title the non selective text 'Media' and it will PSI-5662 consist of information view frame. The areas of even rows will display the average delay of the messages from the beginnings of cycle in surface systems and will have a darkest background indicating that this areas can change the colour under certain criteria. The areas in the even rows will display the medium delay concerning to tracks-plots. The fifth row shall have as title the non selective text 'P99'. The information PSI-5663 view frame will display the 99th percentile for delays concerning to messages from the beginnings of cycle in surface systems in the even rows and the 99th percentile for delays concerning to plots-tracks in the even rows; furthermore, the areas will have a darkest background indicating that can change the colour. The sixth column has as title the non selective title 'Mx' and it shall consist of PSI-5664 information view frame for the maximum values in the delay of messages from the beginnings of cycle in surface systems and the maximum values in the delay concerning plots-tracks. The consecutive column has the non selective title ' Delay Plots Number> PSI-5665 Critique' and it shall consist of information view frame with the number of messages from the beginnings of cycle in surface systems and plots-tracks which has surpassed the critics delay ( defined in DA), this information will be 238 Software Requirements Description
displayed in the odd and even rows, respectively. Over the titles from the fourth to the seventh column will exist another title of non selective text ' Delays in seconds' indicating that this four columns will display information concerning to Delays. Finally the eighth column shall have as title the non selective text 'Number of PSI-5667 Blocks' where in the presentation view frames will be displayed the number of received blocks while the period of calcul of the sensor. Furthermore, the susceptible values to trigger Degradation and Failure states PSI-5669 defined in DA shall be displayed with auxiliar combo box (accessible with BDR). The auxiliar combo box will not hide, under no circumstances, the remaining information presented in the 'Surface Delay Statistics' referred to the radar whose combo box is displayed. Furthermore, in the window a note will be displayed to inform about the possibility to access to that information. The auxiliar combo box shall display the following information for every radar: PSI-5670 'Redundancy Degree' through the non selective text , and next an information view frame with the nominal redundancy value defined. The auxiliar combo box shall display the following information for every radar. 'Media Delay SUC': through the Non selective text and the Non selective texts and information view frames following the previous text: o Synchronism Failure Threshold, this is not an adaptation data, because it is a fixed value; hence the Non selective text 'UF=0' will be displayed. o Non selective text 'UFF' and the presentation view frame with the value for End of Synchronism Failure Threshold (UFF), o Non selective text 'UD' and the associated presentation view frame with the value for End of Synchronism Degradation Threshold, o Non selective text 'UFD' and the presentation view frame with the value for End of Degradation Synchronism, o Non selective text NOM and the associated presentation view frame with the value for Media Category 2 Nominal Delay. The auxiliar combo box shall display the following information for every radar. ' P99 SUC': through the Non selective text and the Non selective texts and information view frames following the previous text: o Non selective text 'P99NOM' and the information view frame with the value of the 99 Percentile Category 2 Nominal, o Non selective text 'UFD' and the presentation view frame with the value of End of Threshold Degradation for Category 2 Vigilance, o Non selective text 'UD' and the associated presentation view frame with the value for End of Synchronism Degradation Category 2 Threshold, o Non selective text 'UFF' and the presentation view frame with the value for End of Failure Delay Category 2 Threshold, o Non selective text 'UF' and the information view frame containing Software Requirements Specification 239 PSI-5672 PSI-5671
the value for Critic Delay Category 2 Nominal.
The auxiliar combo box shall display the following information for every radar. P99 Tracks: o Non selective text 'P99NOM' and the information view frame with the value of the 99 Percentile Category 1 Nominal, o Non selective text 'UFD' and the presentation view frame with the value of End of Threshold Degradation for Category 1 Vigilance, o Non selective text 'UD' and the associated presentation view frame with the value for End of Synchronism Degradation Category 1 Threshold, o Non selective text 'UFF' and the presentation view frame with the value for End of Failure Delay Category 1 Threshold, o Non selective text 'UF' and the information view frame containing the value for Critic Delay Category 1 Nominal.
PSI-5673
The previous information shall be displayed graphically: UF=0 Redundancy Degree:-SUC Media Delay: UFF=-- UD=-- UFD=-- NOM= -UFF=-- UF=-UFF=-- UF=--
PSI-5674
P99 SUC: for every radar P99NOM=-UFD=-- UD=- P99 Tracks: for every radar P99NOM=-UFD=-- UD=-Selective buttons
The operation possible to do shall be 'Close' the window
PSI-5676
4.1.10.1.9. Surface Sensor Statistics (F_ESSUP) This window which displays 'Surface Sensor Statistics' shall just display PSI-5045 information, with an updating period of 5 seconds , independently of the period to update the contained data.The window will consist of: Primary Control Display Panel where the configured identifiers of surface sensors will be displayed and it will control the primary embeded presentation areas. Selective button 'Close'.
240
PSI-5047
The Surface Sensor Statistics window shall be requested from the contextual PSI-5051 menu in TDVT scenario which represent the surface sensors.
The Surface Sensor Statistics window shall be a 'multiple-request' window, PSI-5052 the characteristics are described in the annexe 14 in this document. Primary Control Display Panel It shall have the 'Surface Sensor' title, it shall consist of sensitive box which PSI-5057 shall contain the identifier of every configured surface sensor (adaptation data) to this centre. Display control and closing the window (associated to the 'Close' button) shall PSI-5058 be possible operations on the primary control display panel Primary view frame Here in after the primary view frame is described: The following elements are shaped like a table, there shall be a first column whose rows shall be a set of non selective texts with the name of the statistics items displayed in this window. The first row shall also consist of titles with non selective text, the information view frame shall be placed in the crossroad of the titles. The non selective text title in the first row shall be: 'Total','Media','% over PSI-5056 received' and 'Max in a cicle' In the next horizontal it will be displayed the first statistic item with the non selective text 'Received' title (values concerning to the ADV component) and the three information view frame associated, every one of them in the same vertical than the titles above mentioned and containing the information concerning to the total, media and max number (in a cycle) value of received blocks, respectively ( the item with information about the percentage over received will not be displayed). Here in after the non selective text title 'De-configured' (values concerning the PSI-5589 TDS component) and its four information view frame associated, with the same structure than the previous horizontal, containing, respectively, the total number of rejected tracks due to de-configuration of the sensor, % of rejected tracks due to de-configuration of the sensor over received and the maximum number of rejected tracks by de-configuration of the sensor in a cycle. In the following horizontal an statistic item shall be displayed with the non PSI-5061 selective text title 'Approved' ( values concerning the TDS component) and its four information view frame associated, every one in the same vertical than the above mentioned titles and containing the information about the total value of accepted tracks, accepted track media, percentage of accepted tracks over received blocks and max number of received tracks in a cycle, respectively. Software Requirements Specification 241 PSI-5055
The following element shall be a non selective text title 'Rejected' which shall PSI-5062 involved three horizontal with the non selective text 'by time' ( values concerning the TDS component), 'by format' ( values concerning the ADV component) and 'by geography' ( values concerning the TDS component) and the four corresponding information view frame for every text displaying the total, media and percentage over received number of message and the maximum number in a cycle of temporary causes,by format or geography, respectively. The non selective text 'Accepted' (values concerning the ADV component) PSI-5049 which appear in the next two horizontals with the non selective text 'SUC' and 'PST' and the four information view frame associated to every text, displaying the value for total accepted, media, % over received and max number of accepted in a cycle for SUC and PST messages.
4.1.10.1.10. TDVT Statistics (F_ETDVT) The TDVT Statistics window shall consist of: A primary view frame Selective button 'Close' PSI-5594
The TDVT Statistic window shall be accessible from the contextual menu of PSI-5070 the tandem processors where the TDVT functionality runs, if there are any processor in OPERATIVE state. The window shall be requested from the function menu if any processor is in PSI-5071 OPERATIVE state.
The window shall just display information, with an updating period of 5 PSI-5072 seconds , independently of the period to update the contained data. View frame The primary view frame is composed by the following unitary components: A set of information view frames shall be displayed in the middle of window PSI-5601 shaped as a table, with 11 rows and 3 columns:
The first row in the first column shall display the non selective text 'ADV' PSI-5602 comprehending two rows.
The second row in the first column shall 'TDVM-S' which comprehend 10 rows.
display the non selective text PSI-5603
The third row shall dispose as many information view frame arranged as rows PSI-5604 as the second column and will have as title non selective text 'Total'.
242
Distance between the first row in the first column and the second row in the first column which will correspond with the second and third row of the second and third column will be underline with double line. The first row in the second column shall display the non selective text PSI-5606 'Asterix 10 Incorrect Messages' and the corresponding information view frame with the instantaneous value. In the second row in the second column the non selective text ' Asterix 10 PSI-5607 SIC/SAC Incorrect Messages' and the corresponding information view frame with the instantaneous value. In the third row in the second column the non selective text 'TDVT Tracks' PSI-5608 shall be displayed and the corresponding information view frame above mentioned. In the fourth row in the second column the non selective text 'SMMS master' PSI-5610 and the corresponding information view frame above mentioned.
In the fifth row in the second column the non selective text 'SMMA master' PSI-5611 and the corresponding information view frame above mentioned.
In the next row in the second column the non selective text 'SMR1 master' PSI-5612 and the corresponding information view frame above mentioned.
In the next row in the second column the non selective text 'SMR2 master' PSI-5614 and the corresponding information view frame above mentioned.
In the eighth row in the second column the non selective text 'APP master' PSI-5615 and the corresponding information view frame above mentioned. The distance between the next rows (8th and 9th) of the columns 2 and 3 will be stressed. In the 9th row the second column shall display the non selective text ' PSI-5613 Number of FP in TDVT' and the corresponding information view frame above mentioned. The next row in the second column shall display the non selective text PSI-5617 'Number of Correlated TDVT Tracks' and the corresponding information view frame above mentioned. In the 11th row in the second column the non selective text 'Number of PSI-5618 labeled TDVT tracks' and the corresponding information view frame above mentioned. The action button 'Close' shall close the window. PSI-5619
243
4.1.10.1.11. EADR Statistics 4.1.10.1.11.1. EADR Statistics (only tower)
In the window EADR Statistics, statistics shall be visualized for each PSI-3309 emplacement and mode. Both first and second level texts from the following tables are indicative ( it can be configurable by profile). PSI-3208 See next table. PSI Functions related with Air Surveillance
1 Level Text Route / TMA Normal TDVM Monoradar EADR Statistics Route Autonomous TDVM TMA TDVM Autonomous 2 Level Text No Local TMA TDVT TWR Normal TDVM TDVT SMR TDVM Autonomous TDVM Simple TWR
Table 4.1.10.1.11.1-57 : PSI Functions related with Aire Surveillance(Monoradar EADR Statistics) The possible functions for the Monoradar EADR Statistics shall be PSI-7033 F_EEADR (function gathering the rest of the functions) F_EEADR _NOR (Normal TDVM) F_EEADR_RUTA ( Route Autonomous TDVM) F_EEADR_TMA (TMA Autonomous TDVM) F_EEADR_TOR (Autonomous TDVM) F_ESMR If the function gathering the rest of the functions exists, the existing functions will hung up from that function. If that function gathering the rest of the function does not exist, any of those functions could exist without need any association.
In the window "Normal Radar Emp Statistics/Auton Route/Auton TMA" the PSI-3310 information according to each available radars in Normal/Auton. , Route/Auton TMA shall be displayed.
244
A#12852
DESCRIPTION FOR EACH RADAR: For each Local Radar: Type DDE Per Line [1 .. 2] N of line failure. N of accepted messages. N of rejected messages. N of messages filtered by manual nonconfiguration.. Type ASTERIX N of accepted messages. N of rejected messages. N of messages filtered by manual nonconfiguration.. Delays for each Radar: - N of NRTmessages per radar cycle (it will be 1, by default). - Delay corresponding to the received NRT in the radar cycle. Type ASTERIX or DDE Delays for each Radar: - N of plots cat.1 - Delays of plots cat.1 values (Average, P99 and Maximum.) - Percentage of plots Filtered by time lag according to received plots. RADAR PROCESSING For each radar and for each kind of processing: (PSR, MET, SSR) Accepted Plots Filtered Plots - Manual non-configuration. - Geographic (A) - Time - Split. - Reflex. - Saturation. For each Radar: - Rejected due to transmission or format. Instantaneous Complete Per period Instantaneous Instantaneous Instantaneous Instantaneous Instantaneous Instantaneous Complete Complete Complete Complete Complete Complete Per period Per period Per period Per period Per period Per period Instantaneous Complete Per period Instantaneous Instantaneous Instantaneous Complete Complete Complete Per period Per period Per period Instantaneous Instantaneous Complete Complete Per period Per period Acumulable Acumulable Acumulable Complete Complete Complete Per period Per period Per period Instantaneous Instantaneous Instantaneous Instantaneous Complete Complete Complete Complete Per period Per period Per period Per period TYPE UNITS TYPE OF UPDATE
245
DESCRIPTION - Calculated antenna Period. - Test Plots. - N of monoradar tracks. - N of local meteorologic plots. - N of Rho-Theta enabled areas.
TYPE Instantaneous Instantaneous Instantaneous Instantaneous Instantaneous
UNITS Complete Complete Complete Complete Complete
TYPE OF UPDATE Per period Per period Per multi period Per period Per event
Table 4.1.10.1.11.1-58 : List of statistics elements of a radar emplacement in Normal Mode. Statistics could be of two types: instantaneous or accumulative. PSI-3308 In the first case, we shall deal with values which will take the value from the instant in each refresh. In the second case, we will deal with values which could be increased with each update of the window. The counters associated with the statistic elements of increasing type shall be PSI-3313 reinitiated each 24 hours or when the operator requests it.
A background of dark grey colour shall be used in order to highlight the fields PSI-3314 which are susceptible of displaying Degradation and Failure states; in case of Degraded state, yellow background, and in case of Failure state, Red background. In this window the following test (according to the elements associated with PSI-3315 NRT-North Reception radar, and PLT-Delay in Lan of Radar) shall be performed: RECEPTION OF NORTH MARK state (counter of NRT)- only ASTERIX radars. Checking of the messages reception of North Mark in the Radar Lan, each cycle. The usual will be to receive a message of North Mark in each antenna rotation period. The field of window susceptible of displaying the Degradation state will be the "NRT Counter" (NRT-ACCEP). The possible states of the NRT element will be Nominal, Degraded and Failure, corresponding to the Nominal, Degraded and Failure radar states. It is dimensionless. DELAY IN THE RADAR LAN state (Delay_PLT)-ASTERIX and DDE radars. Checking of the "Delay_PLT" values shall be below the established thresholds in ADMS. The window field susceptible of displaying the Degradation and Failure states will be the P99 of the Delay_PLT of category 1 (PLT-P99). Therefore, the possible states of the PLT element would be Nominal, Degraded and Failure, corresponding to the Nominal, Degraded and Failure radar states. The units will be "seconds", with three decimals. RADAR DATA FILTERED-ASTERIX and DDE radars. Checking of not being filtered plots due to time lag in the dealed TDVM (TDVM or TDVMA) each cycle.The window field susceptible of displaying the Degradation and Failure states will be the percentage of filtered plots (PLT-TIME_FILT). Therefore, the possible states of the PLT element would be Nominal, Degraded and Failure, corresponding to the Nominal, Degraded and Failure radar states. The units will be "seconds", with three decimals. 246 Software Requirements Description
Also the following field shall be highlighted with Red background although it PSI-3312 does not indicate the radar failure state. Maximum of the Demora_ PLT ( Delay_PLT) category 1 (PLT-Max) The following operation button shall be available: [Exit ]: It will close the window. PSI-3316
4.1.10.1.11.2.
EADR Statistics
This window has been created to display the EADR subsystem statistics, it PSI-6733 shall consists of: A primary view frame Selective button 'Exit' PSI-6734
The window shall be requested from SILV scenario elements which represent PSI-6735 the processors.
The window shall just display information, with an updating period of 5 PSI-6736 seconds, independently of the period to update the contained data. Primary View Frame The primary view frame shall be composed by the following unitary PSI-6748 components:
There shall be a title Statistics (Normal Radar), Statistics (TMA PSI-6749 Autonomous Radar) or Statistics (RUTA Autonomous Radar) in function of the kind of statistics required from the corresponding menu. At the left top the primary view frame shall display the non selective text PSI-6750 Location followed by the name of the radar whose statistics has been requested. Next, the information shall be grouped in four information view frames PSI-6751 (separated by a line between every one), shaped as tables, composed by columns and rows: The first area will be composed by following the elements: The first row shall display the non selective text PLOTS centred in the PSI-6753 window, as title. Software Requirements Specification 247
The second row shall display the non selective text Plots PRI followed by a PSI-6754 horizontal bar (diagram) where the number of plots treated related to the primary radars will be depicted through a bar. The horizontal bar will be followed by the non selective text 750 (maximum number of plots which can be depicted with the bar). The third row shall display the non selective text Plots SEC followed by a PSI-6757 horizontal bar (diagram) where the number of treated plots related to the secondary radars will be depicted through a bar. The horizontal bar will be followed by the non selective text 750 (maximum number of plots which can be depicted with the bar). The fourth row shall display the non selective text Plots MET followed by a PSI-6758 horizontal bar where the number of treated plots related to meteorological information will be depicted through a bar. The horizontal bar will be followed by the non selective text 750 (maximum number of plots which can be depicted with the bar). The fifth row shall display the non selective text ACEP and FILT. PSI-6759
The sixth row shall display the non selective text ACEP ,HOR, GEO, PSI-6762 SAT, DES, REF and SPLIT in a row placed just under the FILT text. The seventh row shall display the non selective text PRI. The first column PSI-6763 after that text will be placed under the non selective text ACEP so the interception will give number of accepted plots by the primary radar.
A#12852
The intersection of the seventh row entitled as PRI with the columns below PSI-6760 the rows HOR, GEO, SAT and DES shall display the corresponding information. The eighth row shall display the non selective text SSR. PSI-6761
The first column of the eighth row shall be placed under the non selective text PSI-6765 ACEP, so the interception will give the number of accepted plots by the secondary radar. The intersection of the eighth row entitled as SSR with the columns below PSI-6766 the rows, HOR, GEO, SAT, DES, REF and SPLIT, shall display the corresponding information. The ninth row shall display the non selective text MET. The first column after PSI-6769 that text will be placed under the non selective text ACEP, so the interception will give the number of accepted plots of meteorological 248 Software Requirements Description A#12852
information. The intersection of the ninth row entitled as MET with the columns below the PSI-6770 rows GEO, SAT, DES shall display the corresponding information.
The second area shall be composed by the following elements:
PSI-6771
The first row shall display the non selective text ACEP,FIL HOR, DELAY PSI-6768 (seconds)" (regardless the kind of radar).
The second row shall display the non selective text "VALUE", "AVERAGE", PSI-9054 "99%" and "MX", under the text "DEMORA"
The third row shall display the non selective text NRT"
PSI-9055
The intersection of the third row entitled as NRT" with the columns below the PSI-9056 rows, ACEP and VALUE shall display the corresponding information.
The fourth row shall display the non selective text PLT"
PSI-9057
The intersection of the fourth row entitled as PLT" with the columns below PSI-9058 the rows, AVERAGE, "99%" and MX shall display the corresponding information.
The third area shall be composed by the following elements in function of the PSI-6788 kind of radar: Statistics (Normal Radar) The first row shall display the non selective text ACEP, REJ, DESC, PSI-6755 FAILURE.
The second row shall display in its first column the non selective text DDE PSI-6789 followed by the non selective text Channel 1:. The next columns will give the information concerning to the rows in it intersection. The third row shall display in its second column the non selective text PSI-6790 Channel 2:. The next columns will give the information concerning to the rows in it intersection. Statistics (TMA Autonomous Radar) Software Requirements Specification 249
The first row shall display the non selective text ACEP, REJ, DESC.
PSI-6792
The second row shall display in its first column the non selective text UAST. PSI-6793 The next columns will give the information concerning to the rows to which intersect with the first row. Statistics (RUTA Autonomous Radar) The first row shall display the non selective text ACEP, REJ, DESC. PSI-6796
The second row shall display in its first column the non selective text UAST. PSI-6797 The next columns will give the information concerning to the rows to which intersect with the first row. The fourth area shall be composed by the following elements in function of PSI-6798 the kind of radar:
The first row shall display the non selective text Number of RHO THETA PSI-6804 Areas: followed by that data. Next it will be displayed Antenna Period:, followed by that data. The second row shall display the non selective text Rejected by PSI-6805 transmission or format: followed by that data. Next it will be displayed Plots Test:, followed by that data. The third row shall display the non selective text Monorradar tracks : PSI-6806 followed by that data. Next it will be displayed Meteo Plots:, followed by that data. The selective button Exit shall close the window. PSI-6807
4.1.10.1.12. TCPV Statistics This window shall display the following elements: 250 Last Reset Time FP pending FP coordinated FP controlled FP terminated FPL's received/correct received CPL's received/correct received CHG's received/correct received DEP's received/correct received Software Requirements Description PSI-5900
CNL's received/correct received DLA's received/correct received
This window shall only be an introduction and it will be updated each 5 PSI-5901 seconds.
The statistics shall be able to be reseted clicking on the "Reset" button with PSI-5902 the LB of the pointer device.
A reset of the statistics shall be performed with the date change.
PSI-5903
This window shall show since when the statistics are picked up.
PSI-5904
It shall be possible to operate in order to exit from it by clicking on the "Exit" PSI-5905 button with the LB of the pointer device .
4.1.10.1.13. TLPV Statistics This function shall consist of the following options: TLPV Statistics Adjacent Centres Statistics PSI-3211
TLPV Statistics Window This window shall display the Statistics of the following items according to PSI-3221 the TLPV subsystem: Time of the last reset Pending FP's Departure coord. FP's Arrival coord. FP's Active FP's Preactive FP's Terminated FP's Assigned Codes Retained Codes Non printed strips Created FP's in FDDs PSI-3322
This window shall only be an introduction and it will be updated for event.
251
PSI-3334
The statistics shall be able to be reseted clicking on the "Reset" button PSI-3323 with the LB of the pointer device, except the ones referred to assigned Codes, retained Codes and non printed Strips. It shall be possible to operate in order to exit from it by clicking on the PSI-3324 "Exit" button with the LB of the pointer device .
PSI-3327
It shall not display error messages.
PSI-3325
Adjacent Centres Statistics Window This window shall display the number of sent out, received and correctly PSI-3222 received ACT, ABI, MAC, PAC, REV and OCM messages (LAM has been generated) for each existing adjacent centre. This window shall only be an introduction and it will be updated each 5 PSI-3328 seconds.
PSI-3333
The statistics shall be able to be reseted clicking on the "Reset" button PSI-3329 with the LB of the pointer device.
It shall be possible to operate in order to exit from it by clicking on the PSI-3330 "Exit" button with the LB of the pointer device.
PSI-3331
PSI-3332
252
4.1.10.1.14. GIPV Statistics This window shall display the Statistics of the following elements: Time of the last reset For each external system, the number of application messages is displayed in columns, detailed per kind of message, sent to each external system Number of flight plans in GIPV. PSI-3214
The accumulative statistics shall be able to be reseted clicking on the "Reset" PSI-3353 button with the LB of the pointer device.
A reset of these statistics shall be performed with the date change.
PSI-3354
PSI-3355
4.1.10.1.15. GSI Statistics The statistics to be displayed taken from the ones depicted below shall be PSI-3212 able to be selected from this window.
An Execute button shall be available in order to give access to the different PSI-3337 statistics window which have been selected.
PSI-3342
253
Statistic Windows of Configured Groups: This window shall display the following Statistic items: Name of the group Number of accepted messages Number of filtered messages Number of files Size of the files in megabytes. Occupation percentage Number of accepted files PSI-3224
Statistics Window of FTP Files: This window shall display the following Statistic items: Number of received files Number of accepted files Number of filtered files Number of accepted files with a size bigger than the normal PSI-3226
Number of lost files due to the space in disc has been exceeded. This window shall only be an introduction and it will be updated for event. PSI-3344
Occupation Statistics Window: This window shall show the occupation of: User files split Compressed files split Operative Root partition Stand by Root partition Recording device tape PSI-3228
Statistics Window of FTP Sessions: This window shall display the number of opened instantaneous FTP PSI-3230 sessions and the number of accumulated FTP sessions.
254
PSI-3371
4.1.10.1.16. SIS Statistics In the SIS Statistics window the statistics for each of the following items will be visualized for each external user defined for the SIS: The following statistics shall be displayed: Time of the last reset. Number of sending tries performed in the last 60 minutes Tracks sent to each external system Sending period defined for each system. PSI-3210
PSI-3335
The statistics shall be able to be reseted clicking on the "Reset" button with PSI-3321 the LB of the pointer device.
PSI-3326
4.1.10.1.17. Printers Statistics This window shall display the failure Statistics of each printer of the system. PSI-3216
The counters of the Printers statistics shall be able to be reseted by clicking PSI-3387 with the LB of the pointer device on the "Reset" button which will set to zero the number of recorded failures.
255
This window shall only be an introduction and it will be updated each 5 PSI-3385 seconds
PSI-3386
It shall be possible to operate in order to exit from it by clicking on the "Exit" PSI-3395 button with the LB of the pointer device
4.1.10.1.18. TPVT Statistics The following statistic shall be displaying: Number of Normal PV Number of abbreviated PV Number of incoherent PV Number of Total PV PSI-5879
PSI-5881
4.1.10.1.19. SMR Radar Site Statistics This window shall be displayed after selecting a radar name from the PSI-4174 dropped-down menu, on selecting the option "SMR Radar Site Statistics", which has been displayed on selecting the function"Statistics" from the inferior functions bar. Statistics of the following items shall be displayed: Plots Filt. Plots/Process Filt.Plots/Time Filt. Plots/Quality PSI-4175
256
It shall be possible to operate in order to exit from it by clicking on the "Exit" PSI-4179 button with the LB of the pointer device.
PSI-4180
4.1.10.2.
PROCESSOR STATISTICS
Concerning the processor statistics (disk occupation): In a window will be displayed, the disk partitions and the percentage of occupation through the progress bar. Displaying information about the corresponding partition size and its occupation percentage. From this window the statistics to be displayed for each computer shall be PSI-3215 able to be selected from the ones depicted below: Devices Processes Internal Communications External Communications Disc occupation UDPF Protocol
This window shall allow to select the "Subsystem" and the "Processor" from PSI-3367 what we want to visualize the statistics.
The subsystem and the processor shall be displayed as dropp-down menus
PSI-3368
An "Execute" button shall be available which will give access to the different PSI-3363 statistics window which have been selected.
PSI-3365
4.1.10.2.1. Statistic Window of Devices This window shall show the number of controlled failures of the selected PSI-3232 processor devices. Software Requirements Specification 257
PSI-3377
4.1.10.2.2. Process Statistics Window This window shall display the statistics according to the occupation and PSI-3234 failures of the processes for the selected processor.
The occupation information shall be displayed in bars way, with the following PSI-3374 codes: Instantaneous (green bar) Average (yellow bar)
Peak (black line) except for the element "% Occupation" for which will only display the instantaneous occupation. It shall be possible to operate for: Visualizing a process information. In order to visualize this information we must locate the indicator of the pointer device on the area prepared for this process and click on the right button of it. A window with the information referred to the process (Process name, N of Recovering Rest, Current/Average/Peak CPU, and time Passed since the last reset of the aforementioned process) shall be displayed. The number of crashes of the processor since the last reset. PSI-3376 PSI-3375
PSI-3372
4.1.10.2.3. Internal Communication Statistics Window This window shall display the internal communications statistics of the PSI-3236 selected processor, referred to each LAN according to: 258 Received Messages Received error Messages Transferred Messages Software Requirements Description
Failures
PSI-3379
4.1.10.2.4. External Communication Statistics Window This window shall display the external communications statistics of the PSI-3238 selected processor, (only for TCPV, TLPV, UAST and UDDE) according to the centres: Received Messages Received error Messages Transferred Messages Impossibility of communication Failures
PSI-3382
4.1.10.2.5. Disc occupation window This window shall display the disc occupation statistics of the assembled PSI-3240 partitions, indicating in each of them the following details: Name of the partition Size of it in Megabytes Percentage of occupation in numeric mode Percentage of occupation through bars diagram
PSI-3384
259
4.1.10.2.6. UDPF Protocol Screen With the aim of detect a possible situation of degradation of the link a new PSI-5875 PSI function is defined, which shall allow to display statistics data associated to the protocol: For every UDPR session it shall be indicated: Emission or Outgoing Stream: - Number of NACK's received since last reset. - Number of resent messages since last reset. - Number of NODATA sent messages since last reset. Reception or Incoming Stream: - Number of NACK's sent since last reset - Number of lost messages ( no possible recuperation) since last reset - Average transmission time (in milliseconds) to the received messages in the last 5 seconds ( refresh period of the statistics) ( For the average transmission time of the received messages the processors UDPFEmisor and UDPFReceptor are considered always synchronized, it means, it will not be necessary to verify the state of synchronization in the same (it will be included in next versions of the systems)) PSI-5876
Button 'Reset' and 'Close'. Clicking the BI of the pointer device the button PSI-5877 'Reset' shall run a reset over all the accumulative statistics associates to the window.
4.1.11. CONTROL & MONITORING PSI shall comply with the applicable requirements of MwCM and MwCOM PSI-9171 facilities for the integration in the SACTA System.
4.1.12. TEXTS FOR LETTERING AND MESSAGES 4.1.12.1. EVENT REPORTS A#12845
The following table contains the Variable Text of the ERs, generated by PSI, PSI-9062 that shall be displayed in the PSI: Code PSIaso001 Extended Text Versin Sistema = (Vers_Sistema) Parches Sistema = [Vaco / Parches_Sistema] Versin Adaptacin = (Vers_Adap)
260
Local = [Si / No] Central = [Si / No] PSIaso003 PSIaso005 PSIaso007 PSIaso009 PSIaso011 (Identif_Proc) Arranque en vacio / Arranque con Datos en disco / Arranque con PVs conservados (Identif_Proc) (Identif_tandem) Arranque en vaco / Arranque con Datos en disco /Arranque con PVs conservados (Identif_Proc) (Identif_Proc) * Donde Identif_Proc ser el nombre grfico del ltimo o nico procesador del mensaje. Del procesador (Identif_Proc) por (CAUSA_ABORTO_ARRANQUE) (Identif_Proc) Accin realizada sobre el AE: AEs [MODIFICADA / CREADA / BORRADA] Identificacin del AE: AE: [Identificador] [DIA] Tipo de AE: Tipo: [Dinmica / Esttica] Configuracin AEP: AEP: SI / NO Configuracin AC: AC: SI / NO Altitud: ALTITUD: [N Inf., N. Sup] Intervalos de Actividad, Intervalos de Suspensin : oIA1: [HH:MM-HH:MM], IS1 1: [HH:MM-HH:MM], IS1 2: [HH:MM-HH:MM, IS [HH:MM-HH:MM], IS1 4: [HH:MM-HH:MM], IS1 5: [HH:MM-HH:MM] oIA2: [HH:MM-HH:MM], IS2 1: [HH:MM-HH:MM], IS2 2: [HH:MM-HH:MM], IS [HH:MM-HH:MM], IS2 4: [HH:MM-HH:MM], IS2 5: [HH:MM-HH:MM] PSIcen001 PSIcen002 PSIcev001 (Elemento) pasa de (estado inicial) a conectado (Elemento) pasa de (estado inicial) a no conectado Texto_extendido_1: SICV_MET: [Si /No] SICV_AIS: [Si /No] Texto_extendido_2: ATIS_1: [Si /No] ATIS_2: [Si /No] ... ATIS_N: [Si /No] Texto_extendido_3: SMI_1: [Si /No] SMI_2: [Si /No] SMI_N: [Si /No] PSIcor001 (Identif_Ord) pasa a estado Disponible (Identif_Ord) pasa a estado No Disponible 261
PSIaso012 PSIaso013 PSIcae001
...
PSIcor002 PSIcpa001
(Identif_Ord) pasa a estado Fallo POR [Perfil]AERODROMO : (Identif_Aerodromo) PISTA DESPEGUE 1: (Identif_Pista) PISTA DESPEGUE 2: (Identif_Pista) (Identif_Pista) PISTA ARRIBADA 2: (Identif_Pista) VUELOS AFECTADOS POR PISTA DESPEGUE 1: (Vuelos Afectados 1) VUELOS AFECTADOS POR PISTA DESPEGUE 2: (Vuelos Afectados 2) Este RH no tiene texto entendido Local = [Si/No] Central = [Si/No] Con Parada de TODAS las UCS/Posiciones / Sin Parada de Posiciones Sectorizadas / Sin Parada de SS/Posiciones (Identif_Proc) (Identif_Proc) (Identif_Proc) (Identif_Tandem) (Identif_Proc) POR [GLOBAL / ...] AERDROMO: [Cdigo OACI del aerdromo] QNH: [Valor configurado de QNH] QNH Anterior: [Valor de QNH anterior a la configuracin desde PSI] Estado QNH Anterior: [Estado del valor de QNH anterior a la configuracin desde PSI] Fuente QNH Anterior: [Fuente del valor de QNH anterior a la configuracin desde PSI] Paso a Separacin Radar Degradada. ( y Nombre de la Dependencia) No aplicable Separacin Radar. (y Nombre de la Dependencia) Recuperacin de Separacin Radar Nominal. ( y Nombre de la Dependencia) (Lista de sectores que pierden la DCT) (Lista de sectores que recuperan DTC) Doble Cobertura Radar No garantizada en sectores: (Lista de TODOS los sectores que continan sin DTC) Doble Cobertura Radar No garantizada en sectores: (Lista de TODOS los sectores que continan sin DTC ) (Lista de sectores que pierden TC) (Lista de sectores que recuperan TC) Cobertura Radar No garantizada en sectores: (Lista de TODOS los sectores que continan sin TC) Software Requirements Description
PISTA
ARRIBADA
1:
PSIgfi001 PSIoff001
PSIoff003 PSIoff005 PSIoff007 PSIoff009 PSIoff011 PSIqnh001
PSIrad003 PSIrad004 PSIrad005 PSIrad006 PSIrad007
PSIrad008 PSIrad009 PSIrad010
262
PSIrad011 PSIrad012
No extended Text No extended Text
The following table contains the Variable Text of the ERs, generated by PST, PSI-9063 that shall be displayed in the PST: Code SSTaso001 Text Versin Sistema = (Vers_Sistema) Parches Sistema = [Vaco / Parches_Sistema] Versin Adaptacin = (Vers_Adap) Local = [Si / No] Central = [Si / No] (Identif_Proc) Arranque en vacio / Arranque con Datos en disco / Arranque con PVs conservados (Identif_Proc) (Identif_tandem) Arranque en vaco / Arranque con Datos en disco /Arranque con PV's conservados (Identif_Proc) (Identif_Proc) * Donde Identif_Proc ser el nombre grfico del ltimo o nico procesador del mensaje. Del procesador (Identif_Proc) por (CAUSA_ABORTO_ARRANQUE) (Identif_Proc) (Elemento) pasa de (estado inicial) a conectado (Elemento) pasa de (estado inicial) a no conectado "Configuracin funcin DMAN" [Informar de los valores actuales] (Grupo SACTA) (Dependencia SACTA) (Nombre) TWR01 : (ORS Configurado) TWR02 : (ORs Configurado) TWR03 : (ORs Configurado) TWR04 : (ORs Configurado) .... TWR05 : (ORs Configurado) (Identif_Ord) pasa a (siguiente) estado (Identif_Ord) pasa a (siguiente) estado POR [Perfil]AERODROMO : (Identif_Aerodromo) PISTA DESPEGUE 1: (Identif_Pista) 263
SSTaso003 SSTaso005 SSTaso007 SSTaso009 SSTaso011
SSTaso012 SSTaso013 SSTcen001 SSTcen002 SSTcfd001 SSTcfs001 SSTcop001
SSTcor001 SSTcor002 SSTcpa001
PISTA DESPEGUE 2: (Identif_Pista) PISTA ARRIBADA 1: (Identif_Pista) PISTA ARRIBADA 2: (Identif_Pista) VUELOS AFECTADOS POR PISTA DESPEGUE 1: (Vuelos Afectados 1) VUELOS AFECTADOS POR PISTA DESPEGUE 2: (Vuelos Afectados 2) SSTgfi001 SSToff001 Este RH no tiene texto entendido Local = [Si/No] Central = [Si/No] Con Parada de TODAS las SS/Posiciones / Sin Parada de Posiciones Sectorizadas / Sin Parada de SS/Posiciones (Identif_Proc) (Identif_Proc) (Identif_Proc) (Identif_Tandem) (Identif_Proc) Paso a Separacin Radar Degradada. ( y Nombre de la Dependencia) No aplicable Separacin Radar. Dependencia) (y Nombre de la
SSToff003 SSToff005 SSToff007 SSToff009 SSToff011 SSTrad003 SSTrad004 SSTrad005 SSTscv001
Recuperacin de Separacin Radar Nominal. Nombre de la Dependencia) [SCV1] / [SCV2] / [SCV3] / [SCV4] / [SCV5]
4.2. OPERATIVE REQUIREMENTS As the PSI is mainly an operative component, most of its requirements could be considered inside this category. However, likewise they are functional requirements. That is to say, the distinction and classification of the requirements between operative and functional, for a component like the PSI is very doubtful. Because of that, all the requirements have been included in the Functional Requirements section, leaving this Operative Requirements section without any content. 4.3. INTERFACE REQUIREMENTS The PSI interface requirements are described according to the conventions described in the SARAD document.
264
4.3.1.
PUBLISHED EVENTS
4.3.1.1. EvtPsi_RequestTlpvActiveRunways Event to determine the active runway. The event shall contain the following information: Aerodrome name PSI-7172
The even will be consumed by: TLPV
4.3.1.2. EvtPsi_EnRouteRadarSeparation Event with the radar separation information in en-route dependencies. The event shall contain the following information: Indicator of ACC adapted to provided Reduced Separation (Yes/No) PSI-9132 A#12845
Old state of Radar Separation (Enroute) element (Nominal, Degraded, Failure) Old state of CT (Available, Not Available) Old State of DTC (Availbale, Not Available)
New State of Radar Separation (Enroute) element (Nominal, Degraded, Failure) New state of CT (Available, Not Available) New State of DTC (Availbale, Not Available)
The even will be consumed by: MwREC
4.3.1.3. EvtPsi_ConfigChangeRecording Event with the configuration changes information. The event shall contain the following information for each configuration PSI-9159 change: Old Configuration information. New Configuration information.
The even will be consumed by: MwREC
265
4.3.2.
CONSUMED EVENTS
4.3.2.1. Consumed from CWP 4.3.2.1.1. EvtCwp_EfssSorting PSI-7502
The PSI shall consume the EFSs Sorting CWP event EvtCwp_EfssSorting.
4.3.2.1.2.
EvtCwp_StartLoadEfssSorting
The PSI shall consume the Start of Load of EFSs Sorting event PSI-6361 EvtCwp_StartLoadEfssSorting.
4.3.2.1.3.
EvtCwp_EndLoadEfssSorting
The PSI shall consume the End of Load of EFSs Sorting event PSI-6362 EvtCwp_EndLoadEfssSorting.
4.3.2.2. Consumed from DDVE 4.3.2.2.1. EvtDdve_ServicesConfState PSI-7557
The PSI shall consume the event EvtDdve_ServicesConfState.
4.3.2.2.2.
EvtDdve_ServicesConfChangeAnalysisReply the event PSI-7559
The PSI shall consume EvtDdve_ServicesConfChangeAnalysisReply.
4.3.2.3. Consumed from GIPV 4.3.2.3.1. EvtGipv_DeliveryConfigurationUpdating
The PSI shall consume the event EvtGipv_DeliveryConfigurationUpdating. PSI-7584
4.3.2.3.2.
EvtGipv_ExternalSystemConfigurationUpdating the event PSI-7607
The PSI shall consume EvtGipv_ExternalSystemConfigurationUpdating. 266
4.3.2.3.3.
EvtGipv_ExternalSystemFilterUpdating PSI-7608
The PSI shall consume the event EvtGipv_ExternalSystemFilterUpdating.
4.3.2.3.4.
EvtGipv_ExternalSystemFormatUpdating the event PSI-7609
The PSI shall consume EvtGipv_ExternalSystemFormatUpdating.
4.3.2.3.5.
EvtGipv_ExternalSystemMessageUpdating the event PSI-7610
The PSI shall consume EvtGipv_ExternalSystemMessageUpdating.
4.3.2.3.6.
EvtGipv_ExternalSystemFilterRouteUpdating the event PSI-7611
The PSI shall consume EvtGipv_ExternalSystemFilterRouteUpdating.
4.3.2.3.7.
EvtGipv_ExternalSystemStateUpdating PSI-7612
The PSI shall consume the event EvtGipv_ExternalSystemStateUpdating.
4.3.2.3.8.
EvtGipv_PsiLoadingStart PSI-7613
The PSI shall consume the event EvtGipv_PsiLoadingStart.
4.3.2.3.9.
EvtGipv_PsiLoadingEnd PSI-7614
The PSI shall consume the event EvtGipv_PsiLoadingEnd.
267
4.3.2.4. Consumed from MwALNK 4.3.2.4.1. EvtMwALNK_State PSI-8327
The PSI shall consume the event EvtMwALNK_State.
4.3.2.5. Consumed from MwCM 4.3.2.5.1. EvtMwCM_FMSStateNotification PSI-7942
The PSI shall consume the event EvtMwCM_FMSStateNotification.
4.3.2.5.2.
EvtMwCM_FMSPresence PSI-7944
The PSI shall consume the event EvtMwCM_FMSPresence .
4.3.2.5.3.
EvtMwCM_HWInformation PSI-7972
The PSI shall consume the event EvtMwCM_HWHwInformation.
4.3.2.5.4.
EvtMwCM_HWChange PSI-7975
The PSI shall consume the event EvtMwCM_HWHwChange.
Where Hw is the HW component whose state information is included in this event. 4.3.2.5.5. EvtMwCM_HWCLANState PSI-7980
The PSI shall consume the event EvtMwCM_HWCLANState.
4.3.2.5.6.
EvtMwCM_HWPIVLSesInformation PSI-7982
The PSI shall consume the event EvtMwCM_HWPIVLSesInformation.
268
4.3.2.5.7.
EvtMwCM_SWShut-downWarning PSI-7953
The PSI shall consume the event EvtMwCM_SWShut-downWarning.
4.3.2.5.8.
EvtMwCM_HWPresence PSI-7946
The PSI shall consume the event EvtMwCM_HWPresence.
4.3.2.5.9.
EvtMwCM_ConfigurationRPLsChange PSI-8148
The PSI shall consume the event EvtMwCM_ConfigurationRPLsChange.
4.3.2.5.10. EvtMwCM_RoleUpdate The PSI shall consume the event EvtMwCM_RoleUpdate. PSI-8149
4.3.2.5.11. EvtMwCM_DAMUpdate The PSI shall consume the event EvtMwCM_DAMUpdate. PSI-8150
4.3.2.5.12. EvtMwCM_HWChangeRecord The PSI shall consume the event EvtMwCM_HWChangeRecord. PSI-8369
4.3.2.6. Consumed from MwDC 4.3.2.6.1. EvtMwDist_SSDSessionStateUpdate PSI-8252
The PSI shall consume the event EvtMwDist_SSDSessionStateUpdate.
4.3.2.6.2.
EvtMwDist_CamerasAssignmentUpdate PSI-8254
The PSI shall consume the event EvtMwDist_CamerasAssignmentUpdate.
269
4.3.2.6.3.
EvtMwDist_BlockOrStateUpdate PSI-8255
The PSI shall consume the event EvtMwDist_BlockOrStateUpdate.
4.3.2.6.4.
EvtMwDist_TPVFuncConfigUpdate PSI-7704
The PSI shall consume the event EvtMwDist_TPVFuncConfigUpdate.
4.3.2.6.5.
EvtMwDist_AccessCodeUpdate PSI-7755
The PSI shall consume the event EvtMwDist_AccessCodeUpdate.
4.3.2.6.6.
EvtMwDist_StoredSectUpdate PSI-8244
The PSI shall consume the event EvtMwDist_StoredSectUpdate.
4.3.2.6.7.
EvtMwDist_NovaSMRConfigUpdate PSI-8245
The PSI shall consume the event EvtMwDist_NovaSMRConfigUpdate.
4.3.2.6.8.
EvtMwDist_AsterixCat10SensorsConfigUpdate the event PSI-8246
The PSI shall consume EvtMwDist_AsterixCat10SensorsConfigUpdate.
4.3.2.6.9.
EvtMwDist_SNETSFuncConfigUpdate PSI-8247
The PSI shall consume the event EvtMwDist_SNETSFuncConfigUpdate.
4.3.2.6.10. EvtMwDist_TCPV_TLPVLinkConfigUpdate The PSI shall consume EvtMwDist_TCPV_TLPVLinkConfigUpdate. 270 the event PSI-8249
4.3.2.6.11. EvtMwDist_TLPVtowerLinkConfigUpdate The PSI shall consume EvtMwDist_TLPVtowerLinkConfigUpdate. the event PSI-8250
4.3.2.6.12. EvtMwDist_RemoteTDVMLinkConfigUpdate The PSI shall consume EvtMwDist_RemoteTDVMLinkConfigUpdate. the event PSI-8251
4.3.2.6.13. EvtMwDist_AdjacentCentresConfigUpdate The PSI shall consume EvtMwDist_AdjacentCentresConfigUpdate. the event PSI-7692
4.3.2.6.14. EvtMwDist_AFTNMessageSendingConfigUpdate The PSI shall consume EvtMwDist_AFTNMessageSendingConfigUpdate. the event PSI-7693
4.3.2.6.15. EvtMwDist_AFTNLinesConfigUpdate The PSI shall consume the event EvtMwDist_AFTNLinesConfigUpdate. PSI-7694
4.3.2.6.16. EvtMwDist_ATISLinkConfigUpdate The PSI shall consume the event EvtMwDist_ATISLinkConfigUpdate. PSI-7695
4.3.2.6.17. EvtMwDist_OperationalConfigUpdate The PSI shall consume the event EvtMwDist_OperationalConfigUpdate. PSI-7696
4.3.2.6.18. EvtMwDist_RadarProcConfigUpdate The PSI shall consume the event EvtMwDist_RadarProcConfigUpdate. PSI-7697
271
4.3.2.6.19. EvtMwDist_RadarInputStateUpdate The PSI shall consume the event EvtMwDist_RadarInputStateUpdate. PSI-7698
4.3.2.6.20. EvtMwDist_SectorisationUpdate The PSI shall consume the event EvtMwDist_SectorisationUpdate. PSI-7699
4.3.2.6.21. EvtMwDist_IcaroLinkConfigUpdate The PSI shall consume the event EvtMwDist_IcaroLinkConfigUpdate. PSI-7700
4.3.2.6.22. EvtMwDist_SMILinkConfigUpdate The PSI shall consume the event EvtMwDist_SMILinkConfigUpdate. PSI-7701
4.3.2.6.23. EvtMwDist_TDVMProcessingConfigUpdate The PSI shall consume EvtMwDist_TDVMProcessingConfigUpdate. the event PSI-7703
4.3.2.6.24. EvtMwDist_MtcdConfigUpdate The PSI shall consume the event EvtMwDist_MtcdConfigUpdate. PSI-9167
4.3.2.7. Consumed from MwER 4.3.2.7.1. EvtMwER_SendingToPSI PSI-8290
The PSI shall consume the event EvtMwER_SendingToPSI.
272
4.3.2.8. Consumed from MwRec 4.3.2.8.1. EvtMwRec_FileClosed PSI-8349
The PSI shall consume the event EvtMwRec_FileClosed.
4.3.2.8.2.
EvtMwRec_RecoveryInUse PSI-8350
The PSI shall consume the event EvtMwRec_RecoveryInUse.
4.3.2.8.3.
EvtMwRec_NewTape PSI-8351
The PSI shall consume the event EvtMwRec_NewTape.
4.3.2.8.4.
EvtMwRec_TapeAccessErrorInfo PSI-8352
The PSI shall consume the event EvtMwRec_TapeAccessErrorInfo.
4.3.2.8.5.
EvtMwRec_WrongTapeInfo PSI-8353
The PSI shall consume the event EvtMwRec_WrongTapeInfo.
4.3.2.8.6.
EvtMwRec_EndERQuery PSI-8354
The PSI shall consume the event EvtMwRec_EndERQuery.
4.3.2.9. Consumed from MwStat 4.3.2.9.1. EvtMwStat_StatisticsSILV PSI-8081
The PSI shall consume the event EvtMwStat_StatisticsSILV.
273
4.3.2.9.2.
EvtMwStat_StatisticsATIS-SMI PSI-8082
The PSI shall consume the event EvtMwStat_StatisticsATIS-SMI.
4.3.2.9.3.
EvtMwStat_StatisticsAMAN PSI-8083
The PSI shall consume the event EvtMwStat_StatisticsAMAN.
4.3.2.9.4.
EvtMwStat_StatisticsMTCD PSI-8084
The PSI shall consume the event EvtMwStat_StatisticsMTCD.
4.3.2.9.5.
EvtMwStat_StatisticsTPVT PSI-7993
The PSI shall consume the event EvtMwStat_StatisticsTPVT.
4.3.2.9.6.
EvtMwStat_StatisticsNormalTDVM PSI-7994
The PSI shall consume the event EvtMwStat_StatisticsNormalTDVM.
4.3.2.9.7.
EvtMwStat_StatisticsAutonomousTDVM
The PSI shall consume the event EvtMwStat_StatisticsAutonomousTDVM. PSI-7996
4.3.2.9.8.
EvtMwStat_StatisticsGSIGroups PSI-8073
The PSI shall consume the event EvtMwStat_StatisticsGSIGroups.
4.3.2.9.9.
EvtMwStat_StatisticsGSIFTPFiles PSI-8074
The PSI shall consume the event EvtMwStat_StatisticsGSIFTPFiles.
274
4.3.2.9.10. EvtMwStat_StatisticsGSIUsage The PSI shall consume the event EvtMwStat_StatisticsGSIUsage. PSI-8075
4.3.2.9.11. EvtMwStat_StatisticsGSIFTPSess The PSI shall consume the event EvtMwStat_StatisticsGSIFTPSess. PSI-8076
4.3.2.9.12. EvtMwStat_StatisticsPrinters The PSI shall consume the event EvtMwStat_StatisticsPrinters. PSI-7708
4.3.2.9.13. EvtMwStat_StatisticsSurfaceDelays The PSI shall consume the event EvtMwStat_StatisticsSurfaceDelays. PSI-8077
4.3.2.9.14. EvtMwStat_StatisticsSurfaceSensor The PSI shall consume the event EvtMwStat_StatisticsSurfaceSensor. PSI-8078
4.3.2.9.15. EvtMwStat_StatisticsAirDelays The PSI shall consume the event EvtMwStat_StatisticsAirDelays. PSI-7705
4.3.2.9.16. EvtMwStat_StatisticsSystematicErrorsCalculation The PSI shall consume EvtMwStat_StatisticsSystematicErrorsCalculation. the event PSI-8079
4.3.2.9.17. EvtMwStat_StatisticsRadarTCAMS The PSI shall consume the event EvtMwStat_StatisticsRadarTCAMS. PSI-8080
275
4.3.2.9.18. EvtMwStat_StatisticsProcDev The PSI shall consume the event EvtMwStat_StatisticsProcDev. PSI-7709
4.3.2.9.19. EvtMwStat_StatisticsProcDiskUsage The PSI shall consume the event EvtMwStat_StatisticsProcDiskUsage. PSI-7710
4.3.2.9.20. EvtMwStat_StatisticsProcExtCom The PSI shall consume the event EvtMwStat_StatisticsProcExtCom. PSI-7711
4.3.2.9.21. EvtMwStat_StatisticsProcIntCom The PSI shall consume the event EvtMwStat_StatisticsProcIntCom. PSI-7712
4.3.2.9.22. EvtMwStat_StatisticsProcProc The PSI shall consume the event EvtMwStat_StatisticsProcProc. PSI-7717
4.3.2.9.23. EvtMwStat_StatisticsProcS-RUDP The PSI shall consume the event EvtMwStat_StatisticsProcS-RUDP. PSI-8071
4.3.2.9.24. EvtMwStat_StatisticsEADR The PSI shall consume the event EvtMwStat_StatisticsEADR. PSI-7706
4.3.2.9.25. EvtMwStat_StatisticsSIS The PSI shall consume the event EvtMwStat_StatisticsSIS. PSI-8072
276
4.3.2.9.26. EvtMwStat_StatisticsTCPV The PSI shall consume the event EvtMwStat_StatisticsTCPV. PSI-7716
4.3.2.9.27. EvtMwStat_StatisticsTLPV The PSI shall consume the event EvtMwStat_StatisticsTLPV. PSI-7715
4.3.2.9.28. EvtMwStat_StatisticsGIPV The PSI shall consume the event EvtMwStat_StatisticsGIPV. PSI-7707
4.3.2.9.29. EvtMwStat_StatisticsTDVT The PSI shall consume the event EvtMwStat_StatisticsTDVT. PSI-7992
4.3.2.10.
Consumed from SDA
4.3.2.10.1. EvtSda_SurfaceSensorElementStatus The PSI shall consume the event EvtSda_SurfaceSensorElementStatus. PSI-7575
4.3.2.10.2. EvtSda_SurfaceSensorSynchro The PSI shall consume the event EvtSda_SurfaceSensorSynchro. PSI-7577
4.3.2.10.3. EvtSda_AirRadarSynchro The PSI shall consume the event EvtSda_AirRadarSynchro. PSI-9103
4.3.2.10.4. EvtSda_UddeRadarLinesStatus The PSI shall consume the event EvtSda_UddeRadarLinesStatus. PSI-9105
277
4.3.2.10.5. EvtSda_UddeOperativeStandbyState The PSI shall consume the event EvtSda_UddeOperativeStandbyState. PSI-9107
4.3.2.10.6. EvtSda_AirRadarElementStatus The PSI shall consume the event EvtSda_AirRadarElementStatus. PSI-9120
4.3.2.11.
Consumed from SURV-A
4.3.2.11.1. EvtSurvA_RadarQualityStateElements The PSI shall consume the event EvtSurvA_RadarQualityStateElements. PSI-7579
4.3.2.11.2. EvtSurvA_RadarStatus The PSI shall consume the event EvtSurvA_RadarStatus. PSI-7581
4.3.2.12.
Consumed from SURV-S
4.3.2.12.1. EvtSurvS_RadarState The PSI shall consume the event EvtSurvS_RadarState. PSI-9110
4.3.2.12.2. EvtSurvS_SurfaceSensorElementState The PSI shall consume the event EvtSurvS_SurfaceSensorElementState. PSI-9112
4.3.2.13.
Consumed from TILAIS
4.3.2.13.1. EvtTilais_SpecialDeterminedAreaInformation The PSI shall consume the Start an Special Determined Area Information PSI-7547 Load event EvtTilais_SpecialDeterminedAreaInformation. 278 Software Requirements Description
4.3.2.13.2. EvtTilais_AllSpecialAreasList The PSI shall consume the End All Special Areas List Load event PSI-7550 EvtTilais_AllSpecialAreasList.
4.3.2.14.
Consumed from TILMET
4.3.2.14.1. EvtTilmet_QnhInformation The PSI shall consume EvtTilmet_QnhInformation. the periodic QNH information event PSI-7552
4.3.2.15.
Consumed from TIMDT
4.3.2.15.1. EvtTilmet*_QnhInformation The PSI shall consume EvtTilmet*_QnhInformation. the periodic QNH information event PSI-9118
4.3.2.16.
Consumed from TLPV
4.3.2.16.1. EvtTlpv_ActiveRunwaysInformation The PSI shall consume the event EvtTlpv_ActiveRunwaysInformation. PSI-7624
4.3.3. N/A 4.3.4.
PROVIDED SERVICES
USED SERVICES
4.3.4.1. Used from AMAN 4.3.4.1.1. SrvAman_RulesForOptimumRunwayCalculationModification
The PSI shall use the Rules for Optimum Runway Calculation Modification PSI-7519 service SrvAman_OptimumLandingRunwayCalculation.
279
4.3.4.1.2.
SrvAman_TSPModification PSI-7520
The PSI shall use the TSP Modification service SrvAman_TSPModification.
4.3.4.1.3.
SrvAman_TSPsRequest PSI-7525
The PSI shall use the TSPs Request service SrvAman_TSPsRequest.
4.3.4.2. Used from CWP 4.3.4.2.1. SrvCwp_LoadEfssSorting
The PSI shall use the Load EFSs Sorting service SrvCwp_LoadEfssSorting. PSI-6359
The answer to this service consists of: Start of Load of EFSs Sorting event (EvtCwp_StartLoadEfssSorting) EFSs Sorting events (EvtCwp_EfssSorting) End of Load of EFSs Sorting (EvtCwp_EndLoadEfssSorting)
4.3.4.3. Used from DDVE 4.3.4.3.1. SrvDdve_ServicesConfStateRequest
The PSI shall use the Services Configuration State Request service PSI-7565 SrvDdve_ServicesConfStateRequest.
4.3.4.3.2.
SrvDdve_ServicesConfChangeAnalysis
The PSI shall use the Services Configuration Change/Analysis service PSI-7563 SrvDdve_ServicesConfChangeAnalysis.
4.3.4.4. Used from DMAN 4.3.4.4.1. SrvDman_ModifyDeparturesHourRatio PSI-8292
The PSI shall use the service SrvDman_ModifyDeparturesHourRatio.
280
4.3.4.5. Used from FAST 4.3.4.5.1. SrvFast_FlightStripsAdvanceGeneration PSI-7582
The PSI shall use the service SrvFast_FlightStripsAdvanceGeneration.
4.3.4.6. Used from GIPV 4.3.4.6.1. SrvGipv_DeliveryConfigurationEdition PSI-7600
The PSI shall use the service SrvGipv_DeliveryConfigurationEdition.
4.3.4.6.2.
SrvGipv_ExternalSystemConfigurationEdition the service PSI-7601
The PSI shall use SrvGipv_ExternalSystemConfigurationEdition.
4.3.4.6.3.
SrvGipv_ExternalSystemFilterEdition PSI-7602
The PSI shall use the service SrvGipv_ExternalSystemFilterEdition.
4.3.4.6.4.
SrvGipv_ExternalSystemFormatEdition PSI-7603
The PSI shall use the service SrvGipv_ExternalSystemFormatEdition.
4.3.4.6.5.
SrvGipv_ExternalSystemMessageEdition PSI-7604
The PSI shall use the service SrvGipv_ExternalSystemMessageEdition.
4.3.4.6.6.
SrvGipv_ExternalSystemFilterRouteEdition PSI-7605
The PSI shall use the service SrvGipv_ExternalSystemFilterRouteEdition.
281
4.3.4.6.7.
SrvGipv_ExternalSystemStateEdition PSI-7606
The PSI shall use the service SrvGipv_ExternalSystemStateEdition.
4.3.4.6.8.
SrvGipv_PsiLoad PSI-8366
The PSI shall use the service SrvGipv_PsiLoad.
4.3.4.7. Used from MwALNK 4.3.4.7.1. SrvMwALNK_StateSubscribe PSI-8324
The PSI shall use the service SrvMwALNK_StateSubscribe.
4.3.4.8. Used from MwCM 4.3.4.8.1. SrvMwCM_ConfigurationGetErProfileParam
The PSI shall use the service SrvMwCM_ConfigurationGetErProfileParam PSI-9179 to specify whether an ER is displayed at PSI in a profile or not.
4.3.4.8.2.
SrvMwCM_ConfigurationGetLocalEnvironmentParam service PSI-9181 specify the A#19914
The PSI shall use the SrvMwCM_ConfigurationGetLocalEnvironmentParam to parameters of the local environment.
4.3.4.8.3.
SrvMwCM_ConfigurationGetGraphicPrinterParam
The PSI shall use the service PSI-9183 SrvMwCM_ConfigurationGetGraphicPrinterParam to specify what physical printers are associated to the logical ones.
4.3.4.8.4.
SrvMwCM_ConfigurationGetCorrelationParam the service PSI-8190
The PSI shall use SrvMwCM_ConfigurationGetCorrelationParam.
282
4.3.4.8.5.
SrvMwCM_ConfigurationGetCentreVersionParam the service PSI-8191
The PSI shall use SrvMwCM_ConfigurationGetCentreVersionParam.
4.3.4.8.6.
SrvMwCM_ConfigurationGetSystemIdentParam the service PSI-8192
The PSI shall use SrvMwCM_ConfigurationGetSystemIdentParam.
4.3.4.8.7.
SrvMwCM_ConfigurationGetServerParam PSI-8193
The PSI shall use the service SrvMwCM_ConfigurationGetServerParam.
4.3.4.8.8.
SrvMwCM_ConfigurationGetUastIntParam PSI-8194
The PSI shall use the service SrvMwCM_ConfigurationGetUastIntParam.
4.3.4.8.9.
SrvMwCM_ConfigurationGetUastSurvParam
The PSI shall use the service SrvMwCM_ConfigurationGetUastSurvParam. PSI-8195
4.3.4.8.10. SrvMwCM_ConfigurationGetCat10AsterixSensorsParam The PSI shall use the SrvMwCM_ConfigurationGetCat10AsterixSensorsParam. service PSI-8196
4.3.4.8.11. SrvMwCM_ConfigurationGetInstCat10AsterixSensorsParam The PSI shall use the SrvMwCM_ConfigurationGetInstCat10AsterixSensorsParam. service PSI-8197
4.3.4.8.12. SrvMwCM_ConfigurationGetNTZAlertsParam The PSI shall use SrvMwCM_ConfigurationGetNTZAlertsParam. the service PSI-8199
283
4.3.4.8.13. SrvMwCM_ConfigurationGetRPLsOFFVersion The PSI shall use SrvMwCM_ConfigurationGetRPLsOFFVersion. the service PSI-8178
4.3.4.8.14. SrvMwCM_ConfigurationChangeRPL The PSI shall use the service SrvMwCM_ConfigurationChangeRPL. PSI-8179
4.3.4.8.15. SrvMwCM_ChangeRole The PSI shall use the service SrvMwCM_ChangeRole. PSI-8180
4.3.4.8.16. SrvMwCM_LoadRole The PSI shall use the service SrvMwCM_LoadRole. PSI-8181
4.3.4.8.17. SrvMwCM_GetDAM The PSI shall use the service SrvMwCM_GetDAM. PSI-8182
4.3.4.8.18. SrvMwCM_ConfigurationGetPOSParam The PSI shall use the service SrvMwCM_ConfigurationGetPOSParam. PSI-8186
4.3.4.8.19. SrvMwCM_ConfigurationGetAMANParam The PSI shall use the service SrvMwCM_ConfigurationGetAMANParam. PSI-8187 A#19477
4.3.4.8.20. SrvMwCM_ConfigurationGetDMANParam The PSI shall use the service SrvMwCM_ConfigurationGetDMANParam. PSI-8188
284
4.3.4.8.21. SrvMwCM_ConfigurationGetMTCDParam The PSI shall use the service SrvMwCM_ConfigurationGetMTCDParam. PSI-8189
4.3.4.8.22. SrvMwCM_SWMarkStart The PSI shall use the service SrvMwCM_SWMarkStart. PSI-7955
4.3.4.8.23. SrvMwCM_SWReportPresence The PSI shall use the service SrvMwCM_SWReportPresence. PSI-7957
4.3.4.8.24. SrvMwCM_SWGetStart-upDataInDiskState The PSI shall use the service SrvMwCM_SWGetStart-upDataInDiskState. PSI-7959
4.3.4.8.25. SrvMwCM_SWGetStart-upStoredFPState The PSI shall use the service SrvMwCM_SWGetStart-upStoredFPState. PSI-7961
4.3.4.8.26. SrvMwCM_HWGetId The PSI shall use the service SrvMwCM_HWGetId. PSI-7963
4.3.4.8.27. SrvMwCM_HWModifyState The PSI shall use the service SrvMwCM_HWModifyState. PSI-7965
4.3.4.8.28. SrvMwCM_HWGetState The PSI shall use the service SrvMwCM_HWGetState. PSI-7967
285
4.3.4.8.29. SrvMwCM_GetIdentify The PSI shall use the service SrvMwCM_GetIdentify. PSI-7720
4.3.4.8.30. SrvMwCM_GetDependency The PSI shall use the service SrvMwCM_GetDependency. PSI-7719
4.3.4.8.31. SrvMwCM_GetRealTime The PSI shall use the service SrvMwCM_GetRealTime. PSI-7721
4.3.4.8.32. SrvMwCM_GetSystemTime The PSI shall use the service SrvMwCM_GetSystemTime. PSI-7722
4.3.4.8.33. SrvMwCM_ConfigurationGetRPLsVersion The PSI shall use the service SrvMwCM_ConfigurationGetRPLsVersion. PSI-8176
4.3.4.8.34. SrvMwCM_ConfigurationGetVersionRPLsON The PSI shall use SrvMwCM_ConfigurationGetVersionRPLsON. the service PSI-8177
4.3.4.8.35. SrvMwCM_FMSRegisterCLient The PSI shall use the service SrvMwCM_FMSRegisterCLient. PSI-7936
4.3.4.8.36. SrvMwCM_FMSRegisterGlobalClient The PSI shall use the service SrvMwCM_FMSRegisterGlobalClient. PSI-7938
286
4.3.4.8.37. SrvMwCM_FMSRequestState The PSI shall use the service SrvMwCM_FMSRequestState. PSI-7940
4.3.4.8.38. SrvMwCM_HWGetIFVsState The PSI shall use the service SrvMwCM_HWGetIFVsState. PSI-7984
4.3.4.8.39. SrvMwCM_HWGetIFVsSectorisationState PSI-7986
4.3.4.9. Used from MwCOM 4.3.4.9.1. SrvMwCom_SendData PSI-8319
The PSI shall use the service SrvMwCom_SendData.
4.3.4.9.2.
SrvMwCom_ReceiveData PSI-8321
The PSI shall use the service SrvMwCom_ReceiveData.
4.3.4.10.
Used from MwDC
4.3.4.10.1. SrvMwDist_RegisterClientAdjacentCentresConfig The PSI shall use SrvMwDist_RegisterClientAdjacentCentresConfig. the service PSI-7756
4.3.4.10.2. SrvMwDist_ModifyAdjacentCentresConfig The PSI shall use the service SrvMwDist_ModifyAdjacentCentresConfig. PSI-7757
287
4.3.4.10.3. SrvMwDist_RegisterClientAFTNMessSendingConfig The PSI shall use the SrvMwDist_RegisterClientAFTNMessSendingConfig. service PSI-7758
4.3.4.10.4. SrvMwDist_ModifyAFTNMessSendingConfig The PSI shall use SrvMwDist_ModifyAFTNMessSendingConfig. the service PSI-7759
4.3.4.10.5. SrvMwDist_RegisterClientAFTNLinesConfig The PSI shall use the service SrvMwDist_RegisterClientAFTNLinesConfig. PSI-7760
4.3.4.10.6. SrvMwDist_ModifyAFTNLinesConfig The PSI shall use the service SrvMwDist_ModifyAFTNLinesConfig. PSI-7761
4.3.4.10.7. SrvMwDist_RegisterClientATISLinkConfig The PSI shall use the service SrvMwDist_RegisterClientATISLinkConfig. PSI-7762
4.3.4.10.8. SrvMwDist_ModifyATISLinkConfig The PSI shall use the service SrvMwDist_ModifyATISLinkConfig. PSI-7763
4.3.4.10.9. SrvMwDist_RegisterClientOperationalConf The PSI shall use the service SrvMwDist_RegisterClientOperationalConf. PSI-7764
4.3.4.10.10. SrvMwDist_ModifyOperationalConf The PSI shall use the service SrvMwDist_ModifyOperationalConf. PSI-7765
288
4.3.4.10.11. SrvMwDist_RegisterClientRadarProcConfig The PSI shall use the service SrvMwDist_RegisterClientRadarProcConfig. PSI-7727
4.3.4.10.12. SrvMwDist_ModifyRadarProcConfig The PSI shall use the service SrvMwDist_ModifyRadarProcConfig. PSI-7766
4.3.4.10.13. SrvMwDist_RegisterClientRadarInputState The PSI shall use the service SrvMwDist_RegisterClientRadarInputState. PSI-7767
4.3.4.10.14. SrvMwDist_ModifyRadarInputState The PSI shall use the service SrvMwDist_ModifyRadarInputState. PSI-7768
4.3.4.10.15. SrvMwDist_RegisterClientSectorisation The PSI shall use the service SrvMwDist_RegisterClientSectorisation. PSI-7728
4.3.4.10.16. SrvMwDist_ModifySectorisation The PSI shall use the service SrvMwDist_ModifySectorisation. PSI-7769
4.3.4.10.17. SrvMwDist_RegisterClientIcaroLinkConfig The PSI shall use the service SrvMwDist_RegisterClientIcaroLinkConfig. PSI-7770
4.3.4.10.18. SrvMwDist_ModifyIcaroLinkConfig The PSI shall use the service SrvMwDist_ModifyIcaroLinkConfig. PSI-7771
289
4.3.4.10.19. SrvMwDist_RegisterClienteSMILinkConfig The PSI shall use the service SrvMwDist_RegisterClienteSMILinkConfig. PSI-7772
4.3.4.10.20. SrvMwDist_ModifySMILinkConfig The PSI shall use the service SrvMwDist_ModifySMILinkConfig. PSI-7773
4.3.4.10.21. SrvMwDist_RegisterClientStoredSect The PSI shall use the service SrvMwDist_RegisterClientStoredSect. PSI-7729
4.3.4.10.22. SrvMwDist_ModifyStoredSect The PSI shall use the service SrvMwDist_ModifyStoredSect. PSI-7725
4.3.4.10.23. SrvMwDist_RegisterClientTDVMProcessingConfig The PSI shall use SrvMwDist_RegisterClientTDVMProcessingConfig. the service PSI-7774
4.3.4.10.24. SrvMwDist_ModifyTDVMProcessingConfig The PSI shall use the service SrvMwDist_ModifyTDVMProcessingConfig. PSI-7775
4.3.4.10.25. SrvMwDist_RegisterClientTPVFuncConfig The PSI shall use the service SrvMwDist_RegisterClientTPVFuncConfig. PSI-7776
4.3.4.10.26. SrvMwDist_ModifyTPVFuncConfig The PSI shall use the service SrvMwDist_ModifyTPVFuncConfig. PSI-7777
290
4.3.4.10.27. SrvMwDist_ModifyAccessCode The PSI shall use the service SrvMwDist_ModifyAccessCode. PSI-7724
4.3.4.10.28. SrvMwDist_RegisterClientAccessCode The PSI shall use the service SrvMwDist_RegisterClientAccessCode. PSI-7726
4.3.4.10.29. SrvMwDist_RegisterClientNovaSMRConfig The PSI shall use the service SrvMwDist_RegisterClientNovaSMRConfig. PSI-8261
4.3.4.10.30. SrvMwDist_ModifyNovaSMRConfig The PSI shall use the service SrvMwDist_ModifyNovaSMRConfig. PSI-8262
4.3.4.10.31. SrvMwDist_RegisterClientAsterixCat10Config The PSI shall use SrvMwDist_RegisterClientAsterixCat10Config. the service PSI-8263
4.3.4.10.32. SrvMwDist_ModifyAsterixCat10Config The PSI shall use the service SrvMwDist_ModifyAsterixCat10Config. PSI-8264
4.3.4.10.33. SrvMwDist_RegisterClientSNETSFuncConfig The PSI shall use SrvMwDist_RegisterClientSNETSFuncConfig. the service PSI-8265
4.3.4.10.34. SrvMwDist_ModifySNETSFuncConfig The PSI shall use the service SrvMwDist_ModifySNETSFuncConfig. PSI-8266
291
4.3.4.10.35. SrvMwDist_RegisterClientTCPV-TLPVLinkConfig The PSI shall TLPVLinkConfig. use the service SrvMwDist_RegisterClientTCPV- PSI-8269
4.3.4.10.36. SrvMwDist_ModifyTCPV-TLPVLinkConfig The PSI shall use the service SrvMwDist_ModifyTCPV-TLPVLinkConfig. PSI-8270
4.3.4.10.37. SrvMwDist_RegisterClientTLPVtowerLinkConfig The PSI shall use SrvMwDist_RegisterClientTLPVtowerLinkConfig. the service PSI-8271
4.3.4.10.38. SrvMwDist_ModifyTLPVtowerLinkConfig The PSI shall use the service SrvMwDist_ModifyTLPVtowerLinkConfig. PSI-8272
4.3.4.10.39. SrvMwDist_RegisterClientRemoteTDVMLinkConfig The PSI shall use the SrvMwDist_RegisterClientRemoteTDVMLinkConfig. service PSI-8273
4.3.4.10.40. SrvMwDist_ModifyRemoteTDVMLinkConfig The PSI shall use the service SrvMwDist_ModifyRemoteTDVMLinkConfig. PSI-8274
4.3.4.10.41. SrvMwDist_RegisterClientSSDSessionState The PSI shall use the service SrvMwDist_RegisterClientSSDSessionState. PSI-8275
4.3.4.10.42. SrvMwDist_ModifySSDSessionState The PSI shall use the service SrvMwDist_ModifySSDSessionState. PSI-8276
292
4.3.4.10.43. SrvMwDist_RegisterClientCamerasAssignment The PSI shall use SrvMwDist_RegisterClientCamerasAssignment. the service PSI-8279
4.3.4.10.44. SrvMwDist_ModifyCamerasAssignment The PSI shall use the service SrvMwDist_ModifyCamerasAssignment. PSI-8280
4.3.4.10.45. SrvMwDist_RegisterClientBlockORState The PSI shall use the service SrvMwDist_RegisterClientBlockORState. PSI-8281
4.3.4.10.46. SrvMwDist_ModifyBlockORState The PSI shall use the service SrvMwDist_ModifyBlockORState. PSI-8282
4.3.4.10.47. SrvMwDist_RegisterClientMtcdConfig The PSI shall use the service SrvMwDist_RegisterClientMtcdConfig. PSI-9163
4.3.4.10.48. SrvMwDist_ModifyMtcdConfig The PSI shall use the service SrvMwDist_ModifyMtcdConfig. PSI-9165
4.3.4.11.
Used from MwER
4.3.4.11.1. SrvMwER_Generate The PSI shall use the service SrvMwER_Generate. PSI-7730
293
4.3.4.12.
Used from MwREC
4.3.4.12.1. SrvMwRec_GetUserList The PSI shall use the service SrvMwRec_GetUserList. PSI-8284
4.3.4.12.2. SrvMwRec_GetHostList The PSI shall use the service SrvMwRec_GetHostList. PSI-8287
4.3.4.12.3. SrvMwRec_GetGroupList The PSI shall use the service SrvMwRec_GetGroupList. PSI-8288
4.3.4.12.4. SrvMwRec_GetSimulationSessions The PSI shall use the service SrvMwRec_GetSimulationSessions. PSI-8360
4.3.4.12.5. SrvMwRec_RecoverFromTape The PSI shall use the service SrvMwRec_RecoverFromTape. PSI-8361
4.3.4.12.6. SrvMwRec_GetTapeContain The PSI shall use the service SrvMwRec_GetTapeContain. PSI-8362
4.3.4.12.7. SrvMwRec_NewTape The PSI shall use the service SrvMwRec_NewTape. PSI-8363
4.3.4.12.8. SrvMwRec_GenerateERQuery The PSI shall use the service SrvMwRec_GenerateERQuery. PSI-8364
294
4.3.4.13.
Used from MwSTAT
4.3.4.13.1. SrvMwStat_SubscribeStatisticsProcDev The PSI shall use the service SrvMwStat_SubscribeStatisticsProcDev. PSI-8086
4.3.4.13.2. SrvMwStat_ResetStatisticsProcDev The PSI shall use the service SrvMwStat_ResetStatisticsProcDev. PSI-8087
4.3.4.13.3. SrvMwStat_SubscribeStatisticsProcProc The PSI shall use the service SrvMwStat_SubscribeStatisticsProcProc. PSI-8088
4.3.4.13.4. SrvMwStat_ResetStatisticsProcProc The PSI shall use the service SrvMwStat_ResetStatisticsProcProc. PSI-8089
4.3.4.13.5. SrvMwStat_SubscribeStatisticsProcIntCom The PSI shall use the service SrvMwStat_SubscribeStatisticsProcIntCom. PSI-8090
4.3.4.13.6. SrvMwStat_ResetStatisticsProcIntCom The PSI shall use the service SrvMwStat_ResetStatisticsProcIntCom. PSI-8091
4.3.4.13.7. SrvMwStat_SubscribeStatisticsProcExtCom The PSI shall use the service SrvMwStat_SubscribeStatisticsProcExtCom. PSI-8092
295
4.3.4.13.8. SrvMwStat_ResetStatisticsProcExtCom The PSI shall use the service SrvMwStat_ResetStatisticsProcExtCom. PSI-8093
4.3.4.13.9. SrvMwStat_SubscribeStatisticsProcDiskUsage The PSI shall use SrvMwStat_SubscribeStatisticsProcDiskUsage. the service PSI-8094
4.3.4.13.10. SrvMwStat_ResetStatisticsProcDiskUsage The PSI shall use the service SrvMwStat_ResetStatisticsProcDiskUsage. PSI-8095
4.3.4.13.11. SrvMwStat_SubscribeStatisticsProcS-RUDP The PSI shall use the service SrvMwStat_SubscribeStatisticsProcS-RUDP. PSI-8096
4.3.4.13.12. SrvMwStat_ResetStatisticsProcS-RUDP The PSI shall use the service SrvMwStat_ResetStatisticsProcS-RUDP. PSI-8097
4.3.4.13.13. SrvMwStat_SubscribeStatisticsEADR The PSI shall use the service SrvMwStat_SubscribeStatisticsEADR. PSI-8098
4.3.4.13.14. SrvMwStat_ResetStatisticsEADR The PSI shall use the service SrvMwStat_ResetStatisticsEADR. PSI-8099
4.3.4.13.15. SrvMwStat_SubscribeStatisticsSIS The PSI shall use the service SrvMwStat_SubscribeStatisticsSIS. PSI-8100
296
4.3.4.13.16. SrvMwStat_ResetStatisticsSIS The PSI shall use the service SrvMwStat_ResetStatisticsSIS. PSI-8101
4.3.4.13.17. SrvMwStat_SubscribeStatisticsTLPV The PSI shall use the service SrvMwStat_SubscribeStatisticsTLPV. PSI-8102
4.3.4.13.18. SrvMwStat_ResetStatisticsTLPV The PSI shall use the service SrvMwStat_ResetStatisticsTLPV. PSI-8103
4.3.4.13.19. SrvMwStat_SubscribeStatisticsTCPV The PSI shall use the service SrvMwStat_SubscribeStatisticsTCPV. PSI-8104
4.3.4.13.20. SrvMwStat_ResetStatisticsTCPV The PSI shall use the service SrvMwStat_ResetStatisticsTCPV. PSI-8105
4.3.4.13.21. SrvMwStat_SubscribeStatisticsGIPV The PSI shall use the service SrvMwStat_SubscribeStatisticsGIPV. PSI-8106
4.3.4.13.22. SrvMwStat_ResetStatisticsGIPV The PSI shall use the service SrvMwStat_ResetStatisticsGIPV. PSI-8107
4.3.4.13.23. SrvMwStat_SubscribeStatisticsTDVT The PSI shall use the service SrvMwStat_SubscribeStatisticsTDVT. PSI-8108
297
4.3.4.13.24. SrvMwStat_ResetStatisticsTDVT The PSI shall use the service SrvMwStat_ResetStatisticsTDVT. PSI-8109
4.3.4.13.25. SrvMwStat_SubscribeStatisticsTPVT The PSI shall use the service SrvMwStat_SubscribeStatisticsTPVT. PSI-8110
4.3.4.13.26. SrvMwStat_ResetStatisticsTPVT The PSI shall use the service SrvMwStat_ResetStatisticsTPVT. PSI-8111
4.3.4.13.27. SrvMwStat_SubscribeStatisticsNormalTDVM The PSI shall use SrvMwStat_SubscribeStatisticsNormalTDVM. the service PSI-8112
4.3.4.13.28. SrvMwStat_ResetStatisticsNormalTDVM The PSI shall use the service SrvMwStat_ResetStatisticsNormalTDVM. PSI-8113
4.3.4.13.29. SrvMwStat_SubscribeStatisticsAutonomousTDVM The PSI shall use SrvMwStat_SubscribeStatisticsAutonomousTDVM. the service PSI-8114
4.3.4.13.30. SrvMwStat_ResetStatisticsAutonomousTDVM The PSI shall use SrvMwStat_ResetStatisticsAutonomousTDVM. the service PSI-9099
4.3.4.13.31. SrvMwStat_SubscribeStatisticsGSIGroups The PSI shall use the service SrvMwStat_SubscribeStatisticsGSIGroups. PSI-8115
298
4.3.4.13.32. SrvMwStat_ResetStatisticsGSIGroups The PSI shall use the service SrvMwStat_ResetStatisticsGSIGroups. PSI-8116
4.3.4.13.33. SrvMwStat_SubscribeStatisticsGSIFTPFiles The PSI shall use the service SrvMwStat_SubscribeStatisticsGSIFTPFiles. PSI-8117
4.3.4.13.34. SrvMwStat_ResetStatisticsGSIFTPFiles The PSI shall use the service SrvMwStat_ResetStatisticsGSIFTPFiles. PSI-8118
4.3.4.13.35. SrvMwStat_SubscribeStatisticsGSIUsage The PSI shall use the service SrvMwStat_SubscribeStatisticsGSIUsage. PSI-8119
4.3.4.13.36. SrvMwStat_ResetStatisticsGSIUsage The PSI shall use the service SrvMwStat_ResetStatisticsGSIUsage. PSI-8120
4.3.4.13.37. SrvMwStat_SubscribeStatisticsGSIFTPSess The PSI shall use the service SrvMwStat_SubscribeStatisticsGSIFTPSess. PSI-8121
4.3.4.13.38. SrvMwStat_ResetStatisticsGSIFTPSess The PSI shall use the service SrvMwStat_ResetStatisticsGSIFTPSess. PSI-8122
4.3.4.13.39. SrvMwStat_SubscribeStatisticsPrinters The PSI shall use the service SrvMwStat_SubscribeStatisticsPrinters. PSI-8123
299
4.3.4.13.40. SrvMwStat_ResetStatisticsPrinters The PSI shall use the service SrvMwStat_ResetStatisticsPrinters. PSI-8124
4.3.4.13.41. SrvMwStat_UpdateStatisticsPrinters The PSI shall use the service SrvMwStat_UpdateStatisticsPrinters. PSI-9101
4.3.4.13.42. SrvMwStat_SubscribeStatisticsSurfaceDelays The PSI shall use SrvMwStat_SubscribeStatisticsSurfaceDelays. the service PSI-8125
4.3.4.13.43. SrvMwStat_ResetStatisticsSurfaceDelays The PSI shall use the service SrvMwStat_ResetStatisticsSurfaceDelays. PSI-8126
4.3.4.13.44. SrvMwStat_SubscribeStatisticsSurfaceSensor The PSI shall use SrvMwStat_SubscribeStatisticsSurfaceSensor. the service PSI-8127
4.3.4.13.45. SrvMwStat_ResetStatisticsSurfaceSensor The PSI shall use the service SrvMwStat_ResetStatisticsSurfaceSensor. PSI-8128
4.3.4.13.46. SrvMwStat_SubscribeStatisticsAirDelays The PSI shall use the service SrvMwStat_SubscribeStatisticsAirDelays. PSI-8129
4.3.4.13.47. SrvMwStat_ResetStatisticsAirDelays The PSI shall use the service SrvMwStat_ResetStatisticsAirDelays. PSI-8130
300
4.3.4.13.48. SrvMwStat_SubscribeStatisticsSystematicErrorsCalculation The PSI shall use the SrvMwStat_SubscribeStatisticsSystematicErrorsCalculation. service PSI-8131
4.3.4.13.49. SrvMwStat_ResetStatisticsSystematicErrorsCalculation The PSI shall use the SrvMwStat_ResetStatisticsSystematicErrorsCalculation. service PSI-8132
4.3.4.13.50. SrvMwStat_SubscribeStatisticsRadarTCAMS The PSI shall use SrvMwStat_SubscribeStatisticsRadarTCAMS. the service PSI-8133
4.3.4.13.51. SrvMwStat_ResetStatisticsRadarTCAMS The PSI shall use the service SrvMwStat_ResetStatisticsRadarTCAMS. PSI-8134
4.3.4.13.52. SrvMwStat_SubscribeStatisticsSILV The PSI shall use the service SrvMwStat_SubscribeStatisticsSILV. PSI-8135
4.3.4.13.53. SrvMwStat_ResetStatisticsSILV The PSI shall use the service SrvMwStat_ResetStatisticsSILV. PSI-8136
4.3.4.13.54. SrvMwStat_SubscribeStatisticsATIS-SMI The PSI shall use the service SrvMwStat_SubscribeStatisticsATIS-SMI. PSI-8137
4.3.4.13.55. SrvMwStat_ResetStatisticsATIS-SMI The PSI shall use the service SrvMwStat_ResetStatisticsATIS-SMI. PSI-8138
301
4.3.4.13.56. SrvMwStat_SubscribeStatisticsAMAN The PSI shall use the service SrvMwStat_SubscribeStatisticsAMAN. PSI-8139
4.3.4.13.57. SrvMwStat_ResetStatisticsAMAN The PSI shall use the service SrvMwStat_ResetStatisticsAMAN. PSI-8140
4.3.4.13.58. SrvMwStat_SubscribeStatisticsMTCD The PSI shall use the service SrvMwStat_SubscribeStatisticsMTCD. PSI-8141
4.3.4.13.59. SrvMwStat_ResetStatisticsMTCD The PSI shall use the service SrvMwStat_ResetStatisticsMTCD. PSI-8142
4.3.4.14.
Used from TILAIS
4.3.4.14.1. SrvTilais_RequestSpecialDeterminedAreaInformation The PSI shall use the Request an Special Determined Area Information Load PSI-7542 service SrvTilais_RequestSpecialDeterminedAreaInformation.
4.3.4.14.2. SrvTilais_RequestAllSpecialAreasList The PSI shall use the Request All Special Areas List Load service PSI-7543 SrvTilais_RequestAllSpecialAreasList.
4.3.4.14.3. SrvTilais_DynSpecialAreaCreation The PSI shall use the Dynamic SrvTilais_DynSpecialAreaCreation. Special Area Creation service PSI-7544
4.3.4.14.4. SrvTilais_DynSpecialAreaCancellation The PSI shall use the Dynamic Special Area Cancellation service PSI-7545 SrvTilais_DynSpecialAreaCancellation. 302 Software Requirements Description
4.3.4.14.5. SrvTilais_SpecialAreaModification The PSI shall use the Special SrvTilais_SpecialAreaModification. Area Modification service PSI-7546
4.3.4.15.
Used from TILMET
4.3.4.15.1. SrvTilmet_ModifyQnh The PSI shall use the QNH modification service SrvTilmet_ModifyQnh. PSI-7554
4.3.4.16.
Used from TIMDT
4.3.4.16.1. SrvTimdt_ModifyQnh In Tower environment PSI (PST) shall use the QNH modification service PSI-9115 SrvTimdt_ModifyQnh.
4.3.4.17.
Used from TLPV
4.3.4.17.1. SrvTlpv_RequestAerodromeInformation The PSI shall use the service SrvTlpv_RequestAerodromeInformation. PSI-7621
4.3.4.17.2. SrvTlpv_ChangeActiveRunways The PSI shall use the service SrvTlpv_ChangeActiveRunways. PSI-7622
4.3.4.17.3. SrvTlpv_FlightStripsAdvanceGeneration The PSI shall use the service SrvTlpv_FlightStripsAdvanceGeneration. PSI-7623
303
4.3.4.18.
Used from ADAP-GV
4.3.4.18.1. SrvAdapgv_RemoteDistributionSurveillance The PSI shall use the service SrvAdapgv_RemoteDistributionSurveillance. PSI-8382
4.3.4.18.2. SrvAdapgv_AtisLines The PSI shall use the service SrvAdapgv_AtisLines. PSI-8383
4.3.4.18.3. SrvAdapgv_SmiAerodromes The PSI shall use the service SrvAdapgv_SmiAerodromes. PSI-8384
4.3.4.18.4. SrvAdapgv_PictGroupDepen The PSI shall use the service SrvAdapgv_PictGroupDepen. PSI-8385
4.3.4.18.5. SrvAdapgv_StandardOperationalConfigDepen The PSI shall use SrvAdapgv_StandardOperationalConfigDepen. the service PSI-8386
4.3.4.18.6. SrvAdapgv_RadarDataDepen The PSI shall use the service SrvAdapgv_RadarDataDepen. PSI-8387
4.3.4.18.7. SrvAdapgv_ObjectsOfResponsibilityDepen The PSI shall use the service SrvAdapgv_ObjectsOfResponsibilityDepen. PSI-8388
4.3.4.18.8. SrvAdapgv_SurfaceSensorsDepen The PSI shall use the service SrvAdapgv_SurfaceSensorsDepen. PSI-8389
304
4.3.4.18.9. SrvAdapgv_GpvaAerodromesDepen The PSI shall use the service SrvAdapgv_GpvaAerodromesDepen. PSI-8390
4.3.4.18.10. SrvAdapgv_AmanAerodromes The PSI shall use the service SrvAdapgv_AmanAerodromes. PSI-8391
4.3.4.18.11. SrvAdapgv_PictsDataDepen The PSI shall use the service SrvAdapgv_PictsDataDepen. PSI-8392
4.3.4.18.12. SrvAdapgv_MonoradarParameters The PSI shall use the service SrvAdapgv_MonoradarParameters. PSI-8393
4.3.4.18.13. SrvAdapgv_EnRouteRadarCoverageDepen The PSI shall use the service SrvAdapgv_EnRouteRadarCoverageDepen PSI-9129 to obtain radar separation information in En-route dependencies. A#12845
4.3.4.18.14. SrvAdapgv_TopologyResources The PSI shall use the service SrvAdapgv_TopologyResources to obtain PSI-9170 whether an ACC is adapted to provide Reduced Radar Separation or not. A#12845
4.4. RELIABILITY / MAINTAINABILITY / AVAILABILITY REQUIREMENTS N/A 4.5. DESIGN REQUIREMENTS The software design will be based on Open System principles. It will implement rather open specifications for interfaces, services and data format. In this way, it will be possible to migrate applications, accurately implemented, to a wide range of different systems with minimum changes and both work with other applications of local or remote systems as well as interact with users in a defined way which makes easy also the transition of these users to those systems. Therefore, the following are the main characteristics that the PSI software will have: Software Requirements Specification 305
Portability: It shall be possible to migrate the conceptual and application PSI-1109 objects at source code level to other systems of equal - or superior - scale of the same or subsequent generations, as well as to equipments from different manufacturers. Scalability: It shall be possible to Execute the same application software on PSI-1110 processing platforms with different capacities and processing power. It will include the possibility of functional migrations to platforms with fewer performances.
ASC#88
The operating systems used in the different Sector Suite's processing elements will comply with POSIX 1003.1 standard with at least the conforming POSIX Applications category. Extensions of the real time operating system and of ADA interface will take into account the latest versions of POSIX 1003.4 and POSIX 1003.5 draft versions. 4.5.1. SAFETY REQUIREMENTS
Not applicable for this version. 4.6. CAPACITY AND PERFORMANCES REQUIREMENTS 4.6.1. Data Loading and Data Capacity
Definitions Input load data: Amount of data received by the LAN interface (..... ) concerning or not the PSI. Part of this data may be kept retained and processed by the PSI. Stored load data: It is the received load fraction concerning the PSI and it has to be stored for being processed and displayed in the PSIs. Displayed load data: Amount of data that has to be displayed on screen. It will comprise the stored load data, the HMI management elements and the data for extrapolated future situations or predicted situations generated by planning tools. It is understood that the displayed load data due to extrapolated situations will be equivalent to 30% of the radar data load. The overload level will only affect the system response times in a proportional manner. From the physical point of view it shall be able to exist up to 4 Control, PSI-1128 Monitoring and Display Positions (PSI) according to that defined in the design document of the system. In any of the positions, any of the loaded profiles shall be able to be executed. PSI-1152
4.6.2.
Response Times
Response times refer to displayed load refreshment times. Response times definitions for presentation management: 306 Software Requirements Description
Refresh cycle response time (RCRT). It is the cursor refresh time.
Menus display response time (MPRT). It is the time lag between a symbol entry and the presentation of the menu corresponding to this symbol. Screen update response time (SURT). It is the time necessary for screen re-updating with locally stored data after executing an introduction management action that requires screen changes, e.g. with a change in windows hierarchy. Internal processing response time (IPRT). It is the time lag between a scrolling action ending, a position change or window size and the complete repainting of the image contained in the window with the new configuration. It is also the time necessary for the complete repainting of a window stored in the system and that does not require data previous preparation in external to PSI, neither transmission of them through the LAN. Recovery times are associated with failure situations recovery. The maximum start-up time for a (PSI) position in system mode shall be 5 PSI-4273 minutes. Considering as Initial State: Operating System started up. The start-up time shall be understood as the time elapsed from entering the user and password to displaying the initial screen of the position.
4.6.3.
Graphic Screens Features
Minimum characteristics for the very high resolution monitor (Main Screen) will be: 4.6.4. Minimum resolution: 2048 x 2048 pixels Mask step < 0.31 mm Minimum screen size: 2500 cm2 Video bandwidth > 300 MHz Brightness level > 20 FL Geometric distortion < 1% Lines width < 1.5 mm Refresh frequency > 60 Hz not inter-linked Network Interfaces Features
The PSI will be connected to the remaining system by LAN controllers that comply with the globally laid down requirements by the communications subsystem. 4.6.5. Data Input Devices Features
The Mouse will have 120 points per cm resolution and 3 buttons. The touch membrane will have a 3mm precision, an action force of 100 to 200 gr. and an optical transmission of 91%. 4.6.6. EnRoute Radar Separation Features ASC#526
The maximun number of radar combinations (for each sector) for the TC shall PSI-9185 be 24. The maximun number of radar combinations (for each sector) for the DTC PSI-9186 Software Requirements Specification
ASC#526 307
shall be 286.
4.7. SECURITY / PRIVACY REQUIREMENTS 4.7.1. Logical Security
Non authorized users for using the PSI shall not access to the system or to a PSI-190 part of it.
In the access procedure, the input of the user (login) shall cause the validity of PSI-1171 it, which will be authenticated if the associated user password is correct.
Every authenticated user shall be authorized to access with the PSI-1180 corresponding access profile.
The access profile shall fix the restrictions and functionalities which provide PSI-1181 the application.
The access profile fixes the functionalities where the user shall access.
PSI-1175
The incorrect input of a pair user-password shall impede the access to the PSI-1178 HMI of the application.
The user pairs and password shall be defined in the installation.
PSI-1172
The user pairs and password shall be modified in support.
PSI-4274
The pair user-password shall fix the access profile.
PSI-1174
4.7.2.
Physical Security
The maximum security level and failure resistance are pursued, from the hardware and software points. So, their characteristics degradation in the presence of failures is minimized, and the suitable protection of kept data is guaranteed. The support computer of the PSI shall be connected to two double networks PSI-473 of the local area (LAN) to which the rest of SACTA sub-systems are connected (Radar Control LAN's).
308
4.8. INSTALLATION REQUIREMENTS The PSI shall comply with SACTA installation general requirements. PSI-1117
4.9. ACCEPTANCE REQUIREMENTS Previously its acknowledgement, the component shall have to pass the PSI-202 established tests in the corresponding documents of Tests Plan and Tests Procedures, and the ones performed according to the established in the Quality Guarantee Plan.
4.10.
HW REQUIREMENTS
4.10.1. HW Environment The hardware environment of the PSI consists of: 4.10.2. Screens The PSI will have one screen denominated as Main Screen. The Main Screen shall be a colour monitor with 2048 x 2048 pixel resolution PSI-1063 or a colour monitor with 1280 x 1024 pixel resolution.
All the crystals of presentation devices shall be antireflective in order to not PSI-1065 distort or reflect the environmental light from any view angle.
4.10.3. QWERTY Keyboard The PSI shall have a standard expanded PC QWERTY keyboard with 119 PSI-1070 alphanumeric keys and 12 function keys.
4.10.4. Pointer Device The PSI shall have a three-button prompt device that can be a mouse or a PSI-1068 rollball compatible with the mouse interface.
4.10.5. Sound The PSI shall have associated devices to generate acoustic alarms. PSI-1077
309
4.11.
CONFIGURATION DATA PSI-7270 A#18429 A#19079 A#17182 A#12845 A#12852
The PSI shall load the following not-user configuration parameter:
Hoja de clculo de Microsoft Excel
The user profile will be contained in two files editable with the Vi editor or similar UNIX A#12845 ones, but also with PC tools (Notepad or Word) that generate an output compatible with the application. One of the files will specify the event reports to display on the PSI with that profile, and the other file will contain the following information: Title that will be displayed on the main window. Profile Identification Name. Alarm Availability. Definition of Alarm Monitoring Privilege. Definition of Alarm Privileged Profile. Radar separation availability for TMA dependencies. Radar separation availability for En-route dependencies.
Permanence time of the acknowledged event reports inside the event reports window. Permanence time of the unacknowledged event reports inside the event reports window. Definition of access to the different scenarios. Functions The accessible functions for each profile will be configurable. Likewise it will be possible to define whether these functions will be accessible from the menu and from which menu level (1st or 2nd level) or/and clicking the right button on the corresponding scenario (only available for certain functions) and what text will be displayed on the functions bar. A number of items will be defined to be displayed on the functions bar, and depending on them, the functions will be placed as first or second level ones. Each function will normally include a series of subfunctions which couldn't be dismembered and which will have to be in the same item and in the same level, such as the Radar Processing Configuration (Normal, Autonomous Enroute and Autonomous TMA). In the SPV scenario, in each PSI, the name of the profile in use will be displayed. All user who is authorized to access to the system (see Logical Security PSI-1386 Section) shall load the associated profile which will fix the functionality and appearance of the application for this user. Each Profile shall consist of configurable elements and other elements which PSI-1399 are common to all the profiles and non-configurable items.
310
The profiles shall be configured by means of input in editable plain files by PSI-1400 any text editor.
Also a GLOBAL profile which will have the right to execute all the functions PSI-1409 shall be defined.
The same user profile could be loaded in different PSIs. In these cases, a PSI-1415 different index which will allow to identify them shall be configured.
As many user profiles as modes of operation with the PSI desired shall be PSI-2676 able to be defined in each centre.
It shall be advisable to define redundant profiles, so that, if a position crashes, PSI-2675 another position can take over the functions of the crashed one.
4.11.1. Non-Configurable Elements The following elements will not be configurable by PSI profile and they will be common to all the profiles. EVENT REPORT Messages Zone Time System PSI-1401
Number of subsystems displayed in the Subsystems area of the main scenario. Subsystems Scenarios Composition.
4.11.2. Configurable Elements 4.11.2.1. Title
The Title which shall appear in the profile Identification Area will be PSI-1393 configurable per configuration file.
4.11.2.2.
Functions PSI-1406
The containers which shape the Functions Area shall be configured Container is understood as each pigeonhole where a menu element will be located.
The containers of the functions area shall be activated by clicking on the LB of PSI-2677 the pointer device.
It shall be possible to define for each function if it is accessible from the menu PSI-1412 and in what container it could be located. Software Requirements Specification 311
Those non accessible options/functions shall be displayed grayed out
PSI-2678
The functions could be grouped and displayed in different levels. In these PSI-1413 cases, the option which gives access to this sub-level shall be configurable.
On clicking with the LB of the pointer device on the options/functions which PSI-2679 haven't got sub-level, they shall give access to the function execution window.
Those options/functions which give access to other sub-levels shall show an PSI-2680 arrow on the right of the title.
The sub-levels shall be displayed after clicking with the RB of the pointer PSI-2681 device on the corresponding option.
There shall be functions closely linked each other. In these cases, they could PSI-1410 not be separated. For example: Radar Processing Configuration (Normal, Enroute Autonomous and TMA Autonomous). The profile of each function shall be defined according to its capacity of PSI-1414 executing the aforementioned function: "Yes" Privileged NO" Privileged "ALWAYS" has execution privilege "NEVER" has execution privilege or
"N/A A profile with a "Privileged" associated function means that it will be allowed to execute that function to the operative profile loaded in PSI, with the lower index configured in execution function. If the profile is "Not Privileged", it shall be possible to define the Privileged profile for that function, so that the absence of the privileged user profile in the system shall cause the Non-Privileged profile to obtain the privileges for the function with the lower index configured in execution function. In case the profile has"ALWAYS execution privileges for a function, the configured index will not be taken into account, in order to have the right of execution. This function will always stay as privileged, regardless the state of the remaining PSIs. In case the profile "NEVER" has execution privileges for a function, it won't be able to obtain the right of execution. In this case, no check of privileges will be done, so that, this function will always stay disabled for this profile. In case "N/A", privileges checks won't be performed on executing this function.
312
Not all the functions shall be affected by the rights definition. Only those which PSI-1417 modify data of the system, which hereinafter will be called "configuration functions". Each function shall be catalogued as "Fundamental" or "Not Fundamental", PSI-1418 too.
If a function catalogued as "Fundamental" is not available among all the PSI-1419 execution profiles, the corresponding alarm shall be activated.
The functions to be considered shall be the following: Current Sectoring Other Sectoring (stored and standard) TDVM Functions Configuration Special Areas Configuration Operative Configuration of Adjacent Centres Links Configuration Print Flight Progression Strips QNH Configuration Aerodrome Parameters Change Event Reports Management Advanced event reports Management Query of Received AFTN Messages Physical Configuration of Elements Tandem Switchover Start up-Shutdown Radar Processing Configuration Radar Input Configuration Technical TDVM Functions Configuration SMR Configuration Configuration Automatic AFTN Processing PVRs Change TDVM Statistics EADR Statistics DISPI Statistics TLPV Statistics GSI Statistics SILV Statistics TCPV Statistics GIPV Statistics TDVT Statistics TPVT Statistics SDL Statistics Processor Statistics Printers Statistics
PSI-1396
313
GSI Configuration Tape Information Recovery GIPV Configuration GIPV External Systems Configuration DISPI Configuration
Exit PSI (*see acronyms in Appendix) In a generic way, the following profiles shall be defined for each centre:A PSI-1407 technical profile (PSSE=Technical Supervision Position)An operative profile (PSSO=Operation Room Supervision Position)A support profile (PMTO=Maintenance Position )The functionality of these profiles is depicted in the following table of functionalities: See next table. ACC with Cetntral Systems PSSE Current Sectoring Others Sectoring TDVM Functions Configuration Special Areas Configuration Adjacent Centres Operative Configuration Links Configuration Printing of Flight Strips Aerodrome Parametres Change Advanced Event Report Management Received AFTN Messages search Help Elements Physical Configuration Tandem Switchover Startup-Shutdown Radar Processing configuration Radar Input Configuration Technical TDVM Functions Configuration AFTN Automatic Processing Configuration Messages sending configuration to CFMU. RPLs Change 314 O O O O O O O O Y O Y Y Y Y Y Y Y Y Y Y PSSO Y Y Y Y Y Y Y Y Y Y Y N N N N N N N N N PMTO O O O O O O O O Y O Y O O O O O O O O O ACC without Central Systems PSSE O O O O O O O O Y NA Y Y Y Y Y Y Y NA NA NA PSSO Y Y Y Y Y Y Y Y Y NA Y N N N N N N NA NA NA PMTO O O O O O O O O Y NA Y O O O O O O NA NA NA
Function
Function TDVM Statistics EADR Statistics SIS Statistics TLPV Statistics GSI Statistics TCPV Statistics SILV Statistics TDVT Statistics GIPV Statistics Processor Statistics Printers Statistics GSI Configuration Recovering of Tape Information GIPV Configuration Enabling of GIPV External Systems Configuration of SIS External Systems Exit form PSI Delays Statistics
ACC with Cetntral Systems O O O O O O O O O O O O O O O O Y O N Y N N N N N N N N N N N N N N Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
ACC without Central Systems O O O O O NA O O NA O O O O NA NA O Y O N Y N N N NA N N NA N N N N NA NA N Y N Y Y Y Y Y NA Y Y NA Y Y Y Y NA NA Y Y Y
Legend: Y=Yes; O=Optional; N=No;NA=Not Applicable
Table 4.3.4.18.14-59 : Functionalities Generally, a technical profile shall be defined for each centre (PST:Tower PSI-3857 Supervision Position), from where all the functions could be executed.
The names of the used functions shall be the following: F_SECT: Sectoring (Current, Others) F_TDVM: TDVM Functions F_AESP: Special Areas Warning F_CCOL: Adjacent Centres Configuration F_CENL: Links Configuration F_CENL_TOR: TLPV-Tower Link Configuration F_CES: Link with SCENA Configuration F_IFICH: Flight Plan Strips Printing
PSI-3539
315
F_CQNH: QNH Configuration F_PAER: Aerodrome Parameters F_PAER_QNH: Change of Aerodrome and QNH parameters F_GHISAV: Advanced event reports Management F_CSAFTN: Rejected AFTN Messages Query F_CFIS: Elements Physical Configuration
F_CTAN: Tandem Switchover (UAST, UTDVM, UTLPV, UGSI, UMTLP) F_APAR: Startup-Shutdown (Start Up System, Shut Down System, POS REM, POS ENROUTE, POS TMA, UAST, UCS, PSI, UGSI, UTDVM, USILV, UTLPV, UTPVT) F_CTRAT_RAD: Radar Processing Configuration (Normal TDVM Radar Processing, Enroute TDVM Radar Processing, TMA TDVM Radar Processing) F_ENT_RAD: Radar Inputs Configuration (DDE Radar Inputs and ASTERIX Radar Inputs) F_TDVM_TEC: Technical TDVM Functions Configuration F_CSMR: SMR Configuration F_CAFTN: AFTN Configuration F_CPVRS: RPLs Loading
F_ETDVM: TDVM Statistics (Normal TDVM Statistics, Enroute Autonomous TDVM Statistics, TMA Autonomous TDVM Statistics) F_EEADR: EADR Statistics (Normal Radar Site Statistics, Enroute Radar Site Statistics, TMA Radar Site Statistics) F_EDISPI: DISPI Statistics F_ETLPV: TLPV Statistics F_EGSI: GSI Statistics F_ESILV: SILV Statistics F_ETCPV: TCPV Statistics F_EGIPV: GIPV Statistics F_ESDR: SDR Statistics F_ESDV: TPVT Statistics F_ESDL: SDL Statistics F_ETPVT: TPVT Statistics F_EPRO: Processor Statistics F_EIMP: Printers Statistics
F_CGSI: GSI Configuration (Users Configuration, Information to Record Configuration, Activate-Inhibit Recording, Tape Information Recovery) F_REC_CIN: Tape Information Recovery F_GIPV: GIPV Configuration F_SE_GIPV: GIPV External Systems Configuration F_SIS: SIS Configuration F_EXIT: Exit
316
4.11.2.3.
Scenarios
In the display Central Zone of the screen (see section Interface PSI-1425 Requirements/display Screen) shall be showed a representation of the functional areas which conform the system. The maximum centre scenario shall be defined by adaptation data, so that, PSI-1433 the user profile definition must be according to the centre scenario. The configurations which are not according to the centre scenario shall not be displayed on the PSI. For each user profile, it shall be possible to define whether access is allowed PSI-1432 to the scenario of second level in that area.
The following functional areas shall be available: GIPV TCPV GSI SILV SPV SMDT SIS TLPV TDVM EADR EN-ROUTE SS REM POS TMA SS TWR SS
PSI-1434
The label for these areas shall be configurable within the user profile.
PSI-1435
The display of the RADAR QUALITY element also shall be configured in the PSI-1431 initial scenario of the PSI.
4.11.2.4.
Event Reports
For each user profile the event reports displayed among the ones sent to the PSI-1426 PSI shall be filtered .
The file where the event reports to be displayed shall be specified with that PSI-3537 profile of the PSI will be called event reportS_PerfilZZZ, where "ZZZ" will be the profile name and, the file which will contain the aforementioned Software Requirements Specification 317
information will be called PerfilZZZ, where "ZZZ" will be the profile name. In the user profile shall be indicated the time of permanence on screen of the PSI-1429 acknowledged and unacknowledged event reports. In Appendix C a list of the supervision event reports to be dealed will be displayed. 4.11.2.5. Alarms PSI-1427
For each user profile, it shall be defined whether it includes alarms or not.
If so, it shall be defined if the activation of these alarms is conditioned to the PSI-1428 presence of another user profile in execution, in the system.
318
319
Appendix A : DEFINITIONS
N/A
A-1
A-1
Appendix B : ACRONYMS AND ABBREVIATIONS

A A/C ABI ACC ACID ACT ADB ADEP ADES ADEXP AENA AFDS AFIL AFTN AIS AMIS AoI AoR APP APW ARO ARP ARTAS ASCII ASTERIX ATC ATFM ATIS ATM ATO ATS ATSU C CADF CC CFL CFMU Central Adaptation Data File Control Centre Cleared Flight Level Central Flow Management Unit B-1 Aircraft Advanced Boundary Information message (OLDI) Area Control Centre NATS Aircraft Callsign Information Distributor Activation message (OLDI) Adaptation Data Base Aerodrome of Departure Aerodrome of Destination ATS Data Exchange Protocol Aeropuertos Espaoles y Navegacin Area AFTN Flight Data Server (GIPV client (FDPS)) Aircraft Filed Flight Plan Aeronautical Fixed Telecommunications Network Aeronautical Information Service Air Movement Information System Area of Interest Area of Responsibility Approach Area Proximity Warning Aerodrome Reporting Office Airport Reference Point Air Traffic Management Surveillance Tracker and Server System Information Exchange Code All purpose Structured Eurocontrol Surveillance Information Exchange Air Traffic Control Air Traffic Flow Management Automatic Terminal Information Service Air Traffic Management Actual Time Overhead of Overflying Air Traffic Service Air Traffic Service Unit A#12845
CHG CMD CNL COTS CPL CPU CSSR CTOT CWP D DB DDE DDEP DEP DEP DES DEST DFTI DLA DME DPI DR DT DTC E ECL ECP ECU EET EFL EIA/TIA EOBT ETA ETD ETO F FCR FDDI FDP B-2
Modification Message (ICAO Format) Control Monitoring Display Position Cancellation Message (ICAO Format) Commercial Off-the-shelf systems Current Flight Plan Message (ICAO Format) Control Process Unit Secondary Surveillance Radar Code Calculate Take-Off Time Controller Working Position Data Base Dynamic Data Exchange Date of Deposit Departure Aerodrome Departure Message (OLDI) De-Suspension Message (ADEXP Format) Destination Aerodrome / Aerdromo de Destino Distance From Threshold Indicator Delay Message (ICAO Format) Distance Measuring Equipment Departure Planning Information Direct Route Table Decision Table Double Theoretical Coverage En-Cruise Flight Level Engineering Change Proposal Airspace Controlled by a Sector Suite Estimated Elapsed Time Estimated Flight Plan Level Electronic Industries Association / Telecommunications Industries Association Estimated Off-Block Time Estimated Time of Arrival Estimated Time of Departure Estimated Time Over a significant fix point Ficheros de Control de Reproduccin Fiber Distributed Data Interface Flight Plan Data Processing Software Requirements Description
FDR FIR FIRT FLS FP FPDS FPL FSA FSH FTP G GAT GIPV GPS GSI H HMI HPMUL HPRT HW I IACH IAFP IAPL ICAO ICHG ICMP ICNL ICPL IDEP IDLA IEEE IFP IFPL IFPS IFR IGMP IHG
Fichero de Datos de Reproduccin Flight Information Region FIR Time Flight Suspension Message (ADEXP Format) Flight Plan Flight Plan Dissemination System UK MoD system for air defence Flight Plan Message (ICAO format) First System Activation message (OLDI) Flight Shift Message (CFMU) File Transference Protocol General Air Traffic (Civilian) Gestin de Informacin de Planes de Vuelo Global Positioning System Subsistema Grabador y Servidor de Informacin Human-Machine Interface Historial de Pistas de Sistema HMI Presentation Response Time Hardware Individual ATC Modification Message (ADEXP) Individual ATC Flight Plan Proposal Individual ATC Flight Plan Message (ADEXP) International Civil Aviation Organization Individual Modification Message (ADEXP) Internet Control Message Protocol Individual Cancellation Message (ADEXP) Individual Current Flight Plan Message (ICAO Format) Individual Departure Message (ADEXP) Individual Delay Message (ADEXP) Institute of Electrical and Electronic Engineers Indication of known errors within a FPL Individual Flight Plan Message (ADEXP) Integrated Initial Flight Plan Processing System Instrumental Flight Rules Internet Group Management Protocol Inches of mercury B-3
IMM IP IPC IPRT IPX ISO ISO/OSI L LAM LAN LLC M MAC MART MET METAIS METAR MLDT MOF MPRT MSAW MTBF MTI MTTR N N/A NATS NAVAIDS NCA NE NFS NM NOTAM NSS NTP NTZ NW B-4
Interacting Multiple Models Internet Protocol Interprocess Communication Internal Process Response Time Internetwork Packet Exchange International Organization for Standardization International Standards Organization/Open Systems Interconnect Local Acknowledgment Message Local Area Network Logical Link Control Message for the Abrogation of Coordination (OLDI) Message Acknowledgment Response Time Meteorological Services Meteorological Aeronautical Information Subsystem Meteorological Aviation Routine Weather Report Managed Landing Time Mode of Flight Menus Presentation Response Time Minimum Safe Altitude Warning Medium Time Between Failures Message Type Identifier Medium Time To Repair Not Applicable National Air Traffic Services Ltd Navigational Aids Navigation, Communication and Approach Equipment North-East Orientation Network File System Nautical Mile Notification Aeronautical Message Non-Sectorisable Suit Network Time Protocol Non-Transgression Zones North-West Orientation Software Requirements Description
O O.S. OAT OCM OLDI OMA OSI P PAC PDV PRAD PRADGRAF PSI PSR PST Q QFE QNH QOS R RARP RAW RBL RCRT RDD REDAN REV RFL RMK RNAV RPL RPLDB RPLF RVR RVSM S SAC SACTA System Area Code Sistema Automatizado del Control de Trfico Areo B-5 Reverse Address Resolution Protocol Restricted Area Warning Range Bearing Line Refresh Cycle Response Time Radar Data Display Red de Datos de Navegacin Area Revision message (OLDI) Required Flight Plan Level Remark Area Navigation Repetitive Flight Plan RPL Data Base Repetitive Flight Plan File Runway Visual Range Reduced Vertical Separation Minimum Atmospheric Pressure at Aerodrome Elevation Altimeter sub-scale sitting to obtain elevation when on the ground Quality of Services Preliminary Activation Message (OLDI) Flight Data Operator Position Programa de Reduccin y Anlisis de Datos Programa de Reduccin y Anlisis de Datos de Trfico Areo Grfico Posicin de Supervisin Integrada (Supervision Position) Primary Surveillance Radar Posicin Supervisin de Torre (Tower Supervision Position) Operational System Operational Air Traffic (Military) Operational Coordination message (OLDI) On Line Data Interchange (Standard) Operational Military Aviation Open System Interconnections
SAM SCC SCV SDP SE SELCAL SFDS SFPL SFL SIC SID SIGMET SLC SMI SNMP SP SPECI SPI SPV SRC SRM SS SSR SSS STAR STCA STCA-P STCA-V STS SURT SW SW SYS SYSCO T TACT TAF TAFOR B-6
Slot Allocation Message (ADEXP Format) Space Controlled by Controlling Working Position Voice Communications System Surveillance Data Processing South-East Orientation Selected Calling Surveillance and Flight Data Server System Flight Plan Selected Flight Level System Identification Code Standard Instrumental Departure Procedure Significative MET Slot Requirement Cancellation Message (ADEXP Format) Integrated Meteorological System Simple Network Management Protocol Special Purpose Indicator (ASTERIX) Special Meteorological Aeronautical Report Special Position Identification Subsistema de Supervisin Identification of data Source (ADEXP primary field) Slot Revision Message (ADEXP Format) Sector Suite Secondary Surveillance Radar System Specification (formerly known as a System/Segment Specification) Standard Terminal Arrival Route Procedure Short Term Conflict Alert Short Term Conflict Alert Prediction Short Term Conflict Alert Violation Flight Plan Status (ADEXP Primary Field) Screen Updating Response Time Software South-West Orientation System Messages System Supported Co-ordination CFMU Tactical System Terminal Area Forecast Terminal Area Forecast Report Software Requirements Description
SNOWTAM NOTAM with respect to snow
TC TCP TCP/IP TELNET TFL TMA TLPD TOMS TOS TPV U UAST UDDE UDP UDP/IP UHF UK UKFDB V VFR vLAN VSL W WAN
Theoretical Coverage Transmission Control Protocol Transmission Control Protocol / Internet Protocol Terminal Emulation Local Network Transfer Flight Level Terminal Manoeuvre Area Traffic Load Prediction Device (TOMS) NATS Tactical Operational Management System (flow management systems) Type of Service Tratamiento de Plan de Vuelo Unidad de Adquisicin de Datos ASTERIX Unidad de Adquisicin de Datos Radar en Formato DDE User Datagram Protocol User Datagram Protocol/Internet Protocol Ultra-High Frequency United Kingdom UK Flight Database (NATS management information system) Visual Flight Rules Virtual LAN Vertical Stack List Wide Area Network
Table 4-60 : Acronyms and Abbreviations
B-7
B-8
Appendix C : USE CASES

Not applicable for this version.
C-1
C-1
Appendix D : REQUIREMENTS TRACEABILITY

Information comprised in view "A9 - Trace Table" of Doors.
D-1
D-1
Appendix E : EVENT REPORTS E.1 PSI ERs

The following list specifies the ERs generated by PSI: PSIaso001 PSIaso003 PSIaso005 PSIaso007 PSIaso009 PSIaso011 PSIaso012 PSIaso013 PSIcae001 PSIcen001 PSIcen002 PSIcev001 PSIcor001 PSIcor002 PSIcpa001 PSIgfi001 PSIoff001 PSIoff003 PSIoff005 PSIoff007 PSIoff009 PSIoff011 PSIqnh001 PSIrad003 PSIrad004 PSIrad005 PSIrad006 PSIrad007 PSIrad008 PSIrad009 PSIrad010 PSIrad011 PSIrad012 A#12845
E.2
PST ERs
The following list specifies the ERs generated by PST: SSTaso001 SSTaso003 SSTaso005 E-1
SSTaso007 SSTaso009 SSTaso011 SSTaso012 SSTaso013 SSTcen001 SSTcen002 SSTcfd001 SSTcfs001 SSTcop001 SSTcor001 SSTcor002 SSTcpa001 SSTgfi001 SSToff001 SSToff003 SSToff005 SSToff007 SSToff009 SSToff011 SSTrad003 SSTrad004 SSTrad005 SSTscv001
E-2
Appendix F : WINDOWS DESCRIPTION

Windows Description
F.1
WINDOWS DESCRIPTION
In this section the general characteristics, common to every PSI's new function windows specified in the version 3.5, are described . Here in after the different characteristics and operation form for the different elements, which could be included in the windows are introduced.
F.2
Kind of windows
Main windows: it is associated to the request of any PSI's function, it displays the necessary information for his execution. Acknowledge windows: validation from the operator is needed to execute the function. Information windows: operator receives information about the efective execution of the function
The following kind of windows could be found in PSI:
Error windows: operator receives information about problems while execution of the function.
F.3
F.3.1
Aspect and common elements of the windows

Size
The windows will have some fixed size areas (dimensioned areas ) and other configurable/adaptable data presentation area (scalable areas). In any case the width will be fixed, therefore the total width of the windows will also be fixed. The scalable areas will adapt its size to the information displayed in every case,taking a minimum height and as maximum limit the size of PSI' screen. If this limit is surpassed a vertical scroll bar will appear. F.3.2 External frame
It will determine the environment for the window, having the following characteristics: F.3.2.1 Thickness: [completed by an exemple from INDRA] Colour:[completed by an exemple from INDRA] View Frame
The different elements associated to window and described in the next sections will be allocated here. Background window's colour will be [completed by an exemple from INDRA]
Figure: Window's frame, View Frame and Title Bar. F.3.2.2 Title bar F-1
It will have the following characteristics: Height:[completed by an exemple from INDRA] Colour: [completed by an exemple from INDRA] Text: it will be centred in the title bar and it will be configurable selon PSI's profile for every function's windows, being asociated to the function or subfunction which displays it; for acknowledge, information and error window it will be "Confirmation", "Information" and "Error" respectively. Window's Control buttons will not be displayed on this bar. Source colour will be white, and the size and kind of letter [completed by an exemple from INDRA]
Figure: Title bar Note: Version 3.5 will not allow to configure the title.
F.4
F.4.1
Unitary Component
Non selective text
View frame from PSI's windows will consist of the following unitary components.
It will be displayed with white source over the window background the text intended to organize and identify the different elements which compose the window or the way to operate over it. F.4.2 Non selective graphics, lines and box
It will allow to organise the window and to diplay graphic information. [ completed by an exemple from INDRA , it will also be shown catalogue Non selective graphics, lines and box].
Figure: non selective Box and Text. F.4.3 Sensitive box
Determined areas from window which will contain texts. It would be possible to select/deselect it. If this box are selected there will be a change in the information displayed by the window or it will be possible to run some action over the selected element. F.4.3.1 F-2 Appearence Frame: [completed by an exemple from INDRA] Software Requirements Description
It will have the following characteristics:
Colours: [completed by an exemple from INDRA]. Another criteria could be used if it is explicitly shown ( for instance to indicate state from PSI's elements called in the real Sensitive Box )
F.4.3.2
Procedures
By clicking with left button of the pointer device box will be selected/deselected.
Figure: Selective box no selected
Figure: Selective box selected F.4.4 Toggle
Determined areas from window which will contain texts. It would be possible to mark/demark it. If an area is marked it means that has been included in any configuration.It will consist of an identification (non selective text or selective box ), and selective mark box. F.4.4.1 Appearance
Non selective text characteristics are indicated in 13.3.1 section. Selective box characteristics are indicated in 13.3.3 section. Selective mark box [completed by an exemple from INDRA] F.4.4.2 Procedures
By clicking with left button of the pointer device on the selective mark box it will be manually marked/ no marked. To mark/ no mark automatically look for 13.4.2, 13.5 and 13.6.1 section. When the area has been marked selective area aspect will not be modified.
Figure: Selective mark box manually marked F.4.5 Combo box
Determined areas from window which will contain a selective box where the selected value and an arrow are displayed. This component will allow to select between several options predefined in a menu. F.4.5.1 Appearance
The characteristics in the selective box are the indicated in the 14.3.3 section F.4.5.2 Procedures
The option menu will be dropped-down clicking the left button of the pointer device on the combo box. The dropped-down menu will be a list or calendar which will consist of the selected box containing the value shown Software Requirements Description F-3
by the combo box, where the new value could be selected. When selecting the new value the combo box will dissapear and the new value will placed the combo box.
Figure: Not dropped-down selection menu
Figure: Dropped-down selection menu F.4.6 Related combo box
This will have the same characteristics than combo box adding that the displayed element in the menu will always be alphabetically closer to the included in the text field related to the menu. F.4.7 Spin box
Determined areas from window which will consist of a text field where the configured value will be displayed and two control buttons. Several predefined options could be selected in a menu going through every one of them. F.4.7.1 Appearance
Text field area characteristics are indicated in 13.3.8 section. F.4.7.2 Procedures
Text field area will be completed as indicated in 13.3.8 section or clicking on the control buttons what will display in the text field the discret values which could be selected from it.
Figure: Spin Box F.4.8 Text field
Determined areas from window which will consist of a box to introduce an alfanumeric value from keyboard. It could go optionally with an complementary buttons area. Keyboard values could be introduced. F.4.8.1 Appearance Frame: [completed by an exemple from INDRA] Colours: background and sources colour will be those of Sensitive box when it has not been selected, except the source of introduced characters through complementary buttons, which will be black.
It will have the following characteristics:
Figure: Empty text field The values associated to the requirements mark the minimum threshold the system will provide. F-4 Software Requirements Description
Associated to the text field area it could be a complementary buttons area. This area could gather buttons which makes easy to create a logic expresion in the text field. Logic operators introduced through those buttons will be presented with black source.
Filtro de caracteres: Pepito Y Felipito Prez Y O ( ) NO
Figure: Text field area with complementary buttons. F.4.9 Non selective text field
Information which could not be manually updated but periodically. Background colour will be the same than these of PSI's window. If has not been possible to obtain a value for this area due to being a no aplicable value for this field it will be filled with hyphens. If the value obtained for this area is equal to zero that field will be filled up with this value. The color of the source will be black.
reas de presentacin vaca reas de presentacin rellena
--123
Figure: Non selective text and Information view frame F.4.10 No sensitive and sensitive buttons Sensitive buttons will continue the guideline indicates for the sensitive box ( see 13.3.3). The no sensitive buttons will have a thiner frame than the other and a black color source.
Implantar
Salir
Figure: Sensitive and no sensitive buttons F.4.11 Auxiliar Information Combo Box These components will always be related to other components in the window, generally with non selective graphics. The function performed will be to display aditional information to this displayed in it associated component, for instance, to display numeric values from the graphics to which are associated these auxiliar information combo box. This information will be gathered in a little non selective box. These components will not always appears, it means that it will be displayed by clicking with right button of the pointer device. The component to which is associated will have some characteristics allowing to know the existence of the auxiliar information combo box. The auxiliar information combo box is composed by simpler component: non selective text and information view frame.
F.5
String list
F-5
It could be scalable areas if the operative context allow it, the string list will gather by rows unitary elements belonging to the same cathegory. These elements in the same category could also be gather by colums, exceptionally. At the end of the list it could be included edition elements which with the selective buttons related to the list will allow to develop the posible operations over it. The list could have more than one column, acting like if it were an unic block for doing its own operations. F.5.1 Appearance
The list will be framed by a non selective box. It will have the following characteristics: Width: fix and adapted to the displayed information Frame: separating the list from the other areas
It will consist of a column groups with the following unitary components: F.5.2 non selective box (see 13.3.2) non selective text (see 13.3.1) Toggle (see 13.3.4) Combo Box (see 13.3.5) Spin Box (see 13.3.7) Text field (see 13.3.8) Procedures
The lists could have edition areas at the bottom, which will have the kind of components indicated in the 13.4.1 section and selective or non selective buttons and ordering buttons. The following specific operations could be done: Table: Specific operation which could be done
F.6
Tree list
With the intention of simultaneally display associated configuration to diferent components in a display control list, it could be defined tree list associated to display control list ( it could have more than one colum) which will have the following characteristics: it will be displayed in every view frame controlled by a display control list every row will be related to another row from the display control list so the selection, indivual rearrangement, and arrangement order will apply to each one as for this last. if the associated list would have been formed by text field, it would be possible to try to change some of these areas without have been selected the correspondent component in the display control list, it is against the operation way defined for the display control list to input or modify configurations.To avoid it the tree list will be constitute by non selective text and any modification in the tree list will be developped through edition areas related to the list. Table: Specific operation which could be done
F-6

Operation Select Inputs Availability Associated Elements Selective mark box Always and sensitive button Select alls associated to the list. Functionality Select with the left button of the pointer device the selective mark box associated to the element of the list that we want to include or exclude. With the specific Sensitive button, associated to the list, all the input could be selected one by one or several columns in the same. In the edition area the new input is entered and the button New will be clicked. Note: the element of edition of the list will have the same content than the element of the associated list which has been selected while it is not modify. The sensitive box of the row to delete will be selected and the Delete button will be clicked. The selective box from the row which are going to be modify will be selected, the contain in the edition area will be changed and the button Modify will be clicked.
DESCRIPTION
Include o exclude an element of the associated list in the configurations which has been performed.
Add Inputs
Create a new input Element of the edition in the associated area and the sensitive list. button New associated to the control display list to which is associated.
Delete Inputs
Modify inputs (edition area)
Delete an input in Sensitive box of the the associated list. control display list and the sensitive button Delete associated to the control display list. Modify through Sensitive box of the the edition area a control display list new input in the and the sensitive associated list. button Modify associated to the control display list
Individually As lists. reorganize inputs Organize all As lists. the inputs
As lists. As lists.
If it is a compulsory configuration in the edition area associated it has to be filled with an aceptable value in the list. One of the elements in the associated list has to be selected One of the elements in the associated list should be selected and has to be changed the content in the edition area. As lists. A s lists.
As lists.
As lists.
F.7
Embeded presentation area
With the intention of decreasing displayed information for a single window and organising properly the information, it will be allowed embeding diferent view frames in a piece structure. A display control area should exist for being able of doing the embeded. By selecting the components in the display control area it will be defined the embeded presentation area diplayed at every moment. In this embeded presentation area we will have compulsory configuration elements at optional elements. The presentation control area and its embeded presentation area will be framed by a non selective frame. F.7.1 Control display area
We will distinguish two kind of control display area: F.7.1.1 Control display list
1. Control display list It will be single column list which will consist of unitary components belonging to the same category. It is placed on left side of embeded presentation areas. Control display list will be framed by a non selective box. It will have the following characteristics: Width: fix and adapted to the displayed information Frame: separating the list from the other areas
It will consist of a column groups with the following unitary components: non selective box (see 13.3.2) non selective text (see 13.3.1) Toggle (see 13.3.4) Combo Box (see 13.3.5) Spin Box (see 13.3.7) Text field (see 13.3.8)
Non selective and selective buttons will be used to work on these control display list, usually placed in rows below the list, though due to space problems it could also be placed as columns.
F-7
Inside the embeded presentation area could exist several compulsory configuration associated to a component from the control display list, which will prepare the behaviour and the operating way for the actions to develop, so it should be specified for every component in the control list which configuration are compulsory. Table: The following specific action could be execute
Operation Select Inputs
DESCRIPTION
Include o exclude an element of the associated list in the configurations which has been performed.
Availability Associated Elements Selective mark box Always and sensitive button Select alls associated to the list.
Functionality Select with the left button of the pointer device the selective mark box associated to the element of the list that we want to include or exclude. With the specific Sensitive button, associated to the list, all the input could be selected one by one or several columns in the same. In the edition area the new input is entered and the button New will be clicked. Note: the element of edition of the list will have the same content than the element of the associated list which has been selected while it is not modify. The sensitive box of the row to delete will be selected and the Delete button will be clicked. The selective box from the row which are going to be modify will be selected, the contain in the edition area will be changed and the button Modify will be clicked.
Add Inputs
Create a new input Element of the edition in the associated area and the sensitive list. button New associated to the control display list to which is associated.
Delete Inputs
Modify inputs (edition area)
Delete an input in Sensitive box of the the associated list. control display list and the sensitive button Delete associated to the control display list. Modify through Sensitive box of the the edition area a control display list new input in the and the sensitive associated list. button Modify associated to the control display list
Individually As lists. reorganize inputs Organize all As lists. the inputs
As lists. As lists.
If it is a compulsory configuration in the edition area associated it has to be filled with an aceptable value in the list. One of the elements in the associated list has to be selected One of the elements in the associated list should be selected and has to be changed the content in the edition area. As lists. As lists.
As lists.
As lists.
F.7.1.2
Always visible horizontal taps
It will be taps on selective box belonging to the same category. It is placed on its controlled embeded presentation area. Due to limitations in taps, it will be used just if all the embeded presentation area are included in the configuration and the mandatory fields in every one of them are always filled ( for instance Operational Configuration) It would be possible to work on taps for display control. The visible embeded presentation area will change if any tap is selectionated. The selection of a new tap will mean automatically de-select the one selected. There always be some taps selected. [INDRA will shown tap format selected and no selected] F.7.2 Embeded presentation area
It will have the same characteristics than a view frame and it will be controlled by a display control area . This embeded presentation area could have inside other display control area with its correspondent embeded presentation area, establishing a hierarchy (primary, secondary, tertiary) inside the embeded presentation area. Inside this areas it could be several compulsory configuration which will prepare the behaviour of the control display area to which are associated.
F.8
Acknowledge window
F-8
These windows will have the general characteristics defined for all the windows and a non selective text will be displayed requering acknowledge to run a function. The sensitive buttons associated will be 'Accept' (which confirm the execution of the function) and 'Cancel' (which cancel the execution of the function).
F.9
Information window
These windows will have the general characteristics defined for all the windows and a non selective text will be displayed confirming the execution of a function. The only selective button associated will be "Accept" (which close the information window).
F.10 Error window

These windows will have the general characteristics defined for all the windows and a non selective text will be displayed informing about problems while the execution of the function. Depending on the kind of error two sensitive buttons could be displayed, "Accept" (which confirm the execution of the function despite of the possible problems) and "Cancel" (which cancel the execution of the function).
F.11 Operational capacity

A set of general operative procedures are described in this paragraph, which will be applied to all the windows displayed in the PSI. F.11.1 Function Execution Errors The buttons to Analize will be eliminate and any error in the data introduced in the window will be notify through an error window while trying to run a function. F.11.2 Execution of a function An acknowledge window will be displayed before executing any function. If the action is confirmed in the acknowledge window, the acknowledge window will be closed and the main window, displaying nextly an information window about the accomplished action. If the action in the acknowledge window is refued, the acknowledge window will be closed but the main window will keep open. F.11.3 Action on windows through keyboard The Enter could be used to run functions. The Enter could be used to add enters to a list after introducing the name ( equivalent to click 'New') F.11.4 Displacement inside the window Using the tab to move between selective fields, in the windows where it is concretely indicate ( It should take in account that the tab will never jump between different view frames and it will not apply in the lists). The tab will be in the button 'Execute' or 'Accept' by default. F.11.5 'Multiple-Request' Windows The 'multiple-request' window are those windows which allow to open more than one request (with some restrictions). Hereinafter several particularities which we can found in the 'multiple-request' windows and the special operative of these windows: Characteristics: - These windows will have a primary control display list. - It will be possible to open as many 'Multiple-request' windows as elements compose the primary control display list. Note: If those 'elements' are processors it will be a limit to open a maximum of 10 windows (developpement problems). Nevertheless, by the moment, that limit will be taken in account and it is not requested to eliminate or augment it. -It is not possible to have to windows opened with the same selected item in the primary control display list. Operative: - If the window is requested from the function menu bar, the element in the primary control display list which will appear selected by default will be the first which are 'free' (there are not another window with the same kind of statistics open with that element selected). Software Requirements Description F-9
- If the window is requested from the contextual menu of any element in the primary control display list, a window with that element selected in the primary control display list will be opened. - If there are an open window with the element 'x' selected in the primary control display list and a second window will be selected, again, that element 'x', the first mentioned window will be closed. It means, the window over which the element 'x' is being selected will remain open and it will pass to display information over that element in the embeded information presentation area and it will close automatically the other window. - Except for these particularities, the rest of the window will have an operative like described in this document. Note: In the 3.5 SACTA version, there will be 'Multiple-request' windows only for statistics windows.
F-10
This is the last page
F-1

SRD Psi V03.X5.10

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SRD Psi V03.X5.10

Caricato da

Copyright:

Formati disponibili

SACTA 3.

PROJECT: SACTA 3.5 EXTENDIDA

APPROVED / QA Ana I. Moreno Alcntara

PROJECT: SACTA 3.5 EXTENDIDA Date:

NAME AND SURNAME

Aena Aena Indra

DIV. AUTOMATIZACIN DIV. AUTOMATIZACIN Programas Europeos ATM

ID Doc: SPSIHMER3I.016 PROJECT: SACTA 3.5 EXTENDIDA

Edition: Revision: Date:

PAGE EDITION AND REVISION RECORD

B-1 a B-8 C-1 a C-2 D-1 a D-2 E-1 a E-2

DOCUMENT CHANGES RECORD

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

INDEX OF TABLES Software Requirements Specification i

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

SACTA 3.5 EXTENDIDA SRD

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Software Requirements Specification

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

SACTA 3.5 EXTENDIDA SRD

Page intentionally left blank

Software Requirements Description

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Software Requirements Specification

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

SACTA 3.5 EXTENDIDA SRD

Software Requirements Description

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Software Requirements Specification

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Page intentionally left blank

Software Requirements Specification

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Software Requirements Specification

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

SACTA 3.5 EXTENDIDA SRD

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Figure 3.2-1 : Sw Environment

Software Requirements Specification

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

SACTA 3.5 EXTENDIDA SRD

Page intentionally left blank

Software Requirements Description

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

Software Requirements Specification

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07

SACTA 3.5 EXTENDIDA SRD

Physical States Device Element Type

Logical and Other States

Physical States Device Element Type

Logical and Other States

Software Requirements Description

SACTA 3.5 EXTENDIDA SRD

Id. Doc: SPSIHMER3I.016 Edition: 3 Revision: 0 Date: 22/10/07