# Presentation: 451629

## System Wide Information Management (SWIM)

**Segment 1 Details and Community of Interest Processes**

-  RTCA 2007 Forum

-  Ahmad Usmani, SWIM Program Manager (Acting)

- September 18, 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 to share data between FAA systems.

How SWIM increases speed for new interfaces:  Use of standard interfaces reduces customization time.  Plus, XML protocols eliminate the need for “information consumers” to write special parsing programs 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**

## Communicating via SWIM: One Example 

## SWIM Segment 1 Overview 

**SWIM Segment 1 Overview**** **

**ARTCC 1**

**TRACON 1**

**ATCT 1**

**WJHTC**

**FTI**

- TFMS TPC
- CIWS
- ERAM
- TDDS

- TDDS

- WMSCR

**ATCSCC**

- SAMS

**VNTSC**

- ITWS

- TDDS

**AOCs**

**AOCs**

**NNCC**

- ERAM

## Program Status

**Joint Resources Council (JRC) Final Investment Decision was made on June 20**
- Two-year baseline (FY09 and FY10) approved
- SWIM will return to the JRC in FY09 for approval of the rest of Segment 1 (FY11-13)
**A kick-off meeting with SWIM Implementing Programs (SIPs) was conducted July 17, 2007; next meeting to be held in October**

**Notes:**
Working with 7 other FAA program offices to implement the 9 capabilities in SWIM Segment 1

## JRC Decision Requested (and Approved)

**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 initial deployment of the following Segment 1 capabilities:
- SUA Automated Data Exchange
- Flight Data Publication
- CIWS Publication
**In-service decisions are delegated to implementing programs**
- CIWS, ERAM, ITWS, AIM, TDDS, TFM, WMSCR

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

## SWIM Segment 1 COI Capabilities

## AIM COI

**AIM COI**

**SAMS**

**ATCSCC**

**FTI**

**SUA updates**

**FAA HQ**

**SUA updates**

**Current SUA Status and SUA updates**

**Notes:**
Goals:

 Improved SUA status data – in terms of consistency and timeliness – respond to updates more dynamically

 Controllers will be able to use this better SUA status data to make better use of SUAs for reroutes – thereby increasing capacity

## F&FM: ERAM and Terminal SWIM

**F&FM: ERAM and Terminal SWIM**

**WJHTC**

**ATCSCC**

**ERAM**

**ARTCC**

**FTI**

**Flight Data**

**SUA Data**

**SAMS**

**TFMS**

**ICE**

**NORAD**

**Gateway**
**    ****(FTI)**

**EFSTS**

**TDLS**

**ASDE-X**

**TDDS**

**Terminal Cluster **
**(TRACON & TOWER)**

**RVR**

**Flight Data**

**Flight Data**

**Notes:**
This diagram shows two of the Segment 1 capabilities: Flight Data Publication and Terminal Data Distribution

ERAM will be the authoritative source for flight data;  Terminal/tower/TFM are all recipients of this flight data.  Towers will be able to get full routes of flight (currently character-limited due to field width on paper strips).

## F&FM: TFMS and Terminal SWIM

**   ****AOCs**

**ZDC**

**Flow Data, Reroute Data**

**ARTCC**

**F&FM: TFMS and Terminal SWIM**

** ****Surface Data**

**TFMS **
**DRC**

** ****(Backup Data)**

**ERAM**

** ****AOCs**

**FTI**

**EFSTS**

**TDLS**

**ASDE-X**

**TDDS**

**Terminal Cluster **
**(TRACON & TOWER)**

**RVR**

-  **Flow Information, RVR, and Reroute Data**

-  **Flow Information, Surface, & Reroute Data**

**Notes:**
This diagram shows the TFM and Terminal capabilities

Flow Information Publication, RVR Publication, and Reroute Data Exchange
	Flow data – related to GDPs, GSs, AFPs, FCAs, MITs

TDDS will provide much more surface data than is currently available; many systems and external users will benefit from this data

## Weather COI

**VOLPE**

**ITWS**

**NNCC**

**Weather COI**

**ITWS products**

**WMSCR**

**AOCs**

**WJHTC**

**CIWS**

**FTI**

**ARTCC**

**PIREPs & Altimeter data**

**ERAM**

**NWS**

**PIREPs**

**ITWS, CIWS, WMSCR products**

**CIWS Products**

**ITWS, CIWS, WMSCR products**

**Notes:**
Publishing ITWS and CIWS data to external users

Capturing more PIREPs and distributing this information to NWS

NNCC = National Network Control Centers in Atlanta and Salt Lake City

## SWIM High-Level Program Schedule

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

## FY08 Goals

**Complete SWIM Service Specification Document (SvSD)**
**Validate current Segment 1 approach via prototyping at WJHTC and select commercial product(s) to provide required SWIM Core Services capabilities**
**Begin Segment 2 Definitization**
**Prepare for FY09 return to JRC for Segment 1 Baseline FY11-FY13**

## Community of Interest Process

## COI Concept

**Guidance for Implementing Net-Centric Data Sharing:  **
- DoD 8320.02-G, 12 Apr 06
- Definition of COI
-   “a collaborative group of users who must exchange information in pursuit of their shared goals, interests, missions or business processes and who therefore must have [a] shared vocabulary for the information they exchange”

## COI Definition

**Community of Interest = core community of processing systems plus the stakeholders that require access to the derived product information**
**Based on information needs, not systems**
**To support SWIM Segment 1, three COIs were identified:**
- Aeronautical Information Management
- Flight and Flow Management
- Weather

## COI Participants

**COI Leadership**
- Leads are domain system engineers
**COI Membership**
- Producers of Information
- Consumers of Information
- Stakeholders
- Advisory Members
- SMEs, as needed

## COI Process

**COI Process**

**COI-1**

**COI-2**

**COI-3**

**COI-4**

**COI-5**

**                ****ATO-E**

**ATO-T**

**ATO-W**

**                  ****ATO-R**

- 1.  SWIM Program Office establishes and supports COI teams to develop Concept of Use,  requirements, and planning activities.  COI teams staffed by front line service units

- 2.  COI  Leads provide cost, schedule, and technical requirements to the SWIM Program Office

**SWIM Program Office**

- 3.  SWIM Program Office performs budget formulation function

- 4.  Fiscal Year funding is appropriated to the SWIM Program Office

- 5.  SWIM Program Office establishes Service Level Agreements with performing Directorates and/or Service Units w/cost, schedule, funding, metrics, and oversight mechanisms

## Cross COI Objectives

**Address Cross COI/Cross Domain Issues**
- Exchange “lessons learned”
- Work scheduling issues
**Introduce SWIM Technical/Policy Guidance and receive COI feedback**
**Interface with FAA Enterprise Architecture Board (EAB), Chief Systems Engineers, and JPDO**
- Align SWIM Implementation with NextGen goals
- Provide responses to JPDO and EAB requests for information

## COI Plans Beyond SWIM Segment 1

**Possible Future COIs**
- Surveillance
- NAS Management
**Future SWIM Segment Development**
- Identify candidate functions for future SWIM segments
- Help develop business cases for new functions

## Reminder

**COIs are bigger than SWIM**
- SWIM was the first program to benefit from the COI process
- Many other programs and activities can benefit from the COI process and from the COIs that have already been established