Taking into Account of Cross-Project (External) Links during Scheduling

Information

  • The interlinkage of projects via links results in the generation of a total network plan covering all projects involved. Any projects which have cross-area links to the project selected by the user will automatically be included in the calculation. Here, own project dates (PR Requested start /Requested end, PR Actual start/Actual end) and project priorities will be taken into account.

Calculation sequence of the projects

  • During replanning, the cross project links override the the calculation sequence. It may occur that a project with bad priority is calculated earlier due to the existence of a cross-project link.

Example

  • Cross-project links between different main projects
    • There is a cross-project link from task 03 in project 2511 to task 01 in project 2512.

  • Result of scheduling
    • TA 01 in Project 2512 cannot take place until after TA 03 in Project 2511 is finished. When the calculations are being performed for Project 2512, Project 2511 will automatically be calculated at the same time. Although the project priority for project 2511 is less urgent, tasks 01 to 03 will be loaded before task 01 from project 2512.

Information

  • The rank of a task which has a cross-project predecessor is determined as the maximum of its rank within its own project, and the rank of its cross-project predecessor.

Example

  • Project A has tasks A1, A2, A3, A4, and Project B has tasks B1, B2, B3; both projects have the same priority.

  • Task (B2) has rank 2 within its project, its cross-project predecessor (A3) has rank 3 within its respective project. As a result, task B2 is given the rank 4 within the Total Network Plan. The rank of its successor will be 5.
  • The loading sequence is: A1, B1, A2, A3, A4, B2, B3.

Example

  • If project B has a less urgent priority, then task B1 receives rank 3.

  • Loading sequence, taking into account the project priority: A1, A2, A3, B1, A4, B2, B3.