The premise that the distribution product can be used by users

We have been working on the distribution supply chain system, which is what we call DCM and what others call DRP. the distribution supply chain has many distribution stores throughout the country. It is inconvenient to achieve centralized management of the C/S model. in the B/S mode, data can be directly transferred to the server at the headquarters for unified control. the boss does not need to collect data from various places. No matter where he is, he can only access the computer to view the operations of various places and the entire company. This sounds beautiful and looks amazing, however, if this system is to be used accurately by customers, I think it should at least reach the following points:

1. Powerful data collection function at the beginning of the period.

All companies cannot be established only after the birth of distribution products. The first e-based product they adopt is unlikely to be our DCM, from MIS to MRP to MRPII, ERP, many companies are step-by-step implementation of enterprise e, and a large amount of initial data must be imported into the DCM system. If you cannot easily import the data from the original system of the enterprise to our DCM system, DCM will lose its meaning because the initial data is wrong, can you expect DCM to run properly?

Generally, the customer is happy to organize the Excel, because many systems can export data to the Excel and then import it to our DCM. Since the customer is keen on organizing excel, we need to provide a standard Excel format for the customer to organize data. Of course, we now want consultants to sort out the initial materials in our system, but it is impossible to make products by relying on consultants. A real product should include a setup.exe, and then the consultant will train the customer to use it. The road is long ......

2. Real-time Data Update capabilities.

When supporting customers, they found that they used a lot of dirty data in the original system. For example, if a person is no longer there or has been transferred, the data stored in the system is still old data, this results in a large amount of dirty data. If dirty data exists in the system, the operation of the entire system will be greatly affected.

In particular, the promoter management system, due to the large flow of personnel, may still belong to this outlet today, and will belong to other outlets tomorrow. How do I settle my salary? How to consider the cost ownership during cost accounting? Salary is generally settled once a month. What is the real business process for some temporary promoters? Is it just a few days of employment, or is it another way? It is possible that a large batch of people will be called for promotion in a short period of time, but will be disbanded after the promotion ends. Is it necessary for such a batch of people to be recorded in the system for record filing? If you do not enter the system, how will you calculate your salary in the future? However, is it necessary for some people who only appear once? A lot of things do not have a good flexible processing method. It is not easy for the system to do so now. What is the real use of the customer?

For users of some systems, they are generally internal staff or sales personnel in various offices. They must be able to accurately and immediately respond to changes of these personnel. Of course, in the real business, the customer will also file for such a situation. The system should be able to send a notification to the headquarters its administrator for unified change of system users for such personnel changes, or adopt other methods, but ensure that the system can be updated in real time.

3. Complete data statistics functions

The data entered on the system interface does not have a statistical function. Although data under this condition can be obtained based on a certain query condition, no statistical summary is taken. Such data is of little significance to customers. That is to say, we only get some daily work input flow accounts through the interface, this function is necessary, the data is the source of future statistics, it is difficult to make it easy. The requirement is refined to the specific operator. What data does he want to see after work every day? The statistics of the data are meaningful to him.

For example, the clerk who ships the warehouse enters many documents every day. On the operation interface, he can see one of the documents he shipped today. After a day's work, he may want to know the total quantity and amount of his shipments today? A month later, he needs to know how much he has made and how much he has earned this month. These are common requirements. We now attach great importance to the functions of the operation interface, but regard the most important report function as the response header. I think it is necessary to improve the status of the report. It should not be used as a scanning job after development. In addition, the report requirement must be communicated with the operator and the report viewer, what do they want to see. I feel that RD is very poor. I stare at the requirement document and look for fields from the database like reading tianshu. I don't know what it means to connect the tables. This status is not acceptable. In addition, the current report development mode is too inefficient. The number of reports requested by the customer should be huge, which should be similar to the number of Operation interfaces. Of course, we can ask the customer to compress the requirements, however, from the perspective of the product, the report cannot be compressed, so you must add a lot on your own.

The current report implementation method urgently needs to be changed, and the development efficiency is low. What is presented to the customer is not intuitive.