System Wide Information Management (SWIM)

1. System Wide Information Management (SWIM) “SWIMposium” - An Informational Panel on the SWIM Program FAA Staff SWIM Program September 22, 2009

2. Agenda • Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond • How to Learn More • Q&A

3. SWIM and the Evolution of Air Transportation SWIM supports FAA’s long-term goals for the Next Generation Air Transportation System to: • Allow more aircraft to fly more closely together on more direct routes • Reduce delays and congestion • Provide benefits for the environment and the economy through reductions in carbon emissions, fuel consumption, and noise Specifically, SWIM will support these goals by: • Providing data and services to support better real-time planning • Streamlining communications • Connecting more FAA systems to more customers

4. Terminal Controllers En Route Controllers Non-FAA Users (e.g., Airlines, DoDDHS, ANSPs) FAA Command Center NextGen Applications SWIM Infrastructure for Messaging FTI IP Backbone Conceptual Overview

5. Agenda • Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond • How to Learn More • Q&A

6. Program Concept SWIM is an IT infrastructure program that will operate in the background to provide data to authorized users SWIM will: • Implement a Service-Oriented Architecture (SOA) in the National Airspace System (NAS) • Allow the FAA to create new system interfaces more quickly and cheaper than is possible today • Facilitate the data-sharing that is required for NextGen SWIM is not: • A set of avionics equipment • A substitute for NAS modernization programs • An FTI replacement

7. Host ETMS WARP IDS/ERIDS ASDE ATOP ERAM STARS/ ARTS/ TAMR CIWS Inter-Agency TMA TFM STARS CARTS/ 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 Today Enterprise Management FAA Systems ERAM AIM TFMS CIWS TDDS - Existing point-to-point hardwired NAS - Unique interfaces, custom designs SWIM Compliant Government Systems SWIM Compliant Non-Government Systems FTI ITWS LEGEND TBFM WMSCR DOTS SWIM Segment 1 SWIM Future Segment SWIM Adapter

8. SOA standardizes the necessary interfaces and behavior to support interaction SOA establishes services as the mechanism by which needs and capabilities are brought together SOA provides an organizing and delivery paradigm that derives greater value by reusing existing software solutions rather than duplicating capabilities What is SOA?SOA organizes technical capabilities in a standard way to allow flexible accomplishment of constantly changing demands Service S Capabilities performed by one for another to achieve a desired outcome Oriented O When capabilities are self-contained and independent to enable a collection of services to be linked together to solve a business problem Architecture A The fundamental organization of a system embodied in its capabilities, their interactions, and the environment

9. Key Aspects of SWIM • Business and IT Alignment • Systems design is driven by a market forces model (supply and demand) • Systems are grown to evolve with the environment rather than designed and built as a fixed structure (a city vs. a building) • Adaptability • Agility: allow for rapid enhancement of services capability • Flexibility: enable on-demand composition and restructuring of services to meet business needs • Interoperability • Priority on exposing capability for rapid consumption • Create ability for unanticipated utilization (emergent behaviors) • Reuse • Maximize utility of the services provided • Maximize utilization of existing services (eliminate/reduce development) • Scalability • Distribution of effort: widely distribute the development of capability • Distribution of value: enable wide access to capability

10. What types of information are shared through SWIM? SWIM facilitates more efficient sharing of NAS information such as: • Airport surface management information • Flight planning data • Notices to Airmen (NOTAMs) • Status of navigational aids • Airspace restrictions

11. Current SWIM Capabilities Capabilities will be implemented as multiple services over the next five years

12. FY09 Accomplishments • ITWS Publication prototype service subscribed to by UPS, Harris, and DoD; MOA signed with NWA and FedEx • Trained SIP developers on FUSE software • SIPs have started systems engineering and design • Conducting SOA suitability assessments of other FAA programs • Finishing design for the AIM portion of SUA Automated Data Exchange • Developing CIWS Publication prototype service • Received Final Investment Decision for Segment 1B (FY11-15) • Phase 1 SWIM Registry operational • SWIM COTS Repository operational

13. SWIM Program Management - Points of Contact • Jim Eck, Director of ATC Communication Services • James.Eck@faa.gov • (202) 493-5901 • Ahmad Usmani, SWIM Program Manager • Ahmad.Usmani@faa.gov • (202) 267-3391

14. Agenda • Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond • How to Learn More • Q&A

15. SWIM-Compliance Objectives • Define Governance • Outline Policies • Introduce Processes

16. Governance Basics • Definition • Ensuring and validating that assets and artifacts within the architecture are acting as expected and maintaining a certain level of quality. (Gartner, 2007) • Components • WHO is responsible • Governance Authority • Service Providers • Service Consumers • WHAT must they do • Governance Policies • Service Contracts • HOW must they do it • Standards • Governance Processes

17. SWIM Compliance Overview • Goals • Interoperability • Reusability • Key Principle • Adherence to Standards • Governance Policies • Service Oriented Architecture (SOA) Strategic • Service Design-Time • Runtime and Operational • Governance Processes • How to comply with Policies SWIM Compliant

18. Compliance Aspects • Use of Common data standards • Consistent approach for describing and publishing services • Use of Common message formats and transports • A Common SWIM-wide security profile • Use of prescribed message products and protocols

19. 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)

20. Simplified NextGen NAS SV-4 Framework Enterprise Governance Administrative Services Interaction Services Data/Network Support Services Run-time Management Mission Services Support Services (Content Management /Data Acquisition) Services Provisioning Management SOA Governance SOA Core Services Technical Infrastructure Services

21. SWIM Governance Policies Outline • STRATEGIC SOA • SOA Technology Acquisition • Enterprise Architecture • Opportunity Management for SOA Services • Interoperability, Reuse and Standards • SWIM Enterprise Services Registry/Repository • SOA/SERVICE DESIGN POLICIES • Namespace and Schema • Service Interface Design • Services Technical and Design • Information Security • Service Development Process • Service Lifecycle Management • Services Operations Readiness • Service Provisioning • Service Consumer • RUNTIME AND OPERATIONAL • Messaging and Routing • Runtime Security • Service Management • Maintenance and Support

22. Governance Process Development • Bottom-up • Ensure every Policy is captured in Process definition • Top-down • Decompose the Service Lifecycle model

23. SWIM-Compliance - Points of Contact • Jim Robb, Requirements and Governance Lead • Jim.Robb@faa.gov • (202) 267-8357 • Paul Jackson, Requirements and Governance • Paul.Jackson@faa.gov • (202) 267-3789 Risk Management

24. Agenda • Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and requirements for your JRC package • Segment 2 and Beyond • How to Learn More • Q&A

25. FUSE Software Overview • Progress Fuse software is required for SWIM compliance and to implement Segment 1 Core Services • Supports SWIM goals of interoperability and reuse • The SWIM Program office supports the ability of Programs to procure the FUSE software, training, support and consulting

26. 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 • Iona was purchased by Progress Software on September 12, 2008 • FUSE remains and continue to evolve

27. Users Users NAS Application System Functions Application Application NAS System NAS System Service Interface Service Interface Service Interface Service Interface Messaging Messaging Interface Management Value-Added Services SWIM Service Functions Enterprise Service Management Service Security Boundary Protection Secure IP Network Connectivity Naming & Addressing Identity & Certificate Management Intrusion Detection and Response Information Technology Infrastructure Functions SWIM Functional Architecture

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

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

30. SWIM Core Services Product Stack Interface Management Interface Specification Progress Artix Interface Discovery Registry HQ Schema Management Enterprise Service Management Service Monitoring Artix Enterprise Service Configuration Progress Artix t HQ Management n System Monitoring Registry e Service m e g a n Security a M Authentication y Authorization Progress Security c Apache CXF i l Audit o P Messaging Reliable Messaging Publish - Subscribe Apache Camel Apache Servicemix Apache CXF Message Routing Artix Enterprise Management Service Apache Active MQ Artix ESB C ++

31. Progress FUSE Software • FUSE Suite • Apache Servicemix 3.x and 4.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)

32. SWIM Progress Support and Consulting Services • Non Segment 1 SIPs can buy support using the Progress contract • Additionally, Non Segment 1 SIPs can buy consulting services using Progress contract • More information on Progress software products is available at www.progress.com

33. Progress Training • Non Segment 1 SIPs can purchase training using Progress contract • Classes are being planned for Fall 2009 • FUSE 3.x Bootcamp (5 days) • Developer Training for Apache Active MQ 5.x (2 days) • Developer Training for Apache Servicemix 3.x and 4.x (2 days) • Developer Training for Apache Camel 1.x (2 days) • Developer Training for Apache CXF 2.x (2 days) • Administrator Training for FUSE HQ 3.x (2 days) • Artix for Developers (C++, Std) (4 days) • Artix for Developers (Advanced) (3 days) • Artix for Architects (2 days) • Artix RegRep Workshop (2 days) • Progress Actional Team Server Workshop (2 days) • Web Services Foundation Course (1 day) • Web Services and SOA Boot Camp (4 days) • FUSE Architect Course (3 days)

34. FUSE Software - Point of Contact • Jeff Hobbs, SWIM Implementation Lead • Jeffery.Hobbs@faa.gov • (202) 267-9772

35. Agenda • Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond • How to Learn More • Q&A

36. SWIM and Your JRC Package • Acquisition Management System (AMS) and SWIM Service Lifecycle • Suitability Analysis • Process • Results • Scorecard • Infrastructure Requirements • Development Follow-up

37. Role of the SWIM Program Office • The SWIM program will work with you to determine the cost of SWIM-compliance • SWIM will work with you to document required hardware, software, and standards in your SWIM Infrastructure Implementation Plan • SWIM will participate in your ISD/IOC

38. Stages of SWIM Service Lifecycle Model

39. Service Lifecycle Stages

40. SWIM Suitability – Gateway to Stage 1

41. Scorecard and Linkage to AMS

42. Gate #1 to Stage 2 - Suitability Scorecard 28 total items Step #1 Summary of scoring Step #2 Value range Step #3

43. SWIM Infrastructure Implementation Plan • Provides a mechanism for • Documenting Service Provider/program requirements for SWIM infrastructure • A “contract” between your program and SWIM • Addresses program infrastructure requirements • SWIM functional areas: messaging (patterns, protocols), enterprise service management, security • SWIM non-functional areas: availability, latency, reliability, etc. • SWIM locations: endpoints, types, etc.

44. SWIM and JRC Requirements - Points of Contact • Jim Robb, Requirements and Governance Lead • Jim.Robb@faa.gov • (202) 267-8357 • Deborah Young, Program Control Lead • Deborah.Young@faa.gov • (202) 267-8003 Risk Management

45. Agenda • Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond • How to Learn More • Q&A

46. Segment 2 Overview • Goals • Support anticipated data exchange needs of NextGen Programs • Build on Segment 1 Governance, for all NAS programs that score well on the SOA Suitability Checklist • Expand SWIM infrastructure to include additional Enterprise Service Management, Security, other SOA infrastructure services, and Core services that were delegated to the SIPs in Segment 1 • Segment 2 JRC planned for summer FY10, to request baseline funding for FY12 – FY15

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

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

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

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