It was a Tuesday in January 2024, and I was staring at a wall in our main conference room. Not the wall itself—the thermostat on it. A digital screen that looked like it was speaking a language I didn't learn. The sun, a snowflake, a fan icon that seemed to be doing jumping jacks... our Johnson Controls thermostat symbols were suddenly a mystery to everyone in the office.
I'm the office administrator for a 150-person engineering firm. I manage all the facility service purchasing—roughly $350,000 annually across maybe 20 vendors. HVAC, cleaning, supplies, you name it. If it keeps the building running, it crosses my desk. And on that Tuesday, the building was running cold. Or hot. Actually, it was one of those days where the system couldn't make up its mind.
“The AC is set to ‘fridge’ again,” one of our engineers joked, pointing at the screen. But he wasn't wrong to complain. The meeting we had scheduled was about to be a sweat-fest.
The moment it all clicked (or didn't)
Like most facilities people, I thought I had the basics down. Set the temperature, pick a mode (heat, cool, fan), and move on. But our building had been retrofitted with a newer Johnson Controls system about three years before I took over purchasing in 2020. The old manual dials were gone. In their place were these sleek digital thermostats with a whole set of symbols I'd never seen before.
There's this misconception that a thermostat is a thermostat. But I didn't fully understand the complexity until that Tuesday. The snowflake symbol wasn't just ‘cool’—it meant continuous cooling mode. The sun symbol meant continuous heating. The fan icon with the word 'Auto' beneath it? That's not just ‘auto fan speed.’ It means the fan only runs when the system is actively heating or cooling. If you wanted constant air circulation, you needed to select the fan symbol with two wavy lines, which is the 'On' mode.
I felt like an idiot. Three years managing this building, and I'd been accidentally flipping between heating and cooling modes without understanding the nuances. No wonder the energy bills were spiking.
“It's tempting to think you can just set a temperature and walk away. But modern programmable logic, especially with building automation systems like Metasys, requires you to understand zones, schedules, and even outdoor air dampers.”
The turning point: a cold call and a hot mess
After the conference room debacle, I decided we needed to standardize. The problem was, we had a mix of equipment. The conference room had one of the newer touchscreen models. The break room still used a classic battery-powered round thermostat from a previous vendor. Our server room—don't get me started—had a digital controller that looked like it belonged on a spaceship from 1995.
I called up our usual HVAC service contractor. “Can you just come in and fix it?” I asked, maybe a little desperate.
“Well,” the dispatcher said, “we can schedule you for next Thursday.”
Next Thursday? It was only Tuesday. I had a board meeting the next afternoon. That's when I made the classic rookie mistake: I tried to fix it myself. In my first year of managing this, I made the classic tinkering error: assumed I could just Google the manual and adjust an internal setting. Cost me a $200 service call the next day when I accidentally triggered the building's emergency shutdown protocol.
OK, fine. I admitted defeat. But the experience sparked a bigger question for me. Weren't these systems supposed to simplify things? Why were there so many different symbols and interfaces across our own building?
The solution wasn't a new thermostat (at first)
Instead of just fixing that one room, I decided to tackle the whole problem. I started by creating a one-page cheat sheet. I took photos of every thermostat in the building, labeled them by location, and made a simple guide. “If this symbol is flashing, it means X.” “To switch from heat to cool (without causing a system war), press this sequence.”
I laminated it and posted it next to each unit.
It helped. A little. But I knew the real issue was that our system was a patchwork of different generations of technology. We were using a johnson controls variable speed drive on the main air handler that was brilliant at balancing airflow, but the actual user interface on the wall was still from the 'dumb' era. The brains were smart, but the mouths (the thermostats) weren't keeping up.
That's when I started looking into upgrading the controllers themselves. We didn't need a full building automation rip-and-replace. We just needed modern, consistent user interfaces that could communicate properly with the VFDs and chillers already in place.
The vendor who didn't laugh at my budget
I reached out to three different vendors. One was a national giant who basically laughed when I said our budget was around $15,000 for the upgrade. “We don't really do projects that size,” they said. The second vendor quoted me for a full Metasys upgrade—which would have been nice, but it was $45,000 and would have required shutting down the building for a week. Not an option.
The third vendor was a smaller local integrator who specialized in Johnson Controls equipment. They didn't make me feel small for my $15,000 budget. They came in, surveyed the building, and said, “You know what? You don't need all new controllers. You just need better endpoints and a gateway to unify them.”
When I was starting out in this role, the vendors who treated my $15,000 order seriously (which to some is a small project) are the ones I still call for smaller $2,000 repair jobs. It's about trust, not just transaction size.
What we actually did
The solution was elegant. We replaced the wall controllers in the main zones with modern digital thermostats that had clear, consistent symbols. We installed a small network gateway that let the thermostats talk to our existing VFDs and the central chiller plant. The whole project took two days, cost $12,500, and the biggest win was that I could finally standardize the cheat sheet. Every thermostat now had the same symbols for the same functions.
Our utility bill for July that year was 14% lower than the previous July. Not entirely because of the thermostats—we'd also had the ducts cleaned and upgraded the insulation in the server room. But the system was actually being used correctly now. That's a big deal.
Lessons from the admin's chair
So what did I learn that might help you?
- Know your symbols. Whether it's a Johnson Controls thermostat or a competitor's device, understand what those little icons actually mean. 'Auto' on the fan doesn't always mean 'on automatically.' Sometimes it means 'off unless needed.'
- Don't try to fix it yourself in a panic. A service call costs less than accidentally triggering a fire suppression system. Trust me.
- Standardize the user interface. If you have a high-end variable speed drive managing the airflow, don't let the user control it with a thermostat from 2010. The brain is only as good as the interface.
- Vendors matter more than price. The vendor who treated my small project with respect is now my go-to for everything. The big company who laughed at my budget? They call me every quarter trying to sell me a chiller. I don't even return the call.
I know there are bigger, more complex problems out there. Data centers need far more sophisticated cooling than a 150-person engineering office. But the principles of a dehumidifier vs air purifier argument in your own home are the same: understand what the device is actually doing before you judge its performance. A dehumidifier doesn't clean the air, and an air purifier doesn't lower humidity. Know your tools.
Looking back, that confusing Tuesday was the best thing that could have happened. It forced me to actually learn the system, question my assumptions, and ultimately make the building more comfortable for everyone. Plus, I no longer feel dumb staring at a thermostat. Now I just feel empowered.
Prices as of January 2024; verify current rates with your local integrator. Regulatory information for building codes is for general guidance only.
