Traffic Operations
TrafficOps is the FactVerse module for transport hub, checkpoint, passenger, vehicle, cargo, and border-style operations. It connects live queues, wait-time signals, throughput, lane and checkpoint status, incidents, staff planning, equipment health, scenario simulation, and review evidence into one operating workflow.
Use this guide when an operations team needs to monitor a terminal or checkpoint environment, understand where congestion is forming, compare staffing or lane scenarios, and prepare reviewed action plans with traceable evidence.
For AI-assisted analysis surfaces, see Traffic Operations AI Tools.
Current service boundary
TrafficOps is implemented across several runtime surfaces:
| Surface | Current role |
|---|---|
| FactVerse frontend | Provides TrafficOps home, scene editor, passenger flow, checkpoint overview, passenger clearance, vehicle operations, cargo operations, multi-region view, data ingestion, equipment config, simulation, Commander views, capacity planning, SLA monitor, incidents, energy dashboard, density heatmap, training, predictive maintenance, and passenger analytics views. |
| TrafficOps backend services | Provide /api/v1/trafficops dashboards, KPIs, queues, lane snapshots, passenger, vehicle, cargo, WCP, incident, operations event, canonical model, equipment, density, energy, optimization, multi-region, training, decision, report, rule, workflow, and simulation endpoints. |
| AI Engine | Provides TrafficOps forecast, proactive alerts, monitor state, what-if comparison, optimization, calibration, DES/DAG simulation, and package-based scene or road-network services when enabled. |
| Platform tool framework | Provides TrafficOps tools such as traffic flow analysis and wait-time prediction for approved Agent workflows. |
| DFS | Prepares arrival, queue, incident, equipment, staffing, layout, schedule, and operational datasets before they are used by dashboards, tools, and simulations. |
| Inspector and work orders | Provide action tracking, incident follow-up, maintenance feedback, and field execution context when TrafficOps actions become operating work. |
TrafficOps supports operational review, scenario planning, and action preparation. Teams should confirm source data, local operating rules, and owner approval before changing staffing, lane configuration, or field procedures.
Operations workflow
What users can do today
| Workflow | What users can review or perform |
|---|---|
| Operations overview | Review throughput, wait time, queue state, utilization, active incidents, SLA risk, and operational events. |
| Passenger flow | Review current flow, timeline, wait-time distribution, checkpoint heatmap, passenger analytics, and forecasted demand. |
| Checkpoint overview | Review lane or checkpoint status, queue length, utilization, current configuration, recent snapshots, and scene-level status. |
| Vehicle operations | Review vehicle arrivals, lane configuration, tidal-lane scenarios, incident impact, and car or motorcycle clearance views. |
| Cargo operations | Review cargo queue, inspection pipeline, staffing impact, sampling-rate scenarios, held cargo, and throughput KPIs. |
| WCP and processing | Review bus schedules, peak simulation, congestion rules, dashboard state, and rule evaluation output for checkpoint processing. |
| Incidents and density | Review active incidents, incident statistics, density grid, red/amber/green density cells, surge alerts, and replay evidence when available. |
| Resource planning | Review current optimization state, staff schedules, recommendations, shift planning, capacity planning, SLA monitor, and decision logs. |
| Simulation | Run or review DES/DAG simulation runs, compare scenarios, inspect run results, and export or replay run output where available. |
| Equipment and energy | Review equipment configuration, sensitivity analysis, health reports, maintenance schedule, and energy KPIs for the operating scope. |
| Multi-region operations | Review regional KPIs, timeline, resilience, and cross-region simulation results. |
| Training | Review training dashboard and drill state for operator learning or incident rehearsal. |
Before you start
Prepare the operating scope and source data before relying on TrafficOps outputs:
| Requirement | Notes |
|---|---|
| Tenant and operating scope | Define site, terminal, checkpoint, zone, direction, route, and time window. |
| Permissions | Match the user role to TrafficOps module access, decision review, simulation, reporting, and write actions. |
| Stable objects | Use stable IDs for facilities, zones, checkpoints, lanes, equipment, staff roles, incidents, schedules, and vehicle or passenger categories. |
| Source data | Prepare arrivals, throughput, wait times, snapshots, schedules, incidents, equipment status, staffing, and rule data. |
| Review owner | Define who accepts recommendations, approves staffing or lane changes, opens incidents, and records feedback. |
| Scenario assumptions | Record demand windows, service-time assumptions, staffing cost, capacity limits, failure assumptions, and SLA targets. |
| Data quality | Check timestamp alignment, missing snapshots, stale schedules, duplicate incidents, and unit consistency. |
Use DFS when source systems need connector configuration, source-to-target mapping, sync monitoring, data-quality review, and governed dataset preparation.
Open TrafficOps
Open the FactVerse application and use the TrafficOps workspace. Current frontend surfaces include:
| View | Route |
|---|---|
| Home | /trafficops |
| Scene editor | /trafficops/scenes |
| Passenger flow | /trafficops/flow |
| Resource optimization | /trafficops/optimization |
| FactVerse 3D view | /trafficops/3d-view |
| Passenger clearance | /trafficops/passenger |
| WCP dashboard | /trafficops/cp |
| Checkpoint overview | /trafficops/checkpoint-overview |
| Vehicle operations | /trafficops/vehicles |
| Cargo operations | /trafficops/cargo |
| Multi-region | /trafficops/multi-region |
| Data ingestion | /trafficops/data-ingestion |
| Equipment config | /trafficops/equipment-config |
| Simulation | /trafficops/sim |
| Commander passenger and vehicle views | /trafficops/commander-pax, /trafficops/commander-vehicle |
| What-if and optimization | /trafficops/whatif, /trafficops/optimize |
| Capacity and SLA | /trafficops/capacity-planning, /trafficops/sla-monitor |
| Incidents and density | /trafficops/incidents, /trafficops/density-surge |
| Energy and training | /trafficops/energy-dashboard, /trafficops/training |
| Predictive maintenance and passenger analytics | /trafficops/predictive-maintenance, /trafficops/passenger-analytics |
| Vehicle clearance and bus hall | /trafficops/car-mc-clearance, /trafficops/departure-bus-hall |
Module availability depends on tenant configuration and enabled routes.
Prepare operational data
TrafficOps depends on a consistent operating data package:
| Data area | Typical preparation |
|---|---|
| Facility and checkpoint model | Map facilities, zones, checkpoints, lanes, equipment, staff roles, and directions to stable IDs. |
| Arrival and queue data | Prepare passenger, vehicle, cargo, and bus arrival records with timestamps, category, source, and lane or checkpoint context. |
| Lane snapshots | Prepare latest, recent, and historical snapshots for queue length, status, capacity, and scene review. |
| Incidents | Map incident severity, type, status, affected zone, replay evidence, and response state. |
| Staffing and schedules | Prepare rosters, shift plans, staff roles, and schedule constraints for resource planning. |
| Equipment and maintenance | Prepare equipment status, service-time distributions, sensitivity parameters, health records, and maintenance schedule. |
| Simulation inputs | Prepare baseline scenarios, what-if overrides, failure assumptions, route graphs, and comparison metrics. |
Review live operations
Start from the operations dashboard, then drill into the operational area:
- Select the facility, checkpoint, direction, or region under review.
- Review throughput, average wait, P95 wait, queue length, utilization, incidents, and SLA state.
- Open passenger, vehicle, cargo, or WCP views based on the affected queue.
- Check lane snapshots and checkpoint status to confirm whether the bottleneck is local or cross-zone.
- Record the time window, data sources, and operating assumptions before approving action.
Use the dashboard as a review surface. Field owners should confirm local constraints before changing lane, staff, or incident procedures.
Analyze passenger, vehicle, and cargo flow
TrafficOps separates operating flows so teams can review the right evidence:
| Flow | Review focus |
|---|---|
| Passenger flow | Current passenger volume, flow timeline, wait distribution, checkpoint heat, and forecasted demand. |
| Vehicle flow | Current vehicle flow, arrivals, active lanes, lane configuration, tidal-lane simulation, and incident impact. |
| Cargo flow | Truck queue, inspection pipeline, sampling rate, held cargo, staff allocation, throughput, and time in system. |
| Officer performance | Processing efficiency, workload distribution, and checkpoint staffing review. |
| Passenger analytics | Passenger trend and behavior review for planning and reporting. |
Plan resources and scenarios
Use resource planning when the current state requires a staffing, lane, or capacity decision:
| Surface | Use |
|---|---|
| Resource optimization | Review current staffing, schedule, and recommendations. |
| Shift planning | Prepare personnel schedules and inspect coverage. |
| Capacity planning | Review longer-horizon demand and capacity assumptions. |
| What-if analysis | Compare baseline and changed parameters such as staff count, lane capacity, service time, or failure assumptions. |
| Simulation runs | Run, compare, and export DES/DAG scenarios for queue and service-process analysis. |
| Decision log | Preserve accepted, rejected, and reviewed recommendations with context. |
Scenario outputs should be read with their inputs. Store demand assumptions, service-time assumptions, and constraint notes with the review.
Review incidents, density, and training
Incidents and density views support operational response:
- Review active incidents and incident statistics.
- Check density grid cells and threshold state for the selected window.
- Open replay evidence when an incident requires operator training or post-incident review.
- Prepare or approve the response plan through the responsible owner.
- Use training drills to rehearse procedures before applying them in live operation.
Density, incident, and training outputs support human review and training. Site safety procedures and local command rules remain the execution basis.
Review equipment and energy
TrafficOps includes equipment and energy surfaces for operations teams:
| Area | What to check |
|---|---|
| Equipment configuration | Checkpoint profile, service-time settings, sensitivity parameters, and zone-level updates. |
| Equipment health | Health report, maintenance schedule, affected facility, and linked operating risk. |
| Predictive maintenance | Equipment risk and maintenance planning when TrafficOps assets need reliability review. |
| Energy dashboard | Energy KPIs for the operating scope when source readings are mapped and validated. |
For deeper asset reliability workflows, use Predictive Maintenance Operations.
API surface
TrafficOps APIs are grouped under /api/v1/trafficops:
| Group | Example endpoints |
|---|---|
| Overview and KPIs | /overview, /queues, /events, /kpis, /info |
| Lane snapshots | /lane-snapshots/latest, /lane-snapshots/recent, /lane-snapshots/history, /lane-snapshots/scenes, /lane-snapshots/overview, /lane-snapshots/reconfig |
| Passenger, vehicle, and cargo flow | /passenger-flow/current, /passenger-flow/timeline, /passenger-flow/wait-distribution, /passenger-flow/heatmap, /vehicle-flow/current, /vehicle-ops/overview, /cargo-flow/kpis, /cargo-ops/overview |
| WCP and checkpoint processing | /wcp/bus-schedule, /wcp/evaluate-rules, /wcp/peak-simulation, /wcp/congestion-rules, /wcp/dashboard |
| Incidents and operations events | /incidents/active, /incidents/stats, /ops/dashboard, /ops/events, /ops/events/{id}/ack, /ops/events/{id}/resolve |
| Canonical model | /canonical/facilities, /canonical/facilities/{code}, /canonical/checkpoints/{id}/config, /canonical/zones/{id}/staff-schedule, /canonical/facilities/{code}/capacity |
| Equipment and maintenance | /equipment-config, /equipment-config/{checkpointId}/profile, /equipment-config/{checkpointId}/sensitivity-analysis, /equipment-config/facilities/{facilityCode}/health-report, /equipment-health, /equipment-health/schedule |
| Density and energy | /density/grid, /energy/kpis |
| Planning and reporting | /resource-optimization/current, /resource-optimization/staff-schedule, /resource-optimization/recommendations, /reports, /reports/generate, /rules |
| Multi-region, training, and decisions | /multi-region/regions, /multi-region/timeline, /multi-region/simulate, /multi-region/resilience, /training/dashboard, /decisions |
| Workflow | /workflow/action-plan/submit, /workflow/action-plan/dismiss, /workflow/tasks/pending, /workflow/ecm/incident-report, /workflow/ecm/what-if |
| Simulations and AI endpoints | /simulations, /simulations/runs, /forecast, /simulate, /recommend, /ai/* |
AI Engine surfaces include /ai/trafficops/forecast, /ai/trafficops/proactive-alerts, /ai/trafficops/monitor, /ai/trafficops/what-if, /ai/trafficops/optimize, /ai/trafficops/calibration/*, /ai/whatif/*, /ai/des/*, /ai/optimize/trafficops, and /ai/packages/{package_key}/* where enabled.
Validation checklist
Before using TrafficOps output in an operations meeting or field action, confirm:
- tenant, site, checkpoint, direction, region, and time window match the review scope;
- arrival, queue, lane, incident, equipment, schedule, and staffing data share stable IDs;
- source timestamps and units are aligned across the selected window;
- simulation and what-if assumptions are recorded with the output;
- recommendations identify the owner who accepts or rejects the action;
- lane, staff, incident, and maintenance changes remain governed by the local approval path;
- decision logs, incident notes, reports, or exports are stored with the review package;
- feedback from the action is recorded so future forecasts, scenarios, and operating playbooks can improve.