System Wide Information Management (SWIM)

1
System Wide Information Management (SWIM)

• 3rd Annual SWIMposium An Informational Panel on
  the SWIM Program

2
Agenda

• Introduction
• SWIM Program Overview
• Service Oriented Architecture (SOA) Governance
  and the National Airspace System (NAS) Service
  Registry/Repository (NSRR)
• NAS Enterprise Messaging Service (NEMS)
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

2
3
Agenda

• Introduction
• SWIM Program Overview
• SOA Governance and the NSRR
• NEMS
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

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

• SWIM will
• Implement a SOA in the 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
  the Next Generation Air Transportation System
  (NextGen)
• SWIM will not
• Be a set of avionics equipment
• Substitute for NAS modernization programs
• Replace FAA Telecommunications Infrastructure
  (FTI)

4
5
SWIM Concept

• Migrate the NAS to SOA
• Makes it easier to establish interfaces between
  systems
• Get the right information to the right place at
  the right time Net-Centricity!
• Facilitate Shared Situational Awareness
• Facilitate Collaborative Decision Making
• Establish governance over service implementations
• Represents significant cultural change

5
6
SOA organizes technical capabilities in a
standard way to allow flexible accomplishment of
constantly changing demands
Service
S
Capabilities performed by one for another to
achieve a desired outcome
Oriented
O
When capabilities are self-contained and
independent to enable a collection of services to
be linked together to solve a business problem
Architecture
A
The fundamental organization of a system embodied
in its capabilities, their interactions, and the
environment
6
7
SWIM is a SOA Implementation

• SWIM provides
• SOA technology infrastructure
• Governance to ensure that information management
  standards and processes are followed
• Leads to consistent service development,
  operation, and management across the enterprise
• By following SOA standards and principles
• SWIM makes services available on a network
• 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)

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

• SWIM Segment 1
• Implementation of a set of federated services in
  the NAS with SWIM-provided governance, standards,
  and software to support development of reusable
  SOA services
• SWIM provides requirements, schedule, and funding
  to seven other NAS programs tracks progress via
  formal monthly reviews
• Segment 1 results in SOA services deployed to all
  Air Route Traffic Control Centers (ARTCCs), 37
  Terminal Radar Approach Controls (TRACONs), the
  Air Traffic Control System Command Center, the
  William J. Hughes Technical Center (WJHTC), and
  NAS Enterprise Management Centers (NEMCs)
• SWIM Segment 2
• Continues provision of governance, standards, and
  software to additional NAS programs
• Implements enterprise messaging service for new
  SWIM Implementing Programs (SIPs) and
  facilitates transition by Segment 1 SIPs

10
11
Segment 1 Capabilities
Capabilities will be implemented as multiple
services by SIPs through FY15
11
12
SWIM Schedule
FY 09 FY 09 FY 09 FY 09 FY 10 FY 10 FY 10 FY 10 FY 11 FY 12 FY 13 FY 14 FY 15 FY 15 FY 15 FY 16 FY 16 FY 16 FY 16 FY 17 FY 17 FY 17 FY 17

SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1 SWIM Segment 1

SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2 SWIM Segment 2
12
13
SWIM Milestones
DATES CAPABILITIES
October 2010 Corridor Integrated Weather System (CIWS) Publication operational CIWS SIP
December 2010 Special Use Airspace (SUA) Automated Data Exchange operational Aeronautical Information Management (AIM) SIP
January 2011 Integrated Terminal Weather System (ITWS) Publication operational ITWS SIP
June 2011 Reroute Data Exchange operational Traffic Flow Management (TFM) SIP
June 2012 PIREP Data Publication operational Weather Message Switching Center Replacement (WMSCR) SIP
October 2012 Flight Data Publication Initial Flight Data Services operational En Route Automation Modernization (ERAM) SIP
?
?
?
?
13
14
SWIM Milestones (cont.)
DATES CAPABILITIES
February 2013 SUA Automated Data Exchange operational ERAM SIP
August 2013 Flow Information Publication operational TFM SIP
August 2013 Terminal Data Distribution operational SWIM Terminal Data Distribution System (STDDS) SIP
March 2014 Flight Data Publication Host Automation Data Distribution System/Flight Data Input Output (HADDS/FDIO) operational ERAM SIP
June 2014 Runway Visual Range (RVR) Publication Service operational TFM SIP
March 2015 Flight Data Publication Enterprise Services operational ERAM SIP
March 2015 PIREP Data Publication operational ERAM SIP
September 2015 SWIM Tool Kits SWIM Core Services
14
15
FY11 Accomplishments

• Released the SWIM Segment 2 Technical Overview
  and draft Final Program Requirements
• CIWS and ITWS SWIM services became operational
• AIM demonstrated SUA Automated Data Exchange
  Initial Operating Capability (IOC)
• Deployed Terminal Data Distribution System (TDDS)
  prototype
• Performed governance oversight of SIPs and other
  FAA programs to ensure interoperability between
  systems
• Continued SOA suitability assessments of other
  FAA programs that are going through the Joint
  Resources Council (JRC) process
• Continued operating Commercial-Off-The-Shelf
  (COTS) software repository, wiki, and web site

15
16
FY12 Planned Activities

• Implement enterprise SOA governance
• Execute Segment 2 activities
• Deploy WMSCR PIREP Data Publication
• Develop Domain Name Service (DNS) prototype
• Design Review for Network Time Protocol (NTP)
• Design Review for Identity and Key Management
  (IKM)
• Conduct Segment 2 JRC Final Investment Decision
  (FID)

16
17
Questions and Comments?
17
18
Agenda

• Introduction
• SWIM Program Overview
• SOA Governance and the NSRR
• NEMS
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

18
19
What is Governance?

• The set of processes that specifies the decision
  making and accountability that encourage
  desirable behaviors in the organization (Gartner,
  2007)
• Ensuring and validating that assets and artifacts
  within the architecture are acting as expected
  and maintaining a certain level of quality
  (Gartner, 2007)
• It needs to be just enough to ensure success,
• but not so much as to become inflexible and
  monolithic

19
20
How does one Govern?

• Establishing chains of responsibility, authority,
  and communication to empower people (decision
  rights)1
• Establishing measurement, policy and control
  mechanisms to enable people to carry out their
  roles and responsibilities1
• An Enterprise Perspective

1 Rational Unified Process, version 7.0.1 SOA
Governance and Management Overview
20
21
Enterprise Governance Perspective
The Good
FAA Systems
SWIM Compliant Government Systems
SWIM Core Capabilities
the Bad
and the Ugly
Zeal for SOA and Web Services without Governance
leads to incompatible implementations and rogue
services.
21
22
Scope of SWIM Governance
Its a part of FAA Governance
FAA Governance
What is FAA/ATO/NAS governance?
ATO Governance
NAS Governance
Establishing decision making rights associated
with the FAA/ATO/NAS Establishing mechanisms and
policies used to measure and control the way
FAA/ATO/NAS decisions are made and carried out
SWIMGovernance
What is SWIM governance?
Extension of NAS governance focused on the
lifecycle of services to ensure the business
value of SWIM
SWIM Governance is a catalyst for improving
overall NAS, Air Traffic Organization (ATO) and
FAA governance
22
23
SWIM Governance

• WHO is responsible
• Governance Authority
• Initial Service Candidate Approval by Technical
  Review Board (TRB)
• SWIM manages remainder of lifecycle for approved
  programs
• Service Providers responsibilities documented
• Service Consumers responsibilities documented
• WHAT must they do
• SWIM Governance Policies v1.1
• SWIM Service Lifecycle Management Processes v1.0
• HOW must they do it
• Technical Standards coordinated with NAS
  Enterprise Architecture
• TV-1 Technical Standards Profile
• TV-2 Technical Standards Forecast
• FAA Standards
• FAA-STD-063 XML Namespaces
• FAA-STD-064 Web Service Registration
• FAA-STD-065 Web Service Description Documents
• FAA-STD-066 Web Service Taxonomies
• SWIM Version Management Processes v1.0

23
24
Simplified Enterprise Architecture System View
24
25
SWIM Governance Policies Outline

• STRATEGIC SOA POLICIES
• SOA Technology Acquisition
• Enterprise Architecture
• Opportunity Management for SOA Services
• Interoperability, Reuse and Standards
• NSRR
• SERVICE DESIGN-TIME 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 POLICIES
• Messaging and Routing
• Runtime Security

Note Adapted from the Simplified Enterprise
Architecture System View
25
26
SWIM Interoperability Standards

• Use of SWIM Service Container Software (Segment
  1)
• JMS Provider Standardization (FUSE Message Broker
  / 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-Java Message Service (JMS)
• XML-over-JMS
• SOAP Messaging WS-I Conformance
• SWIM Interoperability Basic Profile
• Binary Attachments in SOAP Messages
• SOAP with Attachments
• Message Transmission Optimization Mechanism (MTOM)

26
27
SWIM Interoperability Standards (cont.)

• JMS Message Type
• TextMessage for XML or text
• ByteMessage for binary data
• ObjectMessage NO, implies undesirable language
  coupling
• Registry / Repository
• Discoverability - Web Services Description
  Language (WSDL)
• Categorization - FAA-STD-066 and SWIM Taxonomies
• Service Interface Design
• Design Policies
• Service Interface Description Web Service
  Description Document (WSDD)
• Information Security
• SWIM Basic Security Profile
• Service Management
• Java Management eXtensions (JMX)

27
28
SWIM Compliance

• SWIM Compliance Definition
• Verified conformance to SWIM Policies. (SWIM
  Service Lifecycle Management Processes v1.0)
• Verification Mechanisms
• Manual review of artifacts
• Governance-enabling Technology
• NSRR
• Testing Tools (Actional, Lisa, etc)
• SWIM Web Service Security Compliance Test Kit
  (SWIM WS-S CTK)
• Policy Servers
• XML Gateways
• Enterprise Service Management (ESM) software

28
29
Service Lifecycle Management Decisions

• TRB
• Investment Decision Authority
• SWIM Governance Team

In Service Decision (ISD) Authority
29
30
SOA Suitability Criteria

• NAS Enterprise View
• Potential for existing SWIM service to be
  utilized or tailored to meet the requirement
• Potential for other users to benefit from the
  information exchange
• Potential hazards for exposing data through SWIM
  (e.g., proprietary data, non-FAA user access)
• Program View (Cost, Schedule, Technical)
• Life-Cycle Cost of SWIM versus other solutions
• System performance requirements latency,
  transmission rate, bandwidth, response time,
  overhead, etc.
• Safety/certification requirements
• Information security requirements
• Existing architecture/vendor solution impacts

30
31
Service Discoverability

• Discoverability is a key Principle of Service
  Design1 in a SOA
• Common metadata framework to express purpose and
  capabilities of the Service
• Allow human browsing
• Allow machine-to-machine queries
• 1 Principles of Service Design, Erl et.al.
  Prentice Hall, 2008

31
32
Registry Repository
Service Registry
Discover and Retrieve Contract
Publish and Register Contract
Service Consumer
Service Provider
Exchange Messages
"In fact, it was the existence of a discovery
mechanism that primarily distinguished SOA from
previous distributed architecture
models." Principles of Service Design
32
33
Service Registry/Repository

• A Service Registry is a resource that provides
  controlled access to data necessary for the
  implementation and governance of SOA projects
• A Repository is a database containing the
  artifacts and metadata that constitutes a SOA
  registry
• Facilitates content validation and workflow
  support
• Stores Policies, Processes, and Schemas to
  support Governance Activities
• Note These are usually referenced as one
  product, often called a Registry/Repository

33
34
Why a Registry/Repository?

• Centralized discovery
• Lifecycle governance
• Centralized deployment
• Policy and standards enforcement
• Automated service notification mechanism
• Central to any SOA infrastructure in the
  promotion of reuse

34
35
Taxonomies

• A hierarchical organization of categories or
  values used for classification (FAA-STD-066)
• FAA-STD-066 defines required taxonomies for FAA
• SWIM has defined additional taxonomies required
  for NAS Services
• Use and support of taxonomy enforcement is
  critical to the success of any registry
  implementation
• Potential Taxonomy Candidates

Organization Unit Business Name
Lifecycle Stage Services for Citizens
35
36
Artifacts

• An Artifact is a repository item attached to a
  service that describes the service or may be used
  to access the service
• Some examples include
• WSDL (Web Service Description Language)
• WSDD (Web Service Description Document, defined
  in FAA-STD-065)
• ConOps (Concept of Operations, for interfaces,
  messaging, etc.)
• IRD (Interface Requirements Document)

Registry Standards

• Universal Description, Discovery, and Integration
  (UDDI)
• Supports the enforcement of enterprise policies
• Policy enforcement will enhance registry data
  quality
• Electronic Business XML (ebXML)
• Created to primarily support secured business
  transactions

36
37
NSRR Video

click for video
37
38
Questions and Comments?
38
39
For more information ...

• For more information on SWIM Governance and the
  NSRR, please contact
• Paul Jackson
• SWIM Governance Lead
• email paul.jackson_at_faa.gov
• phone [phone]

39
40
Agenda

• Introduction
• SWIM Program Overview
• SOA Governance and the NSRR
• NEMS
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

40
41
NEMS Agenda

• NEMS
• SWIM Evolution
• SWIM in NAS Architecture
• NEMS Integration Into NAS Architecture
• Major Segment 2 Activities
• Transition Planning Provisioning
• On-Ramping
• Q A

41
42
Enterprise SOA Services Allocation (NAS SV-4
2012-2016)
Enterprise Governance
Interaction Services
Runtime Management
Administrative Services
Service Choreography
User Interaction Interface and Portals
Notifications and Alerts
Data/Network Support Services
Browser
Client
Flow Constrain Notification
Airport Status and Mission Critical Notification
Weather Notification
Service Orchestration
Database Admin Services
Web Application
On-Demand NAS Portal
Admin Portal
Security Policy Management
Network Support Services
Mission Services
Separation Management
Trajectory Management
Flight and State Data Management
Flow Contingency Management
Short Term Capacity Management
Long Term Capacity Management
Information System Security Support Management
Service Policy Management
Weather Information Management
Surveillance Information Management
Navigation Support
Safety Management
Incident Detection and Response Services
System and Services Analysis
System and Services Management
Aeronautical Information Management
Service SLA Management
Service Scorecard Generation and Publication
Support Services
Business Continuity Management
Data Access
Data Flow Management
Data Acquisition
Service Adaptation
Content Discovery
Data Flow Mechanisms
Data Composition
Help Desk
Strategic Governance
Interaction Services
Strategic SOA Governance
Services Provisioning Management
SOA Core Services
Enterprise Service Management
Messaging Services provided by NEMS
Service Design Governance
Services Diagnostics
Policy Enforcement and Metric Collection
Performance Monitoring and Reporting
Request/ Response
Publish/ Subscribe
Services Development, Integration and Test
Run-time and Operations Governance
Mediation
Message Routing
SLA Compliance and Metrics Collection
Fault Monitoring and Reporting
SOA Governance Service Desk Support
Security Services
Collaboration Services
Interface Management
Services Provisioning
Security Policy Enforcement and Access Management
Service Security Monitoring
White Board
Instant Messaging
Service Registration
Service Discovery
Interaction Services
Certified Software Management
SWIM
FTI
Technical Infrastructure Services
SIPs
Training Support
Sensor Systems
Boundary Protection
Information System Security Support Infrastructure
SOA Support Platforms
Web Application Hosting Capability
Terrestrial Network Communication
Air/Ground Communication
Data Storage
Computing Platform
Future/Other
NEMC
TBD
43
Layered, Two-Tier ArchitectureEnterprise Domain
and Service Domain

• Layered architecture used for re-usability of
  information/content assets
• Service Domain Tier application programs able to
  provide/consumer available data
• Enterprise Tier hosts enterprise services
  accessible by all authorized users
• Interface Management layer abstracts enterprise
  domain to service domains
• Alleviates requirements on application programs
  to expose services to enterprise
• Enables a simple, standardized mechanism for
  applications programs to discover, acquire, and
  ingest enterprise services, rapidly improving
  information re-usability across the NAS

Sponsor Programs
External Customers
NAS Users
NEMS
Interface Toolkit
NAS Enterprise Security Gateway
System/ Security Admin
UESB
Governance
SOA Governance
Service Administration
Hosted on Shared Infrastructure
WAN Services Network Security
Monitor Control
Runtime Discovery
Enterprise Tier ESB
Service Level Security
Security Operations
Infrastructure Service Developers
Service Management
Service Provision
Policy Repository
Standards-Based ESB Interface (SOA-enabled)
Message-Oriented Middleware (Legacy Systems)
Standards-Based ESB Interface (SOA-enabled)
Service Legend NEMS FTI Flight Plan
Domain Weather Domain Airport Domain
Data Repository
Service Registry
43
44
NEMS Enterprise Architecture
Leveraging Enterprise Domain ESB
Enterprise Domain Tier
NEMS
Separates the IT and integration infrastructure
concerns from domain specific ATM concerns
Decoupled using JMS and WS
Legend
NEMS Service
FTI Service
Service Container Enabled Apps
Legacy NAS System Apps
Enables NAS use of multiple vendor technologies
avoiding lock-in
NAS programs and lines of business are executed
by domain experts
Policy Implementation Points
44
45
Segment 2 Enterprise Messaging Activities

• Infrastructure Build Out
• Provisioning - On-Ramping Producers/Consumers
• Capabilities Enhancements

45
46
NEMS On-ramping Steps
Data Architecture
Decision to On-ramp content (Policy)
Consumer On-ramps
Producer On-Ramps
Configure Infrastructure
Service Provisioning On-Ramping Providers and
Consumers to NEMS
46
47
NEMS User Deployment Status
Producer Consumer(s) Product Network Segment Status Cutover Date
TFMS Airlines/External Users ASDE-X (Track reports) NESG Operational 2011
WARP CIWS (MIT/LL) NEXRAD products NESG Deploying Sep-2011
WARP OASIS HWDS NAS Ops Planning Feb-2012
ITWS ITWS products NESG Planning TBD
WMSCR WMSCR msgs Planning TBD
EWINS Planning 2013
TFMS ASDI Planning TBD
AIM AIXM NOTAMs Planning TBD
FDPS Planning TBD
47
48
Questions and Comments?
48
49
For more information ...

• For more information on how your program will
  interface with NEMS, please contact
• Jim Robb
• SWIM Requirements Lead
• email jim.robb_at_faa.gov
• phone [phone]
• or
• Maureen Cedro
• FTI Engineering Manager
• email maureen.cedro_at_faa.gov
• phone [phone]

49
50
Agenda

• Introduction
• SWIM Program Overview
• SOA Governance and the NSRR
• NEMS
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

50
51
SWIM Segment 1

• Federated Approach
• Implementation of a set of federated services in
  the NAS with SWIM-provided governance, standards,
  and software to support development of reusable
  SOA services
• SWIM provides
• Overall Program Cost and Schedule
• SWIM System Engineering and Requirements
  Management
• Definition and Maintenance of Program Level
  Agreements (PLAs) with implementing programs
• Governance of Segment 1 participants
• SIPs 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

51
52
SWIM Segment 1 Capabilities
Capabilities will be implemented as multiple
services over the next five years
52
53
AIM COI
Service that enables SUA data updates dynamically
from ERAM via an improved Air Traffic Control
Graphical User Interface Service for consumers
to subscribe and receive SUA information
dynamically in the Aeronautical Information
Exchange Model (AIXM) standard Services to
dynamically publish AIXM SUA definitions for use
by the public and within NAS operational systems
(i.e., SUA Airspace Management System (SAMS))
SUA Automated Data Exchange
AIM (P)
ERAM (C)
53
54
Weather COI

• Services to publish both image and binary encoded
  CIWS data products to serve the varied needs of
  the consumers. Products available are
• VIL Mosaic (1KM resolution)
• VIL 2-hr. Forecast
• Echo Tops Mosaic (1 km resolution)
• Echo Tops 2-hr. Forecast
• Satellite Mosaic
• Storm Info Echo Top Tags
• Storm Info Leading Edges
• Storm Info Motion Vectors
• VIL Forecast Contours (Standard Mode)
• VIL Forecast Contours (Winter Mode)
• Echo Tops Forecast Contours
• Growth Decay Contours
• Forecast Accuracy Echo Tops
• Forecast Accuracy Standard Precipitation
• Forecast Accuracy Winter Precipitation

54
55
Weather COI(cont.)

• Services to provide ITWS products digitally to
  the Airline Operation Centers (AOCs) and other
  subscribers. Products available are
• Airport Lightning Warning
• Configured Alerts
• Forecast Accuracy
• Forecast Contour
• Forecast Image
• Gust Front TRACON Map
• Microburst TRACON Map
• Precipitation 5nm
• Precipitation Long Range
• Precipitation TRACON
• SM SEP 5nm
• SM SEP Long Range
• SM SEP TRACON
• Terminal Weather Text Normal
• Tornado Alert
• Tornado Detections
• Wind Profile

55
56
Weather COI (cont.)
Service to allow En Route controllers that
receive voice Pilot Reports, to efficiently enter
them into ERAM, which will transmit the reports
to WMSCR Service to provide stored
PIREPs Service to provide altimeter settings
56
57
Flight Flow Management (FFM) COI
Flight Data Publication
Service to provide flight data available to NAS
users and external users
TFM (C)
ERAM (P)
57
58
FFM COI (cont.)
Service to provide the means for Traffic Managers
to efficiently convey reroutes to Air Traffic
Controllers for pre-departure flights taking into
account NAS Customer preferences.
Reroute Data Exchange
TFM (C)
ERAM (P)
58
59
FFM COI (cont.)
Service to provide runway visibility data
available to NAS users and external users
RVR Publication
TDDS (P)
TFM (C) External (C)
59
60
FFM COI (cont.)

• Services will be provided to NAS users and
  external users
• ASDE-X streaming data service
• Surface Movement Events (SME)
• Tower Departure Events (TDE)

60
61
FFM COI (cont.)

• Services that provide a means for ERAM to
  subscribe to flow information describing several
  types of traffic flow initiatives. These will
  include the following
• Flow Constrained Area (FCA)
• Airspace Flow Program (AFP)
• Ground Delay Program (GDP)
• Ground Stops (GSs)
• Reroutes
• Advisories

61
62
Segment 1 Status Summary

• SWIM Segment 1 commits to delivery of 9
  capabilities, 8 of which are on track
• Two capabilities complete and operational
• ITWS Data Publication
• CIWS Data Publication
• Three capabilities complete and waiting for
  installation
• WMSCR PIREP Data Publication
• AIM SUA Automated Data Exchange
• Pre-Departure Reroute
• Two capabilities are on schedule and within
  budget allocations
• TDDS
• TFM Flow Data Publication
• One capability being replanned
• Flight Data Publication Service

62
63
Questions and Comments?
63
64
For more information ...

• For more information on SWIM Implementation,
  contact
• Jeff Hobbs
• SWIM Implementation Lead
• email jeffery.hobbs_at_faa.gov
• phone [phone]
• or
• Linda Chen
• SWIM Implementation
• email linda.chen_at_faa.gov
• phone [phone]

64
65
Agenda

• Introduction
• SWIM Program Overview
• SOA Governance and the NSRR
• NEMS
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

65
66
Cloud Computing Overview

• Cloud computing is a model for enabling
  convenient, on-demand network access to a shared
  pool of configurable computing resources that
  can be rapidly provisioned and released with
  minimal management effort or service provider
  interaction. (National Institute of Standards
  and Technology (NIST))
• Federal Cloud Computing Strategy (February 8,
  2011, Vivek Kundra, U.S. Chief Information
  Officer)
• Decision Framework for Cloud Migration
• NIST facilitates and leads the development of
  standards for security, interoperability, and
  portability
• Each Agency CIO is required to identify three
  must move services and create a project plan
  for migrating each of them to cloud solutions and
  retiring the associated legacy systems.
• Of the three, at least one of the services must
  fully migrate to a cloud solution within 12
  months and the remaining two within 18 months.

66
67
FAAs Cloud Progress

• FAA NAS and Non-NAS organizations have and will
  continue to work collaboratively on cloud
  adoption under the leadership of the Chief
  Information Officer (CIO)
• SWIM Program is responsible for implementing
  cloud in the NAS
• The FAA IT Infrastructure Board is responsible
  for oversight and guidance for FAAs non-NAS IT
  infrastructure, including cloud as well as data
  center consolidation efforts
• FAA is currently in the early stages of evolution
  to cloud
• Held formal and informal learning sessions, which
  included industry cloud leaders and experts
• Identified several cloud opportunities and
  currently using pilots as a means to better
  understand cloud issues
• The FAA is currently establishing a private cloud
  that will be used by the FAA and other federal
  agencies

67
67
68
Cloud Suitability Assessment

• Developing a Cloud Suitability Assessment that
  will be used to identify which data is suitable
  to move to the cloud

68
68
69
Questions and Comments?
69
70
Agenda

• Introduction
• SWIM Program Overview
• SOA Governance and the NSRR
• NEMS
• Segment 1 Update
• Cloud Computing
• Long-Term Plans

70
71
Agenda

• Long-Term Plans
• Net-Centric Prototypes and Demonstrations
• Other External Coordination
• Aircraft Access to SWIM (AAtS)

71
72
Net-Centric Prototypes/Demos Activity

• SWIM hosts Net-Centric Prototypes/Demos Technical
  Interchange Meetings (TIMs)
• Initial TIM held April 2008
• Recent TIMs held November 3, 2010 and May 4, 2011
• Facilitate Net-Centric Demo coordination/interacti
  on
• Demos may interact with SWIM in the future
• Coordination for SWIM Compliance
• Next TIM scheduled for November 2, 2011
• SWIM-Maintained List of Net-Centric
  Prototypes/Demos
• Listing of existing and planned prototypes and
  demos of possible interest to SWIM
• Contains name, owner, location, key features,
  points-of-contact (POCs), and SWIM relationship
• Shared with Joint Planning and Development Office
  (JPDO) for use in information sharing environment

72
73
Other External Coordination

• JPDO Net-Centric Operations Working Group
• JPDO Net-Enabled Test Environment
• Net-Centric Operations Industry Consortium
• NextGen Implementation and Integration (II)
  Segment Alpha and Bravo Working Groups
• FAA/Single European Sky Air Traffic Management
  (ATM) Research Joint Undertaking (SESAR JU) SWIM
  Interoperability Coordination

73
74
AAtS Overview

• What is AAtS?
• Provides aircraft with a connection to NAS
  services enabled by SWIM
• Why do we want AAtS?
• Improves aircraft situational awareness
• Aircraft will have the same information the FAA
  uses to make ATM decisions
• A collaborative decision making (CDM) enabler
• AAtS finally allows all three parties (ATM, AOC,
  and the aircraft) to operate from a common
  picture
• Other systems get information to the cockpit.
  AAtS delivers common information

74
75
AAtS Overview (cont.)

• Concept
• AAtS will initially use existing NAS and aircraft
  infrastructure (e.g., FTI, SWIM, Electronic
  Flight Bags (EFBs))
• Information delivered via AAtS is not intended
  for uses that directly affect the trajectory of
  the aircraft
• Note
• FAA has no plans at this time to acquire a system
  or infrastructure to specifically support AAtS
• AAtS will not replace existing or planned FAA
  systems

75
76
AAtS Overview (cont.)

• Data services via AAtS
• Only services available through NEMS will be
  available by AAtS
• AAtSWIM without SWIM there is no AAtS
• Scalability capability is key
• New data elements can be added more quickly, more
  easily, and less expensively
• New NAS data will be made available to aircraft
  by granting operators access to the additional
  data elements provided by SWIM

76
77
AAtS Notional Concept
77
78
Key AAtS components

• FAA Data Providers
• Aeronautical Information
• Flight and Flow Information
• Weather Information
• Etc.
• FAA Enterprise Infrastructure (SWIM, FTI)
• Data Management Service (DMS) Providers (Non-FAA)
• Access, process disseminate data products from
  FAA and end users
• Create applications as needed
• Data Transport Providers
• Provide terrestrial and/or satellite data links
  to and from the aircraft and ground
  infrastructure
• End Users
• Airlines, Business Aviation, General Aviation,
  and Military Aviation

78
79
Notional
80
AAtS Activities

• Demos to begin late 2011
• To continue to 2014
• Scope is to perform simulations, demonstrations,
  and trials
• Both domestic and oceanic/remote area global
  interoperability trials planned
• Architecture and technical profile definition
  underway
• Functional architecture is being developed in
  phases
• Demo to support AAtS simulations and
  infrastructure development out in draft
• Mid-term to support AAtS capability IOC in
  early 2014 March 2012
• Far-term to support long term evolution
  September 2012
• Technical requirements development targeted for
  late 2012
• Derived from architecture as technical profile
  (TV-5)

80
81
AAtS FAA Efforts

• New ATM Requirements NextGen System Development
• Concept of Use development. Associated definition
  and identification of the ways that AAtS affects
  the operations of the NAS includes
  Human-In-The-Loop (HITL) simulations and
  demonstrations
• Technical Concept development. Associated
  definition of the AAtS architecture, technical
  profile, and identification of AAtS impact on the
  NAS infrastructure includes technical
  simulations and tests
• AAtS Demonstrations
• AAtS Operational Trials includes the
  demonstration of use and technical concepts
  developed above

81
82
AAtS Simulations, Tests, And Operational Trials

• 2011
• AAtS ConUse concepts validation
• AAtS technical concepts validation, requirements,
  and metrics development
• Services used in demo to be determined by the
  availability of services that are structured
  similar to services found on SWIM (real or
  emulated)
• 2012
• AAtS domestic operational trials
• Services used in trials to be determined by
  availability of services on SWIM (operational or
  scheduled-to-be-operational by 2014)
• Safety analyses
• Robustness evaluations and additional other
  technical evaluations
• 2013
• AAtS global interoperability oceanic/remote area
  operational trials
• Services used in trials to be determined by the
  same method as 2012 domestic operational trials
  with the potential addition of other ANSP SWIM
  products
• Security analyses
• Robustness evaluations and additional other
  technical evaluations

82
83
Questions and Comments?
83
84
For more information ...

• For more information on SWIMs Long-Term Plans,
  contact
• Mike Hritz
• SWIM Evolution Coordination Lead
• email mike.hritz_at_faa.gov
• phone [phone]

84
85
There are several ways to learn more about SWIM
The SWIM.gov website describes the SWIM program
and provides news announcements for current
issues It also contains key documentation,
including select briefings, the SWIM Newsletter
and the SWIM QA
www.swim.gov
85
86
SWIM Points of Contact

• Program Manager
• Ahmad Usmani
• ahmad.usmani_at_faa.gov
• [phone]
• Implementation
• Jeffery Hobbs
• jeffery.hobbs_at_faa.gov
• [phone]
• Linda Chen
• linda.chen_at_faa.gov
• [phone]
• Requirements
• Jim Robb
• jim.robb_at_faa.gov
• [phone]

Evolution Coordination Mike Hritz
mike.hritz_at_faa.gov [phone] Acquisition
Robert Klein robert.klein_at_faa.gov (202)
493-4651 Program Control Ellen
Muldoon ellen.muldoon_at_faa.gov [phone]
86