Who I Am
The Background
I started my career as an Air Force machinist and welder — working rocket propulsion R&D at Edwards AFB and combat aircraft maintenance at Kadena AB. That's where I learned what a maintenance backlog actually feels like when a mission is on the line. Nobody in that environment had patience for systems that didn't work or data that couldn't be trusted.
When I transitioned out of the military, I brought that perspective into the civilian world. Maximo became my domain because it's where maintenance operations and information systems meet — and most organizations were getting both wrong. I've spent 20+ years fixing that across government, defense, pharma, utilities, and transit.
"My goal isn't to implement software. It's to build a maintenance operation that actually runs on it — and keeps running after I leave."
I've worked at every level of this discipline: as a product owner at Battelle managing $145M in DoD assets, as a program manager at WMATA running engineering and supply chain systems for Washington Metro, as an eminence hire at Deloitte building their Maximo practice, and now as the principal of my own SDVOSB practice.
Along the way I wrote Work Execution Management in Maximo (ReliabilityWeb, 2024) — the practitioner's guide I wanted to exist when I was starting out. I've spoken at MaximoWorld, delivered workshops, and built the IMPACT System to give organizations a repeatable methodology for Maximo success. The 725-KPI reference library came out of the same frustration: nobody had documented this at that depth, so I did it.
I'm based in Norfolk, Virginia. I work remotely and on-site. I'm direct, I take positions, and I'll tell you when your Maximo is broken and exactly what it's going to take to fix it.
