The next paragraph will briefly explain the two different scheduling modes available on Sablono. They can be found in the Project Settings.
Don't worry! Switching between manual and auto scheduling will never delete any dates even if the results may differ heavily between both modes. If you are not satisfied with the results of the other mode, you can switch back anytime.
This mode should be used if you are working in a project including defined start and/or due dates for all deliverables but without any dependencies between those deliverables. The "manual scheduling" mode works like this:
- If you defined start or due date for your deliverables, Sablono will automatically schedule the activities, after assigning a process template to deliverables. This calculation is done separately for all deliverables.
- If you defined start and due date for your deliverables, Sablono will use the user-defined start date to calculate the earliest start and end and the user-defined end date to calculate latest start and end. If only one of the two is defined, only earliest or latest dates will be calculated.
- If you did not set-up any user-defined dates, Sablono will not be able to schedule the activities of your deliverables.
- Sablono will also calculate the total float for all activities as the difference between earliest and latest start/end. If you only defined either start or due date, Sablono will only calculate the one corresponding date, but without a float.
- If the duration of the process assigned to your deliverables is longer than your defined start and due dates allow for, Sablono will present that conflict to you. To solve it, please delete either start or due date of the deliverables.
- Dependencies between deliverables or activities of different deliverables are not included into the calculated programme while using Sablono in the "manual scheduling" mode.
- If you want to create custom gaps within the process of your deliverable (e.g. Activity 3 can only be started on a specific date), please move that activity using the bulk “configure activities” feature on the Deliverables list or the Week Plan. Once you move Activity 3 all successors will follow according to the dependencies and durations defined in your Process Template.
- If you change information or settings related to the programme, those changes will trigger an automatic rescheduling of the affected parts of the programme.
The "auto scheduling" mode should best be used if you want your project programme to be automatically calculated based on dependencies between deliverables and activities of different deliverables. It works like this:
- This mode will calculate dates of your project programme automatically, as long as the connected string of deliverables/activities contains one user-defined date parameter.
- It uses the user-defined start or due date if a deliverable does not have a predecessor or successor, the duration of all activities (defined in your process templates) and the dependencies between your deliverables or activities of your deliverables to do so.
- Dependencies defined between deliverables will be converted to dependencies between activities of those deliverables by Sablono.
- Start and due dates for all deliverables which have a predecessor or successor will be defined by the connected activities assigned to them. The results of that calculation may differ heavily from your user-defined start and due dates (depending on how well the process assigned to your deliverables fits into your user-defined dates), especially if a deliverable has a lot of predecessors or successors.
- The total float is calculated in the same manner as described earlier, but in the “auto scheduling” mode the total float relates to the string of connected deliverables, instead of individual deliverable schedules.
- Gaps within the process of your deliverables can not only be created manually but can also be be defined by setting up a dependency to an activity of another deliverable (e.g. Activity 3 can only be started once Activity 5 of another deliverable was finished). This will not only help you to understand the root-cause of those delays but also make them transparent to anyone involved with the project.
- You may still move specific activities through the bulk-change-dates feature on the Deliverables page or on the Week Plan, but following successors will not move according to the defined process.
- Not all changes of information or settings related to the programme instantly result in an automatic rescheduling. Some smaller changes are collected, and the programme is only recalculated if the user decided to start the process.
Calculation and Presentation
Changes of the following information will trigger a rescheduling:
- Updating deliverables by re-importing the source file
- Changing start and/or due dates of deliverables
- Creating or deleting dependencies between deliverables and activities
- Changing the project calendar (see above)
- Assigning process templates to deliverables
- Changing and re-assigning process templates
- Changing start and/or due date of the project (see above)
The results of Sablono’s schedule calculation will be presented everywhere in the platform and also be used for further data aggregations and analytics (e.g. KPIs or Dashboards). The following dates will be presented to you:
- The Details View will show all available dates for your deliverables: User-defined start and end, earliest start and end, latest start and end, total float, forecasted delay
- Additionally, the list of activities will show these dates per activity: Earliest start, latest end, total float
- The list of your deliverables as well as the Bar Chart will show: Earliest start, latest end
- The Week Plan will show: Latest start and end
- All data aggregations and analytics (e.g. KPIs or Baseline comparison calculations) will work based on: Latest start and Latest end
- If one of those dates is not available (e.g. earliest start) the Sablono platform will present the corresponding one (e.g. latest start) if available