Gos Manual 2hnt

Software (iii) Press START. (iv) Follow on-screen instructions and accept default settings during the installation.

4.3.4

GOS Access Manager Setup Whenever GOS HMI uses centralized access handling (log on to GOSHMI required to get access to the system) the tool GosAccessManager.exe is used when creating system s. Install the software as follows: (i) Start the program Gosinstall.exe (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 is recommended that maintenance software is only installed on a separate GOS Maintenance computer specifically dedicated for Safedock maintenance. Install the software as follows: (i) Start the program Gosinstall.exe (ii) Select Install SDK Maintenance Software (iii) Press START

©Safegate Group Document: IN-GosRUH-Installation

Page 11 of 18 Date: June 2008

Version: 1.0

IOM Manual GOS Gate Operating System

Chapter 2. Installation

4.4

SHARED DIRECTORIES Directories that shall be shared will become shared automatically when the GOS software is installed. The directories to be shared are defined in GOSINSTALL.INI. Note: If redundant servers are used, the running the Goskrnl service (normally the ) must have full rights to the ‘GosShared’ share (location: \GosShared. Refer to the Windows operating system for a description of how to assign 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 GOS Concentrator 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 RS422 communications. The project can have any combination of these devices or individual port configuration. However, the individual port configuration MUST match that as required for the serial communication signaling to the DGS

4.5.1

Hardware Installation Each device is connected to a local network switch or router via Ethernet patch-cable on the DeviceMaster-RTS Ethernet-port labeled “UP”. Alternately, a DeviceMasterRTS unit can be connected directly to the GOS-Server or a laptop computer to the Ethernet-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 document manual “RTS_Guide.pdf”, located in the “DeviceMaster-RTS” folder on the GOS Software Installation CD-ROM. The document describes how to install the device drivers and configure the DeviceMaster-RTS devices to assign its ports as standard Windows 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 ed from the internet by searching for “Adobe Acrobat Reader ” and locating the Adobe website). General Configuration Settings: Below settings are done in the Windows “Device Manager” under the “Multi-port serial adapters” by double-clicking the device to configure. 1. Configure starting COM PORT to be 5 for the first serial HUB. Other HUBs shall start at next available port (COM1 through COM4 should be excluded from these setups). 2. When the GOS-Server and the DeviceMaster are on the same network segment, it is recommended to configure the DeviceMaster-RTS to use MACaddressing for communications between it and the GOS-Server. When the GOS server and the DeviceMaster reside on different network segments, the unit must be setup to use T-IP addressing. The latter also applies when two or more network cards are used in the server. 3. KeepAlive Timeout Period: 15

©Safegate Group

Page 12 of 18 Document: IN-GosRUH-Installation

Date: June 2008

Version: 1.0



4.6

COM-PORT TEST Every COM port can be tested with a ‘Loop Back’ test. A loop back plug shall be connected to the target port to be tested at the DeviceMaster-RTS unit (typically located 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 result of the test will be shown on the screen (e) Test a RS422-port via the menu selection “Port/ Send and Receive Test Data” (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 sub stations, i.e. server and the workstation. The installation program installs the GOS Kernel service automatically when the software is installed.

4.7.2

Configuring the GOS Kernel Service If configuring a GOS server and redundant servers are being used, the service must be configured to be started by the local and not the Local System , which is default (the servers log on to each other and this cannot be accomplished if the service is configured to be started by the Local System ). Configuration can be done as follows: (i) Enter Control (ii) Double click the ‘istrative 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 ’ (vii) Press ‘Browse’, select the ‘’ and press ‘OK’ (viii) Type in the current and confirm it. (ix) Press ‘OK’ and exit. Note: above must also be done whenever the for the is being changed, otherwise the service will fail to start at next restart.

4.7.3

ing 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.



Version: 1.0



4.8.2

Installing Camera Software To install the component; start Gosinstall.exe and select the ‘Install AXIS Camera Control’ option and press START. Follow screen instructions and accept default settings.

4.8.3

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

©Safegate Group


Date: June 2008

Version: 1.0



4.9

RIGHTS AND ISTRATION

4.9.1

General Following is a table describing which s and s to be created in the system and on which computers. The installation program will be used to create the s except the ‘’, which is automatically created during the installation of Windows. Computer: Name: : GOS_SERVER1: GOS_SERVER2: GOSWS_MONITOR: GOSWS_MONITORDOCK:

gos

dgsmaint

manager X X X X

gos X X X X

dgsmaint X X X X

The “” is automatically created on every GOS computer when Windows 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 . The “gos” will have the possibility to run the GOS-application (Monitoring or Docking Control and Monitoring) from the Workstation/Workstations. The “dgsmaint” will have the possibility to perform central maintenance on each Safedock system through GOS. Note: To increase system reliability, do not configure Auto Logon on GOS-Server computers. 4.9.2

Creating Windows s The necessary s for the GOS system can be created with the installation program. See above table. The installation program will read the configuration for the PC from the file “GosInstall.INI”. The specified will then be created, and the necessary rights will be set on the configured directories. During the installation procedure, a series of batch files are run during the installation process. In case of any error during the installation the batch files will halt, and the can study the output messages on the screen. To Create s: (i) Start Gosinstall.exe from the CD ROM (ii) Select ‘Setup s’ (iii) Press Start (iv) Select the computer to create s for. The program will create s, set rights and display created s once finished. Note: If redundant servers are used, the running the Goskrnl service (normally the ) must have full rights to the ‘GosShared’ share (location: \GosShared. Refer to the Windows operating system for a description of how to assign rights to a network share.

4.9.3

Creating GOSHMI s A set of application s, controlling the access to the GOS system, can be created using the GosAccessManager tool. Refer to the GosAccessManager documentation for a detailed description of how to use this tool.



Version: 1.0



4.10

CONFIGURING AUTO LOGON Auto Logon can be configured on Workstations if desired. The installation program can 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 Windows 2000 built-in time synchronization system called Windows Time Service. The GOS computers will synchronize its time against the Airport master clock if one exists.

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 to sync. (vi) Press APPLY to enter the information into the registry. (vii) Start the service again by pressing START SERVICE (might take a while), and finish by pressing EXIT. The time synchronization can be verified by changing the system time on the computer, and then restart the PC. The system time shall be synchronized to one of the synchronization sources after restart. Note: Other NTP options will not work with Windows XP and 2003 Server OS.

©Safegate Group


Date: June 2008

Version: 1.0



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 the application in different ways does this.

5.2.1

ing the GOS.INI file Configuration If changes have been made to the GOS.INI file or starting the application for the first time, it is recommended to start the GosKrnl.exe program in a non-service mode. Any serious error to the configuration will cause a dialog box to pop up with an error message 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 the configuration is OK.

5.2.2

ing the Gos Kernel Service Set-up To that the configured to start the service is able to do so, the service can be manually started from the service . If the service starts without an error message the configuration is OK.

5.2.3

ing the Automatic Service Start-up Since GosKernel is running as a service, it shall start up automatically whenever the PC is rebooted. To this, reboot PC, log on to Windows and start the GOSMMI application. 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 the C:\GOS” folder accessed using ‘Windows Explorer’ or via shortcut-link on the Windows Desktop if found. The GOS MMI will show a screen layout of the airport where the DGS gates are located along with their status (if all is configured and operating properly).

5.2.4

ing File Synchronization Between Servers The GOS servers will synchronize configuration files such as docking logs and Safedock configuration files during operation. The Standby server will be notified of any file updates taking place on the Active server and automatically copy them to itself. Do as follows to that synchronization works. (i) Stop Standby server and remove the files in folder \GosShared. (ii) Start the Goskrnl service on the Standby server. (iii) that files are copied from the Active server. Note: it might take about 20 seconds before file synchronisation starts. Possible causes for failure: (i) Possibly incorrect IP-Address assignment between the servers – Check GOS.INI. (ii) GosKrnl service is being run by the Windows System – set it up to be run by the or equal . (iii) GosKrnl service does not have full access rights to the network share ‘GosShared’ – grant full access.



Version: 1.0



5.3

VERIFICATION OF DATABASE SOFTWARE

5.3.1

GOS Database Connection Test To that GOS can access the Database an arriving flight can be inserted into the database. 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. This verifies that GOS can connect to the database and process flights.

5.4

VERIFICATION OF SAFEDOCK CONFIGURATION SOFTWARE

5.4.1

Connection Test To that the “Stand Configuration Software” (or “SdConfig.exe”) can be connected to a Safedock/DGS through the GOS, start the “SdConfig.exe” program and perform a REMOTE connection to a known Stand/Gate-ID. To do this, select the REMOTE mode and set the IP-Address of the GOS-Server as well as the Stand/GateID 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).

©Safegate Group


Date: June 2008

Version: 1.0


Chapter 2. Installation: Appendix A INSTALLATION: APPENDIX A GOS SYSTEM CONFIGURATION CONTENTS

Section

Description

Page No.

1.

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

2. 2.1 2.2 2.3 2.4 2.5 2.5.1 2.5.2 2.6

GOS CONFIGURATION ............................................................................................... 2 GENERAL ......................................................................................................... 2 GENERAL APPLICATION SETTINGS ............................................................. 3 AIRCRAFT IN SYSTEM.................................................................................... 4 AIRCRAFT AT STAND CONFIGURATION ...................................................... 5 CHANGING THE IP ADDRESS ON A GOS SERVER ..................................... 6 Required Changes in the Server’s INI file ............................................... 6 Required Changes in the Workstation’s INI file...................................... 6 CHANGING THE IP ADDRESS ON A WORKSTATION.................................. 6

3. 3.1 3.2 3.2.1 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5

STAND NAME CONFIGURATION ............................................................................... 7 GENERAL ......................................................................................................... 7 SAFEDOCK CONFIGURATION ....................................................................... 7 Com Id Configuration ................................................................................ 7 GOS INI FILE CONFIGURATION .................................................................... 7 General ........................................................................................................ 7 GOS/Safedock Communication................................................................ 7 GOS HMI Stand Name ............................................................................... 9 Aircraft at Stand Configuration ................................................................ 9 Miscellaneous Sections ............................................................................ 9

4. 4.1 4.2 4.2.1 4.2.2 4.2.3

IATA CODE AND AIRCRAFT CONFIGURATION ..................................................... 10 GENERAL ....................................................................................................... 10 GOS INI FILE CONFIGURATION .................................................................. 10 Updating IATA/ICAO codes .................................................................... 10 Updating the Aircraft Menu..................................................................... 11 Aircraft at Stand Configuration .............................................................. 11

5. 5.1 5.2

INTERLOCK CONFIGURATION ................................................................................ 12 GENERAL ....................................................................................................... 12 CONFIGURATION EXAMPLES ..................................................................... 13

6. 6.1 6.2 6.3

CAMERA CONFIGURATION ..................................................................................... 14 IP ADDRESS CONFIGURATION ................................................................... 14 PICTURE VIEWING ........................................................................................ 14 PICTURE LOGGING ...................................................................................... 14

©Safegate Group Document: IN-AppA-GosRUH-SystemConfig


Version: 1.0


Chapter 2. Installation: Appendix A

1.

SCOPE This document describes the maintenance of the GOS.INI file, which is unique for every GOS PC. From this file, all GOS related applications get their parameters at start-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 modified by the . 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 more configuration settings for the system. Each setting consists of an ItemName to identify the 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, telling about the file version, changes that have been made and when they were made. 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 ignore the line, e.g. ;TIME_INFO =UTC (e) For changes to take affect, the GOSKRNL and GOSHMI applications must always be restarted.

©Safegate Group

Page 2 of 14 Document: IN-AppA-GosRUH-SystemConfig

Date: June 2008

Version: 1.0


2.2


GENERAL APPLICATION SETTINGS The section APPLICATION controls several functions of the system. Item Name

Value

Description

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 on screen or not. If NO is configured, the status button will only appear on screen when a status change occurs, and disappear when a confirms the event.

STDBY_VISIBLE=

YES NO

Only relevant if SYSTEMSTATUS =YES. Whether to display ‘Standby Server’ button on screen or not. If NO is configured, the status button will only appear on screen when a status change occurs, and disappear when a confirms 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 LTC format. If neither UTC nor LTC is configured, the time will not be displayed at all.

OPERATOR=

YES NO YES NO

Whether to allow PARK ON/OFF and SHUT DOWN from GOS

ALLOWSTARTDOCK=

ALLOWACTIVATE=

YES NO

SEND_RAMP_COMMAND

YES NO YES NO YES NO

SEND_FREE_TEXT SEND_LAST_BAGS

Whether to allow start of docking or not from GOS (OPERATOR=YES must be used here) Whether to allow start of scheduled docking or not from GOS (OPERATOR=YES must be used here) Whether to allow Open/Close Ramp to be sent from GOSMMI Whether to allow to send free text to DGS from GOSMMI Whether to allow to send Parked Last Bags from GOSMMI



Version: 1.0

IOM Manual GOS Gate Operating System 2.3


AIRCRAFT IN SYSTEM The aircraft name displayed for each aircraft type is controlled by the BUTTONS 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 to take 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 SAFEDOCK system 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

©Safegate Group


Date: June 2008

Version: 1.0


2.4


AIRCRAFT AT STAND CONFIGURATION Any attempt to activate a docking procedure, using an aircraft type not configured at the Safedock, will result in an error generated by the Safedock. To avoid sending commands containing aircraft types not configured at a specific Stand, the GATECONFIG section can be used to specify all aircraft types configured at each Stand. Only the aircraft types listed will be displayed in the HMI for the selected Stand. This can be useful to set up on a GOS Workstation. Syntax: RecId=StandName, AircraftName_1, ..., AircraftName_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. This name must match the name for one of the Stands specified in the GATES section. AircraftName: A list of names of the aircraft types allowed for docking at this Stand. Each aircraft name must have a matching entry in the BUTTONS section. Note: (i) The configuration for a single Stand can be divided into more than one 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 the docking 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



Version: 1.0



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 T port number, used by the server to listen for connection 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 the servers.

2.6

CHANGING THE IP ADDRESS ON A WORKSTATION It’s the responsibility of the workstations to connect to the servers. Therefore changing the IP Address on a workstation has no impact on the configuration of other parts of the system.

©Safegate Group


Date: June 2008

Version: 1.0



3.

STAND NAME CONFIGURATION

3.1

GENERAL A change of stand requires changes in different parts of the system. The following is a description 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 using SdConfig.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 value between 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 the Safedock. 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 good practice 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 several configuration scripts in the GOS.INI file. One COMM_LINKS section listing all stands available and one section STAND_kk for each individual Stand. Syntax of COMM_LINKS: StandID = LinkName StandID:



Version: 1.0



A unique name identifying the Stand. This name can, but need not, be the same as that found in the GATES section, the Stand and the communication link will be tied together by the ComId of theStand. Each Stand listed will have its own section, listing the communication parameters to use. LinkName: The name of the communication link to be used for the Stand. The available communication links are SAFEDOCK for serial communication and SD_TIP/SD_UDP for network communication. Syntax of each StandID section: The name of each section must match the StandID listed in the COMM_LINKS section. Each section can contain the following items: PORT = The Ethernet converter in the Safedock is configured to listen for connection attempts from GOS on this T port. ADDR = IP Address of Ethernet converter in the Safedock Configuration of Ethernet controller is described in chapter 2, Appendix C. LOG= Flag to indicate whether this link should automatically gather Safedock log files at the end of each docking procedure. FirstLastGosID = Tells with which Safedock this Link shall communicate with. corresponds to the ComId used in the GATES section and in the SAFEDOCK setup. For a point-to-point communication, the FirstComId and LastComId will match. Example: [COMM_LINKS] STAND_A01=SD_TIP STAND_A02=SD_TIP . . [STAND_A01] PORT=50101 ADDR=192.168.2.35 FirstLastGosID=1,1 LOG=YES [STAND_A02] PORT=50101 ADDR=192.168.2.36 FirstLastGosID=2,2 LOG=YES Description of example: The lines STAND_A01=SD_TIP and the section [STAND_A01] work together. The string 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).

©Safegate Group


Date: June 2008

Version: 1.0

IOM Manual GOS Gate Operating System 3.3.3


GOS HMI Stand Name The symbols and parameters of the GOS HMI is configured under the section GATES. The example below illustrates some parameters with the Stand name, used in 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 the HMI. 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 the same as the ComId used in the Safedock. The ‘n’ parameters are for internal use, and should not be modified (specifies the location 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, the GATECONFIG 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. Some examples are given below.

3.3.5.1

MMILINK The MMILINK section defines the Stands, for which the GOS HMI monitors status. Syntax: FirstLastGosID = 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 remote between SAFEDOCK and SDCONFIG is allowed. Syntax: FirstLastGosID =



Version: 1.0



Defines the range of Stands, by ComId, to be controlled. PORT=PortNo Defines the T port number, used by SETUPCAL.DLL to listen for connection 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 by GOS. Syntax: FirstLastGosID = 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 send IATA/ICAO codes to GOS, the IATA codes have to be converted to valid SAFEDOCK ID:s. By using the IATA_NAME section it is possible to configure the GOS system so that several IATA/ICAO subtypes get converted to one generic aircraft type when sent to Safedock. 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 for one of the names specified in the BUTTONS section. (b) FIDS_1

©Safegate Group


Date: June 2008

Version: 1.0

IOM Manual GOS Gate Operating System (i)

Chapter 2. Installation: Appendix A The IATA code of the aircraft as reported by the FIDS link. Several codes stated on the same line will all be converted to the same aircraft 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 BUTTONS section. 4.2.2

Updating the Aircraft Menu The aircraft name displayed for each aircraft type is controlled by the BUTTONS section. If an aircraft name is updated in the BUTTONS section (left column), it must 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 to take 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 SAFEDOCK system 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] 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, the GATECONFIG section can be used to specify all aircraft types configured at each Stand. If this feature is used and an entry in the BUTTONS section is updated, changes must be also be made in the GATECONFIG section. This section is described in more detail in section 2 of this manual.



Version: 1.0



5.

INTERLOCK CONFIGURATION

5.1

GENERAL The module INTERLOCK.DLL evaluates rules about what aircrafts are allowed to dock on a stand based on the status of adjacent stands. Every aircraft type has a class designation, which is ranging from A-Z, where earlier letters will always indicate a smaller (with regard to wingspan) aircraft. Thus, a class A aircraft will always be smaller than a class C aircraft. The interlock information will contain a series of blocking rules for each stand, where each rule identifies an aircraft class, the blocking stand and the smallest aircraft class on 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 SelectedStand

Unique index in INI file The name of the stand for which a rule applies to (shall match any of the names seen in GOSMMI) SelectedAc The smallest aircraft class at the selected stand this rule applies to. The rule is valid for aircraft of this and all higher classes. I.E. any rule for class A will apply to ALL aircraft types, a rule for class D will apply to aircrafts of class D-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 the selected aircraft. If there is an aircraft of this class or higher at the blocking stand, the rule is fulfilled and the requested docking will be blocked. A blocking aircraft of class A will therefore mean that any aircraft at the blocking stand will block the requested operation. {} Free Text field. Any text within brackets is treated as a comment, and can be put in anywhere in the interlock rule. [AC1,AC2,…;Class;stand1:stand2,…. Redefinition of class designator. ] If A310 is parked at stand D42 and stand D44 requests to start docking, the A310 shall be redefined to be a class B type.

Example 1: D42=D42, [A310;B;D44] Example 2: D44=D44, [A310, B737;D;D42,D46]

If A310 or B737 is parked at stand D44 and stand D42 or D46 requests to start docking, the A310/B737 shall be redefined to be a class D type. Note: exception rules shall only be used when necessary to redefine the class types. ©Safegate Group


Date: June 2008

Version: 1.0



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) Stand2 =S2, A(Stand1:A), C(Stand3:E)

Stand3=S3, E(Stand2:C)

Any aircraft at stand 2 will block operations at stand 1 1. Docking at stand 2 will be blocked if there is any aircraft at stand 1. 2. Docking a C type or bigger aircraft at stand 2 will be blocked if there is a E-type or bigger aircraft at stand 3. Dockings an E type or bigger aircraft at stand 3 will be blocked if there is a C-type or bigger aircraft at stand 2. All smaller aircrafts are always 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 on stand 2 will be blocked if there is an E-type or bigger parked at stand 3. However, docking a C-type or bigger at stand 2 when a B747 is Parked at stand 3 will be allowed, because the B747 on stand 3 has been redefined to be a class D type when stand 2 is docking. Note: If no blocking rules are configured, docking will always be allowed.



Version: 1.0



6.

CAMERA CONFIGURATION

6.1

IP ADDRESS CONFIGURATION In order to communicate with the camera on each stand, IP Address for each camera must be known by GOS. This is configured in the [CAMERA_IP] section according to the 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 from disk from GOSMMI POPUP_ON_ERROR=YES Camera window will pop-up in GOSMMI upon error from Safedock MAX_CAMERA_FORMS=4 Maximum number of camera forms allowed to be open at the same time in GOSMMI

6.3

PICTURE LOGGING In the [FEATURE_LINKS] section GOS can be configured to camera images automatically during a docking. Add the following line to the [FEATURE_LINKS] section: PICTURE_LOG= PICTURE_LOG Create 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 docking has finished. LOGDAYS=7

ACTIVE=NO DOCKING=YES DOWNGRADE=YES BLOCKED=NO ERROR=YES

Number of days to keep camera images on disk. (Make sure necessary disk space is available for chosen configuration) States to start/not start camera recording for

©Safegate Group


Date: June 2008

Version: 1.0


Chapter 3. Operation CHAPTER 3 OPERATION CONTENTS

Section

Description

Page No.

1.

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

2. 2.1 2.1.1 2.1.2 2.2 2.2.1 2.3 2.3.1 2.4 2.4.1 2.4.2 2.4.3 2.4.4

DOCKING MONITORING ............................................................................................. 4 GENERAL ......................................................................................................... 4 GOS Standard System............................................................................... 4 Co-operation with External Systems ....................................................... 4 VDU SCREEN LAYOUT ................................................................................... 5 General ........................................................................................................ 5 HELP MENU SYSTEM ..................................................................................... 7 General ........................................................................................................ 7 EVENT AND STATUS DISPLAY ...................................................................... 8 Stand Status Display ................................................................................. 8 Stand Status Box ..................................................................................... 11 DGS Error Codes ..................................................................................... 12 System Event Windows .......................................................................... 13

3. 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.3 3.3.1 3.4 3.4.1 3.5 3.5.1 3.6 3.6.1

MAINTENANCE FUNCTIONS .................................................................................... 14 GOS AND SAFEDOCK EVENT LOGGING.................................................... 14 GOS Event Log......................................................................................... 14 Viewing a GOS Event Log File................................................................ 14 DOCKING LOG FILES.................................................................................... 18 General ...................................................................................................... 18 Viewing and Print-Out ............................................................................. 18 AUTOMATIC OF SAFEDOCK CONFIGURATION FILES ............. 19 General ...................................................................................................... 19 CLOSING DGS FOR MAINTENANCE ........................................................... 19 General ...................................................................................................... 19 DISPLAY OF DGS TYPE................................................................................ 20 General ...................................................................................................... 20 SAFEDOCK MAINTENANCE USING SDCONFIG ........................................ 21 General ...................................................................................................... 21

4. 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.2.8

DOCKING CONTROL ................................................................................................. 21 GENERAL ....................................................................................................... 21 DOCKING COMMANDS ................................................................................. 21 Log On Procedure.................................................................................... 21 Creating s ......................................................................................... 22 Starting a Docking Procedure ................................................................ 23 Activating a Scheduled Docking ............................................................ 25 Inserting a Scheduled Flight................................................................... 25 Displayed Statuses During Docking ...................................................... 26 Shut down................................................................................................. 28 Park On ..................................................................................................... 28

©Safegate Group Document: US-GosRUH-Operation


Version: 1.0


Chapter 3. Operation

4.2.9 4.3 4.3.1 4.3.2 4.4 4.4.1

Park Off ..................................................................................................... 28 CAMERA ......................................................................................................... 29 Viewing Live Images ................................................................................ 29 Viewing Recorded Images ...................................................................... 30 ADJACENT STAND INTERLOCK .................................................................. 30 Important Things to Know ...................................................................... 30

5. 5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.5.3

FIS INTERFACE .......................................................................................................... 31 BASIC FUNCTIONALITY................................................................................ 31 ARRIVAL PROCEDURE................................................................................. 31 DEPARTURE PROCEDURE .......................................................................... 31 RIDS INFORMATION ..................................................................................... 31 SPRECIAL OPERATIONAL PROCEDURES ................................................. 32 General ...................................................................................................... 32 Unprocessed Arriving Flight .................................................................. 32 Unsuccessful Docking ............................................................................ 32

APPENDICES: GOS Features GOS Access Manager GOS Reporter

Appendix A Appendix B Appendix C

©Safegate Group

Page 2 of 32 Document: US-GosRUH-Operation

Date: June 2008

Version: 1.0


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 and Stand parameters. (a) The table A_FLIGHT contains information about scheduled active flights. These data are used for starting the docking and departing procedures at the Stands and are also used for displaying relevant flight information during these 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’s DGS 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.



Version: 1.0



2.

DOCKING MONITORING

2.1

GENERAL

2.1.1

GOS Standard System The Gate Operating System/GOS of Safegate comprises one or several PC computers, 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 Interfaces/MMI at a GOS Workstation. For maintenance purposes the Docking Monitoring system also includes an Event Log feature, giving a history of all events at the Stands and within the GOS system itself.

2.1.2

Co-operation with 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 GOS workstation in ACC for example. An external FIS/GMS system is connected to GOS for automatic insertion and updates of scheduled flights. The FIS connection can also be used for displaying flight information at the Stand assigned for an arriving or departing flight.

©Safegate Group


Date: June 2008

Version: 1.0



2.2

VDU SCREEN LAYOUT

2.2.1

General The operator at a GOS node uses a PC workstation with Microsoft Windows 2000 based software for monitoring the docking operations at each Stand. After having logged on as a GOS , the program GOSMMI is selected from Windows Start Menu/Program. The first time the program is started IP Addresses to the GOS servers must be entered into the address fields.

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



Version: 1.0



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

AIRPORT STAND LAYOUT

©Safegate Group


Date: June 2008

Version: 1.0



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.



Version: 1.0



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 of these changes will be displayed on the screen by Stand number tags changing colour, and by aircraft symbols appearing on Stand centrelines. Green Stand number tag with black text: Stand is Ready. The Stand is empty but not confirmed to be used yet. This status will appear automatically after a pushback procedure. READY Green Stand number tag with white text: Stand is Ready Open. The Stand is empty and confirmed to be used by a local or GOS operator.

READY OPEN Grey Stand number tag with black text: Stand is Scheduled for docking but not confirmed by operator at a Stand. Docking is started immediately when confirmed by local operator. SCHEDULED DOCKING Yellow Stand centreline:

number

tag

and

Docking Request status. Operator has selected an aircraft, which is checked against the GOS server. Docking is started immediately if allowed. REQUEST INTERLOCK Red Stand number tag with white text: An interlock request has been evaluated to not allow start of docking.

STAND INTERLOCKED

©Safegate Group


Date: June 2008

Version: 1.0


Chapter 3. Operation GREY stand number tag with red text:

The interlock request could not be evaluated by GOS.

INTERLOCK UNKNOWN GREY stand number tag with red text:

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

INTERLOCK TIMEOUT Yellow Stand centreline:

number

tag

and

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

ACTIVE Yellow Stand centreline:

number

tag

and

Stand is in down grade mode. The docking has been started, but the visibility is low due to heavy fog, rain or snow. DOWN GRADE Yellow Stand number tag and centreline with a yellow aircraft on centreline: Docking status. An aircraft is docking. DOCKING Blue Stand tag, blue aircraft and black centreline: Parked status. The aircraft reached its stop position.

has

PARKED



Version: 1.0


Chapter 3. Operation Light blue Stand tag, blue aircraft and black centreline: Scheduled departure status (Only with standard interface to FIS). An aircraft is parked at the Stand. The aircraft is planned to depart shortly. SCHEDULED DEPARTURE Light blue Stand tag, blue aircraft and black centreline: Departing. The aircraft is no longer present at its parked position, but may still be within the gate area. DEPARTING Red Stand number tag: Emergency stop button has been pushed.

EMERGENCY STOP Pink Stand number tag: Communication error. The communication with the docking system is interrupted.

COM ERROR Pink Stand number tag with white text: DGS error. The Docking System has an error status.

DGS ERROR

©Safegate Group


Date: June 2008

Version: 1.0



Brown Stand number tag with white text: Maintenance status. Stand is occupied for maintenance activities. Remote activation of docking procedures is not allowed. MAINTENANCE

Brown Stand number tag with white text: Closed for Maintenance. The stand is closed for remote access due to planned maintenance activities. The VDGS remain available for local operations. CLOSED FOR MAINTENANCE 2.4.2

Stand Status Box Status of the Docking System, SAFEDOCK, at a Stand can be viewed by selecting the Stand number tag with the mouse. When the tag is selected, a small box, that contains status information, will appear next to the tag. On the below picture a number of Stands have been selected, and information in the status boxes can be viewed. When the Stand tag is selected again, the status box disappears.

STAND STATUS BOXES The system indicates following aircraft/flight information in the status box under the aircraft type field. (a) If started by the local Stand operator the text ”- LOCAL” will be displayed in the 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 status box under the aircraft type, if flight number is not available. (c) If flight number is available, this will be displayed instead of “- GOS”.



Version: 1.0

IOM Manual GOS Gate Operating System (d)

2.4.3


If both flight and registration number is available, the flight number will be displayed as default. Flight and Registration number can be alternatively displayed by left clicking with the mouse in the status box under the aircraft type field.

DGS Error Codes In case of an error with the SAFEDOCK system, an associate code is displayed with the error message in the status box and in the log file. The code represents the following error types for the SAFEDOCK system: SAFEDOCK Error Codes ‘00’ - No error

Description This code is sent when the system has not an error status

‘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/U 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 error

No communication with operator

‘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

©Safegate Group


Date: June 2008

Version: 1.0



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

Each type of event can be configured to generate an audible alarm. By default no alarm 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 the local 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 its window to start flashing indicating that a new message has arrived. Each window is resizable and movable on the screen. The window can be collapsed/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 window will expand whenever the mouse pointer hovers over the control and disappears again as the mouse leaves the window area. A message/all messages can be manually removed from the window by right clicking on 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 is displayed in this window. Error Codes

DGS Statuses

Interface statuses (not in picture)

A possible error message for a Safedock is displayed in this window. A new error will overwrite existing error. The error will remain until confirmed by an operator. Current status of each Safedock is displayed in this window. A new status will overwrite existing status. Interface connection statuses (FIS, TMS etc) are displayed in this window. A new status will overwrite existing status.



Version: 1.0



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 Docking Systems) and the communication to external systems, if any, are monitored and logged 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 (an option) (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 format YYMMDD.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 (specified in 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 by two pop-up menus. These menus are accessed by right clicking anywhere on the monitor 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 outside any 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 be restricted to events pertaining the selected Stand only.

©Safegate Group


Date: June 2008

Version: 1.0



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

SELECTION OF LOG FILE 3.1.2.2

GOS Events Log View If ‘View log’ was selected from the GOS Monitor pop-up menu, the below data would be 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 systems like FIS. This view also includes Commands and Blocks On/Off events.



Version: 1.0



LOG FILE VIEW

©Safegate Group


Date: June 2008

Version: 1.0

IOM Manual GOS Gate Operating System 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



Version: 1.0

IOM Manual GOS Gate Operating System 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 docking procedure, 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 sub directory where the log files will be stored. The sub directories will have the same name 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 the program STANDCONFIGPRINT.EXE, called the Stand Configuration Print-Out Utility. This Utility program is described in the DGS IOM Manual, chapter 4, MAINTENANCE.

©Safegate Group


Date: June 2008

Version: 1.0



3.3

AUTOMATIC OF SAFEDOCK CONFIGURATION FILES

3.3.1

General To store a backup of each Safedock configuration the configuration files (centreline and 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 own sub directory where the configuration files will be stored. The sub directories will have the same name as the stand symbols in the GOS MMI application (this requires at least 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 this state; 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.



Version: 1.0



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. The information 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 Type 2). The text to be displayed is configurable in GOS.INI on the local computer.

©Safegate Group


Date: June 2008

Version: 1.0



3.6

SAFEDOCK MAINTENANCE USING SDCONFIG

3.6.1

General Maintenance on Safedocks can be performed from GOS by using the software SDCONFIG.EXE. From a workstation, log on to Windows as ‘dgsmaint’. Over the network, access the shared folder ’SDK’ on the server by using Windows Explorer. Start SdConfig.exe by double-clicking on the filename. This Utility program is described in the DGS IOM Manual, chapter 4, MAINTENANCE.

4.

DOCKING CONTROL

4.1

GENERAL Control of a SAFEDOCK/DGS system at a Stand can occur from the Local Operator on apron or from a GOS Workstation. The local control and the GOS always 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. SAFEDOCK Control, a system can be installed optionally. There are two ways to enter the Log on dialog, by right clicking anywhere on the screen 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 cannot be performed. However, current status will be displayed, and local operation at the stand is allowed, of course. Also the Log File can be viewed. When clicking the ‘Log On’ field, the system will ask for a ID and a according to the figure below.



Version: 1.0



LOG ON DIALOG After having logged on as a defined , the following dialogs will be displayed, when clicking the screen or a particular stand. With the dialog to the left it’s possible to log off again, and with the dialog to the rights it’s now possible to send the commands that are allowed for the stand specified.

COMMAND MENU 4.2.2

Creating s When starting the GOS system for the first time, the original supervisor has to log on as = ‘safegate’ and input the original ‘gos’. Once a new or supervisor has been assigned, the original and will be removed. Therefore it is important to first assign a new supervisor and , before a new is defined. After that the supervisor can create other s (or other supervisors) and assign s to these. The or supervisor can be the name in plain text of the person, who shall operate, and the will be a secret code for each individual. The difference between a supervisor and a is that the supervisor has the power to decide who shall be authorised as a . When you log on as a supervisor, the following dialog will appear, when clicking somewhere on the screen.

©Safegate Group


Date: June 2008

Version: 1.0



LOG OFF MENU By selecting the field ‘istration’, it’s now possible to create new supervisors and s. The dialog shown below is used for the purpose.

CREATING S DIALOG 4.2.3

Starting a Docking Procedure A docking procedure can be started from apron/SAFEDOCK or from the GOS. When right-clicking over a stand, a command menu appears. This menu indicates which commands are allowed for the selected stand.



Version: 1.0



• 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 tower operator 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 the dialog below.

OPEN STAND MENU • Docking can be started by clicking ‘StartDock’ in the command menu followed by selecting Manufacturer, and Aircraft Type from the drop down menu. The command is sent to SAFEDOCK, as soon as the ‘Confirm dialog’ is completed.

©Safegate Group


Date: June 2008

Version: 1.0



START DOCKING MENU 4.2.4

4.2.5

Activating a Scheduled Docking •

When the stand has been scheduled with a flight (usually received from a FIS system), the operator will have the possibility to activate the docking system with 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 is sent to SAFEDOCK as soon as the ‘Confirm dialog’ is completed.

Inserting a Scheduled Flight When FIS is unavailable and thus no flights are sent to GOS, the flights can be inserted from the GOSMMI instead. Right-Click over a stand and select ‘Schedule Flight’; the following dialog will appear.



Version: 1.0


1. 2. 3. 4. 5. 6. 7.


Select A/C type Select Arrival or Departure flight Type in flight number Type in registration number if one exists Select STAD time (Scheduled time of arrival/departure) Select ETAD time (Estimated time of arrival/departure) Press Schedule Docking to send the flight for further processing

Note: 1. The ETAD time will determine when the flight shall be scheduled. Default configuration is set to 10 minutes before ETAD time. 2. Example: setting the ETAD time to one hour ahead of current time will cause the 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 identity at the bottom 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 on information from the GMS, Flight No and Aircraft type will be displayed in the status box, if this field of the pop-up menu is clicked. •

When the docking is completed the stand status changes over to Parked.

©Safegate Group


Date: June 2008

Version: 1.0



DOCKING COMPLETED MENU • If the Gate Operating System, GOS, is not working, or the tower operator has stated the wrong aircraft type, the operator at the apron can always start a docking procedure from the Operator in the bridge. This is done by selecting among the aircraft types available on the operator , and pressing ‘Enter’. The GOS system will indicate (in the status box of GOS Monitor) the source of the Start Docking command, which is ‘GOS’. • If docking is started from operator , based on information from the GMS/FIDS, the Flight No. will be displayed in the status box under the aircraft type.

GOS MMI STATUS BOX



Version: 1.0



Shut down The ‘Shut Down’ button can be used if there is a reason for turning off the SAFEDOCK system. A typical reason could be a last minute change of Stand, so the aircraft 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 to SAFEDOCK. 4.2.8

Park On Manual Park On is done by selecting ‘Park On’ and also the aircraft type from the drop down menu. The GOS operator must confirm the ‘Park On’ command before it is sent to SAFEDOCK. When GOS has a connection to a FIS system and a flight is associated with the operation (Safedock is scheduled for arrival with a flight received from FIS), a Blocks On transaction will be sent to FIS.

4.2.9

Park Off When the Safedock is parked with an aircraft, the Safedock will periodically scan the Stand area for the departure of the aircraft, and when the aircraft is no longer detected 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 down menu. The GOS operator must confirm the ‘Park Off’ command before it is sent to SAFEDOCK. When GOS has a connection to a FIS system and a flight is associated with the operation (Safedock is scheduled for departure with a flight received from FIS), a Blocks Off transaction will be sent to FIS. Note: Local Blocks On/Off transactions (no flight information available from FIS) can also be reported to a FIS system if configured to do so. This is optional and depends on the interface between GOS and FIS.

©Safegate Group


Date: June 2008

Version: 1.0



4.3

CAMERA

4.3.1

Viewing Live Images Live images can be view from the GOSHMI whenever a camera is installed in the Safedock. 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 live images from the selected stand.



Version: 1.0



Viewing Recorded Images The GOS system can be configured to record dockings, which then can be viewed from the GOS HMI. To view a recorded docking sequence, right click over a stand symbol 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 recording

Open today’s recordings

About/Info

Close

1. “Open today’s recordings” will allow the to select and view one of the camera recordings for the current day for the selected stand. 2. ‘Open any recording’ will allow the to select and view one of the available camera recordings for the selected stand. 3. Once a camera recoding has been opened it can be viewed or stepped through one picture at a time by using the available buttons as illustrated below.

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 Safedock systems are holding correct status. If an aircraft is manually towed in to a stand, a manual Park On must be made from GOS or from the operator to put the stand in correct status. The simulated stands must be manually Parked On from the GOSMMI. 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, System Description.

©Safegate Group


Date: June 2008

Version: 1.0



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 (not whole flight scheduled in advance). Thus, a new flight sent from FIS will override any existing 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; default is 10 minutes before BTA – best time available of arrival) and Safedock is ready to accept the flight (in Ready and Scheduled status), GOS will schedule DGS or start DGS with the flight (schedule or start of docking is configurable in GOS). A scheduled docking needs to be activated from GOS or from the local Operator 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 be accepted, GOS will not Schedule the Safedock with the flight. However, if Safedock changes to a status in which it can accept the flight, then GOS will Schedule the Safedock unless the flight is too old (the time when a flight is considered to be old is configurable).

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 but default is 10 minutes before BTD) and Safedock is Parked, GOS will schedule Safedock with the flight and start Park Off detection. Upon successful departure of the 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 departure flight cannot be accepted, GOS will not Schedule Safedock with the flight. However, if Safedock changes to a status in which it can accept the flight, then GOS will Schedule the Safedock unless the flight is too old (the time when a flight is considered to be old is configurable).

5.4

RIDS INFORMATION Based on the flight information received from FIS prior to each docking the system can be configured to display text messages on Safedock some time before start of docking. Currently the following text information is available: Main flight number, ETAD or STAD and Count down time to Arrival or Departure. Example:



Version: 1.0


Arrival


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 the GOS 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 either a ‘start of docking’ or cancellation (OFF) is made from the Operator or the ‘Shut Down’ command is made from GOSMMI or the flight becomes to old; the default configuration considers a flight to be old when the time es ETAD + 30 minutes.

5.5.3

Unsuccessful Docking If for any reason the docking was unsuccessful, the GOS operator or bridge shall make a manual ‘Park On’ command in order to make it possible to process the next departing flight. Thus, every docking attempt must end with PARKED status at DGS.

©Safegate Group


Date: June 2008

Version: 1.0


Chapter 3. Operation: Appendix A OPERATION: APPENDIX A GOS FEATURES CONTENTS

Section

Description

Page No.

1. 1.1

SCOPE .......................................................................................................................... 2 GENERAL ......................................................................................................... 2

2. 2.1

GOS SYSTEM TOPOLOGY.......................................................................................... 2 GENERAL ......................................................................................................... 2

3. 3.1

REDUNDANT SERVERS .............................................................................................. 2 GENERAL ......................................................................................................... 2

4. 4.1

COMMUNICATION BETWEEN GOS AND DGS ......................................................... 2 GENERAL ......................................................................................................... 2

5. 5.1

OPERATING SYSTEM SOFTWARE ............................................................................ 2 GENERAL ......................................................................................................... 2

6. 6.1 6.2 6.2.1 6.3 6.3.1 6.4 6.4.1 6.5 6.5.1

STANDARD FEATURES .............................................................................................. 2 GENERAL ......................................................................................................... 2 DOCKING MONITORING AND CONTROL ..................................................... 2 General ........................................................................................................ 2 GOS EVENT LOG FILES ................................................................................. 2 General ........................................................................................................ 2 AUTOMATIC OF SAFEDOCK DOCKING LOG FILES .................... 3 General ........................................................................................................ 3 AUTOMATIC OF SAFEDOCK CONFIGURATION FILES ............... 3 General ........................................................................................................ 3

7. 7.1

SAFEDOCK MAINTENANCE ....................................................................................... 3 GENERAL ......................................................................................................... 3

8. 8.1 8.2

INTERFACE TO EXTERNAL SYSTEMS ..................................................................... 3 FIS ..................................................................................................................... 3 NTP ................................................................................................................... 3

©Safegate Group Document: US-AppA-GosRUH-Features


Version: 1.0


Chapter 3. Operation: Appendix A

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 detailed description can be found in the SY-AppB-GosAirport-Redundant document.

4.

COMMUNICATION BETWEEN GOS AND DGS

4.1

GENERAL DGS 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 any GOS subsystem the airport layout with stands and docking systems can be displayed and monitored. The Docking Control and Monitoring function is fully explained in the chapter 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.

©Safegate Group

Page 2 of 4 Document: US-AppA-GosRUH-Features

Date: June 2008

Version: 1.0



A docking procedure contains several events, which are stored with time stamps, for example: 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 configurable period 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 IOM manual. 6.4

AUTOMATIC OF SAFEDOCK DOCKING LOG FILES

6.4.1

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

6.5

AUTOMATIC OF SAFEDOCK CONFIGURATION FILES

6.5.1

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

7.

SAFEDOCK MAINTENANCE

7.1

GENERAL Maintenance on Safedocks can be performed from GOS by using the software SDCONFIG.EXE. This Utility program is described in the DGS IOM Manual, chapter 4, MAINTENANCE.

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 report Block 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.

©Safegate Group Document: US-AppA-GosRUH-Features


Version: 1.0



©Safegate Group

Page 4 of 4 Document: US-AppA-GosRUH-Features

Date: June 2008

Version: 1.0


Chapter 3. Operation: Appendix B OPERATION: APPENDIX B GOS ACCESS MANAGER CONTENTS

Section

Description

Page No.

1. 1.1

INTRODUCTION ........................................................................................................... 2 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 ............................................. 7 EDITING S GROUPS AND CREDENTIALS .......................................... 8 CONFIGURE S, GROUPS, STANDS AND CREDENTIALS ............... 10

5. 5.1 5.2 5.3 5.4 5.5

MORE INFORMATION................................................................................................ 12 DOCUMENTATION ........................................................................................ 12 VERSION ........................................................................................................ 12 REFERENCES AND TRADEMARKS............................................................. 12 TERMINOLOGY ............................................................................................. 12 LANGUAGE .................................................................................................... 12

©Safegate Group Document: US-AppB-GoRUH-AccessManager


Version: 1.0


Chapter 3. Operation: Appendix B

1.

INTRODUCTION

1.1

GOS ACCESS MANAGER GOS Access Manager is a tool to manage credentials, such as setting up istration and rights and privileges for airport personnel in a Gate Operating System (GOS). GOS Access Manager benefits to GOS s are: •

Reduced lead times for system changes.

•

Changes can be made for specific site requirements.

•

Strengthened ownership of the purchased system with control over system configuration.

•

Improved management efficiency with internal resources and less traffic disturbance.

This document includes information how to install and use GOS Access Manager on a computer with Microsoft Windows XP. Note: GOS Access Manager software releases are subject to the latest development improvements and may differ to the information and image examples used in this document. Software images and menu selections (Arial Bold font) used in instructions are examples 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 for translation.

©Safegate Group

Page 2 of 12 Document: US-AppB-GoRUH-AccessManager

Date: June 2008

Version: 1.0

IOM Manual GOS Gate Operating System 2.


INSTALLATION GOS Access Manager is installed with a setup application, on a computer with Windows 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.



Version: 1.0



MENUS AND COMMANDS GOS Access Manager includes a number of menus, tabs, entry fields, commands and views. Commands are based on standard Windows application commands specifically 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 configuration information.

About

Program, version and more information. Click OK to close.

s

Tab views and commands

Existing s

Select from a list of s to edit or view information.

Edit

Entry fields and commands to create, update and delete s.

name

Enter a name.

Enter a .

Enter the same for confirmation.

Create

Create a with the information in the entry fields.

Update selected

Select an existing , edit information in the entry fields and click to update.

Delete selected

Select an existing and click to delete.

Group hip

View the groups to which a belongs.

Select group

Select an existing , and use to select from available groups to belong to.

©Safegate Group


Date: June 2008

Version: 1.0



Menus, tabs, commands

Description

Examples

groups


Existing groups

Select from a list of groups to edit or view information.

Edit group

Entry fields and commands to create, rename and delete groups.

Group name

Enter a 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.

s in group

View the s in the group.

Select s

Select from existing s for group hip.

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


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 the information 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 group

View the stands in the stand group.

Select stands

Select from existing stands for stand group hip.



Version: 1.0



Menus, tabs, commands

Description

Examples

Stand credentials


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 stand credential and click to delete.

Included stands

Select the tab for a list of existing stands credentials for stand group hip.

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 for included 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.

©Safegate Group


Date: June 2008

Version: 1.0



USING GOS ACCESS MANAGER GOS Access Manager is designed with an intuitive interface and logical functionality.

¾ START GOS ACCESS MANAGER AND 1. Start GOS Access Manager •

Double-click on the desktop icon or

•

Go to Start\Programs\GOS Access Manager to start the program.

2. Enter information: A. name B. C. Server, if required or different from localhost.



Version: 1.0



¾ EDITING S GROUPS AND CREDENTIALS 1. Create, update or delete s •

Click the s tab.

Create a new : A. Enter a new name, and the . B. Click Create . Update an existing : A. Select an existing . B. Change information in the entry fields. C. Click Update selected . Note: When renaming a only, no new information is entered for the to remain the same. Delete a : A. Select an existing . B. Click Delete selected .

2. Create, rename or delete groups •

Click the groups tab.

Create a new group: C. Enter a new group name. D. Click Create group. Rename an existing group: A. Select an existing group. B. Change the name in the entry field. C. Click Rename selected group. Delete selected group: A. Select an existing group. B. Click Delete selected group.

©Safegate Group


Date: June 2008

Version: 1.0



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.



Version: 1.0



¾ CONFIGURE S, GROUPS, STANDS AND CREDENTIALS 1. Select groups hip A. Click the s tab. B. Select an existing group. C. Click Select groups. •

From Available groups, click

•

From Selected groups, click

to select or to remove.

D. Click Close when completed.

2. Select s for a group A. Click the groups tab. B. Select an existing . C. Click Select s. •

From Available s, click

•

From Selected s, click



3. Select credentials for a group A. Click the groups tab. B. Select an existing group. C. Click Select credentials. •

From Available credentials, click

•

From Selected credentials, click



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

•

From Selected stands, click



©Safegate Group


Date: June 2008

Version: 1.0



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

•

From Selected stands, click


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 groups. •

From Available stand groups, click

•

From Selected stand groups, click



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

•

From Selected credentials, click





Version: 1.0



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 alphabetical revisions for external use. Version

Date

Prep.

Status

App.

Change Description

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 their respective owners. Any rights not expressly granted herein are reserved. All illustrations and images are for illustration only and may not accurately depict the actual product.

5.4

TERMINOLOGY This document includes a selection of , words and abbreviations.

5.5

Term or word

Abbreviation

Gate Operating system

GOS

Technical Writer

TW

Product Leader

PL

Comment

LANGUAGE Original documentation is created in English (U.K.). Note: Software images and menu selections (Arial Bold font) used in instructions are examples 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 fro translation. For more information, see www.safegate.com.

©Safegate Group


Date: June 2008

Version: 1.0


Chapter 3. Operation: Appendix C OPERATION: APPENDIX C GOS REPORTER CONTENTS

Section

Description

Page No.

1. 1.1 1.2

INTRODUCTION ........................................................................................................... 2 GOS REPORTER ............................................................................................. 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. 4.1 4.2 4.3 4.4 4.5

MORE INFORMATION.................................................................................................. 7 DOCUMENTATION .......................................................................................... 7 VERSION .......................................................................................................... 7 REFERENCES AND TRADEMARKS............................................................... 7 TERMINOLOGY ............................................................................................... 7 LANGUAGE ...................................................................................................... 7

©Safegate Group Document: US-AppC-GosRUH-Reporter


Version: 1.0


Chapter 3. Operation: Appendix C

1.

INTRODUCTION

1.1

GOS REPORTER GOS Reporter is a tool for airport personnel using a Gate Operating System (GOS) to generate reports. Reports are generated by making queries against the GOS log. The following common queries are ed: •

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). The information is sorted and/or filtered by error type.

•

Blocks On/Off for all gates/a specific gate between two dates (from/to). The information is sorted and/or filtered by blocks on/off.

• Free text searches in error messages. Note: Other queries can be ed, if required. 1.2

DOCUMENTATION This document includes information how to install and use GOS Reporter on a computer with Microsoft Windows XP. Note: GOS Reporter software releases are subject to the latest development improvements and may differ to the information and image examples used in this document. Software images and menu selections (Arial Bold font) used in instructions are examples 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 for translation.

©Safegate Group

Page 2 of 8 Document: US-AppC-GosRUH-Reporter

Date: June 2008

Version: 1.0



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 3.

GosReporterSetup.exe.

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 is already installed on your computer.

4.

When Installation Complete appears, Click Close.



Version: 1.0



MENUS AND COMMANDS GOS Reporter includes a number of menus, entry fields, commands and views. Commands are based on standard Windows application commands specifically adapted for GOS Reporter. The following menus with commands are available:

¾ NAVIGATE MENUS AND COMMANDS Menus, commands

Description

Examples

File New Query

Create a new log view.

Open Query

Open a previously saved view.

Exit

Close the program.

©Safegate Group


Date: June 2008

Version: 1.0



USING GOS REPORTER GOS Reporter is designed with an intuitive 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. A. Enter information to start the program. •

name.

•

.

•

IP Address or host name of Server 1 and 2.

B. Click OK. Note: At first start up the Server field is empty. name, and server information is verified with a s 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 Aircraft, 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\Export.

Note: For more information, see the following examples.



Version: 1.0



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.

©Safegate Group


Date: June 2008

Version: 1.0



4.

MORE INFORMATION

4.1

DOCUMENTATION This document aims to give personnel an insight into the benefits of using the GOS Reporter 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 alphabetical revisions for external use. Version

Date

Prep.

Status

App.

Change Description

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 their respective owners. Any rights not expressly granted herein are reserved. All illustrations and images are for illustration only and may not accurately depict the actual product.

4.4

TERMINOLOGY This document includes a selection of , words and abbreviations.

4.5

Term or word

Abbreviation

Gate Operating system

GOS

Technical Writer

TW

Product Leader

PL

Comment

LANGUAGE Original documentation is created in English (U.K.). Note: Software images and menu selections (Arial Bold font) used in instructions are examples 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 fro translation. For more information, see www.safegate.com.



Version: 1.0



©Safegate Group


Date: June 2008

Version: 1.0


Chapter 4. Maintenance CHAPTER 4 MAINTENANCE CONTENTS

Section

Description

Page No.

1. 1.1 1.2 1.3

INTRODUCTION ........................................................................................................... 2 SCOPE.............................................................................................................. 2 MAINTENANCE ON THE ETHERNET LAN..................................................... 2 GENERAL PRECAUTIONS .............................................................................. 2

2. 2.1 2.2 2.3

CORRECTIVE MAINTENANCE ................................................................................... 2 FAULT FINDING AND RECTIFICATION ......................................................... 2 REPLACEMENT OF MALFUNCTIONING UNITS ........................................... 2 SOFTWARE INSTALLATION ........................................................................... 2

3. 3.1

PREVENTIVE MAINTENANCE .................................................................................... 3 GENERAL ......................................................................................................... 3

4. 4.1 4.1.1 4.1.2 4.2 4.2.1 4.2.2 4.3 4.3.1 4.3.2 4.4 4.4.1 4.4.2 4.5 4.5.1 4.5.2 4.6 4.6.1 4.6.2

FAULT FINDING GUIDE ............................................................................................... 3 COMM ERROR ON ALL STANDS ................................................................... 3 General ........................................................................................................ 3 Step-by-step troubleshooting................................................................... 3 COMM ERROR ON A SINGLE DGS - LAN CONNECTION ............................ 3 General ........................................................................................................ 3 Step-by-step troubleshooting................................................................... 3 COMM ERROR ON A SINGLE DGS – CURRENT LOOP MODEM ................ 4 General ........................................................................................................ 4 Step by step trouble shooting .................................................................. 4 HARD DISK/OPERATING SYSTEM FAILURE ................................................ 5 General ........................................................................................................ 5 Step by step trouble shooting .................................................................. 5 NTP CONNECTION ERROR ........................................................................... 5 General ........................................................................................................ 5 Step by step trouble shooting .................................................................. 5 GOS HMI FAILS TO START............................................................................. 5 General ........................................................................................................ 5 Step by step trouble shooting .................................................................. 5

APPENDICES: GOS Fault Finding Guide

Appendix A

©Safegate Group Document: MA-GosRUH-Maintenance


Version: 1.0


Chapter 4. Maintenance

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 and Workstations 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 LAN used 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 little maintenance. Before commencing any maintenance activity, the following precautions must be considered: CAUTION: PROTECTION AGAINST ELECTROSTATIC DISCHARGE The transfer of static electricity causes ESD damage when electronic components are handled. It’s essential to protect components from electrostatic discharge to avoid damage 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 touching any electronic component. WARNING: ISOLATE THE POWER SUPPLY PRIOR TO UNDERTAKING ANY MAINTENANCE 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 a failure 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 are presented in section 4.

2.2

REPLACEMENT OF MALFUNCTIONING UNITS The GOS system is built using conventional rack mounted PC computers with a back plane and plug-in electronic boards. It is supposed that the replacement of electronic boards of these PCs is an elementary 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.

©Safegate Group

Page 2 of 6 Document: MA-GosRUH-Maintenance

Date: June 2008

Version: 1.0



3.

PREVENTIVE MAINTENANCE

3.1

GENERAL The GOS system is built with a standard type of PC computers, which need very little preventive 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 most likely resides on the GOS Server, which is handling the communication. The reason might also be that the Workstation is no longer connected to the GOS Server.

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 gets through, the hardware’s good. Check the service Goskrnl: Stop the service Goskrnl, and restart Goskrnl.exe from Windows’ Explorer. If communication is established with DGS:s, it’s an indication that the service settings are incorrect. Stop Goskrnl.exe, and reinstall the Service according to maintenance 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 its current status continuously. Thus, if Safedock doesn’t receive any questions from GOS, 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). Remove converter from DGS, and connect it to a GOS Maintenance PC with a crossover cable. Perform a PING test against the converter. If the converter replies, 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 cable between 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 the communication. Two of these LED:s are for GOS communication. Check ‘transmit‘ and ‘receive’ if they are blinking. If none is blinking, this could



Version: 1.0



indicate that the motherboard is broken or there is a broken cable between Motherboard and converter. If only the ‘receiver’ is blinking, this indicates that Safedock receives signals but doesn’t recognise them. This is a typical scenario when the U is replaced and the Stand is configured with an incorrect 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 its current status continuously. Thus, if Safedock doesn’t receive any questions from GOS, Safedock will newer respond. With this in mind troubleshooting should always start on the GOS side and work its way 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 and Receive signals. •

At GOS: Start by checking if the ‘Transmit’ LED is blinking. If it is, the GOS is sending data to the modem. If no blinking, problem might reside somewhere between 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 is described 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 communication between PC and Modem is OK. Next step will be to how far the ‘transmit’ signal goes. •

Check DCD LED. If it is lit on GOS side and on Safedock side, it is a good indication that the communication line between the two modems is OK.

•

On Safedock: Check ‘receiver’ LED. If no blinking, the problem might be the modem or the line. Start by replacing the modem. If there is still no blinking, the communication line might be broken. When measuring a communication line, it is preferred to measure the resistance on the line ( the two braches at the remote end; resistance should be between 10-400 ohms depending on length of line).

•

The mother board is equipped with LED:s as well(D2-D10). Two of these LED:s are for GOS-DGS communication. Check ‘transmit‘ and ‘receive’ if they are blinking. If not, the motherboard might be broken or the cable between Motherboard and modem fails. If only the ‘receiver’ LED is blinking, Safedock receives signals but doesn’t recognise them. This is a typical scenario when the U 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 on modem. If blinking, measure resistance on the ‘transmit’ line.

©Safegate Group


Date: June 2008

Version: 1.0



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 or the operating system is corrupted.

4.4.2

Step by step trouble shooting •

PC goes down and fails to restart: Replace the hard disk, and reinstall operating system according to installation manual. 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 master clock, 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

4.5.2


the network connection to the master clock: Make a PING test against the NTP server. If ping gets through, the hardware works fine. that the master clock is functioning correctly: this by checking the functionality of another system, which uses the same 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 of time, it’s a good indication that Goskrnl.exe is not running.

4.6.2


Check the service Goskrnl: Stop the service Goskrnl, and restart Goskrnl.exe from Windows Explorer. If GOS HMI starts up now, it’s an indication that the service settings are incorrect for autostart. Stop Goskrnl.exe, and reinstall the Service according to maintenance manual.



Version: 1.0



©Safegate Group


Date: June 2008

Version: 1.0


Chapter 4. Maintenance: Appendix A MAINTENANCE: APPENDIX A GOS FAULT FINDING GUIDE

GOS Server Comm error, All Concentrators Symptom ‘Comm error’ on all DGS’s.

Possible Cause Concentrators not running. Network connection failed.

Action to Rectify Start the concentrators. Check network connection cable, network, network adapter board.

Comm error, Concentrator Symptom ‘Comm error’ on all DGS’s connected to the concentrator.

Possible Cause

Action to Rectify

Concentrator not running.

Start the concentrator.

Concentrator not accessible through network.

See GOS Concentrator.

Comm error, DGS Symptom ‘Comm error’ on a single DGS.

Possible Cause

Action to Rectify



AODB connection error Symptom Entry in GOS log file:

Possible Cause GOS unable to access network.

Check network connection cable, network, network adapter board.

GOS unable to connect to AODB server.

Check AODB servers.

HKSFD – OraGos-Stand Logon/connect- ORA-12154: TNS:could not resolve GOS

Entry in GOS log file: HKSFD – OraGos TFG/connect to AODB_P_1, AODB_P_2, AODB_S_1, AODB_S_2.

Action to Rectify

©Safegate Group Document: MA-AppA-GosRUH-FaultFindGuide


Version: 1.0


Chapter 4. Maintenance: Appendix A

DGS error Symptom ‘Error nn’ reported at stand.

Possible Cause DGS error

Action to Rectify See fault finding, DGS.

NTP connection error Symptom Entry in NT Event Viewer Application Log: NTP Could not connect

Possible Cause NTP client is unable to connect to NTP server.

Action to Rectify Check network connection cable, network, network adapter board.

Hard disk failure Symptom Entry in NT Event Viewer System Log: Bad sectors ‘diskName’.

Possible Cause Hard disk failure.

Replace the hard disk.

©Safegate Group

Page 2 of 6 Document: MA-AppA-GosRUH-FaultFindGuide

Action to Rectify

Date: June 2008

Version: 1.0



GOS Concentrator Comm error, Server Symptom Comm error on all DGS’s not connected to this concentrator.

Possible Cause Concentrator not accessible through the network.


Comm error, DGS Symptom Comm error on a single DGS.

Possible Cause DGS not running. DGS modem failure. Communication line error. Serial port (Rocket port) connector board failure.

Serial port (Rocket port) board failure.

Action to Rectify Activate DGS. Check/replace DGS modem. Check/Repair communication line. Perform serial port loop back test according to Rocket port documentation. Replace serial port connector board. Replace serial port board.









Version: 1.0





Replace the hard disk.

©Safegate Group


Action to Rectify

Date: June 2008

Version: 1.0



GOS Workstation (ACC) Comm error, Server Symptom Comm error on all DGS’s.

Possible Cause Workstation not accessible through the network.


Comm error, DGS Symptom ‘Comm error’ on a single DGS.

Possible Cause

Action to Rectify












Action to Rectify Replace the hard disk.


Version: 1.0



SFDUPD connection error Symptom Error message at start of SFDUPD program: TNS: Unable to connect to destination Alias: GOS.

Possible Cause Workstation unable to connect to database at GOS server.

Check network connection cable, network, network adapter board.

©Safegate Group


Action to Rectify

Date: June 2008

Version: 1.0

Gos Manual 2hnt

Overview 5o1f4z

More details 6z3438

Related Documents c2h70

Gos Manual 2hnt

Manual Book Simrs Gos 1f3y2t

Outsourcing Gos 3s4x5l

Implementasi Simrs Gos Jadi 6f6d3p

Ph Dept Gos 3b4v37