EventRecorderIQ: Modern Crossing Event Recording on the WSDMM

Tens of thousands of Siemens SEAR (Switching Event & Activation Recorder) units sit at highway-rail grade crossings across North America. The SEAR family — SEAR II, SEAR IIi inside the GCP 4000/5000, and the Ethernet-equipped Argus — is the event recorder a generation of signal maintainers grew up on. Crews know its terminology, analysts know its event formats, back offices run on the Siemens ATCS Office and GenATCS protocols it feeds, and decades of operational expertise are encoded in CDL (Custom Design Language) configuration libraries that define how each crossing reports itself. None of that institutional knowledge is going away — and none of it should. But the SEAR's connectivity model belongs to an earlier era: serial cables, a single radio uplink, no way to surface the device to anything modern at the wayside without bolting on extra equipment.

KB Signaling solved the wayside-platform half of that gap with the WSDMM, and opened the application half through the Certified Developer Program: focused, domain-specific software that brings third-party wayside devices into the WSDMM ecosystem without forcing railroads to replace what is already in the field. OEG answered that call with EventRecorderIQ, a WSDMM application that gives the Siemens SEAR a modern monitoring interface, modern data forwarding, and a path forward, without disturbing the SEAR itself or the back office it already reports to.

EventRecorderIQ is a WSDMM-native application that talks to the Siemens SEAR family — SEAR II (A80273), SEAR IIi (A80410), and Argus (A80311) — over the device's existing ASCII terminal interface, and presents the recorder's state, configuration, and activation history through a modern browser-based UI hosted on the WSDMM. Every supported SEAR variant is reached the way it was designed to be reached: an RS-232 link off the SEAR or its expansion module into the WSDMM, no hardware modifications to the recorder, no replacement of the radio uplink the railroad already depends on. The application parses the SEAR's Configuration Report directly, so site identification — site name, milepost, DOT number, ATCS address — and the full I/O channel map come into EventRecorderIQ as the SEAR already understands them.

The UI is built for the people who actually work crossings. A live crossing schematic shows the state of every digital input — XR1, BELL OUT, AGPK, BGDK, and the rest of the familiar SEAR tag set — alongside relay outputs and battery monitor channels. An activation history grid lets a maintainer drill into a specific event, see the inputs that participated and the timing across them, and step through a Gantt-style timeline of the surrounding window. Device health — WAG radio, VHF, iLOD, and the SEAR itself — is monitored continuously and surfaced in the same view, so a maintainer does not have to assemble the picture from three separate tools.

Behind the UI, EventRecorderIQ runs the event and alarm engine the SEAR's serial output alone cannot provide. Activations are classified using a three-tier detection algorithm — CDL-tagged XR channels first, environment-configured channels next, cascade inference last — so the same logic applies whether a site has a hand-tuned CDL library or a default configuration. Time-series data is recorded locally to SurrealDB and SQLite so the history survives reboots and back-office outages. When a back-office link is available, EventRecorderIQ forwards events, alarms, crossing state, GPIO, and device health over MQTT using the Sparkplug B specification — full lifecycle messaging (NBIRTH/DBIRTH/DDATA/DDEATH/NDEATH) — so a railroad's existing centralized monitoring platform ingests crossing data on the same standards-based path KB's ecosystem is built around.