These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Smart Meter Data Platform
- Features
- Service Case Coordination
Service Case Coordination
Keep reported scope, external incident identity and accountable ownership connected to the meter-data work.
OverviewRestoration Review Queue×
Smart Meter Data Platform · Service Case Coordination
New
Restoration Review Queue
Service cases
| Record number | Subject | Reported at | Affected units | Asset reference | External incident ID | |
|---|---|---|---|---|---|---|
| SC-17634 | Review sc-962 | 11 Oct | 860 | AR-236 | EII-863 | |
| SC-64474 | Review sc-227 | 10 Oct | 50 | AR-438 | EII-407 | |
| SC-67221 | Review sc-456 | 03 Oct | 190 | AR-864 | EII-430 | |
| SC-14562 | Review sc-261 | 24 Oct | 420 | AR-891 | EII-938 | |
| SC-86574 | Review sc-713 | 27 Oct | 450 | AR-914 | EII-770 |
6 of 6 records
Review sc-962Service cases · SC-17634
Reported at11 Oct
Affected units860
Asset referenceAR-236
External incident IDEII-863
Revision680
What you can do
Give the reading an operating context
A service case records the reported time, affected scope and external incident identity within an organization and service area. Its subject and record number make the work recognizable to the team. Utility Coordinator uses the case to organize the relevant interval readings, source evidence and attachments, while the owner remains accountable for the operational handoff.
The case lifecycle follows Reported, Triaged, Assigned and Review before a supported restoration and closure. Those stages describe the operational work surrounding the meter data. An interval can have its own review and acceptance result under that case. Keep the separate states clear so a completed reading does not make an unresolved case disappear from the team’s discussion.
How the work is organized
- Actual reported scope. Record when the incident was reported and the affected units known to the team. Retain the external incident identity and relevant asset reference. Check that the organization and service area describe the intended operating scope before the case is routed.
- Authorized ownership. Triage verifies the external incident identity and assigns an authorized responder. The case owner gives the team a person to follow for the next action. Keep membership and organization scope aligned with the work the person is allowed to prepare.
- Evidence handoff. Bring source-identified observations and supporting files into the review context. The supervisor needs the current revision and the intended subject, whether the decision concerns operational evidence, restoration or an interval under the case. Retain the operation identity with the resulting evidence.
What to agree during setup
Agree what affected units means for your service operation and how the value is established. Decide which external system owns the incident identity and how the coordinator checks it. Keep the source reference available when a duplicate or ambiguous case needs investigation. Avoid assuming that affected scope is unique across separate cases when reviewing area totals.
Confirm the organization and service-area ownership rules, the people eligible to receive work and the information needed for the review handoff. Resolve the signed-in user’s team membership before relying on a personal case view. Define how the team handles changed scope so the supervisor reviews current evidence rather than an earlier version of the incident.
Check the handoff on an actual case
Use an illustrative service incident with an external reference and a known affected scope. Utility Coordinator records the actual reported time, checks the intended service area and opens the case as Reported. Triage verifies the external identity and assigns the work. The coordinator then gathers the interval and source context needed for independent review.
Repeat the handoff after the affected scope changes. Present the current revision and make the difference visible to Authorized Utility Supervisor before a guarded action proceeds. Then inspect a completed interval under a case that still lacks restoration evidence. Its acceptance should remain traceable while the case stays in its appropriate operational state. The owner must still be able to explain the next response.
What your team sees
- Service Cases — Open operational work with reported scope, service area and accountable owner.
- My Service Cases — Cases assigned to the staff member associated with the signed-in user.
- Service Case Board — Reported through review-stage work for discussing the next response.
Follow the work through
Use case intake and evidence review, then follow restoration and closure when field confirmation is available.
What it keeps track of
Data model- Service cases
- Operational service cases with lifecycle, affected scope and restoration.
- Service areas
- Eligible service areas and counterparties within an organization.
- Organizations
- Utility organizations operating the smart meter data platform.
- Team members
- Utility staff with platform identity, role and time zone.
- Service evidence
- Source-identified evidence lines supporting a service case.
- Interval readings
- Verified meter interval readings submitted for acceptance.
- Operation receipts
- Stable operation keys and persisted results for guarded actions.
Who uses it
Permissions- Utility Coordinator
- Prepares assigned case work.
- Authorized Utility Supervisor
- Reviews eligible evidence and actions.
- App Administrator
- Maintains membership and service-area context.
- Auditor
- Inspects authorized history.
Set up Smart Meter Data Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.