1. Pan regional ICD for AIDC structure and status (SP/09)
SPECIAL IMPLEMENTATION PROJECT (SIP) ASBU B0-FICE ATS INTER-FACILITY DATA COMMUNICATION AIDC IMPLEMENTATION SEMINAR (28 –31 October 2014, Bangkok, Thailand)
Pan regional ICD for AIDC structure and status (SP/09)

2. Background
PAN ICD for AIDC is the result of the progressive evolution of the Asia/Pacific Regional ICD for AIDC, issued by the ICAO APAC on behalf of APANPIRG, and the North Atlantic Common Coordination ICD, published by the ICAO European and North Atlantic Office, on behalf of North Atlantic Systems Planning Group (NAT SPG).
Each of the two documents provided guidance on a regional basis. In recognition to provide globally harmonized guidance for AIDC, PAN ICD merging the APAC and NAT guidance material envisaged to be adopted 2014
Addresses ground to ground data link provision from technical and operational point of view.

3. Meetings on the subject
The ICAO Inter-regional AIDC Task Force (IRAIDCTF) was formed* and its first meeting was held from 16 to 18 January 2013 at the ICAO EUR/NAT Office in Paris, France
Second meeting was held from July 2013 at ICAO APAC Bangkok.
Third meeting was held from March 2014 at ICAO Montreal.
Number of Web based teleconferences.
*Terms of Reference (ToR) as approved by NAT SPG Conclusion 48/28 and APANPIRG Conclusion 23/20 to bring out a common ICD for AIDC

4. Intermediate PAN ICD Versions
Outcome of IRAIDC TF/1
(PAN ICD) Version 0.5 – November 2011/January 2013
Outcome of IRAIDC TF/2 and subsequent web meetings
PAN Regional ICD for AIDC Version 0.83 – July 2013
Outcome of IRAIDC TF/3 and subsequent web meetings
PAN Regional ICD for AIDC Version 0.92 – July 2014

5. Status - Adoption of Pan Regional ICD for AIDC by APANPIRG 25
The CNS SG/18 meeting reviewed and endorsed the then latest draft of the Pan Regional APAC/NAT AIDC ICD (Version 0.91). Later Version 0.92 was issued as outcome of Teleconference on 6 August 2014.
The ICD was initially developed based on the APAC AIDC ICD Version 3.0 and NAT AIDC ICD Version    It was anticipated that the ICD would likely be adopted by IMG in NAT Region in November 2014 then get NAT SPG agreement through correspondence by the end of 2014.  In view of the foregoing, the meeting adopted the draft Conclusion 18/12 endorsed by CNS SG/18 meeting and ATM SG/2 meeting:  
Conclusion APANPIRG 25/35 – Adoption of Pan Regional ICD for AIDC
That, the Pan Regional ICD for AIDC provided in APANPIRG/25/WP09, Appendix O, be adopted as Version 1.0 serving as regional guidance for AIDC implementation in the APAC and NAT Regions.

6. Dissolution of IRAIDCTF
Considering the tasks given by NAT SPG through Conclusion 48/28 and APANPIRG through Conclusion 23/20 being completed once the PAN regional ICD for AIDC is adopted by both the regions, the CNS SG/18 meeting agreed that IRAIDC Task Force be dissolved after adoption of the Version 1 of PAN Inter-regional ICD for AIDC by NAT SPG. Accordingly the meeting made the following Decision:
Decision APANPIRG 25/36 – Dissolving Inter-regional AIDC Task Force
That, once Version 1 of the PAN Inter-regional ICD for AIDC is adopted by both APAC and NAT Regions, the Inter- regional AIDC Task Force established through  NAT SPG Conclusion 48/28 and APANPIRG Conclusion 23/20 be dissolved.

7. Structure of Document Forward
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 Letter of Agreement on AIDC
Appendix B: Regionally Specific Messages
Appendix C: Additional Implementation Guidance Material (includes more elaborate and structured approach for implementation)

8. Structure of APAC ICD Version 3.0
Forward
The Document ( Part – I, Part –II)
Part-I
Purpose, Scope, Policy, Units of Measurement, Restriction Formats
Part – II
Introduction, Message Headers, Timers, ATSU Indicators, Engineering Considerations
Appendix A - ATS Coordination Messages
Appendix B – Error Codes
Appendix C – ATM Application Naming Conventions
Appendix D – Implementation Guidance Material
Appendix E – Relationship to ICAO AIDC Messages
Appendix F - Interim Operational Support
Appendix G – Templates for Bi-lateral LOA on AIDC

9. AIDC vs OLDI
On-Line Data Interchange (OLDI), a separate application, would not be integrated into the present PAN AIDC ICD, as it was considered out of scope for the TF.
Some ATS Units in particular with neighbouring ATS units in different ICAO regions may need to support both OLDI and AIDC.

10. Overview of Changes
Cruise Climb concept was added in addition to the Block Levels.
ATSU-1 and ATSU-2 instead of C-ATSU and D-ATSU
Harmonization of Error Codes of APAC and NAT regions.

11. Overview of Changes
Changes were made to resolve inconsistency in Optional Data Field 3 (ODF3) for CDN-CDN messages in the NAT and APAC regions.
As part of performance monitoring, RCP for AIDC message (to be delivered one-sided from machine to machine) has been included as 12 seconds for 95 percent time and 30 seconds for 99.9 percent time. In bilateral agreements, ATSUs, may agree on different performance requirements
Two types of message sets - Core and Non-core Message sets. Optional message set renamed as Non-core message set.

12. Overview of Changes
AIDC messages described in the PAN ICD may support different units of measurement to those described below. If this occurs, bilateral agreements should determine the units to be transmitted, as well as their format and any associated limitations (e.g. minimum/maximum value, resolution etc).
PCM/PCA (Profile Confirmation Message/Profile Confirmation Acceptance) messages have been added.
Region specific examples have been added.

13. Thanks for Kind Attention