Architecture & tech
ERP, MES and AI: Who Owns Which Data?
Most integration pain comes from unclear ownership. A practical system-of-record map for manufacturers.
Trikaan Research & Engineering4 min read
KEY TAKEAWAYS
- Integration pain usually comes from unclear data ownership.
- Each data object should have exactly one master system.
- ERP typically owns finance and commercial masters; shop-floor systems own execution data.
- AI should read from masters, never create shadow copies.
Many manufacturers run an ERP for finance and purchasing, plus other systems for production, quality and maintenance. Trouble starts when two systems both think they own the same data.
Here is a practical map of who owns what.
A typical ownership map
| Data | Usual owner | Others |
|---|---|---|
| Chart of accounts, ledgers | ERP | Read only |
| Items and units | ERP or central master | Synced |
| Customers and vendors | ERP | Synced |
| Recipes and routings | Production system | Summary to ERP |
| Work orders execution | Production system | Results to ERP |
| Quality results | Quality / production system | Status to ERP |
| Machine signals | Edge / time-series store | Aggregates elsewhere |
Integration contracts
For each object, write down the owner, the direction of sync, the trigger (real-time or scheduled), the fields involved and what happens on failure. This one document prevents most integration disputes.
Avoid double entry
If production confirmations are typed into both the shop-floor system and the ERP, they will differ. Enter once, sync automatically, and reconcile exceptions daily.
Where AI fits
AI reads from the systems of record through permissioned access and writes back only through approved actions in the owning system. It should not maintain its own copy of masters.
When to replace vs integrate
- Replace when the ERP cannot support essential processes or is end-of-life.
- Integrate when the ERP handles finance well but lacks shop-floor depth.
- Phase replacements to avoid disrupting finance.
Frequently asked questions
What is the difference between ERP and MES?
ERP manages business transactions such as finance, purchasing and sales; MES manages execution on the shop floor.
Should items be mastered in the ERP?
Usually yes, or in a central master data system that feeds the ERP and other systems.
How often should systems sync?
Real-time for operational events where possible; scheduled for less time-sensitive data.
Do we need both ERP and MES?
Many mid-to-large manufacturers benefit from both, or from a platform that covers execution and integrates with the ERP.
- #ERP vs MES
- #system of record manufacturing
- #ERP integration
- #MES integration
- #manufacturing data ownership
Trikaan Research & Engineering
Trikaan
Written by the researchers and engineers who build Anvaya, ASTR and Seed Track, with input from Trikaan's delivery and engineering teams.
