SWIM-SUIT Integrating Legacy System

1. SWIM-SUIT Integrating Legacy System Antonello Cedrone WP3 Leader - Selex Sistemi Integrati SWIM-SUIT User Forum, Rome

2. Agenda Legacy Adapter Overview Integration objectives and approach Integration Test Bed environment Overview of the Legacy Systems currently integrated with the SWIM-BOX Examples SWIM-SUIT User Forum, Rome

3. SWIM-BOX towards the Adapters The SWIM-BOX exposes Web Services: FDD: coarse grained services to create, update, read Flight Objects SDD: to publish/receive surveillance information AID: provides a local proxy to call AIS services over a HTTP/SOAP interface: • SDD: • Publish • getMessages • Notify • FDD: • createFO • readFO • requestFOservice • handoverFO • notifyFO • AID: • requestPrivateSlots • requestPublicSlots • requestPrivateSlotContent • requestPublicSlotContent SWIM-SUIT User Forum, Rome

4. Integrating Legacy Systems - Objectives Overall Adapter Integration and Testing ADAPTER ADAPTER ADAPTER ADAPTER Legacy Legacy Legacy Legacy ADAPTER ADAPTER Legacy Legacy Validated Carry out the Adapters of the existing legacy systems and connect them to the SWIM-SUIT prototype (SWIM-BOX) SWIM-SUIT prototype Integration & Testing Prepare the input for SWIM-SUIT Validation SWIM-SUIT prototype SWIM-SUIT User Forum, Rome

5. Local IntegrationApproach • Local Integration • This step is mandatory for each Legacy • The Legacy System is adapted to the SWIM-BOX, in a stand-alone configuration • No connection between the SWIM-BOXes • A Test application is customized by each Partner in order to: • Simulate external calls - if the Legacy has to provide services • Accept external calls – if the Legacy has to call services Legacy A Node Legacy ICD Adapter ICD Legacy System A Adapter layer SB Services SWIM-BOX Test Application FDD SDD AID SWIM core Test Application DDS/JMS Web Services SWIM-SUIT User Forum, Rome

6. Overall Integration approach Legacy B Node Legacy System B SWIM-BOX Adapter layer FDD SDD AID SB Services SWIM core DDS/JMS Web Services • Overall Integration • This step is mandatory for each Legacy • The Legacy System is adapted to the SWIM-BOX and connected to another Legacy System • Integration Tests have been built and linked to Validation scenarios • Integration Tests are technichal: subscription to SWIM-SUIT domain, produce/consume Flight Object and Flight Tracks, handover of a Flight Object Legacy A Node Legacy ICD Adapter ICD Legacy ICD Adapter ICD Legacy System A Legacy ICD Adapter ICD Adapter layer SB Services SWIM-BOX FDD SDD AID Wire-ICD SWIM core DDS/JMS Web Services SWIM-SUIT User Forum, Rome

7. Integration environment • The SWIM-BOX machine: “plug and play” ready to be connected to other SWIM-BOXes: • the SWIM-BOX application; • the Middleware (Jboss Application Server); • Legacy System environment; • Network configuration: The SWIM-BOX is configured in the VPN-SWIM network SWIM-SUIT User Forum, Rome

8. Adapting Legacy data updates Observer of Legacy state legacy legacy legacy order order order • Adapter Typology: AdapterToSwimBox • The Adapter is: • Client for the SWIM-BOX • Server of the Legacy • Adapter as Observer of the Legacy System State SWIM BOX Legacy System AdapterTo SwimBox Soap request Legacy System Data Flight Object Flight Object Legacy System Data SWIM-SUIT User Forum, Rome

9. Adapting Flight Object updates • Adapter Typology: AdapterToSwimBox • The Adapter is: • Client for the Legacy • Server of the SWIM-BOX • The SWIM-BOX acts as a proxy for the Adapter SWIM BOX Legacy System AdapterTo Legacy Request To Legacy Soap request Flight Object Legacy System Data Flight Object Legacy System Data SWIM-SUIT User Forum, Rome

10. Adaptation of Legacy Systems (1/4) • Legacy: ISPOC ATSU-AMAN – Boeing • Integration scenario: • FDD: Manager/Contributor of the FO (Trajectory, FlightScript, etc.) • SDD: In/out surveillance data flow by XML • Legacy: ENAV ACC - ENAV • Integration scenario: • FDD: Manager/Contributor of the FO • publishing the Trajectory (from the FDP subsystem) • SDD: In/out surveillance data flow is in ASTERIX cat 62 • Legacy: LISATM - NAV Portugal • Integration scenario: • FDD: User of the FO using FDP sub-system • SDD: output from LISATM is sent to the SWIM-BOX in ASTERIX cat 62 SWIM-SUIT User Forum, Rome

11. Adaptation of Legacy Systems (2/4) • Legacy: CFMU – Eurocontrol • Integration Scenario: • FDD: Manager of the FO, • pushing FO into the SWIM-BOX • It triggers the handover to another legacy • Legacy: BDV (Banca Dati Volo) - SEA Aeroporti di Milano • Airport CDM – NATS • Integration Scenario: • FDD: User, Contributor of the FO updating the gate, the stand, taxi time, taxi ways ... • Legacy: LIDO OOC – Alitalia; AOC Air France • Integration Scenario: • FDD: planning phase of the flight • Manager of the FO: publishing a large amount of data related the planning of the Flight; Contributor: missing role in the execution phase • SDD: presentation of Alitalia tracks SWIM-SUIT User Forum, Rome

12. Adaptation of Legacy Systems (3/4) • Legacy: Frequentis EAD • Integration Scenario: the Legacy is capable to provide an EAD and a WFS Server, conform to AIXM data model, accessed by: • SkyView tool (by EuroControl)  • an open source WFS browser • Air France (in progress) SWIM-SUIT User Forum, Rome

13. Adaptation of Legacy Systems (4/4) • Legacy: Alitalia FMS; Boeing FMS • Integration Scenario: • FDD: Contributor of the FO Trajectory • publishing ETA on WTP and DEST • SDD: in XML format - the last waypoint overflown SWIM-SUIT User Forum, Rome

14. Example of the ENAV-ACC Adapter ENAV Legacy Receive Legacy Flight Plan Send Legacy Flight Plan LegacySender LegacyReceiver SWIM BOX AdapterToSwimBox AdapterToLegacy ENAV-SWIM DataConverter Legacy SenderReceiver Bean Map of Legacy Flight Plan and Flight Object SWIM-SUIT User Forum, Rome

15. Questions and Feedback