LESSON 5-4: Leveling Resources
This tutorial describes:
•    how to use resource leveling
•    how to resolve overallocation
•    how to use Prioritization as tiebreaker

[MUSIC PLAYING]
1. Resource Leveling.
Resource overallocation can occur when multiple activities are scheduled to use the same resource at the same time. Use resource leveling to delay one or more activities, so they are no longer scheduled at the same time. To get started, let's examine a simple project.
All activities need the same piece of equipment for eight hours a day. The equipment is only operational for 16 hours a day. Two eight-hour activities can be scheduled on the same day. But when three or more are scheduled, overallocation occurs.

2. Activity examined one at a time
The project usage histogram shows the overallocation. Resource leveling can resolve the overallocation by examining each activity.

3. Activity remain or are moved.
If sufficient resources are available, the activity remains as scheduled. If not, it is moved to a later date when sufficient resources are available.

4. Leveler obey network logic.
Because the levelers starts at the beginning of the project, network logic is obeyed. This means and activity will not be delayed, so that it's scheduled after its successor. Constraints are also respected when leveling. For example, an activity with a mandatory start or finish will not be delayed.

5. Prioritization.
Let's go ahead and launch the leveler. Choose the resources to be leveled, or use the option to level all resources. 
Prioritization is used as the tiebreaker when multiple activities qualify to be leveled next. Use calculated fields, such as Total Floats and Late Start for prioritization. Or as is the case here, set your own priority using the activity level priority field, which is manually assigned to activities. The resources are leveled. The project usage histogram now shows the overallocation is resolved. 
[MUSIC PLAYING]