Please be reminded that MSP nor P6 have a field for crew size, they just use effort and attempt to level resources using effort, and this might create unfeasible schedules. In this software you will never update resource quantity but effort; you will never update available resource quantity but available effort which can be related by complex relationships under partial workloads.
As previously said the goal is to be able to vary crew size and immediately see the impact on the activity duration and on the resource leveled schedule as a whole.
As you can see in the previous example you can change productivity only and this will result in changed activity duration as well effort or resource hours [units] without any change in the resource quantity.
On the other hand if you change resource quantity the activity duration will change without any change in total effort, it is just that with less resources same effort it will take more time to do the same volume of work.
It shall be easy and transparent.
There should be an easier way to do so in your software!
So simple, so easy.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Sat, 2017-05-20 14:13
I realize this is a very late response, almsot 6 years haha, but I have determined a way to show what you need through 2 global changes. The first one is the change the crew size, use the below 1st GB. Then use create a UDF field named crew size, and a user defined field named Remaining Units/Time and use the next global change.
Well this is as far as I can go without having P6, still I believe this is such a basic need it shall be available without the need of any UDF and global changes. It shall be easy and transparent.
No, all necessary fields are available, except crew size, in the 'resource tab'. Crew size does exist when viewing the project under "Resource Assignments". But if you create a UDF called 'crew size', you cannot use it to do the math of multiplying crew size by default units/time to get a remaining units/time to determine the duration. At least, I have not been able to do so.
The goal is to be able to vary crew size and immediately see the impact on the activity duration.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Tue, 2011-06-21 21:41
Do you mean Remaining Units is not an available field?
Remaining Units / time = Remaining Units / Remaining Duration
Even Units/Time shall be an available field. Perhaps because P6 do not handle these at the resource level you are not able to find them under the resource tab but maybe, ???, you can find them under the activity table as available fields.
Member for
18 years 6 months
Member for18 years6 months
Submitted by Dennis Hanks on Tue, 2011-06-21 15:56
Fixed units is the key. The estimated remaining manhours should account for all expected productivity factors, so the only real variable is crew size when determining activity duration. Currently P6 provides a default units/time (hours/day) that has to be manually manipulated to reflect crew size (number of men X default units/time).
What I want to do is be able to use 'crew size' as a UDF to determine the remaining units/time and do it on a more or less real time basis.
Again, thanks for your suggestions.
Member for
18 years 6 months
Member for18 years6 months
Submitted by Dennis Hanks on Mon, 2011-06-20 16:16
Thanks for the reply. The math is not the problem (hours are already determined). Getting Primavera to do the math is. Remember this is a "conceptual, high-level schedule", I do not need the 'granularity' you suggest.
Looking for a technique that will allow realtime calculation of duration given estimated hours and crew size. Right now this can all be done in Excel, but I was hoping for something that would let me do this in the P6 'resource tab' and then F9 or run Global Change.
Again, thanks.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Fri, 2011-06-17 23:57
This is an everyday issue you shall be able to handle easily, it usually a bit "less easy" because of the fact many individual resources do not have same productivity. For example a 20-cm truck and a 30-cm truck have different earth moving capabilities. You shall be able to model different resources with different productivity as same skill, and depending on availability the software will adjust activity duration. Same goes for a masonry crew with different composition, a few masons versus a few mason apprentices with lower productivity.
If your software cannot handle this issue directly and transparently only then you shall consider alternate ways.
No matter how you do it it is important to keep the relation between resource assignment and remaining duration, it shall be automatic and transparent otherwise Murphy will show up at the worst moment.
I don't use P6 but believe using multiple UDFs and multiple Global Changes in this particular case is calling for trouble if you do not keep a record of remaining duration and resource loading values before adjustments are performed, this mean a few extra global changes on UDFs. Kind of compliicated.
Member for
16 years 3 monthschange the activity type to
change the activity type to Resource depanedent and change the duration type to fixed units/time
Member for
21 years 8 monthsPlease be reminded that MSP
Please be reminded that MSP nor P6 have a field for crew size, they just use effort and attempt to level resources using effort, and this might create unfeasible schedules. In this software you will never update resource quantity but effort; you will never update available resource quantity but available effort which can be related by complex relationships under partial workloads.
Member for
21 years 8 monthsAs previously said the goal
As previously said the goal is to be able to vary crew size and immediately see the impact on the activity duration and on the resource leveled schedule as a whole.
On the other hand if you change resource quantity the activity duration will change without any change in total effort, it is just that with less resources same effort it will take more time to do the same volume of work.
Member for
21 years 8 monthsWell I do not know well P6,
Well I do not know well P6, I used P3e years ago, but what you are doing makes so much sense that what you are asking shall exist in some easy way.
Best regards,
Rafael
Member for
8 years 5 months...
...
Member for
8 years 5 monthscapture1.png
[[wysiwyg_imageupload:4809:]]
Member for
8 years 5 monthsHey Dennis, I realize this is
Hey Dennis,
I realize this is a very late response, almsot 6 years haha, but I have determined a way to show what you need through 2 global changes. The first one is the change the crew size, use the below 1st GB. Then use create a UDF field named crew size, and a user defined field named Remaining Units/Time and use the next global change.
[[wysiwyg_imageupload:4807:]]
Member for
11 years 11 monthsMember for
21 years 8 monthsWell this is as far as I can
Well this is as far as I can go without having P6, still I believe this is such a basic need it shall be available without the need of any UDF and global changes. It shall be easy and transparent.
http://youtu.be/4RwlszpYYq4
Good luck,
Rafael
Member for
18 years 6 monthsNo, all necessary fields are
No, all necessary fields are available, except crew size, in the 'resource tab'. Crew size does exist when viewing the project under "Resource Assignments". But if you create a UDF called 'crew size', you cannot use it to do the math of multiplying crew size by default units/time to get a remaining units/time to determine the duration. At least, I have not been able to do so.
The goal is to be able to vary crew size and immediately see the impact on the activity duration.
Member for
21 years 8 monthsDo you mean Remaining Units
Do you mean Remaining Units is not an available field?
Remaining Units / time = Remaining Units / Remaining Duration
Even Units/Time shall be an available field. Perhaps because P6 do not handle these at the resource level you are not able to find them under the resource tab but maybe, ???, you can find them under the activity table as available fields.
Member for
18 years 6 monthsRafael;Fixed units is the
Rafael;
Fixed units is the key. The estimated remaining manhours should account for all expected productivity factors, so the only real variable is crew size when determining activity duration. Currently P6 provides a default units/time (hours/day) that has to be manually manipulated to reflect crew size (number of men X default units/time).
What I want to do is be able to use 'crew size' as a UDF to determine the remaining units/time and do it on a more or less real time basis.
Again, thanks for your suggestions.
Member for
18 years 6 monthsRafael;Thanks for the reply.
Rafael;
Thanks for the reply. The math is not the problem (hours are already determined). Getting Primavera to do the math is. Remember this is a "conceptual, high-level schedule", I do not need the 'granularity' you suggest.
Looking for a technique that will allow realtime calculation of duration given estimated hours and crew size. Right now this can all be done in Excel, but I was hoping for something that would let me do this in the P6 'resource tab' and then F9 or run Global Change.
Again, thanks.
Member for
21 years 8 monthsDennis,This is an everyday
Dennis,
This is an everyday issue you shall be able to handle easily, it usually a bit "less easy" because of the fact many individual resources do not have same productivity. For example a 20-cm truck and a 30-cm truck have different earth moving capabilities. You shall be able to model different resources with different productivity as same skill, and depending on availability the software will adjust activity duration. Same goes for a masonry crew with different composition, a few masons versus a few mason apprentices with lower productivity.
If your software cannot handle this issue directly and transparently only then you shall consider alternate ways.
No matter how you do it it is important to keep the relation between resource assignment and remaining duration, it shall be automatic and transparent otherwise Murphy will show up at the worst moment.
I don't use P6 but believe using multiple UDFs and multiple Global Changes in this particular case is calling for trouble if you do not keep a record of remaining duration and resource loading values before adjustments are performed, this mean a few extra global changes on UDFs. Kind of compliicated.
Best regards,
Rafael