Preventive maintenance is scheduled work performed to reduce the chance of equipment failure, while predictive maintenance uses asset condition or performance signals to decide when maintenance is needed. Proactive maintenance is the broader practice of spotting potential problems early and acting before failure. In ServiceNow FSM, these approaches connect maintenance plans and schedules to Work Orders, technician capacity and customer service commitments.
Consider a company responsible for hundreds of machines at customer sites. Every six months, technicians inspect selected equipment. That is preventive maintenance.
Now imagine one machine starts behaving differently before its next scheduled visit. Its performance moves outside the expected range, so the service team investigates it early. That is proactive, condition-driven maintenance.
The important difference is what triggers the work.
What is preventive maintenance?
Preventive maintenance is planned service performed before an expected failure occurs.
A company might service a generator every six months, inspect an HVAC system quarterly or replace a component after a defined number of operating hours.
The idea is simple: accept a predictable maintenance cost rather than wait for an unpredictable breakdown.
In ServiceNow FSM, Planned Work Management supports recurring maintenance activities and planned schedules. Triggers can be based on duration, meter, condition or script. The resulting planned work can then become operational field work through Work Orders and Work Order Tasks.
What is proactive maintenance?
Proactive maintenance means identifying early signs of a problem and doing something about them before they become a failure.
ServiceNow describes proactive maintenance around comparing current asset functionality with an established baseline and resolving potential problems early.
For example, a machine may normally operate within a certain range. It has not failed, but its behaviour begins to move away from that baseline. The service team investigates before a breakdown occurs.
Preventive maintenance is one form of proactive maintenance, but proactive is the wider idea. It can include responding to trends, observations or early warning signs rather than simply following a calendar.
What is predictive maintenance?
Predictive maintenance uses asset condition, measurements or performance patterns to decide when intervention is needed.
Instead of asking, "When is this asset due?" the organisation asks, "Is there evidence that this asset needs attention now?"
ServiceNow supports condition- and meter-based triggers within Planned Work Management.
Predictive maintenance does not have to mean a complicated AI model. A useful threshold based on reliable asset data can be enough to start with.
How is reactive maintenance different?
Reactive maintenance begins after an asset fails or an immediate service problem is reported.
A customer reports that a machine has stopped working, a Case is created, the issue is assessed and a Work Order is dispatched. That is reactive or break-fix work.
| Maintenance approach | Trigger | Typical example |
|---|---|---|
| Reactive | Failure or urgent issue | Repair a machine after it stops |
| Preventive | Planned schedule or usage | Service an asset every six months |
| Proactive | Early warning or deviation | Investigate abnormal equipment behaviour |
| Predictive | Condition or performance signal | Trigger work after a defined threshold |
These approaches can coexist. The right mix depends on asset criticality, failure risk, service cost and the customer's agreement.
How does ServiceNow turn a maintenance plan into field work?
ServiceNow connects maintenance planning to execution through Planned Work Management, Work Orders and Work Order Tasks.
A typical flow is:
Asset → Maintenance Plan or Work Plan → Planned Work Schedule → planned occurrence → Work Order → Work Order Task → scheduling and dispatch → technician execution → completion
Work-order templates can also provide repeatable tasks, skill requirements and parts requirements for recurring work.
The important point is that creating a maintenance schedule is only the beginning. The organisation still has to fit that work into real technician capacity.
How do technician schedules, shifts and breaks affect maintenance?
A maintenance plan determines when work is due, but technician schedules determine when it can actually happen.
An eight-hour shift does not equal eight hours of available field capacity. Breaks, time off, existing jobs, travel and task duration all consume the day.
That matters when many assets become due together.
If 50 preventive jobs are generated for the same week, the maintenance plan has created demand. The dispatch operation still has to decide how that demand fits around working hours, skills, locations and higher-priority work.
Maintenance planning and workforce planning therefore need to work together.
What roles do Initiators, Qualifiers and Dispatchers play?
FSM separates the creation, preparation and assignment of work so that maintenance demand can move into field execution in a controlled way.
The Initiator can create a Work Order or start work from another supported process. The Qualifier checks whether the work contains enough information to be executed. The Dispatcher then assigns qualified Work Order Tasks to suitable field agents.
For planned maintenance, that gives each stage a clear purpose:
Plan the work → qualify the work → assign the work → execute the work.
This becomes especially useful when planned maintenance competes with urgent reactive requests.
What are dispatch groups and Dispatcher Workspace used for?
Dispatch groups provide an operational structure for field work, while Dispatcher Workspace supports the day-to-day assignment of tasks to field resources.
A maintenance task may require a particular skill, territory or team. Once qualified, the dispatcher can consider availability, location, workload and existing commitments.
A maintenance plan may create 100 tasks, but that does not mean 100 appointments can simply be booked. The dispatch process turns planned demand into workable assignments.
How does condition-based maintenance trigger work?
Condition-based maintenance starts when a defined condition becomes true rather than when a calendar date is reached.
ServiceNow Planned Work Management supports Condition and Meter-based triggers alongside duration and script-based scheduling.
That changes the process from:
"The asset is due for maintenance."
to:
"The asset has given us a reason to intervene."
It can make maintenance more targeted, but only if the condition and threshold are meaningful.
How does maintenance support contract-driven service revenue?
For many field-service organisations, maintenance is not just an engineering activity; it is part of the service a customer has purchased.
A customer may have a contract that includes quarterly inspections, annual servicing, a fixed number of service calls or a defined response commitment.
ServiceNow's customer contract and entitlement capabilities can represent coverage such as preventive maintenance, included service calls and rates that apply after an included limit.
That makes maintenance commercially important.
The business needs to know:
- Which assets are covered
- Which services are included
- How often maintenance is due
- When the agreement starts and ends
- How many service calls are included
- What happens when the entitlement is exhausted
A scheduled maintenance visit is therefore part of the customer's contracted service, not simply another Work Order.
Completion evidence matters as well. The organisation may need to show that the promised maintenance happened, what was inspected, what was found and what work was completed.
That information can support customer communication, contract compliance and renewal discussions.
Predictive maintenance creates another commercial question. Suppose a condition trigger identifies a failing component outside the normal maintenance schedule. The system should not simply assume that the repair is included.
The business may need to determine whether the work is covered by the existing entitlement, consumes an included service allowance, needs customer approval or becomes separately chargeable.
This is where the link between asset, maintenance plan, entitlement, Work Order and completion record becomes commercially valuable.
What would we actually do in a ServiceNow implementation?
We would design the maintenance strategy and the commercial rules before automating the field process.
First, classify the assets. Decide which need fixed preventive schedules, which can use meter or condition triggers and which require a combination.
Then define the contract side. What maintenance is included? Which assets are covered? What happens when a customer requests additional work?
Next, configure the operational flow using maintenance plans, schedules and Work Order Templates where repeatable tasks, skills or parts are required.
Finally, test the situations that usually expose gaps: a technician is unavailable, an emergency job takes priority, a condition trigger fires early, a required part is missing or the customer requests work outside the contract.
The goal is not simply to automate a maintenance calendar.
It is to connect what was promised to the customer with what actually happens in the field.
What business impact comes from getting maintenance right?
Good maintenance planning can reduce avoidable failures while making technician capacity and recurring service delivery more predictable.
Preventive maintenance creates planned demand instead of waiting for breakdowns.
Proactive and predictive approaches allow the organisation to act earlier when asset behaviour changes.
For service providers, there is an additional benefit: maintenance can represent recurring revenue that must actually be delivered.
The organisation therefore gains value in three areas: asset reliability, operational planning and contract fulfilment.
What is the honest limitation of preventive and predictive maintenance?
Automation cannot compensate for poor asset data, a bad maintenance strategy or insufficient field capacity.
A schedule can be perfectly configured and still create unnecessary work if the interval is wrong.
A condition trigger can also generate too many visits if the threshold is poorly designed.
And predictive maintenance is only as useful as the condition data behind it.
There is a commercial trade-off too. More maintenance is not automatically better. Excessive service consumes technician time and parts, while too little maintenance increases failure risk.
The goal is not maximum maintenance.
It is the right maintenance at the right time, within the customer's service commitment and the organisation's capacity.
Frequently asked questions
What is the difference between preventive, proactive and predictive maintenance?
Preventive maintenance follows a planned schedule. Proactive maintenance is the broader practice of identifying potential problems early. Predictive maintenance uses asset condition or performance information to decide when intervention is needed.
Is reactive maintenance the opposite of preventive maintenance?
Reactive maintenance responds after a failure or immediate issue, while preventive maintenance is performed before an expected failure. Both can exist in the same FSM operation.
Does ServiceNow support condition-based maintenance?
Yes. Planned Work Management supports condition- and meter-based triggers in addition to duration and script-based scheduling.
How does ServiceNow connect maintenance to field execution?
Maintenance plans and schedules can generate planned work that becomes Work Orders and Work Order Tasks. Work Order Templates can provide repeatable tasks, skills and part requirements.
Why does contract entitlement matter for maintenance?
A customer agreement may include preventive maintenance, a defined number of service calls or other service commitments. Entitlement information helps determine whether requested work is covered or requires another commercial treatment.
Can predictive maintenance create additional service revenue?
It can identify work that needs attention, but whether that work is included or chargeable depends on the customer's contract, entitlement and commercial rules. A condition trigger identifies the operational need; the service agreement determines the commercial treatment.