<?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: How we can socialize PLM Bill of Materials?</title>
	<atom:link href="http://plmtwine.com/2009/05/06/how-we-can-socialize-plm-bill-of-materials/feed/" rel="self" type="application/rss+xml" />
	<link>http://plmtwine.com/2009/05/06/how-we-can-socialize-plm-bill-of-materials/</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: olegshilovitsky</title>
		<link>http://plmtwine.com/2009/05/06/how-we-can-socialize-plm-bill-of-materials/#comment-6848</link>
		<dc:creator><![CDATA[olegshilovitsky]]></dc:creator>
		<pubDate>Thu, 24 Jun 2010 03:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://olegshilo.wordpress.com/?p=1330#comment-6848</guid>
		<description><![CDATA[Jeff, absolutely! If you are doing it online on the web, I appreciate you put a link on plmtwine.com. Best, Oleg]]></description>
		<content:encoded><![CDATA[<p>Jeff, absolutely! If you are doing it online on the web, I appreciate you put a link on plmtwine.com. Best, Oleg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://plmtwine.com/2009/05/06/how-we-can-socialize-plm-bill-of-materials/#comment-6845</link>
		<dc:creator><![CDATA[Jeff]]></dc:creator>
		<pubDate>Thu, 24 Jun 2010 02:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://olegshilo.wordpress.com/?p=1330#comment-6845</guid>
		<description><![CDATA[Can I use this graphic?

Jeff]]></description>
		<content:encoded><![CDATA[<p>Can I use this graphic?</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: olegshilovitsky</title>
		<link>http://plmtwine.com/2009/05/06/how-we-can-socialize-plm-bill-of-materials/#comment-4523</link>
		<dc:creator><![CDATA[olegshilovitsky]]></dc:creator>
		<pubDate>Fri, 19 Mar 2010 11:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://olegshilo.wordpress.com/?p=1330#comment-4523</guid>
		<description><![CDATA[Paul, Tags are good approach in implementing what I mentioned here - connection between people and BOM. Regardless on the implementation, my point was - links between BOM (elements) and people in the organization is very important. Tags are not good if you try to replace links with them, since they don&#039;t have an ability to represent relationship&#039;s predicates. Tags are more about bottom up classification (opposite to what we can be a taxonomy- classification, we need to define top down). ERP, PDM, PLM systems are based on taxonomies. Folksonomies came from social systems and Web 2.0, but becomes very popular. Some of my thoughts about that -

Social Tagging in PLM - can it work together?
http://plmtwine.com/2010/03/03/social-tagging-and-plm-can-it-work-together/

How Tagging can prevent PLM from a compulsive obsessive disorder problem
http://plmtwine.com/2009/04/09/how-tagging-can-prevent-plm-from-a-compulsive-obsessive-disorder-problem/

Thanks for your comments! Best, Oleg]]></description>
		<content:encoded><![CDATA[<p>Paul, Tags are good approach in implementing what I mentioned here &#8211; connection between people and BOM. Regardless on the implementation, my point was &#8211; links between BOM (elements) and people in the organization is very important. Tags are not good if you try to replace links with them, since they don&#8217;t have an ability to represent relationship&#8217;s predicates. Tags are more about bottom up classification (opposite to what we can be a taxonomy- classification, we need to define top down). ERP, PDM, PLM systems are based on taxonomies. Folksonomies came from social systems and Web 2.0, but becomes very popular. Some of my thoughts about that -</p>
<p>Social Tagging in PLM &#8211; can it work together?<br />
<a href="http://plmtwine.com/2010/03/03/social-tagging-and-plm-can-it-work-together/" rel="nofollow">http://plmtwine.com/2010/03/03/social-tagging-and-plm-can-it-work-together/</a></p>
<p>How Tagging can prevent PLM from a compulsive obsessive disorder problem<br />
<a href="http://plmtwine.com/2009/04/09/how-tagging-can-prevent-plm-from-a-compulsive-obsessive-disorder-problem/" rel="nofollow">http://plmtwine.com/2009/04/09/how-tagging-can-prevent-plm-from-a-compulsive-obsessive-disorder-problem/</a></p>
<p>Thanks for your comments! Best, Oleg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://plmtwine.com/2009/05/06/how-we-can-socialize-plm-bill-of-materials/#comment-4508</link>
		<dc:creator><![CDATA[Paul]]></dc:creator>
		<pubDate>Thu, 18 Mar 2010 20:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://olegshilo.wordpress.com/?p=1330#comment-4508</guid>
		<description><![CDATA[I think this is an interesting approach.  A colleague used to say &#039;we should have a &#039;cloud&#039; of bits and tag them with (eg) x,y,z, position, BoM position, Material etc.  i.e. stop relying on the structure as this can (by definition) only really work in one direction.

I suppose the thing here is that one set of relationships is the master - i.e. only one set of tags identifies the &#039;design&#039;, every other set is a &#039;view&#039; but not the official &#039;view&#039;.  The other complexity is where to put attributes that traditionally live on a relationship - if I define a BoM with tags, where do I put part quantity per parent? for example.  I do think that with complex tags it must be possible, but wonder whether it just moves the problem (multi-BoM reconciliation to multi-tag reconciliation) or improves the situation?

Paul]]></description>
		<content:encoded><![CDATA[<p>I think this is an interesting approach.  A colleague used to say &#8216;we should have a &#8216;cloud&#8217; of bits and tag them with (eg) x,y,z, position, BoM position, Material etc.  i.e. stop relying on the structure as this can (by definition) only really work in one direction.</p>
<p>I suppose the thing here is that one set of relationships is the master &#8211; i.e. only one set of tags identifies the &#8216;design&#8217;, every other set is a &#8216;view&#8217; but not the official &#8216;view&#8217;.  The other complexity is where to put attributes that traditionally live on a relationship &#8211; if I define a BoM with tags, where do I put part quantity per parent? for example.  I do think that with complex tags it must be possible, but wonder whether it just moves the problem (multi-BoM reconciliation to multi-tag reconciliation) or improves the situation?</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>

