Job Dependencies are used for linking jobs - for example, when a series of jobs must be carried out in a specific order, like a project. Job Dependencies can also be used to plan jobs which are linked for other reasons, such as a parts pick-up stop prior to carrying out the main job.
Fig. 1: Series of dependent jobs which must happen in a specific order
The Job Dependencies feature helps you to schedule jobs in the correct sequence (by drag-and-drop or using Smart Scheduler), carry out partial billing as each phase is completed, and specify whether the same technician should be assigned to all jobs in the sequence.
Fig. 2: Dependencies are created by adding a predecessor and successor to a job
This documentation focuses on two main use cases: Project Planning and Parts Pick-Up.
Use Case 1: Project Planning
A project consists of a chain of jobs which must be completed in a specific order. The most common order is finish-to-start, i.e. each job must be completed before the next one can commence, as shown in this
Fig. 3 below. This example has four stages: Survey; Installation; Inspection; Test & Commission.
Fig 3. Example of multi-stage work
Use the Job Dependencies controls on the Job Page or Scheduled Quote page to link a series of jobs/quotes. You can create dependencies between jobs in two ways:
Add an existing job or quote to the current job by entering its Job or Quote ID
Use the Create New or Clone actions
Fig. 4: Job Dependencies controls in the Job and Quote page
Tips for Success
To quickly create a chain of dependencies, use the following workflow:
build out the first job in the chain
save the job
To create the successor, use the Clone action to create a copy of the first job
The clone will contain key attributes of the first job, such as customer, contact, custom fields, tasks, assets, etc. This saves time and ensures data integrity.
Create additional successors by cloning each new stage of the chain.
Viewing Dependencies in Job Page
The Job Dependencies table shows the predecessor and successor to the job being viewed. It is here that you can specify if all jobs require the same job lead.
Fig. 5: Project where Same Job Lead is not required
Monitoring Project Progress
To monitor the progress of the project, use the view all link in the Job Dependencies section to view the entire chain of in the familiar Jobs List view.
Fig. 6: “View all” link in Job and Quote page
This list view allows you to monitor the progress of the work, and even carry out part-billing as each phase is completed.
Fig. 7: Viewing project progress, with two jobs selected for Invoicing
Use Case 2: Parts Pick-Up
This section covers parts pick-up specifically, but the approach can be applied to any situation where the technician has to carry out an activity prior to the main job.
The diagram below shows a customer job, J201 which has been created in the system. However the parts required to carry out the work are not in stock and must be collected en route to the job. The planner creates a parts pick-up job, J203, at the inventory location and makes it a predecessor of J201.
Fig. 8: A customer job, J201, with a parts pick-up predecessor, J203
An essential feature of parts pick-up work is that the same technician must carry out both stages of the work. To ensure this happens, select the Same Job Lead Required checkbox.
Fig. 9: Parts pick-up job with “Same Job Lead Required” checkbox selected
Assigning Parts Pick-Up Jobs
The ordering of the stages is enforced by the Scheduler drag and drop rules. The Same Tech requirement is also enforced.
Fig. 10: Scheduler rules prompt you to drag the Parts Pick-Up before the customer repair job
Fig. 11: Because Same Tech Required has been set, the Scheduling rules rules prompt you choose the same assignee. This can be overridden.
The Same Tech Required setting is also enforced by the Smart Scheduler. If there is a potential problem fulfilling this requirement, a warning will be displayed in the Job Dependencies section.
Limitations
Jobs in a dependency chain can have only one predecessor and one successor.
Finish to Start relationship is the most common in project workflows and is the only one supported by the Scheduling rules.