Establishing Quality Objectives In ISO 9000 Standards

Establishing Quality Objectives In ISO 9000 Standards

The ISO 9000 Standard requires that top management ensure that quality objectives are established.

ISO 9001 defines quality objectives as results sought or aimed for related to quality. It also suggests that these

objectives be based on the quality policy and be specified at different levels in the organization, being

quantified at the operational level. As with quality policy the details will be addressed later and here we

will focus on what it means to establish qualityobjectives and how they relate to other objectives.

As the quality policy equates to the corporate policy, it follows that quality objectives equate to corporate objectives. All of the organization’s objectives should in some way serve to fulfil requirements of customers and other interested parties. It is also interesting to note that inISO 9001, the term requirement is defined as a need or expectation that is stated, customarily implied or obligatory. While an investor may not specify a requirement for growth in share value, it would certainly be an expectation. While an employee does not express requirements for salary increases when profits rise, it would certainly be an expectation and while society has no way other than to protest or invoke the law to impose its desires upon an organization, it certainly has the power to make organization’s comply and even change the law in extreme cases. So quality objectives do equate to corporate objectives.

Management needs to ensure that the objectives are established as a basis for action. All work serves an objective and it is the objective that stimulates action.

The reason for top management setting the objectives is to ensure that everyone channels their energies in a positive direction that serves the organizations purpose and mission.

For an objective to be established it has to be communicated, translated into action and become the focus of all achievement. Objectives are not wish lists. The starting point is the purpose and mission statement and the factors

identified as affecting the ability of the organization to accomplish its mission. It is in these areas the organization needs to excel and therefore they become the focus for action and consequently the setting of objectives. Although ISO 9001 suggests that the quality objectives should be based on the quality policy, it is more likely to be current performance, competition and opportunities arising from new technology that drive the objectives.

An objective is a result that is aimed for and is expressed as a result that is to be achieved. Objec-

tives are therefore not policies. The requirement should also not be interpreted as applicable only to

organizational functions and levels. Objectives are required at levels within the organization not levels

within the organization structure. This is clarified by the requirement for objectives to include those

needed to meet requirements for product. There are therefore five levels at which control and improve-

ment objectives need to be established:

Corporate level where the objectives are for the whole enterprise to enable it to fulfil its vision

Process level where the objectives are for specific processes to enable them to fulfil corporate goals

Product or service level where the objectives are for specific products/services or ranges of products/services to enable them to fulfil or create customer needs and expectations

Departmental or function level where the objectives are for an organizational component to enable it to fulfil corporate goals Personal level where the objectives are for the development of individual competency

A management system is not a static system but a dynamic one and if properly designed and implemented can drive the organization forward towards world class quality. All managerial activity is concerned either with maintaining performance or with making change. Change can retard or advance performance. That which advances performance is beneficial. In this regard, there are two classes of quality objectives, those serving the control of quality

(maintaining performance) and those serving the improvement of quality (making beneficial change).

maintain or to prevent from deteriorating. To maintain your performance and your position in the market you will have to continually seek improvement.

Remaining static at whatever level is not an option if your organization is to survive. Although you will be striving for improvement it is important to avoid slipping backwards with every step forwards. The effort needed to prevent

regression may indeed require innovative solutions. While to the people working on such problems, it may appear that the purpose is to change the status quo, the result of their effort will be to maintain their present position not raise it to higher levels of performance. Control and improvement can therefore be perceived as one and the same thing depending on the standards being aimed for and the difficulties in meeting them.

The statements of objectives may be embodied within business plans, product development plans, improvement plans, process descriptions and even procedures.

Achievable objectives do not necessarily arise from a single thought even when the policies provide a framework. There is a process for establishing objectives.

At the strategic level, the subjects that are the focus for setting objectives are the factors that affect the organization’s ability to accomplish its mission – the critical success factors such as marketing, innovation, human resources,

physical and financial resources, productivity and profit. There may be other factors such as the support of the community, of unions, of the media as certain businesses depend on continued support from society. Customer needs, regulations, competition and other external influences shape these objectives and cause them to change frequently. The measures arise from an analysis of current performance, the competition and there will emerge the need for either improvement or control. The steps in the objective setting process are as follows:

Identifying the need

Drafting preliminary objectives

Proving the need to the appropriate level of management in terms of:

whether the climate for change is favourable

the urgency of the improvement or controls

the size of the losses or potential losses

the priorities

Identifying or setting up the forum where the question of change or control is discussed Conducting a feasibility study to establish whether the objective can be achieved with the resources that can be applied Defining achievable objectives for control and improvement

Communicating the objectives

The standard does not require that objectives be achieved but it does require that their achievement be planned and resourced. It is therefore prudent to avoid publishing objectives for meeting an unproven need and which has not

been rigorously reviewed and assessed for their feasibility. It is wasteful to plan for meeting objectives that are unachievable and it diverts resources away from more legitimate uses.

Objectives are not established until they are understood and therefore communication of objectives must be part of this process. Communication is incomplete unless the receiver understands the message but a simple yes or no is not an adequate means of measuring understanding. Measuring employee understanding of appropriate quality objectives is a subjective process. Through the data analysis carried out to meet the requirements of clause 8.4 you will have produced metrics that indicate whether your quality objectives are being achieved. If they are being achieved you could either assume your employees understand the quality objectives or you could conclude that it doesn’t matter. Results alone are insufficient evidence. The results may have been achieved by pure chance and in six months time your performance may have declined significantly. The only way to test understanding is to check the decisions people make. This can be done with a questionnaire but is more effective if one checks decisions made in the work

place. Is their judgement in line with your objectives or do you have to repeatedly adjust their behaviour?

For each objective you should have a plan that defines the processes involved in its achievement. Assess these processes and determine where critical decisions are made and who is assigned to make them. Audit the

decisions and ascertain whether they were contrary to the objectives. A simple example is where you have an objective of decreasing dependence upon inspection. By examining corrective actions taken to prevent recurrence of

nonconformities you can detect whether a person decided to increase the level of inspection in order to catch the nonconformities or considered alternatives.

Any person found increasing the amount of inspection has clearly not understood the objective.

ISO 9000 Standards – Document Approval

ISO 9000 Standards – Document Approval
The ISO 9000 Standards requires that documents be approved for adequacy prior to issue.

Approval prior to issue means that designated authorities have agreed the document before being made available for use. Whilst the term ade-
quacy is a little vague it should be taken as meaning that the document is judged as fit for the intended purpose. In a paper based system, this means approval before the document is distributed. With an electronic system, it means that the documents should be approved before they are published or made available to the user community.

The ISO 9000 Standards document control process needs to define the process by which documents are approved. In some cases it may not be necessary for anyone other than the approval authority to examine the documents. In others it may be necessary to set up a panel of reviewers to solicit their comments before approval is given.
It all depends on whether the approval authority has all the information
needed to make the decision and is therefore ‘competent’. One might think that the CEO could approve any document in the organization but just because a person is the most senior executive does not mean he or she is competent to perform any role in the organization.

Users should be the prime participants in the approval process so that the
resultant documents reflect their needs and are fit for the intended purpose. If the objective is stated in the document, does it fulfil that objective? If it is stated that the document applies to certain equipment, area or activity, does it cover that equipment, area or activity to the depth expected of such a document? One of the difficulties in soliciting comments to documents is that you will gather comment on what you have written but not on what you have omitted. A useful method is to ensure that the procedures requiring the document specify the acceptance criteria so that the reviewers and approvers can check the document against an agreed standard.

To demonstrate documents have been deemed as adequate prior to issue,
you will need to show that the document has been processed through the
prescribed document approval process. Where there is a review panel, a simple method is to employ a standard comment sheet on which reviewers can indicate their comments or signify that they have no comment. During the drafting process you may undertake several revisions. You may feel it
necessary to retain these in case of dispute later, but you are not required to do so. You also need to show that the current issue has been reviewed so your comment sheets need to indicate document issue status.

Introduction to ISO 9001 Standard Certification

Introduction to ISO 9001 Standard Certification

Certification is a way to attest, by the intermediary of a third-party certifier, to a company’s ability to provide a service, product or system in accordance with client requirements and regulation requirements. ISO and IEC give the following definition:
Procedure by which a third party gives written assurancethat a product, process or service complies with the requirementsspecified in a benchmark.The ISO 9000 family of standards corresponds to all the management best practices benchmarks as regards quality, which are defined by ISO (the International Organisation for Standardization).
ISO 9000 standards were originally written in 1987, with revisions taking place in 1994 and 2000. Thus, the 2000 version of the ISO 9001 standard, which is part of the ISO 9000 family, is written “ISO 9001:2000?. The ISO 9001:2000 standard mainly focuses on the processes used to produce a service or product, whereas the ISO 9001:1994 standard was mainly focused on the product itself. Here is an overview of all the different standards in the ISO 9000 family:
ISO 9000: “Quality Management Systems – Basic Principles and Vocabulary”. The ISO 9000 standard describes the principles of a quality management system and defines the terminologyISO 9001: “Quality Management Systems – Requirements”. The ISO 9001 standard describes the requirements relative to a quality management system either for internal use or for contractual or certification purposes. Therefore, this standard is a group of requirements that companies must followISO 9004: “Quality Management Systems – Guidelines for Improving Performance”. This standard, which is intended for internal use and not for contractual purposes, focuses particularly on continually improving performanceISO 10011: “Guidelines for auditing quality management and/or environmental management systems”.

ISO 9000 Standards Training Video

ISO 9000 Standards Training DVD

ISO 9000 Standards Training Video

ISO 9000 Standards Training DVD

Quality characteristics in ISO 9000 Standards

Quality characteristics in ISO 9000 Standards

Any feature or characteristic of a product or service that is needed to satisfy customer needs or achieve fitness for use is a quality characteristic. When dealing with products the characteristics are almost always technical characteristics, whereas service quality characteristics have a human dimension. Some typical quality characteristics are given below.

Product characteristics

1. Accessibility Functionality Size

2. Availability Interchangeability Susceptibility

3. Appearance Maintainability Storability

4. Adaptability Odour – Strength

5. Cleanliness Operability -Taste

6. Consumption Portability – Testability

7. Durability Producibility Traceability

8. Disposability Reliability – Toxicity

9. Emittance Reparability Transportability

10. Flammability Safety – Vulnerability

11. Flexibility Security – Weight

Service quality characteristics

1. Accessibility Credibility – Honesty

2. Accuracy Dependability Promptness

3. Courtesy Efficiency - Responsiveness

4. Comfort Effectiveness Reliability

5. Competence Flexibility – Security

These are the characteristics that need to be specified and their achievement controlled, assured, improved, managed and demonstrated. These are the characteristics that form the subject matter of the product requirements referred to in ISO 9000. When the value of these characteristics is quantified or qualified they are termed product requirements. We used to use the term quality requirements but this caused a division in thinking that resulted in people regarding quality requirements as the domain of the quality personnel and technical requirements being the domain of the technical personnel. All requirements are quality requirements – they express needs or expectations that are intended to be fulfilled by a process output that possesses inherent characteristics. We can therefore drop the word quality. If a modifying word is needed in front of the word requirements it should be a word that signifies the subject of the requirements. Transportation system requirements would be requirements for a transportation system, Audio speaker design requirements would be requirements for the design of an audio speaker, component test requirements would be requirements for testing components, and management training requirements would be requirements for training managers. ISO 9000 requirements are often referred to as quality requirements as distinct from other types of requirements but this is misleading. ISO 9000 is no more a quality requirement than is ISO 1000 on SI units, ISO 2365 for Ammonium nitrate or ISO 246 for Rolling Bearings. The requirements of ISO 9000 are quality management system requirements – requirements for a quality management system.

ISO 9000 registered organizations

Managing Processes In ISO 9000 Standards

The ISO 9000 Standard requires the organization to manage the identified processes in accordance with the requirements of ISO 9001.

The first stage in managing a process is to establish what it is you are trying to achieve, what requirements you need to satisfy, what goals you are aiming at; then establish how you will measure your achievements. The next stage is to define the process you will employ to deliver the results. Managing the process then involves managing all the inherent characteristics of the process in such a manner that the requirements of customers and interested parties are fulfilled by the process outcomes. This means:

Managing the process inputs

Managing the work

Managing the physical resources

Managing the financial resources

Managing the human resources

Managing the constraints

Managing the outputs

Process management is therefore much more than managing activities and therefore when describing processes, one needs more than a flow chart of activities. The chart is a diagrammatical representation of a process but only one aspect. One can also add numerical data to the charts to indicate resources, cycle times, delays, costs etc. but the intangible factors of the human environment cannot be reduced to numerical data to add to the charts.

The notes to clause 4.1 of ISO 9001 need some explanation. It is stated that the processes needed for the management system include management activities, provision of resources, product realization and measurement. This note could cause confusion because it suggests that these are the processes that are needed for the management system. It would be unwise to use this as the model and far better to identify the processes from observing how the business operates. The term provision of resources should be Resource Management, which is the collection of processes covering financial, human and physical resources.

Product realization is also a collection of processes such as design, production, service delivery, etc. Measurement is not a single process but a sub-process within each process. Grouping all the measurement processes together serves no useful purpose except it matches the standard – a purpose of little value in managing the organization.

The second note refers to outsourcing processes although it is difficult to imagine that management activities, product realization or measurement would be outsourced in its entirety. It is likely that market research; design, product verification, equipment calibration and other specialized services may be outsourced. While outsourcing comes under purchasing, it is correct to point out that the organization should control any outsourced processes. The supplier of the process is usually referred to as a subcontractor because they provide services to the organization’s requirements not their own. Control of subcontractors is covered by clause 7.4 but in meeting clause 7.4.3, you need to treat suppliers and subcontractors differently.

ISO 9000 Standards – Retention Of Records

ISO 9000 Standards – Retention Of Records
It is important that records are not destroyed before their useful life is over.
There are several factors to consider when determining the retention time for records.
The duration of the contract – some records are only of value whilst the contract is in force.
The life of the product – access to the records will probably not be needed for some considerable time, possibly long after the contract has closed. On defence contracts the contractor has to keep records for up to 20 years and
for product liability purposes, in the worst-case situation (taking account of
appeals) you could be asked to produce records up to 17 years after you made the product.
The period between management system assessments – assessors may wish to see evidence that corrective actions from the last assessment were taken. If the period of assessment is three years and you dispose of the evidence after 2 years, you will have some difficulty in convincing the assessor that you corrected the deficiency.
You will also need to take account of the subcontractor records and ensure
adequate retention times are invoked in the contract.
Where the retention time is actually specified can present a problem. If you
specify it in a general procedure you are likely to want to prescribe a single
figure, say 5 years for all records. However, this may cause storage problems – it may be more appropriate therefore to specify the retention times in the procedures that describe the records. In this way you can be selective.
You will also need a means of determining when the retention time has
expired so that if necessary you can dispose of the records. The retention time doesn’t mean that you must dispose of them when the time expires – only that you must retain the records for at least that stated period. Not only will the records need to be dated but the files that contain the records need to be dated and if stored in an archive, the shelves or drawers also dated. It is for this reason that all documents should carry a date of origin and this requirement needs to be specified in the procedures that describe the records. If you can rely on the selection process a simple method is to store the records in bins or computer disks that carry the date of disposal.
While the ISO 9000 requirement applies only to records, you may also need to retain tools, jigs, fixtures, test software – in fact anything that is needed to repair or reproduce equipment in order to honour your long-term commitments.
Should the customer specify a retention period greater than what you
prescribe in your procedures, special provisions will need to be made and this is a potential area of risk. Customers may choose not to specify a particular time and require you to seek approval before destruction. Any contract that requires you to do something different creates a problem in conveying the requirements to those who are to implement them. The simple solution is to persuade your customer to accept your policy. You may not want to change your procedures for one contract. If you can’t change the contract, the only alternative is to issue special instructions. You may be better off storing the records in a special contract store away from the normal store or alternatively attach special labels to the files to alert the people looking after the archives.

Identifying and Recording Design Changes In ISO 9000 Standards

Identifying and Recording Design Changes In ISO 9000 Standards

The documentation for design changes in ISO 9000 Standards should comprise the change proposal, the results of the evaluation, the instructions for change and traceability in the changed documents to the source and nature of the change. You will therefore need:
- A Change Request form which contains the reason for change and the
results of the evaluation – this is used to initiate the change and obtain
approval before being implemented.
- A Change Notice that provides instructions defining what has to be changed this is issued following approval of the change as instructions to the owners of the various documents that are affected by the change.
- A Change Record that describes what has been changed – this usually forms part of the document that has been changed and can be either in the form of a box at the side of the sheet (as with drawings) or in the form of a table on a separate sheet (as with specifications).
Where the evaluation of the change requires further design work and possibly experimentation and testing, the results for such activities should be documented to form part of the change documentation.
At each design review a design baseline should be established which identifies the design documentation that has been approved. The baseline
should be recorded and change control procedures employed to deal with any changes. These change procedures should provide a means for formally
requesting or proposing changes to the design. For complex designs you may prefer to separate proposals from instructions and have one form for proposing design changes and another form for promulgating design changes after approval. You will need a central registry to collect all proposed changes and provide a means for screening those that are not suitable to go before the review board, (either because they duplicate proposals already made or because they may not satisfy certain acceptance criteria which you have prescribed). On receipt, the change proposals should be identified with a unique number that can be used on all related documentation that is subsequently produced. The change proposal needs to:
- Identify the product of which the design is to be changed
- State the nature of the proposed change identify the principal requirements, specifications, drawings or other design documents which are affected by the change
- State the reasons for the change either directly or by reference to failure
reports, nonconformity reports, customer requests or other sources
- Provide for the results of the evaluation, review and decision to be
recorded