1 / 48

(Global) PAN AIDC ICD

(Global) PAN AIDC ICD. AIDC Implementation Seminar 28 th – 31 st October 2014. Adam Watkin Airservices Australia. History. In 1971, Canada and the United Kingdom agreed to exchange data between Gander and Shanwick Oceanic Area Control Centres (OACs) using On-Line Data-Interchange (OLDI)

alden-pennington
Download Presentation

(Global) PAN AIDC ICD

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. (Global) PAN AIDC ICD AIDC Implementation Seminar 28th – 31st October 2014 Adam Watkin Airservices Australia

  2. History • In 1971, Canada and the United Kingdom agreed to exchange data between Gander and Shanwick Oceanic Area Control Centres (OACs) using On-Line Data-Interchange (OLDI) • Subsequently, a similar arrangement was agreed to between Reykjavik and the Shanwick OAC/ACCs • Improved efficiency between the Air Traffic Services (ATS) units concerned • However, they were not standard (or even compatible) • To gain full benefits regional standardisation was required

  3. History • At NAT SPG/25 (Paris, September 1988), a Task Force was established to develop a future ATS system concept for the whole of the NAT Region (NAT SPG/25, Conclusion 25/11 refers) • The Task Force identified that a common interface Control Document (ICD) that would describe OLDI exchanges between ATS units within and adjacent to the NAT Region was required

  4. History • At NAT SPG/26 (Paris, May 1990) it was agreed that a working group should be established to oversee the development and co-ordinated implementation of a common ICD for the NAT Region (NAT SPG/26, Conclusion 26/17 refers) • At NAT SPG/27 (Paris, June 1991), it was noted that the draft ICD was sufficiently mature to be used for planning purposes and therefore agreed that States should endeavour to replace agreements that existed at the time with the common ICD by the end of 1991

  5. History • On the basis of the work conducted by NAT SPG, APANPIRG/5 (Bangkok, 1994) undertook the task of developing a document describing the interfacility message exchanges required to support automation in the Asia Pacific region • As a result of this undertaking, Asia Pacific AIDC ICD V1 was issued in May 1995 • The content of the original document was based mainly on North Atlantic AIDC ICD • Few differences • Divergence over the years as both documents have evolved

  6. History

  7. History • Decision 20/14 – Support for Global ICD for AFTN AIDC • “That, recognizing the benefits to be gained from globally harmonized interface arrangements for AIDC, APANPIRG supports the work being undertaken by the United States to coordinate a global Interface Control Document (ICD) for AFTN AIDC and invites the Asia/Pacific Regional Office to act as the regional point of contact for this work”

  8. Establishing IRAIDCTF • Inter-regional AIDC task force (IRAIDCTF) established in January 2013 • This Task Force was established in accordance with: • NAT SPG Conclusion 48/28; and • APANPIRG Conclusion 23/20

  9. Establishing IRAIDCTF • Meetings held: • IRAIDCTF/1: Paris 16-18 January 2013 • IRAIDCTF/2: Bangkok 22 to 26 July 2013 • IRAIDCTF/3: Montreal 24-28 March 2014 • Webexes: • Web/1: 27 February 2013 • Web/2:10 April 2013 • Web/3: 11 June 2014 • Web/4: 9 July 2014 • Web/5: 6 Aug 2014

  10. Developing PAN AIDC ICD • Work initially focussed on merging the North Atlantic & Asia Pacific ICDs • Common functionalities were sometimes worded differently • Best text chosen, or new text developed • Differences identified, and an acceptable way forward discussed and implemented • There were not an insurmountable number of significant differences!

  11. Developing PAN AIDC ICD • Several messages were retained in the PAN AIDC ICD even though technically not AIDC messages • NAT (NAT Organized Track Structure Message) • TDM (Track Definition Message) • Moved to an Appendix • Retained because message format does not appear to be defined anywhere else

  12. Developing PAN AIDC ICD • Once the structure and overall content of the document was agreed to • Overhaul of text • Lessons learnt  incorporated • Area where ambiguities have occurred  improved

  13. Developing PAN AIDC ICD • Current version is V0.92 (Coordination draft) • Similar layout to parent documents • Awaiting resolution to several comments emanating from NAT SPG • Presented to OPLINK Panel meeting – Oct 2014 • Intention is to develop into an ICAO Document, with references in Annexes and PANS-ATM

  14. PAN AIDC ICD • The following slides outline the significant differences between the current Asia Pacific AIDC ICD, and the draft PAN AIDC ICD

  15. Global ICD - contents • Foreword • Chapter 1 – Abbreviations and AIDC messages • Chapter 2 – Purpose, Policy and Units of Measurement • Chapter 3 – Communications and Support Mechanisms • Chapter 4 – AIDC messages • Chapter 5 – Error Codes • Chapter 6 – Implementation Guidance Material • Appendix A – Templates for Bilateral Agreements on AIDC • Appendix B – Regionally Specific messages • Appendix C – Additional Implementation Guidance Material

  16. Chapter 2 • Cruise climb format • Examples on Field 14 formats moved to Chapter 4 • “Restriction” section significantly updated

  17. Ch2 - Cruise climb format • A format to coordinate a cruise climb has been added to Chapter 2 • Format: F340F320C • Meaning: “The aircraft is assigned FL340, cruise climbing from FL320” • The cruise climb format may be used in Field 14, or in a TRU message

  18. Ch2 – Field 14 examples • All the examples of Field 14 formats have been moved to Chapter 4 • Provides consistency, because Ch4 contains examples of other flight plan fields

  19. Ch2 - Restriction formats • The section describing Restriction format has been considerably updated. It now accommodates: • Change of speed and/or level to commence at a future time or place • Change of level to be completed by a future time or place • The descriptions in existing documents were a little confusing and contradictory • Formats are now standardised • Addition of numerous examples

  20. Chapter 3 • Specified the CRC to be used • Interpreting the AIDC Header • Measuring AIDC performance

  21. Ch3 - CRC • Historically there have been problems with the CRC, due to a number of versions of CRC-CCITT being available • Defined which specific CRC to use (“XModem”) • Provided examples of AIDC messages, along with their associated CRC for testing purposes

  22. Ch3 – AIDC Message Header • Provides information concerning the AIDC message Header • Description of the contents a description of the contents • Example showing the linking of AIDC messages using message header information

  23. Ch3 - AIDC performance • Provides information on AIDC performance: • Description and examples using time stamp information

  24. Chapter 4 – AIDC messages • Expanded description of allowable flight plan fields (with examples) • Rewrite of the description of AIDC messages • New AIDC messages added • Allowable contents of TRU message updated • Moved TDM and NAT messages

  25. Ch4 - Flight Plan fields • New section added describing flight plan fields • Description of allowable contents • Inclusion of examples (including Field 14 examples, moved from Ch2)

  26. Ch4 – Description of AIDC messages • The description of the AIDC messages has been rewritten • Standardised format and content • Examples improved, and updated to 2012 FPL format • Removed the ability to amend destination in ABI • Updated table showing allowable content of messages

  27. Ch4 – Description of AIDC messages • The description of the AIDC messages has been rewritten • Standardised format and content • Examples improved, and updated to 2012 FPL format • Removed the ability to amend destination in ABI • Updated table showing allowable content of messages

  28. Ch4 - New AIDC messages – PCM, PCA • PCM (Profile Confirmation Message) • Used to detect and recover from coordination errors, such as: • No coordination conducted at all • Coordination completed, but amendments have not been coordinated • Intended to be sent as the aircraft approaches the FIR boundary (e.g. 5 minute prior to FIR boundary)

  29. Ch4 - New AIDC messages – PCM, PCA • PCM – Contents (Mandatory) • Aircraft identification • Departure aerodrome • Estimate data • Destination aerodrome • (Optional) • Flight rules and type of flight • Number, type of aircraft, and wake turbulence category • Equipment • Route • Other information

  30. Ch4 - New AIDC messages – PCM, PCA • PCA (Profile Confirmation Acceptance) • Sent in response to a PCM • Confirms coordination information previously transmitted is correct; or • Acts as a last minute “Safety net” • PCA – Contents (Mandatory) • Aircraft identification • Departure aerodrome • Destination aerodrome

  31. Ch4 – Allowable contents of TRU message • Allowable contents of TRU message updated • Added ability to coordinate “Present level”, and “Requested Flight level”

  32. Ch4 – TDM and NAT messages • These messages are not strictly AIDC messages “(TDM TRK A 940413124001 9404131900 9404140800 LILIA 27N170W 29N180E 31N170E 32N160E MASON RTS/ PHNL KEOLA2 LILIA MASON OTR15 SMOLT OTR16 SUNNS OTR20 LIBRA RJAA RMK/0)”

  33. Ch4 – TDM and NAT messages • These messages are not strictly AIDC messages “(NAT-1/1 TRACKS FLS 310/390 INCLUSIVE JULY 01/0100Z TO JULY 01/0800Z PART ONE OF ONE PART- V YAY 53/50 54/40 55/30 56/20 56/10 MAC EAST LVLS 310 320 330 340 350 360 370 380 390 WEST LVLS NIL EUR RTS WEST NIL NAR N125A N129B- …..”

  34. Ch4 – TDM and NAT messages • These messages are not strictly AIDC messages • However, format does not appear to be defined elsewhere • Messages retained, but moved to Appendix

  35. Chapter 6 - Implementation Guidance Material • Substantial re-write • Reorganised, additional guidance added • Improved examples • Description of Area of Common Interest • Updated Flight State Transition Diagram

  36. Ch6 - Implementation Guidance Material • This chapter was significantly expanded • 15 pages in Asia Pacific ICD expanded to 41 pages in PAN AIDC ICD • Sections moved around to match the order that AIDC messages are listed in elsewhere in the document • Additional guidance provided for all AIDC message types

  37. Ch6 - Description of ACI • A description of the Area of Common Interest (ACI) has been added • Includes diagrams • References to ACI have been updated throughout the document

  38. Ch6 - Description of ACI

  39. Ch6 – Flight State Transition diagram • The flight state transition diagram was updated • Corrected previous limitations • Included new AIDC messages • Improved legend • To be discussed in greater detail later in the seminar

  40. Ch6 - mini FST diagams • Each AIDC message description has a mini flight state transition diagram associated with it • Provides an indication of how the flight state evolves as individual messages are sent

  41. Ch6 - AIDC flight threads - examples • Examples have all been updated and expanded upon • Now 14 examples • Cross section of all message types & formats • Each example contains: • Text describing the scenario; • A graphical flight thread that illustrates the sequence of messages • flight threads are colour coded • message ‘dialogues’ displayed in the same colour • A table containing the associated AIDC messages

  42. Ch6 - AIDC flight threads - examples • Example 1 – Coordination using abbreviated initial coordination dialogue • ATSU 1 transmits a notification message (ABI) to ATSU 2. The ABI contains Estimate data of RUNOD at 1209, operating in a block clearance between FL350 and FL370. By agreement, ATSU 1 includes flight planned speed/level changes in Field 15 of AIDC messages. Subsequently the estimate for RUNOD changes to 1213, but ATSU 1 has an agreement with ATSU 2 not to sent revised Notification messages for revisions of less than 5 minutes. • ATSU 1 transmits an abbreviated coordination message (EST) to ATSU 2. The proposed coordination contains Estimate data of RUNOD at 1213 operating in a block clearance between FL350 and FL370. ATSU 2 accepts the proposed coordination conditions by responding with an ACP. • ATSU 1 proposes a transfer of control responsibility by transmitting a TOC to ATSU 2. ATSU 2 accepts control responsibility by responding with an AOC

  43. Ch6 - AIDC flight threads - examples

  44. Ch6 - AIDC flight threads - examples

  45. PAN AIDC ICD - future • PAN AIDC ICD presented at OPLINKP/2 (WP/11 refers) • Proposed to be developed as an ICAO Manual Doc XXXX • Include European OLDI • Wont be merged with OLDI – too many differences • OLDI probably included as a separate section • Update Annexes, Doc 4444 appropriately

  46. More information • Adam Watkin • Air Traffic Controller • Brisbane Centre • adam.watkin@airservicesaustralia.com

More Related