1 Hans Koolen NMOC/CFMU Network Operations Services A-CDM – Integration of Airport into the Network Implementation Steps & StatusEdition June 2012Hans Koolen NMOC/CFMU Network Operations Services
2 Purpose of presentation IntroductionPurpose of presentationTo describe which implementation steps are applicable for Integrating a CDM airport into the Network via DPI and FUM messages.To provide the latest available planning informationTarget AudienceManagementAirport CDM Project TeamAll others who would like to have a global overview of the planning
3 AGENDAIntroductionDPI/FUM Implementation StepsLast available planning info
4 Airport CDM Integration Plan A-CDM is implemented in phasesIt is a Cooperation between:At the airport: AO, handler, Airport, ATC/TWREUROCONTROL: Airport CDM-team, NMOC/CFMUThe process requires:Clear roles & responsibilities of EUROCONTROLIdentification of clear & transparent criteriaThe process has been defined together by APT and NMOC/CFMU
5 DPI/FUM Implementation Procedure DecisionGapAnalysisCompletenessAssessmentElements (1-5)CBADPI MessageGoNoDecision NMOC/CFMUOperationalEvaluationNot Ready AdviceAirport Interestin Airport CDMInformationMore AnalysisOperational DPITransmission toNMOC/CFMUPhaseDPI OperationalEvaluation PhaseDPI Element ** The technical support for the DPI element can be implemented either in parallel with elements15 or after their completionLocal AirportCDM OperatingStatus CDMAirport
6 Five A-CDM Implementation Phases Information PhaseNMOC/CFMU provides general info about DPI/FUM and NMOC/CFMU’s role in the A-CDM projectAnalysis PhaseNMOC/CFMU does not actively participate but is ready to answer to questions if necessary.Implementation PhaseNMOC/CFMU provides DPI implementation detailsNMOC/CFMU and Airport CDM Project team draft DPI-ICDAirport CDM platform software is updated with DPI/FUM processingNMOC/CFMU and Airport CDM Project team agree planning of the DPI Operational Evaluation PhaseDPI Operational Evaluation PhaseBefore start: Evaluate CDM Completeness CriteriaEvaluate DPI messagesPut DPIs into operations
7 CDM Implementation Phases (1/3) Information PhaseInformation CollectionAirport is interested in A-CDMDecision to analyse the optionsGap AnalysisCBADecision to Implement A-CDMAnalysis PhaseMainly Airport CDM Activities – NMOC/CFMU provides information
8 CDM Implementation Phases (2/3) Decision to implement Airport CDMImplement CDM Elements 1 to 5Implement FUM(local) CDM in OperationsImplement DPICDM Completeness AssessmentNot yet ReadyReadyDecision to start DPI transmission to NMOC/CFMUImplementation PhaseActivity managed by Airport CDM with support from NMOC/CFMU
9 DPI Implementation Steps First Information ExchangeDevelopment of the DPI-ICDFUM used by A-CDMValidation of Local Data accuracy and TimelinesDPI Operational EvaluationCommunication and Message SyntaxEvaluation of Live DataATFCM Impact AssessmentOperational TrialDPIs Fully operational
10 DPI Implementation Steps First Information ExchangeDevelopment of DPI-ICDValidation of Local Data Accuracy and TimelinesFUM used by A-CDMDPI Operational EvaluationDPIs Operational at NMOC/CFMU
11 First Information Exchange PurposeNMOC/CFMU provides Global Overview of DPI/FUM messages.Airport provides overview of the A-CDM project.First contact between the A-CDM project team and the NMOC/CFMU team.WhenAfter the A-CDM project has been approvedThe A-CDM project wants to include DPI/FUM into the project planningDuration1 day meetingRequired participantsA-CDM project team (preferably a representative of each stakeholder such as Airport, ATC-TWR ATC-FMP, AO,…)NMOC/CFMU staff
12 Development of the DPI-ICD PurposeNMOC/CFMU provides DPI messages implementation details.NMOC/CFMU provides detailed presentation on the DPI Operational Evaluation process.NMOC/CFMU and A-CDM project team start drafting the DPI-ICD.WhenWhen the A-CDM project is approaching the implementation phase.Before the A-CDM software requirements for the DPI messages are written.DurationStart with a 1-2 day meetingFinalisation of the DPI-ICD is estimated to take 1-2 monthsRequired participantsA-CDM project team, especially TWR OPS staff, FMP representative, Software Requirements Specialist.NMOC/CFMU staff
13 Required participants FUM used by A-CDMPurposeNMOC/CFMU will provide FUM on request.The A-CDM team can send request to NMOC/CFMU.WhenAfter the A-CDM info sharing platform is ready to receive the FUM.DurationProvision of FUM can be arranged on short notice.Required participantsA-CDM project Mgr.ODSG representative of ANSP concerned.
14 Validation of Local Data Accuracy and Timelines PurposeTo assess accuracy of CDM Data ProvisionTo prevent unnecessary long DPI Operational EvaluationSee “CDM Completeness Criteria” in Airport CDM Manual.WhenAfter A-CDM has been put into operations.Before DPI Operational Evaluation is started.DurationEstimated duration: 1 week – 1 month.Required participantsA-CDM project team to asses the Criteria.EUROCONTROL CND Airport team to discuss the Criteria.
15 CDM Completeness Criteria (1/2) Implement 5 Airport CDM Concept ElementsAirport CDM Information SharingAirport CDM Turn-around process – Miles Stones ApproachVariable Taxi-Time (VTT) CalculationCollaborative Pre-Departure Sequence (TSAT)CDM in Adverse conditionsInclusion of the following major events in the CDM processVerification of the flight plan with the airport slotEstablishment of the TOBTIssue of the TSATActual Off-BlockAdherence to Operational ProceduresCDM procedures documented in AIP and Airport Operating InstructionsSee Airport CDM Implementation Manual – Attachment 6
16 CDM Completeness Criteria (2/2) Accuracy & Coverage of the provided dataDPIs received for at least 97% of the flightsAccuracy of TTOT based upon TOBT <= 12minAccuracy of TTOT based upon TSAT <= 10minAccuracy of TTOT based upon AOBT <= 5minThe accuracy of the provided TOTs must be for 95% of the flights during normal circumstancesAdherence to ATFM SlotsMust be 80% or better during the last month before the CDM Completeness AssessmentAgreementsMoU signed by all partners at the airportDPI-ICD with NMOC/CFMU agreedLoA with NMOC/CFMU ready
17 DPI Operational Evaluation PurposeTo evaluate completeness and accuracy of DPI messages.See “DPI & FUM Implementation Roadmap” for details.WhenAfter local A-CDM has been put into operations.Before DPI messages are put into operations in NMOC/CFMU.DurationEstimated duration: 3-6 months.Required participantsA-CDM project (OPS and ENG expertise).NMOC/CFMU (URB and OPS expertise).
18 CDM Implementation Phases (3/3) Decision to start DPI transmission to NMOC/CFMUDPI Operational Evaluation PhaseSystem & Operations ImprovementsDPI Operational EvaluationNot yet ReadyReadyOperationsActivity managed by NMOC/CFMU
19 Required participants DPI in OperationsPurposeTo do the last preparations (admin).To put DPIs into operations (at NMOC/CFMU).WhenAfter successful DPI Operational EvaluationDurationEstimated duration: 1 month.Required participantsA-CDM project team.NMOC/CFMU.
20 DPI Implementation Steps First Information ExchangeDevelopment of DPI-ICDValidation of Local Data Accuracy and TimelinesFUM used by A-CDMDPI Operational EvaluationDPIs Operational at NMOC/CFMU
21 DPI Operational Evaluation – Major Steps Communication and Message SyntaxEvaluation of Live DataATFCM Impact AssessmentOperational TrialOperationsPost Operations Support
22 Operational Evaluation Phases 1. Communication and Message SyntaxPurpose: Initial and quick verification of message syntax and connections in order to save time during testing with live data.How: transmission of copies of several DPI message types via and via AFTN.How Long: one or several s and a few messages via AFTN.Report: feedback is given by NMOC/CFMU via .
23 Operational Evaluation Phases 2. Evaluation of Live DataPurpose: Determine accuracy and consistency of Live Data and suitability for ATFCM purposes.How: transmission of DPIs for operational traffic to the ETFMS OPS evaluation (test) system.How Long: initially 1 hour, later 24hours to several days.Report: initial feedback is given by NMOC/CFMU via . Later statistics reports will be produced and discussed with the airport concerned.Note that this phase may take several months dependent on the results of the first evaluations. It is required to have at least one long duration test of 7-14 days.
24 Operational Evaluation Phases 3. ATFCM Impact AssessmentPurpose: Determine the impact of the provided DPIs on the ATCFM process managed by ETFMS.How: transmission of DPIs for operational traffic to the ETFMS OPS evaluation (test) system.How Long: at least 24 hours without interruption.Report: Analysis and reports will be done via the ETFMS standard HMI (count graphs, oplog query,..).
25 Operational Evaluation Phases 4. Operational TrialPurpose: to verify the correct working of DPI/FUM messages in a fully operational environment.How: transmission of DPIs for operational traffic to the ETFMS OPS system and FUMs to the airport OPS system.How Long: several hours on 2 different days.Report: Analysis and reports will be done via the ETFMS standard HMI (count graphs, oplog query,..) and via the airport CDM system.
26 Operational Evaluation Phases 5. Operations (prepare for…)Purpose: to organise a GoNoGo meeting and take the last actions for final operationsHow: Organise the meeting, do last actions.How Long: takes approximately 1 week.Report: Go or NoGo decision and completed action-list.
27 Operational Evaluation Phases 6. Post Operations SupportPurpose: to learn from operations and to iron-out last problemsHow: Closely monitor operations and ensure the availability of Operations Support.How Long: approximately 2 weeks close monitoring and after that normal operations support.Report: Incident reports and others.
29 DPI Operational Evaluation Criteria DPI Quality IndicatorsDPI Completeness; i.e. DPIs for almost all flightsDPI Update rate; i.e. sufficient nr of updates per flightDPI to Flight plan correlation; no DPIs for VFR/OAT flightsRejected/ignored DPIs; must be below 3%Filing time behaviour; must be as agreed in the ICD…DPI performance IndicatorsTOT predictability; must be better than flight plan predictability
33 Documentation (1/2) Airport CDM Manual Contains CDM Milestones approach and a general Description of DPI messagesRef: Edition 3.1, July 2010.NM/CFMU Flight Progress Messages DocumentContains DPI and FUM message syntax and semantics, general trigger eventsRef: URB/USD/MSG_INTF, version 1.900, dated 01/02/2012DPI Implementation GuideContains a details of DPI messages, including trigger events and processing by ETFMSRef: URB/USD/DPI_Impl_Guide, version 1.600, dated 01/02/2012
34 Documentation (2/2) FUM Implementation Guide Contains a details of FUM messages, including accuracy info and implementation guidelinesRef: URB/USD/FUM_Impl_Guide, version 1.200, dated 01/02/2012DPI & FUM Implementation Road MapContains description of steps for the DPI & FUM evaluation and Evaluation CriteriaRef: URB/USD/DPI_FUM_Impl_RM, version 1.400, dated 01/02/2012DPI ICDContains the Airport specific DPI interface with the actual implementation of the DPI contents and trigger events
35 Contacts Contacts: Hans Koolen, tel +32 2 729 9876 Ioana Coliban, tel
Your consent to our cookies if you continue to use this website.