WSTCF management process

From the EM RAM(S) Autumn Working Guidance (Appendix I) — report → FMS → classification → response → sign-back.

Process flow

1 — Report received
WSTCF reported by a signaller (train on TC showing clear) or by an RCM alarm (RADAR / Centrix). Log time, TC, line and reporting train.
2 — FMS fault raised
Raise the failure on FMS. Record on the daily CCIL 'Autumn Suspect WSTCF' log (created 00:01 for 24h); confirmed failures transfer to the per-DU WSTCF CCIL Master Log, open all season.
3 — Classify
Classify High / Low / Negligible using the hazard index (NR/L3/SIG/10047 Mod 03 §10.1). RCM trace evidence drives classification — a blip under 300ms is Negligible; no RCM at site means treat as High.
4 — Operational response
Apply the Appendix C scenario response: Reg 3.5 / double block / TS11 as required; arrange a wheelset check of the train involved within 30 minutes of the SCWO.
5 — Treatment before attendance
No site attendance where RCM traces indicate contamination — arrange RHTT/MPV treatment before staff attend. Staff attendance ahead of treatment needs SFI Level 3 permission.
6 — Sign back
Sign back at the Appendix D level for the classification (FF/NFF). Level 2/3 sign-back may be granted on RCM evidence. L2/L3 closure requires the SFI report + independent inspection RCM traces + interlocking data-logger extract.
7 — Report to NOC
High-risk failures: Form A (first failure) / Form B (simplified, subsequent on same circuit) to the NOC by 18:00, otherwise by close of play. TS11 s15 / F3.17A form daily.
8 — Restore normal working
Remove special working per the restoration rules below (RHTT pass / 3 consecutive trains + good RCM traces), reinstating on red/black forecasts.
9 — Withdraw special working
Formal withdrawal with photographic evidence and the Withdrawal form to the NOC (see withdrawal procedure below).

Scenario guidance (Appendix C)

Ref	Situation	Actions	Sign-back
1.1	Momentary blip under a passing train — TC shows clear while the train is on it	Check the RCM trace: was the loss of occupation over or under 300ms? Classify from the hazard index and arrange a wheelset check of the train involved within 30 minutes.	Per classification (App D)
1.2	Signaller-reported SCWO with no RCM at the site	No trace evidence available — treat as HIGH risk. Implement special working (Reg 3.5); SFI response required.	Full sign-back — L3
1.3	RCM-detected blip over 300ms	Classify via the hazard index (High unless mitigations apply). Special working until classification confirmed; check traces on adjoining TCs.	Per classification; L2/L3 may be granted on RCM evidence
1.4	RCM-detected blip under 300ms	Negligible (N0). No special working; record on FMS and the daily CCIL log.	L1
1.5	Late-reported failure — occurred less than 8 hours ago	Check the last 2 RCM traces: both normal → no further action. Traces unavailable → apply Reg 3.5 for the next 2 trains.	L1 on 2 good traces; otherwise per classification
1.6	Late-reported failure — more than 8 hours ago, TC continuously occupied since, 2 normal traces	Classify Negligible and close.	L1 — closed
1.7	Wheelset contamination suspected as cause	Arrange wheelset checks of the train involved within 30 minutes of the SCWO; record findings on the CCIL entry.	Supports classification — per App D
1.8	Overlay AHB level-crossing TC — RCM alarm	NO Reg 3.5. Check the crossing operating sequence via the data logger; FMS classified Negligible.	L1
1.9	Rusty rails on a little-used line or loop	Apply TS11 special block arrangements (Appendix E rusty-rail areas: Newstead loop, Wetmore, Cricklewood, Nadins GF, Leicester P4, Uttoxeter Loop, Leicester North Jct).	n/a — TS11 in force
1.10	SCWO while Reg 3.5 special working is already in force	Classify Negligible — protection is already in place. Record and continue to monitor.	L1
1.11	SCWO during a TS11 special block	Rated N0 — no additional action beyond the block; record on FMS.	L1

Sign-back levels (Appendix D)

Failure	Fault found	No fault found
High — signal / interlocking / level-crossing failure	L3	L3
High — railhead contamination, unprotected	L2	L3
Low — indication-only circuit	L2	L2
Low — RCM blip under 300ms	L1	L2
Negligible — sequencing controls effective	L1	L2
Negligible — special block in force	L1	L1

L2/L3 closure requires the SFI report, independent inspection RCM traces and an interlocking data-logger extract. Sign-back at Level 2/3 may be granted on RCM evidence without site attendance.

Restoration of normal working

Remove Reg 3.5 after an RHTT pass — reinstate at the end of the day.
Remove special working after 3 consecutive trains operate the TC correctly with good RCM traces.
Re-implement Reg 3.5 when a red or black adhesion forecast is issued.
Sites without RCM require a joint end-of-season inspection with MOM photographic evidence before final removal.

Withdrawal of special working

Photographs of the railhead from 2–3 points plus a line-of-view shot.
Evidence sent to the Route Control Manager and DU S&T for agreement.
Withdrawal form submitted to the NOC.
Change circulated via the daily record of special working (Appendix K) and the 18:00 Autumn Log.

Grouping of TC failures

Failures may be grouped under one SFI pack when they share the same line, the same interlocking area and the same geographic section.
Maximum one grouped pack per area per year.

Retrospective RCM alarms (8-hour rule)

Reported less than 8 hours after occurrence: check the last 2 RCM traces; if unavailable apply Reg 3.5 for the next 2 trains.
Reported more than 8 hours after occurrence with continuous occupation since and 2 normal traces: classify Negligible and close.

Wheelset checks (30-minute rule)

Wheelset checks of the train involved must be carried out within 30 minutes of the SCWO.
Findings (wheelset contaminated yes/no, TCA fitted/working, sander fitted/working/used) are recorded on the WSTCF CCIL entry.