GOS Manual

8/17/2019 GOS Manual

http://slidepdf.com/reader/full/gos-manual 1/138

Effective Date: October 2005 11.0

Page 1 of 8PP-GosRUH-PrelPages

Installation Operation Maintenance

Manual

GOS

Gate Operating System for

King Khaled International irport

Date: June 2008 Version: 1.0





IOM Manual

GOS Gate Operating System Introduction

©Safegate Group Page 1 of 6Document: PP-GosRUH-PrelPages Date: June 2008 Version: 1.0

INTRODUCTION

CHAPTERS AND APPENDICES

CONTENTS

Section Description

Preface Introduction

Chapter 1. System Description

Appendix A. System Topology

Appendix B. Redundant GOS Server

Appendix C. Camera Integration

Chapter 2. Installation

Appendix A. System Configuration

Chapter 3. Operation

Appendix A. GOS Features

Appendix B. GOS Access Manager

Appendix C. GOS Reporter

Chapter 4. Maintenance

Appendix A. GOS Fault Finding Guide



IOM Manual


Page 2 of 6 ©Safegate GroupDocument: PP-GosRUH-PrelPages Date: June 2008 Version: 1.0

COPYRIGHT

© Copyright 2008 by Safegate Group. All rights reserved. This item and the information containedherein are the property of Safegate Group. No part of this document may be reproduced, transmitted,

transcribed, stored in a retrieval system, or translated into any language or computer language in anyform or by any means otherwise, without the expressed written permission of Safegate Group,Stenåldersgatan 2A, SE-213 76 Malmö, Sweden.

HISTORY

Version Date Descript ion1.0 June 2008 First Release

ORIGINAL DOCUMENTS

The following is a list of original documents used to create this manual.

File Name Version Chapter/Appendix Descript ion

PP-GosrRUH-PrelPages 1.0 INTRODUCTION General Safety Information

SY-GosRUH-System 1.0 Chapter 1. SYSTEM DESCRIPTION

SY-AppA-GosRUH-Topology 1.0 Appendix 1A. Airport Topology

SY-AppB-GosRUH-Redundant 1.0 Appendix 1B. Redundant Server

SY-AppC-GosRUH-Camera 1.0 Appendix 1C. Camera Integration

IN-GosRUH-Installation 1.0 Chapter 2. INSTALLATION

IN-AppA-GosRUH-SystemConfig 1.0 Appendix 2A. System Configuration

US-GosRUH-Operation 1.0 Chapter 3. OPERATION

US-AppA-GosRUH-Features 1.0 Appendix 3A. GOS Features

US-AppB-GosRUH-AccessManager 1.0 Appendix 3B. GOS Access Manager

US-AppC-GosRUH-Reporter 1.0 Appendix C. GOS Reporter

MA-GosRUH-Maintenance 1.0 Chapter 4. MAINTENANCE

MA-AppA-GosRUH-FaultFindGuide 1.0 Appendix 4A. Fault Finding Guide

Note: This page is to be updated with every authorised change to the manual.



IOM Manual



INTRODUCTION

This manual has been compiled to give the reader an understanding of installation, operation and

maintenance (IOM) procedures of the GOS Gate Operating System, with a focus on safety andefficiency.Note: Some documents in this manual may include blank pages for convenient double-sided printing.

The manual includes chapters with contents for quick access to information as follows:

IntroductionInformation about copyright, version history, original documents used to create this manual, a generalcontents list for quick access to information. Contents are also included at the beginning of each of themain chapters for quick access to information. There is also an abbreviations list.

Chapter 1 – System Description A system overview of the constituent system parts with a detailed technical description. A description

of system architecture and the software and hardware components involved.Note: Appendix documents may be included with this chapter if required.

Chapter 2 – InstallationGuidance to system installation engineers with references to software programming instructions,calibration procedures and cross references to the Maintenance chapter.Note: Appendix documents may be included with this chapter if required.

Chapter 3 – Operation A system operation and user interface description.Note: Appendix documents may be included with this chapter if required.

Chapter 4 – Maintenance

A system designed to minimize maintenance downtime. The chapter also includes high-levelmaintenance procedures and fault diagnosis information.Note: Appendix documents may be included with this chapter if required.



IOM Manual



ABBREVIATIONS

Term Description

AC Alternate Current

ACC Apron Control Centre

ACFS Aircraft

ACTYP Aircraft type

ALB Aircraft Loading Bridge

APA Aircraft Parking Aid

APACC Aircraft Parking Aid Central Computer

ATA Actual Time of Arrival

ATD Actual Time of Departure

CCR Communication Concentrator Unit of APACC

CDB Central Database

CL Centre Line

COTS Commercial Off-the-shelf Items

CPU Central Processing Unit

CR Communication Room

CU Control Unit of Docking System

DC Direct Current

DGS Docking Guiding System

ESD Electrostatic Discharge

ETA Estimated Time Of ArrivalETD Estimated Time Of Departure

FAT Factory Acceptance Test

FIDS Flight Information and Display System

GBMS General Building Management System (maintenance system)

GMS Gate Management System

GOS Gate Operating System, same as APACC

HMI Human Machine Interface

IB Information Broker, an interface between CDB and other systems

I/O Input/ Output

IOM Installation Operation MaintenanceISO International Standardisation Organisation

IT Information Technology

LCC Life Cycle Cost

LCD Liquid Crystal Display

LED Light Emitting Diode

LRU Line Replaceable Unit

MDT Mean Down Time

MTBF Mean Time Between Failure

MTTR Mean Time To Repair

NTP Network Time Protocol

PBB Passenger Boarding Bridge



IOM Manual



ABBREVIATIONS

Term Description

QCP Quality Control PlanRAM Random Access Memory

RH Relative Humidity

RVR Runway Visual Range

SAT Site Acceptance Test

SBU Safety Back-up

SMGCS Surface Movement Guidance & Control System

S/N Serial Number

SQL Structured Query Language

STA Scheduled Time of Arrival

STD Scheduled Time of Departure

TCP/IP Transmission Control Protocol/Internet Protocol

U/S Unserviceable/ Out of Service

UPS Uninterruptible Power Supply



IOM Manual





IOM Manual

GOS Gate Operating System Chapter 1. System Description

©Safegate Group Page 1 of 12

Document: SY-GosRUH-System Date: June 2008 Version: 1.0

CHAPTER 1

SYSTEM DESCRIPTION

CONTENTS

Section Descript ion Page No.

1.

INTRODUCTION ........................................................................................................... 3

1.1 GENERAL ......................................................................................................... 3

2. USING A CENTRAL DOCKING & GUIDANCE SYSTEM............................................ 3

2.1 GENERAL PURPOSES .................................................................................... 3

3. SYSTEM ARCHITECTURE ........................................................................................... 4

3.1 GENERAL STRUCTURE.................................................................................. 4

3.2 GOS SYSTEM COMPONENTS ....................................................................... 5

3.3 CONFIGURATION OF SOFTWARE ................................................................ 7

3.3.1

General ........................................................................................................ 7 3.3.2

Gos Software Module Architecture/Descript ion..................................... 7

4. STANDARD FEATURES ............................................................................................ 10

4.1 GENERAL ....................................................................................................... 10

4.2 DOCKING MONITORING AND CONTROL ................................................... 10

4.2.1 General ...................................................................................................... 10

4.3 GOS EVENT LOG FILES ............................................................................... 10

4.3.1

General ...................................................................................................... 10

4.4 AUTOMATIC UPLOAD OF SAFEDOCK DOCKING LOG FILES .................. 10

4.4.1 General ...................................................................................................... 10

4.5

AUTOMATIC UPLOAD OF SAFEDOCK CONFIGURATION FILES ............. 10 4.5.1 General ...................................................................................................... 10

4.6 SAFEDOCK MAINTENANCE ......................................................................... 10

4.6.1 General ...................................................................................................... 10

5. ENHANCED FEATURES (OPTION) ........................................................................... 11

5.1 GENERAL ....................................................................................................... 11

5.2 REDUNDANT GOS SERVERS ...................................................................... 11

5.3 INTERFACE TO EXTERNAL SYSTEMS ....................................................... 11

5.3.1 FIS Interface ............................................................................................. 11

5.3.2 TMS Interface ........................................................................................... 11

5.4

STAND IMAGES FROM CAMERA ................................................................. 11

5.4.1 General ...................................................................................................... 11

5.5 INTERLOCK FUNCTION ................................................................................ 11

5.5.1 General ...................................................................................................... 11

6.

INSTALLATION .......................................................................................................... 12

6.1 GENERAL ....................................................................................................... 12



IOM Manual


Page 2 of 12 ©Safegate Group


GOS System Topology Appendix A

Redundant GOS Server Appendix B

Camera Integration Appendix C



IOM Manual




1. INTRODUCTION

1.1 GENERAL

Safegate’s concept for central Docking & Guidance Control is called GOS, the GateOperating System. The GOS is a multi-user system, based on Microsoft’s WindowsNT/2000 operating system.

The GOS concept is briefly described in this SYSTEM DESCRIPTION, and the mainfunctions, which are specific for the particular Airport, are focused upon.

Maintenance of GOS is described in the MAINTENANCE chapter of the IOM manual.

The operation of the GOS system, Docking Control and Monitoring, is described in theOPERATIONS chapter of the IOM manual.

Maintenance of Docking & Guidance System, done from the GOS system, isdescribed in the MAINTENANCE chapter of the IOM manual of SAFEDOCK.

Items or features below stated as ‘optional’ are available from Safegate but are not apart of the delivery.

A GOS system normally includes only the features, which are especially specified fora particular customer. Chapter 3, OPERATION, of the IOM MANUAL for a deliveredsystem includes an appendix, called GOS FEATURES. That appendix is a subset ofthis generic document and covers only the features delivered.

2. USING A CENTRAL DOCKING & GUIDANCE SYSTEM

2.1 GENERAL PURPOSES

Using the Gate Operating System/GOS will give the operator a detailed view of all theStands and the Docking Systems at the Airport and an option of central dockingcontrol, event monitoring/logging and maintenance.

The possibility to interface to other computer systems at the airport provides access todata such as Scheduled Flight information. A FIS system may also be updated withactual time of arrivals and departures for statistics and billing purposes etc.

The Docking system can also be a part of a Ramp Information Display System/RIDS.

The Gate Operating System/GOS is used for the general purposes described in thetable below:

General Purposes Realisation

- Central Stand Monitoring The GOS Monitor

- Central DGS Error Log The GOS Logging Feature

- Central System Event Log The GOS Logging Feature

- Docking Log The DGS Logging Feature

- Central Maintenance of DGS The Stand Configuration Utility and the

Stand Config PrintOut Utility

- Status Report to a CentralMaintenance System

Interface GOS – CMS (option)

- Airfield Lightning Control

- Push-back info to Ground Radar

Interface GOS – SMGCS (option)


- Stand Area Monitoring The GOS Camera Interface and StandImage logging (option)



IOM Manual




At arrivals the following functions are realised with the GOS system:

Functions at Arrivals Realisation

- Capture of Aircraft Type to be

docked

Data Entry at a GOS Workstation

Data gained from a FIS connection*

- Check of Aircraft Type to be dockedto a specified Stand


- Capture of Flight No. Data Entry at a GOS Workstation

Data gained from a FIS connection

- Capture of Registration/Tail No. Data Entry at GOS Workstation (option)

Date gained from a FIS connection*

- Initiation of the Docking Procedure Entry of a Command (aircraft type) froma GOS Workstation or automatically ondata gained from a FIS connection

- Capture of Blocks On Time GOS – interface to FIS (option)

- Display of flight information GOS – interface to FIS (option)

At departures the following functions are realised with the GOS system:

Functions at Departures Realisation

- Capture of Flight No. Data Entry at a GOS Workstation


- Capture of Registration/Tail No. Data Entry at GOS Workstation


- Capture of Blocks Off Time GOS – interface to FIS (option)- Display of flight information GOS – interface to FIS (option)

3. SYSTEM ARCHITECTURE

3.1 GENERAL STRUCTURE

The Gate Operating System/GOS concept of Safegate is a multi-user system, basedon Microsoft’s Windows NT/2000 operating system with the Oracle’s databasecommunication software SQL*Net, as the main alternative.

Control and Monitoring of the docking guidance systems, called SAFEDOCK, is

performed by the GOS, which uses an Ethernet LAN for the communication with eachdocking system. Commands from GOS are made to put SAFEDOCK in theoperational modes needed, and as soon docking status has changed, a transactionwill be created by SAFEDOCK and sent to the Central Computer system, andautomatically distributed to all GOS nodes.

At one time all subsystems have the total information about status of all SAFEDOCKsystems, at terminals and at remote Stands.

Also status of external systems like the Aircraft Loading Bridge and other equipmenton apron can be reported to GOS.

The Central Docking Control System, or GOS, comprises one or several WorkStations, used for maintenance and operation of the SAFEDOCK units, and also oneServer/Concentrator, communicating with each Docking & Guidance System and with

other Airport Systems, such as FIS and the central maintenance system/CMS.



IOM Manual




3.2 GOS SYSTEM COMPONENTS

A GOS Server may be used for the logical connection to external systems and for acentral database. The server also controls the connection to the docking systems.The DGS systems are connected to the GOS by either an Ethernet LAN or serialcommunication media.

Workstations at separate locations are used for Airfield Stand Monitoring and DockingControl and for updating Scheduled Flights and System dependent parameters andmaintenance of DGS.

The physical communication media, preferably used, is Ethernet 10/100Mz with theTCP/IP protocol.

An example of an Airport System integrated with GOS is illustrated in the belowfigure. The specific system topology for a site can be found in appendix A to thismanual.



IOM Manual



Common Data Network/Ethernet LAN


External Systems, option

FIS/GMS

CMS

NTP

Gate Mana ement S stem or FIS

Central Maintenance System/CMS

NTP Time Server (if available)

Operation & Maintenance

Ethernet LAN

GOSServer

SDK

HUB HUB

SDK

HUB

………………….

SDK SDK

HUB

GOSWorkstation 1

Patch cables to horizontalnetwork outlets, 10BaseT / RJ 45

# SAFEDOCK units

connected to Ethernet LAN

FIGURE 1.1 GOS SYSTEM TOPOLOGY



IOM Manual




3.3 CONFIGURATION OF SOFTWARE

3.3.1 General

The GOS is a multi-user system, based on Microsoft’s Windows NT/2000 operatingsystem.

The GOS system comprises a set of software modules that can be executed in one orseveral PC computers, connected to data networks.

The GOS Software is mainly built around two items, called GosKrnl and GosMMi,which are common to all subsystems, and one configuration file for each subsystem,called GOS.INI. GosKrnl also uses a number of modules (DLLs and EXE files). TheGOS.INI file on each PC specifies the modules that will be used on each PC.

Below is a description of each individual item that builds up the GOS system. This isfurther illustrated in figure 1.2 below.

3.3.2 Gos Software Module Architecture/Descr ipti on

The following is a short description of each software module. All of them may notalways be included in a GOS system configuration.

(a) Gosinstall.exe

Installation program used to install GOS software on each computer.

(b) GOSMMI.exe

GOSMMI.exe is a monitor program used to monitor and control theSAFEDOCK system. It also displays the layout of the airport.

GOSMMI.exe interfaces to GOSKRNL.EXE. The two programs arecompletely separated from each other. Thus, for the GOScommunication to work properly, there is no need to runGOSMMI.exe. GOSMMI.exe is only to run when monitoring andcontrol is required. Since GOSMMI.exe gets all information fromGOSKRNL.EXE, the latter has to be running for GOSMMI.exe towork.

(c) GOSKRNL.EXE

GOSKRNL.EXE handles all communication between SAFEDOCKand GOS nodes. GOSKRNL.EXE is the program that starts the GOSsystem. When GOSKRNL.EXE is started, it loads a number ofmodules (DLL and EXE files). For finding out what files to beloaded/used GOSKRNL.EXE reads configuration information from afile called GOS.INI.

(d) GOS.INI

The GOS.INI file is unique for every GOS PC. From this file, the GOSapplication gets its start–up parameters.

The file is read by the GOS application at start up (booth

GOSKRNL.EXE and GOSMM.EXE).The file contains information such as whether the computer shouldact as a GOS server or Workstation, which stand connections toactivate, or whether time synchronisation shall be made on theSAFEDOCKs from GOS etc.

(e) GOSUTIL.DLL

This is a resource file for all modules in a GOS system. It contains theinterface between GOSKRNL.EXE and its modules (SAFEDOCK.DLLand COMLIDGS.DLL etc.).

(f) SERVICELINK.DLL

This module allows GOSMMI.EXE to connect to GOSKRNL.EXE.This link can also be used when other stand-alone programs need to

connect to GOSKRNL.EXE.



IOM Manual




(g) SAFEDOCK.DLL , SD_UDP.DLL, SD_TCPID.DLL and COMLIDGS.DLL

These modules handle the communication between GOS andSafedock/Loopsystem. When a SAFEDOCK system is used, theSAFEDOCK.DLL (Serial communication) orSD_UDP.DLL/SD_TCPID.DLL (Ethernet LAN) module is used. When

a Loop system is used, the COMLIDGS.DLL module is used.

(h) SETTIME.DLL

This module handles the time synchronisation of the SAFEDOCKreal-time clock.

(i) SETUPCAL.DLL

This module handles a remote connection to SAFEDOCK withSDConfig.exe.

(j) NETHUB.DLL

This module makes a PC computer act as the GOS server. EveryGOS system needs to have one server. When information is sendfrom a Concentrator to the server, it is the responsibility of the GOS

server to update the GOS Workstation.(k) NETNODE.DLL

This module makes a PC computer act as a GOS Workstation. AGOS system can have several Workstations connected.

(l) DBKERNEL.EXE

This module communicates with the GOS database and providesSAFEDOCK with flight information (schedules dockings)

(m) INTERLOCK.DLL

This module evaluates rules about what aircrafts is allowed to dockon a stand based on the status of adjacent stands.

(n) SCHEDULELINK.DLL

This module will schedule Safedock with flights received from FIDS. Itwill also create Blocks On/Off messages after arrival/departuredockings, which will then be forwarded to FIDS by the LAN module(Extip3Client etc).

(o) EXTIP3.DLL

This module will receive flight information from FIDS. It will also sendBlocks On/Off messages to FIDS. Stand statuses can also bereported to a maintenance system for instance from this module.

(p) GOSFLIGHTDBLINK.DLL

This module is an internal flight database used in the GOS system. All flights are stored in RAM or in a MySql database depending onselected configuration type.



IOM Manual



F I S

FIGURE 1.2 SOFTWARE CONFIGURATIONS




IOM Manual




4. STANDARD FEATURES

4.1 GENERAL

This section describes standard features included in a GOS system.

4.2 DOCKING MONITORING AND CONTROL

4.2.1 General

The primary purpose of the GOS system is Docking Control and Monitoring. At anyGOS subsystem the airport layout with stands and docking systems can be displayedand monitored.

The Docking Control and Monitoring function is fully explained in chapterOPERATIONS of the IOM manual.

The following commands are available:

- Open Stand

- Start of Docking- Activation of a Scheduled Docking

- Park On

- Park Off

4.3 GOS EVENT LOG FILES

4.3.1 General

Event Log files are created once per day, and is used for statistics and themaintenance of the DGS system.

A docking procedure contains several events, which are stored with time stamps, forexample: DGS Ready; Active (aircraft, flight); Docking (aircraft, flight); Parked(aircraft, flight, Reg No).

The name of a log file will be the date of the day, and has the format YYMMDD.log

The files are stored automatically, one per day, and are stored for a configurableperiod of time. Default period is thirty-two days. After that it is automatically deleted.

The Event Logging facility is fully explained in chapter OPERATIONS of the IOMmanual.

4.4 AUTOMATIC UPLOAD OF SAFEDOCK DOCKING LOG FILES

4.4.1 General

Each docking in Safedock generates a docking log. The docking log will automaticallybe dumped to GOS at the end of each docking procedure, where it will be retained for30 days.

4.5 AUTOMATIC UPLOAD OF SAFEDOCK CONFIGURATION FILES

4.5.1 General

To store a backup of each Safedock configuration, the configuration files (centrelineand gate configuration) will automatically be dumped to GOS from Safedock when theconfiguration has been updated in the Safedock.

4.6 SAFEDOCK MAINTENANCE

4.6.1 General

The maintenance tool, Sdconfig, used to configure/upgrade Safedock can be usedfrom a GOS Maintenance computer. For instance, it can be used to performcentralized program upgrade to Safedocks within a site, thereby shortening

maintenance time.



IOM Manual




5. ENHANCED FEATURES (OPTION)

5.1 GENERAL

GOS functions can be enhanced with features such as:

- Redundant GOS servers

- FIS Interface

- TMS Interface

- RIDS Interface

- Support for cameras installed in DGS

- Interlock

- Etc

5.2 REDUNDANT GOS SERVERS

To provide a more reliable GOS system, redundant servers can be used. Seeappendix B to this manual for a detailed description.

5.3 INTERFACE TO EXTERNAL SYSTEMS

5.3.1 FIS Interface

The GOS system can be connected to FIS to exchange flight information.

FIS will provide GOS with arrival and departure flight information and GOS will reportBlock On/Off events to FIS upon successful arrival/departure docking.

5.3.2 TMS Interface

The GOS can be connected to the TMS (Technical Management System) to provideTMS with system statuses for the various GOS and Safedock systems installed on asite.

5.4 STAND IMAGES FROM CAMERA

5.4.1 General

Cameras can be installed with the Docking Systems at the Stands. A separateEthernet LAN connection is required for the communication to the GOS system. A PCcomputer or GOS workstation is used for the presentation of Images from anyStand/Camera. One or several Images can be displayed at a time.

Stand Images can be synchronised with the docking monitoring function of GOS. Forexample: when the Docking Guidance System has captured an approaching aircraft,the transmission of Stand Images could be automatically started and logged, until theaircraft has come to a parked position.

See Appendix C to this manual for a more detailed description.

5.5 INTERLOCK FUNCTION

5.5.1 General

With this feature, Start of docking for a stand can be blocked for operation based onselected aircraft type and current status of adjacent stands.

Upon start of docking, either from GOS or locally from the operator panel, the GOSsystem will evaluate, based on the status of adjacent stands, whether or not dockingshall be allowed.

The interlock evaluation is based on a series of blocking rules, which are configuredfor each stand in GOS.INI. Whenever start of docking is requested, all the rules forthat stand must be evaluated, and if any of them are fulfilled, the docking request isdenied. If GOS is unavailable upon start of docking, Safedock will ask the localoperator for a manual confirmation of the docking procedure. If no rules are specifiedfor the selected stand, the docking will always be allowed.



IOM Manual




Evaluation performance:

(a) A blocking evaluation can be done in the following states (for adjacentstands): Active, Docking, Downgrade, Parked, Parked Last Bags, InterlockTimeout, Interlock Unknown and Request interlock

(b) A blocking evaluation can be done for the following errors: 13, 14, 15, 21, 23and 24 (for other errors evaluation cannot be done (safety issue) - localoperator can confirm the docking procedure)

(c) A blocking evaluation cannot be done in the following statuses: Comm error,Unknown, Emergency stop and Maintenance

For other statuses, a stand is considered as empty, and docking will always beallowed

6. INSTALLATION

6.1 GENERAL

GOS workstations are normally installed on desks. The GOS server could be installed

in a cabinet, if required.

Power lines/outlets and System Earth lines shall be available close to the cabinet andthe PC desktop units.

Normally a LAN connection, 10/100BaseT, shall be available at each GOS station.



IOM Manual

GOS Gate Operating System Chapter 1. System Description: Appendix A


Document: SY-AppA-GosRUH-Topology Date: June 2008 Version: 1.0

CHAPTER 1: APPENDIX A

A GOS SYSTEM TOPOLOGY AND HARDWARE UNITS - EXAMPLE

CONTENTS


1.1 GOS SYSTEM TOPOLOGY (AN EXAMPLE) .................................................. 2

1.2 GOS HARDWARE SUB-UNITS (AN EXAMPLE) ............................................. 3

1.2.1 General ........................................................................................................ 3

1.2.2 GOS Server Hardware Items ..................................................................... 3

1.2.3

GOS Concentrator Items (used i f non- LAN conf iguration) .................. 4

1.2.4 GOS Workstation Hardware Items ........................................................... 4



IOM Manual



1.1 GOS SYSTEM TOPOLOGY (AN EXAMPLE)

System components, specified for the actual airport, and their interconnection areshown below.

Customer’s Ethernet LAN, 10BaseT connections


SAFEDOCK LAN Connections

Maintenance

Operation

Modem Rack(option)

Option: Asynchronouscurrent loop 2-pair lines,connected to SAFEDOCK

Patch cable per modem (15)

10BaseT / Cross-over cable (1)

GOS

Workstation 1

GOSServer

GOSWorkstation 2

Patch cables to horizontalnetwork outlets, 10BaseT / RJ 45

Concentratoro tion

FIGURE 1.1 GOS SYSTEM TOPOLOGY



IOM Manual




1.2 GOS HARDWARE SUB-UNITS (AN EXAMPLE)

1.2.1 General

The GOS system is built up with the following components

(a) GOS Server(b) Concentrator (if no LAN connection to SAFEDOCK)

(c) GOS Workstation for Docking Control

(d) GOS Workstation for DGS Maintenance

1.2.2 GOS Server Hardware Items

Part No Qty Equipment Supplier

N/A 1 Optiplex GX240 1.6 GHz TabletopComputer

Dell

N/A 1 32 MB ATI Rage Ultra video card DellN/A 1 Documentation Optiplex ENGLISH Dell

N/A 1 3.5” Floppy Drive Dell

N/A 1 256MB RAM, Memory Dell

N/A 1 20.0 GB IDE Hard Drive Dell

N/A 1 20x48 Speed IDE CD ROM Reader/Writer Dell

N/A 1 Integrated 10/100 3COM Network card Dell

N/A 1 Keyboard, English Dell

N/A 1 MS PS/2 Mouse Dell

N/A 1 MS Windows 2000 Pro, SP2 ENG CDNTFS file system

Dell

34-1002 1 Extra LAN card 10 Mb Direktronik

N/A 1 Monitor: E771-17” Dell

SW621A-R2 1 Serv Switch (for Monitor, keyboard andmouse)

Black BoxCorp.

RMK 19M 1 Rack Kit for Serv Switch Black BoxCorp.

EHN 151-0005 2 Serv Switch Cable (1,5 meters) Black BoxCorp.

EHN 151-0010 2 Serv Switch Cable (3 meters) Black BoxCorp.

Safeg4603 1 Floor cabinet Rittal

Note: A patch cable, 10BaseT/RJ-45, will be needed on site for the connection ofthe Server to the LAN.



IOM Manual




1.2.3 GOS Concentrator Items (used if non- LAN configuration)


38-000138-0071

00

Wall CabinetCover Plate (accessory to Cabinet)

DirektronikDirektronik

SAFE4603 0 Floor Cabinet Rittal

24-0500 0 Rocket LAN (16 RS-232 COM ports), VS1000 Comtrol

24-0505 Rocket LAN Expansion (16 ports), VS1100(Cable to main unit included)

Comtrol

05-6231 0 Patch cable 1m (cross-over cable, for theconnection between the Concentrator and theServer)

Direktronik

05-6239 0 Patch cable 10m (cross-over cable) Direktronik

RV-1 0 Modem Rack Frame with Power Supply

Mains: 230VAC, 50 Hz

Ritex

R-1 0 Modem R-1 Ritex

590160 0 Modem Cable Safegate

1.2.4 GOS Workstation Hardware Items


N/A 2 Optiplex GX240 1.6 GHz Tabletop Computer Dell

N/A 2 32 MB ATI Rage Ultra video card Dell

N/A 2 Documentation Optiplex ENGLISH DellN/A 2 3.5” Floppy Drive Dell

N/A 2 256MB RAM, Memory Dell

N/A 2 20.0 GB IDE Hard Drive Dell

N/A 2 20x48 Speed IDE CD ROM Dell

N/A 2 Integrated 10/100 3COM Network card Dell

N/A 2 Keyboard, English Dell

N/A 2 MS PS/2 Mouse Dell

N/A 2 MS Windows 2000 Pro, SP2 ENG CDNTFS file system

Dell

N/A 2 Monitor: E991-19” Dell

Note: A patch cable, 10BaseT/RJ-45 connectors, will be needed (length to bespecified according to site conditions) for the connection of the server/workstation tothe LAN. Alternatives may be as follows:

(a) Cat5 Cable, 10metres, grey Part No. 05-6260, Direktronik

(b) Cat5 Cable, 20 metres, grey Part No. 05-6271, Direktronik



IOM Manual

GOS Gate Operating System Chapter 1. System Description: Appendix B


Document: SY-AppB-GosRUH-Redundant Date: June 2008 Version: 1.0

SYSTEM DESCRIPTION: APPENDIX B

REDUNDANT GOS SERVER

CONTENTS


1.

SCOPE .......................................................................................................................... 2

2. TECHNICAL CONCEPT ............................................................................................... 2

2.1 GENERAL ......................................................................................................... 2

3. OPERATION.................................................................................................................. 4

3.1 SYSTEM START UP ........................................................................................ 4

3.1.1 General ........................................................................................................ 4

3.1.2

File Synchronization at Start up ............................................................... 4

3.1.3 Flight Synchronization at Start up ........................................................... 4

3.2

NORMAL SYSTEM OPERATION .................................................................... 4 3.2.1 General ........................................................................................................ 4

3.2.2 Continuous File Update ............................................................................ 4

3.2.3 Continues Flight Update ........................................................................... 5

3.2.4 Connection to External Systems .............................................................. 5

3.2.5 Connection to Internal Systems ............................................................... 5

3.3 SYSTEMS SWAPPING DURING NORMAL OPERATION .............................. 5

3.3.1 General ........................................................................................................ 5

3.3.2 Swap Cr iteria .............................................................................................. 5

3.3.3 File Updates ................................................................................................ 5

3.3.4

Re-connection to External Systems ........................................................ 5

3.4 SYSTEM STATUS DISPLAY ON GOS HMI ..................................................... 5



IOM Manual



1. SCOPE

This document is a functional description of the redundant Central Docking ComputerSystem/GOS, being the gateway between SAFEDOCK systems and external controland monitoring systems with a central location.

2. TECHNICAL CONCEPT

2.1 GENERAL

The Central Docking system consists of two redundant GOS servers. These twoservers will work in parallel. When both computers are running, one of them will bethe Active server and the other one will be the Standby server.

The Active server will handle the communication with all external systems, while theStandby server will be logically disconnected (by software) from external systems.

If the Active server for any reason goes down, the Standby Server will become the

Active server and re-establish connection with external systems.For the two servers, to determine the overall status, Keep-Alive transactions are sent,once per second, in both directions between the Active server and the Standbyserver, using the external network.

Active-to-Standby swap time will depend on IP disconnect and reconnect time of theexternal systems. Disconnect and reconnect time regarding SAFEDOCK units isapproximately 15-60 seconds. Data from SAFEDOCK will be buffered during thistime, as the GOS server gets data by a polling method.

The figure below is a state diagram, illustrating Computer A and Computer B states,being Main, Standby or a Failing units.

Start

StandBy

do/ Exchange Status

do/ Synchronice DB

Main

do/ Exchange Status

do/ Update StandBy DB

Computer A

StandBy

do/ Exchange Status

do/ Synchronice DB

Main

do/ Exchange Status

do/ Update StandBy DB

Computer B

Yield

Fail

Swap

Fail

Yield

Fail

Swap

Fail

GATEWAY STATES




IOM Manual



The figure below is a detailed state diagram of computer A or B.

Start

StandBy

SyncStandby DB

Gateway Status Monitor

do/ Send Status

do/ Receive Status

Init

do/ Deactivate Gateway (Links)

SyncStandby DB


do/ Send Status

do/ Receive Status

Main


do/ Send Status

do/ Receive Status

Init

do/ Activate Gateway (Links)


do/ Send Status

do/ Receive Status

Init

do/ Activate Gateway (Links)

Init

do/ Deactivate Gateway (Links)

No other main[ First time ]

Main found

Main found[ Fi rst time ]

No Main found in random time

SWAP CONDITIONS AND ACTIVITIES




IOM Manual




3. OPERATION

3.1 SYSTEM START UP

3.1.1 GeneralWhen a server computer starts up, it will enter the Standby mode and try to exchangeStatus information with the other server computer. If no Active server is found on thenetwork after a random period of time, the computer will become the Active serverand establish connection with external systems. If an Active server already exists onthe network, the newly started server will enter Standby mode, and a datasynchronization operation between the two servers will be initiated (described below).This is the initial procedure at start up for both computers.

Note: Database synchronization described below only takes place when a databaseis used in the GOS system.

3.1.2 File Synchronization at Start up

When the standby server gets connected to the active server, the standby server willstart to synchronize some of its file directories with corresponding file directories onthe active server. The directories to be synchronized are configurable.

Following files are to be synchronized:

(a) GOS event log file, ”date.log”

These files will be copied from the Active server to the Standby server only ifthe file on the Active server is newer.

(b) Safedock configuration files, ”standname.gte” and “standname.sdc”


(c) Safedock log files, ”standname_date_time.sdl”.


3.1.3 Flight Synchronization at Start up

(a) GOS equipped with SQL Database

Through a replication mechanism the Standby server will be populated withflight data from the Active server.

(b) No SQL database used

When GOS is connected to a FIS system providing GOS with currentarrival/departure flight information prior to docking, all flights sent to GOS aredouble-stored in the Safedock system. Upon start-up the newly ACTIVEserver will collect current flights (arrival and departure) from each Safedock.

3.2 NORMAL SYSTEM OPERATION

3.2.1 General

This is the scenario where both servers are up and running. One server is the Active,and the other one is Standby.

3.2.2 Continuous File Update

During normal operation certain file updates take place between the two servers. The Active server will notify the Standby server about file updates that take place on the Active server. The Standby server will then copy (read) the updated/new files from the Active server.

Following files will be updated:

(a) GOS event log file

(b) Safedock Log



IOM Manual




(c) Safedock configuration files (.gte and .sdc files)

3.2.3 Continues Flight Update

(a) GOS equipped wi th SQL Database

During normal operation the database on the Standby server will be updatedby the Active server.

(b) No SQL database used

Each flight sent to GOS for a specific stand double-stored in the Safedocksystem. Limitation: Unsent Blocks On/Off records are only buffered in RAMon the Active server until successfully sent to FIS. Thus, if the Active serverbreaks down buffered messages will be lost.

3.2.4 Connection to External Systems

The Active server will establish connection to external systems. External systems areSafedocks and FIS. The Standby server will be disconnected from all externalsystems.

3.2.5 Connection to Internal SystemsInternal System means Workstations, built on the GOS concept. These are allconnected to both the Active and the Standby Central Computer. Only the activeserver is sending HMI information. The workstation only sends commands to theactive server.

3.3 SYSTEMS SWAPPING DURING NORMAL OPERATION

3.3.1 General

This is the scenario where the Standby server no longer detects the Active server onthe network, or in case that both servers detect each other as being the Active server.

3.3.2 Swap Criteria

(a) If the Standby server doesn’t receive any Keep-Alive transactions within fiveseconds from the Active server, the Standby server will switch state andbecome Active. This may have the following reasons:

(i) Computer break-down or Power failure

(ii) LAN Adapter break-down

(iii) One or several software items are not running properly. However theNTP client cannot be tested this way.

(b) Both servers detect each other as being Active: The one with the fewestconnections to Safedocks will yield and become Standby.

3.3.3 File Updates

Servers will perform the same file synchronization as within a system start up,described above.

3.3.4 Re-connection to External Systems

When a system swap has occurred, and both servers have found its roles (Active andStandby), both servers will perform the same action as within normal systemoperation. The connection to each external system will be performed according to therespective interface specification.

Any Blocks On/Off data sent to GOS during the time neither of the two servers areconnected to the Safedock systems will be lost.

3.4 SYSTEM STATUS DISPLAY ON GOS HMI

The current system status for both servers can optionally be displayed in the GOSmonitor software GOSHMI during operation.



IOM Manual




When configured on Maintenance Workstation and/or servers, there will be two statusbuttons visible on the screen representing the Active and the Standby server. In caseof a system swap or a hardware failure, the status buttons will start to flash, and willdo so until acknowledged by the user.

The Server Status Display is described in chapter 3. OPERATION.



IOM Manual

GOS Gate Operating System Chapter 1. System Description: Appendix C


Document: SY-AppC-GosRUH-Camera Date: June 2008 Version: 1.0

SYSTEM DESCRIPTION: APPENDIX C

CAMERA INTEGRATION

CONTENTS


1.

INTRODUCTION ........................................................................................................... 2

1.1 GENERAL ......................................................................................................... 2

2. EXTENDED FUNCTIONALITY OF GOS ...................................................................... 3

2.1 PURPOSES OF USING GOS........................................................................... 3

2.2 VIEWING AND LOGGING STAND IMAGES USING CAMERAS .................... 5

2.2.1 General ........................................................................................................ 5

2.2.2 Camera ........................................................................................................ 5

2.2.3 Communication .......................................................................................... 5

2.2.4 GOS Monitor screen .................................................................................. 5

2.2.5

Image Logging ........................................................................................... 5

3. SYSTEM ARCHITECTURE ........................................................................................... 6

3.1 GENERAL ......................................................................................................... 6

3.2 SYSTEM SUB-UNITS ....................................................................................... 6

3.2.1 General ........................................................................................................ 6

3.2.2

Camera Hardware ...................................................................................... 6

3.3 GOS TOPOLOGY ............................................................................................. 6

3.3.1 GOS Sub-Uni ts Interconnect ion ............................................................... 6

4. CONFIGURATION ........................................................................................................ 8

4.1

CONFIGURING THE CAMERA ........................................................................ 8

4.2 CAMERA SPECIFICATION .............................................................................. 8



IOM Manual




1. INTRODUCTION

1.1 GENERAL

The Central Docking Control System or Gate Operating System/GOS can be

upgraded with Cameras for Stand Surveillance.This document describes how to upgrade the infrastructure, LAN, needed and how tointegrate the Stand Surveillance system, the Cameras, and the associated software inthe GOS system.



IOM Manual




2. EXTENDED FUNCTIONALITY OF GOS

2.1 PURPOSES OF USING GOS

Main purposes of using GOS are as earlier and according to the tables below,

updated with the Stand Surveillance Feature, highlighted below.General Purposes Realisation

- Central Stand Monitoring The GOS Monitor

- Central DGS Error Log, SystemEvent Log and Docking Log

-

The GOS Logging Feature

- Central Maintenance of SAFEDOCK The Stand Configuration Utility and theStand Config PrintOut Utility

- Status Report to a CentralMaintenance System

Interface GOS – CMS (option)

- Airfield Lightning Control

- Push-back info to Ground Radar



- Stand Surveillance The Stand Images Viewing andLogging Feature, using digitalCameras



IOM Manual




At arrivals the following functions are realised with the GOS system:

Functions at Arrivals Realisation

- Capture of Aircraft Type to bedocked

Data Entry at GOS Workstation


- Check of Aircraft Type to be dockedto a specified Stand


- Capture of Flight No. Data Entry at GOS Workstation (option)

Data gained from a FIS connection

- Capture of Registration/Tail No. Data Entry at GOS Workstation (option)

Date gained from a FIS connection*

- Initiation of the Docking Procedure Entry of Command (aircraft type) fromGOS Workstation

- Capture of failures The Stand Images Viewing andLogging Feature, using digital

Cameras - Capture of Blocks On Time

-

GOS – interface to FIS

- Display of flight information

-

GOS – interface to FIS (option)

- Managing the Stand event PARKEDafter an aircraft ground movements

Entry of Command from GOSWorkstation.

At departures the following functions are realised with the GOS system:

Functions at Departures Realisation- Capture of Flight No. Data Entry at GOS Workstation


- Capture of Registration/Tail No. Data Entry at GOS Workstation


- Capture of Blocks Off Time GOS – interface to FIS

- Display of flight information GOS – interface to FIS

- Managing the Stand event PARKOFF after an aircraft ground

movements

Entry of Command from GOSWorkstation

*Note: ‘FIS connection’ means a FIS workstation or, optionally, a data interface FIS-GOS.



IOM Manual




2.2 VIEWING AND LOGGING STAND IMAGES USING CAMERAS

2.2.1 General

Optionally, cameras can be installed with the Docking Systems at the Stands. Aseparate Ethernet LAN connection is required for the communication to the GOSsystem. For maximum throughput 100BaseFX is needed.

2.2.2 Camera

A digital camera will be used, sending stand area images, one per second (anexample) to one or several PC-monitors (or GOS Workstations) connected to anetwork. The camera will work as a ‘Stand image server’, using TCP/IPcommunication to the Monitor PCs and GOS, the Camera clients.

Resolution is 320 x 240 pixels, normally, but can be set to 640 x 480 as well.

Stand Image resolution and frequency depends on the allowed network loading anddisc storage capacity.

2.2.3 Communication

The camera system will be connected to a 10-100 Mbps Ethernet LAN using an RJ-45 connector. (CAT 5 cable from camera to hub, max 90 metre, is not included in thestandard delivery of materiel). Load on the network would be approximately 10 kBdata per image and client. For further information refer to the section ‘CameraSpecification’ below.

2.2.4 GOS Monitor screen

A PC computer or GOS workstation is used for the presentation of Images from anyStand/Camera. One or several Images can be displayed at the same time (max 4pictures can be displayed simultaneously).

2.2.5 Image Logging

Stand Images can be synchronised with the docking monitoring function of GOS. Forexample: when the Docking Guidance System has captured an approaching aircraft,

the transmission of Stand Images could be automatically started and logged, until theaircraft has come to a parked position.

Depending on disc space available and image back-up frequency Stand Images couldbe retrieved from docking events more or less back in time.



IOM Manual




3. SYSTEM ARCHITECTURE

3.1 GENERAL

All SAFEDOCK status transactions are distributed around the GOS system nodes,

over an Ethernet LAN, and at the same time all subsystems have the total informationabout status of all SAFEDOCK systems at the terminals and the remote Stands.

Some of the Stands may be equipped with digital Cameras, which are connected to aLAN, sending stand images to the GOS system. These images can be monitored, andare also automatically logged during a docking sequence until this is completed.

3.2 SYSTEM SUB-UNITS

3.2.1 General

Main components of GOS systems are PC computers. Several workstations may beconnected to a LAN for multi-client usage. Cameras are also connected to a LAN ateach Stand, and the Stand area can be viewed from any GOS workstation.

The physical communication media, preferably used, is Ethernet 10-100 Mz with theTCP/IP protocol.

3.2.2 Camera Hardware

The following hardware is used.

Item Qty Materials Notes

1 Camera Axis 211 Axis

2 Camera housing HPV42K0A017 Axnet AB

3.3 GOS TOPOLOGY

3.3.1 GOS Sub-Units Interconnection

The picture below illustrates a Docking system updated with Cameras, connected toan Ethernet LAN. In this case the docking systems have previously been installedusing 2-pair communication lines, handled by GOS Concentrators and short haulmodems.

When a LAN is available from the start, also the docking systems are connected tothis according to the 10BaseT specification.



IOM Manual



An example of Sub-Units and their interconnections are shown below.

12 SDKs

Fibre Hub

12 Cameras*

10BaseT (max 90 metres)

GOS Workstation


Fibre Hub GOS Server

<128 Stands/ SDKs

Concentrator

16 Stands/SDKs

Concentrator

32 Stands/Loop DGS

Fibre to AUI Converter/Transceiver

Hub (max 90 metres) 16 Cameras*

Fibre 10BaseT

Concentrator 16 SDKs

(Ethernet COM)

Units previously installed

*Note: A central location for the Hub is needed, as max line length of CAT 5 cable is 90 meters.

‘Ethernet COM’ means 16 COM ports connected to the Ehernet LAN, which can be expanded to 64ports.



IOM Manual




4. CONFIGURATION

4.1 CONFIGURING THE CAMERA

Refer to the DGS manual kit for a description of how to configure the camera in DGS.

Refer to the GOS manual kit for a description of how to configure GOS for camera.

4.2 CAMERA SPECIFICATION

Refer to current documentation for “AXIS 211/211A Network Camera” from AxisCommunication AB.

For more information, go to www.axis.com.

http://www.axis.com/

http://www.axis.com/



IOM Manual

GOS Gate Operating System Chapter 2. Installation


Document: IN-GosRUH-Installation Date: June 2008 Version: 1.0

CHAPTER 2

INSTALLATION

CONTENTS


1.

SCOPE .......................................................................................................................... 3

1.1 GENERAL ......................................................................................................... 3

1.2 REPORTING SYSTEM SET UP ......... ERROR! BOOKMARK NOT DEFINED.

2. INSTALLING WINDOWS 2000-PRO/XP-PRO/2003-SERVER .................................... 4

2.1 GENERAL ......................................................................................................... 4

2.2 CONFIGURATION SETTINGS ......................................................................... 4

2.2.1 Computer Name, Workgroup, and Organization: ................................... 4

2.2.2 GOS Installation Types.............................................................................. 4

2.2.3 Network Card Setup .................................................................................. 5

2.2.4 Hard Disk Setup ......................................................................................... 5

2.2.5 Users and Adminis trator Password Setup ............................................. 5

3.

GOS CONFIGURATION ............................................................................................... 6

4. GOS APPLICATION SOFTWARE ................................................................................ 7

4.1 SOFTWARE PACKAGE STRUCTURE ............................................................ 7

4.2 GOS DATABASE SETUP (OPTION) ............................................................... 7

4.2.1 General ........................................................................................................ 7

4.2.2 Installing MYSQL Database ...................................................................... 7

4.2.3 Installing MySql Administration Too ls .................................................... 8

4.2.4

Creating the Database ............................................................................... 8

4.3 GOS SOFTWARE SETUP .............................................................................. 11

4.3.1 DB Express Setup .................................................................................... 11

4.3.2 Standard GOS Software Setup ............................................................... 11

4.3.3 Non-Standard Interface Software ........................................................... 11

4.3.4 GOS Access Manager Setup .................................................................. 11

4.3.5 SDK Maintenance Software Setup ......................................................... 11

4.4 SHARED DIRECTORIES ............................................................................... 12

4.5 DEVICE DRIVER INSTALLATION FOR DEVICEMASTER-RTS .................. 12

4.5.1

Hardware Installation .............................................................................. 12

4.5.2

Software Driver Installat ion .................................................................... 12

4.6

COM-PORT TEST .......................................................................................... 13

4.7

GOS KERNEL AS A SERVICE ....................................................................... 13

4.7.1 General ...................................................................................................... 13

4.7.2 Conf iguring the GOS Kernel Service ..................................................... 13

4.7.3 Verifying the GOS Service Set-up .......................................................... 13

4.8 CAMERA SOFTWARE ................................................................................... 13

4.8.1

General ...................................................................................................... 13

4.8.2 Installing Camera Software .................................................................... 14

4.8.3 Conf iguring Camera in Safedock ........................................................... 14

4.9 USER RIGHTS AND PASSWORD ADMINISTRATION ................................. 15

4.9.1 General ...................................................................................................... 15



IOM Manual




4.9.2

Creating Windows Users ........................................................................ 15

4.9.3 Creating GOSHMI Users .......................................................................... 15

4.10 CONFIGURING AUTO LOGON ..................................................................... 16

4.11 TIME SYNCHRONIZATION OF COMPUTERS ............................................. 16

4.11.1

General ...................................................................................................... 16

4.11.2 Conf iguring the NTP Client ..................................................................... 16

5. BASIC VERIFICATION OF SOFTWARE CONFIGURATION .................................... 17

5.1 GENERAL ....................................................................................................... 17

5.2 VERIFICATION OF GOSKRNL SOFTWARE................................................. 17

5.2.1 Verify ing the GOS.INI file Configuration................................................ 17

5.2.2

Verifying the Gos Kernel Service User Set-up ...................................... 17

5.2.3 Verifying the Automatic Service Start-up .............................................. 17

5.2.4 Verify ing File Synchron ization Betw een Servers ................................. 17

5.3 VERIFICATION OF DATABASE SOFTWARE ............................................... 18

5.3.1

GOS Database Connection Test ............................................................ 18

5.4 VERIFICATION OF SAFEDOCK CONFIGURATION SOFTWARE ............... 18

5.4.1 Connection Test ....................................................................................... 18

APPENDICES:

System Configuration Appendix A



IOM Manual




1. SCOPE

1.1 GENERAL

This manual is an instruction that shall be used when system software has to be

reinstalled again i.e. after the remedy of a hardware or software failure.

The following installation instructions are included herein:

(a) OS related parameters of GOS Server and Workstations

(b) Configuration of HMI

(c) Installation of GOS application software

(d) Time Synchronization of Computers

(e) User Rights and Password Administration

It is assumed that maintenance staff is familiar with MS Windows. Regardinginstallation of the operating system only configuration data will be given in thisinstruction.

For the installation of GOS specific components such as GOS software, creation ofGOS users and time synchronization of computers, an installation program calledGosinstall.exe is provided.

The installation program together with other GOS software is provided on a CD ROM.

Note: It is recommended to perform the installation according to the order describedin the manual.



IOM Manual




2. INSTALLING WINDOWS 2000-PRO/XP-PRO/2003-SERVER

2.1 GENERAL

Each GOS computer delivered by Safegate will come with an installation CD as

provided by the computer equipment manufacturer. This CD-ROM shall be usedwhenever the Windows Operating System (or Windows 2000-Pro/XP-Pro/2003-Server OS) needs to be re-installed. It is recommended not to make any specialWindows configurations that may interfere with the GOS operations. It is alsorecommended to NOT install any added features that may be available on the CD-ROM that will not be used on the GOS computer.

Only the configuration settings will be described herein.

2.2 CONFIGURATION SETTINGS

2.2.1 Computer Name, Workgroup, and Organization:

The GOS software installation does not require any special names of the GOS

computers. Instead, it relies on the installer to determine the GOS installation type forthe target computer for GOS operations as desired for that computer. If there are nocomputer names given to the GOS-Server and/or GOS-Workstations, the list belowprovides some suggested names.

Name and Organization:

Name: Same as computer name (see below)

Organization: ‘Name of the airport’

Computer and Workgroup name (recommended names):

Computer Names: Suggested computer names are shown below (yoursystem administrator can supply alternate names).

GOSSERVER1 For main GOS-Server

GOSSERVER2 For redundant GOS-Server (ifused)

GOSWS1,GOSWS2,

GOSWS3 etc

For GOS-Workstations

GOSMAINT

Workgroup Name: If none are provided by your system administrator, it isrecommended to use “GOS” as the Workgroup Name.

2.2.2 GOS Installation Types

The GOS installation types will be listed in the computer type selection screen of the

GOS software installation procedure. The installer should select the correct type asdetermined for the target computer the software will be installed on. In general, thesoftware is common for all GOS installation types although the configuration changesdepending on the GOS operations as desired for that computer. The list belowprovides some likely GOS installation types:

GOS_Server1: Main GOS-Server.

GOS_Server2: Alternate/redundant GOS-Server (if supplied).

MaintDock: GOS-Workstation, allows view of GOS/DGS status,activation of aircraft docking, and maintenance.

GOS_MaintOnly: GOS-Workstation, allows view of GOS/DGS statusand maintenance (no aircraft docking).

GOS_MonitorDock: GOS-Workstation, allows view of GOS/DGS status

and activation of aircraft docking.

GOS_MonitorOnly: GOS-Workstation, allows view of GOS/DGS status.



IOM Manual




2.2.3 Network Card Setup

Any GOS computer will have at least one network card or built-in Ethernet hardware(with RJ45-port). Often, in the GOS-Server, it is recommended to have two Ethernetconnections: one for the GOS-network to all GOS-Workstations and Concentrator

units and another for the external connections to FIS and/or NTP. Of course thenetwork setup will vary per site based upon customer preference, networkconfigurations, and/or network security.

Below are suggested use of the network card use in a typical GOS system:

Network Card 1 (GOS computers):

Use for GOS/Safedock LAN

Network Card 2 (FIS LAN):

Use for external connections such as FIS, NTP etc

Note: IP addresses and other network details may also be assigned and

configured by the network manager or system administrator. 2.2.4 Hard Disk Setup

The NTFS file-system shall be used on all GOS computers to allow properoperation and file-sharing restrictions.

2.2.5 Users and Administrator Password Setup

See ‘User rights and Password Administration’ section in this document.



IOM Manual




3. GOS CONFIGURATION

Each GOS Computer is executing the same GOS application software, but hasdifferent kind of configurations, depending on its specific functionality in the GOSsystem.

The GOS.INI file determines the configuration, and especially the HMI layout. Theconfiguration procedure is described in Appendix A.



IOM Manual




4. GOS APPLICATION SOFTWARE

4.1 SOFTWARE PACKAGE STRUCTURE

Application software package for the whole GOS system is delivered on a CD ROM,

and must be installed on each GOS computer.

Each computer has its own directory with its unique software on the CD ROM (only ifunique software is used). The CD ROM also contains a COMMON directory wheresoftware files common to all PCs in the GOS system resides.

The GOS software is built around items, called GosKrnl and GOSHMI, which arecommon to all subsystems, and one unique configuration file for each subsystem,called GOS.INI. GosKrnl also uses a number of modules (DLLs and EXE files). TheGOS.INI file on each PC specifies the modules that will be used on each PC.

Also other files/drivers essential to the GOS system are included in the directories.

Softw are package Name

(a) GOS Kernel: GosKrnl.exe

(b) GOS Monitor/HMI: GosMmi.exe(c) Configuration File for each PC: Gos.INI

(d) GOS modules for each PC DLLs and EXE files

(e) Driver files essential to GOS

4.2 GOS DATABASE SETUP (OPTION)

4.2.1 General

The GOS server/servers have an SQL database installed, which is used to store flightinformation received from a FIS system. Setting up the GOS database includes thefollowing steps:

(i) Installing MySql database

(ii) Installing MySql Administarator

(iii) Installing MySql Query Browser

(iv) Creating the GOS database

4.2.2 Installing MYSQL Database

Log on to Windows as user ‘Administrator’ on the server (the database shall only beinstalled on the server/servers).

Start Gosinstall.exe and select the ‘Install MySql Database’ option and press START.

The following settings shall be made throughout the installation:

(i) Setup Type: select ‘Typical’

(ii) MySql Sign-up: select ‘Skip Sign-Up’

(iii) Choose ‘Configure the MySql Server now’(iv) Select ‘Standard configuration’

(v) Select ‘Install As Windows Service and accept default service name

(vi) Select ‘Launch the MySql Server automatically

(vii) Select ‘Include Bin Directory in Windows PATH

(viii) Select ‘Modify Security Settings’ and type in the password for the rootuser – use password <manager>

(ix) Uncheck ‘Enable root access from remote machines’

(x) Uncheck ‘Create An Anonymous Account’

(xi) Press Finish to complete the installation



IOM Manual



4.2.3 Installing MySql Adminis tration Tools

Together with the MySql database a set of user tools are supplied that can be usedwhen working with the database. Refer to the MySql documentation for a completedescription of how to use the tools.

Start Gosinstall.exe and select the ‘Install MySql Administration Tools’ option, pressSTART and follow screen instructions.

4.2.4 Creating the Database

Creating a SQL connection to the database

The GOS application needs an SQL connection to be able to communicate with thedatabase.

Perform the following to create the database:

(a) Start ‘MySql Query Browser’ from the Programs\MySQL menu. The followingdialog will appear. If this is the first time the program is being run proceed toitem b to create a SQL connection, otherwise select, from the ‘StoredConnection’ drop down menu, the connection ‘Local host’ and proceed to iteme.




IOM Manual



(b) To create the SQL connection, press the … button in previous dialog and thefollowing dialog will appear.

(c) Press ‘Add new Connection’ and type in the following information in the editfields under the ‘Connection Parameters’ tab:

(i) Connection: Local host

(ii) Username: root

(iii) Password: manager

(iv) Hostname: localhost

(v) Port: accept default

(vi) Type: accept default

(vii) Schema: GOSDB

(d) Press ‘Apply’ to create the new connection and ‘Close’ to exit theconfiguration wizard and continue with the log on procedure using the newlycreated connection.

(e) Type in the password (manager) in the password’s edit field and press ‘OK’ tolog on to the database. If requested, accept to create GOSDB schema.

(f) From the File menu, select ‘Open Script’ and browse to the script file locatedon the installation CD in directory Software\Common\Sqlscript\<????.sql>).Select the script and press Open to load the script into the editor.

(g) Press the ‘Execute’ button to run the script. If no error message appears inthe dialog’s footer, it’s an indication that it went OK.

Generating the Database:

To create the database and its tables, run the file MySqlCreateGosDb.bat usingWindows Explorer. The file can be located in the directoryCDROM:\Software\Common\Sqlscript. Note: running this file might take some time(10 – 20 seconds). The result will be displayed on screen once the operation has

completed.




IOM Manual




Setting up Replication (if redundant GOS servers are used with MySql):

If the server shall use MySql replication, the following steps must be performed:

1) Using notepad.exe, open the file my.ini in the MySQL installation directory (i.ec:\Program Files\MySQL\MySQL Server 5.0).

2) Find the section [mysqld] (Note: do not confuse with the section named [mysql])and insert the following lines directly after the [msyqld]-header:

#enable bin-log

log-bin=mysql-bin

server-id=1

relay-log=relay-bin

#don’t start slave threads

skip-slave-start

expire_logs_days=20

master-connect-retry=30

3) If installing server A, set the server-id value to 1, as in the example above. Ifinstalling server B, the value must be set to 2

4) Save and close the file.

5) Restart the server.



IOM Manual




4.3 GOS SOFTWARE SETUP

4.3.1 DB Express Setup

The GOS application uses a third-party component to communicate with the

database.Install the software as follows:

(i) Start Gosinstall.exe

(ii) Select Install Core Labs MySql Driver

(iii) Press START

(iv) Follow on-screen instructions and accept default settings during theinstallation.

4.3.2 Standard GOS Software Setup

Log on to Windows as an Administrator.

If old GOS software already exists it has to be shut down before any new softwarecan be copied. Perform following on each GOS computer:

(a) Shut down the GOSMMI application by pressing ‘Alt+F4’ and confirm theaction. The GosKrnl service will be automatically shut down by the installationprogram.

(b) Install software as follows:

(i) Start the program Gosinstall.exe

(ii) Select Install GOS Software

(iii) From the drop down menu, select desired computer to installsoftware for.

(iv) Press START.

4.3.3 Non-Standard Interface Software

Whenever GOS is interfacing to an external system using interface software otherthan Safegate standard, the installation program will be setup to allow installation ofthe required software as follows:


(ii) Select ‘Install <name of ifc> Software

(iii) Press START.

(iv) Follow on-screen instructions and accept default settings during theinstallation.

4.3.4 GOS Access Manager Setup

Whenever GOS HMI uses centralized access handling (log on to GOSHMI required toget access to the system) the tool GosAccessManager.exe is used when creating

system users.Install the software as follows:


(ii) Select Install GOS Access Manager Software

(iii) Press START

4.3.5 SDK Maintenance Software Setup

Safedock maintenance software can be installed in the GOS system. It isrecommended that maintenance software is only installed on a separate GOSMaintenance computer specifically dedicated for Safedock maintenance.

Install the software as follows:


(ii) Select Install SDK Maintenance Software

(iii) Press START



IOM Manual




4.4 SHARED DIRECTORIES

Directories that shall be shared will become shared automatically when the GOSsoftware is installed. The directories to be shared are defined in GOSINSTALL.INI.

Note: If redundant servers are used, the user running the Goskrnl service (normally

the Administrator) must have full rights to the ‘GosShared’ share (location: <Gos App.Dir>\GosShared. Refer to the Windows operating system for a description of how toassign rights to a network share.

4.5 DEVICE DRIVER INSTALLATION FOR DEVICEMASTER-RTS

The GOS-Server establishes communication to each DGS via DeviceMasters-RTS(LAN to Serial Communication device otherwise known generically as the GOSConcentrator Unit), which is connected to a LAN. Each device is equipped with 1, 4,8, 16 or 32 serial ports each configurable for RS232, RS485, or RS422communications. The project can have any combination of these devices or individualport configuration. However, the individual port configuration MUST match that asrequired for the serial communication signaling to the DGS

4.5.1 Hardware InstallationEach device is connected to a local network switch or router via Ethernet patch-cableon the DeviceMaster-RTS Ethernet-port labeled “UP”. Alternately, a DeviceMaster-RTS unit can be connected directly to the GOS-Server or a laptop computer to theEthernet-port labeled “DOWN” for troubleshooting and/or configuration of the device(note that the device driver must be installed first).

4.5.2 Software Driver Installation

Details of the DeviceMaster-RTS software installation are found in the documentmanual “RTS_Guide.pdf”, located in the “DeviceMaster-RTS” folder on the GOSSoftware Installation CD-ROM. The document describes how to install the devicedrivers and configure the DeviceMaster-RTS devices to assign its ports as standardWindows COM-ports. Refer to section “NS-Link Installation and Configuration”,

“Installing the NS-Link Device Driver”, and “Adding Devices After Initial Installation”. Adobe Acrobat Reader can be found in the AdobeReader directory on the CD-ROM(or can be downloaded from the internet by searching for “Adobe Acrobat Readerdownload” and locating the Adobe website).

General Configuration Settings:

Below settings are done in the Windows “Device Manager” under the “Multi-port serialadapters” by double-clicking the device to configure.

1. Configure starting COM PORT to be 5 for the first serial HUB. Other HUBsshall start at next available port (COM1 through COM4 should be excludedfrom these setups).

2. When the GOS-Server and the DeviceMaster are on the same networksegment, it is recommended to configure the DeviceMaster-RTS to use MAC-addressing for communications between it and the GOS-Server. When theGOS server and the DeviceMaster reside on different network segments, theunit must be setup to use TCP-IP addressing. The latter also applies whentwo or more network cards are used in the server.

3. KeepAlive Timeout Period: 15



IOM Manual




4.6 COM-PORT TEST

Every COM port can be tested with a ‘Loop Back’ test. A loop back plug shall beconnected to the target port to be tested at the DeviceMaster-RTS unit (typicallylocated in a remote telecom room). Testing a COM-port is done using the“Wcom32.exe” program provided with the “Comtrol utilities”.

Testing a COM-port is as follows:

(a) Place the loop back plug on chosen DeviceMaster-RTS port.

(b) Open the ”Test Terminal” (access via “Start/All Programs/ Comtrol/ Utilities/Test Terminal (Wcom2)”)

(c) Select target COM-port from the “File/ Open” menu (one assigned to a DGS).

(d) Test a RS232-port via the menu selection “Port/ Loopback Test”. The resultof the test will be shown on the screen

(e) Test a RS422-port via the menu selection “Port/ Send and Receive TestData” (sends a repetitive character pattern from A-Z as “A”, “AB”, “ABC”, etc.).If the port is OK, the data stream will be shown on the screen as sent.

(f) Close the com port.

4.7 GOS KERNEL AS A SERVICE

4.7.1 General

The GOS kernel, called GosKrnl.exe, shall be executed as a service in all GOS substations, i.e. server and the workstation.

The installation program installs the GOS Kernel service automatically when thesoftware is installed.

4.7.2 Configuring the GOS Kernel Service

If configuring a GOS server and redundant servers are being used, the service mustbe configured to be started by the local Administrator and not the Local Systemaccount, which is default (the servers log on to each other and this cannot beaccomplished if the service is configured to be started by the Local System account).

Configuration can be done as follows:

(i) Enter Control Panel

(ii) Double click the ‘Administrative Tools’ icon

(iii) Double click the ‘services’ icon

(iv) Double click on ‘GosKrnl’ (ignore any error messages

(v) Click the ‘Log On’ tab

(vi) Choose ‘This account’

(vii) Press ‘Browse’, select the ‘Administrator’ and press ‘OK’

(viii) Type in the current password and confirm it.(ix) Press ‘OK’ and exit.

Note: above must also be done whenever the password for the Administrator accountis being changed, otherwise the service will fail to start at next restart.

4.7.3 Verifying the GOS Service Set-up

See the chapter where software verification is described.

4.8 CAMERA SOFTWARE

4.8.1 General

Before any camera features can be used on a GOS computer, an Active X

Component must be installed.



IOM Manual




4.8.2 Install ing Camera Software

To install the component; start Gosinstall.exe and select the ‘Install AXIS CameraControl’ option and press START. Follow screen instructions and accept defaultsettings.

4.8.3 Configuring Camera in SafedockSee the Safedock manual kit for a description on how to configure the camera.



IOM Manual




4.9 USER RIGHTS AND PASSWORD ADMINISTRATION

4.9.1 General

Following is a table describing which users and passwords to be created in the

system and on which computers.The installation program will be used to create the users except the ‘administrator’,which is automatically created during the installation of Windows.

Computer:

User Name:

Password:

administrator

manager

gosuser

gosuser

dgsmaint

dgsmaint

GOS_SERVER1: X X X

GOS_SERVER2: X X X

GOSWS_MONITOR: X X X

GOSWS_MONITORDOCK: X X X

The user “administrator” is automatically created on every GOS computer whenWindows is installed.

Maintenance work on the GOS system concerning reinstallation of network card,rocket port card, Windows and GOS software etc. shall be carried out by the Administrator.

The user “gosuser” will have the possibility to run the GOS-application (Monitoring orDocking Control and Monitoring) from the Workstation/Workstations.

The user “dgsmaint” will have the possibility to perform central maintenance on eachSafedock system through GOS.

Note: To increase system reliability, do not configure Auto Logon on GOS-Servercomputers.

4.9.2 Creating Windows Users

The necessary users for the GOS system can be created with the installationprogram. See above table. The installation program will read the user configuration forthe PC from the file “GosInstall.INI”. The specified user will then be created, and thenecessary rights will be set on the configured directories. During the installationprocedure, a series of batch files are run during the installation process. In case ofany error during the installation the batch files will halt, and the user can study theoutput messages on the screen.

To Create Users:

(i) Start Gosinstall.exe from the CD ROM

(ii) Select ‘Setup users’

(iii) Press Start

(iv) Select the computer to create users for. The program will createusers, set user rights and display created users once finished.

Note: If redundant servers are used, the user running the Goskrnl service (normallythe Administrator) must have full rights to the ‘GosShared’ share (location: <Gos App.Dir>\GosShared. Refer to the Windows operating system for a description of how toassign rights to a network share.

4.9.3 Creating GOSHMI Users

A set of application users, controlling the user access to the GOS system, can becreated using the GosAccessManager tool. Refer to the GosAccessManagerdocumentation for a detailed description of how to use this tool.



IOM Manual




4.10 CONFIGURING AUTO LOGON

Auto Logon can be configured on Workstations if desired. The installation programcan be used to configure Auto Logon.

Note: To increase system reliability, do not configure Auto Logon on GOS server

computers.

4.11 TIME SYNCHRONIZATION OF COMPUTERS

4.11.1 General

The real time clock on each PC will be synchronized through the use of Windows2000 built-in time synchronization system called Windows Time Service.

The GOS computers will synchronize its time against the Airport master clock if oneexists.

4.11.2 Configuring the NTP Client

(i) Start Gosinstall.exe from CD ROM

(ii) Select Setup Windows Time Service, and press START

(iii) Stop the service by pressing STOP SERVICE (might take a while)

(iv) Select the Client option.

(v) Enter DNS name or IP address of the server/servers from which tosync.

(vi) Press APPLY to enter the information into the registry.

(vii) Start the service again by pressing START SERVICE (might take awhile), and finish by pressing EXIT.

The time synchronization can be verified by changing the system time on thecomputer, and then restart the PC. The system time shall be synchronized to one ofthe synchronization sources after restart.

Note: Other NTP options will not work with Windows XP and 2003 Server OS.



IOM Manual




5. BASIC VERIFICATION OF SOFTWARE CONFIGURATION

5.1 GENERAL

The verification process described here is not comprehensive, but will serve as an

overall installation check for each individual GOS computer.

5.2 VERIFICATION OF GOSKRNL SOFTWARE

The configuration of the GOS software shall be verified in several steps. Starting theapplication in different ways does this.

5.2.1 Verifying the GOS.INI file Configuration

If changes have been made to the GOS.INI file or starting the application for the firsttime, it is recommended to start the GosKrnl.exe program in a non-service mode. Anyserious error to the configuration will cause a dialog box to pop up with an errormessage being displayed.

Errors captured here can for example be missing files in the program directory,

allocation of non-existing communication ports, erroneous aircraft configuration etc.When there are no dialog boxes being displayed, it’s a good indication that theconfiguration is OK.

5.2.2 Verifying the Gos Kernel Service User Set-up

To verify that the user configured to start the service is able to do so, the service canbe manually started from the service panel. If the service starts without an errormessage the configuration is OK.

5.2.3 Verifying the Automatic Service Start-up

Since GosKernel is running as a service, it shall start up automatically whenever thePC is rebooted. To verify this, reboot PC, log on to Windows and start the GOSMMIapplication. If GOSMMI starts up without immediate shut-down or closing, it indicates

that the GOS-Kernel has started.The GOSMMI application can be started as follows:

Start the GOS Monitor application program, by selecting “GosMMI.exe” in theC:\GOS” folder accessed using ‘Windows Explorer’ or via shortcut-link on theWindows Desktop if found. The GOS MMI will show a screen layout of the airportwhere the DGS gates are located along with their status (if all is configured andoperating properly).

5.2.4 Verifying File Synchronization Between Servers

The GOS servers will synchronize configuration files such as docking logs andSafedock configuration files during operation. The Standby server will be notified ofany file updates taking place on the Active server and automatically copy them toitself. Do as follows to verify that synchronization works.

(i) Stop Standby server and remove the files in folder <Gos App.Directory>\GosShared.

(ii) Start the Goskrnl service on the Standby server.

(iii) Verify that files are copied from the Active server. Note: it might take about 20seconds before file synchronisation starts.

Possible causes for failure:

(i) Possibly incorrect IP-Address assignment between the servers – CheckGOS.INI.

(ii) GosKrnl service is being run by the Windows System user – set it up to berun by the Administrator or equal user.

(iii) GosKrnl service user does not have full access rights to the network share

‘GosShared’ – grant user full access.



IOM Manual




5.3 VERIFICATION OF DATABASE SOFTWARE

5.3.1 GOS Database Connection Test

To verify that GOS can access the Database an arriving flight can be inserted into thedatabase. Use the FIS system or a FIS simulator to insert a new arriving flight into the

database for a known stand. Use current time for STA and ETA.Within a minute the stand shall become scheduled with the newly inserted flight. Thisverifies that GOS can connect to the database and process flights.

5.4 VERIFICATION OF SAFEDOCK CONFIGURATION SOFTWARE

5.4.1 Connection Test

To verify that the “Stand Configuration Software” (or “SdConfig.exe”) can beconnected to a Safedock/DGS through the GOS, start the “SdConfig.exe” programand perform a REMOTE connection to a known Stand/Gate-ID. To do this, select theREMOTE mode and set the IP-Address of the GOS-Server as well as the Stand/Gate-ID as shown on the GOS-MMI screen (details on how to use the “SdConfig.exe”program is fully explained in the DGS O & M manual).



IOM Manual

GOS Gate Operating System Chapter 2. Installation: Appendix A


Document: IN-AppA-GosRUH-SystemConfig Date: June 2008 Version: 1.0

INSTALLATION: APPENDIX A

GOS SYSTEM CONFIGURATION

CONTENTS


1.

SCOPE .......................................................................................................................... 2

2. GOS CONFIGURATION ............................................................................................... 2

2.1 GENERAL ......................................................................................................... 2

2.2 GENERAL APPLICATION SETTINGS ............................................................. 3

2.3 AIRCRAFT IN SYSTEM .................................................................................... 4

2.4 AIRCRAFT AT STAND CONFIGURATION ...................................................... 5

2.5 CHANGING THE IP ADDRESS ON A GOS SERVER ..................................... 6

2.5.1 Required Changes in the Server ’s INI fi le ............................................... 6

2.5.2 Required Changes in the Workstation’s INI file...................................... 6

2.6 CHANGING THE IP ADDRESS ON A WORKSTATION .................................. 6

3. STAND NAME CONFIGURATION ............................................................................... 7

3.1 GENERAL ......................................................................................................... 7

3.2 SAFEDOCK CONFIGURATION ....................................................................... 7

3.2.1 Com Id Configuration ................................................................................ 7

3.3 GOS INI FILE CONFIGURATION .................................................................... 7

3.3.1 General ........................................................................................................ 7

3.3.2 GOS/Safedock Communication ................................................................ 7

3.3.3 GOS HMI Stand Name ............................................................................... 9

3.3.4

Ai rcraft at Stand Configuration ................................................................ 9

3.3.5 Miscellaneous Sections ............................................................................ 9

4. IATA CODE AND AIRCRAFT CONFIGURATION ..................................................... 10

4.1 GENERAL ....................................................................................................... 10

4.2 GOS INI FILE CONFIGURATION .................................................................. 10

4.2.1

Updating IATA/ICAO codes .................................................................... 10

4.2.2 Updating the Aircraft Menu ..................................................................... 11

4.2.3 Ai rcraft at Stand Configuration .............................................................. 11

5. INTERLOCK CONFIGURATION ................................................................................ 12

5.1 GENERAL ....................................................................................................... 12

5.2

CONFIGURATION EXAMPLES ..................................................................... 13

6.

CAMERA CONFIGURATION ..................................................................................... 14

6.1 IP ADDRESS CONFIGURATION ................................................................... 14

6.2 PICTURE VIEWING ........................................................................................ 14

6.3 PICTURE LOGGING ...................................................................................... 14



IOM Manual




1. SCOPE

This document describes the maintenance of the GOS.INI file, which is unique forevery GOS PC. From this file, all GOS related applications get their parameters atstart-up.

The GOS.INI file contains several sections that are not described in this manual.These sections are for internal usage of the GOS system and are not to be modifiedby the user.

This document also describes the configuration of the following matters:

(a) HMI layout at workstations

(b) Stand Name assignments

(c) IATA code and aircraft definitions

2. GOS CONFIGURATION

2.1 GENERAL

The GOS.INI file is built up around several sections. Each one contains one or moreconfiguration settings for the system. Each setting consists of an ItemName to identifythe item and a set of values for that item.

Example:

[SECTIONNAME]

ItemName=value1, value2, ..., value n

Note: ItemName must be unique for each line within the section.

Considerations:

(a) In the beginning of the GOS.INI file, there is an information header, tellingabout the file version, changes that have been made and when they weremade. After every change, this header shall be updated.

(b) TAB characters shall not be used in the INI file.

(c) SPACE characters shall not be used in SECTIONNAMEs or ItemNames.

(d) If you place a semicolon in front of a statement, the GOS software will ignorethe line, e.g. ;TIME_INFO =UTC

(e) For changes to take affect, the GOSKRNL and GOSHMI applications mustalways be restarted.



IOM Manual




2.2 GENERAL APPLICATION SETTINGS

The section APPLICATION controls several functions of the system.

Item Name Value Descript ion

SYSTEMSTATUS= YES

NO

Whether system status (active/standby)shall be reported or not to GOS MMI.

ACTIVE_VISIBLE= YES

NO

Only relevant if SYSTEMSTATUS =YES.

Whether to display ‘Active Server’ button onscreen or not.

If NO is configured, the status button willonly appear on screen when a statuschange occurs, and disappear when a userconfirms the event.

STDBY_VISIBLE= YESNO

Only relevant if SYSTEMSTATUS =YES.Whether to display ‘Standby Server’ buttonon screen or not.

If NO is configured, the status button willonly appear on screen when a statuschange occurs, and disappear when a userconfirms the event.

ACTIVE_POS= x-pos,y-pos

Position on screen for ‘Active Server’button.

STDBY_POS= x-pos,y-pos

Position on screen for ‘Standby Server’button.

TIME_INFO= UTC

LTC

Whether to display the time in UTC or LTCformat.

If neither UTC nor LTC is configured, thetime will not be displayed at all.

OPERATOR= YES

NO

Whether to allow PARK ON/OFF and SHUTDOWN from GOS

ALLOWSTARTDOCK= YES

NO

Whether to allow start of docking or not

from GOS (OPERATOR=YES must be usedhere)

ALLOWACTIVATE= YES

NO

Whether to allow start of scheduled dockingor not from GOS (OPERATOR=YES mustbe used here)

SEND_RAMP_COMMAND YES

NO

Whether to allow Open/Close Ramp to besent from GOSMMI

SEND_FREE_TEXT YES

NO

Whether to allow to send free text to DGSfrom GOSMMI

SEND_LAST_BAGS YES

NO

Whether to allow to send Parked Last Bagsfrom GOSMMI



IOM Manual




2.3 AIRCRAFT IN SYSTEM

The aircraft name displayed for each aircraft type is controlled by the BUTTONSsection.

The BUTTONS section lists all aircraft types, and assigns them to a unique GOS

Aircraft ID. The GOS.INI file must be updated on every GOS PC for any changes totake effect.

Syntax:

GosAircraftName=N, N, GosAircraftID, N, Manufacturer

GosAircraftName:

The name of this aircraft type displayed in GOS HMI.

GosAircraftID:

Aircraft ID for this aircraft type. Each aircraft type defined in the SAFEDOCKsystem has a unique ID assigned to it. This ID is used to synchronize the

GOS with the configuration data in the DGS.

Manufacturer:

Aircraft manufacturer text displayed in GosHMI

The ‘N’ parameters are for internal use, and should not be modified.

Example:

[BUTTONS]

A30B=5,1,1,1,Airbus

A310=4,1,2,1,Airbus

A320=2,1,3,0,Airbus



IOM Manual




2.4 AIRCRAFT AT STAND CONFIGURATION

Any attempt to activate a docking procedure, using an aircraft type not configured atthe Safedock, will result in an error generated by the Safedock.

To avoid sending commands containing aircraft types not configured at a specificStand, the GATECONFIG section can be used to specify all aircraft types configuredat each Stand. Only the aircraft types listed will be displayed in the HMI for theselected Stand.

This can be useful to set up on a GOS Workstation.

Syntax:

RecId=StandName, AircraftName_1, ..., Ai rcraftName_n

RecId:

A unique name (preferably based upon the stand name) to identify the entry.

StandName:The name of the Stand for which the configuration is being specified. Thisname must match the name for one of the Stands specified in the GATESsection.

Ai rcraftName:

A list of names of the aircraft types allowed for docking at this Stand. Eachaircraft name must have a matching entry in the BUTTONS section.

Note:

(i) The configuration for a single Stand can be divided into more thanone line, simply by making another line containing the same‘StandName’ but different ‘RecId’, with the next part of the aircraft list.

(ii) If no entry exists for a Stand, all aircraft types will be allowed in thedocking commands sent to the Safedock at that Stand.

Example 1:

[GATECONFIG]

A01A=A01,B 727,B 767-300,A 300,A 330,B 757,B 777-200,L 1011,L 1011-500

Example 2: (The StandName A02 binds the two lines together into the same Stand)

[GATECONFIG]

A02A=A02,B 727,B 767-300,B 747,B 747SP,A 300,A 330,A 340,B 757,B 777-200

AO2B=AO2,B 737, B 767-300,M 90,M 80



IOM Manual




2.5 CHANGING THE IP ADDRESS ON A GOS SERVER

2.5.1 Required Changes in the Server’s INI file

Changing the IP Address on the servers affects the keep-alive communication and file

replication on the servers.The following sections must be updated in the servers INI files:

[SYSTEMMONITOR] – Keep-Alive communication

ADDR=192.168.2.35

PORT=5000

[SYSTEMSYNC] – File replication

ADDR=192.168.2.35

PORT=5050

The ‘ADDR’ field in both sections must specify the ip address of the other server.The ‘PORT’ field defines the TCP port number, used by the server to listen forconnection attempts from other server.

Important! The port number must be the same on both servers.

2.5.2 Required Changes in the Workstation’s INI file

Restart GOSMMI, halt the connection and type in the new IP-Addresses to theservers.

2.6 CHANGING THE IP ADDRESS ON A WORKSTATION

It’s the responsibility of the workstations to connect to the servers. Therefore changingthe IP Address on a workstation has no impact on the configuration of other parts of

the system.



IOM Manual



3. STAND NAME CONFIGURATION

3.1 GENERAL

A change of stand requires changes in different parts of the system. The following is adescription of where changes are required:

(a) SAFEDOCK Configuration

(b) GOS.INI on all computers

3.2 SAFEDOCK CONFIGURATION

3.2.1 Com Id Configuration

The parameter Com Id in the ‘Setup Parameters’ dialog must be set usingSdConfig.exe. Below picture gives an indication of where to find this parameter.

The field Com Id must be unique for each Safedock, and can be set to any valuebetween 1-93 and 96-223 (94 and 95 are reserved for other purposes).

The Com Id value will also be set at the GOS side (described below).

Note: The name of the Stand can optionally be displayed in the LED display of theSafedock. The fields ‘Stand No’ and ‘Stand name’ determine what to be displayed.What is displayed here is not essential to the system functionality. However it’s goodpractice to display the actual Stand name to avoid confusion.

3.3 GOS INI FILE CONFIGURATION

3.3.1 General

The following functions in GOS are depending on the Stand Name:

(a) The Communication between GOS and SAFEDOCKs

(b) GOS HMI layout configuration

(c) Aircraft at Stands

(d) GOS Database

3.3.2 GOS/Safedock Communication

The communication between GOS and SAFEDOCKs are set up by severalconfiguration scripts in the GOS.INI file. One COMM_LINKS section listing all standsavailable and one section STAND_kk for each individual Stand.

Syntax of COMM_LINKS:

StandID = LinkName

StandID:




IOM Manual




A unique name identifying the Stand. This name can, but need not, be thesame as that found in the GATES section, the Stand and the communicationlink will be tied together by the ComId of theStand. Each Stand listed will haveits own section, listing the communication parameters to use.

LinkName:

The name of the communication link to be used for the Stand. The availablecommunication links are SAFEDOCK for serial communication andSD_TCPIP/SD_UDP for network communication.

Syntax of each StandID section:

The name of each section must match the StandID listed in theCOMM_LINKS section. Each section can contain the following items:

PORT = <TCP Port Number>

The Ethernet converter in the Safedock is configured to listen forconnection attempts from GOS on this TCP port.

ADDR =<IP Address>

IP Address of Ethernet converter in the Safedock

Configuration of Ethernet controller is described in chapter 2, Appendix C.

LOG=<YES/NO>

Flag to indicate whether this link should automatically gatherSafedock log files at the end of each docking procedure.

FirstLastGosID =<FirstComId, LastComId>

Tells with which Safedock this Link shall communicate with.

<FirstComId, LastComId> corresponds to the ComId used in the GATESsection and in the SAFEDOCK setup. For a point-to-point communication, theFirstComId and LastComId will match.

Example:

[COMM_LINKS]STAND_A01=SD_TCPIPSTAND_A02=SD_TCPIP..[STAND_A01]PORT=50101 ADDR=192.168.2.35FirstLastGosID=1,1LOG=YES

[STAND_A02]PORT=50101 ADDR=192.168.2.36FirstLastGosID=2,2LOG=YES

Description of example:

The lines STAND_A01=SD_TCPIP and the section [STAND_A01] work together. Thestring STAND_A01 points out a specific Stand, and must be equal in both places.(The string STAND_A01 only binds the two sections together, but it’s essential, for an

easy understanding, that a name similar to the actual Stand name is used).



IOM Manual




3.3.3 GOS HMI Stand Name

The symbols and parameters of the GOS HMI is configured under the sectionGATES. The example below illustrates some parameters with the Stand name, usedin the HMI.

Syntax: StandName=n,n,n,n, n ,n,n,n, n,n,n,n, n,n, n,n, ComId, n

Stand Name:

The name of the Stand. This name is displayed on the Stand symbol in theHMI. This name must match the ‘Stand name’ used in the GOS database

Com Id:

The unique communication ID that identifies this Stand. This ID must be thesame as the ComId used in the Safedock.

The ‘n’ parameters are for internal use, and should not be modified (specifies thelocation of stand symbol, centre line and aircraft types on the screen).

Example:

[GATES] A57=0,0,0,0, 0,0,0,0, 70,15,50,50, 0,0, 0,0, 157,0 A55=0,0,0,0, 0,0,0,0, 120,15,50,50, 0,0, 0,0, 155,0 A53=0,0,0,0, 0,0,0,0, 170,15,50,50, 0,0, 0,0, 153,0

3.3.4 Aircraft at Stand Configuration

To avoid sending commands containing aircraft types not configured in the DGS, theGATECONFIG section can be used to specify all aircraft types configured at each

Stand.If this feature is used and an entry in the GATES section, or in the BUTTONS section,is updated, changes must also be made in the GATECONFIG section.

Configuration of this section is described in more detail in section 2 above.

3.3.5 Miscellaneous Sections

A series of configuration sections are used for miscellaneous purposes. Someexamples are given below.

3.3.5.1 MMILINK

The MMILINK section defines the Stands, for which the GOS HMI monitors status.

Syntax:FirstLastGosID =<FirstComId, LastComId>

Defines the range of Stands, by ComId, to be monitored at this HMI.

Example:

[MMILINK]

FirstLastGosID=1,157

3.3.5.2 SETUPCAL

The SETUPCAL configuration section defines the Stands, for which a remotebetween SAFEDOCK and SDCONFIG is allowed.

Syntax:

FirstLastGosID =<FirstComId, LastComId>



IOM Manual




Defines the range of Stands, by ComId, to be controlled.

PORT=PortNo

Defines the TCP port number, used by SETUPCAL.DLL to listen forconnection attempts from SDCONFIG.

Example:

[SETUPCAL]

FirstLastGosId=1,157

PORT=4500

3.3.5.3 Time Synchronization

The following sections define the Stands, which shall have time synchronization byGOS.

Syntax:

FirstLastGosID =<FirstComId, LastComId>Defines the range of Stands, by ComId, to be time synchronized.

Example:

[SETTIME]

FirstLastGosID=1,157

4. IATA CODE AND AIRCRAFT CONFIGURATION

4.1 GENERAL

An update of IATA codes or aircraft types requires changes in different parts of the

system. The following indicates where changes are required.(a) GOS.INI on all GOS computers

4.2 GOS INI FILE CONFIGURATION

4.2.1 Updating IATA/ICAO codes

The IATA_NAME section is used when GOS is interfacing to FIDS. When FIDS sendIATA/ICAO codes to GOS, the IATA codes have to be converted to valid SAFEDOCKID:s.

By using the IATA_NAME section it is possible to configure the GOS system so thatseveral IATA/ICAO subtypes get converted to one generic aircraft type when sent toSafedock. Below example will illustrate:

[IATA_NAME] A 300=AB2,AB3,AB4,AB6,ABF

A 310=310,312,313,31F

A 319=319

Etc.

Every entry has the format: DGS_NAME =FIDS_1, FIDS_2,k#

Where

(a) DGS_NAME

(i) The name of the DGS Aircraft. This name must match the name forone of the names specified in the BUTTONS section.

(b) FIDS_1



IOM Manual




(i) The IATA code of the aircraft as reported by the FIDS link. Severalcodes stated on the same line will all be converted to the sameaircraft type when sent to Safedock.

Every conversion that exists in this section must also exist in the BUTTONS section.If this section is not present, the conversion will be made directly from the BUTTONSsection.

4.2.2 Updating the Aircraft Menu

The aircraft name displayed for each aircraft type is controlled by the BUTTONSsection. If an aircraft name is updated in the BUTTONS section (left column), itmust also be updated in the IATA_NAME section.

The BUTTONS section lists all aircraft types, and assigns them to a unique GOS Aircraft ID. The GOS.INI file must be updated on every GOS PC for any changes totake effect.

Syntax:

GosAircraftName=N, N, GosAircraft ID, N, Manufacturer

GosAircraftName:

The name of this aircraft type displayed in GOS HMI.

GosAircraftID:

Aircraft ID for this aircraft type. Each aircraft type defined in the SAFEDOCKsystem has a unique ID assigned to it. This ID is used to synchronize theGOS with the configuration data in the DGS.

Manufacturer:

Aircraft manufacturer text displayed in GosHMI

The ‘N’ parameters are for internal use, and should not be modified.

Example:

[BUTTONS]

A-300=5,1,1,1,Airbus

A-310=4,1,2,1,Airbus

A-320=2,1,3,0,Airbus

4.2.3 Aircraft at Stand Configuration

To avoid sending commands containing aircraft types not configured at the DGS, theGATECONFIG section can be used to specify all aircraft types configured at eachStand.

If this feature is used and an entry in the BUTTONS section is updated, changes mustbe also be made in the GATECONFIG section.

This section is described in more detail in section 2 of this manual.



IOM Manual




5. INTERLOCK CONFIGURATION

5.1 GENERAL

The module INTERLOCK.DLL evaluates rules about what aircrafts are allowed todock on a stand based on the status of adjacent stands.

Every aircraft type has a class designation, which is ranging from A-Z, where earlierletters will always indicate a smaller (with regard to wingspan) aircraft. Thus, a class Aaircraft will always be smaller than a class C aircraft.

The interlock information will contain a series of blocking rules for each stand, whereeach rule identifies an aircraft class, the blocking stand and the smallest aircraft classon that stand that blocks this docking. The interlock rules are placed in the[INTERLOCK] section of GOS.INI, and the syntax for the rules is:

StandItem=,SelectedStand, SelectedAc(BlockingStand:BlockingAc), {Comments},[AC1,AC2,….;AcClass;Stand1,Stand2,….], [AC3;AcClass;Stand3]

Where:StandItem Unique index in INI file

SelectedStand The name of the stand for which a rule appliesto (shall match any of the names seen inGOSMMI)

SelectedAc The smallest aircraft class at the selectedstand this rule applies to. The rule is valid foraircraft of this and all higher classes. I.E. anyrule for class A will apply to ALL aircraft types,a rule for class D will apply to aircrafts of classD-Z.

BlockingStand The name of a stand that can block

operations at this stand.BlockingAc The smallest aircraft class at the blocking

stand that will block an operation of theselected aircraft. If there is an aircraft of thisclass or higher at the blocking stand, the ruleis fulfilled and the requested docking will beblocked. A blocking aircraft of class A willtherefore mean that any aircraft at theblocking stand will block the requestedoperation.

{} Free Text field. Any text within brackets istreated as a comment, and can be put in

anywhere in the interlock rule.[AC1,AC2,…;Class;stand1:stand2,….]

Example 1:

D42=D42, [A310;B;D44]

Example 2:

D44=D44, [A310, B737;D;D42,D46]

Redefinition of class designator.

If A310 is parked at stand D42 and stand D44requests to start docking, the A310 shall beredefined to be a class B type.

If A310 or B737 is parked at stand D44 andstand D42 or D46 requests to start docking,the A310/B737 shall be redefined to be aclass D type.

Note: exception rules shall only be used whennecessary to redefine the class types.



IOM Manual




Note: A rule for a stand can be divided into two lines in the GOS.INI file.

Example:

D42_A=D42, A(D44:C), [AC1;B;D44]

D42_B=D42, B(D46:F), [AC2;C;D44]

The class configuration is done in the [BUTTONS] section.

Example:

[BUTTONS]

B737=3,3,7,0,Boeing,C

B 747=2,3,8,1,Boeing,E

5.2 CONFIGURATION EXAMPLES

B737 = class B, B747 = class D

Stand1=S1,A(Stand2:A) Any aircraft at stand 2 will block operations atstand 1

Stand2 =S2, A(Stand1:A),C(Stand3:E)

1. Docking at stand 2 will be blocked if there isany aircraft at stand 1.

2. Docking a C type or bigger aircraft at stand2 will be blocked if there is a E-type or biggeraircraft at stand 3.

Stand3=S3, E(Stand2:C) Dockings an E type or bigger aircraft at stand3 will be blocked if there is a C-type or biggeraircraft at stand 2. All smaller aircrafts arealways allowed to dock.

Redefinition example:

Stand2=S2, C(Stand3:E)Stand3=S3,E(Stand2:C),[B747;D;Stand2]

In general, docking a C type or bigger onstand 2 will be blocked if there is an E-type orbigger parked at stand 3.

However, docking a C-type or bigger at stand2 when a B747 is Parked at stand 3 will beallowed, because the B747 on stand 3 hasbeen redefined to be a class D type whenstand 2 is docking.

Note: If no blocking rules are configured, docking will always be allowed.



IOM Manual




6. CAMERA CONFIGURATION

6.1 IP ADDRESS CONFIGURATION

In order to communicate with the camera on each stand, IP Address for each cameramust be known by GOS. This is configured in the [CAMERA_IP] section according tothe format: Stand=Camera IP Address.

[CAMERA_IP]

24=192.168.2.20

32=192.168.2.22

….

6.2 PICTURE VIEWING

Setup the following in the [APPLICATION] section to affect the behaviour of GOSMMI.

CAMERA=YES Enables real time picture viewing in GOSMMI

PICTURELOG=YES Allows to view stored camera images fromdisk from GOSMMI

POPUP_ON_ERROR=YES Camera window will pop-up in GOSMMI uponerror from Safedock

MAX_CAMERA_FORMS=4 Maximum number of camera forms allowed tobe open at the same time in GOSMMI

6.3 PICTURE LOGGING

In the [FEATURE_LINKS] section GOS can be configured to upload camera imagesautomatically during a docking.

Add the following line to the [FEATURE_LINKS] section: PICTURE_LOG=

PICTURE_LOGCreate a section [PICTURE_LOG] and add the following:

SERVICE=CAMERALOG Will load Cameralog.exe upon start of of GOS

FirstLastGosID=1,161 Stands that camera pictures will be saved for

PICT_AFTER_STOP=5 Number of pictures to record after dockinghas finished.

LOGDAYS=7 Number of days to keep camera images ondisk. (Make sure necessary disk space isavailable for chosen configuration)

ACTIVE=NO

DOCKING=YES

DOWNGRADE=YES

BLOCKED=NO

ERROR=YES

States to start/not start camera recording for



IOM Manual

GOS Gate Operating System Chapter 3. Operation


Document: US-GosRUH-Operation Date: June 2008 Version: 1.0

CHAPTER 3

OPERATION

CONTENTS


1.

SCOPE .......................................................................................................................... 3

2. DOCKING MONITORING ............................................................................................. 4

2.1 GENERAL ......................................................................................................... 4

2.1.1 GOS Standard System............................................................................... 4

2.1.2 Co-operation wi th External Systems ....................................................... 4

2.2 VDU SCREEN LAYOUT ................................................................................... 5

2.2.1 General ........................................................................................................ 5

2.3 HELP MENU SYSTEM ..................................................................................... 7

2.3.1 General ........................................................................................................ 7

2.4 EVENT AND STATUS DISPLAY ...................................................................... 8

2.4.1 Stand Status Display ................................................................................. 8

2.4.2 Stand Status Box ..................................................................................... 11

2.4.3 DGS Error Codes ..................................................................................... 12

2.4.4 System Event Windows .......................................................................... 13

3. MAINTENANCE FUNCTIONS .................................................................................... 14

3.1 GOS AND SAFEDOCK EVENT LOGGING .................................................... 14

3.1.1 GOS Event Log ......................................................................................... 14

3.1.2 Viewing a GOS Event Log File................................................................ 14

3.2

DOCKING LOG FILES .................................................................................... 18

3.2.1 General ...................................................................................................... 18

3.2.2 Viewing and Print-Out ............................................................................. 18

3.3 AUTOMATIC UPLOAD OF SAFEDOCK CONFIGURATION FILES ............. 19

3.3.1 General ...................................................................................................... 19

3.4 CLOSING DGS FOR MAINTENANCE ........................................................... 19

3.4.1 General ...................................................................................................... 19

3.5 DISPLAY OF DGS TYPE ................................................................................ 20

3.5.1 General ...................................................................................................... 20

3.6 SAFEDOCK MAINTENANCE USING SDCONFIG ........................................ 21

3.6.1 General ...................................................................................................... 21

4. DOCKING CONTROL ................................................................................................. 21

4.1 GENERAL ....................................................................................................... 21

4.2 DOCKING COMMANDS ................................................................................. 21

4.2.1

Log On Procedure.................................................................................... 21

4.2.2 Creating Users ......................................................................................... 22

4.2.3 Start ing a Docking Procedure ................................................................ 23

4.2.4 Activating a Scheduled Dock ing ............................................................ 25

4.2.5 Insert ing a Scheduled Flight ................................................................... 25

4.2.6 Displayed Statuses During Dock ing ...................................................... 26

4.2.7 Shut down................................................................................................. 28

4.2.8 Park On ..................................................................................................... 28



IOM Manual




4.2.9

Park Off ..................................................................................................... 28

4.3 CAMERA ......................................................................................................... 29

4.3.1 Viewing Live Images ................................................................................ 29

4.3.2 Viewing Recorded Images ...................................................................... 30

4.4

ADJACENT STAND INTERLOCK .................................................................. 30

4.4.1 Important Things to Know ...................................................................... 30

5. FIS INTERFACE .......................................................................................................... 31

5.1 BASIC FUNCTIONALITY ................................................................................ 31

5.2 ARRIVAL PROCEDURE................................................................................. 31

5.3 DEPARTURE PROCEDURE .......................................................................... 31

5.4 RIDS INFORMATION ..................................................................................... 31

5.5 SPRECIAL OPERATIONAL PROCEDURES ................................................. 32

5.5.1 General ...................................................................................................... 32

5.5.2 Unprocessed Arr iving Flight .................................................................. 32

5.5.3

Unsuccessful Dock ing ............................................................................ 32

APPENDICES:

GOS Features Appendix AGOS Access Manager Appendix BGOS Reporter Appendix C



IOM Manual




1. SCOPE

The Gate Operating System/GOS has two separate Man-Machine-Interfaces.

(a) The Docking Monitoring program, named GOSMMI

(b) The Scheduled Flight Management Tool, named SFM

Sections 2 and 3 of this document are descriptions of the Docking Monitoring &Control MMI.

Section 4 describes the man-machine interfaces for updating Scheduled Flights andStand parameters.

(a) The table A_FLIGHT contains information about scheduled active flights.These data are used for starting the docking and departing procedures at theStands and are also used for displaying relevant flight information duringthese procedures.

(b) The table STAND contains information mainly about process start times,

related to scheduled flight’s arrivals and departures at a Stand. Each Stand’sDGS status is also a part of this database table.

A special MMI is used for SAFEDOCK maintenance, and is described in Chapter 4,MAINTENANCE, of the IOM Manual of the SAFEDOCK SYSTEM.



IOM Manual




2. DOCKING MONITORING

2.1 GENERAL

2.1.1 GOS Standard System

The Gate Operating System/GOS of Safegate comprises one or several PCcomputers, communicating with the Docking Systems, SAFEDOCK, at each Stand. All SAFEDOCK units at the airport can be monitored from each GOS system node,which could be the GOS Workstation or the GOS Server.

This section covers Docking Monitoring & Control, which is one of the UserInterfaces/MMI at a GOS Workstation.

For maintenance purposes the Docking Monitoring system also includes an EventLog feature, giving a history of all events at the Stands and within the GOS systemitself.

2.1.2 Co-operation wi th External Systems

GOS has an internal database for automatic control of scheduled flights. The

database can be created or updated from an MMI software, installed on a GOSworkstation in ACC for example.

An external FIS/GMS system is connected to GOS for automatic insertion andupdates of scheduled flights.

The FIS connection can also be used for displaying flight information at the Standassigned for an arriving or departing flight.



IOM Manual



2.2 VDU SCREEN LAYOUT

2.2.1 General

The operator at a GOS node uses a PC workstation with Microsoft Windows 2000based software for monitoring the docking operations at each Stand.

After having logged on as a GOS user, the program GOSMMI is selected fromWindows Start Menu/Program.

The first time the program is started IP Addresses to the GOS servers must beentered into the address fields.

At next program start-up the program will automatically try to connect to specifiedsources after a few seconds. The connection attempt can be halted by the user byclicking the Halt Connection button.




IOM Manual



The VDU screen displays a picture of the airport’s layout with symbols for all theStands, which are connected to the central system GOS.

AIRPORT STAND LAYOUT




IOM Manual



2.3 HELP MENU SYSTEM

2.3.1 General

The GOSHMI has a built-in help system that can be displayed by pressing the F1 key.




IOM Manual



2.4 EVENT AND STATUS DISPLAY

2.4.1 Stand Status Display

During a docking procedure, the status of a Stand is changed several times. All ofthese changes will be displayed on the screen by Stand number tags changingcolour, and by aircraft symbols appearing on Stand centrelines.

Green Stand number tag with blacktext:

Stand is Ready. The Stand is emptybut not confirmed to be used yet. Thisstatus will appear automatically after apushback procedure.

READY

Green Stand number tag with whitetext:

Stand is Ready Open. The Stand isempty and confirmed to be used by alocal or GOS operator.

READY OPEN

Grey Stand number tag with black text:

Stand is Scheduled for docking butnot confirmed by operator at a Stand.Docking is started immediately whenconfirmed by local operator.

SCHEDULED DOCKING

Yellow Stand number tag andcentreline:

Docking Request status. Operator has

selected an aircraft, which is checkedagainst the GOS server. Docking isstarted immediately if allowed.

REQUEST INTERLOCK

Red Stand number tag with white text:

An interlock request has beenevaluated to not allow start of docking.

STAND INTERLOCKED




IOM Manual


GREY stand number tag with red text:

The interlock request could not be evaluated byGOS.

INTERLOCK UNKNOWN

GREY stand number tag with red text:

GOS has not responded to the Interlock requestwithin a certain time (time is configured in DGS)

INTERLOCK TIMEOUT


Stand is active. The docking system iswaiting for the aircraft to dock.

ACTIVE


Stand is in down grade mode. Thedocking has been started, but thevisibility is low due to heavy fog, rain orsnow.

DOWN GRADE

Yellow Stand number tag andcentreline with a yellow aircraft oncentreline:

Docking status. An aircraft is docking.

DOCKING

Blue Stand tag, blue aircraft and blackcentreline:

Parked status. The aircraft hasreached its stop position.

PARKED





IOM Manual


Light blue Stand tag, blue aircraft andblack centreline:

Scheduled departure status (Onlywith standard interface to FIS). An

aircraft is parked at the Stand. Theaircraft is planned to depart shortly.

SCHEDULED DEPARTURE

Light blue Stand tag, blue aircraft andblack centreline:

Departing. The aircraft is no longerpresent at its parked position, but maystill be within the gate area.

DEPARTING

Red Stand number tag:

Emergency stop button has beenpushed.

EMERGENCY STOP

Pink Stand number tag:

Communication error . Thecommunication with the dockingsystem is interrupted.

COM ERROR

Pink Stand number tag with white text:

DGS error .

The Docking System has an errorstatus.

DGS ERROR





IOM Manual


Brown Stand number tag with whitetext:

Maintenance status. Stand is

occupied for maintenance activities.Remote activation of dockingprocedures is not allowed.

MAINTENANCE

Brown Stand number tag with whitetext:

Closed for Maintenance. The stand isclosed for remote access due to

planned maintenance activities. TheVDGS remain available for localoperations.

CLOSED FOR MAINTENANCE

2.4.2 Stand Status Box

Status of the Docking System, SAFEDOCK, at a Stand can be viewed by selectingthe Stand number tag with the mouse. When the tag is selected, a small box, thatcontains status information, will appear next to the tag.

On the below picture a number of Stands have been selected, and information in thestatus boxes can be viewed. When the Stand tag is selected again, the status boxdisappears.

STAND STATUS BOXES

The system indicates following aircraft/flight information in the status box under theaircraft type field.

(a) If started by the local Stand operator the text ”- LOCAL” will be displayed inthe status box under the aircraft type (as flight number is not available).

(b) If started by the GOS operator the text ”- GOS” will be displayed in the statusbox under the aircraft type, if flight number is not available.

(c) If flight number is available, this will be displayed instead of “- GOS”.





IOM Manual




(d) If both flight and registration number is available, the flight number will bedisplayed as default. Flight and Registration number can be alternativelydisplayed by left clicking with the mouse in the status box under the aircrafttype field.

2.4.3 DGS Error CodesIn case of an error with the SAFEDOCK system, an associate code is displayed withthe error message in the status box and in the log file. The code represents thefollowing error types for the SAFEDOCK system:

SAFEDOCK Error Codes Descript ion

‘00’ - No error This code is sent when the system has not an errorstatus

‘01’ - Laser error Laser does not send data, time-out during scan

‘02’ - Mirror error Stepper motor with mirror are not moving, or

home position is not found

‘03‘ – Auto-calibration error Calibration check unsuccessful

‘04’ – Installation data error Calibration data are not present, calibration

might not be done

‘05’ – Profile error Profiles of a specific aircraft type could not

be loaded into memory

‘06’ - Not used

‘07’ - Not used

‘08’ – Configuration error Aircraft is not configured for the Stand;

Invalid stop position or reference (others than nose,door or nose wheel)

‘09’ - Door blocked Aircraft is not allowed to dock to the selected door

‘10’ – Display error A severe error with the LED matrix display is

Detected

‘11’ - CU Restarted Controller/CPU has restarted previously

‘12’ - ID failed Identification of the selected aircraft has failed.

‘13’ – Docking too fast Aircraft is approaching too fast

‘14’ – Bridge not in (option) Aircraft Loading Bridge is not drawn in, if configured

‘15’ –Bridge not up (option) Aircraft Loading Bridge is not in upper position

‘16’ – Parameter error Stand parameters could not be loaded

‘17’ – Anomalous Abort Aircraft is lost just before stop position

‘18’ – Operator Panel error No communication with operator panel‘19’ – Emergency Stop error Emergency stop circuitry is not working

‘20’ – Laser Amplitude Laser amplitude check error

‘21’ – Stand Blocked The DGS view of the Stand area is blocked.

‘22’ – Undefined Centreline Undefined/Invalid centreline

‘23’ – View Blocked Laser view through the window blocked

‘24’ – Apron Blocked Object detected during apron check

‘25’ – Walktest Required Walktest is required due to changes in configuration

‘26’ – Temp Out of Range The temperature in the system is to high or to low.

‘27’ – Laser Safety Error Safety circuitry of laser has not a correct time

constant or does not control the laser.‘99’ – Communication Error Communication between DGS and GOS is broken



IOM Manual



2.4.4 System Event Windows

All events and errors of the Docking systems, the central Gate Operating System, andthe communication to external systems can be configured to be displayed in separateevent windows according to picture:

Each type of event can be configured to generate an audible alarm. By default noalarm sound is generated. Configuration is done in the GOS.INI file.

The alarm button indicates if the audible alarm feature is enable or disabled on thelocal PC. By changing the state of the alarm button to disabled/enabled, the audible

alarm will be turned off/on. Any message generating an audible alarm will also cause the title screen of itswindow to start flashing indicating that a new message has arrived.

Each window is resizable and movable on the screen. The window can becollapsed/expanded by pressing the button in the upper right corner.

The window can also be docked to the edge of the screen. When docked, the windowwill expand whenever the mouse pointer hovers over the control and disappearsagain as the mouse leaves the window area.

A message/all messages can be manually removed from the window by right clickingon the message and select Acknowledge/Acknowledge All according to picture.

Available windows and its functionality:

Server Status Window: Current status for Active and Stand by server isdisplayed in this window.

Error Codes A possible error message for a Safedock isdisplayed in this window. A new error willoverwrite existing error. The error will remainuntil confirmed by an operator.

DGS Statuses Current status of each Safedock is displayed inthis window. A new status will overwrite existingstatus.

Interface statuses (not inpicture)

Interface connection statuses (FIS, TMS etc)are displayed in this window. A new status willoverwrite existing status.




IOM Manual



3. MAINTENANCE FUNCTIONS

3.1 GOS AND SAFEDOCK EVENT LOGGING

3.1.1 GOS Event Log

All events and errors of the Gate Operating System, it’s subsystems (the DockingSystems) and the communication to external systems, if any, are monitored andlogged for maintenance purposes. Such information is:

(a) Safedock/DGS system errors

(b) Safedock/DGS events associated with the docking procedure

(c) Commands from GOS

(d) Docking Sequence record; i.e. distance and lateral position of aircraft (anoption)

(e) Billing Events; e.g. Block-On/Off Time at Stands

The name of the log file is based on the current date, and has the formatYYMMDD.log. The GOS event log files are stored in the ‘log’ directory.

The file is stored automatically on the hard disc for a limited number of days (specifiedin GOS.INI). When that limit is reached, the file will be automatically erased.

3.1.2 Viewing a GOS Event Log File

3.1.2.1 General

The Event Log Files are mainly for maintenance purposes, and they are accessed bytwo pop-up menus. These menus are accessed by right clicking anywhere on themonitor screen or on a particular Stand symbol.

COMMAND MENUS

There are three views of the log file available:

(a) View of Log file A view of the entire content of the log file.

(b) View of Blocks on/off A view containing only park on/off events.

(c) View of Command history A view containing only operator commands.

If the ‘log file view’ is activated from the GOS Monitor menu by right-clicking outsideany Stand selector, the view will contain events from the entire GOS system. If the

‘log file view’ is activated by right-clicking on a Stand selector, the view will berestricted to events pertaining the selected Stand only.




IOM Manual



After selecting the ‘View ….’ command, the user can choose to open either today’slog file or any other log file from the speed bar menu.

SELECTION OF LOG FILE

3.1.2.2 GOS Events Log ViewIf ‘View log’ was selected from the GOS Monitor pop-up menu, the below data wouldbe displayed after opening one of the log files. Not only Stand events are displayed,but also GOS system events and those, which are associated with external systemslike FIS. This view also includes Commands and Blocks On/Off events.




IOM Manual



LOG FILE VIEW




IOM Manual



3.1.2.3 Blocks On/Off View

Below is a sample of a ‘Blocks on/off view’ of a selected Stand:

PARKED ON/OFF LOG VIEW




IOM Manual



3.1.2.4 Command History View

Below is a sample of a ‘Command history view’ of a GOS system:

COMMAND HISTORY VIEW

3.2 DOCKING LOG FILES

3.2.1 General

The DGS Log is an extended version of the ‘Short-log’.

The DGS Log will automatically be dumped to GOS at the end of the dockingprocedure, where it will be retained for 32 days default (configurable in GOS.INI).

Under directory “C:\Gos\Log” on the server/servers, each DGS will have its own subdirectory where the log files will be stored. The sub directories will have the samename as the stand symbols in the GOS MMI application.

3.2.2 Viewing and Print-Out

The DGS log files, and the Short-Log files, can be viewed and printed out with theprogram STANDCONFIGPRINT.EXE, called the Stand Configuration Print-Out Utility.

This Utility program is described in the DGS IOM Manual, chapter 4, MAINTENANCE.




IOM Manual




3.3.1 General

To store a backup of each Safedock configuration the configuration files (centrelineand gate configuration) will automatically be dumped to GOS from Safedock when the

configuration has been updated in the Safedock.Under directory “C:\Gos\Log” on the servers/servers, each Safedock will have its ownsub directory where the configuration files will be stored. The sub directories will havethe same name as the stand symbols in the GOS MMI application (this requires atleast Safedock 5.65 and Gos system 3.1.0).

3.4 CLOSING DGS FOR MAINTENANCE

3.4.1 General

The stand can be closed for remote access due to planned maintenance activities.Only local operation and maintenance operations using SdConfig is allowed in thisstate; all other communication is blocked.

The operation is done by selecting ‘Close for Maintenance’ from the drop down menu.

Once maintenance is finished, the stand can be opened for operation by selecting‘Open after Maintenance’ from the drop down menu.




IOM Manual



3.5 DISPLAY OF DGS TYPE

3.5.1 General

The GOSHMI can be configured to display the type of DGS installed on a stand. Theinformation is available by right-clicking on the stand symbol. The first line in the drop

down menu will display the stand name together with type information (Stand F4 Type2). The text to be displayed is configurable in GOS.INI on the local computer.




IOM Manual



3.6 SAFEDOCK MAINTENANCE USING SDCONFIG

3.6.1 General

Maintenance on Safedocks can be performed from GOS by using the softwareSDCONFIG.EXE.

From a workstation, log on to Windows as user ‘dgsmaint’. Over the network, accessthe shared folder ’SDK’ on the server by using Windows Explorer. Start SdConfig.exeby double-clicking on the filename.


4. DOCKING CONTROL

4.1 GENERAL

Control of a SAFEDOCK/DGS system at a Stand can occur from the Local Operatorpanel on apron or from a GOS Workstation. The local control panel and the GOSalways work in parallel. However the GOS workstation has additional data entry

features.

4.2 DOCKING COMMANDS

4.2.1 Log On Procedure

In order to prevent unauthorised personnel to operate the system i.e. SAFEDOCKControl, a password system can be installed optionally.

There are two ways to enter the Log on dialog, by right clicking anywhere on thescreen or by selecting a particular stand. The two options are shown below.

LOG ON MENU

Without anybody logged on, the docking control functions of the GOS system cannotbe performed. However, current status will be displayed, and local operation at thestand is allowed, of course. Also the Log File can be viewed.

When clicking the ‘Log On’ field, the system will ask for a user ID and a passwordaccording to the figure below.




IOM Manual



LOG ON DIALOG

After having logged on as a defined user, the following dialogs will be displayed, whenclicking the screen or a particular stand. With the dialog to the left it’s possible to logoff again, and with the dialog to the rights it’s now possible to send the commandsthat are allowed for the stand specified.

COMMAND MENU

4.2.2 Creating Users

When starting the GOS system for the first time, the original supervisor has to log onas user = ‘safegate’ and input the original password ‘gos’. Once a new user orsupervisor has been assigned, the original user and password will be removed.Therefore it is important to first assign a new supervisor and password, before anew user is defined. After that the supervisor can create other users (or othersupervisors) and assign passwords to these. The user or supervisor can be the namein plain text of the person, who shall operate, and the password will be a secret codefor each individual. The difference between a supervisor and a user is that thesupervisor has the power to decide who shall be authorised as a user.

When you log on as a supervisor, the following dialog will appear, when clickingsomewhere on the screen.




IOM Manual



LOG OFF MENU

By selecting the field ‘Administration’, it’s now possible to create new supervisors and

users. The dialog shown below is used for the purpose.

CREATING USERS DIALOG

4.2.3 Starting a Docking Procedure

A docking procedure can be started from apron/SAFEDOCK or from the GOS. Whenright-clicking over a stand, a command menu appears. This menu indicates which

commands are allowed for the selected stand.




IOM Manual



• Before ‘start-of-docking’ can be performed from the GOS system the ‘Open Stand’command has to be sent to Safedock. This is done for safety reasons, as the toweroperator could not personally inspect the stand area before his order.

• From the menu, shown below, the commands allowed are displayed. Every

command has to be confirmed, and the operator is prompted according to thedialog below.

OPEN STAND MENU

• Docking can be started by clicking ‘StartDock’ in the command menu followed byselecting Manufacturer, and Aircraft Type from the drop down menu. Thecommand is sent to SAFEDOCK, as soon as the ‘Confirm dialog’ is completed.




IOM Manual



START DOCKING MENU

4.2.4 Act ivating a Scheduled Docking

• When the stand has been scheduled with a flight (usually received from a FISsystem), the operator will have the possibility to activate the docking systemwith the scheduled flight information. When right-clicking over a stand,following command menu appears.

• Docking can be started by clicking ‘Activate’ in the menu. The command issent to SAFEDOCK as soon as the ‘Confirm dialog’ is completed.

4.2.5 Inserting a Scheduled Flight

When FIS is unavailable and thus no flights are sent to GOS, the flights can beinserted from the GOSMMI instead.

Right-Click over a stand and select ‘Schedule Flight’; the following dialog will appear.




IOM Manual



1. Select A/C type

2. Select Arrival or Departure flight

3. Type in flight number

4. Type in registration number if one exists

5. Select STAD time (Scheduled time of arrival/departure)6. Select ETAD time (Estimated time of arrival/departure)

7. Press Schedule Docking to send the flight for further processing

Note:

1. The ETAD time will determine when the flight shall be scheduled. Defaultconfiguration is set to 10 minutes before ETAD time.

2. Example: setting the ETAD time to one hour ahead of current time will causethe flight to be scheduled in 50 minutes.

4.2.6 Displayed Statuses During Docking

• The latest command made from GOS will be displayed with the user identity at thebottom line of the GOS Monitor screen. An example is shown below.

LAST COMMAND

• The state of the activated stand will now change to ‘Active’ or ‘Docking’. Based oninformation from the GMS, Flight No and Aircraft type will be displayed in the statusbox, if this field of the pop-up menu is clicked.

• When the docking is completed the stand status changes over to Parked.




IOM Manual


DOCKING COMPLETED MENU

• If the Gate Operating System, GOS, is not working, or the tower operator hasstated the wrong aircraft type, the operator at the apron can always start a dockingprocedure from the Operator Panel in the bridge. This is done by selecting amongthe aircraft types available on the operator panel, and pressing ‘Enter’. The GOSsystem will indicate (in the status box of GOS Monitor) the source of the StartDocking command, which is ‘GOS’.

• If docking is started from operator panel, based on information from theGMS/FIDS, the Flight No. will be displayed in the status box under the aircraft type.

GOS MMI STATUS BOX





IOM Manual



4.2.7 Shut down

The ‘Shut Down’ button can be used if there is a reason for turning off theSAFEDOCK system. A typical reason could be a last minute change of Stand, so theaircraft would arrive at another Stand than was first selected.

SHUT DOWN MENU

The GOS operator must confirm the ‘Shut Down’ command before it is sent toSAFEDOCK.

4.2.8 Park On

Manual Park On is done by selecting ‘Park On’ and also the aircraft type from thedrop down menu.

The GOS operator must confirm the ‘Park On’ command before it is sent toSAFEDOCK.

When GOS has a connection to a FIS system and a flight is associated with theoperation (Safedock is scheduled for arrival with a flight received from FIS), a BlocksOn transaction will be sent to FIS.

4.2.9 Park Off

When the Safedock is parked with an aircraft, the Safedock will periodically scan theStand area for the departure of the aircraft, and when the aircraft is no longerdetected at the stand the Safedock will automatically go to ‘Ready’ state.

However, Manual Park Off can be done by selecting ‘Park Off’ from the drop downmenu.

The GOS operator must confirm the ‘Park Off’ command before it is sent toSAFEDOCK.

When GOS has a connection to a FIS system and a flight is associated with theoperation (Safedock is scheduled for departure with a flight received from FIS), aBlocks Off transaction will be sent to FIS.

Note: Local Blocks On/Off transactions (no flight information available from FIS) canalso be reported to a FIS system if configured to do so. This is optional and dependson the interface between GOS and FIS.




IOM Manual



4.3 CAMERA

4.3.1 Viewing Live Images

Live images can be view from the GOSHMI whenever a camera is installed in theSafedock. To view an image, right click over a stand symbol and select ‘View Camera’from the drop down menu. A camera window will appear on screen showing liveimages from the selected stand.




IOM Manual



4.3.2 Viewing Recorded Images

The GOS system can be configured to record dockings, which then can be viewedfrom the GOS HMI. To view a recorded docking sequence, right click over a standsymbol and select ‘View Camera Log file’ from the drop down menu. Select the

docking sequence to view by clicking on the buttons “Open today’s recordings” or“Open any recording” as show below.

Open any recordingOpen today’s recordings

About/Info Close

1. “Open today’s recordings” will allow the user to select and view one of thecamera recordings for the current day for the selected stand.

2. ‘Open any recording’ will allow the user to select and view one of theavailable camera recordings for the selected stand.

3. Once a camera recoding has been opened it can be viewed or steppedthrough one picture at a time by using the available buttons as illustratedbelow.


Play/Pause Stop Back Forward

4.4 ADJACENT STAND INTERLOCK

4.4.1 Important Things to Know

In order for the interlock functionality to work correctly, it’s important that the Safedocksystems are holding correct status. If an aircraft is manually towed in to a stand, amanual Park On must be made from GOS or from the operator panel to put the stand

in correct status. The simulated stands must be manually Parked On from theGOSMMI. Thus, any stand which has an aircraft parked must be in Parked state.More information about the interlock feature can be found in Chapter 1, SystemDescription.



IOM Manual




5. FIS INTERFACE

5.1 BASIC FUNCTIONALITY

FIS will send arrival and departure flight information to GOS prior to arrival/departure.

One arrival and/or one departure flight at a time per stand will be sent to GOS (notwhole flight scheduled in advance). Thus, a new flight sent from FIS will override anyexisting flight for a stand.

GOS will send Block On/Off events to FIS upon successful arrival/departure.

5.2 ARRIVAL PROCEDURE

Before the aircraft arrives at the gate (at touch down), FIS will send a flight to GOS.When the flight gets within the time window for start of docking (configurable; defaultis 10 minutes before BTA – best time available of arrival) and Safedock is ready toaccept the flight (in Ready and Scheduled status), GOS will schedule DGS or startDGS with the flight (schedule or start of docking is configurable in GOS).

A scheduled docking needs to be activated from GOS or f rom the local Operator

Panel at the gate.Upon successful docking, a Block On message will be sent to FIS.

As long as the docking system has not been activated, FIS can update the flight(change stand, new aircraft, new Registration number etc).

If Safedock is in such a status (Maintenance, error etc) that the arrival flight cannot beaccepted, GOS will not Schedule the Safedock with the flight. However, if Safedockchanges to a status in which it can accept the flight, then GOS will Schedule theSafedock unless the flight is too old (the time when a flight is considered to be old isconfigurable).

5.3 DEPARTURE PROCEDURE

Before departure, FIS will send a departure flight to GOS (10 minutes before BTD -best time available of departure).

When the flight gets within the time window for start of scanning (configurable butdefault is 10 minutes before BTD) and Safedock is Parked, GOS will scheduleSafedock with the flight and start Park Off detection. Upon successful departure ofthe aircraft, a Block Off message will be sent to FIS.

As long as the docking system remains Parked, FIS can update the departure flight.

If Safedock is in such a status (Ready, Maintenance, error etc) that the departureflight cannot be accepted, GOS will not Schedule Safedock with the flight. However, ifSafedock changes to a status in which it can accept the flight, then GOS will Schedulethe Safedock unless the flight is too old (the time when a flight is considered to be oldis configurable).

5.4 RIDS INFORMATION

Based on the flight information received from FIS prior to each docking the systemcan be configured to display text messages on Safedock some time before start ofdocking. Currently the following text information is available: Main flight number,ETAD or STAD and Count down time to Arrival or Departure.

Example:



IOM Manual


Ar rival Departure

Note: The line on DGS where a specific text is displayed is configurable in GOS.

5.5 SPRECIAL OPERATIONAL PROCEDURES

5.5.1 General

Following sections describe some operational procedures that might be useful for theGOS operator when a connection to a FIS system is used.

5.5.2 Unprocessed Arriving Flight

If DGS unit is in status ‘Scheduled’ (grey on GOS monitor) it will remain so, until eithera ‘start of docking’ or cancellation (OFF) is made from the Operator Panel or the ‘ShutDown’ command is made from GOSMMI or the flight becomes to old; the defaultconfiguration considers a flight to be old when the time passes ETAD + 30 minutes.

5.5.3 Unsuccessful Docking

If for any reason the docking was unsuccessful, the GOS operator or bridge user shallmake a manual ‘Park On’ command in order to make it possible to process the nextdeparting flight. Thus, every docking attempt must end with PARKED status at DGS.





IOM Manual

GOS Gate Operating System Chapter 3. Operation: Appendix A


Document: US-AppA-GosRUH-Features Date: June 2008 Version: 1.0

OPERATION: APPENDIX A

GOS FEATURES

CONTENTS


1.

SCOPE .......................................................................................................................... 2

1.1 GENERAL ......................................................................................................... 2

2. GOS SYSTEM TOPOLOGY .......................................................................................... 2

2.1 GENERAL ......................................................................................................... 2

3. REDUNDANT SERVERS .............................................................................................. 2

3.1 GENERAL ......................................................................................................... 2

4. COMMUNICATION BETWEEN GOS AND DGS ......................................................... 2

4.1 GENERAL ......................................................................................................... 2

5.

OPERATING SYSTEM SOFTWARE ............................................................................ 2

5.1 GENERAL ......................................................................................................... 2

6. STANDARD FEATURES .............................................................................................. 2

6.1 GENERAL ......................................................................................................... 2

6.2 DOCKING MONITORING AND CONTROL ..................................................... 2

6.2.1

General ........................................................................................................ 2

6.3 GOS EVENT LOG FILES ................................................................................. 2

6.3.1 General ........................................................................................................ 2

6.4

AUTOMATIC UPLOAD OF SAFEDOCK DOCKING LOG FILES .................... 3

6.4.1 General ........................................................................................................ 3

6.5

AUTOMATIC UPLOAD OF SAFEDOCK CONFIGURATION FILES ............... 3

6.5.1 General ........................................................................................................ 3

7. SAFEDOCK MAINTENANCE ....................................................................................... 3

7.1 GENERAL ......................................................................................................... 3

8. INTERFACE TO EXTERNAL SYSTEMS ..................................................................... 3

8.1 FIS ..................................................................................................................... 3

8.2 NTP ................................................................................................................... 3



IOM Manual




1. SCOPE

1.1 GENERAL

This document is a detailed description of functional variations of the GOS system.The features described are related to the following categories:

(a) GOS system setup

(b) Operating system software

(c) Redundant servers

(d) Communication interface between GOS and DGS

(e) Standard GOS features

(f) Camera

(g) Connections to external systems

2. GOS SYSTEM TOPOLOGY

2.1 GENERAL

A GOS system layout can be found in the SY-AppA-GosAirport-Topology document.

3. REDUNDANT SERVERS

3.1 GENERAL

Redundant GOS servers are used to increase system reliability. A more detaileddescription can be found in the SY-AppB-GosAirport-Redundant document.

4. COMMUNICATION BETWEEN GOS AND DGS

4.1 GENERALDGS is connected to GOS by means of an Ethernet LAN.

5. OPERATING SYSTEM SOFTWARE

5.1 GENERAL

Server: Windows 2003

Workstation: Windows XP Pro

6. STANDARD FEATURES

6.1 GENERAL

This section describes standard features included in a GOS system.

6.2 DOCKING MONITORING AND CONTROL

6.2.1 General

The primary purpose of the GOS system is Docking Control and Monitoring. At anyGOS subsystem the airport layout with stands and docking systems can be displayedand monitored. The Docking Control and Monitoring function is fully explained in thechapter OPERATIONS of the IOM manual.

6.3 GOS EVENT LOG FILES

6.3.1 General

Event Log files are created once per day, and is used for statistics and the

maintenance of the DGS system.



IOM Manual




A docking procedure contains several events, which are stored with time stamps, forexample: DGS Ready; Active (aircraft, flight); Docking (aircraft, flight); Parked(aircraft, flight, Reg No).

The name of a log file will be the date of the day, and has the format YYMMDD.log

The files are stored automatically, one per day, and are stored for a configurableperiod of time. Default period is thirty-two days. After that it is automatically deleted.

The Event Logging facility is fully explained in chapter OPERATIONS of the IOMmanual.

6.4 AUTOMATIC UPLOAD OF SAFEDOCK DOCKING LOG FILES

6.4.1 General

Each docking in Safedock generates a docking log. The docking log will automaticallybe dumped to GOS at the end of each docking procedure, where it will be retained for30 days.


6.5.1 GeneralTo store a backup of each Safedock configuration, the configuration files (centrelineand gate configuration) will automatically be dumped to GOS from Safedock when theconfiguration has been updated in the Safedock.

7. SAFEDOCK MAINTENANCE

7.1 GENERAL

Maintenance on Safedocks can be performed from GOS by using the softwareSDCONFIG.EXE.


8. INTERFACE TO EXTERNAL SYSTEMS

8.1 FIS

The GOS system is connected to FIS to exchange flight information.

FIS will provide GOS with arrival and departure flight information and GOS will reportBlock On/Off events to FIS upon successful arrival/departure docking.

A more detailed description can be found in the FIS Interface Control document.

8.2 NTP

All GOS computers are synchronizing its time against the airport’s master clock.



IOM Manual






IOM Manual

GOS Gate Operating System Chapter 3. Operation: Appendix B


Document: US-AppB-GoRUH-AccessManager Date: June 2008 Version: 1.0

OPERATION: APPENDIX B

GOS ACCESS MANAGER

CONTENTS


1.

INTRODUCTION ........................................................................................................... 2

1.1 GOS ACCESS MANAGER ............................................................................... 2

2. INSTALLATION ............................................................................................................ 3

INSTALL GOS ACCESS MANAGER ............................................................... 3

3. MENUS AND COMMANDS .......................................................................................... 4

NAVIGATE MENUS AND COMMANDS ........................................................... 4

4. USING GOS ACCESS MANAGER ............................................................................... 7

START GOS ACCESS MANAGER AND LOGIN ............................................. 7

EDITING USERS GROUPS AND CREDENTIALS .......................................... 8

CONFIGURE USERS, GROUPS, STANDS AND CREDENTIALS ............... 10

5. MORE INFORMATION ................................................................................................ 12

5.1 DOCUMENTATION ........................................................................................ 12

5.2 VERSION ........................................................................................................ 12

5.3 REFERENCES AND TRADEMARKS ............................................................. 12

5.4 TERMINOLOGY ............................................................................................. 12

5.5 LANGUAGE .................................................................................................... 12



IOM Manual



1. INTRODUCTION

1.1 GOS ACCESS MANAGER

GOS Access Manager is a tool to manage user credentials, such as setting upadministration and user rights and privileges for airport personnel in a Gate OperatingSystem (GOS).

GOS Access Manager benefits to GOSusers are:

• Reduced lead times for systemchanges.

• Changes can be made for specificsite requirements.

• Strengthened ownership of thepurchased system with control oversystem configuration.

• Improved management efficiencywith internal resources and lesstraffic disturbance.

This document includes information how to install and use GOS Access Manager ona computer with Microsoft Windows XP.

Note: GOS Access Manager software releases are subject to the latest developmentimprovements and may differ to the information and image examples used in thisdocument.Software images and menu selections ( Ar ial Bold font) used in instructions areexamples from the software language used for creating this document, English UK.

These examples may therefore not to be localised in any translated revisions of thisdocument if the software is not available in the corresponding language fortranslation.




IOM Manual



2. INSTALLATION

GOS Access Manager is installed with a setup application, on a computer withWindows XP.

INSTALL GOS ACCESS MANAGER

1. Insert the installation CD into your computer disk drive and

open the CD.

2. Double-click Gosinstall.exe.

3. Select Install GOS Access Manager .

4. Press Start and follow the instructions that appear.

Note: Click Accept to install Microsoft .NET

Framework 2.0. This message does not appear if it is

already installed on your computer.




IOM Manual



3. MENUS AND COMMANDS

GOS Access Manager includes a number of menus, tabs, entry fields, commands andviews. Commands are based on standard Windows application commandsspecifically adapted for GOS Access Manager.

The following menus with commands are available:

NAVIGATE MENUS AND COMMANDS

Menus, tabs, commands Description Examples

File Menu command

Exit Close the program.

Database Menu command

Reread data from database Reload system configurationinformation.

About Program, version and more

information.

Click OK to close.

Users Tab views and commands

Existing users Select from a list of users to edit

or view information.

Edit user Entry fields and commands to

create, update and delete users.

User name Enter a user name.

Password Enter a user password.

Verify password Enter the same user password

for confirmation.

Create user Create a user with the

information in the entry fields.

Update selected user Select an existing user, edit user

information in the entry fields

and click to update.

Delete selected user Select an existing user and click

to delete.

Group membership View the groups to which a user

belongs.

Select user group Select an existing user, and use

to select from available user

groups to belong to.




IOM Manual




User groups Tab views and commands

Existing user groups Select from a list of user groups

to edit or view information.

Edit user group Entry fields and commands to

create, rename and delete user

groups.

Group name Enter a user group name.

Create group Create a group with the

information in the entry field.

Rename selected group Select an existing group, edit the

group name in the entry field

and click to rename.

Delete selected group Select an existing group and

click to delete.

Users in group View the users in the group.

Select users Select from existing users for

group membership.

Credentials for group Select from existing stand

credentials for the group.

Select credentials Select an existing group, and use

to select from available rights

for the group.

Stand groups Tab views and commands

Existing stand groups Select from a list of stand

groups to edit or view

information.

Edit stand group Entry fields and commands to

create, rename and delete stand

groups.

Group name Enter a stand group name.

Create group Create a stand group with theinformation in the entry field.

Rename selected group Select an existing stand group,

edit the stand group name in the

entry field and click to rename.

Delete selected group Select an existing stand group

and click to delete.

Stands in g roup View the stands in the stand

group.

Select stands Select from existing stands for

stand group membership.




IOM Manual




Stand credentials Tab views and commands

Existing stand credentials Select from a list of stand

credentials to edit or view

information.

Credential name Enter a stand credential name.

Create stand credential Create a stand credential with

the information in the entry

field.

Rename selected credential Select an existing stand

credential, edit the stand

credential name in the entry

field and click to rename.

Delete credential Select an existing standcredential and click to delete.

Included stands Select the tab for a list of

existing stands credentials for

stand group membership.

Select stands Use to select stands for

included stands.

Included stand groups Select the tab for a list of stand

groups to edit or view

information.

Select stand groups Use to select stand groups forincluded stand groups.

Included credential types Entry fields and commands to

create, rename and delete

stand groups.

Select credentials Use to select credentials for

included credential types.




IOM Manual



4. USING GOS ACCESS MANAGER

GOS Access Manager is designed with an intuitive user interface and logicalfunctionality.

START GOS ACCESS MANAGER AND LOGIN

1. Start GOS Access Manager

• Double-click on the desktop icon or

• Go to Start\Programs\GOS Access Manager to start the

program.

2. Login

Enter information:

A. User name

B. Password

C. Server , if required or different from localhost .




IOM Manual



EDITING USERS GROUPS AND CREDENTIALS

1. Create update or delete users

• Click the Users tab.

Create a new user:

A. Enter a new user name, password and verify the password.

B. Click Create user .

Update an existing user:

A. Select an existing user.

B. Change information in the entry fields.

C. Click Update selected user .

Note: When renaming a user only, no new password information

is entered for the password to remain the same.

Delete a user:

A. Select an existing user.

B. Click Delete selected user .

2. Create rename or delete user groups

• Click the User groups tab.

Create a new user group:

C. Enter a new group name.

D. Click Create group.

Rename an existing user group:

A. Select an existing user group.

B. Change the name in the entry field.

C. Click Rename selected group.

Delete selected group:

A. Select an existing user group.

B. Click Delete selected group.




IOM Manual



3. Create rename or delete stand groups

• Click the Stand groups tab.

Create a new stand group:

A. Enter a new stand group name.

B. Click Create group.

Rename an existing stand group:

A. Select an existing stand group.

B. Change the name in the entry field.

C. Click Rename selected group.

Delete selected group:

A. Select an existing stand group.B. Click Delete selected group.

4. Create rename or delete credentials

• Click the Stand credentials tab.

Create a new stand credential:

A. Enter a new stand credential name.

B. Click Create stand credential.

Rename existing stand credentials:

A. Select an existing stand credential.B. Change the name in the entry field.

C. Click Rename credential.

Delete selected credential:

A. Select an existing stand credential.

B. Click Delete credential.




IOM Manual



CONFIGURE USERS GROUPS STANDS AND CREDENTIALS

1. Select groups membership

A. Click the Users tab.

B. Select an existing user group.

C. Click Select user groups .

• From Available user groups, click to select or

• From Selected user groups, click to remove.

D. Click Close when completed.

2. Select users for a group

A. Click the User groups tab.

B. Select an existing user.

C. Click Select users.

• From Available users , click to select or

• From Selected users, click to remove.


3. Select credentials for a user group

A. Click the User groups tab.

B. Select an existing user group.

C. Click Select credentials.

• From Available credentials , click to select or

• From Selected credentials, click to remove.


4. Select stands for a stand group

A. Click the Stand groups tab.

B. Select an existing stand group.

C. Click Select stands.

• From Available stands, click to select or

• From Selected stands, click to remove.





IOM Manual



5. Select individual stands for a credential

group

A. Click the Stand credentials tab.B. Select an existing stand credential.

C. Click the Included stands tab, in the lower window.

D. Select an existing stand from the list.

E. Click Select stands.

• From Available stands, click to select or

• From Selected stands, click to remove.

F. Click Close when completed.

6. Select stand groups for a credential

group

A. Click the Stand credentials tab.

B. Select an existing stand credential.

C. Click the Included stand groups tab, in the lower

window.

D. Select an existing stand group from the list.

E. Click Select stand g roups.

• From Available stand groups , click to select or

• From Selected stand groups , click to remove.


7. Select credentials for a credential group

A. Click the Stand credentials tab.

B. Select an existing stand credential.

C. Click the Included credential types tab, in the lower

window.

D. Select an existing credential type from the list.

E. Click Select credentials.

• From Available credentials , click to select or

• From Selected credentials, click to remove.





IOM Manual




5. MORE INFORMATION

5.1 DOCUMENTATION

This document aims to give personnel an insight into the benefits of using the GOS

Access Manager tool and a guide to general use that is logical and intuitive.

5.2 VERSION

This document is revised according to change descriptions with full alphabeticalrevisions for external use.

Version Date Prep. Status App. Change Descript ion

1.0 21-1-2008 TW Approved PL First Edition:

For External Use.

Note: Safegate Group is responsible for providing updates, as available.

5.3 REFERENCES AND TRADEMARKS

GOS, GOS Access Manager are trademarks of Safegate Group.

Other products and company names mentioned herein may be the trademarks of theirrespective owners.

Any rights not expressly granted herein are reserved. All illustrations and images arefor illustration only and may not accurately depict the actual product.

5.4 TERMINOLOGY

This document includes a selection of terms, words and abbreviations.

Term or word Abbreviation Comment

Gate Operating system GOS

Technical Writer TW

Product Leader PL

5.5 LANGUAGE

Original documentation is created in English (U.K.).

Note: Software images and menu selections ( Ar ial Bold font) used in instructions areexamples from the software language used for creating this document, English UK.These examples may therefore not to be localised in any translated revisions of this

document if the software is not available in the corresponding language frotranslation.

For more information, see www.safegate.com.

http://www.safegate.com/




IOM Manual

GOS Gate Operating System Chapter 3. Operation: Appendix C


Document: US-AppC-GosRUH-Reporter Date: June 2008 Version: 1.0

OPERATION: APPENDIX C

GOS REPORTER

CONTENTS


1.

INTRODUCTION ........................................................................................................... 2

1.1 GOS REPORTER ............................................................................................. 2

1.2 DOCUMENTATION .......................................................................................... 2

2. INSTALLATION ............................................................................................................ 3

INSTALL GOS REPORTER ............................................................................. 3

3. MENUS AND COMMANDS .......................................................................................... 4

NAVIGATE MENUS AND COMMANDS ........................................................... 4

USE GOS REPORTER ..................................................................................... 5

4.

MORE INFORMATION .................................................................................................. 7

4.1

DOCUMENTATION .......................................................................................... 7

4.2

VERSION .......................................................................................................... 7

4.3

REFERENCES AND TRADEMARKS ............................................................... 7

4.4 TERMINOLOGY ............................................................................................... 7

4.5 LANGUAGE ...................................................................................................... 7



IOM Manual




1. INTRODUCTION

1.1 GOS REPORTER

GOS Reporter is a tool for airport personnel using a Gate Operating System (GOS) togenerate reports. Reports are generated by making queries against the GOS log.

The following common queries are supported:

• Statuses for all gates/the status of a specific gate between two dates(from/to). The information is sorted and/or filtered by status:

(a) Aircraft

(b) Flight

(c) Tow-in

(d) Gate

(e) Error type

• Errors for all gates/a specific gate between two dates (from/to). Theinformation is sorted and/or filtered by error type.

• Blocks On/Off for all gates/a specific gate between two dates (from/to). Theinformation is sorted and/or filtered by blocks on/off.

• Free text searches in error messages.

Note: Other queries can be supported, if required.

1.2 DOCUMENTATION

This document includes information how to install and use GOS Reporter on acomputer with Microsoft Windows XP.

Note: GOS Reporter software releases are subject to the latest developmentimprovements and may differ to the information and image examples used in thisdocument.Software images and menu selections ( Ar ial Bold font) used in instructions areexamples from the software language used for creating this document, English UK.These examples may therefore not to be localised in any translated revisions of thisdocument if the software is not available in the corresponding language fortranslation.



IOM Manual



2. INSTALLATION

GOS Reporter is installed with a setup application, on a computer with Windows XP.

INSTALL GOS REPORTER

1. Insert the installation CD into your computer disk drive and

open the CD.

2. Double-click GosReporterSetup.exe.

3. Click Next to continue, follow the instructions that appear.

Note: Click Accept to install Microsoft .NET

Framework 2.0. This message does not appear if it isalready installed on your computer.

4. When Installation Complete appears, Click Close.




IOM Manual



3. MENUS AND COMMANDS

GOS Reporter includes a number of menus, entry fields, commands and views.Commands are based on standard Windows application commands specificallyadapted for GOS Reporter.

The following menus with commands are available:

NAVIGATE MENUS AND COMMANDS

Menus, commands Description Examples

File

New Query

Open Query

Exit

Create a new log view.

Open a previously saved view.

Close the program.




IOM Manual



USING GOS REPORTER

GOS Reporter is designed with an intuitive user interface and logical functionality.

USE GOS REPORTER

1. Start GOS Reporter

• Double-click on the desktop icon or

• Go to Start\Programs\Safegate\GOS Reporter to start

the program.

2. Login

A. Enter login information to start the program.

• User name.

• Password.

• IP Address or host name of Server 1 and 2.

B. Click OK.

Note: At first start up the Server field is empty. User name,

password and server information is verified with a users table in

the GOS database. When verified GOS Reporter starts.

If only one GOS server is used, the Server 2 field is left empty.

3. Create and use a log view query)

A. Select File, Log View.

B. Select From: and To: dates for the query, if required.

C. Select Main type.

D. Select Sub type, if required.

E. Select Ai rcraft, if required.

F. Select Gate, if required.

G. Select Flight, if required.

H. Click Execute query to create the log view.

The following options are also available:

• Preview – preview the current log before printing.

• Print – print the current log view.

• Open query – open a previously saved log view.

• Save query – save a log as a file (.que) in a folder:

C:\Program Files\Safegate\GOS Reporter\Query.

• Export results – export a log to a file (.txt) in a folder: C:\Program Files\Safegate\GOS Reporter\Expor t.

Note: For more information, see the following examples.




IOM Manual


4. Log view examples

• Open a previously saved query.

• Save the current query.

• Change a filter for a query.

• Change a sub type for a query.

• Export a query as a (.txt) file.





IOM Manual




4. MORE INFORMATION

4.1 DOCUMENTATION

This document aims to give personnel an insight into the benefits of using the GOSReporter program and a guide to general use that is logical and intuitive.

4.2 VERSION

This document is revised according to change descriptions with full alphabeticalrevisions for external use.

Version Date Prep. Status App. Change Descript ion

1.0 12-2-2008 TW Approved JW First Edition:

For External Use.

Note: Safegate Group is responsible for providing updates, as available.

4.3 REFERENCES AND TRADEMARKS

GOS, GOS Reporter are trademarks of Safegate Group.

Other products and company names mentioned herein may be the trademarks of theirrespective owners.

Any rights not expressly granted herein are reserved. All illustrations and images arefor illustration only and may not accurately depict the actual product.

4.4 TERMINOLOGY

This document includes a selection of terms, words and abbreviations.

Term or word Abbreviation Comment

Gate Operating system GOS

Technical Writer TW

Product Leader PL

4.5 LANGUAGE

Original documentation is created in English (U.K.).

Note: Software images and menu selections ( Ar ial Bold font) used in instructions areexamples from the software language used for creating this document, English UK.These examples may therefore not to be localised in any translated revisions of this

document if the software is not available in the corresponding language frotranslation.

For more information, see www.safegate.com.





IOM Manual






IOM Manual

GOS Gate Operating System Chapter 4. Maintenance


Document: MA-GosRUH-Maintenance Date: June 2008 Version: 1.0

CHAPTER 4

MAINTENANCE

CONTENTS


1.

INTRODUCTION ........................................................................................................... 2

1.1 SCOPE .............................................................................................................. 2

1.2 MAINTENANCE ON THE ETHERNET LAN..................................................... 2

1.3 GENERAL PRECAUTIONS .............................................................................. 2

2. CORRECTIVE MAINTENANCE ................................................................................... 2

2.1 FAULT FINDING AND RECTIFICATION ......................................................... 2

2.2 REPLACEMENT OF MALFUNCTIONING UNITS ........................................... 2

2.3 SOFTWARE INSTALLATION ........................................................................... 2

3.

PREVENTIVE MAINTENANCE .................................................................................... 3 3.1 GENERAL ......................................................................................................... 3

4. FAULT FINDING GUIDE ............................................................................................... 3

4.1

COMM ERROR ON ALL STANDS ................................................................... 3

4.1.1 General ........................................................................................................ 3

4.1.2 Step-by-step troub leshoot ing ................................................................... 3

4.2 COMM ERROR ON A SINGLE DGS - LAN CONNECTION ............................ 3

4.2.1 General ........................................................................................................ 3

4.2.2

Step-by-step troub leshoot ing ................................................................... 3

4.3 COMM ERROR ON A SINGLE DGS – CURRENT LOOP MODEM ................ 4

4.3.1

General ........................................................................................................ 4 4.3.2 Step by step trouble shooting .................................................................. 4

4.4 HARD DISK/OPERATING SYSTEM FAILURE ................................................ 5

4.4.1 General ........................................................................................................ 5

4.4.2 Step by step trouble shooting .................................................................. 5

4.5 NTP CONNECTION ERROR ........................................................................... 5

4.5.1

General ........................................................................................................ 5

4.5.2 Step by step trouble shooting .................................................................. 5

4.6 GOS HMI FAILS TO START ............................................................................. 5

4.6.1 General ........................................................................................................ 5

4.6.2

Step by step trouble shooting .................................................................. 5

APPENDICES:

GOS Fault Finding Guide Appendix A



IOM Manual




1. INTRODUCTION

1.1 SCOPE

This document is a maintenance description of a Central Docking Control System,also called Gate Operating System/GOS. The system topology is described in Appendix A of the System Description and includes both GOS servers andWorkstations with connections to external system via an Ethernet LAN.

This description includes:

• Corrective Maintenance

• Preventive Maintenance

• A Fault Finding Guide

1.2 MAINTENANCE ON THE ETHERNET LAN

Safedock Installation Appendix C is a maintenance instruction for the Ethernet LANused to communicate with Docking Systems and external computer systems.

1.3 GENERAL PRECAUTIONS

The GOS system is built with a standard type of PC computers, which need very littlemaintenance.

Before commencing any maintenance activity, the following precautions must beconsidered:

CAUTION: PROTECTION AGAINST ELECTROSTATIC DISCHARGE

The transfer of static electricity causes ESD damage when electronic components arehandled. It’s essential to protect components from electrostatic discharge to avoiddamage and extra costs in connections with service and production. Therefore

• All ESD- sensitive materials must be stored in ESD- safe area.

All ESD- sensitive components must be stored in protective packages.

Apply a conductive band around your wrist and connect it to ground before touchingany electronic component.

WARNING: ISOLATE THE POWER SUPPLY PRIOR TO UNDERTAKING ANYMAINTENANCE ACTIVITY!

2. CORRECTIVE MAINTENANCE

2.1 FAULT FINDING AND RECTIFICATION

The Docking Guidance Central Computer, GOS, is not executing any run time

diagnostic tests. System operation is monitored from the GOS Workstations, and afailure in the Server or LAN will be reported as a COMM Error of the Docking System.Possible causes of other errors and the recommended actions to be taken arepresented in section 4.

2.2 REPLACEMENT OF MALFUNCTIONING UNITS

The GOS system is built using conventional rack mounted PC computers with a backplane and plug-in electronic boards.

It is supposed that the replacement of electronic boards of these PCs is anelementary type of maintenance work, which is not described in this manual.

2.3 SOFTWARE INSTALLATION

Chapter 2 of the Manual covers the software installation procedures. Please refer to

that chapter, when reinstalling or upgrading GOS software.



IOM Manual




3. PREVENTIVE MAINTENANCE

3.1 GENERAL

The GOS system is built with a standard type of PC computers, which need very littlepreventive maintenance.

Database housekeeping is done automatically.

Three times a year the following parameters should be checked:

- Check Memory Usage by the Windows NT/2000 Task Manager.

- Check available hard disk space. More than 1GB shall always be available.

If any anomalies are found, system shall be restarted and old log files deleted.

4. FAULT FINDING GUIDE

4.1 COMM ERROR ON ALL STANDS

4.1.1 General

If system shows communication error with all docking systems, the problem mostlikely resides on the GOS Server, which is handling the communication.

The reason might also be that the Workstation is no longer connected to the GOSServer.

4.1.2 Step-by-step troubleshooting

(a) Make sure PC is running

(b) Check Network according to Safedock Installation Appendix C.

• Check network cable and network adapter board.

Make a PING test against any available PC on the network. If ping getsthrough, the hardware’s good.

Check the service Goskrnl:

Stop the service Goskrnl, and restart Goskrnl.exe from Windows’ Explorer. Ifcommunication is established with DGS:s, it’s an indication that the servicesettings are incorrect. Stop Goskrnl.exe, and reinstall the Service according tomaintenance manual.

4.2 COMM ERROR ON A SINGLE DGS - LAN CONNECTION

4.2.1 General

When GOS is connected to a Safedock system, the GOS polls Safedock for itscurrent status continuously. Thus, if Safedock doesn’t receive any questions fromGOS, Safedock will never respond.

4.2.2 Step-by-step troubleshooting

• Confirm (at apron) that DGS is running

• Check Ethernet Converter in DGS:

Find out the IP Address for the converter (lock in the GOS.INI file). Removeconverter from DGS, and connect it to a GOS Maintenance PC with acrossover cable. Perform a PING test against the converter. If the converterreplies, it’s OK. This test also verifies the functionality of the PC.

If the PC and converter are OK, the problem might reside in the network cablebetween PC and DGS.

• Check Network according to Safedock Installation Appendix C.

• Check Motherboard/configuration and cables in DGS:

The mother board is equipped with LED:s (D2-D10) for monitoring thecommunication. Two of these LED:s are for GOS communication. Check‘transmit‘ and ‘receive’ if they are blinking. If none is blinking, this could



IOM Manual




indicate that the motherboard is broken or there is a broken cable betweenMotherboard and converter. If only the ‘receiver’ is blinking, this indicates thatSafedock receives signals but doesn’t recognise them. This is a typicalscenario when the CPU is replaced and the Stand is configured with anincorrect COM ID.

4.3 COMM ERROR ON A SINGLE DGS – CURRENT LOOP MODEM

4.3.1 General

When GOS is connected to a Safedock system, the GOS polls Safedock for itscurrent status continuously. Thus, if Safedock doesn’t receive any questions fromGOS, Safedock will newer respond.

With this in mind troubleshooting should always start on the GOS side and work itsway towards the Safedock and finally back to GOS again.

4.3.2 Step by step trouble shooting

On the modem, there are LED:s, monitoring DCD (data carrier detect), Transmit andReceive signals.

• At GOS: Start by checking if the ‘Transmit’ LED is blinking. If it is, the GOS issending data to the modem. If no blinking, problem might reside somewherebetween the PC and the modem.

• Check Patch cable and cable between the PC and the Concentrator.

• Make a LOOP BACK test between the PC and the Concentrator. This isdescribed in the GOS software installation manual (loop back plug required).

• Make LOOP BACK test between PC and modem.

Having come this far without any problems, it’s almost certain that communicationbetween PC and Modem is OK. Next step will be to verify how far the ‘transmit’ signalgoes.

• Check DCD LED. If it is lit on GOS side and on Safedock side, it is a goodindication that the communication line between the two modems is OK.

• On Safedock: Check ‘receiver’ LED. If no blinking, the problem might be themodem or the line. Start by replacing the modem. If there is still no blinking, thecommunication line might be broken. When measuring a communication line, it ispreferred to measure the resistance on the line (join the two braches at theremote end; resistance should be between 10-400 ohms depending on length ofline).

• The mother board is equipped with LED:s as well(D2-D10). Two of these LED:sare for GOS-DGS communication. Check ‘transmit‘ and ‘receive’ if they areblinking. If not, the motherboard might be broken or the cable betweenMotherboard and modem fails. If only the ‘receiver’ LED is blinking, Safedock

receives signals but doesn’t recognise them. This is a typical scenario when theCPU is replaced and the stand is configured with incorrect COM ID.

If ‘receiver’ and ‘transmitter’ are blinking on the motherboard, go on to check ‘transmit’ LED onmodem. If blinking, measure resistance on the ‘transmit’ line.



IOM Manual




4.4 HARD DISK/OPERATING SYSTEM FAILURE

4.4.1 General

If a PC fails to start up or suddenly goes down, it’s an indication that the hard drive orthe operating system is corrupted.


• PC goes down and fails to restart:

Replace the hard disk, and reinstall operating system according to installationmanual.

If it can be verified that the hard disk is OK only reinstall the operating system.

Reinstall GOS application software

4.5 NTP CONNECTION ERROR

4.5.1 General

If the computer is unable to synchronize its time against the NTP server or masterclock, a system message will be planted in Windows’ system log.

Note! If two synchronization sources are used there will be two messages in the log


• Verify the network connection to the master clock:

Make a PING test against the NTP server. If ping gets through, the hardwareworks fine.

Verify that the master clock is functioning correctly:

Verify this by checking the functionality of another system, which uses thesame synchronization software and source/master clock to sync from.

Reconfigure the time service according to the installation manual.

4.6 GOS HMI FAILS TO START

4.6.1 General

For GOS HMI to run, the program GOS kernel (GOSkrnl) must run.

If GOS HMI is started, and the airport layout is displayed on screen for short period oftime, it’s a good indication that Goskrnl.exe is not running.


• Check the service Goskrnl:

Stop the service Goskrnl, and restart Goskrnl.exe from Windows Explorer. If GOSHMI starts up now, it’s an indication that the service settings are incorrect for

autostart. Stop Goskrnl.exe, and reinstall the Service according to maintenancemanual.



IOM Manual






IOM Manual

GOS Gate Operating System Chapter 4. Maintenance: Appendix A


Document: MA-AppA-GosRUH-FaultFindGuide Date: June 2008 Version: 1.0

MAINTENANCE: APPENDIX A

GOS

FAULT FINDING GUIDE

GOS Server

Comm error, All Concentrators

Symptom Possible Cause Action to Rectify

‘Comm error’ on all DGS’s. Concentrators not running. Start the concentrators.

Network connection failed. Check network connectioncable, network, networkadapter board.

Comm error, Concentrator


‘Comm error’ on all DGS’sconnected to the concentrator.

Concentrator not running. Start the concentrator.

Concentrator not accessiblethrough network.

See GOS Concentrator.

Comm erro r, DGS


‘Comm error’ on a single DGS. See GOS Concentrator. See GOS Concentrator.

AODB connect ion error

Symptom Possible Cause Action to RectifyEntry in GOS log file:

HKSFD – Or aGos- St andLogon/ connect - ORA- 12154:

TNS: coul d not r esol ve GOS

GOS unable to access network. Check network connectioncable, network, networkadapter board.

Entry in GOS log file:HKSFD – Or aGos -

TFG/ connect t o AODB_P_1,AODB_P_2,

AODB_S_ 1, AODB_S_ 2.

GOS unable to connect to AODB server.

Check AODB servers.



IOM Manual




DGS error


‘Error nn’ reported at stand. DGS error See fault finding, DGS.

NTP connection error


Entry in NT Event Viewer Application Log:

NTP Could not connect

NTP client is unable to connectto NTP server.

Check network connectioncable, network, networkadapter board.

Hard disk failure


Entry in NT Event ViewerSystem Log:

Bad sectors ‘diskName’.

Hard disk failure. Replace the hard disk.



IOM Manual




GOS Concentrator

Comm error , Server


Comm error on all DGS’s notconnected to this concentrator. Concentrator not accessiblethrough the network. Check network connectioncable, network, networkadapter board.

Comm erro r, DGS


Comm error on a single DGS. DGS not running. Activate DGS.

DGS modem failure. Check/replace DGS modem.

Communication line error. Check/Repair communicationline.

Serial port (Rocket port)connector board failure.

Perform serial port loop backtest according to Rocket portdocumentation. Replaceserial port connector board.

Serial port (Rocket port) boardfailure.

Replace serial port board.

DGS error











IOM Manual




Hard disk failure







IOM Manual




GOS Workstation (ACC)

Comm error , Server


Comm error on all DGS’s. Workstation not accessiblethrough the network. Check network connectioncable, network, networkadapter board.

Comm erro r, DGS


‘Comm error’ on a single DGS. See GOS Concentrator. See GOS Concentrator.

DGS error









Hard disk failure







IOM Manual


SFDUPD connection error


Error message at start ofSFDUPD program:

TNS: Unable to connect todestination Alias: GOS.

Workstation unable to connectto database at GOS server. Check network connectioncable, network, networkadapter board.

Documents

GOS Manual