Presentation: AVEVA System Platform: Deep dive into latest enhancements

2024 - AVEVA World - Paris - HMI/SCADA

AVEVA System Platform: Deep dive into latest enhancements

Alright. My name is Harren Svermick. I'm gonna start this off. I think I know we're a couple of seconds early, but I don't think we're gonna get a lot more people in here. And I do have a bunch of things that I wanna go through. The marketing folks asked me to leave a little bit of time for Q and A at the end, and I didn't really plan for that. So I may have to go a little bit faster than normal and then see if I can get, you know, one or two questions in there. Again, not from the Aviva folks on the side, please. Alright. So I just quickly have a look at the timeline as we have it right now, and I think most of you kind of know where we came from. System platform, again, twenty twenty three, was released somewhere in the middle of twenty twenty, around August that year. And at that point in time, we also had a release called system platform enterprise. And the big goal of that system platform enterprise is to in to allow for the building of the UOC type in, implementations that we see. And the only way to get that was actually through the of your operations control enterprise. Now those license that license doesn't exist anymore today. Today, UOC is the correct licensing to go for. And the reason why we did it on the system platform enterprise version is we needed a a web client that could work in enterprise environment. Now, a lot of the, the use cases that people look at that, oh, my web client was more HMI SCADA side, so we had to go and build a an HMI SCADA version of that, which is what we did in twenty twenty three r two. But just to talk a little bit about that enterprise web client, that client there, and and let's delve into it a little bit deeper. Oh, by the way, you would have seen us releasing patches over the last couple of, quarters. The first patches took a little bit of time to get out to just to explain where that comes from, and if you were in the road map session, I'm sorry that I'm repeating that to you now. We have the idea of getting rid of hotfixes. We wanna go to full patch releases. We wanna get to a patch cadence of monthly. No more hotfixes so that every user can just grab the latest patch. There's no risk to it. There's no new features. Nothing. It's just a roll up of the fixes. And you don't have to work with, tech support and go back and forth and find out there's a hotfix and do a hotfix request, etcetera. The patch should just be there for you to use. Took us a little bit of time to get the first one out. The second one, we started getting into this cadence, and we're right now running about quarterly cadence. You would have seen us stopping, for the enterprise version because right about that time when patch three came out, we, deprecated the the system platform enterprise release. Not a lot of customers were using it. I know a lot of customers were aware of it simply because it had that web client in there. So we then decided to put out the system our own brand of the web client that is more SCADA HMI based. So it's it's more of a web client that is really a SCADA or an HMI running directly inside a browser. Okay. So let's talk about that a little bit, and see where it comes from. If you wanna run an o miner browser, right, we'd have to look at where the data comes from. Right? And I think everyone knows kind of where this picture goes. You know, we have real world feeding data into system platform. System platform feeds it up into OMI. And there's, of course, some third party systems that you can run-in there. You can send that data into system platform, meaning you've got to build your own graphics. But what OMI really did really well is it's able to visualize, or use visualization already exists. So if you have a spreadsheet that you wanted to show, you can just take a spreadsheet and run it directly in context directly inside OMI. And there's a couple of these apps. Right? There's, like, map apps and video apps and picture apps and document viewers and all kinds of apps. So OMI does that really good. How do we build an OMI application? Well, we build a view app framework that gives us our navigation that's telling us how to, you know, do auto filling and all of those kind of things. And then inside of that, we have some content that we're showing. Content basically being industrial graphics, used to be known as orchestral graphics. Right? That's our visualization or main visualization. And, of course, these OMI apps that I just spoke of, this would be applications like the map app or being able to run a spreadsheet view or a JPEG view or whatever it is that you're running directly in there. And we also introduced a bit ago, we've introduced OMI, web widgets that allows you to run because our OMI apps are dot net based. These web widgets are JavaScript and HTML, based. So and they allowed us to get more web friendly widgets in there. So when we build our initial in enterprise, we needed to find a way of running all of these things in a browser. Now, obviously, immediately, I have a problem because dot net doesn't run dot net one forms dot net WPF doesn't run-in a browser. So we had to go and create some additional, web widgets. So if you ever looked inside the installation of the enterprise version, you would have seen a whole lot of duplicated web widgets, duplications of the OMI apps in there that allowed us to run those apps inside the browser version of the enterprise version. Visualization, basically two parts. There is my, kind of, my, business logic that figures out, you know, what the fill is, what the color is, what all of those things are. And then there's the drawing part that actually just draws the picture. After I've done all the logics and scripting and everything, I just draw the picture on the screen. And it turns out if I'm running in a browser client or inside a web client, all I needed to do is create that web view framework or that web app framework that sit there with the with the navigation and the layouts. And then web, we just just run there because they JavaScript and HTML five, so they just run it directly in the browser. And it's very easy to draw already in the browser. We use SkiaSharp to do that, and we get some really fast reactions on it. This is a a lot more scalable than running in touch access anywhere, for instance, where you have a remote desktop session per person. But in this case, you still have to have a process per person a process per session. Right? So that's why the enterprise version was kind of gets to a point where it's not suitable for SCADA HMI solutions. So this is what we released for enterprise. We specifically called it enterprise because it's supposed to live on the IT side of your firewalls, not on the OT side. But we had a lot of customers asking for it, so what we had to do is move that visualization logic, that dot net scripting and all of those things running in the background, move it all into the browser. We found all of the best, most neatest technologies that Microsoft has, and we used it to, move the visualization logic, move that entire dot net logic into the browser as well. And we did the same for our OhMyApps. The OhMyApps back ends are all dot net. We just put a new front end on it, and the technology we're using there is called Blazor. So we put Blazor on top of our dot net back ends and we move those apps into the browser as well. Right. So that's the release of Oh My web client that you get in twenty twenty three r two. Okay. There's a couple of things to take note of here and this is just based deep deep diving into the technology a bit. We know we're using dot net. Right? We're using Blazor on the on dot net. We've we're using, WebAssembly, so that means that our dot net, applications are compiled to run directly in the browser. Right? It's it's running on WebAssembly in the browser. Make it really fast. And, we're using Skia to draw to draw our industrial graphics inside the browser. Why did we do it this way? It gives us black it removes all dependency on the platform. Right? It's platform agnostic. I am not bound to Windows. I can run-in Linux. I can run-in Android. I can run-in iOS. I can run-in different places because I'm no longer bound to my to to the Windows environment. And give us a single code base, and this has been probably mentioned a number of times in different sessions. We are moving all of our visualization into this technology, which we call VisualizationCore, internally, but that technology is going to be used by all of our products. We're all adopting it. I'm gonna move it into the desktop environment of OMA as well, which which means that we have to, you know, make sure that there are no parity gaps between that and the desktop version. But what it gives us is it gives us a single code base. So if I want to add a feature in the future, I only have to add it once. Right now, if I wanna add new feature, I have to add it for InTouch. I have to add it for OnMyDesktop, OnMyWebClient, InTouchWebClient, Insight. If I wanna add a new feature, I have to do it five times. Once we get to the single code base, I only have to do it once. So that helps me, but we also did it in a way that it helps you because we want you to leverage your existing, efforts and your existing investment as well. In other words, if you build a Vue app that runs on the desktop version of OMI, you can take that same Vue app, deploy it on the web view engine, and run it right there. Now there's gonna be some gaps right now. We've got a lot of them sorted out. So I would guess that most applications that we have today, if you only use industrial graphics, you're gonna get there probably to the ninety percent. If you use some homegrown application objects and some home homegrown Ohmai apps and things like that, there's gonna be a little bit of a gap that you need to close yourself. But we're gonna make it as as as tight as possible so that everything that you can do in the Ohmai desktop, you can do in the web client. Right. So it's the same view app as you use in the desktop client, and it's really, really fast. Microsoft is investing quite a bit in some of the technologies that we're running here. In some of our testing, we we we seem to be drawing faster in the in the web client than we do on the on the desktop client, which was a bit of a surprise. So we'll continue exploring that and make sure that we can give you the fastest possible solution that we can. And, of course, no additional installation is required. If you wanna point your browser, whatever machine you have, point your browser. As long as you're on the right network and you have the right credentials, you can go to your HMI. Okay. So this is how it looks. This is what it looks like. This is inside the IDE. I have my applications here. I've got a couple of view apps sitting on the side. I'm gonna take my nuclear plan. I'm going to deploy it on my WebView engine, so it's the same Vue app. I'm just putting it there. And once I've done that, I can just click on the URL and it will open up my, WebView browser sorry, my WebView server, and I can go and select my application. In this case, I've selected my nuclear plant there, and it will do all the kind of things that you expect from OMI to be able to do. You can resize things and you can, of course, operate things and drag sliders around and all those kind of things. It will do zooming. It will do panning and all of those kind of things that you need there. All of your animations and stuff should work pretty good. It also has the navigation tree on the side. You have your breadcrumb at the top. All of those things will work, as well as, of course, there's an alarm app and there's a trend app in there. Things that we are busy ex expanding and making better than they are right now, but most of the things that you have in your current applications will just translate directly into the web browser. Okay. So what that means also is it's platform agnostic. So just for fun, I added this into Ubuntu Linux. So this is Linux running over here, and I opened up a couple of, you know, opened it up in Firefox to see what it will do. And you can see it supports Firefox. And it's the same kind of experience that you have on there. It will open in Chromium browsers in Firefox. It will open up on iOS. It will open up on phones. Had a very unfortunate experience because I wanted to show it on my phone to you, but apparently our security is really good. And I left I left the US more than two weeks ago about. And, on the hotel room networks, when my oh, my I saw the hotel room networks. It didn't allow me to say to do any control on my OT network. It just said, nope. You're on a public network. You cannot do this. So, on my private network back home, I could get it running, but, unfortunately, I couldn't build you the the example here for my phone. But look out for YouTube. I will build you some videos on YouTube on how to do it, and you'll see the differences there. Of course, this is just showing that it also runs in Chromium, and I then had a little bit of fun of putting these two things side by side to try and see if they if one is faster or a better experience than the other one. And I I really couldn't see it. I think it's pretty much the same code executing there because it's just WebAssembly that runs both of them. So they are side by side, have the same kind of experience that you would have. Alright. Much fun. That's the web client. So there was a lot of talk about that in the road map session as well. If you missed the road map session, please have a look at the presentations. They will be available afterwards. In there, you'll see that we also now with the new releases coming up, we'll support progressive web apps, which means you can run this without a browser. Pretty cool. So if you missed that session, please have a look at that presentation afterwards. Let's talk about embed content. Moving on to the more mundane stuff in system platform right now. You all know if you're gonna design something in system platform, you need to kind of know what's gonna be on the graphic. Right? If I'm building a field of cows, I need to know exactly how many cows I have there. In design time, I put my four cows on there, and it's all good. But what if those cows are not known? If I if they stored somewhere else, they're not part of my model. They're sitting in a database of SQL or Oracle somewhere or I've got a REST APIs to my cows or, maybe they're sitting in a CSV file. And I only know at run time how many cows I have or where they are. So for that, we added the embed content function that allows you to go and view the well, pull whatever data you need from wherever, and in run time, place them on at the correct x y location. So it doesn't matter what they are. You you can just dynamically find out and put them where you need them on the screen. Bunch of use cases you can think about this. Initially, we kind of played around with it, but we've got people building dynamic face plates and things like that just directly from the PLC. It's pretty cool. So the way we, I explained it here is I've got some people. Actually, it's just interesting. This is a SVG that I pulled out from just from the web. It was pretty cool. I just put because I don't know if you're aware of that. In the previous version, we allowed you to just drag an SVG onto the screen. It will create all the elements, so it will create a shirt and the shoes and everything available for you, and you can go and animate them directly. If you have someone building stuff for you in SVG, nice cool tool. And assign some custom properties to that. And, of course, you can in design time go and drag these things onto the screen if you know where they are. Orient them, give them custom properties, but we wanna do it in run time. So in run time, I'm taking that that graphic. I'm setting some of its custom properties, changing the color of this of the shirt and the likes, and I'm rotating it. And then I select an x and y position, and I say add it and it adds it to the screen. And, actually, what I did here is I made it so that if I switch on that random and I click anywhere on the screen, it will just randomly put a human being at that x y location, which is also now readable from your mouse. So you can easily just stick a couple of pictures on there. Actually, that ad multiple just added ten random people, and it did that in basically milliseconds, so it's fairly reactive, except if you have really big graphics, you can keep that in mind. You can also do things like deleting them and, you know, if you select something you can go and change the custom properties, hit the modification button, and it would modify it in place. I actually made it so that if you select something and then modify it and just right click somewhere, it will just move that that human around in the this is the White House, by the way, so I'm putting humans in the White House. It was just for fun. The the important part is these graphics participate as if they were embedded in design time. They can pan. They can zoom. They can do all of those things that you would normally do. It's as if you built this with the graphics in there right from the beginning. So it's not little hover over dialogue boxes and stuff sitting here. It's part of the graphic. Very nice little feature. If you build nice stuff for that, send it to me. I'd like to see what you did, even if it's just a screenshot. Alright. Let's move on. Alarm latching is something we did for some of our customers, that were asking about different ways of handling alarming or an additional method. Quickly, before this release, we had four modes of alarms. You had normal. Nothing's going on. Goes into alarm. I can go out of alarm in two ways. I can acknowledge it and then wait for it to return back to normal, or it could go back to return to normal, and then I acknowledge it. Right? Those are the the four states I have there. And, of course, I can if if it goes back into alarm, then I go back into the alarming state, on there. So what we've added is optional, but if you're interested in that, you can optionally add the latch state, which means it does not go back to normal state when it's acknowledged and returned. It actually goes into the latch state, and you can hit the dismiss button. It will go off the screen. It just gives you that extra you know, the alarm is fully handled. It's been seen. It's acknowledged. It's returned. You can now take it off the screen if anyone wants to use that. We made some changes to the IDE, to the UI and UX. Don't swear at me when you see them. But, there's some of them that are really cool, and we're gonna make them better. I know that there are some things that have really moved everyone's cheese around a little bit, but it is we are trying to make it better, and we were kind of forced to do certain things because of changes in life cycles and the likes. So we will try to make improve it. Things that I really like that's new in there is the ability to go and search for something, so you can just start typing something in there. It searches for it. It shows you in the tree where it is. You can actually also go and make it a flat list, so it will just give you a flat list of all the things that it found. Our status indicators are sitting on the side now with little tooltips. If you hover over it, it will tell you if it's in warning, if it's opened up. And if you go and, check something and you make a change to something and check it in, it'll tell you, that it's edited and you need to go and, deploy it on there. And then there's a little, icon guide that will show you what all these icons mean. We're not done here. We need to add filtering and things like that in there, and we are gonna make it better. I know there's some things here that are really bugging some people and we are trying to make it better for you. One other thing that I wanted to show you, and I wasn't sure if anyone knows this, and I'm on purpose used a slightly smaller resolution here. It's I think it's thirteen sixty six by seven sixty eight, so it's a little cramped. But I I don't know if everyone's aware here, so I wanted to show it because, I found that a lot of people would didn't know that we made this change. You can drag things around. You could always do this kind of, but it wasn't really a good experience. But now we've added these little, tie in points so you know exactly where you're dragging a a panel in there. And, all fun and games. If I put all my panes once next to each other, I can start drilling into them. By the way, I don't know if you know this, but if you press control shift zed, it will synchronize those panes. The problem being if I open it up, I am running out of space. Right? It's difficult to do. But luckily, you can just drag that attribute editor, put in another screen, run it in the full screen or that time. I don't know if you were aware of that. And you can just start working on that. And, of course, if you have my screens, you can add your graphic editor and your SMC and your, all of your editors can run side by side on that. But the important part is if you add more of these attributes, you can drag them onto that other screen. You can run them in the same tab group, so it will create a tab group, or you can drag them onto the side and you can have two different tab groups or whatever you want. Really makes it a lot easier to work with your attribute editor if you can drag it around. Okay. So I wanted to show that to you. Okay. Internationalized string support. You all may be familiar with the fact that we have an attribute type internationalized string. And that internationalized string is now translatable. So in the IDE, if you go and export it for an object, you get the option to export internationalized strings like you would be able to export alarms, and that gives you a list of all the internationalized strings and their values in a CSV format, which you can then go and open up in in this case, I'm opening it up in Excel. And I'm I am cheating a little bit here because I'm using the translate in Excel because I didn't wanna type them out in front of you. Just copying all the translations in there. Gave me a quick Afrikaans version of this, and, then you can just go back and import it. Now if you look at the application, this is all internationalized strings. So for instance, the Boolean on off message for auto manual stop and start, those are internationalized strings. The descriptions for objects, the descriptions for attributes, engineering units, they are all internationalized strings, and those are also the things that we use when we push down into the alarm system and into the trend system. We also have internationalized strings as the alias for that's used in our navigation. So if I go out and I change this over to Afrikaans now, everything on the screen will change over to Afrikaans. Every internationalized string that's in there, by the way, I also did the alarm so the entire screen will turn over to to show you the Afrikaans version of the software. And you can see if you, you know, if you swap around these things, they they the Boolean on off messages and all of those things are translated properly. If you use one of the big six that we have full translation for, it will even translate things like the so if I use German, for instance, you'll see the column names and the actual UI of the train controls and the alarms will also be translated. That happens with the metric. You don't have to export, import anything for that. Alright. That was string translation, global buffering. I hope everyone here is aware that we can add on buffering for your IO. So if you enable IO today, there's a there's a little checkbox that you can enable and say make it buffered, which means if the data is coming in faster than I can show it on the screen, I still want to have that in a in a in an array. Keep it between an array. Store it all in the historian at the back end so that means I can get data faster than I would normally do. I can do that for multiple attributes. I can but it is a little bit of a pain if you have to do it for every attribute. So in the last version, we added one checkbox under the communication, advanced communication, enable that, buffering goes on automatically for all IO that you have in the system. If your IO speed is more or less the same as your engine speeds, you will see zero performance difference between them. We see no performance impact at all with the added advantage that if they don't if they don't intersect, if there is a missed attribute, it will grab that one and also send it to the store, and so you won't miss any IO. And you can actually get to them if you want to in the in the array. Alright. That was auto buffering. Then there's the AVEVA operations control experience. I'm I'm gonna quickly talk about why we wanna do that. I think a lot of people have already talked about that. But the main case here is we wanna do something similar to what some what Microsoft has done. In other words, they have a bunch of on prem software. Right? And they have a hybrid cloud platform, which means that they also have a bunch of cloud software. And some of these things are really useful in on prem. In other words, like a PowerPoint or an Excel or whatever is something that you run on your machine. Right? It's not something that you run-in the in in the cloud always, but you wanna be able to share and do things in the cloud. So what they've done is they've they've given a bunch of Office three sixty five. It used to be called now Microsoft three sixty five packages that allows you to connect to Azure AD, and all of their on prem products now also connect to Azure AD, AD, which is pretty cool. That means that suddenly your Excel works inside Teams, and you can share stuff in SharePoint, and you can have Outlook and SharePoint and and OneDrive, and all of these things work together because you're all the same user. Right? It understands exactly who you are. We have the same kind of thing that we wanna do in our products, bunch of on premises products that we have. Right? InTouch and OMI and all of those kind of things. We also have our cloud products. We have Teamwork and Insight and all of those kind of things. And what we're doing is we had it connect to it. Right? So now you have a single user in there and everything is connected. So everyone using on premises software as well as the cloud software has the same user and has access to the same things. And the idea here is not just to make it single sign on, although that is the first use case, but it's also to start adding value to it so that if you build a graphic in InTouch and you store it under your name in the cloud and you go into OMI and you open it up there, it's the same graphic. It's the same folder. You you can just keep on working with that because it's the same kind of experience that we have with Microsoft. Alright. And then, of course, there's the three packages there, Edge Supervisor and UOC. One last point to drive home on that is, in the traditional software models, typically, you would have a license for one box over there, but that user, if you wanted to use his phone or a tablet or a browser or anything else, would need separate licenses. He couldn't get any access to any of those things. In the operations control model, we have all of those devices licensed just by the username. So this single user gets access to all of those devices, and, by the way, has a he has a consistent experience over that, meaning that if he looks at these graphics on one device or on another device or on another product, it's the same graphics that he's looking at. So that's kind of where we're going after the ops connected, stuff. And, of course, the just last one point is, you know, someone this is what they call the day in life. This is a person. What is he doing during the day? It's just one person on one day, has a bunch of tasks. You know, they have all these things that they need to do, and they perform all these things during the day, and they perform all of these things on different devices. Right? Right? And then if you think in the past, how would you license all of that, you would have to go and figure out what this use case it the the product is, what this use case product is. Then you would have to go and have a license for each one of those devices. In the ops control model, you license the user, and he does everything on any device that he wants to be. Very easy. So I really would advise you to look at ops control as a as a as a very good alternative for licensing and getting your hands on our software. Alright. Quickly showing you what that looks like. I'm just gonna show you the system platform pod. This is guy logging for the first time in the IDE, logs in with his username and password, gets challenged by the Aviva Connect by the Connect ID, signs into it, and once he's done that, everything knows who he is. He's now in single sign on mode. If he opens up his licensing, it knows what his entitlements are. If he actually connects to a Galaxy, it automatically unauthenticate him against the roles of that Galaxy, make that available. If he looks at his graphics repository, it's all sitting there. It's already authenticated. He doesn't have to log in again on that. If he looks at security, the entire Connect security model is available for him. He can assign groups and roles directly in the IDE, give them access levels and the likes like he would normally have done with the Windows or something like that. And, of course, that means that in the run time, if they go to OMI, in this case, it's single sign on, it passes on that ID to the to the historian, all the inside applications that you have in there as well. So this is kind of the the first step of it. There are sessions or there will still be sessions, that will explore this a little bit further and show you how it goes to all of the other products as well. Alright. The one other thing that we are working on constantly, which is surprisingly hard work to do, is to get rid of decom out of our products. It is entrenched there for the last two decades, and for the last couple of versions, we've been pulling it out slowly. I think we're gonna have two more versions where where it will be present or one more version that will be present, and that will be service pack one that's coming out now, and the next version in twenty twenty six, DCOM should be completely removed. But we are continuously removing it from the product, so it has been removed out of some parts of, twenty twenty three r two as well and know that we are getting to a point where you no longer have to to deal with that. We also added, IO without DI objects. If you set up an OI server today, you can specify a scope for it. Instead of using a DI object, you can then directly talk to the scope. So let's say the scope is called PLC one. Set up your OI server, point it to PLC one. When you do IO, you're just gonna go PLC one colon tag name and that's your IO. There's no need to go through a DI object, scan groups. No need to suffer with all of those things. It's in early stages right now. It is released, and we are busy improving it. We want to get to a very solid, high performance version of that because my goal is by twenty twenty six or the version after that, I don't need to have DI objects. I want you to rather prefer to move away from DI objects because they're painful. Alright. And then, of course, the deployment guides, has been released. So if you I think everyone here has heard of by now of docs dot aviva dot com. Please go and visit it. This is where all of our documentation lives. We are busy moving more there. Right now, the the deployment guide is there, but we are moving all of our documentation on there. Install guides, readme files, all of that will will make it onto that. Alright. Then just quickly, we released Patch one. There's no features in Patch one. It's just a bunch of fixes. We released Patch four on top of twenty twenty three. Same story, no features, just a bunch of fixes that we have in there. So it's easy to grab those fixes. And Service Pack one shall be released hopefully by the end of this month. We had to push it out a little bit to make sure of a couple of things. Basically, we released that because Microsoft is ending the life of dot net six on November the twelfth. Usually, when this happens, and it happens, Chromium, Google sometimes end of life stuff and Java and the like. Usually, we have a release available for us to go and make that change. This time around, we didn't, so it was too far out to wait for the twenty twenty six release. So we decided to put out a service pack, and the main reason for that service pack is that put a couple of features in there. So there's some features in there and that's in this other session I spoke about it, so go and have a look at that presentation if you if you miss it. Alright. Just very quickly, help us help you. I've see I put this in every one of my presentations. We recently launched, for application server, OMI, the products feedbacks, page. This is our ideas portal. You can go in there, look at the ideas that other people have in our product in in for products for application server and OMI and vote them up or add your own stuff. Very easy to use. Go log in. Create yourself a username and password. It's not decide it's not to spam you with anything. This is just to make sure you don't vote seven times. Right? Just to give you one vote per email address. Go to application server OMI. You can vote for idea ideas that are there. You can scroll through them. You can comment on them if you want to. If you have an idea that you can't find there, just hit the plus idea. It will open up this page, and then you can start typing your your idea in there. Right? And the system is quite clever. If you start typing your idea out there, it is going to start trying to recognize what it is that you're trying to do, and it's gonna give you some other ideas and go, is any one of these the ones that you actually would rather wanna use? And then you can just vote them up. But if this is a brand new original idea, you can just give us a little bit of information. Select the category in there, categories being parts of the product or aspects of the product like alarming or things like that. Select that in there. Click the add idea, and away you go. Right. This is moderated, so we get that. We will we will sanitize it. If there is if you have company information that accidentally exposed personal information, we're just gonna remove that so that we don't have you know, scare anyone by releasing personal information. But once we have that, we make it public, so be aware of that. And we've asked everyone else to vote on it, like, do you like this? And then we look at, you know, what comes to the top, and hopefully that's the thing that we build next. And then, of course, the last thing here is the Euros Forum. I think everyone has heard about this of this by now. Rachel is running our forum, very easy to get to. This is our community. This is where we wanna build community information, community knowledge. So I would like you to please help us with this. We cannot make this work on our own. We need we need our community to help us. This is the place to go and ask questions. If you have questions that are just, especially application type questions instead of product type questions, this is a good place to do that. If you just wanna look around and see what everyone else is doing, that's also okay. You don't have to. But, really, if you see something that you know the answer of and you see no one else has answered, please get involved. Tell them what you think, and we can have a conversation. And in this way, we broaden the the entire community's knowledge on our products. So there's a QR code to, to get to that.

Discover how the latest advancements in AVEVA System Platform and OMI are revolutionising the way you operate. Dive into groundbreaking updates that extend the reach of your OMI applications, bringing them to new environments with impressive speed and flexibility. Experience expanded data-driven visualisation capabilities that adapt dynamically to your operational data, and explore innovative features enhancing visualisation and localisation to better support your global operations. Learn how AVEVA’s pioneering connected experience is unifying our suite of products like never before, creating a seamless, integrated environment that sets a new standard in industrial software.

Download Presentation

Company

AVEVA

Speaker

Ernst Van Wyk

Ernst is a product manager at AVEVA and is responsible for defining the product strategy and roadmap for Operations Control, Supervisory products including AVEVA System Platform and the AVEVA Operations Management Interface (OMI).

Session Code

AW24-HMI-D2-SESS-358

Transcript

The marketing folks asked me to leave a little bit of time for Q and A at the end, and I didn't really plan for that. So I may have to go a little bit faster than normal and then see if I can get, you know, one or two questions in there. Again, not from the Aviva folks on the side, please.

Alright. So I just quickly have a look at the timeline as we have it right now, and I think most of you kind of know where we came from. System platform, again, twenty twenty three, was released somewhere in the middle of twenty twenty, around August that year. And at that point in time, we also had a release called system platform enterprise.

And the big goal of that system platform enterprise is to in to allow for the building of the UOC type in, implementations that we see. And the only way to get that was actually through the of your operations control enterprise. Now those license that license doesn't exist anymore today. Today, UOC is the correct licensing to go for.

And the reason why we did it on the system platform enterprise version is we needed a a web client that could work in enterprise environment. Now, a lot of the, the use cases that people look at that, oh, my web client was more HMI SCADA side, so we had to go and build a an HMI SCADA version of that, which is what we did in twenty twenty three r two. But just to talk a little bit about that enterprise web client, that client there, and and let's delve into it a little bit deeper. Oh, by the way, you would have seen us releasing patches over the last couple of, quarters.

The first patches took a little bit of time to get out to just to explain where that comes from, and if you were in the road map session, I'm sorry that I'm repeating that to you now.

We have the idea of getting rid of hotfixes. We wanna go to full patch releases. We wanna get to a patch cadence of monthly.

No more hotfixes so that every user can just grab the latest patch. There's no risk to it. There's no new features. Nothing.

It's just a roll up of the fixes. And you don't have to work with, tech support and go back and forth and find out there's a hotfix and do a hotfix request, etcetera. The patch should just be there for you to use. Took us a little bit of time to get the first one out.

The second one, we started getting into this cadence, and we're right now running about quarterly cadence. You would have seen us stopping, for the enterprise version because right about that time when patch three came out, we, deprecated the the system platform enterprise release. Not a lot of customers were using it. I know a lot of customers were aware of it simply because it had that web client in there.

So we then decided to put out the system our own brand of the web client that is more SCADA HMI based. So it's it's more of a web client that is really a SCADA or an HMI running directly inside a browser.

Okay. So let's talk about that a little bit, and see where it comes from. If you wanna run an o miner browser, right, we'd have to look at where the data comes from. Right? And I think everyone knows kind of where this picture goes.

You know, we have real world feeding data into system platform. System platform feeds it up into OMI. And there's, of course, some third party systems that you can run-in there. You can send that data into system platform, meaning you've got to build your own graphics.

But what OMI really did really well is it's able to visualize, or use visualization already exists. So if you have a spreadsheet that you wanted to show, you can just take a spreadsheet and run it directly in context directly inside OMI. And there's a couple of these apps. Right?

There's, like, map apps and video apps and picture apps and document viewers and all kinds of apps. So OMI does that really good. How do we build an OMI application? Well, we build a view app framework that gives us our navigation that's telling us how to, you know, do auto filling and all of those kind of things.

And then inside of that, we have some content that we're showing. Content basically being industrial graphics, used to be known as orchestral graphics. Right? That's our visualization or main visualization.

And, of course, these OMI apps that I just spoke of, this would be applications like the map app or being able to run a spreadsheet view or a JPEG view or whatever it is that you're running directly in there. And we also introduced a bit ago, we've introduced OMI, web widgets that allows you to run because our OMI apps are dot net based. These web widgets are JavaScript and HTML, based. So and they allowed us to get more web friendly widgets in there.

So when we build our initial in enterprise, we needed to find a way of running all of these things in a browser. Now, obviously, immediately, I have a problem because dot net doesn't run dot net one forms dot net WPF doesn't run-in a browser. So we had to go and create some additional, web widgets. So if you ever looked inside the installation of the enterprise version, you would have seen a whole lot of duplicated web widgets, duplications of the OMI apps in there that allowed us to run those apps inside the browser version of the enterprise version.

Visualization, basically two parts. There is my, kind of, my, business logic that figures out, you know, what the fill is, what the color is, what all of those things are. And then there's the drawing part that actually just draws the picture. After I've done all the logics and scripting and everything, I just draw the picture on the screen.

And it turns out if I'm running in a browser client or inside a web client, all I needed to do is create that web view framework or that web app framework that sit there with the with the navigation and the layouts. And then web, we just just run there because they JavaScript and HTML five, so they just run it directly in the browser. And it's very easy to draw already in the browser. We use SkiaSharp to do that, and we get some really fast reactions on it.

This is a a lot more scalable than running in touch access anywhere, for instance, where you have a remote desktop session per person. But in this case, you still have to have a process per person a process per session. Right? So that's why the enterprise version was kind of gets to a point where it's not suitable for SCADA HMI solutions.

So this is what we released for enterprise. We specifically called it enterprise because it's supposed to live on the IT side of your firewalls, not on the OT side. But we had a lot of customers asking for it, so what we had to do is move that visualization logic, that dot net scripting and all of those things running in the background, move it all into the browser. We found all of the best, most neatest technologies that Microsoft has, and we used it to, move the visualization logic, move that entire dot net logic into the browser as well. And we did the same for our OhMyApps. The OhMyApps back ends are all dot net.

We just put a new front end on it, and the technology we're using there is called Blazor. So we put Blazor on top of our dot net back ends and we move those apps into the browser as well.

Right. So that's the release of Oh My web client that you get in twenty twenty three r two. Okay.

There's a couple of things to take note of here and this is just based deep deep diving into the technology a bit.

We know we're using dot net. Right? We're using Blazor on the on dot net. We've we're using, WebAssembly, so that means that our dot net, applications are compiled to run directly in the browser.

Right? It's it's running on WebAssembly in the browser. Make it really fast. And, we're using Skia to draw to draw our industrial graphics inside the browser.

Why did we do it this way? It gives us black it removes all dependency on the platform. Right? It's platform agnostic.

I am not bound to Windows. I can run-in Linux. I can run-in Android. I can run-in iOS. I can run-in different places because I'm no longer bound to my to to the Windows environment.

And give us a single code base, and this has been probably mentioned a number of times in different sessions.

We are moving all of our visualization into this technology, which we call VisualizationCore, internally, but that technology is going to be used by all of our products. We're all adopting it. I'm gonna move it into the desktop environment of OMA as well, which which means that we have to, you know, make sure that there are no parity gaps between that and the desktop version. But what it gives us is it gives us a single code base.

So if I want to add a feature in the future, I only have to add it once. Right now, if I wanna add new feature, I have to add it for InTouch. I have to add it for OnMyDesktop, OnMyWebClient, InTouchWebClient, Insight. If I wanna add a new feature, I have to do it five times.

Once we get to the single code base, I only have to do it once. So that helps me, but we also did it in a way that it helps you because we want you to leverage your existing, efforts and your existing investment as well. In other words, if you build a Vue app that runs on the desktop version of OMI, you can take that same Vue app, deploy it on the web view engine, and run it right there. Now there's gonna be some gaps right now.

We've got a lot of them sorted out. So I would guess that most applications that we have today, if you only use industrial graphics, you're gonna get there probably to the ninety percent.

If you use some homegrown application objects and some home homegrown Ohmai apps and things like that, there's gonna be a little bit of a gap that you need to close yourself.

But we're gonna make it as as as tight as possible so that everything that you can do in the Ohmai desktop, you can do in the web client.

Right. So it's the same view app as you use in the desktop client, and it's really, really fast.

Microsoft is investing quite a bit in some of the technologies that we're running here. In some of our testing, we we we seem to be drawing faster in the in the web client than we do on the on the desktop client, which was a bit of a surprise. So we'll continue exploring that and make sure that we can give you the fastest possible solution that we can. And, of course, no additional installation is required. If you wanna point your browser, whatever machine you have, point your browser. As long as you're on the right network and you have the right credentials, you can go to your HMI.

Okay. So this is how it looks. This is what it looks like. This is inside the IDE.

I have my applications here. I've got a couple of view apps sitting on the side. I'm gonna take my nuclear plan. I'm going to deploy it on my WebView engine, so it's the same Vue app.

I'm just putting it there. And once I've done that, I can just click on the URL and it will open up my, WebView browser sorry, my WebView server, and I can go and select my application. In this case, I've selected my nuclear plant there, and it will do all the kind of things that you expect from OMI to be able to do. You can resize things and you can, of course, operate things and drag sliders around and all those kind of things.

It will do zooming. It will do panning and all of those kind of things that you need there. All of your animations and stuff should work pretty good. It also has the navigation tree on the side.

You have your breadcrumb at the top. All of those things will work, as well as, of course, there's an alarm app and there's a trend app in there. Things that we are busy ex expanding and making better than they are right now, but most of the things that you have in your current applications will just translate directly into the web browser.

Okay. So what that means also is it's platform agnostic. So just for fun, I added this into Ubuntu Linux. So this is Linux running over here, and I opened up a couple of, you know, opened it up in Firefox to see what it will do.

And you can see it supports Firefox.

And it's the same kind of experience that you have on there. It will open in Chromium browsers in Firefox. It will open up on iOS. It will open up on phones. Had a very unfortunate experience because I wanted to show it on my phone to you, but apparently our security is really good.

And I left I left the US more than two weeks ago about. And, on the hotel room networks, when my oh, my I saw the hotel room networks. It didn't allow me to say to do any control on my OT network. It just said, nope.

You're on a public network. You cannot do this. So, on my private network back home, I could get it running, but, unfortunately, I couldn't build you the the example here for my phone. But look out for YouTube.

I will build you some videos on YouTube on how to do it, and you'll see the differences there. Of course, this is just showing that it also runs in Chromium, and I then had a little bit of fun of putting these two things side by side to try and see if they if one is faster or a better experience than the other one. And I I really couldn't see it. I think it's pretty much the same code executing there because it's just WebAssembly that runs both of them.

So they are side by side, have the same kind of experience that you would have.

Alright.

Much fun.

That's the web client. So there was a lot of talk about that in the road map session as well. If you missed the road map session, please have a look at the presentations. They will be available afterwards.

In there, you'll see that we also now with the new releases coming up, we'll support progressive web apps, which means you can run this without a browser. Pretty cool. So if you missed that session, please have a look at that presentation afterwards. Let's talk about embed content.

Moving on to the more mundane stuff in system platform right now.

You all know if you're gonna design something in system platform, you need to kind of know what's gonna be on the graphic. Right? If I'm building a field of cows, I need to know exactly how many cows I have there. In design time, I put my four cows on there, and it's all good.

But what if those cows are not known? If I if they stored somewhere else, they're not part of my model. They're sitting in a database of SQL or Oracle somewhere or I've got a REST APIs to my cows or, maybe they're sitting in a CSV file. And I only know at run time how many cows I have or where they are.

So for that, we added the embed content function that allows you to go and view the well, pull whatever data you need from wherever, and in run time, place them on at the correct x y location. So it doesn't matter what they are. You you can just dynamically find out and put them where you need them on the screen.

Bunch of use cases you can think about this.

Initially, we kind of played around with it, but we've got people building dynamic face plates and things like that just directly from the PLC. It's pretty cool. So the way we, I explained it here is I've got some people. Actually, it's just interesting.

This is a SVG that I pulled out from just from the web. It was pretty cool. I just put because I don't know if you're aware of that. In the previous version, we allowed you to just drag an SVG onto the screen.

It will create all the elements, so it will create a shirt and the shoes and everything available for you, and you can go and animate them directly. If you have someone building stuff for you in SVG, nice cool tool.

And assign some custom properties to that. And, of course, you can in design time go and drag these things onto the screen if you know where they are. Orient them, give them custom properties, but we wanna do it in run time. So in run time, I'm taking that that graphic.

I'm setting some of its custom properties, changing the color of this of the shirt and the likes, and I'm rotating it. And then I select an x and y position, and I say add it and it adds it to the screen. And, actually, what I did here is I made it so that if I switch on that random and I click anywhere on the screen, it will just randomly put a human being at that x y location, which is also now readable from your mouse. So you can easily just stick a couple of pictures on there.

Actually, that ad multiple just added ten random people, and it did that in basically milliseconds, so it's fairly reactive, except if you have really big graphics, you can keep that in mind.

You can also do things like deleting them and, you know, if you select something you can go and change the custom properties, hit the modification button, and it would modify it in place. I actually made it so that if you select something and then modify it and just right click somewhere, it will just move that that human around in the this is the White House, by the way, so I'm putting humans in the White House.

It was just for fun. The the important part is these graphics participate as if they were embedded in design time. They can pan. They can zoom.

They can do all of those things that you would normally do. It's as if you built this with the graphics in there right from the beginning. So it's not little hover over dialogue boxes and stuff sitting here. It's part of the graphic.

Very nice little feature. If you build nice stuff for that, send it to me. I'd like to see what you did, even if it's just a screenshot.

Alright. Let's move on. Alarm latching is something we did for some of our customers, that were asking about different ways of handling alarming or an additional method.

Quickly, before this release, we had four modes of alarms. You had normal. Nothing's going on. Goes into alarm.

I can go out of alarm in two ways. I can acknowledge it and then wait for it to return back to normal, or it could go back to return to normal, and then I acknowledge it. Right? Those are the the four states I have there.

And, of course, I can if if it goes back into alarm, then I go back into the alarming state, on there. So what we've added is optional, but if you're interested in that, you can optionally add the latch state, which means it does not go back to normal state when it's acknowledged and returned. It actually goes into the latch state, and you can hit the dismiss button. It will go off the screen.

It just gives you that extra you know, the alarm is fully handled. It's been seen. It's acknowledged. It's returned.

You can now take it off the screen if anyone wants to use that.

We made some changes to the IDE, to the UI and UX.

Don't swear at me when you see them.

But, there's some of them that are really cool, and we're gonna make them better. I know that there are some things that have really moved everyone's cheese around a little bit, but it is we are trying to make it better, and we were kind of forced to do certain things because of changes in life cycles and the likes. So we will try to make improve it. Things that I really like that's new in there is the ability to go and search for something, so you can just start typing something in there. It searches for it. It shows you in the tree where it is. You can actually also go and make it a flat list, so it will just give you a flat list of all the things that it found.

Our status indicators are sitting on the side now with little tooltips. If you hover over it, it will tell you if it's in warning, if it's opened up. And if you go and, check something and you make a change to something and check it in, it'll tell you, that it's edited and you need to go and, deploy it on there. And then there's a little, icon guide that will show you what all these icons mean. We're not done here. We need to add filtering and things like that in there, and we are gonna make it better. I know there's some things here that are really bugging some people and we are trying to make it better for you.

One other thing that I wanted to show you, and I wasn't sure if anyone knows this, and I'm on purpose used a slightly smaller resolution here. It's I think it's thirteen sixty six by seven sixty eight, so it's a little cramped. But I I don't know if everyone's aware here, so I wanted to show it because, I found that a lot of people would didn't know that we made this change.

You can drag things around. You could always do this kind of, but it wasn't really a good experience. But now we've added these little, tie in points so you know exactly where you're dragging a a panel in there. And, all fun and games.

If I put all my panes once next to each other, I can start drilling into them. By the way, I don't know if you know this, but if you press control shift zed, it will synchronize those panes. The problem being if I open it up, I am running out of space. Right?

It's difficult to do. But luckily, you can just drag that attribute editor, put in another screen, run it in the full screen or that time. I don't know if you were aware of that. And you can just start working on that.

And, of course, if you have my screens, you can add your graphic editor and your SMC and your, all of your editors can run side by side on that. But the important part is if you add more of these attributes, you can drag them onto that other screen. You can run them in the same tab group, so it will create a tab group, or you can drag them onto the side and you can have two different tab groups or whatever you want.

Really makes it a lot easier to work with your attribute editor if you can drag it around. Okay. So I wanted to show that to you.

Okay.

Internationalized string support. You all may be familiar with the fact that we have an attribute type internationalized string. And that internationalized string is now translatable. So in the IDE, if you go and export it for an object, you get the option to export internationalized strings like you would be able to export alarms, and that gives you a list of all the internationalized strings and their values in a CSV format, which you can then go and open up in in this case, I'm opening it up in Excel.

And I'm I am cheating a little bit here because I'm using the translate in Excel because I didn't wanna type them out in front of you. Just copying all the translations in there. Gave me a quick Afrikaans version of this, and, then you can just go back and import it. Now if you look at the application, this is all internationalized strings.

So for instance, the Boolean on off message for auto manual stop and start, those are internationalized strings. The descriptions for objects, the descriptions for attributes, engineering units, they are all internationalized strings, and those are also the things that we use when we push down into the alarm system and into the trend system.

We also have internationalized strings as the alias for that's used in our navigation. So if I go out and I change this over to Afrikaans now, everything on the screen will change over to Afrikaans. Every internationalized string that's in there, by the way, I also did the alarm so the entire screen will turn over to to show you the Afrikaans version of the software. And you can see if you, you know, if you swap around these things, they they the Boolean on off messages and all of those things are translated properly. If you use one of the big six that we have full translation for, it will even translate things like the so if I use German, for instance, you'll see the column names and the actual UI of the train controls and the alarms will also be translated. That happens with the metric. You don't have to export, import anything for that.

Alright. That was string translation, global buffering.

I hope everyone here is aware that we can add on buffering for your IO. So if you enable IO today, there's a there's a little checkbox that you can enable and say make it buffered, which means if the data is coming in faster than I can show it on the screen, I still want to have that in a in a in an array. Keep it between an array. Store it all in the historian at the back end so that means I can get data faster than I would normally do. I can do that for multiple attributes. I can but it is a little bit of a pain if you have to do it for every attribute. So in the last version, we added one checkbox under the communication, advanced communication, enable that, buffering goes on automatically for all IO that you have in the system.

If your IO speed is more or less the same as your engine speeds, you will see zero performance difference between them. We see no performance impact at all with the added advantage that if they don't if they don't intersect, if there is a missed attribute, it will grab that one and also send it to the store, and so you won't miss any IO. And you can actually get to them if you want to in the in the array.

Alright. That was auto buffering.

Then there's the AVEVA operations control experience. I'm I'm gonna quickly talk about why we wanna do that. I think a lot of people have already talked about that. But the main case here is we wanna do something similar to what some what Microsoft has done.

In other words, they have a bunch of on prem software. Right? And they have a hybrid cloud platform, which means that they also have a bunch of cloud software. And some of these things are really useful in on prem.

In other words, like a PowerPoint or an Excel or whatever is something that you run on your machine. Right? It's not something that you run-in the in in the cloud always, but you wanna be able to share and do things in the cloud. So what they've done is they've they've given a bunch of Office three sixty five.

It used to be called now Microsoft three sixty five packages that allows you to connect to Azure AD, and all of their on prem products now also connect to Azure AD, AD, which is pretty cool. That means that suddenly your Excel works inside Teams, and you can share stuff in SharePoint, and you can have Outlook and SharePoint and and OneDrive, and all of these things work together because you're all the same user. Right? It understands exactly who you are.

We have the same kind of thing that we wanna do in our products, bunch of on premises products that we have. Right? InTouch and OMI and all of those kind of things. We also have our cloud products.

We have Teamwork and Insight and all of those kind of things. And what we're doing is we had it connect to it. Right? So now you have a single user in there and everything is connected.

So everyone using on premises software as well as the cloud software has the same user and has access to the same things. And the idea here is not just to make it single sign on, although that is the first use case, but it's also to start adding value to it so that if you build a graphic in InTouch and you store it under your name in the cloud and you go into OMI and you open it up there, it's the same graphic. It's the same folder. You you can just keep on working with that because it's the same kind of experience that we have with Microsoft.

Alright. And then, of course, there's the three packages there, Edge Supervisor and UOC.

One last point to drive home on that is, in the traditional software models, typically, you would have a license for one box over there, but that user, if you wanted to use his phone or a tablet or a browser or anything else, would need separate licenses. He couldn't get any access to any of those things. In the operations control model, we have all of those devices licensed just by the username. So this single user gets access to all of those devices, and, by the way, has a he has a consistent experience over that, meaning that if he looks at these graphics on one device or on another device or on another product, it's the same graphics that he's looking at.

So that's kind of where we're going after the ops connected, stuff. And, of course, the just last one point is, you know, someone this is what they call the day in life. This is a person. What is he doing during the day?

It's just one person on one day, has a bunch of tasks. You know, they have all these things that they need to do, and they perform all these things during the day, and they perform all of these things on different devices.

Right? Right? And then if you think in the past, how would you license all of that, you would have to go and figure out what this use case it the the product is, what this use case product is. Then you would have to go and have a license for each one of those devices. In the ops control model, you license the user, and he does everything on any device that he wants to be. Very easy. So I really would advise you to look at ops control as a as a as a very good alternative for licensing and getting your hands on our software.

Alright. Quickly showing you what that looks like. I'm just gonna show you the system platform pod. This is guy logging for the first time in the IDE, logs in with his username and password, gets challenged by the Aviva Connect by the Connect ID, signs into it, and once he's done that, everything knows who he is.

He's now in single sign on mode. If he opens up his licensing, it knows what his entitlements are. If he actually connects to a Galaxy, it automatically unauthenticate him against the roles of that Galaxy, make that available. If he looks at his graphics repository, it's all sitting there.

It's already authenticated. He doesn't have to log in again on that. If he looks at security, the entire Connect security model is available for him. He can assign groups and roles directly in the IDE, give them access levels and the likes like he would normally have done with the Windows or something like that.

And, of course, that means that in the run time, if they go to OMI, in this case, it's single sign on, it passes on that ID to the to the historian, all the inside applications that you have in there as well. So this is kind of the the first step of it. There are sessions or there will still be sessions, that will explore this a little bit further and show you how it goes to all of the other products as well.

Alright. The one other thing that we are working on constantly, which is surprisingly hard work to do, is to get rid of decom out of our products.

It is entrenched there for the last two decades, and for the last couple of versions, we've been pulling it out slowly.

I think we're gonna have two more versions where where it will be present or one more version that will be present, and that will be service pack one that's coming out now, and the next version in twenty twenty six, DCOM should be completely removed. But we are continuously removing it from the product, so it has been removed out of some parts of, twenty twenty three r two as well and know that we are getting to a point where you no longer have to to deal with that.

We also added, IO without DI objects. If you set up an OI server today, you can specify a scope for it. Instead of using a DI object, you can then directly talk to the scope. So let's say the scope is called PLC one.

Set up your OI server, point it to PLC one. When you do IO, you're just gonna go PLC one colon tag name and that's your IO. There's no need to go through a DI object, scan groups. No need to suffer with all of those things.

It's in early stages right now. It is released, and we are busy improving it. We want to get to a very solid, high performance version of that because my goal is by twenty twenty six or the version after that, I don't need to have DI objects. I want you to rather prefer to move away from DI objects because they're painful.

Alright. And then, of course, the deployment guides, has been released. So if you I think everyone here has heard of by now of docs dot aviva dot com. Please go and visit it.

This is where all of our documentation lives. We are busy moving more there. Right now, the the deployment guide is there, but we are moving all of our documentation on there. Install guides, readme files, all of that will will make it onto that.

Alright. Then just quickly, we released Patch one. There's no features in Patch one. It's just a bunch of fixes.

We released Patch four on top of twenty twenty three. Same story, no features, just a bunch of fixes that we have in there. So it's easy to grab those fixes.

And Service Pack one shall be released hopefully by the end of this month. We had to push it out a little bit to make sure of a couple of things. Basically, we released that because Microsoft is ending the life of dot net six on November the twelfth. Usually, when this happens, and it happens, Chromium, Google sometimes end of life stuff and Java and the like.

Usually, we have a release available for us to go and make that change. This time around, we didn't, so it was too far out to wait for the twenty twenty six release. So we decided to put out a service pack, and the main reason for that service pack is that put a couple of features in there. So there's some features in there and that's in this other session I spoke about it, so go and have a look at that presentation if you if you miss it.

Alright. Just very quickly, help us help you. I've see I put this in every one of my presentations.

We recently launched, for application server, OMI, the products feedbacks, page. This is our ideas portal. You can go in there, look at the ideas that other people have in our product in in for products for application server and OMI and vote them up or add your own stuff. Very easy to use.

Go log in. Create yourself a username and password. It's not decide it's not to spam you with anything. This is just to make sure you don't vote seven times.

Right? Just to give you one vote per email address.

Go to application server OMI.

You can vote for idea ideas that are there. You can scroll through them. You can comment on them if you want to. If you have an idea that you can't find there, just hit the plus idea.

It will open up this page, and then you can start typing your your idea in there. Right? And the system is quite clever. If you start typing your idea out there, it is going to start trying to recognize what it is that you're trying to do, and it's gonna give you some other ideas and go, is any one of these the ones that you actually would rather wanna use?

And then you can just vote them up. But if this is a brand new original idea, you can just give us a little bit of information. Select the category in there, categories being parts of the product or aspects of the product like alarming or things like that. Select that in there.

Click the add idea, and away you go. Right. This is moderated, so we get that. We will we will sanitize it.

If there is if you have company information that accidentally exposed personal information, we're just gonna remove that so that we don't have you know, scare anyone by releasing personal information. But once we have that, we make it public, so be aware of that. And we've asked everyone else to vote on it, like, do you like this? And then we look at, you know, what comes to the top, and hopefully that's the thing that we build next.

And then, of course, the last thing here is the Euros Forum. I think everyone has heard about this of this by now. Rachel is running our forum, very easy to get to. This is our community.

This is where we wanna build community information, community knowledge. So I would like you to please help us with this. We cannot make this work on our own. We need we need our community to help us.

This is the place to go and ask questions.

If you have questions that are just, especially application type questions instead of product type questions, this is a good place to do that. If you just wanna look around and see what everyone else is doing, that's also okay. You don't have to. But, really, if you see something that you know the answer of and you see no one else has answered, please get involved.

Tell them what you think, and we can have a conversation. And in this way, we broaden the the entire community's knowledge on our products. So there's a QR code to, to get to that.