<?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: One-to-One: Dassault Strives to Make 3D Accessible to All in the SMB with V6</title>
	<atom:link href="http://tech-clarity.com/clarityonplm/2009/one-to-one-dassault-strives-to-make-3d-accessible-to-all-in-the-smb-with-v6/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech-clarity.com/clarityonplm/2009/one-to-one-dassault-strives-to-make-3d-accessible-to-all-in-the-smb-with-v6/</link>
	<description>Clarity on software for innovation, product development, engineering, and manufacturing</description>
	<lastBuildDate>Mon, 30 Aug 2010 12:29:00 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Jonathan Scott</title>
		<link>http://tech-clarity.com/clarityonplm/2009/one-to-one-dassault-strives-to-make-3d-accessible-to-all-in-the-smb-with-v6/comment-page-1/#comment-121</link>
		<dc:creator>Jonathan Scott</dc:creator>
		<pubDate>Tue, 14 Jul 2009 15:59:28 +0000</pubDate>
		<guid isPermaLink="false">http://tech-clarity.com/clarityonplm/?p=310#comment-121</guid>
		<description>I agree with your comments that change is certainly difficult, and even more so when people lose their jobs.  I too hope that the people at SmarTeam that were let go are able to find new opportunities - they are a VERY talented development group.

That being said, I think the consolidated V6 approach is a good and healthy one for Dassault.  To be able to take the best of SmarTeam, VPLM, and MatrixOne, at some point they needed to centralize development.  The good news is that it sounds like V6 is still going to have VPLM, MatrixOne, and SmarTeam DNA baked in, even if those old product brands eventually die.

The other detail that seems to be overlooked in some of the discussion about this is how V5 is being affected.  Since V5 is by no means a dead platform (we hear that development will continue for several years), it is important to mention this.  As far as I can tell, V5 development is still right on track, and driven by the same team in Israel.

We&#039;ve had our own conversations with some folks at Dassault about this topic, and hopefully you&#039;ll find some other useful information here: http://www.razorleaf.com/2009/07/enovia-changes/</description>
		<content:encoded><![CDATA[<p>I agree with your comments that change is certainly difficult, and even more so when people lose their jobs.  I too hope that the people at SmarTeam that were let go are able to find new opportunities &#8211; they are a VERY talented development group.</p>
<p>That being said, I think the consolidated V6 approach is a good and healthy one for Dassault.  To be able to take the best of SmarTeam, VPLM, and MatrixOne, at some point they needed to centralize development.  The good news is that it sounds like V6 is still going to have VPLM, MatrixOne, and SmarTeam DNA baked in, even if those old product brands eventually die.</p>
<p>The other detail that seems to be overlooked in some of the discussion about this is how V5 is being affected.  Since V5 is by no means a dead platform (we hear that development will continue for several years), it is important to mention this.  As far as I can tell, V5 development is still right on track, and driven by the same team in Israel.</p>
<p>We&#8217;ve had our own conversations with some folks at Dassault about this topic, and hopefully you&#8217;ll find some other useful information here: <a href="http://www.razorleaf.com/2009/07/enovia-changes/" rel="nofollow">http://www.razorleaf.com/2009/07/enovia-changes/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jim.brown</title>
		<link>http://tech-clarity.com/clarityonplm/2009/one-to-one-dassault-strives-to-make-3d-accessible-to-all-in-the-smb-with-v6/comment-page-1/#comment-120</link>
		<dc:creator>jim.brown</dc:creator>
		<pubDate>Tue, 14 Jul 2009 15:36:27 +0000</pubDate>
		<guid isPermaLink="false">http://tech-clarity.com/clarityonplm/?p=310#comment-120</guid>
		<description>Just responded to some comments on my Manufacturing Business Technology blog on this same topic. I will summarize here, but to read the full discussion thread please visit the post on MBT at: http://www.mbtmag.com/blog/PLM_and_Profitability/18613-One_to_One_Dassault_Strives_to_Make_3D_Accessible_to_All_in_the_SMB_with_V6.php.

In short, an ex-SmarTeam employee was informing me that the SmarTeam product is being discontinued. In response, a Dassault representative responded with his perspective on why SmarTeam lives on. I won&#039;t try to recreate their words here, but let me share my response with you:

Thank you for the inside story and for the updates. I have always had a lot of respect for SmarTeam (the people and the product) and felt it served a very good purpose by providing a strong, supply-chain-oriented PLM offering. This was true in the small to mid-sized businesses, but also for some larger businesses. But I also understand the need for Dassault to move toward a common solution. This is the reality of the software business. I am hopeful that the SmarTeam employees find new opportunities quickly. My true hope is that they will create new, innovative solutions that extend the offerings of the larger PLM vendors in new, interesting, and valuable areas. For SmarTeam customers, I hope that those that choose to transition will find the transition a positive one. I wish them the best, change is never easy. I also hope that Dassault will make the customer transition as painless as they can, by supporting V5 and helping customers transition to V6 if they choose to. Dassault would do well to keep those customers happy and in the Dassault customer family. This day had to come, I hope that everyone involved can make the best out of it.</description>
		<content:encoded><![CDATA[<p>Just responded to some comments on my Manufacturing Business Technology blog on this same topic. I will summarize here, but to read the full discussion thread please visit the post on MBT at: <a href="http://www.mbtmag.com/blog/PLM_and_Profitability/18613-One_to_One_Dassault_Strives_to_Make_3D_Accessible_to_All_in_the_SMB_with_V6.php" rel="nofollow">http://www.mbtmag.com/blog/PLM_and_Profitability/18613-One_to_One_Dassault_Strives_to_Make_3D_Accessible_to_All_in_the_SMB_with_V6.php</a>.</p>
<p>In short, an ex-SmarTeam employee was informing me that the SmarTeam product is being discontinued. In response, a Dassault representative responded with his perspective on why SmarTeam lives on. I won&#8217;t try to recreate their words here, but let me share my response with you:</p>
<p>Thank you for the inside story and for the updates. I have always had a lot of respect for SmarTeam (the people and the product) and felt it served a very good purpose by providing a strong, supply-chain-oriented PLM offering. This was true in the small to mid-sized businesses, but also for some larger businesses. But I also understand the need for Dassault to move toward a common solution. This is the reality of the software business. I am hopeful that the SmarTeam employees find new opportunities quickly. My true hope is that they will create new, innovative solutions that extend the offerings of the larger PLM vendors in new, interesting, and valuable areas. For SmarTeam customers, I hope that those that choose to transition will find the transition a positive one. I wish them the best, change is never easy. I also hope that Dassault will make the customer transition as painless as they can, by supporting V5 and helping customers transition to V6 if they choose to. Dassault would do well to keep those customers happy and in the Dassault customer family. This day had to come, I hope that everyone involved can make the best out of it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
