<?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>Rooster&#039;s Revenge &#187; formability</title>
	<atom:link href="http://www.dieguy.com/tag/formability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dieguy.com</link>
	<description>Official Tim Stephens Website</description>
	<lastBuildDate>Sun, 05 Feb 2012 14:26:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Time Well Spent</title>
		<link>http://www.dieguy.com/2010/09/09/time-well-spent/stephens/</link>
		<comments>http://www.dieguy.com/2010/09/09/time-well-spent/stephens/#comments</comments>
		<pubDate>Thu, 09 Sep 2010 12:07:37 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[Engineering Decisions]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[Tips & Techniques]]></category>
		<category><![CDATA[commodity code]]></category>
		<category><![CDATA[die design]]></category>
		<category><![CDATA[formability]]></category>
		<category><![CDATA[job]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[quoting]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[task analysis]]></category>
		<category><![CDATA[waiting]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=875</guid>
		<description><![CDATA[Interesting conversation the other day with someone about getting the job done fast. Although the topic of discussion was quoting dies in advance of an actual design, this applies to design, formability analysis, and just about every other J-O-B in this business. It seems like everyone rushes to say &#8220;we need faster quote tools&#8221; or [...]]]></description>
			<content:encoded><![CDATA[<p>Interesting conversation the other day with someone about getting the job done fast. Although the topic of discussion was quoting dies in advance of an actual design, this applies to design, formability analysis, and just about every other J-O-B in this business.</p>
<p>It seems like everyone rushes to say &#8220;we need faster quote tools&#8221; or &#8220;we need faster simulation software&#8221; or &#8220;we need faster die design programs&#8221; and the like.</p>
<p>I counter with faster does not mean better. Better is usually accuracy. Believe me, they want accuracy too. But speed is the challenge.</p>
<p>At the heart of the speed challenge is usually not about the job of quoting, forming, or designing. Quite the contrary.</p>
<p>When I was doing die design, I spent more time seeking information to do the job than it took to do the design job itself. The same goes for when I did formability analysis. Hell, I would spend more time trying to find out what some bullshit proprietary commodity code for material really was than it took to set up and run the simulation.</p>
<p>So, let&#8217;s take quoting for a detailed breakdown of what I am talking about. To quote a job, you need a process. Once you have a process or die operational lineup, most companies use some form of semi-automated Excel spreadsheet for quoting.</p>
<p>To process and quote a job, for instance, this is typically what happens:</p>
<p>1. Search for CAD file. (5 minutes)</p>
<p>2. Launch one-step to get blank size. (5 minutes)</p>
<p>3. One-step needs IGS and you have a Catia file. Go get coffee. (10 minutes)</p>
<p>4. Launch Catia, open file, and save as IGS. (10 minutes)</p>
<p>5. Run one-step to get blank. (5 minutes)</p>
<p>6. Determine process (5 minutes)</p>
<p>7. Get files needed to create process and quote forms (5 minutes)</p>
<p>8. Export images of part and blank from one-step (5 minutes)</p>
<p>9. Import images into process sheet and crop so they look pretty (5 minutes)</p>
<p>10. Fill out process form by copying info from a BOM (9 minutes)</p>
<p>11. Use Ouija board quoting tool to get price (1 minute)</p>
<p>12. Put quote 10 folders deep on a server to make them hard to find (10 minutes)</p>
<p>13. Take the quotes out of the folder and send to 57 people for review (10 minutes)</p>
<p>14. Make necessary changes and put back in the folder (10 minutes)</p>
<p>15. Take a nap until the next job comes up (usually 5 minutes) </p>
<p>As you can see, most of what needs to happen to get the job done is NOT time well spent. Instead, it is spent doing things that really do not, or should not, matter.</p>
<p>Bottom line in this example is the quote itself &#8211; the price &#8211; is only 1% of the effort. Getting the quote depends on the process and the process takes 9% of the effort. The other 90% is spent getting to the point of doing the meaningful work.</p>
<p>Let&#8217;s say you cut the time spent quoting and processing by 90%. This comes down to 1 minute. Everything else still takes 90 minutes (in this example anyway). So now instead of having 90% of non-value, we have 99% non-value to complete the task.</p>
<p>Why not focus on cutting down on the non-value like searching for CAD files and material specs and such? Keep the coffee and lose the folders I say.</p>
<p>If you want to go faster, focus on cutting out the steps that consume non-value added time, like finding and converting CAD files.</p>
<p><img src="http://badges.alltop.com/images/alltop_170x30_whoa.jpg" alt="Alltop. How the hell did that happen?" width="170" height="30" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2010/09/09/time-well-spent/stephens/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Commodity Codes Suck</title>
		<link>http://www.dieguy.com/2010/05/26/commodity-codes-suck/stephens/</link>
		<comments>http://www.dieguy.com/2010/05/26/commodity-codes-suck/stephens/#comments</comments>
		<pubDate>Wed, 26 May 2010 16:19:55 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[Engineering Decisions]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[commodity code]]></category>
		<category><![CDATA[formability]]></category>
		<category><![CDATA[material specification]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[simulation]]></category>
		<category><![CDATA[stamping]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=794</guid>
		<description><![CDATA[Why is it that, when I either process a stamping or setup a formability simulation for any company in any industry on any continent, I get some proprietary commodity code for a material specification from the customer? Commodity codes suck, and I will tell you why: they are completely useless. Every company that needs sheet [...]]]></description>
			<content:encoded><![CDATA[<p>Why is it that, when I either process a stamping or setup a formability simulation for any company in any industry on any continent, I get some proprietary commodity code for a material specification from the customer?</p>
<p>Commodity codes suck, and I will tell you why: they are completely useless.</p>
<p>Every company that needs sheet steel to manufacture products buys the same steel from the same material manufacturers. Commodity codes are a reference to an existing material that the company will purchase.</p>
<p>Die engineers need material properties to do their job effectively. It takes longer to cross-reference some bullshit commodity code to something meaningful than it does to do the job itself.</p>
<p>Here is an idea: create a universally-recognized generic smart code for each material. By smart I mean include the abbreviation for the material type and grade plus the tensile strength.</p>
<p>So, instead of a commodity code like SPX28975AFU, I would have S-DP-500 for Dual Phase Steel with a tensile strength of 500 MPa.</p>
<p>From there, I not only know generally what the material is, I can also get the material properties I need without guessing.</p>
<p><img src="http://badges.alltop.com/images/alltop_170x30_clueless.jpg" alt="Alltop. I don't know how I got there either." width="170" height="30" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2010/05/26/commodity-codes-suck/stephens/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>The Point</title>
		<link>http://www.dieguy.com/2010/03/10/the-point/stephens/</link>
		<comments>http://www.dieguy.com/2010/03/10/the-point/stephens/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 16:50:50 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[Engineering Decisions]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[articles]]></category>
		<category><![CDATA[formability]]></category>
		<category><![CDATA[the point]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=535</guid>
		<description><![CDATA[I continue to be amazed at how some highly educated people miss the point. Case in point: I had a customer that was experiencing splitting on a stamping. Certain coils would run fine. Others would have 90%+ failure. I get their process data and run a formability simulation. The result? A good stamping. No risk [...]]]></description>
			<content:encoded><![CDATA[<p>I continue to be amazed at how some highly educated people miss the point.</p>
<p>Case in point: I had a customer that was experiencing splitting on a stamping.</p>
<p>Certain coils would run fine. Others would have 90%+ failure.</p>
<p>I get their process data and run a formability simulation.</p>
<p>The result? A good stamping. No risk of failure.</p>
<p>I then ask for tool architecture data. They had a holding pad that did not really serve a purpose. But, I model it up anyway and re-run the simulation.</p>
<p>Good results.</p>
<p>I then ask for force and travel information off the actual tool. I wanted it down to individual spring locations.</p>
<p>I model that up and re-run.</p>
<p>Still, no failures.</p>
<p>I have the customer take a sample from a failing coil and have an independent laboratory give me engineering properties for the material.</p>
<p>I model that up. And after this iteration, the formability is just fine.</p>
<p>On a conference call with the customer, we brainstorm the root cause.</p>
<p>We come up with nothing.</p>
<p>At the end of the call, the press operator comes into the room.</p>
<p>&#8220;Hey Tim. This material feels like it is corrugated. And it is really gritty, just like sandpaper. The other coils we run fine are not like this. Thought I would mention it.&#8221;</p>
<p>Thought you would mention it? We just found the root cause.</p>
<p>Now, the formability analysis software on the market takes material texture, tool texture, lubrication, and heat and throws it all into one variable: coefficient of friction.</p>
<p>I tweak that variable from a standard 0.20 to 0.15.</p>
<p>Lo and behold, my model now fails EXACTLY like the production stamping.</p>
<p>Exactly.</p>
<p>The customer is ecstatic.</p>
<p>As engineers, we spend our lives trying to make something work.</p>
<p>In this case, I had to purposely make something break.</p>
<p>I write an article titled <em>Make it Break: How to Make a Successful Simulation Fail</em> for a confidential newsletter published by the formability software company.</p>
<p>The customer loved the article. I thought it was one of my best.</p>
<p>The point to the story was simple: the trials of tribulations of making the formability fail instead of making the formability pass.</p>
<p>It was that simple.</p>
<p>Now, I write for the average die guy. I am an average die guy. I like to keep it simple. My goal is to write in a clear, concise, and precise manner. Free from needlessly complex jargon and the theoretical analysis.</p>
<p>So, what happens next?</p>
<p>The software company has alot of PhDs. Alot.</p>
<p>One of them wants to run a statistical variation analysis to judge the sensitivity of the process to different variables.</p>
<p>Ok. We had already solved the problem. We identified the root cause, and developed corrective and preventative action plans.</p>
<p>The process is sensitive only to the surface texture of the material. Nothing else mattered.</p>
<p>But, the statistical analysis was done.</p>
<p>The results were wrong because the assumptions were wrong.</p>
<p>I go in and tweak the numbers to get the result to agree with what I already know.</p>
<p>This statistical thing was added to my article under protest.</p>
<p>The publisher initially refuses to publish the work because it was &#8220;missing&#8221; the equations, charts, and graphs.</p>
<p>I explain the intent of the article. It now gets published under <em>their</em> protest.</p>
<p>Then comes the phone calls and emails.</p>
<p>All these PhDs start asking for the model. The equations. The inputs.</p>
<p>They wanted to fix the problem and get the stamping to pass instead of failing.</p>
<p>The only purpose of the article &#8211; the message &#8211; was this was the one in a million jobs where success meant failure.</p>
<p>It was the complete opposite of how us engineers are supposed to think.</p>
<p>That&#8217;s it.</p>
<p>That was July 2009.</p>
<p>And I am still getting emails from those that have missed the point.</p>
<p><a href="http://engineering.alltop.com/"><img src="http://badges.alltop.com/images/ka_alltop_170x30.jpg" alt="Alltop, confirmation that I kick ass" width="170" height="30" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2010/03/10/the-point/stephens/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Skin It</title>
		<link>http://www.dieguy.com/2009/10/13/skin-it/stephens/</link>
		<comments>http://www.dieguy.com/2009/10/13/skin-it/stephens/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 21:24:12 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Tips & Techniques]]></category>
		<category><![CDATA[autoform]]></category>
		<category><![CDATA[formability]]></category>
		<category><![CDATA[skin parts]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=347</guid>
		<description><![CDATA[Forming simulation software needs a zero thickness sheet for meshing purposes. Oftentimes, the designer will have an IGES or STEP file of the product data at full material thickness. We have to perform a step known as &#8220;skinning&#8221; to get just the inside of metal surface in order to setup and run a simulation. For [...]]]></description>
			<content:encoded><![CDATA[<p>Forming simulation software needs a zero thickness sheet for meshing purposes.</p>
<p>Oftentimes, the designer will have an IGES or STEP file of the product data at full material thickness.</p>
<p>We have to perform a step known as &#8220;skinning&#8221; to get just the inside of metal surface in order to setup and run a simulation.</p>
<p>For you AutoForm users, [Disclaimer: I am not affiliated with AutoForm but have used their products] here is a step-by-step simple way to skin your parts.</p>
<p>After importing the product data, with the Geometry Generator open on the Pre tab and look to the &#8220;Define objects&#8221; area:</p>
<ol>
<li>Select &#8220;Face Grouping&#8221;</li>
<li>Select Angle</li>
<li>Click OK</li>
<li>Select all product data</li>
<li>Assign to Deleted</li>
<li>Click Display deleted</li>
<li>Hold the Ctrl key down and select a surface on the master side of material</li>
<li>Click Part</li>
<li>Uncheck the Display deleted box</li>
<li>Click Apply</li>
</ol>
<p>You now have a skinned part!</p>
<p><a href="http://engineering.alltop.com/"><img src="http://badges.alltop.com/images/ka_alltop_170x30.jpg" alt="Alltop, confirmation that I kick ass" width="170" height="30" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2009/10/13/skin-it/stephens/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

