Access Official Technical PDF

Share Summary:LinkedInEmail

Connected machines can give manufacturers and equipment builders a way to make machine telemetry available beyond the local operator station. For industrial automation teams, the value depends on more than adding network ports: equipment must fit the plant’s network architecture, support the application’s communication requirements and be protected through appropriate security controls.

This is particularly relevant for machine builders serving production environments with multiple dependent systems and equipment from different vendors. When machines operate in isolation, telemetry can remain difficult to access, limiting visibility into the wider process and making remote support impractical. A considered industrial networking approach can provide a foundation for monitoring and operational services while keeping plant requirements in view.

Why connect machines to the plant network?

In a disconnected architecture, machine data may be available only to local operators. Operations teams then have less visibility across production equipment, while machine builders and integrators lack a network path for remote support. Manual inspection may remain necessary, and telemetry from different parts of a multi-vendor production chain can be difficult to bring together.

Networked machines can provide a basis for collecting standard telemetry and making it available for monitoring, alarms and analysis. When the data is accessible across the relevant production process, teams can investigate machine and process conditions with a broader view. Connectivity can also support remote assistance and control, subject to the plant’s operational and security policies.

For an original equipment manufacturer (OEM), embedding suitable networking in a machine may also make integration more consistent for system integrators and end users. The network design still needs to account for the customer’s requirements, including scale, resilience, complexity and management tools. A single design is not automatically suitable for every machine or facility.

Connected machines need an industrial network design

Industrial control system (IACS) networks have communication needs that differ from typical enterprise applications. Depending on the process, traffic may need low latency and low jitter to support more deterministic communication. Requirements vary: monitoring and information exchange may tolerate longer intervals than time-critical factory automation or multi-axis motion applications.

Start by documenting what the application needs to communicate, how quickly it needs to communicate and what loss of connectivity would mean for the process. These requirements inform choices such as network topology, switch capabilities and resiliency protocols. Resiliency is application-driven: the appropriate approach depends on the required recovery behavior, network layout and whether the design includes mixed-vendor equipment.

Industrial Ethernet switches can form part of a cell or area network, connecting a machine, machine ensemble or skid to the wider manufacturing network. Equipment selection should reflect the installation environment and design requirements, including mounting, power, port types, temperature and ingress protection. Management needs matter too: teams should decide how devices will be configured, monitored and maintained.

Use segmentation to make the network manageable

A flat network can make it harder to isolate faults and manage traffic. Broadcast traffic can spread more widely than intended, and a compromised or malfunctioning device may have unnecessary reach. Industrial network segmentation divides the environment into smaller zones, helping teams limit communication paths and troubleshoot within a more defined scope.

Cell/area zones are commonly organized around devices that communicate consistently with one another. VLANs and IP subnets can provide the basis for this separation. The design should specify which devices belong in each zone, which traffic is permitted between zones and where routing is required. Multicast traffic used by communicating devices also needs to be considered when assigning VLANs.

Segmentation is not a substitute for security policy. It provides a structure for applying controls, such as access control lists and rules governing traffic between manufacturing and enterprise environments. Document the addressing plan, trust boundaries and required connections before deployment.

Build security into connectivity and remote support

Security is more difficult to retrofit when it has not been considered during architecture design. A sound approach addresses network boundaries, device and communication protection, visibility, data security and administrative access. It should also account for the operational realities of IACS devices, some of which may not support the authentication methods used by standard IT systems.

Practical measures include developing a plant-specific security policy, restricting physical access to network infrastructure, disabling unused switch ports and applying suitable access and authentication procedures. Keep industrial protocols within the manufacturing environment rather than exposing them to generally available networks. Use secure management protocols and maintain configuration backups so approved changes can be tracked and recovered.

Remote access should be controlled rather than treated as a direct extension of the enterprise network. A design can place access services in an industrial demilitarized zone (IDMZ), use firewalls to inspect and restrict traffic, and provide remote users with approved applications on controlled servers. Access should be limited to the systems and functions required, with authentication and monitoring applied at the appropriate points. The specific implementation must align with plant policy and the automation application.

Plan deployment as a managed lifecycle

A phased process helps connect machines without losing sight of operational requirements:

  1. Assess: Document current and future capacity, application performance needs, segmentation, remote access, services and security policies.
  2. Design: Choose the topology and addressing approach, review cabling and define how machine cells connect to the plant network.
  3. Prepare: Create version-controlled configuration templates and decide how network configuration and monitoring will fit existing tools.
  4. Deploy: Install and configure equipment according to the documented design, coordinating work with operations and automation teams.
  5. Manage: Monitor connectivity and network use, review configuration changes, and establish alerts and reporting for ongoing support.

Network management tools can help operations and plant IT teams view automation-device connectivity, investigate issues in context and integrate network information with existing applications. The goal is a shared operational picture, not simply a switch inventory.

Conclusion: connect with purpose

Connected machines can improve access to production telemetry and establish a foundation for monitoring and remote support. Realizing those benefits requires an industrial network designed around application performance, clear segmentation and controlled access. For machine builders, integrators and plant leaders, the practical priority is to define requirements early, make security part of the architecture and manage connectivity through a documented deployment and support process.

Access Official Technical PDF

About The Author