How to Read the ORCHCAVIA Dashboard
A plain-English walkthrough of every box, number, and color on the dual-branch traffic integrity dashboard — so you know exactly what the engine is telling you at a glance.
What Is ORCHCAVIA
Explain Like I'm 5
ORCHCAVIA is a traffic watcher. It looks at how fast cars are stacking up on a road or how far behind your delivery trucks are running — and tells you if a route is about to jam up before it actually happens. Think of it as a weather radar, but for traffic and fleet routes.
Technical
ORCHCAVIA is a physics-based kinetic engine that ingests traffic and routing telemetry in real time and computes deviation rate, structural mass, kinetic index, and kinematic velocity to classify the route's trajectory. It escalates directives — from flow nominal to kinetic turbulence to route integrity compromised — before the ping-storm cascades across the network.
The Two Branches
The dashboard shows two branches side by side. Each branch watches a different domain of your traffic network.
Watches city traffic flow — density, congestion, and ride-hailing ping volume.
Traffic Density · Flow Rate · ETA Deviation · Ping Volume
Watches fleet routing integrity — dispatch lag, hub throughput, delivery completion.
Delivery Density · Fleet Velocity · Hub Throughput · Dispatch Lag
Reading the Boxes
Each box on the dashboard is one signal (one segment's "thermostat"). Here's what every part of the box means, from top to bottom:
The Three Directives
FLOW NOMINAL
Green. Route is within plan parameters. No action needed. The box stays quiet — no threshold or circuit breaker numbers are shown because there's nothing to fix.
KINETIC TURBULENCE
Yellow. Congestion trajectory is forming but hasn't crossed the critical threshold yet. The dispatcher should monitor and prepare a diversion. Threshold and stabilize targets appear.
ROUTE COMPROMISED
Orange. The segment has crossed the threshold and is heading toward route collapse. The engine issues a proactive diversion directive. Issue the divert immediately.
Metric Glossary
Reading
Explain Like I'm 5
What the sensor is measuring right now — like the speedometer in your car.
Technical
The live telemetry value from the routing/telemetry bridge for this signal type (vehicles, pings, minutes).
Baseline
Explain Like I'm 5
What the number should be if the route is flowing according to plan.
Technical
The route-plan / historical-norm expected value. The engine measures all deviation against this.
Deviation
Explain Like I'm 5
How far off the reading is from the plan, shown as a percentage. 0% = perfect.
Technical
(Reading − Baseline) / Baseline × 100. The primary deviation rate (D) that feeds the kinetic index.
Kinetic Idx
Explain Like I'm 5
A danger score. Higher = more risk. It goes up when the reading is both big and off-plan.
Technical
The combined index that amplifies when structural mass (M) and deviation rate (D) intersect.
Velocity
Explain Like I'm 5
How fast the number is changing between readings. A sudden jump means trouble is accelerating.
Technical
Kinematic velocity — the rate of change of the signal value relative to the previous reading.
Rapidity
Explain Like I'm 5
A speed score compared to the plan. If it hits 1.0 or higher, the problem is going vertical — act fast.
Technical
Normalized rapidity (velocity / baseline). ≥ 1.0 indicates a near-vertical trajectory toward a critical event.
Threshold
Explain Like I'm 5
The danger line. Once your reading crosses this number, the engine turns orange.
Technical
The action-threshold signal value. Crossing it triggers the kinetic turbulence or route-compromised directive.
Stabilize
Explain Like I'm 5
The target number to get back to so the box turns green again.
Technical
The stabilization target — the signal value the dispatcher should aim for to return the route to nominal.
Circuit Breaker
Explain Like I'm 5
The 'oh no' number. If the reading hits this, it's a full route collapse — divert everything.
Technical
The hard critical threshold. Reaching it implies a catastrophic route-integrity event requiring immediate fleet-wide diversion.
The Trajectory Graph
Each box includes a small line graph (sparkline). Here's how to read it:
- ● The solid line is the signal's path over the last few readings.
- ┄ The dashed line is the baseline — the "plan." A healthy line stays near it.
- ┄ The yellow dashed line (alerts only) is the threshold — the danger zone boundary.
- ┄ The orange dashed line (alerts only) is the circuit breaker — the hard route-collapse limit.
When you press "Inject Anomaly" in the demo, watch the line climb away from the baseline and toward the threshold. That visual climb is exactly what the engine detects — before the reading reaches the circuit breaker.
Classification Rules
The engine uses a deterministic, first-match-wins rule set. Every reading is classified by exactly one rule — this is your audit trail.
Dispatcher Workflow
When multiple alerts fire across different cities or routes simultaneously, the dashboard prioritizes for you:
Sort by Rapidity
Alerts with the highest rapidity index (≥ 1.0) are the most critical — the trajectory is near-vertical. Handle those first.
Check the Circuit Breaker
If the reading is approaching the orange dashed line, that segment is about to collapse. Divert traffic away from it now.
Acknowledge or Dismiss
Once you've issued the diversion or determined the alert is a false positive, acknowledge or dismiss the alert to clear it from the active list.
Refresh for New Alerts
Click the Refresh button to pull the latest readings. New alerts from the ingest pipeline will appear in the Open Alerts list automatically.
Ready to see it in action?
Go back to the live demo and inject an anomaly to watch the engine escalate.