An ISO automation system doesn't need to absorb your ERP or MES to be useful — it needs a small number of clean, well-defined integration points where document-control state and production state touch. Get those points right and the two systems stay decoupled; get them wrong and you've built a second source of truth that fights the first one.
Most Thai manufacturers run document control, ERP, and MES as three systems that don't talk to each other at all — a factory owner or QMR usually knows this instinctively, because it's why a work instruction can go stale on the floor weeks after it was revised in the register. The question worth asking isn't "should these systems connect," it's "where, specifically, should they."
Why document control and production systems rarely talk today
Document control, ERP, and MES were built to solve different problems, for different audiences, usually at different times. Document control exists to prove what was approved and when. ERP exists to plan and track what's being made and consumed. MES exists to execute and record what's happening on the line right now. None of the three was designed with the others' data model in mind, which is exactly why manufacturers end up maintaining the same fact — "which revision of this work instruction is current" — in two or three places by hand.
That gap is invisible until it isn't. A revision gets approved in the document register on Tuesday. The laminated copy on the line doesn't get swapped until someone notices on Friday. In between, production is running against a superseded document, and nothing in ERP or MES flags it, because neither system was told the revision changed.
Where an ISO automation system should connect
Not every field in your ERP or MES needs to know about document control, and not every document needs to reach the shop floor system. The useful integration points are narrower than that:
| Integration point | What flows | Direction |
|---|---|---|
| Current revision status → MES | The approved, current revision number and effective date for a controlled work instruction or quality record | Document control → MES |
| Document effective date → production scheduling | Whether a work order references a document that is currently valid, or has been superseded | Document control → ERP |
| Distribution matrix → access control | Which departments or roles should have visibility into a controlled document once it's released | Document control → ERP/MES user groups |
| Change event → notification | An alert that a controlled document affecting a specific line, product, or process just changed | Document control → ERP/MES or messaging layer |
Notice the direction in every row: it runs from document control outward. That's deliberate. The document register is the source of truth for revision status; ERP and MES are consumers of that fact, not co-owners of it. Trying to make revision status editable from two systems is how you end up with a register and a shop-floor system that disagree about which document is current.
What stays separate
Integration points are not an invitation to merge the systems, and they're not a shortcut around the human decision gates that ISO 9001 actually requires. A production order in ERP can reference a document's current revision. It should never be able to trigger, approve, or bypass a document revision on its own. The judgment about whether a document is technically adequate and ready for release stays exactly where it already is — with the reviewer and the approver named in your SOP — regardless of how many other systems eventually read the result of that decision.
This matters practically, not just philosophically. An ERP or MES integration that lets a production planner "approve" a document change because a work order is blocked on it has quietly moved a compliance decision into a system that was never designed to make one, and that has no audit trail built for the purpose. The integration should carry information outward from a completed decision. It should never carry a decision inward.
A practical way to think about scope
The mistake we see most often is manufacturers trying to design the ERP/MES integration before the document-control automation underneath it is solid. That's backwards. The eight fields a document controller currently retypes by hand — revision number, effective date, register entries, distribution matrix, retention date, and the rest — are the actual source data any downstream integration would consume. If those fields aren't being written accurately and traceably in the first place, connecting ERP or MES to them just automates the propagation of bad data faster.
A workable rollout order looks like this:
- Automate the clerical writes into the document-control register itself, so revision status, effective dates, and distribution are accurate and logged the moment a human approves them.
- Confirm that register is reliable enough to be treated as a single source of truth — verified against acceptance criteria, not assumed.
- Only then expose the specific fields (current revision, effective date, distribution) that ERP or MES actually need to consume, through a narrow, one-directional integration point.
Skipping straight to step three, before step one is solid, is how manufacturers end up with an ERP dashboard that confidently displays the wrong revision number.
This ordering also keeps the integration cheap to build and cheap to change. A single field — current revision, effective date — exposed through a narrow, well-tested integration point is easy to extend later if a second downstream system needs the same fact. A wide, ad hoc integration built before the underlying register is trustworthy has to be rebuilt every time the document-control side changes, which is the more expensive failure mode in practice.
FAQ
Does ISO automation require integrating with our ERP or MES?
No. Document-control automation is useful on its own — the register, the decision gates, and the audit trail don't depend on ERP or MES knowing anything about them. Integration is an optional extension once the core is solid, not a prerequisite.
Can production be blocked automatically if a document is out of date?
That's a decision your organization can choose to build into an ERP or MES integration, but it's a business-logic decision layered on top of document control, not something ISO 9001 itself requires. It should read the document register's status, not decide it.
Which system should own the "current revision" field?
Document control should. ERP and MES should read that value, not maintain their own copy of it, to avoid the two systems disagreeing about what's current.
What platform is used to build these integration points?
Our reference build runs on n8n, which is well suited to this kind of narrow, event-driven integration between document control and other business systems, though the right platform depends on what you already run.
Should we integrate everything at once?
No. Start with the document-control automation itself, confirm it's accurate and auditable, and add ERP or MES integration points one at a time, scoped to what actually needs to flow.
If you want to map out where your document control should — and shouldn't — connect to your ERP or MES, book a free consultation with 1% EVO. Bring a description of your current systems; we open a running system and walk it through, live.