ASQ Automotive Division Symposium

The ASQ Automotive Division is hosting a symposium on April 4, 2011. If your live around Detroit you may be interested. I went to the event last year and had an enjoyable and informative day.

Here is the speaker list:
Dan Nicholson, Vice President Global Quality, General Motors
Keynote Presentation

Mike VanNieuwkuyk, Executive Director Global Vehicle Research, J.D. Power and Associates
Consumer Aligned Product Development in a Quality Equality Market

JD Marhevko, Lean and Quality Independent Consultant and Chair, ASQ Quality Mgmt. Division
Sample Size of One: Quality & Lean Tools with a Kid on the Autism Spectrum

Vince Mastrangelo, Vice President Quality, Continental Automotive
Assuring the Quality of Innovation, Continental Automotive Group: Delivering Invention to our Customers

Bill Hampton, Publisher, AutoBeat Group
Where is our Industry Headed?

Jane Hoying, Consulting Manager, Shainin, LLC
TransaXional Problem Solving – A New Paradigm


Here is other information:
Date: Monday, April 4, 2011
Time: 7:30 am – 8:30 am: Registration & Breakfast
8:30 am – 5:00 pm: Symposium & Networking

Location: Macomb Community College (Center Campus)
University Center UC 1 - Assembly Hall
44575 Garfield Rd, Clinton Township, MI 48038-1139
Cost: Before Mar 25, 2011 - $30 for ASQ Automotive Division Member; $45 all others. After Mar 25, 2011: $65 for All
Food: Continental Breakfast, Lunch and Snacks included
RU’s: 1.0 RU (Recertification Unit) for ASQ Recertification
Register: www.Regonline.com/ASQAuto2011

Contact: Jennifer Schneider, Symposium Chair, Phone: (248) 705-3216
E-Mail: Jennifer.Schneider@continental-corporation.com

New Product Development - Additional Protection From Unknowns

I thought I would lay out some of the things that I think are needed to have a chance for a clean launch of a new product.
I have started to discuss PFD and PFMEA and there is more to come on that. In addition to those two essentials, there are some other tools that can reduce the risk of an unknown problem from slipping through to the customer.
Remembering that the PFD defines the intended process and the PFMEA picks apart things that might go wrong, and why, we have the fact that humans are fallible and mistakes and omissions will be made. We will not be able to 100% determine all of the prevention and detection controls in advance. How do we protect ourselves from these "unknown"risks?

Here is a list.

High Tech Production Still Too Costly in US

An interesting article from the Metrowest Daily News about a tech start up company. Evergreen Solar had an innovative way to produce solar panels. The cost per watt was still higher than the market would bear, but with incentives and subsidies in 2008 they could make it:

Back then, photovoltaic panels - or "modules" - sold for an average of $4 per watt. Still spending $4.35 per watt to make the panels, Evergreen knew mass production was the key to lowering costs. The race was on: Make more. Sell more.

The production strategy worked. Production costs dropped to $2 per panel by the end of 2009. Shipments rose 84 percent to 104 megawatts. By then, the company was supposed to be turning healthy profits, spokesman Chris Lawson says.

But then, competition from China.

As Chinese photovoltaic companies moved into the market, panel sale prices have plummeted to record lows in two short years.
Chinese companies manufacture panels for $1.20 per watt and sell them for $1.60 to $1.70. Evergreen spends $1.90 per watt to make the panels.

Is the difference between the cost in China and the cost in the US due only to labor costs? In a high tech production system, how much of the cost per watt is due to labor?

Read more: The eclipse of Evergreen Solar - Framingham, MA - The MetroWest Daily News http://www.metrowestdailynews.com/archive/x945640045/The-eclipse-of-Evergreen-Solar#ixzz1FsRQlnjO

Process Flow Diagram

While discussing the PFMEA we are inevitably drawn to the topic of the process flow diagram. Where I work we and our suppliers are supposed to have a process flow diagram. The requirement is somewhat vague, I guess. And when I say "have a PFD..." I mean, we should have and UTILIZE an effective PFD. The PFD shown below would fit the letter of the law. In the illustrated case the manufacturer is just describing, for sales purposes, the process steps that their piezo actuator goes through. The instructions from the AIAG APQP Manual state:

The process flow chart is a schematic representation of the current or proposed process flow. It can be used to analyze sources of variations of machines, materials, methods, and manpower from the beginning to end of a manufacturing or assembly process. It is used to emphasize the impact of sources of variation on the process. The flow chart helps to analyze the totalprocess rather than individual steps in the process. The flow chart assists
the organization’s product quality planning team to focus on the process when conducting the PFMEA and designing the Control Plan.

There is a process flow chart checklist in the appendix. The checklist is focused on including steps in the process, but not process description

However, when a NPD team is working to develop a manufacturing process they need to define the process in detail, including inputs and outputs. A complete PFD is essential for the PFMEA discussion.


This PFD is shown at noliac.com

The Fight is Against Single Piece Errors

The series of posts I have recently begun on PFMEAs are rooted in my frustration at single piece defects getting to the customer factories. By this, I mean "one body missing a machined hole" or "one assembly missing a retaining pin".

Part of the manufacturing/quality struggle is to produce all parts within print specification. This struggle is addressed by dimensional controls and SPC. The PFMEA usually, almost exclusively, addresses dimensional issues. But the problema that I see passing through to customers are not that "our process shifted 10 microns over size", it is that that one machining operation was missed on one piece.

In the attached video the PFMEA is mentioned. I liked this video. The PFMEA comment was accurate.
"PFMEAs, although a great tool, are only as good as the knowledge put into them."



The video author admits that often failure modes and causes are missed in the PFMEA. What is the countermeasure to this failure mode in the NPD (new product development) process?


Thanks to TheUjigamiGuy on YouTube

PFMEA Training in China

Note: The video link is not always working, even directly to the site.

Here is a little video of a PFMEA training session in China. The banner reads,

"Failure Mode and Consequences Analysis"

The company is Konka Television, apparently pretty famous in China. When I work in China I see training like this quite often. It strikes me that I do not see this kind of thing in the US. Is it because it is assumed everyone in the US knows how to do a PFMEA? Don't get me wrong, I am not saying that this kind of training will be extremely effective. I am saying that the focus on "attempting" to improve the process is refreshing.

Where is the effective use of a PFMEA? Anywhere.

I am getting far enough in my career so that I dread starting work with a new product development team and the inevitable disappointment I will feel when I see how ineffective they are. The team is responsible for launching the new product without any glitches, defects or flaws. This is a tall order, right? Not easy. Yet these teams sleepwalk through advanced quality planning and walk into launch with their pants down.

Let's look at the use of PFMEAs. Can anyone reading this blog tell me of a time they worked in a cross=functional team that actually worked to develop the PFMEA as an honest attempt to list out potential failure modes and causes?

What I find is:
A) The PFMEA is a stale document handed down from project to project. Always, it never was that good in the first place and, even for new aspects of the new product there is no attempt to freshen it up.
B) The PFMEA was written by one person, not a team.
C) The PFMEA was written for the sole reason of checking the box: Is there a PFMEA? Yes or No
D) When confronted with the fact that the PFMEA is a stinker the author, or the project manager 1) denies it, and 2) challenges me to produce good examples (in other words, do it for them)
E) When obvious failure modes are brought to their attention the response is, "oh, that cannot happen because..." Without the PFMEA exercise holes in the prevention and detection process are not effectively reviewed.
F)Several times the new product development team will start to use some kind of PFMEA software to show they are now serious about doing a PFMEA. However, the software is difficult to use and somehow seems to distract from the goal.

Time and time again we see defects arriving at customer plants that are well known failure modes that should be expected if there are inadequate controls. Yet, they happen. Again and again.

The next article will be focused on some of the best practices I have seen.