Case study · Manufacturing

A manufacturer let agents write to ERP and MES without loosening a single permission

The integration fabric verified every proposed write against the plant's own state before it committed — and refused 4.9% of them.

Industrial manufacturer · 31 plants · published September 23, 2026

Download the PDF Apply for early access

4.9%

of proposed writes refused on contradiction with plant state

unscheduled downtime events attributed to agent writes

63%

reduction in planner re-entry time

plants live on the same enforced write path

Summary

An industrial manufacturer wanted maintenance and production-planning agents to write directly into ERP and MES. Orcher sat in the write path, checked each proposal against live plant state and standing work rules, and produced a record for each committed change.

Orcher components enforced

Logic Scrubber
Verifies the proposed action against systems of record before commit.
Role Identity Fabric
Binds the directive to a human and a role, cryptographically and revocably.
Observability
Real-time cross-provider trace: which model, which role, what cost, what outcome.

Solution: Identity & role-scoped authority

The situation

What was happening before Orcher.

Agents could read plant data but not write, so every recommendation still needed manual re-entry.
Manual re-entry introduced its own error rate and erased most of the time saved.
Plant IT would not grant write access to a system that could not explain a change after the fact.

What Orcher enforced

The control surface, component by component.

Every proposed write was verified against live MES state, standing work rules and maintenance windows before commit.
Role Identity Fabric derived agent write scope from the planner or maintenance lead who issued the directive.
Contradictions produced refusals with the specific conflicting state attached, routed back to the human.
Observability gave each plant a local view of what agents had changed in its own systems that shift.

The data

Measured over the engagement window.

Write type	Proposed	Committed	Refused	Top refusal cause
Work order creation	18,400	17,610	790	Outside maintenance window
Schedule adjustment	9,220	8,690	530	Conflicts with active run
Parts reservation	12,050	11,700	350	Stock already allocated
Downtime coding	6,310	6,240	70	Code not valid for asset class
Shift note	4,900	4,900	0	—

One quarter of agent write traffic across 31 plants.

Outcomes

What the organisation did next.

Plant IT extended write access to two further agent classes on the strength of the refusal record.
Planners spend their time on the refusals, which are the genuinely interesting cases.
Refusal causes fed back into work-rule cleanup, retiring 140 stale rules.
The manufacturer standardised the enforced write path for all future automation projects.

“Write access was never a technical question for us. It was a question of what happens the first time the system is confidently wrong.”

— VP of Manufacturing IT, industrial manufacturer (partner declined attribution by name)

Read further

The research behind this engagement.

Disclosure. Design-partner engagement, anonymised at the partner's request. Figures are measured by Orcher's own observability and ledger instrumentation over the stated period and have not been independently audited. Market figures carry their own source line.

More engagements

Other organisations that had to prove the same thing.

Healthcare

Run this pattern on your own workflow

Design partners deploy Orcher on one directive class, instrument it the way this study was instrumented, and keep the evidence whatever they decide afterwards.

Apply for early access All case studies