# Presentation: 390314

## FAA System-Wide Information ManagementProgram Overview for SWIM-SUIT Public Lauch

**FAA System-Wide Information Management****Program Overview for ****SWIM-SUIT Public Lauch**

**Donald Ward**
**Program Manager**
**FAA SWIM Program**
**April 2007**

## SWIM Foundation for U.S. Next Generation System  

**NextGen**

**Trajectory-Based Operations**
**Aircraft Data Communications**
**Performance-Based  **
**Operations and Services**
**Separation Management**
**Collaborative TFM**
**Precision Navigation **
**Weather Integration**
**Surveillance Services**
**Network-Centric **
**Information Sharing**

** ****ERAM Enhancements**
*Automated Problem Resolution*
**Concept Demonstrations**
*Trajectory-Based Ops/High Density*
***Infrastructure ***
*Robust Flow of Information*
**TFM-M Enhancements**
*Time-Based Metering*
**   ****Terminal Enhancements**
*Merging and Spacing Tools*
**RNP/RNAV Expansion**
*Precise Navigation*
**Data Communications**
*Flight Intent Downlink*
**ADS-B**
*Aircraft Separation*
**SWIM/Net-Enabled Weather**
*Net-Centric Information Sharing*

**ERAM**
**TFM-M**
**STARS/CARTS**
**RNP/RNAV**
**Airspace Mgmt Program**
**Initial ADS-B**
**Initial SWIM**

**Current Programs**

**Notes:**
There is no direct linkage between services provided and costs to operate the NAS.

Operations are going up
Trend is for smaller aircraft

## What is FAA SWIM?

**What is FAA SWIM?**

**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 FAA agility**
**Improve ability to share information with European providers**

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

## Problems with Current FAA Information Sharing

**WARP**

**IDS/****ERIDS**

**ATOP**

**CIWS**

**TFM**

**TMA**

**STARS/**
**ARTS/**
**TAMR**

**ERAM**

**ASDE**

**Inter-****Agency**

**Problems with Current FAA Information Sharing**

## FAA Future with SWIM

- SWIM Core Capabilities

***standard data interfaces***

***Enterprise Information Distribution***

**FAA Systems**

**FAA Future with SWIM**

## SWIM Program Approach

- Segment 1

- Rqmts & Design

- Integration & Test

- ERAM & TFM Changes

- AIM Changes

- Terminal Data Services

- Weather (CIWS, WMSCR, ITWS)

- Segment 2 Implementation

- Research, Demonstrations, and Trials

## SWIM Segment 1 Services

**SWIM Segment 1 Services**

**SWIM**
**Office**

**Special Use Airspace Automation**

## SWIM Segment 1 (2009 – 2013)

**Main Components of Segment 1**
- There are no equipage requirements in SWIM Segment 1
- There are no rule changes as result of SWIM
- Many Segment 1 activities are targeted for improving information flow to reduce delays
- More surface data exchange between Terminal systems and Traffic Flow Management/En Route
- Pre-departure clearance updates for En Route automation
- Automated Special Use Airspace (SUA) updates
- Greater dissemination of weather products (CIWS, ITWS, and WMSCR)
**Segment 2 is tentatively planned for 2011 – 2015 and will have more focus on external data exchange.**

- Contents not final until program is approved by Joint Resource Counsel (June 2007)

**Notes:**
The airlines are interested in these features because:

No equipage in Segment 1 means no cost is imposed on the airlines
More surface data means that TFM will have more accurate planning and prediction of departure times.  This will help reduce unnecessary delays.  More importantly, when this information is fed to TFM it will thus be available to send to the airlines... and they have shown a big interest in surface data.   SWIM will also help automate reroute information between TFM and ERAM
Pre-departure clearance updates will result in better agility/response to system changes.
Automated SUA updates will result in better commercial use of restricted zones (when the military is not using them).  This means less delays in the system and more routing options.
Weather Products:  Most airlines are very interested in getting data feeds of CIWS and ITWS  (Corridor Integrated Weather System and Integrated Terminal Weather System).  By modifying these weather products to SWIM standards, the data will become available via web services in a more usable, and less expensive, format for the airlines.  

## SWIM Capital Budget

- Dollars are in millions
- FY09 – FY13 will be adjusted as part of Final Investment Decision, June 2007

## SWIM Extended Team

**SWIM Extended Team**

## Global Networking for Atlantic Trials

**Automated decision support and information sharing for safety, capacity, and security**
- Identify issues for interoperability, information exchange, and shared situational awareness
- Apply core principles of system wide information  management and network centric enterprise services
- Explore/validate concepts of use and procedures

**Initiate trials to enable international communications, collaboration & coordination**
- Enhance International situational awareness
- Reduce response times, ambiguities, and error rates

**Architected to work with any Net-Centric Architecture**
- Uses data/protocol adapters to connect with FAA SWIM Service Bus for data exchange

## Demo:  “Green Trans-Atlantic Flights”

**In-Trail****Procedures**

**Timed Oceanic****Exit & TOD**

**Tailored****Arrivals**

**CTO**

**CTO**

**En Route**

**Oceanic**

**En Route**

**Terminal**

**Terminal**

**Departure****Airport**

**Arrival****Airport**

**Global Networking for Up-To-Date Trajectory Information Exchange**

**Phased Implementation of Oceanic 4D Trajectory Operations**

***Timed Oceanic Exits:*** Management of oceanic flow to meet CTO at exit and/or TOD
- More efficient management of delays from down stream constraints
- Lower emissions and fuel burn

***Tailored Arrivals:*** Data-linked clearance prior to TOD for CDA that is adjusted for airspace constraints, traffic, and a targeted time of arrival
- Lower emissions, noise, and fuel burn

**Notes:**
Track regions:

NOPAC – North Pacific Route System
PACOTS – Pacific Organized Track System
CENPAC – Central Pacific Route System
SOPAC – South Pacific Route System

NAT OTS – North Atlantic Organized Track System
EUR-NAM – Europe-North America
EUR-CAR – Europe-Caribbean
WATRS – West Atlantic Route System

Flights:
	400,000 air carrier
	50,000 military and GA