Brussels Airport, a roadmap to A-CDM implementation

Transcription

1 Brussels Airport, a roadmap to A-CDM implementation

2 BRU A-CDM: where did we start from? BRU A-CDM: how did we proceed? BRU A-CDM: how did we communicate? BRU A-CDM: implemented! What about customer care? BRU A-CDM: the way ahead BRU A-CDM: what we have experienced

3 Where did we start from? Brussels Central Database (CDB): a head start for data sharing through existing syst-to-syst links BRU CENTRAL DATABASE TOWER [User Interfaces] STAFF PAGES DGS

4 Where did we start from? As a result of CDB ops, a basic understanding of stakeholder ops by each airport partner Joint meetings: internal & external usergroups Bilateral meetings: set-up of data input procedures A basis for enhanced collaboration towards A-CDM implementation

5 How did we proceed? Installing dedicated task forces to analyse and map the inbound/turn around/outbound process Data coherency check INBOUND Local Radar Data Taxi In Matching the 16 milestones to the process map Each process delivering a best known time to the next ATOT Final Approach ALDT Minimum Turn Round Times will be in the CDM platform and can be updated TURN ROUND 11 Boarding ARDT ASRT Take Off from Outstation 7/8 AIBT AGHT /13 OUTBOUND 14 ASAT -2hrs ATFM Slot allocation TOBT Taxi Out -3hrs Flight Plan Submission TSAT AOBT ATOT

6 How did we proceed? Mapping scenarios to grasp the TOBT & DPI concept BSC AO GH IFPS CFMU E-DPI 1 ATC submits E-DPI to CFMU (at SOBT-2H) based upon SOBT and ACIS submits TOBT based upon IOBT = EOBT (at SOBT-2H) ATC ACIS TOBT = EOBT 2

7 How did we proceed? ACIS development: CDB (Central Database): defining the CDM information elements TMA (Terminal Management Application): set-up of CDM data tab Airport GH staff Staff Pages application: web based, easy-to-use, a/c operator based login Airport community Remote OCC s, Simultaneous developments in GH and ANSP systems

8 How did we proceed? What we kept in mind: Strict adherence to Eurocontrol functional requirements (terminology, acronyms ) A guideline to cover all aspects of the project A lead through difficult discussions A back up for CDM procedure adherence Currently the only book to go by for alignment between all A-CDM implementation initiatives (enabler buy-in from AO and a way to CDMsuccess)

9 TMA view How did we proceed?

10 Staff Pages View How did we proceed?

11 How did we proceed? The CDM alert mechanism: Developed out of existing CDB functionality (on line data quality checks) Notification by Started off as manual procedure, developing a fully automated mechanism

12 How did we proceed? strict project set-up setting realistic, best fit target dates progress follow-up through well-plotted meeting sequence! Steering group meetings: every 2 months Advisory group meetings: every 3 weeks ARR, turn around, DEP and TOBT taskforces : independent meeting schedule, progress reporting on AG meetings! Backward project planning by bottom-up feedback

13 How did we proceed? Opting for a sequenced start-up: June 15th 2010: start-up in local mode both GH, selected set of AO s involved testing ACIS and alert mechanism performance June 29th 2010: kick-off DPI transmission by Belgocontrol All airlines involved Support, adjust, communicate August 17th 2010: procedure adherence focus on TOBT/EOBT alignment

14 How did we proceed? Last but not least General Aviation ops

15 How did we communicate? Phased project introduction letters via and letter

16 How did we communicate? The Brussels info brochure

17 How did we communicate? Info sessions for the community, up to 6 in the month of July Staff briefings by GH and Belgocontrol The BRU info cards

18 Implemented! What about customer care? Monthly info sessions, still ongoing, incorporating use cases and actual operational scenarios Dedicated sessions for tough customers Close monitoring of, and feedback on ACIS performance & alert messaging. Set-up series of CDM core meeting

19 The way ahead How are we doing? Performance monitoring How do we stay tuned? Procedure adherence Discipline! What if Fallback procedures Ops in adverse weather conditions. CDM 2.0 kick-off with: de-icing process communication by GH airport operational status by BRU APOC-approach (establish reduced airport capa, communicate, coordinate corresponding scenarios) Sharing experiences to keep our different A-CDM set-ups aligned in the interest of the AO s

20 What we have experienced data sharing BUT also creating mutual process insights! believers at all stakeholders, at every organisation level seamless interaction of your local CDM-representatives between the project and their own organisational disciplines (IT, operations, commercial, legal ) good CFMU contacts make sure the dialogue stays open-minded at all times, whatever difficulties ahead speeding up implementation to a critical mass of A-CDM airports will speed up the network benefits for us all