Internal & External Factors

Clause 4 of the new standard requires that an organization must determine what issues and requirements will impact planning and quality. To establish the context means to define the external and internal factors and must consider when and how they affect quality.

The internal context may include:

  • Your products and services
  • Organizational structure and accountability
  • Regulations and / or legal requirements
  • The policies and strategies used to achieve the organization’s goals
  • Assets – both human capital and traditional hard assets
  • Information systems
  • The relationships and communication methods used to disseminate the organization’s values to stakeholders, suppliers, and partners
  • Method and scope of the organization’s contractual obligations and relationships with the QMS

The external context may include:

  • Government regulations and changes in the law
  • Economic shifts in the organization’s market
  • The organization’s competition
  • Events that may affect corporate image
  • Changes in technology

Typically, all this information is in the heads of your organization’s Leadership Team, but it was never put on paper; the best way to gather it is by organizing some brainstorming. Understanding and integrating all this information can be very valuable and demonstrate where you stand as an organization.

So, what are the next steps?

  1. Determine the internal/external factors that are relevant to the company’s purpose, goals, and the QMS.
  2. Define the interested parties and their needs and expectations.
  3. Based on the relevant contextual issues and the needs of relevant parties, in conjunction with the company’s products and services, establish the scope of the QMS and document it. If something in ISO 9001 doesn’t apply to the business, document the justification to exclude it.
  4. Set up a process to monitor all the information pertaining to these factors as a regular agenda item in your Management Review process.

strategicplanningRemember, although you have until 2018 to changeover and become certified/recertified to the new standard, now is the time to start the transition in order to minimize disruption to the business as much as possible. And if you are considering pursuing ISO 13485 for medical or AS9100 for Aerospace, there is significant crossover and using someone highly experienced in all three will assure the changes to your QMS will translate seamlessly with all three.

Contact me for my free ISO 9001:2015 Readiness Checklist and perform a quick self-assessment to gage your preparedness for the new standard. Then call to see how I can help.

920-841-3478

Steve@TheRightApproachConsulting.com

 

Where to Start?

First, you need to determine which of the new requirements are already being satisfied in your existing quality system documentation (whether a formal certified QMS or homegrown), because some of the requirements scattered throughout ISO 9001:2008 are now consolidated into this new clause.

If you have already implemented ISO 9001:2008, then you probably have already defined the scope of the QMS in the Quality Manual and the sequence of processes and their interaction, either in the form of discussion, meeting minutes or flowcharting. If you are implementing the standard from scratch, then the first thing you need to do in this planning phase is identify the processes and their interactions (an example is illustrated in the adjacent figure).

QMSProcessModelInteractionOnce the scope of the QMS is defined (the Scope should concisely define your core business), together with exclusions (there will be more on what is an acceptable exclusion in Clause 7 of ISO 9001 in a later edition), and processes and their relations are identified, you need to get your hands around what factors impact your business from a high level.

These factors and how they are managed within your QMS comprise the context of the organization. The organization’s culture are internal factors, while the socio-economic environment are external factors. They all play a role in how the organization delivers products or services and the new standard requires you to state what these factors are and their effects on quality.

In next week’s final discussion of Context of the Organization (Pt. 3), I will present what types of issues should be included in both the internal and external factors.

Contact me for my free ISO 9001:2015 Readiness Checklist and perform a quick self-assessment to gage your preparedness for the new standard. Then call to see how I can help.

920-841-3478

Steve@TheRightApproachConsulting.com

 

Making the Simple Complex

With each iteration of ISO 9001, the powers that be seem bent on developing one requirement using verbiage that makes a simple concept complicated to understand. For the 2015 version of ISO 9001, Context of the Organization is it. They can certainly take a cue from my friend Tom Peters when, while explaining a new management concept in his typically simple terms, he told the CEO of a Fortune 500 Company “I just don’t know how to make this any more complicated for you!”

iso2015wordmapThe “Organization’s Context” is defined as “the combination of internal and external factors and conditions that can have an effect on an organization’s approach to its products, services, investments and interested Parties.”

Wow, see what I mean! This really applies to the development of your organization’s Quality Management System (QMS), and if you are already certified to ISO 9001:2008 you have most likely done this analysis informally during strategic planning using SWOT Analysis, Market Research, Competitive Landscape Benchmarking and other tools. The difference is that now this activity must be documented and reviewed regularly; with my suggestion being via your current Management Review process.

The “Interested Parties” are defined as those that effect your QMS. Conversely, management need not consider entities that do not have an effect on the QMS, although this should be a very short list, because as I preach to my clients, the “Q” can functionally be removed from QMS as it is actually a Management System for the entirety of the business.

Because the textbook definition of “Context” talks about how something can be influenced by its surrounding circumstances and facts, it does make sense to apply this to your QMS. Since the implementation of a QMS is a strategic decision, there are certain factors that influence how the organization operates in their business environment. These “factors” that make up the “context” are divided into two categories: Internal and External.

Next week in Part 2 I will show you “Where to Start” and discuss what types of influences should be included in both the Internal and External context analysis.

Contact me for my free ISO 9001:2015 Readiness Checklist and perform a quick self-assessment to gage your preparedness for the new standard. Then call to see how I can help.

920-841-3478

Steve@TheRightApproachConsulting.com

 

The new ISO 9001:2015 standard is now released and is quite a departure from the 2008 version. While the official drop-dead date to be fully compliant and certified is not until September 2018, this will come much faster than you think. Now is the time to begin the transition from your 2008 QMS to the 2015 version.

These changes can be overwhelming, but by following my common sense approach it can be broken down into very manageable steps. Risk based thinking, Context of the Organization, Leadership, Performance Evaluation & Demonstrated Improvement are just some of the critical changes to the standard.

ISO2015Checklist

I can help with anything from a comprehensive GAP Analysis and Implementation Plan that you can implement yourself to full support through the entire transition and qualification process.

Contact me for my free ISO 9001:2015 Readiness Checklist and perform a quick self-assessment to gage your preparedness for the new standard. Then call to see how I can help.

920-841-3478

Steve@TheRightApproachConsulting.com

The goal of root cause analysis (RCA) is to find out what really happened, why it happened, and how to prevent it from happening again. Chasing symptoms instead of digging deep to find root cause will almost certainly guarantee that the problem will repeat. Peeling back the onion, layer-by-layer, can be a long and tedious process, but it will be very difficult to attack the heavy-hitters by analyzing the symptoms and not the source.

Although RCA is initially a reactive mechanism, it can become a tool for developing prevention strategies if used properly. Whatever methodology of RCA is used, the system must:

  • Be interdisciplinary team-based
  • Include those most familiar with the situation
  • Dig deep at each level of cause & effect
  • Employ the 5 Whys
  • Be a process that identifies needed system changes
  • Be unbiased

While there may be the occasional Nero Wolfe in a company (or for my younger readers, a Gil Grissom), advanced RCA skills are generally a learned behavior. The first investment should be in advanced problem-solving training for (at a minimum) all management and quality personnel on the tools we have discussed here recently that are part of the Quality Toolbox. I like to make the analogy to one of my favorite television programs, Crime Scene Investigation (the Grissom reference).

CSIRCA

I think a quality professional is like a CSI, and the defect is the crime scene. As illustrated in the adjacent figure, during each episode the point is reiterated that the evidence will lead to the origin of the crime. The same is true with root cause analysis; where you find one you will always find the other if you dig deep enough.

 

One of the most frustrating parts of a customer’s life is dealing with a performance issue that hasn’t been properly addressed at a supplier. A company can have all of the most effective Quality Tools at their disposal, but if not used properly, they will see little benefit. Most companies have some form of a corrective action system in place to handle customer complaints, returned goods, defects, internal scrap, etc. And while any system can always be improved upon, the source of the frustration is usually not the system, but the methodology. “Treating the symptoms” is a condition that afflicts many companies, and a general education in true root cause analysis methodology is sorely needed.

RootCauseAnalysisOne of the most abused people in any company is the poor line operator. How many times has your company stated to a customer that the root cause for such-and-such a defect was “operator error”? More than you would be willing to admit I would venture. It is my belief that if a company did a true root cause analysis, it would discover that only about 5% of these claims would be actually attributable to true operator error, and that 95% would be directly attributable to a management issue. Without the proper training, tools and systems, the poor operator doesn’t stand a chance.

Next week we will look at some practical ways to avoid the symptoms and drive to true root cause.

Plan-Do-Check-Act Cycle (PDCA): This is more of a quality methodology that employs a four-step model, which seeks continuous improvement by combining constant evaluation of management policy and procedures with statistical analysis. The PDCA model was developed by Dr. Walter A. Shewhart and was later refined by the good doctor’s most famous student; W. Edwards Deming. PDCA can be used in a variety of situations, for example, when beginning improvement projects, developing a new or improved process, product or service, defining a repetitive work process, performing root cause analysis, or implementing any change.

The process-based quality management systems prescribed by ISO are also based on the Plan-Do-Check-Act model, and this methodology can apply to any industry in both manufacturing and service business sectors.

PDCA

  • Plan: Identifying a goal or purpose, formulating a theory, defining success metrics and putting a plan into action
  • Do: Action or implementation of the plan
  • Check: Outcomes are monitored to test the validity of the plan for signs of progress and success, or problems and areas for improvement
  • Act: Closes the cycle, integrating the learning generated by the entire process, which can be used to adjust the goal, change methods or even reformulate a new theory altogether

 

These four PDCA steps are repeated over and over as part of a never-ending cycle of continuous improvement.

 

Failure Mode Effects Analysis (FMEA): This is another of those “scary” quality tools that people often don’t utilize strictly because they don’t really understand them. A Failure Mode Effects Analysis is simply a step-by-step attempt to identify all possible failures in a product, design or process. If it is being used for a process it is called a pFMEA and for design use a dFMEA. This method uses a model to prioritize each potential failure based on their severity, expected frequency, and likelihood of detection. This tool should highlight any actionable weaknesses that will improve robustness and drive continuous improvement. Developed in the 1940s by the US military, Failure Mode Effects Analysis was further developed by the aerospace and automotive industries and has now gained widespread acceptance.

The 10 Steps to developing a FMEA are:

Step 1: Review the process—Use a process flowchart to identify each process component.

Step 2: Brainstorm potential failure modes—Review existing documentation and data for clues.

Step 3: List potential effects of failure—There may be more than one for each failure.

Step 4: Assign Severity rankings—Based on the severity of the consequences of failure.

Step 5: Assign Occurrence rankings—Based on how frequently the cause of the failure is likely to occur.

Step 6: Assign Detection rankings—Based on the chances the failure will be detected prior to the customer finding it.

Step 7: Calculate the RPN—Severity X Occurrence X Detection.

Step 8: Develop the action plan—Define who will do what by when.

Step 9: Take action—Implement the improvements identified by your PFMEA team.

Step 10: Calculate the resulting RPN—Re-evaluate each of the potential failures once improvements have been made and determine the impact of the improvements.pFMEA

Pareto Analysis: Around the turn of the 20th century, Italian economist Vilfredo Pareto made a couple of observations that led him to develop a principle that continues to be a powerful problem-solving tool today. He observed that around 20% of the Italian population owned approximately 80% of Italy’s wealth. He later observed that about 20% of the pea pods in his garden produced roughly 80% of his pea crop each year. This correlation led Pareto to postulate that, in most things, a small number of causes are responsible for a large percentage of the effect. In the late 1930’s, quality guru Dr. Joseph M. Juran recognized this principle as the Vital Few and Trivial Many Rule, which was later generalized into Pareto’s Principle or the 80/20 Rule.

Pareto analysis allows management by data instead of emotion; and as with most things, data-based decision-making will yield the highest return on investment. The first step is to categorize the problems by type or defect code. Next, generate a simple histogram, which ranks the defects in descending order of magnitude. Then, using the data set in the histogram, graphically portray the data set in a simple bar chart format. Finally, add a trend line showing the accumulated relationship of the defects to the whole, to visually identify what defects make up roughly 80% of the total dollars. The attached Figure illustrates what a Pareto Diagram might look like in a typical metal fabrication process. The strategy behind Pareto Analysis is to identify the areas with the highest improvement potential while minimizing the number of improvement initiatives. What this means in simple terms is getting the biggest bang (improvement) for the buck (effort).

ParetoAnalysis

Referring again to the Figure, the improvement team would easily determine that their efforts should be focused on eliminating the two defects labeled “Scratches” & “Paint”. Once improvement has been attained on these “80/20” areas, the reporting cycle is run again. The “new 80/20” problem areas are identified, and the team now focuses on eliminating these. The beauty of this system is that, with each iteration, the order of magnitude continuously declines so that the next 80% of the dollars represent a much lower amount of waste dollars, which is the essence of continuous improvement.

 

5 Whys: This technique can be used very effectively during cause & effect analysis to drive to true root cause. Anyone with small children has first-hand experience with this problem-solving tool, although in the business environment root cause should not end at “Because I said so!” Although the word “Why?” may be your three-year-old’s favorite word, it could also teach you a valuable problem-solving technique. By repeatedly asking the question “Why?” (five is a good rule of thumb), you can peel away the layers of symptoms which can lead to the true root cause of a problem.

The biggest mistake that most organizations make in problem solving is to try to fix a symptom instead of the root cause. Only addressing a symptom will result in the root cause manifesting in the form of another symptom, and the problem will continue. Although this technique is called the “5 Whys,” it may be necessary to ask the question fewer or more times than five to drive to root cause in some instances.
An example of using the 5 Whys is presented in the attached Figure. Now if we really wanted to solve this problem permanently, we could implement an oil level sensor Poka-yoke that would alert the operator and/or shut down the machine before a critical level was reached. Hopefully it is becoming clear how these tools can all work together to provide a solution!

FiveWhys