iphist:index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
iphist:index [2021/06/28 07:26] – su | iphist:index [2021/08/16 12:15] – [System Requirements] su | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | Intelligent Plant' | + | Intelligent Plant' |
+ | |||
+ | For many data sources (such as Modbus, MQTT, and more), it is possible | ||
+ | |||
+ | Additionally, | ||
- | eg. Modbus, OPC, MQTT, etc.. The majority of data can all be automatically recorded and mostly filtered with default exception and compression rules. | ||
=====How Historians Work - Exception and Compression===== | =====How Historians Work - Exception and Compression===== | ||
Line 18: | Line 22: | ||
===== Data Query Types ===== | ===== Data Query Types ===== | ||
+ | |||
+ | IP Historian supports a number of different types of data queries. | ||
==== Snapshot ==== | ==== Snapshot ==== | ||
Line 38: | Line 44: | ||
==== Values-at-Times ==== | ==== Values-at-Times ==== | ||
- | A values-at-times query is used to retrieve the value of a tag at specified points in time. IPHist | + | A values-at-times query is used to retrieve the value of a tag at specified points in time. IP Historian |
==== Aggregated ==== | ==== Aggregated ==== | ||
- | Aggregated queries can be used to perform ad hoc processing and filtering of raw historical data based on a query time range and sample interval. | + | Aggregated queries can be used to perform ad hoc processing and filtering of raw historical data based on a query time range and sample interval. |
== ANNOTATIONCOUNT == | == ANNOTATIONCOUNT == | ||
Line 98: | Line 104: | ||
- | =====Archiving Model===== | + | ==== Annotations ==== |
+ | |||
+ | IP Historian allows annotations to be recorded against tags at specific points in time. Annotations can be used to track or highlight events a tag value exceeding an operating limit, an action taken as part of a workflow, and so on. | ||
+ | |||
+ | |||
+ | ==== Specifying Query Time Ranges ==== | ||
+ | |||
+ | As part of the Data Core data connectivity layer, IP Historian can accept query time ranges specified as both absolute timestamps (using standard ISO 8601 formatting), | ||
+ | |||
+ | |||
+ | ===== Archiving Model ===== | ||
+ | |||
+ | 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/ | ||
+ | |||
+ | When recording process data, we normally recommend "Index per Month" as the optimal indexing period. | ||
+ | |||
+ | |||
+ | ===== Backing Up ===== | ||
+ | |||
+ | Indexes can be backed up and restored on another IP Historian instance. | ||
+ | |||
+ | |||
+ | ===== System Requirements ===== | ||
+ | |||
+ | See [[app_store_connect: | ||
- | IPHist supports | + | 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. |
- | A Single index for all data (recommended for constants, or values that change infrequently) | + | ===== Configuration Best Practice |
- | An index per year, month, etc.. | + | |
- | we normally recommend index per month as the indexing period for process data. | + | |
- | =====Backing Up===== | + | |
- | Indexes can be backed up and restored on another IPHist instance, | + | Details to follow. |
- | =====System Requirements===== | + | |
- | =====Licensing===== | ||
+ | ===== Licensing ===== | ||
- | IPHist instances that are connected | + | When connecting IP Historian |
- | The free 1000 tag license | + | |
- | Instances | + | IP Historian deployments |
iphist/index.txt · Last modified: 2022/08/29 12:05 by su