iphist:index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
iphist:index [2021/06/28 08:29] – su | iphist:index [2022/08/29 12:05] (current) – [Licensing] su | ||
---|---|---|---|
Line 118: | Line 118: | ||
IP Historian supports multiple indexing models depending on the requirements of the data being recorded: | IP Historian supports multiple indexing models depending on the requirements of the data being recorded: | ||
- | * "One Big Index" - optimised for constant or infrequently-changing values. | + | |
- | * "Index per Day/ | + | * "Index per Day/ |
When recording process data, we normally recommend "Index per Month" as the optimal indexing period. | When recording process data, we normally recommend "Index per Month" as the optimal indexing period. | ||
Line 130: | Line 130: | ||
===== System Requirements ===== | ===== System Requirements ===== | ||
+ | |||
+ | See [[app_store_connect: | ||
+ | |||
+ | However, note the system requirements should be adjusted for the particular use-case of the historian. If you intend to support historization of large data volumes and intensive data queries, a more powerful spec is required. Please consult with the Intelligent Plant support team for detailed guidance. | ||
+ | |||
+ | ===== Configuration Best Practice ===== | ||
+ | |||
+ | Details to follow. | ||
+ | |||
Line 139: | Line 148: | ||
+ | ==== How to find your Machine ID ==== | ||
+ | |||
+ | It is necessary to know the Machine ID of your system for licensing to be completed. To find your Machine ID, you must first open App Store Connect and select " | ||
+ | |||
+ | Go to your Data Sources and click " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Under Action, click " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | And at the bottom you will see the Machine ID for your system. | ||
+ | |||
+ | {{: | ||
=====IPHist - IPHist replication===== | =====IPHist - IPHist replication===== | ||
Connections can be setup in datacore to provide reslient transfer of historical data between IPHist instances. this means that a loss in connectivity will not result in a permanent loss of data on the remote IPHist to the datasource. that data will be back filled, and consistent. | Connections can be setup in datacore to provide reslient transfer of historical data between IPHist instances. this means that a loss in connectivity will not result in a permanent loss of data on the remote IPHist to the datasource. that data will be back filled, and consistent. | ||
- | this can be configured by ..? | + | For further information regarding replication and data resilience, contact support@intelligentplant.com. |
=====Other historian - IPHist replication, | =====Other historian - IPHist replication, |
iphist/index.1624868944.txt.gz · Last modified: 2021/06/28 08:29 by su