Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Microsoft Project and the As Late As Possible (ALAP) Constraint

1 reply [Last post]
Emily Foster
User offline. Last seen 1 year 46 weeks ago. Offline
Joined: 19 Aug 2011
Posts: 625
Groups: None

The default constraint in Microsoft Project is ASAP. This is the ideal for most forward scheduling situations. Here we look at the As Late As Possible (ALAP) Constraint http://ow.ly/XWd830aUwVd

Replies

Tom Boyle
User offline. Last seen 3 weeks 5 days ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

MSP ALAP's consumption of ALL TOTAL SLACK makes it pretty useless for CPM-type forward scheduling in my view.  If you are scheduling just-in-time material delivery for an installation that has some slack (not the TS=0 case shown in the example), then the ALAP constraint will delay the installation.  This is probably not what you intend.

MSP ALAP might be useful in a critical chain methodology, but those who are not explicitly managing feeding/project buffers should beware.

Just an opinion....