Presentation: AVEVA Roadmap: AVEVA Operations Control, an evolution in HMI/SCADA

2024 - AVEVA World - Paris - HMI/SCADA

AVEVA Roadmap: AVEVA Operations Control, an evolution in HMI/SCADA

So I'm Elliot Middleton and I'm the product manager for, traditionally for Aviva Insight and Aviva Historian. I've had those roles for decades. And so most of the the things that are in the historian you can blame on me and that includes the problem. So I'll I'll own that. And happy to talk to you afterwards, hear about needs that you have, challenges you're having there, or, about the, the talk today. So with that, we'll go ahead and get started. I am based in the US, if you can't tell. I originally spent my time, at in the company in Lake Forest in the California office there. And more recently, started working from a home office in Texas. So today, what we're gonna talk about is a little bit broader than the historian and insight. It's really about the the parts of operations control that are beyond just the pure HMI SCADA. One way to think of this if I use an analogy of Microsoft. So if you think of Office twenty nineteen, twenty sixteen versus Microsoft three sixty five. So Microsoft three sixty five has a bunch of extra stuff in there, it includes office but has extra stuff. So, what I'm gonna be talking about today is the extra stuff and a little bit of what's in that kinda that core. So with that, here's a kind of a visual representation of that. The bottom pieces here, I guess you can't see that, are the on premises components and then the, purple colored ones are the, software as a service components, the SaaS components. Including connect. And we'll talk about each of these, at least briefly focusing on the the on premises pieces. What we hear from customers and from industry experts is that one of the big challenges that you have is access to useful information to help drive, solutions to problems. Better, decision making. And so one of the things that we've done is tried to address that in part with Aviva historian. And the way we've done that is to deliver historian into more places. So it's part of operations control, it's part of system platform, but we've also included it with InTouch Unlimited under the flex program and more recently we've added it to the on or the excuse me, the perpetual version of InTouch Unlimited as well. You'll notice here that some of these are actually, unlimited and unlimited has a footnote. So it's no license enforced tag limit. It's strictly the architectural limit of two million tags. Which is more than enough for most of the applications we encounter. But we wanted to make this, more accessible, for you to be able to leverage. I often get the question, well what about pie? Now, pie is more than a historian. It does include a historian, but it is more than that. In particular, the asset framework, asset analytics, event frames, components are, kind of extra value on top of a historian. It's a very well established solution. It's been around for a long time, has a large install base. But it's particularly well suited to these enterprise type applications. And that's in part because of the things that are on top of the archive. In the case of Aviva Historian, we also have a well established presence and a large install base. And these tend to be smaller applications that are more intimately tied to the HMI SCADA. And some of that's the level of integration that we have, some of that's things like the alarming event history, that we have that make it a a natural extension of HMI SCADA. I often get the question, so what are you gonna do about these two? And we're gonna keep both of them. Now the one change that that we made in the strategy for Aviva historian after the the merger with OSI is we used to have this thing that we call the enterprise edition historian. Anybody familiar with that? Yep. So we still have that. We renamed it so it's advanced. But same capabilities. We're gonna keep that capability, but we're not gonna be investing a lot in that. I'll be honest. We are gonna be investing more in how do we get information from here into pie, and probably more importantly more of a focus into our cloud solutions in Connect. And I'll say more about that in a few minutes. The real themes that we have for Aviva Historian are really around, that connect integration. We'll elaborate on that and making the information more accessible. I mentioned earlier some of that accessibility being availability of the historian, but it's also how do we make the information that is there more readily available to people. Some of that is, the browser based access that we have. And we also wanna make it more interesting, more relevant to people, to a larger audience. So it's not just the the few people that know how to use the historian in detail, but perhaps a casual user. And broaden the interest add make that information more valuable. Some of that summary information, some of that requires adding context to the information so it it's more meaningful. And then we also wanna do all of all of this in a way that it takes less work for you to do it. So easier to install, easier to consume, easier to learn, all those kind of things. So I'll elaborate on all of these points. The the real core technology we have for the browser based access started as something at the time we called it Wonderware online, now we call it Aviva Insight. And then we've adapted that to use on premises as part of what we now call Historian Client Web. And then more recently we've, taken that same technology stack and adapted it to, Connect visualization services. Now you'll you'll notice the the black triangle there, this actually has two themes, a light and a dark theme in connect visualization. We haven't adopted the the dark theme option and the other two incarnations but we expect to do that, sometime next year. So it looks a little different but under the covers it's the same core charting, technology, same widgets and we get a lot of leverage out of that and a lot of consistency. When we originally developed this, we had what we now call the classic user interface, in insight and Historian Client Web. That's kinda the default in the current shipping versions of Historian Client Web. And we are gonna be, retiring that in the twenty twenty six release. Even though it's called twenty twenty six, it will be next year, in the second half of next year. Part of the reason is we've reached or pretty close to reaching feature parity in what's the replacement which is the modern experience. And this modern experience is what we actually have across all three of those platforms that I just talked about a minute ago. One thing that we are adding in a service pack that's coming out into this month is, one of those kinda minor detailed gaps is the ability to create a chart all through a URL. That makes it easy to integrate with other systems to invoke, the trend chart, for example, or a column chart and preconfigure it, for that particular application and that's coming in, s p one. One of the big things that we added in historian twenty twenty three, a few years ago, is ad hoc expressions. And this is consistent across the on premises historian as well as insight. But it's real simple to add, an ad hoc calculation. This example, I'm gonna calculate a control error. So I find the difference in the set point and the process variable. And there I have a new pen in bingo. So super simple to do for an end user. You don't have to have any elevated privileges to do that. In this particular case, maybe I want to don't want the instantaneous one. I want to to dampen that a little bit, and so I'll add a average calculation. And I'm gonna add a one minute average to that, control error just to smooth it out a little bit. Save that change and there we have it. Super simple to do, try to make it easy to to explore. It's a syntax that's pretty consistent with Excel, so it should be familiar to most people. We have a rich library of expressions, functions in this expression library. We've added to that with each subsequent release the black text is the original. And then, we added some in the r two release. We have some more being added in the upcoming twenty twenty six release. And, it's not really a function but we also have some some limited string support. Particularly useful in an if condition. So you can use it in the logical part of the if or in the results. Those string literals will be useful. And we have some other ideas and if one of those is for example, these aggregate functions are all based on a time interval. Hour, day, five minutes in this example. One of the things that we're looking at doing is is expanding that to be event based. So a batch ID, recipe step, a logical expression as you see in the last example. One brief explanation on my terminology. I'll talk about ideas, things that we wanna do, and plans. And the big difference in the two is plans have assigned schedule, budgets, and staff. Ideas don't have those things. And so we are a little bit further along in that we've actually done some of the work on this. But we're we're not yet committed to a schedule. But this event based, expressions are likely to make it in the twenty twenty six release. One thing that we're definitely doing is, addressing some performance challenge. So one of the one of the problems with these expressions is we've seen people using them pretty widely, pretty aggressively. And in particular, we've seen a lot of usage of, time based aggregates. And over longer time periods, this, because these are calculated ad hoc, it can be a lot of compute. So let's take the example of a one second value. It's stored once a second and I want a daily average. That's eighty six thousand operations in the simple case. Right? They do that for a few days and it gets to be a lot. Now, we actually have that value pre stored and calculate calculated and stored in what we call the auto summary system. And we'll leverage that in in a lot of the retrieval notes. We don't currently leverage it in expression. And so one of the changes we're gonna make is, to start to leverage that dollar summary we'll see in the testing that we've done we've seen thousands of times, performance improvements in some cases. Depends on the expression. And on the data rate and a lot of variables. But it can be a huge performance gain. Now it doesn't apply to everything. So for example, here's some expressions that it won't work with or it doesn't help. So the expressions still work, the numbers will be the same, but the performance isn't gonna be any better. For example this one is a too small of an interval. We do up to an hour. So if it's an hour or longer it may be useful. Here what I have an expression that I'm evaluating and then doing the aggregate on. Doesn't help with that because we haven't precalculated that result. Here's one to be mindful of. So if I put the the division inside the parenthesis it's not gonna benefit. But if I do it like this and move it outside, it will. So just some things to keep in mind, once we release that. And this is definitely gonna be in the next release. We're gonna deliver it online at end of this month. We're also working on, how do we get data into Historian Better. So one example is InTouch. We do have this ability to push historical data and tag creation into, historian from in InTouch. We have a a tech note for how to do that with a redundant tag server configuration. Be aware of that. But one of the things that we're gonna add is support for partner historians or redundant historians. So I can send that same data to two destinations. An explanation here on my notation here. So the the black dots are things that we've already released. The green plus is something that we're adding in the near term. So for system platform, we're going to be pushing asset type. So we already push assets based on the galaxy model. We're gonna be pushing the template derivation view essentially into historian. We'll be able to leverage that for search, and then we'll also be able to push it in, some other places and we'll talk about in a second. Have plant SCADA connectivity that's gaining Windows authentication to the plant SCADA system. Possibly some other things there that we're gonna add. And then, we can today collect from MQTT sources and push that into the historian, but you have to configure it item by item. One of the things that we're adding is gonna be the auto configure. So you give it a topic with a a wild card in it and you'll just pull in all those tags and start, populating the data as well. On the outbound side, we're we have a service pack coming out at the end of the month. And we're gonna be adding the asset model into connect data services. So today we push tags. That's available. We have some minor tweaks to how we're doing that. But we'll also be creating the asset model based on the galaxy model view. That's coming in s p one. In the next major release, we'll also be pushing the asset types. As we get those into the story, we'll be able to replicate those, into data services. Here's what it looks like in s p one. So here's the model view within the IDE over here on the left. And if I switch over to the SMC and configure replication from the historian, I select the destination type as connect data services. Register, I get a login challenge for connect. Log in, and then I'll select from the available name spaces in data services, pick one of those, and that's where I wanna register this. And now, now I've established a connection to data services. I do have some naming conventions or a naming rule for generating tags and data services. I can change the default, but I'm gonna keep that. And now I'm gonna add some particular tags that I wanna send to data services. This part of the workflow is is consistent with what we released two years ago. So if you've used that, it that part hasn't changed, but the results have changed a little bit. I can edit the destination tag name here. I'm gonna keep the defaults there. And then once I, commit those changes it starts sending. And if I switch over to data services, I can see those streams created using that default naming convention. And if I switch over to the asset explorer, you see the assets that were automatically created from that model view. And they have the properties assigned. I'm gonna pick this is supposed to be a boiler. I'm gonna pick the temperature and pressure. Change the time period here to the last five minutes, and you see there I have data. Now I can also use the backfill. So if I want, I had two years of data on that in the Veeva Historian, I can send that, take a little bit of time, but that'll work. And then if I switch over to connect visualization, see that same asset hierarchy is recreated here. And we have a default view for an asset in, visualization. This is that default view. Show some of the static information and then, we'll call a status board with the the time series data. You can customize this to your particular application but that's what it looks like out of the box. It's kind of a high level view of the, the road map. So we have had, some patches recently. We have the service pack coming up soon. Another big change there is the dot net run time we're using. The plant SCADA connector update I mentioned is coming out soon, shortly after that. The ability to send data to con to, connect data services and visualization, we're gonna break that out of the embedded, the way it's embedded in Historian so we can deliver new functionality easier on older versions of Historian, and we'll be doing that. And then, as part of ops control twenty twenty six, we'll be doing more things, around expressions, may do some more around, alarm analysis and visualization as well. And, and then, some of the other items I talked about there. A lot of ways to get information out of the historian, historian client desktop, historian client web, the excel add in, and Aviva reports for operations. I'll come back to that in a second. Power, Power BI will work with historian, but Power BI is particularly well suited to multi dimensional data and historian's not really a good multi multi dimensional source. So you can get the data but it's typically not as useful to pull into Power BI as you might like. Talk about rev Aviva reports some more. So some of the same type of aggregates that that I can use in Historian Client Web, I can use in Aviva reports. Aviva reports is particularly well suited to kind of a paginated format. Anybody still using paper reports? I expected somebody, but it but it's at least well suited to a PDF, and maybe you put it on a piece of paper too. Good for email distribution of those reports as well. Just a a scheduled static report that you can archive. It's great for that. There are also some special functions in Aviva reports for doing a set point analysis, alarm analysis, SBC, and we've add some some richer capability in the batch area. So over here on the left I have event frames out of pie and we we've mapped those into kind of a hierarchical model of a batch. That's a new feature in reports. So I can have different levels for the batch, for the unit procedure, etcetera. And then I can also create, import event frames from pie for that and then create reports that use what we call, clusters that are specialized for each of those levels. So the the layout for unit procedure is different from a phase, etcetera. We are going to be, adding the ability to publish a report from Aviva reports into, Connect. In this particular case, Insight. And that publishing will initially go into the Aviva drive, that shared folder that you have in, Connect. And then we'll be expanding that so it's browsable for within inside and Connect visualization. We're also gonna be leveraging the single sign on capability we have in Connect for the connected experience, so we can use that in Aviva reports. High level roadmap here. The event frame support, nested batching, that's, already released. By the end of the year we're gonna have the publishing capability to connect and the single sign on. And then, next year we'll be adding, kind of the run time hosted in connect. Design time will still be the thick client that we have today, slightly updated, for the authoring, but then I can publish reports to the online solution. A lot of focus to date on ROUND Connect has been, on the data side. But one of the things that we're trying to do is, expand the access to that data and then use Connect for more. We'll talk about both of those. We've been on a journey when it comes to the this hybrid SaaS, for operations control. Started as standalone insight on premises historian that could integrate. And then when we introduced operations control, we really had an integrated solution. Now, this doesn't show up here but imagine that there's a a gray rectangle behind this part. It's just not showing up, contrast doesn't work right. But, operations control going right, it is, our vision is to add more and more SAS components to operations control. Started with insight and teamwork. We're adding the single sign on. We're adding, connect data services support. And then, this last thing, we're adding some integrated models, that to simplify the workflow for teamwork. Then Aviva insight is really focused on this accessible information, particularly a lot of people are using the mobile device access for that. Just to make that detailed operational data available to a larger audience. And then it's, accessible in several ways. The kinda ad hoc access. We had a problem yesterday. I wanna find out the root cause and try to prevent it from reoccurring tomorrow. Create dashboards from that. And then we also have OEE performance, in the utilization area. Automated analytics. So you just push the data and we start doing anomaly detection and reporting that. And then for more sophisticated applications where you wanna invest a little bit engineering expertise into that, we have the guided analytics option. And then more recently, if you're in John's presentation earlier today, he mentioned, that we're also expanding that to include, connect data services. And one of the big advantages in connect data services is the idea of communities. The idea to to share subsets of the data, subsets in granularity, time frame and, tag selection. All those options, with a larger audience. And that might be an internal audience for other applications or it might be, partners like supply chain partners that you wanna give access to subsets of that data. And the other big advantage in data services, the availability of advanced analytics. When guided analytics, doesn't really meet your needs and you have the expertise, advanced analytics is a a great option. In the area of user identity, kind of the typical model is people have a Windows Active Directory for a at a business layer. Maybe they federate that with Microsoft Intra or formerly Azure Active Directory. But typically on the supervisory network you've got a different identity. Maybe these are, trusteds in some manner but that but it's a different identity. Maybe you even have a third on the DMZ. And that's the traditional way that we've deployed applications. Many of you are probably doing that. With the twenty twenty three r two release, we added an, the option for a single sign on that's federated with our, Aviva ID. And I can use that consistently across all of these domains. We even have a utility DMZ Secure Link that lets you, that helps bridge that DMZ case. We'll also use that for, some not quite all of the entitlement. So as an alternative to installing local licenses on a local license server, you can use this entitlement enabled through Aviva connect. Let me show you what that looks like. That single sign on across multiple applications within system platform or operations control. So I can log in when I launch the, system platform IDE, for example. And you'll see in the upper right hand corner this, the identity and that's my identity. And if I, switch over to uh-oh. I get a little bit of additional detail there in that back backstage if I launch, OMI. I don't know if you noticed it but that login challenge showed up and then disappeared automatically. It automatically signed me in to that same identity. Here I select a trend and it's authenticating against the historian, using that same identity. Same thing with the historian client web and same identity. Now one of the gaps in this initial release is works great as long as you have that active connection. But if you lose the connection, to Aviva Connect, then, you couldn't log in. So one of the things that we're doing is adding this intermittent connection support and that's coming out next year. So here I can have kind of a parallel on premises active directory identity that has the same rights and entitlements available even in that kind of disconnected intermittent connection scenario. And then all of the applications have this kind of consistent banner up here which you may not be able to read. But basically says you're disconnected, you're able to still use the software until whatever the end time is. Okay. Our goal is to use more and more of this cloud enabled functionality in the on premises offers. So we've done some with identity with some with entitlement, some with the models, and we're continuing to expand this. So over the next few years expect more and more of this to get filled out. If you use Development Studio, today you can get access to, some of the entitlements, software downloads. But we're adding, later this year we're gonna add the ability to upload a Galaxy backup. So when I upload that it's a it's a archive repository for that backup and I can download it, restore it. But there's more I can do with it. One of the challenges we've had is we wanna make sure it's easy for people to leverage configuration across the portfolio. So the first installment of that is being able to leverage that same model to populate teamwork. So you see one of the options here is to export that model or I think publish is the word we use. Publish that model to Teamwork. Now, we expect most customers aren't gonna have one to one correspondence between a Galaxy model and a Teamwork model. So we wanted but we still wanted to make it easy to leverage the existing model. So the approach we've taken here is this side by side. I can select items from the left, the galaxy model, drag them over to the right to populate the teamwork model. So I can select the subset that I wanna map. Drag those across. And this does save me the typing and the tedium of that, but it also maintains that connection between them. And that I can leverage, elsewhere in the solution in the future. And then, I complete that, didn't have the errors, and, now if I launch teamwork and, select the model here, There are those, that equipment that I created, automatically based on the Galaxy model. We do have some entitlement access. So currently you can access downloads and, licenses. Actually the license here basically takes you to a help page today. But we are expanding that so you actually download perpetual licenses, as part of your, operations control entitlement. All from the same place. Teamwork. So anybody familiar with teamwork? Few of you. Alright. Real brief explanation here. So teamwork is really focused on how do we organize people to solve problems in production. Particularly with with equipment. So it's about the communication side of that. How do we communicate the problem? It's about, capturing knowledge about how to solve problems and, creating a catalog of that. And then also tracking the training, who's, learned how to solve these kind of problems, maintain this type of equipment. Who needs to be, needs a refresher. And then when there are particular issues, marshaling resources to solve those problems. That's the real focus of teamwork and we wanna jump start that with this model transfer that I I talked about earlier. We've we've made some improvements over the last, few months in it's an online solution so we've delivered those. Some usability improvements. We're gonna have this, model creation that I mentioned and before the end of the year we're gonna introduce, the single sign on so it's a consistent sign on across connect including teamwork. Last component of the portfolio I'm gonna talk about here briefly is Integration Studio. It's a virtualization solution where we make it really simple to create, multi node configurations particularly for development and testing of, a distributed application. And, it includes the entitlement, the installation, our base images based on released versions of the software and, let you quickly stand up configurations, for development and test. We've made several changes over the last, several months. Added images for the new r two releases, some usability improvements. Next year we have planned a more sophisticated configurations with things like multiple NICs, including a domain controller so that I can leverage that across multiple projects and, being able to snapshot those. They you have to do it inside the VM and it's a little bit harder to to manage. So, just a reminder, this is the the components that we talked about as part of this overall operations control offer. One thing to keep in mind and people been hearing about heroes HQ this week, several of you. Great. Really encourage you to leverage that both, to learn from what's available there as well as share some of your expertise, there with other users. It's, got the same type of forum capability we've had for a while but also has a lot of videos, training, a lot broader information and, really want you to be able to take advantage of that. There are a couple of other sessions later on this afternoon that that are might be relevant if you thought this was helpful. Wanna call attention to those and with that, appreciate your time and attention. Thank you very much.

It’s time to reimagine the industrial environment and empower your workforce to reach their full potential. Learn how innovative software specifically designed to connect workers efficiently, enable data-driven decisions, enhance performance through effective visualization, and digitize knowledge, will help identify value capture opportunities and boost productivity. Join John Krajewski, as he walks through how AVEVA’s operations control portfolio empowers a day in the life of an operator and how AVEVA technology has and will continue to support your journey toward operational excellence.

Download Presentation

Company

AVEVA

Speaker

John Krajewski

John has 28+ years of experience in industrial automation and control systems. After acquiring a bachelor’s degree in electrical engineering from the University of Delaware, John began his career working as a Control System Engineer in the potable water industry. Subsequently, John worked as an Application Engineer for a System Integrator who primarily focuses on the pharmaceutical and biotech industries. He joined Invensys Wonderware in April 2000 as a Senior Application Developer in the Product Marketing Department. Shortly thereafter, John assumed the role of Product Marketing’s Functional Manager of Infrastructure. John Spent 5 years as a Domain Architect with responsibilities for architectural and functional definition of InTouch and ArchestrA technologies. Since then, John has served in multiple Product Management roles for AVEVA HMI/Supervisory Control products.

Session Code

AW24-HMI-D2-SESS-350

Transcript

So I'm Elliot Middleton and I'm the product manager for, traditionally for Aviva Insight and Aviva Historian. I've had those roles for decades.

And so most of the the things that are in the historian you can blame on me and that includes the problem. So I'll I'll own that.

And happy to talk to you afterwards, hear about needs that you have, challenges you're having there, or, about the, the talk today.

So with that, we'll go ahead and get started.

I am based in the US, if you can't tell.

I originally spent my time, at in the company in Lake Forest in the California office there. And more recently, started working from a home office in Texas.

So today, what we're gonna talk about is a little bit broader than the historian and insight. It's really about the the parts of operations control that are beyond just the pure HMI SCADA. One way to think of this if I use an analogy of Microsoft.

So if you think of Office twenty nineteen, twenty sixteen versus Microsoft three sixty five. So Microsoft three sixty five has a bunch of extra stuff in there, it includes office but has extra stuff. So, what I'm gonna be talking about today is the extra stuff and a little bit of what's in that kinda that core. So with that, here's a kind of a visual representation of that.

The bottom pieces here, I guess you can't see that, are the on premises components and then the, purple colored ones are the, software as a service components, the SaaS components.

Including connect. And we'll talk about each of these, at least briefly focusing on the the on premises pieces.

What we hear from customers and from industry experts is that one of the big challenges that you have is access to useful information to help drive, solutions to problems.

Better, decision making. And so one of the things that we've done is tried to address that in part with Aviva historian.

And the way we've done that is to deliver historian into more places. So it's part of operations control, it's part of system platform, but we've also included it with InTouch Unlimited under the flex program and more recently we've added it to the on or the excuse me, the perpetual version of InTouch Unlimited as well. You'll notice here that some of these are actually, unlimited and unlimited has a footnote. So it's no license enforced tag limit.

It's strictly the architectural limit of two million tags.

Which is more than enough for most of the applications we encounter.

But we wanted to make this, more accessible, for you to be able to leverage.

I often get the question, well what about pie?

Now, pie is more than a historian. It does include a historian, but it is more than that.

In particular, the asset framework, asset analytics, event frames, components are, kind of extra value on top of a historian.

It's a very well established solution. It's been around for a long time, has a large install base.

But it's particularly well suited to these enterprise type applications.

And that's in part because of the things that are on top of the archive.

In the case of Aviva Historian, we also have a well established presence and a large install base.

And these tend to be smaller applications that are more intimately tied to the HMI SCADA.

And some of that's the level of integration that we have, some of that's things like the alarming event history, that we have that make it a a natural extension of HMI SCADA.

I often get the question, so what are you gonna do about these two? And we're gonna keep both of them. Now the one change that that we made in the strategy for Aviva historian after the the merger with OSI is we used to have this thing that we call the enterprise edition historian. Anybody familiar with that?

Yep. So we still have that. We renamed it so it's advanced. But same capabilities.

We're gonna keep that capability, but we're not gonna be investing a lot in that. I'll be honest. We are gonna be investing more in how do we get information from here into pie, and probably more importantly more of a focus into our cloud solutions in Connect. And I'll say more about that in a few minutes.

The real themes that we have for Aviva Historian are really around, that connect integration. We'll elaborate on that and making the information more accessible. I mentioned earlier some of that accessibility being availability of the historian, but it's also how do we make the information that is there more readily available to people.

Some of that is, the browser based access that we have. And we also wanna make it more interesting, more relevant to people, to a larger audience. So it's not just the the few people that know how to use the historian in detail, but perhaps a casual user.

And broaden the interest add make that information more valuable. Some of that summary information, some of that requires adding context to the information so it it's more meaningful.

And then we also wanna do all of all of this in a way that it takes less work for you to do it.

So easier to install, easier to consume, easier to learn, all those kind of things. So I'll elaborate on all of these points.

The the real core technology we have for the browser based access started as something at the time we called it Wonderware online, now we call it Aviva Insight.

And then we've adapted that to use on premises as part of what we now call Historian Client Web. And then more recently we've, taken that same technology stack and adapted it to, Connect visualization services. Now you'll you'll notice the the black triangle there, this actually has two themes, a light and a dark theme in connect visualization.

We haven't adopted the the dark theme option and the other two incarnations but we expect to do that, sometime next year. So it looks a little different but under the covers it's the same core charting, technology, same widgets and we get a lot of leverage out of that and a lot of consistency.

When we originally developed this, we had what we now call the classic user interface, in insight and Historian Client Web. That's kinda the default in the current shipping versions of Historian Client Web. And we are gonna be, retiring that in the twenty twenty six release.

Even though it's called twenty twenty six, it will be next year, in the second half of next year.

Part of the reason is we've reached or pretty close to reaching feature parity in what's the replacement which is the modern experience.

And this modern experience is what we actually have across all three of those platforms that I just talked about a minute ago.

One thing that we are adding in a service pack that's coming out into this month is, one of those kinda minor detailed gaps is the ability to create a chart all through a URL. That makes it easy to integrate with other systems to invoke, the trend chart, for example, or a column chart and preconfigure it, for that particular application and that's coming in, s p one.

One of the big things that we added in historian twenty twenty three, a few years ago, is ad hoc expressions. And this is consistent across the on premises historian as well as insight. But it's real simple to add, an ad hoc calculation. This example, I'm gonna calculate a control error. So I find the difference in the set point and the process variable.

And there I have a new pen in bingo.

So super simple to do for an end user. You don't have to have any elevated privileges to do that. In this particular case, maybe I want to don't want the instantaneous one. I want to to dampen that a little bit, and so I'll add a average calculation.

And I'm gonna add a one minute average to that, control error just to smooth it out a little bit.

Save that change and there we have it.

Super simple to do, try to make it easy to to explore. It's a syntax that's pretty consistent with Excel, so it should be familiar to most people.

We have a rich library of expressions, functions in this expression library.

We've added to that with each subsequent release the black text is the original. And then, we added some in the r two release. We have some more being added in the upcoming twenty twenty six release.

And, it's not really a function but we also have some some limited string support.

Particularly useful in an if condition. So you can use it in the logical part of the if or in the results.

Those string literals will be useful.

And we have some other ideas and if one of those is for example, these aggregate functions are all based on a time interval.

Hour, day, five minutes in this example. One of the things that we're looking at doing is is expanding that to be event based. So a batch ID, recipe step, a logical expression as you see in the last example.

One brief explanation on my terminology. I'll talk about ideas, things that we wanna do, and plans. And the big difference in the two is plans have assigned schedule, budgets, and staff.

Ideas don't have those things. And so we are a little bit further along in that we've actually done some of the work on this. But we're we're not yet committed to a schedule. But this event based, expressions are likely to make it in the twenty twenty six release.

One thing that we're definitely doing is, addressing some performance challenge. So one of the one of the problems with these expressions is we've seen people using them pretty widely, pretty aggressively.

And in particular, we've seen a lot of usage of, time based aggregates.

And over longer time periods, this, because these are calculated ad hoc, it can be a lot of compute.

So let's take the example of a one second value. It's stored once a second and I want a daily average.

That's eighty six thousand operations in the simple case. Right? They do that for a few days and it gets to be a lot.

Now, we actually have that value pre stored and calculate calculated and stored in what we call the auto summary system. And we'll leverage that in in a lot of the retrieval notes. We don't currently leverage it in expression. And so one of the changes we're gonna make is, to start to leverage that dollar summary we'll see in the testing that we've done we've seen thousands of times, performance improvements in some cases. Depends on the expression.

And on the data rate and a lot of variables. But it can be a huge performance gain. Now it doesn't apply to everything. So for example, here's some expressions that it won't work with or it doesn't help.

So the expressions still work, the numbers will be the same, but the performance isn't gonna be any better. For example this one is a too small of an interval. We do up to an hour. So if it's an hour or longer it may be useful.

Here what I have an expression that I'm evaluating and then doing the aggregate on. Doesn't help with that because we haven't precalculated that result.

Here's one to be mindful of. So if I put the the division inside the parenthesis it's not gonna benefit. But if I do it like this and move it outside, it will. So just some things to keep in mind, once we release that.

And this is definitely gonna be in the next release. We're gonna deliver it online at end of this month.

We're also working on, how do we get data into Historian Better. So one example is InTouch.

We do have this ability to push historical data and tag creation into, historian from in InTouch. We have a a tech note for how to do that with a redundant tag server configuration. Be aware of that.

But one of the things that we're gonna add is support for partner historians or redundant historians. So I can send that same data to two destinations.

An explanation here on my notation here. So the the black dots are things that we've already released.

The green plus is something that we're adding in the near term.

So for system platform, we're going to be pushing asset type. So we already push assets based on the galaxy model. We're gonna be pushing the template derivation view essentially into historian. We'll be able to leverage that for search, and then we'll also be able to push it in, some other places and we'll talk about in a second.

Have plant SCADA connectivity that's gaining Windows authentication to the plant SCADA system. Possibly some other things there that we're gonna add.

And then, we can today collect from MQTT sources and push that into the historian, but you have to configure it item by item. One of the things that we're adding is gonna be the auto configure. So you give it a topic with a a wild card in it and you'll just pull in all those tags and start, populating the data as well.

On the outbound side, we're we have a service pack coming out at the end of the month. And we're gonna be adding the asset model into connect data services. So today we push tags. That's available. We have some minor tweaks to how we're doing that. But we'll also be creating the asset model based on the galaxy model view.

That's coming in s p one.

In the next major release, we'll also be pushing the asset types. As we get those into the story, we'll be able to replicate those, into data services.

Here's what it looks like in s p one. So here's the model view within the IDE over here on the left.

And if I switch over to the SMC and configure replication from the historian, I select the destination type as connect data services.

Register, I get a login challenge for connect.

Log in, and then I'll select from the available name spaces in data services, pick one of those, and that's where I wanna register this.

And now, now I've established a connection to data services.

I do have some naming conventions or a naming rule for generating tags and data services. I can change the default, but I'm gonna keep that.

And now I'm gonna add some particular tags that I wanna send to data services.

This part of the workflow is is consistent with what we released two years ago.

So if you've used that, it that part hasn't changed, but the results have changed a little bit. I can edit the destination tag name here. I'm gonna keep the defaults there.

And then once I, commit those changes it starts sending.

And if I switch over to data services, I can see those streams created using that default naming convention. And if I switch over to the asset explorer, you see the assets that were automatically created from that model view.

And they have the properties assigned. I'm gonna pick this is supposed to be a boiler. I'm gonna pick the temperature and pressure.

Change the time period here to the last five minutes, and you see there I have data. Now I can also use the backfill. So if I want, I had two years of data on that in the Veeva Historian, I can send that, take a little bit of time, but that'll work. And then if I switch over to connect visualization, see that same asset hierarchy is recreated here.

And we have a default view for an asset in, visualization. This is that default view. Show some of the static information and then, we'll call a status board with the the time series data. You can customize this to your particular application but that's what it looks like out of the box.

It's kind of a high level view of the, the road map. So we have had, some patches recently. We have the service pack coming up soon. Another big change there is the dot net run time we're using. The plant SCADA connector update I mentioned is coming out soon, shortly after that.

The ability to send data to con to, connect data services and visualization, we're gonna break that out of the embedded, the way it's embedded in Historian so we can deliver new functionality easier on older versions of Historian, and we'll be doing that. And then, as part of ops control twenty twenty six, we'll be doing more things, around expressions, may do some more around, alarm analysis and visualization as well.

And, and then, some of the other items I talked about there.

A lot of ways to get information out of the historian, historian client desktop, historian client web, the excel add in, and Aviva reports for operations. I'll come back to that in a second.

Power, Power BI will work with historian, but Power BI is particularly well suited to multi dimensional data and historian's not really a good multi multi dimensional source.

So you can get the data but it's typically not as useful to pull into Power BI as you might like.

Talk about rev Aviva reports some more. So some of the same type of aggregates that that I can use in Historian Client Web, I can use in Aviva reports.

Aviva reports is particularly well suited to kind of a paginated format.

Anybody still using paper reports?

I expected somebody, but it but it's at least well suited to a PDF, and maybe you put it on a piece of paper too.

Good for email distribution of those reports as well.

Just a a scheduled static report that you can archive. It's great for that.

There are also some special functions in Aviva reports for doing a set point analysis, alarm analysis, SBC, and we've add some some richer capability in the batch area.

So over here on the left I have event frames out of pie and we we've mapped those into kind of a hierarchical model of a batch. That's a new feature in reports. So I can have different levels for the batch, for the unit procedure, etcetera.

And then I can also create, import event frames from pie for that and then create reports that use what we call, clusters that are specialized for each of those levels. So the the layout for unit procedure is different from a phase, etcetera.

We are going to be, adding the ability to publish a report from Aviva reports into, Connect. In this particular case, Insight.

And that publishing will initially go into the Aviva drive, that shared folder that you have in, Connect.

And then we'll be expanding that so it's browsable for within inside and Connect visualization.

We're also gonna be leveraging the single sign on capability we have in Connect for the connected experience, so we can use that in Aviva reports.

High level roadmap here.

The event frame support, nested batching, that's, already released.

By the end of the year we're gonna have the publishing capability to connect and the single sign on. And then, next year we'll be adding, kind of the run time hosted in connect.

Design time will still be the thick client that we have today, slightly updated, for the authoring, but then I can publish reports to the online solution.

A lot of focus to date on ROUND Connect has been, on the data side. But one of the things that we're trying to do is, expand the access to that data and then use Connect for more. We'll talk about both of those.

We've been on a journey when it comes to the this hybrid SaaS, for operations control. Started as standalone insight on premises historian that could integrate. And then when we introduced operations control, we really had an integrated solution. Now, this doesn't show up here but imagine that there's a a gray rectangle behind this part.

It's just not showing up, contrast doesn't work right. But, operations control going right, it is, our vision is to add more and more SAS components to operations control. Started with insight and teamwork. We're adding the single sign on.

We're adding, connect data services support.

And then, this last thing, we're adding some integrated models, that to simplify the workflow for teamwork.

Then Aviva insight is really focused on this accessible information, particularly a lot of people are using the mobile device access for that. Just to make that detailed operational data available to a larger audience.

And then it's, accessible in several ways. The kinda ad hoc access. We had a problem yesterday. I wanna find out the root cause and try to prevent it from reoccurring tomorrow.

Create dashboards from that.

And then we also have OEE performance, in the utilization area.

Automated analytics. So you just push the data and we start doing anomaly detection and reporting that.

And then for more sophisticated applications where you wanna invest a little bit engineering expertise into that, we have the guided analytics option. And then more recently, if you're in John's presentation earlier today, he mentioned, that we're also expanding that to include, connect data services. And one of the big advantages in connect data services is the idea of communities. The idea to to share subsets of the data, subsets in granularity, time frame and, tag selection. All those options, with a larger audience. And that might be an internal audience for other applications or it might be, partners like supply chain partners that you wanna give access to subsets of that data.

And the other big advantage in data services, the availability of advanced analytics.

When guided analytics, doesn't really meet your needs and you have the expertise, advanced analytics is a a great option.

In the area of user identity, kind of the typical model is people have a Windows Active Directory for a at a business layer.

Maybe they federate that with Microsoft Intra or formerly Azure Active Directory.

But typically on the supervisory network you've got a different identity.

Maybe these are, trusteds in some manner but that but it's a different identity.

Maybe you even have a third on the DMZ.

And that's the traditional way that we've deployed applications. Many of you are probably doing that.

With the twenty twenty three r two release, we added an, the option for a single sign on that's federated with our, Aviva ID.

And I can use that consistently across all of these domains.

We even have a utility DMZ Secure Link that lets you, that helps bridge that DMZ case.

We'll also use that for, some not quite all of the entitlement. So as an alternative to installing local licenses on a local license server, you can use this entitlement enabled through Aviva connect.

Let me show you what that looks like.

That single sign on across multiple applications within system platform or operations control.

So I can log in when I launch the, system platform IDE, for example.

And you'll see in the upper right hand corner this, the identity and that's my identity. And if I, switch over to uh-oh. I get a little bit of additional detail there in that back backstage if I launch, OMI.

I don't know if you noticed it but that login challenge showed up and then disappeared automatically. It automatically signed me in to that same identity. Here I select a trend and it's authenticating against the historian, using that same identity.

Same thing with the historian client web and same identity. Now one of the gaps in this initial release is works great as long as you have that active connection. But if you lose the connection, to Aviva Connect, then, you couldn't log in. So one of the things that we're doing is adding this intermittent connection support and that's coming out next year.

So here I can have kind of a parallel on premises active directory identity that has the same rights and entitlements available even in that kind of disconnected intermittent connection scenario. And then all of the applications have this kind of consistent banner up here which you may not be able to read. But basically says you're disconnected, you're able to still use the software until whatever the end time is.

Okay.

Our goal is to use more and more of this cloud enabled functionality in the on premises offers.

So we've done some with identity with some with entitlement, some with the models, and we're continuing to expand this. So over the next few years expect more and more of this to get filled out.

If you use Development Studio, today you can get access to, some of the entitlements, software downloads.

But we're adding, later this year we're gonna add the ability to upload a Galaxy backup.

So when I upload that it's a it's a archive repository for that backup and I can download it, restore it.

But there's more I can do with it.

One of the challenges we've had is we wanna make sure it's easy for people to leverage configuration across the portfolio.

So the first installment of that is being able to leverage that same model to populate teamwork.

So you see one of the options here is to export that model or I think publish is the word we use. Publish that model to Teamwork.

Now, we expect most customers aren't gonna have one to one correspondence between a Galaxy model and a Teamwork model.

So we wanted but we still wanted to make it easy to leverage the existing model.

So the approach we've taken here is this side by side. I can select items from the left, the galaxy model, drag them over to the right to populate the teamwork model.

So I can select the subset that I wanna map.

Drag those across.

And this does save me the typing and the tedium of that, but it also maintains that connection between them.

And that I can leverage, elsewhere in the solution in the future.

And then, I complete that, didn't have the errors, and, now if I launch teamwork and, select the model here, There are those, that equipment that I created, automatically based on the Galaxy model.

We do have some entitlement access. So currently you can access downloads and, licenses.

Actually the license here basically takes you to a help page today.

But we are expanding that so you actually download perpetual licenses, as part of your, operations control entitlement.

All from the same place.

Teamwork. So anybody familiar with teamwork?

Few of you. Alright. Real brief explanation here. So teamwork is really focused on how do we organize people to solve problems in production. Particularly with with equipment. So it's about the communication side of that.

How do we communicate the problem?

It's about, capturing knowledge about how to solve problems and, creating a catalog of that. And then also tracking the training, who's, learned how to solve these kind of problems, maintain this type of equipment.

Who needs to be, needs a refresher.

And then when there are particular issues, marshaling resources to solve those problems. That's the real focus of teamwork and we wanna jump start that with this model transfer that I I talked about earlier.

We've we've made some improvements over the last, few months in it's an online solution so we've delivered those. Some usability improvements. We're gonna have this, model creation that I mentioned and before the end of the year we're gonna introduce, the single sign on so it's a consistent sign on across connect including teamwork.

Last component of the portfolio I'm gonna talk about here briefly is Integration Studio. It's a virtualization solution where we make it really simple to create, multi node configurations particularly for development and testing of, a distributed application.

And, it includes the entitlement, the installation, our base images based on released versions of the software and, let you quickly stand up configurations, for development and test.

We've made several changes over the last, several months. Added images for the new r two releases, some usability improvements.

Next year we have planned a more sophisticated configurations with things like multiple NICs, including a domain controller so that I can leverage that across multiple projects and, being able to snapshot those. They you have to do it inside the VM and it's a little bit harder to to manage.

So, just a reminder, this is the the components that we talked about as part of this overall operations control offer.

One thing to keep in mind and people been hearing about heroes HQ this week, several of you. Great.

Really encourage you to leverage that both, to learn from what's available there as well as share some of your expertise, there with other users.

It's, got the same type of forum capability we've had for a while but also has a lot of videos, training, a lot broader information and, really want you to be able to take advantage of that.

There are a couple of other sessions later on this afternoon that that are might be relevant if you thought this was helpful.

Wanna call attention to those and with that, appreciate your time and attention.

Thank you very much.