Applicability of the capability maturity model for engineer-to-order firms

Most of the well-known management and improvement systems and techniques, such as Lean Production (e.g. Just-In-Time (JIT) pull production, one piece flow) and Six Sigma (reduction in variation) were developed in high volume industries. In order to measure the progress of the implementation of such systems, companies and consultants use reference frameworks, which contain descriptions of best practice processes. The core principles of these systems are applicable in any type of industry or service (e.g. focus on reliability and minimisation of waste). However, the best practice references and other implementation tools are dependent on the context in which the principles are applied. For the Engineer-to-Order (ETO) industry, many of the traditional practices (e.g. JIT logistics or line balancing) are not applicable. In this paper, it is demonstrated that the Capability Maturity Model Integrated CMMI), a best practice reference framework widely used in the software industry, contains practices which are also widely applicable in ETO companies, but that the original model needs to be enhanced. CMMI provides a philosophy, as well as a set of hands-on guidelines and measurable stages for process improvement. CMMI may provide practical techniques to ETO companies which other companies acquire from systems such as Lean Production and Six Sigma.

[1]  Alain Abran,et al.  Software Maintenance Maturity Model (SMmm): the software maintenance process model , 2005, J. Softw. Maintenance Res. Pract..

[2]  Mary J. Benner,et al.  Exploitation, Exploration, and Process Management: The Productivity Dilemma Revisited , 2003 .

[3]  Richard Turner,et al.  CMMI Distilled: A Practical Introduction to Integrated Process Improvement , 2001 .

[4]  David Wilemon,et al.  Software development and new product development: potentials for cross-domain knowledge sharing , 2000, IEEE Trans. Engineering Management.

[5]  Mayuram S. Krishnan,et al.  Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development , 2000 .

[6]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .

[7]  Gary Klein,et al.  An exploration of the relationship between software development process maturity and project performance , 2004, Inf. Manag..

[8]  Thiagarajan Ravichandran,et al.  Structural analysis of the impact of knowledge creation and knowledge embedding on software process capability , 2003, IEEE Trans. Engineering Management.

[9]  Paul Braiden,et al.  Using business process re-engineering for the development of production efficiency in companies making engineered to order products , 2004 .

[10]  R. Andersson,et al.  Similarities and differences between TQM, six sigma and lean , 2006 .

[11]  Kenneth D. Mackenzie,et al.  Processes and Their Frameworks , 2000 .

[12]  Roger G. Schroeder,et al.  Six sigma: A goal-theoretic perspective , 2003 .

[13]  Marjan Sarshar,et al.  SPICE: a business process diagnostics tool for construction projects , 2000 .

[14]  R. Grant,et al.  Environments: Organizational Capability as Knowledge Integration , 2022 .

[15]  M. Hosein Faltah Process audit: from compliance to self-management , 1997 .

[16]  Kevin P. Grant,et al.  Project management maturity: an assessment of project management capabilities among and between selected industries , 2006, IEEE Transactions on Engineering Management.

[17]  Christopher F. Earl,et al.  An analysis of company structure and business processes in the capital goods industry in the UK , 2000, IEEE Trans. Engineering Management.

[18]  Joanne M. Sulek,et al.  Measuring performance in multi-stage service operations: An application of cause selecting control charts , 2006 .

[19]  Christian Hicks,et al.  Supply chain management: A strategic issue in engineer to order manufacturing , 2000 .

[20]  Peter T. Ward,et al.  Lean manufacturing: context, practice bundles, and performance , 2003 .

[21]  John C. Anderson,et al.  Maturity and its impact on new product development project performance , 2001 .

[22]  Jan Olhager,et al.  Strategic positioning of the order penetration point , 2003 .

[23]  Luk N. Van Wassenhove,et al.  Knowledge Driven Quality Improvement , 1998 .

[24]  Matthias Holweg,et al.  The genealogy of lean production , 2007 .

[25]  Watts S. Humphrey,et al.  Characterizing the software process: a maturity framework , 1988, IEEE Software.

[26]  M. Engwall No project is an island: linking projects to history and context , 2003 .

[27]  Peter Axel Nielsen,et al.  Competing values in software process improvement: an assumption analysis of CMM from an organizational culture perspective , 2003, IEEE Trans. Engineering Management.

[28]  Soo Wook Kim,et al.  Disentangling leanness and agility: An empirical investigation , 2006 .

[29]  Noushin Ashrafi,et al.  The impact of software process improvement on quality: in theory and practice , 2003, Inf. Manag..

[30]  Renate Fruchter,et al.  An ethnographic study of design knowledge reuse in the architecture, engineering, and construction industry , 2006 .

[31]  P. Adler The Evolving Object of Software Development , 2005 .

[32]  Graham Winch,et al.  Models of manufacturing and the construction process: the genesis of re-engineering construction , 2003 .

[33]  Colin Herron,et al.  A methodology for developing sustainable quantifiable productivity improvement in manufacturing companies , 2006 .

[34]  Lauri Koskela,et al.  Should project management be based on theories of economics or production? , 2006 .

[35]  Mary Beth Chrissis,et al.  CMMI: Guidelines for Process Integration and Product Improvement , 2003 .

[36]  Luis F. Alarcón,et al.  Construction process improvement methodology for construction projects , 1998 .

[37]  Andrew Davies,et al.  Building Project Capabilities: From Exploratory to Exploitative Learning , 2004 .

[38]  Ossama Salem,et al.  Lean Construction: From Theory to Implementation , 2006 .