To effectively analyze issue root causes, it is crucial that evidence is properly collected, coded, filtered and analyzed. This presentation will outline proper data gathering and organizing techniques. It will examine various analysis methods, comparing their relative strengths and weaknesses. Lastly, it will introduce Root Cause Pattern Diagrams, a breakthrough analysis technique that displays data in colored graphical patterns that are compared against a library of known root cause patterns.
The Seven Basic Tools of Quality (also known as 7 QC Tools) originated in Japan when the country was undergoing major quality revolution and had become a mandatory topic as part of Japanese’s industrial training program. These tools which comprised of simple graphical and statistical techniques were helpful in solving critical quality related issues. These tools were often referred as Seven Basics Tools of Quality because these tools could be implemented by any person with very basic training in statistics and were simple to apply to solve quality-related complex issues.
Quality Maintenance is an "advanced" pillar of TPM and aims to assure zero defect conditions. Also known as Hinshitsu Hozen in Japanese, it does this by understanding and controlling the process interactions between the 4Ms - manpower, material, machines and methods that could enable defects to occur. The key is to prevent defects from being produced in the first place, rather than screening them out through inspection systems after they have been produced. Controlling quality through its causes is the essence of Quality Maintenance.
Developed by our JIPM-certified TPM Instructor, this presentation teaches the key concepts, principles and philosophy of Quality Maintenance, the 4M conditions that are essential for defect-free production, as well as the step-by-step process for Quality Maintenance.
LEARNING OBJECTIVES
1. Understand the key concepts, principles and philosophy of Quality Maintenance
2. Acquire knowledge on the 4M conditions and the prerequisites for promoting Quality Maintenance
3. Describe the 8-step process of Quality Maintenance and the key analytical tools and techniques
CONTENTS
1. Key Concepts & Philosophy of Quality Maintenance
2. 4M Conditions - The Determinants of Quality
3. The 8 Steps of Quality Maintenance
4. Key Tools & Techniques for Quality Maintenance
5. Towards Excellence in Quality Maintenance
To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations
The Seven Basic Tools of Quality (also known as 7 QC Tools) originated in Japan when the country was undergoing major quality revolution and had become a mandatory topic as part of Japanese’s industrial training program. These tools which comprised of simple graphical and statistical techniques were helpful in solving critical quality related issues. These tools were often referred as Seven Basics Tools of Quality because these tools could be implemented by any person with very basic training in statistics and were simple to apply to solve quality-related complex issues.
Quality Maintenance is an "advanced" pillar of TPM and aims to assure zero defect conditions. Also known as Hinshitsu Hozen in Japanese, it does this by understanding and controlling the process interactions between the 4Ms - manpower, material, machines and methods that could enable defects to occur. The key is to prevent defects from being produced in the first place, rather than screening them out through inspection systems after they have been produced. Controlling quality through its causes is the essence of Quality Maintenance.
Developed by our JIPM-certified TPM Instructor, this presentation teaches the key concepts, principles and philosophy of Quality Maintenance, the 4M conditions that are essential for defect-free production, as well as the step-by-step process for Quality Maintenance.
LEARNING OBJECTIVES
1. Understand the key concepts, principles and philosophy of Quality Maintenance
2. Acquire knowledge on the 4M conditions and the prerequisites for promoting Quality Maintenance
3. Describe the 8-step process of Quality Maintenance and the key analytical tools and techniques
CONTENTS
1. Key Concepts & Philosophy of Quality Maintenance
2. 4M Conditions - The Determinants of Quality
3. The 8 Steps of Quality Maintenance
4. Key Tools & Techniques for Quality Maintenance
5. Towards Excellence in Quality Maintenance
To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations
More https://quality.eqms.co.uk/blog/introduction-to-apqp
New to the advanced product quality planning framework?
Don't despair. In this article, Mike Bendall, Business Mentor at Qualsys, explains APQP, provides a checklist for each APQP phase, and there is a link to download his APQP training course for beginners.
More https://quality.eqms.co.uk/blog/introduction-to-apqp
New to the advanced product quality planning framework?
Don't despair. In this article, Mike Bendall, Business Mentor at Qualsys, explains APQP, provides a checklist for each APQP phase, and there is a link to download his APQP training course for beginners.
Operating a delivery model of 90:10 (90% - offshore and 10% onsite) or 80:10 implementing the agile practices could be very challenging. The aim of this presentation would be to bring out challenges faced by offshore agile teams. The presentation will be complemented with couple of case studies.
WQD2011 - KAIZEN - EMAL - To eliminate the chances of breaking of PC charging...Dubai Quality Group
Kaizen case study submitted by Emirates Aluminium during 3rd Continual Improvement & Innovation Symposium organized by Dubai Quality Group's Continual Improvement Subgroup to celebrate World Quality Day 2011.
Avatars of Test Driven Development (TDD)Naresh Jain
It's easy to speak of test-driven development as if it were a single method, but there are several ways to approach it. In my experience, different approaches lead to quite different solutions.
In this hands-on workshop, with the help of some concrete examples, I'll demonstrate the different styles and more importantly what goes into the moment of decision when a test is written? And why TDDers make certain choices. The objective of the session is not to decide which approach is best, rather to highlight various different approaches/styles of practicing test-driven development.
By the end of this session, you will understand how TTDers break down a problem before trying to solve it. Also you'll be exposed to various strategies or techniques used by TDDers to help them write the first few tests.
This Webinar will focus on installation and maintenance guidelines and offer valuable tips on inspecting a wide variety of pipe supports and expansion joints in your piping system. We will cover various pipe support applications and point out signs that indicate if a particular support needs replaced or adjusted. Obtain the knowledge you need to avoid the possibility of a potentially catastrophic situation. View examples of real world problems and see how we were able to solve them with timely and cost effective solutions.
On Duty Cycle Concept in Reliability - Definitions, Pitfalls, and Clarifications
By Frank Sun, Ph.D.
Product Reliability Engineering
HGST, a Western Digital company
For ASQ Reliability Division Webinar
August 14, 2014
Objectives
To provide an introduction to the statistical analysis of
failure time data
To discuss the impact of data censoring on data analysis
To demonstrate software tools for reliability data analysis
Organization
Reliability definition
Characteristics of reliability data
Statistical analysis of censored reliability data
Objectives
To understand Weibull distribution
To be able to use Weibull plot for failure time analysis and
diagnosis
To be able to use software to do data analysis
Organization
Distribution model
Parameter estimation
Regression analysis
With the increase in global competition, more and more costumers consider reliability as one of their primary deciding factors, when purchasing new products. Several companies have invested in developing their own Design for Reliability (DFR) processes and roadmaps in order to be able to meet those requirements and compete in today’s market. This presentation will describe the DFR roadmap and how to effectively use it to ensure the success of the reliability program by focusing on the following DFR elements.
Improved QFN Reliability Process by John Ganjei. John will talk about the improvements in the reliability process in this webinar.
It is free to attend - see www.reliabilitycalendar.org/webinars/ to register for upcoming events.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
2. ASQ Reliability Division
ASQ Reliability Division
English Webinar Series
English Webinar Series
One of the monthly webinars
One of the monthly webinars
on topics of interest to
reliability engineers.
To view recorded webinar (available to ASQ Reliability
Division members only) visit asq.org/reliability
) /
To sign up for the free and available to anyone live
webinars visit reliabilitycalendar.org and select English
Webinars to find links to register for upcoming events
http://reliabilitycalendar.org/The_Re
liability_Calendar/Webinars_
liability Calendar/Webinars ‐
_English/Webinars_‐_English.html
3. LCG
Lloyd Consulting Group, Inc.
Lloyd Consulting Group Inc
Product & Transactional Excellence
Six Sigma, Lean, & Shainin Tools
Course Design and Deployment
Background:
Director Design Excellence
Johnson & Johnson
Field Failure Analysis
Director Six Sigma / MBB
Ocwen Financial
Director 5‐NINES Performance
Di t 5 NINES P f
Using Root Cause
Pattern Diagrams
Motorola PCS
Director Product Reliability
Motorola PPG
Led team that broke Japanese
trade barrier in electronics to
become #1 seller pagers in Japan
Six Sigma Instructor / Mentor
& Shainin Tools Instructor at
Motorola (1987 deployment)
Certifications:
Certified Mgr Quality / Org Excel
Certified Six Sigma Black Belt
Certified Lean Sensei
Licensed US Patent Agent
Robert D. Lloyd
President, Lloyd Consulting Group, Inc.
Recipient:
Motorola CEO Quality Award
Motorola CEO 10X Award
SFMA Achievement Award
CES Innovation Award
14 Issued US Patents
Inductee:
Motorola Science Advisory Board
4. Product Handling
Do not lose evidence by improper handling of
defective product returns
How products are handled
Do Not • ESD protective procedures
Induce Other • Protective trays
Issues
How products are shipped
• Static protective bags
Preserve • Boxing or egg-crating
Evidence
How products are stored
• Organized for retrieval
• Protected from harm
5. Product Analysis
Do not lose evidence by service centers “shot-gunning”
problems by repairing products “at-will”
Would you want your car serviced that way?
• New products should have first 200
Do Not returns sent directly back to Product
Induce Other Engineering for a detailed analysis
Issues
• Service centers should have a INTERNAL OPERATING PROCEDURE
FOR ADDRESSING FIELD RETURNS
structured process for the handling,
p g, 1.0 HANDLING OF RETURNED GOODS
2.0 ANALYSIS OF RETURNED GOODS
Preserve analysis, storage of returned goods 3.0 DOCUMENTATION OF ANALYSIS
4.0 ARCHIVING OF RETURNED GOODS
Evidence
• A id service center fi
Avoid i t financial
i l
incentives that might inadvertently $ per Repair
promote unnecessary repairs
6. Product Analysis
Investigation & repairs should follow fault tree maps
• Call Center “Over-the-Phone” Analysis
• Analysis Lab Progressive Investigation
To Avoid
Unnecessary Complaint: Loss of Prime
Can
C the complaint be
Returns No Works Yes
enter
after rebooting
device? investigated & resolved
& Yes Covered by
No over the phone?
Call Ce
g
Troubleshooting
(A-F)?
To Avoid No Covered by
Resolved Yes
Troubleshooting
“Shot-gun” (G-J)?
Record Cartridge
Repairs Return Device
& Cartridge Lot # & Monitor
Utilize Fault
ab
Return all pertinent items
lysis La
Tree Maps Cartridge Issue Device Issue
and conduct progressive
Profile Examine Test Examine Examine non-destructive analysis
Break
“Break” Cartridge Force Force PCB
Anal
& “Flow”
Forces
for Defects Sensor Sensor
Flex
Sockets before making repairs
b f ki i
7. Complaint & Failure Coding
Fail re
For consistent reporting, standardized coding schemes must be implemented
Inconsistent /Insufficient Failure Statements
(when no codes exist and technicians write their own observations)
Codes Must “Broken display”
p
Be Specific
and “Fractured LCD”
“F d
Consistent “Display cracked”
“Blackened LCD”
Best to
Establish
E t bli h How do you search a data base
Codes As when terms are inconsistent?
Early As Which statements refer to
Possible which of these failures?
8. Complaint & Failure Coding
Fail re
For consistent reporting, standardized coding schemes should be implemented
Need for Detailed Failure Coding
Display Edge Fracture DEF
Codes Must
p
Be Specific
and Display Shelf Fracture DSF
Consistent
Display Center Fracture DCF
Best to
Establish
E t bli h Display Black Spotting
Di l Bl k S i DBS
Codes As
Early As •S t
Set-up a robust library of codes i advance b
b t lib f d in d based on
d
Possible past complaint/failure history and FMEA’s
• Adding codes later disrupts historical data tracking
9. Complaint & Failure Coding
Fail re
Complaint “Product does not turn on”
• Report of an issue from a Customer’s
Effectively perspective (symptomatic view)
Document:
Doc ment
Failure “Reason why product does not turn on”
Customer s
Customer’s
Issue • Report of an issue from an Analysis
Lab’s perspective (causation view)
and
d
Reason Why If an issue was due to customer not knowing how to
It Occurred
O d operate the product, it is still indicative of a f il
t th d t i till i di ti f failure of
f
the instruction manual or of the product’s ergonomic
design. Do not write off such issues as “User Errors”.
g
10. Complaint & Failure Coding
Fail re
Separate Complaint and Failure coding schemes are recommended
Standardized Coding Requirements
Effectively • For consistency in reporting, standardized
Document:
Doc ment
cod g schemes should
coding sc e es s ou d be implemented
p e e ted
• Separate Complaint and Failure coding
Customer s
Customer’s schemes are recommended
h d d
Issue
– Multiple complaints may be associated
p p y
and
d with the same failure mechanism
Reason Why
– Advisable to use:
It Occurred
O d
• Numeric for complaints
• Alpha for failures
p
12. Determining Time In Field
Date of Manufacture versus Time in Service
Product Tracking
• Serial Number • Manufacture Date Code
Product • Model Number • Lot Number
Tracking
Strategies Product History After Manufacture
y
Manuf Active Failure
Date Date Date
Product ID, • Manufacturer’s stock room
Time In Field
Ti I Fi ld Storage
S Active Life
f
and User • Distributor's stock room
Warranty
Date
Demographic • On store shelves
Lean activities work to reduce all inventories
13. Determining Time In Field
Date of Manufacture versus Time in Service
Manuf Active Failure
Date Date Date
SKU
Storage Active Life
Product Warranty
Date
D t
Tracking
Strategies When was product placed into active use?
• Indirect sale to end user (database of S/N & sale date)
Product ID,
Time In Field
Ti I Fi ld • Service provider activation date
and User • Direct sale to end user
Demographic Can also obtain
• Registration (“Bingo”) cards important user
– Historically low response rates demographics
– Need incentives to increase returns
14. Virgin vs Repaired Units
s
Virgin Units
• Representative of the designs, materials,
p
process settings, and operators at the time
g p
of manufacture
The
Challenges
Of Trying Repaired Units
To Obtain • A mixture of designs, materials, operators,
Clean Data process settings from date of manufacture
and from various dates of repair
• Effects of being repaired (heat, stress, etc)
15. Virgin vs Repaired Units
s
Virgin Product Segregation
• Best to analyze virgin units and repaired
units separately
• To identify virgin units: subtract Initial Ship
Strategies Month from Last Ship Month for each S/N
p
To Obtain Last Month Shipped Apr 2007
Clean Data Initial Manuf Ship Month Aug 2006
Manufacturing Ship Delta 8 months
Virgin Products Have Mfg Ship Delta = 0
(because it was never returned to ship again)
16. List of Data Filters
• Month of Manufacture
• Month of Complaint
• Time in Field
Importance of • Warranty Date
Filtering the • Activation Date
Data • Virgin vs Repaired vs Reconditioned
• Product Model
• P d t Revision
Product R i i
Cleaner, • Geographic Region (Country, State)
Relevant • Complaint Codes
Data More
• Failure Codes
Important
• User Demographics
Than Sample
Size
• Gender
• Age
• Location (State/Pro ince)
(State/Province)
17. Month of Complaint
Hinge Complaints by Month of Complaint
30%
(Product Introduced in Fall 2006)
o)
Complaint Rat (%/mo
25%
te 20%
Looks at All 15%
Complaints
for a Given 10%
Month 5%
g
Regardless
of When It 0%
Apr-07
May-07
Aug-07
Apr-08
May-08
Aug-08
Nov-06
Nov-07
Dec-06
Jan-07
Feb-07
Jun-07
Jul-07
Sep-07
Dec-07
Jan-08
Feb-08
Jun-08
Jul-08
Sep-08
Oct-06
Mar-07
Oct-07
Mar-08
Was Made
MONTH OF COMPLAINTS
# of Complaints for Specific Month
Complaint Rate =
Install B
I t ll Base for Specific Month
f S ifi M th
18. Pareto Diagrams
June 2008 Failure Code Pareto - Product A
Although It
g
Identifies the
Important
Few,
It is only a
“Snap-Shot”
In Time
But what have been the trends
over th prior months?
the i th ?
19. Pareto Timelines
A Better Perspective on the Larger Picture
Pareto Timeline of Top 6 Failure Codes for Product A
(Specific failures reported for each month divided by respective month install base)
A
Pareto B
Rankings
R ki
Change D
Over Time
C
Seasonality,
Data
Designs, from
Prior
Materials, Page
Processes
A - Hinge failures are steadily rising at a rapid rate
B - Water intrusion failures are seasonally cyclical
C-C Crystal f il
t l failures have been steadily decreasing
h b t dil d i
D - Keypad failures falling, but check for seasonality
20. Weaknesses Regarding
Month of Complaint (MoC)
# of Complaints Received in Specific Month
MoC Complaint Rate =
Install Base for That Specific Month
Month of Complaints Received June 2006
Complaint Different dates of manufacture
Reflects A • Different design revisions Mfr’d Mfr’d
Mixture of • Different materials Mfr’d
Sep ‘05
Mfr’d
Aug ‘04
Mfr’d
Apr ‘04 Oct ‘04 May ‘05
Products • Different process settings Mfr d
Mfr’d
Jan ‘05
Mfr d
Mfr’d
Nov ‘04
• Different operators Install Base June 2006
Mainly “The Chowder
The Chowder”
Reflects
External MoC mainly reflects the impact of external
Factors
environmental f t
i t l factors. It does not clearly
d t l l
represent internal design/process impact.
Might not even reflect current production.
21. An Improper Application
of Month of Manufacture
Man fact re
Hinge Failures by Month of Manufacture
12%
10%
Month of
Failu Rate (% / mo) 8%
Manufacture
ARTIFICIAL IMPROVEMENT CURVE
Alone Is 6%
DUE TO RECENT MONTHS HAVING
Misleading
ure
LESS TIME IN THE FIELD
4%
2%
Must Also
Factor In 0%
Aug-07
Aug-08
Apr-07
Jan-07
Jul-07
Jul-08
Nov-06
Apr-08
Dec-06
May-07
Sep-07
Nov-07
Dec-07
May-08
Sep-08
Feb-07
Jun-07
Oct-07
Jun-08
Mar-07
Jan-08
Feb-08
Mar-08
Oct-06
Time in
A
A
Month of Manufacture
the Field
# of Complaints for Specific Month of Manuf
p p
MoM Complaint R t =
M MC l i t Rate
Install Base for Specific Month of Manuf
22. Month of Manufacture
Man fact re
Cumulative Field Failure Rate
4.5%
4.0% May-07
y
Jun-07
3.5% Jul-07
Aug-07
TURE
Cumulative mo)
3.0%
LIKELY MATERIAL OR PROCESS ISSUES IN
JUN-AUG 2007 CAUSING RISE IN FAILURES
Sep-07
Oct 07
Oct-07
MONTH OF MANUFACT
FAILURE RATE (%/m
Failure R t
F il Rates Nov-07
2.5% Dec-07
Tracked By Jan-08
2.0% Feb-08
Time-in-Field
F
Mar-08
Mar 08
Apr-08
for Multiple 1.5%
May-08
Jun-08
Months of 1.0% Jul-08
Aug-08
Manufacture 0.5% Sep-08
for Specific 0.0%
Product
Prod ct 1 2 3 4 5 6 7 8 9 10
TIME IN FIELD
11 12 13 14 15 16 17 18 19
Those months that deviate garner attention, but
this is not the most effective way to communicate.
ff
23. Preparing MoM Chart
Time to Failure
(months)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
May-07
Jun-07
ses
Jul-07
re
Aug-07
g
stall Bas
Month of Manufactur
Sep-07
Oct-07
Nov-07
Dec-07
Jan-08
Feb-08
MoM Initial Ins Mar-08
Mar 08
Apr-08
May-08
Data Table Jun-08
Jul-08
Aug-08
Used for p
Sep-08
Oct-08
Nov-08
Creating Dec-08
Jan-09
Feb-09
Chart on Mar-09
Apr-09
Apr 09
Prior Slide
Cumulative Failure Rates:
Failures (for specific MoM and Time-in-Field)
Install Base (specific MoM minus all prior failures)
Rates for each MoM are plotted as shown on prior page