How to use dependency links, predecessors and lags with the Schedule app
This FAQ explains how to use dependency links between jobs in a project with the GroupCamp Schedule app. Predecessor types: Finish to start, Start to start, Finish to finish, and Start to finish. Using the dependency link Lag field.
A dependency link is used to add a constraint between two jobs.
Examples of constraints:
- Job 2 starts after the end of Job 1: Link Finish to start.
- Job 2 starts at least 2 days after the end of Job 1: Link Finish to start with a lag = 2 days.
- Job 2 starts at the same time as Job 1: Link Start to start.
- Job 2 starts at least 1 day after the start of Job 1: Link Start to start,with a lag = 1 day.
In GroupCamp, the Schedule app of the Scheduling module allows you to use the links between jobs and phases.
- An indicator appears when a constraint is not respected.
- The constraint resolution is manual. This allows you to take into account the actual resource load when a job needs to be moved to meet a constraint.
This video shows how to create a dependency link between two jobs. How to edit the dependency link, modify the value of the lag, see the Constraint not respected indicator and solve the constraint by moving the job.
Job 2 begins after the end of Job 1
The lag value is set to 0 when you edit the link. The constraint is not respected when the beginning of Job 2 occurs before the end of Job 1. You can move or modify the job as long as the constraint is respected.
If you want a lag > 0. Ex .: Job 2 starts at least 2 days after the end of job 1.
Edit the link and enter the value 2 in the Lag field. The link will turn red and the indicator will come on when Job 2 starts less than 2 days before the end of Job 1.
Special case: negative lag
Job 2 begins BEFORE job 1 finishes when you create an Finish to start link.
In this case, the lag value (negative lag) is taken into account. If you back the job, the link goes red because the constraint is no longer respected.
Scheduling module apps display indicators (red arrows) when a constraint is not respected.
- The "empty" arrows indicate that at least one constraint is not respected in the underlying jobs (Dependency column).
- The "full" arrows are present in the Dependency column of the jobs for which the constraint is not respected.
- The job has a red arrowhead in the Workload plan app.