It’s truly amazing that automobiles can drive themselves. Driverless cars are equipped with a vast array of sensors, processes ginormous amounts of real-time data, and are constantly refining operating parameters. They adjust to crowded or empty roadways, and to all different weather conditions.

Buildings are also equipped with a vast array of sensors that supply real-time data. So why do building operators need to constantly adjust the controls? Why can’t the building drive itself?

Why don’t buildings drive themselves?

First, what is a driverless building? It’s a building that:

  • is properly configured to manage your space as it is used,
  • meets comfort and health & safety standards,
  • automatically responds to occupants’ schedules and usage,
  • precisely manages changes in weather (daily and seasonal) without intervention,
  • optimizes operation with respect to energy efficiency,
  • identifies when and where it needs servicing, and
  • does all of the above without operator intervention.

If you’re thinking that your building automation system (BAS) should be doing all of this, we won’t disagree. It should. But it doesn’t. And the reason is simple—it was never told to.

There’s a difference between what the engineering intent was and what actually got programmed into the control system. That gap is wider in some buildings than others, and the issues that cause it can vary. But until it is closed, buildings cannot drive themselves. The key to closing that gap is fixing the software that controls your buildings’ automation.

IDS can help you close the gap and make your buildings Driverless Buildings™.