What Should a Plant Network Survey Check Before Expansion?
An industrial network survey before adding equipment should establish what is connected, how devices communicate and what condition the existing network is in. Check switch ports, addressing, traffic paths, cables and undocumented connections before deciding where new equipment will connect. Start with observation and approved read-only checks; put disruptive testing into an agreed maintenance window.
What should the survey establish before anyone connects equipment?
Begin with the proposed expansion. List the new controllers, operator panels, drives, instruments and data connections, including their intended locations and communication requirements.
Ask the equipment supplier for the proposed addressing, connection diagram and required network settings. Request any restrictions on discovery, diagnostics or configuration access for existing equipment.
Define the survey boundary around the communication paths the expansion will use. Include shared switches, links and supporting services, even when they sit outside the machine being extended.
Agree success criteria before starting:
- Every proposed connection has an identified switch and port.
- Address allocation has a named owner and a checked plan.
- Required communication paths are documented.
- Existing faults and uncertain connections have a recorded disposition.
- Installation, testing and rollback steps have an agreed window.
How do you establish the actual network topology?
Treat the existing drawing as a starting point. Walk the relevant panels and cabinets with someone who knows the equipment, and compare the drawing with visible connections.
Record each switch, its location, equipment identifier and accessible management details. Trace uplinks and machine connections through patch panels, intermediate cabinets and other connection points. Record physical connections separately from logical groupings, such as virtual networks and routed boundaries.
Where authorised, compare cable labels and drawings with switch neighbour information and forwarding tables. Follow unexplained connections as far as the agreed survey scope permits.
Distinguish three states on the drawing: verified, reported by others and unresolved. A line copied from an old drawing should not look identical to a connection checked during the survey.
Include maintenance access points, wireless links, remote access equipment and temporary switches. Give each unresolved connection an owner and a follow-up action.
What should be checked at each switch?
Inspect the switch as an operating asset, not simply as a collection of sockets.
| Check | What to record | Expansion decision |
|---|---|---|
| Port allocation | Connected device, label, configuration and reservation | Which ports are available for the project? |
| Operating condition | Uptime, alarms, error counters and link changes | Which observations need investigation first? |
| Port settings | Configured and negotiated speed, duplex and network membership | What settings does the new connection require? |
| Shared links | Uplink destination, traffic observations and equipment using it | Where is further capacity review needed? |
| Installation | Power supply, mounting, cabinet condition and access | Is additional hardware practical here? |
| Recovery | Configuration backup, access owner and replacement arrangements | How will the team restore service after a failed change? |
For an empty port, verify its intended use and configuration before allocating it. For an occupied port, identify the connected equipment before proposing a move.
Record the collection time and operating state alongside counters and traffic readings. Ask whether counters were recently reset. Avoid declaring a switch healthy or overloaded from one unexplained reading.
How should addressing and device identity be verified?
Build an address register for the affected scope. Include device name, equipment owner, physical location, hardware address where available, IP address, subnet mask, gateway and whether allocation is static or automatic.
Compare records with approved configuration exports and observations from the running network. Investigate mismatches before assigning addresses to new equipment.
Do not treat a silent address as available. Reserve proposed addresses through the plant’s address-management process, with checks for equipment that is powered down, disconnected or used only during certain operations.
Confirm who manages automatic address allocation, name resolution and address changes. Record the relevant network boundary for each device so that an address is not considered in isolation.
Give particular attention to packaged machines. Ask the supplier to identify machine-internal connections and the intended plant connection, rather than assuming every visible network socket is interchangeable.
Which traffic paths and operating conditions matter?
Map communication by purpose: machine control, operator displays, engineering access, production reporting, historian collection and remote support.
For each required flow, record the source, destination, protocol where known, operating schedule and route through shared equipment. Ask what the process should do when that connection is unavailable.
Choose observation periods with operations staff. Include relevant states such as startup, normal production, changeover and data transfer. Label anything not observed.
Use approved switch diagnostics, existing monitoring or an authorised traffic capture method. Before capturing traffic, agree the collection point, access permissions, storage and handling of captured information.
For the expansion, request expected communication behaviour from the supplier: destinations, update patterns, startup activity and any special network settings. Put unresolved capacity or compatibility questions into the design review instead of treating an apparently quiet network as proof of readiness.
How should cables and undocumented connections be checked?
Inspect accessible cables and terminations without disturbing operating connections. Look for damaged jackets, strained connectors, poor support, unreadable labels, improvised joins and routes exposed to movement or damage.
Record the cable type and the requirements against which its installation will be assessed. Check both ends where accessible, including patch leads and intermediate terminations.
Keep visual inspection separate from electrical or optical testing. If a proposed test requires unplugging a live connection, schedule it through the plant’s isolation and maintenance process.
For undocumented connections, use a simple sequence:
- Photograph or label the accessible endpoints under site rules.
- Compare them with switch records and equipment documentation.
- Ask the equipment owner to confirm their purpose.
- Record what remains unknown and how it will be verified.
Do not unplug an unidentified cable to discover what stops. Leave inaccessible or unverified sections clearly marked for planned follow-up.
Which survey methods are suitable for live plant equipment?
Agree a method statement with operations and maintenance before connecting survey equipment.
Start with drawings, operator interviews, visual inspection, existing monitoring and approved read-only management access. Treat active discovery, scanning and diagnostic requests as separate activities requiring equipment-specific review and authorisation.
Define the devices in scope, permitted actions, responsible contacts and conditions for stopping. Record the starting condition so that a later change can be compared with a known baseline.
Do not assume that approval to inspect includes approval to change switch settings, insert monitoring hardware, disconnect cables or restart equipment. Schedule those actions explicitly.
Where safety-related equipment or communication is involved, have the survey method and proposed changes reviewed with a qualified assessor. Record the boundary of that review.
What should the final survey deliver?
The deliverable should support a connection decision, not merely list equipment.
Include an updated topology, port schedule, address register, cable observations and a summary of operating conditions observed. Separate existing defects from work required for the expansion.
For every finding, state the evidence, affected equipment, required action, owner and verification step. Keep unknowns visible.
Illustrative example: a new inspection station needs a controller connection and a reporting connection. The survey identifies candidate ports but leaves their allocation pending confirmation of reservations, network settings and the reporting route. The expansion plan closes those questions before installation and defines how each connection will be tested.
Carry the agreed requirements into the functional design specification. Put disruptive checks, installation and rollback into the shutdown plan for the retrofit. If the survey shows machine and office traffic sharing a network, see how to separate machine and office networks.
What common mistakes should the survey avoid?
The main mistakes are accepting an old drawing without checking it, counting empty sockets as approved capacity, and allocating addresses from an incomplete list.
Other avoidable gaps include observing only an idle shift, recording counters without context, and leaving temporary connections out of the final drawing.
Keep the decision proportionate to the evidence. If a shared path was not observed during the relevant operating state, record the additional verification needed before approving the expansion.
What do plant teams commonly ask?
Can the survey be completed without stopping production?
Plan observation and approved read-only checks around live production. Identify any remaining cable tests, configuration changes or connection trials separately and agree when they can be performed.
Does every expansion require replacing switches?
Assess the existing equipment against the proposed connections and operating requirements. Recommend replacement only where the survey identifies a specific gap and explains how the proposed hardware addresses it.
What if some equipment cannot be accessed?
Record the limitation, affected connection and consequence for the expansion decision. Assign a way to resolve it, such as supplier-assisted inspection or verification during a maintenance window.
When is the network ready for the new equipment?
Approve connection when the agreed prerequisites are verified, unresolved items have an accepted disposition, and commissioning and rollback steps are assigned.
For help defining the assessment scope, see our automation services.