Thoughts on implementing ERP in China
Three years, a long saying is not long, saying short short time. I have been in the ERP field for three years and do three years in a product. Although the distance from experts from this field is still far away, I have continued to sum up, and I will continue to reflect on the success and failure of the project. Here, I want to discuss some key to the development and implementation process of ERP (this article is positioned in some global critical places, I will explore some ERP in another article. detail). Of course, my strength is meager, I can't touch the entire forest of ERP, but I still have to write some trees I have encountered. I hope that everyone can help me continuously improve this article, and help people in the future in future ERP development and implementation. You can add your opinions or suggestions, and even directly pointed out that this article is not good, it doesn't matter, but many people are willing to participate in this discussion.
Let's talk about our projects first, maybe this model is the epitome of millions of ERPs in China.
It is necessary to implement ERP, and thousands of people are headquartered, and there are 3-5 divisions in China. This company has been basically in a manual operation state, and does not have a computer accessibility (finance because of the use of user software, it is an exception). Enterprises have more than 10 years of history, and many process special and some are deeply rooted. So finding a ready-made system can be used directly (no second development). So what to do is to customize a set of ERP systems from the beginning. Let me feel the most, I feel the most, I feel the deepest thing.
Key 1: Preparation for thought
Since the company's business is a new business, the company is up to the leadership, down to the general staff, lacks understanding for ERP.
Leaders may be determined by the following reasons in the enterprise implementation ERP: It is believed that the aid of the computer will benefit the development needs of the enterprise, and even the competitors have begun to implement ERP. However, once you ask if you know how your company should implement ERP, what is the first implementation, which is the key implementation, which is the focus, the early period is ready, the problem may encounter in the process of implementation, there is already some thinking They are stupid. In other words, it is often necessary to feel ERP, but do not know how to implement ERP, how to implement the software development. After deciding to develop, you are a supporting role, to help software development work; and never think, you are the real protagonist, the company implements ERP blueprints to make yourself, you have to become a bamboo.
And the general staff often does not use it; the work changes after the implementation of ERP, and even do some of them do not belong to their own work; implementation of the initial manual can't be lost, resulting in a multiplication of work, even Instead of laid off, the implementation of ERP is in contact with ERP.
People's behavior is often guided by thought, it is not prepared, and even contradicts it, then such an ERP must be implemented.
In the process of conducting ideological preparation, business leaders will find a lot of problems, don't be afraid, big knives are transformed. The ERP implementation process is originally an opportunity to improve the enterprise.
Key 2: The ability to develop teams
The team responsible for developing has a strong team development capability, and it is necessary to have experience in the development of ERP systems.
There is a team development capability refers to the needs of ERP development, detailed design, encoding, testing, and user training can be well grasped. Manage projects from rich project management experience, very responsible people.
The experience of developing an ERP system is to be familiar with at least the ERP field, and what problems may have occurred. It is best to be familiar with the field you want to do. Because there is also an obedience between the field, it is not familiar with this area, there may be some basic problems, leading to a bad design. These very basic design If there is a problem, it may lead to future projects to use it, and it will be like the water in the water - the heavier drags, if all will come, and it is impossible: forming a riding tiger. A good development team is difficult to measure, but there are some necessary conditions. Good teams can communicate well with companies, and a good team can quickly understand the business process of the company. The good team can write a complete document, and a good team can conduct effective testing, and so on.
Key 3: Legal project leader
Enterprises Implement ERP and must have a person responsible. This person must communicate with the development team and coordinate the interior of the company. Maybe the general manager of the company will take this job, or it may be a person to take a person. If it is the general manager, then it is trouble, often he has a lot of things, you can't find it when you want to find him. If you specify a person, then this person must be very familiar with the business process, and people who can speak in the factory. Of course, this person's enthusiasm is also essential.
The project leader of the company is the core character of the success or failure of the project. From the beginning of the project, it can be implemented until the project can be implemented, and this person has a lot. If this person is very senior in the company, then the blessing of this ERP system, it is reversed that such a system will inevitably fail, at least time and then dragging, the last implementation is still not going to change the speed. In the demand analysis phase, he is responsible for people who are more familiar with each department to assist in completing demand. In the project implementation phase, he is responsible for coordination with the departmental manager of various departments, or allocated directly to everyone in the enterprise.
Key 4: Demand Analysis
Before the project begins: there is a process of demand analysis. This process, I think it is the most important place throughout the project. The general ERP system says it is to listen to others. It can be said to include which departments, each department, but it feels easy, very simple. However, why do you have so many systems, so many systems are drooped again? In fact, the procedure to complete the general process is relatively simple. But the company has long since the habit, or helpless, there are too many reasonable, or unreasonable special circumstances. So an experienced team is to ask these special places. The person in charge of the company also wants to assist the development team to let them understand these special places. It is often these special places to most influenced behind.
Key 5: Standardization of enterprise processes
After the development team has a very detailed understanding of all the processes of the enterprise, many teams began to design the process. In fact, there are two important links between this, here is the first, that is, the authentication (one section below will be said). The rationality of certified enterprise processes. In fact, because the company has long been manually dealt, there are many complex work, and they can't do it. This leads to a vulnerability in the process, and the vulnerability is not completed for a long time, it may be a big problem. For a well-managed company, it should be like this, and each link has a supervision mechanism to avoid problems. And each step is reasonable and efficient. Carefully analyze the workflow of the enterprise, will find a lot of unreasonable, low-efficiency, or lack of supervision, and these places may expose problems. Therefore, once these problems are found, they will negotiate with the leaders of the company and some of the main staff, and the two sides reach a consensus to determine a standard, reasonable, efficient process. Some work should be adjusted immediately, and some work is now inconvenient, and it is necessary to have a sufficient consideration for this, so that it will be completed under the aid of the computer. ERP is not a simple computer copy, but to build a reasonable, efficient and supervised operating system. It can be seen that this process is the so-called BPR (enterprise process reorganization) process, BPR does not necessarily mean that overthrowing completely overthrowing the old dynasty, establishing a new dynasty. Any part of the local improvement is part of the BPR. Of course, this step of this step is that the company should be completed before deciding to implement ERP. However, the leaders of the general enterprise are often unfamiliar with the computer, and they are reluctant to change the inertness of the existing process of the enterprise, so this step is required to have a relatively large strength of the project development team to help the company's leadership.
Key 6: Division of projects
After certifying the process of the company, the development team's thoughts moved forward, not only knowing the current work of the company, but also an unreasonable place, that is, an existing system's improvement version. This improved process can also work well with your computer.
Next, it is not a specific design. Things to do, what modules are to be realized. Not all enterprises have to implement ERP, and the project is also divided into phases. On all, there are many things that still can't be prepared, definitely will not succeed (a fat man can't eat a fat). The process generally has a successful, first, in front, the core, the module that does not change easily, and so on for a period of time, and has been prepared for the next stage of the module. Start the implementation of the next phase of the project.
When developing a blueprint, the task of each phase is to be performed well, and the scheme for determining a phased assessment. The task of dealing with the stage is to focus on, so you can enter the next stage: design.
Key 7: Good design
It is finally going to the design phase. This stage is a step in reflecting the design capabilities of development team, there are many experiences (this paper is not in these details, so it is slightly). After the design is designed, you are looking for multi-party personnel in the enterprise to verify.
There must be a global concept, and the design of each stage is part of the overall design, and it is necessary to make a very good integration with the overall situation. There is no global view, there is no timetable, and there is no phase of sexual assessment will lead to the final fiasco of ERP.
Key 8: Preparation for Foreign Enterprises Specific Implementation
After determining the development of the target system, the development team will enter the coding phase. At this time, the other company has a very important thing, that is, the preparation of the initial data, the development team should be prepared in advance with the company's leadership. Because the project is always implemented in a specific time. There is always some initial values when implementing. The warehouse has the initial value of the warehouse, the sales of sales have sales, and financial initial values have financial initial values. You can book the first phase of the project (in the next stage), and then until that day, all previous data is simultaneously entered simultaneously (a unified initial value entry time will decrease a lot of trouble, Of course, sometimes the initial value may be in the same time, and it can only be specifically analyzed in the case. The company's data is often due to long-term manual reasons, although many data is required, but they can't get it. Sometimes it will be surprised, not clearly have a hand-made account, but they may tell you that if this handcraft is going to record in a regular method, it is too much trouble, so how they make it simplified. Simplification, but some results should be simplified. So, to give the company's staff to prepare the data at enough time, otherwise, etc., must not be put into use immediately.
Key 9: Change management
Variation, password. There is no other enterprise that is unchanged in the world.
Some companies have turned away to open a meeting, discussing a lot of basic processes. This conference will not let the development team participate, because the leaders believe that the development team is not company. When the development team puts the program, the program is good, let the user tried, the company's staff told you that 2 weeks ago, the company's meeting has discussed this approach. What can you have, take out anger?
A good practice is that it is necessary to meet the leadership of the company at the beginning, this change is to coordinate with the development team before the decision. In fact, the development team should contact the company in a longer time, in the business implementation of ERP, their situation to the company is very, and far more than the general staff. It is necessary to think of the development team as an important department of the company, and any process changes in the company have to be recognized by the development team.
Key 10: Stage sex assessment
The project is in phaedments, which is done, in order to have an assessment at the end of a phase. Is there anything in the above stage, and what is well processed, what is the problem is not good. How to continue the place where the previous success is improved.
Stage sex assessment is not a processable process, can't graze. This process is a sublimation of the development process. During a stage implementation, it is difficult to have a systematic, theoretical analysis. To truly evaluate this stage, don't make it become a feast.
Good should be inherited, it should be emergency brakes.
to sum up:
To have successful implementation of ERP, you must handle the above critical. If there is some key place to pay attention to not enough, then your ERP may face the danger of failure.
From the above analysis, it can also be seen that the key to the success or failure of ERP is not technical, but management. It is the management of the company itself, which is the management of the development team itself, is the management of the implementation (ie, the management of both parties). Enterprises must have the thoughts of reform, be brave to make changes, adjust, don't be followed, think that ERP is not going to with you. The development team also demonstrates an efficient and high quality group through the timetable, task arrangement. The two sides must cooperate sincerely. Implement ERP is a long-term, twist, hard work, only mutual support, mutual understanding, in order to win this hard battle. Human thinking, ERP laughed. The implementation of ERP, especially in China, and a long way to go. We should continue to think and summarize the implementation of ERP, especially in China's implementation of ERP. Chinese companies implement ERP is a general trend, we all want this road to be more twists!
