Second task must start after first but not immediately (dynamic lag)
Let us say I have 3 tasks (A, B, C), all of them occupy 100% of the resource "CAESAR". Task A must be completed before any of task B or C can even start. Task B or C can be completed any time before the project ends, but can start much later (but not before as said) the time when task A ends.
I can of course link those tasks via Finish-to-start (FS) (EA in German) - that enforces the task B to start immediately after completion though. I could add lag time, but to my knowledge that is an exact lag, and not a minimum (such a "dynamic" lag would be 0 days in my case, since both tasks B and C could but not have to start immediately after A finishes). The bigger problem, however, is this: When I link both B and C to the finish time of A via FS, I always get resource conflicts since B and C are then set to BOTH start at the end of A, which is not possible as the resource (here "CAESAR") is required 100% by both tasks. I can resolve them manually of course, but I would have expected C to start after B then by default (as it is in the row below B, see red box in attached screenshot). Is there a way to achieve this?
|