Technical services
GIS, OMS, and ADMS data validation
GIS, OMS, and ADMS data validation for connectivity, phasing, and as-operated models in non-prod, before go-live, not live DMS.
Best for
- Pre-load validation for GIS, OMS, or ADMS migrations
- Connectivity, phasing, hierarchy, and customer-link quality
Deliverables
- Rule-based checks, exception queues, and remediation metrics
- Dry-run results and traceable model-readiness evidence
Not included
- Ownership of authoritative source-data corrections
- Production go-live approval or live DMS operation
GIS, OMS, and ADMS data validation
GIS, OMS, and ADMS data validation is where most ADMS delays actually live. Connectivity, phasing, customers, as-operated models, before go-live, in non-prod. Esri, ADMS imports, OMS, and CIS extracts collide here. Transformer-customer exceptions and feeder-trace failures need a defect queue shared with GIS and ADMS engineers, not a hopeful dashboard.
This work can be delivered without operating a live DMS. The brief should name the source GIS, target ADMS and OMS, model-load cadence, known exception classes, and acceptance owner rather than describing the problem only as data quality. GridWorksPositive matches validators for Dallas growth metros, California IOUs, Duke territory, and ComEd programs, with dedicated squads and a U.S. lead for model-load seasons.
Transformer-customer exceptions, feeder-trace failures, phasing mistakes, and CIS joins show up as Jira noise until someone owns the queue. Validators sit between GIS engineers and ADMS testers. Overnight production GIS heroics are not the offer. If go-live is six weeks out and the exception aging is already red, use the project form for a squad rather than one contractor lost in a spreadsheet.
What data validation is not
We do not fix GIS in production overnight. We queue exceptions and re-test in non-prod. Activation stays with the utility. We do not replace your GIS team with web mappers. Electric tracing skill is the filter versus web GIS.
OMS is in scope when outage and customer-to-transformer links are named. If you only needed a data-entry vendor, you would not need this page. Pair with utility GIS engineers and ADMS/SCADA QA so exceptions have both a GIS owner and a test owner.
Connectivity, phasing, OMS, and imports
Screens: traces, phasing, substation internals versus feeder landbase, CIS joins, OMS device-to-customer, ADMS import dry runs, exception aging. Related pages: utility GIS engineers, ADMS engineers, OMS/DERMS engineers, SCADA testing services.
Dallas, Frisco, McKinney, Chicago, Naperville, Raleigh, Atlanta, Sacramento, Los Angeles are typical buyers. Houston appears for CenterPoint-scale landbase, not pipeline alignment sheets.
Who we staff for validation
Electric GIS validators, ADMS import testers, OMS data analysts, and a U.S. lead on model-load squads. Integrators buy surge. IOUs buy standing exception queues before a cutover.
specialist matching for named validators. Project brief for a season. We will not claim the as-operated model is clean because a count went down.
Validation markets we serve
Oncor-scale DFW, Duke Triangle and Charlotte, Ameren St. Louis, ComEd Chicago, Southern Company Atlanta, California IOUs. Satellite: Joliet, Elgin, Chapel Hill, Marietta, Riverside. City pages carry local utilities; this page carries the ADMS/OMS vocabulary.
Hire GIS/OMS/ADMS data validation through the project form when you need a queue owned, not a single contractor lost in a spreadsheet.
How we scope GIS/OMS/ADMS data validation
Most ADMS delays are data. A useful brief names Esri versus other GIS, the ADMS vendor, whether OMS and CIS extracts are in scope, and the go-live date. Electric tracing and phasing interviews are expected. Web GIS dashboards are not a substitute. We queue exceptions and re-test in non-prod. Live model activation stays with the utility.
Dallas growth metros, Duke territory, ComEd programs, Southern Company Atlanta, and California IOUs buy validation squads every model-load season. Pair validators with utility GIS engineers and ADMS/SCADA QA so exceptions have both a GIS owner and a test owner. We identify suitable profiles. Dedicated squads keep a U.S. domain lead through the season.
Validating an operational network model before go-live
Validation begins with source-to-target rules and acceptance thresholds. We inventory GIS classes, associations, connectivity, terminals, phases, voltage, equipment attributes, substation detail, feeder boundaries, service points, transformers, customers, switches, protective devices, and identifiers used by OMS, CIS, AMI, and ADMS. The team records which system owns each attribute and how deltas move. Counts are useful controls, but equal counts do not prove correct topology, phase, direction, or customer connectivity.
For ArcGIS Utility Network programs, checks may include network rules, containment and structural attachment, terminal configuration, subnetworks, topology errors, dirty areas, trace behavior, asset groups and types, and migration mappings from a geometric network or another source. Other GIS platforms require equivalent business-rule and connectivity validation. The ADMS target adds vendor-specific import rules and application expectations. We validate against the client’s approved model specification rather than assuming one universal electric schema.
A model-load cycle should be repeatable. We baseline source extracts, transformation code, reference tables, target build, and validation rules. Automated checks identify missing identifiers, invalid domains, duplicate assets, phase and voltage conflicts, disconnected features, loops, orphaned customers, improbable transformer relationships, and failed feeder traces. Sample-based visual review catches spatial and semantic problems automation may miss. Results become a defect queue with severity, source owner, target impact, evidence, disposition, and retest status.
Operational workflows provide the strongest acceptance cases. In non-production, we can test feeder tracing, device status interpretation, customer-to-transformer and device-to-customer relationships, outage prediction inputs, switching-plan prerequisites, model updates, and selected ADMS application dependencies using approved scenarios. We do not declare an as-operated model correct from migration statistics alone. Utility operations, GIS, OMS, planning, and ADMS owners review the workflows relevant to their responsibilities and authorize any production model activation.
Deliverables can include rule catalog, data profile, mapping review, automated validation results, trace suite, exception dashboard, aging report, root-cause categories, load-by-load reconciliation, acceptance summary, and handoff backlog. Buyers should ask how defects are prevented from returning, not only how quickly they are closed. Trend reporting by source process, feature type, feeder, and rule can identify upstream editing or integration problems. The goal is governed model quality that survives recurring deltas, not a one-time cleanup before cutover.
Specialist matching for validation talent
Project brief preferred. Name Esri versus other GIS, ADMS vendor, OMS, and go-live date. We identify suitable profiles. Live activation stays with the utility.
Needs GIS plus distribution operations vocabulary.
- Connectivity and phasing checks
- Transformer-customer and feeder-trace exceptions
- Model-load dry runs in non-prod
- Defect queues shared with GIS and ADMS engineers
FAQ
Frequently asked questions
Do you fix production GIS overnight before an ADMS go-live?
No. We profile data, define and run validation rules, triage exceptions, support approved remediation workflows, and retest extracts or model loads in non-production. The utility’s GIS editors and data owners control production changes, approvals, versioning, and activation. A rushed cutover is not permission for undocumented edits or for bypassing the owner’s quality process.
Do validators need electric tracing skill?
Yes for electric-utility scope. Validators must understand connectivity, terminals, phase, voltage, feeder and substation context, device states, transformer-service relationships, and the difference between geometric proximity and electrical connection. ArcGIS or another platform skill is necessary but insufficient. Interviews use realistic trace, phasing, import, and exception scenarios rather than generic web-map questions.
Is OMS data in scope as well as ADMS?
Yes when the brief includes outage devices, service points, customer-to-transformer relationships, CIS joins, predicted outage inputs, or model synchronization with OMS. We define ownership and reconciliation across GIS, OMS, CIS, AMI, and ADMS. OMS is not assumed from a GIS-only request because its identifiers, timing, model detail, and acceptance workflows may require separate stakeholders and test data.
How do we buy GIS/OMS/ADMS data validation?
Submit a project brief naming source GIS and version, target ADMS and OMS, migration or delta process, model size, known defect categories, next load, go-live milestone, environments, and required workflows. We identify suitable profiles when suitable names exist. A dedicated squad keeps a U.S. domain lead, owns the exception and retest cadence, and leaves production activation with the utility.
Can validation continue after the initial ADMS migration?
Yes. Recurring delta validation can check changed assets, topology, traces, customer relationships, transformation output, and target-load reconciliation before approved releases. Trend reports show which rules and source processes create repeat defects. The utility keeps ownership of production GIS edits, model publication, ADMS activation, and operational acceptance.
Staff gis/oms/adms data validation
ADMS/SCADA QA, integration, and specialized engineering talent, not a full-stack ADMS product shop.