Enterprise & Manufacturing use case

Spares Leaving Stores With No Idea Which Machine Ate Them

Who this fitsA plant with a stores department issuing spares
Asset rangeAny spares inventory
What it producesMaintenance cost per machine
Issues
Attributed

To the machine that needed the part, not just a department

Cost
Per asset

What each machine has absorbed this year

Patterns
Surfaced

The same part going to the same machine repeatedly

Reorder
Prompted

Based on what actually gets consumed

1. The Problem

Stores issues a bearing, a seal kit or a drive belt to the maintenance department, and that is where the record stops. The cost lands in a departmental budget line. Nobody can say which machine consumed it, so nobody can say which machines are expensive to run. At the end of the year maintenance has overspent and the explanation is that there were a lot of breakdowns.

The consequence is that replacement decisions are made on feel. A production head believes a particular machine is a problem; finance sees no evidence and declines the capital request. Meanwhile parts are ordered in the quantities they were ordered last year, because there is no consumption pattern to work from, and slow-moving stock sits on a shelf while a fast-moving item runs out.

2. How ASTITVAAMS Handles It

This builds on having the machines in the register first. Four things change:

Every issue names a machine

The storekeeper scans the part and the asset it is going to. It adds a few seconds and it is the whole basis of everything below.

Cost accumulates per asset

Parts, labour and contractor invoices all attach to the machine, so its running cost this year is a number rather than an impression.

Repeat consumption gets flagged

The same part going to the same machine for the third time is surfaced, which usually points at a root cause nobody had connected.

Reordering follows actual use

Consumption history drives what you hold, so fast-moving items stop running out and slow movers stop tying up cash.

The short version

The maintenance budget stops being a single number you defend. ASTITVAAMS books every spare against the machine that took it, so it becomes a list you can rank. Replacement arguments are made with consumption history rather than conviction.

Where this applies
Manufacturers with a stores function and machines old enough to differ in running cost

3. What Changes for You

  • Expensive machines identify themselves: When cost sits against the asset, the handful absorbing a disproportionate share of the budget become obvious within a couple of quarters.
  • Capital requests carry evidence: A replacement case built on two years of parts and labour against that machine is a different conversation from one built on frustration.
  • Stock matches consumption: Holding is set by what actually gets used, which frees cash tied up in parts bought out of habit.

Take This Away

A PDF covering how issues are attributed to assets, what the cost-per-machine report looks like, and how consumption history feeds reordering. Useful for stores, maintenance and finance.

Other Use Cases

Enterprise & Manufacturing

Machines That Fail Without Warning and Stop the Line

Enterprise & Manufacturing

Tools and Dies That Keep Disappearing Between Shifts