<?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 for Get Savvy about PLM</title>
	<atom:link href="http://plmsavvy.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://plmsavvy.org</link>
	<description>Product Lifecycle Management without the vendor hype</description>
	<lastBuildDate>Fri, 26 Feb 2010 22:26:58 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Fundamentals of PLM Seminar Video by Samantha</title>
		<link>http://plmsavvy.org/2009/11/18/fundamentals-of-plm-seminar-video/#comment-745</link>
		<dc:creator>Samantha</dc:creator>
		<pubDate>Fri, 26 Feb 2010 22:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.org/?p=80#comment-745</guid>
		<description>Thanks for sharing! I just finished watching the seminar online and it&#039;s really thorough.  
I hope you&#039;ll be back online and blogging again soon!

Samantha
Datastay Corp.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing! I just finished watching the seminar online and it&#8217;s really thorough.<br />
I hope you&#8217;ll be back online and blogging again soon!</p>
<p>Samantha<br />
Datastay Corp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fundamentals of PLM Seminar Video by jiting</title>
		<link>http://plmsavvy.org/2009/11/18/fundamentals-of-plm-seminar-video/#comment-711</link>
		<dc:creator>jiting</dc:creator>
		<pubDate>Thu, 07 Jan 2010 06:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.org/?p=80#comment-711</guid>
		<description>The seminar was really amazing. We learned a lot of PLM knowledge. Thank you very much! Happy new year to you!</description>
		<content:encoded><![CDATA[<p>The seminar was really amazing. We learned a lot of PLM knowledge. Thank you very much! Happy new year to you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Part Numbering Conundrum by Steve</title>
		<link>http://plmsavvy.org/2007/04/04/the-part-numbering-conundrum/#comment-690</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 19 Nov 2009 19:44:26 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.org/2007/04/04/the-part-numbering-conundrum/#comment-690</guid>
		<description>Like many others, we ran into the same problem in trying to decide on using significant or non-significant part numbers. There are pros and cons to each, and as a very small business we were more worried about what was happening today. While we didn&#039;t want to paint ourselves into a corner ten years from now when/if we got to be a big company, we finally decided that was our biggest concern.

We finally ended up deciding on the part numbering service from part-numbering.com (http://www.part-numbering.com). It let us set up our significant numbering formats with a shared sequence across all of our number formats. Our hope is that when we get big, or the &quot;significant&quot; format becomes to much burden to support, we can just switch over to a non-significant format. Since all of our part numbers are drawing from the same sequence, they&#039;ll already be unique across all formats. So the conversion should be a snap (we hope).

Cheers,
Steve</description>
		<content:encoded><![CDATA[<p>Like many others, we ran into the same problem in trying to decide on using significant or non-significant part numbers. There are pros and cons to each, and as a very small business we were more worried about what was happening today. While we didn&#8217;t want to paint ourselves into a corner ten years from now when/if we got to be a big company, we finally decided that was our biggest concern.</p>
<p>We finally ended up deciding on the part numbering service from part-numbering.com (<a href="http://www.part-numbering.com" rel="nofollow">http://www.part-numbering.com</a>). It let us set up our significant numbering formats with a shared sequence across all of our number formats. Our hope is that when we get big, or the &#8220;significant&#8221; format becomes to much burden to support, we can just switch over to a non-significant format. Since all of our part numbers are drawing from the same sequence, they&#8217;ll already be unique across all formats. So the conversion should be a snap (we hope).</p>
<p>Cheers,<br />
Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The importance of a long term roadmap for PLM by Matt</title>
		<link>http://plmsavvy.org/2008/07/11/the-importance-of-a-long-term-roadmap-for-plm/#comment-676</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 24 Oct 2009 18:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.wordpress.com/?p=44#comment-676</guid>
		<description>Meant to add question mark to above?</description>
		<content:encoded><![CDATA[<p>Meant to add question mark to above?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The importance of a long term roadmap for PLM by Matt Brosious</title>
		<link>http://plmsavvy.org/2008/07/11/the-importance-of-a-long-term-roadmap-for-plm/#comment-675</link>
		<dc:creator>Matt Brosious</dc:creator>
		<pubDate>Sat, 24 Oct 2009 18:47:29 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.wordpress.com/?p=44#comment-675</guid>
		<description>Do you think intergated PLM, sourcing and ERP should be part of the roadmap.</description>
		<content:encoded><![CDATA[<p>Do you think intergated PLM, sourcing and ERP should be part of the roadmap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should your PLM system live on Oracle or MS SQL? by Hoda</title>
		<link>http://plmsavvy.org/2007/01/18/should-your-plm-system-live-on-oracle-or-ms-sql/#comment-449</link>
		<dc:creator>Hoda</dc:creator>
		<pubDate>Tue, 12 May 2009 09:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.org/2007/01/18/should-your-plm-system-live-on-oracle-or-ms-sql/#comment-449</guid>
		<description>Hello,

There is an issue which has taken my mind. I have understood that for a company on the PLM road and freshly started its investigations and requirement specifications for PDM system, it is necessary to make sure that every other department which has process or data interface with the product development department (such as customer relationship dep. or service/support dep.) use compatible and integratable systems for their information/document managemenet system.

The question is, when deciding about system vendors, what are the key features to be considered to make sure of no miss-match between the selected PDM system and a document management systems used in another department? .... especially if the other departments are on instant need to buy a software for their own web-based document management needs, before the final decision for PDM system selection is made. Should they really wait until the whole PLM architecture is defined? or am I totally having a wrong approach toward this issue?

(Hope I have expressed myself clearly!)  


I really would be glad to have your opinion abou it. 


Best Regards,

~Hoda</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>There is an issue which has taken my mind. I have understood that for a company on the PLM road and freshly started its investigations and requirement specifications for PDM system, it is necessary to make sure that every other department which has process or data interface with the product development department (such as customer relationship dep. or service/support dep.) use compatible and integratable systems for their information/document managemenet system.</p>
<p>The question is, when deciding about system vendors, what are the key features to be considered to make sure of no miss-match between the selected PDM system and a document management systems used in another department? &#8230;. especially if the other departments are on instant need to buy a software for their own web-based document management needs, before the final decision for PDM system selection is made. Should they really wait until the whole PLM architecture is defined? or am I totally having a wrong approach toward this issue?</p>
<p>(Hope I have expressed myself clearly!)  </p>
<p>I really would be glad to have your opinion abou it. </p>
<p>Best Regards,</p>
<p>~Hoda</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The importance of a long term roadmap for PLM by Phillip K</title>
		<link>http://plmsavvy.org/2008/07/11/the-importance-of-a-long-term-roadmap-for-plm/#comment-444</link>
		<dc:creator>Phillip K</dc:creator>
		<pubDate>Fri, 08 May 2009 14:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.wordpress.com/?p=44#comment-444</guid>
		<description>Good article, most don’t understand the need for a sustained roadmap and building up a resistance to allowing individuals that want to go “off-road” to speed up the process.  
I agree with Laila, it is a good point Chris.  As far as implementing features, it gets back to the focus of the article…the need for a roadmap.  Ideally, the roadmap would include a roll out with the Product Development teams in addition to the change management process.  The initial focus on change management serves several areas.  First, it affects more users on the system from the beginning so the effects are more apparent.  There are many organizations that have separate departments or teams that work independent of the main stream.  Therefore, if the only starting point were with PD team, the initial impact in this case would be small and take a long time for the downstream users to see the effects until the project matured.  Secondly, many projects need to show early benefits for the users and stakeholders.  By having more users, the project should see a larger positive effect and enable the project managers of the system to show cost and time benefits to the stakeholders.    Assuming a good rollout, the excitement generated by a good rollout is infectious and will win over the users that are initially resistant to the change.  Most importantly, to the long term health of the project, is giving back the investment to the stakeholders quickly or they will lose interest and allow the project to die.</description>
		<content:encoded><![CDATA[<p>Good article, most don’t understand the need for a sustained roadmap and building up a resistance to allowing individuals that want to go “off-road” to speed up the process.<br />
I agree with Laila, it is a good point Chris.  As far as implementing features, it gets back to the focus of the article…the need for a roadmap.  Ideally, the roadmap would include a roll out with the Product Development teams in addition to the change management process.  The initial focus on change management serves several areas.  First, it affects more users on the system from the beginning so the effects are more apparent.  There are many organizations that have separate departments or teams that work independent of the main stream.  Therefore, if the only starting point were with PD team, the initial impact in this case would be small and take a long time for the downstream users to see the effects until the project matured.  Secondly, many projects need to show early benefits for the users and stakeholders.  By having more users, the project should see a larger positive effect and enable the project managers of the system to show cost and time benefits to the stakeholders.    Assuming a good rollout, the excitement generated by a good rollout is infectious and will win over the users that are initially resistant to the change.  Most importantly, to the long term health of the project, is giving back the investment to the stakeholders quickly or they will lose interest and allow the project to die.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 18.5% improvement in profit margins with PLM? Sign me up! by Jim Brown</title>
		<link>http://plmsavvy.org/2008/11/26/185-improvement-in-profit-margins-with-plm-sign-me-up/#comment-425</link>
		<dc:creator>Jim Brown</dc:creator>
		<pubDate>Tue, 24 Mar 2009 19:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.wordpress.com/?p=49#comment-425</guid>
		<description>Leila,
I just stumbled across your blog and read your post. I used to lead Aberdeen&#039;s PLM practice, and one of the things I really enjoyed was being able to see what the best manufacturers are doing differently from the rest. I look forward to staying in touch with your blog. I try to share some PLM research in my blog at www.mbtmag.com/plmblog. Some of it is Aberdeen&#039;s, some of it from my company (Tech-Clarity), and some from others. I look forward to sharing information with you moving forward.
Best,
Jim</description>
		<content:encoded><![CDATA[<p>Leila,<br />
I just stumbled across your blog and read your post. I used to lead Aberdeen&#8217;s PLM practice, and one of the things I really enjoyed was being able to see what the best manufacturers are doing differently from the rest. I look forward to staying in touch with your blog. I try to share some PLM research in my blog at <a href="http://www.mbtmag.com/plmblog" rel="nofollow">http://www.mbtmag.com/plmblog</a>. Some of it is Aberdeen&#8217;s, some of it from my company (Tech-Clarity), and some from others. I look forward to sharing information with you moving forward.<br />
Best,<br />
Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PLM Glossary by Laila Hirr</title>
		<link>http://plmsavvy.org/plm-glossary/#comment-421</link>
		<dc:creator>Laila Hirr</dc:creator>
		<pubDate>Thu, 12 Mar 2009 20:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.wordpress.com/plm-glossary/#comment-421</guid>
		<description>Thanks for the suggestions.  I made the addition you requested for the glossary and already have ideas formulating on what to share regarding implementations.  I-deas/NX migrations are vendor specific which I prefer to avoid on this blog however would be happy to discuss it with you directly. I&#039;ll send you a note with my contact information.</description>
		<content:encoded><![CDATA[<p>Thanks for the suggestions.  I made the addition you requested for the glossary and already have ideas formulating on what to share regarding implementations.  I-deas/NX migrations are vendor specific which I prefer to avoid on this blog however would be happy to discuss it with you directly. I&#8217;ll send you a note with my contact information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PLM Glossary by icconian</title>
		<link>http://plmsavvy.org/plm-glossary/#comment-420</link>
		<dc:creator>icconian</dc:creator>
		<pubDate>Thu, 12 Mar 2009 13:47:38 +0000</pubDate>
		<guid isPermaLink="false">http://plmsavvy.wordpress.com/plm-glossary/#comment-420</guid>
		<description>Laila, could you please add SMB to your glossary? Your Nov 08 blog referred to SMBs, but I don&#039;t have a clue. Interesting read, anyway.
Any more stories from the front lines of PLM implementation that you could share with us? Any thoughts on I-DEAS/NX to TeamCenter?</description>
		<content:encoded><![CDATA[<p>Laila, could you please add SMB to your glossary? Your Nov 08 blog referred to SMBs, but I don&#8217;t have a clue. Interesting read, anyway.<br />
Any more stories from the front lines of PLM implementation that you could share with us? Any thoughts on I-DEAS/NX to TeamCenter?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
