Cutting Over a New BMS

When I first thought about writing this, I hesitated, because the truth is, no two BMS cutovers are ever the same.

Every building has its own personality. Different plant, different history, different levels of documentation (or lack of it). And once you start a cutover, that’s it, you’re committed. There’s no easing into it and no clean way to step back out. You’re in, and you’re going through to completion.

I remember standing in front of a switchboard early on in my career, tools in hand, ready to start. Everything looked straightforward on paper. Controllers were specified, points were listed, and the job “made sense.” But the moment you open a panel, reality sets in.

You start noticing things.

Space isn’t quite what you expected. Cable entries are tighter. Someone’s added gear over the years. Suddenly that “simple controller swap” starts looking like you might need another enclosure, a bit of rework, maybe even extending field wiring.

These days, I don’t rush that part anymore. I take a step back and measure everything first. Panel space, clearances, cable paths. It’s not exciting work, but it’s the difference between a controlled job and one that starts drifting on you halfway through.

Once that physical side is understood, I usually sit down, either in the office or in the car before heading to site, and build out a spreadsheet.

Some guys prefer paper, but I’ve always found a spreadsheet forces clarity. It’s where everything in your head gets pushed into something structured. Inputs, outputs, controller allocations, plant areas, all laid out so you can actually see the job. Easy to edit.

It’s never perfect at that stage. You’re pulling information from old specs, bits of sales documentation, maybe some site notes. And to be fair, sales handovers aren’t always detailed, not because anyone’s doing the wrong thing, but because they’re working at a different level. The detail becomes your responsibility.

What you’re really doing in that moment is building a mental model of the system, making sure the controller in the roof actually serves the roof plant, not something three levels below. Making sure the I/O makes sense. Making sure the job is logical before it becomes physical.

Then you get to site.

There’s always that moment, standing there with new controllers, tools ready, the existing system still running, where you know the next move matters.

And before touching anything, I always do two things.

First, I work out how to keep the plant running. Manual modes, overrides, anything that gives you control while the system is in pieces. Because once you start disconnecting controllers, the building doesn’t stop needing air, or lights, or ventilation.

Second, I take photos. Lots of them.

Every terminal, every cable number, every angle I can get. Under the controller, inside the panel, wide shots and close-ups. It feels excessive at the time, but it never is. There’s always one photo, just one, that ends up saving you when something doesn’t quite line up later.

Before the first controller comes out, there’s also a conversation that has to happen with the building manager, sometimes with tenants.

You let them know what’s about to happen. That there may be interruptions. That you’re on site and available. It sounds simple, but it changes the whole tone of the job. People are far more understanding when they know what’s going on.

When it comes to the actual cutover, I’ve learned to start at the top, especially if there’s a JACE going in.

Get the head-end up first.

Bring points online as you go. Check them. Fix issues immediately. Don’t leave a trail of problems behind you thinking you’ll come back later, because later never goes as smoothly as you think it will.

You wire a controller, bring in the I/O, check the points, and confirm they’re reading correctly. If something’s off, you deal with it there and then. Nine times out of ten, it’s something small, a configuration tweak, a mapping issue, but catching it early keeps the job under control.

All the while, that spreadsheet you started becomes something else.

It turns into a live record of the job.

You’re updating it, adding notes, tracking what’s been done and what hasn’t. Sometimes deleting things, sometimes adding more detail than you thought you’d need. Saving new versions as you go. It’s not just documentation anymore, it’s your safety net.

Eventually, you reach that point where the hardware is in, the wiring is done, and it’s time to prove it.

Point by point.

You check that what the BMS is showing actually reflects reality. That when something turns on in the system, it turns on in the plant. That sensors are reading correctly. That outputs behave as expected.

You always find something. A point that doesn’t respond. A signal that’s not quite right. Something that needs further investigation. The key is not to ignore it, log it, understand it, deal with it properly.

And then, finally, you get to the part everyone enjoys.

Programming the control logic. Bringing the system to life properly. Building the graphics. Watching it all come together into something that not only works, but works well.

That’s the moment where a clean, well-managed cutover shows its value.

Because when it’s done right, it doesn’t feel chaotic. It feels controlled. Deliberate. Professional.

And that’s really what a good BMS cutover is, not just technical ability, but discipline in how you approach every step.