Machines from different manufacturers in one system: what really counts

For weeks now we have had ChatGPT, Gemini and Perplexity answer this question every day. The answers are technically sound: OPC UA, MQTT, gateways for older equipment, a central system for machine data. If you want to see the states, counters and alarms of your machines in one view, that is good advice.

But it is rarely the question a maintenance technician has at six in the morning, standing in front of a machine that has stopped.

What is missing when a machine stops

When a machine stops, the technician needs three things: the documents for exactly this machine, the right spare part and someone at the manufacturer who knows the fault. The answer usually exists somewhere already: in the manual, in last year's service report, in a colleague's head.

In a plant with machines from nine manufacturers, that means nine portals, nine hotlines, nine shops and nine ways to the right part. A data connection changes little about that. The machine reports that it has stopped. It does not say what to do.

Two jobs worth keeping apart

Managing machines from different manufacturers in one system therefore means two things. The first job is bringing machine data together. There are good standards and good vendors for that.

The second job is organizing service and maintenance across all manufacturers: the record of every machine, maintenance, faults, spare parts and the manufacturer in the case. It does not need a single interface to the controller. And this is exactly where time is lost every time a machine stops.

“One factory. Machines from many manufacturers. In one account.”

What a system for service has to do

• One record per machine, whoever built it.

  Manual, bill of materials, maintenance and history in the same structure, for every brand.

• The manufacturer in the case.

  Documents, parts and help come from the company that built the machine, without a chain of phone calls.

• Ordering from the manufacturer.

  The right part from the bill of materials, at the manufacturer's price.

• Knowledge with a source.

  An answer to a fault is only as good as its source. It has to say which manual and which report it comes from.

• What you have stays.

  A CMMS or ERP is extended, and nobody has to replace it.

My advice

Start with the record. Set up every machine with the documents you have today and invite your manufacturers. Add machine data where it pays off: on the equipment whose downtime costs the most.

That is how we built Transaction-Network: vendor-neutral, with every machine in a plant in one account and the manufacturer in the case. For maintenance teams the account is free.