The humble task of the definition of ERP implementation much easier than up. The most pragmatic business leaders may be, or indeed in order to achieve more outstanding ERP task becomes impractical.
Constantly emphasize is this: no matter how flexible ERP system, can only support functions to the function, vertical to the vertical plane of the relevant changes, in addition to does not work.
To ensure the global relevance of ERP
ERP system, if the over-extended to every possible direction, sooner or later will be transformed into a loose combination of several similar subsystems. From that moment, the global association began to fall apart. The enterprise ERP advocates and users aware of the error is too high expectations, they have been unable to stop this process has been.
In order to understand what kind of power led to people, processes and platform collapse, or, more precisely, what kind of missing the power, first of all need to know that ERP is a distributed computing framework. Thus, ERP platform, there is no legacy as the core of the computer system. The free-floating structure is very flexible, but very vulnerable. Flexible ERP interface means that it supports the new extension of the field of information, but the ever-changing information that has undermined the stability of the flow of information is available. Content is too hastily, without thinking carefully added, the content is only useful to users on a small aside, for most other people are meaningless, even lead to confusion. Another often happened, the former wide range of relevant information, and now have been abandoned due to poor maintenance. The result is a demonstration for company-wide, up to the local users to provide limited services to effect, the worst case scenario is that this should get the maximum benefit of senior managers to no avail.
Imagine if the network shows the multi-year business relationship with the companies do not have information on vendors, or to change the address of the vendor information, or to be acquired vendors of information, or to change the name after the merger vendors of information, or the combination of all possible vendors for more than information, the results of what would happen? In addition, responsible for authorizing payments to vendors may contact the staff out of date, this is a problem.
If you do not know the specifics with vendors or customers which representative, did not know which vendors or customers on behalf of the contact with the company, your ERP on a global association behind them. Digitally input information in a very easy start, but if it is not in accordance with the mandate of the need to show to the user base to use, or information pointing to the wrong person the wrong, this information will quickly become useless information.
To solve the delay problem ERP challenge is how to ensure that personnel within the enterprise - as well as regular communication with external parties within the enterprise - have as expected action. To ensure consistent behavior and expect a simple way is to give employees rights, capabilities and responsibilities of the ERP in real-time updates of personal data and information. In this way, everyone know who is what kind of data and processes responsible for what, thus maintaining the overall relevance of the ERP.
Of course, solve the ERP synchronization issues can not be all that simple. There is such a company, it relies on subcontractors for the 30 countries to customers in the local service delivery. Received on time because they are always unable to invoice, the company failed to timely payments to subcontractors. In fact, delayed receipt of the invoice, 40% were wrongly sent to the customer at the local office, and then transferred to the new central processing center. Moreover, 25% of the invoice are not necessary for timely payment order number. The results, by about 50,000 invoices an audit found that 30% of them because of sub-contractors can not wait for the repeat issued. The result is a large number of accumulated can not take advantage of information lead to "purchase and pay" channels ERP stagnation. In turn, there has been confusion and delays in the time series of problems.
|
