Dependencies between tasks are one of the most important parts of every schedule. Calculating a programme can only be done once they are set up. Setting up predecessor or successor relations usually takes a lot of time and knowledge about on-site constraints. That's why Sablono tried to make the process as easy as possible. The platform offers three different ways of setting up dependencies: Task Dependencies between Activities within the same Deliverable, Task Dependencies between Activities from different Deliverables, and Dependencies between Deliverables.
Task Dependencies between Activities within the same Deliverable
Once you have created Groups and Activities in your Process Template, you can define dependencies between these activities. Follow these instructions to create these dependencies:
- Enter the Process Template where you would like to create these dependencies.
- Click on the Activity that you want to create dependencies for.
- In this screen you may define a, or even, multiple predecessors or successors for the selected Activity. For example, the insulation of the ceiling can only be installed if the substructure has been erected. To define dependencies simply click into the text fields "Depends on" or "Followed by" and chose from the activities existing in your template. Start typing to search for specific activities.
- Click on the remaining and just follow the same process.
Dependencies between Activities from different Deliverables
First, you can create detailed dependencies between Activities of different Deliverables on the Activities page. One example could be having to wait for all rooms of a floor to be painted before you start installing electrical fixtures. Having such dependencies will create gaps in your schedule. In the illustration below, assume the painting activities are the blue circles '1A', the installation of electrical fixtures is represented by the orange circles '2A' and the green arrows represent the task dependencies between different deliverables, predecessors in this example.
To set this up in Sablono, just follow these simple steps:
- Select the activities you want to define a predecessor/successor for.
2. Depending on if you want to create predecessors or successors for your selection of activities, please hit the according button on the left side of the toolbar.
3. Afterwards click on all those activities that you want to define as a predecessor or successor of your previously selected activities.
4. Please note, you can click on as many activities as you want. As a result, Sablono will create dependencies between your selection and every activity you now click on.
5. Finish the process by using the button on the left side of the toolbar.
6. To review your result, please open the deliverables Details View and navigate to the Dependencies Tab. Here, you will find a list of all dependencies related to the currently reviewed deliverable.
This manual workflow is not only easy to use, but also allows every flexibility that you might need to set up your personal process model in an unprecedented level of detail.
Dependencies between Deliverables
You are also able to create dependencies between deliverables. Sablono will automatically transform them into dependencies between the activities assigned to those deliverables following some simple rules (see below). To create dependencies between deliverables follow these steps:
- Open the Details View of the deliverable for which you want to define a predecessor or successor.
- Navigate to the Dependencies Tab.
- Add predecessors or successors using one of the buttons.
4. Finish the process and review the result.
To understand how Sablono transforms dependencies between Deliverables into dependencies between Activities, please have a look at the following rules:
- If you are connecting two deliverables using different processes, Sablono will always connect the last activity of the predecessors to the first Activity of the successors process.
- If you are connecting two Deliverables using the same process, Sablono will first identify trade-to-trade handovers in that process and connect the Deliverables based on these transfers. Let's look at an example: Whenever Team A finishes its consecutive work and Team B takes over, Sablono will connect the last activity that Team A needs to do on Deliverable 1 to the first activity Team A needs to do on Deliverable 2.
If you are working on a very long process with a lot of Teams involved - where every Team can only work on a single Deliverable at a time - it makes sense to simply create dependencies between Deliverables to save time.
Sablono is able to import schedules from other scheduling tools (Microsoft Project, Asta Powerproject, and Primavera P6). If you choose to do so, you most likely already set up dependencies in those tools. Sablono is able to import them as dependencies between Deliverables, and they will be transformed in the same manner as described above.
Review your dependencies
To review the result of your setup, please open the Details View of any Deliverable connected to your process model. There you will find a list of all predecessor and successor relations, showing in detail which Activity has to be done in order for another one to start. You can also delete those dependencies there or click on them to open the Details View of the connected Deliverable.