Skip to main content
All CollectionsAdministration
Setting up Tolerance tables for QC
Setting up Tolerance tables for QC

Using a tolerance table is quite handy when the same data is used across several workflows or when the data is rapidly changed or updated.

Eli Gimelraikh avatar
Written by Eli Gimelraikh
Updated over 8 months ago

Use case: Part measurement

In this WF (workflow) example, the objective is to measure a certain part and to verify if it is in scope (or not), based on values taken from a tolerances table.

The WF process flow

  1. Operator selects a part from a list.

  2. Operator is requested measure part’s length, and to enter the measure value in a dedicated field.

  3. Next Plus automatically verifies whether the measurement is in scope (based on Min and Max values from the tolerances table.

  4. Next Plus directs the operator to the relevant step.

  5. Operator selects to end the WF or continue to the next part

Configuration Steps

Create a NPT Tolerances Table

Part Name

Minimum length

Maximum length

Part 1

40

50

Part 2

15

23

Part 3

6

13

Part 4

10

17

Part 5

3

8

Go to:

⚙ Modeling → Tables → Big Red Plus

  1. Give the table a name - “Tolerance table - Parts”.

  2. Create columns Give each column a name and type.

ℹ️ Required checkbox - unchecked.

  • Part Name - Type: Text

  • Minimum length - Type: Number

  • Maximum length - Type: Number

Click Save.

Create the Workflow

ℹ️ This is just an example, the WF should look like the diagram. keep reading…..

Steps configuration

  1. Part Selection: In this step the operator will select a part from a list.

    1. Enter descriptive text for the step.

    2. Add a Table Select Field. Name it: Part selection. Link the field to the “Tolerance table - Parts” table. Select the “Part Name” column for reference.

      ℹ️ This way we will let the operator to choose only from parts exist in the table. We will also use this input to retrieve the needed tolerance data from the table to populate the variables.

  2. Measure: In this step the operator will measure the part and enter the data. Link the step to the first step. The arrow should point from Part Selection —> Measure.

    1. Enter descriptive text, and add media that will assist the operator to perform the measurement correctly.

    2. Add a Text Input field. Name it: Measured length. Set type to Number.

      ℹ️ This will be the value for comparison with the Min and Max values from the table.

  3. Part in scope / Part is not in scope: These are two steps that Next Plus will automatically redirect the operator, based on the measurement result. Link steps to the Measure step. The arrows should point outward from the Measure step. Link steps to the Parts selection step. The arrow should point to the Parts selection step.

    1. Enter descriptive text in each step.

    2. Add a Radio button field to each step. Name it: More parts to measure? Set two options: Yes and No.

      ℹ️ This selection will help the operator to end the process or to continue to another round of measurement.

Create Variables

The variables will link the data from the Tolerance table - Parts to the WF.

Go to

⚙ Workflow Editor → Admin tab → Manage variables → Big red plus

Create a variable

  • Name: Min length

  • Type: Next Plus Table variable

  • Table: Tolerance table - Parts

  • Column: Minimum Length

  • Condition: Part name equals (part selection) part name

ℹ️ In other words, set the Min length variable to a value from the “Min Length” column, based on the part that was selected in Part name field in the Part selection step.

Repeat procedure to add “Max Length” variable.

Configure Flow-based Conditions using Variables

Pass arrow condition

Click on the arrow that connects Measure —> Part in scope steps.

In the name field, enter “Pass”.

Click on the Conditions wizard icon.

🎉 Here is where the real magic happens!

Now it’s time to configure the condition:

  • (Measure) Measured Length is Between (Workflow Variable) Min length to (Workflow Variable) Max length

ℹ️ Please note that the Between operator, also includes the border values.

This means that Next plus will check that the the data, that was entered in the Measured Length field in step Measure.

☑️ If the data is between these values - then the condition will be met.

Fail arrow condition

Click on the arrow that connects Measure —> Part is not in scope steps.

In the name field, enter “Fail”.

Click on the Conditions wizard icon.

  • (Measure) Measured Length is Not Between (Workflow Variable) Min length to (Workflow Variable) Max length

ℹ️ Please note that the Not Between operator, does not include the border values.

Did this answer your question?