The Plant Says One Number and the ERP Says Another. The Public Record Says That Is Where AI Pilots Stop.

It is the Monday review. The first slide shows Friday’s second shift.

The production head says the shift made 4,200 pieces. The ERP report on the screen says 3,950. The dispatch supervisor, reading from a spreadsheet, has 4,100 ready to go.

Each of the three figures was recorded by someone careful. For twenty minutes the meeting works out which is right. All three turn out to be right, for different moments of the same evening. Nobody writes that down. Next Monday it will be a different figure.

What We Found

For this article we went through the public record on manufacturers whose figures do not travel between their systems: a report of an industry summit in India in 2026, an industry body’s survey of manufacturers on what holds back their use of AI, and a news report of a survey of small and mid-size Indian firms.

Four findings stand out.

In India, the barrier named first is the state of the records, not the age of the plant. A report of an industry summit held in 2026 says that “smaller and mid-sized Indian producers encounter a deeper barrier: fragmented data, aging machinery, and a lack of standardized operating frameworks”. Fragmented data comes first in that list. The report comes from a market-data firm that rewrites news, and names no firm of that size.

Without that groundwork, the same report says, a good result does not travel. Its words are that “a successful pilot might remain merely a pilot”.

Data comes ahead of machines in what manufacturers say holds them back. In an industry body’s survey of manufacturers, published in April 2026, respondents picked their top three barriers to AI. About six in ten named “Data issues”. By comparison, 25.9% named the “Need to upgrade legacy equipment”. The page does not give the size of the sample or where the respondents are, and the survey is about AI, not about connecting systems.

Many firms are still at the start. In a survey of more than 400 small and mid-size Indian firms across IT, manufacturing, education and retail, reported in June 2025, 43% had reached basic digital maturity, meaning an ERP and the cloud, and 56% cite a lack of technical skills. That survey covers four sectors, not manufacturing alone.

Our reading is that in most mid-size plants the figures do cross between systems. They cross between the firm’s own applications, its ERP and its plant records, and much of the time they cross by hand: a clerk who types the shift sheets into the ERP each morning, a planner who copies the same output into a planning sheet, a file that a script moves at night. Each is a place where a figure can change, and none is on any plan of the firm’s systems.

What Waits While the Figures Cross by Hand

Figures that disagree are usually treated as a nuisance in meetings. Our reading is that they hold back more than that.

The first cost is senior time. The people in the Monday review are among the most experienced in the building, and they begin the week on arithmetic.

The second is that each difference is treated as a one-off. It is explained, adjusted and forgotten, and the crossing that made it is never named, so it makes the next one.

The third is the one the public record points to. Every plan to see the plant’s figures in one place, or to try AI on them, needs figures that arrive by themselves. While they are carried by hand, such a project runs once, on figures gathered for it, and stops. In the report’s words, the pilot remains a pilot.

This is our reading of the evidence. It is not a measured market figure.

Four Ways Forward, Weighed

There are four real options. Each one is right for somebody.

Option	When it fits	What it risks
Put one dashboard over the figures as they are	The figures already agree and only need to be seen together	It shows the same disagreeing figures more clearly, and the crossings that make them stay where they are
Buy a connection product from a specialist	The firm runs several packaged systems that the product already knows how to join, and has people to run it	The firm’s own older applications may have no way in or out, and crossings made by hand are not on any product’s list
Build one connection between two of the firm’s own applications	One crossing is plainly the costliest, and both ends of it are understood	It is one more thing to own and keep up, and it leaves every other crossing as it was
Map every crossing first, then rebuild the firm’s own application one module at a time	Nobody can list how figures travel today, and the firm’s own application is where a figure is typed again	It costs money before anything changes, and the map itself connects nothing

Where You Are Now, and Where You Should Be

Before any work begins we set a benchmark: a few measures taken from your own applications, each with a target.

Measure	Typical starting point	Where it should be	How it is checked
Crossings between your applications, your ERP and your plant records	Listed nowhere	Every crossing listed, including by hand, timed files and spreadsheets	The map of the system
Figures re-typed from one place to another	Not counted	Counted, and falling as each module is accepted	Reported at every review
The source of each figure	Several copies, none named as the source	One named source for each figure	The specification
Disagreements between systems	Argued in meetings and adjusted	Each traced to the crossing that makes it	The risk register

The starting points above are what the public record suggests and what we expect to find. In an engagement they are replaced by your own figures, taken in the first review. The targets are what we would work towards with you. They are not results we have already achieved for a manufacturer.

How We Work With You

1. We listen: a free Reliability Review. A first conversation about your applications, the figures that disagree, and the places nobody is sure how a figure travels. You leave with a short written note of what we found. You can start with a conversation about the system; we ask for read-only code access only when the assessment begins.
2. We research. We research your sector, the regulator’s position and what the public record says about firms in your situation. This article is an example of that work.
3. We read the system and propose: the Legacy System Specification Assessment. Here the system is the applications you built or had built beside your ERP, and the files, scripts and hand-offs that carry figures in and out of them. It produces a map of the system as it stands, a written specification of what it does, a risk register, a cost comparison between keeping and replacing the system, and a staged plan with a fixed quote. AI does a first pass, our senior engineers review it and trace it to the code, and your own experts confirm it. Code access is read-only and logged, never used for training, and deleted within 30 days of the evaluation ending unless we engage. You get the options and our recommendation.
4. If you approve, we build. We replace a system one module at a time while the old one keeps running. Here that means your own application that receives a figure, rebuilt one module at a time so the figure is entered once. We never do a single cutover. Each module has a traceability matrix. The work is billed by milestone, each milestone tied to a module you accept, and you can pause after any accepted module.
5. We review against the benchmark. Before work starts we set the benchmark. After each module we show you where each measure stands, and the filled-in benchmark is yours at the end.

The Review is free. Every paid step is fixed price, agreed at scoping. Stop after any step. The findings are yours. The assessment fee is credited in full against the first build stage if it starts within 90 days of the report.

This approach has limits. A map connects nothing: the day after it is finished, the clerk still types the shift sheets into the ERP. Where a crossing ends inside a packaged ERP product, we record it from the outside and say so; we cannot see inside the product or change it, and anything on its side is your ERP specialist’s work. Some differences begin on the plant floor, with a late sheet or a count taken at another moment, and no map of software removes them. We have no connection or integration product, we do not connect to machines, read machine signals or work on plant control systems, and we do not run or monitor a connection after hand-over. We do not clean or reconcile your records, and we do not keep the old applications running in the meantime; your own team or supplier does. We have no published case of this work for a manufacturer.

What changes for the business:

Role	What they gain
CEO	When two reports disagree, the firm knows which crossing to look at, and reviews stop opening with an argument about figures.
CTO or CIO	A map of every crossing between the firm’s applications, its ERP and its plant records: files, scripts, exports and people.
CFO	A difference between production and the books can be traced to a named crossing, and not only adjusted at month end.
COO	Operations sees which figures are re-typed, where and how late, and can choose which to deal with first.
Head of digital	Every digital project starts from a known picture of where each figure lives and how it travels.

The cases in this article, and what IOanyT does about that kind of problem:

The case	What IOanyT does
A report of an Indian industry summit says smaller and mid-sized producers face “fragmented data, aging machinery, and a lack of standardized operating frameworks”, and that “a successful pilot might remain merely a pilot”. No firm of that size is named.	Our part is narrower. We do not work on machines or plant control systems. For a manufacturer’s own applications, we map every crossing of a figure, including by hand, and rebuild the application that receives it, module by module.
In an industry body’s survey, about six in ten manufacturers named “Data issues” among their top three barriers to AI, and 25.9% the need to upgrade legacy equipment.	We have no connection product and promise no result from AI. We show where each figure comes from, so the firm can decide which crossing to deal with first.

IOanyT is a consultancy with its own engineering team: we study the problem, recommend, and prove it by building only what you approve. We start with the crossings, because that is where the figures part company.

Book a free Reliability Review →

Get a fixed quote →

See the Legacy System Specification Assessment →