ISO 9001 2008 Interpretation
ISO 9001 2008 Interpretation
ISO 9001 2008 Interpretation
This document is created to serve as a guidance tool for common understanding on the intent of the standard and providing clarification of the text. In order to claim conformity with ISO 9001: 2008, the organization has to be able to provide objective evidence of the effectiveness of its processes and its quality management system. Objective evidence as is defined as Data supporting the existence or verity of something and notes that Objective evidence may be obtained through observation, measurement, test or other means. Objective evidence does not necessarily depend on the existence of documented procedures, records or other documents, except where specifically mentioned in ISO 9001:2008. In some cases, it is up to the organization to determine what records are necessary in order to provide objective evidence.
If continual improvement has become a way of life for a company, it is unlikely that a demonstration of company wide continual improvement will come from only a few sources. System deterioration would not necessarily lead to non-conformity if all actions were positive and the improvement path is still evident and logical. The system would be questionable if the company did not recognize it or had not reacted to the issues appropriately. Note: It is the responsibility of the company to demonstrate improvement rather than the auditor to look for it. 4.1 a) Process identification It is expected to see a process model that explains the key processes of the business and how each relates and links to the others. The depth of process explanation may be as detailed as the company chooses, but should be based on its customer
1 OF 31
4.1 b) Sequence and interaction of these processes The interactions of the processes must somehow be described in the quality manual (4.2.2 c). The organization is not required to produce system maps, flow charts, lists of processes etc. as evidence to demonstrate that the processes and their sequence and interactions were identified. Such documents may be used by organizations should they deem them useful, but are not mandatory. Graphical representation such as flow-charting is perhaps the most easily understandable method for describing interactions between processes. Other possible methods may include: documentation prepared for implementation of the product management system; deployment flowcharts; and pictorial diagrams. 4.1 c) Criteria and methods needed to ensure that both the operation and control of these processes are effective. This could be demonstrated with stated objectives, instructions and or procedures as required for consistent output of the processes. 4.1 d) Ensure the availability of resources and information necessary to support the operation and monitoring of these processes. This may be through Management Review or other methods for defining and determining resources. 4.1 e) Monitor, measure and analyze these processes - All identified processes are subject to requirements for monitoring, measurement, and analysis for needed improvement. The methods employed and the timing of such analysis should be based upon priorities established by the organization. It is expected to set measurable objectives established for each process. These objectives should support the organizations overall objectives. 4.1 f) Implement actions necessary to achieve planned results and continual improvement of these processes Same as described above. It is expected to see corrective action taken when measurable objectives fall below target or defined action level. Outsourced Processes: Outsourced processes must be controlled by the organization and these controls must be defined/described within their system. Organizations are required to identify the controls they apply for any outsourced processes. This does not necessarily have to be documented in the quality manual or written documentation. Examples of some outsourced processes are: Process completed wholly or partially by a sister facility outside the scope of registration. Such as corporate performing design, purchasing or customer related processes. This may include the entire element or a subsection i.e. corporate
2 OF 31
Objective evidence must be ascertained to ensure that these processes are being controlled beyond the basic purchasing requirements, which are focused on controlling products not processes. The organization is responsible to ensure that the outsourced process is meeting applicable requirements to ISO9001:2008. Outsourced processes may be controlled through such methods as (not limited to): Internal Audits Internal Agreements between two sites where only the audited site is under the scope of registration (Interface Agreements) Process performance data Purchasing Process
ISO/TC 176/SC 2/N 630R2 ISO 9000 Introduction and Support Package: Guidance on 'Outsourced Processes: An outsourced process can be performed by a supplier that is totally independent from the organization, or which is part of the same parent organization (i.e. a separate department or division that is not subject to the same quality management system). It may be provided within the physical premises or work environment of the organization, at an independent site, or in some other manner The organization has to demonstrate that it exercises sufficient control to ensure that this process is performed according to the relevant requirements of ISO 9001:2008, and any other requirements of the organizations quality management system. The nature of this control will depend, among other things, on the importance of the outsourced process, the risk involved, and the competence of the supplier to meet the process requirements.
TABLE A: Cross-linked references 4.1 General requirements a) Identify the processes, including outsourcing, needed for the quality management system and their application throughout the organization (see 1.2), b) Determine the sequence and interaction of these processes,
Relevant further clauses 5.4.2 QMS planning 7.1 Planning of product realization 8.1 General
5.4.2 QMS planning 7.1 Planning of product realization 4.2.2 (c) c) Determine criteria and methods needed to 7.1 (c) ensure that both the operation and control 7.3.3 (c) of these processes are effective, 7.4.1 (Criteria for selection) 7.5.2 d) Ensure the availability of resources and Whole of 6 information necessary to support the operation and monitoring of these processes, e) Monitor, measure, and analyze these Whole of 8.2 processes, and, f) Implement actions necessary to achieve Whole of 5, 6, 7 and 8
3 OF 31
4 OF 31
The quality manual may have many forms. Although many organizations structure their documentation in a typical pyramid, it is not the only, and not always the most suitable, way. A quality manual doesn't have to exist as a separate document. The quality manual may: Be a direct collection of QMS documents including procedures; Be a grouping or a section of QMS documentation; Be more than one document or level; Be in one or more volumes; Be a stand alone document or otherwise; Be a collection of separate documents. The ISO 9001:2008 standard offers companies a possibility to establish effective, userfriendly systems. This edition offers the current users a unique opportunity to streamline their quality management system documentation. A separate document "addressing" all the clauses of the standard is not required by the standard - neither does the standard require the quality manual to "address" or "cover" the requirements of the standard. The manual may be documented specifically to the organizations processes. 4.2.2 a) Scope The organization may exclude portions of the standard that do not apply to their quality management system due to the nature of the product or service that they supply. ISO 9001:2008 clearly limits and identifies which activities may be excluded. The justification for exclusion and those considered not applicable must be clearly documented in the quality manual. If, for example, design does not apply to the quality management system, the standard stipulates (in section 1.2 Application) how a reduction in scope of the standard may be justified and documented within the quality manual. The exclusion applicability shall be within the clause Design and Development (7.3) only. All other potential exclusions within section 7 must be identified as not applicable or not applicable. The scope of the QMS should be based on the nature of the organization's products and their realization processes, the result of risk assessment, commercial considerations, and contractual, statutory and regulatory requirements. If an organization chooses to implement a quality management system with a limited scope, this should be clearly defined in the organization's Quality Manual and any other publicly available documents to avoid confusing or misleading customers and end users (this includes, for example, certification/registration documents and marketing material). Note: For multi-site/corporate certifications, it is expected to see that one quality manual is applicable for all sites and that any changes are centrally controlled (see 4.2.3)
5 OF 31
4.2.2 c) Interaction between processes This requirement ties closely to section 4.1 b), which is discussed in the previous paragraphs. The interactions between the quality management system processes do not have to be separately described, or illustrated, by charts, tables or maps. Although many organizations may choose such a form, it is not a mandatory method. Interaction between processes may be described, for instance, by way of references and/or cross-references within the procedures, where the procedures form part of the Quality Manual.
6 OF 31
7 OF 31
Where there is lack of documented evidence, an auditor may satisfy him/herself through interviewing the personnel at those levels and functions involved in achieving particular objectives to determine the level of planning. Another methodology allowing audit of effective planning involves review of the progress in implementation of such plans aimed at adhering to individual objectives.
Organizations will choose whichever form best suits their needs at any particular moment. Other actions to bridge competence gaps might include: Recruitment; Outsourcing; Acquisitions; Use of experts and/or consultants. Documented procedures or work instructions
All such means are acceptable as long as an organization has ensured the availability of the competencies needed.
13 OF 31
Any activity that allows individuals to understand how their efforts affect quality objectives may satisfy this requirement. All personnel need to know the specific measurable objective(s) for the process that they work in; they should also know what organizational objective their process effects. They should be able to demonstrate that they know what the actual measurable is, their progress towards that goal, what the plan is to achieve the goal. If they do not know the actual numbers, they should be able to communicate the topics of the measurable and know where the actual measurements are maintained or posted. 6.2.2 e) Maintain appropriate records - The requirement expands record keeping requirements to include education, skills and experience, in addition to training, where appropriate. There are a great variety of ways to record and provide evidence of training, education, skills and experience. Records may include: Diplomas; Certificates; Training log; Annotations in shift logs; Toolbox meeting notes;
14 OF 31
Such records may be filed in any location as long as the Records remain legible, readily identifiable and retrievable.
6.3: Infrastructure
It is the organizations management who determines the adequacy of the infrastructure provided by the organization. Auditors will seek objective evidence to demonstrate that the necessary infrastructure exists for the quality management system to be effectively implemented, for improvement of its effectiveness, and for fulfilment of customer requirements. Auditor would expect to see a process in place for maintenance of the building(s), equipment and any other supporting services. This is generally the responsibility of the maintence and IT departments.
7.2: Customer Related Processes 7.2.1: Determination of requirements related to the product
This clause promotes an up-front determination of all requirements related to the product. This includes requirements for servicing which are now included as post-delivery activities, which implies anything that is provided after the customer has received the product (i.e. repair and/or warranty work, installation, maintenance, etc.).
16 OF 31
17 OF 31
18 OF 31
7.5 Production and Service Provision 7.5.1: Control of product and service provision
20 OF 31
21 OF 31
22 OF 31
23 OF 31
ISO 9000:2008, 3.3.5 defines the Customer as the organization or person that receives a product. The examples stated are; consumer, client, end-user, retailer, beneficiary and purchaser. It is intended that the customer satisfaction measurements be focused on external customer but in addition can include internal customers. Internal customer satisfaction measures can be contained in the establishment of the organizations defined internal process measurable objectives. Measuring only internal customer satisfaction would not meet the intent of this clause and must include all interested parties where appropriate. Customer Satisfaction is determined by the organization measuring its customers perception as to whether they have satisfied their customers requirements and may be somewhat subjective or qualitative as much as quantitative. Customer complaints are a common indicator of low customer satisfaction but their absence does not necessarily imply high customer satisfaction. Simply capturing customer complaints and product returns will only gauge dis-satisfaction which does not fully meet the intent of the clause and will not satisfy these requirements. The organizations management should analyse the implications of the absence or existence of customer complaints. Process definition is needed. The various techniques, methodologies, tools, resources, etc. (forms, surveys, frequency, targeted customers, responsibilities, external survey service companies, benchmarking, etc.) and applicable procedures need to be determined for: 1) Obtaining customer satisfaction information (i.e. identifying, collecting, monitoring and reporting various data/information) 2) Using customer satisfaction information (analyzing, understanding and responding to i.e. making changes, corrections, enhancements and improvements to the products/services/quality system) The requirements 5.2 8.4 a) 8.5.1 5.6.2 b) 7.2.3 in 8.2.1 interrelate closely with those in sub-clauses:
Customer Focus (. with aim of enhancing customer satisfaction.) Analysis of Data customer satisfaction Continual Improvement (via analysis of data) Management Review Input customer feedback Customer Communication customer feedback & complaints
4.2.2 c) Quality Manual (include a description of interaction between processes) 5.6.2 a) Management Review Input (process performance)
26 OF 31
The organization should identify monitoring, and, where appropriate, measurement methods to evaluate process performance. The organization should incorporate these measurements into processes and use the measurements in process management. Measurements of process performance should cover the needs and expectations of interested parties in a balanced manner. Examples (from ISO 9004:2008) might include: Process capability Reaction time Cycle time or throughput Measurable aspects of dependability Yield The effectiveness and efficiency of the organizations people Utilization of technologies Waste reduction Cost allocation and reduction
There are only four possibilities auditors should see as dispositions of nonconforming product, 1- scrap, 2- rework or repair, 3- re-grading of the product, or 4 use with the concession of the customer and records maintained. Obviously reworked or repaired product requires subsequent verification prior to release.
Other potential or useful options might include: Need for Corrective Action Opportunity for Improvement Competition
Requirements of 8.4 interrelate with those in sub-clauses: 5.6.2 8.5.1 8.5.2 8.5.3 Management Review Input Continual Improvement Corrective Action Preventive Action
28 OF 31
Drivers, or impetus for continual improvement must come from the use of (as a minimum): The quality policy Quality objectives Audit results Analysis of data Corrective actions Preventive actions Management review
Requirements of 8.5.1 interrelate with those in clauses / sub-clauses: 5.6.2 g) Management Review Input (recommendations for improvement) 5.6.3 a - b) Management Review Output (improvement of system, processes and product) 8.4 Analysis of Data 8.5.2 Corrective Action 8.5.3 Preventive Action
Note: it is the responsibility of the company to demonstrate improvement rather than the auditor to look for it. Accordingly, it is useful audit practice to ask management to identify any improvement initiatives taken since the previous visit, and also any planned for the future.
8.5.2 b) Determining cause auditor will expect to see a process is in place for determining root cause. 8.5.2 c) Evaluating action needed to prevent recurrence auditor will expect to see evidence that action(s) are evaluated and developed to prevent the nonconformance from recurring. 8.5.2 d) Implementing action evidence that actions are implemented. There is no requirement for time however auditor will expect to see evidence that actions are taken in a timely manner. 8.5.2 e) Maintaining records - corrective actions are required to be maintained as quality records per 4.2.4. 8.5.2 f) Reviewing action taken auditor will expect to see a process in place for reviewing completed corrective action to ensure that the action taken was effective in correcting the nonconformity. Note: The organization may choose to maintain one document for both corrective and preventive action. While this is acceptable, external auditors believe that the processes are unique and should be documented separately. Note: Organizations are free to use their own terminology (i.e., many define corrective action as the fix and preventive action as the subsequent cure). There is no problem with this provided they are not claiming that this preventive action (i.e., after the event) meets the requirements of 8.5.3 (action taken before the event). Note: For multi-site/corporate certifications auditors will expect to see that evaluation of corrective actions across all sites is being performed and analyzed (usually from the headquarters location). This would be an input to management review (see 5.6.2).
8.5.3 b) Evaluating action needed to prevent occurrence auditor will expect to see evidence that action(s) are evaluated and develop to prevent the occurrence of potential nonconformances. 8.5.3 c) Implementing action evidence that actions are implemented. There is no requirement for time however auditor will expect to see evidence that actions are taken in a timely manner. 8.5.3 d) Maintaining records - preventive actions are required to be maintained as quality records per 4.2.4. 8.5.3 e) Reviewing action taken auditor will expect to see a process in place for reviewing completed preventive action to ensure that the action taken was effective. Preventive action is action taken to PREVENT the occurrence of potential problems. The organization might welcome some auditor guidance on terminology. Many companies (especially small companies with simple systems) are struggling to identify opportunities to satisfy 8.5.3, as most of the standard is, in fact, focused on prevention. Anything related to evaluation of risk and related actions, or action to prevent an early dip in a trend graph becoming a problem can be accepted as objective evidence of compliance as well as clear up-front preventive initiatives, of course.
31 OF 31