Any completed activity that is logically included in the current longest path is reported as being on the longest path. To not do so would leave a gap in the longest path. P3 identified this activity while tracing the controlling predecessor back from the last activity in the schedule. P3 stops tracing the controlling predecessors when it reached the last unfinished activity in this chain.
This technique does not allow for the identification of a longest path for completed activities with an internal scheduled start ‘before the data date’ otherwise. Good question!
Member for
22 years 10 monthsRE: As-Built Activities in Critical Path
Any completed activity that is logically included in the current longest path is reported as being on the longest path. To not do so would leave a gap in the longest path. P3 identified this activity while tracing the controlling predecessor back from the last activity in the schedule. P3 stops tracing the controlling predecessors when it reached the last unfinished activity in this chain.
This technique does not allow for the identification of a longest path for completed activities with an internal scheduled start ‘before the data date’ otherwise. Good question!