Skip to content
HVACloud

Appearance

Language

Four parts, one path

Controller, edge client, cloud, people. Configuration comes from the cloud, the client buffers locally and keeps running when the line drops.

  • Under a minute from the plant into the cloud
  • Keeps running offline the client buffers and sends on
  • Android and Linux as client platforms
The path the data takes
  1. Controller The plant, whoever made the controller.
  2. Edge client Touch panel or gateway. Reads, buffers, serves on site.
  3. Your instance History, dashboards, alarms, administration.
  4. People Your teams, your partners, your end customers.

Configuration comes from the cloud

The path the data takes

It starts at the plant controller, whoever made it. An edge client reads it. That is either a touch panel, which doubles as the local interface, or a gateway without a display where the plant needs no visualisation.

The edge client sends to your instance in the cloud. History, dashboards, alarms and administration live there. Your teams, your system partners and your end customers reach it from there, each seeing only what they are entitled to.

Client dumb, server smart

The edge client holds no truth of its own. What it should do, which data points it reads, how the interface looks: all of that comes from the cloud. Two consequences matter in the field.

First, swapping a device is uneventful. A new panel registers, pulls its configuration and carries on. There is no local state anyone had to back up first.

Second, a change can go out to many plants at once, because it lives in one place and not on a thousand devices.

What happens when the line drops

The plant keeps running. The controller controls on its own anyway, it needs no cloud for that. The edge client records locally in the meantime and sends on once the connection returns. No gap appears in the history.

Operation at the panel stays available too. The local HMI works without restriction against the web interface, not as a fallback mode.

This is what it looks like

What the controller delivers

Every data point with type, unit and live value, ordered by the device schema. That is the basis for everything else.

The data point view: the controller tree with outside temperature, blocks, heating and cooling curves, each with type, unit and current value.

Better shown than read

We will show you this area on a real plant, set up around the equipment you build.

Request a demo