Topic 6.2.1: Configuring History
- Historization Background
- The history system supports historization of
process data in distributed history architecture.
- The Galaxy can be configured to store history data into one or more
of those Historians. Since the Engines use push technology to historize, the
Historian box does not have any ArchestrA software requirements.
- Each Engine in the Galaxy
is configured with the location
of the Historian storage node to which its
history data is to be sent. This configuration is stored in an attribute within
the Engine.
- Wonderware Historian requires
a Historian tag to be configured in its database
for each attribute to be historized by an AutomationObject. Thus, there is a
one-to-one relationship between a historized object and a tag in Wonderware Historian.
- The history system supports historization of process data in distributed history architecture.
- The Galaxy can be configured to store history data into one or more of those Historians. Since the Engines use push technology to historize, the Historian box does not have any ArchestrA software requirements.
- Each Engine in the Galaxy is configured with the location of the Historian storage node to which its history data is to be sent. This configuration is stored in an attribute within the Engine.
- Wonderware Historian requires a Historian tag to be configured in its database for each attribute to be historized by an AutomationObject. Thus, there is a one-to-one relationship between a historized object and a tag in Wonderware Historian.
Last modified: Friday, 10 April 2020, 3:47 PM