A Field Technician Drove 90 Minutes to a Site — With the Wrong Parts.

Monday, 7:15 AM. A maintenance work order is dispatched: "Replace filter assembly, Unit 7, Building C." The technician loads the parts listed on the work order, drives 90 minutes to the customer site, and opens the unit.

Wrong filter. The unit was upgraded six months ago, and the new model uses a completely different filter assembly. The asset record in the CMDB still shows the old configuration. The parts catalog carries both SKUs. The work order system pulled the one linked to the outdated asset record, because that's all it had.

The technician calls dispatch. Dispatch calls the warehouse. The warehouse ships the correct part. It arrives the next day. The technician drives 90 minutes back. The customer has been without the unit for 36 hours.

Total cost: two site visits, one overnight shipment, one unhappy customer, and 7 hours of technician time, all for a $40 filter.

• The asset configuration and the parts catalog aren't linked. When the unit was upgraded, the CMDB wasn't updated to reflect the new part requirements.
• The work order system can't verify parts against actual asset state. It trusts whatever the CMDB says, even when the CMDB is wrong.
• The warehouse shows "in stock" for the correct part, but the work order never asked for it, because the systems don't cross-reference.
• Field technicians become the error detection layer. They discover problems on-site that should have been caught before dispatch ever happened.

What if the work order, the asset configuration, the parts catalog, and the warehouse inventory all lived on one connected data model?

When a work order is created, the system cross-references the asset's current configuration, not the one from three years ago. It verifies part availability against the correct SKU. If the part isn't in stock, the work order holds until it is. The technician never leaves the warehouse with the wrong filter, because the system won't let the work order dispatch with a mismatch in the first place.

The 90-minute drive wasn't the failure. The failure happened days earlier, when a work order got created against an asset record that no longer reflected reality. One connected model eliminates the gap, and the wasted trip along with it.