comments on: as late as possible constraint: how to use it in primavera p6 [video] - 瑞士vs喀麦隆足彩赔率

by: fred

tue, 25 oct 2022 21:57:00 +0000

in the example you use, add a task e (duration 3 days), as a fs successor to d. then make task d alap.

will both tasks d and e be pushed against the finish milestone?

as wagas above mentions, the answer in ms project would be yes.
but if my understanding of your explanation is correct, in p6, the answer would be no.

]]>

by: roberson

tue, 12 apr 2022 02:50:50 +0000

waqas. esta correto, ele consome apenas o free float, que seria a data mais tarde possível]]>

by: waqas

wed, 30 mar 2022 01:03:24 +0000

i am trying to use alap on ms project and noticed it eats up not only the free float, which is what i want but also total float and moves all the subsequent/successor tasks on the critical path. which defeats the purpose as i still want the successors to be on the earliest date driven by other predecessors

]]>

by: waqas

wed, 30 mar 2022 01:01:18 +0000

michael lepage. what a good way to move activities that you want to start as late as possible then? use lag from some predecessor like "project start"]]>

by: michael lepage

thu, 28 oct 2021 21:05:24 +0000

evangelos kourentzis. evangelos - thanks for sharing! i don't know that i would always remember to remove, reschedule, then add the alap constraints back. i would likely forget.]]>

by: evangelos kourentzis

mon, 25 oct 2021 12:54:11 +0000

other than procurement activities, i found alap activities very usefully to show early work that should not drive the plan but need to know when to start them:
1) an example is: start an alap 20 d. draft report before you “finalise a report”, then have the last input / predecessor driving the “final report”. this way you don’t use ff relationships with lags , logic is clear to engineers that see pdf plans and criticality remains through your last input your need. it is like an alarm for them.
2) a lot of times consultants will start working on something much earlier than planned because they are waiting for data on something else. by doing so, they want to bring future activities forward, show progress or budget spent to the client, without breaking logic, or mess around with the critical path for when they can have the last predecessor/input of an activity. adding an alap shows this work and maintain the logic.

in regards alap shown on the longest path, i “solved” this by having a filter to temp remove the alap constrain, just before i reschedule and plot longest paths, then apply it again.
fiddly but effective.
also having (alap) on the name of the activities helps with non p6 users to understand why this activity has 0 tf when they see a pdf

all this, of course, show a project that keeps changing; more agile (which are the projects i have worked on) and it may not be appropriate for many other projects.

]]>

by: bill morales

wed, 04 oct 2017 15:04:53 +0000

michael;

alap constraint could be used for procurement activities, but the problem is that any activity that i applied alap constraint its free float now is zero. so in this circumstance, i prefer to use any lag on the relationship of its predecessor and keeping the activity out of the critical path. what do you think?
regards,

bill morales msc cce

]]>

by: michael lepage

thu, 16 feb 2017 14:21:03 +0000

rich ginder. thanks for the comment rich. probably i should have added a bit about minimizing your use of the "alap" constraint. in fact, now consultants are criticizing the use of any constraints and possibly that's justified. i advocate for limited use of alap in specific circumstances, when activities are not on the cp or near-critical.]]>

by: rich ginder

thu, 09 feb 2017 13:43:21 +0000

schedule consultants always criticize the use of “as late as possible” constraints when evaluating baseline schedules. however, i do see some merit in using them in particular instances such as permit acquistion activities that have expiration periods. for example it is not realistic to apply for permit good for 6 months if it is not needed for another year. if the only true predecessor is ntp for this permit activity and its only true successor is a construction activity that occurs next year, then the “as late as possible” will push the early start date of the permit activity to when it will be needed instead of 1 day after ntp.

the downside of “as late as possible” constraints is if the successor activities are on the longest / critical path, then the “as late as possible” constraint will artificially make that activity critical and will show up on longest/critical path printouts.

i wish p6 had the capability of selecting certain activities for a “planned start/finish” that is neither the earliest or latest possible dates where the green bar for select activities can either be the early or the planned start/finish dates at the choice of the user. this would be helpful for short term look ahead schedules.

]]>