OATA and the Flight Object

1
OATA and the Flight Object

• Shanda Cordingley
• EUROCONTROL DAS/ESC
• OATA Chief Architect

European Organisation for the Safety of Air
Navigation
2
Questions

• What is the OATA Project?
• What is OATA doing on the Flight Object?
• How does FOIPS fit with OATA?
• What about SWIM?

3
OATA Phase 2 Project Background

• Primary Goals
• To define and maintain an Overall ATM/CNS Target
  Architecture (OATA) that is accepted as a target
  throughout the EUROCONTROL Organisation (Agency
  Member States)
• To contribute to the future European-wide
  processes for the industry-standardisation of ATM
  system components and regulation of
  interoperability requirements.
• Secondary Goals
• To achieve alignment between the EUROCONTROL
  OATA, and those of the USA and other ICAO Member
  States outside EUROCONTROL
• To achieve global interoperability for users.

4
OATA Phase 2 Main Deliverables

• Concept of Operations
• ConOps 2011 delivered, ConOps 2020 in progress
• Architecture
• 8th iteration (of 9) completed
• Management Overview, Technical Overview, set of
  Domain-level Architecture Design Documents UML
  Model
• Non Functional Requirements (NFRs)
• Report on identified NFRs covering all EATM
  Domains
• Mapped to the Logical Architecture (on going)
• Stakeholder Test-cases Transition Plans
• Support to AENA, ATSA, DFS, DSNA, ENAV, NATS,
  MUAC, (CEATS)
• Architecture Evolution Plan

5
OATA Phase 2 Main Studies

• Cross-Domain Synchronisation Mechanisms Study
• Investigating SWIM technological options
• Avionics Study
• Avionics Roadmap for 2007, 2011 and 2020
• Avionics Logical Architecture for 2011
• Institutional Constraints Study
• Study on Military aspects (technical and
  operational)
• Validation
• Methodology and Plan developed
• Pilot and full validation exercise planned during
  2006
• Safety
• Methodology, Policy and Plan developed
• Safety Assessment planned during 2006

6
OATA Co-operation with EUROCAE
SESAR Definition Phase
Concept
Operational Scenarios Use Cases
OATA project
WG69 (CDM)
Logical Architecture
WG61 (ATC)
System Architecture Detailed Requirements (inclu
ding IRD)
WG59 (FO)
Pre-operational tests

• The system development views are different
• Phase of the life-cycle which is covered
• Functional scope
• Timeframe / applicability

7
OATA Cluster Overview Iteration 8
ATM Operations
En-route/APP ATC
Airport Operations
Airspace Organisation Management
ATFCM
Airspace User Operations
Aerodrome ATC
Air Surveillance
Ground Surveillance
ATM Support
Communications and Distributed System Services
Meteo
Aircraft Navigation
Aircraft Surveillance
Network
Route
Aerodrome
Airspace
Aircraft
Aeronautical Information Management
Flight
ATM Shared Elements
8
OATA Cluster Overview Iteration 8
WG 61 AHLM project
WG 61 VALUE project
WG 69 AAM project
ATM Operations
En-route/APP ATC
Airport Operations
Airspace Organisation Management
ATFCM
Airspace User Operations
Aerodrome ATC
Air Surveillance
Ground Surveillance
En-route/APP ATC
Air Surveillance
Airport Operations
Airspace User Operations
Aerodrome ATC
ATM Support
Communications and Distributed System Services
Meteo
Aircraft Navigation
Aircraft Surveillance
Network
Route
Aerodrome
Airspace
Aircraft
Aeronautical Information Management
Flight
Flight
ATM Shared Elements
WG 59 FOIPS projectNB different project
timescales gt multiple alignments required
9
Scope of Flight Object Specifications
OATA
aspects exchanged between ACCs
aspects specific to 1 domain
FOIPS
Domain 1
ACC 1
Other System
Domain 2
Other ACC
Domain 3
aspects shared by some domains
aspects shared by all domains
aspects exchanged between ACC and other systems
10
Whats Currently in Shared Flight?
11
Other (Non-Shared) Aspects of Flight
12
What about SWIM?
13
Infrastructure for Information Sharing (1)
Eurocontrol SWIM Framework
Aspects to address
Information Management Levels
e.g. security, ownership
1 Meta Information Management
A Legal
B Institutional
C Business
D Organisational
E Operational
F Technical
common understanding
2 Model (Data Standardisation) Management
3 Name Management
4 Identity Management
middleware
5 State Management
6 Copy Management
e.g. networks, protocols
7 Physical Data Distribution Management
14
Infrastructure for Information Sharing (2) - OATA
Cross-Domain Synchronisation Study

• Main Objective Technological Options for G/G
  and A/G Information Sharing
• Flight Data case study
• Conclusions
• G/G Technology is there today, it just needs to
  be applied!
• ORB based Middleware and DB Platforms
• Web technology based on HTTP and XML
• GRID Computing for High Performance Integrated
  IT-Services
• A/G Technology is lacking performance today
• Advanced Technology to be developed
• Significant Constraints exist today
• Non-Technical Areas needing Special Attention
• Institutional, Legal, Operational, Business
  Issues
• Report available on request

15
Infrastructure for Information Sharing (3) AP4
Collaboration on SWIM

• System-Wide Information Sharing framework IM
  services related to interoperability
• Registration service
• Discovery service
• Authentication service
• Certification service
• Identity service
• Lessons learned from other sectors
• Criteria to assist in development of SWIM
  migration Roadmap

16
Summary

• Flight Object is within the scope of OATA
• OATA is collaborating with EUROCAE WGs
• OATA Flight and FOIPS have different scopes
• functionally
• development lifecycle
• Industry will ensure consistency
• Initial activities on SWIM services have been
  started