Episode 01: Unlocking Value by Decoupling Software and Hardware with UniversalAutomation.org | UAO Goes Live: The Future of Automation

Description

In this first episode of UAO Goes Live, we explore how UniversalAutomation.org is transforming industrial automation by decoupling software from hardware through the IEC 61499 standard. Discover why this approach is considered a game-changer for the industry, enabling portability, interoperability, and innovation.

Greg Boucaud, Chief Marketing Officer at UniversalAutomation.org, explains how this open technology empowers vendors and end-users to break free from vendor lock-in, accelerate time-to-market, and embrace new business models. Learn how Universal Automation fosters collaboration between IT and OT, supports greenfield and brownfield applications, and creates an ecosystem similar to an “industrial automation app store.”

Whether you are an automation engineer, system integrator, or technology leader, this episode provides valuable insights into the future of automation, open standards, and the next generation of industrial control systems.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
The world of automation is undergoing a paradigm shift. This changes everything. Welcome to Universal Automation. The world of plug-in produced software components, making complex things simple and reliable. Think of it as the dawn of an industrial automation app store. The IEC 61499 standard is the key to portability and interoperability. UniversalAutomation.org is the community-managing and industrial-grade reference implementation of 61499 because no one vendor or company or person can bring about transformation on their own. UniversalAutomation allows us to use software and hardware in a whole new way to create portable applications and innovative architectures. For the first time, IT and OT engineers can easily work together, combining real-time with right-time to create cost-effective and innovative ways to address complex use cases, like predictive maintenance, production optimization, and virtual commissioning. But how does universal automation really impact you? Vendors can use the Universal Automation Reference Implementation to bring IEC 61499 offers to market fast. That means new software revenues, new business models, and new customers. Universal Automation frees industrial enterprises to integrate best-of-breed components and proven in-use software. You can realize step-change advancements in efficiency, flexibility, and modularity with agile operational models. It's time for us to release the full potential of the fourth industrial revolution. Be a part of the community delivering the solution. Join UniversalAutomation.org.
Speaker #1
Hi everybody and good day to you. Welcome to this first session of the UAO Goes Live. So what's UAO? Universalautomation.org, this new non-profit association which was created a couple of years ago in 2021. So today my name is Greg Boucaud and I'm the Chief Marketing Officer for this organization. So please bear with me as we go through the slide presentation of what is Universal Automation Network, so I can give you a bit more of insights. Then, instead, to come with your questions, as we'll have a Q&A session at the end, and I'll be happy to answer them. So, before we go to the next slide, I would like to hear it from the members.
Speaker #2
Universal Automation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We call it a game changer in automation because we have first one technology which is based on the IEC 6499 which is the standard which aims at decoupling hardware and software.
Speaker #2
Hardware itself is becoming very very performant in terms of processing CPU power.
Speaker #3
And the future is more and more about software. This approach is really a winning approach because it's very, very flexible. You develop the application once and you can reuse in each different configuration.
Speaker #4
That's exactly what Universal Automation and 61499 enables because it brings a new formalism for developing software which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that is the marriage made in heaven.
Speaker #5
So if I want to make more conscious decisions based on my business data which also comes from the automation level, I need Universal Automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #2
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy. and from other companies.
Speaker #6
Advantech is growing really, really fast and I believe if you want to keep on growing in the next future you need to be able to innovate. When I see Universal Automation approach it is exactly the way of innovation we need to go with.
Speaker #7
Most of our customers from Process Automation are pretty conservative to never change a running system but now we see a new generation coming up. what is used to new technologies and they are open to test to try these new functionalities and I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years and I think over the years this is the most exciting changes.
Speaker #3
And from my experience I see that in the IT for example there has been a big revolution and I expect the same in automation. I don't know when it will happen. Probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Welcome back. On the verge of a revolution, that is what is universalautomation.org. So let's start from the beginning. What do we see now in the industrial automation market? We see different situations. We see that the way automation has been done until today is great, but still has some drawbacks when it comes to bringing innovation to the market. It's not easy to update the program that you're using. When you have end of life, the same thing, you are struggling to get your hardware upgraded to the next generation. We can speak about software we use today, the lifecycle of the software. So everything that you implement in your automation program is tightly linked to the hardware on which it runs. So you want to reuse it across different platforms? Well, it's most likely that you can do it today. If we speak about... multiple supplier strategies. So for sure, we are out of this COVID phase, but still some of the customers, some of the end users are struggling with getting some products supplied. So sometimes they need to change for one reason or another, change supplier. So they are stuck with one or two suppliers maybe today. Let's think about the future. Future is about the new talents. And we see here that... in the automation field it's becoming more and more difficult to get young talents interested in the field of automation and which is for example not the case for the field of it so how to bring those those youth talents uh uh back to us and back in in automation and and those this is all those points which universal automation.org is tackling uh overcoming the vendor locks and the the ability to to innovate and for that what do you need you need to rethink the way you are doing automation on the market so the way we are doing uh automation on the way we think we should be doing information with universal automation network is first by decoupling the hardware from the software and enable this portability of application so think about it you are developing your automation application and for this automation application you need to implement, let's say, interoperability or interlink with some IT services. And for that, for sure, either you have the knowledge in-house to do it, either you have it maybe in a library given by your supplier, but then it will really depend on the supplier you are taking. But most likely, you won't be able to reuse something which has been done on the market because it really depends on your hardware topology. What if this could work the same way as what you do in the IT field? So meaning that you have your laptop today running with Windows, you want to install a software, you just take the first software that you see and can install, which does exactly what you need to. And you are not looking for which is the supplier of this hardware. Fundamentally, object-oriented, closer to the assets, closer to the representation, the physical representation of what you are trying to deal with. very asset-centric and appealing to the next generation, meaning that with the capability of using the latest programming languages, and which are already used in the IT system. For that, we have the concept of universal automation. Universal automation is basically two things. One thing is an innovative technology. This innovative technology stands with standard, IEC standard, which is called the 64099, which is the evolution of the today mostly used standards on the market for automation. And these standards aims at, let's say, enlarging the previous standard by adding the decoupling of hardware and software, and adding the possibility to program entire system and distribute this programming amongst multiple CPUs, so basically programming power. And for that, we have within universalautomation.org, a reference limitation of that standard. So meaning that we don't work directly on the 64999 standard, but we are working with a reference limitation of it. So you can compare it of the same as what you see in those Linux environment. So today, lots of people are saying, okay, we use Linux. But in fact, people are using a distribution of Linux. So it could be Ubuntu, Debian, Yocto, whatever distribution which is available on the market, which is at the end a reference implementation of And this is exactly the same what we are doing for the 6.499, which is providing a reference implementation to the market so that people can implement it and go and use it in a faster way. But having a reference implementation is not enough. You need more. Having more means that you need a community around it. This community is universalautomation.org. So it's a community of both users of automation and technology vendors. Users of automation, I take the full chain of users. So starting with end users, system integrator, process OEM, machine builders, distributors, down to even youngs in universities, startups, those are included. And technology vendors, those who are putting the product on the market, which embed that reference implementation. So that is what is Universal Automation Network. And the goal... of that is to create an environment similar to what you see in the Android world with smartphones having the possibility to, let's say, play or run different software coming from different providers on different hardware platforms. And this is the same what we will achieve with Unimersive Automation Network. But I think I have spoken enough. and I prefer to let the members speak for us and confirm what is the portability and the little probability of UAO.
Speaker #8
We built our code, we imported it into the system that UAO is based on, and it ran. It just ran, we thought. Try that with any other two vendors.
Speaker #7
It is interoperable. You don't need to do any fine-tuning, any adjustment. It just works together. And it's not just the communication network, it's the whole functionality. So literally a part of the system can be installed over there and the other part can be installed in Australia. And it will work together.
Speaker #1
So you have heard that from our members. They're using it. They say it's working. So it's not something which is like in the air, something that we are inventing or whatever. This is today something which is working and which is used. Let's come back to the standard. Let's say to the base of the technology behind. The 649 standard, it's made with, let's say, three simple things. The first being event-driven function blocks. So. Event-driven, meaning that we work in the same way as what the IT is doing. IT is working more with transaction. And we do the same for automation, embedding the ability to work with events. And so those events are triggering a program, making whatever, so an addition, a function, whatever you need it to do to work in an application. But this function, as you see it, here is a simple, let's say, block. or whatever, but this could be at the end your boiler, this could be your conveyor, this could be a furnace for example in your application. So this block is in fact a representation of your physical asset. It could be a function but it could be as well representing your physical assets. This block has the ability so you can program it inside and take the programming language which which you want to to program the the the function block but it's a self-contained software component so meaning that when you re when you have it when you receive it when you download it from somewhere and you want to reuse it it comes with all the functionality that you need this function block is not developed for a special hardware but it's developed for doing a special application for you and you can then deploy it on your targeted hardware And the way to do that, it's simple. It's using the same principle of the 64099 standard, which is using the application model. So application model is the way you draw your application by coupling together those function blocks and making your application live. So your conveyor with your reader, with your furnace, with your whatever assets you have in your application, knowing that those assets could be assets from, let's say, the process automation world, could be assets from the diskit world, could be assets from the hybrid world. you name it, because this company is this, this, this technology is hardware segment agnostic. And then at some point you need to decide which hardware you want it to run to. And this is what we call the device model. So it's simply selecting which hardware you want to use for your application. And here you see already the major change compared to automation today. Automation today, you start with your hardware topology. So you start. usually in a centralized way with your hardware, with your CPU, your IOs and everything. And from this topology, you do your programming. It's quite good. The only drawback is that if at some point you need to change your programming or add some new functionalities when your CPU is already overloaded, then you need to make some exchange and you need to ensure that both programs which are running in two different CPUs our processing units can communicate together. Here, with the six-part challenge time, you start first with what is your automation situation? What do you want to program? You program it the same way you do it in the IT fields, and then you deploy to the targeted hardware. The phase which is thinking about which hardware I want to use for my application comes later. you first focus on what you want to achieve and then deploy to your hardware. And from that, we go to the third part of the 64099, which is the system model. The system model is the way to assign your application, so your blocks that you have plugged together to draw your application, to some devices. And those devices could be simple as what you see today, could be IPCs, could be Docker container, could be server. So here we go out from the, let's say, PLC-centric way to whatever processing unit able to process my program. And this is what we have and what we use to produce this ecosystem of Prangent Produce software components, which are independent of the hardware. And this is the core of the 649 and the core of what is Universal Automation.org. Because as said, Here, I've just explained the standard. After the standard, there is the reference implementation, which is managed by the association, Universal Automation Network. Managed by the association, which is the community of users and vendors, which I've told you before. Users, vendors, universities, startup, which are organized to maintain and further develop and deploy on the market. this reference implementation of the standard. So what we promote mainly is the portability and reusability of software application and software application across hardware platform. But for sure, we have many other benefits which are coming from the standard itself. And the way it is done for those who really want to deep dive into the technology, the way it is done is that this reference implementation, this, we can call it runtime execution engine, or basically it's a piece of software which runs on your CPU and runs on your operating system. So again, we are not replacing any operating system. We use them. So today, if you're using Linux or whatever operating system on your devices, you can be able to run the runtime onto it. And this runtime is basically receiving the part of the application which is dedicated to it through the build time. through the studio, through the engineering tool, where you design your application. And that is universalautomation.org. And why doing that? Why doing that? Because at the end, the goal is that you go out from this 80% programming for yourself, which is for your application, and 20% maybe reusing, maybe using from using some libraries or reusing from previous projects. Usually, there are still always some changes to be done, but go out from this 80%, 20% to balance that and say, okay, 80% I can reuse because this is already on the market and I don't need to reinvent the wheel every time. I can just reuse what is available for me over there and do the 20%, which is really typical to my application. So reduce that, reduce the complexity, increase... the the safety around your your your programming for example And by that, we're using those libraries, meaning that in the future, with that ecosystem being created, you will see more and more software being developed around segment-specific software. So a company doing great, for example, in water-west water and having a great functionality which wants to be developed to others without having to develop, let's say, the whole hardware architecture around it, but just selling the software. IoT specific. things like digital twin, like AI in your production, for example. Could be mechatronics, your robots had your robots in your application in a simple way, or even reuse and wrap what is already existing. Because you may think at this point that this technology is only for greenfield application, which is not the case. We can as well handle the brownfield application. by wrapping them and by orchestrating them. And we will have an example just after that. So the way you do it, you take your blocks, I said 80% reusing, 20% doing yourself. So you take mostly your blocks from your marketplaces and do the rest yourself. You can make your own programming, so application model. Select your hardware technology, which really comes toward the end. And once you have done that, you can just deploy your application. and then the entire communication between controllers or between, let's say, devices is done automatically and handled by the runtime itself. So really coming to, let's say, more flexibility into the programming, at the same time more efficiency because you can finally reuse what you have done and increase your return on investment on your software. because the software is no longer done for a typical hardware and for a typical life cycle but the life cycle of the software becomes independent from the life cycle of the hardware so again i can tell you a lot about it but i prefer when the when the members speech so let's let's hear it from them because
Speaker #9
in our vision the way we're moving With our company we need a different way of programming and this tool set was actually very promising and it still is kind of enabling that what we want to achieve.
Speaker #10
One of the reasons we're a member of this is we see the OT transformation happening in front of us so I think the IEC 61499 specification in general is a central set of capabilities right to which you can host 1131 or not. as was mentioned and achieve your goals long term with the flexibility you need for all the new stuff that's coming down the pike right whether it's you know some artificial intelligent llm on the scale we all need to learn something more but
Speaker #8
it's not that hard and once you start using it you'll start to realize oh this is way better cell phones better than a wall phone all our technologies we have today are way better this is another one of those
Speaker #1
Universal Automation Network, a community, but who are those companies who decided, those organizations who decided to go with us down the road? So as said, and as a reminder, we started this whole initiative in November 2021, so a bit more than two years ago, with nine founding members. Today, we are close to 80 members from different categories, vendors, users, universities and startups. You can see here an overview of the companies which are going with us the way. But I mean, it's not only about companies, it's also about developing this ecosystem of products which are running with the UAO runtime. And this has already started because we have Today, 11 offers on the market which are using the runtime. So you can see those companies Advantech, ESRAC Industrial, ESA, Flexbridge, Konzberg, Odot, Belden, Stahl, Phoenix Contact and Schneider Electric. So those offers are already available, so it means that you can use them. And talking about using, let's speak about use cases. There are different use cases and I've decided to concentrate on only a few of them, using the companies which are members of the organization. So few companies such as, for example, ExxonMobil working a lot. on the open process automation from implementation and currently working on the first plant running with that, let's say, with a standard, and at the same time using the universal automation network runtime. So you have to see that our technology is a technology enabler for all the standards. So you have heard maybe about MTP. you have heard about. opath you have heard about other standards and you can see that universal automation.org is there to to help and is there to have a complementary approach by enabling those standards another example is the company concept my team so compare my team is doing um orange glass platform and and ships and in that case they are using the technology especially for for brand-feel applications, meaning that when you want to upgrade, when you want to update your ship or your OEM platform, you can simply add a layer with the devices running our technology. And this layer is orchestrating the applications across subsystems. So the subsystems are still running with the, let's say, the format technology which you are using. And if you want to... automate and you want to make those functionality running, let's say altogether, you can add this layer and add new functionalities and make the link as well with IT. This is the way we can still use universalautomation.org with Boundfield application. Another example, if we go into more the sustainability environment is the company called Geatrian. Geatrian is a Swiss company. which is currently doing their plant using the technology. And for them, for sure, they are working the plastic recycling. So they have a patent on a good way to recycle plastic using microwaves. And for them, the best, let's say, their intellectual property lies into the way how to do the process. They don't want to be linked to one supplier. but they want to be able to develop their architecture, to develop their application independently of the hardware on which it lies. And that's why the 64099 and Universal Automation.org was the best way to implement that. So for sure, we drive significant benefits for both users and vendors. The users, for sure, they become hardware independent, so they... break this vendor up, not meaning that they would necessarily go in the future with more multi-vendor strategy, but just saying that by breaking this lock, they have the ability after to really decouple their lifecycle of the software and make their investment into the software more sustainable in the future and not depending on the lifecycle of the hardware. Still, we have we do have some good benefits for the vendors, especially when it comes to working on the platform because here we deliver with the organization the reference documentation. So it means that for the vendors, it's really a copy and paste and we use what is already available. So a good platforming activity. And I want to tell it again, we need the help. of users, we need the help of vendors to grow this ecosystem. So for sure, we bring benefits to users by
Speaker #0
for sure networking activities, influencing by getting to know what is implemented and which features need to be implemented into the mission. So get active, join us, and you can drive the next generation of automation system. The same goes to vendors. If you want to take this part in this activity, that's the best way to do it is by joining universal automation at all because you can gain from the platforming activities which is done here and you do not have to reinvent the wheel yourself but just using the technology and you'll be benefits from the other libraries which are being developed nevertheless i don't forget the universities and the startups because we also target universities for sure we need to train the next generation and we need to ensure that the next generation of of of talents have the necessary knowledge to be able to to be able to go on the market and implement nice things, nice things using Universal Automation.org. So that's why universities are welcome to join us. So before we go to the Q&A, I propose you to listen again to the members to see what they have to say.
Speaker #1
It's really... A different kind of working. You can really use different kind of hardware. You can bring easier new functionality in and I think this is all about sustainability. We see it here in the room and I think to really do something different, faster, more efficient, I think this is really what we all are looking for.
Speaker #2
You will also say, that's marketing, you will promise us a lot. Test it, try it, do a test installation. And I'm very sure you will be very impressed about the functionality. So all in all, a great package.
Speaker #0
Okay, now we are back together. This was the last point. So just I will have a look in to see if there are some maybe some questions in the chat as of now. I see. Okay, I see one question which is about how to join the organization. So join the organization is a very simple process. Here you see all the links which are available, but the most important one is to go to the website. On the website, you have the possibility to send us a message. So please use that, send us a message, and we'll come back to you. Just to make it clear here, the join... joining the association is really made for organization so if you are a company willing to join the the adventure please feel free to do so if you are in university willing to join the university the universal automation network please feel free to join to to do it we can help you we can help you set up some courses on the technology i thank you all and i wish you a good day don't hesitate to get back to us either linkedin youtube we are here so thank you and have a good day bye

About UAO Goes Live: The Future of Automation

UAO Goes Live brings the conversations from our popular LinkedIn Live series directly to your favorite podcast platform. Each episode explores the world of open, interoperable automation powered by IEC 61499. Join industry leaders, innovators, and experts as they share real-world applications, success stories, and insights that are shaping the future of industrial automation.

Whether you are an engineer, a technology leader, or simply passionate about the next wave of automation, this podcast is your go-to source for cutting-edge discussions, practical knowledge, and thought leadership.

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Description

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
The world of automation is undergoing a paradigm shift. This changes everything. Welcome to Universal Automation. The world of plug-in produced software components, making complex things simple and reliable. Think of it as the dawn of an industrial automation app store. The IEC 61499 standard is the key to portability and interoperability. UniversalAutomation.org is the community-managing and industrial-grade reference implementation of 61499 because no one vendor or company or person can bring about transformation on their own. UniversalAutomation allows us to use software and hardware in a whole new way to create portable applications and innovative architectures. For the first time, IT and OT engineers can easily work together, combining real-time with right-time to create cost-effective and innovative ways to address complex use cases, like predictive maintenance, production optimization, and virtual commissioning. But how does universal automation really impact you? Vendors can use the Universal Automation Reference Implementation to bring IEC 61499 offers to market fast. That means new software revenues, new business models, and new customers. Universal Automation frees industrial enterprises to integrate best-of-breed components and proven in-use software. You can realize step-change advancements in efficiency, flexibility, and modularity with agile operational models. It's time for us to release the full potential of the fourth industrial revolution. Be a part of the community delivering the solution. Join UniversalAutomation.org.
Speaker #1
Hi everybody and good day to you. Welcome to this first session of the UAO Goes Live. So what's UAO? Universalautomation.org, this new non-profit association which was created a couple of years ago in 2021. So today my name is Greg Boucaud and I'm the Chief Marketing Officer for this organization. So please bear with me as we go through the slide presentation of what is Universal Automation Network, so I can give you a bit more of insights. Then, instead, to come with your questions, as we'll have a Q&A session at the end, and I'll be happy to answer them. So, before we go to the next slide, I would like to hear it from the members.
Speaker #2
Universal Automation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We call it a game changer in automation because we have first one technology which is based on the IEC 6499 which is the standard which aims at decoupling hardware and software.
Speaker #2
Hardware itself is becoming very very performant in terms of processing CPU power.
Speaker #3
And the future is more and more about software. This approach is really a winning approach because it's very, very flexible. You develop the application once and you can reuse in each different configuration.
Speaker #4
That's exactly what Universal Automation and 61499 enables because it brings a new formalism for developing software which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that is the marriage made in heaven.
Speaker #5
So if I want to make more conscious decisions based on my business data which also comes from the automation level, I need Universal Automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #2
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy. and from other companies.
Speaker #6
Advantech is growing really, really fast and I believe if you want to keep on growing in the next future you need to be able to innovate. When I see Universal Automation approach it is exactly the way of innovation we need to go with.
Speaker #7
Most of our customers from Process Automation are pretty conservative to never change a running system but now we see a new generation coming up. what is used to new technologies and they are open to test to try these new functionalities and I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years and I think over the years this is the most exciting changes.
Speaker #3
And from my experience I see that in the IT for example there has been a big revolution and I expect the same in automation. I don't know when it will happen. Probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Welcome back. On the verge of a revolution, that is what is universalautomation.org. So let's start from the beginning. What do we see now in the industrial automation market? We see different situations. We see that the way automation has been done until today is great, but still has some drawbacks when it comes to bringing innovation to the market. It's not easy to update the program that you're using. When you have end of life, the same thing, you are struggling to get your hardware upgraded to the next generation. We can speak about software we use today, the lifecycle of the software. So everything that you implement in your automation program is tightly linked to the hardware on which it runs. So you want to reuse it across different platforms? Well, it's most likely that you can do it today. If we speak about... multiple supplier strategies. So for sure, we are out of this COVID phase, but still some of the customers, some of the end users are struggling with getting some products supplied. So sometimes they need to change for one reason or another, change supplier. So they are stuck with one or two suppliers maybe today. Let's think about the future. Future is about the new talents. And we see here that... in the automation field it's becoming more and more difficult to get young talents interested in the field of automation and which is for example not the case for the field of it so how to bring those those youth talents uh uh back to us and back in in automation and and those this is all those points which universal automation.org is tackling uh overcoming the vendor locks and the the ability to to innovate and for that what do you need you need to rethink the way you are doing automation on the market so the way we are doing uh automation on the way we think we should be doing information with universal automation network is first by decoupling the hardware from the software and enable this portability of application so think about it you are developing your automation application and for this automation application you need to implement, let's say, interoperability or interlink with some IT services. And for that, for sure, either you have the knowledge in-house to do it, either you have it maybe in a library given by your supplier, but then it will really depend on the supplier you are taking. But most likely, you won't be able to reuse something which has been done on the market because it really depends on your hardware topology. What if this could work the same way as what you do in the IT field? So meaning that you have your laptop today running with Windows, you want to install a software, you just take the first software that you see and can install, which does exactly what you need to. And you are not looking for which is the supplier of this hardware. Fundamentally, object-oriented, closer to the assets, closer to the representation, the physical representation of what you are trying to deal with. very asset-centric and appealing to the next generation, meaning that with the capability of using the latest programming languages, and which are already used in the IT system. For that, we have the concept of universal automation. Universal automation is basically two things. One thing is an innovative technology. This innovative technology stands with standard, IEC standard, which is called the 64099, which is the evolution of the today mostly used standards on the market for automation. And these standards aims at, let's say, enlarging the previous standard by adding the decoupling of hardware and software, and adding the possibility to program entire system and distribute this programming amongst multiple CPUs, so basically programming power. And for that, we have within universalautomation.org, a reference limitation of that standard. So meaning that we don't work directly on the 64999 standard, but we are working with a reference limitation of it. So you can compare it of the same as what you see in those Linux environment. So today, lots of people are saying, okay, we use Linux. But in fact, people are using a distribution of Linux. So it could be Ubuntu, Debian, Yocto, whatever distribution which is available on the market, which is at the end a reference implementation of And this is exactly the same what we are doing for the 6.499, which is providing a reference implementation to the market so that people can implement it and go and use it in a faster way. But having a reference implementation is not enough. You need more. Having more means that you need a community around it. This community is universalautomation.org. So it's a community of both users of automation and technology vendors. Users of automation, I take the full chain of users. So starting with end users, system integrator, process OEM, machine builders, distributors, down to even youngs in universities, startups, those are included. And technology vendors, those who are putting the product on the market, which embed that reference implementation. So that is what is Universal Automation Network. And the goal... of that is to create an environment similar to what you see in the Android world with smartphones having the possibility to, let's say, play or run different software coming from different providers on different hardware platforms. And this is the same what we will achieve with Unimersive Automation Network. But I think I have spoken enough. and I prefer to let the members speak for us and confirm what is the portability and the little probability of UAO.
Speaker #8
We built our code, we imported it into the system that UAO is based on, and it ran. It just ran, we thought. Try that with any other two vendors.
Speaker #7
It is interoperable. You don't need to do any fine-tuning, any adjustment. It just works together. And it's not just the communication network, it's the whole functionality. So literally a part of the system can be installed over there and the other part can be installed in Australia. And it will work together.
Speaker #1
So you have heard that from our members. They're using it. They say it's working. So it's not something which is like in the air, something that we are inventing or whatever. This is today something which is working and which is used. Let's come back to the standard. Let's say to the base of the technology behind. The 649 standard, it's made with, let's say, three simple things. The first being event-driven function blocks. So. Event-driven, meaning that we work in the same way as what the IT is doing. IT is working more with transaction. And we do the same for automation, embedding the ability to work with events. And so those events are triggering a program, making whatever, so an addition, a function, whatever you need it to do to work in an application. But this function, as you see it, here is a simple, let's say, block. or whatever, but this could be at the end your boiler, this could be your conveyor, this could be a furnace for example in your application. So this block is in fact a representation of your physical asset. It could be a function but it could be as well representing your physical assets. This block has the ability so you can program it inside and take the programming language which which you want to to program the the the function block but it's a self-contained software component so meaning that when you re when you have it when you receive it when you download it from somewhere and you want to reuse it it comes with all the functionality that you need this function block is not developed for a special hardware but it's developed for doing a special application for you and you can then deploy it on your targeted hardware And the way to do that, it's simple. It's using the same principle of the 64099 standard, which is using the application model. So application model is the way you draw your application by coupling together those function blocks and making your application live. So your conveyor with your reader, with your furnace, with your whatever assets you have in your application, knowing that those assets could be assets from, let's say, the process automation world, could be assets from the diskit world, could be assets from the hybrid world. you name it, because this company is this, this, this technology is hardware segment agnostic. And then at some point you need to decide which hardware you want it to run to. And this is what we call the device model. So it's simply selecting which hardware you want to use for your application. And here you see already the major change compared to automation today. Automation today, you start with your hardware topology. So you start. usually in a centralized way with your hardware, with your CPU, your IOs and everything. And from this topology, you do your programming. It's quite good. The only drawback is that if at some point you need to change your programming or add some new functionalities when your CPU is already overloaded, then you need to make some exchange and you need to ensure that both programs which are running in two different CPUs our processing units can communicate together. Here, with the six-part challenge time, you start first with what is your automation situation? What do you want to program? You program it the same way you do it in the IT fields, and then you deploy to the targeted hardware. The phase which is thinking about which hardware I want to use for my application comes later. you first focus on what you want to achieve and then deploy to your hardware. And from that, we go to the third part of the 64099, which is the system model. The system model is the way to assign your application, so your blocks that you have plugged together to draw your application, to some devices. And those devices could be simple as what you see today, could be IPCs, could be Docker container, could be server. So here we go out from the, let's say, PLC-centric way to whatever processing unit able to process my program. And this is what we have and what we use to produce this ecosystem of Prangent Produce software components, which are independent of the hardware. And this is the core of the 649 and the core of what is Universal Automation.org. Because as said, Here, I've just explained the standard. After the standard, there is the reference implementation, which is managed by the association, Universal Automation Network. Managed by the association, which is the community of users and vendors, which I've told you before. Users, vendors, universities, startup, which are organized to maintain and further develop and deploy on the market. this reference implementation of the standard. So what we promote mainly is the portability and reusability of software application and software application across hardware platform. But for sure, we have many other benefits which are coming from the standard itself. And the way it is done for those who really want to deep dive into the technology, the way it is done is that this reference implementation, this, we can call it runtime execution engine, or basically it's a piece of software which runs on your CPU and runs on your operating system. So again, we are not replacing any operating system. We use them. So today, if you're using Linux or whatever operating system on your devices, you can be able to run the runtime onto it. And this runtime is basically receiving the part of the application which is dedicated to it through the build time. through the studio, through the engineering tool, where you design your application. And that is universalautomation.org. And why doing that? Why doing that? Because at the end, the goal is that you go out from this 80% programming for yourself, which is for your application, and 20% maybe reusing, maybe using from using some libraries or reusing from previous projects. Usually, there are still always some changes to be done, but go out from this 80%, 20% to balance that and say, okay, 80% I can reuse because this is already on the market and I don't need to reinvent the wheel every time. I can just reuse what is available for me over there and do the 20%, which is really typical to my application. So reduce that, reduce the complexity, increase... the the safety around your your your programming for example And by that, we're using those libraries, meaning that in the future, with that ecosystem being created, you will see more and more software being developed around segment-specific software. So a company doing great, for example, in water-west water and having a great functionality which wants to be developed to others without having to develop, let's say, the whole hardware architecture around it, but just selling the software. IoT specific. things like digital twin, like AI in your production, for example. Could be mechatronics, your robots had your robots in your application in a simple way, or even reuse and wrap what is already existing. Because you may think at this point that this technology is only for greenfield application, which is not the case. We can as well handle the brownfield application. by wrapping them and by orchestrating them. And we will have an example just after that. So the way you do it, you take your blocks, I said 80% reusing, 20% doing yourself. So you take mostly your blocks from your marketplaces and do the rest yourself. You can make your own programming, so application model. Select your hardware technology, which really comes toward the end. And once you have done that, you can just deploy your application. and then the entire communication between controllers or between, let's say, devices is done automatically and handled by the runtime itself. So really coming to, let's say, more flexibility into the programming, at the same time more efficiency because you can finally reuse what you have done and increase your return on investment on your software. because the software is no longer done for a typical hardware and for a typical life cycle but the life cycle of the software becomes independent from the life cycle of the hardware so again i can tell you a lot about it but i prefer when the when the members speech so let's let's hear it from them because
Speaker #9
in our vision the way we're moving With our company we need a different way of programming and this tool set was actually very promising and it still is kind of enabling that what we want to achieve.
Speaker #10
One of the reasons we're a member of this is we see the OT transformation happening in front of us so I think the IEC 61499 specification in general is a central set of capabilities right to which you can host 1131 or not. as was mentioned and achieve your goals long term with the flexibility you need for all the new stuff that's coming down the pike right whether it's you know some artificial intelligent llm on the scale we all need to learn something more but
Speaker #8
it's not that hard and once you start using it you'll start to realize oh this is way better cell phones better than a wall phone all our technologies we have today are way better this is another one of those
Speaker #1
Universal Automation Network, a community, but who are those companies who decided, those organizations who decided to go with us down the road? So as said, and as a reminder, we started this whole initiative in November 2021, so a bit more than two years ago, with nine founding members. Today, we are close to 80 members from different categories, vendors, users, universities and startups. You can see here an overview of the companies which are going with us the way. But I mean, it's not only about companies, it's also about developing this ecosystem of products which are running with the UAO runtime. And this has already started because we have Today, 11 offers on the market which are using the runtime. So you can see those companies Advantech, ESRAC Industrial, ESA, Flexbridge, Konzberg, Odot, Belden, Stahl, Phoenix Contact and Schneider Electric. So those offers are already available, so it means that you can use them. And talking about using, let's speak about use cases. There are different use cases and I've decided to concentrate on only a few of them, using the companies which are members of the organization. So few companies such as, for example, ExxonMobil working a lot. on the open process automation from implementation and currently working on the first plant running with that, let's say, with a standard, and at the same time using the universal automation network runtime. So you have to see that our technology is a technology enabler for all the standards. So you have heard maybe about MTP. you have heard about. opath you have heard about other standards and you can see that universal automation.org is there to to help and is there to have a complementary approach by enabling those standards another example is the company concept my team so compare my team is doing um orange glass platform and and ships and in that case they are using the technology especially for for brand-feel applications, meaning that when you want to upgrade, when you want to update your ship or your OEM platform, you can simply add a layer with the devices running our technology. And this layer is orchestrating the applications across subsystems. So the subsystems are still running with the, let's say, the format technology which you are using. And if you want to... automate and you want to make those functionality running, let's say altogether, you can add this layer and add new functionalities and make the link as well with IT. This is the way we can still use universalautomation.org with Boundfield application. Another example, if we go into more the sustainability environment is the company called Geatrian. Geatrian is a Swiss company. which is currently doing their plant using the technology. And for them, for sure, they are working the plastic recycling. So they have a patent on a good way to recycle plastic using microwaves. And for them, the best, let's say, their intellectual property lies into the way how to do the process. They don't want to be linked to one supplier. but they want to be able to develop their architecture, to develop their application independently of the hardware on which it lies. And that's why the 64099 and Universal Automation.org was the best way to implement that. So for sure, we drive significant benefits for both users and vendors. The users, for sure, they become hardware independent, so they... break this vendor up, not meaning that they would necessarily go in the future with more multi-vendor strategy, but just saying that by breaking this lock, they have the ability after to really decouple their lifecycle of the software and make their investment into the software more sustainable in the future and not depending on the lifecycle of the hardware. Still, we have we do have some good benefits for the vendors, especially when it comes to working on the platform because here we deliver with the organization the reference documentation. So it means that for the vendors, it's really a copy and paste and we use what is already available. So a good platforming activity. And I want to tell it again, we need the help. of users, we need the help of vendors to grow this ecosystem. So for sure, we bring benefits to users by
Speaker #0
for sure networking activities, influencing by getting to know what is implemented and which features need to be implemented into the mission. So get active, join us, and you can drive the next generation of automation system. The same goes to vendors. If you want to take this part in this activity, that's the best way to do it is by joining universal automation at all because you can gain from the platforming activities which is done here and you do not have to reinvent the wheel yourself but just using the technology and you'll be benefits from the other libraries which are being developed nevertheless i don't forget the universities and the startups because we also target universities for sure we need to train the next generation and we need to ensure that the next generation of of of talents have the necessary knowledge to be able to to be able to go on the market and implement nice things, nice things using Universal Automation.org. So that's why universities are welcome to join us. So before we go to the Q&A, I propose you to listen again to the members to see what they have to say.
Speaker #1
It's really... A different kind of working. You can really use different kind of hardware. You can bring easier new functionality in and I think this is all about sustainability. We see it here in the room and I think to really do something different, faster, more efficient, I think this is really what we all are looking for.
Speaker #2
You will also say, that's marketing, you will promise us a lot. Test it, try it, do a test installation. And I'm very sure you will be very impressed about the functionality. So all in all, a great package.
Speaker #0
Okay, now we are back together. This was the last point. So just I will have a look in to see if there are some maybe some questions in the chat as of now. I see. Okay, I see one question which is about how to join the organization. So join the organization is a very simple process. Here you see all the links which are available, but the most important one is to go to the website. On the website, you have the possibility to send us a message. So please use that, send us a message, and we'll come back to you. Just to make it clear here, the join... joining the association is really made for organization so if you are a company willing to join the the adventure please feel free to do so if you are in university willing to join the university the universal automation network please feel free to join to to do it we can help you we can help you set up some courses on the technology i thank you all and i wish you a good day don't hesitate to get back to us either linkedin youtube we are here so thank you and have a good day bye

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Embed

You may also like

Description

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
The world of automation is undergoing a paradigm shift. This changes everything. Welcome to Universal Automation. The world of plug-in produced software components, making complex things simple and reliable. Think of it as the dawn of an industrial automation app store. The IEC 61499 standard is the key to portability and interoperability. UniversalAutomation.org is the community-managing and industrial-grade reference implementation of 61499 because no one vendor or company or person can bring about transformation on their own. UniversalAutomation allows us to use software and hardware in a whole new way to create portable applications and innovative architectures. For the first time, IT and OT engineers can easily work together, combining real-time with right-time to create cost-effective and innovative ways to address complex use cases, like predictive maintenance, production optimization, and virtual commissioning. But how does universal automation really impact you? Vendors can use the Universal Automation Reference Implementation to bring IEC 61499 offers to market fast. That means new software revenues, new business models, and new customers. Universal Automation frees industrial enterprises to integrate best-of-breed components and proven in-use software. You can realize step-change advancements in efficiency, flexibility, and modularity with agile operational models. It's time for us to release the full potential of the fourth industrial revolution. Be a part of the community delivering the solution. Join UniversalAutomation.org.
Speaker #1
Hi everybody and good day to you. Welcome to this first session of the UAO Goes Live. So what's UAO? Universalautomation.org, this new non-profit association which was created a couple of years ago in 2021. So today my name is Greg Boucaud and I'm the Chief Marketing Officer for this organization. So please bear with me as we go through the slide presentation of what is Universal Automation Network, so I can give you a bit more of insights. Then, instead, to come with your questions, as we'll have a Q&A session at the end, and I'll be happy to answer them. So, before we go to the next slide, I would like to hear it from the members.
Speaker #2
Universal Automation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We call it a game changer in automation because we have first one technology which is based on the IEC 6499 which is the standard which aims at decoupling hardware and software.
Speaker #2
Hardware itself is becoming very very performant in terms of processing CPU power.
Speaker #3
And the future is more and more about software. This approach is really a winning approach because it's very, very flexible. You develop the application once and you can reuse in each different configuration.
Speaker #4
That's exactly what Universal Automation and 61499 enables because it brings a new formalism for developing software which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that is the marriage made in heaven.
Speaker #5
So if I want to make more conscious decisions based on my business data which also comes from the automation level, I need Universal Automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #2
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy. and from other companies.
Speaker #6
Advantech is growing really, really fast and I believe if you want to keep on growing in the next future you need to be able to innovate. When I see Universal Automation approach it is exactly the way of innovation we need to go with.
Speaker #7
Most of our customers from Process Automation are pretty conservative to never change a running system but now we see a new generation coming up. what is used to new technologies and they are open to test to try these new functionalities and I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years and I think over the years this is the most exciting changes.
Speaker #3
And from my experience I see that in the IT for example there has been a big revolution and I expect the same in automation. I don't know when it will happen. Probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Welcome back. On the verge of a revolution, that is what is universalautomation.org. So let's start from the beginning. What do we see now in the industrial automation market? We see different situations. We see that the way automation has been done until today is great, but still has some drawbacks when it comes to bringing innovation to the market. It's not easy to update the program that you're using. When you have end of life, the same thing, you are struggling to get your hardware upgraded to the next generation. We can speak about software we use today, the lifecycle of the software. So everything that you implement in your automation program is tightly linked to the hardware on which it runs. So you want to reuse it across different platforms? Well, it's most likely that you can do it today. If we speak about... multiple supplier strategies. So for sure, we are out of this COVID phase, but still some of the customers, some of the end users are struggling with getting some products supplied. So sometimes they need to change for one reason or another, change supplier. So they are stuck with one or two suppliers maybe today. Let's think about the future. Future is about the new talents. And we see here that... in the automation field it's becoming more and more difficult to get young talents interested in the field of automation and which is for example not the case for the field of it so how to bring those those youth talents uh uh back to us and back in in automation and and those this is all those points which universal automation.org is tackling uh overcoming the vendor locks and the the ability to to innovate and for that what do you need you need to rethink the way you are doing automation on the market so the way we are doing uh automation on the way we think we should be doing information with universal automation network is first by decoupling the hardware from the software and enable this portability of application so think about it you are developing your automation application and for this automation application you need to implement, let's say, interoperability or interlink with some IT services. And for that, for sure, either you have the knowledge in-house to do it, either you have it maybe in a library given by your supplier, but then it will really depend on the supplier you are taking. But most likely, you won't be able to reuse something which has been done on the market because it really depends on your hardware topology. What if this could work the same way as what you do in the IT field? So meaning that you have your laptop today running with Windows, you want to install a software, you just take the first software that you see and can install, which does exactly what you need to. And you are not looking for which is the supplier of this hardware. Fundamentally, object-oriented, closer to the assets, closer to the representation, the physical representation of what you are trying to deal with. very asset-centric and appealing to the next generation, meaning that with the capability of using the latest programming languages, and which are already used in the IT system. For that, we have the concept of universal automation. Universal automation is basically two things. One thing is an innovative technology. This innovative technology stands with standard, IEC standard, which is called the 64099, which is the evolution of the today mostly used standards on the market for automation. And these standards aims at, let's say, enlarging the previous standard by adding the decoupling of hardware and software, and adding the possibility to program entire system and distribute this programming amongst multiple CPUs, so basically programming power. And for that, we have within universalautomation.org, a reference limitation of that standard. So meaning that we don't work directly on the 64999 standard, but we are working with a reference limitation of it. So you can compare it of the same as what you see in those Linux environment. So today, lots of people are saying, okay, we use Linux. But in fact, people are using a distribution of Linux. So it could be Ubuntu, Debian, Yocto, whatever distribution which is available on the market, which is at the end a reference implementation of And this is exactly the same what we are doing for the 6.499, which is providing a reference implementation to the market so that people can implement it and go and use it in a faster way. But having a reference implementation is not enough. You need more. Having more means that you need a community around it. This community is universalautomation.org. So it's a community of both users of automation and technology vendors. Users of automation, I take the full chain of users. So starting with end users, system integrator, process OEM, machine builders, distributors, down to even youngs in universities, startups, those are included. And technology vendors, those who are putting the product on the market, which embed that reference implementation. So that is what is Universal Automation Network. And the goal... of that is to create an environment similar to what you see in the Android world with smartphones having the possibility to, let's say, play or run different software coming from different providers on different hardware platforms. And this is the same what we will achieve with Unimersive Automation Network. But I think I have spoken enough. and I prefer to let the members speak for us and confirm what is the portability and the little probability of UAO.
Speaker #8
We built our code, we imported it into the system that UAO is based on, and it ran. It just ran, we thought. Try that with any other two vendors.
Speaker #7
It is interoperable. You don't need to do any fine-tuning, any adjustment. It just works together. And it's not just the communication network, it's the whole functionality. So literally a part of the system can be installed over there and the other part can be installed in Australia. And it will work together.
Speaker #1
So you have heard that from our members. They're using it. They say it's working. So it's not something which is like in the air, something that we are inventing or whatever. This is today something which is working and which is used. Let's come back to the standard. Let's say to the base of the technology behind. The 649 standard, it's made with, let's say, three simple things. The first being event-driven function blocks. So. Event-driven, meaning that we work in the same way as what the IT is doing. IT is working more with transaction. And we do the same for automation, embedding the ability to work with events. And so those events are triggering a program, making whatever, so an addition, a function, whatever you need it to do to work in an application. But this function, as you see it, here is a simple, let's say, block. or whatever, but this could be at the end your boiler, this could be your conveyor, this could be a furnace for example in your application. So this block is in fact a representation of your physical asset. It could be a function but it could be as well representing your physical assets. This block has the ability so you can program it inside and take the programming language which which you want to to program the the the function block but it's a self-contained software component so meaning that when you re when you have it when you receive it when you download it from somewhere and you want to reuse it it comes with all the functionality that you need this function block is not developed for a special hardware but it's developed for doing a special application for you and you can then deploy it on your targeted hardware And the way to do that, it's simple. It's using the same principle of the 64099 standard, which is using the application model. So application model is the way you draw your application by coupling together those function blocks and making your application live. So your conveyor with your reader, with your furnace, with your whatever assets you have in your application, knowing that those assets could be assets from, let's say, the process automation world, could be assets from the diskit world, could be assets from the hybrid world. you name it, because this company is this, this, this technology is hardware segment agnostic. And then at some point you need to decide which hardware you want it to run to. And this is what we call the device model. So it's simply selecting which hardware you want to use for your application. And here you see already the major change compared to automation today. Automation today, you start with your hardware topology. So you start. usually in a centralized way with your hardware, with your CPU, your IOs and everything. And from this topology, you do your programming. It's quite good. The only drawback is that if at some point you need to change your programming or add some new functionalities when your CPU is already overloaded, then you need to make some exchange and you need to ensure that both programs which are running in two different CPUs our processing units can communicate together. Here, with the six-part challenge time, you start first with what is your automation situation? What do you want to program? You program it the same way you do it in the IT fields, and then you deploy to the targeted hardware. The phase which is thinking about which hardware I want to use for my application comes later. you first focus on what you want to achieve and then deploy to your hardware. And from that, we go to the third part of the 64099, which is the system model. The system model is the way to assign your application, so your blocks that you have plugged together to draw your application, to some devices. And those devices could be simple as what you see today, could be IPCs, could be Docker container, could be server. So here we go out from the, let's say, PLC-centric way to whatever processing unit able to process my program. And this is what we have and what we use to produce this ecosystem of Prangent Produce software components, which are independent of the hardware. And this is the core of the 649 and the core of what is Universal Automation.org. Because as said, Here, I've just explained the standard. After the standard, there is the reference implementation, which is managed by the association, Universal Automation Network. Managed by the association, which is the community of users and vendors, which I've told you before. Users, vendors, universities, startup, which are organized to maintain and further develop and deploy on the market. this reference implementation of the standard. So what we promote mainly is the portability and reusability of software application and software application across hardware platform. But for sure, we have many other benefits which are coming from the standard itself. And the way it is done for those who really want to deep dive into the technology, the way it is done is that this reference implementation, this, we can call it runtime execution engine, or basically it's a piece of software which runs on your CPU and runs on your operating system. So again, we are not replacing any operating system. We use them. So today, if you're using Linux or whatever operating system on your devices, you can be able to run the runtime onto it. And this runtime is basically receiving the part of the application which is dedicated to it through the build time. through the studio, through the engineering tool, where you design your application. And that is universalautomation.org. And why doing that? Why doing that? Because at the end, the goal is that you go out from this 80% programming for yourself, which is for your application, and 20% maybe reusing, maybe using from using some libraries or reusing from previous projects. Usually, there are still always some changes to be done, but go out from this 80%, 20% to balance that and say, okay, 80% I can reuse because this is already on the market and I don't need to reinvent the wheel every time. I can just reuse what is available for me over there and do the 20%, which is really typical to my application. So reduce that, reduce the complexity, increase... the the safety around your your your programming for example And by that, we're using those libraries, meaning that in the future, with that ecosystem being created, you will see more and more software being developed around segment-specific software. So a company doing great, for example, in water-west water and having a great functionality which wants to be developed to others without having to develop, let's say, the whole hardware architecture around it, but just selling the software. IoT specific. things like digital twin, like AI in your production, for example. Could be mechatronics, your robots had your robots in your application in a simple way, or even reuse and wrap what is already existing. Because you may think at this point that this technology is only for greenfield application, which is not the case. We can as well handle the brownfield application. by wrapping them and by orchestrating them. And we will have an example just after that. So the way you do it, you take your blocks, I said 80% reusing, 20% doing yourself. So you take mostly your blocks from your marketplaces and do the rest yourself. You can make your own programming, so application model. Select your hardware technology, which really comes toward the end. And once you have done that, you can just deploy your application. and then the entire communication between controllers or between, let's say, devices is done automatically and handled by the runtime itself. So really coming to, let's say, more flexibility into the programming, at the same time more efficiency because you can finally reuse what you have done and increase your return on investment on your software. because the software is no longer done for a typical hardware and for a typical life cycle but the life cycle of the software becomes independent from the life cycle of the hardware so again i can tell you a lot about it but i prefer when the when the members speech so let's let's hear it from them because
Speaker #9
in our vision the way we're moving With our company we need a different way of programming and this tool set was actually very promising and it still is kind of enabling that what we want to achieve.
Speaker #10
One of the reasons we're a member of this is we see the OT transformation happening in front of us so I think the IEC 61499 specification in general is a central set of capabilities right to which you can host 1131 or not. as was mentioned and achieve your goals long term with the flexibility you need for all the new stuff that's coming down the pike right whether it's you know some artificial intelligent llm on the scale we all need to learn something more but
Speaker #8
it's not that hard and once you start using it you'll start to realize oh this is way better cell phones better than a wall phone all our technologies we have today are way better this is another one of those
Speaker #1
Universal Automation Network, a community, but who are those companies who decided, those organizations who decided to go with us down the road? So as said, and as a reminder, we started this whole initiative in November 2021, so a bit more than two years ago, with nine founding members. Today, we are close to 80 members from different categories, vendors, users, universities and startups. You can see here an overview of the companies which are going with us the way. But I mean, it's not only about companies, it's also about developing this ecosystem of products which are running with the UAO runtime. And this has already started because we have Today, 11 offers on the market which are using the runtime. So you can see those companies Advantech, ESRAC Industrial, ESA, Flexbridge, Konzberg, Odot, Belden, Stahl, Phoenix Contact and Schneider Electric. So those offers are already available, so it means that you can use them. And talking about using, let's speak about use cases. There are different use cases and I've decided to concentrate on only a few of them, using the companies which are members of the organization. So few companies such as, for example, ExxonMobil working a lot. on the open process automation from implementation and currently working on the first plant running with that, let's say, with a standard, and at the same time using the universal automation network runtime. So you have to see that our technology is a technology enabler for all the standards. So you have heard maybe about MTP. you have heard about. opath you have heard about other standards and you can see that universal automation.org is there to to help and is there to have a complementary approach by enabling those standards another example is the company concept my team so compare my team is doing um orange glass platform and and ships and in that case they are using the technology especially for for brand-feel applications, meaning that when you want to upgrade, when you want to update your ship or your OEM platform, you can simply add a layer with the devices running our technology. And this layer is orchestrating the applications across subsystems. So the subsystems are still running with the, let's say, the format technology which you are using. And if you want to... automate and you want to make those functionality running, let's say altogether, you can add this layer and add new functionalities and make the link as well with IT. This is the way we can still use universalautomation.org with Boundfield application. Another example, if we go into more the sustainability environment is the company called Geatrian. Geatrian is a Swiss company. which is currently doing their plant using the technology. And for them, for sure, they are working the plastic recycling. So they have a patent on a good way to recycle plastic using microwaves. And for them, the best, let's say, their intellectual property lies into the way how to do the process. They don't want to be linked to one supplier. but they want to be able to develop their architecture, to develop their application independently of the hardware on which it lies. And that's why the 64099 and Universal Automation.org was the best way to implement that. So for sure, we drive significant benefits for both users and vendors. The users, for sure, they become hardware independent, so they... break this vendor up, not meaning that they would necessarily go in the future with more multi-vendor strategy, but just saying that by breaking this lock, they have the ability after to really decouple their lifecycle of the software and make their investment into the software more sustainable in the future and not depending on the lifecycle of the hardware. Still, we have we do have some good benefits for the vendors, especially when it comes to working on the platform because here we deliver with the organization the reference documentation. So it means that for the vendors, it's really a copy and paste and we use what is already available. So a good platforming activity. And I want to tell it again, we need the help. of users, we need the help of vendors to grow this ecosystem. So for sure, we bring benefits to users by
Speaker #0
for sure networking activities, influencing by getting to know what is implemented and which features need to be implemented into the mission. So get active, join us, and you can drive the next generation of automation system. The same goes to vendors. If you want to take this part in this activity, that's the best way to do it is by joining universal automation at all because you can gain from the platforming activities which is done here and you do not have to reinvent the wheel yourself but just using the technology and you'll be benefits from the other libraries which are being developed nevertheless i don't forget the universities and the startups because we also target universities for sure we need to train the next generation and we need to ensure that the next generation of of of talents have the necessary knowledge to be able to to be able to go on the market and implement nice things, nice things using Universal Automation.org. So that's why universities are welcome to join us. So before we go to the Q&A, I propose you to listen again to the members to see what they have to say.
Speaker #1
It's really... A different kind of working. You can really use different kind of hardware. You can bring easier new functionality in and I think this is all about sustainability. We see it here in the room and I think to really do something different, faster, more efficient, I think this is really what we all are looking for.
Speaker #2
You will also say, that's marketing, you will promise us a lot. Test it, try it, do a test installation. And I'm very sure you will be very impressed about the functionality. So all in all, a great package.
Speaker #0
Okay, now we are back together. This was the last point. So just I will have a look in to see if there are some maybe some questions in the chat as of now. I see. Okay, I see one question which is about how to join the organization. So join the organization is a very simple process. Here you see all the links which are available, but the most important one is to go to the website. On the website, you have the possibility to send us a message. So please use that, send us a message, and we'll come back to you. Just to make it clear here, the join... joining the association is really made for organization so if you are a company willing to join the the adventure please feel free to do so if you are in university willing to join the university the universal automation network please feel free to join to to do it we can help you we can help you set up some courses on the technology i thank you all and i wish you a good day don't hesitate to get back to us either linkedin youtube we are here so thank you and have a good day bye

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Description

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
The world of automation is undergoing a paradigm shift. This changes everything. Welcome to Universal Automation. The world of plug-in produced software components, making complex things simple and reliable. Think of it as the dawn of an industrial automation app store. The IEC 61499 standard is the key to portability and interoperability. UniversalAutomation.org is the community-managing and industrial-grade reference implementation of 61499 because no one vendor or company or person can bring about transformation on their own. UniversalAutomation allows us to use software and hardware in a whole new way to create portable applications and innovative architectures. For the first time, IT and OT engineers can easily work together, combining real-time with right-time to create cost-effective and innovative ways to address complex use cases, like predictive maintenance, production optimization, and virtual commissioning. But how does universal automation really impact you? Vendors can use the Universal Automation Reference Implementation to bring IEC 61499 offers to market fast. That means new software revenues, new business models, and new customers. Universal Automation frees industrial enterprises to integrate best-of-breed components and proven in-use software. You can realize step-change advancements in efficiency, flexibility, and modularity with agile operational models. It's time for us to release the full potential of the fourth industrial revolution. Be a part of the community delivering the solution. Join UniversalAutomation.org.
Speaker #1
Hi everybody and good day to you. Welcome to this first session of the UAO Goes Live. So what's UAO? Universalautomation.org, this new non-profit association which was created a couple of years ago in 2021. So today my name is Greg Boucaud and I'm the Chief Marketing Officer for this organization. So please bear with me as we go through the slide presentation of what is Universal Automation Network, so I can give you a bit more of insights. Then, instead, to come with your questions, as we'll have a Q&A session at the end, and I'll be happy to answer them. So, before we go to the next slide, I would like to hear it from the members.
Speaker #2
Universal Automation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We call it a game changer in automation because we have first one technology which is based on the IEC 6499 which is the standard which aims at decoupling hardware and software.
Speaker #2
Hardware itself is becoming very very performant in terms of processing CPU power.
Speaker #3
And the future is more and more about software. This approach is really a winning approach because it's very, very flexible. You develop the application once and you can reuse in each different configuration.
Speaker #4
That's exactly what Universal Automation and 61499 enables because it brings a new formalism for developing software which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that is the marriage made in heaven.
Speaker #5
So if I want to make more conscious decisions based on my business data which also comes from the automation level, I need Universal Automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #2
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy. and from other companies.
Speaker #6
Advantech is growing really, really fast and I believe if you want to keep on growing in the next future you need to be able to innovate. When I see Universal Automation approach it is exactly the way of innovation we need to go with.
Speaker #7
Most of our customers from Process Automation are pretty conservative to never change a running system but now we see a new generation coming up. what is used to new technologies and they are open to test to try these new functionalities and I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years and I think over the years this is the most exciting changes.
Speaker #3
And from my experience I see that in the IT for example there has been a big revolution and I expect the same in automation. I don't know when it will happen. Probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Welcome back. On the verge of a revolution, that is what is universalautomation.org. So let's start from the beginning. What do we see now in the industrial automation market? We see different situations. We see that the way automation has been done until today is great, but still has some drawbacks when it comes to bringing innovation to the market. It's not easy to update the program that you're using. When you have end of life, the same thing, you are struggling to get your hardware upgraded to the next generation. We can speak about software we use today, the lifecycle of the software. So everything that you implement in your automation program is tightly linked to the hardware on which it runs. So you want to reuse it across different platforms? Well, it's most likely that you can do it today. If we speak about... multiple supplier strategies. So for sure, we are out of this COVID phase, but still some of the customers, some of the end users are struggling with getting some products supplied. So sometimes they need to change for one reason or another, change supplier. So they are stuck with one or two suppliers maybe today. Let's think about the future. Future is about the new talents. And we see here that... in the automation field it's becoming more and more difficult to get young talents interested in the field of automation and which is for example not the case for the field of it so how to bring those those youth talents uh uh back to us and back in in automation and and those this is all those points which universal automation.org is tackling uh overcoming the vendor locks and the the ability to to innovate and for that what do you need you need to rethink the way you are doing automation on the market so the way we are doing uh automation on the way we think we should be doing information with universal automation network is first by decoupling the hardware from the software and enable this portability of application so think about it you are developing your automation application and for this automation application you need to implement, let's say, interoperability or interlink with some IT services. And for that, for sure, either you have the knowledge in-house to do it, either you have it maybe in a library given by your supplier, but then it will really depend on the supplier you are taking. But most likely, you won't be able to reuse something which has been done on the market because it really depends on your hardware topology. What if this could work the same way as what you do in the IT field? So meaning that you have your laptop today running with Windows, you want to install a software, you just take the first software that you see and can install, which does exactly what you need to. And you are not looking for which is the supplier of this hardware. Fundamentally, object-oriented, closer to the assets, closer to the representation, the physical representation of what you are trying to deal with. very asset-centric and appealing to the next generation, meaning that with the capability of using the latest programming languages, and which are already used in the IT system. For that, we have the concept of universal automation. Universal automation is basically two things. One thing is an innovative technology. This innovative technology stands with standard, IEC standard, which is called the 64099, which is the evolution of the today mostly used standards on the market for automation. And these standards aims at, let's say, enlarging the previous standard by adding the decoupling of hardware and software, and adding the possibility to program entire system and distribute this programming amongst multiple CPUs, so basically programming power. And for that, we have within universalautomation.org, a reference limitation of that standard. So meaning that we don't work directly on the 64999 standard, but we are working with a reference limitation of it. So you can compare it of the same as what you see in those Linux environment. So today, lots of people are saying, okay, we use Linux. But in fact, people are using a distribution of Linux. So it could be Ubuntu, Debian, Yocto, whatever distribution which is available on the market, which is at the end a reference implementation of And this is exactly the same what we are doing for the 6.499, which is providing a reference implementation to the market so that people can implement it and go and use it in a faster way. But having a reference implementation is not enough. You need more. Having more means that you need a community around it. This community is universalautomation.org. So it's a community of both users of automation and technology vendors. Users of automation, I take the full chain of users. So starting with end users, system integrator, process OEM, machine builders, distributors, down to even youngs in universities, startups, those are included. And technology vendors, those who are putting the product on the market, which embed that reference implementation. So that is what is Universal Automation Network. And the goal... of that is to create an environment similar to what you see in the Android world with smartphones having the possibility to, let's say, play or run different software coming from different providers on different hardware platforms. And this is the same what we will achieve with Unimersive Automation Network. But I think I have spoken enough. and I prefer to let the members speak for us and confirm what is the portability and the little probability of UAO.
Speaker #8
We built our code, we imported it into the system that UAO is based on, and it ran. It just ran, we thought. Try that with any other two vendors.
Speaker #7
It is interoperable. You don't need to do any fine-tuning, any adjustment. It just works together. And it's not just the communication network, it's the whole functionality. So literally a part of the system can be installed over there and the other part can be installed in Australia. And it will work together.
Speaker #1
So you have heard that from our members. They're using it. They say it's working. So it's not something which is like in the air, something that we are inventing or whatever. This is today something which is working and which is used. Let's come back to the standard. Let's say to the base of the technology behind. The 649 standard, it's made with, let's say, three simple things. The first being event-driven function blocks. So. Event-driven, meaning that we work in the same way as what the IT is doing. IT is working more with transaction. And we do the same for automation, embedding the ability to work with events. And so those events are triggering a program, making whatever, so an addition, a function, whatever you need it to do to work in an application. But this function, as you see it, here is a simple, let's say, block. or whatever, but this could be at the end your boiler, this could be your conveyor, this could be a furnace for example in your application. So this block is in fact a representation of your physical asset. It could be a function but it could be as well representing your physical assets. This block has the ability so you can program it inside and take the programming language which which you want to to program the the the function block but it's a self-contained software component so meaning that when you re when you have it when you receive it when you download it from somewhere and you want to reuse it it comes with all the functionality that you need this function block is not developed for a special hardware but it's developed for doing a special application for you and you can then deploy it on your targeted hardware And the way to do that, it's simple. It's using the same principle of the 64099 standard, which is using the application model. So application model is the way you draw your application by coupling together those function blocks and making your application live. So your conveyor with your reader, with your furnace, with your whatever assets you have in your application, knowing that those assets could be assets from, let's say, the process automation world, could be assets from the diskit world, could be assets from the hybrid world. you name it, because this company is this, this, this technology is hardware segment agnostic. And then at some point you need to decide which hardware you want it to run to. And this is what we call the device model. So it's simply selecting which hardware you want to use for your application. And here you see already the major change compared to automation today. Automation today, you start with your hardware topology. So you start. usually in a centralized way with your hardware, with your CPU, your IOs and everything. And from this topology, you do your programming. It's quite good. The only drawback is that if at some point you need to change your programming or add some new functionalities when your CPU is already overloaded, then you need to make some exchange and you need to ensure that both programs which are running in two different CPUs our processing units can communicate together. Here, with the six-part challenge time, you start first with what is your automation situation? What do you want to program? You program it the same way you do it in the IT fields, and then you deploy to the targeted hardware. The phase which is thinking about which hardware I want to use for my application comes later. you first focus on what you want to achieve and then deploy to your hardware. And from that, we go to the third part of the 64099, which is the system model. The system model is the way to assign your application, so your blocks that you have plugged together to draw your application, to some devices. And those devices could be simple as what you see today, could be IPCs, could be Docker container, could be server. So here we go out from the, let's say, PLC-centric way to whatever processing unit able to process my program. And this is what we have and what we use to produce this ecosystem of Prangent Produce software components, which are independent of the hardware. And this is the core of the 649 and the core of what is Universal Automation.org. Because as said, Here, I've just explained the standard. After the standard, there is the reference implementation, which is managed by the association, Universal Automation Network. Managed by the association, which is the community of users and vendors, which I've told you before. Users, vendors, universities, startup, which are organized to maintain and further develop and deploy on the market. this reference implementation of the standard. So what we promote mainly is the portability and reusability of software application and software application across hardware platform. But for sure, we have many other benefits which are coming from the standard itself. And the way it is done for those who really want to deep dive into the technology, the way it is done is that this reference implementation, this, we can call it runtime execution engine, or basically it's a piece of software which runs on your CPU and runs on your operating system. So again, we are not replacing any operating system. We use them. So today, if you're using Linux or whatever operating system on your devices, you can be able to run the runtime onto it. And this runtime is basically receiving the part of the application which is dedicated to it through the build time. through the studio, through the engineering tool, where you design your application. And that is universalautomation.org. And why doing that? Why doing that? Because at the end, the goal is that you go out from this 80% programming for yourself, which is for your application, and 20% maybe reusing, maybe using from using some libraries or reusing from previous projects. Usually, there are still always some changes to be done, but go out from this 80%, 20% to balance that and say, okay, 80% I can reuse because this is already on the market and I don't need to reinvent the wheel every time. I can just reuse what is available for me over there and do the 20%, which is really typical to my application. So reduce that, reduce the complexity, increase... the the safety around your your your programming for example And by that, we're using those libraries, meaning that in the future, with that ecosystem being created, you will see more and more software being developed around segment-specific software. So a company doing great, for example, in water-west water and having a great functionality which wants to be developed to others without having to develop, let's say, the whole hardware architecture around it, but just selling the software. IoT specific. things like digital twin, like AI in your production, for example. Could be mechatronics, your robots had your robots in your application in a simple way, or even reuse and wrap what is already existing. Because you may think at this point that this technology is only for greenfield application, which is not the case. We can as well handle the brownfield application. by wrapping them and by orchestrating them. And we will have an example just after that. So the way you do it, you take your blocks, I said 80% reusing, 20% doing yourself. So you take mostly your blocks from your marketplaces and do the rest yourself. You can make your own programming, so application model. Select your hardware technology, which really comes toward the end. And once you have done that, you can just deploy your application. and then the entire communication between controllers or between, let's say, devices is done automatically and handled by the runtime itself. So really coming to, let's say, more flexibility into the programming, at the same time more efficiency because you can finally reuse what you have done and increase your return on investment on your software. because the software is no longer done for a typical hardware and for a typical life cycle but the life cycle of the software becomes independent from the life cycle of the hardware so again i can tell you a lot about it but i prefer when the when the members speech so let's let's hear it from them because
Speaker #9
in our vision the way we're moving With our company we need a different way of programming and this tool set was actually very promising and it still is kind of enabling that what we want to achieve.
Speaker #10
One of the reasons we're a member of this is we see the OT transformation happening in front of us so I think the IEC 61499 specification in general is a central set of capabilities right to which you can host 1131 or not. as was mentioned and achieve your goals long term with the flexibility you need for all the new stuff that's coming down the pike right whether it's you know some artificial intelligent llm on the scale we all need to learn something more but
Speaker #8
it's not that hard and once you start using it you'll start to realize oh this is way better cell phones better than a wall phone all our technologies we have today are way better this is another one of those
Speaker #1
Universal Automation Network, a community, but who are those companies who decided, those organizations who decided to go with us down the road? So as said, and as a reminder, we started this whole initiative in November 2021, so a bit more than two years ago, with nine founding members. Today, we are close to 80 members from different categories, vendors, users, universities and startups. You can see here an overview of the companies which are going with us the way. But I mean, it's not only about companies, it's also about developing this ecosystem of products which are running with the UAO runtime. And this has already started because we have Today, 11 offers on the market which are using the runtime. So you can see those companies Advantech, ESRAC Industrial, ESA, Flexbridge, Konzberg, Odot, Belden, Stahl, Phoenix Contact and Schneider Electric. So those offers are already available, so it means that you can use them. And talking about using, let's speak about use cases. There are different use cases and I've decided to concentrate on only a few of them, using the companies which are members of the organization. So few companies such as, for example, ExxonMobil working a lot. on the open process automation from implementation and currently working on the first plant running with that, let's say, with a standard, and at the same time using the universal automation network runtime. So you have to see that our technology is a technology enabler for all the standards. So you have heard maybe about MTP. you have heard about. opath you have heard about other standards and you can see that universal automation.org is there to to help and is there to have a complementary approach by enabling those standards another example is the company concept my team so compare my team is doing um orange glass platform and and ships and in that case they are using the technology especially for for brand-feel applications, meaning that when you want to upgrade, when you want to update your ship or your OEM platform, you can simply add a layer with the devices running our technology. And this layer is orchestrating the applications across subsystems. So the subsystems are still running with the, let's say, the format technology which you are using. And if you want to... automate and you want to make those functionality running, let's say altogether, you can add this layer and add new functionalities and make the link as well with IT. This is the way we can still use universalautomation.org with Boundfield application. Another example, if we go into more the sustainability environment is the company called Geatrian. Geatrian is a Swiss company. which is currently doing their plant using the technology. And for them, for sure, they are working the plastic recycling. So they have a patent on a good way to recycle plastic using microwaves. And for them, the best, let's say, their intellectual property lies into the way how to do the process. They don't want to be linked to one supplier. but they want to be able to develop their architecture, to develop their application independently of the hardware on which it lies. And that's why the 64099 and Universal Automation.org was the best way to implement that. So for sure, we drive significant benefits for both users and vendors. The users, for sure, they become hardware independent, so they... break this vendor up, not meaning that they would necessarily go in the future with more multi-vendor strategy, but just saying that by breaking this lock, they have the ability after to really decouple their lifecycle of the software and make their investment into the software more sustainable in the future and not depending on the lifecycle of the hardware. Still, we have we do have some good benefits for the vendors, especially when it comes to working on the platform because here we deliver with the organization the reference documentation. So it means that for the vendors, it's really a copy and paste and we use what is already available. So a good platforming activity. And I want to tell it again, we need the help. of users, we need the help of vendors to grow this ecosystem. So for sure, we bring benefits to users by
Speaker #0
for sure networking activities, influencing by getting to know what is implemented and which features need to be implemented into the mission. So get active, join us, and you can drive the next generation of automation system. The same goes to vendors. If you want to take this part in this activity, that's the best way to do it is by joining universal automation at all because you can gain from the platforming activities which is done here and you do not have to reinvent the wheel yourself but just using the technology and you'll be benefits from the other libraries which are being developed nevertheless i don't forget the universities and the startups because we also target universities for sure we need to train the next generation and we need to ensure that the next generation of of of talents have the necessary knowledge to be able to to be able to go on the market and implement nice things, nice things using Universal Automation.org. So that's why universities are welcome to join us. So before we go to the Q&A, I propose you to listen again to the members to see what they have to say.
Speaker #1
It's really... A different kind of working. You can really use different kind of hardware. You can bring easier new functionality in and I think this is all about sustainability. We see it here in the room and I think to really do something different, faster, more efficient, I think this is really what we all are looking for.
Speaker #2
You will also say, that's marketing, you will promise us a lot. Test it, try it, do a test installation. And I'm very sure you will be very impressed about the functionality. So all in all, a great package.
Speaker #0
Okay, now we are back together. This was the last point. So just I will have a look in to see if there are some maybe some questions in the chat as of now. I see. Okay, I see one question which is about how to join the organization. So join the organization is a very simple process. Here you see all the links which are available, but the most important one is to go to the website. On the website, you have the possibility to send us a message. So please use that, send us a message, and we'll come back to you. Just to make it clear here, the join... joining the association is really made for organization so if you are a company willing to join the the adventure please feel free to do so if you are in university willing to join the university the universal automation network please feel free to join to to do it we can help you we can help you set up some courses on the technology i thank you all and i wish you a good day don't hesitate to get back to us either linkedin youtube we are here so thank you and have a good day bye

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Embed