| Essay which doesn't come to end | message | search | history | definitions | русский | |||||||
|
ERP in logistics Pages: 1 2 3I wished to write the treatise on the subject of «SAP in technologies 3PL, 4PL logistical providers». Was not in time. Financial crisis has burst. However if to replace SAP on ERP with licences GNU (free, with open codes), probably, it is possible to state my reasonings. The matter is that the draught copy of this article has been written one year ago. Till the present moment of possibility to finish the article to mind, at me was not. Now such possibility has appeared.
This history has begun several years ago. It has begun with a banal question which I have set to myself. Having behind shoulders successful experience of a management by working out, introduction and operation of an information system for logistics in architecture "client-server" (a logistical information system - LIS), I have understood, that me as the project leader, quality of management does not satisfy with changes. This effect in discrepancy of speed of reaction of updatings of system and changed environmental conditions of business was showed. I would say, an increasing lack in technology of system from requests of the logistical market. The reason was banal - scrappy automation, and add here constantly increasing requests on efficiency of management of changes. Familiar history, isn't that so? I have not thought up anything new how to carry out own analytical researches on the subject of as it is possible to solve this problem. The answer - ERP. It is natural, that me the most known interested world ERP systems (for example, SAP ERP, Oracle e-Business Suite, MS Dynamics NAV/AX, Epicor/Scala, Baan). At the first stage it was important to understand, how in ERP to system it is possible to automate business processes of carriage consignments. For achievement of this purpose I used two principles. Studying of main principles of construction ERPII (in parallel with allowance for requests of own logistics). And the analysis of existing world branch decisions and experiences on the basis of the mentioned software. To convince itself that use ERP of systems for automation business of processes 3PL logistical providers the correct and effective decision has appeared business simple (I even has constructed simple model for MS Axapta). Now it was necessary to convince colleagues of correctness of my ideas. It has appeared much more difficult. The basic complexities were the following. My colleagues were not professionals in the field of information technologies that demanded the explanation of main principles of construction ERP of systems in language clear it. And it is valid than use ERP differs from classical principles of management working out of the software? For what it is necessary to pay the big money if programmers program what will order to them? The following serious problem. This occurrence of several stable myths about ERP which to me should be denied during the project for choice systems (further I I will describe them in details). The reasons of occurrence of myths the following - unsuccessful experience of "neighbours", absence of branch experience. Absence of branch experience (3PL logistics) to operation ERP of systems in Russia led to some uncertainty of interpretation of our problems the consulting companies participating in the project for choice ERP system. Uncertainty gave bad effect of tearing away of systems as "inappropriate" to business requests. The reason is banal. The majority of the consulting companies which had experience of automation of separate directions of logistics on platform ERP, presented it as the universal decision. It not so. Such situation irritated my colleagues (-irritated) as offered decisions mismatched their requests though were declared in quality of full-scale systems for automation of logistical activity. It is natural, that on idea of additional programming ERP on the basis of our technical project, the sensible objection sounded, that we are able to do it. However not all so is bad. As I have understood, that have come not from that party. We tried to find ready decisions from the bottom of a technological chain (front-office). But ready decisions on automation of operative activity was not (today them too a little). Then I have changed tactics. We began to consider ERP system as a platform for construction of full-scale system for automation back-office. After that the situation has considerably improved. ERP technologies have ceased to seem incompatible with logistics, including for colleagues. More interesting result was received with technologies BI (Business intelligence). But about it I will write in other article. Let's return to myths which accompanied the project for choice ERP systems. Partly at the analysis of myths in the conditions of financial crisis it is possible to consider decisions on the basis of the free software (GNU), including - free ERP. However it is not necessary to forget, that introduction and support of free systems requires financial expenditures sometimes big than the paid software. The reason simple - at the free software much less branch experience of use. Myths was 5: ERP system is very expensive decision, ERP the system takes root long term, ERP system this very difficult decision, ERP the system is very expensive in operation, any partner of the company of manufacturer ERP will program any branch decision. Let's look at the results which have turned out at me. 1st myth: ERP systems is very expensive decision. Pages: 1 2 3 | |||||||
| System | General provisions | Applied aspects | System analysis | Digital fields | Rarefied sets | Management | Basic concepts | Mathematics in management | Management problems | Society | National idea | Information technology | Automation of business processes | Projects | Internet technology | Services | ||||||||
