Introduction
The concept of ERP’s customization
Luo (2004) | Brehm et al. (2001) | Glass (1998) | Hong and Kim (2002) | |
---|---|---|---|---|
Configuration | Configure the modules of the innate ERP to represent the business process of the organization | Regularize the modules of the innate ERP to reflect the functionalities of the organization | Choose in the beginning the concerned processes and set the parameters of the innate ERP | |
Modification | Modify the source code of the innate ERP | Modify the modules code to produce a unique business process | The user changes the source code of the innate ERP | Modify the source code of certain modules |
Adaptation | Includes the configuration and the modification | Synonym of customization | ||
Customization | Includes the configuration and the modification | Synonym of configuration | Settle the values of the tables and choose the concerned processes | Does not change the identity of the ERP (at the same time synonym of configure) |
Extension/service supply to the user | Program an additional software in an open interface | Implement the local solutions | Fill the gap between the functionalities of the ERP and the needs of the organization |
Reasons leading to customization of ERPs
Critical factors of success for the implementation and the customization of ERPs
Critical success factors | Used terminology and bibliographical references |
---|---|
Engagement of the direction | Engagement and support of the direction (Sherry Finney 2007; Badewi and Shehab 2015); the implication of the direction (Moon 2007); support and engagement of the direction (Dezdar and Sulaiman 2009; Saade and Nijher 2016); support of the direction (Shaul and Tauber 2013); experience project manager leadership (Osman and Abd-El-Kader 2018) |
Users involvement | |
Management of change | Management of cultural change (Sherry Finney 2007; Osman and Abd-El-Kader 2018); balanced and acquired company settings (Moon 2007); management of organizational change (Moon 2007); program to manage change (Dezdar and Sulaiman 2009); experience of a major organizational change (Shaul and Tauber 2013); preparation atmosphere for the organizational change (Saade and Nijher 2016) |
Support to the project | |
Reengineering of the business process | Reengineering of the business process and software configuration (Sherry Finney 2007); alignment of the business process (Moon 2007); process reengineering and minimal customization (Dezdar and Sulaiman 2009); reengineering of the business process (Saade and Nijher 2016; Osman and Abd-El-Kader 2018) |
Communication | |
Training and education | |
Implementation team | Balanced team (Sherry Finney 2007); composition of the ERP team, competences and compensation (Dezdar and Sulaiman 2009; Osman and Abd-El-Kader 2018); competence of the team project (Shaul and Tauber 2013); champion of the project (Sherry Finney 2007); skilful decider (Sherry Finney 2007); small internal team of the best employees (Saade and Nijher 2016) |
Usage of consultants | |
Implementation strategy | |
Selection of the ERP | |
Management of the project | |
Quality management | |
Risks management |
Types, approaches, life cycle, models, methods, and techniques of customization of ERPs driven requirements engineering
-
The decision of adoption to satisfy their work needs and techniques, organizations start questioning about the necessity of an ERP system. Actually, the literature on ERPs touches many aspects linked to the adoption of the ERP in a context and the environment of small and medium enterprises;
-
Acquisition it refers here to the selection of suppliers and the acquisition of the ERP. This is subsequent to the evaluation of requirements of the organization, of modules of the ERPs and of the suppliers;
-
Implementation concerns the real settlement of the ERP system. This step has many activities, like the customization of the system to conform itself to the needs of the organization, the reengineering of the work process, the migration of data, the formation of the final user, etc.
-
Use and maintenance the final user starts using the system daily, which implies a daily maintenance;
-
Evolution implies the extension and the integration of the ERP system with the other systems as the management of customer relation, of supply chain, etc. It is a non-trivial operation that requires the stability and the maturity of the ERP;
-
The withdrawal corresponds to the step, where the system is abandoned or replaced by another system of Information.
-
A selection of an ERP to minimize the needs of customization for answering already to most of the needs of the organization;
-
The flexibility of the ERP to adapt itself to the evolution of the needs of the organization.
-
doing an abstraction of the existing functionalities of an ERP, create a link between the awaited functionalities and the existing ERP;
-
effectuate an alignment at the level of needs;
-
deduce the aligned functionalities, adaptation and extensions of functionalities chosen using the awaited functionalities of the ERP and the functional links.