Articles by Results

Global 8D - Eight Wastes, Their Common Causes & Solutions

Posted by Graham Cripps on Tue, Aug 11, 2015 @ 04:40 PM

global_8d_logoGlobal 8D - Eight Wastes, Their Common Causes & Solutions

Our Subject Specialist, Graham Cripps, has produced a matrix showing the characteristics, causes and possible solutions to the Eight Wastes of Global 8D.

Download your copy here and if you have any questions email him directly on graham.cripps@resultsresults.co.uk

New Call-to-action

Don't forget to check out our Global 8D pages here to find lots of useful resource to aid your G8D implementation

We also have a recommended reading list for you here

Enjoy, and don't forget we are here to answer any questions you may have!

The Results Team

 

Topics: Global 8D, G8D, problem prevention, 8D, 8D benefits, Business Process Improvement, Resources, lean, lean foundation

Global 8D - D7 & D8: Prevent Recurrence and Recognise Team and Individual Contributions

Posted by Graham Cripps on Mon, Aug 10, 2015 @ 12:05 PM

G8D Process

Global 8D - D7 & D8: Prevent Recurrence and Recognise Team and Individual Contributions

graham_cripps_dec_2010_formal-3

 

In this article I am going to cover the last two stages of the Global 8D problem solving process

I mentioned in my last article that some problem solvers’ activity will stop after having implemented and validated the permanent corrective action

 

 

These last two important steps ensure that: 

  • This type of problem could never occur again
  • Reinforce behaviours and esteem of the team and individuals

These last two steps in the G8D problem solving process are fairly short to explain and technically not much of a stretch. However, their importance should not be underestimated.

Astute problem solvers know that whenever a problem occurs there is normally a procedure, policy or practice (systemic) that has allowed it to happen. I call this the 'root cause of the root cause'. This needs to be established and resolved.

Just as important is recognition of the problem solving effort that has been afforded by the G8D Team and other individuals in the business.

Prevent Recurrence

As stated above, the next step is to examine the evidence established during the problem solving process and establish the policies, procedures and practices that led to this particular problem. For this we use a problem solving tool called 5 Why’s (sometimes called stair stepping).

In essence this involves asking the question “why” of the root cause until the root cause of the root cause is established. The question may be asked more or less than 5 times, it does not have to be 5!

Global 8D ppt

Example: A small engineering company had problems with hole positions being out of tolerance in some instances. Having 'masked the problem' for some time with constant drill changes, the problem solving team discovered the root cause as being a worn spindle bearing. The 5Y’s exercise went something like this: 

  • WHY – was the bearing worn?

  • BECAUSE – it had become dry

  • WHY – did the bearing become dry?

  • BECAUSE – the operator did not carry out shift autonomous maintenance routines fully

  • WHY – didn’t the operator follow maintenance routine fully?

  • BECAUSE – he was not properly trained during induction

  • WHY – was he not trained on induction?

  • BECAUSE – his induction programme missed this off the sheet

  • WHY – was this missing from the sheet?

  • BECAUSE – the induction plan was not signed off by Engineering (Root Cause)

In fact, the induction process allowed for any manager to sign the induction plan (the systemic issue). The induction planning was changed to require function based sign off.

These systemic issues need to be fixed. The goal is to change the system that allowed the problem to occur in the first place and to prevent similar problems from happening.

Because these systemic issues are normally beyond the brief of the G8D team, these changes are made at management level. However the team does have the opportunity to offer recommendations for systemic improvements.

Recognise Team and Individual Contributions

This final step in the Global 8D process is about closing the process and involves: 

  • Recognition and review of team experience (Cooperative Learning)

  • Completing any unfinished business

  • Closure process

Recognition and Review of Team Experience

teamwork_logo_finalThe application of the process requires skills and experience of the business to be able to make progress towards a satisfactory problem resolution.

These skills and experiences are the reason the team are selected.

The problem solving process drives improved data-driven understanding of the problem at each step of the process. As more is understood about the problem, root cause and resolution, different skills and experiences will need to be 'drafted in' at various stages throughout the process.

Recognising the effort of the team and other individuals involved is important as it tends to reinforce behaviour and self-esteem.

Completing unfinished business

Making sure all the problem solving activities have been completed and include:

  • Finalising and archiving documentation

  • Recognising technical lessons learned

  • Making final presentation to the Champion

  • Expressing experiences from team member to team members (Cooperative Learning)

  • Archiving all the lessons learnt from the problem solving effort

  • Ensuring all other related documentation is revisited and up to date (e.g. FMEA’s, Control Plans, etc.)

 

Closure Process

Global 8D Report Template

 

In this final activity the team ensures that the completed 8D report is circulated to all concerned detailing all the above activities including the recommendations for systemic changes.

 

 

 

 

Next Time

There are a number of ways you can gain the skills necessary to apply this world class problem solving methodology in your workplace. Shortly I will share with you how you can gain access to training at various levels, quickly and easily that will get you on the path to solving problems effectively.

If your problem needs immediate attention, then you can contact me directly on graham.cripps@resultsresults.co.uk or you can visit our web site www.resultsresults.co.uk for more information.

Graham Cripps
Results Consortium Ltd

Topics: Root Cause, root cause analysis, Global 8D, G8D, Plan Do Check Act, Permenant Corrective Action, PCA, problem prevention, Problem Desciption

Global 8D - D6: Implement and Validate the Permanent Corrective Action

Posted by Graham Cripps on Mon, Aug 10, 2015 @ 12:00 AM

G8D Permanent Corrective Action

Global 8D - Implement and Validate the Permanent Corrective Action

graham_cripps_dec_2010_formal-3

 

Having established and verified the best PCA’s for the root cause and escape point, the next step is the implementation of the PCA’s.

To do this we employ the Deming 'Plan Do Check Act' cycle to ensure successful implementation.

The Global 8D Problem Solving Process is a structured approach to getting to the root cause and the escape point and taking actions to ensure that these are eradicated permanently through effective controls and actions that are embedded in the operations of the business.

In this article I will explain the steps that need to be taken to ensure that this is done efficiently and effectively.

Global 8D ppt

Implement and Validate the PCA’s

Deming PDCA Cycle

 

The Deming cycle is used in the Global 8D process, starting with the G8D form and is used at various steps through the process.

 

In this current step the cycle is used to: -

PLANThe implementation of the Permanent Corrective Action (PCA) giving particular attention to:

  • Plan for validation of the PCA

  • Plan to remove the Interim Containment Action (ICA) as part of implementation of the PCA

  • Integrate check for side effects

  • Plan for continued monitoring of effectiveness of the PCA’s

  • Plan for all the necessary resources

  • Plan for all documentation, process instructions, training and communication for the implementation of the PCA’s

  • Define clearly the what, when, who and when (team roles and responsibilities)

DOInitiate the implementation plan for both the root cause and escape point, ensuring that all the necessary steps have been managed and adhered to.

CHECKCheck that the PCA’s have been fully implemented and integrated into the operational and business processes. Validate the PVA’s for both the root cause and escape points (see item below on validation). Validation will be carried out at this stage and on an on-going basis.

The measures for effectiveness of the PCA’s should use the same measurables that we used to describe the problem in the article Describe the Problem. In other words comparing like for like data.

ACTTake actions on any variation from the plan or expected outcomes.

Validation

Validation is proof that is developed after implementation has taken place, over a period of time and must:

  • Follow successful verification

  • Provide a data driven comparison before and after implementation

  • Check that the implementation does not introduce a new problem or side effects

Validation is:

  • Normally performed under defined operating conditions on the final product or process

  • May be necessary in earlier stages prior to product completion

  • Uses the same indicators that demonstrated the problem and may be easily tracked

Complete the G8D Report (Template)

 

g8d_-_report_form_-_pdca

 

Complete the Global 8D form and circulate. Remember to update team composition for any changes that are made, at the end of this stage.

The G8D form is a summary of the problem solving activity and is supported by all of the other worksheets, data and supporting information including the validation results that is generated as a results of the problem solving activity.

 

 Download Your Global 8D Report Template

There are two more steps to complete the Global 8D problem solving activity. A lot of problem solvers would normally stop at this point assuming that the job is done. However, for the problem solving process to be truely completed we need to: 

  • Recognise that there was a process, procedure or other activity that allowed this problem to occur in the first place. This is the root cause of the root cause.

  • Having put a lot of effort into the problem solving process, the final stage is to acknowledge the contributions made to the problem solving and to ensure that all lessons learnt are shared and recorded

So join me next week for the final two articles that explain these last two stages. I will also provide access to further help to enable you to apply this world class problem solving methodology in your workplace.

 

Graham Cripps

Results Consortium Ltd

Download your free G8D Report template

Topics: Global 8D, G8D, Escape Point, Plan Do Check Act, Permenant Corrective Action, PCA, problem prevention, Problem Desciption

FMEA | Function Tree - Defining Product Design Functions

Posted by Graham Cripps on Wed, Aug 05, 2015 @ 10:46 AM

Function Tree - Defining Product Design Functions

Defining the product design functions (or design intent) is one key to the success of conducting a successful Design FMEA.

FMEA is a risk management tool that looks at and manages the risk of failure of the products function(s). Failure to identify these leads to the inability to manage the risk of failure of missed functions.

If we know all of the functions that a design has to achieve, then we can consider how those functions could potentially fail to meet the customers requirements. This is the key to understanding the exact functions that the product performs.

This often causes difficulties with FMEA's as there is a tendency to generalise functions as a combination of functions.  Let me explain, using a fountain pen as an example.

FMEA_FT_Blog_P1Lets consider the design of a fountain pen. What is a primary function of a pen? To write?

We cannot design this pen to write on its own!

We have to consider several design functions which might include: to retain ink, to dispense ink, to provide a comforatble grip, to allow for left and right handed use, to resist leaks, to provide smooth contact on a writing surface

The outcome that a user expects is that (in the hands of a capable person) the pen will write. However, this is not a single function of the pen's design (as seen above) but a combination of functions that deliver the customer requirement.

Developing A Function Tree

A robust method of defining a products' function is the application of the Function Tree. The function tree is a process used to determine prime functions and their subordinate functions for a given product. The process steps are as follows:

  • Brief the Team
  • Brainstorm the functions of the product
  • Agree primary functions
  • Organise the brainstorm outputs onto a function tree

Brief The Team

The Team is led by the designer owner and briefed on the process steps and methodology for defining the functions.

At this stage it is important to establish that all the team members are sufficiently familiar with the FMEA process to be able to fully contribute to the FMEA effort. The Team meeting would be arranged, with appropriate Team roles (leader, scribe, time manager and facilitator) and an agenda that sets time aside for briefing, brainstorming, organising the brainstorm outputs and reveiwing.

Brainstorm The Functions Of The Design

Follow the rules of brainstorming:

  • Keep the output visual
  • Keep to the alloted timescales (time managers role)
  • Volume is King!!
  • Do not discuss the ideas (this comes later)
  • Do not criticise
  • Involve all of the team (facilitators role)
  • Do not 'organise' the brainstorm (this comes later)

We use a VERB - NOUN sentencing technique to describe each function

FMEA_FT_Blog_P2

Organise The Brainstorm Outputs Onto A Function Tree

It is very seldom that design specifications are written in this way, so we use the Function Tree tool to capture and sort all the functions of a design from Primary functions to Tertiary functions.

Primary Functions - those that are identified as nearest to the customer usage intent

Secondary Functions - those unique functions that support the primary functions

Tertiary Functions - functions that support the secondary functions and typically suppport more than one

Measureable Level - sometimes referred to as Actionable Level, these functions have a specific measurable or set of measurables that can be specified.

Function Tree Construction

FMEA_FT_Blog_P3

 

First, organise the Brainstorm Output by selecting the primary functions, then secondary and so on. Remember there may be more or less than the four levels shown here, and it is okay to add or duplicate functions

 

 

FMEA_FT_Blog_P4

 

To check that the functions actually support one another you should ask 'How?' the primary function is achieved, through to the secondary and so on

 

 

 

FMEA_FT_Blog_P5

 

 

 

Then look at the tertiary functions (lowest level) and ask 'Why?', moving back up the tree and providing the answer at each level, making grammatical sense throughout.

 

 

 

Assessing Questions

  • Have all functions been transferred from the brainstorm to the function tree?
  • Have all primary functions been developed to an actionable level?
  • Is the sentencing technique obvious and correct?
  • Have all primary functions been recorded on the FMEA record?

 

graham_cripps_dec_2010_formal

Graham Cripps
ResultsResults

 

Topics: Design FMEA, Process FMEA, FMEA Form, FMEA Action Planning, DFMEA, FMEA FAQ's

Sustaining Improvement - The Foundation

Posted by Graham Cripps on Tue, Aug 04, 2015 @ 11:43 AM

Sustaining Improvement - The Foundation 

graham_cripps_dec_2010_formal-3-1

 

I have been asked on a number of occasions why sustaining improvement has been so difficult. In the words of a recent client "We have tried several times but it just doesn't stick"

My question to the client's management team had to be "So what changes have you made in your behaviours?"

 

Regardless of the methods used (Six Sigma, Lean or any other form of Continuous Improvement) the key to success rests with the Senior Management Team.

Sustaining_Imp_blog_P1Any improvement strategy as to be driven by top down behaviours that are linked to the organisations values and vision. This means that instead of 'telling' what needs to be done the Senior Team get involved in the planning, showing and doing. They need to be see to be seeking to understand all of the issues that need to be addressed before they can ask for this understanding in their teams,This will involve Active Listening.

Bringing in a consultant cannot fix the problems associated with disengaged behaviours. Don't think for one minute that walking around the business saying "Good morning" will cut it either..... The Senior Team have to be totally committed and involved before they can begin to ask anyone else to be

I have worked with organisations where members of the board have been very knowledgeable about Continuous Improvement, but have made the mistake of telling people rather than showing them.

So how do we make it happen?

And how do we make it stick?

Starting At The Top

The Company Vision is a statement of what the company wants or needs to achieve. The Mission includes the measurables, in other words 'How will we know when we have got there?'. This requires a good understanding of the goals and what success will look like.

The action planning should be carried out in two stages, the first being the action plan for the Senior Team. The second should involve the next tier of management developing their plan with the support of the Senior Team. At this stage, understanding the team must be a priority.

Knowing that change can be stressful is not enough, providing support and development opportunities in terms of Mental Toughness is part of the plan. 

Facilitating Change

All improvement strategies will involve change. With this in mind, the Senior Team should set the reporting structures in place but not rely on these alone. They should be seen to be getting involved in a supporting role, to ensure that all employees feel comfortable discussing the issues in an open and honest way. Showing how this can be done should be a natural behaviour.

In this way all issues and blockages can be faced honestly, without fear and can be discussed openly to find the best ways forward. Facilitating change is a key role of the Senior Team and they should facilitate through actions not just words. In other words - SHOW DON'T TELL

Commmunication

A key element is communication, the most important part is Active Listening.

Even before the planning stage, the Senior Team need to brief the whole business on the detail behind the Vision and obtain feedback that will provide an early insight into some of the challenges that may have to be managed during implementation.

Remember, the well being of all company members is the responsibility of the Senior Team so understanding the people is critical. The detail of an effective support mechanism need to be an integral part of the business objectives, not just for change.

Throughout the planning and action stages of the implementation, constant open communication is important to ensure the plan is kept alive and relevant to everyone.

Developing the team to cope with change, from top to bottom, is a challenge that must be faced before the initiation of change. This is where Mental Toughness assessment can help.

Cascading The Plan

When setting goals for the business each facet of the business needs to be considered. For example, what does each individual's contribution look like and how are they to achieve it? How will they be supported and developed where necessary?

Mental Toughness is a term that encompasses the 4C's:

Control - I really believe I can do this
Commitment - I promise to do this, I'll set a goal
Challenge - I am driven to do it, I will take a chance
Confidence - I will work hard to use my abilities to the full

For more on Mental Toughness and how it can be reliably measured and developed, click here.

Involving each individual requires the Senior Team to address the fundamental question of 'Whats in it for me?' at every level of the business. We all only do anything for purely selfish  reasons, either it suits us or is the right choice for us at that time.

Make It Your Own

There are lots of books covering the subject of Continuous Improvement and, like this article, a lot contain personal perspectives and opinions. It has been my experience, over the last thirty years or so, that the best programmes are those that are truly 'owned' by the organisation - that is to say everyone in that business.

At the end of the day, the responsibility for the success or failure of any change lies with the Senior Team. Effective communication, goal setting, delegation, facilitation, review and having the right people in the right position are all important and are the responsibility of the Senior Team.

Graham Cripps

New Call-to-action

 

 

 

 

 

Topics: Continuous Improvement, Business Process Improvement, People Development, lean, lean foundation

Global 8D – D5: Choose and Verify Permanent Corrective Action (PCA)

Posted by Graham Cripps on Tue, Aug 04, 2015 @ 10:12 AM

G8D Permanent Corrective Action

Global 8D – D5: Choose and Verify Permanent Corrective Action (PCA)

Graham Cripps, Director

Having determined the root cause/s of the problem and the escape point you are now in a position to determine and choose the most appropriate Permanent Corrective Action (PCA).

PCA’s need to be considered for both the root cause and the escape point.

 

 

The PCA needs to meet several requirements that satisfy both customer and business needs.  Given that there may be a number of possible permanent corrective actions that may be applied, I will describe how the most appropriate PCA is arrived at.

The process for determining the possilbe PCA's will be driven by the nature of the root cuases and the business objectives.

The final choice of which PCA's to implement will be determined from:

  • The best interest of the customer

  • The needs of the business

 Download your free Decision Making Worksheets

Define Permanent Corrective Actions

Having identified the root cause of the problem under investigation, the team will have the data and information at hand to determine what corrective action options there might be available to implement. These are all considered and articulated in such a ways as to ensure that all the necessary steps needed to remove and protect against the route cause have been considered.

As stated above, the process for determining the possilbe PCA's will be driven by the nature of the root cuases and the business objectives.

Chose The Permanent Corrective Action

For this activity we will consider two levels of needs: 

  • Givens – those criterion that must be met (mandatory) and that are measureable and realistic to achieve and satisfy both customer and business needs

  • Wants – those criterion that are nice to have but not necessarily critical and also cover both customer and business aspirations

Examples

Givens could be: 

  • Must be implemented within three months

  • Must not cost more than £25,000 to set up

  • Must be able to continue delivering product during implementation

  • Must solve the root cause of the problem permanently

Wants could be: 

  • To be cost effective in the first year of operation (Set up costs plus running costs within the first year)

  • To be introduced as soon as possible

  • To be implemented without overtime

  • To have zero impact on energy consumption

  • To work on both lines simultaneously

There are two worksheets that are used in this process, the Criteria Worksheet and the Decision Making Worksheets.

Criteria Worksheet

describe the image

Using the Criteria Worksheet on the right, the Wants are scored in terms of relative importance, 10 being the highest. This score will be used as part of the "choosing" process.

The Givens are not scored, these are things that must be achieved by the PCA

This is worksheet used for recording the givens and wants. These are normally populated by the business management team.

A copy of this can also be downloaded free, accessed via a 'button' at the end of this article.

 

Decision Making Worksheet

Having established the Givens and Wants, you can now rank each proposed PCA against these criteria. To help this process we use the Decision Making Worksheet.

NOTE: the number of Givens and Wants worksheets used will depend upon the number of proposed PCA's. One complete section must be recorded for each proposed PCA

G8D   Decision Making Choices Worksheet

 

The Decision Making Worksheets are used to rank each of the PCA’s by first determining if the PCA meets all of the givens.

If the PCA does not meet all of the givens, then it cannot be progressed in its current form.

Then the wants are scored as to how well the PCA achieves each criteria.10 is completely and 0 is not at all.

The scores are added up to and this summative score is used to rank the PCA’s

The highest scoring PCA option is normally the one chosen to move forward with.

 

Verify The Chosen PCA

Before the PCA is fully confirmed, the Global 8D team need to verify that the PVA will actually meet all of the givens and the wants are achieved at the level declared in the decision making worksheets

The Team must verify that the PCA will eliminate the root cause permanently for both the root cause and the escape point.

When verification testing is carried out, it is critical to remeber that an Interim Containment Action has been put in place. Verification must be carried out in such a way that there is no influence on the outcome of verification testing. e.g remove the ICA for testing purposes.

Complete The G8D Form (Template)

G8D Summary Report

 

Complete the Global 8D form and circulate. Remember to update team composition for any changes that are made at the end of this stage.

The G8D form is a summary of the problem solving activity and is suppoirted by all of the other worksheets, data and supporting information. At this stage the report should include the decision making worksheets, verification testing process and data generated as a results of the problem solving activity.

 

 

 

Graham Cripps 

Results Consortium Ltd

 

Topics: Root Cause, root cause analysis, Global 8D, G8D, Interim Containment Action, Escape Point, Plan Do Check Act, Permenant Corrective Action, PCA, ICA, decision making

Global 8D – D4: Define and Verify Root Cause and Escape Point

Posted by Graham Cripps on Tue, Aug 04, 2015 @ 09:30 AM

G8D Root Cause

Global 8D – D4: Define and Verify Root Cause and Escape Point

Graham Cripps, Director

 

At this stage in the G8D problem solving process you have now established the Interim Containment Action (ICA) thus buying some valuable time to concentrate on solving the problem permanently. Also you will have reviewed the team composition to include all the right skills and experience are available for the next step in the problem solving effort.

 

 Download your FREE Root Cause Worksheets

Before I go any further I need to establish two key definitions: -

Escape Point: - the place in the process where the root cause of the problem went undetected allowing the problem to occur

Root Cause: - the lowest level event that can be attributed and proven as that which caused the problem to occur

The Global 8D process uses a number of forms to help drive this process and are as follows: -

  • Differences and changes worksheet

  • Possible causes worksheet

  • Possible root causes worksheet

These sheets are used to drive the discussions and problem solving efforts and form part of the process for narrowing down causal theories to the root cause.

 

G8D Process Outputs

As already mentioned, the G8D process is structured in a way that drives down from the effect or symptom, to the problem and then the root cause. Like a funnel, the process is about filtering out all the theories and ideas using facts (data driven) to be able to find and verify the root cause.

The object of all problem solving is to get to root cause and then take action to correct and sustain the improvement.

 

  

 

Define Root Cause

To explain the process I will use sections of the worksheets to aid understanding and to demonstrate how these worksheets are used.

STEP 1 – Define what is different about the 'IS' compared to the 'IS NOT'

G8D   Worksheet Alignment 1

For this step we use the differences and changes worksheet to help drive the process.

This model shows the Is/Is Not worksheet and the Differences and Changes Worksheet side by side.

You will notice that the Is/Is Not and the Differences and Changes worksheets align.

The reason for this is that the question is asked for each entry on the Is/Is Not form “what is different in, on or around the “IS” when compared with the “IS NOT”?

 

 

Fundamentally there must be differences between the 'IS' and the 'IS NOT' or both would have the problem

Then we need to ask the question what has changed in, on or around the 'IS'? Something must have changed or the problem would have always been there. This must be factual so it’s OK to generate a question log or ask a team member to go and find out.  

STEP 2 – Develop Possible Causal Theories

G8D   Possible Causes

The Possible Root Causes Worksheet is used to record each root cause theory.

First brainstorm the possible causes and record on a separate media.

For each of the causes develop a causal theory that explains how that possible cause would result in the problem being experienced.

Example: the problem could be that the car would not start and the possible cause is 'the auxiliary belt is slipping'. The developed causal theory might read 'the auxiliary belt has worn and is now slipping causing the slow rotation of the alternator thus delivering reduced charge for the battery. The battery has therefore lost charge over time'.

A causal theory is developed for each possible cause.

STEP 3 – Establish Possible Root Causes

G8D   Possible Root Causes

Using the Possible Root Causes Worksheet (which is again aligned to the 'Is/Is Not' worksheet), ask for each causal theory the question for each entry on the 'Is/Is Not' worksheet, does this explain the reason why the problem exists on the 'IS' and not on the 'IS NOT'

For each time the answer is yes put a plus (+) sign. If you do not know or need to find out put a question mark (?). If the answer is no, put a minus sign (-)

When a no is established then this possible cause cannot be a possible root cause. Move onto the next causal theory. Complete this for all causal theories. The results you will be left with are all of the possible route causes.

This is a complex step in the problem solving process and needs diligence on the part of the G8D Team members to ensure assumptions are not made. If in doubt, go and find out!

STEP 4 – Verify Possible Root Causes

For each of the possible root causes, there now needs to be a practical activity to verify the possible root cause. This should be carried out in practical terms where ever possible. However, in some instances modelling may be required.

If the possible root cause is introduced then this should 'switch the problem on'. Once the possible root cause has been removed, this should 'switch the problem off'

This process is repeated for both the root cause of the problem and the root cause for the escape point.

Complete the G8D Form (Template)

G8D Report

 

Complete the Global 8D form and circulate. Remember to update team composition for any changes that are made at the end of this stage.

The G8D form is a summary of the problem solving activity and is suppoirted by all of the other worksheets, data and supporting information (including the worksheets above) that is generated as a result of the Global 8D problem solving activity.

 

 

 

Graham Cripps

Resuts Consortium Ltd

 Download your free Is-Is Not template  Download Your Global 8D Report Template

 

 

Topics: Root Cause, root cause analysis, Global 8D, G8D, Interim Containment Action, Escape Point

Global 8D – D3: Develop an Interim Containment Action (ICA)

Posted by Graham Cripps on Mon, Aug 03, 2015 @ 01:30 PM

G8D Interim Containment Action

Global 8D – D3: Develop an Interim Containment Action (ICA)

Graham Cripps, DirectorHaving already put into place an emergency response action (ERA), the G8D Team now need to replace this with a more considered ICA.

In this article I will describe and discuss the Interim Containment Action (ICA).

Like all structured problem solving methodologies, the continuous review of the G8D Team composition is important to ensure that the team has all the right skills and knowledge to maximise the problem solving efforts.

Having established that we have a problem we need to protect the customer (internal or external) from the effects or symptom of the problem. This is done for two reasons: 

  • To ensure the customer has minimal or no impact felt as a result of the problem 
  • To buy time for the problem to be investigated and solved

Having already put in place an ERA the team now to apply a more considered option to portect the customer, and that is the ICA. By its nature, an ICA will normally be expensive to implement as it will probably involve an additional process being introduced and could include:

  • 100% Inspection
  • Rework
  • Sorting good from bad
  • Field service action

As can be seen, any one of these actions would add considerable cost, however they are necessary to protect the customer. Remember that some of the above actions are not 100% effective, even 100% inspection is subject to variation.

Note: Sometimes the ERA might be considered as the best ERA. In these cases, make sure this is recorded and why.

G8D SnapShot

An ICA is, as it states, interim. The Global 8D process drives learning about the problem to enable a fuller understanding of the problem so that, in some cases, a more cost effective containment action can be derived.

Example: An automotive manufacturer was experiencing water leaks between the inner and outer front wing of a vehicle under water test at the factory. The ICA was to add a thin bead of mastic sealant the whole length of the inner wing before welding the inner and outer together. Once the problem was better understood the length of the mastic sealant applied was reduced to one small area. When making several hundred a day, these few seconds and material savings were significant. 

The choosing and implementation of the ICA uses the Deming Plan Do Check Act Cycle.

PDCA Cycle

PLAN – Chose the most effective ICA and plan its implementation. This will involve verifying that the ICA is effective and that all the necessary work instructions, resources and equipment are made available, on time. It is important to ensure that the ICA is made “official” for accounting and operational purposes.

DO - Implement the ICA as per the plan, ensuring that the action is clearly communicated at operational and management levels.

CHECK - Check that the ICA has been implemented exactly according to the plan and that it continues to be effective.

ACT – Take action to ensure ICA remains effective and sustained within daily operations as necessary.

Assessing Questions

  • Are ICAs required?

  • Is a Service Action required as part of the ICA?

  • What can you learn from the ERA that will help in the selection of the ‘best’ ICA?

  • Based on consultation with the G8D Customer and Champion, have criteria been established for ICA selection?

  • Based on the criteria established, does the ICA provide the best balance of benefits and risks?

  • How does this choice satisfy the following conditions?

    • The ICA protects the customer 100 % from the effect.

    • The ICA is verified.

    • The ICA is cost-effective and easy to implement. 

Complete the G8D Form (Template)

G8D Report

 

Complete the Global 8D form and circulate. Remember to update team composition for any changes that are made at the end of this stage.

The G8D form is a summary of the problem solving activity and is supported by all of the other worksheets, data and supporting information that is generated as a results of the problem solving activity.

Ensure that a a full account of the ICA and supporting documents are alailable to support this summary.

 

Graham Cripps 

Results Consortium Ltd

Download Your Global 8D Report Template

Download Your Global 8D Assessing Questions

 

Topics: Global 8D, G8D, Interim Containment Action, PDCA, Is/Is Not

Explaining SPC - Applying SPC

Posted by Graham Cripps on Mon, Aug 03, 2015 @ 12:45 PM

Applying SPC

graham_cripps_dec_2010_formal-3

 

Statistical Process Control (SPC) is like many tools used in Continuous Improvement (CI) and Quality Control methodologies in that it is not something that you would use for every process. It is also true to say that we don't just apply it to processes that have variable data, as there are other forms of SPC charts available for use (which we will discuss later in this article).

 

Dependant upon which industry you are applying SPC in, there may well be industry standards to be considered, for example supply chain control systems. Therefore, in this article, we will make general recommendations on how you might approach the application of SPC.

Selecting Processes For SPC

SPC should not be applied as a scattergun approach but reserved for processes that are:

  • Critical (as defined by the FMEA process)
  • Producing critical outcomes (as defined by the FMEA process)
  • Known to have reliability issues (out of control conditions)
  • Critical to customer satisfaction (internal or external)

In all cases, it is better to control process parameters rather than the process outcomes. In other words, if the process parameters that make the outcome reliable are known then why risk making reject parts?

For example to produce a 'good' spot weld, the process parameters that can be controlled are:

  • Tip condition
  • Power (Amps)
  • Dwell time
  • Tip to anvil pressure
  • Substrate condition

Get all of these right and the spot weld is guaranteed!

Planning to implement SPC requires the involvement of the team and ensuring that everyone understands their role and are trained in the requirements for this. The plan also needs to reflect why SPC is to be applied to the process in question.

The plan should include:

  • Understanding the process paramters and common cause variation
  • Sample size
  • Sampling frequency
  • Measurement system analysis
  • Data collection and analysis responsibilities
  • Training requirements (where necessary)
  • Timing

When planning to set up SPC on a process, there are a few rules that need to be observed including data source - the data to be collected should be from one source only. In other words avoid collecting data from:

  • More than one process
  • More than one tool
  • More than one mould or cavity
  • More than one measuring station

Calculating Control Limits

Control Limits should not be calcuated, in the first instance, until such time as all of the common causes of variation have been experienced, such as:

  • Changes of shift
  • Normal changes in the environment (internal and external)
  • Change of supply of materials (under normal circumstances)
  • Cutting tool sharpening (after tool wear)
  • Autonomous maintenance
  • Change of operator
  • Change of person taking the measurement

In any event a minimum of twenty sub-sets of data will need to be collected

Once the control limits have been calculated, thay should not be re-calculated until something has changed, that is to say a special cause has taken place, process re-set, tooling changes or other significant event.

We have have experienced, in some organisations, the recalculation of the control limits after every SPC sheet has been completed, this should not be done unless the completion coincides with a significant event, as above.

Other Control Charts

There are two types of data that can come from a process.

1. Variable Data: something that can be measured (length, volume, mass for example), which has been the focus of this series of articles.

2. Attribute Data: something that can be observed, for example presence of components, marks, blemishes, go / no go conditions.

For variable data there are two charts in common use:

X-bar and R Charts (see here for downloadable version of blank and completed)

X and R Charts (individuals and moving range). These are used where small amounts of data are available or sampling frequency is required to be relatively high.

With attribute data the following charts are available for use:

P-Chart - for inconsistent sample sizes and non-conforming uits

N-Chart - for inconsistent sample sizes and non-conformities (faults)

C-Chart - for constant sample sizes and non-confirmities (faults)

Np-Chart - for constant sample sizes and non-confirming units

For more information about how these charts are appplied, or for assistance in your SPC efforts please contact either myself, Graham Cripps on graham.cripps@resultsresults.co.uk or Julie Camp on julie.camp@resultsresults.co.uk

 

Answers to Capability Exercise are here!

 

 

Topics: Continuous Improvement, Statistical Process Control, SPC

Learning To See - Simple Thinking

Posted by Graham Cripps on Fri, Jul 31, 2015 @ 10:09 AM

Learning To See - Simple Thinking

In this article I am going to give a snap shot of the application of simple thinking in a few examples. To gain a better understanding of how this is applied, I will be providing further details in September, via a short 'e-book', of how 'Learning To See' can be applied to Continuous Improvement activities such as problem solving, process management and problem prevention. If this is of interest please take a minute to sign up to the blogs to ensure you are notified of its available.

I have been using this phrase for some time to describe the learned discipline of being able to see things for what they actually are, without cluttering the facts with opinions and assumptions. Its about employing simple thinking.

This approach requires a degree of self-discipline in the first instance. However, it also requires a structured approach to many of the tools and techniques used in the management of business processes and procedures in any business.

There are five methods I use in my approach:

  • Clear factual descriptions of problem, function and purpose statements
  • Defining the boundaries of all activities
  • Use of Visual Management to aid management and control
  • Simple thinking
  • Future State visioning

I will provide an overview of each of these, using simple examples to demonstrate

Clear Factual Descriptions

I commonly use two examples to explain the meaning, the first being problem solving and the second business development

We have a problem to solve, so the first step is to establish exactly what that problem is - this will be a clear statement detailing 'what is wrong with what'. All too often problems are not solved because we end up focusing on and dealing with the effect (the symptom), which masks the problem.

Business development often becomes just an increased sales effort, whether through increased sales activity, product development or looking to new markets, which in isolation often fails. Having a factual description of the business issue is the first step to creating an action plan that takes into consideration four main areas (SWOT) and provides an informed set of actions that can be directly addressed. This list will inevitably include some 'go find out' actions as well.

The SWOT analysis (you can download a free, editable template via the button at the bottom of this blog) is a detailed review of the business considering all of the strengths, weaknesses, opportunities and threats (or risks) that can be clearly articulated, using data and real information - in essence  a clear description of where the business is.

Defining The Boundaries

Defining a boundary for any activity is an efficient way of ensuring time is not spent on things that are not part of the target activity. This may seem simple at first but it is all too easy to wander off in other directions, albeit for seemingly good reasons!

Visual Management

Visual Management is an integrated approach to supporting communication and information sharing, having visual messages may be part of something bigger.

In the 1980's the company I was working for signed up to a quality poster campaign.This involved lots of posters going up on site with a picture of a lion, bearing the legend "The Customer Is King" or a picture of a lovely, shiny, golden key stating "Quality is the KEY to our business" - so what? If the business processes and activities do not reflect these messages then what is the point?

Visual Management is about prompting the right reaction and should be tied into the business objectives and operating procedures and policies.

Simple Thinking

Clear, unclouded, focused, factual thinking. Recently I undertook an observation at a site, involving two guys who were themselves observing a complex activity. Their observation lasted about an hour and, in all fairness, copious notes were taken by both observers on what they saw, heard and experienced. My observation was of both them and the same activity they were observing.

When the observation session was complete we compared notes, I had a lot less written notes but had picked up on a number of issues that they had missed. So what was the difference? Both of the observers had entered the area  expecting to see certain things, which was part of their preparation and plan for the observation event. I had deliberately avoided being told in advance anything about the activity we were to observe.

The two observers were looking for what they expected to see, whilst I saw everything as I carried no expectations for the session. I had no mental clutter, a clear understanding of what I was going to do and was dealing only with what I saw - the facts.

Future State Visioning

Future State Visioning is an important part of goal setting, having a clear visions is the first step to setting business or personal goals (or objectives). When coaching others to develop their goals I always ask if they use any form of visualisation and, as this is often seen as a bit 'fluffy', the answer is usually no. But if I ask the same people what they will be doing for the weekend, I can get them to describe the detail and even some of the emotions attached to that vision.....

Imagination (or creativity) plays a major part in successful goal setting and achievement. It has been said that the brain cannot differentiate between  a real event and a vividly imagined one and we will all have experienced the emotions that imagination can provoke, both positive and negative. In goal setting we use our imagination to see what success would look like, feel like and even smell like!

I coached a Senior Team at a machine manufacturing company and we were looking at articulating their goal (to double turnover in two years). I asked them to consider all their senses in the context of this, what would the business:

Look like - would they be in the same physical space, what would the shop floor look like (more people, more processes, new products etc)

Smell like - new processes generate new smells, new products need new processes etc

Sound like - would the phone be ringing more, who would they be talking to, manufacturing sounds, process sounds, what new technology sounds would they hear

Feel like - kinasthetic feelings that come from new materials, new technologies and new processes.

The more detail we can imagine about our goal (future state) the more real we can make it and the  more detailed your action plan will be.

It is said there is no such thing as luck in business, I disagree! luck is where opportunity and preparedness meet, therefore we need to be prepared to spot those opportunities. The better we can describe (or imagine) our goal, the more prepared we are to spot those opportunities.

Now you might be thinking what about this simple thinking stuff? For me this fits perfectly. Having a clear vision of a goal is the first step towards attaining that very goal.

Download Your SWOT Analysis Template

Graham Cripps

 

 

 

 

Topics: Boundary Diagram, Continuous Improvement, People Development, visual management

Subscribe via E-mail

Latest Posts

Posts by category

Follow Me