The Flight Object in SWIM

1
Air Traffic Organization

• The Flight Object in SWIM

2
Operational Evolution Partnership
(OEP)Integration Implementation
3
SWIMProgram Concept

• SWIM will
• Implement a Service-Oriented Architecture (SOA)
  in the NAS
• Identify industry standards, best practices, and
  COTS products for use by other NAS programs
• Provide SOA governance policies and processes
• In order to
• Ensure interoperability between systems
• Reduce costs of exchanging information
• Reduce time to establish new interfaces
• Increase common situational awareness
• Increase NAS agility

4
SWIMThe Challenge
5
SWIMSegment 1 Overview

• SWIM will not implement separate infrastructure
  for Segment 1

• SWIM is working with SWIM Implementing Programs
  (SIPs) to finalize SWIM requirements documents
• SIPs include ERAM, TFM, AIM, Terminal, CIWS,
  ITWS, and WMSCR
• SWIM Program Office is currently evaluating
  service container software to be provided to SIPs

ATCSCC
ARTCC 1
SAMS
ERAM
NNCC
WJHTC
FTI
WMSCR
TFMSCIWS ERAMTDDS
TRACON 1
TDDS
VNTSC
ATCT 1
ITWS
TDDS
6
SWIMSegment 1 Capabilities

• Nine Segment 1 capabilities were derived from
  Communities of Interest
• SWIM will leverage existing infrastructures,
  processes, resources, and logistics chains that
  are part of the program offices implementing the
  nine SWIM capabilities

7
SWIMSegment 1 Core Services

• Core Services will be implemented by
  participating programs
• Through use of common commercial software
  specified by the SWIM Program Office
• By development or procurement of software that
  meets SWIM Program Office mandated standards.
• SWIM Governance ensures
• All parties adhere to the standards via oversight
  during software development and test phases
• Use of common protocols and interfaces, assisted
  by use of commercial software for some Core
  Services

8
SWIM FFM COIEnRoute and Terminal Information
Data Flows
VNTSC
WJHTC
TFMS
NORAD
ICE
Gateway (FTI)
Flight Information
Flight Information
TDDS
FTI
ERAM
Flight Information
TDLS
EFSTS
Flight Information
ARTCC
ASDE-X
RVR
Terminal Cluster (TRACON/Tower)
9
SWIM FFM COITFMS and Terminal Information Data
Flows
ARTCC
ERAM
ZDC
TFMS DRC
Flow Data, Reroute Data
Flow Information, Surface, Reroute Data
(Backup Data)
FTI
Surface Data
TDDS
Flow Information, RVR, and Reroute Data
TDLS
EFSTS
AOCs
AOCs
ASDE-X
RVR
Terminal Cluster (TRACON TOWER)
10
SWIMSegment 2 Planning Process Flow
11
SWIMSegment 2 Planning and Prototyping

• Stakeholder Coordination
• European SWIM Coordination
• Airspace User Coordination for Operational Needs
• Industry Analysis for future architecture
  options
• JPDO/OEP Coordination
• Concept Exploration/Demonstration
• Initial Air/Ground SWIM Demo Definition
• Centralized Architecture Prototype/Demo
• Program Evolution
• SWIM Evolution Strategy/Template
• Segment 2 COI/Requirements Development Process
• Future Segment/Service Planning
• Develop COI Charters/Rules of Engagement
• Develop COI Instructional Materials
• Establish Segment 2 COI Teams
• Initial Segment 2 Operational Capabilities/Archit
  ectures

12
SWIMSegment 2 Technical Plans

• Determine operational requirements for
  information that must be met in FY12-16
• Determine technical requirements needed to meet
  these operational requirements
• Determine how the Segment 1 architecture must
  evolve to meet these requirements
• Ex. Segment 1 federated approach vs. possible
  future centralized approach

13
OEP II Engineering for TBO and Collaborative
ATMFlight Object Requirements Development and
Demonstrations

• FY08
• Ongoing tasks planning and coordinating for
  International Flight Object Demonstration
  Activity
• Concepts and Integration Requirements for
• Electronic Flight Strip (EFS) and Departure Flow
  Mgmt (DFM)
• Decision Support Tools (DST)
• Tower Flight Data Manager (TFDM)
• FY09
• Define flight object requirements for
  trajectory-based operations which will enable
  movement of aircraft as data objects
• Conduct International Flight Object Demonstration
  Activity which will aid development and
  definition of Flight Object Interface
  Requirements
• FY10
• TBO Trajectory Management Enabler Flight Object
  Complete specification and full set of
  requirements
• Improve Collaborative ATM via advanced TFM
  methods Probabilistic TFM, Integration of
  weather, and TFM Flight Object

14
Daytona Beach NextGen Integrated Test Bed
Planned Demonstration Activities
15
SWIMWebsite
www.swim.gov
16
Backup
17
SWIMFY2008 FY2010 Activities / Service
Delivery Schedule
Milestone
18
SWIMFY2008 FY2010 Activities / Progress
Milestone
JRC 2B SWIMSegment 1B
JRC 2B SWIMSegment 2
Product(s) selection, contract award
19
SWIMContributions to Solutions Sets
Air Traffic Operations