Typical Problems I Help Solve

A project hands over to operations with a register built from a BIM model — thousands of elements that no maintenance team can use, with no hierarchy that reflects how things are actually maintained. The CMMS was configured by IT before operations had any say, so work orders don't match the asset structure, and nobody trusts the data. 

Maintenance plans exist as documents — PDFs in a shared drive — but they've never been loaded into the system. So inspections get missed, reactive work dominates, and when something fails, the history isn't there to learn from. Spare parts sit unreconciled in the warehouse, with no reliable link between what was used, what was ordered, and what a job actually cost. 

Condition monitoring systems generate data that nobody knows how to connect to the asset information system — so it sits in a silo, useful to engineers but invisible to the people planning maintenance. And when staff turn over, the knowledge walks out the door because the processes were never documented and the team was never properly trained.

None of these are isolated problems. They compound. And they all trace back to the same root cause: asset information that was set up for delivery, not for operations.