This article is divided into two parts: experience and practice. The experience part shares some core ideas and theories, and the practice part decomposes the construction process of the entire software system into steps.
Experience part :
**Cure first, then optimize
Use the functions of the software first, ignore some operational details, and the process goes through, then let’s talk about operational details
**Think about the purpose of deploying the system, and what problem does the system solve for the company?
**Function first, operation later
Different ERP systems will have differences, the first thing to consider is whether the functions of the ERP system can meet the needs of the company
**When customizing development, formulate the approximate time node and implementation steps, develop one piece at a time, and test one piece at a time.
**ERP is to solidify the process into the system. When the process is very clear, go to the ERP system
**When drawing a process, list all the flows and solutions of the process, and finally form a closed loop. If the list is not comprehensive, there will be problems in the execution process. If the closed loop is not formed, there may be three areas
**The process that is solidified into the ERP is preferably a process that changes infrequently. Frequent changes in the process, the input-output ratio is too low
Practical part :
1. What is the purpose of a company deploying an ERP system?
Output: The purpose of deploying an ERP system
2. Does the ERP system functionally meet our needs?
3. Discuss and draw detailed business processes
Output result: business process diagram
4. Develop a general framework for implementation and set time nodes for each sub-goal
Output result: time node table
********************************Enter basic data**************** *********************
5. Determine the basic data to be entered into the system, including static data and dynamic data
Static data: material table, employee information table, customer table, supplier table, etc.
Dynamic data: purchase order, sales order
Output result: basic data of various types
Reference: https://wenku.baidu.com/view/d782be00f5335a8103d22016.html
6. Work with the implementation engineer to determine the header of the basic data (some fields are required by the system, some are required by the company, and should be integrated together)
Output result: EXCEL table with standard header
7. Together with the implementation engineer, give a detailed description of each header and make notes
Output result: basic data entry manual
8. Arrange personnel and prepare basic information according to the standard format EXCEL table
Output: Basic data table with complete information
9. Enter the basic data into the system and test
********************************Document Development**************** ********************
10. Confirm the headers of various documents, such as purchase order, purchase receipt, sales order, sales issue, etc.
Output result: document in standard format
11. Find out the related documents in the business process. According to the related documents, mark the headers of the documents, which can be divided into the following types
- unquoted/quoted
- Required / not required
12. The initial entry time of the purchase order should be the same as the initial inventory time, otherwise it will appear: The inventory has increased, and the purchase order has no sales order
13. There should be 2 modes for single entry, mass entry and single entry
Scan code entry is more convenient
The most convenient is to customize the development of the document import function, and obtain data directly from the excel sheet to reduce human factors
14. The data source is unique, and can only be entered and modified in one place. For example, the purchase price can only be modified in the purchase order, and can be viewed during storage, but cannot be modified.
15. ERP should achieve several effects, either saving manpower or improving data accuracy with the same personnel
16. ERP implementation engineer, the most basic thing is to solve the problem, and the further step is to guide the customer how to carry out the work, and help the customer to avoid the problem, so that the whole process is as smooth as the water flow
17. The bigger the company, the more demanding the group has on the timely and accurate data specification, and the more rigid the software, why? With so many subsidiaries, it is impossible to take care of every subordinate, and the subordinates can only adapt. As long as the leaders above get the correct reports on time, they don't care about working overtime and entering data.
18. There are three categories of input data, the beginning of the inventory period, the beginning of the receivable period, and the beginning of the payable period, and the dates must be the same, otherwise there will be discrepancies in the information
Ensure that logistics and cash flow data are consistent
19. There should be two modes of data entry, one is single entry, the other is mass entry (very important, otherwise people will be exhausted)
20. Develop a project schedule, split tasks, arrange the person in charge, and achieve clear responsibilities
21. Seek help from your boss, hold a meeting to make a plan
22. Establish a good communication channel with Party B's erp development engineer, Party A and Party B are actually equal
23. Create training documents for each position
24. With the development of the project, the real demand is actually very huge, it is necessary to discuss frequently, and establish a list of requirements, and check them one by one.
25. Sales, finance, logistics, each position operates in different links, and their best perspectives are also different, so there are two sets of perspective modes, user perspective mode and administrator perspective mode.
In the user perspective mode, only the data related to the position is displayed, and other irrelevant data are hidden
In the administrator's perspective mode, display all data, and can manage whether the data is displayed or not
26. After deploying the ERP system, the company should have a person who is dedicated to connecting with the software company and familiar with all ERP operations first, so that after the project is over, simple daily maintenance work can be carried out