The TTDResultManagementType provides mechanisms to access results generated by the TTD. Basically this is a subtype of the 4:ResultManagementType enforcing the implementation of different methods and objects for the result transfer mechanisms that should be used on the TTD. In general, we want to accomplish the following tasks:

The TTDResultManagementType is formally defined in Table 35.

Table 35 – TTDResultManagementType Definition

Attribute

Value

BrowseName

TTDResultManagementType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 4:ResultManagementType defined in OPC 40001-101

0:HasComponent

Object

4:Results

0:FolderType

M

0:HasComponent

Object

4:ResultTransfer

4:ResultTransferType

M

0:HasComponent

Method

4:GetResultById

M

0:GeneratesEvent

ObjectType

TTDResultReadyEventType

Conformance Units

TTD_TTDResultManagementType

4:Results is a folder that is used to organize available results of the system. It is supposed to store variables of the 4:TTDResultType. A 4:ResultType contains the 4:ResultMetaData (see subtype TTDResultMetaDataType) used to identify the result and optional an data based 4:ResultContent or 4:ReducedResultContent. The ResultContent may be of any DataType but typically it is a field of StatisticResultContent defined in this specification or a 0:ByteString of any raw data.

4:ResultTransfer is used to transfer the content of a result by a temporary file transfer. The file that is to be transferred is identified by its ResultId.

4:GetResultById is used to retrieve a result (4:ResultDataType) from the TTD.

Table 36 – TTDResultManagementType Additional Subcomponents

BrowsePath

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

4:Results

0:HasComponent

Variable

4:<ResultVariable>

4:ResultDataType

TTDResultType

OP