Turn the drawing into operating knowledge
Start with drawings, configurations and supplier information. Walk through the boundaries with maintenance. Include occasional connections such as service laptops, cellular gateways and external services on which a local function depends.
| Connection | Operating purpose | What to establish if it fails |
|---|---|---|
| Line to production planning | Send count and order status | Can production continue? How are missing records reconciled? |
| Machine service to operator panel | Diagnose an authorised fault | Who can assist if the vendor portal is down? |
| Engineering station to controller | Apply approved changes | Where is the released project if the laptop has to be replaced? |
Why separate parts of a network?
A fault on an office computer should have limited reach into production. The machine also needs a defined response if an external service becomes unavailable. IEC 62443 groups assets with shared security needs into zones and considers permitted communication between them. A subnet is one design choice. The actual boundary depends on the traffic permitted across it and any alternative paths.
A useful outcome: Someone can identify the purpose, destination, direction and owner of each connection. Before any planned isolation, operations and maintenance understand the effect on local control, diagnostics and safe stopping.
Related reading
- Who can reach the machine during remote service?
- Understanding IEC 62443: what needs protection on this particular line?
- Could we restart the line from our backups?