Inter-project dependencies in the scheduler allow you to create dependencies between tasks across different projects. This feature does not affect the schedules of linked projects, but displays a warning when tasks dependent on another project are in conflict.
Before creating inter-project dependencies, make sure that the projects for which links will be created are displayed in the scheduler. To create this type of inter-project dependency, you must have Scheduler Manager access to at least one of the two schedules. You can use a filter created from the Project List, Analytics, Report Center or Risk page.
⚠️This feature is only available to customers subscribing to the Enterprise plans of the Aidi platform.
Creating inter-project dependencies
Viewing inter-project dependencies
Conflict with inter-project dependencies
Modifying tasks with inter-project dependencies
Creating Inter-project Dependencies
Inter-project dependencies are created in the Dependencies section of the task details, in the same way dependencies are created between tasks within the same project.
Right-click on the task for which you wish to create a dependency and select Open Task Details.
- Click on the + sign for the type of dependency you wish to create: Tasks that have an impact on this task or Tasks impacted by this task.
- Follow the steps for creating dependencies as illustrated in the article Critical path, dependencies and constraints.
- In the Please choose an option step, you can select a task from the current project or click on the left arrow to select a task from another project.
You will then see all projects displayed in the scheduler.
- Select the appropriate project.
- Select the task for which the dependency is to be created.
- Click on Choose.
- A label indicates that this is a dependency external to the project.
- Click on Save.
Viewing Inter-project Dependencies
In the Gantt chart, inter-project dependencies are indicated by a label. You can click on the label to open the task Dependencies section and see which dependency is associated.
- If the task is dependent on another task, the External label is displayed in front of the task.
- If another task is dependent on this task, the External label is placed after the task.
- If there is only one project displayed in the scheduler, and that project has a dependency on another project, in the Dependencies section of the task associated with another project, you will still see that there is an external dependency.
- When opening the task details, on the Dependencies tab, you will see the name of the associated task followed by the project name.
- When you clicking a dependency and the project is not displayed in the scheduler, a message indicates that the selected task is in an unavailable scheduler (e.g. you don't have access to this project) and if you select another task in this same dependency, you won't be able to select this task again.
Conflict with Inter-project Dependencies
Aidi detects conflicts between inter-project dependencies. To avoid conflicts between tasks, the planned, revised or actual dates of the tasks must respect the delay written in the dependency, while taking into account the calendars of the tasks and schedules concerned, where applicable. In the example below, there must be at least 1 full calendar day between the relevant dates of the 2 dependent tasks, so that there is no conflict between the two tasks:
Basically, here's the conflict detection logic for the 4 types of dependency defined, where a delay of X days is defined between the two tasks. In all cases, the unavailability of the 2 tasks is taken into account in conflict detection.
- End-start relation : A conflict will be detected if task 1 of schedule B starts less than X days after the end of task 5 of schedule A.
- End-to-end relation: A conflict will be detected if task 1 of schedule B ends less than X days after the end of task 5 of schedule A
- Start-start relation: A conflict will be detected if task 1 of schedule B starts less than X days after the start of task 5 of schedule A.
- Start-End relation: A conflict will be detected if task 1 of schedule B ends less than X* days after the start of task 5 of schedule A.
When a dependency is created or modified between the tasks of 2 projects and the criteria are not met, a pop-up window displays the detected conflicts with the following information:
- The name of the current task
- The other project and the task with which there is a dependency link.
- The name of the project manager as defined in the project contacts, or of the person responsible for the task if no project manager is defined.
- Check the box to notify the project manager or task responsible of the detected conflict.
- Click OK.
✏️Note: If the user does not have access to the other project, the project title and task description will not be displayed. Only the person responsible, the project code and the task prefix will be displayed.
In addition, when a conflict is detected, the label indicating an external link is displayed in red and an exclamation mark is displayed to the left of the task as a warning.
When a date change resolves the conflict, the exclamation mark disappears and the labels turn yellow.
Modifying Tasks with Inter-project Dependencies
Changing the dates of a task with an inter-project dependency, either manually or by automatic scheduling may cause a conflict with tasks associated with other projects.
Auto schedule
As soon as you click on the Auto-schedule button, a pop-up window informs you that this action recalculates the dates of tasks with dependencies on external projects.
- Associated projects and tasks are described. You are informed that continuing automatic scheduling may lead to conflicts with the projects listed, and that in the event of conflicts, external projects will not be modified.
- You can continue or cancel the action.
If conflicts are indeed detected as a result of automatic scheduling, another pop-up window displays the information, and you can notify the project manager or the person responsible for each task.
Deleting an inter-project dependency from the project in which it was added removes it from both projects.
✏️Note: Please refer to the article Simulation for information on how inter-project dependencies behave in simulation mode.
Comments
0 comments
Please sign in to leave a comment.