Consistently enforce summary link at task level

[awmccready]

If I establish a finish-to-start link at the summary level, then that link
should be consistently enforced by MS Project at the subordinate task level.
For example, if I have a resource of type work assigned to tasks subordinate
to each of two summary levels, then I currently get an incorrect
overallocation for that resource, even though that resource has sufficient
remaining time available to work. To remove the overallocation, I must
establish a direct finish-to-start link between the task in the predecessor
summary level and the task in the successor summary level. Only then does MS
Project schedule the subordinate task in the successor summary level to start
after the other task has finished. The finish-to-start link at the summary
level was ignored. This behavior may currently only exist when the two tasks
involved are scheduled by MS Project to occur on the same day.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...0070d77&dg=microsoft.public.project.developer

 

[Brian K - Project MVP]

If I establish a finish-to-start link at the summary level, then that link
should be consistently enforced by MS Project at the subordinate task
level.
For example, if I have a resource of type work assigned to tasks
subordinate
to each of two summary levels, then I currently get an incorrect
overallocation for that resource, even though that resource has sufficient
remaining time available to work. To remove the overallocation, I must
establish a direct finish-to-start link between the task in the predecessor
summary level and the task in the successor summary level. Only then does
MS
Project schedule the subordinate task in the successor summary level to
start
after the other task has finished. The finish-to-start link at the summary
level was ignored. This behavior may currently only exist when the two
tasks
involved are scheduled by MS Project to occur on the same day.

I have tried and cannot get a project in to a state where a summary to
summary finish to start link allows for sub tasks within these two
summaries to be scheduled to happen at the same time unless I set the
actual start date of the successor's sub task back in time. Can you
explain more about how you are getting this problem?

 

[awmccready]

Brian, I will try to work something up. I will have to roll that small
project back in time to get the conditions I wrote about. Otherwise, I will
have to create an artificial test. Either approach may take some time. Bear
with me.

 

[Jan De Messemaeker]

Funny. This is the second post I read tonight claiming that subtasks extend
out of the range of summary tasks, something I have never ever seen.
I'm really going to experiment tomorrow trying to create this anomaly.

 

[awmccready]

Unfortunately, I cannot yet recreate the problem either with a dummy project.

I just tried creating a dummy project with two summary levels, two tasks and
a completion milestone for each summary, and three helpers. The second task
and last non-milestone task for summary 1 and the first task for summary 2
were assigned to the same worker 2. Each task was given a duration of 3 or
less hours, so that at least two tasks could be assigned to the same worker
in the same day without over allocation. I used the standard calendar for
all resources. I created FS links for each of the tasks in summary 1. I did
the same for summary 2. Of course, without an FS link between summary 1 and
summary 2, worker 2 was highlighted in red on the resource sheet. However,
when I created an FS link between summary 1 and summary 2, the over
allocation for worker 2 disappeared and the red highlighting changed to black.

Unfortunately, I did not save a snapshot of the other project where I
encountered the original issue, so I may not be able to recreate the problem
I reported. However, for that project, I modified the standard calendar, but
I believe I used the same modification for all resources. I also had
material type resources. If those differences will not allow recreating the
problem reported, then, the problem is probably intermittent or dependent on
a particular sequence of events, rather than the nature of the events.

If and when I get time, I will attempt to recreate the problem with the
original project and the dummy project.

Since the over-allocation condition in the original project disappeared only
when I created the FS link between the individual tasks in the linked summary
tasks, then it is most likely that the condition should never have occurred.
I assure the reader that I actually encountered the problem.

 

[Jan De Messemaeker]

Hi,

Whetever was done in the "faulty" project, the origin of the problem MUST
have been calculation being OFF or the presence of a cricular relationship
(which also ends the calculation).
In a non-corrupt file, with calculation ON, never will a subtask extend
beyond the borders of a summary task.
HTH
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620

Unfortunately, I cannot yet recreate the problem either with a dummy project.

I just tried creating a dummy project with two summary levels, two tasks and
a completion milestone for each summary, and three helpers. The second task
and last non-milestone task for summary 1 and the first task for summary 2
were assigned to the same worker 2. Each task was given a duration of 3 or
less hours, so that at least two tasks could be assigned to the same worker
in the same day without over allocation. I used the standard calendar for
all resources. I created FS links for each of the tasks in summary 1. I did
the same for summary 2. Of course, without an FS link between summary 1 and
summary 2, worker 2 was highlighted in red on the resource sheet. However,
when I created an FS link between summary 1 and summary 2, the over
allocation for worker 2 disappeared and the red highlighting changed to black.

Unfortunately, I did not save a snapshot of the other project where I
encountered the original issue, so I may not be able to recreate the problem
I reported. However, for that project, I modified the standard calendar, but
I believe I used the same modification for all resources. I also had
material type resources. If those differences will not allow recreating the
problem reported, then, the problem is probably intermittent or dependent on
a particular sequence of events, rather than the nature of the events.

If and when I get time, I will attempt to recreate the problem with the
original project and the dummy project.

Since the over-allocation condition in the original project disappeared only
when I created the FS link between the individual tasks in the linked summary
tasks, then it is most likely that the condition should never have occurred.
I assure the reader that I actually encountered the problem.

 

[awmccready]

"Calculation" was and still is the default, "AUTOMATIC". There was and is no
circular relatipnship.

While there is always the possibility that the project or my installed copy
of MS Project is or was corrupt, that has not been established. Moreover,
the possibility that MS Project was implemented incorrectly in this matter
has not been disproven, although it much less likely that MS Project was
designed incorrectly.

In any case, thanks for your time, opinion, and feedback.