Enterprise Resource Planning (ERP) systems are built for financials, inventory, and procurement. But when glass manufacturers try to extend ERP to the shop floor, things often break down. The truth? Most ERPs weren’t designed for real-time production complexity.
A classic issue is lack of granularity. ERPs typically track jobs at the order level—not the operational level. But glass production involves dozens of micro-events: furnace delays, part defects, batch pauses. If the ERP only sees “Job 12345 – Complete,” you’re flying blind on efficiency, quality, and downtime.
ERP systems also struggle with machine-to-system integration. A tempering line may log data every second—furnace temp, quench pressure, cycle time. But without a Manufacturing Execution System (MES) layer, the ERP can’t parse or store this data in a meaningful way. The result: massive gaps in traceability and decision support.
Another friction point is dynamic scheduling. In high-mix glass plants, job sequencing changes daily based on load types, thickness, and priority. Most ERP scheduling modules are static—they can’t adjust based on furnace availability or IGU assembly constraints. The result is rework, idle time, and missed delivery windows.
Inventory accuracy is another trap. ERPs assume WIP updates in real time—but without barcode scanning or RFID on the floor, that WIP might be four hours (or four days) behind reality. That leads to false inventory counts and purchasing headaches.
So what’s the fix?
Decouple production control from ERP: Use MES, SCADA, or IoT platforms to handle the plant floor in detail.
Integrate at the interface: Push clean, aggregated production data up to ERP—not raw PLC chatter.
Map the right KPIs: Use MES for takt time, scrap, and OEE. Use ERP for cost rollups and customer commitments.
Bridge gaps with middleware: Tools like OPC UA servers, message brokers, or cloud platforms can sync ERP and plant-floor data.
The takeaway? ERP is essential—but it’s not sufficient. If your plant floor feels like a square peg in your ERP’s round hole, it’s time to rethink the tech stack—not your process.
