Please be reminded that leveling effort hours is not the same as leveling resource quantity. It might seem equivalent but under partial workloads leveling of effort might yield wrong results.
Rafael - thanks, that's a useful suggestion. I'll give it a go. Obviously the numbers are higher, but the logic behind what you are suggesting should still work, if I create a resource with a limit of 5000 (being silly), assign 1 to each activity that can happen whenever, and 5000 to the one that can only happen on it's own.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Wed, 2018-08-22 22:36
Create a marker resource say Resource A with availability of 9 ea.
Assign 1 ea to the 9 activities that can happen at the same time. If you want to set some prioritization do it. A good resource leveling engine will respect the prioritization as long as it can yield shorter schedule duration.
Assign 9 ea to the activity that cannot happen while the other 9 activities.
Resource level. Check resource leveling by moving some activities to see if the requirement for Activity X holds after leveling.
If using effort hours translate availability and assignments to how your software works.
Member for
15 years 11 monthsJohanness presentation below
Johanness presentation below is the right procedure. This can be applied too using Quantities of Workloads.
Member for
21 years 8 monthsPlease be reminded that
Please be reminded that leveling effort hours is not the same as leveling resource quantity. It might seem equivalent but under partial workloads leveling of effort might yield wrong results.
Member for
15 years 9 monthsHi MartinI have modeled the
Hi Martin
I have modeled the challenge in Primavera P6.
Resource optimization is finding the balance between the resource requirements and the resource availability.
The resource requirements you detail in the activity
The resource availability you detail in the enterprise> resources
In this case, I have 10 times 8 hours/day=80 hours/day requirement
I have detailed 9 times 8 hours/day=72 hours/day availability.
I leveled the resources and the result you see below.
Thrust this is clear
Regards
Johannes
Member for
22 years 4 monthsRafael - thanks, that's a
Rafael - thanks, that's a useful suggestion. I'll give it a go. Obviously the numbers are higher, but the logic behind what you are suggesting should still work, if I create a resource with a limit of 5000 (being silly), assign 1 to each activity that can happen whenever, and 5000 to the one that can only happen on it's own.
Member for
21 years 8 monthsCreate a marker resource say
If using effort hours translate availability and assignments to how your software works.