Layer 03/ data
One screen.
Electricity and heat.
ergOS is the operating layer. It sits on every meter, every source and every heat pump — watching price, weather, storage and the production plan, and acting every fifteen minutes.
The problem/ as plants actually meet it
Electricity, heat and production are usually run from different systems on different clocks, and reconciled monthly from invoices. By then the decisions that mattered — which block to import in, when to run the heat pump, whether to bank or sell — have already been made by default.
How it works/ in delivery order
What we
actually do.
Electricity, steam, thermal energy, fuel flow and water, every fifteen minutes, from the source and the load rather than from the invoice.
Generation, load and price across the coming blocks, so scheduling is a decision rather than a reaction.
Day-ahead, green day-ahead, real-time and term markets; banking and surplus positions managed against the forecast.
Heat pumps and thermal storage run against price and the production plan — the mechanism that puts heat in the cheapest, greenest blocks.
Boundaries/ where this stops
What it
does not do.
Advisory and supported control
What ergOS controls directly, what it recommends, and what remains with plant operations is agreed per site. We describe control separately from monitoring rather than blurring the two.
It needs data to exist
Where meters are absent, they get installed. Where a system already holds the data, we integrate. Estimates are labelled as estimates and are a stopgap, not a design.
Screens shown are illustrative
Interfaces on this site and in our decks are illustrative unless captioned otherwise. Live capability is confirmed per deployment.
What we need/ to start
- Meter points and communication access
- Existing SCADA, EMS or historian, where present
- Production plan or shift pattern
- Contracted supply positions and banking terms
What drives the economics/ the real levers
- Blocks imported at tariff versus scheduled
- Heat pump and storage dispatch against block price
- Demand charge exposure
- Banking and surplus outcomes
Questions/ asked most often
Does it control our plant?
What if we already have an EMS?
In short/ ergOS
ergOS is jouleWise's data solution: metering, forecasting, scheduling and dispatch across electricity and heat.
ergOS is the operating layer. It sits on every meter, every source and every heat pump — watching price, weather, storage and the production plan, and acting every fifteen minutes. Electricity, heat and production are usually run from different systems on different clocks, and reconciled monthly from invoices. By then the decisions that mattered — which block to import in, when to run the heat pump, whether to bank or sell — have already been made by default.
What to take away
- Meter: Electricity, steam, thermal energy, fuel flow and water, every fifteen minutes, from the source and the load rather than from the invoice.
- Forecast: Generation, load and price across the coming blocks, so scheduling is a decision rather than a reaction.
- Schedule and trade: Day-ahead, green day-ahead, real-time and term markets; banking and surplus positions managed against the forecast.
- Dispatch heat: Heat pumps and thermal storage run against price and the production plan — the mechanism that puts heat in the cheapest, greenest blocks.
What it assumes
- Advisory and supported control. What ergOS controls directly, what it recommends, and what remains with plant operations is agreed per site. We describe control separately from monitoring rather than blurring the two.
- It needs data to exist. Where meters are absent, they get installed. Where a system already holds the data, we integrate. Estimates are labelled as estimates and are a stopgap, not a design.
- Screens shown are illustrative. Interfaces on this site and in our decks are illustrative unless captioned otherwise. Live capability is confirmed per deployment.