Criteria used by CIOs for acceptance of ERP projects

The ERP project acceptance is a question that every CIO needs to think about at the beginning of the project. In line with the purpose of "starting from the end" and the project acceptance criteria, in fact, it is necessary to build a "ruler" to verify the success of the ERP project. But now we can see that many ERP projects do not have a clear success scale in the early stage of the project. As a result, after the ERP system is launched, both companies and software vendors are struggling: is the system successfully completed? Even the issue of acceptance is repeatedly entangled.

How Should CIOs determine whether an ERP project is successful? That is, what is the acceptance standard for the ERP project?

We can also set the project success "scale" in the following ways ":

1. Has the system application scope reached the initial goal? Generally, the project pilot and promotion scope will be agreed at the beginning of the project, such as: group + Shenzhen Branch; Promotion: Beijing and Shanghai Branch. It also specifies which business departments need to apply the system, which can be understood as the scope of the organization involved in the project.

2. Application target acceptance of the corresponding subsystem: for example, for a real estate enterprise's Cost System project, the following goals need to be achieved: 1) execute the contract business according to the formulated target cost and contract plan, serious objective cost nature. 2) Register contract, change, settlement and payment information to form a unified account information platform of the group. 3) form Multidimensional Dynamic Cost Analysis results to support closed-loop cost reporting and feedback mechanisms. 4) register suppliers to form a unified information database of the company.

3. Acceptance of project work results: acceptance of project knowledge assets, such as business solutions, training courseware, and Operation Manual.

4. Acceptance of core business data: acceptance of all core business data of the system based on the Application objectives of the system, such as the cost system of a real estate enterprise, the expected number of entries, the number of actually entered entries, and whether the results of the report are consistent with those of the manual report after the report is output are verified by system data.

5. Business Process acceptance: whether the approval process for the relevant work can be completed in the system, for example, whether the approval process for bids can be carried out according to the Business Process of the enterprise, whether the process has passed the actual business Verification is a matter of attention.

6. System Function acceptance: during the implementation of the ERP project, enterprises will propose some unmatched functions in standard ERP products based on their own business characteristics, these functions need to be implemented through secondary development. Whether or not these development functions have been implemented and passed functional verification also requires a clear goal.

Based on the above six points, the successful elements of the ERP system are basically covered at all levels, so we can naturally evaluate whether the ERP system can be accepted based on these six requirements.