1. System Wide Information Management Segment 2
Authorization to Proceed
Joint Resources Council
SWIM Program Manager, Ahmad Usmani
November 17, 2010

2. Mission Need Assessment
Applications cost too much to develop, test, deploy and support
Fewer networked versus many point-to-point interfaces
Reduced flow time and complexity for building new applications and interfacing existing applications
Common shared services for information management
NAS needs to be more agile
Quicker application development
Sever tie between geographical facilities and operations
Easier and quicker system failure recovery
Facilitates special events planning and implementation
Facilitates automation and platform convergence
Data sharing is labor intensive
Shared electronic availability reduces the amount of data shared manually
Real-time access to common data is limited
Published data available to all authorized users
Underlying tools to support a performance-based organization are lacking
Published data can be mined for appropriate metrics

3. State of the System Business as Usual Today Enterprise Management
- More point-to-point
unique interfaces
- Costly development, test, maintenance, CM
- New decisions linked to old data constructs
- Cumbersome data access outside the NAS
Host
WARP
IDS/ ERIDS
ATOP
CIWS
TFM
TMA
STARS/
ARTS/
TAMR
ERAM
ASDE
ETMS
Inter- Agency
Enterprise Management
FAA Systems
AIM
ERAM
TFMS
CIWS
TDDS
- Existing point-to-point hardwired NAS
- Unique interfaces, custom designs
SWIM Compliant Government Systems
SWIM Compliant Non-Government Systems
FTI
CARTS/
STARS
ITWS
TBFM
LEGEND
WMSCR
DOTS
SWIM Segment 1
SWIM Future Segment
SWIM Adapter

4. Capabilities performed by one for another to achieve a desired outcome
SOA organizes technical capabilities in a standard way to allow flexible accomplishment of constantly changing demands
Service S
SOA establishes services as the mechanism by which needs and capabilities are brought together
Capabilities performed by one for another to achieve a desired outcome
Oriented O
SOA standardizes the necessary interfaces and behavior to support interaction
When capabilities are self-contained and independent to enable a collection of services to be linked together to solve a business problem
Jim to review this….
TALKING POINTS
SWIM provides:
SOA technology infrastructure
Information management standards and processes
Leads to consistent service development, operation and management enterprise-wide
Enables systems on the network seeking those services to invoke them without having to change or adapt to the underlying implementation of the service (i.e. loose coupling)
Architecture A
SOA provides an organizing and delivery paradigm that derives greater value by reusing existing software solutions rather than duplicating capabilities
The fundamental organization of a system embodied in its capabilities, their interactions, and the environment

5. (e.g., Airlines, DoD DHS, ANSPs)
Conceptual Overview
Terminal
Controllers
En Route
Controllers
System
Developers
Non-FAA Users
(e.g., Airlines, DoD DHS, ANSPs)
FAA
Command Center
NextGen Applications
SWIM Infrastructure for Messaging
FTI IP Backbone

6. Decision Requested
Approve FY11-12 planning funds; hold acquisition funds for FY12-13
Approve NAS and enterprise SOA governance roles and responsibilities
Authorization to proceed with the preferred alternative
SWIM provides enterprise SOA infrastructure so programs do not need to replicate or procure individually 6

7. Governance Roles and Responsibilities
NAS Governance
SWIM performs SOA suitability assessments in support of the EAB/TRB
Identify potential providers of NAS services
Programs assessed at investment decisions (IARD, IID, FID)
EAB/TRB approves authorized providers of SWIM-compliant NAS services
Enterprise SOA Governance
SWIM ensures governance compliance
SWIM will NOT attempt to govern SOA implementations that are internal to NAS programs 7

8. Service Lifecycle Management Decisions
EAB/TRB
Investment Decision Authority (JRC/EC)
SWIM Governance Team
SOA suitability assessment
Proposal decision taken by TRB, but primarily predicated on SWIM Suitability Analysis
In Service Decision (ISD) Authority 8

9. Implications of Governance Decision
“As-Is”
NAS programs perform ad hoc self-governance
Lack of interoperability
Not all deployed NAS Services are visible to the Enterprise
Policy compliance “after the fact” causes additional rework
“To-Be”
SWIM governance will ensure that programs use SWIM-provided infrastructure, and not replicate functionality in their own program
SOA suitability assessment on all investment decisions early in the lifecycle to provide appropriate compliance guidance
SWIM governance builds on existing AMS policies and FAA Standards
Identification of redundant services

10. Governance Implications
Programs will use the enterprise SOA infrastructure provided by SWIM
Programs will not develop their own redundant enterprise SOA infrastructure
Programs will meet SWIM-compliance requirements as required by EAB/TRB
Disputes related to implementation of enterprise SOA will be resolved by the EAB/TRB

11. Financial Implications
Enterprise SOA infrastructure costs will be included in the SWIM Segment 2 baseline
SWIM-compliance costs for NAS services will be included in each program’s JRC funding request
Programs will prepare SWIM Program Implementation Plan (SPIP) at FID
Joint effort between program and SWIM
Based on the program’s Final Program Requirements

12. Plan to Proceed Activity Offices of Responsibility
Estimated Completion Date
SWIM representatives assist in creation of the NAS Enterprise Architecture roadmap for 2012
SWIM
Dec 2011
Complete Screening Information Request (SIR)
Plan to release SIR
Technical and Pricing Evaluations
SWIM, CO
October 2011
February 2012
Define strategy to address synchronization issues with regard to SWIM SOA implementation and other programs’ timing of core services implementation.
IP&A review
June 2011
Define the processes used by the EAB/TRB to perform NAS Governance
AJP
September 2011
Update Core Services and SIP costs for the Alternative 3 and reference case based on contract proposals.
Provide detailed analysis of how the updated cost estimate changed from November 2010 JRC decision
June 2012
Develop risk management for implementation of NAS SOA services.
Provide periodic updates on system engineering and governance deliverables according to Exhibit A, Monitoring Plan.
On-going based on Exhibit A, Monitoring Plan
Resolution of IP&A comments to the updated cost estimate
IP&A
60 days prior to JRC
EC/JRC pre-briefings
August 2012
AJF pre-briefings
30 days prior to JRC EC
JRC
September 2012

13. SWIM Segment 2 Alternatives
Reference Case
Programs beyond Segment 1 are required to be SWIM-compliant
Self governance
No SWIM infrastructure
Alt. 1 – Expanded Segment 1 Approach
Continue current Segment 1 approach
Programs replicate enterprise SOA infrastructure in their systems
Alt. 2 – Messaging and Security Management
SWIM provides messaging and security management infrastructure
Programs replicate remaining enterprise SOA infrastructure in their systems
Alt. 3 – Enterprise SOA infrastructure (Preferred Alternative)
SWIM provides enterprise SOA infrastructure so programs do not need to replicate
Programs focus on providing services key to their mission
Based on worst case cost assumptions to compare alternative solutions

14. SWIM Alternatives for Segment 2
Ref. Case
Complete Segment 1 based on approved JRC
Alt. 1
Expanded Segment 1 Approach
Alt. 2
Messaging and Security Management
Alt. 3
Enterprise SOA Infrastructure
Ad hoc coordination among individual programs. No enterprise governance, only self-governance
SWIM compliant interfaces, messaging services, support services, interaction services, security mgmt, enterprise service mgmt (same as Seg. 1 but beyond 7 SIPs)
SWIM compliant interfaces, interaction services, orchestration, mediation and enterprise service mgmt
SWIM compliant interfaces
Enterprise SOA governance, registry/repository, interaction services, interface mgmt, messaging, security mgmt, enterprise services mgmt, orchestration, support services, mediation
SIP
Enterprise SOA governance, registry/repository, interface mgmt, messaging, security mgmt
SWIM
Enterprise SOA governance, registry/repository

15. NASEAF SV4 Enterprise Services (SWIM Segment 2)
Interaction Services
Administrative
Governance
User Interaction Interface and Portals
Notifications and Alerts
Services
Runtime Management
Airport Status and Mission Critical Notification
Web Application
On-Demand NAS Portal
Admin Portal
Weather
Flow
Data / Network
Browser
Client
Notification
Constraint
Support Services
Notification
Database Admin Services
Service Choreography
Mission Services
Network Support Services
Service Orchestration
Separation Management
Flight & State Data Management
Flow Contingency Management
Short Term Capacity Management
Long Term Capacity Management
Trajectory Management
Information System Security Support Management
Security Policy Management
Systems and
Systems and
Aeronautical Information Management
Weather Information Management
Surveillance Information Management
Services
Services
Navigation
Safety
Analysis
Management
Support
Management
Incident Detection and Response Services
Service Policy Management
Support Services
Business Continuity Management
Data Access
Data Flow Management
SWIM
Service SLA Management
Content Discovery
Data Acquisition
Service Adaptation
Data Composition
Data Flow Mechanisms
Help Desk
Other
Service Scorecard Generation and Publication
Services
SOA Core Services
Provisioning
Management
SWIM / SIP
Messaging Services
Enterprise Services Management
Services Diagnostics
Strategic Governance
Publish/ Subscribe
Request/ Response
Message Routing
Policy Enforcement and Metrics Collection
Performance Monitoring and Reporting
Mediation
Service Development Integration and Testing
SIP
Strategic SOA
Governance
SLA Compliance and Metrics Collection
Fault Monitoring and Reporting
4/16/2017
Service
Design
Governance
Interface Management
Security Services
Collaboration Services
Services Provisioning
Security Policy Enforcement and Access Management
Service Security Monitoring
Runtime and
Service
Service Registration
Instant
White
Operational
Discovery
Messaging
Board
Certified Software Management
Governance
Technical Infrastructure Services
SOA Governance
Service Desk
Web Application Hosting Capability
Support
Boundary Protection
INFOSEC Support Infrastructure
SOA Support Platforms
Data Storage
Computing Platform
Terrestrial Network Communication
Training
Air/Ground Communications
Sensor Systems
Support

16. NNEW Program Responsibility Allocation
Solution Development and In-Service Management
Filtering/ Extraction Capability
OGC Service Standards (Subscription Extensions)
ISO Registry Implementation
Weather Data Format Standards
Legacy Service Adaptors
Messaging Infrastructure
Software
Hardware 1
NNEW
SWIM 2 3
N/A
Integration and/or Capability Hosting
Each Program

17. SWIM Segment 2 Notional Architecture
ZSE
ZAU
ACY
ZLC/NEMC
FTI Operational IP Network
ZBW
ZLA
ZTL/NEMC
ZFW
ZDC
Place SWIM hardware at:
ARTCCs [6 sites]
Seattle (ZSE), Chicago (ZAU), Boston (ZBW), Leesburg (ZDC), Dallas Fort Worth (ZFW), Los Angeles (ZLA)
Atlanta and Salt Lake NNCCs (co-located with ZTL and ZLC) [2 sites]
Atlantic City (ACY) [1 site]
Total: 9 geographically dispersed sites across the NAS including 3 gateway sites (two NNCCs and ACY)
Fourth gateway location (Okla City) is not included but can represent an additional or fallback location if needed
Site hardware deployment basically falls into 2 categories:
ARTCC sites (6 of 9 sites)
Gateway sites (3 of 9 sites)
An integration and provisioning capability will be located at a gateway site (ACY)
Strategy is consistent with results of a heuristic middleware estimate using service data in SWIM Segment 2 SV-7 as input*
Two gateway sites are co-located with ARTCCs (Atlanta NNCC and ZTL, Salt Lake NNCC and ZLC)
Two gateway sites not co-located with ARTCCs have similar telecommunications connectivity as the ARTCC sites (ACY and Okla City)
Gateway sites may have extra physical space available for SWIM hardware
Integration
and Provisioning
Distributed
SWIM Core
Centralized
SWIM Core
Comm.
Equipment
Gateway
Equipment
Legend

18. 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 Five-Year Strategy Goals
4.1.3 Achieve adaptability and affordability through a common automation platform

19. Program Management Planning phase (FY11/12) will focus on: Prototyping
Meet the immediate needs of dependent programs
Further refinement of Segment 2 system requirements and architecture
Implement enterprise SOA governance
Investment analysis for FID in 2012
Pre-contract award activities leading to contract award in 2012
Release RFO/SIR for Segment 2 integration contract in 2011
Contract award will follow a 2012 FID
Provides capabilities required by NAS programs that were not included in Segment 1, but are required prior to Segment 2
Approach:
SWIM is responding to schedule drivers from NAS programs
SWIM is providing application layer capabilities (as opposed to network layer capabilities like FTI)
SWIM will use COTS products to reduce cost and schedule and minimize risk

20. SWIM Bridge to Segment 2 Prototypes for meeting immediate needs
Domain Name Service (DNS)
Identity and Key Management (IKM)
Network Time Protocol (NTP)
Prototypes for further refinement of Segment 2
Cross Boundary Authentication
NAS Authorization Management
Enterprise Service Management (ESM)
1. SWIM is responding to schedule drivers from NAS programs
2. SWIM is providing application layer capabilities (as opposed to network layer capabilities like FTI)
3. SWIM is doing this jointly with other AJW organizations
4. SWIM will use technical architecture and COTS products to minimize risk and change impacts
Capability
DNS (FTI Partner)
Domain Name Server
Identity and Key Management-IKM (NEISS/NISSE Partner)
Public key infrastructure
Enterprise Service Management-ESM (NEMC Partner)
Network Time Protocol-NTP (FTI Partner)
Reliable and secure way to distribute time across the network
Cross Boundary Authentication
Explore the interactions and required extension of Web Service Security (WSS) standards
Examines the sufficiency and compatibility of DOD/DHS standards and architectures
Increase our understanding of the NAS complexities of implementing “Authorization Services” part of WSS
NAS Authorization Management
Examine Common Security/Interface Issues
Prototype Universal Interface (DoD OneStop Model)
Examine Messaging Application Potential 20

21. Future Plans SWIM plans to have an FID in 2012 for SWIM Segment 2
Refined Segment 2 costs based on contractor estimates
Fully defined SWIM Segment 2 requirements and architecture per preferred alternative (Alternative 3)
Establish a risk management process related to implementation of NAS SOA services 21

22. Decision Requested
Approve FY11-12 planning funds; hold acquisition funds for FY12-13
Approve NAS and enterprise SOA governance roles and responsibilities
Authorization to proceed with the preferred alternative
SWIM provides enterprise SOA infrastructure so programs do not need to replicate 22