Traceback

Determining the Critical Path In any project, there are many factors at play that ultimately determine the critical path. These factors can be represented in schedule files as logical links such as finish to start relationships between activities or known relationships represented by logic lines. There can also be implied relationships between data such as the same resource being used between activities or activities that move by similar durations between schedule files. To interrogate and accurately determine a critical path would require being able to look at all the different activities and all the relationships to then determine the best predecessor. Logic+ achieves this by performing a traceback to determine the critical path. When a schedule file is loaded, all the activities are given a candidate score which is calculated based on the defined relationships in the schedule file as well as implied relationships of 15 key attributes. Then when an activity is selected and the traceback run, the highest rated candidate score will be used to determine the activities predecessor. The traceback then finds the best candidate score activity for the processor found and continues until the start of the schedule.