Re: Error in formula for custom field
- From: PublicMike <PublicMike@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Aug 2009 07:03:01 -0700
Unfortuntately, we aren't applying cost to the work done, therefore
activities don't have a budgeted amount, hence the focus on dates only. This
is something to consider, however. We usually don't consider the labor cost
of performing the work. We have been discussing adding some $ amount on an
hourly basis to the resources, but their time is split between so many other
tasks and projects that often our estimates are based on x days to complete a
job that only requires 8 hours of work.
Thanks for the suggestion.
--
The only thing constant in life is change; therefore, you can follow change
and allow it to control you, or lead change and control your destiny.
"Jim Aksel [MVP]" wrote:
Now it makes sense: [Finish Variance]/[Baseline Duration]. If you have.
costed resources loaded to this schedule and a baseline, why not just use
Schedule Performance Index [SPI]? This is a comparison of what you have
accomplished divided by what you expected to accomplish within the given
time frame.
"PublicMike" <PublicMike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7079DC02-352D-46E8-BAA0-DB5609A70EB6@xxxxxxxxxxxxxxxx
You guys are right. I went back and realized I'd typed the field wrong.
The
field was Baseline Duration rather than Variance. Formula had the right
field, it was my typing/thinking that was screwy.
I'll give the indicator field a try and see what that does for me.
Appreciate the help.
--
The only thing constant in life is change; therefore, you can follow
change
and allow it to control you, or lead change and control your destiny.
"Rob Schneider" wrote:
I also can't find the field [BaseLine Variance] in Project 2007.
Interesting.
I suspect it a custom field (probably one of the number fields).
In any event, PublicMike, why don't you use the field "Indicator" to
indicate if a task is overdue, i.e. late? Let Project do the work. Even
better than telling you when something is already over due, it will warn
you of the computed finish date is beyond the deadline. Better, I
think, to know before something is late that the current schedule is
planning for it to be late.
--rms
PublicMike wrote:
I pulled the Baseline Variance field directly out of a pick list in
project.
It does indeed exist. To test out my theory of the "is anything" being
the
problem, I replaced that line with "is equal to 4294967295" and now the
formula calculates. "4294967295" is apparently the code for #N/A, so
if the
baseline hasn't been set, which would produce and error, it has a value
to
associate with that and return an indicator.
What I was trying to accomplish is to set a graphical indicator that
alerts
when a task is overdue, as determined by the baseline, by a certain
percentage.
I think I've got it now. Thanks for the input.
- Follow-Ups:
- Re: Error in formula for custom field
- From: Jim Aksel
- Re: Error in formula for custom field
- References:
- Error in formula for custom field
- From: PublicMike
- RE: Error in formula for custom field
- From: PublicMike
- Re: Error in formula for custom field
- From: Rob Schneider
- Re: Error in formula for custom field
- From: PublicMike
- Re: Error in formula for custom field
- From: Jim Aksel [MVP]
- Error in formula for custom field
- Prev by Date: editgoto date:=today
- Next by Date: Viewing Multiple Baseline Info
- Previous by thread: Re: Error in formula for custom field
- Next by thread: Re: Error in formula for custom field
- Index(es):
Relevant Pages
|