Creating a Service Task Dependency

Service Modules > Scheduling and Optimization > Service Board > Service Board Usage and Configuration > Service Board for Dispatchers and Crew Managers > Matching Resources to Jobs > Work Plans and Service Tasks > Service Task Dependencies > Creating a Service Task Dependency

You can create a service task dependency by selecting two service tasks from the same job and configuring the dependency type and time buffers.

Prerequisites
Ensure that Job Dependencies, Work Plan scheduling, and Service Task Scheduling are enabled for your Service Board tenant. The work order must not be in a Completed or Cancelled state.

Create a service task dependency when you need to establish a scheduling relationship between two service tasks within the same job. This dependency constrains when the secondary task can start or finish relative to the primary task.

To create a service task dependency:

1. On the Scheduler Job List or Scheduler Calendar, select two Service Task Cards from the same job.

2. Click Create Service Task Dependencies.

The Create Service Task Dependencies button appears only when exactly two service tasks from the same job are selected.

3. In the Create Service Task Dependencies dialog, the selected tasks appear in the first row as the Primary Service Task and Secondary Service Task.

Field

Description

Primary Service Product

Select a product. This selection controls which work plans and service tasks are available and ensures that you create the dependency using valid tasks for the selected product.

Primary Work Plan

Select the work plan that contains the primary service task. This choice filters the list of available primary service tasks and links the dependency to the correct planned sequence of work.

Primary Service Task

Select the service task that controls the dependency. This task determines when the secondary service task can start or finish based on the selected time dependency.

Secondary Service Product

Select a product. This selection filters the work plans and service tasks that the system allows you to constrain using the primary task.

Secondary Work Plan

Select the work plan that contains the secondary service task. This choice ensures that the dependency applies to the correct task within the job’s work structure.

Secondary Service Task

Select the service task that depends on the primary service task. This task follows the rules defined by the time dependency and buffer values.

To select a task without a work plan, clear the selection or leave the field blank in the service product column. The work plan column shows as None and the task column lists all orphan tasks.

Swap

Click this option to switch the primary and secondary service tasks. Use this option to quickly correct the task order without reselecting all fields.

Time Dependency

Define how the primary and secondary service tasks relate in time. Choose from the following option to control when one task can start or finish relative to the other.:

• Finish to Start: The primary service task must finish before the secondary service task can start. (Default)

• Start to Start: The primary service task must start before the secondary service task can start.

• Finish to Finish: The primary service task must finish before the secondary service task can finish.

• Start to Finish: The primary service task must start before the secondary service task can finish.

Minimum Time Buffer

Enter the minimum time gap required between the primary and secondary service tasks. The available options are days, hours, or minutes.

Maximum Time Buffer

Enter the maximum allowed time gap between the primary and secondary service tasks. The available options are days, hours, or minutes.

The image displays the Create Service Task Dependencies table

4. Review all dependency rows for accuracy.

To add another dependency row, click the Add Dependency button and repeat steps 4 through 8 for the additional row.

5. Click Save.

After saving, the Service Task Planning Calendar opens. The Service Board creates a dependency group for the job if one does not already exist. New dependencies are added to the existing group.