Resource loading challenge

Here's the challenge...

You have 10 activities in your schedule.  They are all resource loading (not necessarily the same resources).  They have a 'prioritisation' code allocated to determine the sequence of preference for resource levelling.  There are no real inter-dependencies between them.  They can all happen in any order, they could all happen at the same time, apart from 1 of those activities (let's call it Activity X).  When Activity X happens, none of the other 9 can be planned to happen.  How can this be achieved using resource loading?

 



 

R
Raymund de Laza 👤 Member for 16 years 6 months

Johanness presentation below is the right procedure. This can be applied too using Quantities of Workloads.

J
Johannes Vandenberg 👤 Member for 16 years 4 months

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

Simple, Free Image and File Hosting at MediaFire

M
Martin Corkill 👤 Member for 22 years 11 months

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.

R
Rafael Davila 👤 Member for 22 years 3 months
  • 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.

Challenge2018.08.22

Forum Sponsor

Top Posters

Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts