1. System-Wide Information Management (SWIM) Program and Delivery1

2. Agenda Program Overview and Status Core Services
ATM Services and Data Flows
Prototyping
Future Segments

3. SWIM Program Structure

4. SWIM Program Team Key Roles
Program Management
Responsible for leading and directing the activities of the SWIM Team in the development, test, and deployment of SWIM; Resource Planning and External
Acquisition
Responsible for Acquisition Services Program Management, Acquisition Strategy Planning, Acquisition Contract Management
Program Control
Responsible for Business Management, Risk Management, Metrics Management, Earned Value / Schedule Management / Investment Baseline Reviews, Investment Analysis, Budgeting and Capital Planning Requirements (e.g. OMB Exhibit 300)
Evolution & Coordination
Responsible for Planning & Prototyping Management, Stakeholder Coordination, Concept Exploration, Program Evolution, Future Segment / Service Planning, Prototyping
Responsible for definition and management of SWIM functional and non-functional requirements, (i.e. Security, Safety, Configuration/Interface Management, Quality, and other specialty engineering) and the definition and management of the architecture to meet SWIM requirements and SWIM Governance (program and technical) throughout the system and services lifecycle
Requirements & Governance
Implementation
Responsible for Implementation Management, SIP Coordination, SIP Engineering Support, SWIM Lab Management, Software Component Selection

5. Segment 1 Overview FTI NESG NWS ATCSCC ARTCC 1 AOCs AOCs NNCC WJHTC
ERAM
AIM SUA
NESG
NNCC
WJHTC
FTI
WMSCR
TFMS
CIWS
ERAM
TDDS
TRACON 1
NNCC = National Network Control Centers in Atlanta and Salt Lake City
AOC = Airline Operational Center
TFMS DRC
TDDS
ATCT 1
VNTSC
TDDS
ITWS

6. Program Status
Joint Resources Council (JRC) Final Investment Decision was made on 20 June 2007
Two-year baseline (FY09 and FY10) approved
SWIM returned to the JRC in FY09 for approval to complete the development and deployment of SWIM Segment 1on 15 July 2009
Five-year baseline (FY11 – FY15) approved
Segment 2 JRC planned for summer FY10, to request baseline funding for FY12 – FY15
Working with 7 other FAA program offices to implement the 9 capabilities in SWIM Segment 1

7. Current SWIM Capabilities
SIP – SWIM Implementing Programs
An alternative to a centralized infrastructure, which would otherwise be designed and deployed by SWIM PMO
Mitigates risk of multiple, overlapping deployments in key FAA ATC facilities
Maximizes use of existing contractors; shortens time to get SWIM services available for NextGen programs
IARD in September 2005, IID in July 2006
Nine Segment 1 capabilities were derived from Communities of Interest, and a SWIM Business Case was presented to the JRC in June 2007
SWIM received approval for FY09 and FY10 funding and associated activities at the June 2007 Final Investment Decision (FID)
JRC direction to SWIM was to return in 2009 with refined cost estimates for review and approval by the JRC for the remaining years of SWIM Implementation.
Based on development contractor estimates
AJF recommends requesting funding for FY11 – FY15
Capabilities will be implemented as multiple services over the next five years

8. Segment 1 Program Overview
Nine Segment 1 capabilities were derived from Communities of Interest:
Aeronautical Information Management (AIM)
Flight & Flow Management (F&FM)
Weather
SWIM is not implementing a separate infrastructure for Segment 1
SWIM is leveraging existing infrastructures, processes, resources, and logistics chains that are part of the program offices implementing the 9 SWIM capabilities
SWIM Governance is ensuring use of common protocols and interfaces, assisted by use of commercial software for some Core Services
Moving to the beginning of the SWIM program, we have defined a walk before run implementation plan that marry’s well with our major automation platforms and their current integration windows. Once instantiated in the FAA acquisition system, later segments of the SWIM implementation will look to consolidate core services and provide governance through a SWIM compliance key metric for all new acquisitions.

9. SWIM Is Federated NAS Domains NAS SWIM Federation CIWS ERAM ITWS TFM
Tactical Guideline: In large organizations with semiautonomous BUs, subsidiaries and external partners, a "federated" approach to SOA is the most effective in overcoming political, organizational and technical hurdles.
NAS
CIWS
ERAM
NAS Domains
ITWS
SWIM Federation
TFM
AIM
TDDS
WMSCR

10. Segment 1 Schedule
Note: This schedule shows risk-adjusted dates.

11. Priorities for FY10
Provide SWIM-compliant information to more external users/agencies/aircraft
Procure and start operating SWIM service registry v2.0
Deploy AIM SUA Automated Data Exchange
Conduct Segment 2 JRC Final Investment Decision
Respond to Integrated Baseline Review (IBR) findings

12. Agenda Program Overview and Status Core Services
ATM Services and Data Flows
Prototyping
Future Segments

13. Core Services Components
Core Services SWIM supports include:
Interface Management
Messaging
Security
Enterprise Service Management

14. Publisher Requirements for SWIM-Compliance
Use of FUSE Software
SOAP Message Processing
Java Message Service (JMS) Provider Standardization (Apache Active MQ)
Supported Message Formats and Transports
SOAP-over-HyperText Transfer Protocol (HTTP)/HyperText Transfer Protocol Secure (HTTPS)
eXtensible Mark-up Language (XML)-over-HTTP/HTTPS
SOAP-over-JMS
XML-over-JMS
SOAP Attachments
Message Transmission Optimization Mechanism
JMS Message Type - Text message
Registry / Repository
Discoverability – Web Services Description Language (WSDL)
Categorization – SWIM Taxonomy
Service Management – Java Management Extensions (JMX)

15. Systems Engineering Deliverables
“GFE from SWIM” package for SIPs
Package will contain:
Service Container Software
SIPs will implement and administer servers to run SWIM-provided service container software
Core Services
At a minimum, standards will be specified for all core services
Governance, policy, and guidance
SWIM Approved Products List

16. FUSE Software Contract
Contract award to Iona Technologies on
August 18, 2008
Indefinite Delivery Indefinite Quantity
Base year + 12 option years
Contract options:
Software
Documentation
Support Licenses
Training
Consulting Services

17. Progress FUSE Software
FUSE Suite
Apache Servicemix 3.x
Apache CXF 2.x
HQ 3.x
Apache Camel 1.x
Apache Active MQ 5.x
Artix Suite
Artix Registry/Repository
Artix ESB C++
Artix Connect for WCF
Artix Security
Artix Enterprise Management Service Plug-in
DataXtend Semantic Integrator (DXSI)
Progress Actional Team Server (MindReef SOAPScope)

18. XML Gateway
Currently, three vendors have met the FAA's XML Gateway requirements and have successfully passed a technical evaluation of their product's installation and initial configuration, as well as system performance, including:
Layer 7 Technologies - Secure Span product
Cisco Systems, Inc. - ACE XML Gateway product
Vordel, Inc. - VXG2 XML Gateway product
Their products were deemed capable of providing support to the SWIM Implementing Programs (SIPs)
This QVL is valid through March 31, 2015
The QVL will be reviewed annually

19. Agenda Program Overview and Status Core Services
ATM Services and Data Flows
Prototyping
Future Segments

20. AIM COI FTI FAA HQ ARTCC ATCSCC Current SUA Status and SUA updates
ERAM
NASR
ERAM
Current SUA Status and SUA updates
ARTCC
ERAM
SUA updates
ATCSCC
FTI
SAMS
SUA updates
Goals:
Improved SUA status data – in terms of consistency and timeliness – respond to updates more dynamically
Controllers will be able to use this better SUA status data to make better use of SUAs for reroutes – thereby increasing capacity

21. ITWS, CIWS, WMSCR products ITWS, CIWS, WMSCR products
Weather COI
VOLPE
WJHTC
ARTCC
ITWS
ITWS products
CIWS
ERAM
CIWS Products
NWS
PIREPs
FTI
Gateway
FTI
ITWS, CIWS, WMSCR products
Publishing ITWS and CIWS data to external users
Capturing more PIREPs and distributing this information to NWS
NNCC = National Network Control Centers in Atlanta and Salt Lake City
ITWS, CIWS, WMSCR products
PIREPs & Altimeter data
NNCC
AOCs
WMSCR

22. F&FM: ERAM and Terminal SWIM
ZDC
WJHTC
ATCSCC
TFMS
SAMS
NORAD
SUA Data
Flight Data
Gateway
(FTI)
ICE
FTI
Flight Data
Flight Data
ERAM
TDDS
This diagram shows two of the Segment 1 capabilities: Flight Data Publication and Terminal Data Distribution
ERAM will be the authoritative source for flight data; Terminal/tower/TFM are all recipients of this flight data. Towers will be able to get full routes of flight (currently character-limited due to field width on paper strips).
TDLS
EFSTS
ARTCC
RVR
ASDE-X
Terminal Cluster
(TRACON & TOWER)

23. F&FM: TFMS and Terminal SWIM
ARTCC
ERAM
ZDC
TFMS
DRC
Flow Data, Reroute Data
Flow Information, Surface, & Reroute Data
(Backup Data)
WJHTC
TFMS
TPC
FTI
Surface Data
TDDS
Flow Information, RVR, and Reroute Data
This diagram shows the TFM and Terminal capabilities
Flow Information Publication, RVR Publication, and Reroute Data Exchange
Flow data – related to GDPs, GSs, AFPs, FCAs, MITs
TDDS will provide much more surface data than is currently available; many systems and external users will benefit from this data
TDLS
EFSTS
AOCs
AOCs
RVR
ASDE-X
Terminal Cluster
(TRACON & TOWER)

24. Agenda Program Overview and Status Core Services
ATM Services and Data Flows
Prototyping
Future Segments

25. ITWS/CIWS Prototyping
Two programs are actively participating in SWIM prototyping
SWIM-Compliant ITWS and CIWS data products are now available
ITWS Publication prototype service subscribed to by UPS, Harris, and DoD; MOA signed with NWA and FedEx
VIL = estimate of the mass of water suspended in a square meter of a storm (kg/sq.m)
Configured Alerts service will include airport winds data and real-time ribbon display alerts, which are updated whenever an event notification is received for the requested
airport

26. ITWS-CIWS Summer 2009 Product List

27. Total of 25 Additional Products Total of 47 Products by End of 2010
ITWS-CIWS 2010 Product List
ITWS Products
CIWS Products
AP Indicated Precipitation
Storm Info : Echo Top Tags
AP Status
Storm Info : Leading Edges
Gust Front ETI
Storm Info : Motion Vectors
Hazard Text 5nm
VIL Forecast Contours (Standard Mode)
Hazard Text Long Range
VIL Forecast Contours (Winter Mode)
Hazard Text TRACON
Echo Tops Forecast Contours
ITWS Status Information
Growth & Decay Contours
Microburst ATIS
Forecast Accuracy : Echo Tops
Runway Configuration
Forecast Accuracy : Standard Precipitation
Storm Motion 5NM
Forecast Accuracy : Winter Precipitation
Storm Motion TRACON
Lightning
Terminal Weather Text Special
Terminal Weather Graphics
Wind Shear ATIS
14 Additional Products
11 Additional Products
Total of 25 Additional Products
Total of 47 Products by End of 2010

28. ITWS Prototype Service Demonstration

29. Segment 2 Prototyping Conducted at SWIM Lab at FAA Technical Center
Prototype implementation of an Enterprise Service Bus (ESB)
Purpose is to help refine requirements for SWIM Segment 2
VIL = estimate of the mass of water suspended in a square meter of a storm (kg/sq.m)
Configured Alerts service will include airport winds data and real-time ribbon display alerts, which are updated whenever an event notification is received for the requested
airport

30. Agenda Concept Architectural Context Program Overview and Status
Core Services
ATM Services and Data Flows
Prototyping
Future Segments

31. SWIM Roles
Leadership in Developing Enterprise Service Orientation in the NAS
Understanding NextGen and NAS Objectives which Require SWIM Capabilities
Identification and Evaluation of Information Management Technologies and Processes for the NAS Enterprise
Governance via Industry Standards

32. SWIM SOA Suitability Checklist

33. Suitability Scorecard
28 total items
Step #1
Summary of scoring
Step #2
Step #3
Value range

34. NASEAF SV4 NAS Enterprise Services (SWIM Segment 2)

35. Near Term SWIM Segment 2 SWIM Air SWIM Interagency SWIM International
Operation Services Environment Definition (OSED)
Requirements
Architecture
SWIM Air
SWIM Interagency
SWIM International
Federated vs Consolidated

36. Segment 2: Desired Capabilities
Desired capabilities include:
Current Special Use Airspace (SUA) status
Current Temporary Flight Restrictions (TFRs)
Improved information on Notices to Airmen (NOTAMs)
Automatic Terminal Information Service (ATIS) information
Automated Weather Observing Systems (AWOS) information
More timely flight plans filed
Improved real-time delay reporting
Current route closures and corresponding reroutes status
Improved Airport surface lineups status reporting
Establishment of single centralized route database

37. Mid Term SWIM Segment 3 SWIM Air SWIM Interagency SWIM International
Operation Services Environment Definition (OSED)
Requirements
Architecture
SWIM Air
SWIM Interagency
SWIM International
SOA to Cloud Computing?

38. SWIM Web Site