Resource/Target Leveling: Tuning Parameters

This tab allows you to slightly alter the leveling algorithm if it is not producing the expected results.

The following table describes the fields on this screen shown below:

Field Description
Factors affecting sort order

The initial sort order significantly affects the results of the resource leveling.

To adjust how tasks without resource assignments are handled, you have three options for schedules where the scheduling of unassigned tasks affects the outcome of a leveling run:

  • Ignore tasks with no resource assignments - unassigned tasks are added to the sort list in whatever order they occur based on sorting by the fields assigned in Order for resolving over-allocations on the Details tab. By default, this option is selected.

In earlier versions of DTS, this is the default option for Resource Leveling.

  • Tasks with no resource assignments have HIGHER priority - unassigned tasks are given the highest priority and are added to the top of the sort list. This forces the schedule to occur as fast as possible, and is generally the best option.
  • Tasks with no resource assignments have LOWER priority - unassigned tasks are given the lowest priority and are added to the bottom of the sort list. This can force assigned tasks to be delayed significantly, as they have to wait for unassigned predecessor tasks to complete.
Handling of tasks with fixed constraints

These options and their functionality, as described here, can change in the near future.

These options determine if tasks assigned as Must Start On are considered in Resource Leveling.

  • Assign highest priority and level normally (default) - if this option is selected, the resource leveling algorithm may not level tasks around the Must Start On tasks, which results in over-allocation of the resources. By default, this option is selected.
  • Reduce resource availability before leveling - if this option is selected, the availability of the resources assigned when working on Must Start On tasks is reduced, so that they are considered correctly in the resource leveling algorithm.
Handling of tasks that are not to be levelled If a task was previously delayed due to levelling, but you have excluded such a task from the next levelling run (by switching off its Level Task flag), you can optionally prevent such level delays from being removed prior to the next levelling run.
Handling of tasks with ALAP constraints Normally you would not use this option as it does not give the best results. It can be useful when debugging the leveling output to see the effect of skipping the additional backwards pass.
Clear Leveling Click to clear all currently applied leveling constraints from the tasks.
Level Now Click to run the resource leveling and insert leveling constraints where required.

All previous resource leveling constraints will be automatically cleared before the resource leveling is run.
Cancel Click to lose your changes and close this screen.
Help Click to display the help for this screen.