<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Agility by Design - an Oracle E-Business Suite Blog and Technical Tips &#187; Blogs</title>
	<atom:link href="http://www.eprentise.com/agilitybydesign/category/blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eprentise.com/agilitybydesign</link>
	<description>an eprentise weblog featuring Articles and Technical Tips on Oracle E-Business Suite.</description>
	<lastBuildDate>Wed, 21 Jul 2010 21:12:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Not Your Mother&#8217;s Software</title>
		<link>http://www.eprentise.com/agilitybydesign/2009/09/241/</link>
		<comments>http://www.eprentise.com/agilitybydesign/2009/09/241/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 12:39:04 +0000</pubDate>
		<dc:creator>Helene Abrams</dc:creator>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Data Quality]]></category>
		<category><![CDATA[Data Systems]]></category>
		<category><![CDATA[The Changing Enterprise]]></category>
		<category><![CDATA[Upgrade vs. Reimplementation]]></category>
		<category><![CDATA[ERP]]></category>
		<category><![CDATA[spreadsheets]]></category>

		<guid isPermaLink="false">http://www.eprentise.com/agilitybydesign/?p=241</guid>
		<description><![CDATA[Some of you might be too young to remember - it used to be that the reconciliation and monthly closings were done on a hand-written ledger, and every adjustment was done in pencil so it could be changed.  If an account needed to be changed, it was changed only on a going-forward basis with possibly a [...]]]></description>
			<content:encoded><![CDATA[<p>Some of you might be too young to remember - it used to be that the reconciliation and monthly closings were done on a hand-written ledger, and every adjustment was done in pencil so it could be changed.  If an account needed to be changed, it was changed only on a going-forward basis with possibly a restatement and a single entry to reflect the change.  Then there came the spreadsheet &#8211; and there was a lot of resistance from the accountants to adopting spreadsheets as the standard.</p>
<p>Still, with spreadsheets, there was no clear drill down process.  Further, as organizations grew and required maintaining thousands of spreadsheets rather than a few, the accuracy and integrity of the data became questionable, and for good reason.  Now, the ERP system has taken away some of the burden of manual reconciliation and spreadsheets, but even large ERP systems don&#8217;t reflect the fact that companies change.  There are countless places that are touched when making changes in a relational database, and it is difficult to perform all of the changes required to maintain the relational integrity of the underlying structures that were initially set up.  But it is also difficult and time-consuming to re-implement or reconcile, or to migrate to a new chart of accounts, a new organization unit, or a new ledger and go through a complete test cycle every time a company reorganizes, acquires another company, or sells part of the business (or, if they have just outgrown their current system).  That difficulty, along with the deterioration of data integrity that results from companies having to resort to thousands of spreadsheets to reconcile the changes, doesn&#8217;t make a manual process any more accurate or auditable, and it severely limits a company&#8217;s agility.</p>
<p><a href="http://www.eprentise.com/software/" target="_blank">eprentise</a> and <a href="http://www.eprentise.com/flexfield/" target="_blank">FlexField</a> software products deal with the technical aspects of the change so that EBS can re-align to the current business environment.  The ability to change is now part of the normal lifecycle and ongoing maintenance of an enterprise application.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eprentise.com/agilitybydesign/2009/09/241/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Lean to Win with Speed in the Global Marketplace</title>
		<link>http://www.eprentise.com/agilitybydesign/2009/07/using-lean-to-win-with-speed-in-the-global-marketplace/</link>
		<comments>http://www.eprentise.com/agilitybydesign/2009/07/using-lean-to-win-with-speed-in-the-global-marketplace/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 19:10:53 +0000</pubDate>
		<dc:creator>Mike Liddell</dc:creator>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[TECHANGES]]></category>
		<category><![CDATA[The Changing Enterprise]]></category>
		<category><![CDATA[Trends & Technology]]></category>

		<guid isPermaLink="false">http://www.eprentise.com/agilitybydesign/?p=210</guid>
		<description><![CDATA[Enterprise Resource Planning (ERP) systems such as Oracle’s E-Business Suite have advantages over legacy systems in that they allow businesses to be more flexible and agile.  This article focuses on the concept of Lean Manufacturing, but the value of modern ERP systems is a far-reaching and evident in many industries.
Manufacturers in North America and Europe [...]]]></description>
			<content:encoded><![CDATA[<p><em>Enterprise Resource Planning (ERP) systems such as Oracle’s E-Business Suite have advantages over legacy systems in that they allow businesses to be more flexible and agile.  This article focuses on the concept of Lean Manufacturing, but the value of modern ERP systems is a far-reaching and evident in many industries.</em></p>
<p>Manufacturers in North America and Europe are struggling to meet the challenges of a stressed economy. The good news is that the coming recovery is expected to see early signs of a sharp increase in demand for steel because the street thinks that the steel industry will be among those to lead us out of the recession.</p>
<p><a rel="attachment wp-att-215" href="http://www.eprentise.com/agilitybydesign/?attachment_id=215"><img class="size-full wp-image-215 alignleft" title="13" src="http://www.eprentise.com/agilitybydesign/wp-content/uploads/2009/07/13.png" alt="13" width="342" height="255" /></a></p>
<p>Many manufacturers realize that they must make changes if they are to survive and flourish in a world that promises to be very different from the past. A quick look at some of the factors that are already impacting our world gives us a small taste of what we can expect as we move into the 21st century.</p>
<p>•    Customers are placing smaller orders.<br />
•    Customers are looking for faster turn around times.<br />
•    Customers are demanding more custom products<br />
•    Customers are constantly changing as they try to keep up with their customers’ demand.</p>
<p>In addition to these external factors, manufacturers are being pressured to be more profitable by reducing waste, improving efficiencies and becoming more responsive. The new paradigm is clear; manufacturers who want to be successful must be able to reduce inventories while learning to react faster and smarter to change. For those paying close attention this is not breaking news, but it appears that many companies do not yet have a clear understanding of the underlying problems and what they need to do.</p>
<p>Doing the same old things but faster is unlikely to work and is not the answer. This has been proven through the success achieved by companies such as Nucor.  They have become one of the largest steel producers in the United States by putting in place strategies that have made them fast and nimble.</p>
<p>The underlying cause of the problem is that too many manufacturers are running their businesses with Enterprise Resource Planning (ERP) legacy systems that still have their manufacturing roots in early 1980’s MRP (Material Resource Planning) concepts and technology. These systems were primarily designed to address the needs of make-to-stock manufacturers who could rely on excess inventories at every level of their process. Many companies are starting to understand the limitations of this approach.  This article is for those who are looking to be leaner and more flexible.</p>
<p>The limitations of a traditional MRP based planning system can be more easily understood if applied to a real life situation such as planning a wedding at say 2:00 pm on June 24. This is obviously unrealistic but it does highlight the consequences that stem from a system that can’t even create a starting plan that is accurate and precise.</p>
<p>Everyone involved is initially delighted when told that they can book their wedding on June 24 at 2:00 pm.  What the wedding planner doesn’t initially know is whether or not other weddings are booked for that same day and time. This is a potential problem that could quickly evolve into pandemonium.</p>
<p>It would be nice if a planning tool had the ability to recognize a conflict and a need to re-schedule. MRP planning would not be able to do that because it doesn’t know there is a conflict and it has no logic to help it determine which weddings have priority. Even if it could prioritize the weddings, it couldn’t calculate precise new dates and times for each of the weddings. And if it could calculate a new date and time for each wedding, it would have no way of making sure that the priest was available at that time, and even if the priest was available, it would have no way of notifying the photographer and the chef and the restaurant, etc.</p>
<p>The underlying limitation behind all of these problems is that MRP-based planning systems can’t finitely plan even one constraint, and they certainly can’t synchronize multiple constraints. A few years ago a number of smart people who were frustrated with the limitations of such legacy systems started implementing a concept called Lean manufacturing. Lean was designed to remove complexity and waste and was made popular by the success of companies like Toyota.</p>
<p>At the planning and execution level, Lean is built on three key concepts of waste elimination &#8211; muda, muri, and mura. Without getting into too much detail, muda addresses the need to remove non-value added work such as overproduction (production ahead of demand) and excess inventories (all components, work-in-progress, and finished product not being processed).</p>
<p>Muri is defined mainly as the breaking down of tasks into their smallest constituencies, and mura refers to the need to make work flow from end to end by removing unevenness in the process rather than buffering it.</p>
<p>Other companies were starting to use a management strategy called Six Sigma that had been developed by Motorola to identify and remove the causes of defects and errors in manufacturing and business processes. Today these two concepts are often combined into one concept, which is sometimes called Lean 6Sigma or Lean Six Sigma.</p>
<p>Although most companies who decided to adopt Lean 6Sigma were able to achieve some level of success, manufacturers who had highly predictable demand patterns and a limited number of products were able to achieve the best results.</p>
<p>Other manufacturers who were still looking for ways to manage the daily bombardment of change saw only limited success. One of the reasons for this was that early Lean 6Sigma systems were manually intensive so they were unable to replace all the functions that had previously been performed by their Legacy planning systems.</p>
<p>So while Lean 6Sigma initiatives were working to reduce inventory levels their old planning systems were telling them to increase inventory levels. Because of the obvious conflict, mistakes were made resulting in inventory shortages, which led to late shipments and mass confusion. Faced with this situation, manufacturers realized that they either had to abandon their Lean initiatives or find planning systems that would not only dovetail with their need to reduce waste but would automate it where it made sense.</p>
<p>Without planning software that can prioritize and plan events at the detail level it is not possible to synchronize material and capacity constraints; without synchronizing multiple constraints, there is no basis for planning reduced inventory levels. Similarly, if something changes and specific materials are not available, this information must be synchronized back to the plan.</p>
<p><a rel="attachment wp-att-216" href="http://www.eprentise.com/agilitybydesign/?attachment_id=216"><img class="alignleft size-full wp-image-216" title="2" src="http://www.eprentise.com/agilitybydesign/wp-content/uploads/2009/07/2.png" alt="2" width="432" height="138" /></a></p>
<p>When the plan changes the new planning system must be able to instantly re-calculate the impact of each change on downstream activities, which, in turn, kicks off a new round of synchronizing and re-synchronizing. Right about now you should be starting to understand the problem because none of these things can be done with traditional legacy systems that rely on MRP planning concepts.</p>
<p>We believe that every second spent making the wrong product takes away capacity that could be used for products for which the customer is waiting.</p>
<p>Many industries, such as the steel industry, find it difficult to make only what their customers order because the efficient size of a production run is often much larger than the size of individual customer orders. Traditionally this means that they end up making additional stock that sits around forever.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eprentise.com/agilitybydesign/2009/07/using-lean-to-win-with-speed-in-the-global-marketplace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
