AIXM and Instrument Flight Procedures Automation

1
AIXM and Instrument Flight Procedures Automation
2
Instrument Flight Procedures Automation (IFPA)

• Capability to design all types of flight
  procedures including en route airways, area
  navigation (RNAV) airways, standard terminal
  arrival routes (STARs), precision instrument
  approaches, and standard instrument departures
  (SIDs).
• Capability to store coded instrument flight
  procedures.
• Capability to communicate flight procedure
  information to aircraft flight management system
  (FMS)/multi-mode radio (MMR) manufacturers.
• Capability to evaluate impacts on stored
  instrument procedures.
• Capability to determine the impact of existing or
  proposed obstacles on instrument flight
  procedures.
• Capability to provide metrics that track AVN work
  processes.
• Capability to provide a means for proponents to
  check status and procedure publication date of
  requested instrument flight procedures.
• Capability to access airport, runway,
  navigational aids (Navaids) and obstacle data
  needed for the development and inspection of
  flight procedures.

• Capability to provide future status and multiple
  pending statuses for each piece of data.
• Capability to integrate systems across all AVN
  organizations to eliminate manual effort and
  duplication of data.
• Capability to integrate with external agency and
  non-agency systems in a secure manner.
• Capability to coordinate instrument flight
  procedure requests and communicate implementation
  requests with appropriate FAA and other entities.
• Capability to support NOTAM development.
• Capability to support environmental impact
  assessments.
• Capability to meet future instrument flight
  procedure demands identified in the 1995 NAS
  Architecture 2.

3
Data Exchange Integration for IFPA
4
Military Integration for IFPA
5
IFPA Products

• 8260 Forms (Rule making documents)
• Flight Inspection Documents
• Aeronautical Charts
• Data coding for FMS and MMR

6
IFPA Messages
7
IFPA Messages

• Request Messages
• WFS (getFeature, getObject, etc.)
• Filters
• Response Message
• WFSFeatureCollection
• Custom Application Schema
• Fault errors
• WFS (transaction insert, update, delete)

8
IFPA Request
ltwfsGetFeature service WFS version
1.1.0 resultType results outputFormat
text/xml subtypegml/3.1.1 traverseXlinkDepth
0gt ltwfsQuery handle 123 typeName
aixmAerodromeHeliportgt ltogcFiltergt ltogcBBO
Xgt ltgmlEnvelope srsNameWGS84gt ltgmllo
werCornergt13.0983 31.5899lt/gmllowerCornergt lt
gmlupperCornergt35.5472 42.8143lt/gmlupperCornergt
lt/gmlEnvelopegt lt/ogcBBOXgt lt/ogcFiltergt
lt/wfsQuerygt lt/wfsGetFeaturegt
9
IFPA Messages

• Response Message
• Custom messages extending AIXM

10
AIXM Data Products

• Feature/Object Extensions
• Data Types Extensions
• Codelist Extensions
• Application Schemas

11
Basic Principles of Application Schemas

• Basic principles that regulate Application
  Schemas
• An extension of an existing AIXM Feature should
  remain valid against the definition of the core
  AIXM XSD element with the same name
• An additional feature shall follow the core AIXM
  modeling conventions (stereotypes, naming, data
  types, associations, etc.)
• New stereotypes for collections and choices have
  been added for the message structure

12
Extending AIXM

• Create a new package under the Data Products
  package.
• Set XSD tool attributes
• Create Sub packages
• Feature/Object Extensions
• Data Types Extension
• Application Schema (Message package)

13
XSD Specifications

• The Community of Interest will define the Target
  Namespace and Prefix which are used when
  generating the XML Schema
• Element and Attribute Form Defaults are set to
  unqualified and qualified respectfully
• For ease of file naming, the Generate Filename
  property is overridden to provide a consistent
  file name.

14
Feature/Object Extensions (UML)

• The extension class stereotype must be
  ltltextensiongtgt
• The class name for the extension must match the
  class you are extending
• The extension class must be a specialized class
  extending the matching base class
• The extension class attributes are added to the
  extension class the same as they would a regular
  AIXM class

15
Feature/Object Extensions (XML)

• The ltclassnamegt ExtensionProperyGroup contains
  the properties (elements and relationships) of
  the Extension
• The ltclassnamegt ExtensionType element is
  generated as a XMLSchema ltcomplexType.gt and
  extends base type aixmAbstractExtensionType
• The ltclassnamegt Extension element is generated as
  a XMLSchema ltelementgt

16
Data Type Extensions

• To add new data types create a second
  sub-package, the data types extension package,
  containing any new data types needed
• It is not possible to extend ltltenumerationsgtgt or
  ltltdatatypegtgt classes. Only ltltcodelistgtgt may be
  extended

17
Codelist Extensions

• Extend a codelist by creating a class with
  the same name as the codelist and giving it a
  stereotype ltenumerationgtgt.

18
Fix Holding Data
19
Fix Holding Data Record
20
File Imports Includes

• Files within the same namespace should be
  included
• Files external to the namespace should be
  imported
• The path is configured to match the directory
  structure of the UML Model

21
Application Schema (XML)

• The ltclassnamegtCollectionPropertyGroup is
  generated as a XMLSchema ltcomplexTypegt, which
  extends gmlAbstractFeatureMemberType, and
  includes a ltchoicegt between all of the features
  it is pointing to

22
Application Schema (XML)

• The ltclassnamegtMessagePropertyGroup is
  generated as a XMLSchema ltgroupgt, which contains
  the properties (elements and relationships) of
  the Message.

23
Application Schema (XML)

• The ltclassnamegtMessageType element is
  generated as a XMLSchema ltcomplexType.gt and
  extends base type aixmAbstractAIXMMessageType.

24
Application Schema (XML)

• The ltclassnamegtMessage element is generated
  as a XMLSchema ltelementgt. The associations are
  treated as objects. They are included in the
  schema.

25
WFS (transaction insert, update, delete)

• WFS Insert uses FeatureCollection
• WFS update designed to send property to be
  updated and a filter to specify the feature being
  updated

26
IFPA Request
ltUpdate typeName"aixmAirspaceUsage"gt -
ltPropertygt   ltNamegtaixmtimeSlicelt/Namegt -
ltValuegt - ltAirspaceUsageTimeSlicegt -
ltgmlvalidTimegt - ltgmlTimePeriodgt  
ltgmlbeginPositiongt2006-03-15T000000lt/
gmlbeginPositiongt  
ltgmlendPosition indeterminatePosition"unknown"
/gt   lt/gmlTimePeriodgt   lt/gmlvalidTim
egt   ltinterpretationgtBASELINElt/interpretationgt
  lt/AirspaceUsageTimeSlicegt -
ltAirspaceUsageTimeSlicegt - ltgmlvalidTimegt -
ltgmlTimePeriodgt  
ltgmlbeginPositiongt2006-07-24T090000lt/gmlbeginP
ositiongt   ltgmlendPositiongt2006-0
7-24T150000lt/gmlendPositiongt  
lt/gmlTimePeriodgt   lt/gmlvalidTimegt  
ltinterpretationgtTEMPDELTAlt/interpretationgt  
ltsequenceNumbergt1lt/sequenceNumbergt  
lt/AirspaceUsageTimeSlicegt   lt/Valuegt  
lt/Propertygt - ltogcFiltergt   ltogcFeatureId
fid"A00002" /gt   lt/ogcFiltergt   lt/Updategt
27
Questions?
28
Designated Point (Fix) Extensions
29
Designated Point (Fix) Data Type Extensions
30
(No Transcript)
31
(No Transcript)