Skip to content

Use Case — Distributed Energy Portfolios

Many sites, many vendors, one connected portfolio record

Distributed portfolios accumulate sites, manufacturers, contracts, and monitoring tools over time. GRIDSTROM holds the asset, project, vendor, and service record in one structure so the portfolio can be managed as a portfolio.

Operating Context

The environment this work happens in

  • Solar, storage, generation, and charging assets acquired in different periods.
  • Multiple O&M contracts with varying scope and reporting formats.
  • Performance and availability obligations across owners and offtakers.
  • Lifecycle events — repowering, replacement, disposal — arriving continuously.

The Fragmented-Data Problem

Where the record breaks today

  • One monitoring portal per manufacturer, none comparable.
  • Contract terms held in documents rather than against the asset.
  • Service history fragmented by O&M provider.
  • Portfolio reporting rebuilt manually each period.

Financial Decision

Where does the next dollar of capital or service spend do the most for the portfolio?

Asset performance and degradation against expectation.
Service cost by site and provider.
Replacement and repowering horizon by installed date.
Contract obligations and remaining warranty coverage.

Operational Workflow

How the work moves

  1. 01

    Consolidate

    Sites and equipment become canonical asset records.

  2. 02

    Compare

    Performance and cost are viewed on consistent measures.

  3. 03

    Decide

    Capital and service scenarios are recorded with assumptions.

  4. 04

    Execute

    Requests, quotes, and orders route to qualified providers.

  5. 05

    Verify

    Completion evidence returns to the asset record.

Representative Product Experience

Portfolio register — Cedar Works Energy Holdings (demonstration data)

Sites and assets with performance state, service provider, and lifecycle position.

Portfolio register — Cedar Works Energy Holdings (demonstration data)
RecordSiteAssetsStateLifecycle position
SIT-7101Ridgeway SolarInverters, metersOperatingMid-life
SIT-7108Bexley StorageBattery, PCSWatchService review
SIT-7115Talbot DepotChargingExceptionWork order open
SIT-7122Wren FieldGenerationOperatingReplacement study

Records shown are fictional demonstration data. Capabilities are released progressively.

AssetProjectVendorRequestQuoteOrderWork order

Outputs by Role

What each role gets from the same record

Executive

  • Portfolio state and lifecycle outlook
  • Capital and service spend direction

Finance / Planning

  • Scenario comparison across sites
  • Recorded assumptions and approvals

Operations

  • Cross-vendor exception queue
  • Service provider performance

Technician

  • Site and equipment history at dispatch
  • Evidence capture on completion

Partner

  • Scoped requests across sites
  • Orders and completion tied to assets

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.
  • Manufacturer monitoring portals and data exports are normalized into the canonical asset record.
  • Asset management and accounting platforms remain systems of record for ownership and financial postings.

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.

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.

Portfolio visibility

Share of sites represented by complete asset records.

Comparability

Share of assets reporting on consistent measures.

Service efficiency

Cost and timing of service activity by provider.

Lifecycle readiness

Share of assets with a recorded replacement horizon.

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