Showing posts with label corrective action. Show all posts
Showing posts with label corrective action. Show all posts

Wednesday, July 14, 2010

Corrective and Preventive Actions In ISO 9001 Standard

Corrective and Preventive actions are used to adjust the manufacturing processes, quality system and product documentation to continuously improve product and service quality. This process never ends. Corrective and preventive actions are usually based on an engineering change request and engineering change order system. In general it is recommended that all feedback from internal and external sources be entered into the engineering change request system. This can include customer survey results, customer complaints, nonconforming material data, field failure data, work-in-process testing results, internal audit results, external audit results and suggestions from personnel. The inputs are then entered into the Engineering Change Request System. This system is used to queue workload for the engineering and quality problem solvers. The engineering manager or quality manager then reviews this bulk of requests for prioritization. The highest priority issues are assigned to personnel who create an engineering change order to correct the problem. Some engineering change requests will be denied and the denial will be justified in the ECR system before the item is closed. Other requests will generate an Engineering Change Order that includes an assignment to a project manager. The engineering change order will include complete details on how to correct the problem and when the change will take effect. This system is a closed loop system that will continuously improve quality. The status of the ECR and ECO systems should be used as input for the management review meetings.

The process of managing this data usually requires a database since priorities change on a daily basis and the amount of input can be very large, even at small companies. A database is also advised since the system can be used to generate automated reports that are used in the management reviews. Without constant supervision, engineering requests and change orders can pile up and start dragging down the company.

Corrective and preventive actions are listed separately in the standard to drive home the point that you can not have successful company that only corrects problems, you must prevent problems.

Corrective and preventive actions also go hand-in-hand with the requirement for continuous improvement. If the company is analyzing their mistakes, anticipating future mistakes and continuously improving, The quality of the product and services at the company will eventually be GREAT. The corrective and preventive actions system is the most critical element for an efficient quality system. Corrective and preventive actions are made using Engineering Change Requests (ECR) and Engineering Change Orders (ECO).

Any quality problem or suggestion should generate an ECR. This is the queue for engineering. If the engineering/quality manager decides that an action is required, then an ECO is created and assigned to someone with the resources to correct and prevent future problems.

ECOs should be generated by negative customer feedback, negative trend in product performance, observed areas for improvement, upgrades to documentation, or any other continuous improvement activities. Engineering change orders are the lifeblood of the organization and they must always be flowing to keep the organization strong and growing.

With this in mind, it is critical that the engineering change order system quick, simple and effective. I highly recommend the use of a database for managing ECRs and ECOs. This will give you a searchable history of changes to your products and is the best tool for continuous improvement.

Wednesday, December 16, 2009

Document Review In ISO 9000 Standards


Document Review In ISO 9000 Standards
The ISO 9000 Standard requires that documents be reviewed.
Previously the implication was that the review was a
check by potential users that the document was fit
for purpose before it was offered for approval. It
could be construed that for a document to receive
approval it must be checked and therefore ‘review
and approval’ in this context are one and the same
and the requirement is in this instance enhanced
rather than relaxed.
A review is another look at something. Therefore
document review is a task that is carried out at any
time following the issue of a document.
This requirement responds to the Continual Improvement principle.
Reviews may be necessary when:
- Taking remedial action (i.e. Correcting an error)
- Taking corrective action (i.e. Preventing an error recurring)
- Taking preventive action (i.e. Preventing the occurrence of an error)
- Taking maintenance action (i.e. Keeping information current)
- Validating a document for use (i.e. When selecting documents for use in
connection with a project, product, contract or other application)
- Taking improvement action (i.e. Making beneficial change to the
information)
Reviews may be random or periodic. Random reviews are reactive and arise
from an error or a change that is either planned or unplanned. Periodic reviews
are proactive and could be scheduled once each year to review the policies,
processes, products, procedures, specification etc. for continued suitability. In
this way obsolete documents are culled from the system. However, if the
system is being properly maintained there should be no outdated information
available in the user domain. Whenever a new process or a modified process
in installed the redundant elements including documentation and equipment
should be disposed of.
The ISO 9000 Standard requires that documents be reviewed.
Previously the implication was that the review was a
check by potential users that the document was fit
for purpose before it was offered for approval. It
could be construed that for a document to receive
approval it must be checked and therefore ‘review
and approval’ in this context are one and the same
and the requirement is in this instance enhanced
rather than relaxed.
A review is another look at something. Therefore
document review is a task that is carried out at any
time following the issue of a document.
This requirement responds to the Continual Improvement principle.
Reviews may be necessary when:
- Taking remedial action (i.e. Correcting an error)
- Taking corrective action (i.e. Preventing an error recurring)
- Taking preventive action (i.e. Preventing the occurrence of an error)
- Taking maintenance action (i.e. Keeping information current)
- Validating a document for use (i.e. When selecting documents for use in
connection with a project, product, contract or other application)
- Taking improvement action (i.e. Making beneficial change to the
information)
Reviews may be random or periodic. Random reviews are reactive and arise
from an error or a change that is either planned or unplanned. Periodic reviews
are proactive and could be scheduled once each year to review the policies,
processes, products, procedures, specification etc. for continued suitability. In
this way obsolete documents are culled from the system. However, if the
system is being properly maintained there should be no outdated information
available in the user domain. Whenever a new process or a modified process
in installed the redundant elements including documentation and equipment
should be disposed of.