If you use only days as your duration unit, you don't need to worry about setting correctly the parameters for weeks, months and years. Personnaly, I never bother setting them because all my durations are entered in days, even when they are quite long, e.g. 150 days for some procurement lead times.
What Santosh meant by being manually set is that you have the freedom to determine how many hour make a monnth or year.
Based your example of 8hours/day working time, I'd set the following for week, month & year for a 5-day week.
Option 1:
Hours/Week = hours/day * 5 = 8 * 5 = 40 (assumes 5 days in a week)
Hours/Month = hours/week * 4 = 40 * 4 = 160 (assumes 4 weeks in a month)
Hours/Year = hours/month * 12 = 160 * 12 = 1920 (assumes 12 months in a year)
Option 2:
Hours/Week = hours/day * 5 = 8 * 5 = 40 (assumes 5 working days in a week)
Hours/Month = hours/day * 22 = 8 * 22 = 176 (assumes 22 working days in a month)
Hours/Year = hours/week * 50 = 40 * 50 = 2000 (assumes 50 working weeks in a year)
As you can see, both options are valid as long as you state and document your assumptions in a Schedule Basis or Schedule Memorandum document.
The 172 hours/month that comes as default in P6 is based on 8 hrs/day * 21.5 = 172 and this assumes 21.5 working days in a month. And the 2000 hours/year assumes 50 working weeks in a year, i.e. 40 hrs/week * 50 = 2000
It isn't calculated, it is manually set. P6 calculated all durations in hours. The values that are set here is what P6 uses to return the values to hours. For example using the values you give, if you enter a duration of 1w P6 would determine that task as being 48hrs long, and then spread that 48hrs across the available hours you set in the calendar.
Member for
4 years 8 monthsHi Moutaz,If you use only
Hi Moutaz,
If you use only days as your duration unit, you don't need to worry about setting correctly the parameters for weeks, months and years. Personnaly, I never bother setting them because all my durations are entered in days, even when they are quite long, e.g. 150 days for some procurement lead times.
Member for
21 years 9 monthsMoutaz,What Santosh meant by
Moutaz,
What Santosh meant by being manually set is that you have the freedom to determine how many hour make a monnth or year.
Based your example of 8hours/day working time, I'd set the following for week, month & year for a 5-day week.
Option 1:
Option 2:
As you can see, both options are valid as long as you state and document your assumptions in a Schedule Basis or Schedule Memorandum document.
The 172 hours/month that comes as default in P6 is based on 8 hrs/day * 21.5 = 172 and this assumes 21.5 working days in a month. And the 2000 hours/year assumes 50 working weeks in a year, i.e. 40 hrs/week * 50 = 2000
===
Jerome
www.plannersplace.com
Member for
21 years 10 monthsThanks Santosh and Zoltan,I
Thanks Santosh and Zoltan,
I know it is manually set and there are standard working hours per week, month, and year.
for week it is very easy to calculate it whatever the working hours/day is, but how to calculate it for month and year.
how many working days per month if the working days per week 5 days for example?
Member for
16 years 3 monthsthose are standard working
those are standard working hours per week, month and year
Member for
20 years 6 monthsIt isn't calculated, it is
It isn't calculated, it is manually set. P6 calculated all durations in hours. The values that are set here is what P6 uses to return the values to hours. For example using the values you give, if you enter a duration of 1w P6 would determine that task as being 48hrs long, and then spread that 48hrs across the available hours you set in the calendar.