Scheduling Types
The Scheduling Type defines how the task behaves in relation to other tasks for the same asset.
| Type | Description |
|---|---|
| Simple | Generates Work Orders at fixed intervals (based on calendar days or meter readings). Each task runs independently, regardless of other tasks. |
| Suppression | Allows multiple related tasks to exist within the same scheduling group. When several tasks fall due around the same time, only the highest-priority task is generated, and lower-priority ones are automatically suppressed. |
| Cycle | Links tasks in a specific sequence so that one must be completed before the next is generated (for example, Task A → Task B → Task C). This is used for progressive or conditional workflows. |
How Suppression Works
Suppression helps keep your maintenance program tidy and efficient by avoiding duplicate or overlapping work.
When suppression is in use:
- All related tasks are placed in the same Scheduling Group such as Group A.
- Each task in the group is given a Scheduling Priority where 1 is the highest priority.
- Tasks continue to follow their usual frequency such as every 10,000 hours.
- If two or more tasks fall inside the same Scheduling Window such as within two days or similar usage, only the task with the highest priority will create a work order.
- Lower priority tasks are automatically suppressed for that cycle.
Example
Below is a simple service structure:
| Task | Frequency | Scheduling Priority | Description |
|---|---|---|---|
| Engine | Every 12,000 hours | 2 | Main component replacement |
| Turbocharger | Every 6,000 hours | 1 | Child component replacement |
In this case:
- Both tasks sit within Scheduling Group A.
- The Turbocharger task has the highest priority with a value of 1 and is due every 6,000 hours.
- The Engine task is due every 12,000 hours.
- When both become due around the same time:
- The Engine task suppresses the Turbocharger task.
- Only the correct higher level work order is generated.
This ensures the parent component is serviced at the right time. Replacing the engine also replaces the turbocharger as it is supplied with the new engine.
Below is an expanded help article with two clear examples showing how cycle scheduling works using both hour based services and weekly services.
How Cycles Works
Cycle scheduling creates a repeatable sequence of tasks that run in a fixed order. Each time a task in the sequence is completed, Samurai automatically schedules the next task in the cycle. Once the final task is completed, the cycle returns to the start.
This approach is ideal when servicing follows a structured repeating pattern rather than a simple frequency.
Example 1
Hour Based Cycle
Tasks: 250 hour, 500 hour, 1000 hour, 2000 hour Interval between tasks: 250 hours
In this example, the servicing pattern repeats in a defined sequence. Instead of scheduling each task independently by its own frequency, the cycle ensures they trigger in the correct order.
The cycle runs as follows:
250 hour > 500 hour > 250 hour > 1000 hour > 250 hour > 500 hour > 250 hour > 2000 hour
Cycle returns to the start
With each work order completed, Samurai automatically advances to the next task in the sequence. This ensures the correct long term pattern of 250, 500, 1000 and 2000 hour services without overlap or duplication.
Example 2
Weekly Servicing Cycle
Tasks: 1 Week, 2 Week, 4 Week Interval between tasks: 1 week
Weekly servicing often follows a repeating rotation rather than simple multiples. Using a cycle allows you to define the exact order in which services occur.
1 Week > 2 Week > 1 Week > 4 Week
Cycle returns to the start
This pattern ensures the servicing program repeats in a predictable rhythm. Each time a service is completed, the next one in the cycle is scheduled automatically.
Using cycle scheduling keeps your maintenance program consistent, avoids duplication, and ensures services occur in the intended order based on actual asset usage or time.