Calculate cycle time from load time, haul distance, speed, and wait time, then compare theoretical and actual productivity instantly.
Use fleet size sensitivity, operating ücret comparisons, and bottleneck labels on the same ekran.
The loading, travel, and wait pieces are shown as one truck cycle.
See whether the truck side or the shovel side is limiting, along with the recommended truck count.
60 t payload, 3:00 load time, 4.0 km one-way haul, 25 km/h, 1:00 wait time, 6 trucks, 1 shovel, 85% operating rate
cycle time about 23.2 min, theoretical about 973 t/h, actual about 791 t/h, truck-limited, recommended about 8 trucks/shovel
80 st payload, 3:00 load time, 2.5 mi one-way haul, 18 mph, 1:30 wait time, 5 trucks, 1 shovel, 80% operating rate
cycle time about 21.2 min, theoretical about 1,220 st/h, actual about 907 st/h, truck-limited
60 t payload, loaded 4.0 km at 22 km/h, return 4.0 km at 32 km/h, 3:00 load time, 1:00 wait time, 8 trucks, 1 shovel, 90% operating rate
cycle time about 22.4 min, theoretical about 1,200 t/h, actual about 1,080 t/h, shovel-limited
In basit mode, enter one-way distance and the tool doubles it internally. Detailed mode lets you enter loaded and return legs separately.
Theoretical productivity assumes no wait time and 100% operating ücret. Actual productivity reflects wait time and operating ücret.
Actual productivity changes linearly. The comparison table shows the difference from 50% to 100%.
No. It is a static kapasite comparison that keeps the entered average wait time fixed. It does not tahmin queue growth automatically.
Yes. Choose the unit you actually use on site. The tool does not convert by density, so enter the basis unit directly.
Yes. The page is translated from English, and URL sharing reproduces the same state.
Time for one truck to complete a full loading, haul, return, and wait cycle.
Average load carried per truck cycle.
Paylaşım of scheduled time actually used for production.
The resource or step that most strongly limits çıktı.
Indicates the balance between truck-side and shovel-side kapasite. Values near 1 are more balanced.
Average waiting time including queue, dump, spotting, and short delays.
map[Text:travelTimeSimple = 2 × haulDistance / haulSpeed × 60 text:travelTimeSimple = 2 × haulDistance / haulSpeed × 60]map[Text:travelTimeDetailed = loadedHaulDistance / loadedHaulSpeed × 60 + returnHaulDistance / returnHaulSpeed × 60 text:travelTimeDetailed = loadedHaulDistance / loadedHaulSpeed × 60 + returnHaulDistance / returnHaulSpeed × 60]map[Text:idealCycleTime = loadTime + travelTime text:idealCycleTime = loadTime + travelTime]map[Text:actualCycleTime = idealCycleTime + waitTime text:actualCycleTime = idealCycleTime + waitTime]map[Text:theoreticalTruckRate = payload / idealCycleTime × 60 text:theoreticalTruckRate = payload / idealCycleTime × 60]map[Text:actualTruckRate = payload / actualCycleTime × 60 text:actualTruckRate = payload / actualCycleTime × 60]map[Text:shovelRate = payload / loadTime × 60 text:shovelRate = payload / loadTime × 60]map[Text:actualFleetRate = min(truckCount × actualTruckRate, shovelCount × shovelRate) × operatingRate text:actualFleetRate = min(truckCount × actualTruckRate, shovelCount × shovelRate) × operatingRate]map[Text:recommendedTruckCount = ceil((shovelCount × shovelRate) / actualTruckRate) text:recommendedTruckCount = ceil((shovelCount × shovelRate) / actualTruckRate)]