System Wide Information Management (SWIM)

1. System Wide Information Management (SWIM) Program Overview

2. Agenda • Program Overview • Segment 1 • Segment 2 • Governance • Cloud Computing 2

3. Program Concept 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) 3

4. Business as Usual TAMR State of the System • 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 AIM R-TFMS WARP IDS/ERIDS ASDE-X ATOP ERAM STARS/ ARTS CIWS SWIM-Compliant Government Systems FAA Systems ERAM AIM TFMS Enterprise Management (SWIM) Inter-Agency CIWS TMA TFM TDDS ITWS FTI • Existing point-to-point hardwired NAS • Unique interfaces, custom designs TBFM LEGEND WMSCR SWIM-Compliant Non-Government Systems ATOP SWIM Segment 1 SWIM Future Services SWIM Adapter 4

5. Conceptual Overview NextGen Applications Non-FAA Users (e.g., Airlines, DoD,DHS, ANSPs) System Developers Controllers FAA Command Center Standards for Data Exchange AIXM FIXM WXXM SWIM Messaging Infrastructure FAA Telecommunications Infrastructure (FTI)

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

8. SWIM Schedule

9. SWIM Segment 1 Capabilities Weather COI Aeronautical Information Management (AIM) Community of Interest (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 Runway Visual Range (RVR) Publication Capabilities will be implemented as multiple services by SIPs through FY15 Reroute Data Exchange 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

12. Anticipated Segment 1 Products

13. Anticipated Segment 1 Products(cont.)

14. 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 The NSRR provides Interface Management for the NAS NSRR Discover and Retrieve Contract Publish and Register Contract • The NSRR is open to external users https://swimrep.faa.gov/soa/web/login Service Provider Service Consumer Exchange Messages 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

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)

17. 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 theRequest/ResponseMEP, 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 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 20

21. Producer/Consumer Deployment Status

22. Producer/Consumer Deployment Status (cont.)

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

24. NEMS Data-flows: Non-NAS Consumer 24

25. NEMS Data-flows: Non-NAS Producer 25

26. 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 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 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 SWIMGovernance What is SWIM governance? Extension of NAS governance focused on the lifecycle of servicesto ensure the business value of SWIM SWIM Governance is a catalyst for improving overall NAS, Air Traffic Organization (ATO) and FAA governance 27

28. SWIM Compliance • SWIM Compliance Definition: • “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 In Service Decision (ISD) Authority 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) • Asia/Pacific Flight Data Object Demo (May 2012)

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

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 www.faa.gov/nextgen/swim

34. Questions and Comments? 34