SYSTEM in its operational CONTEXT

Overview HITT A-SMGCS

Technical interfaces to external
(sub)systems

Human interfaces to
Controllers
Maintainers

System Context P. 1
 OVERVIEW HITT A-SMGCS

GATHER POSITIONAL INFORMATION

POSITIONAL INFORMATION

CONFIRM IDENTIFICATION

CHECK CONFLICT ALERT

INFORM DISPLAY

System Context P. 2
 Gather Positional Information

Digitisation Raw Video Radar Target Extraction Radar Target Tracking

Radar Tracks

Mode S Multilateration FUSION ADS - B

ATC Approach System

System Context P. 3
 Confirm Identification

FUSED
DATA

System Tracks

Flight Plan Proc. Sys. Docking System

IDENTIFIED
TRACKS

System Context P. 4
 Check for conflict alerts

FUSED
DATA

IDENTIFIED
TRACKS

Meteorological Info. CONFLICT Runway Configuration

ALERT!

System Context P. 5
 Summary

Radar Tracks ATC Approach System

FUSED
DATA
Mode S Multilateration ADS - B

IDENTIFIED Docking System

Flight Plan Proc. Sys.
TRACKS

Meteorological Info.
CONFLICT
Runway Configuration
ALERT!

System Context P. 6
 System Objectives

To support Traffic Controllers to

safely and efficiently guide the
traffic.

System Context P. 7
 SYSTEM CONTEXT A3000

System Context P. 8
 Surface Movement Radar (SMR) interface

The SMR(s) provide coverage of the airspace on/around the
airfield.

Type of SMR: TERMA ‘SCANTER’

Data is used for conversion to
 video (for presentation to the controller)
 position (as input for tracking)

Supplied data:
 Radar video (analogue or digital)

System Context P. 9
 Domestic Sensors

The SMR sensor sites are equipped with domestic
sensors to report status of:
 door contact
 air-conditioner
 environment temperature limit exceeded
 mains failure

The status of the sensors will be displayed in
the Control and Monitoring System of the A-
SMGCS

System Context P. 10
 Approach radar interface

The Approach Radar System provides coverage of the
airspace in the vicinity of the airfield (e.g. approaching and
departing aircraft), but not on airfield.

Data is used to
 provide automatic identification of arriving flights (together
with flight plan data from the Flight Data Processing System)
 predict runway incursions

Supplied data:
 Tracks
 Position (tracked)
 ID (SSR-code)
 Flight Level
 Track nr.
 Velocity
 Heading

System Context P. 11
 OpsView

Intended to provide a real-time overview of aircraft movement for:
 customs and immigration
 security services
 Fire departments
 Freight agents, logistic service providers.

Opsview consists of the following main functionality:
 A Traffic monitor, showing the real time traffic movements.
 Advanced Data Server (ADS)
 Web portal
 User management tool

OpsView is strictly limited as a monitoring function and can be accessed
via any PC with a web browser.

System Context P. 12
 OpsAnalyzer

OpsAnalyzer is a tool for analysis of aircraft and tow movements at the airport.

OpsAnalyzer makes use of segments of the airport layout:
 Runway
 Runway access
 Holding
 ATC Taxi
 Apron Taxi
 Stand
 Helicopter

OpsAnalyzer executes calculation to determine statistics about flight movements

related to the segments:
 time a aircraft has been in a segment
 time waiting in each segment
 average speed in each segment

OpsAnalyzer stores the results in a database where several reports can be

generated to view the results.

System Context P. 13
 Multilateration (MLAT) interface

Multilateration
 is a surveillance technique that compares the time-of-arrival of an
transponder signal from an aircraft or vehicle at several receiver
sensors.
 operates using the transmissions from:
 SSR transponders (Mode A/C) (=classical SSR transp.) or
 Mode S transponders (Mode A/C and Mode S)

The coverage of the airspace provided by MLAT:

 on/around the airfield
 Approach area

Data is used for
 a reliable automatic identification for transponder equipped aircraft or
vehicles on Approach

Supplied data (tracks):
 Position
 ID (mode-S)
 Optionally ID (SSR-code, when available)

System Context P. 14
 FDPS interface

Data is necessary for
 automatic identification of arriving and departing aircraft
 presentation in the Identification lists

Atleast required flight plan information:
 Identification in ICAO (callsign, ADEP, ADES)
 SSR-code
 Time related data (ETA, ETD, EOBT, ....)

Rest of supplied data:
 used for presentation only.

System Context P. 15
 Voice Communication System (VCS)

Voice communication will be recorded by the system
for playback during a replay session.
 audio from tower positions
 audio from ground controllers

System Context P. 16
 ADS-B interface

Automatic Dependent Surveillance – Broadcast (ADS-B)

The ADS-B System provides coverage of the airspace and
ground in the vicinity of the airfield.

Data is used for
 automatic identification of vehicles that are equipped with an
ADS-B transponder.

Supplied data :
 position (based on GPS or DGPS)
 unique ID (mode-S)

System Context P. 17
 Automated Weather Observation System
(AWOS)

The information recieved from AWOS is used for presentation
on the operational working positions.

The recieved Runway Visual Range measurements are used
for presentation only.

System Context P. 18
 Time reference interface

External source for a reliable reference time.

Data is used for
 synchronization of the components in the A-SMGCS system
 presentation on the operational traffic display

Supplied data
 the reference time (in UTC)

System Context P. 19
 Airfield Ground lighting System (AGL)

The system is recieving information from the Airfield Ground
Lightning System.

Data supplied :
 status of stop bars
 status of the runway lights

System Context P. 20
 CONTROLLERs INTERFACE A3000

System Context P. 21
 TRAFFIC DISPLAY for CONTROLLER
The controllers display presents:
 (Airport) maps
 Video (from the SMR(s))
 Tracks:
 Positions (built from SMR, approach radar, MLAT, ADS-B)
 Identifications (built from approach radar, MLAT, ADS-B,
FDPS, Docking system)
 Flight plan data (shown in lists and track labels)
 Alerts (shown in alert list and track labels)
 System Status and system time
The controllers display offers controls
 Runway configuration
 Visibility status
 Alertings
 Manual identification

System Context P. 22
 MAINTAINERS INTERFACE A3000

System Context P. 23
 WINDOWS for MAINTAINER
The maintainers position presents
windows for supporting functions:
CMS System Control (monitor status and control of
system)
Traffic Display (live traffic picture)
Desktop environment (Linux-KDE)
Archiving Control (store/restore to/from tape)
Replay Control (start/stop, speed control)
Traffic Display (replayed traffic picture)
SMR Control (monitor status and control of SMR)
System Context P. 24
 Summary
This concludes system context and its
technical interfaces to (sub)systems and
human interfaces.

Next:

Functional overview, describing the
 operational functionality for the controller
 supporting functionality for the maintainer

System Context P. 25