Milestone driver - trying to show the earliest one

Thomas

you can make the Act. "Site started on" a Level of Effort Activity and link all Site Act. with SS.

Create the a new bar for the Act. "Site started on".

regards

Thomas

Santosh you are bascially doing the same thing that I have suggested. You stil have to assign a  code once you determine which ones drive to be able to filter for those. 

It is not clear if the question means milestone after the start of the predecessor that started earliest or milestone after the finish of the predecessor that finished earliest.

• The challenge gets more interesting if it means milestone after the finish of predecessor that finished earliest.  In the following scenario the predecessor that started earliest and the predecessor that finished earliest are different activities. 
• It gets more interesting if the challenge is for milestone after start/finish of more than one activities starts/finishes.
• Good model shall allow for successors to milestones to work as expected in any scenario. 
• Easy if using consumable resources.

There is a much simpler answer, that you can add the Relationship Free Float and Relationship Total Float columns into your PRedecessor window and then determine which relationship will drive..

http://www.austprojplan.com.au/relationship-float-and-viewing-in-primav…

Thom:

Try this if nothing else works, you really need this functionality, and the site work activities are on their own WBS node or can be put on their own WBS node.

1. Create a WBS Summary activity for the site WBS work node.

2. Tie the milestone to the WBS Summary activity with a SS relationship.

This was the methodology I used to come up with this:

[[wysiwyg_imageupload:6026:]]

Let me know how it goes.

Raymund's suggestion seems like the best approach if the milestone exists solely to report the start of the collection of activities - i.e. for outputting a date on a table and/or bar chart.  Thom's initial question seemed to imply something different.  In any case, an attempt to flow schedule logic through a milestone constructed this way will have unintended consequences, as Rafael has pointed out.

The Purpose of the Subject ALAP milestone is to reflect the Earliest of the Group as required by Mr. Thom rather than Driving, Trailing or Leading a group of Activities. 

let me kow how that works out 

As per my prior posting.

• Be aware that the option to use an ALAP milestone as a predecessor to the activities is not a solution as it might be moved out of location if a successor to the milestone is added, a common suggestion by novice users.

So much effort for a milestone that add nothing to the schedule makes no sense, usually the need is for the milestone to drive other activities down the road.  If you add a successor to the milestone as to drive some other activity that other activity in some/many cases will move the milestone to the left.

Create a Milestone, Assign the different activities as Succesors. Set a Constraint for the Milestone as As Late as Possible.

The Milestone will always follow the First Activity.

add a code call it PRED  give it a value of P go to the milestone in the predecessor window make sure that the columns driving and critical are shown look of the predecessor that has BOTh the critcal and the driving box checked. Highlight that activity and select go to. Keep doing this until you get back to the data date the last activty that you find is the earliest predecessor. Assign that activity with the P code for PRED and you can now filter for that. Do this of the other 4 minestones

Be aware that the option to use an ALAP milestone as a predecessor to the activities is not a solution as it might be moved out of location if a successor to the milestone is added, a common suggestion by novice users.

In the following video you will see a model of your scenario where site activities are independent of each other and a successor activity is driven by the start of the earliest activity start. 

Easy if using consumable resources leveling.  Most mainstream software are stuck in the 1960's CPM functionality, few can deal with complex modeling of consumable resources.  In the following example the potential predecessor activities produce the consumable resources either at start/finish profile as required and the milestones start when enough consumable resources are created.

Novice schedulers do not understand consumable resources, novice schedulers do not understand spatial resources.

• Renewable and consumable resources

• Consumable and Spatial Resources Presentation

Thom,

Let's say you have a finish milestone with 5 FF predecessors, and you want the milestone to be scheduled (i.e. early finish) as soon as the first of the 5 FF predecessors finishes.  This is a common request among novice schedulers, but it's simply not possible (nor typically desirable) in P6, nor in any of the other mainstream project scheduling tools.

The way logic-driven scheduling works, ALL predecessors must be satisfied before an activity is scheduled.  Scheduling when ANY predecessors are satisfied - i.e. what you are looking for - would require some pretty major programming changes, and there's simply not a demand for it.  Experienced schedulers make the tool work just fine as it is.   

not sure I understand the question there are ealry dates and there are late dates you can show either

maybe you want to use the start on or before constraint date in this situation