Tasks which Conflict

[MAL]

I have a requirement to ensure tasks that have a conflict cannot be scheduled
at the same time. For instance a task such as "lighting matches" cannot be
scheduled when another task such as "repairing gas pipe" is active. We can
identify using an attribute that these tasks are subject to a conflict but
don't know of a way to instantiate a rule that says something like:

“Activity where ConflictType = LightMatch cannot be scheduled with Activity
where Conflict Type = Gas Pipeworkâ€

The idea is that Resource Leveling takes acount of a rule like this and does
not schedule the task concurrently. We have thought of a few work arounds
but nothing that's elegant. Any deep technical knowledge of how this might
be done?

 

[Dale Howard [MVP]]

MAL --

Resource leveling is used to resolve resource overallocations. It has
nothing to do with task scheduling, unless the tasks involved are assigned
to an overallocated resource. So, I doubt that resource leveling will
address your situation. The simplest way to address this situation would be
to set Finish-to-Start (FS) dependencies on tasks that cannot be concurrent
tasks. Beyond this simple solution (which may not work for you, by the
way), I cannot think of any other simple way to address this. A more
complex approach would be to write a macro that identifies the tasks you
have identified with the custom attribute, and then let the macro do a "task
leveling" procedure that reschedules these tasks so they cannot overlap. If
you think that is an option, you might want to repost your question in the
microsoft.public.project.developer newsgroup and allow our developer friends
to guide you. Hope this helps.