System Wide Information Management SWIM SP3 SWIM Program

System Wide Information Management (SWIM) SP/3 SWIM Program Overview Presented to: Asia/Pacific Air Traffic Service Message Handling System (AMHS)/SWIM Workshop By: Hoang Tran, FAA International Telecommunication Service Location: Chiang Mai, Thailand Date: 5 -6 March , 2012 Federal Aviation Administration

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 2

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 ― Ensure adherence to common standards (Governance) ― Allow the FAA to create new system interfaces more quickly and costeffectively than is possible today ― Facilitate the data-sharing that is required for the Next Generation Air Transportation System (Next. Gen) • NAS Programs using SWIM Enterprise Infrastructure will receive SWIM support during their Investment Analysis phase as well as during their Development phase of the new services FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 3

SWIM Concept • Migrate the NAS to SOA – Makes it easier to establish interfaces between systems • Get the right information to the right place at the right time – Facilitate Shared Situational Awareness – Facilitate Collaborative Decision Making (CDM) • Establish governance over service implementations • Represents significant cultural change FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 4

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

SWIM is a SOA Implementation • SWIM provides: ― SOA technology infrastructure ― Governance to ensure that information management standards and processes are followed • Leads to consistent service development, operation, and management across the enterprise • By following SOA standards and principles: ― SWIM makes services available on a network ― Enables systems on the network seeking those services to invoke them without having to change or adapt to the underlying implementation of the service (i. e. , loose coupling) FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 6

What types of information are shared through SWIM? SWIM facilitates more efficient sharing of Air Traffic Management (ATM) system information, such as: • Airport surface management information • Weather data • Flight planning data • Notices to Airmen (NOTAMs) • Status of navigational aids • Airspace restrictions FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 7

Benefits 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 FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 8

Options for NAS Evolution More point-to-point unique interfaces – NAS SYSTEM INTERFACES IN THE LEGACY ENVIRONMENT – BUSINESS Host AS USUAL ETMS WARP New decisions linked to old data constructs IDS/ ERIDS ASDE Cumbersome data access outside the NAS ATOP ERAM STARS/ CIWS Unique interfaces, custom designs MS S FTI CA STARTS/ RS Existing point-to-point hardwired NAS TF TDDS TFM Inter. Agency – ENTERPRISE MANAGEMENT (SWIM) ERAM AIM CIW TMA SWIM-Compliant Government Systems FAA Systems ITWS ARTS/ TAMR Costly development, test, maintenance, CM SWIM-Compliant Non-Government Systems WM FM TB SC R ATOP LEGEND SWIM Segment 1 SWIM Future Services SWIM Adapter FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 9

Conceptual Overview FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 10

Segmented Approach to SWIM • SWIM Segment 1: ― Implementation of a set of federated services in the NAS with SWIMprovided governance, standards, and software to support development of reusable SOA services ― SWIM provides requirements, schedule, and funding to seven other NAS programs; tracks progress via formal monthly reviews ― Segment 1 results in SOA services deployed to all Air Route Traffic Control Centers (ARTCCs), 39 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 new “SWIM Implementing Programs” (SIPs) and facilitates transition by Segment 1 SIPs FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 11

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 12

SWIM Segment 1 • Federated Approach – 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: – Overall Program Cost and Schedule – SWIM System Engineering and Requirements Management – Definition and Maintenance of Program Level Agreements (PLAs) with implementing programs – Governance of SIPs – SIPs are responsible for: – Managing the development and deployment of allocated SWIM requirements per the SWIM Final Program Requirements (FPR) document and in accordance with the SWIM Program Schedule – Reporting progress against schedule FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 13

SWIM Segment 1 Enterprise Infrastructure and Tools • NAS Service Registry/Repository (NSRR), a central repository to help users discover, use and (whenever possible) reuse Web services • Developer Tools: – SWIM Commercial-Off-The-Shelf (COTS) Products Repository (SCPR), which provides a single point from which implementing programs can retrieve COTS products, tools, and artifacts – SWIM Wiki, which provides a forum for developers and other members of the SWIM development community FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 14

Service Registry/Repository • A Service Registry is a resource that provides controlled access to data necessary for the implementation and governance of Service Oriented Architecture (SOA) projects • A Repository is a database containing the artifacts and metadata that constitutes a SOA registry Note: These are usually referenced as one product, often called a Registry/Repository • A Registry/Repository provides: – Centralized discovery – Centralized deployment – Lifecycle governance – Policy and standards enforcement – Automated service notification mechanism – Central to any SOA infrastructure in the promotion of reuse FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 15

Registry/Repository Discover and Retrieve Contract Service Consumer Service Registry Exchange Messages Publish and Register Contract Service Provider "In fact, it was the existence of a discovery mechanism that primarily distinguished SOA from previous distributed architecture models. " Principles of Service Design FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 16

NSRR • The SWIM Program has stood-up a National Airspace System (NAS) Service Registry/Repository • This creates a central repository to help users discover, use and, whenever possible, reuse Web services • The Hewlett Packard Systinet V 3. 2. product is being used to implement the NSRR FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 17

NSRR • Publishers manage and store metadata and service artifacts about their services in a single location. This information includes: – Service Description – Classifications: Protocol Types, Service Category, and Delivery Channels – Access Information: Interface Requirements Documents (IRDs), Web Service Definition Language (WSDL) files, and endpoints • Potential consumers search the registry in order to discover NAS services that will be/are available for consumption. • Potential consumers have access to metadata and service artifacts prior to consuming a service. They can then use this information to request services from the providers. FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 18

NSRR and Governance • Governance organizations ensure that publishers are in compliance with policies and requirements • Contracts between publishers and consumers are created, negotiated, and enforced • The lifecycle of the NAS services can be effectively managed and service changes can be efficiently approved and implemented FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 19

SCPR • Provides a single point from which implementing programs can retrieve COTS products, tools, and artifacts. • Stores current and previous versions of supported COTS products. • Enables the program to more effectively manage version control by ensuring that implementing programs are only using tested, supported and validated versions of the COTS products. FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 20

SCPR FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 21

SWIM Wiki • Provides a forum where developers and other members of the SWIM development community can: – prepare, distribute and update living documents; – post topics for discussion including issues, concerns, and lessons learned; and – store important information and resources such as guidance, standards, and integration patterns FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 22

SWIM Wiki FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 23

SWIM Segment 1 Capabilities Aeronautical Information Management (AIM) Community of Interest (COI) Special Use Airspace (SUA) Automated Data Exchange Weather COI Flight & Flow Management (F&FM) COI 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 FY 15 FAA SWIM Overview 5 -6 March, 2012 Reroute Data Exchange Federal Aviation Administration 24

Segment 1 Status Summary • 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: • Weather Message Switching Center Replacement (WMSCR) PIREP Data Publication • AIM SUA Automated Data Exchange • Pre-Departure Reroute ― Three capabilities are on schedule and within budget allocations: • STDDS • Flow Data Publication • RVR Data Publication ― One capability is has been replanned but is expected to be on schedule and within budget allocation: • Flight Data Publication Service (FDPS) FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 25

Segment 1 Products Capability ITWS Data Publication Products • • • Airport Lightning Warning Configured Alerts Forecast Accuracy Forecast Contour Forecast Image Gust Front TRACON Map Microburst TRACON Map Precipitation 5 nm Precipitation Long Range Precipitation TRACON Tornado Alert • Vertically Integrated Liquid Water (VIL) Mosaic (1 km resolution) • VIL 2 -hr. Forecast • Echo Tops Mosaic (1 km resolution) • Echo Tops 2 hr. Forecast • Satellite Mosaic WMSCR PIREP • PIREPs Data Publication CIWS Data Publication FAA SWIM Overview 5 -6 March, 2012 • Tornado Detections Wind Profile • Storm Motion (SM) Storm Extrapolated Positions (SEP) 5 nm • SM SEP Long Range • SM SEP TRACON • Terminal Weather Text Normal • Anomalous Propagation (AP) Indicated Precipitation • AP Status • Gust Front Estimated-Time-To-Impact (ETI) • • • Hazard Text 5 nm Hazard Text Long Range Hazard Text TRACON ITWS Status Information Microburst Automatic Terminal Information Service (ATIS) Runway Configuration Storm Motion 5 NM Storm Motion TRACON Terminal Weather Text Special Wind Shear ATIS • • • Echo Tops Forecast Contours Growth & Decay Contours Forecast Accuracy: Echo Tops Forecast Accuracy: Std. Precip Forecast Accuracy: Winter Precip Storm Info: Echo Top Tags Storm Info: Leading Edges Storm Info: Motion Vectors VIL Forecast Contours (Std. Mode) VIL Forecast Contours (Winter Mode) • Altimeter settings Federal Aviation Administration 26

Segment 1 Products (cont. ) Capability Products AIM SUA Data Exchange • SUA data, dynamically via an improved Air Traffic Control (ATC) Graphical User Interface (GUI) • SUA data, dynamically provided in the • AIXM SUA definitions Aeronautical Information Exchange Model (AIXM) standard STDDS • Airport Surface Detection System. Model X (ASDE-X) streaming data service • Surface Movement Events (SME) • Tower Departure Events (TDE) Flow Data Publication • Flow Constrained Area (FCA) • Airspace Flow Program (AFP) • Ground Delay Program (GDP) • Ground Stops (GSs) • Reroutes • Advisories FDPS • Flight Information Service (FIS) • Track Information Service (TIS) • Airspace Utilization Information Services • Communication Information Services • Beacon Code Management Information Services • Status Information Services • Metering Information Services • Interfacility Information Services FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 27

Benefits of SWIM-Enabled Weather Services • ITWS CIWS – Without SWIM, ITWS and CIWS only distribute images, not data, to subscribers – Through SWIM, ITWS and CIWS distribute data, which may be integrated into situational displays, providing subscribers with the same information as the FAA • WMSCR PIREPs – Through SWIM, WMSCR data is distributed in near-realtime, allowing subscribers to process the information FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 28

Example: ITWS • There are more than 10, 000 airports in the US, yet less 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 FAA SWIM Overview 5 -6 March, 2012 ITWS information accessed via Internet Federal Aviation Administration 29

ITWS Team on SWIM The SWIM infrastructure and data formats left us perfectly positioned to begin immediately leveraging the capabilities of the Google geospatial applications once there was a requirement for visualizing our data. The integration tools we needed were right at our fingertips as they already existed as part of the SWIM Development Environment. – David Reiser , ITWS Team, Volpe Center FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 30

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 31

SWIM Segment 2 • SWIM Segment 2 received Authorization to Proceed (ATP) from the FAA Joint Resource Council (JRC) in November 2010 – Authorized 2 years of funding (FY 11 -12), divided into planning and procurement activities for prototypes and work toward a Segment 2 Final Investment Decision (FID) ― SWIM to provide the enterprise SOA infrastructure within the NAS for individual programs to use ― SWIM will support the Technical Review Board (TRB) in ensuring that SOA governance complies with NAS regulations ― 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 FAA Telecommunications Infrastructure (FTI), building on the Airport Surface Detection Equipment - Model X (ASDE-X) prototype FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 32

Segment 2 Core Services supported by SWIM include: • Messaging - reliable messaging as well as publish/subscribe services • Interface Management - interface specification, discovery, and schema management • Security –authentication, authorization, and audit services • Enterprise Service Management - service monitoring, service configuration, and system monitoring NEMS is providing Messaging Services FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 33

SWIM Segment 2 Enterprise Infrastructure (via FTI) • NEMS, which will provide the SWIM Segment 2 Enterprise Service Bus (ESB) via Oracle Web. Logic, Oracle Internet Directory (OID), and other COTS products • Domain Name Service (DNS), which will provide naming and name-to-address resolution services across the Enterprise • Network Time Protocol (NTP) and Precision Time Protocol (PTP), which will provide time synchronization services across the Enterprise FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 34

NEMS Deployment • DEX is the operational prototype NEMS • Current DEX deployment includes messaging nodes at: – NAS Enterprise Security Gateways (NESGs) (Atlanta and Atlantic City) – FTI National Test Bed (FNTB) (Atlantic City) – R&D Domain (Atlantic City) • Four internal NAS nodes will be installed: early 2012 – Used for NAS-to-NAS distribution of SOA data products – Node Locations: ACY, ZTL, OEX, ZLC • Implement 2 -way SOA data exchange – Allows for non-NAS Producers to feed data into the NAS – Planned completion date: Fall 2012 • DEX integration with Active MQ – Planned completion date: March 2012 FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 35

NEMS Message Node Locations Current NEMS messaging nodes at: Key Current Message Node Planned Message Node FAA SWIM Overview 5 -6 March, 2012 §Atlanta and Atlantic City NESGs §FNTB §R&D Domain Four internal NAS nodes will be installed beginning of 2012 at: §ACY, ZTL, OEX, ZLC Federal Aviation Administration 36

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 37

SOA Governance • Without a controlling entity, SOA is not only challenging to manage, but it invites chaos because of its open and distributed nature • Because of this nature, SOA needs a management and controlling entity ‒ Governance assures keeping services at a defined level in terms of integrity, performance, reliability, and currency ‒ Governance also enforces security of enterprise data and privacy of information shared across boundaries ‒ It enforces integrity and reliability of data ‒ It ensures a certain level of performance and quality of all services FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 38

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 v 1. 1 – SWIM Service Lifecycle Management Processes v 1. 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 v 1. 0 – NSRR User Guides FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 39

Segment 2 Governance • Programs will use the enterprise SOA infrastructure provided by SWIM • Programs will not develop their own redundant enterprise SOA infrastructure • Programs will meet SWIM-compliance requirements as required by Technology Review Board (TRB) • Disputes related to implementation of enterprise SOA will be resolved by the TRB FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 40

Scope of SWIM Governance It’s a part of FAA Governance What is FAA/ATO/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 FAA Governance ATO Governance NAS Governance SWIM Governance What is SWIM governance? Extension of NAS governance focused on the lifecycle of services to ensure the business value of SWIM FAA SWIM Overview 5 -6 March, 2012 SWIM Governance is a catalyst for improving overall NAS, Air Traffic Organization (ATO) and FAA governance Federal Aviation Administration 41

SWIM Compliance • SWIM Compliance Definition: – “Verified conformance to SWIM Policies. ” (SWIM Service Lifecycle Management Processes v 1. 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 FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 42

Service Lifecycle Management Decisions TRB Investment Decision Authority SWIM Governance Team In Service Decision (ISD) Authority FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 43

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 FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 44

SOA Suitability Assessments SOA Score FY Program 11 Alaska Satellite Telecommunications Infrastructure (ASTI) 11 ATO Resource Management Tool 11 Automatic Terminal Information System (ATIS) Low 11 Aviation Environmental Design tool (AEDT) High 11 Aviation Safety Knowledge Management Environment (ASKME) Segment 2 High 11 Facility Security Risk Management (FSRM) (Phase 2) 11 Flight Standards Inspector Aircraft Replacement (FSIAR) Low 11 Instrument Flight Procedures Automation (IFPA) (Includes Tech Refresh) High 11 Logistics Center Supply System (LCSS) Segment 2 11 Mobile Airport Surveillance Radar (MASR) High 11 Surveillance and Broadcast Services (SBS) High 11 Surveillance Interface Modernization (SIM) High 12 Tower Flight Data Manager (TFDM) High Low Medium SWIM provides SOA Suitability Assessments as NAS programs appear on a JRC watch list FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 45

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 46

Aircraft Access to SWIM (AAt. S) • • • AAt. S provides aircraft with a connection to NAS services enabled by SWIM AAt. S will improve aircraft situational awareness: – Aircraft will have the same information the FAA uses to make ATM decisions AAt. S Concept: – AAt. S will initially use existing NAS and aircraft infrastructure – Information delivered via AAt. S is not intended for uses that directly affect the trajectory of the aircraft Data services via AAt. S – Services available on the NEMS will be available via AAt. S – The scalability of this capability is key: • New data elements can be added more quickly, more easily, and less expensively • New NAS data will be made available to aircraft by granting operators access to the additional data elements provided by SWIM Note: – FAA has no plans at this time to acquire a system or infrastructure to specifically support AAt. S – AAt. S will not replace existing or planned FAA systems FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 47

AAt. S Activities • Demos, Tests, and Simulations – Beginning in late 2011 – Continuing to 2014 – Scope is to: • Define and validate capabilities and interoperability solutions • Define and validate operational changes and impacts • Demonstrate the architecture in both domestic and oceanic/remote areas • Architecture and technical profile definition underway – Functional architecture is being developed in phases • Demo – to support AAt. S simulations and infrastructure development (available for review) • Mid-term – to support AAt. S capability IOC in early 2014 (March 2012) • Far-term – to support long term evolution (September 2012) – Integrated Operational & Technical Requirements Document (IO&TRD) • 2012 • Includes “Quick Start Users Guide” FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 48

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 49

Collaboration with Europe • Past – Memorandum of Cooperation (MOC) between FAA and the European Organization for the Safety of Air Navigation (EUROCONTROL) for joint R&D – In place for 25 years – Work with EUROCONTROL will continue, but will focus on near term and procedural issues • New – MOC between U. S. /FAA and European Union/Single European Sky ATM Research (SESAR) for civil aviation R&D – Primary purpose of the MOC was to create a legal mechanism for Next. Gen – SESAR collaboration – Other joint aviation research (e. g. , metrics or safety) may be added as new annexes FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 50

FAA-SESAR Work Groups • Five Work Groups: – Work Group 1: Transversal Activities – Work Group 2: Information Management – SWIM interoperability – Information Management Interoperability – Meteorological (MET) Information Exchange – Work Group 3: Trajectory Management – Work Group 4: Communication/Navigation/Surveillance (CNS) & Airborne Interoperability – Work Group 5: Collaboration Projects FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 51

Collaboration with Japan • FAA-Japan Civil Aviation Bureau (JCAB) Harmonization of Future Air Transportation System (FATS) Working Group – Harmonize future US and Japanese air traffic management systems – Met on May, 2011: San Francisco • Next. Gen/Collaborative Actions for Renovation of Air Traffic Systems (CARATS) updates: • SWIM update, common terminology, and demonstration status • Flight Object (FO) demonstration status and data dictionary discussion • Global Unique Flight Identifier (GUFI) discussion • Established plan for performance assessment – Met October, 2011: Tokyo • Next. Gen/CARATS updates: • Flight Data, Performance Metrics, 2012 SWIM Activities FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 52

Collaboration with China • Recent FAA-Civil Aviation Authority of China Air Traffic Management Bureau (CAAC/ATMB) workshops and demonstrations: – December 2010, Shenzhen – March 2011, Atlantic City – September 2011: Washington, DC – October 2011: Beijing – Spring 2012: Washington, DC FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 53

Agenda • SWIM Overview • SWIM Segment 1 • SWIM Segment 2 • SWIM Governance • Aircraft Access to SWIM (AAt. S) • International Coordination • Cloud Computing FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 54

Cloud Computing Cloud computing is “a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources… that can be rapidly provisioned and released with minimal management effort or service provider interaction. ” — National Institute of Standards and Technology (NIST) FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 55

FAA Cloud Computing Approach • FAA National Airspace System (NAS) and non-NAS organizations will work collaboratively on cloud adoption under the leadership of the FAA’s Chief Information Officer (CIO) – The SWIM Program will be responsible for implementing cloud in the NAS – The FAA IT Infrastructure Board will be responsible for oversight and guidance for FAA’s non-NAS IT infrastructure, including cloud computing and data center consolidation efforts FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 56

FAA Cloud Overview • Driver: 25 Point Implementation Plan To Reform Federal Information Technology Management (Vivek Kundra, U. S. Chief Information Officer (CIO), December 9, 2010) – “Each agency will identify three “must move” services within three months, and move one of those services to the cloud within 12 months [December 2011] and the remaining two within 18 months [June 2012]. ” • Driver: Federal Cloud Computing Strategy (Kundra, February 8, 2011) – Potential for addressing inefficiencies and reducing costs – Improves government service delivery by allowing us to respond faster FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 57

FAA Cloud Objectives • Support the Office of Management and Budget (OMB) priority on cloud computing • Reduce FAA’s total unit cost for servers and data storage • Increase the agility of the Information Technology (IT) infrastructure • Reduce the time to market of new IT capability • Meet system security requirements as we pursue cloud computing • Seek standardized solutions that avoid vendor lockin FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 58

Questions and Comments? FAA SWIM Overview 5 -6 March, 2012 Federal Aviation 59 Administration 59

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 FAA SWIM Overview 5 -6 March, 2012 Federal Aviation Administration 60