.png)
How CBRE and Microsoft Uncovered a Hidden Network Bottleneck That Broke Schedules Across an 80-Building Campus
This NexusCon 2025 presentation walks through a real troubleshooting story from a large global tech headquarters campus with 80+ buildings and 50,000 occupants. Ping Yao, CTO at Optigo Networks, and April Yi, Director of Digital Engineering at CBRE, explain how a months-long pattern of failed schedules and comfort escalations couldnāt be solved by the BAS vendorsābecause the root cause wasnāt in the BAS at all.
With four BMS platforms, multiple Iconics servers, and a complex campus network, the team shifted focus to the OT network layer to understand what was actually breaking. What they found changed how the client thinks about reliability, comfort, and data visibility going forward.
Behind the paywall, youāll see exactly how CBRE and Optigo traced intermittent schedule failures to a single overloaded BACnet router caused by cross-campus traffic patterns. The team shares what surprised them once they could see network-level BACnet traffic, why traditional BAS troubleshooting kept pointing to the wrong systems, and how a relatively simple server reassignment eliminated the issue.
They also quantify the impact: nearly 118,000 hours of missed runtime across assets, with 38% of equipment failing to turn on for more than half of scheduled days. If youāre an FM, OT, or energy leader dealing with ārandomā failures, comfort complaints, or unexplained overrides, this recording shows why the network layer is often the missing pieceāand how to operationalize that insight without chasing dashboards or silver bullets.
Watch the full recording inside Nexus Pro ā
This NexusCon 2025 presentation walks through a real troubleshooting story from a large global tech headquarters campus with 80+ buildings and 50,000 occupants. Ping Yao, CTO at Optigo Networks, and April Yi, Director of Digital Engineering at CBRE, explain how a months-long pattern of failed schedules and comfort escalations couldnāt be solved by the BAS vendorsābecause the root cause wasnāt in the BAS at all.
With four BMS platforms, multiple Iconics servers, and a complex campus network, the team shifted focus to the OT network layer to understand what was actually breaking. What they found changed how the client thinks about reliability, comfort, and data visibility going forward.
Behind the paywall, youāll see exactly how CBRE and Optigo traced intermittent schedule failures to a single overloaded BACnet router caused by cross-campus traffic patterns. The team shares what surprised them once they could see network-level BACnet traffic, why traditional BAS troubleshooting kept pointing to the wrong systems, and how a relatively simple server reassignment eliminated the issue.
They also quantify the impact: nearly 118,000 hours of missed runtime across assets, with 38% of equipment failing to turn on for more than half of scheduled days. If youāre an FM, OT, or energy leader dealing with ārandomā failures, comfort complaints, or unexplained overrides, this recording shows why the network layer is often the missing pieceāand how to operationalize that insight without chasing dashboards or silver bullets.
Watch the full recording inside Nexus Pro ā
This is a great piece!
I agree.