TA
TRAFFIC AUTHORITY
PROGRAM · SENSOR PARTNERS   CLASSIFICATION · PUBLIC
LiDAR & Sensor Channel Partners

Your sensors work.
DOT backends don't speak their language.
We translate.

Seven production translators between modern LiDAR data and the legacy ATMS protocols state DOTs actually run — TxDOT Z1 binary, FDOT SunGuide, NTTA wrong-way, CFX, MDX, NTCIP 1209, Wavetronix HD emulation. Deployed at the edge, byte-level verified, ready to plug into your next bid.

7 PROTOCOLS PRODUCTION-READY
TXDOT TRANSLATOR LIVE IN FIELD
AIR-GAPPED EDGE DEPLOYMENT
2–4 WK NEW-PROTOCOL TURNAROUND
The Problem Everyone Knows About

Every modern sensor deployment hits the same wall.

LiDAR produces rich, modern data — JSON, point clouds, real-time telemetry. The DOT infrastructure it deploys into speaks protocols designed decades ago: Z1 binary, SunGuide XML, NTCIP 1209, Wavetronix serial. Without translation, the data never reaches the ATMS. Deployments stall. Hardware sits in boxes. Bids get scored down on integration risk.

This isn't one vendor's problem. It's the industry's problem — and it shows up in every legacy DOT deployment, in every territory.

300K+
US signalized intersections
Majority running legacy detection protocols
50+
State DOTs with legacy ATMS
Each with different protocol requirements
$14.8M
El Paso LiDAR project alone
48 intersections — protocol translation required
How It Works

The translation path. Four stages, one edge box.

From sensor output to TMC-native protocol in under 100 milliseconds — entirely at the deployment site. No cloud hop, no middleware on the DOT network, no changes to the backend.

STAGE 01
Sensor Output
LiDAR emits modern data — JSON events, object lists, real-time telemetry — exactly as the manufacturer designed it. No firmware changes, no custom sensor config.
IN · JSON / TCP / UDP STREAM
STAGE 02
Edge Translator
Docker container on the site's edge processor decodes the stream and maps detections to the target protocol's data model. Config cryptographically signed and hardware-locked.
XLT MODULE · AIR-GAPPED
STAGE 03
Protocol Stream
Encoder emits a byte-perfect legacy stream — Z1 binary frames, SunGuide XML, NTCIP 1209 objects, or Wavetronix HD serial — verified against protocol spec to the byte.
OUT · TARGET PROTOCOL, NATIVE FRAMING
STAGE 04
TMC Accepts as Native
The ATMS polls and receives exactly what it expects from a legacy device. Zero backend changes, zero DOT-side software, zero network policy exceptions.
TMC-NATIVE · NO BACKEND CHANGES
FIELD STREAM → EDGE → TMC  ·  END-TO-END LATENCY <100MS  ·  SAME PATH, EVERY PROTOCOL — ONLY THE ENCODER MODULE CHANGES
Translator Library — Current Status

Seven translators. Production-ready today.

Each translator converts modern LiDAR sensor output into a byte-perfect legacy protocol stream the target DOT backend accepts as native. LIVE means deployed and operating in the field. PRODUCTION-READY means complete, verified against protocol spec, and deployable on award.

XLT-001
Z1 HD Binary
TxDOT ATMS — freeway + intersection detection, SWRI polling
LIVE
XLT-042
Wavetronix HD
Sensor emulation — LiDAR presents to existing backends as Wavetronix HD radar. Dominant install base across Western US
LIVE
XLT-002
SunGuide XML
FDOT statewide ATMS — detection + event data into SunGuide
PRODUCTION-READY
XLT-015
NTTA Wrong-Way
NTTA wrong-way driver backend — pairs with any WWD detection device for full backend integration
PRODUCTION-READY
XLT-018
CFX
Central Florida Expressway Authority backend integration
PRODUCTION-READY
XLT-019
MDX
Greater Miami Expressway Agency backend integration
PRODUCTION-READY
XLT-026
NTCIP 1209
Standard transportation sensor objects — universal across modern ATMS, any territory
PRODUCTION-READY
NEED A PROTOCOL NOT LISTED?
50 legacy protocol targets catalogued and prioritized. New output encoder: typically 2–4 weeks. Edge deployment, config signing, and monitoring infrastructure are shared across every translator.
Channel Partner Territory Coverage

What's ready in your territory, right now.

Translators mapped to the territories where channel partners sell. If you hold a territory, the protocols below are the ones your DOT customers already run — and the ones your bids get scored on.

Partner Profile
Ready Translators
What It Unlocks
FL / TN +
WWD National
FLORIDA & TENNESSEE TERRITORY · NATIONAL WRONG-WAY COVERAGE
5 READY: SunGuide XML · CFX · MDX · NTTA Wrong-Way · NTCIP 1209
Full Florida backend coverage on day one. Your WWD detection hardware plus our backend translation = complete wrong-way solution in any state.
Western US
WESTERN STATES TERRITORY
2 READY: Wavetronix HD emulation · NTCIP 1209
Wavetronix HD is the dominant legacy install base in the West — LiDAR that presents as Wavetronix drops into existing backends with zero DOT-side changes.
Any Partner
ANY TERRITORY · ANY MODERN ATMS
UNIVERSAL: NTCIP 1209
The standards-based path. Anywhere a modern ATMS accepts NTCIP sensor objects, LiDAR data flows in without custom work.
Market Position

The sensor platforms that get here first win the DOT market.

Every LiDAR, radar, and video analytics company eventually needs protocol translation for DOT deployments. The question is which platforms and which channel partners get it first. The head start compounds — more deployments means more protocol coverage, more edge cases solved, more DOT acceptance data behind your next bid.

Approach
Protocol Translation
Bid Impact
Partner with Traffic Authority
7 production translators
Integration risk pre-answered
In-house per deployment
Ad-hoc, per project
Months of NRE per protocol, per bid
Wait for DOT modernization
None
Deals lost to legacy-compatible bids
The only production translator library covering TxDOT, FDOT, NTTA, CFX, MDX, NTCIP, and Wavetronix emulation in one platform.
Everyone else is solving this ad-hoc, per deployment, at their own expense — or losing the deal.
Deployment Model

At the edge. Air-gapped. Verified to the byte.

The translation engine runs in Docker on the edge processor at the deployment site. No cloud dependency, no internet requirement — DOT network policies stay intact. Configs are cryptographically signed and hardware-locked per site.

<100MS
Translation latency
Real-time at the edge
100%
Protocol accuracy
Byte-level verified output
0
Internet required
Fully air-gapped operation
99.5%
Uptime tested
7-day unattended bench test
HW
Config locked
Cryptographically signed per site
2–4 WK
New protocol
One encoder module, shared platform
Partnership

Every translator deployed means more sensors sold in your territory.

We don't sell sensors and we don't bid against you. We make your hardware land in legacy backends — so your bids carry less integration risk and your deployments don't stall after award.

Value to You
+Removes the #1 deployment barrier in legacy DOT environments
+Territory-matched translators ready before your next bid cycle
+Your sales team can say "backend integration is handled"
+Every translated deployment = more sensor units moved
+Hardware stays yours — we are software and integration only
+No cost to evaluate, no engineering resources required from you
What We're Asking
→A 15-minute technical walkthrough of the translator library
→Referral when your deployments hit the protocol barrier
→Inclusion in bids where backend integration is scored
→Protocol documentation access for new translator development
No funding requested. No revenue share required to start. No engineering lift on your side. You sell hardware; we make it land in the backend your customer already runs.
Start the Conversation

Tell us your territory. We'll show you what's ready.

Name, company, and what you're deploying into — we'll come back with the territory-matched translator list and a 15-minute walkthrough slot.

The protocol barrier is solved.
Let's put it behind your next bid.

15-minute demo — watch live LiDAR data translate to a legacy DOT protocol stream in real time.

Schedule a Demo Ask About a Protocol
TRAFFIC AUTHORITY · traffic-authority.com
PROGRAM · SENSOR PARTNERS · MAIN SITE