e-Newsletter

 
July, 2004

Welcome to the Whittington & Associates e-Newsletter! Visit and bookmark our web site today: http://www.WhittingtonAssociates.com

This e-Newsletter is in HTML format and may not be displayed properly by some email programs. Please click on our web site address above to see the e-Newsletter with its proper formatting.
 
July Articles
Training in Atlanta

To avoid this newsletter being rejected, or placed in a junk folder, please add <Larry@WhittingtonAssociates.com> to your address book.

Click on a title to jump to the article:

1. Audit by Process Instead of By Clause 

2. Addicted to Data, But in Quality Denial

3. Complexity: Documenting the Right Level of Detail 

4. Numbers: Documenting Numerical Information

5. Science and Technology Information Retrieval

6. Class Schedule: July, 2004 - September, 2004


To see previous articles, go to Newsletter Archives.

Note: Students that have attended a class in Atlanta receive a 20% discount on future Atlanta classes.

ISO 9001:2000 Auditor Update
July 23, 2004

ISO 9001:2000 Lead Auditor
August 23-27, 2004

ISO 9001:2000 Internal Auditor
July 20-22, 2004; September 21-23, 2004

Understanding ISO 9001:2000 Requirements
September 13, 2004

Quality System Documentation
September 14-15, 2004

Implementing ISO 9001:2000
September 16-17, 2004

Green Belt Certification
July 19-21, 2004

Black Belt Certification 
Group 11 (3 weeks)
July 19-23 + August 16-20 + September 13-17

Training Classes in Other Cities

 

1. Audit by Process Instead of By Clause

Internal audits are often scheduled, and therefore conducted, according to the ISO 9001:2000 clause structure. These audits are more focused on judging conformity than evaluating effectiveness. Looking clause by clause, the quality management system may appear conforming, yet be fragmented and ineffective.

Auditors should adopt the process approach and assess the quality management system through its natural workflow. Of course, this requires understanding the business and its process linkages. Audit planning and interviews should identify for each process:
  • Inputs: What, when, and from whom?
  • Resources: With what people, materials, equipment?
  • Methods: How done (procedures and instructions)?
  • Controls: How monitored and controlled?
  • Measures: What are performance indicators?
  • Outputs: What is delivered, when, and to whom?
The traditional "process" audit has been a short, detailed evaluation of a single process within a department. The audit scope may not have included the process interactions outside the functional area. ISO 9001:2000 requires an audit of the entire system, either at one time or spread over multiple subset audits. This broader view must address the process linkages to evaluate the overall system. To be less disruptive, and maintain quality awareness, audits of individual processes may be scheduled each month until the full system is covered.   

Process audits can be conducted horizontally or vertically. A horizontal audit follows a process trail across multiple functional areas. It is good choice for assessing the process interfaces between departments. A vertical audit covers all the key processes within a functional area. This approach is good at examining the interfaces within a department, but may miss the interactions with other departments.

ISO 9001:2000 uses the Plan-Do-Check-Act methodology. As a result, one logical requirement may be addressed in multiple clauses. Auditing by clause defines an artificial audit scope. A process may span different departments and a department may have multiple processes. So, audits should be scheduled for vertical (process) or horizontal (department) coverage. If scheduled by department, ensure interfaces with internal suppliers (upstream) and internal customers (downstream) are included. Whether auditing horizontally or vertically, remember audits must still address all the applicable clauses (requirements) over the annual audit schedule.

Auditors should view the quality management system as a set of integrated processes (by understanding the interfaces and interactions). Adopt the process approach for your audits. Add value by looking at more than just conformity. Evaluate the linked processes for their “effectiveness”. Verify their controls and identify any process risks. Also, determine opportunities for improvement.

Auditors can promote the process approach through their own audit methods. If you are interested in more on this subject, see the Auditor Update course description. Our next class is in Atlanta on July 23, 2004. 

2. Addicted to Data, But in Quality Denial

ISO 9001:2000 requires the collection and analysis of a lot of data. Organizations rely on this information to make important decisions. However, a new survey by Forrester Research shows most enterprises have a big problem with information quality (IQ). Forrester principal analyst Lou Agosta finds that while many firms have improved their IQ, problems persist. They are "addicted to data", he writes, "but in quality denial".

Indeed, company-wide approaches to IQ seem to be the exception rather than the rule. Fully one-fifth of the firms responding to the survey had no consistent IQ strategy, and those that did, tended to have scattered approaches. Almost a third of the respondents dealt with IQ inconsistently, on a localized basis.

Consequently, even though companies are gathering huge quantities of data from business processes and transactions, much of it is obsolete, duplicated, or just plain wrong, subverting its usefulness as actionable information. Moreover, inconsistent and inaccurate information creates business uncertainty, leaving a company swimming in a tide of data, but unable to confidently act.

According to Agosta, it is not enough for companies to sift through data, looking for defects on a case-by-case basis; that's "firefighting, not information quality improvement". What firms need to do is to get serious with IQ improvement, and approach it strategically, as an information product quality control issue, in terms of a service-level agreement, or as a commitment to a system design for information quality.

Most importantly, companies have to be willing to take a close look at themselves and establish IQ processes before deploying technology to solve the problem. Enterprises have to create an information quality "safe harbor" that will allow employees to expose IQ problems without retribution, and then take steps to correct them. Agosta observes that a major reason why IQ issues remain unresolved is that employees fear that management will "shoot the messenger".

Companies need to implement a clear and consistent IQ policy and quantifiable processes across the enterprise and identify and empower an IQ evangelist to lead and coordinate the effort at the highest level. Agosta concludes that the problem, though substantial, can be solved through the application of IQ best practices.

The above portion of this article was based on an article by Matthew Friedman in Enterprise Applications Pipeline http://www.enterpriseappspipeline.com>.

The Guidance document on Terminology used in ISO 9001:2000 and ISO 9004:2000 defines "data" as facts, especially numerical facts, collected together for reference or information. In our July 2001 newsletter, we further defined data, information, knowledge, and wisdom.

Data: Factual material such as measurements and statistics, frequently quantifiable.
Information: Data endowed with meaning and purpose, which may differ according to individual interpretation.
Knowledge: Understanding of a science, art, or technique, which is gained from study, experience, or association.
Wisdom: Use of knowledge, with ability to discern inner qualities and relationships and make sound judgments and decisions.

So, what are some of the "dimensions" of data quality?

Accessible: Data is available and retrievable.
Complete: Data is not missing and of sufficient depth and breadth for our work.
Concise: Data is compactly represented.
Consistent: Data is presented in a consistent format.
Friendly: Data is easy to manipulate and apply to different tasks.
Correct: Data is accurate and reliable.
Defined: Data definitions are clear.
Interpretable: Data is in appropriate languages, symbols, and units.
Objective: Data is unbiased and impartial.
Relevant: Data is applicable and helpful
Secure: Data is protected and access is restricted.
Timely: Data is sufficiently up-to-date for our work.
Understandable: Data is easily comprehended.
Value-Added: Data is beneficial and provides advantages from its use.

Information quality is a hot topic. Perform an Internet search on "information quality" and find conferences, courses, papers, and practices on the subject.  


3. Complexity: Documenting the Right Level of Detail

In last month's newsletter, we covered Syntax and Vocabulary from our list of writing concepts. This month we pick up with Complexity and Numbers.

  • Syntax: the arrangement of words
  • Vocabulary: the choice of words
  • Complexity: the level of detail
  • Numbers: the presentation of numerical information
  • Format: the way a document looks
  • Style: conversational and emphasis methods
  • Organization: the grouping of process information
  • Conditions: the decision criteria
  • Lists: related items, possibly in sequence 
  • Alerts: For warnings, cautions, and notes
This article covers Complexity:

Documents should not contain too little or too much information. They must be written at the appropriate level of detail. The right level of detail depends on the type of document, process frequency, work force stability, and the knowledge, skills, and experience of the reader. Documents with inadequate detail may lead to process errors. However, too much information can bore the reader and result in mistakes from inattention.

All documents assume a certain level of user knowledge. Check on the user qualifications for performing the described process. Write for a typical reader, not a specific reader. Find out what your audience needs to know and how the information should be presented for their understanding and use.

Write to help the reader, not just to describe the subject. Don’t write in isolation. Get to know your “customer”.


Some information should be covered in training instead of in a procedure or instruction. Check with the trainers in your organization to verify the assumed knowledge levels and avoid unnecessary details.

Format the document so users can quickly find relevant information and skip details if they don’t need it. Consider a format with actions in one column and the corresponding guidance in the adjacent column.

4. Numbers: Documenting Numerical Information

The prior article in this newsletter dealt with documenting complex topics at the right level of detail. This article is about documenting numerical information. 

Numbers may be needed in a document to represent instrument readings, calculated values, or control settings. Quantities are most often accompanied by a unit of measure and should be expressed as numerals. In general, use numbers (0, 1, 2) instead of spelling them as words (zero, one, two). However, spell out the number if it has no unit of measure, e.g., “use one of the following”. Or, if it may cause confusion, e.g., “use one 9 volt battery” rather than “use 1 9 volt battery”.

If applicable, specify the unit of measure with the numbers. Use the same units of measure as indicated on the equipment, for example, degrees Fahrenheit. Specify numbers only to the precision (exactness) available on the equipment or data source. Use ranges to specify acceptable limits of operation. For example, 10 - 20 is a range.

Do not express it as an error band (15±5). Avoid asking users to make a calculation. If it is necessary, provide them with a calculation aid in the document to simplify the formula and reduce errors.


5. Science and Technology Information Retrieval

Science.gov has served as a gateway to reliable information about science and technology from across Federal government organizations since its launch in December 2002. Now, the interagency alliance has launched Science.gov 2.0, hailing it the “next major step in government science information retrieval.”

To see its content, go to <http://www.science.gov>.

The updated web site offers additional content, technological enhancements, and a newly-developed relevancy ranking technology that helps users get to the best documents quickly. Science.gov lets users search across 30 databases from 12 government science agencies across 1,700 web sites - that’s 47 million pages.

Use of the site remains FREE with no registration required. The “FirstGov for Science,” as it is called, serves the educational and library communities, as well as, business people, entrepreneurs, agency scientists, and anyone with an interest in science. The advantage of Science.gov is that it lets users search for information by subject, rather than by the agency sponsoring it. Secretary of Energy, Spencer Abraham said: “From the most current information on new technologies, to historical research results, to the most promising medical advancements, Science.gov connects citizens to the world of science.”

Hosted by the DOE’s Office of Scientific and Technical Information, Science.gov is made possible through a collaboration of the Departments of Agriculture, Commerce, Defense, Education, Energy, Health and Human Services, and Interior, as well as, the Environmental Protection Agency, the Government Printing Office, the National Aeronautics and Space Administration, and the National Science Foundation, with support from the National Archives and Records Administration.

This article is an edited version of an article by Paula J. Hane in Information Today <http://www.infotoday.com>.

6. Class Schedule for July, 2004 - September, 2004

To enroll in these public classes, go to Class Schedule at our web site, or call us at 800-404-7585. Classes taught by Larry Whittington are shown in yellow.

ISO 9001:2000 Lead Auditor (RAB Accredited) - BSI Management Systems
Initial course version developed by Larry Whittington 
July August September
12-16  Chicago, IL 02-06  St. Louis, MO 13-17  Detroit, MI
19-23  San Jose, CA 16-20  Reston, VA 13-17  Charlotte, NC
26-30  Pearl River, NY 23-27  Atlanta, GA 20-24  Kansas City, MO
  - -
23-27  Dallas, TX 27-01  Los Angeles, CA
  - -
30-03  San Diego, CA   - -

ISO 9001:2000 Internal Auditor (RAB Accredited) - BSI Management Systems
July August
September
07-09  Chicago, IL 25-27  San Diego, CA 21-23  Atlanta, GA
20-22  Atlanta, GA   - -
22-24  Charlotte, NC

 

ISO 9001:2000 Auditor Update - The Process Approach
Course developed by Larry Whittington
July September
23  Atlanta, GA 20  Atlanta, GA

Implementing ISO 9001:2000
Course developed by Larry Whittington
July August September
19-20  Reston, VA 11-12  Reston, VA 16-17  Atlanta, GA
  - -   - -
23-24  Los Angeles, CA

Understanding ISO 9001:2000
July September
02  Pearl River, NY 17  Kansas City, MO

Understanding ISO 9001:2000 Requirements (Atlanta Only - $295)
Course developed by Larry Whittington
September November
13  Atlanta, GA 29  Atlanta, GA

Quality System Documentation (ISO 9001:2000)
Course developed by Larry Whittington
July September
  - - 14-15  Atlanta, GA
  - -
30-01  Pittsburgh, PA

The above public courses can be offered on-site at your facility. In addition, we offer these on-site courses:

  • Understanding ISO/TS 16949:2002 Requirements (1 day) - Course developed by Larry Whittington
  • Internal Quality Auditing (2 Days) - Course developed by Larry Whittington (based on ISO 19011)

To arrange an economical on-site class, please call us at 800-404-7585.


© 2000-2004 Whittington & Associates, LLC. All rights reserved.
You may copy this e-Newsletter provided you copy it completely, do not change it, and include this copyright notice.

-top-

Site by Frogtown Media Web Design

Send this page to a friend