RM571665Dynamics 365 Field Service: Plan asset maintenance using time, actual usage, and service sequences
Summary
Business value
Description
Business value
Organizations can maintain assets according to how the equipment ages, how much it is actually used, and which service activities have already been completed. A flexible maintenance schedule helps avoid servicing lightly used equipment too often while reducing the risk that heavily used equipment operates beyond its required maintenance interval.
Usage-based schedules connect maintenance directly to meter readings recorded for the individual asset. This allows work to be driven by actual operating hours, mileage, cycles, production counts, or another tracked measure rather than by an estimated calendar interval alone. Combining scheduling methods in one plan supports more consistent execution of manufacturer guidance, internal reliability standards, and contractual maintenance commitments.
Feature detail
Define maintenance activities against the actual usage of an asset by specifying recurring service intervals on its meter. For example, require an oil change after every 150 operating hours or an inspection after every configured number of miles, cycles, or units produced. As new readings are recorded, the asset's accumulated usage determines when the next maintenance interval is reached.
Define other activities using calendar recurrence or combine calendar and usage criteria in one rule. For combined criteria, the plan initiates maintenance when either the elapsed-time threshold or the actual-usage threshold occurs first.
Create sequential maintenance programs in which different activities become due at different points in the maintenance cycle. For example, a plan can progress through inspections, minor services, major services, and overhauls rather than repeating the same activity at every interval.
The maintenance plan continuously evaluates its configured intervals against the asset's dates, recorded meter usage, and completed maintenance sequence to determine which activity is due next. When the applicable threshold is reached, the plan produces the maintenance requirement that drives downstream work-order generation. This gives planners one place to manage calendar-based, actual-usage-based, whichever-comes-first, and multi-step maintenance strategies.
GA date: February CY2027
Preview date: October CY2026