MES connector for test data

When it makes sense

Test data stays stuck on the station

A station that only writes local files falls behind the rest of the plant. A connector makes sense when:

Every result needs a link to a work order and a serial number in the MES.
Quality staff pull pass or fail data from a database instead of station log files.
A new product variant needs its recipe sent to the station automatically.

Data flow

How data moves between the station and the plant

Test stations push results into OpenEOL. The connector maps the schema once and carries results out, then work orders and recipes back, over OPC UA, MQTT or SQL.

Software

The open-source software behind it

Your plantReceives and sends data

MES, ERP and quality databaseTest results in, work orders and recipes out

OpenEOLRuns the connector

Task engine Open sourceRuns the sync and the mapping steps

GUI framework Open sourceScreens for the connection status and the message history

Reports and database Open sourceLocal record of every message sent and received

MappingMatches your schema

Schema mappingMatches each field between the station and your system

Config layer Open sourceReads the field mapping from TOML or XLSX

DriversCarry the traffic

OPC UA client and server Open sourceBuilt on asyncua

MQTT Open sourcePublish and subscribe over paho, or another OpenEOL protocol driver

SQL database Open sourceBuilt on SQLAlchemy

The parts marked open source are code your team can read and change. OPC UA, MQTT and SQL support ship in OpenEOL, and the schema mapping is written for each project inside the same program.

Related use cases

Other test data and functional testing pages

Functional test station for any product

Runs the test sequence and hands the pass or fail result to this connector.

Details

SPC software for test data

Turns the same test records into control charts and trend alerts.

Electric motor end-of-line test bench

A production line station that can push its results through this connector.

Details