1. System Wide Information Management (SWIM)
Program Overview

2. Agenda Program Overview Segment 1 Segment 2 Governance Cloud Computing
Core of Program Concept
How SWIM lowers information costs: Uses standard interfaces and new protocols such as XML. This greatly reduces the amount of software that must be created share data between FAA systems.
How SWIM increases speed for new interfaces: Use of standard interfaces reduces customization time. Plus, XML protocols eliminates the need for “information consumers” to write special parsing program to figure out which data they need.
The ability to manage data at a lower cost (and faster setup speed) means more data sharing… which increases common situational awareness and improved agility.
Lower information costs
Increase speed to establish new interfaces
Increase common situational awareness
Increase NAS agility 2 2

3. Program Concept SWIM will:
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
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)
Core of Program Concept
How SWIM lowers information costs: Uses standard interfaces and new protocols such as XML. This greatly reduces the amount of software that must be created share data between FAA systems.
How SWIM increases speed for new interfaces: Use of standard interfaces reduces customization time. Plus, XML protocols eliminates the need for “information consumers” to write special parsing program to figure out which data they need.
The ability to manage data at a lower cost (and faster setup speed) means more data sharing… which increases common situational awareness and improved agility.
Lower information costs
Increase speed to establish new interfaces
Increase common situational awareness
Increase NAS agility 3 3

4. State of the System Business as Usual
More point-to-point unique interfaces
Costly development, test, maintenance, CM
New decisions linked to old data constructs
Cumbersome data access outside the NAS
NAS System Interfaces in the Legacy Environment
Business as Usual
AIM
WARP
IDS/ ERIDS
ATOP
CIWS
TFM
TMA
STARS/
ARTS
ERAM
ASDE-X
R-TFMS
Inter- Agency
SWIM-Compliant Government Systems
FAA Systems
AIM
ERAM
TFMS
Enterprise Management (SWIM)
CIWS
Existing point-to-point hardwired NAS
Unique interfaces, custom designs
ITWS
FTI
TDDS
TAMR
TBFM
SWIM-Compliant Non-Government Systems
WMSCR
LEGEND
ATOP
SWIM Segment 1
SWIM Future Services
SWIM Adapter 4 4 4

5. (e.g., Airlines, DoD, DHS, ANSPs)
Conceptual Overview
FAA Telecommunications Infrastructure (FTI)
SWIM Messaging Infrastructure
WXXM
FIXM
AIXM
Standards for
Data Exchange
Controllers
FAA Command Center
NextGen
Applications
System
Developers
Non-FAA Users
(e.g., Airlines, DoD, DHS, ANSPs)
NextGen Application Systems (Publishers) (Enroute Automation, Traffic Flow Management, NextGen Weather Processor etc.)
External Users (Subscribers) (Airspace user Flight Ops Centers, DoD Command and Control Centers, Airports, etc.)
SWIM (messaging, identity and certificate management, enterprise service mgmt., interface adaptation, conflict resolution, data re-distribution)
STANDARDS for Data Exchange
AIXM: Aeronautical Information Exchange Model
WXXM: Weather Information Exchange Model
FIXM: Flight Information Exchange Model
NAS IP Network Infrastructure (IP addressing, routing and forwarding, NAS boundary protection, naming (DNS, LDAP), intrusion detection, bandwidth management, etc.)

6. 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
Core of Program Concept
How SWIM lowers information costs: Uses standard interfaces and new protocols such as XML. This greatly reduces the amount of software that must be created share data between FAA systems.
How SWIM increases speed for new interfaces: Use of standard interfaces reduces customization time. Plus, XML protocols eliminates the need for “information consumers” to write special parsing program to figure out which data they need.
The ability to manage data at a lower cost (and faster setup speed) means more data sharing… which increases common situational awareness and improved agility.
Lower information costs
Increase speed to establish new interfaces
Increase common situational awareness
Increase NAS agility 6 6

7. Core Services Components
Core 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
Interface Management will be discussed with the SWIM Governance and the NSRR
Messaging, in the form of the NEMS, will be discussed with SWIM Near-Term Plans 7 7

8. SWIM Schedule
Schedule as of 04/18/11

9. SWIM Segment 1 Capabilities
Aeronautical Information
Management (AIM)
Community of Interest (COI)
Weather COI
Flight & Flow Management
(F&FM) COI
Special Use Airspace (SUA)
Automated Data Exchange
Corridor Integrated Weather
System (CIWS) Publication
Flight Data
Publication Service (FDPS)
Integrated Terminal Weather
System (ITWS) Publication
SWIM Terminal Data
Distribution System (STDDS)
Pilot Report (PIREP) Data
Publication
Flow Information
Publication
SWIM Segment 1 commits to delivery of 9 capabilities, 8 of which are on track:
Two capabilities are complete and operational:
ITWS Data Publication
CIWS Data Publication
Three capabilities are complete and waiting for installation:
WMSCR PIREP Data Publication – Phase I scheduled for June 2012
AIM SUA Automated Data Exchange – scheduled for July 2012
Pre-Departure Reroute – 2012
Three capabilities are on schedule and within budget allocations:
STDDS
Flow Information Publication
RVR Data Publication
One capability is being replanned to be developed at the WJHTC:
FDPS
Runway Visual Range (RVR)
Publication
Capabilities will be implemented as multiple services by SIPs through FY15
Reroute
Data Exchange 9 9

10. Capability Example: ITWS Publication
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
ITWS information accessed through ITWS Situation Display
ITWS information accessed via Internet

11. Segment 1 Status
SWIM Segment 1 commits to delivery of nine capabilities, eight of which are on track:
Two capabilities are complete and operational:
ITWS Data Publication
CIWS Data Publication
Four capabilities are complete and waiting for installation in FY12:
Weather Message Switching Center Replacement (WMSCR) PIREP Data Publication
AIM SUA Automated Data Exchange
Reroute Data Exchange
STDDS
Two capabilities are on schedule and within budget allocations:
Traffic Flow Management (TFM) Flow Information Publication Service (FIPS)
RVR Data Publication
One capability is being replanned and will be developed in-house:
FDPS 11 11 11

12. Anticipated Segment 1 Products
Capability
Products
AIM SUA Data Exchange
SUA data, dynamically via an improved ATC GUI
SUA data, dynamically provided in the AIXM standard
AIXM SUA definitions
ITWS Data Publication
Airport Lightning Warning
Configured Alerts
Forecast Accuracy
Forecast Contour
Forecast Image
Gust Front TRACON Map
Microburst TRACON Map
Precipitation 5nm
Precipitation Long Range
Precipitation TRACON
SM SEP 5nm
SM SEP Long Range
SM SEP TRACON
Terminal Weather Text Normal
Tornado Alert
Tornado Detections Wind Profile
AP Indicated Precipitation
AP Status
Gust Front ETI
Hazard Text 5nm
Hazard Text Long Range
Hazard Text TRACON
ITWS Status Information
Microburst ATIS
Runway Configuration
Storm Motion 5NM
Storm Motion TRACON
Terminal Weather Text Special
Wind Shear ATIS
CIWS Data Publication
VIL Mosaic (1km resolution)
VIL 2-hr. Forecast
Echo Tops Mosaic (1 km resolution)
Echo Tops 2-hr. Forecast
Satellite Mosaic
Storm Info: Echo Top Tags
Storm Info: Leading Edges
Storm Info: Motion Vectors
VIL Forecast Contours (Std. Mode)
VIL Forecast Contours (Winter Mode)
Echo Tops Forecast Contours
Growth & Decay Contours
Forecast Accuracy: Echo Tops
Forecast Accuracy: Std. Precip
Forecast Accuracy: Winter Precip

13. Anticipated Segment 1 Products (cont.)
Capability
Products
WMSCR PIREP Data Publication
Transmission of voice PIREPs to WMSCR
Stored PIREPs
Altimeter settings
Reroute Data Exchange
Pre-departure flight reroute information, from Traffic Managers to Air Traffic Controllers
STDDS
Airport Surface Detection Equipment - Model X (ASDE-X) data
Electronic Flight Strip Transfer System (EFSTS) data
NextGen (NG)-RVR data
Terminal Data Link System (TDLS) data
FIPS
Flow Constrained Area (FCA)
Airspace Flow Program (AFP)
Ground Delay Program (GDP)
Ground Stops (GSs)
Reroutes
Advisories
RVR Data Pub.
Runway visibility data
FDPS
Flight Information
Track Information
Sector Information
General Information
Restriction Information
Beacon Code Mgmt. Information
Operational Data Archive Information (Traffic Count, Instrument Approach Count, Sign In/Sign Out)

14. NAS Service Registry/Repository (NSRR)
The NSRR provides Interface Management for the NAS
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
Service
Consumer
Provider
NSRR
Exchange Messages
Publish
and Register
Contract
Discover
and Retrieve
The NSRR is open to external users
Interface Management will be discussed with the SWIM Governance and the NSRR
Messaging, in the form of the NEMS, will be discussed with SWIM Near-Term Plans 14 14

15. SWIM Segment 2
In November 2010, the FAA Joint Resources Council (JRC) created procedural path for SWIM to become the Governance Agent for SOA in the NAS
SWIM to provide the enterprise SOA infrastructure within the NAS for individual programs to use
SWIM will support efforts to ensure that SOA Governance complies with NAS Governance
Specific SOA tools are being prototyped as Segment 2 candidates
Segment 2 prototyping has identified new opportunities that may reduce cost and risk of Segment 1 services
NAS Enterprise Messaging Service (NEMS) to be provided via FTI, building on the ASDE-X prototype 15 15

16. 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)
. The collection of NEMS across the NAS, if sufficient, behave as a virtual Enterprise Service Bus (ESB)
Per CIO: DNS on non-NAS side already

17. NEMS is providing Messaging Services for the NAS
NEMS Overview
NEMS is providing Messaging Services for the NAS
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 17

18. 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 18

19. NEMS Messaging Capabilities (cont.)
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 19

20. 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
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 20

21. Producer/Consumer Deployment Status
Consumer(s)
Product(s)
Cutover
TFMS (ASDE-X)
Airlines/
External Users
ASDE-X (Track reports)
April 2011
WARP
OASIS
Harris Weather Data Service Products
Feb. 2012
CIWS (MIT/LL)
NEXRAD Products
March 2012
WMSCR (Phase 1)
NIEC
PIREPs and Altimeter Settings
June 2012
CIWS Data Distribution Service (CDDS) (Phase 1)
Time Based Flow Management (TBFM)/Traffic Management Adviser (TMA)
CIWS Products (Static)
Feb. 2013
TBFM Information Sharing (IS) Service
TBD
Collaborative Arrival Planning (CAP) Data
Sept. 2013
STDDS
TFMS
ASDE-X (Tracks), Runway Visual Range, EFSTS, and TDLS Data
2013
TFMS/FIPS
FIPS Products

22. Producer/Consumer Deployment Status (cont.)
Consumer(s)
Product(s)
Cutover
WMSCR (Phases 2 and 3)
TBD
Web services for Requests for PIREPs and Altimeter Settings
2013
CDDS (Phase 2)
TBFM/TMA
CWIS Products (Dynamic)
Enhanced Weather Information Network Server (WINS) Disseminations (EWD)
Weather Data
AIM
TFMS
SUA Information
2014
ITWS
Airlines/
Other External
ITWS Products
SWIM FDPS
FDPS Products
2015

23. NEMS Data-flows: NAS-to-NAS23

24. NEMS Data-flows: Non-NAS Consumer24

25. NEMS Data-flows: Non-NAS Producer25

26. SWIM Governance WHO is responsible WHAT must they do
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 v1.1
SWIM Service Lifecycle Management Processes v1.0
HOW must they do it
Technical Standards coordinated with NAS Enterprise Architecture
TV-1 Technical Standards Profile
TV-2 Technical Standards Forecast
FAA Standards
FAA-STD-063 XML Namespaces
FAA-STD-064 Web Service Registration
FAA-STD-065 Web Service Description Documents
FAA-STD-066 Web Service Taxonomies
SWIM Version Management Processes v1.0
NSRR User Guides
TV-1 Technical Standards Profile
TV-2 Technical Standards Forecast 26 26

27. Scope of SWIM Governance
It’s a part of FAA Governance
FAA Governance
What is FAA/ATO/NAS governance?
ATO Governance
NAS Governance
Establishing decision making rights associated with the FAA/ATO/NAS
Establishing mechanisms and policies used to measure and control the way FAA/ATO/NAS decisions are made and carried out
SWIM Governance
What is SWIM governance?
SOA Governance is defining the process and assigning the rights to make the decisions pertaining to:
ATO automation systems development life cycle
ATO automation operations processes
The way automation systems and processes support the goals of the service unit
What measures to use and policies to follow to address such concerns as:
Service registration
Service versioning
Service ownership
Service discovery and access
Deployment of services and composite applications
Security for services
I see governance as having its largest role during the development phase, not the in-service phase. Could this be clarified?    How exactly does it ensure the business value of a program?    
Extension of NAS governance focused on the lifecycle of services to ensure the business value of SWIM
SWIM Governance is a catalyst for improving overall NAS, Air Traffic Organization (ATO) and FAA governance 27 27

28. SWIM Compliance SWIM Compliance Definition: Verification Mechanisms
“Verified conformance to SWIM Policies.” (SWIM Service Lifecycle Management Processes v1.0)
Verification Mechanisms
Manual review of artifacts
Governance-enabling technology
NSRR
Testing Tools (Actional, Lisa, etc…)
SWIM Web Service Security Compliance Test Kit (SWIM WS-S CTK)
Policy Servers
XML Gateways
Enterprise Service Management (ESM) software 28

29. Service Lifecycle Management Decisions
Technical Review Board (TRB)
Investment Decision Authority
SWIM Governance Team
Proposal decision taken by TRB, but primarily predicated on SWIM Suitability Analysis
In Service Decision (ISD) Authority 29 29

30. SOA Suitability Criteria
NAS Enterprise View
Potential for existing SWIM service to be utilized or tailored to meet the requirement
Potential for other users to benefit from the information exchange
Potential hazards for exposing data through SWIM (e.g., proprietary data, non-FAA user access)
Program View (Cost, Schedule, Technical)
Life-Cycle Cost of SWIM versus other solutions
System performance requirements: latency, transmission rate, bandwidth, response time, overhead, etc.
Safety/certification requirements
Information security requirements
Existing architecture/vendor solution impacts 30 30

31. International Coordination
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) 31

32. 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
FAA is using the NIST definition of cloud computing. The National Institute of Standards and Technology (NIST), an agency of the U.S. Department of Commerce, provides the following definition of cloud computing in NIST Special Publication (NIST SP ):
Cloud computing is as a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models.
NIST prescribes the following five primary characteristics of cloud computing:
On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service's provider. This involves online provisioning.
Broad network access. Capabilities are available over the network and accessed through standard mechanisms. For public cloud, this includes use of the Internet. For private clouds, this typically involves enterprise Wide Area Networks (WANs) supplemented with local area networks (LANs).
Resource pooling. The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand.
Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out, and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service. Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.

33. There are several ways to learn more about SWIM
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 33

34. Questions and Comments?
?Ask participants: “Are there any questions about the material covered in this section?” 34 34