<?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: Brittle Applications</title>
	<atom:link href="http://blog.b2banalysts.com/2009/08/31/brittle-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.b2banalysts.com/2009/08/31/brittle-applications/</link>
	<description>Radical views on the enterprise application industry</description>
	<lastBuildDate>Sat, 11 Dec 2010 20:27:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: toppundit</title>
		<link>http://blog.b2banalysts.com/2009/08/31/brittle-applications/#comment-90</link>
		<dc:creator><![CDATA[toppundit]]></dc:creator>
		<pubDate>Thu, 10 Sep 2009 01:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.b2banalysts.com/?p=181#comment-90</guid>
		<description><![CDATA[Thanks for the challenging comment.

I agree, there&#039;s nothing surprising about the fact that it takes a lot to make MRP work. APICS says this. I say this. You say it.  We&#039;re all right.  

I am simply asking, &quot;Is all that effort worth it, for most companies, most of the time,&quot; and my tentative answer is, &quot;No.&quot;  Why do I say that? Because I&#039;ve been to a lot of companies and looked at their installations, and it&#039;s been clear that that&#039;s what they decided.  

I doubt that APICS comes to the same conclusion; I really do. 

What are alternatives?  Nothing very profound.  In my experience, Kanban is a simpler and less brittle way replenishment strategy. Flow manufacturing is very powerful for certain kinds of production.  In most manufacturing organizations, process improvement and redesign (focused on making replenishment more effective and demand-sensitive) is probably easier and more reliable than putting in a computer system.  

I also think that many companies might well want to use advanced supply chain optimization packages for managing key processes or key inventory items and using more simple-minded, but reliable processes (like Kanban) for everything else.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the challenging comment.</p>
<p>I agree, there&#8217;s nothing surprising about the fact that it takes a lot to make MRP work. APICS says this. I say this. You say it.  We&#8217;re all right.  </p>
<p>I am simply asking, &#8220;Is all that effort worth it, for most companies, most of the time,&#8221; and my tentative answer is, &#8220;No.&#8221;  Why do I say that? Because I&#8217;ve been to a lot of companies and looked at their installations, and it&#8217;s been clear that that&#8217;s what they decided.  </p>
<p>I doubt that APICS comes to the same conclusion; I really do. </p>
<p>What are alternatives?  Nothing very profound.  In my experience, Kanban is a simpler and less brittle way replenishment strategy. Flow manufacturing is very powerful for certain kinds of production.  In most manufacturing organizations, process improvement and redesign (focused on making replenishment more effective and demand-sensitive) is probably easier and more reliable than putting in a computer system.  </p>
<p>I also think that many companies might well want to use advanced supply chain optimization packages for managing key processes or key inventory items and using more simple-minded, but reliable processes (like Kanban) for everything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Jones</title>
		<link>http://blog.b2banalysts.com/2009/08/31/brittle-applications/#comment-89</link>
		<dc:creator><![CDATA[Greg Jones]]></dc:creator>
		<pubDate>Tue, 08 Sep 2009 03:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.b2banalysts.com/?p=181#comment-89</guid>
		<description><![CDATA[I&#039;m skeptical.  I can&#039;t see anything in your post that wasn&#039;t already touched upon by the APICS study material I&#039;ve looked at.  

The points are valid enough, but not particularly new or revolutionary.  The core data has to be right.  Stable demand works better.  And peole are loathe to do the extra work to get there.  

So what other options are there?  If MRP systems are middle-aged apps, what newer apps exist?  What replaces or reinvigorates MRP systems?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m skeptical.  I can&#8217;t see anything in your post that wasn&#8217;t already touched upon by the APICS study material I&#8217;ve looked at.  </p>
<p>The points are valid enough, but not particularly new or revolutionary.  The core data has to be right.  Stable demand works better.  And peole are loathe to do the extra work to get there.  </p>
<p>So what other options are there?  If MRP systems are middle-aged apps, what newer apps exist?  What replaces or reinvigorates MRP systems?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darrel Miller</title>
		<link>http://blog.b2banalysts.com/2009/08/31/brittle-applications/#comment-87</link>
		<dc:creator><![CDATA[Darrel Miller]]></dc:creator>
		<pubDate>Tue, 01 Sep 2009 01:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.b2banalysts.com/?p=181#comment-87</guid>
		<description><![CDATA[I think one of the reasons that ERP systems are becoming brittle is because they are trying to achieve the wrong goal.  Too often I hear the phrase  &quot;the system should not let the user do X&quot;.  I see products being turned into giant employee babysitting services.   Task based UIs guide employees down the predefined sequence of steps to accomplish the required task.  Users are blocked from using their judgement in edge cases by limits and constraints decided business analysts and accountants.  

It is not surprising that users don&#039;t want to use the system, and that they bypass it when they can, invalidating any statistical analysis because so much stuff happens off the books.  

For a company with high-turnover and one that values low cost workers, I can see the advantage of an ERP product that keeps its users on the rails.

But that should not be the goal of an ERP product.  In my high school math class we were warned about the evils of using a calculator.  If you don&#039;t understand the math, then the answer could be completely wrong and you may not know it.  But in the hands of a professional a calculator can be a formidable tool.

ERP software should be about augmenting the capability of your employees.  It should provide them with accurate information to allow them to make smart decisions, faster.  It should not try and hold their hands, limit their control or obstruct them in any way.

With this perspective, an ERP system has to be flexible enough to accommodate whatever the user wants to do, and just because the system let them do it does not absolve the user of that responsibility.  That would be like telling my math teacher that my calculator came up with the wrong answer.]]></description>
		<content:encoded><![CDATA[<p>I think one of the reasons that ERP systems are becoming brittle is because they are trying to achieve the wrong goal.  Too often I hear the phrase  &#8220;the system should not let the user do X&#8221;.  I see products being turned into giant employee babysitting services.   Task based UIs guide employees down the predefined sequence of steps to accomplish the required task.  Users are blocked from using their judgement in edge cases by limits and constraints decided business analysts and accountants.  </p>
<p>It is not surprising that users don&#8217;t want to use the system, and that they bypass it when they can, invalidating any statistical analysis because so much stuff happens off the books.  </p>
<p>For a company with high-turnover and one that values low cost workers, I can see the advantage of an ERP product that keeps its users on the rails.</p>
<p>But that should not be the goal of an ERP product.  In my high school math class we were warned about the evils of using a calculator.  If you don&#8217;t understand the math, then the answer could be completely wrong and you may not know it.  But in the hands of a professional a calculator can be a formidable tool.</p>
<p>ERP software should be about augmenting the capability of your employees.  It should provide them with accurate information to allow them to make smart decisions, faster.  It should not try and hold their hands, limit their control or obstruct them in any way.</p>
<p>With this perspective, an ERP system has to be flexible enough to accommodate whatever the user wants to do, and just because the system let them do it does not absolve the user of that responsibility.  That would be like telling my math teacher that my calculator came up with the wrong answer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

