# Traceability tag

The traceability tag allows to link additional information to a test and they are collected by the operator.

There are several levels where the traceability tag can be required (route, subgroup, inspection, piece/part and sample), three sources from which the information are acquired (barcode, keyboard and picklist), and the possibility to enable the traceability tag request when a test not completed is resumed.

The Traceability tag of subgroup level are not supported in this version.

If the system is upgraded, the subgroup level traceability tag becomes route level traceability tag.

The traceability tag of piece/part level is available only for By part inspections.

In the following, some examples of possible use of the traceability tag.

Example 1

The traceability tag is configured in 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. The barcode is required.

5. Scan of the barcode.

6. Complete the route.

If the route is repeated without exit the route page, the barcode is not required a second time.

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

Example 2

The traceability tag is configured in 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. Do the test.

5. After the first result of the inspection, select a tag from the picklist.

6. Complete the inspection.

7. Select another inspection.

8. Do the test.

9. After the first result of the inspection, select a tag from the picklist.

10. Complete the inspection.

Example 3

The traceability tag is configured in the following parameters:

- Level: part (piece).

- Source: barcode.

- Collection point: before.

Operations:

1. Start the route.

2. Select the enabled inspection.

3. Before the first result, the barcode is required.

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

5. The first test point of all the other inspections are done without tag request.

6. Before the second result of the first inspection is done, the barcode is required.

7. Scan the barcode.

8. The second test point of all the other inspections are done without tag request.

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

Example 4

The traceability tag is configured in the following parameters:

- Level: sample.

- Source: keyboard.

- Collection point: after.

Operations:

1. Start the route.

2. Select an inspection.

3. At the end of each result, the input from the keyboard is required.

## Applies to: