Managed Support

Connect device issues with a clear support process.

Monitoring is only useful if someone acts on it. We are developing a managed support service that turns device events into tracked incidents — assessed, diagnosed, resolved and reported against agreed service levels.

A technician in a hard hat and hi-vis vest testing an electrical meter cabinet at a rural site
Illustrative image

What the service covers

  • Device monitoring

    Initial focus · in development

    Watching supported meters and devices for communication loss and, where devices report them, fault events and abnormal readings.

  • Incident management

    Initial focus · in development

    Every issue raised as an incident with a priority, an owner and a status, so nothing relies on memory or a chat thread.

  • Remote diagnostics

    Integration dependent

    Investigating a fault remotely where the device and its communication link technically support it — reducing unnecessary site visits.

  • Field-service coordination

    Planned

    Arranging approved field partners when a site visit is needed, and tracking the visit through to resolution. Field-partner arrangements are agreed per engagement.

  • SLA reporting

    Planned

    Regular reports on incidents against the service levels agreed with you, showing response and resolution times separately.

The intended workflow

  1. Detect

    A supported event is detected — for example, a meter stops communicating — or a customer reports a problem.

  2. Assess

    We check the event against recent data to judge its likely cause and priority.

  3. Raise and assign

    An incident is raised and assigned to the right person, with its priority and context attached.

  4. Diagnose remotely

    Where the device supports it, we investigate remotely before anyone travels.

  5. Coordinate field work

    If a visit is needed, we coordinate an approved field partner and share what we know.

  6. Resolve and report

    We track the incident to resolution and report it against the agreed service levels.

Illustrative incident history and SLA report

Fictional incidents and example targets showing how reporting could look.

Illustrative incident history Demonstration data
Sample incident history (demonstration data)
ReferenceEventPriorityResponse timeResolution timePathStatus
DEMO-INC-0101Meter not communicatingMedium25 min1 day 3 hRemote diagnosis, then field visitResolved
DEMO-INC-0102Low voltage reported at feederHigh12 min3 h 40 minField partner dispatchedResolved
DEMO-INC-0104Inverter fault codeHigh18 min55 minRemote diagnosis and resetResolved
DEMO-INC-0106Customer reports no displayLow1 h 10 min—Awaiting field visitOpen

Response time runs from an incident being raised to it being acknowledged and assigned. Resolution time runs until the issue is fixed and confirmed.

Illustrative SLA report Demonstration data
Sample SLA report (demonstration data)
MeasureExample targetSample period
Response time — high priorityWithin 30 min2 of 2 within target
Response time — medium/lowWithin 2 h2 of 2 within target
Resolution time — high priorityWithin 8 h2 of 2 within target
Resolution time — medium/lowWithin 3 days1 resolved within target, 1 open

Example targets only. Real service levels, coverage hours and regions are agreed per engagement.

Agreed per engagement

Support is scoped to each customer. Before any engagement we agree:

  • coverage hours
  • response and resolution targets by priority
  • supported regions and sites
  • field-partner arrangements and responsibilities
  • which devices and events are monitored

We do not currently offer nationwide or 24/7 coverage. We will only commit to service levels we have the capacity to meet.

Tell us what support you need

Describe your sites, devices and current support arrangements, and we will explain what we could take on.

Discuss a pilot Contact