The Gateway System tags provide status about the system, such as memory usage, performance metrics, and so on. They exist for the Client and the Gateway. You can modify the Gateway System tags to use alarmingTags are status Tags that Ignition provides about the Client and the Gateway. You cannot create any new Tags in the Client or Gateway scoped folders. The Tag names and folder structure are managed by the Ignition Gateway. However, you can modify Gateway-scoped Tags to perform alarming, history, and scaling but additional System tags cannot be added to the System folder. The tag names and folder structure is managed by the Ignition Gateway.. You cannot modify Client-scoped Tags.
Client-scoped Tags provide status information about the client's system. Every individual client is going to have their own values like IP address, hosting name, username, etc,.
Gateway Scoped Tags
Gateway-scoped Tags provide status information about the Gateway like alarming, database, throughput, memory usage, performance of the server, and much more.
The Client tagsTags, as the name implies, are only available for use in Clients. They are scoped at the client level unlike the Gateway executed tagsExecuted Tags. All clients will have the same client tags Tags, however, the actual values the client tags represent will be are unique and independent of each other. In other words, even though they client Tags are created in the Designer, each client will create their own instances. This makes them very useful as in-project variables, for passing information between screens, and between other parts of the clients, such as scripting.
Client tags Tags are a hybrid of memory, expression, and SQL Query Tags and do not have a scan class. When set to run as an expression or query, a poll rate is specified dictating how often the value should be calculated.
Client tags Tags support datasets in addition to all the other datatypes such as integers and date-times.