NexusCast #2: How DFW Built Validation and Reporting into Their CBM Program
Before their CBM program, DFW Airport's QA team ran entirely on reactive maintenance, fielding calls when something broke. DFW was taking on additional terminal space and equipment scope with minimal staff increase, so a newly implemented CBM program had to help the same team cover more ground. Hannah Baker walks through how they got there, starting with the enablers: fault signals enriched with root cause diagnostics and recommended actions so non-specialists could confidently triage, CMMS integration so condition-based work orders landed alongside reactive and PM work in one system, and filters by location, equipment scope, and cost impact to turn 3,000 faults into a manageable daily list. But the real story is what made the program stick. A weekly meeting rhythm that started as software training and evolved into collaborative fault review sessions where the team gradually built enough confidence to graduate recurring issues into fully automated work orders. They measure their success through a single KPI that validates the entire program.
Pro members can watch the full recording below. Not a NexusPro Member? Join today.
Before their CBM program, DFW Airport's QA team ran entirely on reactive maintenance, fielding calls when something broke. DFW was taking on additional terminal space and equipment scope with minimal staff increase, so a newly implemented CBM program had to help the same team cover more ground. Hannah Baker walks through how they got there, starting with the enablers: fault signals enriched with root cause diagnostics and recommended actions so non-specialists could confidently triage, CMMS integration so condition-based work orders landed alongside reactive and PM work in one system, and filters by location, equipment scope, and cost impact to turn 3,000 faults into a manageable daily list. But the real story is what made the program stick. A weekly meeting rhythm that started as software training and evolved into collaborative fault review sessions where the team gradually built enough confidence to graduate recurring issues into fully automated work orders. They measure their success through a single KPI that validates the entire program.
Pro members can watch the full recording below. Not a NexusPro Member? Join today.


.webp)

This is a great piece!
I agree.