System Wide Information Federal Aviation Management · PDF fileSystem Wide Information Management (SWIM) ... custom designs ... • SWIM Web Service Security Compliance Test Kit

Presented to: CAR AIM Seminar

By: George P. Sempeles after Ahmad Usmani & Jim Robb

Date: July 2012

Federal AviationAdministration

System Wide Information Management (SWIM)

Program Overview


SWIM Program OverviewJuly 2012

Program Concept

• SWIM will:― Implement a Service Oriented Architecture (SOA) in the NAS

by providing Enterprise Infrastructure services that include messaging, security, enterprise service management, and interface management

―Oversee and govern the implementation of cloud computing in the NAS

―Ensure adherence to common standards (Governance)―Allow the FAA to create new system interfaces more quickly

and cost-effectively than is possible today―Facilitate the data-sharing that is required for the Next

Generation Air Transportation System (NextGen)

SWIM is an Information Technology (IT) infrastructure program that operates in the background to provide data to authorized users to

facilitate collaboration across National Airspace System (NAS) domains

2



Business as UsualAIM

WARP

IDS/ERIDS

ATOP

CIWS

TFMTMA

STARS/ARTS

ERAM

ASDE-X

R-TFMS

Inter-Agency

NAS System Interfaces in the Legacy Environment

State of the System

• Existing point-to-point hardwired NAS

• Unique interfaces, custom designs

• More point-to-point unique interfaces

• Costly development, test, maintenance, CM

• New decisions linked to old data constructs

• Cumbersome data access outside the NAS

Enterprise Management (SWIM)

LEGEND

SWIM Segment 1SWIM Future Services

SWIM Adapter

FAA Systems

SWIM-Compliant Non-Government

Systems

SWIM-Compliant Government

Systems

FTI

TDD

S

ITW

SATOP

ERAM

33



Conceptual Overview

FAA Telecommunications Infrastructure (FTI)

SWIM Messaging Infrastructure

WXXMFIXMAIXMStandards for

Data Exchange

Controllers FAA Command Center

NextGenApplications

SystemDevelopers

Non-FAA Users(e.g., Airlines, DoD,

DHS, ANSPs)

4



Segmented Approach to SWIM• SWIM Segment 1:

― Implementation of a set of federated services in the NAS with SWIM-provided governance, standards, and software to support development of reusable SOA services

― SWIM provides requirements, schedule, and funding to seven other NAS programs (i.e. SWIM Implementing Programs (SIPs)); tracks progress via formal monthly reviews

― Segment 1 results in SOA services deployed to all Air Route Traffic Control Centers (ARTCCs), 37 Terminal Radar Approach Controls (TRACONs), the Air Traffic Control System Command Center, the William J. Hughes Technical Center (WJHTC), and NAS Enterprise Management Centers (NEMCs)

• SWIM Segment 2:― Continues provision of governance, standards, and software to

additional NAS programs― Implements enterprise messaging service for NAS programs and

facilitates transition by Segment 1 SIPs

55



Core Services ComponentsCore Services supported by SWIM include:

• Interface Management - interface specification, discovery, and schema management

• Messaging - reliable messaging as well as publish/subscribe services

• Security - authentication, authorization, and audit services

• Enterprise Service Management - service monitoring, service configuration, and system monitoring

6



SWIM Schedule

7



SWIM Segment 1 CapabilitiesAeronautical Information

Management (AIM)Community of Interest (COI)

Special Activity Airspace (SAA)Automated Data Exchange

Weather COI

Corridor Integrated Weather System (CIWS) Publication

Integrated Terminal Weather System (ITWS) Publication

Pilot Report (PIREP) Data Publication

Flight & Flow Management (F&FM) COI

Flight DataPublication Service (FDPS)

SWIM Terminal Data Distribution System (STDDS)

Flow Information Publication

Runway Visual Range (RVR) Publication

RerouteData Exchange

Capabilities will be implemented as multiple services by SIPs through FY15

88



Capability Example: ITWS Publication

ITWS information accessed via InternetITWS information accessed through ITWS Situation Display

•There are more than 10,000 airports in the US, yet fewer than 100 Air Traffic Control Towers have direct access to ITWS Situation Displays

•SWIM enables ITWS information to be accessed by those without direct access, facilitating common situational awareness

9



NAS Service Registry/Repository (NSRR)

• A Service Registry is a resource that provides controlled access to data necessary for the implementation and governance of SOA projects

• A Repository is a database containing the artifacts and metadata that constitutes a SOA registry

• The NSRR is SWIM’s Registry/Repository for NAS Services• Registering with the NSRR will be the only way to receive FAA NAS

data

10

ServiceConsumer

ServiceProvider

NSRR

Exchange Messages

Publishand Register

Contract

Discoverand Retrieve

Contract

The NSRR provides Interface Management for the NAS

• The NSRR is open to external usershttps://swimrep.faa.gov/soa/web/login



SWIM Segment 2 Enterprise Infrastructure

• Domain Name Service (DNS) provides naming and name-to-address resolution services across the Enterprise

• Network Time Protocol (NTP) and Precision Time Protocol (PTP) provides time synchronization services across the Enterprise

• NAS Enterprise Messaging Service (NEMS)

11



NEMS Overview

• NEMS support for NAS Reliability, Maintainability, and Availability (RMA) requirements

• Any service available on one NEMS node will be available on any other NEMS node

• Intelligent Routing, routing decisions made based on certain data attributes or pre-defined conditions

• Data Filtering, based on Java Messaging Service (JMS) message header contents or attributes of the Extensible Markup Language (XML) schema

• Meets Enterprise Boundary Protection (EBP) requirements through integration with the NESG

NEMS is providing Messaging Services for the NAS

12



NEMS Messaging Capabilities• NEMS supports two Message Exchange Patterns (MEPs):

– Publish/Subscribe – Request/Response

• In the Publish/Subscribe MEP, senders (Publishers) send messages to receivers (Subscribers) through Message Broker service

• Subscribers express interest in receiving only specific messages, based on a message topic

• Two main advantage of the Publish/Subscribe pattern are: – loose coupling– scalability

13



NEMS Messaging Capabilities • In the Request/Response MEP, a requestor sends a request

message to a producer that receives and processes the request, ultimately returning a message in response

• Request/Response allows two systems to have a two-way conversation with one another over a messaging channel

• Request/Response is typically (but not always) implemented as a SOAP-based Web Service– NEMS provides a simple proxy capability and transports the data via

HTTP from the Message Producer to the Message Consumer – Most commonly this pattern is implemented synchronously

14



NEMS Deployment Highlights• Current NEMS deployment includes messaging nodes at:

– Atlanta and Atlantic City NESGs– FTI National Test Bed (FNTB) (Atlantic City)– Research and Development (R&D) Domain (Atlantic City)

• Dedicated messaging nodes in the NESG are utilized as an interface between NAS and non-NAS entities

• Four internal NAS nodes will be installed at the beginning of 2012– Used for NAS-to-NAS distribution of SOA data products – Node Locations: ACY, ZTL, OEX, ZLC

• Tentative end-state architecture will utilize 23 internal NAS nodes – 21 Air Route Traffic Control Centers (ARTCCs) (including Alaska) – ACY and OEX

15



NEMS Data-flows: NAS-to-NAS

16



NEMS Data-flows: Non-NAS Consumer

17



NEMS Data-flows: Non-NAS Producer

18



19

SWIM Governance• WHO is responsible

– Governance Authority• Initial Service Candidate Approval by Technical Review Board (TRB)• SWIM manages remainder of lifecycle for approved programs

– Service Providers responsibilities documented– Service Consumers responsibilities documented

• WHAT must they do– SWIM Governance Policies– SWIM Service Lifecycle Management Processes

• HOW must they do it– Technical Standards coordinated with NAS Enterprise Architecture

• Technical Standards Profile• Technical Standards Forecast

– FAA Standards• XML Namespaces• Web Service Registration• Web Service Description Documents• Web Service Taxonomies

– SWIM Version Management Processes– NSRR User Guides



20

Scope of SWIM Governance

SWIM Governance is a catalyst for improving overall NAS, Air Traffic Organization (ATO) and FAA governance

Itʼs a part of FAA GovernanceWhat is FAA/ATO/NAS governance?

Establishing decision making rights associated with the FAA/ATO/NASEstablishing mechanisms and policies used to measure and control the way FAA/ATO/NAS decisions are made and carried out

What is SWIM governance?

Extension of NAS governance focused on the lifecycle of services to ensure the business value of SWIM

ATO Governance

SWIMGovernance

NAS Governance

FAA Governance



• SWIM Compliance Definition:– “Verified conformance to SWIM Policies.”Verification Mechanisms– Manual review of artifacts– Governance-enabling technology

• NSRR• Testing Tools (Actional, Lisa, etc…)• SWIM Web Service Security Compliance Test Kit • Policy Servers• XML Gateways• Enterprise Service Management (ESM) software

SWIM Compliance

21



22

Service Lifecycle Management Decisions

Technical Review Board (TRB)Investment Decision AuthoritySWIM Governance Team

In Service Decision (ISD) Authority



• International Civil Aviation Organization (ICAO)– Air Traffic Management (ATM) Requirements and Performance Panel (ATMRPP)

– ICAO SWIM Concept of Operations (ConOps) (November 2012)– SWIM Guidance Document (December 2013)

• Single European Sky ATM Research Joint Undertaking (SESAR JU)– SWIM Interoperability Workgroup

• Japan Civil Aviation Bureau (JCAB)– Future Air Transportation System (FATS) Working Group

• May 2011, United States• October 2011, Japan• May 2012, United States

– Asia/Pacific Flight Data Object Demo (May 2012)• Civil Aviation Authority of China/

Air Traffic Management Bureau (CAAC/ATMB)– December 2010, China– March 2011, United States– September 2011, United States– October 2011, China

• Airservices Australia (ASA)– Asia/Pacific Flight Data Object Demo (May 2012)

International Coordination

23



FAA Cloud Computing Approach• FAA NAS and non-NAS organizations are working

collaboratively on adoption of cloud computing under the leadership of the FAA Chief Information Officer (CIO)– SWIM is responsible for managing the implementation of

cloud computing in in the NAS

– The FAA Information Technology (IT) Operations Lead Team is responsible for oversight and guidance for FAA’s non-NAS IT infrastructure, including cloud computing

24



The SWIM website describes the SWIM program and provides news, announcements, and information on current issues

It also contains key documentation, including select briefings, the SWIM Newsletter, and the SWIM Q&A

There are several ways to learn more about SWIM

www.faa.gov/nextgen/swim

25



Questions and Comments?

2626