MRO Spare Parts Optimization Software: Custom Build or Buy IBM and Verusen

What IBM, Verusen and Smart Software actually do well

IBM MRO Inventory Optimization is a serious product, particularly if you already run Maximo, and its analytics on stocking policy are real work by people who understand maintenance repair and operations inventory. Verusen attacks the data problem head on, using machine learning to harmonise materials across systems, which is exactly the right target and genuinely useful for finding duplicates at scale. Smart Software handles intermittent demand better than a generic forecasting package. Servigistics and Baxter Planning are credible in service parts planning. SAP and Infor both ship spare parts modules that will do the arithmetic if you feed them.

The honest opening, from a firm that would rather sell you a build. Most organisations should buy, and a fair number should not buy anything at all. One plant, a few thousand items, one storeman who knows the racks: a data cleanup exercise and a disciplined review of min and max levels will get you most of the benefit for the cost of a contractor for a quarter. Nothing in software will beat that, and licensing an optimisation platform at that scale is a subscription looking for a problem.

Buy a packaged product if most of these hold:

• One enterprise resource planning (ERP) or enterprise asset management system across the whole group.
• A material master that has already been cleansed and is governed by somebody.
• An equipment hierarchy you trust, with bills of materials on your critical assets.
• Under roughly 20,000 stock keeping units across one or two storerooms.
• Nobody has raised a new part number this year because they could not find the existing one.

Where they stop: your criticality model and the writeback loop

Pull your material master and search for a common bearing. In most multi-site organisations you will find it at least three times: once as BRG BALL 6205 2RS, once as BEARING,BALL,SKF 6205-2RS, once by a distributor's catalogue number from a purchase made in 2014, and often once more raised by a contractor who could not find the existing record. Each duplicate carries its own reorder point, so you hold more stock than you think, your spend analysis is wrong, and when a line stops at two in the morning the fitter finds the record with zero on hand and calls out emergency freight for a part you already own twice over.

Optimisation software wants clean inputs: an item, a demand history, a lead time, a criticality and a service level target. Real maintenance inventory data has none of those in usable form. A large share of items issue once every few years, which makes standard statistical forecasting close to meaningless. Lead time is whatever the last purchase order took, and that purchase may have been expedited. Criticality is a field that is either blank or set to high on everything, because during a cleanup five years ago high was the safe answer.

So the hard work is not the optimisation. It is producing inputs worth optimising, and that work carries your organisation's fingerprints: your description conventions, your equipment hierarchy, your naming history, the way your planners actually raise a reservation. IBM assumes an achievable level of data quality and equipment linkage. Where that assumption holds it delivers. Where it does not, the project becomes a data remediation programme with an analytics licence attached, and the remediation is the part nobody scoped.

The gap both products share is the loop. Analysis produces a recommendation. Somebody has to review it, approve it, and change the master record. If that loop runs through spreadsheets emailed to site materials managers, it runs once, for the pilot, and then stops. The recommendations age, trust collapses, and the licence gets cancelled at renewal. Without writeback into SAP or Maximo, with an audit trail of who approved what, the whole exercise is a very expensive report.

The arithmetic: cost per stock keeping unit versus the cost to build

Get both onto the same unit, which here is cost per stock keeping unit per year.

Take the licence quote you hold, add the implementation services line, add the internal analyst who will prepare extracts, and divide by items under management. At 40,000 items and a fully loaded $120,000 a year, that is three dollars per item annually. At 120,000 items it is one dollar. Optimisation platforms get cheaper per item as you grow, which is a genuine argument in their favour and worth stating plainly.

Now the build. A first release runs $70,000 to $150,000, and the ongoing cost is support rather than licences, so at the midpoint amortised over five years plus year two support you are carrying roughly $30,000 to $55,000 annually regardless of item count. At 40,000 items that is around one dollar per item. At 200,000 items it is twenty cents.

On cost per item the lines cross near 25,000 to 30,000 stock keeping units. But that is the cheap version of the argument. The number that actually decides it is inventory carrying value. Take the value of duplicated stock plus the value of spares attached to decommissioned equipment. In the storerooms we have worked in, that population alone has repeatedly exceeded the entire build cost, and it is cash sitting on a rack rather than a projected saving. Add one avoided line stoppage and the comparison stops being close.

So the honest crossover: above roughly 20,000 items across two or more storerooms, or any group carrying two material masters after an acquisition, build. Below it, buy or clean up.

Cost to build, and the two lines nobody quotes

A first release covering extraction from your enterprise resource planning or asset management system, description parsing into structured noun and modifier form with attributes, manufacturer part number extraction, duplicate candidates surfaced with a confidence score into a human decision queue, equipment linkage and a criticality model your reliability engineer will sign, plus stocking recommendations with the reasoning shown, runs $70,000 to $150,000 over 12 to 18 weeks. A full platform adding cross-site pooling with transfer suggestions, obsolescence review, lead time driven reorder policy, consignment and vendor managed stock, and writeback to the system of record runs $180,000 to $400,000 across 6 to 12 months.

The lines nobody quotes:

• Data migration and cleansing: 10 to 25 percent of the build. This is the honest one in this category. Every merge needs a human confirmation, because automatic merging of material masters is how you delete a record somebody had reserved. Every merge must be recorded reversibly. The dependency that decides the schedule is access to a decision maker who can approve merges, not engineering capacity.
• Year two: 15 to 20 percent of build cost annually. Normalisation is a permanent function rather than a project, because new records get raised every week. Budget for it or the master drifts back within eighteen months and you will have paid twice.

What pushes cost up: more than one enterprise system across the group, which is common after acquisitions, and storerooms with no reliable equipment hierarchy at all. What holds it down: start with the two largest storerooms and the top spend categories, which usually covers a large share of the value.

The four situations where building wins

• Regulatory and standards fit. If you are governed under ISO 55000 asset management, or you classify to UNSPSC or eCl@ss, or your quality system requires traceability from a stocked item to the equipment it serves, your criticality model has to be defensible to an auditor rather than plausible in a dashboard. A model that inherits criticality from the equipment the part serves, adjusted for alternates and replacement lead time, is something your reliability engineer can sign. A vendor's opaque score is not.
• Scale economics. Past 20,000 items, cost per item falls faster on a build than on a licence, and the pooling view alone releases working capital that no licence renewal ever will.
• A workflow that is your competitive advantage. Your pooling rules between sites, your policy on insurance spares that will issue once in twenty years, and your approval chain are governance decisions, not settings. If uptime is what you sell, that policy is the product and renting it makes no sense.
• Integration sprawl across three or more systems. Two enterprise systems after an acquisition, a maintenance system, a purchasing system and a distributor portal. Recommendations that cannot write back into all of them stay as reports, and reports get ignored by every storeman who has done this for twenty years, who is often right.

How to decide in a week

Run this yourself, with a laptop and one hour a day. Monday, search your material master for one common bearing and count the records that come back. Tuesday, pick twenty items at random from your highest-value storeroom and try to establish, from the system alone, which equipment each one serves. Wednesday, ask what happens to production if that equipment stops, and see whether the criticality field agrees. Thursday, list the equipment decommissioned in the last five years and check whether its spares are still stocked. Friday, take one stocking recommendation from whatever tool you use now and trace what it would take to turn it into a changed min and max in your system of record, including who approves it.

Friday is usually the day that settles it. If nobody can name the approver, no packaged tool will help you, because the loop that makes the analysis real does not exist yet.

Then buy a paid discovery phase rather than a platform. At Digital Heroes that produces a signed product requirements document before any code, covering the data model, the matching and confidence rules, the criticality model, the approval and writeback path, permissions and acceptance criteria. You own it whether we build or not, and it lets three firms quote the same system.

We are the wrong firm for you if you want a body shop billing by the hour, if you want somebody stationed in your plant, or if you are a single site that should be running a cleanup instead. We are more than fifty specialists across India LLP, US LLC and UK LTD entities, so your intellectual property assigns under your own law, and you meet the named team before signing. The cleansed master is the most valuable output of the whole programme and it must never be locked inside a platform you are renting. Check us on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S record.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.