How to Read Euromap Data into an ERP via OPC Archiving

How to Read Euromap Data into an ERP via OPC Archiving

Euromap interfaces on plastics processing machinery expose machine cycle data, production counters, and status information through OPC servers, typically OPC DA or OPC UA. Archiving that data to a SQL database creates a structured intermediary that an ERP system can read from, either on a scheduled query basis or through a live connection. OPC Expert handles the OPC subscription and SQL archiving side of this workflow without requiring a separate historian or custom integration code.

The Data Flow from Machine to ERP

The typical architecture for Euromap-to-ERP data flow has three layers. At the base, the Euromap-compatible machine exposes data through an OPC server, either on the machine controller itself or on a companion PC. OPC Expert runs on the same network, connects to that OPC server as a client, and subscribes to the items you want to capture: production counts, cycle times, temperatures, pressures, or any other available tags. OPC Expert archives those values to a SQL database, where the ERP system or an ERP integration layer can query them on demand. This separates the real-time OPC layer from the ERP layer, which is important because ERP systems are generally not designed to connect directly to OPC servers.

Setting Up the Archive for Euromap Data

In OPC Expert, setting up the archive for Euromap data follows the same process as any other OPC archive. You browse the OPC server, select the items you want to capture, right-click, and choose to create a new archive. You select SQL as the destination, provide the connection details for your SQL server, and choose between event-based capture (writing only when values change) or time-based capture (writing at a fixed interval). For production count and status data, event-based capture is typically the appropriate choice because it records the moment each cycle completes or each status changes rather than polling at an arbitrary interval that may not align with machine cycle timing.

Structuring the SQL Data for ERP Consumption

OPC Expert automatically creates a history table in the SQL database with columns for timestamp, item ID, value, and quality. For ERP integration, the ERP team typically needs to know the item ID naming convention used by the OPC server so that SQL queries can filter correctly for the specific machine and data type. Using a consistent OPC server naming convention that includes the machine identifier in the item path makes the resulting SQL records straightforward to query by machine, shift, or date range. If the ERP system is capable of executing SQL queries or calling a stored procedure, it can pull production data directly from the OPC Expert archive without an additional middleware layer.

Handling Network Gaps Between Machine and SQL

In plant environments, the network connection between a machine controller and a plant-level SQL server may be intermittent, particularly during planned maintenance or shift changeovers. OPC Expert’s store-and-forward capability ensures that Euromap data captured during a connectivity interruption is not lost. Values accumulate in a local buffer and are forwarded to the SQL database when the connection recovers. For production reporting in an ERP context, this data continuity is important because gaps in the record can cause discrepancies between machine-reported production counts and what the ERP system shows.

Relevant Tools

Archive OPC Data from OPC Expert connects to OPC DA and OPC UA servers on Euromap-compatible machines and archives the captured data to SQL databases including Microsoft SQL, MySQL, and SQLite. Its store-and-forward capability protects against data loss during network interruptions. OPC Bridge from OPC Expert can be used upstream of the archive if the machine’s OPC server needs to be accessed remotely or if data from multiple machines needs to be consolidated before archiving.

Conclusion

Archiving Euromap data through OPC Expert and into a SQL database gives your ERP system a reliable, queryable source of machine production data without requiring a direct OPC connection from the ERP layer. The OPC Expert archive handles the protocol complexity and data continuity, while the SQL destination gives the ERP integration team a standard interface they can work with using familiar tools.