1. ATN 2001, London - 18 Sep 01 1 PETAL II and II Extension Maastricht Multi-stack Implementation Lessons Learnt Prepared by Gustaaf Janssens/Konrad Koebe Maastricht UAC

2. ATN 2001, London - 18 Sep 01 2 TOPICS n What Do We Mean by Multi-Stack? n Why Multi-Stack ? n What Are Multi-Stack Design Considerations ? n MUAC Ground Architecture n MUAC Schedule Achievements n How Do We Test ? n What Are Our Lessons Learnt ? n Next Steps n Conclusions

3. ATN 2001, London - 18 Sep 01 3 What Do We Mean by Multi-Stack ? n Accommodating Existing Specifications for AGDL uNEAN Extension (Prototype VDL4) uFANS-1/A uATN SARPs n Aim uCommunicate With Any Avionics Equipment Using One Of The Specifications

4. ATN 2001, London - 18 Sep 01 4 Why Multi-Stack ? n PETAL-II Project Needs for MUAC uOperations - Hide AGDL Technology for User F Operational Requirements Validation Independent From AGDL Technology uQuick Implementation F Project Has to Compete With Daily Life Activities at an Operational Centre uTake Advantage of Existing Operational Avionics Equipment uEncourage ATN SARPs based Air and Ground Implementations

5. ATN 2001, London - 18 Sep 01 5 Design Constraints (1) n Fit In MUAC Existing Ground Structure uHMI, FDPS, Gateways F Add Functionality in HMI and FDPS, Add AGDL Gateway uHMI F Add to Normal Controller Presentation and Interface uFDPS F Based on ATN SARPs Ground End User Applications Definitions u AGDL Gateway F Single Access Point for FDPS F Access Points for Underlying AGDL Technologies

6. ATN 2001, London - 18 Sep 01 6 Design Constraints (2) n Evolutionary Development uNext Step Building on Results of Predecessor

7. ATN 2001, London - 18 Sep 01 7 Maastricht Multi-stack GROUND End System (1) Controller HMI Controller HMI Controller HMI Controller HMI Flight Data Processing System ATM Services NEAN GWY NEAN 9705 BER P2GW (PETAL 2 GATEWAY) FANS-1/A GWY SITA ProATN ES 9705 PER VDL2-ATN ProATN ROUTER

8. ATN 2001, London - 18 Sep 01 8 Maastricht Multi-stack GROUND End System (2) Controller HMI Controller HMI Controller HMI Controller HMI Flight Data Processing System - Flight plan / address association - ATN SARPs (ICAO 9705) CM, ADS, CPDLC - All datalink service logic and dialogue control P2FEP NFEP - Aircraft address/state - ASE emulation CM, CPDLC, ADS - Conv. to NEAN specs. FAFEP - Aircraft address/state - ASE emulation CM, CPDLC, ADS - Conv. To FANS specs ALLA- P2PI - Aircraft address/state - BER-PER Conversion. ProATN - ASEs: CM, CPDLC, ADS - ATN Router FANS-1/A Gateway NEAN Server 9705 BER 9705 PER P2GW

9. ATN 2001, London - 18 Sep 01 9 Design Constraints (3) n P2GW uHolds and Manages Addressing Data uBuffers FDPS from Unexpected communications uMADAP Msg= { Msg ID, Infra ID+24bits+FID+Reg.Mark+9705-BER-Msg} uHides Communication and Network Specifics from FDPS

10. ATN 2001, London - 18 Sep 01 10 Design Constraints (4) n AGDL Applications implemented u CM, ADS, CPDLC n FDPS AGDL Services Using these Applications uCM: DLIC Acceptance uADS: ADS demand (FLIPCY), ADS periodic (CAP) uCPDLC: (ACL, ACM, AMC) n FDPS Functionality Used for AGDL u Manages Flight plan Operational Status F DLIC acceptance and ADS, CPDLC requests F Terminates CPDLC, ADS

11. ATN 2001, London - 18 Sep 01 11 Design Constraints (5) uController Authorisation F Only Controlling Sector handles CPDLC  FDP Controls Sequence Extraction  Next internal or external sector (NDA) identities  Controls Automatic Flight Plan Action F CMContact at OLDI ABI event  CPDLC (NDA) at OLDI ACT event  Extracts Information for Controller HMI  radar picture and tabular display uProvides Authorised Input Sequences and Guidance on Controller HMI

12. ATN 2001, London - 18 Sep 01 12

13. ATN 2001, London - 18 Sep 01 13 MUAC Schedule Achievements (1) n NEAN IN 4/98 n FANS 1/A 2/99 n P2GW - BAC1/11 using ATIF/SATCOM, P-II message set. 5/00 n MC-P2GW-BAC1/11 Flight using ATIF/SATCOM, P-IIe message set. 9/00 n Application Testing: FDPS-Avionics11/00 n FDPS, P2GW Ready 3/01

14. ATN 2001, London - 18 Sep 01 14 MUAC Schedule Achievements (2) n FANS1/A ONLINE: P-IIe Message set 4/01 n NEAN OUT 4/01 n CERTification Testing Support 5/01 n Non Revenue Flights 6/01 n MUAC-RUAC Shadow Flight 7/01 n Revenue Flight 8/01

15. ATN 2001, London - 18 Sep 01 15 MUAC Technical Achievements (1) n ICAO 9705 Compliant FDPS Implementation n Usage of ATN, FANS1/A and Prototype VDL4 n First Fully Certified ATN avionics n CPDLC Flights May1998-June2001 = 8455 (FANS/NEAN) n Test Infrastructure n Test Methodology

16. ATN 2001, London - 18 Sep 01 16 How Do We Test (1) ? n Test Approach uLocal Tests F HMI, FDPS, P2GW uEnd-to-End Application Tests: F FDPS- Other ATC Centre - Avionics grounded avionics airborne avionics F Operational Observation n Overview of Our Test Configurations

17. ATN 2001, London - 18 Sep 01 17 P2GW EMUL FAME AGDG-FANS FDPS EMUL AFAME PSF AGDG ATN NON REV

18. ATN 2001, London - 18 Sep 01 18 PIIe Operational Observation VDL M2 B767 P2GW MAASTRICHT UAC Control Centre PROATN R PROATN End System FDPS LAN CPDLC Services VIA ATN/VDL Mode 2

19. ATN 2001, London - 18 Sep 01 19 What Are Our Lessons Learnt (1) ? n Step by Step Implementation uNEAN F Validation of Technical Concept and Architecture uFANS 1/A F Validation of ‘Multi Stack’ Concept HMI, FDPS Independent From AGDL Technology uATN SARPs F Validation of SARPs Compliant Implementation F Additional Operational Messages and Stack Functions uLessons F More Testing Effort due to Regression Testing ?

20. ATN 2001, London - 18 Sep 01 20 What Are Our Lessons Learnt (2) ? n ATN SARPs Implementation Tests u Early Feedback = Early Application Error Detection and Correction F BAC1-11 Test Flights F ATIF-ground Testing F End-to-End Application testing uNo Application Errors Detected During CERT, Non- Revenue and Revenue Flights

21. ATN 2001, London - 18 Sep 01 21 What Are Our Lessons Learnt (3) ? n Local Tests as Much as Possible u Avionics Emulators uTest Automation u Protocol Test facilities n External Testing is Expensive uTest Setup uTest Execution uTime Consuming n Good Test Objectives and Strategies

22. ATN 2001, London - 18 Sep 01 22 What Are Our Lessons Learnt (4) ? n Future Requirements for Test Tools and Strategies uReference Test Tools Required F Available For All Implementers F Common Development F A lot of Tools exist. Usable to further develop ? uReference Test Objectives and Strategies n Separate Test Network Required uConnect Test Systems uIntra Centre Test uAvionics Tests

23. ATN 2001, London - 18 Sep 01 23 Next Steps (1) n Complete PETAL-IIe uSystem Safety Assessment uDocument Lessons Learned uConsolidate Documentation uEvaluate Test Automation (GEODE) n New Project (P2L = PETAL To LINK2000+) (in approval and initiation phase)

24. ATN 2001, London - 18 Sep 01 24 Next Steps (2) n P2L Objectives uMaintain a State of the Art Implementation of the Existing AGDL Implementation. uEnsure Safety of all Operational Systems uIncrease the Number of aircraft applying AGDL Services (FANS, ATN) uSupport the LINK 2000+ Project F Enabler for aircraft to equip. F Enabler for other Centres F Enabler for COMS F Enabler for Test and Validation tools - Common Development and Support.

25. ATN 2001, London - 18 Sep 01 25 CONCLUSION n MULTI STACK CONCEPT WORKS ! n SERVE MORE AIRCRAFT n CONNECT TO NEIGHBOUR ATC CENTRES THANK YOU PARTNERS FOR THE COOPERATION !