You are on page 1of 1

As an automation vendor, everything we do remotely is collaborative;


if it’s gotten to the point that we need to be involved, we want the
machine builder who wrote the code to be with us so we can teach what
we are doing to increase the independence of the machine builder/
end user. Any command to make the machine operate should be issued
locally by someone who can see and verify if it is okay.

Best Practice: Have discussions with potential parties to


understand how they provide Remote Access support and
review your organizational and process structure to align.

Establish access rules that relate to machine states (e.g., if the


machine is in production, other privileges apply as opposed to a
machine currently in downtime).

Here are some rules for your consideration:

• Any rules that apply to access the equipment locally should also apply
to remote equipment access.
• Safety rules should apply to hazardous chemical area sensors and
protection equipment.
• Develop a manual process based on a mutual agreement that the third
party does not access without approval.
• A machine in production should only allow for read/view access. Offline
or backup machines can be allowed remote control provided there are
no safety concerns.
• There must be something like a traffic signal, where the access rules
are clearly defined.
• If the machine is in production, one shouldn’t be able to access the PLC
without an escort.

2021 I Practical Guide for Remote Access to Plant Equipment 34

You might also like