Calculator
D2
Truck Dispatch Logic & Fleet Utilization
Truck dispatch logic is the real-time system that decides which haul truck goes where, when, and with what load — like a traffic controller for mining trucks.
⚠️ Why It Matters
1
Inefficient dispatch decisions
↓
2
Increased truck idle time and waiting queues
↓
3
Reduced tons-per-hour (TPH) throughput
↓
4
Higher fuel consumption and tire wear per ton
↓
5
Lower fleet availability and premature component fatigue
↓
6
Escalated operating cost per ton and reduced NPV
📘 Definition
Truck dispatch logic is an automated decision-making framework that dynamically assigns haul trucks to loading and dumping points based on real-time equipment status, payload targets, cycle time estimates, queue states, and fleet constraints. It integrates telematics, GPS, payload monitoring, and optimization algorithms (e.g., rule-based, heuristic, or MILP solvers) to maximize fleet utilization while respecting safety, maintenance, and operational KPIs. The system operates within a broader mine automation architecture, interfacing with shovel dispatch, fleet management software (FMS), and production scheduling systems.
🎨 Concept Diagram
AI-generated illustration for visual understanding
💡 Engineering Insight
Dispatch logic isn’t about 'optimizing trucks' — it’s about stabilizing the *system*. A 5% improvement in FUR often comes not from faster trucks, but from reducing queue variance at shovels: a stable 3-truck queue delivers higher throughput than an unstable 1–5 truck queue averaging 3 — because predictability enables tighter shovel cycle synchronization and reduces ramp contention. Always tune for stability before speed.
📖 Detailed Explanation
At its core, truck dispatch logic solves a constrained assignment problem: given N active trucks and M loading/dumping points, assign each truck to the next optimal task without violating physical, temporal, or regulatory constraints. Early systems used fixed rotation or simple 'nearest available' rules — effective only in static, low-complexity environments. Modern implementations rely on layered logic: a top-layer scheduler sets medium-term assignments (e.g., 15-min horizon), while a bottom-layer executor handles real-time adjustments (e.g., rerouting due to a stopped truck or sudden ramp closure).
Advanced systems incorporate predictive elements: machine learning models forecast shovel availability based on bucket fill rate trends and hydraulic pressure decay; digital twin simulations pre-test dispatch policies against stochastic events (e.g., tire puncture probability, loader swing delay). Crucially, the logic must embed *physical fidelity*: acceleration limits, grade-dependent speed caps, and payload-dependent braking distances are not optional inputs — they’re hard constraints baked into the solver’s feasibility domain.
The most mature implementations treat dispatch as part of a closed-loop control system. Telemetry from each completed cycle (actual cycle time, payload error, route deviation) feeds back into model recalibration. This creates adaptive behavior: during wet season, the system automatically increases safety margins on clay-slicked ramps; during high-grade ore pushes, it biases assignment toward higher-capacity trucks with verified payload accuracy — all without operator intervention. True robustness emerges only when dispatch logic respects both physics and human factors: e.g., limiting consecutive uphill cycles to prevent thermal brake fade, or enforcing minimum rest intervals between shifts for autonomous truck operators.
Advanced systems incorporate predictive elements: machine learning models forecast shovel availability based on bucket fill rate trends and hydraulic pressure decay; digital twin simulations pre-test dispatch policies against stochastic events (e.g., tire puncture probability, loader swing delay). Crucially, the logic must embed *physical fidelity*: acceleration limits, grade-dependent speed caps, and payload-dependent braking distances are not optional inputs — they’re hard constraints baked into the solver’s feasibility domain.
The most mature implementations treat dispatch as part of a closed-loop control system. Telemetry from each completed cycle (actual cycle time, payload error, route deviation) feeds back into model recalibration. This creates adaptive behavior: during wet season, the system automatically increases safety margins on clay-slicked ramps; during high-grade ore pushes, it biases assignment toward higher-capacity trucks with verified payload accuracy — all without operator intervention. True robustness emerges only when dispatch logic respects both physics and human factors: e.g., limiting consecutive uphill cycles to prevent thermal brake fade, or enforcing minimum rest intervals between shifts for autonomous truck operators.
🔄 Engineering Workflow
Step 1
Step 1: Define operational boundaries (haul routes, dump/stockpile zones, speed limits, safety exclusion zones)
→
Step 2
Step 2: Calibrate equipment models (truck acceleration/deceleration curves, payload sensor accuracy, GPS latency profiles)
→
Step 3
Step 3: Integrate real-time data feeds (shovel cycle timers, pit grade maps, truck health telemetry, weather-triggered speed derating)
→
Step 4
Step 4: Configure dispatch policy engine (priority rules, fairness weights, KPI trade-off sliders: TPH vs. FUR vs. fuel/kg)
→
Step 5
Step 5: Validate logic via digital twin simulation (100+ shift scenarios, including failure injection and ramp congestion)
→
Step 6
Step 6: Deploy in phased pilot (single pit zone → full fleet), with manual override audit trail enabled
→
Step 7
Step 7: Monitor KPI drift weekly; recalibrate cycle time models monthly; retrain ML-based predictors quarterly
📋 Decision Guide
| Rock/Field Condition | Recommended Design Action |
|---|---|
| Surface mine, steep ramp grades (>12%), high ore variability (density ±18%) | Implement density-compensated payload targeting + dynamic burden adjustment; enforce minimum 2-truck buffer at primary loading point |
| Underground mine, narrow ramps (<5.5 m wide), multiple simultaneous dump points with variable access times | Deploy priority-based shortest-path routing with real-time ramp conflict detection; cap max queue depth at 3 trucks per loading bay |
| Mixed ore/waste haulage with segregation requirements and strict stockpile blending specs | Enforce hard constraint dispatch rules: geo-tagged truck assignment, mandatory GPS-verified dump location logging, and real-time blend deviation alerts |
📊 Key Properties & Parameters
Cycle Time
3.5–12.0 minutes (surface); 8.0–25.0 minutes (underground)Total time for a truck to complete one full haul cycle: load → travel loaded → dump → return empty → queue → load again.
⚡ Engineering Impact:
Directly determines maximum theoretical fleet capacity; errors >±15% in cycle time estimation cause dispatch instability and queue collapse.
Payload Utilization Ratio (PUR)
0.82–0.96 (82–96%) for well-calibrated fleets with consistent material densityRatio of actual payload mass to rated payload capacity, expressed as a decimal or percentage.
⚡ Engineering Impact:
PUR < 0.85 indicates underloading (wasted capacity); PUR > 0.98 increases risk of overload damage, spillage, and regulatory noncompliance.
Fleet Utilization Rate (FUR)
62–78% for optimized surface fleets; 48–65% for complex underground operationsPercentage of total fleet hours actively engaged in productive haul cycles (excluding maintenance, refueling, and idle wait).
⚡ Engineering Impact:
FUR < 60% signals systemic bottlenecks (e.g., shovel downtime, poor dispatch logic, or infrastructure constraints), not just truck availability.
Queue Stability Index (QSI)
0.15–0.45 (low variance = stable; >0.6 = unstable, oscillatory behavior)Dimensionless metric quantifying queue length variance at loading points over rolling 30-min windows, normalized by mean queue length.
⚡ Engineering Impact:
QSI > 0.55 correlates strongly with dispatch algorithm divergence, leading to ‘herding’ effects and cascading delays across shifts.
📐 Key Formulas
Fleet Utilization Rate (FUR)
FUR = (Σ Active Haul Hours / Σ Total Fleet Hours) × 100%Measures percentage of total fleet time spent in productive haul cycles.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| FUR | Fleet Utilization Rate | % | Percentage of total fleet time spent in productive haul cycles |
| Σ Active Haul Hours | Sum of Active Haul Hours | hours | Total hours during which fleet vehicles are actively engaged in haul cycles |
| Σ Total Fleet Hours | Sum of Total Fleet Hours | hours | Total available operating hours across the entire fleet |
Typical Ranges:
Well-optimized surface copper mine
70–78%
Deepening phase with ramp congestion
58–65%
New underground block cave with early-stage infrastructure
48–56%
⚠️ Sustained FUR > 80% indicates chronic under-provisioning; < 55% warrants root-cause analysis of bottlenecks.
Effective Payload Factor (EPF)
EPF = (Actual Payload Mass / Rated Payload Capacity) × (Rated Payload Capacity / Design Payload Density)Normalizes payload efficiency against material density variation; critical for mixed-ore dispatch.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| Actual Payload Mass | Actual Payload Mass | kg | Mass of payload actually carried |
| Rated Payload Capacity | Rated Payload Capacity | kg | Maximum allowable payload mass specified for the vehicle or system |
| Design Payload Density | Design Payload Density | kg/m³ | Reference density used in design, representing expected average density of payload material |
Typical Ranges:
Uniform waste rock haulage
0.92–0.97
High-grade ore with density swings (2.4–3.1 t/m³)
0.83–0.94
⚠️ EPF < 0.80 triggers automatic load verification protocol; EPF > 0.99 flags potential overloading risk.
🏭 Engineering Example
Chuquicamata Open Pit (Codelco, Chile)
Porphyry copper ore (oxidized cap over sulfide zone)Cycle Time
6.8 min (average, dry conditions)
Truck Fleet Size
122 CAT 797F
Avg. Haul Distance
2.1 km
Queue Stability Index
0.29
Fleet Utilization Rate
73.2%
Payload Utilization Ratio
0.91
🏗️ Applications
- Autonomous haulage system (AHS) coordination
- Multi-pit multi-shovel fleet balancing
- Ore-waste segregation enforcement in ROM blending
- Emergency response rerouting during slope instability
📋 Real Project Case
Chilean Copper Mine: Autonomous Haul Fleet Deployment
A Tier-1 copper mine in the Atacama Desert, northern Chile, deployed an autonomous haul fleet across its open-pit operation. The site processes ~450 ktpd of ore and waste, with a 2.8-km average haul distance and 320-m vertical lift. The project involved retrofitting and integrating 42 autonomous 290-tonne CAT 794 AC electric drive haul trucks into existing dispatch and traffic management systems.
Challenge: Achieving safe, reliable, and productive autonomous haulage under extreme environmental conditions (...
Read full case study →
❓ Frequently Asked Questions
What is truck dispatch logic and how does it differ from traditional manual dispatch?
Truck dispatch logic is an automated, real-time decision-making system that dynamically assigns haul trucks to loading and dumping points based on live data—including equipment status, payload targets, cycle times, queue lengths, and fleet constraints. Unlike manual dispatch, which relies on operator judgment and static schedules, this logic uses telematics, GPS, payload monitoring, and optimization algorithms (e.g., rule-based, heuristic, or MILP solvers) to continuously rebalance assignments—improving responsiveness, consistency, and utilization while enforcing safety and maintenance protocols.
How does truck dispatch logic improve fleet utilization?
It improves fleet utilization by minimizing idle time and deadhead travel through intelligent, constraint-aware assignment. By analyzing real-time cycle time estimates, queue states at shovels and dumps, and individual truck capabilities (e.g., payload capacity, health status), the system balances workload across the fleet—reducing bottlenecks, avoiding overloading high-performing units, and ensuring underutilized assets are productively engaged—all while respecting maintenance windows and operational KPIs like tons/hour and fuel efficiency.
What data sources and systems does truck dispatch logic integrate with?
Truck dispatch logic integrates with multiple real-time and enterprise systems: telematics and GPS for location and speed, payload monitoring systems (e.g., load cells or volume estimation) for fill-level verification, shovel dispatch systems for loading availability, fleet management software (FMS) for maintenance status and operational limits, and production scheduling systems for shift targets and material movement plans. This integration enables closed-loop, context-aware decision-making within the broader mine automation architecture.
Can truck dispatch logic adapt to changing conditions like equipment failure or traffic congestion?
Yes—by design, it continuously ingests and processes real-time telemetry and queue state data. If a truck fails or enters maintenance mode, the logic instantly reassigns its pending tasks to available units. Similarly, if congestion is detected (e.g., via prolonged dwell time or GPS-derived speed drops), the system recalculates optimal routes and destinations—potentially diverting trucks to alternate dumps or adjusting shovel priorities—to maintain throughput and KPI compliance without manual intervention.
What types of optimization algorithms are commonly used in truck dispatch logic—and how do they impact performance?
Common approaches include rule-based logic (fast, deterministic, ideal for stable operations), heuristic methods (e.g., shortest-queue or nearest-neighbor, balancing speed and adaptability), and mathematical optimization solvers like Mixed-Integer Linear Programming (MILP) for globally optimal assignments under complex constraints. The choice depends on latency requirements, problem scale, and computational infrastructure: rule-based offers millisecond response times; MILP delivers higher utilization but may require aggregation or rolling-horizon planning to stay within real-time bounds.
What is the primary objective of truck dispatch logic in mining operations?
The primary objective is to maximize fleet utilization and overall production efficiency by dynamically assigning haul trucks to loading and dumping points in real time—while adhering to safety protocols, maintenance schedules, payload targets, cycle time constraints, and operational KPIs such as tonnage moved per hour and equipment availability.
How does truck dispatch logic differ from traditional manual or static dispatch methods?
Unlike manual or static dispatch—which rely on pre-defined routes, fixed assignments, or operator judgment—truck dispatch logic uses real-time data (e.g., GPS location, payload weight, engine status, queue lengths) and optimization algorithms (rule-based, heuristic, or mixed-integer linear programming) to continuously re-optimize assignments. This enables adaptive, responsive, and data-driven decision-making that improves throughput and reduces idle time.
Which systems and data sources does truck dispatch logic integrate with?
It integrates with telematics and GPS for real-time location and health monitoring; payload sensors for load verification; shovel dispatch systems for loading coordination; fleet management software (FMS) for maintenance and availability status; and production scheduling systems for shift targets and material flow plans. Interoperability is typically enabled via standardized APIs or middleware within the mine’s automation architecture.
Can truck dispatch logic accommodate mixed-fleet operations (e.g., different truck sizes, payloads, or OEMs)?
Yes—modern dispatch logic supports heterogeneous fleets by modeling each truck’s unique capabilities (e.g., payload capacity, speed profile, fuel consumption, maintenance state) as constraints and variables in the assignment algorithm. This ensures optimal task allocation across diverse equipment while maintaining compliance with site-specific operational rules and safety limits.
How does truck dispatch logic contribute to key performance indicators (KPIs) like fleet utilization and cycle time?
By minimizing empty travel, reducing queuing at shovels and dumps, and balancing workload across available trucks, dispatch logic directly improves fleet utilization (% uptime actively hauling) and tightens average cycle times. Real-time adjustments also enable rapid response to disruptions (e.g., equipment failure or grade changes), sustaining KPI performance despite dynamic conditions.
🎨 Technical Diagrams
📚 References
[1]
Guidelines for Mine Automation Systems – Part 3: Haul Truck Dispatch Logic
— International Council on Mining and Metals (ICMM)
[2]
SME Mining Engineering Handbook, 4th Edition
— Society for Mining, Metallurgy & Exploration (SME)
[3]
ISO 20474-1:2021 Earth-moving machinery — Safety — Part 1: General requirements
— International Organization for Standardization (ISO)