<?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: Why NX CAD?</title>
	<atom:link href="http://plmexchange.net/why-nx-cad/feed/" rel="self" type="application/rss+xml" />
	<link>http://plmexchange.net/why-nx-cad/</link>
	<description>NX, Teamcenter, and the PLM Market</description>
	<lastBuildDate>Fri, 16 Jul 2010 00:12:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Tony</title>
		<link>http://plmexchange.net/why-nx-cad/comment-page-1/#comment-1410</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Thu, 15 Jul 2010 23:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=282#comment-1410</guid>
		<description>I&#039;ve used Autodesk Inventor versions 11 (2006) to 2010, Solid Works 2006, and NX 5 and 7. I think you&#039;re right that NX is the &quot;best of the best&quot;, but in my opinion it&#039;s mainly in features. I&#039;ll mainly comment on Autodesk Inventor. Compared to NX, Inventor has fewer features (e.g. no complex surfacing like x-form, or capabilities for very large, multi-user, multi-platform assemblies). However, while they lack features, I think they&#039;re trying to make up in UI. As of 2009 they switched to a ribbon interface such as the one used in Microsoft Office 2007. It came as a surprise to me and I think for a lot of people as well, but after giving it a few days to set in - I think they&#039;re targeting novice users rather than trying to displace NX, Pro-E, or Catia.

I would imagine that the ribbon design would be a lot easier to learn than the rather lengthy file menus, and while the novice users go through college, Autodesk could slowly build up its features until Inventor could match NX. By then they&#039;d have both the incoming body of designers and the features to compete with NX, Catia, and Pro-E.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used Autodesk Inventor versions 11 (2006) to 2010, Solid Works 2006, and NX 5 and 7. I think you&#8217;re right that NX is the &#8220;best of the best&#8221;, but in my opinion it&#8217;s mainly in features. I&#8217;ll mainly comment on Autodesk Inventor. Compared to NX, Inventor has fewer features (e.g. no complex surfacing like x-form, or capabilities for very large, multi-user, multi-platform assemblies). However, while they lack features, I think they&#8217;re trying to make up in UI. As of 2009 they switched to a ribbon interface such as the one used in Microsoft Office 2007. It came as a surprise to me and I think for a lot of people as well, but after giving it a few days to set in &#8211; I think they&#8217;re targeting novice users rather than trying to displace NX, Pro-E, or Catia.</p>
<p>I would imagine that the ribbon design would be a lot easier to learn than the rather lengthy file menus, and while the novice users go through college, Autodesk could slowly build up its features until Inventor could match NX. By then they&#8217;d have both the incoming body of designers and the features to compete with NX, Catia, and Pro-E.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tolsnet</title>
		<link>http://plmexchange.net/why-nx-cad/comment-page-1/#comment-1258</link>
		<dc:creator>tolsnet</dc:creator>
		<pubDate>Sun, 03 Jan 2010 20:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=282#comment-1258</guid>
		<description>NX vs AutoCad... NX is a high end 3D modeling package, with many supporting applications such as manufacturing, analysis, motion, assemblies, plus a powerful programming infrastructure. 
 
NX vs SolidWorks... NX has a strong expression engine to build engineering constraints and logic into the application, a leader in 3D surfacing, large assemblies, and the other features in the NX vs AutoCad section 
 
NX vs ProEngineer... The differences here are smaller. The 3D engine (parasolid) that NX uses has more 3rd party support, is more widely used because it is a licensed 3D engine. The UX in NX is modern and fundamentally works different. NX has action object as well as object action for flexibility on how the model is constructed. NX has essentially one file extension for all types of files (except for analysis/motion files), which allows more flexibility. Also the file structure is different. ProE has a internals to the file that can make it more difficult to understand and looses flexibility when trying to reuse files. 
 
These are my opinions and observations, I&#039;m sure many have their preferences to CAD systems that sway their prejudice.  </description>
		<content:encoded><![CDATA[<p>NX vs AutoCad&#8230; NX is a high end 3D modeling package, with many supporting applications such as manufacturing, analysis, motion, assemblies, plus a powerful programming infrastructure. </p>
<p>NX vs SolidWorks&#8230; NX has a strong expression engine to build engineering constraints and logic into the application, a leader in 3D surfacing, large assemblies, and the other features in the NX vs AutoCad section </p>
<p>NX vs ProEngineer&#8230; The differences here are smaller. The 3D engine (parasolid) that NX uses has more 3rd party support, is more widely used because it is a licensed 3D engine. The UX in NX is modern and fundamentally works different. NX has action object as well as object action for flexibility on how the model is constructed. NX has essentially one file extension for all types of files (except for analysis/motion files), which allows more flexibility. Also the file structure is different. ProE has a internals to the file that can make it more difficult to understand and looses flexibility when trying to reuse files. </p>
<p>These are my opinions and observations, I&#39;m sure many have their preferences to CAD systems that sway their prejudice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tolsnet</title>
		<link>http://plmexchange.net/why-nx-cad/comment-page-1/#comment-1259</link>
		<dc:creator>tolsnet</dc:creator>
		<pubDate>Sun, 03 Jan 2010 20:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=282#comment-1259</guid>
		<description>NX vs AutoCad... NX is a high end 3D modeling package, with many supporting applications such as manufacturing, analysis, motion, assemblies, plus a powerful programming infrastructure. 
 
NX vs SolidWorks... NX has a strong expression engine to build engineering constraints and logic into the application, a leader in 3D surfacing, large assemblies, and the other features in the NX vs AutoCad section 
 
NX vs ProEngineer... The differences here are smaller. The 3D engine (parasolid) that NX uses has more 3rd party support, is more widely used because it is a licensed 3D engine. The UX in NX is modern and fundamentally works different. NX has action object as well as object action for flexibility on how the model is constructed. NX has essentially one file extension for all types of files (except for analysis/motion files), which allows more flexibility. Also the file structure is different. ProE has a internals to the file that can make it more difficult to understand and looses flexibility when trying to reuse files. 
 
These are my opinions and observations, I&#039;m sure many have their preferences to CAD systems that sway their prejudice.  </description>
		<content:encoded><![CDATA[<p>NX vs AutoCad&#8230; NX is a high end 3D modeling package, with many supporting applications such as manufacturing, analysis, motion, assemblies, plus a powerful programming infrastructure. </p>
<p>NX vs SolidWorks&#8230; NX has a strong expression engine to build engineering constraints and logic into the application, a leader in 3D surfacing, large assemblies, and the other features in the NX vs AutoCad section </p>
<p>NX vs ProEngineer&#8230; The differences here are smaller. The 3D engine (parasolid) that NX uses has more 3rd party support, is more widely used because it is a licensed 3D engine. The UX in NX is modern and fundamentally works different. NX has action object as well as object action for flexibility on how the model is constructed. NX has essentially one file extension for all types of files (except for analysis/motion files), which allows more flexibility. Also the file structure is different. ProE has a internals to the file that can make it more difficult to understand and looses flexibility when trying to reuse files. </p>
<p>These are my opinions and observations, I&#39;m sure many have their preferences to CAD systems that sway their prejudice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: harinder</title>
		<link>http://plmexchange.net/why-nx-cad/comment-page-1/#comment-1257</link>
		<dc:creator>harinder</dc:creator>
		<pubDate>Sun, 03 Jan 2010 18:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=282#comment-1257</guid>
		<description>Please can anyone give me the list in which NX give more productivity  than other 
 1.NX vs Autocad  
2. NX vs SW 
3. NX vs Proeng </description>
		<content:encoded><![CDATA[<p>Please can anyone give me the list in which NX give more productivity  than other<br />
 1.NX vs Autocad<br />
2. NX vs SW<br />
3. NX vs Proeng</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: harinder</title>
		<link>http://plmexchange.net/why-nx-cad/comment-page-1/#comment-1251</link>
		<dc:creator>harinder</dc:creator>
		<pubDate>Sun, 22 Nov 2009 12:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=282#comment-1251</guid>
		<description>tell me in surfacing which is good solidworks or solidedge? </description>
		<content:encoded><![CDATA[<p>tell me in surfacing which is good solidworks or solidedge?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chriskelley.org &#187; Blog Archive &#187; PLMexchange: Why NX CAD</title>
		<link>http://plmexchange.net/why-nx-cad/comment-page-1/#comment-19</link>
		<dc:creator>chriskelley.org &#187; Blog Archive &#187; PLMexchange: Why NX CAD</dc:creator>
		<pubDate>Wed, 13 Sep 2006 17:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=282#comment-19</guid>
		<description>[...] Why NX CAD? [...]</description>
		<content:encoded><![CDATA[<p>[...] Why NX CAD? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
