Simple to run._ Built from proven parts.Simple to run._ Built from proven parts.

RADA works with separate building blocks, each doing one job well. Your on-site assets report to OpenEMS. One or more OpenEMS installations pass the readings to RADA. RADA stores them, makes sense of them, and presents the data on your dashboard.

Fig. 3 — Sites → OpenEMS → RADA → your teamFig. 3 — Tap a box for details

Solar, battery and mixed sites each run an OpenEMS Edge. The solar and battery sites send their readings to OpenEMS Backend A, the mixed site to OpenEMS Backend B. Both backends send to the OpenEMS Bridge, which passes the readings to the RADA Back. The Back is linked to the Front and the Database. The Front serves your team in the browser; the Back exports daily and monthly data to finance and ERP systems. A plain-language AI assistant is optional.

Your sites

OpenEMS

One or many OpenEMS installations+ more

RADA · four containers

Optional: plain-language AI assistant

Your team

On your sites: OpenEMS Edge

Every site has an OpenEMS Edge: a small physical device installed on site, connected to your equipment over the site’s local network. It talks directly to inverters, batteries and meters, whatever the brand. It reads values such as power produced, battery charge level and energy used, and sends them on securely.

OpenEMS is a mature open-source energy management system, developed and maintained by an active community of manufacturers and energy companies.

The collection point: OpenEMS Backend and Felix

Each group of Edges reports to a central OpenEMS Backend. Think of it as the post office: readings from every site arrive here and are passed on.

OpenEMS is configured through Felix, a settings panel where an administrator switches components on and off and tells each Edge which equipment it is connected to. Felix is kept private, behind a secure connection, and is only used by the system administrator.

One view across many OpenEMS installations

Many organisations end up with more than one OpenEMS installation. A maintenance firm may run one per client. A retailer, a housing association or a council may have one per region, or inherit one when it takes over a site. RADA connects to all of them at the same time and combines their readings into one dashboard. Each installation keeps running as it is; RADA simply brings the picture together.

RADA: four containers

RADA itself comes as four containers. A container is a self-contained package of software that runs the same way on any server, so installing RADA means starting four packages rather than configuring a complex system by hand.

  1. The Front (web application).

    What your team sees in their browser: the dashboard, site and asset pages, exports and the plain-language assistant. Available in English, French, and German.

  2. The Back (API).

    The engine room. It receives readings from the Bridge, combines them, checks who is allowed to see what, does all the calculations, and serves the results to the Front and to other systems such as your accounting software.

  3. The Database (PostgreSQL with TimescaleDB).

    The archive. It stores every reading with its time stamp, built on PostgreSQL – one of the most widely used databases in the world – with an extension designed for measurements over time.

  4. The OpenEMS Bridge.

    The link between OpenEMS and RADA. It connects to each of your OpenEMS Backends, collects their readings and passes them to the Back.

Because the four are separate, you can fit RADA to the infrastructure you already have. Use an existing database server, or host the web application wherever suits you.

The software computes, the AI narrates.The software computes, the AI narrates.

RADA can connect to an AI language model that answers questions in plain language, such as “Which site produced the most last week?” Our rule is simple: the software computes, the AI narrates. Every figure is calculated by RADA from your data. The AI only puts the answer into words. The assistant is optional, for organisations that have the hardware to run it.

Security in brief

  • Every user signs in with an email and password, as an administrator or a viewer.
  • Other systems connect with individual secure keys.
  • All traffic is encrypted, and you host everything yourself.