Transcript of MES to ERP Communications Explained!

then we're using a connector to Erp and we're converting topical namespaces in Erp to a namespace here [Music] all right Discord question number one yes related to this is related to the mesy board video yeah so akkos I'm assuming that's his name on Discord asked um mes2 Erp Communications how is how do they differ between industry 3.0 and Industry 4.0 and are there are there open source solutions to mes or Erp to mes got it okay all right so I'm going to start with the question is mes to Erp communication how do they different in different industry 3.0 and Industry 4.0 all right so I'm gonna start there all right so in the in the uh industry 3.0 world the the former way of doing um or the the typical linear way of integrating Erp to mes look something like this so at the Erp layer what we have is our Master data model so that's the um it's the structure of the business it it's uh it's how we organize the business the Enterprise the the business units locations inventory locations all that kind of stuff so it's the master data model it is uh and then it's definitions so it'll be things like um our products it'll be our product codes it'll be our bill of materials it'll be our manufacturing steps it's going to be all the things that define our business that's what's in the Erp system and as a manufacturing execution system there are things from the Erp that I'm going to want so if I've got my Erp layer here my mes layer here some of the things that I'm going to want is I'm going to want um our product codes so I'm going to want to and Manufacturing execution systems in order to be able to let's say I wanted to do I want to calculate oee by product code well I either have to Define all my product codes in my mes system or I have to go get them where they're already defined so one of the things that I want is I want to list all my product codes I want my work orders and I want my my schedule if my schedule lives in the Erp let's pick those three there are many others that we might want okay but in this case let's say I just want those three the old way of integrating with the Erp system was that I would either hit an API so let's say I have a rest API here um that is not going to be read let's say if it's a rest API let's say it is uh we'll we'll make that one uh green okay because rest is rest is rest I have to learn the API I got to read the rest API documentation so I know which calls to make from the mes system so that I can call for product codes work orders and schedules but the the this is all going to be trigger driven so the mes is going to have to ask the question and the Erp is going to have to give the answer through that rest interface that's number one okay number two is I may connect directly through a SQL database so same thing I I'm going to use a SQL connector so odbc jdbc whatever it is and I'm going to request from the mes system from the Erp system over SQL but I also have to under I'll have to know how the tables are structured I I literally have to know what I'm looking for I have to know what I'm looking for and where it's located okay all right and then the last way is a custom connector so let's say I'm using a I'm using a a wonderwear mes or I'm using Factory talk mes and I'm and I'm talking to sap then I'm going to have a a connector that is an extension of my manufacturing execution system and it's going to do the same thing it's going to request the the things it wants and the Erp system is going to reply through their connector all right here's the problem with doing it this way okay the problem with doing this way is that if I make a change here based on some piece of information I add something else I want to use here let's say what I want to add is uh um let's do Bill materials for a product code and now I want the bill of materials I have to and I want to and I want to include that in my manufacturing execution system I have to make a change here I got to make a change here in my call and I got to make a change here I got to make I have to I have to I may have to add support for Bill materials at all three points that's the industry 3.0 way of doing it the industry 4.0a of doing it is and it's really in two steps so I'm going to do the Legacy example so what I've got is Erp that's got the thing I care about I've got mes that's going to run our mes function and then I have a unified namespace and in this case we'll do line and then underline what I'm going to have is an mes function and then I'm going to have Erp function we would never we won't call them mes and Erp but for illustrative purposes that's what we're going to call them all right everything that is here is published from the manufacturing execution system and everything that's here is published from the Erp system and the way that we normally integrate is we will put together we'll put a platform alongside the two of these this is the way we initially integrate ideally what you want is a manufacturing execution system that supports in this case we're using mqtt we want to support mqtt out of the box so we want to be able to say we want we want to configure on the manufacturing execution side hey we want you to send mes information for line one to this location in the line namespace and we want you and we want to be able to configure on the Erp side we want you to send the Erp information so that would be the product code the list of product codes or the or it could be if if the mes has selected this work order then put this value from the Erp for the product code in this location in the Erp namespace right we're going to use an iot platform here that uses a connector to the Erp and a connector to the mes or we're going to build the Mes in the iot platform natively which is generally what we do then we're using a connector to Erp and we're converting topical namespaces in Erp to a namespace here here's the the big event the big difference on that when we make this connection here so whether I'm doing this over rest SQL or some custom connector from our iot platform what we're doing is we're setting this up in a way where as the the underlying data model in the Erp extends our connection is automatically retrieving data processing it and putting it in the appropriate location in the namespace so now the manufacturing execution system can just monitor the ER Erp namespace for changes and it'll be reported so they I can set up a connection so I can set up a subscription to Erp within this line in my mes system and if my Erp adds something like bill of materials as a new function in the Erp bomb is going to show up here and this subscriber will be notified that that bomb now exists and then the only place we have to make a change is here we don't have to change and we don't have to we don't have to make a change in our connector we don't have to make a change in our subscription as long as I'm subscribing to Erp wildcard I'm going to get anything that's put into Erp okay so the only place I'm making a change is on the consumption side all right so that in a nutshell that's the way um that's the difference between how we're integrating Erp and mes industry 3.0 and how we're integrating Erp mes industry 4.0 obviously the advantage here is that both the Erp and the mes get full context they're not limited to just what we're uh the manual connection we're making between one layer and another the Erp system has access to everything in our unified namespace just like the mes does and the only thing that we have to change is the subscription upon which uh the the things that we're subscribing for