Here are some examples of remote activities that the workgroup members strongly

suggest require escorted access to ensure proper procedures are followed:

• Modification or “soft jumpers” forcing a PLC output or loading new software

or control system updates should have someone present on-site via voice to
verify any activity at the site.
• Code changes, software installation, patches/updates, rebooting computers, and
any activity where safety is an issue. May also include any motion or functional
changes that affect the expected sequence of operation.
• Equipment that can cause bodily harm requires an on-site escort to verify
people are clear of moving parts.
• Have someone close to the PLC to place the key in remote mode when
downloads are required.
• Commissioning (supported by instrumentation/controls people in the plant).

Any action that can make anything move, turn on, heat up, or make a machine
dangerous needs someone by the machine. Any command to make a motion
should be started locally. Cordoning off specific machines in ways that prevent
entry to allow remote start may not require someone present.

Activities that can be performed without the need for escorted access
There are a few activities that do not require a local presence. Many of these
activities are passive and several are outbound in which they are continually
sending data. For example, monitoring, fault diagnosis, minor configuration, data
input and others.

Best Practice: Document all the Remote Access activities and classify them
into categories with definitions, guidelines and requirements. A matrix of
activities should be incorporated into your Remote Access Plan

Having a clear and defined list that includes individuals, assets, and processes
will provide a clear picture of what is required and help in your discussions
with IT.

2021 I Practical Guide for Remote Access to Plant Equipment 31