Moin Moin, Bonjour, Hello, Buenos Dias and Ni Hao! Welcome to the "Mechanical Engineering and Digital Plant" session from WAGO at the Hannover Messe Digital Edition. My name is Norman Südekum. I warmly welcome you. I will be here today to guide you through the session. When I'm not doing that, I'm responsible for mechanical engineering worldwide at WAGO. When we talk about mechanical engineering and digital plants, we have to go on a journey together and we have to circumnavigate some things there. And what we circumnavigate, these areas of tension, these fields of action, I would like to illuminate with you today on this journey. First of all, let's take a look at the topic of productivity: a topic we've all been familiar with since Henry Ford's production lines. The next aspect, perhaps a little more recent, is flexibility, responding to the individual requirements of our customers. And the third aspect is the topic of efficiency, particularly energy efficiency, where we try to treat the world, that was only given to us once, in the most resource-saving way possible and, of course, to act in compliance with the law. And we have to illuminate these three fields of action. I would like to do this with you in such a way that we look through the eyes of the machine builder, what moves him in this field and how WAGO can support him. And on the second side, we want to look through the eyes of the system operator to see what moves him in this subject area. For the first topic, I will accompany you on the journey together with my colleague Franco Polo from Sales Germany, who is responsible for Business Development Industry. And we will take a look at the plant structure, how you can make it modular, how automation can accompany you, how WAGO can support you, and what aspects this may have for the software. So, clear the stage for you, Franco. Welcome to "Machinery and Plant Engineering: Fast and Efficient". Today I'd like to take a look with Franco Polo at how you can achieve, both mechanically and in the software, an efficient setup of machines and plants. Therefore my first question to you, dear Franco: How was that over time? What can you tell us about topologies? How did that develop? For that, let´s look at the following graphic. Here we can simply see how wiring has developed over time in mechanical and plant engineering. On the far left, the classic parallel wiring: all sensors and actuators are wired in the control cabinet, usually to a sub-distribution. From there, the wiring continues to the control line or trunk line in the main control cabinet and then to the actual control system. This is very complex and costs a lot of time. The core cables must be processed, i.e. stripped and connected. There are many clamping points, and so errors also occur. That's why IP67-modules were introduced into the field several years ago. In the past much with Profibus, nowadays of course more ETHERNET-based, PROFINET, EtherCAT® or EtherNet/IP. There you can capture the sensors and actuators directly in the field. A big advantage is that the IP67-modules can be distributed across the plant, making optimum use of the space in the plant. And I have very short cable routes. In addition, the cables are usually used pre-assembled, so that wiring errors are almost impossible and even less trained staff can set up the plant. In 2006 IO-Link was added to the system. IO-Link is a point-to-point connection that is communicating below the actual fieldbus protocol. This means that you continue to use the fieldbus protocol as usual to communicate with the controller and below the network module you can then communicate with IO-Link. IO-Link was invented for making the last meter in the automation pyramid intelligent. This means that there are IO-Link sensors and actuators that provide a lot of diagnostic data in addition to the actual switching signal. In addition, there are so-called IO-Link sensor hubs, where you can collect binary signals again. And that has the huge advantage that you can reduce the wiring costs by about 30 to 40 percent. This is mainly because of the wiring. We only need M12 pre-assembled lines, which are unshielded. On the far right of the picture, we see another topology that is becoming more relevant. Which means, datas are collected parallel to the controller from e.g. from cloud- or engineering tools or from an Edge-Device, which processes the data and then forwards it to the cloud. Therefore our modules speak OPC UA and MQTT. Wow, that was a trip back in time, but also a little glimpse into the future. Now I would like to know, how do I actually transfer that to my mechanical plant engineering? And where are the advantages? Let's take a look at the following production line. It always consists of many, many stations, e.g. in the first station the raw material arrives, is unpacked, inspected and then forwarded. In the second station the packaging is cleaned, for example, and in the third station it is filled. In the further process it is then packaged again. If we now take a closer look at these individual stations, the first station in our example consists of sub-assemblies. This could be, for example, an inspection unit, where the new goods are transported into the plant and a conveyor belt where bad parts are sorted out. Here I can build the whole thing modularly. This means that I have a fieldbus station and can then work in the individual station and the sub-assemblies with IO-Link Devices, for example. The big advantage here is that each IO-Link Device is 100% identifiable and is connected via standard pre-assembled cables. This means that I can pre-produce a module, bring it to the station at the construction site and connect it to the rest of the station via one or maximum two lines. This means I'm very fast and efficient when setting up the plant. Now you've given us a good insight into how that can be optimized in the mechanical setup. Where are the actual advantages in the software? Well, we'll have another look at that and talk about it. The bottom line is that, when we work with IO-Link Devices in the sub-assemblies, the huge advantage is that each IO-Link Device can be clearly identified via the manufacturer ID and the device ID. And I also have the option of assigning a so-called application-specific tag. This can have a maximum size of 32 byte and the user can assign it himself, so to speak. The advantage is that when I now bring the system together, i.e. the sub-assemblies that are pre-wired and pre-produced, to form a station, the PLC can automatically read out the configuration and then set the process and the parameters so that it fits. This is also a huge advantage when changing products: if I need a different inspection unit and put it on, the system automatically reads out, which inspection unit it is and adjusts the program. Here I can really reduce machine downtimes and commissioning times massively. It sounds like I have advantages in commissioning as well as in operation. That must be a winning argument. Maybe a summary conclusion from you: what else can you take away from this? In conclusion, you can mechanically save a lot of time and also costs when setting up the system, but also afterwards on the construction site, when commissioning the system. And on the other hand, if you set up the software accordingly modular, you can also save a lot of time there, again in the commissioning, but also throughout the administration of IP addresses can be significantly reduced. Great thing! I think WAGO has a lot to offer in the area of I/O System Field - our IP67 system. Also for the future in connection with IoT. I think we are both ready to go the distance with the customers. Gladly! On the next journey section we would like to look with you through the eyes of the operator. Namely, we would like to look at how digital business models can increase productivity. I would like to welcome Jürgen Pfeifer from Sales Germany, also Business Development, IoT and Cloud Partner Management. And Jürgen has brought an interesting guest with him - our customer Oliver Slaby from Linde. Clear the stage for you two! Ladies and gentlemen, dear audience, welcome to the session "Enabler for Digital Business Models". My name is Jürgen Pfeifer. I work in the Business Development at WAGO and today I'm being supported by Oliver Slaby from Linde, who we'll get to know better later. There are many motivators and motivations for digital business models. You know many of them. Here are just a few listed. It is certainly the point that you want to be closer to the customer, i. e., you want to have a permanent customer connection and don't want to lose contact with the customer after the sale of a machine or equipment. On the other hand, one aspiration and motivation of digital business models is to lower the entry hurdle for the customer. This means, for example, not selling a machine once for several million euros, but making this machine available to the customer, e.g. via pay-per-use or as a leasing or rental model. And of course the initial investment is much lower than a large, high, multi-million investment sum. And exactly this effort, ladies and gentlemen, has always existed. But ultimately the risk was much greater in the past to offer such models, because these machines were ultimately also operated blind. In other words, although the leasing model was successful and the entry hurdle was lower, but a high risk was taken, because you didn't know how the machine is doing, how the machine's health is, whether unscheduled maintenance or similar is required. And so this kind of business model was only feasible for those who a) wanted to take on this high risk capital and b) of course also wanted to take this risk. Nowadays, with the topic of IoT and digitalization, it is possible to reduce this risk, because digitalization creates transparency. We can permanently see how the machine is doing and have a wide range of options for feeding the data to analytics and business processes via an IoT gateway. And this ultimately makes the topic of new business models attractive for you and for all companies, because the risk accordingly falls. And also the entry hurdle for you is much lower, by adding a WAGO IoT gateway to your machines or plant and it is much more transparent than in the past. If we now look at an example, I would like to mention our WAGO IoT partner GLI Business Solution, which offers a maintenance management in this way. This means that if information from the machine comes to the maintenance management tool, then targeted maintenance work can be implemented, and thus the machine can be operated more permanently without coming to a standstill. So much for the theory, ladies and gentlemen. Now I would like to introduce Mr Oliver Slaby from Linde. Oliver Slaby is Head of IT for Digital Plant Operations. Welcome Oliver. Hello Jürgen. Oliver, what is important to you when it comes to digitalization? Here at Linde, digital services are increasingly being developed, where we can use measurement data to support and improve plant operations. The classic examples here are improvement of performance, such as reducing energy consumption, but also increasing the availability of a plant or a plant component. There it is availability and many other things more. What does the heading "Digital Business Models" mean to you? For us, the services mentioned represent both an extension of the classic plant engineering. This means these services are received together with a plant or a plant component. But also as a complete new business segment of Linde, in order to improve the plant operation through the Linde know-how in after-sale. Please tell us now a very interesting answer to the following question: What role does WAGO play in this? So that we can offer these digital services, it is fundamentally important for us that the measurements are reliably measured under the conditions of the processes industry and then transmitted to Linde. Here, an ATEX certification and security requirements are absolutely fundamental. Here we use WAGO controllers and I/O modules to achieve that. One example we have done is monitoring plate heat exchangers, where we have installed additional sensors for diagnostics and their data is now collected and transmitted by WAGO controllers together with the I/O modules. Oliver, thank you so much for these insights into your work in digital business models. Yes, and ultimately in the solution that you have outlined for us. Dear viewers, I brought you a slide about the WAGO products that are used here from the IoT gateway up to the edge computer. There, of course, you are welcome to join us to talk about your digital business models. Also especially in combination with our WAGO IoT Box as ready-to-use solution. Ready-to-use solution, because it is completely electrically designed and can also be used immediately, in terms of software, purely via parameterization. And of course, we would be happy to design such an IoT box for you individually for your project, for example, even if you have environmental conditions that require the whole thing to be used in stainless steel. Yes, and in this sense, ladies and gentlemen, I invite you: Get in touch with us! Get in touch with us to also talk about your digital business models, to enable you, to get to the data and to realize together with our IoT partners exactly the solution for you, which is the first step into digitalization and also into new business models. So I was pleased that so many of you were here today at this session "Digital Business Models". I say goodbye to you and wish you good health. Stay healthy! We are on our journey and by now we have arrived at the next area of tension: flexibility. What does that mean? In a nutshell: shorter product life cycles, faster time to market, and faster changing requirements of our customers. And in order to fulfill these, you certainly have to gear your machines to it. And what could be more appropriate than designing software and automation in a modular way? I would like to welcome my colleague Lukas Dökel, who is responsible for the topic of the "Digital Plant" worldwide in our Industrial Sales Department. He will introduce us to the topic and will be actively supported by Poljana da Silva Santos from the company Evonik. Welcome, you two! Welcome to the session "Flexible plants through modular automation". Flexibility is the next step in production as well as in automation. Due to constantly changing markets and individualized products, modularity is the next step to meet these requirements. Here we have a process module, a pump, which shows exactly the actual situation. Many physical modules are already designed modularly, but not in automation. To close exactly this gap, there is the MTP concept of NAMUR and ZVEI and it has been standardized in the NAMUR recommendation 148. What exactly the MTP actually contains and how it can provide you with added value, that's exactly what we want to show you in a short video. Rapid adaptation of existing modular plants with WAGO. Vaccine is produced in this factory of a pharmaceutical company. The ingredients are mixed together. The finished vaccine is filled into ampoules and finally screwed with a lid and delivered to hospitals. But every now and then the delivery capacity has to be increased, for example in times of a pandemic. Fortunately, the plant was planned on a modular basis. However, this does not apply to the automation. Data points of the new modules with all variables of the process management level have to be created manually as well as a digital twin of the new adapted plant in the leading control system. On top of that, each new module also speaks a different language. This is because every manufacturer implements an individual control system in a machine. This is where WAGO comes in. Together with NAMUR and the ZVEI, they have paved the way for MTP. MTP can best be compared to a printer driver. It contains the necessary detailed knowledge about the printer and can thus integrate it into any PC. Transferred to a production environment, the module corresponds to the printer, the MTP to the printer driver and the PC to the process control system. Thanks to an MTP library on the part of the module manufacturer, the system integrator of the pharmaceutical company can import the module description quickly and easily into the plant engineering tool. In this way, processes, sequences and production quantities can be easily adapted by simply adding and removing modules without interfering with the modules themselves. First up here on our MTP pie, we have the topic of know how protection. Where in the past you had to expose source code and describe functionalities, today you can map them into services and in handover and engineering you have to describe and use those services. Functionalities encapsulated in services is one of the most important points of the MTP the possibility of offering functionalities of process modules such as pumping as a service is new and makes it possible to release these via different license models, for example. This means that you may only need one program for different plants and you would activate these services for the customer via different licenses. Clear software structures - one of the time-consuming points is the coordination of data exchange and variables with the POL, with the process orchestration layer or control system. This becomes no longer necessary, because the MTP standardizes exactly these in OPC UA. As a basis of the CE marking we must know the dimensions of the module and its interfaces, which is exactly what we can now do with MTP and thus also facilitate CE marking. Standardized interfaces: also before the commissioning or operation of the plant. You as a module builder can of course also use this standardized interfaces to pick up all your information and data from the plant in advance for development and commissioning. And one of the crucial points or most exciting points is the enabling of "as-a-service". In the future, you can use functionalities similar to those in the cloud, where we have been familiar with the topic of "as-a-service" for some time now. We buy them for IT infrastructure or IT resources. In the future we can also buy them for processes functionalities. So the pumping service or the stirring service - all these are advantages for the model builder, which he can use in the future with MTP and modularization. How modularization is applied in practice and what other aspects there are, I would like to involve our customer Evonik and ask Ms. Polyana da Silva Santos. Polyana, how has the MTP supported and helped you in modularization? Evonik is one of the pioneer users of MTP. We have already shown several times that both the engineering of modules and the integration of modules to a process orchestration layer or even a classic DCS is faster and flexible using MTP. We have over 50 modules in use at Evonik especially in the laboratory and pilot plant, where flexibility plays an essential role in the product innovation cycle. Many of these modules are from WAGO. It has proven so successful that MTP will become an integral part of our plant specifications with our module manufacturer. Of course, we have also seen that further efforts are needed in the standardization work. Therefore, cooperation and interoperability are keys to success. And we are very happy that WAGO is one of our cooperation partners. Yes, thank you very much Polyana for the insight. If you are now also thinking about how you can modularize your plants or use the MTP concept, please feel free to contact us. We look forward to hearing from you. We are at the fourth stop of our journey and there I welcome again my colleague Jürgen Peifer, who has brought along reinforcements from WAGO. With him is Dr. Jan Jenke from the business unit Automation, there responsible for the topic analytics, and our colleague Sebastian Pscheidt from our production in Minden, who is responsible for process development. The three of them would like to show us how the mechanisms and applications from the IT world can be transferred to the OT world. And for this purpose they have packed a virtual toolbox. For me it was containerization, but the word sounded too bulky. That's why they called it the virtual toolbox, which they now want to open for you. Clear the stage for you three! Dear viewers, welcome to the WAGO session "The Virtual Toolbox". Using WAGO Analytics as an example, we would like to introduce Docker® technology to you. We, that is Jan Jenke from our innovation and technology department and Sebastian Pscheidt. He works for us as a Process Engineer in the area of production. My name is Jürgen Pfeifer from Business Development at WAGO. Docker® technology and Analytics are both IT technologies that are now increasingly being used on OT hardware, i. e. on control technology. If you would like to have a look at our Docker® Hub, you can see the link pasted here. You will find that there are now many and a growing number of third party applications that you can deploy on our WAGO Docker® Ready Devices, such as the PFCs and the Edge Devices. And the Analytics that is increasingly being implemented and realized with Docker® technology. Jan, why is it like that? Why is Docker® technology increasingly being used in Analytics? An Analytics solution is often integrated onto an existing control system. And this is where Docker® technology offers clear advantages. Using Docker® technology, we can simply bring applications to the devices dynamically and in a resource-saving way. These are then, for example, machine learning models, but also simple applications such as databases. Please explain this in more detail using this slide. So the big advantage of our devices is not only that they are perfect data sources, but they are also perfect for Analytics application because they are Docker® ready. And so we can bring application to these devices for different areas in Analytics. It starts with dynamic data handling. For example, we can have a MQTT broker, but also an application like Node-RED or IO Broker to the devices, send this data to the databases, visualize it using dashboards and visualization like Grafana, chronograf, but also plotly, and then develop machine learning models or data science models based on frameworks like scikit learn, TensorFlow or SciPy and deploy them to the devices. The advantage of such a modular solution is, that the individual containers, the components of the Analytics solution, can be dynamically removed and transferred to other devices respectively can be exchanged. Jan, thank you for this insight and now, dear viewers, let´s come to a concrete application scenario and therefore Sebastian, you bring along this slide for us. Right on this slide you can see the application that we have treated with the topic of Analytics. That is a vacuum conveying system. Here we have an actual data display of the relevant system parameters, from which we have learned, from which we have developed further, gained new insights and ultimately also mapped various models. In the next step, the task is to provide further microservices, such as the example shown here for filter cleaning, i. e. a state-based filter cleaning based on a pre-cast. And here, too, the universal toolbox Idea offers itself, which we can adapt again one-to-one to implement our application. That means adapting and adding of new microservices, i. e. new applications in the form of Docker®, is a very important point for you in order to expand this topic area of Analytics? Exactly, that is the point. We collect a lot of data in the field. We want to use this data profitably and make it available again via many small applications in order to generate added value. And the topic is ideally suited for this. Now, what Jan described to us earlier, but also what you outlined very briefly, seems complex at first. Conversely, I know from our conversations, Sebastian, that you have always repeatedly emphasized that technology or solutions should be as simple as possible to use, especially if you have a larger team. As easy as a screwdriver. How does that fit together? Exactly, we'll stick with the screwdriver example. Everybody's got screwdrivers, they look different. Everyone knows how to use it. We don't even think about it. That's exactly how it has to be with a service like this. The focus here is on the employee. That means we build a solution that is as simple to use as a screwdriver. In the specific case of filter cleaning, this means that we record a maintenance order, then implement and report back. We thereby generate a closed loop, have created added value, we have freed up resources, have taken availability to an even higher level, and have generated a tool that is as simple as a screwdriver. That is, the screwdriver is at least the SAP based maintenance system, about which the employee, the colleague gets informed. Thank you for these first glimpses of the project. Now if you see Docker® technology in total Sebastian: where do you still see potential or opportunities in the production environment? Yes, the opportunity that I personally see and to refer to Jan again is the simple extension of the theme. We can create new applications based on the same technology that we can easily scale and ultimately deploy. That means we can release the application as many times as we want, and of course that's a step into the future and standardize it at the same time. That's a huge added value for me. Sebsation, thanks for your user view and Jan, thanks for your technological insights. Now it's up to you, dear viewers. What are the next steps? Feel free to check out the relevant applications at our Docker® Hub Account. Explore what seminars we offer and feel free to contact us at iot@wago.com, if you want to know more about the topic of Docker® technology. Do you have an Analytics project or a task to analyze your data? Feel free to contact us, so that we can implement your Analytics project together. Thank you for your participation and we look forward to having conversations and implementing projects with you in the future on the topic of Docker® and Analytics. Thank you very much and goodbye. We are on the fifth stop of our journey and are moving into the third area of tension. The topic of efficiency, Energy efficiency. As I said, on the one hand it is a matter of fulfilling the legal requirements, on the other hand, it is also a responsibility to conserve resources and save energy. After all, it also makes good business sense. And with the background of energy data management, I would now like to welcome back my colleague Lukas Dökel. He has brought a customer with him, Mr. Jürgen Ströbel, from the company Endress Holzfeuerungsanlagen, which deals with process heat. It will be about answering the question of how a mechanical engineer can still contribute to increasing efficiency in a company even after commissioning. I am very excited about this and look forward to your presentation. Welcome to the session "Efficient plant operation even after delivery". In many cases, we always look at the operators when it comes to energy efficiency, but there are also many opportunities and new business models for model builders and machine builders in this context. Many requirements affect the machine builder on the one hand from the legislation, on the other hand from the customers. In the case of legislation, for example, technical standards are specified, efficiency standards are specified or also energy data acquisition is commissioned as report. With customer requirements, it's always about getting the most efficient plants possible with a way of low energy consumption, but also of course to maximize the production output. But if we look at the life cycle of such a plant, the energy consumption is actually distributed very unilaterally. In other words, where the machine builder is involved in the development of the plant construction and commissioning, we only have a very small share of the energy consumption. We have 90 percent of the consumption in operation. If we compare this with the specific plant knowledge, i. e. when does my plant run at the optimum point, we see that we have a gap of experience after commissioning, which only builds up over time and gives the operator the experience over time of when my plant runs as efficiently as possible. Therefore, the question to you: Who of you would say that he knows exactly whether his plant runs at the optimum point? And that's where we have to go, that we can say: We have to add up the specific plant knowledge. In other words, the experience of the module manufacturer or the machine builder together with the experience of operating the plant have to be brought together to create the highest possible level of knowledge. This is exactly how we can then increase efficiency and significantly reduce energy consumption. And it is exactly this barrier that we have to break through. And how do we do that? In three important ways. One thing is transparency - we need to have data available in the first place, historically available, in order to be able to evaluate it. The second is the issue of evaluation and monitoring. Only if I can really evaluate and monitor the data and make it available in a targeted manner to the people who can also evaluate it, only then I will be able to make a statement about efficiency. And finally, of course, I have to make recommendations for action that will hopefully at some point go from the model builder to the operator and then trigger maintenance intervals, for example. But also the maintenance of the system must be possible from both areas. And that is exactly where the topic of configuring plants is very important. For transparency, WAGO has created the topic of Energy Data Management, an easily configurable solution, which allows to record signals in the field, store them and transfer them to target systems. The theme of Energy Data Management Visualization, to give targeted information to the people who want to analyze and evaluate it. And the WAGO Cloud as a tooling to share recommended action and information and also to allow access to the plants globally or not. But what are the advantages for the machine builder, for the operator? The operator receives this information in the form of dashboards or visualization and can see at any time how his plant is running and, in the best case, he even receives alarms and messages when and how he has to adjust a plant or maintain it. This not only saves a lot of time and money in maintenance, but also offers a multitude of efficiencies that we can gain today with pure knowledge exchange. On the other hand, the machine builder gets exactly this experience from the operation, which he can use again and he has the opportunity to provide new service models such as the maintenance of energy management or even the statements and long-term maintenance of plants via remote access, for example. This not only brings him advantages in development through the increased knowledge and saves costs, but he can also expand his service portfolio beyond and after commissioning in the future. Yes, and now I am looking forward to involve the company Endress Holzfeuerungsanlagen, as a view into practice, and I look forward to Mr. Ströbel. Mr. Ströbel, how has the WAGO Energy Data Management helped you in your applications? Hello Mr. Dökel! We are manufacturer of wood combustion systems in the range of 100 to 1000 kW and customers of ours use energy data management as energy data collection in the area of process heat. Now you have provided different dashboards to your customers, including the topic of electrical energy. What do the customers use this for? We use the electric energy dashboard so that the customer can see what they are putting energy in and getting out later in terms of thermal energy. That would be exactly the next dashboard, so to speak. The heat energy, that is on the one hand the requirements that you have by law and also for the customer the information, of what he gets out of the back of the plant. Here the process heat is recorded and also if the customer wishes also other heat quantities, depending on what kind of plant he has, this is always customer-specific. And how do you use the WAGO Cloud in this case with remote access? We use the WAGO Cloud, when a customer expands his system, to then configure or parameterize it and we can then use this in a CO2-neutral manner. Very good. Thank you very much, Mr. Ströbel. If you would like to know how you can operate your plants as efficiently as possible, or if you would like to develop new business areas, then please do not hesitate to contact us. We are on the last stop of our journey. Glad you're still on board. The topic is energy efficiency, this time with a view from the operator's perspective. My colleague Lukas Dökel has invited Dr. Karsten Riest from the company Clariant and will discuss the following topic with him. When an energy data management system is installed across several plants worldwide, there are a lot of data acquisition devices that have to be maintained and parameterized from a distance. And how this can be done successfully without generating additional effort or keeping this effort low, that's what they're going to portray. That's why I'm looking forward to your presentation. Welcome to the session "Holistic energy management beyond the factory gate". In the next few minutes, we want to look at the topic of energy management for operators and see what requirements, challenges, but also opportunities and possibilities there are for running an energy management effectively. Let's first look at the requirements. They are very diverse and affect operators from different directions. On the one hand, we have the legislator, which now requires the introduction of an energy management system or an energy audit for medium-sized and large companies. CO2 savings are on everyone's lips, there are also strong requirements here, and a much-discussed topic is also the topic of third-party volume limitation. On the other hand we have the requirements of the market, the customers and the environment, who naturally want to have products that are as cost-efficient as possible, thus also cost-efficient production. More and more important is the image of the company, which should be as green as possible. And of course, we want to reduce the use of raw materials as much as possible. But one of the most important aspects is still the inner drive that the companies and the operators themselves have towards themselves and their production processes. Nowadays, when we come into companies, we often have the challenge that there are different plants, like here on the graphic, with the most diverse software solutions, ways in which we collect the data, sensors are not applicable, because maybe they have a missing connection or have not yet been integrated, because it's just too complex. This is exactly where we at WAGO started thinking: How can we solve this problem? With WAGO Energy Data Management, we have created a solution that can be used in brownfield and greenfield operations. A variety of connectors is available on the field side, such as connection via Modbus. So we can implement various already built-in meters TCP as well as RTU, digital inputs, analog inputs, WAGO meters or even our 3-phase power measurement module. In this way, the customer gets a variety of transparency from the field, in order to bring the right information to the right places. The data is stored, transmitted and visualized in the WAGO Controller. Today, we use MQTT, OPC UA and Modbus as transmission protocols, which are common protocols for energy management, but also in other industrial applications. Here it does not matter what and where the target system is, whether that is on-premise, in the Cloud or simply a database. Everything can be contacted and integrated by us. Now, let's take a look at what the whole thing looks like in practice now, using this topology as an example. This example is from our customer Clariant, who uses WAGO Controllers in various plants, which connect the field sensors to the WAGO Cloud via the integrated modem. This data is transferred to the WAGO Cloud via MQTT. In the WAGO Cloud Clariant uses the functionality of remote access so that they can remotely reconfigure their controllers at any time thus expand or adapt their energy management. In addition, the requirement of the visualization was to be as flexible as possible. Clariant had the idea to use the company Microsoft and the solution Power BI. To make the data available there as well, we use our REST:API, which is connected to the WAGO Cloud, to access the data and transfer it to Power BI. Exactly about this experience I would like to talk now with Clariant and there with Dr. Riest. He is part of the eWatch team at Clariant. And I'm very pleased to be able to invlove him here. Hello Mr. Riest. Hello Mr. Dökel. Mr. Riest, maybe you can say something about the eWatch team and how the WAGO Energy Data Management has helped you in your daily business. One of the strategic pillars of the company Clariant is the topic of sustainability. And we have set ourselves new sustainability targets and want to reduce CO2 emissions at our locations by 40 percent by 2030. And to support that technically, we have a global energy efficiency program called eWatch. And we are currently four colleagues who are setting up and running this eWatch program worldwide. And this is a very comprehensive program, which, in addition to technical optimization, also addresses the mindset and also a corresponding energy data online monitoring system to support technical optimization. As an example, maybe we can look at the dasboard generated via the Rest:API and Power BI. What kind of meaningfulness do you get from that? We have a lot of medium-sized and smaller locations, which currently often don't have a local data collection system, and therefore we use our company's own cloud to collect data at these small and medium-sized locations via data gateways and energy meters among others from WAGO. And then to apply advanced analytics and artificial intelligence algorithms to this data in our cloud, in addition to optimizing the mode of operation. In order to technically optimize the systems and also to set up reporting. Great! The eWatch team supports your locations worldwide. Maybe you can give a brief insight into how how this remote access and remote configuration from the cloud has helped you with the devices? Yes. The device management, the central and also the remote maintainability and configurability, those are absolutely essential. Otherwise, you can't manage and provide this large number of data gateways centrally, because adjustments are necessary again and again as measurements are added, etc., to enable remote configuration. And then the data gets transferred from the WAGO Cloud to our own cloud with the Rest:API, and all options are open to us there as well. Super! So I would say a future-proof concept. Thank you very much, Dr. Riest for that insight. You're welcome. If you are also thinking about the possibilities with WAGO Energy Data Management, feel free to contact us. Let's discuss which optimization potentials are also possible for you. I look forward to it. Thank you very much. Welcome back after our journey with six stops through the world of automation and digitization. I would like to remind you once again that WAGO also has rail-mounted terminal blocks, power supply units and transmitters in its product range. And if any of these topics are of interest to you. or if you would like to have another piece of MTP cake with us, please do not hesitate to make an appointment with us on the page of the Hannover Messe or also on wago.de or wago.com. Until this appointment, I remain and wish you a nice further stay at Hannover Messe. Thanks for listening and bye!