The integration layer between SIMPL-Highway and every state DOT
Built, validated, and ready to ship inside your deployments. Two ways to put it to work — neither asks you to write a line of protocol code.
The gap
SIMPL wins at the intersection. The gap is the freeway.
SIMPL-Intersection is solved — native TS2 actuation, proven at Peachtree Corners, Columbia County, Chattanooga. That's your product and it works.
SIMPL-Highway is different. The moment corridor data has to reach a centralized state DOT freeway TMC, there's a wall: SIMPL speaks clean JSON, and the TMC speaks a proprietary 1990s protocol.
That wall is the only thing standing between SIMPL-Highway and the statewide freeway deals.
The protocol wall
Every state speaks a different language
Texas — TxDOT
TransVISION · Z1 HD binary
Florida — FDOT
SunGuide · XML
California
CalTrans · PeMS
Georgia — GDOT
NaviGAtor
SIMPL-Highway outputs JSON over TCP — stopped vehicle, wrong-way, debris, pedestrian, speed deviation, lane violation. Six clean event types. None of it lands in the TMC without translation. And today, there is no commercial product that does this for any state. Every deployment is custom engineering, from scratch, every time.
How it gets done today
Right now, your integrators pay for this twice — and don't see it
When a DOT adopts new detection hardware, the integration falls to the state's General Engineering Consultant — HNTB, Kimley-Horn, Jacobs, Atkins — who writes custom code under their standing labor contract.
200–400 hours
Billable consulting hours per freeway integration. Redone from scratch every time a new sensor class shows up. Buried inside engineering hours, invisible as a line item — but it's real money, and it's slow.
That's the friction quietly capping how fast SIMPL-Highway can spread across state networks.
What we built
We turned 300 hours of consulting into a product
The translation layer is built and live. Not a concept — validated with your engineering team.
Binary protocol decode + translation engine — Z1 HD and RTMS G4 done, poll/response and push modes.
Runs edge-local on the EP1, containerized — no change to your data model, no writeback.
SIMPL stream integration, already validated.
Seven translators production-ready today; 50+ protocols cataloged across every state DOT and toll authority.
New protocols build in days, not weeks — because the hard part, the decode-and-validate foundation, is already done.
How it sits in your stack
One container on the EP1 you already ship
the layer we add your existing Seyond stack
No new hardware, no cloud dependency, no change to the sensor or the data model. The translator deploys as a container on the EP1 that's already in the field — reads the SIMPL stream, speaks the TMC's language out the other side.
Scope
Sensor-data-only. One direction. Clean.
This layer reads from the sensor and sends to the operations center. That's it.
What it touches — and what it never does
In scope
Classifications & counts
Wrong-way & incident events
Camera slew-to-cue
Plate-read events
Sensor → TMC, one direction
Out of scope
Transaction ledgers
Customer accounts & billing
Fare / payment reconciliation
Any writeback to the field
PCI / SOC2 audit surface
A clean integration that stays out of everyone's compliance burden.
The strategic question
You never wanted to build this. You don't have to.
The translation gap gets solved either way. The only question is who owns the relationship when it does — and how it reaches your integrators.
There are two ways this works for Seyond. Neither asks you to write a line of protocol code.
Two paths
Embed it, or license it per deployment
Path One
Built into SIMPL
Translation becomes a standard capability of SIMPL-Highway. It ships talking to any state DOT, out of the box. You license the translators from us and fold them into the SIMPL package your resellers already sell.
SIMPL-Highway becomes the turnkey freeway product
Closes the statewide deals the protocol wall is slowing
Differentiates against every platform that still can't reach the TMC
Path Two
Per-deployment license
Or don't embed anything. When an integrator wins a corridor and needs the layer, they license it for that project — a known, fixed cost, sized to the deployment.
One published rate card, same terms for every integrator
Volume is the only lever — commit more, the rate drops
No commitment from Seyond, no bundling, no platform change
The natural path
Per-project proves it. Embed scales it.
Most partnerships start per-project — an integrator hits the wall on a live corridor, licenses the layer, it works. Once the pattern proves out across a few deployments, embedding becomes the obvious next step.
Low-commitment entry. Natural path to standard. Seyond's choice at every stage — and the same translation layer underneath either way.
The channel
One layer, every reseller
The translation layer is channel-neutral. It works identically for every Seyond reseller, in every territory:
Texas / Gulf
corridors
Florida / Southeast
SunGuide ready
Western US
CalTrans PeMS in build
Embed it once at the SIMPL level, and every reseller in every region inherits a product that talks to their state's TMC. No reseller has to solve it alone. No deployment stalls on the protocol wall.
Proof point
Texas is the proof
The TxDOT Z1 HD translator — the hardest binary format in the country — is built and ready. A Fort Worth corridor is the live proof point: real sensors, real gantries, real TMC, built and ready for validation.
7 ready · 50+ cataloged
Once it's proven on Texas freeway, the same foundation flows to every other state in the catalog. The catalog isn't a wishlist — it's a build queue with the hard part already finished.
The conversation has changed
It's no longer "can SIMPL-Highway reach the state TMC." It's built. It's validated. It works.
Now it's just: which corridor proves it first — and do we ship it inside SIMPL, or per project.