A house with a pool house and garage. A school with a gym. A business with an office, a hall and a warehouse.
Every building contains technology: heating, lighting, shading, ventilation, meters. The question is: Who controls all of this - and what happens if that device fails?
With a distributed project every building has its own controller. Even so, the whole site is planned, maintained and operated as one single installation.
A central controller runs every building.
Drawback: If it fails, the whole site stops - including the
heating in the outbuilding, even though everything there is fine. On top
of that come long cable runs to every building.
Every building gets its own controller with its own project.
Drawback: Maintenance several times over, every change in several
places, values have to be exchanged one by one, and in the app each
installation stands on its own.
All musicians have the same score - but each one only plays their own part. Together it becomes one piece of music.
A distributed project works the same way: all controllers know the same project. But each one only runs the parts assigned to it - for example “Heating outbuilding” on the controller in the outbuilding.
If one musician is missing, the others keep playing.
Every controller handles its own tasks independently. If one fails, the others carry on undisturbed.
Only the functions of the failed controller are missing - not the whole installation.
The app connects to any controller - and still shows everything: every building, every room, every value.
Residents or caretakers do not need to know which device is responsible for what. They simply operate their installation.
It remains one single project. It is transferred to one controller, which passes it on to all the others by itself.
If a controller was not reachable at the time, it notices on the next connection and fetches the new version by itself. The Studio shows at any time whether all controllers are up to date.
Switching times, setpoints or the presence simulation are changed in the app - no matter which controller it is connected to.
The change arrives where it is needed and is then stored on every controller. A controller that was briefly offline catches up with the newer state on the next connection.
Every 10 seconds each controller sends a sign of life. If it is missing for one minute, the failure is reported automatically - by e-mail or push message to the phone.
A short restart does not trigger a false alarm. Nothing needs to be configured - monitoring is always included.
Each controller connects the technology of its own building directly: electrical installation, heating, meters, inverters.
This saves long cables between the buildings. The normal network is enough between the controllers - and if the connection ever drops, each building keeps working on its own.
An existing project keeps running unchanged. When a building is added, a controller is added and parts are moved over one at a time - without a cut-over date and without replanning.
A device replacement stays simple too: the new device receives the number of the old one and is back in the network.
Pool house, garage or guest house get their own controller - everything is operated in one app.
Every house controls itself. Property management sees the whole site in one place.
Main building, gym, extension: if one building fails, the others stay warm and lit.
Office, hall, warehouse, stable - spread across the site, linked over the network.
Distribution prevents a total failure. But if one controller fails, its own tasks are still missing.
A backup controller closes exactly this gap: it stands next to the most important controller, runs along quietly and takes over automatically if it fails.
The distributed project ensures that every building keeps running on its own.
The backup controller ensures that the tasks of the main controller keep running too.
The backup controller calculates and records along in standby - after a takeover all data is available immediately.
Only one controller per number acts on the outside world. No command is executed twice.
Every controller keeps working independently.
Connected to one controller, in control of the whole site.
Transfer once, all are brought up to date.
Switching times and setpoints apply everywhere.
Failures are reported automatically.
Existing projects keep running, expansion step by step.