Search

Scope: Core (OPC-10000-*) All specs

20 result(s) for Historian

OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

3.1.3 Historian

Historian application storing time series data and/or time series events
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.2 Data architecture

and/or historical Event sources. Figure 1 - Possible OPC UA Server supporting Historical Access The Historian can be implemented as a standalone OPC UA Server that collects data from another ... Server or another data source. The Historian can also just aggregate historical data from underlying Historians . The Client that references the OPC UA Server supporting Historical Access for historical data
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.3 Historians and interruption of data collection

Historians and interruption of data collection When an Historian is collecting and storing data, the data collection can be interrupted. The interruption can have been for collecting the current values ... value or an interruption of the forwarding of historical data from an underlying Historian . The interruption can also have been due to an action that stopped the collection of HistoricalData
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.4 Modification of Historical Data/Events

Modification of Historical Data/Events A Historian collects values (data or Events ) and provides long term storage of these values. Occasionally data that is collected is incorrect. It can be incorrect ... data, even though it can be inserted using an HistoryUpdateDetails service call, the Historian does not have to create a modification record for the initial insertion. Modification of Events
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.5 Timestamps

These Servers can have a mix of data, some with ServerTimestamp some without. The Historian may not know if a HistoricalDataNode supports ServerTimestamps . As a result of this uncertainty
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.6 Bounding Values and time domain

BoundingValues are requested varies according to which of these parameters are provided. For a Historian that has values stored
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.7 Changes in AddressSpace over time

audit events are supported, an audit Event of AuditHistoryConfigurationChangeEventType shall be generated. A Historian shall expose the Historizing attribute on any nodes that are currently collecting historical data. They shall
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.4.2 HistoricalEventFilter Property

HistoricalEventFilter Property can be used as a guideline for what Event fields the Historian is currently storing. But this field may have no bearing on what Event fields the Historian
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.4.3 HistoricalEventConfigurationType

entry point to browse to all EventTypes that can be stored by the Historian . For all EventTypes listed in this folder, all mandatory items in the listed type shall
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.5.1 General

configuration is vendor specific. Some Historians collect information from other OPC UA Servers. The Historian can mirror the point in their own information models and use the HasCurrentData
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.5.2 External Historical Event Node

External Historical Event Node Instances of this ObjectType are used in a Historian to indicate the historical collection related details of an event stream that is being sourced from another ... configuration shall apply. The following optional information can be provided to describe how the Historian connects to receive the event stream: Server is a URI that represents a logical name
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.6.1 Overview

Overview Subclause 5.6 provides examples of Historian instance configuration. It includes both HistoricalData and HistoricalEvent configuration, both internally collected data and externally sourced data
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.6.3 Historical data

Historical data The following example illustrates a Historian that obtains values for a HistoricalData node from another Server. Figure 4 - Example Historizing External Data Source The Pressure Variable
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.6.5 Historical Events

provides an illustration of information related to Event sources that are in a Historian , where the events are being source from external Servers . Figure 6 - Event History configuration example
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.7.3 Default configuration

nodes. If the configuration of individual nodes is not provided for all nodes, the Historian shall expose a default instance under the Server Object. If HistoricalDataNodes exist without a referenced
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.8.10 AuditHistoryBulkInsertEventType

used for tracking a bulk insertion of HistoricalData or HistoricalEvents into a Historian . This Event should not be generated for a given Node more frequently than once per minute, even
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.4 Arrays, index ranges and substrings

arrays. Optional ConformanceUnits exist to indicate if they support storage of arrays. If a Historian does store arrays, it may not support returning an index range in an array ... only provide the entire array. ConformanceUnits are provided to indicate if a Historian supports index ranges. For ReadProcessedDetails, some Aggregates do not support arrays (see 6.5.4 for details
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.2 Read Event functionality

EventType are available for real time updating, but not available from the Historian . In this case a StatusCode value will be returned for any Event field that cannot be returned
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.4 Read modified functionality

EventType are available for real time updating, but not available from the Historian . In this case a StatusCode value will be returned for any Event field that cannot be returned
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.4.2 Insert event functionality

required fields is not provided then the statusCode shall indicate Bad_ArgumentsMissing . If the historian does not support archiving the specified EventType then the statusCode shall indicate Bad_TypeDefinitionInvalid ... fields which are not valid for the EventType or cannot be saved by the Historian then the related operationResults entry shall indicate Good_DataIgnored . Additional information about the ignored fields