Insights · Utility IT/OT hiring · 5 minute read

How to Staff a Water Utility Historian Migration

After a historian migration, a water utility should still be able to reconstruct what happened at a pump station. Use one operating event to define the staffing, test the transfer and decide when the replacement is ready.

By Vitaver Staffing ·

This article draws on the Vitaver Playbook’s Mission First principle. Start with a decision the utility must still be able to make after the migration, then assign someone to prove it before the old system is retired.

Ask an operator to reconstruct one event

A water utility replaces the historian that stores readings from its supervisory control and data acquisition system. Before the switch, choose a question the operations team already needs to answer. In a hypothetical pump station, it might be: Did the pressure drop before the pump stopped, or did we lose the pressure signal while it was still running? The operations supervisor should select an approved historical example and document what the available evidence can establish. Include an interval with a known telemetry gap so the team can see how both systems represent missing information.

A historian stores measurements and equipment states over time. A trend can look familiar even when the underlying records differ. A unit conversion can shift the scale, a timestamp conversion can move the apparent order of events, and a dashboard can draw a line through a gap. The OPC Foundation’s Historical Access specification describes reading stored values with their quality and timestamps. Its read-at-time operation also distinguishes an interpolated result from a recorded value. If your systems use different interfaces, verify how each one represents the same distinction.

Give each part of the migration an owner

One engineer may cover both technical assignments. The staffing brief should specify which judgments the utility retains, the site and shift coverage required for testing, and who authorizes access. Describe the exact collection or archive work before naming a platform requirement. Use an approved test environment or read-only export for the first comparison. NIST’s guide to operational technology security explains why reliability, performance and safety matter in these environments.

Use a small interview exercise with a real discrepancy

Give applicants for the same role the same fictional source and target excerpts, a data dictionary and enough time to explain their approach. In one sample, a pump stop appears twice after import, and a missing pressure reading shows up as a zero with good quality. Ask what each discrepancy could change about the operator’s conclusion, what evidence would distinguish an export problem from a display problem, and who should resolve it. Score identification of tag identity, time and quality issues, the proposed comparison, and a defensible escalation. If formal access is required for the assignment, have the authorized team verify it separately.

Keep the old archive available until the utility can repeat the check

Before switching, compare stored samples, timestamps, units and quality flags for the chosen points. Check the operator-facing trend and any report that consumes those points separately. Agree in advance which differences are expected, which require correction and which justify a hold. Record an owner and retest date for anything deferred. If migrating rarely used history would take time away from validating active points, consider keeping an approved read-only archive and test that staff can retrieve an older interval from it.

During the first agreed shift after cutover, have the receiving operator verify that new readings are arriving and that the historical event can still be reconstructed. The handoff is complete when utility staff can repeat the comparison, explain any gaps and find the evidence without calling the migration team.

← All Insights