Field-tested algorithms, alarm patterns, and operational practice for level crossing monitoring, IEC 61131-3 logic, and remote diagnostics. Written for asset managers, signalling engineers, and control-room operators.
What causes flasher faults, how to detect them remotely with a learning-based count-lamps algorithm, and the full alarm set.
Read guide → Level Crossing MonitoringHow warning time is calculated from approach and island detection, how to handle track circuits, predictors, and axle counters, and the alarm to raise when it falls short.
Read guide → Level Crossing MonitoringThe track fault alarms a monitoring system should raise on the approach and island, and how to handle shunting, predictors, axle counters, and track machines.
Read guide → Level Crossing MonitoringWhat batteries a level crossing has, how to monitor voltage and charger health remotely, and the alarms to raise across primary signalling, auxiliary, boom, and data logger banks.
Read guide → Points & Turnout MonitoringHow to read a point machine's drive-current signature remotely, trend throw time, detect obstructions and loss of correspondence, and use the data for machine-learning predictive maintenance.
Read guide → Level Crossing MonitoringMonitoring booms from the proving relays — out-of-sequence, boom-fault, and boom-delay alarms, the timing against the lights, plus boom lights, pedestrian gates, and optional motor current.
Read guide → Signalling Asset MonitoringHow axle counters fail and how they're reset — count discrepancies, wheel rock, head misalignment, EMC; conditional, unconditional, preparatory (sweep) and co-operative resets; and trending resets without touching the vital function.
Read guide → Architecture & IntegrationOPC UA, MQTT, Modbus and DNP3 for wayside data — where each fits, the cost of proprietary protocols and locked hardware, and why you define the interface and stay open to many transports.
Read guide → Connectivity & ArchitectureChoosing mobile-network bearers (4G/LTE Cat-1, LTE-M, NB-IoT, 5G, satellite), designing store-and-forward for intermittent links, realistic latency budgets, and the security posture — private APN, VPN, mutual TLS — that keeps a field SIM safe.
Read guide → Control Room & OperationsWhat an alarm flood is, the EEMUA 191 and ISA-18.2 benchmarks a healthy system is designed against, and the levers that pull a wide-area control room back under them — rationalisation, killing chattering alarms, and safe, engineered suppression.
Read guide → Control Room & OperationsDetecting a fault is the easy part — managing the alarm is the hard part. Priority by consequence, per-alarm attributes and setpoints, the ISA-18.2 / IEC 62682 alarm state model, and safe shelving and suppression, all on the non-vital monitoring overlay.
Read guide → Control Room & OperationsDetecting a fault is not the same as reaching the right person. On-call schedules, escalation chains that fire when nobody acknowledges, routing by criticality and area and time of day, a pluggable delivery layer (email, SMS, voice, webhook), acknowledge-back, and de-duplication and failover — all on the non-vital monitoring overlay.
Read guide → Control Room & OperationsThe live alarm list is a snapshot; the audit trail is the history. An immutable, append-only record of every alarm lifecycle transition — who acknowledged what and when — source-timestamped in UTC to millisecond resolution, correlated with sequence-of-events data, with configurable retention, controlled access and clean export.
Read guide → Diagnostics & Post-Incident AnalysisWhy the order of signalling events matters more than the events themselves — 1 ms time-tagging at the source, synchronising site clocks with GNSS, PTP and NTP, quality flags, and store-and-forward so the timeline survives a comms outage and stands up in an investigation.
Read guide → Security & ArchitectureHow to secure a signalling network the way IEC 62443 and CLC/TS 50701 intend — segmenting into zones and conduits, assigning security levels by consequence, one-way data diodes for telemetry, locked-down remote access, and bolting a monitoring overlay on as a read-only zone that adds no inbound path to the vital layer.
Read guide → Resilience & ArchitectureA monitoring overlay only earns its place while it is watching. Removing single points of failure — hot, warm and cold standby servers, dual-LAN and PRP/HSR (IEC 62439-3) network redundancy, redundant RTUs and N+1 power, store-and-forward buffering, and automatic failover without split-brain — plus how to prove the failover works before a real fault relies on it.
Read guide →IEC 61131-3 logic patterns for signalling.
