Dynamically create unit control graphical user interface and unit control logic

The graphical setup wizard allows users to dynamically generate unit dashboards and control logic, solving the complex unit configuration problems in existing technologies and achieving a simplified, user-friendly configuration process.

CN114691262BActive Publication Date: 2026-11-17TRANE INTERNATIONAL INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202111646848.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-12-30
Filing Date
2021-12-29
Publication Date
2026-11-17
Estimated Expiration
2041-12-29

AI Technical Summary

Technical Problem

Existing building automation systems require extensive specialized knowledge and involve complex configuration processes when generating graphical user interfaces and control logic for unit control, making it difficult to achieve user-friendly dynamic generation and editing.

Method used

The graphical setup wizard guides users to select unit type, configure unit components and parameters, and dynamically generates unit dashboards and control logic, simplifying the user configuration process, including unit sequence definition, programming and control point mapping.

Benefits of technology

It simplifies unit configuration and control logic generation without requiring specific unit library knowledge, improving user experience and configuration efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114691262B_ABST
    Figure CN114691262B_ABST
Patent Text Reader

Abstract

A method and system are provided for dynamically generating or editing graphical dashboards via graphical user interface (GUI) settings. The method includes: determining a unit type via GUI settings; determining a unit configuration via GUI settings; determining at least one component of the unit via GUI settings; and configuring parameters of at least one component and / or the unit via GUI settings. The method further includes: generating a dashboard including unit control logic based on the type, configuration, at least one component, and parameters of at least one component and / or the unit. The method also includes: controlling the unit based on the unit control logic.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to building automation systems. More specifically, this disclosure relates to systems and methods for dynamically generating unit control graphical user interfaces (GUIs) and control logic via a graphical setup wizard for a building automation system. Background Technology

[0002] Building automation systems are used to coordinate, manage, and automatically control various environmental, physical, and electrical building subsystems, particularly heating, ventilation, air conditioning, and refrigeration (HVACR) systems and climate control, which may also include security, lighting, and electrical systems. HVACR systems may include, for example, rooftop units to provide conditioned air to air distribution systems that include ductwork. In HVACR systems, conditioned air is delivered to the building or occupied spaces. The air handling unit portion of an air handling unit or air conditioning unit used to meet the building's HVACR requirements typically includes a heat transfer loop system housed within a metal plate enclosure. The heat transfer loop may include one or more compressors, condensers, evaporators, fans, filters, dampers, and various other devices. The compressor, condenser, expansion unit, and evaporator are fluidly connected. Summary of the Invention

[0003] This disclosure generally relates to building automation systems. More specifically, this disclosure relates to systems and methods for dynamically generating unit control GUIs and control logic via a graphical setup wizard for a building automation system.

[0004] The embodiments disclosed herein provide visual assistance to guide users in configuring units by selecting or configuring unit types, unit configurations, unit components, unit sequences, and unit parameter configurations. After completing the graphical setup wizard, graphical dashboards and unit control logic can be dynamically created for the user. The unit's graphical dashboard includes unit components such as pumps, valves, pipelines, chillers, boilers, etc. The control logic includes operational controls or operational logic associated with the corresponding components. Furthermore, after completing the graphical setup wizard, a graphical dashboard can be dynamically created for the user, including visualizations of key performance indicators (KPIs) and / or interactive unit diagrams with real-time values ​​(e.g., measured / sensed parameter values ​​such as temperature, pressure, humidity, etc.) for interaction with the unit. The embodiments disclosed herein simplify the process for users, such as defining unit sequences, programming unit sequences, creating custom graphics for units, and / or mapping control points to custom graphics of units, without requiring specific knowledge of a unit library.

[0005] A method for dynamically generating or editing a generator set dashboard via a GUI is disclosed. The method includes: determining the generator set type via GUI settings; determining the generator set configuration via GUI settings; determining at least one component of the generator set via GUI settings; and configuring at least one component and / or parameters of the generator set via GUI settings. The method further includes: generating a generator set dashboard including generator set control logic based on the generator set type, configuration, at least one component, and parameters of the at least one component. The method also includes: controlling the generator set based on the generator set control logic.

[0006] A building automation system (BAS) is disclosed. The system includes at least one unit associated with at least a space, system, or subsystem of at least a portion of a building or campus. The system also includes a controller and GUI settings. The GUI settings are configured to generate or edit a unit dashboard, including unit control logic, based on unit type, unit configuration, at least one component of the unit, and parameters of that component. The controller is configured to control the unit based on the unit control logic. Attached Figure Description

[0007] Reference is made to the accompanying drawings, which form part of this disclosure and illustrate embodiments in which the systems and methods described herein may be practiced.

[0008] Figure 1 A schematic diagram of a building automation system according to an embodiment is shown.

[0009] Figure 2 A schematic diagram of a building automation system controller according to an embodiment is shown.

[0010] Figure 3 A schematic diagram of the unit according to an embodiment is shown.

[0011] Figures 4 to 8 A graphical user interface for the setup wizard according to an embodiment is shown.

[0012] Figure 9A and Figure 9B A graphical dashboard generated via a setup wizard according to an embodiment is shown.

[0013] Figure 10A and Figure 10B The embodiments shown can be illustrated as follows: Figure 9B A list of KPIs, which is part of the KPIs.

[0014] Figure 11 A flowchart is shown for a method for dynamically generating a graphical dashboard via a setup wizard, according to an embodiment.

[0015] The same reference numerals in the figures denote the same parts throughout the text. Detailed Implementation

[0016] In the following detailed description, reference is made to the accompanying drawings, which form a part of the description. In the drawings, similar symbols generally identify similar parts unless the context otherwise requires. Furthermore, unless otherwise stated, the description of each successive drawing may refer to features from one or more prior drawings to provide a clearer context and a more substantial explanation of the current exemplary embodiment. Moreover, the exemplary embodiments described in the detailed description, drawings, and claims are not intended to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter set forth herein. It will be readily understood that aspects of this disclosure, as generally described herein and illustrated in the drawings, can be arranged, substituted, combined, separated, and designed in a variety of different configurations, all of which are expressly contemplated herein.

[0017] The following definitions apply throughout this disclosure. As defined herein, the term "Building Automation System" or "BAS" can refer to a system for coordinating, managing, and automatically controlling various environmental, physical, and electrical building subsystems, particularly HVACR systems and climate control, and may also include security, lighting, power, etc. It will be understood that different embodiments of a BAS are described in U.S. Patent 10,269,235, the entire contents of which are incorporated herein by reference.

[0018] As defined herein, the term "plant" can refer to a group of devices or components (e.g., one or more compressors, condensers, chillers, pumps, piping, switchboards, wiring, valves, fans, thermostats, cooling towers, air handling units, piping systems, etc.) used for generating and networking fluids (e.g., liquids such as water, gases such as air, etc.) for cooling, heating, or regulating fluids (e.g., liquids such as water, gases such as air, etc.). Plants can be water chillers (chilled water and / or hot water), boiler units, simultaneous heating and / or cooling units, air chillers, etc. In embodiments, a plant may have one or more air-cooled condensers or one or more cooling towers connected, for example, via one or more fluid (liquid, gas, etc.) loops to one or more chillers. HVACR systems may include chillers (e.g., water chillers, air-cooled chillers, etc.). In embodiments, a chiller may include a motor and various compressor types, electronic cooling, bearings, air handlers, purifiers, evaporators, and condensers, etc. As defined herein, the term "one or more components" can refer to any equipment within a plant. The unit may include one or more "components," such as pumps (e.g., condenser pumps) that guide the flow of fluid in a fluid circuit, one or more flow control devices (e.g., valves, switches, etc.) that control the flow of fluid in a fluid circuit, lines (e.g., pipes) in the fluid circuit, one or more chillers, one or more boilers, one or more fans, etc. It will be understood that different embodiments of the unit are described in U.S. Patent 10,006,685, the entire contents of which are incorporated herein by reference.

[0019] As defined herein, the term "point" or "point of control" or "control point" can refer to a sensor input, control output, or control value (of a controller), which may have different characteristics depending on the manufacturer. In embodiments, the inputs and outputs of a controller may be referred to as the controller's control points. A "point" can refer to a control action, such as a sensing action (e.g., a sensor input), a control action (e.g., a control output), etc. For example, a point may include a temperature sensor input, the output of a proportional controller that operates a control valve, etc.

[0020] As defined herein, the terms “dynamically generate” or “dynamically create” can refer to creating or generating, for example, an output, such as a user interface (e.g., a GUI), based on actions such as selection, clicking, or data input on the current user interface. For example, when a user changes the configuration of a unit on the GUI (e.g., the number of chillers on a branch / branch of a fluid loop), the GUI can dynamically generate a graphical representation of the newly configured chillers on the branch / branch based on the changed configuration.

[0021] The embodiments disclosed herein provide a GUI setup wizard that prompts the user to select a unit type from a set of graphical representations of the unit layout upon startup (to help the user select the appropriate unit type to match the building's mechanical layout). After selecting the unit type, the setup wizard can prompt the user to configure the unit's equipment / components using additional graphical options. As the user progressively configures the unit, the setup wizard can present graphical illustrations of previously selected options and pose increasingly specific questions to the user based on their choices in previous steps / GUIs. The setup wizard can also guide the user's subsequent actions through graphical and / or other input mechanisms (e.g., command lines, drop-down lists, radio buttons, voice input, etc.) to help the user make appropriate selections. Once the setup wizard is completed, the unit control application / logic may have acquired all the knowledge required to configure and run a pre-designed unit control application, and, with all necessary calculations and control point mappings completed, a GUI with key performance indicators (KPIs) can be created using this application.

[0022] Specific embodiments of this disclosure are described herein in conjunction with the accompanying drawings; however, it will be understood that the disclosed embodiments are merely examples of this disclosure, which may be implemented in various forms. Well-known functions or constructions are not described in detail to avoid obscuring this disclosure with unnecessary detail. Therefore, the specific structural and functional details disclosed herein should not be construed as limiting, but only as the basis for the claims and as a representative basis for teaching those skilled in the art to apply this disclosure in various ways in any suitable detailed structure. In this specification and the accompanying drawings, the same reference numerals denote elements that can perform the same, similar, or equivalent functions.

[0023] The scope of this disclosure should be determined by the appended claims and their legal equivalents, and not by the examples given herein. For example, the steps set forth in any method claim may be performed in any order and are not limited to the order presented in the claims. Furthermore, unless specifically described herein as “critical” or “essential,” no element is essential to the practice of this disclosure.

[0024] Figure 1 A schematic diagram of a building automation system 100 according to an embodiment is shown. The BAS 100 includes a BAS controller 200 communicatively coupled to multiple building automation networks (BANs) 110, 120, and 130. BANs 110, 120, and 130 facilitate communication between the BAS controller 200 and any number of BAS terminal devices 111, 112, 121, and 131. Terminal devices 111, 112, 121, and 131 may include a range of HVACR devices, such as units (e.g., Figure 3The equipment includes refrigeration units, air processors, furnaces, or boilers, which have multiple data sensors that generate continuous data streams, variable air volume (VAV) boxes and dampers, temperature or humidity sensors for monitoring the space, etc. In embodiments, terminal devices include panels, sensors, controllers, microprocessor-controlled devices, converters, thermostats, furnaces, heating systems, refrigeration units, cooling systems, air conditioners, air filters, air purifiers, fire and life safety systems, security systems, alarm systems, occupancy sensors, electrical system monitors and controllers, lighting system monitors and controllers, ventilation system monitors and controllers, smoke sensors, light sensors, motion sensors, humidity sensors, pumps, air processors, fluid and air movement and handling equipment, terminal devices, life science and pharmacology control equipment and monitoring systems, positive pressure cleanrooms, negative pressure cleanrooms, industrial automation control equipment and systems, programmable logic controllers, etc.

[0025] BAS controller 200 includes a communication interface 201 that couples BAS controller 200 to BAN 110. BAN 110 includes a plurality of terminal devices 111 and a terminal device 112 coupled to BAN 110 using a media converter 113. Terminal devices 111, 112, and 121 may be, for example, refrigerators, air processors, furnaces, boilers, VAV boxes, dampers, temperature or humidity sensors, etc. BAS controller 200 also includes a communication interface 202 that couples BAS controller 200 to BAN 120. BAS controller 200 also includes a communication interface 203 that couples BAS controller 200 to BAN 130. BAN 130 includes terminal devices 131, such as temperature sensors, humidity sensors, CO2 sensors, etc. BAS controller 200 also includes a data network interface 204 for transmitting data to one or more user devices 141 via a data network 140 (such as a private LAN and / or the public Internet). User device 141 may include mobile phones, smartphones, tablets, smartwatches, pagers, laptops, and / or desktop computers. Remote server 160 is communicatively coupled to BAS controller 200 via data network 140 and stores information about multiple terminal devices, including information related to specific products, product versions, firmware versions, and / or software versions.

[0026] Figure 2A schematic diagram of a building automation system controller 200 according to an embodiment is shown. The BAS controller 200 includes a processor 210 operatively communicating with a memory 220, a user interface 230, and a data memory 240. The memory 220 includes RAM memory, which can be used for, for example, storing transient data, calculation results and intermediate results, I / O buffering, GUI buffering, program execution, and any other suitable purpose. The data memory 240 includes non-volatile memory such as flash memory drives, EEPROM, ROM, magnetic hard disks, solid-state drives (SSDs), and hybrid drives (combined hard disks / SSDs), which can be used to store data that persists through power cycling.

[0027] User interface 230 includes multiple elements that facilitate user input and display output to the user, and may include one or more of the following: buttons, switches, LED indicators, character displays such as liquid crystal displays (LCDs) or vacuum fluorescent displays (VFDs), graphic displays such as thin film transistor (TFT) displays, touch screen displays, etc.

[0028] Figure 3 A schematic diagram of a unit 300 according to an embodiment is shown. The unit 300 includes an HVACR unit (e.g., which may be or includes a chiller) 302 and a cooling tower 304 connected via a fluid loop 306. It will be understood that the cooling tower 304 may be optional. In another embodiment, the unit (e.g., an air-cooled chiller unit) may not have a cooling tower, but instead has a condenser. The cooling tower 304 includes a fan 318 connected to a motor 320. In an embodiment, the HVACR unit 302 may be a water-cooled chiller. The fluid loop 306 has a condenser fluid supply side (e.g., a chilled water side) 308 and a condenser fluid return side (e.g., a hot water side) 310. The fluid loop 306 includes a pump 312 for pumping fluid (e.g., water) through the fluid loop 306. For example, the pump 312 may be a condenser pump, which operates to direct cooled fluid from the cooling tower 304 to the condenser side 314 of the HVACR unit 302 via the condenser fluid supply side 308. Pump 312 (e.g., condenser pump) has motor 316. It will be understood that unit 300 may have multiple chillers, multiple cooling towers (or multiple fans and / or multiple units), multiple fluid circuits, multiple boilers and / or multiple pumps, etc.

[0029] Unit 300 includes a controller 322. An example of controller 322 is a computer including a processor 324 and a non-transitory memory 326 communicating with the processor 324. In some embodiments, controller 322 is (or includes, or may be connected to) a dedicated computer specifically configured to perform the methods disclosed herein. Non-transitory memory 326 stores computer-readable instructions 328 executable by processor 324. Computer-readable instructions 328 are one or more methods for controlling one or more components of unit 300.

[0030] In an embodiment, the controller 322, operated according to executed computer-readable instructions 328, communicates with other components, such as one or more sensors (or detectors) for detecting temperature and / or pressure at various points, for example, within the unit 300. In an embodiment, the controller 322 (or Figure 2 The controller 200 (or any other suitable controller) may include computer-readable instructions 328 to perform a method for dynamically generating or editing a unit dashboard with unit control logic via a GUI setup wizard.

[0031] Figures 4 to 8 A graphical user interface (GUI) for a setup wizard according to an embodiment is illustrated. It will be understood that the GUIs disclosed herein (e.g., frames, buttons, checkboxes, text fields, drop-down lists, etc.) are exemplary and for descriptive purposes only, and not limiting. Any component of the GUI (e.g., frames, buttons, checkboxes, text fields, drop-down lists, etc.) may be replaced by other suitable components of the GUI without departing from the spirit or scope of the subject matter set forth herein. It will also be understood that the controller disclosed herein, or any other suitable controller, may be configured to run the setup wizard, and the GUI of the setup wizard may be displayed by the controller on an output device (e.g., a display device). In embodiments, the setup wizard may be a configuration tool (e.g., a software application) for, for example, editing a generated unit dashboard.

[0032] Figure 4 A GUI 400 for a setup wizard according to an embodiment is shown. GUI 400 may be the first GUI when the setup wizard is launched. In an embodiment, GUI 400 may be a framework including a title 430, an information button 440, a field 410, a checkbox 420, a button 450, etc.

[0033] exist Figure 4In this document, heading 430 may include the text "Creating a Refrigeration Unit - Defining a Refrigeration Unit". It will be understood that the text disclosed herein can be any suitable text. It will also be understood that the embodiments described and illustrated herein are not limited to refrigeration units. That is, the units described and illustrated herein are provided for descriptive purposes only and are not intended to be limiting. Units may be water chillers (chilled water and / or hot water), boiler units, simultaneous heating and / or cooling units, air chillers, etc.

[0034] Information button 440 is configured to display information that helps in understanding the components of GUI 400 when the information button 440 is clicked (e.g., in a pop-up dialog box independent of GUI 400).

[0035] Field 410 includes a label “Name”, a text field for entering the unit name, a label “Description”, and a text field for entering a detailed description of the unit.

[0036] Checkbox 420 includes multiple checkboxes and their respective descriptions. Deselecting a checkbox, or selecting one or more checkboxes, can generate unit control logic that disables or enables predetermined features. For example, in an embodiment, a checkbox may include "Use the chiller unit to start and stop the system chilled water pumps." Selecting such a checkbox can generate a chiller unit (e.g., a graphical dashboard) with unit control logic capable of starting and stopping the system chilled water pumps. Deselecting such a checkbox can generate a chiller unit (e.g., a graphical dashboard) with unit control logic that cannot start and stop the system chilled water pumps.

[0037] Button 450 includes a "Cancel" button (configured to cancel the setup wizard's execution when clicked) and a "Next" button (configured to navigate the current GUI (e.g., 400) of the setup wizard to the next GUI (e.g., ...). Figure 5 (500). It will be understood that the text on button 450 can be any suitable text. In this embodiment, the "Next" button is disabled (not enabled) until the required input (e.g., the name of the chiller unit) is entered.

[0038] Figure 5 A setup wizard GUI 500 according to an embodiment is shown. In an embodiment, the GUI 500 may be a frame that includes a title 530, radio buttons (510, 511, 512, 513), graphics group types (520, 521A, 521B, 522, 523), buttons 550, and information buttons 540.

[0039] exist Figure 5In the document, heading 530 includes the text “Creating a Chiller Unit - Selecting a Chiller Unit Type”. It will be understood that the text disclosed herein can be any suitable text. Radio buttons (510, 511, 512, 513) include radio button 510 (with the text “Constant Flow - Water always flows through all chillers”), radio button 511 (with the text “Stepped Flow - Water only flows through operating chillers”), radio button 512 (with the text “Variable Primary Flow - Variable water flow through chillers and system”), and radio button 513 (with the text “Decoupling (Primary-Secondary) - Water only flows through chillers at a constant rate while they are running. Excess primary flow is bypassed via a bypass pipe”).

[0040] The graphic unit type 520 (e.g., a constant flow unit type, where fluid always flows through all the chillers in the unit) is located below its corresponding radio button 510. Unit type 520 includes chillers, pumps, loads, and a fluid loop indicating the direction of fluid flow (see arrows).

[0041] Graphical unit types 521A and 521B (e.g., stepped flow unit types, where fluid flows only through the chillers operating within the unit (e.g., chillers that are running and / or switched on and / or have open valves)) are positioned below their corresponding radio buttons 511. Unit type 521A includes chillers, each with a dedicated pump, load, and fluid circuits indicating the direction of fluid flow (see arrows). Unit type 521B includes a chiller, pump, load, valves (each positioned upstream of the chiller relative to fluid flow), and fluid circuits indicating the direction of fluid flow (see arrows). The valves can be any suitable flow control device (valve, switch, etc.) used to control the flow rate of fluid to each operating chiller.

[0042] The graphic unit type 522 (e.g., a variable main flow unit type, where variable fluid flows through the chiller and the system) is located below its corresponding radio button 512. Unit type 522 includes a chiller, a variable speed pump, a load with a valve located upstream of the load, a bypass valve connected in parallel with the load, and a fluid loop indicating the direction of fluid flow (see arrow). It will be understood that the bypass valve can be configured to regulate to maintain a minimum chiller flow rate.

[0043] Graphical unit type 523 (e.g., a decoupled unit type, where fluid flows through them at a constant rate only when the chiller is running, and excess main flow is bypassed via a bypass pipe) is located below its corresponding radio button 513. Unit type 523 includes a chiller, a chiller pump, a load having a valve located upstream of the load and a distribution pump located upstream of the valve, a bypass pipe connected in parallel with the load, and a fluid loop indicating the direction of fluid flow (see arrow).

[0044] It will be understood that other unit types may exist (not shown). It will be understood that the setup wizard may obtain multiple unit types from a library (e.g., a layout library or unit type library) pre-stored in the controller's memory, and display each unit type and its corresponding radio button in GUI 500.

[0045] Information button 540, when clicked, is configured to display information that helps in understanding the components of GUI 500. Button 550 includes a "Cancel" button (configured to cancel the setup wizard's execution when clicked) and a "Previous" button (configured to navigate the current GUI 500 of the setup wizard to the previous page / frame / GUI (e.g., ...) when clicked). Figure 4 The "400" and "Next" buttons are configured to navigate the current GUI of the setup wizard to the next GUI (e.g., when clicked) when the current GUI is 500. Figure 6A (600)).

[0046] During operation, users (e.g., technicians, building / BAS administrators, etc.) can select any of the radio buttons (510, 511, 512, 513, etc.) based on, for example, the mechanical unit layout of the building or BAS, to determine or select the unit type (e.g., 520, 521A / 521B, 522, 523, or other types). When the "Next" button is clicked, GUI500 changes to GUI 600.

[0047] It will be understood that the "Next" button can be disabled when no radio button (510, 511, 512, 513, etc.) is selected. When any of the radio buttons (510, 511, 512, 513, etc.) is selected, the "Next" button can be enabled, and components (such as drop-down lists) can be displayed next to the selected graphical unit type (520, 521A, 521B, 522, 523) in the same GUI 500 to allow, for example, the user to add or subtract methods (such as efficiency, temperature, and / or capacity, etc.) for the chiller unit (and its control logic) to be generated.

[0048] Figure 6A A setup wizard GUI 600 according to an embodiment is shown. In an embodiment, the GUI 600 may be a frame that includes a title 630, radio buttons (610, 611, 612, 613, 614, etc.), graphics group configurations (620, 621, 622, 623, 624), buttons 650 and / or information buttons 640.

[0049] exist Figure 6AIn this document, heading 630 includes the text "Create a chiller unit - Select chiller unit configuration". It will be understood that the text disclosed herein can be any suitable text. Radio buttons (610, 611, 612, 613, 614, etc.) include radio button 610 (with the text "Single chiller"), radio button 611 (with the text "Parallel (simple)"), radio button 612 (with the text "Series (simple)"), radio button 613 (with the text "Series pair"), and radio button 614 (with the text "Series parallel").

[0050] The graphic unit configuration 620 (e.g., a single chiller configuration) is located below its corresponding radio button 610. The unit configuration 620 includes piping for the chiller and fluid circuits.

[0051] The graphic unit configuration 621 (e.g., a chiller arranged in parallel) is located below its corresponding radio button 611. The unit configuration 621 includes a first chiller, a second chiller arranged in parallel with the first chiller, and piping for the fluid circuit.

[0052] A graphic unit configuration 622 (e.g., a chiller arranged in series) is located below its corresponding radio button 612. The unit configuration 622 includes a first chiller, a second chiller arranged in series with the first chiller, and piping for the fluid circuit.

[0053] A graphical unit configuration 623 (e.g., a series-connected chiller configuration) is located below its corresponding radio button 613. Unit configuration 623 includes a first chiller, a second chiller arranged in series with the first chiller, a third chiller, a fourth chiller arranged in series with the third chiller, and piping for a fluid circuit. The first and second chillers are arranged in parallel with the third and fourth chillers. It will be understood that the first and second chillers (or the third and fourth chillers) are dedicated to each other via their interconnecting piping. Within the first and second chiller (or the third and fourth chillers) group, fluid flows through the upstream chiller and then through the downstream chiller.

[0054] A graphic unit configuration 624 (e.g., a series-parallel arrangement of refrigerators) is located below its corresponding radio button 614. Unit configuration 624 includes a first compartment 624A (which includes a first, second, and third refrigerator arranged in parallel with each other), a second compartment 624B (which includes a fourth, fifth, and sixth refrigerator arranged in parallel with each other), and piping for fluid circuits. The first compartment 624A (first, second, and third refrigerators) and the second compartment 624B (fourth, fifth, and sixth refrigerators) are arranged in series. It will be understood that the first compartment 624A includes a set of parallel upstream refrigerators connected in series with the second compartment 624B, which includes a set of parallel downstream refrigerators. In an embodiment, fluid flows through any upstream refrigerator in the first compartment 624A as long as its associated valve is open, and then fluid flows through any downstream refrigerator in the second compartment 624B as long as its associated valve is open. In such embodiments, no upstream refrigerator is strictly paired with a particular downstream refrigerator.

[0055] It will be understood that other unit configurations may exist (not shown). It will be understood that the setup wizard may obtain multiple unit configurations from a library (e.g., a configuration library) pre-stored in the memory (e.g., the controller's) and display each unit configuration and its corresponding radio button in GUI 600.

[0056] Information button 640, when clicked, is configured to display information that helps in understanding the components of GUI 600. Button 650 includes a "Cancel" button (configured to cancel the setup wizard's execution when clicked) and a "Previous" button (configured to navigate the current GUI 600 of the setup wizard to the previous GUI when clicked, e.g., ...). Figure 5 The "500" and "Next" buttons are configured to navigate the current GUI of the setup wizard to the next GUI (e.g., 600) when clicked. Figure 7 700)).

[0057] It will be understood that the "Next" button can be disabled when no radio button (610, 611, 612, 613, 614, etc.) is selected. When any of the radio buttons (610, 611, 612, 613, 614, etc.) is selected, the "Next" button can be enabled, and the component can be displayed next to the selected graphics group type (620, 621, 622, 623, 624) in the same GUI 600 (see [link]). Figures 6B to 6E This allows users, for example, to further configure the refrigeration unit (and its control logic) to be generated.

[0058] In this embodiment, when radio button 610 (with the text "Single Refrigerator") is selected, the "Next" button is enabled.

[0059] In this embodiment, when radio button 611 (with the text "Parallel (Simple)") is selected, the "Next" button is enabled and displayed next to graphics configuration 621 in the same GUI 600. Figure 6B . Figure 6B The label “Number of Refrigeration Units” is shown, along with a text field for typing / entering the number of refrigeration units in the refrigeration unit to be generated. Figure 6B It also shows a label "Pump Configuration" and a drop-down list that offers "Dedicated Pump," "Manifold Pump," and "Pump-less" as options. It will be understood that if from... Figure 5 If the "Decoupled" unit type is selected, the label will be "Main Pump Configuration" instead of "Pump Configuration". When "Manifold Pump" is selected from the dropdown list, Figure 6B The label “Number of pumps in the manifold” and the text field for typing / entering the number of pumps are further shown.

[0060] In this embodiment, when radio button 612 (with the text "Chain (Simple)") is selected, the "Next" button is enabled and displayed next to graphics configuration 622 in the same GUI 600. Figure 6C . Figure 6C The label “Number of Refrigeration Units” is shown, along with a text field for typing / entering the number of refrigeration units in the refrigeration unit to be generated.

[0061] In this embodiment, when radio button 613 (with the text "Chain Pair") is selected, the "Next" button is enabled and displayed next to graphics configuration 623 in the same GUI 600. Figure 6D . Figure 6D The label “Number of Serial Pairs” and a text field are shown for typing / entering the number of chiller pairs in the chiller unit to be generated. Figure 6D It also shows a label "Pump Configuration" and a drop-down list that offers "Dedicated Pump," "Manifold Pump," and "Pump-less" as options. It will be understood that if from... Figure 5 If the "Decoupled" unit type is selected, the label will be "Main Pump Configuration" instead of "Pump Configuration". When "Manifold Pump" is selected from the dropdown list, Figure 6D The label “Number of pumps in the manifold” and the text field for typing / entering the number of pumps are further shown.

[0062] In an embodiment, when radio button 614 (with the text "Serial Parallel") is selected, a widget (e.g., text and / or arrows) can be displayed to indicate the compartments (624A, 624B), and shown next to the graphics unit configuration 624 in the same GUI 600. Figure 6E . Figure 6E The text field shows the label "Number of Cabins", a text field for typing / entering the number of cabins in the refrigeration unit to be generated, and an "Apply" button. Figure 6E It also shows a label "Number of Refrigeration Units in Cabin 1" and a text field for typing / entering the number of refrigeration units in the first cabin, and a label "Number of Refrigeration Units in Cabin 2" and a text field for typing / entering the number of refrigeration units in the second cabin. When the cabin number is entered and the "Apply" button is clicked, Figure 6E The system further displays a label indicating a dynamic update of the number of refrigeration units in the compartment, and displays a text field in the same GUI 600 for typing / entering the dynamic update of the number of refrigeration units in such compartments based on the number of compartments entered, and enables the "Next" button.

[0063] During operation, users can select any of the radio buttons (610, 611, 612, 613, 614, etc.) based on, for example, the chiller configuration, to determine or select a chiller configuration (e.g., 620, 621, 622, 623, 624, or other configurations). When the "Previous" button is clicked, GUI 600 changes back to... Figure 5 The GUI is 500. When the "Next" button is clicked, GUI 600 changes to GUI 700.

[0064] Figure 7 A setup wizard GUI 700 according to an embodiment is shown. In an embodiment, the GUI 700 may be a frame that includes a title 730, a label 710, a unit type 720, a button 750, and an information button 740.

[0065] exist Figure 7 In the text “Creating a Refrigeration Unit - Selecting Equipment”, heading 730 includes the phrase “Creating a Refrigeration Unit – Selecting Equipment”. It will be understood that the text disclosed herein can be any suitable text. Figure 5 When the "Decoupled" chiller unit type is selected, label 710 includes the text "Select equipment for this decoupled chiller unit. Some pumps may be optional." Label 710 may depend on... Figure 5 The choice of refrigeration unit varies depending on the type of refrigeration unit used.

[0066] Graphical unit 720 is displayed in the middle or near the middle of GUI 700. It will be understood that unit 720 is dynamically generated based on selections from GUIs 500, 600, etc. In this example embodiment, unit 720 includes a chiller with a "parallel (simple)" configuration, pumps (each pump positioned upstream of the chiller), a load with pumps positioned upstream of the load, a bypass conduit configured in parallel with the load, and a fluid loop indicating the direction of fluid flow (see arrows).

[0067] Each refrigeration unit is displayed as a drop-down list, allowing the user to select a refrigeration unit from the list. The refrigeration unit can be an air-cooled refrigeration unit, a water-cooled refrigeration unit, etc. It will be understood that when other components (e.g., pumps, valves, loads, etc.) are... Figure 7 When the corresponding icon in the GUI 700 is clicked, the other component can be selected or configured. In this embodiment, the GUI 700 displays icons for the pump and the load. It will be understood that the setup wizard can obtain multiple components from a library (e.g., a component library) pre-stored in (e.g., the controller's) memory, and each component is displayed in the GUI 700 when, for example, a component is clicked or selected from a drop-down list corresponding to the component. In one embodiment, the component library can be pre-determined for, for example, a new unit. In another embodiment, the component library can be generated via, for example, discovering existing units. For example, the controller can discover (determine and / or identify) components connected to the controller in the BAS network (e.g., by verifying components, scanning the network, etc., and by receiving responses from components) and add the components to the component library. It will also be understood that the setup wizard can obtain parameters for multiple components from a library (e.g., a parameter library) pre-stored in (e.g., the controller's) memory, and display these parameters in the GUI for operation (e.g., selection, input, change, etc.).

[0068] For example, in this embodiment, the user can select either an air-cooled or a water-cooled chiller. When an air-cooled chiller is selected, the user can choose the corresponding compressor type (e.g., screw or rotary). When a water-cooled chiller is selected, the user can choose the corresponding compressor type (e.g., centrifugal, screw, or rotary). The user can further configure other parameters of the components (e.g., minimum chilled water setpoint, variable-speed or fixed-speed compressor, alarms, energy consumption input, sensor input, etc.) and unit / system parameters (e.g., operating parameters). Such configuration can be accomplished via, for example, different GUIs (e.g., an intermediate GUI between GUI 700 and GUI 800) using a setup wizard.

[0069] Information button 740, when clicked, is configured to display information that helps in understanding the components of GUI 700. Button 750 includes a "Cancel" button (configured to cancel the setup wizard's execution when clicked), a "Previous" button (configured to navigate the current GUI 700 of the setup wizard to the previous GUI 600 when clicked), and a "Next" button (configured to navigate the current GUI 700 of the setup wizard to the next GUI, e.g., ...). Figure 8 (800). It will be understood that the "Next" button can be disabled until all components (e.g., chiller (e.g., capacity, minimum chilled water setpoint, total operating hours, operation sequence, efficiency, etc.), pumps (e.g., number and / or type of pumps, etc.), valves, loads, etc.) have been selected and / or configured. It will also be understood that other intermediate GUIs may exist between GUI700 and GUI800.

[0070] During operation, the user can select a component (e.g., chiller) based on, for example, the component configuration of the chiller and / or the chiller type of the building or BAS unit, making it possible to identify or select a component (e.g., chiller). When the "Previous" button is clicked, GUI 700 changes back to GUI 600. When the "Next" button is clicked, GUI 700 changes to, for example, GUI 800 (or some other intermediate GUI between 700 and 800). It will be understood that when the "Next" button is clicked, the setup wizard can perform verification (e.g., check for duplicate selections), and if any problems are found during verification (e.g., duplicate selections are found), an error message can be displayed and the setup wizard's GUI 700 may not navigate to the next GUI until, for example, the problem is resolved.

[0071] Figure 8 A setup wizard GUI 800 according to an embodiment is shown. In this embodiment, the GUI 800 may be a frame including a title 830, a text field 810, a refrigerator assembly diagram 820, and buttons 850. Figure 8 In this document, heading 830 includes the text “Creating a Refrigeration Unit – Confirming Selections”. It will be understood that the text disclosed herein can be any suitable text.

[0072] It will be understood that text field 810 and chiller unit diagram 820 are dynamically generated based on selections or configurations from previous GUIs (e.g., GUIs 400, 500, 600, 700, etc.). Chiller unit diagram 820 includes chillers (four chillers are shown as an example in 820), loads (e.g., cooling coils in air handlers or other equipment), pumps (one pump is shown as an example in 820; there may be multiple pumps or multiple manifold pumps, etc.), valves, and fluid loops (see arrows) indicating the direction of fluid flow. Valves can be any suitable flow control device (valve, switch, etc.) used to control fluid flow to, for example, bypass or flow through the load. A controller can control valves (e.g., directly or via relays), sensors (not shown), and other components of the chiller unit to achieve predetermined or desired performance. In embodiments, the controller can control components in the unit (chillers, pumps, condensers, towers, etc.) via digital communication or through hardwired connections (e.g., via binary or analog control).

[0073] In an embodiment, chiller unit diagram 820 may be an interactive unit diagram with real-time parameter values ​​(e.g., system chilled water return temperature, evaporator inlet water temperature, evaporator outlet water temperature, system chilled water supply temperature, system chilled water setpoint, etc.) obtained from interactions with units in the building or BAS. For example, real-time parameter values ​​can be obtained through sensors (e.g., temperature, pressure, humidity, etc.) of the building or BAS unit.

[0074] It will be understood that Unit Diagram 820 may include real-time values / data and can provide users with the ability to execute overlays (e.g., allowing users to control the unit via overlays such as changing setpoints, changing chiller sequence, changing schedules, etc.), which can provide input to the unit control logic via a GUI. The unit control logic can overlay the operating points of components (e.g., pump on, valve open, etc.) via BAS communication. Unit Diagram 820 includes components and can link components to further details about those components.

[0075] Text field 810 displays the configuration dynamically generated from the previous GUI of the setup wizard, including, for example, the unit name and description (from GUI 400), unit type (from GUI 500), chiller configuration (from GUI 600), unit components (equipment) (from GUI 700), and parameter configurations for components and systems (from the intermediate GUI between 700 and 800), etc. It will be understood that... Figure 8 The text field 810 shown is for illustrative purposes only and may not include the complete configuration.

[0076] Button 850 includes a “Cancel” button (configured to cancel the setup wizard when clicked), a “Previous” button (configured to navigate the current GUI 800 of the setup wizard to the previous GUI 700 (or an intermediate GUI between 700 and 800) when clicked), and a “Done” button (configured to complete the creation and / or configuration of the unit via the setup wizard and create / configure dashboard 900 when clicked).

[0077] Figure 9A and Figure 9B A graphical dashboard 900 according to an embodiment is shown, which includes a graphical unit diagram 920, unit control logic associated with the components of the unit diagram 920, and key performance indicators (KPIs) 910 of the unit. It will be understood that the graphical unit dashboard 900 includes components of the unit (such as pumps, valves, pipelines, chillers, boilers, loads, etc.) and associated operating controls or operating logic (e.g., unit control logic, which may be a software algorithm executed by a controller).

[0078] The dashboard 900 is dynamically generated by the setup wizard based on selections or configurations from GUIs such as 400, 500, 600, 700, etc. (e.g., chiller unit name, chiller type, chiller configuration, components, and parameters of components and systems). The unit diagram 920 is similar. Figure 8 Figure 820 shows the unit. The instrument panel 900 can reflect the status of actual equipment (e.g., components) and / or the status of the unit.

[0079] KPI 910 includes performance parameters such as: power values ​​of components (such as pumps, fans, etc.), chiller water flow rate, condenser water flow rate, unit waste heat, chiller water temperature (supply and return), condenser water temperature (inlet and outlet), system chilled water temperature setpoint, unit heat output and efficiency and power consumption, ambient temperature (dry bulb and wet bulb), chiller and unit efficiency, maximum daily unit heat cooling, etc.

[0080] It will be understood that efficiency (kW / Ton) can be determined by summing the power of all components of the unit and dividing it by the cooling power delivered to the load. The efficiency (kW / Ton) KPI may require sensors installed in the BAS and can be determined based on, for example, data sensed by the sensors. For instance, the power (kW) of each component in the unit (e.g., pumps, fans, compressors, etc.) can be measured, and the heat output (Ton) is a measurement of the cooling power delivered by the unit. Ton can be measured directly using energy meters (including flow meters and temperature sensors), or it can be calculated using sensing data from individual temperature sensors and flow meters. The coefficient of performance (COP) is the reciprocal of kW / Ton and is the ratio of the power delivered to the system to the unit's power consumption (power output / power input).

[0081] Will understand, Figure 9A and Figure 9B The units shown are for illustrative purposes only, and the units may be water units (chilled water and / or hot water), boiler units, simultaneous heating and / or cooling units, air units, etc.

[0082] Figure 10A and Figure 10B The embodiments shown can be illustrated as follows: Figure 9B The KPI list is part of KPI 910. Figure 10A and Figure 10B In the text, the "KPI" column can indicate what is available. Figure 9B The KPI 910 section shows data for such KPI items (e.g., performance). The "Ask about this" column indicates whether the setup wizard prompted the user to select / configure the data source for the KPI item during dashboard creation 900, or whether the KPI item data was calculated based on other parameters. The "In the final graph" column indicates whether... Figure 9A The KPI data is shown in the graphical unit diagram 920. The "In Dashboard" column can indicate whether it is in Figure 9A and Figure 9B The data for the KPI items are shown in dashboard 900 and / or KPI 910.

[0083] It will be understood that it can be saved (e.g., as part of an application), edited, and / or reconfigured via tools such as editing tools. Figure 9A and Figure 9B The generated dashboard 900. When edited via a tool, the GUI for editing dashboard 900 can be similar to the setup wizard used to create dashboard 900. Differences between the setup wizard's GUI and the tool's GUI may include the GUI's title (e.g., "Create" in the setup wizard versus "Edit" in the tool) and default values ​​for fields / selections (e.g., predetermined values / selections in the setup wizard versus user-selected values ​​in the tool). In an embodiment, the setup wizard and the tool can be a single software application.

[0084] Figure 11 A flowchart illustrating a method 1100 for dynamically generating or editing a graphical dashboard via a graphical user interface setup wizard, according to an embodiment, is shown. The dashboard may be, for example... Figure 9A and Figure 9B The dashboard 900 includes a graphical unit diagram (including unit components such as pumps, valves, pipelines, chillers, boilers, loads, etc.), operation controls or operation logic associated with the components (e.g., unit control logic), and KPIs.

[0085] The operation flowchart 1100 may include one or more operations, actions, or functions depicted by one or more boxes 1110, 1120, 1130, 1140, 1150, and 1160. Although shown as discrete boxes, the various boxes may be divided into additional boxes, combined into fewer boxes, or eliminated depending on the desired implementation. As a non-limiting example, according to one or more exemplary embodiments described herein, corresponding to Figures 4 to 10B The description of method 1100, as depicted herein and executed by the controller or any other suitable controller, involves dynamically generating or editing a dashboard via a graphical user interface using a setup wizard or a tool such as an editing tool. This dashboard includes a graphical unit diagram, unit control logic, and / or KPIs. Process 1100 may begin at box 1110.

[0086] Box 1110 may represent: the controller runs a GUI setup wizard (or tool) and the user determines the type of unit through the setup wizard or tool. It will be understood that box 1110 may include: the user identifying the type of unit from multiple unit types in a library (e.g., a layout library) (displayed by the setup wizard or tool) and selecting the unit type that matches the mechanical layout of the building automation system. Box 1110 may be followed by box 1120.

[0087] Box 1120 may represent: a user determines the unit configuration through a setup wizard or tool. It will also be understood that box 1120 may include: a user identifying the unit configuration from multiple unit configurations (displayed by the setup wizard or tool) in a library (e.g., a configuration library) and selecting the unit configuration that matches the unit configuration of the building automation system. Box 1120 may be followed by box 1130.

[0088] Box 1130 may represent: a user identifying at least one component of the unit through a setup wizard or tool. It will be understood that Box 1130 (identifying the component) is based on the identification or selection of Box 1110 (identifying the unit type) and / or Box 1120 (identifying the unit configuration). It will also be understood that Box 1130 may include: a user identifying a component of the unit from a library (e.g., a component library) (displayed by the setup wizard or tool) of multiple unit components and selecting a unit component that matches the unit component of the building automation system. At least one component of the unit may include one or more of the following: at least one chiller, at least one condenser pump for pumping fluid, at least one flow control device (e.g., valve, switch, etc.), at least one condenser or at least one tower fan for cooling fluid, and / or a fluid circuit for guiding the flow of fluid pumped by at least one condenser pump, etc. Box 1130 may be followed by Box 1140.

[0089] Box 1140 may represent: a user configuring parameters of at least one component of the unit and / or parameters of the unit (system) via a setup wizard or tool. It will be understood that Box 1140 (Configuring Parameters) is based on the determination or selection of Box 1130 (Determined Components). It will also be understood that Box 1140 may include: a user identifying component and / or system parameters from a library (e.g., a parameter library) (displayed by the setup wizard or tool) of multiple unit components and / or system parameters, and configuring the component or unit parameters that match the parameters of the component and / or the building automation system's unit. Box 1140 may be followed by Box 1150.

[0090] Box 1150 may represent: A setup wizard or tool generates a unit dashboard based on the selected unit type, selected unit configuration, selected at least one component, and configuration parameters of at least one component and / or the unit. This dashboard includes a graphical unit diagram, unit control logic, and / or KPIs for the unit. In an embodiment, generating the graphical dashboard using the setup wizard or tool includes: generating an interactive unit diagram (e.g., showing real-time sensed / measured parameter values) for interaction with the unit. Box 1150 may be followed by box 1160.

[0091] Box 1160 may represent: The controller controls the unit based on the generated or edited unit control logic of the unit dashboard. It will be understood that Box 1160 may include: the controller determining control points for the unit; the controller mapping the control points to components shown in the generated dashboard; and / or the controller controlling the unit based on the mapped control points (e.g., components shown in the generated dashboard), such as the controller controlling one or more valves in the generated dashboard to achieve desired / predetermined chiller performance and / or chiller capacity. In one embodiment, control points may be mapped based on semantic tags (e.g., component metadata). In another embodiment, control points may be mapped by selecting points from a list of installed / discovered components.

[0092] It will be understood that in other embodiments, setup wizards or tools may collect data (e.g., unit selection, configuration, etc.) through user input, such as from checkboxes, radio buttons, drop-down menus, text input, etc., without displaying a graphical representation of the data. Such setup wizards or tools may rely on the user's understanding of textual terminology, the possible configurations of the unit, the settings for each possible configuration, etc. In such embodiments, a graphical interface for human-machine interaction may be custom-built through a separate process that may require the user to add unit components to a library and map each of these components to underlying data points and / or control points within the previously configured system. The user responsible for creating the chiller layout (e.g., the technician responsible for installation, etc.) may differ from the end user of the unit (e.g., the building or BAS administrator), and different requirements from different users may lead to rework.

[0093] The embodiments disclosed herein can reduce the knowledge required about the mechanical systems of units in a building by simplifying unit configuration. This reduced knowledge is because graphical descriptions can guide the selection of unit type and configuration using corresponding pump, tower, and other equipment configurations, along with graphical illustrations dynamically built upon completion of the setup wizard. The embodiments disclosed herein can also reduce the time required to generate procedures and GUIs for unit operation. Furthermore, the embodiments disclosed herein can facilitate the dynamic generation of the GUI based on selections made during configuration. Without the embodiments disclosed herein, users might not realize setup errors until late in the process, potentially wasting time, performing unnecessary steps based on incorrect input, and potentially requiring rework. In the embodiments disclosed herein, errors made by the user during unit creation or editing are more easily identified before the unit creation or editing is complete, due to the automatically generated graphics that can be displayed on the final page / GUI of the setup wizard or tool.

[0094] All aspects:

[0095] It should be understood that any one of aspects 1 to 9 and any one of aspects 10 to 15 can be combined with each other.

[0096] Aspect 1. A method for dynamically generating or editing a unit dashboard via a graphical user interface (GUI), the method comprising:

[0097] The type of unit is determined through the GUI settings;

[0098] The configuration of the unit is determined through the GUI settings;

[0099] At least one component of the unit is determined through the GUI settings;

[0100] The parameters of at least one component of the unit are configured through the GUI settings;

[0101] Generate a unit dashboard including unit control logic based on the unit's type, configuration, at least one component, and parameters of the at least one component; and

[0102] The unit is controlled based on the unit control logic.

[0103] Aspect 2. The method according to aspect 1 further includes:

[0104] At least one key performance indicator (KPI) for the unit is generated based on the unit's type, configuration, at least one component, and the parameters of the at least one component.

[0105] Aspect 3. The method according to aspect 2 further includes:

[0106] Generate a graphical unit diagram.

[0107] The unit dashboard is independent of the GUI settings, and

[0108] The graphic unit diagram and the at least one KPI are displayed on the unit's dashboard.

[0109] Aspect 4. The method according to any one of Aspects 1 to 3, wherein generating the graphical unit diagram comprises: generating an interactive unit diagram for interaction with the unit based on the type of the unit, the configuration, the at least one component, and the parameters of the at least one component.

[0110] Aspect 5. The method according to any one of aspects 1 to 4, further comprising:

[0111] Determine the control points of the unit; and

[0112] Map the control points to the unit's dashboard.

[0113] Controlling the unit includes controlling the unit based on the mapped control points.

[0114] Aspect 6. The method according to any one of Aspects 1 to 5, wherein the at least one component of the unit comprises one or more of the following: at least one refrigeration unit, at least one pump for pumping fluid, at least one load, and a fluid circuit for guiding the flow of the fluid pumped by the at least one pump.

[0115] Aspect 7. The method according to any one of Aspects 1 to 6, wherein determining the type of the unit comprises: identifying the type of the unit from a plurality of unit types in a layout library, and selecting the type of the unit that matches the layout of the building automation system.

[0116] Aspect 8. The method according to any one of Aspects 1 to 7, wherein the determination of the at least one component of the unit is based on the determined type of the unit and the determined configuration of the unit.

[0117] Aspect 9. The method according to any one of Aspects 1 to 8, wherein the configuration of the parameters is based on the determined at least one component of the unit.

[0118] Aspect 10. A building automation system (BAS), comprising:

[0119] A unit associated with at least one of the spaces, systems, or subsystems of a building or campus;

[0120] Controller; and

[0121] Graphical User Interface (GUI) settings,

[0122] The GUI settings are configured to generate or edit a unit dashboard, including unit control logic, based on the unit type, the unit configuration, at least one component of the unit, and parameters of the at least one component of the unit.

[0123] The controller is configured to control the unit based on the unit control logic.

[0124] Aspect 11. The system according to aspect 10, wherein the GUI settings are further configured to generate at least one key performance indicator (KPI) of the unit based on the type of the unit, the configuration, the at least one component, and the parameters of the at least one component.

[0125] Aspect 12. The system according to aspect 11, wherein the GUI settings are further configured to generate a graphical user interface diagram.

[0126] The graphic unit diagram and the at least one KPI are displayed on the unit's dashboard.

[0127] Aspect 13. The system according to any one of Aspects 10 to 12, wherein when the GUI settings generate the graphical unit diagram, the GUI settings generate an interactive unit diagram for interaction with the unit based on the type of the unit, the configuration, the at least one component, and the parameters of the at least one component.

[0128] Aspect 14. The system according to any one of Aspects 10 to 13, wherein the at least one component of the unit comprises one or more of the following: at least one chiller, at least one pump for pumping fluid, at least one load, and a fluid circuit for guiding the flow of the fluid pumped by the at least one pump.

[0129] Aspect 15. The system according to any one of Aspects 10 to 14, wherein the GUI settings provide in a library multiple unit types, multiple unit configurations, multiple components of the unit, and parameters of the multiple components of the unit; and

[0130] The GUI settings generate the unit dashboard based on selections from the plurality of unit types, the plurality of unit configurations, the plurality of components of the unit, and the parameters of the plurality of components of the unit.

[0131] The terminology used in this specification is intended to describe particular embodiments and not to be limiting. Unless expressly stated otherwise, the terms “a,” “an,” and “the” also include the plural forms. When used in this specification, the terms “comprising” and / or “including” specify the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, and / or components.

[0132] Regarding the foregoing description, it should be understood that detailed changes can be made without departing from the scope of this disclosure, particularly in terms of the construction materials used and the shape, size, and arrangement of components. This specification and the described embodiments are merely exemplary, and the true scope and spirit of this disclosure are indicated by the appended claims.

Claims

1. A method for dynamically generating or editing a unit dashboard via a graphical user interface (GUI), the method comprising: The type of refrigeration unit is determined by the GUI settings. The refrigeration unit has at least one refrigeration unit, at least one pump for pumping fluid, at least one load, and a fluid circuit for guiding the flow of the fluid pumped by the at least one pump. The configuration of the chiller unit is determined through the GUI settings, the configuration including one or more configurations for the at least one chiller; The GUI settings determine at least one component of the refrigeration unit, the at least one component including the at least one refrigeration unit; The parameters of at least one component of the refrigeration unit are configured through the GUI settings; A unit dashboard including unit control logic is generated based on the type, configuration, at least one component, and parameters of the refrigeration unit. as well as The chiller unit is operated based on the aforementioned unit control logic. The configurations for the at least one refrigeration unit include a single refrigeration unit configuration, a parallel configuration, a series configuration, a series-parallel configuration, and a series-parallel configuration.

2. The method according to claim 1, further comprising: At least one key performance indicator (KPI) for the refrigeration unit is generated based on the type, configuration, at least one component, and parameters of the at least one component.

3. The method according to claim 2, further comprising: Generate a graphical unit diagram. The unit dashboard is independent of the GUI settings, and The graphic unit diagram and the at least one KPI are displayed on the unit's dashboard.

4. The method according to claim 3, wherein generating the graphic group diagram comprises: An interactive unit diagram is generated based on the type, configuration, at least one component, and parameters of the at least one component of the refrigeration unit to interact with the refrigeration unit.

5. The method according to claim 1, further comprising: Determine the control points of the refrigeration unit; as well as Map the control points to the unit's dashboard. Operating the refrigeration unit includes controlling the refrigeration unit based on the mapped control points.

6. The method of claim 1, wherein determining the type of the refrigeration unit comprises: Identify the type of the chiller unit from multiple chiller unit types in the layout library, and select the type of the chiller unit that matches the building automation system layout.

7. The method of claim 1, wherein the determination of the at least one component of the refrigeration unit is based on the determined type of the refrigeration unit and the determined configuration of the refrigeration unit.

8. The method of claim 1, wherein the parameters are configured based on the determined at least one component of the refrigeration unit.

9. A building automation system, comprising: A refrigeration unit associated with at least one of the spaces, systems, or subsystems of a building or park, the refrigeration unit having at least one refrigeration unit, at least one pump for pumping fluid, at least one load, and a fluid circuit for guiding the flow of the fluid pumped by the at least one pump. Controller; and Graphical User Interface (GUI) settings The GUI settings are configured to generate or edit a unit dashboard, including unit control logic, based on the type of the chiller unit, the configuration of the chiller unit, at least one component of the chiller unit, and parameters of the at least one component of the chiller unit. The configuration includes one or more configurations for the at least one refrigerator, and the at least one component includes the at least one refrigerator. The controller is configured to operate the chiller unit based on the unit control logic. The configurations for the at least one refrigeration unit include a single refrigeration unit configuration, a parallel configuration, a series configuration, a series-parallel configuration, and a series-parallel configuration.

10. The system of claim 9, wherein the GUI settings are further configured to generate at least one key performance indicator (KPI) for the chiller unit based on the type, configuration, at least one component, and the parameters of the at least one component.

11. The system of claim 10, wherein the GUI settings are further configured to generate a graphics group diagram. The graphic unit diagram and the at least one KPI are displayed on the unit's dashboard.

12. The system of claim 11, wherein when the GUI settings generate the graphical unit diagram, the GUI settings generate an interactive unit diagram for interacting with the refrigeration unit based on the type of the refrigeration unit, the configuration, the at least one component, and the parameters of the at least one component.

13. The system of claim 9, wherein the GUI settings provide in a library multiple unit types, multiple unit configurations, multiple components of the chiller unit, and parameters of the multiple components of the chiller unit; and The GUI settings generate the unit dashboard based on selections from the plurality of unit types, the plurality of unit configurations, the plurality of components of the chiller unit, and the parameters of the plurality of components of the chiller unit.

Citation Information

Patent Citations

  • System and method for controlling a cooling system

    US10006685B2

  • System and method to assist building automation system end user based on alarm parameters

    US10269235B2

  • Remote automated deployment of HVAC optimization software

    CN111448427A