Showing posts with label iso 9001 standard. Show all posts
Showing posts with label iso 9001 standard. Show all posts
Tuesday, January 3, 2012
Sunday, January 30, 2011
ISO 9000 Document Management Software System
Today’s manufacturing companies that seek ISO 9001 compliance-(regardless of their motivation to do so) probably don’t find it that difficult to create intelligent documentation. After all, a few days with a good consultant or a quality manager can take care of document creation. The problem lies in the gap between what employees are doing and what employees are supposed to be doing (in terms of adhering to documentation) and the gap between the manner in which processes are being implemented and the manner in which they should be implemented ( in accordance with documentation). In other words, the problem lies in the way processes are strategized and applied and in the way employees commit to standards when compared against existing documentation. How can a company overcome these issues? The answers may be simpler than you think.
Automation is the Answer for ISO Control
If your underlying processes are poorly strategized then an automated document management software system won’t be of much use. However, once the processes have been effectively planned (and applied) a document management software system can speed process-to-process management by leaps and bounds. Companies that automate not only to comply with ISO standards but to generate more revenue by performing less administrative labor save weeks and even years worth of time just by automating their processes and documentation control with a document management software system.
Making Amends
The right document management software system and ISO document control would also allow companies to find deviations and nonconformance events faster and move those events to resolution phases in a small fraction of the time they were originally routed—if they were routed at all. Some ISO 9000 document management software systems may even be combined with a CAPA QMS solution. This is especially valuable when determining the root cause of major to minor deviations.
A Document Management Software System and Employee Training
ISO standards do not require any type of automation but ISO standards lend themselves to automation in a way that’s quite remarkable. Take for instance the following document management requirements from the official ISO 9001 International Standard.
ISO 9001 Section 4.2.3
ISO standards make it clear that ISO 9001 “approved” companies must define (i.e., document) how they will approve documentation, how they will identify documentation changes, how they will update/reapprove revised documentation, how external documentation will be managed and how assurance will be provided that documentation will be available when it is required. 1 And that’s only a shadow of things to come! A document management software system designed for strict compliance can automate the approval of documentation, the identification of document changes, updates and reapproval notifications, external documentation management and high-level document security. Some solutions also integrate training and online exams as well.
How Much Could You Save?
Chances are high that automation will save you thousands, tens of thousands or even hundreds of thousands of dollars annually depending on the size of your company. Just foregoing a typical document routing process (a manual process) can save many employees fruitless trips back and forth from one office to another. Who wouldn’t want to avoid those time consuming searches through 3-ring binders and lost documentation due to employee absence or neglect?
Conclusion
Regulation and control are the future for manufacturing. Gone are the days of free experimentation and a blind eye toward material waste. Today is the day of premeditated design, quality assurance and web-based automation. If your company plans to be, or already is, compliant with ISO 9001 standards why not consider automating those ISO 9001 controls with a document management software system.
Tuesday, August 31, 2010
Records Required by ISO 9001 Standard
Records Required by ISO 9001 Standard
ISO 9000 requires that records be kept of critical operations. Record keeping is the fourth tier of required documentation in ISO 9000, following the Quality Policy Manual, Procedures, and Work Instructions.
Questions you may have include:
•What is a record?
•What are the required records?
•What is the reason for these records?
This lesson will answer those questions. There is a mini-quiz near the end of the lesson.
What is a record?
Records consist of any historical documentation, such as summaries or meetings and reviews, specifications, invoices, results of tests and such. This is different than procedures and instructions that tell what do to. Instead, a record is the history of what has been done.
Records required
The following lists the records required under ISO 9001 version 2000, along with the referring sub-paragraph number from the standard. ISO 9002 and ISO 9003 would be subsets of this list. Of course, a company may choose to include additional records that they deem important.
Para.
Record Required
5.6.1
Management reviews
6.2.2 (e)
Education, training, skills and experience
7.1 (d)
Evidence that the realization processes and resulting product fulfill requirements
7.2.2
Results of the review of the requirements relating to the product and actions arising from the review
7.3.2
Design and development inputs
7.3.4
Results of design and development reviews and any necessary action
7.3.5
Results of design and development verification and any necessary action
7.3.6
Results of design and development validation and any necessary action
7.3.7
Results of the review of design and development changes and any necessary action
7.4.1
Results of supplier evaluations and actions arising from evaluations
7.5.2 (d)
As required by the organization to demonstrate the validation of processes where subsequent monitoring and measurement cannot verify the resulting output
7.5.3
Unique identification of the product, where traceability is a requirement
7.5.4
Customer property that is lost, damaged, or otherwise found to be unsuitable for use
7.6 (a)
Standards used for calibration or verification of measuring equipment where no international or national measurement standards exist
7.6
Validity of previous results when measuring equipment is found not to conform to its requirements
7.6
Results of calibration or verification of measuring equipment
8.2.2
Internal audit results
8.2.4
Evidence of product conformity with the acceptance criteria and indication of the authority responsible for the release of the product
8.3
Nature of the product nonconformities and any subsequent actions taken, including concessions obtained
8.5.2
Results of corrective actions
8.5.3
Results of preventive actions
Reason for records
The reason to keep records is for future use as a reference in case of questions related to contractual and legal matters, work techniques, verification of work done, and other parts essential to the company running smoothly. The company management should use sound judgment as to what records are non-essential and how long to keep a specific record.
ISO 9000 requires that records be kept of critical operations. Record keeping is the fourth tier of required documentation in ISO 9000, following the Quality Policy Manual, Procedures, and Work Instructions.
Questions you may have include:
•What is a record?
•What are the required records?
•What is the reason for these records?
This lesson will answer those questions. There is a mini-quiz near the end of the lesson.
What is a record?
Records consist of any historical documentation, such as summaries or meetings and reviews, specifications, invoices, results of tests and such. This is different than procedures and instructions that tell what do to. Instead, a record is the history of what has been done.
Records required
The following lists the records required under ISO 9001 version 2000, along with the referring sub-paragraph number from the standard. ISO 9002 and ISO 9003 would be subsets of this list. Of course, a company may choose to include additional records that they deem important.
Para.
Record Required
5.6.1
Management reviews
6.2.2 (e)
Education, training, skills and experience
7.1 (d)
Evidence that the realization processes and resulting product fulfill requirements
7.2.2
Results of the review of the requirements relating to the product and actions arising from the review
7.3.2
Design and development inputs
7.3.4
Results of design and development reviews and any necessary action
7.3.5
Results of design and development verification and any necessary action
7.3.6
Results of design and development validation and any necessary action
7.3.7
Results of the review of design and development changes and any necessary action
7.4.1
Results of supplier evaluations and actions arising from evaluations
7.5.2 (d)
As required by the organization to demonstrate the validation of processes where subsequent monitoring and measurement cannot verify the resulting output
7.5.3
Unique identification of the product, where traceability is a requirement
7.5.4
Customer property that is lost, damaged, or otherwise found to be unsuitable for use
7.6 (a)
Standards used for calibration or verification of measuring equipment where no international or national measurement standards exist
7.6
Validity of previous results when measuring equipment is found not to conform to its requirements
7.6
Results of calibration or verification of measuring equipment
8.2.2
Internal audit results
8.2.4
Evidence of product conformity with the acceptance criteria and indication of the authority responsible for the release of the product
8.3
Nature of the product nonconformities and any subsequent actions taken, including concessions obtained
8.5.2
Results of corrective actions
8.5.3
Results of preventive actions
Reason for records
The reason to keep records is for future use as a reference in case of questions related to contractual and legal matters, work techniques, verification of work done, and other parts essential to the company running smoothly. The company management should use sound judgment as to what records are non-essential and how long to keep a specific record.
Saturday, September 12, 2009
How long does it take to register to ISO 9000?
The time it takes to get ISO 9001 registered are varies. But it is talkingmonths here, not weeks. For one thing, you have to keep running yourbusiness. You cannot simply shut down while getting registered.The entire process can be broken down into the following generalphases:a. Implementing the ISO 9000 system.b. Operating it for the minimum time. (A minimum of three, andpreferably six, months before registration audit.)c. Selecting a registrar. This can be done during the registrationprocess, to save time.d. Interval between application and registration audit. This dependson the registrar’s backlog.
The time it takes to implement the ISO 9000 system depends in largepart on where you are when you start. If you already have any of thefollowing, implementation time should be relatively short:a. A documented quality system of any kind that is active, meaningful,but not necessarily compliant with any particular standard.b. Resources temporarily dedicated solely to implementing the system.c. The guidance of a good consultant
If you are starting from square one, implementation can take a longtime. (Unless you can shut down operations while implementing—butwho can do that?) Here are some other factors that can extend thetime it takes:a. Multiple locations.b. Head count.c. Whether or not you are design responsible.d. Corporate turmoil.e. Lack of ongoing, consistent, persistent top management commitment.This exhibits itself in a host of symptoms, including lack ofsufficient resources, other issues taking priority, vacillation, failureto pay attention, failure to learn and understand, and failureto lead.All that being said, experience has shown the following:a. On average, the shortest interval for the entire process—fromlaunch through registration audit—seems to be around 6 to 9months.b. At the other extreme, it’s been known to take 18 to 24 to 36months, even with significant resources and full managementcommitment.On average, for the typical organization (whatever that is), you arelooking at 10 to 18 months to get the job done.
The time it takes to implement the ISO 9000 system depends in largepart on where you are when you start. If you already have any of thefollowing, implementation time should be relatively short:a. A documented quality system of any kind that is active, meaningful,but not necessarily compliant with any particular standard.b. Resources temporarily dedicated solely to implementing the system.c. The guidance of a good consultant
If you are starting from square one, implementation can take a longtime. (Unless you can shut down operations while implementing—butwho can do that?) Here are some other factors that can extend thetime it takes:a. Multiple locations.b. Head count.c. Whether or not you are design responsible.d. Corporate turmoil.e. Lack of ongoing, consistent, persistent top management commitment.This exhibits itself in a host of symptoms, including lack ofsufficient resources, other issues taking priority, vacillation, failureto pay attention, failure to learn and understand, and failureto lead.All that being said, experience has shown the following:a. On average, the shortest interval for the entire process—fromlaunch through registration audit—seems to be around 6 to 9months.b. At the other extreme, it’s been known to take 18 to 24 to 36months, even with significant resources and full managementcommitment.On average, for the typical organization (whatever that is), you arelooking at 10 to 18 months to get the job done.
Subscribe to:
Posts (Atom)