Short answer. Quality management software holds four things. Findings: non-conformities, customer complaints, supplier defects and audit findings, in a single circuit. Causes: each finding is tied to a family of cause, and the analysis is written down. Actions: an owner, a due date, and closure only after checking that the defect has not come back. Documents: the version in force, and proof that it was read at the station. In this page's example, of 120 findings opened in six months, only 37 are closed with effectiveness verified.
This page is for those who run a production or service company, or who are responsible for quality in one, whether the company is aiming for certification or not. The definitions come from public sources: quality management system, ISO 9000 family, nonconformity, corrective and preventive action, root-cause analysis, five whys, PDCA, quality audit, cost of poor quality, Pareto principle. The company, its findings and the defect followed are a constructed example. The page does not say how to obtain a certification and does not replace the text of a standard; it covers neither regulation nor tax, and quotes no hardware price.
What is inside quality management software
The figure stacks five layers; the third is where everything is decided.
The system. A quality management system is a collection of business processes focused on consistently meeting customer requirements. The ISO 9000 family is a set of international standards for such systems, and ISO 9001 deals with the requirements that organisations wishing to meet the standard must fulfil. The software is not the standard: it is the place where what you have decided to do leaves a trace. The nonconformity. It is a deviation from a specification, a standard, or an expectation. Findings. They come in through several doors, detailed below; the software gives them the same circuit.
Causes and actions have their own sections. Documents. A procedure has versions; only one is in force. The software distributes it, asks for reading to be confirmed, and withdraws the old one; the principle is that of the intranet and its read receipt, applied at the workstation. Steering. Indicators are read on a dashboard: findings per month, time to closure, defects that come back. Rights. Who can close an action, who can approve a document: see roles and rights.
Where findings get lost
The figure follows six months of findings, from opening to verification of effectiveness.
The funnel. In the example, 120 findings are opened. 96 have a cause analysed, 81 an action decided, 58 an action carried out, 37 effectiveness verified. The losses. 24 findings were never analysed; 15 were analysed without an action being decided; 23 actions decided were not carried out; 21 were carried out without anyone checking the result. What that says. The company detects well. It loses its findings afterwards: between the meeting and the shop floor, then between the action and its verification.
The cost. Costs of poor quality are costs that would disappear if systems, processes, and products were perfect: scrap, rework, returns, time spent sorting. An action that is not verified lets that cost run on while giving the impression that it is being dealt with. What the software does. Each finding has a step, an owner and a date; what goes past its date surfaces to the owner, then to their manager. The monthly meeting is no longer for remembering: it is for deciding. What is measured. Findings per step; age of open actions; share of actions closed with verification.
«The monthly meeting is no longer for remembering: it is for deciding.»
Five sources, a single circuit
The figure gives, for five sources of findings, what is recorded and who handles it.
In the workshop. The finding is entered at the station or on the phone: the product, the step, the quantity, a photo, kept as in photos that stand as proof. For production tracked at the station, it is tied to the manufacturing order, see production management. The customer complaint. It has two lives: the reply to the customer, covered in complaints and after-sales service, and the internal action, which belongs to quality. The supplier. Incoming inspection and the claim to the supplier are described in inspection at receipt.
The audit. A quality audit is the systematic examination of a quality system by an internal or external quality auditor. Its findings go into the same circuit as the others, with the same requirement of closure. Batches. When a defect affects a batch, traceability says how far it went, see food manufacturing software. Meeting up. Three complaints and five workshop findings on the same defect are a single problem: the software groups them by family, and it is the group that is analysed.
Correcting is not acting on the cause
The figure counts the same defect, month after month.
Three words. Correction is the action to eliminate a detected nonconformity. Corrective action is action taken to eliminate the causes of non-conformities. Preventive action is action taken to prevent their occurrence, generally as a result of a risk analysis. In the example. In the third month, parts are sorted and reworked: that is a correction, and the curve does not move, 57 defects in six months. In the sixth month, the cause is treated, a setting and a check at the station: 8 defects in the following four months.
Finding the cause. Root-cause analysis is a method of problem solving used for identifying the root causes of faults or problems. The five whys is one of its techniques: an iterative questioning used to explore the cause-and-effect relationships underlying a problem. The software does not find the cause; it requires it to be written down before an action is decided. Where to look first. The Pareto principle states that, for many outcomes, roughly 80% of consequences come from 20% of causes: ranking findings by family shows the two or three causes to treat first. The loop. PDCA is an iterative management method used for control and continual improvement: plan, do, check, act. The curve is the “check”.
«Correcting means removing the bad parts; acting on the cause means there are no more of them.»
A finding, in six steps
The figure follows a finding in six steps.
The finding. Described in one sentence, with a photo and a quantity, by the person who saw it. The correction. What is doubtful is isolated, sorted, reworked or scrapped: the customer is protected, the cause is still there. The analysis. That is the accented step. It looks for the cause, not the culprit: a finding that is turned against the person who reported it is the last one they will report.
The action. An owner, a due date, means; not “raise the teams' awareness”, but what actually changes at the station. Verification. On the date planned, the software asks the question: has the defect come back? It has the answer, since it counts the findings of the same family. Closing. Effective, or reopened with a new analysis. The period. You set the observation period per family of defects: a month for daily production, longer for a rare defect.
Seven weeks for one site
Seven weeks in the example, for one site.
- What you receive: entry of findings at the station and on the phone; a single circuit for non-conformities, complaints, supplier defects and audit findings; the written cause analysis; actions with owner, due date and verification; versioned documents with reading confirmed; the audit schedule; the indicators.
- What the company avoids: the defect that comes back under another number, the action decided and never done, the action done and never verified, the old procedure still on the wall, the audit prepared in a week.
- What is measured: findings per month, per source and per family of cause; time to analysis; age of open actions; share of actions closed with effectiveness verified; recurring defects; reading of documents.
- What Symloop does: scoping the families and the circuit, mobile entry, actions and their reminders, document management, audits, dashboards, the link with your production and your complaints.
Scoping. One week: your families of defects, your sources of findings, your owners, your documents in force. Taking over what exists. Paper forms or the spreadsheet give the families; actions still open go into the software, the old ones stay archived. Starting small. One workshop or one line first: entering a finding has to take less than a minute, otherwise it will not be done.
With or without certification. A certified company finds its records kept up to date between two audits; one that is not certified finds the same thing, without the certificate: defects that no longer come back. Ready-made or custom. Quality software exists and suits a standard organisation. Custom work is justified when findings have to be entered at the station in your production tool, and linked to batches, orders and suppliers, in Arabic and in French. The durations are those of a constructed example.
- What is quality management software?
- A tool that records findings, non-conformities, complaints, audit findings, follows their causes and their actions through to a verified closure, and keeps the documents in force. It replaces the forms and the spreadsheet.
- How do you manage quality in a company?
- By giving each finding an owner and a due date, writing down the cause before deciding the action, and closing the action only when the defect has not come back.
- How do you manage non-conformities?
- By entering them where they are seen, with a photo and a quantity, then following them in six steps: finding, correction, analysis, action, verification, closing.
- What is the difference between correction and corrective action?
- Correction eliminates the defect observed: parts are sorted and reworked. Corrective action eliminates its cause, so that it does not come back. Doing the first without the second means starting again every month.
- Why do the same defects keep coming back?
- Most often because the action treated the symptom, or was decided without being done, or done without being verified. Tracking by step shows which of the three.
- How do you follow corrective actions?
- Each action has an owner, a due date and a verification date. What goes past its date surfaces automatically, and the action is only closed if findings of the same family have stopped.
- Do you need ISO 9001 certification to use such software?
- No. The software is first of all there to make defects disappear. A certified company also keeps its records in it between two audits.
- How do you manage quality documents?
- One version in force per document, distributed to the stations concerned, with reading confirmed; old versions are withdrawn and archived.
- How do you prepare an internal audit?
- By scheduling it, with a checklist per process, and feeding its findings into the same circuit as the others. If tracking is kept up all year, the audit needs no separate preparation.
- Who enters the findings?
- The person who sees the defect, at the station or on the phone, in under a minute, with a photo. A finding that has to go through an office to be written down is often never written.