<?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: First &#8220;T&#8221; of CAD &#8211; Tools</title>
	<atom:link href="http://www.caddmanager.com/CMB/2008/08/four-ts-of-cad-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.caddmanager.com/CMB/2008/08/four-ts-of-cad-tools/</link>
	<description>Practical, proven insight into CADD Management from Mark W. Kiker</description>
	<lastBuildDate>Wed, 08 Feb 2012 05:07:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Person</title>
		<link>http://www.caddmanager.com/CMB/2008/08/four-ts-of-cad-tools/comment-page-1/#comment-890</link>
		<dc:creator>John Person</dc:creator>
		<pubDate>Tue, 02 Sep 2008 19:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.caddmanager.com/CMB/?p=645#comment-890</guid>
		<description>Ryan makes a great point. Integration with your existing systems are important. Even if you intend to upgrade your platforms in the near future, changes in plans could make your recent purchase obsolete or unusable.

I try to make sure that the tools are or have been upgraded to follow the upcoming changes of software platforms they will be used on.

One other aspect that merits mentioning is &#039;Learning Curve&#039; and &#039;Acceptability&#039;. Even the best tools are useless if your users can&#039;t or worse, won&#039;t use them.

When looking for a new apps/ tools, I ask myself one questions and categorize the tool in one of two lists. &quot;Does this tool do something new or does it do something better?&quot;

Depending on which, I gear my training differently (but I&#039;ll comment on that one later)


(*Great Blog by the way, Mark.)</description>
		<content:encoded><![CDATA[<p>Ryan makes a great point. Integration with your existing systems are important. Even if you intend to upgrade your platforms in the near future, changes in plans could make your recent purchase obsolete or unusable.</p>
<p>I try to make sure that the tools are or have been upgraded to follow the upcoming changes of software platforms they will be used on.</p>
<p>One other aspect that merits mentioning is &#8216;Learning Curve&#8217; and &#8216;Acceptability&#8217;. Even the best tools are useless if your users can&#8217;t or worse, won&#8217;t use them.</p>
<p>When looking for a new apps/ tools, I ask myself one questions and categorize the tool in one of two lists. &#8220;Does this tool do something new or does it do something better?&#8221;</p>
<p>Depending on which, I gear my training differently (but I&#8217;ll comment on that one later)</p>
<p>(*Great Blog by the way, Mark.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan McVay</title>
		<link>http://www.caddmanager.com/CMB/2008/08/four-ts-of-cad-tools/comment-page-1/#comment-859</link>
		<dc:creator>Ryan McVay</dc:creator>
		<pubDate>Tue, 26 Aug 2008 22:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.caddmanager.com/CMB/?p=645#comment-859</guid>
		<description>When it comes to software tool choices I tend to value how the tool intergrates with the other systems in the company as a high priority: I will look at MES and ERP first. Creating data silo&#039;s that can&#039;t be leveraged by others is not a good thing. 

If that is not an issue, than I take a good hard look/guess at the future to see if scalablity is going to be an issue. Are we planning on opening plants/offices in different area and how will those be supported? (i.e. multi-site server and licenses, vars or direct support)

Finally, I look to see what type of product we build and determine some of the key functionalities based on geometry type and assembly sizes.</description>
		<content:encoded><![CDATA[<p>When it comes to software tool choices I tend to value how the tool intergrates with the other systems in the company as a high priority: I will look at MES and ERP first. Creating data silo&#8217;s that can&#8217;t be leveraged by others is not a good thing. </p>
<p>If that is not an issue, than I take a good hard look/guess at the future to see if scalablity is going to be an issue. Are we planning on opening plants/offices in different area and how will those be supported? (i.e. multi-site server and licenses, vars or direct support)</p>
<p>Finally, I look to see what type of product we build and determine some of the key functionalities based on geometry type and assembly sizes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

