Building Automation
That subhead is a bit cryptic, but what I mean to point out is that it’s important to figure out exactly how things will work with respect to day-to-day adjustments. For example, if the lighting system allows for operating zones remotely, is that a good idea? Can a local wall station be used to change the light levels at that point, or does remote control render wall stations ineffective? In many cases, integrations only accomplish monitoring rather than control (e.g., energy meters), but you still must settle these questions when they include control. For example, in the case of the domestic water heat exchangers, it was in our scope to disable the recirculation pumps whenever the building was unoccupied. Based on a discussion with the product vendor, it was suggested to disable the heat exchangers at the same time. The integration did not afford us direct control of the mixing control valves, so we arrived at resetting the operating set point to a low value during occupied times (e.g., around 70°F instead of around 120°).
It can be really easy to be so caught up in the requirements, specifications, manuals, and drawings that you lose track of what the customer really wants. You should be sure to always keep in mind the purpose behind the important work you’re doing. For example, the reason for monitoring an emergency generator over integration is often condition-based maintenance of the fuel and proving it’s being exercised regularly. The reason for monitoring a UPS is often to catch early signs of battery failure (such as increased battery temperature). As you bear these things in mind, remember that, once communications have been established and information is flowing, your work isn’t quite done. You have an opportunity to make sure the subjective aspects of your work are having a positive impact for your customers.