FS Relationship not working

[CM WM]

I have a task (ASAP constraint) with FS relationship to three predecessors.
The latest finsh date of all three predecessors is 6 Sep 07. But the task
starts on 24 Sep 07.

If I change the constraint to ALAP and then back to ASAP, the task moves to
6 Sep 07, as expected.

Calculation is set to automatic; "Autolink Inserted or Moved Tasks" is set
to off; I'm using MS Project Standard 2003 11.0.2003.0816.15.

This is only one task, but I'm concerned this problem is recurring
throughout the rest of the project.

Can anyone help? Am I missing something simple?

 

[Jack Dahlgren]

Is calculation set to automatic?
Hitting F9 will recalculate the schedule, but try going to tools menu /
options / calculation tab and see what the calculation mode is set to.
Switching to ALAP and back forces a recalc so I wouldn;t be surprised if
perhaps you have the mode set incorrectly.

-Jack Dahlgren

 

[CM WM]

Thanks for your time Trevor. The additional info you requested is as follows:
1. The particular task that is mis-behaving is scheduled ASAP, as are two of
its three predecessors. The third predecessor is an external
(customer-specified) milestone and is scheduled "start no earlier than".
There are other tasks in the schedule that are scheduled "start no earlier
than"; for example, other customer milestones and tasks that have been
re-scheduled to the current date. The only other type of constraint used in
the schedule is the constraint arising from work having been statused as
complete. (the task in question is 0% complete)
2. Leveling is set to "manual", and calculation is automatic.
3. There are no lags on the predecessors for this task. The single
successor is FS+0d.
4. I checked the calendars and there are no non-working days (except for
week ends) associated with the Project Calendar or the Resouce Calendar
associated with the resource for this task. All Tasks have "none" nominated
in the calendar field of the Advanced tab in the Task Information dialogue
box.
5. When I mentioned the "latest finish date of all three predecessors" I was
meaing to be literal. I wasn't referring to MSP terminology.
6. I agree there must be someing else holding this task out ... I just can't
find what it is.

I've also checked that I don't have any predecessors associated with summary
tasks. The fact that changing the task to ALAP (or MFO or MSO or FNET or
SNET) and then immediately back to ASAP tends to indicate there is nothing
obvious holding it out.

Interstingly, it isn't fixed if I change the constraint to FNLT or SNLT (and
allow the subsequent conflicts) and then change it back.

I've tried opening it on another PC in case my softwre is corrupt, but it
behaves the same way.... as do several other tasks around this one.

Perhaps there is some "scheduling conflict allowed" to apply to these tasks?

regards,

Wayne

 

[CM WM]

Thanks for your help Jack.
I've definitely got calculation set to automatic, and leveling is set to
manual.
I've also checked that I don't have any predecessors associated with summary
tasks, and there are no lags associated with the predecessors, nor are there
holidays in the calendars around this time. Changing the task to ALAP (or MFO
or MSO or FNET or SNET) and then immediately back to ASAP fixes the problem.
Interstingly, it isn't fixed if I change the constraint to FNLT or SNLT (and
allow the subsequent conflicts) and then change it back.
regards,

 

[CM WM]

Some more info that might help: the Early Start date for this task is correct
(6 Sep 07 - the date that the last predecessor finishes). But the start date
is 24 Sep 07, and the Late Start date is 17/12/07.

 

[ahelp]

One question Trevor asked that I don't think you answered is the "Schedule
from" setting under the Project menu, Project Information. It should be from
Project Start Date w/ all tasks beginning ASAP.

 

[CM WM]

yes, the Project Information window under the Project menu shows
"Schedule from: Project Start Date" and has text below stating "All tasks
begin as soon as posisble".

 

[CM WM]

It looks like the best solution is to paste everything into Primavera.