Why does MSP2003 split the end of a task

[davidd31415]

I am using a 24/7 project calendar, 24hr work days, fixed duration / effort-driven tasks.

MSP2003 is splitting the end of a task on me and I do not understand why.

Here is an example:

With the above settings, I create two 5 days tasks.
I add one resource with a standard calendar.
I assign the resource to both tasks.

The first task looks fine. The second task levels to the proper position, starting right after the first task but only shows work for the first 2 days; after that it looks like a split but it stays like that into the weekend.

I've seen this behavior where another task with the resource starts on the same day the splitting task starts to split.

Any ideas?

Thanks,

Dave

 

[davidd31415]

While experimenting I noticed that the first task starts on a Thursday. 24 hours of work is computed when the resource is assigned (8hr thur, 8hr fri, 8hr mon). The second task also ends up with 24 hours of work when its resource is assigned (1hr tue, 8hr wed, 8hr thur, 7hr fri).

I'm think the 24hr work might have been computed for the second task using its original location so even though 32hrs could have been performed only 24 is and the split at the end comes in since all the work is completed before the duration ends. I don't understand why the 24hr number would be calculated before the task is moved by leveling/resource assignment.

I am more confused why 8hr of work is not performed on Tue though. The first task completes on Mon (finish date of Tue). The second task starts on Tue but has only 1 hour of work that day (at 4pm).

 

[PDQBach]

I need a bit more info to create a test project.

For the project, I need to know Project Calendar, Tools | Options | Calendar-tab (hours per day, hours per week).

For each task I need to know start date, duration, work, resource(s) assigned, Calendar, constraint date, constraint type, predecessor(s)/successor(s), lags

For each resource I need to know Calendar, resource availability.

 

[davidd31415]

I just recreated this with MSP2000.

Work starts on: Sunday
Default start time: 12:00 AM
Default end time: 12:00 AM
Hours per day: 24.00
Hours per week: 168.00
Days per month: 30

24hr project calendar

Resources (1):
1. Standard calendar
No availability set (I received the same results when setting it)

Tasks (2):
1. Start date: 5/16/07
Duration: 5 days
Work: 0
Calendar: none
Constraint date: 5/16/07
Constraint type: Start no earlier than
Predecessor(s): none
Successor(s): none
Lag: none
Type: Fixed duration, effort-driven

2. Exactly the same as task 1

At this point I assign the resource to both tasks. The work field is then 24 hrs for both tasks. Task 1 starts on Wednesday and ends on Monday. Task 2 starts on Monday and ends on Saturday. The resource is scheduled for only 1 hour of work on Monday (for task 2). Task 2 splits on Thursday after 7 hours of work and continues to show split (......) until Saturday. My first questions: why does task 2 split like that and why doesn't task 2 start on Monday at 8AM ?

---

I have found that the start date changes this behavior. I remove the resources and start both tasks on a Monday (5/14/07). Next I assign the resource to task 1- 40 hours of work will be performed on it over 5 days. If I then assign the resource to task 2, 40 hours of work will be done on it as well but task 2's duration changes to 7 days. The task starts at 4pm on Monday and continues until the following Monday on which 7 hours of work are performed. The "end split" no longer shows up. Why does the duration of task 2 (a fixed duration task) change to 7 days? (I have not tried this one on MSP2003 yet).

---

A few more things that have confused me that can easily be recreated with this test project:


Remove resource from both tasks. Ensure both tasks have a duration of 5 days. Set the work for both tasks to 40hrs. Assign the resource to both tasks. The first task looks fine but the second task ends up with a duration of 18.71 days and a total of 40 hours- it continues to start on the same date the first task starts on but the resource is assigned at 33%, scheduled for 2.67hrs of work even during the 2 weeks after task 1 is complete! The resource is over-allocated for the first week. When assigning the resource, project prompted that it could not resolve the over allocation. Why the over allocation?

If the resource is removed from task 2 and task 2 is reset to 5 days, 0 hours, and the resource is re-assigned, NOW task 2 schedules 40 hours of work, starting with 1 hour of work on Mon of the following week similar to the first situation. The duration is 7 days. Why the different behavior with 0 hours of work in the task before assigning?

I realize there are a lot of questions here and appreciate help with any of them. I don't mind reposting them in individual threads later but wanted to get them all documented at one time since I feel like every thing I attempt to do results in a new failure here!!

Perhaps there is a golden rule of project that I don't know about like "don't use standard resource calendars with 24hr project calendars" but I would like to learn what to do / what not to do to ensure that I don't run into problems like these when working with a complex project.

Thank you!

David

 

[PDQBach]

It will take me a couple of days to "play" with this one and your other question in a different thread. I'll get back to you when I've got something.

In the meantime, if anyone else has thoughts, suggestions, etc., please add your comments.

 

[davidd31415]

Thanks for the support PDQBach, I hope you have some luck.

In the meantime I am thinking about picking up Microsoft Press's "Troubleshooting Microsoft Project 2002." Not a version I work with but the TOC looks promising with entries such as "automatic leveling makes changes I don't want."

Does anyone have recommendations about this book (or the other MSPress Project books) ?

Dave