A typical mid-size city spends six figures a year on manual tube counts and consultant retiming — for a plan that’s already out of date when it ships. Meanwhile, your ATSPM controllers are generating millions of detector events that nobody is using to decide tomorrow’s timing.
Recurring line item in DOT operations budgets. ATSPM cuts the data-collection portion; the manual-engineering portion still recurs.
Frequency depends on agency budget cycles, not a fixed schedule. Mid-cycle congestion waits until the next contract.
Plans sized to data that misses roughly 1 in 10 vehicles.
The pilot fits inside the data agreements DOT signal-ops teams already use. No new sensors, no new contracts, no controller writes. We return a packet your engineers can review, approve, modify, or reject — and decide if it’s worth a conversation.
The Optimization Engine proposes specific timing changes, each anchored to what current operations already do. The Agentic Auditor surfaces anomalies, blockers, and the questions data alone cannot answer. Both land in the same engineer queue with the audit trail already started — the engineer’s job is to accept, modify, block, or reject, not to assemble context from scratch.
DOT operations is an audit culture. Every retiming gets logged, defended, and replayed when something goes wrong — so a black-box recommendation cannot survive that workflow. The Agentic Auditor runs alongside the Optimization Engine to make every finding defendable from the moment it surfaces.
Reading the same ATSPM stream as the Optimization Engine, the Auditor surfaces hypotheses, rules out everything the event stream can rule out, and writes the question that remains — including who to ask, and what evidence to attach when you ask. The audit trail is already started by the time it reaches the engineer’s queue.
Recommended timing changes go through shadow evaluation before any deployment. No simulation, no interpolation, no autonomous writes to the controller. Full method below — open to audit.
Raw ATSPM event stream from one signalized intersection, agency-partner site. 28 consecutive days. ~1.7M events / week. EventCodes 0–82 retained; configuration parsed from controller export.
Advance-detector latency = distance / speed × 1.467. Pair EventCode 1→7 within a cycle window. Numerator = vehicles arriving during green; denominator = vehicles arriving total. No simulation, no interpolation.
Time from EventCode 89 (call) to EventCode 21 (walk). 26,702 samples over the window. Distribution reported as p50 / p90 to avoid mean-skew from long tails.
Pattern splits cross-checked against EventCode 31 history. NEMA dual-ring barrier-equal constraint verified per cycle. Anomaly threshold for “regime change”: ≥2× shift in per-phase AOG with no corresponding EventCode 31.
28-day analysis on agency partner corridor. Raw ATSPM event stream — not synthetic, not simulated.
When data cannot fully explain a finding, the Auditor names the specific question that remains, identifies who can answer it, and starts the audit trail before the engineer opens the ticket.
Recommendations and findings go into the same queue with Accept / Modify / Block / Reject buttons. No autonomous writes to controllers. Every action is logged.
Section 508 / WCAG 2.1 AA. FedRAMP-ready hosting path. Audit log built in.
Send a 28-day ATSPM export (or read-only access), the controller config snapshot, and a list of intersections that matter to you. We return a findings queue, evidence packet, and timing-change candidates — reviewed through shadow evaluation before any deployment.
Calls are confidential. We sign DOT-standard data-use agreements before touching any logs.