Federal Aviation
Administration

Flight Information
Exchange Model

Presented to:
Presented by:
Date:

EIWAC 2013
Midori Tanino, FAA
February, 2013

Globalization* CDM Logo
Federal Aviation
Administration2

State of the System (from SWIM presentation)- More point-to-point
unique interfaces- Costly development, test,
maintenance, CM- New decisions linked toold data constructs- Cumbersome data
access outside the NAS

Today
HostETMS

WARP
IDS/
ERIDS

ASDE

ATOP

ERAM
STARS/ARTS/TAMRBusiness as UsualEnterpriseManagement

CIWS
FAA Systems

TMA
TFM

ERAM

InterAgency- Existing point-to-point
hardwired NAS- Unique interfaces, custom
designs

SWIM Compliant
Non-Government
Systems

FTI

SWIM Compliant
Government
Systems

LEGEND
DOTS

SWIM Segment 1
SWIM Future Segment
SWIM Adapter

Federal Aviation
Administration

33

Conceptual Overview of Operation
Publishers/
Subscribers

TerminalControllers
En RouteControllers

Services for Data
Exchange

Standards for Data
Exchange

Non-FAA Users(e.g., Airlines, DoD,DHS, ANSPs)

SystemDevelopers

FAA CommandCenter

ACS

FOXS

NNEW

AIXM

FIXM

WXXM

SWIM Messaging
Infrastructure

FTI IP Backbone

Federal Aviation
Administration

4

Aviation Related Data Models• AIXM (Aeronautical Information Exchange Model)• WXXM (Weather Information Exchange Model)• FIXM (Flight Information Exchange Model)• AIDX (Aviation Information Data Exchange)

Federal Aviation
Administration

5

FIXM Overview• Flight Data Exchange among ANSPs and users• ICAO ATM Requirement and Performance Panel• ISO19103, ISO19107, ISO19108• Consists of:– Data Dictionary– UML Model– XML Schema• Architecture– Core and Extensions

Federal Aviation
Administration

6

FIXM Data Modeling Process
Data
Dictionary

knowledge

conceptualrefinement
SMEModeler

FICM
concept model

validation

logicalrefinement
improvements

Modeler/Programmer

FIXMlogical model

improvements

FIXS
physical model

physicalrefinement
Developer/Programmer
Federal Aviation
Administration

7

FIXM Release Roadmap
ReleaseTarget Release

Release Contents

ICAO 2012 ATS – FPL message
GUFI
NAS Flight Plan Data
Initial ED-133 Element inclusion

1.0

Aug 2012(completed)

▪
▪
▪
▪

1.1

Dec 2012(completed)▪

Hazardous Cargo (Dangerous Goods)▪
▪
▪

ICAO 2012 ATS (15 remaining messages)
ICAO 2012 AIDC messages
TFM (Strategic)

2.0

3.0

4.0

Aug 2013

Aug 2014

Aug 2015▪
▪
▪

TFM Data Exchange
ANSP-Airline CDM
Fleet Prioritization▪

Airport CDM▪
▪
▪

Surface data (anything not covered in Airport CDM andTFM/CDM elements)
ANSP-ANSP boundary crossing (Tactical)
4D Trajectories (1st package)▪
▪
▪

Security elements (1st package)
Unmanned Aircraft Systems (UAS)
4D Trajectories (2nd package)Federal Aviation
Administration

8

FIXM 1.0 Data Elements – Harmonization

Federal Aviation
Administration

99

Data Dictionary – Data Entry Sample

Federal Aviation
Administration

10

FIXM UML Model v1.0

Federal Aviation
Administration

11

Find FIXM at www.FIXM.aero

Federal Aviation
Administration

12

FIXM 1.0 Lessons Learned and FutureChallenges• Tight deadline• GML initially included, then abandoned• Hand crafted physical model (XML schema)• Lack of consistency with AIXM and WXXM
• Logical model massaged to comply withphysical model• Blurring between conceptual and logicalmodels• Security• Relatively closed process due to timeframe
Federal Aviation 13
Administration

13

FIXM v2.0 Development Process• ANSP Partners Expanded to include:
FAA/NextGen; Eurocontrol/SESAR; Airservices
Australia; JCAB; NAV CANADA; NATS UK• Collaboration and Transparency– Change Control Board– Alignment with other models– Working with standardization organizations– Handling of Extensions– Usage of www.FIXM.aero• Design Philosophies– FIXM 1.0 and FIXM 1.1 and FIXM 2.0 approaches

Federal Aviation
Administration

14

FIXM 2.0 Development Activities- Capabilities to Support Transparency

Once registered as a member, the user can:
1. Participate in the discussion boards
2. Access all comments for Data Dictionary and website
related.
3. Access issue tracker that manages all issues related
to Data Dictionary or website.
4. Subscribe to email notifications when documents
have been posted or updated.
(Models and Schemas will be supported in a similar
Federal Aviation 15
manner in the future.)
15
Administration

Engineering Analysis• Examined areas such as:– Globally Unique Flight Identifier (GUFI)– Flight Data Server Architecture– Transition– Compression– Data Correlation– Data Reconstruction– Data Exchange Mode
“Flight Object Engineering– Data Access Control
Analysis Report”– Data Consistencyat www.FIXM.aero– Data Customization– Data Validation– Data Discovery– Failure Modes– Messaging

Federal Aviation
Administration16

Globally Unique Flight Identifier (GUFI)••Key element for the FIXM success
GUFI Construct Requirements
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

•

Unique world-wide.
Could represent flight leg or flight plan.
Unique for given time range.
Won’t constrain number of GUFIs created in any given time period.
Constant for life-cycle of flight.
Allow any entity to create unique GUFIs.
Allow any number of entities to create GUFIs.
Allow variety of entity name formats.
Usable by human or machine.
Conform to international standards.

Sample format that would meet requirements:–––us.aal.20110210.0631.105
fr.f9893rl.20110930.1745.1
us.kzbw.20110211.1400.24
Federal Aviation
Administration

17

Globally Unique Flight Identifier (GUFI)- Architecture with GUFI
FlightOperator

ARTCC 1ARTCC 2FlightPlanning

Strategic
Planning

ERAM
FlightData
Server

TFM
FlightData
ServerFAA
GUFIService

ARTCC nConsistent,
Authoritative
Flight Plans
w/GUFIs

TFMS
TBFM

TFM n
Consistent,
Authoritative
TFM Data
w/GUFIs

Another
GUFI
Service18

Federal Aviation
Administration

18

Globally Unique Flight Identifier (GUFI)- Transition Approach
GUFI Perimeter

FLT123GUFI

AirlineGUFI-based
data
exchange

GUFI
AdaptorLegacy dataexchange

ERAM

GUFI-based
dataexchange
CentralGUFIService

GUFI-based
dataexchange

FLT123
GUFI

TFMS

GUFI
Adaptor

GUFI-based
dataexchange

Legacy dataexchange

Legacy dataexchange

AirlineNOTES:ANSP systems can be converted independently of each other, while the airline gets full benefit.
Adaptors can also be applied to data exchange between ANSP systems.

19

Federal Aviation
Administration

19

Early Adopters• FAA: Flight Data Publication Services• Airservices Australia: Operational DataServices• International Traffic Flow Management Data
Exchange (possible)
Asia/Pacific Flight Data Object Demonstration
Airservices
Australia

Notional Int’l
SWIM Enterprise

VPN

Florida NextGen
Test Bed (FTB)

FAA( facilitated by Harris Alliance)
FlightData(TFMDE)

Task K
Producers

NEMS (Alliance)

NEMS (FTB)
Task K
Consumers

Federal Aviation
Administration20

Questions?

www.FIXM.aero
Federal Aviation 21
Administration

21