# Presentation: 411761

## System Wide Information ManagementSegment 1

**Final Investment Decision**** **

- Members of the Joint Resources Council

-  Don Ward, SWIM Program Manager

- June 20, 2007

## What is SWIM?

**What is SWIM?**

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

_**SWIM will**_**:**
**Lower information costs**
**Increase speed to establish new interfaces**
**Increase common situational awareness**
**Increase NAS agility**

**Notes:**
How SWIM lowers information costs:   Uses standard interfaces and new protocols such as XML.  This greatly reduces the amount of software that must be created share data between FAA systems.

How SWIM increases speed for new interfaces:  Use of standard interfaces reduces customization time.  Plus, xml protocols eliminates the need for “information consumers” to write special parsing program to figure out which data they need.

The ability to manage data at a lower cost (and faster setup speed) means more data sharing... which increases common situational awareness and improved agility.

## Business as Usual

**Today**

**State of the System**

- - Existing point-to-point hardwired NAS
- - Unique interfaces, custom designs

- - More point-to-point
- unique interfaces
- - Costly development, test, maintenance, CM
- - New decisions linked to old data constructs
- - Cumbersome data access outside of NAS

**Enterprise ****Management**

## One Example 

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

**Notes:**
ERAM F&FM solves DSP issues at ZNY and special “patch” issues at San Juan
ERAM/TFM will use SWIM capabilities for SUA data exchange and for exchange of reroutes
ERAM F&FM replaces the HADDS/FDIO interface and adds capability for 2 way comm with Terminal systems
WMSCR addresses the issue of PIREPs not being entered by controllers, not getting to NWS
AIM SUA addresses the lack of real-time (dynamic) updates to SUA areas
ITWS and CIWS provide their products to AOCs and to NWS, assisting in common sit awareness

## SWIM Segment 1 COI Capabilities

## SWIM High-Level Program Schedule

**Note:** This schedule does not show risk-adjusted dates.

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

**Notes:**
We plan to return to the JRC in FY09 for approval of the SWIM Segment 1 baseline for FY11 – FY13.
Implementing programs will integrate SWIM-provided COTS packages into their respective systems
Implementing programs will conduct in-service decisions in accordance with their approved deployment (ISD) processes

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

## Metrics and Associated Milestones

**(Section I.C. Table 2 of Exhibit 300 Report)**

| Fiscal Year | Measurement Area | Measurement Category | Measurement Indicator | Baseline | Planned Improvements to the Baseline | Actual Results |
| --- | --- | --- | --- | --- | --- | --- |
| FY07 -FY11 | Customer Results | Customer Benefits | Cost of developing an application-to-application I/F | Initial baseline in FY07, refined baseline in FY08 | Reduce by
10% in FY10, 
20% in FY11 |  |
| FY07 -FY13 | Mission and Business Results | IT Security | Cost to deliver data services via external security gateway | Initial baseline in FY07, refined baseline in FY08 | Reduce by 30% per system in FY09, by 60% per system in FY10, maintain improvement through FY13 |  |
| FY09 - FY13 | Processes and Activities | Cycle Time and Timeliness | Frequency of NAS-wide SUA updates | Baseline in FY09 | Reduce cycle time by 50% in FY10, maintain improvement through FY13 |  |
| FY09 - FY13 | Technology
 | Quality and Functionality | Automate the capture of PIREP Data Publication | Initial baseline in  FY09, refined baseline in FY10 | Increase by 
50% in FY11,
75% in FY12,
80% in FY13 |  |
| FY09 – FY13 | Customer Results
 | Customer Benefits | Number of NAS users subscribing to SWIM Data Services | Number of potential users: initial baseline in FY09, refined baseline in FY10 | 5% of potential users subscribe in FY11,
10% in FY12,
20% in FY13 |  |

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

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

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

## Integration into the Enterprise Architecture

**Integrated into NAS Enterprise Architecture Automation Roadmap**
**Engineering Artifacts to Support Architecture Integration:**
- Executive Views
- Operational Views
- System Views

## NAS Enterprise Architecture Automation Roadmap

- Source: NAS Architecture 6 Website

## System Interdependencies

**SWIM Segment 1 has interdependencies with the following systems:**
- CIWS
- ERAM
- ITWS
- NASR
- SAMS
- TDDS
- TFMS
- WMSCR

## Risk Management

| Description of Risk | Risk Rating | Strategy for Mitigation | Current Status |
| --- | --- | --- | --- |
| Software development using SOA technology | High | Apply proven software development processes | Developing process w/programs |
| Unspecified / Changing Segment 1 requirements | Med | Develop use cases for every anticipated application | SWIM SE’s building cases w/COIs.   |
| Governance challenging: no. & complexity of apps. | Med | Hosting SWIM core services in legacy systems | Federated governance planning |
| Contract management | Med | Identify shortcomings early | Developing service level agreements (SLA) w/programs |
| Scope of Program | Med | Segment 1  -  small, sequential implementations | Developing SLA’s to maintain scope |
| Policy changes directed by FAA, DOT or OMB | Med | Network centric policies – Frequent liaison | Coordination initiated |
| Design Coordination & Interface Standards | Med | Integrate design – SOA flexibility – Ind.  standards | Standard specification started |
| Development of SWIM core services | Med | Identify correct core services | Core services identified w/COIs |
| Unmet requirements | Med | Establish clear requirements -Employ S.E. validation | Requirements allocated to programs |
| Infosec | Med | Identify security requirements, procedures |  fPR in coordination |
| Integration of FAA & COTS software | Med | Start with straightforward functions for segment 1 | Coordinating test requirements |
| Cost estimate may underestimate true costs | Med | Segment 1 - match cost & schedule to budget & plan | Cost estimate risk adjusted |
| Schedule estimate may be inaccurate | Med | Establish risk adjusted schedule | Schedule effort addressing risk |
| Benefit estimate may over-claim benefits | Med | Competitive procurement – flexible design | Benefits estimate risk adjusted |

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

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

**Notes:**
We plan to return to the JRC in FY09 for approval of the SWIM Segment 1 baseline for FY11 – FY13.
Implementing programs will integrate SWIM-provided COTS packages into their respective systems
Implementing programs will conduct in-service decisions in accordance with their approved deployment (ISD) processes