Skip to main content

Monitoring Building and HVAC Infrastructure

Keith Bromley

Monitoring of heating, ventilation and air conditioning (HVAC) infrastructures has become a key concern over the last several years. Modern versions of these systems need continual monitoring to stay energy efficient and deliver satisfactory comfort to building occupants. This is because there are a large number of environmental sensors and motorized control systems within HVAC systems. Proper monitoring helps maintain a consistent temperature to reduce energy and maintenance costs for this type of infrastructure.

By deploying Ethernet-based taps, building personnel and network managers have easy access to data from HVAC systems. After taps are installed, a network packet broker (NPB) is used to aggregate data from the various taps. The NPB will capture, filter, and regenerate specific pieces of data as needed and forward that data on to individual application performance monitoring (APM) tools that can be used to examine the data.

The NPB also provides the internal ability to load balance data to multiple APM tools. This allows IT personnel the ability to deploy n+1 survivability. The traffic load is divided up evenly across the number of allocated tools. Should one or more of the tools fail, the data is still split evenly across the remaining number of tools. If the number of tools is dimensioned correctly, there will be no loss of data.

The solution ends up looking like the following:


The monitoring solution described here provides the following benefits:

■ Reuse of the existing Ethernet infrastructure

■ 24 x 7 remote access to the HVAC data and system controls

■ Cost reduction due to faster alerting of system problems

■ Deployment of n+1 survivability for HVAC monitoring tools

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

Monitoring Building and HVAC Infrastructure

Keith Bromley

Monitoring of heating, ventilation and air conditioning (HVAC) infrastructures has become a key concern over the last several years. Modern versions of these systems need continual monitoring to stay energy efficient and deliver satisfactory comfort to building occupants. This is because there are a large number of environmental sensors and motorized control systems within HVAC systems. Proper monitoring helps maintain a consistent temperature to reduce energy and maintenance costs for this type of infrastructure.

By deploying Ethernet-based taps, building personnel and network managers have easy access to data from HVAC systems. After taps are installed, a network packet broker (NPB) is used to aggregate data from the various taps. The NPB will capture, filter, and regenerate specific pieces of data as needed and forward that data on to individual application performance monitoring (APM) tools that can be used to examine the data.

The NPB also provides the internal ability to load balance data to multiple APM tools. This allows IT personnel the ability to deploy n+1 survivability. The traffic load is divided up evenly across the number of allocated tools. Should one or more of the tools fail, the data is still split evenly across the remaining number of tools. If the number of tools is dimensioned correctly, there will be no loss of data.

The solution ends up looking like the following:


The monitoring solution described here provides the following benefits:

■ Reuse of the existing Ethernet infrastructure

■ 24 x 7 remote access to the HVAC data and system controls

■ Cost reduction due to faster alerting of system problems

■ Deployment of n+1 survivability for HVAC monitoring tools

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...