Editor's Note
Last week's issue said predictive maintenance needs appliance records most operators don't have. A reader answered with a working method for capturing that data without it becoming a chore nobody does.
A reader's rule beat the product pitch
The comment came from someone who works with US property management companies on the operations side. Here's the exchange, lightly edited for length.
Install dates and model numbers usually exist somewhere. They sit in invoices and receipts, not on the unit record where anyone could find them fast. Every replacement got paid for at some point, which means a paper trail exists even when a system doesn't.
Backfilling five years of that is a project nobody finishes. The better target is capturing it going forward, at the one moment someone already has the information in hand.
Capture at the close
Whoever closes a work order records the model, serial, and install date right then. That's the only point in the process where a person is standing in front of the unit with the part number visible.
Two years of that habit produces something a five-year backfill never would, a dataset built entirely from equipment that's actually been touched. That's also the equipment most likely to need attention again.
Where most systems break it
Making every field required on every ticket sounds thorough. In practice it backfires.
A reset breaker doesn't need a model number. Require one anyway, and the field still gets filled, just with "N/A" typed in to clear the form. The record looks complete. Nobody checks it again because nothing flags it.
The fix is narrower than it sounds: require the detail only where it holds up, replacements and major repairs. Leave routine tickets optional. One operator who tried this watched optional fields get filled for about three weeks before people drifted away from them, roughly how long a habit needs reinforcement before it sticks.
Why this beats waiting for better software
Every predictive tool, ForVue included, runs on exactly this kind of record. They assume the collection problem is already solved.
A rule enforced at the moment of closing a ticket costs nothing and needs no new software. It also comes from someone who actually does the work, which counts for something most vendor claims don't have behind them.
Did You Know?
A field required everywhere doesn't get more complete. It gets gamed. The moment a mandatory field costs more effort than it's worth, people fill it with whatever clears the screen fastest, and the record stops meaning what it says.
Until next week,
Tomas