Intsoft Intsoft Visual AI SOP System

Connecting Visual SOP to MES: Choosing a Method and Designing the Fields

Published: Updated: 15 min read

The hard part of integration is not the technology choice — it is defining what you actually need to trace. Once the fields are settled, choosing between a direct database write, an HTTP API and a message queue becomes straightforward.

Integration diagram from vision inspection through a gateway into enterprise systems

Key takeaways

  • Define the fields first, choose the channel second. Without agreed fields, every integration method gets reworked.
  • None of the three methods is inherently better; it comes down to how open the existing system is and how much IT resource will be committed.
  • The minimum usable field set is: station, operation, timestamp, result, product serial number.
  • Do not change the schema of the existing system. That single rule is usually what keeps the project moving.
Isometric diagram of an industrial camera and an edge computing box connected by a single cable
The station-level hardware: one industrial camera plus one edge computing box

A visual SOP system delivers value on its own — the station alarms and the problem is corrected on the spot. But the process history is only complete once the data is written into MES, where a defect can be traced back to the specific step that caused it. The capability and implementation detail sits on the visual SOP to MES traceability page. And the projects that fail at integration are almost never blocked by the channel technology. They are blocked by fields that were never defined.

Define the fields first: the minimum set

The minimum field set for a process execution record
FieldWhat it holdsWhy it is required
Product serial numberTies the record to one unitWithout it, a record cannot be traced to an individual product
Station IDThe physical location where the work happenedPins down where the problem occurred
Operation IDMaps to an entry in the SOPDistinguishes which step was missed or done wrong
TimestampWhen the action happened, to the secondEstablishing sequence, analysing cycle time, checking changeovers
ResultPass / fail / skippedThe base data for quality analysis
ConfidenceThe score the model producedSupports later threshold tuning and review

Three ways to connect

Integration methods compared
MethodWhen it fitsAdvantageWatch out for
Direct database writeMES database is reachable and IT has DBA supportLow latency, simple to buildAgree the target table and permissions up front; avoid impacting main table performance
HTTP APIMES already exposes an interfaceClean separation, easy to auditPlan for local buffering and retry when the API is unavailable
Message queueMQ infrastructure already existsAbsorbs peaks, reliable, supports multiple consumersRequires MES-side consumption; longer to implement

What to do with exception records

Normal records are for traceability, exception records are for improvement. Flag exception data separately and keep the action sequence for a window either side of the event, so the quality team can reconstruct what was happening. Where an incident could reflect on an individual’s work, agree the retention scope and access rights with HR during the design phase. The wider picture is in turning visual SOP data into quality records.

What to agree before the first record is written

  • Who owns the interface. One named person on the MES side and one on the vision side. Integration projects stall at the handover, not at the protocol.
  • The target location. A dedicated table or an existing open interface, agreed in writing, with the account and permissions settled before development starts.
  • The failure behaviour. What the system does when MES is unreachable — buffer locally, retry, and log the gap — has to be decided up front rather than discovered during a network outage.
  • The back-fill window. How long a station may hold data offline, and how late arrivals are reconciled against the work order.

Most of the friction in these projects comes from the vendor boundary rather than the technology, which is why it is worth reading working with an MES vendor before the kick-off meeting. On the vision side, the question of what the station itself records is answered under workstation SOP monitoring.

Common questions about MES integration

How much IT effort is involved?

With a direct database write it is usually a case of creating an account and agreeing a target table; with an API it needs interface documentation and joint debugging support from the MES side. The actual effort depends on how open the existing system is.

Will data be lost if MES goes down?

No. Results are stored locally first and uploaded automatically once the network or MES recovers, with the back-fill status logged for checking.

Can it pull work order information back from MES?

Yes. Reading the current work order and product model lets the system switch to the matching SOP operation set automatically, which is common practice on lines with frequent changeovers.

Related reading

Pushing an MES integration project?

Tell us how open your existing system is and what you need to trace, and we can advise on the approach.

Contact us

Related articles

View all

Need specific advice for your production line?

Our engineers can share practical approaches to process error prevention and SOP compliance inspection for your scenario.

Request a free trial plan