Mastering D365 Field Service: Asset Management

This is part 4 of UG Expert Scott LeFante’s Mastering D365 Field Service series, covering lessons learned from years of bumps and bruises. Check out the rest of the series:

• Part 1: Scheduling and Resource Optimization
• Part 2: Mobile Apps
• Part 3: Connected Field Service

Asset Management: The Unglamorous Foundation Everything Else Sits On

Nobody gets excited about asset records. Everybody suffers when they’re wrong. I’ve suffered through this one personally, which is why it gets its own section instead of a passing mention.

Assets, Hierarchies, and Why Your Data Model Matters More Than Your Dashboards

Customer assets in Field Service can be structured into parent-child hierarchies, which matters enormously once you’re dealing with anything more complex than a single standalone unit.

A commercial HVAC rooftop unit with sub-components. A fleet of connected devices under one site asset. A piece of industrial equipment with serialized parts. All of it depends on the hierarchy being modeled correctly from the start. I’ve been part of a project that tried to retrofit an asset hierarchy after two years of flat, disconnected asset records. I would not volunteer for that sprint again.

Along with the hierarchy, you want warranty data and maintenance history populated and current, not “It’s mostly current, we’ll clean it up later.” Preventive maintenance schedules generate batches of future work, and those batches feed straight into RSO or SOA for scheduling. If your asset records are stale, your preventive maintenance schedule is wrong, which means your scheduling engine is optimizing against fiction. Garbage in, confidently scheduled garbage out.

I’ve watched a scheduling engine make a genuinely excellent decision about a piece of equipment that had been removed a year earlier. It’s always fun (well not really), from an organizational and technician perspective, when they arrive at a customer site, only to find out that asset no longer exists.   

A Short, Slightly Obsessive Data Governance Checklist

I can’t write a section like this without turning it into a data governance checklist; that’s just who I am at this point:

• Every serviceable asset has a correct parent record if it belongs to a hierarchy, not just a name that implies one.
• Warranty start and end dates are populated, not left blank “because sales didn’t send them.”
• Preventive maintenance schedules are reviewed on a real cadence, not set once during implementation and then forgotten.
• Asset status (active, inactive, decommissioned) is actually maintained, so RSO isn’t trying to schedule a technician to visit a unit that was ripped out eighteen months ago.
• Someone, specifically, owns asset data quality. “Everyone” owning it means no one does. I’ve watched that exact phrase fail in three different organizations.