Prev: Project 2010
Next: OutlineGrandParent.duration
From: smw on 12 May 2010 16:44
That would be due to the fact that I do not know what edays are. Next thing
to learn I guess

"Roland" wrote:

> Hi Steven,
>
> Just curious. Why did you create another calendar just for lead-time? You
> could use "edays" instead which would have given you the results needed
> without additional calendar maintenance.
>
> RC
>
> "smw" wrote:
>
> > I need to have a separate line item in my plan for the lead-times on several
> > purchases. Example: order is placed on 6/30/2010, lead time to delivery is
> > 60 calendar days, delivery would be on 8/28/2010. To do this I created a
> > lead-time calendar that makes every day a work day by setting all days to
> > 8:00 AM - 5:00 PM. Task is fixed duration, 60d, non-estimated, calendar
> > LeadTime is assigned to the task, no resources specified.
> >
> > The problem; project computes the Planned End Date at 8/22/2010 which by my
> > calculation is 7 days short of 60. Changing the calendar attached to this
> > task to the 24hour one increases the discrepancy.
> >
> > Any suggestions will of course be greatly appreciated.
> >
> > Steven Wheeler
From: Roland on 12 May 2010 17:45
edays = elapsed days

Basically it means every calendar day and non-working days are ignored. You
need to be careful using it if work is input as MSP calculates it as 24 hours
rather than at 8 hours per day of work time.


"smw" wrote:

> That would be due to the fact that I do not know what edays are. Next thing
> to learn I guess
>
> "Roland" wrote:
>
> > Hi Steven,
> >
> > Just curious. Why did you create another calendar just for lead-time? You
> > could use "edays" instead which would have given you the results needed
> > without additional calendar maintenance.
> >
> > RC
> >
> > "smw" wrote:
> >
> > > I need to have a separate line item in my plan for the lead-times on several
> > > purchases. Example: order is placed on 6/30/2010, lead time to delivery is
> > > 60 calendar days, delivery would be on 8/28/2010. To do this I created a
> > > lead-time calendar that makes every day a work day by setting all days to
> > > 8:00 AM - 5:00 PM. Task is fixed duration, 60d, non-estimated, calendar
> > > LeadTime is assigned to the task, no resources specified.
> > >
> > > The problem; project computes the Planned End Date at 8/22/2010 which by my
> > > calculation is 7 days short of 60. Changing the calendar attached to this
> > > task to the 24hour one increases the discrepancy.
> > >
> > > Any suggestions will of course be greatly appreciated.
> > >
> > > Steven Wheeler
First  |  Prev  | 
Pages: 1 2
Prev: Project 2010
Next: OutlineGrandParent.duration