About Checkpoint Conditions

When you create a Checkpoint Condition that is linked to a Measurement Location whose ML Type field contains the value Numeric, the following text appears on the Checkpoint Condition node:

If <ML Category> is <Reading Value> then:

...where:

• <ML Category> is the value stored in the Category field in the Measurement Location. This value is populated automatically after you create the Checkpoint Condition and is used to identify the predecessor Measurement Location whose reading value may trigger the additional checkpoints to appear.
• <Reading Value> is the value that you select from the Select Value list in the workspace for the checkpoint condition.

The following image shows an example of what a character Checkpoint Condition record looks when it is selected in the left pane.

In this image, you can see that Filter Check is the ML Category and Leak is the reading value.

When you create a Checkpoint Condition that is linked to a Measurement Location whose ML Type field contains the value Character, the following text appears on the Checkpoint Condition node:

If <ML Category> <=><Reading Value> then:

... where:

• <ML Category> is the value stored in the Category field in the Measurement Location. This value is populated automatically after you create the Checkpoint Condition and is used to identify the predecessor Measurement Location whose reading value may trigger the additional checkpoints to appear.

• <=> is the quantifier (i.e., <, <=, =, >=, or >) selected in the Select Relation list in the workspace. This specifies the parameters of the condition when used in conjunction with the value in the <Reading Value> cell. The default value is = (equals).

• <Reading Value> is the value entered in the Select Value cell in the workspace.

In other words, you can specify that if the reading value is equal to the value in the Reading Value cell, the successor checkpoint should appear.

The following image shows an example of what a numeric Checkpoint Condition looks like when it is selected in the left pane.

In this image, you can see that:

• Pump Stroke Check is the ML Category.
• <= is the quantifier.
• 500 is the Reading Value.

When you create a Checkpoint Condition that is linked to a Lubrication Requirement, the following text appears on the Checkpoint Condition node:

If <LR Type> is <Reading Value> then:

...where:

• <LR Type> is the value stored in the LR Type field in the Lubrication Requirement. This value is populated automatically after you create the Checkpoint Condition and is used to identify the type of predecessor Lubrication Requirement whose character reading value may trigger the additional checkpoints to appear. There are three types of Lubrication Requirement:
  • Check Off
  • Change Out
  • Tracking
• <Reading Value> is the value that you select from the Select Value list in the workspace for the Checkpoint condition. There are two available character reading values for a Lubrication Requirement:
  • Done
  • Skip

The following image shows an example of what a lubrication Checkpoint Condition record looks when it is selected in the left pane.

In this image, you can see that Check Off is the LR Type.