System Wide Information Management in OATA

1
System Wide Information Managementin OATA
Bert Nijhof OATA Technical ManagerEUROCONTROL
DAS/SAS/OCA
2
OATA contribution to SWIM
The OATA Project provided a first contribution to
SWIMby defining the Shared Elements
Clustersandthrough the Cross Domain
Synchronisation Study
3
Cross Domain Synchronisation Study from
Austrocontrol and Frequentis
Investigated the technological solutions for
implementing SWIM
Peer-to-Peer Messaging
Information Sharing
4
OATA Logical ArchitectureSWIM and Shared Elements
Executive Planning Controller ACC
Supervisor Multi-Sector Planner Local Traffic
Manager Flow Management Position Flight Data
Operator
Airport Operator Airport Slot Coordinator Ground
Handler Stand Planner
PSR, SSR Mode-S Radar
Multi-lateration
Airport Surveillance Detection Equipment
Flow Manager Network Manager
Aircraft Operator
Airspace Manager
Tower Ground Controller Tower Runway
Controller Tower Supervisor
ADS
Pilot
ATM Operations
ATM Support
Communications and Distributed System Services
(SWIM) Messaging and Repository based
ATM Shared Elements
Meteo Service Provider
Aeronautical Information Service Provider
Aircraft Autonomous Sensors
Navigation Aids
ADS - B
Sensors
Pilot
5
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).

6
Repository Based OATA / SESAR Shared Elements
Example the Shared Flight
7
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.

8
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).

9
Infrastructure Aspects example Shared Flight
Shared Flight (Paris ACC)
Shared Flight (Rome ACC)
OO Interface Model
Domain
Technology Independent Services in support of
SWIM
Technology Specific Services
AZ
Data Model
LH
AF
Infrastructure
10
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).

11
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 http//www.oracle.com/technologi
  es/grid/docs/IDC_Grid_Whitepaper.pdf

12
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.).

13
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.

14
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)

15
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.