The Rest Of The Story…

April 24th, 2009

A few years ago, I did some consulting and training for a manufacturing company. Components of their products were made from metal castings with some precision requirements below a thousandth of an inch. The company had some trouble achieving these tough product targets and I was there to help.

Now put yourself in the management of this operation as you read, and ask yourself, “What would I do?

All of the metal components were machined according to mechanical drawings. (”blueprints”.) After some research into the prints I made an interesting discovery. Many of the prints had a common flaw. (Let me simplify the story here to help you make a mental picture.) Imagine that a hole is to be drilled into a eight inch wide block of metal and the drawing calls for the center of the hole to be exactly four inches from the left edge and five inches from the right. Now, make the mental picture. Do the math! See the problem?

The drawing is ambiguous. There are two possible places that the hole could be formed. Errors of this sort are avoided in drawings by specifying all dimensions from a single common reference. The engineering drawings had many of these errors, and I brought this to the attention of management.

Now, if you were responsible for managing this company, what would you do?

I further researched the machining processes and found a long row of machining work centers . Each work center  made one or more cuts into a rough metal casting and finished parts were produced at the end of the line. This “pipeline” approach had tremendous potential to rapidly turn out quantities of product. Once configured for a certain specific part, this “assembly line” approach to metal machining was extremely productive.

Everyone knew that the first machining work center  was extremely critical. It made the “reference” surface. This is the same principle in the handling of materials as in drafting. The first cut created a smooth flat surface on the cast iron part. Every subsequent act of positioning and measuring that specific part for the rest of its manufacture began with lining up that flat reference surface to a known position mark.

The problem was this: the finished parts came out different. Statistical analysis showed four distinct groups which were traced back to a casting “mark” of ‘a’, “b’, “c”, or “d”. The molds for the iron castings formed four parts at a time. Parts that came from mold ‘a’ were very much like any other “a”, but different from “b”. The difference was small, but enough to produce significant scrap.

I recommended that we add one work center to the start of the machining line. The job was simply to -sort- the castings by mold. Castings marked ‘a’ would be processed and then the cutting machines would be recalibrated before ‘b’ parts would run. We did an experiment. We tested the sorting station theory. Setup time was dramatically reduced because first piece QA checks came back on the money and without delay. Every part now left the first machining work center with a consistent reference surface, and the finished parts came out as “same” (plus or minus) and not as “four flavors”.

Now, after this little experiment succeeded, if it were your facility and your money, what would you do?

Finally, there was a third story to tell  from this plant. it is a story that I have told in some detail elsewhere, but here is the abridged version. A work center was designed as a round turntable. Seven stations with cutting tools were arranged around the table, and the eighth station was a standing position for an operation to attach and remove parts from the table. The operator would unload a finished part, load a fresh part, and then start the cycle. The table would rotate 45 degrees and each of the seven machining stations would go to work on their respective parts.

The machine had a terrible reputation with the operators and no one wanted to be responsible for setting it up for a different kind of part. After some investigation, I found out why. The two stations on either side of the operator and the center of the table were designed to form  a perfect 90 degree angle for reference and measurement. All placement of fixtures on the table and all positioning of the remaining five stations were to be made from this objective and absolute frame of reference.

I discovered that someone had unbolted and moved one of the two reference machining stations in an attempt to set up the machine. The perfect right angle was broken and a 91 or 92 degree angle had taken its place. It was now -impossible- to perform precision machining at this work center. The only solution was to reposition the two critical stations relative to the center of the table, and this required the machine maker’s assistance and precision laser measurement tools.

So once again, if it were your responsibility, what would you do?

Here is the rest of the story.

Regarding the blueprints: the company decided to do nothing. Regarding the new pre-sort work center: The company decided to do nothing. Regarding the machine damaged by an untrained setup operator: the company decided do nothing, and to leave the machine at it was.

The next time your engineers, plant managers, training or quality personnel tell you “we did SPC, measurement studies, process management, all those things…and they didn’t make a difference in our scrap rate.” - take that with a big grain of salt, and get the rest of -their- story.

If you do what you always did, you’ll get what you always got.

Ease of Use

April 24th, 2009

Technology products are often evaluated on their “ease of use” although this concept is universal. The deeper issue, however, is the degree to which a customer finds a company easy or hard to to business with.

I just installed a dsl modem for a friend, and it was extremely frustrating to have what should have been a fifteen minute process turn into more than an hour. The problem is, everything went according to plan. However, the ISP has wrapped the install process inside a “must be using one the following versions of windows” installation program. This software ‘wizard’ not only harvests an excessive amount of personal data, it upsells, explains how to put a modular plug in a jack, changes home pages in browsers, and dumps dubious  “utility” programs to the hard drive.

The company has turned what should be a very simple process into a tedious, pedantic waste of time. Such practices may survey well with novices and poorly with “experts”, but do not misinterpret these results. The novices know of no alternative. If they successfully finish their self-install before they get hungry or before nature calls, they will write this off to the complex nature of technology, and not to poor business practices.

Now, I know how to work around such time wasters. If I had three-in-a-row of these things to set up, I would take a look behind the wizard’s curtain, identify the essentials, and pop these out like cookies. I have done it before, but every time they “improve” the install wizards, you have to go back and check your assumptions to see if an ‘add’ to the script is a new requirement of doing business with the company, or an ‘up-sell’ in disguise. But, why should I have to figure this out?

Now, I don’t want to exhaust your attention with too many “difficult do to business” stories, but here are a few teasers to broaden the scope:

  • Businesses that claim their accounting systems cannot generate an invoice until AFTER you pay. (True story!)
  • Equipment model numbers that make no rational sense, and are designed to obscure true product differences and product obsolescence. (Be honest folks. It’s LAST YEAR’s Model!!)
  • Tedious authentication and security practices that are easily subverted, but are perfunctory hurdles that honest customers must jump just to get the answer to a FAQ.
  • Voluminous contracts for small purchases that hide important considerations in a sea of words that recapitulate the obvious, the usual and the customary.
  • Incessant meaningless customer surveys from companies who have no obvious mechanism to submit complaints and unsolicited feedback. (Tell us how good we are doing.)

…and more.

Setting aside those who would misrepresent under the cover of legal cleverness, there are two obvious drivers that cause “ease of doing business” to trend in the wrong direction.

First, in an effort to cut costs, companies sometimes make life harder for customers. They transfer costs to the customers by requiring them to spend increased time “following company processes” or simply waiting in que for services. Difficulties in doing business are  a hidden cost, and new customers do not take this into account when they judge a product’s price and value.

Transferred costs do not have the “sticker shock” of a price increase, but money is time and hidden costs do not remain hidden. “If I had known then what I know now about comapny xyz…., I would have done without their product.” That’s buyer’s remorse! It gives a competitor who meets and exceeds customer expectations an opening to say, “Do business with us and you won’t be disappointed.”

Second, and more fundamentally, there is a rampant mis-understanding of business “process”. I’ll put the truth as clearly as possible. Business process is what your -company- does, not your customer. If you do it right, your company will look to your customer like a big soft drink machine. “Put your money in. Make your selection. Take the product. Enjoy!” Good process architecture makes this miracle happen and a customer need not know or care what goes on behind the “employee” entrance.

Note that I did not say, that customers -should not know- about business processes, only that they -need- not know. The degree to which business processes should be transparent varies by industry and has legal implications as well as policy and strategy considerations.

SPC Caveat

December 30th, 2008

I can’t tell you the number of times that I have taken the ‘executive’ facility tour only to see something surprising offered as their “statistical process control”!

It’s a control chart, demanding attention, loudly proclaiming that the process is ‘out of control’. However, the machinery still turns and product continues to be packaged and shipped.

Many of these operations have an abundance of quality certification banners. They have subscribed to the latest fashions in quality (e.g. Six Sigma, Total Quality, etc.). They have hired quality and engineering professionals so are “supposed to handle quality”.

So, how can this be? How can an organization that values quality continue ‘business as usual’ in the face of an urgent alert like this?

Discounted Information

In situations like these, the message conveyed by the control chart has been almost totally discounted. Its perceived relevance to decision-making is almost nil.

There was once a time when the TV weather report received the same scornful treatment. The report would reccomend umbrellas and the sun would shine. People would smile and say, “I told you you can’t trust the weatherman!”

And, we all have noticed those new car indicators that suddenly urge you to take out your wallet and drive quickly to the nearest dealer/service center. “Check Engine”, the message says, and from the vague discussion in the owners manual - a folklore has sprung up. “It’s a computer malfunction”, people say. “It’s on a timer. Its connected to the odometer”, others theorize. Ultimately, the information is discounted, and many people ignore the check engine warning.

Now, think about the ignored control chart. Like an unreliable weather report or a mystery “idiot light”, people have persuaded themselves that the information in the chart has no relevance to hour by hour workplace decisions.

There are three things which would cause SPC charts to be discounted and ignored.

1 - Operations Not Properly Trained in SPC Based Decision-Making

Why wouldn’t anyone in a room full of people answer a ringing phone? Perhaps everyone assumes the call is for someone else!

Control charts facilitate decision-making, but whose decisions? (Operations!) Too often, operations personnel assume the chart is “for the quality folks” , or for engineering or maintenance.

The first cause of control chart apathy is simply that operations personnel have been trained from a quality or engineering perspective, and have never been shown how they are used to make operations decisions.

2- Operations Leadership Encourages Process “Short-Cuts”

There are many operations managers and supervisors who do not place emphasis on doing a job right. “Right” to them is “whatever gets the alligator off your back”. SPC may be warning, but the folks who approve paychecks pay operators to ignore it.

3-SPC Really is Broken!

If you have a car with capricious warning indicators, you learn quickly to not take them seriously. If the various warnings appeared and disappeared for no apparent reason, and careful observation of the car showed no problem, then the dashboard feedback is now dismissed as “broken”. SPC control charts can be “broken”. There may be a minor or major technical flaw in the way data is gathered and presented, and this is the third cause of chart apathy.

Could Things Be Any Worse?

The only thing worse, than chart apathy, is chart apathy with a veneer of correctness. A common mistake in response to these problems is a management directive to “make SPC look right”. Charts like the one above are “tweaked” to look like the perfect case of “in control”- a mathematical version of telling the boss what he wants to hear.

How to Fix This…

Operations, quality and engineering have different uses for SPC data. Start with operations. The SPC-based decisions that engineers and quality personnel make depend on and assume a correct implementation of Operations SPC.

To fix control chart apathy,

1) Your managers and supervisors must reward work done correctly. 2) .Operations personnel must learn how to “answer the phone” when a control chart tells them their processes have changed. They need to understand what the chart is telling them about their work. 3) Control charts must be implemented in such a way that out-of-control indicators really are relevant to operations decisions.