Biomass and pellets

The platform sits above the controller

HVACloud connects controllers and evaluates what they deliver. Whether a compressor or a feed screw sits behind them changes nothing. The built in protocols are the same, Modbus TCP and RTU first among them, plus CAN and CANopen, the bus of many boiler and burner controls. The data point editor knows no heat generator type.

As things stand: talks with manufacturers are under way, no biomass plant is in operation yet. What follows is therefore stated as capability, not as a reference.

What you get from it

Telemetry and operation. State, consumption, run times and faults across the installed base, in one interface under your brand. Visualisation

Commissioning. In the factory in series with a final test, in the field guided on the panel, both on the same configuration. Factory and field commissioning

Alarms and service. Configure alarms yourself, roll them out to plant groups as a template and delegate the right to do so to service partners. On a boiler with a fuel store and ash removal, the service case is the normal case, not the exception. Alarm management

Your own apps. End customer app and panel HMI under your name, without a development team of your own. Own apps and HMIs

What falls away for you

Grid services. § 14a EnWG and the EAG affect controllable loads, that is electrical ones. A pellet boiler is not one. The chapter Grid services does not concern you, and we will not pretend otherwise.

What affects you just the same

The Cyber Resilience Act. It applies to every product with digital elements, regardless of fuel, and it explicitly includes the manufacturer cloud. From December 2027. Cyber Resilience Act