Eventually most AV Dealers graduate from integrating not just audio and video components but other unrelated sub-systems as well.  When we use the term "sub-system" around our shop we are referring to other systems that our code will touch.  These can include pool controllers, lighting control systems, motorized gates, HVAC systems and security systems just to name a few.

Integration of these systems pushes most Dealers into an area of potential liability that is not applicable with audio and video.  Typically this is because the AV Dealer is the Crestron Dealer and managing your own installation is a snap.  Managing the details of another contractor's system is a whole different bag of bolts.  

If you haven't had the pleasure of working with some of these trades allow me to let you in on a little secret.  There is a high probability that you are better qualified to install the product then the contractor is!   Oh sure people can jump all over me for generalizing about the industry but after doing this a few years I think I have enough scars to prove my point.  So let's review a few items that will keep your profitability high and your frustration low.

First you must ask the question “just because we can integrate it, should we”?  Many click happy programmers and geeky business owners fail on this first question.  The urge to integrate something and get it on the client's panel is so strong that nobody ever asks if it even makes sense.  Think long and hard about what features and functions that you are going to attempt to integrate and then closely examine the liability that you might be introducing into the equation by allowing your client access to certain sub-system types.  Remember that one of your most important services is protecting your client from him or herself.

Second, think long and hard about what it is you are selling and how to be profitable when integrating any sub-system.  After all most times the only equipment sale for you is the serial or Ethernet cable from your processor to the sub-system.  The contractor is providing all the hardware so the only thing you are providing is your programming expertise.  Make sure you charge accordingly and that the functional scope expectations have been clearly communicated with the client.  You would be amazed at how much time you can spend integrating something like a lighting control system when the client says (after the fact) that they want individual raise and lower controls…for all 324 loads in the system.

Most importantly make sure that there is a clear understanding that you will not touch the sub-system in question until the contractor has certified that the system is programmed, calibrated and operating properly on its own .  This is an important point and it gets glazed over by integrators that are anxious to get stuff working.  If you touch a sub-system before it has been given the green light and later there are performance issues with that system, well guess what?  You are going to get associated with being part of the problem.  Sure you can sit there on a drywall compound bucket programming away and insist all day long that your program couldn't possible be part of the issue.  Well that's been tried before and let me assure you, better to stay away and ensure that the system is accepted by the client or G.C. before you so much as walk near it.  Get it in writing, find a witness, just what ever you do don't get involved with it prematurely.

As mentioned above there is the matter of liability when tying into any system that you are not installing.  Just ask yourself questions that include phrases like “life safety” or “Loss of life or personal property”.  These are phrases that should quickly put into perspective the systems that you might not want to integrate.  Some famous examples here are security systems and anything motorized like a garage door or driveway gate.  You should check with your legal council and establish company policies regarding integration with these sub-systems.  You will be glad that you did later.  Should a wealthy client suffer a loss you can bet the insurance company is going to sweep up any and all parties that it can attach to a law suit for recovering losses.  In the case of anything motorized just think about getting a call from a client saying the garage door just crushed his brand new Porsche Cayman S or the motorized gate pinned their granddaughter to the pavement.

 If you think I am joking or am blowing things out of proportion here are a few real world examples.  The names have been removed to protect the not so innocent.

• Pool contractor doesn't wire the suction and return line valves the same.  Client changes from pool to spa mode on his touchpanel and promptly empties all the spa water into the pool, thus burning out the pump.  Try disassociating yourself from that one.
•  Thermostats are functional and wired correctly, but have been connected to the wrong zones.  The client selects mode off for the three season porch but is actually turning off the heat in the garage.  Freezing and bursting water pipes to follow.  Again the initiating device was your touchpanel, right?
•  Security system protocol is written so poorly that excessive polling for zone status actually takes points of protection offline long enough that you could open and close zones while the system is armed.
•  Programmer takes the chandelier winch off of the spring loaded center position off key switch and moves it to a lighting module.  Then programs the module output with maintained instead of momentary logic.  Inexplicably he also manages to put only a down button on the nearest keypad.  Limit switch on the winch fails during the first test of the button and the property manager watches as the chandelier craters on the marble foyer floor.  That $5 key switch in the foyer closet is looking pretty good right about now.
• Integrator is asked to provide driveway enunciation.  Decides to take the request to exit loop detector for the gate, remove the connection to the gate controller and run it to a digital input on his control processor.  Then run a relay output back out to the gate.  Having now interrupted a hardware safety interlock with a software layer the next time the program is not running or the processor is damaged the gate will close even if a vehicle is sitting on the loop in the path of the closing gate.

Disclaimer: ControlWorks is not an agent or employee of Crestron Electronics, Inc.  The opinions expressed are solely those of the writer. Product representations and capabilities may change and should be verified by the user independently. Images are the property of their respective owner.