Episode Description:
Your building automation system may be missing valuable information that already exists elsewhere in the building.
What happens when your BAS and audiovisual (AV) systems operate independently, even though both are designed to support the same spaces?
Conference rooms experience unnecessary heating and cooling, occupancy data goes unused, and facility teams are left troubleshooting comfort complaints that could have been avoided.
In Episode 566 of the Smart Buildings Academy Podcast, we explore the opportunities and challenges of integrating AV systems with building automation systems.
For BAS professionals, understanding how these systems interact can open new possibilities for improving occupant comfort, energy efficiency, and building performance. But successful integration involves more than connecting devices and exchanging data.
Topics Covered
Are you overlooking valuable building data because your AV and BAS systems aren't communicating? Listen in to discover what these integration opportunities could mean for your next project.
Click here to download or listen to this episode now.Podcast Video
Building automation systems (BAS) and audio-visual (AV) systems are often designed, installed, and commissioned as separate systems. Both serve the same building occupants, yet they rarely share information that could improve comfort, energy efficiency, and operational performance.
This separation creates a missed opportunity for building automation professionals.
Modern AV systems collect valuable information about room scheduling, occupancy, and space utilization. When that information becomes available to the BAS, it can support more responsive HVAC operation, better energy management, and improved occupant experiences.
In Episode 566 of the Smart Buildings Academy Podcast, we explore how AV and BAS integration works, the technical and organizational challenges involved, and what controls professionals should consider when planning these integrations.
Consider a corporate headquarters with 12 floors and approximately 20 conference rooms. The building owner has invested more than $2 million in AV technology, including touch panels, microphones, displays, and sophisticated room controls.
The mechanical systems are equally advanced, with modern BAS controls, variable air volume (VAV) boxes with reheat, and occupancy sensors throughout the building.
Both systems pass commissioning. Both perform according to their individual specifications.
Four months after occupancy, however, the facility management team begins receiving repeated heating and cooling complaints from conference rooms.
Rooms scheduled for large meetings are being conditioned as though they are empty. The AV system has information about scheduled meetings and room activity, but the BAS has no access to it.
The problem is not necessarily a failure of either system. It is a failure to coordinate information between them.
This scenario illustrates a common challenge in commercial buildings. Multiple intelligent systems operate within the same environment, but the data needed to optimize overall building performance remains isolated.
Traditional BAS occupancy strategies often rely on motion sensors, occupancy schedules, or predefined operating hours.
These inputs provide useful information, but they do not always reflect how spaces are actually being used.
Conference rooms present a particularly difficult challenge because their occupancy patterns are unpredictable. A room might remain empty for several hours before suddenly accommodating a large group of people.
The BAS may not know that a meeting is scheduled, how many people are expected, or when the room will become occupied.
AV and room scheduling systems may already have access to this information.
Conference room scheduling platforms often contain information about upcoming meetings, expected attendance, and room reservations.
For building automation professionals, this creates opportunities to better align HVAC operation with anticipated room usage.
Instead of treating every conference room according to the same fixed schedule, a BAS could potentially use scheduling information to support more responsive conditioning.
The important distinction is that scheduling information indicates intended use, not necessarily confirmed occupancy.
A reserved room might remain empty if a meeting is canceled or attendees fail to arrive. Integration strategies must account for the difference between scheduled and actual room use.
Many AV systems include room control interfaces, occupancy detection, or other mechanisms that provide information about whether a space is actively being used.
Sharing this information with the BAS can improve its understanding of room conditions.
Confirmed occupancy can complement existing HVAC sensors and help address situations where traditional occupancy detection provides incomplete information.
Some AV environments may provide information about the number of people using a room.
This information can be particularly valuable in conference rooms, training spaces, and other areas with highly variable occupancy.
Occupant count can influence sensible cooling loads and ventilation requirements.
However, occupancy information must be evaluated carefully before being incorporated into ventilation control sequences. Data reliability, sensor accuracy, applicable codes, and system design requirements all affect whether occupancy counts are suitable for controlling outdoor air delivery.
AV and BAS integration does not necessarily require a complicated architecture.
Several communication methods can support data exchange between systems. The appropriate approach depends on the existing equipment, required data, network architecture, and long-term maintenance expectations.
Dry contacts provide a relatively simple method for communicating basic equipment or room states between systems.
For example, an AV controller might expose a binary signal indicating that a room is active.
The BAS can monitor that signal through an appropriate input.
This approach can be useful when only a small number of states need to be exchanged and a straightforward interface is preferred.
Its limitations become apparent when more detailed information is required, such as occupancy counts or scheduling data.
In some buildings, AV and BAS systems may be able to use information from common occupancy sensing devices.
The challenge is determining how that information will be distributed, which system owns the sensor, and how the interface will be maintained.
Sensor compatibility and signal requirements must also be evaluated. Not every device can safely or reliably provide information to multiple systems without additional hardware or a supported communication interface.
When supported by the AV equipment, BACnet can provide a familiar integration path for building automation professionals.
BACnet allows compatible devices and systems to exchange standardized building automation data.
However, the presence of BACnet support does not automatically guarantee a successful integration.
Point availability, object definitions, device configuration, network access, and vendor-specific implementation details must all be verified.
Gateways and application programming interfaces (APIs) provide additional options when the AV system does not directly expose information through a BAS-compatible protocol.
A gateway may translate information between different communication protocols.
An API integration may allow a BAS supervisor or integration platform to retrieve information from an AV or scheduling system.
These approaches can expand the available data, but they also introduce additional considerations involving authentication, software maintenance, network access, and vendor support.
The objective should not be to select the most technically sophisticated integration method.
It should be to identify the simplest reliable approach that meets the building's operational requirements.
AV and BAS systems often have different network requirements.
AV environments may support high-bandwidth media traffic, conferencing equipment, and devices that require rapid communication.
BAS networks generally prioritize reliable control communication, predictable operation, and secure access to building systems.
Connecting these environments requires coordination between controls contractors, AV integrators, and information technology teams.
Network segmentation helps separate different types of traffic and limit unnecessary communication between systems.
An AV and BAS integration should identify the specific devices, services, and data exchanges that need to communicate.
Appropriate firewall rules, network boundaries, and access permissions can then be established around those requirements.
A shared building network should not automatically mean unrestricted access between all connected systems.
Differences in IP addressing practices can create long-term reliability problems.
AV devices are frequently configured using Dynamic Host Configuration Protocol (DHCP), sometimes with reserved addresses.
BAS devices are often configured with static IP addresses.
Neither approach is inherently unsuitable, but undocumented differences can create problems when network equipment is replaced, addressing configurations change, or devices are reconfigured.
The addressing strategy should be coordinated during design and documented in the as-built records and operations and maintenance manuals.
AV devices may include network-connected microphones, cameras, displays, conferencing systems, and control processors.
These devices can introduce additional cybersecurity considerations when connected to building automation infrastructure.
Integration planning should address authentication, software updates, network permissions, and responsibility for maintaining secure configurations.
Cybersecurity should be part of the original integration design rather than an issue addressed after systems have been connected.
AV and BAS systems may operate with different expectations for communication speed.
An AV user interface often needs to respond almost immediately when an occupant presses a button.
A BAS may retrieve information from connected systems at scheduled polling intervals.
If a BAS polls an AV point every 60 seconds, a change in room status may not be recognized until the next polling cycle.
For an occupant expecting a coordinated one-touch room experience, that delay can make the integration appear unreliable.
Where supported, change-of-value communication can reduce unnecessary polling and provide more timely updates.
When polling is necessary, the expected response time should be understood and communicated during design.
Not every integration requires instantaneous operation. The acceptable response time depends on the function being performed.
Building automation integrations must remain reliable throughout the building's operating life, not simply during initial commissioning.
Software and firmware updates introduce an important maintenance risk.
An AV integrator might update a controller's firmware, resulting in changes to its available objects, data structure, or communication behavior.
If the BAS depends on information that changes during the update, the integration may stop functioning.
The failure may not be immediately obvious.
A BAS could continue operating using outdated information while the facility team remains unaware that the AV data source is no longer updating.
Integration design should include a method for identifying unavailable or stale data.
This may involve communication health monitoring, timestamps, heartbeat signals, or other appropriate fault detection methods.
A data point that remains unchanged for an extended period is not necessarily faulty. Some legitimate states can remain constant for days. Monitoring should distinguish between an unchanged operating state and a communication failure.
Maintenance agreements should also establish notification requirements when firmware or software changes could affect connected systems.
This helps reduce the likelihood that routine AV maintenance unintentionally disrupts BAS functionality.
One of the most common integration failures occurs when both systems are commissioned separately.
The AV contractor verifies that the AV equipment performs correctly.
The controls contractor verifies that the BAS performs correctly.
Both systems pass their respective commissioning procedures.
Yet nobody tests whether the information exchanged between them produces the intended result.
An integrated system requires an integrated commissioning process.
Commissioning should validate the complete sequence of operation, including:
These tests should be documented as part of the project commissioning requirements.
A successful point-to-point communication test is not the same as validating the complete operational sequence.
The system must be tested from the initial event through the resulting BAS response.
Technical compatibility is only one part of successful integration.
Projects can encounter significant problems when responsibility for the integration is unclear.
Consider a conference room that begins experiencing comfort complaints two years after occupancy.
The AV integrator determines that its room controller is functioning correctly.
The BAS contractor confirms that the HVAC equipment is operating according to the information it receives.
The facility manager is left coordinating between two contractors, neither of whom accepts responsibility for diagnosing the communication problem.
This situation can be avoided through clearer project documentation.
A responsibility matrix should identify who owns each component and activity involved in the integration.
Responsibilities may include:
These responsibilities should be incorporated into specifications, commissioning documents, warranty requirements, and maintenance agreements.
Coordination should begin during design rather than waiting until installation or commissioning.
When integration requirements are not included in the original project scope, they can become costly change orders or unresolved gaps between contractors.
One of the most important considerations in AV and BAS integration is deciding how much information actually needs to be exchanged.
A technically capable integration platform might allow dozens of points to move between systems.
That does not mean every available point should be integrated.
Each additional data point creates another dependency that must be documented, monitored, maintained, and troubleshot.
Unnecessary complexity can make the system more difficult for facility personnel to understand and support.
A practical initial integration might focus on three types of information:
These inputs can support meaningful building automation applications without requiring an unnecessarily large integration scope.
After the integration has operated successfully through a full seasonal cycle, the team can evaluate whether additional data would provide measurable operational value.
The objective is to create an integration that facility teams can maintain, not simply demonstrate how many systems can communicate.
AV and BAS integration creates opportunities for controls professionals to contribute earlier in the building design process.
Rather than waiting for a complete controls specification, BAS professionals can ask questions about the other technologies being installed throughout the building.
What room scheduling platform will the owner use?
What occupancy information will the AV system collect?
Will that information be available through BACnet, an API, or another supported interface?
Who will maintain the connection after occupancy?
These questions can reveal integration opportunities before the project reaches a stage where changes become expensive.
They can also help controls contractors participate in broader discussions about building performance, occupant experience, and operational efficiency.
The value of building automation increasingly depends on how effectively systems use information from the surrounding building environment.
AV systems often contain information that building automation professionals can use to improve HVAC operation and space management.
In many cases, the building owner has already invested in the technology that collects this information.
The opportunity lies in making selected data available to the BAS in a reliable, secure, and maintainable way.
Successful integration requires more than connecting two communication interfaces. It depends on thoughtful network design, clear scope definition, appropriate data selection, end-to-end commissioning, and established maintenance responsibilities.
For BAS professionals, room scheduling systems represent a particularly promising starting point because they can provide insight into how spaces are expected to be used.
The next time you review a commercial building project, consider what information the AV and scheduling systems already know that the BAS does not.
That conversation may reveal an opportunity to improve building performance without adding another layer of unnecessary complexity.
Explore the technical considerations, common failure points, and practical opportunities involved in integrating audiovisual systems with building automation.
For a deeper discussion and insights from the field, listen to this episode on the Smart Buildings Academy podcast.