System Wide Information Management Segment 1

1. System Wide Information ManagementSegment 1 Final Investment Decision Members of the Joint Resources Council Don Ward, SWIM Program Manager June 20, 2007

2. SWIM is not: A set of avionics equipment A substitute for NAS modernization programs An FTI replacement SWIM is an information technology program that will operate in the background to provide seamless information to users who have a valid need for the data What is SWIM? SWIM will: • Lower information costs • Increase speed to establish new interfaces • Increase common situational awareness • Increase NAS agility

3. Host ETMS WARP IDS/ERIDS ASDE FAA Systems ATOP ERAM STARS/ ARTS/ TAMR CIWS Inter-Agency SWIM Compliant Non-Government Systems SWIM Core Capabilities SWIM Compliant Government Systems TMA TFM 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 of NAS Today Enterprise Management - Existing point-to-point hardwired NAS - Unique interfaces, custom designs

4. ASDE-X TFM currently plans to install several unique interfaces to collect surface data Instead TFM will have one interface to get the same data TDDS RVR EFSTS TDLS TFM TFM One Example

5. Program Overview • MNS/IARD in September 2005, IID in July 2006 • 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 “touched” by the 9 SWIM capabilities

6. SWIM Segment 1 COI Capabilities

7. SWIM High-Level Program Schedule Note: This schedule does not show risk-adjusted dates.

8. Decision Requested • Approve Segment 1 baseline for FY09 – FY10 • Proceed with selection of COTS software for SWIM core services • Proceed with design of all Segment 1 capabilities • Proceed with deployment of the following Segment 1 capabilities: • SUA Automated Data Exchange (SAMS/NASR software only) • Flight Data Publication (initial flight data services only) • CIWS Publication • In-service decisions are delegated to implementing programs

9. Performance Gap / Justification • FAA Flight Plan: Organization Excellence • Objective 2 – Improve Financial Management While Delivering Quality Customer Service • Reduce costs to deliver data services via external gateway • Reduce application-to-application development costs • Provide shared situational awareness through Flight Data Publication • Improve collaborative decision making • ATO SMP: Pathway 2 – Enhance Financial Discipline • P2.4 Reduce unit cost and improve value of operations • Automation of manual processes for capturing weather reports and updating SUA status • Cost avoidance by enabling early retirement of HADDS and FDIO

10. Metrics and Associated Milestones (Section I.C. Table 2 of Exhibit 300 Report)

11. SWIM Program Management Overview • SWIM PO is responsible for: • Overall Program Cost and Schedule • SWIM System Engineering and Requirements Management • Definition and Maintenance of Service Level Agreements (SLAs) with implementing programs • Governance • SWIM Implementing Programs are responsible for: • Managing the development and deployment of allocated SWIM requirements per the SWIM Final Program Requirements Document and in accordance with the SWIM Program Schedule • Reporting progress against schedule, providing monthly cost summary to SWIM PO per SLAs

12. SWIM Program Management Overview • SWIM Acquisition Strategy • SWIM will not deploy a separate infrastructure in Segment 1 • Will use existing programs (other than Terminal Data Distribution System) to deploy the 9 capabilities • EVM Approach • Each of the 9 capabilities will be tracked using EVM; data will be collected from the implementing program offices • Contract Types • SWIM Program Office will use existing contracts for engineering and integration activities FY08 – FY10 • Implementing Programs will use existing contracts to develop Segment 1 capabilities

13. SWIM Service Level Agreements • SLAs will be established between the SWIM PO and the implementing programs • SLAs will be established in two iterations • FY08 SLAs cover requirements and allocation of work to be conducted in FY08 • FY09 and beyond SLAs will cover details of requirements allocated to implementing programs, budget, EVM reporting requirements, and milestones • Status of FY08 SLAs • ERAM: in coordination • TFM: in coordination • Terminal: in coordination

14. Integration into the Enterprise Architecture • Integrated into NAS Enterprise Architecture Automation Roadmap • Engineering Artifacts to Support Architecture Integration: • Executive Views • Operational Views • System Views

15. NAS Enterprise Architecture Automation Roadmap Source: NAS Architecture 6 Website

16. System Interdependencies • SWIM Segment 1 has interdependencies with the following systems: • CIWS • ERAM • ITWS • NASR • SAMS • TDDS • TFMS • WMSCR

17. Risk Management

18. Issues • Acquisition strategy for Terminal Data Distribution System (TDDS) • Relationship to other NAS Processes • NAS Configuration Control Board • Enterprise Architecture Board • JRC Approvals • Insufficient Acquisition expertise in Program Offices that are critical to NextGen

19. Decision Requested • Approve Segment 1 baseline for FY09 – FY10 • Proceed with selection of COTS software for SWIM core services • Proceed with design of all Segment 1 capabilities • Proceed with deployment of the following Segment 1 capabilities: • SUA Automated Data Exchange (SAMS/NASR software only) • Flight Data Publication (initial flight data services only) • CIWS Publication • In-service decisions are delegated to implementing programs