Federal NOTAM System FNS AIXM 5 1 XML

  • Slides: 32
Download presentation
Federal NOTAM System (FNS) AIXM 5. 1 XML Developers’ Seminar #5 Presented to: Eurocontrol

Federal NOTAM System (FNS) AIXM 5. 1 XML Developers’ Seminar #5 Presented to: Eurocontrol By: FAA Aeronautical Information Management Date: March 23, 2010 Federal Aviation Administration

Federal NOTAM System (FNS) • Overview of FNS – Concept • FNS Prototype Applications

Federal NOTAM System (FNS) • Overview of FNS – Concept • FNS Prototype Applications – Approach and Description – Technical Use of AIXM • Other FAA AIM Initiatives with AIXM Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 2

What is FNS? • FAA Concept – Enabling digital entry, evaluation, and dissemination of

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 3

New Concept of Operations FNS DATALINK Web AIM Originator Web service (AIXM) Originate NOTAMs

New Concept of Operations FNS DATALINK Web AIM Originator Web service (AIXM) Originate NOTAMs at the Source Digital Capture (AIXM via scenario templates) Federal NOTAM System (FNS) March 23, 2010 Federal NOTAM System Web Page Service (AIXM) Legacy Formats Validate and Publish by FAA Integrated permanent and temporary information Computer readable Electronic distribution to customers Federal Aviation Administration 4

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

FAA NOTAM Policy • Part of the FNS initiative at the FAA includes updating the FAA NOTAM policy • Anticipated timeline for policy changes – FAA 7930. 2 M Change 2: November 2010 – FAA ICAO Policy: August 2011 • FAA adoption of ICAO format Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 5

FNS Prototype • FNS addresses the collection, processing, and distribution of NOTAM information DATALINK

FNS Prototype • FNS addresses the collection, processing, and distribution of NOTAM information DATALINK Web AIM Originator Web service (AIXM) NOTAM Manager Direct entry of NOTAMs at their origination and processing Federal NOTAM System Web Page Service (AIXM) Legacy Formats NOTAM Search ATC Tracking of NOTAM acknowledgement in an ATC environment NOTAM Search Public search site Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 6

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 7

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 7

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 8

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 8

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 9

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 9

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 10

NOTAM Manager (NM) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 10

FNS Approach: Scenarios • What is a scenario? – A scenario describes the NOTAM

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 17 R TDZ LGTS OTS Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 11

Scenario Mapping to AIXM • Map every element of each scenario to AIXM 5.

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: Runway. Direction. Light. System/aixm: time. Slice/aixm: Runway. Direction/aixm: time. Slice/aixm: Runway. Direction. Light. System/aixm: time. Slice/aixm: Runway. Direction. Light. System. Time. Slice/aixm: operational tion. Time. Slice/aixm: designator Runway. Direction. Light. System. Time. Slice/aixm: position Runway. Direction. Light. System. Time. Slice/aixm: intensity. Le status vel Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 12

Approach: Dynamic Database • The logical AIXM model (UML) is implemented as a relational

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 13

Approach: AIXM Temporality • FNS database designed to fully implement the temporality model •

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 14

FNS AIXM Extension • Currently developing an AIXM schema extension to support FNS –

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 15

FNS AIXM Extension Examples • Airport Beacon/Surface Contamination – Issues will be resolved with

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 obscured. Lights. Side: LEFT, RIGHT, BOTH, OTHER However, FAA uses cardinal direction (NORTH, SOUTH, EAST, WEST, etc. ) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 16

NOTAM Search ATC (NSATC) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration

NOTAM Search ATC (NSATC) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 17

NOTAM Search ATC (NSATC) • Users can search on: – Locations using airport ID

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 18

NOTAM Search ATC (NSATC) • Users can view NOTAM details such as: – –

NOTAM Search ATC (NSATC) • Users can view NOTAM details such as: – – – NOTAM # Effective date/time Facility Class Status Translations Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 19

Approach: Search Distribution • Currently ATC search is a user-interface based web-application that communicates

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 20

FNS Field Tests NM test site NSATC test site • Purpose: Live operational test

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 21

FNS Next Steps • Continue and evaluate the field tests • Update prototype applications

FNS Next Steps • Continue and evaluate the field tests • Update prototype applications to meet anticipated changes in policy • Migrate to AIXM 5. 1 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 22

FNS Prototype Demo • NOTAM Manager • NSATC Federal NOTAM System (FNS) March 23,

FNS Prototype Demo • NOTAM Manager • NSATC Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 23

Long-term Goals To-Be 2014 To-Be 2018 • Data management – Single authoritative source for

Long-term Goals 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. ) Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 24

Other AIM Projects Implementing AIXM • Airports GIS • ADAM – SAA Management –

Other AIM Projects Implementing AIXM • Airports GIS • ADAM – SAA Management – CARF • SOP/LOA Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 25

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

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 Airport. Heliport element - the data in this element comes from NASR. If Airports GIS has survey data for an airport, we additional elements (e. g. Runway, Taxiway. Element). Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 26

Sample WMS Data for DFW Topographic Data Terminal Area Chart Data Federal NOTAM System

Sample WMS Data for DFW Topographic Data Terminal Area Chart Data Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 27

Sample AIXM Data for CLM Port Angeles, WA – William Fairchild International Airport Federal

Sample AIXM Data for CLM Port Angeles, WA – William Fairchild International Airport Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 28

Airports GIS (future plans) • Test WMS, WFS, WCS, and AIXM Web services •

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 Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 29

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

Questions? • Contact information: – Brett Brunk, FAA, AIM Manager of Architecture and Planning • brett. brunk@faa. gov – Navin Vembar, FAA, AIM Enterprise Architect • navin. vembar@faa. gov – Jennifer Bewley, CNA, Research Analyst • jennifer. ctr. bewley@faa. gov • FNS Website – http: //notams. aim. faa. gov Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 30

AIXM Temporality: Example Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 31

AIXM Temporality: Example Federal NOTAM System (FNS) March 23, 2010 Federal Aviation Administration 31

AIXM Temporality: Example • <? xml version="1. 0" encoding="UTF-8"? > < fns: FNSMessage gml:

AIXM Temporality: Example • <? xml version="1. 0" encoding="UTF-8"? > < fns: FNSMessage gml: id =" ID_5 " xsi: schema. Location =" 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. w 3. org/2001/XMLSchemainstance " xmlns: aixm =" http: //www. aixm. aero/schema/5. 1 "> < fns: has. Member > < aixm: Vertical. Structure gml: id =" _1999 AGL "> < aixm: time. Slice > < aixm: Vertical. Structure. Time. Slice gml: id =" ID_3 "> < gml: valid. Time /> < aixm: interpretation > TEMPDELTA </ aixm: interpretation > </ aixm: Vertical. Structure. Time. Slice > </ aixm: time. Slice > </ aixm: Vertical. Structure > </ fns: has. Member > < fns: Notam. Request gml: id =" ID_2 "> < fns: time. Slice > < fns: Notam. Request. Time. Slice gml: id =" ID_1 "> < gml: valid. Time > < gml: Time. Period gml: id =" ID_4 "> < gml: begin. Position > 2010 -08 -13 T 12: 08: 00 </ gml: begin. Position > < gml: end. Position > 2010 -08 -15 T 12: 08: 00 </ gml: end. Position > </ gml: Time. Period > </ gml: valid. Time > < aixm: interpretation > TEMPDELTA </ aixm: interpretation > < fns: scenario. ID > 1005 </ fns: scenario. ID > < fns: request. Action > CREATE </ fns: request. Action > </ fns: Notam. Request. Time. Slice > </ fns: time. Slice > </ fns: Notam. Request > </ fns: has. Member > </ fns: FNSMessage > Federal NOTAM System (FNS) Federal Aviation 32 March 23, 2010 Administration