Worktickets

Overview

A number of Workticket and Routing Form models are supported for various industries.  Below we describe each Workticket and how the Items need to be setup to make it work.

Workticket grouped by Service 

In this model, a Workticket is generated for each distinct Service found in the Estimate items of a Transaction. The Code on Services is used to order the Services. Ideally, the code will be prefixed by numbers that make it easy to insert Items. For example, in an Engineering environment you might use the following model:

• 101-200 - Cutting Services eg. 101 - Cutting; 102 Laser Cutting, etc. 

• 201-300 - Bending, Drilling and Forming

• 301-400 - Welding

• 401-500 - Coating 

• 501-600 - Assembly

• 601-700 - Packaging

• 701-800 - Outwork

Data Pipelines

The Data pipelines used for this model are:

• Est_Services - This pipeline will typically be grouped on the Service Code - CODE

• Est_Service_Mat - Lists the materials in the same component including Qty and Size

• Est_Service_Ser - This is an ordered list of Services in the same component. The matching Service can be highlighted to provide an indication of where the items came from and where they are headed to.

Workticket grouped by Assemblies

This model allows you to group the Workticket by Assemblies in the Estimate. The Assembly name for the Root item is derived from the Transaction Item.

Data Pipelines

The Data pipeline used for this model are: Est_Components