Truck Productivity
Estimate scheduled truck throughput with utilization conditional on availability; cycle times include operating delays and fleet dispatch interactions are external.
Description
Scheduled truck productivity discounts cycle-based output by availability and utilization.
Scheduled truck productivity discounts cycle-based output by availability and utilization. Those two factors must use compatible definitions to avoid double counting downtime.
The tool returns perTruckScheduledTonnesPerHour (per truck scheduled tonnes per hour); fleetScheduledTonnesPerHour (fleet scheduled tonnes per hour). Input measurements and model parameters are supplied by the caller; the tool computes the stated summary rather than acquiring those measurements.
When to use Truck Productivity
Use Truck Productivity when you already have payloadTonnes, cycleMinutes, mechanicalAvailability, operatingUtilization, truckCount and want perTruckScheduledTonnesPerHour, fleetScheduledTonnesPerHour. This is useful for checking a supplied calculation, documenting a measurement convention, or comparing observations prepared on the same basis.
How to use Truck Productivity and understand its results
- Enter payloadTonnes, cycleMinutes, mechanicalAvailability, operatingUtilization, truckCount using the field table below. Match the units, ordering and data boundaries described in the calculation.
- Run the tool after checking the stated bounds and matching paired observations or categories. A malformed request gives a tool error rather than a usable measurement.
- Read perTruckScheduledTonnesPerHour, fleetScheduledTonnesPerHour. Use the calculation and interpretation below to distinguish amounts, ratios, signs and decision flags where applicable.
- Review the supplied parameters and assumptions before using the result in a report or comparing it with another observation.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| payloadTonnes | Payload tonnes | number | Required |
| cycleMinutes | Cycle minutes | number | Required |
| mechanicalAvailability | Mechanical availability | number | Required |
| operatingUtilization | Operating utilization | number | Required |
| truckCount | Truck count | integer | Required |
Use positive payload, cycle and integer truck count with fractions in [0,1]. Multiply per-truck scheduled output by truck count.
tonnes/hour/truck = payload×60/cycleMinutes×availability×utilization The symbols refer to the supplied quantities or generated values described above; unit conversions and comparison boundaries follow the stated implementation.
{
"input": {
"payloadTonnes": 100,
"cycleMinutes": 20,
"mechanicalAvailability": 0.8,
"operatingUtilization": 0.5,
"truckCount": 4
},
"output": {
"perTruckScheduledTonnesPerHour": 120,
"fleetScheduledTonnesPerHour": 480
}
}Limitations and assumptions
Fleet interactions, queues and loader limits are not added automatically; they must be reflected in inputs or reviewed separately.
Numerical inputs must be finite. The tool checks its declared input shape and calculation constraints; those checks do not verify the quality, calibration or representativeness of the supplied observations.
Alternative or Complementary methods
Truck Cycle Time: Sum loaded/empty segment travel and service/queue times; speed profiles are inputs, not traction predictions. Truck Queue Time: Estimate Erlang-C truck waiting with stable Erlang-B recursion; Poisson arrivals, exponential independent service, infinite queue; not dispatch simulation.
Methodological background: Design of Surface Mine Haulage Roads: A Manual.1
References
-
Design of Surface Mine Haulage Roads: A Manual — U.S. Bureau of Mines, Information Circular 8758
Similar or alternative tools
- Truck Cycle Time
Sum loaded/empty segment travel and service/queue times; speed profiles are inputs, not traction predictions.
- Truck Queue Time
Estimate Erlang-C truck waiting with stable Erlang-B recursion; Poisson arrivals, exponential independent service, infinite queue; not dispatch simulation.