Primary, of course, is quarantine or "sequester" of suspect material until the MRB has confirmed the nonconformance and issued a finding and course of action.
From my point of view:
- Nonconformance Report (NCR) is one person's [an inspector, customer, etc.] "suspicion" that a product or service is nonconforming.
- The next step in many organizations is referral to a Material Review Board (MRB) which confirms [or denies] the nonconformance and then sets a course of action (possible courses listed below.)
- If NCR is affirmed and requires action, one person or a team investigates and reports - the Corrective Action Report (CAR)
Bev D echoes my own thinking when she writes
"Not all Nonconformances (either product or process) require corrective action"
In the vast majority of cases, a nonconformance report documents
known nonconformities, not suspicions. The primary responsibility of an MRB is almost always disposition--"We know it's bad, now what do we do with it?". When a nonconformity has been identified, some kind of action will
always be necessary. The results of an investigation, if there is one, might be that CA isn't necessary or prudent.
The MRB usually has the following courses of action to follow:
- First, root cause investigation does not even begin until the suspect material (whether a physical product, a software program, or a service rendered) is declared nonconforming.
- Next, disposition of the suspect material is decided.
- Then, and only then, can the topic of root cause be taken up IF the material was nonconforming.
- Finger pointing is not part of a Deming process - effort is aimed at finding a solution, not assigning blame. (Short of outright sabotage, nonconforming material can usually be traced to the system - was the individual given proper tools, workspace, training, evaluation of competence? Was the design at fault? Was the machine inadequate to the task?)
- sometimes, the root cause is quickly discovered and a solution is very apparent and implemented - the CAR is the report of the investigation, the solution, and the start date of the implementation of action. Some organizations forget to followup with an evaluation (and followup report) that the implementation actually works to reduce or eliminate nonconformance.
- sometimes, the root cause is discovered, but for economic reasons, correcting the process is not a workable solution. In such cases, MRBs and executives may negotiate and compromise on waivers or permanent changes to requirements (such cases may fall under a concept of Acceptable Quality Level (AQL) or other compromise from 100% perfection)
Although MRB activity will always be at least slightly different from company to company, in most cases it's a matter of disposition and determining whether or not CA is needed. There are practically no customers these days that will accede to accepting any level of nonconforming material. Just the other day I had a customer ask for an RMA for one $2.00 part, and the source of the defect was untraceable. Customers these days think nothing of creating $500 worth of paperwork and misery for an obvious outlier.
Finally, I think you're (perhaps unwittingly) engaging in finger-pointing when you suggest that an MRB should always confirm the existence of a nonconforming condition. What does this say about the people who are charged with identifying nonconformities? Why would this level of distrust ever be allowed to persist?