1SWIM-SUIT Public Launch – 23 April 2007 System Wide Information Management in OATA Bert Nijhof OATA Technical Manager EUROCONTROL DAS/SAS/OCA

2SWIM-SUIT Public Launch – 23 April 2007 OATA contribution to SWIM The OATA Project provided a first contribution to SWIM by defining the Shared Elements Clusters and through the Cross Domain Synchronisation Study

3SWIM-SUIT Public Launch – 23 April 2007 Cross Domain Synchronisation Study from Austrocontrol and Frequentis Investigated the technological solutions for implementing SWIM

4SWIM-SUIT Public Launch – 23 April 2007 OATA Logical Architecture SWIM and Shared Elements Meteo Service Provider Meteo Aircraft Autonomous Sensors Navigation Aids Air Surveillance Surface Surveillance Aircraft Navigation Aircraft Surveillance PSR, SSR Mode-S Radar ADS Multi- lateration Airport Surveillance Detection Equipment Aeronautical Information Service Provider Aircraft Operator Pilot ADS - B ATM Support ATM Operations Executive & Planning Controller ACC Supervisor Multi-Sector Planner Local Traffic Manager Flow Management Position Flight Data Operator Tower Ground Controller Tower Runway Controller Tower Supervisor Airport Operator Airport Slot Coordinator Ground Handler Stand Planner Flow Manager Network Manager Airspace Manager Communications and Distributed System Services (SWIM) Messaging and Repository based ATM Shared Elements Flight Airspace Organisation Aerodrome Navigation Aids Aircraft Sensors En-route/APP ATC Airport Operations Airspace Organisation & Management ATFCM Airspace User Operations Aerodrome ATC

5SWIM-SUIT Public Launch – 23 April 2007 Messaging: OATA / SESAR Distribution Pattern The distribution pattern (Publish/Subscribe) is used in the following cases: –Information is updated and users need to be notified that the change occurred; –The movements of aircraft are sampled and the users are interested in the most recent values of those measurements. Different Implementations of the Distribution Pattern are possible : –Web Services; –CORBA; –ATM Specific Developments (e.g. based on ASTERIX formats).

6SWIM-SUIT Public Launch – 23 April 2007 Repository Based: OATA / SESAR Shared Elements Example : the Shared Flight

7SWIM-SUIT Public Launch – 23 April 2007 Cross Domain Synchronisation Study The CDS study has: Identified the Technology Assessment Aspects for comparing the candidate SWIM technologies; Investigated the Infrastructure Aspects; Compared existing Technologies; Analysed the Transition Issues from OLDI/SYSCO, ADEXP, AFTN, etc to SWIM.

8SWIM-SUIT Public Launch – 23 April 2007 Technology Assessment Aspects The identified technologies were assessed wrt the following aspects : –Data Transport (Network characteristics; Mobility and location transparency); –Data Representation (Data Model; Schema Description; Object Replica); –Quality of Service (QOS Monitoring; QOS Negotiation); –Redundancy (Scope of Redundancy; Data Replication); –Data Ownership (Authorisation; Operational Ownership; Technical Ownership); –Access Control & Authorisation (Data Access; System Access; Data Security; Digital Signature); –Object Lifecycle (Object creation/deletion; Archiving of Data); –System Parameter Management; –Architecture (Centralised Architecture or Distributed System Architecture or Centralised Architecture with Caching).

9SWIM-SUIT Public Launch – 23 April 2007 Infrastructure Aspects example: Shared Flight AF LH AZ Data Model OO Interface Model Shared Flight (Paris ACC) Shared Flight (Rome ACC) Domain Infrastructure Technology Independent Services in support of SWIM Technology Specific Services

10SWIM-SUIT Public Launch – 23 April 2007 CDS Technology Comparison ( First half year of 2004) The following technology options for implementing SWIM were compared : –New ATM-specific technology development; –Distributed Databases; –XML based technologies (Web services); –Distributed Objects (CORBA); –“Exotic” (four years ago) solutions: GRID computing; Real time distributed data bases (i.e. used by Navy military applications).

11SWIM-SUIT Public Launch – 23 April 2007 Technologies getting more integrated Some of the technologies investigated in 2004 by the OATA CDS study are now integrated into commercial products: –Standards for GRID computing are developed as an extension of Web Services; –Grid computing has been implemented in commercial “database” products like e.g. ORACLE; –See for example:

12SWIM-SUIT Public Launch – 23 April 2007 CDS Study Recommendations The technology choice should be based on the Non Functional Requirements (response times, update and access rates, required data integrity, availability etc.) identified for each of the shared elements. Do not underestimate the non technical aspects (Institutional, organisational, training etc.).

13SWIM-SUIT Public Launch – 23 April 2007 OATA Vision for the Near Future Commercial products dealing with: –Computing Resources available on a net (Private Network or Virtual Private Network (incl. P2P versions)). –Deployable Units (DU) of software : Database services (Authentication, Authorisation, Security, Distribution, Replication, Transaction Recovery); Shared information services (Flight, Flight Scripts, Constraints, Trajectories); Application oriented services (ex: MTCD). Properties: –Automatic deployment and re-deployment based on rules (required performances (NFR) and computing resource availability; –Integrated System and Network Management.

14SWIM-SUIT Public Launch – 23 April 2007 OATA wish list for the SWIM-SUIT Project (1) Identify the technology independent SWIM Infrastructure Services; Propose the appropriate technology for each Shared Element based on known Non Functional Requirements; Map the SWIM Infrastructure Services to the selected technologies; Check / prototype the use of off-the-shelf software to achieve the identified ATM NFRs; Detail and promote the aircraft proxy (mirror) approach over time. Identify what can be done in the mid-term and long- term; Propose the geographical deployment of the aircraft proxies (close to the CNS transceivers, in the ATC centres or centrally);

15SWIM-SUIT Public Launch – 23 April 2007 OATA wish list for the SWIM-SUIT Project (2) Promote the SWIM “culture” to the involved ATM experts; –A higher Level of Abstraction to support Interoperability between Systems requires a different way of thinking by Operational Experts and Architects. Analyse the transitions / integration aspects for the introduction of SWIM for flight data, sensor data (e.g. ASTERIX), EAD, etc; Look at the integration of the system management facilities of the chosen SWIM products with the ATC Centres Technical Supervision facilities.