Presentation on theme: "Simone Gabriele Air Navigation Division, Static and Dynamic Data Management - Product Manager Via Flaminia, 1068 - 00189 Rome, Italy Phone: +39 06 33217."— Presentation transcript:
Simone Gabriele Air Navigation Division, Static and Dynamic Data Management - Product Manager Via Flaminia, Rome, Italy Phone: IDS PLX Solution & ADQ ADQ IMPLEMENTATION WORKSHOP EUROCONTROL HQ May -2013, Brussels
26/02/2014AeroSig 2012: AIS/AIM Breakout session 2 Outline AIS Data Process and ADQ: Workflow Traceability IDS AIS/AIM PLX: Overview Case history: PLX at ENAV and AUSTROCONTROL IDS PLX solution for ADQ compliancy
26/02/2014AeroSig 2012: AIS/AIM Breakout session 3 AIS DATA PROCESS AND ADQ: WORKFLOW TRACEABILITY IDS AIS/AIM PLX: Overview Case history: PLX at ENAV and AUSTROCONTROL IDS PLX solution for ADQ compliancy
26/02/2014AeroSig 2012: AIS/AIM Breakout session 4 AIS / AIM Process and ADQ: Quality, Workflow Traceability Aeronautical Data Quality (ADQ): domain example
26/02/2014AeroSig 2012: AIS/AIM Breakout session 5 AIS / AIM process implementation at an ANSP: ADQ requirements Eurocontrol specifications provide guidelines each national AIS has to define the process according to its providers, customers, internal structure DEFINE THE OWN PROCESS All the tasks defined inside the process must be executed by the right person, in the right time and using the right tools EXECUTE IT The whole process must be tracked and recorded on a Log Sheet for later reference TRACK IT Interoperability Regulation (552/2004) in the context of Single European Sky (SES) - objective: ensure the interoperability of the European ATM Network Aeronautical Data Quality Implementing Rule (ADQ IR) No 73/2010 requirements on the quality of aeronautical data & information APPLICABLE REGULATIONS FOR DATA QUALITY
All rights reserved to IDS 6 INITIAL CHECK Receive Evaluate Raw Data Process / Calculate Authorize / Approve PREPARE Store Choose Publication Method Select Assemble Translate Quality Check ISSUE Print Collate Final Quality Check Distribute Raw Data Products [Eurocontrol ADP - Chapters 3/4] AIS/AIM Process - outline
26/02/2014AeroSig 2012: AIS/AIM Breakout session 7 AIS Data Process and ADQ: Workflow Traceability IDS AIS/AIM PLX: OVERVIEW Case history: PLX at ENAV and AUSTROCONTROL IDS PLX solution for ADQ compliancy
26/02/2014AeroSig 2012: AIS/AIM Breakout session 9 IDS Solution to the AIS Data Process Management The PLX web application supports the whole lifecycle of the AIS Data Process DATA COLLECTION Internal\Extrenal Originator Interfaces PROCESS MANAGEMENT Process Definition (WMS\TMS) Process Execution (Full integration with IAS), concurrent processing Process Tracking and Auditing, Information Search and Reporting DATA DISTRIBUTION Allows to distribute data via web, both in tabular and geographical format (Web GIS) The system tracks all the operations performed by the actors, including comments, remarks and messages. Search interfaces are provided for analysis and reporting.
All rights reserved to IDS 10 IDS Solution to the AIS Data Process Management
26/02/2014AeroSig 2012: AIS/AIM Breakout session 11 AIS Data Process and ADQ: Workflow Traceability IDS AIS/AIM PLX: Overview CASE HISTORY: PLX AT ENAV AND AUSTROCONTROL IDS PLX solution for ADQ compliancy
26/02/2014AeroSig 2012: AIS/AIM Breakout session 12 Case History: PLX AT ENAV Reference / Point of Contact: Giulio Melilli Aeronautical Information Service Head of Aeronautical Data Management/Quality and Production Unit Enav S.p.A. Via Salaria, Roma - Italia Tel Cell PLX IMPLEMENTATION PROJECTS: CASE HISTORY – PLX AT ENAV
All rights reserved to IDS 13 ENAV CASE HISTORY: Implementation Timeline (1 of 3) 2010 AIRNAS KICK OFF - Goals: integrated management of aeronautical data and information at ENAV – operational department REQUIREMENTS IMPLEMENTATION 2012 BUSINESS PROCESS ANALYSIS Workflow design and implementati on 2013-JAN WEB FORMS Goals: user fiendly forms, for NON-AIS originators Result: forms recalling AIP sections and tables 2013 APR-JUN testing origination 2013-JUL SWITCH TO OPERATIONS parallel processing with traditional system for next 1 year only
All rights reserved to IDS 14 ENAV CASE HISTORY: Operations (2 of 3)
All rights reserved to IDS 15 ENAV CASE HISTORY: PLX configuration (3 of 3) PLX ENAV WORKFLOWS Dedicated Workflow for Data Maintenance & Product Generation IAS Applications involved Results: Integrated environment Less manual activities introducing errors Controlled workflow Less confilicts of responsibility when processing WEB FORMS Mapping AIP sections & tables Renaming Features & Attributes as per AIP reference sections / fields Data Entry Rules implemented for error limitation Results: AIP friendly Web Forms for non-AIS Originations Less errors less effort in data process
26/02/2014AeroSig 2012: AIS/AIM Breakout session 16 Case History: PLX AT AUSTROCONTROL Reference / Point of Contact: Robert Wehofer Aeronautical Information Management (AIM) Manager Static Data Management (SDM) Austro Control GmbH Towerstrasse, Objekt 120 A-1300 Flughafen Wien Telefon: +43(0) Mobil: +43(0) Fax: +43(0) PLX IMPLEMENTATION PROJECTS: CASE HISTORY – PLX AT AUSTROCONTROL
All rights reserved to IDS 17 AUSTROCONTROL CASE HISTORY: Implementation Timeline (1 of 3) 2010-MAR KICK OFF part of Austrocontrol Data quality project 2010-JUN REQUIREMENTS 2010-SEP BUSINESS PROCESS ANALYSIS IMPLEMENTATION AND CONFIGURATION WORKFLOW DESIGN TESTING 2011 SWITCH TO OPERATIONS First only in AIM to document working processes More and more originators will be integrated !
All rights reserved to IDS 18 AUSTROCONTROL CASE HISTORY: Operations (2 of 3)
All rights reserved to IDS 19 AUSTROCONTROL CASE HISTORY: PLX configuration (3 of 3) PLX AUSTROCONTROL WORKFLOWS Dedicated Workflow for Data Maintenance & Product Generation IAS Applications involved... WEB FORMS Dedicated Web Forms for Originations Data Entry Rules implemented...
26/02/2014AeroSig 2012: AIS/AIM Breakout session 20 PLX IMPLEMENTATION PROJECTS: BENEFITS & ADQ SUPPORT AUSTROCONTROLENAV BENEFITS Very flexible configuration management User configuration and profiling (roles/permissions) Internal AIS process implemented (full traceability) Individual workflows for originators AIM processes are transparent (traceability) Statistical reports Supports both structured and unstructured requests Simplified origination: dedicated data profiles (web forms) per Originator types (aerodrome operators, CAA, Air Force, etc); display and editing of selected data only - under specific responsibility – subject to data entry rules (for every field involved!) Extremely flexible configuration capability allowed the design of user friendly AIP like web forms for non-AIS personnel Internal AIS workflow fully implemented Traceability of aeronautical data process – from receipt to publication – granted SUPPORT ADQ COMPLIANCY PLX IS CONSIDERED AS ADQ TOOL; ADQ requirements fulfilled: Article 5(1) – direct electronic connection Article 6(2) – evidence requirements Article 6(5) – data process requirements Article 6(6) – error reporting Article 8 – Tools and software requirements (Article 9(1) – Data protection) Article 9(2) – Traceability maintenance Article 11 – EC declaration of suitability for use Formal arrangements with originators refer to PLX PLX SUPPORTS COMPLIANCY WITH EU REG. 73/2010 PLX is the new mean for aeronautical data origination and trasmission to AIS - overtakes the older way for data exchange ENAV is going to present the PLX as the new tool as for the trasmission of aeronautical data to AIS - as per requirements of EU Reg. 73/2010 PLX is being introduced in the Service Level Agreement which ENAV, as per EU Reg. 73/2010 is signing with all the Originators of Aeronautical Data
26/02/2014AeroSig 2012: AIS/AIM Breakout session 21 PLX IMPLEMENTATION PROJECTS: OPEN POINTS, ACTIONS AUSTROCONTROLENAV OPEN POINTS Austro Control only refers to unstructured requests (reason: Attached files support full automation in data chain) PLX web form require manual inputs (coordinates, elevation, etc.) PLX web form too data centric (therefore user-friendliness for originator not optimal) CRC requirement for upload/download not supported Not clear, if all originators will accept PLX PLX not well integrated in other IDS products (e.g. Airspace Designer) Extending the CHAIN with PLX up to the Originator tools How to interface PLX with Databases and tool belonging to Originator IDS, AUSTROCONTROL, ENAV ACTIONS IDS PROPOSED: improve originator usability & efficiency improve the automation in the flow of Structured Data – verify how to integrate PLX with originator tools limit further the manual data entry (e.g. import of originator files in PLX) Wider use of Geoserver capabilities verify where/when and how to grant better monitoring of Data Integrity (CRC check or other algorithms) improve the Web Forms with a close cooperation and dedicated mappings through ad hoc projects improve the integration of PLX in IDS applications (e.g. integrated PLX process in originator design phase)
All rights reserved to IDS 22 CONCLUSIONS PLX has been adopted for the Workflow Management and Traceability of the AIS process at two major european ANSPs Full configurability allowed to match the AIS goals by tailoring the system to local AIS needs dedicated web forms have been designed to simplify the Data Collection / Origination dedicated Workflows could be deployed to make more efficient the processing of any data The capability to store any action performed at workflow level (processing history) and at system level (transactions) supports the implementation of the ADQ requirements THE SYSTEM WILL BE FURTHER DEVELOPED TO IMPROVE ORIGINATION AND AUTOMATION