Five platforms, one team: why multi-platform capability matters in 2026

Walk a Maritime plant floor and count the control platforms. On a site of any age you will usually find at least three, sometimes five: an Allen-Bradley line installed when the plant expanded, a Schneider panel that came with a piece of European equipment, an Omron controller inside an OEM machine nobody has opened, and something from a vendor that no longer exists.

This is normal. Plants do not buy control systems. They buy machines, and the control system arrives inside them.

The single-brand problem

Most integrators specialise. There are good reasons for it: depth in one platform is genuinely valuable, and certification programmes reward it. The difficulty is what happens at the boundary.

When a line contains three brands and your integrator knows one, two things follow. The parts they know get modernised and the parts they do not get worked around. And when something fails on the unfamiliar equipment, the response is a referral rather than a fix. The plant ends up holding relationships with three suppliers to keep one line running.

What multi-platform actually means

Bedford programs five PLC platforms in-house: Allen-Bradley, Schneider Electric, Omron, Phoenix Contact PLCnext and Unitronics, with the SCADA and HMI layer above them. That is a statement about staffing rather than a badge. It means the person who takes the call has a reasonable chance of knowing the controller in question, and if they do not, the person at the next desk does.

Practically, it changes three things:

• Diagnosis is not delegated. When a line stops, working out whether it is the program, the drive or the field device does not wait for a third party.
• Migrations can be honest. If you are moving off obsolete hardware, the recommendation is not automatically the one brand we happen to sell. The right answer sometimes is the incumbent.
• Standards survive the boundary. Tag naming, documentation and backup practice can be applied across a mixed floor rather than stopping where the specialism does.

The IEC 61131-3 point

Platform breadth is only useful if what gets written is readable afterwards. Code written in the IEC 61131-3 languages your own electricians already read is the difference between owning a system and renting access to it. That is the standard we work to wherever the platform supports it; on a proprietary environment such as Unitronics we keep the logic just as readable and leave it unlocked, and it is why the program comes back to you with no locked routines.

Why it matters more here

In a dense industrial region a single-brand integrator works because there is another specialist an hour away for everything else. In the Maritimes there frequently is not. Breadth is not a luxury position in this market; it is what makes a mixed floor supportable at all.

If your line runs more than one brand and you are managing more than one supplier because of it, that is worth an hour of conversation. Start with what the controls team does, or call and ask directly.