ADQ IR Implementation

Transcription

1 ADQ IR Implementation DSNA experience Direction Générale de l Aviation Civile

2 CONTENTS DSNA considerations ADQ objectives The context : a coordinated approach DSNA approach to ADQ implementation The pillars The initiatives Challenges, issues and DSNA suggestions The main challenges The various issues - and suggestions European regulation for AIS-AIM and ADQ

3 DSNA CONSIDERATIONS Data Quality is a «must» to meet the required level of safety to meet our user requirements to enable key modern ATM applications (PBN, airspace management, etc.) to support interoperability DSNA support to ADQ objectives From the early days of ADI to 73/2010 up to ADQi WG setup Active involvement in the development of Eurocontrol specifications

4 DSNA CONTEXT Regulator DSNA NSA HEADQUARTERS Planning and Strategy Resources Safety Quality Security Mgmt TECHNICAL DPT ATM systems CNS systems R&D European projects OPERATIONS OPERATIONS 5 ACCs 11 Regional Air Navigation Services (APP / TWR) Aeronautical Information Service Central Systems OTHER RELATED STAKEHOLDERS Airports, Airlines, National Geographic Institute, FABEC, foreign AIS-P,

5 DSNA ADQ pillars

6 DSNA ADQ pillars Originator Data sets EAD AI Data Administrator NOPIA Data Centric Approach Traceability Impact management Products and Services AIP Administrator Cartographer

7 ONGOING INITIATIVES LINK WITH DATA ORIGINATORS Data originators Data providers AIS provider SPECS Survey Procedure Design Airspace design SPECS Data collection V&V SPECS AIS provisions Data publication

8 ONGOING INITIATIVES LINK WITH DATA ORIGINATORS Formal arrangements DSNA provides support to develop them Data origination specifications Based on Eurocontrol specifications when applicable Further refined to best fit the national context Consolidated with national experts (eg NGI) Digital data exchanges Work in Progress

9 THE MAIN CHALLENGES Scope of the rule Originators number and diversity (within and beyond SIA, DSNA or even DGAC) Impact on many systems (SDO, INO, Procedure Design, data provision systems e.g. PIB) System acquisition or upgrades Financial aspects Operational implementation Timeframe Many evolutions (AIS to AIM, data scope growth) Operational considerations take precedence

10 ISSUES (1) NOTAM and existing systems NOTAM system based on a legacy system feeding many operational applications NOTAMs are mainly text messages System upgrade financially arguable and potentially detrimental to operations DSNA suggestion: clarify ADQ applicability to NOTAM

11 ISSUES (2) Technical aspects CRC standard (technical solution) vs data protection target (performance requirement) Metadata : exchange vs collection DSNA suggestion: revisit these technical points in a rule update

12 ISSUES (3) Data exchange format AIXM fully supported Version 5 characteristics are very stringent Evolution to AIXM 5 takes a lot of time AIXM 4.5 can be an intermediate step DSNA suggestion: accept AIXM 4.5 as an intermediate step for data exchanges

13 APPLICATION DATES Intermediate dates Correspond to one specific stepped approach Does not necessarily match all increment types Final date Sets the overall implementation initiative It should remain unchanged DSNA suggestion: consider intermediate dates as recommended steps

14 WAY FORWARD EU AIS-AIM REGULATION ADQ is a good basis for any EU AIS-AIM rule Address all data quality related items Includes origination as one actual key step for data quality Ensures interoperability But sometimes too detailed EASA AIS-AIM RMG is a good follow-up In line with the overall EU rule-making process Extends provisions beyond data quality only But does not address the origination part

15 WAY FORWARD EU AIS-AIM REGULATION In the long term Strong case for one and only one rule No break in momentum for ADQ compliance Take advantage of the evolution to strenghthen key points of ADQ and address existing issues

16 THANK YOU FOR YOUR ATTENTION