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.
I was on the phone with one of our customers who is trying to grow his BAS business to $20M in revenue by next summer. As he and I were talking he asked me "Phil if you were in my shoes how would you build and grow a contracting business?".
That was an interesting question, I paused and thought to myself, "Man, there are so many different things I would do and so many interrelated areas I would need to cover."
So, I told him this is not a quick answer and that it would take several conversations to really flush out the topic.
He agreed and we set up a reoccurring weekly call to really dissect the topic.
I asked him if he was okay with me turning this into a weekly blog post that I could update as we moved through the calls and he agreed that would be useful to others in the same position.
When I was a tech I realized there was not a good source of information on common protocols. That's why I created this guide. However, if you are in sales, facilities management, or engineering you will still find this guide to be helpful. This guide starts with general overviews and then dives deep into each protocol. Feel free to go as deep down the rabbit hole as you'd like.
[Author's Note] This guide will continue to be updated/restructured in a series of future releases, your feedback is critical to this.
So without further ado let's get started.
A protocol is a set of rules that establishes how systems communicate. One of the best analogies for a
protocol is that of a language. If you think of the English language it has rules for the syntax and structure of language. It also has object types in the form of verbs, nouns, etc.
Protocols are the rules that dictate the structure, organization, and function of communication systems.
BEMS, BMS, BAS, EMCS, and this list goes on and on. Welcome to the acronym-filled wasteland know as building automation. You may be wondering, "What is a Building Automation System?"
Even among "building automation" professionals, there's a lack of consensus around what building automation is. And this is exactly why I wrote this guide.
The purpose of this guide is to help you understand what building automation is.
No matter what your role is when you finish this guide you will understand what a building automation system is and how it works.
"I’m new to building automation and it’s a bit overwhelming. What’s the first thing I should do?"
More and more, folks who aren’t building automation professionals are being put in charge of building automation systems.
I’ve compiled a list of 13 actions someone with a new or existing building automation system can take to make sure their system is setup to support them. The good news is that with a few actions you can reduce the risk of your building automation system failing.
I'm proud to say that for several months now this post is the number 2 result on Google Search for "What is Tridium". So if you are landing here for the first time, first off welcome!
The post below is part of a 2 part series that seeks to provide an overview of what Tridium is and what Tridium isn't. At the end of this article, I will provide you some related articles and a chance to learn more about building automation.
This post will teach you how to program a Building Automation System. But not in the way you think…
Of all the topics I’ve discussed, this is the one I’ve skirted around the most. I’d been struggling with how to best teach this topic. Not because I don’t know how to program but rather because each company has a different set of programming tools. So therein lies the rub, how do you teach a topic that is unique to each vendor…
Well, after a ton of hemming and hawing (that’s a southern US phrase for y'all that means I was procrastinating…) I decided to ignore the vendor problem and just dive into the basics.
So without further delay...
Well, folks, it's time. Time for me to update one of my most popular posts. A lot has happened since I wrote my two-part series on Tridium.
You can click on the links to read Part 1 and Part 2.
I initially wrote the series as a way to solidify my knowledge around Tridium. Little did I know it would become one of my most popular posts and also a top ranking Google search.
Well, a lot has changed since I wrote those articles. Tridium released a new solution called N4 (Generation 4 of Tridium essentially), and to answer a ton of questions I am updating my series.
Systems Integration is a tough topic. I've been planning to write this series for a long time. This series is going to take you from zero to systems integration hero.
In this series you will learn the process I created when I first started systems integration way back in 2008. I've since refined this process to align more closely with enterprise architecture models, but at the end of the day, it's still my same process, just a little bit cleaner :-D
