history-HistoryConfig

This component configures a history in the History database.
Figure 164.   History Config properties
Image

This following table summarizes the History Config properties.

Property Value Description
History Config additional properties
Serves as a container for sub-properties used to configure the attributes of the history record stored in the History space.

A separate topic documents these properties.

Id read-only
Displays string results from a value configured in history extension’s History Name property. An error string here indicates the History Name property is incorrectly configured.
Source read-only
Displays the ORD of the active history extension.
Time zone Text String
Displays the time zone of the active history extension.
Record type Text
Displays the data that the record holds in terms of: extension type (history) and data type (BooleanTrendRecord, NumericTrendRecord, and so on).
Capacity Record Count: nnn (500 default), Unlimited
Specifies local storage capacity for histories. In general, 500 (default record count) or less is adequate for a controller station because those records are usually archived (exported) to a Supervisor station. For this reason, a very large number, such as 250,000 is acceptable for Supervisor stations. Unlimited is not the wisest choice even for a Supervisor station.
Full Policy Roll (default), Stop

Applies only if Capacity is set to Record Count. When capacity reaches record count, the newest records overwrite the oldest records.

Interval Text string
Defines, for Interval-based data collection, the cycle time, or how often the history properties are checked. Changing this property creates a new history (or splits-off) from the original history because histories with different intervals are not compatible.
System tags text
Assigns additional metadata (the System Tag) to a history extension. This identifier is then available for selective import or export of histories using the Niagara System History Import or Niagara System History Export option (using the System Tag Patterns). Each System Tag is separated by a semicolon. For example: NorthAmerica;Region1;Cities.