Christopher method should do the trick and is simple until you start updating the schedule and different activities actual happen in the middle of the individual curve, each at a different point, this slightly complicates the issue, especially when you switch to named resources and use the schedule to manage your manpower.
You can apply this method to not started jobs and as soon as the job is committed and scheduled use bottom up scheduling with a sufficiently detailed breakdown that does not require the use of resource curves. This will make it easier.
Most probably this method is documented on P6 literature as it goes to the bare bones of how resource curves are implemented.
I probably would add the 21 workload values and divide by 21, this will yield the average daily workload and multiply by calendar average hours per day to get the scale factor for 1 resource 1 day. Then total mh can be computed by multiplying the scale factor by activity duration in days by resource quantity.
Best regards,
Rafael
Member for
14 years 11 months
Member for14 years11 months
Submitted by ca*****@y***** on Fri, 2012-05-18 17:09
This is an issue of fixed resource quantity with variable workload, perhaps variable units/time in P6 language. You might be switching workload and resource quantity and they are not the same. You got it when you tried with remaining units/time just that you cannot apply a curve to this parameter as you can to resource quantity. It is a very simple allocation for which I used special fields to determine the duration of the different phases for each job. I defined a "phase" for each workload discrete duration. I defined the resource as non leveling because I do not want it to drive the activities during resource leveling. If there is an overload then I would fix the supply.
From the above figure you will see that during Oct and Nov 2 resources A will be needed.
After you get it we can start talking about how with the use of skills functionality you can see the details on how each individual resource unit is assigned and how to keep some control using priorities and in some cases using direct resource assignment instead of only skills with or w/o priorities.
It is different software but the general concept shall be similar.
By the way I do not believe P6 resource level those resources to which a curve has been applied. Maybe old P3 but at the cost of a poor resource leveling algorithm that would use some kind of "brute force".
Member for
15 years 8 monthsHi,I wrote an article
Hi,
I wrote an article regarding How does “Resource curve” work?
If you're interested, kindly read it here https://doduykhuong.wordpress.com/2016/01/09/how-does-resource-curve-work/
Cheer
Member for
21 years 7 monthsRonnie,Christopher method
Ronnie,
Christopher method should do the trick and is simple until you start updating the schedule and different activities actual happen in the middle of the individual curve, each at a different point, this slightly complicates the issue, especially when you switch to named resources and use the schedule to manage your manpower.
You can apply this method to not started jobs and as soon as the job is committed and scheduled use bottom up scheduling with a sufficiently detailed breakdown that does not require the use of resource curves. This will make it easier.
Most probably this method is documented on P6 literature as it goes to the bare bones of how resource curves are implemented.
I probably would add the 21 workload values and divide by 21, this will yield the average daily workload and multiply by calendar average hours per day to get the scale factor for 1 resource 1 day. Then total mh can be computed by multiplying the scale factor by activity duration in days by resource quantity.
Best regards,
Rafael
Member for
14 years 11 monthsThanks guys for the replies.
Thanks guys for the replies. I'll give it a go.
Regards
Ronnie
Member for
20 years 1 monthThis can be made a lot more
This can be made a lot more complex
If we all try
Thanx
Member for
21 years 7 monthsThis is an issue of fixed
This is an issue of fixed resource quantity with variable workload, perhaps variable units/time in P6 language. You might be switching workload and resource quantity and they are not the same. You got it when you tried with remaining units/time just that you cannot apply a curve to this parameter as you can to resource quantity. It is a very simple allocation for which I used special fields to determine the duration of the different phases for each job. I defined a "phase" for each workload discrete duration. I defined the resource as non leveling because I do not want it to drive the activities during resource leveling. If there is an overload then I would fix the supply.
From the above figure you will see that during Oct and Nov 2 resources A will be needed.
After you get it we can start talking about how with the use of skills functionality you can see the details on how each individual resource unit is assigned and how to keep some control using priorities and in some cases using direct resource assignment instead of only skills with or w/o priorities.
It is different software but the general concept shall be similar.
By the way I do not believe P6 resource level those resources to which a curve has been applied. Maybe old P3 but at the cost of a poor resource leveling algorithm that would use some kind of "brute force".
Best regards,
Rafael