Simone Gabriele Air Navigation Division, Static and Dynamic Data Management - Product Manager Via Flaminia, 1068 - 00189 Rome, Italy Phone: +39 06 33217.

Simone GabrieleAir Navigation Division,

Static and Dynamic Data Management - Product ManagerVia Flaminia, 1068 - 00189 Rome, Italy

Phone: +39 06 33217 468E-mail: [email protected]

IDS PLX Solution & ADQ

ADQ IMPLEMENTATION WORKSHOPEUROCONTROL HQ28-29 May -2013, Brussels

10/04/23 AeroSig 2012: AIS/AIM Breakout session2

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


AIS DATA PROCESS AND ADQ: WORKFLOW TRACEABILITY





AIS / AIM Process and ADQ: Quality, Workflow Traceability

Aeronautical Data Quality (ADQ): domain example


AIS / AIM process implementation at an ANSP: ADQ requirements



IDS AIS/AIM PLX: OVERVIEW



Charting

Originators

10/04/238

IDS Solution Digital Data

Aeronautical Catalog

Aeronautical Database

Translators

AeroDB

ICEDesign Dept.

ICE - Demo

Publishing

Aerocatalog

NOTAM

Validation

Approve

d

Reject

ed

CollectionCollection AnalysisAnalysis ValidationValidation PublicationPublication

PLX

AeroPub

CRONOS

GFeaman


IDS Solution to the AIS Data Process Management

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




CASE HISTORY: PLX AT ENAV AND AUSTROCONTROL



Case History: PLX AT ENAV

Reference / Point of Contact:

Giulio MelilliAeronautical Information ServiceHead of Aeronautical Data Management/Quality and Production Unit

Enav S.p.A.Via Salaria, 716 - 00138 Roma - ItaliaTel. +39 06 81662051Cell. +39 331 [email protected]

PLX IMPLEMENTATION PROJECTS:CASE HISTORY – PLX AT ENAV


ENAV CASE HISTORY:Implementation Timeline (1 of 3)


ENAV CASE HISTORY: Operations (2 of 3)


ENAV CASE HISTORY: PLX configuration (3 of 3)


Case History: PLX AT AUSTROCONTROL

Reference / Point of Contact:

Robert Wehofer Aeronautical Information Management (AIM)Manager Static Data Management (SDM)

Austro Control GmbHTowerstrasse, Objekt 120A-1300 Flughafen Wienwww.austrocontrol.atTelefon: +43(0) 51703 3281Mobil: +43(0)664 964 8601Fax: +43(0) 51703 2036E-Mail: [email protected]

PLX IMPLEMENTATION PROJECTS:CASE HISTORY – PLX AT

AUSTROCONTROL


AUSTROCONTROL CASE HISTORY:Implementation Timeline (1 of 3)

More and more originators will be integrated !


AUSTROCONTROL CASE HISTORY: Operations (2 of 3)


AUSTROCONTROL CASE HISTORY: PLX configuration (3 of 3)


PLX IMPLEMENTATION PROJECTS:BENEFITS & ADQ SUPPORT

AUSTROCONTROL ENAVBENEFITS • 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


PLX IMPLEMENTATION PROJECTS:OPEN POINTS, ACTIONS

AUSTROCONTROL ENAV

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, ENAVACTIONS 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)


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


Questions?

Simone Gabriele Air Navigation Division, Static and Dynamic Data Management - Product Manager Via Flaminia, 1068 - 00189 Rome, Italy Phone: +39 06 33217.

Documents

aisaim process

raw data process

data quality slide

outline ais data process

enav slide

case history plx

austrocontrol ids plx

plx configuration