In most industrial companies it makes more sense for a new AI tool to start as a layer on top, since systems like the CMMS, ERP and document control hold years of data and are tied into many other processes. Those systems sit at the centre of maintenance history, purchasing, finance, compliance records and reporting, and people across the business have built their daily work around them, so they are far more connected than they look from the outside.
Replacing them is a long project with a lot of risk, and the AI tool usually does not need to own that data to be useful. A replacement means migrating data, rebuilding integrations, retraining staff and often running two systems in parallel for months, and if anything goes wrong it affects core operations, while a tool that reads from and writes to the existing systems can deliver value within weeks and be judged on results before any larger decision is made.
A layer on top can read from the existing systems, do the work that those systems are bad at, like turning documents into usable steps or connecting information across systems, and write results back where they belong. A CMMS is good at holding work orders and maintenance history but poor at guiding a technician through a procedure on a phone, and a document control system stores approved files well but does not turn them into something a crew can execute and record step by step.
Writing results back where they belong is what keeps this approach clean, since completed work, readings and status updates end up in the system of record that everyone else already relies on. It also helps to agree with IT which system owns each piece of information and how the layer authenticates and connects, so the AI tool is treated as part of the architecture rather than a side project.
Replacement only makes sense when the incumbent system is clearly the problem and the business is ready for the change. Signs of that include a system that is out of support, one that cannot hold the data the business needs or one so heavily customized that every change is painful, and even then a layer on top can be a useful step, since it can keep working while the system underneath is swapped out.
