ADQ Aeronautical Data Quality

Transcription

1 ADQ Aeronautical Data Quality Ulan Bator, Mongolia May, 2013 Simone Gabriele

2 Outline Introduction - ADQ is Regulation Context ADQ IR Structure Means Of Compliance IDS Approach to ADQ Implementation ADQ Implementation Example (PLanning extensions) 2

3 Outline Introduction - ADQ is Regulation Context ADQ IR Structure Means Of Compliance IDS Approach to ADQ Implementation ADQ Implementation Example (PLanning extensions) 3

4 Why ADQ... Introduction The European Organization for the Safety of Air Navigation (EUROCONTROL) was mandated to develop an interoperability Implementing Rule (IR) that supplements and strengthens the requirements of the International Civil Aviation Organization's (ICAO) Annex 15, in order to achieve aeronautical data and information of sufficient quality to support current and future flight operations. 4

5 ADQ is... Introduction European Regulation 73/2010 (Compliance dates ) Laying down requirements on the quality of aeronautical data and information Key enabler of the European Air Traffic Management Network (EATMN) and Single European Sky 5

6 ADQ Key Provisions Introduction QUALITY INTEROPERABILITY AND PERFORMANCE CONFORMITY ASSESSMENT 6

7 ADQ Stakeholders Introduction Applicable to all the actors interacting with aeronautical data from data originators to publications: Surveyors Procedure Designers Aerodrome Authorities Air Navigation Services Aeronautical Information Services Civil Aviation Authorities Industries (System providers) 7

8 Introduction ADQ-2 Objective: develop a draft SES interoperability implementing rule to achieve aeronautical information of sufficient quality in the aeronautical data chain from post-publication by the AIS provider to the end-user. Purpose: Provide the data quality required to enable current and future concepts such as Performance Based Navigation (PBN) Apply common quality measures throughout the data supply chain Output: Proposals are currently being drafted. 8

9 Outline Introduction - ADQ is Regulation Context ADQ IR Structure Means Of Compliance IDS Approach to ADQ Implementation ADQ Implementation Example (PLanning extensions) 9

10 Regulation Context ESSENTIAL REQUIREMENTS FOR INTEROPERABILITY Reg. 552/ Mar 2004 on the interoperability of Air Traffic Management network For all system and constituents of the EATMN currently by 20 April 2011 INTEROPERABILITY IMPLEMENTING RULES Mean of Compliance: - EUROCONTROL SPECIFICATION - COMMUNITY SPECIFICATION Reg. 73/ /01/2010 laying down requirements on the quality of aeronautical data and aeronautical information for the single European sky Electronic AIP (eaip) Data Assurance Level (DAL) Data Origination (DO) Aeronautical Data Exchange (AIX) Data Quality Requirements (DQR) Application from 01 July 2013 Aeronautical Data and Aeronutical Information published before 01 July 2013 and not amended shall be brught in line with this regulation by 30 June 2017 at latest v. 2.0 Released Feb v. 1.0 Released Mar v. 1.0 Released Feb v. 1.0 Released Dec v. 1.0 Released Feb

11 ADQ Reg73/2010 CHAPTER I General Provisions Articles 1-3 Aeronautical Data Process CHAPTER II Interoperability and Performance Articles 4-9 (ANNEX I-VI) CHAPTER III Quality, Safety and Security Management Article 10 (ANNEX VII) ADQ Structure Means of Compliance Eurocontrol Specifications Electronic AIP (eaip) Data Assurance Level (DAL) Data Origination (DO) Aeronautical Data Exchange (ADE) Data Quality Requirements (DQR) Other Guidelines Service Level Agreement (SLA) CHAIN CHAPTER IV Conformity Assessment and Additional Requirements Articles (ANNEX VIII-XI) CHAPTER V Final Provisions Articles

12 Data Set Requirements ADQ Requirements Data Set Definition : AIP Aerodorme Mapping Electronic Obstacle Data Electronic Terrain Data Metadata M.O.C. Eurocontrol Specifications Aeronautical Data Exchange (AIX) 12

13 Data Exchange Requirements ADQ Requirements XML Aeronautical Data Terrain Data ICAO standards Aeronautical Information Readable on Computer Screen Aeronautical Information M.O.C. Eurocontrol Specifications Aeronautical Data Exchange (AIX) Electronic AIP (eaip) 13

14 The AIX addresses : Integrated Aeronautical Information Package (IAIP) Aerodrome mapping Electronic obstacle Means Of Compliance - AIX Aeronautical Information Exchange (AIX) Specification data set specification and data exchange format requirements AIX and the supporting Guidelines is implemented as a layer between the ADQ IR and the AIXM 14

15 Electronic AIP (eaip) Specification Means Of Compliance - eaip The scope of eaip specification covers the visual presentation of the IAIP (Integrated Aeronautical Information Package) including the AIP, AMDTs, SUPs and AICs. ADQ IR requires them to be presented in a way that allows the content and format of the documents to be directly readable on a computer screen. The presentation of charts, including the text on these, is excluded The eaip is not intended to support the Digital Notice to Airmen (NOTAM) 15

16 Data Quality ADQ Requirements Requirements Definition Data Origination Data Process Definition and Tracking Aeronautical Data Process Data Request Data Origination Data Measurement Data Derivation Evaluation and Approval Product Preparation Product Distribution 16

17 Data Quality Define Requirements Data Quality Requirements in terms of: Accuracy Resolution Integrity ability to determine the origin of the data M.O.C. level of assurance that the data is made available on time ADQ Requirements Eurocontrol Specifications Data Quality Requirements (DQR) Data Origination Integrity Accuracy & Resolution Data Request Data Measurement Data Derivation Evaluation and Approval Product Preparation Product Distribution 17

18 Means Of Compliance - DQR Data Quality Requirements (DQR) Specification The DQR introduces: Data Quality Requirements Harmonised List (DQR HL) Initial set of geospatial and other navigation data items, limited to those included in Appendix 7 of ICAO Annex 15 Integrity and resolution data quality requirements are transposed literally from ICAO Annex 15 Accuracy data quality requirements are transposed literally from ICAO Annex 11 and ICAO Annex 14 A standardized process for the derivation and validation of new or updated data quality requirements: Addition\Modification\Removal of data items Minimum requirements for the safety assessment for establishment of data quality requirements 18

19 Data Quality ADQ Requirements Procure Data Formal arrangements with Data Originators M.O.C. Other Guidelines Service Level Agreement (SLA) Service Level Agreement (SLA) Data Origination Data Request Data Measurement Data Derivation Evaluation and Approval Product Preparation Product Distribution 19

20 Service Level Agreement (SLA) Guidance The SLA Guidance act as an introduction to the SLA as follows: Introduce the concept Provide a template Provide guidance on its negotiation, agreement and implementation Means Of Compliance - SLA 20

21 Data Quality ADQ Requirements Assure Accuracy and Resolution Data Origination Requirements M.O.C. Eurocontrol Specifications Data Origination (DO) Data Request Data Origination Data Measurement Data Derivation Evaluation and Approval Product Preparation Product Distribution 21

22 Means Of Compliance - DO Origination of Aeronautical Data (DO) Specification The DO extends and updates concepts present in the ICAO Doc 9674 The WGS-84 Manual (guidance for surveyors), and provides requirements in terms of: Data Quality Validation and Verification Reference System Specification Survey Units of Measurement Instrument Flight Procedure Design Data Product Specification Airspace Design Categories of Data Data Processing Data Exchange 22

23 Data Quality ADQ Requirements Assure Integrity (preserve Accuracy and Resolution) Data Process Evidence Error Reporting and Rectification M.O.C. Eurocontrol Specifications Data Assurance Level (DAL) Other Guidelines CHAIN (AIS Data Process) Data Assurance Level (DAL) Data Request Data Measurement Data Origination Data Derivation AIS Data Process (CHAIN) Evaluation and Approval Product Preparation Product Distribution 23

24 Means Of Compliance - DAL Data Assurance Level (DAL) Specification The DAL introduces: Definition of Data Assurance Levels (DALs), mapped to the defined ICAO Data Integrity Level (DIL) Objectives applicable to each of the DALs, in terms of : Measurement, Data Processing, Data Checking, etc. (Based on the ATM error Barrier Model) Survey Validation Procedure Design Authentication Activities Data Preparation Data Publication/ Distribution Data Application Integration End Use Data Error Accident Introduced Errors 24

25 ADQ Implementation Benefits Implementing ADQ Improve the quality Improve the performance Reduce the costs Increase the Business 25

26 Outline Introduction - ADQ is Regulation Context ADQ IR Structure Means Of Compliance IDS Approach to ADQ Implementation ADQ Implementation Example (PLanning extensions) 26

27 IDS Approach to ADQ Implementation IDS Approach Services for the complete project implementation Solution necessary to comply with regulation Life Cycle Support & System Quality Maintenance 27

28 IDS Services IDS Services Assessment of initial status Impact assessment Solution provision Validation and verification Training & awareness 28

29 IDS Services months Initial Assessment Impact Assessment Default Project Implementation Solution provision Validation & Verification Training & On the Job Training 29

30 IDS Solutions 30

31 IDS Solution & ADQ Implementation IDS Solutions Data Origination Data Request Data Measurement Data Derivation Evaluation and Approval Product Preparation Product Distribution etod Suite FPDAM Suite Airspace Designer PLX IAS Data Maintenance AeroDB (AIXM 5.1) IAS Publishing (eaip) IAS GIS Charting Digital data dissemination 31

32 Outline Introduction - ADQ is Regulation Context ADQ IR Structure Means Of Compliance IDS Approach to ADQ Implementation ADQ Implementation Example (PLanning extensions) 32

33 ADQ Implementation Example (PLX) PLX Planning EXtensions Web Application supporting the execution of the AIS data process: Data Collection: Internal\Extrenal Originator Interface Process Management Process Definition (WMS\TMS) Process Execution (Full integration with IAS) Process Tracking and Auditing Data Distribution Allows to distribute data via web, both in tabular and geographical format (Web GIS, Web Services) 33

34 Data Collection According to the type of data Originator and to the type of data different interfaces can be provided. So the system provides: Web Interfaces, for collecting structured data from external originators. Integration with the project workspace and project tools for collecting structured data from internal originators Attachment support for the collection of unstructured data (PDF, DGN, XLS, DOC, XML, ) 34

35 Data Collection PLX guides data originators in entering structured and unstructured aeronautical data 35

36 Data come from generic data sources (Ex. AeroDB Snapshot) Data integrity is mantained via CRC check 36 Change Requests on the effective reference data can be done

37 Process Management PLX allows to manage the whole AIS Process, from definition to execution. Process Definition: the system supports both Task and Workflow management. It is possible to implement different processes for different types of data. Process Execution: the system takes care of assigning tasks to an operator or a team. Integration with IAS allows to execute tasks using the right tool. Process Tracking: the system tracks all operations performed by the actors, including comments and messages. Search interfaces are provided for analysis and reporting 37

38 Workflow Definition Graphical Workflow Definition 38

39 Auditing A detailed log of all the actions performed on the Raw Data Package is provided 39

40 Data Distribution PLX provides an interface for Web publication of Aeronautical Data in both tabular and geographical format (Web GIS, WMS, WFS) 40

41 Questions? 06/05/2013 AeroSig 2012: AIS/AIM Breakout session 41

42 26-27 April 42

43 26-27 April 43

44 Initial Assessment Necessary to know the starting point Will provide a report outlining where the complaince is achieved and where the work is needed Will provide necessary input for the planning of the activities 44

45 Impact Assessment IDS will provide a specific impact assessment on the resources, process and solution to be updated. IDS will provide the suggested approach to solution upgrade: Change requests to current products Different Configuration of the same products Acquisition of new products IDS will provide suggested workflow from the data origination to the data distribution 45

46 Solution provision Delivery ot the solution required based on Commercial offthe-shelf Configuration of the products Design & implementation of: Workflows Business Rules Reports Production rules (charting, publishing, digital i/o) Etc etc 46

47 Validation and Verification The ADQ regulation requires that any tool used that may impact data quality are formally validated and verified IDS will provide support to define the documentation to deliver and the right approach to reduce the costs of its maintenance IDS will provide the required documentation to demonstrate the compliancy with related regulation 47

48 Training and Awareness IDS will perform specific workshops to establish the correct awareness in all the department of your organization Specific Training session will be executed to train the employees On the Job Training for the first cycle of implementation IDS will be available to provide training and presentation on your behalf (in case of external data originators) 48

49 Net Centric approach based on SOA Notam Configuration FPL FPL Briefing Task Managment Met Manager AMHS/AFTN ETOD Data Originator Profiling Workflow Managment MET User Authorization AERODB Web Feature Services NOTAM Web user/ Worksation SOA/ESB Auditing Messaging Doc. repository EAD DATA 49

50 IDS AIM Service Oriented Architecture Data Users Data Originators ESI EAD AMHS AFTN Airlines, pilots,... Airports, military,... AIS Operators Designers Communication services AeroEAD NOTAM Exchange NOTAM Web Interface HTTP PLX Web Interface IAS Workstations Design Workstations WFS WMS WCS LDAP NOTAM Store AeroDB Aero Catalog Centralized AIS database Centralized AIM Database Web Services Catalog Common Services (access, workflow, logginig, ) Common services External Systems 50

51 Interoperability Interface Data Technical Details AFTN Notam, MET, Flight Plans RS232, TCP/IP, X.25, Telex, TTY, AMHS Notam, MET, Flight Plans X.400 P2 IPM over P1, P3, P7 over TCP/IP or OSI SADIS MET FTP over TCP/IP Web Feature Service (WFS) AIXM 5.1 OGC WFS 1.0.0, EAD SDO,PAMS,INO ESI Web Map Service (WMS) Images OGC WMS LDAP User data RFC2307 SNMP System Configuration 51

52 Service Oriented Architecture Provided Services Aeronautical Data AIXM5 via WFS Aeronautical Charts JPG/PNG/ via WMS Aeronautical Info eaip in HTML via HTTP Portrayal WPS Aeronautical Messaging 52

53 Main Standards ICAO Annex 3 Meteorological Services Annex 10 Aeronautical Telecommunications Doc 4444 Rules of the Air and Air Traffic Services Doc 8126 AIS Manual Doc 8896 Manual of Aeronautical Meterorological Services Doc Manual of Technical Provisions for the ATN WMO Doc 386 Manual of the Global Telecommunications System Eurocontrol IFPS/CFMU TACT Manual AIS Data Processes (ADP) Static Data Procedures (SDP) ADEXP OPAD EU Regulations EC 73/2010 (ADQ) EC 552/2004 AIXM version 4.5 version 5.1 OGC Web Feature Server (WFS) Web Map Server (WMS) 53

54 Deployment Configuration Network Switches Web-Servers AIM Central Equipment Rack AFTN over RS232 or TCP/IP AFTN System AFTN or AMHS RS232 or TCP/IP AMHS System System Admin Console Application Servers System Administrator NOTAM Office MET Office Flight Planning Office Briefing Office Web Clients Internet Remote Access Network Security Device Database Servers Redundant LAN/WAN System Administrator AIP Office Design Office Obstacle Office EM Analysis Office Workstations 54

55 GIS Charting Live connection to data and GIS Capabilities Spatial and Temporal database connector Aeronautical Chart management : Management and maintenance of the ICAO Annex 4 Charts Estimation for future changes detected for each chart. Visual and tabular chart impact for data changes. Flexibility: Capability to produce a chart starting from a well-defined set of rules Complex Chart Labelling: Complex Label Definition starting from predefined templates Automatic Label Deconflicting Label Cleaning Complex Chart Layout: Capability to define and manage dynamic chart Layout. WYSIWYG rendering engine 55

56 AIXM 5.1 An exhaustive temporality model, including support for the temporary information contained in NOTAM Alignment with ISO standards for geospatial information, including the use of the Geography Markup Language (GML) Support for the latest ICAO and user requirements for aeronautical data including obstacles, terminal procedures and airport mapping databases Modularity and extensibility to support current and future aeronautical information messaging requirements and additional data requirements 56

57 Planning extensions PLX is the solution proposed by IDS to assess the AIM Data Process Management. PLX is designed to fit requirements coming from international regulation and standards, such as: RTCA 200A Eurocontrol - ADQ, CHAIN, SDP ICAO Annex 15, Doc 8126 (AIS Manual) Web Application supporting the execution of the Whole AIS data process: Data Collecting: Interface for Internal\External Originators of Aeronautical Data Process Management Process Definition (WMS\TMS) Process Execution (Full integration with AIM Solution) Process Tracking and Auditing Data Distribution Allows to distribute data via web, both in tabular and geographical format (Web GIS WMS/WFS) 57

58 Airspace Designer AD is the solution proposed by IDS to design and maintain bounded airspaces and routes according to ICAO annex 11 and doc AD is fully capable of performing vertical and horizontal separation between routes/airspaces, routes/routes and airspaces/airspaces: Fully configurable buffers (horizontal and vertical planes) Separation analysis done by airspaces structures types (P R D only, ATS only, etc..) Airspaces geometries data storage Special Use Airpaces (SUA) capabilities (corridors, sectors, etc...) Usage management and Flexible Use of Airspaces (FUA) Collaborative Design (CDM) capabilities The definition of airspaces is typically done by designers by experience using different and not fully operable systems. AD allows: Data loading: Load data from the central AIS or from external databases Assess and tracking etod assessment Volumes analysis (airspaces and routes) with configurable buffers MEA/MEL, MOCA, lower/ upper limit calculation and tracking Data Distribution Automatic AIP look-like reports Data storage in AIXM4.5 and 5.1 databases 58

59 etod Suite etod is the key factor for a real data quality checks to comply with ICAO annex 15 and doc 9881 etod is fully capable of validating obstacle/terrain data by: Merging human made obstacles data and compare them with the terrain information Import several terrain formats withouit any manual entry Import several (also user defined) human made obstacle formats) based on ASCII and xml Check Annex 15 requirements Export the obstacle data in different formats (aixm; 5.1, CSV, etc) Storage in a dedicated database or in the central AIS database The data collection and validation is the first step toward a complete ADQ implementation. etod allows: Data loading: Import in a controlled way obstacles and airport data and validate with terrain information and annex 15 requirements assessment Annex 4 and 14 surfaces geometries data storage Penetrating obstacle /terrain data storage Data Distribution AIXM 5.1 output, data sorage in central database 59

60 EMACS EMACS is the solution proposed by IDS to evaluate the performances of all the navigation aids and to prevalidate (ground validation) flight procedure and/or airspaces. EMACS is fully capable of performing the following operational evaluations: BRA (Building Restricted Areas) evaluation according to the ICAO EUR Doc 015 Generation of navigation aids coverage volumes Generation of usability volumes (limitations) by evaluating multipath effecting the navaids themselves (obstacle assessement) Distribution of the coverage/usability volumes to the designers by storing the information into the AIXM 5.1 Database Validation of the navaids signal in space and evaluation of the obstacle vs antenna safeguarding areas is typically done using different and not fully operable systems. EMACS allows: Data loading: Load data from the central AIS or from external databases Obstacle safeguarding and Radiolectric coverage evaluation Building Restricted Areas evaluation Volumes analysis (navigation aids coverage evaluation at several FL) Navaids Coverage Volume (navaids limitations included) generation Data Distribution Data storage in AIXM 5.1 databases 60

61 A solution to: IDS Improve the quality Improve the efficency Reduce the costs Increase the Business 61