The maintenance plan hierarchy is the structure that organizes preventive maintenance at different levels, from the general plan logic to the specific services and tasks that each vehicle must execute. In fleets, this hierarchy allows standardizing criteria by unit type, ordering which interventions apply, and providing traceability to planned work. Its value lies in transforming maintenance into a clearer, scalable, and consistent system.

What is the maintenance plan hierarchy?

The maintenance plan hierarchy is the way preventive maintenance is organized in levels that range from a general definition to concrete actions on each unit.

Instead of managing maintenance as isolated events, this logic orders work within a structure. First a general plan is defined, then the services that form part of that plan, and finally the specific tasks that compose each service.

In a fleet, this hierarchy ensures that maintenance does not depend on improvised decisions case by case, but rather on a standard logic linked to vehicle type, its use, and its service need.

What is the maintenance plan hierarchy for?

It serves to order and scale preventive maintenance. When a company works with different vehicles, models, or operational contexts, it needs a structure that allows repeating criteria without losing control over the detail.

The hierarchy helps with exactly that. It allows defining plans by unit type, associating services to those plans, and then breaking down the tasks that each service must execute. That way, maintenance becomes clearer both for configuration and for daily operation.

It also improves traceability, because it makes visible how each preventive intervention is built and what logic is behind each ticket or control.

How is a maintenance plan hierarchy composed?

The hierarchy usually consists of three main levels: plan, service, and task.

The plan is the most general level. It groups the maintenance strategy for a vehicle type or a family of units. The service represents a concrete intervention within that plan, for example maintenance every certain number of kilometers. The task is the specific action that makes up that service, such as inspecting, changing, or controlling a specific component.

This structure allows the same general logic to translate into concrete and repeatable actions, without losing order between strategy, execution, and technical detail.

Why is it important to work with this hierarchy?

It is important because preventive maintenance needs consistency. If a company manages each service in isolation, without a common structure, the risk grows of omitting tasks, duplicating configurations, or losing criteria between similar vehicles.

The hierarchy reduces that disorder. It helps build plans that are easier to maintain over time, allows adapting the logic by unit type, and improves the ability to analyze what services and tasks are associated with each plan.

It also makes operation growth simpler. A fleet that adds vehicles or changes configurations needs an ordered foundation to continue managing without adding unnecessary complexity.

What relationship does it have with preventive tickets?

The relationship is direct. Preventive tickets do not arise from scratch, but rather from controls and configurations that have a plan, services, and tasks logic behind them.

When the hierarchy is well-defined, each preventive ticket inherits a clear structure about what service corresponds to executing and what tasks are associated with that work. This improves the quality of maintenance and reduces room for improvisation.

In other words, the plan hierarchy is the foundation that gives meaning to preventive work when the time comes to execute it.

Use cases

How VEC Fleet can help

VEC Fleet helps work with the maintenance plan hierarchy by structuring preventive maintenance in a clear logic of plans, services, and tasks.

The functional documentation describes this organization as a pyramid. At the top are the maintenance plans by model or vehicle type. At the intermediate level are the services to be performed, such as interventions at a certain mileage. At the base are the tasks that make up those services. This structure allows understanding how each plan is built and how it translates into concrete actions on the unit.

Additionally, VEC Fleet allows assigning preventive plans, viewing their associated services, editing their composition, and configuring services with related tasks. In this way, the hierarchy does not remain just as a design concept, but rather as a practical way to organize maintenance, improve consistency, and sustain a more orderly operation.

FAQs