Split Order Setup

The following article details the behind-the-scenes setup required to control split order functionality. Split Orders are created when a (parent) work order has an uncompleted task (such as returning the yard box back to the site) and completing that task requires a new work order to be created. Split orders act the same as the work order they are split from and can be used to schedule and record servicing details. Once a split order has been created, a parent/child relationship between the two records is formed. Because of this relationship, a split order can not be posted unless the parent work order is in a posted or billed status.

Setup: Work Type

Pathway: Setup > Operations > Work Type

Create a ‘Work Type’ for each line of business a split order may be created in. In the image example below, a ‘Return Yard Box Only’ Work Type was created.

 

Setup: Work Type Event Class

Pathway: Setup > Operations > Work Type Event Class

After adding Work Types, create a Work Type Event Class. It is important that when the Work Type Event Class is created, ‘Split Order’ is populated in the Event Type field.

Create a Split Order Event Type

  1. Select the Work Type from the upper grid to display the Work Type Event Class below.

  2. From Work Type Event Class, select the green '+' icon.

  3. Select ‘Split Order’ from the Event Type drop down.

  4. Select the previously created Work Type from the Work Type drop down.

  5. Enter a Note for internal referencing (optional).

Setup: Reason Code

Pathway: Setup > System > Reason Code

Review the Reason Codes created for Service Exceptions. If needed, add additional Reason Codes for the driver to select indicating the reason for a service exception.

When a driver marks a stop with an exception AND includes a Reason Code, the stop will display under the Exceptions column in Dispatch and the work order will update to match the ‘WO New Status’ for the selected Reason Code. Otherwise, if the drivers marks the stop with an exception and does not include a reason code the stop will display in Dispatch under the Do Not Service column as ‘Not Serviced’.

Â