VCA-0036-15 DGD Operators Manual 1-0 PDF

Commercial – in – Confidence
GAREX 220 VCCS
VCA-0036-15 DGD OPERATORS MANUAL
Northrop Grumman
Name Signature Date
Park Air Systems AS
Approved by Andreas Tønnesen Sign. 26-Mar-09
GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS
Commercial – in - Confidence
STATUS
Filename:
Q:\800_Documentation\VCA\VCA-0036_DGD_Operators_Manual\VCA-0036-15_DGD_Operators_Manual_1-
0.doc
Owner Andreas Tønnesen
Issue PR / CO Review Review Date Author Based on document

1.0 N/A B2563 24-Mar-09 MHO/lkr Initial issue
Changes Incorporated
Issue Paragraph Paragraph Heading/Description of Change
 Copyright 2009 Northrop Grumman Park Air Systems AS
The information contained herein is the property of Northrop Grumman Park Air Systems and may not be copied, used or
disclosed in whole or in part except with the prior written permission of Northrop Grumman Park Air Systems, or if it has been
furnished under a contract as expressly authorised under that contract. The copyright and the foregoing restrictions on copyright
use and disclosure extend to all media in which this information may be preserved including magnetic storage, punched card,
paper tape, computer printout, visual display, etc.

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS Page i of x
-Page intentionally blank-
VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

Rev. 1.0 / 26-Mar-09
Page ii of x © 2009 Northrop Grumman Park Air Systems AS
TABLE OF CONTENTS
1 INTRODUCTION .............................................................................................. 1
2 EQUIPMENT AND SERVICES ............................................................................ 3
3 TECHNICAL STATE ......................................................................................... 7
4 MAINTENANCE STATE .................................................................................. 11
5 LOGGING ON .............................................................................................. 15
5.1 Automatic Logon ................................................................................................ 16
5.2 Logon with Logon Prompt .................................................................................. 17
6 USERS AND ENGINEERING ROLES................................................................. 19

6.1 User Management.............................................................................................. 19
6.1.1 Editing a User Account ....................................................................................... 19
6.1.2 Default Password Parameters ............................................................................ 21
6.1.3 Adding a User Account....................................................................................... 21
6.1.4 Deleting a User Account..................................................................................... 22
6.1.5 Printing User Account Data ................................................................................ 22
6.1.6 Viewing and Printing Logged On Users .............................................................. 22
6.1.7 Forcing Logout of a Logged On User ................................................................. 23
6.2 Engineering Role Management .......................................................................... 23
6.2.1 Editing an Engineering Role ............................................................................... 23
6.2.2 Adding an Engineering Role ............................................................................... 28
6.2.3 Deleting an Engineering Role ............................................................................. 29
6.2.4 Assigning Screen Layout to an Engineering Role ............................................... 29
6.2.5 Printing Engineering Role Data .......................................................................... 30
7 ASSET TREE W INDOW ................................................................................. 31
8 ALARM LIST ................................................................................................ 33

8.1 Alarm Acknowledge ........................................................................................... 34
8.2 Automatic Acknowledge ..................................................................................... 34
8.3 Intermittent Faults .............................................................................................. 35
8.4 Severity Levels ................................................................................................... 35
8.5 Severity Level Audio Alarm ................................................................................ 35
8.6 User Comments ................................................................................................. 36
8.7 Columns and Sorting .......................................................................................... 36
8.8 Auto Scroll.......................................................................................................... 36
8.9 Opening Details Windows .................................................................................. 36
8.10 Printing ............................................................................................................... 37
8.11 Configuration of Severity Level Images and Audio ............................................. 37
9 MAIN VIEW ................................................................................................. 41
10 DETAIL VIEWS ............................................................................................. 43

10.1 Radio ................................................................................................................. 44
10.1.1 Channel Details .................................................................................................. 44
10.1.2 Channel Leg Details ........................................................................................... 44
10.1.3 Channels Selected for Retransmission............................................................... 45

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS Page iii of x
10.1.4 Option: Opening MARC in Channel Leg Details View......................................... 46

10.2 Radio Station ..................................................................................................... 46
10.2.1 Radio Station Overview ...................................................................................... 47
10.2.2 Radio Group Details ........................................................................................... 48
10.2.3 Transmitter Changeover..................................................................................... 49
10.2.4 MARC Option: Opening MARC in Radio Station Details View ............................ 49
10.3 Controller Working Position ................................................................................ 50
10.3.1 Controller Working Position Details .................................................................... 50
10.3.2 Position Equipment Details ................................................................................ 50
10.4 Telephone .......................................................................................................... 51
10.4.1 Telephone Service Details ................................................................................. 51
10.5 Auxiliary Equipment ........................................................................................... 51
10.5.1 Auxiliary Service Details ..................................................................................... 51
10.6 VCS ................................................................................................................... 52
10.6.1 Rack Details ....................................................................................................... 53
10.6.2 SWC/SDC Details .............................................................................................. 54
10.7 VCMS ................................................................................................................ 54
10.8 Diagnostics ........................................................................................................ 54
10.9 Channel Leg Summary....................................................................................... 55
10.10 Radio Item Status............................................................................................... 56
10.11 Event Log ........................................................................................................... 57
10.11.1 Column Sorting and Selection ............................................................................ 58
10.11.2 Filtering .............................................................................................................. 59
10.11.3 Printing ............................................................................................................... 60
10.11.4 File Export .......................................................................................................... 60
11 BASIC SETTINGS ......................................................................................... 61

11.1 Language ........................................................................................................... 61
11.2 MARC Option: MARC Router ............................................................................. 62
11.3 Colours of Graphic Elements.............................................................................. 62
11.4 Screen Utilisation ............................................................................................... 63
12 HELP FUNCTIONS ........................................................................................ 65

12.1 Tooltip Help ........................................................................................................ 65
12.2 Help on Colour Coding ....................................................................................... 65
13 APPENDIX: SERVICES AND EQUIPMENT GROUP DETAILS................................. 67

13.1 Radio Channel Services (CHANNEL ROOT) ..................................................... 71
13.1.1 Channel Leg Propagation Rules ......................................................................... 72
13.1.2 Multi-Carrier Channels Propagation Rules ......................................................... 73
13.1.3 Single-Carrier Channels Propagation Rules ....................................................... 73
13.2 Controller Working Position Services (OPERATOR POSITION ROOT) ............. 74
13.2.1 Controller Equipment Technical States .............................................................. 74
13.2.2 Controller Working Position Propagation Rules .................................................. 74
13.2.3 Telephone Line Services (GROUND/GROUND ROOT) ..................................... 75
13.2.4 Telephone Line Service Propagation Rules........................................................ 75
13.2.5 Telephone Line Group Propagation Rules.......................................................... 76
13.3 The VCMS Service (VCMS ROOT) .................................................................... 76
13.4 Auxiliary Services ............................................................................................... 77
13.5 Radio Station Equipment Groups ....................................................................... 78
13.6 VCS Equipment Groups ..................................................................................... 79

Rev. 1.0 / 26-Mar-09
Page iv of x © 2009 Northrop Grumman Park Air Systems AS
LIST OF FIGURES
Figure 1-1: VCMS server and clients with DGD 1
Figure 2-1: Equipment and Service graphical elements 3
Figure 3-1: Service and equipment graphical elements 7
Figure 4-1: Maintenance state indication 11
Figure 4-2: Maintenance details window 12
Figure 4-3: Opening maintenance state dialogue 12
Figure 4-4: Pop-up menu in maintenance details window 12
Figure 4-5: Maintenance state dialogue 13
Figure 5-1: Database logon data 15
Figure 5-2: Enabling automatic logon 16
Figure 5-3: Disabling automatic logon 16
Figure 5-4: Logout and Logon buttons on the toolbar 17
Figure 5-5: Logon prompt 17
Figure 5-6: Logon error messages 17
Figure 5-7: Logon data on the toolbar 18
Figure 6-1: Editing a user account 19
Figure 6-2: User account data 20
Figure 6-3: Assigning engineering roles to user accounts 20
Figure 6-4: Setting default password parameters 21
Figure 6-5: Adding a user account 21
Figure 6-6: Deleting a user account 22
Figure 6-7: Logging out a user 23
Figure 6-8: Editing an engineering role 24
Figure 6-9: Engineering role data, Roles tab 24
Figure 6-10: Engineering role data, Rights tab 25
Figure 6-11: Engineering role data, Event log tab 26
Figure 6-12: Engineering role data, Misc. tab 27
Figure 6-13: Auto expansion example 27
Figure 6-14: Adding an engineering role 28
Figure 6-15: Copying an engineering role 28
Figure 6-16: Deleting an engineering role 29
Figure 6-17: Assigning screen layout an engineering role 30
Figure 6-18: Placing the asset tree on top 30
Figure 7-1: Opening the asset tree window 31
Figure 7-2: Asset tree window and button on the toolbar 31
Figure 7-3: Asset pop-up menu in asset tree window 32
Figure 8-1: Alarm list window, service alarms 33
Figure 8-2: Alarm list window, equipment alarms 33
Figure 8-3: Controls in the alarm list window 34
Figure 8-4: Alarm list comment editor 36
Figure 8-5: Images configuration 37
Figure 8-6: Changing severity level image 38
Figure 8-7: Audio notification configuration 39
Figure 8-8: Changing severity level audio notification 39
Figure 9-1: Main view 41
Figure 9-2: Asset tooltip and pop-up menu 41
Figure 10-1: Message when all detail view tiles are in use 43
Figure 10-2: Selecting number of tile rows and columns 43
Figure 10-3: Channel details view with position list 44
Figure 10-4: Channel leg details view 45
Figure 10-5: Keying query and response message 45

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS Page v of x
Figure 10-6: List of channels selected for retransmission 46

Figure 10-7: Radio station details view without auto expansion 47
Figure 10-8: Radio station details view with auto expansion 48
Figure 10-9: Radio group details view with and without auto expansion 48
Figure 10-10: Changeover of radio station transmitters 49
Figure 10-11: Result of changeover 49
Figure 10-12: Controller working position details view 50
Figure 10-13: Position equipment details view 51
Figure 10-14: Changing asset mode of auxiliary equipment 52
Figure 10-15: Choosing new asset mode and results dialog 52
Figure 10-16 Updated icon illustrating the present mode of the asset 52
Figure 10-17: Pop-up menu on zoomed in rack 53
Figure 10-18: Rack details view 53
Figure 10-19: SWC/SDC details view 54
Figure 10-20: VCMS Root 54
Figure 10-21: VCMS status on toolbar 54
Figure 10-22: Diagnostics view 55
Figure 10-23: Channel Leg Summary view 55
Figure 10-24: Radio Item Status view 57
Figure 10-25: Event log 58
Figure 10-26: Event log columns selection and ordering 59
Figure 10-27: Event log filter 59
Figure 11-1: Local language setup 61
Figure 11-2: Default language and MARC router setup 61
Figure 11-3: Colour configuration 62
Figure 11-4: Editing colour name and description 63
Figure 11-5: Colour configuration 63
Figure 12-1: Colour legend 65
Figure 13-1: Equipment alarm list 68
Figure 13-2: Detail views of equipment 68
Figure 13-3: Service alarm list 69
Figure 13-4: Detail views of services 69
Figure 13-5: Detail view of the root node 70
Figure 13-6: Channel service hierarchy 71
Figure 13-7: Controller working position service hierarchy 74
Figure 13-8: Telephone line service hierarchy 75
Figure 13-9: VCMS service hierarchy 76
Figure 13-10: Auxiliary service hierarchy 77
Figure 13-11: Radio station equipment hierarchy 78
Figure 13-12: VCS equipment hierarchy 79

Rev. 1.0 / 26-Mar-09
Page vi of x © 2009 Northrop Grumman Park Air Systems AS
LIST OF TABLES
Table 3-1: Technical states 10
Table 4-1: Maintenance states 11
Table 8-1: Default severity levels 35
Table 8-2: Custom severity levels example 35
Table 13-1: Channel leg propagation rules 72
Table 13-2: Multi-carrier channels propagation rules 73
Table 13-3: Single-carrier channels propagation rules 73
Table 13-4: Controller equipment technical states 74
Table 13-5: Controller working position propagation rules 75
LIST OF ABBREVIATIONS
AAS Alternative Access System
DGD2 Diagnostics Graphical Display version 2
HMI Human - Machine Interface
MMS Monitoring and Maintenance System
SDC Switch Distribution Card
SWC Switch Card
VCCS Voice Communication Control System
VCMS Voice Control Management System
VCS Voice Control System

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS Page vii of x
GLOSSARY
Administrator user A user with User and role administration access assigned.
Alarm list An area at the lower edge of the screen used to display equipment
and services that need attention, i.e. has technical state not OK.
Asset tree The tree structure (hierarchy) of services and equipment groups
branching into lower level services and equipment groups, ending
with basic equipment as the leaves. This structure is configured in
the database of the VCMS server.
Asset tree window An optional area on the left hand side of the screen showing the
asset tree.
Channel The main and optionally standby radios that operate on the same
frequency.
Channel leg The main and optionally standby radios at a radio station site that
operate on the same frequency.
Details view area A tiled area of the screen with place for one or more windows with
detail information, like event logs, services, equipment diagnostics,
etc. The area is either at the upper right hand side of the screen, or
on the second screen for two-screen workstations.
Engineering role A set of rules for screen layout and access rights selected while
logging on, configured according to the intended tasks of a user.
Equipment Physical part of the system to which failures are assigned, leading to
a technical state other than OK.
Equipment group Group of physically related equipment or lower level equipment
groups that can be monitored as a unit and assigned an aggregated
technical state.
Main view An area of the screen above the alarm list showing a fixed graphical
overview of the monitored top-level assets.
Maintenance state Used to force equipment to report OK or Faulty technical state, and
may also inhibit the VCS from using radios and telephone line cards.
Monitoring and A part of the GAREX 220 VCMS, providing equipment and service
Maintenance System monitoring, diagnostics and some control functions.
Service Group of logically related equipment or lower level services that can
be monitored as a unit and assigned a technical state.
Technical state Used to identify which assets that need attention. Equipments with
technical state other than OK, Not monitored and Not installed are
placed in the equipment alarm list. Services with other than these
states are placed in the service alarm list.
VCMS server A server computer running the VCMS Oracle database that
connects to the VCS and client PCs running VCMS client
applications, e.g. the DGD2.
VCMS terminal A workstation connected to a VCMS server running VCMS client
applications.

Rev. 1.0 / 26-Mar-09
Page viii of x © 2009 Northrop Grumman Park Air Systems AS
NOTATION
This manual assumes that the reader is familiar with the use of a PC with keyboard and
mouse. It describes how to start and use the software. The document is not intended as a
description of the tasks, functions and duties included in the work and responsibilities of
system administrators or maintenance personnel.
The manual uses these typographical conventions for references to the controls in the user
interface:
Menus selections: Each menu selection is shown as a shaded box,
e.g. View Tree view Display
Buttons and keys: Shown in bold face as a shaded box, e.g. OK .
Captions on tabs, frames,

fields, checkboxes, radio
buttons, etc.: Shown in italics, e.g. Event log.
Technical states: Shown in bold face, e.g. OK, Loss of redundancy.
Maintenance states: Shown in bold face italics, e.g. Forced OK.
Note:
All windows shown in this manual are examples. Details, content and colours may vary from
system to system, and may show values not realistic compared to your actual system.

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS Page ix of x

Rev. 1.0 / 26-Mar-09
Page x of x © 2009 Northrop Grumman Park Air Systems AS
1 Introduction
The DGD is the client software providing the human-machine interface of the GAREX 220
Monitoring and Maintenance System (MMS). The MMS handles these aspects of the Voice
Communication Management System (VCMS):
• Monitoring of VCCS services and equipment
• Diagnostics of equipment failures, including help to locate failing parts
• Means to switch between main and standby radio transmitters, select radio receivers and
disable equipment during maintenance
The DGD is installed on standard personal computers running Microsoft Windows. The
software connects to the Oracle database on the VCMS server and displays the data in the
database in a user-friendly and intuitive way. All data is communicated through the server
database, making sure that all connected DGD clients are up to date and showing the same
data. Note that the DGD depends on an Oracle database client being installed on the client
computer. Normally the DGD is installed on VCMS terminals with one or two displays.
VCMS terminal
GAP
VCS VCMS server
GASP
Database
DGD2
Reconfiguration
Other PC
Statistics DGD2
VCMS terminal
Monitoring GAP
GASP
DGD2
DGD2
Figure 1-1: VCMS server and clients with DGD
Note to DGD users:

This manual gives a description of how to use the DGD2 application. A general note applies
to users of DGD2: After having executed a command, the user should monitor the system's
response to verify that the command was correctly executed. If not, the user should try again.

Rev. 1.0 / 26-Mar-09
© 2009 Northrop Grumman Park Air Systems AS Page 1 of 80

Rev. 1.0 / 26-Mar-09
Page 2 of 80 © 2009 Northrop Grumman Park Air Systems AS
2 Equipment and Services

In addition to monitoring equipment, the VCMS database provides a service model that
makes it possible to monitor groups of equipment that logically form a VCCS service. E.g. all
receivers and transmitters that are tuned to the same frequency form a logical radio channel.
Services may also consist of other services, e.g. a radio channel may consist of channel leg
services, each containing the main and standby radios located at a specific radio station site.
Groups of equipment are assembled into equipment groups in an equipment hierarchy. E.g.
line cards are assembled into card frames, and card frames are assembled into racks, etc.
The alarm window has two separate alarm lists, one for services and one for equipment. The
service alarm list will show failing services in order to quickly identify mitigation, while the
equipment alarm list shows faulty equipment to quickly do diagnostics and start repair.
In graphical representations, equipment is shown as rectangles and services as rectangles
with trimmed corners. Standby (not selected) equipment and connections to them are shown
with dotted lines. From a graphical element, the level below can be opened in a detail view
from a pop-up menu or by double-clicking.
Figure 2-1: Equipment and Service graphical elements
The faulty state of equipment will propagate to the services and equipment groups containing
it according to the propagation rules in the VCMS database.
The top-level services of the DGD Asset tree:

• CHANNEL ROOT: Radio channel services
• OPERATOR POSITION ROOT: Controller working position services
• GROUND/GROUND ROOT: Telephone line services
• VCMS ROOT: VCMS service
• Auxiliary services
The top-level equipment groups are:

• Radio station equipment groups
• VCS equipment groups
Chapter 0

Rev. 1.0 / 26-Mar-09

Rev. 1.0 / 26-Mar-09
Appendix: Services and Equipment Group describes in detail each group with failure
propagation rules.

Rev. 1.0 / 26-Mar-09

Rev. 1.0 / 26-Mar-09
3 Technical State
To quickly identify assets that need attention, all equipment and services are assigned a
technical state. The normal state is called OK. Assets with other states are placed in the
alarm lists to be handled by the DGD operators.
If a failure is reported to the VCMS Server, it is assigned to the equipment most likely to
cause that failure, and that equipment is set to one of the technical states Faulty, Degraded
or Loss of redundancy. If more than one failure is assigned on the same equipment leading
to the possibility for more than one technical state, the highest priority technical state is set.
Filter: Remove
spurious failures
Assign failure to
Failure
equipment
Change technical Event log

state if current
Tech. state Equipment Alarm list
state has lower
Alert clients
priority
Check if failure Event log

Failure Affected
affects other Alarm list
Tech. state equipment
equipment Alert clients
Services/ Event log

Propagate to
Tech. state Equipment Alarm list
higher levels
groups Alert clients
Figure 3-1: Service and equipment graphical elements
Then the server checks if this failure could affect the operation of other equipment, and these
are given the state Affected (unless they have the higher priority state Faulty). Normally
Affected means that the equipment is unable to report its own status due to a failure in the
connection used to report status. Affected equipment may be operational, but the MMS is
unable to decide.
The technical states of the equipment are propagated upwards through the equipment
groups and services hierarchies. This is reflected in the graphical views of the system.
The equipment alarm list is updated with new equipment states, equipment groups are never
placed in the alarms lists, and only services configured to generate alarms are placed in the
service alarm list. Note that as a failure may affect other equipment and also is propagated to
higher levels, multiple alarms and log entries may occur.
The table below shows the technical states for equipment, equipment groups and services.
The specific propagation rules for equipment groups and services are described in Chapter 0

Rev. 1.0 / 26-Mar-09

Rev. 1.0 / 26-Mar-09
Appendix: Services and Equipment Group.

Rev. 1.0 / 26-Mar-09
Priority Technical Shown in the alarm Applies to Applies to services

state lists equipment and equipment
groups
1 Faulty Yes
2 Affected Yes Yes, set according to
Yes, set according to
3 Degraded Yes failure assignment
propagation rules
Loss of rules
4 Yes
redundancy
Yes, set if unable to
Yes, set if unable to
apply any of the
5 Unknown Yes apply any propagation
assignment rules for
rule
a failure
Yes, if one of the
states above goes
6 OK away before the Yes, if no failures
alarm is Yes, set if all lower
acknowledged level assets have this
7 Not installed Yes, must be state
reconfigured in the
Not No
8 VCMS database,
monitored
inhibits other states
Table 3-1: Technical states
Every asset is in one of the technical states, and never appear with more than one entry in
the alarm lists, even if there are more failures on an equipment or more than one failing
equipment in a service. Inspecting the level below a service or equipment group by
expanding the asset tree or opening a details window will show the states of the assets at
this level. Inspecting equipment will show a list of failures causing the not OK state. The
event log will show all changes to equipment failures in addition to changes in asset technical
states.

Rev. 1.0 / 26-Mar-09
4 Maintenance State
Maintenance state applies to equipment only. There are six states, where Normal is the
default state. The other states are used for these purposes:
1 To force an equipment to report one of the technical states OK or Faulty
2 To inhibit the operational use of an equipment that is being maintained
3 A combination of the two above
The table below shows possible maintenance states and which states that applies to different
kinds of equipment:
Maintenance state Reported technical Locked for Applies to

name state operational use
Normal As is All equipment
Forced OK Always OK No
Forced faulty Always Faulty
Maintenance normal As is Radios and telephone line
Maintenance OK Always OK Yes cards only
Maintenance faulty Always Faulty
Table 4-1: Maintenance states
If the maintenance state is other than Normal, the equipment is not placed in the alarm list
even if the technical state indicates a failure. The state is however propagated to higher-level
services and equipment groups. A service may be placed in the service alarm list due to this.
Equipments with maintenance state other than Normal are shown in the graphics with a blue
line at the top. All services depending on the equipment and equipment groups containing it
will also be marked with the same kind of blue line.
Figure 4-1: Maintenance state indication
The privilege to change maintenance state is a parameter of the engineering roles. When
maintenance state is changed, the user may enter a short comment which is saved to the
event log together with the state change and user name. If the Locked option is selected,
only the user that changed state or a user with administrator privileges can change the
maintenance state for that equipment.
All equipment with maintenance state other than Normal can be viewed by clicking the
Maintenance button on the toolbar. This opens a details window with a list as shown in the
figure below:

Rev. 1.0 / 26-Mar-09
Figure 4-2: Maintenance details window
Procedure to edit maintenance state:

1 Log on as a user and role with privilege to change maintenance state.
2 Open the pop-up menu by right-clicking on the asset either in the asset tree window or on
a graphical element in the main view or in a detail view, and select Set Maintenance...
to open the maintenance state dialogue.
3 To edit equipment with maintenance state set other than Normal, you may open the
maintenance details window by clicking the Maintenance button on the toolbar. Then
double-click on the line with the equipment in demand. Right-clicking the line shows a
pop-up menu to either open the maintenance state dialogue, or set maintenance state to
Normal.
4 Select maintenance state and optionally Locked and click the OK button
....
Figure 4-3: Opening maintenance state dialogue
Figure 4-4: Pop-up menu in maintenance details window
The maintenance state dialogue serves both the purpose of editing the maintenance state
and to browse the current settings for an equipment. It has the following controls:
The checkbox Set status for underlying equipment is only enabled for the radio groups and
radio arrays. As these are equipment groups, they do not have maintenance state
themselves, so the checkbox must in this case be checked to enable the other controls.

Rev. 1.0 / 26-Mar-09
The frame Reporting sets the technical state to be reported. Normal means that the technical
state shall not be overridden, while OK and Faulty will override any technical state with the
selected state.
The checkbox Maintenance is only enabled for radios and telephone line cards. If checked,
the equipment is set to be non-selectable in the VCS.
The checkbox and frame Locked controls whether other users shall be able to edit the
maintenance state of this equipment. If checked, the text fields By user and When are
automatically filled in when the OK button is clicked. To add a comment for the
maintenance state, use the text field in the Comment frame.
Figure 4-5: Maintenance state dialogue

Rev. 1.0 / 26-Mar-09
-Page intentionaly blank-

Rev. 1.0 / 26-Mar-09
5 Logging On
Logging on to the DGD provides access to the VCMS database and to the PAE radio
monitoring and maintenance functions (MARC). Logon data for MARC is automatically
fetched from the VCMS server.
The actual logon consists of three steps:

1 When selecting database, the client is logging on to the database and fetching the list of
configured engineering roles.
2 When logon is confirmed, user name, password and engineering role are checked, and if
OK a data connection between the DGD and the database is established.
3 Then asset data and asset status are fetched, and the screen layout is drawn according
to the selected engineering role.
The logon to the database is dependent on a list of valid VCMS servers in the file
tnsnames.ora which is created during installation of the Oracle client. In addition, the
username and password to the server database must be correctly set in the DGD.exe.config,
which is located in the same folder as the DGD executable (DGD.exe). The configuration file
is in XML format, e.g.
<?xml version="1.0" encoding="utf-8"?>

<configuration>
<appSettings>
<add key="DatabaseUsername" value="my_db_usern" />
<add key="DatabasePassword" value="my_db_password" />
</appSettings>
</configuration>
Figure 5-1: Database logon data

Rev. 1.0 / 26-Mar-09
5.1 Automatic Logon

There are two modes for logging on: Automatic or with logon prompt. Automatic logon can be
enabled as shown and described below:
Figure 5-2: Enabling automatic logon
Procedure to enable automatic logon:

1 Log on to the desired database with the username and role for which automatic logon
shall be enabled.
2 From the menu, select: Configuration Auto logon…
3 A message box will ask the user to confirm the action. Confirm by clicking OK.
4 The Configuration Auto logon… is now check-marked, verifying that the automatic
logon is enabled.
To try it out: Close and restart the DGD. To disable automatic logon (set up by same or by
another user), follow the figures and procedure below:
Figure 5-3: Disabling automatic logon
Procedure to disable automatic logon:

1 From the menu, select: Configuration Auto logon…
2 A message box will ask the user to confirm the action. Confirm by clicking OK.

Rev. 1.0 / 26-Mar-09
5.2 Logon with Logon Prompt

Logging on with logon prompt requires the user to provide user name, password, engineering
role and optionally database name if more than one VCMS server is available. The logon
prompt appears if automatic logon is not enabled when the DGD is started, or if the user logs
out and then logs on again.
Figure 5-4: Logout and Logon buttons on the toolbar
The latter is done by clicking the Logout button on the toolbar, clicking OK on the prompt
to confirm, and then clicking the Logon button on the toolbar.
Figure 5-5: Logon prompt
The Database field holds a list of available VCMS servers as listed in the tnsnames.ora file.
The Role field holds a list of engineering roles as defined in the VCMS database. Both the
Username and the Password fields are case sensitive.
If logon fails, a message box with an appropriate error description will appear:
Figure 5-6: Logon error messages

Rev. 1.0 / 26-Mar-09
After successful logon the VCMS server name, username and engineering role can be seen
on the right hand side of the toolbar, next to the clock.
Figure 5-7: Logon data on the toolbar

Rev. 1.0 / 26-Mar-09
6 Users and Engineering Roles
6.1 User Management

To log on to the DGD, the user must have a user account. The account authenticates the
user through a password, and is used to track control commands in the event log. User
accounts are managed by users with the proper administrator privileges.
6.1.1 Editing a User Account

The account data for a user can be edited from the asset tree, as is shown in the figure
below.
Figure 6-1: Editing a user account
Procedure to edit user account data:

1 Log on as an administrator user.
2 If the Asset Tree window is hidden, click the Asset tree button on the toolbar to unhide
it.
3 Expand User and roles and Users nodes to see the user names. Optionally adjust the
Asset tree window width by dragging the right hand edge until the user names are visible.
4 Open the Users window by either double-click on the user name, or right-click on the user
name to open the pop-up menu and select Edit user... , or right-click the user name and
select Configuration Users and roles Edit user... from the main menu.
5 Select the User tab.
The Username field is defined when the user account is created, and cannot be changed.
The fields First name, Last name, Department, Office telephone and Mobile telephone are all
optional.
If the Password field is changed, the Confirm password field is enabled and the password
must be correctly retyped here. The password must be at least eight characters long and is
case sensitive. If a user’s password is lost, an administrator’s account must be applied to
provide a new password.
If the checkbox in the Expiry date field is checked, the user must change the password
before this date, or on the first attempt to log on after this date.
If the password is not renewed, or wrong password is entered five times within 30 minutes,
the user account becomes locked, and an administrator user must clear the User account
locked checkbox to re-enable logon for this user.

Rev. 1.0 / 26-Mar-09
Figure 6-2: User account data
When the password is renewed, the expiry date is set a configurable number of days into the
future. The user is warned to change the password on every logon from a configurable
number of days before the expiration date.
These two configurations are described in the Section 0
Default Password Parameters.
The Roles tab holds the set of engineering roles that the user must select from when logging
on. An administrator user can add and remove engineering roles by selecting a role and
clicking the >>Add>> or <<Remove button. Assigning users to engineering roles can also
be done while editing the engineering roles (which becomes effective on the next logon by
the user).
Figure 6-3: Assigning engineering roles to user accounts

Rev. 1.0 / 26-Mar-09
6.1.2 Default Password Parameters

These are in the Options window opened by selecting Configuration Options... from the
main menu. Select the General tab and look for the Password frame. The field Default
validity in days sets period from a password change until it must be renewed. The field
Warning before expiring (days) sets the period before expiry that the user is warned about it.
These settings only apply to users where the Expiry date checkbox is checked, see Section
6.1.1 Editing a User Account.
Figure 6-4: Setting default password parameters
6.1.3 Adding a User Account
Figure 6-5: Adding a user account
Procedure to add a user account:

it.

Rev. 1.0 / 26-Mar-09
4 Either right-click on the Users node to open the pop-up menu and select Add user... , or
click the Users node and select Configuration Users and roles Add user... from
the main menu.
5 Enter user name and other data in the user account data window. The Username field
cannot be changed after it has been saved, since this is the identifier of the user account.
6.1.4 Deleting a User Account
Figure 6-6: Deleting a user account
Procedure to delete a user account:

it.
4 Either right-click on the user name to open the pop-up menu and select Remove user... ,
or click the user name and select Configuration Users and roles Remove user...
from the main menu.
5 Click OK on the prompt to confirm.
The last user with administration privileges cannot be deleted.
6.1.5 Printing User Account Data

It is possible to print user account data for all or a single user by right-clicking on the Users
node or on a single user, and then clicking Print... on the pop-up menu.
6.1.6 Viewing and Printing Logged On Users

A list of users currently logged on can be viewed by expanding the Logged on users node.
The list also shows engineering role, name of computer and log on time for the user.
The list can be printed by right-clicking on the Logged on users node or on a single user, and
then clicking Print... on the pop-up menu.

Rev. 1.0 / 26-Mar-09
6.1.7 Forcing Logout of a Logged On User

An administrator user can log out another user. This will close the connection between that
DGD client and the VCMS server database.
Figure 6-7: Logging out a user
Procedure to log out a logged on user:

it.
3 Expand the User and roles node and then the Logged on users node to see the user
names. Optionally adjust the Asset Tree window width by dragging the right hand edge
until the user names are visible.
4 Either double-click on the user name, or right-click on the user name to open the pop-up
menu and select Logout user... , or left-click the user name and select Configuration
Users and roles Logout user... from the main menu.
6.2 Engineering Role Management

To make the DGD suit the needs of different technicians and supervisors, screen layout and
access privilege configurations can be stored as engineering roles. Each user account must
be associated with at least one engineering role. While logging on, the user must select one
of these roles. When proceeding, the default screen layout and restrictions on access
privileges are applied. At least one user must at all times be assigned the privileges of the
administrator.
6.2.1 Editing an Engineering Role

The access privileges for an engineering role can be edited from the asset tree, as shown in
the figure below.

Rev. 1.0 / 26-Mar-09
Figure 6-8: Editing an engineering role

Procedure to edit an engineering role:
it.
3 Expand User and roles and Engineering roles nodes to see the engineering role names.
Optionally adjust the Asset Tree window width by dragging the right hand edge until the
engineering role names are visible.
4 Either right-click on the role name to open the pop-up menu and select Edit role... , or
click the role name and select Configuration Users and roles Edit role... from the
main menu.
Figure 6-9: Engineering role data, Roles tab
On the Roles tab, the following settings are available:

Rev. 1.0 / 26-Mar-09
In the Single/multiple frame, the Restrict role logon to one user at the time checkbox decides
whether one or multiple users are allowed to use the engineering role simultaneously. This
can be used to avoid two users selecting the same engineering role.
The User to role assignment frame is used to assign which users that are allowed to log on
with this engineering role. Add and remove users by selecting a user name and clicking the
>>Add>> or <<Remove button. Assigning engineering roles to users can also be done
while editing the user accounts.
Figure 6-10: Engineering role data, Rights tab
On the Rights tab, the following settings are available:

The User and role administration checkbox in the Administration frame sets whether the
users logging on with this role are administrator users. At least one role must have this
privilege, and at least one user must be assigned to that engineering role.
In the Alarms frame, the Acknowledge alarms checkbox grants the right to acknowledge
alarms, and the Comment alarms checkbox grants the right to add and edit user comments
in the alarm list.
The access rights to set Maintenance state of equipment is controlled by the Maintenance
state frame. Both Change state and override and Change state grant the right to change
maintenance state, but Change state and override also grants the engineering role the right
to change a locked maintenance state, and should only be set for roles intended for
administrators. No control means that users with this engineering role cannot change
maintenance state.
In the Auto logon frame, the Set auto logon checkbox grants the role the right to enable
automatic logon.
In the Change Views frame, the Change main view checkbox grants the right to alter the
layout of the Asset tree, Main view and Alarm list windows, and the Change detail view
checkbox grants the right to alter the layout within the screen area for details windows. I.e.
without any of these the user cannot change the screen layout at all, except for hiding and
un-hiding the asset tree.

Rev. 1.0 / 26-Mar-09
In the Radio control frame, The TX changeover checkbox grants the role access to switch
between main and standby (A and B) radios, the Muting of receivers checkbox grants the
role access to mute receivers, and the Start MARC checkbox grants the right to start the third
party MARC program for monitoring of PAE T6 radios1.
Figure 6-11: Engineering role data, Event log tab
On the Event log tab, predefined column selection and sequence can be configured by
clicking the Setup column(s) button, and predefined filtering can be configured by clicking
the Setup filter(s) button. See Chapter 10.11 Event Log for an explanation of the column
and filtering settings.
1
The PAE T6 radios and the MARC program are not applicable to COMPACT 3.

Rev. 1.0 / 26-Mar-09
Figure 6-12: Engineering role data, Misc. tab

On the Misc. tab, the levels for the severity level sounds can be preset. Zero is silence while
100 is maximum. The Auto expansion for asset display sets the maximum number of levels
that a graphical representation of an asset shall display within itself. This is always automatic
according to the size of the window, but it is possible to limit the expansion. A setting of 1
means that elements will not expand to show sublevels. The figure below shows part of a
radio station with auto expansion set to 3 and 1.
Figure 6-13: Auto expansion example

Rev. 1.0 / 26-Mar-09
6.2.2 Adding an Engineering Role
Figure 6-14: Adding an engineering role
Procedure to add an engineering role:

it.
3 Expand the User and roles node. Optionally adjust the Asset tree window width by
dragging the right hand edge until the Engineering roles node is visible.
4 Either right-click on the Engineering Roles node to open the pop-up menu and select
Add role... , or click the Engineering Roles node and select Configuration Users and
roles Add role... from the main menu.
5 Enter engineering role name in the New role field and configure the role in the
engineering role data window (the engineering role name cannot be changed after it has
been saved). Optionally the settings of an existing role may be copied and used as a
basis for the new role. This is done by selecting a role in the Copy role box, clicking the
<<Copy button and confirming to overwrite any existing role parameters.
Figure 6-15: Copying an engineering role

Rev. 1.0 / 26-Mar-09
6.2.3 Deleting an Engineering Role
Figure 6-16: Deleting an engineering role
Procedure to delete an engineering role:

it.
3 Expand User and roles and Engineering roles nodes to see the engineering role names.
Optionally adjust the Asset tree window width by dragging the right hand edge until the
role names are visible.
4 Either right-click on the role name to open the pop-up menu and select Remove role... ,
or click the role name and select Configuration Users and roles Remove role...
from the main menu.
Observe that the last role with administration privileges cannot be deleted.
6.2.4 Assigning Screen Layout to an Engineering Role

When the screen layout is configured according to the needs of a single user or a group of
users, this layout can be stored as part of an existing engineering role. A saved layout
includes:
• Asset tree width, or hidden,
• Alarm list height,
• Alarm list sorting and auto scroll,
• Detail view area located on same screen or right hand screen,
• Main view width, if detail view area is on the same screen,
• Number of tile rows and columns on the detail view area,
• Contents of the main view and detail views.

Rev. 1.0 / 26-Mar-09
Figure 6-17: Assigning screen layout an engineering role
Procedure to assign screen layout to an engineering role:

2 Lay out the screen according to the user needs.
3 If the asset tree is visible in the layout, right-click on the role name to open the pop-up
menu and select Store role view... .
4 If the asset tree is not visible, click View Tree view On top on the main menu.
This shows the asst tree without disturbing the screen layout. Expand User and roles and
Roles nodes to see the engineering role names. Optionally adjust the Asset tree window
width by dragging the right hand edge until the role names are visible. Select the role by
clicking on the role name. Hide the asset tree by unchecking View Tree view
Display on the main menu. Then select Configuration Users and roles
Store role view... from the main menu.
Figure 6-18: Placing the asset tree on top

6.2.5 Printing Engineering Role Data

It is possible to print engineering role data for all or a single role by right-clicking on the
Engineering Roles node or on a single engineering role, and then clicking Print... on the
pop-up menu.

Rev. 1.0 / 26-Mar-09
7 Asset Tree Window

The asset tree window is located on the left hand side of the main screen, and shows the
equipment group and service hierarchies as a tree structure. In addition, the Users and roles
node has branches for viewing and handling engineering roles, user accounts and currently
logged on users. See Chapters 6 and 6.2 for details on this. Clicking the small plus or minus
boxes in front of the nodes will expand and collapse the branches, as e.g. folders in Windows
Explorer.
The window can be toggled visible or hidden by clicking the Asset tree button on the
toolbar. Checking and un-checking View Tree view Display from the main menu does
the same. This menu also has the option to select whether the asset tree window shall
occupy the left hand side screen area, or be floating on top of other windows. The latter is
used when creating a screen layout for an engineering role, see Chapter 6.2.
The width of the window can be adjusted by dragging the right hand side border. It is not
possible to adjust the height or placement of the window.
Figure 7-1: Opening the asset tree window
The top-level asset node is called Asset root. The next level is the top-level equipment
groups and services. Each of them can be expanded down to basic equipments. Each asset
node has an image showing either the equipment type, or if the asset is in the alarm list, it
shows the severity level image. If the alarm is not acknowledged the severity level image is
blinking, else it is steady.
Figure 7-2: Asset tree window and button on the toolbar

Rev. 1.0 / 26-Mar-09
Right-clicking an asset opens the asset pop-up menu as shown below. Only currently valid
selections are enabled, e.g. it is only possible to acknowledge if there is a pending alarm, it is
only possible to open equipment diagnostics if there are failures, it is only possible to open a
lower level detail view for equipment groups and services, etc.
Type icon and name of asset
Technical state
Click to open detail window
Click to acknowledge pending alarm
Click to view or change maintenance state
Click to open detail window with diagnostics
Click to print status report for asset and child assets
Figure 7-3: Asset pop-up menu in asset tree window
The Spares top-level node holds all assets that have not been given a parent in any of the
predefined equipment groups or services.

Rev. 1.0 / 26-Mar-09
8 Alarm List
The alarm list is located at the bottom of the main screen. It is actually two lists, one for
equipment and one for services. Each list is selected by clicking the appropriate tab within
the alarm list window. The height of the window can be adjusted by dragging the upper edge.
The width or placement of the window cannot be adjusted.
The right hand side of the alarm list window holds controls for the alarm list functions. Most of
these controls are also available in a pop-up menu that opens when right-clicking a line in
one of the lists.
Severity level image
Service list tab
Equipment list tab

Alarm bar
Figure 8-1: Alarm list window, service alarms
Figure 8-2: Alarm list window, equipment alarms
The alarm lists let the user easily identify failing services to do mitigation, and quickly locate
equipment with failures to do diagnostics and set priority for repair actions.
A faulty equipment or service will never appear more than once in the list. The failure
assignment rules for equipment assure that the technical state reflects the most severe
failure. Likewise will the propagation rules for services assure that the technical state of a
service is the most appropriate according to the states at the level below.
Each individual asset can be configured on the VCMS server to appear in the alarm list or
not. The asset will, independently of this, show its technical state in the asset tree and
graphical windows.

Rev. 1.0 / 26-Mar-09
8.1 Alarm Acknowledge

To distinguish between new and recognized alarms, each alarm is either not acknowledged
or acknowledged. A not acknowledged alarm will have a blinking image in the Severity
column.
As long as there is at least one not acknowledged alarm in the equipment or service alarm
list, this is indicated with blinking of the most severe severity image on the list tab and
blinking of the red alarm bar at the top of the alarm window. When all alarms are
acknowledged, the tabs show the most severe severity image in the list without blinking, and
the red alarm bar is steady.
Procedure to acknowledge one alarm:

1 Select the alarm in one of the alarm lists by clicking on it.
2 Click on the Ack selected button.
Procedure to acknowledge all alarms:

1 Click on the Ack all... button.
2 Confirm by clicking the OK button when prompted.
Procedure to acknowledge a selection of alarms within a list:

1 Select the alarms by clicking on them while holding the Shift or Ctrl button on the
keyboard.
2 Click on the Ack selected... button.
3 Confirm by clicking the OK button when prompted.
Please observe that alarms can be acknowledged from the pop-up menu on asset tree
nodes and assets in graphical windows.
Figure 8-3: Controls in the alarm list window
8.2 Automatic Acknowledge

A service alarm will be automatically acknowledged when all the equipment alarms that
influenced the service alarm are acknowledged. On the other hand, an equipment alarm will
be automatically acknowledged when all the services that the equipment influenced are
acknowledged.
Example: Both a transmitter and a receiver within a channel leg may get the technical state
Faulty in the equipment alarm list, and the channel leg is then set to Loss of redundancy in
the service alarm list. Acknowledging the channel leg service will cause both the transmitter
and receiver alarm to be automatically acknowledged.

Rev. 1.0 / 26-Mar-09
If instead the transmitter alarm is acknowledged, the channel leg service is still not
acknowledged. When then the receiver is acknowledged, the channel leg service will be
automatically acknowledged.
Another example: A line card that is Faulty is included in two different line services.
Acknowledging the line card will cause both line services to be automatically acknowledged,
but both line services must be acknowledged to automatically acknowledge the line card.
8.3 Intermittent Faults

If an asset reports a technical state other than OK and this causes the asset to be placed in
the alarm list, the asset will remain in the alarm list until it is acknowledged. This stands even
if the state of the asset meanwhile has changed to OK. In this case, the asset disappears
from the alarm list when it is acknowledged.
8.4 Severity Levels

To ease the task of prioritizing the handling of alarms, each asset is assigned a severity level
according to its technical state. The default configuration is shown below:
Technical state
Faulty Affected Degraded Loss of Unknown OK
redundancy
SL1 SL1 SL2 SL3 SL4 SL4
Table 8-1: Default severity levels
The severity level for each asset and technical state is configurable on the VCMS server. An
example is shown in the table below:
Technical state
Asset Faulty Affected Degraded Loss of Unknown OK
redundancy
Service A SL1 SL1 SL1 SL3 SL3 SL4
Service B SL2 SL2 SL2 SL2 SL4 SL4
Equipment A SL1 SL1 SL2 SL1 SL2 SL4
Table 8-2: Custom severity levels example
8.5 Severity Level Audio Alarm

There are different sounds associated with the severity levels. When a new alarm is placed
in the equipment or service alarm list, the audio of the most severe, not acknowledged alarm
in both lists is played. The audio can be configured to be played once, or to be repeated until
the alarm is acknowledged.
Repeating audio may be stopped by clicking the Silence button. Any new alarm will restart
the audio.
Acknowledging the most severe alarm will cause recalculation of what alarm to be played,
unless the Silence button has been clicked and no new alarms have occurred. Audio
alarms depend on audio being installed on the computer and turned on. The volume should
be set to a proper level.

Rev. 1.0 / 26-Mar-09
8.6 User Comments

A short comment may be added to each of the assets in the alarm lists. It may be edited or
deleted at any time. The comment is linked to the asset record. It will remain in the alarm list
even if the asset changes technical state. If the asset disappears from the alarm list and then
reappears, the comment is deleted. All changes to comments are saved to the event log. The
privilege to add comments may be denied for an engineering role by an administrator.
Procedure to add or edit a comment:
1 Select a line in one of the alarm lists.
2 Click on the Comment button to open the comment editor.
3 Write the comment.
4 Click the OK button to save the comment.
Figure 8-4: Alarm list comment editor
8.7 Columns and Sorting

The alarm lists have the following columns:
1 Severity with an image according to the alarm severity level - blinking for not
acknowledged alarms
2 Date and time shows the last change to the technical state of this asset in UTC time
3 Name identifies the asset
4 State shows the technical state of the asset
5 Equipment in the service alarm list shows the equipment causing this alarm, Service(s) in
the equipment alarm list shows the services affected for equipment alarms
6 User comment shows a an optional text entered by a DGD operator.
The width of the columns can be adjusted by dragging the column border on the header line.
The alarms are sorted either by severity level or by date and time. The default sorting for
each of the two lists is set according to the engineering role. The sorting is changed by
clicking one of the radio buttons in the Sort by frame placed top right in the alarm list window.
8.8 Auto Scroll

If sorting by date and time is selected, the Auto scroll checkbox is enabled. When checked,
new alarms are automatically brought into view by scrolling the alarm list. This is useful when
awaiting new alarms and there are many alarms in the list.
It is recommended, however, to turn this feature off when doing selections in the alarm list,
as the list may auto scroll causing the wrong alarm to be selected.
8.9 Opening Details Windows

A service or equipment in the alarm list may be viewed graphically in a detail view by
selecting the alarm and then clicking the Details... button, or by double-clicking the alarm. If
the selected asset is a basic equipment, the level above will be opened.

Rev. 1.0 / 26-Mar-09
8.10 Printing
The service or equipment alarm list may be previewed and sent to a connected printer by
selecting one of the alarm lists and then clicking the Print... button on the alarm list. You
must select printer before preview is shown.
8.11 Configuration of Severity Level Images and Audio

The images shown in the Severity column and on the alarm list tabs and the audio alarm
sounds are configurable for engineering roles with administrator privileges.
Procedure to change a severity level image:

1 Select Configuration Options from the main menu.
2 Select the Images tab in the Options window.
3 Select “AlarmImageList” in the Image list combo box.
4 Select one of the severity levels and click the Change... button (or double-click on the
line). The first line (with index 0) is the image displayed when blinking OFF for all the
severity levels. The next lines (with indices 1 to 4) is displayed when blinking ON for each
severity level.
5 Click the Change... button in the Set image form dialogue.
6 Browse for the new file, of type “.bmp” or “.ico”, and click the Open... button.
7 Optionally edit the image description.
8 Click the OK... buttons in the dialogue and in the Options window.
Figure 8-5: Images configuration

Rev. 1.0 / 26-Mar-09
Figure 8-6: Changing severity level image
Procedure to change a severity level audio notification:

1 Select Configuration Options from the main menu.
2 Select the Sounds tab in the Options window.
3 Select one of the severity levels audio notifications and click the Change... button (or
double-click on the line).
4 Click the Sound... button in the Sound information... dialogue.
5 Browse for the new file, of type “.wav”, and click the Open... button.
6 Check the Looping box if the audio is to be played repeatedly. If not checked, the file is
played once every time it is triggered.
7 Click the OK button.
8 Optionally test the sound by clicking the Play and Stop buttons.
9 Click the OK buttons in the Options window.
The audio level for each severity level is set individually for each engineering role, see
Section 6.2.1 Editing an Engineering Role.

Rev. 1.0 / 26-Mar-09
Figure 8-7: Audio notification configuration
Figure 8-8: Changing severity level audio notification

Rev. 1.0 / 26-Mar-09

Rev. 1.0 / 26-Mar-09
9 Main View
The main view above the alarm list gives a graphical overview of the system. It is divided into
groups of main services and equipment. The content is fully configurable for each
engineering role. The engineering role setup also decides if the user is able to change the
main view. The example below shows channel groups to the left; radio stations, telephone
services and auxiliary equipment in the middle; and a sample rack to the right.
Figure 9-1: Main view
Hovering the cursor on an element will show asset type and name as tooltip. Right-clicking
will open the asset pop-up menu, while double-clicking will open a detail view with the lower
level for services and equipment groups, equipment diagnostics if there are faults, or no
action if no lower level and no faults.
Figure 9-2: Asset tooltip and pop-up menu

Rev. 1.0 / 26-Mar-09
Procedure to assign screen layout to an engineering role:

2 If the asset tree shall be a part of the layout, click View Tree view Inline on the
main menu and drag the right hand asset tree border to adjust the window size.
3 Else click View Tree view On top . The asset tree is placed over the main view
layout, and will not be visible in the saved layout.
4 Expand the Users and roles node and then the Engineering roles node.
5 Drag the top alarm list border to adjust the alarm list size.
6 Drag the border between the main view and detail view area to a suitable position, or
drag the detail view area to the right hand screen if two screens are used.
7 Expand the asset tree nodes until the wanted asset is shown, and drag it with the mouse
into the main view. A shaded area indicates alignment to other assets. Drop the asset at
the indicated position.
8 Drag the borders between the assets in the main view to resize contents.
9 Right-click on the role name in the asset tree to open the pop-up menu and select
Store role view... , or click Configuration Users and roles Store role view... on the
main menu.
11 See also Section 6.2.4 Assigning Screen Layout to an Engineering Role.

Rev. 1.0 / 26-Mar-09
10 Detail Views
The detail view area is placed on either the right-hand side of the main view, or on the right-
hand screen if two screens are used. It is split in tiles, where a detail view may occupy a
rectangle with any number of tiles from one to all. The privilege to change the detail view
area must be granted by the engineering role’s access rights.
A new detail view opens in a single tile in the first free location from left to right and top to
bottom. Placing the cursor on a border towards an unused tile, it will appear as an X, and
clicking will remove the border, expanding the view into the empty tile. If the border cannot
be deleted, the cursor changes into a ‘no parking’ sign. This procedure can be repeated until
all tiles are used by the view.
When there are no more free tiles, and a detail window is attempted opened, the user gets
the message shown below.
Figure 10-1: Message when all detail view tiles are in use
Opening other detail views that are already opened will place focus on the existing window.
The number of tile rows and columns can be set by clicking View
Grid columns and rows... on the main menu. The default numbers are according to what
was saved with the engineering role.
Figure 10-2: Selecting number of tile rows and columns
A detail view can be opened in many ways:

• clicking on a detail view button on the toolbar (e.g. Event log),
• selecting View and a detail view item (e.g. Event log) from the main menu,
• selecting Open... or Diagnostics... from either the pop-up menu of an asset in the main
view, an asset in a detail view or an asset node in the asset tree,
• double-clicking on an asset in the main view, an asset in a detail view or an asset node in
the asset tree,
• dragging a node from the asset tree and dropping it into a tile, or
• clicking the Details... button in the alarm list.

Rev. 1.0 / 26-Mar-09
A detail view can be dragged and dropped into an unused tile. If it occupies more than one
tile, it will however be reduced to occupy the single target tile. After the drag-and-drop
operation, the view may be expanded into empty tiles as usual. Detail views are closed
individually by clicking the X in the upper right hand corner. The entire detail view area can
be cleared by clicking the Close detail views button on the toolbar, or selecting View
Close detail views from the main menu.
Most of the detail views for services and equipment groups are showing the assets on the
lower level as boxes. Some views are however specialised to provide graphical information
on how the assets are coupled, or group assets in a specialised way. These are explained in
the following sections.
10.1 Radio
There are five detail views for the radio services:
• Channels Root showing all the channel groups in the system (standard boxes)
• Channel Group showing all the channels in a group (standard boxes)
• Channel showing the channels legs and coupling to position equipment
• Channel Leg showing the radios in a single leg with control for receiver muting and
transmitter changeover
• Channels selected for retransmission
10.1.1 Channel Details

This view has two or more tabs. All but the last tab selects one of the channel legs that the
channel consists of. See the next section for a description of the channel leg details view.
The last tab shows a list of position equipment that has selected this channel, and which
mode is selected. The table can be sorted ascending or descending on any of the three
columns by clicking the column header.
Figure 10-3: Channel details view with position list
10.1.2 Channel Leg Details

The channel leg is normally shown on a tab within the channel detail view. A single channel
leg may however be opened from the asset tree. It shows the leg, the contained radios and
logical connections.

Rev. 1.0 / 26-Mar-09
Figure 10-4: Channel leg details view
A transmitter changeover can be initiated by clicking the radio button of the not selected
transmitter (dashed and dimmed line). If the selected transmitter has technical state not OK
or maintenance state other than Normal, a confirmation is required before proceeding. This
starts a request to the VCS for a changeover, and if successful the graphics will shortly be
updated with the new selection. If the request fails, a warning message will appear.
A receiver may be muted by un-checking the checkbox on the logical line between the
channel leg and the receiver. The user must confirm before a request is sent to the VCS. The
graphics will shortly be updated with the new state. If the request fails, a warning message
will appear.
It is possible from this detail view to query which position equipments that are keying the
channel. Select Keying query from the pop-up menu of the channel leg. After a while the
VCS will respond and a list of position equipments with used transmitter will appear.
Figure 10-5: Keying query and response message
10.1.3 Channels Selected for Retransmission

A list of channels selected for retransmission can be opened in a details view by clicking the
X-Coupled Channels button on the toolbar, or by selecting View X-Coupled channels
from the main menu. The list can be sorted ascending or descending on either of the two
columns by clicking the column header.

Rev. 1.0 / 26-Mar-09
Figure 10-6: List of channels selected for retransmission
10.1.4 Option: Opening MARC in Channel Leg Details View

Multi-Access Remote Control (MARC) is an option. MARC is an advanced Remote Control
and Monitoring System (RCMS) for the E1-RIC units and T6-series radio equipment. If the
MARC application on your local client is running properly, the MARC page for a selected
asset may be opened directly from the Channel Leg Details view.
The MARC asset on the Toolbar, refer to chapter , shall be green. To open MARC, right-click
on the radio asset (receiver or transmitter), select Open on the pop-up menu. The MARC
application will open, showing the MARC page for the selected asset.
When trying to open the radio asset, while the MARC asset on the Toolbar is red (e.g MARC
local router is not running) nothing will happen.
The MARC asset on the toolbar may still appear green even if the local MARC Navigator is
not running. In this case the system will respond with the error message “Problem with UDP
Connection with MARC. No reply received.”
10.2 Radio Station

The radio station view is applicable for digital radio connections, i.e. T6 radios or analogue
radios connected via protocol converter units.
There are five detail views for radio stations:
• Radio Stations Root showing all the radio stations in the system (standard boxes)
• Radio Station showing the main equipment groups of a single station
• Radio Group showing the contained radio arrays
• Radio Array showing a single E1-RIC and the connected radios (standard boxes)
• Auxiliary Equipment showing all auxiliary equipment at the radio station (standard boxes)

Rev. 1.0 / 26-Mar-09
10.2.1 Radio Station Overview

The Radio Station detail view shows all the radio groups in a radio station as a chain of
boxes according to their connections through E1-RICs. It also shows the state of the
connections to switch cards and the switch card within the local VCS. At the bottom, there is
an equipment group for the auxiliary equipment at the site.
Figure 10-7: Radio station details view without auto expansion

Rev. 1.0 / 26-Mar-09
Figure 10-8: Radio station details view with auto expansion
10.2.2 Radio Group Details

The Radio Group detail view shows all the radio arrays in the group as a chain of boxes
according to their connections through E1-RICs.
Figure 10-9: Radio group details view with and without auto expansion

Rev. 1.0 / 26-Mar-09
10.2.3 Transmitter Changeover

It is possible to switch to A or B transmitters for a radio station or a radio group. This is done
from the node in the asset tree or the pop-up menu on the graphical element as depicted
below:
Figure 10-10: Changeover of radio station transmitters
Figure 10-11: Result of changeover
Procedure to switch to A or B transmitters:

1 Right-click the radio station or radio group and select either Switch to TX A radios... or
Switch to TX B radios.....
2 Confirm or abort the action by clicking the OK or Cancel button respectively.
3 A separate window will display the results of the changeover.
10.2.4 MARC Option: Opening MARC in Radio Station Details View

As for the Channel leg Details View, the MARC page for a selected asset may be opened
directly from the Radio Station Details View.
The MARC asset on the Toolbar, refer to chapter , shall be green. To open MARC, right-click
on the radio asset (receiver or transmitter), select Open on the pop-up menu. The MARC
application will open showing the MARC page for the selected asset.

Rev. 1.0 / 26-Mar-09
For further information refer to chapter 0
10.3 Controller Working Position

There are four detail views for the controller working position services:
• Controller Working Positions Root showing all the controller working position groups in
the system (standard boxes)
• Controller Working Positions Group showing all the controller working positions in a
group (standard boxes)
• Controller Working Position showing the position equipment and coupling to channels
used
• Position Equipment showing the equipment and links within a single position equipment
10.3.1 Controller Working Position Details

This view has one or more tabs. Each tab selects one of the position equipments that the
controller working position consists of. See the next section for a description of the position
equipments details view.
Figure 10-12: Controller working position details view
10.3.2 Position Equipment Details

The position equipment is normally shown on a tab within the controller working position
detail view. A single position equipment may however be opened from the asset tree.
The view is divided in two. The left hand side holds a graphical view of the position
equipment (including any monitored powersupplies) and the two connections to the VCS.
The right hand side shows a list of the channels selected, and in which mode each channel is
selected. The list can be sorted ascending or descending on any of the columns by clicking
on the column headers.

Rev. 1.0 / 26-Mar-09
Figure 10-13: Position equipment details view
10.4 Telephone
There are three detail views for the telephone services:
• Telephone Services Root showing all the telephone service groups in the system
(standard boxes)
• Telephone Service Group showing all the telephone services in a group (standard boxes)
• Telephone Service showing basic equipment
10.4.1 Telephone Service Details

A telephone service may consist of telephone line cards and M-modules on switch cards.
10.5 Auxiliary Equipment

There are two detail views for the auxiliary equipment services:
• Auxiliary Services Root showing all the Auxiliary services (standard boxes)
• Auxiliary Service showing basic auxiliary equipment (standard boxes)
10.5.1 Auxiliary Service Details

An auxiliary service may consist of any auxiliary equipment. Depending on the equipment, it
may support an user-initiated change of mode. This is the case for the relay as shown in the
figure below:

Rev. 1.0 / 26-Mar-09
Figure 10-14: Changing asset mode of auxiliary equipment
Figure 10-15: Choosing new asset mode and results dialog
Procedure to change asset mode:

1 Right-click the asset and select Change asset mode....
2 In the popup window, select the new asset mode and click OK.
3 The result is displayed in a new result window.
After choosing a new mode, the icon displaying the current mode of the asset will be
updated:
Figure 10-16 Updated icon illustrating the present mode of the asset
10.6 VCS
There are three detail views for the VCS:
• VCS Root showing all VCSs known to this VCS system (standard boxes)
• VCS showing rack groups (standard boxes)
• Rack showing graphically a single rack with fitted cards and panels
• Frame showing the contained cards (standard boxes, can only be opened from the asset
tree)
• SWC/SDC showing the card with installed M-modules and links
Even if other VCSs are displayed in the VCS root, they are not monitored and further
exploration is not available.

Rev. 1.0 / 26-Mar-09
10.6.1 Rack Details

The rack details view shows a rack exactly as it looks
to easily identify the location of faulty cards.
If text on a card is too small to be displayed, the name
can be seen as a tooltip by pointing with the mouse at
the card, or by right-clicking the card to display the
pop-up menu. The latter will also show the technical
and maintenance states.
Figure 10-17: Pop-up menu on zoomed in rack

The view also supports zooming and panning.
Zooming is done by clicking on the - or + buttons to
the left of the bottom scrollbar, by pressing the - or
+ keys on the keyboard, or by using the scroll
function on the mouse.
Panning is only available when the rack is partially
viewed. Use the scrollbars, the arrow keys on the
toolbar, or click and drag on the white area to the left
or right of the rack graphics.
Figure 10-18: Rack details view

Rev. 1.0 / 26-Mar-09
10.6.2 SWC/SDC Details

The SWC/SDC details view has three columns. To the left is the SWC/SDC itself, in the
middle is the installed M-modules (none, one or two), and to the right are the links controlled
by the card.
Figure 10-19: SWC/SDC details view
10.7 VCMS
The VCMS self monitoring consists of five elements, which also can be seen on the toolbar:
• DGD client main thread (this can also be monitored by watching the clock on the toolbar:
It should be updated every second)
• Connection to the VCMS server (on the toolbar, the name of the database is shown when
connected)
• MARC Option: Connection to the local instance of the MARC third party software for
monitoring of PAE T6 radios
• Status of the VCMS network, as monitored by the third party software NimBUS
• Connection from the VCMS server to the VCS
Figure 10-20: VCMS Root
Figure 10-21: VCMS status on toolbar
The boxes on the toolbar do not have pop-up menus. Diagnostics must by opened from the
asset tree, the alarm list or a graphical view.
10.8 Diagnostics
The diagnostics detail view is available for basic equipment that has at least one fault. The
view is opened in several ways:
• double-clicking the equipment in a graphical view,

Rev. 1.0 / 26-Mar-09
• right-clicking the equipment in a graphical view and selecting Diagnostics... from the
pop-up menu, or
• right-clicking the equipment in the asset tree and selecting Diagnostics... from the pop-
up menu.
Figure 10-22: Diagnostics view
The view is divided in two. The left hand side holds a list of pending faults. By clicking on one
of them, the right-hand side will show either a short explanation, corrective actions, or a list of
spare parts, depending on the tab selected at the top of the right hand side.
The list of faults shows the faults that were pending when the view was opened. To get an
updated list, click the Refresh button.
All faults with their explanation, corrective actions and spare parts can be previewed and
sent to a connected printer by clicking the Print... button.
10.9 Channel Leg Summary

The Channel Leg Summary view is a view that displays available channel legs in the system.
The view is layed out as a vertical list of channel legs where the first column displays the
channel leg service, the second column displays the leg’s transmitters and the third column
displays the leg’s receivers. The figure below shows an example of a Channel Leg Summary
detail view.
Figure 10-23: Channel Leg Summary view

Rev. 1.0 / 26-Mar-09
The radio assets shown in the view are not labelled with their symbolic name. To get the
symbolic name of a radio, the user may right-click the radio to show the regular pop-up menu
for that asset.
As with the regular channel leg detail view, this view allows the user to change the
main/standby state of individual transmitters and to mute/unmute individual receivers. In
addition, the view holds buttons in the bottom part of the view that enables the user to
change the main/standby state or mute/unmute radios across all channel legs in one user
action. For the transmitters one button per radio column is provided. Clicking one of these
buttons will set all transmitters in the selected radio column to the main state (selected). For
the receivers, two buttons are provided per radio column. The button at the top will unmute
(select) all radios in the selected radio column, while the button at the bottom will mute
(deselect) all radios in the selected radio column.
Clicking any of the buttons will ask the user to confirm the action before it is executed. After
confirming, the user will be presented with a separate pop-up window displaying the status of
the operation.
Note that the Channel Leg Summary view does not display legs that are empty or legs that
are not placed in a channel.
10.10 Radio Item Status

The Radio Item Status view is a view that displays all positions in the system and their radio
selections. The view is layed out as a grid showing the positions in the leftmost column and
the different radio items in the other columns. The figure below shows an example of the
Radio Item Status detail view.

Rev. 1.0 / 26-Mar-09
Figure 10-24: Radio Item Status view

The positions are color coded with their technical state, while the radio items are color coded
with their selection state. Three different selection states are shown:
• Rx selected
• Tx selected
• Cross Coupled
To view the color codes, select Help Colors... from the main menu to open a color
legend. The colors representing the selection states are configurable by selecting
Configuration Options from the main menu and then selecting the Colors tab.
Note that this view is not refreshed automatically. To update the status of positions and radio
items, click the . Refresh button.
10.11 Event Log

The event log can be viewed in one or more detail view windows. The windows are opened
by clicking the Event log button on the toolbar, or by selecting View Event log from the
main menu. It contains these events:
• Changes to equipment failures
• Changes to asset technical states
• Request to change equipment maintenance state
• Changes to maintenance states
• Request to switch between redundant equipment

Rev. 1.0 / 26-Mar-09
• Changes to selection of redundant equipment

• Request to mute receivers
• Changes to receiver muting
• Request for operators keying channels
• Result of operators keying channels
• Acknowledge of asset alarms
• Changes to the user comment of asset alarms
• Successful logon and logoff
• Failed logon attempts
• Changes to engineering roles
• Changes to user accounts
• Reconfiguration of the user interface
Figure 10-25: Event log
10.11.1 Column Sorting and Selection

The event log may be sorted on any of the columns, in ascending or descending order. This
is done by clicking on the column header once or twice. A small icon will show on which
column the list is currently sorted and in which order.
The columns may be hidden or placed in a specific sequence by clicking the Columns
button on the Event Log toolbar.
In the Event log columns dialogue, check the columns to be visible, and click the up and
down arrows to change the order of appearance.

Rev. 1.0 / 26-Mar-09

Figure 10-26: Event log columns selection and ordering
10.11.2 Filtering
There are many options to apply filters to select a subset of the available events. The filters
are changed by clicking the Filter button on the Event Log toolbar.

Figure 10-27: Event log filter
If no checkboxes in a field is checked, this filter is not applied. If at least one checkbox is
checked, only events matching the selection will be shown.

Rev. 1.0 / 26-Mar-09
10.11.3 Printing
The event log with the current selection of columns, sort order and filtering can be previewed
and sent to a connected printer by the Print button on the Event Log toolbar.
10.11.4 File Export

The event log with the current selection of columns, sort order and filtering can be exported
to a text file by the Export log button on the Event Log toolbar. The file format has
semicolon as field separator and carriage return/line feed (ASCII 13 and 10) as record
separator. The first record contains the column headers and is followed by double carriage
return/line feed. This format can easily be imported into many tools for further analysis, e.g.
Microsoft Excel.

Rev. 1.0 / 26-Mar-09
11 Basic Settings
11.1 Language
There are two levels of language settings: One for the default language of all clients, and one
for the language of the local client. The common, default language is set by selecting
Configuration Options from the main menu. Select the General tab. Select one of the
languages available in the frame Default language.
To set the language of local client, select Configuration Change language from the main
menu. Select a language from the Language combo and click OK .
Figure 11-1: Local language setup
This will replace all text strings in the user interface except for standard Windows message
and dialogue windows. These follow the language set by the operating system.
Figure 11-2: Default language and MARC router setup

Rev. 1.0 / 26-Mar-09
11.2 MARC Option: MARC Router

The MARC application will not work if the port numbers to be used are wrong. To set port
numbers, select Configuration Options from the main menu. Select the General tab. The
figure above shows standard settings in the frame MARC router.
11.3 Colours of Graphic Elements

The colours on graphical elements for technical states and maintenance state can be set
according to the preset windows palette or to any RGB value. The changes to the colours are
saved to the VCMS server and hence affect all clients.
Select Configuration Options from the main menu. Select the Colours tab. The current
configuration is shown. Select the colour to be changed in the Colour function combo and
click the Change... button.
Figure 11-3: Colour configuration
Edit the Name and Description fields. Then click the Change... button to open the colour
palette.

Rev. 1.0 / 26-Mar-09
Figure 11-4: Editing colour name and description
Select a colour from the palette, or click the Define Custom Colours button and enter RGB
values.
Figure 11-5: Colour configuration
11.4 Screen Utilisation

To allow more of the screen to be used for the alarm list, asset tree and graphical views,
there are two options under the View menu.
By unchecking View Border the standard windows will be removed. This is only
recommended when the DGD window is maximised to fill the entire screen.
By unchecking View Status bar the status bar at the bottom of the DGD window will be
removed.

Rev. 1.0 / 26-Mar-09

Rev. 1.0 / 26-Mar-09
12 Help Functions
12.1 Tooltip Help

When holding the mouse pointer on an control, a short description of the function will appear.
12.2 Help on Colour Coding

Select Help Colours... from the main menu to open a colour legend.
Figure 12-1: Colour legend

Rev. 1.0 / 26-Mar-09

Rev. 1.0 / 26-Mar-09
13 Appendix: Services and Equipment Group Details

Services and equipment groups form hierarchies with equipment at the lowest level.
Equipment groups allow for monitoring a large number of physically related equipment with a
single indication of which groups that need attention. Services allow monitoring groups of
logically related equipment.
The depth of the hierarchies range from two to six levels. The levels above the bottom
equipment level will never generate alarms for equipment groups, since one alarm from the
bottom level equipment is sufficient to bring attention to the physically related hierarchy. E.g.
it would be confusing to have alarms on a failing line card, the card frame and the rack.
Services may generate alarms in a separate service alarm list. Normally this applies to only
one of the levels above the equipment level. The exception is channels and channel legs
where both service levels generate alarms. Which service level that generates alarms may
be reconfigured in the VCMS database. The default configuration is shown in the figures of
the following sections by shaded boxes for assets that generate alarms.
The technical states of services and equipment groups are set according to pre-programmed
propagation rules based on the states of the child assets. This is described for each
equipment group and service in the following sections.
For the top-level services, these general rules apply:

1 If all child services are OK, then the top-level service is OK.
2 If one or more child service is Loss of redundancy and all the others are OK, then the
top-level service is Loss of redundancy.
3 If at least one child service is Faulty, Affected or Degraded, then the top-level service is
Degraded.
4 If all child services are Faulty or Affected, then the top-level service is Faulty.
The technical states Not installed and Not monitored are not described in the specialized
propagation rules. They affect the parent state according to the following general rules:
1 If all children are Not installed, then the parent is Not installed.
2 If all children are Not monitored, then the parent is Not monitored.
3 If all children are either Not monitored or Not installed, then the parent is Not
monitored.
4 If at least one child has another state than Not monitored or Not installed, the children
with Not monitored or Not installed are ignored, i.e. the propagation rules described in
the following sections apply based on the children with other states.
The technical state Unknown is not described in the specialized propagation rules. This
state should normally not appear, as it indicates that there is an unhandled equipment failure,
or unhandled combination of child states.
The figures below depict an example, where a line card fault produces both equipment and
service alarms. Technical states changes through propagation.

Rev. 1.0 / 26-Mar-09
Figure 13-1: Equipment alarm list
In the figure above, the alarm list for equipment is depicted. The window shows that there is
an alarm for the FLC01 LC09 line card.
Figure 13-2: Detail views of equipment
The figure above depicts the equipment detail views for the VCS. Notice how the technical
state is propagated up through the other equipment views. Here, the line card with a fault is
represented as a red box while the brown boxes are used for indicating that the asset is
degraded.

Rev. 1.0 / 26-Mar-09
Figure 13-3: Service alarm list
The line card fault also causes a service alarm to be generated, which is placed in the
service alarm list as shown above.
Figure 13-4: Detail views of services
The figure above shows how the technical state is propagated up through the service
hierarchy.

Rev. 1.0 / 26-Mar-09
Figure 13-5: Detail view of the root node
As shown in the root node depicted above, both the GROUND/GROUND ROOT service and
the ROOT VCS equipment group is degraded.

Rev. 1.0 / 26-Mar-09
13.1 Radio Channel Services (CHANNEL ROOT)

The main and optionally standby radios at a radio station site that operates on the same
frequency are configured into a service called a channel leg. Several channel legs of same
frequency are grouped together to form the radio channel, and this forms the primary radio
service. To supervise e.g. a sector where multiple channels are in use, radio channels are
grouped into channel groups. Both channel and channel leg services generate alarms.
Channels
Channel Channel Channel

group group group

leg leg leg
Receiver Receiver Transmitter Transmitter

A B A B
Figure 13-6: Channel service hierarchy

Rev. 1.0 / 26-Mar-09
13.1.1 Channel Leg Propagation Rules

The following rules apply to all channel legs:
1 If all radios in the channel leg are OK, then the channel leg is OK.
2 If one receiver and/or one transmitter have Faulty or Affected and the other radios are
OK, then the channel leg is Loss of redundancy.
3 If all receivers and/or all transmitters in the channel leg have Faulty or Affected then the
channel leg is Faulty.
The following state table describes the effect of these rules in a channel leg with two
receivers and two transmitters:
RxA TxA RxB TxB Channel leg

1 OK OK OK OK OK
2 Faulty/Affected OK OK OK Loss of redundancy
3 OK Faulty/Affected OK OK Loss of redundancy
4 Faulty/Affected Faulty/Affected OK OK Loss of redundancy
5 OK OK Faulty/Affected OK Loss of redundancy
6 Faulty/Affected OK Faulty/Affected OK Faulty
7 OK Faulty/Affected Faulty/Affected OK Loss of redundancy
8 Faulty/Affected Faulty/Affected Faulty/Affected OK Faulty
9 OK OK OK Faulty/Affected Loss of redundancy
10 Faulty/Affected OK OK Faulty/Affected Loss of redundancy
11 OK Faulty/Affected OK Faulty/Affected Faulty
12 Faulty/Affected Faulty/Affected OK Faulty/Affected Faulty
13 OK OK Faulty/Affected Faulty/Affected Loss of redundancy
14 Faulty/Affected OK Faulty/Affected Faulty/Affected Faulty
15 OK Faulty/Affected Faulty/Affected Faulty/Affected Faulty
16 Faulty/Affected Faulty/Affected Faulty/Affected Faulty/Affected Faulty
Table 13-1: Channel leg propagation rules

Rev. 1.0 / 26-Mar-09
13.1.2 Multi-Carrier Channels Propagation Rules

The following propagation rules apply to multi-carrier channels:
1 If all channel legs are OK, then the channel is OK.
2 If one or more channel legs are Loss of redundancy and the others are OK, then the
channel is Loss of redundancy.
3 If at least one channel leg is Faulty or Affected, then the channel is Degraded.
4 If all channel legs are Faulty, then the channel is Faulty.
The following table shows the effects for a two-legged channel:
Channel leg 1 Channel leg 2 Channel

1 OK OK OK
2 Loss of redundancy OK Loss of redundancy
3 Faulty/Affected OK Degraded
4 OK Loss of redundancy Loss of redundancy
5 Loss of redundancy Loss of redundancy Loss of redundancy
6 Faulty/Affected Loss of redundancy Degraded
7 OK Faulty/Affected Degraded
8 Loss of redundancy Faulty/Affected Degraded
9 Faulty/Affected Faulty/Affected Faulty
Table 13-2: Multi-carrier channels propagation rules
13.1.3 Single-Carrier Channels Propagation Rules

Single-carrier channels are a bit special, as for these channels only one transmitter can be in
use at any one time. The following rules have been implemented for these channels:
1 If all channel legs are OK, then the channel is OK.
2 If all channel legs are Faulty or Affected, then the channel is Faulty.
3 If at least one channel leg have Loss of redundancy, then the channel is Loss of
redundancy.
The following table shows the effects for a two-legged channel:
Channel leg 1 Channel leg 2 Channel

1 OK OK OK
3 Faulty/Affected OK Loss of redundancy
6 Faulty/Affected Loss of redundancy Loss of redundancy
7 OK Faulty/Affected Loss of redundancy
8 Loss of redundancy Faulty/Affected Loss of redundancy
Table 13-3: Single-carrier channels propagation rules

Rev. 1.0 / 26-Mar-09
13.2 Controller Working Position Services (OPERATOR POSITION ROOT)

The main controller working position service is the work position, which consists of normally
one or two sets of controller equipment, i.e. position equipment, touch screen, headset and
switches. The work positions are grouped into position groups, according to physical location
or ATC work area. Only the work position service generates alarms.
Controller
working
positions
Position Position Position

group group group
Work Work Work

position position position
Controller Controller
equipment equipment
A B
Figure 13-7: Controller working position service hierarchy
13.2.1 Controller Equipment Technical States

One set of controller equipment may have one of the following states:
Technical state Condition

OK The position is connected to the VCS on both E1 links and reports no problems
Faulty Will be reported if the position reports a fault.
Loss of Will be reported in any of the following events:
redundancy 4 If one of the E1 links to the VCS is disconnected
5 If the SWC where one of the E1 links is terminated fails
Affected Will be reported in the event that both E1 links to the VCS are disconnected
because either the link is disconnected or the SWCs controlling the link fail.
Table 13-4: Controller equipment technical states
13.2.2 Controller Working Position Propagation Rules

Where a controller working position consist of one or more sets of position equipment, the
propagation rules are defined as:
1 If all controller equipments are OK, then the controller working position is OK.
2 If one or more controller equipments are Loss of redundancy and the rest of the
controller equipments are OK, then the controller working position is Loss of
redundancy.
3 If at least one controller equipment is Faulty or Affected, then the controller working
position is Degraded.

Rev. 1.0 / 26-Mar-09
4 If all controller equipments are Faulty or Affected, then the controller working position is
Faulty.
The following table shows the effects for a controller working position with two sets of
controller equipment:
Controller equipment 1 Controller equipment 2 Controller working position

1 OK OK OK
3 Faulty/Affected OK Degraded
6 Faulty/Affected Loss of redundancy Degraded
7 Loss of redundancy Faulty/Affected Degraded
8 OK Faulty/Affected Degraded
Table 13-5: Controller working position propagation rules
13.2.3 Telephone Line Services (GROUND/GROUND ROOT)

A telephone line service is built from one or more telephone line cards, and in some cases an
M-module if the telephone service protocol is executed on a switch card. The telephone line
service is grouped into telephone line groups, according to e.g. line type. Only the telephone
service generates alarms.
Telephone
line
services
Telephone Telephone Telephone

line line line
group group group
Telephone Telephone Telephone

line line line
service service service
Telephone Telephone
M-module M-module
line card line card
Figure 13-8: Telephone line service hierarchy
13.2.4 Telephone Line Service Propagation Rules

Where a telephone line service consist of one or more telephone line cards, the propagation
rules are defined as:
1 If all telephone line cards are OK, then the telephone line service is OK.

Rev. 1.0 / 26-Mar-09
2 If one or more telephone line cards are Loss of redundancy and the rest of the
telephone line cards are OK, then the telephone line service is Loss of redundancy.
3 If all telephone line cards are Faulty or Affected, then the telephone line service is
Faulty.
4 If at least one telephone line card is Faulty or Affected, then the telephone line service is
Degraded.
13.2.5 Telephone Line Group Propagation Rules

Where a telephone line group consist of one or more telephone line services, the
propagation rules are defined as:
1 If all telephone line services are OK, then the telephone line group is OK.
2 If one or more telephone line services are Loss of redundancy and the rest of the
telephone line services are OK then the telephone line group is Loss of redundancy.
3 If at least one telephone line service is Faulty, Affected or Degraded, then the
telephone line group is Degraded.
4 If all telephone line services are Faulty or Affected, then the telephone line group is
Faulty.
13.3 The VCMS Service (VCMS ROOT)

The VCMS service contains equipment or functions within the VCMS. On the VCMS server,
the interface to the VCS in monitored. Each DGD program will also monitor the connection to
the server and its own operation. In case of a failure, the DGD can only generate local
pseudo-alarms, as the connection to the database may not be working. The VCMS server
will however detect a non-responding DGD client and automatically log it off. The VCMS
service may also contain third party equipment or functions used for tasks like monitoring
and control (e.g. monitoring of the VCMS network, or monitoring and control of radios).
VCMS
service
VCS Database Third party

DGD2
interface connection applications
Figure 13-9: VCMS service hierarchy
The propagation rules are defined as:

1 If all VCMS equipments are OK, then the VCMS service is OK.
2 If at least one VCMS equipment is Faulty, Affected or Degraded, then the VCMS
service is Degraded.
3 If all VCMS equipments are Faulty or Affected, then the VCMS service is Faulty.

Rev. 1.0 / 26-Mar-09
13.4 Auxiliary Services

If auxiliary equipment is interfaced to the VCMS server database in such a way that it can
insert alarms into the database tables, this equipment can be monitored the same way as the
VCCS. One or more pieces of auxiliary equipment may form auxiliary services that generate
alarms.
Auxiliary
services
Auxiliary Auxiliary Auxiliary

service service service
Auxiliary Auxiliary Auxiliary

equipment equipment equipment
Figure 13-10: Auxiliary service hierarchy

1 If all Auxiliary equipments are OK, then the Auxiliary service is OK.
2 If at least one Auxiliary equipment is Faulty, Affected or Degraded, then the Auxiliary
service is Degraded.
3 If all Auxiliary equipments are Faulty or Affected, then the Auxiliary service is Faulty.

Rev. 1.0 / 26-Mar-09
13.5 Radio Station Equipment Groups

There are three levels of equipment groups for a radio station. None of the equipment groups
will generate alarms. The low level group is called a radio array. It consists of receivers or
transmitters controlled by the same E1-RIC. The middle level group is called a radio group. It
consists of all the radio arrays connected to the same E1 link. The highest level is the radio
station, consisting of radio groups, the E1 link and optionally a group of auxiliary equipment
that is capable of being monitored by the VCMS.
Radio
stations
Radio Radio Radio

station station station
Ground/
Ground/ Auxiliary
Radio Radio
ground equipment
group group
link group
Radio Radio Auxiliary Auxiliary Auxiliary

array array equipment equipment equipment
E1-RIC Radio Radio
Figure 13-11: Radio station equipment hierarchy

1 If all child assets are OK, then the parent asset is OK.
2 If at least one child asset is Faulty, Affected or Degraded, then the parent asset is
Degraded.
3 If all child assets are Faulty or Affected, then the parent asset is Faulty.

Rev. 1.0 / 26-Mar-09
13.6 VCS Equipment Groups

A VCS has four levels of equipment groups. The highest level of equipment grouping is the
local VCS, which consists of one or more rack groups, where each group normally is located
in separate equipment rooms. The rack group consists of one or more racks. Each rack
consists of card frames and non-monitored hardware, e.g. ventilation blinds. A frame
consists of frame modules, e.g. power supplies, telephone line cards and switch cards. The
switch card consists of the card itself, but is also a group that may contain up to two
M-modules and the links controlled by the card.
VCS
Local Remote Remote

VCS VCS VCS
Rack Rack Rack

group group group
Rack Rack Rack
Frame Frame Hardware Hardware
Ground/
Ground/
Frame Switch
ground line
module card
card
M-module M-module Link
Figure 13-12: VCS equipment hierarchy

1 If all child assets are OK, then the parent asset is OK.
2 If at least one child asset is Faulty, Affected or Degraded, then the parent asset is
Degraded.
3 If all child assets are Faulty or Affected, then the parent asset is Faulty.

Rev. 1.0 / 26-Mar-09
-End of the document-

Rev. 1.0 / 26-Mar-09

VCA-0036-15 DGD Operators Manual 1-0 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

VCA-0036-15 DGD Operators Manual 1-0 PDF

Загружено:

Авторское право:

Доступные форматы

Commercial – in – Confidence

GAREX 220 VCCS

VCA-0036-15 DGD OPERATORS MANUAL

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

Owner Andreas Tønnesen

Issue PR / CO Review Review Date Author Based on document

Issue Paragraph Paragraph Heading/Description of Change

 Copyright 2009 Northrop Grumman Park Air Systems AS

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

-Page intentionally blank-

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

2 EQUIPMENT AND SERVICES ............................................................................ 3

3 TECHNICAL STATE ......................................................................................... 7

4 MAINTENANCE STATE .................................................................................. 11

6 USERS AND ENGINEERING ROLES................................................................. 19

7 ASSET TREE W INDOW ................................................................................. 31

8 ALARM LIST ................................................................................................ 33

9 MAIN VIEW ................................................................................................. 41

10 DETAIL VIEWS ............................................................................................. 43

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

10.1.4 Option: Opening MARC in Channel Leg Details View......................................... 46

11 BASIC SETTINGS ......................................................................................... 61

12 HELP FUNCTIONS ........................................................................................ 65

13 APPENDIX: SERVICES AND EQUIPMENT GROUP DETAILS................................. 67

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

Figure 10-6: List of channels selected for retransmission 46

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

Buttons and keys: Shown in bold face as a shaded box, e.g. OK .

Captions on tabs, frames,

Technical states: Shown in bold face, e.g. OK, Loss of redundancy.

Maintenance states: Shown in bold face italics, e.g. Forced OK.

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

-Page intentionally blank-

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

Figure 1-1: VCMS server and clients with DGD

Note to DGD users:

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

-Page intentionally blank-

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

2 Equipment and Services

Figure 2-1: Equipment and Service graphical elements

The top-level services of the DGD Asset tree:

The top-level equipment groups are:

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

-Page intentionally blank-

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

-Page intentionally blank-

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

Change technical Event log

Check if failure Event log

Services/ Event log

Figure 3-1: Service and equipment graphical elements

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

-Page intentionally blank-

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS

Appendix: Services and Equipment Group.

GAREX 220 VCCS VCA-0036-15 DGD Operators Manual

Priority Technical Shown in the alarm Applies to Applies to services

VCA-0036-15 DGD Operators Manual GAREX 220 VCCS