Technician's Facility For Westlock: User Manual

User Manual
Technician’s Facility
for WESTLOCK
X1512-CTF-ENG-MN00207 User Manual

Revision 3.1 / December 2014 Technician’s Facility for WESTLOCK
© Siemens Rail Automation Ltd 2014. All rights reserved. Page 1 of 224
Manual Ref X1512-CTF-ENG-MN00207
Revision 3.1
Date December 2014
Copyright
Transmittal, reproduction, dissemination or editing of this document is prohibited. Use of this document’s contents
and communication thereof to others without express authorization is also prohibited. Offenders will be held liable
for payment of damages. All rights created by patent grant or registration of a utility model or design patent are
reserved.
This manual has been produced with care to ensure the information contained within is correct at the
time of printing. Any inaccuracies or omissions should be reported in writing to the Team Leader
Technical Publications Group
Siemens Rail Automation Ltd.

PO Box 79
Pew Hill
Chippenham
Wiltshire
SN15 1JD
Tel: +44(0)1249 441 441
Fax +44(0)1249 441 442
User Manual X1512-CTF-ENG-MN00207

Technician’s Facility for WESTLOCK Revision 3.1 / December 2014
Page 2 of 224 © Siemens Rail Automation Ltd 2014. All rights reserved.
Quick Start TF-L and TF-R
Quick Start TF-L and TF-R
Starting the Technician’s Facility (Local)

Power up the monitor if required, (the Workstation should have been left working by the
last user, but the monitor may have been powered down). If anything other than Default
access to the TF-L or TF-R is required select ‘Log on’ from the Access menu.
Note: When attempting to use the TF-R after it has been accessed from a TF-R+ the user may be
required to login to the TRF box, for this they should use the user account ‘User’ with a
default password of ‘U5er’.
Note: When using the TF-R+ to start the Remote Desktop Protocol session the user must login
to the TFR box, for this they should use the user account ‘User’ with a default password
of ‘U5er’.
Opening Windows
State Viewer, on the left of the default screen, works as for Windows Explorer.
Click on a Tab at the bottom of the State Viewer to select required view (Signals,
Points etc).
Expand items in the State Viewer using for added detail.
Alarm View window, available from the Pane toolbar on the default screen.
Mimic window (Track Diagram), available from the Pane toolbar on the default screen.
Zoom in, click on . Zoom out, click on .
Show/hide extra detail, click on:
Miscellaneous labels
Point labels
Signal labels
Track labels
Power labels
Location labels
Lie of points
Attribute Monitor window opened by clicking the tab on the Pane toolbar.
Drag and drop items from the State Viewer as required into the ‘Selected Attributes’
area.
States Monitor window opened by clicking the tab on the Pane toolbar.
Drag and drop items from right to left as required.
Technician Controls
Generate a report of the currently applied Technician controls by clicking ‘Technician
Controls’ > ‘Reports’.
Apply or remove a Technician Control by clicking ‘Technician Controls’ > ‘Apply or remove
control’ and then follow the dialog box.
(Note that Technician Controls are only available when logged on with the required
user role.)

Document History
Document History
Revision Date Amendment
1.1 Oct 2014 Review comments incorporated
1.2 Oct 2014 Initial Issue
2.1 Nov 2014 Updated due to configuration system clean up.

No technical changes.
3.1 Dec 2014 ECO0031720

OBS11452
Note added to Section 6.3.
OBS11641
Note added to Sections 6.5.2, 7.4.3 and 7.5.3.
OBS11642
Table 5.1 amended.
Note added to Section 5.5.
Cautions added to Sections 5.5 and 5.5.2.
OBS11643
Section 8.1 text amended.
Caution added to Section 8.1.
OBS11657
Quick Start title and first paragraph amended.
Notes added to Quick Start.

Contents List
Contents List
Quick Start TF-L and TF-R ....................................................................3

Document History ...............................................................................4
Contents List .......................................................................................5
List of Tables .......................................................................................9
List of Figures....................................................................................11
Glossary ............................................................................................15
1 Introduction to this Manual ............................................................. 19

1.1 Purpose of Manual .................................................................................................. 19
1.2 Manual Outline ....................................................................................................... 19
1.3 Applicability ............................................................................................................ 20
1.4 Related Documents ................................................................................................. 20
1.5 Conventions Used in this Manual ............................................................................. 21
1.6 Role and Purpose of the Technician's Facility ............................................................ 24
1.7 Connectivity............................................................................................................ 25
1.7.1 Technician's Facility (Local)................................................................................. 25
2 Safety Information........................................................................... 27
2.1 Definition of Warning .............................................................................................. 27
2.2 Definition of Caution ............................................................................................... 27
2.3 Authority ................................................................................................................ 27
2.4 General Safety Precautions ...................................................................................... 27
2.5 Safety Warnings and Precautions ............................................................................. 28
2.5.1 Leptospiral Jaundice ........................................................................................... 28
2.5.2 Lethal Voltage .................................................................................................... 28
2.5.3 Heavy Equipment ............................................................................................... 28
2.5.4 Working Practices ............................................................................................... 29
2.5.5 Laser Safety and Optical Fibre ............................................................................. 29
2.5.6 Batteries Handling .............................................................................................. 29
2.5.7 Handling of Lithium Batteries ............................................................................. 30
2.5.8 Electrostatic Sensitive Devices ............................................................................ 30
2.5.9 Module and Cards Storage And Transit................................................................ 31
2.5.10 Use of Mobile Phone/Mobile Radio Units ............................................................. 31
3 Operating Procedures - Local........................................................... 33

3.1 Introduction ............................................................................................................ 33
3.1.1 Facilities............................................................................................................. 33
3.2 Powering Up And Powering Down ........................................................................... 35
3.2.1 Powering Up ...................................................................................................... 35
3.2.2 Powering Down the Monitors ............................................................................. 35
3.2.3 Powering Down the TF-L..................................................................................... 35
3.2.4 Administrator Access .......................................................................................... 36
3.3 Logging in / Logging out.......................................................................................... 37
3.3.1 Introduction ....................................................................................................... 37

Contents List
3.3.2 Log-On ............................................................................................................... 37

3.3.3 Log-Off ............................................................................................................... 38
3.3.4 Logged In As Administrator ................................................................................. 38
3.3.5 User Management functions ............................................................................... 39
3.3.6 Creating a New User ........................................................................................... 47
3.4 TF Screen Layout ..................................................................................................... 48
3.4.1 TF-S Initial Screen ............................................................................................... 48
3.4.2 TF-L and TF-R Initial Screen ................................................................................. 48
3.4.3 Track Diagram Mimic Window ............................................................................. 49
3.4.4 Alarms View ....................................................................................................... 51
3.4.5 Attribute Monitor................................................................................................ 52
3.4.6 States Monitor .................................................................................................... 52
3.5 Use of the Menu Bar ................................................................................................ 54
3.5.1 Introduction ....................................................................................................... 54
3.5.2 Menus Provided .................................................................................................. 54
3.6 Use of the State Viewer............................................................................................ 56
3.6.1 Purpose .............................................................................................................. 56
3.6.2 Signal Explorer View ........................................................................................... 59
3.6.3 Tracks Sections Explorer View ............................................................................. 60
3.6.4 Points Explorer View ........................................................................................... 61
3.6.5 Routes Explorer View .......................................................................................... 62
3.6.6 Flags Explorer View............................................................................................. 63
3.6.7 Panel Requests Explorer View .............................................................................. 64
3.6.8 Trackside Telegrams by TFM Explorer View .......................................................... 65
3.6.9 Trackside Telegrams by Object Explorer View ...................................................... 67
3.6.10 WESTLOCK to WESTLOCK Telegrams Explorer View.............................................. 69
3.6.11 Direct Input Telegrams Explorer View .................................................................. 71
3.6.12 WESTLOCK Equipment Explorer View .................................................................. 72
3.6.13 FEP (Front End Processor) Telegrams by Object Explorer View.............................. 93
3.6.14 Virtual Trackside Telegrams by TFM Explorer View ............................................... 95
3.6.15 WESTRACE Network Communications Explorer View............................................ 96
3.6.16 TF Explorer View ................................................................................................. 97
3.6.17 IOM (Input / Output Modules) Explorer View ....................................................... 99
3.7 Use of the Track Diagram Mimic Window ............................................................... 100
3.7.1 Introduction ..................................................................................................... 100
3.7.2 Viewing the State of the Railway ....................................................................... 101
3.7.3 Viewing the Aspects of Signals .......................................................................... 102
3.7.4 Viewing the Lie of Points................................................................................... 103
3.7.5 Viewing Track Section Occupancy ..................................................................... 104
3.8 Use of the Attribute Monitor Window ..................................................................... 105
3.8.1 Introduction ..................................................................................................... 105
3.8.2 Adding Items .................................................................................................... 105
3.8.3 Viewing Monitored Items .................................................................................. 106
3.9 Use of the States Monitor Window ......................................................................... 108
3.9.1 Introduction ..................................................................................................... 108
3.9.2 Adding Items .................................................................................................... 108
3.9.3 Viewing Monitored Interlocking Items ............................................................... 109
4 Area of Control (AoC) .................................................................... 111

4.1 Introduction .......................................................................................................... 111
4.1.1 Alarms .............................................................................................................. 111
4.1.2 Tech Controls.................................................................................................... 111
4.2 Take Control .......................................................................................................... 112
4.3 Release Control...................................................................................................... 114

Contents List
5 Technician Controls ....................................................................... 117

5.1 Introduction .......................................................................................................... 117
5.2 Determining Which Controls Are Applied ............................................................... 117
5.3 Technician Controls Report Selection ..................................................................... 118
5.3.1 Technician Controls .......................................................................................... 118
5.3.2 Differences....................................................................................................... 118
5.3.3 The Track Diagram............................................................................................ 120
5.4 Generating a Technician Controls Report ............................................................... 120
5.5 To Apply and Remove Technician Controls ............................................................. 121
5.5.1 Track................................................................................................................ 127
5.5.2 Interlocking...................................................................................................... 128
5.5.3 Route ............................................................................................................... 130
5.5.4 Points............................................................................................................... 131
5.5.5 Signal............................................................................................................... 132
5.5.6 Technician’s Latch ............................................................................................ 134
6 Alarms and Fault Diagnosis ........................................................... 135

6.1 Introduction .......................................................................................................... 135
6.2 New Alarms .......................................................................................................... 135
6.3 Progressing of Alarms............................................................................................ 136
6.4 Alarms View Window............................................................................................. 138
6.5 Alarms Report Selection......................................................................................... 141
6.5.1 Introduction ..................................................................................................... 141
6.5.2 Generating a Report ......................................................................................... 141
6.5.3 Filtering by equipment type.............................................................................. 142
6.5.4 Filtering by alarm type...................................................................................... 143
6.5.5 Viewing the Report........................................................................................... 144
7 Logging .......................................................................................... 145

7.1 Introduction .......................................................................................................... 145
7.2 Dismounting a Logging Drive................................................................................. 146
7.3 Mounting a Logging Drive ..................................................................................... 146
7.4 Viewing Logs......................................................................................................... 147
7.4.1 Introduction ..................................................................................................... 147
7.4.2 Generating A Report ......................................................................................... 149
7.4.3 Viewing The Report .......................................................................................... 156
7.4.4 Types Of Report................................................................................................ 157
7.5 Export ................................................................................................................... 163
7.5.1 Introduction ..................................................................................................... 163
7.5.2 Creating Data To Export.................................................................................... 163
7.5.3 Viewing Exported Data ..................................................................................... 164
7.5.4 Selecting Data To Export................................................................................... 165
8 Event Replay Facility...................................................................... 167

8.1 Introduction .......................................................................................................... 167
8.2 Applicability .......................................................................................................... 169
8.3 Operation ............................................................................................................. 169
8.3.1 Opening the SERFG .......................................................................................... 169
8.3.2 Opening the ERF............................................................................................... 169
8.3.3 Selecting A Data Source.................................................................................... 170
8.3.4 Defining Selection Criteria ................................................................................ 172

Contents List
8.3.5 Events To Replay Window ................................................................................. 175

8.3.6 Collapse All ....................................................................................................... 176
8.3.7 Replayed Events window................................................................................... 186
9 Reference Information .................................................................. 187

9.1 Alarm Categories ................................................................................................... 187
9.2 Fault List Entries .................................................................................................... 192
9.2.1 Text Line Format............................................................................................... 192
9.2.2 Fields Used in Text Lines ................................................................................... 193
9.3 WESTLOCK Equipment (WLE) Tab Variations ........................................................... 208
9.4 Printer ................................................................................................................... 224
9.5 TF Clock................................................................................................................. 224

List of Tables
List of Tables
Table 3.1 Role Operations................................................................................................. 39

Table 3.2 State Viewer Tab Meanings................................................................................ 58
Table 5.1 Technician Controls Available .......................................................................... 121
Table 9.1 Typical Faults for each Category....................................................................... 187
Table 9.2 Causes of Faults List Entries ............................................................................. 195
Table 9.3 WLE Tab Variations .......................................................................................... 209
Table 9.4 WLE Tab Error Corrective Actions ..................................................................... 218

© Siemens Rail Automation 2014. All rights reserved. Page 9 of 224
List of Tables
Intentionally Left Blank

Page 10 of 224 © Siemens Rail Automation 2014. All rights reserved.
List of Figures
List of Figures
Figure 1.1 Scroll Boxes ....................................................................................................... 22

Figure 1.2 TF-L Connections............................................................................................... 25
Figure 3.1 Log On dialog box ............................................................................................. 37
Figure 3.2 Change Inactivity Time dialog box’ ..................................................................... 38
Figure 3.3 View Roles dialog box ........................................................................................ 41
Figure 3.4 Export Role List.................................................................................................. 41
Figure 3.5 Edit Roles dialog box ......................................................................................... 42
Figure 3.6 Add New Role dialog box ................................................................................... 42
Figure 3.7 Modify Role dialog box ...................................................................................... 43
Figure 3.8 View Users dialog box........................................................................................ 44
Figure 3.9 Export User List ................................................................................................. 44
Figure 3.10 Edit Users dialog box ......................................................................................... 45
Figure 3.11 Add New User dialog box................................................................................... 45
Figure 3.12 Modify User dialog box ...................................................................................... 46
Figure 3.13 Change Password dialog box ............................................................................. 46
Figure 3.14 Example: Technician's Facility (Local) Initial Screen ............................................ 48
Figure 3.15 Example of a Tool Tip ........................................................................................ 49
Figure 3.16 Example: Typical Basic Track Diagram Window ................................................... 51
Figure 3.17 Example: Typical Track Diagram with all options labels selected ......................... 51
Figure 3.18 Export attribute states dialog box ...................................................................... 52
Figure 3.19 States Monitor toolbar....................................................................................... 52
Figure 3.20 Example State Viewer Layout............................................................................. 56
Figure 3.21 Example TF-R State Viewer Layout ..................................................................... 57
Figure 3.22 Example: Signals State Viewer Layout ................................................................ 59
Figure 3.23 Example: Signals State Viewer Expanded Layout ................................................ 59
Figure 3.24 Example: Track Sections State Viewer Layout ..................................................... 60
Figure 3.25 Example: Track Sections State Viewer Expanded Layout ..................................... 60
Figure 3.26 Example: Points State Viewer Layout.................................................................. 61
Figure 3.27 Example: Points State Viewer Expanded Layout.................................................. 61
Figure 3.28 Example: Routes State Viewer Layout................................................................. 62
Figure 3.29 Example: Routes State Viewer Expanded Layout................................................. 62
Figure 3.30 Example: Flags State Viewer Layout ................................................................... 63
Figure 3.31 Example: Sub Routes State Viewer Expanded Layout .......................................... 63
Figure 3.32 Example: Technician’s Latches State Viewer Expanded Layout ............................ 63
Figure 3.33 Example: Requests State Viewer Layout ............................................................. 64
Figure 3.34 Example: Requests State Viewer Expanded Layout ............................................. 64
Figure 3.35 Example: TFM State Viewer Layout .................................................................... 65
Figure 3.36 Example: TFM State Viewer Expanded Layout .................................................... 66
Figure 3.37 Example: TbO State Viewer Layout (Level 1 Nodes) ............................................ 67
Figure 3.38 Example: TbO State Viewer Layout (Level 2 Nodes) ............................................ 67
Figure 3.39 Example: TbO State Viewer Expanded Layout..................................................... 68
Figure 3.40 Example: W2W State Viewer Layout ................................................................... 69
Figure 3.41 Example: W2W State Viewer Expanded Layout ................................................... 70
Figure 3.42 Example: DIO State Viewer Layout ..................................................................... 71
Figure 3.43 Example: DIO State Viewer Expanded Layout ..................................................... 71
Figure 3.44 Equipment Explorer View Layout (Level 1 Node) ................................................ 72
Figure 3.45 Equipment Explorer View Layout (Level 2 Nodes)............................................... 72
Figure 3.46 Equipment Explorer View Layout (CIP Level 3 Nodes) ......................................... 73
Figure 3.47 Equipment Explorer View Layout (MP Status Level 4 and 5 Nodes) ..................... 74
Figure 3.48 Equipment Explorer View Layout (CM Status Level 4 and 5 Nodes) ..................... 75
Figure 3.49 Equipment Explorer View Layout (DI 1 Status Level 4 and 5 Nodes) .................... 75
Figure 3.50 Equipment Explorer View Layout (CIP Application Status Level 4 Nodes)............. 76
Figure 3.51 Equipment Explorer View Layout (Comms Alarm Status Level 4 and 5 Nodes)..... 76

List of Figures
Figure 3.52 Equipment Explorer View Layout (Link Status Level 4 and 5 Nodes) ....................76
Figure 3.53 Equipment Explorer View Layout (Safety Layer Status Level 4 and 5 Nodes) ........77
Figure 3.54 Equipment Explorer View Layout (Context Status Level 4 and 5 Nodes)...............77
Figure 3.55 Equipment Explorer View Layout (Version Numbers Level 4 and 5 Nodes)...........78
Figure 3.56 Equipment Explorer View Layout (CSG Level 3 Nodes) ........................................78
Figure 3.58 Equipment Explorer View Layout (PMUX Status Level 4, 5 and 6 Nodes)..............79
Figure 3.59 Equipment Explorer View Layout (FEP Level 3 Nodes) .........................................80
Figure 3.60 Equipment Explorer View Layout (SMB Level 3 and 4 Nodes) ..............................80
Figure 3.61 Equipment Explorer View Layout (PM primary and PM secondary
Level 3, 4 and 5 Nodes)......................................................................81
Figure 3.62 Equipment Explorer View Layout (Vital and Non-vital communications
Level 3, 4 and 5 Nodes)......................................................................82
Figure 3.63 Equipment Explorer View Layout (IOMs Level 4, 5 and 6 Nodes) .........................83
Figure 3.64 Equipment Explorer View Layout (IOM Status Level 6 Nodes)..............................84
Figure 3.65 Equipment Explorer View Layout (SOM110 Status Level 6 and 7 Nodes) .............85
Figure 3.66 Equipment Explorer View Layout (FenSouth1 Level 4 and 5 Nodes) ....................86
Figure 3.67 Equipment Explorer View Layout (TIF Level 3 Nodes) ..........................................86
Figure 3.68 Equipment Explorer View Layout (MP Status Level 4 and 5 Nodes)......................87
Figure 3.69 Equipment Explorer View Layout (CM Status Level 4 and 5 Nodes)......................88
Figure 3.70 Equipment Explorer View Layout (SCM Status Level 4 and 5 Nodes)....................89
Figure 3.71 Equipment Explorer View Layout (TIF Application Status Level 4 Nodes) .............90
Figure 3.72 Equipment Explorer View Layout (Comms Alarm Status Level 4 and 5 Nodes) .....90
Figure 3.74 Equipment Explorer View Layout (Safety Layer Status Level 4 and 5 Nodes) ........91
Figure 3.75 Equipment Explorer View Layout (Context Status Level 4 and 5 Nodes)...............91
Figure 3.76 Equipment Explorer View Layout (Version Numbers Level 4 and 5 Nodes)...........92
Figure 3.77 Equipment Explorer View Layout (TF Level 3 Nodes)...........................................92
Figure 3.78 Example: FbO State Viewer Layout (Level 1 Nodes).............................................93
Figure 3.79 Example: FbO State Viewer Layout (Level 2 Nodes).............................................93
Figure 3.80 Example: FbO State Viewer Expanded Layout .....................................................94
Figure 3.81 Example: VTFM State Viewer Layout...................................................................95
Figure 3.82 Example: VTFM State Viewer Expanded Layout ...................................................95
Figure 3.83 Example: WNC State Viewer Layout ....................................................................96
Figure 3.84 Example: WNC State Viewer Expanded Layout ....................................................96
Figure 3.85 Example: TF State Viewer Layout........................................................................97
Figure 3.86 Example: TF State Viewer Expanded Layout ........................................................98
Figure 3.87 Example: IOM State Viewer Layout .....................................................................99
Figure 3.88 Example: IOM State Viewer Expanded Layout .....................................................99
Figure 3.89 Example: State of Railway View ........................................................................101
Figure 3.90 Example: Monitored attribute added ................................................................105
Figure 3.91 Example: Typical Attribute Monitor window displaying Tracks...........................106
Figure 3.92 Typical Attribute Monitor window - All Attribute Changes .................................107
Figure 3.93 Example: Typical States Monitor window - Selected States................................108
Figure 3.94 Example: Typical States Monitor window - Selected State Changes ...................109
Figure 4.1 Example: Area of control selection dialog box - Take control .............................111
Figure 4.2 Example: Area of control selection dialog box - Alarms selected ........................112
Figure 4.3 Example: Area of control selection dialog box - Alarms control taken ................113
Figure 4.4 Example: Area of control selection dialog box - No items to control...................113
Figure 4.5 Example: Area of control selection dialog box - Alarms selected ........................114
Figure 4.6 Example: Area of control selection dialog box - Alarms control released ............115
Figure 4.7 Example: Area of control selection dialog box - No items to release...................115
Figure 5.1 Technician controls report selection .................................................................117
Figure 5.2 Example: Technician controls report selection -
Current state of technician controls ..................................................118
Figure 5.3 Request Technician control report - Differences ................................................119
Figure 5.4 Example: Technician control report - Differences ..............................................119
Figure 5.5 Example: Request Technician Control - Select object.........................................122

List of Figures
Figure 5.6 Example: Request Technician Control - Select technician control ...................... 123
Figure 5.7 Example: Request Technician Control - Technician control application details ... 124
Figure 5.8 Request Technician Control - Control request confirmation prompt .................. 124
Figure 5.9 Example: Request Technician Control - Control request result cancelled............ 125
Figure 5.10 Example: Request Technician Control - Control request result successful .......... 125
Figure 5.11 Example: Request Technician Control - Control request result unsuccessful ...... 125
Figure 5.12 Example: Request Technician Control - Track.................................................... 127
Figure 5.13 Example: Technicians Control - State Viewer (Track)......................................... 127
Figure 5.14 Example: Request Technician Control - Interlocking.......................................... 128
Figure 5.15 Example: Technicians Control - State Viewer (Interlocking)............................... 129
Figure 5.16 Example: Request Technician Control - Route ................................................... 130
Figure 5.17 Example: Technicians Control - State Viewer (Route) ........................................ 130
Figure 5.18 Example: Request Technician Control - Points .................................................. 131
Figure 5.19 Example: Technicians Control - State Viewer (Points) ....................................... 131
Figure 5.20 Example: Request Technician Control - Signal .................................................. 132
Figure 5.21 Example: Technicians Control - State Viewer (Signal) ....................................... 133
Figure 5.22 Example: Request Technician Control - Technician’s Latch ................................ 134
Figure 5.23 Example: Technicians Control - State Viewer (Technician’s Latch) ..................... 134
Figure 6.1 Example: Status Bar New Alarm Indicator......................................................... 135
Figure 6.2 Example: Alarms View - alarms acknowledged ................................................. 136
Figure 6.3 Example: Alarms View Window........................................................................ 138
Figure 6.4 Example: Alarms View - progressing a fault ...................................................... 139
Figure 6.5 Example: Alarms Report Selection dialog box ................................................... 141
Figure 6.6 Example: Alarms Report Selection - Filter by equipment type............................ 142
Figure 6.7 Example: Alarms Report Selection - Filter by alarm type.................................... 143
Figure 6.8 Example: Alarm Report results ......................................................................... 144
Figure 7.1 Example: Log Report - Data selection criteria.................................................... 148
Figure 7.2 Example: Log Report dialog box ....................................................................... 149
Figure 7.3 Example: Log Report dialog box - Attribute filter tab......................................... 151
Figure 7.4 Example: Interlocking filter - ‘All states’ filtered alphabetically........................... 152
Figure 7.5 Example: Interlocking filter - ‘All states’ filtered categorised .............................. 153
Figure 7.6 Example: Alarm filter - Filter by alarm type ....................................................... 154
Figure 7.7 Example: Alarm filter - Filter by equipment type ............................................... 155
Figure 7.8 Example: Interlocking Log Report Results dialog box ........................................ 156
Figure 7.9 Example: Interlocking Log Report dialog box .................................................... 157
Figure 7.10 Example: Interlocking Event Log Report dialog box .......................................... 158
Figure 7.11 Example: Signalling Model Log Report dialog box............................................. 159
Figure 7.12 Example: Alarms Log Report dialog box............................................................ 160
Figure 7.13 Example: Technician Controls Log Report dialog box ........................................ 161
Figure 7.14 Example: Access Control Log Report dialog box................................................ 162
Figure 7.15 Export All interlocking states dialog box........................................................... 164
Figure 7.16 Example: Export All interlocking states - Preview .............................................. 165
Figure 8.1 Event Replay initial screen ............................................................................... 169
Figure 8.2 Example: Replay Source Selection .................................................................... 170
Figure 8.3 Example: Select Log File(s) dialog box.............................................................. 170
Figure 8.4 Example: Replay Source Selection .................................................................... 171
Figure 8.5 Example: Select Log File(s) dialog box.............................................................. 171
Figure 8.6 Example: Corrupted file ................................................................................... 172
Figure 8.7 Example: Invalid Header .................................................................................. 172
Figure 8.8 Empty file........................................................................................................ 172
Figure 8.9 Example: Data Selection Criteria dialog box...................................................... 173
Figure 8.10 Data Selection Criteria Data Error ..................................................................... 174
Figure 8.11 Data Selection Criteria Data Error (Multiple GeoData versions).......................... 174
Figure 8.12 Example: Events To Replay window ................................................................. 175
Figure 8.13 Example: Events To Replay - Expand All............................................................ 176
Figure 8.14 Example: Events To Replay - Collapse All .......................................................... 176
Figure 8.15 Example: Replay Event Search - Time Stamp..................................................... 177
Figure 8.16 Example: Replay Event Search - Mnemonic Name............................................. 177

List of Figures
Figure 8.17 Example: Replay Event Search - Attribute Name................................................178

Figure 8.18 Example: Replay Event Search - Alarm ..............................................................178
Figure 8.19 Replay Event Search - Equipment Type .............................................................179
Figure 8.20 Example: Replay Event Search - Equipment Instance.........................................179
Figure 8.21 Example: Events To Replay - highlighted matching events ................................180
Figure 8.22 Example: Save Extracted Events .......................................................................181
Figure 8.23 Save Extracted Events - successful ....................................................................181
Figure 8.24 Replay Control Panel ........................................................................................182
Figure 8.25 Replay Control Panel - Play mode......................................................................182
Figure 8.26 Replay Control Panel - Repeat check box selected .............................................183
Figure 8.27 Replay Control Panel - Speed of replay..............................................................183
Figure 8.28 Events To Replay - Go To ..................................................................................184
Figure 8.29 Example: Events To Replay - current replayed event highlighted .......................185
Figure 8.30 Example: Replayed Events window...................................................................186

Glossary
Glossary
Term Definition
AoC Area of Control.
AWS Automatic Warning System.
Bit An individual item from the State Viewer.
CIP Central Interlocking Processor.
Control System Any one of:
- Panel with panel multiplexer and train describer.
- IECC or compatible Control Centre.
- WESTCAD Control System.
CSG Control System Gateway.
DI Direct Input (module).
An input from the Signaller to the Interlocking that bypasses the

Direct Input
main Control System, typically for reasons of speed or safety.
DIO Direct Input Telegrams.
DLM Data Link Module.
ERF Event Replay Facility.
ESOC Emergency Signals On Control.
FbO FEP Telegrams by Object.
FEP Front End Processor.
HTML Hyper Text Markup Language.
I/O Input / Output.
IDL Internal Data Link.
IECC Integrated Electronic Control Centre.
Interlocking Centre A collection of WESTLOCK equipment interfaced to (and

including) a single CIP. The size of the Interlocking Centre is
dependent upon the size of the area of control.
IOM Input / Output Module.
Item A piece of information that can be monitored on its own and

cannot be decomposed further.
J-Log Used for arrest and removal by an Incident Investigator, the

Judicial Log is used to record all interlocking controls and
indications, alarms and user interaction. This is a write only log
and is not intended to be accessed online. The log file is written
to the Removable Logging Drive (see below).
LDT Long Distance Terminal.

Glossary
Term Definition
Left-Click A method of selecting an item on the screen by using the mouse
to position the cursor over the item, then pressing and releasing
the left-hand mouse button.
LLL Long Line Link.
Fixed Logging Drive This is the PC hard disk.
Removable Logging The TF-L is fitted with two removable Logging drives. These are
Drive both hot-swappable, removable SATA hard drives that attach via
USB. The J-Log is written to these drives.
PLJI Position Light Junction Indicator.
PM(s) Processor Module(s).
PMux Panel Multiplexer.
REB Relocateable Equipment Building.
Relay I/L Relay Interlocking.
Removable hard drive A portable hard disk that is capable of connecting to other
disk devices.
Right-Click A method of selecting an item on the screen by using the mouse

to position the cursor over the item, then pressing and releasing
the right-hand mouse button.
SCM SSI Communications Module.
SERFG Standalone Event Replay Facility Graphical.
SIF SSI Interface.
SoR State of Railway.
SSI Solid State Interlocking.
State The current value of an item.
TbO Trackside Telegrams by Object.
TDL Trackside Data Link.
TF Technician's Facility.
TF-L Technician's Facility (Local).
TF-R Technician's Facility (Remote).
TF-S Technician’s Facility (Server).
TFM Trackside Functional Module.
TIF Trackside Interface.
Toolbar A set of buttons that perform related tasks.
VTFM Virtual Telegrams by TFM.
W-Log Working Log used to record the same information as the J-Log
but in a form that can be accessed online. The W-Log is written
to the Fixed Logging Drive.
W2W WESTLOCK to WESTLOCK telegrams.
WESTCAD Westinghouse Control And Display (system).

Glossary
Term Definition
WISR WESTLOCK Interlocking Status Record.
WLE WESTLOCK Equipment.
WNC WESTRACE Network Comms.
WTS WESTRACE Trackside System.
XML Extensible Markup Language.

Glossary

Section 1 - Introduction to this Manual
1 Introduction to this Manual
1.1 Purpose of Manual

The purpose of this manual is to provide operating information relating to the Siemens
Rail Automation WESTLOCK Technician's Facility equipment.
The Technician's Facility is the primary tool for diagnosing failures throughout a
WESTLOCK interlocking and its associated trackside equipment.
For a description of the WESTLOCK interlocking, refer to manual M1360/SYS.
For first line maintenance information on the WESTLOCK interlocking and Technician's
Facility, refer to manual M1360/MAINT.
1.2 Manual Outline

This manual is divided into the following sections:
Section 1 Introduction to this Manual
Section 2 Safety Information
Section 3 Operating Procedures - Local
Section 4 Area of Control (AoC)
Section 5 Technician Controls
Section 6 Alarms and Fault Diagnosis
Section 7 Logging
Section 8 Event Replay Facility
Section 9 Reference Information

1.3 Applicability
Should subsequent software versions result in changes affecting this manual, the
manual will be amended and re-issued as appropriate.
For information on the applicability of this manual to other versions, please contact
Siemens Rail Automation at the following address:
Siemens Rail Automation Holdings Limited
Langley Park
PO Box 79
Pew Hill
Chippenham
Wiltshire
SN15 1JD
Tel:+44(0)1249 441441
Fax:+44(0)1249 441442
The software version of the TF is permanently displayed on the title bar of the
application. This manual refers to version 2.A.17 except where otherwise stated.
Note: There are no FEPS or CSG in this version of the software.
1.4 Related Documents

Associated manuals are listed in the Table below:
Manual
Manual Ref Manual Title
Railside Ref
Key Differences Between WESTLOCK and
M1360/DIF X1360-6-EN-MN00054
SSI.
WESTLOCK Data Preparation Process

M1360/DPP X1360-6-EN-MN00052
Manual.
WESTLOCK First Line Maintenance

M1360/MAINT X1360-6-EN-MN00051
Manual.
M1360/SYS X1360-6-EN-MN00050 WESTLOCK System Description Manual.
Technician's Facility for WESTLOCK Manual

X1512-CTF-ENG-MN00207 X1512-CTF-ENG-MN00207
(this manual).
Design Workstation, Test Environment

M1360/WTE X1360-6-EN-MN00068
User Guide
SSI Trackside Functional Module Go/No Go

MTE038 MTE038
Tester.
SSI Data Link Test Set (Receive) Technical

MTE039 MTE039
Manual.
SSI Data Link Test Set (Transmit/Receive)

MTE040 MTE040
Technical Manual.
224
1.5 Conventions Used in this Manual

'Select'
Use the mouse to position the cursor ( ) over the button or item to be selected, then
press and release the left-hand mouse button.
'Right-Click'
Use the mouse to position the cursor ( ) over the button or item to be selected, then
press and release the right-hand mouse button.
'Drag and Drop'

Use the mouse to position the cursor ( ) over the item to be moved. Press and hold the
left-hand mouse button to capture a copy of the item. Move the mouse to select the new
position for the item, then release the left-hand mouse button.
If an attempt is made to move the item to a prohibited position, the cursor changes to a
' '. If the new position is acceptable, the cursor changes to ' '.
'Re-size Window'
Windows may be re-sized by moving the cursor ( ) to the boundary line of the window,
at which point the cursor changes shape to . Press and hold the left-hand mouse
button, move the mouse to position the cursor in the position where you require the
boundary to be, then release the mouse button.
Alternatively, place the cursor over the corner of the window to be re-sized, press and
hold the left-hand mouse button to get a or cursor, move the cursor to the required
position, then release the mouse button.
Note: Only dockable windows can be resized, all pop-up windows are fixed in size.
'Move Window'
A window may be moved without re-sizing it by placing the cursor ( ) in the blue Title
bar at the top of the window, pressing and holding the left-hand mouse button, moving
the mouse to re-position the window, then releasing the mouse button.

'Scroll Down'
Use the mouse to position the cursor ( ) over the Scroll Box (see Figure 1.1). Press and
hold the left-hand mouse button and move the mouse to position the Scroll Box to bring
the required area of the display into view in the window. Release the mouse button.
Step Up
Arrow Box
Vertical
Scroll Box
Step Down
Step Left Arrow Box
Arrow Box
Step Right
Horizontal Arrow Box
Scroll Box
Figure 1.1 — Scroll Boxes
The length of the Scroll Box gives an indication of the amount of the display that is
outside the area covered by the window. For example, if the length of the Scroll Box is
60% of the length of the window, then 40% of the display is outside the area covered by
the window.
Alternatively, the Scroll Box can be moved in single steps by clicking on the arrow boxes
located at each end of the scroll bar. Holding the left mouse button down will result in
rapid multiple steps until the button is released.
Dock/Undock
This applies to the State Viewer, Track Diagram and the Alarms/Monitoring Window.
To Undock:
Double-click or drag the window by its top border. The window can then be moved
and re-sized as normal. The window remains floating until docked or may be
double-clicked again to return to its previous (default) position.
To Dock:
Dragging the undocked window around the screen’s edges will create a highlighted
grey border that the window will snap position to. Once the floating window has
snapped to a new position, this becomes its new default position.
'Item'
An entry on a list in the State Viewer e.g. the Signal list, when expanded, shows a list of
signals which are 'items' on that list.
'Attribute'
In the State Viewer, an item can be expanded into further sub-divisions known as
'attributes'. An attribute cannot be expanded further in the State Viewer.
Fixed Logging Drive

The Fixed Logging Drive is the PC hard disk.
224
Removable Logging Drive

The TF-L is fitted with two Logging Drives. These are both hot-swappable, removable
SATA hard drives that attach via USB.
Note: The Technicians Facility is highly configurable and therefore the content provided
within this manual may differ from real deployments. Content such as screen shots and
field names should be considered as examples only to help explain the function
provided.

1.6 Role and Purpose of the Technician's Facility

The Technician's Facility (TF) comprises the following sub-systems.
1. The Technician's Facility Local (TF-L). This provides the signalling Technician or
Incident Investigator with information concerning the state of the interlocking and
of the associated external signalling equipment. The TF-L can be used to view the
state of signalling objects, to diagnose faults and to restrictively modify the
characteristics of the Interlocking. An event recording facility is also provided. The
TF-L is located within the control centre equipment room and is connected to the
WESTLOCK interlocking via Ethernet networks. One TF-L is required for each
interlocking.
Note: The Technician’s Facility data acts as the equivalent of the version control strapping in
SSI; this means that the TF-L data must be updated every time the CIP data is updated.
Note: It is not possible to give the TF-L the same name as the CIP.
2. The Technician’s Facility Server (TF-S). This resides in the control centre equipment
room and obtains State of the Railway (SoR), diagnostics and fault information from
a number of TF-L. This information is stored locally and is passed to any connected
TF-R for analysis or replay purposes. The TF-S provides an access point to which
TF-R may connect in order to receive SoR, diagnostics and fault information, take
control of an interlocking in order to apply or remove technician controls, or take
control of the alarms associated with a TF-L. One TF-S is required per WESTLOCK
scheme.
3. The Remote Technician’s Facility (TF-R) resides at a location remote from the control
centre equipment room (and possibly from the TF-S). The TF-R connects to a TF-S
and obtains the SoR, diagnostics and fault information associated with each TF-L
connected to the TF-S for analysis or replay purposes (the Event Replay Facility
(ERF)). The TF-R allows the Technician to take control of a Tech Controls or Alarms
database in order to apply or remove technical controls, or to action alarms.
Note: The TF-R+ provides the means via remote desktop facility to connect remotely to any
configured TF-R.
Note: Replication of TF-L logs to TF-S and access via TF-R will take some time if the TF-S has
been disconnected from the TF-L.
Note: If connection between a TF-L and the TF-S is lost, the TF-R will not be able to gain access
to the interlocking.
4. The Stand Alone Event Replay Facility Graphical (SERFG). Operated from a stand
alone PC device, the SERFG replays previous logged data to allow incidents to be
investigated. Interlocking, Alarm and Signalling model logs along with Access and
Technician Control logs can be replayed according to the replay mode, utilising a
control panel with standard replay controls. The SERFG allows the user to select
data from the J-Log or from previously stored replay data, and also enables the user
to save selected J-Log data for subsequent replay. The same functionality is
available on the TF-R, but only data from the W-Log or previously stored replay data
can be accessed.
Note: SERFG has a minimum screen resolution requirement of 1280 by 1024.
224
1.7 Connectivity
1.7.1 Technician's Facility (Local)
As shown in Figure 1.3, the TF-L connects to the WESTLOCK interlocking system via both
the Control Network and the Signalling Network. These are both dual redundant
Ethernet networks. The connection to each network from the TF-L is via duplicated links.
Using the Control Network, the TF-L obtains CIP internal states from the CIP, CSG
diagnostic data from the CSG and passes on Signallers alarms to the CSG.
Note: Where the control system is a WESTCAD, a CSG may not be required, in which case the
TF-L connects directly to the WESTCAD.
Figure 1.2 — TF-L Connections

The TF-L communicates via the Signalling Network with the CIP, FEP, TIF(s), SIF(s) and
adjacent CIP(s) to obtain diagnostic information.
The TF-L communicates with the CIP via either the Signalling or the Control networks to
apply or remove Technician's controls.
Note: The TF-S and TF-R in the above diagram are used when deployed.
224
Section 2 - Safety Information
2 Safety Information
2.1 Definition of Warning
Warnings are given to highlight the DANGER to PERSONNEL of serious injury or death
when handling, operating or maintaining equipment or systems.
2.2 Definition of Caution
Caution Cautions are given to highlight the possibility of DAMAGE to EQUIPMENT, or

DEGRADATION of EQUIPMENT OPERATION when handling, operating or maintaining
equipment.
2.3 Authority
The following instructions do not supersede any current company or statutory safety
instructions/regulations, which must be complied with.
Before handling, operating or maintaining any material, obtain the necessary authority.
2.4 General Safety Precautions

Assess the need for Personal Protection Equipment (PPE) before undertaking installation,
maintenance or manual operations.
Use PPE to prevent abrasions and to minimize the risk of infection from pigeon, rat
droppings, etc.
Rat bites must be treated immediately.
Abrasions and cuts must be treated immediately.

2.5 Safety Warnings and Precautions

2.5.1 Leptospiral Jaundice
Leptospiral Jaundice can be contracted through contact with contaminated

water, particularly if rats are present. The infection enters through broken skin
and early stages mimic influenza: jaundice (Weil’s Disease) can occur later. The
disease is treatable but the following precautions must be observed:
• Cover all exposed cuts and abrasions with waterproof plaster BEFORE starting
work.
• Always wear protective clothing.
• Apply thorough first aid immediately to wounds.
• Seek medical assistance if you have sustained any injury or if you feel ill.
2.5.2 Lethal Voltage
Electrical power within this system/equipment is at a level considered, by the

European Council Low Voltage Directive 73/23/EEC, as amended by Directive
2006/95/EC, to be sufficient to kill.
• Always assume conductors are live until proved dead.
• Before attempting any maintenance task, ensure that equipment is isolated
from electrical supplies.
• When the electrical supplies cannot be isolated, testing/maintenance tasks
are to be undertaken only by personnel who are aware of the dangers
involved and after all necessary precautions have been taken.
2.5.3 Heavy Equipment
Manual handling must only be carried out by trained personnel.

All manual handling must be in accordance with the Manual Handling
Operations Regulations 1992 / 2793, Guidance on Regulations L23.
224
2.5.4 Working Practices
Unauthorised interruption of the system may endanger the safe operation of

the railway. Before attempting any maintenance on the equipment, obtain the
necessary permission from the relevant authority. Ensure the consequence of
any interruption has been fully considered and understood.
If a component or equipment becomes overheated or burnt, a toxic fume hazard
may exist. Isolate the power to the equipment, ventilate the area and allow the
equipment time to cool before carrying out repairs.
When working on equipment, especially in the confines of a train or a cubicle, do not
wear metal rings, bracelets, watches, etc. These articles can cause personal injury or
damage to equipment by becoming entangled in components or causing a short
circuit.
Care has been taken to ensure that no sharp edges are present. However, take care
that no sharp edges have been created or exposed during installation or
maintenance. Always check for sharp edges before undertaking any installation or
maintenance activities
2.5.5 Laser Safety and Optical Fibre
General good working practices adapted from EN60825-2: 1994:

Do not stare with unprotected eyes or with any unapproved optical device at the
fibre ends or connector faces or point them at other people.
Use only approved filtered or attenuating viewing aids.
Any single or multiple fibre end or ends found not to be terminated (for example,
matched, spliced) shall be individually or collectively covered when not being
worked on. They shall not be readily visible and sharp ends shall not be exposed.
When using test cords, the optical power source shall be the last connected and the
first disconnected.
Use only approved methods for cleaning and preparing optical fibres and optical
connectors.
Always keep optical connectors covered to avoid physical damage
Do not allow any dirt/foreign material ingress on the optical connector bulkheads.
The optical fibre jumper cable maximum bend radius is 3cm, any smaller radii may
result in optical cable breakage or excessive transmission losses.
2.5.6 Batteries Handling
When handling batteries containing liquid electrolyte, protective clothing must be

worn to safeguard against the possibility of electrolyte coming into contact with skin
or eyes.
If contact with electrolyte does occur, wash the affected area immediately with
copious amounts of clean water and seek immediate medical attention.

2.5.7 Handling of Lithium Batteries
Observe the following procedures when handling Lithium batteries:

• NEVER attempt to recharge a non-rechargeable Lithium battery - it may vent or
explode.
• NEVER short circuit a Lithium battery -it may overheat or vent.
• NEVER place equipment containing a Lithium battery on a conductive surface.
• NEVER carry a Lithium battery in a pocket or container with other batteries or
conductive material, unless battery terminals are suitably insulated.
• NEVER crush, puncture or attempt to open a Lithium battery. This can release
hazardous material or cause spontaneous ignition.
• NEVER store equipment containing Lithium batteries above 70ºC.
• NEVER expose a Lithium battery to fire. Incineration or overheating of a Lithium
battery can result in venting or an explosion.
• ALWAYS insulate battery terminals before transporting batteries.
• ALWAYS observe the polarity of Lithium batteries and ensure correct connection.
• ALWAYS insulate terminals before disposal.
Accident Procedures
If a Lithium battery is damaged and venting or spillage occurs, proceed as follows:
Evacuate the area and ventilate with fresh air.
Wear face mask, goggles and gloves while cleaning up.
Disconnect batteries without creating any sparks and place battery in a remote, well
ventilated area.
Lithium battery liquid is corrosive. Use plenty of clean water to remove spillage.
Use carbon dioxide extinguishers for fires involving Lithium batteries.
2.5.8 Electrostatic Sensitive Devices
Caution Certain Printed Circuit Cards (PCCs) equipment contain Electrostatic Sensitive Devices
(ESDs) which may be damaged or destroyed by incorrect handling.
These PCCs are to be handled in accordance with the following precautions and with
any additional local instructions for handling ESDs:
• When removing or installing PCCs, wear a tested wrist strap and cord connected
to the cubicle/vehicle frame.
• Grasp PCCs by their handles or edges only. Do not touch circuit cards or connector
pins
• Ensure that all spare PCCs, and those being returned for repair, are enclosed in
the original packaging or in anti-static bags.
224
2.5.9 Module and Cards Storage And Transit
Caution WESTRACE modules and cards in storage or in transit:

• must not be in close proximity to magnets, e.g. Automatic Warning System (AWS)
magnets.
• must be packaged to:
• protect from damage due to electrostatic discharge.
• protect from the environment including physical handling damage.
Conductive frames or racks can be used to store modules and cards. Ensure that any
exposed connectors or pins will be static safe. Anti-static bags and wraps are the
preferred packaging for storage.
2.5.10 Use of Mobile Phone/Mobile Radio Units
Caution: Do not operate radio transmitters, mobile phones, vacuum cleaners or power tools
within close proximity unless the equipment is under a possession. The radio
frequency emissions can effect the operation of computer-based systems.

224
Section 3 - Operating Procedures - Local
3 Operating Procedures - Local
3.1 Introduction
The TF runs under Windows XP® embedded, using the Microsoft.NET framework. The
standard Microsoft Windows® facilities to open and close, to scroll up and down and to
select items using menus and toolbars are all supported.
3.1.1 Facilities
Windows available
There are a series of windows available which show the current state of signalling
objects:
• State Viewer (see Section 3.6)
This window displays lists of signals, points, routes, track circuits, flags, timers,
requests or (trackside functional module) telegrams, direct inputs and WESTLOCK
equipment, as selected by the user.
Lists are selected by clicking on Tabs located at the bottom of the window, and may
be expanded to show additional information regarding each item on the list.
These lists provide the user with a quick method of viewing the current state of any
item or attribute in the interlocking area. Items or attributes may be dragged to a
Monitor window if required (see below).
• Mimic Display Window - Track Diagram (see Section 3.7)
This displays the track plan and state of the railway in varying degrees of detail, as
required by the user.
• Attribute & States Monitor Window (see Section 3.8 & 3.9)
This provides two separate windows into which items of interest to the user can be
dragged from the State Viewer.
This feature is especially useful during testing or fault finding, as specific signals or
attributes can be extracted and monitored by the user. Items can be dragged either
as a group, e.g. complete details of an individual signal, or as attributes - single
items from different groups.
The Attribute Monitor Window is used to monitor items or attributes from the State
Viewer and can be used to show the state changes of these monitored items. The
States Monitor Window is used to select and monitor a number of interlocking items
and can be used to show ‘All’ or ‘Selected’ state changes.
Area of Control (see SECTION 4 — AREA OF CONTROL (AoC))
This functionality allows an AoC to be taken or released in order to apply or remove

controls or to gain write access to the alarms view.
Technician Controls (see SECTION 5 — TECHNICIAN CONTROLS)
This enables the user to initiate Technician's requests using a dialog box. Typical requests
include enabling or disabling the interlocking and applying or removing Technician
Controls.

Alarms View (see SECTION 6 — ALARMS AND FAULT DIAGNOSIS)
Provides details of both current and cleared faults throughout the interlocking area.
Logging (see SECTION 7 — LOGGING)
Logging of status and fault messages is carried out as a background task onto three
Logging Drives (see Section 7.1).
224
3.2 Powering Up And Powering Down

3.2.1 Powering Up
Note: The TF-L should have been left powered up. If the monitor is powered down, restore
power by pressing and releasing the Power button on the front panel.
Note: In the event that the TF-L is powered down, please note that it can take several minutes
to start-up. Users should wait until Signal icons appear in the Signals State Viewer tab
before assuming the TF-L is ready to use.
Caution: The TF must always be run using a USER account, under no circumstances should an
ADMIN account be used. If the TF is run on a PC that is logged into an ADMIN
account, corrective action is required before the TF will run using a USER account.
Log folders created using the ADMIN account will not be accessible using a USER
account. All TF log folders must be deleted prior to restarting the TF using a USER
account.
3.2.2 Powering Down the Monitors
It is recommended that the monitor is powered down when not required for use.
To power down the monitor, press and release the Power button on the front panel. To
restore power, press the same button again.
3.2.3 Powering Down the TF-L
The TF-L should be left powered up and operating when connected to an operational
interlocking. This is to allow diagnostics to be performed and to provide logging.
Caution: Powering down the TF-L will halt the Data Logging function and prevent any alarms
being reported to the control centre.
The TF-L should only be powered down when under maintenance and the control of
the maintenance technician.
Note: Only a user with shutdown privileges can close the TF-L application.
1. Click the Access menu, select ‘Logon’ and log-on as the required user.
2. Click the Access menu again and select ‘Shutdown’.
3. A ‘Confirm Shutdown’ prompt will appear. Click ‘OK’ to continue.

3.2.4 Administrator Access
An Administrator can access the TF-L for housekeeping or software upgrade purposes by
logging on manually, as follows:
Note: Only a user with shutdown privileges can close the TF-L application.
If the TF-L is powered up, use steps 1-3 below.
If the TF-L is powered down, press and hold the SHIFT key while powering up the TF-L
housing, then go to 4.
1. Click the Access menu, select ‘Logon’ and log-on.
2. Click the Access menu again and select ‘Shutdown’.
3. A ‘Confirm Shutdown’ prompt will appear. Click ‘OK’ to continue.
Caution: If the user has shutdown the TF-L the Windows Desktop will become available -
allowing access to the Start Menu. Unless specifically authorised to do so, under no
circumstances should the user take any further action or leave the TF-L unattended
in this state. Unauthorised actions could result in significant damage to the TF-L
installation.
4. Click the Windows Start button and select ‘Restart’. While the PC is rebooting hold
down the SHIFT key.
5. When prompted enter the Admin password.
6. Perform housekeeping.
7. On completion of housekeeping re-start the PC for normal use. The TF-L application
starts automatically.
224
3.3 Logging in / Logging out

3.3.1 Introduction
The TF has varying levels of operation (roles) - all configurable by the Administrator. The
Administrator can edit, create and delete these roles, assigning each with varying levels
of access. ‘Default’ is the default role used on start-up of the TF-L and does not require
the user to log-in. A user without Technician or Administrator rights can select and view
screens for information only. Facilities to which the user is not permitted access are
greyed out. For further information on ‘Users’ and ‘Roles’ refer to Section 3.3.4.
A user must log-on as ‘Maintainer’ to obtain use of the Technician Controls and as
‘Investigator’ to obtain access to the Event Replay Facility on a TF-R.
Log-on and log-off details are recorded in the Event log (see Section 7.4).
3.3.2 Log-On
To log on click on the 'Access' menu and select ‘Logon'. Complete the required entries in
the 'Username', ‘Role’ and ‘Password’ dialog box then click on 'Log On'. Note that the user
is required to log out at the end of the session, or the TF-L will automatically revert to the
default role after 30 minutes of inactivity.
Figure 3.1 — Log On dialog box
To increase the 30 minute inactivity timer, click on the 'Access' menu again, then select
'Expand Inactivity Time'. This opens a dialog box enabling the user to specify the
expected period of inactivity. Alternatively, select ‘Turn Off Inactivity Timer’.

Figure 3.2 — Change Inactivity Time dialog box’
Caution: Follow Railway Authority procedures with respect to control of access to the
Technician's Facility.
If an authorised user is logged on, but not present, the facilities are open to use by
unauthorised personnel.
It is recommended that authorised users close all open dialog boxes and log off
completely before leaving the workstation.
3.3.3 Log-Off
To log off, click on the 'Access' menu and select 'Logoff'.
3.3.4 Logged In As Administrator
Note: User Management functions are performed on the TF-R. The exception to this is when
there is no TF-R configured, in which case the TF-L should be used.
Logging in as Administrator provides access to the User Management functions. User

Management allows the maintenance of ‘Users’ and ‘Roles’. A ‘User’ refers to an account
that is assigned credentials (a username and password) used to logon to the TF. The
functionality the user is allowed to perform is defined by the ‘Role’. Roles are specified by
defining a user group and allowing no access or full access to each operation (see Table
3.1). Access by a user to each group can be controlled either by associating a password
with the group or with the individual user.
As the functionality the user is allowed to perform is defined by the role, the TF allows
users to have more than one role. The user is required to log on using a unique role name
to enable access to specific functionality. To gain access to different functionality, the
user is required to log off and log in using a different role name.
Various roles may be created, for example - one with access to the Technician Controls
and one without. Both Users and Roles are combined through the User Management
console to manage multiple user accounts. Users are assigned roles and Roles are
effectively assigned privileges.
224
If a user is configured for ‘Individual Password’ access, the password entered shall
correspond to the stored password associated with the username. If a user role is
configured for ‘Common Password’ access, the password entered shall correspond to the
stored password associated with the selected user role.
Once logged on as Administrator (see Section 3.3.2) the user is presented with the
following two menus and sub-options:
Access -
Logoff - opens a prompt to log-off, shutdown or cancel.
Shutdown - shuts down the TF-L application.
User Management -
View Roles - view the role name, type and operations. A role list can
also been exported.
Edit Roles - add a new role or modify or delete a selected role. A role
list can also be exported. (Area of control needs to be
taken.)
View Users - view the users and their assigned roles.
Edit Users - add a new user or modify or delete a selected user. A
user list can also be exported. (Area of control needs to
be taken.)
Change Password - change the Administrator password.
3.3.5 User Management functions
Once logged in as Administrator (see Section 3.3.4) the User Management menu is
available. The following describes each operation:
3.3.5.1 View Roles
Displays a read only view of the roles created on the TF. Three fields of information are
given:
• Role Name - a user defined name given to the role account.
• Role Type - displays one of three password settings, defined when
the role is created. Options include ‘Default’, ‘Common
Password’ and ‘Individual Password’.
• Role Operations - provides a list of functions available to the selected role.
Table 3.1 — Role Operations
Operation Description
Without this operation assigned, the user cannot select items
ItemSelection
(attributes and interlocking states) for monitoring.
When assigned this operation enables the user to collapse or

TreeLayout
expand group entries in tree views (eg. the State Viewer).
This enables the user to start/stop monitoring items and to also

MonitoringCommands
clear the monitoring views.
This operation allows access to commands that should only be

IRTechCommands
carried out by Siemens Rail Automation technicians.

Table 3.1 — Role Operations
Operation Description
When assigned, enables the user to manipulate the layout of
AlarmsDisplay
the Alarms View and also allows access to the Alarm reports.
Enables the user to acknowledge and action alarms. Operation

AlarmsControl
is available only if ‘AreaOfControl’ has also been assigned.
Without this operation assigned, the pane layout icons and

Layout
View menu are disabled.
Permits access to all reporting functionality except Alarm

reports. This includes Technician Control reports, monitored
Reporting
attribute and interlocking item reports, and historical database
reports.
AccessLogon Enables the Logon command.
Without this operation assigned, all ‘Access’ menu items are

disabled.
AccessControl
The user will not be able to log off without this
operation.
With this operation assigned, the user is permitted to select
Shutdown
‘Shutdown’ from the ‘Access’ menu.
With this operation assigned, the user has access to the User
Management functionality. Note that this functionality is only
available at the TF-R.
UserManagement
Users and Roles may be created, edited and deleted
at will with this operation assigned.
Without this operation assigned, the user cannot access the
TechnicianControl Technician Controls. Within the ‘Technician Controls’ menu,
‘Apply or remove control’ is disabled.
Enables the user to take or release control of the Area Of

Control items at a location. These items are Alarms (for
AreaOfControl
acknowledging and actioning alarms) and Interlocking (for
applying and removing Technician Controls).
Caution: Care should be taken when assigning Role Operations to the Default or Common
Password Role Types. Follow Railway Authority procedures with respect to control of
access to the Technician's Facility.
224
Figure 3.3 — View Roles dialog box
The user may export a file containing the current roles by clicking ‘Export Role List’. A
dialog box appears allowing a filename to be entered. For more information on
exporting refer to Section 7.5.
Figure 3.4 — Export Role List
3.3.5.2 Edit Roles
The Edit Roles dialog box presents the same information to that provided within View
Roles. The following additional features are provided: Add New Role, Modify Selected
Role and Delete Selected Role.

Figure 3.5 — Edit Roles dialog box
Note: This is current functionality not yet supported.
Add New Role

Clicking this button opens a new dialog box. The user is required to enter a new Role
Name, select a Role Type and finally the Operations available to this role.
Figure 3.6 — Add New Role dialog box
224
Modify Selected Role

To modify an existing role first select the required role then click the ‘Modify Selected
Role’ button. Fields that can be modified include Role Name, Role Type and Role
Operations.
Figure 3.7 — Modify Role dialog box
Delete Selected Role

To delete a role first select the required role then click the ‘Delete Selected Role’ button.
A ‘Confirm Delete Role’ prompt appears. Click ‘Yes’ to delete or ‘No’ to cancel the deletion.
3.3.5.3 View Users
Displays a ready only view of the users created on the TF. Two fields of information are
given:
• User Name - the name given to the user account
• User Role - the name given to the role account

Figure 3.8 — View Users dialog box
The user may export a file containing the current roles by clicking ‘Export Role List’. A
dialog box appears allowing a filename to be entered.
Figure 3.9 — Export User List
224
3.3.5.4 Edit Users
The Edit Users dialog box presents the same information to that provided within View
Users. The following additional features are provided: Add New User, Modify Selected
User and Delete Selected User.
Figure 3.10 — Edit Users dialog box
Add New User

Clicking this button opens a new dialog box. The user is required to enter a new User
Name and Password if an individual password is required. The new user is assigned a role
(see Section 3.3.5.1) by clicking the check box next to the required role.
Figure 3.11 — Add New User dialog box

Modify Selected User

To modify an existing user first select the required user then click the ‘Modify Selected
User’ button. Fields that can be modified include the User Name and assigned Role. To
apply or update the Individual Password click the ‘Update Individual Password’ check box
and enter the required password.
Figure 3.12 — Modify User dialog box
Delete Selected User

To delete a user first select the required user then click the ‘Delete Selected User’ button.
A ‘Confirm Delete User’ prompt appears. Click ‘Yes’ to delete or ‘No’ to cancel deletion.
3.3.5.5 Change Password
Opens a dialog box enabling the user to change the Administrator password. The old
password must be entered first followed by the new. The user is required to confirm the
new password a second time.
Figure 3.13 — Change Password dialog box
224
3.3.6 Creating a New User

1. Log-on as Administrator as per Section 3.3.2.
2. If the Role has not been created, do so now as per Section 3.3.5.2.
3. Add a new user as per Section 3.3.5.4.

3.4 TF Screen Layout

3.4.1 TF-S Initial Screen
The TF-S currently has no user interface.
3.4.2 TF-L and TF-R Initial Screen
Title bar
Menu bar
Pane layout
icons
Pane
Toolbar
State viewer
Main
window
Status bar
Figure 3.14 — Example: Technician's Facility (Local) Initial Screen
Note: The title bar shows the version of TF software, Geographic Data, Configuration data,
Model data and CMF.
The initial screen (Figure 3.14) provides Title Bar, Menu Bar, Pane Layout Icons, Pane
Toolbar, Status Bar, State Viewer and Main Window. A cursor ( ) controlled by the
mouse will be present on the screen.
Using the Screen View Icons ( ), the current view may be changed from the
default two pane layout to that of a one or three pane layout. One Pane Layout
maximises the currently active window.
The State Viewer is used to display the current states of signalling objects, expandable
by the user. Signalling objects are divided into lists (points, signals etc), selected by
clicking on the appropriate Tab at the bottom of the window.
To expand the list to show all items on the list, click on the (Expand) box. A complete
list is shown of all the item types (signals, points etc.) selected.
224
If the list is too long to be displayed in the window, a scroll bar will appear on the right-
hand side of the window. Scroll down (see Section 1.5) to view the remainder of the
items in the window.
To expand an item in the list, click on the box adjacent to the item. To return the
expanded item to a heading only, click on the (Contract) box adjacent to the item.
The State Viewer can be hidden by clicking the One Pane Layout icon ( ).
To restore the State Viewer click either the Two or Three Pane Layout icon ( ).
An explanation of the various State Viewer displays is contained in 'Use of the State
Viewer', Section 3.6.
When in One or Two Pane Layout, the Main Window can be changed to another window
view by clicking on the Pane Toolbar tabs (Track Diagram, Alarms View, Attribute
Monitor,etc).
Holding the mouse pointer over a button will cause a 'Tool Tip' to be displayed. A Tool
Tip is a brief description of the function of the button, as shown in Figure 3.15.
Tool Tip
Figure 3.15 — Example of a Tool Tip
Opening Additional Windows
The following additional windows are available where applicable:

1. Track Diagram see Section 3.4.3.
2. Alarms View see Section 3.4.4.
3. Attribute Monitor see Section 3.4.5.
4. States Monitor see Section 3.4.6.
5. Events To Replay (TF-R and SERFG only) see Section 8.3.5.
6. Replayed Events (TF-R and SERFG only) see Section 8.3.7.
3.4.3 Track Diagram Mimic Window
The name assigned to this tab(s) will vary with differing deployments. It shall be referred
to as the ‘Track Diagram’. The Track Diagram window is open by default and may be re-
sized as required (as explained in Section 1.5).
TF-Rs can display multiple Track Diagram tabs within the pane toolbar. Each TF-L
connected to the TF-R will be represented by its own tab.

The basic Track Diagram (Figure 3.16) provides:

• A title showing the interlocking name
• The track layout
• Positions of platforms, bridges and tunnels
• Position of signals with lit aspect shown
• Position of points with condition shown
• Condition of track section with occupancy shown
The following additional information can be added to, or removed from the basic Track
Diagram by clicking on the corresponding icon in the Pane Toolbar. This is shown in
Figure 3.17.
Miscellaneous labels Names are added respectively
Point labels Names are added in black text adjacent to each

set of points
Signal labels Names are added in black text adjacent to each

signal
Track labels Names are added in black text adjacent to each

track circuit
Power labels Shows the position and identity of trackside

power supply equipment
Location labels Shows the position and identity of location cases
Lie of points A yellow bar appears next to each set of points

showing the 'Normal' lie of those points
Note: Labels will only be displayed on the Track Diagram if they have been added at the design
stage.
Zoom In and Zoom Out buttons can be used to alter screen magnification if
required.
Click to restore the zoom level to 100%.
224
Figure 3.16 — Example: Typical Basic Track Diagram Window
Figure 3.17 — Example: Typical Track Diagram with all options labels selected
3.4.4 Alarms View
This window lists alarms and allows a user with the relevant access to acknowledge and
action alarms. The following fields of information are provided: Id, Fault Description,
Criticality, Time, Occurrences and State. For more information refer to Section 6 - Alarms
and Fault Diagnosis.

3.4.5 Attribute Monitor
For the attributes currently monitored, this tab provides information on ‘All’ or ‘Selected
Attribute Changes’. The following fields are given: Date & Time, Attribute and Value.
The Pane Toolbar provides the following icons as a means to manipulate the currently
monitored data:
Stop monitoring Once clicked changes to ‘Start monitoring’ icon.
Start monitoring Clicked again will change to ‘Stop monitoring’

icon.
Clear monitor windows Clears all current entries.
Apply filter Filters attributes to show historical events as

opposed to those currently monitored.
Export data Clicking the down arrow produces three options:

‘Export all attribute states’, ‘Export all attribute
changes’ and ‘Export selected attribute changes’.
Once the user has selected the required option,
the dialog box below opens.
Figure 3.18 — Export attribute states dialog box
For more information on the Attribute Monitor refer to Section 3.8.
3.4.6 States Monitor
This tab provides information on ‘All States’, ‘All State Changes’ or ‘Selected State
Changes’ of the interlocking. Name, State, Source and Direction are values given.
Additional icons provide a means of displaying this data:
Show alphabetic Expand all nodes Collapse all nodes
Figure 3.19 — States Monitor toolbar
224
The Pane Toolbar provides icons as Section 3.4.5 above. The export data icon will export
interlocking states/changes as opposed to attribute state/changes.
For more information on the States Monitor refer to Section 3.9.

3.5 Use of the Menu Bar

3.5.1 Introduction
The Menu bar is located immediately below the Title bar on the initial screen and
provides access to all the functionality provided by the TF-L.
To use a menu, click on a heading in the Menu Bar. This results in the display of a drop-
down menu containing items as detailed below. Select the required item from the drop-
down menu by clicking on it. Items not available from the menu are greyed out.
3.5.2 Menus Provided
The following menus are provided:
Access -
Logon - opens a log-on prompt requiring
username, role and password.
Logoff - logs off the current user.
Expand Inactivity Time - increases the time value specified for
inactivity.
Turn off Inactivity Timer - deactivates the inactivity timer.
Shutdown - shuts down the TF-L application.
View -
One pane layout - maximises the currently active
window.
Two pane layout - splits the screen into two panes
showing the State Viewer and Track
Diagram window.
Three pane layout - splits the screen into three panes
showing the State Viewer, Track
Diagram and Alarms/Monitoring
windows.
Asset Management - shows a dialogue giving version
information summary.
Technician Controls -
Apply or remove control - allows the Technician to apply or
remove control of any trackside
equipment.
Reports - view currently applied Technician
Controls. Provides options for viewing
both current and historic data, as well
as defining the differences between
the two.
AOC -
Take control - this allows the Technician to take
control of an area & alarms.
224
Release control - having taken control this allows the

Technician to release it back to its
default state.
Export -
Export all interlocking states - save, print or preview report.
Export all interlocking changes - save, print or preview report.
Export selected interlocking changes - save, print or preview report.
Export all attribute states - save, print or preview report.
Export all attribute changes - save, print or preview report.
Export selected attribute changes - save, print or preview report.
Export control states - this is the same report as Technician
Controls - Reports.
Reports -
Alarm report - opens an alarm report dialog box.
Log report - select and view recorded log data.
Choose from the Interlocking,
Interlocking Event, Signalling Model,
Alarms, Technician Controls and
Access Control log data.
J-Log mount/dismount - (TF-L only)

J-Log 1 (drive E:) - mount or dismount J-Log 1 (drive E:).
J-Log 2 (drive F:) - mount or dismount J-Log 2 (drive F:).
Replay - (TF-R only) - shows a dialog box providing event

source options.
Note: Controls are greyed out when they are not available at the selected access level.

3.6 Use of the State Viewer

3.6.1 Purpose
The State Viewer allows the user to view the current state of every item within the
WESTLOCK system.
The layout of the State Viewer is shown in Figure 3.20.
Expand all nodes Monitor all equipment
Collapse all nodes
Collapse Node. Click

to contract the node
and hide the lower
level nodes
Scroll Bar - position
cursor over scroll box,
press and hold left
hand mouse button
then move the mouse
Expand Node. Click to bring the required
to reveal lower level area of the display into
nodes view
Indicates amount of
display outside the
area of the window
Click on Tab to select required view - Signals, Points etc.
Figure 3.20 — Example State Viewer Layout
224
If viewing the State Viewer from a TF-R, multiple TF-Ls can be displayed within the
appropriate tabs. See Figure 3.21.
TF-Ls
Figure 3.21 — Example TF-R State Viewer Layout

Table 3.2 — State Viewer Tab Meanings
TAB VIEW
Signals Signals
Tracks Track Circuits
Points Points
Routes Routes
TbO Trackside Telegrams by Object
FbO FEP Telegrams by Object
TFM Trackside Telegrams by TFM
VTFM Virtual Telegrams by TFM
DIO Direct Input Telegrams
W2W WESTLOCK to WESTLOCK Telegrams
WNC WESTRACE Network Communications
WLE WESTLOCK Equipment
Flags Flags
Requests Panel Requests
TF Technician’s Facility
IOM Input / Output Module
The general style of the State Viewer is similar to the Folders view in the Microsoft
Windows® Explorer for navigating the file structure of a PC.
The State Viewer is divided into a number of panes, accessible via tabs at the bottom of
the window. The TF always presents tabs in the State Viewer, even if there is no
information to be displayed within a pane. Click on a Tab to access the associated pane.
The following paragraphs show example panes with explanatory annotations.
Within the State Viewer, states that are True are shown as a 1 within a blue square.
Unknown states are shown as a question mark within a blue square.
Note: The icon colour shown for TF items show green for full operation, red for total failure
and yellow for partial failure. Faults may be seen by expanding the icon to reveal
individual items or checking alarms.
Note: The TF only displays bits on the DIO, TFM and TbO tabs if they have been configured.
Note: All attributes throughout the TF use a ‘-’ to separate the attribute name from its value.
When the value is negative it will be displayed thus: Time offset - - 12345.00.
224
3.6.2 Signal Explorer View
Click on the 'Signal' Tab to obtain this view.

Signal Symbols
R Most Restrictive
Red
Green
Yellow
Double Yellow
Call-on or Main with Sub
Figure 3.22 — Example: Signals State Viewer Layout
The list shows all the signals controlled by the interlocking and the aspect displayed (as
driven by the interlocking).
Clicking on the for a signal name expands the entry as shown below.
Identifies Signals View

and aspect
Signal Name
Items applicable to
Signal S126 where:
0 = Not true
1 = True
Figure 3.23 — Example: Signals State Viewer Expanded Layout

3.6.3 Tracks Sections Explorer View
Click on the 'Tracks' Tab to obtain this view.
Figure 3.24 — Example: Track Sections State Viewer Layout
Clicking on the for a track section name expands the entry as shown below.
Identifies Track Sections View.

Icon colour identifies track
section state:
Red - occupied (not proved clear)
Blue - proved clear
Grey - status unknown (no
connection)
Items applicable to T1 where:

Track Section 0 = Not true
identifier 1 = True
Figure 3.25 — Example: Track Sections State Viewer Expanded Layout
224
3.6.4 Points Explorer View
Click on the 'Points' Tab to obtain this view.
Point symbols:
Normal
Reverse
Out of
correspondence
Figure 3.26 — Example: Points State Viewer Layout
Clicking on the for a points name expands the entry as shown below.
Points Name
Identifies Points View.

Icon shows current lie
of P150
Items applicable to Point

P150 where:
0 = Not true
1 = True
Figure 3.27 — Example: Points State Viewer Expanded Layout

3.6.5 Routes Explorer View
Click on the 'Routes' Tab to obtain this view.
Figure 3.28 — Example: Routes State Viewer Layout
Clicking on the for a route name expands the entry as shown below.
Route Name
Icon colour signifies:
Green - Route Set
Black - Route available
Items applicable to
Route R35A(C) where:
0 = Not true
1 = True
Figure 3.29 — Example: Routes State Viewer Expanded Layout
224
3.6.6 Flags Explorer View
Click on the 'Flags' Tab to obtain this view.
Figure 3.30 — Example: Flags State Viewer Layout
Clicking on the for Sub Routes expands the entry as shown below.
Sub Route Name
Item applicable to Sub Route

U779C(M/C)(WY)KW-BA
where:
0 = Not true
1 = True
Figure 3.31 — Example: Sub Routes State Viewer Expanded Layout
Clicking on the for Technician’s Latches expands the entry as shown below.
Items applicable to
Technician’s Latches
where:
0 = Not true
1 = True
Figure 3.32 — Example: Technician’s Latches State Viewer Expanded Layout

3.6.7 Panel Requests Explorer View
Click on the 'Requests' Tab to obtain this view.
Figure 3.33 — Example: Requests State Viewer Layout
Clicking on the for Panel Requests expands the entry as shown below.
Panel Request List
Panel Request Queue.

Up to 20 entries with latest
entry in position 1.
Figure 3.34 — Example: Requests State Viewer Expanded Layout
224
3.6.8 Trackside Telegrams by TFM Explorer View
Click on the 'TFM' Tab to obtain this view.
Figure 3.35 — Example: TFM State Viewer Layout

Clicking on the for WILWEST 15 expands the entry as shown below.
where: WILNTH 9
TIF TDL
Name Number
Telegram Name
Items applicable to
Telegram TFM 1 where:
0 = Not true
1 = True
Figure 3.36 — Example: TFM State Viewer Expanded Layout
224
3.6.9 Trackside Telegrams by Object Explorer View
Click on the 'TbO' Tab to obtain this view.
Figure 3.37 — Example: TbO State Viewer Layout (Level 1 Nodes)
Clicking on the for WILACTON 12 expands the entry as shown below.
Figure 3.38 — Example: TbO State Viewer Layout (Level 2 Nodes)

Clicking on the for Signals expands the entry as shown below.
Name of Trackside
Interface (TIF)
Type of Signalling Object
Name of Signal
Telegram Type (Output)
where: S655 R GE[47/7]
Bit TFM Bit

Name Number Number
Telegram Type (Input)
State of Bit where:

0 = Not true
1 = True
Figure 3.39 — Example: TbO State Viewer Expanded Layout
The same process may be used to expand Points, Tracks, Latches etc. to view the
associated telegrams.
Note: Where an object uses more than one TFM, then those TFMs may be on different
trackside data links. It will be necessary to open more than one TbO overview to see that
complete object.
Note: If there are no items under a TIF sub heading i.e. Signal, Point, Track, Latch,
Miscellaneous Proving or Miscellaneous Non-Proving Inputs, then that sub heading will
not be displayed in the State Viewer.
224
3.6.10 WESTLOCK to WESTLOCK Telegrams Explorer View
Click on the 'W2W' Tab to obtain this view.
Figure 3.40 — Example: W2W State Viewer Layout

Clicking on the for RefSys1 expands the entry as shown below.
Name of connected
Adjacent CIP
Telegram Number
Bit settings for Telegram 1

where:
0 = Not true
1 = True
Bits telegram
Codes telegram
Current code in telegram 4
Last non-zero code in

telegram 4
Figure 3.41 — Example: W2W State Viewer Expanded Layout
224
3.6.11 Direct Input Telegrams Explorer View
Click on the 'DIO' Tab to obtain this view.
Figure 3.42 — Example: DIO State Viewer Layout
Clicking on the for Telegram 0 expands the entry as shown below.
Items applicable to
Telegram 0 where:
0 = Not true
1 = True
Figure 3.43 — Example: DIO State Viewer Expanded Layout

3.6.12 WESTLOCK Equipment Explorer View
Note: Normal values for the WESTLOCK Equipment Explorer (WLE) entries are given in Table
9.3. Corrective actions for incorrect values are given in Table 9.4.
Note: The WLE tab will not display any states for two minutes after the TF-L has been powered
up.
Note: If the WESTLOCK Address and Software Version are not populated in the WLE tab, all the
other information for the CIP or TIF should not be relied upon. Ensure that the related
CIP or TIF is connected to the signalling network.
Click on the 'WLE' Tab to obtain this view.
Figure 3.44 — Equipment Explorer View Layout (Level 1 Node)
Clicking on the for LeamingtonSpa expands the entry as shown below.
Interlocking status
where:
0 = Not true
1 = True
Expand for further information

(see Figure 3.46)

(see Figure 3.56)

(see Figure 3.59)

(see Figure 3.67)

(see Figure 3.77)
Figure 3.45 — Equipment Explorer View Layout (Level 2 Nodes)
224
Expand CIP to obtain:
Current status
CIP status where:

0 = Not true
1 = True

(see Figure 3.47 to Figure 3.55)
Figure 3.46 — Equipment Explorer View Layout (CIP Level 3 Nodes)

Expand MP Status and Left MP Status to obtain:
Current states of
items common to all
three MPs where:
0 = Not true
1 = True
Left MP Status
where:
0 = Not true
1 = True
Expand to give information as

for Left MP above
Figure 3.47 — Equipment Explorer View Layout (MP Status Level 4 and 5 Nodes)
224
Expand CM Status and Left CM Status to obtain:
Left CM Status
where:
0 = Not true
1 = True
Expand to give information

as for Left CM above
Figure 3.48 — Equipment Explorer View Layout (CM Status Level 4 and 5 Nodes)
Expand DI 1 Status and Left DI 1 Status to obtain:
Current states of
items common to
both DIs where:
0 = Not true
1 = True
Left DI Status where:

0 = Not true
1 = True

as for Left DI above
Figure 3.49 — Equipment Explorer View Layout (DI 1 Status Level 4 and 5 Nodes)

Expand Application Status to obtain:
CIP Application
Status where:
0 = Not true
1 = True
Figure 3.50 — Equipment Explorer View Layout (CIP Application Status Level 4 Nodes)
Expand Comms Alarm Status to obtain:
Comms Alarm Status

where:
0 = Not true
1 = True
Figure 3.51 — Equipment Explorer View Layout (Comms Alarm Status Level 4 and 5 Nodes)
Expand Link Status to obtain:
Link Status where:

0 = Not true
1 = True
Figure 3.52 — Equipment Explorer View Layout (Link Status Level 4 and 5 Nodes)
Note: Link status information can take up to half a minute to be updated following failure or
repair of a link. This is normal operation.
Note: Care must be taken when checking equipment network link status. The TF-L link status
should be used to confirm status of the network links.
224
The CIP and TIF link status shows that the link is healthy provided there is a physical
connection plugged in, but does not take into account the diagnostic status. Therefore
relying purely on the reported CIP or TIF link status can cause a problem such as an
incorrectly configured IP address to be missed.
The TF link status takes the diagnostic status into account, and therefore should be used
to confirm link status. Although unlikely, it is possible that an IP addressing error has
been made during data preparation and that a link is potentially operating without
redundancy. Checking the TF-L link status will identify this issue.
Expand Sig N/W Safety Layer Status to obtain:
Current status
where:
0 = Not true
1 = True
Figure 3.53 — Equipment Explorer View Layout (Safety Layer Status Level 4 and 5 Nodes)
Expand Sig N/W Context Status to obtain:
Current status
where:
0 = Not true
1 = True
Figure 3.54 — Equipment Explorer View Layout (Context Status Level 4 and 5 Nodes)

Expand Version Numbers to obtain:

Version number is
correct value
Version number
Figure 3.55 — Equipment Explorer View Layout (Version Numbers Level 4 and 5 Nodes)
Expand CSG to obtain:
Current status
CSG status where:

0 = Not true
1 = True
Expand for further

information
(see Figure 3.57 to
Figure 3.58)
Figure 3.56 — Equipment Explorer View Layout (CSG Level 3 Nodes)
224
Link Status where:

0 = Not true
1 = True
TD Links status
where:
0 = Not true
1 = True
Expand PMUX Status to obtain:

Indicates Panel Multiplexer
information
PMUX Status where:

0 = Not true
1 = True
Figure 3.58 — Equipment Explorer View Layout (PMUX Status Level 4, 5 and 6 Nodes)

Expand FEP to obtain:
Current status
Expand for further

information
(see Figure 3.60 to
Figure 3.66)
Figure 3.59 — Equipment Explorer View Layout (FEP Level 3 Nodes)
Expand SMB A to obtain:
SMB A Status where:

0 = Not true
1 = True

as for SMB A above
Figure 3.60 — Equipment Explorer View Layout (SMB Level 3 and 4 Nodes)
224
Expand PM Primary to obtain:
Current status where:

0 = Not true
1 = True

as for PM Primary above
Figure 3.61 — Equipment Explorer View Layout (PM primary and PM secondary
Level 3, 4 and 5 Nodes)

Expand Vital and Non-vital communications to obtain:
Vital communications
status where:
0 = Not true
1 = True
Non-vital communications
status where:
0 = Not true
1 = True
Figure 3.62 — Equipment Explorer View Layout (Vital and Non-vital communications
Level 3, 4 and 5 Nodes)
224
Expand IOMs to obtain:
where: SOM110 3 3
IOM Housing Slot

type
Current status
Expand for further

information
(see Figure 3.64)
Expand for further
information
(see Figure 3.65)
Figure 3.63 — Equipment Explorer View Layout (IOMs Level 4, 5 and 6 Nodes)

Expand IOM status to obtain:
Items applicable to
SOM110 3 3 where:
0 = Not true
1 = True
Figure 3.64 — Equipment Explorer View Layout (IOM Status Level 6 Nodes)
224
Expand SOM110 status to obtain:
Items applicable to
SOM110 3 3 where:
0 = Not true
1 = True
Figure 3.65 — Equipment Explorer View Layout (SOM110 Status Level 6 and 7 Nodes)

Expand FenSouth1 to obtain:

RSMB name
where: RSA-A[3/1]
Channel Housing Slot
Items applicable to
RSMB where:
0 = Not true
1 = True
Figure 3.66 — Equipment Explorer View Layout (FenSouth1 Level 4 and 5 Nodes)
Expand TIF to obtain:
Current status
TIF status where:

0 = Not true
1 = True

(see Figure 3.68 to Figure 3.77)
Figure 3.67 — Equipment Explorer View Layout (TIF Level 3 Nodes)
224
Expand MP Status and Left MP Status to obtain:
Current states of
items common to all
three MPs where:
0 = Not true
1 = True
Left MP Status
where:
0 = Not true
1 = True
Expand to give information as

for Left MP above
Figure 3.68 — Equipment Explorer View Layout (MP Status Level 4 and 5 Nodes)

Expand CM Status and Left CM Status to obtain:
Left CM Status
where:
0 = Not true
1 = True

as for Left CM above
Figure 3.69 — Equipment Explorer View Layout (CM Status Level 4 and 5 Nodes)
224
Expand SCM Status and Left SCM Status to obtain:
Current states of
items common to
both SCMs where:
0 = Not true
1 = True
Left SCM Status

where:
0 = Not true
1 = True

as for Left SCM above
Figure 3.70 — Equipment Explorer View Layout (SCM Status Level 4 and 5 Nodes)

Expand Application Status to obtain:
TIF Application
Status where:
0 = Not true
1 = True
Figure 3.71 — Equipment Explorer View Layout (TIF Application Status Level 4 Nodes)
Expand Comms Alarm Status to obtain:
Comms Alarm Status

where:
0 = Not true
1 = True
Figure 3.72 — Equipment Explorer View Layout (Comms Alarm Status Level 4 and 5 Nodes)
224
Link Status where:

0 = Not true
1 = True
Expand Sig N/W Safety Layer Status to obtain:
Current status
where:
0 = Not true
1 = True
Figure 3.74 — Equipment Explorer View Layout (Safety Layer Status Level 4 and 5 Nodes)
Expand Sig N/W Context Status to obtain:
Current status
where:
0 = Not true
1 = True
Figure 3.75 — Equipment Explorer View Layout (Context Status Level 4 and 5 Nodes)

Expand Version Numbers to obtain:

Version number is
correct value
Version number
Figure 3.76 — Equipment Explorer View Layout (Version Numbers Level 4 and 5 Nodes)
Expand TF to obtain:
Current status
Figure 3.77 — Equipment Explorer View Layout (TF Level 3 Nodes)
224
3.6.13 FEP (Front End Processor) Telegrams by Object Explorer View
Click on the 'FbO' Tab to obtain this view.
Figure 3.78 — Example: FbO State Viewer Layout (Level 1 Nodes)
Clicking on the for WEMBSTH 13 expands the entry as shown below.
Figure 3.79 — Example: FbO State Viewer Layout (Level 2 Nodes)

Clicking on the for Signals expands the entry as shown below.
Name of FEP
Type of Signalling Object
Name of Signal
Telegram Type (Output)
Housing Slot
where: S336 D GE[19/7/2]
Bit Bit
Name Number
Telegram Type (Input)
State of Bit, where:

0 = Not true
1 = True
Figure 3.80 — Example: FbO State Viewer Expanded Layout
The same process may be used to expand Points, Tracks, Latches etc to view the
associated telegrams.
224
3.6.14 Virtual Trackside Telegrams by TFM Explorer View
Click on the 'VTFM' Tab to obtain this view.
Figure 3.81 — Example: VTFM State Viewer Layout
Clicking on the for WEMBSTH 13 expands the entry as shown below.
Telegram Name
Items applicable to
Telegram VTFM 2 where:
0 = Not true
1 = True
Figure 3.82 — Example: VTFM State Viewer Expanded Layout

3.6.15 WESTRACE Network Communications Explorer View
Click on the 'WNC' Tab to obtain this view.
Figure 3.83 — Example: WNC State Viewer Layout
Clicking on the for JB1 0 expands the entry as shown below.
WNC channel name
Channel status
Items applicable to JB1 0

where:
0 = Not true
1 = True
Figure 3.84 — Example: WNC State Viewer Expanded Layout
224
3.6.16 TF Explorer View
Click on the 'TF' Tab to obtain this view.
Figure 3.85 — Example: TF State Viewer Layout

Clicking on the of an object name expands the entry as shown below.
State & items

connected to the TF
Icon colour identifies

Interlocking state:
Red - no connection
Green - connected
Yellow - partially
connected
Grey - unknown
Applied Area Of
Control
Information on
Removable Logging
Drive J-Log 1
Information on
Removable Logging
Drive J-Log 2
Information on the
Fixed Logging Drive/
W-Log
Figure 3.86 — Example: TF State Viewer Expanded Layout
224
3.6.17 IOM (Input / Output Modules) Explorer View
Click on the 'IOM' Tab to obtain this view.
Figure 3.87 — Example: IOM State Viewer Layout
Clicking on the for FEP[FenSouth] expands the entry as shown below.
R-SMB Name
IOM Name
Items applicable to
SOM110[3/3] where:
0 = Not true
1 = True
Figure 3.88 — Example: IOM State Viewer Expanded Layout

3.7 Use of the Track Diagram Mimic Window

3.7.1 Introduction
The Track Diagram window contains a mimic diagram showing the state of the railway
controlled by the CIP, and may also show details of some of the surrounding railway if
that area contains useful information.
Using the mimic diagram, the user can:
View the state of the railway (Section 3.7.2)
View displayed aspect of signals (Section 3.7.3)
View the lie of points (Section 3.7.4)
View track circuit occupancy (Section 3.7.5)
224
3.7.2 Viewing the State of the Railway
The mimic display is continuously updated to show the current condition of signalling
items and the positions of trains as detected by the track circuits.
Additional information can be added or removed in layers over the basic mimic diagram
by clicking on the corresponding icon in the Pane Toolbar:
Displays or removes miscellaneous labels
Displays or removes point labels
Displays or removes signal labels
Displays or removes track labels
Displays or removes power labels

Pane Toolbar Displays or removes location labels
Displays or removes lie of points labels
Track Diagram Mimic Window
Figure 3.89 — Example: State of Railway View

3.7.3 Viewing the Aspects of Signals
When signal aspects are lit (as seen by the CIP) then the signal on the mimic panel
displays the colour of the lit aspect.The signal names can be displayed or removed from
the display by clicking on the button.
Note: The following icons are given as non exhaustive examples only and may differ between
each deployment.
Aspect lit, colour as indicated.

The state of the proving is shown (EK, EC).
AWS magnets shown (black triangles).
Aspect not lit.
Shunt signals.
Banner Repeater signal.
Route Indicators
These are shown adjacent to the signal. A lit route
indicator contains a figure or letters representing the
RI not lit stencil or PLJI indication.
Note route indicators are never lit on the mimic at

present. In order to determine what route indicators are
showing, the State Viewer must be used.
RI lit
224
3.7.4 Viewing the Lie of Points
A Normal lie of points indication can be added to, or removed from the display by clicking
on the button. A yellow bar appears next to each set of points showing the Normal
lie of those points.
The point names can be displayed or removed from the display by clicking on the
button.
Basic points indication.
Points with Normal lie of points indication.
Points with Normal lie of points indication and points

name.
Points out of correspondence or Points failed.
Points with contactor proving relay.
= 1 = proved
= 0 = not proved

3.7.5 Viewing Track Section Occupancy
Track section identities can be displayed adjacent to each track circuit by clicking on the
button. To remove the identities, click on the button again.
Track section proved clear.
Track section not proved clear.
Track controlled by adjacent interlocking

or not controlled.
224
3.8 Use of the Attribute Monitor Window

3.8.1 Introduction
Selectable from the Pane Toolbar, the Attribute Monitor window allows the user to select
a number of items or attributes from the State Viewer and to place them in a dedicated
window where they are visible as a group. This is especially useful during testing, or for
diagnosis of intermittent faults. Selected attributes can be exported using the standard
export mechanism (see Section 7.5).
All items shown in Section 3.6 can be viewed in the Monitor window.
The Attribute Monitor can be set to show the state changes of the monitored items
(see Section 3.8.3).
3.8.2 Adding Items
To add items or attributes into the Attribute Monitor window:

1. At the State Viewer, open the list containing the required item.
2. If an attribute is required, expand the item by clicking on the adjacent to the item.
3. Click on the required item or attribute to highlight it.
4. Drag and drop the item or attribute into the ‘Selected Attributes’ area of the
Attribute Monitor, or right-click to open further context menu options.
Note: It is not possible to ‘Monitor all similar attributes’ of level one items within the State
Viewer. The attribute must be expanded to show the ‘state’ before the ‘Monitor all
similar attributes’ option becomes available by right-clicking. When selected the
information within the ‘Selected Attributes’ panel of the Attribute Monitor will currently
display all attributes and not all similar attributes.
Note: If a whole W2W telegram is selected and dragged into the ‘Selected Attributes’ panel of
the Attribute Monitor, the input and output items are not identified. The user must drag
the input and output items separately to overcome this problem.
Figure 3.90 — Example: Monitored attribute added
Note: Where a single attribute is added to the Attribute Monitor, the item to which the
attribute belongs is added to the display. For example in the above figure, the single
attribute ‘Controlled normal’ is added and therefore the identifier ‘Point P202’ is added
to the Attribute Monitor too.

To copy more items / attributes into the monitor window, repeat the above.
To remove an item from the window, first select then right-click to select ‘Remove’ or
‘Remove All’. Further options include ‘Fully expand’ and ‘Collapse all but this’.
The Monitor window may be re-sized (see Section 1.5) to view the displayed items.
Figure 3.91 — Example: Typical Attribute Monitor window displaying Tracks
Note: Signals, Points, Routes etc. provide similar displays if added to the Attribute Monitor
window.
3.8.3 Viewing Monitored Items
The Attribute Monitor window is divided into two views, selected via tabs at the top of
the window. Each tab gives access to a separate view. These views are:
All Attribute Changes - All changes of state, continually recorded by the TF.
Selected Attribute Changes - Changes of state of items chosen by the user.
The window may be re-sized (see Section 1.5) to view the displayed items.
224
Figure 3.92 — Typical Attribute Monitor window - All Attribute Changes
Note: The Attribute Monitor window is capable of displaying 10,000 entries. It will then begin
overwriting the oldest entries with the new.

3.9 Use of the States Monitor Window

3.9.1 Introduction
Selectable from the Pane Toolbar, the States Monitor window allows the user to select a
number of Interlocking items or attributes and to place them in a dedicated window for
monitoring. This is especially useful during testing, or for diagnosis of intermittent faults.
The States Monitor window consists of three views selected via tabs at the top of the
window (see Section 3.9.3). The default screen showing ‘All States’ is initially populated
with all Interlocking items, from which items can be dragged into the adjacent ‘Selected
States’ window. The items can be dragged as a group or as individual attributes.
3.9.2 Adding Items
To monitor interlocking items or attributes:

3. Drag and drop the item or attribute into the ‘Selected States’ area left of the
Interlocking Monitor window, or right-click to open further context menu options.
To add more items / attributes into the monitor window, repeat the above.
To remove an item from the window, first select then right-click to select ‘Remove’.
Alternatively select ‘Remove All’.
The Monitor window may be re-sized (see Section 1.5) to view the displayed items.
Show
categorised
Figure 3.93 — Example: Typical States Monitor window - Selected States
Items in the All States tab are by default shown as each individual attribute. However,
there is a ‘Show categorised’ button that allows the user to group attributes for an object
into a high level item that can be dragged to the Selected States tab. This negates the
need to drag each attribute individually.
224
3.9.3 Viewing Monitored Interlocking Items
The States Monitor window is divided into three views, selected via tabs at the top of the
window. Each tab gives access to a separate view. These views are:
All States - Default screen showing all Interlocking. Drag

items from this window into the ‘Selected States’
window to monitor.
All State Changes - This window continually monitors all Interlocking states.
Selected State Changes - This window monitors the items added to the ‘Selected
States’ window.
The window may be re-sized (see Section 1.5) to view the displayed items.
Figure 3.94 — Example: Typical States Monitor window - Selected State Changes
Note: The States Monitor window is capable of displaying 10,000 entries. It will then begin
overwriting the oldest entries with the new.

224
Section 4 - Area of Control (AoC)
4 Area of Control (AoC)
4.1 Introduction
Area of Control (AoC) refers to the interlocking area over which the Technician has
control. The functionality of this allows an AoC to be taken or released in order to apply
or remove controls or to gain write access to the alarms view.
Note: Prior to taking or releasing an AoC, the user must have logged on to the TF-L with the
required user role. Once logged in only one AoC may be assumed, avoiding multiple
users applying or interacting with alarms.
Two options are available within the AoC. The Technician may assume control over the
Alarms or Tech Controls, or both:
4.1.1 Alarms
Taking control of the alarms permits the ability to acknowledge and action alarms to the
selected area(s) of control. In taking control, other Technicians are prevented from
interacting with alarms of the same area.
4.1.2 Tech Controls
Taking control of the Tech Controls prior to applying Technician Controls allows
uninterrupted control of that area. Without this functionality another Technician may for
example apply or remove control of the same equipment. Taking control of the Tech
Controls prevents this from happening within the selected area(s).
Figure 4.1 — Example: Area of control selection dialog box - Take control

4.2 Take Control

To take control of an AoC:
1. Click ‘AOC’ on the Menu Bar.
2. Select ‘Take control’.
3. In the ‘Item’ column click on the icon to expand the tree.
4. Select the required item to control. To select both items simultaneously click the
head of the tree (‘WA1’ in the example below). Alternatively items can be selected
individually.
5. Once an item has been selected click the ‘Take Control’ button.
Figure 4.2 — Example: Area of control selection dialog box - Alarms selected
224
6. Note the ‘Status’ of the item has changed to show that control has been taken. Click
the ‘Close’ button once finished.
Figure 4.3 — Example: Area of control selection dialog box - Alarms control taken
7. To take control of another item repeat steps 1 to 6 above.
8. Clicking ‘Take control’ in the Menu Bar once control has been taken of all items the
following is shown:
Figure 4.4 — Example: Area of control selection dialog box - No items to control

4.3 Release Control

To release control of an AoC:
1. Click ‘AOC’ on the Menu Bar.
2. Select ‘Release control’.
3. In the ‘Item’ column click on the icon to expand the tree.
4. Select the required item to control. To select both items simultaneously click the
head of the tree (‘WA1’ in the example below). Alternatively items can be selected
individually.
5. Once an item has been selected click the ‘Release Control’ button.
Figure 4.5 — Example: Area of control selection dialog box - Alarms selected
224
6. Note the ‘Status’ of the item has changed to show that control has been released.
Click the ‘Close’ button once finished.
Figure 4.6 — Example: Area of control selection dialog box - Alarms control released
7. To release control of another item repeat steps 1 to 6 above.
8. Clicking ‘Release control’ in the Menu Bar once control has been released of all items
the following is shown:
Figure 4.7 — Example: Area of control selection dialog box - No items to release
Note: When a user logs off any AoC selections that have been made are automatically
relinquished.

224
Section 5 - Technician Controls
5 Technician Controls
5.1 Introduction
The Technician Controls refer to the ability of applying and removing control of trackside
objects. For a list of the available controls refer to Table 5.1. In applying control the
Technician assumes control over the signalling equipment for maintenance and
diagnostics. A Technician Controls report provides information on both the current and
recorded Technician controls.
Note: Prior to applying or removing technician controls, the user must have logged on to the
TF-L with the required user role. The user must have also taken control of the required
area(s) (see Section 4 — Area of Control (AoC)). This does not prevent other users from
logging onto the system, but access to area(s) already under the control of other users
is prohibited.
5.2 Determining Which Controls Are Applied

Before applying (or removing) Technician Controls it is important to first determine
those currently active. The Technician Controls Report provides options for viewing both
current and historic data, as well as defining the differences between the two. To
generate a report using the current data see Section 5.3.1. To view the differences
between current and recorded data see Section 5.3.2. The Technician controls report
selection dialog box also contains options for viewing all controls or applied controls
only.
Figure 5.1 — Technician controls report selection
Note: If the CIP is powered down with Interlocking enable and other technician’s controls
applied then the report will continue to display the applied technician’s controls but with
the Interlocking enable removed.

5.3 Technician Controls Report Selection

The following selectable criteria determine the data used to populate the report:
5.3.1 Technician Controls
This selection reports the current state of the Technician controls. Two options exist:
• Current state of technician controls
• Previous state of technician controls (when interlocking last enabled)
Figure 5.2 — Example: Technician controls report selection - Current state of technician controls
5.3.2 Differences
This selection reports upon the differences generated between the current and
previously applied technician control states.
Note: The Technicians Controls ‘Previous State’ reports are not available on the TF-R. These
reports can only be generated on the TF-L.
224
Figure 5.3 — Request Technician control report - Differences
Figure 5.4 — Example: Technician control report - Differences

Note: If Technician Controls have been applied to an interlocking that is subsequently

powered off, any report generated will show Technician Controls applied in error.
5.3.3 The Track Diagram
Applied Technician Controls will be shown in the track diagram and display as a blue box
around the signalling object concerned.
5.4 Generating a Technician Controls Report

A Technician Controls report can be generated as follows:
1. Click ‘Technician Controls’ in the Menu bar, then select ‘Reports’.
2. In the ‘Select report’ area chose the required criteria to form the report.
Refer to Section 5.3 for more information.
3. Select whether all or applied controls are required.
4. Once all required criteria has been set correctly click the ‘Request report’ button. A
new window is opened previewing the results. The report can be previewed, saved
to an external file or printed.
Note: If the TF-L is shutdown and restarted, any Technician Controls applied are displayed
without the reason entered on application and the duration is set to 01/01/0001
00:00:00.
224
5.5 To Apply and Remove Technician Controls

The following Technician Controls can be applied:
Table 5.1 — Technician Controls Available
REQUEST TYPE TECHNICIAN CONTROL

Apply Interlocking Enable
Remove Interlocking Enable

Interlocking
Apply ESOC Disconnect (See caution below)
Remove ESOC Disconnect
Apply Aspect Disconnection
Remove Aspect Disconnection

Signal
Apply Temporary Approach Control
Remove Temporary Approach Control
Apply Disable at Normal
Remove Disable at Normal

Points
Apply Disable at Reverse
Remove Disable at Reverse
Apply Route Bar

Route
Remove Route Bar
Apply Track Occupy

Track
Remove Track Occupy
Apply Latch Set

Technician's Latch
Remove Latch Set
To add or remove Technician Controls the user must be logged in with the relevant role
(see Section 3.3).
Note: Only signalling objects within the users area(s) of control are available for selection.
Note: Technician’s latches are generally defined in data and can be used for such things as
taking possession of a predefined area. If they are used then the technician will be
advised on a site by site basis as to their effect. There are always two predefined PSU
latches which should not be applied by the technician.
Note: If a data version mismatch alarm is raised on the TF-R, then you should not attempt to
issue Technician Controls from the TF-R for the indicated TF-L until this is resolved.
Note: The technician has a five minute window to perform the ESOC test, after which the ESOC
will be reconnected automatically. If the technician finishes before five minutes, then
the Remove ESOC Disconnect Command can used to reconnect ESOC without waiting for
the timeout.

Caution: When ESOC disconnect is applied, it will expire after 5 minutes and then be
reconnected automatically after 5 minutes. Therefore the technician has a five
minute window to perform the ESOC test, after which the ESOC will be reconnected
automatically.
Performing an ESOC test any later than 5 minutes after ESOC Disconnect has been
applied will cause ESOC to be applied to the CIP and therefore set signals to
restrictive states.
Caution: The user must close the Request Technician Control dialog box when leaving the TF
terminal.
After logging in but before issuing each Technician's Request, it is very important to
check which controls are currently applied. Do this by generating a Technician Controls
report (see Section 5.4).
Technician Controls may be applied or removed as follows:

1. In the Menu bar, click on 'Technician Controls'.
2. Select 'Apply or remove control'.
3. The Request Technician Control dialog box is displayed:
Figure 5.5 — Example: Request Technician Control - Select object

4. Select the type of Technician's Control (Track, Interlocking etc) by clicking on the
associated radio button in the ‘Select technician control’ left-hand section. Areas of
the dialog box not applicable to the selected method are greyed out.
224
5. Using the drop down list to the right of the selected radio button, select the required
object.
6. In the ‘Select technician control’ right-hand area click the drop down list to apply or
remove control.
Note: Only the Technician Controls that are currently applicable to an item will be displayed.
Figure 5.6 — Example: Request Technician Control - Select technician control

7. Inside the ‘Technician control application details’ area, enter a reason and the
expected duration for assuming control. Whilst this field is left blank the Issue
button is not enabled.

Note: The expected duration does not require changing from its default value and is requested
for information only; it does not affect the applied control in any way.
Figure 5.7 — Example: Request Technician Control - Technician control application details
8. To confirm the selected options click ‘Issue’ to send the request or ‘Cancel’ to close
without sending.
9. If a 'Control request confirmation' prompt box is now displayed, click inside the
‘Confirm’ field and enter the object name within 30 seconds.
Note: When typing in the object name, the full name in the correct case must be entered as
displayed in the ‘Select object’ drop down list.
Figure 5.8 — Request Technician Control - Control request confirmation prompt
224
If the command is not validated within the 30 seconds, it is timed out and the following
dialog box is displayed. Click on 'OK' to close:
Figure 5.9 — Example: Request Technician Control - Control request result cancelled
10. If a 'Technician's Request Error' dialog box is displayed, click 'OK' to abandon the
Request and close the Request dialog box.
11. If the command is validated correctly, a 'Control request result' dialog box is
displayed after a few seconds. This confirms the request has been actioned or gives
a reason for failure e.g. 'No technician control validation received from
interlocking'.
Figure 5.10 — Example: Request Technician Control - Control request result successful
Figure 5.11 — Example: Request Technician Control - Control request result unsuccessful
Note: Failure of a request can be caused by a break in communications during the period the
request is being actioned.

When removing Technician Controls the TF-L checks whether the logged in user is the
same user that applied the control. If it is a different user, a dialog box is displayed
requesting confirmation that the user wishes to proceed with the removal of the
Technician Control. The dialog box provides:
• The name of the Technician Control that has been applied.
• The name of the object that the Technician Control has been applied to.
• The identity of the user who applied the Technician Control.
• The location of the TF-L that applied the Technician Control.
• The time the Technician Control was applied.
• The expected duration of its application.
• The reason why it was applied.
If the information on the selected Technician Control is not available, a warning dialog
box is shown. This advises the user to check it is safe to remove the control. The warning
dialog box requests confirmation that the user wishes to proceed with the removal of the
Technician Control.
224
5.5.1 Track
Click the ‘Track’ radio button in the ‘Select technical control’ dialog box. Complete all
other selections as required according to Section 5.5.
Figure 5.12 — Example: Request Technician Control - Track
Upon successful application of a Technician Control, representation is given in the State

Viewer to inform the Technician of the applied control. The relevant Track icons are
marked with a red bar whilst the value of relevant attributes may change from a ‘1’ to a
‘0’ or vice versa.
Figure 5.13 — Example: Technicians Control - State Viewer (Track)

5.5.2 Interlocking
Caution: When ESOC disconnect is applied, it will expire after 5 minutes and then be
reconnected automatically after 5 minutes. Therefore the technician has a five
minute window to perform the ESOC test, after which the ESOC will be reconnected
automatically.
Performing an ESOC test any later than 5 minutes after ESOC Disconnect has been
applied will cause ESOC to be applied to the CIP and therefore set signals to
restrictive states.
Click the ‘Interlocking’ radio button in the ‘Select technician control’ dialog box. Complete
all other selections as required according to Section 5.5.
Figure 5.14 — Example: Request Technician Control - Interlocking

Viewer to inform the Technician of the applied control.
224
The relevant Interlocking attribute(s) may change from a ‘1’ to a ‘0’ or vice versa.
Figure 5.15 — Example: Technicians Control - State Viewer (Interlocking)

5.5.3 Route
Click the ‘Route’ radio button in the ‘Select technician control’ dialog box. Complete all
Figure 5.16 — Example: Request Technician Control - Route

Viewer to inform the Technician of the applied control. The relevant Route icon is marked
with a red bar whilst the value of relevant attributes may change from a ‘1’ to a ‘0’ or vice
versa.
Figure 5.17 — Example: Technicians Control - State Viewer (Route)
224
5.5.4 Points
Click the ‘Points’ radio button in the ‘Select technician control’ dialog box. Complete all
Figure 5.18 — Example: Request Technician Control - Points

Viewer to inform the Technician of the applied control. The relevant Point icon is marked
with a red bar whilst the value of relevant attributes may change from a ‘1’ to a ‘0’ or vice
versa.
Figure 5.19 — Example: Technicians Control - State Viewer (Points)

5.5.5 Signal
Click the ‘Signal’ radio button in the ‘Select technician control’ dialog box. Complete all
Figure 5.20 — Example: Request Technician Control - Signal
224

Viewer to inform the Technician of the applied control. The relevant Signal icons are
marked with a red bar whilst the value of relevant attributes may change from a ‘1’ to a
‘0’ or vice versa.
Figure 5.21 — Example: Technicians Control - State Viewer (Signal)

5.5.6 Technician’s Latch
Click the ‘Technician’s Latch’ radio button in the ‘Select technician control’ dialog box.
Complete all other selections as required according to Section 5.5.
Figure 5.22 — Example: Request Technician Control - Technician’s Latch

Viewer to inform the Technician of the applied control.
The relevant Technician’s Latch attribute(s) may change from a ‘1’ to a ‘0’ or vice versa.
Figure 5.23 — Example: Technicians Control - State Viewer (Technician’s Latch)
224
Section 6 - Alarms and Fault Diagnosis
6 Alarms and Fault Diagnosis
6.1 Introduction
Faults are notified to the Technician in the Alarms View window via an alarm entry.
Alarms have an identity number and a life cycle during which they progress through the
following states appended to the ‘Fault Description’: Cleared or Occurred.
Alarms are categorised into 'Critical', 'Non-critical' or 'None' depending upon the severity
of their effect on the signalling system. Typical faults for each category are given in Table
9.1.
The faults that can be listed, together with the likely causes, are given in Table 9.2.
Where a fault is shown as being on a WESTLOCK equipment, use of the WLE Tab on the
State Viewer (see Section 3.6.12) will provide details of the fault. Table 9.3 lists the
information available via the WLE Tab and shows the normal (no fault) condition of each
item. Table 9.4 gives recommended corrective actions for each WLE Tab fault condition.
Methods for repairing faults, replacing modules etc, are contained in the WESTLOCK First
Line Maintenance Manual M1360/MAINT.
Note: If a data version mismatch alarm is raised on the TF-R, then you should not attempt to
issue Technician Controls from the TF-R for the indicated TF-L until this is resolved.
6.2 New Alarms

The number of alarms for each category is indicated in the status bar. The red area
(critical alarms) or blue area (non-critical alarms) flashes for five seconds when a new
alarm is received. The number of alarms that require acknowledgement is indicated
within each box.
Figure 6.1 — Example: Status Bar New Alarm Indicator

6.3 Progressing of Alarms

Note: Only a user with the relevant access can progress alarms. The default user role provides
read only access. For more information refer to Section 4 - Area of Control (AoC).
Alarms are progressed from initial indication to clearance in the following order.
Acknowledgement
The Technician can acknowledge the presence of the alarm in the Alarm View. The alarm
must be acknowledged before it can be actioned.
Figure 6.2 — Example: Alarms View - alarms acknowledged
Note: If an alarm’s Fault Description is too long to be displayed, either lengthen the column
width or rollover the description to display the complete description in a tool tip (see
Figure 3.15).
Repair the Fault

First, repair Critical faults (shown in red type) as indicated in the alarm entry.
• Diagnosis of a fault down to a line replaceable unit (LRU) may be made using the
State Viewer (Section 3.6).
• User selected items or attributes from the State Viewer can be grouped together
and monitored using the Attribute Monitor window (Section 3.8). This is especially
useful for the diagnosis of intermittent faults.
• The state of trackside signalling objects can also be viewed on the Track Diagram
Mimic window (Section 3.7).
• Technician Controls may be applied or removed as required by local regulations (see
Section 4 - Area of Control (AoC)).
Once the suspect LRU is identified, LED or other indications (listed in the WESTLOCK First
Line Maintenance Manual M1360/MAINT) can be used to confirm or refine the diagnosis.
Removal and replacement procedures for WESTLOCK LRUs are given in M1360/MAINT.
Clearance
Once a fault is repaired, it will automatically progress to the 'cleared' state with the word
‘Cleared’ appended to the Fault Description column.
An alarm must be cleared to be actioned.
Acknowledgement
Once a fault has been 'cleared', the alarm must be acknowledged for a second time
before it can be actioned.
224
Actioning Faults
Once an alarm is cleared and the Technician is satisfied with its resolution, the alarm
should be actioned as described in Section 6.4. This will remove all its entries from the
Alarms View window.
Note: Display of diagnostic information from CIP/TIF may on rare occasion lock up. i.e. a fault
is reported on the TF that has been rectified. This can be corrected by shutting down the
TF application (log on as Engineer and shutdown, the application will automatically
restart).

6.4 Alarms View Window

The Alarms View (Figure 6.3) shows current (active) and new alarms, and provides a
single-line entry for each stage of the alarm process from occurred to cleared.
New alarms are initially shown in bold type.
Figure 6.3 — Example: Alarms View Window
The window is divided into the following columns:
Id
The identity number refers to the type of alarm. Alarms of the same type will have the
same identity whilst the occurrences column is incremented by 1.
Fault Description
This field details the equipment reporting the fault, followed by the fault details. The
word ‘cleared’ or ‘occurred’ is appended to the end of each entry, signifying whether the
fault has been repaired or not. The faults that can be listed, together with the likely
causes are given in Table 9.2.
Criticality
The fault criticality is shown as one of the following:
Critical (red text)

System seriously downgraded - requires immediate attention. Running of trains can
be affected.
Non-Critical (blue text)

System downgraded but continues to be fully operational due to the availability of
duplicated equipment. No effect on the running of trains.
None (black text)

System not downgraded but requires the attention of the Technician. No effect on
the running of trains.
Typical faults for each alarm category are given in Table 9.1.
Time
The date and time that the listed event took place.
Occurrences
Total number of times that a specific fault has occurred.
224
State
The State type is shown as one of the following:
Occ
Occurred. Fundamental state informing that the fault has generated an alarm.
Clr
Cleared. The condition that raised the alarm has been cleared.
Auto
The TF maintains a persistent record of alarms. On start-up it reads in this persistent
record and clears any alarms that were in the ‘Occ’ state. This automatic clearance
is shown as ‘Auto’. Any alarms which are still in effect will be re-raised.
Note: Alarms will be present on TF start-up. Use of the ‘State’ sort column within the Alarms
View window allows for quicker acknowledging and actioning of all cleared and auto
faults.
Source
Identifies the TF that generated the alarm.
The way in which information is presented can be altered by right-clicking on a column

heading. This presents a menu allowing individual columns to be hidden or shown,
alternatively there are options to ‘Show all columns’ and ‘Hide all columns’. The alarms
can also be sorted by left-clicking on the Criticality, Time, State and Source column
headers.
Right-clicking on any alarm entry in the Alarm View generates a drop-down menu,
providing a number of options for progressing the fault. Options not applicable to the
selected alarm entry are greyed-out.
Figure 6.4 — Example: Alarms View - progressing a fault
The options are as follows:
Acknowledge alarm entries

Once the Technician has an understanding of the fault, appropriate action may be taken.
First the alarm must be acknowledged.
A new alarm is acknowledged by right-clicking on the entry, then selecting

'Acknowledge alarm entries' in the resulting menu. The alarm line then reverts to normal
type.

Note: It is possible to acknowledge multiple alarms (using the CTRL or Shift key to select).
The selection can contain previously acknowledged alarms.
Action alarm(s)
Only when an alarm has been acknowledged and has a cleared state may it be actioned.
It should be used to indicate that, following repair, the fault has been dealt with
successfully. When an alarm is Actioned, all its entries are removed from the Alarm View.
Note: It is also possible to action multiple alarms (using the CTRL or Shift key to select). Only
cleared alarms maybe actioned in this way. If a block selection contains alarms that are
not in the clear state, the alarms will not be actioned.
224
6.5 Alarms Report Selection

6.5.1 Introduction
An alarm report can be generated and viewed either within the TF-L application itself, or
previewed in HTML and exported to an external file.
Figure 6.5 — Example: Alarms Report Selection dialog box
The report can be generated within a user defined time frame. It can also be filtered by
equipment or alarm type. Filtering by equipment type displays faults applicable only to
specific signalling objects or sub-systems. Filtering by alarm type allows the report to be
generated from a list of alarm entries. The report can be tailored further to show active
alarms only or current alarms including the alarms history.
6.5.2 Generating a Report
To generate a report proceed as follows:

1. Click ‘Reports’ on the Menu bar and select ‘Alarm report’.
2. To apply a date and time filter, using the ‘Select time range’ area tick the ‘From’ and
‘To’ check boxes. Each attribute (date, month, year, hours, minutes and seconds)
becomes editable using either the keyboard for numeric input or by clicking the up/
down arrows.
3. Using the ‘Select filter type’ area, select either ‘Filter by equipment type’ (see Section
6.5.3) or ‘Filter by alarm type’ (see Section 6.5.4).
4. Using the ‘Select alarms’ area, select either ‘Show all current alarms’ or ‘Show active
alarms only’.

5. Click the ‘Show Report’ button to view and save the results.
Note: When saving results the user is presented with a save dialog box. Only locations under
‘G:\reports’ (TF-L) and ‘E:\reports’ (TF-R) should be selected. Whilst using the save dialog
the user should not perform any action other than specifying a filename and folder
under this location.
Note: Saving to removable drives can fail if the USB drive has been allocated the wrong drive
letter by the Operating System. In this case a new USB drive will need to be used.
6.5.3 Filtering by equipment type
Selecting ‘Filter by equipment type’ generates a report based on equipment added by the
user. Items are managed in a similar fashion to those monitored in the Attribute/States
Window.
Figure 6.6 — Example: Alarms Report Selection - Filter by equipment type
6.5.3.1 Adding Items
To add items or attributes:

1. In the ‘Available equipment types’ area open the list containing the required item.
4. Drag and drop the item or attribute into the ‘Selected equipment types’ area.
To add more items or attributes repeat the above process as necessary.
224
Right-clicking an item or attribute in the ‘Available equipment types’ area generates a

drop-down menu providing options to ‘Select equipment type’ or ‘Select equipment’
respectively.
Right-clicking multiple attributes generates a drop-down menu providing options to

‘Select equipment type’ or ‘Select all similar equipment’.
To remove an item from the window, first select it then right-click and select ‘Remove’ or
‘Remove All’.
6.5.4 Filtering by alarm type
Selecting ‘Filter by alarm type’ generates a report based on alarm entries added by the
user.
Figure 6.7 — Example: Alarms Report Selection - Filter by alarm type
6.5.4.1 Adding Items
To add alarm entries tick the ‘Alarm No.’ check box. Selected entries are added to the
‘Selected alarm types’ area. Alternatively, all entries can be added in one click by ticking
the ‘Select all’ check box.
To remove an entry from the ‘Selected alarm types’ area un-tick the check box.

6.5.5 Viewing the Report
Clicking the ‘Show Report’ button generates the report with the selected criteria. The
results open in a new window.
The Report window may be re-sized (see Section 1.5) to view the displayed items.
The way in which information is presented can be altered by left-clicking on a column

heading. Column order can be changed by left-clicking and dragging and dropping the
column header to its required location.
Figure 6.8 — Example: Alarm Report results
224
Section 7 - Logging
7 Logging
7.1 Introduction
The Technicians Facility is fitted with a Fixed Logging Drive and two Removable Logging
Drives:
• The term ‘Fixed Logging Drive’ refers to the PC hard disk.
• The term ‘Removable Logging Drive’ refers to either of the two removable SATA
drives that attach via USB.
Caution: The Removable Logging Drive should only be removed under judicial arrest. Upon no
other circumstance is the Drive required to be removed.
Analysis of recorded data is carried out using the reporting functionality built into
the TF-L (see Section 7.4 - Viewing Logs).
Mounting and dismounting of the Logging Drives MUST be performed via the TF-L
menu. Failure to use the correct procedure for mounting and dismounting may
cause an incorrect alarm and J-Log status to be reported - in particular the disk may
be shown as mounted when it is in fact absent.
The TF will raise an alarm if a Logging Drive is removed.
Logged data is written to the Fixed and Removable Logging Drives. Logging of status and
fault messages is a background task that is transparent to the user. Only if logging fails,
or if data is to be removed for analysis, will the user become involved.
The logging process includes two levels of monitoring:
Disk availability
The availability of the disk storage used for logging is monitored. If a disk becomes
unavailable logging to that disk will cease. An alarm will be raised and there will be a
limited (configurable) buffering of log entries. If the disk becomes available logging will
continue. The logging buffers are also used to manage log files that are currently being
accessed. Log data is not buffered whilst the storage is in a failed state.
Disk usage
Log files are stored in an un-compressed format and stored for a minimum of 31 days.
Log files are removed as the disk becomes full (90%).
Note: The Event Replay application allows log files to be accessed and replayed. For more
information see Section 8 — Event Replay Facility.

Section 7 - Logging
7.2 Dismounting a Logging Drive

The Removable Logging Drives are identified in the TF-L as Drives E and F.
To remove a logging drive:

1. Click ‘J-Log mount/dismount’ from the Menu bar.
2. Select ‘J-Log 1 (drive E:)’ or ‘J-Log 2 (drive F:)’.
3. Select ‘Dismount’ for the selected drive. The selected drive is now ready to be
physically removed.
Caution: Do not attempt to remove the Logging Drive without following the above procedure,
as this may result in corruption of the log file.
Note: The TF will raise a ‘non-critical’ alarm if a Logging Drive is removed and a ‘critical’ alarm
if both are removed.
7.3 Mounting a Logging Drive
Caution: Always use logging disks labelled as 'E' in the 'E' drive position, and logging disks
labelled as 'F' in the 'F' drive position.
Inserting a logging disk in the incorrect drive will cause problems in the log swap
operation as the logging disk will not correspond to the drive letter stated on the
TF-L display.
If a logging disk is inadvertently inserted into the wrong drive position, it should be
removed, and replaced with the correctly labelled logging disk.
The Removable Logging Drives are identified in the TF-L as Drives E and F.
To insert a logging drive:

1. Click ‘J-Log mount/dismount’ from the Menu bar.
2. Select ‘J-Log 1 (drive E:)’ or ‘J-Log 2 (drive F:)’.
3. Select ‘Mount’ for the selected drive. The selected drive is now ready to be physically
installed.
Caution: A Logging Drive may be erroneously reported as mounted when not physically
present. It is therefore essential that a replacement is mounted using the method
above. Once replaced, the user should check the Alarms View Window to see that the
non-critical alarm has cleared.
If the drive fails to be recognised after following the correct procedure, the TF-L
should be shut down (see Section 3.2.3) and the power reset. Restarting the
application alone will not work. The user should check the State Viewer TF tab that
the appropriate drive is shown as mounted and logging.
224
Section 7 - Logging
7.4 Viewing Logs

7.4.1 Introduction
The TF-L continually records log file data that the user can view, save or print. Several
different log types exist:
Interlocking Log
Reports on the current state of the interlocking.
Interlocking Event Log

Reports on interlocking events historically.
Signalling Model Log

Reports on the state of the Signalling.
Alarms Log
Reports on faults generated. Provides extra fields to that provided in the Alarms
Report.
Technician Controls Log

Reports on Technician Controls and is filtered using the Attribute filter.
Access Control Log

Reports on user access data, e.g. users logging in and out.
The TF-L also includes an ‘Export’ option in the Menu Bar. From here the user can view,
save or print similar information which is described in more detail later in this chapter
(see Section 7.5).

Section 7 - Logging
Figure 7.1 — Example: Log Report - Data selection criteria
To generate a log report, the user must select at least one log type and one Site ID. The
Site ID refers to the interlocking area. Further items can be added to the report by
dragging into the ‘Selected equipment items’ area. Items are added from a choice of 3
filters, explained further in Section 7.4.2.2.
224
Section 7 - Logging
7.4.2 Generating A Report

1. Click ‘Reports’ on the Menu bar and select ‘Log report’.
2. Adjust the ‘From’ and ‘To’ fields in the ‘Date range’ area. Each attribute (date, month,
year, hours, minutes and seconds) becomes editable using either the keyboard for
numeric input or by clicking the up/down arrows.
3. Select at least one Log type.
4. Select at least one Site ID.
5. Select and add equipment items as required.
Figure 7.2 — Example: Log Report dialog box

Section 7 - Logging
7.4.2.1 Adding Optional Items
First select the required filter as per Section 7.4.2.2. To add items or attributes:
1. In the ‘Available equipment items’ area open the list containing the required item.
4. Drag and drop the item or attribute to the right into the ‘Selected’ area.
To add more items or attributes repeat the above process as necessary.
Items and attributes can also be selected by right-clicking and selecting the appropriate
option from the drop-down menu provided.
7.4.2.2 Filtering Items
When adding optional items as in Section 7.4.2.1, the user may filter the available items
that construct the report. Three types of filter are available via the ‘Attribute filter’,
‘Interlocking filter’ and ‘Alarm filter’ tabs:
Attribute filter
Displays the following list of optional items:
DataVersion - Trackside data version
Link - Displays the Links to the interlocking and other
equipment
AreaOfControlGroup - Displays the selected AoC
DataLog - Displays data on J-Log 1 & 2 and W-Log
Interlocking - Displays interlocking data
Signal - Displays Signalling data
Track - Displays Track data
Points - Displays Point data
Route - Displays Route data
Sub Route - Displays Sub Route data
Sub Overlap - Displays Sub Overlap data
Latch - Displays Latch data
Technicians Latch - Displays Technicians Latch data
Unexpected Telegram - Displays Unexpected Telegram data
TFMPSU - Displays Power Supply Unit data
224
Section 7 - Logging
Figure 7.3 — Example: Log Report dialog box - Attribute filter tab

Section 7 - Logging
Interlocking filter
Displays interlocking items. Filter can applied alphabetically or categorised. To toggle
click the icon below ‘All states’.
Figure 7.4 — Example: Interlocking filter - ‘All states’ filtered alphabetically
224
Section 7 - Logging
Figure 7.5 — Example: Interlocking filter - ‘All states’ filtered categorised

Section 7 - Logging
Alarm filter
Enables the user to filter by alarm or equipment type.
Figure 7.6 — Example: Alarm filter - Filter by alarm type
224
Section 7 - Logging
Figure 7.7 — Example: Alarm filter - Filter by equipment type

Section 7 - Logging
7.4.3 Viewing The Report
Once all required criteria has been set correctly click the ‘Show Report’ button to view the
report. A new window is opened previewing the results. The report may be saved (to the
pre-configured paths ‘G:\reports’ (TF-L) or ‘E:\reports’ (TF-R)) or printed. The user can only
save to a file at these pre-configured paths.
Figure 7.8 — Example: Interlocking Log Report Results dialog box
The report lists the following fields of information: Time Stamp, Entry Type, Interface
Name, Item Name, Item Value, Equipment Type, Equipment Name, Alarm No., Alarm
Desc., Alarm Action, Alarm Occ., User Name, User Role and User Action.
Only those fields with applicable information are populated.
Note: The Report window is capable of displaying a maximum of 10,000 entries. It may be
necessary to adjust the date range, log type and filter criteria in order to view the
required results.
224
Section 7 - Logging
7.4.4 Types Of Report
The TF-L is capable of producing the following log reports:
7.4.4.1 Interlocking Log
Provides current data on the interlocking including software features used for testing
and analysis.
Default fields provided in report: Time Stamp, Interface Name, Item Name, Item Value
and Entry Type.
Figure 7.9 — Example: Interlocking Log Report dialog box
Note: Reports can be generated from multiple log sources. The columns in the report will be a
combination of the columns in the log sources and therefore will differ from the above
example.

Section 7 - Logging
7.4.4.2 Interlocking Event Log
Provides historical data on the interlocking including software features used for testing
and analysis.
Default fields provided in report: Time Stamp, Entry Type, Interface Name, Item Name
and Item Value.
Figure 7.10 — Example: Interlocking Event Log Report dialog box
example.
224
Section 7 - Logging
7.4.4.3 Signalling Model Log
Provides data on the Signalling including software features used for testing and analysis.
Default fields provided in report: Time Stamp, Interface Name, Item Name, Item Value
and Entry Type.
Figure 7.11 — Example: Signalling Model Log Report dialog box
example.

Section 7 - Logging
7.4.4.4 Alarms Log
Default fields provided in report: Time Stamp, Interface Name, Equipment Type,
Equipment Name, Alarm No., Alarm Desc., Alarm Action, Alarm Occ., User Name, User
Role and Entry Type.
Note that the User Name and User Role provide the name and role of the user that
acknowledged and/or actioned the alarm(s).
Figure 7.12 — Example: Alarms Log Report dialog box
example.
224
Section 7 - Logging
7.4.4.5 Technician Controls Log
The Technician Controls Log includes (but is not limited to) data on the type, duration
and purpose of Technician Controls.
Default fields provided in report: Time Stamp, Interface Name, Equipment Type,
Equipment Name, Control Type, Control Value, Control Action, Control Purpose, Control
Duration, User Name, User Role and Entry Type.
Figure 7.13 — Example: Technician Controls Log Report dialog box
example.
Note: This log contains a field labelled 'Control Duration' with values relating to the end date
for the applied controls. A value of '01/01/0001:00:00' relates to controls which are no
longer applied.

Section 7 - Logging
7.4.4.6 Access Control Log
Default fields provided in report: Time Stamp, User Name, User Role and Operation Type.
Figure 7.14 — Example: Access Control Log Report dialog box
example.
224
Section 7 - Logging
7.5 Export
7.5.1 Introduction
The TF-L includes an Export menu, allowing the user to quickly save, view or print logged
data. The following options for export include:
Export all interlocking states

This option exports the current values of all states received from the interlocking.
Fields provided in export: Mnemonic, State, Source and Direction.
Export all interlocking changes

This option exports historical interlocking changes.
Fields provided in export: Timestamp, Mnemonic, State, Source and Direction.
Export selected interlocking changes

This option exports historical changes of the currently monitored interlocking
items.
Fields provided in export: Timestamp, Mnemonic, State, Source and Direction.
Export all attribute states

This option exports the current values of all attributes.
Fields provided in export: Attribute and State.
Export all attribute changes

This option exports historical attribute changes.
Fields provided in export: Timestamp, Attribute and State.
Export selected attribute changes

This option exports historical changes of those attributes being monitored.
Fields provided in export: Timestamp, Attribute and State.
Export control status

This option launches the Technician Controls Report Selection dialog box. Refer to
Section 5.3 for more information.
7.5.2 Creating Data To Export
To export data:
1. Click ‘Export’ on the Menu Bar.
2. Select the required option to export.

Section 7 - Logging
7.5.3 Viewing Exported Data
Figure 7.15 — Export All interlocking states dialog box
Once the required menu option has been selected, the user is presented with the dialog
box shown above. Available options include Save, Print, Preview or Close. The report may
be saved (to the pre-configured paths ‘G:\reports’ (TF-L) or ‘E:\reports’ (TF-R)) or printed.
The user can only save to a file at this pre-configured path.
224
Section 7 - Logging
Figure 7.16 — Example: Export All interlocking states - Preview
7.5.4 Selecting Data To Export
With the Preview window open as per Figure 7.16, the user can chose to export ‘All’ data
or a ‘Selection’ in the ‘Save or print report data’ area. Selecting ‘All’ will export the full
report whilst ‘Selection’ allows the user to select single or multiple entries both
consecutively and non consecutively. This functionality is useful for selecting items out
of the ‘Export all Interlocking changes’ and ‘Export all attribute changes’ report.
To select a single entry left-click as required.
To select consecutive entries left-click on the first entry, hold the ‘shift’ key then left-click
on the last entry.
To select non consecutive entries left-click on the first, hold the ‘CTRL’ key then left-click
additional entries as required.

Section 7 - Logging
224
Section 8 - Event Replay Facility
8 Event Replay Facility
8.1 Introduction
The Event Replay Facility (ERF) can be accessed via either the TF-R or the Stand Alone
Event Replay Graphical application (SERFG).
It is intended that the ERF on the TF-R should be used for general investigation, where
offline analysis is required the SERFG should be used. The SERFG requires data from the
removable Logging Drives.
Note: Prior to accessing the Event Replay Facility on the TF-R, the user must have logged on as
an ‘Investigator’.
Caution: Mounting and dismounting of the Logging Drives on the TF-L MUST be performed via
the TF-L menu. Failure to use the correct procedure for mounting and dismounting
may cause an incorrect alarm and J-Log status to be reported - in particular the disk
may be shown as mounted when it is in fact absent.
The TF will raise an alarm if a Logging Drive is removed.
The Technician's Facility continuously writes log files to record the current state of the
railway. Log files are written to the (Fixed and) Removable Logging Drives (see Section
7.1) - one of which may be arrested in the event of an investigation. Replaying logged
events to create past scenarios is valuable for investigation purposes. The duration of a
log file is restricted to a maximum of 24 hours.
The Event Replay Facility displays replayed events in the same way that live SoR events
are displayed by the TF. The Track Diagram can be used to see the passages of trains,
track occupancy etc. (refer to Section 3.7). The State Viewer can also be used for the
same purpose (refer to Section 3.6). Items can be dragged from the State Viewer into the
attribute monitor and monitored (refer to Section 3.8). Live alarms are still reported in
the alarms window (TF-R only) (refer to Section 6). Alarms raised during the replay
window are shown in the ‘Replayed Events’ window (refer to Section 8.3.7).
Note: The TF-R can take considerable time to load and prepare data for replay. During this
time the TF-R cannot be used for any other operation.
The Event Replay application allows log files to be accessed and replayed. The Technician
is able to define the criteria of historical events to replay. Using the Replay Control the
Technician is able to:
• Display events that are being replayed or are due to be replayed.
• Search for a particular event - either by time or content and play that event.
• Save extracted events as a single file to disk.

The Technician is able to select data from the J-Log or from a previously saved set of
logged events. Log data can be selected from single or multiple log types, i.e.
interlocking and alarms. The selection criteria can be based upon the following
parameters:
• Date and time range.
• Mnemonic name.
• Attribute name.
• Alarm type.
• Equipment type.
• Equipment instance.
The Technician is provided with standard replay options such as Start, Stop, Pause,
Resume, Single Step Forward, Single Step Backward, Repeat, Speed Control and Go To.
224
8.2 Applicability
Refer to Section 1.3.
8.3 Operation
To access logged data via the SERFG, insert the Removable Logging Drive containing the
data, if not already inserted. The TF-R accesses data from the W-Log via the control
network.
8.3.1 Opening the SERFG
The SERFG application is provided as part of the WESTLOCK SitePC, and is started from a
menu option, refer to the WESTLOCK Data Preparation Process Manual -
X1360-6-MN-00052. The following screen is displayed:
Figure 8.1 — Event Replay initial screen
From the Menu bar select ‘Replay’. A dialog box is shown as per Figure 8.2.
8.3.2 Opening the ERF
Note: The ERF is available from the TF-R.
Selectable from the Pane Toolbar (see Section 3.4), click the ‘Events to Replay’ Window
tab.
From the Menu bar select ‘Replay’. A dialog box is shown as per Figure 8.2.

8.3.3 Selecting A Data Source
8.3.3.1 SERFG
Select the required data source by clicking the corresponding radio button.
Note: If accessing the Event Replay Facility via the SERFG, only the J-Log and Extracted Events
radio buttons will be selectable.
Figure 8.2 — Example: Replay Source Selection
If this is the first time the application has been run, the white box in the centre of the
dialog box will be empty as shown in the figure above. If the application has been run
previously, the user may select from a list of existing logs. Once a file is selected the
‘Remove’ button is enabled, allowing the user to remove files from the selected list.
If ‘J-Log’ or ‘Extracted Events’ is selected the ‘Browse’ button is enabled. This allows the
user to select the required log file from a configured location. Click ‘Browse’ to select a
log file:
Figure 8.3 — Example: Select Log File(s) dialog box
To select an individual log left-click the required file then click ‘Open’. To select multiple
logs, left-click the first file, hold down the CTRL key and left-click the next required file.
Once completed click ‘Open’.
224
8.3.3.2 ERF
Select the required data source by clicking the corresponding radio button.
Note: If accessing the Event Replay Facility via the TF-R, only the W-Log and Extracted Events
radio buttons will be selectable.
Figure 8.4 — Example: Replay Source Selection
If this is the first time the application has been run, the white box in the centre of the
dialog box will be empty as shown in the figure above.
If ‘Extracted Events’ is selected the ‘Browse’ button is enabled. This allows the user to
select the required log file from a configured location. Click ‘Browse’ to select a log file:
Figure 8.5 — Example: Select Log File(s) dialog box
To select an individual log left-click the required file then click ‘Open’. To select multiple
logs, left-click the first file, hold down the CTRL key and left-click the next required file.
Once completed click ‘Open’.

If there is an error associated with any of the selected file(s), a warning message is
displayed. Errors may occur because the log file is corrupted, has an invalid header or is
empty.
Figure 8.6 — Example: Corrupted file
Figure 8.7 — Example: Invalid Header
Figure 8.8 — Empty file
The user will not be able to proceed until the erroneous file is removed from the selected
list. If there is no error in the data source selection, click ‘OK’.
8.3.4 Defining Selection Criteria
Upon successful selection of a log file, a dialog box opens allowing the user to define the
required criteria to be filtered from the log. The user is required to:
1. Select the required date range.
2. Select at least one ‘Log type’
3. Apply filters as required. The Attribute, Interlocking and Alarm filters are all
optional. The user may provide criteria for one or more filters or alternatively leave
them empty to fetch the entire set of events.
Note: If accessing the Event Replay Facility via the SERFG, the tick boxes within the ‘Log types’
window will be automatically populated, depending on the type of log file that has been
opened. If accessing via the TF-R the tick boxes will require manual selection.
Note: The maximum number of log entries that can be replayed is 50,000. It may be necessary
to adjust the date range, log type and filter criteria in order to view the required events.
Note: The TF-R State Viewer and Track Diagram Mimic will only display information on replay
if all five separate logs have been selected. If any of the five separate logs are not
selected then information will not be presented on replay.
224
Figure 8.9 — Example: Data Selection Criteria dialog box
For an explanation of the filters, refer to Section 7.4.2.2.

To apply the filters (add optional items) refer to Section 7.4.2.1.
Once all selection criteria have been made, click the ‘OK’ button. If no errors are
encountered, the Events To Replay window is used to display the fetched log entries.

Note: If the data installed on the Event Replay PC is different from that on the TF-L, the
following error message is displayed:
Figure 8.10 — Data Selection Criteria Data Error
Clicking ‘OK’ will allow the log to be replayed, but this might compromise the replayed
data. The user should select ‘Cancel’ and reload the compatible data.
If the selected log file contains multiple GeoData versions e.g. as a result of a data update
or re-installation, a warning message is displayed.
Figure 8.11 — Data Selection Criteria Data Error (Multiple GeoData versions)
Clicking ‘OK’ will open the ‘Data selection criteria’ window, refer to Figure 8.9. A time
range can now be entered that has a single GeoData version.
224
8.3.5 Events To Replay Window
The Events To Replay window is used to display events fetched from the log files as per
the user defined selection criteria (see Section 8.3.4). This window provides controls for
replay functions (pause, play, stop etc.) and a search and save facility to refine the
fetched results.
Figure 8.12 — Example: Events To Replay window
The example above displays unfiltered Interlocking, Signalling Model, Alarms and Access
Control Logs. Some entries are expanded [-] and some collapsed [+]. As logs are created
there may be multiple events with the same timestamp. The Event Replay is configured
such that if there are five or less events with the same timestamp, by default they are
shown as expanded. If there are six or more events with the same timestamp, they are
shown collapsed. By left-clicking on the [+] the full list of events for that timestamp can
be displayed.

8.3.5.1 Expand All
Click the ‘Expand All’ button to view all the events in expanded format.
Figure 8.13 — Example: Events To Replay - Expand All
8.3.6 Collapse All
Click the ‘Collapse All’ button to view all the events in collapsed format.
Figure 8.14 — Example: Events To Replay - Collapse All
8.3.6.1 Search
The Search button opens a dialog box that allows the fetched log events to be refined.
The selection criteria can be based upon one of the following: Time Stamp, Mnemonic
Name, Attribute Name, Alarm, Equipment Type and Equipment Instance.
Search criteria is displayed based on the contents of the available fetched log events.
224
Time Stamp
Select the ‘Time Stamp’ radio button to search the events based on the ‘From’ and ‘To’
range.
Note: Once selected, the time for replay cannot be changed. To change the search criteria a
new search must be initiated.
Figure 8.15 — Example: Replay Event Search - Time Stamp
Mnemonic Name
Select the ‘Mnemonic Name’ radio button to search the events by the monitor states
listed. Items are listed in the ‘All states’ area and dragged left to right into the ‘Selected
states’ area. Alternatively, right-clicking the item will provide similar options for adding.
Figure 8.16 — Example: Replay Event Search - Mnemonic Name
If items have been incorrectly added to the ‘Selected states’ area, they can be removed
by right-clicking and selecting the correct option. Options include ‘remove item’ and
‘remove all items’.

Attribute Name
Select the ‘Attribute Name’ radio button to search the events by selecting available
equipment items. Items are listed in the ‘Available equipment items’ area and dragged
left to right into the ‘Selected equipment items’ area. Alternatively, right-clicking the
item will provide similar options for adding.
Figure 8.17 — Example: Replay Event Search - Attribute Name
If items have been incorrectly added to the ‘Selected states’ area, they can be removed
by right-clicking and selecting the correct option. Options include ‘remove item’ and
‘remove all items’.
Alarm
Select the ‘Alarm’ radio button to search the events by the available alarms. Tick the
required check box to select or alternatively use the ‘Select All’ check box.
Figure 8.18 — Example: Replay Event Search - Alarm
224
Equipment Type
Select the ‘Equipment Type’ radio button to search the events by the available equipment
type. Items are listed in the ‘Available equipment types’ area and are added/removed
from the ‘Selected equipment types’ area by clicking the corresponding buttons.
Selecting any one of the items listed will add all of the items in that category e.g.
selecting ‘Signal’ will add all signals in the interlocking area.
Click to add items and to remove.
Figure 8.19 — Replay Event Search - Equipment Type
Equipment Instance
Select the ‘Equipment Instance’ radio button to search the events by the available
equipment instances. This search is similar to Equipment Type except it allows individual
items to be selected (e.g. one signal as opposed to all). Items are listed in the ‘Available
equipment instances’ area and dragged left to right into the ‘Selected equipment
instances’ area. Alternatively, right-clicking the item will provide similar options for
adding.
Figure 8.20 — Example: Replay Event Search - Equipment Instance

To select multiple items, left-click on the first then hold the CTRL key and left-click further
items as required. To add items right-click or drag left to right as previously described.
8.3.6.2 Viewing Matched Events
Once the required criteria have been set, click ‘OK’ to continue. The matching events are
highlighted in Events To Replay window.
Figure 8.21 — Example: Events To Replay - highlighted matching events
Clicking the ‘Previous’ or ‘Next’ buttons will navigate consecutively through the
highlighted search items.
The ‘Clear Search’ button will clear the highlighted search items.
224
8.3.6.3 Save
The fetched log events may be saved to a file inside one of the configured folders or its
subdirectories. Click the ‘Save’ button to open the dialog box below. The user is required
to enter a filename and click ‘Save’.
Figure 8.22 — Example: Save Extracted Events
If the file is successfully saved the following prompt is displayed:
Figure 8.23 — Save Extracted Events - successful

8.3.6.4 Replay Control Panel
Play Go To Single Step Stop

Backward
Replay Pause Single Step Repeat Speed

Timer Forward
Figure 8.24 — Replay Control Panel
The Replay Control Panel provides the user with the following playback options:
Play
The Play button starts the replay. The first event is replayed immediately while the
subsequent events are replayed as per their timestamp at the currently selected speed.
Once the Play button is clicked, the Pause button is enabled and the Play, Single Step
Forward, Single Step Backward and Go To buttons are disabled.
Figure 8.25 — Replay Control Panel - Play mode
Pause
The Pause button pauses the ongoing replay. Once pressed, the Play, Single Step and Go
To buttons are enabled.
Single Step Forward and Backward
The Single Step buttons replay events one at a time. Once paused, the application will
replay the next or previous event from where it was paused. Events are continued to be
played as the user repeatedly clicks the Single Step button.
Note: The ‘Single Step Backward’ button will only step backward in single events. If larger
backward steps are required the ‘Go To’ facility must be used.
224
Repeat
The Repeat check box is used to repeat log events. Once ticked, when the end of the log
events are reached the replay restarts from the first event.
Figure 8.26 — Replay Control Panel - Repeat check box selected
Speed
The Speed drop down list is used to alter the replay speed.
Figure 8.27 — Replay Control Panel - Speed of replay

Go To
The Go To button is used to replay a specific event. Once clicked, the ‘Replay Event
Search’ dialog box (Section 8.3.4) is displayed allowing the user to provide the criteria to
locate the specific event. Once the search criteria is confirmed, all the events from the
start of the log to (and including) the matching event are replayed. If there is more than
one matching event, the replay occurs up to the first matching event only.
The Go To command may also be used by right-clicking on an entry in the Events To

Replay window. The event will be highlighted in green (indicating the current replay
event).
Figure 8.28 — Events To Replay - Go To
Stop
The stop button is used to exit the replay mode. When clicked, the Replay Control Panel
will close and the Events To Replay and Replayed Events windows will be cleared. To
restart the replay application, click ‘Event Replay’ from the Menu bar and select ‘Replay’.
224
8.3.6.5 Starting The Replay
To inform the user, the current replayed event is highlighted in green in the Events To
Replay window.
Note: Live alarms will continue to be displayed whilst in replay mode and should be
considered current and not historical.
Figure 8.29 — Example: Events To Replay - current replayed event highlighted

8.3.7 Replayed Events window
The Replayed Events tab displays events that have already been replayed. There is no
user control available.
Note: The ‘Replayed Events’ window will not be populated with all events replayed. Only the
Alarm, Technician Control and Access Control logs will be displayed in the window. All
other attributes and mnemonic states are replayed on the Track Diagram Mimic or State
Viewer tabs and therefore will not appear in the ‘Replayed Events’ window.
Figure 8.30 — Example: Replayed Events window
224
Section 9 - Reference Information
9 Reference Information
9.1 Alarm Categories

Alarms are categorised according to the severity of their effect on the signalling system,
as follows:
Critical
System seriously downgraded - requires immediate attention. Running of trains can be
affected. The Technician and Signaller are both notified.
Non Critical
System downgraded, but continues to be fully operational due to availability of
duplicated equipment. No effect on the running of trains. The Technician and Signaller
are both notified.
None
System not downgraded but requires the attention of the Technician, e.g. filament
failure. No effect on the running of trains. Only the Technician is notified.
Table 9.1 — Typical Faults for each Category
NON-
CRITICA
AREA FAULT REPORTED CRITICA NONE
L
L
Main filament of aspect failed. X
Searchlight signal aspect proving failed. X
Lamp of aspect failed. X
Points detection in a particular direction failed. X

SSI Trackside
Equipment Points failed to move in the requested direction
X
and still detected in opposite direction.
Points contactor failed in particular direction. X
Lamp of route indicator failed. X
Main filament of route indicator failed. X
Points Module motor fault. X
Signal Module input and output interface fault. X
Points Module input and output interface fault. X
Outward link fault for a TFM (link A or B). X

SSI TFM and Trackside Outward link fault for all TFMs in a location case
Data Link X
(link A or B).
Outward link fault for all TFMs at or beyond a

X
location case (link A or B).
No reply from a TFM on one data link (links A or B). X
No reply from a TFM on both data links. X

Table 9.1 — Typical Faults for each Category (Continued)
NON-
CRITICA
L
L
No reply from all TFMs in a location case on one

X
data link (links A or B).
No reply from all TFMs in a location case on both

X
data links (links A and B).
SSI TFM and Trackside
No reply from all TFMs at and beyond a location
Data Link X
case on one data link (links A or B).
(continued)
No reply from all TFMs at and beyond a location
X
case on both data link (links A and B).
No reply from all TFMs connected to a particular

X
power supply.
Message loss from one SSI on one data link. X
Message loss from one SSI on both data links. X

SSI Internal Data Link
Message loss from all SSIs on one data link. X
Message loss from all SSIs on both data links. X
MP Assembly in dual mode. X
MP Assembly in single mode. X
Logic power supply 1 or 2 failed on MPs. X
Unknown fault on left, middle or right MP. X
Left, middle or right MP not installed. X
Left, middle or right MP not locked. X
Battery failed on left, middle or right MP. X

Main Processor
Assembly TriStation port active on left, middle or right MP.
This may indicate that someone is trying to alter X
the application with the WESTLOCK Controller.
Left, middle or right MP hot (above 74 ºC). X
Left, middle or right MP out of temperature range. X
Programmable alarm (function determined by the

X
application).
Scan over-run occurred. X
Scan time close to limit. X
224
NON-
CRITICA
L
L
Logic power supply 1 or 2 failed on left and/or right

X
CM.
Unknown fault on left or right CM. X
Left or right CM not installed. X

Communications
Module Left or right CM not locked. X
Net 1 not receiving messages on left or right CM. X
Net 2 not receiving messages on left or right CM. X
Left or right CM out of temperature range. X
DI assembly in dual mode. X
DI assembly in single mode. X

X
DI.
Unknown fault on left or right DI. X
Left or right DI not installed. X

Direct Input Module Left or right DI not locked. X
Field power supply 1 or 2 failed on left and/or right

X
DI.
Field power supply 1 and 2 failed on left and/or

X
right DI.
Field fault on active left or right DI. X
Voter fault on left or right DI. X
SCM assembly in dual mode. X
SCM assembly in single mode. X

X
SCM.
Unknown fault on left or right SCM. X
SSI Communications Left or right SCM not installed. X

Module
Left or right SCM not locked. X
Field power supply 1 or 2 failed on left and/or right

X
SCM.
Field power supply 1 and 2 failed on left and/or

X
right SCM.
Field fault on active left or right SCM. X
Voter fault on left or right SCM. X

NON-
CRITICA
L
L
Communications path between nodes X and Y

X
non-redundant.
Communications path between nodes X and Y

X
Signalling Network non-existent.
communication faults
First missed message from TIF. X
First missed message from adjacent CIP. X
Multiple missed message from adjacent CIP. X
Communications path between nodes TW(L) and

X
CIP non-redundant.

X
CIP non-existent.

Control Network X
CSG non-redundant.
communication faults
(see note) Communications path between nodes TW(L) and
X
CSG non-existent.
Communications path between nodes CSG and CIP

X
non-redundant.
Communications path between nodes CSG and CIP

X
non-existent.
Invalid data received from WESTLOCK component. X

TF-L
Logger fault. X
Link Failure Total. X

TF-S/TF-L/TF-R
Link Failure Partial. X
Communications
Channel Failure. X
Installation Version File Failed Audit Check. X

and Audit Handling Installation modified since previous audit check. X
PM Failure. X
Addressing/Address Error. X
FEP Alarms Module Negated. X
Configuration Error. X
24 V supply failure - Link A/B. X
Output interface disabled. X
FEP Alarms (SOM 110 Red retain enforcement test. X

Object Controllers) Supply voltage. X
Output current. X
224
NON-
CRITICA
L
L
FEP Alarms (LOM 110 Signalling Supply. X

Object Controllers) Output current. X
ESOC Operation. X
ESOC Alarms
ESOC High/Low Input failure. X
NTP Server Connection Failed. X
NTP Free Running. X

Time Synchronisation
No Time Reference available. X
Signification Time Jump. X
No Reply From Remote SMB/Housing/Location

X
single link.
No Reply from Remote SMB/Housing/location both

X
links.
FEP Transmission No Reply From and Beyond FEP/Remote SMB/

X
status Location single link.
No Reply From and Beyond FEP/Remote SMB/

X
Location both links.
Module link failure. X
Module Failure. X
CSG total failure. X
CSG Link to IECC total failure. X
Control System CSG Link to Train describer A/B total failure. X

Gateway CSG Link to PMUX Input/output cards total failure. X
CSG Input scanner total failure. X
CSG Link to PMUX total failure. X
Note: When CSG is not present, CSG alarms do not apply to CSG equipment, but to equipment
connected to CIP via CADLOCK protocol.
Note: If status information for a set of points is split across multiple IOMs and one of these
IOMs is removed then this can result in spurious alarms being reported.

9.2 Fault List Entries

9.2.1 Text Line Format
The descriptive text lines under the 'Fault Description' heading in the Faults List (see
Section 6.4 and Figure 6.3) are made up of fields into which the TF enters variable
information, and of preset text for fixed information.
For example, the fault message below is made up of the following segments:
The <TDLName> is the field, which in this case contains 'LSpa TIF'. On a different system
it could contain 'Rugby TIF' or 'Euston TIF' etc.
Another message may be:
Table 9.2 lists the text lines showing the fields, together with the likely causes of the fault
message. For actions to repair the fault, refer to the WESTLOCK First Line Maintenance
Manual M1360/MAINT.
A single fault affecting several items of equipment may result in separate fault reports
from those equipment. When diagnosing a fault, look for groups of fault reports from the
same area, then look for a common factor as the possible cause.
Table 9.2 has fault messages laid out in the following order:
1. Trackside Functional Modules and Trackside Data Links.
2. Trackside Equipment.
3. Direct Inputs.
4. Communication networks.
5. WESTLOCK Controller.
6. Control System Gateway.
224
9.2.2 Fields Used in Text Lines
<File> - File name of A file installed as part of the TF installation.
<CRC> - A Calculated or expected CRC value used by the installation auditing process.
<LinkId> - Identifier for a Communication link.
<ChannelId> - Identifier for a channel used in communication. E.g 'A' or 'B'.
<FEP> - The name of the FEP.
<PM> - Identifies the PM within the FEP. In a dual configuration this will be either PRI or
SEC. In a single PM configuration this will be simply PRI.
<SMBPort> - The SMB, either 'A' or 'B'.
<Interface> - An interface name used for communication over a channel or Link.
<Network> The name of a network. E.g signalling network, control network.
<Tid> - Identifier for a track.
<Sid> - Identifier for a signal.
<Pid> - Identifier for a set points.
<Pids> - A collection of <Pid> items.
<TDLName> - Trackside data link name.
<TDLNumber> - Trackside data link number.
<TFMNumber> - Trackside functional module number.
<ModuleType> - Module type of a TFM, either 'Signal' or 'Points'.
<IOM> - identifier for a LOM/SOM IO Module associated with a FEP.
<CIP/TIF> - The name of associated TIF or CIP.
<MPMod> - The specific MP module to which the alarm relates.
<CMMod> - The specific CM module to which the alarm relates.
<DIMod> - The specific DI module to which the alarm relates.
<SCMMod> - The specific SCM module to which the alarm relates.
<ModSide> - Specific module side, left, right, middle where
<CIPTIFMod> - The specific module within the CIP or TIF to which the alarm relates (MP,
CM, DI, SCM).
<CSG> - Identifier for the Control system gateway.
<IECC> - Identifier for IECC control centre.

<IECCFaultCode> - Fault code reported for IECC.
<PMUX> - Identfier for PMUX panel processor.
<Location> - A junction, Repeater, long distance terminal or DLM associated with the
alarm.
<TrainDesc> - Identifier for a train describer linked to from the CSG.
<Westcad> - Identifier for a Westcad based control centre.
 - Input bit identifier used for filament/lamp proving
<FaultCode> An error code relating to the alarm.
224
Table 9.2 — Causes of Faults List Entries
ALARM
FAULT LIST ENTRY CAUSES
ID
<File> has been altered since

The installed file, <file> has been altered during run time resulting
9502 initialisation. Version now
in a CRC checking error
<Version>
<File> failed audit check. Version The installed file did not match its configured version value during
9503
not <Version> - CRC <CRC> start up audit checking
Installation.xml failed audit check. The installation.xml file did not validate against its expected CRC
9504
CRC <CRC>. Actual CRC <CRC> value during start up audit checking
<FILE> failed audit check.

The installed file, <file> did not match its expected CRC value
9505 Expected CRC <CRC> - Actual CRC
during start up audit checking
<CRC>
10001 Link <LinkId> failure Network link to an external TFL/TFS/TFR has failed (critical)
Channel failure. Interface A single channel has failed on a connection to a specific

10003
<Interface> Channel <ChannelId> <interface>. Check network connections to <Interface>
10004 Link <LinkId> failure Network link to an external TFL/TFS/TFR has failed (non critical)
<FEP> vital communications to

11011 Vital communication link to the FEP has failed
<LinkId> failure - %0
<FEP> non-vital communications

11012 Non vital communication link to the FEP has failed
to <LinkId> failure - %0
PM <PM> TF / WESTRACE data

11038 Identity received from PM did not correlate with configured value
mismatch
<FEP> PM <PM> network

11044 <Network> communications Network failure on PM <Primary/Secondary> Network<A/B>
failure
<FEP> SMB <SMBPort> not

11045 SMB <A/B> ports 1 and2 reporting non functional
functional
<FEP> SMB port <SMBPort> not

11046 SMB Port 1 OR port 2 reporting non functional
functional
11047 J-Logs not operational J Log drive not operational
11048 J-Logs not operational J Log drive not operational
11049 <volume> dismounted Specified drive not mounted
11105 NTP Server connection failed Connection to the NTP timer server failed
The NTP Time server is free running from its local CMOS clock
11106 NTP Server free-running indicating it could not establish communication with an external
time source
The TF is not receiving time from an NTP time server. Check NTP
11107 No Time Reference available
time server is running.
A time resynchronisation event has occurred. E,g day light saving

11108 Significant time jump
time change
<FEP> PM <PM> total network

11110 Network A and Network B failure for PM <PM>
communications failure

Table 9.2 — Causes of Faults List Entries (Continued)
ALARM
ID
<FEP> PM <PM> changeover

11111 Duty PM changeover occurred
occurred
<PM> network <Network>

11131 Indicates network failure to the specified PM
communications to TF failure
<Tid> Last Count In Override

11132 Override rejected for <Tid>
rejected by axle counter
Signal lamp proving input bit (R) from TFM/IOM = 0; output bit = 1.
11300 Signal <Sid> Red Lamp Proving
Failure of lamp in signal <Sid>.
First filament proving input bit (R) from TFM/IOM = 0; output bit =
11301 Signal <SId> Red First Filament 1; signal lamp proving bit = 1.
Failure of first filament of lamp in signal <Sid>.
Signal lamp proving input bit (H) from TFM/IOM = 0; output bit =
11302 Signal <Sid> Yellow Lamp Proving 1.
Failure of first yellow lamp in signal <Sid>.
First filament proving input bit (H) from TFM/IOM = 0; output bit =
11303 Signal <Sid> Yellow First Filament 1; signal lamp proving bit = 1.
Failure of first filament of first yellow lamp in signal <Sid>.
Signal lamp proving input bit (D) from TFM/IOM = 0; output bit =
11304 Signal <Sid> Green Lamp Proving 1.
Failure of green lamp in signal <Sid>.
First filament proving input bit (D) from TFM/IOM = 0; output bit =
11305 Signal <Sid> Green First Filament 1; signal lamp proving bit = 1.
Failure of first filament of green lamp in signal <Sid>.
Signal lamp proving input bit (HH) from TFM/IOM = 0; output bit =
Signal <Sid> Second Yellow Lamp
11306 1.
Proving
Failure of second yellow lamp in signal <Sid>
First filament proving input bit (HH) from TFM/IOM = 0; output bit
Signal <Sid> Second Yellow First
11307 = 1; signal lamp proving bit = 1.
Filament
Failure of first filament of second yellow lamp in signal <Sid>.
Signal lamp proving input bit (SUB) from TFM/IOM = 0; output bit
11308 Signal <Sid> Sub Lamp Proving =1.
Failure of lamp in subsidiary signal <Sid>.
First filament proving input bit (SUB) from TFM/IOM =0; output bit
11309 Signal <Sid> Sub First Filament =1; signal lamp proving bit = 1.
Failure of first filament of lamp in subsidiary signal <Sid>.
Signal lamp proving input bit (PL) from TFM/IOM = 0; output bit =
Signal <Sid> Position Light Lamp
11310 1.
Proving
Failure of position light lamp in signal <Sid>.
First filament proving input bit (PL) from TFM/IOM = 0; output bit
Signal <Sid> Position Light First
11311 = 1; signal lamp proving bit = 1.
Filament
Failure of first filament of lamp in position light signal <Sid>.
224
ALARM
ID
Signal lamp proving input bit (ON) from TFM/IOM = 0; output bit =
1.
11312 Signal <Sid> ON Lamp Proving
Failure of On lamp in shunt or fibre optic banner repeater signal
<Sid>.
Signal lamp proving input bit (OFF) from TFM/IOM = 0; output bit
= 1.
11313 Signal <Sid> OFF Lamp Proving
Failure of Off lamp in shunt or fibre optic banner repeater signal
<Sid>.
First filament proving input bit (ON) from TFM/IOM = 0; output bit
= 1; signal lamp proving bit = 1.
11314 Signal <Sid> ON First Filament
Failure of first filament of On lamp in shunt or fibre optic banner
repeater signal <Sid>.
First filament proving input bit (OFF) from TFM/IOM = 0; output bit
= 1; signal lamp proving bit = 1.
11315 Signal <Sid> OFF First Filament
Failure of first filament of Off lamp in shunt or fibre optic banner
repeater signal <Sid>.
Signal lamp proving input bit (U) from TFM/IOM = 0; output bit =
Route Indicator <Sid> Lamp
11316 1.
Proving
Failure of lamp in route indicator signal <Sid>.
First filament proving input bit (U) from TFM/IOM = 0; output bit =
Route Indicator <Sid> First
11317 1; signal lamp proving bit = 1.
Filament
Failure of first filament of lamp in route indicator signal <Sid>.
Signal lamp proving input bit from TFM/IOM = 0.

11318 Signal <Sid> Lamp Proving
Failure of lamp in mechanical banner signal <Sid>.
First filament proving input bit from TFM/IOM = 0; signal lamp

11319 Signal <Sid> First Filament Proving proving bit = 1.
Failure of first filament of lamp in mechanical banner signal <Sid>.
Signal lamp proving input bit (OFF) from TFM/IOM = 0; O output

11320 Banner Signal <Sid> (OFF) Proving bit = 1.
Failure of Off lamp in mechanical banner signal <Sid>.
Signal lamp proving input bit (ON) from TFM/IOM = 0; O output

11321 Banner Signal <Sid> (ON) Proving bit (OFF) = 0.
Failure of On lamp in mechanical banner signal <Sid>.
Searchlight Signal <Sid> Red Input bit (R) = 0; output bit (H) = 0; output bit (D) = 0.
11322
Proving Failure of red lamp in signal <Sid>.
Searchlight Signal <Sid> Yellow Lamp proving Input bit (H) = 0; output bit (H) = 1;.
11323
Proving Failure of yellow lamp in signal <Sid>.
Searchlight Signal <Sid> Green Lamp proving Input bit (D) = 0; output bit (D) = 1;.
11324
Proving Failure of green lamp in signal <Sid>.
Point <Pid> selected Normal but not detected Normal.

11325 Point <Pid> Normal Detection Control circuit failure; point machine failure; contactor failure;
power failure.

ALARM
ID
Point <Pid> selected Reverse but not detected Reverse.

11326 Point <Pid> Reverse Detection Control circuit failure; point machine failure; contactor failure;
power failure.
Point <Pid> selected Reverse but detected Normal.

Point <Pid> Normal Detection,
11327 Control circuit failure; point machine failure; contactor failure;
Reverse Control
power failure.
Point <Pid> selected Normal but detected Reverse.

Point <Pid> Reverse Detection,
11328 Control circuit failure; point machine failure; contactor failure;
Normal Control
power failure.
Point <PId> selected Normal and detected Normal, but slow to

Point <Pid> Normal Operation operate.
11329
Slow Point drive voltage low; point machine requires servicing; inspect
P-way for distortion and damage. Manual clearing by technician.
Point <PId> selected Reverse and detected Reverse but slow to

Point <Pid> Reverse Operation operate.
11330
Slow Point drive voltage low; point machine requires servicing; inspect
P-way for distortion and damage. Manual clearing by Technician.
Point <PId> detected Normal, but cannot be moved from Normal

Point <Pid> Normal Detection, No by Signaller's control.
11331
Control Control circuit failure from or at Control Centre, point machine
failure, point machine motor drive power failure, contactor failure.
Point <PId> detected Reverse, but cannot be moved from Reverse

Point <Pid> Reverse Detection, No by Signaller's control. Control circuit failure from or at Control
11332
Control Centre, point machine failure, point machine motor drive power
failure, contactor failure.
Point <Pid> Normal Detection,

11333 Error in interlocking data. Report fault to data designer.
Error Control
Point <Pid> Reverse Detection,

Error Control
Point <Pid> Error Detection, Point machine being detected N and R at the same time.
11335
Normal Control Point machine detection fault or detection wiring fault.
Point <Pid> Error Detection, Error Point machine being detected N and R at the same time.
11336
Control Point machine detection fault or detection wiring fault.
Point <Pid> Error Detection, No Power failure at point machine. Tail cable disconnected/damaged.
11337
Control Point machine failure in mid stroke. Point mechanism jammed.
Point <Pid> No Detection, No

Control
Point <Pid> Contactor while

Reverse
Point <Pid> No Detection, Error

Control
Point <Pid> Contactor While Contactor relay for points <Pid> failed while driving points
11341
Reverse Reverse.
11342 Point <Pid> Detection Signalling system not detecting points Normal or Reverse.
224
ALARM
ID
Point machine being detected N and R at the same time. Point

11343 Point <Pid> Error Detection
machine detection fault or detection wiring fault.
11344 Point <Pid> Contactor Contactor lost while interlocking disabled.
<TDLName>(<TDLNumber>)
Motors status bit from TFM = 0. Motor failure reported on points
11345 Points Module <TFMNumber>
number <Pids>
(Points <Pids>) Motor
Input interface status bit from TFM = 0.

Failure of tail cable between <TFMNumber> and points/signal.
11346 <ModuleType> <TFMNumber>
Internal failure of <TFMNumber>; Power supply fault, TFM down
Input Interface
due to external fault. Powering TFM down then up may clear fault.
Output interface status bit from TFM = 0.

<TDLName> (<TDLNumber>) Failure of tail cable between <TFMNumber> and points/signal,
11347 <ModuleType> <TFMNumber> internal failure of <TFMNumber>, power supply fault, if points
Output Interface machine connected to TFM, check contactor relay. TFM down due
to external fault. Powering TFM down, then up may clear fault.
<TDLName> (<TDLNumber>) Output interface statusbiti from TFM = 0. If fault persists, TFM will
<ModuleType> <TFMNumber> shut down due to external fault.
11348
Output Interface Temporary Powering TFM down, then up may clear fault. Otherwise check
Disable external circuits and connected equipment.
<TDLName> (<TDLNumber>) OPT RX <LinkID> status bit from TFM = 0.

11349 Outward Link Fault at TFM
Failure of TFL Link A or B between DLM and <TFMNumber>.
<TFMNumber> Link <LinkID>
OPT RX A and OPT RX B status bits from TFM = 0.

<TDLName> (<TDLNumber>)
Failure of both TDL links between DLM and <TFMNumber> TFM
11350 Outward Link Fault at TFM
failed, replace TFM, otherwise check connections between DLM
<TFMNumber> Both Links
and TFM.
<TDLName> (<TDLNumber>) No IPT RX <Link ID> status bit status bit from TFM = 0.
11351 Reply from TFM <TFMNumber> Failure of TDL Link A or B before <TFMNumber>. Faulty connection
Link <LinkID> or TFM failure.
IPT RX A and IPT RX B status bits from TFM = 0.

<TDLName> (<TDLNumber>) No Failure of TDL Link A and B before <TFMNumber>. Faulty
11352 Reply from TFM <TFMNumber> connection, TFM failure. TFM shut down due to external fault.
Both Links Powering TFM down, then up may clear fault. Otherwise check
external circuits and connected equipment.
<TDLName> (<TDLNumber>) TFM Outward Link Fault. Link A alarm from all TFMs at <Location>.
11353 Outward Link Fault at Location
Check output connections from common DLM to TFMs.
<Location> Link <LinkID>
<TDLName> (<TDLNumber>) TFM Outward link fault. Link A and B alarm from all TFMs at
11354 Outward Link Fault at Location <Location>.
<Location> Both Links Check output connections from common DLM to TFMs.
<TDLName>(<TDLName>) No
11355 Replies from TFMs at Location TFM IPT RX A or IPT RX B alarm from all TFMs at <Location>.
<Location> Link <LinkID>
<TDLName>(<TDLName>) No
11356 Replies from TFMs at Location TFM IPT RX A and IPT RX B alarm from all TFMS at <Location>.
<Location> Both Links

ALARM
ID
IPT RX A or IPT RX B status received from a TFM that was not
11358 Unexpected Reply from TFM
defined in the scheme.
<TFMNumber> Link <LinkID>
IPT RX A and IPT RX B status received from a TFM that was not
11359 Unexpected Reply from TFM
defined in the scheme.
<TFMNumber> Both Links
<FEP> Outward Link Fault at And

11360 Outward link fault reported for all DLMs at and beyond <Location>
Beyond <Location> Link <LinkID>
<TDLName> No Reply From And

IPT RX A or IPT RX B alarm from all TFMs at all locations for <TIF>
11361 Beyond INTERLOCKING Link
on link <LinkID>
<LinkID>
IPT RX A and IPT RX B alarm from all TFMs at all locations for
11362 Outward Link Fault at And Beyond
<TDLName>(<TDLNumber>).
INTERLOCKING Both Links
OPT RX A or OPT RX B alarm from all TFMs at and beyond
11363 Outward Link Fault at and Beyond
<identifier>
<Identifier> Link <LinkID>
<TDLName>(<TDLNumber>) No
IPT RX A or IPT RX B alarm from all TFMs from and beyond
11364 Reply From And Beyond
<identifier> on link <LinkID>
<Identifier> Link <LinkID>
OPT RX A and OPT RX B alarm from all TFMs at and beyond
<identifier>
<Identifier> Both Links
OPT RX A and OPT RX B alarm at and Beyond <identifier> both
links.
<TDLName>(<TDLNumber>) No
OPT RX A and OPT RX B alarm from all TFMs on
11367 Reply From And Beyond
INTERLOCKING Both Links
<TDLName> (<TDLNumber>) No
11368 Reply from and Beyond
<identifier> on link <LinkID>
<Identifier> Link <Link>
<location> on link <LinkID>
<Location> Link <Link>
IPT RX A and IPT RX B alarm from all TFMs from and beyond
<location> on link <LinkID>
<Location> Both Links
IPT RX A and IPT RX B alarm from all TFMs from and beyond
<identifier>
OPT RX A or IPT RX B alarm from all TFMS at and beyond
11372 Outward Link Fault at And Beyond
INTERLOCKING Link
Point <Pid> Contactor While

11373 Contactor relay for points <Pid> failed when driving points Normal
Normal
224
ALARM
ID
Point <Pid> Reverse Contactor

11374 Contactor not responding to Reverse points calls
Operation
Point <Pid> Normal Contactor

11375 Contactor not responding to Normal points calls
Operation
<FEP> No Reply From RSMB SMB A or SMB B port status for all IOMs on <RemoteSMB> at
11376
<RemoteSMB> Link <LinkID> <FEP> failed
<FEP> No Reply from RSMB SMB A and SMB B port status for all IOMs on <RemoteSMB> at
11377
<Remote smb> Both Links <FEP> failed
<FEP> No Reply From and Beyond SMB A or SMB B port status for all IOMs from and beyond
11378
<LocationIdentifer> Link <LinkID> <LocationIdentifier> at <FEP> for link <Link ID>
<FEP>No Reply From and Beyond SMB A and SMB B port status for all IOMs from and beyond
11379
<LocationIdentifier> Both Links <LocationIdentifier> at <FEP> for link <LinkID>
<FEP> <IOM> Module failure on

11380 SMB A or SMB B port status failure at <IOM> on link <LinkID>
Link <link>
11381 <FEP><IOM> Module failure Module failure reported by <IOM>
11382 <CIP/TIF> WESTLOCK address error Trident reported WESTLOCK address error status bit = 1
11383 <CIP/TIF> Message type error Trident reported message type error status bit = 1.
11384 <CIP/TIF> Protocol type error Trident reported protocol type error status bit = 1.
<CIP/TIF> <Mod> MP 24 v logic Trident reported logic power status bit = 0 for MP <Mod>
11385
power <Logic Power ID <LogicPowerID> as 0
11386 <CIP/TIF> MP System Fault Trident reported System OK status bit = 0
11387 <CIP/TIF> Program Fault Trident reported Program Alarm status bit = 1
11388 <CIP/TIF> System Fault Trident reported System Shutdown status bit = 1
<CIP/TIF> MP <MPMod> Network

11389 Trident reported MP <Mod> Net OK status bit = 1
fault
11390 <CIP/TIF> <MPMod> MP Fault Trident reported Battery OK status bit = 0
<CIP/TIF> <CMMod> CM Signalling

11391 Trident reported Net 1 OK (Signalling Network) status bit = 0.
network failure
<CIP/TIF> <Mod> CM Control

11392 Trident reported Net 2 OK (Control Network) status bit = 0.
network failure
Trident reported. Field Power 1 OK status = 0 and Field Power 2 OK

11393 <CIP/TIF> <DIMod> DI fault
status = 0.
11394 MP Module Fault Trident reported No Failed Modules status bit = 0
<CIP/TIF> <CIPTIFMod> Hardware

11397 Trident reported Hardware Fault status bit = 1
Fault
11398 <CIP/TIF> Data Version Fault Trident reported True/Complement DV Mismatch status bit = 1
<CIP/TIF> Received message type

11400 Trident reported Received Tech Request MT Error status bit = 1
fault
11401 <CIP/TIF> Received QDIV Fault Trident reported Panel Request IV Error status bit = 1

ALARM
ID
<CIP/TIF> Received <Link>

11402 Trident reported First telegram out of range status bit = 1
telegram range fault
<CIP/TIF> Received <Link>

11403 Trident reported invalid number of telegrams status bit = 1
telegram volume fault
<CIP/TIF> Received <Link> SSI

11404 Trident reported Invalid SSI number status bit = 1
identity fault
<CIP/TIF> <Link> Channel Trident reported signalling network link status for Channel
11405
<ChannelID> failure <Channel ID> Link status bit = 0
<CIP/TIF> Received <LinkID>

11406 Trident reported Safety Code Error status bit = 1
Safety Code error

11407 Trident reported Message Out Of Sequence status bit = 0
Message sequence fault

11408 Trident reported Message Delayed status bit = 1
Message delay fault

11409 Trident reported Single Missed Message status bit = 1
Message missed fault

11410 Trident reported Single Late Message status bit = 1
Message late fault

11411 Trident reported Protocol Type Error status bit = 1
Protocol Fault
11412 <CSG> Duty failure Duty Processor failure detected for <CSG>
11413 <CSG> Event Logger Not in Use Event logger not in use detected for <CSG>
11414 <CSG> Temperature Not OK Temperature reported as Not OK by <CSG>
11415 <CIP/TIF> Not Healthy <CSG> reported Not healthy
11416 <CIP/TIF> Not Available <CSG> reported as not available
11417 <CSG> Link to IECC<IECC> failed Failure of link to <IECC>
<CSG> Fault on IECC

11418 <IECCFaultCode> Reported for IECC
<IECCFaultCode>
<CSG> Link to Train

11419 Connection failure between CSG and Train Describer
Describer<LinkID> failed
<CSG> Link to PMUX <PMUX>

11420 Connection failure between CSG and PMUX <PMUXID>
failed
<CSG> Link to PMUX

11421 Connection failure to <PanelProceIDs> panel processors
<PanelProcIDs> <PMUX>
11422 <CSG> PMUX <PMUX> Fault code reported for <PMUX> by <CSG>
<CSG> Link to PMUX<PMUX>

11423 <PMUX> Output card failure
Output cards

11424 <PMUX> Input card failure
Input cards
224
ALARM
ID

11425 <PMUX> Input Scanner
Input Scanner
Total failure of CSG. Can be due to any of:

11426 <CSG> Total Failure “Duty Processor”,”Event Logger”,” Temperature OK”, “Healthy” or
“Available” states reporting as failed on both CSGs in CSG pair.
<CSG> to IECC Link <IECC> Total

11427 Both CSGs in pair reporting link failure to <IECC>
Failure

11428 Both CSGs in pair reporting link failure to <PMUX>
Total Failure
<CSG> Link to Train Describer

11429 Both CSGs in pair reporting link failure to <TrainDesc>
<TrainDesc> Total Failure
<CSG > Link to PMUX <PMUX>

11430 Both CSGs in pair reporting <PMUX> Output card failure
Output Cards Total Failure
<CSG > Link to PMUX <PMUX>

11431 Both CSGs in pair reporting <PMUX> Input card failure
Input Cards Total Failure
11432 <CSG> Input Scanner Total Failure Both CSGs in pair reporting input scanner failure

11433 Both CSGs in pair reporting PMUX <PMUX> link failure
Total Failure
11434 <TIF> <SCMMod> DLM Link Fault <TIF> SCM <SCMMod> reporting DLM link fault
11435 <Westcad> Not available Link failure between the WESTCAD based control centre and CIP
<CIP/TIF> TDL Tgm manchester Trident reported Manchester encoding error status bit = 1 for <CIP/
11436
encoding fault TIF>
<CIP/TIF> TDL Tgm – Direction Trident reported Manchester encoding error status bit = 1 for <CIP/
11437
fault TIF>
11438 <CIP/TIF> TDL SSI Identity fault Trident reported SSI Number Error status bit = 1 for <CIP/TIF>
11439 <CIP/TIF> Tgm – TFM address fault Trident reported TDL Address Error status bit = 1 for <CIP/TIF>
11440 <CIP/TIF> TDL Tgm – Parity fault Trident reported TDL Parity Error status bit = 1.
<CIP/TIF> TDL A/B Data Mismatch

11441 Trident reported TDL A/B Data Mismatch.
fault
MP <MOD> Installed, Active or Passed status bit = 0 reported by

11442 <CIP> <MPMOD> MP Fault
trident.
11443 <CIP><MPMOD> MP Fault Trident reported >= Dual Mode Status bit = 0
Trident reported TMR Status bit = 0 and >= Dual Mode status bit =
11444 <CIP> Fault
1
Trident reported Installed, Locked, Active, Passed, No Faults, Logic

11445 <CIP/TIF><CMMod> CM Fault
Power 1 OK or Logic Power 2 status bit = 0
Trident reported Active, Locked, Installed, Passed, No Field Faults,

11446 <CIP> <DIMod> <DISide> DI Fault
Logic Power 1 OK or Logic Power 2 OK status bit = 0
Trident reported Field Power 1 OK and Field Power 2 OK status bit

11447 <CIP> <DIMod> DI Fault = 0… or Active (right side), Active (left side) status bit = 0 or No
Faults On Active Module status bit = 0.

ALARM
ID
Trident reported No Faults, or Not Faults On Active Module status

11448 <TIF> SCM Fault
bit = 0 for SCM on <TIF>
Trident reported Installed, Locked, Active or Passed Status bit = 0

11449 <TIF><SCMMod> Fault
for <SCMMOD> on <TIF>
11450 <TIF><SCMMOD> Link Fault Trident reported all DLT link status bits = 0
<Westcad> Link to <LinkID>

11451 The westcad control centre link has failed to <LinkID>
Channel <ChannelID> Failed
CC Link to <LinkID> Channel Both Westcad CSGs in a pair report that link to <ChannelID> on
11452
<ChannelID> Total Failure <LinkID> has failed
Indicates that no diagnostics are being received over the trident

11453 No P2P Diagnostics received
link. Check trident connections
<CMMod> CM Control network

11454 Trident reports Control Network Status bit = 0 for CM
total failure
<CSG> Link to <LinkID> Channel

11455 CSG (PMUX) link to <LinkID> has failed
<ChannelID> Failed
<CSG> Link to <LinkID> Channel

11456 CSG <PMUX> link to <LinkID> failed for both CSGs in pair
<ChannelID> Total Failure
DI <DIMod> <ModSide> DI Trident reports Locked, Installed, Passed or No Field Faults status
11457
Standby module unavailable bit = 0 when Active status bit also equals 0
11458 Loss of WNC channel <ChannelID> Indicates loss of a WNC channel
<CIP/TIF> CM not receiving

11459 messages for WNC <WNCID> No message for <WNCID> on <ChannelID>
channel <ChannelID>
Left/Right message count

Differing number of messages have been received on
11460 divergence detected for <WNCID>
<ChannelID> for <WNCID>
channel <ChannelID>
11461 <CIP/TIF> <CMMOD> Not Locked Trident reports <CMMOD> Locked status bit = 0.
<CIP/TIF> <MPMOD> MP Not

11462 Trident reports <MPMOD> Locked status bit = 0.
Locked
Trident reports Net OK, Batter OK, Locked, Installed, Active and
11463 <CIP/TIF><MPMOD> MP Fault
Passed status bit = 0 for <MPMOD>
Trident reports Installed, Locked, Active, Passed, No Faults,

<CIP/TIF> <CMMOD> CM Total
11464 LogicPower 1 OK and Logic Power 2 OK status bits = 0 for
Failure
<CMMOD>
Signal lamp proving input bit (U) from TFM/IOM = 0. Output bit =
Standard Route Indicator <Sid>
11465 Signal lamp proving bit = 1
 Lamp Proving
Failure of lamp on Standard route indicator signal <Sid>.
Standard Route Indicator <Sid> First filament input bit (U) from TFM/IOM = 0. Output bit =
11466
 First Filament Failure of lamp on Standard route indicator signal <Sid>.
Miniature Route Indicator <Sid>
11467 Signal lamp proving bit = 1.
 Lamp Proving
Failure of lamp on Miniature route indicator signal <Sid>.
224
ALARM
ID
Miniature Route Indicator<Sid>
11468 Signal lamp proving bit = 1.
 First Filament
Failure of lamp on miniature route indicator signal <Sid>.
Disconnect ESOC Technicians

Indicates the ESOC has been disconnected for <TMinutes>
11500 Control applied for more than
minutes
<TMinutes> minutes - %0
11501 <FEP> <IOM> Not Operational IOM Module is not operational
11502 <FEP><IOM>< Addressing Error Installation address error reported for IOM
<FEP> <IOM> is Negated. Code Indicates that module <IOM> is negated. <Code> provides the
11503
<Code> error code.
11504 <FEP> <IOM> Configuration Error Configuration Error detected on <IOM>
11505 <FEP> <IOM> Address Error Address Error detected on <IOM>
<FEP> <IOM> 24V Supply Failure

11506 24V supply failure on Link A for <IOM>
Link A
<FEP> <IOM> 24V Supply Failure

11507 24V supply failure on Link B for <IOM>
Link B
<IOM> Output Interface Disabled

11508 SOM110 module has been disabled due to <FaultCode>
<FEP> with code <FaultCode>
11509 <IOM> Red Retaining Enforcement Red retaining enforcement failure at <IOM>
test output <Outputs>
11510 <IOM> Output <Outputs> over <IOM> reports over current
current
11511 <IOM> Signalling Supply Voltage <IOM> Signalling supply voltage out of range
Out of Range
11512 <IOM> Total Output Over-Current <IOM> exceeded over current
exceeded
11513 <IOM> Signalling Supply <IOM> Frequency is out of range
Frequency Out of Range
11514 <IOM> Current leakage detected
<IOM> Current Leakage Detected
11515 <IOM> Over Current on Coded <IOM> Signal source A over current
Signal Source A
11516 <IOM> Over Current on Coded <IOM> Signal source B over current
Signal Source B
11517 <IOM> Signalling Supply <IOM> Frequency out of range
Frequency Out of Range

ALARM
ID
11518 <IOM> Loss if signalling supply
<IOM> Loss of Signalling Supply
11519 <IOM> Bad quality Signalling <IOM> Bad quality signalling supply
Supply
11520 <IOM> Signalling Supply Voltage <IOM> Signalling supply voltage out of range
Out of Range
11521 <IOM> Outputs <Outputs> Short Short circuit detected in <IOM>
Circuit
11522 <IOM> Outputs <Outputs> Over <Outputs> on <IOM> over circuit
Circuit
11523 <IOM> Outputs <Outputs> Current leakage detected for <Outputs> on <IOM>
Current Leakage
11524 ESOC Operation ESOC Has been operated
ESOC Operation with High Input

11525 High Input failure detected upon ESOC operation
Failure
ESOC Operation with Low Input

11526 Low input failure detected upon ESOC operation
Failure
<CIP/TIF> <LinkID> Blocked

11527 Message context blocked to <LinkID>
context fault
<CIP/TIF> <LinkID> Next context

11528 Next message context blocked to <LinkID>
blocked fault
11529 <CIP/TIF>Trident Actual Scan Error Trident reported Actual Scan Error status bit = 1
<CIP/TIF>Trident Requested Scan

11530 Trident reported Requested Scan Error status bit = 1
Error
<CIP/TIF>Trident Scan Overrun

11531 Trident reported Requested Scan Overrun Error = 1
Error
11532 <CIPTIFMod> High Temperature Trident reports temperature >70Degrees and < 80 degrees
11533 <CIPTIFMod> High Temperature Trident reports temperature > 70 degrees and < 80 degrees
<CIP/TIF> Version number Trident reported version number does not match configured
11534
mismatch value. Suggests incorrect scheme data on either CIP or TF
<CIP/TIF> <LinkID> Total link

11535 Channel A and Channel B failure to <LinkID>
failure
<FEP> No Reply From And Beyond Indicates that SMB Port status that SMB A or SMB B links have
11536
FEP SMB Link <LinkID> failed for all IOMS on <FEP>
<FEP> No Reply From And Beyond

11537 Indicates both SMB A and SMB B links are down
Both FEP SMB Links
11538 Cadlock Link failure Indicates there is not link between the TF and Cadlock
224
Note: A repeating transient Control Network fault may be seen occasionally as a false alarm.
It should be ignored unless its frequency is obscuring other messages.
Note: If status information for a set of points is split across multiple IOMs and one of these
IOMs is removed then this can result in spurious alarms being reported.
Note: The TF aggregates all TFMs associated with a given PSU and only raises an alarm when
all TFMs report a failure to reply.
Note: In the event of a CM module being removed or in any other way disabled, it is possible
that an occurrence of alarm 11405 is seen. The alarm should be ignored if observed in
this scenario.

9.3 WESTLOCK Equipment (WLE) Tab Variations

This sub-section lists all the information available via the WLE tab on the State Viewer,
indicates the normal (fault-free) condition for each entry and recommends corrective
action if a fault is indicated.
Level 1 is the top level view with CIP, TIF, CSG A, CSG B and TW(L) all shown collapsed.
Level 2 is the first expansion of an entry, obtained by clicking on the + to the left of the
heading. Levels are shown in Figure 3.20.
Note: Before relying on the information in the WLE Tab for the CIP or TIFs, ensure that its
WESTLOCK Address is non-zero.
Following the total loss of Signalling Network communications, the WESTLOCK Address
is reset to zero. However, other information remains as last set and may therefore be
incorrect.
224
Table 9.3 — WLE Tab Variations
NORMAL SEE TABLE 9.4

LEVEL 1 LEVEL 2 LEVEL 3 LEVEL 4
VALUE SERIAL No. …
WESTLOCK Address = See WISR
As per
Software Version = installed
baseline
Data Build Version = See WISR
Requested Scan Time = 212 ms
Actual Scan Time = <195 ms 15
Num Scan Overruns = 0 15
TMR Mode 1 1
>=Dual Mode 1 2
Logic Power 1 OK 1 3
CIP No Failed Modules 1 4
System OK 1 5
Program Alarm 0 6
System Shutdown 0 7
MP Status
Net OK 0 8 (i)
Battery OK 1 9
Installed 1 10
Locked 1 11
Right MP Status
Active 1 12
Passed 1 13
Should be less
Shows
Temperature than +70 °C If
value in °C
greater, see 14.

Table 9.3 — WLE Tab Variations (Continued)

Middle MP Status As above

MP Status (con)
Left MP Status As above
Net 1 OK (Signalling
1 8 (ii)
Network)
Net 2 OK (Control
1 8 (iii)
Network)
Installed 1 16
Locked 1 11
Active 1 17
Right CM Status
Passed 1 13
CM Status
No Faults 1 18 (i)
CIP
(con) Should be less
Shows
Temperature = than +70 °C If
value in °C
greater, see 14.
As for Right CM
Left CM Status
Status above.
TMR Mode 1 20
>=Dual Mode 1 21
DI Status Field Power 1 OK 1 19
Field Power 2 OK 1 19
No Faults 1 18 (ii)
No Faults on
1 22
Active Module
224

Installed 1 16
Locked 1 11
1 if on-line
Right DI Status Active 1
0 if off-line.
DI Status (con)
Passed 1 13
No Field Faults 1 23
As for Right DI Status

Left DI Status
above
True Data Error 0 24
Complement Data
1 24
Error
True/Complement
0 25
Disagreement
Hardware Fault 0 26
Received Version
0 27
Number Error
CIP
True/Complement
(con) 0 28
Application Status DV Mismatch
Received Tech
0 29
Request MT Error
Received Panel
0 30
Request IV Error
First Telegram Out of

0 31
Range
TIF Comms Alarms
Invalid Number of
[Location] 0 31
Telegram
Invalid SSI Number 0 32
Green - Link
healthy
Orange - Partial
failure (Dual
[SIG/CTRL] N/W
link)
Link Status Node [n]
Red - Link
[Destination]
failure
Grey - Link state
unknown/
unreported.


Mac Error Detected 0 34
Message Out of
0 35
Sequence
Message Delayed 0 36
Node 3 TIF Initialising 0 37

[Location] Recovering 0 37
Sig N/W Safety Layer Single Missed
Status 0 38
Message
Single Late Message 0 38
Protocol Type Error 0 39
Node 4 TIF
As for Node 3 above
[Location]
Node 5 TIF
As for Node 3 above
[Location]
Node 2 TW(L) Number Blocked 0 40

CIP
(con) Next Blocked 0 41
Node 3 TIF
As for Node 2 above
[Location]
Sig N/W Context Status
Node 4 TIF
As for Node 2 above
[Location]
Node 5 TIF
As for Node 2 above
[Location]
TIF [Location] MT
42
= [Version No.]
CADLOCK Version
42
= [Version No.]
Indication IV =
42
[Version No.]
Version Numbers
Panel Request PT
42
= [Version No.]
Panel Request IV =
42
[Version No.]
Technician's
CIP
Request PT = 42
(end)
[Version No.]
224

As per
baseline
Requested Scan Time 50 ms
Actual Scan Time <50 ms 15
Num Scan Overruns 0 15
TMR Mode 1 1
>=Dual Mode 1 2
TIF
(for
each No Failed Modules 1 4
TIF System OK 1 5
Loca-
tion) Program Alarm 0 6
System Shutdown 0 7
Net OK 0 8 (i)
MP Status
Battery OK 1 9
Installed 1 10
Locked 1 11
Right MP Status
Active 1 12
Passed 1 13
Should be less
Shows
value in °C
greater, see 14.
As for Right MP
Middle MP Status
Status above
As for Right MP
Left MP Status
Status above


Net 1 OK (Signalling
1 8 (ii)
Network)
Net 2 OK (Control
0 8 (iv)
Network)
Installed 1 16
Locked 1 11
Active 1 17
Right CM Status
Passed 1 13
CM Status
No Faults 1 18 (ii)
Should be less
Shows
value in °C
greater, see 14.
As for Right CM
Left CM Status
Status above
TIF (con) TMR Mode 1 20
>=Dual Mode 1 21
No Faults 1 18 (ii)
No Faults on
1 22
Active Module
SCM Status TMR Mode 1 20
>=Dual Mode 1 21
Installed 1 16
Locked 1 11
Right SCM Status
Active 1 17
Passed 1 13
Connected 1 43
Initialising 0 37
224

DLM/LDT Link A OK 1 44
Right SCM Status
DLM/LDT Link B OK 1 44
(con)
SCM Status (con) DLM/LDT Link C OK 1 44
As for Right SCM

Left SCM Status
Status above.
True Data Error 0 24
Complement Data
0 24
Error
True/Complement
0 25
Disagreement
Hardware Fault 0 26
Received Version
0 27
Number Error
DLM Health Error 0 45

TIF (con)
TDL Manchester
0 46
Error
TDL Direction Bit

Application Status 0 47
Error
TDL SSI Number

0 48
Error
TDL Address Error 0 49
TDL Parity Error 0 50
TDL A/B Data

0 51
Mismatch
First Telegram Out of

0 31
Range
CIP Comms
Invalid Number of
Alarms 0 31
Telegram
Invalid SSI Number 0 32


Green - Link
healthy
Orange - Partial
failure (Dual
[SIG/CTRL] N/W
link)
Red - Link
[Destination]
failure
Grey - Link state
unknown/
unreported.
Mac error detected 0 34
Message out of
0 35
sequence
Message delayed 0 36
TIF (con)
Sig N/W Safety Layer Initialising 0 37
Node 1 CIP
Status Recovering 0 37
Single Missed
0 38
Message
Single Late Message 0 38
Protocol Type Error 0 39
Node [number] Number Blocked 0 40

CIP Next Blocked 0 41
Sig N/W Context Status
Node [number] Number Blocked 0 40
TW(L) Next Blocked 0 41
TIF CIP MT = [Version

Version Numbers 42
(end) No.]
224

As per
baseline
Duty Processor 1 52
Event Logger in Use 1 53
Temperature OK 1 54
CSG Healthy 1 55
CSG Available 1 56
Receiving From
1 57
Panel Processor 1
Receiving From
1 57
Panel Processor 2
Output Scanner 1
1 58
OK
CSG 01
Output Scanner 2
1 58
OK
[Location] Status
Non Duplicate
1 59
Output Cards OK
Non Duplicate
1 59
Input Cards OK
Input Scanner OK 1 58
WLPP Fault Code CC 0 60
LC 0 60
Green - Link
healthy
Orange - Partial
failure (Dual
[SIG/CTRL] N/W
link)
Red - Link
[Destination]
failure
Grey - Link state
unknown/
unreported.
CSG 02 As for CSG 01


As per
baseline
Green - Link
healthy
TW(L) Orange - Partial
failure (Dual
[SIG/CTRL] N/W
link)
Red - Link
[Destination]
failure
Grey - Link state
unknown/
unreported.
CIP = [Version
Version Numbers 42
No.]
Table 9.4 — WLE Tab Error Corrective Actions
SERIAL
(from
MEANING REQUIRED CORRECTIVE ACTION
Table
9.3)
If 0, Controller is not working in

Identify the faulty MP module in the Controller, using the MP
Triple Modular Redundant mode.
1 Status entries. Replace the faulty MP using the procedure given in
One or more MP modules have
manual M1360/MAINT.
failed.
Identify the faulty MP modules in the Controller, using the MP

If 0, two or more MP modules in Status entries. Replace the faulty MPs using the procedure given in
2
Controller have failed. manual M1360/MAINT. Then download data versions as specified
in WISR.
Check Status indicator on corresponding PSU. If not lit and 110 V

a.c. input present, replace PSU. If 110 V a.c. input not present,
If 0, indicated Controllers 24 V d.c
3 check supply source and fuses. If PSU Status indicator lit and other
supply failed.
equipment powered from that PSU is OK, check fuse in MP
baseplate.
Check WLE Tab indications for all modules in CIP, looking for
abnormal indications, then refer back to this Table. Check status
4 If 0, failed module detected in CIP. indicators on faulty equipment / module (see M1360/MAINT) to
confirm and refine fault diagnosis. Replace the faulty LRU,
following procedure given in manual M1360/MAINT.
Check all Fault List entries for the Controller and carry out required
5 If 0, system fault detected. corrective actions listed in this Table for those entries showing
incorrect values.
224
Table 9.4 — WLE Tab Error Corrective Actions (Continued)
SERIAL
(from
Table
9.3)
Check Software Version against installed baseline and check Data

Build Version against WISR. If incorrect, download correct software
If 1, software fault or incorrect version.
6
software version loaded. If software versions correct, remove and replace the affected MP
module (using method given in M1360/MAINT).
If fault persists, replace the MP module with a serviceable spare.
If 1, Controller has been forced to Note: For CIP, MP Status, System Shutdown - this bit is never set. If
shutdown due to failure of shutdown does occur, then TW(L) will report a critical fault.
7 processing channels to agree For TIF, MP Status, System Shutdown, Identify and replace faulty
correct output, or other MP module(s) in the Controller, using the procedure given in
catastrophic safety related failure. manual M1360/MAINT.
If 1 indicates that the MP's data

8 (i) download port (TriStation port) is For MP TriStation port (for CIP and TIF) - no action required
in use.
CM Signalling Network (for CIP and TIF) - restore communications

If 0, indicates loss of channel.
8 (ii) communication with Control or
A power supply failure will cause a loss in communication on the
Signalling Network channel.
connected networks - check the UPS is working correctly.
If 0, indicates loss of CM Control Network (for CIP) - restore communications channel.

8 (iii) communication with Control or A power supply failure will cause a loss in communication on the
Signalling Network channel. connected networks - check the UPS is working correctly.
CM Control Network (for TIF) - note that when a CM is plugged

into a TIF, at the point in the initialisation process where the PASS
8 (iv) Not used
light is on but the ACTIVE light is still off, the Net2 bit in the WLE
tab goes to 1 (Net OK) temporarily. This is normal operation.
This has no practical affect on the operation of the system, but

identify and replace faulty MP module in the Controller, using the
9 If 0, MP module battery has failed.
procedure given in manual M1360/MAINT. Return replaced
module to Siemens Rail Automation for fitment of new battery.
Fit serviceable MP module using procedure given in manual

If 0, indicated MP module M1360/MAINT. Wait for it to become Active following
10
removed from Controller. programming by remaining two MP modules (approximately 10
minutes).
Re-seat (i.e. remove and replace) module. Lock module correctly

If 0, module unlocked from to baseplate (see manual M1360/MAINT). If this is not possible,
11
baseplate. replace module with a serviceable spare (see M1360/MAINT). If
fault still present, replace baseplate (see M1360/MAINT).
If 0, module not processing

Wait at least 10 minutes to give module time to be programmed.
interlocking data. If module has
If still not Active, remove and re-fit module and wait a further 10
12 just been re-fitted or replaced,
minutes. If still not active, replace MP module with a serviceable
then it is still being programmed
spare using procedure given in manual M1360/MAINT.
by remaining two MP modules.
Remove and re-fit faulty module. Monitor the indications to see if

13 If 0, module has failed self-test. fault recurs. If fault recurs replace module with a serviceable spare
using procedure given in manual M1360/MAINT.

SERIAL
(from
Table
9.3)
If temperature greater than 70 °C,

Take immediate action to reduce ambient temperature inside the
14 module is overheating and
cubicle. >70 is non-critical. >80 is critical.
immediate action is required.
If actual scan time is the same as During normal operation, occasional scan overruns will be seen. If
the requested scan time, there is a the ‘Num Scan Overruns’ item in the WLE tab is greater than 5,
15 possibility that a Scan Overrun has report occurrence to a second line engineer.
occurred. These are reported by
Non-critical.
the Num Scan Overruns bit.
Fit serviceable module using procedure given in manual M1360/

If 0, indicates module removed
16 MAINT. Wait for it to become Active following programming by
from Controller.
MP modules (approximately 10 minutes).
If 0, module not processing

Wait at least 10 minutes to give module time to be programmed.
interlocking data. If module has
If still not Active, remove and re-fit module and wait a further 10
17 just been re-fitted or replaced,
minutes. If still not active, replace module with a serviceable spare
then it is still being programmed
using procedure given in manual M1360/MAINT.
by MP modules.
Intended to be a summary of the other status information. Value

18 (i) If 0, fault detected on module. of No Faults bit on \ should not be trusted - use the other CM
Status bits to diagnose CM faults.
At module, check indicator LEDs for additional information (see

manual M1360/MAINT for indicator meanings). Remove and
18 (ii) If 0, fault detected on module. replace module then wait for it to become Active. Check Passed=1.
If Passed = 0 or fault still indicated, replace module with a
serviceable spare using procedure given in manual M1360/MAINT.
Check Status indicator on corresponding PSU. If not lit and 110 V

a.c. input present, replace PSU. If 110 V a.c. input not present,
If 0, indicated Field power supply
19 check supply source and fuses. If PSU Status indicator lit check
failed.
output voltage is correct. If fault still present, check wiring from
PSU to DI baseplate.
If 0, failure detected in one of the If other DI module is not serviceable, replace that faulty DI module
three internal channels of the immediately, using the procedure given in manual M1360/MAINT.
20 module. Module can continue
If other DI module is serviceable replace faulty module when
operating on the remaining two
convenient.
channels.
If 0, failure detected in two of the If hot spare was available at the time of failure, automatic
three internal channels of the changeover will have occurred. Identify and replace faulty DI
21
module. Module is not module in the Controller, using the procedure given in manual
operational. M1360/MAINT.
If 0, fault detected on active Urgently check status of hot-standby module and replace if faulty,
module and automatic using the procedure given in manual M1360/MAINT. After
22 changeover not possible as hot- initialisation, changeover should then occur.
standby module not detected as Check No Faults indication and if 0 see serial 18.
available.
If 0, fault detected in direct input Check Field wetting PSU for correct output. Repair as necessary.
23 Field wiring or associated switch If OK, check Field wiring, switches and contacts and repair as
or contact. necessary.
224
SERIAL
(from
Table
9.3)
Note: For CIP, Application Status, True Data Error - not reported,
always set to zero.
Note: For CIP, Application Status, Complement Data Error - always
If 1, error detected in True or set to 1.
24
Complement data channel. For TIF, Application Status, True Data Error, required corrective
action is to check all Fault List entries for the Controller and carry
out required corrective actions listed in this Table for those entries
showing incorrect values.
If 1, True and Complement data

25 channel outputs detected as For development use. Should not occur in the field.
producing different results.
For CIP and TIF, check all Fault List entries for the Controller and
26 Hardware fault. carry out required corrective actions listed in this Table for those
entries showing incorrect values.
Note: For CIP, Application Status, Received Version Number Error is

If 1, message received from set to 1, except when it is waiting for confirmation of a
27 network from location loaded with Technician's Request, when it is set to zero.
incorrect version software. For TIF, check CIP software version numbers are correct. If found
to be incorrect, report occurrence to second line engineer.
If 1, True and Complement data

28 channel outputs detected as For development use. Should not occur in the field.
producing different results.
If 1, Technician's request message

29 For development use. Should not occur in the field.
not understood and not actioned.
If 1, Panel (Control System)

30 request message not understood For development use. Should not occur in the field.
and not actioned.
Note: For TIF, Application Status, CIP Comms Alarms, First

31 If 1, communications error. Telegram Out of Range - not reported, always set to zero.
For development use. Should not occur in the field.
Note: For TIF, Application Status, CIP Comms Alarms, Invalid SSI
Number - if CIP sends an invalid SSI number, this bit will set and
If 1, TIF detected an invalid SSI unset once a second rather than being always set.
32
number sent by CIP.
Required corrective action is to report the occurrence to a second
line engineer.
33 Spare -
Note: For CIP, not reported, always set to zero.

34 If 1, communications error.
For TIF - For development use. Should not occur in the field.
Note: For CIP, not reported, always set to zero.

35 If 1, communications error.
If 1, message delayed due to busy

36 Not reported, always set to zero.
Signalling Network.

SERIAL
(from
Table
9.3)
If 1, Signalling Network
temporarily unavailable due to Note: For CIP, not reported, always set to zero.
37
initialising or recovering from a For TIF - For development use. Should not occur in the field.
fault.
If 1, single message on Signalling Note: For CIP, not reported, always set to zero.
38 Network not received or received
too late.
If 1,protocol error detected in Note: For CIP, not reported, always set to zero.
39 message(s) received from
Signalling Network.
If >1 indicates the number of

40 For development use. Should not occur in the field
contexts. Currently blocked.
If 1,indicates that the next context

41 For development use. Should not occur in the field
is blocked.
If , indicates there is an Note: CIP, Version Numbers, Technician's Request PT = is not

incompatibility between the two reported, always set to zero.
42 ends of the interface. Can only For all other Version Numbers, check software version numbers
occur if the wrong data has been are correct. If found to be incorrect, report occurrence to second
installed. line engineer.
43 Not used.
44 If 0, indicated LDT or DLM faulty. Investigate and repair.
If 1, Data Link Module detected as Replace faulty Data Link Module with a serviceable spare as
45
faulty. detailed in manual M1360/MAINT.
Note: If TIF receives a Manchester error in a trackside telegram,

If 1, coding error detected on this bit will set and unset once a second rather than being always
46 trackside data link. Suspect a poor set.
quality communication circuit.
Test communications circuit and repair as necessary.
Note: If TIF receives a trackside telegram with the direction bit set
If 1, trackside telegram has incorrectly, this bit will set and unset once a second rather than
47 being always set.
direction bit set incorrectly.
Report occurrence to second line engineer.
Note: If TIF receives an invalid SSI number in a trackside telegram,

If 1, invalid SSI number detected in this bit will set and unset once a second rather than being always
48 set.
a trackside telegram.
Note: If TIF receives a reply from the wring TFM, this bit will set
If 1, a reply from the wrong TFM
49 and unset once a second rather than being always set.
has been received.
Note: If TIF receives a trackside telegram with a parity error set,

this bit will set and unset once a second rather than being always
If 1, parity error detected in set.
50
trackside telegram.
Suspect a poor quality communications link. Test communications
circuit and repair as necessary.
224
SERIAL
(from
Table
9.3)
Note: If TIF receives a trackside telegram where the data from the
A and B link differs, this bit will set and unset once a second rather
If 1, TIF has received a trackside than being always set.
51 telegram where the data from the
Suspect a poor quality trackside data link. Test communications
A and B links differs.
circuit and repair as necessary. If comms circuit is OK, check TFM
status.
52 If 0, CSG indicated is off-line. Providing CGS Healthy = 1, no action required.
If 0, CSG's internal event logger is Information only. No action required. For development purposes
53
not in use. only.
Immediately open cubicle and reduce ambient temperature

If 0, CSG internal temperature is
54 around CSG. Check CSG internal fans are running and that air
too high.
filters are not clogged. Repair/clean as necessary.
Use CSG front panel indications (see manual M1360/MAINT) to

55 If 0, fault detected in CSG. diagnose fault to a line replaceable unit. Replace faulty LRU using
procedure contained in manual M1360/MAINT.
Check reason for non-availability - check CSG is powered up, check

front panel indications (see M1360/MAINT) for incorrect
If 0, CSG not available to go on-
56 indications, check all connections are correct. If fault persists,
line.
power down CSG for two minutes, then power up again to re-boot
it.
Check indicated Panel Processor is operational. If so, check

If 0, not receiving data from Panel
57 communication link connections between Panel Processor and
Processor link indicated.
CSG (terminated on 16-port RS422 serial card on CSG).
Check power supplies and connections to Scanner are correct. If

If 0, fault detected in indicated
58 fault persists, replace Scanner with a serviceable spare of the
output Scanner.
same type.
If 0, fault detected on one or more Use card indicators and any fault reports from Panel Processor
59 of indicated I/O cards on Panel operator to identify faulty card / input / output. Repair by
Processor. replacement of faulty line replaceable unit.
If 1, fault reported by WESTLOCK Re-start the CSG and report the occurrence to second line
60
Panel Processor software maintenance.

9.4 Printer
The print driver MicrosoftXPS is installed on the TF-L and TF-R, however there are
currently no local printing facilities.
A new printer will require the old printer ‘driver’ (software on the PC) to be replaced with
a driver specific to the new printer. To do this it will be necessary to close down the TF
(Section 3.2.3), log on as Administrator (Section 3.2.4), then install the new printer
driver, following the instructions provided with the new printer.
Even if the new printer is the same model as the old one, it may still be necessary to
delete the old printer driver and install the driver supplied with the new printer.
9.5 TF Clock
The TF acquires its NTP - compliant time source via a time signal generator located in the
network hardware. An NTP - compliant time interface then uses these messages to
modify the local system clock such that the system time synchronises with the source.
Note: The NTP time offset is configurable in milliseconds, i.e. 1000 represents a 1 second time
offset.
Note: If an NTP server is not detected the TF will not start.
Note: When the NTP time is reset, an alarm will be raised, indicating loss of connection whilst
the timing signal is re-established. This can take about one minute.
224

Technician's Facility For Westlock: User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technician's Facility For Westlock: User Manual

Uploaded by

Copyright:

Available Formats

User Manual

X1512-CTF-ENG-MN00207 User Manual

Date December 2014

Siemens Rail Automation Ltd.

User Manual X1512-CTF-ENG-MN00207

Quick Start TF-L and TF-R

Starting the Technician’s Facility (Local)

X1512-CTF-ENG-MN00207 User Manual

Revision Date Amendment

1.1 Oct 2014 Review comments incorporated

1.2 Oct 2014 Initial Issue

2.1 Nov 2014 Updated due to configuration system clean up.

3.1 Dec 2014 ECO0031720

User Manual X1512-CTF-ENG-MN00207

Quick Start TF-L and TF-R ....................................................................3

1 Introduction to this Manual ............................................................. 19

3 Operating Procedures - Local........................................................... 33

X1512-CTF-ENG-MN00207 User Manual

3.3.2 Log-On ............................................................................................................... 37

4 Area of Control (AoC) .................................................................... 111

User Manual X1512-CTF-ENG-MN00207

5 Technician Controls ....................................................................... 117

6 Alarms and Fault Diagnosis ........................................................... 135

7 Logging .......................................................................................... 145

8 Event Replay Facility...................................................................... 167

X1512-CTF-ENG-MN00207 User Manual

8.3.5 Events To Replay Window ................................................................................. 175

9 Reference Information .................................................................. 187

User Manual X1512-CTF-ENG-MN00207

Table 3.1 Role Operations................................................................................................. 39

X1512-CTF-ENG-MN00207 User Manual

Intentionally Left Blank

User Manual X1512-CTF-ENG-MN00207

Figure 1.1 Scroll Boxes ....................................................................................................... 22

X1512-CTF-ENG-MN00207 User Manual

User Manual X1512-CTF-ENG-MN00207

X1512-CTF-ENG-MN00207 User Manual

Figure 8.17 Example: Replay Event Search - Attribute Name................................................178

User Manual X1512-CTF-ENG-MN00207

AWS Automatic Warning System.

Bit An individual item from the State Viewer.

CIP Central Interlocking Processor.

Control System Any one of:

- Panel with panel multiplexer and train describer.

- IECC or compatible Control Centre.

- WESTCAD Control System.

CSG Control System Gateway.

DI Direct Input (module).

An input from the Signaller to the Interlocking that bypasses the

DIO Direct Input Telegrams.

DLM Data Link Module.

ERF Event Replay Facility.

ESOC Emergency Signals On Control.

FbO FEP Telegrams by Object.

FEP Front End Processor.

HTML Hyper Text Markup Language.

I/O Input / Output.

IDL Internal Data Link.

IECC Integrated Electronic Control Centre.

Interlocking Centre A collection of WESTLOCK equipment interfaced to (and

IOM Input / Output Module.

Item A piece of information that can be monitored on its own and

J-Log Used for arrest and removal by an Incident Investigator, the