Slide title minimum 48 pt Slide subtitle minimum 30 pt ERICSSON MEETS SMID Improve April, 2011

  • View
    213

  • Download
    0

Embed Size (px)

Transcript

  • Slide 1
  • Slide title minimum 48 pt Slide subtitle minimum 30 pt ERICSSON MEETS SMID Improve April, 2011
  • Slide 2
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 2 (40) Agenda 4 th April Ericsson presentation Statistical tools in manufacturing DMAIC/IDDOV 7 th April Define Measure 11 th April Analyze 14 th April Implement Control
  • Slide 3
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 3 (40) DMAIC Chart Comprehensive Light D efine Understand the task and its financial impact. Task selection matrix SMART review Stakeholder map Risk Management SWOT analysis Process map VOC and break down to CTQs 7MT Affinity diagram M easure Develop and execute an appropriate data collection method. Process map Data collection table Pareto diagram 7QCT Measurement system analysis Sampling technique SIPOC Gauge R&R, Gauge attribute Capability analysis Benchmark Tagushi loss functions A nalyze Find the root causes. Fishbone diagram Correlation analysis 7QCT Hypothesis testing Regression- analysis DOE Anova 7MT Data transformations Simulations I mprove Generate and implement solutions. FMEA risk analysis Process map Poka-Yoke Hypothesis testing Loss functions Cost/Benefit selection Pugh Concept Selection C ontrol Ensure that the results will last. Documentation, standardization and training 7QCT SPC Business case verification
  • Slide 4
  • Slide title minimum 48 pt Slide subtitle minimum 30 pt FMEA FAILURE MODE AND EFFECTS ANALYSIS
  • Slide 5
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 5 (40) FMEA Focus on observable behaviors
  • Slide 6
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 6 (40) FMEA Why? If it can go wrong - it will go wrong! Prevention is better than cure Where? Can be applied to any process Who? A team of people connected with the process "A large safety factor does not necessarily translate into a reliable product. Instead, it often leads to an overdesigned product with reliability problems. Failure Analysis Beats Murphy's Law Mechanical Engineering, September 1993
  • Slide 7
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 7 (40) FMEA worksheet
  • Slide 8
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 8 (40) FMEA severity (SEV) rating For each failure mode, decide on the impact on the product or operation when it occurs. Rate this impact in the column labeled SEV (severity). Establish your baseline for the analysis, i.e. SEV=10 means death of a human or machine failure. A SEV rating cannot change when improvement actions are put in place unless the design has changed. Potential Failure ModePotential Failure Effects S E V Reciever & Output data loss, track loss 3 Output loss from pre-amp Effect of failure mode Potential Failure modes Loss of signal from 2 nd RF amp Loss of position, velocity & time. 5 Severity Rating for the Failure Effect.
  • Slide 9
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 9 (40) FMEA occurrence (OCC) rating For each potential failure mode come up with one or more potential causes. Rate the probability of each potential cause occurring and place the rating in the column labeled OCC (occurrence). Potential Failure Effects S E V Potential Causes O C C C1 short 1 U21 function 10 Severity Rating for the Failure Effect. Effect of the failure mode Receiver & Output data loss, track loss Loss of position, velocity & time 3 5 Potential cause of failure mode Probability of Occurrence
  • Slide 10
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 10 (40) FMEA detection (DET) rating For each potential cause, identify the current controls which are in place to prevent or detect the failure mode. Rate the ability of each current control to prevent or detect the failure mode once it occurs. Place the rating in the column labeled DET (detection). Potential Causes O C C Current Controls D E T R P N C1 short 2 Test PR-20 & HW-5 232 U21 function 6 None 6288 Current Controls for each failure mode. Ability to prevent or detect the failure mode.
  • Slide 11 action plan Multiply the SEV, OCC and DET ratings together and place the value in the RPN column. The largest RPN numbers should get the greatest focus. Any SEV which has a value 10 should have attention regardless of the OCC and DET values. For those RPN numbers which warrant corrective action, recommended actions and the person responsible for implementation should be listed. SEV * OCC * DET = RPN (3 *1*6 = 18) SEV * OCC * DET = RPN (3 *1*6 = 18) Potential Failure Effects S E V Potential Causes O C C Current Controls D E T R P N Actions Recommended Resp. Operator skill/training Motor frame is unstable 3 1 6 18 Recommended actions and person responsible for implementation. Operator Knowledge experience Ticket specifies - but coded Coding chart to be issued & displayed by machine Darren Wooler Risk Priority Number (RPN)">
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 11 (40) RPN calculation => action plan Multiply the SEV, OCC and DET ratings together and place the value in the RPN column. The largest RPN numbers should get the greatest focus. Any SEV which has a value 10 should have attention regardless of the OCC and DET values. For those RPN numbers which warrant corrective action, recommended actions and the person responsible for implementation should be listed. SEV * OCC * DET = RPN (3 *1*6 = 18) SEV * OCC * DET = RPN (3 *1*6 = 18) Potential Failure Effects S E V Potential Causes O C C Current Controls D E T R P N Actions Recommended Resp. Operator skill/training Motor frame is unstable 3 1 6 18 Recommended actions and person responsible for implementation. Operator Knowledge experience Ticket specifies - but coded Coding chart to be issued & displayed by machine Darren Wooler Risk Priority Number (RPN)
  • Slide 12
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer area Ericsson @ SMID - Improve | Commercial in confidence | Ericsson AB 2011 | 2011-04-04 | Page 12 (40) Impact of corrective actions When making corrective actions use the available data to secure the best corrective action at the time. Correct SEV most probably needs a design change. Correct OCC may need a design and process change. Correct DET may need a design or process change.
  • Slide 13
  • Slide title minimum 32 pt (32 pt makes 2 rows Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRST UVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z{|}~ Do not add objects or text in the footer

Recommended

View more >