Quality alerts
Introduction
With a quality alert help, record a problem with a product and ensure simple follow-up. In addition, a quality alert is designed to create an alert linked to a product, record problems and propose simple corrective and preventive actions. A quality alert applies in cases where a product presents a problem with simplified approach to the resolution.
Use - Workflow
Change the status of the quality alert with the action buttons. A status will be displayed in Kanban mode and in the quality report. The Kanban view can also be used to change the status by dragging and dropping an alert.
Case study - Quality alert
Introduction
Access : Quality → Quality Alert
In a quality alert, you will find the quality teams (see documentation on quality control).
Access : Quality → Configuration → Quality teams
- Create a quality team which will be in charge of alerts. You will also find problem root causes here, which will enable you to classify all the problems you have encountered.
Access : Quality → Configuration → Root causes
Create problem sources
Access : Quality → Configuration → Root causes
In this example, we need to create two root causes. One will relate to production, and the other to tagling problems.
-
Open a new origin file.
-
Give it a name.
-
Save the file.
The necessary parameters also include tags. Tags are used to qualify or classify all quality alerts. In this example, create four tags with associated colours (Access : Quality → Configuration → Tags).
-
Open a new tag.
-
Give it a name.
-
Assign a tag colour.
-
Save your changes.
Once these elements are ready, you can move on to the quality alert.
Quality Alert
Access : Quality → Quality Alerts → +New
Like quality checks, alerts can be represented in kanban view, sorted according to their status.
In this example, add a quality alert relating to a hard disk, which is tagged incorrectly.
-
Product: select a product reference, for example, a hard disk with a faulty tag.
-
Team: then select a team responsible for this alert.
-
Work center: enter the workstation where the problem was identified (the test bench).
-
Root cause: enter the cause of the problem. For example, the tagging problem.
-
Responsible: designate a responsible person to follow up this alert.
-
Priority: enter the priority. Select from Low, Standard, High, Urgent.
-
Dates: enter the start and end dates of the alert to position the quality alert in the alert calendar. The concept of a deadline allows you to prioritise the treatment using custom searches.
-
Tag: select a tag. If you have created four tags, you will find them in the drop-down list. For a quality alert, select the ‘Non-compliant’ tag.
-
Description: in this field, describe the fault that has been found. During a check on the test bench, it was detected that the product did not correspond in terms of memory capacity to what had been stated on the product tag.
-
Corrective actions: indicate the corrective action taken following an alert. For example, you can request a supplier return as a corrective action.
-
Preventive actions: indicate the preventive actions that should be taken in response to this alert. For example, propose a systematic check on receipt as a preventive action.
-
Modify tags: you can then modify or add tags. For example, add ‘Under surveillance’ to ‘Non-compliant’.