[00:00] In this lesson, we will take a look at memory tags. A memory tag is a very simplistic tag. It doesn't automatically update or change its value, but it's just a simple tag that stores the value in memory hence the name. Creating a memory tag is as easy as creating any of the other standard types of tags. In our tag browser, I can click on the plus button here and select the new tag menu to give us the option to create a memory tag. This should bring up our tag editor. I will name my tag mem one and leave its data type as integer. I will set this value to say 10. Clicking okay will finish my tags configuration, and it will create my new tag as you can see here. Its current value is 10. With my designer in read and write mode, I can double click on the tag's value and change it to 60 if I wanted to. Now again, the memory tag does not automatically update or it does not pull anything. It simply sits with the value until something comes along and writes to it. Typically, that's something is a component bi-directionally bound to a tag or a script running somewhere that is writing to the tag. Memory tags are really useful if you just need a placeholder tag. Say you want to start a project, but you have no access to any viable PC data, you can simply use memory tags. Say you want to test functionality of a script instead of using live production tags, you can use memory tags instead. It's also pretty common to use these as say, set point tags for alarms, storing the current work order for a particular line or any number of other uses. And again, because this is inside of one of our tag providers, every other module, every other subsystem or feature inside of ignition has access to this tag. The ability for a memory tag to be independent from OPC and databases makes them a powerful part of the ignition tag system.