Use Case — Fleets & EV Charging
Depot planning and charger uptime on the same record
Charging programs fail on operations more often than on capital. GRIDSTROM keeps the depot project, installed chargers, service history, and vendor performance connected from first decision to daily operation.
Operating Context
The environment this work happens in
- Duty cycles and dwell windows that determine required charging capacity.
- Phased depot buildout tied to vehicle delivery schedules.
- Multiple charger manufacturers and network providers across sites.
- Uptime directly affecting whether vehicles complete their routes.
The Fragmented-Data Problem
Where the record breaks today
- Charger status split across manufacturer portals per site.
- Utility and construction cost recorded outside the charging plan.
- Service dispatch handled by phone, with no shared history.
- Vendor performance judged by impression rather than record.
Financial Decision
What charging capacity is installed, in which phase, and at what operating cost?
Operational Workflow
How the work moves
- 01
Plan the depot
Duty cycle and dwell define required capacity and phasing.
- 02
Approve the phase
Scenarios and assumptions travel with the approval.
- 03
Onboard equipment
Manufacturer, model, and protocol map to canonical asset records.
- 04
Operate
Exceptions raise work orders with diagnosis context.
- 05
Verify and learn
Recovery is verified and vendor performance is retained.
Representative Product Experience
Depot operations — Northline Logistics, Harbor Point Depot (demonstration data)
Charging assets with live state, assigned work orders, and vendor accountability.
| Record | Asset | Bay | State | Action |
|---|---|---|---|---|
| AST-3301 | DC charger 01 | Bay 1 | Operating | None |
| AST-3305 | DC charger 05 | Bay 5 | Degraded output | WO-8811 dispatched |
| AST-3309 | DC charger 09 | Bay 9 | Offline | Quote requested |
| PRJ-3402 | Phase 2 expansion | Bays 13–20 | Approved | Order issued |
Records shown are fictional demonstration data. Capabilities are released progressively.
Outputs by Role
What each role gets from the same record
Executive
- Network availability across depots
- Phase status against vehicle delivery
Finance / Planning
- Phase scenarios with recorded assumptions
- Operating cost inputs retained with the decision
Operations
- Live exception queue by depot
- Vendor response and recurrence tracking
Technician
- Incident detail with prior faults and parts
- Checklist and verified recovery capture
Partner
- Service request with diagnosis context
- Quote and order tied to the asset
Integration Approach
Connect what is already in place
- Vendor-neutral intake: existing spreadsheets, ERP exports, monitoring portals, and equipment telemetry are read into a canonical asset record.
- GRIDSTROM is not the general ledger. ERP and accounting platforms remain systems of record for financial postings.
- Charging network and OCPP-capable equipment contribute telemetry to the canonical asset record where an interface is available.
- Telematics and fleet systems remain in place; GRIDSTROM references vehicles rather than replacing fleet management.
Security & Governance
How access and evidence are handled
Role-based access, least-privilege permissions, and an append-only history for approvals and status changes. Documents and evidence are stored privately, and access is scoped to the organization, project, and role that requires it. Driver and vehicle operator personal data are out of scope.
Measurement
What success could be measured
Metric categories only. Results depend on the organization, its data, and how the work is adopted; no outcome is promised.
Availability
Share of charging assets in an operating state during required windows.
Time to recovery
Detection to verified recovery for each exception.
Recurrence
Repeat faults on the same asset within a defined period.
Vendor responsiveness
Response and closure timing by vendor.
Related Use Cases
Adjacent operating environments
Next Step
Discuss your use case
Bring the sites, systems, and decisions you are working with. We will walk through how the record would be structured.
Roles served: Executive · Finance / Planning · Operations · Technician · Partner