umati showcase specification


This provides the specification to connect to the umati showcase

View the Project on GitHub umati/Showcase

umati showcase information model for Plastics and Rubber machines OPC 40082-2

1. General

The namespace for the instances is manufacturer specific, e.g.

Table 2 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the HRD_InterfaceType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are markes in bold.

Important: In OPC 40082-2 it is defined, that the instance of the HRD_InterfaceType is located under the Object DeviceSet. For umati it is necessary to add it under the Machines folder defined by OPC UA for machinery. In practice it is not necessary to create a new instance. It is sufficient to have an Organizes Reference from the Machines folder to the instance located under DeviceSet

OPC 40082-2 Overview

In addition, OPC 40082-2 uses the MachineInformationType defined in OPC 40083. For participation in the umati demonstrator it is necessary to create in parallel an instance of the MachineIdentificationType defined in OPC UA for Machinery.

Download: Compleate documentation umati showcase information model Plastics and Rubber

Table 1 – Namespaces used in this document

NamespaceURI Namespace Index Example 0 0:NodeVersion 1 Default namespace of OPC 40082-2 –> no prefix used, e.g. HRD_InterfaceType 2 2:DeviceClass 3 3:MachineInformationType 4 4:MachineIdentificationType

Table 2 – Sample instance of HRD_InterfaceType

BrowseName Type Example Value Remarks
   HRD_<Manufacturer>_<SerialNumber> HRD_InterfaceType    
    2:Identification 4:MachineIdentificationType   1)
     2:ProductInstanceUri 2)
     2:Manufacturer 0:LocalizedText “Sample Manufacturer”  
     2:Model 0:LocalizedText “HRD 3000” 3)
     2:SerialNumber 0:String “1234”  
     2:DeviceClass 0:String “Hot Runner Device”  
     4:Location 0:String “K 14 F42/N 51.260407 E 6.744588” 3), 4)
    Identification 3:IdentificationType   2)
     2:DeviceClass 0:String “Hot Runner Device” 2)
     2:Manufacturer 0:LocalizedText “Sample Manufacturer” 2)
     2:Model 0:LocalizedText “HRD 3000” 2)
     2:SerialNumber 0:String “1234” 2)
    MachineConfiguration 3:MachineConfigurationType   2)
     3:UserMachineName 0:String “My HRD” 2)
     3:LocationName 0:String “K 14 F42/N 51.260407 E 6.744588” 2)
     3:TimeZoneOffset 0:TimeZoneDataType <p>offset: 0</p><p>daylightSavingInOffset: true</p> 2)
    Operation OperationType    
     ActiveErrors 3:ClassifiedActiveErrorDataType empty array / NULL 2)
     ActiveSetValues 0:MultiStateValueDiscreteType 0 2)
     DeviceMappingNumber 0:UInt32 1 2)
     EnablePower 0:Boolean true  
     HighestAlarmSeverity 0:UInt16 0 2)
     ReactionOnDisconnect 0:MultiStateValueDiscreteType 0 2)
0:String “MySession” 2)
    Zones ZonesType    
     0:NodeVersion 0:String “1” 2)
     Zone_1 ZoneType    
      Name 0:String “Zone 1” 3)
      HighestAlarmSeverity 0:UInt16 0 2)
      Controller ControllerType   2)
       ActualType ControllerTypeEnumeration 0 (= CLOSED_LOOP_CONTROL) 2)
       ActualValueActive 0:Boolean true 2)
       SetValueActive 0:Boolean true 2)
       SetValueType 0:MultiStateValueDiscreteType 0 2)
      Temperature 3:ControlledParameterType    
     ActiveSetValue 0:MultiStateValueDiscreteType 0 2)
     ActualValue 0:AnalogItemType à 0:Double 168.4  
        EURange 0:Range <p>Low: 0</p><p>High: 200</p>  
        EngineeringUnits 0:EUInformation <p>namespaceUri: “”</p><p>unitId: 4408652</p><p>displayName: “°C”</p><p>description: “degree Celsius”</p>  

1) Not included in OPC 40084-2 HRD_InterfaceType. To be added in the instance 2) This variable is mandatory in the model but will not be displayed in the demonstrator 3) Not mandatory in NodeSet but for this model and will be displayed in the demonstrator 4) See for rules for filling the location.