<?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; process</title>
	<atom:link href="http://www.dieguy.com/tag/process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dieguy.com</link>
	<description>Official Tim Stephens Website</description>
	<lastBuildDate>Tue, 07 Feb 2012 02:27:11 +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>Writing Galore</title>
		<link>http://www.dieguy.com/2011/01/22/writing-galore/stephens/</link>
		<comments>http://www.dieguy.com/2011/01/22/writing-galore/stephens/#comments</comments>
		<pubDate>Sat, 22 Jan 2011 13:38:55 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[About]]></category>
		<category><![CDATA[Engineering Decisions]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[calculation]]></category>
		<category><![CDATA[die design]]></category>
		<category><![CDATA[die guy]]></category>
		<category><![CDATA[die standards]]></category>
		<category><![CDATA[equation]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[quoting]]></category>
		<category><![CDATA[waiting]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=906</guid>
		<description><![CDATA[Just a quick note to say hello to all the Die Guys out there! All evidence to the contrary, I have started writing again. I teamed up with my pal Lou Kren to collaborate on an article for one of his ventures. I am my toughest critic &#8211; but I am very pleased with my [...]]]></description>
			<content:encoded><![CDATA[<p>Just a quick note to say hello to all the Die Guys out there!</p>
<p>All evidence to the contrary, I have started writing again. I teamed up with my pal Lou Kren to collaborate on an article for one of his ventures. I am my toughest critic &#8211; but I am very pleased with my work with Lou.</p>
<p>I also have no less than 5 book concepts in the works. At the rate I am going, it will take a couple years to get it all out there &#8211; but am close to getting the first one going. It will most likely be an engineering calculations-focused book.</p>
<p>I feel good overall &#8211; and I genuinely believe I am doing my best work ever.</p>
<p>That said, did you know that Vince Lombardi prepared his entire career to be a head coach? And no less than 20 years into his journey, he finally got the opportunity with the Green Bay Packers and helped put the NFL on the map. [my prediction is they will be in this year's Superbowl and walk away with the Lombardi trophy]</p>
<p>We are approaching the 25 year mark on my career. Does my dream job of building a championship-caliber die engineering and build team with owning the quoting method and die standards lurk on the horizon?</p>
<p>If I had THAT opportunity, the possibilities are boundless. I foresee a reversal of work going overseas back to my hometown with the right die engineering and build processes with my brand of modern die standards to guide the efforts.</p>
<p>I do not know if 2011 is my year or not, but I know this: I am having fun right now.</p>
<p><a href="http://engineering.alltop.com/"><img src="http://badges.alltop.com/images/alltop_170x30_bribes.jpg" alt="Alltop. Bribes work." width="170" height="30" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2011/01/22/writing-galore/stephens/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Overboard</title>
		<link>http://www.dieguy.com/2010/09/22/overboard/stephens/</link>
		<comments>http://www.dieguy.com/2010/09/22/overboard/stephens/#comments</comments>
		<pubDate>Wed, 22 Sep 2010 11:42:01 +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[feasibility]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[manufacturing]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[quoting]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=886</guid>
		<description><![CDATA[The curse of technical people, I am convinced, is they are too technical in situations where detail does not matter. They have an obsession with covering every minute detail when a high level concept is all that is needed. Case in point: advanced feasibility of metal stampings. Here is a situation where the product geometry, [...]]]></description>
			<content:encoded><![CDATA[<p>The curse of technical people, I am convinced, is they are too technical in situations where detail does not matter. They have an obsession with covering every minute detail when a high level concept is all that is needed.</p>
<p>Case in point: advanced feasibility of metal stampings.</p>
<p>Here is a situation where the product geometry, material type, and material thickness is far from frozen. &#8220;Frozen&#8221; is an automotive term for final designs that are released for production. Final, in this market, means &#8220;design intent will most likely change unless hell freezes over&#8221;.</p>
<p>At this point in the product development process, someone somewhere is simply looking for feasibility. Not validation.</p>
<p>The formability and proposed process is all we are looking for here. Is it a crash form or a form or a multi-stage draw?</p>
<p>Will it run in a progressive die or transfer?</p>
<p>Hell, even a rough blank size and budgetary tool cost may be required as well. Rough does not mean down to two place decimals on dimensions. Budgetary does not mean down to plus or minus 2 cents.</p>
<p>And that is my two cents: getting down to the level of detail of sourcing blank suppliers, getting 57 people to sign-off on a process that stands a 90% chance of never turning into a job for a product design that stands a 99.9% chance changing somehow someway to make all the advanced work a complete waste of time.</p>
<p>Focus on what matters. Don&#8217;t go overboard.</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/09/22/overboard/stephens/feed/</wfw:commentRss>
		<slash:comments>4</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>Another Strike</title>
		<link>http://www.dieguy.com/2010/05/22/another-strike/stephens/</link>
		<comments>http://www.dieguy.com/2010/05/22/another-strike/stephens/#comments</comments>
		<pubDate>Sat, 22 May 2010 15:03:36 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[Engineering Decisions]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[cafe]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[restrike]]></category>
		<category><![CDATA[variation]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=785</guid>
		<description><![CDATA[The discussion on the validity of restrike dies continues with a comment from Eric Kam that I would like to post here instead of comments due to length: It seems to me that the reason that the restrike is more appealing and rational than the trim line correction&#8230; by creating an adjustment point closer to the [...]]]></description>
			<content:encoded><![CDATA[<p>The discussion on the <a href="http://www.dieguy.com/2010/05/18/strike-the-restrike/stephens/" target="_self">validity of restrike dies</a> continues with a comment from Eric Kam that I would like to post here instead of comments due to length:</p>
<p style="padding-left: 30px"><em>It seems to me that the reason that the restrike is more appealing and rational than the trim line correction&#8230;</em></p>
<p style="padding-left: 30px"><em>by creating an adjustment point closer to the final destination (the conveyor belts and the racks) they are able to affect the &#8220;illusion&#8221; of control over some of the variation. To address the initial form or flange die may require the definition of a different tip angle, or inclusion of a CAM that was not originally part of that planned operation. Additionally, fudging a &#8220;calibration&#8221; hit or tweaking the restrike may have far less negative impact on the overall behavior of the panel.</em></p>
<p style="padding-left: 30px"><em>I am not defending it, but I can see the safety-blanket-like appeal of using the purpose-built restrike die as a control point. A tool that if the attempt at re-cutting or shimming or welding up or just plain hard hitting the tool away from original design intent will not have as broad or potentially negative impact on larger portions of the product. severely mess with the restrike and you are not messing with the product.</em></p>
<p style="padding-left: 30px"><em>Similar to the concept of double draw beads used in large panel draws. We know that square lock beads can effectively lock out all material flow, and that grinding on those square beads can affect all gradients of restraint until the bead is gone. However, we still see double draw beads and the significantly larger blanks that they require in production. Why? Because if I have to make adjustments to the material flow, it feels like we can safely grind and weld on one of the two drawbeads without drastically altering the die. While grinding on the ONLY drawbead feels more risky.</em></p>
<p style="padding-left: 30px"><em>Rational yes, but still an illusion of control.</em></p>
<p style="padding-left: 30px"><em>What folks need to be able to do more effectively during their engineering of the PROCESS and all the tools in the entire process, is to meaningfully evaluate not just what the die does in the best/worst/nominal cases that they might be simulating as their standard. But they need to consider what happens when the world changes slightly around them-as it will. In springback there is no Best or Worst case.</em></p>
<p style="padding-left: 30px"><em>Different is Different. And when it comes to springback any difference can end up being wrong. The restrike die just gives us one more bite at the apple to fix what we could not stabilize in the initial hit and when it appears to fix the problem at buy-off via tweaking, it actually becomes a bit of a self-fulfilling prophecy. We will prove by having it that we needed it. Vicious cycle, the only good news is that we might get paid to make the restrike die, so I don&#8217;t foresee the world doing away with them.</em></p>
<p>Good points, Eric. But with Obama now wanting more aggressive CAFE standards in the next 20 years, the only profitable way to stamp automotive vehicles is to get away from the unnecessary bells and whistles like restrike dies and just-in-case cam operations.</p>
<p><img src="http://badges.alltop.com/images/alltop_170x30_bribes.jpg" alt="Alltop. Bribes work." width="170" height="30" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2010/05/22/another-strike/stephens/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Costing is not Quoting</title>
		<link>http://www.dieguy.com/2009/10/04/costing-is-not-quoting/stephens/</link>
		<comments>http://www.dieguy.com/2009/10/04/costing-is-not-quoting/stephens/#comments</comments>
		<pubDate>Sun, 04 Oct 2009 16:34:54 +0000</pubDate>
		<dc:creator>stephens</dc:creator>
				<category><![CDATA[Automated Transactions]]></category>
		<category><![CDATA[Engineering Decisions]]></category>
		<category><![CDATA[costing]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[quoting]]></category>

		<guid isPermaLink="false">http://www.dieguy.com/?p=342</guid>
		<description><![CDATA[There has been much discussion on the web lately about quoting and costing software for stamping dies. Costing is not quoting. The calculated or estimated cost has no practical relation to the quoted price for two reasons. First, the price that will win the work relies exclusively on what the customer is willing to pay. [...]]]></description>
			<content:encoded><![CDATA[<p>There has been much discussion on the web lately about quoting and costing software for stamping dies.</p>
<p>Costing is not quoting.</p>
<p>The calculated or estimated cost has no practical relation to the quoted price for two reasons.</p>
<p>First, the price that will win the work relies exclusively on what the customer is willing to pay. End of story.</p>
<p>The customer does not care that it will cost the die shop $500,000 USD to build if they are willing to pay only $400,000 USD for the job.</p>
<p>Even if your costing software is accurate to +/-0.005%, a cost of anything over $400,000 USD is a loser.</p>
<p>Second, most die shops have no real clue as to what their geniune costs are. At the quoting level, it is guesswork.</p>
<p>At the historical level, the data is usually poorly tracked, collected, and reconciled. The historical data should be the baseline for future work. Without this important data, all decisions moving forward are simply guesses.</p>
<p>Again, even if the historical data was valid and the costing method &#8211; software or otherwise &#8211; was accurate, the only thing that matters is quoting the maximum that the customer is willing to pay and work like the devil to reduce costs once the quote becomes an order.</p>
<p><a href="http://my.alltop.com/speedraft/"><img src="http://badges.alltop.com/images/myalltop_visit_170x30.gif" alt="Visit MyAlltop Page" width="170" height="30" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dieguy.com/2009/10/04/costing-is-not-quoting/stephens/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

