Demand-driven and process-driven, is the ERP in the development of the concept put forward two different times. However, I think the needs and processes are twins, there is no essential difference. Or, more precisely, to grasp needs should understand the process from the beginning. Apart from process to talk about needs? Demand-driven and process-driven, is ERP development two different times during the proposed concepts. However, I think the needs and processes are twins, there is no essential difference. Or, more precisely, to grasp needs should understand the process from the beginning. Apart from process to talk about needs? Not. On the one hand a wide range of business needs, very fragmented, there is no process that a line to the needs of a tiny link, then the demand will be difficult to manage. Second, demand is also carried out around the process, or that demand is only in business management processes in this context, it has a practical significance. Leaving aside the demand process to talk about, as if aside comment on the historical background of the same historical figures, it is difficult to achieve "reasonable" of this basic requirement.
So, I think, whether it is process-driven, or demand-driven, to grasp the needs of business must be based on the management and business process management processes using this line to tap the business needs. With the more professional words, should focus on business needs and processes, process the corresponding rules and regulations, process the corresponding algorithms, processes corresponding to the input and output, the transmission of messages and other aspects.
Specific say, grasp the understanding of process requirements from the beginning, mainly to achieve the following three areas.
Research needs will be met and process carding a depth issue.
Workers in well-digging depth is fancy. Dug too hidden, well water is not clean; digging too deep, well water contains too many minerals do not taste good. Not dig very deep and shallow well water before you eat.
Demand for research and process comb is the same one truth. Carding process have a certain scale, scale a bit deeper into a dead end, and the formation of negative demand; scale shallow, and they can not be fully reflected in the needs of users, it can not serve as basis for our implementation of the project. Therefore, to grasp the depth of combing business processes, is that we have top priority for business needs.
One is that the important and commonly used process. Processes such as sales orders, purchase orders process, accounts receivable accounts payable processes and so on. Enterprises in the daily management of such processes often need to use, and that these management processes are also directly linked with the enterprise funds. If the good management of these processes, it is equivalent to most of the asset management businesses better. Therefore, we demand at the time of research, based on these processes, these processes are related to the needs of good order, then the task of research also needs to complete one half of the.
The second is important and not commonly used in management processes. Change processes such as sales orders, purchase order change process, product information changing process and so on. These management By contrast, in the enterprise does not always occur only in certain circumstances, these processes will precipitate events. However, these things happen, then one, if we are dealing with is not good, it will bring to the enterprise relatively large losses. Change processes such as sales orders. Upon Customer's sales order changes in demand, we do not have time to change this situation in order for feedback to the production or procurement department, the only damage caused by enterprises themselves. Therefore, these important and not commonly used processes, but also directly related to the corporate agenda aside. Therefore, the demand associated with these processes, but also the focus of our attention needs to be.
|
