Method and system for defining and configuring hardware settings of a fluid handling system

Abstract

The present disclosure relates to a method for defining and configuring a hardware setup (2) of a fluid handling system, the method comprising: - processing (103) user input at a client module (15), wherein the user input comprises a requirements data set for the fluid handling system, - receiving (105) the requirements data set from the client module (15) at a server module (17), wherein the server module (17) is connected to the client module (15) via a network (11), - defining (107) the hardware setup (2) of the fluid handling system by a setup module (19) based on the requirements data set and stored catalog data, - generating (109) a configuration file (25) by a configuration module (23) based on the hardware setup (2) and the requirements data set, - approving (113) the hardware setup (2) by the client module (15), and - transmitting (116) the configuration file (25) to a universal control module (29) to configure the fluid handling system, the universal control module being part of the hardware setup (2).

Description

Technical Field

[0001] The present disclosure relates to a method and system for defining and configuring hardware settings for a fluid treatment system. In particular, the present disclosure relates to providing a software and hardware environment to facilitate setting up a water treatment system including a plurality of dosing pumps for adding chemicals and additives to a water distribution system. Background Art

[0002] Setting up a fluid handling system can be a challenging and daunting task for a provider of a water distribution system. Often, the provider of a water distribution system only knows the requirements that the water treatment system needs to meet, but has no information about an adequate hardware setup that can do the job. There are countless configuration options for defining a hardware setup, which can include multiple pumps and other devices such as sensors, mixers, valves, controllers, etc. The provider of the fluid handling system has stored catalog data for all the hardware components and is able to provide any potential hardware setup, but has no information about the requirements that the water treatment system needs to meet.

[0003] The present disclosure provides a new method and system for bringing together demand information and catalog information in an efficient manner. Thus, sufficient hardware settings can be defined and configured to meet specific needs. In addition, the method and system described herein for defining and configuring hardware settings for a fluid handling system allow for providing hardware settings as a minimum viable product (MVP) that can be enhanced upon user feedback. In addition, the process of configuring hardware settings is facilitated to reduce the risk of misconfiguration and improper assembly of hardware settings. Summary of the invention

[0004] According to a first aspect of the present disclosure, there is provided a method for defining and configuring hardware settings of a fluid treatment system, the method comprising the following steps:

[0005] - processing user input at a client module, wherein the user input comprises a requirements data set for the fluid treatment system,

[0006] - receiving the requirement data set from the client module at a server module, wherein the server module is connected to the client module via a network,

[0007] - defining, by a setup module, said hardware setup of said fluid treatment system based on said requirements data set and stored catalogue data,

[0008] - generating, by a configuration module, a configuration file based on the hardware settings and the requirement data set,

[0009] - approval of said hardware settings by said client module, and

[0010] - transferring the configuration file to a universal control module for configuring the fluid handling system, the universal control module being part of the hardware setup.

[0011] Thus, the user may enter the requirement data at a client module, which may be implemented as an executable application on a mobile device (e.g., a smartphone or tablet). At a relatively high level, the requirement data may be, for example, "disinfect a water flow at 500 liters per hour and continuously control the water value". The graphical user front end of the client module may guide the user through a series of questions to interrogate the requirement data set. In particular, the requirement data may contain information about the type and scale of tasks that the fluid treatment system should accomplish.

[0012] Preferably, both the server module and the client module can be part of a common software environment or virtual "ecosystem" that connects different modules via a network (e.g., the Internet). Based on the demand data set and the stored catalog data, the setup module is able to define the hardware settings, for example, defining how many pumps of what type are needed and which kind and how many other components (e.g., sensors, controllers, valves, connectors, etc.) are needed. The client module can be configured to display a graphical representation of the proposed hardware settings and prompt the user to approve or reject the proposed hardware settings. In the case of rejecting the proposed hardware settings, the user can be prompted to update and / or add demand data to redefine the hardware settings. Once the user approves the proposed hardware settings, the hardware settings can be shipped to the user.

[0013] In addition to defining and delivering customized hardware settings, the methods and systems described herein also facilitate the difficult task of configuring the hardware settings to fully operate. To provide this, the hardware settings include a universal control module for configuring the fluid handling system. Preferably, the universal control module is integrated in or attached to the electronics housing of the pump assembly of the hardware settings.

[0014] The configuration module (e.g., as part of a common software environment or virtual "ecosystem") generates a configuration file based on the hardware settings and the requirements data set. This configuration is then transmitted to the common control module. The transmission of the configuration file can be done before shipping the hardware settings, or preferably after shipping based on user request. For example, the configuration file can include a connection table with address information of the hardware components to ensure that the hardware components are properly assembled and connected according to the defined hardware settings.

[0015] Optionally, the method may include the step of receiving monitoring and performance data from the universal control module via the network at the monitoring module. Thus, based on this feedback, the fluid treatment system may be updated or enhanced by software and / or hardware. Furthermore, maintenance and repair intervals may be adjusted based on the monitoring and performance data received as feedback.

[0016] Optionally, the hardware arrangement may include a pump assembly, wherein the universal control module is mounted in or attached to an electronics housing of the pump assembly. Preferably, the universal control module is arranged in an electronics box, which is attached to the electronics housing of the pump assembly. The electronics box may have a shape and cross-sectional dimensions similar to the electronics housing to allow a space-saving and neat arrangement of the electronics box and adjacent electronics housings forming at least one flush common lateral side. For example, the electronics box and the electronics housing may be stacked on top of each other.

[0017] Optionally, the hardware setup may include at least one sensor unit having a communication link with the universal control module, wherein the configuration file includes sensor setup parameters associated with the at least one sensor unit. For example, the at least one sensor unit may include one or more of the following: a flow meter, a pressure sensor, a temperature sensor, a pH sensor and / or another type of sensor. According to the defined hardware setup, each of the at least one sensor unit may have a defined address and connection point in the hardware setup, which address and connection point may be recorded in the configuration file in the form of a connection table. Thus, a fast and correct assembly of the hardware setup may be ensured.

[0018] Optionally, the configuration file may include identification information of hardware components of the hardware setting. The identification information of the hardware components may allow a clear distinction between different hardware components. The identification information may include separate product information, such as a serial number. Thus, the universal control module is able to check whether all hardware components match the hardware setting according to the configuration file. The universal control module may be configured to reject any non-compliant hardware components and / or output a warning about them.

[0019] Alternatively, the configuration file may include hardware address information in a bus communication link connecting the hardware components of the hardware setup. The address information of the hardware components may allow for clear location of different hardware components within the hardware setup. Thus, the universal control module is able to check whether all hardware components are correctly assembled within the hardware setup based on the configuration file. The universal control module may be configured to reject any incorrectly assembled hardware component and / or output a warning about it.

[0020] Optionally, the hardware setup may include a list of hardware components and instructions for connecting the hardware components of the hardware setup. This may facilitate the assembly process and reduce the risk of incorrect assembly.

[0021] Optionally, the demand data may include at least one of a demand group, the group including:

[0022] - water treatment purposes,

[0023] - the type of chemical to be dispensed or delivered,

[0024] - the expected volume or flow rate of fluid to be processed, and

[0025] - Installation parameters, specifically height difference, conduit length, location of feed ports and fluid pressure.

[0026] Preferably, the demand data only contains information available in the domain of the provider of the water distribution system. Therefore, the provider of the water distribution system as a user can be queried by the user module to retrieve the demand data. Once the demand data is sufficient for the setup module to make a proposal for the hardware settings, the query can be stopped.

[0027] Optionally, the step of defining the hardware settings of the fluid treatment system may include determining the required type and / or quantity of the pumps in the hardware settings based on the required flow of the fluid to be treated. This is one of the most difficult optimization problems to be solved in order to define the hardware settings. The settings module may have two or more options for selecting the type and / or quantity of pumps from the catalog data to meet the needs defined by the demand data. These options may be displayed to the user by the user module for selection. Options may be sorted according to certain user preferences (such as cost or energy consumption). Preferably, the settings module is configured to automatically select among several options based on predetermined user preferences so that the user module only displays a proposed hardware setting for user approval. The user can update the user preferences via the user module.

[0028] Optionally, the configuration file may include controller setting parameters to customize the generic control module to a specific control module defined by the controller setting parameters. For example, the generic control module may include a P-, I-, PI-, PD- or PID-controller for closed-loop control of a pump or valve, for example using the following control function

[0029]

[0030] where u(t) is a control parameter (e.g., pump speed or valve opening), and e(t) is a time-dependent error variable representing the deviation between the setpoint value and the measured value (e.g., the setpoint temperature and the temperature measured by a temperature sensor). p , Ki and / or K d are the tuning coefficients of the proportional, integral and derivative terms of the control function, which depend on the specific hardware settings and the desired control function derived from the requirement data. Since the configuration module knows the specific hardware settings and the desired control function when generating the configuration file, it can calculate the tuning coefficient K p , K i and / or K d The controller is then configured and preset in the configuration file. Therefore, the user no longer has to adjust the controller to the desired purpose. Once the configuration file is transferred to the universal control module, the controller therein is specifically configured and adjusted to perform the desired control function with the selected hardware settings.

[0031] Optionally, the configuration file may include at least one of a group of operating parameters, the group comprising:

[0032] - Feed pressure,

[0033] - dosage mass flow,

[0034] - set point pressure,

[0035] - set point flow,

[0036] - set point temperature,

[0037] - Controller setting parameters,

[0038] - connection table, and

[0039] -Communication and / or network parameters.

[0040] For example, operating parameters may be derived from the demand data and / or the user module may ask the user for more specific information to be stored in the configuration file, such as set point values ​​for pressure, flow and / or temperature. Connection tables and / or other communication and network parameters may be determined by the defined hardware settings.

[0041] Optionally, the step of approving the hardware settings by the client module comprises: displaying the hardware settings at the client module and receiving approval of the displayed hardware settings. The user may be asked for a positive decision / negative decision and / or a selection from a list of proposed hardware settings.

[0042] Optionally, the method may further include updating the configuration file according to a user command and / or according to monitoring and performance data received by the monitoring module from the universal control module via the network. For example, if the performance data indicates a change in pipeline characteristics, such as due to increased filter resistance, an update of the configuration file may be beneficial. The controller setting parameters may then be updated. In the event that a new hardware component (e.g., a sensor) is added to an already assembled system, the user may command the download of a new configuration file including data about the new hardware component.

[0043] Optionally, the method may further comprise displaying assembly instructions for the hardware setup. This is particularly useful in order to show the user assembly instructions exactly for a highly customized hardware setup to be installed. Thus, the assembly instructions may be as independent as the hardware setup. This reduces the risk of incorrect assembly.

[0044] Optionally, the step of defining the hardware setup may include providing two or more options for one or more hardware components of the hardware setup, and asking for a selection of the options at the client module. Preferably, an inexperienced user should not have the option of selecting a specific hardware component. However, a more experienced user may wish to have a specific hardware component in the hardware setup. This selection of a specific hardware component may be interpreted as requirement data for the rest of the hardware setup.

[0045] The above method can be implemented in the form of compiled or uncompiled software code, which is stored on a computer-readable medium with instructions for executing the method. Alternatively or additionally, the method can be performed by software in a cloud-based system (i.e., one or more modules of the control system), in particular, the processing module can be implemented in a cloud-based system.

[0046] According to a second aspect of the present disclosure, there is provided a system for defining and configuring hardware settings of a fluid handling system, the system comprising:

[0047] - a client module configured to process user input, the user input comprising a requirements data set for the fluid treatment system,

[0048] - a server module, said server module being connectable to said client module via a network to receive said requirement data set from said client module,

[0049] a setup module configured to define the hardware settings of the fluid treatment system based on the requirements data set and stored catalogue data,

[0050] - a configuration module configured to generate a configuration file based on the hardware settings and the requirements data set, and

[0051] - a universal control module, said universal control module being part of said hardware arrangement, wherein said universal control module is configurable by downloading said configuration file,

[0052] The client module is configured to approve the hardware settings and / or trigger the transmission of the configuration file to the universal control module.

[0053] Optionally, the client module may be installed on a mobile device.

[0054] Optionally, the system may further include a monitoring module connectable to the universal control module via the network to receive monitoring and performance data from the universal control module.

[0055] Optionally, the hardware setup may include a pump assembly, wherein the universal control module is mounted in an electronics housing of the pump assembly.

[0056] Optionally, the hardware setup may include at least one sensor unit having a communication link with the universal control module, wherein the configuration file includes sensor control parameters associated with the at least one sensor unit.

[0057] Optionally, the configuration file may include identification information of hardware components of the hardware setup.

[0058] Optionally, the configuration file may include hardware address information in a bus communication link connecting hardware components of the hardware setup.

[0059] Optionally, the hardware setup may include a list of hardware components and instructions for connecting the hardware components of the hardware setup.

[0060] Optionally, the demand data may include at least one of a demand group, the group including:

[0061] - water treatment purposes,

[0062] - the type of chemical to be dispensed or delivered,

[0063] - the expected volume or flow rate of fluid to be processed, and

[0064] - Installation parameters, specifically height difference, conduit length, location of feed ports and fluid pressure.

[0065] Optionally, the setup module may be further configured to determine the required type and / or number of pumps in the hardware setup based on the required flow rate of the fluid to be processed.

[0066] Optionally, the universal control module can be customized as a specific control module based on controller setting parameters in a configuration file.

[0067] Optionally, the configuration file may include at least one of a group of operating parameters, the group comprising:

[0068] - Feed pressure,

[0069] -Dose mass flow rate,

[0070] - set point pressure,

[0071] - set point flow,

[0072] - set point temperature,

[0073] - Controller setting parameters,

[0074] - connection table,

[0075] -Communication and / or network parameters.

[0076] Optionally, the client module may be configured to display the hardware settings and receive user approval when displaying the hardware settings.

[0077] Optionally, the universal control module may also be configured to receive updates to the configuration file based on user commands and / or based on monitoring and performance data received by the monitoring module from the universal control module via the network.

[0078] Optionally, the client module may be configured to display assembly instructions for the hardware setup.

[0079] Optionally, the setting module may be further configured to provide two or more options for one or more hardware components of the hardware setting, and wherein the client module is configured to inquire about a selection of the options.

[0080] The above-described system may be implemented in the form of one or more computer devices having network access to and / or including at least a portion of a common software environment or virtual "ecosystem".

[0081] Various features of the disclosure are pointed out with particularity in the claims annexed hereto and forming a part thereof.For a better understanding of the disclosure, its operating advantages and specific objects attained by its uses, reference is made to the accompanying drawings and descriptive matter in which preferred embodiments of the disclosure are shown. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] Embodiments of the present disclosure will now be described by way of example with reference to the following drawings, in which:

[0083] Figure 1 is a schematic diagram of an example of a system for defining and configuring hardware settings for a fluid handling system according to the present disclosure;

[0084] Figure 2 is a schematic diagram of an example of a hardware setup for a fluid handling system according to the present disclosure; and

[0085] Figure 3a to Figure 3c is a schematic diagram of a simple example of a hardware setup of a fluid handling system according to the present disclosure and an excerpt from a corresponding configuration file. DETAILED DESCRIPTION

[0086] Figure 1 The hardware setup 2 for defining and configuring a fluid handling system is shown (see Figure 2 ) in the form of a virtual "ecosystem". System 1 may include a user realm 3 and a provider realm 5. User realm 3 may include one or more computer devices connected by wire or wireless means accessible by a user, such as a personal computer 7 and / or a mobile device 9 (e.g., a smart phone or tablet device). Provider realm 5 may include one or more computer devices of a provider, such as a personal computer and / or a database server. User realm 3 and provider realm 5 may be communicatively connected via a network 11 (e.g., the Internet). Some parts of system 1 may be implemented in a network cloud 13, i.e., neither in user realm 3 nor in provider realm 5. Such cloud-based part 13 may be communicatively connected to user realm 3 and / or provider realm 5 via a network 11 (e.g., the Internet).

[0087] The user domain 3 of the system 1 includes a client module 15, which can be accessed by and / or implemented in an application on the user's PC 7 and / or mobile device 9. After starting 101 the client module 15, the user can use the client module 15 (preferably, at a fairly high level) to formulate 103 a question, request or need for the fluid treatment system. For example, the user may need to "disinfect a 500 liter water flow per hour". The client module 15 can provide a text field for the user to enter a free query and / or provide questions, option lists and / or other guidance to formulate the query. The formulated query includes a set of demand data for the fluid treatment system as input by the user.

[0088] The provider domain 5 of the system 1 comprises a server module 17 for receiving 105 a requirement data set from the client module 15 via the network 11. Furthermore, the provider domain 5 of the system 1 comprises a setup module 19 for defining 107 a hardware setup 2 of the fluid treatment system based on the requirement data set and the stored catalog data. The catalog data may be stored on a database 21 in the provider domain 5 of the system 1. Figure 1 As depicted, the database 21 is connected to a server module 17, which forwards the requirements data and the catalog data to a connected setup module 19. The provider domain 5 of the system 1 also includes a configuration module 23, which is used to generate 109 a configuration file 25 based on the hardware settings 2 and the requirements data set. The server module 17, the setup module 19 and / or the configuration module 23 can be implemented as a software component and / or a hardware component on at least one computer device in the provider domain 5 of the system 1. In particular, the setup module 19 and / or the configuration module 23 can be a software component implemented on a computer device in the provider domain 5 of the system 1. The output of the setup module 19 can be a hardware setup in the form of a "Bill of Materials" (BoM) 27, i.e., an order list of hardware components ready to be shipped 115 to the user. The output of the configuration module 23 can be a configuration file 25.

[0089] The solution that satisfies the requirement data set may be presented 111 to the client module 15 in the user domain 3 of the system 1 via the network 11. The user may approve 113 or disapprove the proposed hardware setup by corresponding input into the client module 15. Disapproval may result in the user changing or adding requirement data for redefining the hardware setup. In case of approval of the proposed hardware setup 2, the components of the hardware setup 2 according to the BoM 27 may be shipped 115 to the user. One of the components of the hardware setup 2 is a universal control module 29. For example, the universal control module 29 may be installed in an electronics box that is part of or attached to a metering pump 31 of the hardware setup 2. Before or after the hardware setup 2 is shipped 115 to the user domain 3, a configuration file 25 may be transmitted 116 to the universal control module 29 for configuring the fluid treatment system. Preferably, the user may receive the configuration file 25 through the client module 15 and upload 116 the configuration file 25 to the universal control module 29 after shipping 115. Alternatively or additionally, the universal control module 29 may be configured to download 116 the configuration file 25 from the provider domain 5 of the system 1 after shipping 115. Such downloading may be triggered automatically or upon user input at the client module 15.

[0090] The user domain 3 may include an office section 33 and a workshop section 35. Processing 103 of question inquiries and order approvals 113 using the client module 15 may be performed in the office section 33 of the user domain 3, while receiving, assembling 117, and operating 119 the shipped hardware setup 2 may be performed at the workshop section 35 of the user domain 3. Thus, at the workshop section 35 of the user domain 3, the user may receive the shipped hardware setup 2 and preferably customized assembly instructions 34. The assembly instructions 34 may be displayed to the user by the client module 15. The assembly instructions 34 may be personalized and customized to the user's preferences editable by the user using the client module 15. The assembly instructions 34 may be customized to the specific hardware setup 2 shipped 115 to the user.

[0091] Once the user has assembled 117 the hardware setup 2 with the help of the assembly instructions 34 displayed by the client module 15, the universal control module 29 is able to test the correct assembly by using the configuration file 25. The configuration file 25 may include a connection table of the hardware components and / or communication and network parameters. Thus, the universal control module 29 is able to check whether the hardware setup 2 has been correctly assembled 117, for example, whether the hardware components have been correctly connected. Because the configuration file 25 may include controller setting parameters that allow the operation of the fluid treatment system to begin immediately, the user does not need to manually configure the hardware setup 2.

[0092] The operation 119 of the fluid handling system may be monitored 121 permanently, periodically, or occasionally. The cloud-based monitoring module 37 may have all information of the hardware setup 2 and the current configuration file 25 loaded at the universal control module 29. The universal control module 29 may directly or indirectly communicate via, for example, Figure 1 The client module 15 shown communicates 123 the performance data to the monitoring module 37. The user can use the client module 15 or another computer device 39 to display and / or analyze the performance data. The monitoring module 37 can be configured to analyze the performance data and compare it with the demand data set by the user via the client module 15. If certain standards are no longer met, for example due to hardware degradation, scaling, material wear, sensor failure, filter clogging or other reasons, certain maintenance, repair and / or hardware replacement actions can be suggested to the user. Depending on the severity and / or urgency of the fault or malfunction, the client module 15 can be configured to obtain the user's attention through a visual alarm and / or an audible alarm. For minor adaptations or optimizations of the fluid treatment system to improve performance, the configuration file 25 can be updated, for example, including new controller setting parameters. In addition, in the case of adding a new compatible product to the catalog data in the provider domain 5, if better performance or further functional features can be added to the hardware setting 2, this new product can be suggested to the user. In order to prove this better performance or useful new functional features to the user, the cloud-based monitoring module 37 can analyze the performance data of other systems.

[0093] Figure 2 An example of a hardware setup 2 after assembly 117 at a workshop section 35 in a user domain 3 of a system 1 is shown. The hardware setup 2 comprises a first metering pump 31, which comprises a control module 29, which is within an electronics housing arranged at a lower part of the metering pump 31. The first metering pump 31 with the control module 29 serves as a master component for controlling a bus communication link 41 to other components of the hardware setup 2. These other components of the hardware setup 2 include a second metering pump 43, a circulation pump 45, an electric valve 47, a dual pump control unit 49, and five different sensors 51, 53, 55, 57, 59. A first sensor 51 (e.g., a first pressure sensor) is directly connected to the first metering pump 31. A second sensor 53 (e.g., a temperature sensor) is connected to the bus communication link 41. A fourth sensor 57 (e.g., a second pressure sensor) is directly connected to the second metering pump 43. A fifth sensor 59 (e.g., a flow meter) is directly coupled to the dual pump control unit 49. Each of the second metering pump 43 , the circulation pump 45 , the electric valve 47 and the dual pump control unit 49 is connected to the bus communication link 41 .

[0094] The control module 29 is also configured to communicate with a Supervisory Control and Data Acquisition (SCADA) system 61 by using the Common Interface Model (CIM) as a communication standard, wherein data may be exchanged in XML format. Figure 1 The client module 15 on the mobile device 9, the cloud-based monitoring module 37 and / or other computer device 39 may be part of the SCADA system 61 or separate therefrom (e.g. Figure 2 shown).

[0095] Figure 3a A simplified example of a hardware setup 2 is shown to explain how the control module 29 “knows” the correct hardware setup 2 . Figure 3b A corresponding excerpt of a configuration file in human readable XML format that is transmitted 116 or downloaded 116 to the control module 29 is shown. Figure 3b In <system>(<system>)) includes a dosing pump 31 identified in the configuration file as component type "DOSINGPUMP" and identifier "H". The dosing pump 31 includes a connector "A" of type "BACKBONE" and a component of type "E-BOX" with identifier "I". The control module 29 is installed in an electronic box (i.e., e-box) below the dosing pump 31. The hardware setup 2 also includes a component 63 of type "T-SPLITTER" with identifier "B". The T-splitter 63 has three connectors "B1", "B2" and "B3", of which "B1" and "B2" are trunk connectors and B3 is a so-called "MODBUS" connector, which is connected to a further hardware component with identifier "K", in the form of a pH sensor 65 with a Modbus connector "C". The trunk connectors "B1" and "B2" of the T-type splitter 63 are connected to two cable assemblies 67, 69 of the "trunk" type and identifiers "C1" and "C3", respectively. The two trunk cables 67, 69 form a Figure 2 The bus communication link 41 is shown. A first trunk cable 67, identified as "C1", connects the connector "A" of the metering pump 31 to the trunk connector "B1" of the T-splitter 63 (i.e., "B"). A second trunk cable 69, identified as "C3", connects the trunk connector "B1" of the T-splitter 63 (i.e., "B") to another hardware component in the form of a terminator 71 having an identifier "D" and a trunk connector "D1". The modbus connector "C" of the pH sensor 65 (i.e., "K") is connected to the modbus connector "B3" of the T-splitter 63 (i.e., "B") via another hardware component in the form of a "MODBUS" cable 73 identified as "C2".

[0096] If Hardware Setup 2 is not as Figure 3b If the hardware configuration file 2 is installed exactly as defined by the configuration file shown, the control module 29 can recognize the incorrect configuration and can communicate any incorrect connection or hardware components to the client module 15 (e.g., on the mobile device 9). Once the assembled hardware configuration 2 corresponds to Figure 3b The configuration file shown in the figure can be Figure 3c The controller configuration extract of the configuration file shown is used to configure the control module 29. The closed-loop control type is here "PID" identified as "DESINFECTION". This means that the originally generic control module 29 is now specifically configured to operate as a proportional-integral-derivative controller (PID) controller for disinfection. The feedback value for the closed-loop control is provided by the pH sensor 65, based on which the metering pump 31 is closed-loop controlled to pump disinfectant into the fluid treatment system. Since the configuration file is generated 109 by the configuration module 23 in the provider domain 5 based on the demand data received 105 from the user on the one hand and on the hardware setup 2 on the other hand, the controller setting parameters "P", "I" and "D" are preset by the configuration file to meet the user's needs. The user does not need to manually configure the controller nor does he need to adjust the controller setting parameters according to the specific hardware setup 2.

[0097] like Figure 2 As already indicated in the Hardware Setup 2, Figure 3a to Figure 3c . Correspondingly, the assembly and configuration of the hardware setup 2 can be a complex task. Therefore, the present disclosure adds significant value to the user in terms of convenience, time and effort, error reduction, maintenance and control for assembly and configuration.

[0098] When reference is made in the foregoing description to integers or elements that have known, obvious or foreseeable equivalents, then such equivalents are included herein as if individually set forth. Reference should be made to the claims for determining the true scope of the present disclosure, which should be interpreted to encompass any such equivalents. The reader will also understand that integers or features described as optional, preferred, advantageous, convenient, etc. are optional and do not limit the scope of the independent claims.

[0099] The above embodiments are to be understood as illustrative examples of the present disclosure. It is to be understood that any feature described with respect to any one embodiment may be used alone or in combination with other features described, and may also be used in combination with one or more features of any other embodiment, or in combination with any combination of any other embodiment. Although at least one exemplary embodiment has been shown and described, it should be understood that other modifications, substitutions, and variations are obvious to those of ordinary skill in the art and may be varied without departing from the scope of the subject matter described herein, and this application is intended to cover any adaptation or variation of the specific embodiments discussed herein.

[0100] Furthermore, "comprising" does not exclude other elements or steps, and "a" or "an" does not exclude a plurality. Furthermore, a feature or step that has been described with reference to one of the above exemplary embodiments may also be used in combination with other features or steps of the other above-mentioned exemplary embodiments. The method steps may be applied in any order or in parallel, or may constitute a part of or a more detailed version of another method step. It should be understood that all such modifications that reasonably and properly fall within the scope of contribution to the art should be implemented within the scope of the patent secured hereby. Such modifications, substitutions and alternatives may be made without departing from the spirit and scope of the disclosure, which should be determined by the appended claims and their legal equivalents.

[0101] While particular embodiments of the disclosure have been shown and described in detail to illustrate the application of the principles of the disclosure, it will be understood that the disclosure may be embodied in other ways without departing from those principles.

[0102] List of reference numerals:

[0103] 1 System

[0104] 2 Hardware Setup

[0105] 3 User Areas

[0106] 5 Provider Domain

[0107] 7 Computer Devices

[0108] 9 Mobile Devices

[0109] 11 Network

[0110] 13 Network Cloud

[0111] 15 Client Module

[0112] 17 Server Module

[0113] 19 Setting Module

[0114] 21 Database

[0115] 23 Configuration Module

[0116] 25 Configuration Files

[0117] 27 Bill of Materials (BoM)

[0118] 29 Universal Control Module

[0119] 31 First metering pump

[0120] 33 Office Section

[0121] 35 Workshop Section

[0122] 37 Monitoring module

[0123] 39 Computer device

[0124] 41 Bus connection link

[0125] 43 Second metering pump

[0126] 45 Circulation Pump

[0127] 47 Electric valve

[0128] 49 Dual Pump Controller

[0129] 51 First Sensor

[0130] 53 Second sensor

[0131] 55 Third sensor

[0132] 57 Fourth Sensor

[0133] 59 Fifth Sensor

[0134] 61 SCADA system

[0135] 63 T-type splitter

[0136] 65 pH Sensor

[0137] 67 First trunk cable

[0138] 69 Second trunk cable

[0139] 71 Terminal

[0140] 73 modbus cable

[0141] 101 Methods Start

[0142] 103 Handling User Input

[0143] 105 Receive demand data

[0144] 107 Define Hardware Settings

[0145] 109 Generate configuration file

[0146] 111 Display Hardware Settings

[0147] 113 Approval of hardware setup

[0148] 115 Shipping Hardware Setup

[0149] 117 Assembling the Hardware Setup

[0150] 119 Operation Hardware Setup

[0151] 121 Monitoring Hardware Settings

[0152] 123 Receive monitoring and performance data< / system>

Claims

1. A method for defining and configuring a hardware setup (2) of a fluid handling system, the method comprising: - processing (103) a user input at a client module (15), wherein the user input comprises a requirements data set for the fluid treatment system, - receiving (105) the requirement data set from the client module (15) at a server module (17), wherein the server module (17) is connected to the client module (15) via a network (11), - defining (107) the hardware settings (2) of the fluid treatment system by a settings module (19) based on the requirements data set and stored catalogue data, - generating (109) a configuration file (25) by a configuration module (23) based on said hardware settings (2) and said requirements data set, - approving (113) said hardware settings (2) by said client module (15), and - transmitting (116) the configuration file (25) to a universal control module (29) for configuring the fluid handling system, the universal control module (29) being part of the hardware setup (2).

2. The method according to claim 1, further comprising: Monitoring and performance data is received (123) at a monitoring module (37) from the universal control module (29) via the network (11).

3. The method according to claim 1 or 2, wherein: The hardware arrangement comprises a pump assembly (31), wherein the universal control module (29) is mounted in an electronics housing of the pump assembly (31).

4. A method according to any one of the preceding claims, wherein: The hardware setup (2) comprises at least one sensor unit (51, 53, 55, 57, 59) having a communication link with the common control module (29), wherein the configuration file comprises sensor setup parameters associated with the at least one sensor unit (51, 53, 55, 57, 59).

5. A method according to any one of the preceding claims, wherein: The configuration file (25) includes identification information of hardware components of the hardware setup (2).

6. A method according to any one of the preceding claims, wherein: The configuration file (25) includes hardware address information in a bus communication link (41) connecting hardware components of the hardware setup (2).

7. A method according to any one of the preceding claims, wherein: The hardware setup (2) comprises a list of hardware components and instructions for connecting the hardware components of the hardware setup (2).

8. The method according to any one of the preceding claims, in, The requirement data includes at least one of a requirement group, the group including: - water treatment purposes, - the type of chemical to be dispensed or delivered, - the expected volume or flow rate of fluid to be processed, and - Installation parameters, specifically height difference, conduit length, location of feed ports and fluid pressure.

9. A method according to any one of the preceding claims, wherein: Defining (107) the hardware setup (2) of the fluid treatment system includes determining the required type and / or number of pumps (31, 43, 45) in the hardware setup (2) based on a required flow rate of the fluid to be treated.

10. A method according to any one of the preceding claims, wherein: The configuration file (25) includes controller setting parameters to customize the general control module (29) to a specific control module defined by the controller setting parameters.

11. A method according to any one of the preceding claims, wherein: The configuration file (25) comprises at least one of a group of operating parameters, the group comprising: - Feed pressure, -Dose mass flow rate, - set point pressure, - set point flow, - set point temperature, - Controller setting parameters, - connection table, -Communication and / or network parameters.

12. A method according to any one of the preceding claims, wherein: Approving (113) the hardware settings (2) by the client module (15) includes displaying (111) the hardware settings (2) at the client module (15) and receiving approval of the displayed hardware settings (2).

13. The method according to any one of the preceding claims, further comprising: The configuration file (25) is updated according to user commands and / or according to monitoring and performance data received by the monitoring module (37) from the universal control module (29) via the network (11).

14. The method according to any one of the preceding claims, further comprising: Assembly instructions (34) for the hardware setup (2) are displayed.

15. A method according to any one of the preceding claims, wherein: Defining (107) the hardware setup (2) includes providing two or more options for one or more hardware components of the hardware setup (2), and querying (111) at the client module (15) for a selection of the options.

16. A system (1) for defining and configuring a hardware setup (2) of a fluid handling system, the system comprising: - a client module (15) configured to process user input, said user input comprising a requirement data set for said fluid treatment system, - a server module (17) connectable to said client module (15) via a network (11) to receive said requirement data set from said client module (15), a settings module (19) configured to define the hardware settings (2) of the fluid treatment system based on the requirements data set and stored catalogue data, - a configuration module (23) configured to generate a configuration file (25) based on the hardware settings (2) and the requirement data set, and - a universal control module (29) being part of said hardware arrangement (2), wherein said universal control module (29) is configurable by downloading said configuration file (25), The client module (15) is configured to approve the hardware settings (2) and / or trigger the transmission of the configuration file (25) to the universal control module (29).

17. The system (1) according to claim 16, wherein: The client module (15) is installed on the mobile device (9).

18. The system (1) according to claim 16 or 17, further comprising a monitoring module (37) connectable to the common control module (29) via the network (11) to receive monitoring and performance data from the common control module (29).

19. The system (1) according to any one of claims 16 to 18, wherein: The hardware arrangement (29) comprises a pump assembly (31), wherein the universal control module (29) is mounted in an electronics housing of the pump assembly (31).

20. The system (1) according to any one of claims 16 to 19, wherein: The hardware setup (2) comprises at least one sensor unit (51, 53, 55, 57, 59) having a communication link with the common control module (29), wherein the configuration file (25) comprises sensor control parameters associated with the at least one sensor unit (51, 53, 55, 57, 59).

21. The system (1) according to any one of claims 16 to 20, wherein: The configuration file (25) includes identification information of hardware components of the hardware setup (2).

22. The system (1) according to any one of claims 16 to 21, wherein: The configuration file (25) includes hardware address information in a bus communication link (41) connecting hardware components of the hardware setup (2).

23. The system (1) according to any one of claims 16 to 22, wherein: The hardware setup (2) comprises a list of hardware components and instructions (34) for connecting the hardware components of the hardware setup (2).

24. System (1) according to any one of claims 16 to 23, in, The requirement data includes at least one of a requirement group, the group including: - water treatment purposes, - the type of chemical to be dispensed or delivered, - the expected volume or flow rate of fluid to be processed, and - Installation parameters, specifically height difference, conduit length, location of feed ports and fluid pressure.

25. The system (1) according to any one of claims 16 to 24, wherein: The setup module (19) is further configured to determine the required type and / or number of pumps (31, 43) in the hardware setup (2) based on the required flow rate of the fluid to be processed.

26. The system (1) according to any one of claims 16 to 25, wherein: The universal control module (29) can be customized as a specific control module (29) based on the controller setting parameters in the configuration file (25).

27. The system (1) according to any one of claims 16 to 26, wherein: The configuration file (25) comprises at least one of a group of operating parameters, the group comprising: - Feed pressure, -Dose mass flow rate, - set point pressure, - set point flow, - set point temperature, - Controller setting parameters, - connection table, -Communication and / or network parameters.

28. The system (1) according to any one of claims 16 to 27, wherein: The client module (15) is configured to display the hardware settings (29) and receive user approval when displaying the hardware settings (2).

29. The system (1) according to any one of claims 16 to 28, wherein: The universal control module (29) is further configured to receive updates to the configuration file (25) based on user commands and / or based on monitoring and performance data received by the monitoring module (37) from the universal control module (29) via the network (11).

30. The system (1) according to any one of claims 16 to 29, wherein: The client module (15) is configured to display assembly instructions (34) for the hardware setup (2).

31. The system (1) according to any one of claims 16 to 30, wherein: The setup module (19) is further configured to provide two or more options for one or more hardware components of the hardware setup (2), and wherein the client module (15) is configured to inquire about a selection of the options.

Images