Specify naming schemes for replication
- Last UpdatedFeb 04, 2026
- 3 minute read
A replication naming scheme is a collection, or expression, of identifiers that fully describe a replication tag. Replication tag naming schemes identify the information being replicated quickly and easily and also prevent name collisions between tags that inadvertently have identical names. You are encouraged to plan your naming conventions and system requirements before implementing a naming scheme.
Note: Name collisions can occur when you have two or more tags (usually from different historians) that have the same name. The data stored from one tag is mixed with data from the other tag, contaminating the data on the replication server.
The naming scheme placeholders are described in the following table:
|
Value |
Description |
|---|---|
|
<ReplicationDefaultPrefix> |
A prefix based on the replication server name. |
|
<SourceTagName> |
The name of the source tag on the lower-tier Historian that is being replicated to the next-tier Historian. |
|
<TypeAbbreviation> |
The type of summary tag: blank for analog summary or S for state summary. The type abbreviation is most useful for preventing collisions between analog tags. For an integer source tag, you can create both analog and state summary tags, which can result in tag naming collisions if you use only the other naming parameters. |
|
<GroupAbbreviation> |
The abbreviation for the replication group. |
This diagram illustrates the naming scheme relationships:
When you define a new replication server:
-
The default scheme for the simple replication tag naming scheme is taken from the SimpleReplicationNamingScheme system parameter.
-
The default scheme for the summary replication tag naming scheme is taken from the SummaryReplicationNamingScheme system parameter.
When you define a new replication schedule, you define a schedule abbreviation.
When you define a new replication group:
-
The default value for the group abbreviation is taken from the schedule abbreviation for the associated replication schedule.
-
The default scheme for the summary replication tag naming scheme is copied from the summary replication tag naming scheme of the associated replication server.
When you define a new replication tag:
-
The value for the <ReplicationDefaultPrefix> is taken from the current setting of the ReplicationDefaultPrefix system parameter.
-
The value for the <TypeAbbreviation> is taken from the StateSummaryReplicationTypeAbbreviation or AnalogSummaryReplicationTypeAbbreviation system parameter, depending on the type of replication (the "folder" within the server). The <TypeAbbreviation> is applicable only for summary replicated tags.
To configure the naming scheme
-
Specify a custom naming scheme in a dialog box by clicking Custom, and then clicking the button to the right of the box. The Naming Scheme dialog box appears.
-
Enter the naming scheme to use for tagging the replication tags. The parameters you can use and an example of what the string looks like appear in the Tag Name Example box.
Note: Simple replication tags do not have a type abbreviation and are not assigned to a group. You can use the <TypeAbbreviation> and <GroupAbbreviation> parameters in a simple replication tag naming scheme, but they always have empty values.
-
Click Finish.
Multiple lower-tier historians can replicate alarm and events to the same next-tier Historian. Replication records on the next-tier Historian include a source name to indicate the originating lower-tier Historian. By default, that is the server name itself, but it can be modified.
To change source name for a lower-tier Historian
-
In the OCMC, click Configuration Editor, click System Configuration, and then click Parameters.
-
In the list on the right, right-click ReplicationDefaultPrefix and then click Properties.
-
In Value, type a new name. Click OK.