Search

19 result(s) for HistoricalDataNode

• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  3.1.5 HistoricalDataNode
  HistoricalDataNode Variable or Property in the AddressSpace where a Client can access historical data Note 1 to entry: A HistoricalDataNode represents any Variable or Property in the AddressSpace for which ... Client can read and/or update historical data. " HistoricalDataNode history" or "history of a HistoricalDataNode " refers to the time series data stored for this HistoricalNode . Examples
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  3.1.7 ModifiedValues
  ModifiedValues HistoricalDataNode ' s value that has been changed (or manually inserted or deleted) after it was stored in the historian Note 1 to entry: For some Servers , a lab data ... historical Services operate on the current, or most recent, value for the specified HistoricalDataNode at the specified timestamp. Requests for ModifiedValues are used to access values that have been superseded
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  3.1.8 RawData
  RawData data that is stored within the historian for a HistoricalDataNode Note 1 to entry: The data can be all data collected for the DataValue or it can be some
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.3 Historians and interruption of data collection
  then no data was lost and nothing needs to be stored indicating the given HistoricalDataNode 's data collection was interrupted. But if the SourceTimestamp of the initial value is later
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.5 Timestamps
  data, some with ServerTimestamp some without. The Historian may not know if a HistoricalDataNode supports ServerTimestamps . As a result of this uncertainty, the Bad_TimestampNotSupported can be returned
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  details on access levels). If the HistoricalConfiguration of a HistoricalDataNode in the AddressSpace is changed and audit events are supported, an audit Event of AuditHistoryConfigurationChangeEventType shall be generated. A Historian
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.1.2 Annotations Property
  Annotations Property is used to indicate that the history collection exposed by a HistoricalDataNode supports Annotation data. Annotation DataType is defined in 6.6.6 . ConformanceUnits Historical Access Annotations Since ... only available for DataVariables or Objects . The Annotations Property shall be present on every HistoricalDataNode that supports modifications, deletions, or additions of Annotations whether or not Annotations currently exist. Annotation
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.2 HistoricalDataConfigurationType
  defines the general characteristics of a Node that defines the historical configuration of any HistoricalDataNode that is defined to contain history. It is formally defined in Table 3 . Instances ... vendor-specific, human readable string that specifies how the value of this HistoricalDataNode is calculated. Definition is non-localized and will often contain an equation that can be parsed
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.4 Historical Data Configuration Object
  Configuration Object This Object is used as the browse entry point for information about HistoricalDataNode configuration. The content of this Object is already defined by its type definition in Table ... formally defined in Table 6 . If a HistoricalDataNode has configuration defined then one instance shall have a BrowseName of 'HA Configuration'. Additional configurations can be defined with different BrowseNames
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.3.3 HasCurrentData ReferenceType
  subtype of the NonHierarchicalReferences ReferenceType and will be used to refer from a HistoricalDataNode to a Node that is the source of the data being historized by the Source Node ... specified in Table 8 . The Source node of this reference type shall be a HistoricalDataNode. The Target node shall be any Variable or Property Table 8 - HasCurrentData ReferenceType Attributes Value
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.2 HistoricalDataNodes Address Space Model
  that includes History. Figure 3 - Historical Variable with Historical Data Configuration and Annotations Each HistoricalDataNode with history shall have the Historizing Attribute (see OPC 10000-3 ) defined and can reference ... HistoricalAccessConfiguration Object . In the case where the HistoricalDataNode is itself a Property then the HistoricalDataNode inherits the values from the parent node of the Property . Not every Variable
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.2 HistoryServerCapabilitiesType
  maximum number of values that can be returned by the Server for each HistoricalDataNode accessed during a request. A value of 0 indicates that the Server forces no limit
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.3 Default configuration
  This specification defines a manner of exposing the configuration associated with a HistoricalNode (both HistoricalDataNode and HistoricalEventNode ), but this configuration is not required for all nodes. If the configuration
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.10 AuditHistoryBulkInsertEventType
  NodeId that had a bulk insert of historical information. It can be a HistoricalDataNode or a HistoricalEventNode . StartTime is the oldest time of the block that was inserted. EndTime
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.3 Continuation Points
  only used to maintain the state information for the Server to continue from. For HistoricalDataNode requests, a Server can use the timestamp of the last returned data item
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.5.2 Delete raw functionality
  more HistoricalDataNodes . If no data is found in the time range for a particular HistoricalDataNode , then the StatusCode for that item is Bad_NoData
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.5.3 Delete modified functionality
  more HistoricalDataNodes . If no data is found in the time range for a particular HistoricalDataNode , then the StatusCode for that item is Bad_NoData
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.1 General
  Object shall reference an AggregateFunction Object . In addition, each HistoricalConfiguration Object belonging to a HistoricalDataNode may reference an AggregateFunction Object using the HasComponent Reference
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.1 General
  StatusCode . If a requested timestamp is not supported in any other way for a HistoricalDataNode , the operation shall return the Bad_TimestampNotSupported StatusCode . For MonitoredItem the Server shall not return