10 OPC UA DataTypes
10.1 JoiningResultMetaDataType

This structure is a subtype of 5:ResultMetaDataType. It is used to define additional meta data of a Result in a joining system. The structure is defined in Table 193.

Table 193 – JoiningResultMetaDataType Structure

Name

Type

Description

Optional

JoiningResultMetaDataType

structure

Subtype of the 5:ResultMetaDataType defined in OPC 40001-101.

True

JoiningTechnology

0:LocalizedText

It is a human readable text to identify the joining technology.

True

SequenceNumber

0:UInt64

It is the cyclic counter which is incremented for each result generated.

True

Name

0:String

It is the user-friendly name of the result.

Examples: Job Result, Batch Result, etc.

True

Description

0:LocalizedText

It is the additional information associated with the result. It can contain information on the ResultConent.

True

Classification

0:Byte

It provides information on the classification of the result in the joining system. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – SINGLE_RESULT represents a single result.
  • 2 – SYNC_RESULT represents a group of results from a synchronized process.
  • 3 – BATCH_RESULT represents a group of results done with the same program.
  • 4 – JOB_RESULT represents a group of results done with the different programs.
  • 5 – STITCHING_RESULT represents a group of SYNC_RESULT.
  • 6 – INTERVENTION_RESULT represents a result generated due to an intervention during the execution of the operation. Example: Manual Abort.
  • 7 – TEXT_RESULT represents a simple text result of type 0:String.

Note: ResultContent shall be populated with the following options based on the ResultMetaData.Classification value. Refer Annex F for detailed examples.

True

OperationMode

0:Byte

It provides information on how the joining operation was performed. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – AUTOMATIC indicates that the joining operation was performed automatically.
  • 2 – MANUAL indicates that the joining operation was performed manually.

True

AssemblyType

0:Byte

It provides the type of joining operation. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – ASSEMBLED
  • 2 – DISASSEMBLED

True

AssociatedEntities

EntityDataType[]

It is a list of identifiers associated to the given result.

Examples: ProductId, VIN, SocketId, JointId, JoiningProcessId, etc.

True

ResultCounters

ResultCounterDataType[]

It is a list of counters associated to the given result.

Examples: Batch Counter, Retry Counter, Channel Counter, etc.

True

InterventionType

0:Byte

It provides information on type of intervention which has occurred during the joining operation. It has the following pre-defined values which shall be used for each instance of this type.

Note: It is only applicable when the Classification is INTERVENTION_RESULT.

  • 0 – UNDEFINED
  • 1 – OTHER
  • 2 – INCREMENTED
  • 3 – DECREMENTED
  • 4 – BYPASSED
  • 5 – ABORTED
  • 6 – RESET
  • 7 – MANUAL

True

IsGeneratedOffline

0:Boolean

It indicates that the result is generated when the asset was offline. The default value is false.

Note: The definition of offline status is application specific.

Example: Wireless tool performing joining in radio shadow.

True

ExtendedMetaData

KeyValueDataType[]

It is used to send any additional meta data associated with the result. It is intended to be used for future and vendor-specific extensions.

True

Its representation in the AddressSpace is defined in Table 194.

Table 194 – JoiningResultMetaDataType Definition

Attribute

Value

BrowseName

JoiningResultMetaDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of 5:ResultMetaDataType defined in OPC 40001-101.

Conformance Units

IJT Basic Result

IJT Single Result

IJT Result Processing Times

IJT Batch Result

IJT Batch Result Counters

IJT Sync Result

IJT Sync Result Counters

IJT Job Result

IJT Intervention Result

IJT Result Internal Identifiers

IJT Result External Identifiers

IJT Result Extended Meta Data

10.2 JoiningResultDataType

This structure represents the data associated with Joining Result and the corresponding measurement values. The structure is defined in Table 195.

Table 195 – JoiningResultDataType Structure

Name

Type

Description

Optional

JoiningResultDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

FailureReason

0:Byte

It provides the primary reason for failure. If a violation is handled by a rework step resulting in a successful operation, then it is not reported as failure. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – NOT_OK_REASON_UNDEFINED
  • 1 – NOT_OK_REASON_PROGRAM indicates the failure of the operation is due to the violation of global program limits.
  • Note: Refer OverallResultValues if this is the failure reason.
  • 2 – NOT_OK_REASON_STEP indicates the failure of the operation is due to the violation of program step limits.
  • Note: Refer StepResults if this is the failure reason.
  • 3 – NOT_OK_REASON_ERROR indicates the failure of the operation is due to external factors which are outside the boundary of the joining operation. Example: Temperature Overheat, Tool Trigger Lost, etc.
  • Note: Refer Errors list if this is the failure reason.

True

OverallResultValues

ResultValueDataType[]

It is an array of overall result values which contains the measurement values of different quantities like torque, angle, time, etc. based on the program.

Note: If the operation is terminated in the first step and no values are available to report, then this list may be empty.

False

StepResults

StepResultDataType[]

It is an array of step results corresponding to each step in the program. This parameter is used if the system provides one or more step results.

True

Errors

ErrorInformationDataType[]

It is an array of external errors which captures the failures outside the boundary of the program are captured as part of the Errors. It is up to the application to fill in the critical/primary error in the Errors list as top entry.

True

FailingStepResultId

0:TrimmedString

It is the identifier of the step result which is the primary cause of failure.

True

Trace

JoiningTraceDataType

It is a structure to include the Joining Trace content. This can be NULL or empty and it is up to the application to send this as part of the Joining Result.

True

Its representation in the AddressSpace is defined in Table 196.

Table 196 – JoiningResultDataType Definition

Attribute

Value

BrowseName

JoiningResultDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Result Failure Reason

IJT Joining Result Overall Result Values

IJT Joining Result Step Results

IJT Joining Result Errors

IJT Joining Result Trace

IJT Result Content

10.3 ResultValueDataType

It is used to report measurement values of the joining operation. Those are meant to characterize the quality of the process. It is used in JoiningResultDataType and StepResultDataType. The structure is defined in Table 197.

Table 197 – ResultValueDataType Structure

Name

Type

Description

Optional

ResultValueDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

MeasuredValue

0:Double

It is the measured value of the given result. The value corresponds to the PhysicalQuantity attribute of JoiningDataVariableType in the following section 9.1.

False

Name

0:String

It is a user readable name of the given measurement value.

True

ResultEvaluation

5:ResultEvaluationEnum

It indicates whether the measured value is as per the configured limits and corresponds to a successful result or not.

True

ValueId

0:TrimmedString

It is the identifier of the given value if it is available in the system.

True

ValueTag

0:Int16

It is an associated tag to the given measurement value to classify it based on the joining domain. Examples: FINAL, YIELD, SNUG, etc. It has the following pre-defined values which shall be used for each instance of this type.

  • < 0 – application specific extensions.
  • 0 – UNDEFINED
  • 1 – FINAL indicates the final reported measurement value.
  • 2 – TORSION indicates the twisting of the joining system when applying the tightening torque. When a bolt is tightened, it is subjected to tensile stress as preload is introduced but also to torsion stress because of thread friction.
  • 3 – SNUG or SEATING is the reported point where screw head touches the surface and all parts have mated.
  • 4 – YIELD is the yield point is the reported point on a stress-strain curve that indicates the limit of elastic behaviour and the beginning of plastic behaviour.
  • 5 – EXIT indicates a transition value between two steps in a multi-step program.
  • 6 – TRACE_START is the point that represents the offset from the start of the step to the FIRST reported trace value when a given trace is not beginning at the start of the step.
  • 7 – TRACE_END is the point that represents the offset from the start of the step to the LAST reported trace value when a given trace is not beginning at the start of the step.
  • 8 – MAX represents the maximum value of the given measurement.
  • 9 – MIN represents the minimum value of the given measurement.
  • 10 – TOOL_ANGLE_MOVEMENT represents the angle that handheld tool has moved until reaching the FINAL point, as registered by the internal GYRO.

Note: Additional explanations and pictures describing of some of the ValugTag values are provided in Annex C.

True

TracePointIndex

0:Int32

It is the index to the trace sample array from which corresponds to this specific result.

True

TracePointTimeOffset

0:Duration

It is the time offset to point out the absolute time point in the array of trace samples. This may or may not match with an element in the TraceContent array. If it is not available in the TraceContent array, the value can be visualized in the trace graph via interpolation or some other plotting mechanisms.

True

ParameterIdList

0:TrimmedString[]

It is an array of parameter identifiers configured in the Program which is being monitored or sampled.

Note: In most common cases, it can be a single identifier.

True

ViolationType

0:Byte

Indicates whether the measured value is above or below the configured limit. It is only relevant if program or step configuration is violated. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – ABOVE_LIMIT indicates that the measured value is above the configured limit.
  • 2 – BELOW_LIMIT indicates that the measured value is below the configured limit.
  • 3 – NOT_DECIDABLE indicates that the decision is not possible or applicable.

True

ViolationConsequence

0:Byte

It provides information on the consequence occurred due to the violation of the configurable limits. Examples: Step Transition, Abort Joining Operation. Is the consequence repairable or not, etc. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – ABORT
  • 2 – NORMAL_STEP_TRANSITION
  • 3 – REPAIR_STEP_TRANSITION
  • 4 – WARNING

True

SensorId

0:TrimmedString

It is the system-wide unique identifier of the sensor which has reported the value.

True

LowLimit

0:Double

It provides the lower limit of the measured value as per the program.

True

HighLimit

0:Double

It provides the upper limit of the measured value as per the program.

True

TargetValue

0:Double

It provides the target value of the specific measurement in the program step.

True

ResultStep

0:String

It provides the step number or name of the program step which has generated the result.

Note: This is not applicable for StepResultValues in StepResultDataType. This is added for OverallResultValues in JoiningResultDataType to get the information of the step which has reported the specific value.

True

PhysicalQuantity

0:Byte

It is to determine the type of the physical quantity associated to a given value(s). Refer section 9.1 for the pre-defined values.

True

EngineeringUnits

0:EUInformation

It is the engineering unit of the measured value.

True

Its representation in the AddressSpace is defined in Table 198.

Table 198 – ResultValueDataType Definition

Attribute

Value

BrowseName

ResultValueDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Result Value Trace Point Index

IJT Result Value Trace Point Time Offset

IJT Result Value FINAL Tag

10.4 StepResultDataType

This structure represents the measurement values corresponding to a given step in the program. It is used in JoiningResultDataType. The structure is defined in Table 199.

Table 199 – StepResultDataType Structure

Name

Type

Description

Optional

StepResultDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

StepResultId

0:TrimmedString

It is the system-wide unique identifier of the step result.

False

ProgramStepId

0:TrimmedString

It is the system-wide unique identifier of the Program Step.

True

ProgramStep

0:String

It is the step number or name of the program step. Sometimes the step id is like 2A, 3B based on number of branches. Hence a string place holder is needed instead of number.

True

Name

0:String

It is the user-friendly name of the given step. This can be the name of the step in the configuration for ease of use and troubleshooting.

True

ResultEvaluation

5:ResultEvaluationEnum

It indicates if the StepResult is successful or not.

True

StartTimeOffset

0:Duration

It is the offset to the ProcessingTimes.StartTime in Result, this value can be used to order the steps in execution order if same step is run multiple times.

True

StepTraceId

0:TrimmedString

It is the system-wide unique identifier of the StepTrace associated to the StepResult.

True

StepResultValues

ResultValueDataType[]

It is the set of values which needs to be measured as per the program step.

True

Its representation in the AddressSpace is defined in Table 200.

Table 200 – StepResultDataType Definition

Attribute

Value

BrowseName

StepResultDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Result Step Results

IJT Result Value FINAL Tag

10.5 ErrorInformationDataType

This structure represents the errors that have occurred in the system which are outside the boundaries of the given program. It is used in JoiningResultDataType. The structure is defined in Table 201.

Table 201 – ErrorInformationDataType Structure

Name

Type

Description

Optional

ErrorInformationDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

ErrorType

0:Byte

It is the classification of type of errors due to external factors. Examples: Tool Trigger Lost is Operator error. Temperature overheat is hardware error, etc. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – OTHER
  • 2 – HARDWARE
  • 3 – PROCESS
  • 4 – OPERATOR
  • 5 – SYSTEM
  • 6 – SAFETY

False

ErrorId

0:TrimmedString

It is the system-wide unique identifier of the error in the system. This will be useful if system wants to provide an identifier where user can query the system and get more information for troubleshooting. It can also point to the respective EventId reported if available.

True

LegacyError

0:String

It is the application or system specific error code.

True

ErrorMessage

0:LocalizedText

It is user readable text message to describe the error.

True

Its representation in the AddressSpace is defined in Table 202.

Table 202 – ErrorInformationDataType Definition

Attribute

Value

BrowseName

ErrorInformationDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Result Errors

10.6 TraceDataType

It is a base type to encapsulate common data for a Trace. The structure is defined in Table 203.

Table 203 – TraceDataType Structure

Name

Type

Description

Optional

TraceDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

TraceId

0:TrimmedString

It is the system-wide unique identifier of the Trace.

False

ResultId

0:TrimmedString

It is the system-wide unique identifier of the associated result. This is useful to link Result and Trace instances when the Result and Trace are sent separately.

False

Its representation in the AddressSpace is defined in Table 204.

Table 204 – TraceDataType Definition

Attribute

Value

BrowseName

TraceDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Result Trace

10.7 JoiningTraceDataType

This structure is to describe the content of traces for all the steps in the given program. It is used in JoiningResultDataType. The structure is defined in Table 205.

Table 205 – JoiningTraceDataType Structure

Name

Type

Description

Optional

JoiningTraceDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

StepTraces

StepTraceDataType[]

It is an array of StepTraceDataType which provides trace content for each step in the given result.

False

Its representation in the AddressSpace is defined in Table 206.

Table 206 – JoiningTraceDataType Definition

Attribute

Value

BrowseName

JoiningTraceDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the TraceDataType.

Conformance Units

IJT Joining Result Trace

10.8 StepTraceDataType

It is to describe of the trace for a given program step. It is used in JoiningTraceDataType. The structure is defined in Table 207.

Table 207 – StepTraceDataType Structure

Name

Type

Description

Optional

StepTraceDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

StepTraceId

0:TrimmedString

It is the system-wide unique identifier of the step trace.

False

StepResultId

0:TrimmedString

It is the system-wide unique identifier of the associated step result.

False

NumberOfTracePoints

0:UInt32

It is the total number of trace points to be sent for each quantity.

False

SamplingInterval

0:Duration

It is the time between each sample in the given Trace array. This is required if applications want to reduce the amount of data by omitting the StepTraceContent array which represents TIME.

True

StartTimeOffset

0:Duration

It is the offset to the ProcessingTimes.StartTime in the Result instance. This value can be used to order the steps in execution order if same step is run multiple times.

True

StepTraceContent

TraceContentDataType[]

It is an array of trace data which contains the samples of different quantities like torque, angle, time, etc. The array size of TraceContent array should be same for each quantity and that is determined by the NumberOfTracePoints value.

False

Its representation in the AddressSpace is defined in Table 208.

Table 208 – StepTraceDataType Definition

Attribute

Value

BrowseName

StepTraceDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Result Trace

10.9 TraceContentDataType

It is to describe of the trace samples for a given program step. It is used in StepTraceDataType. The structure is defined in Table 209.

Table 209 – TraceContentDataType Structure

Name

Type

Description

Optional

TraceContentDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

Values

0:Double[]

It is an array of trace samples. The values correspond to the PhysicalQuantity attribute.

False

SensorId

0:TrimmedString

It is the system-wide unique identifier of the sensor which has reported the values. This will be useful for identifying the sensor when the same set of samples are reported by multiple sensors.

True

Name

0:String

It is the user-friendly name for the given trace.

True

Description

0:String

It is an additional text to describe the trace samples.

True

PhysicalQuantity

0:Byte

It is to determine the type of the physical quantity associated to a given value(s). Refer section 9.1 for the pre-defined values.

True

EngineeringUnits

0:EUInformation

It is the engineering unit of the values.

True

Its representation in the AddressSpace is defined in Table 210.

Table 210 – TraceContentDataType Definition

Attribute

Value

BrowseName

TraceContentDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Result Trace

10.10 EntityDataType

This structure provides the identification data for a given entity in the system. The structure is defined in Table 211.

Table 211 – EntityDataType Structure

Name

Type

Description

Optional

EntityDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

Name

0:String

It is the name of the entity identifier.

Examples: VIN, Program Id, etc.

Note: Application can send custom names which could be a combination of different terms in the system.

True

Description

0:String

It is the description of the entity. Any additional information for the entity can be sent using this property.

Examples: Name of the program in the given system.

True

EntityId

0:TrimmedString

It is the identifier of the given entity.

Examples: JoiningProcessId, JointId, etc.

False

EntityOriginId

0:TrimmedString

It is the origin identifier of the given entity. It is provided only when it is applicable and available for a given entity.

Examples: JoiningProcessOriginId, JointOriginId, etc.

True

IsExternal

0:Boolean

It indicates if the EntityId is provided by the external system or not.

Example: VIN is provided by an external system.

True

EntityType

0:Int16

It provides the type of the Entity. It has the following pre-defined values which shall be used for each instance of this type.

Important Note: EntityType >=0 is defined as part of this specification.

For application specific extensions, EntityType < 0 can be used.

  • 0 – UNDEFINED
  • 1 – OTHER
  • 2 – ASSET
  • 3 – CONTROLLER
  • 4 – TOOL
  • 5 – SERVO
  • 6 – MEMORY_DEVICE
  • 7 – SENSOR
  • 8 – CABLE
  • 9 – BATTERY
  • 10 – POWER_SUPPLY
  • 11 – FEEDER
  • 12 – ACCESSORY
  • 13 – SUB_COMPONENT
  • 14 – SOFTWARE
  • 15 – RESULT
  • 16 – EVENT
  • 17 – ERROR
  • 18 – SYSTEM
  • 19 – LOG
  • 20 – VEHICLE
  • 21 – PRODUCT
  • 22 – PART
  • 23 – JOINT
  • 24 – MODEL
  • 25 – ORDER
  • 26 – JOINING_PROCESS
  • 27 – PROGRAM
  • 28 – JOB
  • 29 – BATCH
  • 30 – RECIPE
  • 31 – TASK
  • 32 – PROCESS
  • 33 – CONFIGURATION
  • 34 – SOCKET
  • 35 – CHANNEL
  • 36 – STATION
  • 37 – PRODUCTION_LINE
  • 38 – LOCATION
  • 39 – USER
  • 40 – PARENT
  • 41 – VIRTUAL_STATION

False

Its representation in the AddressSpace is defined in Table 212.

Table 212 – EntityDataType Definition

Attribute

Value

BrowseName

EntityDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Result Internal Identifiers

IJT Result External Identifiers

IJT Event Payload Associated Entities

IJT Start Joining Process

10.11 ResultCounterDataType

This structure is used to provide various types of counters associated to a Result. These counters are related to a joining process with sub-processes. The structure is defined in Table 213.

Table 213 – ResultCounterDataType Structure

Name

Type

Description

Optional

ResultCounterDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

Name

0:String

It is the name of the counter.

True

CounterValue

0:UInt32

It is the value of the counter.

False

CounterType

0:Int16

It is the type of the Counter. It has the following pre-defined values which shall be used for each instance of this type.

  • 0 – UNDEFINED
  • 1 – OTHER
  • 2 – BATCH_SIZE
  • 3 – BATCH_COUNT
  • 4 – RETRY_COUNT
  • 5 – SOCKET_NUMBER
  • 6 – CHANNEL_NUMBER is the respective channel number in a fixtured system containing multiple channels. A channel is a servo and spindle together which has an associated identifier or an assigned number.
  • 7 – SPINDLE_NUMBER is the respective spindle number in a fixtured system containing multiple spindles. A spindle is a Tool in a fixtured system.
  • 8 – TOTAL_NUMBER_OF_CHANNELS
  • 9 – TOTAL_NUMBER_OF_SPINDLES
  • 10 – TOTAL_JOINING_PROCESS_SIZE is the total number of elements in the joining process that generated the result.

False

Its representation in the AddressSpace is defined in Table 214.

Table 214 – ResultCounterDataType Definition

Attribute

Value

BrowseName

ResultCounterDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Batch Result Counters

IJT Sync Result Counters

10.12 ReportedValueDataType

This structure provides the given value and corresponding limits for a given physical quantity (if applicable). The structure is defined in Table 215.

Note: It is required that CurrentValue , PreviousValue, LowLimit, HighLimit have the same Engineering Units.

Table 215 – ReportedValueDataType Structure

Name

Type

Description

Optional

ReportedValueDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

PhysicalQuantity

0:Byte

It is the physical quantity of the value. Example: Torque, Angle, etc.

Note: It may not be applicable for few reported values such as Software Version, etc.

True

Name

0:String

It is the name of the given value.

True

CurrentValue

0:BaseDataType

It is the current value. The data type can be any simple data type such as Integer, String, Double, DateTime, etc. If the value is corresponding to the physical quantity, then the recommended data type is Double.

False

PreviousValue

0:BaseDataType

It is the previous value (if available). The data type can be any simple data type such as Integer, String, Double, DateTime, etc. If the value is corresponding to the physical quantity, then the data type should be Double.

True

LowLimit

0:Double

It is the low limit of the given value. It is not applicable for values which does not have PhysicalQuantity.

True

HighLimit

0:Double

It is the high limit of the given value. It is not applicable for values which does not have PhysicalQuantity.

True

EngineeringUnits

0:EUInformation

It is the engineering unit of the CurrentValue, PreviousValue, LowLimit, HighLimit.

It is not applicable for values which does not have PhysicalQuantity.

True

Its representation in the AddressSpace is defined in Table 216.

Table 216 – ReportedValueDataType Definition

Attribute

Value

BrowseName

ReportedValueDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Event Payload Reported Values

10.13 CalibrationDataType

This structure contains the Calibration information. It is used as an input argument in SetCalibration method.

Note: The input data sent in SetCalibration shall be updated in the respective parameters of the asset under Maintenance/Calibration.

The structure is defined in Table 217.

Table 217 – CalibrationDataType Structure

Name

Type

Description

Optional

CalibrationDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

LastCalibration

0:UtcTime

It is the date when the last calibration took place.

Note: It can have the initial operation date for a new asset if it is not available.

False

CalibrationPlace

0:String

It is the location where the last calibration took place.

True

NextCalibration

0:UtcTime

It is the date of the next planned calibration.

True

CalibrationValue

0:Double

It is the actual measured value of the calibration.

True

SensorScale

0:Double

It is the nominal scale of the sensor. It corresponds also with the measurement range of the sensor.

True

CertificateUri

0:UriString

It contains the URI of a certificate of the calibration target in case the calibration target is certified and the information available. Otherwise, the Variable should be omitted. The String shall be a URI as defined by RFC 3986.

Example: MCE test document.

True

EngineeringUnits

0:EUInformation

It defines the engineering unit of the value.

True

Its representation in the AddressSpace is defined in Table 218.

Table 218 – CalibrationDataType Definition

Attribute

Value

BrowseName

CalibrationDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining System Base

10.14 SignalDataType

This structure contains the signal information which is used in SetIOSignals and GetIOSignals methods.

The structure is defined in Table 219.

Table 219 – SignalDataType Structure

Name

Type

Description

Allow Subtypes

SignalDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

SignalId

0:TrimmedString

It is the identifier of the signal.

False

SignalValue

0:Number

It is the value of the signal.

True

SignalDescription

0:String

It is the description of the signal.

False

SignalType

0:Int16

It is the type of the signal. It has the following pre-defined values:

< 0 – vendor specific extensions.

0 – UNDEFINED

1 – INPUT

2 – OUTPUT

3 – BOTH

False

Its representation in the AddressSpace is defined in Table 220.

Table 220 – SignalDataType Definition

Attribute

Value

BrowseName

SignalDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining System Base

10.15 JointDataType

This structure provides the joint information. Joint is the physical outcome of the joining operation which determines the properties of the point where multiple parts are assembled. Refer Annex H for examples.

The structure is defined in Table 221.

Table 221 – JointDataType Structure

Name

Type

Description

Optional

JointDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

JointId

0:TrimmedString

It is the identifier of the joint.

False

JointOriginId

0:TrimmedString

It is an identifier to track the changes made to the original instance in the system.

Example: It can point to the identifier of the object when it was created for the first time. It should be an existing ID in the system if it is available else it can be NULL if it is not tracked in a joining system.

True

JointDesignId

0:TrimmedString

It is the identifier of the associated joint design.

True

CreationTime

0:UtcTime

It is the time when the joint was created.

True

LastUpdatedTime

0:UtcTime

It is the time when the joint was updated last time. If it is not available, it can be same as CreationTime.

True

Name

0:String

It is the name of the joint.

True

Description

0:LocalizedText

It is the description of the joint.

True

Classification

0:Int16

It is the classification of the joint. It has the following pre-defined values.

0 – UNDEFINED

1 – OTHER

2 – CATEGORY_A is high risk, danger to life or environment. (VDI-VDE 2862-2).

3 – CATEGORY_B is medium risk, operational malfunction, or system shutdown. (VDI-VDE 2862-2).

4 – CATEGORY_C is low risk, non-critical. (VDI-VDE 2862-2).

True

ClassificationDetails

0:LocalizedText

It is the details of the classification. It can also be used to provide any other type of classification.

Examples: Safety Critical, etc.

True

JointStatus

0:TrimmedString

It is the status of the joint.

Examples: Ok, InUse, NotInUse, NotYetDone, etc.

True

AssociatedEntities

EntityDataType[]

It is the list of entities associated to the joint.

Examples: JoiningProcessId, JobId, QualityProcessId, SimulationProcessId, etc.

True

JoiningTechnology

0:LocalizedText

It is a human readable text to identify the joining technology.

True

Its representation in the AddressSpace is defined in Table 222.

Table 222 – JointDataType Definition

Attribute

Value

BrowseName

JointDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Send Joint

IJT Get Joint List

IJT Get Joint

IJT Joint Data

10.16 JointDesignDataType

This structure provides the design information of a given joint. Refer Annex H for examples.

The structure is defined in Table 223.

Table 223 – JointDesignDataType Structure

Name

Type

Description

Optional

JointDesignDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

JointDesignId

0:TrimmedString

It is the identifier of the joint design.

False

Name

0:String

It is the name of the joint design.

True

Description

0:LocalizedText

It is the description of the joint design.

True

JointDesignContent

DesignValueDataType[]

It is the list of design values.

True

JointComponentIdList

0:TrimmedString[]

It is the list of joint components associated to the joint design.

Examples: BoltId, RivetId, GasketId, etc.

True

Its representation in the AddressSpace is defined in Table 224.

Table 224 – JointDesignDataType Definition

Attribute

Value

BrowseName

JointDesignDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Send Joint Design

IJT Get Joint Design List

IJT Get Joint Design

IJT Joint Design Data

10.17 JointComponentDataType

This structure is the base container for any joint component such as Bolt, Rivet, Gasket, Glue string, etc.

Note: The concrete definition of joint component is not defined in this version of the specification.

The structure is defined in Table 225.

Table 225 – JointComponentDataType Structure

Name

Type

Description

Optional

JointComponentDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

JointComponentId

0:TrimmedString

It is the identifier of the joint component.

Examples: BoltId, RivetId, GasketId, etc.

False

Name

0:String

It is the name of the joint component.

True

Description

0:LocalizedText

It is the description of the joint component.

True

Manufacturer

0:LocalizedText

It is the manufacturer of the joint component

True

ManufacturerUri

0:String

It is the identifier of the manufacturer.

True

JointComponentContent

0:BaseDataType

It is the content of the joint component.

Examples: Bolt, Rivet, Gasket, etc.

True

Its representation in the AddressSpace is defined in Table 226.

Table 226 – JointComponentDataType Definition

Attribute

Value

BrowseName

JointComponentDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Send Joint Component

IJT Get Joint Component List

IJT Get Joint Component

IJT Joint Component Data

10.18 DesignValueDataType

This structure provides the design value for a given physical quantity. It is used in JointDesignDataType.

The structure is defined in Table 227.

Table 227 – DesignValueDataType Structure

Name

Type

Description

Optional

DesignValueDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

PhysicalQuantity

0:Byte

It is the physical quantity of the value. Example: Force, Angle, etc.

True

Name

0:String

It is the name of the given value.

True

DesignValue

0:BaseDataType

It is the design value. The data type can be any simple data type such as Integer, String, Double, DateTime, etc. If the value is corresponding to the physical quantity, then the data type should be Double.

True

EngineeringUnits

0:EUInformation

It is the engineering unit of the design value.

True

Its representation in the AddressSpace is defined in Table 228.

Table 228 – DesignValueDataType Definition

Attribute

Value

BrowseName

DesignValueDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joint Design Data

10.19 JoiningProcessDataType

This structure provides the base container for any joining process in a joining system.

Note: This specification defines the meta data of a JoiningProcess, and the actual content of the Joining Process is application specific.

The structure is defined in Table 229.

Table 229 – JoiningProcessDataType Structure

Name

Type

Description

Allow Subtypes

JoiningProcessDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

JoiningProcessMetaData

JoiningProcessMetaDataType

It is the meta data of the joining process.

True

JoiningProcessContent

0:BaseDataType[]

It is the actual content of the joining process which is defined by JoiningProcessMetaData.Classification property.

Examples: Joining Program, Joining Job, etc.

Note: The content is application-specific and is not defined in this version of the specification.

False

Its representation in the AddressSpace is defined in Table 230.

Table 230 – JoiningProcessDataType Definition

Attribute

Value

BrowseName

JoiningProcessDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Joining Process Management

IJT Select Joining Process

10.20 JoiningProcessMetaDataType

This structure provides the meta data which describes the joining process.

The structure is defined in Table 231.

Table 231 – JoiningProcessMetaDataType Structure

Name

Type

Description

Optional

JoiningProcessMetaDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

JoiningProcessId

0:TrimmedString

It is the system-wide unique identifier of the joining process.

False

JoiningProcessOriginId

0:TrimmedString

It is an identifier to track the changes made to the original instance in the system.

Example: It can point to the identifier of the object when it was created for the first time. It should be an existing ID in the system if it is available else it can be NULL if it is not tracked in a joining system.

True

CreationTime

0:UtcTime

It is the time when the joining process was created.

True

LastUpdatedTime

0:UtcTime

It is the time when the joining process was updated last time. If it is not available, it can be same as CreationTime.

True

Name

0:String

It is the name of the joining process.

True

Description

0:LocalizedText

It is the description of the joining process.

True

JoiningTechnology

0:LocalizedText

It is a human readable text to identify the joining technology.

True

Classification

0:Int16

It is the classification of the joining process.

< 0 is for vendor specific extensions.

0 – UNDEFINED

1 – OTHER

2 – JOINING_PROGRAM

3 – JOINING_SYNC

4 – JOINING_BATCH

5 – JOINING_JOB

True

AssociatedEntities

EntityDataType[]

It is the list of entities associated to the joining process.

Examples: ProductInstanceUri of the Controller.

True

Its representation in the AddressSpace is defined in Table 232.

Table 232 – JoiningProcessMetaDataType Definition

Attribute

Value

BrowseName

JoiningProcessMetaDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Get Joining Process List

10.21 JoiningProcessIdentificationDataType

This structure contains the identification information of a Joining Process. It is used in set of methods defined in JoiningProcessManagementType.

The structure is defined in Table 233.

Table 233 – JoiningProcessIdentificationDataType Structure

Name

Type

Description

Optional

JoiningProcessIdentificationDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

JoiningProcessId

0:TrimmedString

It is the system-wide unique identifier of the joining process.

True

JoiningProcessOriginId

0:TrimmedString

It is an identifier to track the changes made to the original instance in the system.

Example: It can point to the identifier of the object when it was created for the first time. It should be an existing ID in the system if it is available else it can be NULL if it is not tracked in the system.

True

SelectionName

0:TrimmedString

It is the configured selection name of the joining process in the system.

True

Its representation in the AddressSpace is defined in Table 234.

Table 234 – JoiningProcessIdentificationDataType Definition

Attribute

Value

BrowseName

JoiningProcessIdentificationDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Abort Joining Process

IJT Start Selected Joining

IJT Select Joining Process

IJT Deselect Joining Process

IJT Reset Joining Process

IJT Increment Joining Process Counter

IJT Decrement Joining Process Counter

IJT Set Joining Process Size

IJT Start Joining Process

10.22 KeyValueDataType

This structure is similar to 0:KeyValuePair which uses 0:TrimmedString instead of 0:QualifiedName. The structure is defined in Table 233.

Table 235 – KeyValueDataType Structure

Name

Type

Description

Optional

KeyValueDataType

structure

Subtype of the 0:Structure defined in OPC 10000-5.

Key

0:TrimmedString

It is the key of the value.

False

Value

0:BaseDataType

It is the value associated with the key.

False

Its representation in the AddressSpace is defined in Table 234.

Table 236 – KeyValueDataType Definition

Attribute

Value

BrowseName

KeyValueDataType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of the 0:Structure defined in OPC 10000-5.

Conformance Units

IJT Result Extended Meta Data