EAD Towards ADQ Compliance

Transcription

1 EAD Towards ADQ Compliance EC Workshop ADQ Eurocontrol HQ, Brussels, Belgium, 23 rd, June 2014 EUROCONTROL NMD/NS/EAIM

2 Content EAD ADQ IR (EC) 73/2010 Compliance Steps ADQ Assessment (Gap Analysis) Required Steps/Activities Data Set and Data Exchange Requirements EAD Release 9 META Data Storage AIXM 5.1 output EAD ADQ Workflow Management Tool Customer Support ADQ Annotation EAD Release 10 AIXM 5.1 Input Backward Compatibility AIXM Customer Support CRC32 EAD Service/Function Certification Conclusion Additional Information for those interested

3 EAD ADQ Assessment (Gap Analysis) Commission Regulation ADQ (EC) 73/2010 requires those involved in the provision of aeronautical data/information to comply with a series of requirements intended to assure data quality. The EAD is a key element of many ANSPs AIS systems and will therefore need to be taken into account by those ANSPs when assessing their compliance with Commission Regulation (EU) 73/2010. EUROCONTROL therefore undertook to assess the EAD by an external company (Mileridge report 2012) in regards to Commission Regulation (EU) 73/2010.

4 EAD ADQ Assessment (Main Findings) The overall level of conformity is very high: The processes established are considered highly mature and well applied; This results from the manner in which the EAD is managed, such that the stakeholder is included in the process; Some work is needed for the EAD System. The main issues are: Data Set (including metadata); Data Exchange; Data Protection. The service provision is considered to need very little refinement to achieve full compliance.

5 EAD Steps towards ADQ Compliance (1) EUROCONTROL has scheduled a number of activities that address these issues and provide a path towards compliance with the Regulation. ADQ training; Address identified gaps and undergo safety assessment; Provision of a Declaration of Suitability for Use or Declaration of Conformity; Meeting ADQ Data Storage and Data Entry requirements. ADQ requirements for metadata: addressed within the scope of EAD Release 9 development. EAD Release 9 activities: completed according to the defined processes including Change Management (for the release content definition). EAD Safety Case: updated. The goal is to be able to issue an EAD System Statement of Compliance after EAD Release 9 goes into production.

6 EAD Steps towards ADQ Compliance (2) EAD ADQ Phase 1 (Release 9) will cover Requirements engineering Specification Design Implementation Unit test Integration test System test Assessment and verification Full traceability from requirement to test result Software traceability from identified and documented error to requirement implementation is ongoing Full ED153 / SWAL3 compliance of the EAD software development process

7 Data Set and Data Exchange Requirements EAD plans to meet the data set / data exchange requirements in two phases. Phase 1: Capability to output data in AIXM 5.1 format as well as AIXM 4.5, covering the existing data scope of the EAD Static Data Operations (SDO) subsystem. Included as part of EAD Release 9, to be available by end October Phase 2: Upload of data in AIXM 5.1 format; upload and download of additional data defined by this format. Part of EAD Release10 planned for October 2015.

8 EAD ADQ Phase 1 Release 9 (High Level) Step 1: Oct/Nov 2014 Metadata Input (ECIT and ESI) Metadata elements required for ADQ Using AIXM 5.1 metadata schema Output of Static data in AIXM 5.1 format Based on AIXM 4.5 -> 5.1 mapping Covering existing SDO data scope only Support of the seamless data chain by EAD Workflow Management Tool Support of the ADQ annotation in the SDC tool (June 2014) Dedicated data model in UML for Chart

9 Safety Briefing Content for Release 9 Changes to the EAD as a constituent to EATMN Safety Argument Safety Change Process Safety Hazards Change Requests of Release 9 Safety - Pre-classification Safety Assessment Models Planned and Ongoing FHA Report PSSA Report SSA Report Detailed analysis on performance Workshop EAD Release 9 Stakeholder Safety Briefing (done) Safety Case

10 SDC ADQ Annotation Phase 1 (Input) - Factory Acceptance Review log information from SDC installation on FAT system Testcase execution Free tests Successful assessment end of April 2014 Data entry available for all EAD clients since beginning of June 2014 Phase 2 (Export) Requirement for ADQ Annotation Export Format of export Integration into SDC Application Milestones

11 ADQ Phase 2 (Release 10): Direct Stakeholder Support A facility allowing upload of static data in AIXM 5.1 format must be provided (request of stakeholders to keep the ESI clients); AIXM 5.1 data being uploaded must be validated to the fullest extent possible; The existing Static Data Operations (SDO) subsystem must be continued, to support the clients who will continue to provide data in AIXM 4.5 format (transition period); EAD must be able to continue cross-border validation and the consistency checking of data provided by different states. Therefore a means must be provided to compare data provided in different formats (backwards compatibility); If necessary, EAD subsystems (Charting, AIP, etc) that use static data from SDO must be able to input AIXM 5.1 data, since this will be the only complete (and ADQ compliant) data set available from those states with AIXM 5.1 systems.

12 Release 10 & ADQ issues Cyclic Redundancy Check (CRC32) Requested by IR 73/2010 Discussed last summer / autumn Final decision December 2013 Too late for Release 9 EAD already assures data integrity through digital signatures ESI: digital signature is a MD5 checksum encrypted with private Key of sender AIMSL: digital signature is a SHA1 checksum of the canonicalised (normalised and thus comparable) XML payload; encrypted with Public Key of sender (WS-Security compliant). Conclusion: EAD will investigate application of CRC32Q for data exchange in R10 Such a development will bring no additional value in terms of integrity and security

13 EAD Service/Function Certification SSC#53 decision to create a TF in order to clarify the legal framework for EAD (NM IR 667/2010 or pan European AIS Provider IR (EC)1035/2011) Mitigation measures: Declaration of Conformity (DoC) Declaration for Suitability (DoS per Subsystem) Safety Briefing Documentation Tests: FAT July 2014 (R9) SAT August 2014 (R9)

14 Conclusion We have addressed ADQ in very condensed manner and defined and implement the steps required towards EAD ADQ Compliance, based on an assessment (gap analysis) performed by an external company. We support our customers with the ADQ Annotation and close the gap between the data originators and data providers with the Workflow Management Tool. We support our customers with the conversion of AIXM4.5 data to AIXM5.1 and allow a smooth transition (backward compatibility). We will assure full compliance of the EAD and our customers (states) to become fully ADQ compliant in a step approach with EAD Release 10. To achieve this takes an enormous amount of effort in time and money and requires all resource to focus on this

15 Additional Information

16 EAD R9 Enabling AIS Client sides Decoupling Performance improvements Stability improvements SDO INO DP INO DU INO BF LightSpeed (LUCIAD) for graphical display Reporting with EAD WorkFlowManagement Tool ADQ Annotation Keeping the pace of the evolution of the technology Java Browser support Weblogic DNS

17 EAD Workflow Management Tool (The Main Building Blocks) Roles Responsible for data provision (identification of changes) Responsible for data origination, surveyor Responsible for approval for publication AIS, CAA/NSA, etc. EAD workflows Data origination SDO update CHART update AIP update PAMS publication Metadata associated to each EAD workflow activities

18 ADQ Data Set and Data Exchange Requirements For Release 10 Data Entry in AIXM 5.1 format (B2B) Download of additional AIXM 5.1 features (beyond AIXM 4.5 scope) Cyclic Redundancy Check (CRC32)

19 Glossary EAD = European AIS Data Bank AIXM = Aeronautical Information Exchange Model ED153/SWAL3 = Software Assurance Level Metadata = Metadata assists in resource discovery by "allowing resources to be found by relevant criteria, identifying resources, bringing similar resources together, distinguishing dissimilar resources, and giving location information." SDO = Static data Operation SDC = Static Data Completeness (tool) ADQ Annotation = Customer tool to reflect status of ADQ implementation FHA = Functional Hazard Assessment PSSA = Preliminary System Safety Assessments SSA = System Safety Assessment UML = Unified Modeling Language (A logical information model format using XML Schema technology). INO = International NOTAM Operation PAMS = Published AIP Management System for Data Users Workflow Management Tool = Internet Application which closes the gap between data originator and data providers (AIS)