What is match factor in open pit mining, and why does it size a fleet?
Match factor is the one number mine planners reach for when someone asks "do we have the right number of trucks for this shovel." It's a ratio of truck arrival rate to shovel loading rate, and it tells you, in a single figure, whether your fleet is balanced, overbuilt, or short.
Get it wrong in either direction and it shows up on the shift report. Too few trucks and the shovel stands idle between loads, burning dig-rate potential. Too many trucks and they queue at the face, burning fuel and payroll while going nowhere. Match factor is the planning tool that's supposed to keep you off both ends of that.
The formula, in plain terms
The classic version, going back to Morgan and Peterson's original work on shovel-truck matching, is:
Match Factor = (Number of Trucks × Truck Cycle Time) / (Number of Loading Units × Loading Time per Truck)
Truck cycle time is the full loop: spot, load, haul loaded, dump, return empty, queue if there's queueing. Loading time per truck accounts for the number of passes the shovel or loader needs to fill that truck's tray.
An MF of 1.0 means trucks and shovel are, on paper, perfectly matched: nobody waits on anybody. Drop below 1.0 and you're short on trucks relative to shovel capacity, so the shovel sits idle waiting for the next truck to spot. Push past 1.0 and you've got more truck capacity than the shovel can feed, so trucks queue and your fleet utilization numbers take the hit even though nothing mechanical is wrong.
Most pits don't run at exactly 1.0 on purpose. A planner might deliberately push MF slightly above 1 to keep the shovel, the most expensive and hardest-to-replace asset on the bench, working flat out, accepting a bit of truck queue time as the cheaper trade-off. That's a real decision, not an error, and it's one reason match factor numbers vary between pits running the same equipment.
Why it drives fleet size, not just daily efficiency
Match factor gets used two ways. On shift, it's a quick check on whether today's assignment is tight. In fleet planning, it's the thing you solve backward from: given a shovel's known loading time and a haul road's known cycle time, how many trucks does this route need to hit a target MF?
That second use is why match factor shows up in capital planning conversations, not just operations meetings. Add a truck to a route and you've changed the ratio for every other truck on that route too. Change haul distance, because the pit's gone deeper or the dump's moved, and cycle time shifts, which moves MF even if truck count stays the same. That makes fleet sizing a recalculation every time geometry or routing changes, which in an active pit is often.
Where the formula runs into real-world noise
The formula assumes you know truck cycle time and loading time with some confidence. In practice, both drift. Haul road condition changes cycle time more than most planning sheets account for: a road that's rutted or wet adds minutes per cycle that compound across a shift, pulling actual MF away from the planned figure without anyone changing truck count.
This is also where match factor calculations done on paper diverge from what a fleet is actually doing on the ground. A planner's MF is only as good as the inputs, and cycle time in particular is hard to pin down without watching trucks move. Counting trucks on the haul network from VHR imagery, alongside a read on road condition, gives operators and analysts an outside check on those assumptions without needing a site visit or telematics feed. If you're trying to sanity-check a match factor calculation or benchmark someone else's haul fleet from outside the fence, a daily truck count and road condition read is a reasonable place to start.
Match factor won't tell you why a route is running slow. It just tells you the ratio is off, and that's usually enough to know where to look next.