international programmes gnss monitoring meetings seminars and workshops/pbn a… · international...

International Programmes &

GNSS Monitoring

Patrizio Vanni ([email protected])

GNSS expert

ICAO PBN and PANS-OPS Provisions Implementation workshop

Minsk, 8 April 2015

Contents

• ENAV profile

• BLUEMED

• MEDUSA’s technical assistance in aviation

• GNSS monitoring activities

• Conclusions

2 PBN and associated PANS-OPS Provisions Implementation

Workshop - Minsk - April 2015

Company profile

Flights handled in one year

Peak of flights managed in one day

Control Towers (TWRs)

Area Control Centers (ACCs)

Total sq km of airspace managed

Air/ground contacts per year

ENAV Group Employees

Hours of training imparted

ENAV contributes to the

of the national

guaranteeing the and

within the Italian air space to

all categories of users,

respecting the international

obligations of the country

Such objective is to be reached

by achieving the company's

and by

satisfying users’ needs in

terms of and

The company directly provides

, ensuring

the highest standards in flight

safety

Punctuality: Top 5 2012

PBN and associated PANS-OPS Provisions Implementation Workshop - Minsk - April 2015

3

Ownership and Partnership

16,67%

Maintenance, development

and operative management

of ATM Hardware and

Software

R&D activities in the ATM

domain

Provision of Air Navigation

Services and Systems in the

Asia Pacific area

Service Provider of the

European Satellite

multimodal Service EGNOS

ADS-B via satellite

12,50%


4

Participation to PBN/GNSS Groups


5


6

• Regional ATM deployment project aiming towards the creation of a Functional Air Block (FAB) in the South East Mediterranean area under the SES regulatory framework

• FABs represent one of the pillars of the implementation of the SES regulatory framework, and are expected to implement in a synchronized manner all SESAR deliveries

• Harmonize a large portion of the Mediterranean airspace joining the EU core area with the African and Middle-East borders

• State Level Agreement (SLA) signed on 12 October 2012, is the final step of the FAB establishment through the continuous

implementation of a number of operational

solutions and the deployment of identified

technical enablers


7

BM Implementation Programme

• The BLUE MED Implementation Programme (BM-IP) is the agreed roadmap of all the deployment initiatives undertaken by the BM Partners

• Performance-driven approach

• Is a living document to be updated regularly in order to ensure its full compliance with Members’ needs and priorities as well as with EU and ATM Industry expectations

• Incremental approach

• Requires tight coordination among BM Partners to ensure synchronization of deployment and mutual transfer of expertise, concepts and practices

• Is open to collaboration at inter-FAB level and with non-EU Countries to improve coordination and optimization


8

PBN Implementation Roadmap

• BLUEMED PBN Task Force setup – Meeting through webex and F2F meetings

– BLUE MED PBN Implementation Policy

– PBN implementation roadmap • RNP APCH

• Other phases of flight will be investigated in next meetings

– Sharing of expertise and lessons learnt

– EC funding opportunities (H2020 framework)

• Interests on collaborating with neighboring States and FABs


9


10

http://it.wikipedia.org/wiki/File:Flag_of_Egypt.svg

http://it.wikipedia.org/wiki/File:Flag_of_Israel.svg

http://it.wikipedia.org/wiki/File:Flag_of_Algeria.svg

http://it.wikipedia.org/wiki/File:Flag_of_Libya.svg

http://it.wikipedia.org/wiki/File:Flag_of_Lebanon.svg

http://it.wikipedia.org/wiki/File:Flag_of_Jordan.svg

http://it.wikipedia.org/wiki/File:Flag_of_Palestine.svg

http://it.wikipedia.org/wiki/File:Flag_of_Morocco.svg

http://it.wikipedia.org/wiki/File:Flag_of_Syria.svg

MEDiterranean follow-Up for EGNOS Adoption: • May 2012 – end of 2015 • Pool of EU experts with the involvement of Euromed organizations:

– Telespazio (coordinator), ENAV, Ineco, Helios – ESSP support on performance assessment and operational introduction

• Euromed partner countries: – Algeria, Egypt, Israel, Jordan, Lebanon, Libya, Morocco, Palestine, Syria,

Tunisia

Goal: • Best practices sharing • Assistance to countries towards the exploitation of EGNOS services and

operational adoption • Technological transfer and capacity building • Networking and cooperation activities (public events, workshops)



ENAV role in Medusa

ENAV participates in Medusa to provide specific expertise on:

• Procedure design

• PANS-OPS training

• ICAO regulations

• GNSS monitoring

• Pilots

• Flight inspection

• EGNOS use in operations


12

EGNOS coverage in Euromed region



ESSP August 2014 monthly performance reports

Technical assistance in aviation

• Regional • Regional

• National

• Sub-regional

• Regional

• National

• Sub-regional

• Regional

Monastir RNP approach case

study

GNSS data recording and

monitoring

“International regulatory

baseline” for EGNOS

approaches implementation

Euromed regional

coverage needs



Monastir RNP app. case study (1/2) • Goal: technical assistance action to support the implementation of

GNSS approach (RNP APCH) and EGNOS based approach operations

• Validation for the airport of Monastir (Piaggio P180 Avanti)

• First complete experience for the use of EGNOS SoL service outside Europe


15

Monastir RNP app. case study (2/2) Process compliant towards ICAO but also taking in account Eurocontrol guidelines • Design of procedures in a “3 minima lines combined chart” (Doc8168, Annex 14,

Annex 15) • FAS data blocks codification & airborne data bases generation (Doc8071, Annex

10) • Training • Validation flights campaign (Doc8071) • Safety Case (Doc9859) • Business Assessment • Installation and operation of a GPS/EGNOS receiver for GNSS performance

monitoring • Technical assistance for the procedures publication and for the operational

introduction (list of “to-dos”) • Exploitation towards operations/publication of the GNSS procedures:

– Requirements on GNSS data recording/monitoring (Annex 10, Doc9849) – Elaboration of list of to-dos & analysis of regulatory/service provision framework for

LPV operations


16

Euromed regional coverage needs Deliverable: • Euromed regional coverage needs/priorities (in terms of

aerodromes with favorable conditions for LPV introduction)

• Recommendations for the roadmap related to deployment of the infrastructures necessary to extend the EGNOS service coverage across the Euromed area

• Criteria/drivers: – SoL coverage on country’s aerodromes – High-level official commitment in relation to the operational

implementation for EGNOS SoL/LPV – Inputs from Countries project focal points


17

The main actors in EGNOS

EC

ESA


18

• EC: EGNOS System owner

• GSA: Programme Manager

• ESSP: EGNOS Service Provider

• ESA: System Architect

International regulatory framework (1/2)


19

ICAO

SES

National

• Essential steps required for EGNOS based operations implementation in aviation in the Euromed countries:

Bilateral International Agreement

•Actors: State/EC

•This Agreement is aimed at clarifying the overall framework/provisions for the use of EGNOS SoL service in the non-EU country (such as the governance, financial and liability terms), and defining the regulatory (mutual recognition) aspects in the aviation domain

Working level Agreement

•Actors: ANSP/ESSP

•Formalization of operational/technical modalities in support to LPV introduction, including also the delivery of additional services (NOTAM proposals, Data recording, Collaborative Decision Making)

• Minimum regulatory baseline/set of

minimum operational requirements based on ICAO relevant documents (GNSS manual, PBN manual, Annex 10, Safety oversight manual) needed to start the process with EC and ESSP

• Gap analysis for each non-EU country and proposing recommendations/actions (ongoing)

• Sharing with interested neighboring regional bodies and initiatives

Activity on going


20

International Agreement

[State/EC]

EWA

[ANSP/ESSP]

ICAO Compliance

International regulatory framework (2/2)


21

ICAO Doc Title Volume/Section (*) Area

Annex 2 Rules of the Air Chapter 3. General rules Chapter 5. Instrument Flight rules

General-ATS

Annex 4 Aeronautical Charts Chapter 11. Instrument Approach Chart Chapter 13. Aerodrome/Heliport Chart

General-AIS

Annex 10 Aeronautical Telecommunications Volume I Volume II Volume III

NOTAM proposal and distribution Data recording/ Performance

monitoring

Annex 11 Air Traffic Services Whole document General-ATS

NOTAM

Annex 13

Aircraft Accident and Incident investigation

Whole document Accident/incident

investigation/reporting

Annex 15 Aeronautical information services

Chapter 5. NOTAM Chapter 10. Electronic terrain and obstacle data Appendix 4. Information to be notified by AIRAC Appendix 5. Predetermined distribution system for NOTAM Appendix 6. NOTAM format Appendix 7. Aeronautical data quality requirements Appendix 8. Terrain and obstacle data requirements

NOTAM proposal

Doc. 8126 Aeronautical information services Manual Chapter 6. NOTAM/Appendix A, B & C NOTAM formatting

Doc. 8168 Procedures for Air Navigation Services- Aircraft Operations (PANS-OPS)

Volume I. Volume II. Flight procedures design

Doc 8071 Manual on Testing of Radio Navigation Aids

Volume II. Testing of Satellite-based Radio Navigation Systems/Chapter 3. Satellite-based augmentation systems (SBAS) Data recording/ Performance

monitoring

Doc 9613 Performance-Based Navigation (PBN) Manual

Volume I. Concept and Implementation Guidance/Part B. Implementation guidance Volume II. Implementing RNAV and RNP Operations

General

Doc. 9859 Safety Management Manual Chapter 7. Hazard and incident reporting Chapter 9. Safety analysis and safety studies Chapter 13. Safety Assessments

General-Safety

Doc. 9906 Quality Assurance Manual for Flight Procedure Design

Volume I. Flight Procedure Design Quality Assurance System Volume II. Flight Procedure Designer Training Volume V. Validation of Instrument Flight Procedures Volume VI. Flight Validation Pilot Training and Evaluation

Flight procedures design/implementation

Other activities • Contribution to the elaboration of an example of GNSS data

analysis/recording activity

• GNSS approach procedures for Beirut APT – Development of GNSS approach procedures (including LPV) – Safety case and guidelines on safety requirements

• PANS OPS 8168 Advanced Class in Morocco

– PBN Concept – GNSS instrument flight procedures - General Criteria – Non precision approach procedures construction (LNAV minima) – Localizer Performance without Vertical Guidance (LP minima) – APV/BARO vertical navigation procedures construction (LNAV/VNAV

minima) – APV/SBAS vertical navigation procedures (LPV minima)


22


23

Preamble • At ICAO NSP#14 (November 2013) a working paper presented by Italy

identified the need for further guidance on GNSS monitoring, including details on the objectives, acceptable methodology, policy for the retention of data, reporting and notification process in case of anomaly.

• A Drafting Group was established to start preparing guidance material on GNSS monitoring.

• Participants: – USA – UK – Eurocontrol – EC – Canada – Netherlands – Russian Federation – Italy

– ICCAIA

– Germany

– Japan

– Australia

– Spain



GMDG activities

• As first step, the GNSS Monitoring Drafting Group is preparing guidance

material on GNSS performance assessment and legal recording and will

propose amendments to relevant documentation.

• Activities:

– Definition of requirements for performance assessment and legal recording

– Definition of a common vocabulary and GNSS Monitoring concept

– Definition of Performance Assessment Methodology

– Identification of documentation impacted

• Since November 2013 several teleconferences have been held. Results will

be presented at next NSP (April 2015)



States concerns

• Why GNSS Monitoring?

• What performance parameters need to be monitored for GPS and for the others constellations? and why?

• How to measure these parameters? Which density of stations is needed? What computation methodology? Which tools? How often performance reports are needed?

• Who should measure the parameters? States/NSAs, ANSPs, the core constellations service providers? International/regional organization?

• What to do if degradations/anomalies are measured?



Requirements identification

Id Ref. Category Requirement

GNSS-1 Att.D #12 Objectives Data recorded can be used periodically to confirm GNSS performance

GNSS-2 Att.D #11.1 General All parameters available to users within a given service area should be recorded at

representative locations in the service area

GNSS-3 Att.D #11.2 General Recording system need not be independent

GNSS-4 Att.D #11.2 Recording Recording System may be delegated to other States or entities

GNSS-5 Att.D #11.2 Recording Data shall be logged continuously at 1Hz rate

GNSS-6 Att.D #11.3 Recording Observed satellite carrier-to-noise density (C/N0)

GNSS-7 Att.D #11.3 Recording Observed satellite raw pseudo-range code and carrier phase measurements

GNSS-8 Att.D #11.3 Recording Broadcast satellite navigation messages, for all satellites in view

GNSS-9 Att.D #11.3 Recording Relevant recording receiver status information

GNSS-10 #2.1.4.2 Objectives State should monitor and record relevant GNSS data to support accident and

incident investigations.

GNSS-11 #2.1.4.2 Recording A State should ensure that GNSS data relevant to the operations required are

recorded

GNSS-12 #2.1.4.3 Recording Recordings should be retained for a period of at least fourteen days. When the

recordings are pertinent to accident and incident investigations, they should be

retained for longer periods until it is evident that they will no longer be required.

GNSS-13 #2.1.4.3 Performance GNSS-6/7/8/9 support periodic confirmation of GNSS performance in the service

area.

27

[1] To be noted that this is a minimum requirement and that could be adjusted in order to be compliant with National Legislations for accident and incident investigations.

Requirements extracted from Annex 10 vol.I


GNSS Monitoring Concept

GNSS Monitoring

GNSS Performance Assessment

GNSS Recording

GNSS Real-time Monitoring

GNSS interference monitoring



Proposal definition • GNSS performance assessment: is a periodic off-line activity

performed by a State, or delegated entity, aiming to demonstrate SIS conformance vs. Annex 10 relevant requirements, it can be done at system and/or application level.

• GNSS real-time monitoring: is an activity performed by a State, or

delegated entity, whose main objective is to provide information to technical staff and ATC services on the operational status of GNSS services in relation to a defined operation. – GNSS Interference Monitoring: is a real time monitoring sub activity

performed by a State, or delegated entity, whose main objective is to provide warning to technical staff and/or ATC services in case of detection of interferences on relevant GNSS band for a specific location.

• GNSS recording: is an activity performed by a State, or delegated entity, whose objective is to have GNSS status historical data to support post-incident/accident investigations. It could cover also the legal recording part depending on national regulations.



Performance Assessment Process



Main outcomes [1/2] • Integrity is the most critical parameter, due to its link to safety. It is applicable and

measureable to the total system (including RAIM) and not to the core constellation itself. Different approaches for integrity are taken:

– For ABAS, integrity monitoring is done at airborne level with RAIM. Receivers that are certified in accordance with relevant international standards (e.g. MOPS, TSO series) have been designed to meet the integrity requirement defined in Table 3.7.2.4-1 of Annex 10 assuming GPS is compliant with key parameters defined in GPS SARPs Annex 10 and GPS SPS PS.

– For SBAS, integrity monitoring is done at ground segment level and the verification and assurance is given by the SBAS service provider.

– For GBAS a similar approach to SBAS is taken with responsibilities to national ANSP.

It is suggested that States do not have to implement monitoring capabilities for integrity since integrity is provided in real time by RAIM, SBAS or GBAS depending on the augmentation in use.



Main outcomes [2/2]

• Availability, accuracy and continuity may have a different meanings (e.g. the meaning of continuity parameter for SIS performance requirements is different from the one defined for the SPS).

• Development of criteria (taking in account satellite geometry, tropospheric/ionospheric delay) for the determination of density of stations that can produce suitable performance reports and can be used for data recording



Parameters proposal Performance Parameter Definition Targets

Positioning Accuracy 95 percentile of the position error measured, intended as difference between

the estimated position by the receiver and the reference position, calculated

over an interval of 24hrs, for any point considered within the service volume.

§3.7.3.1.1.1 for GPS

§3.7.3.2.1.1 for GLONASS

the targets reported referred to space/control segment only

and does not take in account atmospheric or receiver errors.

Range Domain Accuracy

(Instantaneous URE)

Difference between the pseudorange measured at a given location and the

expected pseudorange as derived from the NAV message.

§3.7.3.1.1.3 for GPS

§3.7.3.2.1.3 for GLONASS

The reported targets referred to space/control segment only

and does not take into account atmospheric or receiver

errors.

Availability Percentage of time over any 24hrs interval that the position accuracy is less

than a specified value within the service volume.

§3.7.3.1.2 for GPS

§3.7.3.2.2 for GLONASS

The targets do not take into account atmospheric or receiver

errors.

Probability of major service

failure

Probability that over a specific time interval, a healthy satellite’s ranging signal

error (excluding atmospheric and receiver errors) exceeds a specific range error

limit.

Up today only GPS targets exists as defined in §3.7.3.1.4.

Continuity Continuity of service of a core constellation is the capability of the core

constellation to perform its function without unscheduled interruptions (e.g.

loss of availability, loss of PVT computation, etc) during the intended nominal

operation.

§3.7.3.1.5 for GPS

§3.7.3.2.2 for GLONASS

Probability of simultaneous

major failures of 2 or more

satellites

Probability of simultaneous failure (under the same conditions defined for

major service failure) of 2 or more satellites.

1x10-9



Observations

• Error components assigned to Space and Control Segments (error budget components assigned to the User Segment such as the atmosphere, multipath, and receiver noise).

• For some parameters the target “average location” is used for stations disseminated globally so sometimes could be more useful to refer to the worst case target only, depending on the geographical extension of the area considered and number of stations used for the performance computation.


34

Approach proposed

Today

• Use public reports provided by GNSS service providers or by other Organizations;

• Establish formal agreement with neighbouring State that is publishing performance reports and could cover the national interested area;

• Implement its own solutions in line with the guidelines provided in this document.

2020+

• Core constellation service providers to provide global periodic performance reports towards relevant SPS parameters identified in Annex 10 vol.I.

• Reports can be used by States in combination or substitution of what already implemented.



Preliminary conclusions

• State Safety Oversight Function

• Ensure performances vs SARPS WHY?

• Significant core constellation parameters WHAT?

• Network of stations (IGS, EDAS, etc)

• Off line activity HOW?

• State, International Organizations

• Core constellation service provider WHO?

• Share reports

• Escalate to International Organization IF?


36

Next steps

• Inclusion of definitions in Annex 10 vol. I

• Guidelines to be included in

Doc9849 GNSS Manual

• Real time monitoring concept…

– Output from SESAR activities



RACOON: the ENAV Initiative

• Demonstration activity in the context of SJU Very Large Scale Demonstrations

• 2-year project (Fall 2014-Fall 2016) • Demo on Milano Linate airport, including remote ATS

service provision from Remote TWR Center located in Milano Malpensa

• Topics: – Remote TWR for Single and Multiple Airports – RNP APCH procedures – GNSS approaches for helicopters – GNSS Monitoring (including real time solutions)

PBN and associated PANS-OPS Provisions Implementation

Workshop - Minsk - April 2015 38

Conclusions

• Take opportunities offered by agreements with FABs (sharing of resources, knowledge, training, etc)

• Harmonized regional cooperation

• GNSS monitoring – top down approach (ICAO framework)

• Prepare to the challenging future for GNSS (new core constellations)


39


40

[email protected]

international programmes gnss monitoring meetings seminars and workshops/pbn a… · international...

Documents