.webp)
NexusCast #2: Integrating CBM With CMMS... Without Flooding Work Orders
The University of Iowa's FDD system generates over 3,500 faults a day. Nobody is fixing 3,500 things. So how do you keep that from becoming just another ignored backlog? Brad Dameron and Katie Rossman walk through the workflow they built over a decade of running this program, starting with two dedicated people who prioritize faults by energy savings, match work to the right skillset, and monitor each shop's current capacity before sending anything out. They sort every fault into one of three buckets: complex issues the Asset Optimization Team handles internally, programming changes routed to the controls shop, and mechanical fixes sent to frontline crews as "slam dunks" with clear diagnostics attached. The key design decision: condition-based work orders enter the CMMS looking exactly like any other work order, framed as planned work rather than reactive work, which is how they got buy-in from technicians. They close the loop with a Friday meeting across all five maintenance shops and a bidirectional integration between the FDD platform and CMMS that syncs work order notes back to the original fault. Katie adds the trust angle: if you're going to remove PM tasks because you have fault detection coverage, the maintenance team needs to see that faults actually get prioritized and executed, or the whole program loses credibility.
Pro members can watch the full recording below. Not a NexusPro Member? Join today.
The University of Iowa's FDD system generates over 3,500 faults a day. Nobody is fixing 3,500 things. So how do you keep that from becoming just another ignored backlog? Brad Dameron and Katie Rossman walk through the workflow they built over a decade of running this program, starting with two dedicated people who prioritize faults by energy savings, match work to the right skillset, and monitor each shop's current capacity before sending anything out. They sort every fault into one of three buckets: complex issues the Asset Optimization Team handles internally, programming changes routed to the controls shop, and mechanical fixes sent to frontline crews as "slam dunks" with clear diagnostics attached. The key design decision: condition-based work orders enter the CMMS looking exactly like any other work order, framed as planned work rather than reactive work, which is how they got buy-in from technicians. They close the loop with a Friday meeting across all five maintenance shops and a bidirectional integration between the FDD platform and CMMS that syncs work order notes back to the original fault. Katie adds the trust angle: if you're going to remove PM tasks because you have fault detection coverage, the maintenance team needs to see that faults actually get prioritized and executed, or the whole program loses credibility.
Pro members can watch the full recording below. Not a NexusPro Member? Join today.
This is a great piece!
I agree.