8 OPC UA ObjectTypes

8.1 MachineModuleType ObjectType

8.1.1 Overview

The MachineModuleType represents a machine module or workcentre and is formally defined in the following table.

Table 12 – MachineModuleType Definition
Attribute Value
BrowseNameMachineModuleType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectConfigurationMachineModuleConfigurationTypeM
0:HasComponentObjectControlModules0:FolderTypeO
0:HasComponentObjectDefectDetectionSensors0:FolderTypeO
0:HasComponentObjectEquipmentModules0:FolderTypeO
0:HasComponentObjectLiveStatusMachineModuleLiveStatusTypeM
0:HasComponentObjectMaterialBuffers0:FolderTypeO
0:HasComponentObjectMaterialLoadingPoints0:FolderTypeO
0:HasComponentObjectMaterialLocations0:FolderTypeO
0:HasComponentObjectMaterialOutputPoints0:FolderTypeO
0:HasComponentObjectMaterialRejectionPoints0:FolderTypeO
0:HasComponentObjectPastSpecificationRecords0:FolderTypeO
0:HasComponentObjectProcessControlLoops0:FolderTypeO
0:HasComponentObjectProcessItems0:FolderTypeO
0:HasComponentObjectProductionMachineModuleProductionTypeO
0:HasPropertyVariableRemote0:Boolean0:PropertyTypeM, RO
0:HasComponentObjectSetupMachineModuleSetupTypeO
0:HasComponentObjectSpecificationMachineModuleSpecificationTypeO
Conformance Units
TMC Data Collection
TMC Core Production
TMC Process Variables Ingestion and Control
TMC Intralogistics at the machine
BrowseName Description
ConfigurationThe Configuration Object provides the descriptions (metadata) for settings, stop reasons and root causes of the machine module as well as affordances to make modifications.
ControlModulesThe ControlModules folder provides control modules belonging to the machine module (and not belonging to an equipment module).
DefectDetectionSensorsThe DefectDetectionSensors folder provides the sensor(s) and sensing systems fitted to the machine module that detect product defects.
EquipmentModulesThe EquipmentModules folder provides equipment modules of the machine module.
LiveStatusThe LIveStatus Object provides information about the real time status of the machine module and provides affordances to control the machine module remotely in real time.
MaterialBuffersThe MaterialBuffers folder provides material storage buffers of the machine module.
MaterialLoadingPointsThe MaterialLoadingPoints folder provides the loading points and the materials being loaded, as well as the brand integrity checks required.
MaterialLocationsThe MaterialLocations folder provides material locations used to deliver or retrieve materials to/from the machine.
MaterialOutputPointsThe MaterialOutputPoints folder provides the output(s) of the machine module.
MaterialRejectionPointsThe MaterialRejectionPoints folder provides rejection traps where material is discarded from the machine module.
PastSpecificationRecordsThe PastSpecificationRecords folder contains the information about the machine as was operating in a previous period of time.
ProcessControlLoopsThe ProcessControlLoops folder provides control loops of the machine module.
ProcessItemsThe ProcessItems folder provides analog sensor values.
ProductionThe Production Object provides information about the current production order and quantity produced as well as affordances to start/stop a production order and reset totals for the machine module.
Remote

When Remote is True, all methods exposed by the machine module and contained objects are executed and all variables marked as RW can be written to.

When Remote is False, the OEM may decide to not execute some qualified methods and/or not allow some qualified RW variables to be written to because of justified safety concerns. The justification shall be provided in the machine safety assessment provided to the customer. Lacking justification, the method shall be executable. For instance, informative methods such as (but not limited to) GetProductionOrder, GetDataSet, GetMaterialList, GetDataSetList, GetRootCauseGroupList, GetRootCauseList, GetStopReasonList, ValidateDataSet, ValidateMaterialList are executable regardless of the value of Remote.

The invoking of qualified methods and/or writing of qualified RW variables can be disallowed only for the MachineModuleLiveStatus which includes the methods SendCommand and SetControlMode.

When a method is not executed due to the Remote flag, the MethodExecutionFeedback shall report “The system is under local control. Please, switch to Remote to execute the method.” When a RW variable is not allowed to be written to, the StatusCode “Bad_NotWritable” is produced.

Remote is read-only because of safety concerns and because it is typically implemented as a physical rotary selector on the machine cabinet: it is the operator who will release the control to a remote system.

SetupThe SetUp Object contains the value of all the settings (including mechanical adjustments) required to run production as well as affordances to validate and load settings for the machine module.
SpecificationThe Specification Object contains the specification about the machine as currently operating including capabilities, internal buffers and loading points.

The components of the MachineModuleType have additional subcomponents which are defined in the following table.

Table 13 – MachineModuleType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
ControlModules0:HasComponent Object AnalogInputs 0:FolderTypeO
0:HasComponent Object <AnalogInput> AnalogInputTypeOP
ControlModules0:HasComponent Object DigitalInputs 0:FolderTypeO
0:HasComponent Object <DigitalInput> DigitalInputTypeOP
ControlModules0:HasComponent Object Motors 0:FolderTypeO
0:HasComponent Object <Motor> MotorTypeOP
ControlModules0:HasComponent Object Sensors 0:FolderTypeO
0:HasComponent Object <Sensor> SensorTypeOP
ControlModules0:HasComponent Object Valves 0:FolderTypeO
0:HasComponent Object <Valve> ValveTypeOP
DefectDetectionSensors0:HasComponent Object <DefectDetectionSensor> DefectDetectionSensorTypeOP
EquipmentModules0:HasComponent Object <EquipmentModule> EquipmentModuleTypeOP
MaterialBuffers0:HasComponent Object <MaterialStorageBuffer> MaterialStorageBufferTypeOP
MaterialLoadingPoints0:HasComponent Object <MaterialLoadingPoint> MaterialLoadingPointTypeOP
MaterialLocations0:HasComponent Object <MaterialLocation> MaterialLocationTypeOP
MaterialOutputPoints0:HasComponent Object<MaterialOutput> MaterialOutputPointTypeOP
MaterialRejectionPoints0:HasComponent Object <MaterialRejectionPoint> MaterialRejectionPointTypeOP
PastSpecificationRecords0:HasComponent Object <SpecificationRecord>MachineModuleHistoricalRecordTypeOP
ProcessControlLoops0:HasComponent Object <ProcessControlLoop> ProcessControlLoopTypeOP
ProcessItems0:HasComponent Object <ProcessItem> ProcessItemTypeOP
ProcessItems0:HasComponent Object <ProcessControlItem> ProcessControlItemTypeOP
ProcessItems0:HasComponent Object <ProcessControlItem> ProcessControlItemTypeOP

Instances of the MachineModuleType are components of the DeviceSet Object as defined by OPC10000-100, 5.9 DeviceSet.

For additional clarity, MachineModuleType instances shall be grouped under the DeviceSet object.

8.2 MachineModuleHistoricalRecordType ObjectType

8.2.1 Overview

The MachineModuleHistoricalRecordType ObjectType contains the specifications of the machine module that have been valid in the past. When the machine module manufacturer modifies the machine in a way that impact the OPC UA server specification, the machine module manufacturer will save an object of type MachineModuleHistoricalType to the folder PastSpecificationRecords which is a component of the relevant MachineModule

The MachineModuleHistoricalRecordType is formally defined in the following table.

Table 14 – MachineModuleHistoricalRecordType Definition
Attribute Value
BrowseNameMachineModuleHistoricalRecordType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectMachineModuleSpecificationMachineModuleSpecificationTypeM
0:HasPropertyVariableValidUntil0:UtcTime0:PropertyTypeM, RO
Conformance Units
TMC Asset Management
BrowseName Description
MachineModuleSpecificationThe MachineModuleSpecification Object contains a specification that was valid in the past.
ValidUntilThe ValidUntil Propertyontains the date and time the MachineModuleSpecification was last valid. The Property ValidUntil shall be set by the OEM when changes that impact the machine module specification are made.

8.3 MachineModuleConfigurationType ObjectType

8.3.1 Overview

The MachineModuleConfigurationType provides descriptions for settings, stop reasons and root causes as well as affordances to make modifications.

The MachineModuleConfigurationType is formally defined in the following table.

Table 15 – MachineModuleConfigurationType Definition
Attribute Value
BrowseNameMachineModuleConfigurationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableDataSetListDataSetDefinitionType0:PropertyTypeO, RO
0:HasComponentMethodGetDataSetListSee below.O
0:HasComponentMethodGetRootCauseGroupListSee below.M
0:HasComponentMethodGetRootCauseListSee below.M
0:HasComponentMethodGetStopReasonListSee below.M
0:HasPropertyVariableLastChangeDate0:UtcTime0:PropertyTypeM, RO
0:HasPropertyVariableLongestMicroStopDuration0:Double0:PropertyTypeM, RW
0:HasPropertyVariableRootCauseGroupListRootCauseGroupType[]0:PropertyTypeM, RW
0:HasPropertyVariableRootCauseListRootCauseMessageType[]0:PropertyTypeM, RW
0:HasPropertyVariableRootCauseListInputIsMandatory0:Boolean0:PropertyTypeM, RW
0:HasComponentMethodSetDataSetListMESIDSee below.M
0:HasComponentMethodSetRootCauseListsSee below.M
0:HasPropertyVariableStopReasonListMessageType[]0:PropertyTypeM, RO
0:GeneratesEventObjectTypeRootCauseGroupListChangeLogType
0:GeneratesEventObjectTypeRootCauseListChangeLogType
0:GeneratesEventObjectTypeStopReasonListChangeLogType
Conformance Units
TMC Data Collection
TMC Single PO Production
TMC Multi PO Production
BrowseName Description
DataSetListThe Property DataSetList of type DataSetDefinition contains the descriptors for all the parameters used to set up the machine.
LastChangeDate

The Property LastChangeDate is the date and time of the last change applied to the machine

module configuration and the effective date of the modification.

LongestMicroStopDurationThe Property LongestMicroStopDuration is the maximum duration of a micro-stop in seconds, longer stops are not micro-stops. Operators are not required to enter a root cause for micro-stops.
RootCauseGroupList

The Property RootCauseGroupList is the list of groups that root causes can be grouped in.

They are defined by the end user. Same as the RootCauseList property. The RootCauseGroupList is user defined.

RootCauseListThe Property RootCauseList is the complete list of the root causes that the end user has defined to classify and organize the downtime due to the machine module stops. The RootCauseList is user defined.
RootCauseGroupListIsMandatoryThe Property RootCauseListInputIsMandatory is true when the operator is mandatorily required to select the root cause that best describes the current stop situation. For micro- stops such requirement does not apply.
StopReasonListThe Property StopReasonList is a list containing the descriptors for all the possible machine module messages, including alarms and warnings. Messages include their localization. The list is defined, created and maintained by the OEM.

8.3.2 GetDataSetList Method

The GetDatasetList Method returns the list of descriptions for parameters of the dataset filtered by the dependency and subset created by the user.

The GetDatasetList Method is typically used for clients to visualize the parameters’ descriptions and related metadata.

The signature of this Method is specified below. Table 16 specifies the Arguments representation.

Signature

	GetDataSetList (
	  [in]  ParameterDependencyEnumeration			Dependency,
	  [in]  0:Boolean								UserSubset,
	  [in]  0:Boolean       						CompleteSet,
	  [out] DataSetDefinitionType						DataSetList,
	  [out] MethodExecutionFeedbackType				ExecutionFeedback
			);
Table 16 – GetDataSetList Method Arguments
Argument Description
DependencyDependency specifies how to select (filter) a subset of the dataset based on dependency.
UserSubsetUserSubset specifies how to select (filter) a subset of the dataset based on the user-defined UserSubset.
CompleteSetIf CompleteSet is True, then the method returns the complete dataset without considering the input parameters Dependency and UserSubset.
DataSetListThe list of parameters filtered as per the input arguments Dependency and UserSubset.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.3.3 GetRootCauseGroupList Method

The GetRootCauseGroupList Method returns the complete list of root cause groups as persisted by the server.

The signature of this Method is specified below. Table 17 specifies the Arguments representation.

Signature

	GetRootCauseGroupList(
	  [out] RootCauseGroupType[]			RootCauseGroupList,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 17 – GetRootCauseGroupList Method Arguments
Argument Description
RootCauseGroupListThe complete list of root cause groups.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.3.4 GetRootCauseList Method

The GetRootCauseList Method returns the complete list of root causes as persisted by the server.

The signature of this Method is specified below. Table 18 specifies the Arguments representation.

Signature

	GetRootCauseList(
	  [out] RootCauseMessageType[]			RootCauseList,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 18 – GetRootCauseList Method Arguments
Argument Description
RootCauseListThe complete list of root cause messages.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.3.5 GetStopReasonList Method

The GetStopReasonList Method returns the complete list of stop reasons as persisted by the server.

The signature of this Method is specified below. Table 19 specifies the Arguments representation.

Signature

	GetStopReasonList(
	  [out] MessageType[]					StopReasonList,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 19 – GetStopReasonList Method Arguments
Argument Description
StopReasonListThe complete list of stop reason messages.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.3.6 SetDataSetListMESID Method

The SetDataSetListMESID Method sets the MES_ID of one or more items of the array Definitions contained in the DataSetList.

For clarity, the DataSetList is a Variable of type DataSetDefinitionType which contains Definitions, an array of structures of type DataDefinitionType. In turn DataDefinitionType is a subtype of DataDescriptionType, meaning it inherits MES_ID. The latter is set by SetDataSetListMESID.

Each item of Definitions is identified by its ID.

The signature of this Method is specified below. Table 20 specifies the Arguments representation.

Signature

	SetDataSetListMESID (
	  [in]  0:String[]						IDs,
	  [in]  0:String[]						MESIDs,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 20 – SetDataSetListMESID Method Arguments
Argument Description
IDsThe IDs of the elements of the Definitions array whose MES_ID shall be changed if the method executes successfully.
MESIDsThe values of the MES_IDs to be set.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.3.7 SetRootCauseLists Method

The SetRootCauseLists Method sets both the RootCauseList and RootCauseGroupList according to the input arguments. The RootCauseList and RootCauseGroupList properties are set together to ensure consistency of root causes with the relevant groups.

The signature of this Method is specified below. Table 21 specifies the Arguments representation.

Signature

	SetRootCauseLists (
	  [in]  RootCauseMessageType[]			RootCauseList,
	  [in]  RootCauseGroupType[]			RootCauseGroupList,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 21 – SetRootCauseLists Method Arguments
Argument Description
RootCauseListThe list of root causes to be transferred to and used by the server.
RootCauseGroupListThe list of root cause groups to be transferred to and used by the server.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.4 MachineModuleLiveStatusType ObjectType

8.4.1 Overview

The MachineModuleLiveStatusType ObjectType contains information about the real time status of the machine module and provides affordances to control the machine module remotely in real time.

The MachineModuleLiveStatusType is formally defined in the following table.

Table 22 – MachineModuleLiveStatusType Definition
Attribute Value
BrowseNameMachineModuleLiveStatusType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethodAcknowledgeAlarmsSee below.M
0:HasComponentObjectAlarms0:FolderTypeM
0:HasPropertyVariableControlModeControlModeEnumeration0:PropertyTypeM, RW
0:HasComponentObjectData0:FolderTypeO
0:HasPropertyVariableIdleEnergySavingMode0:Boolean0:PropertyTypeM, RW
0:HasComponentMethodResetAggregatesSee below.M
0:HasComponentMethodSendCommandSee below.M
0:HasComponentMethodSetControlModeSee below.M
0:HasComponentMethodSetIdleEnergySavingModeSee below.M
0:HasPropertyVariableStateStateEnumeration0:PropertyTypeM, RO
0:HasComponentObjectStateMachineTMCStateMachineTypeO
0:GeneratesEventObjectTypeControlModeChangeLogType
0:GeneratesEventObjectType0:DiscreteAlarmType
0:GeneratesEventObjectTypeDowntimeLogType
0:GeneratesEventObjectTypeExternalAlarmType
0:GeneratesEventObjectTypeStateChangeLogType
Conformance Units
TMC Basic Machine Status
TMC Advanced Machine Status
BrowseName Description
ControlModeThe ControlMode property describes the current control mode of the machine.
IdleEnergySavingModeThe IdleEnergySavingMode Property is set to True when the energy saving mode during the idle phase is set.
StateThe Property State describes the status of the state machine controlling the machine module. State provides a subset of the information of the state machine, when the latter is implemented.
StateMachineThe state machine describes the current state of the machine, the possible transitions and their conditions.
AlarmsThe Alarms folder contains alarms of the machine module.
DataThe Data Folder contains additional data that is not identified elsewhere in this specification.

The components of the MachineModuleLiveStatusType have additional subcomponents which are defined in the following table.

Table 23 – MachineModuleLiveStatusType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Alarms0:HasComponentObject<Alarm> 0:DiscreteAlarmTypeOP
Alarms0:HasComponentObject<ExternalAlarm> ExternalAlarmTypeOP
Data0:HasComponentVariable<DataItem>0:BaseDataType 0:BaseDataVariableTypeOP, RO

8.4.2 AcknowledgeAlarms Method

The AcknowledgeAlarms Method acknowledges all alarms of the machine module. The acknowledgement is cascades to other objects belonging to the machine module e.g., equipment modules and control modules.

The signature of this Method is specified below. Table 24 specifies the Arguments representation.

Signature

	AcknowledgeAlarms (
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 24 – AcknowledgeAlarms Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.4.3 ResetAggregates Method

The ResetAggregates resets all the aggregates for the objects contained in the ProcessItems and ProcessControlLoops of the machine module.

The signature of this Method is specified below. Table 25 specifies the Arguments representation.

Signature

	ResetAggregates (
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 25 – ResetAggregates Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.4.4 SendCommand Method

The Method SendCommand sends a command to change the state of the machine module state machine remotely.

The signature of this Method is specified below. Table 26 specifies the Arguments representation.

Signature

	SendCommand (
	  [in]  CommandEnumeration				Command,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 26 – SendCommand Method Arguments
Argument Description
CommandThe command to be sent to the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.4.5 SetControlMode Method

The SetControlMode Method sets the control mode of the machine module.

The signature of this Method is specified below. Table 27 specifies the Arguments representation.

Signature

	SetControlMode (
	  [in]  ControlModeEnumeration			ControlMode,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 27 – SetControlMode Method Arguments
Argument Description
ControlModeThe control mode to be set to the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.4.6 SetIdleEnergySavingMode Method

The Method SetIdleEnergySavingMode activates the energy saving mode when the machine module is idle.

The signature of this Method is specified below. Table 28 specifies the Arguments representation.

Signature

	SetIdleEnergySavingMode (
	  [in]  0:Boolean						IdleEnergySavingMode,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 28 – SetIdleEnergySavingMode Method Arguments
Argument Description
IdleEnergySavingModeThe energy saving mode to set.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5 MachineModuleProductionType ObjectType

8.5.1 Overview

The MachineModuleProductionType Object provides information about the current production order and quantity produced as well as affordances to start/stop a production order and reset totals for the machine module.

The MachineModuleProductionType is formally defined in the table below.

Table 29 – MachineModuleProductionType Definition
Attribute Value
BrowseNameMachineModuleProductionType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethodAbortProductionOrderSee below.O
0:HasPropertyVariableAssignedProductionOrdersProductionOrderType[]0:PropertyTypeO, RO
0:HasComponentMethodAssignProductionOrderSee below.O
0:HasPropertyVariableAutoComplete0:Boolean0:PropertyTypeO, RW
0:HasPropertyVariableAutoStart0:Boolean0:PropertyTypeO, RW
0:HasComponentMethodClearProductionOrderSee below.O
0:HasComponentMethodCompleteProductionOrderSee below.M
0:HasComponentObjectData0:FolderTypeO
0:HasPropertyVariableProductionOrderProductionOrderHeaderType0:PropertyTypeM, RO
0:HasPropertyVariableProductionStatusProductionStatusEnumeration0:PropertyTypeM, RO
0:HasComponentMethodResetProductionTotalsSee below.M
0:HasComponentMethodStartAssignedProductionOrderSee below.O
0:HasComponentMethodStartProductionOrderSee below.M
0:HasComponentObjectStateMachineMachineModuleProductionStateMachineTypeO
0:HasComponentMethodUnassignProductionOrderSee below.O
0:GeneratesEventObjectTypePOStartedLogType
0:GeneratesEventObjectTypePOStoppedLogType
Conformance Units
TMC Core Production
TMC Single PO Production
TMC Multi PO Production
BrowseName Description
AssignedProductionOrdersThe AssignedProductionOrders array contains the production orders that have been assigned to the machine module and have not yet been started or unassigned.
AutoCompleteThe AutoComplete Boolean defines how to trigger the machine module to complete the execution of a production order. When AutoComplete is False, the completion of a production order at the machine module is triggered with the method CompleteProductionOrder. When AutoComplete is True, the machine module initiates the completion of the production order when all the active upstream machine modules running the production order are in state complete.
AutoStart

The Autostart Boolean defines how to trigger the machine module to start a production order.

When AutoStart is True and AssignedProductionOrders[] contains one PO, the assigned machine module initiates the starting sequence automatically for the assigned production order.

When AutoStart is False, the start of a production order at the machine module is triggered with the method StartProductionOrder. StartProductionOrder is also invoked when AutoStart is True and AssignedProductionOrders[] contains more than one production order.

DataThe Data folder provides additional production data that is not identified elsewhere in this specification. e.g. a shift report.
ProductionOrderThe production order header in execution at the machine module.
ProductionStatusThe execution status of the production order.
StateMachineThe StateMachine extends ProductionStatus and provides detailed production execution status as well as methods to trigger the transitions and events when the transitions occur.

8.5.2 AbortProductionOrder Method

The AbortProductionOrder method is used to abnormally terminate, or abort, a production order that is in execution or starting or completing. Aborting cannot be reversed or undone.

The signature of this Method is specified below. Table 30 specifies the Arguments representation.

Signature

	AbortProductionOrder (
	  [in]  ProductionOrderHeaderType		POToAbort,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 30 – AbortProductionOrder Method Arguments
Argument Description
POToAbortThe production order to be aborted. The argument is unnecessary for execution (since at most one production order can be executed at any time in the machine module) but provided as a safety net since aborting cannot be reversed.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5.3 AssignProductionOrder Method

The AssignProductionOrder Method is used to transfer the information of an upcoming production order to the machine module.

The signature of this Method is specified below. Table 31 specifies the Arguments representation.

Signature

	AssignProductionOrder (
	  [in]  ProductionOrderType			POToAssign,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
	
Table 31 – AssignProductionOrder Method Arguments
Argument Description
POToAssignThe production order to assign to the machine module for later execution.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5.4 ClearProductionOrder Method

The ClearProductionOrder method is used to positively confirm that the machine module where a production order is aborted has been cleared of the product or parts left by the aborted production order.

The signature of this Method is specified below. Table 32 specifies the Arguments representation.

Signature

	ClearProductionOrder (
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 32 – ClearProductionOrder Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5.5 CompleteProductionOrder Method

The CompleteProductionOrder method is used to complete a production order in execution.

The signature of this Method is specified below. Table 33 specifies the Arguments representation.

Signature

	CompleteProductionOrder (
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 33 – CompleteProductionOrder Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

When the StateMachine is in state Execute, the successful execution of the method causes the transition to state Completing.

When the method is invoked in any other state, the method property Executable is False and when the method is invoked, the status code Bad_NotSupported is returned.

8.5.6 StartAssignedProductionOrder Method

The StartAssignedProductionOrder Method starts a production order whose state is Assigned at the machine module.

The signature of this Method is specified below. Table 34 specifies the Arguments representation.

Signature

	StartAssignedProductionOrder (
	  [in]  ProductionOrderHeaderType	POHeaderToStart,
	  [in]  0:String[]					SourceMaterialLoadingPointIDs,
	  [in]  0:String[]				 DestinationMaterialOutputPointIDs,
	  [out] MethodExecutionFeedbackType	ExecutionFeedback);
Table 34 – StartAssignedProductionOrder Method Arguments
Argument Description
POHeaderToStartThe header of the production order to be started.
SourceMaterialLoadingPointIDsThe list of material loading points that are going to be used by the production order to be started.
DestinationMaterialOutputPointIDsThe list of material output points that are going to be used by the production order to be started.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5.7 StartProductionOrder Method

The StartProductionOrder Method starts a production order at the machine module.

The signature of this Method is specified below. Table 35 specifies the Arguments representation.

Signature

	StartProductionOrder (
	  [in]  ProductionOrderType			POToStart,
	  [in]  0:String[]					SourceMaterialLoadingPointIDs,
	  [in]  0:String[]				 DestinationMaterialOutputPointIDs,
	  [out] MethodExecutionFeedbackType	ExecutionFeedback);
Table 35 – StartProductionOrder Method Arguments
Argument Description
POToStartThe production order to be started.
SourceMaterialLoadingPointIDsThe list of material loading points that are going to be used by the production order to be started.
DestinationMaterialOutputPointIDsThe list of material output points that are going to be used by the production order to be started.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5.8 UnassignProductionOrder Method

The UnassignProductionOrder method is used to remove the specified production order from AssignedProductionOrders[] of an infeed machine module.

The signature of this Method is specified below. Table 36 specifies the Arguments representation.

Signature

	UnassignProductionOrder (
	  [in]  ProductionOrderHeaderType		POToUnassign,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 36 – UnassignProductionOrder Method Arguments
Argument Description
POToUnassignThe production order to be unassigned at the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.5.9 ResetProductionTotals

The Method ResetProductionTotals simultaneously resets the totals of the machine components belonging to the following machine folders: DefectDetectionSensors, MaterialLoadingPoints, MaterialOutputPoints, MaterialRejectionPoints.

The master totals belonging to the same objects are not reset.

The signature of this Method is specified below. Table 37 specifies the Arguments representation.

Signature

	ResetProductionTotals (
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 37 – ResetProductionTotals Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.6 MachineModuleSpecificationType ObjectType

8.6.1 Overview

The MachineModuleSpecificationType provides the specification of the machine module as currently operating including capabilities, internal buffers and loading points.

This MachineModuleSpecificationType is formally defined in the table below.

Table 38 – MachineModuleSpecificationType Definition
Attribute Value
BrowseNameMachineModuleSpecificationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethodDeleteSpecificationRecordSee below.M
0:HasComponentObjectDocumentation0:FolderTypeM
0:HasComponentMethodLoadMachineModuleDocumentationSee below.M
0:HasPropertyVariableLocationName0:String0:PropertyTypeM, RW
0:HasPropertyVariableMaterialLoadingPointsMaterialPointType[]0:PropertyTypeM, RO
0:HasPropertyVariableMaterialOutputPointsMaterialPointType[]0:PropertyTypeM, RO
0:HasPropertyVariableMaterialRejectionPointsMaterialPointType[]0:PropertyTypeM, RO
0:HasPropertyVariableMaterialStorageBuffersMaterialStorageBufferDataType[]0:PropertyTypeM, RO
0:HasComponentMethodRemoveMachineModuleDocumentationSee below.M
0:HasComponentMethodSetNewSpecificationSee below.M
0:HasPropertyVariableTimeZone0:TimeZoneDataType0:PropertyTypeM, RW
0:HasPropertyVariableTotalRunningHours0:UInt640: PropertyTypeM, RO
0:HasPropertyVariableUserMachineName0:String0:PropertyTypeM, RW
0:HasPropertyVariableValidSince0:UtcTime0:PropertyTypeM, RO
0:GeneratesEventObjectTypeMachineModuleSpecificationChangeLogType
Conformance Units
TMC Single PO Production
TMC Asset Management
BrowseName Description
DocumentationThe Object Documentation is the sole repository for the machine module documentation resources. The Documentation is accessed, for example, by clients and HMIs.
LocationNameThe Property LocationName of type String contains the location of the machine module within the user production site. The Property LocationName will contain the following: Country/City/Department/Floor/Bay/Position. LocationName and UserMachineName uniquely identify the machine module in the user organization.
MaterialLoadingPointsThe Property MaterialLoadingPoints identifies the loading points of the machine module and their capability in terms of what materials can be loaded at a loading point. The Property MaterialLoadingPoints is defined as a list of objects of type MaterialPointType.
MaterialOutputPointsThe Property MaterialOutputPoints identifies the output points of the machine module and their capability in terms of what materials can be output The Property MaterialOutputPoints is defined as a list of objects of type MaterialPointType.
MaterialRejectionPointsThe Property MaterialRejectionPoints identifies the rejection points of the machine module and their capability in terms of what materials are rejected The Property MaterialRejectionPoints is defined as a list of objects of type MaterialPointType.
MaterialStorageBuffersThe Property MaterialStorageBuffers describes the buffers inside the machine module and their current status. The Property MaterialStorageBuffers is a list of objects of type MaterialStorageBufferDataType.
TimeZoneThe local time zone where the machine operates. It is required to convert UTC times into local time.
TotalRunningHoursThe Property TotalRunningHours counts the number of hours the machine module has been in operation since the last time its configuration was changed. More specifically, time is counted when the machine module state is different from: Stopping, Stopped, Aborting, Aborted, Clearing.
UserMachineNameThe Property UserMachineName of type String contains the name used by the user to identify the machine module. LocationName and UserMachineName uniquely identify the machine module in the user organization.
ValidSinceThe Property ValidSince is the date since the configuration was last modified.

The components of the MachineModuleSpecificationType have additional subcomponents which are defined in the table below.

Table 39 – MachineModuleSpecificationType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Documentation0:HasPropertyVariable <DocumentName>0:ByteString 0:PropertyTypeOP, RO

8.6.2 DeleteSpecificationRecord Method

The DeleteSpecificationRecord Method deletes a specification record.

The signature of this Method is specified below. Table 40 specifies the Arguments representation.

Signature

	DeleteSpecificationRecord (
	[in]		0:NodeId							SpecificationRecord,
	[out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 40 – DeleteSpecificationRecord Method Arguments
Argument Description
SpecificationRecordThe OPC UA unique node identifier for the specification to be deleted from the underlying system repository.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.6.3 LoadMachineModuleDocumentation Method

The LoadMachineModuleDocumentation Method allows to securely load any machine module documentation to the documentation repository Documentation folder where it can be reached by applications.

The signature of this Method is specified below. Table 41 specifies the Arguments representation.

Signature

	LoadMachineModuleDocumentation (
	[in]		0:ByteString						DocumentToBeLoaded,
	[in]		0:String							DocumentName,
	[out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 41 – LoadMachineModuleDocumentation Method Arguments
Argument Description
DocumentToBeLoadedThe document, as a byte string, to be transferred to the Documentation folder.
DocumentNameThe document name to be associated to the document in the underlying system.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.6.4 RemoveMachineModuleDocumentation Method

The RemoveMachineModuleDocumentation Method allows to securely remove, i.e. permanently delete, any machine module documentation from the documentation repository Documentation.

The signature of this Method is specified below. Table 42 specifies the Arguments representation.

Signature

	RemoveMachineModuleDocumentation (
	[in]		0:String							DocumentName,
	[out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 42 – RemoveMachineModuleDocumentation Method Arguments
Argument Description
DocumentNameThe document name to be associated to the document in the underlying system.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.6.5 SetNewSpecification Method

The Method SetNewSpecification saves its arguments as the new specification for the machine module. Prior to that it saves the previous specification into the PastSpecification Records Object of the same machine module.

The signature of this Method is specified below. Table 43 specifies the Arguments representation.

Signature

	SetNewSpecification (
	[in]	MaterialPointType[]     			NewMaterialLoadingPoints,
	[in]	MaterialStorageBufferDataType[]	NewMaterialStorageBuffers,
	[in]	MaterialPointType[]     			NewMaterialOutputPoints,
	[in]	MaterialPointType[]     		   NewMaterialRejectionPoints,
	[out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 43 – SetNewSpecification Method Arguments
Argument Description
NewMaterialLoadingPointsThe information about the material loading points that will be valid after the machine specification is changed.
NewMaterialStorageBuffersThe information about the storage buffers that will be valid after the machine specification is changed.
NewMaterialOutputPointsThe information about the material output points that will be valid after the machine specification is changed.
NewMaterialRejectionPointsThe information about the material rejection points that will be valid after the machine specification is changed.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.7 MachineModuleSetupType ObjectType

8.7.1 Overview

The MachineModuleSetupType ObjectType contains the value of all the settings (including mechanical adjustments) required to run production as well as affordances to validate and load settings for the machine module.

This MachineModuleSetupType is formally defined in the table below.

Table 44 – MachineModuleSetupType Definition
Attribute Value
BrowseNameMachineModuleSetupType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableDataSetDataSetType0:PropertyTypeM, RW
0:HasComponentMethodLoadDataSetSee below.O
0:HasComponentMethodLoadMaterialListSee below.O
0:HasPropertyVariableMaterialListMaterialListType0:PropertyTypeM, RO
0:HasComponentObjectMechanicalAdjustments0:FolderTypeM
0:HasComponentObjectDataSetFolder0:FolderTypeM
0:HasComponentMethodValidateDataSetSee below.O
0:HasComponentMethodValidateMaterialListSee below.O
0:GeneratesEventObjectTypeDataSetChangeLogTypeM
Conformance Units
TMC Single PO Production
TMC Advanced Setup
BrowseName Description
DataSet DataSet contains all the digital settings (other than the mechanical settings stored in the folder MechanicalAdjustments) required by the machine module.
MaterialList MaterialList contains the list of materials that are going to be used for the production of the current production order.
MechanicalAdjustmentsThe MechanicalAdjustments folder contains the non-digital settings required to setup the machine e.g. mechanical adjustments.
DataSetFolderThe DataSetFolder contains the DataSet including values and descriptions. It contains the same information as DataSet but in a way that is friendlier to simple clients.

The components of the MachineModuleSetupType have additional subcomponents which are defined in the table below.

Table 45 – MachineModuleSetupType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
MechanicalAdjustments0:HasPropertyVariable <DocumentName>0:ByteString 0:PropertyTypeOP, RO
DataSetFolder0:HasComponentVariable DataSetID0:String 0:DataItemTypeM, RW
DataSetFolder0:HasComponentVariable DataSetDescription0:LocalizedText 0:DataItemTypeM, RW
DataSetFolder0:HasComponentVariable <DataSetValue>0:BaseDataType 0:DataItemTypeOP, RW

8.7.2 LoadDataSet Method

The LoadDataSet Method loads the dataset to the underlying system after having validated that (a) the dataset is complete when IsCompleteDataset is True and (b) the dataset is valid.

When the validation is not passed, then the data set is not loaded to the underlying system rolling back any data change and a specific message shall be returned via ExecutionFeedback.

For detailed validation diagnostics, the Method ValidateDataSet shall be invoked.

The signature of this Method is specified below. Table 46 specifies the Arguments representation.

Signature

	LoadDataSet (
	[in]		DataSetType						DataSet,
	[in]		Boolean							IsCompleteDataSet,
	[out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 46 – LoadDataSet Method Arguments
Argument Description
DataSetThe dataset to be transferred to the underlying system.
IsCompleteDataSetWhen true, the DataSet argument is a complete dataset, meaning all DataSet entries are included.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.7.3 LoadMaterialList Method

The LoadMaterialList Method loads the material list to the underlying system after having validated that (a) the material list is complete and (b) the material list is valid.

When the validation is not passed, then the material list is not loaded to the underlying system rolling back any data change and a specific message shall be returned via ExecutionFeedback.

For detailed validation diagnostics, the Method ValidateMaterialList shall be invoked.

The signature of this Method is specified below. Table 47 specifies the Arguments representation.

Signature

	LoadDataSet (
	[in]		MaterialListType				MaterialList,
	[out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 47 – LoadMaterialList Method Arguments
Argument Description
MaterialListThe material list to be transferred to the underlying system.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.7.4 ValidateDataSet Method

The ValidateDataSet Method transfers a dataset, complete when IsCompleteDataSet is True, to the underlying system and returns the result of the validation, i.e. verifying that the dataset is complete and can run in production.

When the ValidateDataSet Method is executed, the DataSet variable is not affected. If the validation is not passed, the identifiers of the datapoints that did not pass are provided with the ExecutionFeedback.

The validation of the DataSet normally occurs before the DataSet is required, i.e. while production is running and using a different dataset. As a matter of fact, the ValidateDataSet Method is used to validate a DataSet beforehand giving time to the higher-level systems in charge to correct mistakes. Thus the underlying system is required to provide all affordances to perform the validation without disrupting running production orders.

The signature of this Method is specified below. Table 48 specifies the Arguments representation.

Signature

	ValidateDataSet (
	[in]		DataSetType					DataSet,
	[in] 	Boolean						IsCompleteDataSet,
	[out] 	DataSetEntryType[]	 		FailedValidationEntries,
	[out] 	MessageType[]					FailedValidationMessages,
	[out] 	MethodExecutionFeedbackType	ExecutionFeedback);
Table 48 – ValidateDataSet Method Arguments
Argument Description
DataSetThe dataset to be validated by the underlying system.
IsCompleteDataSetWhen true, the DataSet argument is a complete dataset, meaning all DataSet entries are included.
FailedValidationEntriesThe dataset items that failed the validation.
FailedValidationMessagesThe detailed reasons the validation failed.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.7.5 ValidateMaterialList Method

The ValidateMaterialList Method transfers a material list to the underlying system and returns the result of the validation, i.e. verifying that the material list is complete and can run in production.

When the ValidateMaterialList is executed, the MaterialList variable is not affected. If the validation is not passed, the identifiers of the materials that did not pass are provided with the ExecutionFeedback.

The validation of the MaterialList normally occurs before the MaterialList is required, i.e. while production is running and using a different material list. As a matter of fact, the ValidateMaterialList Method is used to validate a MaterialList beforehand giving time to the higher-level systems in charge to correct mistakes. Thus the underlying system is required to provide all affordances to perform the validation without disrupting running production orders.

The signature of this Method is specified below. Table 49 specifies the Arguments representation.

Signature

	ValidateMaterialList (
	[in]		MaterialListType			MaterialList,
	[out] 	MaterialListItemType[] 		FailedValidationEntries,
	[out] 	MessageType[]				FailedValidationMessages,
	[out] 	MethodExecutionFeedbackType	ExecutionFeedback);
Table 49 – ValidateMaterialList Method Arguments
Argument Description
MaterialListThe material list to be validated by the underlying system.
FailedValidationEntriesThe material list items that failed the validation.
FailedValidationMessagesThe detailed reasons the validation failed.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.8 MaterialLoadingPointType ObjectType

8.8.1 Overview

The MaterialLoadingPointType ObjectType describes the machine module part where materials are loaded (either manually or by means of an automated system or both) and the materials being loaded, as well as the brand integrity checks required.

The MaterialLoadingPointType is formally defined in the following table.

Table 50 – MaterialLoadingPointType Definition
Attribute Value
BrowseNameMaterialLoadingPointType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableActualDispensingRate0:DoubleMaterialRateTypeM, RO, HR
0:HasComponentVariableConsumedMaterialMasterTotal0:DoubleMaterialQuantityVariableTypeM, RO
0:HasComponentVariableConsumedMaterialTotal0:DoubleMaterialQuantityVariableTypeM, RO, HR
0:HasComponentVariableDispensedMaterialMasterTotal0:DoubleMaterialQuantityVariableTypeM, RO
0:HasComponentVariableDispensedMaterialTotal0:DoubleMaterialQuantityVariableTypeM, RO, HR
0:HasComponentVariableDispensingRateState0:LocalizedText0:StateVariableTypeM, RO, HR
0:HasPropertyVariableExpectedMaterialsMaterialSublotType[]0:PropertyTypeM, RO
0:HasComponentVariableLoadedMaterialMaterialSublotType[]0:BaseDataVariableTypeM, RO
0:HasPropertyVariableMaterialPointDefinitionMaterialPointType0:PropertyTypeM, RO
0:HasPropertyVariableMaterialIntegrityAgentMaterialIntegrityAgentEnumeration0:PropertyTypeM, RW
0:HasPropertyVariableMES_ID0:String0:PropertyTypeM, RW
0:HasComponentVariableNominalDispensingRate0:DoubleMaterialRateTypeM, RO
0:HasComponentVariablePresentedMaterialMaterialSublotType0:BaseDataVariableTypeM, RW
0:HasComponentVariablePresentedMaterialValidationStatusMaterialValidationStatusEnumeration0:BaseDataVariableTypeM, RO
0:HasComponentMethodSetPresentedMaterialValidationStatusSee below.M
0:HasPropertyVariableAllowMixedLots0:Boolean0:PropertyTypeM, RW
0:HasPropertyVariableUpstreamHold0:Boolean0:PropertyTypeM, RO
0:GeneratesEventObjectTypeIntegrityRejectedMaterialLogType
0:GeneratesEventObjectTypeLoadingPointUnloadedLogType
0:GeneratesEventObjectTypeMaterialConsumedLogType
0:GeneratesEventObjectTypeMaterialDispensedLogType
0:GeneratesEventObjectTypeMaterialUnloadingRequiredLogType
0:GeneratesEventObjectTypeNewPresentedMaterialLogType
Conformance Units
TMC Core Production
BrowseName Description
ActualDispensingRateThe actual rate at which the input material is being dispensed.
ConsumedMaterialMasterTotalThe total quantity of material that entered the machine loading point. This total is never reset.
ConsumedMaterialTotal

The total quantity of material that entered the machine loading point. When the material is loaded, it may be immediately dispensed or may be stored and dispensed when required according to the machine logic. When the material is immediately dispensed, the consumed material quantity equals the dispensed material quantity (DispensedMaterialTotal).

The quantity is reset by the successful execution of the ResetMachineTotals method, only.

DispensedMaterialMasterTotalThe total quantity of material dispensed at the machine after loading at the loading point. This total is never reset.
DispensedMaterialTotalThe total quantity of material dispensed at the machine after loading at the loading point. The quantity is reset by the successful execution of the ResetMachineTotals method, only.
DispensingRateState

The DispensingRateState provides information about the state of the dispensing rate justifying why the ActualDispensingRate is different from the NominalDispensingRate. At a minimum the list of states below shall be provided:

Id=0, Speed is at Nominal value

Id=1, Speed Changed by Operator

Id=2, Speed Followed from Downstream Internal

Id=3, Speed Reduced due to low input material

Id=4, Speed Reduced due to internal high input material level

Id=5, Speed Reduced due to Filling Mode

Id=6, Speed Reduced due to internal procedure (e.g. calibration)

Id=7, Speed Reduced due to input material change (e.g. foil splicing, inner frame bobbin change, etc.)

Id=8, Speed Changed by Remote Host

When the actual rate is not measured, Id=0 Speed is at Nominal value will be returned. The speed set by an external host, if any, is used as the NominalDispensingRate.

Null speed is a speed reduction. The list may be extended for specific states not already covered in the list above.

ExpectedMaterialsThe array of sublots of the material that are expected at the machine loading point for the current production. ExpectedMaterials is a set of MaterialListItems such that the UserMachineName in LoadingPoint matches the LoadingPointID of the MaterialListItem.
LoadedMaterial

An array of the sublots that entered the machine loading point. When a sublot is unloaded, it is also removed from the array.

The sublot in the first position is the sublot from which the machine module is currently dispensing the material. The quantity of the sublot in the first position is decreased by an amount equal to the dispensing.

MaterialPointDefinitionThe Property MaterialPointDefinition contains the identification of the material point and the material that is processed.
MaterialIntegrityAgent

MaterialIntegrityAgent defines how material validation is performed. The scenarios taken into consideration are defined by the MaterialIntegrityEnumeration:

None: the material validation is not requested. In this case the underlying system sets MaterialValidationResult to None.

External: an external system performs the material validation. The external system validates the PresentedMaterial and invokes the SetValidationResult method to transfer the validation results to the machine.

Local: the underlying system performs the material validation on the PresentedMaterial and sets the result in MaterialValidationResult.

When an unsupported value is written to the variable, the underlying system will overwrite it with a supported one.

MES_IDUnique identifier for the material point in an external system, e.g. MES.
NominalDispensingRateThe nominal rate at which the input material is dispensed when the machine runs at design speed.
PresentedMaterial

The material presented to the material loading point, but not yet loaded.

When the material is loaded, the underlying system resets the PresentedMaterial and the MaterialValidationStatus to Failed.

When an upstream machine is connected, the material output from the upstream machine is the presented material.

Read/Write to allow for external systems to request the validation of a material. When the PresentedMaterial changes, the validation system performs validation.

PresentedMaterialValidationStatusThe status of the validation of the presented material. When Passed, the presented material is loaded by the machine module; when Failed, the presented material will be removed from the loading point, either automatically or manually. When InProgress, the validation is in progress. When MaterialIntegrityAgent is None and MaterialPresented is empty, then the value is None.
AllowMixedLotsWhen AllowMixedLots is False and BatchManaged in the material definition of the ExpectedMaterials is True, then one material lot will be processed i.e. the first material lot received.
UpstreamHold UpstreamHold is true when the loading point cannot receive more product and the upstream machine is required to stop loading, False when the loading point can receive product.

8.8.2 SetPresentedMaterialValidationStatus Method

The SetPresentedMaterialValidationStatus Method provides a client with an affordance to perform the validation of the PresentedMaterial against the ExpectedMaterials and set the result of the validation in the PresentedMaterialValidationStatus variable.

The method is called by the material integrity agent, i.e. when MaterialIntegrityAgent is External.

The method is executed only when the MaterialValidationStatus is Waiting.

The signature of this Method is specified below. Table 51 specifies the Arguments representation.

Signature

	SetPresentedMaterialValidationStatus (
	  [in]  MaterialValidationStatusEnumeration		ValidationResult,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 51 – SetPresentedMaterialValidationStatus Method Arguments
Argument Description
ValidationResultThe result of the validation of the PresentedMaterial.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

The material validation is performed checking (1) a sublot, (2) material lot of the sublot and (3) material definition of the PresentedMaterial against each material sublot in the ExpectedMaterials array. When one matches, the PresentedMaterial is valid and its ValidationStatus is set to True, otherwise False.

The PresentedMaterial is compared against a material sublot from the ExpectedMaterials array as follows being valid when all checks are True:

Sublot:

The PresentedMaterial sublot MES_ID is equal to the sublot MES_ID of a material sublot from the ExpectedMaterials. If the MES_ID of a material sublot from the ExpectedMaterials is Null, then the result of the check is true.

Material lot:

If AllowMixedLots is True, then the result of the check is True. If AllowMixedLots is False, then the result of the check is True for the first presented MaterialSublot and for all subsequent MaterialSublots of the same MaterialLot.

The PresentedMaterial MaterialStockStatus is Unrestricted or equal to the ExpectedMaterial MaterialStockStatus. For example, a ripping machine processes blocked material.

The BestUsedBeforeDate of the material sublot from the ExpectedMaterials is not greater than the current date. If BestUsedBeforeDate is NULL, then the result of this check is true.

Material Definition:

The PresentedMaterial material definition MES_ID is equal to an ExpectedMaterial material definition MES_ID. If the ExpectedMaterial MES_ID is Null, then the result of the check is true.

When the material is validated, the machine proceeds loading it. If it is not validated, the IntegrityRejectedMaterialLogType event is triggered and when the PresentedMaterial is unloaded and the loading procedure terminates, the LoadingPointUnloadedLogType event is generated. If the underlying system cannot reject the invalid material automatically, a MaterialUnloadingRequiredLogType event is generated.

8.9 MaterialOutputPointType ObjectType

8.9.1 Overview

This OPC UA MaterialOutputPointType ObjectType describes the capability and real time information about the hand-over point of material from one machine module to another.

The MaterialOutputPointType is formally defined in the following table.

Table 52 – MaterialOutputPointType Definition
Attribute Value
BrowseNameMaterialOutputPointType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableDownstreamHeld0:Boolean0:PropertyTypeM, RO
0:HasComponentVariableNominalProductionRate0:DoubleMaterialRateTypeM, RO
0:HasComponentVariableProducedMaterialMasterTotal0:DoubleMaterialQuantityVariableTypeM, RO
0:HasPropertyVariableMaterialDefinitionMaterialDefinitionType0:PropertyTypeM, RO
0:HasPropertyVariableMES_ID0:String0:PropertyTypeM, RW
0:HasComponentVariableActualProductionRate0:DoubleMaterialRateTypeM, RO, HR
0:HasComponentVariableProducedMaterialMaterialSublotType0:BaseDataVariableTypeM, RO
0:HasComponentVariableProducedMaterialTotal0:DoubleMaterialQuantityVariableTypeM, RO, HR
0:HasComponentVariableProductionRateState0:LocalizedText0:StateVariableTypeM, RO, HR
0:HasPropertyVariableMaterialPointDefinitionMaterialPointType0:PropertyTypeM, RO
0:GeneratesEventObjectTypeMaterialOutputProducedLogType
Conformance Units
TMC Data Collection
BrowseName Description
DownstreamHeld

When the downstream machine module cannot receive the product flow, the upstream machine is required to hold the transfer of product to the downstream machine module.

The Variable DownstreamHeld is True when the corresponding Variable UpstreamHold in the connected MaterialLoadingPoint is True.

NominalProductionRate The nominal rate at which the output is produced, a.k.a. the machine design speed.
ProducedMaterialMasterTotalThe total quantity of complete sublots created at the machine material output. The value is never reset.
MaterialDefinitionThe material definition of the material that the material output is expected to produce.
MES_IDA higher-level system e.g., MES, identification of the carrier.
ProducedMaterialThe sublot currently being produced by the material output. The sublot quantity is updated by the underlying system as output is generated.
ActualProductionRate The actual rate at which the output is being produced.
ProducedMaterialTotalThe total quantity of complete sublots created at the machine material output.
ProductionRateState

The ProductionRateState provides information about the state of the production rate justifying why the ActualProductionRate is different from the NominalProductionRate. At a minimum the list of states below shall be provided:

Id=0, Speed is at Nominal value

Id=1, Speed Changed by Operator

Id=2, Speed Followed from Downstream Machine

Id=3, Speed Reduced due to high material level at outfeed

Id=4, Speed Reduced due to internal low material level

Id=5, Speed Reduced due to Emptying Mode

Id=6, Speed Reduced due to internal procedure (e.g. calibration)

Id=7, Speed Reduced due to input material change (e.g. foil splicing, inner frame bobbin change, etc.)

Id=8, Speed Changed by Remote Host

When the actual rate is not measured, Id=0 Speed is at Nominal value will be returned. The speed set by an external host, if any, is used as the NominalProductionRate.

Null speed is a speed reduction. The list may be extended for specific states not already covered in the list above.

MaterialPointDefinitionThe Property MaterialPointDefinition contains the identification of the material point and the material that is processed.

8.10 MaterialStorageBufferType ObjectType

The MaterialStorageBufferType ObjectType describes locations where the product is stored in a machine module and the stored product.

The MaterialStorageBufferType representation in the AddressSpace is formally defined in the following table.

Table 53 – MaterialStorageBufferType Definition
Attribute Value
BrowseNameMaterialStorageBufferType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableActualLoadingRate0:DoubleMaterialRateTypeM, RO, HR
0:HasComponentVariableLoadingRateState0:LocalizedText0:StateVariableTypeM, RO, HR
0:HasPropertyVariableMaterialPointDefinitionMaterialStorageBufferDataType0:PropertyTypeM, RO
0:HasPropertyVariableMES_ID0:String0:PropertyTypeM, RW
0:HasPropertyVariableMixingLogicStorageMixingLogicEnumeration0:PropertyTypeM, RW
0:HasComponentVariableNominalLoadingRate0:DoubleMaterialRateTypeM, RO
0:HasComponentVariableNominalUnloadingRate0:DoubleMaterialRateTypeM, RO
0:HasPropertyVariableStorageLogicStorageLogicEnumeration0:PropertyTypeM, RO
0:HasComponentVariableStoredLot0:DoubleMaterialLotVariableTypeM, RO, HR
0:HasPropertyVariableTotalStorageCapacity0:Double0:PropertyTypeM, RW
0:HasComponentVariableActualUnloadingRate0:DoubleMaterialRateTypeM, RO, HR
0:HasComponentVariableUnloadingRateState0:LocalizedText0:StateVariableTypeM, RO, HR
Conformance Units
TMC Core Production
BrowseName Description
IDThe unique identifier for the material storage buffer.
ActualLoadingRateThe rate at which the material is loaded onto the material storage buffer. The variable ActualLoadingRate indicates the quantity of the material consumed in 60 seconds.
LoadingRateState

The LoadingRateState provides information about the state of the loading rate justifying why the ActualLoadingRate is different from the NominalLoadingRate. At a minimum the list of states below shall be provided:

Id=0, Speed is at Nominal value

Id=1, Speed Changed by Operator

Id=2, Speed Followed from Upstream Internal

Id=3, Speed Reduced due to Upstream Internal low material level

Id=4, Speed Reduced due to internal high material level

Id=5, Speed Reduced due to Filling Mode

Id=6, Speed Reduced due to internal procedure (e.g. calibration)

Id=7, Speed Reduced due to input material change (e.g. foil splicing, inner frame bobbin change, etc.)

Id=8, Speed Changed by Remote Host

When the actual rate is not measured, Id=0 Speed is at Nominal value will be returned. The speed set by an external host, if any, is used as the NominalLoadingRate.

Null speed is a speed reduction. The list may be extended for specific states not already covered in the list above.

MaterialPointDefinitionThe Property MaterialPointDefinition contains the identification of the material point and the material that is processed or stored in the buffer.
MES_IDThe unique identifier of the material buffer storage according to a higher-level system, e.g. MES or ERP.
MixingLogic MixingLogic identifies if and how materials can be mixed in the MaterialStorageBuffer.
NominalLoadingRateThe MaterialStorageBuffer loading rate at nominal conditions.
NominalUnloadingRateThe MaterialStorageBuffer unloading rate at nominal conditions.
StorageLogicThe logic used at the buffer storage to store and retrieve material.
StoredLotThe material stored in the material storage buffer.
TotalStorageCapacityThe total capacity of the material storage buffer.
ActualUnloadingRateThe rate at which the material is unloaded from the material storage buffer. The variable ActualUnloadingRate indicates the quantity of the material consumed in 60 seconds.
UnloadingRateState

The UnloadingRateState provides information about the state of the unloading rate justifying why the ActualUnloadingRate is different from the NominalUnloadingRate. At a minimum the list of states below shall be provided:

Id=0, Speed is at Nominal value

Id=1, Speed Changed by Operator

Id=2, Speed Followed from Downstream Internal

Id=3, Speed Reduced due to low material level

Id=4, Speed Reduced due to Downstream Internal high material level

Id=5, Speed Reduced due to Emptying Mode

Id=6, Speed Reduced due to internal procedure (e.g. calibration)

Id=7, Speed Reduced due to input material change (e.g. foil splicing, inner frame bobbin change, etc.)

Id=8, Speed Changed by Remote Host

When the actual rate is not measured, Id=0 Speed is at Nominal value will be returned. The speed set by an external host, if any, is used as the NominalUnloadingRate.

Null speed is a speed reduction. The list may be extended for specific states not already covered in the list above.

8.11 MaterialRejectionPointType ObjectType

8.11.1 Overview

The MaterialRejectionPointType describes a device that is capable of rejecting product from the product flow. The MaterialRejectionPointType is formally defined in the following table.

Table 54 – MaterialRejectionPointType Definition
Attribute Value
BrowseNameMaterialRejectionPointType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableMaterialDefinitionMaterialDefinitionType0:PropertyTypeM, RO
0:HasPropertyVariableMES_ID0:String0:PropertyTypeM, RW
0:HasComponentVariableRejectedMaterialMasterTotal0:DoubleMaterialQuantityVariableTypeM, RO
0:HasComponentVariableRejectedMaterialTotal0:DoubleMaterialQuantityVariableTypeM, RO, HR
0:HasComponentVariableRejectedMaterialRatio0:Double0:BaseDataVariableTypeM, RO
0:HasComponentVariableRejectionCountMasterTotal0:UInt640:BaseDataVariableTypeM, RO
0:HasComponentVariableRejectionCountTotal0:UInt640:BaseDataVariableTypeM, RO, HR
0:HasPropertyVariableRejectionMode0:Boolean0:PropertyTypeM, RW
0:HasPropertyVariableMaterialPointDefinitionMaterialPointType0:PropertyTypeM, RO
0:HasComponentVariableRejectionsRatio0:Double0:BaseDataVariableTypeM, RO, HR
0:HasComponentMethodSetRejectionModeSee below.O
0:GeneratesEventObjectTypeMaterialRejectedLogType
0:GeneratesEventObjectTypeRejectionModeChangeLogType
Conformance Units
TMC Data Collection
BrowseName Description
MaterialDefinitionThe material definition for the material to be rejected at the rejection trap.
MES_IDUnique identifier for the material point in an external system, e.g. MES.
RejectedMaterialMasterTotalThe total material quantity rejected at the rejection trap. The total is never reset to zero.
RejectedMaterialTotalThe total material quantity rejected at the rejection trap. The total is reset to zero only when the ResetRejecitonTotals is invoked.
RejectedMaterialRatioThe Variable MaterialRejectedRatio is the ratio of the total material rejected (MaterialRejectedTotal) over the total good product and is computed by the underlying system.
RejectionCountMasterTotalThe total number of times the rejection trap was triggered. The total is never reset to zero.
RejectionModeWhen RejectionMode is True, the rejection trap discharges material when triggered, otherwise no material is rejected.
MaterialPointDefinitionThe Property MaterialPointDefinition contains the identification of the material point and the material that is processed.
RejectionsRatioThe Variable RejectionsRatio is the ratio between the good product output total and the rejected quantity total.
RejectionCountTotalThe total number of times the rejection trap was triggered. The total is reset to zero only when the ResetRejectionTotals is invoked.

8.11.2 SetRejectionMode Method

The Method SetRejectionMode enables or disables the rejection trap.

The signature of this Method is specified below. Table 55 specifies the Arguments representation.

Signature

	SetRejectionMode (
	  [in]  0:Boolean     					RejectionMode,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 55 – SetRejectionMode Method Arguments
Argument Description
RejectionModeWhen True, the rejection trap rejects.When False, the rejection trap does not reject.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.12 DefectDetectionSensorType ObjectType

8.12.1 Overview

The DefectDetectionSensorType represents a sensor or sensing system fitted to the machine module that detects product defects or a quality sampling point that can be triggered by an operator.

The DefectDetectionSensorType is formally defined in the following table.

Table 56 – DefectDetectionSensorType Definition
Attribute Value
BrowseNameDefectDetectionSensorType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObject<SensorFunction>SensorFunctionTypeMP
0:HasComponentObjectData0:FolderTypeO
0:HasComponentVariableDetectionCountMasterTotal0:UInt640:BaseDataVariableTypeM, RO
0:HasComponentVariableDetectionCountTotal0:UInt640:BaseDataVariableTypeM, RO, HR
0:HasPropertyVariableDetectionMode0:Boolean0:PropertyTypeM, RW
0:HasComponentMethodSetDetectionModeSee below.O
0:GeneratesEventObjectTypeDetectionModeChangeLogType
Conformance Units
TMC Quality Assurance and Control
BrowseName Description
SensorFunctionThe sensor functions that the defect detection sensor or system is measuring.
DetectionCountMasterTotalThe total number of times a detection occurred. The total is never reset to zero.
DetectionCountTotalThe total number of times a detection occurred. The total is reset to zero only when the ResetProductionTotals method in the MachineModuleProductionType is executed successfully.
DetectionModeWhen DetectionMode is True, the defect detection sensor or system detects defects and the inner sensor functions are enabled, meaning they can be active or not. When DetectionMode is False, the inner sensor functions are also not active.

The components of the DefectDetectionSensorType have additional subcomponents which are defined in the following table.

Table 57 – DefectDetectionSensorType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Data0:HasComponent Variable<DataItem>0:BaseDataType0:BaseDataVariableTypeOP, RO

8.12.2 SetDetectionMode Method

The Method SetDetectionMode enables or disables the defect detection sensor.

The signature of this Method is specified below. Table 58 specifies the Arguments representation.

Signature

	SetDetectionMode (
	  [in]  0:Boolean     					Enable,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 58 – SetDetectionMode Method Arguments
Argument Description
EnableSpecifies if the method enables, when True, or disables, when False, the defect detection sensor.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

The Method SetDetectionMode sets the DetectionMode of the defect detection sensor and of its components, i.e. sensor functions and defect reasons.

8.13 SensorFunctionType ObjectType

8.13.1 Overview

The SensorFunctionType describes a single measuring function or quality sampling function and is formally defined in the following table.

Table 59 – SensorFunctionType Definition
Attribute Value
BrowseNameSensorFunctionType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObject<DefectReason>DefectReasonTypeOP
0:HasPropertyVariableDetectionMode0:Boolean0:PropertyTypeM, RW
0:HasComponentMethodLoadReferenceFeaturesSee below.O
0:HasComponentVariableSensorValue0:Number0:AnalogUnitTypeO, RO
0:HasComponentMethodSetDetectionModeSee below.O
0:HasComponentObjectUIInfoUIInformationTypeO
0:GeneratesEventObjectTypeDetectionModeChangeLogType
Conformance Units
TMC Quality Assurance and Control
BrowseName Description
<DefectReason>The defect reasons triggered by the sensor function.
DetectionModeWhen DetectionMode is True, the sensor function measures the sensor value and the inner defect reasons are enabled, meaning they can be active or not. When DetectionMode is False, the inner defect reasons are also not active.
SensorValueThe value measured for the sensor function.
UIInfoThe visualization resources to display the SensorFunctionType on the User Interface.

8.13.2 LoadReferenceFeatures Method

The Method LoadReferenceFeatures loads binary profiles to be used as references for defect detection.

The signature of this Method is specified below. Table 60 specifies the Arguments representation.

Signature

	LoadReferenceFeatures (
	  [in]  0:ByteString[]     				Features,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 60 – LoadReferenceFeatures Method Arguments
Argument Description
FeaturesThe list of binary profiles used as references for a detection system.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.13.3 SetDetectionMode

The Method SetDetectionMode enables or disables the defect detection sensor.

The signature of this Method is specified below. Table 61 specifies the Arguments representation.

Signature

	SetDetectionMode (
	  [in]  0:Boolean     					Enable,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 61 – SetDetectionMode Method Arguments
Argument Description
EnableSpecifies if the method enables, when True, or disables, when False, the sensor function.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

The Method SetDetectionMode sets the DetectionMode of the sensor function and of its components, i.e. the defect reasons.

8.14 DefectReasonType ObjectType

8.14.1 Overview

The DefectReasonType describes a defect reason that is monitored by a SensorFunction. The DefectReasonType is formally defined in the following table.

Table 62 – DefectReasonType Definition
Attribute Value
BrowseNameDefectReasonType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableDetectionMode0:Boolean0:PropertyTypeM, RW
0:HasComponentVariableDetectionCountMasterTotal0:UInt640:BaseDataVariableTypeM, RO
0:HasComponentVariableDetectionCountTotal0:UInt640:BaseDataVariableTypeM, RO, HR
0:HasComponentObjectUIInfoUIInformationTypeO
0:HasComponentMethodSetDetectionModeSee below.O
0:GeneratesEventObjectTypeDetectionModeChangeLogType
0:GeneratesEventObjectTypeDefectDetectedLogType
Conformance Units
TMC Quality Assurance and Control
BrowseName Description
DetectionModeWhen DetectionMode is True, the defect reason is triggered. When DetectionMode is False, the defect reason is not active, i.e. never triggered.
DetectionCountMasterTotalThe total number of times the defect reason occurred. The total is never reset to zero.
DetectionCountTotalThe total number of times a defect reason occurred. The total is reset to zero only when the ResetProductionTotals method in the MachineModuleProductionType is executed successfully.
UIInfoThe visualization resources to display the DefectReasonType on the User Interface.

8.14.2 SetDetectionMode

The Method SetDetectionMode enables or disables the defect detection sensor.

The signature of this Method is specified below. Table 63 specifies the Arguments representation.

Signature

	SetDetectionMode (
	  [in]  0:Boolean     					Enable,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 63 – SetDetectionMode Method Arguments
Argument Description
EnableSpecifies if the method enables, when True, or disables, when False, the defect reason.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.15 EquipmentModuleType ObjectType

8.15.1 Overview

The EquipmentModuleType ObjectType represents an equipment module according to the ISA 95 Physical Structure.

The EquipmentModuleType is formally defined in the following table.

Table 64 – EquipmentModuleType Definition
Attribute Value
BrowseNameEquipmentModuleType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectConfigurationEquipmentModuleConfigurationTypeM
0:HasComponentObjectControlModules0:FolderTypeO
0:HasComponentObjectLiveStatusEquipmentModuleLiveStatusTypeM
0:HasComponentObjectProcessControlLoops0:FolderTypeO
0:HasComponentObjectProcessItems0:FolderTypeO
0:HasComponentObjectSetupEquipmentModuleSetupTypeM
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
ConfigurationThe Configuration contains all digital settings, stop reasons and root causes of an equipment module.
ControlModulesThe ControlModules folder contains the control modules belonging to the equipment module.
LiveStatusThe LiveStatus Object contains information about the real time status of the equipment module and provides affordances to control the equipment module remotely in real time.
ProcessControlLoopsThe ProcessControlLoops folder contains process control loops of the equipment module.
ProcessItemsThe ProcessItems folder contains process items of the equipment module.
SetupThe Setup Object contains the value of all the settings (including mechanical adjustments) required to run production as well as affordances to validate and load settings for the equipment module.

The components of the EquipmentModuleType have additional subcomponents which are defined in the following table.

Table 65 – EquipmentModuleType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
ControlModules0:HasComponent Object <ControlModule> ControlModuleTypeOP
ControlModules0:HasComponent Object AnalogInputs 0:FolderTypeO
0:HasComponent Object <AnalogInput> AnalogInputTypeOP
ControlModules0:HasComponent Object DigitalInputs 0:FolderTypeO
0:HasComponent Object <DigitalInput> DigitalInputTypeOP
ControlModules0:HasComponent Object Motors 0:FolderTypeO
0:HasComponent Object <Motor> MotorTypeOP
ControlModules0:HasComponent Object Sensors 0:FolderTypeO
0:HasComponent Object <Sensor> SensorTypeOP
ControlModules0:HasComponent Object Valves 0:FolderTypeO
0:HasComponent Object <Valve> ValveTypeOP
ProcessControlLoops0:HasComponentObject <ProcessControlLoop> ProcessControlLoopTypeOP
ProcessItems0:HasComponentObject <ProcessItem> ProcessItemTypeOP
ProcessItems0:HasComponentObject <ProcessControlItem> ProcessControlItemTypeOP

8.16 EquipmentModuleConfigurationType ObjectType

8.16.1 Overview

The EquipmentModuleConfigurationType ObjectType contains all digital settings, stop reasons and root causes of an equipment module.

The EquipmentModuleConfigurationType is formally defined in the following table.

Table 66 – EquipmentModuleConfigurationType Definition
Attribute Value
BrowseNameEquipmentModuleConfigurationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariable<ConfigurationItem>0:BaseDataType0:DataItemTypeOP, RO
0:HasPropertyVariableLastChangeDate0:UtcTime0:PropertyTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
ConfigurationItemA data item used for configuration of the equipment module such as for example a setting, stop reason, root cause or another editable field. The data item type is any BaseDataType, e.g., string, float, integer and so on, for maximum flexibility.
LastChangeDateThe UTC date and time when the configuration was last changed.

8.17 EquipmentModuleLiveStatusType ObjectType

8.17.1 Overview

The EquipmentModuleLiveStatusType ObjectType contains information about the real time status of the equipment module and provides affordances to control the control module remotely in real time.

The EquipmentModuleLiveStatusType is formally defined in the following table.

Table 67 – EquipmentModuleLiveStatusType Definition
Attribute Value
BrowseNameEquipmentModuleLiveStatusType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethodAcknowledgeAlarmsSee below.O
0:HasComponentObjectAlarms0:FolderTypeM
0:HasPropertyVariableControlModeControlModeEnumeration0:PropertyTypeM, RW
0:HasComponentObjectData0:FolderTypeO
0:HasComponentMethodSendCommandSee below.O
0:HasComponentMethodSetControlModeSee below.O
0:HasPropertyVariableStateStateEnumeration0:PropertyTypeM, RO
0:HasComponentObjectStateMachineTMCStateMachineTypeO
0:GeneratesEventObjectTypeDiscreteAlarmType
0:GeneratesEventObjectTypeControlModeChangeLogType
0:GeneratesEventObjectTypeStateChangeLogType
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
AlarmsThe Alarms folder contains alarms of the equipment module.
ControlModeThe ControlMode describes the current control mode of the equipment module.
DataThe Data folder provides additional production data that is not already identified by TMC.
StateThe State Property describes the status of the state machine controlling the equipment module. State provides a subset of the information of the state machine when the latter is implemented.
StateMachineThe state machine describes the current state of the equipment module, the possible transitions, and their conditions.

The components of the EquipmentModuleLiveStatusType have additional subcomponents which are defined in the following table.

Table 68 – EquipmentModuleLiveStatusType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Alarms0:HasComponentObject <Alarm> 0:DiscreteAlarmTypeOP
Data0:HasComponentVariable <DataItem> 0:BaseDataType 0:BaseDataVariableTypeOP, RO

8.17.2 AcknowledgeAlarms Method

The AcknowledgeAlarms method acknowledges the alarms of the equipment module and control modules belonging to it.

The signature of this Method is specified below. Table 69 specifies the Arguments representation.

Signature

	AcknowledgeAlarms (
	  [out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 69 – AcknowledgeAlarms Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.17.3 SendCommand Method

The Method SendCommand sends a command to change the state of the equipment module state machine remotely.

The signature of this Method is specified below. Table 70 specifies the Arguments representation.

Signature

	SendCommand (
	  [in]  CommandEnumeration				Command,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 70 – SendCommand Method Arguments
Argument Description
CommandThe command to be sent to the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.17.4 SetControlMode Method

The SetControlMode Method sets the control mode of the equipment module.

The signature of this Method is specified below. Table 71 specifies the Arguments representation.

Signature

	SetControlMode (
	  [in]  ControlModeEnumeration			ControlMode,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 71 – SetControlMode Method Arguments
Argument Description
ControlModeThe control mode to be set to the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.18 EquipmentModuleSetupType ObjectType

8.18.1 Overview

The EquipmentModuleSetupType ObjectType contains the value of all the settings required to run as well as affordances to validate and load settings for the equipment module.

The EquipmentModuleSetupType is formally defined in the following table.

Table 72 – EquipmentModuleSetupType Definition
Attribute Value
BrowseNameEquipmentModuleSetupType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariable<SetupItem>0:BaseDataType0:DataItemTypeOP, RW
Conformance Units
TMC Basic Visualisation and Control

8.19 ControlModuleType ObjectType

8.19.1 Overview

The ControlModuleType ObjectType represents a control module according to the ISA 95 Physical Structure.

The ControlModuleType is formally defined in the following table.

Table 73 – ControlModuleType Definition
Attribute Value
BrowseNameControlModuleType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectAggregatesControlModuleAggregatesTypeO
0:HasComponentObjectConfigurationControlModuleConfigurationTypeM
0:HasComponentObjectLiveStatusControlModuleLiveStatusTypeM
0:HasComponentObjectSetupControlModuleSetupTypeO
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 configuration (i.e., seldom changing) settings, stop reasons and root causes of a control module.
LiveStatus LiveStatus Object provides information about the real time status of the control module and affordances to control the control module remotely in real time.
Setup Setup provides the value of all the digital settings required to run the control module.

8.20 ControlModuleAggregatesType ObjectType

8.20.1 Overview

The ControlModuleAggregatesType ObjectType contains aggregated data for the control module e.g. running hours for a motor.

The ControlModuleAggregatesType is formally defined in the following table.

Table 74 – ControlModuleAggregatesType Definition
Attribute Value
BrowseNameControlModuleAggregatesType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariable<AggregateItem>0:BaseDataType0:BaseDataVariableTypeOP, RO
0:HasComponentMethodResetAggregatesSee below.M
0:HasPropertyVariableValidSince0:UtcTime0:PropertyTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
AggregateItemAn aggregate data item computed by the control module.
ValidSinceThe UTC date and time of the last aggregates reset.

8.20.2 ResetAggregates Method

The ResetAggregates resets the aggregates of the control module.

The signature of this Method is specified below. Table 75 specifies the Arguments representation.

Signature

	ResetAggregates (
	  [out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 75 – ResetAggregates Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.21 ControlModuleConfigurationType ObjectType

8.21.1 Overview

The ControlModuleConfigurationType ObjectType contains all digital settings, stop reasons and root causes of a control module.

The ControlModuleConfigurationType is formally defined in the following table.

Table 76 – ControlModuleConfigurationType Definition
Attribute Value
BrowseNameControlModuleConfigurationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariable<ConfigurationItem>0:BaseDataType0:DataItemTypeOP, RO
0:HasPropertyVariableDeviceLifeSpan0:UInt320:PropertyTypeO, RO
0:HasPropertyVariableValidSince0:UtcTime0:PropertyTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
ConfigurationItemA digital setting for the control module e.g. parameter, stop reason or root cause.
DeviceLifeSpanThe control module expected life span duration.
ValidSinceThe UTC date and time when the configuration was last changed.

8.22 ControlModuleLiveStatusType ObjectType

8.22.1 Overview

The ControlModuleLiveStatusType ObjectType contains information about the real time status of the control module and provides affordances to control the control module remotely in real time.

The ControlModuleLiveStatusType is formally defined in the following table.

Table 77 – ControlModuleLiveStatusType Definition
Attribute Value
BrowseNameControlModuleLiveStatusType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethodAcknowledgeAlarmsSee below.O
0:HasComponentObjectAlarms0:FolderTypeM
0:HasPropertyVariableControlModeControlModeEnumeration0:PropertyTypeM, RW
0:HasComponentObjectData0:FolderTypeO
0:HasComponentObjectInterlocks0:FolderTypeO
0:HasComponentObjectMeasurements0:FolderTypeO
0:HasComponentObjectProcessControlLoops0:FolderTypeO
0:HasComponentMethodSendCommandSee below.O
0:HasComponentMethodSetControlModeSee below.O
0:HasPropertyVariableStateStateEnumeration0:PropertyTypeM, RO
0:HasComponentObjectStateMachineTMCStateMachineTypeO
0:GeneratesEventObjectTypeControlModeChangeLogType
0:GeneratesEventObjectTypeDiscreteAlarmType
0:GeneratesEventObjectTypeStateChangeLogType
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
AlarmsThe Alarms folder provides alarms of the control module.
ControlModeThe ControlMode describes the current control mode of the equipment module.
DataThe Data folder contains additional data whose structure and name are not known in advance.
InterlocksThe Interlocks Folder provides the interlocks that, when not True, do not allow the operation of the control module.
MeasurementsThe Measurement Folder provides measurement values produced by the control module that do not require a dedicated process item e.g., actual motor current.
ProcessControlLoopsThe ProcessControlLoops Folder contains regulation systems of the control module e.g., servo drives.
StateThe State Property describes the status of the state machine controlling the control module. State provides a subset of the information of the state machine, when the latter is implemented.
StateMachineThe StateMachine describes the current state of the control module, the possible transitions, and their conditions.

The components of the ControlModuleLiveStatusType have additional subcomponents which are defined in the following table.

Table 78 – ControlModuleLiveStatusType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Alarms0:HasComponentObject <Alarm> 0:DiscreteAlarmTypeOP
Data0:HasComponentVariable <DataItem> 0:BaseDataType 0:BaseDataVariableTypeOP, RO
Interlocks0:HasComponentVariable <InterlockConditionItem> 0:Boolean 0:BaseDataVariableTypeOP, RO
Measurements0:HasComponentVariable <MeasurementItem> 0:Number 0:AnalogItemTypeOP, RO
ProcessControlLoops0:HasComponentObject <ProcessControlLoop> ProcessControlLoopTypeOP

8.22.2 AcknowledgeAlarms Method

The AcknowledgeAlarms Method acknowledges the alarms of the control module.

The signature of this Method is specified below. Table 79 specifies the Arguments representation.

Signature

	AcknowledgeAlarms (
	  [out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 79 – AcknowledgeAlarms Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.22.3 SendCommand Method

The Method SendCommand sends a command to change the state of the control module state machine remotely.

The signature of this Method is specified below. Table 80 specifies the Arguments representation.

Signature

	SendCommand (
	  [in]  CommandEnumeration				Command,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 80 – SendCommand Method Arguments
Argument Description
CommandThe command to be sent to the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.22.4 SetControlMode Method

The SetControlMode Method sets the control mode of the control module.

The signature of this Method is specified below. Table 81 specifies the Arguments representation.

Signature

	SetControlMode (
	  [in]  ControlModeEnumeration			ControlMode,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 81 – SetControlMode Method Arguments
Argument Description
ControlModeThe control mode to be set to the machine module.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.23 ControlModuleSetupType ObjectType

8.23.1 Overview

The ControlModuleSetupType ObjectType contains the value of all the settings required to run as well as affordances to validate and load settings for the control module.

The ControlModuleSetupType is formally defined in the following table.

Table 82 – ControlModuleSetupType Definition
Attribute Value
BrowseNameControlModuleSetupType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariable<SetupItem>0:BaseDataType0:DataItemTypeOP, RW
Conformance Units
TMC Basic Visualisation and Control

8.24 UIInformationType ObjectType

8.24.1 Overview

The UIInformationType provides graphical specifications required for creating faceplates to display the information made available by the OPC UA Server.

When the information described in the UIInformationType is provided, an OPC UA Client can render the visualisation without further configuration efforts. Thus a suitable zero-config, zero- engineering visualisation is possible.

The UIInformationType is formally defined in the following table.

Table 83 – UIInformationType Definition
Attribute Value
BrowseNameUIInformationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethodDeleteUIResourceSee below.M
0:HasComponentMethodLoadUIResourceSee below.M
0:HasPropertyVariablePositionX0:Double0:PropertyTypeM, RW
0:HasPropertyVariablePositionY0:Double0:PropertyTypeM, RW
0:HasPropertyVariablePositionZ0:Double0:PropertyTypeM, RW
0:HasPropertyVariableResizable0:Boolean0:PropertyTypeM, RW
0:HasComponentObjectUIResources0:FolderTypeM
0:HasPropertyVariableWidth0:Double0:PropertyTypeM, RW
Conformance Units
TMC Advanced Visualisation and Control
BrowseName Description
PositionX PositionX is the relative horizontal position of the top-left corner of the object rendering in the target visualization scope.
PositionY PositionX is the relative vertical position of the top-left corner of the object rendering in the target visualization scope.
PositionZ PositionZ is the depth of the object rendering in the target visualization scope.
ResizableWhen Resizable is True, the UI resource Width is rescaled based on the actual display size.
UIResources

The UIResources folder contains any number of vectorial images of the object to be rendered in the status/mode defined by the name of the file, e.g. Running.svg is the representation of the object when the status is running.

The server will persist external resources that a client will save into the folder.

Width Width is the width of the object visualization in the target visualization scope.

The components of the UIInformationType have additional subcomponents which are defined in the following table.

Table 84 – UIInformationType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
UIResources0:HasPropertyVariable<ResourceName>0:String0:PropertyTypeOP, RW
UIResources0:HasPropertyVariableDefault0:String0:PropertyTypeM, RW

8.24.2 LoadUIResource Method

The Method LoadUIResource loads a UI resource in the underlying system for visualization. It will override the existing UI resource by the same name.

The signature of this Method is specified below. Table 85 specifies the Arguments representation.

Signature

	LoadUIResource (
	  [in] 	0:String							ResourceName,
	  [in] 	0:String							ResourceValue,
	  [out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 85 – LoadUIResource Method Arguments
Argument Description
ResourceNameThe name of the UI resource to be created in the underlying system.
ResourceValueThe value that the UI resource will obtain in the underlying system, i.e. the SVG file.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.24.3 DeleteUIResource Method

The Method DeleteUIResource permanently removes a UI resource from the underlying system memory.

The signature of this Method is specified below. Table 86 specifies the Arguments representation.

Signature

	DeleteUIResource (
	  [in]		0:String							ResourceName,
	  [out] 	MethodExecutionFeedbackType		ExecutionFeedback);
Table 86 – DeleteUIResource Method Arguments
Argument Description
ResourceNameThe name of the UI resource to be deleted from the underlying system.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.25 AnalogInputType ObjectType

The AnalogInputType ObjectType describes an analog input signal.

The AnalogInputType representation in the AddressSpace is formally defined in the following table.

Table 87 – AnalogInputType Definition
Attribute Value
BrowseNameAnalogInputType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableRawValue0:Number0:AnalogItemTypeM, RO
0:HasComponentObjectSetupAnalogInputSetupTypeM
0:HasComponentVariableValue0:Double0:AnalogItemTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
RawValueThe raw value of the analog input.
SetupThe settings to set up the analog input.
ValueThe engineering unit value of the analog input.

8.26 DigitalInputType ObjectType

The DigitalInputType ObjectType describes a digital input signal.

The DigitalInputType representation in the AddressSpace is formally defined in the following table.

Table 88 – DigitalInputType Definition
Attribute Value
BrowseNameDigitalInputType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectSetupDigitalInputSetupTypeM
0:HasComponentVariableValue0:Boolean0:TwoStateDiscreteTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
SetupThe settings to set up the digital input.
ValueThe raw value of the digital input.

8.27 MotorType ObjectType

The MotorType ObjectType describes a motor.

The MotorType representation in the AddressSpace is formally defined in the following table.

Table 89 – MotorType Definition
Attribute Value
BrowseNameMotorType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectAggregatesMotorAggregatesTypeM
0:HasComponentObjectSetupMotorSetupTypeM
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
AggregatesThe aggregated data exposed by the motor.
SetupThe settings to set up the motor.

8.28 SensorType ObjectType

The SensorType ObjectType describes a sensor.

The SensorType representation in the AddressSpace is formally defined in the following table.

Table 90 – SensorType Definition
Attribute Value
BrowseNameSensorType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectSetupControlModuleSetupTypeM
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
SetupThe settings to set up the motor.

8.29 ValveType ObjectType

The ValveType ObjectType describes a valve.

The ValveType representation in the AddressSpace is formally defined in the following table.

Table 91 – ValveType Definition
Attribute Value
BrowseNameValveType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectAggregatesValveAggregatesTypeM
0:HasComponentObjectConfigurationControlModuleConfigurationTypeM
0:HasComponentObjectSetupValveSetupTypeM
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
AggregatesThe aggregated data exposed by the valve.
ConfigurationThe configuration settings for the valve.
SetupThe settings to set up the valve.

8.30 ControlModuleAggregatesType ObjectType

The ControlModuleAggregatesType ObjectType provides aggregates computed by the underlying system for the control module.

The ControlModuleAggregatesType representation in the AddressSpace is formally defined in the following table.

Table 92 – ControlModuleAggregatesType Definition
Attribute Value
BrowseNameControlModuleAggregatesType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariable<AggregateItem>0:BaseDataType0:BaseDataVariableTypeOP, RO
0:HasComponentMethodResetAggregatesSee below.M
0:HasPropertyVariableValidSince0:UtcTime0:PropertyTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
AggregateItemA single aggregate data point exposed by the control module.
ValidSinceThe time of the last reset for the aggregates.

8.30.1 ResetAggregates Method

The ResetAggregates Method resets the aggregates of the control module.

The signature of this Method is specified below. Table 93 specifies the Arguments representation.

Signature

	ResetAggregates (
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 93 – ResetAggregates Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.31 MotorAggregatesType ObjectType

The MotorAggregatesType ObjectType provides aggregates computed by the underlying system for an analog input.

The MotorAggregatesType representation in the AddressSpace is formally defined in the following table.

Table 94 – MotorAggregatesType Definition
Attribute Value
BrowseNameMotorAggregatesType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleAggregatesType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableTotalRunningHours0:UInt320:BaseDataVariableTypeM, RO
0:HasComponentVariableTotalStartStopCounter0:UInt320:BaseDataVariableTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
TotalRunningHoursThe total number of running hours for the motor.
TotalStartStopCounterThe total number of times the motor was started and stopped.

8.32 ValveAggregatesType ObjectType

The ValveAggregatesType ObjectType provides aggregates computed by the underlying system for an analog input.

The ValveAggregatesType representation in the AddressSpace is formally defined in the following table.

Table 95 – ValveAggregatesType Definition
Attribute Value
BrowseNameValveAggregatesType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleAggregatesType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableCycleCounter0:UInt320:BaseDataVariableTypeM, RO
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
CycleCounterThe total number of times the solenoid valve was energized and de-energised.

8.33 AnalogInputSetupType ObjectType

The AnalogInputSetupType ObjectType provides settings and other affordance to set up an analog input.

The AnalogInputSetupType representation in the AddressSpace is formally defined in the following table.

Table 96 – AnalogInputSetupType Definition
Attribute Value
BrowseNameAnalogInputSetupType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleSetupType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableForcedValue0:Double0:AnalogItemTypeM, RW
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
ForcedValueThe value to set as the input value when control mode is manual.

8.34 DigitalInputSetupType ObjectType

The DigitalInputSetupType ObjectType provides settings and other affordance to set up an analog input.

The DigitalInputSetupType representation in the AddressSpace is formally defined in the following table.

Table 97 – DigitalInputSetupType Definition
Attribute Value
BrowseNameDigitalInputSetupType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleSetupType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableForcedValue0:Boolean0:DataItemTypeM, RW
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
ForcedValueThe value to set as the input value when control mode is manual.

8.35 MotorSetupType ObjectType

The MotorSetupType ObjectType provides settings and other affordances to set up a motor.

The MotorSetupType representation in the AddressSpace is formally defined in the following table.

Table 98 – MotorSetupType Definition
Attribute Value
BrowseNameMotorSetupType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleSetupType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariableDirectionMotorDirectionEnumeration0:DataItemTypeO, RW
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
DirectionThe rotation direction of the motor.

8.36 ValveSetupType ObjectType

The ValveSetupType ObjectType provides aggregates computed by the underlying system for a valve.

The ValveSetupType representation in the AddressSpace is formally defined in the following table.

Table 99 – ValveSetupType Definition
Attribute Value
BrowseNameValveSetupType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the ControlModuleSetupType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentVariablePositionSetPoint0:Double0:AnalogItemTypeO, RW
Conformance Units
TMC Basic Visualisation and Control
BrowseName Description
PositionSetPointThe position set point for the valve to reach.

8.37 UserInterfaceType ObjectType

8.37.1 Overview

The UserInterfaceType provides a generic User Interface description consisting of:

An overview display, modelled by OverVU;

A close-up, detail display, modelled by ZoomedVU;

A control-loop view where the connections (modelled by the LoopVUReferences) among objects belonging to the same control loop are shown;

An overlay display where KPIs are shown, modelled by KPIVU;

A control panel, where shown objects can be read only (modelled by ControlPanelVURO) or read-write (modelled by ControlPanelVURW);

The UserInterfaceType is formally defined in the following table.

Table 100 – UserInterfaceType Definition
Attribute Value
BrowseNameUserInterfaceType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectControlPanelVURO0:Double0:BaseObjectTypeM
0:HasComponentObjectControlPanelVURW0:Double0:BaseObjectTypeM
0:HasComponentObjectKPIVU0:Double0:BaseObjectTypeM
0:HasComponentObjectLoopVUReferences0:Double0:BaseObjectTypeM
0:HasComponentObjectOverVU0:Double0:BaseObjectTypeM
0:HasComponentObjectZoomedVU0:Double0:BaseObjectTypeM
Conformance Units
TMC Advanced Visualisation and Control
BrowseName Description
ControlPanelVUROThe control panel area where read-only objects are shown. Objects connected to a ControlPanelVURO by means of a non-hierarchical reference of type IsDisplayedBy are shown in the control panel.
ControlPanelVURWThe control panel area where read-write objects are shown. Objects connected to a ControlPanelVURW by means of a non-hierarchical reference of type IsDisplayedBy are shown in the control panel.
KPIVUThe object collecting variables to be displayed in the KPI section. Objects connected to a KPIVU by means of a non-hierarchical reference of type IsDisplayedBy are shown in the KPI display area.
LoopVUReferencesThe collection of references to control loops to be displayed. Non-hierarchical references connected to LoopVuReferences by means of a non-hierarchical reference of type IsDisplayedBy are shown in the control panel.
OverVUThe overview of the UI interface. Objects connected to an OverVU by means of a non-hierarchical reference of type IsDisplayedBy are shown in the overview display.
ZoomedVUThe zooned view of the UI interface. Objects connected to a ZoomedVU by means of a non-hierarchical reference of type IsDisplayedBy are shown in the zoomed in area.

8.38 ProductionOrderOrchestrationLayerType ObjectType

8.38.1 Overview

The ProductionOrderOrchestrationLayerType (POOL) ObjectType consists of a set of variables, generated events and methods that are used to orchestrate production orders for a set of Machine Modules that implement the MachineModuleProductionType and are variously connected in a production line. The production line is also known as a Process Cell according to ANSI/ISA-88.00.01-2010 Physical Model.

The POOL ObjectType is an external application, i.e. it is not implemented by a machine module. Nonetheless it is of interest for machine modules and their implementations because of the tight connection and interaction.

The ProductionOrderOrchestrationLayerType is formally defined in the following table.

Table 101 – ProductionOrderOrchestrationLayerType
Attribute Value
BrowseNameProductionOrderOrchestrationLayerType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableProductionOrdersRetentionTime0:UInt32M, RW
0:HasComponentObjectProductionOrders0:FolderTypeM
0:HasComponentMethodAbortProductionOrderSee below.M
0:HasComponentMethodAssignProductionOrderSee below.M
0:HasComponentMethodCompleteProductionOrderSee below.M
0:HasComponentMethodGetDataSetSee below.M
0:HasComponentMethodGetMaterialListSee below.M
0:HasComponentMethodGetProductionOrderSee below.M
0:HasComponentMethodReleaseProductionOrderSee below.M
0:HasComponentMethodStartProductionOrderSee below.M
0:HasComponentMethodUnassignProductionOrderSee below.M
0:HasComponentMethodUnreleaseProductionOrderSee below.M
Conformance Units
TMC Production Order Orchestration Layer

The components of the ProductionOrderOrchestrationLayerType have additional subcomponents which are defined in the following table.

Table 102 – ProductionOrderOrchestrationLayerType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
ProductionOrders0:HasComponent Object <ProductionOrderNumber>ProductionOrderExecutionStateMachineTypeOP
BrowseName Description
ProductionOrdersRetentionTimeThe time in hours a ProductionOrderStateMachine is retained in memory after the production order is complete. When the ProductionOrdersRetentionTime is elapsed, the ProductionOrderExecutionStateMachine is discarded from memory and from the containing folder ProductionOrders.
ProductionOrders

ProductionOrders is a folder that organizes objects of type ProductionOrderExecutionStateMachineType i.e., one state machine per production order managed by POOL.

Production orders are managed by POOL from their release by a higher-level system, e.g. MES, MOM, to their normal or abnormal completion or un-release and afterwards are persisted for a period of time defined by ProductionOrdersRetentionTime after which production orders are discarded from memory.

The reader shall note that there is one production order state machine for any given production order for the entire process cell regardless of the number of machine modules, each having its own StateMachine of the Production object within the MachineModule. In ways that are defined in this section, ProductionOrderExecutionStateMachine consolidates and coordinates the state of all machine modules with respect to the production order.

8.38.2 AbortProductionOrder Method

The AbortProductionOrder Method is used to abort a production order that is in execution or starting or completing in the production line.

To execute the method, POOL will in turn invoke the AbortProductionOrder method at all the machine modules where the production order is present in the arrary AssignedProductionOrders.

The signature of this Method is specified below. Table 103 specifies the Arguments representation.

Signature

	AbortProductionOrder(
	  [in]  ProductionOrderHeaderType   	POToAbort,
	  [out] MethodExecutionFeedbackType     ExecutionFeedback);
Table 103 – AbortProductionOrder Method Arguments
Argument Description
POToAbortThe Production Order to be aborted.
ExecutionFeedbackThe result of the execution of the method.

8.38.3 AssignProductionOrder Method

The AssignProductionOrder Method is used to assign a production order to one infeed machine module where it shall be executed.

To execute the method, POOL will in turn invoke the AssignProductionOrder method at the machine modules identified by the argument MachineModulesToAssign.

Assignment is required and useful because there are generally many machine modules that can execute a production order so that it is necessary to identify which machine module will be executing the specific one. The attentive reader shall note that a production order may require many infeed machine modules to execute the production order.

The signature of this Method is specified below. Table 104 specifies the Arguments representation.

Signature

	AssignProductionOrder(
	  [in]  ProductionOrderHeaderType   	POToAssign,
	  [in]  0:String[]					     MachineModuleUserName,
	  [out] MethodExecutionFeedbackType     ExecutionFeedback);
Table 104 - AssignProductionOrder Method Arguments
Argument Description
POToAssignThe Production Order Header to be assigned.
MachineModuleUserNameThe user name of the machine modules to which the PO is assigned. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
ExecutionFeedbackThe result of the execution of the method.

8.38.4 CompleteProductionOrder Method

The CompleteProductionOrder Method is used to complete a production order in execution.

To execute the method, POOL will in turn invoke the CompleteProductionOrder method at the machine module identified by the input argument MachineModuleToComplete.

The signature of this Method is specified below. Table 105 specifies the Arguments representation.

Signature

	CompleteProductionOrder(
	  [in]  ProductionOrderHeaderType		POToComplete,
	  [in]  0:String						MachineModuleUserName,
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 105 - CompleteProductionOrder Method Arguments
Argument Description
POToCompleteThe Production Order Header to be completed.
MachineModuleUserNameThe user name of the machine module where the PO is completed. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
ExecutionFeedbackThe result of the execution of the method.

8.38.5 GetDataSet Method

The signature of this Method is specified below. Table 106 specifies the Arguments representation.

Signature

	GetDataSet(
	 	[in]  ProductionOrderHeaderType		POHeader,
		[in]  0:String						MachineModuleUserName,
	[out] DataSetType					DataSet,
	 	[out] MethodExecutionFeedbackType     ExecutionFeedback);
Table 106 - GetDataSet Method Arguments
Argument Description
POHeaderThe Production Order Header of the dataset to be retrieved.
MachineModuleUserNameThe user name of the machine module for which the information is requested. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
DataSetThe DataSet for the production order with Production Order Header.
ExecutionFeedbackThe result of the execution of the method.

8.38.6 GetMaterialList Method

The GetMaterialList Method is used to retrieve the material list information from a production order header. The primary intended use is for a memory constrained underlying system to retrieve the production order information just in time without storing it for all assigned production orders.

The signature of this Method is specified below. Table 107 specifies the Arguments representation.

Signature

	GetMaterialList(
	 	[in]  ProductionOrderHeaderType		POHeader,
		[in]  0:String						MachineModuleUserName,
	[out] MaterialListType				MaterialList,
	 	[out] MethodExecutionFeedbackType     ExecutionFeedback);
Table 107 - GetMaterialList Method Arguments
Argument Description
POHeaderThe Production Order Header of the Material List to be retrieved.
MaterialListThe Material List for the production order with Production Order Header.
MachineModuleUserNameThe user name of the machine module for which the information is requested. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
ExecutionFeedbackThe result of the execution of the method.

8.38.7 GetProductionOrder Method

The GetProductionOrder Method is used to retrieve the complete production order information starting with a production order header as an input argument. The primary intended use is for a memory constrained underlying system to retrieve the production order information just in time without storing it for many assigned production orders. In the memory constrained case, it is the responsibility of the underlying system to retrieve the production order information on time without delaying the production order execution start.

The signature of this Method is specified below. Table 108 specifies the Arguments representation.

Signature

	GetProductionOrder(
	 	[in]  ProductionOrderHeaderType		POHeader,
		[in]  0:String						MachineModuleUserName,
	[out] ProductionOrderType			ProductionOrder,
	 	[out] MethodExecutionFeedbackType     ExecutionFeedback);
Table 108 - GetProductionOrder Method Arguments
Argument Description
POHeaderThe Production Order Header of the Material List to be retrieved.
MachineModuleUserNameThe user name of the machine module for which the information is requested. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
ProductionOrderThe complete Production Order with header Production Order Header.
ExecutionFeedbackThe result of the execution of the method.

8.38.8 ReleaseProductionOrder Method

The ReleaseProductionOrder Method is used to make a production order available to a machine module for orchestrated execution in a production line (Process Cell according to ANSI/ISA-88.00.01-2010 Physical Model).

When the method is executed successfully, a new ProductionOrderExecutionStateMachine is instantiated for the released production order when not already existing.

When the ProductionOrderExecutionStateMachine is in state Unreleased, the successful execution of the method causes the state transition to Releasing.

The signature of this Method is specified below.

Signature

	ReleaseProductionOrder(
	 	[in]  OrchestrationProductionOrderType POToRelease,
	[in]  0:String						 MachineModuleUserName,
	 	[out] MethodExecutionFeedbackType      ExecutionFeedback);
Table 109 - ReleaseProductionOrder Method Arguments
Argument Description
POToReleaseThe Production Order Header for the Production Order to be released.
MachineModuleUserNameThe user name of the machine module where the PO is released. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
ExecutionFeedbackThe result of the execution of the method.

8.38.9 StartProductionOrder Method

The StartProductionOrder Method is used to start the execution of a production order at a machine module specifying the loading points that input materials will be fed to and the output points where output will be directed.

To execute the method, POOL will in turn invoke the StartProductionOrder method at the machine module identified by the input argument MachineModuleToStart.

The signature of this Method is specified below.

Signature

	StartProductionOrder(
	 	[in]  ProductionOrderHeaderType	POToStart,
	[in]  0:String					MachineModuleUserName,
	[in]  0:String[]					SourceMaterialLoadingPointIDs,
	[in]  0:String[]				 DestinationMaterialOutputPointIDs,
	 	[out] MethodExecutionFeedbackType	ExecutionFeedback);
Table 110 - StartProductionOrder Method Arguments
Argument Description
POToStartThe Production Order Header for the Production Order to be started.
MachineModuleUserNameThe user name of the machine module where the PO is started. The machine module identifier is exposed in the UserName in the MachineModuleConfiguration of the machine module.
SourceMaterialLoadingPointIDsThe MaterialLoadingPoints where input materials will be fed for the Production Order to be started.
DestinationMaterialOutputPointIDsThe MaterialOutputPoints where output materials will be directed to for the Production Order to be started.
ExecutionFeedbackThe result of the execution of the method.

8.38.10 UnassignProductionOrder Method

The UnAssignProductionOrder Method is used to unassign a production order previously assigned to an infeed machine module. It reverses the effect of the AssignProductionOrder method when the production order is not yet in execution.

To execute the method, POOL will in turn invoke the UnAssignProductionOrder method at all the machine modules where the production order is present in the AssignedProductionOrders.

The signature of this Method is specified below.

Signature

	UnassignProductionOrder(
	 	[in]  ProductionOrderHeaderType		 POToUnassign,
		[out] MethodExecutionFeedbackType      ExecutionFeedback);
Table 111 - UnassignProductionOrder Method Arguments
Argument Description
POToUnassignThe Production Order Header for the Production Order to be unassigned.
ExecutionFeedbackThe result of the execution of the method.

8.38.11 UnreleaseProductionOrder Method

The UnreleaseProductionOrder Method is used to reverse the effect of the ReleaseProductionOrder method and make a previously released production order unavailable for assignment and production.

For example, it is used prior to sending changes to an already released production order.

The signature of this Method is specified below. Table 109 specifies the Arguments representation.

Signature

	ReleaseProductionOrder(
	 	[in]  ProductionOrderHeaderType		 POToUnrelease,
		[out] MethodExecutionFeedbackType      ExecutionFeedback);
Table 112 - UnreleaseProductionOrder Method Arguments
Argument Description
POToUnreleaseThe Production Order Header for the Production Order to be unreleased.
ExecutionFeedbackThe result of the execution of the method.

8.39 MachineModuleProductionStateMachineType Object Type

The MachineModuleProductionStateMachineType provides state information about the execution of a production order at a Machine Module.

The MachineModuleProductionStateMachineType is formally defined in the following table.

Table 113 – MachineModuleProductionStateMachineType Definition
Attribute Value
BrowseNameMachineModuleProductionStateMachineType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the FiniteStateMachineType defined in OPC 10000-5 Annex B, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectAborted0:StateType
0:HasComponentObjectAbortedToComplete0:TransitionType
0:HasComponentVariableAbortedToCompleteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAborting0:StateType
0:HasComponentObjectAbortingToAborted0:TransitionType
0:HasComponentVariableAbortingToAbortedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAssigned0:StateType
0:HasComponentObjectAssignedToComplete0:TransitionType
0:HasComponentVariableAssignedToCompleteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAssignedToStarting0:TransitionType
0:HasComponentVariableAssignedToStartingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectComplete0:InitialStateType
0:HasComponentObjectCompleteToAssigned0:TransitionType
0:HasComponentVariableCompleteToAssignedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectCompleting0:StateType
0:HasComponentObjectCompletingToAborting0:TransitionType
0:HasComponentVariableCompletingToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectCompletingToComplete0:TransitionType
0:HasComponentVariableCompletingToCompleteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectExecute0:StateType
0:HasComponentObjectExecuteToAborting0:TransitionType
0:HasComponentVariableExecuteToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectExecuteToCompleting0:TransitionType
0:HasComponentVariableExecuteToCompletingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentVariableLastTransition0:LocalizedText0:FiniteTransitionVariableTypeM, RO
0:HasComponentObjectStarting0:StateType
0:HasComponentObjectStartingToAborting0:TransitionType
0:HasComponentVariableStartingToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectStartingToExecute0:TransitionType
0:HasComponentVariableStartingToExecuteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:GeneratesEventObjectTypeProductionOrderTransitionLogType
Conformance Units
TMC Single PO Production
BrowseName Description
Assigned

When the CurrentState of the StateMachine is Assigned, the information for at least one production order to be started is available.

When the CurrentState of the StateMachine is Assigned and there is a production order in execution, i.e. ProductionOrder is not null, the state transitions to Starting.

The variable ProductionOrder is set in the following cases:

For infeed machine modules: the method StartProductionOrder method is executed successfully.

For non-infeed machine modules with more than one assigned production order: when AssignedProductionOrders[] contains more than one production order, the method StartProductionOrder method is executed successfully.

For non-infeed machine modules configured to start automatically: when the AssignedProductionOrders array contains one production order and the state of the upstream machine modules is Execute or Starting for the same production order.

When the CurrentState of the StateMachine is Assigned and there are no assigned production orders, i.e. no elements in the array AssignedProductionOrders, the CurrentState of the MachineModuleProductionStateMachineType transitions to Complete.

Starting

When the CurrentState of the StateMachine is Starting, the underlying system performs the preparation to process product or parts according to the started production order. The machine module can receive input product(s) or parts from the loading points specified by the production order according to its machine specific sequence.

For example, while the CurrentState of the StateMachine is Starting, the machine may be pre-filled, warmed up or cooled down according to the requirements of the production order.

When the underlying system completes such machine specific sequence and starts processing product, the CurrentState of the StateMachine transitions to Execute.

When the CurrentState of the StateMachine is Starting and the AbortProductionOrder method is successfully executed, the ProductionState state machine transitions to Aborting.

The machine module shall not receive product from an upstream machine module processing a different production order. To this goal, the machine module underlying system will set UpstreamHold to True for the MaterialLoadingPoints connected to (1) non-active upstream machine modules and (2) active upstream machine modules with a different ProductionOrder.

Execute

When the CurrentState of the StateMachine is Execute, the production order is processed and input product(s) or parts are received.

In order to further detail the processing phases, the StateMachine object within the object LiveStatus may be used. The states and transitions of the machine are defined according to the underlying system specifics.

The machine module shall not receive product from an upstream machine module processing a different production order. To this end, the machine module will set UpstreamHold to True of the MaterialLoadingPoints connected to (1) non-active upstream machine modules and (2) active upstream machine modules with a different ProductionOrder.

For machine modules with AutoComplete false, when the CurrentState of the StateMachine is Execute, the successful execution of the method CompleteProductionOrder causes the state transition to Completing.

For machine modules with AutoComplete true, when the CurrentState of the StateMachine is Execute and the active upstream machine modules are in state Complete the CurrentState of the StateMachine transitions to Completing.

The described logic implements production order propagation in a standardized and transparent way.

Completing

When the CurrentState of the StateMachine is Completing, the underlying system performs the preparation to complete the production order which is complete in the active upstream machine modules.

When the underlying system completes such machine specific sequence, including checking that no more product(s) or parts are being received and that no more product(s) or parts that can be processed are in the machine module, and the active upstream machine modules’ state is Complete, the CurrentState of the StateMachine transitions to Complete and the ProductionOrder is nulled. Likewise, when the CurrentState of the StateMachine is Execute and the active upstream machine modules are in state Assigned or Execute for a different production order.

The machine module shall not receive product from an upstream machine module processing a different production order. To this end, the machine module will set UpstreamHold to True of the MaterialLoadingPoints connected to (1) non-active upstream machine modules and (2) active upstream machine modules with a different ProductionOrder.

Aborting

When the CurrentState of the StateMachine is Aborting, the machine module stops receiving additional product or parts from the active upstream machine modules in an orderly way.

When the stopping sequence is complete the CurrentState of the StateMachine transitions to Aborted.

Aborted

When the CurrentState of the StateMachine is Aborted, the product(s) or parts present in the machine module are discharged from the machine, either through machine specific automatic sequences or manually by the operators.

When the CurrentState of the StateMachine is Aborted and the ClearProductionOrder method is successfully executed, the state transitions to Complete.

Complete

When the CurrentState of the StateMachine is Complete, the machine module does not accept any more input product(s) or parts, the ProductionOrder is nulled and the machine is ready to execute a new production order.

When the CurrentState of the StateMachine is Complete and there is at least one production order in the AssignedProductionOrders array, the CurrentState of the StateMachine transitions to Assigned.

The components of the MachineModuleProductionStateMachineType have additional references which are defined in the following table.

Table 114 – MachineModuleProductionStateMachineType Additional References
SourceBrowsePath Reference Type Is Forward TargetBrowsePath
AbortedToComplete0:FromStateTrueAborted
0:HasGuardTrueAbortedToCompleteGuard
0:ToStateTrueComplete
0:HasEffectTrueProductionOrderTransitionLogType
AbortingToAborted0:FromStateTrueAborting
0:HasGuardTrueAbortingToAbortedGuard
0:ToStateTrueAborted
0:HasEffectTrueProductionOrderTransitionLogType
AssignedToComplete0:FromStateTrueAssigned
0:HasGuardTrueAssignedToCompleteGuard
0:ToStateTrueComplete
0:HasEffectTrueProductionOrderTransitionLogType
AssignedToStarting0:FromStateTrueAssigned
0:HasGuardTrueAssignedToStartingGuard
0:ToStateTrueStarting
0:HasEffectTrueProductionOrderTransitionLogType
CompleteToAssigned0:FromStateTrueComplete
0:HasGuardTrueCompleteToAssignedGuard
0:ToStateTrueAssigned
0:HasEffectTrueProductionOrderTransitionLogType
CompletingToAborting0:FromStateTrueCompleting
0:HasGuardTrueCompletingToAbortingGuard
0:ToStateTrueAborting
0:HasEffectTrueProductionOrderTransitionLogType
CompletingToComplete0:FromStateTrueCompleting
0:HasGuardTrueCompletingToCompleteGuard
0:ToStateTrueComplete
0:HasEffectTrueProductionOrderTransitionLogType
ExecuteToAborting0:FromStateTrueExecute
0:HasGuardTrueExecuteToAbortingGuard
0:ToStateTrueAborting
0:HasEffectTrueProductionOrderTransitionLogType
ExecuteToCompleting0:FromStateTrueExecute
0:HasGuardTrueExecuteToCompletingGuard
0:ToStateTrueCompleting
0:HasEffectTrueProductionOrderTransitionLogType
StartingToAborting0:FromStateTrueStarting
0:HasGuardTrueStartingToAbortingGuard
0:ToStateTrueAborting
0:HasEffectTrueProductionOrderTransitionLogType
StartingToExecute0:FromStateTrueStarting
0:HasGuardTrueStartingToExecuteGuard
0:ToStateTrueExecute
0:HasEffectTrueProductionOrderTransitionLogType

The component Variables of the MachineModuleProductionStateMachineType have additional Attributes defined in the following table.

Table 115 – MachineModuleProductionStateMachineType Attribute values for child Nodes
BrowsePath Attribute Value
1
2
3
4
5
6
7

8.40 ProductionOrderExecutionStateMachineType Object Type

The ProductionOrderExecutionStateMachineType provides state information about the execution of a production order at a production line.

The ProductionOrderExecutionStateMachineType is formally defined in the following table.

Table 116 - ProductionOrderExecutionStateMachineType Definition
Attribute Value
BrowseNameProductionOrderExecutionStateMachineType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the FiniteStateMachineType defined in OPC 10000-5 Annex B, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableProductionOrderHeaderProductionOrderHeaderType0:PropertyTypeM
0:HasComponentObjectMachineModuleProductionOrders0:FolderTypeM
0:HasComponentObjectAborted0:StateType
0:HasComponentObjectAborting0:StateType
0:HasComponentObjectAssigned0:StateType
0:HasComponentObjectAssigning0:StateType
0:HasComponentObjectComplete0:StateType
0:HasComponentObjectCompleting0:StateType
0:HasComponentObjectExecute0:StateType
0:HasComponentObjectReleased0:StateType
0:HasComponentObjectReleasing0:InitialStateType
0:HasComponentObjectStarting0:StateType
0:HasComponentObjectUnassigning0:StateType
0:HasComponentObjectUnreleased0:StateType
0:HasComponentObjectUnreleasing0:StateType
0:HasComponentObjectAbortingToAborted0:TransitionType
0:HasComponentVariableAbortingToAbortedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAssignedToStarting0:TransitionType
0:HasComponentVariableAssignedToStartingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAssignedToUnassigning0:TransitionType
0:HasComponentVariableAssignedToUnassigningGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAssignedToUnreleasing0:TransitionType
0:HasComponentVariableAssignedToUnreleasingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectAssigningToAssigned0:TransitionType
0:HasComponentVariableAssigningToAssignedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectCompletingToAborting0:TransitionType
0:HasComponentVariableCompletingToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectCompletingToComplete0:TransitionType
0:HasComponentVariableCompletingToCompleteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectExecuteToAborting0:TransitionType
0:HasComponentVariableExecuteToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectExecuteToCompleting0:TransitionType
0:HasComponentVariableExecuteToCompletingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectReleasedToAssigning0:TransitionType
0:HasComponentVariableReleasedToAssigningGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectReleasedToUnreleasing0:TransitionType
0:HasComponentVariableReleasedToUnreleasingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectReleasingToReleased0:TransitionType
0:HasComponentVariableReleasingToReleasedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectReleasingToUnreleasing0:TransitionType
0:HasComponentVariableReleasingToUnreleasingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectStartingToAborting0:TransitionType
0:HasComponentVariableStartingToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectStartingToExecute0:TransitionType
0:HasComponentVariableStartingToExecuteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectUnassigningToReleased0:TransitionType
0:HasComponentVariableUnassigningToReleasedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectUnreleasedToReleased0:TransitionType
0:HasComponentVariableUnreleasedToReleasedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectUnreleasingToUnreleased0:TransitionType
0:HasComponentVariableUnreleasingToUnreleasedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentVariableLastTransition0:LocalizedText0:FiniteTransitionVariableTypeM, RO
0:GeneratesEventObjectTypeProductionOrderTransitionLogTypeM
Conformance Units
TMC Production Order Orchestration Layer
BrowseName Description
ProductionOrderHeaderThe ProductionOrderHeader of the production order in execution. When no production order is in execution, the ProductionOrderNumber in the ProductionOrderHeader is an empty string.
MachineModuleProductionOrdersThe production orders that have been released to the ProductionOrderExecutionLayer. The MachineModuleProductionOrders folder contains one production order for each required machine module having the ProductionOrderHeader (above).

The components of the ProductionOrderExecutionStateMachineType have additional subcomponents which are defined in the following table.

Table 117 – ProductionOrderExecutionStateMachineType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
MachineModuleProductionOrders0:HasComponent Variable<MachineModuleUserName>ProductionOrderType0:BaseDataVariableTypeOP

The components of the ProductionOrderExecutionStateMachineType have additional references which are defined in the following table.

Table 118 – ProductionOrderExecutionStateMachineType Additional References
SourceBrowsePath Reference Type Is Forward TargetBrowsePath
AbortingToAborted0:FromStateTrueAborting
0:HasGuardTrueAbortingToAbortedGuard
0:ToStateTrueAborted
0:HasEffectTrueProductionOrderTransitionLogType
AssignedToStarting0:FromStateTrueAssigned
0:HasGuardTrueAssignedToStartingGuard
0:ToStateTrueStarting
0:HasEffectTrueProductionOrderTransitionLogType
AssignedToUnassigning0:FromStateTrueAssigned
0:HasGuardTrueAssignedToUnassigningGuard
0:ToStateTrueUnassigning
0:HasEffectTrueProductionOrderTransitionLogType
AssignedToUnreleasing0:FromStateTrueAssigned
0:HasGuardTrueAssignedToUnreleasingGuard
0:ToStateTrueUnreleasing
0:HasEffectTrueProductionOrderTransitionLogType
AssigningToAssigned0:FromStateTrueAssigning
0:HasGuardTrueAssigningToAssignedGuard
0:ToStateTrueAssigned
0:HasEffectTrueProductionOrderTransitionLogType
CompletingToAborting0:FromStateTrueCompleting
0:HasGuardTrueCompletingToAbortingGuard
0:ToStateTrueAborting
0:HasEffectTrueProductionOrderTransitionLogType
CompletingToComplete0:FromStateTrueCompleting
0:HasGuardTrueCompletingToCompleteGuard
0:ToStateTrueComplete
0:HasEffectTrueProductionOrderTransitionLogType
ExecuteToAborting0:FromStateTrueExecute
0:HasGuardTrueExecuteToAbortingGuard
0:ToStateTrueAborting
0:HasEffectTrueProductionOrderTransitionLogType
ExecuteToCompleting0:FromStateTrueExecute
0:HasGuardTrueExecuteToCompletingGuard
0:ToStateTrueCompleting
0:HasEffectTrueProductionOrderTransitionLogType
ReleasedToAssigning0:FromStateTrueReleased
0:HasGuardTrueReleasedToAssigningGuard
0:ToStateTrueAssigning
0:HasEffectTrueProductionOrderTransitionLogType
ReleasingToUnreleasing0:FromStateTrueReleasing
0:HasGuardTrueReleasingToUnreleasingGuard
0:ToStateTrueUnreleasing
0:HasEffectTrueProductionOrderTransitionLogType
ReleasingToReleased0:FromStateTrueReleasing
0:HasGuardTrueReleasingToReleasedGuard
0:ToStateTrueReleased
0:HasEffectTrueProductionOrderTransitionLogType
StartingToAborting0:FromStateTrueStarting
0:HasGuardTrueStartingToAbortingGuard
0:ToStateTrueAborting
0:HasEffectTrueProductionOrderTransitionLogType
StartingToExecute0:FromStateTrueStarting
0:HasGuardTrueStartingToExecuteGuard
0:ToStateTrueExecute
0:HasEffectTrueProductionOrderTransitionLogType
UnassigningToReleased0:FromStateTrueUnassigning
0:HasGuardTrueUnassigningToReleasedGuard
0:ToStateTrueReleased
0:HasEffectTrueProductionOrderTransitionLogType
UnreleasedToReleased0:FromStateTrueUnreleased
0:HasGuardTrueUnreleasedToReleasedGuard
0:ToStateTrueReleased
0:HasEffectTrueProductionOrderTransitionLogType
UnreleasingToUnreleased0:FromStateTrueUnreleasing
0:HasGuardTrueUnreleasingToUnreleasedGuard
0:ToStateTrueUnreleased
0:HasEffectTrueProductionOrderTransitionLogType

The component Variables of the ProductionOrderEecutionStateMachineType have additional Attributes defined in the following table.

Table 119 – ProductionOrderExecutionStateMachineType Attribute values for child Nodes
BrowsePath Value Attribute
1
2
3
4
5
6
7
8
9
10
11
12
13

8.41 TMCStateMachineType ObjectType

8.41.1 Overview

The TMCStateMachineType describes the finite state machine of a complex automation item including a machine module, an equipment module and a control module.

The TMCStateMachineType is modelled and inherits from the PackMLBaseStateMachineType defined in OPC 30050 - UA for PackML (OMAC) v1.01 and provides additional TMCMachineStateMachineType and transition information by means of guards implemented by the BooleanGuardVariableType.

The TMCStateMachineType is formally defined in the following table.

Table 120 – TMCStateMachineType Definition
Attribute Value
BrowseNameTMCStateMachineType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the PackMLBaseStateMachineType defined in OPC 30050, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentMethod3:AbortSee OPC 30050, PackMLStateMachineType.O
0:HasComponentObjectAborted0:StateType
0:HasComponentObjectAbortedSubstateStateMachineTypeO
0:HasComponentObjectAbortedToCleared0:TransitionType
0:HasComponentVariableAbortedToClearedGuard0:LocalizedTextBooleanGuardVariableTypeM, RW
0:HasComponentObjectAborting0:StateType
0:HasComponentObjectAbortingToAborted0:TransitionType
0:HasComponentVariableAbortingToAbortedGuard0:LocalizedTextBooleanGuardVariableTypeM, RW
0:HasComponentMethod3:ClearSee OPC 30050, PackMLStateMachineType.O
0:HasComponentObjectCleared0:StateType
0:HasComponentObjectClearedToAborting0:TransitionType
0:HasComponentVariableClearedToAbortingGuard0:LocalizedTextBooleanGuardVariableTypeM, RW
0:HasComponentVariableLastTransition0:LocalizedText0:FiniteTransitionVariableTypeM, RO
0:HasComponentObjectMachineStateTMCMachineStateMachineTypeM
0:GeneratesEventObjectTypeTransitionEventTypeM
Conformance Units
TMC Advanced Equipment Module and Control Module Status

The component Variables of the TMCStateMachineType have additional Attributes defined in the following table.

Table 121 – TMCStateMachineType Attribute Values for Child Nodes
BrowsePath Value Attribute
9
8
19

The components of the TMCStateMachineType have additional references which are defined in the following table.

Table 122 – TMCStateMachineType Additional References
SourceBrowsePath Reference Type Is Forward TargetBrowsePath
Aborted0:HasSubStateMachineTrueAbortedSubstate
AbortedToCleared0:FromStateTrueAborted
0:HasGuardTrueAbortedToClearedGuard
0:HasCauseTrue3:Clear
0:ToStateTrueCleared
0:HasEffectTrueTransitionEventType
AbortingToAborted0:FromStateTrueAborting
0:HasGuardTrueAbortingToAbortedGuard
0:ToStateTrueAborted
0:HasEffectTrueTransitionEventType
ClearedToAborting0:FromStateTrueCleared
0:HasGuardTrueClearedToAbortingGuard
0:HasCauseTrue3:Abort
0:ToStateTrueAborting
0:HasEffectTrueTransitionEventType

8.42 TMCExecuteStateMachineType ObjectType

8.42.1 Overview

The TMCExecuteStateMachineType is modelled and inherits from the PackMLExecuteStateMachineType defined in OPC 30050 - UA for PackML (OMAC) v1.01, and provides additional transition information by means of guards implemented by the BooleanGuardVariableType.

The TMCExecuteStateMachineType is formally defined in the following table.

Table 123 – TMCExecuteStateMachineType Definition
Attribute Value
BrowseNameTMCExecuteStateMachineType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the PackMLExecuteStateMachineType defined in OPC 30050, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectComplete0:StateType
0:HasComponentObjectCompleteSubstateStateMachineTypeO
0:HasComponentObjectCompleteToResetting0:TransitionType
0:HasComponentVariableCompleteToResettingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectCompleting0:StateType
0:HasComponentObjectCompletingToComplete0:TransitionType
0:HasComponentVariableCompletingToCompleteGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectExecute0:StateType
0:HasComponentObjectExecuteSubstateStateMachineTypeO
0:HasComponentObjectExecuteToCompleting0:TransitionType
0:HasComponentVariableExecuteToCompletingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectExecuteToHolding0:TransitionType
0:HasComponentVariableExecuteToHoldingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectExecuteToSuspending0:TransitionType
0:HasComponentVariableExecuteToSuspendingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectHeld0:StateType
0:HasComponentObjectHeldToUnholding0:TransitionType
0:HasComponentVariableHeldToUnholdingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentMethod3:HoldSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentObjectHolding0:StateType
0:HasComponentObjectHoldingToHeld0:TransitionType
0:HasComponentVariableHoldingToHeldGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectIdle0:StateType
0:HasComponentObjectIdleSubstateStateMachineTypeO
0:HasComponentObjectIdleToStarting0:TransitionType
0:HasComponentVariableIdleToStartingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentVariableLastTransition0:LocalizedText0:FiniteTransitionVariableTypeM, RO
0:HasComponentMethod3:ResetSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentObjectResetting0:StateType
0:HasComponentObjectResettingToIdle0:TransitionType
0:HasComponentVariableResettingToIdleGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentMethod3:StartSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentObjectStarting0:StateType
0:HasComponentObjectStartingToExecute0:TransitionType
0:HasComponentVariableStartingToExecuteGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectStartingToHolding0:TransitionType
0:HasComponentVariableStartingToHoldingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentMethod3:SuspendSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentObjectSuspended0:StateType
0:HasComponentObjectSuspendedToHolding0:TransitionType
0:HasComponentVariableSuspendedToHoldingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectSuspendedToUnsuspending0:TransitionType
0:HasComponentVariableSuspendedToUnsuspendingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectSuspending0:StateType
0:HasComponentObjectSuspendingToHolding0:TransitionType
0:HasComponentVariableSuspendingToHoldingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectSuspendingToSuspended0:TransitionType
0:HasComponentVariableSuspendingToSuspendedGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentMethod3:ToCompleteSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentMethod3:UnholdSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentObjectUnholding0:StateType
0:HasComponentObjectUnholdingToExecute0:TransitionType
0:HasComponentVariableUnholdingToExecuteGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectUnholdingToHolding0:TransitionType
0:HasComponentVariableUnholdingToHoldingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentMethod3:UnsuspendSee OPC 30050, PackMLExecuteStateMachineType.O
0:HasComponentObjectUnsuspending0:StateType
0:HasComponentObjectUnsuspendingToExecute0:TransitionType
0:HasComponentVariableUnsuspendingToExecuteGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:HasComponentObjectUnsuspendingToHolding0:TransitionType
0:HasComponentVariableUnsuspendingToHoldingGuard0:LocalizedTextBooleanGuardVariableTypeO, RO
0:GeneratesEventObjectTypeTransitionEventTypeM
Conformance Units
TMC Advanced Equipment Module and Control Module Status

The component Variables of the TMCExecuteStateMachineType have additional Attributes defined in the following table.

Table 124 – TMCExecuteStateMachineType Attribute Values for Child Nodes
Source Path Value Attribute
17
16
6
11
10
4
15
3
5
13
12
14

The components of the TMCExecuteStateMachineType have additional references which are defined in the following table.

Table 125 – TMCExecuteStateMachineType Additional References
SourceBrowsePath Reference Type Is Forward TargetBrowsePath
Complete0:HasSubStateMachineTrueCompleteSubstate
Execute0:HasSubStateMachineTrueExecuteSubstate
Idle0:HasSubStateMachineTrueIdleSubstate
CompleteToResetting0:FromStateTrueComplete
0:HasGuardTrueCompleteToResettingGuard
0:HasCauseTrue3:Reset
0:ToStateTrueResetting
0:HasEffectTrueTransitionEventType
CompletingToComplete0:FromStateTrueCompleting
0:HasGuardTrueCompletingToCompleteGuard
0:ToStateTrueComplete
0:HasEffectTrueTransitionEventType
ExecuteToCompleting0:FromStateTrueExecute
0:HasGuardTrueExecuteToCompletingGuard
0:HasCauseTrue3:ToComplete
0:ToStateTrueCompleting
0:HasEffectTrueTransitionEventType
ExecuteToHolding0:FromStateTrueExecute
0:HasGuardTrueExecuteToHoldingGuard
0:HasCauseTrue3:Hold
0:ToStateTrueHolding
0:HasEffectTrueTransitionEventType
ExecuteToSuspending0:FromStateTrueExecute
0:HasGuardTrueExecuteToSuspendingGuard
0:HasCauseTrue3:Suspend
0:ToStateTrueSuspending
0:HasEffectTrueTransitionEventType
HeldToUnholding0:FromStateTrueHeld
0:HasGuardTrueHeldToUnholdingGuard
0:HasCauseTrue3:Unhold
0:ToStateTrueUnholding
0:HasEffectTrueTransitionEventType
HoldingToHeld0:FromStateTrueHolding
0:HasGuardTrueHoldingToHeldGuard
0:ToStateTrueHeld
0:HasEffectTrueTransitionEventType
IdleToStarting0:FromStateTrueIdle
0:HasGuardTrueIdleToStartingGuard
0:HasCauseTrue3:Start
0:ToStateTrueStarting
0:HasEffectTrueTransitionEventType
ResettingToIdle0:FromStateTrueResetting
0:HasGuardTrueResettingToIdleGuard
0:ToStateTrueIdle
0:HasEffectTrueTransitionEventType
StartingToExecute0:FromStateTrueStarting
0:HasGuardTrueStartingToExecuteGuard
0:ToStateTrueExecute
0:HasEffectTrueTransitionEventType
StartingToHolding0:FromStateTrueStarting
0:HasGuardTrueStartingToHoldingGuard
0:HasCauseTrue3:Hold
0:ToStateTrueHolding
0:HasEffectTrueTransitionEventType
SuspendedToHolding0:FromStateTrueSuspended
0:HasGuardTrueSuspendedToHoldingGuard
0:HasCauseTrue3:Hold
0:ToStateTrueHolding
0:HasEffectTrueTransitionEventType
SuspendedToUnsuspending0:FromStateTrueSuspended
0:HasGuardTrueSuspendedToUnsuspendingGuard
0:HasCauseTrue3:Unsuspend
0:ToStateTrueUnsuspending
0:HasEffectTrueTransitionEventType
SuspendingToHolding0:FromStateTrueSuspending
0:HasGuardTrueSuspendingToHoldingGuard
0:HasCauseTrue3:Hold
0:ToStateTrueHolding
0:HasEffectTrueTransitionEventType
SuspendingToSuspended0:FromStateTrueSuspending
0:HasGuardTrueSuspendingToSuspendedGuard
0:ToStateTrueSuspended
0:HasEffectTrueTransitionEventType
UnholdingToExecute0:FromStateTrueUnholding
0:HasGuardTrueUnholdingToExecuteGuard
0:ToStateTrueExecute
0:HasEffectTrueTransitionEventType
UnholdingToHolding0:FromStateTrueUnholding
0:HasGuardTrueUnholdingToHoldingGuard
0:HasCauseTrue3:Hold
0:ToStateTrueHolding
0:HasEffectTrueTransitionEventType
UnsuspendingToExecute0:FromStateTrueUnsuspending
0:HasGuardTrueUnsuspendingToExecuteGuard
0:ToStateTrueExecute
0:HasEffectTrueTransitionEventType
UnsuspendingToHolding0:FromStateTrueUnsuspending
0:HasGuardTrueUnsuspendingToHoldingGuard
0:ToStateTrueHolding
0:HasEffectTrueTransitionEventType

8.43 TMCMachineStateMachineType ObjectType

8.43.1 Overview

The TMCMachineStateMachineType is modelled and inherits from the PackMLMachineStateMachineType defined in OPC 30050 - UA for PackML (OMAC) v1.01, and provides additional transition information by means of guards implemented by the BooleanGuardVariableType.

The TMCMachineStateMachineType is formally defined in the following table.

Table 126 – TMCMachineStateMachineType Definition
Attribute Value
BrowseNameTMCMachineStateMachineType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the PackMLMachineStateMachineType defined in OPC 30050, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectClearing0:StateType
0:HasComponentObjectClearingToStopped0:TransitionType
0:HasComponentVariableClearingToStoppedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectExecuteStateTMCExecuteStateMachineTypeM
0:HasComponentVariableLastTransition0:LocalizedText0:FiniteTransitionVariableTypeM, RO
0:HasComponentMethod3:ResetSee OPC 30050, PackMLMachineStateMachineType.O
0:HasComponentObjectRunning0:StateType
0:HasComponentObjectRunningToStopping0:TransitionType
0:HasComponentVariableRunningToStoppingGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentMethod3:StopSee OPC 30050, PackMLMachineStateMachineType.O
0:HasComponentObjectStopped0:StateType
0:HasComponentObjectStoppedSubstateStateMachineTypeO
0:HasComponentObjectStoppedToRunning0:TransitionType
0:HasComponentVariableStoppedToRunningGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:HasComponentObjectStopping0:StateType
0:HasComponentObjectStoppingToStopped0:TransitionType
0:HasComponentVariableStoppingToStoppedGuard0:LocalizedTextBooleanGuardVariableTypeM, RO
0:GeneratesEventObjectTypeTransitionEventTypeM
Conformance Units
TMC Advanced Machine Status

The component Variables of the TMCMachineStateMachineType have additional Attributes defined in the following table.

Table 127 – TMCMachineStateMachineType Attribute Values for Child Nodes
Source Path Value Attribute
1
18
2
7

The components of the TMCMachineStateMachineType have additional references which are defined in the following table.

Table 128 – TMCMachineStateMachineType Additional References
SourceBrowsePath Reference Type Is Forward TargetBrowsePath
Stopped0:HasSubStateMachineTrueStoppedSubstate
ClearingToStopped0:FromStateTrueClearing
0:HasGuardTrueClearingToStoppedGuard
0:HasCauseTrue3:Stop
0:ToStateTrueStopped
0:HasEffectTrueTransitionEventType
RunningToStopping0:FromStateTrueRunning
0:HasGuardTrueRunningToStoppingGuard
0:HasCauseTrue3:Stop
0:ToStateTrueStopping
0:HasEffectTrueTransitionEventType
StoppedToRunning0:FromStateTrueStopped
0:HasGuardTrueStoppedToRunningGuard
0:HasCauseTrue3:Reset
0:ToStateTrueRunning
0:HasEffectTrueTransitionEventType
StoppingToStopped0:FromStateTrueStopping
0:HasGuardTrueStoppingToStoppedGuard
0:ToStateTrueStopped
0:HasEffectTrueTransitionEventType

8.44 ProcessItemType ObjectType

8.44.1 Overview

The ProcessItemType is used to measure and monitor over time a measurement point. The ProcessItemType also provides aggregates (Avg, Max, Min, Std, Total) that are computed by the underlying system. The aggregates are computed over a time period or for a product quantity and can be configured by a client altogether with the sampling time.

The ProcessItemType is formally defined in the following table.

Table 129 – ProcessItemType Definition
Attribute Value
BrowseNameProcessItemType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableAggregationWindow0:UInt320:PropertyTypeM, RW
0:HasComponentObjectLimitAlarms0:NonExclusiveLevelAlarmTypeM
0:HasComponentVariableValue0:DoubleDisplayAnalogUnitTypeM, RO, HR
0:HasComponentVariableAvg0:Double0:BaseDataVariableTypeM, RO, HR
0:HasPropertyVariableLastResetTime0:UtcTime0:PropertyTypeM, RO
0:HasComponentVariableMax0:Double0:BaseDataVariableTypeM, RO
0:HasComponentVariableMin0:Double0:BaseDataVariableTypeM, RO
0:HasComponentMethodResetAggregatesSee below.M
0:HasComponentVariableSamplingRate0:Double0:AnalogUnitRangeTypeM, RW
0:HasComponentVariableStd0:Double0:BaseDataVariableTypeM, RO, HR
0:HasComponentVariableTotal0:Double0:BaseDataVariableTypeM, RO
0:HasComponentObjectUIInfoUIInformationTypeO
0:GeneratesEventObjectType0:NonExclusiveLevelAlarmType
0:GeneratesEventObjectTypeProcessItemResetLogType
Conformance Units
TMC Process Variables Ingestion and Control
BrowseName Description
AggregationWindow

Tthe number of samples over which the aggregates are computed. When the number of aggregated samples since the last reset exceeds the AggregationWindow, the aggregates are rolled over, i.e. computed over the last AggregationWindow number of samples.

The value of the AggregationWindow can be set by a client to obtain the desired aggregation.

If the written value is below (above) the minimum (maximum) value that can be managed by the underlying system, the underlying system will overwrite it with the minimum (maximum).

LimitAlarmsThe deviation alarm with 4 thresholds: HighHigh, High, Low, LowLow. All 4 thresholds shall be supported.
ValueValue represents the current value measured by the sensor.
Avg

The average of valid values over the last AggregationWindow samples and after the last reset.

It is only reset by the successful execution of the ResetAggregates method.

LastResetTimeThe time (in UTC) when ResetAggregates was last successfully executed.
Max

The maximum valid value for the last AggregationWindow samples and after the last reset.

It is only reset by the successful execution of the ResetAggregates method.

Min

The minimum valid value for the last AggregationWindow samples and after the last reset.

It is only reset by the successful execution of the ResetAggregates method.

SamplingRate

The rate samples are collected for aggregation. The rate is referred to the either product or time, as indicated by the EURange property.

For example, SamplingRate equal to 100 ms means that the value is measured and collected for aggregation every 100 ms. SamplingRate equal to 10 kg means that the value is measured and collected for aggregation every 10 kg of product. SamplingRate equal to 100 rods means that the value is measured and collected for aggregation every 100 rods of product.

The EURange property of the SamplingRate is read only and defines both the unit of measure and the supported range.

The value of the SamplingRate can be set by a client to obtain the desired sampling rate for aggregation.

If the written value is below (above) the minimum (maximum) value that can be managed by the underlying system, the underlying system will overwrite it with the minimum (maximum).

The underlying system will support equivalent sampling rates of 100ms or better.

Std

The standard deviation of the valid value for the last AggregationWindow samples and after the last reset. After reset, when only one value is available, the standard deviation is not defined and zero will be returned.

It is only reset by the successful execution of the ResetAggregates method.

Total

The accumulated total of the valid value for the last AggregationWindow samples and after the last reset.

It is only reset by the successful execution of the ResetAggregates method.

UIInfoThe visualization resources to display the ProcessItemType on the UserInterface.

8.44.2 ResetAggregates Method

The ResetAggregates Method restarts from new the computation of aggregates performed by the underlying system.

The signature of this Method is specified below. Table 130 specifies the Arguments representation.

Signature

	ResetAggregates (
	  [out] MethodExecutionFeedbackType		ExecutionFeedback);
Table 130 – ResetAggregates Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

When the ResetAggregates method is invoked, an event of type ProcessItemResetLogType is generated with the last value of the aggregate variables, then the aggregates are reset as specified and the LastResetTime is set at the time when the method completes successfully.

8.45 ProcessControlItem ObjectType

8.45.1 Overview

The ProcessItemType is formally defined in the following table.

Table 131 – ProcessControlItemType Definition
Attribute Value
BrowseNameProcessControlItemType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the ProcessItemType, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableOperatorControl0:Boolean0:PropertyTypeM, RO, HR
0:HasPropertyVariableRemoteControlEnable0:Boolean0:PropertyTypeM, RO, HR
0:HasComponentVariableRemoteValue0:Double0:BaseDataVariableTypeM, RW, HR
0:HasPropertyVariableRemoteControl0:Boolean0:PropertyTypeM, RW, HR
0:HasComponentMethodSetRemoteControlSee below.M
BrowseName Description
RemoteValueThe value set by the client to override the object value.
RemoteControlEnableThe RemoteControlEnable variable exposes when the underlying system is ready to activate the RemoteControl upon a request by a client. When RemoteControlEnable is False, the underlying system is not ready and will not activate a request to remotely control the ProcessControlItem.
RemoteControl

The RemoteControl variable lets the underlying system expose which system is currently in control of the ProcessControlItem. More specifically, if RemoteControl is True, the underlying system copies the RemoteValue to the ProcesControlItem Value to drive it, i.e. the ProcessControlItem is remotely controlled. If RemoteControl is False, the underlying system is not using RemoteValue to drive the ProcessControlItem, but another value that is exposed as the ProcessControlItem Value, i.e. the ProcessControlItem is locally controlled.

A client requests (resp. releases) control of the ProcessControlItem by setting RemoteControl to True (resp. False) preferably by invoking the SetRemoteControl Method. If the client does not support methods, then the client sets RemoteControl to True. The underlying system will reset RemoteControl to False if remote control is not activated.

OperatorControlThe OperatorControl variable qualifies the source of the ProcessControlItem Value when RemoteControl is False, otherwise OperatorControl is undefined. When OperatorControl is True, the underlying system exposes the information that the ProcessControlItem Value is modified by the operator with respect to the nominal value, e.g. NominalRate, a.k.a. design speed for a speed control loop. When OperatorControl is False, the underlying system exposes the information that the ProcessControlItem Value is not modified by the operator.

8.45.2 SetRemoteControl Method

The SetRemoteControl Method enables or disables the remote control mode.

The signature of this Method is specified below. Table 132 specifies the Arguments representation.

Signature

	SetRemoteControl (
	  [in]		0:Boolean						Enable,
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 132 – SetRemoteControl Method Arguments
Argument Description
EnableThe flag enables (True) or disables (False) the remote control mode.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

When the method SetRemoteControl completes successfully with input argument Enable equal to True, RemoteControl is set to True and the RemoteAnalogMeasurement persistently overrides the ProcessControlItem value.

When the method SetRemoteControl completes successfully with input argument Enable equal to False, RemoteControl is set to False and the ProcessControlItem value is generated by the underlying system.

8.46 ProcessControlLoopType ObjectType

8.46.1 Overview

The ProcessControlLoopType is the general description of a control loop consisting of the desired value (SetPoint) for a measured value (ProcessValue) which is obtained by acting on an actuator (ControlValue).

The ProcessControlLoopType is formally defined in the following table.

Table 133 – ProcessControlLoopType Definition
Attribute Value
BrowseNameProcessControlLoopType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectsControlValueProcessControlItemTypeM
0:HasComponentObjectsProcessValueProcessControlItemTypeM
0:HasComponentObjectsSetPointProcessControlItemTypeO
0:HasPropertyVariableWatchdogEnabled0:Boolean0:PropertyTypeM, RW
0:HasPropertyVariableWatchdogTimeout0:Duration0:PropertyTypeM, RW
0:HasComponentObjectExternalAlarms0:FolderTypeM
0:GeneratesEventObjectTypeExternalAlarmType
Conformance Units
TMC Process Variables Ingestion and Control
BrowseName Description
ControlValueThe ControlValue is the output of the control loop function. The control value directly drives the actuator.
ProcessValueThe value read by a sensor or other analog measurement of the physical quantity that is monitored.
SetPointThe value we aim to obtain from the ProcessValue by means of driving the control value.
WatchdogEnableWhen WatchdogEnable is True, if a ProcessControlLoop component’s RemoteControl is True and the time between two consecutive writes of the RemoteValue is longer than WatchdogTimeout, then the underlying system will generate an alarm, set RemoteControl to False and take control of the loop. When WatchdogEnable is False, no watchdog alarm is generated.
WatchdogTimeoutThe longest time between two write actions before a watchdog alarm is generated by the underlying system. The value is expressed in milliseconds. If the written value is below (above) the minimum (maximum) value that can be managed by the underlying system, the underlying system will overwrite it with the minimum (maximum).
ExternalAlarmsThe external alarms folder is used to organize external alarms.

The components of the ProcessControlLoopType have additional subcomponents which are defined in the following table.

Table 134 – ProcessControlLoopType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
ExternalAlarms0:HasComponentObject ExternalAlarm1ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm2ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm3ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm4ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm5ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm6ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm7ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm8ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm9ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm10ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject <ExternalAlarmN>ExternalAlarmTypeOP

The ExternalAlarms folder provides 10 spare external alarms that are mandatorily implemented by the underlying system. Additional ones can be added via the ExternalAlarmN optional placeholder.

8.47 CarrierType ObjectType

8.47.1 Overview

The CarrierType ObjectType provides a description for a uniquely identified reusable carrier. Examples of CarrierType implementations are AGVs, trays with RFIDs, IBCs with RFIDs, bins with permanent bar codes.

The CarrierType is formally defined in the following table.

Table 135 – CarrierType Definition
Attribute Value
BrowseNameCarrierType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectData0:FolderTypeO
0:HasComponentMethodEndSubCarrierLoadingSee below.M
0:HasComponentMethodEndSubCarrierUnloadingSee below.M
0:HasPropertyVariableFormFactor0:String0:PropertyTypeM, RO
0:HasPropertyVariableID0:String0:PropertyTypeM, RO
0:HasComponentMethodLoadSubCarrierSee below.M
0:HasComponentMethodLoadSublotsSee below.M
0:HasPropertyVariableMES_ID0:String0:PropertyTypeM, RW
0:HasPropertyVariableParentCarrierID0:String0:PropertyTypeM, RO
0:HasComponentMethodStartSubCarrierLoadingSee below.M
0:HasComponentMethodStartSubCarrierUnloadingSee below.M
0:HasComponentObjectSubCarriers0:FolderTypeO
0:HasComponentVariableSublotsMaterialSublotType[]0:BaseDataVariableTypeO, RO
0:HasComponentMethodUnloadSubCarrierSee below.M
0:HasComponentMethodUnloadSublotsSee below.M
0:GeneratesEventObjectTypeCarrierSublotsChangeLogType
0:GeneratesEventObjectTypeSubCarrierLoadedLogType
0:GeneratesEventObjectTypeSubCarrierLoadingEndedLogType
0:GeneratesEventObjectTypeSubCarrierLoadingStartedLogType
0:GeneratesEventObjectTypeSubCarrierUnloadedLogType
0:GeneratesEventObjectTypeSubCarrierUnloadingEndedLogType
0:GeneratesEventObjectTypeSubCarrierUnloadingStartedLogType
Conformance Units
TMC Intralogistics at the machine
BrowseName Description
DataThe Data folder organizes implementation specific data for the carrier.
FormFactorThe form factor of the carrier e.g., trolley, AGV, core, IBC, etc.
IDThe underlying system identification of the carrier.
MES_IDA higher-level system e.g., MES, identification of the carrier.
ParentCarrierIDThe unique identifier of the carrier that contains the carrier in question.
SubCarriersThe SubCarriers folder organizes carriers contained in the carrier.
SubLotsThe SubLots contained in the carrier.

The components of the CarrierType have additional subcomponents which are defined in the following table.

Table 136 – CarrierType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Data 0:HasComponentVariable <DataItem> 0:BaseDataType 0:BaseDataVariableTypeOP, RO
SubCarriers 0:HasComponentObject <SubCarrier> CarrierTypeOP

8.47.2 EndSubCarrierLoading Method

The EndSubCarrierLoading Method informs the underlying system that the loading of (sub) carriers into the carrier is complete.

The signature of this Method is specified below. Table 137 specifies the Arguments representation.

Signature

	EndSubCarrierLoading (
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 137 – EndSubCarrierLoading Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.3 EndSubCarrierUnloading Method

The EndSubCarrierUnloading Method informs the underlying system that the unloading of (sub) carriers into the carrier is complete.

The signature of this Method is specified below. Table 138 specifies the Arguments representation.

Signature

	EndSubCarrierUnloading (
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 138 – EndSubCarrierUnloading Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.4 LoadSubCarrier Method

The LoadSubCarrier Method requests the underlying system to load a subcarrier into the carrier that is currently being loaded.

The signature of this Method is specified below. Table 139 specifies the Arguments representation.

Signature

	LoadSubCarrier (
	  [in]		0:String							ID,
	  [in]		0:String							MESID,
	  [in]		0:String							ParentCarrierID,
	  [in]		MaterialSublotType[]				Sublots,
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 139 – LoadSubCarrier Method Arguments
Argument Description
IDThe unique identifier of the carrier to be loaded.
MESIDThe higher-level system identifier for the carrier to be loaded.
ParentCarrierIDThe unique identifier of the parent carrier i.e., the carrier containing the carrier.
SublotsThe material sublots to be loaded to the carrier.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.5 LoadSublots Method

The LoadSublots Method requests the underlying system to load one or more material sublots into the carrier that is currently being loaded.

The signature of this Method is specified below. Table 140 specifies the Arguments representation.

Signature

	LoadSublots (
	  [in]		MaterialSublotType[]				Sublots,
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 140 – LoadSublots Method Arguments
Argument Description
SublotsThe material sublots to be loaded to the carrier.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.6 StartSubCarrierLoading Method

The StartSubCarrierLoading Method informs the underlying system that the loading of (sub) carriers into the carrier has started.

The underlying system is expected to perform its own loading process while the (sub) carriers are loaded.

The signature of this Method is specified below. Table 141 specifies the Arguments representation.

Signature

	StartSubCarrierLoading (
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 141 – StartSubCarrierLoading Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.7 StartSubCarrierUnloading Method

The StartSubCarrierUnloading Method informs the underlying system that the unloading of (sub) carriers from the carrier has started.

The underlying system is expected to perform its own unloading process while the (sub) carriers are unloaded.

The signature of this Method is specified below. Table 142 specifies the Arguments representation.

Signature

	StartSubCarrierUnloading (
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 142 – StartSubCarrierUnloading Method Arguments
Argument Description
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.8 UnloadSubCarrier Method

The UnloadSubCarrier Method requests the underlying system to unload a subcarrier from the carrier that is currently being unloaded.

The signature of this Method is specified below. Table 143 specifies the Arguments representation.

Signature

	LoadSubCarrier (
	  [in]		0:String							ID,
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 143 – UnloadSubCarrier Method Arguments
Argument Description
IDThe unique identifier of the carrier to be loaded.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.47.9 UnloadSublots Method

The UnloadSublots Method requests the underlying system to unload one or more sublots from the carrier that is currently being unloaded.

The signature of this Method is specified below. Table 144 specifies the Arguments representation.

Signature

	UnloadSublots (
	  [in]		0:String[]						SublotIDs,
	  [out]	MethodExecutionFeedbackType		ExecutionFeedback);
Table 144 – UnloadSublots Method Arguments
Argument Description
SublotIDsThe unique identifiers of the material sublots to be unloaded.
ExecutionFeedbackThe extended feedback returning a detailed message in case of execution failure.

8.48 MaterialLocationType ObjectType

The MaterialLocationType ObjectType describes locations where material is stored around a machine module.

Examples of such locations are the designated areas on the floor where materials are delivered for consumption or where material produced by the machine is waiting to be collected. When the location where the material is stored is integral part of the mechanics or controls of the machine, the location shall be modelled as a MaterialStorageBuffer.

The MaterialLocationType representation in the AddressSpace is formally defined in the following table.

Table 145 – MaterialLocationType Definition
Attribute Value
BrowseNameMaterialLocationType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the BaseObjectType defined in OPC 10000-5 - Part 5: Information Model, i.e. inheriting the Instance Declarations of that Node.
0:HasPropertyVariableCanReceive0:Boolean0:PropertyTypeM, RO
0:HasPropertyVariableCanSend0:Boolean0:PropertyTypeM, RO
0:HasComponentObjectCarriers0:FolderTypeM
0:HasComponentVariableSublotsMaterialSublotType[]0:BaseDataVariableTypeM, RO
0:HasPropertyVariableID0:String0:PropertyTypeM, RO
0:HasPropertyVariableMES_ID0:String0:PropertyTypeM, RW
0:HasPropertyVariableStateStateEnumeration0:PropertyTypeO, RO
0:HasComponentObjectStateMachineTMCStateMachineTypeO
0:HasComponentObjectUIInfoUIInformationTypeO
0:GeneratesEventObjectTypeCarrierEnteredLogType
0:GeneratesEventObjectTypeCarrierReleasedLogType
0:GeneratesEventObjectTypeStateChangeLogType
Conformance Units
TMC Intralogistics at the machine
BrowseName Description
CanReceiveWhen True, material sublots or carriers can be stored in the material location. It is set by the underlying system to make the material location available for receiving.
CanSendWhen True, material sublots or carriers can be removed in the material location. It is set by the underlying system to make the material location available for sending.
CarriersThe Carriers folder provides carriers that are stored in the material location.
SublotsThe Sublots array of MaterialSublotType provides carriers that are stored in the material location.
IDThe unique identifier for the material location.
MES_IDThe unique identifier of the material location according to a higher-level system, e.g. MES or ERP.
StateThe state the material location is in.
StateMachineThe state machine describing the state and transitions of the material location.
UIInfoThe visualization resources to display the MaterialLocationType on the User Interface.
Table 146 – MaterialLocationType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
Carriers 0:HasComponentObject <Carrier> CarrierTypeOP

8.49 TMCDeviceType ObjectType

The TMCDeviceType ObjectType is used to include UIInfo and specify which DeviceType components are mandatory when used in compliance with TMC. The TMCDeviceType is abstract, meaning there will be no instances of the TMCDeviceType.

The TMCDeviceType representation in the AddressSpace is formally defined in the following table.

Table 147 – TMCDeviceType Definition
Attribute Value
BrowseNameTMCDeviceType
IsAbstractTrue
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the DeviceType defined in OPC 10000-100, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectUIInfoUIInformationTypeO
Conformance Units
TMC Advanced Visualisation and Control
BrowseName Description
UIInfoThe visualization resources to display the Device on the User Interface.

Instances of the TMCDeviceType and derived types are components of the DeviceSet Object as defined by OPC10000-100, 5.9 DeviceSet.

For additional clarity, TMCDeviceType instances and instances of derived types shall be grouped under the DeviceSet object.