1. Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange By: Deborah Young Date: November 4, 2009 SWIM Program Update SWIM Segment 2 Progress Air Traffic Organization

2. 2 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 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 will not implement a separate infrastructure for Segment 1  SWIM will leverage existing infrastructures, processes, resources, and logistics chains that are part of the program offices implementing the 9 SWIM capabilities  SWIM Governance will establish operating rules for the stakeholders and their services/applications to ensure use of common protocols and interfaces, assisted by use of commercial software for some Core Services

3. 3 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 SWIM Segment 1 COI Capabilities AIM SUA Automated Data Exchange Weather CIWS Publication ITWS Publication PIREP Data Publication Flight & Flow Management Flight Data Publication Terminal Data Distribution Flow Information Publication RVR Publication Reroute Data Exchange

4. 4 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009

5. 5 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009  ITWS Publication prototype service subscribed to by: UPS Harris Corporation Global Information Grid  Train SWIM Implementing Program developers on SWIM middleware  Develop CIWS Publication prototype service  SIPs begin systems engineering and design  Finish design for the AIM portion of the SUA Automated Data Exchange  Conduct SOA suitability assessments of other FAA programs  Start operating the initial SWIM registry  Initiate procurement of SWIM registry version 2.0  Conduct JRC FID for FY11-15  Finalize Segment 2 definitization  Initiate Segment 2 FID JRC preparation FY2009 Activities

6. 6 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009  SWIM Program Office  Oversee SIP systems engineering and development  Perform governance functions on SIPs and other FAA programs to ensure interoperability between systems  Continue SOA suitability assessment of other FAA programs  Continue operating the initial SWIM service registry, COTS repository, wiki, and web site  Procure SWIM service registry 2.0  Initial registry doesn’t meet all requirements  Finalize Segment 2 requirements  Conduct Segment 2 FID JRC FY2010 Planned Activities

7. 7 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009  SWIM Implementing Programs  Test and deploy the AIM portion of SUA Automated Data Exchange  Code and test CIWS Publication  Code and test ITWS Publication  Code and test PIREP Data Publication  Code initial Flight Data Publication  Finish requirements and prototype for Terminal Data Distribution  Code and test Reroute Data Exchange FY2010 Planned Activities (cont’d)

8. 8 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 88 SWIM Segment 2 Approach  Understanding NextGen and NAS Objectives which Require SWIM Services (FY12-16)  Support anticipated data exchange needs of NextGen Programs  Requirements based on needs to satisfy the mid-term (FY12-16) NextGen Operational Improvements and the Enterprise Roadmap  Informal COIs will be used to validate the results of the Operational Improvements/Roadmap analysis  Requirements for Segment 2 focus on providing infrastructure core services rather than business applications or capabilities

9. 9 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 SWIM Segment 1 ( SV4 NAS Enterprise Services ) 9

10. 10 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 SWIM Segment 2

11. 11 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 Alternatives Description  Alt. 1 – Expanded Federated Approach  Continue current Segment 1 approach expanded beyond the 7 SWIM Implementing Programs (SIP’s)  Alt. 2 - Messaging Backbone  Alt. 1 plus Centralized Messaging Services  Alt. 3 - SOA Core  Includes all SOA Core Services from SV-4

12. 12 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 Alternatives Comparison

13. 13 Federal Aviation Administration Presented to: Network Centric Demonstrations and Prototypes Technical Interchange Date: November 4, 2009 SWIM 2 Investment Analysis  Objective: Final Investment Decision for SWIM Segment 2 by summer 2010  Costs and benefits for each alternative  Economic analysis to determine preferred approach