FAA Efforts in AIXM

1
FAA Efforts in AIXM

• Projects, Lessons Learned and Questions for the
  Future

AIXM Developers Seminar
Navin Vembar Prakash Mangalathan
10/26/2009
2
Overview

• Projects using AIXM
• Airports GIS
• Digital NOTAMs
• SWIM
• SAA and CSE
• CSSD
• Lessons Learned
• Questions for the Future

3
Airports GIS

• FAAs system of record on airport survey data
• Down to the paint on the runways
• Geospatial definitions of the airport elements as
  well as high-resolution raster imagery
• Exposed through WMS and WFS
• Moving to AIXM
• Gap analysis being conducted between the current
  data model and AICM
• Will be exposing Airport data as AIXM over the
  SWIM network

4
Digital NOTAMs

• End-to-end digital definition of NOTAMs
• Input through drop-downs
• Visualization through website
• Dissemination through web services
• Exercising much of the AIXM model
• Representing NOTAM activity across the FAA using
  TEMPDELTAs

5
Digital NOTAM Architecture
6
FAAs SWIM

• FAAs System Wide Information Management is the
  agency-wide SOA
• Governance
• Technology Selection
• Guidance
• Enterprise Service Bus Selection
• IONA FUSE ServiceMix
• Productized Apache ServiceMix
• Includes Apache CXF, ActiveMQ, Camel, Fuse HQ

7
Special Activity Airspace

• One of the pilot components of the FAAs System
  Wide Information Management (SWIM) program
• SAAs are airspaces that can be turned on and off
  based on schedule, generally based on external
  factors
• E.g., Special Use Airspace, Temporary Flight
  Restrictions, Altitude Reservations

8
Special Activity Airspace, contd

• Project to define SUAs and Air Traffic Controlled
  Activity Airspace (ATCAAs) from end-to-end
• Static definition
• Using LuciadMap for editing
• Schedule management
• Status management

9
Sample SUA Data

• Cape Canaveral
• R-2932 Cape Canaveral, FL Boundaries. Beginning
  at lat. 2839'21"N., long. 8042'39"W. to lat.
  2841'41"N., long. 8034'59"W. thence 3 nautical
  miles from and parallel to the shoreline to lat.
  2825'01"N., long. 8030'29"W. to lat.
  2825'01"N., long. 8037'59"W. to lat.
  2834'01"N., long. 8039'29"W. to the point of
  beginning,. Designated altitudes. Surface to but
  not including 5,000 feet MSL. Time of
  designation. Continuous. Controlling agency. FAA,
  Miami ARTCC. Using agency. Commander, 1st Range
  Operations Squadron, Cape Canaveral AFS, FL.
  AMENDMENTS 1/20/05 69 FR 68075 (Amended) Corr 69
  FR 70887

10
Common Scheduling Enterprise

• Tied to the SAA project
• Department of Defense to FAA schedule request
• Using SAA network to define schedule requests
• Moving AIXM outside of FAA

11
Common Status and Structure Data

• Newly started effort
• Taking disparate authoritative sources across
  many systems and providing an aggregated view
  through AIXM and OGC standards
• Use Case Pilot Briefing describe all the
  features and NOTAMs that will affect a flight
  based on a filed flight plan
• Exploration will include
• Single authoritative source identification
• UUID management across multiple systems
• Creation of adapters to existing systems to AIXM
  5.1

12
Lessons Learned

• Overcoming Complexity
• Detailed Web Service Definition Descriptions or
  Interface Requirements Documents aids consumer
  and developer
• Working with developmental complexity when
  constructing systems dealing with only a specific
  subset of AIXM (e.g., SAA)
• AICM/AIXM simplifies data modeling by providing a
  largely complete model of aeronautical
  information
• Understanding the core concepts of Features and
  their Temporality is key
• Building blocks features, objects, messages,
  timeslices

13
Lessons Learned

• Binding
• Were unable to use common Java-SOAP binding
  solutions JAX-WS JAX-B
• XMLBeans works
• IONA had to develop a number of bug fixes
• Settling on a best practice for moving from AIXM
  to the in-memory model
• Seeing more and more commercial solutions
  becoming available
• Very positive

14
Lessons Learned

• XPath XQuery promotes rapid development
• Take advantage of the XLink capabilities to treat
  the XML as a database
• Avoids issues with binding
• Allows for flexible addition of new use cases
• Very important for Digital NOTAMs for example
• GeoTools
• Open Source APIs for geographic computations
• Provides for intelligent interpretation of GML
  components of AIXM

15
Lesson Learned

• Focus on development should be on native XML
  processing not Java/.NET/etc
• Use of tools such as XPath, XQuery, Schematron,
  XSLT, XForms is key for success in managing what
  appears to be a large schema from a binding
  perspective

16
Questions for the Future

• Proof of SWIM and AIXM compatibility
• XML Gateway Compatibility
• Software Capability
• How to expose AIXM to other agencies?
• As AIXM becomes pervasive in the FAA, events like
  this one will help us transition external
  consumers to using AIXM
• Aggregation through a SOA
• Draw together different data sources to single
  messages based on user need
• Software solutions DXSI? FME in pipeline?
• Data Management
• UUID Management
• Traceability
• Exposure using OGC Standards
• WFS, WFS-T, Filter