Let us know if you've used the Update Baseline Feature, and in what context. Also, we cover updating projects, and making change requests extensively in our new Advanced Progressing course: www.planacademy.com/course/advanced-p6-progressing/
I've used update baseline for correcting minor errors in the baseline programme after the project has started (in the early stages of project going live).. such as a non critical duration or incorrect date.. but even still ive only done this once or twice
Here is the challenge: what if the U5 shows the contractor is behind the schedule and CR1 is for some additional work? By adding CR1 to U5 and considering it as the B2 you (as the owner) are kinda accepting the delays caused by the contractor.
It is accepting delay but not taking responsibility for the delay. There is no point a Client putting their head in the sand. It is not a case of accepting delay, it is more a case of the Client accepting the Contractor's delay to open up discussion on how to mitigate it.
When a deviation caused by outside factor like weather occurs (or similar event), and it is acknowledged as per contractual procedures (typically NEC3) and suitably compensated for, then I believe an updated baseline can be (or should be) stored to acknowledge changes affected / effected and agreed upon, plus it leaves a good auditable history .... [my thoughts]
I think we can do a new baseline without actuals by adding the new tasks to BL1 . This is what we used to do in our projects. So we have BL2 but without actuals
I just started working with a major utility and I was surprised to find update baseline in their procedure. My experience was like you stated. There use is to update at a gate milestone. The purpose is to show variances in the past but zero variances after the gate. I was told testing was done last year to verify. I’m skeptical so I was checking videos. Maybe it works now ?
I agree with "never change B1". However, taking a new Baseline will erase the sins of the past. One option is to keep B1 Locked & take another as a Control Baseline & use the update feature to incorporate the new tasks to show the revised plan. Assign the CR-1 schedule as the project Baseline & the B1 as the B1 User baseline. However, the update baseline feature does generate errors..... when in doubt, Excel it out! lol
The sins are indeed in the past. As a programme you are not interested in whats on the left, only what is on the right hand side of the programme. The sins are still inherited in the new programmes, that can't be escaped from.
Let us know if you've used the Update Baseline Feature, and in what context.
Also, we cover updating projects, and making change requests extensively in our new Advanced Progressing course:
www.planacademy.com/course/advanced-p6-progressing/
I've used update baseline for correcting minor errors in the baseline programme after the project has started (in the early stages of project going live).. such as a non critical duration or incorrect date.. but even still ive only done this once or twice
Hey thanks for letting us know, Simon.
Here is the challenge: what if the U5 shows the contractor is behind the schedule and CR1 is for some additional work? By adding CR1 to U5 and considering it as the B2 you (as the owner) are kinda accepting the delays caused by the contractor.
It is accepting delay but not taking responsibility for the delay. There is no point a Client putting their head in the sand. It is not a case of accepting delay, it is more a case of the Client accepting the Contractor's delay to open up discussion on how to mitigate it.
When a deviation caused by outside factor like weather occurs (or similar event), and it is acknowledged as per contractual procedures (typically NEC3) and suitably compensated for, then I believe an updated baseline can be (or should be) stored to acknowledge changes affected / effected and agreed upon, plus it leaves a good auditable history .... [my thoughts]
I think we can do a new baseline without actuals by adding the new tasks to BL1 . This is what we used to do in our projects. So we have BL2 but without actuals
I just started working with a major utility and I was surprised to find update baseline in their procedure. My experience was like you stated. There use is to update at a gate milestone. The purpose is to show variances in the past but zero variances after the gate. I was told testing was done last year to verify. I’m skeptical so I was checking videos. Maybe it works now ?
Sorry - no idea if it's fixed or not. You can check the Primavera P6 Cummulative Update Tool - google that.
I agree with "never change B1". However, taking a new Baseline will erase the sins of the past. One option is to keep B1 Locked & take another as a Control Baseline & use the update feature to incorporate the new tasks to show the revised plan. Assign the CR-1 schedule as the project Baseline & the B1 as the B1 User baseline. However, the update baseline feature does generate errors..... when in doubt, Excel it out! lol
The sins are indeed in the past. As a programme you are not interested in whats on the left, only what is on the right hand side of the programme. The sins are still inherited in the new programmes, that can't be escaped from.
Hi, unable to assign baselines, under project baseline button is locked. anyone can help