Delta/JLL at LaGuardia couldn’t standardize alarms and trends across two BMS stacks—so they used an overlay to enforce one monitoring workflow
Delta Air Lines and JLL stopped trying to standardize alarms inside two different BMS platforms at LaGuardia Airport’s Terminal C—and instead enforced one operating workflow above them.
Terminal C spans four concourses and a headhouse, with more than 30 systems across HVAC, power, and airport-specific assets like jet bridges and queue monitoring. Even with “only two” BMS vendors, JLL found that alarm setup, naming, routing, and response varied by contract and front end.
“The issue wasn’t, ‘Can the BMS alarm?’” said Kate Stelzel, Technology Operations Manager at JLL. “It was the fact that we weren’t able to standardize that across the airport.”
Rather than force alignment through two vendor workflows, the team centralized alarming and trending in a Mitsubishi Electric Iconics Digital Solutions-based data layer they call an “information broker.” Both BMS stacks feed into it, where alarms are normalized and routed through one process.
“If we wanted to do this in the BMS, we would’ve had two different workflows,” Stelzel said. “The alarms would look different, and it was just going to confuse the team.”
The shift wasn’t just technical. Multiple organizations—JLL, Delta, the Port Authority, and some vendors—now work from the same operational view.
“It’s not just bringing systems into one place,” Stelzel said. “It’s bringing people into the same system.”
The result: JLL uses the platform as its day-to-day operating tool, not a wall dashboard. The lesson for large, multi-vendor sites is straightforward—if contracts and front ends prevent standardization, owners may need to enforce it elsewhere.
Learn more:
- Watch the full presentation from NexusCon 2025
- Sign up for the Nexus Labs newsletter to get five similar stories for owners each Wednesday
Delta Air Lines and JLL stopped trying to standardize alarms inside two different BMS platforms at LaGuardia Airport’s Terminal C—and instead enforced one operating workflow above them.
Terminal C spans four concourses and a headhouse, with more than 30 systems across HVAC, power, and airport-specific assets like jet bridges and queue monitoring. Even with “only two” BMS vendors, JLL found that alarm setup, naming, routing, and response varied by contract and front end.
“The issue wasn’t, ‘Can the BMS alarm?’” said Kate Stelzel, Technology Operations Manager at JLL. “It was the fact that we weren’t able to standardize that across the airport.”
Rather than force alignment through two vendor workflows, the team centralized alarming and trending in a Mitsubishi Electric Iconics Digital Solutions-based data layer they call an “information broker.” Both BMS stacks feed into it, where alarms are normalized and routed through one process.
“If we wanted to do this in the BMS, we would’ve had two different workflows,” Stelzel said. “The alarms would look different, and it was just going to confuse the team.”
The shift wasn’t just technical. Multiple organizations—JLL, Delta, the Port Authority, and some vendors—now work from the same operational view.
“It’s not just bringing systems into one place,” Stelzel said. “It’s bringing people into the same system.”
The result: JLL uses the platform as its day-to-day operating tool, not a wall dashboard. The lesson for large, multi-vendor sites is straightforward—if contracts and front ends prevent standardization, owners may need to enforce it elsewhere.
Learn more:
- Watch the full presentation from NexusCon 2025
- Sign up for the Nexus Labs newsletter to get five similar stories for owners each Wednesday


.png)

This is a great piece!
I agree.