Traceability Tags

Traceability tags are additional attributes that can be linked to routes in QA Supervisor. If a route is configured with traceability tags, during the test the operator must provide the tags to QA Inspector when requested to. According to how the route's traceability tags have been configured in QA Supervisor, there are different methods and moments in which the tags have to be provided.

Traceability tags can be requested at different Levels within the operation:

Level

Description

Route

Traceability tag requested either before or after the first measurement of the first inspection in the route, depending on the configured Collection Point.

Inspection

Traceability tag requested either before or after the first measurement in the inspection, depending on the configured Collection Point.

Part (piece)

Traceability tag requested either before or after the first measurement of each part/piece in the route, depending on the configured Collection Point.

This Level is available only for Forced by Piece Routes.

Sample

Traceability tag requested either before or after each measurement (sample) in the inspection, depending on the configured Collection Point.

Traceability tags can be requested in different Collection Points of the specified operation level:

Collection point

Description

Before

Traceability tag requested before starting a measurement according to the selected Level.

After

Traceability tag requested after finishing a measurement according to the selected Level.

Traceability tags can be provided to the system from different Sources:

Source

Description

Keyboard

The operator has to manually type a text string using the device keyboard when prompted.

Barcode

The operator has to scan a barcode when prompted.

Picklist

The operator has to select an item from a Picklist configured for the route when prompted.
If enabled in QA supervisor, the operator can also manually enter an additional item to the Picklist using the device keyboard.

If the traceability tag is configured as optional in QA supervisor, it is possible to skip the requests without providing the tag.

If the Traceability tag on resume option is enabled in QA supervisor, the traceability tag is requested when an incomplete test is resumed.

Below are some examples of tests with different traceability tag configurations:

Example 1

The traceability tag is configured with the following parameters:

  • Level: Route.

  • Source: Barcode.

  • Collection point: Before.

Operations:

  1. Configure a route with more than one inspection.

  2. Start the route.

  3. Select the inspection.

  4. Barcode scan is requested.

  5. Scan the barcode.

  6. Complete the route.

If the route is repeated without leaving the Route page, the barcode scan is not requested a second time.

The barcode scan is required only at the beginning of the first inspection of the route.

Example 2

The traceability tag is configured with the following parameters:

  • Level: Inspection.

  • Source: Picklist.

  • Collection point: After.

Operations:

  1. Configure a route with two inspections.

  2. Start the route.

  3. Select the inspection.

  4. Run the test.

  5. After the first result of the inspection, a picklist is displayed on the measuring device's interface: select a tag from the list.

  6. Complete the inspection.

  7. Select another inspection.

  8. Run the test.

  9. After the first result of the inspection, a picklist is displayed on the measuring device's interface: select a tag from the list.

  10. Complete the inspection.

Example 3

The traceability tag is configured with the following parameters:

  • Level: Part (piece).

  • Source: Barcode.

  • Collection point: Before.

Operations:

  1. Start the route.

  2. Select the inspection.

  3. Before collecting the first result, the barcode scan is requested.

  4. Scan the barcode, so that the first part (piece) is linked to the tag.

    The barcode scan is not required for the first test points of the other inspections in the route.

  5. Before collecting the second result of the first inspection, the barcode scan is required.

  6. Scan the barcode, so that the second part (piece) is linked to the tag.

    The barcode scan is not required for the second test points of the other inspections in the route.

This process is repeated for a number of times equal to the number of parts (piece to test).

Example 4

The traceability tag is configured with the following parameters:

  • Level: Sample.

  • Source: Keyboard.

  • Collection point: After.

Operations:

  1. Start the route.

  2. Select an inspection.

  3. After each result, the input from the keyboard is required.