Use Case — Education
Many buildings, one capital record
Districts and campuses manage large, varied building portfolios with constrained staff and public budget cycles. GRIDSTROM keeps projects, vendors, and assets consistent so each budget request is comparable to the last.
Operating Context
The environment this work happens in
- Many buildings of different age served by a small facilities team.
- Bond, grant, and general fund cycles with distinct rules.
- Bus electrification and campus load arriving in the same planning window.
- Board and community reporting on how funds were used.
The Fragmented-Data Problem
Where the record breaks today
- Building condition data held separately from energy scope.
- Grant documentation detached from the project it funded.
- Vendor service history rebuilt at each contract renewal.
- No consolidated inventory of installed energy equipment.
Financial Decision
Which buildings and programs receive funding, and how is the request supported?
Operational Workflow
How the work moves
- 01
Collect requests
Building needs enter as structured projects.
- 02
Compare
Scope and cost options are evaluated on the same inputs.
- 03
Approve and document
Board-ready packets carry their evidence.
- 04
Procure
Requests, quotes, and orders follow district process.
- 05
Operate
Assets carry warranty, vendor, and service history.
Representative Product Experience
District capital register — Weller Valley Schools (demonstration data)
Projects and assets across buildings, with funding source retained on the record.
| Record | Project | Building | Funding | Stage |
|---|---|---|---|---|
| PRJ-5201 | Bus depot charging | Transportation yard | Grant program | Approval routed |
| PRJ-5208 | Rooftop solar study | Weller High | Bond | Scenario review |
| PRJ-5214 | Service upgrade | Ridge Elementary | General fund | Quotes received |
| AST-5320 | Storage cabinet | Weller High | Installed | Operating |
Records shown are fictional demonstration data. Capabilities are released progressively.
Outputs by Role
What each role gets from the same record
Executive
- District-wide program status
- Board-ready summary of decisions
Finance / Planning
- Funding source tracked per project
- Approval and variance record
Operations
- Building asset register
- Vendor and service scheduling
Partner
- Structured request with access constraints
- Order tied to a defined scope
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.
- Student information and HR systems are out of scope; only facility and asset data are used.
- District financial systems remain the record for postings; projects carry cost references.
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. No student or personnel data is collected or stored.
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.
Request comparability
Share of projects using standard inputs and assumptions.
Funding traceability
Share of projects with source and eligible scope recorded.
Delivery windows
Work completed within scheduled break periods.
Inventory completeness
Share of installed equipment represented in the register.
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 · Partner