About Quality Control

With quality control, you can record the results of quality testing activities that are performed against item lots. The results of quality testing can be used to inform decisions as to whether certain lots are suitable for use in various processes.

The sections below describe the various features of quality control.

Data Collection Data Elements

If quality control information is to be recorded for a particular item, that item must be lot tracked. When quality control tests exist for an item, they are assigned as pending tests for every new lot record that is created. All historical quality control data is maintained on a lot by lot basis.

The Quality Control application area utilizes the data collection data element feature found in the Process Data Collection application area. Data collection data element codes can be assigned to items as quality tests. When a data collection data element is defined as a quality control test, it becomes a required value that you expect to record with every new item lot.

Quality Control Activities & Tests

Whenever a new lot for an item with defined quality tests is received into inventory, a pending quality control activity is created for that lot. A quality control activity consists of the quality control tests that have been assigned to the relevant item record. The user can record results for each item quality test. Once all test results have been entered, the activity must also be completed.

If an item lot needs to be re-tested, you can assign additional quality control activities to it.

Strict Quarantine Posting

You can require that an item lot must pass quality control testing before it can be used in sales and production transactions by activating the strict quarantine posting feature. Strict quarantine posting makes it impossible to post item lots on sales and consumption lines if they have not yet been released through a successfully completed quality control activity.

For more information about strict quarantine posting, click here.

Incident Registration

In NAV Food, it is possible to enter information about incidents and link them to source records. We are specifically not talking about complaint-management, because the functionality goes beyond entering complaints.
Incident registration can be set up by the customer in such a way that the customer decides against which sources (e.g. customers, vendors, items, bins, locations, resources, machines etc.) incidents can be entered and how they are dealt with.
Incident registration deals not only with entering data about the incident, but also with reporting on resolutions and providing a basis for extensive reporting with BI-tools.

For more information about incident registration, click here.

Skip Logic

Sometimes it is easier to set up a test-regimes for items received or produced in such a way that increasing proof on continued quality leads to less testing of items. In general quality management terms this is called Skip Logic.
Based on settings per Item for production and per Item/Vendor for production, it is possible to let the system calculate whether a planned QC-test can be skipped.

For more information about using skip logic, click here.

Average Measurement Calculation

When there are multiple registered quality control activities for a specific lot, it is possible to let the system calculate an average test result based on (some of) these tests.
The user can determine on the Data Collection Data Element level how an average should be calculated (always first result or always last result e.g. for Booleans or Options, Arithmetic for regulare average calculations or geometric calculations e.g. for PH-values).
the calculated averages are available on screen through a factbos and can be printed using a standard NAV Food report.

For more information about strict quarantine posting, click here.