ms powerpoint

Presented to:

By:

Date:

Federal AviationAdministration

System Wide Information Management (SWIM)

“SWIMposium” - An Informational Panel on the SWIM Program

FAA Staff

SWIM Program

September 22, 2009

2 2Federal AviationAdministration

1st Annual SWIMposiumSeptember 22, 2009

Agenda

• Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond• How to Learn More • Q&A



SWIM and the Evolution of Air TransportationSWIM supports FAA’s long-term goals for the Next Generation Air Transportation System to:• Allow more aircraft to fly more closely together on more direct

routes• Reduce delays and congestion• Provide benefits for the environment and the economy through

reductions in carbon emissions, fuel consumption, and noise

Specifically, SWIM will support these goals by:• Providing data and services to support better real-time planning• Streamlining communications• Connecting more FAA systems to more customers



Conceptual Overview

NextGen Applications

FTI IP Backbone

En RouteControllers

TerminalControllers

Non-FAA Users(e.g., Airlines, DoD

DHS, ANSPs)FAA

Command Center

SWIM Infrastructure for Messaging



Agenda

• Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package

• Segment 2 and Beyond • How to Learn More • Q&A



Program Concept

SWIM will:• Implement a Service-Oriented Architecture

(SOA) in the National Airspace System (NAS)• Allow the FAA to create new system interfaces

more quickly and cheaper than is possible today

• Facilitate the data-sharing that is required for NextGen

SWIM is not:• A set of avionics equipment• A substitute for NAS modernization programs• An FTI replacement

SWIM is an IT infrastructure program that will operate in the background to provide data to authorized users



Business as Usual

HostWARP

IDS/ERIDS

ATOP

CIWS

TFMTMA

STARS/ARTS/TAMR

ERAM

ASDE

ETMS

Inter-Agency

Today

State of the System

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

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

Enterprise Management

LEGEND

SWIM Segment 1

SWIM Future Segment

SWIM Adapter

FAA Systems

SWIM Compliant Non-Government

Systems

SWIM Compliant Government

SystemsFTI

TFMS

CIW

S

TDD

S

ITWS

WMSCR

AIM

TBFM

DOTS

ERAM

CA

RTS

/S

TA

RS



Capabilities performed by one for another to achieve a desired

outcome

When capabilities are self-contained and independent to enable a

collection of services to be linked together to solve a business problem

The fundamental organization of a system embodied in its capabilities,

their interactions, and the environment

Architecture

Oriented

Service

S

O

A

SOA standardizes the necessary interfaces and behavior to support interaction

SOA establishes services as the mechanism by which needs and capabilities are brought together

SOA provides an organizing and delivery paradigm that derives greater value by reusing existing software solutions rather than duplicating capabilities

What is SOA?SOA organizes technical capabilities in a standard way to allow flexible accomplishment of constantly changing demands



Key Aspects of SWIMBusiness and IT Alignment

– Systems design is driven by a market forces model (supply and demand)– Systems are grown to evolve with the environment rather than designed and built as a fixed

structure (a city vs. a building)

Adaptability– Agility: allow for rapid enhancement of services capability – Flexibility: enable on-demand composition and restructuring of services to meet business

needs

Interoperability – Priority on exposing capability for rapid consumption– Create ability for unanticipated utilization (emergent behaviors)

Reuse – Maximize utility of the services provided– Maximize utilization of existing services (eliminate/reduce development)

Scalability– Distribution of effort: widely distribute the development of capability– Distribution of value: enable wide access to capability



What types of information are shared through SWIM?SWIM facilitates more efficient sharing of NAS information such as:

• Airport surface management information

• Flight planning data• Notices to Airmen (NOTAMs)• Status of navigational aids• Airspace restrictions



Current SWIM Capabilities

Aeronautical Information Management (AIM) COI

Special Use Airspace (SUA)Automated Data Exchange

Weather COI

Corridor Integrated Weather System (CIWS) Publication

Integrated Terminal Weather

System (ITWS) Publication

Pilot Report (PIREP) Data Publication

Flight & Flow Management COI

Flight DataPublication

Terminal Data Distribution

Flow Information Publication

Runway Visual Range (RVR) Publication

RerouteData Exchange

Capabilities will be implemented as multiple services over the next five years



FY09 Accomplishments• ITWS Publication prototype service subscribed to

by UPS, Harris, and DoD; MOA signed with NWA and FedEx

• Trained SIP developers on FUSE software• SIPs have started systems engineering and design• Conducting SOA suitability assessments of other

FAA programs• Finishing design for the AIM portion of SUA

Automated Data Exchange• Developing CIWS Publication prototype service• Received Final Investment Decision for Segment

1B (FY11-15)• Phase 1 SWIM Registry operational• SWIM COTS Repository operational



SWIM Program Management - Points of Contact

• Jim Eck, Director of ATC Communication Services– [email protected]– (202) 493-5901

• Ahmad Usmani, SWIM Program Manager– [email protected]– (202) 267-3391



Agenda

• Introduction • Overview of the SWIM Program • SWIM-Compliance • FUSE Software Overview• SWIM and Requirements for Your JRC Package

• Segment 2 and Beyond• How to Learn More • Q&A



SWIM-Compliance Objectives

• Define Governance• Outline Policies• Introduce Processes



Governance Basics

• Definition– Ensuring and validating that assets and artifacts within the

architecture are acting as expected and maintaining a certain level of quality. (Gartner, 2007)

• Components– WHO is responsible

• Governance Authority• Service Providers• Service Consumers

– WHAT must they do• Governance Policies• Service Contracts

– HOW must they do it• Standards• Governance Processes



SWIM Compliance Overview

• Goals– Interoperability– Reusability

• Key Principle– Adherence to Standards

• Governance Policies– Service Oriented Architecture

(SOA) Strategic– Service Design-Time– Runtime and Operational

• Governance Processes– How to comply with Policies



Compliance Aspects

• Use of Common data standards• Consistent approach for describing and

publishing services• Use of Common message formats and

transports• A Common SWIM-wide security profile• Use of prescribed message products and

protocols



Requirements for SWIM-Compliance• Use of FUSE Software

– SOAP Message Processing– Java Message Service (JMS) Provider Standardization (Apache

Active MQ)• Supported Message Formats and Transports

– SOAP-over-HyperText Transfer Protocol (HTTP)/HyperText Transfer Protocol Secure (HTTPS)

– eXtensible Mark-up Language (XML)-over-HTTP/HTTPS– SOAP-over-JMS– XML-over-JMS

• SOAP Attachments– Message Transmission Optimization Mechanism

• JMS Message Type - Text message• Registry / Repository

– Discoverability – Web Services Description Language (WSDL)– Categorization – SWIM Taxonomy

• Service Management – Java Management Extensions (JMX)



Simplified NextGen NAS SV-4 Framework

Interaction Services

Mission Services

Support Services(Content Management /Data Acquisition)

SOA Core Services

Technical Infrastructure Services

Enterprise Governance

Administrative Services



SWIM Governance Policies Outline • STRATEGIC SOA

– SOA Technology Acquisition– Enterprise Architecture– Opportunity Management for SOA Services– Interoperability, Reuse and Standards– SWIM Enterprise Services Registry/Repository

• SOA/SERVICE DESIGN POLICIES– Namespace and Schema

– Service Interface Design

– Services Technical and Design

– Information Security

– Service Development Process

– Service Lifecycle Management

– Services Operations Readiness

– Service Provisioning

– Service Consumer

• RUNTIME AND OPERATIONAL– Messaging and Routing– Runtime Security– Service Management– Maintenance and Support


SOA Governance

StrategicSOA

Governance

Runtime and OperationalGovernance

Service Design-Time Governance

SOA Governance Service Desk

Support



Governance Process Development

• Bottom-up– Ensure every Policy is captured in Process definition

• Top-down– Decompose the Service Lifecycle model

Stage 1: Service

Proposal

Stage 2: Service

Definition

Stage 3a: New Service Development

Stage 5: Service

Deprecation

Approved service

Candidate service

New service proposal

Operational service

Retired service

Service update /patch

Rej

ecte

d pr

opos

al

Stage 3b: Service

MaintenaceOperational

service

Stage 6: Service

Retirement

Deprecated Service

Development State

Stage 4: Service

Operations

Operational service

Risk Management 23Federal AviationAdministration


SWIM-Compliance - Points of Contact

• Jim Robb, Requirements and Governance Lead– [email protected]– (202) 267-8357

• Paul Jackson, Requirements and Governance– [email protected]– (202) 267-3789



Agenda

• Introduction• Overview of the SWIM Program• SWIM-Compliance • FUSE Software Overview • SWIM and requirements for your JRC package

• Segment 2 and Beyond • How to Learn More • Q&A



FUSE Software Overview

• Progress Fuse software is required for SWIM compliance and to implement Segment 1 Core Services

• Supports SWIM goals of interoperability and reuse• The SWIM Program office supports the ability of

Programs to procure the FUSE software, training, support and consulting



FUSE Software Contract• Contract award to Iona Technologies on August 18, 2008• Indefinite Delivery Indefinite Quantity • Base year + 12 option years• Contract options:

– Software– Documentation– Support Licenses– Training– Consulting Services

• Iona was purchased by Progress Software on September 12, 2008

• FUSE remains and continue to evolve



SWIM Functional Architecture

Service Security

Intrusion Detection and Response

Information Technology Infrastructure Functions

SWIM Service Functions

Value-Added Services

Interface Management

Messaging Messaging

Naming & Addressing

Users Users

NAS System

Application

Service InterfaceService InterfaceService Interface

NAS System

ApplicationNAS ApplicationSystem Functions

Identity & Certificate Management

Enterprise Service

ManagementBoundary Protection

Service Interface

Secure IP Network Connectivity



Core Services Components

• Core Services SWIM supports include: – Interface Management

• Interface Specification• Interface Discovery• Schema Management• Service Invocation• SWIM Basic Profile

– Messaging • Reliable messaging routes will be provided on a case by

case basis by NAS integration partners



Core Services Components (cont’d)

• Core Services (cont’d): – Security

• Authentication and authorization will be manually coordinated and integrated by NAS integration partners

– Enterprise Service Management • Service monitoring and configuration

– Not to be done with SWIM administered HW or SW

– Will be accomplished by leveraging existing SIP program system monitoring capabilities and coordinating them across NAS programs



SWIM Core Services Product StackInterface Management

Messaging

Security

• P• o

• l•i• c•

y• •M•

a• n• a

• g•e•

m•e•

n• t

Enterprise Service Management

Apache Servicemix

Apache Active MQ

Apache CXF

Progress Artix Registry

HQ

Interface SpecificationInterface DiscoverySchema Management

Progress Artix Registry

Service MonitoringService ConfigurationSystem Monitoring

AuthenticationAuthorization

Audit

Apache Camel

Reliable MessagingPublish •-•SubscribeMessage Routing

HQ

Artix Enterprise Management

Service

Artix Enterprise Management

Service

Progress Security

Artix ESB C •++

Apache CXF



Progress FUSE Software• FUSE Suite

– Apache Servicemix 3.x and 4.x

– Apache CXF 2.x

– HQ 3.x

– Apache Camel 1.x

– Apache Active MQ 5.x

• Artix Suite

– Artix Registry/Repository

– Artix ESB C++

– Artix Connect for WCF

– Artix Security

– Artix Enterprise Management Service Plug-in

• DataXtend Semantic Integrator (DXSI)

• Progress Actional Team Server (MindReef SOAPScope)



SWIM Progress Support and Consulting Services

• Non Segment 1 SIPs can buy support using the Progress contract

• Additionally, Non Segment 1 SIPs can buy consulting services using Progress contract

• More information on Progress software products is available at www.progress.com



Progress Training• Non Segment 1 SIPs can purchase training using

Progress contract• Classes are being planned for Fall 2009

– FUSE 3.x Bootcamp (5 days)

– Developer Training for Apache Active MQ 5.x (2 days)

– Developer Training for Apache Servicemix 3.x and 4.x (2 days)

– Developer Training for Apache Camel 1.x (2 days)

– Developer Training for Apache CXF 2.x (2 days)

– Administrator Training for FUSE HQ 3.x (2 days)

– Artix for Developers (C++, Std) (4 days)

– Artix for Developers (Advanced) (3 days)

– Artix for Architects (2 days)

– Artix RegRep Workshop (2 days)

– Progress Actional Team Server Workshop (2 days)

– Web Services Foundation Course (1 day)

– Web Services and SOA Boot Camp (4 days)

– FUSE Architect Course (3 days)



FUSE Software - Point of Contact

• Jeff Hobbs, SWIM Implementation Lead– [email protected]– (202) 267-9772



Agenda

• Introduction • Overview of the SWIM Program• SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond• How to Learn More • Q&A



SWIM and Your JRC Package

• Acquisition Management System (AMS) and SWIM Service Lifecycle

• Suitability Analysis – Process

– Results• Scorecard

• Infrastructure Requirements• Development Follow-up



Role of the SWIM Program Office

• The SWIM program will work with you to determine the cost of SWIM-compliance

• SWIM will work with you to document required hardware, software, and standards in your SWIM Infrastructure Implementation Plan

• SWIM will participate in your ISD/IOC



Stages of SWIM Service Lifecycle Model

Stage 1: Service

Proposal

Stage 2: Service

Definition

Stage 3a: New Service Development

Stage 5: Service

Deprecation

Approved service

Candidate service

New service proposal

Operational service

Retired service

Service update /patch

Rej

ecte

d pr

opos

al

Stage 3b: Service

MaintenaceOperational

service

Stage 6: Service

Retirement

Deprecated Service

Development State

Stage 4: Service

Operations

Operational service



Service Lifecycle Stages

Stage 2

Stage 3a

Stage 4

Stage 3b

Stage 5

Stage 1



SWIM Suitability – Gateway to Stage 1

Information need identified

EnterpriseArchitecture

Board

Program/BU

SOA suitabilityanalysis initiated

Suitability Info Doc completed

Suitability Checklist

completed

EAB/TRB reviews

information

Suitable for SOA implementation?

AMS Process

SWIM Infrastructure Implementation Plan (SIIP) developed w/

SWIM PO

YES

NO

Suitability Scorecardcompleted



New Data Req'd Data Refresh

SWIM Suitability ChecklistInvestment Analysis Readiness Decision

Initial Investment Decision

Final Investment Decision

Description of New Service or Mod X X X1 SOA service availability verification X X X2 Intended Audience/User Community (FAA) X X X3 Intended Audience/User Community (Non FAA) X X X4 Type of user information X X X5 Frequency of Data Usage (FAA) X X X6 Frequency of Data Usage (Non FAA) X X X7 Role in NextGen strategic plan X X X8 Durability of proposed process X X X9 Granularity of service(s) X X X

10 Reusability of service(s) X X X11 Degree of use of SOA infrastructure X X12 Impact on FAA Users X X13 Impact on non-FAA Users (DOD, NASA, Airlines, etc) X X14 # Interfaces Required to Existing Systems X X X15 Technical Complexity of Pt-Pt X X16 Technical Complexity of SOA X X17 Ability to use SWIM common components X X18 IT Security (Pt-Pt vs. SOA) X X19 Greenfield vs Mod to Existing X X20 Technological Maturity of non-SOA solution X X X21 Technical risk of SOA approach X X22 Safety X X23 Human Factors/Impact to Workforce X X24 Operational Cost Efficiencies X X25 Maintainability X X26 Risk of SOA approach X X27 Executability X X28 Known dependencies for SOA solution X X

Scorecard and Linkage to AMS



Gate #1 to Stage 2 - Suitability Scorecard

INSERT PROGRAM NAME HERE

SWIM Suitability Checklist N/A LOW Yes-1 MEDIUM Yes-2 HIGH Yes-3

1 SOA service availability verificationNo comparable service exists

Partially compliant service exists that would require moderate development

Compliant service exists that would need minimal development

2 Intended Audience/User Community (FAA)Single primary user; limited audience (1-

10)Multiple primary users; moderate audience (11-

20)Multiple primary users; large audience (21-

40)

3 Intended Audience/User Community (Non FAA)Single secondary user; limited audience (1-

10)Multiple secondary users; moderate audience

(11-20)Multiple secondary users; large audience

(21-40)

4 Type of user informationMinimal value to user(s) primary

role/functionModerate value to user(s) primary role/function High value to user(s) primary role/function

5 Frequency of Data Usage (FAA)Infrequent use of data by primary users (1-

2 x per month)Periodic use of data by primary users (1-2 x per

week)Frequent use of data by primary users (1-2

x per day)

6 Frequency of Data Usage (Non FAA)Infrequent use of data by secondary users

(1-2 x per month)Periodic use of data by secondary users (1-2 x

per week)Frequent use of data by secondary users (1-

2 x per day)

7 Role in NextGen strategic planInformation has minimal role in NextGen

strategic planInformation has moderate role in NextGen

strategic planInformation has critical role in NextGen

strategic plan

8 Durability of proposed processService/info will only be required for a short

period of time (months)Service/info will only be required for a moderate

period of time (quarters)Service/info will only be required for a

significant period of time (years)

Only select one category (Low, Medium, High) per criteria; Input 1,2 or 3 into applicable cell28 total items

N/A LOW MEDIUM HIGH Total ScoreEvaluation Criteria 0 0 0 0 0

Low value in SOA-based solution 0 28Moderate value in SOA-based solution 29 56

High value in SOA-based solution 57 84

Range

Summary of scoring

Value range

Step #1

Step #2

Step #3



SWIM Infrastructure Implementation Plan• Provides a mechanism for

– Documenting Service Provider/program requirements for SWIM infrastructure

– A “contract” between your program and SWIM

• Addresses program infrastructure requirements– SWIM functional areas: messaging (patterns,

protocols), enterprise service management, security– SWIM non-functional areas: availability, latency,

reliability, etc.– SWIM locations: endpoints, types, etc.



SWIM and JRC Requirements - Points of Contact

• Jim Robb, Requirements and Governance Lead– [email protected]– (202) 267-8357

• Deborah Young, Program Control Lead– [email protected]– (202) 267-8003



Agenda

• Introduction• Overview of the SWIM Program• SWIM-Compliance • FUSE Software Overview • SWIM and Requirements for Your JRC Package • Segment 2 and Beyond• How to Learn More • Q&A



Segment 2 Overview

• Goals– Support anticipated data exchange needs of NextGen

Programs– Build on Segment 1 Governance, for all NAS programs that

score well on the SOA Suitability Checklist– Expand SWIM infrastructure to include additional Enterprise

Service Management, Security, other SOA infrastructure services, and Core services that were delegated to the SIPs in Segment 1

• Segment 2 JRC planned for summer FY10, to request baseline funding for FY12 – FY15



SOA Core Services

Enterprise Services Management

Interaction Services User Interaction Interface and

Portals

Browser Client On-DemandNAS Portal

AdminPortal

Notifications and Alerts

Weather Notification

Flow Constraint

Notification

Airport Status and Mission

Critical Notification

SLA Compliance and

Metrics Collection

PolicyEnforcement and Metric Collection

Technical Infrastructure Services

Boundary Protetion

Information System Security

Support Infrastructure

SOASupport

Platforms

Computing Platform

Terrestrial Network

Communication

Web Application

HostingCapability

DataStorage

Air/Ground Communications

Fault Monitoring And Reporting

Support Services

Administrative Services


SOA RuntimeManagement

ServicePolicy

Management

ServiceSLA

Management

SOA StrategicGovernance

StrategicSOA

Governance

Run-time and OperationsGovernance

Service Design

Governance

SOA Governance Service Desk

Support

SecurityPolicy

Management

Security ServicesSecurity Policy

Enforcement andAccess

Management

Service SecurityMonitoring

InstantMessaging

Data/Network Support Services

DatabaseAdmin

Services

NetworkSupportServices

Information SystemSecurity Support

Management

Incident Detection And Response

Services

Help Desk

ServicesProvisioningManagement

Services Diagnostics

ServicesIntegration and

Testing

Services Provisioning

Business Continuity

Management

TrainingSupport

WhiteBoard

Collaboration Services

Data Acquisition ServicesAeronautical

DataManagement

WeatherData

Management

Content Discovery

SurveillanceData

Management

Content Management ServicesWeather

Data Acquisition

Surveillance Data

Acquisition

Maintenance Data

Acquisition

Messaging Services

Publish/Subscribe

MessageRouting

Mediation

Interface Management

ServiceDiscovery

Service ScorecardGeneration and

Publication

Mission Services

Separation Management

TrajectoryManagement

Flight and State Data Management

FlowContingency Management

Surveillance Information Management

NavigationSupport

Short Term Capacity

Management

Long Term Capacity

ManagementWeather

Information Management

System and Services

Management

System and ServicesAnalysis

SafetyManagement

Aeronautical Information Management

ServiceChoreography

CertifiedSoftware

Management

Request/Response

WebAppication

ServiceRegistration

Performance Monitoring and

Reporting

SIP

SWIM

Other/Not in Segment

NASEAF SV4 NAS Enterprise Services (SWIM Segment 2)



SWIM Roles

• Leadership in Developing Enterprise Service Orientation in the NAS

• Understanding NextGen and NAS Objectives which Require SWIM Capabilities

• Identification and Evaluation of Information Management Technologies and Processes for the NAS Enterprise

• Governance via Industry Standards



Near Term

• SWIM Segment 2– Operation Services Environment Definition (OSED)– Requirements– Architecture

• SWIM Air• SWIM Interagency• SWIM International• Federated vs Consolidated



Mid Term

• SWIM Segment 3– Operation Services Environment Definition (OSED)– Requirements– Architecture

• SWIM Air• SWIM Interagency• SWIM International• SOA to Cloud Computing?



Segment 2 and Beyond - Points of Contact

• Mike Hritz, Evolution and Coordination Lead– [email protected]– (202) 385-7198



Agenda




The SWIM.gov website describes the SWIM program and provides news announcements for current issues

www.swim.gov

1

There are several ways to learn more about SWIM…



Key documentation, including the SWIM Newsletter and the SWIM Q&A, provides an overview of the SWIM program

www.swim.gov

2

There are several ways to learn more about SWIM…



SWIM Team Leads

Program Manager

Ahmad Usmani

[email protected]

(202) 267-3391

Implementation

Jeffery Hobbs

[email protected]

(202) 267-9772

Requirements and Governance

Jim Robb

[email protected]

(202) 267-8357

Evolution and Coordination

Mike Hritz

[email protected]

(202) 385-7198

Acquisition

Rhonda Thomas

[email protected]

(202) 493-467

Program Control

Deborah Young

[email protected]

(202) 267-8003



Agenda




Questions and Comments?

ms powerpoint

Technology

program concept swim

fti replacement swim

nextgen swim isnot

key aspects of swim

faa programs

demand systems

restructuring of services

multiple services