How is the equipment spare parts management system implemented? Associated with equipment assets
Conclusion first: the linkage of spare parts and equipment assets is a fundamental function of "Main data first, then functional"
The spare parts management system is really hard to do, not to purchase, not to unload, but to connect the equipment assets. There's no clear structure in the equipment account (the list of materials, which indicates what a device consists of), and the spare parts cannot be attributed; there's no standard code or inventory strategy for spare parts, and the better systems can only become an accounting tool. We have seen many projects, stuck on "line and discard", often at the root: master data are not fully integrated and then quickly put up. This paper opens up in order of implementation, each part of the section is a lesson that emerges from stepping through the pit.
First, answer the question: Why should spare parts and equipment assets be managed in conjunction?
The goal of spare parts management is not "less money," but "get the equipment out of hand." The most direct expression of this is that there are thousands of items in the warehouse, and no one knows which equipment is used; maintenance workers do not know where they are, and have enough stock; financial devices are only brain-shot when they cost for their entire life cycle -- because spare parts are not consumed to specific equipment.
The connection will solve three things:
- The automatic attribution of spare parts consumption to equipment allows for the calculation of maintenance costs for single-office equipment and an assessment of whether it should be overhauled or scrapped
- Direct identification of stock and location of spare parts requirements when equipment fails, reducing the time required for maintenance and downtime
- The spare parts procurement plan can refer to the age and failure rate of equipment rather than to "minimum stock" only
Shanghai Alternative Technologies has been implemented in similar ways in a number of manufacturing and storage logistics projects, with the feeling that, in a well-connected project, spare parts stock turnover (the number of times inventory goes to and from the warehouse within one year) can be increased by 20-30 per cent, while emergency procurement frequency declines are evident (source: rough statistics based on client returns data, 2023).
First level: master data of the device must be cleared first
The spare parts system can run, 80% depending on the equipment's master data. This is a step to be lazy.
Which level do you want to build?
A common error zone is to build only to the level of "equipment" -- for example, "specify machine 01" -- and then to be more detailed in the management of spare parts: it usually comes to the fourth stage of "system-equip-component-part." For example, a hydraulic system for retrofitting machines has been built up less than enough to contain the gas pump seal. The spare parts cannot be attached. The specific layers are based on the size of the enterprise: less than 500 units, three levels are basically sufficient; over 2,000 recommended levels four or even five, because the finer particles are more useful when they are analysed for failure.
How do you maintain the device BOM?
BOM is a bridge between spare parts and equipment. It is recommended to start with critical equipment – for example, high failure rates, the 20 per cent of maintenance costs, and prioritize BOM. One device has a BOM line control between 30 and 80 items, too much maintenance costs, too little and not enough. The initial data can be extracted from the equipment instructions, maintenance records, and then checked by the maintenance team's teachers, which is done in no way.
Second level: spare parts code and inventory strategy
The spare parts data are not standardized, and the perfect system is garbage entry and outage.
The code is simple and readable.
The spare parts code suggests a "class code + flow" form, such as the bearings starting with "B", and the seals beginning with "S." The length is 8-12. Once it is determined, do not easily change the code, or all historical data will be invalidated. Name as much as possible in the format of "name + specification + model," so that no numbering can be named "axis 001".
Inventory strategy: ABC classification (value-based distribution of spare parts into A/B/C, step III) is more effective than one-size-fits-all
Not all spare parts are subject to a secure inventory (also called the minimum stock, i.e., replacements below this level).
- Category A (high value and low usage): strict control of inventory, with 30 days coverage based on a ratio to the list of spare parts for single-desk equipment (i.e. BOM above)
- Category B (medium value, average usage): maximum/minimum inventory per historical consumption, monthly review
- Category C (low-value, perishable): appropriate availability and cyclical replenishment (e.g., quarterly)
A rough reference ratio: Category A accounts for 10-20 per cent of the spare parts range, but 60-70 per cent of the funding (source: generic experience in manufacturing spare parts management, 2022). Focusing on category A with the most significant return.
Third level: several business scenarios linked to equipment assets
The system is more functional than it is in business. The following four scenarios are really valuable to users.
We'll see the spare parts directly at the time of the session.
When the maintenance worker initiates a call on a mobile phone or a desk machine, the system automatically lists spare parts available under BOM for this equipment based on the malfunctioning device, current stock, storage position (specific shelf location of the spare parts stored). This step seems simple, but it reduces the response time for maintenance from hour to minute - especially during nighttime or break-out.
Auto-assessed spare parts consumption to equipment
Each time the library is connected to specific worksheets (i.e. maintenance task orders) and equipment. So, when you do a double drive six months later, the manager can see clearly what it costs to retrofit the retrofit machine 01 this year, what spare parts are used, which ones the failure is focused on. Without this data, whether the device should be overhauled, whether or not the phase-out should be phased out, basically only by feeling.
Status of equipment reference in the acquisition plan
Traditional spare parts purchasing looks only at stock levels. Linking procurement to equipment data adds factors such as years in service, recent failures, and preventive maintenance plans. Take the carbon brushes for a particular motor model, a wear part. If the system finds that the group of motors of that batch and model has run for more than 8,000 hours and only two brush sets are in stock, it automatically recommends a purchase rather than waiting for stock to reach zero.
Reverse retroactive of spare parts and equipment
In addition to the positive search for "equipment spare parts", you have to support a reverse backtracking of "spare-spare-spare" equipment. For example, in some batch, aerodynamic elements find quality problems, and it is possible to quickly identify which equipment is loaded with this, and how far that impact is. This is what mass can be traced and recalled in the scene.
Pumping pits: the most easily run over places in operation
This is part of the most valuable thing in experience — many projects are not lost to function, but to detail.
Pipe One: Master data is entered once, and can't run.
Many companies came up and tried to complete all the BOMs, and it took three months to get the first data out of the record, and project morale collapsed. The right thing was to do this in batches: the first set of vital equipment (such as 80% of maintenance costs) run through the process and let the maintenance staff complete it in use. The system has a mechanism for "better-than-use" rather than requiring data to be available once.
Pipe II: Unharmonized coding systems, difficulties in moving old systems
If an enterprise has previously used an ERP or a simple system of acquisition, the spare parts coding rate is a historical mess. The new system must be online with a full code combo and a "old code-new code" cross-reference. Never add "backs" to the old code, it will only bring the confusion into the new system.
Pit three: The retrofitting of the warehouse doesn't keep up with the pace of the system.
The system requires that the vault be precisely on the shelf level, but the actual warehouse is still in a "we can find it" state. This situation starts with a round of storerooms: the coding, the rack label, the storage and the system map. Even the basic two or three of 5S, which is the most useful system.
Pipe Four: User training only once
Maintenance technicians, warehouse staff, and equipment engineers use the system in different ways and need separate training. Do not limit training to one session before go-live. Repeat it in the first and third months after launch, gather feedback, and make improvements. Many new requirements only surface once people use the system.
After the line: How do you figure the system really works?
The system is not on the line, but rather on the starting point. The following indicators can be used to measure implementation:
- Spare parts release associated with work-unit ratio: over 90 per cent (meaning that the vast majority of the inventory is documented)
- Frequency of emergency procurement: whether there was a significant decline in 3 to 6 months after the start-up (a reasonable target is 30 per cent to 50 per cent)
- Equipment maintenance cost aggregation coverage: whether or not to account for more than 80 per cent of critical equipment
- Spare parts stock turnover: increase compared to pre-line (reference target is above 20 per cent)
If these metrics haven't improved after three months, review master data quality and whether workflows are being followed. Don't rush to add features.
One last suggestion.
The spare parts management system and equipment asset interface is essentially a "data governance before systems build" project. Selecting what system, using which platform, rather than the hardest part; the hardest thing is to standardize the primary data, make it available to business people, and keep the data up to date. If you're doing this, you suggest that 60% of your efforts be focused on primary data and process combo, 40% on system selection and implementation -- the sense of the scale, a reset from multiple real projects.
In the course of implementation, it is much less important to find teams with similar project experience than to find out for themselves if there are incorrect links in the main data governance that multi-system integration (MES, manufacturing implementation system, WMS, storage management system, interlocking ERP).

Ms. Lei
Mr. Pang