The Four Steps to Two-System BAS Integration: The Role of Iteration
This month, we dig deeper into the topic and take a look at nested use cases.
In my previous article on two-system integration, I discussed the four steps for effective integration. Just to recap, those steps are:
- Step 1: Define the use case;
- Step 2: Seek solutions for the use case;
- Step 3: Build out work packages; and
- Step 4: Secure contractors
How Does this Process Apply to Systems that Encompass More than Two Systems?
It used to be that the building automation system would act as a centralized point for integration; however, due to the rise of APIs and web-based systems, designers and engineers must consider that “getting data” to the building automation system might involve multiple layers of integration.