.webp)
Dartmouth Traced an OEM Firmware Defect by Matching Reporting-Level Communication Dropouts to a Single Firmware Version While Buildings Kept Running Normally
A firmware defect in a major OEM's devices at Dartmouth College produced no comfort complaints. The buildings stayed conditioned. The occupants were unaware.
Dartmouth's sophisticated IT network observability toolset picked up the invisible issue. HVAC devices running a particular firmware version intermittently stopped communicating with the front-end server, even though BACnet traffic continued to flow normally to the device-level equipment. Without fleet-wide visibility into the behavior that exposed the pattern, Douglas Plumley, Software Architect at Dartmouth College, said, "we'd probably still be working on the issue."
The tool that made the correlation possible is AKiPS, a network monitoring platform that maps IP and MAC addresses to switch ports and tracks switch-port statistics over time. When the BAS team noticed devices going dark from the BMS server, they could pull AKiPS data for each affected device, identify the common firmware version, and escalate the issue to the vendor with evidence. The pattern was visible only because every affected device was in the same inventory and had the same type of network data.
Investing in device record data (device ID, firmware version, configuration, switch-port attribution) directly helps Dartmouth reduce diagnostic time. "Anytime we go to fix an operational issue in a building, having those records intact, knowing what the devices are, what the firmware versions are, how they're configured, really helps us lower the time to resolve issues," Plumley said.
The case is a specific argument for IT-side observability applied to OT. Dartmouth runs a converged IT/OT network, which accelerates the maturity of their OT device management capabilities.
Register for the next Nexus Labs event.
Sign up for the newsletter to get 5 stories like this per week:
A firmware defect in a major OEM's devices at Dartmouth College produced no comfort complaints. The buildings stayed conditioned. The occupants were unaware.
Dartmouth's sophisticated IT network observability toolset picked up the invisible issue. HVAC devices running a particular firmware version intermittently stopped communicating with the front-end server, even though BACnet traffic continued to flow normally to the device-level equipment. Without fleet-wide visibility into the behavior that exposed the pattern, Douglas Plumley, Software Architect at Dartmouth College, said, "we'd probably still be working on the issue."
The tool that made the correlation possible is AKiPS, a network monitoring platform that maps IP and MAC addresses to switch ports and tracks switch-port statistics over time. When the BAS team noticed devices going dark from the BMS server, they could pull AKiPS data for each affected device, identify the common firmware version, and escalate the issue to the vendor with evidence. The pattern was visible only because every affected device was in the same inventory and had the same type of network data.
Investing in device record data (device ID, firmware version, configuration, switch-port attribution) directly helps Dartmouth reduce diagnostic time. "Anytime we go to fix an operational issue in a building, having those records intact, knowing what the devices are, what the firmware versions are, how they're configured, really helps us lower the time to resolve issues," Plumley said.
The case is a specific argument for IT-side observability applied to OT. Dartmouth runs a converged IT/OT network, which accelerates the maturity of their OT device management capabilities.
Register for the next Nexus Labs event.
Sign up for the newsletter to get 5 stories like this per week:
This is a great piece!
I agree.