Railroad Wayside Telemetry Standard™

The open IoT standard that unifies wayside equipment data across every vendor. Openly licensed — free to implement, in any product.

v1.0.0 — pre-release as of September 2026. Specification, GitHub repository, and Python reference library release together — join the waitlist.

What is RWTS™?

RWTS is the open IoT standard for railroad wayside equipment. It unifies grade crossings, signals, switches, detectors, and power systems under one common language, regardless of vendor — defining not just the message format but device behavior, transport requirements, and conformance profiles.

Historically, wayside monitoring meant vendor lock-in: each manufacturer's equipment speaks its own protocol, so multi-vendor deployments require custom translation at every seam. RWTS closes that gap with a single open contract any vendor can implement.

Key Features

  • 800+ standard alarm codes spanning 100+ equipment families — consistent semantics across vendors, with defined room for vendor-specific and custom codes
  • 10 message types covering registration, heartbeat, telemetry, alarm lifecycle (raise / clear / acknowledge), configuration, and server commands
  • Transport flexible — runs over MQTT, SNMPv3, or both at once for redundancy
  • Four conformance profiles — every device declares which one it implements, so mixed fleets interoperate without special cases
  • Self-describing devices — plug-and-play with zero pre-configuration
  • RWTS Expanded — a defined, lossless human-readable form of every message, so SCADA systems, historians, and dashboards that don't implement RWTS can still ingest it
  • Geographic addressing — milepost-based (MARK-SUB-MP-HOUSE-UNIT)
  • Efficient encoding — CBOR binary by default, roughly half the bandwidth of JSON, with JSON available for debugging

Figures describe RWTS v1.0.0, currently in pre-release and in final development. Counts may grow before public release; the transports, addressing scheme, and security baseline are settled. Last checked against the specification September 2026.

Technical Specification

Devices are identified by a milepost-based address — reporting mark, subdivision, milepost, house, unit — so every message ties to a physical location on the railroad. Messages travel over MQTT, secured with TLS 1.2+, or SNMPv3 in authPriv mode, and carry UTC timestamps with sequence numbers for integrity.

The standard ships in two volumes: a normative volume that implementations must conform to, and an informative companion covering implementation guidance and worked examples.

How RWTS aligns with AREMA Part 24.2.1

Adopting RWTS

For Railroads

Deploy the Wayside Maintenance Monitoring System, the reference implementation of RWTS. Sentinel runs at each location; Overwatch and Nexus are optional.

View WMMS

For Equipment Vendors

Implement RWTS in your devices to offer interoperability to railroad customers. Free to implement, including in proprietary firmware, with no fees. State the version and profile you implement, so integrators know what they are getting.

Discuss implementation

For Developers

Build from the specification, or start with our Python reference library — pure standard library, zero dependencies. AGPL-3.0-only, commercial licensing available.

Join the RWTS waitlist

Need something the standard doesn’t cover yet? Propose a change.

FAQ

How is RWTS licensed?

The specification is published under Creative Commons Attribution 3.0. Read it, implement it, redistribute it, translate it. Redistributing or adapting the document itself requires credit to EPU Engineering; implementing the standard in your own product requires nothing at all, no fee and no agreement. The Python reference library is licensed separately under AGPL-3.0-only, with commercial licensing available. You never need the library to implement RWTS.

I ship proprietary firmware. Can I implement RWTS?

Yes, with no fees and no obligation to us. The specification is openly licensed, so you can implement RWTS in closed-source firmware directly from the document. Only our Python reference library carries copyleft. If you would rather build on that library than write your own implementation, and you need to keep your firmware proprietary, contact us for a commercial license.

What if EPU Engineering goes out of business?

The Creative Commons grant on the specification is irrevocable, so the standard remains freely available regardless. Any implementation built on RWTS v1.0 will continue to work. The standard is designed to outlive any single company.

Is RWTS production-ready?

RWTS v1.0.0 is in pre-release as of September 2026. The specification is written and the reference library is implemented and under test. EPU's Wayside Sentinel, Overwatch, and Nexus together form the reference implementation. Join the waitlist to get the spec and reference library on public release.

Can I use the RWTS name for my product?

Railroad Wayside Telemetry Standard and RWTS are trademarks of EPU Engineering LLC. You may describe your product as RWTS-compatible, or as supporting RWTS, if it genuinely implements the specification, and you should state the version and profile it implements. An RWTS certification program is in development and not yet available. Until it launches, conformance is self-declared and no product, including ours, is certified. Contact us with questions about trademark usage.

Do I have to replace my existing monitoring systems?

No. RWTS defines an expanded representation: every message in a human-readable form with the same meaning, convertible back to the wire format without loss. Wayside Sentinel emits it in parallel with the compact wire format, so SCADA systems, historians, and dashboards that already speak MQTT or SNMP ingest wayside data without implementing the protocol.

Be First to Get RWTS™

Join the RWTS waitlist