Download presentation
Presentation is loading. Please wait.
1
Federal NOTAM System (FNS)
AIXM 5.1 XML Developers’ Seminar #5 Eurocontrol
2
Federal NOTAM System (FNS)
Overview of FNS Concept FNS Prototype Applications Approach and Description Technical Use of AIXM Other FAA AIM Initiatives with AIXM
3
What is FNS? FAA Concept AIM Modernization Segment 1
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 Outcome: fully digitized NOTAMs, transition from legacy system and adoption of ICAO
4
New Concept of Operations FNS
DATALINK Web AIM Web Page Service (AIXM) Legacy Formats Web service (AIXM) Originator Federal NOTAM System Originate NOTAMs at the Source Digital Capture (AIXM via scenario templates) Validate and Publish by FAA Integrated permanent and temporary information Computer readable Electronic distribution to customers
5
FAA NOTAM Policy Part of the FNS initiative at the FAA includes updating the FAA NOTAM policy Anticipated timeline for policy changes FAA M Change 2: November 2010 FAA ICAO Policy: August 2011 FAA adoption of ICAO format How exactly are the translations done? are you using xslt? Not in the current version. The current version uses a simplistic approach of using templates and replacing the variable values. But it also supports case statement and preliminary algebraic calculations.
6
NOTAM Search Public search site
FNS Prototype FNS addresses the collection, processing, and distribution of NOTAM information DATALINK Web AIM Web Page Service (AIXM) Legacy Formats Web service (AIXM) Originator Federal NOTAM System NOTAM Manager Direct entry of NOTAMs at their origination and processing NOTAM Search ATC Tracking of NOTAM acknowledgement in an ATC environment NOTAM Search Public search site [may be able to better display this concept graphically Collection/processing – NM Distribution – NSATC/NS]
7
NOTAM Manager (NM)
8
NOTAM Manager (NM)
9
NOTAM Manager (NM)
10
NOTAM Manager (NM)
11
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
12
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:RunwayDirection/aixm:timeSlice/aixm:RunwayDirectionTimeSlice/aixm:designator aixm:RunwayDirectionLightSystem/aixm:timeSlice/aixm:RunwayDirectionLightSystemTimeSlice/aixm:position aixm:RunwayDirectionLightSystem/aixm:timeSlice/aixm:RunwayDirectionLightSystemTimeSlice/aixm:intensityLevel aixm:RunwayDirectionLightSystem/aixm:timeSlice/aixm:RunwayDirectionLightSystemTimeSlice/aixm:operational status
13
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 Dynamically driven template creation Stored in AIXM based data model driven by scenarios
14
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 Transition to describing the distribution of NOTAMs
15
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
16
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 obscuredLightsSide: LEFT, RIGHT, BOTH, OTHER However, FAA uses cardinal direction (NORTH, SOUTH, EAST, WEST, etc.)
17
NOTAM Search ATC (NSATC)
18
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
19
NOTAM Search ATC (NSATC)
Users can view NOTAM details such as: NOTAM # Effective date/time Facility Class Status Translations
20
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
21
FNS Field Tests NM test site NSATC test site 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
22
FNS Next Steps Continue and evaluate the field tests
Update prototype applications to meet anticipated changes in policy Migrate to AIXM 5.1 FNS Demo
23
FNS Prototype Demo NOTAM Manager NSATC
24
Long-term Goals Data management
To-Be 2014 To-Be 2018 Data management Single authoritative source for static and dynamic data sources Integration with other systems (AGIS, NASR, SAMS, etc.) Pic- screen shots from aaron
25
Other AIM Projects Implementing AIXM
Airports GIS ADAM SAA Management CARF SOP/LOA
26
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).
27
Sample WMS Data for DFW Topographic Data Terminal Area Chart Data 27
28
Sample AIXM Data for CLM
Port Angeles, WA – William Fairchild International Airport 28
29
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
30
Questions? Contact information: Brett Brunk, FAA, AIM Manager of Architecture and Planning Navin Vembar, FAA, AIM Enterprise Architect Jennifer Bewley, CNA, Research Analyst FNS Website
31
AIXM Temporality: Example
Transition to describing the distribution of NOTAMs
32
AIXM Temporality: Example
<?xml version="1.0" encoding="UTF-8"?> < fns:FNSMessage gml:id =" ID_5 " xsi:schemaLocation =" FNS_Messages.xsd " xmlns:fns =" " xmlns:gml =" " xmlns:xsi =" " xmlns:aixm =" "> < 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:NotamRequest gml:id =" ID_2 "> < fns:timeSlice > < fns:NotamRequestTimeSlice gml:id =" ID_1 "> < gml:validTime > < gml:TimePeriod gml:id =" ID_4 "> < gml:beginPosition > T12:08:00 </ gml:beginPosition > < gml:endPosition > T12:08:00 </ gml:endPosition > </ gml:TimePeriod > </ gml:validTime > < fns:scenarioID > 1005 </ fns:scenarioID > < fns:requestAction > CREATE </ fns:requestAction > </ fns:NotamRequestTimeSlice > </ fns:timeSlice > </ fns:NotamRequest > </ fns:FNSMessage > Transition to describing the distribution of NOTAMs
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.