Sign up for free and we’ll send you regular Tips & Tricks to help you get more from Primavera. The out-of-sync baseline is actually a common issue that you will run into once you get comfortable scheduling and start getting more experience using Oracle’s Primavera P6 software.Basically, the point to make here is that Planned Dates are not considered useful as P6 calculates them all for you at the beginning and they typically never match your actual dates.As well, when you mark activities as started and enter an Actual Start Date (the date the activity in reality started on), the Planned Dates get recalculated for other affected activities.As always, I welcome readers to contact us or connect with me over social media if you have any questions!Have you ever faced the challenge of reviewing a monthly schedule update that includes both progress updates and non-progress revisions?To effectively evaluate potential schedule impacts, a schedule reviewer needs to separate the progress updates from the non-progress revisions.
When you update or restore a baseline, however, the baseline’s original state is not preserved.
When you capture your baseline at a specific point in time with your project and want it to match exactly what you have on the Gantt chart, you’ll find a tonne of slippage between the baseline bar and the activity bars.
This happens because the baseline is calculated from the Planned Dates as mentioned above!
Below, in this sample project, the activity B1010 has been marked started and an Actual Start Date of January 7, 2014 has been selected, as opposed to the Planned Start Date of January 6: Once the project is scheduled and the data date is moved forward to January 7, you will notice that all the Planned Start Dates have changed: What is being demonstrated here is the irrelevance of Planned Dates in general because they never match the dates before and after a schedule update takes place.
They always move in accordance with the changes and new Data Dates.