Advanced Historian Topics

Archiving Process Overview

The Historian module has a three-step archiving process:

1. An event triggers the request to archive a group of values. There are two types of events (Trigger or TagChange), which are configured in a Historian Table.

2. The Historian archives the values in the Target database. The Target Database can be a SQL Database or a TagProvider that is configured to act as a historian.

3. If Store and Forward is enabled, the data synchronization is executed. This option stores data in a local database if the Target Database is not available, and sends it to the target when it becomes available.

The archiving process considers two types of archiving events:

• Trigger: The Trigger can be a Tag Value, Tag Property, or any object from the runtime namespace (e.g., server.minute). When a value change is detected in the object, the archive request event is generated. Only Tags of domain Server or objects residing in server-side namespaces can be used as Triggers since the Historian process runs on the Server computer. The Trigger is configured in the HistorianTable. All tags and objects connected to that HistorianTable will be requested to be archived, regardless of having or not a new value.

• Tag Change: The Tag Change is a check-box on the TableHistorian configuration. Enabling this checkbox allows the Historian process to verify all tags connected to that HistorianTable. When the tag has a new value, the archive request event is generated. The request to archive will be generated only for the Tag that has a new value. However, according to the Historian Target Database, only the tag or all tags in the group will be archived. Further information on this is included in the next section of this page.

For a more detailed Historian execution explanation, check Archiving process.

Runtime execution

When the Solution runs, the Module Historian runs in an isolated process on the Server Computer. 

The main procedures executed by the module include:

• Check if a request to archive from a HistorianTable was generated (by the Trigger or OnTagChange events).

• Archive the Data as needed.

• Synchronize with remote archives if store and forward or redundancy is enabled.

• Reply to requests from Displays and Scripts on querying the archived data.

Those procedures as described in detail in the Archiving Process page.

On this page, we have covered the essentials of the Historian module, which provides a comprehensive solution for managing time-related data in industrial equipment and systems. To further enhance your understanding and optimize the use of this module, we recommend exploring the following sections:

Displaying TrendCharts

Is that all data is achieve, with NO addition configuration, can be really used by Displays and scripts

ON Displays, when you configure a TREND chart with a TAG, no configuration is required for the tech to use the archive, the Platform uses its built cross-referenced to know that the TAG

int ehcarft, has Historian arquivid, and queries it automatcily. 

The configuration the trend char tis on THIS LINKD

It allows the visualization of trend charts for analysis and comparison of historical and real-time data. This functionality makes it easy to identify patterns and trends in system performance. For detailed information, see the Displaying TrendCharts.

Historian Runtime Attributes

The Historian namespace exposes properties and methods of the .NET objects used by the Tag Historian Module execution.

For general information on namespace and object concepts, go to the section Objects and Namespaces.

This section describes only some commonly used properties. See Namespaces Reference for the complete list of properties and available methods.

In this section: