Presented to: By: Date: Federal Aviation Administration AIM – SAA and AGIS Net-Centric Demos Navin...

Presented to:

By:

Date:

Federal AviationAdministrationAIM – SAA and

AGIS

Net-Centric DemosNavin VembarKevin LewJoe Norton

May 26th, 2010

Presented to:

By:

Date:

Federal AviationAdministrationSAA Modernization

Net-centric TIM

Kevin Lew

AIM

May 26, 2010

3Federal AviationAdministration

AIM Technology Stack December 200904/18/23

Content

• Introduction to SAAs• Overview of the SAA System• Approach• Lessons Learned• Next Steps


AIM Technology Stack December 2009

Introduction to Special Activity Airspaces (SAAs)

• Special Use Airspace (SUA)– Airspace in which activities must be confined or

limitations may be imposed on aircraft, generally below en route airspace

• Air Traffic Controlled Assigned Airspace (ATCAA)– En Route airspace analogous to SUAs

• SAAs may depend on many other features– NAVAIDs, airports, runways, cities, other airspaces,

geographic features or arbitrary points



Goals for the SAA Project

• Define SUAs and ATCAAs in a consistent manner using an editing tool

• Use a Service Oriented Architecture (SOA) to distribute that data to interested users

• Manage the schedule and status of those airspaces through a SOA



The Creator/Editor Tool

• Allow a user to create and modify SAAs

• SAAs defined using AIXM 5.0




Carson MOA, NVBoundaries. Beginning at lat. 40°06'00"N., long.

117°57'33"W.; to lat. 40°06'00"N., long.118°15'04"W.; to lat. 39°57'00"N., long. 118°38'04"W.; to lat. 39°51'00"N., long.118°38'04"W.; to lat. 40°01'00"N., long. 118°15'04"W.; thence to the point of beginning.

Altitudes. 500 feet AGL to but not including FL180.

Times of use. 0715-2330 daily; other times by NOTAM.

Controlling agency. FAA, Oakland ARTCC.Using Agency. U.S. Navy, Commander, Naval

Strike and Air Warfare Center, NAS, Fallon, NV.

• Generate the SUA 7400.8 legal definition from the AIXM definition




• Using Lucy and LuciadMap v9– This version has

an extension to support for AIXM 5.0

• Users of the first release are NFDC



Static Repository

• Stores the static definitions of SAAs in AIXM 5.0

• Notifies subscribers of new SAAs created and old SAAs updated – JMS pub/sub services

• Provides the SAA definitions to users – SOAP request/response web services



Operational Repository

• Accepts schedule requests and airspace status changes – SOAP request/response

web services

• Distributes schedule and airspace status updates – JMS pub/sub services



SAA Project Web Services

JMS Schedule

topics

JMS topicSAA ID

Operational Repository

(SAMS)

Static Repository(NASR)

Operational Schedulers

(MADE, CSE)

ERAM

USNS / FNS

Others Systems

Create/Update/Retrieve “get” SAA

“get” SAA

Status Changes

Schedule Changes

Create Schedule Changes

Status & Schedule Changes

Project Repository

SAA Editor

AIXM service to be available with first release

AIXM service planned for the future

SAA Project System



Benefits

• One definitive source for SUA definitions– Currently there are multiple digital definitions for

SUAs and none accurately represent the complete SUA legal definition

• The AIXM definition of the SUA generates the legal definition

• Provide an accurate picture of SAA utilization



SWIM Integration

• The SAA project is an FAA System Wide Information Management (SWIM) implementing program.

• SWIM implementing programs use Progress FUSE products for their SOA infrastructure– ESB (based on Apache ServiceMix)– Message Broker (based on Apache ActiveMQ)– Services Framework (based on Apache CXF)– Mediation Router (based on Apache Camel)

• Able to implement AIXM 5.0 services with FUSE ESB 4.2



Next Steps for the SAA Project

• Deploy the system this year• Add support for AIXM 5.1 for the second

release• Have the Editor adopted earlier in the

workflow of designing SAAs– Military use of the Editor to define SUAs– Implement the Review and Comment System for the

back and forth dialogue and approvals of SAAs

04/18/23



Next Steps for the SAA Project

• Expand the consumers of the Operational Repository service– The Air Force’s Central Scheduling Enterprise (CSE)– Airlines– En Route Automation Modernization (ERAM)– Federal NOTAM System (FNS)

• Add other types of airspace in future releases– Altitude Reservations (AltRevs)– Temporary Flight Restrictions (TFR)

• Use Airports GIS for Airport data used in SAAs

04/18/23

Presented to:

By:

Date:

Federal AviationAdministrationAIXM Operational

Perspectives

Airports GIS (AGIS)

2010 AIXM/WXXM Conference

Joseph Norton, CNA

April 18, 2023



Airports GIS (AGIS)• Objectives

– Create a single integrated web application for the collection of survey data

– Establish guidance and standards for airport survey data collection

– Promote productivity and fiscal responsibility

– Improve existing programs – data-centric support for and production of digital products

– Deliver static airport information through enterprise services



A Collaborative Partnership• Air Traffic Organization (ATO)

– System engineering– Data management, processing, and distribution

• Office of Airports (ARP)– Airport data collection and standards– Airport design, equipment, and operational

standards– Certification and inspection of air carrier airports

• National Geodetic Survey– Inter-agency agreement to perform Independent

Validation & Verification (IV&V)



Supporting NextGen Objectives• Provide SWIM-compliant digital enterprise

aeronautical information services to support shared situational awareness

• NextGen operational improvements– Provide secure on-demand airport and constraint information – Provide consistent and managed airport data to airport users

during airport operations

• Surface situation information

• Low visibility surface operations

• Improve runway safety awareness for pilots and controllers

• Surface traffic management

• Improved management of arrival/surface/departure flow operation



High-Level Operational Concept

AIM

Airport Survey DataAC 150/5300

Office of AirportsAirport Data Changes

Digital Products

Static Airport Data

AGIS

• OE/AAA• SDAT• SAA• FNS• NFPO

• SWIM• TFDM• ERAM• TMA/TBFM• TDDS• RTCA



Airports GIS (AGIS) System

• Web application interface for survey data collection, GIS viewing, digital products, and airport data maintenance

• SWIM compliant service interface based on OGC standards

• Centralized database



Survey Data Collection• FAA Advisory Circulars 150/5300 Series

– 16, Geodetic Control– 17, Imagery– 18, Survey Data Collection

• Provide standardized data collection guidance and a common view of airport survey data

• Current efforts to make data model more AIXM compliant

• Current AGIS survey projects– 800+ airport surveys– 37 completed surveys (13 new surveys, 24 existing

surveys) (as of May 3, 2010)



Data Distribution using OGC Web Services• Data Layer

– AIM database and external databases

• Service Layer– Java-based GeoServer

platform – Strictly adheres to OGC

standards (e.g., WMS, WFS, WCS, KML)

• Data Users– Data consumers/producers– Data stewardship– Custom adapters to

support legacy systems



AIXM Web Services• Web Services

– WSDL (Web Service Description Language)– REST (Representative State Transfer)

• Currently, airport data is provided as AIXM 5.1– Approximately 800 airports – National Geospatial-Intelligence

Agency (NGA)– NASR data– Convert 3D to 2.5D– Simplified XLink – internally refer to gml:id

• In the future, airport data will be provided through WFS (WFS 2.0)– Survey data will be integrated with NGA baseline data



Support Tactical Airport Operations• Provide static airport

configuration information to support operations in the Terminal and En Route environments– Airport/runway configurations– Taxiway routing– Airport base data for moving

map displays• Airport Mapping Database

(AMDB)



Integration with Industry

• AMDB requirements• RTCA data link applications (DO-272) –

performance and operations– D-(Aerodrome) NOTAMs– D-Taxi– D-Traffic– D-Lighting

• Aeronautical Radio, Incorporated (ARINC)– Airlines Electronic Engineering Committee (AEEC)



Integration with Federal NOTAM System (FNS)

Closure of TWY A between RWY 13/31 and Approach RWY End 22 at ACY



Integration with Special Activity Airspace (SAA)

Design of an SAA around a VORTAC near GRB



Status & Next Steps

• Prototype OGC and AIXM web services• Demonstrate enterprise airport data services (End June

2010)• Deliver digital airport information to support situational

awareness – airport configuration (End September 2011)

• Airport survey data collection– Support improvement of data standards, workflow, and automatic

validation– Phase I (FY2009) – Southwest Region – 6 airports and ATL– Phase II (FY2010) – Remaining Regions – 30 airports– Phase III (FY2010–25) – Incremental projects

• Electronic Airport Layout Plans (eALP)– Beta (CY10–11) and Release (CY12)



Contact Information

Joseph NortonResearch Analyst

CNA Analysis & Solutions

Aeronautical Information Management (AIM)

(202) 580-7497

[email protected]

Airports GISWeb Application – http://airports-gis.faa.gov

Web Services – https://agisdemo.faa.gov/airportsgis/services



Summary

• AGIS is a single access point for the collection of airport survey data; continually working to improve workflow and data standards

• AGIS uses a data-centric approach to support the aeronautical community– Support distribution of airport data using a standardized format;

ICAO and international standards – AIXM and OGC web services

– Provide static airport data to support dynamic operational environment of NextGen – airport configuration, airport status, taxiway routing

• Integrate with other FAA and AIM systems, and industry

Presented to: By: Date: Federal Aviation Administration AIM – SAA and AGIS Net-Centric Demos Navin...

Documents

Transcript of Presented to: By: Date: Federal Aviation Administration AIM – SAA and AGIS Net-Centric Demos Navin...