MULTI-NODAL ATFM COMMON OPERATING PROCEDURES (COP)

Transcription

1 MULTI-NODAL This document provides an essential framework, details of procedures, rules and requirements applicable for Air Traffic Flow Management for Operational Trial. ATFM COMMON OPERATING PROCEDURES (COP) Effective 1 July 2016

2 Table of Content Document Change Record... 1 Document Administration... 2 Reference Material Introduction Network Concept Overview Operational Trial: A Phased Approach with Tiered Participation Multi-Nodal General Stakeholders Responsibilities Information on ATFM Measures Processes and Procedures for ATFM Measures Flight Plan and ATS Messages Exemption of Flights Compliance monitoring Performance assessment Failure of the ATFM system Safety Measure for the Operational Trial ATS Data Exchange Presentation (ADEXP) Messages Annex A Annex B Annex C Annex D Annex E

3 1 Document Change Record The following table records the complete history of the successive editions of the present document. Version Number Effective Date Reason for Change Pages Affected July 2016 Original release version All

4 2 Document Administration This document has been co-authored by members of the Distributed Multi-Nodal Air Traffic Flow Management (ATFM) project. Comprising members from the participating Air Navigation Service Providers (ANSPs) and relevant stakeholders, this document aims to document provide a framework, details of procedures, rules and requirements applicable for ATFM operations based on the Distributed Multi-Nodal ATFM concept. This document will continue to evolve as the project matures from the operational trial stages to the eventual implementation of ATFM. The following Air Navigation Service Providers (ANSPs) shall be jointly responsible for the administration and maintaining of this document: ANSPs Administrator Details Aeronautical Radio of Thailand (AREOTHAI) Civil Aviation Administration of China (CAAC) Civil Aviation Authority of Singapore (CAAS) Civil Aviation Department (CAD) of Hong Kong Tel: / / Fax: / atfmu@bobcat.aero ATFM Web Portal: Refer to alerts for web link AFTN Address: VTBBZDZX Tel: Fax: SANYAATFMU@GMAIL.COM / MULTINODAL@gmail.com ATFM Web Portal: (temporarily) AFTN Address: ZJSYZRZX (temporarily) Tel: Fax: caas_atfmu@caas.gov.sg ATFM Web Portal: AFTN Address: WSJCZQZX Tel: Fax: atmdflm@cad.gov.sg / hkatfmtrial@outlook.com ATFM Web Portal: Refer to alerts for web link AFTN Address: To be advised

5 3 Reference Material 1. Chapter 3 paragraph (Air Traffic Flow Management) of Annex 11 to the Chicago Convention Air Traffic Services (13th edition July 2001, incorporating amendment No 47) 2. Chapter 3 (ATS Capacity and Air Traffic Flow Management) of ICAO Doc 4444, Procedures for Air Navigation Services Air Traffic Management (PANS-ATM) (15th edition 2007) 3. ICAO Doc nd Ed Manual on Collaborative Air Traffic Flow management 4. ICAO Asia/Pacific Regional Air Traffic Flow Management Concept of Operations 5. ICAO Asia/Pacific Regional Framework for Collaborative Air Traffic Flow Management

6 4 DISTRIBUTED MULTI-NODAL ATFM (COP) 1 Introduction 1.1 The Asia Pacific region has experienced rapid increase in air traffic demand in the recent years with majority being cross-border flights within the region. While Air Navigation Service Providers (ANSPs) and airport operators are continuously exploring means to increase airspace and airport capacity to match the increasing demand, there is a need for a systematic method to balance demand and capacity in order to allow a sustainable growth in traffic demand in the near future. 1.2 Air Traffic Flow Management (ATFM) is a means to address demand and capacity imbalance. ATFM is a service established with the objective of contributing to a safe, orderly and expeditious flow of air traffic by ensuring that air traffic control capacity is utilized to the maximum extent possible, and that the traffic volume is compatible with the capacities declared by the ANSP. 1.3 Regulating air traffic flow through the application of ATFM measures such as Ground Delay Programs (GDP) is a known operational concept. This is typically carried out by a single entity within a region or independently applied within the domestic boundaries of an ANSP. However, there is an increasing need to apply ATFM measures to facilitate cross-border flight operations especially with the growth of international traffic movements. The concept of applying ATFM measures on cross-border traffic by different control authority can be achieved through the distributed multi-nodal ATFM concept. 1.4 Through a research collaboration led by Civil Aviation Authority of Singapore (CAAS) and Airbus ProSky, with participation from AEROTHAI, Air Traffic Management Bureau of Civil Aviation Administration of China, Department of Civil Aviation Malaysia and Hong Kong Civil Aviation Department, along with other relevant stakeholders, the effort has resulted in the Distributed Multi-Nodal ATFM Network concept. The concept relies on independent ATFM Nodes connected via information sharing network and operating on the same principle. The concept was adopted by ICAO Asia Pacific ATFM Steering Group as the foundation for cross-border ATFM in the Asia- Pacific Regional Framework for Collaborative ATFM document, which was developed to outline key performance enhancements needed for the region. 1.5 The distributed multi-nodal ATFM has since undergone several rounds of validation through the conduct of operational trials. The operational trial also includes the development and refinement of processes and procedures to enable cross-border ATFM service based on the provision of Calculated Take-Off Time (CTOT) for efficient pre-flight operations.

7 5 1.6 The progress made by the various ANSPs to operationalize the distributed multi-nodal ATFM concept would pave the way for the widespread implementation of ATFM throughout the Asia- Pacific region. Beyond the ANSPs that embark to carry out the operational trials, the ICAO Asia Pacific ATFM Steering Group (ATFM/SG) would be the suitable platform to propagate participation and implementation of ATFM. The ICAO ATFM/SG, recognizing the need and the challenges of implementing cross-border ATFM, has adopted the distributed multi-nodal ATFM concept and a viable option to address the imbalance and ensure smooth flow of air traffic across the region. 1.7 This document aims to outline key principles and requirements for all stakeholders to involve in the distributed multi-nodal ATFM concept. The document aims to establish the common operating procedures for stakeholders to have a reference and guidance to establish their local process and procedures to implement multi-nodal ATFM. This document also aims to provide the individual ANSPs the basis for publishing their respective AIP Supplement which would contain the specific details and procedures for multi-nodal ATFM operations in their area of service. It is foreseeable that the procedures established in this document will be use as a foundation to harmonize cross-border ATFM process and procedures for the wider aviation community in the Asia-Pacific region.

8 6 2 Network Concept Overview 2.1 Asia-Pacific airspace is characterized by several FIRs and low transit times for flights. Independent local ATFM measures implemented in isolation within one FIR tend to have knock-on effect on downstream FIRs. Existing ATFM frameworks operated fundamentally on centralized management of air traffic flow, which adequately addressed domestic ATFM needs. However, a distributed solution for cross-border ATFM was essential to meet the needs of Asia-Pacific. CAAS and Airbus ProSky, with inputs from other industry partners developed a Network concept as an alternative solution to implement cross-border ATFM in this region. 2.2 The concept involves each ANSP leading and operating an independent, ATFM/CDM node supported by interconnected information sharing framework. The flow of air traffic will be managed based on a common set of agreed principles among participating stakeholders. An ATFM Node comprising ANSP and associated airports manages demand and capacity through adjustments in aircraft Calculated Landing Time (CLDT) which in turn determines the Calculated Take-Off Time (CTOT) distributed to aircrafts prior to departures from the airports of origin. By using CTOT as a basis for traffic management in the region, ANSPs can avoid imposing excessive unpredictable ground delays through application of measures such as Minutes-in-Trail, Miles-in- Trail or Minimum Border-Crossing Intervals. This could also further reduce the potential airborne delay and carbon emission that would otherwise be incurred when approaching the destination airport. 2.3 Airspace Users play a fundamental role in Collaborative Decision Making (CDM) by specifying delay absorption intent and additional information regarding the flights indicating the capability of compliance to CTOTs. Additionally, being involved in the ATFM operations, Airspace Users will be able to receive advance CTOT information, which will in turn allow for improved flight operations and optimization of available resources. 2.4 Airport Operators, contribute to CDM by providing accurate and updated airport capacity and maximum allowable gate delay based on the airport s operational demand and capability to manage it. The maximum gate delay component could be considered in the appropriate issuance of CTOTs during ATFM implementation.

9 7 2.5 In summary, common core principle, efficient interconnected information sharing platform, and effective CDM chain with comprehensive stakeholder participation form the basis of Distributed Multi-Nodal ATFM Network concept. The concept in turn forms the most viable ATFM solution that can better manage the cross-border flow of traffic in Asia-Pacific region.

10 8 3 Operational Trial: A Phased Approach with Tiered Participation 3.1 The Operational Trial aims to validate the Network concept leading toward implementation. To enable timely commencement and to provide room for continuous development and expansion, the Operational Trial would first focus on addressing Demand- Capacity Balancing (DCB) at individual airports through regulating arriving flights using CTOT and GDP at ports of origin. Subsequently the project would focus on DCB within sectors and airspace managed by participating ANSPs as well as looking into flow management of long-haul interregional flights. 3.2 To methodically work toward the goal of the Operational Trial, the project adopts a multi-stage, multi-phase approach as follows: Phase 1 DCB for Constrained Arrival Airports Stage 1 Stage 2 Stage 3 Communication Linkage Demand Prediction and Protocols Validation Information Dissemination Local Table-Top Exercises Cross-Border ATFM Procedure Development and Validation through Demonstration Flights Phase 2 DCB for Constrained Airspace TBD Limited-Scope Operational Service: Providing ATFM service for planned and ad-hoc events; introduction of Combined ATFM Measure 3.3 Participating stakeholders form individual ATFM Nodes for each respective FIR comprising the ANSP as the Node leader and local Airspace Users (AUs) and Airport operators (AOs) as members. As an example, a typical Singapore ATFM Node would consist of the Civil Aviation Authority of Singapore (CAAS) as the Node Leader, Changi Airport Group (CAG) and local AUs as members. This approach provides a coherent linkage among individual stakeholders within the same FIR and ensures harmonized capability development across the industry. Tiered Participation Level Level 3 ATFM Nodes Level 2 ATFM Nodes Level 1 ATFM Nodes Expected Capabilities Capable to generate, deliver, receive, and comply with CTOT Capable to receive and comply with CTOT Observe and participate in the Trial Progress

11 9 3.4 In order to encourage more participation from regional states, the Operational Trial adopts a tiered participation level approach to provide the opportunity for stakeholders to participate based on their readiness and capability. The different participation levels also aims to provide an avenue for ATFM Nodes to upgrade to a higher level as members become more ready and capable. The participation levels and their associated capabilities are as follows: 3.5 With the rapid and sustained increase in air traffic in the region, it is palpable that ATFM nodes endeavor to be at Level 3 to implement ATFM for constraint airports when required. Recognizing the importance of ATFM nodes to make appropriate preparations to upgrade their participation level, a Readiness Checklist has been developed as a guideline for the required personnel, procedures, support system and stakeholder awareness, with the view that Node Leaders will ensure stakeholders readiness appropriately. The checklist can be found in Annex A.

12 10 4 Multi-Nodal General 4.1 To achieve effective DCB through cross-border ATFM measures, it is important that ATFM Stakeholders adhere to the Multi-Nodal to ensure a common understanding of process, procedures and outcomes. 4.2 The planning, coordination and execution of the ATFM measures by the parties referred to below in para 4.3 shall comply with the ICAO provisions specified in the Annex This document lays down the common requirements in order to optimise the available airports and airspace capacity of the ATFM Nodes for: (a) airspace users; (b) airport operators; (c) air traffic services (ATS) units; (d) other flow management positions (FMPs); (e) ATFM units; (f) slot coordinators of coordinated airports; and (g) all other organisations and individuals that have a stake in ATFM. 4.4 All flights intended to operate in accordance with the instrument flight rules (IFR) within the airspace and that is subject to ATFM. 4.5 ATFM measures should: (a) prevent excessive air traffic demand compared with declared air traffic control (ATC) capacity of sectors and airports; (b) use airspace capacity to the maximum extent possible in order to optimise the efficiency of the airspace and minimise adverse effects on operators; (c) optimise the airspace capacity made available through the development and application of capacity enhancing measures by ATS units; (d) support the management of critical events; and 4.6 The allocation of ATFM departure slots shall give priority to flights according to the order of their planned entry into the location at which the ATFM measure will apply.

13 11 Stakeholders Responsibilities 4.7 ANSP stakeholder plays a key role as Node Leaders in the Operational Trial. Accurate traffic demand prediction and airspace outlook, effective issuance of ATFM measures (CTOT information), and coordination of CDM web/teleconference are important elements provided by ATFMU and Tower ATC Units within each ANSP. The following tables outline responsibilities on the part of Level 2 and 3 ANSPs. Level 3 ANSPs Responsibilities Demand prediction and monitoring ATFM Measures Host local CDM conference Host / Participate in cross-border CDM conference Generate and distribute ATFM Daily Plan (ADP) Generate and distribute CTOT and provide slot substitutions ATFM Measure Effectiveness Adhere to CTOT in departure management Descriptions Predict traffic demand at airports within the node through a range of data sources including AU schedules, Airport slots, and ATS messages (FPLs) and assess demand-capacity imbalance; monitor effectiveness of the demand. Ensure the effective implementation of ATFM measures in conjunction with local FMP/ATS units, moreover providing information on ATFM in a timely manner to relevant stakeholder in accordance to the cross-border procedures developed. Host scheduled CDM conference with local stakeholders to prepare ATFM measures Host or participate in cross-border CDM conference with other node leaders Generate ADP to outline the air traffic situation for the day Generate CTOTs and distribute via appropriate channels preferably 2 hours before Estimated Off-Block Time (EOBT) Monitor CTOT effectiveness and lead post-ops analysis effort Manage departure traffic in adherence to CTOT within the CTOT tolerance of -5/+10 minutes Where a flight is subject to an ATFM departure slot, that slot is included as part of the air traffic control clearance Make every effort to enable departing flights to comply with CTOT.

14 12 Level 2 ANSPs Responsibilities Participate in crossborder CDM conference Adhere to CTOT in departure management Descriptions Participate in cross-border CDM conference with other node leaders Manage departure traffic in adherence to CTOT within the CTOT tolerance of -5/+10 minutes Where a flight is subject to an ATFM departure slot, that slot is included as part of the air traffic control clearance Make every effort to enable departing flights to comply with CTOT. 4.8 Other stakeholders participation is crucial to the success of the project and of an ATFM system. Timely sharing of information, operational planning, and participation in the CDM chain are all important elements provided by Airport Operators and Airspace Users. The following tables outline responsibilities on the part of these stakeholders. Airport Operators Responsibilities Provide flight schedules Update airport capacity constraints Participate in CDM conference Ensure capability in receiving CTOT info Participate in post-ops analysis Descriptions Provide updated flight schedule to ATFMU for accurate demand prediction Notify ATFMU of events that may impact capacity Actively participate in local CDM conference to provide input on ATFM measures Participate in CTOT communication flow Provide feedback on ATFM operations Airspace Users Responsibilities Flight Plan (FPL) Management DLA/CHG Message Participate in CDM conference Descriptions Ensure updated FPLs are filed at least 3 hours prior to EOBT Submit DLA or CHG messages via AFTN for delay of more than 15 minutes. * Do not update EOBT as a result of CTOT * Actively participate in CDM conference to provide input on ATFM measures

15 13 Monitor alerts and receive CTOT Raise critical operations concerns Participate in post-ops analysis Receive CTOT for departure via website and/or and monitor ATFM alerts via for changes Highlight significant operations concerns during CDM conference Provide feedback on ATFM operations Information on ATFM Measures 4.9 Information on ATFM will be distributed by the node leaders. This information includes ADPs, alerts/notifications on ATFM measures, CDM web conference/ helpdesk and CTOT dissemination. (a) The ATFM Daily Plan (ADP) The ADP will provide a summary of planned ATFM measures for the 24 hours period. ADP will be released at 0100UTC. When necessary, a revised ADP will be released. Sample of ADP can be found in Annex B. (b) Alerts/notifications on ATFM measures Alerts and notification on ATFM measures will be disseminated through the various means of communications established by the Operational Trial such as , web portal, AFTN, direct line, instant message applications, etc. Examples on alerts/notifications of ATFM measures can be found in Annex C. (c) Collaborative Decision-Making Web Conferences Collaborative decision-making (CDM) will allow all members of the ATM community to participate in the ATM decision-making that affects them. Node leaders will arrange and lead the CDM web conferences, where the ADP will be presented and discussed to provide further information on identified constraints. This platform will also provide opportunities for all stakeholders to participate in the decisions marking process which may have a potential impact on their operations. Processes and Procedures for ATFM Measures 4.10 The IATA strategic airport slot allocation procedures remain in force and airspace users are to comply with their EOBT unless subjected to ATFM or other forms of flow measures. When ATFM measures are in place, stakeholders are required to adhere to the set of Multi-Nodal ATFM processes and procedures. These were developed through the table-top exercises and demonstration flights. The following key processes and workflow for Multi-Nodal ATFM can be found in Annex D: (a) CTOT Information and Dissemination (b) CTOT Management

16 14 (c) Revision of ATFM measure (d) Re-time of flights (e) Over-riding constraints/restrictions Flight Plan and ATS Messages 4.11 In order to ensure that ATFM can balance demand and capacity effectively, up-to-date flight information is required to anticipate the traffic demand. Air traffic demand can be determined from sources such as airport flight schedules/slots, flight plans submitted by operators, and ATS messages through the Aeronautical Fixed Telecommunication Network (AFTN) The submission of timely flight plans together with ATS messages such as DLA, CNL, CHG and DEP helps ensure accuracy in demand prediction. This also allows ATFM units to derive an effective ATFM measure when required. The transmission of DEP messages provides ATFM operations with accurate updates of the predicted demand and facilitates the verification of CTOT adherence for the arrival ATFM unit, as well as allowing statistical analysis for post operations review In view of the above, stakeholders should adhere to the following: (a) Except where necessary for operational or technical reasons, FPL should be submitted not less than 3 hours before EOBT; (b) DLA message should be originated when the departure of an aircraft, for which basic flight plan data (FPL or RPL) has been sent, is delayed by 15 minutes of more after the EOBT contained in the basic flight plan; (c) CHG and CNL message are promptly originated in accordance with the provision of ICAO Doc 4444 Procedures for Air Navigation Services (PANS-ATM) ; and (d) DEP message to be transmitted in accordance with the provision of ICAO Doc 4444 Procedures Exemption of Flights for Air Navigation Services (PANS-ATM) States may choose to prioritize or exempt certain classes of flight from ATFM measures. Examples of such flights include but are not limited to: (a) flights experiencing an emergency, including aircraft subjected to unlawful interference; (b) flights on search and rescue or firefighting missions; (c) urgent medical evacuation flights specifically declared by medical authorities; (d) flights with Head of State status; and

17 15 (e) other flights specifically identified by State authorities 4.15 Additionally, aircraft, which are already airborne prior to coming into ATFM area, will be exempted from CTOT requirements. Airborne and long haul flow control will be explored in the later phase of the Operational Trial. Compliance monitoring 4.16 Airspace users should plan their flight to be ready for take-off at the CTOT (at the holding point). The CTOT adherence window is defined as 5 to +10 minutes for the Operational Trial; this enables the ATC to manage traffic tactically. Level 2 and 3 ANSPs shall ensure that adherence to CTOT at an airport of departure. Departure nodes shall provide relevant information of noncompliance and the actions taken to ensure adherence to ATFM departure slots. Performance assessment 4.17 Level 3 node ANSPs shall ensure that post analysis reports are produced indicating the quality of ATFM and shall include details of: (a) causes of ATFM measures; (b) impact of ATFM measures; (c) adherence to ATFM measures; and (d) ATFM Measure effectiveness. Failure of the ATFM system 4.18 In the event of a ATFM system failure during the Operational Trial period, the node leader will advise on the cancellation of CTOT restrictions and airspace users are to depart according to their EOBTs unless alternate or other flow measures are in place. Safety Measure for the Operational Trial 4.19 Should stakeholders raise any safety concern during the trial, respective Node Leaders shall be responsible to initiate and coordinate the suspension of the test and subsequently, coordinate to resume. ATS Data Exchange Presentation (ADEXP) Messages ADEXP provides a format for use in on-line, computer to computer message exchange and for message exchange over switched messaging networks. The ADEXP specification defines the 1

18 16 principles and syntax rules of the ADEXP format. It provides this definition in terms of a comprehensive definition of the ADEXP fields. ADEXP messaging is optional during the trial ATFM ADEXP messages issued by ATFM Nodes are: SAM, SRM, SLC, FLS, DES, see Annex E for examples Slot Allocation Message (SAM) The SAM is used to inform AOs & ATS of the Calculated Take-Off Time (CTOT) computed by the ATFM system for an individual flight, to which AOs/ATC must adhere. This message is usually sent to AOs/ATS 2 hours before the last received EOBT. TITLE SAM ARCID SIA123 ADEP WSSS ADES VTBS EOBD EOBT 0100 CTOT 0115 REGUL VTBS TAXITIME 0015 REGCAUSE WA 84 Figure 4-1 Composition of Slot Allocation Message (SAM) The SAM is used to inform AO s and ATS of the Calculated Take-Off Time (CTOT) for an individual flight. Normal response of AO s/ats to a SAM message AO s must comply with the CTOT. A slot is issued as a Calculated Take-Off Time (CTOT). The CTOT is defined as a time at which the aircraft shall take-off. The calculation of take-off times takes into account the off-block times and an average taxiing time for the runway in use at the airfield concerned Slot Revision Message (SRM) After the ATFM system has issued an initial SAM, subsequent updates may be notified via the Slot Revision Message (SRM). This message may be used to indicate a delay increase or decrease. The SRM notifies a change of slot. It is issued after the SAM, if applicable. AOs/ATC must comply with the NEWCTOT. Sending of a SRM A SRM is sent to notify all concerned of either a significant change (>5 ) to the original CTOT. Such changes are due to circumstances unrelated to the flight e.g. the introduction of a new restriction or a change to the parameters of an existing restriction. When AO modifies slot on the web portal or through the Nodes and the new slot is within a TMI then a SRM will be sent. To notify all concerned of a routine improvement/deterioration of the CTOT. TITLE SRM ARCID ABC101 ADEP VTBS ADES VHHH EOBD EOBT 0125 NEWCTOT 0150 REGUL VHHH COMMENT CLDT TAXITIME 0010

19 17 REGCAUSE WA 84 Figure 4-2 Composition of a Slot Revision Message (SRM) Response of AOs/ATS to SRM Comply with the NEWCTOT Flight Suspense Message (FLS) Indicates that a specific flight has been suspended in the system and is considered as not taking off. The flight data is kept in the database, but suspended (closure of an aerodrome for a long period, for example). AOs may suspend their flights on Web portal and later de-suspend their flights into open slots. This is used when an AO is experiencing technical difficulties and needs to temporarily suspend their flight. AOs are still required to send a CHG or DLA to modify the FPL. The system will cancel the original CTOT, issue the suspension with a Flight Suspension (FLS) message and await the response of the AO. TITLE FLS ARCID ABC101 ADEP VHHH ADES VTBS EOBD EOBT 0945 TAXITIME Slot Requirement Cancellation Message (SLC) Figure 4-3 Composition of Flight Suspense Message (FLS) Sent to AOs/ATS to advise that a flight is no longer subject to ATFM measures and may depart without delay or as per EOBT. An SLC is sent to AOs/ATS to advise that a flight which has received a CTOT is no longer subject to an ATFM restriction. It may be due to the change in parameters of an existing restriction or its cancellation, or to the reception of a message from AOs such as DLA, and CHG. TITLE SLC ARCID ABC101 ADEP VHHH ADES VTBS EOBD EOBT 0945 TAXITIME 0015 Figure 4-4 Composition of Slot Requirement Cancellation Message (SLC) Response of AOs/ATS to a SLC A flight may normally depart without an ATFM restriction De-Suspension Message (DES) This message indicates that a flight, which was previously suspended, is now de-suspended and active in the system. No further action is expected after the reception of a DES by the AO.

20 18 The ATFM system sends a DES when a flight not subject to ATFM restrictions is de-suspended. The original suspension could have been due to e.g. receipt of an SAM, the effect of exceptional conditions, closure of aerodrome, termination of the activation monitoring. TITLE DES ARCID ABC101 ADEP VTBS ADES WSSS EOBD EOBT 0945 COMMENT CLDT TAXITIME 0015 Figure 4-5 Composition of a De-Suspension Message (DES) The required action by the AO/ATC is to amend the EOBT by more than 15 minutes later than the EOBT given in the flight plan by sending a DLA message.

21 19 Readiness Checklist Annex A-1 LEVEL 3 ANSP Checklist Item Operations Capacity Assessment Procedure Internal Communication Procedure ATFMU Staffing Staff Training ATCs Staff Training ATFMU Managers and FMPs System Support ATFM Support System Capacity Assessment Tool (if needed) CTOT Distribution Channels Web Conference and Help Desk Facility Awareness / Outreach Engagement with Local Stakeholders (Airlines and Airport Operators) Awareness Documents / AIP Supplement / NOTAM Regulator Engagement Rationale To ensure that the ANSP is able to accurately assess airport capacity under various situations, and thus able to put appropriate Airport Acceptance Rate (AAR) and ATFM program in place To ensure ADP, ATFM Measures and CTOT information can be communicated in a timely manner among ATFMU and operational ATS units To ensure that the ATFMU is operational and staffed with appropriate personnel, able to initiate ATFM program when needed regardless of time-of-day To ensure that ATCs understand the ATFM concept of operations and are able to facilitate departures for flights regulated by CTOTs. This also includes training on CTOT confirmation through clearance delivery. To ensure ATFMU staffs are appropriately trained and capable of facilitating ATFM program effectively. This includes demand-capacity balance assessment, initiation and administering of ATFM Measure, and provision of assistance to stakeholders through Help Desk facility. To ensure that the ATFM Support System that is able to (1) accurately predict demand against capacity, (2) generate and disseminate CTOT information, and (3) allow user to interact with CTOT by changing, adding, canceling, and swapping slots. To aid ATFMU personnel in assess resource (airport / airspace) capacity accurately. To ensure ATFMU can disseminate CTOT information to relevant stakeholders in a timely manner through channels discussed (Web Portal, , AFTN) To ensure the ATFMU can host online web conference for the CDM process and also provide Help Desk for stakeholders to coordinate and/or request assistance during the ATFM program To exchange knowledge on ATFM concept of operations and procedures between ANSP and Aircraft Operators / Airport Operators and ensure understanding among all stakeholders To ensure information regarding the Operational Trial gets distributed to relevant stakeholders and can affect changes in their operations to support the progress To ensure that regulator is up to date with the progress of the Operational Trial, and can assist in any regulatory administration necessary

22 20 Readiness Checklist Annex A-2 LEVEL 2 ANSP Checklist Item Operations Internal Communication Procedure ATFM Point of Contact Staff Training ATCs System Support ATFM Communication Linkage Awareness / Outreach Engagement with Local Stakeholders (Airlines and Airport Operators) Rationale To ensure ADP and CTOT information can be communicated in a timely manner among ATFM Point of Contact and operational ATS units To ensure that there is an established Point of Contact for ATFM operational information and that the Point of Contact can disseminate information to relevant units as appropriate To ensure that ATCs understand the ATFM concept of operations and are able to facilitate departures for flights regulated by CTOTs. This also includes training on CTOT confirmation through clearance delivery. To ensure that there is an established communication linkage to receive ADP and CTOT information through channels discussed (Web Portal, , AFTN) To exchange knowledge on ATFM concept of operations and procedures between ANSP and Airlines / Airport Operators and ensure understanding among all stakeholders

23 21 Readiness Checklist Annex A-3 AIRLINES / AIRSPACE USERS Checklist Item Operations Internal Communication Procedure ATFM Point of Contact Staff Training Pilots and Dispatchers System Support ATFM Communication Linkage Awareness / Outreach Engagement with Ground Handlers Rationale To ensure ADP and CTOT information can be communicated in a timely manner between Flight Dispatchers and Pilots and other relevant operational units To ensure that there is an established Point of Contact for ATFM operational information and that the Point of Contact can disseminate information to relevant units as appropriate To ensure that Pilots and Flight Dispatchers understand the ATFM concept of operations and are able to appropriately plan departures for flights regulated by CTOTs or coordinate with ATFMU to manage CTOTs if needed To ensure that there is an established communication linkage to receive ADP and CTOT information through channels discussed (Web Portal, , AFTN) To exchange knowledge on ATFM concept of operations and procedures with relevant Ground Handlers and ensure understanding as Ground Handlers can sometimes be vital to aircraft turnaround process for flights regulated by CTOTs

24 22 Readiness Checklist Annex A-4 AIRPORT OPERATORS Checklist Item Operations Internal Communication Procedure ATFM Point of Contact Staff Training Airside Operations / Gate Planning System Support ATFM Communication Linkage Rationale To ensure ADP and CTOT information can be communicated in a timely manner between relevant units for operations To ensure that there is an established Point of Contact for ATFM operational information and that the Point of Contact can disseminate information to relevant units as appropriate To ensure that Airside Operations / Gate Planning Personnel understand the ATFM concept of operations and are able to appropriately plan gate usage for flights regulated by CTOTs or coordinate with ATFMU to manage CTOTs if needed To ensure that there is an established communication linkage to receive ADP and CTOT information through channels discussed (Web Portal, , AFTN)

25 23 ATFM Daily Plan (ADP) TEMPLATE Annex B ATFM DAILY PLAN DATE / TIME OF ISSUE STATUS / REFERENCE SINGAPORE 17 NOVEMBER 15, 0100UTC NEW / WSSS CONSTRAINTS AND IMPACT EXPECTED LOCATION APPLICABLE ARRIVAL REMARK PERIOD (UTC) DELAY (AVERAGE) WSSS 17 NOV THUNDERSTORM 20 MINS ATFM MEASURE / REDUCED AAR LOCATION ATFM MEASURE PERIOD (UTC) NOMINAL AAR (Per Hour) REDUCED AAR % OF REDUCTION WSSS 17 NOV % WSSS 17 NOV % OTHER INFORMATION Weather Condition SIGMET, AD, TAF, METAR, Met charts, etc) Additional Remarks

26 24 Alerts/notifications on ATFM Messages Template Annex C-1 1. ADP dissemination + CDM Web Conference Subject: MULTI-NODAL ATFM OPS TRIAL TABLE-TOP EXERCISE [Node] ADP and CDM Web Conference Dear All, Please refer to the attached for: 1. ADP - Information on the declared AAR and proposed ATFM Measure 2. Meteorological Information Due to thunderstorm with rain expected from [start time] to [end time], there is a high potential for ATFM Measure to be initiated for arrivals into [ICAO designator for airport] on [date] from [start time] to [end time] Action required: ATFMUs (Level 2 & 3) please join the CROSS BORDER web conference conducted by [Node] ATFMU at [time] UTC. URL [ web conference address] Airlines and Airport Operators participation in the cross border CDM web conference are OPTIONAL No acknowledgement on the receipt of this is required. If you encounter any issues participating in the web conference, please [Node] ATFMU at [Node s ATFMU address] THIS IS A TABLE TOP EXERCISE NOT REQUIREMENT TO PARTICIPATE IN ANY WEB CONFERENCE COMPLIANCE OF CTOT IS NOT REQUIRED

27 25 Alerts/notifications on ATFM Messages Template Annex C-2 2. CTOTs Publication and Slot management Web Conference Subject: ATFM OPS TRIAL MULTI-NODAL TABLE-TOP EXERCISE [Node] CTOTs Publication and Slot Management Web Conference Dear All, ATFM Measure will be initiated for arrivals into [ICAO designator for airport] on [date] from [start time] UTC to [end time] UTC. Calculated Take Off Time (CTOT) Information Please refer to the following website: [ATFM CTOT information website] to view CTOT information. Slot Management (If required) 1. Identify the flight(s) and slot you wish to swop. Example: Slot Swop: Flight A and Flight B Open Slot: Flight C and Slot xx/xxxx 2. Join the Slot management web conference conducted by [Node] ATFMU to request for slot change. URL [Web conference address] Action required: Login to web portal using User ID and Password which was provided to the key POCs in your organization (please check with your respective POCs) View CTOT information Acknowledge the receipt of this through your ATFM Node leader If required, join Slot Management web conference THIS IS A TABLE TOP EXERCISE - COMPLIANCE OF CTOT IS NOT REQUIRED

28 26 Alerts/notifications on ATFM Messages Template Annex C-3 3. Slot Management Subject: ATFM OPS TRIAL MULTI-NODAL TABLE-TOP EXERCISE [Node] Slot Management Dear all, Please note that the following request for Slot Management is successful. Slot Swop Flight A: Updated CTOT XXXX UTC Flight B: Updated CTOT XXXX UTC Open Slot Flight C: Updated CTOT XXXX UTC Please refer to the following website: [ATFM CTOT information website] to view the updated Calculated Take Off Time (CTOT) information. THIS IS A TABLE TOP EXERCISE - COMPLIANCE OF CTOT IS NOT REQUIRED

29 27 Alerts/notifications on ATFM Messages Template Annex C-4 4. ADP Revision Dissemination Subject: ATFM OPS TRIAL MULTI-NODAL TABLE-TOP EXERCISE [Node] ADP Revision Dissemination Dear All, ATFM Measure implemented for arrivals into [ICAO designator for airport] on [date] from [start time] UTC to [End Time] UTC will be REVISED. Due to change in weather conditions, the duration of the ATFM Measure will be extended till [End Time] UTC. With a further reduced AAR of xx between [start time] UTC to [End Time] UTC Please refer to the following website: [ATFM CTOT information website] to view the revised Calculated Take Off Time (CTOT) information. Action required: Login to web portal using User ID and Password which was provided to the key POCs in your organization (please check with your respective POCs) View revised CTOT information THIS IS A TABLE TOP EXERCISE - COMPLIANCE OF CTOT IS NOT REQUIRED

30 28 Alerts/notifications on ATFM Messages Template Annex C-5 5. CTOT Publication (Revision) + Slot Management Web Conference Subject: ATFM OPS TRIAL MULTI-NODAL TABLE-TOP EXERCISE [Node] CTOT Publication (Revision) + Slot Management Web Conference Dear All, ATFM Measure for arrivals into [ICAO designator for airport] on [date] has been REVISED from [start time] UTC to [End Time] UTC Revised Calculated Take Off Time (CTOT) Information Please refer to the following website: [ATFM CTOT information website] to view CTOT information. Slot Management (If required) 3. Identify the flight(s) and slot you wish to swop. Example: Slot Swop: Flight A and Flight B Open Slot: Flight C and Slot xx/xxxx 4. Join the Slot management web conference conducted by [Node] ATFMU to request for slot change. URL [Web conference address] Action required: Login to web portal using User ID and Password which was provided to the key POCs in your organization (please check with your respective POCs) View REVISED CTOT information Acknowledge the receipt of this through your ATFM Node leader If required, join Slot Management web conference THIS IS A TABLE TOP EXERCISE - COMPLIANCE OF CTOT IS NOT REQUIRED

31 CTOT Dissemination and Publication (1/2) Annex D-1 Arrival ATFMU Arrival Airport Departure ATFMU Departure Airport Airspace Users Assessment of demand prediction and weather conditions Disseminate ADP through indicating time and attach web link for CDM web conference Receive ADP Receive ADP and prepare for web conference Receive ADP Receive ADP Conduct cross-border CDM web conference Join web conference (optional) Join web conference Join web conference (optional) Join web conference (optional) Model and implement ATFM measure with reduced AAR Arrival ATC Departure ATC Pilots Publish CTOTs on web portal No action required No action required No action required

32 30 CTOT Dissemination and Publication (2/2) Annex D-2 Arrival ATFMU Arrival Airport Departure ATFMU Departure Airport Airspace Users CTOTs Publication Receive and access web portal to view CTOTs Receive and access web portal to view CTOTs Receive and access web portal to view CTOTs Receive and access web portal to view CTOTs Send alerts to stakeholders informing them of the implementation of ATFM measure, publish of CTOTs on web portal and slot management web conference link Inform ATC of ATFM Measures Note the changes in arrival timing for gate planning Inform ATC of CTOTs Collate acknowledgement s of CTOTs from all local node Inform Arrival ATFMU on the receipt of CTOTs by all local node Note CTOT information for gates planning Acknowledge implementation of ATFM measure through to respective local ATFMUs Acknowledge implementation of ATFM measure through to respective local ATFMUs Inform affected flights of CTOTs Arrival ATC Departure ATC Pilots Note ATFM measures for arrivals Receive CTOTs Receive CTOTs

33 31 Annex D-3 CTOT Compliance Arrival ATFMU Arrival Airport Departure ATFMU Departure Airport Airspace Users After CTOT dissemination Monitor changes in demand prediction and the amount of pop-up flights Note changes in arrival timing for gate planning No action required Note CTOT information for gate planning No action required Arrival ATC Departure ATC Pilots Assess effectiveness of existing ATFM measure and revise/cancel ATFM measure, if required Tactical management of arrivals with due considerations to compliance flights Refer to CTOTs to facilitate departures Depart in compliance with CTOTs

34 32 CTOT Management Slot Swop between 2 Flights Annex D-4 Pilots Arrival ATFMU Departure ATFMU Flight A inform Flight Ops unable to comply CTOT due technical Maintain web conference line to serve as a Help Desk for CTOT management Acknowledge slot swop information from Arrival ATFMU through Inform ATCs and Airports of slot swop information Airspace Users Determine which flight (Flight B) to perform a slot swop with Flight A based on web portal information Assist Flight Ops in slot swop through web portal Departure ATC Facilitate departures based on revised CTOTs Departure Airport Note revised CTOTs information for gates planning Request for slot swop between Flight A and B from Arrival ATFMU Receive Revised CTOTs Inform Arrival Airport, Departure ATFMUs and Airspace Users of revised CTOTs through Arrival Airport Note the changes in arrival timing for gate planning

35 33 CTOT Management Slot Swop into Open Slot Annex D-5 Pilots Arrival ATFMU Departure ATFMU Flight C inform Flight Ops unable to comply CTOT due scheduling requirements Maintain web conference line to serve as a Help Desk for CTOT management Acknowledge slot swop information from Arrival ATFMU through Inform ATCs and Airports of slot swop information Airspace Users Departure ATC Departure ATC Check and identify appropriate open slot for Flight C based on web portal information Assist Flight Ops in slot swop through web portal Facilitate departures based on revised CTOTs Note revised CTOTs information for gates planning Request to swop Flight C into identified open slot from Arrival ATFMU Receive Revised CTOTs Inform Arrival Airport, Departure ATFMUs and Airspace Users of revised CTOTs through Arrival Airport Note the changes in arrival timing for gate planning

36 34 Cancellation of ATFM Measures Annex D-6 Arrival ATFMU Arrival Airport Departure ATFMU Departure Airport Airspace Users Assessment of ATFM measures based on Demand Capacity Balancing ATFM measures is no longer required, Arrival ATFMU decides to cancel/purge the ATFM measures Note the cancellation of ATFM measures for arrivals Arrival ATC Note the cancellation of ATFM measures and inform Departure Airport and ATC Departure ATC Note the cancellation of ATFM measures for arrivals Note the cancellation of ATFM measures for arrivals and inform affected flights Pilots Send alerts to stakeholders informing the cancellation of ATFM measure Note the cancellation of ATFM measures for arrivals Note the cancellation of ATFM measures and facilitate departures based on normal operations Acknowledge cancellation of ATFM measure and depart based on normal operations

37 35 Over-riding Flow Constraints/Restrictions on ATFM Measures Annex D-7 When applicable Airspace Users Departure ATFMU Arrival ATFMU Inform arrival ATFMU if there is an over-riding constraint Inform arrival ATFMU if there is an over-riding constraint Manually exclude the particular arrivals with another known restriction prior to issue of CTOTs or Departure ATC Inform arrival ATFMU if there is an over-riding constraint Departure Airport Inform arrival ATFMU if there is an over-riding constraint Tactical management of arrivals for unknown restrictions and evaluate at post event

38 36 Re-timing of Flights into Contraint Period Annex D-8 Airspace Users Arrival ATFMU Cancel and refile FPL or send Delay or Change messages Note cancelled/ new FPL/ Delay/ Change messages sent by airline Monitor changes in demand prediction and the amount of pop-up flights Revise ATFM measure if required

39 37 Re-timing of Flights out of Contraint Period Annex D-9 Airspace Users Arrival ATFMU Cancel and refile FPL or send Delay or Change messages Note cancelled/ new FPL/ Delay/ Change messages sent by airline

40 38 Revision of ATFM Measures Annex D-10 Arrival ATFMU Arrival Airport Departure ATFMU Departure Airport Airspace Users Assessment of constraint and determine if revision of ATFM measure is required Further reduce AAR and extend duration of ATFM measure Receive revised ADP Receive revised ADP Receive revised ADP Receive revised ADP Disseminate ADP revision through indicating intention to revise ATFM measure (reduce AAR) Arrival ATC Departure ATC Pilots Model and implement ATFM measure with reduced AAR No action required No action required No action required Publish CTOTs on web portal

41 39 CTOT Publication (Revision) Annex D-11 Arrival ATFMU Arrival Airport Departure ATFMU Departure Airport Airspace Users CTOTs Publication (Revision) Send alerts to stakeholders informing them of the implementation of revision of ATFM measure Inform ATC of ATFM Measures Receive and access web portal to view revised CTOTs Note the changes in arrival timing for gate planning Arrival ATC Note the revision of ATFM measures for arrivals Receive and access web portal to view revised Inform ATC of revision in CTOTs Collate acknowledgement s of CTOTs from all local node Inform Arrival ATFMU on the receipt of CTOTs by all local node Departure ATC Receive and access web portal to view revised CTOTs Note revised CTOT information for gates planning Acknowledge revision of ATFM measure through to respective local ATFMUs Facilitate departures based on revised CTOTs Receive and access web portal to view revised CTOTs Acknowledge revision of ATFM measure through to respective local ATFMUs Inform affected flights of revised CTOTs Pilots Depart in compliance to revised CTOTs

42 ATFM ADEXP ATFM Messaging Annex E-1 Each ATFM message comprises a number of fields some of which are mandatory and some optional. Their number varies according to the message type. The fields used ATFM messages are summarized as follows. FIELDS ADEP ADES CTOT EOBD EOBT NEWCTOT NEWEOBT REGUL COMMENT TAXITIME REGCAUSE TITLE DEFINITION ICAO indicator of aerodrome of departure ICAO indicator of aerodrome of destination Calculated Take-Off Time Estimated Off-Block Day. Estimated Off-Block Time Revised CTOT Revised EOBT Identifier for the restriction imposed (may include more than one) Commentary Taxi Time Regulation Cause Title of the message

43 41 ATFM ADEXP Messages List (Optional) Annex E-2 ATFM Messages issued by ATFM Nodes: SAM, SRM, SLC, FLS, DES ATFM Messages Examples The following tables give examples of all ATFM messages currently in use. The tables include a brief description of each message and subsequent actions. Message Originator and Description Action - TITLE SAM - ARCID ABC123 SAM: Slot Allocation Message - ADEP VTBS Sent to AU/ATC 2 Hours before last received - ADES WSSS EOBT. - EOBD Sent to AUs/ATS 2 hours before - EOBT 0925 Web-portal shows CTOT. the last received EOBT. AUs/ATC - CTOT 1037 must comply with the CTOT. - REGUL WSSS The SAM is used to inform AUs & ATS of the - COMMENT CLDT Calculated Take-Off Time (CTOT) computed 1237 by ATFM system for an individual flight, to - TAXITIME 0010 which AUs/ATC must adhere. - REGCAUSE TBA - TITLE SRM - ARCID ABC123 - ADEP VTBS - ADES WSSS - EOBD EOBT NEWCTOT REGUL WSSS - COMMENT CLDT TAXITIME REGCAUSE TBA - TITLE SLC - ARCID ABC123 - ADEP VTBS - ADES WSSS - EOBD EOBT TAXITIME 0010 SRM : Slot Revision Message Sent to AU/ATC to pass or confirm any revision to a CTOT following the issue of the initial SAM. This message may be used to indicate a delay increase or decrease. SLC : Slot Requirement Cancellation Message Sent to AU/ATC to advise that a flight, which has received a CTOT, is no longer subject to a restriction. The SRM notifies a significant change of slot. AUs/A TC must comply with the NEWCTOT. Flight may depart without restriction unless a new message is received later.