ERP project experience summary

ERPProject Experience Summary

Purpose: To summarizeERPProject implementation experience to refine Project risks. Including personnel, organizational structure, management system,ProgramFiles and other aspects provide reference for other projects to avoid risks.

1The biggest feeling of the project is that the architecture is determined by strategy. The senior leaders of the Project Implementation Department should not authorize others after the project is launched. It is best to be able to work with each other and must be implemented in place, in this way, the project can be better promoted and implemented.

2Senior leaders, especially leaders, should also participate in the project at the initial stage and in the blueprint stage, the problem can be solved or relevant rules and regulations can be formulated in a timely manner at all stages of the project or when a leader needs to make a conclusion. Otherwise, the problem will be accumulated and cannot be fundamentally solved, this affects the progress and quality of the project.

3The consciousness of senior leaders is very important. Only the leaders can push forward projects from top to bottom, so the project can be promoted very well. So the focus of the project is how to improve the leadership consciousness, how can leaders truly promote projects.

4If it is a small project, because the business scope is relatively small, there is no need to set up too many functional departments, so that the power is not very scattered, to avoid inter-department occlusion, mutual responsibility, it can also clearly establish relevant work in the project and solve problems better and faster.

5It is best for each project to formulate the corresponding management system at the blueprint stage as much as possible, otherwise the project will be put on hold after it is launched; the promotion of the project should be conducted by a dedicated person or a dedicated department, this will be more conducive to promotion.

6It is best to start from the blueprint stage for end-user training, which helps to modify various habits in the early stage, start with the implementation of software and project principles, and publicize the process, key users can view problems from the perspective of the project, so as to better implement the project and increase the project success rate.

For example, for external inspection, procurement and other departments, if they do not understand the blueprint, they are still responsible for their own affairs, or follow their original procedures, the project will not be smooth, and there will be controversy. After all, we had a habit in the early stage and used it for a long time. We were familiar with it. If we didn't understand the blueprint, we wouldn't really change our habits.

7The regular meeting system in the project stage, especially in the early stage, should designate the responsible person, and the responsible person should be the person with strong speech, and urge the responsible person to communicate with each other and understand each other's business and practical difficulties, it can be conducive to project promotion and better implementation of the project.

8System operations will feel tired compared with the manufacturing department. First, let them understand the meaning and benefits of the system for the entire company, so as to prevent complaints from looking at problems only from personal and one-sided perspectives, so that it can be well controlled in terms of cost and process balance.

9Report the work progress and difficulties encountered in the work with senior leaders, from the perspective of systems and projects, we can understand why some seemingly feasible requirements cannot be achieved in the actual implementation and operation process.

10The accuracy of primary data maintenance plays a vital role in subsequent work. You can't just say it is right, it plays a leading role in the later stages of cost and inventory precision and accuracy.

11The degree to which key users and end users understand the business and system is the key to the success of each project. Therefore, the training for key users and end users should be strengthened, only when the business department is willing to learn and accept can it better solve the problem and reflect the value of the project.

12It is best to perform a simulated trial run for each project before it is launched. First, check whether there is anyBugSecond, the user's knowledge about the system can better expose the problem and increase the project success rate.

13External Implementation of the company's capabilities is crucial to the project. The way of bidding should be done, so that all bidding companies can explain the scheme and relevant departments can participate in the bidding, the Project Manager and consultant of the winning company should have an interview, and the consultant must communicate with the first-line department to understand the business and avoid repeated changes to the development scheme.

14The requirements for participants of the relevant project departments must be the backbone of the business and must be full-time. Full participation is required. Therefore, it is recommended that the project initiator be the department of the project, in this way, they can have a higher sense of responsibility and be more active in the project.

15Regardless of any project, the project objectives must be clear, and once the project objectives are clear, they cannot be changed at will, you must consider whether the changes can be made from the perspective of project risks.

16Project goals cannot be set too high. We need to consider the basis. In order to make the project advance as soon as possible, it is best to just change the habits of business personnel, rather than looking forward to a project that will bring dramatic changes to the company, it will be able to take a new look. For example, the success rate of foreign countries in Europe and the United States is very high. In the final analysis, the reason is that their project cycle is long, implementation is a little bit, and the business department changes a little bit, in this way, the implementation can be very good and solid.

17Key users must have a real grasp of the system, and key users should be trained to end users, so that key users can independently solve some daily qualifying problems, instead of finding an internal consultant when a problem occurs.

18In the blueprint stage of the project, it is best to determine the assessment system after the project is launched. If the initial stage is not specified and the implementation of the project has been officially launched, it is easy to implement it. The detailed rules should be put into the detailed responsibilities of each department.

19The best way for project end users to truly use, understand the system, and better operate the system is to train key users, training for others is also the best way to improve your own level.