Primavera P6 Training
Developing project plans in Primavera P6 involves identifying the sequence or network logic in which your activities should occur. The network logic is strategic in the calculation of a Critical Path Method schedule, which is calculated based upon the activity durations and network logic (predecessor/successor relationships). The schedule’s early dates are calculated during the “forward” pass and the late dates are calculated during the “backward” pass. The “optimized” project plan becomes the basis for the “baseline” or target plan, which is utilized for performance measurement. This blog and Primavera P6 Training tutorial demonstrate the options for calculating the schedule when activities occur “out of sequence” thereby violating the network.
Retained Logic Versus Progress Override
The Primavera P6 Schedule Options dialog box enables users to select between Retained Logic, Progress Override, and Actual Dates to identify how Primavera P6 will schedule progressed activities. The video below demonstrates both Retained Logic and Progress Override options.
When using Retained Logic, the activity that starts out of sequence cannot finish until it’s predecessor has finished. The remaining duration of the out of sequence activity will be scheduled to begin after the predecessor is scheduled to finish. Retained Logic respects the network logic.
When scheduling using Progress Override, Primavera P6 ignores the relationship between the activities and schedules any remaining duration of the “out of sequence” activity from the data date.
The Primavera P6 Training Tutorial video below demonstrates scheduling the remaining duration of “out of sequence” activities using both Retained Logic and Progress Override.