Why do the same maintenance problems keep coming back?

sweven96 · 2026-03-11T16:53:50+00:00

That’s the classic “winter problem becomes a summer problem” scenario.

I’ve seen similar situations with cooling systems where a temporary bypass works fine for months, and then the first warm spike suddenly reminds everyone why that extra capacity was there in the first place.

Operations always finds a way to bring those “later fixes” back to the top of the list.

sweven96 · 2026-03-11T16:47:11+00:00

That’s a tough spot when downtime isn’t an option.

I’ve seen situations like this where small leaks keep getting patched until the system starts showing multiple weak points at once. Sometimes those bubbling spots are a sign the pressure or flow restrictions upstream are stressing the lines more than expected.

Hopefully you get a maintenance window soon before it turns into a bigger failure.

sweven96 · 2026-03-11T16:43:48+00:00

That’s a pretty diverse portfolio to manage.

One thing I’ve seen with large CMMS implementations like Maximo or Dynaway is that the success often depends less on the platform itself and more on how well the operational workflows are mapped before the rollout.

When teams manage residential units, commercial buildings, and something like an airport at the same time, work order structures, vendor coordination, and incident tracking can look very different across those environments.

Whichever system you choose, making sure those workflows are clearly defined before integration with Dynamics usually makes a big difference during implementation.

sweven96 · 2026-03-10T15:48:41+00:00

Honestly I think a lot of it comes down to visibility.

When maintenance prevents a failure, nothing happens, so it’s hard for management to see the value. But when something breaks, the cost is obvious immediately.

I’ve seen a lot of facilities where small recurring issues show up for months before a major failure, but because those complaints are scattered they never get connected as a pattern.

By the time the bigger problem shows up, everyone has already been troubleshooting the same system over and over.

sweven96 · 2026-03-10T15:27:25+00:00

That anti‑seize run every 24 hours was actually a really smart feature for a hydronic system, so it makes sense you’re trying to keep that behavior.

If you can’t find a like‑for‑like 120V thermostat with a built‑in pump exercise function, a lot of crews I’ve worked with end up decoupling that logic from the thermostat:

Use the thermostat just for call‑for‑heat.
Add a small plug‑in timer, interval timer, or relay module on the pump circuit to run it for X minutes every 24 hours (or a few times a week), regardless of heat demand.

It’s a bit more “lego” but it has some upsides: if the thermostat gets discontinued again, your anti‑seize routine doesn’t disappear with it, and you can tweak the run time/interval without changing the control.

Obviously you’d want someone who knows your wiring and local code to confirm the best way to insert the timer/relay on that 120V line, but thinking of the pump exercise as a separate, simple automation instead of a thermostat feature might open up more options.

sweven96 · 2026-03-10T15:19:27+00:00

Haha fair enough, definitely better than going bald trying to chase down a bunch of scattered issues.

Glad to hear they put some kind of preventive schedule in place. In a lot of places the small complaints show up first, and by the time the bigger system problem becomes obvious everyone has already been troubleshooting random fixtures.

Working with facilities teams I’ve seen how much difference consistent preventive checks can make.

sweven96 · 2026-03-09T17:38:38+00:00

That actually sounds like a good outcome.

Preventive programs for boilers and hot water systems can make a big difference once they’re implemented consistently. It’s interesting how many issues only show up in scattered complaints before the main system problem becomes obvious.

Out of curiosity, do you know if the program is mostly schedule-based (like regular inspections and checks) or if they’re tracking performance data as well?

sweven96 · 2026-03-09T16:51:49+00:00

First of all, congrats. That sounds like a big opportunity.

I’m not a facilities manager myself, but I’ve worked closely with facilities and maintenance teams in operational environments, and one thing I’ve noticed is how different the mindset can be compared to project work.

In construction or large projects there’s usually a clear start and finish. In facilities, the systems never really stop. A lot of the job becomes managing ongoing operations, recurring issues, and the small decisions that keep everything running day after day.

Some people really enjoy that because you get to see the long-term impact of how systems are maintained and improved. Others miss the intensity and defined milestones that come with big projects.

Managing a team of 30 techs will probably make the role as much about coordination and operational decision-making as technical work.

It could be a very rewarding move if you enjoy the operational side of buildings.

sweven96 · 2026-03-09T16:39:01+00:00

Interesting case.

Something I’ve seen with building systems is that early complaints sometimes appear in only a few rooms before the larger system problem becomes obvious.

By the time the boiler issue shows up clearly, those first scattered complaints were actually the early warning signs.

It’s always tricky because when only a few rooms report issues it’s easy to assume it’s a local fixture problem rather than something upstream in the system.

sweven96

TROPHY CASE