Skip to content
Project manager with tablet in front of a residential building, building data on the display
das.os
The Energy Operating System

An operating system for energy.

das.os connects generation, storage, consumers and billing into one system. Six modules control, display, evaluate and bill every energy flow in the building.

Orchestration · Monitoring · Analytics · Billing
Principle

Four layers, four tasks.

Each layer of das.os has exactly one task. Together they form a closed loop: act, see, evaluate, bill.

Orchestration controlsMonitoring displaysAnalytics evaluatesBilling bills
01Orchestration

controls

Acts and optimises. Detects a looming peak load and dispatches battery storage, charging infrastructure or consumers against it.

02Monitoring

displays

Shows what is happening: current load, grid supply, storage output, peak values and status messages like “Peak shaving active”.

03Analytics

evaluates

Evaluates in retrospect: avoided peaks, reduced peak load in kW and the resulting savings in euros.

04Billing

bills

Settles the accounts: tariffs, meter readings, electricity costs and – where needed – cost centres and tenant electricity.

Peak shaving

One peak load. Four layers.

Peak shaving is the best way to see how the layers interlock. The same peak load passes through all four – from control to invoice.

Orchestration

The system steers against it

This is where peak shaving actually happens: das.os detects a looming peak load and dispatches battery storage, charging infrastructure or consumers against it.

actsand optimises

Monitoring

You watch it happen

Current load, grid supply, storage output and peak values in real time – including the status message “Peak shaving active”.

displayswhat is happening

Analytics

Then the numbers are run

How many peaks were avoided? How many kW of peak load were reduced? How many euros were saved? Analytics answers this in retrospect.

evaluatesin hindsight

Billing

And it lands on the invoice

Tariffs, meter readings and electricity costs flow into the billing – separated by cost centre or as tenant electricity if required.

billstariffs & readings
Modules

Six modules. One system.

das.os is modular. Each module covers its own area – from controlling the energy flows to connecting individual devices.

das.os.orchestration

Intelligent control of all energy flows.

The acting layer. Orchestration recognises situations in the energy system and intervenes before they cost money.

  • Peak shaving
  • Self-consumption optimisation
  • Storage control
  • PV surplus
  • Charging optimisation
  • Dynamic grid supply
Orchestration

Six functions, one layer.

Peak shaving, self-consumption optimisation, storage control, PV surplus, charging optimisation and dynamic grid supply are all functions of Orchestration.

Technical control centre with a row of inverters and storage cabinet
das.os.orchestration

acts

and optimises

01

Peak shaving

A looming peak load is detected and intercepted with storage, charging infrastructure or consumers.

02

Self-consumption optimisation

Self-generated energy is used where it has the highest value in the building.

03

Storage control

Charging and discharging the battery follow the situation in the grid and in the building.

04

PV surplus

Surplus solar power is used deliberately instead of flowing into the grid uncontrolled.

05

Charging optimisation

Charging sessions are distributed so they don't push the peak load any higher.

06

Dynamic grid supply

Supply from the grid follows tariff and situation – not chance.

Two people in front of an evaluation view with peak comparison
das.os.analytics

evaluates

in retrospect

0 modulesin one system
0 layerscontrol, display, evaluate, bill
0 functionsin Orchestration alone
0 platformfor the entire building
Evaluation

Three questions. Verifiable answers.

What Orchestration does in operation, Analytics makes traceable in retrospect – for every billing period.

01

How many peaks were avoided?

Every intercepted peak load is counted and attributed to the intervention that prevented it.

02

How many kW of peak load were reduced?

The difference between uncontrolled and controlled peak load is reported in kilowatts.

03

How many euros were saved?

Reduced peak load and the stored tariff produce the amount that is missing from the bill.

Connect

Without data, nobody controls anything.

das.os.connect connects meters, plants and third-party systems. Only this connection makes Monitoring, Analytics and Billing possible.

Control cabinet with data logger and smart meter
das.os.connect
01

Interfaces

Connection of existing plants and third-party systems in the building.

02

Smart meters

Meter readings as the basis for monitoring, analytics and billing.

03

Devices

Storage, inverters, charging points and consumers become addressable.

04

APIs

Open programming interfaces for data exchange in both directions.

Enquiry

We'll show you das.os on your building.

Tell us about your building and existing systems – you'll receive an assessment of which modules make sense and what they can control.

  • Response within 24 hours
  • Modules individually or as a complete system
  • Connection of existing plants via das.os.connect
das.os enquiry00 / 07 required fields
Reply within 24 hours.
Fragen

What you should know about modules, control and data.

The Energy Operating System by das.kraftwerk. It consists of six modules: Orchestration, Monitoring, Analytics, Billing, Care and Connect. Together they control, monitor, evaluate and bill all energy flows of a building.

Orchestration acts and optimises – this is where peak shaving actually happens, by controlling storage, charging infrastructure or consumers. Monitoring shows what is happening: current load, grid supply, storage output, peak values and messages like “Peak shaving active”.

In Orchestration. das.os detects a looming peak load and steers against it. Monitoring shows the process in real time, Analytics evaluates it in retrospect, Billing brings the result into the invoice.

Peak shaving, self-consumption optimisation, storage control, PV surplus, charging optimisation and dynamic grid supply.

Analytics answers three questions in retrospect: How many peaks were avoided? How many kW of peak load were reduced? How many euros were saved? Plus performance data, forecasts and KPIs.

Yes. das.os.billing settles tariffs, meter readings and electricity costs – separated by cost centre or as tenant electricity if required.

Via das.os.connect: interfaces to existing plants, smart meters, connected devices and open APIs.

Your contact at das.kraftwerk

Personal consultation

We show you das.os on your building.