<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: GR&amp;R as it applies to ECD products – OvenCHECKER™, OvenRIDER®, WaveRIDER® and MEGARIDER®</title>
	<atom:link href="http://www.ecd.com/blog/index.php/2009/11/06/grr-as-it-applies-to-ecd-products-ovenchecker-ovenrider-waverider-and-megarider/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ecd.com/blog/index.php/2009/11/06/grr-as-it-applies-to-ecd-products-ovenchecker-ovenrider-waverider-and-megarider/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=grr-as-it-applies-to-ecd-products-ovenchecker-ovenrider-waverider-and-megarider</link>
	<description></description>
	<lastBuildDate>Sat, 05 Nov 2011 07:47:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Paul Austen</title>
		<link>http://www.ecd.com/blog/index.php/2009/11/06/grr-as-it-applies-to-ecd-products-ovenchecker-ovenrider-waverider-and-megarider/comment-page-1/#comment-116</link>
		<dc:creator>Paul Austen</dc:creator>
		<pubDate>Mon, 26 Jul 2010 22:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.ecd.com/blog/index.php/2009/11/06/grr-as-it-applies-to-ecd-products-%e2%80%93-ovenchecker%e2%84%a2-ovenrider%c2%ae-waverider%c2%ae-and-megarider%e2%84%a2/#comment-116</guid>
		<description>Rip;

I agree in general.

So the result would be a GR study (so to speak) and not a hard core GR&amp;R, which we are often asked to provide. I maintain “we” cannot do a GR&amp;R (or GR) for someone because it is not a “specification” we can add to the data sheet but rather a study only “they” can do using our tool, their ovens and their personal, and maybe a good consultant like yourself. And even when they take the time to do it, the results, as you say, will be one “R” short of a GR&amp;R :-) 

PA</description>
		<content:encoded><![CDATA[<p>Rip;</p>
<p>I agree in general.</p>
<p>So the result would be a GR study (so to speak) and not a hard core GR&amp;R, which we are often asked to provide. I maintain “we” cannot do a GR&amp;R (or GR) for someone because it is not a “specification” we can add to the data sheet but rather a study only “they” can do using our tool, their ovens and their personal, and maybe a good consultant like yourself. And even when they take the time to do it, the results, as you say, will be one “R” short of a GR&amp;R <img src='http://www.ecd.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </p>
<p>PA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rip Stauffer</title>
		<link>http://www.ecd.com/blog/index.php/2009/11/06/grr-as-it-applies-to-ecd-products-ovenchecker-ovenrider-waverider-and-megarider/comment-page-1/#comment-114</link>
		<dc:creator>Rip Stauffer</dc:creator>
		<pubDate>Sun, 11 Jul 2010 17:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.ecd.com/blog/index.php/2009/11/06/grr-as-it-applies-to-ecd-products-%e2%80%93-ovenchecker%e2%84%a2-ovenrider%c2%ae-waverider%c2%ae-and-megarider%e2%84%a2/#comment-114</guid>
		<description>Interesting article. One thing to note: this is accurate insofar as it pertains to crossed studies (depicted in your form and description). When doing studies with unique parts or destructive testing, you don&#039;t do a crossed study; you do a nested study. In that study, reproducibility is not assessed, only repeatability.</description>
		<content:encoded><![CDATA[<p>Interesting article. One thing to note: this is accurate insofar as it pertains to crossed studies (depicted in your form and description). When doing studies with unique parts or destructive testing, you don&#8217;t do a crossed study; you do a nested study. In that study, reproducibility is not assessed, only repeatability.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

