The TextileTestingDeviceType is the main entry point for the functionality of the TTD.

The TextileTestingDeviceType is formally defined in Table 15.

Table 15 – TextileTestingDeviceType Definition

Attribute

Value

BrowseName

TextileTestingDeviceType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of 0:BaseObjectType defined in OPC 10000-5

0:HasProperty

Variable

AvailableExchangeableParts

ExchangeablePartDataType[]

0:PropertyType

M

0:HasAddIn

Object

2:Identification

3:MachineIdentificationType

M

0:HasProperty

Variable

InstalledTesterModules

OptionalModuleDataType[]

0:PropertyType

M

0:HasComponent

Object

MachineStatistics

MachineStatisticsType

M

0:HasAddIn

Object

3:MachineryBuildingBlocks

0:FolderType

M

0:HasComponent

Object

6:Notification

6:NotificationType

M

0:HasComponent

Object

RecipeManagement

RecipeManagementType

M

0:HasProperty

Variable

TestProcedureIds

TestProcedureIdDataType[]

0:PropertyType

M

Conformance Units

TTD_TextileTestingDeviceType

AvailableExchangeableParts is an array holding the available exchangeable parts of the TTD.

2:Identification is the entry point for the MachineIdentification.

InstalledTesterModules is an array that stores the optional modules for the TTD.

MachineStatistics holds the machine statistics for the TTD.

3:MachineryBuildingBlocks contains all machinery building blocks. See for More Information.

6:Notification is the main entry point for upcoming events from the device. It also contains different tasks like calibration that have to be performed on the TTD. The NotificationType is inherited from OPC 40501-1.

RecipeManagement is the entry point for the recipe management on the TTD.

ResultManagement is the entry point for the result management on the TTD.

TestProcedureIds is an array that contains the IDs of the test procedures of the TTD.

The components of the TextileTestingDeviceType have additional references which are defined in Table 16.

Table 16 – TextileTestingDeviceType Additional References

SourceBrowsePath

Reference Type

Is Forward

TargetBrowsePath

3:MachineryBuildingBlocks

0:HasAddIn

true

2:Identification

The components of the TextileTestingDeviceType have additional subcomponents which are defined in Table 17.

Table 17 – TextileTestingDeviceType Additional Subcomponents

Source Path

Reference

NodeClass

BrowseName

DataType

TypeDefinition

Others

3:MachineryBuildingBlocks

0:HasAddIn

Object

3:MachineryItemState

3:MachineryItemState_StateMachineType

M

3:MachineryBuildingBlocks

0:HasAddIn

Object

3:MachineryOperationMode

3:MachineryOperationModeStateMachineType

M

3:MachineryBuildingBlocks

0:HasAddIn

Object

8:JobManagement

8:JobManagementType

M

3:MachineryBuildingBlocks

0:HasAddIn

Object

4:ResultManagement

TTDResultManagementType

M

MachineryItemState is the entry point for the MachineryItemState statemachine and holds the state of the TTD.

MachineryOperationMode is the entry point for the MachineryOperationMode statemachine and holds the operation mode of the TTD.

JobManagement is the entry point for the job management for the TTD.

OPC 10031-4 defines mechanisms to add job order information using the 7:ISA95JobOrderDataType and mechanisms getting the result or current status of the job order using the 7:ISA95JobResponseDataType. Both DataTypes define arrays of properties of a job order: general, personal, equipment, physical assets, and material. The 7:ISA95JobOrderDataType uses the general properties to describe the job order and the other properties to define the requirements, whereas the 7:ISA95JobResponseDataType uses the general properties to describe the output and the other properties to provide the information what has been used.

OPC UA Machinery Job Management (OPC 40001-3) standardizes some of those parameters, which are application-specific from the view of OPC 10031-4.

The guidelines and extensions specified in this section are designed to complement the foundational models, providing a structured framework for implementation. The Optional element (e.g. fields or parameters) of the OPC 10031-4 or OPC 40001-3 may be used as defined.

Table 18 – Predefined 7:ISA95JobOrderDataType/JobOrderParameters

Key

DataType

Description

Engineering Units

Sub-parameters

Others

RecipeId

RecipeIdDataType

The available Recipes are stored on the TTD and referenced by their Id.

-

-

M

NumberOfTests

TestNumDataType[]

This array contains TestNumDataType structures that describe how many tests per procedure have to be performed.

-

-

M

SampleInfos

SampleInfoDataType[]

This array contains SampleInfoDataType structures that hold the information about the samples that have to be tested.

-

-

M

CarrierTypeId

0:String

Id to identify the creel geometry or the geometry of the fiber container.

-

-

M

CarrierId

0:String

Id of the fiber container or carrier/creel. For creels it represents the number of the creel wagon.

-

-

M

AdditionalInfos

0:KeyValuePair[]

A set of key/value pairs that define additional information for the job.

-

-

O

Scheduled

0:Boolean

Indicates if a job was scheduled by a remote client (MES).

-

-

M

Table 19 – Predefined 7:ISA95JobResponseDataType/JobResponseData

Key

DataType

Description

Engineering Units

Sub-parameters

Others

TesterJobId

0:String

TTD-internal id given to the tested set of samples(job).

-

-

M

TotalInitializingTime

0:Duration

The total time in ms the job was initializing. The initializing time starts/resets when the job enters the AllowedToStart state and stops when the job enters the Running or Aborted state.

-

-

M

TotalInterruptedTime

0:Duration

The Time in ms the job was interrupted

-

-

M

TotalRunningTime

0:Duration

the total time in ms the job was running

-

-

M

Additional to the listed Keys the Fields StartTime and EndTime are Mandatory in the JobResponseDataType.