Your ‘Common Cause Floor’ will Help Define a Reasonable DPMO Target

Let’s look in on Patty; it has been a very long time …

Patty left her house in Woodstock VT very early on her way to Ivy University. She chuckled at the darkness of the early morning; it reminded her of a book she was reading.  In the book, Gray Girl, Jan Wishart is a young woman in her first year at West Point. The cadets use military time, so, for example, 9:00AM is referred to as 0900 hrs. When it is so early that it is still very dark, the cadets simply call it, “0 dark thirty.”

She had to admit that, even though she occasionally had to leave at “0 dark thirty,” she loved being a professor at Ivy University. She had just finished teaching a statistics class and had submitted the grades – she was ready for the holiday break.  As she drove past the Woodstock Green, she noticed that Christmas ornaments decorated Woodstock’s covered bridge. The entire town was getting ready for Wassail Weekend.

“What a great place to raise a family,” Patty thought.  She, her husband Rob, and their twin 7-year-old sons just loved it there.  It was a very wholesome place for the boys (all three), with many outdoor activities.

She was going in early to meet with The Professor, but, before that, she had to hit the gym for her daily workout.  As she approached the Taftsville Bridge she decided to venture across and take the back road. This route was a mile longer, but crossing the bridge and riding on the back road was more uplifting to the soul.  The back road went along the river and was more picturesque and peaceful than the bustling Vermont Route 4.

The bridge in Taftsville, VT, is a pleasant sight on the way to Ivy University.

Wild turkeys near Taftsville, VT.

After crossing the bridge and driving a few miles, she suddenly had to hit the brakes as a flock of wild turkeys crossed the road – just another reason to like living in Vermont.

 

Before she knew it, she was in the faculty parking lot.  As with almost all universities, parking was a challenge. But, the sun was just rising on this late November day and the lot was mostly empty – except for Dean Howard’s car.

After her workout and shower, she was in The Professor’s office with her long-term sidekick, Pete.  Her husband Rob would join them soon after getting the boys off to school.  The four of them spoke Spanish and, when together, agreed to converse in this romance language to keep their skill sharp.  If Pete wasn’t there, the three would speak Mandarin Chinese, a language he didn’t know.  No one knew for sure how many languages The Professor spoke, but it was rumored to be about 18.  His parents were missionaries for Wycliffe Bible Translators, so he lived in many countries as a youth.

“Hola a mis amigos, la razón por la que les invité aquí fue a discutir DPMO,” The Professor began.

(The remainder of the text will be in English for our non-Spanish speakers.)

“Gee, I haven’t heard people talk about DPMO in years,” Pete responded.

“Remind us how it is tallied,” The Professor requested.

“Well, in electronics assembly, each lead that is assembled is counted as a possible soldering defect ‘opportunity,’ so you count the end of line defects and divide by the opportunities,” Pete began.

“Don’t forget that you normalize to parts per million,” Patty added.

“That’s where DPMO (defects per million opportunities) comes from,” Rob chimed in as he stuck his head in the door.

“And don’t forget to add one defect opportunity for the component itself,” The Professor added.

“Why the concern for DPMO?” Patty asked.

“One of my clients asked if a DPMO of 20 was good enough.” The Professor answered.

“With continuous improvement, shouldn’t they be striving to improve?” Pete asked.

“Well, to a point. But does anyone have a counter-thought?” The Professor answered, always trying to make a learning experience.

“Well if all special cause defects have been addressed and only common cause variation is left, it may be too expensive to improve significantly,” Patty commented.

Pete opined, ”I remember about 20 years ago, I worked for a large OEM and they were at a DPMO of 20.  They tried to get to 5, but it cost a fortune in engineering expense.  A DPMO of 20 hit their ‘common cause floor.’ It costs much more in engineering expense to try to get below the 20 DPMO than the small amount they would be saving in rework costs.”

“Hitting your ‘Common Cause Floor’ sounds like a new expression that you just created Pete— congrats,” Patty said.

Rob had been busy on his laptop and he suddenly chimed in, “I found an article that suggests that 20 to 50 DPMO is a reasonable goal.”

“Let’s do a shirt-sleeve calculation,” the Professor suggested.

“My client has a DPMO of 20. Each product has about 2500 leads and components. It costs $2 to repair a defective device. And, they make 1 million devices with a value of $100 each and a net profit margin of 5%,” The Professor went on.

“So, 20 DPMO times 2500 equals 50,000 or 5% defects in the 1 million units,” Patty started.

“That means 50,000 reworked devices out of the million manufactured for a cost of $100,000 or 2% of the $5 million net profit,” Rob added.

“Getting the DPMO to much less than 20 will cost millions a year in engineering expense,” Pete stated.

“So, let’s sum it all up,” the Professor suggested. “The ‘Common Cause Floor’ will be different for different manufacturers, but hoping to get a DPMO near 0 will likely be too expensive in engineering costs.”

“And, Pete will become famous for inventing the term, ‘The Common Cause Floor,” Patty joked.

They all ended the meeting with a laugh and a slap on Pete’s back.

Cheers,

Dr. Ron

OEM/EMS Barrier Permanently Cut

For years we’ve been told that EMS companies are in the service business only and would never develop their own products. In one of the first interviews I did, back in late 1991, then IPC director Tony Hilvers — a leading proponent of the then-emerging CM industry (it wasn’t even called EMS then; that term was coined by Sue Mucha the following year) — insisted to me that contract assemblers wouldn’t go down the product development and branding path because it would put them in position of competing with their customers.

We can bury that old saw. With today’s news that Foxconn has, at long last, bought Sharp (for the low, low price of $3.4 billion), the loop between EMS and OEM has been drawn taut.

Not that this is ground-breaking in practice. Certainly, many, many EMS companies have, through acquisition or otherwise, developed and marketed their own products. Our 2009 EMS Company of the Year had a healthy, branded keyboard product line. And we estimated in this space in 2012 that 15 to 20% of the (then) 2,400 companies listed in our EMS directory did some degree of ODM/OEM work.

Going further, we wrote in 2015 we felt the line between EMS and ODM has been “permanently crossed.” But the Foxconn-Sharp marriage takes it to an entirely different scale.

Whether the Sharp name stays on its product lines, which range from Aquos televisions to smartphones to solar panels, and includes the OLED technology so prized by Apple that it compelled Foxconn to write the check in the first place, remains to be seen.

Either way, there’s no going back. EMS is now OEM. Going forward, who is the customer they will serve? And knowing the line keeping their suppliers from their end-customers has been permanently breached, will this spur OEMs  to reestablish their assembly operations?

Good Talk

The big story out of IPC Apex Expo last week – about the only story, really – was the introduction of an open communications standard by Mentor Graphics’ Valor division, followed by the rapid response by more than two dozen assembly equipment providers and software developers over shared concern that the solution to machine-to-machine communication might end up residing in the hands of a single company.

At the heart of the matter is the so-called Industry 4.0. Also referred to as IIC (US), Made in China 2025 (China), Industrial Value Chain Initiative (Japan), Manufacturing 3.0 (South Korea) and other names, it stands for the capability for different equipment, made by different OEMs, to share bi-directional data over an open, yet secure, platform. Done right, it’s a major step toward permitting manufacturers to pick the best machines for their specific needs, versus being beholden to a single line solution. Fundamentally, it’s at the heart of a fully beating Internet of Things; some feel the fully automated factory can increase production efficiency by more than 30% over time, adding billions or more to national GDPs.

Let’s start with the Mentor specification. Two years in the making and announced just prior to the annual IPC trade show, it was released at the Las Vegas event as OML, which stands for Open Machine Language. Having years of experience writing translators for various assembly line machines, Valor took those translators and installed OML in front of them, and packaged the combination in a black box. Thus, in a relative instant, a solution to a much-discussed electronics assembly problem was at hand; OML satisfied the need for machines to talk to each other, and the box handled any connectivity issues.

Mentor planned to make OML available to any company through a partner program and would retain ownership over the protocol while relying on the partners to help shape the future direction of the specification.

In Las Vegas, of course, everything’s a gamble. Once word got around the show, equipment vendors said “not so fast.”

Mentor’s angle was to multiply the use of IoT through OML, thus exponentially expanding the market for its Valor tools. Perhaps worried by the legalese, or the potential for a single “owner” to license and potentially change or even shut out competitors, roughly two dozen assembly OEMs met over the course of two days to hammer out an agreement that reshapes the trajectory of the specification. Several equipment OEMs PCD&F/CIRCUITS ASSEMBLY spoke with agreed OML is technically sound but felt the business issues inherent in licensing a corporate spec could pose a host of problems. Up against this strong front, Mentor pivoted and offered OML as a starting point for a to-be-determined IPC standard.

In one sense, then, bi-directional communication goes back to the drawing board. Some 15 years ago an IPC committee published a shop floor equipment communication standard labeled IPC-2541 and colloquially known as CAMX. One presenter at the Apex sessions demonstrated how IoT could work using enhanced CAMX. The early take – and this has yet to be finalized, as not even the charter is on paper yet – is the task group will study a combination of OML, CAMX and perhaps other, yet-to-be-written software as part of its IPC mission.

All sides agree there will be an emphasis on speed. If nothing else, OML forced the industry to confront the fact that not only is a standard needed, it was needed yesterday.

Going forward, it will be up to each software company and manufacturer to leverage the IPC standard as they see fit. It remains to be seen if Mentor will ultimately concede OML or whether it will attempt to go it alone.

Some will recall a similar scenario with the data transfer formats for printed circuit board designs. Various specifications sat mostly idle for years, IPC-D-350, IGES and EDIF among them, until the powers behind Valor’s ODB and IPC’s GenCAM formats squared off. Valor donated the XML version of ODB to IPC in 2008, yet continues to maintain its ODB++ format. GenCAM evolved into IPC-2581, and upon Mentor’s purchase of Valor, finally gained traction among worried software competitors and OEMs who feared being shut out of markets or forced to switch tools.

Regardless of the back story, this is where the industry stands today, and a basically workable plan is being formulated. The speed with which the industry moved – and Mentor should be thanked for spurring action – screams the need is present and widespread, and there is general consensus on the solution. That’s a great story. After all, in electronics, how often does that happen.

Parts Shortage

While assembling SMT PCBs for a customer, the line unexpectedly ran out of 01005 package size resistors during the production run. This was due to an error on the customer’s part; they simply did not provide us with enough. But the customer still expected the finished product in-hand by the due date, and we did not want to disappoint him.

This, of course, created a dilemma. Should we halt production while additional parts were ordered, or simply continue? We placed a replenishment order immediately, and learned that we could not get them until the next day. We asked, “Is it possible to assemble these boards now, and add the part later when they arrive?” We also had to quickly assess the feasibility adding the part later on. How accessible is the site for this tiny part? Can it be done by a skilled soldering technician? We decided that it could.

An 01005 parts shortage didn’t stop production.

We proceeded to build the order with the exception of that single 01005 component. The site was accessible, we decided, so that the part could indeed be added individually to each PCB. Sure, it would take some time and hand soldering, but it would not cost us nearly as much time as if we had put the entire build on hold to wait for the parts.

Once the needed parts arrived, they were hand soldered onto each assembly by a skilled operator using slender soldering iron tips.

When the parts arrived the next day, we were able to employ our best hand soldering people with soldering irons equipped with special slender tips. The job went quickly and easily, and we were able to minimize downtime on the SMT line due to the unexpected component shortage, and keep this job on schedule, much to the relief of our customer. We came through for them despite their mistake, and they appreciated that.

The 01005 parts were easily and quickly added, and the entire job shipped by the required due date since the rest of the assembly had already been finished.

Efficient use of time, getting whatever can be done while minimizing down time, pays dividends when one is living by tight delivery schedules and expected ship dates. The more that can be achieved without unnecessary delays, the better the chances that a ship date can be honored.

Roy Akber

www.rushpcb.com

[email protected]

 

Happy St. Patrick’s Day!

And some trivia. You may have noticed that the soldermask used on most PC boards is green, as is the paint used on most steel truss bridges. Why is that? And what do the two things have in common? Why green PCBs and why green bridges?

To answer, I brought in color expert expert Patty O’Patrick O’Dell, who stated: “Many bridges and PCBs are green because they absorb red and blue light, only reflecting the green.”

That wasn’t quite what I was getting at, but close enough. The important thing, is that, generally, in commercial products, the PC boards are hidden, so the color doesn’t matter that much. With prototypes and a lot of the hobby or development boards, that is not the case, so many companies have chosen to use a different color as a part of their identity.

Arduino products are blue, as are most boards from Adafruit. SparkFun makes theirs red. Ti Launchpads are red as well. The Beaglebone uses color, essentially, as a model number; Beaglebone black, Beaglebone green. This is possible because major PC board fab houses have made different colors more economical than they used to be.

I’ve been asked if the color makes any difference electrically. In general, no. If you’re dealing with super high speeds, RF, or other exotic conditions, it’s always best to ask your board house. In those fringe areas, a lot of things have the potential to make a difference. Other than that, if you can afford it, and want to make a statement, go for it. You can often get different color silk screen legend too. Just make sure there’s contrast between the two. White silkscreen on white soldermask would not be the best choice.

Duane Benson
Beware the monsters from Id

blog.screamingcircuits.com

Goldman Moment

Congratulations to my old friend — as in “long-term”; I would never dare call her old — Patty Goldman, who was inducted into the IPC Hall of Fame this week (long overdue). In doing so, Patty becomes the first woman inducted to receive IPC’s highest honor (also long overdue).

I was on the IPC staff when Patty was chair of the Technical Activities Executive Council, which sets the priorities for all IPC standards activities. She ran that group of unruly engineers with an iron fist (well, really a gavel), demonstrating that not only could some sense of order and civility be brought to the Council, but that their meetings didn’t have to last four hours, either.

Way to go, Patty!

Electronic Swarms — Overhangs

As I’ve stated many times before, we see many, many different jobs go through our shop. In those jobs, we see some of the absolute newest components and packages; some not yet available to the public; some are so R&D that they never will be available outside of a lab. We see the best of the best in terms of design practices and complexity, and we see many that aren’t so much in that arena.

Given that, it would seem logical that the design problems we see would be pretty much scattered all over the map. By some measures they are, but on a day to day basis, they tend to cluster. For a few months we’ll see a lot of QFN footprint issues. In a different few months, we’ll see a lot of via in pad issues, etc. I don’t know why. It just works that way — problems come in swarms, or storms.

The latest swarm relates to panelized boards and components that stick over the edge of the board. We build things like that all the time. The problem comes in when the panel tabs come out right where the component overhangs. If the component overhangs in the cut out area, it’s usually not a problem. However, if the component is on the connection tabs, we can’t place that part without first depaneling.

Probably the most common example is the surface mount USB Micro-B receptacle. It over hangs the board by a small amount, and that overhanging part is actually bent down. If it’s at the tab, it won’t even mount flush. Take a close look at the images along the right. That connector won’t mount as it’s sitting on a tab.

So, what do you do about it?

You can have your boards made as individuals. Although if you want short-run production, or if the boards are really small, that might not be possible or practical. You can also talk to your fab house about it. They may be able to place the tabs in a spot that won’t get in the way of the overhanging part, of they might be able to tell you where the tabs will be, allowing you to keep clear in your layout.

Duane Benson
Anyone ever drink Tab Clear?

http://blog.screamingcircuits.com