Home > Enterprise >  Talk about experience WMS, MES and ERP integration road (at the beginning of the first paper: taste)
Talk about experience WMS, MES and ERP integration road (at the beginning of the first paper: taste)

Time:10-12

Last confusion whenever recall still cold, although the road ahead is unknown, also must way, who let you bear this modern builders, who let you to perform the duties as "fireman"

Naturally, we abandoned the plan provided by the supplier (3) artificial processing way, the reason is also fully: amount of data, large amount of documents, finish operation a system should be equipped with a certain quality of people continue to another operating system, low efficiency, error rate is the highest, and is not a wish, although mass can play such a big business, even if you had a good time, there is no lack of manpower, but not low? Is very low, no problem, and later when can realize automation described o? Short step, without even thousands of miles. No product small flow, beyond into jianghai,

Plan 1, we will put the realization of the demand on to ERP or WMS, MES manufacturer or a third party, to evaluate the following aspects:
1> Needs to develop, development, testing cycle;
2> Without the ERP development pattern determines the difficulty of the interface, such as the quantity of documents plug-in development model to consider documents (thoughtless function will result in a cycle and budget well beyond), and such as the development model of button events needs assessment and establish standard operating functions (many living ERP are facing documents have button operation, list operation, other documents can also be the back-end operations, etc.);
3> Secondary development of upgrades, migration defects (if development after the update or upgrade package execution have serious impact on two open failure please careful and cautious, "fireman" better to die but could not bear the torture of soul,),
4> , of course, is to consider the cost and maintenance, first time budget down would be paid at least hundreds of thousands of, although the risk is passed on, but the maintenance, optimization of others, and reuse the basic is zero, not to mention management, IT decision makers, please think how to effective management and operations, IT is far from the get pay,

Scheme 2, on this basis, we finally helpless chose it for the first time, really helpless, please pardon me incompetent, the integration of all parts by internal team for ERP data table and associative table attached write timing scheduling query function, to the timestamp records for screening, the mighty data transfer to the middle table, write back part combed the business relevance, from a small amount of data back to the premise, to grab the relational data of upstream and downstream, to write the ERP business data table, it is too in January, trembling,

Here to talk about why recommend careful trigger: the main reason is the reasonable trigger a high requirement on the designers and writers to write, must be comprehensive analysis of the related business, to fully understand the working principle of the trigger at the same time, that is to say, write a trigger that consider comprehensively in our business, do the best in technology, can not affect business and performance, the trigger is not easy to be noticed, brings to the later period maintenance difficulties, at the same time the business often need to consider the mount of the trigger, such as documents are child table, table when sun need to verify whether the business system and the mechanism of transaction processing in the transaction, otherwise the data is incomplete, incomplete logic will bring serious consequences, at the same time, the performance and cost would have to consider, in view of the trigger more system manufacturers cause confusion will tell out of place in the maintenance of data,

When later we still immersed in the joy of the completion, consciously to fix bugs will continue to perfect this plan, to meet accept reality hit:
1> Business from the start 1 hour time scheduling discontent gradually into 30 minutes time, five minutes time, 1 minute time even more so, because really good reasons, production waiting for data to operate, at that moment, found that the more and more data is disorder, natural sequence has appeared various problems, is constantly repair, but we have pain, bury in the affairs of modifying data, daily business of its step to;
2> Data while in transit, but never restrict each other between business, for example, ERP after purchase order issued by A material purchase quantity is 100 PCS, WMS vendors have released barcode, packing, delivery, even ERP due to special reasons to change the purchase quantity is 80 PCS, the WMS is innocent, you call I modified, well, then the modified extra 20 PCS will be how to treat the problem of follow-up, the WMS remedial voice again, I add A check back to the middle table cannot be modified, ERP and timing to grab ban on ERP, in the long run, the data with interaction is like A spider web, IT daily with dizziness, who's reality to pay for this? Is management standards used to bound? Or modification work of staff is constantly check error correction in the hard work? Answers are so often hard convincing enough, limiting function usually leads to more complex operations to undo and make up, a lot of maintenance will be not worth, inefficient,
Is in the heart of this more than a year, a trip, but not read to think, how helpless, IT out capital with a computer company, have IT silently in with production line to work overtime, if lucky you in a few shifts of the enterprise, is decided to do your man don't sleep for 24 hours on standby or flip bar thy wife, and of course there are fun guy, think maybe there are some other benefits, or consciously,
Like clip in hetian seed makings stone, water is as smooth and bright appearance, but it is not from kunlun through mountain flowing water in ten million years of precipitation, the result is,
  • Related