Calculation Settings
Featured Partner
Top Posters
Zine Eddine
2 posts
Alex Lyaschenko
27 posts
mxsiegel
0 posts
Mattvtek
0 posts
Gareth Evans
3 posts
PP Admin
3, 129 posts
Rajkamal Tangirala
5 posts
Rahul Kumar
1 posts
blake333_
0 posts
Jeamiell Ostrovsky
2 posts
Our Partners
Handling out-of-sequence
Retained Logic vs. Progress Override
Retained logic and Contiguous Durations are mutually exclusive per software settings, unless you make the exception for in-progress tasks.
It is your choice.
Best Regards,
Rafael
Thank you Rafael. This was well stated. I fully agree with your assessment of out-of-sequence logic and the argument of retained logic v progress override.
I am working with a client who would like to stipulate in their contract that specific calculation rules be used when submitting schedules. They are specifying retained logic, Durations contiguous (not interruptible) and Float calculated on Finish Dates.
I am having difficulty providing documentation on these calculation methods.
Any thoughts?
Regards,
Donna
Donna
Under P3/SureTrak if an activity has been worked on (had progress) before one of its predecessors, choose how to display this out-of-sequence progress. When you choose Retained Logic, P3/SureTrak does not schedule the remaining duration of a progressed activity until all of its predecessors are complete. When you choose Progress Override, P3 ignores network logic and allows the activity to progress without delay. Neither option solves the issue of out-of-sequence; there are arguments in favor and against each method.
Because you are looking for the option under MS Project I assume you know that.
I believe you can set this under Tools/ Options/ Schedule, split in progress check box.
Split in-progress tasks Allows rescheduling of remaining duration and work when a task slips or reports progress ahead of schedule. With this check box selected, if progress is reported on a successor task before the predecessor task is completed, the remaining work on the successor task can be shown as a split, using the same task dependency with the predecessor on remaining work. If this check box is cleared, remaining work is not split. The progress information is recorded on the originally scheduled dates, regardless of when the actuals took place. Likewise, remaining work is not rescheduled to maintain the task relationship. By default, this check box is selected.
A matter of semantics.
The major problem I had with MS Project with this regard is the lack of a report that identifies the existence of out-of-sequence and where. I tried to get a VB script to this purposes and never got it. For your knowledge there are some add-on packages that provide these reports but at extra cost.
These reports are usually a listing of your out-of-sequence activities (tasks in MS Project language) their predecessors and type of relationship. These reports are essential as out-of-sequence might invalidate your update unless you solve the issue through changed logic. Out-of-sequence at times drives crazy some reviewers who do not understand the issue. Out-of-logic is common, is not a sin, and per-se alone does not mean bad planning but a change in course.
Best regards,
Rafael
Does anyone know where I can find documentation on the calculation method used by microsoft?
Hi Donna,
Sorry, I think Retained Logic is mostly used with the Primavera toolset and maybe one or two others. There isnt a suitable equivalent in MS Project as it doesnt use remaining duration to calculate EF or LF dates, only start dates and durations (and float of course).
Can anybody else help?
Regards
Darren