Federal Aviation
Administration

System Wide Information
Management (SWIM)

Presented to: Japanese Civil Aviation Bureau
Presented by: Jay Merkle

SWIM

The ChallengeEnterpriseManagementToday

FAA
Systems

HostETMS

WARP
IDS/
ERIDS

ASDE-XATOPERAMSTARS/
ARTS/
TAMR

SWIM
SWIM
CompliantCompliant
NonNonGovernment
Government
SystemSystem

FTI
FTI

SWIM
SWIM
CompliantCompliant
Government
Government
SystemSystemSWIM Core
Services andStandards

CIWS

Business as Usual
TMA
TFM

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

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

(NextGen without SWIM)- More unique, point-topoint interfaces- Costly development, test,maintenance, CM- New decisions linked toold data constructs- Cumbersome data accessoutside of NAS
Federal Aviation
Administration

22

SWIM

Program Concept
SWIM is an IT infrastructure program that will
operate in the background to provide data toauthorized users
SWIM will:• Implement a Service-Oriented Architecture (SOA) inthe NAS• Lower information costs• Increase speed to establish new interfaces• Increase common situational awareness• Increase NAS agility

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

33

SWIMThe Plan

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

44

SWIMSegment 1 Overview• Nine Segment 1 capabilities were derived from three
Communities of Interest:¾ Aeronautical Information Management (AIM)¾ Flight & Flow Management (F&FM)¾ Weather• SWIM will not implement a separate infrastructure for
Segment 1¾ SWIM will leverage existing infrastructures, processes,
resources, and logistics chains that are part of the program
offices implementing the nine SWIM capabilities¾ SWIM Governance will ensure use of common protocols andinterfaces, assisted by use of commercial software for someCore Services

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

55

SWIM

Segment 1 Capabilities

AIM

Flight & Flow
Management

Weather

SUA AutomatedData Exchange

CIWS
Publication

Flight Data
Publication

ITWS
Publication

Terminal Data
Distribution

PIREP Data
Publication

Flow Information
Publication
RVR
Publication

Capabilities will be implemented as services by
SWIM Implementing Programs (SIPs) over thenext five years
2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

RerouteData Exchange

Federal Aviation
Administration

66SWIM

High-Level Schedule
FY07
FY08
FY09
FY10FY11FY12FY13O N DJF M A M JJA S O NDJF M A M JJA S O NDJF M A M JJA S O NDJF M A M JJA S O NDJF M A M JJA S O NDJF M A M JJA S O N D J F M A M J J A SCore Services

Requirements
COTS Integration
Initial Prototype at WJHTC

WJHTC SWIM Test Facility Operations
Seg 1 Prototype at WJHTC

Terminal (TDDS)

Requirements
TFM Infrastructure Requirements

Prototype

Design

TFM Flow Object

Code & Test

Requirements

TFMS

TDDS Deployment

Prototype Design Code and Test Sys Int OT&E/
Sys Int OT&E/
Prototype

DesignSys Int OT&E/KS

Code & Test

TFM Reroutes to FO Require Proto Desig Code &Sys OT&TFM SWIMize RVR Require Pr Desi Code & Sys OT

Initial Flight Requirements&Design
Data Services

ERAM Flight Data
Services

DesignCode & Test OT&E

Flight Data
Services - Requirements
HADDS/FDIO

Requir Pr Desi Dev &Sy OT

Deployment

Design Code and Test
EnterpriseServices

Requirements

AIM SUA Requirements Desig Dev & Test

Deployment

Sys Int & OT&E

Sys Int/train

DesignCode & Test OT&E

Deployment

DesignCode & Test OT&E

Deployment

Depl

AIMRequirements

AIM ERAMITWSRequirem

DesignRequire Desi Code & Test De

CIWS
WMSCR PIREPs Requirem

WMSCR

Code & Test Syst Int & Test Depl

Design & Proto

WMSCR ERAM PIREPs Requirements&Design

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Develop

Develop
Int. & Test

Code & Test
OT&E

DeployDeployment

Federal Aviation
Administration

77

SWIM

FY2008 – FY2010 Activities / Progress
FY 2008

Milestone

1QTR

2QTR

FY 2009
3QTR

4QTR

1QTR

2QTRFY 2010
3QTR

JRC 2B SWIM
Segment #1B

4QTR

1QTR

2QTR

3QTR

4QTR

JRC 2B SWIM
Segment #2

Identified software standards
needed for SWIM compliance
Issued SWIM service container
software/middleware
RFO/SIR

Product(s) selection,
contract award

Establishing SWIM governance via
standards & coordination with EAB
reviews of other NAS programs
Kicked off Segment 2 definition
activities with Community ofInterest (COI) leads
Restructured WJHTC labs tosupport SWIM prototyping andintegration with NAS systems
ITWS
SWIM compliant CIWS & ITWS
weather products prototypes;
prototype products may beprovided to airspace users

Prototype Operational

CIWS

SWIM workgroup set up with
Government Electronics and IT
Association (GEIA)
Established relationship with ATA,AOPA, NBAA and RAA for airspace
users Segment 2Work with NAS Configuration
Control Board to establish SWIM
governance for proposed NAS
Changes
Return to JRC Investment analysis
process
FY09/10 SIP Service Level
Agreements

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

88Technical Overview

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

99SWIMTechnicalArchitecture

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1010

SWIM

Current Standards
Standard Designation Standard Title
JMX V1.4
Java Management Extensions
SNMP v3
RFC 2573 SNMP Applications
HTTP v1.1
Hypertext Transfer Protocol (RFC 2616)
JMS v1.1
Java Message Service
Websphere MQ
SOAP v1.2
Simple Object Access Protocol
WS-Addressing v1.0
W eb Services Addressing C ore
WS-Attachments
MTOM
SOAP Message Transmission Optimization Mechanism
XML v1.0 & v1.1
Extensible Markup Language (XML)XSD (working draft) v1.1 XML Schema Definition Language
Xpath v1.0
XML Path Language
XqueryXquery Version 1.0
XSLT v1.0
XSL Transformations
UDDI 3.0.2
Universal Description Discovery & Integration (UDDI)
WSDL v2.0
W eb Services Description Language
X.509 CertificatesInternet X.509 Public Key Infrastructure Certificate and CRL Profile (RFC 2459)
WS-Security v1.1
W eb Services Security Policy
TLS
Transport Layer Protocol (RFC 2246)
SSL
Secure Socket Layer v3.0 (Internet D raft)

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1111

SWIMService Container Contract••Contract award to Iona Technologies on August 18, 2008
Contract options:–––––•••

SoftwareDocumentation
Support Licenses
TrainingConsulting Services

Indefinite Delivery Indefinite Quantity
Base year + 12 option years
Iona was purchased by Progress Software on September 12, 2008––––

Fuse will remain and continue to evolve
Artix will be combined with Progress SOA portfolio
Artix already interoperates with the Progress Sonic ESB
Product integration between Artix and Actional for run-time visibility andgovernance is already underway as part of an existing partnership
between IONA and Progress2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1212

SWIM

Available Products on Contract•

Products Available:–FUSE Suite•••••––––––••FUSE ESBFUSE Services Framework
FUSE HQFUSE Mediation Router
FUSE Message Broker

Artix Data Services
Artix Registry/Repository
Artix ESB C++
Artix Connect for WCF
Artix Security
Artix Enterprise Management Service Plug-in

Artix Orchestration (meets desirable requirement for BPEL)
available at extra cost
Fuse is not currently supported on AIX but will be by mid
November 2008.

2009/3/26System
Wide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1313

SWIM

Use of Iona Software for Core Services

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1414

SWIM

Prototype: Goals• Prior to Service Container Contract award to IONA Technologies,
Two prototypes were developed to evaluate service containers– ITWS-SWIM Prototype using a service container product provided by IONAFuse
– CIWS-SWIM Prototype using a service container product provided by Mule••

CIWS-SWIM Prototype was completed and was not made available
to users once the IONA Service Container Product was selected.
ITWS-SWIM prototype was extended to be able to provide service
to interested non-FAA consumers to evaluate web services andXML formats, and overall products’ usability– Publishing four ITWS weather products• Microbursts; Gust Fronts; Configured Alerts; Terminal Text•

ITWS-SWIM Prototype became operational on October 6, 2008 andwill operate until ITWS-SWIM Segment One capability is deployedin December 20102009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration1515

SWIM

Prototype: FY08 ITWS-SWIM Prototype Accomplishments
•••

•
•

Initial end-to-end testing and stress testing successful, August 2008
Conducted successful tests with the FTI National Test Bed (FNTB) and theED-8 Gateway
Three airlines selected as initial participants– JetBlue, UPS, NWA– UPS operational today
SCAP update effort successful to date – with late September Certification
and Authorization target
FTI connectivity between Volpe and the WJHTC in place– Backbone will support ITWS SWIM Prototype subscriber traffic•UPS connectivity to FTI ED-8 Gateway occurred the week ofSeptember 23•Successfully explored “don’t code, configure” principles. Results to datewith Iona Fuse have been very promising– Produced a proof-of-concept configuration enabling WS-Security functions inITWS SWIM Prototype System through configuration only (no codingrequired)2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1616

SWIM

Prototype: FY09 Plans• Agreement reached and documented with ITWS to maintain thePrototype through FY10
– No enhancements after initial deployment are currently funded or planned••Volpe will provide client software and a user guide to additional
service consumers
More service consumers may be added until the current allocatedbandwidth limit for the prototype is reached2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1717

SWIM

FY09 Work•

Service Registry/Repository––•

XML Gateway–••

Initial RegistryRepository stood up at WJHTC
Evaluation based on Requirements to be conducted this year
Qualified Vendor List in process

Policy Server– Requirements in Development– Evaluation to be conducted early next year
SWIM Resource Kit– Assist the SIP developers in learning and utilizing the SWIM Core Services– Assist the SIP developers in debugging COTS and related third party
products– Assist the SIP developers in obtaining and managing the resources
required for development.
– Assist the SIP developers in identifying the SWIM Service Container
components required to implement their Service.
– Assist the SIP developers in sharing knowledge.
– Provide tools to assist the SIP developers with testing.

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1818

SWIM Resource Kit•

Guidance Documentation– Maven Guidance– Developers Guide for Fuse ESB•••••

Procedures for installing Eclipse, Fuse tools for Eclipse and Maven plug-in
Build procedures
Debugging procedures
ExamplesCOTS Repository– Fuse ESB, Fuse Mediation Router, Fuse Message Broker, Fuse HQ, Fuse
Service Framework, Spring, Eclipse, Maven, Ant•

SWIM Reference Model– Description of Service Container components and interfaces– Maps Service Container components to Core Services– Decision Tree for identifying which Service Container components andarchitecture are required to achieve particular operational needs• i.e., guaranteed messaging••

Governance and Policy GuidanceStandards

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

1919

SWIM Resource Kit (Continued)• Tools– WS-I Testing Tools– iTKO LISA – SOA Test Tool and Virtual Service Emulation (VSE)••••XML Gateway Qualified Vendor List
SWIM Wiki
Third Party References and Training Information
Available on the SWIM Wiki as Resource Kit items arecompleted (NLT 1/1/09)• Resource Kit is dynamic– New items will be added as required

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal AviationAdministration

2020

SWIM

Future Plans for Segment 2•

Determine operational requirements for information that must be
met in FY12-16 (Segment 2)– Input from JPDO, Roadmaps, Operational Improvements••

Determine technical requirements needed to meet Segment 2
operational requirements
Determine how the Segment 1 architecture must evolve to meetSegment 2 requirements– Ex. Segment 1 federated approach vs. possible future centralized approach•

JRC for Segment 2 currently planned for June 20102009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

2121SWIMWeb Sitewww.swim.gov

2009/3/26
SystemWide Information Management (SWIM)
October 22, 2008

Federal Aviation
Administration

2222