AIS Implementation Failure: American LaFrance Case Study
This paper examines the collapse of American LaFrance (ALF), a historic U.S. fire apparatus manufacturer, whose bankruptcy was precipitated by a failed IBM Enterprise Resource Planning (ERP) system implementation during its separation from parent company Freightliner. Through case analysis, the paper identifies key factors behind the AIS failure—including inadequate employee training, poor system planning, and insufficient testing—and evaluates management's role in the breakdown. It then proposes alternative strategies and outlines best practices for successful AIS migration, including comprehensive requirements analysis, systems design, documentation, testing, data conversion, and stakeholder engagement.
- Introduction to Accounting Information Systems: AIS role in business planning and decision-making
- Case Presentation: American LaFrance: ALF's ERP failure and resulting bankruptcy
- Lessons Learned and Failure Factors: Training gaps, poor planning, and insufficient testing
- Effect on the Company and Management Responsibility: Data loss, financial impact, and management accountability
- Alternative Plan of Action and Design Recommendations: Proposed management strategies and design-phase fixes
- Best Practices for AIS Migration: Step-by-step implementation framework for AIS change
- Proposed Foundation for Changing AIS: Stakeholder engagement and risk management principles
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- Uses a concrete real-world bankruptcy case (American LaFrance) to ground abstract AIS concepts in tangible consequences, making the analysis immediately credible.
- Moves logically from diagnosis (failure factors) to prescription (alternative plans and best practices), giving the paper a clear problem-solution arc.
- Draws on multiple academic and practitioner sources (Romney & Steinbart, Gelinas et al., Peppard & Ward) to support both analytical and prescriptive claims.
Key academic technique demonstrated
The paper demonstrates applied case analysis: a theoretical framework (AIS components and implementation phases) is used as a lens to diagnose a documented organizational failure. This technique shows how abstract systems concepts translate into real operational and financial outcomes, and is particularly effective in business and accounting courses.
Structure breakdown
The paper opens with a brief introduction to AIS, then presents the ALF case, extracts lessons and failure factors, assesses organizational impact and management responsibility, proposes alternative actions and design improvements, and closes with a detailed best-practices checklist for AIS migration (requirements analysis, design, documentation, testing, training, data conversion, and launch). A final section proposes a stakeholder-centered foundation for system change.
Introduction to Accounting Information Systems
Accounting information systems (AIS) have transformed business processes on a worldwide scale. When financial data is entered into an AIS, financial statements and reports are generated at several business levels to support profitability. Romney and Steinbart (2012) revealed that accounting systems process information to provide data to users so that they can plan, manage, and operate their respective businesses. Given this, accounting information systems are viewed as a method that assists management in planning and control by offering data that is both reliable and relevant for decision-making. The primary objective of an accounting system is to provide accounting data to outside parties, operational personnel, and management.
Case Presentation: American LaFrance
American LaFrance (ALF), an American automotive manufacturer, produced fire aerials, fire engines, and emergency apparatus such as ambulances and rescue vehicles. Established in 1873, ALF had long been a pioneer in fire apparatus production in the United States, and by the mid-2000s was recognized as the top brand of custom-made fire-fighting equipment, rescue vehicles, and ambulances (Huber and Daft, 1986; Bhagwani, 2009).
In 2008, ALF experienced a serious financial crisis and subsequently determined that the failure was caused by IBM's unsuccessful Enterprise Resource Planning (ERP) implementation. Specifically, information filed in bankruptcy court indicated that the problems arose when ALF separated as an independent firm from its parent company, Freightliner. During the transition, ALF had outsourced its manufacturing, payroll, inventory, and accounting services to its former owner. As part of the transition, ALF created a separate ERP system to support the company following the separation from Freightliner (Bhagwani, 2009). Despite considerable effort to resolve the issues with IBM's ERP software, ALF was unable to overcome the major conflicts and suffered significant losses as a result. The consequences included an inability to manage inventory, distribute finished products, and generate adequate cash flow. This liquidity crisis ultimately bankrupted the company.
Lessons Learned and Failure Factors
The process of implementing a financial management information system is a rigorous undertaking that must be carefully planned before the project begins. The project team tasked with AIS integration must be properly trained and knowledgeable in order to ensure positive system outcomes. When implementing an accounting information system, it is imperative that the organization is prepared to devote the attention necessary to make the AIS work properly for its specific needs (Bhagwani, 2009). Because no two companies are identical, there are divergent factors that determine the success or failure of an AIS implementation.
In ALF's case, the cost evaluation was limited because the company ultimately chose to file for bankruptcy. Additionally, when ALF gained independence from Freightliner, management did not understand how to monitor the new systems because they lacked familiarity with them (Bhagwani, 2009).
Inadequate employee training was a primary contributing factor. Businesses sometimes take shortcuts due to the cost and time associated with training, which can prevent the organization from reaching its anticipated performance targets (Iskandar, 2015). Insufficient workforce training may also cause staff to seek help from colleagues who are proficient in the system, thereby reducing coworker efficiency and increasing costs.
Poor system planning was another contributing element. Management sometimes holds unrealistic expectations and goals for an AIS, or the system may be too complex to understand, leading to failure. Management must therefore set practical and achievable expectations and conduct a feasibility evaluation that addresses five key aspects: legal, technical, scheduling, economic, and operational feasibility (Iskandar, 2015).
Insufficient system testing was the third key factor. Inadequate testing can be extremely costly for an enterprise. Testing should be conducted early in the development phase to identify and eliminate issues as soon as possible (Iskandar, 2015). To reduce this risk, firms should use debugging methods and apply testing techniques such as processing test data, walkthroughs, and acceptance tests.
Effect on the Company and Management Responsibility
The primary risk was that the AIS was not properly prepared. Throughout the contract period with Freightliner, inventory was not effectively recorded, and data was lost during the transition. When ALF moved from Freightliner's accounting system to its own new ERP system, the changeover caused a system collapse in which lost data cost the firm nearly one hundred million dollars (Bhagwani, 2009).
Because ALF's inventory was not being tracked properly, and because there were several instances where accounts did not balance, no "red flag" emerged to indicate that errors had occurred in the AIS. ALF's system was designed to allow both input and output of inventory-related data. However, after the system transition from Freightliner to ALF, inventory and other significant business data were lost and became unrecoverable (Bhagwani, 2009). Because this data was unrecoverable, numerous orders and details were lost, and the firm was unable to deliver products and satisfy customer needs — a key reason the company faced bankruptcy.
Management responsibility was central to this failure. The ALF management team had the duty of ensuring that the implemented AIS worked properly and was capable of meeting its goals alongside organizational objectives. Successful execution of an accounting information system is typically led by a project manager who dedicates time, budget, and planning to workflow and processes. Staff members must be adequately trained before the transition to a new AIS is made, and the project team must take sufficient time to select an appropriate alternative AIS only after thorough training and technical support have been established.
References
Bhagwani, A. (2009). Critical success factors in implementing SAP ERP software.
Daft, R., & Huber, G. (1986). How organizations learn: A communication framework (No. TR-ONR-DG-18). Texas A&M University, College Station, Department of Management.
Gelinas, U. J., Dull, R. B., & Wheeler, P. (2011). Accounting information systems. Cengage Learning.
Hines, D. C., & Carrington, A. (2010). What we know now: Lessons learned implementing federal financial systems projects. Forum: Driving Performance — Strategies for More Effective Government. IBM Center for The Business of Government. Retrieved from http://www.businessofgovernment.org/sites/default/files/Forum_FM.pdf
Iskandar, D. (2015). Analysis of factors affecting the success of the application of accounting information system. International Journal of Scientific & Technology Research, 4(2), 155–162.
Peppard, J., & Ward, J. (2016). The strategic management of information systems: Building a digital strategy. John Wiley & Sons.
Reifer, D. J. (Ed.). (2006). Software management (Vol. 16). John Wiley & Sons.
Romney, M. B., & Steinbart, P. J. (2012). Accounting information systems. Pearson.
Create your account
Always verify citation format against your institution’s current style guide requirements.