Nine Plants, Nine Versions of the Truth

Every group MD has lived this Monday morning. The review call starts, and someone asks a simple question. What was our on time delivery across all plants last month? There is a pause. One plant head reads a number off his own MIS. Another says his figure looks different because he counts the dispatch date, not the invoice date. A third promises to send it by evening. The CFO quietly notes that the consolidated pack is still being built in Excel and will land on Thursday.

A simple question, and the honest answer is that nobody in the room can give it with confidence right now.

This is not a technology failure. It is what growth looks like from the inside.

How one company quietly becomes nine

When a company runs one plant, everyone shares the same reality. You walk the floor, you see the line, you know the number. Add a second plant in another state, then a third, then a unit that arrived through an acquisition, and something quiet happens. Each plant grows up with its own systems, its own registers, its own habits, and its own vocabulary.

The word rejection means scrap at one site and rework plus scrap at another. On time is measured against the customer date in Chennai and against the planned date in Pune. Nobody sat in a meeting and decided any of this. It accreted, one expansion at a time.

By the time the group has five or nine sites, consolidation has become a monthly act of translation. A capable person, usually someone far too senior for the job, spends the first week of every month stitching plant reports into one pack, resolving the mismatches by hand, and hoping the definitions line up. The pack is accurate enough to circulate. It is rarely fast enough to act on.

The bill arrives quietly

The cost of this shows up in three quiet ways.

First, decisions wait for the number. The group view arrives after the month has closed, so leadership is always steering by looking in the rear view mirror. By the time you learn that one plant slipped on delivery, the customer already knows too.

Second, plants cannot be compared, so good practice does not travel. If one plant improved its yield by changing a single setting, and another is still wrestling with the same process, nobody spots it, because the two report yield differently. The best idea in the group stays stuck in one building.

Third, when a board member, a lender, or a new investor asks for a straight operational number, the scramble begins. For a company that has just raised money or listed, that scramble is not a good look. The data exists. It just does not exist in one language.

Good tools, wrong question

It is tempting to blame the tools, but that misreads the problem. Each plant's ERP does its job. It records what happened inside that plant's transactions. A BI dashboard faithfully shows whatever it is fed, which is exactly the catch, because it cannot fix numbers that were never defined the same way at source. The month end Excel pack is a genuine feat of effort, but it is slow, fragile, and lives in one person's head and one person's formulas.

None of these tools is wrong. They were simply built to answer a different question. An ERP answers what happened here. A dashboard answers show me what I already collect. The review meeting answers who disagrees with whose figure. What no single one of them was built to do is take nine plants speaking nine dialects and turn them into one comparable, trustworthy view of the whole group. That is not a tooling failure. It is a translation problem that no plant level tool was ever asked to solve.

A smaller shift than it looks

The fix is quieter than buying another dashboard. It is about agreeing, once, that a number should mean the same thing everywhere, and then capturing and curating data so that it does.

Start at the source. Capture what happens on each floor in a consistent way, rather than re-keying it later. Then curate it into a shared language, so that a rejection, a delay, and a downtime hour mean the same thing in every plant. Only then does a group scorecard become worth trusting, because for the first time the plants are actually comparable. This is the heart of manufacturing intelligence. Not more reports, but one version of the truth that every site helped write.

Done well, this runs continuously, not once a month. Leaders can look at the group on any given morning, drill into the plant that looks off, and ask why before the month closes.

It is worth being clear about what this is and is not. It is decision support. It helps leaders see and question the operation. It does not run the plants for you, and it does not replace the systems each plant already trusts. It sits above them and makes them speak to each other.

Questions for your next leadership meeting

• If I asked every plant head for our group on time delivery right now, would I get one number or several?
• Does the word rejection mean the same thing in every one of our plants?
• How many senior hours go into building the monthly consolidated pack, and what else could those people be doing?
• When we last made a capacity or capex decision, did we compare plants on equal terms, or on gut and loyalty?
• If a new investor asked for a single operational metric across the group tomorrow, how long would it take us to answer, and how sure would we be of it?
• Which is our best performing plant on quality, and can we prove it in a way the other plant heads would accept?

The clock everyone reads differently

Growth does not create the data problem. It simply multiplies a small one you could afford to ignore when you had a single plant and a single reality. The company that scales cleanly is not the one with the most dashboards or the thickest MIS pack. It is the one where every plant, whatever its age or its address, tells time by the same clock.

Until then, you do not have nine plants. You have nine companies that happen to share a logo.

If this sounds familiar, it may be worth stepping back from the monthly scramble and looking at how growing manufacturers are building a single, shared view of their operations. Explore our executive guide on turning multi plant data into one manufacturing scorecard, and see what changes when every site finally speaks the same language.