Feature image

Nested PM

The Challenges of Traditional Preventive Maintenance

Traditionally, if multiple preventive maintenance (PM) cycles for a piece of equipment coincided on the same date, maintenance teams had to create separate scheduled maintenance triggers in their CMMS (Computerized Maintenance Management System). This led to an increase in manual paperwork. Consider a simple analogy—owning a car necessitates various maintenance tasks such as:

  1. Oil change every 3,000 km
  2. Oil filter change every 12,000 km
  3. Spark plug replacement every 12,000 km
  4. Air filter change every 12,000 km
  5. Timing belt replacement every 60,000 km

In a basic CMMS system, you’d create multiple work orders for tasks overlapping on the same date, making management cumbersome—particularly challenging when managing numerous assets.

What Is Nested Preventive Maintenance?

Nested preventive maintenance (Nested PM) is a unique feature of modern CMMS solutions like Fiix. This functionality allows maintenance teams to group PMs of varying durations and complexities, streamlining management when tasks are set to occur simultaneously.

For instance, if you have a monthly maintenance task alongside annual tasks, you can group them together, reducing the need for multiple work orders. When the monthly task is due, only that task will be released for work—similarly for the annual tasks. This method ensures that more frequent tasks are incorporated into less frequent ones, simplifying your maintenance schedule.

Example of a Nested PM Cycle

Consider a piece of equipment with the following PM cycles established:

PM CycleTasksNesting Code
Weekly4 tasksN1
MonthlyWeekly tasks + 2 additional monthly tasksN2
QuarterlyWeekly tasks + 4 additional quarterly tasksN3
AnnualQuarterly tasks + 2 additional annual tasksN4

During an annual PM, you execute all the tasks from the weekly, monthly, and quarterly schedules along with other annual tasks.

Understanding How Nested PMs Operate

When setting up nested PMs, each PM activity builds off the shortest PM cycle, known as the root PM. For instance, if the weekly PM is the root with a nesting code of N1, this forms the base for all other PMs. With 52 weeks in a year, the annual PM becomes a multiplier of 52.

Time-Based Example:

PM CycleNumber of WeeksMultiplier
Weekly11
Monthly44
Quarterly1313
Annual5252

Meter-Based Example:

PM CycleMultiplierNesting Code
250-hour PM1N1
500-hour PM2N2
1000-hour PM4N3
2000-hour PM8N4
10,000-hour PM40N5

The 250-hour PM serves as the N1 root PM, establishing a straightforward mathematical relationship.

Accessing Nested PM Functionality in Your CMMS

The nested PM feature is included with the enterprise package of CMMS solutions. If you’re already utilizing an enterprise CMMS, you can find the new nested PM tab available within your scheduled maintenance section. Note, however, that if you opt for traditional PMs, you can disregard the nested PM tab.

If you’re looking to upgrade your current CMMS to access these features, click the green upgrade button available on our site. Upgrading unlocks additional benefits such as rotating assets and enhanced reporting tools.

Important Notes to Consider

Explore Further:

← Back to Glossary