Presented to: By: Date: Federal Aviation Administration Web Services Implemented During System Wide Information Management (SWIM) Segment 1 AIXM/WXXM Conference

Presented to:

By:

Date:

Federal AviationAdministration

Web Services Implemented During System Wide Information Management (SWIM) Segment 1

AIXM/WXXM Conference

Jeffery L. Hobbs, FAA SWIM Implementation Lead

May 13, 2009

2 2Federal AviationAdministrationMay 13, 2009 V1.0

The “Problem”


Key Deficiencies in Current Approach

• The National Airspace System (NAS) is not an agile air traffic system

• Costs to develop, test, deploy, and support new NAS interfaces and NAS applications are too high

• Data sharing in the NAS is labor-intensive• Timely access to common data is lacking in the NAS• The underlying tools to support becoming a

performance–based organization are currently lacking


The Challenge

HostWARP

IDS/ERIDS

ATOP

CIWS

TFMTMA

STARS/ARTS/TAMR

ERAM

ASDE-X

ETMS

Inter-Agency

Today

- Existing point-to-point, hardwired NAS- Unique interfaces, custom designs

Business as Usual(NextGen without SWIM)

- More unique, point-to-point interfaces

- Costly development, test, maintenance, CM

- New decisions linked to old data constructs- Cumbersome data

access outside of NAS

Enterprise Management

FAA Systems

FTIFTI SWIM Compliant

Government System

SWIM Compliant

Government System

SWIM Compliant

Non-Government

System

SWIM Compliant

Non-Government

System

ED8ED8


The “Solution”


NAS Transformation to Next Generation Air Transportation System

• Ensure interoperability between systems as required by Next Generation Air Transportation System (NextGen)

• Lower costs for information exchange• Reduce time needed to establish new

interfaces• Increase common situational awareness• Increase NAS agility


What is SWIM?


Key Concepts

• Implement a federated Service-Oriented Architecture (SOA) in the NAS

• Use best commercial practices to the extent practical, while ensuring all FAA safety and security requirements are met

• Commercial Off the Shelf Software (COTS) based to the extent possible

• Establish governance policy, process, mechanisms and metrics

• Delegate applications to SWIM Implementing Programs (SIPs), regulate the interfaces with a combination of requirements (paper) and products


Details of Segment 1


SWIM Program

•The SWIM Program will promote state-of-the-art information management and exchange technologies to:

– ensure information is available to SWIM-enabled systems – allow more distributed decision-making – improve the speed, efficiency, and quality of distributed decision-making

•SWIM-enabled systems will have the ability to:– request and receive information when they need it– subscribe for automatic receipt of new or updated data– publish information and services as appropriate

•The SWIM Program – is an integral part of the NAS Enterprise Architecture roadmap and will close

the performance gap by promoting the development of a secure NAS-wide information web to connect FAA systems

– will enable interaction with other members of the decision-making community including other agencies, air navigation service providers, and airspace users


SWIM Segment 1

ARTCC 1

TRACON 1

ATCT 1

WJHTCSWIM FTINetwork

TFMS TPCCIWSSWIM Labs

TDDS

WMSCR

ATCSCC

SAMS

VNTSC

ITWS

TDDS

AOCsAOCs

NNCC

ERAM

NWS

FTIGateway


Segment 1 Overview

• Nine Segment 1 capabilities were derived from Communities of Interest: Aeronautical Information Management (AIM) Flight & Flow Management (F&FM) Weather

• SWIM will meet its Segment 1 Goals using a “Federated Architecture” SWIM will leverage existing infrastructures, processes,

resources, and logistics chains that are part of the program offices implementing the SWIM capabilities

SWIM Governance will establish operating rules for the stakeholders and their services to ensure use of common protocols and interfaces,

Common commercial software products for some Core Services will be mandated to ensure interoperability


Segment 1 Capabilities

AIM

SUA Automated Data Exchange

Weather

CIWS Publication

ITWS Publication

PIREP Data Publication

Flight & Flow Management

Flight DataPublication

Terminal Data Distribution

Flow Information Publication

RVR Publication

RerouteData ExchangeCapabilities will be implemented as (multiple)

services by SWIM SIPs over the next five years


Core Services


SWIM Functional Architecture

Service Security

Intrusion Detection and Response

Information Technology Infrastructure Functions

SWIM Service Functions

Value-Added Services

Interface Management

Messaging Messaging

Naming & Addressing

Users Users

NAS System

Application

Service InterfaceService InterfaceService Interface

NAS System

ApplicationNAS ApplicationSystem Functions

Identity & Certificate Management

Enterprise Service

ManagementBoundary Protection

Service Interface

Secure IP Network Connectivity


Core Services Components

• Core Services SWIM supports include: – Interface Management

• Interface Specification• Interface Discovery• Schema Management• Service Invocation• SWIM Basic Profile

– Messaging • Reliable messaging routes will be provided on a case by

case basis by NAS integration partners


Core Services Components (cont’d)

• Core Services (cont’d): – Security

• Authentication and authorization will be manually coordinated and integrated by NAS integration partners

– Enterprise Service Management • Service monitoring and configuration

– Not to be done with SWIM administered HW or SW

– Will be accomplished by leveraging existing SIP program system monitoring capabilities and coordinating them across NAS programs


SWIM Core Services Product StackInterface Management

Messaging

Security

• P• o

• l•i• c•

y• •M•

a• n• a

• g•e•

m•e•

n• t

Enterprise Service Management

Progress Fuse ESB

Progress Fuse •Message Broker

Progress Fuse Service Framework

Progress Artix Registry

Progress Fuse HQ

Interface SpecificationInterface DiscoverySchema Management

Progress Artix Registry

Service MonitoringService ConfigurationSystem Monitoring

AuthenticationAuthorization

Audit

Progress FuseService Framework

Progress Fuse Mediation Router

Reliable MessagingPublish •-•SubscribeMessage Routing

Progress Fuse HQ

Artix Enterprise Management

Service

Artix Enterprise Management

Service

Progress Security

Artix ESB C •++


Support to SIPs

• SWIM support to the SIPs includes:– Ensure all parties adhere to the standards via oversight during

requirements definition, software development and test phases, and through SWIM governance

– Provide design guidance – Design-Time Service Registry will be developed and maintained

by SWIM • The servers are not on the operational NAS and will be maintained

at the Tech Center

– Provide Progress Fuse software, training, support licenses, and consulting


SWIM Communication with SIPs

• Implementation team spearheads SIP interactions– Monitors SIP development of services to ensure SWIM

requirements are met, and development is in accordance with SWIM standards

– Holds periodic Technical Interchange meetings– Holds monthly Program Management Reviews with each SIP

• SWIM Wiki initiated to encourage technical interactions

• SWIM KSN used as a document repository• SWIM COTS Repository has been established to

ensure all SIPs use the same software versions


SWIM High-Level Program Schedule

O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S

Core Services

Terminal (TDDS)

TFMS

ERAM Flight Data Services

AIM

ITWS

CIWS

WMSCR

FY13FY11 FY12FY07 FY08 FY09 FY10

Requirements Prototype Design Code & Test Sys Int OT&E/TFM Infrastructure

Requirements Prototype Design Code & Test Sys Int OT&E/KSTFM Flow Object

Require Proto Desig Code & Sys OT&TFM Reroutes to FO

Requir Pr Desi Dev & Sy OTTFM SWIMize RVR

TDDS DeploymentRequirements DesignPrototype Code and Test Sys Int OT&E/

Initial Prototype at WJHTCRequirements COTS Integration WJHTC SWIM Test Facility Operations

Deployment

Requirements

Pr Desi Code & Sys OT

Requirements Desig Dev & Test Sys Int/train Depl

Requirements

Design

Code & Test Deplo

Requirements

Design Code & Test Syst Int & Test

Requirements

Develop Code & Test DeployDesign & Proto

Seg 1 Prototype at WJHTC

Requirements&Design Develop Int. & Test OT&E DeploymentWMSCR ERAM PIREPs

AIM SUA

AIM ERAM Requirements Design Code & Test OT&E Deployment

WMSCR PIREPs

Requirements&Design Design Code & Test OT&E DeploymentInitial Flight Data Services

Flight Data Services - HADDS/FDIO

Requirements Design Code and Test Sys Int & OT&E

Requirements Design Code & Test OT&E DeploymentEnterprise Services

Deploym


Operational Services


AIM: SUA Automated Data Exchange• The Airspace Information Management (AIM) Special Use Airspace (SUA)

Automated Data Exchange will improve capacity and efficiency of the NAS by increasing civilian access to current SUA status.

• The primary benefit to NAS users is improved efficiency: specifically, to increase the capacity and operational efficiency of airspace operations by improving airspace management.

• The SWIM AIM SUA capability will help ensure SUA geometry, schedules and status are digitally managed in the NAS, and changes in SUA status are captured and distributed as they are made.

• Developed in SWIM Segment 1– A standard data entry user interface to accommodate creating and storing SUA and

ATCAA (Air Traffic Control Assigned Areas) definitions in a centralized, configuration managed aeronautical information database management system.

– Services to dynamically publish AIXM SUA definitions for use by the public and within NAS operational systems such as the SUA Airspace Management System (SAMS)

– Standard service that enables users to subscribe to this SUA service and receive SUA information dynamically via the AIXM standard

– A new interface that enables SAMS to receive SUA data updates dynamically from ERAM via an improved ATC GUI


ERAMERAM

AIM

ARTCCARTCC

ERAM

SAMSSAMS

ATCSCCFTI

SUA updates

FAA HQ

NASR

SUA updates

Current SUA Status and SUA updates


Weather: CIWS Data Publication• CIWS products range from current weather depictions, including

growth and decay trends, to convective weather forecasts, including precipitation and echo tops, out to two hours.

• CIWS products are made available to traffic managers and area supervisors where the products are used to support traffic management decisions during convective weather events.

• CIWS has been shown to narrow the gap between unavoidable delay and actual delay associated with convective weather by supporting traffic managers in making use of available capacity during storms that, in the past, would have been lost.

• The SWIM Segment 1 CIWS Data Publication Service will make CIWS data products available to all AOC external NAS users.

• These data services using SWIM standards will enable wider access to weather products furthering common situational awareness.

• In addition, standards based weather product formatting will reduce integration costs.


Weather: CIWS Data Publication

Echo Tops (ET) with annotation

Precipitation with ET Annotation, SEP, and 30/60 minute forecast contours


Weather: ITWS Data Publication

ITWS improves NAS efficiency (and enhances NAS capacity) by displaying the impact of convective weather, storm cells, precipitation, airport winds, microbursts, gust fronts, windshear, lightning, and tornadic activity at selected NAS pacing airports to AOC dispatchers and traffic managers at the ATCSCC, ARTCCs, ATCTs, and large TRACONs.

With this real-time picture of convective weather at pacing airports, traffic managers can collaborate with dispatchers to route/re-route traffic as necessary.

Sharing of weather data promotes common situational awareness, which is absolutely crucial to the collaborative decision making process that is necessary to reduce weather-related delays

The SWIM provided ITWS Data Publication Service will improve on this by providing ITWS products digitally to the AOCs and other subscribers that supports overlay of ITWS products onto user workstations for greater common situational awareness

Further, engineering these data services using SWIM standards will reduce integration costs while enabling wider access to weather products.


Weather: ITWS Data Publication

ITWS Products

Windshear

Microburst

Gust Front

Precipitation

Six-Level Precipitation

Ribbon Display

Runway Configuration

Lightning in Storm Cell

Storm Motion-Direction

Storm Cell

Long-range Precipitation

Short-range Precipitation

Terminal Convective Weather Forecast

Terminal Winds


Weather: PIREP Data Publication

The Aviation Weather Center (AWC) provides dedicated 7X24-hour services for aviation, including the generation of advisories on significant weather impacting aviation (e.g., AIRman's METeorological Information (AIRMETs), Significant METeorological Information (SIGMETs), and Convective SIGMETs)

Pilot Reports (PIREPs) are an important part of AIRMETs and SIGMETs

Segment 1 will develop a capability that will allow En Route controllers to efficiently capture PIREPs in ERAM, which will transmit the reports to WMSCR for distribution to the AWC

Today, it is estimated that approximately 90% of voice-received PIREPs are not reported

Capture of crucial pilot observations by ERAM and distribution of these to other NAS users by WMSCR via a new SWIM service will significantly enhance NAS safety.


VOLPEVOLPE

ITWS

NNCCNNCC

Weather

ITWS products

WMSCR AOCs

WJHTCWJHTC

CDDS

ED8Gateway

FTI

ARTCC

WMSCR PIREPs

ERAM

NWS

WMSCR PIREPs

ITWS, CIWS, WMSCR PIREP products

CIWS Products

ITWS, CIWS, WMSCR PIREP products

MIT/LLMIT/LL

CIWS


F&FM: Terminal Data Distribution• SWIM Segment 1 provides the infrastructure to support

transition to a SWIM IP-based front end to Terminal legacy systems.

• Existing flight data interfaces to Terminal are antiquated and are limited to receiving a subset of the data.

• Terminal systems are connected via a passive tap off an existing En Route/terminal interface to the flight strip printer and are therefore limited to only those data elements that support the current flight strip printer interface.

• A direct interface will allow for the bidirectional flow of information and make status event information available to users outside of Terminal.

• In the SWIM segment 1 timeframe, Tower Data Link Services (TDLS)/Pre-Departure Clearance (PDC) will have access to the full route of flight in the flight data that will support the data link delivery of full route clearances and revised clearances due to flight plan amendments.


TFM DRCTFM DRC

F&FM: Terminal Data Distribution WJHTCWJHTC

ERAMERAM

ARTCC

FTI

Flight Information

Flight Information

TFMS

ICE

NORAD

Gateway (ED8)

EFSTSTDLS

ASDE-X

TDDS

Terminal Cluster (TRACON & TOWER)

RVR

Flight Information


F&FM: Flight Data Publication• One goal of better flight data management in the Segment 1 timeframe

is to improve the flight data processing to ensure consistency of flight data across the NAS and to consolidate the flight data maintained by multiple systems into a distributed flight object accessible by all.

• The distributed flight data will include data such as the filed flight plan, the currently-cleared route, the “ATC-intended” route to be cleared, the predicted aircraft trajectory, and the current state of the flight.

• The distributed flight data will be comprised of elements supplied by multiple domains, and through this data sharing and coordination, the Flight Data Publication Service will support trajectory-based ops between En Route, Terminal, and TFM domains.

• The operational threads to be integrated across these domains will require the ability of other systems to update flight data. Examples include aircraft taxi status information and clearance delivery status from Terminal systems such as the TDLS and the EFSTS.

• Other ATM systems such as TFMS will be synchronized via flight data received from the En Route Domain. Conversely, the En Route Domain flight object will be updated by flight data received from TFMS.


F&FM: Flight Data Publication


Flight Data

WJHTCWJHTC

ERAMERAM

ARTCC

FTI

Flight Data

Flight Data

TFMS

ICE

NORAD

Gateway (ED8)

EFSTSTDLS

ASDE-X

TDDS

RVR

SWIM Service

SWIM Service


F&FM: Flow Information Publication, Runway Visual Range and Reroute

• Flow Information Publication– Flow information that describes current and planned traffic flow

initiatives in the NAS provides a means for ERAM and other clients to subscribe to flow information describing several types of traffic flow initiatives.

– These will include the following: Flow Constrained Area (FCA) Airspace Flow Program (AFP) Ground Delay Program (GDP) Ground Stops (GSs) Reroutes Advisories


F&FM: Flow Information Publication, Runway Visual Range and Reroute• Runway Visual Range (RVR) Publication

– Make runway visibility data available to more National Airspace System (NAS) users, with more RVR data from more Terminal facilities than TFM presently provides

– Provision RVR data as a SWIM service that employs standard industry web service and networking protocols

– Facilitate addition of new subscribers to the service, including members of the DoD, General Aviation, and Homeland Security.

• Reroute Data Exchange– Traffic Flow Management (TFM), through its Collaborative Decision

Making (CDM) programs, facilitates development of aircraft reroutes because of predicted airspace congestion due to severe weather, facility outages, special events, or emergencies in the NAS.

– This will be achieved via exchange of pre-departure rerouting information between TFM and En Route domains, once a flight plan has been filed with the En Route domain.


AOCs AOCs

DRCDRC

WJHTCWJHTC

TFMSTPCTFMSTPC

Flight Information

ARTCC

F&FM: Flow Information Publication, Runway Visual Range and Reroute

Surface Data from Terminal Clusters

TFMSTFMS

(Backup Data)

Flow Information

ERAMERAM

AOCs AOCs

Flow Information, RVR

FTI

EFSTSTDLS

ASDE-X

TDDS


RVR

Gateway (ED8)


Summary


SWIM Segment 1

• SWIM– Supports OMB endorsed Federal Enterprise Architecture goal to

simplify processes and unify work across agencies– Allows software applications in the NAS to interact with one another

without knowledge of application's underlying platform implementation– Simplifies interface requirements to existing NAS system– Reduces NAS development and implementation costs and risks for

new applications– Enables transition net-centric NAS operations from tactical conflict

management to strategic trajectory-based operations

• Additional information on Segment 1 and future segments – www.swim.gov

Documents

Presented to: By: Date: Federal Aviation Administration Web Services Implemented During System Wide Information Management (SWIM) Segment 1 AIXM/WXXM Conference