About Setting up a Cloud Historian System
In a Cloud Historian Historian system, there is only one Historian server. This type of system is suitable for a small-scale Historian setup.
To set up a Cloud Historian system, you must first set up Configuration Hub.
- The Historian server: You must deploy a Cloud Historian Server, and apply the license.
- A Historian system: A Historian system is a network of Historian servers
that collect, store, and retrieve data related to tags, alarms, and events.
By default, a system is created when you set up Configuration Hub.
- A data store: A data store is a logical collection of tags used to store,
organize, and manage tags according to your requirements. The primary use of
data stores is segregating tags by data collection intervals. For example, you
can put name plate or static tags (where the value rarely changes) in one data
store, and put process tags in another data store. This can improve the query
performance.
By default, a user data store is created when you set up Configuration Hub. You can add more as needed.
- A collector instance: Collectors are the applications that collect data
from a data source, and send it to an on-premise Historian server or a
cloud destination such as Predix Time Series and Azure IoT hub.
You must add a collector instance to begin collecting data. You can choose the type of the collector depending on your need. You can use any existing instances (created during collector installation or ported during an upgrade).
- Tags: Tags are the parameters for which you want to store data (for
example, temperature, pressure, torque).
You must specify the tags for which you want to collect data.
- Data archiver: This is a service that indexes all the data by tag name
and timestamp, and stores the result in an .iha file.
By default, this is installed when you install the Historian server.
- Clients: These are applications that retrieve data from the archive files
using the Historian API.
By default, these are installed when you set up Configuration Hub.