astos description

8/8/2019 ASTOS Description

1/33

ASTOSAdvanced Surface Movement Guidanceand Control System

System Description

Prepared by

AviBit data processing GmbH

Friedhofweg 16

A-8510 Stainz / Austria

www.avibit.com

February 11, 2008

USE AND DISCLOSURE OF DATA:

This document contains data that is proprietary to,

and the property of, AviBit GmbH, and shall not beduplicated, used or disclosed, in whole or part, for anypurpose other than to evaluate its content.


2/33

ASTOS System Description

Table of Contents

1 Overview ......................................................................................................................................... 1

2 Basic Functionality ........................................................................................................................ 3

2.1 Basic Functions of an ASTOS .................................................................................................. 3

2.1.1 Surveillance ....................................................................................................................... 3

2.1.2 Monitoring/Alerting (Safety Logic)...................................................................................... 4

2.1.3 Guidance............................................................................................................................ 4

2.1.4 Functional Description ....................................................................................................... 4 3 Hardware......................................................................................................................................... 7

3.1 Server........................................................................................................................................ 7

3.2 Controller Working Position (CWP)........................................................................................... 8

4 Software ........................................................................................................................................ 10

5 Data Fusion................................................................................................................................... 12

5.1 (Mono) Sensor Tracker ........................................................................................................... 13

5.2 Multi Sensor Tracker (Data Fusion)........................................................................................ 14

6 Human Machine Interface (HMI).................................................................................................. 15

7 Safety Logic .................................................................................................................................. 16

7.1 Introduction ............................................................................................................................. 16

7.2 Definitions ............................................................................................................................... 16

7.3 Alarm Checker Operating Modes............................................................................................ 17

7.4 SSR Code Exclude Filtering ................................................................................................... 17

7.5 Detailed Alarm Description ..................................................................................................... 17

7.5.1 Identified Vehicle on a Restricted Area ........................................................................... 17

7.5.2 Aircraft on a Restricted Area............................................................................................ 18

7.5.3 Identified Vehicle on a Runway ....................................................................................... 18 7.5.4 Approaching Aircraft and another Target on the Same Runway..................................... 18

7.5.5 Arriving Aircraft and Another Aircraft on an Intersecting Runway ................................... 18

7.5.6 Arriving Aircraft Approaching an Inactive Runway .......................................................... 18

7.5.7 A Target on the Same Runway in Front of a Departing Aircraft ...................................... 18

7.5.8 Departing Aircraft and Another Aircraft on an Intersecting Runway................................ 19

7.5.9 Departing Aircraft Lines Up an Inactive Runway............................................................. 19

7.5.10 Stop Bar Crossing............................................................................................................ 19

7.5.11 Same Taxiway Checks .................................................................................................... 19

7.5.12 Taxiway Junction Checks ................................................................................................ 19

8 System Monitoring and Control (SMC)...................................................................................... 20


3/33


8.1 Overview ................................................................................................................................. 20 8.2 Server Hardware Monitoring ................................................................................................... 23

9 Recording and Playback ............................................................................................................. 25

9.1 Recording................................................................................................................................ 25

9.1.1 Long-term archiving ......................................................................................................... 26

9.2 Data locking ............................................................................................................................ 26

9.3 Playback.................................................................................................................................. 26

9.3.1 Active Playback ............................................................................................................... 27

9.3.2 Active On-line playback ................................................................................................... 27

9.3.3 Active Off-line playback ................................................................................................... 29 10 AviBit Scope of Work............................................................................................................... 30

List of figures

Figure 1: ASTOS Block Diagram............................................................................................................. 1

Figure 2 : ASTOS as installed at Vienna Airport Tower. ......................................................................... 2

Figure 3: The logical functional elements and their interaction ............................................................... 3

Figure 4: Independent and dependent surveillance is an integral part of the A-SMGCS ....................... 5 Figure 5: The functional characteristics of ASTOS ................................................................................. 6

Figure 6: HP ProLiant 380 G5................................................................................................................. 7

Figure 7: PC, HP EVO DC7700 Small Form Factor................................................................................ 9

Figure 8 ASTOS User Display as installed at Vienna Airport................................................................ 10

Figure 9: ASTOS Data Fusion Overview............................................................................................... 13

Figure 10: Overview over the ASTOS Control and Monitoring Tool ..................................................... 22

Figure 11: Control and Monitoring, detailed for SSR input.................................................................... 23

Figure 12: System Management Homepage of a Server Computer..................................................... 24

Figure 13: Playback Control Window .................................................................................................... 27

Figure 14: Archive Selection Dialog ...................................................................................................... 28

Figure 15: Active Playback Indicator ..................................................................................................... 28

Figure 16: Playback Control Program ................................................................................................... 29


4/33


Page 1

1 OverviewASTOS - an advanced surface movement and guidance system (A-SMGCS) - is anessential tool to make airport traffic more efficient and safe and can particularly help toprevent conflict situations and congestions.

ASTOS is a modular and scaleable system providing surveillance, monitoring, control,guidance and planning functions for ATC. An open system architecture is employed forease of implementation and communication with other systems, and permits the systemto be tailored to meet the operational requirements of different users. The system buildingblocks are commercial off-the-shelf industrial computers running specialised applicationsoftware. Existing sensors such as radar are used for the surveillance tasks.

A central server collects data from sensors and other systems, performs processing anddistribute the processed data to the controller working positions (CWP). The variouscomponents of the system communicate via a fully redundant off-the-shelf high speedcomputer network.

Figure 1: ASTOS Block Diagram


5/33


Page 2

Figure 1 shows the block diagram of the ASTOS System. It consists of the followingmain-parts:

- Surface Movement Radar (SMR or Ground radar) and Video Decoder: Detectsobjects on the airport and provides primary radar data for all objects visible by theSMR.

- Secondary Surveillance Radar (SSR or ASR). Is used to display the approachsituation in the approach windows of the CWP and for initiation ground tracks ofarriving aircraft.

- Flightplan Database: Is used for deriving label information to be shown for alldetected aircraft and for the display of the departure window on the CWP.

- Multilateration System. Is used for detecting aircraft (and for the future also vehicles)equipped with Mode-S or Mode-A transponder on the ground.

- Data Fusion: Is the central processing unit of ASTOS. It performs all the requiredcentral processing and is serving all connected CWPs.

- HMI at the controller working positions (CWP): Displays the ground and approachsituation and interfaces with the controller.

- Archive and Playback Station: Automatically archives all data in the system and playsback certain situations as requested by the user.

- Interface to Airport lighting System: Is used to derive current status of the stop bars.For future extensions it is also planned to control airport lighting.

All components and interfaces are redundant in the system but this not shown in thefigure for simplicity reasons.

Figure 2 shows the ASTOS display as installed at Vienna Airport Tower.

Figure 2 : ASTOS as installed at Vienna Airport Tower.


6/33


Page 3

2 Basic Functionality2.1 Basic Functions of an ASTOS

In order to analyse the requirements of an Airport A-SMGCS and provide an evolutionarymodular concept, it is necessary to split the system into its logical functional elements.These basic functions are surveillance, monitoring/alerting, guidance and route planning,together with the necessary communications. The interaction between these functions isillustrated in the diagram below.

Control of lights / signs / pilot / vehicle displays

Plannedroutes

Planning rulesand objectives

ConflictresolutionsDeviation from

planned routes

Planned routes

Definition ofmonitoring

parameters(Conflict table)

HumanMachineInterface

Monitoring/ Alerting

RoutePlanning

Guidance

Location, Identity,Velocity, Quality

Surveillance

fusionExternal Information

co-op non co-op Movements

Figure 3: The logical functional elements and their interaction

2.1.1 SurveillanceThe most fundamental function for ASTOS is the surveillance of the aerodrome surface,together with the initial and final stages of flights. The objective is that both identity andposition of all traffic should be provided, with an adequate update rate to drive speed anddirection, if required. To achieve this objective a system providing co-operativesurveillance is required. For co-operative surveillance, targets need to be equipped withmeans for communicating position and usually identity information to ASTOS. It is alsoessential that some means of surveillance are available to enable the system to detectnon co-operative targets including obstacles.


7/33


8/33


Page 5

A-SMGCS

CO-OP

FusionSystem

IndependentSurveillance

SurfaceMovement

Radar

PrimarySurveillance

Radar

DependentSurveillance

MultiLateration

System

SecondarySurveillance

Radar

VehicleSquitter

AircraftTransponder

Additional application for data preparationand extra functionallity

NON CO-OP

Ground

Airborne

Figure 4: Independent and dependent surveillance is an integral part of the A-SMGCS

The performance, in terms of accuracy, integrity, probability of detection and update rateof the surveillance element is consistent with the situation awareness role of the system.

System functionality

Situation awareness

Situation monitoring and alerting

Alert situation resolution

Per Target functionality Data source identifier

Target report descriptor

Unique target identification

Target classification

Measured position of target referred to WGS-84 coordinates

Time of location

Track-parameters


9/33


Page 6

Track history, after-glow. Recording and Replay

Human-Machine functionality

Basic situation awareness

Alerts of situations requiring appropriate user action

Prompts to users with suggested actions for their approval

General Characteristics of ATC-Workstation (HMI)

Permit rapid situation assessment

Employ user friendly and familiar data entry means

Minimize the number of input actions required

Permits the user to make the decisions on those actions which he/she is responsiblefor

Maintain a balance between human and machine functions

Ensure a level of user workload which is consistent with efficient and effective activity

Permit full manual operation in the event of a failure of an automatic function

Immediately forward alerts to users in the event of a failure or when system

performance degrades.ASTOS

System functionality

Situationawareness

Tactical routeplanning

Alert situationresolution

Situation monitoringand alerting

Human-Machine functionality

Basic situation awareness

Prompts to unsers with suggestedactions for their approval

Alerts of situations requiringappropriate user action

Machine-Machine functionality

Data source identifier

Target report descriptor

Unique target identification

Target classification

Measured position of targetreferred to WGS-84 coordinates

Time of location

Track-parameters

Age-parameters G e n e r a l

R e q

i r e m e n

t s f o r

A T C - W o r k s t

t a i o n

( H M I )

Permit rapid situation assessment

Immediately forward alerts to users in the event ofa failure or when system performance degrades.

Ensure a level of user workload which isconsistent with efficient and effective activity

Permits the user to make the decisions onthose actions which he/she is responsible for

Minimize the number of input actions required

Be harmonized existing ATM-HMI

Permit full manual operation in the event of afailure of an automatic function

Maintain a balance between human andmachine functions

Employ user friendly and familiar data en trymeans

Figure 5: The functional characteristics of ASTOS


10/33


Page 7

3 Hardware3.1 Server

The standard hardware AviBit usually provides with an ASTOS delivery is a based on aHP ProLiant 370 G4 server running under Linux operating system.

ASTOS usually runs in a fully redundant configuration on two independent servers, onebeing the operational one and the other one being the hot standby one. Additionally ourdelivery includes two sets of serves, one being the operational system and the other onebeing the experimental and test system which is needed to check new software releases,or to perform tests.

The following table and figure describe the features of the proposed ProLiant servers:

Figure 6: HP ProLiant 380 G5

The proposed HP ProLiant G4 server has the following key features :

Processor and Memory

Processor One Intel Xeon 2.33 GHz Dual Core CPU, 4 MB L2Cache

Maximum Processor Capacity Two (8 Processor Cores)

Memory 2 GByte (2 x 1 GByte)

Memory Type PC2-5300 DDR2-667


11/33


Page 8

Max Memory 32 GByte Memory Protection Advanced ECC, Online Spare

Storage

Harddisks used 2 redundant disks for operating system andapplication: 36 GB SAS Harddisk, 10.000 rpm,hot pluggable, RAID 1

2 additional redundant disks for data recording:146 GB SAS harddisk, 10.000 rpm, hotpluggable, RAID 1

Storage Type SAS Hot Plug, RAID-1 (Mirroring)

Max Drive Bays 8 SAS Optical Storage DVD/CD RW drive

Storage Controller HP Smart Array P400/256 MB Controller (RAID0/1/1+0/5)

Deployment

Form Factor Rack

Rack Height 2 U

Networking Embedded Dual NC373i plus an additional dual-portgigabit server adapter NC360T for a total of 4 gigabit

network interfacesRemote Management Integrated Lights-Out Standard, ROM-Based Setup

Utility and Redundant ROMs

Hotplug Redundant Power Supply Yes

Hotplug Redundant Fans Yes

Operating Temperature 10 35 C

Operating Humidity 10 90%, relative

Other

Operating System Centos 4.2 Linux (Red Hat Enterprise Linux 4)

Monitoring and Control SNMP

The servers will be delivered with an Emergency Recovery CD-ROM by which thesystem can be installed within 15 minutes. All drivers, configuration files and software isalready included on this CD-ROM.

3.2 Controller Working Position (CWP)For the controller working positions we propose HP Compaq dc7700 Small Form FactorDesktop PC. They will also be equipped with two independent network interfaces and canfully be integrated into the redundant network.


12/33


Page 9

Their small size and low noise makes it easy to integrate them into an (existing) TowerConsole.

Figure 7: PC, HP EVO DC7700 Small Form Factor

The PC is delivered with an Emergency recovery CD-ROM by which the system can befreshly installed within 15 minutes. The PC has the following features:

Processor and Memory

Processor Intel Core 2 Duo E6300, 1.86 GHz, 2MB L2 Cache

Processor Capacity 1 (2 cores)

Memory Type PC-5300

Memory 1 Gbyte

Chipset Intel 965Q ExpressStorage

Storage Type Serial ATA

Storage Controller Dual Channel SATA controller

Harddisk 80 GB

Deployment

Form Factor Small Form Factor, Rack Height: 3U on a rack shelf

Dimension 33,78 x 37,85 x 10,03 cm

Networking Integrated Intel 82566DM Gigabit with an additionalPCIe based NIC to make a total of 2 NICs.

Operating System Centos 5 Linux (Red Hat Enterprise Linux 5)

Operating Temperature 1035 C

Operating Humidity 1090%, relative


13/33


Page 10

4 SoftwareASTOS consist of the following software parts:

The ASTOS server which is capable to be installed on multiple computers to supportfully redundant operation. The ASTOS server performs all internal processing likedecoding of all input data, target processing, target tracking, data fusion, datarecording, handling of connected user displays, monitoring and control of the overallsystem. The ASTOS server software can be provided for UNIX or Windows operatingsystems. We recommend to use it for LINUX operating system.

The ASTOS Display: Is the front-end of the overall system to the air traffic controller. Ithas been developed over two years time in very close co-operation with the air traffic

controllers at Vienna International Airport. Thus it fully covers the operational needsfor ground movement operation and control. The following figure shows a screen-shotof the ASTOS system as installed at Vienna Airport (refer also to Figure 2):

Figure 8 ASTOS User Display as installed at Vienna Airport.

The ASTOS display provides a huge number of features like the following:

- Display of ground situation and approach situation


14/33


Page 11

- Display of time to touchdown showing the aircraft call signs on a vertical time-scale.

- Display of flight plan information

- Manual labelling of non co-operative targets

- Up to three line and two column label display

- User definable maps and colors

- Day / night colors

- And many, many more

Please refer to the ASTOS HMI Description for more details. Alerting functionality: Continuously performs checks and rises alerts in case of critical

situations.

Recording and Replay Software: This software records the traffic situation on theserver and replays it on any User display if required.

Maintenance and Control Software: Is a technical control system being used toobserve correct operation by the maintenance staff and to perform systemconfiguration and optimisation.


15/33


Page 12

5 Data FusionASTOS contains a multi-sensor data fusion/tracking process (SDPS) which is capable offusing data from different internal and external data sources. These data sources are:

SMR data from the SMR data extractor/ground tracker

MLAT data from the MDS system

SSR data

Vehicle position data

ADS-B receivers

Tracks from other multi-sensor trackers

Basic system capabilities are:

Support of a maximum of 1000 simultaneous system tracks originating from any ofthese above mentioned data sources.

Tracking and identifying (correlating) aircraft and vehicles on the ground, within themaneuvering areas and in the runway approach areas, provided that all connectedsensors deliver data of appropriate quality on these areas.

Arrivals are identified and correlated automatically

Correlation is performed for all targets using information from the flightplans receivedfrom FDP

Vehicle information for correlation purposes can be received via external interfaces

Manual correlation information between flight plan and track number can be receivedvia the HMI.

All of the data sources can have different properties and the tracker needs to account forthat. So the SDPS employs different sensor level trackers which are tuned to the natureof the single sensor types. The following figure shows the basic data fusion/trackingmethod employed:


16/33


Page 13

plots Sensor Tracker(mono-)tracks

Multi SensorTracker

plots Sensor Tracker (mono-)tracks

plots Sensor Tracker (mono-)tracks

(system-)tracks

Radar

MultilaterationSystem

SurfaceMovement

Radar

. . . . . .

Plot checking and filteringSensor bias correctionTrack creation and uniquetrack-ID assignmentTwo-phase plot-to-trackassociationTrack state update andsmoothing

Sensor Tracker processing steps:System track creation and uniquetrack-ID assignmentMonotrack-to-systemtrack-association (multi-sensor coverdetection & correlation)Sytem track state computation viamono track data fusionTrack termination/continuation/ deletion

Multi Sensor Tracker processing steps:PSRSSRMLATADS-BArchive replays

Data sources:

Figure 9: ASTOS Data Fusion Overview

5.1 (Mono) Sensor Tracker(Mono) sensor trackers maintain a list of mono tracks that are in coverage of theconnected sensor for the tracking process. Each mono sensor tracker is a separatesoftware object. Each instantiated mono sensor tracker object is individually configurableand performs:

Plot checking and filtering according to the properties of the received plots andtheir position (area filtering).

Plot-to-track association via matching, using maximum likelihood estimation fortargets in proximity.

Track creation (incorporating unique track-ID assignment), termination,continuation and deletion.

Automatic systematic error (bias) correction. Track state update and smoothing using Kalman filtering. Recordings and loggings of statistical data.


17/33


Page 14

5.2 Multi Sensor Tracker (Data Fusion)The multi sensor tracker (or system tracker, respectively) merges the received monotracks to one list of system tracks. The multi sensor tracker performs:

Monotrack-to-systemtrack association via matching, using maximum likelihoodestimation for targets in proximity.

Maintenance of the mono track correlations representing the same targets, i.e.targets in multi sensor cover, within its system tracks.

Data fusion, i.e. the computation of a common system track state from multiplemono tracks, by weighted averaging.

Recordings and loggings of statistical data.


18/33


Page 15

6 Human Machine Interface (HMI)Please refer to the HMI description


19/33


Page 16

7 Safety LogicThe altering mechanisms built into the ASTOS system have been defined andimplemented in a very close cooperation with the Air Traffic Controllers at Vienna Airport.This work has been performed in the frame of a project with Eurocontrol titledEurocontrol Validation of A-SMGCS (EVA).

This project has been finished end of 2005 and the final acceptance tests of all alertingfunctionality has been performed in November 2005. The safety logic went operational atVienna Airport in December 2005. Since then ASTOS is officially validated againstEurocontrol A-SMGCS level 2 specifications.

Special care has been taken to ensure that all critical situations are detected by thesystem and alerts are given to the controller. On the other hand it had to be ensured notto rise too many false alerts. Otherwise the controllers would not trust the systemanymore.

In order to accomplish this target, intensive logging has been performed with the systemand all alerts (true and false) have been recorded and analyzed offline. The result of thisactivity, which lasted several months, was an optimal tuning of the alert functionalitywhich has finally been validated against Eurocontrol A-SMGCS level 2 specifications.

7.1 IntroductionThis section describes the general ASTOS alarm checker capabilities, which can becustomized for specific airports. Starting with the definition of terms used in this documentand the description of the alarm checker configuration are followed by a detaileddescription of all supported alarms. The following chapters cover reliability, logging,replay, simulation, limitations. Furthermore a description of the alarm checker processingchain will be presented.

7.2 DefinitionsThe following notions are used in this document:

Notion Meaning

Restricted Area Area defined by a controller with optional properties. A restricted

area may be defined by XML via TCP/IP. Each area may have astart time/date and an end time/date, which denote the period ofvalidity.

Safety Strip Rectangle around a runway which must be free for safe runwayoperations.

Reduced Safety Strip Same area as the "Safety Strip" but only half in size to eachside of the runway. (Especially not covering the RVR stationsand not including the ILS protection areas.)

ILS Protection Area Area around ILS equipment, which must be free for safe ILSoperations.


20/33


Page 17

Arrival Protection Area The Safety Strip plus the ILS Protection Area, which must befree for save arrival operations. Normally used to check forrunway incursions for landing targets.

Departure ProtectionArea

The Safety Strip only (without the ILS Protection Area), whichmust be free for save departure operations. Normally used tocheck for runway incursions for departing targets.

Line-up An aircraft entering a protection area after taxi.

Alarm Either a hint or an alert (see below).

Hint This is an indication that a special condition occurs. A hint isalso called a "Stage 1" Alert in common A-SMGCS literature.Generally a hint can be seen as an allowed situation that mightlead to a dangerous situation.

Alert This is a strong indication that a special potentially dangerouscondition occurs. An ASTOS alert is also called "Stage 2" alertin common A-SMGCS literature. A separate section in thisdocument shows examples of such an alert display.

7.3 Alarm Checker Operating ModesThe alarm checker supports an arbitrary number of different and fully customizableoperating modes, which can be changed online via XML over TCP/IP. The currentoperating mode and the list of available operating modes will be send out via XMLmessages over TCP/IP.For example, different operating modes can be used to distinguish between normal andlow visibility operations, different runway operation, etc. All alarm criteria parameters canbe set independently for each operating mode. The operating mode can also be switchedvia XML messages sent to the alarm checker process via TCP/IP.

Each of the alarms described in chapter 7.5 can be activated or deactivated in eachoperating mode individually.

7.4 SSR Code Exclude FilteringFor every operating mode a filter list of MODE-A codes and a filter list of MODE-S codes,which should be excluded from alarm checking, can be specified.

7.5 Detailed Alarm DescriptionThe system supports two different levels of warnings: Level 1 (Hint) and Level 2 (Alert).

7.5.1 Identified Vehicle on a Restricted Area

An identified vehicle (with any speed) entering a restricted area can be configured totrigger an alarm (hint or alert). Restricted areas can be entered with XML messages overTCP/IP.


21/33


Page 18

7.5.2 Aircraft on a Restricted AreaAn aircraft with a groundspeed below a certain configurable speed (e.g. 30kts) entering arestricted area can be configured to trigger an alarm (hint or alert). Restricted areas canbe entered with XML messages over TCP/IP.

7.5.3 Identified Vehicle on a Runway

Any vehicle (with any speed) entering a configurable area (either approach protectionarea, departure protection area, reduced safety strip or runway only) can be configured totrigger an alarm (hint or alert). Additionally a runway highlight area may be defined foreach runway, which will be highlighted in the case of an alarm.

7.5.4 Approaching Aircraft and another Target on the Same RunwayAlarm checking limits for approaching aircraft can either be defined using the time totouchdown or the distance to touchdown value. If an approaching aircraft drops below theconfigured limit, a configurable area related to the landing runway (either approachprotection area, departure protection area, reduced safety strip or runway only) can bechecked for other aircraft or vehicles. Additionally a so called suppress speed can bedefined, which an aircraft on the runway must exceed, in order to suppress a potentialalarm for the approaching aircraft. After the approaching aircraft passed the landingrunway's threshold, only the area in front of the landing aircraft will be checked for alarms.All of these alarm-checking criteria can be defined separately for hint and alert checking.This alarm will e.g. be triggered if another target is going to cross the runway while anarriving aircraft rolls down the runway.

7.5.5 Arriving Aircraft and Another Aircraft on an Intersecting Runway

Alarm checking limits for approaching aircraft can either be defined using the time totouchdown or the distance to touchdown value. If an approaching aircraft drops below theconfigured limit, any configured number of intersecting runways can be checked fordeparting aircraft. Additionally a suppress speed can be defined, which a departingaircraft must be below in order to suppress a potential alarm for the arriving aircraft.

All of these alarm checking criteria can be defined separately for hint and alert checking.

7.5.6 Arriving Aircraft Approaching an Inactive Runway

An alarm will be triggered if an arriving aircraft approaches a runway which is notcontained in the set of current active runways. Either a hint or an alert may be triggered.

7.5.7 A Target on the Same Runway in Front of a Departing Aircraft

When a departing aircraft (exceeding a configurable speed) enters the departureprotection area of a runway, a configurable area related to the departure runway (eitherapproach protection area, departure protection area, reduced safety strip or runway only)can be checked for other aircraft or vehicles (these areas may be configured differentlyfor aircraft and vehicles). Additionally a so called suppress speed can be defined, whichanother aircraft in front of the departing one must exceed, in order to suppress a potentialalarm. All of these alarm-checking criteria can be defined separately for hint and alertchecking. This alarm will e.g. be triggered if another target is going to cross the runwaywhile a departing aircraft rolls down the runway.


22/33


Page 19

7.5.8 Departing Aircraft and Another Aircraft on an Intersecting RunwayWhen a departing aircraft (exceeding a configurable speed) enters the departureprotection area of any runway, any configured intersecting runways can be checked forother departing aircraft. Additionally a suppress speed can be defined, which bothdeparting targets must be below in order to suppress a potential alarm. All of these alarm-checking criteria can be defined separately for hint and alert checking.

7.5.9 Departing Aircraft Lines Up an Inactive Runway

An alarm will be triggered if an arriving aircraft lines up a runway which is not containedin the set of current active runways. Either a hint or alert may be triggered.

7.5.10 Stop Bar CrossingIf an aircraft or identified vehicle crosses an active stop bar, an alarm will be triggered.Besides the normal alert display, the crossed stop bar will be marked with two red linesleft and right of the stop bar like this: "|--|". Additionally a stop bar inactivity time inseconds can be specified, suppressing stop bar crossing alarm this many seconds afterthe stop bar changed from inactive to active (to avoid alarms for targets just passing thestop bar when the stop bar turned back active).

7.5.11 Same Taxiway Checks

An alarm (of a configurable type) will be triggered, if all of the following conditions aremet:

- The distance between two taxiing targets lies below a configurable limit.

- The taxiing target's speed vector shows, that it will reach the other taxiing targetin front in a configurable amount of time

- The speed vectors angle difference of the two targets lies within a configurablelimit (to detect if the two targets are taxiing in the same direction).

- The speed difference between the two targets exceeds a configurable maximumvalue.

7.5.12 Taxiway Junction Checks

An alarm (of a configurable type) will be triggered, if all of the following conditions aremet:

- The distance between two taxiing targets lies below a configurable limit.

- The taxiing target's speed vector intersects with the speed vector the othertaxiing target within a configurable amount of time.

- The speed vectors angle difference of the two targets lies within configurablelimits (to detect if the two targets are really approaching each other).


23/33


Page 20

8 System Monitoring and Control (SMC)8.1 Overview

ASTOS comes with a separate local SMC workstation which can be located either in theASTOS server rack or at another suitable place (for example in a central monitoring andcontrol or equipment room). The ASTOS SMC solution has the following key features:

- supports multiple SMC workstations located at different places- uses SNMP and HTTP as the only communications protocols between SMC

workstations and the ASTOS server.-

comes with a comprehensive SNMP MIB (management information base) andcan thus be integrated into other third party systems and network monitoringsolutions

- All ASTOS monitoring and control functions can be executed from the SMCworkstation

- In addition to the server status which can be retrieved via SNMP GETcommands, SNMP traps are sent when critical events occur.

Basically ASTOS monitoring comprises the following areas and parameters (note that thisis only a subset of the actually available parameter list):

1. Hardware:- CPU temperature(s)- IO zone temperature(s)- Processor Fan status (Absent, nominal, Low, High etc.)- IO Zone Fan status (Absent, nominal, Low, High etc.)- Fan redundancy status- Power Supply status- Power supply redundancy status- RAID status

- Status of the single RAID member disks- Redundant network interface status- Hardware inventory: installed components, serial numbers etc.

2. Operating System State:- CPU utilization- File system utilization- Operating system and HP driver version numbers


24/33


Page 21

3. ASTOS:- general software status: EXEC, STANDBY, OFFLINE- status of the single subsystems- status of the single data inputs (SMR, MLAT, Flightplan, etc.)- data input counters (data input rate)

ASTOS system control comprises the following points:

- manual EXEC/STANDBY failover- software restart of the complete ASTOS software- re-configuration of subsystems- reboot (reset) the a complete server

The complete system status is displayed in an intuitive HMI. An example is depictedbelow:


25/33


Page 22

Figure 10: Overview over the ASTOS Control and Monitoring Tool

The figure above shows the total ASTOS system state. In this case, server 1 would beEXEC and server 2 would STANDBY. The total state of the system is ok (green).

In the figure above each ASTOS subsystem is represented by a box. The color of the boxshows the status of the subsystem:

- GREEN = OK- YELLOW = OFFLINE / STANDBY

- RED = NOT OK

Control actions can be executed be clicking on one of the boxes. Also a more detailedview on particular subsystems can be retrieved by clicking on the boxes. For example:


26/33


Page 23

Figure 11: Control and Monitoring, detailed for SSR input

Furthermore an audible alert can be triggered or a dry contact (relays) can be closedwhich stays on until it is confirmed.

8.2 Server Hardware MonitoringIn addition to the SMC application running on the ASTOS SMC workstation which alsomonitors basic hardware parameters, a web browser can be used to access the WBEM(web based management) pages of the servers. These pages contain information abouthardware status, grant access to the integrated management log (a server hardware logwritten in an EEPROM) and much more. This pages are created by an applicationsupported by HP on the ProLiant servers. An example of such a page is shown below:


27/33


Page 24

Figure 12: System Management Homepage of a Server Computer

The interface is very comprehensive and allows an in depth look into the serverhardware.

More information about the HP WBEM can be obtained on the following web site:

http://h71028.www7.hp.com/enterprise/cache/9920-0-0-225-121.html


28/33


Page 25

9 Recording and Playback

The optional recording software can be installed directly on the ASTOS server but also adedicated archiving server can be provided if required.

ASTOS generally supports the following types of recording:

1. Output recording: All data at the output from the ASTOS server are recorded.This is basically all what the CWP display program receives. The purpose of thisrecording is to have an active replay, meaning that an ASTOS HMI or anotherCWP can be fed with the recorded data and users can actively modify all clientHMI settings during the playback. This includes things like zooming, panning,colours, etc.Output recording is performed permanently.

2. Raw data recording: Recording of all data received from the external interfaces,all in their particular formats. Such a recording can by played back to the ASTOSdata fusion server which is especially configured to read its input data from thearchive rather than from the actual hardware interfaces. In this way it is possibleto run an ASTOS server in a test environment without actually having all physicalinterfaces or data sources available. The purpose for this is parameter tuning,configuration etc.

Raw data recording is done on demand, meaning: When raw data recording isnecessary, it is manually turned on and after the recording session, it is turned off

again. The reason is the huge amount of data which is usually collected duringraw data recording.

The following general description applies to all of the above mentioned recordingmethods.

9.1 RecordingRecording data files are primarily kept on the harddisk of the ASTOS server system. Both(redundant) servers perform the same recording function so basically all recordings areavailable twice. The recording process is independent of the ASTOS software. It startsautomatically when the system is booted and it connects to the current ASTOS EXEC

server and records all data. In addition the recording process is also independent of anyplayback activity. One recording file per day is created. The current day recording file canimmediately be used for playback. The daily files can be accessed by the administratorvia the file system and can be transferred through the network for whatever purposes(e.g. manual long-term archiving). Replay of these files at the ASTOS HMI (provided onthe local monitoring and control workstation) or on Microsoft Windows based office PCsis also possible.

The data retention time depends on the harddisk capacity of the ASTOS server and onthe actual amount of data being fed into the ASTOS system.

A special "housekeeper" process runs once per day to keep track of the recording files. Ifthe harddisk is about to become full, the oldest recording files are automatically deleted.


29/33


Page 26

In order to prevent automatic deletion of old recordings, long term archiving can beswitched in as described below.

9.1.1 Long-term archiving

Long term archiving can be achieved by connecting a tape drive with sufficient capacity toone of the ASTOS servers. A minimum native (uncompressed) capacity of 200GB isrecommended.

When a tape drive is connected, the ASTOS housekeeper process automaticallyappends the newest recording files to the tape and in addition eject the tape when it is fulland send an e-mail to an administrator asking for a new tape.

If required by the customer, long-term archiving can also be performed on CD-ROMs,

DVDs or on external USB harddisks.

9.2 Data lockingData locking is usually required when incidents occur. All recorded data about theincident need to be locked then. Data locking has the following objectives:

- incident data are securely stored on a storage medium where it cannot be alteredanymore

- incident data must not be seen by unauthorized personnel, so it is removed fromthe ASTOS servers

Data locking is supported by ASTOS using the following method:- A special data lock program exists which can only be started by an administrator

user.

- The program asks for a time range of the data to be locked

- The associated recording data files are located on the harddisk and the data filesare copied to two different CD-ROMs or DVDs.

- In addition to the data files, a PC (Windows XP) based replay program is alsocopied to the CD-ROM or DVD. This makes the CD-ROM/DVD self contained,meaning that any Windows XP based PC can be used to replay the data.

- After copying to the DVDs, a separate data verification run is executed in order to

make sure that the data is correct.- After the data is verified, it is optionally erased from the harddisk

9.3 Playback

Depending on the type of recording, the type of playback must be chosen as follows:

- Active Playback: Can be done for output recordings.


30/33


Page 27

- Raw Playback: Needs a dedicated ASTOS test server and can only be done forraw data recordings.

9.3.1 Active Playback

Active playback can be started in two different ways:

1. On-line on the CWP computer, during the normal ASTOS client live function or

2. Off-line on a separate workstation or PC

9.3.2 Active On-line playbackOn-line active playback is supported on the ASTOS HMI (running on the local monitoringand control computer). The HMI contains a special "Replay archive" menu entry whichopens the playback control window:

Figure 13: Playback Control Window

In this dialog, he first presses "Select archive" to select an archive file which is currentlyon-line. A dialog window like the following appears:


31/33


Page 28

Figure 14: Archive Selection Dialog

The window shows the available on-line archives and the date/time ranges of data theycontain. After selecting an archive, the playback control window can be used to controlthe start time and speed of the playback. After pressing the PLAY button, the display isdisconnected from the live data feed and starts the archive replay mode which isindicated by an off-line indicator (red rectangle with white cross in the upper left corner)and the "Archive replay" text in the upper left window corner as shown below:

Figure 15: Active Playback Indicator

During the active playback mode, the ASTOS HMI remains fully functional. Only functionswhich would require a server response (like changing flight-plan data or assigning manualground tracks. etc.) are not possible. All other functions and settings can be performed asin live mode.

When the playback control dialog is closed, the ASTOS HMI returns to normal liveoperation.


32/33


Page 29

9.3.3 Active Off-line playbackThis can be performed on any Windows XP based PC which has access to therecording data files. A Linux version is also available upon request.

For offline playback, two programs are started, a playback control program and theASTOS HMI. The playback control program is shown below:

Figure 16: Playback Control Program

The program allows to select the recording data file, the desired playback start time andthe playback speed. After pressing the "START Playback" button, the data is sent to theASTOS HMI for display which is usually running on the same computer. During theplayback, the ASTOS HMI remains fully functional as is during On-line playback.

The same playback software is also copied to the DVDs containing locked data (see 9.2).


33/33


10 AviBit Scope of WorkAviBit usually provides the following deliverables / services:

Provision of all software licenses and hardware delivery

AviBit usually provides all requires software licenses and delivers and installs all requiredcomputer and networking hardware

Programme Management and System Engineering

Together with the customer AviBit will install a project team, perform the appropriateproject management (according to the project management plan), perform configurationmanagement and perform the system engineering. AviBit will provide the requiredprogramme management and system engineering resources to ensure the programme tobe carried out in accordance with the agreed specifications and timeframes.

Factory Acceptance Testing (FAT)

AviBit will perform a factory acceptance test (FAT) in the premises of AviBit before theequipment is shipped to site. If required the customers engineering staff will attend theFAT.

Installation

AviBit will install the components as agreed with the customer. The customer is

responsible to install the required cables and to provide electricity supply and networkinfrastructure as required. AviBit will install the software on the target systems includingthe operating system.

Site Acceptance Testing (SAT)

Together with the customer AviBit will perform a site acceptance test in accordance witha mutually agreed site acceptance test procedure.

Training and Documentation

AviBit will provide on-site maintenance and user training course (in English language) asrequired by the customer. Operations manuals will be provided in English language.

Warranty

Usually AviBit provides full system warranty and maintenance for one year after SAT.

astos description

Documents