BMS integration: comprehensive data integration
All Nebatic room, consumption and analysis data through APIs in your own software.
Do you already run your own application, a property platform or a digital building system? Then your users do not have to switch between different interfaces. Through suitable interfaces, Nebatic data can be brought into existing software products and workflows.
Your application stays at the centre
Nebatic provides the data, while you decide how it is used in your product: for example as an indoor climate display in a tenant portal, as an extra data layer in a facility management dashboard or as part of an internal reporting process. The integration is aimed at companies, software providers and technical partners who already run or develop digital solutions.
One interface, new functions
- PropTech & property platforms: Assign environmental readings to individual rooms, units or buildings and show them in existing portals.
- Facility management: Combine room data with existing operating information to classify anomalies faster.
- Software and IoT providers: Add Nebatic readings as an extra data source to your own applications, dashboards or analyses.
- Research & pilot projects: Provide structured data for defined analyses and study periods.
Technically integrable, meaningful in practice
Together we clarify which data is needed, how rooms and devices are mapped, how up to date values should be and which access rights apply. The right connection is designed on that basis. Technical details – such as available endpoints, authentication, data formats, historical data and usage limits – are agreed within the specific integration scope.
What matters is not only connecting two systems, but the meaning of the data: a CO₂ value needs a timestamp, a unit and spatial context so that it can be interpreted correctly in the target application. Data protection and tenant separation are taken into account according to each use case.
Part of the solution API & Integration
Frequently asked questions
Does Nebatic offer a BACnet cloud connection for existing building technology?
Nebatic does not offer a finished BACnet cloud as a separate product. Nebatic connects existing building systems and data sources through suitable interfaces depending on the project. Whether and how BACnet data is connected is something we check together with you for your building.
Can Modbus cloud connections be set up for meters and equipment?
Many meters and pieces of equipment deliver values via Modbus. With Nebatic, a Modbus cloud connection is an integration path checked per project: which devices, which values, which gateway. The data then appears in the platform next to indoor climate and consumption data.
How does Nebatic connect buildings and equipment via MQTT?
If sensors or gateways already send data via MQTT, buildings and equipment can be connected this way, provided the data format and access fit. Nebatic checks this in the project and brings the values into the platform, where they are evaluated together with indoor climate and consumption data.
Open API for building technology: how open are Nebatic's interfaces?
By an open API for building technology, meaning building systems and software exchanging data, Nebatic means interfaces (APIs) to its own data. Nebatic provides APIs through which authorised applications retrieve measurements, trends and evaluations. It is not a public open-source API; access and scope are agreed per project.
How does an IoT platform connect buildings, sensors and existing systems?
In the Nebatic IoT platform, buildings, floors and rooms form the structure into which sensors, meters and existing building systems are placed. Nebatic's own sensors measure indoor climate; other sources are connected through suitable interfaces depending on the project. This produces shared trends, issues and reports.
Digitalising facility management: where is the best place to start?
Digitalising facility management often starts with bringing existing data together. Nebatic integrates existing sensors, meters and building systems via interfaces and adds missing indoor climate measurements. This creates a shared overview without replacing everything, as a basis for the next steps.
Digital facility management: how does Nebatic fit into existing systems?
For digital facility management, Nebatic provides APIs through which room and system data can flow into CAFM, ticketing or BI systems. Conversely, existing data sources can be integrated into the Nebatic platform. Nebatic complements your digital facility management rather than replacing it.
Property management: digital solutions for multiple buildings – what does Nebatic offer?
Property managers look for digital solutions that make many buildings easy to oversee. Nebatic shows indoor climate, consumption data from existing meters and anomalies for all properties on one platform. This helps property management spot earlier where action is needed, for example with humidity or heating issues.
Energy consultant software: can energy consultants use Nebatic data?
Yes, energy consultants can use Nebatic as software for analysing measured building data. The platform and APIs provide indoor climate and consumption histories that can be transferred into their own tools. Nebatic does not replace calculation or certification software; it supplies measured data from operation.
BACnet cloud integration: can existing building automation be connected?
Often, yes. In a BACnet cloud integration, a gateway in the building reads BACnet objects locally and sends the values outbound over an encrypted connection to a platform. Nebatic does not sell a finished BACnet cloud as a separate product; whether and how BACnet data is connected is checked together with you for your building. The values then appear in the platform next to indoor climate and consumption data and can be passed on through APIs.
BACnet to MQTT: how do building data reach the cloud?
BACnet is the field protocol of building automation, with its own object model; MQTT is a lightweight publish/subscribe transport from sensors or gateways to a platform. A common BACnet to MQTT setup has a gateway poll BACnet objects locally and publish the values as MQTT messages over TLS. MQTT does not define message content, so the project needs its own data model with units, timestamps and room assignment. Nebatic checks this per project and brings the values into its platform.
How does BMS integration work with Nebatic?
BMS integration with Nebatic starts with a short clarification: which systems, which data points, which interface and how rooms are named in each system. Existing building management data is then connected through suitable interfaces, depending on the project, and shown next to Nebatic room sensors and meter data. This makes visible where the system and the room tell different stories. Control stays with your building management system; Nebatic adds measurement, trends, issues and reports.
Smart building data silos: why do they arise and how can they be overcome?
Smart building data silos arise because a building runs several systems side by side: building management, meters, room automation, sensors and CAFM, each with its own formats, naming and often its own contractor. The same room can have a different name in every system. An integration layer with a shared room and device structure replaces many point-to-point links. Nebatic places sensors, meters and existing systems into buildings, floors and rooms and provides the data through APIs.
BMS upgrade: does the old system have to be replaced?
Not necessarily. A BMS upgrade can often be done step by step: gateways translate proprietary data into open protocols, new components are connected using an open standard and a data platform brings meters, room sensors and plant data together. Full replacement makes sense when spare parts are no longer available or the system cannot meet legal requirements. Nebatic supports the data side; installation and commissioning stay with system integrators and building services contractors.
BMS vs BAS: what is the difference?
In BMS vs BAS, the terms overlap. A building automation system (BAS) usually means the controllers and field devices that run heating, ventilation and other plant. A building management system (BMS) is the supervisory level on top that displays, stores and analyses data and allows intervention. EU law uses the umbrella term building automation and control system (BACS). Nebatic is neither; it connects to existing systems and adds room-level measurement and analysis.
Modbus to MQTT: how do meter and plant data reach the platform?
Many meters and pieces of equipment deliver values via Modbus, a field protocol that stays on the building network. In a typical Modbus to MQTT setup, a gateway in the building reads the Modbus registers locally and publishes the values as MQTT messages, sent outbound over an encrypted connection. MQTT only transports messages; it does not define their content, so the project needs its own data model with units, timestamps and room assignment. Nebatic checks per project which devices, which values and which gateway fit, and then shows the data in its platform next to indoor climate and consumption data.