I hadnt realised that you could state a "unit" but on the other hand, ity seems to be a text field that you could put anything in that suits your fancy (I tried xyz as a unit) I would have thought, if it were to be used in calculations anywhere, that it would be a drop down list that selected a planning unit
Where does this "unit" appear, aside from the key of the resource graph?
tbh, I would still match the resource unit to the planning unit, from what I see
Member for
18 years 3 months
Member for18 years3 months
Submitted by Ferdinand U. on Tue, 2007-10-16 01:14
in the resources dialog box you can put what unit you are using for BQ,so still the units per timeperiod will be as what you entered in it..if you input BQ as 1000 hrs in 10 days duration,UPT shows 100hrs per day means approx 10 people as you said..
Member for
18 years 2 months
Member for18 years2 months
Submitted by James Barnes on Mon, 2007-10-15 09:23
The units in the RES tab will match the planning unit. Thus the figure that you enter will be Man Days not Man Hours if your planning unit is days. In your example, you should enter 100 as the Budgetted Q, which will return 10 units per day. P3 cannot work in different planning units within the same plan and you need to set the units (Hours, Days, weeks or Months) when you first create the schedule, I believe this is different in Enterprise.
If you are happy with this constraint then carry on, if not then change your planning unit to hours (easier said than done, depending on how far down the road you are in preparing your plan) and define activity and resource calenders. Then you can define different shift lengths, for example; some activities may need to occur at night, others on a standard day shift and certain critical items on a double or even triple shift
Within the constraint of a Day planning unit, your calender can only define workdays in the week (for example label Sunday as non working) and blank out certain days (holidays, for example) but only at the Day level, not down to hours. Thus you could not define a shorter saturday shift.
There may be some clever workrounds for the above, but I am not aware of them. We plan in hours for everything except strategic level planning, it is the most powerful, I believe. The only problem Ive come across with hour based plannign is that you need to keep close control on your calenders and very long lags (>30,000 planning units or about 3.5 years using hours for positive lags, 10,000 for negative ones) are not possible, but its very rare that youll hit that ceiling, Id rekon.
Member for
18 years 3 monthsRE: P3
i use manhours as BQ unit for workers.for resource histogram, if you want in mandays you must have a divisor..i.e. 60 for 6days/wk 10 hrs/day..
Member for
18 years 2 monthsRE: P3
I stand corrected.
I hadnt realised that you could state a "unit" but on the other hand, ity seems to be a text field that you could put anything in that suits your fancy (I tried xyz as a unit) I would have thought, if it were to be used in calculations anywhere, that it would be a drop down list that selected a planning unit
Where does this "unit" appear, aside from the key of the resource graph?
tbh, I would still match the resource unit to the planning unit, from what I see
Member for
18 years 3 monthsRE: P3
in the resources dialog box you can put what unit you are using for BQ,so still the units per timeperiod will be as what you entered in it..if you input BQ as 1000 hrs in 10 days duration,UPT shows 100hrs per day means approx 10 people as you said..
Member for
18 years 2 monthsRE: P3
The units in the RES tab will match the planning unit. Thus the figure that you enter will be Man Days not Man Hours if your planning unit is days. In your example, you should enter 100 as the Budgetted Q, which will return 10 units per day. P3 cannot work in different planning units within the same plan and you need to set the units (Hours, Days, weeks or Months) when you first create the schedule, I believe this is different in Enterprise.
If you are happy with this constraint then carry on, if not then change your planning unit to hours (easier said than done, depending on how far down the road you are in preparing your plan) and define activity and resource calenders. Then you can define different shift lengths, for example; some activities may need to occur at night, others on a standard day shift and certain critical items on a double or even triple shift
Within the constraint of a Day planning unit, your calender can only define workdays in the week (for example label Sunday as non working) and blank out certain days (holidays, for example) but only at the Day level, not down to hours. Thus you could not define a shorter saturday shift.
There may be some clever workrounds for the above, but I am not aware of them. We plan in hours for everything except strategic level planning, it is the most powerful, I believe. The only problem Ive come across with hour based plannign is that you need to keep close control on your calenders and very long lags (>30,000 planning units or about 3.5 years using hours for positive lags, 10,000 for negative ones) are not possible, but its very rare that youll hit that ceiling, Id rekon.