Home > Enterprise >  Talk about experience WMS, MES and ERP integration path (first:)
Talk about experience WMS, MES and ERP integration path (first:)

Time:10-12

In the early 2016 group information, leadership, policy makers and cognition to the attention of the enterprise informatization, as practitioners feel more pressure, large areas of peripheral system migration and infrastructure as busy as a bee, but when hope for perfect encounter with reality, but fortunately, can go into practice, step by step to complete the vision and planning, have to think how small at the same time, decision at the moment, how multi-pronged, methodical work, this year, under the leadership to lead the team to complete the process system support, orders the development of the front-end system, decision-making data collection, display to provide data support, data and business double drive,
Policy makers in 2017 following test, fast, in principle from a group enterprise in optimizing the pilot projects, aims to establish a WMS, MES factory wisdom,
Selection stage, many still, the demand of business sink into noodles, multidimensional, evaluate and develop business requirements; The IT team more consideration from the aspects of hardware and software support and improve the degree of the expansion of the function of secondary development ability; The supplier from the professional point of view, the answer early blueprint,
As demand clear, hardware and software evaluation, and finally confirmed by the supplier, from policy makers we put this project on the targets of the key controls as:
? The interaction between system and intelligent response; ? Systematic management plan, establishing (quantitative, procedural, standardized);
? Software business layer implementation and control, it is easy to understand, software layer would be worked out by both inside and outside and the ground, it is also the basic delivery capability of the supplier; At the same time the two sides should jointly establish a management plan, business and management can quantify the quantitative, to quantify the routing, can not flow to control the standardization of business flow, process constraints, to achieve simple operation, high efficient robust operation efficiency, however, multiple communication back we first listed in the supplier can identify risks of important points to: interface interaction how to implement,
When consciousness is the first problem, internal team with WMS, MES manufacturers conducted in-depth communication face to face for the first time, of course, as a small white, we are waiting for feed position to accept baptism for the first time:
1. Open ERP query and write back interface to query to the other party or scheduling;
2. The trigger to the WMS, ERP end MES manufacturers in the middle of the library, in order to offer each other time load, while time grasping WMS, MES vendor data back to the writing of ERP;
3. Manual processing,

In the face of confusion, already no longer is much ado about nothing, but it is difficult to support decision making, from the point of reality, then no interface of ERP in service, unable to mount the trigger (and certainly not respected, later have Syria), confusion of the software; Group the enterprise belongs to small batch more varieties, production change is a murky business documents, its business demand obviously cannot accept artificial intervention in great quantities, the IT team facing technology and personnel equipped with confusion,

It is true that many participants, each bosom to his own opinion and then team brainstorm moment, at this moment you heart? Opinions and various solutions in our set thinking, after think that whether we, or WMS, MES supplier, even tried to communicate to a third party is an insurmountable divide, presumably IT team on this, the in the mind have a steelyard to measure IT: the ideal interface interaction should be integrators followed the seamless integration of the software, real-time interaction, handshake authentication and so on, because the concept aims to reduce operating costs, reduce maintenance costs and shortening the time of communication, improve the efficiency of service, to provide historical records,
? So the question comes, how can I achieve it?
? Who to implement, is the supplier, a third party, or as a "fireman" we?
? Eight, think twice before everything known check and win a few, how to build the platform from the dimension of management?
With no pity is not cutting, sensitive and studious attitude of it is not difficult to find that we have a lot of concepts have been put forward:
? EAI (Enterprise Application Integration, Enterprise Application Integration) : interface Integration, business process Integration, Application Integration, data Integration, platform Integration of five major types,
? The ESB (Enterprise Service Bus), Enterprise Service Bus (ESB), a service-oriented architecture (SOA) has gradually become the mainstream of IT integration technology, service-oriented architecture (SOA), Service - oriented architecture, SOA) is a software system design method, through published and discoverable interfaces for end-user applications or other services to provide services,
Just like the lyrics written: I stumbled toward you, you also can't a person to leave, we said together, no matter how experienced wind and rain together, high-energy has direction ahead, I will certainly will follow, of course, this type of worship to follow, passion and thoughts are like behind the lyrics: plain and quiet die,
When we are in the system after further study concluded its major functions: transformation and integration, conversion refers to the protocol and message format, integration refers to the atomic concatenated on a regular basis in accordance with the requirements, a professional manufacturer of the above integration, finally came to the conclusion:? System is too expensive, free, open source Mule ESB is secondary development, application, the pit is too much, running is not stable, or identified as technical requirement is too high, not ordinary people chosen,)? Also need a lot of tedious work with it to help them achieve connectivity, and require high? Too old, has been difficult to adapt to the lightweight, fast response, the development difficulty is high, the redundant configuration function become very inflexible,
Though as IT decision makers would you consider the previous pass on the risk, but underestimate even ignoring the subsequent operations and management? Whether or not you have the drive under heavily, YongFu?
  • Related