Insights · Utility IT/OT hiring · 5 minute read

How to Staff Utility Distribution Model Validation

Staff the work so an electric utility can verify its own distribution model. A feeder pilot gives hiring teams a concrete way to define the roles, assess candidates, and agree on acceptance.

By Vitaver Staffing ·

This guide draws on the Vitaver Playbook’s Mission First principle: define the result the owner must be able to verify before assigning the work.

Define what an operator needs to trust

An electric utility preparing a feeder model for an advanced distribution management system (ADMS) needs to know whether the model represents the equipment and connections that operators depend on. A successful import only shows that the receiving system accepted some data. Before opening a requisition, name the first operational use and the person who will accept the evidence. For a pilot, the question could be whether operations can independently verify a specific feeder trace in a test environment before the model is promoted.

The U.S. Department of Energy’s ADMS implementation report emphasizes that accurate geographic information system (GIS) data and the ongoing process for maintaining it both support the ADMS. Pacific Northwest National Laboratory’s model validation research also distinguishes the need to validate the static and operational network models. Those two points explain why a team needs people who can trace defects back to their source and people who can judge the effect on the receiving application.

Match the roles to the evidence

A small implementation can combine roles if the people have the relevant skills and their authority is clear. If the source inventory is uncertain, prioritize a GIS specialist who can resolve discrepancies with distribution engineering. If the source is reliable but the target changes identifiers or connectivity, prioritize integration and validation expertise. Budget for the utility reviewers and any field verification alongside the external staffing effort.

Use one test case to see how candidates think

Give each candidate for the same role an equivalent, fictional feeder diagram and a short set of source and target records. Include a three-phase segment, a downstream lateral, and a switch represented differently in the two exports. State which snapshot is authoritative for the exercise and which operating scenario the model should represent. Ask the candidate which discrepancy they would verify first, what evidence would let them resolve it, and which decision needs an operations or engineering owner.

A GIS candidate might trace an unconnected endpoint to a source edit. An integration candidate might compare asset identifiers and transformation rules. A model engineer might show that two snapshots represent different assumed switch states and ask which one the trace is meant to test. Score observable work such as locating the mismatch, distinguishing evidence from an assumption, and defining a rerun with an expected result. Use a synthetic or approved sample with no live network access or real system details.

Make the pilot acceptance repeatable

For an illustrative first feeder, retain the GIS revision, transformation version, resulting run ID, expected traces, actual results, and unresolved differences. The technical lead should agree with operations on a handful of representative cases, including a recent asset change and an expected disconnection. Record who can confirm each exception and when they will do so. Ask a utility team member to rerun the agreed checks from the handoff notes before closing the pilot.

In the staffing request, specify the environment and approved access, site or remote expectations, review windows, first deliverable, and the acceptance owner. Schedule the acceptance review before the engagement starts. Keep production promotion with the utility’s authorized decision maker. An open discrepancy that could change the expected trace is a concrete reason to hold that case and name the next person who can resolve it.

← All Insights