<?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: Large Monolithic PLM Implementations Are a Thing of the Past</title>
	<atom:link href="http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/feed/" rel="self" type="application/rss+xml" />
	<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/</link>
	<description>Product Lifecycle Management by Oleg Shilovitsky</description>
	<lastBuildDate>Tue, 14 Feb 2012 21:57:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Social Intranet and PLM Apps &#171; Daily PLM Think Tank Blog</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-9652</link>
		<dc:creator><![CDATA[Social Intranet and PLM Apps &#171; Daily PLM Think Tank Blog]]></dc:creator>
		<pubDate>Mon, 01 Nov 2010 15:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-9652</guid>
		<description><![CDATA[[...] In my view, the key word here is &quot;disintegration&quot;. Opposite to a very strong trend of vertical integration, disintegration will introduce social identity and related to these standards like OpenSocial as a mechanism to break enterprise product suites into Enterprise App Stores. I think, we are in the early beginning of this process. However, enterprise company are starting to get this point. For most of them today, is just an understanding of the fact Large Monolithic PLM Implementations are A Thing of the Past. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] In my view, the key word here is &quot;disintegration&quot;. Opposite to a very strong trend of vertical integration, disintegration will introduce social identity and related to these standards like OpenSocial as a mechanism to break enterprise product suites into Enterprise App Stores. I think, we are in the early beginning of this process. However, enterprise company are starting to get this point. For most of them today, is just an understanding of the fact Large Monolithic PLM Implementations are A Thing of the Past. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Social Intranet and PLM Apps</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-9651</link>
		<dc:creator><![CDATA[Social Intranet and PLM Apps]]></dc:creator>
		<pubDate>Mon, 01 Nov 2010 15:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-9651</guid>
		<description><![CDATA[[...] In my view, the key word here is &#8220;disintegration&#8221;. Opposite to a very strong trend of vertical integration, disintegration will introduce social identity and related to these standards like OpenSocial as a mechanism to break enterprise product suites into Enterprise App Stores. I think, we are in the early beginning of this process. However, enterprise company are starting to get this point. For most of them today, is just an understanding of the fact Large Monolithic PLM Implementations are A Thing of the Past. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] In my view, the key word here is &#8220;disintegration&#8221;. Opposite to a very strong trend of vertical integration, disintegration will introduce social identity and related to these standards like OpenSocial as a mechanism to break enterprise product suites into Enterprise App Stores. I think, we are in the early beginning of this process. However, enterprise company are starting to get this point. For most of them today, is just an understanding of the fact Large Monolithic PLM Implementations are A Thing of the Past. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: olegshilovitsky</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-6129</link>
		<dc:creator><![CDATA[olegshilovitsky]]></dc:creator>
		<pubDate>Wed, 26 May 2010 15:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-6129</guid>
		<description><![CDATA[Raj,  Thanks for your comment! I think, ERP apps won&#039;t be monolithic too. However, the basis of ERP is much stronger (from $$$). So, for big company the lifespan of ERP apps can be 10-15 years. Therefore, wait 4-5 more years and you&#039;ll hear lots of companies splitting there ERP implementations on services. Smaller customers will be the first segment to experience this change. Just my thoughts...Oleg]]></description>
		<content:encoded><![CDATA[<p>Raj,  Thanks for your comment! I think, ERP apps won&#8217;t be monolithic too. However, the basis of ERP is much stronger (from $$$). So, for big company the lifespan of ERP apps can be 10-15 years. Therefore, wait 4-5 more years and you&#8217;ll hear lots of companies splitting there ERP implementations on services. Smaller customers will be the first segment to experience this change. Just my thoughts&#8230;Oleg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raj</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-6103</link>
		<dc:creator><![CDATA[Raj]]></dc:creator>
		<pubDate>Tue, 25 May 2010 16:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-6103</guid>
		<description><![CDATA[So, Oleg, why does this not apply to ERP systems? ERP implementations are monlithic...]]></description>
		<content:encoded><![CDATA[<p>So, Oleg, why does this not apply to ERP systems? ERP implementations are monlithic&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mid-market PLM: Smashed Or Transformed? &#171; Daily PLM Think Tank Blog</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-4858</link>
		<dc:creator><![CDATA[Mid-market PLM: Smashed Or Transformed? &#171; Daily PLM Think Tank Blog]]></dc:creator>
		<pubDate>Mon, 05 Apr 2010 14:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-4858</guid>
		<description><![CDATA[[...] this word. For me, it means first of all precision and understanding. As I mentioned few months ago, large monolithic PLM implementations are a thing in the past. To find PLM solution for smaller customers will require to go and understand what these customers [...]]]></description>
		<content:encoded><![CDATA[<p>[...] this word. For me, it means first of all precision and understanding. As I mentioned few months ago, large monolithic PLM implementations are a thing in the past. To find PLM solution for smaller customers will require to go and understand what these customers [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: olegshilovitsky</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-3494</link>
		<dc:creator><![CDATA[olegshilovitsky]]></dc:creator>
		<pubDate>Tue, 05 Jan 2010 09:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-3494</guid>
		<description><![CDATA[Cam, thank you for your comment and sharing of experience with Agile. If I understand correctly, you increased functionality of implementation within the time. I&#039;ve seen it in many successful implementations with different products. Normally, it shows rational approach and good balancing between goals and system capabilities. The key for me in such implementation always was &quot;cost of change&quot;. If you can keep the cost of change &quot;low&quot;, you will be successful with software/system you are going to implement. Best, Oleg]]></description>
		<content:encoded><![CDATA[<p>Cam, thank you for your comment and sharing of experience with Agile. If I understand correctly, you increased functionality of implementation within the time. I&#8217;ve seen it in many successful implementations with different products. Normally, it shows rational approach and good balancing between goals and system capabilities. The key for me in such implementation always was &#8220;cost of change&#8221;. If you can keep the cost of change &#8220;low&#8221;, you will be successful with software/system you are going to implement. Best, Oleg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cam Bickel</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-3490</link>
		<dc:creator><![CDATA[Cam Bickel]]></dc:creator>
		<pubDate>Mon, 04 Jan 2010 19:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-3490</guid>
		<description><![CDATA[I would take a bit of exception to some of the statements above.  We implemented Agile in one week - initially using only as a PDM system.  This was 10 years ago and before much of the function was added through version upgrades. Yet we still started with using a fraction of the capabilities available at the time.  It was certainly easier to evolve with the package than to be exposed to an overwhelming set of decisions - but I think with the right guidance you could start off small and use the pre-configured settings to begin.  With a few exceptions we have not had problems changing our mind on the configuration over time - the flexibility of the package has allowed us to expand it&#039;s use and change our processes without a lot of pain.  Eventually we got into some customization to optimize some processes but there is a lot you can do with just configuration before you get to this point.

I agree about data being a disaster in companies with a lot of history, especially acquired IP.  I think the best approach is to avoid massive clean up before you implement.  Decide which data attributes are fundamental and focus only on these.  You can then get value from PLM earlier and use the categorization capabilities of PLM to manage further clean up activities.  You may find a lot of the dirty data is no longer active and can be left alone.

Conclusion is to find a configurable package and start using it to get your BOMs and Drawings and change process under control and then expand from there.

Also, we did not have any problem with moving from our paper change form to the out of the box electronic version - we just did it.]]></description>
		<content:encoded><![CDATA[<p>I would take a bit of exception to some of the statements above.  We implemented Agile in one week &#8211; initially using only as a PDM system.  This was 10 years ago and before much of the function was added through version upgrades. Yet we still started with using a fraction of the capabilities available at the time.  It was certainly easier to evolve with the package than to be exposed to an overwhelming set of decisions &#8211; but I think with the right guidance you could start off small and use the pre-configured settings to begin.  With a few exceptions we have not had problems changing our mind on the configuration over time &#8211; the flexibility of the package has allowed us to expand it&#8217;s use and change our processes without a lot of pain.  Eventually we got into some customization to optimize some processes but there is a lot you can do with just configuration before you get to this point.</p>
<p>I agree about data being a disaster in companies with a lot of history, especially acquired IP.  I think the best approach is to avoid massive clean up before you implement.  Decide which data attributes are fundamental and focus only on these.  You can then get value from PLM earlier and use the categorization capabilities of PLM to manage further clean up activities.  You may find a lot of the dirty data is no longer active and can be left alone.</p>
<p>Conclusion is to find a configurable package and start using it to get your BOMs and Drawings and change process under control and then expand from there.</p>
<p>Also, we did not have any problem with moving from our paper change form to the out of the box electronic version &#8211; we just did it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: olegshilovitsky</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-3459</link>
		<dc:creator><![CDATA[olegshilovitsky]]></dc:creator>
		<pubDate>Sun, 03 Jan 2010 11:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-3459</guid>
		<description><![CDATA[Andy, Thanks! I agree with you about flexibility. Over-flexibility as well as complete out-of-the-box vertical solution is both dangerous for the company as a source of wasted time and resources. In my view, open source (or free) solution like Innovator can solve the problem of high risk. You emphasized it  by saying &quot;you don&#039;t waste several million dollars&quot;. By saying - no license fees, organization is getting lower entry barrier. It will be very interesting to see the evolution of this business model and impact of software development in the enterprises... Best, Oleg]]></description>
		<content:encoded><![CDATA[<p>Andy, Thanks! I agree with you about flexibility. Over-flexibility as well as complete out-of-the-box vertical solution is both dangerous for the company as a source of wasted time and resources. In my view, open source (or free) solution like Innovator can solve the problem of high risk. You emphasized it  by saying &#8220;you don&#8217;t waste several million dollars&#8221;. By saying &#8211; no license fees, organization is getting lower entry barrier. It will be very interesting to see the evolution of this business model and impact of software development in the enterprises&#8230; Best, Oleg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AndyF</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-3450</link>
		<dc:creator><![CDATA[AndyF]]></dc:creator>
		<pubDate>Thu, 31 Dec 2009 21:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-3450</guid>
		<description><![CDATA[While there are lots of application building software that can be used to solve various PLM problems, Innovator is the best one we&#039;ve ever seen.  The trick with Innovator is that it has so much pre-built functionality.  The pre-built functions can be quickly assembled to solve most any data management problem.  The fact that the software is free is a very nice bonus but the functionality is what is important.

Of course, a person needs to be careful with so much flexibility.  If you aren&#039;t careful you can build something that works just as bad as a monolithic PLM system from a major vendor.  Of course since the Innovator package is free you&#039;ll only have wasted your time and not several million dollars.]]></description>
		<content:encoded><![CDATA[<p>While there are lots of application building software that can be used to solve various PLM problems, Innovator is the best one we&#8217;ve ever seen.  The trick with Innovator is that it has so much pre-built functionality.  The pre-built functions can be quickly assembled to solve most any data management problem.  The fact that the software is free is a very nice bonus but the functionality is what is important.</p>
<p>Of course, a person needs to be careful with so much flexibility.  If you aren&#8217;t careful you can build something that works just as bad as a monolithic PLM system from a major vendor.  Of course since the Innovator package is free you&#8217;ll only have wasted your time and not several million dollars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: olegshilovitsky</title>
		<link>http://plmtwine.com/2009/12/20/large-monolithic-plm-implementations-are-a-thing-of-the-past/#comment-3444</link>
		<dc:creator><![CDATA[olegshilovitsky]]></dc:creator>
		<pubDate>Wed, 30 Dec 2009 20:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://plmtwine.com/?p=3850#comment-3444</guid>
		<description><![CDATA[Andy, Thank you for your comment! Let me ask you provocative question. I had chance to see the similar situation (translate a business requirements in flexible PDM/PLM model) with other tools (not Aras). And it works... It is always based on skills and good project organization. Is there something specific in Aras Innovator that helps or this is just a notion of &quot;free tool&quot;? Best, Oleg]]></description>
		<content:encoded><![CDATA[<p>Andy, Thank you for your comment! Let me ask you provocative question. I had chance to see the similar situation (translate a business requirements in flexible PDM/PLM model) with other tools (not Aras). And it works&#8230; It is always based on skills and good project organization. Is there something specific in Aras Innovator that helps or this is just a notion of &#8220;free tool&#8221;? Best, Oleg</p>
]]></content:encoded>
	</item>
</channel>
</rss>

