Running Five Plants on Five Versions of the Truth

A manufacturer that grows from one plant to five rarely plans its systems for five. Each new plant brings its own codes, spreadsheets and habits, and group reporting becomes a monthly exercise in translation.

This article sets out how to build one view across plants without forcing every plant into an identical process.

The symptoms

• The same material has different codes in different plants.
• Units differ: one plant reports in tonnes, another in quintals.
• Plants calculate yield or OEE differently.
• Leadership gets numbers by calling plant heads.

Common masters first

Items, customers, vendors, units of measure and charts of accounts should be governed at group level. Plants can request new entries through a simple approval process, but they should not create their own versions. This one decision removes most of the translation work.

Local workflows, shared data

Plants differ for good reasons: equipment, product mix, local regulations, workforce. Approval chains, checklists and screens can be configured per plant. What must stay common is the meaning of the data they produce.

Comparing plants fairly

Ranking plants on a single number causes resentment and gaming. Compare on like-for-like products, adjust for raw-material grade or batch size where it matters, and look at trends as well as levels. The goal is to spread good practice, not to embarrass a plant head.

A group dashboard that works

• Plan vs actual output by plant and product family.
• Yield, downtime and quality, with the same definitions everywhere.
• Stock cover and shortages by plant.
• Exceptions only, with drill-down to the plant and the record.

Master data governance in practice

Governance sounds heavy, but it can be a simple routine: a request form for new items or customers, a central reviewer who checks for duplicates and correct units, and a target turnaround of a day or two. Plants accept central control when it is fast. They work around it when it takes a week.

Periodic clean-ups still matter. Every quarter, look for duplicates, unused codes and inconsistent units, and merge or retire them with a clear audit trail.

Group dashboards for leadership

A CXO view should answer three questions in under a minute: are we on plan, where are we not, and why? That means plan versus actual by plant, exceptions highlighted, and the ability to click through to the plant, product and record that explains the gap.

Adding the next plant

With common masters and configurable workflows, a new plant becomes a configuration project: set up the plant, map local codes once, configure approvals, connect machines and train people. That is the difference between a group that scales and one that re-implements with every acquisition.