Impact of a Server Reload on Historical Records
- Last UpdatedJul 18, 2023
- 2 minute read
The following sections detail the effects on the history of reloaded Alarm, Trend and Report records. This is dependent on which fields have changed.
-
A ‘Yes’ in the New Alarm column indicates changes to that field will make a new alarm and delete the old one and therefore the history is not kept.
-
A ‘Yes’ in the Invalid History column means changes to that field will make the history of that record invalid.
Alarm Servers
Common Alarm fields
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Alarm Tag |
Yes |
No |
|
Cluster Name |
Yes |
No |
|
Alarm Description |
No |
No |
|
Alarm Category |
No |
No |
|
Help |
No |
No |
|
Delay |
No |
No |
|
Comment |
No |
No |
|
Privilege |
No |
No |
|
Area |
No |
No |
|
Custom 1..8 |
No |
No |
|
Paging |
No |
No |
|
Paging Group |
No |
No |
Analog and Time Stamped Analog Alarm fields
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Variable Tag |
No |
Yes |
|
High High |
No |
Yes |
|
High |
No |
Yes |
|
Low Low |
No |
Yes |
|
Low |
No |
Yes |
|
SetPoint |
No |
Yes |
|
Deviation |
No |
Yes |
|
High High Delay |
No |
No |
|
High Delay |
No |
No |
|
Low Low Delay |
No |
No |
|
Low Delay |
No |
No |
|
Deviation Delay |
No |
No |
|
Rate |
No |
Yes |
|
Deadband |
No |
Yes |
|
Format |
No |
No |
Digital and Time Stamped Digital Alarm fields
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Variable Tag A |
No |
Yes |
|
Variable Tag B |
No |
Yes |
Time Stamped Alarm fields
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Variable Tag |
No |
Yes |
|
Timer |
No |
Yes |
Advanced Alarm fields
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Expression |
No |
Yes |
Multi-Digital Alarm fields
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Variable Tag A |
No |
Yes |
|
Variable Tag B |
No |
Yes |
|
Variable Tag C |
No |
Yes |
|
Realarm |
No |
Yes |
|
On Function |
No |
Yes |
|
Off Function |
No |
Yes |
|
State |
No |
Yes |
|
State Description |
No |
Yes |
Trend Servers
Changes to the following properties of trends make existing trend files invalid and result in the creation of a new trend file (renaming the old one for backup):
-
Sample Period
-
Type
-
Storage Method
-
No of Files
-
Time (File)
-
Period (File)
Changing the scale of a tag will make the trend history invalid.
Effect of reload on a modified Trend:
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Trend Tag Name |
Yes |
No |
|
Cluster Name |
Yes |
No |
|
Expression |
No |
Yes |
|
Trigger |
No |
Yes |
|
Comment |
No |
No |
|
Privilege |
No |
No |
|
Area |
No |
No |
|
Eng Units |
No |
No |
|
Format |
No |
No |
Report Servers
Effect of reload on a modified Report:
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Report Name |
Yes |
No |
|
Cluster Name |
Yes |
No |
|
Time |
No |
Yes |
|
Period |
No |
Yes |
|
Trigger |
No |
No |
|
Report File Format |
No |
No |
|
Output Device |
No |
No |
|
Privilege |
No |
No |
|
Area |
No |
No |
Accumulators
Effect of reload on a modified Accumulator:
|
Field Name |
New Alarm |
Invalid History |
|---|---|---|
|
Name |
Yes |
No |
|
Cluster Name |
Yes |
No |
|
Trigger |
No |
Yes |
|
Run Time |
No |
Yes |
|
No. of Starts |
No |
No |
|
Totaliser Inc |
No |
No |
|
Totaliser |
No |
No |
|
Comment |
No |
No |
|
Privilege |
No |
No |
|
Area |
Yes |
No |