Most fleets are running min-max levels that were never actually calculated. They were inherited from the last parts manager, guessed at when the system was set up, or copied off a vendor's suggestion — then left untouched for years while the fleet, the routes, and the lead times all changed around them. That's why a storeroom can be simultaneously overstocked and stocking out: the numbers driving replenishment have nothing to do with how the fleet actually uses parts. Setting bus parts min-max levels from real usage fixes both problems at once, and it's simpler than most parts managers expect.
Bus Parts Min-Max Levels: Set Them From Real Usage
The min-max numbers most fleets run were guessed, inherited, or vendor-set — which is why they stock out and overstock at the same time. Here's how to reset them from your own usage data.
Why Your Current Min-Max Numbers Are Probably Wrong
Min-max only works when the numbers reflect reality: the minimum should trigger a reorder with just enough time to restock before you run out, and the maximum should cap you at what you'll actually use before the next order. When the numbers are set on anything other than real usage and lead time, one or both of those breaks — and the storeroom pays for it in stockouts, dead stock, or both. Here's where bad numbers come from.
Inherited & Never Revisited
The levels came with the job and nobody's touched them since. They may have been right for a fleet of a different size, age, or route mix — but that fleet is gone, and the numbers didn't move with it.
Guessed at Setup
When the system went live, someone put a round number in every field to get moving. Those placeholders became permanent, and now they drive real ordering decisions they were never meant to make.
Flat Across Every Part
The same min-max applied to a part used weekly and one used once a year. A flat rule guarantees you overstock the slow movers and stock out the fast ones — the exact opposite of what you want.
Set to the Vendor's Suggestion
Vendor-recommended levels are built to sell parts, not to match your usage. They lean high, which keeps their volume up and your cash tied up in stock you may not turn.
The tell that your numbers are wrong is the paradox every parts manager knows: shelves overflowing with parts you never touch, while the one you need is on backorder. That's not bad luck — it's what mis-set min-max always produces, because the levels aren't tuned to how each part actually moves. The fix isn't a better guess; it's replacing the guess with three real numbers you already have. This is the practical, per-part complement to the broader min-max stock-level framework — the framework sets the structure, and real usage sets the numbers inside it. Book a demo to see min-max levels recalculated from your usage.
The Three Inputs Real Min-Max Levels Need
A min-max level set from data isn't complicated — it comes down to three inputs per part. Get these and the numbers calculate themselves; miss them and you're back to guessing. Here's what each one does.
Usage Rate
How many of this part you actually consume per week or month, from your real history. This is the foundation — every min and max is built on how fast the part truly moves, not a guess about it.
Lead Time
How long from placing an order to the part on your shelf. The minimum has to cover the usage you'll burn through during that lead time — a part that takes three weeks to arrive needs a higher min than one that comes overnight.
Demand Variability
How much usage swings around the average — steady, or spiky? A part with lumpy demand needs a bigger safety buffer on top of the minimum, so a sudden run doesn't empty the shelf before the order lands.
The logic that ties them together is straightforward. Your minimum is the usage you'll consume during the lead time, plus a safety buffer sized to the variability — that's the point where you must reorder to avoid running out before stock arrives. Your maximum is the minimum plus a sensible order quantity, capped so you're not holding more than you'll turn over before the next cycle. Notice all three inputs are things your shop already generates or can measure — you're not forecasting the future, just reading the recent past. That's what makes usage-based min-max both more accurate and less work than the guessing it replaces, and it's the same demand signal that powers smarter parts demand forecasting. Sign up free and pull real usage and lead time per part.
How to Recalculate Bus Parts Min-Max Levels From Usage
Turning those three inputs into set levels is a four-step pass you can run across your catalog. The output is a min-max on every part that reflects how the fleet actually uses it — and reorders itself once it's set.
Pull Real Usage per Part
Get the actual consumption rate for each part from your history — how many you used over the last several months. Rank parts by movement so you tackle the fast, high-impact movers first, where wrong numbers cost the most.
Measure Each Part's Lead Time
Use real order-to-receipt times, not the supplier's promise. A part's minimum lives or dies on this number, so base it on what deliveries actually take — including the ones that ran long.
Set Min = Lead-Time Demand + Safety
Set the minimum to the usage you'll burn during the lead time, plus a safety buffer sized to how variable that part's demand is. Steady parts need little buffer; spiky ones need more. Then set the max to min plus a practical order quantity.
Automate the Reorder
Wire the levels to auto-reorder so hitting the minimum fires a purchase automatically. A perfect min-max still fails if someone has to remember to act on it — automation is what makes the calculation actually prevent stockouts.
The step that separates a real reset from a cosmetic one is basing lead time on actuals rather than the supplier's quote. Vendors quote best-case delivery; your minimum needs to survive their worst-case. If a part usually arrives in a week but occasionally takes three, a minimum built on "one week" will stock you out every time the long delivery hits — and those are exactly the moments a bus is waiting. Building the minimum on real, observed lead times — including the bad ones — is what makes usage-based min-max reliable instead of merely tidy. Getting all of this captured cleanly is what a well-run CMMS storeroom is built to do. Book a walkthrough to see min-max calculated on real lead times.
Keeping Min-Max Levels Live as Usage Shifts
The reason min-max drifts wrong in the first place is that it's usually set once and forgotten — but usage never stops moving. A level that's perfect today goes stale as the fleet and its demands change. The fix is to treat min-max as living, and to recalculate when the things that drive it move. These are the shifts that should trigger a refresh.
Seasonality
Some parts spike with the calendar — heating and cooling components, winter items. A single year-round level over-stocks the off-season and stocks out the peak. Adjust the buffer as the season turns.
Fleet Changes
Add buses and usage of their parts climbs; retire a model and its parts should drop off the shelf. Every fleet change ripples into parts demand — the min-max should move with it, not lag a year behind.
Lead-Time Drift
When a supplier gets slower or you switch vendors, the lead time behind every minimum changes. If deliveries start taking longer, the old minimum no longer covers them — raise it before it burns you.
The practical way to stay ahead of all three is to let the system recalculate continuously from live usage rather than relying on an annual manual review. When min-max is tied to actual consumption and real lead times, seasonality shows up as the usage rate climbs, a fleet change shows up as demand shifts, and lead-time drift shows up as deliveries lengthen — and the levels adjust before a stockout announces the problem for you. That's the difference between min-max as a one-time project and min-max as a self-correcting system. A parts room running live levels spends its time on exceptions, not on re-guessing the whole catalog every year. Sign up free and keep your min-max levels self-correcting.
The Parts Data That Sets Min-Max Automatically
Usage-based min-max only works if usage, lead time, and variability are captured cleanly per part — which is exactly what a parts system does as a byproduct of normal ordering and issuing. BusCMMS parts and inventory management turns that captured data into calculated levels and automatic reordering, so the numbers are right and stay right.
-
Real Usage Tracking
Every part issued to a work order is recorded, building the true consumption rate per part — the foundation number that makes a min-max real instead of a guess.
-
Lead-Time Capture
Order-to-receipt time is logged per part and supplier, so minimums are built on real delivery times — including the slow ones — not the vendor's best-case quote.
-
Demand-Variability Insight
Usage history shows which parts move steadily and which spike, so safety buffers are sized to real variability — bigger where demand is lumpy, lean where it's steady.
-
Calculated Min-Max
Levels computed from usage, lead time, and variability per part — not one flat rule across the catalog — so fast movers and slow movers each get the right numbers.
-
Auto-Reorder at Minimum
Hitting the min fires a reorder automatically, so the calculation actually prevents stockouts instead of depending on someone noticing the shelf is low.
-
Continuous Recalibration
As usage and lead times shift with seasons, fleet changes, and suppliers, the levels update from live data — so min-max stays right instead of drifting stale between annual reviews.
The reason a purpose-built bus platform matters here is that accurate min-max is only as good as the usage data underneath it, and that data has to be captured without extra work or it won't be captured at all. If setting levels means someone manually tallying a year of parts issues from receipts, it happens once and never again. Because BusCMMS records every part issued to a work order and every order's real lead time as part of normal shop flow, the usage and lead-time history builds itself, the min-max calculates off it, and auto-reorder executes it — a closed loop that keeps the storeroom lean and stocked at the same time. That's typically live in two to four weeks, and BusCMMS reports fleets cutting both stockouts and excess inventory once levels run on real usage. Book a demo to see usage-based min-max on your parts catalog.
A Parts Manager's Take
That's the surprise usage-based min-max delivers: less stock and fewer stockouts together, because the two problems shared one cause — numbers that never reflected real usage. Fix the numbers and both sides improve at once. It was never a tradeoff; it was just bad data.
The Bottom Line on Bus Parts Min-Max Levels
The reason a storeroom can overstock and stock out at the same time is almost always the same: bus parts min-max levels that were guessed, inherited, set flat, or copied from a vendor — never calculated from how the fleet actually uses parts. Setting them right takes three inputs you already have: real usage rate, real lead time (including the slow deliveries, not the vendor's best case), and demand variability. From those, the minimum is the usage you'll burn during the lead time plus a safety buffer sized to the variability, and the maximum is that minimum plus a sensible order quantity — calculated per part, never as one flat rule. Wire it to auto-reorder so hitting the minimum acts on its own, and keep it live so seasonality, fleet changes, and lead-time drift recalibrate the numbers before a stockout does it for you. Do this and you get the outcome that sounds impossible until you see it: less cash tied up in stock and fewer stockouts, at the same time, because both were symptoms of numbers that never matched reality. Min-max stops being a set-and-forget guess and becomes a self-correcting system that keeps the shelf exactly as full as it needs to be. Book a walkthrough to reset your min-max on a fleet like yours.
