It can also be used to balance the workload of primary resources over the course of the project[s], usually at the expense of one of the traditional triple constraints (time, cost, scope).
Project management software leveling requires delaying tasks until resources are available.
In either definition, leveling could result in a later project finish date if the tasks affected are in the critical path.
These work orders have other attributes such as report date, priority, asset operational requirements, and safety concerns.
For the most part, when it comes to maintenance scheduling, there is less, if any, task interdependence, and therefore less need to calculate critical path and total float.