In quality control processes, efficiency and accuracy are critical. Suggestive parameters are a practical tool that enable the preloading of essential quality data into inspections. This simplifies inspection processes and allows for easier comparisons between current and previous results.
What are Suggestive Parameters?
Suggestive parameters allow the transfer of specific quality data to inspections ahead of time. This can include results from earlier inspections or initial quality requirements. Their purpose is to streamline the inspection process, enhance accuracy, and facilitate faster decision-making. Keep in mind that suggestive parameters can only be set up for customers who create the inspections through an API connection.
Use Cases for Suggestive Parameters
Suggestive parameters can be applied in various quality inspection scenarios. Here are two common examples where they provide significant value:
1. Comparing Results Over Time
When inspecting a batch of goods during inbound delivery, you may need to re-inspect the same batch after a few days in storage. Using suggestive parameters, you can transfer the results from the first inspection into the subsequent inspection. This enables you to:
Compare the current state of the batch with the initial results.
Identify any quality changes or deviations efficiently.
Make decisions about the batch based on concrete data.
By preloading the historical data, you avoid manual data entry and ensure the information is readily available.
2. Validating Inspection Requirements
Suggestive parameters can also be used to ensure specific quality requirements are met. For example, if a particular EAN code is required during an inspection, you can:
Use suggestive parameters to preload the expected EAN code into the inspection process.
Use another parameter to confirm whether the observed code matches the expected value.
This simplifies the validation process and ensures that inspections are conducted consistently and accurately.
How does it work?
In order to preload the parameter values into the inspections, the parameterValues have to be added to the API post messages. In the segement ‘'ParameterValues'' you can define:
The parameter Id
The parameter value/enum item id (can be an enum value id or a numerical or string value)
Example Json
Example XML
After the suggestive parameters are set up in the API messages, the specific parameters also have to be added to the inspection template in the QC One portal. If the correct parameters are not set up in the inspection template, no data will be sent to the parameter fields in the QC One Inspector app.
