[0:00] Mark Hepburn, ICONICS Vice President of Global Sales
I would like now to illustrate these together and invite up by my colleague, Mr. Luke Gonyea. Luke, come on up, please. So, Luke is our one of our Solution Sales Engineers here in Massachusetts. He has been with us for three and a half years. So, Luke will demonstrate Hyper Alarming and AssetWorX together in the some applications, so you can see how these things work and bring value.
[0:3]7 Luke Gonyea, ICONICS Solution Engineer
Excellent, thank you, Mark. Appreciate it. I prepared a demo today for the Hyper Alarm Server.
[0:46]
And thank you again for joining our virtual event today. I want to spend time on this demonstration highlighting our Hyper Alarm Server that was released in our 10.97.1 release, and then I will also touch on our new Hyper Alarm Logger which will be released with the 10.97.1 version of GENESIS. My demonstration today is going to be expanding on the same asset base modeling that Chris mentioned in his cloning dynamic example. For the presentation, I have a roller chain manufacturing facility. On the right half of my screen, you will see the layout of my different pieces of equipment in our facility. So, we have a high level facility that has several areas, each area has different product lines. And then each product line is going to have several pieces of equipment manufacturing these different parts. The asset model we have in GENESIS64 is going to model that physical layout of our equipment. So, on the left hand side, you can see my Asset Navigator and how it is mirroring that same configuration. With the Hyper Alarm Server, we are now able to have further integration between our alarms and that asset structure that we define. In my example, I have an additional column to my asset navigator titled “Active Alarms”. So, this is looking at that Hyper Alarm Server alarm data and then associating it with individual pieces of my asset tree. So, in our case, I have press A that has five current alarms, the 100 line, which is the parent line of that press A has between six and seven alarms, and then so forth, all the way up to auto assembly which would be the department and then the chain manufacturing plant which would be site wide. In addition to visualizing our alarms through our Asset Navigator, we have the traditional tabular view that our existing users would be familiar with our AlarmWorX64 product. In the tabular view, we can filter by different metadata fields that we have associated with our Hyper Alarm Server alarms. In this case, I have this current operator field and I'm looking at alarms just for John Smith. We can navigate using those alarms. As you see I load the alarm details pane on the right hand side. I'll use that to load our floorplan. The floorplan in addition to all the different widgets we have, can easily integrate with that Hyper Alarm Server. You can see that my asset is color coded based on alarm status. I also have historical information and a trend viewer right on the bottom of the screen. And then the real time asset information on the right hand side, all in a single interface so there's not multiple displays for these different functions. In addition to that asset information, we can have our Hyper Alarm Logger log these events for long term storage. And as I go and expand my alarm log, you can see the same fields that were available in the Hyper Alarm Server on the previous display available here on the Logger alarms. I want to spend a little more time talking about the configuration in the workbench in the back end here.
[4:36]
So, I'm going to jump over to the workbench and talk more about our asset structure. In auto assembly, we have several product lines, and each line has its own associated pieces of equipment. In the graphical interface, we are emphasizing the configuration of press A so just quickly touching on the advanced analytics and the configuration of that on this asset in the workbench. And then on each individual property, we can configure our historical, our real time, and now our alarm information. So, if I go to this temperature asset, I have a Modbus tag reading in that real time information. I have the configuration for my Hyper Historian tag. And I now have my alarm conditions that I can define directly from this asset property. The configuration of the Hyper Alarm Server is also going to allow for more control over the configuration of these alarms and events.
[5:48 ]
Part of that is having the ability to generate our own expressions. So, in our example, I'm going to look at this high limits alarm in actual Hyper Alarm Server configuration. In the Expression, I'm able to use the full ICONICS expression library to generate a statement that defines different alarm conditions. In this case, I have three conditions: I'm going to have a high high condition; I'm going to have a high condition; and then I'm going to have a normal condition, each of those conditions is going to be associated with a numeric trigger. In this case, we have three: normal being zero; high being one; and high high being two. In addition to this, further control and better modeling of our facility, we can define what inputs are available to our operators or to our engineers who are actually configurating these projects. In the case of my high limits alarm, I have our normal alarm and events, fields that we expect. So different values, the message text. In addition, I also have the related value that was talking about when we're looking at that GraphWorX display. So, I have my current operator relay and value. So, two of the biggest differences: One is that there's no longer limit to how many relay values we have on these different alignment events. The second from an engineering perspective is that in AlarmWorX64, it was just related values, 01, 02, 03, and so forth. With the new Hyper Alarm Server, we have the control to name that related value whatever we want. So, in our case, we're looking at current operator. The benefit of this being is that you and your engineers no longer have to memorize which related value maps to what field. You have the ability to customize and help that normalization and standardization of nomenclature across our project. So as this project grows, it's much easier to keep track of what field means what. In addition to the configuration of our Hyper Alarm Server, we also have a new area to configure the Hyper Alarm Logger. Not too much to show in terms of the configuration, but we can automatically download the subscription of our Hyper Alarm Logger without having to do any additional engineering behind the scenes. This all is going to work out of the box, reducing your time to value of these alarming event tools. In addition to having our Hyper Alarm Server configured directly from the provider in the workbench, we can integrate it with our equipment classes.
[9:12]
So, in our case, I have the equipment classes for my 600 ton press. And what we'll see is on the actual figuration, I have all those fields that I mentioned in that Hyper Alarm Server configuration available to me as an engineer in the interface. Any extra fields I'm not using for this high limit alarm is not visible. So, it declutters our interface and makes things more intuitive and straightforward. In addition, you can also see this current operator related value, and how I'm able to configure that and how it works seamlessly with, in this case, the self-referential properties that we have in AssetWorX. So, it's pointing at whatever instance of this press I create, look at the operator property. This works seamlessly with our Bulk Asset Configurator. So, I can create as many presses as I need in my application, and this related value current operator field will update automatically.
[10:14]
That concludes my demonstration of the Hyper Alarm Server. If you take one thing away from this presentation, I want to emphasize that the configuration for our real time connection, our historical data logging, our advanced analytics, and now with the Hyper Alarm Server and Logger, alarm and events are all configured through this centralized asset tool, AssetWorX, in the GENESIS64 platform.