[0:00]
Next, I'd like to pivot and talk about alarm innovation. Hyper alarming is our 10.97.1 product. ICONICS has long been a leader in distributed advanced alarm management. Now with version 10.97.1, we are delivering what we aim at minimum 5X performance improvements really ready for the future. So first Hyper Alarm Server introduced in March with our 10.97.1, a much more powerful native integration server, better performance, control, and integrates natively with AssetWorX. So, everything comes together with a Hyper Alarm Server, and the Hyper Alarm Logger. So Hyper Alarm Logger introduced in 10.97.1, so that's our November release. This will have redundancy, again, native integration with platform services, full scalability, this asynchronous multi-threading processing that you get with a managed services that we have is a core ICONICS platform. So, there's not just for now, but also for the future, ready for cloud based, scalable applications that build on the really an underpinning of the roadmap for more analytics and for more cloud based applications that Ted Hill reviewed in the opening?
[1:30]
Okay, so I'd like to just pivot a little bit around this concept of digital twins. We hear a lot about digital twins these days. The concept combines elements from our physical world and digital world and pulls them together with telemetry, with context from not just the things and their sensor data but putting in context where they are and how they're used and the people that are using them and historical data and alarm data. So, this whole idea, generally is digital twins. But I think if you ask a half dozen people, you're going to get different answers. What exactly a digital twin is. From our standpoint, I like to think of a digital twin for operations. Somebody who's trying to improve the productivity resilience of the other operating plant is the fusion of geometry, telemetry, that's the sensor data, analytics, and metadata. This metadata could come from the people, places, things are that used to come information systems like: What's the product? What's the batch? What's this, what's that? It's all part of the digital twin. So multiple data sources for operational control and insight. That's digital twins for operations. So, in this case, we see an object or set of objects. This is a crane; you'll hear more about cranes later in this presentation and marine ports crane, big stuff. So, I'm going to have a digital twin of a geometric twin coming from the computer automated design, from the Product Lifecycle Management application. I add telemetry to that; I get key performance indicators. I can put them in context on the device. With ICONICS, we connect that data through our digital twin, we call AssetWorX, so I can take elements like speed, pressure, temperature, humidity, and so this is live and historical data, I can combine this with analytics, etc. And I end up with an object or with relation to all this metadata. And then I can organize that object into a logical structure, often geographical or financial, etc. And, of course, with AssetWorX, I have flexibility of creating virtual views of that, etc. It's a really flexible tool. So, we have then this digital twin in context, in AssetWorX. So, I see the object and who's working, what are they lifting, what's in the container, anything there's metadata that I can bring in from web servers and or from OPC or any of the data communications methods and combine them into this asset framework. So AssetWorX - ICONICS digital twin; it is a multi-level distributed architecture. It has the ability not just for live and historical data from AlarmWorX and live alarms from the Hyper Alarm Server, historical data from the Hyper Historian but also from analytics, all together in one framework. We think over the years the ISA95 kind of architecture. This helps us support and define the layers of the architecture. Often, as you saw on the map with Chris's example, we'll look at things kind of geographically or financially, or you know, it could be logically around production. So, AssetWorX all at the center of this, and it's not just the back end the ability to connect into the data. There's also very nice front end. So, there's a tree like structure, some really nice features in there that help us to manage the project and run as an operator, including the ideas of reusable templates.
[5:23]
There are back end data templates. There are front end visual templates, and the ability to add in some very nice visual effects, totalization, and iconagraphy, etc. And AssetWorX becomes an actionable operational template, so operators can interact. So, this concept of global commanding is very important for AssetWorX. As we look at web based, scalable cloud based applications is really important for us to avoid scripting that requires kind of client side activity or complex scripting that's really hard to diagnose. So, AssetWorX and of course, the entire ICONICS front end supports us global commanding, it's server side actions that substitute for scripting. Of course, ICONICS is open, so you can do scripting as well. But we think this is one of the major differentiators when we look at other projects from other applications, it's just this tangled web of scripting. Get rid of the scripting when you can, and you can I think virtually all of our projects use zero scripting