Presented to: By: FAA Aeronautical Information Management Date: March 23, 2010 Federal Aviation Administration Federal NOTAM System (FNS) AIXM 5.1 XML

Presented to:

By: FAA Aeronautical Information Management

Date: March 23, 2010

Federal AviationAdministrationFederal NOTAM

System (FNS)

AIXM 5.1 XML Developers’ Seminar #5

Eurocontrol

2Federal AviationAdministration

Federal NOTAM System (FNS)March 23, 2010

Federal NOTAM System (FNS)

• Overview of FNS– Concept

• FNS Prototype Applications– Approach and Description– Technical Use of AIXM

• Other FAA AIM Initiatives with AIXM



What is FNS?

• FAA Concept– Enabling digital entry, evaluation, and dissemination of aeronautical

information and improving customer’s ability to manage NOTAMs– Implementing Business Process/Workflow to improve data integrity,

management oversight, and reduce the level of effort to manage and validate aeronautical data

– Ensuring delivery by tracking acknowledgements of disseminated NOTAMs and ensuring receipt by operational personnel at NAS facilities.

• AIM Modernization Segment 1– Anticipated Timeline

• 2011 - 2015– Outcome: fully digitized NOTAMs, transition from legacy system and

adoption of ICAO



New Concept of OperationsFNS

AIM

DATALINK

Originator

Validate and Publish by FAA

Integrated permanent and temporary information

Computer readableElectronic distribution to customers

Originate NOTAMs at the Source

Digital Capture (AIXM via scenario

templates)

Web

Web service (AIXM)Federal NOTAM System

Web PageService (AIXM)Legacy Formats



FAA NOTAM Policy

• Part of the FNS initiative at the FAA includes updating the FAA NOTAM policy

• Anticipated timeline for policy changes– FAA 7930.2M Change 2:

November 2010

– FAA ICAO Policy: August 2011

• FAA adoption of ICAO format



FNS Prototype• FNS addresses the collection, processing, and

distribution of NOTAM information

AIM

DATALINK

Originator

NOTAM Search ATCTracking of NOTAM

acknowledgement in an ATC environment

NOTAM SearchPublic search site

NOTAM ManagerDirect entry of NOTAMs at their origination

and processing

Web

Web service (AIXM)Federal NOTAM System

Web PageService (AIXM)Legacy Formats



NOTAM Manager (NM)



NOTAM Manager (NM)



NOTAM Manager (NM)



NOTAM Manager (NM)



FNS Approach: Scenarios

• What is a scenario?– A scenario describes the NOTAM condition or event

that is being reported– A scenario is applied to a feature

Example:

!EFD 03/020 EFD RWY 17R TDZ LGTS OTS



Scenario Mapping to AIXM

• Map every element of each scenario to AIXM 5.0 feature attributes

• Must identify any gaps in the core AIXM model– Gap analysis will lead to an extension to AIXM

Example:

RWY designator type Intensity status

aixm:RunwayDirectionLightSystem/aixm:timeSlice/aixm:RunwayDirectionLightSystemTimeSlice/aixm:operational status

aixm:RunwayDirectionLightSystem/aixm:timeSlice/aixm:RunwayDirectionLightSystemTimeSlice/aixm:intensityLevel

aixm:RunwayDirectionLightSystem/aixm:timeSlice/aixm:RunwayDirectionLightSystemTimeSlice/aixm:position

aixm:RunwayDirection/aixm:timeSlice/aixm:RunwayDirectionTimeSlice/aixm:designator



Approach: Dynamic Database

• The logical AIXM model (UML) is implemented as a relational model with implementation related changes.

• NOTAM submissions in AIXM will be consumed using the XPATH values for a given scenario. – For distribution, AIXM will be generated based on

metadata of the data model including relationships.• This is an ongoing initiative



Approach: AIXM Temporality

• FNS database designed to fully implement the temporality model

• All NOTAMs are stored as temp (temporary) delta's in the relational data model



FNS AIXM Extension

• Currently developing an AIXM schema extension to support FNS– Filling gaps identified during scenario analysis

against the AIXM model

• Expected outcome – Formalized schema for System Interface

documentation



FNS AIXM Extension Examples

• Airport Beacon/Surface Contamination– Issues will be resolved with AIXM 5.1 implementation

• Runway Lights Obscured– !SVA 02/001 SVA RWY 5/23 RWY LGTS OBSC SOUTH SIDE WEF

0902062026

RWY designator LGTS OBSC obscuredLightsSide

obscuredLightsSide: LEFT, RIGHT, BOTH, OTHER

However, FAA uses cardinal direction (NORTH, SOUTH, EAST, WEST, etc.)



NOTAM Search ATC (NSATC)




• Users can search on:– Locations using airport ID

– Accountability

– Geographic Location• Within a specified radius of a

Lat/Long• Within a specified radius of a

designator

• Find a NOTAM based on NOTAM number or condition




• Users can view NOTAM details such as:– NOTAM #– Effective date/time– Facility– Class– Status– Translations



Approach: Search Distribution

• Currently ATC search is a user-interface based web-application that communicates with the database through a data access object layer.

• Future capability to add a WFS layer to provide system interface capability for search– Move toward compliance with OGC web standards



FNS Field Tests

• Purpose: Live operational test to receive feedback on the prototype systems

• NOTAM Manager– Schedule: 12 airports

over the next year • Atlantic City (ACY) first

airport in Spring 2010

• NOTAM Search ATC– Schedule: 3 ATC

facilities over the next six months

NM test site

NSATC test site



FNS Next Steps

• Continue and evaluate the field tests• Update prototype applications to meet

anticipated changes in policy• Migrate to AIXM 5.1



FNS Prototype Demo

• NOTAM Manager• NSATC



Long-term Goals

• Data management– Single authoritative source for static and dynamic data sources– Integration with other systems (AGIS, NASR, SAMS, etc.)

To-Be 2014 To-Be 2018



Other AIM Projects Implementing AIXM

• Airports GIS• ADAM

– SAA Management– CARF

• SOP/LOA



Airports GIS

• Deployed prototype for Web services (WMS, WFS, WCS)

• Deployed prototype for AIXM Web services– Airport data exposed as AIXM 5.0 with plans to upgrade to

AIXM 5.1 now that it is officially released.

– The airport data returned always includes an AirportHeliport element - the data in this element comes from NASR. If Airports GIS has survey data for an airport, we add additional elements (e.g. Runway, TaxiwayElement).



Sample WMS Data for DFW

Terminal Area Chart Data

Topographic Data



Sample AIXM Data for CLMPort Angeles, WA – William Fairchild International Airport



Airports GIS (future plans)

• Test WMS, WFS, WCS, and AIXM Web services

• Update compliance to AIXM 5.1– AIXM Database Model

• Coordination between AGIS and FNS to provide a single source of static airport data for FAA AIM



Questions?

• Contact information:– Brett Brunk, FAA, AIM Manager of Architecture and Planning

• [email protected]

– Navin Vembar, FAA, AIM Enterprise Architect• [email protected]

– Jennifer Bewley, CNA, Research Analyst• [email protected]

• FNS Website– http://notams.aim.faa.gov



AIXM Temporality: Example



AIXM Temporality: Example•<?xml version="1.0" encoding="UTF-8"?> < fns:FNSMessage gml:id =" ID_5 " xsi:schemaLocation =" http://www.faa.gov/aim/fns/1.0 FNS_Messages.xsd " xmlns:fns =" http://www.faa.gov/aim/fns/1.0 " xmlns:gml =" http://www.opengis.net/gml/3.2 " xmlns:xsi =" http://www.w3.org/2001/XMLSchema-instance " xmlns:aixm =" http://www.aixm.aero/schema/5.1 "> < fns:hasMember > < aixm:VerticalStructure gml:id =" _1999AGL "> < aixm:timeSlice > < aixm:VerticalStructureTimeSlice gml:id =" ID_3 "> < gml:validTime /> < aixm:interpretation > TEMPDELTA </ aixm:interpretation > </ aixm:VerticalStructureTimeSlice > </ aixm:timeSlice > </ aixm:VerticalStructure > </ fns:hasMember > < fns:hasMember > < fns:NotamRequest gml:id =" ID_2 "> < fns:timeSlice > < fns:NotamRequestTimeSlice gml:id =" ID_1 "> < gml:validTime > < gml:TimePeriod gml:id =" ID_4 "> < gml:beginPosition > 2010-08-13T12:08:00 </ gml:beginPosition > < gml:endPosition > 2010-08-15T12:08:00 </ gml:endPosition > </ gml:TimePeriod > </ gml:validTime > < aixm:interpretation > TEMPDELTA </ aixm:interpretation > < fns:scenarioID > 1005 </ fns:scenarioID > < fns:requestAction > CREATE </ fns:requestAction > </ fns:NotamRequestTimeSlice > </ fns:timeSlice > </ fns:NotamRequest > </ fns:hasMember > </ fns:FNSMessage >

Documents

Presented to: By: FAA Aeronautical Information Management Date: March 23, 2010 Federal Aviation Administration Federal NOTAM System (FNS) AIXM 5.1 XML