System Overview


BACE is a multipurpose device-to-cloud solution, enabling the user to measure and receive data in an easy, fast, and secure way. Users can connect their devices to an enterprise system using BACE with a few lines of code.

The BACE system consists out of two main components: the IoT Connectivity Module and the IoT Connector. BACE integrates seamlessly with your assets and enterprise system. A schematic overview of the system is shown below with a more detailed description of each part of the system.

Your Device

This could be any device that you would like to get connected in order to unlock the power of IoT. You can think of a sensor, a machine, an appliance, a wearable or any other type of hardware device.

IoT Connectivity Module

There are three different IoT Connectivity Modules: BACE Core, BACE Plus and BACE Go. Each module comes in a different form factor and supports a wide range of communication protocols to speak with your device. The information fetched from your asset by IoT Connectivity Module is sent to cloud via cellular, WiFi or Ethernet communication. More information about different modules could be found here.

IoT Connector

IoT Connector is a group of cloud applications to manage bi-directional device communication and store your device data. The asset information is exposed as an API service or webhook so that it can be connected to enterprise systems with a few lines of code. The API endpoints could be used for fetching the latest data from your device, retrieve historical device data from IoT Connector, and get any event errors occurred between your asset and IoT Connectivity module. Each API call is checked against the user accounts rights before replying information.

Webhooks are usually setup to get notifications immediately when new data is fetched from your device. The big difference compared to API is that the latest data is automatically published to your endpoint and where as you need to poll API endpoints in regular basis to check if there is an update.

In order to do your first API call you will need to sign in with a valid user account. Read how to authenticate in the next section.

Last updated