▸

Data model

Make every part of the portfolio speak the same language.

Talk to us

A portfolio is more than assets. Customers, contracts, tariffs, telemetry, flexibility, and markets all need to connect in the same operational structure.

‍

The Fever data model creates that shared foundation, so every team can work from the same operational reality.

A

For your team

Operations teams

See assets, customers, contracts, tariffs, telemetry, and participation through one operational structure.
‍

Commercial teams

Connect services, contracts, participation, and customer relationships without maintaining parallel data models.
‍

Tech teams

Build systems on a shared operational foundation instead of stitching together disconnected datasets.

B

What it enables

One portfolio. One operational language.

Assets, sites, customers, contracts, tariffs, telemetry, and markets shouldn't live in separate versions of reality.

The data model captures how they relate: a battery belongs to a site, a site to a customer, a customer to a contract that defines participation, tariffs, and markets.

So forecasting, optimization, dispatch, billing, and support all work from the same context, and stay aligned as the portfolio grows.

C

Why it matters

The value is in the relationships.

A battery belongs to a site.
A site belongs to a customer.
A customer has a contract.
A contract defines participation, tariffs, and markets.

‍

The data model keeps those relationships structured so forecasting, optimization, dispatch, billing, support, and reporting all operate from the same operational context.

C

How it's built

Fever
Platform
Core
Data model

‍

  • Shared operational data model across Core, Modules, and Interfaces
  • Structured entities for assets, sites, customers, contracts, tariffs, markets, and portfolios
  • Relationship model connecting assets, sites, meters, customers, products, and market participation
  • Operational state model for telemetry, connectivity, onboarding, diagnostics, health, and flexibility
  • Support for mixed asset types, vendors, protocols, and connectivity models
  • Portfolio, site, customer, and asset-level operational structures
  • Customer and participation data linked to operational workflows
  • Tariff, contract, and market data linked to optimization and trading workflows
  • Shared data foundation for Insight, Predict, Optimize, Trade, Console, View, Charge, and Field
  • Designed for controlled scaling across regions, markets, products, and operational teams

D

Our approach

Tech works better in the background.

At Fever, we’re building the technology needed to make distributed energy work at scale.

But performance alone does not create adoption.

Distributed energy has to work across operations, installers, support, commercial teams, and contributors.

That is why we design for how distributed energy actually works in practice. Across all the people, systems, and operational realities involved.

Your brand in front. Fever in the background.

Next in Platform

Core

/

Integrations

Make every system work together.

ϟ .‿. Making distributed energy work.

©Fever Energy AB 2026. Stockholm, Europe.

All rights reserved. Privacy Policy