CPSIA: Unit vs Component Testing
I don’t know how you’re feeling about this but I feel very discouraged much of the time. No, I don’t make children’s clothes but a great many of my friends do. Even if you don’t either, I’m hoping you’ll follow this closely and lend your support just as if it affected you directly. They don’t have any friends other than us.
At this point I’ll try to clear up a few questions that have been posed and provide other resources. I’m using four main sources for these entries.
- The AAFA -which I joined (@$3,000 fee!)- they’re having a Product Safety Council Meeting on December 3rd in Washington D.C. which I will be attending for up to the minute information and strategy. I hope you guys appreciate this; other than the costs I’m not fond of travel. I don’t have anything to wear either. I’ll be so outclassed it’s not even funny. Most of their members earn more in annual salaries than my gross annual sales so you could rightly surmise a bit of trepidation on my part.
- The CPSC website. There’s a listserv you can be added to upon request which will send you the rulings as they are released. If you need to catch up, here are all of the General Counsel advisory opinions released so far (scroll down).
- The videos of the CPSC Public Meeting on lead. There are three of them: staff and panel presentations and a Q & A. Of these, I’ve found the panel presentations from PLU to be the most interesting. As I write this entry, I’ll be referring to specific speakers in the panel discussion. It’s worth a listen with the exception of one guy I’ve dubbed Captain America for posturing and adding little to the content. This being a public blog I can’t say who that is but anyone who was there or watches it will know exactly who I’m talking about.
- The videos of Rick Woldenberg’s portion of the panel presentation. His presentation was so good, somebody took it upon themselves to post it on Youtube in three parts. He’s not a professional speaker and it takes him a few minutes to hit his stride but he is nothing short of compelling and convincing. While a large concern (a manufacturer and distributor of toys), he cogently makes the case of why these laws would adversely affect small producers too. If you only follow one link from this entry, this is the one to watch.
The rest of this entry focuses on unit vs component testing, what it means and why it matters.
Unit vs Component Testing
Component testing means you can test your inputs (fabric, buttons etc) going into the product individually. Unit testing means a completed product is tested rather than individual inputs. In the panel discussion, Stephen Lamar (AAFA) talks about this, some 21 minutes into the video. He also mentions this law is overwhelming the testing community because we don’t have enough labs even assuming everyone had the time, money and logistical infrastructure to do it.
Component testing is preferable for two main reasons.
- This saves money and time if you’re repeating fabrications and inputs over several styles -as you should be for continuity purposes and meeting minimums for purchasing.
- It achieves the safety intent of the law best.
Unit testing is not preferable for two reasons:
- It’s wasteful. If you’re using the same exact inputs in your products across styles, it’s dumb to retest the same zipper that is identical in each unit.
- It is less safe, circumventing the intent of the law. Let’s say you melt down a widget or whatever to reduce it into constituencies for testing. The total weight of the product is calculated in comparison to the weight of lead or phthalates so maybe the product is deemed within guidelines -but that doesn’t mean it’s safe. For example, let’s assume the major attributes of the product -like a flat screen tv- are inaccessible to a child and won’t be touched by them but the on and off button is and it’s completely constructed of lead. Should this product pass? Under current guidelines of unit testing it would but it shouldn’t. It would not pass with component testing. In other words, it is more important to test inputs as those can be weighted with respect to accessibility by the child.
Perhaps you’re asking yourself why lead needs to be in anything at all. That was addressed best by Christopher Cleet from the Information Technology Industry Council in the panel discussion (he was a good speaker). He said (paraphrased) “it’s not that we have truck loads of lead and are looking for a place to put it, it’s that it’s needed and useful”. Take your typical TV; that screen glass is full of lead (so don’t let your kids lick it). It has to be, otherwise viewers would be exposed to radiation. Mr. Fashion-Incubator concurs saying lead solder is best. In the EU, they’ve gravitated to tin solder (RoHS). The problem with tin solder is that it’s a friendly and sociable metal and likes to hook up with tin solder nearby forming tin whiskers. This will short out the unit causing failures in everything from pacemakers to video games. He adds that this will happen after your warranty is expired leaving you stuck with a lousy product.
At the risk of being pilloried in the community, it’s only fair to mention two reasons why unit testing is preferable. I didn’t hear any of the speakers mention these and it’s important to address so we can develop appropriate resolutions.
Why unit testing is preferable:
- The veracity of component testing can be questionable under certain circumstances. By this I mean that it is very very common in outsourcing situations for your contractor to make unauthorized substitutions for components at the last minute. This is the bane of small manufacturing. While you may have tested the proposed component when in the sourcing stage, unless you’re a large concern who operates your own plants overseas, you often don’t know what you’re getting until it lands at the dock. At this point you don’t have many choices. Maybe you’re “lucky” in that the only last minute change was shortening the sleeves but you’re stuck. You have to get with buyers to see if they’ll take the goods, hopefully without a discount or other losses.
- The other problem with component testing is that just as we make prototypes which we then present to buyers for orders, our suppliers do too. Just as you sometimes have to make changes to a style that was ordered and have to go back to your customer and okay the change, we’re working off of prototype components sometimes. You only have assurances on stock items. This is why suppliers will often call you to glean the liklihood of you buying a particular item down the road because they want to know if they’ll have enough orders themselves to justify producing it. As with us, there may be changes between the prototype and production component.
This is probably enough for one entry. I’ll continue in part two.
Related in the forum:
The War Room: CPSIA & Consumer Safety. This is a very active section with nearly 60 different threads and over 1,000 postings. Open to the public.