in MSP vocabulary, "e" stands for "elapsed"; 1 day equals 8 hours, and 1 "e"day equals 24 hours
a 5-day task (#1) created on Sunday will start the following Monday and finish on Friday evening, and a 5-eday task (#2) will start Sunday morning and finish on Friday morning
a resource assigned to task #1 will work 40 hours, the same resource assigned to task #2 will work 120 hours
Use task #1 for regular work at work hours, and task #2 for curing concrete, drying paintings, ...
Member for
22 years 9 monthsBrad,in MSP vocabulary, "e"
Brad,
in MSP vocabulary, "e" stands for "elapsed"; 1 day equals 8 hours, and 1 "e"day equals 24 hours
a 5-day task (#1) created on Sunday will start the following Monday and finish on Friday evening, and a 5-eday task (#2) will start Sunday morning and finish on Friday morning
a resource assigned to task #1 will work 40 hours, the same resource assigned to task #2 will work 120 hours
Use task #1 for regular work at work hours, and task #2 for curing concrete, drying paintings, ...
Alexandre
Member for
19 years 10 monthsHi Brad I am assuming ehrs =
Hi Brad
I am assuming ehrs = estimated hours? - yes?
When resourcing a plan to set up duration modelling you must use the estimated hours.
In this way you form the triangle of Scope - Time - Money.
I use only one resource called "Hours" irrespective of the trade - I use codes to filter on the trade.
Best regards
Mike Testro