1 / 16

EAD AIXM 5.1 Implementation

EAD AIXM 5.1 Implementation. Razvan Guleac DNM/COO/NOM/ADM. AIXM 5.1 Seminar. PLANNING. EAD Evolution. One release every 12 Months Client involvement during definition & assessment Dedicated workshops depending on release content Extensions to a release

gypsy
Download Presentation

EAD AIXM 5.1 Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EAD AIXM 5.1 Implementation Razvan Guleac DNM/COO/NOM/ADM AIXM 5.1 Seminar

  2. PLANNING EAD AIXM 5.1 Implementation

  3. EAD Evolution • One release every 12 Months • Client involvement during definition & assessment • Dedicated workshops depending on release content • Extensions to a release • Necessity to react to the needs of the EAD clients • On dedicated topics • No impact on existing MyEAD/ESI API • Between release – every 6 months • Patches • Maximum one per month • Bug fixing EAD AIXM 5.1 Implementation

  4. End of April /Beginning of May Release 6 m 12 months EAD Development Process Regulatory Operational Evolution TF members SSG Members DOP, ITP Subsystems Etc. EUROCONTROL ICAO SES Etc. Web Tool – EAD CHM Tool Release End of October/Beginning of November Extension Test Test Test Test Acceptance Acceptance EAD AIXM 5.1 Implementation

  5. EAD Change Management Tool EAD AIXM 5.1 Implementation

  6. EAD CHM – 814 – Route Package Download in AIXM 5.1 EAD AIXM 5.1 Implementation

  7. Future Implementation Milestones • AIXM 5.1 • Digital NOTAM • ICAO 2012 Flight Plan EAD AIXM 5.1 Implementation

  8. AIXM 5.1 Implementation (1) Analysis, Specifications,Development, Testing AIXM 5.1 Obstacles UploadDigital NOTAM Increment 1 Min SDODownload 6 months ObstaclesUpload / Download Min SDODownload DigitalNOTAM Increment 1 AIXM 5.1decoupling EADPre-Ops Min SDODownload EADProduction R6E1 R7 R6 MAR 2011 NOV 2011 APR 2012 EAD AIXM 5.1 Implementation

  9. AIXM 5.1 Implementation (post R7) ADQ Support: Upload – ADQ scope (AIP, Charting, eTOD) Digital NOTAM upload & visualisation … R8 R8E1 R7E1 NOV 2012 MAY 2013 NOV 2013 EAD AIXM 5.1 Implementation

  10. SDO 5.1 Architecture EAD AIXM 5.1 Implementation

  11. System Architecture AIMSL WS AIMSL WFS AIMSL WMS AIP SDDO CORE CHP AIXM 4.5 DP - ESI AIP I/F AIMSL I/F AIXM 4.5 -> AIXM 5.1 Mapping 4.5 ESI I/F CHP I/F INO-DU SDDO Business Logic and AIXM 5.1 Database 5.1 AIXM 5.1 DP - ESI INO-DU I/F HMI I/F INO-DP I/F Digital N. I/F AIXM 5.1 DP - HMI INO-DP (current) AIXM 5.1 Download Digital NOTAM AIXM 5.1 -> CACD Mapping AIXM 5.1 -> ARINC Mapping AIXM 5.1 -> INSPIRE Mapping AIXM 5.1 -> AIXM 4.5 Mapping CFMU CACD ARINC Data User INSPIRE Data User AIXM 4.5 Data User AIXM 5.1 Data User EAD AIXM 5.1 Implementation

  12. Data Maintenance Principles • Data maintenance is done only in the appropriate system. This means that AIXM 4.5 data is handled in SDO (4.5) while AIXM 5.1 data is handled in SDO (5.1). This includes the HMI as well as uploads via ESI and IFS. • The synchronisation is done via dedicated system interfaces between SDO (4.5) and SDO (5.1); backwards download (5.1 -> 4.5) shall be limited, e.g. ad-hoc SNAPSHOT • Minor updates in the SDO (4.5) system to enable data model compatibility: new business rules, new DHOs • It is not possible to have mixed slots, the slot-handling for 4.5 slots is done in SDO (4.5) while the equivalent handling for the 5.1 slots is done in SDO (5.1). Slot-operations are therefore only possible in the system where the slot has been created originally. • The mapping shall be robust enough not to lead to any error in the counterpart system (mapping & business rules). EAD AIXM 5.1 Implementation

  13. AIXM 5.1 Business Rules EAD AIXM 5.1 Implementation

  14. EAD AIXM 5.1 Business Rules • Based on the AIXM 5.1 Business Rules • Will be transposed into EAD AIXM 5.1 Business Rules • Using SBVR - Semantics of Business Vocabulary and Business Rules • Will be developed progressively with the implementation of the upload packages (i.e. starting with Release 7 – May 2012) • Will contain both Static Data rules and Digital NOTAM Event Specification Rules EAD AIXM 5.1 Implementation

  15. EAD AIXM 5.1 Implementation

  16. EAD AIXM 5.1 Implementation

More Related