(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.
Dear All,
i have read a topic about delay analysis mentioning one of the tricks that the contractor use to his favor when issuing a claim.
That to sequence the activities that are potentially can be delayed by the owner so that the critical path pass thorough these activities.
Does anyone know hoe to practically apply this , a trick to force an activity on the critical path?.
Printer-friendly version
Send to friend
Keep in mind that an activity with a "as late as possible" constraint is driven by its successor. The activity will be critical if its successor is critical but the driver remains the successor instead of the predecessor!
ALAP constraint in different software may work in different ways.
http://www.planningplanet.com/forums/microsoft-project/691256/alap-constraint-behavior-question
Tue, 2018-09-18 09:36
Tom Boyle
When used in a forward-scheduled project, the ALAP constraint in MSP is in fact a Zero-Total-Float constraint, which serves no useful purpose as you have found.
A restriction you impose on an activity or work unit with positive float that allows it to start as late as possible without delaying its successors. This constraint sets the early dates as late as possible without affecting successor activities.
- This means that if successor is not critical the activity does not becomes critical.
Just changing the status of the task to ALAP will turn it critical.
If using P6 changes in calendars can be difficult to detect, it is an easy way to delay activities.
The Claim digger or Schedule Comparison is a widely used tool in P6 to compare between two projects and detect the differences.
One of the main shortage of the Claim Digger or the Schedule Comparison tool is detecting the changes in calendars.
The tool will not detect any revisions in calendars working hours or changing from Project to Global calendar if both have the same description.
Claim Digger will tell us nothing about calendars other than whether the name of the calendar is different.
http://www.planningplanet.com/blog/detect-changes-made-calendars-between-two-projects-p6
If the Schedule/Program has been approved this way there is nothing you can do about it.
However you should check that the contractor did not submit a modified Schedule/Program just before he submited his claim. It is possible for him to change logic of the network, without changing dates, in order to favor him...but again this is a gray area from my point of view...it depends a lot on contract form and provisions.
This also depends on type of works, in Civil engineering less likley, in Road projects and Water Waste it is possible with relative ease.
Email: PPadmin@planningplanet.com
Replies