Hire Esri Utility Network specialists for electric ArcGIS UN programs

What Utility Network staffing is not

This is not a generic ArcGIS Pro upgrade. It is not Portal theming. It is not a water or gas UN resume dropped onto an electric ADMS program. Those estates share vocabulary and diverge on device modeling, phase, and protective-device hierarchy.

We will not declare the estate modern because topology is clean. Subnetwork definitions, export to ADMS, and representative operational traces are the proof. If you needed a training class, buy it from Esri. If you needed editors, use GIS specialists. If you needed a conversion lead with FME and policy, use senior GIS engineers.

UN concepts we actually interview

Expect questions on structural versus connectivity associations, containment, terminal configuration, midspan connectivity, dirty areas, validate network topology, subnetwork controllers, and the difference between a geometric-network weight and a UN attribute. Ask how a normally open tie is modeled so a trace and an ADMS import agree. Ask what happens to branch versions when two editors post conflicting device status.

Migration questions matter more than UI tours. Source classes, asset-group mapping, rule explosion, orphaned associations, and how rejected features return to the source system separate people who have cut over a territory from people who completed a sandbox tutorial.

Who we match on Utility Network programs

Typical fills: UN configuration specialists, geometric-network conversion engineers, electric data-modelers who can sit with ADMS import owners, and testers who can write a trace suite that operations will recognize. Accenture-shaped solution-architect titles are thinner; we will not invent that bench. Validators who understand UN errors but do not configure rules belong on the validation page.

Integrators buy UN surge. IOUs buy people who will not “fix” a rule to silence a dirty area that is actually a field error. Name Smallworld or a mixed estate if UN is only one source.

Utility Network hiring markets

California IOU conversion programs, Oncor-scale North Texas, ComEd consulting delivery, Duke territory, Southern Company Atlanta, and AEP Columbus show UN language most often. Seattle and Renton appear when Puget Sound programs name Esri next to ADMS adapters.

City pages keep local utilities and pay. This page keeps UN mechanics. We still refuse role-by-city UN URLs.

Scope a Utility Network engagement before you hire

Write the source and target, not “implement UN.” Identify geometric network, another Esri model, Smallworld, or a vendor extract. Record feature counts, association volumes, subnetwork count, and whether editing will be service-based on day one or after a dual-run. Dual-run estates need an explicit system of record for each attribute or two teams will both be right and the ADMS will be wrong.

Rule design is a product decision. Asset groups, categories, and network rules encode operating practice. Candidates should explain how they workshop those rules with protection, GIS, and operations, and how they prevent a rule change from becoming an undocumented hotfix. We look for change control, not hero edits.

Branch versioning, reconcile and post, and conflict policy belong in the brief. Storm weeks and contractor dump weeks break sloppy version strategies. Ask how the candidate isolated a bad post without freezing the whole territory. Ask how quality rules run before reconcile, not only after a weekend batch.

ADMS and OMS consumption is the acceptance test that matters to this practice. A UN that traces beautifully and still fails vendor import is unfinished. Name the ADMS vendor, the export or adapter, and the non-production dry-run cadence. We can staff UN people next to ADMS testers. The utility still publishes and activates.

Buy a specialist for configuration and mapping. Buy a senior GIS engineer when policy and FME ownership sit in one seat. Buy a validation squad when exception volume is the constraint. Provide Enterprise versions, UN version, territory, milestone, and whether gas or water UN is in the same geodatabase so we do not mix electric assumptions into another commodity.

Diagrams, export named traces, and network diagrams are useful demonstrations only when they map to an operating question: feeder lockout, nested outage, or a switching prerequisite. We ask candidates to walk one failed validate-network-topology session and name the class of error they refused to silence. People who treat dirty areas as a dashboard to zero without reading the feature are a risk on electric estates.

How we match Utility Network specialists

Send UN versus geometric-network stage, Enterprise version, electric versus mixed commodity, ADMS vendor, and whether you need configuration, conversion, or trace testing. We return names when they exist. Solution-architect seats can be empty this week; we will offer conversion specialists or validators rather than a padded architect title.