Knowledge Base

How to Unify MES, WMS, QMS and CMMS Without Replacing Everything

DBR77 Team7 min read

On this page

You unify MES, WMS, QMS and CMMS by agreeing on shared master data first, then connecting the few events that cross departments, and replacing a system only when it blocks that flow. ERP usually stays, and a tool that works can stay too. The goal is one record of machines, orders, material lots and people, even if it spans several vendors.

Integration usually fails when plants change everything at once, or connect systems that still disagree on what a machine or a lot is called.

Why replacing everything at once usually fails

A full replacement sounds clean: one project, one go-live, one new system. In practice it means months of parallel work while the plant keeps running on the old tools. Software author Martin Fowler says of the full-rewrite plan that he has seen it go down in flames most of the time. His alternative is to build new parts next to the old system and move behavior over piece by piece. Small pieces carry less risk, and each one starts paying back as soon as it works.

The same logic fits a plant. Each line has to keep shipping, and operators, setters and technicians know the current screens. A replacement that touches four departments on one weekend puts every shift at risk at once.

The ISA-95 standard defines the exchange between plant and business systems, and its stated goal is to reduce the risk, cost and errors of implementing those interfaces. Unifying starts with agreeing what is exchanged, before any new software is bought.

Clean the master data: one ID for each machine, material, lot, work order and person.

Six steps to unify MES, WMS, QMS and CMMS: master data, machine data, one event, quality, material, then retire duplicates

What "unified" means on the shop floor

The OPC Foundation's summary of ISA-95 says coordination and control must happen in at least four parts of an organization: production, quality tests and labs, warehousing and inventory, and maintenance. That matches the MES, QMS, WMS and CMMS split most plants have.

Unified means three things:

  1. Every system uses the same master data, with one ID for each machine, material, lot, work order and person. If the filler is "F-02" in the CMMS and "Line 2 Filler" in the MES, no interface will fix the reports.
  2. A short list of cross-department events moves between systems without retyping: a machine stop opens a work order, a failed inspection puts a lot on hold, a material shortage warns the line, a finished order updates stock.
  3. When the work is done, one closed record shows what happened in all four areas: the stop, the repair, the check and the stock change.

With those three, you have most of the value, even with several vendors.

Keep, connect or replace: a test for each system

Ask what each system does to the cross-department flow. One that does its job well and can exchange data should stay for now.

SystemKeep it whenConnect it byReplace it when
MESOrder tracking and counts are trusted on the floorSharing order, line and machine IDs; sending stops and counts outCounts are typed by hand, or it has no way to send events
WMSStock and locations are accurate and scannedSending stock moves and receipts; receiving material calls from the lineStock lives in a spreadsheet or the ERP is updated once a day
QMSInspections and non-conformances are recorded digitallyLinking each result to an order, machine and lot; sending holds and releasesQuality runs on paper forms or email, so nothing can be linked
CMMSTechnicians use it and asset history is completeReceiving faults as work orders; sending closures back with the asset IDWork orders are opened after the repair, or the asset list is outdated

Most plants find one or two systems to replace and the rest to keep or connect, which keeps the project small. The roles of MES and ERP in this picture are explained in Plant Operating System vs MES vs ERP.

A step-by-step order that keeps the plant running

  1. Clean the master data. Agree on one asset list, one material and lot format, and one list of roles. Assign an owner for each list. This step costs little and removes most later errors.
  2. Connect machine data. Trusted states, counts and stop reasons are the raw material for every other connection. When to Integrate IoT with MES, ERP and CMMS explains when to connect machine data to each system.
  3. Connect one cross-department event. Pick the handoff that is retyped most often. For many plants it is stop to work order.
  4. Add the quality link. Tie inspections and holds to orders and lots, so a defect points to a machine and a time window.
  5. Add the material link. Let the line call material and let finished orders update stock.
  6. Retire what is duplicated. Only now replace the systems that failed the test above.

Use open interfaces. OPC UA, a platform-independent architecture released in 2008, suits the machine side; REST APIs usually cover the business side.

Illustrative example: a plant with three lines keeps its ERP and a CMMS that technicians like. Production runs on spreadsheets, quality on paper, and the warehouse in an ERP add-on. The team spends two weeks agreeing on asset and lot IDs, connects machine stops to the existing CMMS, replaces the spreadsheets and paper with production and quality modules, and leaves the warehouse for later. The CMMS stays because it passed the test.

How this works in DBR77 IRIS

DBR77 IRIS is built for this kind of step-by-step path. IRIS MES, IRIS WMS, IRIS QMS and IRIS CMMS share one data model, so the links between them already exist: starting an order in IRIS MES reserves its material in IRIS WMS, finished output is booked into stock, SPC alarms and defect reports open non-conformances in IRIS QMS, and equipment failure events open corrective work orders in IRIS CMMS.

Pricing is per module, so a plant can start with one module and add others later; data and configurations carry over. Where an existing system stays, IRIS exchanges data with it through its API and webhooks, and the ERP connection is set up for each project. Machine data comes from DBR77 IIoT: devices are attached to stations, and IRIS CMMS maps each station to its asset. More on connections is on the integrations page. When a module is ready to compare against the tool it may replace, use the criteria in How to Evaluate a Plant Operating System.

FAQ

Do we have to replace our ERP?

No. ERP keeps finance, purchasing and the master plan. The shop-floor systems send it closed records, such as finished orders and stock changes.

Can we keep a CMMS from another vendor?

Yes, if technicians use it and it can exchange work orders and asset IDs. Connect it first and decide later whether it still earns its place.

Who should own master data?

One owner per list: usually maintenance for assets, the warehouse or planning for materials and lots, and HR or the plant manager for roles. IT keeps the rules, not the content.

What is the first sign it is working?

The same event is no longer typed twice. Count how often a stop, defect or stock move is retyped each week, and watch that number fall.

Conclusion

Start with the asset list: one ID per machine, owned by maintenance. Then count how often a stop, defect or stock move is retyped each week, connect the handoff that is retyped most, and replace a system only when it fails the keep, connect or replace test. Following that order lets the plant keep shipping during the change and see value after each step.

Sources