This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
a) Scope of data to be provided; b) Accuracy, resolution and integrity; c) Method used to demonstrate data conformity with ADQ
requirements; d) Actions to be taken in case of data error and/or
inconsistency; e) Criteria for notification of data changes; f) Any limitations on the use of data; g) Metadata requirements; h) Contingency measures; i) Requirements for the production of quality reports by data
providers.
User Experiences: PLX AT ENAV
14 Commercial-in-Confidence
RECOMMENDATION: a) Identify all “ADQ data originators”; b) Sign a Formal Agreement with them; c) Define the area of responsibility of every single data
originator, in terms of data to be provided including every related DB features.
traceability; • Individual workflows for originators; • Statistical reports.
• PLX supports “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;
• 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
PLX SUPPORTING ADQ-IR
• PLX Support the following ADQ-IR Art.: • 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
• Customers will present PLX as the new SW application for Data transmission to AIS;
• Customers are introducing PLX in SLA with its Data Originators.
User Experiences: SUMMARY (Benefits & Open Points)
24/06/2014 20
AUSTROCONTROL – ENAV - PANSA
OPEN POINTS
• PLX web form still require manual inputs (coordinates, elevation, etc.);
• PLX web form are data centric (user-friendliness for originators not optimal);
• CRC requirement for upload/download not supported
• Not clear if all originators will accept PLX; • Improve Web Browser performance s.
• How to interface PLX with Databases and tool belonging to Originator;
• Extending the CHAIN with PLX also to others Originators ;
• Interface PLX with Military with a sincronized workflow from AIS MIL to AIS CIV;
• Land Use Assesment (workflow for new obstacles proposals);
• Baltic FAB coordination (Lithuania / Poland) digital data exchange;
• Digital Notam Implementation; • Integrated Web briefing .
IDS PROPOSAL
ACTIONS • 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)
User Experiences: SUMMARY (Benefits & Open Points)