Thursday, September 22, 2011
Breakthrough in Material Planning: Demand Driven MRP
For the first time in over 30 years, Material Requirements Planning (MRP), is undergoing a fundamental improvement. A major new development, dubbed Demand Driven MRP (DDMRP) is moving from theory to practice, and the results are impressive. If you care about manufacturing ERP, you would be wise to pay attention.
Carol Ptak recently called my attention to her work with Chad Smith at the Demand Driven Institute
, which they founded in 2010 to promote the concepts of DDMRP. I've known Carol for many years, through her work as past President and CEO of APICS and her time at PeopleSoft, where she was an early proponent of making MRP more "demand driven." I wrote a brief blog post in 2003 covering this subject (see: PeopleSoft Strengthens Its Manufacturing Offerings by Acquiring Demand Flow).
So, I jumped at the opportunity to set up a briefing on DDMRP with Carol and Chad for me and my associates Bob Gilson and Nick Hann at Strativa
Bringing MRP into the 21st Century
Before we look at some of the key concepts of DDMRP, let's review the history of material planning.
MRP, first developed in limited fashion in the 1950s and 60s, really took off in the 1970s, when computer systems enabled widespread adoption and APICS undertook the "MRP Crusade" to popularize it. It was a great advance over previous material planning techniques, such as statistical order point (popularized during the Second World War), which viewed each inventory item separately. The big conceptual breakthrough of MRP was to separate dependent demand (sub-assemblies and purchased items) from independent demand (e.g. finished goods and service parts). MRP, therefore, provided a holistic, or system-wide view of inventory.
MRP (material requirements planning) morphed in the late 1970s and 80s into MRP II (manufacturing resource planning) and ultimately ERP (enterprise resource planning). But the heart of today's ERP systems (at least in the manufacturing sector) is still the MRP processing logic that is essentially unchanged since the 1970s.
In practice, MRP relied heavily on demand forecasts to drive planning and used safety stock inventory to cover variability in lead-times and forecast errors. The results, though far better than the old order point systems, were often excess inventory and less-than-acceptable customer service levels.
Just-in-Time (JIT) inventory and lean manufacturing techniques were, in part, a reaction to the complexity of MRP and a desire to obtain better outcomes. Introduced in the 1980s, JIT was a simplification in material planning and it took inspiration from the quality management movement and Toyota Production System in Japan. JIT is essentially a "pull system"--relying upon simple demand signals, such as Kanbans, from customers to suppliers up and down the supply chain, often with little or no computerized support. Unlike MRP, which viewed inventory as an asset, JIT viewed inventory as a "waste" and sought to minimize it wherever possible by minimizing variation in supply and demand, and reducing setup times to enable smaller lot sizes. But its emphasis on inventory reduction, lack of a system-wide view of inventory, and incomplete planning equation created brittle supply chains, subject to disruptions.
Embracing and Extending MRP and JIT
Demand Driven MRP is not a completely new method: it builds upon and extends the concepts of MRP while borrowing the best features of lean manufacturing. Like lean manufacturing, it seeks to "align efforts and resources as close as possible to actual demand" (a so-called pull system) while at the same time, like MRP, provide "visibility to the total requirements and status picture across the enterprise."
The authors' background in the Theory of Constraints is evident. They are not looking to compromise between MRP and lean manufacturing. Rather they recognize and seek to satisfy the legitimate objectives of both. For example:
- The greatest extension of DDMRP is the introduction of supply chain modeling prior to generating material plans, as shown in steps 1-3 in the Figure at the top of this post. Here, the organization determines the optimum places where inventory should be held. This is a step that MRP simply does not address. MRP and even Advanced Planning systems (APS) generally take inventory stocking points and safety stock levels as givens and plans within them. At the opposite end of the spectrum, JIT techniques are blind to the overall supply chain. Each node of a pure pull system is only sensitive to the demand at the next downstream operation. DDMRP, on the other hand, models where inventory should be held in order to minimize lead times and reduce variability where it matters the most.
- In terms of inventory, DDMRP stakes out a middle ground between MRP and lean manufacturing. It does not view inventory as a waste, as lean manufacturing does with its goal of "zero inventory," and it does not seek to establish safety stock levels in a static way, as MRP generally does. Rather it seeks to hold the right amount of inventory at the right place in the supply chain "to promote flow but minimize working capital," and "to size and dynamically adjust those strategic stock positions" based on a set of rules dominated by six factors.
- DDMRP deals with lead times in a more realistic fashion than traditional MRP, which in calculating manufacturing lead time assumes all components are in stock, or in calculating cumulative lead times assumes nothing is in stock. Neither are good assumptions in most environments today. DDMRP introduces a concept it calls Actively Synchronized Replenishment (ASR) Lead Time (ASRLT), which represents "the longest unprotected sequences in the bill of material" where "protection" is defined by strategic stocking points. These points decouple, compress, and ultimately define the calculated lead time of an item.
- MRP is only a planning tool and JIT is only an execution tool, whereas DDMRP is both a planning tool (in the modeling and planning stages) and an execution tool, in the execution stage (see Figure at top of this post).
- DDMRP greatly reduces the emphasis on accurate forecasts in driving supply plans. Demand is driven entirely or largely by actual customer demand (typically sales orders), which can then be satisfied from compressed lead time due to the strategically placed inventories at the subassembly or component level.
These are just a few of the key concepts of DDMRP. For a more complete view, see the additional resources listed at the end of this post.
If there is any doubt that DDMRP is a major breakthrough, consider this: the book everyone considers the "Bible" of MRP was written in 1974 by the late Joseph Orlicky, and the second edition was authored in 1994 by the late George Plossl. McGraw-Hill, publisher of Orlicky's Material Requirements Planning
has just released the third edition, which is authored by Carol Ptak and Chad Smith, the brains behind DDMRP. This third edition now incorporates the concepts of DDMRP, building upon the work done by Orlicky and Plossl, two of the fathers of MRP.
Proof in the Pudding
Think DDMRP is just a nice theory? Not so. The benefits have already been demonstrated by at least two early adopters:
- Oregon Freeze Dry, after adopting DDMRP, saw a 20% increase in sales 20% and 60% inventory reduction in one division, along with 60% reduction in make-to-order lead-time and 20% inventory reduction in another division.
- LeTourneau Technologies (LTI) is an interesting case study in the natural resources sector. The firm implemented DDMRP in one of its two plants, while letting the other plant continue with traditional MRP. Both plants had similar resources, bills of material, and material planning personnel.
During a boom and decline cycle of 2005 to 2008, the DDRMP plant grew revenues from $270M to over $620M, while growing inventory by only about $80M. In contrast, the traditional MRP plant experienced the similar growth in revenues, but inventories grew at the same pace. When the recession hit in 2008, the DDMRP plant , however, was well positioned with lean inventories while the traditional MRP plant was exposed to a huge amount of inventory liability.
Additional case studies should begin to appear as other organizations gain experience with these new methods.
I believe that enterprise software vendors, especially those focused on supply chain management, are going to move quickly to begin to incorporate DDMRP concepts into their systems. So far, there is only one software provider that has done so, Replenishment+® from Demand Driven Technologies
, of which Chad Smith is a paid advisor. However, I see indications that some other vendors are moving in this direction. In other words, I do not believe availability of software is going to be an obstacle.
If there is any obstacle to wholesale adoption of DDMRP, it is going to be in the general level of resource planning skills in many manufacturing organizations. The concepts behind DDMRP are not simple. Many practitioners tasked with responsibility for MRP systems today do not have a deep understanding of MRP principles, even of traditional MRP circa 1974. How are they going to grasp the concepts behind DDMRP? I think this will be the key limitation hindering widespread adoption, unless manufacturing organizations are willing to re-invest in professional development in a sustained way. Conceptual education--not just software training--is going to be key.
A corollary observation is this: production and material planning is going to become an even more critical function for manufacturing and distribution firms. It always has been, of course, but it will become even more critical in industries where some players have the skills to adopt DDMRP and others don't. No longer just a back-office function, resource management should once again become an inviting career path for young people.
There is much more to DDRMP than I can outline here, such as its ability to accommodate seasonality, ramp up/down in production, and end-of-life scenarios, all of which are troublesome for traditional MRP systems and especially lean-manufacturing systems. Therefore, it is best to point readers to the following resources.
- Demand Driven MRP. The flagship DDMRP website maintained by Carol and Chad, with a good introduction to DDRMP. Free white papers, videos, and podcasts are available on a number of DDMRP topics.
- Demand Driven Institute. The educational and consulting organization promoting the concepts of DDMRP. The textbook I mentioned earlier, Orlicky's Material Requirements Planning, Third Edition, is also available here, with a supplemental DVD.
- Orlicky's MRP. This is the official website of the new edition of Orlicky's Material Requirements Planning.
There are several white papers and videos linked at these sites that go into more depth on DDMRP. Training classes are now being rolled out. In addition, the authors will be presenting more on this subject at the APICS International Conference
in Pittsburgh, October 23-35. If you are planning to be at this conference you will be wise to register for this session, as it will probably be standing room only.
Related PostsAPICS Returns to Its RootsPeopleSoft Strengthens Its Manufacturing Offerings by Acquiring Demand FlowLean Manufacturing: Not a Complete Solution without Information TechnologyLean Manufacturing Doesn't Really Need Software, But Software Can HelpLean Thinking is Still More Than Software
Thursday, September 01, 2011
Kenandy: A New Cloud ERP Provider Emerges from Stealth Mode
There's news for those of us interested in manufacturing ERP: a new cloud ERP provider is having its coming-out party this week at Dreamforce, the annual user conference of Salesforce.com. Kenandy
, which is built entirely on Salesforce.com's platform, provides core manufacturing functionality, such as inventory, shop orders, purchase orders, and material planning. Founded in 2010, Kenandy already has one customer live and a handful of others sold and in implementation.
Early this week, several people forwarded me advance word on Kenandy from a Wall Street journal blog post
. Normally, the launch of a new cloud provider would not warrant this kind of attention. But this launch has an interesting twist: the brains behind Kenandy is none other than Sandra Kurtzig. She is the original founder and CEO of ASK Group, the developer of the well-known ManMan ERP system--more or less the SAP of the 1980s. She retired something like 10 years ago, but was convinced to come out for an encore by Marc Benioff, CEO of Salesforce.com and her neighbor on a beach in Hawaii. Kenandy has venture funding from Kleiner Perkins Caufield & Byers, and its managing partner Ray Lane sits on Kenandy's board.
I scored an interview with Sandra and her CMO Rod Butters yesterday, prior to Sandra's appearance on stage with Marc Benioff this morning at Dreamforce. I had a lot of questions for Sandra, and she was forthcoming with answers.
- Kenandy is positioning itself for small and midsize manufacturers ($15M - $300M), especially those that source, manufacture, and distribute products through contract manufacturers and channel partners. Sandra noted that ERP vendors with systems designed in the 1970s and 80s (such as ManMan) assumed their customers were vertically integrated. Her perspective is that this orientation has carried forward in the design assumptions of the leading on-premise ERP providers today, which have their roots in systems built during that time period. This is not a good assumption today, as even small and midsize manufacturers are contracting large parts of their operations offshore and have complex distribution relationships with channel partners. Such organizations need an extended ERP system, and Kenandy is being designed with these scenarios in mind.
- Built on Salesforce.com's platform, Kenandy is a full multi-tenant SaaS offering. An organization can run multiple facilities within a single tenant, or it can set up multiple tenants, for its contract manufacturers or business partners, for example, and gain inventory and production visibility up and down its supply chain. (Disclaimer: I have not evaluated Kenandy on any functionality points to confirm these features).
- Kenandy expects very short implementation times. Its first customer, Den-Mat, a maker of dental products, went live in two weeks, converting from a legacy IBM Series i (AS/400) system.
- Kenandy is focusing on manufacturing functionality and depending on other cloud providers to fill out other parts of the enterprise suite. For example, there is integration (of course) with Salesforce.com for CRM, and with FinancialForce.com for financials. In addition, Sandra claims that integration with customer's legacy systems (e.g. Quickbooks) are always an option.
- Development of Kenandy is being led directly by Sandra: in other words, she is not only the founder and CEO. Like many start-up software firms, she is also the brains behind the product and the chief product management executive. She is working with a small group of internal developers and is supplemented by development resources from Persistent Systems in India.
I also took a walk to the Expo floor and got a quick view of Kenandy's system. I also met the "Ken" of Kenandy. (The firm is named after Sandra's two sons, Ken and Andy).
A Market with Lots of Open Space
I am currently working on a research report on cloud-based ERP systems, so I was quite interested in seeing a new competitor emerge in this market. In my view the market is wide open. There are only a handful of pure multi-tenant SaaS ERP providers, and even few that can support the needs of manufacturers. These providers include NetSuite, SAP's Business ByDesign, Workday, Plex, and Rootstock.
Compare this to the dozens or scores of ERP providers that we could choose from in the 1980s and 1990s. Today the market for traditional on-premise ERP systems is dominated by two vendors: SAP and Oracle. Microsoft occupies a strong secondary place, especially in the SMB space. Many of the other players have been acquired by Infor and Oracle, though several good providers, such as IFS, Epicor, QAD, Syspro remain independent.
Nevertheless, the broad industry trend is moving to cloud computing, and manufacturers that want full-suite ERP in the cloud have few choices. Therefore, the market is wide open. As I mentioned to Sandra, it's like the Pilgrims landing at Plymouth Rock. There is a whole continent waiting for anyone so inclined to stake a claim. There's no need to argue about property lines with neighbors. Just go out, pick a few verticals, geographies, and organization sizes, and build out your offering. There is plenty of room to grow.
Other providers are already doing so. Plex
was first out of the gate, with a full cloud-based ERP offering dating back to the middle of the last decade, and they continue to gain momentum. SAP's launch of Business ByDesign
is also gaining traction, not only in subsidiaries of SAP's traditional large customer base, but in net new SMBs as well. Rootstock
, not as well known, has a credible offering for manufacturers (especially project-based) on NetSuite's platform, and it has now migrated its manufacturing ERP offering to Salesforce.com's platform. Moreover, other on-premise vendors, such as Epicor and Infor, have enabled their products to operate in a multi-tenant cloud deployment model.
But there are large swaths of open space. Kenandy is a welcome new player.Update, 10:02 a.m.:
Sandy is on stage now at Dreamforce. She's wearing a button with the letters ERP crossed out. Marc asks, "Your previous firm ASK built on HP's platform, right?" She jokes, "Is HP still in business?" Ray Lane, an HP board member, is standing next to her. Sandy mentions Salesforce.com's investment in Kenandy. Ray, as mentioned in my post above, is also an investor, and now relates the story of Sandy showing up in Ray's office, asking for money. Ray, who like Sandy, is well over the median age at Dreamforce, admonishes the audience, "Don't think our generation is through yet!"Update, 10:20 a.m.: Dennis Howlett
looks at manufacturing cloud ERP developments.Update, Sep. 6:
Dennis Howlett interviews me live about my thoughts on Kenandy. Click on the image below to watch the interview.
Related PostsWorkday pushing high-end SaaS for the enterpriseSAP Innovating with Cloud, Mobile, and In-MemoryPlex Online: pure SaaS for manufacturingNetSuite a viable alternative for SAP customers?Workday: evidence of SaaS adoption by large firms
(c) 2002-2014, Frank Scavo.
Independent analysis of issues and trends in enterprise applications software and the strengths, weaknesses, advantages, and disadvantages of the vendors that provide them.
About the Enterprise System Spectator.
Send tips, rumors, gossip, and feedback to Frank Scavo at
I'm interested in hearing about best practices, lessons learned, horror stories, and case studies of success or failure.
Selecting a new enterprise system can be a difficult decision.
My consulting firm, Strativa, offers assistance that is independent and unbiased.
For information on how we can help your organization make and carry out these decisions, write to me.
For reprint or distribution rights for content published on the Spectator, please contact me.
Go to latest postings
ERP Support Staffing Ratios
IT Spending and Staffing Benchmarks
IT Staffing Ratios
IT Management Best Practices
Worldwide Technology Trends
IT Salary Report
Get these headlines on your site, free!
Blog Roll and Favorite Sites
Strativa: ERP software vendor evaluation, selection, and implementation consultants, California
StreetWolf: Digital creative studio specializing in web, mobile and social applications
Vinnie Mirchandani: The Deal Architect
Si Chen's Open Source Strategies