Hi Vladimir,

Yes That exercise we have to do before assigning the resources.

Sudarshan

• Resource Leveling:

 If resources are not leveled, resources are either over allocated or under allocated (or both).  Over allocation means the scheduled work is not likely to occur (or the resource may be annoyed, overworked or burned out).  Under allocation means suboptimal utilizing and billing of resource, lowering of profitability.  Lastly, the schedule won’t be accurate, unless resources are correctly loaded.

When we level the resources Primavera follows the following process:

• Resource requirement of all schedule activities are compared to the maximum quantity available at the time of leveling.
• An activity is delayed if too few resources are available at any time during the activity duration.

The maximum quantity for a resource is determined through the Max units/time for a particular resource in the Resource Tab.

We have a resource called Cladders with max unit /time as 10hrs/day and this resource is assigned to 2 activities happening on same days. The requirement for that resource will be 20hrs/day but it can only work for 10hrs/day.Hence that resource is found to be over allocated.

Over allocated resource can be checked by going to resource usage profile option and activating the limit line as  

 <?xml:namespace prefix = v /> <?xml:namespace prefix = o />

Once it is known that which resources in the project are over allocated, we can go for level resource option in the tool tab to level the resources.

When entering schedule information for the tasks, keep the following in mind to make sure P6-Project schedules project accurately, and to help prevent unnecessary resource over allocations.  Here are some tips:

• Task Dependencies
  Use task dependencies to reflect a necessary sequence of events. Don’t   overuse them, as each additional dependency can result in resource underutilization or completion date slippage.

• Constraints
  Avoid inflexible constraints, except where necessary. 
  Inflexible constraints are those tying a task to a date. The inflexible constraints are Must Finish On and Must Start On date constraints. We can specify that a task must start on or finish no later than a particular date.  Note such constraints limit the adjustments that Project can make when determining which tasks to adjust when leveling resources.

• Priorities

Mark to include resource assignments in other projects within the range of the leveling priority you specify when determining if a resource is over-allocated. Assignments in closed projects are considered. For example, if you mark the checkbox and specify a leveling priority of 5 in this field, the leveler considers all projects with a project leveling priority of 1,2,3,4, and 5.

• Automatically level resources when scheduling:
        This option levels resources every time when schedule is updated.

• Preserve scheduled early and late dates:

Mark to preserve the early and late dates that were calculated during project scheduling.

• Recalculate assignment costs after leveling:                                                              Mark to recalculate resource and role costs after leveling resources/roles in the projects. Use this option to calculate the costs of resource/role assignments that are assigned multiple rates.

• Level resources only within activity Total Float:                                                        Mark to delay activities with resource conflicts only up to their late finish date.

• Preserve minimum float when leveling:                                                                         The amount of float you want to maintain when activities are delayed because of resource conflicts.

Hi Chetan

I never allow the software to level resources because you have no control of what is happening.

Do it manually if you have to.

Best regards

Mike T.