ERAM Flight Object Update and SWIM Overview

1
ERAM Flight Object Updateand SWIM Overview

• 23 June 2006
• Sid Rudolph
• Director, Aviation Solutions Architecture
• Lockheed Martin Transportation and Security
  Solutions
• sid.rudolph_at_lmco.com
• 1.301.640.3715

2
ERAM Overview

• ERAM replaces the primary and backup automation
  systems in the US En Route ATC facilities
• ERAM provides an open software architecture, with
  modular sub- systems, that is easily enhanced to
  support the evolving operational needs of the
  National Airspace System (NAS)
• The ERAM infrastructure provides increased
  security to protect the En Route information
  assets

• The ERAM architecture provides two highly
  available, full function channels
• Eliminates system down time due to scheduled and
  unscheduled outages
• Allows more flexibility for scheduled
  maintenance
• The ERAM architecture provides separation of
  mission critical and non-mission critical
  functions
• Reduces ATC critical service outages

3
ERAM Level I/II Schedule
2003
2004
2005
2006
2007
2008
2009
2010
3/03
System Requirements Review
8/03
Systems Engineering and Software Development
System Design Review
6/04
System SW Specification Review
2/05
System SW Detailed Design Review
2/06
SW Handoff To Test
11/06
System Integration Milestone 1
3/07
Integration and Test
System Integration Milestone 2
8/07
Test Readiness Review
10/07
WJHTC Government Acceptance
1/07
Site Readiness Review
10/07
First Site Deployment Activities
Installation Integration Test
Salt Lake City En Route Center
4/08
First Site Government Acceptance
10/08
First Site Initial Operational Capability
4/09
Last Site Government Acceptance
Last Site Deployment Activities
Miami En Route Center
11/09
Last Site Initial Operational Capability
4
ERAM Operational Environment Overview
Terminal Tower Radars Oceanic ATC
Terminal Tower Radars Oceanic ATC
ARTCC 1
ARTCC 2
. . .
FTI IP WAN
Airspace Users Traffic Flow Mgmt. Mexico, Canada
ATC Homeland Security Law Enforcement Weather
Data NOTAM Dist. System
Terminal Tower Radars Oceanic ATC
ARTCC 20
5
ERAM Flight Object

• The ERAM Flight Object is based on the Flight
  Object currently fielded in the User Request
  Evaluation Tool (URET)
• The URET Flight Object was deployed to the field
  in 2001
• URET is operational at all 20 US En Route Air
  Route Traffic Control Centers (ARTCCs) and shares
  flight data via Flight Objects within an ARTCC
  (between URET components) and between ARTCCs
  (URET to URET)
• The initial release of ERAM will share flight
  data via Flight Objects within an ARTCC (between
  ERAM components) and between ARTCCs (ERAM to
  ERAM)
• In follow on releases of ERAM, legacy interfaces
  will move to the Flight Object as the means of
  sharing flight data
• A task is underway to document the ERAM Flight
  Object and develop a replacement strategy for the
  current flight data distribution mechanism
• The initial flight data interfaces being
  considered to migrate to the Flight Object are
  Traffic Flow Management and Terminal Control
  facilities

6
ERAM Flight Data Object Components

• Flight Root object that contains all flight
  data
• Flight Plan Filed Flight Plan data
• Trajectory Computed path of flight
• Cusps Transition points in the trajectory
• Crossings Sector crossings
• Converted Route Represents complete set of
  fixes along the route
• Restrictions Restricted airspace that is
  crossed
• Addenda Additional information stored with the
  flight object
• Pairing Pairing of flight objects to tracks
• Coordination Data Data used in coordinating
  with neighboring sectors/centers
• Control Data For handoffs and point-outs
• Progress Flight Progress

7
ERAM Flight Object Data Model
8
ERAM Release 1 Physical Architecture
Other ARTCCs (ERAM, URET) NOTAM Dist. System
CMS Clients
WMSCR Airspace Users Non-US ATC
CTAS TMA
HADDS
FTI
US ATC (HCS, TRACON, FDIO) Radars
Router/IDS/ Firewall
Router/ Firewall/IDS
WARP TT
WARP TT
ECG I/F Procs
ECG I/F Procs
MC
MC
To Support ERIDS Wkstns.
ERIDS Server
NOTAM Dist. System
ECG LAN (CH A)
ECG LAN (Ch B)
ERIDS LAN
AT Specialists
D Positions
R Positions
ERIDS
ERIDS
Conflict Probe
Conflict Probe
WDP
SDP
FDP
FDP
SDP
WDP
APPL LAN (CH A)
APPL LAN (Ch B)
Data Sync
Data Sync
Enterprise Storage
MC Proc
MC Proc
MC
MC
MC LAN (CH A)
MC LAN (Ch B)
Channel A
Channel B
MC Wkstns
MC Wkstns
Security Wkstn
Security Wkstn
ERAM
Printers
Other En Route Programs
Other Systems in ARTCC
9
ERAM Release 1 Logical Architecture
Flight Object Clients Internal to ERAM
Common Msg. Set Processing
Traffic Flow Mgmt.
Homeland Security
Host-ATM Data Distribution System
Law Enforcement
Mexico, Canada ATC
Adjacent ERAM
Airspace Users
NOTAM Dist. System
Weather Data
Terminal ATC
Tower ATC
Oceanic ATC
Radar
Airspace User IFP
HADDS IFP
Non-US ATC IFP
Terminal IFP
FDIO IFP
Surv. Processing
NOTAM / GI Processing
Weather Data Processing
ERAM IFP
Monitor Flights
Flight Services
Aeronautic Services
Oceanic IFP
STCA
General Information Processing
Weather Data Processing
Surv. Data Processing
Flight Data Processing
MTCD
Display System Management
Trial Planning
IFP Interface Proxy
Display
Conflict Probe Tools
ERAM Subsystem
Subscribes to Flight Object
10
ERAM Flight Object Task Order

• In the ERAM system design, flight data is stored
  and distributed to client applications via the
  Flight Object
• In ERAM Release 1, the Flight Object has been
  documented as an internal design abstraction with
  Application Programming Interfaces (APIs) that
  provide a mechanism to access, create, modify and
  delete information in the Flight Object
• With ERAM Release 1, external systems can use the
  legacy Host-ATM Data Distribution System (HADDS)
  interface to access flight data
• The flight data available in HADDS is a subset of
  the Flight Object
• As part of follow-on ERAM releases, the Flight
  Object will provide the basis for sharing flight
  data with internal and external applications
• Under the ERAM contract, a task order is underway
  to support a standard Flight Object interface for
  internal and external users

11
ERAM Flight Object Task Order

• There are three key activities in the ERAM Flight
  Object Task Order
• Develop an interface document that defines the
  ERAM Release 1 Flight Object data fields and
  services that can be used by an external system
  to access the information
• Perform an analysis to identify the data and
  services needed to augment the ERAM Release 1
  Flight Object capabilities in order to
• Replace the HADDS as the means of distributing
  data external to the ERAM system
• Provide a mechanism for external systems to
  provide updates to the Flight Object data
• Support the flight data interoperability
  activities with Eurocontrol and the ICAO
  community

12
Notional SWIM Program Management Paradigm
Cost, schedule, and risk to be worked for each
Communities of Interest (COI). Schedule driven
by balancing system need against technical and
acquisition reality. Balance between cost,
schedule and risk is key
(Data Registry, Message Brokering, Info Security,
Infrastructure System Management, NAS System
Interfaces)
Core Services comprise services that must be
common across two or more COIs to manage the
publication, subscription, security, and other
aspects of the data efficiently. Implementation
timeline driven by needs of COIs
System Wide Information Management Program Status
and Forward Plans
12
13
Overview of LM SWIM RD Activities

• LMs SWIM RD activities are focusing on sharing
  Information and Services based on current ATC
  Systems to provide common situational awareness
• One of the key operational areas that is the
  focus of the LM SWIM RD is Sharing Flight data
  Information and Services based on URET/ERAM
• LMs SWIM test bed demonstrates information and
  services sharing using representative automation
  systems
• Washington (ZDC) Air Route Traffic Control Center
  (ARTCC) URET
• Richmond Virginia Airport Tower FDIO and
  Pre-Departure Clearance (PDC)
• Delta Airlines Operations Center (AOC) Flight
  Plan Pre-Processor
• Patuxent River Naval Air Station SAA Airspace
  Management Tool
• ATC System Command Center (ATCSCC) Demand
  Calculator

14
Flight Object Data Distribution

• The following design considerations for Flight
  Object data distribution are based on our
  experience with the URET and ERAM Flight Object
• Volume of Data contained within a Flight Object
• Considering all data for a flight, including one
  or more 4-D trajectories, a single set of flight
  information is significant in size
• In binary form, it could be as large as 100K
  bytes
• In XML form, it would be considerably larger
• The Flight Object data distribution mechanism
  must provide the following capabilities
• Subscribe to only flights of interest (given
  specified criteria)
• Publish only delta updates for a flight
• Support data compression of the XML

15
Flight Object Data Distribution

• The following design considerations for Flight
  Object data distribution are based on our
  experience with the URET and ERAM Flight Object
• Ownership and Eligibility
• In order to properly maintain the data integrity
  of the Flight Object, ownership must be
  established as well as Eligibility rules that
  determine who has the authority to update (e.g.,
  create, modify and delete) the Flight Object
• Ownership determines who publishes the data
• Eligibility determines who is authorized to
  update the Flight Object
• Eligibility can be on a field by field basis
  (e.g., a flight could be "owned" by TFM, while
  the Tower is providing gate information)
• The aircraft itself will be a source of some data
  and fields
• Extensibility
• The Flight Object will be defined by an XML
  schema and its associated version
• The data distribution mechanism may be required
  to publish some number of versions

16
Flight Data Todays Environment
En Route
Oceanic
URET
VOICE
INTIO
ATOP
HCS
Traffic Flow Management
INTIO
CMS
ETMS
INTIO
Terminal
INTIO
Service-B
ARTS/ STARS
ASDI
GPIO
ASDI
CMS
Airline Operations Center
FDIO
NADIN
Service-B
A/L FPS
GPIO
Tower
FDIO
DHS/DoD
Service-B
Service-B
NORAD
Law Enforcement
FPS
Customs
OASIS
MIL FPS
Internet
DUATS
General Aviation
Military Operations Center
Flight Service Station
17
Flight Data SWIM Environment
En Route
Oceanic
ATOP
ERAM
ATN/
Traffic Flow Management
FANS
TFM-M
Terminal
Fp3-s
Flight Data
ARTS/ STARS
Aero Data
Surv Data
Airline Operations Center
FDIO
A/L FPS
SWIM
NAS Status
Wx Data
Tower
Fp3-c
FDIO
DHS/DoD
NORAD
Law Enforcement
FPS
Customs

• Flight Data Core Services
• Common Route Conversion
• Common Trajectory Model
• Common Adaptation
• Common Restriction status

MIL FPS
AFSS
Fp3-c
Fp3
Fp3-c
General Aviation
Military Operations Center
Flight Service Station
18
Flight Data Information Sharing Architecture
Fat Client can provide API with FO services
Ownership passes as flight progress through
phases of flight
Web Browser
Fat Client
Fp3 TFM ARTCC1 Oceanic
ARTCCn
Local Flight Data
Thin Client
. . .
Flight Data Processor
Flight Data Processor
Data Only Interface
Publish XML Flight Objects
Subscribe to XML Flight Objects
Enterprise Service Bus

• Selective Subscription, for example
• By FO field
• By Flight
• Geographic
• Time
• Airlines
• Specify update rates

Flight Plan Manager
Flight Data Repository

• Services Provided
• Start Up
• Reconstitution
• Steady State Publish

Data Repository
19
Demo Configuration
ZDC ARTCC
RIC Tower
Pax River Naval Air Stn.
SWIM Enterprise Service Bus
Data Repositories
FP3 Server
ATCSCC
Delta AOC
Flight Data Core Svc.
Flight
SAA
20
RD Lab Physical Architecture
Pax River Naval Air Station
Military Dispatcher
Data Repositories
SAA Web Page
Fp3 Services
Enterprise Service Bus (BEAs WebLogic)
Demand Calculator
FDIO
Fp3
URET In a Box
Terminal/Tower System
Airline Services
TFM Services
En Route System
ZDC ARTCC
RIC Tower
Delta (DAL) AOC
ATCSCC