In-Process Tracking Field Types

Create a library of in process tracking (IPT) fields to easily be assigned to operations throughout a job. IPT is commonly used for quality checks and data inputs per operation. You can use this to confirm your tolerance every 10 units, or have your team enter what tool they used on a specific operation.

IPT fields can be added to Operations within your system data as a default, or as a one-off to the routing step of an individual routing of an item.

Types of Checkpoints

PreOperation Checkpoints

Expected to be filled out before beginning the operation

In-Process Checkpoints

Allow you to set a number of units the team should be answering these questions for.

PostOperation Checkpoints

Expected to be filled out upon completion of the operation

<aside> ⚠️ Download your IPT data from the Jobs grid so you can be sure you are capturing the critical checkpoints for your manufacturing

</aside>

Setup

Quality checkpoints can be setup in your system data or can be added directly within the item routing.

System Data

Navigation:

**Business Setup** → System Data → Advanced → In-Process Tracking

1. Add field - Set the Name, Description, and Type of the In-Process Tracking Field

1. Navigate to the Operation that you would like this IPT to be included. Choose either Pre, In-process, or Post-Operation and add this IPT.

Item Routing

Navigation:

Items & Inventory → Items → Item Record → Production → Operation → Quality

Quality checkpoints can be added to the item within the operation under the Quality tab.

Select Field Type to choose from existing quality checkpoints or Create New.

Checkpoint Configuration

Value to Flag - How and when do you want the system to flag the operator if the checkpoint has not been complete?

Required - This will block the operation from being completed until the checkpoint has been completed

Restricted - Only users with specific permissions can complete these checkpoints. A Switch User icon will be available in the operation to quickly swap to another operators profile to complete the checkpoint if needed.

Applies only to First Articles - This will block the user from completing more than the frequency input (typically First 1 unit) until the checkpoint is cleared.

Label - Name of the checkpoint

Data Type - Type of checkpoint

• Number - Measurements
• Boolean - True/False
• Checkbox
• Dropdown - List of options
• Text

Description - Description of the checkpoint

Frequency - How often does this checkpoint need to be completed (e.g. Every 5 units)