Search

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

44 result(s) for Aggregates

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

3.2 Specification parts

Certificate management , key credential management, and authorization services. Part 13 ( OPC 10000-13 ) - Aggregates Part 13 specifies how to compute and return aggregates like minimum, maximum, average etc. Aggregates
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.6 Aggregates ReferenceType

Aggregates ReferenceType The Aggregates ReferenceType is an abstract ReferenceType ; only subtypes of it can be used. It is a subtype of HasChild . The semantic is to indicate a part
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.11 Organizes ReferenceType

used to span multiple hierarchies independent of any hierarchy created with the non-looping Aggregates References . The SourceNode of References of this type shall be an Object , ObjectType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.2 Notation

name is used as the role name, identifying the direction of the Reference (e.g. Aggregates has the subtype HasComponent ). For simplicity, the inverse role name is not shown
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.22.4 AggregateFilter

time that is in the past when received from the Server . The number of Aggregates to be calculated in the past should not exceed the queueSize defined in the MonitoringAttributes ... same boundary (startTime + revisedProcessingInterval * n = revisedStartTime). That behaviour simplifies accessing historical values of the Aggregates using the same boundaries by calling the HistoryRead service. The extensible Parameter AggregateFilterResult is used
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

A.2 BNF of RelativePath

period (dot) character indicates that the Server is to follow any subtype of a Aggregates ReferenceType . <[#!ns:]ReferenceType> A string delimited by the '<' and '>' symbols specifies ... hierarchical Reference with target BrowseName = "3:Truck" and from there a forward Aggregates Reference to a target with BrowseName "0:NodeVersion". "<1:ConnectedTo
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

1 Scope

specified in OPC 10000-4 . This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.2.2 HistoricalDataConfigurationType

Object is required to be present even if it contains no Aggregate configuration Objects . Aggregates are defined in OPC 10000-13 . AggregateFunctions is an entry point to browse ... supported by the Server should be able to be browsed starting from this Object . Aggregates are defined in OPC 10000-13 . The Stepped Variable specifies whether the historical data
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.7.2 HistoryServerCapabilitiesType

Boolean PropertyType Optional ConformanceUnits Historical Access Read Raw Historical Access Time Instance Historical Access Aggregates Historical Access Events All UA Servers that support Historical Access shall include an instance ... supported by the Server should be able to be browsed starting from this Object . Aggregates are defined in OPC 10000-13 . If the Server does not support Aggregates the Folder
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.4 Arrays, index ranges and substrings

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). If the Historian does not support index
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.4.1 ReadProcessedDetails structure details

defined. aggregateType[] NodeId The NodeId of the HistoryAggregate object that indicates the list of Aggregates to be used when retrieving the processed history. See OPC 10000-13 for details. AggregateConfiguration ... TypeDefinition Other Subtype of the HistoryReadDetails defined in Table 28 Conformance Units Historical Access Aggregates
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.4.2 Read processed functionality

interpret such a case. If the ProcessingInterval is specified as 0 then Aggregates shall be calculated using one interval starting at startTime and ending at endTime . The aggregateType[] parameter allows ... Client to request multiple Aggregate calculations per requested NodeId. If multiple Aggregates are requested then a corresponding number of entries are required in the NodesToRead array. For example, to request
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

3.1.7 bounding values

bounding values values at the startTime and endTime needed for Aggregates to compute the result Note 1 to entry: If Raw data does not exist at the startTime and endTime
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.1 General

buffered real time data in the OPC Unified Architecture. This includes the definition of Aggregates used in processed data retrieval and in historical retrieval. This definition includes both standard Reference
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.2.1.2 AggregateConfigurationType

details on using this Variable when assigning StatusCodes . For details on which Aggregates use the PercentDataBad Variable , see the definition of each Aggregate . The default value is 100. The PercentDataGood ... details on using this Variable when assigning StatusCodes . For details on which Aggregates use the PercentDataGood Variable , see the definition of each Aggregate . The default value is 100. The following
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.2.2.1 General

General This Object is used as the browse entry point for information about the Aggregates supported by a Server . The content of this Object is already defined by its type ... ModellingRule HasTypeDefinition Object Type FolderType Defined in OPC 10000-5 Conformance Units Historical Access Aggregates Each ServerCapabilities and HistoryServerCapabilitiesType Object shall reference an AggregateFunction Object . In addition, each HistoricalConfiguration Object
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.2.2.2 AggregateFunctionType

Rule Subtype of the BaseObjectType defined in OPC 10000-5 Conformance Units Historical Access Aggregates For the AggregateFunctionType , the Description Attribute (inherited from the Base NodeClass ) , is mandatory. The Description ... Values . AnnotationCount Retrieve the number of Annotation s in the interval (applies to Historical Aggregates only). StandardDeviationSample Retrieve the standard deviation for the interval for a sample of the population
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.3.1 MonitoredItem AggregateFilter Defaults

MonitoredItem AggregateFilter Defaults The default values used for MonitoredItem Aggregates are the same as those used for historical Aggregates . They are defined in 4.2.1.2 . For additional information on MonitoredItem AggregateFilter
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.3.2 MonitoredItem Aggregates and Bounding Values

MonitoredItem Aggregates and Bounding Values When calculating MonitoredItem Aggregates that require the use of Bounding Values , the bounds may not be known. The calculation is done in the same manner
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.1 General

General OPC 10000-4 specifies all Services needed for OPC UA Aggregates . In particular: The Browse Service Set or Query Service Set to detect Aggregates and their configuration. The HistoryRead
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.2.2 ReadProcessedDetails structure overview

values. aggregateType[] The NodeIds of the AggregateFunction Objects . AggregateFunction Objects indicate the list of Aggregates to be used when retrieving processed history. aggregateConfiguration Aggregate configuration structure. useServerDefaults If True
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.2.3 AggregateFilter structure overview

first time. aggregateType The NodeIds of the AggregateFunction Objects that indicates the list of Aggregates to be used when retrieving processed data. processingInterval The period to be used to compute
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.3.1 Overview

defines additional codes and rules that apply to the StatusCode when used for Aggregates . The general structure of the StatusCode is specified in OPC 10000-4 . It includes ... common operational result codes which also apply to Aggregates
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.3.2 Operation level result codes

Operation level result codes In OPC UA Aggregates the StatusCode is used to indicate the conditions under which a value or Event was stored, and thereby can be used ... important to note, that these are the codes that are specific for OPC UA Aggregates and that they supplement the codes that apply to all types of data; they
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.3.3.2 Partial Information bit

after the interval with a Partial bit will be flagged Bad_NoData. For those Aggregates with extrapolation, the Partial bit may be set. See the Aggregate specific characteristics for more
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.1 General

subclause 5.4 is to detail the requirements and behaviour for OPC UA Servers supporting Aggregates . The intent is to standardize the Aggregates so users can reliably predict the results ... Aggregate computation and understand its meaning. If users require custom functionality in the Aggregates , those Aggregates should be written as custom vendor defined Aggregates . The standard Aggregates shall
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.2.2 Generating intervals

Generating intervals To read Historical Aggregates , OPC clients shall specify three time parameters: startTime (Start) endTime (End) ProcessingInterval (Int) The OPC Server shall use these three parameters to generate ... Start and End time combination. The range is defined to be |End - Start|. All Aggregates return a timestamp of the start of the interval unless otherwise noted for the particular
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.2.3 Data types

Data types Table 50 outlines the valid DataType for each Aggregate . Some Aggregates are intended for numeric data types - i.e. integers or real/floating point numbers. Dates, strings, arrays ... supported. Other Aggregates are intended for digital data types - i.e. Boolean or enumerations. In addition some Aggregates may return results with a different DataType than those used to calculate
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.2.4 Time calculation issues

Time calculation issues The following issues may come up when calculating Aggregates that include time as part of the calculation. All Aggregate calculations include the startTime but exclude the endTime
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.1 General

Server shall create one Aggregate value for the entire time range. This allows Aggregates over large periods of time. A value with a timestamp equal to endTime will be excluded
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.15 Minimum2

Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . If a bounding value is returned then the status will indicate, Raw, Calculated or Interpolated
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.16 Maximum2

Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . If a bounding value is returned then the status will indicate, Raw, Calculated or Interpolated
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.17 MinimumActualTime2

Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . If a bounding value is returned then the status will indicate, Raw, Calculated or Interpolated
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.18 MaximumActualTime2

Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . If a bounding value is returned then the status will indicate, Raw, Calculated or Interpolated
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.19 Range2

maximum and minimum values in the interval as returned by the Minimum2 and Maximum2 Aggregates . Note that the range is always zero or positive. Table 67 - Range2 Aggregate summary Range2
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.21 Count

Aggregate StatusCode is determined using the StatusCode Calculation (see 5.4.3 ) for non-time based Aggregates . If no Good data exists for an interval, the count is zero. Unless otherwise indicated
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.22 DurationInStateZero

Aggregate StatusCode is determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . Duration is in milliseconds. Unless otherwise indicated, StatusCodes are Good, Calculated. Table 70 - DurationInStateZero Aggregate summary
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.23 DurationInStateNonZero

Aggregate StatusCode is determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . Duration is in milliseconds. Unless otherwise indicated, StatusCodes are Good, Calculated. Table 71 - DurationInStateNonZero Aggregate summary
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.24 NumberOfTransitions

Aggregate StatusCode is determined using the StatusCode Calculation (see 5.3 ) for non-time based Aggregates . The earliest transition shall be calculated by comparing the earliest non-Bad value
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.30 DeltaBounds

Aggregate defined in Table 78 returns the difference between the StartBound and the EndBound Aggregates with the exception that both the start and end shall be Good
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.37 StandardDeviationSample

Good values were ignored, the Aggregate quality is uncertain/subnormal. All interval Aggregates return timestamp of the start of the interval. Unless otherwise indicated, qualities are Good, Calculated . This calculation
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.39 StandardDeviationPopulation

Good values were ignored, the Aggregate quality is uncertain/subnormal. All interval Aggregates return timestamp of the start of the interval. Unless otherwise indicated, qualities are Good, Calculated . This calculation
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

9.2.1 MadeUpOf

abstract ReferenceType that cannot be used directly. It is a subtype of Aggregates . Table 79 - MadeUpOf ReferenceType Attributes Value BrowseName MadeUpOf InverseName ContainedBy Symmetric False IsAbstract True References NodeClass BrowseName ... Comment Subtype of Aggregates ReferenceType defined in OPC 10000-5 This ReferenceType is used to describe a shared aggregation. The SourceNode contains the TargetNodes . The SourceNode of this ReferenceType shall
OPC-30060 – OPC UA for Tobacco Machine Communication

8.19.1 Overview

TMCDeviceType, i.e. inheriting the Instance Declarations of that Node. 0:HasComponent Object Aggregates ControlModuleAggregatesType O 0:HasComponent Object Configuration ControlModuleConfigurationType M 0:HasComponent Object LiveStatus ControlModuleLiveStatusType M 0:HasComponent Object ... Setup ControlModuleSetupType O Conformance Units TMC Basic Visualisation and Control BrowseName Description Aggregates Aggregates contains aggregate information for the control module e.g., running hours for a motor. Configuration Configuration provides