Zero Defects

In other projects we have witnessed the significant impact that Zero Defects programs can have on a manufacturing organization. Zero Defects, also known as "Zero Quality Control" or "ZQC," is a quality improvement philosophy that seeks to eliminate defects in the production process. This philosophy has its roots in the Total Quality Management (TQM) movement and has been widely adopted by many manufacturing organizations.

The Zero Defects philosophy is based on the belief that quality should be built into every product, from start to finish. The goal is to eliminate defects and ensure that products are produced to the highest standard, meeting or exceeding customer expectations. This approach to quality focuses on the entire production process, from raw materials to finished goods, and encourages all employees to be actively involved in the quest for zero defects.

One of the key benefits of a Zero Defects program is that it helps to create a culture of continuous improvement. Employees are encouraged to identify areas where defects are occurring, and to work together to eliminate these issues. This creates a sense of ownership and engagement among employees, which in turn drives improved performance and results.

Another key benefit of Zero Defects is that it reduces the costs associated with rework and product defects. Defects in the production process can lead to increased costs, such as scrap, waste, and retooling. By reducing or eliminating these costs, organizations can improve their bottom line and remain competitive in their industry.

The key to success with Zero Defects is to have a well-defined process in place. This process should start with defining the standards for each product and then identifying the critical-to-quality characteristics that must be met. From there, a detailed process map should be created that outlines the steps involved in the production process, from raw materials to finished goods. This process map should also identify the potential sources of defects and highlight the steps that need to be taken to eliminate these defects.

Once the process map is in place, the next step is to implement the Zero Defects program. This involves training employees on the Zero Defects philosophy, as well as the process map and the critical-to-quality characteristics. It is also important to provide employees with the necessary tools and resources to identify and eliminate defects. This may include things like checklists, forms, and software programs.

In addition to training and tools, it is also important to have a robust feedback and continuous improvement process in place. This can include regular quality audits, customer feedback, and employee suggestion programs. The goal of these programs is to identify areas where defects are occurring, and to work together to eliminate these issues.

Finally, it is important to track progress and measure success. This can be done by tracking key performance indicators (KPIs), such as the number of defects, scrap rates, and customer satisfaction levels. By tracking these KPIs, organizations can determine whether their Zero Defects program is having a positive impact and make adjustments as needed.

In conclusion, Zero Defects is a powerful tool for organizations looking to improve the quality of their products and processes. By eliminating defects, organizations can improve customer satisfaction, reduce costs, and remain competitive in their industry. The key to success with Zero Defects is to have a well-defined process in place, and to actively involve employees in the quest for zero defects. By doing so, organizations can achieve operational excellence and realize their full potential.

8D

The so called “8D”-Report is a document resulting from an 8D process which is part of a structured problem solving process in quality management if there are quality issues between customer and supplier.

8D represents the eight mandatory process steps that are performed when processing a claim to get to the root of the cause. The report details the nature of the claim, responsibilities, and actions taken to prevent the problem from reoccurring:

The 8D methodology is intended to ensure that complaints are dealt with systematically. Consistent documentation of the associated troubleshooting steps and a high level of fact orientation ensure that errors in the product or system are thoroughly investigated and thus permanently corrected instead of just solving the problem.

Application

These eight steps are performed for the 8D report: 

1 Define a team to solve the problem

A team familiar with the process and/or the product is formed. They analyze the problem, take corrective actions, and monitor the effectiveness.

2 Describe the problem

In this step, the problem is defined as precisely as possible and the root cause of the problem is identified.

3 Containment action

These measures are intended to resolve the problem quickly and limit the damage until a permanent solution is found.

4 Root cause analysis

You probably haven’t found the real root cause during step 2 therefor various tests and experiments are used during step 4 to search for the real root cause of the error and the most likely causes are identified. This is intended to ensure that similar errors do not occur again.

5 Planning of counter measures

It then determines the means by which the causes of the problem can be eliminated. It is tested whether these measures solve the problem efficiently and no undesired side effects occur.

6 Check effectiveness of counter measures

Once the corrective actions have been carried out successfully, the immediate actions must be stopped. In the automotive industry, only process-improving measures are regarded as permissible shutdown measures.

7 Prevent recurrence of error

To ensure that such an error does not happen again, the team must initiate and monitor preventive measures. In the automotive and aerospace industries, manufacturers must use the FMEA method to assess the risks identified during root cause analysis. .Also, quality management system rules and procedures may need to be adjusted.

8 Appreciation of team performance and Lessons Learned

In a last step, the achievements of the team are recognized and experiences are exchanged.

JIDOKA

JIDOKA - the Japanese term meaning automation. In this form of automation the machinery itself is checking the parts produced for defects after processing. With this constant checking of process quality deviations can be directly detected and when defects occur the complete process is automatically stopped until the problem is solved.

You might have come across the word autonomation, which is simply a combination of the words autonomous and automation that describes the automation with still human interactions. JIDOKA has to be seen as a manufacturing principle rather than a methodology. The idea behind JIDOKA is that all machines in the process chain can run without a dedicated operator checking for process stability and quality outcome. If there is a defect or non-conformity of the process, the machine shuts itself down, preventing the defective parts of getting passed on the downstream process steps and for this reason it prevents producing scrap.

In the Toyota Production System, autonomation is one of the main pillar and is also known as intelligent automation as it is firstly focusing on the quality and the ability of a self running system rather than just focusing on the output. You might have also heard the description of automation with a human touch - if a deviation occurs the machine itself will stop the complete manufacturing process and only with the interaction of an operator, after the problem is solved, it can continue production. The upside is pretty clear - you will not produce any defective parts or waste value adding activities on non-conforming components.

With the use of the JIDOKA principle a number of advantages are coming with it:

• Processing of non-conforming parts is immediately noticed, so that neither scrap nor rework occurs. Furthermore, no defective parts are passed on to the downstream processes steps

• Since the defects are detected automatically, a 100% end of line inspection is no longer needed within the scope of quality assurance

• With the help of automatic error detection, operators are no longer needed to monitor machinery, which is no-value adding activity anyway, so it can be declared as waste in the form of waiting time

• Operators have now the freedom to perform multiple tasks during the same time or are able to dedicate themselves to new tasks at all

• Maintenance activities will also decrease as crashes or malfunction due to the passing on of non-conforming parts is avoided

• JIDOKA is the basis of analyzing the root cause of failures and implement sustainable counter measures to avoid these of occurring again

Stop the line authority

Stop the line authority describes the ability or permission of operators to stop the process when a deviation or problem occurs. By doing so it is prevented that defective parts are passed on the downstream process steps.

A typical example are so called “Andon cords“ that can be pulled to immediately stop the process and inform the supervisor. To read more about Andon itself go here.

When you are in the lean world you might have come across the famous Toyota quality control mechanism “Andon Cord”. The cord is a simple tool to alert others of deviations or problems in the production line, at Toyota everyone has the authority to pull the cord. By pulling the cord almost instantly production will stop and give the alert to responsible supervisors that there is a crucial issue that needs immediate action. Following the lean principles and shop floor structure, a supervisor would step up and help the operator reviewing the deviation of product or process and define counter measures. When doing so and working with an A3 Problem Solving approach, the supervisor is coaching through the problem solving process and shares with others the outcome or lessons learned on how to prevent this failure of happening again.

In Lean Manufacturing - pulling the Andon Cord is emphasized to all operators. The target is simply to block all defective parts from leaving the company and reaching the customer. At the same time it creates the opportunity to improve your processes to prevent future defects.

NEXT STEP: GO GEMBA

Instead of explaining you the complete principle of Gemba Walks here the short version. But if you want to learn more about Gemba Walks go here.

You can discuss problems as much as you want but when you don’t get yourself to see it, it is worthless. This is where the Gemba Walk comes in the game. Gemba is a Japanese term and stands for “the place where it actually happens”. This can be everywhere and everything in the process chain, but by pulling the Andon Cord the place is defined.

Key of Gemba is not to talk in wild theories or totally abstract about problems, but to have a look where it occurs and discuss them on site (looking at the process in the real world, get rid of unnecessary power points and excel sheets! Nobody cares anyway!) Too often we want to believe the statement of an “expert” and forget about it instead of going there and have a look ourselves in oder to gain a better understanding of the problem and make up our own opinion.

VISUALIZATION

When you are at the place of action, make sure to bring an A3 with you. Make sure that you describe the process properly and the failure that occurred.

In the lean manufacturing world the best known use case of the A3 report is the problem solving report. In this case the responsible person from the quality department takes the A3 report, starts the problem solving actions and follows a systematic structure that makes it possible to describe the effects that are currently leading to a deviation from the standard. Using the A3 only makes sense when you don’t know the root cause yet. If you already know the root cause don’t waste your time. Fix it and go back to normal.

Key Questions are with Gemba Walks and A3:

1. What should happen?

2. What is happening?

3. Explain why!

The A3 Report is foldable and can be then placed at the line or the work station. This is a great and a standardized tool to visualize that a problem is known and on the watch list.

LAST BUT NOT LEAST - STOP THE LINE (JIDOKA)

Now it is time to tackle the hardest part for all players in your organization: STOP THE LINE. In Lean Management, the original term is the Japanese word JIDOKA. This concept is driven by the maxim to have the best quality of goods and to bring the potentials out of the processes or products through continuous improvement. You have to stop all production when a deviation occurs and implement effective counter measures before restarting the line.

On the first view stopping the line might sound hard and insane, as you will stop all value adding activities and actually stop shipping goods. But think about it again. Failing to solve problems when they occur will force you to pile up your inventory with non-conforming parts that will need rework before shipping. You will bind additional resources in space and workers and by that you will burn money. Finally it will keep your organization away to improve and move forward with the developments of the market and with your competitors.

This is exactly the point where the principle of continuous improvement comes in the game, where you see all deviation as an opportunity of improvement.

To practice and learn more about continuous improvement and the CIP methodology, go ahead and read the CIP article here.

If you can’t measure you can’t control

Make sure that you have an organization wide monitoring in place which provides you with all KPIs necessary to run your business. Line stops and counter measures will be part of the tracking process in order to understand if the counter measures are effective, gain a better understanding of the processes and documentation of the improvement process itself.

1. What is the deviation?

2. What are the measures implement?

3. Are the counter measures effective?

You see there is again the logic of PDCA in the continuous improvement process.

All this information will be than part of the Shop Floor Mgmt. to get the information throughout the complete organization and to make sure that all players have the same understanding in what direction your organization is heading.

Layered Process Audit

Today we will talk about layered process audits.

LPA, or Layered Process Auditing, is a quality technique developed for manufacturing management. When used correctly, LPA brings your organization to improve quality, minimize scrap and rework, plus reduce customer rejections by driving cultural change throughout your company. To gain a better idea and to understand what LPA means we will have a little deep dive.

Layered Audits are a defined approach that devotes time and resources to ensuring that high-risk procedures and error-proofing mechanisms are consistent and functional. Therefore, three important components make up a Layered Process Auditing System:

• Full focus on High Risk Processes (HRP) by a list of defined audits

• Depending on layer of audit the audit itself is performed from various levels of management

• A system of reporting and follow-up to ensure that containment is maintained based on specific needs. But also, to maintain and drive the continuous improvement process in your organization

A full stack of audits

This part of a Layered Process Auditing System is straightforward. Audits are merely a set of questions aimed to investigate machinery or processes. An LPA system's audits should concentrate solely on parts of the value adding process where deviation poses a high risk of producing defective products. E.g. if you have an end of the line quality check station that is measuring crucial parameters or functions that are critical to customers of your product and the calibration is wrong, you are producing in Takt defective or non-conforming products. No need to mention that you should keep an eye on that process. With the help of a proper LPA system you will have the EOL station within the layers allowing containment and corrective action as soon as the station surpasses set tolerances.

Multiple layers of audits comes with multiple layers of auditors

Multiple layers of authority from across your manufacturing department conduct audits on a regular basis, at a predetermined frequency, in an LPA system. For example, once per shift, the Shift Leader conduct an audit that checks the parameters or settings of your EOL-Station. Another layer of management, which may include process engineers, maintenance staff, or even the human resources department, would circulate through the system performing the exact same audit. The sample audit might be performed once a week or once a month by someone in the layer by assigning a number of auditors to this layer and establishing a timetable that cycles through the system's audits. Yet another layer of management, such as the plant manager or even executive staff (the number of levels in an LPA system can vary enormously from facility to facility, depending on your organizations demands and needs). This extra layer of auditors performs the same collection of audits on a rotating schedule, concluding the example audit once a month or once a quarter, for example.

Countermeasures, Containment Actions, Reporting and Improvement Process

In order to have an effective, a Layered Process Audit system you’ll have to combine analysis, measures and improvement process.

If an auditor observes a non-conformance during an audit, the auditor should not only document their findings but also take quick appropriate action to ensure that defective products do not leave the facility. In order to help with the documentation and immediate actions you can use the A3 report and methodology. Simple but effective. You can find it here. Anyway, the findings should be documented and made readily available to management for further analysis. An LPA system is a handy tool for debugging problem areas and identifying areas that are suitable for improvement actions when combined with a strong system for recording and reporting these audit results. A systematic approach will be discussed in the Shop Floor Mgmt. article.

Though Layered Process Audits may be developed to meet a customer or corporate demand, effective LPA systems are built, implemented, managed, accountable to, and owned by your participatory manufacturing management group. A solid LPA system may help you to take proactive control of your manufacturing operations while also enhancing product quality and business bottom line.

Deviation Management

Deviation Management is simply said the pure ability to identify deviation of a process according to the standard work process and you have a structured approach to tackle that issue.

5 Reasons to work with Deviation Management

1. Improve compliance and ownership of defective goods or processes

2. Continuous feedback to operators and staff of their deviations

3. Structured process for deviation documentation, tracking of counter measures and problem solving

4. Prioritization of improvement measures

5. Data collection to engage external suppliers and customers

Shojinka

Constantly improving the amount of workers in a production cell to match the volume of demand and type which has been given to the unit requires that training is provided to every worker in various process steps. The layout of the work cell is done in a circular or U-shaped layout, where the number of operators performing can vary and be adjusted. The capacity and ability to have an adjustable manufacturing process is relevant to meet the demand profile and have a sustainable growth.

Ever thought if there was a particular way through which you can use less manpower but produce more? Needless to say, there is a way through which you can do this: Maximizing the output while simultaneously minimizing the input is a business 101 idea and theory that we carry with us since inception, and strive hard to completely tackle for the whole of our careers.

There certainly is a way through where you can do more with less, and that way is known as Shojinka. It is also referred to as "flexible staffing" or "flexible manufacturing." Shojinka is again a Japanese term, and it was born from the lean manufacturing principles of Toyota. There is no denying that the idea of "flexible staffing" has proven to be the best performer in lean theory.

So what can be understood as Shojinka

Primarily, Shojinka is defined by two elements. The first one is the operators are trained on several workstations and following a qualification matrix. The second one is the layout for the work cell, of cause preferable in a U-Shape layout rather than a straight old fashioned line, but this has to be discussed in all cases separately.

Let’S have a look on the Pros and Cons of Shojinka

Pros

Flexible staffing, as its name suggests, has the biggest advantage in that the staff is flexible. This means that the operators have been provided with training in almost every part of the production following the qualification matrix.

This will enable them to work in areas of production where there is more demand or will allow them to switch quickly as the demand changes. Unlike a highly specialized working environment or fixed linear manufacturing, flexible staffing allows you to keep your efficiency high under every type of manufacturing demand, rather than an ideal pre-determined set. In addition to this, Shojinka also provides an opportunity for operators to work on improving products or on the various side whenever the demand falls all across the board. It will not only enable your staff or the operators to become more effective and efficient at changing levels of demand, but it will also allow them to swap between these specific levels on a shop floor that has been properly and correctly set up.

The inputs and the final outcomes are kept on the identical and corresponding sides of the work cell due to the U-shaped manufacturing line, which ultimately helps your organization of logistics and transportation. Furthermore, it also enables the operators to move conveniently between the first process step and the final process step on an assembly line without the need to walk its whole or complete length.

Cons

As soon as it has been implemented and applied, there are almost no cons to the Shojinka assembly line.

But to start off implementing flexible staffing you need to clear of some major obstacles to get started. If not already implement you have to install a training matrix and train your operators accordingly, to get them qualified to handle all aspects of your operation. Undoubtedly, it may require you to make some investment upfront.

Simultaneously with the training of your operators you will need to standardize every process step in your production. By doing so you will reduce the amount of training and therefore qualification needed in order to fulfill the requirements for the single process steps, as they are broken down to the simplest operation.

Clear and simple “Standard Operation Instructions“ (SOI) will be required to explain the operation and guide operators through the qualification and later performing the process step. By this due to variation of operators in a assembly cell they can get fast into new work requirements. In addition the supervisor can always react faster as the standard process is always described and if deviation occurs the cause is faster detected and eliminated.

So the cons can be wrapped up as investments upfront. Paying all of the expenses at the initial stages for the purpose of integrating and incorporating Shojinka will prove to be worthwhile in the end. There is no denying that your workforce will ultimately become significantly streamlined and that Takt Time of goods will be flexible to the max.

7 Steps - Problem Solving

The 7 Steps problem solving is an analysis method that is typically used in the 0miles major customer complaints and warranty complaints: when risk analysis is necessary. The single steps are as follows:

1. Problem description / risks on similar products and processes

2. Define containment actions

3. Data collection (grasping the facts / failure mode analysis)

4. Identify possible Root Causes

5. Implement corrective actions

6. Evaluate effectiveness (Tracking Chart)

7. Lessons Learned 

Root Cause Analysis is one of the crucial and basic requirements in a quality system for continuous improvement. Its target is to recognize a deviation and its origins, resolve the issue so that it is not recurring and improve the quality of the product or processes. Root Cause Analysis always depends on time if you observe a deviation start asap your RCA-activities as no problem should be allowed to grow.

To gain a better understanding let us describe the 7 Steps in more details

1 Problem Description:

Capturing the deviation -  Ask the following questions:

1. What is the problem? (symptom; use illustrations to describe as clear as possible)

2. Why is it a problem? (content of complaint / definition of problem statement)

3. Where was it detected? (location of occurrence/Area of the product or process)

4. When was it detected?

5. Who detected it?

6. How was it detected?

7. How many defective / suspect parts?

Can the problem appear on other products or processes?

1. Other parts

2. Generic parts

3. Opposite hand

2 Define containment actions:

1. Use a Tracking Chart to list your counter measures

2. Track how many defective parts have been detected

3. List in Pareto format what kind of failures have been detected

4. Put in containment actions and responsible person

5. Define when the actions have been planned and implemented

Data collection (grasping the facts / failure mode analysis) get and check the valid documentation:

1. 1st part release

2. Maintenance records

3. Poka Yoke checks

4. Process parameters tracking charts

5. Work Instructions (SOI)

6. Control Plan

7. Drawings

8. Production information

9. Error collection sheet

10. First Time Through Report

11. Boundary sample

12. Ok part available

Ask the following questions:

1. Was it the correct process? - How should it be?

2. Was it the correct tool/fixture?

3. Was it the correct part?

4. Has something changed in the process?

5. Has something changed in the product design?

6. Is the process in control?

7. Do all product components meet quality requirements?

Collect pictures, evidences and records to support analysis.

3 Build the ISHIKAWA Diagram

1. List the problem to be studied in the "head of the fish".

2. Use an idea-generating technique (e.g., brainstorming) to identify the factors for non-conformance and non-detection within each category that may be affecting the problem and/or effect being studied.

3. Repeat this procedure with each factor under the category to produce sub-factors. Continue asking, "Why is this happening?" and put additional segments each factor and subsequently under each sub-factor.

4. Continue until you no longer get useful information

To learn more about the Ishikawa – read this article.

4 Identify the Root Cause

Analyze the results of the Ishikawa after team members agree that an adequate amount of information is provided for each major category. Do this by looking for those items that appear in more than one category. These become the “most likely causes".

For those items identified as the "most likely causes" the team should reach consensus on listing those items in priority order with the first item being the most “probable" cause. A useful method here is to allow each team member to allocate 3 points to their chosen root causes. The root cause with the most points can be taken for further analysis using 5 Why.

Once the most probable causes are drawn explain failure mechanism focusing on 2 aspects:

1. Cause of non-conformance

2. Cause of non-detection named

Use the 5 Why method for looking at the problem

5 Possible Actions

Create an action plan with countermeasures for non-conformance and non-detection to eliminate/minimize the effect

Do not forget about due dates and responsible persons (preferable only one person for one action)

6 Evaluate the effectiveness (Tracking Chart)

Put in permanent actions (+ responsibility) and make clear when the action has been planned, implemented and stopped. Track how many defect parts have been detected. After implementation of permanent actions remove containment measures only if there are no defects detected any more.

7 Lessons Learned

1. Visualize BEFORE and AFTER (KAIZEN REPORT)

2. Specify what needed to be documented (e.g. Standard Operating Instruction (SOI), etc.)

3. Grasp what you’ve learned (improvements in working and detection process)

4. Think about potential applicability in your organization (review similar design, equipment, components, processes, material or manufacturing processes).

Share what you have learned within your organization.

Some of the benefits of the Root Cause Analysis process are that you will identify which procedures will need to be changed, which documents describing those procedures will require modification and who will need to be trained or re-trained.

Finally, don’t forget that the root cause analysis process must lead to an effective corrective and preventive action plan. One without the other would mean that there is no certainty that the issue is solved and that the failure cannot reoccur.

If liked this article give it a thumbs up.

Affinity Diagram

So you have a large number of ideas and need to organize them. The affinity diagram is the perfect fit to get the job done and to structure your ideas into their natural relationships. Basically the affinity diagram describes a structured outcome from a brainstorm session. You can use it to generate, organize and consolidate information related to a product or process, complex issues or different problems. After the brainstorming session you should group the ides according to their affinity or similarity. This idea creation method was created in the 1960s by Japanese anthropologist Jiro Kawakita. 

When should you use an Affinity Diagram

The typical use of an Affinity Diagram is when you are confronted with many influences or ideas in a state of chaos. Sometimes a problem seems too large or just too complex to understand it at first sight. Or you simply want that the whole team has a common understanding of a topic.

Usually you are confronted with this situation:

•  After a brainstorming session

• When analyzing open questionnaires, such as survey results

• When collecting and organizing large sets of data

• When trying to develop relationships between different ideas

• Or trying to reduce input to a higher level of categories

Typical process of developing an Affinity Diagram

The Affinity Diagram process gives a group a direction to go beyond normal creative thinking and defines categories to get all thoughts in order. This technique opens the doors and shows relations in between the whole organization which is typically separated due to department silo thinking. The Affinity Diagram has no limits, so don’t be irritated if you have to deal from 20 up to 400 items after a session. It is a starting point not more not less.

Materials needed: Sticky notes or cards, marking pens, and for sure a large surface (wall, table, or floor). Brown paper is a good way to start. 

Step 1:

• The brainstorming

• Write down all ideas on separate sticky notes or cards.

• Spread the sticky notes or cards randomly all over the brown paper

• Gather all participants around the brown paper after all notes are taken

Hint: Use big markers so it easy to read for everybody from distance. Make key statements on the notes don’t write an essay.

Step 2:

• Try to sort all ideas that are related in some way and group them up

• Try to find relations between these several ideas

• Let the team sort ideas

• Try to find 8-10 relation groups

• Repeat until all ideas are grouped

It is fully reasonable that there might be an idea staying by itself or that team members will move an already grouped note again to another. If an idea belongs in two groups, make a second sticky note or card.

Hint: In this step it is crucial that there are chats going on, it has to be done in silence. Focus is on sorting and grouping ideas. Headlines are done afterwards! Not upfront!

Step 3:

Open discussion with your team.

Try to find common categories and define headlines for each group together with all team members. Discuss what you see or why members see an idea in a different category. If necessary, make changes and move ideas between categories. In the end, when all ideas are grouped in the consent of the whole team, define the headlines of each group. Try to find a catchy headline that describes the meaning of the category in short.

Hint: Cards with the headline should be in a different color than the rest and should be self explaining about the group.

Step 4:

If reasonable, try to define “mastergroups” of several “subgroups”.

Sort all ideas to their identified category by placing all ideas under the “headline card”.

Hint: The sorting is done by gut feeling, not with a scientific approach.

SMED

Single Minute Exchange of a Die

This series of techniques was invented by Shigeo Shingo to set-up manufacturing equipment in less than 10 minutes. Most of the time people think in one minute but is thought as single digit minutes.

So what is behind the set-up time reduction?

This method is driving to increase the net production time as much as possible by minimizing the needed time to change from one model to another. As far as you have two or more products running on your line or to simply exchange parts of your machine or equipment that regularly needs to be replaced. This is increasing the flexibility of your production and allows you to react on changes in demand more quickly.

When trying to reduce changeover tomes the typical goal is to reach less than 10 minutes. The short summary of SMED activities is to analyze each element of the changeover with the EMIPS method to see if it can be eliminated, modified or moved outside the process, integrated, tasks are parallelized or synchronized.

SMED

When looking at those three stages we can simplify it further for each stage:

Just ask yourself:

Separate:
Can this task, as currently performed, be done while the line is still running?

Convert:
Which process steps can be moved out of the changeover itself and be parallelized or completely taken out? How can you do it?

Synchronize:
How can the remaining tasks be synchronized so you need as little time as possible to complete the changeover?

I save you the story with the pit stop in formula 1 - just google it by yourself and you will find the evolution of pit stops. Quite interesting and still valuable.

So what are the benefits of SMED?

The first effect you will see on improvements of the OEE of your manufacturing facility. If this is important for you and you are numbers driven. In the end you will reduce downtimes and therefore manufacturing costs as your machines will have a greater net operating time.

With a long term perspective SMED will enable you to have smaller batch sizes, which will improve your possibilities to react faster on changes of customer demands and in addition your inventory (tied capital) and WIP (work in progress) will decrease.

PPM

Parts per million or also known as Defect Parts per Million

The PPM rate (Defect Parts per Million) shows how many NOK parts have been produced or occurred with one million parts produced or delivered. Rates can be categorized into two main processes. Lower rate on processes where defects can be easily found and higher rate on processes where defects are mainly hidden, e.g. the structure on casted parts. The PPM rate is mainly used to determine the quality capability of deliveries of manufacturing goods.

Thinking about the automotive industry with the SOP (Start of Production) there are still many failures and defects in the process and those must be eliminated through continuous improvement (CIP) measures. In order to take the customer wishes into account, PPM rates are implemented as KPIs to see the progress of your actions concerning the reduction of those defects.

If you are dealing with the automotive industry you will find a lot of PPM regulations and they are often misused as a source of income. OEMs will give you penalties for exceeding the PPM rate, this is a very common approach. Small and mid-sized companies typically sign some sort of quality agreement with OEMs or their customer, Tier 3 up to Tier 1, this is sort of a framework for PPM rates for manufacturing processes throughout the complete value stream of production.

If you have your customer knocking at your door and asking for a PPM regulation, make sure to categorize your production into major fields of operation such as casting, molding, machining, etc. Or if you have dedicated manufacturing lines for your customer try to focus on the end of line quality check and agree on which ratio is acceptable and which not. Don’t go in the details, this will only give you a higher risk of screwing it up and a wider area of attack. And finally try to agree realistic PPM rates, nothing worse than promising something you already know you can’t achieve.

Just to make sure you got this, the way PPM will be evaluated depends on the criteria defined between you and your customers. E.g. agree on with how many non-conforming parts an entire delivery will be rejected.

Until know we looked on it as supplier, so let us change perspective and see it from customer point of view. 

Supplier evaluation includes several performance measures in order to compare them and rank them properly. The PPM rate is the most meaningful evaluation to asses the quality among your suppliers. In addition to the PPM rate the number of complaints and costs per defect can be included as evaluation criteria. Specially in the automotive industry there are several rules and regulations but key is certification. You can make sure that your supplier follows several rules by being certified after standard norms, just think about EN ISO XXXX. Even when the certification process can be seen as complete waste of time and money, in the end you know that the suppliers know the rules of the game.

So what to do when the PPM rate is exceeding the agreed limit. First of all your quality management should step in. As customer I would ask for an 8D report, of course depending on the failure rate. Therefore again, agree what limits you will have and at what limit what actions will be necessary. It might also be that you will demand from your supplier to immediately conduct a sorting action.
What ever it is or you will work on make sure to follow a structured approach to successfully tackle the PPM rate. For this we recommend to read the PDCA article or the A3 article. No worries there is more that you can do but in the end problem solving in all the cases always follows the PDCA cycle.

The PPM rate is also a great example for a KPI that can measure the effect of your improvement or KAIZEN actions. You see it is a versatile KPI that effectively runs your business and shows you if you’re on track.

A3 Report

The term A3 report comes simply from the size of paper which is used for the documentation of the report. The structure itself follows the PDCA methodology.

In the lean manufacturing world the best known use case of the A3 report is the problem solving report. In this case the responsible person from the quality department takes the A3 report, starts the problem solving actions and follows a systematic structure that makes it possible to describe the effects that are currently leading to a deviation from the standard. Using the A3 only makes sense when you don’t know the root cause yet. If you already know the root cause don’t waste your time. Fix it and go back to normal.

Schematic structure of an A3 report

Let us go through the different stages of an A3:

Describe the problem:
The A3 gives you the chance to initially describe the problem or symptoms - this can be done verbally or as a sketch. Don’t forget to mention when it was and under what circumstances. No matter what it must be easy to understand.

Keep in mind that the target in Lean Mgt. is always to train the people to improve their problem solving skills. Therefore if you are a quality representative try to coach the operators in this process or make a team work out of it.

The result of the description of the problem is the delta from the target state.

Root Cause Analysis:
Please be aware that your paper is only and A3 format. So either you go with an Ishikawa or a 5 Why. But not more. If you can’t conduct a root cause analysis with either on of these methods, the A3 is probably the wrong approach at all.

Counter Measures:
Following the PDCA plan your counter measures what you and your team or operators found out or might think have the most effect.

Lessons Learned:
Great you have done the job, you followed the PDCA and the root cause was found, defined measures helped and the problem is solved. No finalize the A3 report on where to find the documentation and what impact will it have on other operations as lessons learned.

When you are a quality representative using the A3 method ensure that the A3 report is also used for long term development of employees and quality standards.

With the help of the A3 report and a clear coaching through the quality department, all employees learn to recognize, evaluate and solve problems on their own. This is serving the general rule of continuous improvement (CIP)

Therefore the A3 systematic increases the problem solving competencies of your whole organization. And as already said, a problem is only the missing of an idea.

If you want to go deeper on the A3 report itself or the problem solving with the help of A3, we recommend our reading pick “Understanding A3 thinking” this book goes in the details and gives you great insights. Read our summary here. Or you can’t wait? Here is the link straight to the book:

Ad

Buy on Amazon