Ames AOL Capabilities and Lab Connectivity
• DAG simulation capabilities at ARC
• Simulation Architecture
• ADRS-The Distributed Simulation Hub
• Some Requirements for ARC-LaRC connection
• Options and Proposal for data connection
DAG Simulation capabilities at ARC
• AOL
• ATC,
• multi aircraft
pilot stations
• Experiment control
• CDTI-LAB
• Fully equipped desktop
pilot stations
• CVSRF
• Fully equipped full
mission flight simulator
• Remote Sites
• SJSU
• Rotorcraft:
• Fully equipped desktop
pilot stations
ATC stations in
Airspace operations laboratory (AOL)
audio
CB
audio audio audio
Blade 100 0
wide CB CB CB CB
WAK phone
abq
AMA
Blade 100 0
wide
Ultra 60
w/ Sony
Ultra 60
w/ Sony
Ultra 60
w/ Sony
• 6 Center Controller positions
Ghos
G
S S
t out WAK
2K
WAK
2K
WAK
2K
• 3 full size Radar displays
phone phone
obs h
A
ADM F
SPS B
UKW • 3 wide screen Radar
Ultra 5
obs
displays
obs obs
camera
Ultra 5
Ultra 5
• 1 Traffic Management postion
Bl
adwi
Ghos
camera • Timeline Gui, Overview,
C B e de G
NN
10
00
t ort
obs
Ultra 2 Planning GUI
obs h
camera
(second
phone
TMC
monitor)
phone
• 1-3 TRACON controller
TR
DFW TMC audio
Blade
Ultra 60 positions
wide
1000
(second
room 278 CB room 280E monitor) CB
Controller Positions Recording & Communication Equipment
•Up to 12 pseudo pilot positions
room 278 room 280E
Amarillo (AMA)
Ghost South*
Ardmo re (ADM)
Falls (SPS)
camera came ra to remote VCR (3) on MACS stations
DFW TRACON* Bowi e (UKW)
phone speak er ph one (5-7)
TMC/Arrival Planne r
Ghost North* audio audio line to PC recorder (5 -6)
CB .
air-ground comm box (8)
position s
*confede rate po sitions
WAK Workload Assessment Keyboard (4)
Decision support tools accessible
for Air Traffic Controllers
• CTAS Traffic Management Advisor (TMA)
• Descent Advisor (DA) EDA
• Final approach spacing tool (FAST)
• Include:
– Scheduling and sequencing support
– Conflict probe
– Trajectory visualization tools
– Trial Planning and Advisories on controller request
• Self Spacing (CE11) support for TRACON controllers
• Controller Pilot Data Link Communication (CPDLC)
• ADS(B) state and trajectory intent information
Controller
Displays
(Radar):
Currently
CTAS
Planview
Graphical
User
Interfaces
(PGUI)
Controller displays (TRACON)
Trial Planning for Controllers
AAL 137
AAL 137 160 2
AAL 137
Aircraft target generation
Full mission flight simulators Desktop based flight simulators
Pseudo Aircraft System PAS Prerecorded traffic MACS
Multi Aircraft Control System
MACS pilot station
MACS Analysis View
Automated Agents
• CATS can act as model-based agent for
certain aspects of the simulation
• MACS can be configured for automatically
performing tasks or prompting operators
Experiment control and management
Cockpit Display of Traffic Information
Desktop based single pilot station
Integrates NASA Langley’s PC-Plane with the CDTI and data link
Simulation Architecture
ADRS*- The Distributed Simulation Hub
• *Aeronautical Datalink and RADAR Simulator
• Distribution of communication load:
– Unlimited number of servers and clients can be connected
by adding identical ADRS processes to the simulation
network that share their information
• Merging of multiple homogeneous aircraft data
sources into one scenario
• Host emulation
• Radar simulation
• Datalink simulation
• Aircraft state and trajectory data harmonization and
maintenance
• Process control and monitoring
Requirements for Ames-Larc
Data Connection
• Minimum/no changes to simulation end-processes
– ASTOR, CDTI, CDTI-PcPlane, CTAS, MACS, ACFS
• Aggressive Timeline
– Full Experiment in FY04:
– September 03: Demo with full capabilities
– May/June 03: Connectivity Event
– March 03: Initial Lab connection
• All existing and defined DAG capabilities should be supported
– Information exchange for
• Flight Plan information
• Complete aircraft state information @ 1 second
• Trajectory intent broadcast whenever it changes and at waypoints/intervals
• Route*, speed* and RTA uplinks
* CE6 only
• Trajectory request downlinks *
• Weather (RUC, NexRad, FIS-B) synchronization
• Long term perspective
– Support future projects (e.g. VAMS)
Possible Connections ARC to LaRC
Type status Communicat Changes to Resource Information Risk
ion processes requireme exchange Not to be
nts requirements ready
ADRS Completed in ADRS-LARC None at Ames, Low supported Low
To individual 1999 ICD and ASTOR may be
PcPlanes Frequently In use ARINC702+ incompatible.
Or PcPlane exists
PasCommon
ADRS Started in 2000, ADRS-ASTOR LaRC ADRS changes Low to supported moderate
To ADRS with basic ICD and need to be merged moderate
ASTOR with hooks delivered, ARINC702+ back to Ames baseline.
custom ICD ASTORs LaRC ?
connected ?
ADRS HLA supported ADRS changes for moderate supported Moderate
To ATOS at LaRC, not yet HLA and HLA.
with at ARC. A702p ARINC702+ ATOS need to
HLA/A702P message distribute/collect
handling information to/from
available ASTORS
ADRS To Not started HLA Needs to be built into high Probably high
ATOS Hub ADRS from scratch. supported
with pure May exist at Langley
HLA
ADRS-ATOS HLA/ARINC702P
connection
Long Range ARC-LaRC communication handled by ADRS to ADRS TCP/IP
via internet. (Supports all messages, reliable, frequently used, fast enough)
ADRS to ATOS high level communication handled by HLA wrapper
Aircraft dependent messages exchanged via ARINC 702P datalink
specification, new messages communicated as free text
Filed flight plans can be communicated by dedicated message or stored
locally in Scenario Data Base
Wind files pre-loaded, no on-line update
Weather Hazard synchronization TBD
Allows LaRC to run additional MACS stations for air traffic monitoring (or
participation as unmanaged aircraft).
LaRC
ARC HLA
ATOS
AOL ADRS ADRS ARINC702P
CDTI-LAB
ACFS
MACS