Legal Truth and Consequences for a Failed ERP Implementation

Legal Truth and Consequences for a Failed ERP Implementation

Walter W. Austin, Linda L. Brennan, James L. Hunt
Copyright: © 2011 |Pages: 20
DOI: 10.4018/jcit.2011010103
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

This case is inspired by a complaint and response filed in the U.S. court system. One of the case’s authors served as an expert witness in the case. Because the suit settled before going to trial, some of the details of the case are not part of the public record; therefore, the names of the companies involved have been changed and certain details disguised to protect the identity of the litigants. However, the essentials of the case remain faithful to the actual circumstances and provide a basis for analysis of decision points and a discussion of costs and responsibilities for the issues in the case. A leading manufacturer of building materials in the United States selected an integrated enterprise resource planning (ERP) system to install on its existing hardware infrastructure. This case describes the ERP selection, implementation and migration challenges, impaired functionality, and the business and legal issues that ensued due to the software’s incompatibility with the hardware. With the software not performing as expected, the vendor withdrawing its software support, and costs escalating, the manufacturer sought legal counsel.
Article Preview
Top

Organization Background

Building Blocks, Inc. (BBI) is a large producer of residential and commercial roofing and insulation products, with manufacturing and sales facilities in the United States and Canada. Founded in the early 1980s as a family business with a single manufacturing facility, the company has become one of the largest building materials manufacturers in the world with global product distribution. The company describes itself as a fast-growing, innovative and environmentally responsible manufacturer of quality building materials.

BBI is a privately-held corporation with a work force of approximately 1,700. It manufactures 26 different products at 15 factories located in 10 states. Its sales force, operating from 14 offices strategically located in various states and Canada, had 2007 sales of $137,000,000 in North America, China, and the European Union.

BBI is organized with traditional functional divisions, with a separate division devoted to international sales. Each of the vice presidents, with the exception of the vice president of the international division, was a long-time company employee. The Vice President (VP) of the international division had previously served as president of one of the Canadian companies acquired by BBI. The VPs for sales and operations had both risen through the ranks as BBI grew, and had little formal education in their respective functions. The VP for finance had been employed by BBI almost since its founding, having been recruited from a Big Four accounting firm shortly after BBI began to grow. Each of the VPs had ownership in the company, though the President and other family members held a controlling interest.

As can be seen from the organization chart presented in Figure 1, the VP for finance was responsible for information and systems functions within BBI. None of the other VPs had much experience with information systems, and generally deferred to the VP - Finance. While highly knowledgeable of accounting and finance, his knowledge of information systems was primarily from a user perspective. He was, however, acutely aware of his limited knowledge of technology and as the company grew, knew more expertise was needed. After creating a new position he had hired an extremely competent information systems manager to be the Director – Information Systems.

Figure 1.

BBI organization chart

jcit.2011010103.f01

This individual had earned a master’s degree in computer science from a large state university, and had been employed immediately upon graduation by a large oil company. She was subsequently employed as an assistant director of information systems by a large oil tanker manufacturer. With a combined eleven years of experience in these two positions, she was hired by BBI to be the new Director. In the six years since she had joined the company, she had recruited and developed a competent, experienced staff, several of whom had degrees in information technology-related fields.

Top

Setting The Stage

The computing infrastructure at BBI was centered on the IBM AS/400 mid-range computer. The AS/400 was a popular, general-purpose computer, first introduced by IBM in the early 1990s. It offered relational database capability and an object-based operating system; both of which were relatively advanced capabilities at the time. Moreover, it was intended to be operated without the talent in systems programming that was needed for mainframe computers. As it replaced popular minicomputers (the System/36 and System/38) with extensive software package availability, there was increased interest in development of packaged software to offer on the AS/400 platform.

The technology has been extended, rebranded, and replaced in the years since its initial introduction, although nominally the AS/400 was discontinued in 1999. In its 1998 Annual Report, IBM (1998, p. 31) reported that it “shipped the AS/400s in record numbers… and delivered a 94 percent performance improvement.”

Complete Article List

Search this Journal:
Reset
Volume 26: 1 Issue (2024)
Volume 25: 1 Issue (2023)
Volume 24: 5 Issues (2022)
Volume 23: 4 Issues (2021)
Volume 22: 4 Issues (2020)
Volume 21: 4 Issues (2019)
Volume 20: 4 Issues (2018)
Volume 19: 4 Issues (2017)
Volume 18: 4 Issues (2016)
Volume 17: 4 Issues (2015)
Volume 16: 4 Issues (2014)
Volume 15: 4 Issues (2013)
Volume 14: 4 Issues (2012)
Volume 13: 4 Issues (2011)
Volume 12: 4 Issues (2010)
Volume 11: 4 Issues (2009)
Volume 10: 4 Issues (2008)
Volume 9: 4 Issues (2007)
Volume 8: 4 Issues (2006)
Volume 7: 4 Issues (2005)
Volume 6: 1 Issue (2004)
Volume 5: 1 Issue (2003)
Volume 4: 1 Issue (2002)
Volume 3: 1 Issue (2001)
Volume 2: 1 Issue (2000)
Volume 1: 1 Issue (1999)
View Complete Journal Contents Listing