EGNOS Service Provision

Meeting, EC - Brussels24/06/2010

Agenda

10:00 - 10:30 Welcome and context 10:30 - 12:00 Past EGNOS performances 12:00 - 12:30 Q&A on EGNOS Past Performances

12:30 - 13:30 Lunch

13:30 - 15:30 EGNOS Service Provision status and future 15:30 - 15:45 Break

15:45 - 16:00 Status of FP7 projects related to EGNOS trials 16:00 - 17:00 Q&A on EGNOS Service Provision

17:00 - 17:30 Conclusions

Content

1. EGNOS Program Context 2. ESSP Introduction 3. EGNOS Past performances 4. EGNOS Service Provision status and future

4.1Certification Status 4.2 SoL service Introduction 4.3 EGNOS User Support 4.4 EGNOS NOTAMs 4.5 EGNOS Operations & Maintenance

5. Status of FP7 projects related to EGNOS trials 6. Conclusions

1. EGNOS Program Context

2. ESSP Introduction

European Satellite Services Provider

AENA NATSDFS ENAVDGAC SKYGUIDE NAV

ESSP Mission

To provide the EGNOS Open Service and Safety of Life Service compliant with ICAO SARPS throughout the ECAC region

ESSP Status (1/2)

ESSP EEIG founded in 2001 Mission: Operation of EGNOS Based in Brussels

ESSP SAS created in 2008 Mission: EGNOS Service Provider HQ,PASSQ & SOU: Toulouse SPU: Madrid

ESSP Status (2/2)

ESA Initial Operation Phase (IOP) Ended April 2009

EGNOS Signal Continuity Provision (ESCP) 6 Months: Ended in October 2009

EGNOS Service Provision (ESP) Contract signed 30 September 2009 for 51 months

ESSP Past Milestones

April 2009: Transition of the EGNOS Service Provision and Operations from the ESSP EEIG organisation to the new ESSP SAS.

April 2009 – September 2009: execution of the EGNOS Signal Continuity Provision Contract with the EC. Completed the “hand over” of the EGNOS system of the EGNOS program from the ESA ARTES 9 program to the European Commission GNSS Program

> October 2009: enter EGNOS Service Provision period, On that date the EC formally declared the EGNOS Open Service available

ESSP Future Milestones

Preparation of Safety of Life service provision

July 2010: Certification of the ESSP as a Navigation Service Provider under the SES regulation

August 2010: Message Type 0 off

November 2010: SoL Service Declaration to users

3. EGNOS Past Performances

(1 April 2009 – 31 March 2010)

EGNOS Performances

The ESSP and EC have implemented several Key Performance Indicators (KPI) for the measurement of the EGNOS performances as well as ESSP management performances

The performance presented as well as the reference service area has been established for the current EGNOS version v2.2-ext

Following slides show the highlights for the past performances for the Required Navigation Services (RNS) Signal In Space (SIS) broadcast availability Open Service (OS) NPA APV-1

EGNOS Performances Parameters

EGNOS has been designed to meet stringent requirements coming from Aviation

ICAO SARPS define performances in terms of Accuracy Availability

Continuity Integrity

14

EGNOSService Area

EGNOS SatelliteFootprints

EGNOS GEO footprints

3 Geostationary satellitesPRN120: INMARSAT 3F2 AOR-E (15.5°W), PRN124: ARTEMIS (21.3°E), PRN126: INMARSAT 3F5 IOR-W (25°E) - test

RIMS MCCs NLESASQFPACF

EGNOS = 48 SITES OVER 23 COUNTRIES

SIS Broadcast Availability

SIS: 99,99% Network Issue

PRN 124: Artemis payload

PRN 120: Inmarsat AOR + Operator

PRN 124:Artemis payload

Open Service (1/6)

Horizontal and Vertical Accuracy was monitored at 19 RIMS sites.

The 95th percentile of the Horizontal/Vertical Navigation System Error (HNSE/VNSE) over a day, in each of the days of the period from April 2009 to March 2010 has been below HNSE < 3m VNSE < 4m

The only exceptions were found at Kirkenes (Norway) and

Tromsoe (Norway)

EGNOS Open ServicePositioning Compliance Area

(2/6)

Area where the user is able to calculate its position within the accuracy requirements

Open Service (3/6)

Histogram of HNSE for all monitored RIMS sites during the full period reported for PRN124

Open Service (4/6)

The value for OS Availability (% of time in the month in which HNSE<3m and VNSE<4m) has always been above 99% for each month of the period April’09-March’10 and for the monitored RIMS sites

The only exceptions were found at Kirkenes (Norway) and Tromsoe (Norway) sites on the month of October 2009 and February 2010

Open Service (5/6)

Main Observations: October 2009

Underperformances are located in the timeframe between 14th and 25th, due to NANU.

Visible peak caused by the important loss of monitored IGPs over the north ECAC detected from 22nd to 24th October.

Open Service (6/6)

Main Observations: February 2010 RIMS LYR has not been operational from 15th February

until the end of the month

Several NANUs have taken place during this period. In particular the NANU in PRN20 from 15th to 19th, the NANU in PRN30 from 22nd to 24th, the NANUs in PRN02 occurred on 16th and the NANU in PRN06 occurred on 22nd February.

On 15th February a planned maintenance activity provoked the loss of the RIMS connected to MCC-LAN (ALB, KIR, WRS, BRN, GVL, LAP) during a few minutes.

NPA service area reference map

NPA Availability

NPA Availability (% of time in the month in which HPL NPA < AL NPA) has always been above 99% for each month of the period April’09-March’10 and for the measured sites .

HPL: Horizontal Protection LevelAL: Alert Limit

APV-1 service area reference map

APV-1 Availability (1/4)

APV-I availability is reported using maps showing the area for which APV-1 availability (99%) is reached.

During the period from April 2009 to March 2010 , the APV-I Availability requirement is met over 98.6% of the Service area for both operational GEOs PRN120 and PRN124.

APV-1 Availability (GEO/ PRN120) (2/4)

APV-1 Availability (GEO/ PRN124) (3/4)

APV-1 Availability (Best Day) (4/4)

APV-1 Continuity (1/4)

APV-I continuity is reported using maps showing the area for which 5*10-4 value for APV-1 continuity is reached.

During the period from April 2009 to March 2010 , the APV-I Continuity Risk requirement was met.

APV-1 Continuity (GEO/ PRN120) (2/4)

APV-1 Continuity (GEO/ PRN124) (3/4)

APV-1 Continuity (Best Day) (4/4)

APV-1 Availability & Continuity

Border areas are more sensitive to potential degradations caused by GPS and RIMS outages.

Several anomalies have been identified during the year being the main drivers: GPS outages (NANUs). To be highlighted:

PRN8 and PRN24 were not usable from 15th to 27th October and from 5th to 29th November 2009.

PRN20 and PRN30 were not usable during 4.5 and 2 days during February 2010.

EWAN breaks. It should be noted that a significant part of the issues resulted during the network migration from Frame-Relay technology to MPLS one.

Ionosphere Monitoring degradation. Specially relevant in the North of ECAC area and also partially related to the effect of geomagnetic activity in northern latitudes. Future version 2.3.1 implements an improvement of IGP monitoring algorithm.

APV-1 Integrity (1/2)

The measurements of the Safety Index demonstrate a very good safety confidence.

One Misleading Information (MI) event was detected on the 26th June 2009 in a receiver located at Bergen. No impact on integrity.

Safety index (meters):

PRN 120 PRN124

HSI 95th VSI 95th Max HSI Max VSI HSI 95th VSI 95th Max HSI Max VSI

0.11 0.1 0.41 0.51 0.11 0.1 0.33 0.52

APV-1 Integrity (2/2)

Safety Index histogram measured in RIMS locations:

PRN120

HSI

EGNOS Performances – Summary (1/6)

The Required Navigation Services (Availability, Continuity, Integrity and Accuracy) are in line with ICAO-SARPS Signal-in-space performance requirements except for

continuity for which the probability of discontinuity has been increased until 5*10-4 for APV-1 operation (instead 1-8*10-6 in SARPS)

This limitation of current version v2.2-ext in continuity performances does not prevent the use of the service but it should be taken into account in the specific Application Safety Cases.

EGNOS Performances – Summary (2/6)

The Accuracy target value have been improved to

below 3 meters for horizontal and 4 meters for vertical accuracy (being in SARPS 16m and 20m for APV1 operation)

in line with the accuracy requirements for the potential provision of LPV approaches down to 200 feet minima

EGNOS Performances – Summary (3/6)

GPS outages

RIMS/EWAN outages

IGPs Not Monitored

RIMS maintenance2.23%

RIMS failure6.53%

SIS Outage -Planned 3.02%

SIS Outage - NLES maintence

1.12%

SIS Outage -Mono NLES

0.29%

SIS Outage - Double NLES failure3.35%

SIS Outage -GEO failure

1.74%

NANU20.09%

GPS monitoring9.96%

Iono monitoring16.54%

CPF-Sw0.29%

NLES switch9.34%

Input Quality1.41%

EWAN failure13.31%

EWAN maintenance1.94%

CPF degradation4.26%

EWAN failure -serveral RIMS

4.38% Unknown0.21%

Drivers distributionRIMS maintenance

RIMS failure

SIS Outage - Planned

SIS Outage - NLES maintence

SIS Outage - Mono NLES

SIS Outage - Double NLES failureSIS Outage - GEO failure

NANU

GPS monitoring

Iono monitoring

CPF-Sw

NLES switch

Input Quality

EWAN failure

EWAN maintenance

CPF degradation

EWAN failure - serveral RIMS

• Main underperformance drivers affecting specially the stability in border areas :

EGNOS Performances – Summary (4/6)

All underperformances are duly investigated, reported and tracked via anomaly investigation reports (Observation Reports) when relevant.

EGNOS Performances – Summary (5/6)

Current EGNOS V2.2ext achieving good levels of performance towards Aviation ICAO SARPS

New EGNOS V2.3.1 (in 2011) with 4 additional RIMS sites and improvement EGNOS functions will increase the service area the service robustness in the service border area

42

43

APV-1 Expected Availability Extension (2011) (6/6)

Indicative coverage observed with EGNOS Test

4. EGNOS Service Provision status and future

4.1 Certification Status

The need for Certification

To provide the SoL Service for Aviation, ESSP has to be certified as ANSP according to the EC-SES Single European Sky regulation

The (SES) Certification process is managed by the French National Supervisory Authority (NSA)

Seven other NSA are associated to the process: Belgium, Germany, Italy, Portugal, Spain, Switzerland, United Kingdom

Certification Framework (Actors, Roles)

ESSPAs

Navigation Service Provider

European Commission EC-EGNOS

the customer

ContractNational SupervisoryAuthority

NationalAir TrafficService Provider

Certification

Service

Notification

Service

Product Support Services

TWAN Services

Geostationarytransponder

lease

Logistic entity Training entity

MCC4 sites

NLES4 sites

RIMS34 sites

47

SES Applicable Regulations

NSA Organisation

NSACommittee

manages the certification process

CertificationTeam (CT)

Safety Case Interoperability

Assessment Team (SCIAT)Provide

supportSERVICE regulation

management orientedSYSTEM regulation

Technical oriented

49

Certification activities

1) ESSP SAS Certification (compliance to SES 2096, SES 668)

Mid 2010

3) EGNOS System Interoperability (compliance to SES 552)

2) Safety Demonstration of the change (compliance to SES 1315, SES 482)

Safety Case

Safety Assessment of changeis one management process

Implemented

Provided in

Is one interoperability evidence

NSA Certification Team (CT)

NSA Safety Case Interoperability Assessment team (SCIAT)

• ESSP to provide the 3 demonstrations of compliance• NSA (CT and SCIAT) to assess the compliance

ESSP SAS Certification

51

The conditions for a safe and efficient provision of air navigation services(in compliance with the Common Requirements : organisational structure and management , safety, quality, security,

human resources, financial strength, liability and insurance, quality of service, reporting)

Change 0 Safety Case

52

Safety Case Part A

Design is safe

Safety Case Part B

Operation and Maintenance of EGNOS

are safe

Introduction of EGNOS in EATMN is

safe

Interoperability Dossier

53

Technical File(compliance EVIDENCE of the

system to the ER)

Declaration of Verification(PROCEDURE of verification that the system is

compliant to the ER)

In compliance with the applicable Essential Requirements (ER) (Seamless operation, Support for new concepts of operation, Safety, Environmental constraints, Principles governing the logical architecture of systems, Principles governing the construction of systems)

Declaration of Suitability for Use(compliance EVIDENCE of the constituent to the ER)

Current status/ progress

ESSP Certification as ANSP Safety, Quality and Security audits have been held successfully No major non conformity identified

Interoperability Dossier Convergence on format and content of DOV and TF has been reached Delivery of Interoperability dossier for last review on 16/06/201

Introduction of EGNOS in EATMN Delivery of safety argument for last review on 16/06/2010

Final steps before first EGNOS introduction in EATMN ESSP certification: 12-July-2010 Formal delivery by ESSP of Interoperability and safety dossiers: 13-July-2010 Formal acceptance by NSA of EGNOS introduction in EATMN: 30-July-2010

The future Oversight of ESSP Certificate by EASA, Safety Management of next Changes

4.2 EGNOS Safety-of-Life Service Introduction

56 56

EGNOS Services

EGNOS Open Service (OS) Service Declaration: 1st October 2009

EGNOS Safety-of-Life (SoL) Service Service Declaration: November 2010 ESSP Certification & Declaration of Verification process

EDAS (EGNOS Data Access Service) Service Level under definition by EC Beta-test phase available from 2009

EGNOS Open Service

Declared available by EC in October 2009 Terms and Conditions of access

OS SDD (Service Definition Document) Positioning and timing service

Improving accuracy of GPS positioning and timing Free access to compatible receivers

Minimum service lifetime of 20 years 6-years advance notice in case of significant change of service

Available even with MT0

EGNOS Signal-In-SpaceMessage Type 0

Message Type 0 (Don't Use for Safety Applications message) Message currently transmitted by the EGNOS Signal in

Space

When the Message Type 0 is on, EGNOS can not be used for Safety of Life applications and therefore is not usable for aviation.

EGNOS SoL Schedule

2009

MT0 Removal: 2-Aug-10

2010 2011

MTO on MT0 off

SoL Declaration to users:

latest 3-Nov-10

OS available

OS Declaration to users:

1-Oct-09

SoL availableObs. period

ESSP certified:

12-Jul-10

SoL Service implementation

The Declaration of SoL Service by the EC is just the first step in the service provison to the final civil aviation user

National ANSPs have to

Develop and submit to the NSA for approval and publish flight procedures based on EGNOS

Sign a service agreement with the ESSP

SoL Service Communication Plan:

Target Audience

EU ANSPs and NSAs: Independently of the level of EGNOS service coverage achieved in their respective State.

Non EU countries: only the ones with service coverage will be targeted (Switzerland, Norway, some Baltic countries)

SoL Service CommunicationOBJECTIVES

MESSAGES

CHANNELS

MT0 OFF Observation period

Service agreement

SoL Service

declaration

EGNOS ESSP

SoL progress

Service Agreements awareness

MT0 OFF period: safe & transparent

Material for procedures APPROVAL

Operational feed-back & user consultation process

TARGET AUDIENCE

EGNOS & ESSP awareness

ESSP Points of Contacta

DIR

EC

TC

HA

NN

EL

us

ers

fora

, g

rou

ps

or

tas

k fo

rce

7 F

P

PR

OJ

EC

TS

PR

ES

S

ES

SP

W

EB

SIT

E

ANSPANSPANSPANSPANSPANSP ANSPANSPANSPANSPANSPNSA

EGNOS Service Agreements The need for

SES regulation requires that ANSPs using services from another ANSP shall formalise their working relationships by means of written

agreements setting out the specific duties and functions assumed by each

provider allowing for the exchange of operational data between the

service providers Those arrangements shall be notified to the national supervisory

authority

EGNOS Service Agreements: Objectives

To trigger the definition of an harmonized approach or the implementation of EGNOS based procedures by interacting with the appropriate stakeholders (ANSPs, NSAs, EC, etc.)

To gather the ANSPs operational needs and integrate them into the initial general agreement proposed.

To set a formal interface with the ANSP’s and define the appropriate points of contact (PoC) in every relevant matter within every ANSP for any coordination needed.

To understand the ANSP implementation plan for RNAV procedures based on EGNOS to ensure the availability of such Service Agreement to enable the corresponding approval processes.

EGNOS Service Agreements: Implementation Schedule

Progress on Service Agreement (SA) definition: General draft version already available General final version by end of July First SA ready for signature before the SoL Service declaration to

users

ANSPs involved so far:

Interaction mainly with ESSP shareholders for SA definition

Next step: Contact with the rest of European (EU) ANSPs and Contact with non-EU-with-coverage

EGNOS Service Agreements: SA’s structure (1/2)

Main structure of the agreement address legal and contractual clauses

For the time being the SA includes: ANSP and ESSP respective duties Liability allocation rules Service commitment (Annex 1) Operational coordination (Annex 2)

EGNOS Service Agreements: SA’s structure (2/2)

Annex I: The SoL service commitment equivalent to the content included in the SoL Service Definition

Document (SoL SDD) establish the terms & conditions of the Service provided together

with the performances & associated coverage areas as committed by the industry

Annex II: Service Arrangements Operational coordination identified to be included within the

agreement scope (e.g. NOTAM Proposal origination)

SoL Service Definition Document (1/3)

Define the conditions of access to the EGNOS SoL Service

EC Programme document

Prepared jointly by ESSP and EC

Part of the EGNOS Service Agreements with ANSPs

SoL Service Definition Document (2/3)

Draft SoL SDD version: end July 2010

Before MT0 removal

Final SoL SDD version: latest November 2010

Ready for SoL Service Declaration

EC Programme document

SoL Service Definition Document:

Content (3/3)

Terms and Conditions of use for SoL service General disclaimer & Warning

EGNOS information Service Provision Environment EGNOS SIS Certification & Receivers

EGNOS SoL Service Performance Commitments Definitions Commitments: Accuracy, Availability, Continuity, Integrity & Service

Area Real Performances

EGNOS SoL Service Limitations EGNOS SoL Service real performances

4.3 EGNOS User Support

EGNOS User Support

The EGNOS User Support activities are aimed at providing the user with an interface with the ESSP and EGNOS for technical

subjects a primary source of information on the status and

performances of the EGNOS services. The means to provide this service are mainly:

EGNOS User Support Helpdesk

EGNOS User Support Website

EGNOS User Support Helpdesk (1/3)

Via e-mail: egnos-helpdesk@essp-sas.eu primary user interface with EGNOS In order to complement the sources of information,

the EGNOS Helpdesk interacts with several entities, among them: GSA for EGNOS applications requests,

particularly from EGNOS applications developers.

EC for programmatic aspects

EGNOS User Support Helpdesk (2/3)

The main objectives of this service are:

To provide a single point of contact for EGNOS related requests

To get direct feedback from the EGNOS user on the way EGNOS is used To channel all the EGNOS operationally relevant information to the user.

Integration of the EDAS Service Heldpesk managing user questions and registration requests related to EDAS

EGNOS User Support Helpdesk (3/3)

EGNOS User Support Website (1/2)

http://egnos-user-support.essp-sas.eu

Provides users with information on the status of the EGNOS signal and its performances

As part of the website evolution program, additional contents are being developed in order to provide each user with the specific information for their activity: Open Service user

Safety of Life Service user

Technical user

EGNOS User Support Website (2/2)

The main contents currently provided by this website are: Signal in Space Status (PRN status, broadcast schedule, MT0

on/off)

EGNOS performances (availability, continuity, protection levels, perf. forecast)

Additionally, the registered users can subscribe to the following services: SiS outage alerts service (automatic information of SiS

outages by email) SiS advisory service (relevant information on SiS performaces

by email)

User Consultation Process (1/2)

ESSP

Communication Channels

MethodologyMail / E-mail /

Meeting - Workshop / EGNOS

User Support Website

Targeted Users

Aerial Works Users

Commercial air transport

users

General aviation users

Air Navigation

Service Providers

European / National

organisations

Identified equipped

operators / users

ANSP’s providing NPA

or LPV procedures

Specialized Press

User Consultation Process (2/2)

Regular Yearly User Consultation Process To comply with the applicable regulation At least once a year Linked to the company Annual Report

Specific User Consultation Processes EGNOS change/modification/new release

MT0 Observation Period Consultation Process So-called Observation Period Feedback from pilots For the 2-3 months after MT0 removal

4.4 EGNOS NOTAMs

81

ESSP Role

ESSP will be the EGNOS NOTAM Data Originator providing EGNOS NOTAM proposals to the NOFs

ESSP will not be an Aeronautical Information Services (AIS)

Generation

Formatting

Validation

Distribution

End user

Und

er th

e N

OT

AM

G

ene

rato

r re

spo

nsib

ility

Und

er th

e N

OF

resp

onsi

bilit

y

NOTAM proposal

Official NOTAM

Generation

Formatting

Validation

Distribution

End user

Und

er th

e N

OT

AM

G

ene

rato

r re

spo

nsib

ility

Und

er th

e N

OF

resp

onsi

bilit

y

NOTAM proposal

Official NOTAM

82

EGNOS NOTAMRoles & Responsabilities

(current status)

82

Courtesy Eurocontrol

Civil Aviation Users

ESSP

EGNOS prediction

EGNOS

AIS

EUROCONTROL

NOFNOF

NOF

AFTN & EAD

RAIM NOTAM proposals

EGNOS NOTAM proposals

RAIM predictions

EGNOS NOTAM

EGNOS predictions

Internet

RAIM NOTAMFormatting to NOTAM

GPS data collection

NANUs, Almanacs, GPS status

Secured Web service

GPS

GPS RAIM prediction

Formatting to Web

Formatting to NOTAM EGNOS NOTAM

proposals

AFTN

Civil Aviation Users

ESSP

EGNOS prediction

EGNOS

AIS

EUROCONTROL

NOFNOF

NOF

AFTN & EAD

RAIM NOTAM proposals

EGNOS NOTAM proposals

RAIM predictions

EGNOS NOTAM

EGNOS predictions

Internet

RAIM NOTAMFormatting to NOTAM

GPS data collection

NANUs, Almanacs, GPS status

Secured Web service

GPS

GPS RAIM prediction

Formatting to Web

Formatting to NOTAM EGNOS NOTAM

proposals

AFTN

Area of responsibility

Communication network

Legend:

AFTN address

GNSS system

Tools

Area of responsibility

Communication network

Legend:

AFTN address

GNSS system

Tools

83

ESSP Status

ESSP participating in two parallel activities:

Support to the implementation of the NOTAM service for SoL in aviation together with EC & Eurocontrol

Evolution: Support to the definition of an interface to automatically receive the EGNOS inputs (ATC IF)

84

EGNOS NOTAM Service Levels

Initial Service (Level 1+) will include NOTAM proposals resulting from: GNSS predicted outages generated min. 72 hours in advance GNSS unplanned outage handled within one working day, every

calendar day (7/7)

Next Service (Level 2) will include (target: end 2010) GPS unplanned outage handling within 2 hours, every

day of the week (H24/7)

85

EGNOS NOTAM Service Levels

Next service levels (Level3 & Level4) deployment are under discussion

Level3: GNSS unplanned outage handled within 2 hours (H24/7)

Level4: from GNSS unplanned outage handled within 15 minutes (H24/7) as per ICAO recommendation

86

ICAO SARPS Recommendation

Service Level 1+ is not compliant with 15 minutes advance notice requirement for unplanned events (from ICAO Annex 10 Attach D Section 9.3) EGNOS I/F readiness expected by ESR2.4.x

For automatically retrieving the EGNOS status and planned outages

EURONOTAM tool readiness expected by August But

EGNOS Declaration of SoL Service not compromised Not a requirement neither for ESSP certification nor for EGNOS

Declaration of Verification (DoV)

This recommendation is questioned and under discussion between Eurocontrol and ICAO

4.5 EGNOS Operations & Maintenance

EGNOS System Releases

1. ESRv2.2ext : operational since November 2008

2. ESRv2.3.1 : delivery by EC planned in Oct. 2010• Deployment : mid-2011• Contents : CPF upgrade + Inmarsat 4 GEO + Athens/Alexandria

RIMS + CCF upgrade Agadir/Abu Simbel/Tamanrasset RIMS

3. ESRv2.4.1 : expected delivery end 2011• Deployment : mid-2012• Expected contents : RIMS-D, NLES New Generation, CCF

Hardware & COTS, ASQF/PACF HW/SW• LPV200 & NOTAM tool ATC I/F

4. ESRv2.4.2 : expected delivery end 2013

Expected improvements

ESRv2.3.1 (operational mid-2011) Coverage Area extension

South ECAC (additional RIMS) Northern ECAC (improved ionosphere monitoring)

Improved robustness (CPF upgrades)

ESRv2.4.1 (operational mid-2012) Improved robustness & performance (resolution of obsolescence

issues: RIMS-D, new NLES, CCF hardware) Coverage Area extension Improved level of service with LPV200 Improved NOTAM service

Operations & Maintenance

Strong confidence from ESSP Operations & Maintenance proved by continuity of EGNOS SIS provision ensured at 99,999% since beginning 2009 in parallel with : Company re-organisation (from ESSP EEIG to ESSP SAS) Support to SES Certification process, Negotiation of new contracts (with EC & with ≈ 30 subcontractors), Management of recurrent EGNOS obsolescence issues, Support to major system evolutions (e.g. EWAN migration)

ESSP also demonstrated its ability to purchase system upgrades from Industry in parallel to System Releases delivered by EC E.g. PSS1 ESR purchased to TAS in Dec. 2009

5. Status of FP7 projects related to EGNOS trials

Questions?

Conclusions

ESSP mission is to be the certified EGNOS SoL service provider

EGNOS Open Service available since Oct.09 EGNOS Service Provision performances are at

excellent level ESSP Certification and EGNOS Declaration of

Verification by mid July 10 EGNOS SoL service is almost there (latest 3 Nov.10) First use in civil aviation with precision approach

procedures (APV) planned before end 2010

Summary and Conclusions

95

Contact ESSP

ESSP Website: www.essp-sas.eu

EGNOS User Support: Website: http://egnos-user-support.essp-sas.eu/ Helpdesk: Egnos-helpdesk@essp-sas.eu

ESSP SAS18, avenue Edouard Belin - BPI 60231401 Toulouse Cedex 9FRANCE

21/04/23

The EGNOS Services Provider

Thank You!

Back-up Slides

EGNOS Open ServiceOS Receiver (II)

MT Function

MTs 9 & 17 User Geostationary satellite ranging function

This function is currently not supported by EGNOS

MTs 2-5

MT 1 (SVN)

Decode and apply satellite clock corrections

MTs 24-25 Decode and apply satellite ephemeris corrections

MT 26

MT 18 (IGPs)

Decode and apply ionospheric corrections

MTs 2-5 & 6 Take into account major warnings

MT12 (optional) May use the content of message type 12, if used for time determination

Minimum Set of functions expected for an OS receiver

99

EGNOS NOTAM Roadmap

99

E2E Validation Service Level 1+ Service Level 2

1 June 2010 1 Sep 2010

Insfrastrutcture preparation

EURONOTAM V.2 DELIVERY

1 Nov 2010

Feasability SL2

Contract for SL2

Feasability SL3

Contract for SL3

ATC IF Deployement

(TBD)

RTPM Deployment

(TBD)

Service Level 3

Feasability SL4

Contract for SL4

Service Level 4Without transfer(TBD) With transf.

SoL Declaration

EURONOTAM V3 DELIVERY

EURONOTAM V4 DELIVERY

EURONOTAM V.2.1 DELIVERY

Service Level 4 conditioned to:

-EGNOS I/F deployment (V2.4.1) EC -NOTAM Tool readiness EC / Eurocontrol-Required contractual framework EC-RTPM Deployment ESSP

Safety Management

101

Safety Incident Management Process (1/2)

Focuses on acknowledged events at User level Critical : Loss Of Integrity Major : Loss Of Continuity on a significant area

Appl. French Reg. (Arrêté du 26/03/04, Arrêtés du 17/08/07)

Includes a step for emergency measures

Safety Incident Management Process (2/2)

Includes timing target for important steps

3WD for notif. Of critical incidents;

5WD for prelim. Investigation of critical incidents

PRO-13

Launch Emergency / mitigation measures

PASSQ, SOU, SPU, MCC, NSA, EC

Confirm and notify incidentPASSQ, SOU, SPU

OCB

European Commission,

NSA

Close the Safety Incident Report (SIR)

PASSQ, SOU, SPU, MCC, EC

PRO-12 – OR Management

Process

System / Mission

performance monitoring

SIR initialized

SIR final issue

Safety Incidents,OR,

Integrity Issue,Performance Anomalies Safety Incident Notification

Applied on 11 MAJOR incidents 1 CRITICAL Incident

Security Management

Information Security Management System (SecMS)

(1/3)

Scope of ESSP SecMS Agreed with EC Successfully audited by NSA

Planned evolution of ESSP SecMS scope (next 4 years) Current scope: EGNOS Assets + TWAN + Legal Archives +

Tools Target: full ESSP scope of activities

Major documents describing the ESSP SecMS• The ESSP Security Management Plan • The ESSP Security Management Manual

Information Security Management System (SecMS)

(2/3) SecMS addresses EC 2096 security

requirements through ISO/IEC 27001 standard Primarily

Security Governance & Policies Security Risk Management Process Security Incident Management Process Security Awareness Security Audits

Additionally : ESSP specifics Restricted Documentation Management Process Site Security Management Plan

Information Security Management System (SecMS)

(3/3)• Next steps

• Implement the ESSP Security Management Plan

• Take onboard the NSA Security audits recommendations and findings

• Complete the security requirements for the next version of the SPRD (fall 2010)

• Consolidate Security baseline with EC (security governance)