Skip to main content
Networking Hardware

Stop Chasing Protocols: Buy the Installed Base

Your plant's existing hardware should dictate your industrial network choices, not vendor hype. Here's why the installed base wins every time.

You're about to pick a network for your next machine or line. The vendor slides are glossy. The protocol debates are loud. And you're tempted to chase the newest, fastest, most open standard on the market. Don't. The single best move is to buy into the installed base you already have. If your plant runs Rockwell, you buy EtherNet/IP. If it runs Siemens, you buy PROFINET. If it runs Beckhoff, you buy EtherCAT. That's it. The most important networking hardware decision isn't which protocol is theoretically superior—it's which one your maintenance techs can troubleshoot at 2 a.m. without a manual.

The installed base is your real standard

Protocols don't win on technical merit. They win on volume. PROFIBUS & PROFINET International reports more than 68 million PROFIBUS nodes and over 69 million PROFINET nodes installed worldwide as of the end of 2023 (PROFIBUS & PROFINET International). That's not a recommendation; that's a moat. When you choose PROFINET, you're choosing a supply chain, a training ecosystem, and a spare-parts inventory that already exists. The same logic applies to EtherNet/IP, which runs the Common Industrial Protocol over standard Ethernet and dominates North American Rockwell/Allen-Bradley platforms (OPC Foundation). You don't need to like it. You need to support it.

Here's the contrarian part: the protocol with the best specs often loses. EtherCAT delivers cycle times of 100 microseconds or less and jitter below 1 microsecond (EtherCAT Technology Group). Sercos can hit 31.25 microseconds (Sercos International). Those numbers are impressive. But if your plant standardized on Allen-Bradley PLCs a decade ago, dropping an EtherCAT line into the mix means your electricians now need two sets of tools, two training paths, and two spares kits. That overhead eats the performance gain before the first production run.

Why 'best protocol' arguments miss the point

You'll hear engineers argue that OPC UA is the only future-proof choice because it's vendor-neutral, platform-independent, and has built-in encryption and authentication (OPC Foundation). They're right about the technology. OPC UA is standardized as IEC 62541 and is the backbone for IT/OT integration (IEC 62541 OPC UA Standard). But OPC UA doesn't replace your fieldbus. It sits above it. Protocols are layered: Modbus, PROFINET, and EtherNet/IP connect field devices and PLCs, while OPC UA and MQTT carry data securely to SCADA, MES, and cloud systems (OPC Foundation). You still need a deterministic network at the machine level. So the 'best protocol' debate is really a debate about the wrong layer.

Now the strongest counter-argument: 'If I lock into one vendor's ecosystem, I'm trapped. Open standards prevent that.' Fair. But open standards are only open if multiple vendors actually implement them. EtherNet/IP runs on standard, unmodified Ethernet and supports star, linear, and device-level ring topologies (ODVA EtherNet/IP). That's genuine openness. The trap isn't the protocol; it's buying hardware from a vendor that doesn't support the protocol you already run. You can buy EtherNet/IP drives from dozens of vendors. You can't buy a Siemens-only PROFINET device and make it speak EtherNet/IP without a gateway.

Hardware is where the money and the pain live

Look at where the spending goes. Hardware—robots, PLCs, sensors, HMI panels—dominates with 50% to 60% of the industrial automation market share (Maximize Market Research). In the IIoT market, the hardware segment (sensors, processors, connectivity ICs) accounts for the largest share, ahead of software and platforms (MarketsandMarkets Industrial IoT Report). You are not buying software-defined networking nirvana. You are buying switches, cables, connectors, and I/O blocks. Those components live or die by the installed base.

Here's a concrete example. You're adding a new packaging line with 40 IO-Link sensors. IO-Link is the first globally standardized I/O technology (IEC 61131-9) and uses point-to-point communication over the standard 3-wire sensor connection (IO-Link Consortium). It's not a fieldbus. If your plant runs PROFINET, you buy PROFINET IO-Link masters. If it runs EtherNet/IP, you buy EtherNet/IP IO-Link masters. The sensors are the same. The masters are not. Pick wrong and you're buying 40 gateways or rewiring the cabinet.

Decision factor Choose installed base Choose best-of-breed protocol
Spare parts Already on shelf New SKUs, new lead times
Technician training Existing skills apply New certs, new tools
Performance ceiling Good enough for 90% of apps Best-in-class for motion
Vendor lock-in risk Moderate if protocol is open Low at protocol level, high at tooling level

How to make the call without regret

Ask three questions before you buy anything. First: what protocol does your existing PLC platform speak natively? Second: can your maintenance team troubleshoot it without calling a specialist? Third: does the hardware you're buying support CIP Security or an equivalent that helps you comply with IEC 62443 (ODVA EtherNet/IP)? If the answer to any of these is no, stop.

  • If you run Rockwell, standardize on EtherNet/IP and use CIP Security for compliance.
  • If you run Siemens, standardize on PROFINET and use its real-time classes for motion.
  • If you run Beckhoff, standardize on EtherCAT and use its distributed clocks for synchronization.

Quick tip: Before you specify a single switch, walk your plant floor and count the protocol logos on existing hardware. That count is your real standard.

One more thing. Don't let the IIoT hype pull you into a rip-and-replace. The industrial IoT market is growing fast—projected to rise from $198.2 billion in 2025 to $286.3 billion by 2029 (MarketsandMarkets Industrial IoT Report)—but that growth is built on brownfield deployments. CISA identifies brownfield—layering legacy infrastructure with modern OT systems—as a challenge unique to ICS (CISA Industrial Control Systems). The winners are the ones who add OPC UA and MQTT on top of existing fieldbuses, not the ones who tear them out. You can run MQTT for cloud messaging with minimal resources (MQTT.org) while keeping your PROFINET or EtherNet/IP machine network intact. That's the pragmatic path.

Bottom line

Buy the networking hardware that matches the installed base you already have. If you're a Rockwell shop, that's EtherNet/IP. If you're a Siemens shop, that's PROFINET. If you're a Beckhoff shop, that's EtherCAT. Stop chasing protocol purity. Start counting the logos on your existing machines. That's your standard, and it's the only one that will keep your line running at 3 a.m.

Sources

  • PROFIBUS & PROFINET International (PI) - https://www.profibus.com/technology/
  • OPC Foundation - https://opcfoundation.org/
  • Maximize Market Research - https://www.maximizemarketresearch.com/
  • MarketsandMarkets Industrial IoT Report - https://www.marketsandmarkets.com/Market-Reports/industrial-internet-of-things-market-129733727.html
  • CISA Industrial Control Systems - https://www.cisa.gov/topics/industrial-control-systems

Share this article:

Comments (0)

No comments yet. Be the first to comment!