It is the user-friendly name of the result.

Examples: Job Result, Batch Result, etc.

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.

Classification = SINGLE_RESULT

ResultContent = An instance of JoiningResultDataType

Classification = BATCH_RESULT or SYNC_RESULT or JOB_RESULT or STITCHING_RESULT

ResultContent = One or more instances of ResultDataType where each element in the ResultContent is a sub-result of the parent Result.

Classification = INTERVENTION_RESULT

ResultContent = NULL or an instance of JoiningResultDataType if any measurement values are available.

Classification = TEXT_RESULT

ResultContent = One or more instances of 0:String.

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.

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

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

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

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

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

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

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.

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.

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 or values which are common for multiple steps.

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

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 value sampled when the decision for the step transition is made.

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.

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.

11 – AVERAGE is the average value.

12 – EXIT_TRIGGER indicates that this value triggered the step transition.

13 – FIRST

14 – RUNDOWN

15 – PREVAILING

16 – SELFTAP

17 – SHUTOFF

18 – RESIDUAL

19 – RESCINDING

20 – PULSE_COUNT

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

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.

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.

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

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 information of the step which has reported the specific value.

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

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.

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.

It is the identifier of the given entity.

Examples: JoiningProcessId, JointId, etc.

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.

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

Example: VIN is provided by an external system.

It provides the type of 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

42 – JOINT_COMPONENT

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.

11 – JOB_SIZE is the number of immediate sub-joining processes.

12 – JOB_COUNT is incremented after the sub-joining process is completed.

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

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

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

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

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.

NextCalibration

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.

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

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.

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).

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

Examples: Safety Critical, etc.

It is the status of the joint.

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

It is the list of entities associated to the joint.

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

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

Examples: BoltId, RivetId, GasketId, etc.

It is the identifier of the joint component.

Examples: BoltId, RivetId, GasketId, etc.

It is the content of the joint component.

Examples: Bolt, Rivet, Gasket, etc.

Note: The content is application specific.

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.

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.

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

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

Examples: ProductInstanceUri of the Controller.

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.