Legacy utility files contained conflicting meter serials, premise references and installation statuses. For the Meter and Service-Point Register Migration in Australia workload, reviewers spent additional time opening individual files because filenames and folder locations did not answer common retrieval questions.
A utility preparing legacy customer and metering data for a platform migration.
The primary client-side owner was the Metering Data Manager. That role coordinated source access, destination rules, reviewer availability and acceptance of each delivery. SDES would provide controlled production capacity; the client would retain authority over the business meaning of the records.
Problem: Legacy utility files contained conflicting meter serials, premise references and installation statuses. For the Meter and Service-Point Register Migration in Australia workload, reviewers spent additional time opening individual files because filenames and folder locations did not answer common retrieval questions.
Required solution: Records were mapped using approved account, service-point and meter identifiers; operational status conflicts stayed outside the load file. For Meter and Service-Point Register Migration in Australia, each index row retained its source filename or document reference, and unclear classifications were separated for records-owner review.
Planned outcome: The utility received a structured migration register and a focused identity and status review queue. After completing Meter and Service-Point Register Migration in Australia, internal reviewers could focus on genuine exceptions instead of rechecking every completed record.
The completed scope covered 58,700 meter, service-point and premise relationship records — completed in 9 weeks. Effort also reflected field count, document readability, relationship complexity, exception frequency and destination validation.
The client defines required fields, accepted formats, controlling sources and decisions that must be escalated. The operating guide records those boundaries before entry begins.
The review covered the stated volume of 58,700 meter, service-point and premise relationship records — completed in 9 weeks, including ordinary records, incomplete sources and difficult relationships.
The pilot uses Meter registers, service-point files, account extracts, installation sheets and status dictionaries. Questions are returned with exact record and source references so approved answers can enter the production guide.
Service-area pilot, area batches and final account-meter coverage review. Completed, held, excluded and rejected items remain distinguishable throughout production.
Serial uniqueness, service-point relationship, unit consistency, date order and source-status preservation receive focused checks. Unsupported assumptions do not enter the clean output merely to complete a record.
Batch totals, exception counts and source manifests are compared before final release. The handoff identifies what was delivered, held and returned for client direction.
The review focus would cover Serial uniqueness, service-point relationship, unit consistency, date order and source-status preservation. Sampling depth and second-pass review would be agreed according to field significance and source quality rather than advertised as an unsupported universal accuracy percentage.
Operators could prepare records but could not change live meter status, dispatch work or customer accounts.
Utility teams approved operational status, engineering interpretation, billing and field activity.
Metering Data Manager or another authorised owner would resolve exceptions that change meaning, identity, status, classification or commercial treatment. SDES would document the question and apply only the approved resolution.
The handoff would follow the destination structure and preserve enough source information for review and recovery. Delivery timing would follow Service-area pilot, area batches and final account-meter coverage review.
Migration table
meter-to-service relationship file
identity-conflict queue and batch reconciliation
The client would validate the pilot before scale and review each scheduled release. Rejections caused by entry error would be corrected against the approved guide. New rules, changed destination fields or newly supplied sources would be recorded as controlled changes so earlier batches were not silently processed under later assumptions.
The work on Meter and Service-Point Register Migration gave our team a dependable handoff. Confirmed records were ready for operational use, while uncertain items came back with clear source references. Our reviewers could focus on the decisions that required internal ownership instead of rechecking the full dataset. Very good value for money—we would confidently outsource this work to SDES again.
