Telemetry projects can appear complete when screens show live values, yet hidden configuration and recovery issues may remain. A structured test programme confirms that every important point and function behaves as approved. It also gives operators and maintenance teams evidence they can use after handover.

Prepare traceable test documents

Test procedures should connect requirements, drawings, point lists, control descriptions and acceptance criteria. Each test needs an expected result, actual result, witness record and status. Defects should be numbered, assigned, corrected and retested rather than recorded only in meeting notes.

Freeze the relevant document revisions before formal testing. If point addresses or logic change during the test, the affected drawings, software and procedures must be updated. Buyers should retain a clear record of the final accepted configuration.

Factory acceptance testing

Factory testing allows panels, PLC programs, RTU configurations and SCADA applications to be reviewed before equipment reaches site. Simulated signals can verify ranges, units, status changes, alarms, interlocks, sequences, trends and reports. Communication between major components should also be demonstrated.

The client should agree which functions can be accepted in simulation and which require site conditions. Factory tests are particularly useful for identifying inconsistent naming, missing points and screen-navigation problems while changes are easier to make.

Site installation checks

Before live testing, confirm panel installation, power, earthing, surge protection, cable identification, environmental protection and communication equipment. Instrument calibration records and wiring checks should be available. Remote sites need antenna, battery and enclosure inspection.

Point-to-point testing follows each signal from the field device through the PLC or RTU and network to the SCADA display and history. Commands should be checked in the reverse direction, including permissions, confirmation and field response. Testing only the software address does not prove the installed instrument or wiring.

Prove alarms, sequences and failures

Alarm tests should verify setpoints, delays, priorities, messages, timestamps, acknowledgement and notification routes. Repeated or nuisance alarms should be corrected before handover. Operators need to understand the condition and required response from the message shown.

Control sequences should be tested under normal, abnormal and manual conditions. Include instrument failure, pump trip, communication loss, power interruption, server restart and restoration. The system should return to a defined state without executing unsafe or stale commands.

Complete operational commissioning

Commissioning confirms performance with the real process operating. Staged activation may be required where existing systems remain in service. The project team should agree cutover plans, rollback arrangements, operator coverage and restrictions during testing.

Acceptance periods can reveal intermittent communication faults, alarm floods and reporting issues that short tests miss. Performance measures may include network availability, missing data, alarm delivery, server recovery and operator response. Any temporary bypass or outstanding defect should be visible and controlled.

Control defects and late changes

Not every defect has the same consequence. Classify issues by safety, operational impact, data integrity and usability, then define which categories prevent acceptance. The owner should know the status of every open item and the planned correction date. Verbal promises should not replace a controlled defect register.

Late process changes can affect logic, screens, alarms, reports and training material. Use a formal change process during commissioning so revised requirements are assessed and retested. Emergency site adjustments should be incorporated into the master source files before handover.

Deliver usable handover information

Handover should include as-built drawings, point lists, control descriptions, PLC and SCADA source files, configuration backups, licences, passwords, test records, equipment manuals, warranties and spare-parts lists. Backups need a documented restoration method, not just a storage device.

Training should be role-based. Operators need displays, alarms and reports; maintainers need diagnostics, isolation and component replacement; administrators need user, backup and recovery procedures. Practical exercises are more useful than a single general presentation.

Handover records should be checked for consistency. Model numbers, network addresses, software versions and point names must match the installed system. A document package assembled from earlier design revisions can be misleading during future fault finding, even when every expected file is present.

Plan preventive maintenance and support

Maintenance may cover instrument calibration, enclosure condition, battery tests, communication performance, server health, backups, software updates and spare equipment. Frequencies should reflect manufacturer guidance, site environment and operational consequence. Records help identify repeated faults and ageing components.

Useful maintenance indicators include communication availability, battery test failures, repeated device restarts, unresolved alarms, server storage, backup success and time to close faults. Reviewing these trends helps the owner plan replacement before a hidden weakness becomes an outage.

The central telemetry systems procurement guide explains why testing, documents and support should be included in the supplier comparison from the beginning. Adding them after award can leave scope gaps and uncertain cost.

Support agreements should define response levels, remote access controls, site attendance, exclusions and escalation. Buyers should periodically test recovery and confirm backups remain usable. A telemetry system is operational infrastructure; sustained value depends on disciplined maintenance and the owner’s ability to recover it when components or communications fail.

Buyer references