Best Practices for Integrating Weighing & Dosing with Your Existing Mixer and ERP
A batch weighing system in isolation captures data. A batch weighing system integrated with your ERP, MES, and quality systems transforms that data into real-time inventory accuracy, automatic batch records, and recipe management that's owned by a single source of truth. Here's how to do the integration right.
Why Integration Is the Highest-Value Feature of Modern Dosing Systems
A batch weighing system that operates in isolation — capturing accurate weights but storing them locally, disconnected from your ERP and quality systems — delivers only a fraction of its potential value. The data it generates (actual ingredient weights, batch completion timestamps, operator IDs, tolerance exceptions) is exactly what ERP, MES, and quality management systems need to function accurately.
Without integration, that data gets manually re-entered — creating a transcription error risk that undermines the accuracy the dosing system was installed to provide. Or it doesn't get entered at all, leaving ERP inventory records stale and quality records incomplete.
With integration, the dosing system becomes the production floor's data source of record: pulling recipes from the ERP, confirming batch completions back, updating inventory in real time, and generating quality records without any manual intervention. This is where the full ROI of automated dosing is realized.
Step 1: Map Your Data Flows Before Any Technical Work
Before configuring any integration, document the data flows you need:
Inbound (ERP → Dosing System):
- Production orders (batch number, recipe ID, quantity, scheduled date)
- Recipe updates (when formulation changes are approved, they should flow automatically, not by manual PLC update)
- Material lot numbers (for traceability linking)
Outbound (Dosing System → ERP):
- Batch completion confirmations with actual weights
- Inventory consumption (actual material used per ingredient per batch)
- Operator data and batch record exports
- Exception and deviation records (tolerance overrides, substitutions)
Documenting these flows in advance prevents scope creep during integration — and identifies whether you need a simple one-way data push, a bi-directional real-time feed, or something in between.
Step 2: Involve Your IT Team (and ERP Vendor) Early
The most common integration delays come from IT and ERP vendor involvement arriving too late — after the dosing system is installed and someone asks "so how does it talk to SAP?"
Involve your IT team at the specification stage, not the installation stage. Key questions to answer early:
- What integration method does your ERP support? (REST API, OPC-UA, flat file import, direct database, proprietary connector)
- What authentication and network security requirements apply to production floor devices?
- Does your ERP vendor have a certified integration partner or documented interface specification for the Gomaplast system?
- What is the IT team's change control process for production system integrations?
Gomaplast has worked with SAP, Oracle, Microsoft Dynamics, and custom MES environments. Your Gomaplast project team can work directly with your IT team and ERP vendor during the integration specification phase — but this conversation needs to happen before equipment order, not after delivery.
Step 3: Standardize Your Recipe Master Data
ERP-to-dosing integration breaks down when recipe master data is inconsistent between systems. Common problems:
Ingredient naming mismatches: The ERP lists "Sulfur 80% MC" while the PLC recipe library references "S-80." If the integration maps by ingredient name rather than material number, mismatches produce incorrect recipe downloads.
Unit of measure inconsistencies: ERP recipes stored in kg while PLC works in grams — a conversion error produces 1000x dosing error.
Multiple recipe versions: ERP has the approved revision while the PLC still has an older version. Without a defined data authority (ERP owns the master, PLC receives), versions diverge.
Before integration go-live, audit your recipe master data in both systems and establish a single source of truth — typically the ERP, with changes flowing downstream to the PLC automatically upon approval.
Step 4: Define the Batch Record Schema
The batch record generated by the dosing system needs to map to fields in your quality management system. Define the schema before integration — not after.
A complete Gomaplast batch record includes: batch number, recipe ID, recipe version, production date/time, operator RFID ID, each ingredient with planned vs. actual weight, tolerance status for each step, any exceptions or overrides with operator notes, and batch completion timestamp.
Your QMS may need a subset of these fields, or may need them mapped to specific field names. Document this mapping before integration configuration begins. Post-installation changes to the schema are possible but require retesting and revalidation — front-loading this work saves time.
Step 5: Run Parallel Operation Before Cutting Over
When you go live with ERP integration, don't eliminate your backup process immediately. Run parallel operation — integrated system plus manual backup — for at least two to four weeks.
During parallel operation, verify:
- Production orders from the ERP are arriving at the dosing station correctly and on schedule
- Batch completions are confirming in the ERP within the expected timeframe
- Inventory consumption records match the actual weights from batch records (within normal rounding)
- Exception handling works as designed (tolerance overrides are flagged in the ERP, not silently accepted)
Only after parallel operation confirms consistent, accurate data flow should manual backup processes be retired. This step protects against integration configuration errors that aren't visible during bench testing.