Predessor logic

[AntzyClancy]

This is a little complicated. Let’s say I have 5 or so separate installation activities that each require the same WAP approval. Each of the these 5 activities have completion dates that move around a lot. I’d like the WAP done 10 days before the earliest of these 5 activities. How do I tie these together?

The way I’ve done this in the past is to add a predecessor to the WAP task with a “SF-10day” qualifier. Trouble is that this only works with a single activity, which requires me to constantly evaluate all of the activities to determine which is the first to start. If I use the same qualifier on multiple activities in the WAP task predecessor field, the WAP due date becomes driven by the latest activity, not the earliest.

 

[johnherman]

Here's a possibility. Add a Milestone task for the approval. Make each of the 5 dependent tasks dependent on the approval with a mandatory lag of 10 days.

====================================
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright

 

[AntzyClancy]

The approval is a milestone. Your suggestions makes the 5 tasks dependent on the approval. I want the approval dependent on the 5 tasks, but to occur 10 days before the start of the earliest of the 5 tasks.

Thanks for trying.

Todd

 

[JulieInMaine]

Hi Todd,

A task may have multiple predecessors. Have you tired setting the 5 installation activities as the predecessors (Start to Finish) to the WAP task?

As a quick comment, using SF relationships should model your need - but in most circumstances require some psychic abilities that most of us don't have. If the installation tasks moves to 8 days before today -- do you really think you can move the WAP task two days into the past?

Can you do an installation without a WAP approval?

Julie