<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How To Successfully Implement SolidWorks 2009</title>
	<atom:link href="http://rocksolidperspective.com/2008/09/24/how-to-successfully-implement-solidworks-2009/feed/" rel="self" type="application/rss+xml" />
	<link>http://rocksolidperspective.com/2008/09/24/how-to-successfully-implement-solidworks-2009/</link>
	<description></description>
	<lastBuildDate>Tue, 20 Sep 2011 20:27:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Paul Kellner</title>
		<link>http://rocksolidperspective.com/2008/09/24/how-to-successfully-implement-solidworks-2009/#comment-454</link>
		<dc:creator><![CDATA[Paul Kellner]]></dc:creator>
		<pubDate>Thu, 12 Mar 2009 15:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://rocksolidperspective.com/2008/09/24/how-to-successfully-implement-solidworks-2009/#comment-454</guid>
		<description><![CDATA[This is a fleshing out of someting that was mentioned in a CAD Manager Boot Camp a while back. 

One of the first steps I take in upgrading SW from one release to the next is to determine the benefit and cost.

Benefits can be new features that are sorely needed, bug fixes, or customer or vendor demands for an upgrade. A lesser reason might be to accommodate further purchase of SW seats. 

Costs include possible performance hits, retraining, necessity of upgrading hardware (video card compatibility or cpu power), the cost of redeployment, testing, rewriting macros or programs, upgrading 3rd party software and the cost of converting files from one version to the next which can be difficult when using PDM. 

In any event I usually try to delay changing to the next version till the end of the release to avoid having to install multiple service packs.]]></description>
		<content:encoded><![CDATA[<p>This is a fleshing out of someting that was mentioned in a CAD Manager Boot Camp a while back. </p>
<p>One of the first steps I take in upgrading SW from one release to the next is to determine the benefit and cost.</p>
<p>Benefits can be new features that are sorely needed, bug fixes, or customer or vendor demands for an upgrade. A lesser reason might be to accommodate further purchase of SW seats. </p>
<p>Costs include possible performance hits, retraining, necessity of upgrading hardware (video card compatibility or cpu power), the cost of redeployment, testing, rewriting macros or programs, upgrading 3rd party software and the cost of converting files from one version to the next which can be difficult when using PDM. </p>
<p>In any event I usually try to delay changing to the next version till the end of the release to avoid having to install multiple service packs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

