Connectivity as a Service
Connect Devices to BuildingPro Suites
Last updated
Connect Devices to BuildingPro Suites
This chapter describes how to connect external devices to BuildingPro Suites and display data from these devices in BuildingPro Suites.
The first step is to establish a communication link between BuildingPro Suites and the devices to be connected. In Fig. 1, this is Phase "B".
In the second step, the incoming raw data usually has to be decoded. This is because external devices send their data (payload) encoded or in another unusable format.
In the third step, the decoded data values are finally assigned to the individual ↗ attributes of an asset via formats.
The last two steps occur in Phase C.

Fig. 1 shows the schematic data flow from an external device to BuildingPro Suites.

Phase A takes place entirely outside of BuildingPro Suites. In Phase A, raw data from individual devices is provided and sent to a server or broker. An example of such a server is ↗ TTN [External Link]
The details, e.g., which transmission format is used, vary greatly depending on the manufacturer and device. Phase A is not a part of BuildingPro Suites and is not explained in more detail in this documentation. Consult the documentation of the external devices or servers to learn more about this topic.
For the further steps in this document, it is assumed that you have access to correctly configured external devices and/or access to a server.
In Phase B, the actual connection of BuildingPro Suites and the device data takes place. In this phase, a data connection is established between BuildingPro Suites and the external devices.
BuildingPro Suites accepts the following interfaces:
Kafka
Click on a link to jump directly to the instructions that describe how to establish a data connection via the corresponding interface.
In Phase C, the data is processed and made usable within BuildingPro Suites.
The data sent by the external devices and received in BuildingPro Suites is in most cases not easily readable. Depending on the manufacturer, this raw data is encoded or is in a format that cannot be used further. Therefore, this raw data is decoded with ↗ functions and converted into a human-readable .json format.
The decoded data is assigned to the individual attributes of an asset via ↗ formats.
The following prerequisites must be met to connect external devices:
The devices to be connected must be configured correctly and send data properly.
Servers and brokers must be configured correctly.
The access data for servers and brokers must be known.
It is assumed that you have created correct asset templates. The asset template must have the necessary asset attributes
Assets must be created based on the asset template.
Last updated