The need and approach
The ability to click a remote button is not a complete control architecture. Identity, authorisation, network boundaries, command validity and physical safety are distinct responsibilities.
Data flow
Authorised user → operation approval → command checks → local acceptance → verified result and audit record.
A requested command, an accepted command and an observed physical outcome are separate states. Expired commands are rejected; old commands do not execute automatically after reconnection.
Illustrative workflow
At a remote pumping site, an authorised person requests an operation. The field component evaluates it only when local conditions and approvals permit, and the outcome is verified separately.
Questions for discovery
- Which operations truly need remote access?
- Which roles may act under which conditions?
- How are local interlocks and safety preserved?
- Which actions need a second approval?
- What is the safe state during communication loss?
How is remote control scope limited?
Identify exactly which operations may be requested for each piece of equipment. User roles, preconditions, local/remote mode and any second approval are assessed separately. The web application creates a request; the field component evaluates it against valid local conditions.
Keep the operation identifier, requester, approval time, delivery state and field result distinct. A successful network response is not evidence that a pump or machine physically reached the requested state.
Failure scenarios for commissioning
Test connectivity loss, delayed responses, duplicate requests, unauthorised users and unmet local conditions. An operation that times out should not automatically be repeated while its outcome is unknown.
Remote monitoring may be sufficient when no control action is needed. Adding control requires its own assessment and acceptance process beyond the existing monitoring project.
Limits and field conditions
Emergency stops and physical protection cannot be replaced by the web application. Security and process safety need coordinated specialist assessment.
Common questions
Can a pump or machine be controlled over the internet?
It can only be scoped where a suitable field interface, authorisation, local conditions and safety assessment are in place. Adding a web button alone does not create a safe control solution.
What happens when the internet connection fails?
Safe behaviour must be defined for the equipment and process in advance. Field owners validate which requests are blocked and which local functions continue. There is no single safe behaviour for every installation.
What information is needed for remote control integration?
Provide the operation list, equipment models, existing control architecture, local interlocks, user roles, field owners and available outcome feedback. Physical implementation, software and commissioning responsibilities must be clarified separately.