Factry
Overview
The Factry Historian connector enables Seeq to access data from Factry Historian . This includes signal data, asset tree data, UOMs and capsules.
Prerequisites
The Factry Historian connector is compatible with Factry Historian version 6.1 and higher.
Configuration
This is an example configuration template that is displayed in the Additional Configuration box that appears when you click Configure for an existing datasource (or if a new datasource is being created, in the Create new datasource connection modal that appears after clicking Add Datasource) on the Datasources administration page.
{
"Uri": "http://myhistorian.company.dev:8000",
"OrganizationUUID": "b6fa43ca-add8-11ed-907d-1234ac170004",
"AccessToken": "eyJhbGciOiJIUzI1NiIs.....HgYxTdtQtcTn2vq9I"
}
Factry Historian Additional Configuration
| Property Name | Default Value | Data Type | Description |
|---|---|---|---|
| Uri | null | String | The URL used to connect to Factry Historian. For example : http://myhistorian.company.dev:8000 |
| OrganizationUUID | null | String | The UUID of the organization you wish to consult data from. You can find the organization UUID in the historian admin interface under Configuration > Server Settings > Organizations |
| AccessToken | null | String/ SecretFile | The API access token used to communicate with the Factry Historian API. You can find more information on how to create an API token here |
Known issues
- Only Factry Historian measurements of type number, boolean and string are supported for indexing. Arrays and raw data types are not indexed
Performance consideration
- Prior to version 6.3 of Factry Historian the historian has a fixed timeout for queries. This may cause some issue while fetching data over longer time periods, for example a couple of months. This issue can be resolved by limiting the “Max results per request” configuration value to a value of around 100000.