<?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: Preventive Action Request- Ambiguous?  Ever done one?</title>
	<atom:link href="http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/feed/" rel="self" type="application/rss+xml" />
	<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/</link>
	<description>ISO Quality Manuals, Certification, and Consultant Comments</description>
	<lastBuildDate>Thu, 04 Mar 2010 17:01:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chuck</title>
		<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/comment-page-1/#comment-4104</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 21 Oct 2009 08:06:45 +0000</pubDate>
		<guid isPermaLink="false">http://qualitymanualchat.com/uncategorized/preventive-action-request-ambiguous-ever-done-one/84/#comment-4104</guid>
		<description>I work in a very large company and we have a guy pushing that all depts fill out PARs. He is not liked much.</description>
		<content:encoded><![CDATA[<p>I work in a very large company and we have a guy pushing that all depts fill out PARs. He is not liked much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/comment-page-1/#comment-4078</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Tue, 13 Oct 2009 14:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://qualitymanualchat.com/uncategorized/preventive-action-request-ambiguous-ever-done-one/84/#comment-4078</guid>
		<description>We view PARs as opportunities for improvement as well as for preventing mistakes.  For instance, as we added new staff to a department, we discovered a lot of important information had become intuitive to the longer-term staff and, as such, wasn&#039;t recorded anywhere.  A PAR (preventing errors) was written: to formalize and record the experiential knowledge and, as a result training was done to bring all staff to the same level of understanding of the products.  Another instance was to involve all employees (we&#039;re a small company) into the customer service/satisfaction objective; we solicited input on how we could better relate to customer expectations.  That discussion resulted in multiple ideas for improvement, i.e., PARs for more focused customer satisfaction.</description>
		<content:encoded><![CDATA[<p>We view PARs as opportunities for improvement as well as for preventing mistakes.  For instance, as we added new staff to a department, we discovered a lot of important information had become intuitive to the longer-term staff and, as such, wasn&#8217;t recorded anywhere.  A PAR (preventing errors) was written: to formalize and record the experiential knowledge and, as a result training was done to bring all staff to the same level of understanding of the products.  Another instance was to involve all employees (we&#8217;re a small company) into the customer service/satisfaction objective; we solicited input on how we could better relate to customer expectations.  That discussion resulted in multiple ideas for improvement, i.e., PARs for more focused customer satisfaction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edgar Loste</title>
		<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/comment-page-1/#comment-4030</link>
		<dc:creator>Edgar Loste</dc:creator>
		<pubDate>Wed, 30 Sep 2009 06:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://qualitymanualchat.com/uncategorized/preventive-action-request-ambiguous-ever-done-one/84/#comment-4030</guid>
		<description>Preventive action requests are very rare indeed. 
Suggestions to improve processess are potential sources of these requests. Often, the requestor detects potential risks/problems hence the suggestion.</description>
		<content:encoded><![CDATA[<p>Preventive action requests are very rare indeed.<br />
Suggestions to improve processess are potential sources of these requests. Often, the requestor detects potential risks/problems hence the suggestion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Windson</title>
		<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/comment-page-1/#comment-3663</link>
		<dc:creator>Windson</dc:creator>
		<pubDate>Thu, 20 Aug 2009 06:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://qualitymanualchat.com/uncategorized/preventive-action-request-ambiguous-ever-done-one/84/#comment-3663</guid>
		<description>Preventive actions are actions taken based on &quot; potential problems &#039;, such as FMEA. I often confused as well on corrective actions where we taken after a defect is found.
For example, part A has a defect, and corrective actions are taken. 
Part B has the potential of this defect occurrence, Preventive Actions are taken.
So for Part A, what ever actions we are going to take, are deemed as
CORRECTIVE ACTIONS.
This is the what my understanding is, how about your comments ?</description>
		<content:encoded><![CDATA[<p>Preventive actions are actions taken based on &#8221; potential problems &#8216;, such as FMEA. I often confused as well on corrective actions where we taken after a defect is found.<br />
For example, part A has a defect, and corrective actions are taken.<br />
Part B has the potential of this defect occurrence, Preventive Actions are taken.<br />
So for Part A, what ever actions we are going to take, are deemed as<br />
CORRECTIVE ACTIONS.<br />
This is the what my understanding is, how about your comments ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Phillips</title>
		<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/comment-page-1/#comment-1773</link>
		<dc:creator>Michael Phillips</dc:creator>
		<pubDate>Thu, 13 Nov 2008 05:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://qualitymanualchat.com/uncategorized/preventive-action-request-ambiguous-ever-done-one/84/#comment-1773</guid>
		<description>I know what you mean about ambiguity. I have just finished a certification audit and there seems to be a difference in what the standard requires and what the auditor expects to see.</description>
		<content:encoded><![CDATA[<p>I know what you mean about ambiguity. I have just finished a certification audit and there seems to be a difference in what the standard requires and what the auditor expects to see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erin Ward</title>
		<link>http://QualityManualChat.com/general-quality-system/preventive-action-request-ambiguous-ever-done-one/84/comment-page-1/#comment-791</link>
		<dc:creator>Erin Ward</dc:creator>
		<pubDate>Wed, 18 Jun 2008 17:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://qualitymanualchat.com/uncategorized/preventive-action-request-ambiguous-ever-done-one/84/#comment-791</guid>
		<description>Hello, I have noticed that you have not mentioned anything about a gap analysis. I was wondering what your thoughts on GA s are why you have chosen not to include it in your package. How do others feel about this?</description>
		<content:encoded><![CDATA[<p>Hello, I have noticed that you have not mentioned anything about a gap analysis. I was wondering what your thoughts on GA s are why you have chosen not to include it in your package. How do others feel about this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
