Re: ALAP scheduling
- From: "Jan De Messemaeker" <jandemes at prom hyphen ade dot be>
- Date: Fri, 28 Sep 2007 22:17:41 +0200
Hi,
ALAP is a possible constraint in Project too.
You can try setting this constraint for your testP's (or have you already)
Then they inded "bump up" against test1 but (is this the origin of your
question? you definitely didn't phrase it like that) then test1 goes on the
move and becomes a
critical task.
This may be alap in its stricted sense, but it is not JIT which you seem to
look for.
Sorry but "glitch" or not, Project cannot exactly simulate what you look for
(JIT scheduling)
What's even more of a pity when I discuss with MS people they do not
recognize the problem, chances to see this corrected are very slim.
There are (very poor) workarounds like making test1 the predecessor with a
SF relation to the testp's but they make a phony plan, not modeling reality.
Again, I regret this as much as you.
Hope this helps,
--
Jan De Messemaeker
Microsoft Project MVP
http://users.online.be/prom-ade
"JPD" <jdescant@xxxxxxxxx> wrote in message
news:1191008778.069328.193630@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
So here is what I am trying to do:
We have a task Fab1 that has to be done before Test1 can begin.
Test1 has predecessors TestP1, TestP2, TestP3, TestP4. That all have
a path to Test1 as there successor.
If I schedule Test1 ASAP and all the TestPs ALAP, they should all bump
up against Test1's start which is driven by the Completion of Fab1.
This is a typical Fab & Test cycle, where a number of meetings, plans,
etc need to be done before product received. There is no relationship
to Fab1 and the TestPs.
This would have worked fine using Primavera, is this another Project
quirk ??
.
- References:
- ALAP scheduling
- From: JPD
- ALAP scheduling
- Prev by Date: ALAP scheduling
- Next by Date: Re: Microsoft project 2003 - progress lines
- Previous by thread: ALAP scheduling
- Next by thread: Re: ALAP scheduling
- Index(es):
Relevant Pages
|
