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.
Welcome to the second Learn Series article!
If this is your first time ever reading the learn series then you're in for a treat. In these articles I discuss a technical topic and provide solid education for those in or thinking of joining the building automation field.
If you'd like to save a ton of time I included a video on PID Loop tuning for you.
[smart_track_player url="http://traffic.libsyn.com/buildingautomationmonthly/Episode17.mp3" title="BAM Episode 017: The How, What and Why of PID Loops" social="true" social_twitter="true" social_facebook="true" social_gplus="true" social_linkedin="true" social_email="true" hashtag="smartbuildings" ]
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?
