Integrating maintenance and spare parts management
David Berger describes the critical areas of integration that yield maximum benefit.
By David Berger, P.Eng., contributing editor
In Part I of this multi-part column, an argument was made in favor of running spare parts management as a fully integrated module within your CMMS, as opposed to integrating to a separate and distinct software package such as a corporate ERP system. For similar benefits, it was also suggested that those responsible for spare parts inventory, such as stock keepers, should report to the maintenance organization, and spare parts procurement specialists should report at least dotted-line to the maintenance department. This is to improve the accountability for optimizing key measures such as service level, inventory level, obsolescence, and response time.
In this column, we continue to explore optimization through integration of maintenance and spare parts management modules. Described below are critical areas of integration that yield maximum benefit.
Fundamental to integrating maintenance and inventory management modules is the sharing of master data. For example, each piece of equipment may have a standard list of spare parts recommended by the manufacturer to keep on hand. When the scheduler begins to schedule a given work order, this standard parts list, or some subset, can be seen from within the work order scheduling screen. For parts relevant to the job, the scheduler can then determine, from the same screen, whether parts are in stock, reserved, on order, or in transit. This level of integration can be very difficult or expensive to achieve if the maintenance and inventory data are resident in two separate software packages.
Some packages can display a complete hierarchy of equipment and parts using an indented and hierarchical format, similar to the manner in which MS Windows Explorer displays nested and hierarchical devices, folders and files. The more advanced CMMS packages have a drag-and-drop capability so that users can easily move components and parts from one asset to another, assuming they have administrative rights to do so. Other sophisticated packages have built an interactive interface between the hierarchy in one window and a graphic parts book in another window. As you double-click on hot spots to drill down within the graphic, you can observe the equivalent movement in the hierarchy and vice versa. A few packages display the master data or historical cost data in another window, which dynamically changes as you move up or down the hierarchy or between the graphic layers.
Another integration dilemma is to what level cost data should be kept current. In order to estimate accurately and report on the cost of completing a work order, the cost of spare parts must be obtained from some database. Even if maintenance and inventory control modules are fully integrated within the CMMS, there is still the issue of what amount was actually paid to the vendor by accounting. Perhaps there was a disagreement between what was ordered, what was received, and what was invoiced. Will the inventory cost data reflect the actual cost paid?
The benefit from achieving this level of integration is not worth the cost of doing so because the variances over the course of the year are typically small. Maintenance can still make effective management decisions, even if the equipment history reports show costs that are potentially out by a few percentage points. Accounting and finance, however, require absolute accuracy for financial reporting.
Another complication for those companies that choose to separate maintenance and inventory management modules lies in defining and controlling which parts are:
- not kept in stock and do not appear on the parts master (handled through a direct purchase)
- not kept in stock but appear on the parts master (for faster retrieval of header information such as manufacturer’s part number)
- kept in stock and appear on the parts master (controlled by min, max, reorder point, reorder quantity, lead time)
- kept in stock like a part but also comprise an asset to which work orders are assigned and for which equipment history is tracked (rotating assets).
It’s difficult and expensive to determine which parts are required for a given job, provide an estimate of work order costs, purchase the parts, and track equipment history accurately for parts used internally or by outside contractors, if maintenance and inventory control modules are not properly integrated.
When a planner creates a job plan for, say, preventive maintenance work on a given asset, it should include a list of parts required. When the work order is then initiated, it should automatically check and reserve stock or launch a purchase request for non-stock parts. This is easier to do when maintenance and inventory control modules share the same system.