<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Shipulski On Design &#187; Product Development</title>
	<atom:link href="http://www.shipulski.com/category/product-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shipulski.com</link>
	<description>Innovation, Product Development, Design</description>
	<lastBuildDate>Sun, 25 Jul 2010 22:13:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Anyone want to save $50 billion?</title>
		<link>http://www.shipulski.com/2010/06/30/anyone-want-to-save-50-billion/</link>
		<comments>http://www.shipulski.com/2010/06/30/anyone-want-to-save-50-billion/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 01:50:22 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Cost Savings]]></category>
		<category><![CDATA[Culture]]></category>
		<category><![CDATA[DFA]]></category>
		<category><![CDATA[DFMA]]></category>
		<category><![CDATA[Design Engineers]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Product Development]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=953</guid>
		<description><![CDATA[I read a refreshing article in the Washington Post. Defense Secretary Robert M. Gates wants to save $20B per year on the Pentagon&#8217;s spend. I could kiss this guy! Gates wants contracts scrutinized more closely for inefficiencies and unneeded overhead. He said the savings could be shifted to support U.S. troops around the globe. Pentagon [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-955" title="money" src="http://www.shipulski.com/wp-content/uploads/2010/06/money.jpg" alt="" width="240" height="160" />I read a <a href="http://www.washingtonpost.com/wp-dyn/content/article/2010/06/28/AR2010062805053.html">refreshing article in the Washington Post</a>. Defense Secretary Robert M. Gates wants to save $20B per year on the Pentagon&#8217;s spend. I could kiss this guy!</p>
<p>Gates wants contracts scrutinized more closely for inefficiencies and unneeded overhead. He said the savings could be shifted to support U.S. troops around the globe. Pentagon officials said they&#8217;re looking for annual savings in the $400 billion spent on goods and services. They&#8217;re looking to save $20B, or 5%.</p>
<p>Gates has it right. The government must stop overpaying. But how? Gates suggests improved contract scrutiny to eliminate inefficiencies and unneeded overhead. He&#8217;s on the right track, but that&#8217;s not where the money is. Gates&#8217; real target should be material cost &#8211; that&#8217;s where the money is. But, can material cost bring $20B savings? Yes.</p>
<p>Assume the Pentagon spends $100B on services and $300B on goods. The cost of those of goods falls into three buckets: labor, material, and overhead, where material cost makes up the lion&#8217;s share at 70%, or $210B. A 10% reduction in material cost brings $21B in savings, and gets Gates to his target. But how?</p>
<p>To get the savings, the Pentagon must drive the right behavior.  They must must make suppliers submit a &#8220;<a href="http://www.dfma.com/software/supplier.htm">should cost</a>&#8221; with all proposals. The should cost is an estimated cost based on part geometries, materials, manufacturing processes used to create the parts, prevailing wage rates and machine rates, and profit. From these parameters, a should cost can be created in the design phase, without actually making the parts. So, the Pentagon will know what they should pay before the product is made. This cost analysis is based on real data, real machines, and real material costs.  There is no escape for defense contractors.  The cash cow is no longer.</p>
<p>Should costing will drive the design engineers to create designs that work better <strong>and </strong>cost less, something the defense industry thinks is impossible. <strong>They&#8217;re wrong</strong>. Given the tools, time, and training, the defense industry&#8217;s design engineering community can design out at least 25% of material cost, resulting in $50B+ in savings, more than twice Gates&#8217; goal. Someone just has to teach them how.</p>
<p>Mr. Secretary, the non-defense world is ready to help.  Just ask us. (But we&#8217;ll go after a 50% cost reduction.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/06/30/anyone-want-to-save-50-billion/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Back to Basics with DFMA</title>
		<link>http://www.shipulski.com/2010/06/27/back-to-basics-with-dfma/</link>
		<comments>http://www.shipulski.com/2010/06/27/back-to-basics-with-dfma/#comments</comments>
		<pubDate>Sun, 27 Jun 2010 21:00:26 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[DFMA]]></category>
		<category><![CDATA[Downstream Savings]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Manufacturing Competitiveness]]></category>
		<category><![CDATA[Part Count Reduction]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Product Robustness]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=928</guid>
		<description><![CDATA[About eight years ago, Hypertherm embarked on a mission to revamp the way it designed products. Despite the fact its plasma metal-cutting technology was highly regarded and the market leader in the field, the internal consensus was that product complexity could be reduced and thus made more consistently reliable, and there was an across-the-board campaign [...]]]></description>
			<content:encoded><![CDATA[<p>About eight years ago, Hypertherm embarked on a mission to revamp the way  it designed products. Despite the fact its plasma metal-cutting  technology was highly regarded and the market leader in the field, the  internal consensus was that product complexity could be reduced and thus  made more consistently reliable, and there was an across-the-board  campaign to reduce product development and manufacturing costs. Instead  of entailing novel engineering tactics or state-of-the-art process  change, it was a back-to-basics strategy around design for manufacture  and assembly (DFMA) that propelled Hypertherm to meet its goals.</p>
<p>The first step in the redesign program was determining what needed to  change. A steering committee with representation from engineering,  manufacturing, marketing, and business leadership spent weeks trying to  determine what was required from a product standpoint to deliver radical  improvements in both product performance and product economics. As a  result of that collaboration, the team established aggressive new  targets around robustness and reliability in addition to the goal of  cutting the parts count and labor costs nearly in half.</p>
<p><a href="http://engineeringcases.knovelblogs.com/2010/06/11/hypertherm-goes-back-to-basics-with-design-for-manufacture-and-assembly/">See link for entire article</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/06/27/back-to-basics-with-dfma/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Ready, Fire, Aim.</title>
		<link>http://www.shipulski.com/2010/04/28/ready-fire-aim/</link>
		<comments>http://www.shipulski.com/2010/04/28/ready-fire-aim/#comments</comments>
		<pubDate>Thu, 29 Apr 2010 00:46:22 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Recession]]></category>
		<category><![CDATA[Product Development Engine]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=771</guid>
		<description><![CDATA[Pent up demand is everywhere.  After almost two years of cutting inventories and pushing out purchases, companies are ready to buy. And with credit coming back on line, they&#8217;re ready to buy in bulk.  Good news?  No, great news.  We&#8217;re back on our growth path. And that&#8217;s good because Wall Street now expects growth. But, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.shipulski.com/wp-content/uploads/2010/04/Scylla-and-Charybdis.jpg"><img class="alignright size-medium wp-image-775" title="Scylla and Charybdis" src="http://www.shipulski.com/wp-content/uploads/2010/04/Scylla-and-Charybdis-300x224.jpg" alt="Scylla and Charybdis" width="300" height="224" /></a>Pent up demand is everywhere.  After almost two years of cutting inventories and pushing out purchases, companies are ready to buy. And with credit coming back on line, they&#8217;re ready to buy in bulk.  Good news?  No, great news.  We&#8217;re back on our growth path. And that&#8217;s good because Wall Street now expects growth. But, together this wicked couple of pent up demand and Wall Street&#8217;s appetite for immediate growth has created a powder keg that&#8217;s ready to blow.</p>
<p>Companies want more new products to satisfy the pent up demand (and Wall Street).  Growth through new products is a theme heard around the globe; there&#8217;s a relentless push for more products – early and often. Resources be damned, best practices be damned, we&#8217;re going to launch more products. Were going to market and will fix it later. The battle cry &#8211; Don&#8217;t launch, don&#8217;t sell!. However, the real battle cry is more aptly &#8211; Ready, fire, aim!  We&#8217;re going too fast.</p>
<p>I&#8217;m all for productivity, but we&#8217;re heading for a cliff, a cliff some have already accelerated off of, albeit in an unintended way.</p>
<p><span style="color: #ffffff;"><span style="font-size: x-small;">a</span></span></p>
<p><strong><span style="color: #0000ff;"><span style="font-size: medium;">We&#8217;ve forgotten the golden rule – provide value to customers, or you&#8217;re hosed.</span></span></strong></p>
<p><span style="color: #ffffff;"><span style="font-size: x-small;">a</span></span></p>
<p>Customers value function, or &#8220;what it does&#8221;.  Function first. But in this need-for-speed environment that&#8217;s just what&#8217;s at risk. To reduce time to market, we eliminate tasks (best practices?) in our product development processes. All good unless we eliminate tasks that make the product function as intended.  All good unless we load our engineers so heavily they don&#8217;t have time to design in functionality.  We must be careful here.  If you&#8217;re first to market and your product doesn&#8217;t work, you should have waited.</p>
<p>I believe launching too early is worse than launching too late because a botched launch can damage your brand, the brand you&#8217;ve taken years to build. <a href="http://www.shipulski.com/2009/12/09/lack-of-product-robustness-can-damage-your-brand/">(Click this link to see a post on brand damaging.)</a> As we know, word gets around when your product doesn&#8217;t work (or accelerates on its own).</p>
<p>Satisfying the siren of pent up demand can run you into the rocks if you&#8217;re not careful.  So block your ears to her song, and take the time to get your products right.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/04/28/ready-fire-aim/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Custom Model, exploring customized manufacturing (Mechanical Engineering Magazine)</title>
		<link>http://www.shipulski.com/2010/04/24/custom-model-exploring-customized-manufacturing-mechanical-engineering-magazine/</link>
		<comments>http://www.shipulski.com/2010/04/24/custom-model-exploring-customized-manufacturing-mechanical-engineering-magazine/#comments</comments>
		<pubDate>Sat, 24 Apr 2010 12:50:36 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Assembly Time Reduction]]></category>
		<category><![CDATA[Design Engineers]]></category>
		<category><![CDATA[Floor Space]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Part Count Reduction]]></category>
		<category><![CDATA[Product Development]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=762</guid>
		<description><![CDATA[By reducing parts count and easing assembly, one plasma cutter maker explores customized manufacturing. By Jean Thilmany, Associate Editor, Mechanical Engineering Magazine Ask nearly any engineer or manufacturer about customized manufacturing and—to a person—they’ll all say the same thing: Have you heard the Dell story? Dell is offered up again and again as the number [...]]]></description>
			<content:encoded><![CDATA[<p><em><strong>By reducing parts count and easing assembly, one plasma cutter maker explores customized manufacturing.</strong></em></p>
<p><strong>By Jean Thilmany, Associate Editor, Mechanical Engineering Magazine<br />
</strong></p>
<p>Ask nearly any engineer or manufacturer about customized manufacturing and—to a person—they’ll all say the same thing: Have you heard the Dell story?</p>
<p>Dell is offered up again and again as the number one example of customized manufacturing done right and done successfully. Shortly after its founding in 1984, Dell began what it calls a configure-to-order approach to manufacturing. The computer company lets customers customize their own computers on the Dell Web site. Buyers select how much memory and disk space they desire and the resulting computer is manufactured and shipped to them.</p>
<p>The approach has helped the computer maker see skyrocket growth. Last year, it held the second-highest spot for desktops and laptops shipped, behind Hewlett Packard, according to market-share numbers from research firm International Data Corp. in Framingham, Mass.</p>
<p>Manufacturers—particularly electronics manufacturers—have long been  taking notice. Many of them are investigating how the configure-to-order  model could be put to use at their own companies. And some of them have  implemented the method—along with the necessary software to get the job  done—with great success.</p>
<p>Take Hypertherm Inc. of Hanover, N.H.,  maker of plasma metal cutting equipment. The company has recently  started allowing customers to choose online from ten CNC Edge Pro  product configurations, up from three configurations in the former  product line, said John Sobr, head designer on the project.</p>
<p>Hypertherm recently redesigned its plasma metal cutting  equipment to  reduce part count by 27 percent while doubling the  number of inputs  available. Customers can now choose from ten product configurations.</p>
<p><a href="http://www.shipulski.com/publications/">Link to full article</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/04/24/custom-model-exploring-customized-manufacturing-mechanical-engineering-magazine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DFMA Won&#8217;t Work</title>
		<link>http://www.shipulski.com/2010/04/21/dfma-wont-work/</link>
		<comments>http://www.shipulski.com/2010/04/21/dfma-wont-work/#comments</comments>
		<pubDate>Thu, 22 Apr 2010 00:02:24 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[DFMA]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Intellectual Intertia]]></category>
		<category><![CDATA[Part Count Reduction]]></category>
		<category><![CDATA[Product Development]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=747</guid>
		<description><![CDATA[Ask a company or team to do DFMA, and you get a great list of excuses on why DFMA is not applicable and won&#8217;t work. Product volumes are too low for DFMA, or too high; product costs are too low, or too high; production processes are too simple, or complex; production mix is too low, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.shipulski.com/wp-content/uploads/2010/04/Negative-skeptic.jpg"><img class="alignright size-full wp-image-752" title="Negative skeptic" src="http://www.shipulski.com/wp-content/uploads/2010/04/Negative-skeptic.jpg" alt="Negative skeptic" width="185" height="240" /></a>Ask a company or team to do DFMA, and you get a great list of excuses on why DFMA is not applicable and won&#8217;t work. Product volumes are too low for DFMA, or too high; product costs are too low, or too high; production processes are too simple, or complex; production mix is too low, or too high.  That’s all crap – just excuses to get out of doing the work.  DFMA is applicable; it’s just a question of how to prioritize the work.</p>
<p>To prioritize the work, take a look at product volumes.  They&#8217;ll put you in the right ballpark. Here are three categories, low, medium, and high volume, to explain.</p>
<p><span style="color: #ffffff;">a<span id="more-747"></span></span></p>
<p><strong>Low Volume – 10 to 500 units per year</strong></p>
<p>“Our volumes are too low.  We can’t do DFMA.”  Yes you can.  Here’s how to prioritize:</p>
<p>Eliminate fasteners and connectors. Products in this category are riddled with nuts, bolts, and washers.  Zero thought has been put into manufacturing – none.  Nothing fancy here, just eliminate fasteners with good joint design.  Joints have twice the number of required bolts, so take some out.  Also, try nuts with integrated star washers.  Do DFA on the highest part count subassembly to get rid of some parts and learn the tool. Do DFM on your most costly part.  Yes, one single part.  You’ll be tempted to do more, but don’t.  That’s not where the money is.</p>
<p><span style="color: #ffffff;">a</span><span style="color: #ffffff;">a</span></p>
<p><strong>Medium Volume – 500 to 5000 units per year</strong></p>
<p>“Our volumes are too low and too high. (How can it be both?) We can’t do DFMA.” Yes you can.  Here’s how to prioritize:</p>
<p>Eliminate fasteners and connectors. Products in this category are riddled with nuts, bolts, and washers &#8211; use good joint design.  Do DFA on the whole product (all the subassemblies) to design out parts.  Take a special look at the wire harness if you have one (lots of connectors and wires) or create one from the loose wires. Add features to the remaining parts to reduce fasteners and connectors, e.g., tabs and slots in sheet metal.  Create features in the parts to aid in assembly – alignment, anti-rotation, and poke-yoke.  Do DFM on your five most costly parts.  Yes, five parts.  You’ll be tempted to do more, but don’t.  That’s not where the money is.</p>
<p><span style="color: #ffffff;">a</span><span style="color: #ffffff;">a</span></p>
<p><strong>High Volume – 10,000+ per year</strong></p>
<p>“Our volumes are too high.  We can’t do DFMA.”  Yes you can.  Here’s how to prioritize:</p>
<p>Eliminate fasteners and connectors. Products in this category are riddled with nuts, bolts, and washers.  To start, do everything described in the Medium Volume category. You must use new manufacturing technologies, such as molding and forming, to further reduce part count.  Add features in parts to further improve assembly and add some process automation. Do DFM on your 10 most costly parts.  Yes, 10 parts. You’ll be tempted to do more, but don’t.  That’s not where the money is.</p>
<p><span style="color: #ffffff;">a</span><span style="color: #ffffff;">a</span></p>
<p>The volume numbers for the categories are not absolute, they&#8217;re just guidelines. (For example, some companies in the Medium Volume category use molding to eliminate parts. Soft tooling can reduce tooling costs enough to make it work.)</p>
<p>The excuses and static thinking are powerful obstacles to overcome.  But with 50% savings on the line, it&#8217;s worth pushing through them.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/04/21/dfma-wont-work/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>DFMA to Control Controller Design &#8211; Design2Part Magazine</title>
		<link>http://www.shipulski.com/2010/04/05/dfma-to-control-controller-design-design2part-magazine/</link>
		<comments>http://www.shipulski.com/2010/04/05/dfma-to-control-controller-design-design2part-magazine/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 01:46:08 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Cost Savings]]></category>
		<category><![CDATA[DFA]]></category>
		<category><![CDATA[DFMA]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Part Count Reduction]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Product Robustness]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=694</guid>
		<description><![CDATA[Design for Manufacture and Assembly is reported to improve CNC performance, modularity, durability, and serviceability When Hypertherm (www.hypertherm.com) was getting ready to design its next generation of metal cutting CNCs, the engineering team’s goal was to make improvements. But the controllers, which automate the Hanover, New Hampshire-based company’s advanced cutting tools and systems, were already [...]]]></description>
			<content:encoded><![CDATA[<p><em>Design for Manufacture and Assembly is reported to improve CNC performance, modularity, durability, and serviceability</em></p>
<p>When Hypertherm (<a href="http://www.hypertherm.com">www.hypertherm.com</a>) was getting ready to design its next generation of metal cutting CNCs, the engineering team’s goal was to make improvements. But the controllers, which automate the Hanover, New Hampshire-based company’s advanced cutting tools and systems, were already well-accepted in the marketplace and highly regarded in the industry. So why redesign? And how would they go about it?</p>
<p>See this link for the full article -<a href="http://www.jobshoptechnology.com/Article.aspx?ArticleID=130"> Using DFMA to Control Controller Design</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/04/05/dfma-to-control-controller-design-design2part-magazine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Discontinuous Improvement at the Expense of Continuous Improvement</title>
		<link>http://www.shipulski.com/2010/03/31/discontinuous-improvement-at-the-expense-of-continuous-improvement/</link>
		<comments>http://www.shipulski.com/2010/03/31/discontinuous-improvement-at-the-expense-of-continuous-improvement/#comments</comments>
		<pubDate>Thu, 01 Apr 2010 02:36:49 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Innovation]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Top Line Growth]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=678</guid>
		<description><![CDATA[Five percent here, three percent there. I&#8217;m tired as hell of continuous improvement. Sure there&#8217;s a place for it, but it shouldn&#8217;t be the only type of work we do. But, unfortunately, that&#8217;s just what&#8217;s happened in manufacturing. To secure the balance sheet, the pendulum swung too far toward continuous improvement. Just look at what [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.shipulski.com/wp-content/uploads/2010/03/s-curve.jpg"><img class="alignright size-medium wp-image-682" title="s-curve" src="http://www.shipulski.com/wp-content/uploads/2010/03/s-curve-300x225.jpg" alt="s-curve" width="300" height="225" /></a>Five percent here, three percent there. I&#8217;m tired as hell of continuous improvement. Sure there&#8217;s a place for it, but it shouldn&#8217;t be the only type of work we do. But, unfortunately, that&#8217;s just what&#8217;s happened in manufacturing. To secure the balance sheet, the pendulum swung too far toward continuous improvement. Just look at what we&#8217;re writing about – the next low cost country, shorter lead times, how to be profitable where there&#8217;s no profit to be had. Those topics scream continuous improvement – take nickels and dimes out of processes to increase profits. But there&#8217;s a dark side to all this focus on continuous improvement.  It has created a big problem: it has come at the expense of discontinuous improvement.</p>
<p>Continuous improvement is a philosophy of minimization with a focus on cost and waste reduction, while discontinuous improvement is a philosophy of maximization with a focus on creation of new markets through product innovation. As of late, we&#8217;ve minimized waste at the expense of invention and innovation. I propose we flip this on its head and maximize through discontinuous improvement at the expense of continuous improvement. That&#8217;s right; I said do less lean and Six Sigma.</p>
<p>But we must ask ourselves if we&#8217;re capable of doing discontinuous improvement. Remember, we ignored or dismantled our innovation engines over the last years. And what about our big thinkers, our creative thinkers, our innovators? Do they still work for us, or have they just stopped talking about big ideas? I urge you to answer that question because your next actions depend on it.</p>
<p>If your innovative thinkers are gone, go out and hire the best you can find ASAP. If you were fortunate enough to retain your big thinkers, congratulations. Now it&#8217;s time to get the band back together, but first you&#8217;ve got to do some reconnaissance to ferret them out of their hiding places. Once you find them, invite them to a nice lunch – the nicer the better. Don&#8217;t push too hard at lunch, just start to  get reacquainted. In time you&#8217;ll get to talk about their ideas on new technologies and how to create new markets.</p>
<p>It will be difficult to get your company swing the pendulum away from continuous improvement, but you must try. Without discontinuous improvement your company will be destined to wrestle for nickels using lean and Six Sigma.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/03/31/discontinuous-improvement-at-the-expense-of-continuous-improvement/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Pareto&#8217;s Three Lenses for Product Design</title>
		<link>http://www.shipulski.com/2010/03/24/paretos-three-lenses-for-product-design/</link>
		<comments>http://www.shipulski.com/2010/03/24/paretos-three-lenses-for-product-design/#comments</comments>
		<pubDate>Thu, 25 Mar 2010 03:16:02 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Assembly Time Reduction]]></category>
		<category><![CDATA[Cost Savings]]></category>
		<category><![CDATA[Design Engineers]]></category>
		<category><![CDATA[Floor Space]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Part Count Reduction]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Seven Wastes]]></category>
		<category><![CDATA[Engineering Mindset]]></category>
		<category><![CDATA[Part Count]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=658</guid>
		<description><![CDATA[Axiom 1 &#8211; Time is short, so make sure you&#8217;re working on the most important stuff. Axiom 2 &#8211; You can&#8217;t design out what you can&#8217;t see. In product development, these two axioms can keep you out of trouble. They&#8217;re two sides of the same coin, but I&#8217;ll describe them one at a time and [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: small;"><strong><span style="color: #0000ff;">Axiom 1 &#8211; Time is short, so make sure you&#8217;re working on the most important stuff.</span></strong></span></p>
<p><span style="font-size: small;"><strong><span style="color: #0000ff;">Axiom 2 &#8211; You can&#8217;t design out what you can&#8217;t see.</span></strong></span></p>
<p>In product development, these two axioms can keep you out of trouble. They&#8217;re two sides of the same coin, but I&#8217;ll describe them one at a time and hope it comes together in the end.</p>
<p>With Axiom 1, how do you make sure you&#8217;re working on the most important stuff? We all know it&#8217;s function first – no learning there. But, sorry design engineers, it doesn&#8217;t end with function. You must also design for lean, for cost, and factory floor space. Great. More things to design for. Didn&#8217;t you say time was short? How the hell am I going to design for all that?</p>
<p>Now onto the seeing business of Axiom 2. If we agree that lean, cost, and factory floor space are the right stuff, we must &#8220;see it&#8221; if we are to design it out. See lean? See cost? See factory floor space? You&#8217;re nuts.  How do you expect us to do that?</p>
<p>Pareto to the rescue – use Pareto charts to identify the most important stuff, to prioritize the work. With Pareto, it&#8217;s simple: work on the biggest bars at the expense of the smaller ones. But, Paretos of what?</p>
<p>There is no such thing as a clean sheet design &#8211; all new product designs have a lineage. A new design is based on an existing design, a baseline design, with improvements made in several areas to realize more features or better function defined by the product specification. The Pareto charts are created from the baseline design to allow you to see the things  to design out (Axiom 2). But what lenses to use to see lean, cost, and factory floor space?</p>
<p>Here are Pareto&#8217;s three lenses so see what must be seen:</p>
<p>To lean out lean out your factory, design out the parts. Parts create waste and part count is the surrogate for lean.</p>
<p><a href="http://www.shipulski.com/wp-content/uploads/2010/03/Slide2.JPG"><img class="aligncenter size-medium  wp-image-661" title="Slide2" src="http://www.shipulski.com/wp-content/uploads/2010/03/Slide2-300x225.jpg" alt="Slide2" width="300" height="225" /></a></p>
<p>To design out cost, measure cost. Cost is the surrogate for cost.</p>
<p><a href="http://www.shipulski.com/wp-content/uploads/2010/03/Slide3.JPG"><img class="aligncenter size-medium wp-image-659" title="Slide3" src="http://www.shipulski.com/wp-content/uploads/2010/03/Slide3-300x225.jpg" alt="Slide3" width="300" height="225" /></a></p>
<p>To design out factory floor space, measure assembly time. Since factory floor space scales with assembly time, assembly time is the surrogate for factory floor space.</p>
<p><a href="http://www.shipulski.com/wp-content/uploads/2010/03/Slide1.JPG"><img class="aligncenter size-medium  wp-image-660" title="Slide1" src="http://www.shipulski.com/wp-content/uploads/2010/03/Slide1-300x225.jpg" alt="Slide1" width="300" height="225" /></a></p>
<p>Now that your design engineers have created the right Pareto charts and can see with the right glasses, they&#8217;re ready to focus their efforts on the most important stuff. No boiling the ocean here. For lean, focus on part count of subassembly 1; for cost, focus on the cost of subassemblies 2 and 4; for floor space, focus on assembly time of subassembly 5. Leave the others alone.</p>
<p>Focus is important and difficult, but Pareto can help you see the light.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/03/24/paretos-three-lenses-for-product-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fasteners Can Consume 20-50% of Assembly Labor</title>
		<link>http://www.shipulski.com/2010/02/03/fasteners-can-consume-20-50-of-assembly-labor/</link>
		<comments>http://www.shipulski.com/2010/02/03/fasteners-can-consume-20-50-of-assembly-labor/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 17:36:14 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Allocating Cost]]></category>
		<category><![CDATA[Assembly Time Reduction]]></category>
		<category><![CDATA[DFA]]></category>
		<category><![CDATA[DFMA]]></category>
		<category><![CDATA[Floor Space]]></category>
		<category><![CDATA[Part Count Reduction]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Design for Assembly]]></category>
		<category><![CDATA[Part Count]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=496</guid>
		<description><![CDATA[The data-driven people in our lives tell us that you can&#8217;t improve what you can&#8217;t measure.  I believe that. And it&#8217;s no different with product cost. Before improving product cost, before designing it out, you have to know where it is. However, it can be difficult to know what really creates cost.  Not all parts [...]]]></description>
			<content:encoded><![CDATA[<p>The data-driven people in our lives tell us that you can&#8217;t improve what you can&#8217;t measure.  I believe that. And it&#8217;s no different with product cost. Before improving product cost, before designing it out, you have to know where it is. However, it can be difficult to know what really creates cost.  Not all parts and features are created equal; some create more cost than others, and it&#8217;s often unclear which are the heavy hitters. Sometimes the heavy hitters don&#8217;t look heavy, and often are buried deeply within the hidden factory.</p>
<p>Measure, measure, measure.  That&#8217;s what the black belts say.  However, it&#8217;s difficult to do well with product cost since our costing methods are hosed up and our measurement systems are limited. What do I mean? Consider fasteners (e.g., nuts, bolts, screws, and washers), the product&#8217;s most basic life form. Because fasteners are not on the BOM, they&#8217;re not part of product cost. Here&#8217;s the party line: it&#8217;s overhead to be shared evenly across all the products in a socialist way.  That&#8217;s not a big deal, right?  Wrong.  Although fasteners don&#8217;t cost much in ones and twos, they do add up. 300-500 pieces per unit times the number of units per year makes for a lot of unallocated and untracked cost.  However, a more significant issue with those little buggers is they take a lot of time attach to the product.  For example, using standard time data from DFMA software, assembly of a 1/4&#8243; nut with a bolt, locktite, a lockwasher, and cleanup takes 50 seconds.  That&#8217;s a lot of time. You should be asking yourself what that translates to in your product. To figure it out, multiply the number nut/bolt/washer groupings by 50 seconds and multiply the result by the number of units per year. Actually, never mind.  You can&#8217;t do the calculation because you don&#8217;t know the number of nut/bolt/washer combinations that are in your product. You could try to query your BOMs, but the information is likely not there.  Remember, fasteners are overhead and not allocated to product. Have you ever tried to do a cost reduction project on overhead?  It&#8217;s impossible.  Because overhead inflicts pain evenly to all, no one is responsible to reduce it.</p>
<p style="padding-left: 60px;"><span style="color: #0000ff;"><strong><span style="font-size: medium;">With fasteners, it&#8217;s like death by a thousand cuts.</span></strong></span></p>
<p>The time to attach them can be as much as 20-50% of labor. That&#8217;s right, up to 50%.  That&#8217;s like paying 20-50% of your folks to attach fasteners all day. That should make you sick.  But it&#8217;s actually worse than that.  From Line Design 101, the number of assembly stations is proportional to demand times labor time. Since fasteners inflate labor time, they also inflate the number of assembly stations, which, in turn, inflates the factory floor space needed to meet demand. Would you rather design out fasteners or add 15% to your floor space?  I know you can get good deals on factory floor space due to the recession, but I&#8217;d still rather design out fasteners.</p>
<p>Even with the amount of assembly labor consumed by fasteners, our thinking and computer systems are blind to them and the associated follow-on costs. And because of our vision problems, the design community cannot be held accountable to design out those costs.  We&#8217;ve given them the opportunity to play dumb and say things like, &#8220;Those fastener things are free. I&#8217;m not going to spend time worrying about that.  It&#8217;s not part of the product cost.&#8221;  Clearly not an enlightened statement, but it&#8217;s difficult to overcome without cost allocation data for the fasteners.</p>
<p>The work-around for our ailing thinking and computer-based cost tracking systems is simple: get the design engineers out to the production floor to build the product.  Have them experience first hand how much waste is in the product.  They&#8217;ll come back with a deep-in-the-gut understanding of how things really are. Then, have them use DFMA software to score the existing design, part-by-part, feature-by-feature.  I guarantee everyone will know where the cost is after that. And once they know where the cost is, it will be easy for them to design it out.</p>
<p>I have data to support my assertion that fasteners can make up 20-50% of labor time, but don&#8217;t take my word for it. Go out to the factory floor, shut your eyes and listen.  You&#8217;ll likely hear the never ending song of the nut runners. With each chirp, another nut is fastened to its bolt and washer, and another small bit of labor and factory floor space is consumed by the lowly fastener.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/02/03/fasteners-can-consume-20-50-of-assembly-labor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Innovation, Technical Risk, and Schedule Risk</title>
		<link>http://www.shipulski.com/2010/01/13/innovation-technical-risk-and-schedule-risk/</link>
		<comments>http://www.shipulski.com/2010/01/13/innovation-technical-risk-and-schedule-risk/#comments</comments>
		<pubDate>Thu, 14 Jan 2010 03:17:54 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Innovation]]></category>
		<category><![CDATA[One Page Thinking]]></category>
		<category><![CDATA[Problems]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Problem Definition]]></category>
		<category><![CDATA[Understanding Physics]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=444</guid>
		<description><![CDATA[There is a healthy tension between level of improvement, or level of innovation, and time to market. Marketing wants radical improvement, infinitely short project schedules, and no change to the product. Engineers want to sign up for the minimum level of improvement, project schedules sufficiently long to study everything to death, and want to change [...]]]></description>
			<content:encoded><![CDATA[<p>There is a healthy tension between level of improvement, or level of innovation, and time to market. Marketing wants radical improvement, infinitely short project schedules, and no change to the product. Engineers want to sign up for the minimum level of improvement, project schedules sufficiently long to study everything to death, and want to change everything about the new product. It&#8217;s healthy because there is balance &#8211; both are pulling equally hard in opposite directions and things end up somewhere in the middle. It&#8217;s not a stress-free environment, but it&#8217;s not too bad. But, sometimes the tension is unhealthy.</p>
<p>There are two flavors of unhealthy tension. First is when engineering has too much pull; they (we) sandbag on product performance and project timelines and change the design willy-nilly simply because they can (and it&#8217;s fun). The results are long project timelines, highly innovative designs that don&#8217;t work well, a lack of product robustness, and a boatload of new parts and assemblies. (Product complexity.) Second is when Marketing has too much pull; they ask for radical improvement in product functionality with project timelines too short for the level of innovation, and tightly constrain product changes such that solutions are not within the constraints. The results are long project timelines and un-innovative designs that don&#8217;t meet product specifications. (The solutions are outside the constraints.) Both sides are at fault in both scenarios. There are no clean hands.</p>
<p>What are the fundamentals behind all this gamesmanship? For engineering it&#8217;s technical risk; for marketing it&#8217;s schedule risk. Engineering minimizes what it signs up for in order to reduce technical risk and petitions for long project timelines to reduce it. Marketing minimizes product changes (constraints) to reduce schedule risk and petitions for short project timelines to reduce it. (Product development teams work harder with short schedules.) Something&#8217;s got to change.<span id="more-444"></span></p>
<p>The relationship between innovation and technical risk must be changed. For every unit measure of innovation there must be less technical risk. Or, conversely, for every unit measure of technical risk there must be more innovation. Sounds great, but how? Well, deep questions like this deserve deep answers, answers that only the great philosophers can provide. As it turns out, the great American philosopher (and baseball player) Yogi Berra provides the answer:</p>
<blockquote><p>If you don&#8217;t know where you are going, you will end up somewhere else.</p></blockquote>
<p>&#8220;Where we are going&#8221;, our destination, is a solution to a technical problem which the innovation process winds us toward, and the probability we&#8217;ll &#8220;end up somewhere else&#8221;, getting lost, is technical risk. We&#8217;ve got to know where we&#8217;re going if we&#8217;re to have any hope of getting there.</p>
<p>The key to getting there is problem definition. Not the regular kind, but the physics-capturing kind; the kind that is expressed simply, with regular nouns and verbs, that can be explained to non-technical folks, and fits on one page. An example of this one-page problem definition can be found in a previous post. (Search the site for &#8220;one-page thinking&#8221;.) Problem definition of this type is powerful and difficult, and it&#8217;s the key to innovation. Once the real problem is defined, once the physics are understood and can be described plainly, the problem is solved, and the destination is close-at-hand.</p>
<p>Not many have seen or done this one-page, physics-capturing problem definition. And it&#8217;s power is severely underestimated and poorly understood. I&#8217;m sure many think I&#8217;m off my rocker when I say that one-page, physics-capturing problem definition is the key to innovation. But, I stick by my assertion. Once this hyper-rigorous problem solving helps you know where you are going, innovation can be as straightforward as entering a street address into your GPS.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2010/01/13/innovation-technical-risk-and-schedule-risk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
