Workflow for Creating a Historian Model | Configuration Hub 2023 Documentation

Step Number	Description	Notes
1	Set up Configuration Hub.	This step is required. It involves installing the required components to get started with Configuration Hub.
2	Create a collector instance.	This step is required. It involves creating a collector instance using which you want to collect data from the object instance and store it in an on-premises Historian server or a cloud destination.
3	Specify the tags for data collection.	This step is required. It involves specifying the tags for which you want to collect data by browsing through the tags in the data source. For example, for an iFIX collector, if there are 1,00,000 tags in the iFIX server, you must specify the ones for which you want to collect data. Only then data is collected for those tags. You will later map these tags with the variables in each object instance, thus collecting data for the variables (explained later in this workflow).
4	Create an object type.	This step is required. It involves creating an object type, a default template, one or more custom templates as needed, and adding variables to each object type.
5	Create an object instance.	This step is required. It involves creating an object instance and applying the required template from the object type. The object instance then inherits the variables from the object type.
6	Provide/collect data for static, direct, and indirect variables.	This step is required. You can provide data for the following types of variables: Static: For a static variable, the value does not change; therefore, you just provide the value of the variable. Direct: For a direct variable, you associate the variable with a collector instance and a tag. When you do so, the tag is created in Historian, and values for the variable are collected by the collector instance and stored in Historian. Indirect: For an indirect variable, you associate the variable with a collector instance and an existing Historian tag. The values for the variable are then collected by the collector instance and stored in Historian. For more information on the types of variables, refer to About a Historian Model.

1

This step is required. It involves installing the required components to get started with Configuration Hub.

2

This step is required. It involves creating a collector instance using which you want to collect data from the object instance and store it in an on-premises Historian server or a cloud destination.

3

Specify the tags for data collection.

This step is required. It involves specifying the tags for which you want to collect data by browsing through the tags in the data source. For example, for an iFIX collector, if there are 1,00,000 tags in the iFIX server, you must specify the ones for which you want to collect data. Only then data is collected for those tags.

You will later map these tags with the variables in each object instance, thus collecting data for the variables (explained later in this workflow).

4

Create an object type.

This step is required. It involves creating an object type, a default template, one or more custom templates as needed, and adding variables to each object type.

5

Create an object instance.

This step is required. It involves creating an object instance and applying the required template from the object type. The object instance then inherits the variables from the object type.

6

Provide/collect data for static, direct, and indirect variables.

This step is required. You can provide data for the following types of variables:

Static: For a static variable, the value does not change; therefore, you just provide the value of the variable.
Direct: For a direct variable, you associate the variable with a collector instance and a tag. When you do so, the tag is created in Historian, and values for the variable are collected by the collector instance and stored in Historian.
Indirect: For an indirect variable, you associate the variable with a collector instance and an existing Historian tag. The values for the variable are then collected by the collector instance and stored in Historian.

For more information on the types of variables, refer to About a Historian Model.