...
| Excerpt | ||
|---|---|---|
| ||
Critical path tasks must have start/end dates. Tasks without dates can’t be visualized on the timeline and aren’t included in the critical path. When one tasks on a critical path doesn’t have start/end dates, the entire critical path is disrupted. Once the start/end dates are provided the critical path will be calculated normally and include all the connected tasks.  |
...
Critical path calculation
Use strong dependencies to determine the correct order of tasks.
The path is calculated from the end (the last task(s) in the project)
The algorithm works backward looking for strong links connecting tasks
The most direct path (without a time gap between tasks) is highlighted
A gap between tasks is allowed only if an ASAP link has a "lag time" added
...
...
The non-working days do not affect the critical path calculation. This means that if there are two tasks on the critical path (connected with a dependency) and the predecessor ends before a non-working day, the App will move the successor to start on the first working day and both will remain on the critical path.
Critical path Infobar tab
Tasks that are a part of the critical path are listed in the Infobar > Critical path tab.
...
Lag time and ASAP mode
...
Strong links (non-ASAP)
Strong links determine the necessary order of tasks , but don’t always result in a critical path.
...
A critical path does allow for gaps between tasks, but they have to be added as lag time. Lag time can be added to strong ASAP dependencies.
...
Non-working days
The non-working days do not ‘break’ the critical path calculation. This means that if there are two tasks on the critical path (connected with a dependency) and the predecessor ends before a non-working day, the App will move the successor to start on the first working day and both will remain on the critical path.
Critical path Infobar tab
Tasks that are a part of the critical path are listed in the Infobar > Critical path tab.
...