Difficulty: starter
Content
Learning Objectives
After reading this article, you’ll be able to:
Understand which sensors natively integrate with Workplace
Define which approach is needed when you want to integrate a new sensor
Hardware selection process
Our commitment to continuous impact extends not only to our software but also to the hardware selection and data platform integrations we offer. We recognize the critical role that hardware plays in gathering accurate and reliable data, and we strive to stay at the forefront of IoT technology by conducting extensive research and development, fostering partnerships with leading hardware vendors, engaging in co-development initiatives, and actively seeking market feedback.
Hardware Agnosticism and Evaluation
To ensure that our customers have access to the best IoT sensors and building management systems, we maintain a hardware-agnostic approach. This means that we are not tied to any specific vendor or technology, allowing us to remain flexible and adapt to advancements in the IoT landscape. Since 2015, we have invested in a dedicated team of IoT engineers who continuously research, test, and evaluate the available hardware technologies. Our goal is to recommend the most suitable sensors and systems to our customers based on their specific needs, ensuring optimal performance and compatibility with our software solutions.
Neutral Vendor Evaluation Matrix and Sensor Quadrant
Through our years of experience and extensive testing, we have developed a neutral vendor evaluation matrix and sensor quadrant. This comprehensive assessment tool allows us to evaluate different hardware solutions based on key criteria such as accuracy, battery life, granularity, availability, sustainability, price, and support. By leveraging this evaluation matrix, we can provide our customers with the reasoned choice behind our proposed IoT sensor vendor. This ensures that the selected sensors and/or data platforms align with the requirements and deliver the desired outcomes, while remaining neutral and avoiding vendor lock-in.
3 approaches we apply for hardware
1. Native sensors in the Spacewell Portfolio
Spacewell adds sensors into the Hardware Portfolio when we can vouch for them in terms of Hardware quality, data stability, ease of installation (both software viewpoint and from a handyman perspective), etc. Of course there are also logistics and pricing requirements that need to align with our strategy and values.
The portfolio is very limited because not many sensors pass all the tests and the whole process is time consuming.
Devices in scope: LoRa devices listed under LoRa Sensors & Gateways, Pointgrab, Xovis, VergeSense
How to configure to make these devices send data to Spacewell? Not needed: Native integration
2. Sensors that “work with Spacewell”
These are sensors that Spacewell does not sell nor distribute, so customers need to buy them themselves. However, Spacewell will make sure we can connect to the sensors. In more technical terms, we make sure the API connection works.
This approach creates work and responsibility at Spacewell side since we need to develop and maintain the connection. In other words, it has roadmap impact. A strong business case is needed if a sensor you want to bring forward a sensor to be considered for this case.
Devices in scope: Airthings, https://www.elsys.se/en/ers-co2/
How to configure to make these devices send data to Spacewell? Not needed: Native integration
3. Sensors that push data to Spacewell using the Generic Endpoint
When customers or hardware providers want to connect with Spacewell, they can create the integration themselves: using the Generic Endpoint feature, Workplace will provide a webhook URL and authorization token which can be used to set up a connection between the external data source and Workplace.
Devices in scope: all devices that use a Spacewell supported data type and where the data can be send in the supported payload format; see https://spacewell.atlassian.net/wiki/spaces/KB/pages/5242896/External+Data+Sources#Supported-data-types-%26-payload
Examples of devices we connected with: https://bgrid.com/, https://www.siemens.com/global/en/products/buildings/automation/desigo.html ,https://www.se.com/ww/en/, Zens PuK IoT Visual, https://www.regent.ch/en/
How to configure to make these devices send data to Spacewell? External Data Sources
Search