Florida's authorities are racing to wrong-way coverage on every exit ramp in the state. The detector catches the driver. Getting that event into SunGuide — native, supported, with no custom integration — is the wall every deployment hits. We've turned that wall into a product. Token-based, one-time per detection point. Unlimited events.
Three authorities — the Turnpike, the Central Florida Expressway, and the FDOT districts — are all expanding at once, and the next generation of detection is moving from radar to LiDAR. Every one of those new detection points has to report into a Regional Transportation Management Center. That's where we come in.
SunGuide is Florida's statewide traffic management software, running across the FDOT districts and toll authorities. It accepts a new device only through a formal integration process — the device speaks a supported protocol, or someone writes custom code to make it fit. A wrong-way event that can't speak SunGuide doesn't reach the operators.
It takes the wrong-way event off the edge device and delivers it into SunGuide as a supported message — operator alarm, DMS trigger, FHP notification. The detector keeps doing what it does; we make the center hear it.
Here's exactly how a wrong-way corridor goes from procurement to live events in SunGuide. No mystery, no open-ended engineering — a known path with known timing.
A district, the Turnpike, or an expressway authority has ramps to cover and a procurement or task order that requires detection reporting to the RTMC. You're bidding it, or you already hold the contract.
Before you submit, we give you the fixed token cost to get your detection events into SunGuide. The SunGuide translator is already built — so it's an activation, not a research project. You carry a known, defensible number in your bid.
You win. No 200–400 consulting hours hiding in the integration line, because the integration is a product, not a custom build. Your margin is protected and your schedule is real.
We load the SunGuide translator onto the edge device at each detection point, map it to your RTMC and corridor, and validate the event types — wrong-way, incident, camera cue — against SunGuide's interface. Two days, because the hard part, the protocol decode, is already finished.
Events flow to the RTMC: operator alarm, DMS trigger, Florida Highway Patrol notification — with the low false-alert behavior the district expects. Clears the SunGuide device-integration check.
Your wrong-way events are native in SunGuide. The next corridor — and the next authority — reuses the same translator. Every deployment after the first is just an activation: faster, cheaper, already proven.
Token-based, one-time. Each detection point is a fixed token cost; the SunGuide translator is already built, so most Florida deployments are activations, not new-protocol builds. Volume lowers the rate. No per-event metering, no monthly.
| Token volume | Rate / token | Vs. list |
|---|---|---|
| 10,000 – 24,999 Single corridor of ramps | $0.95 | 5% |
| 25,000 – 49,999 District-wide wrong-way program | $0.92 | 8% |
| 50,000 – 149,999 Multi-district rollout | $0.90 | 10% |
| 150,000 – 499,999 Statewide program | $0.80 | 20% |
| 500,000+ National or OEM programs | $0.72 | 28% |
Start at 10,000 tokens. Buy more for a better rate, and stack purchases as you grow — two packs within 3 months combine and re-rate at the better tier.
The translator carries the detection event to the center. It never touches the financial or control layer.