AVEVA™ Historian

Replication tiers

Save PDF

TABLE OF CONTENTS

Replication tiers

Save PDF

Last UpdatedMar 10, 2025
3 minute read

When you replicate data, it creates a tiered relationship between the historians.

That is, the tier-1 historian send its replicated data to a tier-2 historian.

AVEVA Historian can replicate process data as well as alarms and events.

Relationship of Historian tiers

A historian can act as a tier-1 and a tier-2 historian simultaneously.

Here's a typical scenario for a tiered historian:

TagA is collected by Hist1, a historian. It is replicated and stored on Hist2.

In this relationship, Hist1 is a tier-1 historian and Hist2 is a tier-2 historian.
Concurrently, TagB is collected by Hist2. It is replicated and stored on Hist3.

In this relationship, Hist2 is a tier-1 historian and Hist3 is a tier-2 historian.

How tags move among Historian tiers

Historian supports multi-tier replication. Data originating at tier 1 can be replicated to tier 2, then again to tier 3, and so on.

This diagram illustrates two relationships between historians.

TagC is replicated from Hist1, a tier-l historian, to Hist2, a tier-2 historian. Hist2 replicates the tag to Hist3, a tier-3 historian. Hist3 replicates the tag once again to AVEVA Insight (tier 4 in this scenario).
TagD is also replicated from Hist1, but this time directly to AVEVA Insight. In this case, Hist1 is the tier-1 historian and Insight is the tier-2 historian.

Multi-tier replication

The following tables show how the replicated data is named as it is replicated in these two scenarios. These examples are based on the default naming scheme.

TagC replicated across 4 tiers (Hist1, Hist2, Hist3, Insight)

Tier	Computer name	Tag name	Summary tag name
Tier 1	Hist1	TagC	TagC.1M
Tier 2	Hist2	Hist1.TagC	Hist1.TagC.1M
Tier 3	Hist3	Hist1.TagC	Hist1.TagC.1M (see note below)
Tier 4	Insight (and data source = DS)	DS.Hist1.TagC	DS.Hist1.TagC.1M

Note: Summary replication happens between tier 1 and tier 2 only. All data replication to tier 3 and beyond is simple replication.

TagD replicated from Hist1 to Insight

Tier	Computer name	Tag name	Summary tag name
Tier 1	Hist1	TagD	TagD.1M
Tier 2	Insight (and data source = DS)	DS.TagD	DS.TagD.1M

Note: Before version 17.3.100, replication to AVEVA Insight used the same default naming as any other tier 2 and still included the "DS" prefix (where "DS" is the name of the data source). For example, consider how "TagC" was replicated to Insight before and since version 17.3.100:
- Before 17.3.100: TagC was replicate to Insight as "DS.Hist1.TagC".
- Since 17.3.100: TagC is replicated to Insight as "DS.TagC".

AVEVA™ Historian