Blog / Technical guide
Specifying remote access for a water operations platform
Define user roles, audit records and offline behavior before adding remote plant access.
HOSON WATER editorial ·
Separate monitoring from permission to act
Define the users who need to see trends, acknowledge alarms or change equipment settings. Identify which actions remain local and which, if any, are permitted remotely. Keep privileges tied to named roles and use site-approved authorization for service access. Require multi-factor authentication for remote access where appropriate to the approved design.
Verify communication failure behavior
The local plant should have an agreed operating response when the connection to a remote platform is unavailable. Ask what equipment logic remains available, whether the gateway buffers data and how the dashboard marks stale readings. Test loss and restoration of connectivity during commissioning and verify that a restored connection does not trigger an unexpected action.
Set ownership for access and incident review
Record who provisions accounts, reviews access logs, removes contractor access and approves updates. Confirm the data collected for each remote session and how staff report suspicious changes. Include a method to disable remote access while retaining safe local operation so the owner can respond to a problem without a supplier visit.