May be this problem is similar to a problem that I have met in Primavera project Planner.
the problem was: the Late Finish date is changed,
from my Experience the Late finish date should not change because this is your limit.
I discover after a while that this problem they have named it in primavera "Out of sequence problem".
Out of sequence can be happen if you update the progress not according to the relation you give(linking the activities).
How?
If an activity A is a predessor of B and linked by a Finish-Start relation(F.S).
And you update the Activity B(give actual date),before the Activity A Finish , you will find after sheduling that the Late finish has been changed ,inspite that it should be fixed.
To solve this problem , you should update according to the relations given, other wise change the link to reflict the actual situation of the Project.
Best Luck
Ali
-------------------------------
Member for
24 years 3 months
Member for24 years4 months
Submitted by Kevin Walker on Mon, 2001-07-23 05:48
Member for
23 years 9 monthsRe: MSP2k
Hi,
May be this problem is similar to a problem that I have met in Primavera project Planner.
the problem was: the Late Finish date is changed,
from my Experience the Late finish date should not change because this is your limit.
I discover after a while that this problem they have named it in primavera "Out of sequence problem".
Out of sequence can be happen if you update the progress not according to the relation you give(linking the activities).
How?
If an activity A is a predessor of B and linked by a Finish-Start relation(F.S).
And you update the Activity B(give actual date),before the Activity A Finish , you will find after sheduling that the Late finish has been changed ,inspite that it should be fixed.
To solve this problem , you should update according to the relations given, other wise change the link to reflict the actual situation of the Project.
Best Luck
Ali
-------------------------------
Member for
24 years 3 monthsRe: MSP2k
Additional investigation has led to the following observations:
1. Late dates and Total Slack (Total Float) calculate properly for activities that are "to-go".
2. Late Finish dates and TS calculate properly for in-progress tasks that are not "critical".
3. The "bad" dates and "bad" TS only show-up when the path hits a critical condition.