Hot take:   Rushing a submittal out the door isn’t productivity.  It’s cost shifting.  In building automation, we sometimes celebrate speed like it’s the ultimate KPI.  “Just get it submitted.”  “We’ll clean it up later.”  “We’ll figure it out in the field.”  But “later” always shows up.  And it usually shows up wearing a hard hat.  As the Lead Project Engineer at XL Automation Solutions, I’ve seen the difference one early decision makes:  Spend an extra 5% of effort fully de

Why market demand is compounding faster than we can build techs -- and what the industry can do about it. If you work in Building Automation and Controls, you’ve lived this cycle: Demand accelerates. Experienced BAS technicians get harder to find. Companies hire greener talent and build internships/apprenticeships to grow capability. Right when a tech becomes productive, the market offers a small bump and they jump -- leaving the training company holding the bill. I’m not wr

The XL Automation Philosophy of Building Automation --- Part 1 The Low Bid Is Actually the Most Expensive Option A Building Automation System is often treated like nothing more than a project deliverable. It gets designed. It gets installed. It gets commissioned. It gets turned over. And then… everyone moves on. But the building doesn’t. Ten years from now, that same BAS will still be there --- running comfort, energy, alarms, equipment life, and daily operations. What rarely

Q: Is the extra time to group our histories worth it? A: YES! With ungrouped histories we have to scroll through hundreds of history entries to get to the one we want and it’s easy to lose track of where we are in the tree. How long does it take to find the same one during grouped histories? 25 seconds versus 15! 10 seconds doesn’t seem like much, but consider, have you ever closed out of an app or web page because you have to spend 10 seconds watching an ad? 10 seconds can b

In building automation, the “design intent” is our roadmap — the ideal vision of how a system should perform to meet the comfort, efficiency, and operational goals of the customer. But once we get on site, reality often presents unforeseen challenges that require adaptability, technical insight, and clear communication between team members and other trades. From field conditions to unanticipated architectural constraints, every project teaches us something new. What separates

If you’ve spent any time in building automation, you start to hear the same phrases over and over again. They’re almost never said with bad intent. Most of the time, it’s good people trying to keep a project moving. But over the years, I’ve learned that certain sentences are quiet warning lights. They usually mean we’re about to trade clarity now for pain later. And that pain shows up as rework, confusion, long nights, and strained teams. Here are five I hear a lot — and what

Integration has become a buzzword. Most of the time, “integrated” just means someone got it talking once. But here’s what rarely gets said out loud: integration without accountability isn’t integration. It’s a collection of connections that someone hopes will keep working. And watch-out: if your integration plan is “the vendors will coordinate,” that’s a problem. Because once the first change order hits, a device gets swapped, or a firmware update rolls through, the mapping