The transaction can be traced back to the evidence that produced it.
The transaction is a derived record. The evidence remains available: video, trajectory, plate images, axle and classification signals, LiDAR and RFID where present, timestamps, confidence, provenance, and model context.
One screen. Vehicle path, video, plate, class, confidence, transaction state.
A reviewer should see why a transaction exists without reconstructing it from separate logs. DVAS collapses investigation time and makes hard cases explainable.
The evidence is the ground truth. The transaction is a view over it.
Legacy systems often treat raw events as intermediate inputs. Once a transaction is formed, the durable record may be the transaction and a few attached images. Tollscopic preserves the evidence beyond the transaction so the transaction stays explainable.
Video segments, trajectory records, per-device events, classification outputs, confidence values, model + scorer + configuration + schema versions, decision provenance, and back-office state.
Retention is policy-driven by the operator. The system supports both short retention for cost-sensitive operators and long retention for audit-heavy contexts.
An evidence store that can be rewritten is not an evidence store. Audit, reconciliation, and replay all depend on the records being durable.
Improvements can be tested against historical evidence.
When a model, threshold, or configuration changes, historical evidence can be reprocessed to understand how the change would have affected real cases. Regression testing, auditability, and safer model evolution all live here.
A day, a week, a set of disputed transactions, or a corpus of edge cases.
New model, new scorer, new threshold, new configuration. Pinned by version.
Differences are surfaced as a diff. Reviewer decides whether to promote.
What the road saw. What was generated. What was acknowledged.
One evidence chain across the roadside, the transaction engine, the back-office adapter, and the back-office response. The system treats these as states of one record, not as separate logs to compare.
What the roadside captured: trajectories, plate reads, tag events, classification evidence.
What the transaction engine produced: a transaction record with class, confidence, and refs.
What was published to the back-office: payload, timestamp, idempotency key, retries.
What the back-office accepted, rejected, or routed to its own exception queue.
Disputes are not solved by faster billing. They are solved by better evidence.
The audit story is what a serious tolling operator measures vendors on. We are happy to walk through any disputed case end-to-end.