The T-1 Auto Inc. Production Part Testing (PPT) Process: A Workflow Automation Success Story

The T-1 Auto Inc. Production Part Testing (PPT) Process: A Workflow Automation Success Story

Charles T. Caine, Thomas W. Lauer, Eileen Peacock
Copyright: © 2003 |Pages: 14
DOI: 10.4018/978-1-59140-061-5.ch005
(Individual Articles)
No Current Special Offers


This case describes the development, design, and implementation of a workflow automation system at a tier one automotive supplier, T1-Auto. T1 is a developer and manufacturer of anti-lock brake systems. In 1991, T1-Auto had outsourced its IT department. They retained a management core consisting of the CIO and five managers, but transitioned approximately 80 other members of the department to the outsourcing firm. In 1994, Lotus Notesä was installed as the corporate standard e-mail and workflow platform. A team of four Notesädevelopers wrote workflow-based and knowledge management-based applications. Another team of three administrators managed the Notesä infrastructure. The first workflow application written at T1-Auto was developed for the Finance department. The finance team quickly realized the workflow benefit of streamlining and tracking the capital expense request process. The Notesä development team and the project sponsor, the Controller, worked closely to develop the application. Following this initial success, the power and value of workflow technology caught on quickly at T1-Auto. One of the most successful projects was the Electronic Lab Testing Process described in this paper. The Electronics Lab and Testing System (ELTS) was identified as a Transaction Workflow problem by the IT Lotus Notesä team. Because the ELTS involved policies and procedures that crossed many groups and divisions within T1-Auto, and since the process was consistent across the organization, the solution lent itself very well to Lotus Notes. However, while T1-Auto was experiencing rapid growth and the number of tests was increasing, the testing process was prone to communication and coordination errors. As part of their production and product development processes, their electronics laboratory was required to test electronic components that were part of the brake systems. Clearly the testing process was critical to T-1 since delays or errors could adversely affect both product development and production. The case goes on to describe the design and development of the Lotus Notes workflow management system. The design description includes process maps for the as-is and the new system. In addition, descriptions of the testing phase, the pilot, and the roll out are included. The case concludes with a discussion of project success factors and planned future enhancements.

Complete Article List

Search this Journal:
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