When a lane misbehaves, a reader drifts, a host queue backs up or the vendor answers only on request, toll agencies and their operators call ITS Roads. We troubleshoot, find temporary and permanent fixes, carry the overload, reverse-engineer what was never documented, and put your current and legacy systems under real-time monitoring so you are in the know.
Nearly every new U.S. toll facility since 2010 is cashless, and more than half the country's tolled miles have no cash option[1]. That makes the roadside electronics, the hosts and the back office the revenue system itself. When something in that chain degrades, revenue leaks, violations pile up, and customer service hears about it first.
ITS Roads is an engineering firm, not a toll system integrator. We work for the agency, under the agency's direction, alongside whichever integrator built the system. Our engineers have designed, built, commissioned and maintained open road tolling, express lanes, plazas and hosts for Florida's Turnpike, the New Jersey Turnpike and Port Authority crossings, Bay Area bridges, Maryland's violation enforcement system and Southern California express lanes. We bring that bench to your lanes, remotely within hours and on site nationwide.
Each of these has a quick containment and a durable fix. We do both and tell you which is which.
Intermittent reads, cross-lane reads, protocol transitions (6B or Title 21 to 6C, adding TDM for E-ZPass reciprocity), RF tuning, cable and connector degradation, read rates slipping below the 99.95 percent agencies specify[5].
Image capture rate, focus and exposure drift, illuminator failure, trigger timing, OCR confidence trends and the image-review backlog they create. We measure before and after so the improvement is on the record.
Loops aging under heavy truck volumes, splashover and pulse break-up, treadle and profiler faults, detector-versus-reader count mismatches that turn into misclassified transactions and disputed bills[19].
Unsupported operating systems and industrial PCs, database bloat, stuck queues, time-sync drift between lane, host and back office, interface changes that silently broke a file transfer.
Reconciliation gaps, tag-validation-list and transaction-file exchange failures with the E-ZPass, Southeast, CUSIOP and CTOC hubs, NIOP ICD conformance, functions that were never turned on after a migration[9].
Hover or tap a number. Open road tolling fuses tag reads, vehicle detection, classification and images into one transaction in the lane controller, then hands it to the host, the back office and the interoperability hub.
Multi-protocol readers for ISO 18000-63 (6C), TDM/IAG, SeGo and legacy 6B; antenna footprint, lane discrimination, RF power and tuning, OmniAir-certified equipment[12].
Front and rear capture, infrared illumination, trigger timing, OCR and image quality for video tolling and violation processing.
Laser and LiDAR profilers, 3D scanners and overhead detectors that separate vehicles and establish class and axle count at highway speed.
Presence and axle detection whose life is set by truck volume and pavement condition; the most common root cause of classification disputes[19].
Industrial PCs, I/O controllers, UPS, surge protection, environmental sensors, managed switches; where every event becomes a transaction, and where legacy obsolescence shows up first[6].
Fiber, cellular and LAN links, VPNs and time synchronization between lane, plaza and host; the layer we monitor with SNMP, ISO 15784-2 and NTCIP objects[14].
Transaction processing, image review, account management, violation and pay-by-plate billing, reconciliation and reporting; where migrations and cutovers go wrong[11].
Tag validation lists and transaction files exchanged with E-ZPass, the Southeast, CUSIOP and CTOC hubs under the IBTTA NIOP ICD v2.1[2].
Most agencies run a sensible model: in-house technicians do first-level swaps and preventive maintenance, and the system vendor supplements on request[7]. The model breaks when the queue outgrows the crew, when a fault needs a protocol analyzer rather than a spare, or when the vendor's response time is measured in weeks.
ITS Roads plugs into that model without changing it. We take the tickets your team cannot close: remote triage over your secure access, root-cause analysis, bench reproduction in our lab, a written containment step and a permanent fix with the evidence behind it. For recurring support we pre-stage spares, maintain the as-built documentation and track everything in your maintenance management system to the acknowledgement and resolution times in your contracts[20].
Toll electronics are specified for roughly ten years of service[5], and replacement programs routinely slip for years[8]. The result is lanes running on unsupported operating systems, proprietary serial protocols nobody documented, and vendors that no longer exist under the same name. The agency still owes its customers an accurate bill every day.
We capture the traffic on the wire, reconstruct the message formats and state machines, bench the component where we can, and write the documentation you were never given. From there we can specify a drop-in replacement, build an adapter, or simply keep the subsystem alive and watched until the new system is accepted. When the replacement arrives, that documentation becomes your interface control reference and your acceptance-test baseline.
Most toll systems report on themselves only through the integrator's maintenance console. We add an independent, vendor-neutral layer on top of your current and legacy systems using state-of-the-art open-source and commercial enterprise monitoring platforms: non-invasive collectors inside your network, outbound-only encrypted links, dashboards for operations and management, and monthly reports keyed to the KPIs in your contracts.
Where a device speaks SNMP we use it, with ISO 15784-2 and NTCIP objects for power, environmental and network equipment[14]. Where a lane controller or back office does not, we read syslog, vendor APIs, read-only database views and transaction files, and derive the health indicators that matter: read rate by protocol, image capture rate, detector-versus-reader mismatch, queue depth, hub exchange status and time offset.
Interactive: click a node to expand or collapse.
Every facility has its own vendors, protocols and history. The engineering problems repeat. Reference photographs of U.S. facilities, credited below each.
Describe the symptom, the lane and what has been tried. Same-business-day engineering response.
Over your secure access we read logs, counters and configurations and reproduce the fault where possible.
A documented temporary fix that stops the revenue leak or restores the lane while the root cause is confirmed.
Bench reproduction in our lab, protocol capture, vendor engagement on your behalf, and a written finding.
Replacement, adapter, configuration or procedure change, tested and installed under your change control.
The subsystem goes under watch so the next deviation is caught before it becomes a complaint.
ISO 18000-63 (6C) and the 6C Toll Operators Coalition, TDM and IAG for E-ZPass reciprocity, SeGo, legacy ISO 18000-6B and Title 21, ASTM E2158 physical layer[16], OmniAir certification for 6C, 6B-80K and TDM[12].
Cabinets pre-assembled in our lab, a proof-of-concept operational in under 45 days, 280 qualification test scenarios with zero errors, then lane and plaza host deployment and industrial I/O conversion.
Project summary
Roadside and 99.999 percent availability host design, site surveys and multi-vendor equipment selection for OCTA, RCTC and SANDAG facilities, approved on first review.
Project summary
An independent camera-vision count and classification running 24/7 against the toll system, and roadside consulting on the authority's replacement toll system procurement.
Project summaryDesign-side services for new systems, from requirements and RFP packages to host architecture and acceptance testing, are described under tolling engineering support.
Yes. Roadside toll readers are typically specified with a ten-year design life, and agencies have reported lane computers and software that were no longer supported within nine years of installation. We keep those lanes running, document what was never documented, add monitoring so you can see them, and plan the path to replacement on your schedule rather than a vendor's.
Yes. Agency technicians doing first-level swaps while the system vendor supplements per request is a common model. ITS Roads provides overflow engineering for the faults that are beyond your team's tools or training: remotely first, then on site, under your direction and your change-control process.
ISO 18000-63 (6C), TDM and IAG (E-ZPass), SeGo and legacy ISO 18000-6B readers and antennas; license-plate recognition cameras and illuminators; inductive loops, treadles, laser and LiDAR profilers and overhead vehicle detection; lane and zone controllers; plaza and roadside hosts; back-office interfaces; cabinet power, UPS and surge protection; and the fiber, cellular and LAN networks that tie them together.
Yes. We capture serial and network traffic, reconstruct message formats and state machines, bench the component in our lab where possible, and produce the documentation you were never given, so the fault can be diagnosed, the subsystem can be monitored, and a permanent fix or replacement can be specified.
Lane and zone status, reader health and read rate by protocol, camera and illuminator health and image-capture rate, detector-versus-reader count mismatches, host and back-office queue depth, interoperability file exchanges, UPS and battery state, cabinet temperature and door, network links and time-sync offset. We collect with SNMP, syslog, vendor APIs and read-only database views, and report against the KPIs in your contract.
We work alongside your system integrator under your direction. We use non-invasive diagnostics first, record every finding and change, and keep warranty and KPI responsibilities clear in writing before we touch production equipment.
Yes. Tag-validation-list and transaction-file exchange failures, reconciliation mismatches, reader certification and protocol-transition issues are engineering problems we have worked on both sides of, aligned to the IBTTA NIOP interface control document and the OmniAir certification programs.
Yes. Segmentation and DMZ isolation for vendor remote access, hardened monitoring collectors, NIST Cybersecurity Framework alignment following FHWA's transportation management center guidance, and PCI DSS considerations where payment data is handled.
Our engineering lab and network operations center are in Northern Virginia, nine miles from Washington, DC. Remote triage normally begins the same business day. For on-site work we travel nationwide, and for recurring support we pre-stage spares and remote access so most issues never require a truck roll.
Call (703) 375-9990 or send the symptom. An engineer, not a sales desk, will respond.
