What does "eday" stand for in MS Project 2003

In the Detail Gantt and Leveling Gantt views in MS Project 2003 there is a
Leveling field. The units are edays. I'm wondering what an eday is.

"PD" <PD@discussions.microsoft.com> wrote in message
news:B892A87E-B8FA-4804-A40A-FAB23595E544@microsoft.com...
> In the Detail Gantt and Leveling Gantt views in MS Project 2003 there is a
> Leveling field. The units are edays. I'm wondering what an eday is.

Elapsed Days
It is the number of calendar days rather than business days.

Note that you can enter your task durations in edays as well. This is useful
when you have tasks which do not obey working hours (things like waiting for
concrete to cure are typical examples)

--
-Jack ... For Microsoft Project information and macro examples visit
http://masamiki.com/project
or http://zo-d.com/blog/index.html
..
"Gilgamesh" <gilgamesh@spam.me.not> wrote in message
news:OrIFCWL7FHA.3200@TK2MSFTNGP11.phx.gbl...
> "PD" <PD@discussions.microsoft.com> wrote in message
> news:B892A87E-B8FA-4804-A40A-FAB23595E544@microsoft.com...
> > In the Detail Gantt and Leveling Gantt views in MS Project 2003 there is
a
> > Leveling field. The units are edays. I'm wondering what an eday is.
>
> Elapsed Days
> It is the number of calendar days rather than business days.
>
>

Hi,

I don't understand why after levelling, some tasks got few edays (eg. 3
edays ...) but the start dates change by years (eg. 3 years from the previous
task), if I manually change it to some other number, then it set the start
date delay correctly for some days only.

I felt concern that levelling will delay one task (in the middle of a link)
for several years. Levelling sounds useless if there is no way to bring the
delay back to reasonable range.

Hung

"JackD" wrote:

> Note that you can enter your task durations in edays as well. This is useful
> when you have tasks which do not obey working hours (things like waiting for
> concrete to cure are typical examples)
>
> --
> -Jack ... For Microsoft Project information and macro examples visit
> http://masamiki.com/project
> or http://zo-d.com/blog/index.html
> ..
> "Gilgamesh" <gilgamesh@spam.me.not> wrote in message
> news:OrIFCWL7FHA.3200@TK2MSFTNGP11.phx.gbl...
> > "PD" <PD@discussions.microsoft.com> wrote in message
> > news:B892A87E-B8FA-4804-A40A-FAB23595E544@microsoft.com...
> > > In the Detail Gantt and Leveling Gantt views in MS Project 2003 there is
> a
> > > Leveling field. The units are edays. I'm wondering what an eday is.
> >
> > Elapsed Days
> > It is the number of calendar days rather than business days.
> >
> >
>
>
>

Leveling will move tasks into the future until the resource(s) assigned to
it are available. If your task is getting delayed by 3 years by leveling,
it means the first time the resource assigned to it shows enough percentage
free is three years into the future. Now that's pretty weird, I'd agree,
and seems to indicate something is not set correctly. To find the exact
reason you need to look at things like task priorities, the resource's
calendar, the resource's available from and to data, and the like.

Here's one way it might happen. Try this experiment, it might give you some
ideas where to start looking in your own project. Create a plan with one
task "Build Something" with 5 days duration, starting next week. Enter a
resource "Carpenters" in the Resource Sheet view. Click on the ID number
and in the Resource Information show that Carpenters are available at 100%
until the end of the year and the 300% after Jan 01 (we've got one guy right
now but will hire 2 more after the holidays). Back in the Gantt chart,
assign Carpenters to the task 200% (we figure it will require 2 guys working
together to do it). The resource sheet will show the Carpenters in red,
overallocated. Run Resource Leveling. You'll see the task jump out to
start the first week of January, the first point in time where we'll have
two men available to work together on the task, ie, a resource assignment of
200% is valid. Something like this is probably going on in your plan though
pinning it down might take a bit of digging.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs


"Hung" <Hung@discussions.microsoft.com> wrote in message
news:D08A1B35-EE6F-41CD-B946-085AC08A7425@microsoft.com...
> Hi,
>
> I don't understand why after levelling, some tasks got few edays (eg. 3
> edays ...) but the start dates change by years (eg. 3 years from the
> previous
> task), if I manually change it to some other number, then it set the start
> date delay correctly for some days only.
>
> I felt concern that levelling will delay one task (in the middle of a
> link)
> for several years. Levelling sounds useless if there is no way to bring
> the
> delay back to reasonable range.
>
> Hung
>
> "JackD" wrote:
>
>> Note that you can enter your task durations in edays as well. This is
>> useful
>> when you have tasks which do not obey working hours (things like waiting
>> for
>> concrete to cure are typical examples)
>>
>> --
>> -Jack ... For Microsoft Project information and macro examples visit
>> http://masamiki.com/project
>> or http://zo-d.com/blog/index.html
>> ..
>> "Gilgamesh" <gilgamesh@spam.me.not> wrote in message
>> news:OrIFCWL7FHA.3200@TK2MSFTNGP11.phx.gbl...
>> > "PD" <PD@discussions.microsoft.com> wrote in message
>> > news:B892A87E-B8FA-4804-A40A-FAB23595E544@microsoft.com...
>> > > In the Detail Gantt and Leveling Gantt views in MS Project 2003 there
>> > > is
>> a
>> > > Leveling field. The units are edays. I'm wondering what an eday is.
>> >
>> > Elapsed Days
>> > It is the number of calendar days rather than business days.
>> >
>> >
>>
>>
>>

Thank you Steve for digging in this.

I discovered that I got the problem because I did not update my MS Project
Professional with SP2.
After applying it, the Resource levelling went well.
Just for whom who got the same problem to know.

Thanks
Hung