China 
Africa 
Explore chapters and articles related to this topic
Two Paradigms
Published in James E. Luckman, Olga Flory, Transforming Leader Paradigms, 2019
We are not the only ones to be critical of fad programs. Geoffrey James, a writer and a contributor to CBS’ MoneyWatch, put together a list of the stupidest business fads of all time. In no particular order, here are some of them: Six Sigma, an approach to quality management created by Motorola.Business Process Reengineering—used to analyze business processes and rework them to achieve a defined business outcome.Matrix Management—an attempt to combine direct and dotted reporting relationships.Management by Objectives—evaluation of employee performance against a previously agreed upon set of objectives.Core Competency/competencies—focusing on what a company does (wants to do) better than anybody else and identifying critical skills needed to succeed.
The Systems Integration Life Cycle: A Reengineering Approach
Published in Michael A. Mische, Reengineering, 2017
Integration process acceleration is accomplished through the combination of several techniques that are implicit to the process-driven methodology. The process-driven approach to systems integration achieves the rapid deployment and delivery of integrated systems by using many of the reengineering concepts that are applied to business processes and the principles of concurrent engineering. The major principle is to view the systems integration project as a continuous and harmonious process rather than distinct or separate pieces that somehow must fit together. In this regard, the PDIM has the following key attributes: Use of concurrent engineering practices and techniques.Adoption and adaptation of business process reengineering principles.Front-loading of critical human resources into the design and assessment stages of the integration process.Use of quality function deployment (QFD) techniques to ensure that design changes are recognized early in the integration process and are minimized later in the effort to help ensure efficiency.
Six Sigma Body of Knowledge Outline: Full Narrative Version (SSD Global Solution Version 6.1)
Published in Terra Vanzant Stern, Leaner Six Sigma, 2019
Business Process Reengineering is an approach intended to elevate efficiency and effectiveness of an existing business process. BPR is also known as Business Process Redesign, Business Transformation and Business Process Change Management. BPR supports the following methodologies for process improvement: Process IdentificationReview Update As-Is StateDesign To-BeTest and Implement To-Be
Using cloud computing integrated architecture to improve delivery committed rate in smart manufacturing
Published in Enterprise Information Systems, 2021
Ting Xia, Wei Zhang, W.S. Chiu, Changqiang Jing
Step 1. User requirement collection: software project is user requirement collection. Step 2. Business Process Reengineering: when software project collects user requirement and system design, there is a need to Business Process Reengineering many times.Step 3. Integrated Architecture development: after implementation, software need to integrate hardware architecture for development.Step 4. Solution examination: when complete, coding system needs solution examination more times to confirm system work.
Reconciling engineer-to-order uncertainty by supporting front-end decision-making
Published in International Journal of Production Research, 2019
Iain Reid, David Bamford, Hossam Ismail
An established modelling technique, Integration Definition for Function Modelling (IDEF), is a compound acronym (Icam DEFinition for Function Modelling), where ‘ICAM’ is an acronym for Integrated Computer Aided Manufacturing, a well-tested language, and comprehensive systems modelling technique (Chin et al. 2006; Waissi et al. 2015). The IDEF modelling technique is designed and developed to facilitate understanding, as an instrument for business process reengineering (Soung-Hie and Ki-Jin 2002). It is considered one of the strongest modelling approaches for the support of complex systems (Yigit and Allahverdi 2010) and is therefore suitable for representing process flow descriptions of the complex and intricate processes in an ETO supply chain. IDEF adopts a probing approach for capturing the process characteristics in a qualitative format and provides the platform for identifying the resources, in terms of inputs, controls, outputs and methods (ICOMs) through a connecting network that ties the processes together (Ismail et al. 2007). It presents a clear description about input information, output information, and resources of a process concerned in a hierarchical and systematic way. Furthermore, IDEF employs a top-down method that starts from general activities and moves into more specific process issues, providing a means to capture the ‘as-is’ model shown in Figure 2.
Combining design science with data analytics to forecast user intention to adopt customer relationship management systems
Published in Journal of Industrial and Production Engineering, 2019
Chih-Hsuan Wang, Ching-Yu Lien
Enterprise information system (EIS) is a particular information system which focuses on business process reengineering by integrating various functions of an enterprise to achieve the goal of decision support [1,2]. In reality, the EIS must be used by all departments of an enterprise and all partners of a supply chain. Typical benefits for a company in adopting an EIS include time and cost-saving, enhancement of operational efficiency, identification of business opportunity, process improvement, and performance management [3,4]. Although several benefits have been reported from the adoption of the EIS, managers or practitioners are still skeptical of adopting EIS in their firms. Typical reasons are illustrated as: (1) people are usually reluctant to change due to inertia, (2) platform interface is not easy-to-learn, (3) lack of clear business goals to convince the top management, (4) difficulty in tailoring customized EIS to meet the requirements of business process, and (5) problems in integrating legacy systems or heterogeneous databases [5,6]. In general, user satisfaction usually leads to willingness to adopt and repurchase and frequent word-of-mouth recommendation [7,8; 9].