--- title: "Vendor-neutral building automation — logiccloud" description: "Control ventilation, lighting and energy vendor-neutrally and keep every site up to date from one place – from a single building to the whole portfolio." url: https://logiccloud.com/en/solutions/building-automation/ language: en-GB --- Software-defined building automation Vendor-neutral building automation.\ Kept current centrally. ======================= For operators of many buildings — property portfolios, branch networks, production and office sites. One end-to-end software platform instead of systems that have grown piece by piece — from a single controller to hundreds of buildings. [Request a demo](https://logiccloud.com/en/demo/) [Discuss the use case](https://logiccloud.com/en/contact/) logiccloud ORCHESTRATE · properties live Ventilation control 2.4 · rollout Site System Version Status Branch Cologne Ventilation 2.3 2.4 running updated Branch Mainz Ventilation 2.3 2.4 waiting updated Campus South Ventilation 2.3 2.4 waiting updated Branch Ulm Ventilation 2.3 2.4 waiting updated Vendor-neutral: the same app on different hardware Illustrative example — names and values are made up. Starting point ## The problem: Every building works differently. Systems that have grown out of different controllers, gateways and vendors come at a price. - ### High engineering costs Every building is planned, programmed and commissioned individually. - ### Laborious maintenance Updates and changes have to be carried out building by building, on site. - ### Vendor lock-in Proprietary control hardware ties every extension to individual vendors. - ### Missing transparency Across whole property portfolios there is no unified view of status and consumption. How it works ## Automate. Manage. Extend. With logiccloud CONTROL and ORCHESTRATE you get one software platform for the entire building ecosystem — independent of which hardware is installed on site. 1. 1 Control Automate Control becomes software: CONTROL runs on standard edge hardware and connects heating, air conditioning and ventilation, lighting, and energy and load management on one shared platform. 2. 2 Orchestrate Manage ORCHESTRATE connects the decentralized systems into one centrally managed edge ecosystem: software, configurations and updates are provided centrally and managed across the whole lifecycle. 3. 3 Apps Extend New functions become apps: energy management, dashboards, condition monitoring, MQTT and OPC UA services — provided centrally and installed on compatible edge systems. distributed through ORCHESTRATE Customer value ## What changes for operators. - ### Less hardware. Less dependency. Existing and new buildings run on one unified software architecture — automation becomes independent of proprietary control hardware. - ### One site or 10,000 — the same platform. Updates no longer have to be carried out building by building. New functions are rolled out centrally, systems are managed remotely — fewer on-site visits, higher availability. - ### Install instead of integrate. New requirements no longer automatically mean new hardware: buildings gain new digital functions through software, across their entire lifecycle. - ### Transparency across the whole portfolio. Software versions, configurations and updates are traceable per building — the basis for maintenance planning, support and evidence. Use the operating data ## What the operating data can deliver. Temperatures, energy consumption, operating states, runtimes and faults are already there — apps you distribute through ORCHESTRATE make them usable. - ### Optimize energy consumption Analyse consumption, adjust operating hours, improve control parameters. - ### Reduce peak loads Distribute loads intelligently and increase self-consumption of PV systems. - ### Detect anomalies Make deviations visible and identify maintenance needs early. - ### Compare buildings Benchmark properties against each other and spot the best operating strategies. - ### Transfer strategies Roll proven optimizations out to whole portfolios — via ORCHESTRATE. - ### Change traceably Every rolled-out change is in the audit log — who, when, what, on which building. A scenario ## 500 buildings — one platform. Suppose a real-estate company operates 500 buildings — with different controllers, software versions and technical systems. With logiccloud they get one shared software architecture: CONTROL runs the technical systems locally in every building, ORCHESTRATE connects all 500 sites into one centrally managed estate and distributes new applications to selected or all buildings. When a new energy strategy is developed, it becomes an application or configuration — and is rolled out to hundreds of buildings via ORCHESTRATE. ## Frequently asked questions about building automation Does this work with our existing systems? CONTROL reads and writes over OPC UA, Modbus TCP/RTU, MQTT and HTTP/REST — the full list is on the [connectors](https://logiccloud.com/en/products/control/connectors/) page. Which building services and protocols are in use in your buildings is something we check in the first conversation. Do we have to switch all buildings over at once? No. Start with one building or one group. In ORCHESTRATE, devices are grouped by label by site, building type or building service — a proven change then goes to the next group in stages. Can we also distribute software that does not come from logiccloud? Yes. ORCHESTRATE distributes any container application available as a Helm chart or Docker Compose file — from your own Git and OCI registries. Where does our buildings’ data live? Wherever you decide: on the edge device in the building, on your own infrastructure, or in cloud operation hosted in Europe. ## Your buildings. One platform. Tell us about your properties — we will show you the path from single buildings to one centrally managed building ecosystem. [Request a demo](https://logiccloud.com/en/demo/) [See the Raintime example](https://logiccloud.com/en/solutions/distributed-assets/)