etkr - eurocontrol | - driving excellence in atm … service will replace the primary surveillance...

EUROCONTROL

ETKR

Centralised Service on European Tracker Service

Concept of Operations (CONOPS)

Edition Number : 2.0

Edition Date : 23 October 2013

Status : Released Issue

Intended for : EUROCONTROL Stakeholders

Centralised Service on European Tracker Service Concept of Operations (CONOPS)

© European Organisation for the Safety of Air Navigation (EUROCONTROL) 2013

Edition: 2.00 Released Issue Page 1 of 60

DOCUMENT CHARACTERISTICS

TITLE


Publications Reference:

ISBN Number:

Document Identifier Edition Number: 2.0

CS3_ETKR_CONOPS Edition Date: 23 October 2013

Abstract

The European Tracker Service (ETKR) will enable the creation of a Europe-wide, consistent, high quality picture of the air situation, merging traffic data provided by the various surveillance sources (PSR, SSR, ADS, WAM) and distributing resultant tracks to the service consumer sites..

The service will replace the primary Surveillance Data Processing infrastructure deployed in the ATC centres. The objective of the European Tracker Service is to de-fragment the European Surveillance layer as an enabler to the improvement of the Network performance, both in terms of safe capacity and cost.

The tracks are elaborated in an ETKR Data Centre (EDC) by the EUROCONTROL ATM suRveillance Tracker And Server (ARTAS) and a second dissimilar, but functionally equivalent, tracker. The tracks are distributed to the Users, or clusters of Users, throughout the Pan European Network Service (CS8). For contingency and business continuity purposes two EDC sites are foreseen to be deployed.

ETKR will be operated under the responsibility of the Network Manager and will encompass ANSPs of the EUROCONTROL Member States.

ETKR will facilitate and where required comply with applicable regulations, notably on interoperability.

Keywords

CONOPS Centralised Service ETKR Tracker

ESASSP GEN-SUR-SPR Surveillance Sensor

ARTAS

SASS-C SDDS PENS Service Wrapper

SDPS Air Situation Picture Radar

Authors

Jean-Marc DUFLOT, Costas CHRISTODOULOU and CS3 Project Team

Herman BARET - Centralised Services Programme Manager

Contact(s) Person Tel Unit

Jean-Marc DUFLOT +32 2 729 3126 NMD/NS/SRS

Costas CHRISTODOULOU +32 2 729 3135 NMD/NS/SRS




STATUS, AUDIENCE AND ACCESSIBILITY

Status Intended for Accessible via

Working Draft General Public Intranet

Draft ECTL Stakeholders Extranet

Proposed Issue Restricted Audience Internet (www.eurocontrol.int)

Released Issue Electronic copies of this document can be downloaded from :

This document is copyright protected. It may be copied in whole or in part by the recipients for their own purposes strictly related to the support of the development of Centralised Services by EUROCONTROL. All copies shall display the following notice "© EUROCONTROL 2013". Any commercial use of the document or its contents, their use for purposes other than specified in this notice, as well as their distribution to third parties is strictly prohibited.




DOCUMENT APPROVAL

The following table identifies all management authorities who have successively approved the present issue of this document.

AUTHORITY NAME AND SIGNATURE DATE

Project Manager

Jean-Marc Duflot

Programme Manager

Herman Baret

Director Single Sky

Luc Tytgat

Director Network Manager

Joe Sultana

Principal Director ATM

Bo Redeborn

Director General, after consultation with the Board of Directors

Frank Brenner




DOCUMENT CHANGE RECORD The following table records the complete history of the successive editions of the present document.

EDITION NUMBER

EDITION DATE

REASON FOR CHANGE PAGES

AFFECTED

1.00 09/09/2013 Draft for CONOPS Workshop All

2.00 23/10/2013 Comments from Stakeholders consultation

All

Publications

EUROCONTROL Headquarters

96 Rue de la Fusée

B-1130 BRUSSELS

Tel: +32 (0)2 729 1152

Fax: +32 (0)2 729 5149

E-mail: [email protected]

mailto:[email protected]




Contents

EXECUTIVE SUMMARY ............................................................................................. 9

INTRODUCTION ....................................................................................................... 10

CHAPTER 1 – Context ............................................................................................. 12

1.1 Geographical applicability ........................................................................................12

1.2 Aim ...........................................................................................................................12

1.3 Intended Audience ...................................................................................................12

1.4 Intended Benefits .....................................................................................................12

CHAPTER 2 – Operational Concept ....................................................................... 14

2.1 Scope .......................................................................................................................14

2.1.1 Current Situation .........................................................................................14

2.1.2 Scope of ETKR ...........................................................................................14

2.2 Service Concepts and Components ........................................................................15

2.2.1 Overall Concept ..........................................................................................15

2.2.2 Sensor data provision .................................................................................16

2.2.3 Customers sites ..........................................................................................16

2.2.4 Provision of Communication services .........................................................17

2.2.5 Post Operations Performance ....................................................................17

2.3 Roles and responsibilities ........................................................................................17

2.3.1 Overview .....................................................................................................17

2.3.2 ETKR Service Provider ...............................................................................18

2.3.3 Customers (ANSPs and Others) .................................................................19

2.3.4 Surveillance Data Providers (ANSPs and Others) .....................................19

2.3.5 EUROCONTROL as Network Manager......................................................19

2.3.6 CS8 – PENS ...............................................................................................20

2.3.7 CS5 – EAIMS ..............................................................................................20

2.3.8 CS2 – 4DPP ................................................................................................20

2.3.9 CS7 – NIPS ....................................................................................................20

2.4 Safety and Performance ..........................................................................................21

2.5 Security ....................................................................................................................21

2.6 Reliability and Availability ........................................................................................22

CHAPTER 3 – Regulatory requirements ................................................................ 23

3.1 Existing applicable regulation ..................................................................................23

3.1.1 Operational Requirements ..........................................................................23

3.1.2 European Union Regulatory Framework ....................................................23

3.2 Requirements for new/updated regulations to implement the CS#3 ETKR ............24




CHAPTER 4 – Links of the CS#3 ETKR to ICAO GANP, SESAR deployment, ESSIP – current procedures and future evolution ......... 26

4.1 Baseline – Interim Deployment Programme (IDP) ..................................................26

4.2 Pilot Common Projects (PCP) and Common Projects (CP) ....................................27

4.3 European Single Sky ImPlementation (ESSIP) .......................................................27

4.4 ICAO Global Air Navigation Plan (GANP) ...............................................................27

4.5 Current procedures and future evolution .................................................................27

ANNEX 1 – Information flows ................................................................................ 29

A1.1 Operational process .................................................................................................29

A1.2 Technical process ....................................................................................................30

ANNEX 2 – Data Set ................................................................................................ 31

A2.1 Sensor Data Input ....................................................................................................31

A2.2 Track information Output .........................................................................................31

A2.3 Airspace Data ..........................................................................................................31

ANNEX 3 – EUROCONTROL Proposal for a first set of Centralised Services to contribute to SES Performance Achievement, March 2013 .......................................................................................................... 32

ANNEX 4 – Brief Description of Centralised Services ......................................... 32

ANNEX 5 – Minutes of the 29 April 2013 Airspace Users CS Workshop ........... 32

ANNEX 6 – Minutes of 4 March 2013 Member States CS Workshop .................. 32

ANNEX 7 – Minutes of 24 April 2013 ANSPs CS Workshop ................................ 32

ANNEX 8 – Minutes of 17 May 2013 Manufacturing Industry CS Workshop ..... 32

ANNEX 9 – Working papers, slides and extract from the Minutes of PC/39, 16 May 2013 ............................................................................................. 32

ANNEX 10 – Working Papers, slides and extract from the Minutes of PCC/31, 2 July 2013 ................................................................................ 32

ANNEX 11 – Slides and Minutes of CS#3 Workshop of 1st of July 2013 ........... 32

ANNEX 12 – ETKR Service Features ..................................................................... 33

A12.1 Service level ............................................................................................................33

A12.2 Track Information Service ........................................................................................33

A12.2.1 Customer area of interest ...........................................................................34

A12.2.2 Update rate .................................................................................................34

A12.3 Sensor coverage management ...............................................................................34

A12.3.1 Configuration of ETKR Sensors ..................................................................34

A12.3.2 Sensor Planning and coordination ..............................................................35

A12.3.3 Sensor outage or degradation ....................................................................36

A12.3.4 Sensor maintenance coordination ..............................................................36




A12.4 Monitoring and Control ............................................................................................36

A12.4.1 Monitoring and Control of ETKR infrastructure ...........................................36

A12.4.2 Sensor monitoring .......................................................................................37

A12.4.3 Service monitoring ......................................................................................38

A12.4.4 Performance monitoring..............................................................................39

A12.5 Recording and Playback ..........................................................................................40

A12.5.1 Customer’s Site level ..................................................................................40

A12.5.2 EDC level ....................................................................................................40

A12.6 Development of new releases .................................................................................41

A12.6.1 Development ...............................................................................................41

A12.6.2 Validation and tuning ..................................................................................41

A12.6.3 Transitional support ....................................................................................41

A12.7 Maintenance and Operational Support ....................................................................41

ANNEX 13 – ETKR System Architecture............................................................... 43

A13.1 ETKR Components ..................................................................................................43

A13.1.1 ETKR Data Centre ......................................................................................43

A13.1.2 ETKR Service Wrapper (ESW) ...................................................................44

A13.2 Dissimilar Redundancy ............................................................................................45

A13.3 ETKR system architecture options ..........................................................................45

A13.3.1 Option 1: Centralised ..................................................................................45

A13.3.2 Option 2: Semi-distributed ..........................................................................47

A13.4 Communication Infrastructure .................................................................................47

A13.4.1 Networks .....................................................................................................47

A13.4.2 Access points ..............................................................................................47

A13.5 Redundancy and Contingency ................................................................................48

ANNEX 14 – ETKR Service Set-up ........................................................................ 49

A14.1 Demonstrator ...........................................................................................................49

A14.2 Development ............................................................................................................49

A14.3 Implementation and Deployment .............................................................................50

A14.3.1 ETKR Data Centres ....................................................................................50

A14.3.2 Customer site adaptation ............................................................................50

A14.3.3 ETKR testbed ..............................................................................................50

A14.4 ETKR Supporting Processes and Activities.............................................................53

A14.5 ETKR Service Transfer ............................................................................................53

Applicable and Reference Documents .................................................................. 54

Applicable Documents .......................................................................................................54

Reference Documents .......................................................................................................55

GLOSSARY .............................................................................................................. 56

ABBREVIATIONS ..................................................................................................... 57




List of Figures

Figure 1: ETKR Overall Architecture .................................................................................16

Figure 2 : Roles and Responsibilities ...............................................................................18

Figure 3 : Operational process ..........................................................................................29

Figure 4 : Technical process .............................................................................................30

Figure 5 : ETKR performance assessment points ...........................................................40

Figure 6 : ETKR block diagram .........................................................................................43

Figure 7 : ETKR Centralised (Option 1A) ..........................................................................46

Figure 8 : ETKR Centralised (Option 1B) ..........................................................................46

Figure 9 : ETKR semi-distributed (Option 2) ....................................................................47

Figure 10 : ETKR testbed block diagram ..........................................................................50




EXECUTIVE SUMMARY

In the present situation, each of the ANSPs of the 40 EUROCONTROL Member States, either civil or military, is responsible for providing surveillance information to its Operational centre(s), collecting surveillance reports from their local sensors (Radar, ADS-B, WAM and ADS-C Target Reports), in some cases shared with neighbouring countries. In most of the cases, each ATC centre operates its own Surveillance Data Processing System (SDPS), meaning there are now about seventy Tracker systems deployed in Europe at a local level (i.e. in the respective ATC units), about half of them being ARTAS units. In parallel, most European nations operate their own national Air Defence system using Air Defence surveillance sensors together with own tracker systems.

This fragmentation and variety of the tracker technologies have both financial drawbacks and operational consequences, justifying the creation of a centralised European Tracker (ETKR) service with the objective to enable the optimisation of the Network performance in terms of safety, capacity and cost efficiency.

The ETKR service will enable the creation of a Europe-wide, consistent, high quality Air Situation Picture and the provision of its required subsets to any User of processed surveillance information, civil and military. It will replace the existing Surveillance Data Processing services for en-route and approach control as they are today deployed in the various ATC and major APP centres.

ETKR will provide the needed surveillance data, foster cooperation and defragmentation between ANSPs of different countries, thus reducing the need to invest and maintain all the current national surveillance equipment covering the national airspace. This reduction of cost will be achieved mainly due to less capital investment and less operating cost both at the level of the ATC centres and at the sensors sites, as less equipment will be needed at the centres, while the exchange of surveillance data will foster the rationalisation of the number of sensors needed, leading to decommissioning of those sensors considered as redundant and the upgrade or replacement of certain sensors by cheaper solutions. Furthermore, the sharing of the surveillance data will help to eliminate a few white spots with no radar coverage, marginal radar coverage or only single radar coverage, thus increasing safety and capacity.

The Service will implement the concept of dissimilar redundancy, whereby the Track Information Service will be delivered in parallel by independent ETKR Data Centres (EDCs), originated from two different Surveillance Data Processing System (SDPS) and distributed by redundant and reliable communication services provided by CS8, the Pan European Network Service (PENS). At the customer sites an ETKR Service Wrapper will ensure the reception of the ETKR service and distribution surveillance services as needed by the final users.

The Domain of Interest of the Service will be adequately covered by surveillance sensors providing good quality surveillance data allowing the generation by the Tracker of an Air Situation Picture suitable for five (5) and three (3) Nautical Miles separation. This will lead to the reduction of separation currently requested in the transfer of aircraft between ANSPs, according to their LOAs, thus leading to higher capacity values.

The sensors data will be provided to the EDCs through appropriate contractual arrangements or on the basis of regulatory requirements by ANSPs owning the ground sensors and possibly with other providers of surveillance dataThe ETKR deployment and operation will allow the ANSPs, in addition to the optimization of the Network, to become users of a uniform, high quality surveillance service, giving them the possibility of having the advantages of the economy of scale and better control of their surveillance related expenses.




INTRODUCTION

Introduction by the Director General of EUROCONTROL

Following a request of the European Commission in November 2012, EUROCONTROL developed the concept of Centralised Services (CS).

Version 2.0, dated March 2013 of the EUROCONTROL Proposal for a first set of nine Centralised Services to contribute to SES Performance Achievement is attached as Annex 3. A short description of the proposed CS is attached as Annex 4.

The Agency proposed the CS concept in order to significantly support:

the Member States and their ANSPs to reach or at least to come closer to the EU performance targets,

the implementation of SESAR results on a central pan-European level

the development of high tech solutions by European ATM manufacturers to be deployed on a central level providing the services to all ANSPs of the EUROCONTROL Member States,

the creation of pan-European operational concepts for the Centralised Services proposed

the creation of a pan-European market for these ANS support services

the implementation of market mechanisms for some ANS support services through tendering of the services with time limited performance based contracts

the creation of market opportunities for the ANSPs of EUROCONTROL Member States to provide services outside of their national boundaries, cooperating in newly founded consortia,

the strengthening of the European Network, increasing capacity and safety,

in the planning and execution phase much more user friendly 4 D trajectories throughout the European airspace

EUROCONTROL works closely with the Member States, ANSPs, civil and military airspace users, airports, the aerospace industry, professional organisations, intergovernmental organisations and the European institutions.

On 29 April 2013 EUROCONTROL invited the Airspace Users to participate in a workshop where the concept of Centralised Services was briefed. The Minutes of this Workshop are attached as Annex 5.

EUROCONTROL also invited the EUROCONTROL Member States on 4 March 2013, the ANSPs on 24 April 2013 and the ATM Manufacturing Industry on 17 May 2013 to demonstrate the Centralised Services concept. The minutes of these workshops are respectively attached as Annexes 6, 7 and 8.

Following the PC/39 on 16 May 2013 and PCC/31 on 2 July 2013 EUROCONTROL updated on the CS concept. The working papers and slides presented as well as an extract from the Minutes of both meetings are respectively attached as Annexes 9 and 10.

EUROCONTROL advisory groups such as AAB, NMB, MAB, CMIC, as well as EU bodies such as the SSC, ICB and its subgroups were briefed. These briefings were followed by so called CS specific workshops. This was a series of 9 workshops held in June and July 2013 - for each proposed CS one specific workshop was held; ETKR workshop was held on the 1st of July 2013. The slides presented as well as the minutes of this meeting are attached as Annex 11.




The questions asked and answered in an intensive dialogue since the beginning of the program are publicly available. We like to refer to the FAQ list that is constantly updated and available on the EUROCONTROL homepage.

The CBA figures presented in detail for all the nine CS support the initial assessment done, that a 150 to 200 million € cost reduction for the airspace users is possible through the implementation of the nine centralised services proposed by EUROCONTROL. Specific focus was put on the synergy effects foreseen between the different centralised services. It was agreed with the stakeholders, that the Agency would invite the participants to the individual CS workshops, as well as the existing EUROCONTROL advisory groups to participate in specific meetings in September and October 2013 to develop a pan-European ops concept for each of the Centralised Services.

This draft ops concept has been prepared for the presentation and discussion with all interested stakeholders at the Ops Concept Workshop for ETKR which will be held on 12 September 2013.

The Ops Concept will be used by EUROCONTROL to develop requirements to be part of a Call for Interest and a Call for Tender for ETKR. All proposed Centralised Services will be operated under performance based contracts by a Service Provider on behalf of EUROCONTROL.

Our partners are involved at every level of the corporate governance structure. The deployment and operation of CS will impact the remit of the Network Manager. Therefore, its governing body, i.e. the Network Management Board where the EC, EUROCONTROL, ANSPs, airspace user, airports and the military are represented could be extended in the future, the operation of the CS being supervised by EASA; the latter is already supporting the European Commission in the oversight of the Network Manager. Through its nomination as Network Manager, EUROCONTROL will be entrusted to manage the centralised services.

Frank Brenner

Director General of EUROCONTROL

October 2013




CHAPTER 1 –Context

1.1 Geographical applicability

The ETKR service is intended to be applied in all EUROCONTROL Member States. It may be expanded to adjacent States if so required as part of the NM area of interest and in case it is identified as being beneficial for the overall ATM network.

1.2 Aim

The objective of the ETKR is to eliminate the operational and financial drawbacks of the present situation by changing the present fragmented situation with a new concept that implements a centralised Europe-wide tracker service. This shift of paradigm of how the surveillance service is produced and distributed to its users is an enabler for the improvement of the Network performance in terms of safety, capacity and cost efficiency.

The creation of a Europe-wide, consistent, high quality Air Situation Picture and the provision of its required subsets to any User of processed surveillance information, civil and military, will replace the existing Surveillance Data Processing services for en-route and approach control as they are today deployed in the various ATC and major APP centres.

ETKR will participate to the benefits stemming from the deployment of the Centralised Service on 4D Trajectory Calculation for Planning Purposes (4DPP). The ETKR service will contribute to increase the accuracy of the trajectory by providing live radar tracks at a high update rate, thereby increasing the predictability and reliability through reduction of over- and under-deliveries.

1.3 Intended Audience

The intended audience are the CS3 CONOPS workshop participants and all the stakeholders who are interested in the development of CS3. The document will also be used to define the operational requirements for the Call-for-Tenders for the Centralised Service on the European Tracker Service (ETKR).

1.4 Intended Benefits

ETKR will have both operational and financial benefits.

The exploitation of a common Air Situation Picture (ASP) throughout the complete area of the EUROCONTROL Member States complying with the requirements for the performance and the interoperability of surveillance for the single European sky (SPI-IR [AD5]), will:

Strengthen interoperability between En-Route areas and/or operational sectors by potentially eliminating one of the obstacles for the establishment of the same




separation minima across the whole Domain of Operation of the Service. The network capacity is thereby increased, as operational staff at different centres and sectors have the same view of the traffic at the various points of the airspace and at the same time.

Ease the implementation of the same surveillance performance standard throughout the complete area.

Ease the implementation of new operational concepts across the complete area.

Participate to the ATM system design standardisation, enabling the introduction of new technologies for all customers at the same time as this can be materialised only once, at a central point.

Enhance the benefits stemming from the deployment of the Centralised Service on 4D Trajectory Calculation for Planning Purposes (4DPP). The ETKR service will contribute significantly to increase the accuracy of the trajectory, by providing live radar tracks at a high update rate, thereby increasing the predictability and reliability through reduction of over- and under-deliveries.

Facilitate the implementation of the Gate-to-Gate (G2G) surveillance, i.e. continuous aircraft surveillance from Airport to Airport, by improved interoperability with local surveillance systems.

Create opportunities for innovations in the areas of surveillance techniques and tools that will further be exploited by the operational staff.

Harmonising the tracker infrastructure and fostering the exchange of surveillance data will:

Reduce the cost of capital investment for new SDPS and subsequent adaptations at national level.

Reduce the operating cost both at the level of the ATC centres and at the sensors sites. As the trust on the service will increase, the local surveillance environments might be considered redundant, leading to their de-commissioning and further reduction of the site deployment and operating cost.

Be the catalyst for the optimisation of the surveillance sensors environment. Using a fusion system covering the whole Europe will reveal which sensors are essentially contributing to the quality of the ASP and which are not. In this way, the service will foster the rationalisation of the number of sensors needed, leading to decommissioning of those sensors considered as redundant and the upgrade or replacement of certain sensors by cheaper solutions.

Reduce the cost of implementation of new technologies (e.g. WAM, ADS-B and Multi-static PSR).

Reduce the cost of implementing new User’s requirements, as this will be implemented once centrally, making implementation in each site superfluous.

Enable operational benefits that will be materialised by the improvement of ATM functions making use of an integrated, high performance Air Situation Picture and thus contribute to further cost reduction.

Create opportunities to the European Industry to develop high tech solutions and export that know-how to the rest of the World.




CHAPTER 2 –Operational Concept

2.1 Scope

2.1.1 Current Situation

The size of the European airspace is about 4.000 NM from West to East and 3.000 NM from North to South. In this airspace, there can be up to 15.000 surveillance targets simultaneously, taking into account all IFR/VFR airborne traffic. There are at present around 500 Radars and 200 Ground Stations for ADS-B and/or Wide Areas Multilateration (WAM).

In the present situation, each of the ANSPs of the 40 EUROCONTROL Member States, either civil or military, is responsible for providing surveillance information to its Operational centre(s), collecting surveillance reports from their local sensors (Radar, ADS-B, WAM) and ADS-C Target Reports, in some cases shared with neighbouring countries. In most of the cases, each ATC centre deploys and operates its own Surveillance Data Processing System (SDPS), meaning there are now about seventy Tracker systems in Europe deployed on local level (i.e. in the respective ATC units), using either the EUROCONTROL ARTAS system or another surveillance fusion technology.

The ASTERIX data format is more and more used for the exchange of sensors and SDPD data both in civil and military environments.

This fragmented situation leads to an increased cost, but in addition to the cost of deploying tracker technology in each European Centre, there are other than financial drawbacks. A consequence of the implementation of different technologies in adjacent centres is that the Air Traffic pictures of these centres are not perfectly aligned and do not have the same level of quality. This is one of the main factors leaving room for the application of different separation minima at different places in Europe, impacting on the overall Network capacity.

2.1.2 Scope of ETKR

ETKR will enable the creation of a consistent, high quality Air Situation Picture (ASP) covering the Member States of EUROCONTROL and the provision of its required subsets to any User of processed surveillance information, civil and military. The service is mainly intended for the En-Route and Approach control. Its exploitation for other purposes and by other organisations should not be excluded. ETKR will not be responsible for the investment and operation of sensor equipment, but will make the processed data available to all ANSPs.

ETKR will not cover ground surveillance1. The reason is that the total number of local sensors that would have to be processed over Europe in this case would induce a tremendous processing load. In order to enable the Gate-to-Gate surveillance, the approach will be to implement local processors that will merge ETKR data stream with local sensors.

1 The ASP, however, provided to an Approach Service can be made available to the Tower Service for monitoring purposes.




As mentioned in the Benefits section above, ETKR will strengthen interoperability between En-Route areas and/or operational sectors by potentially removing one of the main obstacles for the establishment of the same separation minima across the whole Domain of Interest of the Service.

The possibility for augmenting the service by other surveillance data based services like Short Term Conflict Alert (STCA) or Minimum Safety Altitude Warning (MSAW) should be further studied.

2.2 Service Concepts and Components

As presented in Figure 1: ETKR below and Figure 3 : Operational process of ANNEX 1 –Information flows, the ETKR Service, will be provided by the ETKR data-centre(s) (EDCs).

The EDCs will merge traffic data provided by surveillance sources (PSR, SSR, Mode S, ADS-B and WAM) and ADS-C Target Reports to produce a unique, system-wide reference of the actual air traffic situation (including DAPs) to be distributed to the Service Customer Sites. The provision of the surveillance data will be originated from the existing civil and military sensors infrastructure.

The Data Centres will ensure 24hours/day and 7days/week operations and reducing the operating cost.

The whole Domain of Interest of the Service is assumed to be covered by the sensors in an optimum manner, allowing the generation of an ETKR Air Situation Picture (ASP) enabling the application of five (5) NM and three (3) NM separations.

Both the provision of surveillance data by the sensors and the distribution of track information to the customers will be executed over Europe-wide WAN communication architecture.

At the Service Customer sites, an ETKR Service Wrapper (ESW) containing network gateway functionalities will be deployed to connect to the ETKR. A local back-up SDPS system, running under the responsibility of the Customer, could be used as a last resort solution2.

Figure 4 : Technical process of ANNEX 1 – Information flows, indicates the various stakeholders and their systems, relevant to the Service and what has to be developed and updated by each one of them.

In the following sections, the main functional components are described. Further ETKR features are described in ANNEX 12 – ETKR Service Features while the physical architecture and components can be found in ANNEX 13 – ETKR System Architecture.

2.2.1 Overall Concept

Figure 1 below depicts the high level architecture of the service and the overall concept. The various actors will be connected onto WAN infrastructure, using ASTERIX for the exchange of surveillance data.

2 It is noted that the potential Local Back-up tracking system is not considered part of the ETKR and deployment will be under

the responsibility of the Customer. The issue, however, will be addressed as part of the safety work during the feasibility/demonstrator Phase (Phase1).




Figure 1: ETKR Overall Architecture

2.2.2 Sensor data provision

Surveillance data will be provided to the EDCs by the ANSPs owning the ground sensors and also with alternative commercial providers of surveillance data3. Surveillance data from military organisations can be used as well, provided that adequate arrangements are in place.

The organisation responsible for the provision of the sensors data will also be responsible for the quality, reliability and availability of the sensors; the delivery point will be a PENS access link via a gateway (e.g., SDDS).

2.2.3 Customers sites

The main customers will be the ANSPs requiring ETKR data for ATC purpose, as well as the Network Manager itself for the execution of its functions.

ETKR service tracks will be distributed to the ATC processing systems for use and operational exploitation in the ACCs and major APPs and to the other Centralised services as needed. Such systems or services, referred to as Users of ETKR, comprise all tools exploiting track information such as Flight Plan Processing Systems, Display System managing the CWPs, Short Term Conflict Alert, etc. It shall be noted that the correlation of tracks with Flight Plan Data will not be provided by ETKR.

Outside the ATC Centres, Airports and Air Defence systems will be either direct customers of ETKR, i.e. connected to ETKR, or users, in which case they will receive track information from an ATC Centre, potentially supplemented with basic flight data.

3 This latter case refers to potential ADS-B proprietary networks.




Other European organisations or Agencies may request to take advantage of the service to assist them in carrying out their missions.

ETKR is provided to its Customers through appropriate arrangements. The relevant subsets of surveillance tracks are distributed on the basis of a Service Level Agreement (SLA).

2.2.4 Provision of Communication services

Communication Network services are needed for receiving the sensors messages and distributing the resulting ASP(s) to the Customers. CS8 PENS Centralised Service will be used for this purpose.

Contractual arrangements will be put in place that will include Key Performance Indicators (KPIs) for the provision of the Services. KPIs for the Communication Services are to be guaranteed.

2.2.5 Post Operations Performance

A post operations performance analysis of the service will continuously take place in order to improve its quality and reduce the cost. Areas expected to be improved are, e.g.

Those operational functions that are based on the surveillance services.

The optimisation of the number of sensors providing data, particularly when sensors of newer and cheaper technologies are deployed.

The support to surveillance data providers to share infrastructure investment and operating costs.

The optimisation of the Network related services.

As the trust of the service is increased, the magnitude of the local surveillance infrastructure might be reduced avoiding the otherwise needed replacement after the end of the lifecycle, as data are shared across the national boundaries to a much higher extend than currently. It is understood that all interested parties will be involved in this decision.

2.3 Roles and responsibilities

2.3.1 Overview

The operational importance of the ETKR service, providing an essential ATM service in a large region with high traffic volumes, requires a clear and unambiguous allocation of roles and responsibilities to the various stakeholders in order to ensure a smooth, efficient and effective provision of this service. Figure 2 shows the identified roles and links to other Centralised Services which are further detailed in the subsequent paragraphs.




Figure 2 : Roles and Responsibilities

2.3.2 ETKR Service Provider

The ETKR Service Provider for the provision of the ETKR Service is a consortium of organisations and/or companies that through a contractual arrangement with NM will provide the service. They will be responsible to:

Operate the service according to their contractual obligations (including Service Level Agreements).

Monitor the service quality and report to the Customers any deterioration of the service.

Deploy the infrastructure for the provision of service.

Carry out the relevant safety related studies.

Provide maintenance and operational support to the whole ETKR technical infrastructure, including second level maintenance for the equipment (e.g. service wrappers) located at the Customers’ sites.

Manage outsourced activities where required.

Participate in and approve the implementation of the software developments for the Technical Infrastructure as it will be required for the implementation of the selected architectural option. This includes the verification and validation activities.

ETKR

(CS#3)

Network

Manager

ASP

Surveillance DataSurveillance

Data

Provider

Provider

User

Management

EAIMS

(CS#5)

4DPP

(CS#2)

WAN InfrastructurePENS

(CS#8)

SLA Surveillance Data Delivery

Customer

Track Information

Service

SLA Service Provision

Network

Manager

EAD Data

NIPS

(CS#7)

SSM




Be responsible for the performance up to the delivery of data out of the local ETKR Service Wrapper.

Issue a Declaration of Suitability for Use and Declaration of Conformity.

Report to the various bodies.

Provide SES certificates, if and where applicable.

In order to rapidly resolve technical issues with operational impact, an adequate organisation structure has to be created by the Service Provider, allowing quick decisions at any time (24H7).

2.3.3 Customers (ANSPs and Others)

An ETKR customer is a Legal body that operates any site or cluster of sites, civil and military, public or private, making use of track data generated by and distributed through the ETKR Service. The responsibilities of the customers comprise (non-exhaustive) to:

Sign and comply with relevant Service Level Agreement(s) if required.

Ensure the local maintenance and operational support of the equipment interfacing to the EDC(s).

Verify that the track data delivered by the ETKR SP meet the specified performances and availability for their operations

Carry out Safety Cases for their environment.

Immediately report any deterioration of the Service and take the foreseen mitigation measures.

2.3.4 Surveillance Data Providers (ANSPs and Others)

An ETKR surveillance data provider is a Legal body that operates any site or cluster of sites, civil and military, public or private, providing surveillance sensor data to the EDC for the elaboration of the Air Situation Picture. Their responsibilities comprise (non-exhaustive) to:

Sign and comply with the relevant Data provision Agreement(s)

Ensure the provision of surveillance sensor data to ETKR with the expected quality and availability from their surveillance sensors.

Take care of the adequate coverage with surveillance data in their national/regional territory.

Coordinate with EDC as required for coverage planning, management, monitoring and preventive maintenance scheduling.

Immediately report any deterioration of the Service and take the foreseen mitigation measures.

2.3.5 EUROCONTROL as Network Manager

With respect to the ETKR service, the role of NM will comprise (non-exhaustive):

Management of the procurement process up to the selection of the architectural option to be implemented.

Management of the contractual arrangements and Service Level Agreements as needed for the establishment of the Service and the Demonstrator.

Supervision of the software developments for the Technical Infrastructure as it will be required for the implementation of the selected architectural option, up to the moment




of its deployment.

Monitoring of the setting up of the maintenance and operational support required by the Service.

Chairing of the Customers Technical Groups.

Supporting the Customers (ANSPs and Others) in the assessments of optimal (cross national borders) surveillance provision

Supporting the Surveillance Data Providers (ANSPs and Others) in providing the required coverage/quality/availability in a most cost efficient manner on a cross national border basis

Holder of either exclusive or full but not exclusive IPRs of the various sub-systems required by the service (ARTAS, Dissimilar Tracker, Wrappers, any other functional component needed).

Issuing Declaration of Suitability for Use for those constituents of the system, as required by the SES regulations.

2.3.6 CS8 – PENS

The Pan European Network Service (PENS), CS8, is a Centralised Service providing the underlying ground communication infrastructure between sites and partners. It is an expansion of the current PENS for handling increased data interchanges.

The ETKR Service will use PENS for receiving sensor data from the Surveillance Data Providers at the delivery PENS access link via a gateway (e.g., SDDS) and transmitting the ETKR Track Information Service to the Customers and other Centralised Services (CS2). PENS is therefore an essential component for the ETKR service provision, imposing requirements for a reliable communication infrastructure with very high availability and redundancy; therefore it is expected to have different access links to connect to different PENS cores such that a disruption will not impact the overall end-to-end connectivity

2.3.7 CS5 – EAIMS

The European ATM Information Management Service (EAIMS) is the evolution of the existing EAD service, to include all pre-departure static and dynamic data (e.g. airport information, weather and digital NOTAMs) and to enable the acceleration of the early deployment of the SWIM technology.

The ETKR Service will become a user of EAIMS Centralised Service for the provision of geographical and aeronautical data such as Runway, SID & STAR, etc.

2.3.8 CS2 – 4DPP

The 4D Trajectory Calculation for Planning Purposes (4DPP) is a Centralised Service for calculating and communicating 4D trajectory profiles with high accuracy, leading to improved predictability in the planning phase.

4DPP is as well a direct user (direct feed of ETKR data) as an indirect user of the ETKR data since it is using the Correlated Position Reports (CPRs) i.e. ETKR tracks correlated with Flight Plan related information at ATC level.

2.3.9 CS7 – NIPS

The network Infrastructure Performance monitoring and analysis Service (NIPS) ensures the safe function and anomaly resolution of common/distributed CNS infrastructure. This service sets-up and operates sensors so that performance of the infrastructure can be measured and




issues resolved.

NIPS will exploit the Sensor Service Messages (SSM) received from ETKR, as needed in particular for detecting GPS outages having operational impact in the frame of Precision Based Navigation (PBN).

2.4 Safety and Performance

The OSED is a key element of the GEN-SUR Safety and Performance Requirement document (GEN-SUR SPR - [AD1]) that provides the minimum operational, safety and performance requirements for a Surveillance System supporting Air Traffic Control (ATC) Services. GEN-SUR system includes people, procedures and equipment and addresses spatial, aircraft and ground domains of the surveillance system.

GEN-SUR SPR offers a top-down process for the derivation of the ground surveillance requirements and assumptions to support Air Traffic Control (ATC) Services in typical operational environments. The Airborne domain is assumed to be conform with the European Commission (EC) Surveillance Implementing Regulation (1207/2011) laying down requirements for the performance and the interoperability of surveillance for the single European sky (SPI-IR - [AD5]) In addition, a number of safety assessment requirements are also included as part of the EC 1035/2011.

Over the past years, the main document used for surveillance requirements had been the “EUROCONTROL Standard document for radar surveillance in En-route airspace and major terminal areas” (The document is referred to as the “Blue Book” - [AD6]). It has been recently supplemented by the “EUROCONTROL Specification for ATM Surveillance System Performance” (ESASSP - [AD8]). However, these two documents do not address the safety aspects as required by the above regulations.

The ETKR safety requirements will be derived from the operational service analysis, following the GEN-SUR SPR model.

A complete safety assessment, including Functional Hazard Analysis, will be conducted, taking into account the overall ETKR service architecture comprising both EDC and Customer site levels.

It is assumed that the required Safety analysis will be carried out at the Customer’s site, under his responsibility, before the ETKR Service is operationally exploited.

2.5 Security

For confidentiality reasons, Surveillance Security aspects are processed separately from GEN-SUR SPR and are not publicly released. They are developed as part of a specific document (GEN-SUR SEC). This is carried out in coordination with the Civil Military ATM Coordination Division/Security Unit (CM-SEC) which is the EUROCONTROL contact point for these activities. External coordination is taking place through NEASCOG (NATO EUROCONTROL ATM Security Coordinating Group), ICAO Threat and Risk Working Group, EUROCONTROL SET (Security Team). SESAR WP 10.06.02 is involved regarding Security Methodology. Related areas of work are SESAR WP 15.4.5 ("Surveillance Ground system Enhancement for ADS-B) and EUROCAE WG51-SG4 ("Composite Ground Station Specifications)

The GEN-SUR SEC model [AD2] includes a proposed approach for security risk assessment on a generic surveillance system that is supporting an ATS service (for area and approach control services). It includes threat scenario identification and operational impact




assessment, leading to an initial security risk assessment and the identification of related mitigation means.

ETKR shall be resistant to any attempt of intrusion.

On the operation side, procedures shall be defined such that sufficient control over ETKR infrastructure elements is granted to ETKR staff. This may comprise authorisation to intervene on local sites.

The security arrangements will be made confidentially available to the Customers, to allow them, amongst others, to ensure the compliance with their own internal security policy and implementation.

The interconnection of ETKR with military organisations will be an area of specific security requirements and may have to be done through secure gateways.

2.6 Reliability and Availability

ETKR will deliver an essential and safety critical service to the Customers. A degradation or failure of this service may potentially impact the safety and capacity in a large region with high traffic volumes. It is therefore regarded as inevitable to apply high standards for reliability and availability of this service.

The concrete availability and reliability requirements will be determined by both the GEN-SUR SPR and the Customer’s local safety assessment..




CHAPTER 3 –Regulatory requirements

3.1 Existing applicable regulation

3.1.1 Operational Requirements

The aim of Surveillance is to provide means to the ATC Controller to see the position and trajectory of all aircraft in their domain of responsibility in order to support the application of given separation minima.

At ICAO level, the general requirements for the Surveillance Services are defined in Chapter 8 of the Air Traffic Management, Procedures for Air Navigation Services, (Ch8 PANS/ATM - [RD1]),

The typical Operational Requirements for Europe derived from Ch8 PANS/ATM are defined in the Operational Service and Environment Definition (OSED) document (GEN-SUR SPR - [AD1]). The OSED describes the ATC services, the surveillance System in terms of surveillance information provided to the controllers and associated procedures, and the assumptions about the environment in which the surveillance System is specified to operate.

In the case of military users of ETKR services operational requirements are twofold. Military ATC has the same major operational requirement as civil to ensure safety of Air Traffic in all phases of flights whereas the major operational requirement of Air Defence is to ensure security and sovereignty of the respective nations.

3.1.2 European Union Regulatory Framework

At the level of the European Union, no regulatory provisions address yet the centralised services, and the ETKR in particular. However, the following regulations are worth considering:

Regulation (EC) No 552/2004 of the European Parliament and of the Council of 10 March 2004 on the interoperability of the European Air Traffic Management network (as amended)

Regulation (EC) No 551/2004 of the European parliament and of the Council of 10 March 2004 on the organisation and use of the airspace in the SES, (as amended) in particular its Article 6

Commission Regulation (EU) No 677/2011 of 7 July 2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions and amending Regulation (EU) No 691/2010 (as amended), in particular its Article 4.1 which provides that the Network manager shall perform a number a tasks to support the execution of its functions. He shall notably:

o provide a consolidated and coordinated approach to all planning and




operational activities of the network (Art. 4.1 (g))

o support the different operational stakeholders in the execution of the obligations that are placed on them in the deployment of ATM/ANS systems and procedures (Art. 4.1(i);

o ensure appropriate operational coordination, as well as optimisation, interoperability and interconnectivity within its area of responsibility (art. 4.3 (c));

Commission Regulation (EU) No 1207/2011 of 22 November 2011 laying down requirements for the performance and the interoperability of surveillance for the single European sky and

“Commission Regulation (EC) No 482/2008 establishing a software safety assurance system to be implemented by Air Navigation Service Providers (as amended).

It is assumed that the implementation of the ETKR concept will facilitate and improve the execution of the objectives set by these provisions.

The following regulations, related to the oversight should also be considered:

REGULATION (EC) No 216/2008 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 20 February 2008 on common rules in the field of civil aviation and establishing a European Aviation Safety Agency (as amended)

COMMISSION IMPLEMENTING REGULATION (EU) No 1034/2011 of 17 October 2011 on safety oversight in air traffic management and air navigation services and amending Regulation (EU) No 691/2010 (as amended): Article 3.d of this Regulation foresees that the safety oversight of organisations providing pan-ATM/ANS is exercised by EASA

Finally, the European Commission has issued in its Communication of 11 June 20134 a proposal to revise the SES package, with a view notably to reinforce the role of the network manager. The proposal also covers the new notion of ‘support services’ to ATS, which correspond to the centralised services proposed by EUROCONTROL.

3.2 Requirements for new/updated regulations to implement the CS#3 ETKR

The development and implementation of the ETKR centralised service would ideally benefit from the following regulatory actions:

3.2.1 Requirements related to the EU framework

A provision in the SES Regulations is necessary to make the technical migration to the future centralised services (or ‘support services’) mandatory for stakeholders concerned (e.g. by a further amendment to Regulation No 677/2011), make the data delivery from the Surveillance Data Providers mandatory, require the acceptance of the concept, that the data will be shared for the benefit of all. It would need to ensure that:

the Surveillance Data Providers are delivering the required input data to operate the ETKR service, maintaining the sensor infrastructure as required by ETKR, coordinating changes to the sensor infrastructure with ETKR, establish Service Level Agreements with ETKR and respecting them,

the use of the ETKR service by the Customers (in particular ANSPs) is mandatory.

4 Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Committee of the Regions “Accelerating the Single European Sky” of 11 June 2013 (COM (2012) 408 final)




3.2.2 Requirements related to the EUROCONTROL framework

The ETKR will be implemented as a Pan-European Service in the applicability area of the EUROCONTROL Member States. To unlock the full benefits for the Network on one side and the ANSPs and other operational stakeholders on the other side, it is pivotal that all Member States cooperate in the set-up and implementation of the service.

While the above-mentioned EU regulations will apply to EU Member States and their operational stakeholders, as well as ultimately to non EU Member States bound by these Regulations because of relevant agreements with the EU for the implementation of aviation regulations (e.g. ECAA), the intention is to achieve consent in the Provisional Council and Permanent Commission of EUROCONTROL to make full use of the procedures in all EUROCONTROL Member States.

Therefore, it is expected that by a Decision, the Permanent Commission of EUROCONTROL will make the centralised services and their related conditions binding on all the EUROCONTROL Member States and their operational stakeholders. The EU regulatory framework would just reinforce this obligation for the States concerned.

3.2.3 Requirements related to the national legal/regulatory frameworks

Updated/amended EU regulations are directly applicable in the EU Member States and would not require measures at national level.

For EUROCONTROL Member States not bound by EU Regulations, appropriate rules and regulations would have to be adopted at national level to comply with the obligations deriving from the decision of the Permanent Commission of EUROCONTROL.




CHAPTER 4 – Links of the CS#3 ETKR to ICAO GANP,

SESAR deployment, ESSIP – current procedures and

future evolution

4.1 Baseline – Interim Deployment Programme (IDP)

Centralised Services (CS) are in line with the Interim Deployment Programme (IDP). The conformity analysis was initiated by EUROCONTROL and further completed at the Interim Deployment Steering Group (IDSG) Expert Team in the meeting of 27 June 2013.

The possible relationships between CS and IDP deployments have been analysed and clustered in four categories of potential interactions, which are:

1. No relationships between IDP activities and CS. This means that the functions and services deployed in a centralised manner by the CS do not directly interface any of the deployments of the IDP.

2. IDP deployment is improved by the independent CS capabilities. The functions and services deployed in a centralised manner by the CS will be used by one or several IDP deployments but in an independent way. This is the case when CS does not impact functionalities already deployed, i.e. Independent function improvements, or when the CS implements some add-on function or services such as equipment performance monitoring, centralised management of shared parameters, i.e. Development of supporting option.

3. IDP is a pre-requisite for CS. This means that the functions and services deployed in a centralised manner by the CS reuse an IDP deployment.

4. IDP deployment is an alternative to the CS solution. The functions and services deployed in a centralised manner by the CS offer a different implementation of an IDP deployment.

The ETKR centralised service proposes to replace the use of local Surveillance Data Processing (SDP) by the use of a centralised European Tracker Service, which is a system rationalisation in support of ATC and to facilitate the compliance with the Surveillance performance and interoperability (SPI) Implementation Regulation (EU) No 1207/2011. This centralised service is categorised as no relationships which means that there is no IDP activity that deals with surveillance data and that there are no direct relationships / interfaces between surveillance data management and IDP deployments. So, the improved surveillance data are not directly related to current planned IDP activities.




As there are no relationships / interfaces, there are no cross-benefits between IDP and the ETKR centralised service.

4.2 Pilot Common Projects (PCP) and Common Projects (CP)

Centralised Services interact with the Pilot Common Project (PCP). Interdependencies between Centralised Services and the six ATM Functionalities (AFs) of the Pilot Common Projects (PCP) have been analysed.

The Centralised Services will influence the future Common Projects (CP).

There are no relationships between the ETKR centralised service and the PCP ATM Functionalities.

4.3 European Single Sky ImPlementation (ESSIP)

The possible relationships between CS and ESSIP, being the Level 3 of the European ATM Master Plan, have been analysed.

The ETKR centralised service is categorised as independent function improvements and is related to the ESSIP Objective ITY-SPI “Surveillance performance and interoperability”.

Depending on the evolution of the ETKR centralised service, in future, new ESSIP Objectives may have to be developed or existing ones may have to be amended.

4.4 ICAO Global Air Navigation Plan (GANP)

The possible relationships between CS and ICAO Global Air Navigation Plan (GANP) have been analysed.

The ETKR centralised service and ICAO GANP in perspective ensures increased efficiency of a fully interoperable surveillance capability including data fusion, notably in B0-ASUR – Initial Capability for Ground Surveillance.

Furthermore, it is enabled by IPV-6 ground network in GANP COM roadmap (CS8 – Pan European Network Service (PENS)).

4.5 Current procedures and future evolution

Currently, all the procedures for acquisition, setting up (and possibly development), exploiting and maintaining the tracker service is fragmented. It is under the responsibility of each provider. More specifically, the sensors are deployed according to the needs of each centre, without considering the implications to the whole Network. The system design of the surveillance infrastructure are defined, procured and deployed according to locally developed concepts. The performance monitoring of the sensors and the track information service, the investigation of technical incidents caused by problems of the sensor infrastructure or airborne equipment, as well as the sensor coverage monitoring and coordination are all done in isolation at the level of each centre, not necessarily using the same tools5. Exception is

5 The tracker services are now obliged to ensure that the applicable performance regulation (i.e. SPI-IR) and user requirements

are met by the end of 2013.




made only for the deployment of the ARTAS system where the further development, exploitation and operational support and maintenance is governed by the ARTAS adopted procedures.

Moving to ETKR Service, the Customer will not have to worry any longer with many of Primary and other Lifecycle Processes as they will be carried out centrally, e.g., introducing a new sensor or decommissioning of an old sensor will be done according to the needs of the ETKR service, procurement and maintenance of the major part of the centre surveillance infrastructure will be carried out by the Network Manager, leading to the harmonization of the whole infrastructure. Technical incident investigation, sensor maintenance coordination and coverage monitoring will be done only once by the ETKR service. As a result the consistent Air Situation Picture centrally produced and distributed across the whole Network, will contribute to increased safety and capacity and steer the development of new tools for increasing the productivity of the operational staff.

Finally, ETKR service will implement all the relevant evolutions stemming from the WP15 (CNS system) of the SESAR Joint Undertaking.




ANNEX 1 – Information flows

A1.1 Operational process

Figure 3 : Operational process




A1.2 Technical process

Figure 4 : Technical process

Legend:

= CS#3 development

= NM development / upgrade

= NM development / upgrade

= Stakeholder development / upgrade

B2B: Business-to-Business

B2C: Business-to-Consumer

FDPD: Flight Data Processing and Distribution

SWIM: System Wide Information Management




ANNEX 2 – Data Set

A2.1 Sensor Data Input

Groups of sensors are connected at a given site (e.g. ACCs) and are then concentrated and streamed to the ETKR Data Centres (EDC) via the gateway (e.g. SDDS). In order to avoid single points of failure, sensors shall be connected to at least two sites.

All the various types of messages (PSR, SSR, Mode S, ADS, WAM) arriving at the EDCs shall conform to the latest approved and released version of ASTERIX categories CAT001 & CAT002 (Primary and secondary radar data), CAT034 & CAT048 (Mode-S radar data), CAT020 & CAT019 (Multilateration data) and CAT021, CAT 023 (ADS-B data) and CAT 221 (ADS-C Target Reports). To support the usage of Enhanced Mode S (EHS) information, the extraction of Down-linked Aircraft Parameters (DAPs), in particular those being part of the Mode S Enhanced Surveillance specification, i.e. BDS registers 4-0, 5-0 and 6-0, are required for every scan for those sensors essential to maintain sufficient Mode-S coverage.

The useful set of sensors to build the ETKR ASP will be determined as part of the Demonstrator. Some rationalisation is expected i.e. not all surveillance ground sensors may be required to feed ETKR in order to meet the SPI-IR requirements (see section A12.3.1) and the performance standards as stated in Section A12.4.4 Performance monitoring.

A2.2 Track information Output

The customers, including CS2, will connect and get access to the service throughout a publish/subscribe type of interface.

The ETKR Service will deliver surveillance data to the Customer Site in the latest approved version of ASTERIX categories CAT062 (system track data, CAT063 & CAT065 (SDPS status messages).

Amendment of these categories, in particular CAT063 & CAT065 may be required to accommodate specific ETKR monitoring and control messages.

A2.3 Airspace Data

Dynamic Airspace data stemming from CS5 EAIMS will be used.




ANNEX 3 – EUROCONTROL Proposal for a first set of Centralised Services to contribute to SES Performance Achievement, March 2013

ANNEX 4 – Brief Description of Centralised Services

ANNEX 5 – Minutes of the 29 April 2013 Airspace Users CS Workshop

ANNEX 6 – Minutes of 4 March 2013 Member States CS Workshop

ANNEX 7 – Minutes of 24 April 2013 ANSPs CS Workshop

ANNEX 8 – Minutes of 17 May 2013 Manufacturing Industry CS Workshop

ANNEX 9 – Working papers, slides and extract from the Minutes of PC/39, 16 May 2013

ANNEX 10 – Working Papers, slides and extract from the Minutes of PCC/31, 2 July 2013

ANNEX 11 – Slides and Minutes of CS#3 Workshop of 1st of July 2013

These annexes are provided in a separate file.




ANNEX 12 – ETKR Service Features

A12.1 Service level

The ETKR service will be provided twenty-four hours per day, seven days per week, with availability close to 100%6. In any case, the Service will ensure that the total number and the quality of the data streams will improve the existing situations in the various operational sites and in the worst case will not lead to any regression compared to the present situation.

A quality monitoring function of the Sensor data will be available at the ETKR Data Centres (EDC’s). The results of the quality monitoring shall be made available as an added value to the Sensor Operators in order to improve the overall service quality.

Quality monitoring data of the Service will be available at the EDC’s and accessible by the Customer sites. The Customer Sites may perform additional quality monitoring of the Service at their discretion.

A Central support structure operated by the ETKR service provider will ensure the Operational Maintenance and Support of the Service, as well as the further development of the components of ETKR.

The local support of the entry nodes and exit nodes will be provided by the respective data user or data provider, mainly the ANSP Centre/site connecting to the EKTR

A12.2 Track Information Service

With the ETKR model, the Track Information Service will replace the existing Surveillance Data Processing System (SDPS) infrastructure.

The Track Information Service refers to the provision of track data to the customers as a subset of the Air Situation Picture (ASP), according to customer specified characteristics.

Optimally, a unique ETKR ASP covering the whole Domain of Interest of ETKR should be adequate to address all Customers’ needs. However, it cannot be excluded at this stage that a unique ETKR ASP would not be sufficient to address specific and justifiable Customers’ requirements; consequently, the Service will be flexible enough to provide, in exceptional cases, additional ETKR ASP(s) (e.g. requiring specific tuning of the tracker or additional local sensors) according to the needs of Customers or Groups of Customers.

ETKR will implement the concept of dissimilar redundancy (see Annex A13.2), whereby the

6 Safety analysis during the Feasibility phase will show how many seconds of unavailability of service is accepted (e.g., two

seconds), the frequency of failures, etc. The overall figure will be cascaded down to the availability of the various components of the service.




Track Information Service will be delivered in parallel by two independent ETKR Data Centres, originated from two different SDPS. It will be the decision of the Customer to select either one or the other data stream as the main source for their operations, and to switch from one to the other. In this case, the switch-over will be as transparent as possible to the Customer.

As already mentioned in the Footnote 2 the ETKR does not include in its scope a local backup system. This topic will be further analysed during the feasibility phase. This does not prevent the Customer however to deploy and operate a local back-up system,if felt necessary beyond the redundancy of dual operation in addition to the dissimilar software already foreseen and operated by the ETKR.

A significant flexibility is designed to suit a wide range of Customer requirements in terms of track information service.

Through the connection protocol to ETKR, registered Customers have the possibility to define which type of track information service they need, in terms of Domain of interest and Update rate.

A12.2.1 Customer area of interest

The area of interest is a customer specified 3D geographical area, totally enclosed within the ETKR domain of operation, from which they want to receive all or subsets of tracks. In case not all tracks are needed, typical track selector allows specifying additional filters on the basis of e.g. Aircraft Id (ACID) and tracking number.

A12.2.2 Update rate

The update rate defines when and how the track updates shall be delivered by the ETKR Data Centre. It does not take into account any consideration on the latency over the network. This will have to be treated at Customer level. Three update modes are considered, corresponding to different use of track information:

Asynchronous: the characteristic of this mode is to provide track updates as soon as they are available in the Tracker. There is, however, a minimum period between two consecutive updates of the same track, e.g. 0.5 second,

Periodical: the characteristic of this mode is to provide adjacent tracks at the same age (which is not the case in asynchronous mode). The period may range from 3 seconds to 3 minutes (TBD). Track updates are then sent according to a sliding window technique, scanning the complete domain of interest during the specified period.

Radar synchronised: the characteristic of this mode is to provide track updates in synchronisation with the rotation of customer specified radar antenna.

A12.3 Sensor coverage management

A12.3.1 Configuration of ETKR Sensors

It shall be ensured that the whole Domain of Interest of the Service is adequately covered by surveillance sensors providing good quality surveillance data to allow the proper functioning of ETKR.

The required (optimum) surveillance coverage will be defined in order to ensure that the applicable performance regulation (i.e. SPI-IR) and user requirements are met.

The selection of sensors will be coordinated between the customers of the ETKR service and




NM, as ultimate responsible party for the service. The ETKR Service Provider will establish Service Level Agreements (SLAs) with the Sensor Operator(s).

To meet this objective, the following stepwise approach shall be followed

Inventory: an inventory of the existing sensor infrastructure will be performed, resulting in the set-up of a common database containing all the sensor characteristics. In the case of military sensors classified characteristics may be excluded.

Operational coverage definition: the current operational requirements in terms of sensor coverage, applicable separation minima, airspace volume in which and traffic to which the ATC service is provided, will be specified.

Selection: sensors (radar, WAM system, ADS-B ground station) will be qualified as a potential candidate for input to ETKR when they meet, as a minimum, the respective applicable performance requirements as described in section A12.4.47.

Sensor configuration design: this will lead to the definition of an optimal multi-sensor configuration as input to ETKR, taking into account many factors such as:

o Essential Sensor for APP

o Essential Sensor for ACC/UAC

o Sensor Type

o Sensor Information Update Rate

o Sensor Availability

o Sensor Obsolescence or Used as Temporary Back-up

o Sensor Supporting Specific Applications (e.g. other than 3 NM and 5 NM separation applications, like PAM)

o Any additional local consideration (e.g. Radome protection, etc.)

As a basic principle for redundancy reasons, each sensor used as input to ETKR shall be connected to two independent network access points, via a gateway (e.g. SDDS).

A top-down analysis will be performed, based on the SPI-IR and separation requirements, to determine the required types of overlapping coverage. The definition of the optimum sensor configuration is likely to result in proposed rationalisation of the existing infrastructure, e.g. with recommendation to decommission overlapping sensors and to replace or upgrade existing sensors with cheaper solutions. Such recommendation will be issued to the NM governance that will decide how to implement the proposed rationalisation measures.

A relevant methodology that will also be considered for the rationalisation of the ANSPs surveillance infrastructure – as a means to improve the ratio of performance versus cost of the infrastructure whilst also considering a range of pertinent Key Performance Areas – is the Methodology to Support a Rationalisation of the Surveillance Infrastructure, part 1 & 2, a deliverable (D10-01) of SJU project 15.04.01see [RD7].

A12.3.2 Sensor Planning and coordination

A centralised planning of sensor maintenance arrangements used in ETKR shall be elaborated, co-ordinated and maintained up-to-date.

A database of points of contacts (PoC) for immediate and non-immediate actions with

7 If the sensor does not comply with the corresponding standard and still is considered to be ‘fit-for-purpose’, it will not be

excluded from being operationally used; this might have to be reviewed and evaluated on a case-by-case basis.




respect to the delivery of sensor data (reporting, co-ordination) shall be elaborated and maintained up-to-date.

A12.3.3 Sensor outage or degradation

The ETKR Service Provider will monitor the availability and performance of the selected sensors as described in section A12.4.2. In case an outage or degradation of a sensor is detected, the ETKR Service Provider will immediately inform the sensor owner in order to get the problem fixed according to the agreed SLA.

The ETKR Service Provider will analyse the consequences of a sensor outage/degradation using pre-defined failure scenarios.

In case of an outage, the ETKR Service Provider will analyse the remaining coverage.

In case of degradation, the ETKR Service Provider will analyse the effect of the degradation and its impact on the overall ETKR system performance. As result of the analysis, using pre-defined failure scenarios, the ETKR Service Provider may decide to

1. Take the sensor out of the system

2. Leave the sensor in the system

3. Apply a pre-defined filter to the received sensor data in order to minimize the problem for some users while keeping a potentially essential sensor for other users.

In all cases the ETKR Service Provider will inform all affected Customers immediately on the detected problem, the decision taken and the consequences for the service provision (if there are any). It is up to the Customer to further assess the problem and take the appropriate measures to mitigate the potential impact of the problem.

A12.3.4 Sensor maintenance coordination

The ETKR Service Provider will coordinate, monitor and analyse all planned maintenance activities of the sensor owners. SLAs with the sensor owners will ensure that ETKR is informed timely on all planned maintenance activities.

If the ETKR Service Provider detects a conflict between planned maintenance activities, leading to a potential degradation of the service or required redundancy, he will contact the involved parties in order to resolve the problem.

A12.4 Monitoring and Control

A12.4.1 Monitoring and Control of ETKR infrastructure

An ETKR Monitoring and Control Centre (EMCC) will be created in each ETKR Data Centre (EDC) to monitor the complete underlying infrastructure, including sensors, networks, etc. and to control the available infrastructure under the direct responsibility of the ETKR Service Provider. It will operate twenty four hours per day, seven days per week.

The EDC shall have the capability of Monitoring and Control all the required ancillary equipment.

The EMCC will be designed in a manner that the track services from ARTAS and the Dissimilar Technology Tracker will not be, in any case, influenced by one or the other.

It is assumed, that the Monitoring and Control of the surveillance sensors and the Communication Networks will be carried out by the organisations responsible for the sensors and the Communication Network respectively – this links to the CS6 (new OCS) and CS8 (PENS).




The Customers will have real-time permanent monitoring access to ETKR technical information status. The controlling part at the Customer’s site will be defined when the ETKR system design and the detailed definition of roles and responsibilities are finalised. It should be also expected that the system will detect performance deviations/anomalies and act upon them centrally before they affect the Customers. In any case, at the Customers’ site, a capability should be available in order to customise the monitoring and potentially control the local functionality, according to the needs of each Customer.8

Procedures shall be defined how a given sensor will be degraded or rejected from data processing when an anomaly (e.g. performance deviation) is detected by a Customer of ETKR Service.

A12.4.2 Sensor monitoring

The sensor monitoring will be performed both regularly (on a quasi-real-time basis) and continuously (i.e. on a real-time basis)

Performance Indicator Verification Frequency

Remark/Note

Probability of target report detection (Pd).

Regular9. Defined as ratio of the number of detected target reports to the number of total expected reports.

Rate of correct and incorrect Mode 3/A and Mode C validated codes.

Regular5

Rate of false reports (single, multiple, reflections, side lobes).

Regular5

Biases: range bias, range gain, azimuth bias, time bias.

Regular5 Not Applicable for WAM, ADS-B and ADS-C.

Accuracy in range and azimuth. Regular5 Defined by the Mean, RMS, Standard Deviation, Minimum and Maximum of the residual random errors in range and azimuth.

Not Applicable for WAM, ADS-B and ADS-C.

Processing delay (Time consistency) and Time stability.

Regular5 / Continuous10

Processing delay is defined as: “Reception Time – Detection Time”, the Detection Time being the Timestamp contained in the respective message.

Time consistency measured with [Mean, RMS, Standard Deviation, Minimum and Maximum] of North/Sector/Plot messages Processing Delay.

8 The potential integration of the monitoring and control functionalities of the ETKR service, (e.g., the ETWs) into the Customer’s

Monitoring and Control Systems of their ATM infrastructure is out of the scope of the ETKR service.

9 A regular verification is one that is executed at fixed time intervals, using data for a time period of adequate length immediately

before the start of the verification. This type of verification allows trend analysis, but, due to its nature, not the immediate detection of deviations from the required performance.

10 A continuous verification is one that is permanently executed. This type of verification allows a real time detection of

deviations from the required performance




Performance Indicator Verification Frequency

Remark/Note

Time stability measured with [Mean, RMS, Standard Deviation, Minimum and Maximum] of the Timestamp difference between consecutive North and Sector messages.

Sensor status. Continuous6 Indicating if the sensor is operationally available or not.

Sensor load. Continuous6 Indicating the number of target reports being processed: overall (e.g. per scan for a radar) and on a sector model basis (e.g. 32 sectors, this latter is Not Applicable for WAM, ADS-B and ADS-C).

In addition, the following parameters will be Continuously6.monitored:

Number of measurements per sensor and assessment of the combination rate when applicable;

Sensor systematic errors - as applicable for the various surveillance technologies – e.g., for radars in time, range (bias and gain) and azimuth and monitoring of these using the ASTX CAT063 data stream;

Capability of the radar stations and automatic detection of:

o Loss of the PSR capability (of a combined PSR/SSR or combined PSR/Mode-S radar station);

o Severe degradation of the Mode S ELS (Elementary Mode-S) capability;

o Severe degradation of the Mode S EHS (Enhanced Mode-S) capability.

In addition, the facility to put a sensor station in a special “Test” mode shall be envisaged to assess if a sensor can be re-integrated in the sensor configuration actually used by ETKR, e.g. after a maintenance action has been performed on that sensor. In other words, in “Test” mode, the respective sensor does not contribute to the ASP as delivered by ETKR.

Finally, a dedicated sensor information monitoring tool shall be used to perform real-time eye-ball assessment by displaying the incoming sensor information and the multi-radar tracks generated by ETKR.

The EKTR Service Provider will coordinate outages with the sensor owners and involve relevant parties to resolve problems and to take mitigation measures; Controllers can inform about problems too.

ATTENTION practical use case: it may be extremely difficult to take the decision of removing a radar from the operational configuration due to conflicting User Requirements -> this could be solved by dynamic filtering techniques at input level of ETKR (in ESW or SDDS - TBD) based on a pre-defined set of operational scenarios

A12.4.3 Service monitoring

The quality of the ETKR service will have a large impact on the capacity and safety levels of the service provided by the customers. This puts high requirements on the service monitoring as well. In principle the ETKR Service Provider shall have access to all monitoring information that is required to ensure a reliable and high quality ASP. This means in addition




to monitoring information about his own systems, he would need information about the state of the sensors and the communication infrastructure (both on the sensor as well as on the customer side). If the sensors and infrastructure are not operated or maintained by the ETKR Service Provider, the operators will provide information about maintenance planning well ahead of any action.

The ETKR Service Provider on the other hand, will forward all necessary information to enable the customer to take precautions to mitigate outages or potential outages. This may include, but is not limited to:

Real-time status information about the sensors, the ETKR trackers and the communications infrastructure

ETKR Service Provider maintenance planning information

Sensor and communication infrastructure maintenance planning information

The real-time information will be provided in an adequate commonly used open format (e.g. SNMP).

The maintenance planning information will be delivered in English language.

A12.4.4 Performance monitoring

The performance of delivered data from Sensors will be continuously assessed and monitored.

The performance of the Track Information Service as well as the performance of delivered data from sensors will be verified using the EUROCONTROL Surveillance Analysis and Support System for Centre (SASS-C) and other tools or plug-ins that may have to be developed around SASS-C for specific purposes.

SASS-C provides a set of assessment and verification systems. The location and the number of assessment / verification points where the Track Information Service and the delivered data from sensors will be assessed/verified depends on the applicable Surveillance Standard.

Nevertheless it is mandatory that

The performance of the delivered data from sensors be assessed and verified against the applicable Surveillance Standard before it is delivered to the EDC, under the responsibility of the data provider

The performance of the Track Information Service be assessed and verified against the applicable Surveillance Standard at the CWP level ( Customer level ) under the responsibility of the customer

The following figure shows applicable performance standards at different assessment/evaluation points in the ETKR environment.




Figure 5 : ETKR performance assessment points

In addition to the sensor input and track output defined performance, the assessment of ETKR performance will also take into account communication quality criteria (TBD).

A12.5 Recording and Playback

A12.5.1 Customer’s Site level

It is assumed that at the Customer’s site a Recording and Playback System is already available and the same will continue during the Service Provision for the same purposes, that is:

Incident and accident investigations

Search and rescue operations

ATC procedures evaluation

Traffic load analysis

Checking completeness and correctness of data streams

System performance and efficiency analysis

System testing

Error tracing, debugging of hardware/software

Statistical analysis

Training

These recording and playback capabilities are expected to be easily adapted and exploited for the data streams related to the ETKR Service.

Further details of the Recording and Playback facilities, e.g., the classes and volume of data, the duration of the recording are still to be defined.

A12.5.2 EDC level

At the EDC level, recording and playback facilities will be provided to be used for:

Checking completeness and correctness of data streams

System performance and efficiency analysis




Investigation of consistency between Customer’s site recorded data and EDC level recorded data

Traffic load analysis

System testing

Error tracing, debugging of hardware/software

Statistical analysis

Training

All the Operational, Technical and Administrative data flows entering and leaving the Data Centres will be recorded.

A12.6 Development of new releases

A12.6.1 Development

During their life-cycle, the components of ETKR will evolve as required because of the introduction of new service requirements, the implementation of new surveillance technologies and the evolution of IT.

The Service shall provide the flexibility of accommodating messages for new types of Surveillance Sensors, e.g. Multi-Static Primary Surveillance Radars (MSPSR).

In case of architecture with dissimilar redundancy, the components of both chains will evolve in parallel, in order to ensure that the same level of performance is always provided.

A12.6.2 Validation and tuning

The ETKR Data Centre will ensure that new releases are fit for operation for all customers following relevant tuning and evaluation.

A12.6.3 Transitional support

The Service should allow modifications at the EDC level, including new release of the ETKR data service, to be carried out in a transparent manner not influencing the ASP. Modifications, however, at the level of the Wrapper influencing the Customer’s services, inevitably, will not be transparent and the appropriate measures should be taken at the Customer’s site.

Due to the anticipated high number of customers, it seems not feasible to implement a transfer of new releases for all customers at the same time (Big bang approach). The service implementation shall therefore foresee a gradual transfer of customers to a new service release.

A12.7 Maintenance and Operational Support

An ETKR centre for Maintenance and Operational Support (EMOS) will be set-up for supporting the whole Service Technical Infrastructure, operational 24hours/day and 7days/week, including hot-line support.

The existing structures for Maintenance and Operational Support of the three EUROCONTROL products (CAMOS, SACSO and RIT/SDD-IT) will continue to provide service up to the end of the transition period to operational ETKR.

As part of EMOS, an ETKR testbed will enable the emulation of the complete ETKR




operational environment and enable the assessment of performance throughout this environment. It will be used to ensure that the new release of any ETKR component is fit for operation, following relevant tuning and evaluation, prior to putting into an operational release. The testbed will also be used in support to any incident analysis.




ANNEX 13 – ETKR System Architecture

This annex contains elements on possible architecture options for building the ETKR service infrastructure, introducing in particular the concept of dissimilar redundancy, as a solution to meet the very high safety and availability levels expected for ETKR.

A13.1 ETKR Components

Figure 6 : ETKR block diagram

A13.1.1 ETKR Data Centre

The ETKR data centre will carry out the tracker and server functions, as well as all required supervision functions.

A13.1.1.1 Tracker

The tracker will process surveillance inputs received from all sensors in order to build the tracks that will be stored in the ETKR track data base. At the heart, the multi sensor fusion function will initiate and update the tracks on the basis of incoming reports from all selected sensors. The fusion will implement the so-called variable-update technique whereby each track is updated immediately after the reception of each aircraft report from any of the participating sensors.




A13.1.1.2 Server

The server will distribute subsets of the ETKR track data base to the users, as introduced in section A12.2. Three options are considered with respect to implementing the ETKR server functionality either in a centralised, a distributed mode or a combination of both.

In the centralised server mode, the customer service is provided by the EDC itself, meaning that the ETKR Server has the capability to deliver simultaneously a wide range of different services according to the needs of the various customers.

In the distributed server mode, the server functionality is physically located at the Customer’s site. The EDC broadcasts a generic asynchronous track information service over the network. Data stream is then turned into periodical or radar synchronised service at the customer side, e.g. as a function of the ETKR Service Wrapper (ESW).

In the combined server mode, both the centralised server mode is deployed for those Customers not needing specific customisation of the Service, and the distributed server mode is deployed for customers with further specific needs.

A13.1.2 ETKR Service Wrapper (ESW)

The Service Customer sites will deploy an ETKR Service Wrapper (ESW) to connect to the European Tracker Service.

The prime functions of the ESW - delivered by ETKR - will be to act as a Customer Gateway, comprising:

Protocol management (connection oriented to multicast/broadcast)

Filtering of data according to different criteria (geographical, id based, …)

Reception of tracks from the EDC and, in case of distributed server mode (see section A13.1.1.2) and sequencing according to customer specified service characteristics (see section A12.2).

In addition, a number of optional functions – not delivered by ETKR - may be considered, according to the selected architectural design:

Track Number Gateway aiming to associate to each Track the Track Numbers of the other trackers, in order to support the seamless switch of data-streams from one to the other. Depending on the final architecture, potentially five data streams will be involved i.e. the dissimilar streams from the dual EDCs along with the track number of local back-up Tracker system11.

Projection function (geodesic coordinates to local system plane)

QNH correction

Format conversion from standard ASTERIX to local format used by customer ATC systems or e.g. some military Air Defence Systems.

Corrections taking into consideration the network latency

Connection to the Flight Plan Systems for the reception of flight plan information in order to be able to distribute correlated position reports (identical to the mechanism used in the ARTAS system).In the case of Military: more stringent security requirements have to be fulfilled by either the ESW and/or possibly a military specific secure gateway.

11

To be further evaluated whether this functionality will be implemented at both the ESW and the EDCs level, in order to ensure that the switching of ASPs is carried out in a transparent manner for the final User.




A13.2 Dissimilar Redundancy

It is assumed that:

a. ETKR will use the Surveillance products developed by EUROCONTROL on behalf of its Member States. This comprises ARTAS (Tracker A) for the tracker part and the Surveillance Data Distribution System (SDDS) as central and local front-end component. . As required to interface the local ATM systems, the SDDS deployed at the Customer’s site might be enhanced with additional functionality; any local adaptation for optional functionality is the responsibility of the Customer.

b. ETKR will use an equivalent ETKR functionality delivered by a second solution in parallel, based on a completely independent development and implementation.

c. The necessary communication infrastructure will be provided by CS8.

d. It is foreseen that the EUROCONTROL product SASS-C will be enhanced and used for the verification of performance (Service quality monitoring).

The relevance of such an approach from a Safety point of view will be addressed as part of the ETKR Safety Case, following a thorough Functional Hazard Analysis (FHA).

In principle and in order to avoid single modes of failure, there is no link (synchronisation) between the two Trackers, and CS8 assures redundancy within the communication infrastructure.

As an outcome of the dissimilar redundancy, two Air Situation Pictures will then be available at customer sites. It will be further investigated whether the Service shall ensure the switching between data streams from an ETKR ASP to a second one in a transparent manner for the operational staff (typically ensuring same track numbering in the two ASPs) and as much as possible transparent for the other users/subsystems using the service.

Provision should be made to keep the dissimilar redundancy during the life-cycle of the ETKR service, especially the one related to the Trackers, by taking the appropriate measures, (e.g., different maintenance and development teams).

A13.3 ETKR system architecture options

Two architecture options are considered so far for the ETKR Data-Centres (EDCs), with different level of centralisation. The Demonstrator project will conclude which one is the best in terms of performance, safety, security and economic efficiency across the complete ETKR life cycle. Due attention will be given on transition cost, from current situation to ETKR.

A13.3.1 Option 1: Centralised

In this model, two EDCs are mirroring each other. Each of them has the capability of generating the ASP over the complete area and to serve all Customers. However, in nominal mode, each data-centre will have the responsibility to serve only a given cluster of Customers, for load balancing purpose.

Inside the Data Centre, the Tracker (ARTAS and the dissimilar Tracker) can be either a “big” system processing all load, or a group of smaller redundant systems potentially cooperating together (Optimum configuration to be assessed). This latter case could be the preferred solution, if more than one ASP has to be produced - with different tuning parameters - by each one of Tracker A and Tracker B. Another advantage of such architecture is the flexibility for any potential expansion of the ETKR domain of interest..




As illustrated below, two implementation options of the dissimilar redundancy can be considered, either with each of the two EDCs hosting both Trackers A and B (Figure 7) or with each EDC hosting only one technology (Figure 8).

On Customer side, a service Wrapper will allow selecting either Tracker A or Tracker B data stream and ensuring that the ASP arriving to the operational staff is identical independently whether data stream from Tracker A or Tracker B is selected.

It will be further investigated whether the Wrapper is responsible for keeping the same Track number independently whether it is originated from the one or the other Tracker. Ideally, the Wrapper shall keep the same Track number even in the case of switching to the local Tracker (if it is available).

Figure 7 : ETKR Centralised (Option 1A)

Figure 8 : ETKR Centralised (Option 1B)




A13.3.2 Option 2: Semi-distributed

In this model, there are several EDCs installed at sub-regional level, e.g. at FAB level.

Each EDC processes an ASP within a domain of interest partly overlapping with the neighbouring EDCs and provides track service tracks to a given set of Customers.

As in the case of the Centralised option, in each EDC a system or a group of smaller redundant systems cooperating together will process the whole load (Optimum configuration to be assessed). This latter case could be the preferred solution, if more than one ASP has to be produced - with different tuning parameters - by each one of Tracker A and Tracker B.

Compared to the centralised one, this model offers more contingency options to mitigate failure (a data centre being capable to take over its neighbour(s)) and is more resilient against security threats.

Figure 9 : ETKR semi-distributed (Option 2)

A13.4 Communication Infrastructure

A13.4.1 Networks

Data communication between the Surveillance sensors (downstream from the PENS delivery node), the European Tracker Service and the Customers will be carried out over CS8 (see section 2.3.6) which will provide the required quality of service for the exchange of Surveillance data.

A13.4.2 Access points

The data exchanges from the sensors to the data Centres and between the Data centres and the Customers will be carried out via the EUROCONTROL Surveillance Data Distribution System (SDDS).

With respect to security aspects, SDDS implements advanced security concepts (e.g. stateless and stateful firewall, Security Enhanced Linux Kernel, protected system

ETKR DC3

ETKR DC2

ETKR DC1

PSR

SSR

Mode S

ADS-B

WAM

ADS-C

Tracker &

Server A1

Tracker &

Server B1

ATC

functions

Surveillance

Sensors

Surveillance

Tracks

Customers

Tracker &

Server A3

Tracker &

Server B3

Tracker &

Server A2

Tracker &

Server B2




management functions). In the case of military users additional measures may have to be implemented.

The Customers are connected to ETKR via a common interface and the tracks are distributed to the Customers throughout a publish/subscribe type of interface.

The alternative access point for the dissimilar redundancy is not defined yet.

A13.5 Redundancy and Contingency

The high reliability and the continuous availability of the Air Situation Picture are essential for the provision of Air Traffic Control.

The Demonstrator, in addition to recommending the most appropriate Architectural Option, will investigate and determine the optimum manner of switching between the various physical sub-systems and services in order to ensure the maximum possible reliability and availability of the Service.

With this objective in mind:

a) The Redundancy has to be ensured by duplicating all the platforms hosting the various functional Units (e.g., trackers, wrappers) and

b) The ETKR-based Surveillance chain comprises 2 levels of fall-back as follows:

- Central level 1: Dual Data-Centre switch

- Central level 2: Dissimilar technology switch

ETKR does not require a local Back-up at the Customer’s site.

In case a distributed architecture is selected (Option 2), an additional contingency level is possible, whereby the backup of one ETKR tracker system is carried out by adjacent system(s). The contingency process will consist in the extension of the domain of responsibility of ETKR systems adjacent to the failing one, in order to continue the surveillance and related services within the area originally attached to that unavailable system.




ANNEX 14 – ETKR Service Set-up

This Annex gives an overview of the successive phases for the development of the ETKR service, from the demonstrator that will prove the feasibility of the concept up to the service operation.

A14.1 Demonstrator

The main objective of the Demonstrator will be to validate the ETKR concept. It comprises several phases (non-exhaustive):

The Architecture Definition Phase will concern the elaboration of the ETKR system architecture in order to meet the performance and safety requirements, including the communication infrastructure requirements. The various options described in Annex 13 will be elaborated. This Phase covers as well the selection of the dissimilar tracker and server system that will run in parallel to the EUROCONTROL components.

The Specification Phase will deliver the specification of functional and performance enhancements to ARTAS, to the dissimilar Tracker and other relevant components such as the Service Wrapper, in order to meet the ETKR requirements.

The Prototyping Phase will comprise the development of prototypes on the basis of the selected system components and their evaluation to demonstrate the feasibility of the concept, in particular in terms of load management. This phase includes the set-up of the required test environment to execute the validation.

A14.2 Development

After having achieved positive results on the Demonstrator, the next phase will be the development of the ETKR and its full-size evaluation. It concerns the development of the ETKR system components at the required Software Assurance Level (SWAL). It comprises (non-exhaustive):

Upgrade of the tracker function (ARTAS and dissimilar Tracker) to process the complete Europe wide air situation picture. Depending on the outcome of the Demonstrator two possibilities may be considered within a Data-Centre: either one “big” Tracker processing the full load or several “smaller” Trackers interconnected together to build the ASP through cooperation function.

Upgrade of the Server function (ARTAS and dissimilar component) to process required Europe wide services.

Development of the Service Wrapper installed at customer sites, on the basis of




SDDS and other dissimilar component.

Development of maintenance and operational procedures

Installation of an ETKR pilot configuration and execution of full-size evaluation.

A14.3 Implementation and Deployment

This phase concerns the implementation of the complete operational infrastructure to carry out the ETKR service

A14.3.1 ETKR Data Centres

The sites where the operational chains will be installed are not selected yet and will depend in particular on the selected architecture option (see section A13.3).

All the elements of the operational chain will be (at least) duplicated, comprising Sensor data acquisition equipment, Tracker & Server, monitoring & Control equipment, etc.

This applies to both chains (cf dissimilar redundancy).

A14.3.2 Customer site adaptation

The service Wrapper installed at each customer site aims to replace the local SDPD as prime source for the provision of ASP. Its role is to interface with the ETKR Data Centre, to retrieve required ASP subset and to distribute it to the respective ATC system or e.g. Air Defence system in case of military customers. The service Wrapper will carry out format conversion as needed.

A14.3.3 ETKR testbed

The ETKR testbed will enable the emulation of the complete ETKR operational environment and the assessment of performance throughout this environment. It is not intended to replace a pre-operational evaluation to be carried out - if it is deemed necessary - before a new ETKR service is operationally used, especially during major modifications of the service.

The ETKR environment is divided in five environment modules namely Sensor, Customer, Sensor Gateway, Customer Gateway and the ETKR Data Centre (EDC).

Figure 10 : ETKR testbed block diagram

Each environment module will be independent of the others and have the capability to record and replay the input stream to reproduce any situation in isolated manner.

Of course, it should be possible to correlate the input scenarios of the Sensor Environment




with the Tracker configurations of the ETRK Environment to test and analyse troubles of the full architecture.

The emulation of the operational network environment (e.g. PENS) is not included in these modules. Such a module will be provided by CS8.

The ETKR testbed is foreseen to be hosted in the EDCs.

A development environment is not foreseen at the Customers’ sites. For testing purposes, however, a similar environment to the one described in Section Error! Reference source not found. Error! Reference source not found. should not be excluded; it would be equipped with the appropriate evaluation tools. This environment may be also used for performing end to end trials based on agreed procedures between the Customers involved and the ETKR SP.

A14.3.3.1 Sensor Environment

This module of the testbed will cover the following capabilities or functionalities:

Creation of simulated scenarios to be used to stress the full architecture. This includes:

o Emulation of PSR, SSR, Mode S, ADS-B and WAM sensors as well as ADS-C Target Reports for given traffic scenarios and given configuration of sensors

o ASTERIX frames manipulation to provoke message rejections and/or specific stress situation to the Tracker systems

o Simulation of spoofing messages (e.g. ADS-B)

Archiving of scenarios. This concerns the simulation scenarios and also the scenario related to Customer’s problems investigation.

Replay of recorded scenarios, reproducing exactly the initial conditions of each scenario in term of time differences, errors and network load.

Analysis of Sensor characteristics, as required to tune the Tracker systems. The SASS-C system is fit for this purpose.

Decoding of ASTERIX frames to facilitate the investigation of issues related to message rejections and Tracker misbehaviour.

A14.3.3.2 Sensor Gateway Environment

This module of the testbed will cover the following capabilities or functionalities:

Realistic simulation of an operational configuration of sensor gateways (typically, one per ATC centre).

Routing of ASTERIX frames over different networks and to different destination addresses.

Introduction of delay to network frames to simulate high latency or low bandwidth situations.

Simulation of loss of network frames

Corruption of network frames

Simulation of security infringement attempts

Computation of the network bandwidth.

Such functionalities are available as part of the SDDS test environment.




A14.3.3.3 ETKR Data Centre (EDC) Environment

This module of the testbed will encompass the following capabilities or functionalities:

Replica of the operational systems i.e. two EDC systems, each of them including both the ARTAS and the Dissimilar Tracker Technologies. The 4 trackers will process surveillance inputs received from the Sensor Gateway module and build the tracks that will be served to the different customers via the Customer Gateway module.

Archiving of the various setting of the ARTAS system and the dissimilar tracker.

Simulation of failures of one of the two EDC systems.

Simulation of failures of one of the two trackers part of an EDC system.

Comparison of track output to analyse differences of the same service stream delivered by ETKR A and ETKR B.

Analysis of the air situation picture delivered by any of the ETKR Tracker along with the related radar and sensor information.

A14.3.3.4 Customer Gateway Environment

This module of the testbed will emulate the Customer gateway functions of the ESW (see section A13.1.2), covering the following capabilities or functionalities:

Realistic simulation of an operational configuration of customer gateways (typically, one per ATC centre).

Routing of ASTERIX frames over different networks and to different destination addresses.

Introduction of delay to network frames to simulate high latency or low bandwidth situations.

Simulation of loss of network frames

Corruption of network frames

Simulation of security infringement attempts

Computation of the network bandwidth.

Create some geographical area filters or track selection mode to be used to filter the air situation picture delivered by the ETRKs to Customers’ needs.

Most of those functionalities are available as part of the SDDS test environment.

A14.3.3.5 Customer Environment

In complement to the Customer Gateway, this module of the testbed will emulate additional ESW functions (see section A13.1.2), comprising:

The possibility to emulate different categories of Customer services (Immediate, Periodical and Radar synchronised)

Decoding of ASTERIX frames to investigate any sort of issues.

Analysis of the air situation picture delivered to a Customer along with the related radar and sensor information.

A tracker comparator to analyse differences of the two (or more) service streams provided to each Customer

A local Tracker system (e.g. ARTAS) that processes ”customer local” surveillance inputs received from the “local sensors” and builds the “local air situation picture” that




will be served to the different Customers via the Track Number Gateway.

The Track Number Gateway, associating the Track Numbers of the ETKR-DC and the local Tracker system.

Simulation of the SUPERVISION position to monitor the entire architecture.

A14.4 ETKR Supporting Processes and Activities

Supporting Processes and other relevant activities will be put in place according to well-established international standards, e.g. Configuration Management of the ETKR artefacts, Verification and Validation activities, releases of new version of software builds, handling Trouble Reports, introducing new functionalities.

A14.5 ETKR Service Transfer

By the end of the contractual period with the first selected ETKR Service Provider, the ETKR Service has, in no case, to be disrupted or to be degraded. To this end, a number of measures will be taken for the smooth transfer of Service between the old and the new ETKR Service Provider. These measures will be detailed in a Closeout/Transfer Plan to be included in the contract with the selected ETKR Service Providers.




Applicable and Reference Documents

Applicable Documents

[ADx] Title/edition

[AD1] GEN-SUR SPR EUROCONTROL GEN-SUR Generic Surveillance Safety and Performance Requirement document (SPR), under development version 0.8

[AD2] GEN-SUR SEC EUROCONTROL GEN-SUR Generic Surveillance Security Requirements document (under development)

[AD3] ED-129 EUROCAE document: Technical Specification for a 1090 MHz Extended Squitter ADS-B Ground Station, issued on June 2010.

[AD4] ED-142 EUROCAE document: Technical Specification for Wide Area Multilateration (WAM) Systems.

[AD5] SPI-IR Commission Implementing Regulation (EU) No 1207/2011 of 22 November 2011 laying down requirements for the performance and the interoperability of surveillance for the single European sky (SPI-IR)

[AD6] Blue Book EUROCONTROL Standard document for radar surveillance in En-route airspace and major terminal areas” (dated March 97)

[AD7] ANS-IR Commission Implementing Regulation (EU) No 1035/2011 of 17 October 2011 laying down common requirements for the provision of air navigation services and amending Regulations (EC) No 482/2008 and (EU) No 691/2010

[AD8] ESASSP EUROCONTROL Specification for ATM Surveillance System Performance EUROCONTROL-SPEC-0147 Ed. 1.0 Dated30/03/2012

[AD9] Interoperability Regulation Regulation (EC) No 552/2004 (the interoperability Regulation) as amended by Regulation (EC) No 1070/2009




Reference Documents

[RDn] Title/Edition

[RD1] Ch8 PANS/ATM ICAO Doc 4444 – PANS-ATM Air Traffic Management, Procedures for Air Navigation Services, Fifteenth edition-2007

[RD2] ED-153 Guidelines for ANS Software Safety Assurance

[RD3] ARTAS-SSS-V8B1 ARTAS V8B1 System/Segment Specification (SSS)

[RD4] ARTAS-EIRS-V8B1 ARTAS V8B1 External Interfaces Requirement Specification (EIRS)

[RD5] SDDS SDDS Factsheet, SDDS Application sheet, SDDS Security Concept

[RD6] SASS-C SASS-C product & Service description (ref SASS-C-PROJ-10)

[RD7] Surveillance Infrastructure Rationalisation

Methodology to Support a Rationalisation of the Surveillance Infrastructure, part 1 & 2 – SESAR project 15.04.01, deliverable D10-01

[RD8] SURNET Surveillance Data Sharing Agreement




GLOSSARY

Term Description

Area of Interest Customer specified 3D geographical area, totally enclosed within the ETKR domain of operation, from which they want to receive all or subsets of tracks.

Customer Legal body that operates any site or cluster of sites, civil and military, making use of track data generated by and distributed through the ETKR Service

Domain of operation Geographical area over which ETKR will elaborate the Air Situation Picture, using all connected sensors located within and also possibly outside this area.

User System or function making use of ETKR track information acquired by a Customer.




ABBREVIATIONS

Abbreviation Description

ACID (Mode S) AirCraft IDentification

4DPP 4D Trajectory Flight Profile Calculation for Planning Purposes

ADS-B Automatic Dependent Surveillance - Broadcast

ADS-C Automatic Dependent Surveillance - Contract

ANSP Air Navigation Service provider

ARTAS EUROCONTROL ATM suRveillance Tracker And Server

ASP Air Situation Picture

ASTERIX All-purpose Structured EUROCONTROL Surveillance Information Exchange

ATC Air Traffic Control

CAMOS Central ARTAS Maintenance and Operational Support

CNS Communication, Navigation & Surveillance

CPR Correlated Position Report

CWP Controller Working Position

DAP Downlinked Aircraft Parameter

DSU Declaration of Suitability for Use

EAD European AIS (Aeronautical Information System) Database

EAIMS European ATM Information Management Service

EASA European Aviation Safety Agency

EDC ETKR Data Centre

EMCC ETKR Monitoring and Control Centre

EMOS ETKR Maintenance and Operational Service

ESASSP EUROCONTROL Specification for ATM Surveillance System Performance




ESW ETKR Service Wrapper

ETKR European Tracker Service

EUROCAE European Organisation for Civil Aviation Equipment

EUROCONTROL European Organisation for the Safety of Air Navigation

FDPS Flight plan Data Processing System

GEN-SUR-SEC EUROCONTROL Generic Surveillance Security

GEN-SUR-SPR EUROCONTROL Generic Surveillance Safety and Performance Requirements

IFR Instrument Flight Rules

IPR Intellectual Property Rights

IT Information technology

KPI Key Performance Indicator

MSAW Minimum Safe Altitude Warning

MSPSR Multi Static Primary Surveillance Radars

NIPS Network Infrastructure Performance monitoring and analysis Service

NM Nautical Mile

OSED Operational Service and Environment Definition

PANS/ATM ICAO Procedures for Air Navigation Services - Air Traffic Management

PENS Pan European Network Service

PSR Primary Surveillance Radar

QNH Q-code for barometric pressure adjusted to sea level

SACSO SASS-C Support Office

SASS-C EUROCONTROL Surveillance Analysis and Support System for Centre

SDDS EUROCONTROL Surveillance Data Distribution System

SDDIT Surveillance Data Distribution Implementation Team

SDPS Surveillance Data Processing System

SESAR Single European Sky ATM Research (Programme)




SLA Service Level Agreement

SPI-IR Surveillance Performance and Interoperability Implementing Rule

SSM Sensors Service Message

SSR Secondary Surveillance Radar

STCA Short Term Conflict Alert

SWAL Software Assurance Level

TBD To be defined

VFR Visual Flight Rules

WAM Wide Area Multilateration