Spare parts inventory management for maintenance

What spare parts inventory management is

Spare parts inventory management is the discipline of holding the right maintenance spares, in the right quantity, so a repair never has to wait for a part. In a CMMS it is a connected loop: each spare is linked to the asset it fits, every critical spare carries a min-max reorder level that raises a low-stock alert, spares are issued against a maintenance work order, and stock and consumption are reported per asset. Done well, it is one of the highest-leverage things a maintenance function can control — because a missing spare is the biggest reason a short repair becomes long downtime.

This is where maintenance and inventory meet. The store is not a warehouse of "just in case" boxes; it is the buffer that decides whether a technician standing at a stopped machine fixes it in the next hour or waits three days for a courier. Managed loosely, spares tie up cash on shelves you never use and still run out of the one part you need. Managed as a system, spares become a predictable, measurable input to uptime.

Everything that follows in this guide is a piece of that system: the spare BoM that ties parts to assets, the min-max levels that keep the shelf stocked, the issue against a work order that keeps stock honest and cost traceable, and the procurement flow that refills before you run out. For the wider context of how spares sit inside maintenance management, start with the pillar guide, What is CMMS software?

The spare BoM — spares linked to the parent asset

The foundation of the whole system is the spare bill of materials: a list of spares that belong to one parent asset or equipment, each with its unit of measure. In Fast Maintenance this lives in the Spare Part Master, where the Spare Part BoM links every spare to the asset it fits. It answers the first question a technician asks at a stopped machine — which parts fit this asset, and are they in stock? — without a phone call to the stores clerk or a hunt through a spreadsheet.

That link is what makes every downstream step possible. Because the spare knows its parent asset, a reorder alert can be traced back to the machine it protects; a spare issue can be booked to the right work order; and spare cost can roll up per asset. Without the BoM, spares are a flat store list with no idea which machine they belong to — and every question about "which spare, for what, how much" needs a human to answer.

Building it is a one-time investment that pays back on every breakdown. Walk each critical asset, list the spares it consumes, set the unit of measure, and attach them in the Spare Part Master. It pairs naturally with a clean asset register — the register defines the parent equipment, the spare BoM hangs the parts beneath it. If you have not built the register yet, see How to build an equipment & asset register first, because the spare BoM keys off it.

Min-max and reorder levels — how to set them

Set the reorder level from usage and lead time, not gut feel. A workable formula is simple, and you can apply it spare by spare:

Reorder level ≈ (average daily usage × supplier lead-time in days) + safety stock
Maximum level = reorder level + economic order quantity

The reorder level covers the parts you will consume while a fresh order is on its way, plus a safety buffer for the times usage spikes or the supplier slips. The maximum level adds an economic order quantity — enough that you are not raising a purchase order every week, without over-stocking cash on the shelf. The moment on-hand falls to the reorder level, the CMMS raises a low-stock alert. Here is the arithmetic on four representative spares:

Notice how the critical bearing carries proportionally more safety stock despite low usage — its 21-day lead time and the cost of its downtime justify the buffer. The fast-moving filter carries a large EOQ because it is cheap and consumed constantly, so frequent tiny orders would waste effort. That is the judgement min-max encodes: usage and lead time set the floor; criticality and cost tune the buffer. (Figures here are illustrative, to show the method.)

ABC and criticality of spares

Not every spare deserves the same treatment. Classifying spares by criticality tells you where to hold buffer stock and where to run lean. Three broad classes cover most stores:

Criticality is not a label you set once and forget — it is what tunes the min-max levels from the previous section, and it should track the asset criticality carried in the register. A spare that feeds an A-class production machine inherits that urgency. When you review breakdown history and find a "C" spare that keeps causing downtime, promote it. The classification is a living decision about where to spend inventory cash for the biggest reduction in risk.

Issue-against-work-order consumption

A spare should leave the store against a work order, not a loose note. When a technician takes a part for a repair, the stores engine raises an issue document tied to that maintenance work order. That single action does two jobs at once — and it is the difference between a store you can trust and a store you argue about.

The pay-off is honesty and traceability. You never end a month wondering where a box of bearings went, because every issue names its asset and work order. And you never mistake a maintenance cost for a mystery, because the spend is attributed the moment the part is consumed. This ties directly into how repairs are recorded — see Asset Inward & Repairs — and it is what makes the per-asset cost roll-up below possible.

Procurement: reorder alert → PR → PO → GRN

When on-hand falls to the reorder level, replenishment should flow without a scramble. In Fast Maintenance the low-stock alert feeds procurement through the Purchase "Maintenance" PE category, following the standard document chain:

India note — GST input tax credit. Spare purchases and external service bills typically carry GST, and a registered plant can usually claim input tax credit (ITC) on eligible spares and maintenance service invoices — provided the supplier has filed correctly, the invoice is valid, and the input is used in the course of business. Booking the GRN against a GST-compliant PO keeps the paper trail clean for that claim. This is indicative only — confirm the treatment of specific spares and service bills with your CA or tax advisor. The procurement side runs through Fast Inventory & Purchase, so a reorder alert becomes a PR without re-keying.

Spare cost roll-up per asset

Because every spare issue names its asset and work order, spare spend does not vanish into a general maintenance overhead — it rolls up per asset. That single design choice turns the store from a cost centre nobody can explain into a data source that answers the questions management actually asks: which machines are eating our spare budget; is this asset cheaper to keep repairing or to replace; where is the money going?

This per-asset spare cost feeds straight into the maintenance cost KPI. Add the labour on the work order and any external service bill, and you have a defensible total cost of maintenance for each asset — the number a plant head takes to a management review or an annual budget. An asset whose spare consumption keeps climbing is telling you something: either its preventive schedule is too loose, or it is reaching the end of its economic life. Both are visible only because the cost was attributed at the moment of consumption. See how these numbers surface in Dashboards & MTTR/MTBF, and how tighter preventive maintenance lowers the spare bill by preventing the failures that consume parts.

Dispatch & receive for external repair

Not every spare is scrapped and replaced. Sub-assemblies — a motor, a gearbox, a servo drive, a control card — are often sent out to an external vendor for repair and returned to service. The danger with these is simple: an expensive item leaves the plant on an informal gate pass, sits on a vendor's bench for weeks, and nobody can say where it is or what it cost to fix.

Managing dispatch and receive inside the system removes that risk. When a sub-assembly goes out, it is booked on a dispatch document; when the repaired item comes back, it is received against the same reference. The item is never "lost in transit" on a WhatsApp message, the repair cost is captured, and the turnaround is visible — so you know whether that vendor is fast enough to rely on for a critical spare, or whether you need a stocked replacement instead. This is part of the same Asset Inward & Repairs engine that records in-house repairs.

How Fast Maintenance Software implements it

Fast Maintenance Software is a working implementation of everything above, built by Improsys in Pune on the shared Fast Suite platform and available cloud or on-premise. Mapping the discipline to the product:

The result is the thread that runs through this whole guide: because spares are linked to assets and consumed against work orders, the store stops being the place repairs go to wait. It becomes a measured lever on MTTR and availability — see MTTR, MTBF & availability explained and machine downtime tracking for how that lever shows up in the numbers.

Frequently asked questions