Traffic Authority is the protocol translation platform that connects next-generation sensors to legacy state DOT traffic management systems. One integration point. Every state format. Fixed token pricing — volume moves the rate down.
You win DOT construction contracts. You deploy sensors, controllers, and communication networks. But when the state spec says "data shall be transmitted to the TMC in [state-specific format]" — that's where the project stalls. Your sensor manufacturer gives you JSON. The TMC expects Z1 HD binary, SunGuide XML, or NTCIP. Someone has to build the bridge. That's us.
Every state has its own TMC platform and its own data format. Building custom translation for each deployment means weeks of engineering, specialized talent you don't have on staff, and risk that your bid timeline slips. Most integrators either avoid LiDAR corridors entirely or inflate their bids to cover the unknown.
We've decoded the hard formats — TxDOT Z1 HD binary, FDOT SunGuide, NTCIP 1209 — and built a translation engine that converts sensor output into whatever the state TMC requires. Seven translators are production-ready today. New protocols take days, not months. You deploy, we translate.
Protocol translation becomes a fixed line item in your bid — 2,500 tokens per gantry, known in advance. No open-ended engineering. No specialist hires. You can bid LiDAR corridors you'd otherwise pass on, and your margins improve because the integration cost is predictable.
Your hardware is best-in-class. It captures better data, at higher resolution, than anything else on the market. But DOTs don't buy sensors — they buy systems that work with their TMC. If an integrator can't connect your sensor to the state platform without custom engineering, they'll specify the legacy vendor instead. You lose the deal not because your product is worse, but because it's harder to deploy.
Integrators love your specs in the demo. Then they look at the bid timeline and realize they need 6 weeks of custom protocol work to connect your sensor to TxDOT or FDOT. The legacy vendor with a native NTCIP output wins on deployment simplicity, not performance. You're losing deals on protocol, not product.
Bundle Traffic Authority translation with your hardware. When an integrator evaluates your product, protocol translation is solved — every state format, one integration point. Your sensor + our translation = a complete package that deploys as easily as the legacy competition. The integrator doesn't have to think about it.
Every state you couldn't sell into because of protocol becomes addressable. Your integrator partners deploy faster, which means they order more hardware. An annual OEM commitment at volume rates means the translation cost per sensor is negligible compared to your hardware margin.
You build highways. ITS integration is a line item in your scope — one you'd rather hand to someone who knows what they're doing. You need a fixed cost you can carry in your bid, a partner who delivers on schedule, and zero surprise change orders on the sensor integration piece.
You sub out the sensor integration, and the sub comes back with change orders because the state protocol was more complex than expected. Or you try to handle it internally and burn weeks of engineering time you needed elsewhere. Either way, the ITS line item bleeds into your margin.
2,500 tokens per sensor location. Known before you submit the bid. Protocol translation, activation, and deployment — all drawn from one token balance, one-time. You know the number, you carry it in your bid, and it doesn't change.
Your bid carries a precise ITS integration cost instead of a padded contingency. That makes you more competitive. And when the project is in execution, the sensor integration isn't on your critical path — we handle it on a timeline measured in days, not weeks.
You run the traffic management center. New sensor types are coming online — LiDAR, V2X, next-gen radar — and your platform doesn't speak their language. Rebuilding your TMC stack to ingest new formats is a multi-million-dollar, multi-year project. You need a translation layer that sits between the new sensors and your existing platform.
Your TMC was built for NTCIP devices and loop detectors. The state is deploying LiDAR sensors that output JSON, V2X systems with SAE J2735, and camera analytics with proprietary APIs. Each new sensor type is a custom integration project on a platform that wasn't designed for it.
We sit between the new sensors and your TMC. Sensor data comes in as-is, leaves as whatever your platform expects — NTCIP, TMDD, SunGuide XML, Z1 HD binary. Your platform doesn't change. You just start seeing new data types appear in your existing dashboards.
Instead of a $5M+ platform rebuild, you add a translation layer for a fraction of the cost. Every new sensor type the state deploys, you can ingest. Your operations contract becomes more valuable because you can handle any hardware the DOT throws at you — without asking for a change order.
Seven translators are production-ready today. New protocols take days, not months. The hard engineering — decoding proprietary binary formats, mapping state-specific XML schemas, building a universal translation engine — is done.
Your corridor probably runs one of these. If it doesn't, a new protocol build is 25,000 tokens and measured in days. We don't build on spec — new protocols are engineered on signed deals with mobilization paid. Testing happens on your corridor, with your sensors, on your infrastructure.
Integrator, OEM, prime, TMC operator — everyone buys from the same rate card. The more tokens you commit, the better the rate. That's it.
| Annual commitment | Rate / token | Savings |
|---|---|---|
| 10,000 – 24,999 Single corridor starter | $0.95 | 5% |
| 25,000 – 49,999 Small corridor + platform | $0.92 | 8% |
| 50,000 – 149,999 1 large or 2 medium corridors | $0.90 | 10% |
| 150,000 – 499,999 Multi-corridor regional | $0.80 | 20% |
| 500,000+ National or OEM programs | $0.72 | 28% |
Tokens don't expire. Want the next rate? Commit to the volume.
Every buyer uses the same rate table. Volume is the only variable. Here's what different deployments look like.
Z1 HD binary translator is ready. Activation is same-day.
Fixed line item in the bid. No change orders.
Volume unlocks the best rate. Translation cost <1% of hardware.
Fraction of a platform rebuild. Months instead of years.
Fixed costs per action. No variable metering.
| Action | Tokens |
|---|---|
| Deployment | |
| Corridor deployment Per gantry, one-time. 24-gantry corridor = 60,000 tokens. | 2,500 |
| Protocol engineering | |
| New protocol New state-format translator from scratch. | 25,000 |
| Protocol activation Activate existing translator for a new scope. | 2,500 |
| Advisory | |
| Advisory & pre-bid Spec review, bid architecture, technical advisory. | 250 /hr |
No RFP required. No six-month procurement cycle. Here's how it works.