ERP System Solutions for Small Companies: Readiness & Selection
Abstract
Over the past decade almost all of major businesses in the US have implemented Enterprise Resource Planning (ERP) systems to run daily business operations. However, a complex ERP system, if not implemented properly, can easily disrupt, or sometimes cripple, the flow of the manufacturing and other operations. While large organizations are in a unique position to implement a good RP system, most small companies cannot afford the acquisition and implementation cost of a big name ERP system. Therefore, smaller organizations rely on vendors with affordable, but not necessarily proven, ERP systems. To help small businesses avoid implementation problems and system glitches after ERP implementation, two proactive initiaves are recommended. ERP readiness and ERP selection. This article organizes a checklist for each initiative so that small companies are better prepared to overcome implementation challenges and their expectations are more aligned with the norm of an ERP implementation.
References
Chalmers, R. E. ( 1999). Small manufacturers seek best ERP fit. Manufacturing Engineering, 123(4), 42-46.
Chapman, S., Ettkin, L., & Helms, M. (2000). Do small business need supply chain management. ff£ Solutions. 32( 8), 31-33.
Doyle, J. (2000a). ERP: Going after the little guy. Midrange Systems. /3(13), 18-22.
Doyle, J. (2000b). For mission hokey, small business ERP is mission: possible. Midrange Systems. /3(13), 24-26.
Eshelman, R.G., Jurs, P.E., & Taylor, T.C. (2001). When small companies implement big systems. Strategic Finance, 82( 8), 28-33.
Fichman, R. G. & Moses, S. A. (1999). An incremental process for software implementation. Sloan Management Review, 40( 2), 39-52.
Hamey, J. (2000, January/February). Hosted ERP: Who offers what and how. Inform, 14( 1 ), 38-40.
Jeffery, B. & Morrison, J. (2000). ERP, one letter at a time. CIO, 13( 22), 72-76.
Jiang, J. J., Klein, G., & Chen, H. (2001). The relative influence of!S project implementation policies and project leadership on eventual outcomes. Project Management Journal, 32( 3), 49-55.
Kumar, K. & Van Hillegersberg, J. (2000). ERP experiences and evolution. Communications of the ACM, 43(4), 22-26.
Mabert, V., Soni, A., & Venkataramanan, M. (2000). Enterprise Resource Planning survey of U.S. manufacturing firms. Production and Inventory Management Journal, 4/(2), 52-58. Markus, M. L., Tanis, C., & Fenema, P. C. (2000). Multisite ERP implementations. Communications of the ACM, 43(4 ), 42-46.
Nairn, G. ( 1998, September 2). ERP market software vendors target smaller companies. Financial Times Surveys Edition, Financial Times, 9.
Romeo, J. (2001). Less pain, more gain in ERP rollouts. Network Computing, 12( 19), 49-56. Scheer, A. & Habermann, F. (2000). Making ERP a success. Communications of the ACM , 43(4), 57-61.
Siriginidi, S. (2000). Enterprise resource planning in reengineering business. Business Process Management Journal, 6(5), 376-391.
Smith, D. (1999). Better data collection for greater efficiency. Manufacturing Engineering, 123( 4), 62-68. .
Stedman, C. (1999a, November 15). ERP flops point to users' plans. Computerworld, 33(46), l , 137.
Stedman, C. (1999b, December 13). ERP project problems plague city payroll. Computerworld, 33( 50), 38.
Taylor, J. (1998). Small company, big challenge. Manufacturing Systems. 16( 10), 82-90.
Taylor, J. (1999). Fining enterprise software in smaller companies. Management Accounting, 80(8), 36-39.
The United States Chamber of Commerce (2003). How is small business defined. http://www.uschamber.com/events/matchmaking/faq.htm
Tuynman, J. (2000, November). Software solutions. Business Mexico, / O( l l), 46-51.
Zheng, S., Yen, D., & Tam, J. (2000). The new spectrum of the cross-enterprise solution: the integration of supply chain management and enterprise resources planning systems. The Journal of Computer Information Systems, 41(1), 84-93.