Wayside Maintenance Monitoring System

WMMS™ is the reference implementation of RWTS™, from the author of the standard itself.

Request a demonstration

Your Hardware. Our Software.

Deploy on standard x86 or ARM industrial computers. No proprietary black boxes. Use your preferred vendors, your existing infrastructure, your procurement process.

Non-Vital Platform, Read-Only Interface

The Wayside Maintenance Monitoring System is a non-vital platform. It observes equipment health and generates maintenance alerts. It is not part of the vital chain, it does not control train movements, and nothing it produces can affect a signal aspect or a route.

It does monitor vital equipment — vital logic controllers, vital relays, and track circuits among them — and it does so read-only. Pollers issue diagnostic queries only. They cannot write configuration, modify device settings, or trigger actions, and deployments use a dedicated least-privilege account so the monitoring path cannot become a control path.

The boundary is set by the standard, not just by our implementation. RWTS defines no vital device-actuation commands. Its server-to-device messages are limited to housekeeping — firmware updates, maintenance windows, sleep, commissioning, and registration revocation.

How It Fits Together

Wayside Maintenance Monitoring System architecture Wayside Sentinel runs at each wayside location and polls local equipment — grade crossings, signals, switches, detectors and power systems — read-only. It has two parallel outputs over MQTT or SNMP. The first carries RWTS in its compact wire format to two optional central components, Wayside Overwatch, the dispatch-side fleet dashboard, and Wayside Nexus, long-term time-series storage. The second carries RWTS Expanded, the same messages with human-readable keys, to existing SCADA systems, historians and dashboards that do not implement the protocol. AT THE WAYSIDE EDGE CENTRAL — OPTIONAL Grade crossings Signals Switches Detectors Power systems polls read-only CORE Wayside Sentinel Runs at each location Alarms · local storage Works standalone compact compact RWTS™ MQTT / SNMPv3 RWTS™ Expanded MQTT / SNMP Wayside Overwatch Dispatch dashboard Fleet in one view Wayside Nexus Long-term storage Analytics-ready Existing systems SCADA · historians dashboards · MQTT / SNMP
Sentinel is the only required component. Overwatch and Nexus are optional and attach to an existing Sentinel fleet. In parallel, Sentinel emits RWTS Expanded, the human-readable form of the same messages, so existing MQTT and SNMP consumers ingest wayside data without implementing the protocol. Polling of wayside equipment is read-only throughout — the platform observes and reports, it never commands.
Standalone

Wayside Sentinel

Edge Software for Wayside Locations

Wayside Sentinel runs at wayside locations — polling equipment, evaluating alarm rules, storing data locally, and communicating in RWTS. Works independently; connects to Overwatch and Nexus for centralized capabilities, or feeds the monitoring systems you already run.

  • Continuous equipment polling with configurable alarm thresholds
  • Local data storage with configurable retention
  • Offline operation with store-and-forward during outages
  • Legacy protocol support — ingests SNMP, Modbus, and serial from existing equipment and delivers RWTS-formatted messages upstream
  • Two outputs in parallel — RWTS compact to Overwatch and Nexus, and RWTS Expanded, the same messages with human-readable keys, to your existing SCADA, historians, and dashboards over MQTT or SNMP. Nothing to replace

Ask about Wayside Sentinel

Complements Sentinel

Wayside Overwatch

Dispatch-Side Dashboard

Wayside Overwatch is the dispatch-side dashboard. It receives telemetry and alarms from Sentinel deployments and presents the fleet in one view.

Ask about Wayside Overwatch

Complements Sentinel

Wayside Nexus

Centralized Metrics Collection

Wayside Nexus aggregates telemetry from your entire Sentinel fleet and stores it long-term — the data foundation that predictive-maintenance, trend-analysis, and historical-reporting tools build on. Nexus collects and stores; you bring or integrate your analytics layer.

  • Fleet-wide aggregation with 365-day retention
  • Time-series storage — every metric, every device, queryable
  • Analytics-ready — designed to feed predictive maintenance, trend analysis, and reporting workflows
  • Data export — CSV, JSON, and API access for downstream tools

Ask about Wayside Nexus

Deployment Sizing

Deployments scale to the railroad's size and operational requirements.

Short Lines

Single edge device per location. Sentinel-only, feeding the dashboards you already have via RWTS Expanded.

Regional Railroads

Distributed edge with centralized Overwatch.

Class I Railroads

Full fleet with Nexus aggregation. Enterprise integration.

Ready to Explore?

Tell us about your current monitoring setup, fleet size, and operational challenges. We'll recommend a deployment approach that fits.

Discuss a deployment