the best adjustment will be replacing the current fs logic to ss/ff+lag to maintain the integrity of the sequence of work.

do you correct the logic in baseline as well or just in the updates ? shouldnt you make sure that this logic adjustment does not affect the baseline project finish date ?

http://www.bazarek.nl/user/profile/4708

1- i have an out of sequence, an activity still on progress and the successor activitiy has been completed by submitting an undertaken letter. meanwhile, the on progress activity still showing and driving the delay of the project, and primavera expect it to be finished before the project completion date. so why there is delay !!
2- i had a lot of oos activities, and i have changed the links, when i submitted a notice of delay to the consultat, he rejected the update due to changes in the relations. it seems that he was not revising the weekly submitted soft copy of the primavera file.
3- what is the best way to measure the progress % complete ? is it the cost ? or the duration ? or labour unit % complete?

thanks in advanced.

regards,

http://ow.ly/ziprq

but when you filter you found a lot.

so please let me know what that guy did in the option of the schedule?

thanks sean,

what you said is correct and logical. but generally i think we required prior consent from client for this kind of scheduling.

also could you please suggest me some references about this practice. so that i could convince my people over here about this practice.

thank you so much and will be watching the blog closely for these kind of informative tips.

regards
mimoune

the update tracks the progress of a project and is supposed to adapt and change to what is going on with said project, whereas the baseline stays untouched. you must certainly fix any out-of-sequence progress encountered with the project because the update is not always going to track what the baseline laid out. this is very common in most forms of construction and is expected to be implemented where necessary. remember, the baseline is the original plan for the project and it is a best case scenario for the buildout of the the project. the update is as built status, current forecast and future forecast that changes with the project.

any delay notices should be based off the update, although you can also show delays in a copy of the baseline for some forms of delay analysis.

so on which program we will prepare the eot.
based on which program dates we can send delay notices?

that would be assuming the logic tie is a ss relationship. with the predecessor activity not complete, it will still drive the successor properly which is shown above in the example.

i would not advise switching between the retained logic or progress override setting on any project regardless of the out-of-sequence activities. you need to check what the contract specifies for which option is to be used and that setting should be used for the duration of the project. most projects will specify the use of retained logic.

thanks for your comments. maybe i should have used a different example. typically, as a contractor, we do not get schedules from the general contractor and we need to track the key predecessors to our work (work by others that drives our work) in our schedule. in doing that we do not put the complete activity in but, just the predecessor. so in a case where the work by others is not complete and ultimately holds up our work, we leave the out-of-sequence work in place to show that we still need that predecessor to finish before our work can complete. i hope that is clearer.

larry,

to your first question, yes, the out-of-sequence work should be corrected even if one of the activities in question is complete. it is good practice to review all out-of-sequence work each update period to make sure you do not have a very long list (of oos) as well as not to have any remaining duration pushing through complete activity logic. the effect on the critical path will be that you have good forecasted end dates and not any issues of out-of-sequence working inadvertently pushing out any work that is not complete. in regards to the second question, you cannot ask for compensation until you have used up all available float (you’ve gone negative) and this can be quantified by comparing your current update to the baseline schedule to see if there has been a delay issue. out-of-sequence logic does not necessarily cause negative float but, it can use up available float very easily and the more out-of-sequence logic you have the more issues you will have with incorrect forecast dates and less available float for all the activities tied to the out-of-sequence (in question).