Aeronautical Information Management Developments and activities

1
Aeronautical Information ManagementDevelopments
and activities
RTCA SC 206 Washington, July 2005

• Presented by
• Ana Paula Frangolho
• EUROCONTROL
• Email ana-paula.frangolho_at_eurocontrol.int

2
Drivers for change

• ATM dependent upon safe and efficient global
  Aeronautical Information Management
• ATM reliant on high quality data
• Need to make the transition to a fully digital,
  real time, accredited and secure aeronautical
  information environment
• Move from product centric provision of AIS to
  holistic, data oriented approach

3
Progress DevelopmentsEUROCONTROL

• EAD
• AICM/AIXM
• xNOTAM
• Airport Mapping Modelling
• AIM Models
• Data Link Strategic context
• Applications/trials and studies
• Conclusions

4
European AIS Database - EAD Objectives

• Improve the safety and cost effectivenessof air
  navigation by
• Ensuring the quality of aeronautical information
• Enhancing accessibility to and availability of
  aeronautical information
• European Solution to a European problem

5
The EUROCONTROL Solution

• A European AIS Database
• Which
• 1. Provides a repository of validated dynamic and
  static aeronautical information and of
  publications
• 2. Supports and facilitates maintenance,
  publication, and timely distribution of validated
  aeronautical information
• 3. Improves the current operational structure of
  AIS
• 4. Relies on a standard interface for the
  exchange of aeronautical information

6
NOTAM
EAD Applications
AIS Office Data Provider
Data User
NOTAM queries
NOTAM creation
INO
PIB

• Static Data

Static Data input
Static Data Retrieval
SDO
Library of AIPs/Charts
AIP Production
Browsing AIP / Charts
Chart Production
PAMS
7
EAD Data Flow
Data Provider
Data User
Public User
NOTAM
Static Data
AIP
The EAD performs coherence checking of the data
and then makes a consistent view available to the
Users of the Data.
Data Providers create, maintain and use
Aeronautical Information available through the
EAD.
8
EAD Data Coverage

• World wide NOTAM
• Static Data
• World wide area
• Static data set necessary for
• NOTAM validation and PIB generation
• ECAC Area
• Complete static data set based on the AIXM
• Aeronautical Information Publications, SID/STAR
  Procedures, Traffic Flow restrictions
• AIP Publication
• ECAC Area
• AIP, AIP Amdt, AIP Supplement, AIC and Chart

9
The Enabler AICM/AIXM

• Aeronautical Information Conceptual Model (AICM)
• September 1996, drafting group created
• October 1997, AICM Edition 1.0
• Based on
• ICAO SARPS
• real AIP
• ARINC 424
• Entity-Relationship methodology
• Aeronautical Information Exchange Model (AIXM)
• Derived from AICM
• October 1997, start work
• March 1998, first draft
• Since December 2004 version 4.0
• AIXM Change Control Board
• Controls the evolution of AIXM and related
  specifications
• Includes ECAC States, Japan, Russia, Australia
• USA, EUROCONTROL Agency and Industry

Ed 4
Airport Mapping
Vectorial Charts
xNOTAM
10
AICM/AIXM - implementations

• European AIS Database (EAD)
• AICM - data model for the central database
• AIXM - exchange format (input/output)
• Local databases in ECAC
• Slovakia, Norway, Switzerland, Czech Rep.,
• International adoption
• US, Japan, Australia, Peru, Egypt...
• Support at the ICAO Air Navigation Conference of
  2003
• Commercial products reasons to use AIXM
• XML industry standard format
• Freely available, easy to re-use (extensibility)
• Validated by implementation (EAD)

11
AIXM Application - EAD
http//www.eurocontrol.int/ead
AIXM reality check!
AIXM, ARINC 424
AIXM
12
One day, soon
NOTAM (TWY closed)
AIRPORT DATA
Need for fully computer interpretable real-time
updates
AF 375
Taxi Routing
13
NOTAM limitations by example

• TWY closure
• Today, published as NOTAM
• A0874/03 NOTAMN
• Q) EBBU/QMXLC/IV/M/A/000/999/5054N00429E005
• A) EBBR
• B) 0308250500 C) 0310271600
• E) TAXIWAYS OUTER 7 AND E6 CLSD
• Not possible for a computer to identify
  automatically which TWY is closed
• NOTAM is intended to be read and understood by
  humans, not by machines
• unreliable to ask a computer to interpret the
  free text field

ltOK for computersgt
ltnot OK for computersgt
14

• Merge "static" and "dynamic" data
• single data exchange format
• describe the underlying data content
• for intelligent machine use
• equally suitable for in-flight and ground systems
• fully backward compatible with the current NOTAM
  system.
• Build on AIXM
• Proof of concept developed in 2003
• Operational concept under advanced development
• Implementation programme in ECAC start in 2006

15
AIS Office 2
AIP, charts, etc.
AIS Office 1
NOTAM
Data management
AIP, charts, etc.
NOTAM
Data management
ARO
Briefing
eAIP, iPIB Applications
NOTAM
Narrow band COM networks (AFTN)
Surface mail
16
xNOTAM - summary

• Key requirement is timeliness of data
• Present means NOTAM - Use quite restricted
• Not structured for intelligent machine use
• Risk safety critical, last information
  information to remain outside the automated data
  processing chains
• Challenge - to provide data in format suitable
  for in-flight/ground database use
• AIM Project - xNOTAM based on AIXM
• Change a data bit in a database whilstNOTAM
  compliant
• Close cooperation with FAA and NGA
• Prototype schema to be developed with FAA by end
  year (GML/AIXM)
• xNOTAM to replace current NOTAM ?
• not an objective of the xNOTAM project
• rather a logical consequence
• new products and system, xNOTAM based, will
  decrease and eventually eliminate the need for
  classical NOTAM

17
Airport Mapping Modelling
Our users are anywhere, anytime on any device
the right data at the right time in the right
place
Common requirements/standards for information
exchange gt Open (Geospatial) Interoperability
18
Airport Mapping
New/expanding requirements of Airport Mapping to
serve new functions fitted into new applications.

• Route awareness
• Position awareness
• Traffic awareness
• Deviation detection
• Incursion detection
• gt
• Airport Advanced Surface Movement Guidance
  applications increase safety and capacity levels.

19
AMDB Standardisation
Airport mapping data base (AMDB) requirements and
conceptsED99/DO272
Airport mapping interchange standards
specificationED119/DO291
Airport Mapping Exchange Model AMXM
AMDB Metadata ISO19115 Profile
Spatial Schema ISO19107
AMDB Feature Catalogue ISO19110
AMDB Application Schema ISO19109

Airport Mapping Exchange Schema
Airport Mapping Exchange Schema AMXS
AMXS-GML Schema
20
Ground and Airborne AMDB

• EUROCAE/RTCA WG44 - ED99A, ED119
• Ground AMXS (GML-OpenGIS)
• AEEC ARINC-ADB
• Cockpit ARINC 816 (Binary XML - OpenGIS)

GROUND
COCKPIT
Integrator
Originator
Cockpit
AMXS
ARINC 816
AEEC ARINC
EUROCAE/RTCA ED119/DO272
EUROCAE/RTCA ED99/DO272
OpenGIS
21
EMMA
European Commission 6th Framework

• European Movement Management by A-SMGCS
• Duration 2004 2006
• Development of onboard functions algorithms for
  runway incursion avoidance, including HMI, based
  on AMDBs

22
AIM Models

• AIXM Aeronautical Information Exchange Model
• AMXM Airport Mapping Exchange Model
• WXXM Weather Information Exchange Model
• AOXM Airport Operations Information Exchange
  Model
• ENXM Environmental Information Exchange Model

AOXM
WXXM
ENXM
AMXM
AIXMIACOBST
TERRAIN
FLTOBJECTS
?
?
Established
Taking profit of other developments
Not included in AIM Domain aero data elements
only
23
AIRPORT CDM

• Considerable work going on to enable airport CDM
• Based on the concept of collaborative information
  sharing
• Interactions information requirements (APT
  CDMTF)
• Future Systems Architecture Project (OATA)
• CFT to define UML Model for airport (recently
  launched)
• EUROCAE WG69 CDM
• Developing MASPS
• Will use UML Model to develop
• AOCM
• AOXM
• Probable outputs will include ground/air,
  air/ground and ground/ground data exchange

24
Strategic Context
ATS Domain Applications FCS
LINK 2000
CASCADE
Airborne Separation Trajectory
negotiation Autonomous Separation
Departure Clearance Digital-ATIS Oceanic
Clearance Classical Radar

• Strategic Context
• Objectives
• Scope
• Approach

ACARS
PS RADAR
Mode S
2000gt
2005 gt
2010 gt
25
CASCADE and AIS 1 FIS
AIRSPACE information D-ORIS en-route
weather info data NOTAM SIGMET PIREPS
Objectives - Improve flight safety and flight
management - Reduce aircrew and controller
workload
AIRPORT information D-OTIS D-ATIS VOLMET
NOTAM/SNOWTAM SIGMET PIREP D-RVR

• And more
• - Graphical presentation on airborne display
• - Data transfer to the FMS, optimising the flight

26
Integrated Applications
NOTAM (D-OTIS)
AIRPORT DATA (D-SIG)
ADS-B
XXXXXX
Require Compatibility and integrity of
databases Global interoperability
AF 375
Taxi Routing (D-TAXI)
27
D-OTIS Trial (1)

• From August 2005 till March
  2006
• With The whole SN BRU fleet.
• Where In BRU.
• A/C types AVRO A 320 A330
• Technology ACARS
• Consortium SITA, Belgocontrol, SN Brussels
  Airline, Systex, Blusky.
• What .see next slides

28
D-OTIS Trial (2)
OTIS SERVER
EAD
ATSU
ATIS VOLMET
NOTAM, SNOWTAM FIB
29
D-OTIS Trial (3) Notam part
Company profile
server
KEY
QUERY
EAD
30
NOTAM REFERENCE TIMES
31
FLYSAFE Project

• Funded by the European Commission
• Being undertaken by major consortium industry
  including the UK Met Office and Meteo France
• 4 Year joint effort (Feb 2005 to Jan 2009)
• Structured upon three threats
• Collision with other aircraft
• Collision with terrain and obstacles
• Adverse atmospheric conditions
• Lead to the validation of new concepts in
  collecting and presenting safety related
  information to the pilot

32
FLYSAFE overall concept
33
Conclusion

• How will the work in SC 206 take into account
  European projects ?

34
Thank you for your attention