The Most Overlooked Tool in BAS? Your Graphics: If They Don’t Match the Field, You’ve Got a Cartoon
- Alex Khachaturian
- Oct 8
- 4 min read
Updated: Oct 21
Promise: Graphics are the bridge between your BAS front end and the real world. If they don’t match what’s in the field, they’re not helping you, they’re lying to you.
TL;DR
A BAS graphic that doesn’t match the field is worse than useless, it’s misleading.
Updating graphics is one of the fastest credibility wins with customers and IT.
Graphics aren’t just “pretty pictures.” They’re the first troubleshooting tool.
Key Takeaways
Graphics drive technician speed, trust, and clarity in the field.
A mismatched graphic destroys confidence, from operators, IT, and your own team.
Small improvements (naming, color standards, live point verification) have big ROI.
Quick Links
Next Read
The Cartoon BAS
I walked into a site once where the operator was red in the face, yelling that nothing worked. His BAS showed the supply fan running, VAVs tracking, everything looking pristine. Only problem? The fan belts were shredded and the AHU was dead silent.
The screen said “normal.” The room said “broken.”
That’s when it hit me: a BAS graphic that doesn’t match the field isn’t a tool, it’s a cartoon. And cartoons don’t keep people comfortable, don’t fix equipment, and don’t win customer trust. They make you laugh and question reality!
I’ve been in countless sites since then, and I can spot within 30 seconds whether the graphics are taken seriously. You know the sites, clip-art boxes, VAVs all copy-pasted, no live status, points in the wrong place. The graphics are lying, and everyone knows it.
Quick Win: One BAS Graphic That Earns Respect
If you’re short on time, don’t start with the whole site. Start with the main AHU graphic.
Here’s why:
Operators live on that screen.
Technicians troubleshoot from it.
Customers judge you by it.
Spend an extra hour cleaning it up, make sure every fan status is tied to a real input, temperatures are labeled and correct, and alarms match the sequences. It’s the fastest way to flip the perception of your system from “toy” to “tool.”
Recommended Gear
Step-by-Step Playbook: Building Graphics That Don’t Lie
1. Start with the Field, Not the Software
Never build graphics in the office. Walk the site. Take photos of equipment. Document the tag names, control points, and wiring.
2. Standardize Your Naming
Operators should be able to move from AHU-1 to AHU-7 and know exactly where to look. Stick to a consistent naming convention (supply fan = SF, return fan = RF, mixed air damper = MAD).
3. Map Every Point to Reality
Every sensor, every alarm, every command should be verified against the field. If you’ve got a static text box that says “fan running” with no input tied to it, you’ve just lied to the operator.
4. Keep It Clean
No one needs a graphic that looks like a CAD submittal drawing. Keep it clean, with logical airflow, color coding (blue for cold, red for hot), and just enough info for quick troubleshooting.
5. Add Operator Value
Build shortcuts: links to trend logs, schedules, overrides. A good graphic isn’t just a picture, it’s a dashboard.
6. Test, Test, Test
Before handoff, sit with the operator. Walk through point by point. Does it match reality? Does it make sense to someone who wasn’t on-site for the install?
Troubleshooting Bad Graphics
Symptom: Operator says the BAS “never works.”
Cause: The graphics don’t match the field, so trust is gone.
Fix: Audit the top 10 graphics and clean up naming, points, and live values.
Symptom: Techs spend too long finding issues.
Cause: Graphics don’t show live faults or are missing common points.
Fix: Add alarms, color changes, and key performance indicators.
Symptom: Customer refuses to pay for graphics updates.
Cause: They see graphics as “decoration.”
Fix: Demonstrate ROI: a $500 update saves thousands in troubleshooting time.
FAQ
Q: Why do graphics get ignored during projects?
A: Because they’re seen as “finish work.” But they’re what the customer sees every day.
Q: How often should graphics be updated?
A: At every major service event. If equipment changes, graphics must change too.
Q: Who owns the graphics, contractor or customer?
A: The customer owns the system, but contractors are responsible for leaving it accurate.
Q: Can AI build graphics automatically?
A: Not yet. Tools are coming, but nothing beats a tech who’s walked the site.
Q: What’s the biggest mistake in graphics?
A: Using templates without verifying live points.
Q: How do you get customers to pay for updates?
A: Show them side-by-side, the cartoon versus the real. Once they see the gap, they’ll pay.
Field Checklist
Walk every major piece of equipment.
Verify sensor/actuator points against live values.
Standardize naming and colors.
Add alarm tie-ins where needed.
Test graphics with an operator before sign-off.
Results & ROI
When your graphics match the field:
Technicians troubleshoot 30–50% faster.
Operators stop bypassing the BAS and start trusting it.
Customers see value and justify premium service contracts.
Your credibility as a controls tech skyrockets.
Wrap-Up
Your graphics are your reputation. If they don’t match the field, you’ve just handed the operator a cartoon and called it a tool. Don’t be that tech. Take the extra time, verify the points, and build graphics that tell the truth.
For me, every time I see a cartoon BAS, I remember that AHU with shredded belts. The screen lied. The room told the truth. I’d rather trust the room.
Comments