[00:00] Since UDTs are comprised of other tags, we can configure alarms on any of the tags inside of the UDT. The great thing about UDT is that you define it in one place in the definition and every instance of the UDT automatically inherit that configuration. So if I configure an alarm on the definition every instance will automatically have that alarm. If I configure a new instance, it should automatically get that same configuration. So here for example, I have a motor data type and I have four instances. Motor one, two, three and four down here. So if I go to my definition, I can configure an alarm on the AMPS tag. Every single one of my instances automatically get that configuration and if I had a new instance, it'll automatically get that configuration as well. Let's go here my motor. Double click on it. To go and configure alone on the AMPS tag. So, before we go down to the alarming tab, I can add one or more alarm conditions. Go ahead add one. And this lets us set this to a simple. Lets say, High AMPS alarm. Now one thing about putting alarms inside of UDT is that you have to be very cautious about is this display path because this is what the operator is going to see on the screen. So if I leave a blank, it's going to use the full path to the instance of that tag. So for example if AMPS in motor one is active, it'll be motors forward slash motor 1, forward slash AMPS. If I type something in here like I just type it AMPS. The problem with that is that every instance while automatically have the same display parts. So the operator if I have multiple different instances that are all active, they won't know which is which. So in this case, it's best to use if we're going to have a display path you put in manually. It's best to use one of the parameters you have that you defined in the UDTs. So for example, I defined a motor number parameter. I'm as good as basic say motor one and I'll say motor 1, Hi AMPS here to the operator. So it's really important the display path is unique because defining in one place, every instance has to be unique for that value. Then once I have that done I come down here to the mode and I can say what it's going to be above set point and when the value is let's say above 60, it's going to be an alarm. That's it. I'm going to go down and press OK and now they've defined the alarm and the definition you'll see every instance automatically gets that same definition. If I add a new motor, of course, that's also going to have that same configuration for us. If I expand these tags, I can see if they're currently active or not right now.