Welcome back to another exciting article in the systems integration 101 series. In this article we are going to walk through the first step of the systems integration process, creating use cases.

Over the years I've created tons of systems integration use cases. I like to think I've come up with a pretty good process for detailing out use cases that works quite well. In today's article I am going to walk you through just that.

How can my building automation system communicate with xyz system?

What protocols can my BAS support?

BACnet, Lon, Modbus, all I really want to do is run my building!

Do any of these thoughts sound familiar to you?

How can you ensure that your investment into a BAS will be around 5 years from now?

Can you determine if your new BAS will work with your legacy systems?

How do you manage software upgrades and critical system patches?

A building automation system is a life-cycle investment. However, the BAS is often only evaluated based on first cost.

Let's face it most informal training sucks!

How can you build the skills you need to support your BAS?

How do you know if your BAS is designed efficiently?

Does your BAS have the correct capacity to grow with you?

These are questions that every building owner and controls contractor face at some point in their career. Up until this point there really hasn't been an answer to these questions.

Do you know what tools are provided with your new BAS?

Did you know that there is an analytics package built into your BAS?

Would you like to ensure that you have the ability to look at the historical performance of your BAS?

Does the thought of sifting through hundreds, maybe even thousands of data-points seem more painful than a root canal?

If so, don't worry, in this article I'm going to help you pin down the key capabilities you need to effectively implement a trending strategy. This is the fourth article in a 10-part series on how to evaluate your building automation systems.

Are you overwhelmed with how fast the BAS market is changing?

Do you find yourself struggling to keep up with systems and how to evaluate them?

Are you looking for an easy way to consistently evaluate BAS's that is vendor neutral?

If so you are in the right spot. This is the third article in a 10-part series on how to evaluate your building automation systems.

Are you overwhelmed with how fast the BAS market is changing?