Since a CPM Network is a “model” of reality, it’s likely that the actual activity sequence will differ from (i.e. out-of-sequence) the planned sequence. Therefore, identifying, assessing and adjusting in response to out-of-sequence events are necessary components to maintaining a functional and high-quality CPM schedule.
In general, the more out-of-sequence activities in the CPM network, the more likelihood that logic revisions are necessary. Zümmer’s Analysis Report # 24 – Out of Sequence in Progress Tasks Report not only lists the “In Progress” tasks that are out-of-sequence but also sorts the activities in order of # Days out-of-sequence.
Zümmer considers activities as “Out-of-Sequence” when a) the activity is a task; b) the task is in-progress and; c) the Early Start is not equal to the Data Date.
Note: P6 will not consider an activity as “out-of-sequence” when a Finish-to-Finish relationship is “pulling” the Early Start/Early Finish dates of an in-progress tasks away from the Data Date. Therefore, when reviewing the P6 schedule log, some tasks in the Zümmer Out-of-Sequence report will not be listed in the P6 schedule log.
Zümmer defines the # of Days out-of-sequence as the difference between the Early Start and the Data Date. In this case, Task D is out-of-sequence by 20 Days.
In the illustration, the schedule is calculated using Retained Logic and the Data Date is 20-May-16. Task D started out-of-sequence and the calculated Early Start is 09-Jun-16.
Other Zümmer Analysis Reports that relate to Out-Of-Sequence type conditions include:
Analysis Report #23 – Not Complete with Started Successor and:
Analysis Report #25 – Not Started with No Active Predecessors.
Copyright ©2019 FoxQuest Systems, Inc. – All Rights Reserved