BUSI 615 Week 3 Discussion Board 2 thread Example

Discussion Board 2: Enterprise Resource Planning

BUSI 615 Logistics, Discussion Board 2 (thread)

Thread by [Student Name]

The stove manufacturer is a composite standing in for the firm a student would choose; the research cited is real, and the requirements follow Liberty's public course guide for BUSI 615.

Thread

What does a mid-sized manufacturer actually buy when it spends a year and several million dollars on an Enterprise Resource Planning system? Our readings this week list many benefits, but I think they reduce to three: one shared database, standardized processes and faster information. My thread examines each, using research to separate what ERP reliably delivers from what depends on how a firm implements it.

One shared database

In the Week 1 forum I used a composite firm, Harlan Ridge Stoveworks, a Pennsylvania maker of wood and pellet stoves, to illustrate MRP II. Imagine that the firm still runs separate systems: an order-entry program in sales, a planning package in the plant and an accounting system in finance. When a dealer orders 40 pellet stoves, a clerk enters the order once for sales, a planner retypes the demand into the schedule and the accounting staff create the invoice from a printed packing list. Each handoff introduces delay and the chance of error, and the three departments see three different figures for the same order.

An ERP system replaces those handoffs with a single transaction. The order updates the sales module, creates demand that the planning module explodes into parts, reserves finished stock if any exists and later posts revenue and receivables in the financial module. Jacobs and Weston (2007) describe this shared database, built on the MRP logic of earlier decades, as the defining feature that separated ERP from the specialized programs it replaced. For a seasonal firm, the practical gain is that the sales manager, plant scheduler and controller look at the same stove order on the same screen, a benefit the textbook stresses in its chapter on ERP functions.

Standardized processes

The second thing ERP buys is a set of business processes built into the software. Most packages assume a particular way of entering orders, receiving goods and closing the books. A firm can adopt those processes, adjust settings within them or rewrite the software to match its existing habits. Umble et al. (2003) listed among their critical success factors a clear understanding of strategic goals, committed top management, a strong implementation team, accurate data and extensive training, and they warned that changing the software to preserve old practices adds cost and risk. Their account of one manufacturer's implementation showed how much depended on managing organizational change rather than technology.

The difference between configuring and customizing matters a great deal for a firm like Harlan Ridge. Setting dealer credit limits or choosing a costing method is configuration, and it survives software upgrades. Writing new code so that the old order form looks the same is customization, and each upgrade must then be tested against it. Every customization is a small decision to keep an old process, and the bill for it arrives with every upgrade. The textbook's discussion of reengineering makes the same point from the other direction: ERP is an opportunity to question how work is done, not only to automate it.

Faster information, and what the evidence says about returns

The third claim is that integrated, timely information improves decisions and therefore performance. Here the evidence is more cautious than the brochures. Hendricks et al. (2007) studied 186 announcements of ERP implementations along with supply chain management and customer relationship management systems. They found some evidence that ERP adopters improved profitability, with stronger gains for early adopters, but no clear improvement in stock returns. Supply chain systems showed improvements in both, while customer relationship systems showed neither. The authors noted that, despite high implementation costs, they found no persistent evidence of harm from enterprise system investments.

Gattiker and Goodhue (2005) help explain why results vary. In their survey of 111 plants, ERP fit best where plants were highly interdependent and least where they differed sharply from one another, and customization and time since implementation also shaped outcomes. A firm whose sales, plant and finance functions constantly depend on one another, as at a stove maker with a short selling season, stands to gain more from integration than a holding company of unrelated businesses.

What the purchase price leaves out

A fair comparison also needs the full cost, because the license or subscription is usually the smallest part of it. Harlan Ridge would pay for consultants to configure the system, for staff time spent mapping processes and cleaning data, for training every user from the shipping dock to the controller's office and for the temporary drop in productivity most firms see in the months after go-live. Data cleanup alone can be large at a firm with years of duplicate part numbers and dealer records entered three different ways. Ongoing costs follow: annual support fees, periodic upgrades and the internal staff needed to maintain the system. Our chapter on ERP benefits lists the gains in inventory, order cycle time and closing the books; a responsible business case sets those gains against this whole stream of costs over five or more years rather than against the first-year invoice.

Reading the evidence together

Taken together, these studies suggest that ERP reliably delivers the first benefit, a shared database, and makes the second possible. The third, better performance, depends on implementation choices and on the firm's structure. I would therefore ask two questions before recommending a system. First, how interdependent are the firm's functions and sites? High interdependence strengthens the case. Second, is management willing to change processes to fit the software rather than the reverse? If not, the firm may pay for integration and receive an expensive copy of its old systems.

For Harlan Ridge, the answers favor ERP: its departments depend on a single seasonal plan and its processes are informal enough that adopting standard ones would be an improvement. A firm with mature, distinctive processes built over decades, and staff attached to them, might reasonably reach a different conclusion, or choose to integrate only the functions that depend on each other most, such as planning and purchasing, and leave the rest alone for now. I am curious whether classmates who have lived through an ERP go-live saw their firms adapt to the software or adapt the software to themselves, and which choice they would make again.

References

Gattiker, T. F., & Goodhue, D. L. (2005). What happens after ERP implementation: Understanding the impact of interdependence and differentiation on plant-level outcomes. MIS Quarterly, 29(3), 559-586. https://doi.org/10.2307/25148695

Hendricks, K. B., Singhal, V. R., & Stratman, J. K. (2007). The impact of enterprise systems on corporate performance: A study of ERP, SCM, and CRM system implementations. Journal of Operations Management, 25(1), 65-82. https://doi.org/10.1016/j.jom.2006.02.002

Jacobs, F. R., & Weston, F. C., Jr. (2007). Enterprise resource planning (ERP): A brief history. Journal of Operations Management, 25(2), 357-363. https://doi.org/10.1016/j.jom.2006.11.005

Umble, E. J., Haft, R. R., & Umble, M. M. (2003). Enterprise resource planning: Implementation procedures and critical success factors. European Journal of Operational Research, 146(2), 241-257. https://doi.org/10.1016/S0377-2217(02)00547-7