What would be the name of the destination tag on NodeB if ReactTemp is using the 5-minute analog summary replication group and replicating from NodeA?

In the context of the AVEVA Historian Server and how replication groups function, the naming convention for tags can be understood through the structure of the replication process. When ReactTemp is part of a 5-minute analog summary replication group and is replicating from NodeA, the destination tag on NodeB will likely retain a reference to the original source node along with the appropriate time interval associated with the summary replication.

The destination tag is constructed based on the source tag's name, the node it originated from (in this case, NodeA), and the summary interval of 5 minutes. Therefore, the name of the destination tag on NodeB accurately reflects its source tag from NodeA but also incorporates the time period used for the summary replication. As a result, the correct rendering of the destination tag combines these elements, yielding the name NodeA.ReactTemp.5m.

This identification helps in clearly indicating where the data is coming from and the specific characteristics of the data being replicated, such as the time interval, thus aiding users in understanding the context of the data within the system.