I don't know if I'm helping you but with all this rhetoric, does this
In my mind it does. This stuff is awesome.
I had a meeting this morning and my head is buzzing with insight.
P.S. Who is Al Wallace and where did you say that gold was?
Al Wallace posted in the last couple days.
Currently, we can only set/see task dependencies. How can we show resource
dependencies? For instance, I have two >>tasks for Fred. Fred is the only
one I have currently available to work those tasks. The tasks themselves
are not related, and one should be completed before the other begins.
However, the >>tasks themselves are not dependent upon one another. They
are dependent on Fred, though.>>
Sorry that really doesn't directly address the input of actuals which you
replied to. But it is central to the two concepts that are in my head right
now(and may be working at cross efforts).
Al Wallace was wanting a report that outlined resource dependencies as a
tool to make alternative resource decisions. As it applies to our current
conversation that would represent the outsourcing. Non existent resources
until there is an overallocation. That is long lead time manufacturing you
don't know "what and when" you need specifically until you get there because
shit has happened all along the way. I realize now I need project to
automatically substitue resources in order to calculate a "best fit"
constrained be end date. If that means weighting the resource suitablity or
something like that I'd love to know about it.
P.S. Who is Al Wallace and where did you say that gold was?
The gold is all over the place. Come get some if you can stand the cold,
bugs and loneliness.
The bulldozer stuff I made up. But the concept is the same.
Lets say each bulldozer needed to progress through five tasks spaced amongst
a total of five hundred that relied on a single resource
during a year build.
Lets make the resource up for clarity
An extremely articulated long reach gundrill that cuts the bushing holes for
a power take off shaft.
This laser guided big bore long reach drill was $5 Million we only have one.
That was fine for the first year when we just used it
for the one PTO drilling operation per dozer but it does such a great job;
it now handles four additional tasks per dozer.
No problem as long as the scheduler does his job.
If that single resource was booked solid for
the full year and one buldozer's turn came up but it wasn't ready to take
it's turn. (The welder put the bucket bracket
1 inch too far left this morning)
I need the impact of that "actual" turn missed. The actual is him running to
the web screen submitting status/actual
work done this morning " = -3 " cause he has to take it off and reweld!
Now I spring into action.
What do I know? That the turn was missed.
"What-if"... I move the turn three days from now, just before the "extremely
articulated long reach gundrill" was scheduled for maintenance.
We always overestimate the maintenance duration a little.
Well that three day delay of course cascades down to a few hundred other
tasks but what stands out as most devastating is
missing a hydralic fitting session two days from now. So this recovery slot
won't work
Next option is I simply have to get it done in the next two days. But where
do I put it? A shift one way or another;
and I hope I've been graphic enough but I dare say an hour here or there
could swing the rest of the year huge amounts.
Maybe not for this dozer but tack on weeks on the Decembers Dozers because
I'll probably have to do this exact same thing again.
Those welders keep forgetting the thickness of the bucket bracket
reinforcement, argh kids!.
Third option is to bump everything. What is the result? that is what I need
project to tell me.
The only result that is unacceptable is a missed end date or an
overallocation.
That is a long winded example of how as I see that actuals are so vital. I
don't see it as a MICRO issue either. If I'm to
accomplish 3 custom machining operations of 8 hours each in a twenty four
hour day I'm pretty sure I need to know if the cutting speeds needed to
be reduced and each operation took 10 hours then I'm into the next day
right. That affects my plan, stack 100 projects under it pulling from the
same
resource pool and I can't imagine anything other than profound effects on
end dates. I do agree though that status expectations could be modelled to
take
place a few steps farther removed but where, to what end and where is the
break even point?. What is too short a time span for status input? I'm not
sure, but I can't
PLAN for one that is too long a delay as the resource utilization would not
be anywhere near what experienced humans making judgement calls can
approximate
without anything more than a general guideline. If long range impacts could
be seen at each of those continuously reported status requests
those experienced individuals would make even sounder judgements, meet more
and more oppresive end dates or ask for help(outsorce)
earlier, when it matters most. That's really the most basic question where
are we, enterprise wide.
Thus when first investigating Project Server the act of distributing the
status requests seem so vital to any kind of succes and I still believe
that.
But I still haven't resolved some other key issues about the capability of
Project. Unfortunately another recent post returned a "no" on that one but
I'm
still trying, to understand the Project landscape.
Whew, I'm beat.