Incorrectly split task for shared resource

[KevininNH]

I work in a group where all project schedules are linked to a single resource
pool. I have assigned a task to a shared resource (a lab technician)
starting in early June. Project is splitting that task in my schedule, which
I would normally take to mean that the technician has conflicting tasks in
other project schedules that are also linked to the resource pool. However,
when I look at the pool, he does not have any hours scheduled for other
projects during that time frame.

How do I get my task to show up in the resource pool, and/or how do I keep
Project from splitting the task? Any help will be greatly appreciated.

Regards,
Kevin Fredette

 

[Dave]

Does Project split the tasks as you enter them? If so you may have
levelling set to automatic (tools/levelling/manual to turn it off).
Otherwise at what point does the splitting occur?

If you remove levelling for the affected tasks, do the splits go away?
And at that point, what does Project think of your resource's scheduled
hours for the affected periods?

 

[KevininNH]

Levelling _was_ set to automatic, and turning it off for the selected task
does remove the split. As far as I can tell, it didn't screw up any other
projects linked to the common resource pool.

Thanks for the help!

Kevin

 

[Dave]

But it must have done it because it thought your resource was
overallocated. Was the levelling set to anything lower than
week-by-week? And do the hours worked by your resource now each week
seem plausible. It's easy to get the Gantt bars in visually pleasing
places, but harder to get a plausible plan.

Dave

 

[KevininNH]

Automatic levelling is set for day-by-day. And the hours worked by that
technician do show that he's overallocated during the time period for these
tasks. But that reflects reality. That is, we have one tech and 4 projects
that he has to work on in that period. In the unlikely event that the other
projects stay on schedule and no other frantic emergencies come up, I suspect
that my project will actually take priority during that time because I'm the
furthest behind. So I'm going to leave the "overallocation" as is for now.

Kevin