Skip to content

Asset Operations & Service

From Asset Exception to Coordinated Service Recovery

An exception on a monitored asset becomes a diagnosed work order, a technician visit with evidence, and a verified return to service.

Problem

An underperforming charger or inverter surfaces in a vendor portal, gets discussed in a group chat, and is resolved without a durable record of what failed or what fixed it.

GRIDSTROM response

GRIDSTROM raises the exception against the canonical asset record, attaches recent telemetry and history, quantifies the operational and financial exposure, and opens a work order with the diagnosis carried forward.

Decision / outcome

A closed work order with technician evidence, parts used, and a verified performance recovery recorded against the same asset for the rest of its life.

How it runs

Four steps on one record

  1. 01

    Detect

    An exception is raised against the canonical asset record.

  2. 02

    Diagnose

    Telemetry, service history, and probable cause in one view.

  3. 03

    Act

    A work order is dispatched with the diagnosis and checklist attached.

  4. 04

    Verify

    Post-service performance is compared against the pre-fault baseline.

Product Experience

What the screen shows

Demonstration data. Exception queue for a fictional charging portfolio.
AssetExceptionExposureState
DCFC-04 · North LotSession failure rate 18%Est. 42 sessions/wkDiagnosed
DCFC-04 · North LotWork order WO-1182Technician assignedDispatched
DCFC-04 · North LotContactor replacedEvidence attachedCompleted
DCFC-04 · North LotFailure rate 1.2%7-day verify windowVerified

Illustrative product workflows use sample data to demonstrate the GRIDSTROM product experience. Actual configurations and available capabilities depend on deployment scope, data sources, integrations, and authorized access.

The Reasoning Loop

One connected record, end to end

  1. Data

    Telemetry, service history, warranty terms, and site context resolve to one persistent asset record.

  2. Detect

    An exception or performance variance is raised against that asset.

  3. Diagnose

    Recent behavior and history are assembled into a probable cause with a 'show me why' explanation.

  4. Value

    Operational and financial consequences of the exception are quantified before spend is authorized.

  5. Decide

    Repair options, coverage, and the approval required to proceed are presented together.

  6. Act

    An authorized work order is dispatched with the diagnosis, checklist, and parts context attached.

  7. Verify

    Post-service performance is compared against the pre-fault baseline and documented on the record.

  8. Learn

    Cause, remedy, and outcome remain on the asset for future service and lifecycle decisions.

Who it serves

Operations

One queue for exceptions across vendors and sites.

Technician

Mobile detail, checklist, and evidence capture.

Finance & Planning

Exposure quantified before the spend is approved.

Related Capabilities

  • Exception detection
  • Work coordination
  • Evidence capture
  • Verification

Next Step

Take this workflow to your portfolio