Improve Spare-Parts Availability
The right part on the shelf when the machine needs it.
Spare-parts shortages rarely announce themselves in advance — they surface as a technician standing at an idle machine waiting for a part that should have been reordered weeks earlier. AssetAI won't run your stores, but it gives you the cost and demand signals to manage spares intelligently against whatever inventory system you already run, whether that's a spreadsheet, an ERP module, or a dedicated stores team.
How the Data Connects Repairs to Parts
Every work order — PM, CM, breakdown, or predictive — carries parts as costed line items using a fixed formula: qty x unit cost x (1 - discount%). This is the same calculation used for labour and service lines, so a part's cost sits permanently with the repair record it belongs to, not in a separate spares ledger disconnected from context.
This matters because breakdown and corrective work orders in AssetAI cannot close without a recorded failure cause and remedy. That means every part consumed against a failure is tied to a verified root cause — so when you build a failure-mode Pareto (a standard view in the platform), you can read it alongside exactly which parts were consumed against which failure types. Over time this tells you which failure modes are parts-hungry and worth pre-positioning stock against, rather than guessing from memory or gut feel.
Where to Look Before You Order
Two views inside AssetAI point you toward smarter stocking decisions without pretending to be a stores system:
- The reorder-level KPI tile. The Downtime Cost, OEE & Analytics dashboard includes a "spares at or below reorder level" count inside its rolling 30/90/180/365-day window, sitting alongside availability, MTTR, MTBF, PM compliance, backlog age, and open breakdowns. It's a read-only number in your shared KPI set, not a triggered reorder workflow or a purchase requisition — treat it as an early warning to check your stores system, not an automatic instruction.
- The BOM view per asset. In the EBS tree, each node down to Component and Part level carries a live BOM-line counter next to child count and work-order counts. Clicking into an asset tells you how many parts are structurally attached to it — a parts breakdown, not a quantity-on-hand record, but useful for scoping what a machine could need before it fails.
Pair these two views with the downtime-cost Pareto — the ranked list of your top assets by downtime hours x cost/hour — and you get a defensible answer to "which machines are worth stocking spares against first," based on actual repair and cost history rather than intuition.
What This Means for Indian Plants
Manufacturing plants across India, per IBEF's industry data, often run lean stores with long supplier lead times for imported components — which makes reactive stock-outs expensive in both downtime and expedited freight. AssetAI's role here is deliberately narrow: it won't scan barcodes, log goods-receipt transactions, or generate POs. What it does is make sure the cost and failure data behind every part consumed is accurate and auditable, so whoever runs your stores — a dedicated inventory system or a manual process — is working from real repair history instead of anecdote. Explore how this fits with other use cases and features, or book a demo to see it against your own asset hierarchy.
The signals only help if someone acts on them before the shelf goes empty — and that means knowing where to look inside AssetAI and building a habit around it, not waiting for a shutdown to force the question.
Reading the BOM Before You Build a Reorder List
The EBS asset tree carries a BOM view at every node, down to Component and Part level, with a live BOM-line count shown alongside child count and work-order counts. Before assuming a part needs stocking, check this view against the asset's actual work-order history:
- Does the part appear on multiple closed CM/BM orders, or was it a one-off replacement?
- Is the asset itself high on the downtime-cost Pareto (top 8 assets by downtime hours x cost/hour) — worth prioritising over a low-impact machine with the same part shortage?
- Does the BOM line count suggest a complex assembly where several parts share a failure mode, meaning one stockout risks cascading into several?
This structural view won't tell you quantity on hand — AssetAI doesn't run a stock ledger — but it tells you which parts are structurally tied to which assets, which is the first filter before any purchasing conversation.
Common Mistakes When Treating the KPI as a Workflow
Plants new to this approach sometimes expect the "spares at or below reorder level" tile to behave like a purchasing trigger. It doesn't, and treating it as one leads to gaps:
- Assuming a breach auto-generates a requisition. It's a read-only count inside the shared analytics tile set — the same view that carries MTTR, MTBF, PM compliance and downtime cost. Someone still has to look at the number and act.
- Ignoring the failure-cause link. Because BM/CM orders can't close without a recorded cause and remedy, the part-consumption data behind a reorder breach is already diagnosed — skipping that context and reordering blind wastes the one advantage the data gives you.
- Treating BOM as inventory. A BOM line tells you a part belongs to the machine, not that it's sitting in a bin. Confusing structure with stock is the fastest way to under- or over-order.
Fitting This Into an Existing Stores Setup
None of this replaces a stores system, and it isn't meant to. Whether spares are tracked in a spreadsheet, an ERP inventory module, or a dedicated store, AssetAI's role is to hand that system better demand signals — cost-per-repair, failure-linked consumption, and a ranked list of which assets are worth stocking against — rather than duplicate its ledger. That division of labour matters more in Indian plants where stores are often run separately from maintenance planning, following practices closer to TPM than to fully integrated ERP-driven inventory. If you're evaluating how this fits your current setup, the full feature list and other use cases show how the same work-order and asset data feeds several maintenance decisions beyond spares — or you can book a demo to walk through your specific asset tree.
Improve Spare-Parts Availability FAQs
How do I know which spare parts to stock more of to prevent line stops?
AssetAI shows you a KPI tile on the Downtime Cost, OEE & Analytics dashboard flagging parts that have dropped to or below reorder level in your chosen time window (30/90/180/365 days). This tells you immediately which parts are running thin. Combined with the downtime-cost Pareto—which ranks your top 8 assets by total downtime hours × cost per hour—you can prioritize stocking spares for the machines that hurt you most when they stop. The system ties each part consumption to a verified failure cause, so you're not just guessing; you're stocking based on what actually breaks and costs money.
Can I see which parts are used most often against specific equipment failures?
Yes. Every corrective and breakdown maintenance work order must be closed with a documented failure cause and remedy before it's complete. The parts you consume against that repair are permanently linked to that cause. When you run a failure-mode Pareto analysis (built into AssetAI's analytics layer), you see which parts get used against which specific failures across your plant. This prevents you from overstocking parts for rare failures while understocking for repeat problems. You're matching spare-parts strategy directly to your actual failure patterns, not assumptions.
Where do I see the complete list of parts for each machine in one place?
The EBS (Equipment Breakdown Structure) tree shows a BOM (bill of materials) view for every asset node, organized through five fixed levels: Equipment → Assembly → Sub-Assembly → Component → Part. Next to each BOM line you see a live counter of how many child items exist, plus work-order history and open work orders at that level. This gives you a structured parts breakdown so you can drill down from a whole machine to the exact component or individual part, see what's attached to what, and understand your stocking obligations at every level of assembly. No guesswork about what belongs where.
How does spare-parts cost show up in my maintenance reports?
Every work order—preventive, corrective, breakdown, or predictive—carries parts as costed line items (quantity × unit cost × applied discount). That cost sits directly on the repair record, so when you look at your downtime-cost reports and OEE dashboards, you're not just seeing labor and machine downtime; you're also seeing the spare-parts spend attached to each failure. This makes it obvious which assets are bleeding money through repeated repairs and which parts contribute most to total maintenance cost. You can then decide whether to invest in stocking those parts or redesign your maintenance strategy.
What should I measure to know if my spare-parts strategy is working?
The core KPI is "spares at or below reorder level"—tracked on your rolling 30/90/180/365-day window in the Downtime Cost, OEE & Analytics dashboard. If that number is high, you're understocked; if spares never hit reorder, you may be overstocked. Pair this with downtime-cost Pareto (top 8 assets ranked by lost production cost) and failure-mode Pareto to see whether the parts you're stocking match the machines and failures that matter most. Unlike generic metrics, these CMMS dashboards tie spare-parts action directly to machine performance and cost, not inventory turnover alone.
Can AssetAI connect to my stores system, or do I have to manage inventory separately?
AssetAI does not include a dedicated inventory or stores module with stock ledgers, goods-receipt transactions, or movement logs. What it does is show you which parts are used, how often, against which failures, and which machines consume them most. You use that data to inform your inventory decisions, then manage the actual stock movements in your existing stores system or ERP. Think of AssetAI as the decision layer—telling you what and how much to stock based on real failure and cost data—rather than the execution layer. Many plants run this way, using features like work-order parts costing and Pareto analysis to guide their purchasing and stocking decisions.
How do I reduce the lead time impact when a critical spare part is unavailable?
Track supplier lead times in AssetAI and set reorder points based on usage frequency plus lead time buffer. Flag parts with long lead times for higher stock levels. Use the equipment history to identify which parts fail predictably, so you can order before failure occurs rather than after.