Theme: Shared communications with unchanged process accountability
Quick definition
IP-based automation uses Internet Protocol for addressing and packet transport in one or more parts of an automation system. IP may carry supervision, configuration and some control flows over Ethernet or other links. It does not imply that every sensor has an IP address or one network suits every function.
In context: where IP fits
IP is a network layer, not a complete automation architecture. Application protocols, information models, link technologies and physical I/O sit above or below it. Fieldbuses and local control links can coexist with IP, sometimes behind gateways or edge devices.
For example: an automation network
A building system may use BACnet/IP between controllers and a supervisory interface while sensors remain locally wired. In manufacturing, controls may send diagnostics to a maintenance service over IP without that service participating in the fastest control loop.
Determinism and safety remain
IP adoption changes transport options; it does not remove requirements for cycle time, jitter, priority, availability or functional safety. Suitable protocol profiles, network design, local logic and verification must meet those requirements. Ordinary TCP/IP does not automatically provide a timing guarantee.
Opportunities
Shared tools and skills can simplify addressing, diagnostics and governed data access. IP may remove some specialist links and make services easier to integrate. Benefits still depend on clear names, semantics, version management and ownership.
Limitations and risks
Greater reach can increase failure and attack surfaces. Broadcast traffic, incorrect routing, central-service dependencies or an overloaded link may affect operations. Segmentation, capacity analysis, redundancy, access control and monitoring must be designed for process consequence.
HubMind’s view
Choose IP where it creates a maintainable boundary, not as an objective in itself. Separate information requirements from transport and fast-control requirements. Prove behaviour under load, outage, failover and restart before calling it shared infrastructure.
A practical next step
Classify each flow by latency, jitter, volume, consequence and fallback needs. Mark functions that must continue locally. Only then select protocols, network segments, priorities and monitoring.
Related concepts
Sources and further reading
Scope and freshness
IP use in OT with NIST SP 800-82 Rev. 3 for operating and security context and IEEE 802.1Q-2022 for bridged networks. No industrial profile is prescribed. Reviewed 31 August 2026.