How do I prevent task bars from being split when resource is shared

[Spz1]

I'm a new user who would appreciate some help.

Background:
My project plan has it's own calendar with working hours specified. All tasks are defualted to finish-to-start relationship.I have a resource sheet from where I have assigned resource to my list of tasks.

Problem:
If I assign the same resource to two tasks that run during the same period MS project will automatically split the task bar of one task so that it runs before/after/both (effectively levelling resource for me). It might look something like this - [ ]....[ ]

Expected result:
I would like MS project to allow the tasks to run at the same time and with the same resource without splitting the task bar. Instead I would like the 'resource usage' to show that the resource is overallocated in hours for that day.


I would really appreciate any help that can be offered on this. Many thanks in advance.

Mark

 

[Spz1]

Just thought I would update this becuase I think I found the solution. Seems to have worked but if anyone thinks this action was ill-advised please let me know.

Tools > Level Resources

Then Select the 'clear all leveling' button

Hope this may help someone else - Should Project default to automatically level resource? Seems strange.

Regards
Mark

 

[JulieInMaine]

Hello Mark,

I would not recommend that you leave Project to automatically leveling. Go back to Tools > Level Resources, and set your leveling calculation to Manual. You can still use the leveling command if you need to -- but you'll need to go back to Tools > Resource Leveling, and choose the Level Now button to level resources.

The reason why project split the tasks was because your resource was overallocated -- assigned to two tasks which run concurrently and likely assigned at the maximum units. During the period that the tasks overlapped, the resource was assigned at 200% causing the overallocation.

I hope this helps.

Julie

 

[Spz1]

Many thanks for the comments Julie

Regards
Mark

 

[JulieInMaine]

You're welcome and thanks for the feedback, Mark.