October 2018

[an error occurred while processing this directive]
(Click Message to Learn More)

One Protocol to Rule them all?

Taking buildings to the cloud, connected buildings, advanced analytics, machine learning, Internet of things… How do we get value out of buildings in the best way possible that is also future proof? Is there such a way?

Nicolas Waern
Nicolas Waern

New Products
[an error occurred while processing this directive]
Site Search
[an error occurred while processing this directive]
Past Issues
[an error occurred while processing this directive]
[an error occurred while processing this directive]

The Handshake-Problem with the API-economy

It doesn’t have to be complicated, so I will try to simplify things, starting with the API-economy. There’s a lot of data in buildings, and there’s a lot of opportunities to make sense of the data, do analytics on it and to create new services for people working with buildings. To get the data out usually you must have an interface, an API of sorts. Making buildings talk to people is, after all, the one thing that I try to help out with.

An API is basically like defined handshake. I have my defined handshake, you might have yours, and if we were to shake hands, we'd face a couple of different options which are described here. The definition of an API is an Application Programming Interface. Simply put, it is a defined handshake which will make the process of making handshakes into something that will at least be easier than without a defined API. But it won’t solve everything, far from it. It might make things worse in the long run. Not necessarily, but it might.

Let’s go through a couple of scenarios.

We don’t have any defined APIs

If we don’t have any defined APIs, it will be difficult for us to shake hands because we don’t even know how we could shake hands. And if someone else wanted us to shake hands, they would have a really hard time figuring out how we could shake hands because they might not have a good idea to what languages we are talking or if we even want to shake hands.

The first step would be to get APIs = the possibility to shake hands in a defined way and not lock in the data, hoping that will make us irreplaceable.

We have an APIs, but they are not the same

We now have our own handshakes, but they are not the same. Who wants to initiate the handshake? Let’s say that one side wants to shake hands; then they will have to figure out how to do it. They can change their handshake to fit the other one’s handshake or also create something in between where the handshaking will take place. This might be anything but simple or difficult, but it adds complexity, and it will take time.

Let’s say you walk into a room with 20 different APIs. 20 people with different handshakes, and for every person you need to figure out what is in their handshake and how you should approach it. That will take time, effort and as we’ll describe later, it will only be 1% of the effort needed in getting to the complete solution.

We have an APIs, and they are the same

We now have our own handshakes, and they have been defined in the same way as our counterpart. We can now rest assured that things will be easier moving forward. However, the handshake is only the first part. It doesn’t mean that we speak the same languages. It doesn’t mean that we have the same values. It doesn’t really say much of how we can talk to each other, the effort it takes to talk to each other and also what language we should use in talking to each other.

Imagine this at scale.

We are in the same room. We all want to talk to each other, but we have different definitions of the same things. Or we have different definitions of different things. We speak in different languages. And everything about what we do, how we do it, is totally different. We come from different worlds, but somehow, someone came up with the idea that we are going to act like one just because we share the same definition of a handshake. And someone else out there expects that it is the outcome of us working together that is the amazing thing.

Culture eats strategy for breakfast

Basically, this is a cultural question which relates to us people as well. Consider a merger between two companies where the culture is different even though everything else stays the same. This will be problematic and as we all know Culture eats strategy for breakfast.

It is not far-fetched to compare the definition of culture and values to that of semantic interoperability between systems considering that definition of culture is:

“The customary beliefs, social forms, and material traits of a racial, religious, or social group.”


“the characteristic features of everyday existence (such as diversions or a way of life) shared by people in a place or time.”

And semantic interoperability:

Semantic interoperability is the ability of computer systems to exchange data with unambiguous, shared meaning. Semantic interoperability is a requirement to enable computable machine logic, inferencing, knowledge discovery, and data federation between information systems.”

Semantic interoperability leaves little to no doubt as to what is inferred. Whereas cultural norms and values would be more open to interpretation. However, both play the vital role of acting as a mediator between two or more otherwise interoperable areas what could be important boundary spanning elements and possible definitions of a subset of the ANT-theory by Bruno Latour.

And as such, an important piece when trying to make different things come together to make things happen in a better, future-proof way.

A shared set of values is the key

A handshake is nothing but a handshake. It is what comes after which is the most important and exciting part. Thinking that the outcome of the merger will lead to amazing results just because you shake hands with the other company is exactly the same thing that is happening right now out there in the world of IoT. It won’t really bode well.

“According to McKinsey research, only 16% of merger reorgs fully deliver their objectives in the planned time, 41% take longer than expected, and in 10% of cases, the reorg actually harms the newly-formed organization.” – HBR

A merger is after all a clash of two systems with their own set of standardized definitions and ways of working. Just making them shake hands won’t make them work. Far from it.

“…You will have to choose one structure that integrates the two companies.”

Replace companies with systems, and the two companies mentioned might not be two companies but a merger of 10 companies, i.e., Systems.

If I say tree, what do you think of?
I think about a Christmas tree.
And when I say Christmas tree, what do you think about?

•    What is the size?
•    What is the location?
•    Does it have a star at the top?
•    What’s the color of the star?
•    The material of the star?

It doesn’t say anything else about anything really because we haven’t got shared definitions and boxes of what should be included about what a tree is. It is partly to define the size of the boxes and what they are and a part where we can standardize a subset of an industry with the same tagging conventions/standards.

I could write 30 more pages on this matter but let’s move on to the final remarks…

Artificial Intelligence and Machine learning needs more than a handshake

The truth is that most of the analytics efforts out there today are spent on 80-90% cleaning of data. And 10-20% on the part where the value gets derived. So, this is an immediate problem that needs to be solved to leverage existing data with Artificial Intelligence and Machine Learning. This is crucial for us to really make sense of the data and to achieve results never before possible.

The problem within the building automation sphere is not that big in comparison to other fields. And why is that?

The solution to all of these problems

As discussed, APIs are a good start but don’t get fooled in thinking that the API economy is the end of all of our problems. As discussed over and over again (It’s important!) it might actually be the exact opposite and the beginning of a whole new set of problems as depicted above. 

The answer lies in standardized protocols which can harmonize data from different vendors, acting as a device to device communication protocol.

Semantic interoperability, and how to solve this issue will be of major importance moving forward. Consider it as the rule book when having made a merger and how everyone should work.

It is here Haystack tagging comes in, and where BACnet will play a major role moving forward and as we have said before, BACnet might be renamed to BACnet/IoT soon enough!

BACnet is the standardized bowl filled with pockets to fill with an industry-specific standard and IoT solutions. But the bowl and the BACnet objects within the protocol is what is needed, and luckily we seem to be well on our way in realizing this for the betterment of all buildings and cities out there. The problem is not that big within the building automation sphere, yet. But with the advent of unstructured data coming in from the sides, we are bound to have a lot of challenges moving forward.

Because BACnet and upcoming addendums solve that pretty well, providing a standardized platform for others to build on.

Final words – Focusing on the outcomes

For others to build on, that is the important part.

Using BACnet as the protocol layer for everything is, in my opinion, the key in transforming data to information when making both buildings and cities “Go-IoT” and Cloud ready.

Connor McCloud might be angry at me for writing this, but there won’t be the only one solution out there. And that is how it should be. There won’t be one solution to rule them all, and what we should strive for is open standards, service transparency and the creation of true Digital Twins for the betterment of others. I might think that BACnet is the solutions to rule them all, but it is the outcome we all should collaborate towards. I’m in it to create a better world for everyone with smarter, more energy efficient buildings. Fewer costs and headache for maintenance and above all, better indoor climate, personalized experiences for tenants and users of buildings worldwide.

In order to make buildings talk to people, we need to understand what they are saying. And luckily, we are well on our way!

Nicolas Waern
The Building Whisperer

[an error occurred while processing this directive]




About the Author

Nicolas Waern is the CEO of the fast-growing Nordic IoT company Go-IoT and is usually accompanied with the hashtag #Thebuildingwhisperer on Linkedin and Twitter. He loves what he does, and he knows he’s in this business for the long run, having the time of his life. Go-IoT makes it easier for others to harmonize data in buildings as well as simplifying the transfer of any data to and from the edge to any cloud, leveraging all that is BACnet with their dynamic BACnet server on the edge. Their offering consists of open and modular software and hardware solutions which form a powerful edge gateway under the name of DINGO and Go-IoT Cloud. Their solutions have the power of converting any sensor technology into BACnet objects, creating a BACnet umbrella for everything making SCADA systems, BAS, BEMS and anything in between, IoT-Ready. Why not take advantage of all that the API economy has to offer?


[an error occurred while processing this directive]
[Click Banner To Learn More]

[Home Page]  [The Automator]  [About]  [Subscribe ]  [Contact Us]


Want Ads

Our Sponsors