Presentation: AVEVA Roadmap: Edge software driving efficiency for plant floor monitoring and control

2024 - AVEVA World - Paris - HMI/SCADA

AVEVA Roadmap: Edge software driving efficiency for plant floor monitoring and control

Welcome. I'm Rick Arnurin. I'm a product manager in the operations control, part of the business. I, oversee our HMI or Edge offer, including InTouch, Aviva Edge, communication drivers. I have my colleague, Scott Cartier, here in the room also who manages this together with me. We have a very exciting presentation, I think, about where we're going with our HMI offer. I guess some of you were attending John Krajewski's presentation just before this and heard some of, hints at what we're doing here. But, we have some really exciting times in front of us with some new versions over the next couple of years. So let's dig into it. Our HMI journey started in the late '80s, early '90s with two brands, Wonderware and InduSoft. And we have had a fantastic journey with these brands, through the nineties, through the 2000s, and up to date with establishing ourselves in about a third of the manufacturing assets in the world, and going beyond manufacturing into infrastructure, power, all kind of things you can imagine. So we the impact we have on our daily lives and the food we eat, the power we consume, the roads we travel on, is amazing. So it's been really good, going through that, you know, starting on Windows version two to being on a sixty four bit Windows eleven today. And we're taking a major new step forward on this journey. Right? Aviva HMI and Aviva Edge, the former Indusoft brand, is now taking that journey together. We're starting off with making a major step forward with InTouch, and then Edge will will kind of follow and join into that as we go. Modernization at accelerated rate, adopting new technologies, addressing new or the contemporary requirements. We're also trying to put a lot of emphasis on the legendary ease of use that made this product so successful to begin with. But we've recognized that over the years, we have added so many features into the products without taking anything out that it's become a little bit complicated. Today, I have several different ways to draw a rectangle on the screen. Which one do I pick? If I want to put a historical trend on the screen, I have five or six different options. One works in the web client. One works in the desktop. And there's all these kind of things that, as an application developer, I need to navigate. So we're trying to reduce that, to keep the same capabilities, enrich those capabilities, but fewer options, have options that have a a a consistent capability regardless if you look at it through a web browser or a desktop client. As part of this, you will see some new technologies joining into the in Touch HMI. You also see some of the older technologies leaving. But we are very much committed to protecting your investments in the applications you built, into the skills you have acquired to to continue that path forward and have incremental value on top of what you have today. So there there will be a lot of different things. I'm going to touch on a couple of aspects around common visualization, around ease of use, ease of getting started. So let's get started with getting started. Right? The first thing we often do is if you want to try out an HMI product, you want to download it and install it. We have had a interesting journey. As I mentioned, we started off somewhere here with the floppy disks in the early nineties, but we kept that paradigm. Right? It's always been a disk, a floppy disk, a half inch disk. You we went to optical disks. We went to virtual disk, like zip files and ISO archives, but still a disk. We have also increasingly complex post install configuration that you need to do to sit through after you install the product, which adds to a very kind of complex journey before we actually can start to try the software. So we want to embrace, you know, this being digital and look at different patterns on how to deliver the software. One of the things we already done is just access the software. You can go to the product page on aviva dot com today, download InTouch from there, and start to try it out. Now it's still a, whopping nine gigabyte ISO file together with system platform and a bunch of things, which makes for a large download and and, of course, exposure to a little bit more complexity in terms of what you pick to install and and and those things. But we're addressing that next. So this is available today. But where we foresee going and mind you, this is a prototype, so it's not a finished thing, but actually working software today in our lab, where we download a small, in this case, an eight gigabyte oh, sorry, eight megabyte. We shrunk it. Right? It's eight gigabyte today, and now it's eight megabyte. You install that, you run that, and you pick what to download and install. So if I if I'm connected to Internet here, I just hit install, and it will download and install simultaneously just the pieces that I choose, not the full range of of operations control software. And, of course, we will support here also to kind of predownload a a installer that I can bring with me to an offline computer to install it without an Internet connection. We will also support your automated installation or silent or unattended install by scripting, by just calling this executable and telling it what you want to install. As as part of that ease of use, as part of the the expectations we have today, my monitor went blank here, we, we also support dark mode. So we follow the user preferences in the operating system. If I prefer to light mode, it follows that. If you have dark mode, it follows the dark mode. Our internal joke there is that we prefer dark mode because bugs are attracted to light. Don't know if that holds true. Now something very interesting here is that after that install, which is about a five minute process, we jump directly into developing an application, directly into what we start to refer to now as the the InTouch h IDE. And, I can directly start to build content and drag data into this to to build an application. We merge in the application manager of InTouch so that you don't need to jump through multiple utilities until you get to to to development. Alright. We also recognize that we need to manage updates in a better way. So, still a bit of a conceptual design here, but you go into the same installer again, and you can check for updates. If new patches are available, you can install them from there through this interactive user interface or, again, through downloading it and bringing it with you to the offline computer or, by automating this with shell scripting or or other IT tools. Now, of course, once you have acquired a software, you installed it, you may want to have some guidance. We are embracing an openness in terms of of much of this, not only putting the installer publicly on our website, but we have also recently moved the entire documentation to the common documentation portal of Aviva at docs dot aviva dot com. It's there already for the twenty three r two version, and this is the focal point for documentation moving forward. We'll still install documentation with the products, but by having it online, we can also have a more living documentation. We can start to enrich this with more immersive content like how to videos and and and more things which would be problematic to install and and carry with us in in the installer. So we're very excited about that, and, we're also working on a deployment guide for InTouch, which will be published through this site, in the next month or so. You need further guidance on that. Well, beyond documentation, we have our online community, Heroes HQ, where you can interact with peers across the ecosystem. Aviva is very active there. We have system integrators active there, customers active there, talking about troubleshooting, best practices, or whatever topics that that may come up. From the Heroes HQ portal, you can also access the learning bytes, like micro learning content around in touch HMI, how you use it for different particular features and purposes. So all of that is available openly. There's no paywalls. There's no registration to go through to access those kind of things. You do need to register if you want to comment or or publish things in this forum, but you don't need to register to to access it. It. Same goes with the documentation portal. It's just wide open. You don't need to log in. You don't need to speak to an Aviva salesperson to get access to it or nothing like that. Now once once you're in there, what is the typical thing you you do? We have different workflows. I mean, some people prefer to start to create a graphic. Other prefer to pull some data into an application. Now accessing data, we have recognized, is a little bit awkward workflow today involving multiple tools and utilities. We're bringing all of that into the InTouch IDE and, subsequently, also into the system platform IDE so that I can manage my data sources there. When I arrive into the IDE here, I can click a button to say that, hey. I want to connect to a data source. Is that an OPC UA server? Is it the broker for MQTT? Is it the Siemens PLC or Schneider PLC or whatever? You just pick whatever you want to connect to. With if if that protocol supports discovery, it may actually say that, hey. I found this three OPC UA server on network. You can just pick one of those, and you're directly immersed in that that data model. You can explore that data model, pick whatever you need, and then drag that into your application. Bits and pieces of this are already in Intacct twenty twenty three r two, but we're refining this to to also support QDTs and structures. And we are also integrating not only OPC UA, which is there today, but MQTT. We will make it easier here also to publish out through MQTT and the an OPC UA. You may have heard from John this morning that these are our areas that we're focusing very much upon, but we're building it in such a way that we expect, subsequently to also plug in other browsable sources, PLCs, vendor specific protocols, and and other open standards. So you can very rapidly go from hitting download on the Inter product page on aviva dot com until having live data in your application. We we aim for that to be around five minutes. Now, realistically, perhaps in the first couple of releases, we will be around ten minutes, but five is our goal. And and, of course, also to bring these things together is not about only configuration. We want to have a a clear indication. Am I connected to a data source that I just configured or not? What's going on with it? Can I just drag a few items into a watch window and see if I've referenced it correctly? Is my subscription working? Have direct feedback on this without having to go back and forth and look at log messages and environment, you can just put those things on a work window and and see how you go. Of course, build out a little bit more views. And and I recognize we need to offer perhaps a way to save and open different windows there also. So that drastically reduces the amount of work you need to do to get to a point where you have live data in your application. Now there are many more enhancements to what we're doing. These are some of the more visual items. But on the back end of this, we are also doing a lot of refactoring on the underlying services. Intel today is a very monolithic executable. If you want it to run faster, you need a faster CPU. Now, I think many of you are aware of the fact that the CPU industry is going in a different direction. We're no longer going for faster and hotter CPUs. We're embracing parallelism instead with multiple cores, slower, CPUs. If you have a new laptop, you may recognize that you have these eco cores that run slower than the performance course to just consume less power. We are working on making InTouch a microservices architecture to scale such a way. We're introducing power consumption as a performance metric in our labs to be able to to to address it. Part of this is also that we make it into a sixty four bit process, which allows us to address some different things, new data types with higher resolution. We are addressing also this y two k thirty eight time issue. That's a I guess most of you were there for the y the the y two k, the backfill. We have another one on the horizon. If you if you're not aware of that in two thousand thirty eight, the the thirty two bit time representation will kind of overflow, and we need a sixty four bit number to do that, to keep track of time. Now many thirty two bit systems already have ways to deal with that today, but we are covering this by just moving into a a sixty four bit architecture. And that could be good to know because you may see requirements from your internal IT teams. Or if you're a vendor, you may see this in procurements right now that you need to have a plan to deal with this already today even though it's still a few days or years into the future. As we're reworking this, we're also trying to adopt more modern terminologies. We have some legacy vocabularies today in our HMI offers with phrasings like discrete instead of a Boolean. We find that, increasingly, people don't really connect with that. They they have learned a different vocabulary before before they even see our software. So we're moving to call a Boolean a Boolean. We are moving from real to float. We're working calling it string instead of message. And, of course, adding a few data types to that. We are working right now on double, and Jira is still out if we call this elapsed time or duration, but, basically, a time span, type. And there's more to come there also as we're driving further alignment with external standards like OPC UA, which has things also like byte string, image, audio, those kind of aspects. So there there there's much more more to come in in terms of that also. Some of the some of this is, of course, under the hood, but some of it also opens up to new development capabilities. Now the final piece of this is around the visualization. And, hopefully, many of you recognize this journey that we we started to to talk about a few years back, what we call the the operations day in life, how, throughout the workday in operations and takes you to different locations, working together with different people, using different type of devices. Sometimes you're in front of the HMI, which is bolted onto the machine on the planet floor, but sometimes you may be, in the metro on your way to work. You may be in the cantina just with your phone having access to things. You may be in a centralized control room with a lot of different screens and devices. But throughout this journey, we want you to be able to access information from the HMI in a consistent way. Just pick up whatever device that is nearest. If you have access, you can access that information. So so going from the traditional presence where where you're in front of the machine with HMI, we want HMI to be reachable also when when you're, let's say, within reach and also make the same information available when you're out of reach. You're connected from a different network. And, obviously, this this operator personality doesn't work in a vacuum. There's other people around there also, and collaboration requires, I think, unambiguous information. You need to not only have the same data, you also need it to be visualized the same way. So when when operators say, do you see what I'm seeing? He can be confident that a lot of people say, yes. We see exactly what you're seeing, pixel perfect representation, of what you're seeing. So there's several things we're doing around that. The first is one graphics technology. In our HMI offer today, we have multiple different technologies. As I mentioned, drawing a rectangle on the screen, that's different ways to do that. Making trend tools, different ways to do that. So we're focusing around industrial graphics, and we're migrating our legacy graphics onto industrial graphics. For InTouch, that migration from legacy graphics to to industrial graphics is a very high fidelity, has been there now for close to ten years. But we're focusing on industrial graphics, and we're leaving some of the older technologies behind. We also have one rendering mechanism to make sure that that graphic that I created, it looks exactly the same on any of these devices for all of these different people. And, of course, this a a key value of this is also as you start to grow into other Aviva solutions, if you if you plug this into a supervisor's SCADA also with system platform, that symbol will be reusable there. It will look and behave exactly the same. If you draw that you pick that symbol up and and and stick it into our cloud visualization, it looks the same there. It behaves the same there as well. Now industrial graphics has been around for quite some time, and there is a really powerful visualization technology. These are just some examples that I've threw together from some demos we have had over the years. It's actually the same application. It's just gone through different generations of design, design philosophies from that rich, artistic, skeuomorphic representation to the various felt, situational awareness graphics, to a more, let's say, Google material like thing onto a more dashboard or or dashboard oriented thing. Right? So industrial graphics allows you to do a very wide range of things. So, it's a fantastic technology for us to convert on. We also support with, industrial graphics a designer and developer collaboration. We introduced recently an SVG import, which allows us to take designer output from tools like Figma, Adobe XD, and other design software, and just drag that directly onto a industrial graphic surface and apply animations to it. So we we reduced that that the turnaround process between the designer and and the developer also. And and involving designers in also this industrial context is incredibly valuable in terms of promoting perception of information, quick understanding of information, and how we can get from vast datasets to actionable information. So in in InTouch, we are changing. I I mentioned the InTouch IDE. We cannot call it WindowMaker anymore because there's actually no windows here anymore. We're now talking more about pages As we move to a more web oriented architecture, more web oriented terminology, we draw those pages directly here in the Intouch IDE as an industrial graphic. The industrial graphics are now promoted to be at the at the forefront of the IDE, as we replaced the the legacy graphics. And and we can draw that directly on tabs here in the surface. We can add custom properties and scripts as usual to it. And adding to those pages, we're also introducing the layout capability from the OMI framework so that I can organize these these pages into particular layouts and things and and drive things like footers, headers, menus, slide in menus, from all different directions. And, of course, that I can develop all this stuff, take that with me into a system platform application, or take what I have in system platform and build out an HMI from it also. So these are some quick early previews of what we're working on right there. Obviously, if you go hit run time now, you will end up in a in a kind of web based client server experience, instead of the traditional desktop experience. And we as part of this, we are dropping things like the legacy graphics, ActiveX controls, and some other technologies that had been on their way out for quite some time, but now we're taking that leap forward. And again, the legacy graphics, if you're still using those, those convert very nicely into industrial graphics. But it comes back really to our idea around this being portable across everywhere. Consistent user experience. If I'm looking at the same information through one lens or another, I see it consistently. My colleagues see it consistently. If my workday takes me across these different areas from the operation center out to the machine itself or if I have just mobile access on my phone, I can see it in the same way. Very important. And from a a application and life cycle management perspective, all these things, the graphics and content that I build is pluggable across this entire span, with different tiers of of Aviva products. Finally, with this, of course, you need to license it. At some point, we also like to get paid. So, but we are relaxing some of those commercial constraints. Right? No license. If I'm trying this out, I just downloaded it off the Aviva website. Do I need to talk to a salesperson just to try it out? No. Starting with our our recent patch, and it's more formalized now in the service pack we're releasing in a few weeks, the development environment no longer requires a license. So that makes it so much easier to get started. But also for existing customers, if you're doing field services work, you no longer need to go on to the plant floor and plug in your development license and and all this back and forth with activating the deactivating licenses. You can just run the if you're authorized to do so, you can run the development tools, make changes, try those out, and then put that into production. The the runtime will actually now run without a license. In the past, you could run-in demo mode up to sixty four tags. Now, Intouch runs for free up to sixty four tags. If you want to think through with this at home and apply Intouch or HMI to to some of your home automation, go ahead. But beyond sixty four tags, it runs in demo mode and will stop every two hours, so that you can actually develop and test the full application without having to talk to to us for a license about it. Now when you put it into production, obviously, then you need a license. We have made significant changes there as well to accommodate the the the more contemporary needs. We offer unlimited licenses, which bundle up with different tiers of of of other Aviva software. But the fundamentals of this is that you can have a license today which is completely unlimited from tags standpoint, unlimited Windows, unlimited clients. If you're doing the standard edition, you have unlimited web clients. If you're doing the professional edition, you have unlimited remote desktop clients. We're bundling historian. We're bundling reports and things, and it's really a fantastic offer. Now I see I'm slightly over time, so I will just try to wrap up here. Next year, we aim to release Intouch twenty twenty six, which makes this big leap forward. There will be a minor release for Aviva Edge with some customer commitments, security enhancement, and things. But after the twenty six releases, we are working toward a unification of these two products. This may take us a few versions, but we make sure that you can stay where you are today, without any disruptive changes. Right? So the twenty three r two versions will be a long term servicing channel with extended support lifespans, so that we can start or or our ecosystem can start to to consume these changes at your own pace. I also want to highlight that the InTouch four system platform will be kept as is. So all the changes we're doing to the HMI will be for standalone HMI. If you're using InTouch as a client to a system platform, it will be put into maintenance mode. It will continue to get bug fixes, security enhancements. We're not building any new features for that. OMI, the operations management interface, is now the the primary client for system platform. And we will put our efforts into enhancing that migration capability from InTouch Force system platform to OMI. That's where we invest in terms of system platform. But no new features for InTouch as a client to system platform. And we'll keep InTouch Force system platform around for the foreseeable future. I guess we will just extend that forward until we have a very small step into the operations management interface. So, it's absolutely not going away, but we have just put a stop to it in terms of new features. We will say that if you're doing system platform for new projects today, use OMI. If you have an existing state of InterForce system platform, you can continue running that and we will close the gap in terms of moving you forward. With that, I need to wrap up and, I guess, hand over the stage to the next speaker. You can hear also more about our HMI offer at Scott's session later today, where he goes into the details about what we did recently in terms of features. I stole a few of his slides and and some of his thunder here also, but, there's there's many more great things there to to see. So with that, I will, get off the stage, but I'll be around for for for questions. Thank you very much.

AVEVA has been a leader for the last 30 years in ensuring your frontline teams have the local process monitoring and control they need to get the job done right whether monitoring a manufacturing line or at a remote operating site. We continue that tradition and ensure your teams can take advantage of all the capability our latest 2023 R2 releases have to offer. Join Rickard Norin as he walks through the roadmap and latest functionality available with AVEVA Operations Control – Edge including AVEVA InTouch HMI, the world’s most widely used plant HMI and AVEVA Edge HMI.

Download Presentation

Company

AVEVA

Speaker

Rickard Norin

Session Code

AW24-HMI-D2-SESS-351

Transcript

Welcome. I'm Rick Arnurin. I'm a product manager in the operations control, part of the business.

I, oversee our HMI or Edge offer, including InTouch, Aviva Edge, communication drivers. I have my colleague, Scott Cartier, here in the room also who manages this together with me. We have a very exciting presentation, I think, about where we're going with our HMI offer.

I guess some of you were attending John Krajewski's presentation just before this and heard some of, hints at what we're doing here. But, we have some really exciting times in front of us with some new versions over the next couple of years.

So let's dig into it.

Our HMI journey started in the late '80s, early '90s with two brands, Wonderware and InduSoft. And we have had a fantastic journey with these brands, through the nineties, through the 2000s, and up to date with establishing ourselves in about a third of the manufacturing assets in the world, and going beyond manufacturing into infrastructure, power, all kind of things you can imagine. So we the impact we have on our daily lives and the food we eat, the power we consume, the roads we travel on, is amazing. So it's been really good, going through that, you know, starting on Windows version two to being on a sixty four bit Windows eleven today.

And we're taking a major new step forward on this journey. Right?

Aviva HMI and Aviva Edge, the former Indusoft brand, is now taking that journey together.

We're starting off with making a major step forward with InTouch, and then Edge will will kind of follow and join into that as we go.

Modernization at accelerated rate, adopting new technologies, addressing new or the contemporary requirements.

We're also trying to put a lot of emphasis on the legendary ease of use that made this product so successful to begin with. But we've recognized that over the years, we have added so many features into the products without taking anything out that it's become a little bit complicated.

Today, I have several different ways to draw a rectangle on the screen. Which one do I pick? If I want to put a historical trend on the screen, I have five or six different options.

One works in the web client. One works in the desktop. And there's all these kind of things that, as an application developer, I need to navigate.

So we're trying to reduce that, to keep the same capabilities, enrich those capabilities, but fewer options, have options that have a a a consistent capability regardless if you look at it through a web browser or a desktop client.

As part of this, you will see some new technologies joining into the in Touch HMI.

You also see some of the older technologies leaving.

But we are very much committed to protecting your investments in the applications you built, into the skills you have acquired to to continue that path forward and have incremental value on top of what you have today.

So there there will be a lot of different things. I'm going to touch on a couple of aspects around common visualization, around ease of use, ease of getting started.

So let's get started with getting started. Right? The first thing we often do is if you want to try out an HMI product, you want to download it and install it.

We have had a interesting journey. As I mentioned, we started off somewhere here with the floppy disks in the early nineties, but we kept that paradigm. Right? It's always been a disk, a floppy disk, a half inch disk. You we went to optical disks. We went to virtual disk, like zip files and ISO archives, but still a disk.

We have also increasingly complex post install configuration that you need to do to sit through after you install the product, which adds to a very kind of complex journey before we actually can start to try the software.

So we want to embrace, you know, this being digital and look at different patterns on how to deliver the software.

One of the things we already done is just access the software. You can go to the product page on aviva dot com today, download InTouch from there, and start to try it out.

Now it's still a, whopping nine gigabyte ISO file together with system platform and a bunch of things, which makes for a large download and and, of course, exposure to a little bit more complexity in terms of what you pick to install and and and those things.

But we're addressing that next. So this is available today.

But where we foresee going and mind you, this is a prototype, so it's not a finished thing, but actually working software today in our lab, where we download a small, in this case, an eight gigabyte oh, sorry, eight megabyte.

We shrunk it. Right? It's eight gigabyte today, and now it's eight megabyte. You install that, you run that, and you pick what to download and install.

So if I if I'm connected to Internet here, I just hit install, and it will download and install simultaneously just the pieces that I choose, not the full range of of operations control software.

And, of course, we will support here also to kind of predownload a a installer that I can bring with me to an offline computer to install it without an Internet connection.

We will also support your automated installation or silent or unattended install by scripting, by just calling this executable and telling it what you want to install.

As as part of that ease of use, as part of the the expectations we have today, my monitor went blank here, we, we also support dark mode. So we follow the user preferences in the operating system. If I prefer to light mode, it follows that. If you have dark mode, it follows the dark mode. Our internal joke there is that we prefer dark mode because bugs are attracted to light.

Don't know if that holds true. Now something very interesting here is that after that install, which is about a five minute process, we jump directly into developing an application, directly into what we start to refer to now as the the InTouch h IDE.

And, I can directly start to build content and drag data into this to to build an application.

We merge in the application manager of InTouch so that you don't need to jump through multiple utilities until you get to to to development.

Alright.

We also recognize that we need to manage updates in a better way. So, still a bit of a conceptual design here, but you go into the same installer again, and you can check for updates.

If new patches are available, you can install them from there through this interactive user interface or, again, through downloading it and bringing it with you to the offline computer or, by automating this with shell scripting or or other IT tools.

Now, of course, once you have acquired a software, you installed it, you may want to have some guidance.

We are embracing an openness in terms of of much of this, not only putting the installer publicly on our website, but we have also recently moved the entire documentation to the common documentation portal of Aviva at docs dot aviva dot com.

It's there already for the twenty three r two version, and this is the focal point for documentation moving forward. We'll still install documentation with the products, but by having it online, we can also have a more living documentation. We can start to enrich this with more immersive content like how to videos and and and more things which would be problematic to install and and carry with us in in the installer.

So we're very excited about that, and, we're also working on a deployment guide for InTouch, which will be published through this site, in the next month or so.

You need further guidance on that. Well, beyond documentation, we have our online community, Heroes HQ, where you can interact with peers across the ecosystem.

Aviva is very active there. We have system integrators active there, customers active there, talking about troubleshooting, best practices, or whatever topics that that may come up.

From the Heroes HQ portal, you can also access the learning bytes, like micro learning content around in touch HMI, how you use it for different particular features and purposes.

So all of that is available openly. There's no paywalls. There's no registration to go through to access those kind of things. You do need to register if you want to comment or or publish things in this forum, but you don't need to register to to access it.

It. Same goes with the documentation portal. It's just wide open. You don't need to log in. You don't need to speak to an Aviva salesperson to get access to it or nothing like that.

Now once once you're in there, what is the typical thing you you do? We have different workflows. I mean, some people prefer to start to create a graphic.

Other prefer to pull some data into an application.

Now accessing data, we have recognized, is a little bit awkward workflow today involving multiple tools and utilities.

We're bringing all of that into the InTouch IDE and, subsequently, also into the system platform IDE so that I can manage my data sources there.

When I arrive into the IDE here, I can click a button to say that, hey. I want to connect to a data source. Is that an OPC UA server? Is it the broker for MQTT? Is it the Siemens PLC or Schneider PLC or whatever? You just pick whatever you want to connect to.

With if if that protocol supports discovery, it may actually say that, hey. I found this three OPC UA server on network. You can just pick one of those, and you're directly immersed in that that data model. You can explore that data model, pick whatever you need, and then drag that into your application.

Bits and pieces of this are already in Intacct twenty twenty three r two, but we're refining this to to also support QDTs and structures.

And we are also integrating not only OPC UA, which is there today, but MQTT.

We will make it easier here also to publish out through MQTT and the an OPC UA.

You may have heard from John this morning that these are our areas that we're focusing very much upon, but we're building it in such a way that we expect, subsequently to also plug in other browsable sources, PLCs, vendor specific protocols, and and other open standards.

So you can very rapidly go from hitting download on the Inter product page on aviva dot com until having live data in your application.

We we aim for that to be around five minutes.

Now, realistically, perhaps in the first couple of releases, we will be around ten minutes, but five is our goal.

And and, of course, also to bring these things together is not about only configuration. We want to have a a clear indication. Am I connected to a data source that I just configured or not? What's going on with it?

Can I just drag a few items into a watch window and see if I've referenced it correctly? Is my subscription working? Have direct feedback on this without having to go back and forth and look at log messages and environment, you can just put those things on a work window and and see how you go. Of course, build out a little bit more views.

And and I recognize we need to offer perhaps a way to save and open different windows there also.

So that drastically reduces the amount of work you need to do to get to a point where you have live data in your application.

Now there are many more enhancements to what we're doing. These are some of the more visual items.

But on the back end of this, we are also doing a lot of refactoring on the underlying services.

Intel today is a very monolithic executable.

If you want it to run faster, you need a faster CPU.

Now, I think many of you are aware of the fact that the CPU industry is going in a different direction. We're no longer going for faster and hotter CPUs. We're embracing parallelism instead with multiple cores, slower, CPUs.

If you have a new laptop, you may recognize that you have these eco cores that run slower than the performance course to just consume less power.

We are working on making InTouch a microservices architecture to scale such a way. We're introducing power consumption as a performance metric in our labs to be able to to to address it.

Part of this is also that we make it into a sixty four bit process, which allows us to address some different things, new data types with higher resolution. We are addressing also this y two k thirty eight time issue. That's a I guess most of you were there for the y the the y two k, the backfill.

We have another one on the horizon. If you if you're not aware of that in two thousand thirty eight, the the thirty two bit time representation will kind of overflow, and we need a sixty four bit number to do that, to keep track of time.

Now many thirty two bit systems already have ways to deal with that today, but we are covering this by just moving into a a sixty four bit architecture. And that could be good to know because you may see requirements from your internal IT teams. Or if you're a vendor, you may see this in procurements right now that you need to have a plan to deal with this already today even though it's still a few days or years into the future.

As we're reworking this, we're also trying to adopt more modern terminologies.

We have some legacy vocabularies today in our HMI offers with phrasings like discrete instead of a Boolean. We find that, increasingly, people don't really connect with that. They they have learned a different vocabulary before before they even see our software. So we're moving to call a Boolean a Boolean.

We are moving from real to float. We're working calling it string instead of message.

And, of course, adding a few data types to that. We are working right now on double, and Jira is still out if we call this elapsed time or duration, but, basically, a time span, type. And there's more to come there also as we're driving further alignment with external standards like OPC UA, which has things also like byte string, image, audio, those kind of aspects.

So there there there's much more more to come in in terms of that also.

Some of the some of this is, of course, under the hood, but some of it also opens up to new development capabilities.

Now the final piece of this is around the visualization. And, hopefully, many of you recognize this journey that we we started to to talk about a few years back, what we call the the operations day in life, how, throughout the workday in operations and takes you to different locations, working together with different people, using different type of devices.

Sometimes you're in front of the HMI, which is bolted onto the machine on the planet floor, but sometimes you may be, in the metro on your way to work. You may be in the cantina just with your phone having access to things. You may be in a centralized control room with a lot of different screens and devices.

But throughout this journey, we want you to be able to access information from the HMI in a consistent way.

Just pick up whatever device that is nearest. If you have access, you can access that information.

So so going from the traditional presence where where you're in front of the machine with HMI, we want HMI to be reachable also when when you're, let's say, within reach and also make the same information available when you're out of reach. You're connected from a different network.

And, obviously, this this operator personality doesn't work in a vacuum. There's other people around there also, and collaboration requires, I think, unambiguous information.

You need to not only have the same data, you also need it to be visualized the same way. So when when operators say, do you see what I'm seeing? He can be confident that a lot of people say, yes. We see exactly what you're seeing, pixel perfect representation, of what you're seeing.

So there's several things we're doing around that. The first is one graphics technology. In our HMI offer today, we have multiple different technologies. As I mentioned, drawing a rectangle on the screen, that's different ways to do that. Making trend tools, different ways to do that. So we're focusing around industrial graphics, and we're migrating our legacy graphics onto industrial graphics. For InTouch, that migration from legacy graphics to to industrial graphics is a very high fidelity, has been there now for close to ten years.

But we're focusing on industrial graphics, and we're leaving some of the older technologies behind.

We also have one rendering mechanism to make sure that that graphic that I created, it looks exactly the same on any of these devices for all of these different people.

And, of course, this a a key value of this is also as you start to grow into other Aviva solutions, if you if you plug this into a supervisor's SCADA also with system platform, that symbol will be reusable there. It will look and behave exactly the same. If you draw that you pick that symbol up and and and stick it into our cloud visualization, it looks the same there. It behaves the same there as well.

Now industrial graphics has been around for quite some time, and there is a really powerful visualization technology. These are just some examples that I've threw together from some demos we have had over the years. It's actually the same application. It's just gone through different generations of design, design philosophies from that rich, artistic, skeuomorphic representation to the various felt, situational awareness graphics, to a more, let's say, Google material like thing onto a more dashboard or or dashboard oriented thing.

Right? So industrial graphics allows you to do a very wide range of things. So, it's a fantastic technology for us to convert on. We also support with, industrial graphics a designer and developer collaboration.

We introduced recently an SVG import, which allows us to take designer output from tools like Figma, Adobe XD, and other design software, and just drag that directly onto a industrial graphic surface and apply animations to it.

So we we reduced that that the turnaround process between the designer and and the developer also. And and involving designers in also this industrial context is incredibly valuable in terms of promoting perception of information, quick understanding of information, and how we can get from vast datasets to actionable information.

So in in InTouch, we are changing.

I I mentioned the InTouch IDE. We cannot call it WindowMaker anymore because there's actually no windows here anymore. We're now talking more about pages As we move to a more web oriented architecture, more web oriented terminology, we draw those pages directly here in the Intouch IDE as an industrial graphic.

The industrial graphics are now promoted to be at the at the forefront of the IDE, as we replaced the the legacy graphics.

And and we can draw that directly on tabs here in the surface. We can add custom properties and scripts as usual to it.

And adding to those pages, we're also introducing the layout capability from the OMI framework so that I can organize these these pages into particular layouts and things and and drive things like footers, headers, menus, slide in menus, from all different directions.

And, of course, that I can develop all this stuff, take that with me into a system platform application, or take what I have in system platform and build out an HMI from it also.

So these are some quick early previews of what we're working on right there. Obviously, if you go hit run time now, you will end up in a in a kind of web based client server experience, instead of the traditional desktop experience.

And we as part of this, we are dropping things like the legacy graphics, ActiveX controls, and some other technologies that had been on their way out for quite some time, but now we're taking that leap forward. And again, the legacy graphics, if you're still using those, those convert very nicely into industrial graphics.

But it comes back really to our idea around this being portable across everywhere. Consistent user experience. If I'm looking at the same information through one lens or another, I see it consistently.

My colleagues see it consistently. If my workday takes me across these different areas from the operation center out to the machine itself or if I have just mobile access on my phone, I can see it in the same way. Very important. And from a a application and life cycle management perspective, all these things, the graphics and content that I build is pluggable across this entire span, with different tiers of of Aviva products.

Finally, with this, of course, you need to license it. At some point, we also like to get paid. So, but we are relaxing some of those commercial constraints. Right?

No license. If I'm trying this out, I just downloaded it off the Aviva website. Do I need to talk to a salesperson just to try it out? No.

Starting with our our recent patch, and it's more formalized now in the service pack we're releasing in a few weeks, the development environment no longer requires a license.

So that makes it so much easier to get started. But also for existing customers, if you're doing field services work, you no longer need to go on to the plant floor and plug in your development license and and all this back and forth with activating the deactivating licenses.

You can just run the if you're authorized to do so, you can run the development tools, make changes, try those out, and then put that into production. The the runtime will actually now run without a license.

In the past, you could run-in demo mode up to sixty four tags. Now, Intouch runs for free up to sixty four tags. If you want to think through with this at home and apply Intouch or HMI to to some of your home automation, go ahead.

But beyond sixty four tags, it runs in demo mode and will stop every two hours, so that you can actually develop and test the full application without having to talk to to us for a license about it. Now when you put it into production, obviously, then you need a license. We have made significant changes there as well to accommodate the the the more contemporary needs.

We offer unlimited licenses, which bundle up with different tiers of of of other Aviva software. But the fundamentals of this is that you can have a license today which is completely unlimited from tags standpoint, unlimited Windows, unlimited clients.

If you're doing the standard edition, you have unlimited web clients. If you're doing the professional edition, you have unlimited remote desktop clients.

We're bundling historian. We're bundling reports and things, and it's really a fantastic offer. Now I see I'm slightly over time, so I will just try to wrap up here.

Next year, we aim to release Intouch twenty twenty six, which makes this big leap forward.

There will be a minor release for Aviva Edge with some customer commitments, security enhancement, and things. But after the twenty six releases, we are working toward a unification of these two products. This may take us a few versions, but we make sure that you can stay where you are today, without any disruptive changes. Right? So the twenty three r two versions will be a long term servicing channel with extended support lifespans, so that we can start or or our ecosystem can start to to consume these changes at your own pace.

I also want to highlight that the InTouch four system platform will be kept as is.

So all the changes we're doing to the HMI will be for standalone HMI. If you're using InTouch as a client to a system platform, it will be put into maintenance mode. It will continue to get bug fixes, security enhancements. We're not building any new features for that. OMI, the operations management interface, is now the the primary client for system platform.

And we will put our efforts into enhancing that migration capability from InTouch Force system platform to OMI.

That's where we invest in terms of system platform. But no new features for InTouch as a client to system platform.

And we'll keep InTouch Force system platform around for the foreseeable future.

I guess we will just extend that forward until we have a very small step into the operations management interface.

So, it's absolutely not going away, but we have just put a stop to it in terms of new features. We will say that if you're doing system platform for new projects today, use OMI.

If you have an existing state of InterForce system platform, you can continue running that and we will close the gap in terms of moving you forward.

With that, I need to wrap up and, I guess, hand over the stage to the next speaker. You can hear also more about our HMI offer at Scott's session later today, where he goes into the details about what we did recently in terms of features. I stole a few of his slides and and some of his thunder here also, but, there's there's many more great things there to to see. So with that, I will, get off the stage, but I'll be around for for for questions. Thank you very much.