Configuring operation of an HVAC actuator with an HVAC flow control device

Abstract

A method of configuring operation of an HVAC actuator (10) with an HVAC flow control device (50), the method comprising: retrieving, by a control unit (12) of the HVAC actuator (10), a machine-readable control device semantic model CDM descriptive of the HVAC flow control device (50); and configuring, by the control unit (12), the HVAC actuator (10) to operate the HVAC flow control device (50) by applying the control device semantic model CDM descriptive of the HVAC flow control device (50) using a domain ontology DO defining entities and relationships of the control device semantic model CDM.

Description

[0001] P28924PC00 December 2025

[0002] 1 / 44

[0003] CONFIGURING OPERATION OF AN HVAC ACTUATOR WITH AN HVAC FLOW CONTROL DEVICE

[0004] TECHNICAL FIELD

[0005] The present invention relates to a method of configuring operation of an HVAC actuator with an HVAC flow control device. The present invention further relates to an HVAC actuator configured to carry out the method of configuring its operation in accordance with an HVAC flow control device. The present invention further relates to an HVAC system and a computer program product for configuring operation of an HVAC actuator with an HVAC flow control device.

[0006] BACKGROUND OF THE INVENTION

[0007] Heating, Ventilation, and Air Conditioning (HVAC) systems are widely used to regulate indoor air quality, temperature, and comfort in residential, commercial, and industrial settings. These systems rely on the interaction of components for example actuators and flow control devices to regulate fluid (liquid or gas) flow according to specific operational requirements. Proper configuration of HVAC actuators to operate flow control devices for example dampers and valves, is necessary to achieve performance, energy efficiency, and reliability.

[0008] Configuring HVAC actuators with flow control devices has been a manual and labor- intensive process. This approach often relies on predefined configurations that may not adapt well to different operational conditions or system requirements. As HVAC systems grow in complexity, there is a greater need for flexible and accurate methods of ensuring that actuators and flow control devices function together as intended. The manual nature P28924PC00 December 2025

[0009] 2 / 44 of existing configuration processes increases the risk of errors and limits scalability in modern systems with diverse and evolving needs.

[0010] SUMMARY OF THE INVENTION

[0011] The objective of the present invention is to provide a method, an HVAC actuator, an HVAC system and a computer program product for configuring operation of an HVAC actuator with an HVAC flow control device which overcomes one or more of the above- mentioned problems of the prior art.

[0012] According to the present invention, these objects are addressed by the features of the independent claims. In addition, further advantageous embodiments follow from the dependent claims and the description hereinafter.

[0013] In particular, according to the present invention, these objects are addressed by a method of configuring operation of an HVAC actuator with an HVAC flow control device.

[0014] The term "HVAC actuator" in the context of the present invention refers to a field device as part of HVAC systems, primarily responsible for operating HVAC flow control devices for example valves and dampers. HVAC actuators perform electro-mechanical actions based on control signals to regulate fluid or airflow parameters for example pressure, temperature, or humidity.

[0015] The method of configuring operation of an HVAC actuator with an HVAC flow control device comprises a control unit of the HVAC actuator retrieving a machine-readable control device semantic model CDM. The control device semantic model CDM is descriptive of the HVAC flow control device. Having retrieved the control device semantic model CDM, the control unit configures the HVAC actuator to operate the HVAC flow control P28924PC00 December 2025

[0016] 3 / 44 device by applying the control device semantic model CDM using a domain ontology DO defining entities and relationships of the control device semantic model CDM.

[0017] According to embodiments disclosed herein, before retrieval of the control device semantic model CDM, the control unit retrieves an identifier from the HVAC flow control device. Depending on the application, the control unit retrieves the identifier from the HVAC flow control device on a conditional basis, including one or more of: upon startup, restart, initial commissioning, updating, power loss of the HVAC actuator. Alternatively, or additionally, the control unit retrieves the identifier from the HVAC flow control device periodically and / or based on usage, e.g., actuation cycles, of the HVAC flow control device and / or of the HVAC actuator.

[0018] Thereafter, the control unit retrieves the machine-readable control device semantic model CDM descriptive of the HVAC flow control device using the identifier.

[0019] The control device semantic model CDM represents an instance of the domain ontology DO descriptive of the HVAC flow control device identified by the identifier. According to embodiments disclosed herein, the method further comprising interpreting, by the control unit, the control device semantic model CDM using the domain ontology DO by mapping the instance represented by the control device semantic model CDM to the domain ontology DO.

[0020] According to embodiments disclosed herein, the domain ontology DO comprises:

[0021] Definitions of entities corresponding to physical and / or logical components;

[0022] Definitions of relationships between entities, for example hierarchical, functional, and / or logical relationships; and P28924PC00 December 2025

[0023] 4 / 44

[0024] Definitions of attributes of entities and / or relationships.

[0025] Analogously, the control device semantic model CDM, representing an instance of the domain ontology DO corresponding to the HVAC flow control device identified by the identifier, comprises: - Instances of entities corresponding to physical and / or logical components of the

[0026] HVAC flow control device;

[0027] Instances of relationships between the entities, corresponding to relationships between the physical and / or logical components of the HVAC flow control device, for example instances of hierarchical, functional, and / or logical relationships; and - Attribute values of entities and / or relationships of the HVAC flow control device.

[0028] In the context of the present invention, the term “relationship” refers to a link between a subject and an object within the domain ontology (DO) or within the control device semantic model (CDM).

[0029] According to embodiments, a relationship comprises one or more attributes that qualify, quantify, or provide context to the connection between the subject and the object. According to embodiments, these attributes may be represented in two ways:

[0030] (a) the relationship itself carries attributes as part of its definition; and / or

[0031] (b) an intermediary node representing the relationship, whereby the attributes are defined as separate entities or triples linked to the intermediary node. P28924PC00 December 2025

[0032] 5 / 44

[0033] According to embodiments disclosed herein, interpreting the control device semantic model CDM using the domain ontology DO comprises:

[0034] Parsing the control device semantic model CDM to identify instances of one or more entities and relationships;

[0035] Mapping the identified instances of entities and instances of relationships to corresponding definitions in the domain ontology DO; and

[0036] Using the mapping to configure the HVAC actuator to operate the HVAC flow control device according to the control device semantic model CDM.

[0037] According to embodiments disclosed herein, the control device semantic model CDM comprises a graph, whereby nodes of the graph correspond to one or more entities of the HVAC flow control device and / or one or more attribute values and edges of the graph correspond to relationships between entities of the HVAC flow control device.

[0038] According to embodiments disclosed herein, the control device semantic model CDM is described by a series of triples comprising a subject, a predicate, and an object, whereby:

[0039] The subject is representative of at least one entity;

[0040] The predicate is representative of at least one relationship between two or more entities; and

[0041] The object is representative of at least one attribute value or at least one entity.

[0042] In embodiments where relationships include attributes, the attributes may be expressed as direct properties of the relationship and / or as separate triples. P28924PC00 December 2025

[0043] 6 / 44

[0044] According to embodiments disclosed herein, the control device semantic model CDM comprises a resource identifier of the domain ontology DO corresponding to the control device semantic model CDM and wherein the method further comprises the control unit retrieving the domain ontology DO using the resource identifier from a storage device comprised by or communicatively coupled to the control unit.

[0045] According to embodiments disclosed herein, the control device semantic model CDM descriptive of the HVAC flow control device represents one or more of the following:

[0046] An operational parameter;

[0047] Context data indicative of a respective functionality

[0048] Interoperability and / or compatibility information;

[0049] A behavioral rule;

[0050] A control algorithm;

[0051] Addressing data of a sensor element, the addressing data enabling retrieval of sensor data related to the HVAC flow control device and / or components thereof.

[0052] According to embodiments disclosed herein, interpreting the control device semantic model CDM comprises one or more of the following:

[0053] Analyzing the operational parameters of the HVAC flow control device, for example flow control characteristics, pressure limits, and / or temperature thresholds, actuation times, or torque characteristics, to ensure operation within specified range(s); P28924PC00 December 2025

[0054] 7 / 44

[0055] Assessing the compatibility and / or interoperability information to confirm proper mechanical and / or electronic compatibility and / or interoperability between the HVAC actuator and the HVAC flow control device and / or component(s) thereof;

[0056] Applying the behavioral rules and / or the control algorithms defined in the control device semantic model CDM to dynamically adjust operation of the HVAC actuator based on current system conditions, including environmental factors and / or sensor data, in particular real-time sensor data;

[0057] Referencing any context data to adapt a control strategy of the HVAC actuator to a structure and / or operational logic of the HVAC flow control device represented by the control device semantic model CDM; and

[0058] Retrieving additional data and / or an update to ensure that the HVAC actuator is operating with the most up-to-date control device semantic model CDM descriptive of the HVAC flow control device.

[0059] According to embodiments disclosed herein, the control unit of the HVAC actuator reads out the identifier from a memory device of the HVAC flow control device upon the HVAC flow control device being brought into proximity of the HVAC actuator.

[0060] Alternatively, or additionally, the control unit of the HVAC actuator reads out the identifier from a memory device of the HVAC flow control device upon attachment of a driving interface of the HVAC actuator with a driven interface of the HVAC flow control device.

[0061] According to embodiments disclosed herein, retrieving the control device semantic model CDM descriptive of the HVAC flow control device comprises the control unit of the HVAC actuator retrieving the control device semantic model CDM from a memory device P28924PC00 December 2025

[0062] 8 / 44 of the HVAC flow control device. Alternatively, or additionally, retrieving the control device semantic model CDM descriptive of the HVAC flow control device comprises the control unit of the HVAC actuator retrieving the control device semantic model CDM from a storage device of the HVAC actuator. Alternatively, or additionally, retrieving the control device semantic model CDM descriptive of the HVAC flow control device comprises the control unit of the HVAC actuator retrieving the control device semantic model CDM from a remote computer.

[0063] According to embodiments disclosed herein, the method of configuring operation of the HVAC actuator with the HVAC flow control device further comprises:

[0064] The HVAC actuator receiving usage data related to the HVAC flow control device and / or component(s) thereof; and

[0065] The HVAC actuator updating the control device semantic model CDM using the usage data.

[0066] According to embodiments disclosed herein, the method of configuring operation of the HVAC actuator with the HVAC flow control device further comprises:

[0067] The control unit of the HVAC actuator validating the control device semantic model CDM against an actuator semantic model AM descriptive of the HVAC actuator and / or of the HVAC application; and

[0068] Enabling operation of the HVAC actuator with the HVAC flow control device upon successful validation or generating an alarm upon an unsuccessful validation. P28924PC00 December 2025

[0069] 9 / 44

[0070] The term “validation” as used herein refers to verifying whether the HVAC actuator can operate the identified HVAC flow control device and vice versa, i.e. , whether the identified HVAC flow control device can be operated by the HVAC actuator. Validation may comprise validation whether for software and / or hardware interoperability.

[0071] According to embodiments, "validation" refers to a comprehensive process of assessing compatibility between the HVAC actuator and the HVAC flow control device. The purpose is to verify that the two components can function together effectively within specified parameters. The validation process may include, but is not limited to:

[0072] Software Interoperability:

[0073] Validation ensures that the control device semantic model CDM, which represents the HVAC flow control device, aligns with the actuator semantic model AM of the HVAC actuator. This may include, but is not limited to:

[0074] Checking compatibility of control algorithms and behavioral rules.

[0075] Ensuring that operational parameters (e.g., flow characteristics, actuation timing) are interpretable and actionable by the control unit of the actuator.

[0076] Verifying communication protocols and data formats for seamless data exchange.

[0077] Hardware Interoperability:

[0078] The physical and electronic components of the HVAC actuator and flow control device should be compatible. This may include, but is not limited to: P28924PC00 December 2025

[0079] 10 / 44

[0080] Matching mechanical interfaces (e.g., the driving interface of the actuator and the driven interface of the flow control device).

[0081] Ensuring electrical and sensor connections are functional and adhere to the required specifications (e.g., voltage, signal types, connectivity). Operational Validation:

[0082] The control unit may evaluate whether the actuator can operate the flow control device within acceptable limits. This may include, but is not limited to:

[0083] Verifying that the HVAC actuator has the necessary torque, speed, and actuation range to drive the HVAC flow control device. - Ensuring that operational parameters for example temperature thresholds, pressure limits, or actuation cycles are within the HVAC actuator’s capabilities.

[0084] Semantic Mapping Validation:

[0085] Using the domain ontology DO, validation involves mapping the semantic instances from the CDM to the AM. This may include, but is not limited to: - Identifying and resolving conflicts in entity definitions or attribute values.

[0086] Confirming that the relationships and hierarchical structures in the CDM align with the HVAC actuator’s operational logic.

[0087] Upon successful validation, the control unit enables operation of the HVAC actuator with the flow control device, ensuring compatibility and interoperability. P28924PC00 December 2025

[0088] 11 / 44

[0089] If validation fails, the system generates an alarm or warning, which may highlight specific incompatibilities, for example incorrect parameters, mechanical mismatches, or unsupported algorithms.

[0090] This validation process ensures that the HVAC actuator and HVAC flow control device function together as intended, reducing risks of errors, inefficiency, or damage, and supporting system scalability and adaptability.

[0091] According to embodiments disclosed herein, validating the control device semantic model CDM against the actuator semantic model AM comprises:

[0092] Extracting, by the control unit, an actuator compatibility ontology (AGO) descriptive of requirements of the HVAC actuator to be compatible with the HVAC flow control device;

[0093] Extracting, by the control unit, a control device compatibility ontology (CDMCO) descriptive of requirements of the HVAC flow control device in order to be compatible with the HVAC actuator; and

[0094] Merging the actuator compatibility ontology (AGO) with the control device compatibility ontology (CDMCO) into a compatibility ontology (CO) descriptive of relationships between entities of the HVAC actuator and the HVAC flow control device.

[0095] According to embodiments disclosed herein, the requirements of the HVAC actuator to be compatible with the HVAC flow control device (as described by the actuator compatibility ontology (AGO)) and / or requirements of the HVAC flow control device in order to be compatible with the HVAC actuator (as described by the control device compatibility ontology (CDMCO)) comprise one or more of the following: P28924PC00 December 2025

[0096] 12 / 44

[0097] Definitions of requirement(s) of entities corresponding to physical and / or logical components. For example, the actuator compatibility ontology (AGO) defines a minimum set of physical and / or logical components of the HVAC actuator to drive a specific HVAC flow control device. Similarly, for example, the control device compatibility ontology (CDMCO) defines a minimum set of physical and / or logical components of the HVAC flow control device required to be driven by the specific HVAC actuator.

[0098] Definitions of requirement(s) of relationships between entities. For example, the actuator compatibility ontology (AGO) defines a minimum set of interactions between components of the HVAC actuator to drive a specific HVAC flow control device. Similarly, for example, the control device compatibility ontology (CDMCO) defines a minimum set of physical and / or logical connections between components of the HVAC flow control device required to be driven by the specific HVAC actuator.

[0099] Definitions of requirement(s) of attributes of entities and / or relationships. For example, the actuator compatibility ontology (AGO) defines attributes or characteristics of the minimum set of components of the HVAC actuator to drive a specific HVAC flow control device. Similarly, for example, the control device compatibility ontology (CDMCO) defines attributes or characteristics of the minimum set of physical and / or logical connections between components of the HVAC flow control device required to be driven by the specific HVAC actuator.

[0100] According to embodiments disclosed herein, the method of configuring operation of the HVAC actuator with the HVAC flow control device further comprises: P28924PC00 December 2025

[0101] 13 / 44

[0102] Extracting, by the control unit, the actuator compatibility ontology (AGO) from the actuator semantic model AM. In other words, the compatibility ontology (AGO) is comprised by / derivable from the actuator semantic model AM.

[0103] Extracting, by the control unit, the control device compatibility ontology (CDMCO) from the control device semantic model CDM. In other words, the control device compatibility ontology (CDMCO) is comprised by / derivable from the control device semantic model CDM.

[0104] According to embodiments disclosed herein, validating the semantic model CDM by the control device comprises generating a compatibility report (CR) between the control device semantic model CDM and the actuator semantic model AM. For example, the compatibility report (CR) is descriptive of matching entities, attributes, and / or relationships between the HVAC actuator and the HVAC flow control device. According to embodiments, the compatibility report (CR) may comprise indications of full but also partial compatibility or lack of compatibility. For example, the compatibility report (CR) may indicate that a motor of the HVAC actuator has sufficient torque to drive a valve of the HVAC flow control device but at the same time indicate that the compatibility is also partial since even a less powerful motor would be sufficient to drive the specific valve. As a further example, the compatibility report (CR) may indicate that a motor of the HVAC actuator has sufficient torque to drive a valve of the HVAC flow control device but only at a low actuation speed while the valve is capable of significantly higher actuator speeds, hence the compatibility being only partial or dependent on the requirements as to actuation time.

[0105] According to embodiments disclosed herein, the method of configuring operation of the HVAC actuator with the HVAC flow control device further comprises generating, by a recommendation engine (RE) of the control device, a proposal indicative of alternative P28924PC00 December 2025

[0106] 14 / 44

[0107] HVAC flow control device(s) and / or alternative control strategy(s) yielding an improved interoperability with the actuator semantic model AM. Continuing with the first example above, the recommendation engine (RE) would provide a recommendation for an alternative HVAC actuator with a less powerful motor, which would have a better compatibility with the specific valve of the HVAC flow control device.

[0108] According to the present invention, the objects identified in the beginning of this section above are addressed by an HVAC actuator comprising a motor, a control unit and a driving interface, the HVAC actuator being configured to carry out the method of configuring operation with an HVAC flow control device, according to one of the embodiments of the method disclosed herein.

[0109] According to the present invention, the objects identified in the beginning of this section above are further addressed by an HVAC system comprising an HVAC actuator and an HVAC flow control device comprising a flow regulating element and a driven interface drivingly coupled with the flow regulating element, the driven interface of the HVAC flow control device being complementary to the driving interface of the HVAC actuator. As used herein, the term “complementary,” when referring to the driven interface of the HVAC flow control device being complementary to the driving interface, shall be understood to comprise interfaces which are mechanically compatible for example to enable the driving interface to mechanically drive the driven interface. For example, the driven interface may be a shaft, or a stem and the corresponding driven interface comprises a socket, or a slot designed to securely engage with the shaft or stem of the driving interface. This mechanical engagement allows the transfer of torque from the actuator to the flow regulating element. The complementary interfaces may include features for example splines, or threading to ensure alignment, prevent slippage, and support precise actuation under varying loads or operational conditions. P28924PC00 December 2025

[0110] 15 / 44

[0111] According to embodiments of the HVAC system disclosed herein, the HVAC flow control device comprises a memory device; and the HVAC actuator comprises a data reader communicatively coupled to the control unit. The data reader of the HVAC actuator is configured to retrieve the identifier from the memory device of the HVAC flow control device upon the HVAC flow control device being brought into proximity of the HVAC actuator. Alternatively, or additionally, and / or the data reader of the HVAC actuator is configured to retrieve the identifier from the memory device of the HVAC flow control device upon the HVAC flow control device being brought into physical contact with the HVAC actuator.

[0112] According to embodiments disclosed herein, the HVAC flow control device comprises a data transmitter arranged adjacent to the driven interface of the HVAC flow control device. The data transmitter may be comprised by the memory device. Alternatively, the memory device is comprised by the data transmitter. Alternatively, the data transmitter is communicatively coupled with the memory device by a wired or wireless data connection. Correspondingly, the data reader is arranged adjacent to the driving interface of the HVAC actuator, the data reader being configured to retrieve the identifier and / or the control device semantic model CDM from the memory device, via the data transmitter of the HVAC flow control device upon attachment of the driving interface of the HVAC actuator with the driven interface of the HVAC flow control device.

[0113] According to embodiments disclosed herein, the data transmitter comprises a wireless and / or a wired data transmitter, arranged inside and / or within proximity of a stem of the driven interface. Correspondingly, the data reader comprises a wireless and / or a wired data receiver, arranged around and / or within proximity of the driving interface of the HVAC actuator. P28924PC00 December 2025

[0114] 16 / 44

[0115] According to the present invention, the objects identified in the beginning of this section above are further addressed by a computer program product comprising computer-read- able instructions, which, when executed by a control unit of an HVAC actuator, cause configuration of an HVAC actuator to operate an HVAC flow control device according to one of the embodiments disclosed herein.

[0116] Further disclosed herein are a computer-readable storage medium, in particular a non- transitory storage medium, a computer-readable data carrier, a computer-readable data carrier comprising computer-readable instructions which, when executed by a control unit of an HVAC actuator, cause configuration of an HVAC actuator to operate an HVAC flow control device according to one of the embodiments disclosed herein.

[0117] It is to be understood that both the foregoing general description and the following detailed description present embodiments and are intended to provide an overview or framework for understanding the nature and character of the invention. The accompanying drawings are included to provide a further understanding and are incorporated into and constitute a part of this specification. The drawings illustrate various embodiments, and together with the description serve to explain the principles and operation of the concepts disclosed.

[0118] BRIEF DESCRIPTION OF THE DRAWINGS

[0119] The present invention will be explained in more detail, by way of example, with reference to the drawings in which:

[0120] Figure 1 shows a schematic perspective view of an HVAC system according to an embodiment of the present invention; P28924PC00 December 2025

[0121] 17 / 44

[0122] Figure 2 shows a schematic lateral cross-sectional view of an HVAC system according to an embodiment of the present invention;

[0123] Figure 3 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator with an HVAC flow control device according to an embodiment of the present invention;

[0124] Figure 4 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator with an HVAC flow control device according to a further embodiment of the present invention;

[0125] Figure 5 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator with an HVAC flow control device according to an even further embodiment of the present invention;

[0126] Figure 6 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator with an HVAC flow control device according to yet a further embodiment of the present invention;

[0127] Figure 7 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator with an HVAC flow control device according to yet an even further embodiment of the present invention;

[0128] Figure 8 shows a flowchart illustrating steps of validating a control device semantic model CDM against an actuator semantic model AM according to an embodiment of the present invention;

[0129] Figure 9 shows an illustration of a graph representing a control device semantic model, according to an embodiment of the present invention; and P28924PC00 December 2025

[0130] 18 / 44

[0131] Figure 10 shows a schematic lateral cross-sectional view of an HVAC system according to a further embodiment of the present invention.

[0132] In the figures, the term “Figure” is abbreviated as “Fig.”. Furthermore, related components and steps are annotated with similar reference signs to indicate correspondence between the drawings.

[0133] In the figures, dashed lines illustrate functional and / or structural features and / or method steps / substeps of one or more embodiments. The illustration with dashed lines is not to be interpreted as indicating optionality with respect to all embodiments of the present invention.

[0134] DETAILED DESCRIPTION OF THE EMBODIMENTS

[0135] Figure 1 shows a schematic perspective view of an HVAC system 1 according to an embodiment of the present invention, comprising an HVAC actuator 10 and an HVAC flow control device 50. Figure 1 illustrates the HVAC actuator 10 being brought in proximity of the HVAC flow control device 50, a driving interface 16 of the HVAC actuator 10 being aligned with a driven interface 56 of the HVAC flow control device 50.

[0136] Figure 2 shows a schematic lateral cross-sectional view of the HVAC system 1 according to an embodiment of the present invention. As illustrated, the HVAC actuator 10 comprises a motor 14, a control unit 12, and a driving interface 16. The motor 14 is drivingly coupled with the driving interface 16, typically through a gearing. In some embodiments the control unit 12 may comprise a storage device 13 as shown in Fig 2 or be communicatively coupled to a storage device 13. Optionally, the HVAC actuator 10 comprises a communication interface 17, for example a wired or wireless communication interface, for data exchange with a remote computer 200, for example for retrieving the control device semantic model CDM. P28924PC00 December 2025

[0137] 19 / 44

[0138] In the embodiments shown in the figures, the HVAC flow control device 50 comprises a flow regulating element 52, for example a valve having an orifice, whereby rotation of the driven interface 56 about a rotational axis drives a valve shaft causing the orifice to be displaced between a closed and open position hence allowing the regulation of liquid flow therethrough. While not shown in the figures, regulation of the flow of gaseous fluids, for example air, is achievable similarly using a damper as the HVAC flow control device.

[0139] The HVAC actuator 10 comprises a data reader 15 communicatively coupled to the control unit 12. The HVAC flow control device 50 comprises a memory device 55. The control unit 12 of the HVAC actuator 10 is configured to retrieve an identifier of the HVAC flow control device 50 from the memory device 55 using the data reader 15. According to a particular embodiment, the memory device 55 is comprised by a Radio Frequency Identifier RFID tag or Near-Field Communication NFC tag, the RFID tag or NFC tag also acting as a data transmitter 57. In a particular embodiment, the identifier is retrieved upon the HVAC flow control device 50 being brought into proximity of the HVAC actuator 10, i.e. within communication range of the RFID tag or NFC tag acting as both the memory device 55 and data transceiver 57. Alternatively, not illustrated in the figures, the data reader 15 and the data transmitter 57 comprise one or more wired communication interfaces or buses, for example one or more single conductor wired interfaces or wired serial buses such as 1-Wire® or a similar proprietary wired communication interface. In this case the data reader 15 needs to make electrical contact with the data transmitter 57. In other words, merely bringing the data reader 15 and data transmitter 57 into proximity of one another is insufficient.

[0140] The flowcharts of Figures 3 to 8 illustrate various steps of embodiments of a method of configuring operation of the HVAC actuator 10 with the HVAC flow control device 50 according to the present invention. It shall be noted that a computer program product according to the present invention comprises computer-readable instructions which, P28924PC00 December 2025

[0141] 20 / 44 when executed by the control unit 12 of the HVAC actuator 10, cause configuration of the HVAC actuator 10 to operate the HVAC flow control device 50 according to one of the embodiments disclosed herein.

[0142] Figure 3 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator (e.g. the HVAC actuator 10) with an HVAC flow control device (e.g. the HVAC flow control device 50) according to an embodiment of the present invention. In a first, preparatory step S310, according to an embodiment, the control unit 12 of the HVAC actuator 10 retrieves an identifier from the HVAC flow control device 50. Depending on the application, the control unit 12 retrieves the identifier from the HVAC flow control device 50 on a conditional basis, including one or more of: upon start-up, restart, initial commissioning, updating of the HVAC actuator 10, or loss of power to the HVAC actuator 10. Alternatively, or additionally, the control unit 12 retrieves the identifier from the HVAC flow control device 50 periodically and / or based on usage, e.g. actuation cycles, of the HVAC flow control device 50 and / or of the HVAC actuator 10. Alternatively, or additionally, according to embodiments disclosed herein, the control unit 12 of the HVAC actuator 10 reads out the identifier from a memory device 55 of the HVAC flow control device 50 upon the HVAC flow control device 50 being brought into proximity of the HVAC actuator 10.

[0143] Thereafter, in a step S320, the control unit 12 retrieves, using the identifier or information therefrom, a machine-readable control device semantic model CDM descriptive of the HVAC flow control device 50. According to embodiments disclosed herein, retrieving the control device semantic model CDM descriptive of the HVAC flow control device 50 comprises the control unit 12 of the HVAC actuator 10 retrieving the control device semantic model CDM from a memory device 55 of the HVAC flow control device 50. Alternatively, or additionally, retrieving the control device semantic model CDM descriptive of the HVAC flow control device 50 comprises the control unit 12 of the HVAC actuator 10 P28924PC00 December 2025

[0144] 21 / 44 retrieving the control device semantic model CDM from a storage device 13 of the HVAC actuator 10. Alternatively, or additionally, retrieving the control device semantic model CDM descriptive of the HVAC flow control device 50 comprises the control unit 12 of the HVAC actuator 10 retrieving the control device semantic model CDM from a remote computer (e.g., a server or the remote computer 200 of Figure 1).

[0145] According to some embodiments, the step S310 of retrieving the identifier from the HVAC flow control device 50 may be skipped. For instance, if only one control device semantic model CDM is available to or known by the control unit 12, then the step S310 of retrieving the identifier from the HVAC flow control device 50 is not required and thus can be omitted.

[0146] Having retrieved the control device semantic model CDM, the control unit 12, in a following step S330 configures the HVAC actuator 10 to operate the HVAC flow control device 50. In a first substep S332 of configuring the HVAC actuator, the control unit 12 interprets the device semantic model CDM using a domain ontology DO. The domain ontology DO defines entities and relationships of the control device semantic model CDM. As part of interpreting the device semantic model CDM, in a step S340, an instance represented by the control device semantic model CDM is mapped to the domain ontology DO.

[0147] In the context of the present invention, the distinction between instance and definition relates to how the domain ontology (DO) and the control device semantic model (CDM) describe and utilize information:

[0148] Definition:

[0149] Definitions (of entities corresponding to physical and / or logical components, of relationships between entities, of attributes of entities and / or relationships) are comprised by the domain ontology (DO) P28924PC00 December 2025

[0150] 22 / 44

[0151] For example, a definition comprised by the domain ontology DO might state: "A valve has attributes for example flow rate, pressure limit, and actuation torque, and is connected to an actuator.

[0152] Instance:

[0153] Instance(s) of one or more of the entities corresponding to physical and / or logical components, of relationships between entities, of attributes of entities and / or relationships defined by the domain ontology DO are described by the control device semantic model (CDM). This represents specific, real-world examples or cases of the defined entities and relationships. Contains actual data values or characteristics.

[0154] For example, an instance might state: "This valve (Device ID: V123) has a flow rate of 100 L / min, a pressure limit of 5 bar, and requires an actuation torque of 10Nm.

[0155] Mapping

[0156] Mapping the instance (from the CDM) to the definition (in the DO) allows the control unit 12 to understand specific data related to the identified HVAC flow control device 50 in the context of a standardized framework. This enables a consistent and measurable way of rating the level of interoperability (hereinafter "interoperability level") achievable between the HVAC actuator 10 and the specific HVAC flow control device 50. Further details of the mapping process are described below with reference to figure 4. P28924PC00 December 2025

[0157] 23 / 44

[0158] Thereafter, in step S380, the control unit 12 configures the HVAC actuator 10 to operate the HVAC flow control device 50 by applying the control device semantic model CDM, which has been interpreted and aligned with the domain ontology DO:

[0159] Operational Parameter Integration:

[0160] The specific attributes of the HVAC flow control device 50, for example actuation limits, flow rates, or pressure thresholds (captured as instances in the control device semantic model CDM), are used to configure the operational settings of the HVAC actuator 10.

[0161] Control strategies:

[0162] Behavioral rules or control algorithms defined in the control device semantic model CDM (e.g., how to manage varying pressure conditions or flow rates dynamically) are implemented into the logic of the control unit 12.

[0163] Overall, step S380 ensures the HVAC actuator 10 is precisely tailored to the specific requirements and characteristics of the HVAC flow control device 50, enabling a consistent and measurable way of rating the interoperability level achievable between the HVAC actuator 10 and the specific HVAC flow control device 50.

[0164] Figure 4 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator 10 with an HVAC flow control device 50 according to a further embodiment of the present invention. In a step S415, the control unit 12 retrieves the domain ontology DO using the resource identifier from a storage device 13 comprised by or communicatively coupled to the control unit 12. P28924PC00 December 2025

[0165] 24 / 44

[0166] As illustrated in this figure, as part of step S432 of interpreting the control device semantic model CDM using the domain ontology DO, two further substeps are introduced as part of mapping an instance represented by the control device semantic model CDM to the domain ontology DO of step S440. Steps S410, and S420 are analogous to steps S310 and S320, respectively, and to avoid repetition will not be described here. Instead, the reader is referred to the description above in relation to Fig. 3. In a substep S442 the control device semantic model CDM is parsed to identify instances of one or more entities and relationships:

[0167] Identification of Entities:

[0168] The control device semantic model CDM is examined to locate instances of entities that represent physical or logical components of the HVAC flow control device 50. Examples of entities include a valve, a sensor, or an actuator component.

[0169] Detection of Relationships:

[0170] Relationships between the identified entities are extracted, for example hierarchical associations (e.g., an HVAC flow control device comprising a valve), functional connections (e.g., a sensor providing data to a controller), or physical linkages (e.g., a valve being connected to a driving interface 16).

[0171] Thereafter, in a substep S444, the control unit 12 maps the identified instances of entities and relationships from the control device semantic model CDM to corresponding definitions in the domain ontology DO. This involves associating specific components or attributes (e.g., a valve or its flow rate limit) with their generalized counterparts in the domain ontology DO. By doing so, the HVAC actuator 10 gains a structured understanding of the HVAC flow control device 50, aligning its operation with standardized definitions. P28924PC00 December 2025

[0172] 25 / 44

[0173] This enables a consistent and measurable way of rating the interoperability level achievable between the HVAC actuator 10 and the specific HVAC flow control device 50.

[0174] This mapping is then used in step S480 to apply the control device semantic model CDM using the domain ontology. In this way it is possible to configure the HVAC actuator 10 to operate the HVAC flow control device 50 according to the control device semantic model CDM.

[0175] Figure 5 shows a flowchart of a method of configuring operation of an HVAC actuator 10 with an HVAC flow control device 50 according to an even further embodiment of the present invention, illustrating various additional or alternative substeps of the step of interpreting (S332 or S432) the control device semantic model (CDM) using the domain ontology (DO). Otherwise step S530 as well as steps S510, S515 and S520 are analogous to those previously described in relation to Figure 3 (steps S310 and S320) and Figure 4 (step S415) and for brevity a description will not be repeated here.

[0176] In a substep S545 of step S532, operational parameters of the HVAC flow control device 50, for example but not limited to, flow control characteristics, pressure limits, temperature thresholds, actuation times, and torque characteristics, are analyzed by the control unit 12 to ensure the HVAC actuator 10 operates within specified ranges or any other operational parameter described in the semantic model.

[0177] Additionally, or alternatively, in a substep S546 of step S532, compatibility and interoperability information are assessed to confirm proper mechanical and / or electronic compatibility between the HVAC actuator 10 and the HVAC flow control device 50.

[0178] Additionally, or alternatively, in a substep S547 of step S532, behavioral rules and control algorithms defined in the control device semantic model CDM are applied to dynamically P28924PC00 December 2025

[0179] 26 / 44 adjust the operation of the HVAC actuator 10 based on current system conditions, including environmental factors and sensor data, in particular real-time sensor data.

[0180] Additionally, or alternatively, in substep S548 of step S532, context data is referenced to adapt the control strategy of the HVAC actuator 10 to align with the structure and operational logic of the HVAC flow control device 50 as represented in the control device semantic model CDM.

[0181] Additionally, or alternatively, in a substep S549 of step S532, additional data and / or updates are retrieved to ensure that the HVAC actuator 10 operates with the most up-to- date control device semantic model CDM descriptive of the HVAC flow control device 50.

[0182] Figure 6 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator 10 with an HVAC flow control device 50 according to yet a further embodiment of the present invention. Apart from two additional steps, the method shown is analogous to the method illustrated in Figure 3. Thus, to avoid repetition, analogous steps S610, S620 and S630 will not be described here. The reader is referred to the description of these steps above in relation to Figure 3. In step S660, the control unit 12 of the HVAC actuator 10 retrieves usage data related to the HVAC flow control device 50 and / or its components. Optionally, the control unit 12 may store the usage data or a subset thereof, for instance in the storage device 13, or write the same to the flow control device 50 or the memory device 55. This data may include operational metrics for example actuation frequency, operational cycles, wear-and-tear indicators, environmental factors (e.g., temperature or humidity), and sensor feedback from the HVAC flow control device 50. The data can be retrieved by the control unit 12 in real-time or periodically from the flow control device 50. This step ensures the HVAC actuator 10 maintains awareness of the current state and performance of the flow control device 50. P28924PC00 December 2025

[0183] 27 / 44

[0184] In step S662, the HVAC actuator 10 updates the control device semantic model CDM using the received usage data. This update involves integrating the new data into the CDM to reflect changes in the operational characteristics or status of the HVAC flow control device 50. For example, updated parameters might include recalibrated flow rates, revised pressure thresholds, or adjusted actuation torque requirements. The updated CDM ensures that the HVAC actuator 10 continues to operate the HVAC flow control device 50 with the highest level of precision and efficiency, adapting to evolving conditions and usage patterns.

[0185] Figure 7 shows a flowchart illustrating steps of a method of configuring operation of an HVAC actuator 10 with an HVAC flow control device 50 according to yet an even further embodiment of the present invention. The method is similar to that illustrated in Figure 3 in that steps S710, S720, S732, S740 and S780 are analogous to steps S310, S320, S332, S340 and S380, respectively. To avoid repetition, the reader is referred to the description of these steps provided above in conjunction with Figure 3. As shown, the method of Figure 7 includes two additional steps compared to the method depicted in Figure 3. After step S740, in step S770, the control unit 12 of the HVAC actuator 10 performs a validation of the control device semantic model CDM against the actuator semantic model AM. This process enables a consistent and measurable way of rating the interoperability level achievable between the HVAC actuator 10 and the specific HVAC flow control device 50. The validation encompasses several aspects:

[0186] The control unit 12 checks whether the behavioral rules, control algorithms, and operational parameters defined in the control device semantic model CDM align with the actuator's capabilities as described in the actuator semantic model AM. This includes verifying for example, but limited to, communication protocols, command execution compatibility, and data format consistency. P28924PC00 December 2025

[0187] 28 / 44

[0188] The control unit 12 evaluates mechanical and / or electronic compatibility between the HVAC actuator 10 and the HVAC flow control device 50. This involves, for example, confirming that physical interfaces (e.g., driving interface 16 and driven interface 56) align and / or that electrical connections, for example voltage and / or signal compatibility, are adequate and / or digital or functional compatibility such as data formats, data rate, communication protocols, data encryption etc.

[0189] The validation may further ensure that the combined operation of the HVAC actuator 10 and the HVAC flow control device 50 meets the functional requirements of the overall HVAC application, taking into account environmental and application-specific constraints.

[0190] Upon successful validation, the control unit 12 enables the HVAC actuator 10 to operate the HVAC flow control device 50. If validation results in a level of interoperability lower than a minimum interoperability threshold (e.g., due to mismatched operational parameters or incompatible interfaces), in a step S790 the system generates an alarm, alerting the user or system administrator to the issue. This ensures safe, reliable, and efficient operation while preventing potential errors or damage.

[0191] Figure 8 shows a flowchart illustrating steps of validating a control device semantic model CDM against an actuator semantic model AM according to an embodiment of the present invention. In step S872, the control unit 12 extracts an actuator compatibility ontology (ACO). The ACO is a structured representation of the HVAC actuator 10’s requirements for compatibility with an HVAC flow control device 50. These requirements may include, for example, but not limited to mechanical specifications (e.g., torque, speed, and driving interface dimensions), electronic parameters (e.g., voltage range, communication protocols), and operational constraints (e.g., actuation range or temperature limits). P28924PC00 December 2025

[0192] 29 / 44

[0193] In step S874, the control unit 12 extracts a control device compatibility ontology (CDMCO). This control device compatibility ontology (CDMCO) describes the requirements of the HVAC flow control device 50 to be operated by the HVAC actuator 10. These requirements include properties for example torque tolerances, actuation dynamics, pressure or flow thresholds, and driven interface specifications.

[0194] In step S876, the control unit 12 merges the actuator compatibility ontology AGO with the control device compatibility ontology CDMCO to create a compatibility ontology (CO). The CO provides a unified representation of the relationships between the HVAC actuator 10 and the HVAC flow control device 50, making it possible that all compatibility criteria of both components are evaluated together.

[0195] In step S878, the control unit 12 compares the merged compatibility ontology CO with the specific operational context of the HVAC application. This involves checking whether the relationships and attributes defined in the CO satisfy the functional and environmental conditions under which the HVAC actuator 10 and the HVAC flow control device 50 will operate.

[0196] In step S879, a recommendation engine (RE) of the control device 12 generates a proposal indicative of alternative HVAC flow control device(s) 50 and / or alternative control strategy(s) yielding an improved interoperability with the actuator semantic model AM.

[0197] Figure 9 illustrates a graph representation of a control device semantic model (CDM), in accordance with an embodiment of the present invention, whereby nodes of the graph correspond to one or more entities of the HVAC flow control device 50 and / or one or more attribute values and whereby edges of the graph correspond to relationships be- P28924PC00 December 2025

[0198] 30 / 44 tween entities of the HVAC flow control device 50. The graph comprises entities, attributes, and relationships that define the characteristics of the HVAC flow control device 50, specifically in this case, a valve and its associated interface.

[0199] Valve Entity: The Valve is the central component in the graph and is identified by a unique

[0200] Valve ID, represented by a node labeled with an identifier (e.g., "DSADEDCDESASDCGSRE").

[0201] Valve Interface:

[0202] The Valve Interface connects the Valve to the external entities, for example an HVAC actuator. The valve interface is further detailed through an entity labeled

[0203] Interface 1 , which serves as the linkage point for threaded connections.

[0204] Threaded Connections:

[0205] Two Threaded Connections are represented, labeled Threaded Connection 1 and Threaded Connection 2. These connections are attributes of the Interface 1 , specifying the method by which the valve is connected mechanically.

[0206] Connection Sizes:

[0207] Each threaded connection, Threaded Connection 1 and Threaded Connection 2, has a thread size represented by nodes TISize and T2Size. Both sizes are explicitly labeled with values (e.g., "25") and units (e.g., "millimeters"). P28924PC00 December 2025

[0208] 31 / 44

[0209] The units for these sizes are detailed in nodes TISizeUnit and T2SizeUnit, ensuring precise dimensional specification.

[0210] This graph highlights how the control device semantic model CDM organizes and defines the physical and logical components of a valve, enabling the HVAC actuator 10 to interpret and interact with the HVAC flow control device 50 effectively. Each node and edge represents either an entity, a relationship, or an attribute, structured according to a domain ontology (DO).

[0211] In an embodiment, the control device semantic model CDM is described by a series of triples comprising a subject, a predicate, and an object, whereby the subject is representative of at least one entity, the predicate is representative of at least one relationship between two or more entities; and the object is representative of at least one attribute value or at least one entity. The following series of triples describe non-exhaustively the valve represented by the graph of Figure 9:

[0212] This is a Valve

[0213] Valve has property Valve ID

[0214] Valve has object Valve Interface

[0215] Valve ID is "DSADEDCDESASDCSGRE "

[0216] Interface 1 is a Valve Interface

[0217] Valve Interface enables Interconnection

[0218] Interface 1 has Threaded Connection 1

[0219] Threaded Connection 1 has T ISize

[0220] T I Size has value 25

[0221] T I Size has engineering unit T ISizeUnit P28924PC00 December 2025

[0222] 32 / 44

[0223] TISizeUnit is equal to millimeters

[0224] Interface 1 has Threaded Connection 2

[0225] Threaded Connection 2 has T2Size

[0226] T2 Size has value 25

[0227] T2 Size has engineering unit T2SizeUnit

[0228] T2 SizeUnit is equal to millimeters

[0229] According to embodiments, relationships between entities may be represented in different ways within the control device semantic model CDM.

[0230] Method 1 : Parameters comprised by the Relationship - Property Graph Model

[0231] In a Property Graph Model, an edge, i.e. the relationship linking two entities, may hold its own set of properties similar to a node. This model provides a direct connection that embeds descriptive details and is comparatively simple to express.

[0232] For example:

[0233] (Actuator SN789 ) — controls ^ (Valve Model Z )

[0234] The controls relationship itself may comprise parameters as follows:

[0235] Parameter on "controls" Value controlType "Modulating"

[0236] Torque "20 Nm" installationDate "2024 -10-31" failsafeStatus "Normally Open" P28924PC00 December 2025

[0237] 33 / 44

[0238] In this approach, each property is intrinsically linked to the edge representing the relationship. The control unit 12 interprets both entities and edge attributes when configuring the HVAC actuator 10 to operate the HVAC flow control device 50.

[0239] Method 2: Intermediary Node (RDF / Reification Model) In a RDF / Reification Model, relationships themselves do not inherently carry attributes. Instead, descriptive details are expressed through a newly created intermediary node that represents the relationship instance.

[0240] The actuator and valve are each connected to this node, and attributes are attached to the node through individual statements. For example:

[0241] Subj ect Predicate Ob ect

[0242] Actuator SN789 participates In Connection 123

[0243] Connection 123 controls Valve Valve Model Z

[0244] Connection 123 hasControlType "Modulating"

[0245] Connection 123 hasTorque "20 Nm"

[0246] Connection 123 wasInstalledOn "2024-10-31"

[0247] Connection 123 hasFailsaf e "Normally Open"

[0248] While this representation requires multiple triples to describe what a Property Graph Model expresses in a single enriched relationship, reification provides a highly explicit and standards-compliant representation within a formal Subject-Predicate-Object structure. P28924PC00 December 2025

[0249] 34 / 44

[0250] Figure 10 shows a schematic lateral cross-sectional view of an HVAC system 1 according to a further embodiment of the present invention, whereby a wireless data transmitter 57 - integral with the memory device 55 - is arranged around a stem of the driven interface 56 of the HVAC flow control device 50 (shown above the driven interface 56 in Figure 10 for clarity), for example using a ring-shaped RFID tag or NFC tag. Correspondingly a wireless data reader 15 of the HVAC actuator 10 is arranged around the driving interface 16 of the HVAC actuator 10, for example, using a ring-shaped data reader 15 (cross section shown in Figure 3). This arrangement enables the data reader 15 of the HVAC actuator 10 to retrieve the identifier from the memory device 55 of the HVAC flow control device 50 upon the HVAC flow control device 50 being brought into proximity of the HVAC actuator 10 yielding certainty about identifying the HVAC flow control device 50 that is coupled with the HVAC actuator 10. Hence, false identification of a nearby HVAC flow control device can be avoided.

[0251] P28924PC00 December 2025

[0252] 35 / 44

[0253] REFERENCE LIST

[0254] HVAC system 1

[0255] H VAC actuator 10

[0256] Control unit 12

[0257] Storage Device 13

[0258] Motor 14

[0259] Data reader 15

[0260] Driving interface 16

[0261] Communication interface 17

[0262] HVAC flow control device 50

[0263] Flow regulating element 52

[0264] Driven interface 56

[0265] Memory device 55

[0266] Data transmitter 57

[0267] Remote computer 200

Claims

P28924PC00 December 202536 / 44CLAIMS1. A method of configuring operation of an HVAC actuator (10) with an HVAC flow control device (50), the method comprising: retrieving, by a control unit (12) of the HVAC actuator (10), a machine-readable control device semantic model CDM descriptive of the HVAC flow control device (50); and configuring, by the control unit (12), the HVAC actuator (10) to operate the HVAC flow control device (50) by applying the control device semantic model CDM descriptive of the HVAC flow control device (50) using a domain ontology DO defining entities and relationships of the control device semantic model CDM.

2. The method according to claim 1 , further comprising retrieving, by the control unit (12), an identifier from the HVAC flow control device (50), wherein the control unit (12) retrieves the machine-readable control device semantic model CDM descriptive of the HVAC flow control device (50) using the identifier.

3. The method according to claim 1 or 2, wherein the control device semantic model CDM represents an instance of the domain ontology DO descriptive of the HVAC flow control device (50) identified by the identifier, the method further comprising interpreting, by the control unit (12), the control device semantic model CDM using the domain ontology DO by mapping the instance represented by the control device semantic model CDM to the domain ontology DO.

4. The method according to claim 3, wherein the domain ontology DO comprises: definitions of entities corresponding to physical and / or logical components; definitions of relationships between entities; and definitions of attributes of entities and / or relationships,P28924PC00 December 202537 / 44 wherein the control device semantic model CDM, representing an instance of the domain ontology DO corresponding to the HVAC flow control device (50) identified by the identifier, comprises: instances of entities, corresponding to physical and / or logical components of the HVAC flow control device (50); instances of relationships between the entities, corresponding to relationships between the physical and / or logical components of the HVAC flow control device (50); and attribute values of entities and / or relationships of the HVAC flow control device (50).

5. The method according to claim 4, wherein interpreting the control device semantic model CDM using the domain ontology DO comprises: parsing the control device semantic model CDM to identify instances of one or more entities and relationships; mapping the identified instances of entities and instances of relationships to corresponding definitions in the domain ontology DO; and using the mapping to configure the HVAC actuator (10) to operate the HVAC flow control device (50) according to the control device semantic model CDM.

6. The method according to claim 4 or 5, wherein the control device semantic model CDM comprises a graph, whereby nodes of the graph correspond to one or more entities of the HVAC flow control device (50) and / or one or more attribute values and edges of the graph correspond to relationships between entities of the HVAC flow control device (50).P28924PC00 December 202538 / 447. The method according to one of claims 1 to 6, wherein the control device semantic model CDM is described by a series of triples comprising a subject, a predicate, and an object, whereby: the subject is representative of at least one entity; the predicate is representative of at least one relationship between two or more entities; and the object is representative of at least one attribute value or at least one entity.

8. The method according to one of claims 1 to 7, wherein the control device semantic model CDM comprises a resource identifier of the domain ontology DO corresponding to the control device semantic model CDM and wherein the method further comprises the control unit (12) retrieving the domain ontology DO using the resource identifier from a storage device (13) comprised by or communicatively coupled to the control unit (12).

9. The method according to one of claims 1 to 8, wherein the control device semantic model CDM descriptive of the HVAC flow control device (50) represents one or more of the following: an operational parameter; context data indicative of a respective functionality interoperability and / or compatibility information; a behavioral rule; a control algorithm; addressing data of a sensor element, the addressing data enabling retrieval of sensor data related to the HVAC flow control device (50) and / or components thereof.P28924PC00 December 202539 / 4410. The method according to claim 9, wherein interpreting the control device semantic model CDM comprises one or more of the following: analyzing the operational parameters of the HVAC flow control device (50); assessing the compatibility and / or interoperability information to confirm proper mechanical and / or electronic compatibility and / or interoperability between the HVAC actuator (10) and the HVAC flow control device (50) and / or component(s) thereof; applying the behavioral rules and / or the control algorithms defined in the control device semantic model CDM to dynamically adjust operation of the HVAC actuator (10) based on current system conditions, including environmental factors and / or sensor data; referencing any context data to adapt a control strategy of the HVAC actuator (10) to a structure and / or operational logic of the HVAC flow control device (50) represented by the control device semantic model CDM; and retrieving additional data and / or an update to ensure that the HVAC actuator (10) is operating with the most up-to-date control device semantic model CDM descriptive of the HVAC flow control device (50).11 . The method according to one of claims 2 to 10, further comprising the control unit (12) of the HVAC actuator (10) reading out the identifier from a memory device (55) of the HVAC flow control device (50) upon the HVAC flow control device (50) being brought into proximity of the HVAC actuator (10), and / or upon attachment of a driving interface (16) of the HVAC actuator (10) with a driven interface (56) of the HVAC flow control device (50).

12. The method according to one of claims 1 to 11 , wherein, retrieving the control device semantic model CDM descriptive of the HVAC flow control device (50) comprises:P28924PC00 December 202540 / 44 the control unit (12) of the HVAC actuator (10) retrieving the control device semantic model CDM from a memory device (55) of the HVAC flow control device (50); and / or the control unit (12) of the HVAC actuator (10) retrieving the control device semantic model CDM from a storage device (13) of the HVAC actuator (10); and / or the control unit (12) of the HVAC actuator (10) retrieving the control device semantic model CDM from a remote computer (200).

13. The method according to one of claims 1 to 12, further comprising: the HVAC actuator (10) receiving usage data related to the HVAC flow control device (50) and / or component(s) thereof; and the HVAC actuator (10) updating the control device semantic model CDM using the usage data.

14. The method according to one of claims 1 to 13, further comprising: the control unit (12) of the HVAC actuator (10) validating the control device semantic model CDM against an actuator semantic model AM descriptive of the HVAC actuator (10) and / or of the HVAC application; and enabling operation of the HVAC actuator (10) with the HVAC flow control device (50) upon successful validation or generating an alarm upon an unsuccessful validation.

15. The method according to claim 14, wherein validating the control device semantic model CDM against the actuator semantic model AM comprises: extracting, by the control unit (12), an actuator compatibility ontology (ACO) descriptive of requirements of the HVAC actuator (10) to be compatible with the HVAC flow control device (50);P28924PC00 December 202541 / 44 extracting, by the control unit (12), a control device compatibility ontology (CDMCO) descriptive of requirements of the HVAC flow control device (50) in order to be compatible with the HVAC actuator (10); and merging the actuator compatibility ontology (ACO) with the control device compatibility ontology (CDMCO) into a compatibility ontology (CO) descriptive of relationships between entities of the HVAC actuator (10) and the HVAC flow control device (50).

16. The method according to claim 15, wherein the requirements of the HVAC actuator (10) to be compatible with the HVAC flow control device (50) and / or requirements of the HVAC flow control device (50) in order to be compatible with the HVAC actuator (10) comprise one or more of the following: definitions of requirement(s) of entities corresponding to physical and / or logical components; definitions of requirement(s) of relationships between entities; and definitions of requirement(s) of attributes of entities and / or relationships.

17. The method according to claim 15 or 16, further comprising: extracting, by the control unit (12), the actuator compatibility ontology (ACO) from the actuator semantic model AM; and / or extracting, by the control unit (12), the control device compatibility ontology (CDMCO) from the control device semantic model CDM.

18. The method according to one of claims 14 to 17, wherein validating the semantic model CDM by the control device comprises generating a compatibility report (CR) between the control device semantic model CDM and the actuator semantic model AM.P28924PC00 December 202542 / 4419. The method according to one of claims 14 to 18, further comprising generating, by a recommendation engine (RE) of the control device, a proposal indicative of alternative HVAC flow control device(s) (50) and / or alternative control strategy(s) yielding an improved interoperability with the actuator semantic model AM.

20. An HVAC actuator (10) comprising a motor (14), a control unit (12) and a driving interface (16), the HVAC actuator (10) being configured to carry out the method according to one of claims 1 to 18.

21. An HVAC system (1) comprising an HVAC actuator (10) according to claim 20 and an HVAC flow control device (50) comprising a flow regulating element (52) and a driven interface (56) drivingly coupled with the flow regulating element (52), the driven interface (56) of the HVAC flow control device (50) being complementary to the driving interface (16) of the HVAC actuator (10).

22. The HVAC system (1) according to claim 21 , wherein: the HVAC flow control device (50) comprises a memory device (55); and the HVAC actuator (10) comprises a data reader (15) communicatively coupled to the control unit (12) and configured to retrieve the identifier from the memory device (55) of the HVAC flow control device (50) upon the HVAC flow control device (50) being brought into proximity of the HVAC actuator (10) and / or upon the HVAC flow control device (50) being brought into physical contact with the HVAC actuator (10).

23. The HVAC system (1) according to claim 21 , wherein: the HVAC flow control device (50) comprises a data transmitter (57) arranged adjacent to the driven interface (56) of the HVAC flow control device (50), the data transmitter (57) being comprised by the memory device (55) and / or the memoryP28924PC00 December 202543 / 44 device (55) being comprised by the data transmitter (57) and / or the data transmitter (57) being communicatively coupled with the memory device (55); and the data reader (15) is arranged adjacent to the driving interface (16) of the HVAC actuator (10), the data reader (15) being configured to retrieve the identifier and / or the control device semantic model CDM from the memory device (55), via the data transmitter (57) of the HVAC flow control device (50) upon attachment of the driving interface (16) of the HVAC actuator (10) with the driven interface (56) of the HVAC flow control device (50).

24. The HVAC system (1) according to claim 23, wherein: the data transmitter (57) comprises a wireless and / or a wired data transmitter (57), arranged inside and / or within proximity of a stem of the driven interface (56); and the data reader (15) comprises a wireless and / or a wired data receiver, arranged around and / or within proximity of the driving interface (16) of the HVAC actuator (10).

25. A computer program product comprising computer-readable instructions, which, when executed by a control unit (12) of an HVAC actuator (10), cause configuration of an HVAC actuator (10) to operate with an HVAC flow control device (50) according to the method of one of claims 1 to 19.

Images