1 Scope

This standard defines a communication interface for commercial kitchen equipment.

This standard specifies manufacturer-neutral communication systems and serves as a design basis for communication protocols in commercial kitchen equipment as well as devices in these networks.

This standard does not specify any safety requirements with regard to device technology and data access.

OPC Foundation

OPC is the interoperability standard for the secure and reliable exchange of data and information in the industrial automation space and in other industries. It is platform independent and ensures the seamless flow of information among devices from multiple vendors. The OPC Foundation is responsible for the development and maintenance of this standard.

OPC UA is a platform independent service-oriented architecture that integrates all the functionality of the individual OPC Classic specifications into one extensible framework. This multi-layered approach accomplishes the original design specification goals of:

Platform independence: from an embedded microcontroller to cloud-based infrastructure

Secure: encryption, authentication, authorization and auditing

Extensible: ability to add new features including transports without affecting existing applications

Comprehensive information modelling capabilities: for defining any model from simple to complex

HKI

Manufacturers of commercial kitchen equipment and domestic heating and cooking appliances are organized in HKI industrial association of House, Heating and Kitchen Technology. Both manufacturer groups are organized in separate associations which are subdivided into device-specific departments.

2 Normative references

The following referenced documents are indispensable for the application of this specification. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling and commercial kitchen devices are understood in this specification. This specification will use these concepts to describe the commercial kitchen devices information model. For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-7, OPC 10000-100 as well as the following apply.

Note that OPC UA terms and terms defined in this specification are italicized in the specification.

3.2 OPC UA for commercial kitchen devices terms

3.2.1 Communication interface

electronic interface for the exchange of data

3.2.2 Device

3.3 Abbreviations and symbols

3.4 Conventions used in this document

3.4.1 Conventions for Node descriptions

Node definitions are specified using tables (see Table 2).

Attributes are defined by providing the Attribute name and a value, or a description of the value.

References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass.

• If the TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table.

• The DataType is only specified for Variables; “[<number>]” indicates a single-dimensional array, for multi-dimensional arrays the expression is repeated for each dimension (e.g. [2][3] for a two-dimensional array). For all arrays the ArrayDimensions is set as identified by <number> values. If no <number> is set, the corresponding dimension is set to 0, indicating an unknown size. If no number is provided at all the ArrayDimensions can be omitted. If no brackets are provided, it identifies a scalar DataType and the ValueRank is set to the corresponding value. In addition, ArrayDimensions is set to null or is omitted. If it can be Any or ScalarOrOneDimension, the value is put into “{<value>}”, so either “{Any}” or “{ScalarOrOneDimension}” and the ValueRank is set to the corresponding value and the ArrayDimensions is set to null or is omitted. Examples are given in Table 1.

• The TypeDefinition is specified for Objects and Variables.

• The TypeDefinition column specifies a symbolic name for a NodeId, i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node.

• The ModellingRule of the referenced component is provided by specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace, the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object.

If the NodeId of a DataType is provided, the symbolic name of the Node representing the DataType shall be used.

Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType, their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition.

Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point to the Node definition.

In addition, the following abbreviations defined in Table 3 are used in the ModellingRule column in the tables for the definition of ObjectTypes.

As example for the use of the Modelling Rule Mandatory and AccessLevel Readable and Writable variables, the abbreviation is “M, RW”.

Components of Nodes can be complex that is containing components by themselves. The TypeDefinition, NodeClass, DataType and ModellingRule can be derived from the type definitions, and the symbolic name can be created as defined in 3.4.3.1. Therefore, those containing components are not explicitly specified; they are implicitly specified by the type definitions.

3.4.2 NodeIds and BrowseNames

3.4.2.1 NodeIds

The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.

The symbolic name of each Node defined in this specification is its BrowseName, or, when it is part of another Node, the BrowseName of the other Node, a “.”, and the BrowseName of itself. In this case “part of” means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique name in this specification, the symbolic name is unique.

The namespace for all NodeIds defined in this specification is defined in Annex A. The namespace for this NamespaceIndex is Server-specific and depends on the position of the namespace URI in the server namespace table.

Note that this specification not only defines concrete Nodes, but also requires that some Nodes shall be generated, for example one for each Session running on the Server. The NodeIds of those Nodes are Server-specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this specification, because they are not defined by this specification but generated by the Server.

3.4.2.2 BrowseNames

The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes. The NamespaceIndex for all BrowseNames defined in this specification is defined in Annex A.

If the BrowseName is not defined by this specification, a namespace index prefix like ‘0:EngineeringUnits’ or ‘2:DeviceRevision’ is added to the BrowseName. This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this specification. Table 75 provides a list of namespaces and their indexes as used in this specification.

3.4.3 Common Attributes

3.4.3.1 General

The Attributes of Nodes, their DataTypes and descriptions are defined in OPC 10000-3OPC 10000-3. Attributes not marked as optional are mandatory and shall be provided by a Server. The following tables define if the Attribute value is defined by this specification or if it is server-specific.

For all Nodes specified in this specification, the Attributes named in Table 4 shall be set as specified in the table.

3.4.3.2 Objects

For all Objects specified in this specification, the Attributes named in Table 5 shall be set as specified in the Table 5. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.3 Variables

For all Variables specified in this specification, the Attributes named in Table 6 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.4 VariableTypes

For all VariableTypes specified in this specification, the Attributes named in Table 7 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.5 Methods

For all Methods specified in this specification, the Attributes named in Table 8 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

4 Introduction to OPC Unified Architecture

4.1 What is OPC UA?

OPC UA is an open and royalty free set of standards designed as a universal communication protocol. While there are numerous communication solutions available, OPC UA has key advantages:

A state of art security model (see OPC 10000-2).

A fault tolerant communication protocol.

An information modelling framework that allows application developers to represent their data in a way that makes sense to them.

OPC UA has a broad scope which delivers for economies of scale for application developers. This means that a larger number of high quality applications at a reasonable cost are available. When combined with semantic models such as commercial kitchen devices, OPC UA makes it easier for end users to access data via generic commercial applications.

The OPC UA model is scalable from small devices to ERP systems. OPC UA Servers process information locally and then provide that data in a consistent format to any application requesting data - ERP, MES, PMS, Maintenance Systems, HMI, Smartphone or a standard Browser, for examples. For a more complete overview see OPC 10000-1.

4.2 Basics of OPC UA

As an open standard, OPC UA is based on standard internet technologies, like TCP/IP, HTTP, Web Sockets.

As an extensible standard, OPC UA provides a set of Services (see OPC 10000-4) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information in a standard way. More importantly all OPC UA Clients are expected to be able to discover and use vendor-defined information. This means OPC UA users can benefit from the economies of scale that come with generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users.

OPC UA Clients can be any consumer of data from another device on the network to browser based thin clients and ERP systems. The full scope of OPC UA applications is shown in Figure 1.

OPC UA provides a robust and reliable communication infrastructure having mechanisms for handling lost messages, failover, heartbeat, etc. With its binary encoded data, it offers a high-performing data exchange solution. Security is built into OPC UA as security requirements become more and more important especially since environments are connected to the office network or the internet and attackers are starting to focus on automation systems.

4.3 Information modelling in OPC UA

4.3.1 Concepts

OPC UA provides a framework that can be used to represent complex information as Objects in an AddressSpace which can be accessed with standard services. These Objects consist of Nodes connected by References. Different classes of Nodes convey different semantics. For example, a Variable Node represents a value that can be read or written. The Variable Node has an associated DataType that can define the actual value, such as a string, float, structure etc. It can also describe the Variable value as a variant. A Method Node represents a function that can be called. Every Node has a number of Attributes including a unique identifier called a NodeId and non-localized name called as BrowseName. An Object representing a ‘Reservation’ is shown in Figure 2.

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 3 illustrates the relationship between an instance and its TypeDefinition.

The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 3 the PersonType ObjectType defines two children: First Name and Last Name. All instances of PersonType are expected to have the same children with the same BrowseNames. Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed to search for children based on the BrowseNames from the type instead of NodeIds. This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers implement.

OPC UA also supports the concept of sub-typing. This allows a modeller to take an existing type and extend it. There are rules regarding sub-typing defined in OPC 10000-3, but in general they allow the extension of a given type or the restriction of a DataType. For example, the modeller may decide that the existing ObjectType in some cases needs an additional Variable. The modeller can create a subtype of the ObjectType and add the Variable. A Client that is expecting the parent type can treat the new type as if it was of the parent type. Regarding DataTypes, subtypes can only restrict. If a Variable is defined to have a numeric value, a sub type could restrict it to a float.

References allow Nodes to be connected in ways that describe their relationships. All References have a ReferenceType that specifies the semantics of the relationship. References can be hierarchical or non-hierarchical. Hierarchical references are used to create the structure of Objects and Variables. Non-hierarchical are used to create arbitrary associations. Applications can define their own ReferenceType by creating subtypes of an existing ReferenceType. Subtypes inherit the semantics of the parent but may add additional restrictions. Figure 4 depicts several References, connecting different Objects.

The figures above use a notation that was developed for the OPC UA specification. The notation is summarized in Figure 5. UML representations can also be used; however, the OPC UA notation is less ambiguous because there is a direct mapping from the elements in the figures to Nodes in the AddressSpace of an OPC UA Server.

A complete description of the different types of Nodes and References can be found in OPC 10000-3 and the base structure is described in OPC 10000-5.

OPC UA specification defines a very wide range of functionality in its basic information model. It is not expected that all Clients or Servers support all functionality in the OPC UA specifications. OPC UA includes the concept of Profiles, which segment the functionality into testable certifiable units. This allows the definition of functional subsets (that are expected to be implemented) within a companion specification. The Profiles do not restrict functionality, but generate requirements for a minimum set of functionality (see OPC 10000-7)

4.3.2 Namespaces

OPC UA allows information from many different sources to be combined into a single coherent AddressSpace. Namespaces are used to make this possible by eliminating naming and id conflicts between information from different sources. Namespaces in OPC UA have a globally unique string called a NamespaceUri and a locally unique integer called a NamespaceIndex. The NamespaceIndex is only unique within the context of a Session between an OPC UA Client and an OPC UA Server. The Services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values.

There are two types of values in OPC UA that are qualified with Namespaces: NodeIds and QualifiedNames. NodeIds are globally unique identifiers for Nodes. This means the same Node with the same NodeId can appear in many Servers. This, in turn, means Clients can have built in knowledge of some Nodes. OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model.

QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames; however, instances do not have that restriction.

4.3.3 Companion Specifications

An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes, VariableTypes, DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects as entry points into the AddressSpace.

5 General type definitions for commercial kitchen devices

5.1 Definitions for the properties of the DeviceType

Figure 6 shows an overview of the DeviceType with its Properties.

5.1.1 General

The general DeviceType from the OPC UA information model for the device configuration is taken as the basis in this specification. This information model is defined in IEC62541-100:2015.

All sub types derived from CommercialKitchenDevice can be supplemented by vendor-specific types.

5.1.2 DeviceClass property

The DeviceType defines the DeviceClass property. The classification is industry-specific and is defined for commercial kitchen devices in Table 9.

5.1.3 Manufacturer property

The manufacturer of the device is provided as freely definable text in the Manufacturer property.

5.1.4 Model property

The device designation is provided as freely definable text in the Model property.

5.1.5 SerialNumber property

The identification number, e.g. the serial number of the device, is provided as freely definable text in the SerialNumber property.

5.1.6 HardwareRevision property

The hardware version of the device is provided as freely definable text in the HardwareRevision property.

5.1.7 SoftwareRevision property

The software version of the device is provided as freely definable text in the SoftwareRevision property.

5.1.8 DeviceHealth property

The status of the device is provided as DeviceHealth enumeration in the DeviceHealth property. The possible values are NORMAL_0, FAILURE_1, CHECK_FUNCTION_2, OFF_SPEC_3 and MAINTENANCE_REQUIRED_4.

5.2 CommercialKitchenDeviceType

5.2.1 General

The CommercialKitchenDeviceType represents the basic type for all device classes according to Table 9. It is derived from the general DeviceType from the OPC UA information model for the device configuration. This information model is defined in IEC 62541-100:2015.

Figure 7 shows an overview of the CommercialKitchenDeviceType with its properties and associated Objects. The type is formally defined in Table 10.

5.2.2 Object type definition

The CommercialKitchenDeviceType is formally defined in Table 10.

5.2.3 Object type description

5.2.3.1 DeviceClass Property

The property DeviceClass of the DeviceType is overwritten in order to change the ModellingRule to Mandatory. The DeviceClass Strings used for this specification are defined in Table 9.

5.2.3.2 DeviceLocationName Property

The DeviceLocationName property represents a user-defined designation of the machine location.

Using this property the user can assign a name to the location, e.g. a room number.

5.2.3.3 BatchInformation Object

The BatchInformation object contains information on batch and article tracking. The BatchInformationType is defined in section 5.3.

5.2.3.4 ErrorConditions Object

The ErrorConditions object contains a list of currently pending error messages.

The basis for the processing of error messages is the Alarm and Condition Model from OPC UA, which is defined in IEC 62541-9:2015.

An error message is represented by an object of the type AlarmConditionType or by a type derived from it.

The AlarmConditionType and its base types define various states such as EnabledState, AckedState or ActiveState and further properties such as Severity, Message, Time and SourceNode. The Retain Property indicates whether an error message is of interest to the client.

Changes to the status of an error message are supplied to the clients via Events. A client can request the current status for all error messages where Retain = true as an event via the ConditionRefresh method. Clients can thus request a list of pending error messages after establishment of a connection.

Clients can confirm error messages via Methods in order, for example, to change the AckedState of the error message.

5.2.3.5 InformationConditions Object

The InformationConditions object contains a list of currently pending information messages.

The basis for the processing of information messages is the Alarm and Condition Model from OPC UA, which is defined in IEC 62541-0:2015.

An item of information is represented by an object of the type AlarmConditionType or by a type derived from it.

5.2.3.6 HACCPValues object

The HACCPValues object contains a list of HACCP-relevant measured values.

If a device provides HACCP-relevant measured values, these measured values must be referenced via the FunctionalGroup HACCPValues.

For HACCP-relevant measured values the corresponding variable must reference an information object of the type KitchenDeviceHAConfigType with the name "HA Configuration". The KitchenDeviceHAConfigType and its use are defined in section 5.4.

5.3 BatchInformationType

5.3.1 General

The BatchInformationType defines the data for the tracking of batches and articles.

Figure 8 shows an overview of the BatchInformationType with its Properties. The type is formally defined in Table 11.

5.3.2 Object type definition

The BatchInformationType is formally defined in Table 11.

5.3.3 ObjectType description

5.3.3.1 OrderId property

The OrderId Property represents the machine user's order number for the traceability.

5.3.3.2 BatchId property

The BatchId Property represents the machine user's batch number for the traceability.

5.3.3.3 SystemTime property

The SystemTime Property represents the current system time as a coordinated world time in UTC format.

5.3.3.3.1 LocalTime property

The LocalTime property represents the current difference between the local time and the UTC time. The data type TimeZoneDataType is defined in OPC 10000-5.

5.4 KitchenDeviceHAConfigType

5.4.1 General

The KitchenDeviceHAConfigType configures the logging of HACCP-relevant data.

Figure 9 shows an overview of the KitchenDeviceHAConfigType with its Properties. The type is formally defined in Table 12.

In the case of variables for which HACCP-relevant measured values are logged on the device, the corresponding variable must offer the settings relevant for the logging via an object with the name "HA Configuration". The BrowseName must have the Namespace Index 0. The KitchenDeviceHAConfigType or a type derived from it is used as the type for this Object.

5.4.2 Object type definition

The KitchenDeviceHAConfigType is formally defined in Table 12.

5.4.3 ObjectType description

5.4.3.1 HistoryDuration property

The HistoryDuration Property represents the logging time in milliseconds for which data are stored in the device.

5.4.3.2 SamplingInterval property

The SamplingInterval Property represents the sampling rate for the logging in milliseconds.

5.5 KitchenDeviceParameterType

5.5.1 Object type definition

The KitchenDeviceParameterType is formally defined in Table 13. It represents the abstract base type for the device-specific parameter object types.

5.5.2 ObjectType description

5.5.2.1 ProgramId variable

The ProgramId Variable with the data type Int32 represents the program number of the currently selected program.

5.5.2.2 ProgramName variable

The ProgramName Variable with the data type LocalizedText represents the program name of the currently selected program. If no names are available, the program number can also be used as text.

5.5.2.3 ProgramUId variable

The ProgramUId Variable with the data type Guid represents the globally unique identifier of the currently selected program.

6 Type definitions for Fryer

6.1 General

The fryer is used to fry various cooked foods, such as French fries and others. A system may consist of one or more fryer vats. Each fryer vat can be operated individually.

If the device is equipped with a lift, the frying basket of each vat can be automatically lowered and raised again after an adjustable cooking time.

Figure 10 shows an overview of the object types for the Fryer device class.

6.2 FryerParameterType

6.2.1 General

FryerParameterType provides information about the state, the set values and the current actual values of a frying vat.

6.2.2 Definition of the object type

The FryerParameterType is formally defined in Table 14.

6.2.3 Description of the object type

6.2.3.1 ProgramMode variable

This variable describes the state of the device, e.g. heating up or frying.

The data type for the FryerModeEnumeration is defined in 6.4.1.

6.2.3.2 SetTemperature variable

This variable contains the set temperature to which the frying fat is to be heated.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

6.2.3.3 ActualTemperature variable

This variable describes the currently measured frying temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

6.2.3.4 SetProcessTime variable

This variable describes the set cooking time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

6.2.3.5 TimeRemaining variable

This variable describes the remaining frying time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

6.2.3.6 SignalMode variable

This variable describes the state of the signal output. In addition to the on and off states, the "Signal was acknowledged" state is also saved.

The data type for the SignalModeEnumeration is defined in 6.4.2.

6.2.3.7 IsLiftUp variable

This variable describes whether the frying basket is raised.

6.3 FryerDeviceType

6.3.1 General

A fryer may consist of one or more frying vats. Each fryer vat can be operated individually. The device can be equipped with a lift for the frying basket for each existing frying vat.

6.3.2 Definition of the object type

The FryerDeviceType is formally defined in Table 15.

6.3.3 Descripiton of the object type

6.3.3.1 IsWithLift property

This property describes whether the device has an automatic lift for raising and lowering the frying basket.

6.3.3.2 EnergySource property

The EnergySource property returns the type of energy supply. The data type for the EnergySourceEnumeration is defined in 21.1.

6.3.3.3 FryerCup_<No.> objects

A fryer may consist of one or more frying vats. The FryerCup_<No.> object contains the data of a frying vat.

6.4 Data types for enumerations

6.4.1 FryerModeEnumeration

The data type is an enumeration of the current status of the fryer.

The enumeration values are defined in Table 16.

6.4.2 SignalModeEnumeration

This data type is an enumeration of the signal state.

The enumeration values are defined in Table 17.

7 Type definitions for Frying Pan

7.1 General

The term "frying pan" includes the following device types

• tilting frying pan;

  braising pan

  pressure braising pan.

Figure 11 shows an overview of the object types for the Frying Pan device class.

7.2 FryingPanParameterType

7.2.1 General

FryingPanParameterType provides information about the state of the device, the set values and the current actual values.

7.2.2 Definition of the object type

The FryingPanParameterType is formally defined in Table 18.

7.2.3 Description of the object type

7.2.3.1 ProgramMode variable

This variable describes the state of the device, e.g. heating up or frying.

The data type for the FryingPanModeEnumeration is defined in section 7.4.1.

7.2.3.2 CookingLevel variable

This variable describes the cooking level with which heating up is to take place.

The value is used only in the Cook and CookSlow ProgramMode.

7.2.3.3 SetTemperature variable

This variable contains the set temperature to which heating up is to take place. With pressure cooking the set pressure is calculated on the basis of the set temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

7.2.3.4 ActualTemperatur variable

This variable describes the currently measured temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

7.2.3.5 SetProcessTime variable

This variable describes the set process time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

7.2.3.6 TimeRemaining variable

This variable describes the remaining process time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

7.2.3.7 SetCoreTemperature variable

This variable describes the set core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

7.2.3.8 ActualCoreTemperature variable

This variable describes the currently measured core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

7.2.3.9 SignalMode variable

This variable describes the state of the signal output. In addition to the on and off states, the "Signal was acknowledged" state is also saved.

The data type for the SignalModeEnumeration is defined in 7.4.2.

7.2.3.10 ActualPressurePan variable

This variable describes the currently measured pressure in the pan.

The EngineeringUnit property of the AnalogItemType has the value mbar. The value for the EURange property is device-specific.

7.2.3.11 IsLidLocked variable

This variable describes whether the lid is locked.

7.3 FryingPanDeviceType

7.3.1 General

FryingPanDeviceType describes a device from the FryingPan device class. The following device types belong to this device class:

7.3.2 Definition of the object type

The FryingPanDeviceType is formally defined in Table 19.

7.3.3 Description of the object type

7.3.3.1 IsWithPressure property

This property describes whether the device has the equipment for pressure cooking.

7.3.3.2 EnergySource property

The Energy property returns the type of energy supply. The data type for the EnergySourceEnumeration is defined in 21.1.

7.3.3.3 Object FryingPan

The FryingPan object contains the parameters for a device of the type FryingPan.

7.4 Data types for enumerations

7.4.1 FryingPanModeEnumeration

The data type is an enumeration of the possible status values of the device.

The enumeration values are defined in Table 20.

7.4.2 SignalModeEnumeration

This data type is an enumeration of the signal state.

The enumeration values are defined in Table 21.

8 Type definitions for Combi Steamer

8.1 General

Various methods of cooking are possible with a combi steamer; these include:

In addition, further vendor-specific types of cooking and actions are possible in a cooking process:

A cooking program may consist of one or more cooking steps. Each cooking step may consist of a cooking method or one of the other actions.

Figure 12 shows an overview of the object types for the Combi Steamer device class.

8.2 CombiSteamerParameterType

8.2.1 General

CombiSteamerParameterType provides information about the state of a combi steamer, the set values and the current actual values.

8.2.2 Definition of the object type

The CombiSteamerParameterType is formally defined in Table 22.

8.2.3 Description of the object type

8.2.3.1 CombiSteamerMode variable

This variable describes the state of the device, e.g. preheating, active, cleaning, etc. The data type for the CombiSteamerModeEnumeration is defined in section 8.4.1.

8.2.3.2 SetTemperature variable

This variable contains the set temperature to which heating up is to take place and be regulated.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

8.2.3.3 ActualTemperatureChamber_<No.> variable

The numbered variable ActualTemperaturChamber_<No.> contains the current temperature of a cooking chamber. This variable may be used several times (numbered consecutively), depending on the number of cooking chambers that exist.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

8.2.3.4 SetProcessTimeProgram variable

This variable describes the set process time of the entire cooking program in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

8.2.3.5 TimeRemainingProgram variable

This variable describes the remaining process time of the entire cooking program in seconds, i.e. of the current and all subsequent cooking steps.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

8.2.3.6 SetInternalCoreTemperature variable

This variable describes the set core temperature for the internal core temperature sensor.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

8.2.3.7 ActualInternalCoreTemperature_<No.> variable

The numbered variable ActualInternalCoreTemperature_<No.> contains the current temperature of an internal core temperature sensor. This variable may be used several times (numbered consecutively), depending on the number of internal core temperature sensors that exist.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

8.2.3.8 SetExternalCoreTemperature variable

This variable describes the set core temperature for the external core temperature sensor, if the sensor exists.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

8.2.3.9 ActualExternalCoreTemperature_<No.> variable

The numbered variable ActualExternalCoreTemperatur_<No.> contains the current temperature of an external core temperature sensor. This variable may be used several times (numbered consecutively), depending on the number of external core temperature sensors that exist.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

8.2.3.10 SpecialCookingMode variable

This variable describes additional cooking methods that do not belong to the standard scope of a combi steamer.

The data type for the SpecialCookingModeEnumeration is defined in 8.4.2.

8.2.3.11 SetProcessTimeStep variable

This variable describes the set process time of the current cooking step in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

8.2.3.12 TimeRemainingStep variable

This variable describes the remaining process time of the current cooking step in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

8.2.3.13 SetHumidity variable

This variable describes the set humidity in percent.

The EngineeringUnit property of the AnalogItemType has the value %. The value for the EURange property is device-specific.

8.2.3.14 ActualHumidity variable

This variable describes the actual humidity in percent.

The EngineeringUnit property of the AnalogItemType has the value %. The value for the EURange property is device-specific.

8.2.3.15 IsDoorOpen variable

This variable describes whether the door is open.

8.2.3.16 IsEnergySavingActive variable

This variable describes whether the energy saving mode is active. The heating power is reduced in this mode.

8.2.3.17 IsSteamExhaustSystemActive variable

This variable describes whether the steam extraction is active.

8.2.3.18 IsLoaActive variable

This variable describes whether the device, when connected to a power optimisation system (LOA), has received the release for heating. The value applies only to those devices that are equipped with a LOA connection and are connected.

8.3 CombiSteamerDeviceType

8.3.1 General

CombiSteamerDeviceType describes a device from the CombiSteamer device class.

8.3.2 Definition of the object type

The CombiSteamerDeviceType is formally defined in Table 23.

8.3.3 Description of the object type

8.3.3.1 EnergySource property

The EnergySource property returns the type of energy supply. The data type for the EnergySourceEnumeration is defined in 21.1.

8.3.3.2 IsWithAutomaticCleaning property

This property describes whether the device is equipped with automatic cleaning.

8.3.3.3 IsWithInternalCoreTempSensor property

This property describes whether the device is equipped with an internal core temperature sensor.

8.3.3.4 IsWithExternalCoreTempSensor property

This property describes whether the device is equipped with an external core temperature sensor.

8.3.3.5 IsWithSousvideTempSensor property

This property describes whether the device is equipped with a sous-vide temperature sensor.

8.3.3.6 Object CombiSteamer

The CombiSteamer object contains the parameters for a device of the type CombiSteamer.

8.4 Data types for enumerations

8.4.1 CombiSteamerModeEnumeration

The data type is an enumeration of the current status of the device.

The enumeration values are defined in Table 24.

8.4.2 SpecialCookingModeEnumeration

This data type is an enumeration of the various special cooking modes.

The enumeration values are defined in Table 25.

9 Type definitions for Convection Oven, Multiple Deck Oven

9.1 General

Figure 13 shows an overview of the object types for the Convection Oven, Multiple Deck Oven device class.

9.2 ChamberType

9.2.1 Definition of the object type

The ChamberType is formally defined in Table 26.

9.2.2 Description of the object type

9.2.2.1 OperationMode variable

The OperationMode variable with the data type ChamberModeEnumeration represents the current operation mode of the chamber.

The data type for the ChamberModeEnumeration is defined in section 9.4.1.

9.2.2.2 TimeRemaining variable

The TimeRemaining variable with the data type Int32 represents the remaining running time of the current process (baking, cooling, cleaning, etc.). 0 is returned if no process running time is intended.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

9.2.2.3 SetChamberTemperature variable

This variable represents the set value for the chamber temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.4 SetTopTemperature variable

This variable represents the set value for the top chamber temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.5 SetBottomTemperature variable

This variable represents the set value for the bottom chamber temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.6 SetCoreTemperature variable

This variable represents the set value for the core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.7 SetBoilerTemperature variable

This variable represents the set value for the temperature of the steam generator.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.8 ActualChamberTemperature_<No.> variable

This variable represents the actual value of the chamber temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.9 SetProcessTimeProgram variable

This variable represents the actual value of the process program time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

9.2.2.10 ActualTopTemperature_<No.> variable

This variable represents the actual value of the top chamber temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.11 ActualBottomTemperature_<No.> variable

This variable represents the actual value of the bottom chamber temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.12 ActualCoreTemperature_<No.> variable

This variable represents the actual value of the core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.13 ActualBoilerTemperature_<No.> variable

This variable represents the actual value of the temperature of the steam generator.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

9.2.2.14 SetHumidity variable

This variable represents the set humidity in the chamber.

The EngineeringUnit property of the AnalogItemType has the value rel%. The value for the EURange property is device-specific.

9.2.2.15 ActualHumidity_<No.> variable

This variable represents the actual humidity in the chamber.

The EngineeringUnit property of the AnalogItemType has the value rel%. The value for the EURange property is device-specific.

9.2.2.16 IsReadyToStart variable

This variable is set when all conditions for a program start are satisfied. (Boolean).

9.2.2.17 IsProgramEnd variable

This variable is set when the program has completely finished. (Boolean).

9.2.2.18 IsDoorOpen variable

This variable is set when the chamber door is open. (Boolean).

9.2.2.19 ActualFanSpeed_<No.> variable

This variable represents the current fan speed in percent.

9.2.2.20 SetFanSpeed variable

This variable represents the set fan speed in percent.

9.3 OvenDeviceType

9.3.1 Definition of the object type

The OvenDeviceType is formally defined in Table 27.

9.3.2 Description of the object type

9.3.2.1 Chamber_<No.> objects

List of chambers. At least one baking chamber exists. Optionally, further baking chambers (e.g. stoves in the case of multiple deck ovens) may exist. The ChamberType is defined in section 9.2.

Baking chambers are numbered consecutively from bottom to top or from left to right.

9.4 Data types for enumerations

9.4.1 ChamberModeEnumeration

This data type is an enumeration of the signal state.

The enumeration values are defined in Table 28.

10 Type definitions for Pressure Cooking Kettle

10.1 General

Figure 14 shows an overview of the object types for the Pressure Cooking Kettle device class.

10.2 PressureCookingKettleParameterType

10.2.1 General

Various cooking processes are possible with a pressure cooking kettle; these include:

In addition, an agitator can be used.

PressureCookingKettleParameterType provides information about the state of the device, the set values and the current actual values.

10.2.2 Definition of the object type

The PressureCookingKettleParameterType is formally defined in Table 29.

10.2.3 Description of the object type

10.2.3.1 ProgramMode variable

This variable describes the state of the device, e.g. heating up, frying.

The data type for the PressureCookingKettleModeEnumeration is defined in section 10.4.1.

10.2.3.2 CookingLevel variable

This variable describes the cooking level with which heating up is to take place. The value is used only in the Cook and CookSlow ProgramMode.

10.2.3.3 SetTemperature variable

This variable contains the set temperature to which heating up is to take place.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

10.2.3.4 ActualTemperature variable

This variable describes the currently measured temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

10.2.3.5 SetProcessTime variable

This variable describes the set process time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

10.2.3.6 TimeRemaining variable

This variable describes the remaining process time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

10.2.3.7 SetCoreTemperature variable

This variable describes the set core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

10.2.3.8 ActualCoreTemperature variable

This variable describes the currently measured core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

10.2.3.9 ActualPressureAbsolute variable

This variable describes the current absolute pressure in the cooking chamber.

The EngineeringUnit property of the AnalogItemType has the value mbar. The value for the EURange property is device-specific.

10.2.3.10 ActualPressureKettle variable

This variable describes the current absolute pressure in the steam chamber.

The EngineeringUnit property of the AnalogItemType has the value mbar. The value for the EURange property is device-specific.

10.2.3.11 SignalMode variable

This variable describes the state of the signal output. In addition to the on and off states, the "Signal was acknowledged" state is also saved.

The data type for the SignalModeEnumeration is defined in 10.4.2.

10.2.3.12 IsLidLocked variable

This variable describes whether the lid is locked.

10.2.3.13 IsSteamActive variable

This variable describes whether the use of low-pressure steam is active.

10.2.3.14 IsOpenExpressActive variable

This variable describes whether the express pressure relief is active.

10.3 PressureCookingKettleDeviceType

10.3.1 General

PressureCookingKettleDeviceType describes a device from the PressureCookingKettle device class.

10.3.2 Definition of the object type

The PressureCookingKettleDeviceType is formally defined in Table 30.

10.3.3 Description of the object type

10.3.3.1 EnergySource property

The EnergySource property returns the type of energy supply. The data type for the EnergySourceEnumeration is defined in 21.1.

10.3.3.2 Object PressureCookingKettle

The PressureCookingKettle object contains the parameters for a device of the type PressureCookingKettle.

10.4 Data types for enumerations

10.4.1 PressureCookingKettleModeEnumeration

The data type is an enumeration of the current status of the device.

The enumeration values are defined in Table 31.

10.4.2 SignalModeEnumeration

This data type is an enumeration of the signal state.

The enumeration values are defined in Table 32.

11 Type definitions for Cooking Kettle

11.1 General

Figure 15 shows an overview of the object types for the Cooking Kettle device class.

11.2 CookingKettleParameterType

11.2.1 General

Various cooking processes are possible with a cooking kettle; these include:

In addition, an agitator can be used.

CookingKettleParameterType provides information about the state of the device, the set values and the current actual values.

11.2.2 Definition of the object type

The CookingKettleParameterType is formally defined in Table 33.

11.2.3 Description of the object type

11.2.3.1 ProgramMode variable

This variable describes the state of the device, e.g. heating up, frying.

The data type for the CookingKettleModeEnumeration is defined in section 11.4.1.

11.2.3.2 CookingLevel variable

This variable describes the cooking level with which heating up is to take place. The value is used only in the Cook and CookSlow ProgramMode.

11.2.3.3 SetTemperatur variable

This variable contains the set temperature to which heating up is to take place.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

11.2.3.4 ActualTemperature variable

This variable describes the currently measured temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

11.2.3.5 SetProcessTime variable

This variable describes the set process time in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

11.2.3.6 RemainingTime variable

This variable describes the remaining process time for cooking in seconds.

The EngineeringUnit property of the AnalogItemType has the value s. The value for the EURange property is device-specific.

11.2.3.7 SetCoreTemperature variable

This variable describes the set core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

11.2.3.8 ActualCoreTemperature variable

This variable describes the currently measured core temperature.

The EngineeringUnit property of the AnalogItemType has the value °C. The value for the EURange property is device-specific.

11.2.3.9 SignalMode variable

This variable describes the state of the signal output. In addition to the on and off states, the "Signal was acknowledged" state is also saved.

The data type for the SignalModeEnumeration is defined in 11.4.2.

11.3 CookingKettleDeviceType

11.3.1 General

CookingKettleDeviceType describes a device from the Cooking Kettle device class.

11.3.2 Definition of the object type

The CookingKettleDeviceType is formally defined in Table 34.

11.3.3 Description of the object type

11.3.3.1 IsWithAgitator property

This property describes whether the device is equipped with an agitator.

11.3.3.2 IsWithCooling property

This property describes whether the device is equipped with a cooling function.

11.3.3.3 EnergySource property

The Energy property returns the type of energy supply. The data type for the EnergySourceEnumeration is defined in 21.1.

11.3.3.4 Object CookingKettle

The CookingKettle object contains the parameters for a device of the type Cooking Kettle.

11.4 Data types for enumerations

11.4.1 CookingKettleModeEnumeration

The data type is an enumeration of the current status of the device.

The enumeration values are defined in Table 35.

11.4.2 SignalModeEnumeration

This data type is an enumeration of the signal state.

The enumeration values are defined in Table 36.

12 Type definitions for Multi Function Pan

12.1 General

Various cooking processes are possible with a multi function pan; these include:

In addition, further manufacturer-specific types of cooking and actions are possible in a cooking process:

A multi function pan may consist of one or two pots. Each pot is independently operable. There are various pot sizes and depths.

Figure 16 shows an overview of the object types for the Multi Function Pan device class.

12.2 MultiFunctionPanParameterType

12.2.1 General

MultiFunctionPanParameterType provides information about the state of a pot, the set values and the current actual values.

12.2.2 Definition of the object type