Integrating with Different MES Vendors: What to Watch For

The data a visual SOP system needs to write is simple: which station, which operation, what time, what result, and which product. But the same set of data meets very different friction when it is written into SAP, Siemens, UFIDA or Kingdee. The difficulty rarely sits at the "can the link be made to work" layer. It sits in three places: how work orders and operations are coded, how fields mean and format what they hold, and how go-live is coordinated. The transport question — direct database write, HTTP API, or message queue — is covered in how visual SOP connects to MES. What follows is the vendor-specific reality once a transport has been chosen.

Difference one: how work orders and operations are coded

The most common trap is treating the MES "operation number" as a stable, universal primary key. In most systems a work order expands into several operations, each carrying a number or line number, but vendors name and nest that model differently. The safe pattern is a composite key of work order + operation + product serial number, never the operation number on its own.

• In SAP, the PP module ties a production order to operations, whose numbers are typically sequence numbers bound to the material and routing.
• Siemens MES products (which vary a great deal between versions) lean on resource and routing models to describe stations and operations, so the numbering follows however the site was modelled.
• UFIDA structures work orders and operation line items more like a document with lines, where an operation is often not a standalone key.
• Kingdee builds on production task orders, where operation numbers are generally combined with the order and product code.

Difference two: field meaning and format

Normalising the result field is the easiest step to overlook. The vision side may produce several states — pass, exception, skipped — while the MES target field accepts only OK/NG. Without a mapping layer in between, exception and skipped collapse into one value and no one can later tell "done wrongly" from "never done". Batch versus serial is the other structural choice: unit-traceable products (auto parts, 3C devices) are recorded by serial, which is the pattern behind automotive parts assembly and 3C electronics; process-manufactured goods (food, chemicals, textiles) can only be traced to a batch. The recording granularity on the vision side has to match what the back end can actually hold — see how to design visual SOP traceability.

Difference three: the go-live and integration split

• Test environment. Most plants run a single production MES, so integration tests need a booked window or a sandbox with no live data. Confirm which, early in scheduling.
• Change authority. Writing into MES usually needs a vendor consultant or the customer IT team, so who performs the change and how fast they respond must be agreed up front.
• Change window. Production systems are often only touched during shutdown windows, so integration testing is paced by the production calendar.
• Three-party communication. Equipment vendor, MES consultant and customer IT frequently understand the same task differently — issue a written confirmation after every integration session.

Reducing the back-and-forth