<?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"
	>
<channel>
	<title>Comments on: MES Requirements, MES Selection</title>
	<atom:link href="http://manufit.com/2008/04/09/mes-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://manufit.com/2008/04/09/mes-requirements/</link>
	<description>The best and worst of manufacturing and information technology</description>
	<pubDate>Fri, 21 Nov 2008 06:25:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Scott Whitlock</title>
		<link>http://manufit.com/2008/04/09/mes-requirements/#comment-302</link>
		<dc:creator>Scott Whitlock</dc:creator>
		<pubDate>Mon, 28 Apr 2008 12:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://manufit.com/2008/04/09/mes-requirements/#comment-302</guid>
		<description>Shripad,
Thanks for the comment.  You are right, this is always the hard part.  Fortunately, there are some standards that are starting to define the transactions, terminology, etc. for this interaction.  Have you heard of the ISA S95 standard?

These standards will help the larger companies where the lines of demarcation between systems can be drawn with a little more certainty.  In most companies, the rationalization between systems, master data, etc. is very difficult.

Perhaps it would be a good exercise for me to define what the best practices are in this area and make that available on the blog.

Thanks again.
-scott</description>
		<content:encoded><![CDATA[<p>Shripad,<br />
Thanks for the comment.  You are right, this is always the hard part.  Fortunately, there are some standards that are starting to define the transactions, terminology, etc. for this interaction.  Have you heard of the ISA S95 standard?</p>
<p>These standards will help the larger companies where the lines of demarcation between systems can be drawn with a little more certainty.  In most companies, the rationalization between systems, master data, etc. is very difficult.</p>
<p>Perhaps it would be a good exercise for me to define what the best practices are in this area and make that available on the blog.</p>
<p>Thanks again.<br />
-scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shripad Lale</title>
		<link>http://manufit.com/2008/04/09/mes-requirements/#comment-301</link>
		<dc:creator>Shripad Lale</dc:creator>
		<pubDate>Sat, 26 Apr 2008 01:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://manufit.com/2008/04/09/mes-requirements/#comment-301</guid>
		<description>I totally agree. But things are probably worse. When a family goes to a builder and says, "5 Bedrooms, 4 Full Baths,...", there is an implicit understanding of what a 'Bedroom' and 'Bath' means, what it is supposed to do and what not. Unfortunately in the MES domain, the boundary line between MES and ERP itself is fuzzy, and I have seen customers wanting to implement a specific funcationality, which I thought would be ERP's business, in MES, and vice versa. So, it would be good to hear your thoughts on how organizations should partition their functionality between MES and ERP. We call this 'application rationalization'. Deciding what to put in which bucket. In fact, in my opinion, this decision is perhaps the greatest influencer in selecting the right MES!</description>
		<content:encoded><![CDATA[<p>I totally agree. But things are probably worse. When a family goes to a builder and says, &#8220;5 Bedrooms, 4 Full Baths,&#8230;&#8221;, there is an implicit understanding of what a &#8216;Bedroom&#8217; and &#8216;Bath&#8217; means, what it is supposed to do and what not. Unfortunately in the MES domain, the boundary line between MES and ERP itself is fuzzy, and I have seen customers wanting to implement a specific funcationality, which I thought would be ERP&#8217;s business, in MES, and vice versa. So, it would be good to hear your thoughts on how organizations should partition their functionality between MES and ERP. We call this &#8216;application rationalization&#8217;. Deciding what to put in which bucket. In fact, in my opinion, this decision is perhaps the greatest influencer in selecting the right MES!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
