2 July 2015 © Thales Australia Limited. This document and the information it contains is commercial-in-confidence and shall remain the property of Thales Australia Limited. Any unauthorised use or disclosure of its contents is prohibited. AIDC status October 2014

1 2 July 2015 Communications OVERVIEW  TopSky-ATC and AIDC implementation  Geographical view  Technical view (Messages list, technology: X-25 / AFTN / AMHS / IP)  Lessons learned in the implementation of AIDC  CONCLUSION

2 2 July 2015 Communications OVERVIEW  TopSky-ATC and AIDC implementation  Geographical view  Technical view (Messages list, technology: X-25 / AFTN / AMHS / IP)  Lessons learned in the implementation of AIDC  CONCLUSION

3 2 July 2015 Communications AIDC implementation - world map Take Away - Key Message of the Slide (optional) Thales en-route centres market share (#1 worldwide) 82 FIRs out of 300 approx., + 60 countries or 27% worldwide market share More than 20 countries over AIDC (v1, v2, v3) AIDC installed AIDC installed and operational

4 2 July 2015 Communications AIDC implementation – Messages list Implemented operationalTransmissionReception ABIAutomatic or ManualAutomatic CPLAutomatic or ManualManual ESTAutomatic or ManualAutomatic PACAutomatic or ManualAutomatic MACAutomatic or ManualManual CDNManual ACPAutomatic or ManualAutomatic (EST) or manual (CDN) REJManual TOCAutomatic or ManualAutomatic AOCManualAutomatic EMGManualAutomatic MISManual LAMAutomatic LRMAutomatic TDMAutomatic

5 2 July 2015 Communications AIDC implementation – Messages list Implemented in deploymentTransmissionReception ADSManual TRUManual Under implementationTransmissionReception FANN/A FCNN/A ASMN/A

6 2 July 2015 Communications AIDC implementation – Technology  Implemented operational  AIDC over X25, AFTN, IP, AMHS  But there is no standard for AIDC over IP  Session layer to be standardised

7 2 July 2015 Communications OVERVIEW  TopSky-ATC and AIDC implementation  Geographical view  Technical view (Messages list, technology: X-25 / AFTN / AMHS / IP)  Lesson learned in the implementation of AIDC  CONCLUSION

8 2 July 2015 Communications Lessons learned  General feed-back from integrators and operational people is very positive: only two significant issues  Reasons  Dynamic standard  ICD definition with customer Design Review process ICD defines all OSI Layers, data transmitted and options being exercised  High flexibility of the TopSky-ATC data preparation offline data defined (messages conditions, timer, Protocol, connections, flag (CPL/LAM, EST/LAM), format)  Clear Letter of Agreement  Test strategy (simulation, operational tests)

9 2 July 2015 Communications Lessons learned  Offline definition example

10 2 July 2015 Communications CONCLUSION  Positive Feed back  Future development  Native Product should gather most AIDC developments  Next Generation product will implement full AIDC V3 based on previous programs Block levels, Mach number, OTD/WTD ADS/TRU messages FAN/FCN and ASM messages

11 2 July 2015 New HMI: Normal case Communications EventPosition StateCoord StateUI Example NotifiedNot Started QFA092 H XCCS ResponsibleNot Started QFA092 H XCCS ABI SentResponsibleNotified QFA092 H XCCS EST SentResponsibleNotified QFA092 H XCCS ACP received after ESTResponsibleCompleted QFA092 H XCCS Action click on RESP Indicator field TOC sent Transfer-Control-OutCompleted QFA092 H XCCS AOC received ExitingCompleted QFA092 H XCCS

12 2 July 2015 EventPosition StateCoord StateUI Example EST SentResponsibleNotified QFA092 H XCCS Timeout or LRM ReceivedResponsibleFailed QFA092 H XCCS Tasklist Entry: Timeout for QFA… Action Click on phone iconResponsibleFailed Clearance Window opens on Exit tab Apply in Clearance Window clicked ResponsibleCompleted QFA092 H XCCS Next FIR AIDC failure

2 July 2015 © Thales Australia Limited. This document and the information it contains is commercial-in-confidence and shall remain the property of Thales Australia Limited. Any unauthorised use or disclosure of its contents is prohibited. Thank you