SAM/IG/2 WP/10 30/10/08...SAM/IG/2 WP/10 - 2 - 1.3 Automation activities carried out by Project...

SAM/IG/2 WP/10

30/10/08

International Civil Aviation Organization

South American Regional Office

SECOND WORKSHOP/MEETING OF THE SAM IMPLEMENTATION GROUP (SAM/IG/2) REGIONAL PROJECT RLA/06/901

Lima, Peru, 3 to 7 November 2008

Agenda Item 6: Operational implementation of new ATM automated systems and integration of the existing systems

RESULT OF THE WORK CARRIED OUT BY PROJECT RLA/06/901 WITH REGARD TO AUTOMATION

(Presented by the Secretariat)

Summary

This working paper presents the results of the work carried out by Project RLA/06/901 with regard to activities of this project, and proposed some actions to initiate implementation of interconnection of automated systems in the SAM Region.

References: • Report of the SAM/IG/1 Meeting ICAO Strategic objective: D: Efficiency

1 Introduction 1.1 Objective No. 3 of Regional Project RLA/06/901 establishes the tasks to be carried out for the operational implementation of new ATM automated systems and the interconnection of existing automation systems in the Region. 1.2 The activities related with operational implementation of new ATM automated systems and the integration of the existing ones, were initiated with Project RLA/98/003.

SAM/IG/2 WP/10 - 2 -

1.3 Automation activities carried out by Project RLA/98/003 basically consisted in the preparation of a questionnaire which permitted to know automated systems installed in ATS units and their interphases in the CAR/SAM Regions, the implementation of an interconnection trial between automated systems of the Manaus ACC (Amazonica FIR) in Brazil, and the Maiquetía ACC (Maiquetía FIR) in Venezuela, missions to States for data collection, in order to evaluate the current situation of automated systems in the ACCs of the CAR/SAM States, the preparation of an System Interphase Control Document (SICD) and the preparation of a CAR/SAM Initial Interconnection Plan of Automated Systems. 1.4 The First Workshop/Meeting of the SAM Implementation Group (SAM/IG/1) held in Lima, Peru, from 21 to 25 April 2008, analysed the automation activities carried out by Project RLA/98/003 and formulated an action plan for the interconnection of automated systems, which is presented as Appendix A to this working paper. 1.5 In order that States of the Region implement the activities described in the action plan SAM/IG/1 Meeting formulated Conclusion SAM/IG/1-7 Adoption of the Action Plan for the regional interconnection of automated systems. 1.6 SAM/IG/1 Meeting also considered that within the automation activities, a model document of requirements of the SAM Automation System, which contains the common basic functionalities and may be used as reference for the acquisition of new systems and modification of the existing systems. 2 Analysis 2.1 The interconnection of automated systems in the SAM Region is foreseen to be executed through the implementation of bilateral agreements between States having adjacent ACCs. The interconnection, as per the action plan (See Appendix B of this working paper) would be made in phases, taking into account the current degree of automation in the ACCs of the Region. 2.2 The interconnection of automated systems consists in the implementation of the exchange of information of flight plans and radar data between two States having adjacent ACCs in the Region. Interconnection of information of flight plans between automated ACCs in the SAM Region 2.3 The action plan for the interconnection of automated systems contemplates for the exchange of flight plans between adjacent automated ACCs in the SAM Region, the implementation in a short term of the following existing applications: OLDI, automated messages of ICAO Doc 4444, and AIDC application. Implementation of the interconnection of flight plans through OLDI 2.4 As per the information collected by Project RLA/98/003 as regards activities of automation, the ACCs of the Region presenting capacity for the OLDI are: Argentina, Chile, Colombia, Ecuador, Panama and Uruguay.

SAM/IG/2 WP/10

- 3 -

2.5 Most of the ACCs mentioned in the above paragraph present the basic characteristics of the OLDI, but the same is not used. The difficulty in using it mainly consists in configuration of the automation system as necessary, as well as the apparent differences in the implementation of the protocol by systems providers. 2.6 In order to implement the interconnection of the OLDI application, between States adjacent ACCs, mentioned above, as specified in the action plan, it is necessary that the indicated States express in first place their will to proceed to the implementation of the OLDI between adjacent ACCs of the Region. 2.7 Once it has been established which States wish to implement the interconnection of the OLDI application, it will first be necessary to proceed to a complete evaluation of the existing OLDI systems in each one of the interested States of the Region, determine the minimum configuration of OLDI messages to implement and verify consideration of local and regional communications for the interconnection of OLDI applications, prepare technical specifications that enable implementation of the interconnection of OLDI systems, proceed to a process of price consultation, analyse the approval of the acquisition and if feasible, proceed to the cancelation of necessary fees for each one of the States involved in the current project for its implementation. 2.8 The implementation of the interconnection of the OLDI application for more than 2 States should be more economical than implementing the OLDI interconnection between two States in an independent manner. Implementation of interconnection of automated flight plans through messages specified in Doc 4444 PANS/ATM 2.9 Some ATC systems make use of the message coordination (CDN, LAM, ACP), as specified in Doc 4444 – PANS/ATM for the coordination of flight plans between adjacent ACCs, being this the specific case of Brazil. 2.10 Venezuela has also the capacity to coordinate through Doc 4444, PANS/ATM messages and even though it has not been used at an operational level, this characteristic has been subject to the demonstration of possibility during the trials of interconnection conducted between Amazonica FIR and Maiquetía FIR, carried out under Project RLA/98/003. 2.11 To this respect, it is necessary that the aeronautical Administrations of Brazil and Venezuela proceed to the operational implementation of interconnection of flight information through messages specified in Doc 4444. Implementation of interconnection of automated systems through the application of AIDC 2.12 Currently, only Argentina counts with the application of AIDC. The same is installed in the Ezeiza and Cordoba ACCs. The interconnection of this application between the Ezeiza and Cordoba ACC is being tested. It is expected that by mid November 2008, such application is in operation between the ACCs mentioned. The application of AIDC will run over an AMHS message network implemented over an IP network. It is also expected that during the meeting, detailed information be presented on the works carried out on this respect.

SAM/IG/2 WP/10 - 4 -

Radar data interconnection between SAM Region adjacent automated ACCs 2.13 Based in radar surveillance systems installed in the SAM Region, the action plan contemplates for the radar data interconnection between automated adjacent ACC the following cases: inter-centres surveillance data interconnection using Asterix 62/63 protocol, surveillance data interconnection using Asterix ICD, and surveillance data interconnection using ICD owner. 2.14 To implement radar data interconnection proposed in the action plan it is suggested that this be executed once flight plans interconnection is implemented. 2.15 For the execution of radar data interconnection it is suggested that this is done bilaterally, such as indicated in the action plan. In order to initiate the implementation, it is important, as first step, that the Project elaborates a format of memorandum of understanding that contains technical, administrative and institutional requirements necessary to carry out the radar data interconnection between two States. SAM Automation System Requirements Document 2.16 Following activities planned during SAM/IG/1 Meeting, the project elaborated a preliminary document on SAM Automation System Requirements for the SAM Region, which contains basic operations that are common to automated Systems of the SAM Region ACCs. 2.17 The elaborated document, which is being presented as Appendix B to this working paper, represents a preliminary document which once reviewed by the States of the Region could be used as reference for the purchase of new systems and for the modification of existing automated systems. 3 Conclusions 3.1 It is suggested that for the interconnection of SAM Regional automated systems works be initiated with the initial implementation of flight plans interconnection. To carry out the implementation of the OLDI interconnection, it is suggested to hire an expert to elaborate the necessary technical specifications. 3.2 The expert for the elaboration of technical specifications will analyse the SICD document (Interface Control System) prepared by project RLA/98/003 and will visit, if necessary, each State of the Region interested in the interconnection of the OLDI application in order to determine all technical and operative requirements necessary to complete the technical specifications document. 3.3 Having in consideration the positive results of the trials on automated messages exchange of Doc. 4444 carried out between the ACCs of Manaus and Maiquetia, it is necessary that the Aeronautical Administrations of Brazil and Venezuela proceed to put in operation this application. 3.4 Likewise, once completed the implementation of AIDC application in the ACCs of Ezeiza and Cordoba, as well as the interconnection between these two ACCs, that the Aeronautical Administration of Argentina prepares guidelines including the considerations to be followed when interconnecting the AIDC application between both ACCs.

SAM/IG/2 WP/10

- 5 -

3.5 It is suggested that the interconnection of radar data between adjacent ACCs of the SAM Region be implemented once the applications of flight plans information exchange is completed. 3.6 It is suggested that the radar data exchange of States involved be done bilaterally and, as first step, the project elaborates a format of memorandum of understanding containing technical, administrative and institutional elements necessary to implement the radar data interconnection. 3.7 States should analyze the preliminary document of SAM Automation System Requirements in order to be able to use it in the Region as guiding material to implement new automation Systems in the Region ACCs. 4 Suggested actions 4.1 The Meeting is urged to:

a) take note of the information being presented b) analyse automated systems interconnection implementation considerations for

the flight plans exchange described in section 2 of paragraphs 2.3 to 2.12, and in section 3, from paragraph 3.1 to 3.4

c) analyse radar data interconnection considerations described in section 2 paragraphs 2.13 to 2.15, and in section 3, paragraphs 3.4 and 3.5

d) analyse the preliminary SAM automation system requirements document being presented as Appendix B to this working paper

e) analyse any other aspect related to this issue considered necessary by the Meeting.

ID Nome da tarefa Duration Start Finish

1 CAR/SAM Interconection Plan 1425 days Mon 21/04/08 Fri 04/10/132 Plan Approval 160 days Mon 21/04/08 Fri 28/11/083 Plan Presentation in the 1ª GT CNS/ATM SAM-ATM/CNS/IG 1

Meeting5 days Mon 21/04/08 Fri 25/04/08

4 Plan Presentation ATM/CNS/SG/6 5 days Mon 30/06/08 Fri 04/07/08

5 Plan presentation in the GREPECAS Meeting 5 days Mon 13/10/08 Fri 17/10/08

6 CAR/SAM interconnection plan Approval 30 days Mon 20/10/08 Fri 28/11/08

7 Project Managing Board Creation 90 days Mon 01/12/08 Fri 03/04/09

8 Project Organization 22 days Mon 06/04/09 Tue 05/05/099 Managing plan 22 days Mon 06/04/09 Tue 05/05/09

10 Communication Plan 22 days Mon 06/04/09 Tue 05/05/09

11 Human resources Plan 22 days Mon 06/04/09 Tue 05/05/09

12 Cost Plan 22 days Mon 06/04/09 Tue 05/05/09

13 Risk Assesment Plan 22 days Mon 06/04/09 Tue 05/05/09

14 Escope Managing Plan 22 days Mon 06/04/09 Tue 05/05/09

15 Quality plan 22 days Mon 06/04/09 Tue 05/05/09

16 Procurement and Acquisition plan 22 days Mon 06/04/09 Tue 05/05/09

17 Plan execution 1330 days Mon 01/09/08 Fri 04/10/1318 STARTUP MEETING 2 days Mon 02/03/09 Tue 03/03/09

19 Coordination Meetings 940 days Fri 04/09/09 Thu 11/04/1320 1 Coordination Meeting 2 days Fri 04/09/09 Mon 07/09/09

21 2 Coordination Meeting 2 days Thu 11/03/10 Fri 12/03/10

22 3 Coordination Meeting 2 days Wed 15/09/10 Thu 16/09/10

23 4 Coordination Meeting 2 days Tue 22/03/11 Wed 23/03/11

24 5 Coordination Meeting 2 days Mon 26/09/11 Tue 27/09/11

25 6 Coordination Meeting 2 days Fri 30/03/12 Mon 02/04/12

26 7 Coordination Meeting 2 days Thu 04/10/12 Fri 05/10/12

27 8 Coordination Meeting 2 days Wed 10/04/13 Thu 11/04/13

28 Institutional/Legal Documents Creation 120 days Mon 02/03/09 Fri 14/08/0929 Responsability definition over Shared Resources 22 days Mon 02/03/09 Tue 31/03/09

30 Operational Agreements Between States 60 days Mon 02/03/09 Fri 22/05/09

31 Surveilance Area definition to be shared 90 days Mon 02/03/09 Fri 03/07/09

32 Security Plan 120 days Mon 02/03/09 Fri 14/08/09

33 Flight Plan Interconection Implementation 434 days Mon 01/09/08 Thu 29/04/1034 Flight Plan interconnection using OLDI 304 days Mon 02/03/09 Thu 29/04/1035 First Phase 198 days Mon 02/03/09 Wed 02/12/09

Oct Mar Aug Jan Jun Nov Apr Sep Feb Jul Dec May Oct Mar Aug Jante 1st Quarte 1st Quarte 1st Quarte 1st Quarte 1st Quarte 1st Quarte 1st

Tarefa

Divisão

Andamento

Etapa

Resumo

Resumo do projeto

Tarefas externas

Etapa externa

Prazo final

APÉNDICE A/APPENDIX A SAM/IG/2 - NE10/WP10A-1

Página 1

Projeto: SAM1GNE19ApnCData: Thu 30/10/08


36 EZEIZA-MONTEVIDEO 22 days Mon 02/03/09 Tue 31/03/09

37 EZEIZA-CORDOBA 22 days Wed 01/04/09 Thu 30/04/09

38 EZEIZA-SANTIAGO 22 days Fri 01/05/09 Mon 01/06/09

39 BOGOTÁ-GUAYAQUIL 22 days Tue 02/06/09 Wed 01/07/09

40 BOGOTÁ-PANAMÁ 22 days Thu 02/07/09 Fri 31/07/09

41 BOGOTÁ-BARRANQUILHA 22 days Mon 03/08/09 Tue 01/09/09

42 BARRANQUILHA-PANAMÁ 22 days Wed 02/09/09 Thu 01/10/09

43 SANTIAGO-CORDOBA 22 days Fri 02/10/09 Mon 02/11/09

44 PANAMÁ-CENAMER 22 days Tue 03/11/09 Wed 02/12/09

45 Second Phase ( With Brazil) 44 days Mon 01/03/10 Thu 29/04/1046 CURITIBA-URUGUAI 22 days Mon 01/03/10 Tue 30/03/10

47 AMAZÔNICO-BOGOTÁ 22 days Wed 31/03/10 Thu 29/04/10

48 Flight Plan interconnection using Doc 4444 (CDN,LAM,ACP)

60 days Mon 01/09/08 Fri 21/11/08

49 MAIQUETIA - AMAZONICO Interconnection Comissioning 60 days Mon 01/09/08 Fri 21/11/08

50 Flight Plan interconnection using AIDC 22 days Mon 01/03/10 Tue 30/03/1051 BRASIL-ARGENTINA 22 days Mon 01/03/10 Tue 30/03/10

52 Surveillance Data interconnection Implementation 1330 days Mon 01/09/08 Fri 04/10/1353 Surveillance Data interconnection Implementation using

Intercenter ASTERIX 62/63304 days Mon 02/03/09 Thu 29/04/10

54 EZEIZA-MONTEVIDEO 22 days Mon 02/03/09 Tue 31/03/09

55 BRASIL- MONTEVIDEO 44 days Mon 01/03/10 Thu 29/04/10

56 Surveillance Data interconnection Implementation withProprietary ICD

60 days Mon 01/09/08 Fri 21/11/08

57 AMAZONICO-MAIQUETIA 60 days Mon 01/09/08 Fri 21/11/08

58 Surveillance Data interconnection Implementation usingASTERIX Radar ICD

352 days Wed 01/07/09 Thu 04/11/10

59 EZEIZA-SANTIAGO 22 days Wed 01/07/09 Thu 30/07/09

60 EZEIZA-CORDOBA 22 days Fri 31/07/09 Mon 31/08/09

61 EZEIZA- MONTEVIDEO 22 days Tue 01/09/09 Wed 30/09/09

62 AMAZÔNICO-BOGOTÁ 22 days Thu 01/10/09 Fri 30/10/09

63 CURITIBA-MONTEVIDEO 22 days Mon 02/11/09 Tue 01/12/09

64 SANTIAGO-CORDOBA 22 days Wed 02/12/09 Thu 31/12/09

65 BOGOTÁ-GUAYAQUIL 22 days Fri 01/01/10 Mon 01/02/10

66 BOGOTÁ-PANAMÁ 22 days Fri 01/01/10 Mon 01/02/10

67 BOGOTÁ-BARRANQUILHA 22 days Tue 02/02/10 Wed 03/03/10

68 BOGOTÁ-MAIQUETIA 22 days Thu 04/03/10 Fri 02/04/10


Tarefa

Divisão

Andamento

Etapa

Resumo

Resumo do projeto

Tarefas externas

Etapa externa

Prazo final


Página 2



69 BOGOTÁ-LIMA 22 days Mon 05/04/10 Tue 04/05/10

70 PANAMÁ-CENAMER 22 days Wed 05/05/10 Thu 03/06/10

71 CORDOBA-EZEIZA 22 days Fri 04/06/10 Mon 05/07/10

72 MAIQUETIA-BARRANQUILHA 22 days Tue 06/07/10 Wed 04/08/10

73 BARRANQUILHA-PANAMÁ 22 days Thu 05/08/10 Fri 03/09/10

74 BARRANQUILLA-MAIQUETIA 22 days Mon 06/09/10 Tue 05/10/10

75 MAIQUETIA-PIARCO 22 days Wed 06/10/10 Thu 04/11/10

76 Surveillance Data interconnection Implementation usingRADNET for the CAR/SAM Region

440 days Tue 01/03/11 Mon 05/11/12

77 Specification 44 days Tue 01/03/11 Fri 29/04/11

78 Acquisition 132 days Mon 02/05/11 Tue 01/11/11

79 Installation 264 days Wed 02/11/11 Mon 05/11/12

80 Telecommunication infrastructure Coordination 1200 days Mon 02/03/09 Fri 04/10/13

81 Surveillance Data interconnection Implementation usingSISTRASAG

100 days Mon 02/03/09 Fri 17/07/09

82 BRASIL 30 days Mon 02/03/09 Fri 10/04/09

83 LIMA 10 days Mon 13/04/09 Fri 24/04/09

84 LA PAZ 10 days Mon 27/04/09 Fri 08/05/09

85 ASSUNCION 10 days Mon 11/05/09 Fri 22/05/09

86 GEORGETOWN 10 days Mon 25/05/09 Fri 05/06/09

87 PARAMARIBO 10 days Mon 08/06/09 Fri 19/06/09

88 ROCHAMBEAU 10 days Mon 22/06/09 Fri 03/07/09

89 RESISTENCIA 10 days Mon 06/07/09 Fri 17/07/09


Tarefa

Divisão

Andamento

Etapa

Resumo

Resumo do projeto

Tarefas externas

Etapa externa

Prazo final


Página 3


SAM/IG/2NE-WP/10

B-1

APENDICE B / APPENDIX B

Preliminary

Reference System/Subsystem Specification

for the

Air Traffic Control Automation System

Prepared by: SAM Automation Team

SAM/IG/2 WP-NE/10

B-2

2

SSS SIGNOFF SHEET

Responsible Person Signature Date

Onofrio Smarrelli ____________________ __________ OACI Program Manager

Antonio Marcos C. Fonseca ____________________ __________ Systems Engineer

Luiz Antonio G. de Oliveira ____________________ __________ Telecommunication Engineer

SAM/IG/2NE-WP/10

B-3

Change Record

Rev Description of Change Page No's

Affected Date

- Initial Release All 22 Sept 2008

A Preliminary Release All 04 Oct 2008

SAM/IG/2 WP-NE/10

B-4

Summary

AIR TRAFFIC CONTROL AUTOMATION SYSTEM................................................... 1

PREPARED BY:........................................................................................................... 1

SSS SIGNOFF SHEET ................................................................................................ 2

CHANGE RECORD ..................................................................................................... 3

TABLE LIST ................................................................................................................. 8

FIGURE LIST ............................................................................................................... 9

1. SCOPE ............................................................................................................. 10

1.1 Identification.............................................................................................................................................. 10

1.2 System Overview ....................................................................................................................................... 11 1.2.1 Introduction............................................................................................................................................. 11 1.2.2 Context Diagram..................................................................................................................................... 12

FIGURE 1.1 – CONTEXT DIAGRAM FOR ATCAS .................................................. 12 1.2.3 Component and External Interfaces ....................................................................................................... 12

1.2.3.1 Components ................................................................................................................................... 12 1.2.3.2 External Interfaces ......................................................................................................................... 13 1.2.3.3 System Features ............................................................................................................................. 14

1.3 Document Overview.................................................................................................................................. 14 1.3.1 Document Conventions .......................................................................................................................... 15

2. REFERENCED DOCUMENTS......................................................................... 16

3. REQUIREMENTS............................................................................................. 18

3.1 Required States and Modes...................................................................................................................... 18

3.2 System Capability Requirements ............................................................................................................ 18 3.2.1 Man-Machine Interface .......................................................................................................................... 18

3.2.1.1 Graphic Interface ........................................................................................................................... 18 3.2.1.1.1 Predicted Position Indicator..................................................................................................... 18 3.2.1.1.2 Functional Controls.................................................................................................................. 18 3.2.1.1.3 Radar Coverage Diagrams and Color Assignment ................................................................. 19 3.2.1.1.4 Screen Annotation.................................................................................................................... 19 3.2.1.1.5 Windows Presentation ............................................................................................................. 19 3.2.1.1.6 Images ...................................................................................................................................... 20 3.2.1.1.7 Surveillance Data Display Elements ....................................................................................... 21 3.2.1.1.8 Surveillance Data Position Symbols........................................................................................ 22 3.2.1.1.9 Track History Information ....................................................................................................... 22

SAM/IG/2NE-WP/10

B-5

3.2.1.1.10 Display Range ........................................................................................................................ 22 3.2.1.1.11 Range Rings ........................................................................................................................... 22 3.2.1.1.12 Quick Look............................................................................................................................. 22

3.2.1.2 Range Bearing Line ....................................................................................................................... 23 3.2.1.3 Smart Labels .................................................................................................................................. 23

3.2.1.3.1 Controller Jurisdiction Indicator (CJI) .................................................................................... 23 3.2.1.3.2 Special Position Indicator (SPI)............................................................................................... 23

3.2.1.4 Filters ............................................................................................................................................. 24 3.2.1.5 Maps............................................................................................................................................... 24

3.2.1.5.1 Weather Surveillance Data ...................................................................................................... 25 3.2.1.5.2 Private Maps............................................................................................................................. 25

3.2.1.6 Flight Plan...................................................................................................................................... 25 3.2.1.6.1 Flight Strip Window................................................................................................................. 25 3.2.1.6.2 Flight Data Displays................................................................................................................. 25 3.2.1.6.3 Flight List Presentation ............................................................................................................ 26 3.2.1.6.4 Flight Strip Presentation .......................................................................................................... 26 3.2.1.6.5 General ..................................................................................................................................... 26 3.2.1.6.6 Flight Plan Data Retrieval........................................................................................................ 27 3.2.1.6.7 Repetitive Flight Plan Retrieval............................................................................................... 27 3.2.1.6.8 Flight Plan History ................................................................................................................... 27 3.2.1.6.9 Free Text Input and Distribution ............................................................................................. 27 3.2.1.6.10 RVSM..................................................................................................................................... 28 3.2.1.6.11 PBN ........................................................................................................................................ 28

3.2.2 Datalink Communication........................................................................................................................ 28 3.2.2.1 CPDLC........................................................................................................................................... 28 3.2.2.2 ADS................................................................................................................................................ 30 3.2.2.3 Notification of Error Messages ..................................................................................................... 30 3.2.2.4 Timestamps and Timers................................................................................................................. 31 3.2.2.5 AFN Logon Functions ................................................................................................................... 32

3.2.3 Surveillance Data Processing ................................................................................................................. 32 3.2.3.1 Air Situation establishment ........................................................................................................... 32 3.2.3.2 Surveillance Data Output............................................................................................................... 34 3.2.3.3 Surveillance Data Processing Capabilities.................................................................................... 34 3.2.3.4 Surveillance Presentation .............................................................................................................. 34 3.2.3.5 Surveillance Data Processing Functions ....................................................................................... 34 3.2.3.6 Direct Surveillance Access (DSA) Back-up Mode....................................................................... 35 3.2.3.7 Real-Time Quality Control (RTQC) of Surveillance Data........................................................... 35

3.2.3.7.1 Automatic Test Target Monitoring.......................................................................................... 35 3.2.3.7.2 Status Message Monitoring ..................................................................................................... 35 3.2.3.7.3 Surveillance Data Counts Monitoring ..................................................................................... 35 3.2.3.7.4 Registration Analysis ............................................................................................................... 35 3.2.3.7.5 Registration Correction............................................................................................................ 36 3.2.3.7.6 SSR Reflections ....................................................................................................................... 36 3.2.3.7.7 Altitude Processing .................................................................................................................. 36

3.2.4 Flight Plan Data Processing.................................................................................................................... 36 3.2.4.1 Flight Data Processing Functions.................................................................................................. 36 3.2.4.2 Flight Data Processing Capabilities .............................................................................................. 37 3.2.4.3 Flight Data Database...................................................................................................................... 37

3.2.4.3.1 Repetitive Flight Plan (RPL) Data........................................................................................... 37 3.2.4.3.2 AFTN/AMHS Flight Plan Data ............................................................................................... 38 3.2.4.3.3 Operator Flight Data Input....................................................................................................... 38 3.2.4.3.4 MET Data................................................................................................................................. 39 3.2.4.3.5 Input Message Processing........................................................................................................ 39

3.2.4.4 Flight Progress Processing ............................................................................................................ 39 3.2.4.5 Route Processing............................................................................................................................ 40 3.2.4.6 Secondary Surveillance (SSR) Code Allocation........................................................................... 40 3.2.4.7 Flight Plan/Track Association Function........................................................................................ 41 3.2.4.8 Sectorization .................................................................................................................................. 41

SAM/IG/2 WP-NE/10

B-6

3.2.4.8.1 Sector Reconfiguration Function............................................................................................. 41 3.2.4.9 ATFM Functions............................................................................................................................ 42 3.2.4.10 FDPS Output ............................................................................................................................. 42

3.2.4.10.1 Output of Messages to AFTN/AMHS Network.................................................................... 42 3.2.4.10.2 Flight plan Handoff................................................................................................................ 42 3.2.4.10.3 ATFM unity ........................................................................................................................... 43

3.2.5 Alerts....................................................................................................................................................... 43 3.2.5.1 Special Codes and Emergency Messages ..................................................................................... 43 3.2.5.2 Short Term Conflict Alert (STCA) ............................................................................................... 44 3.2.5.3 Minimum Safe Altitude Warning (MSAW) ................................................................................. 44 3.2.5.4 Medium Term Conflict Detection (MTCD).................................................................................. 45 3.2.5.5 Cleared Level Adherence Monitoring (CLAM) ........................................................................... 45 3.2.5.6 Route Adherence Monitoring (RAM)........................................................................................... 45 3.2.5.7 Area Infringement Warning (AIW)............................................................................................... 45 3.2.5.8 Conflict Probe ................................................................................................................................ 45 3.2.5.9 Approach Funnel Deviation Alert ................................................................................................. 45

3.2.6 Recording and Playback ......................................................................................................................... 46 3.2.6.1 Recording....................................................................................................................................... 46 3.2.6.2 Playback......................................................................................................................................... 46 3.2.6.3 Surveillance Display Playback ...................................................................................................... 47 3.2.6.4 Non-interactive Playback Mode.................................................................................................... 47 3.2.6.5 Interactive Playback Mode ............................................................................................................ 47 3.2.6.6 Flight Data Display Replay ........................................................................................................... 47

3.2.7 Architecture and Supervision ................................................................................................................. 48 3.2.7.1 Functional Redundancy ................................................................................................................. 48 3.2.7.2 System Requirements .................................................................................................................... 48 3.2.7.3 Online Test..................................................................................................................................... 49 3.2.7.4 ATCAS System Control and Reconfiguration.............................................................................. 49 3.2.7.5 ATCAS Sector Reconfiguration.................................................................................................... 50

3.2.8 Aeronautical and Meteorological Information....................................................................................... 50 3.2.9 Management, Operational and Technical Information Report Tool ..................................................... 51

3.3 System External Interface Requirements .............................................................................................. 51 3.3.1 Datalink and Surveillance sensors interfaces......................................................................................... 52

3.3.1.1 Datalink Service Provider.............................................................................................................. 52 3.3.1.2 Radar Data ..................................................................................................................................... 52 3.3.1.3 Multilateration (MLAT) ................................................................................................................ 52

3.3.2 AFTN/AMHS ......................................................................................................................................... 52 3.3.3 Adjacent ATCAS interface..................................................................................................................... 53

3.3.3.1 Flight Plan Coordination ............................................................................................................... 53 3.3.3.2 Surveillance Data Sharing ............................................................................................................. 53

3.3.4 Defense systems interfaces..................................................................................................................... 54 3.3.5 Operator interface ................................................................................................................................... 54

3.3.5.1 Human Factors ............................................................................................................................... 54 3.3.5.2 Displays.......................................................................................................................................... 54 3.3.5.3 Message Handling ......................................................................................................................... 55 3.3.5.4 Input Devices ................................................................................................................................. 55

3.3.6 Time Reference System and Audio Recorder interface......................................................................... 55 3.3.7 ATFM Unity Interface............................................................................................................................ 55 3.3.8 AIS and MET.......................................................................................................................................... 56

3.4 System Internal Interface Requirements ............................................................................................... 56

3.5 System internal data Requirements ........................................................................................................ 56

3.6 Adaptation requirements ......................................................................................................................... 56 3.6.1.1 Database Management................................................................................................................... 56

SAM/IG/2NE-WP/10

B-7

3.7 Safety requirements .................................................................................................................................. 58

3.8 Security and Privacy Requirements........................................................................................................ 58

3.9 System environment requirements ......................................................................................................... 58

3.10 Computer Resource Requirements ......................................................................................................... 58

3.11 System Quality Factors............................................................................................................................. 58 3.11.1 System Reliability .............................................................................................................................. 58 3.11.2 System Maintainability ...................................................................................................................... 58 3.11.3 System Availability............................................................................................................................ 58

3.12 Design and Construction constraints ...................................................................................................... 59

3.13 Personnel-related requirements .............................................................................................................. 59

3.14 Training-related requirements ................................................................................................................ 59

3.15 Logistics-related requirements ................................................................................................................ 59

3.16 Other requirements................................................................................................................................... 59 3.16.1 Time Requirements ............................................................................................................................ 59 3.16.2 Capacity Requirements ...................................................................................................................... 60

3.17 Packaging requirements ........................................................................................................................... 61

3.18 Precedence and criticality of requirements............................................................................................ 61

4. QUALIFICATION PROVISIONS...................................................................... 62

5. REQUIREMENTS TRACEABILITY ................................................................. 63

6. NOTES ............................................................................................................. 64

6.1 Abbreviations............................................................................................................................................. 64

6.2 Glossary...................................................................................................................................................... 67

SAM/IG/2 WP-NE/10

B-8

TABLE LIST

INTERNATIONAL ATC DOCUMENTS AND OTHER STANDARDS: 16

REQUIREMENT PRECEDENCE TABLE 61

SAM/IG/2NE-WP/10

B-9

FIGURE LIST

FIGURE 1.1 – CONTEXT DIAGRAM FOR ATCAS 12

SAM/IG/2 WP-NE/10

B-10

1. SCOPE 1.1 Identification

This document is based on the requirements identified in the OACI Project RLA/06/901 for Air Traffic Control Automation Systems. This System Specification is based on the pre-existing systems used in the SAM Region and it incorporates requirements from the ATM Group as required. SAM Automation Team will update this document to reflect the required refinement.

The main objective of this specification is to consolidate all the requirements, mainly the mandatory ones to be used as a reference for future implantations of new ATCAS Systems and upgrades as well.

These requirements originated in a survey in the States, where each country presented an abstract of all the functionalities available in their automation systems.

This effort is in line with the need of harmonization to provide interchange of flight plan and surveillance data, and establish a minimum common level ground among the several ACC installed in the SAM region and the new systems as well.

SAM/IG/2NE-WP/10

B-11

11

1.2 System Overview 1.2.1 Introduction

This specification includes detailed requirements for ATC Automation Systems.

The system's mission is to enhance the safety of air travel by providing controllers with information on flights from surveillance sensors and adjacent centers. The information is presented on different functional displays, including situation displays, flight data displays, supervisor positions and aeronautical information displays.

The system must follow the International Civil Aviation Organization (ICAO) standards to provide routine ATC services for aircraft operating in SAM airspace.

ATM is described in the ICAO Global ATM operational Concept (Doc 9854) as the dynamic, integrated management of air traffic and airspace in a safe, economical and efficient manner through the provision of facilities and seamless services in collaboration with all parties. The operational concept also describes a system that provides ATM through the collaborative integration of humans, information, technology, facilities and services, supported by air, ground and/or space-based communications, navigation and surveillance.

This operational concept identifies seven interdependent components of the future ATM system. They comprise:

a) Airspace organization and management;

b) Aerodrome operations;

c) Demand and capacity balancing;

d) Traffic synchronization;

e) Conflict management;

f) Airspace user operations;

g) ATM Service Delivery Management.

SAM/IG/2 WP-NE/10

B-12

1.2.2 Context Diagram

The following Figure 1.1 illustrates the relationship of the ATCAS with its externals entities:

FIGURE 1.1 – CONTEXT DIAGRAM FOR ATCAS

1.2.3 Component and External Interfaces

The main components and External interfaces of the ATCAS are:

1.2.3.1 Components

Operational System

The Operational System takes the information from surveillances systems such as Radar and ADS, and integrates them with other information. Then, all the information is put together to form a representation of the airspace traffic environment.

Simulation and Training

ATCS ACC/APP

Defense Systems

Adjacent ATCS

Surveillance Sensors (Multilateration)

Surveillance Sensors ( Radar )

AircraftDatalink CPDLC, ADS (Surv.)

ATFM unity /central

Operators

Audio Recorder/ Reproduction

Time Reference

AFTN / AMHS (AIS/MET/PLN)

AIS/AIM MET

SAM/IG/2NE-WP/10

B-13

13

This system is capable to provide a realistic simulation of the Air Traffic environment in order to serve as a training platform for the operational and maintenance personnel. It uses Pilot Workstations to provide the training personnel with skills necessary to operate the ATCAS.

1.2.3.2 External Interfaces

The external interfaces to the ATCAS are:

a) Surveillance Sensors:

• PSR/MSSR surveillance;

• MSSR surveillance;

• ADS-B and ADS-C datalink;

• Multilateration;

The system receives surveillance data, processes the information and presents a synthetic image of the Air Situation to the controller.

b) Aircraft:

The controller uses a communication with the pilot through a specific protocol called CPDLC (Controller Pilot Data Link Communications).

The system receives track and flight plan information and sends commands to the pilot.

c) Adjacent ATCAS

The adjacent Centers represent the Area control centers and Approach control. This interface sends and receives mainly flight plan coordination messages, using the standard ICAO 4444 messages or OLDI and AIDC protocols.

The system will share surveillance data with adjacent centers.

d) Time Reference System

Time Reference System receives the UTC Time from the GPS and sends this information to synchronize the ATCAS Workstations time.

e) Audio Recorder

This interface is used to synchronize the recording and the playback system activities with the audio recording and playback.

f) Operators

They are represented by the main controllers, assistant, Flight data Operators and Technical/ Operational supervisors.

SAM/IG/2 WP-NE/10

B-14

g) AFTN Interface

It represents the interface with the AFTN to receive and transmit ATS messages, when the AMHS system is not available.

h) AMHS Interface

It represents the new interface for sending and receiving ATS messages. This system has a gateway to the AFTN.

i) ATFM Unity

This link is used to transmit the flight plan and traffic information and coordinate measures to diminish problems associated with the flow management.

j) Defense Systems

This interface is used to exchange surveillance information and coordination information with defense systems.

k) AIS and MET

This interface is designed for Web interfaces (HTTP) to access AIS and MET database using a Web Browser with a LAN connection.

1.2.3.3 System Features

The system includes the following features: Dual Surveillance Data Processing Servers- SDPS; Dual Flight Data Processing Servers- FDPS; Dual Data Recording Servers – DRS; Dual System Monitoring and Control – SMC; Multiple ASTERIX-format surveillance interfaces; Multiple Surveillance input formats; Surveillance Displays with 2048 x 2048 high resolution color monitors; Flight Data Displays; Supervisor Displays with printers; Flight Progress Strip Printers; Dual LAN; Database Management System for site adaptation and map generation; Interface for Time Synchronization with Audio Recorders; Electronic Flight Strip Displays; Direct Surveillance Access; Kalman-filter based Surveillance Tracker; Dual-redundant surveillance input lines; Physical Integration with Voice Control System; Interface with adjacent ACCs; Simulation/Training and Test System; Aeronautical Information System; Datalink interface; Air Defense interface to exchange surveillance data and other coordination information.

1.3 Document Overview This document is identified as the System Subsystem Specification (SSS) for the ATC Automation Systems in the SAM region.

SAM/IG/2NE-WP/10

B-15

15

The document is organized as follows:

Chapter 1 Scope: This chapter contains the identification and a overview of the system Chapter 2 Referenced Documents: contains the list of documents referenced in this

document. Chapter 3 Requirements: contains the list of characteristics and functionalities available

in the system. Chapter 4 Qualification Methods: defines the way that each requirement is tested. Chapter 5 Requirements Traceability: contains the list of requirements with specific

identifiers that will follow till the formal acceptance Test and documentation. Chapter 6 Notes: Contains the glossary and abbreviations used in this document. The following diagram shows the hierarchical structure of the documents and identifies the relative position of this document.

1.3.1 Document Conventions

These operational requirements and specifications use the words "shall", "will", "should", and "option (ally") with definite meanings. These are defined below:

1. "Shall" indicates that the requirement or specification it refers to is mandatory.

2. "Will", "should", or "option (ally)" indicates intent to realize the functionality within the system (unless it concerns functionality within the scope of external systems) but such statements are not testable.

Note that "will" is also used to introduce requirements that are more precisely stated elsewhere in the document.

SAM/IG/2 WP-NE/10

B-16

2. REFERENCED DOCUMENTS

INTERNATIONAL ATC DOCUMENTS AND OTHER STANDARDS:

AIDC

International Civil Aviation Organization – Asia and Pacific Office -

Asia/Pacific Regional Interface Control Document (ICD) for ATS

Interfacility Data Communications (AIDC) – Version 3.0 –

September 2007

OLDI Eurocontrol standard document for On-Line Data Interchange

(OLDI) - edition: 3.00, edition date: 31/10/2003.

ICAO Doc 4444

ATM/501

Air Traffic Management - Procedures for Air Navigation Services

15ª edition – 2007 and Amendment 1 (Jan 2008)

ICAO ANNEX 10 Volume I - Aeronautical Telecommunications;, Communication

Procedures Volume III, Communication Systems

ICAO ANNEX 15 Aeronautical Information Services

ASTERIX Eurocontrol Standard for Surveillance Data Exchange Issue 0.1,

September 1991

ICAO Doc 9705

AN956

Manual of Technical Provisions for the Aeronautical

Telecommunication Network – ATN.

ICAO Doc 9578 Manual of the Aeronautical Telecommunication Network (ATN)

ICAO Doc 9694

AN/955

Manual of Air Traffic Services Data Link Applications

ICAO Doc 9854 Global Ait Traffic Operational Concept - ATM

ICAO Doc 9880

AN/466

MANUAL ON DETAILED TECHNICAL SPECIFICATIONS FOR -

Aeronautical Telecommunication Network – ATN - 5 April 2007

ICAO Doc 9896 Aeronautical Telecommunication Network - ATN IPS

ICD for AIDC Asia/Pacific Regional Interface Control Document version 2

SAM/IG/2NE-WP/10

B-17

17

ICAO Doc 9613 Performance Based Navigation Manual – PBN

Volume I - concept and implementation guidance

SGN2-8 IP 10 Aeronautical Communication Panel ATN – CPDLC, ADS, FIS –

June 2006

(MLAT) Multilateration Concept of use Edition 1.0 – September 2007

(Doc 9688) Manual on Mode S Specific Services - 2nd edition, 2004

ICAO Doc 9377

AN/915

Manual on Coordination between Air Traffic Services,

Aeronautical Information Services and Aeronautical

Meteorological Services. 3rd edition, 2007. 142 pp.

ICAO Doc 9873

Manual on the Quality Management System for the Provision of

Meteorological Service to International Air

Navigation. 1st edition, 2007. 62 pp

ARINC 622 ATS Datalink Applications over ACARS Air-Ground Network (end-to-

end).

RTCA DO-

258/EUROCAE ED-100

Interoperability Requirements for ATS Applications Using ARINC

622 Data Communications.

ARINC 620 Datalink Ground System Standard and Interface Specification

(ground-to-ground)

ICAO Guidance Material

GUIDANCE MATERIAL OR THE ASIA/PACIFIC REGION FOR

ADS/CPDLC/AIDC GROUND SYSTEMS PROCUREMENT AND

IMPLEMENTATION Version 1 - September 2007

Preliminary System Interface Control Document for the

Interconnection of ACC Centers of the CARSAM Region

CAR/SAM Automated ACC Interconnection Plan

SAM/IG/2 WP-NE/10

B-18

3. REQUIREMENTS

These requirements represent a database of functionalities that can be shaped accordingly in the system. The States are responsible for the decision of implementation involved in the installation or in the modernization process.

3.1 Required States and Modes

SSS 1 - The system shall have the capability to operate in Operational partition or in Simulator Partition.

SSS 2 - The surveillance and Flight display consoles shall have the capability to operate in Operational Mode, Direct Radar Access Mode, Simulator Mode, and Playback Mode.

SSS 3 - The servers shall have the capability to operate in Mode Active, Hot Stand-by and Maintenance Mode.

3.2 System Capability Requirements 3.2.1 Man-Machine Interface

The surveillance positions will be able to provide surveillance tracks without interruption.

Data will be displayed in a clear way avoiding confusion and/or misunderstanding, and taking into consideration its contents, meaning, or the importance of the data displayed.

3.2.1.1 Graphic Interface

3.2.1.1.1 Predicted Position Indicator

SSS 4 - The Main Controller Display shall be able to designate a track vector and to define the predicted ahead in time (minutes) what those vectors represent.

SSS 5 - The system shall have a command to designate a track for display and define a specific time ahead.

SSS 6 - The graphic representation of a velocity will be displayed as an extended velocity vector and the length of the vector shall be a function of the controller selected time for predicted positions.

3.2.1.1.2 Functional Controls

SSS 7 - The system shall have the capability to cancel or delete any input action that has been initiated, before the completion or confirmation of execution of the command.

SSS 8 - The system shall have functional controls using dedicated function keys and a trackball.

SAM/IG/2NE-WP/10

B-19

19

3.2.1.1.3 Radar Coverage Diagrams and Color Assignment

SSS 9 - The supervisor position shall have the capability to select colors to be applied to various display elements, in a manner not to degrade or affect the processing of operational functions.

SSS 10 - Selection of color brightness and intensity shall be available as an operational function in the individual workstation.

SSS 11 - The main controller position shall have capability to display coverage diagrams for each surveillance sensor and resultant coverage diagram for all ground based surveillance sensors presented in a specific color.

SSS 12 - These coverage diagrams shall be customized to emulate the theoretical coverage for the heights 5,000 feet, 10,000 feet, and 20,000 feet for each azimuth. Areas with no surveillance coverage shall have a special color.

3.2.1.1.4 Screen Annotation

SSS 13 - The surveillance workstations shall have the capability for entering up to TBD annotations for display. Each annotation will have a specific text and color.

SSS 14 - The surveillance workstation shall have the capability to route the screen annotation to other surveillance workstations and to suppress displayed annotations as well.

3.2.1.1.5 Windows Presentation

SSS 15 - The surveillance workstation shall organize all the information presented in windows to present surveillance data, flight plan data, alerts, status, commands, where each window shall be selected, resized or moved by the controller.

SSS 16 - The system shall have the capability to notify any critical information shown in a minimized or inactive window.

3.2.1.1.5.1 Main Surveillance Window

SSS 17 - The main surveillance window shall present the surveillance data with the capability to zoom and pan.

3.2.1.1.5.2 Secondary Surveillance Window

SSS 18 - The secondary surveillance windows shall provide the same capability than the main surveillance window with independent resize, zoom and pan.

3.2.1.1.5.3 System Status Window

SAM/IG/2 WP-NE/10

B-20

SSS 19 - The System Status Window shall display the following information:

• Time and Date;

• Selected display range;

• Altitude filter bounds;

• SSR block code selections;

• CJS Designation;

• Presentation mode;

• Magnetic Variation;

• Label line selections.

3.2.1.1.5.4 General Information Window

SSS 20 - The system shall provide the capability to display the following information on the Flight Data Display:

• Flight Plan

• MET data

• Aeronautical/Meteorological Information: Notice to Airmen (NOTAM) and Meteorological Report (METAR), and other meteorological messages (SIGMET, AIRMET, GAMET, SPECI and TAF);

• General Purpose Information;

• QNH values for aerodromes and regions.

3.2.1.1.5.5 Messages Windows

SSS 21 - The system shall have the capability to display pending coordination messages between centers, sectors or tracks (via Datalink).

SSS 22 - The system shall have the capability to register all the coordination actions even when the interface between the systems is not working.

SSS 23 - The system shall have the capability to display an alert when a response to a coordination message is not received.

SSS 24 - The system shall have the capability to display the coordination messages received till the operator send the answer correctly.

SSS 25 - The system shall have the capability to display the history of coordination messages.

3.2.1.1.6 Images

SAM/IG/2NE-WP/10

B-21

21

SSS 26 - The main surveillance window shall have the capability to display georeferenced images representing meteorological information as an overlay under operator control.

3.2.1.1.7 Surveillance Data Display Elements

SSS 27 - ADS-B, ADS-C, PSR, SSR, and PSR/SSR plot presentation shall be available as a selectable function.

SSS 28 - Surveillance workstations shall have the capability of manually enable or disable the presentation of plot data besides the presentation of tracked targets.

SSS 29 - The Track information shall indicate:

• Aircraft position;

• Track history information.

SSS 30 - The system shall have the capability to process and display:

• SSR code or callsign when correlated with a flight plan;

• Flight level/altitude based on Mode C or barometric corrected altitude ( below the transition level) surveillance information;

• Heading and ground speed (as a speed vector);

• Attitude indicator, i.e., climb, descent, or level flight.

The system will have the capability to calculate and display the predicted position of any track as designated by a controller input action.

SSS 31 - The surveillance position shall have the capability to process and display alphanumerically the ground speed and heading (track) of any track designated.

SSS 32 - The following elements shall be available for display:

• Map information;

• Range rings;

• Time;

• Selected Surveillance Display range;

• Selected height filter;

• Controller jurisdiction indicator;

• Handoff indication;

• Range/bearing line (cursor);

• Indication when the Air Situation Display is not being updated;

• Selected track presentation mode/surveillance sensor;

• Special codes;

• STCA (Short Term Conflict Alert);

SAM/IG/2 WP-NE/10

B-22

• MSAW (Minimum Safe Altitude Warning);

• MTCD (Medium Term Conflict Detection);

• CLAM (Cleared Level Adherence Monitoring);

• AIW (Area Infringing Warning);

• RAM (Route Adherence Monitoring);

• Track information, including:

o Position symbols;

o Track history information.

• Label information.

SSS 33 - Critical information related to the display of special codes, STCA, MSAW, MTCD, CLAM, AIW Data or information considered to be critical for the operation shall always be displayed in a clear and unambiguous manner.

3.2.1.1.8 Surveillance Data Position Symbols

SSS 34 - Different symbols shall be used for indicating a PSR plot, SSR plot, PSR track, SSR track, PSR/SSR track, ADS-B Track, ADS-C Track, Multilateration Surveillance track, Flight Plan navigated track.

3.2.1.1.9 Track History Information

SSS 35 - The surveillance workstation shall have the capability to enable or disable track history information in each position.

SSS 36 - The surveillance workstation shall have a capability to select the number of track history positions, using a specific symbol.

3.2.1.1.10 Display Range

SSS 37 - The Surveillance Display shall have the capability to select a specific range for each surveillance workstation.

3.2.1.1.11 Range Rings

SSS 38 - The system shall have the capability to display Range rings individually selectable at each surveillance workstation as circles centered on the selected ground based surveillance sensor in monoradar mode and multiradar mode.

3.2.1.1.12 Quick Look

SAM/IG/2NE-WP/10

B-23

23

SSS 39 - The system shall have a capability to display all tracks and labels through an individual quick look function.

SSS 40 - The quick look function shall enable display of label track data bypassing all local filters.

3.2.1.2 Range Bearing Line

SSS 41 - Each Surveillance Display shall have the capability to display a minimum of 3 range/bearing lines, displayed at the end of the line, as the following types:

• Between any two operator selectable points;

• Between any two moving targets, including a time field,

• Between a operator selectable point and a moving target, including a time field;

3.2.1.3 Smart Labels

The smart label will be the main way to interact with the system.

SSS 42 - The system shall have a capability to display three types of label:

• Standard Label – with the minimal track/flight plan information.

• Extended Label – activated when the cursor pass over the label.

• Selected Label- similar to the extended label but with interaction in the fields.

3.2.1.3.1 Controller Jurisdiction Indicator (CJI)

SSS 43 - The system shall have a capability to display an indication an indication of which sector has jurisdiction over the track in question.

SSS 44 - The system shall allocate a separate jurisdiction indicator as defined in adaptation data.

SSS 45 - This CJI shall be shown in conjunction with the handoff function.

SSS 46 - The system shall display involved in a handoff through a distinct presentation.

3.2.1.3.2 Special Position Indicator (SPI)

SSS 47 - The system shall display activation of SPI using a unique indication.

SSS 48 - The system shall have the capability to re-position any label relative to the position symbol, manually or using an automatic algorithm.

SSS 49 - The following data shall be displayed in a label, if available:

• SSR code or call sign when correlated with a flight plan or entered manually from a surveillance workstation;

SAM/IG/2 WP-NE/10

B-24

• Mode C flight level/altitude;

• Attitude indicator, i.e., climb, descent, or level flight;

• Controller jurisdiction indicator;

• Calculated ground speed, expressed in tens of knots;

• Cleared flight level;

• Quality Factor;

• ADS Data:

• Coordination Data;

• Free text, entered manually.

SSS 50 - The calculated vertical speed shall be displayed after an appropriate controller input action.

3.2.1.4 Filters

SSS 51 - The system shall have a capability to select an upper and lower limit for the level filter, at each surveillance workstation.

SSS 52 - The following conditions shall override the filters:

• Tracks which are under the jurisdiction of this workstation;

• Special condition tracks;

• Tracks that are quick-looked at the display;

• Active handoff tracks;

• Targets that do not currently have valid Mode C data;

• Tracks which are individually selected for display by the controller;

• Unsuppressed tracks in MSAW, STCA, MTCD, CLAM, RAM, AIW alerts.

SSS 53 - The surveillance shall have a capability to display the height filter limits selected.

SSS 54 - The system shall have the capability enable/disable adapted areas within which detected tracks will not be displayed.

SSS 55 - The system shall have a capability to designate specific codes or code groups to filter the track label presentation.

3.2.1.5 Maps

SSS 56 - The system shall have a capability to select and present map data in each surveillance workstation.

SAM/IG/2NE-WP/10

B-25

25

SSS 57 - The map presented shall have specific graphic representation for the following entities:

• FIR/UIR borders;

• Lateral limits of sectors;

• Terminal control areas;

• Control zones;

• Traffic information zones;

• Airways and ATS routes;

• Restricted areas.

3.2.1.5.1 Weather Surveillance Data

SSS 58 - The system shall have the capability to display weather surveillance data from PSR radars or Meteorological radars.

SSS 59 - The system shall have a capability to select the display of high intensity, both high and low intensity, or no weather, if this information is available.

3.2.1.5.2 Private Maps

SSS 60 - The surveillance workstation shall provide the capability to define and to display private maps created on-line with different attributes of lines.

SSS 61 - Presentation of each private map shall be individually selectable.

3.2.1.6 Flight Plan

3.2.1.6.1 Flight Strip Window

SSS 62 - The system shall provide the capability to display up to TBD pages of flight strip information in this window on the ESD.

3.2.1.6.2 Flight Data Displays

SSS 63 - The system shall provide functional controls to enter, modify, cancel and display flight plan data.

SSS 64 - The system shall have the capability to insert a change in a flight plan route through graphical point selection.

SSS 65 - The flight plan functions shall include:

• flight plan data entry;

• flight plan update data update;

• Display of flight plan data;

SAM/IG/2 WP-NE/10

B-26

• Edition of stored/displayed information;

• Printing of Flight Progress Strips:

• Edition of departure clearance for inactive and pre-active flight plans;

• Manual edition of ATS messages;

SSS 66 - The system shall have the capability to edit a flight plan using a graphic tool over a specific thematic map.

SSS 67 - The system shall have a capability to display a flight plan history, with all the actions and message updates received or transmitted related to that flight plan.

3.2.1.6.3 Flight List Presentation

SSS 68 - The system shall have the capability to display traffic lists, based on the flight plan status, including coast and hold information.

3.2.1.6.4 Flight Strip Presentation

SSS 69 - The system shall have the capability to display Electronic Flight Strip and to print Paper Flight Progress Strip.

3.2.1.6.4.1 Paper flight progress strip

SSS 70 - The system shall have the capability to define a flight Strip format and layout in adaptation data.

SSS 71 - The system shall distribute flight strips in accordance with the route system and the Strips distribution plan as defined in adaptation, and the capability to print flight strips at any time.

3.2.1.6.4.2 Electronic Flight Strips

3.2.1.6.5 General

SSS 72 - The system shall have the capability to display electronic flight strips.

SSS 73 - The system shall have the capability to allow the operator to select pre-defined flight level using smart labels.

SSS 74 - The system shall display electronic flight strips associated with the flight under control or prior to control of the associated jurisdiction sector at the position associated to the sector.

SSS 75 - The system shall have the capability to display at least the following sub-states for a flight plan:

• active not controlled;

SAM/IG/2NE-WP/10

B-27

27

• active controlled;

• in transfer (donor, receptor and proposed);

• announced;

• holding;

• transferred;

SSS 76 - There shall be specific presentations for the following conditions:

• correlated;

• multicorrelation (two or more tracks having identical SSR code associated to the same flight plan);

• non-conformance route/track position indication;

SSS 77 - There shall be a unique presentation for the first display of the flight plan.

3.2.1.6.6 Flight Plan Data Retrieval

SSS 78 - The system shall have the capability to retrieve flight Plans, repetitive flight plans, and flight plan history from the database.

SSS 79 - The system shall have the capability to retrieve flight plan data available on the basis of: Flight identification, in combination with departure aerodrome, and/or EOBT/ETA (validity times).

3.2.1.6.7 Repetitive Flight Plan Retrieval

SSS 80 - The Flight plan workstations shall have access to RPL data in the RPL file, and to retrieve RPL data available on the basis of: Flight identification, in combination with departure aerodrome and/or EOBT/ETA.

3.2.1.6.8 Flight Plan History

SSS 81 - The system shall have a capability to display and print all messages concerning a flight plan, including associated update messages, for at least adaptable hours after termination of flight plan.

3.2.1.6.9 Free Text Input and Distribution

SSS 82 - The system shall have the capability to perform "free text" input, and to be able to route this information for output to other designated workstations or any AFTN/AMHS address.

SAM/IG/2 WP-NE/10

B-28

3.2.1.6.10 RVSM

SSS 83 - The system shall have the capability to process and display RVSM status according with the associated flight plan, the operator input data and coordination messages as well, considering the RVSM airspace;

3.2.1.6.11 PBN

SSS 84 - The system shall have the capability to process and display the PBN status associated to the flight plan according with the Amendment 1 of Doc 4444, considering the operator input data and coordination messages as well;

3.2.2 Datalink Communication

SSS 85 - The system shall be linked to aircraft by a datalink service provider (DSP).

SSS 86 - The system shall be capable of transmitting and receiving AFN, ADS and CPDLC messages complying with RTCA/DO258A-EUROCAE/ED-100 and AIDC messages complying with the Asia/Pacific Regional Interface Control Document for AIDC (ICD).

SSS 87 - The system shall include the ACARS Convergence Function (ACF) to convert messages between the character-oriented data of ACARS and the bit-oriented data used in ADS and CPDLC.

SSS 88 - The system shall provide air traffic controllers with:

• Display of message exchanges;

• Display of updated aircraft positions and maps;

• Tools for measuring separation in distance or time;

• Tools for measuring angles between aircraft flight paths;

• Information on aircraft flight status;

• HMI tools for composing ADS and CPDLC messages;

• Alerts for exception conditions;

• Conflict probe capability;

• Electronic flight progress strips, and paper strips if required;

• Presentation of emergency status;

• Other information pertinent to ATS operations.

3.2.2.1 CPDLC

SSS 89 - The system shall have the capability to communicate using the protocol CPDLC (“Controller- Pilot Datalink Communication”).

SAM/IG/2NE-WP/10

B-29

29

SSS 90 - The system shall be capable of processing the specified number of message exchanged with each of the aircraft.

SSS 91 - Down-linked CPDLC messages shall be displayed to controllers. Tools shall be provided to allow simple and intuitive initiation of, or response to, CPDLC messages.

SSS 92 - CPDLC position reports shall be used to display aircraft positions when no ADS report is available.

SSS 93 - The system shall have the capability of terminating CPDLC connection with the aircraft.

SSS 94 - The system shall allow transfer of CPDLC between sectors of an ATCAS without changing the data authority and with the same CPDLC link.

SSS 95 - The system shall be capable of handling the message set and the standardized free text messages defined in the FOM, as well as free text.

SSS 96 - The system shall allow controllers to review uplink messages prior to sending.

SSS 97 - Messages shall be handled in order of priority.

SSS 98 - Messages with the same priority shall be processed in the time order of receipt.

SSS 99 - The controller shall be alerted to unsuccessful receipt of the required response in the specified time or receipt of Message Assurance Failure (MAF).

SSS 100 - The system shall allow controllers to send any response messages linking with the reference number of the message received.

SSS 101 - A CPDLC dialogue shall not be closed until an appropriate closure response for that message with same reference number is received.

SSS 102 - When the closure response message is sent, the dialogue is closed and the system shall reject any further attempt to send a response message.

SSS 103 - The capability of closing a CPDLC dialogue, independent of CPDLC closure message receipt, shall be provided.

SSS 104 - The system shall have the capability to send the more frequent CPDLC messages through an interface using the associated track label.

SSS 105 - The system shall have the capability to display aircraft data, received by ADS, in the standard or extended track label.

SSS 106 - The system shall have the capability to display different shapes or symbols to differentiate that the aircraft is ADS/CPDLC capable and it is in contact with the Center.

SSS 107 - The system shall have the capability to allow the operator to differentiate information of course, speed and vertical speed received automatically by ADS.

SSS 108 - The system shall have the capability to uplink messages to the aircraft regarding the controller actions that the pilot need to know.

SSS 109 - The system shall have the capability to display in the outbox message list all the uplink CPDLC messages that are pending for an answer from the pilot.

SAM/IG/2 WP-NE/10

B-30

SSS 110 - The system shall have the capability to display in a unique way the field associated to a change made by the controller till a downlink message is received from a pilot saying the change was made.

SSS 111 - The system shall have the capability to display a communication failure message, when an expected downlink message is not received during a time-out (adaptable).

3.2.2.2 ADS

SSS 112 - The capacity of the ADS function shall be determined from the operational policy and procedures and the airspace characteristics, including number of FANS capable aircraft, periodic reporting rate, airspace size, waypoint event report frequency, usage of event and demand contracts, and projected traffic growth.

SSS 113 - The system shall be capable of initiating periodic, event and demand contracts.

SSS 114 - The system shall be able to support a demand, an event and a periodic contract simultaneously with each aircraft.

SSS 115 - The system shall apply validation checks to incoming data by reference to flight plan data in relation to time, altitude, direction and position.

SSS 116 - The system shall be capable of processing ADS reports to display aircraft positions, tracks and altitude. Between ADS reports, aircraft positions shall be extrapolated and displayed automatically at specified intervals.

SSS 117 - Air and earth reference data of ADS reports shall be provided to controllers if required.

The types of ADS contract are described at ICAO 9694 and 9880 documents.

SSS 118 - ADS messages shall be processed by the system in the following order:

1. ADS emergency mode.

2. Demand/event reports.

3. Periodic report.

SSS 119 - Within these categories, messages shall be handled in the order received.

SSS 120 - The following errors shall be notified to controllers:

• Message validation error.

• Message sequence error detected with time stamp.

• Time-out of ADS report in response to request.

• Periodic and waypoint event report failure.

3.2.2.3 Notification of Error Messages

SSS 121 - The system shall be capable of performing the cyclic redundancy check (CRC) on each message.

SAM/IG/2NE-WP/10

B-31

31

SSS 122 - The system shall be capable of verifying the format and validity checks appropriate to each message.

SSS 123 - Controllers shall be notified when the system detects:

• A message error;

• A message sequence error;

• A duplicate message identification number;

• Message non-delivery;

• An expected response not received.

SSS 124 - The system shall have a capability to display ADS or CPDLC emergency message received from an ADS/CPDLC equipped aircraft.

3.2.2.4 Timestamps and Timers

SSS 125 - CPDLC and AIDC messages shall be timestamped; however, the form of some timestamps is actually set differently from that specified in Doc 9694.

SSS 126 - By setting and/or deactivating various timer values for the messages received in response to transmitted messages, the system shall monitor whether or not aircraft responses arrive within a specified time limit.

Timers are generally based on the operational requirements of each ATCAS.

SSS 127 - The timers for sending messages relating to the automatic transfer of CPDLC connection and to AIDC shall be set according to bilateral agreements with adjacent ATCAS concerned.

SSS 128 - A timer file shall be provided in the system for:

• Timeout settings for delayed response.

• Timing to initiate actions in ADS/CPDLC operations for:

o Connection request (CR);

o ADS periodic, event and demand requests;

o Automated transfer of connection to the next ATCS;

o Sending Next Data Authority (NDA) message;

o Sending AFN Contact Advisory (FN_CAD): at least 30 minutes prior to FIR boundary message;

o Sending End Service message prior to the aircraft crossing the FIR boundary (e.g. 5 minutes before);

o Timer to trigger actions for sending AIDC messages;

o Timer for re-transmission of the message when no response is received within a specified time.

SAM/IG/2 WP-NE/10

B-32

3.2.2.5 AFN Logon Functions

The AFN logon functions provide the necessary information to enable ADS and CPDLC communications between the system and aircraft avionics systems for:

• Logon;

• Forwarding logon information to the next ATCAS.

Note: Details of Datalink Initiation Capability (DLIC) functional capabilities are provided in Doc 9694 Part 2.

The required capacity for AFN logons will be determined from the operational requirements, such as estimated number of FANS aircraft at the peak hours and anticipated growth of FANS traffic.

SSS 129 - The system shall be capable of accepting or rejecting AFN logon requests.

SSS 130 - The system shall have the capability to correlate the AFN logon data automatically with the aircraft flight plan.

SSS 131 - The controller’s workstation shall be capable of displaying the following data:

• Address and version number of the aircraft applications, if required;

• Response from the aircraft with timestamp;

• Status of correlation of the aircraft with its stored flight plan;

• Indication of ‘Acceptance’ or ‘Rejection’ to the logon request from aircraft.

SSS 132 - When an aircraft downlinks its supported applications and their version numbers in an FN-CON message, the ATCAS system response shall indicate whether or not it supports those version numbers.

SSS 133 - The system shall be capable of sending the Acceptance message or the Rejection message with reason, as appropriate.

3.2.3 Surveillance Data Processing

Ideally, surveillance systems shall incorporate all available data to provide a coherent picture that improves both the amount and utility of surveillance data to the user. The choice of the optimal mix of data sources shall be defined on the basis of operational demands, available technology, safety and cost-benefit considerations.

3.2.3.1 Air Situation establishment

SSS 134 - The system shall make available a plot position presentation as a selectable function.

SAM/IG/2NE-WP/10

B-33

33

SSS 135 - The system shall have the capability to receive, process and integrate all the messages (plots and tracks) to create and update a dynamic Air Situation received form the following surveillance sources:

• ADS-B: Eurocontrol Asterix Protocol Standard including Categories 10, 11, 21 e 23;

• ADS-C: ACARS Protocol;

• Multilateration: Eurocontrol Asterix Protocol Standard including Categories 10, 11, 19 e 20;

• Mode S: Eurocontrol Asterix Protocol Standard including Categories 10, 11, 34 e 48;

• Adjacent Centers: Eurocontrol Asterix Protocol Standard including Categories 62, 63 e TVT2;

• Radars: Eurocontrol ASTERIX protocols including categories 1, 2, 8, 34, 48 with UAP from Raytheon, Thales, SELEX, Lockheed Martin, INDRA, INVAP;

• Radars: CD2, AIRCAT500, TVT2 legacy Protocols.

SSS 136 - The system shall have the capability to create and update track information based on the flight plan information and controller data input (Flight Plan Navigated tracks);

SSS 137 - All the messages shall be submitted to a process to validate the message format before the surveillance integration, discarding erroneous messages and logging all errors found.

SSS 138 - The system shall have the capability to create a timestamp for all the messages using an UTC Time reference sent by the sensor, or using the local relative time.

SSS 139 - The system shall have the capability to integrate all the meteorological information from the primary radars (cat 8 messages) to display at the surveillance display.

SSS 140 - The system shall have a capability to tracking all the surveillance reports using a Surveillance Multisensor Tracking, improving accuracy and smoothing of the resulting system tracks through adaptative Kalman filters.

SSS 141 - The system shall have the capability to manage the status of all sensors, to determine which of the sensors are available to participate of the data fusion.

SSS 142 - The system shall have the capability to manage the surveillance report aging from all the sensors, and to verify the eventual interruption of message flow.

SSS 143 - The system shall have the capability to manage the surveillance track update and the track suppression for both the system track file and the local track file.

SSS 144 - The system shall have the cap

Date post:	17-Feb-2021
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times