Everyone Was Working. But Everyone Wasn’t Seeing the Same Plan.

A team can be busy and still lack a shared operational picture. People may each have useful information, but if that information lives in different spreadsheets, meeting notes and personal records, the organisation can end up making connected decisions from different versions of reality.

That was the practical problem described in Siemens’ case study of SUMIDA Lehesten in Germany.

The information existed. It did not exist in one shared view.

Before the intervention, production planning was spread across Excel lists, meeting minutes and personal employee notes. The problem was not a complete absence of information. It was fragmentation.

When planning information is fragmented, a change in one place may not become visible everywhere it matters. Capacity, lot size, employee availability and system constraints can interact, while different people continue working from different assumptions.

A common planning database changed visibility

SUMIDA implemented a common production-planning database through Siemens’ Opcenter APS. The stated aim was to make the manufacturing process more transparent and to optimise capacity, lot sizes, employee availability and production constraints from a shared source.

The important word is shared. Operational clarity does not require every employee to see every detail. It requires the people making connected decisions to work from enough common information that their decisions remain compatible.

Delivery reliability and lead time changed

Siemens reports that delivery reliability increased from 60 percent to 95 percent. Lead time reportedly fell from 20 days to five days — a 75 percent reduction.

The company also described being able to identify problems earlier and more precisely because planning information was available in a common system. That connects the intervention to a practical behaviour: seeing the problem soon enough to act.

A strong outcome, but still provider-reported evidence

The performance numbers are meaningful, but they come from a Siemens customer case study. That means they should be presented as attributed programme outcomes, not as independently verified causal estimates.

The case is still useful because the before-condition and the operational change are concrete: fragmented planning information became shared planning visibility, and the company reported measurable improvements afterward.

Shared visibility changes the quality of escalation

When information is fragmented, escalation often begins with reconstruction: Which spreadsheet is current? What did the meeting decide? Who changed the schedule? By the time the team agrees on the facts, the operational window may already have narrowed.

A shared view does not eliminate problems. It changes how early they can be seen and how precisely they can be discussed. That is a different capability from simply having more data.

Clarity is visible in coordination

Operational clarity can be tested by watching handoffs. Does production know what sales promised? Does planning see the same capacity constraints as the team executing the work? Can a manager identify what changed without asking several people to reconstruct the story?

If connected decisions repeatedly require reconciliation, the business may have an information-clarity problem even when every individual is competent. The system is asking good people to coordinate through fragmented context.

The value of a shared plan appears when conditions change

When everything runs exactly as expected, fragmented systems can look good enough. The weakness appears when a machine goes down, an order changes, a worker is unavailable or capacity becomes tight. Then each local plan must be reconciled with the others under time pressure.

A shared planning view becomes valuable because the organisation can see the interaction earlier. It does not make uncertainty disappear. It reduces the amount of uncertainty created by the organisation’s own information structure.

A shared source is useful only if people trust it

Centralising information does not automatically create clarity. If employees continue keeping parallel spreadsheets because the central plan is late or incomplete, fragmentation simply moves underground. The practical test is whether people actually use the shared source when they make decisions.

That is why adoption belongs inside the observation. A technically perfect system with low trust can leave the same coordination problem intact.