## 6 Development Data-Driven Implementation Methodology
### Proposed Methodology  
The proposed methodology fills in the existing gaps in the standard ERP system implementation methodology needed to properly implement the forecasting module. The methodology has been initially proposed in Ref. [20]. In particular, there is a lack of elements that will enable a rapid prototype to confirm the required accuracy of the forecasts. The methodology also needs to be phased according to the IFS Application implementation methodology, as the module being implemented is part of the IFS Application implementation. Standard stages do not include elements that are necessary to implement the forecast module:  
1. **Formulation** of the forecasting problem;
2. Analysis of prognostic premises;
3. Establishing data **requirements**;
4. Data collection;
5. Data analysis-understanding data;
6. Data processing;
7. **Modelling**;
8. **Evaluation**;
9. **Implementation**;
10. **Feedback**. \begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt}} \hline \hline
**Author(s)** & **ERP Implementation Model** \\ \hline [PERSON] et al. [31] & (1) Focus, (2) Creating As-Is picture, (3) Creating of the To-Be design, (4) Construction and **testing**, (5) Actual Implementation \\ \hline [PERSON] [32] & (1) Initiation, (2) Requirement definition, (3) Acquisition/development, (4) **Implementation**, (5) Termination \\ \hline [PERSON] and [PERSON] [33] & (1) Project chartering, (2) **The project**, (3) Shakedown, (4) Onward and upward \\ \hline [PERSON] [34] & (1) Initiative, (2) Evaluation, (3) Selection, (4) Modification, Business process Re-engineering, and Conversion of Data, (5) **Training**, (6) Go-Live, (7) Termination, (8) Exploitation and Development \\ \hline [PERSON] and [PERSON] [35] & (1) Planning, (2) Project: setup, re-engineer, design, configuration and **testing**, installation, (3) Enhancement \\ \hline [PERSON] and [PERSON] & (1) Review the pre-implementation process to date, (2) Install and test any new hardware, (3) Install the software and perform the computer room pilot, (4) Attend system training, (5) Train on the conference room pilot, (6) Established security and necessary permissions, (7) **ensure that all data bridges are sufficiently robust, and the data are sufficiently accurate**, (8) Document policies and procedures, (9) Bring the entire organization online, either in a total cut over or in a phased approach, (10) Celebrate, (11) Improve continually \\ \hline Verviell and Halingten & (1) Planning, (2) Information search, (3) Selection, (4) **Evaluations**, (5) Negotiation \\ \hline IFS Implementation Methodology & (1) Initiate Project, (2) Designing the solution, (3) Preparation of the solution, (4) **Implement Solution**, (5) Go Live. \\ \hline INFOR Deployment Method & (1) Inception, (2) Elaboration, (3) **Construction**, (4) Transition and Optimize. \\ \hline MICROSOFT Dynamics Sure Step Methodology & (1) Diagnostic and Analysis, (2) Design, (3) **Development** and (4) Operation. \\ \hline ORACLE - A.I.M. (Applications Implementation Methodology) & (1) Definition, (2) Operations Analysis, (3) Solution Design, (4) Build, (5) **Transition**, (6) Production. \\ \hline SAP–ASAP methodology & (1) Project Preparation, (2) Blueprint, (3) Realization, (4) **Final Preparation**, (5) Go Live Support, (6) Operate. \\ \hline \hline \end{tabular}
\end{table} 
Table 1: ERP implementation methodologies both described in the literature and in the ERP leader vendors own methodology are suited to implement transactional but not analytical modules with migration of a small sample of data for business process testing [29,30]. These elements should be properly integrated into the standard methodology. Below are the standard stages of the implementation project supplemented with elements specific for the forecasting module (see Figure 4). **Stage 1**  
The first stage of the project is to **define the project**.