Conditional eSigning Routing Made Easy

Conditional esigning routing

good morning and welcome to webinar 11 in the capoeira 2020 webinar series from max solutions this is Dave Hammond product manager for the capresso fir in the UK today's webinar is on the subject of OPC and how OPC can interact with databases mes ERP SAP and other high-level business systems the agenda for today is going to be as follows first of all we'll look at ODBC databases on the shop floor and then we'll look at a few scenarios starting from simple database connectivity scenarios through to some more complex data connectivity sark scenarios involving other systems rather than just databases will then look at an example of a typical complex data connectivity situation and then go on to look at the different softwares that you can use to solve these problems so who is this webinar aimed at if you're an automation engineer who is designing or maintaining shop law systems which involve interactions with databases or external systems this is for you if you are a data engineer perhaps an IT data engineer who's investigating ways in which your high-level systems can communicate to the lower level shop floor systems again this should hit the spot for you and anyone obviously who is looking to integrate such projects in the future wants to get an idea of the way these things have done so let's have a look at databases first of all and theta based on the shop floor and why why they're used so nowadays ODBC data databases are seen as the de facto standard for storage locally on the shop floor for several reasons the first one is that the data is in the neutral format it used to be the time when historians were were used a lot on the shop floor because storage of data was expensive and one of the advantages of historians is they scrunch the data down to a small package size but nowadays storage is cheap and so storing large database is not as not as costly as it would have been so storing databases which might be seen by some people as bloated on the shop floor it's this seen as a good thing these days and the data is this not transformed into a bespoke format like some historians do but it's then retrievable by many tools it's also low-cost to deploy and integrate the database many of the tools of three and two vendor-neutral so it's not owned by anyone OD BC as a standard across multiple different suppliers and because of that there's a very wide skills base and it's very widely understood in in various spheres they're well supported because it's supported in Windows but then there's many many database integration tools reporting tools and other applications which you can use on top of a database to turn the data into information and knowledge and finally it's very easy to exchange data between databases and other platforms so pretty much any other any other platform you'd come across on an IOT platform of scarlet platform of historian platform a reporting platform they'll be able to ingest data from a database without any issues so it's a very good way of taking the data on the shop floor and archiving it away locally to make sure that you've got the data straight from the horse's mouth without it being modified and transformed in any way so let's look at some scenarios about database connectivity starting the simple ones so here we have a database on the right hand side we have Kip server communicated to a PLC on the left hand side in this case the data is coming from the database - Kip server and Kim server that is then sending it down to the PLC so that's a very simple unidirectional data fetch from the database down to the PLC and typically these this is used for downloading recipes or part build instructions or settings for the devices or settings for the machine so that's scenario one we then have scenario two which is the opposite which is data logging from the Kip server data coming up from the PLC and then being sent to the database for archiving and storage within that database and again this is very very common on the shop floor that database will then have the they will have the data strengthen the machine without any omissions or any filtering straight from the machine this is this data logging is typically based upon a couple of conditions so it could be a condition trigger like the the end of a machine cycle or a part being made or it could be based upon some time if it's based upon time then often this type of solution would be used for recording energy readings or power usage and that sort of thing if it's based upon fear occurs it can be the end of batch end of sequence or some sort of data being archived away for compliance or part traceability so those are two simple connectivity scenarios less Lucas and more complex ones here we have the database on the right hand side we have capes over on the left in this case we need the data bank going in both directions so states are going to be coming from the database to the PLC biochip server and vice versa so on top are kept server in this scenario we need some application which I'm returning a data handling application and the data handling application will be taking care of both directions so that we're taking data from the database and then also to the database so it's actually handling in in writing the day to a database but also reading it back so if you're writing to the database you then might also want the ability to have a confirmation before the machine moves on to the next stage of its production so here we have a more complex sequence to interactions on the left-hand side you have kept server talking to a PLC one on the right-hand side you can see there's different environments you have an NES you can SAP you've got databases and in the middle you'll need some sort of application which is able to handle the different systems on the right hand side and also interactive kept server on the left so on the Left we have the kept server doing the data calms and then passing the data using a PC to the state of routing application one on the right hand side will have the different systems and the data routing application is able to connect to all of those and communicate to those different systems using the bespoke comms at those different systems would require there's also a lot more going on in this scenario than then improve in the previous scenarios because these installations are from much more involved because they're dealing with sequencing on the right-hand side between the different platforms there's data transformation and translation between the different platforms because each of them will present the data to this data routing application with a different format and often the data is being amalgamated from the different disparate sources before it is actually then moved on and perhaps archived to the database so you can see this is a far more complex scenario than the previous one so let's look at a real world data connectivity example so here we have and now below caps over and you've got systems sitting at the business level and at the IOT level and the data routing application and kept Saylor so a scenario for a complex assembly might be as follows you've got a barcode reader that's reading the the park when it comes in build instructions would then be needed to be pulled down from the SAP system down to the PLC for the PLC to build the the mission depart the completed signal will then be need to be passed back to the SAP system if they then perhaps a label needs to be printed in a catch to the part that's been made that would then need to be logged away into a database so the database will then have a record of revenues being made and perhaps the data is then being sent to the iot-cloud for analysis later so you can see there's a lot of going lot going on in that sequence and each of these systems is different from each other the iot-cloud is put in from a different supplier from the SAP system different supplier from the database discard er and and the data routing so there's lots of lots of things lots of strands to pull together there so how do you solve these particular problems how do you what tools do you use to for these person areas so let's look at the first one the U Direction directional data fetching this is simply the ODBC driver since I kept soweth from the ODBC driver inside kept server is used for reading data from an OD you see deep ODBC database so that's a one-way drive up from the database down to the PLC the second one is the data logging where you have time triggers or conditional triggers and that's data being sent from the plc to a database that's achieved using the plug-in from kept server called the data logger and actually the the data logger plug-in is the most common plug-in that we provide to keep server users for the third scenario which is a bi-directional communications and this is ideal for two-way connectivity with databases the decoding software has a very powerful scripting engine as well so if you need to do customization of the data or if you need additional flexibility on top of just sending and receiving data to a flat database you can do that you can use background calculations and all sorts of very useful things it also interfaces between lots of other environments as you can see in the in the diagram there for the very complex sequence scenario we looked at earlier then this is a product from a German company called in grey and it's called OPC Reuter this is a very powerful software utility which combines multiple types of connectivity with a very clever and powerful graphical sequencing and logic engine so within the OPC Reuter software you can create flowcharts of data you can create rules based interactions with the internet with the external systems you can put logic in there and it also has a scripting and customization aspect as I said the configuration is graphical so it's very easy to to understand what's going on when you're configuring it and when the software is actually in its runtime the graphical flow of data is actually overlaid on top of the flowchart diagrams so you can see of the real-time data flowing between different systems on top of the flowchart diagram so that's very very good software and it's ideal for complex situations where you otherwise normally have to write your some sort of bespoke package to do these interactions again this communicator clip server using OPC UA to recap the agenda where you first of all looked at early BC databases on the shop floor then we looked at some simple connectivity scenarios for databases and then some more complex scenarios a real-world example of a complex situation and then we looked at some of the software types that can be used so thank you very much for attending today's webinar my name is Dave Hammond from Mac solutions the product manager for the Kipp where software in the UK we've been the kept where software people in the UK since 2001 and as we've covered today we also sell the the cogent software from a Canadian company cogent and also the PC Rooter software from the German company in wreck so feel free to contact us if you have any applications which are relevant to today's subject and we hope that you all stay safe and well so thank you very much