IDS PLX Solution & ADQ
ADQ IMPLEMENTATION WORKSHOP
EUROCONTROL HQ
28-29 May -2013, Brussels
Simone Gabriele
Air Navigation Division,
Static and Dynamic Data Management - Product Manager
Via Flaminia, 1068 - 00189 Rome, Italy
Phone: +39 06 33217 468
E-mail: s.gabriele@idscorporation.com
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
2
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
 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
3
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
AIS / AIM Process and ADQ:
Quality, Workflow Traceability
AIS PROCESS GOALS
PROCESS INPUT:
RAW DATA - AIS is a provider of
Information, the vast majority of which is
not sourced from within the AIS. Therefore
that Raw Data is an input to the AIS
process
Receive / originate, collate or assemble,
edit, format, publish/store and distribute
aeronautical information /data […].
Aeronautical Information shall be published
as an Integrated Aeronautical Information
Package.”
[…] ensure that aeronautical
information/data […] is adequate, of
required quality;
PROCESS OUTPUT:
AERONAUTICAL PRODUCTS - ICAO Annex 15
identify the products that shall be provided
by AIS and may therefore be identified as
the outputs of the process. (AIP, AIC, SUP,
Charts, Digital Outputs, etc.)
AIS must timely provide the necessary
information, in the form required and
ensure its quality
Aeronautical Data Quality (ADQ): domain example
4
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
AIS / AIM process implementation at
an ANSP: ADQ requirements
DEFINE THE OWN PROCESS
• Eurocontrol specifications provide guidelines
• each national AIS has to define the process according to its providers, customers, internal structure
EXECUTE IT
• All the tasks defined inside the process must be executed by the right person, in the right time and using
the right tools
TRACK IT
• The whole process must be tracked and recorded on a Log Sheet for later reference
APPLICABLE REGULATIONS FOR DATA QUALITY
• 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
5
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
 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
7
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
IDS Solution
Digital Data
Translators
ICE
Design Dept.
Charting
Aerocatalog
AeroDB
Aeronautical Catalog
Originators
AeroPub
Publishing
Aeronautical Database
GFeaman
NOTAM
Validation
CRONOS
Collection
Analysis
Validation
PLX
08/04/2015
ICE - Demo
Publication
8
IDS Solution to the AIS Data Process
Management
The PLX web application supports the
whole lifecycle of the AIS Data Process
DATA
COLLECTION
PROCESS MANAGEMENT
DATA
DISTRIBUTION
Internal\Extrenal
Originator
Interfaces
Process Execution
(Full integration
with IAS),
concurrent
processing
Allows to distribute
data via web, both
in tabular and
geographical
format (Web GIS)
Process Definition
(WMS\TMS)
Process Tracking
and Auditing,
Information
Search and
Reporting
The system tracks all the operations performed by the actors, including comments ,
remarks and messages. Search interfaces are provided for analysis and reporting.
9
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
IDS Solution to the AIS Data Process
Management
All rights reserved to IDS
10
 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
11
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
PLX IMPLEMENTATION PROJECTS:
CASE HISTORY – PLX AT ENAV
 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, 716 - 00138 Roma - Italia
Tel. +39 06 81662051
Cell. +39 331 6231490
giulio.melilli@enav.it
www.enav.it
12
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
ENAV CASE HISTORY:
Implementation Timeline (1 of 3)
2010
2012
•AIRNAS 2010 - KICK
OFF - Goals:
integrated
management of
aeronautical data
and information at
ENAV – operational
department
•BUSINESS
PROCESS
ANALYSIS
•Workflow
design and
implementati
on
2013
APR-JUN
•testing
origination
2010-2011
2013-JAN
2013-JUL
•REQUIREMENTS
•IMPLEMENTATION
• WEB FORMS
•SWITCH TO
OPERATIONS
•parallel
processing with
traditional
system for next
1 year only
•Goals: user
fiendly forms, for
NON-AIS
originators
•Result: forms
recalling AIP
sections and
tables
All rights reserved to IDS
13
ENAV CASE HISTORY:
Operations (2 of 3)
All rights reserved to IDS
14
ENAV CASE HISTORY:
PLX configuration (3 of 3)
WORKFLOWS
WEB FORMS
• Dedicated Workflow for Data
Maintenance & Product
Generation
• IAS Applications involved
• Mapping AIP sections & tables
• Renaming Features & Attributes
as per AIP reference sections /
fields
• Data Entry Rules implemented
for error limitation
• Results:
• Integrated environment
• Less manual activities
introducing errors
• Controlled workflow
• Less confilicts of responsibility
when processing
• Results: AIP friendly Web Forms
for non-AIS Originations
• Less errors
• less effort in data process
PLX
CONFIGURATION
@ ENAV
All rights reserved to IDS
15
PLX IMPLEMENTATION PROJECTS:
CASE HISTORY – PLX AT AUSTROCONTROL
 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
www.austrocontrol.at
Telefon: +43(0) 51703 3281
Mobil: +43(0)664 964 8601
Fax: +43(0) 51703 2036
E-Mail: robert.wehofer@austrocontrol.at
16
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
AUSTROCONTROL CASE HISTORY:
Implementation Timeline (1 of 3)
2011
2010-MAR
•SWITCH TO
OPERATIONS
•First only in AIM to
document working
processes
2010-SEP
•KICK OFF
•part of Austrocontrol
“Data quality” project
•BUSINESS PROCESS
ANALYSIS
2010-JUN
2010-2011
•REQUIREMENTS
•IMPLEMENTATION
AND
CONFIGURATION
•WORKFLOW DESIGN
•TESTING
More and more originators will be integrated !
All rights reserved to IDS
17
AUSTROCONTROL CASE HISTORY:
Operations (2 of 3)
All rights reserved to IDS
18
AUSTROCONTROL CASE HISTORY:
PLX configuration (3 of 3)
WORKFLOWS
WEB FORMS
• Dedicated Workflow for
Data Maintenance &
Product Generation
• IAS Applications involved
• ...
• Dedicated Web Forms for
Originations
• Data Entry Rules
implemented
• ...
PLX Configuration
@
AUSTROCONTROL
All rights reserved to IDS
19
PLX IMPLEMENTATION PROJECTS:
BENEFITS & ADQ SUPPORT
AUSTROCONTROL
ENAV
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 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
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
20
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
PLX IMPLEMENTATION PROJECTS:
OPEN POINTS, ACTIONS
OPEN POINTS
AUSTROCONTROL
ENAV
• 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)
21
08/04/2015
AeroSig 2012: AIS/AIM Breakout session
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
All rights reserved to IDS
22
Questions?
23
08/04/2015
AeroSig 2012: AIS/AIM Breakout session