I think of the Actual Date option as middle ground between Progress Override and Retained Logic. It uses available actual dates rather than remaining date to perform the calculation. This will behave like retained logic for in-progress out-of-sequence tasks, but like progress override for completed out-of-sequence tasks. Stated another way, logic behind the DD is treated as if scheduling in Progress-Override and logic beyond the DD as if using Retained Logic. I typically use this option only when I need to record progress beyond the datadate and still want to show tasks progressed beyond the datadate with the driving indicator for the associated pred or successor. It makes active logic traces a little easier without completed tasks showing as driving unless there is duration after the DD. However, I agree that it's best to use Retained Logic for any "official" schedule reporting.
Actual Dates runs as Retained Logic until there is an Actual Date applied after the Data Date then that one activity is treated as Progress Override. Using Actual Dates allows the illogical use of Actual Dates after the Data Date while not flagging an error in the Schedule Log.
Actual dates : as the name suggests considers actualized logic to show impact . This is helpful when you actualize and update logic prior to rolling DD. Ex : We update our schedules weekly and make sure we address every current week planned activities (current filters on),give new forecast and only then roll Data date. "Actual dates" help in such scenarios.
When I Update the actual costs the costs in the previous period changes. Why?. How do I make p6 to maintain the previously entered values when I entre the current values
Regardless whether retained logic or progress over ride, the actual should be before the data date. Activity H is done, so to my understanding activity H should be before the data date?
Hi Michael, thanks for useful videos. I have questions there. Is it correct way if we use all 3 options (depends which we need) during the progress updates? I mean, firts month using retain logics, second month with override logics,... sixth month again with retain logics and etc. When/where we can choose them on right way? If we change it every month (for example) we may get different critical paths and also finish date can be unstable (can get back).
You could do that. It's a setting in the "schedule options" screen. These options are set and saved with each project. So you would have to manually change them on each update project.
Great video and explanation! One question: What is the difference between update schedule using the button F9 "Schedule" and the button "Update Progress"? Thank you!
Need to learn P6? Check out the best Advanced P6 Training Available online:
www.planacademy.com/
I think of the Actual Date option as middle ground between Progress Override and Retained Logic. It uses available actual dates rather than remaining date to perform the calculation. This will behave like retained logic for in-progress out-of-sequence tasks, but like progress override for completed out-of-sequence tasks. Stated another way, logic behind the DD is treated as if scheduling in Progress-Override and logic beyond the DD as if using Retained Logic.
I typically use this option only when I need to record progress beyond the datadate and still want to show tasks progressed beyond the datadate with the driving indicator for the associated pred or successor. It makes active logic traces a little easier without completed tasks showing as driving unless there is duration after the DD. However, I agree that it's best to use Retained Logic for any "official" schedule reporting.
Agree, Troy
Yes agree but when it’s recommended to use it??
Actual Dates runs as Retained Logic until there is an Actual Date applied after the Data Date then that one activity is treated as Progress Override. Using Actual Dates allows the illogical use of Actual Dates after the Data Date while not flagging an error in the Schedule Log.
Actual dates : as the name suggests considers actualized logic to show impact . This is helpful when you actualize and update logic prior to rolling DD. Ex : We update our schedules weekly and make sure we address every current week planned activities (current filters on),give new forecast and only then roll Data date. "Actual dates" help in such scenarios.
Thanks for this. Using a similar update process and wish I’d known this earlier.
Hi Michael, about the Actual Dates option it impacts the Late / Early dates. So some floats may change because of it
When I Update the actual costs the costs in the previous period changes. Why?. How do I make p6 to maintain the previously entered values when I entre the current values
Sir, do you have a video about the total budget cost minus the expense actual cost to give me the remaining cost. something like that.
Regardless whether retained logic or progress over ride, the actual should be before the data date. Activity H is done, so to my understanding activity H should be before the data date?
Hi Michael, thanks for useful videos. I have questions there. Is it correct way if we use all 3 options (depends which we need) during the progress updates? I mean, firts month using retain logics, second month with override logics,... sixth month again with retain logics and etc.
When/where we can choose them on right way? If we change it every month (for example) we may get different critical paths and also finish date can be unstable (can get back).
You could do that. It's a setting in the "schedule options" screen. These options are set and saved with each project. So you would have to manually change them on each update project.
😂😂😂Actual dates , I don’t know . I like your comment on that . Thanks a lot
When it’s recommended to use actual date ??
Great video and explanation!
One question: What is the difference between update schedule using the button F9 "Schedule" and the button "Update Progress"?
Thank you!
Exactly the same. It is simply a shortcut for us DOS shortcut users from back in the day.
Progress override is not a preferred scheduling option since it ignores the network logic
anybody on here ever take the course from these guys???
Hi sir May I course syllabus
Many thanks
Nothing understood, you are not goos teach r