16 Monitoring

16.1 Overview

This building block provides a base structure for monitoring information of a MachineryItem. In Figure 24, the MonitoringType is shown. It provides some sub-structures for grouping different monitoring information. Vendors or companion specifications may add additional sub-structures on the different levels of this building block. The Status Object shall reference the MachineryItemState and MachineryOperationMode AddIns, if they are provided by the MachineryItem. The Health of the MachineryItem may be represented by the 2:IDeviceHealthType Interface defined in OPC 10000-100.

Figure 24 – MonitoringType

The building block can be used in parallel to other structures of the MachineryItem or as the main structure of the MachineryItem. In Figure 25 three different examples are shown. X:Machine1 only reference the Monitoring Object under MachineryBuildingBlocks, X:Machine2 has some additional structuring referencing the Monitoring Object in addition, and X:Machine3 references the Monitoring Object also directly to provide it as additional top-level entry point. It is recommended to provide this top-level entry point.

Figure 25 – Usage as Monitoring Entry Point

When the building block is used in combination with the MachineryItemState (see section 12) or MachineryOperationMode (see section 13), they should be combined as shown in Figure 26. The MachineryItemState and MachineryOperationMode should be referenced as building block from the MachineryBuildingBlocks Object, and in addition, from the Status Object of the Monitoring building block.

Figure 26 – Combination of MachineryItemState, MachineryOperationMode and Monitoring

In B.4, some more detailed examples are given on how to use this building block.

16.2 MonitoringType

The MonitoringType provides entry points for monitoring a MachineryItem and is formally defined in Table 40.

Table 40 – MonitoringType Definition
Attribute Value
BrowseNameMonitoringType
IsAbstractFalse
DescriptionEntry point for monitoring information of a MachineryItem.
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the 0:FolderType
0:HasPropertyVariable0:DefaultInstanceBrowseName0:QualifiedName0:PropertyType-
HasComponentObjectStatusFolderTypeO
HasComponentObjectHealthFolderTypeO
HasComponentObjectProcessFolderTypeO
HasComponentObjectConsumptionFolderTypeO
Conformance Units
Machinery Monitoring

The child Nodes of the MonitoringType have additional Attribute values defined in Table 41.

Table 41 – MonitoringType Attribute values for child Nodes
BrowsePath Value Attribute Description Attribute
0:DefaultInstanceBrowseNameMonitoringThe default BrowseName for instances of the type.
Status-Entry point for status information of the MachineryItem. If this Object is provided, and the MachineryItemState is provided, it shall be referenced. If this Object is provided and the MachineryOperationMode is provided, it shall be referenced.
Health-Entry point of health information of the MachineryItem.
Process-Entry point for process information of the MachineryItem.
ConsumptionEntry point for consumption information of the MachineryItem.

The components of the MonitoringType have additional subcomponents which are defined in Table 42.

Table 42 – MonitoringType Additional Subcomponents
Source Path Reference Node Class BrowseName DataType TypeDefinition Others
Status0:HasComponentObjectMachineryItemStateMachineryItemState_StateMachineTypeO
Status0:HasComponentObjectMachineryOperationModeMachineryOperationModeStateMachineTypeO
Status0:HasComponentObjectStacklight3:BasicStacklightTypeO
Health0:HasComponentObject2:DeviceHealthAlarms0:FolderTypeO
Health0:HasComponentVariable2:DeviceHealth2:DeviceHealthEnumeration0:BaseDataVariableTypeO

The components of the MonitoringType have additional References which are defined in Table 43.

Table 43 – MonitoringType Additional References
SourceBrowsePath Reference Type Is Forward TargetBrowsePath
Health0:HasInterfaceTrue2:IDeviceHealthType