Distributed microgrid control system with multiple controllers connected to each other in peer-to-peer network

Abstract

Systems and methods for controlling distributed energy resources are disclosed. A controller (107) in a peer-to-peer network is configured to act as a scheduling processor for a power bus (103) connected to a respective set of power assets (101) and loads. The controllers (107) are configured to broadcast micro-grid configuration information to each controller (107) over a peer-to-peer network. Each controller (107) is configured to determine to divide the power buses (103) into independent microgrids; and assigning a controller (107) as a supervisor for each of the standalone microgrids. The controllers (107) are configured such that a supervisor controller (107) assigned to a standalone microgrid is configured to determine a scheduling command for a power asset (101) associated with the standalone microgrid to handle a load demand, and broadcast the determined scheduling command on the peer-to-peer network. Each controller (107) is configured to send the determined scheduling command to a power asset (101) electrically connected to a power bus (103) for which the controller (107) acts as a scheduling processor to process the load demand.

Description

Technical Field

[0001] The present disclosure relates generally to control of electrical equipment and, more particularly, to systems and methods for controlling distributed energy resources. Background Art

[0002] A microgrid generally refers to an electric power system that includes a group of localized power generation sources. Such power sources can be connected to a traditional centralized power grid and work synchronously with it, but can be configured to disconnect and work autonomously, for example, to allow the integration of smaller power sources. Microgrids generally have several advantages over typical centralized distribution networks, such as robustness to failures in centralized power grids, and lower transmission losses due to local power generation and consumption. However, existing control systems for microgrids tend to be centralized and / or require complex network systems. Such centralized control systems for microgrids introduce a single point of failure. Centralized control systems must also typically be customized for specific applications, which prevents changes in the system by adding new resources, thereby reducing adaptability.

[0003] U.S. Patent No. 9,158,294 B2, issued on October 13, 2015 (the "'294 patent"), discloses a method for realigning a group of microgrid elements to form a second grid configuration in response to status data from the group of microgrid elements indicating a reconfiguration of the microgrid, whereby the realignment means changing one or more tasks associated with the microgrid elements, changing loads associated with distributed energy resources, and / or changing the relationship between elements within the microgrid and the distributed energy resources. However, the method may require a microgrid control center that may introduce a single point of failure. Furthermore, the method considers microgrid elements on a per-element basis and may not consider aspects of how the microgrid may be configured or interconnected, such as the location of circuit breakers that electrically interconnect separate power buses.

[0004] The disclosed methods and systems may solve one or more of the above problems and / or other problems in the art. However, the scope of the present disclosure is defined by the appended claims, rather than by the ability to solve any particular problem. Summary of the invention

[0005] According to certain aspects of the present disclosure, methods and systems for controlling a distributed control system of a microgrid are disclosed.

[0006] In one aspect, a distributed microgrid control system may include a plurality of controllers connected to each other in a peer-to-peer network. Each of the plurality of controllers is configured to act as a dispatch processor for one or more of a plurality of power buses, which are connected to a corresponding set of power assets and loads in each case. The plurality of controllers are also configured to broadcast microgrid configuration information to each controller through the peer-to-peer network. Each controller is also configured to determine based on the microgrid configuration information: segmenting the plurality of power buses into one or more independent microgrids; and assigning a corresponding controller in the plurality of controllers as a supervisor for each of the one or more independent microgrids. The plurality of controllers are also configured so that each controller assigned to an independent microgrid as a supervisor is configured to determine a dispatch command for an electric asset associated with the independent microgrid to handle load demand, and broadcast the determined dispatch command on the peer-to-peer network. Each controller is also configured to send the determined dispatch command to an electric asset, which is electrically connected to the one or more power buses, and the controller acts as a dispatch processor for the one or more power buses to handle load demand.

[0007] On the other hand, a distributed microgrid may include a plurality of power assets; a plurality of power buses, each of which is electrically connected to a corresponding group of the plurality of power assets; and a plurality of controllers connected to each other in a peer-to-peer network. Each of the plurality of controllers is configured to act as a dispatch processor for one or more of the plurality of power buses, which are connected to a corresponding group of power assets and loads in each case. The plurality of controllers are also configured to broadcast microgrid configuration information to each controller through the peer-to-peer network. Each controller is also configured to determine based on the microgrid configuration information: segmenting the plurality of power buses into one or more independent microgrids; and assigning a corresponding controller of the plurality of controllers as a supervisor for each of the one or more independent microgrids. The plurality of controllers are also configured so that each controller assigned as a supervisor to an independent microgrid is configured to determine a dispatch command for a power asset associated with the independent microgrid to handle load demand, and broadcast the determined dispatch command on the peer-to-peer network. Each controller is also configured to send the determined dispatch command to the power asset, which acts as a dispatch processor for one or more power buses electrically connected to the controller to handle load demand.

[0008] In a further aspect, a controller for a distributed microgrid control system may include at least one memory storing instructions; and at least one processor, the at least one processor operably connected to the at least one memory and configured to execute the instructions to perform operations, including: broadcasting microgrid configuration information on a peer-to-peer network in which the controller is one of a plurality of controllers; determining based on the microgrid configuration information provided on the peer-to-peer network: segmenting a plurality of power buses connected to the plurality of controllers into one or more independent microgrids; and assigning a corresponding controller of the plurality of controllers as a supervisor for each of the one or more independent microgrids. In response to the assignment of the controller as a supervisor for one of the one or more independent microgrids: determining a dispatch command for an electric power asset associated with the independent microgrid to handle a load demand, and broadcasting the determined dispatch command on the peer-to-peer network. In response to receiving a dispatch command for an electric power asset associated with one or more electric power buses for which the controller acts as a dispatch processor via the peer-to-peer network, sending a dispatch command to the associated electric power asset to handle the load demand.

[0009] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the disclosure, as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary embodiments and, together with the description, serve to explain the principles of the disclosed embodiments.

[0011] Figure 1 Depicted is a schematic diagram of an exemplary distributed control system for controlling a microgrid in accordance with aspects of the present disclosure.

[0012] Figure 2 is a diagram of components of the controller 107 according to aspects of the present disclosure.

[0013] Figure 3 is an architectural diagram illustrating the interactions between various components of a distributed control network for microgrid controls according to aspects of the present disclosure.

[0014] FIG. 4A to FIG. 4C is an architectural diagram illustrating a microgrid configuration in a distribution network based on circuit breaker locations according to aspects of the present disclosure.

[0015] Figure 5 is a ladder diagram depicting a distributed control system for breaker position based microgrid controls in accordance with aspects of the present disclosure.

[0016] Figure 6is a flow chart of a process of a distributed microgrid control system according to aspects of the present disclosure. DETAILED DESCRIPTION

[0017] Both the foregoing general description and the following detailed description are exemplary and illustrative only and do not limit the claimed features. As used herein, the terms "comprises," "comprising," "having," "including," or other variations thereof, are intended to encompass non-exclusive inclusions such that a process, method, article, or apparatus comprising a series of elements includes not only those elements, but may also include other elements not expressly listed or inherent to such processes, methods, articles, or apparatuses. The term "or" is used without limitation such that "at least one of A or B" includes A, B, A and A, A and B, etc. In addition, in the present disclosure, relative terms such as "about," "substantially," "generally," and "approximately" are used to indicate possible variations of ±10% of the value.

[0018] Centralized control systems for microgrids eliminate one or more advantages provided by the distributed nature of microgrids, such as robustness against single points of failure. In one instance, a centralized control system can have a central point of contact, i.e., a centralized controller or control center, which can receive / collect information from multiple power assets and loads in a distributed location. The controller can process the information and can send commands to each of the individual assets. In a centralized distribution network of the type described herein, a failure in a communication line with a controller results in a loss of control of the power assets associated with the communication line. In addition, a failure of the controller results in a failure of the entire network.

[0019] In centralized control systems, scalability is often limited. In other words, the number of power assets that can be controlled by a centralized controller is limited by the capabilities of the centralized controller (e.g., input / output (I / O) limitations, processing power limitations, etc.). Such limitations may hinder or complicate the addition of new resources to the system. Furthermore, such centralized control systems often require specially customized control logic, which may increase expense and / or may lead to lower adoption. Advances in control technology for microgrids are needed.

[0020] Figure 1An example microgrid 100 that can be used with the techniques presented herein is depicted. As an example, the microgrid 100 can include power assets 101a-101d (collectively referred to as power assets 101), controllers 107a-107d (collectively referred to as controllers 107), loads 113a-113c (collectively referred to as loads 113), and storage devices 115 that are operably connected to each other via intermediate devices such as power buses 103a-103c (collectively referred to as power buses 103), circuit breakers 105a-105b (collectively referred to as circuit breakers 105), Modbus 109, or a common industrial protocol (CIP) microgrid 111.

[0021] In one instance, the microgrid 100 may distribute control of the power assets 101 across different controllers 107. For example, the microgrid 100 may operate without a central controller or a central control center. In addition, the various embodiments of the microgrid 100 may range from a simple setup (e.g., a single digital asset without a connected circuit breaker) to a complex setup (e.g., a large number of assets with multiple connected circuit breakers), multiple micro-microgrids, and multiple utility connections. Traditionally, varying microgrid configurations may be associated with different customized solutions. Customized case solutions may not be robust for changing microgrid configurations, and may be excessive and / or uneconomical for simple systems. The microgrid 100 according to the present disclosure may be modular and / or scalable, and may provide a mechanism for dividing control functions between various modular controllers based on field configuration conditions.

[0022] In addition, the microgrid 100 can be robust to changes. In one instance, the microgrid 100 can be a peer-to-peer network. Such a peer-to-peer network can be a self-organizing network that can be configured to dynamically add or remove power assets 101, power buses 103, circuit breakers 105, controllers 107, etc. The robustness of adding / removing elements can cause the microgrid 100 to be infinitely scalable. For example, when the power bus 103 and / or the accompanying power assets 101 are added to or removed from the network, the controller 107 can also be reconfigured, reassigned, and / or added or removed as needed. In one instance, each power asset 101 can be electrically connected to a specific controller 107 via the power bus 103. Similarly, the power asset 101 can be connected to the controller 107 via any communication protocol (e.g., Modbus 109), and the controllers 107 can be connected to each other via the CIP microgrid 111. In one example, the microgrid control system can be configured to scale with the microgrid, for example, the controller 107 can be added to or removed from the network along with the power bus 103, power assets 101, and loads 113. In this manner, the microgrid control system can grow with the size and complexity of the microgrid.

[0023] In one example, components in a peer-to-peer network may be connected to each other in a ring architecture that may be configured to provide network redundancy, eg, each controller 107 is connected to the network via multiple communication channels.

[0024] As will be discussed in detail below, in the microgrid 100, each controller 107 acts as a dispatch processor for the electrical assets 101 that are electrically connected to one or more electrical buses associated with the controller 107. However, the controller 107 may or may not be responsible for the supervision of these electrical assets 101. In other words, in some cases, as discussed in further detail below, a controller 107 different from the controller 107 connected to the electrical bus 103 may be responsible for determining dispatch commands for the electrical assets 101 connected to the electrical bus 103.

[0025] For example, in the microgrid 100, each of the connected controllers 107 can broadcast information about what elements it is connected to via a peer-to-peer network. In addition, each controller 107 using such broadcast information can be configured to determine the overall configuration of the network, such as the location of the circuit breakers 105, and can use the overall configuration to determine the effective configuration for assigning which controller 107 to supervise the power assets 101 associated with the different power buses. The supervisor controller 107 can, for example, determine the dispatch commands for the power assets 101 it supervises, and can then broadcast such dispatch commands to the controllers 107 that handle those power assets 101.

[0026] In one example, the electrical assets 101 may include a generator set, a photovoltaic array, an energy storage system, a fuel cell array, a grid connection, a wind turbine, a hydro turbine, pumped water, any other type of power generation unit, etc. or a combination thereof. In one example, the generator set may have operating characteristics, such as an apparent power limit, an active power rating limit, a power factor range limit, a predetermined, regulated and / or designed minimum load capacity, a start / stop frequency limit or threshold, a maximum load capacity, a total operating life, a current operating life, a fuel consumption rate, a power output, a maintenance cost, a replacement cost, etc. Such characteristics may be predetermined, such as set during manufacturing or established via management requirements, or may change during the operation process or life of the generator set. It should be understood that in various embodiments, various electrical assets may be included or omitted in the microgrid 100 instead of or in addition to the electrical assets listed above. It should also be understood that the electrical assets 101 listed above are merely exemplary, and any suitable electrical assets may be included in any suitable arrangement. In one example, the power assets 101 may include any suitable number of power assets, for example, 1, 5, 10, 100, 150, etc. The power assets 101 may be operably connected within the microgrid 100 in any suitable manner. In one example, the power assets 101 may be connected to each other via various intermediate devices, such as a power bus 103, transformers, substations, inverters, rectifiers, load balancers, etc. In one example, the power assets 101 may be connected to the controller 107 via any communication protocol, such as Modbus 109.

[0027] In one example, the power bus 103 may include multiple parallel wires, conductors, etc. that distribute electrical signals from source devices (e.g., power assets 101) to various electrical devices (e.g., loads 113) coupled to the bus. In one example, one or more power buses 103 can be electrically connected to one or more power assets 101 in any suitable arrangement. In another example, one or more power buses 103 can be electrically connected to one or more controllers 107 in any suitable arrangement. Any suitable type of power bus can be used, such as a hybrid power bus (HEB), a fuel cell power bus (FCEB), a battery power bus (BEB), etc.

[0028] In one example, the circuit breaker 105 may include a pair of separable contacts that may be operated automatically in response to a detected fault condition, manually via user-adjusted settings, automatically in response to an automatic instruction, such as for load balancing operations, according to a predetermined schedule that connects or disconnects photovoltaic assets, such as based on a duty cycle, or for any other suitable purpose. For example, the circuit breaker 105 may open the separable contacts in response to a detected anomaly (e.g., an overload or short circuit current in the network) to interrupt the flow of current through the interconnected power bus. The circuit breaker 105 may close the separable contacts to allow power to flow through the interconnected power bus. Any suitable type of circuit breaker may be used, such as a tie breaker, a load breaker, a microgrid inter-breaker, etc.

[0029] In one example, the controller 107 may include multiple interconnected components, such as one or more servers, smart networking devices, computing devices, and corresponding software to monitor, track, and / or control the operation of the microgrid 100. As will be discussed in further detail below, the controller 107 may be configured to optimize the operation of different types of power assets 101, such as to improve efficiency, maintain the integrity of the power assets 101, and the like. In one example, the controllers 107 may be connected to each other via the CIP microgrid 111. In another example, the controllers 107 may be connected to each other via a communication network. The communication network may include a data network, a wired or wireless network, a telephone network, or any combination thereof. It is contemplated that the data network may be any local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a public data network (e.g., the Internet), a short-range wireless network, or any other suitable packet switching network, such as a commercially owned, proprietary packet switching network, such as a proprietary cable or fiber optic network, and the like, or any combination thereof. In addition, the wireless network can be, for example, a cellular network, and can adopt various technologies, including 5G (fifth generation), 4G, 3G, 2G, Long Term Evolution (LTE), Enhanced Data Rates for Global Evolution (EDGE), General Packet Radio Service (GPRS), Global System for Mobile Communications (GSM), Internet Protocol Multimedia Subsystem (IMS), Universal Mobile Telecommunications System (UMTS), etc., and any other suitable wireless medium, such as Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Wireless Fidelity (Wi-Fi), Wireless Local Area Network (WLAN), Internet Protocol (IP) data broadcasting, satellite, mobile ad hoc network (MANET), etc., or any combination thereof.

[0030] In one example, the controllers 107 can be connected in a peer-to-peer network, where each controller 107 can be configured to act as a dispatch processor for one or more power buses 103 connected to a corresponding set of power assets 101. In one example, the controllers 107 can be configured to broadcast microgrid configuration information on the peer-to-peer network. In one example, the microgrid configuration information can include the number or location of one or more circuit breakers 105 electrically interconnecting the plurality of power buses 103, the number, state, or load of the plurality of controllers, the number or state of the corresponding set of power assets, and / or the demand or state of the plurality of loads.

[0031] As discussed in more detail below, the controller 107 can segment the power bus 103 into independent microgrids based on the microgrid configuration information. In one instance, the controller 107 can assign at least one controller 107 as a supervisor for the independent microgrid. In one instance, the controller 107 can determine the supervisor assignment based on the network configuration data available on the network, applying a predetermined assignment logic or algorithm. In one instance, in response to a change in the microgrid configuration information, the controller 107 can update the segmentation of multiple power buses 103 into one or more independent microgrids, and / or update the assignment of controllers 107 as supervisors for independent microgrids. In one instance, the number of controllers 107 acting as supervisors is equal to the number of independent microgrids, wherein each of the one or more independent microgrids operates independently and asynchronously.

[0032] In one example, the supervisor controller 107 may determine a dispatch command for an electrical asset 101 associated with an isolated microgrid, and may broadcast the dispatch command over a peer-to-peer network to other controllers 107. The other controllers 107 receiving the dispatch command may send the dispatch command to the electrical asset 101 electrically connected to the electrical bus 103 for which the controller 107 acts as a dispatch processor.

[0033] In one example, the controller 107 may classify the power assets 101 based at least in part on the asset type. The classified power assets 101 may be aggregated to determine an optimal power dispatch. The controller 107 may determine a dispatch command based at least in part on the optimal power dispatch. In one example, the controller 107 may process historical data of the power assets 101 to determine power generation capabilities, wherein the historical data includes past power generation information. The controller 107 may broadcast such power generation capabilities of the power assets 101 on a peer-to-peer network to actively manage power distribution to the loaders 113.

[0034] In one example, loads 113 may include any number of systems, devices, and the like to be powered by microgrid 100, such as building electronic power systems, air conditioning systems, machines, and the like. In some cases, a portion of loads 113 may be automatic, such as systems or devices with a predetermined operating schedule. In some cases, a portion of loads 113 may be at least partially predictable, such as an air conditioning system that operates in relation to ambient temperature or a building electronic power system that operates in relation to business hours, and the like. In some cases, a portion of loads 113 may be user controlled, such as appliances, machines, and the like. In some cases, a portion of loads 113 may be controlled by controller 107.

[0035] In one example, the storage device 115 can be a battery, a capacitor bank, or any suitable electronic or mechanical device that can hold energy and discharge the energy as an electric current. However, in various embodiments, any suitable type of storage system can be used, such as, for example, a flywheel, a thermal energy storage system, a pumped hydroelectric storage device, a pneumatic energy storage device, etc. In one example, the controller 107 can communicate with the storage device 115 via a communication network. In one example, the power asset 101 can generate excess power, so the controller 107 can store the excess power or energy in the storage device 115. In one example, the load 113 can request additional power beyond the power generation capacity of the power asset 101. The controller 107 can instruct the storage device 115 to provide the stored power or energy power to the load 113.

[0036] Although in Figure 1 Although depicted as separate components in the microgrid 100, it should be understood that in some embodiments, components or portions of components in the microgrid 100 may be integrated with or incorporated into one or more other components. In some embodiments, the operations or aspects of one or more components discussed above may be distributed among one or more other components. Any suitable arrangement and / or integration of the various components and devices of the microgrid 100 may be used.

[0037] In addition, it should be understood that in some cases, components such as power assets 101, loads 113, storage devices 115, power buses 103, circuit breakers 105, etc. may include sensors or other components (not shown) that are configured to determine, sense and / or record status information of the component (e.g., operating status, other connected components, power capacity or demand, maintenance status, etc.) and transmit such information to other components in the microgrid 100, such as the controller 107.

[0038] Although several examples above relate to microgrids, it should be understood that the technology according to the present disclosure can be applied to any suitable type of application of distributed power systems. It should also be understood that the above embodiments are merely illustrative. The technology and techniques of the present disclosure can be applied to any suitable activity.

[0039] Figure 2 is a diagram of components of the controller 107 according to an exemplary embodiment. As used herein, terms such as "component" or "module" generally include hardware and / or software, for example, a processor or the like can be used to implement the associated functionality. As an example, the controller 107 includes one or more components of a distributed control system for a microgrid control. It is contemplated that the functions of these components can be combined in one or more components, or performed by other components of equivalent functionality. In one instance, the controller 107 includes a processor 201, a memory 203, an optimizer 205, a monitoring module 207, a coordination module 209, and a scheduling module 211, or any combination thereof.

[0040] In one example, the processor 201 may include one or more microprocessors, central processing unit (CPU) devices, computing devices, microcontrollers, digital signal processors, or similar devices. The processor 201 may receive instructions from the memory 203 or similar device and execute the instructions to perform one or more processes defined by the instructions for controlling the microgrid 100.

[0041] In one example, the memory 203 can store data and / or software, such as instructions, models, algorithms, equations, data tables, etc., which can be used and / or executed by the processor 201 to perform one or more operations for controlling the microgrid 100. For example, the memory 203 can include one or more optimizers 205, which when executed by the processor 201 are configured to generate commands to optimize the operation of the microgrid 100. In one example, the optimizer 205 can use algorithms that take into account information from other modules to make and provide outputs of certain energy-related determinations, such as whether it is best to generate energy and store it, draw energy from the storage device 115 to meet the needs of the load 113, etc.

[0042] In one example, the monitoring module 207 can monitor the microgrid configuration, for example, in real time or near real time, and can update one or more modules to optimize the microgrid 100. For example, the monitoring module 207 can monitor the addition or removal of the power bus 103 and the accompanying asset group 101, the addition or removal of the controller 107, the addition or removal of the circuit breaker 105, and the change of the position of the circuit breaker 105 (e.g., opening or closing). In another example, the monitoring module 207 can monitor the frequency and voltage of the power on the power bus 103, and can alert one or more modules when it is determined that the frequency and voltage exceed the maximum threshold. In another example, the monitoring module 207 can monitor the condition of the microgrid, and can disconnect the microgrid from the distribution network in response to a power outage to operate independently. In one example, the monitoring module 207 can monitor the capacity of the controller 107, for example, the ability of the controller 107 to control the number of power assets 101, the energy generation capacity of the power assets 101, and the demand of the load 113.

[0043] In one instance, the coordination module 209 can act as an arbitrator between the controllers 107 to designate at least one controller 107 as a supervisor for an isolated microgrid. For example, the monitoring module 207 can detect a load problem within the distributed network, and the coordination module 209 can coordinate with the controllers 107 to select at least one controller 107 as a supervisor for an isolated microgrid to handle the load problem. In one instance, the coordination module 209 can segment the power bus into isolated microgrids based at least in part on the position of the circuit breakers. For example, power buses A and B are electrically connected through circuit breaker 1, and power buses B and C are electrically connected through circuit breaker 2. When circuit breakers 1 and 2 are in the closed position, power buses A, B, and C can form microgrid ABC. However, if circuit breaker 1 is in the open position, the coordination module 209 can segment microgrid ABC into isolated microgrid A and isolated microgrid BC. In one instance, the controllers 107 can exchange microgrid configuration information with each other in real time or near real time, and at least one controller 107 can be selected as a supervisor based on the microgrid configuration information, capacity information, or a combination thereof. As previously discussed, a plurality of power buses A, B, and C electrically connected by circuit breakers can form a microgrid ABC. In this case, the group-level scheduling logic can be given a unique identification (ID) based at least in part on the number of directly connected power buses. For an independent microgrid BC from microgrid ABC, the group-level scheduling logic with the lowest unique ID can be selected as the supervisor. However, it should be understood that in various embodiments, any suitable scheme or technique for assigning supervisors may be used.

[0044] In one example, the scheduling module 211 can determine a scheduling command and transmit the scheduling command to other modules for further processing. In one example, the scheduling module 211 can determine a scheduling command for the power assets 101 associated with the stand-alone microgrid, and can broadcast the scheduling command on the peer-to-peer network. In one example, the scheduling module 211 can determine an optimal power schedule for a group of assets aggregated, and can determine a scheduling command for the power assets based at least in part on the optimal power schedule.

[0045] The above modules and components of the controller 107 may be implemented in hardware, firmware, software, or a combination thereof. The various implementations presented herein contemplate any and all arrangements and models.

[0046] Figure 3 300 is an architectural diagram illustrating the interaction between various components of a distributed control network for a microgrid control according to an exemplary embodiment. Although the schematic diagram 300 is shown and described as an operational flow between components, it is contemplated that various embodiments of the schematic diagram 300 may be performed in any order or combination and need not include all of the steps shown.

[0047] In step 301, the electric asset 101 can communicate with the input 302 via any communication protocol (e.g., MODBUS). In one example, the electric asset 101 can transmit capacity information (e.g., power generation information) and operating characteristic data to the input 302. However, it should also be understood that the electric asset 101 can transmit any other information to the input 302.

[0048] In step 305, the asset interface 303 may receive data from the input 302. The asset interface 303 may convert the data (e.g., raw data) received from the input 302 to uniform data familiar to the controller 107 via any data conversion mechanism. In one example, various types of power assets 101 may provide power data in different measurements, such as kilowatts, watts, kilowatt-hours, state of charge (SOC), etc. The asset interface 303 may perform unit conversions on these different measurements via any unit conversion mechanism. The varying measurements are converted to uniform measurements familiar to the controller 107. Such data conversions may enhance data processing and may result in uniform processing of various types of power assets 101.

[0049] In step 307, the input classifier 309 can classify the power bus 103 and the associated power assets 101 into an electrically isolated network (e.g., an isolated microgrid) based at least in part on the circuit breaker position. In one instance, the power bus 103 can be connected via a tie breaker or any other electrical circuit breaker device. In one instance, multiple power assets 101 can be distributed on different power buses 103, for example, there can be 1,000 power assets 101 connected via different circuit breakers 105. If all circuit breakers 105 are closed, the multiple power assets 101 are electrically connected to each other via the power bus 103, and the microgrid 100 is a single isolated microgrid. Such electrically connected buses and assets can be controlled by a management controller 107 selected from a plurality of controllers 107.

[0050] On the other hand, if at least one circuit breaker 105 is open, the configuration of the microgrid may be different, for example, the power assets 101 associated with the power bus 103 having an open tie breaker are electrically independent and operate independently. In one example, the input classifier 309 may group the power assets 101 based on the circuit breaker location so that each group belongs to a single microgrid. In one example, the input classifier 309 may broadcast information about each individual microgrid to the various computational blocks to compute an optimal schedule for all asset types.

[0051] In one example, the controllers 107 (e.g., microcontrollers that perform processing and IO functions) communicate with each other within a peer-to-peer network, for example, in real time, near real time, on a schedule, etc. The controllers 107 can read data related to their respective power assets 101 in real time or near real time, and can transmit the data to the input classifier 309. In step 311, the input classifier 309 can forward the data to the aggregation logic 313a-313b (collectively referred to as the aggregation logic 313) for data aggregation. In one example, the aggregation logic 313 can group the power assets 101 based on their types, and can aggregate their data. Such data aggregation before transmission reduces the amount of data that needs to flow between the controllers 107 and reduces data traffic.

[0052] In one instance, data aggregation can allow for efficient determination of dispatch commands based on asset type. Such determination of dispatch commands by asset type can achieve unlimited scalability. For example, if a microgrid has 1000 power assets, it may exceed the ability of a single controller 107 to determine dispatch commands for each of the 1000 power assets. Therefore, multiple controllers 107 in a peer-to-peer network can aggregate 1000 power assets based on their types (e.g., generator sets, energy storage systems, photovoltaic groups, fuel cell groups, grid connections, etc.). Multiple controllers 107 can determine aggregate dispatch commands for each type of power asset 101 under their supervision, and can transmit the aggregate dispatch commands to each of the individual controllers 107 that can handle the dispatch of the 1000 power assets, for example, by broadcasting the aggregate dispatch commands on the network. Each of the individual controllers 107 can process the received aggregate dispatch commands and can determine individual dispatch commands for each power asset 101. In some embodiments, the aggregation of power assets by type can also lead to improved efficiency in determining dispatch commands, for example, compared to determining each dispatch command individually.

[0053] For example, in step 315, the group-level dispatch logic microgrid control 317 may broadcast aggregated data for the grouped power assets 101 on a peer-to-peer network, or may send the aggregated data to a specific controller 107 designated as a supervisor for the stand-alone microgrid. The supervisor controller 107 may solve the dispatch problem for the stand-alone microgrid.

[0054] In step 319, the asset-to-asset allocation logic 321 may calculate the optimal dispatch between the same type of power assets 101. The group level dispatch logic microgrid control 317 and the asset-to-asset allocation logic 321 may find the optimal solution to the power dispatch problem.

[0055] In step 323, the output classifier 325 can assign commands (eg, dispatch commands) from a particular controller 107 to separate independent grids. In one example, the output is based on the input order, eg, the output is in the same order as the input.

[0056] FIG. 4A to FIG. 4C is an architectural diagram showing a microgrid configuration in a distributed network based on circuit breaker locations according to an exemplary embodiment. As shown in the figure, FIG. 4A to FIG. 4CIncluding power buses connected by circuit breakers (e.g., connecting circuit breakers 401 and 403), for example, power buses 1, 2, and 3. In one example, the IO limit of the controller can be 30 power assets per controller. As depicted, power bus 1 can be connected to 20 power assets, power bus 2 can be connected to 50 power assets, and power bus 3 can be connected to 20 power assets. In one example, circuit breakers 401 and 403 can be in a closed position, whereby power buses 1, 2, and 3 can form a single microgrid. The group-level dispatch logic with the lowest unique ID can be selected as the supervisor in each of power buses 1, 2, and 3 to control up to 30 power assets. For example, the group-level dispatching logic microgrid control 317a can control 20 power assets in power bus 1 and 10 power assets in power bus 2, the group-level dispatching logic microgrid control 317c can control 30 power assets in power bus 2, and the group-level dispatching logic microgrid control 317e can control 10 power assets in power bus 2 and 20 power assets in power bus 3.

[0057] exist Figure 4A , because the circuit breakers 401 and 403 are open, the power buses 1, 2, and 3 can operate independently of each other. The independent power buses 1, 2, and 3 can be controlled by the group-level dispatch logic microgrid controls 317a, 317c, and 317e, respectively. In one example, during the closed position of the circuit breakers 401 and 403, data for 20 power assets in the power bus 2 can be transmitted by the group-level dispatch logic microgrid control 317c of the power bus 2 to the group-level dispatch logic microgrid control 317e of the power bus 3. Since the microgrid configuration changes, that is, the circuit breakers 401 and 403 are open, the transmission data of the 20 power assets in the power bus 2 can be returned to the group-level dispatch logic microgrid control 317c for effective control of all 50 assets in the power bus 2.

[0058] exist Figure 4B , because breaker 401 is closed, power buses 1 and 2 are electrically connected, and because breaker 403 is open, power bus 3 is independent. The 20 power assets in power bus 1 and the 50 power assets in power bus 2 can form a microgrid of 70 power assets, and a simple rule-based approach (e.g., arbitration logic) can be implemented to designate the group-level dispatch logic microgrid control 317a of power bus 1 as the supervisor for the 70 power assets. In one example, the 50 power assets in power bus 2 can be aggregated by the group-level dispatch logic microgrid control 317c and then sent to the group-level dispatch logic microgrid control 317a. However, power bus 3 can operate independently, and the group-level dispatch logic microgrid control 317e can operate as an active controller of power bus 3.

[0059] exist Figure 4C , because breaker 403 is closed, power buses 2 and 3 are electrically connected, but because breaker 401 is open, power bus 1 is independent. Power bus 1 can operate independently, and the group-level dispatch logic microgrid control 317a can operate as an active controller of power bus 1. On the other hand, 50 power assets in power bus 2 and 20 power assets in power bus 1 can form a microgrid of 70 power assets, and a simple rule-based approach (e.g., arbitration logic) can be implemented to designate the group-level dispatch logic microgrid control 317c of power bus 2 as the supervisor for the 70 power assets. In one example, 20 power assets from power bus 3 can be aggregated by the group-level dispatch logic microgrid control 317e and then transmitted to the group-level dispatch logic microgrid control 317c for effective control of the supervised assets.

[0060] Industrial Applicability

[0061] The disclosed method and system for controlling distributed energy resources can be used in any microgrid type system that sends and receives power. The method and system disclosed herein can provide robustness against single fault points, allow new resources to be added, and reduce transmission losses caused by local power generation and consumption. In addition, the method and system disclosed herein can be applied to configurations ranging from simple settings (e.g., single digital assets without connecting circuit breakers) to complex settings (e.g., a large number of assets with multiple connecting circuit breakers, multiple microgrids, and multiple utility connections). Microgrids according to the methods and systems disclosed herein can provide modularity and scalability, and can provide mechanisms for dividing control functions between various module controllers based on field configuration conditions. In one example, the disclosed microgrid control system can be a peer-to-peer network of controllers connected via a ring network, wherein each node can have two physical paths to the network and is robust to interruptions at a single point. Such a ring network can allow communication line interruptions and increase reliability and robustness. In another case, the disclosed microgrid control system can respond to changes in the microgrid structure, such as the connection breaker position, by assigning at least one controller to an independent microgrid. Each controller may be able to control any set of independent resources, for example, grouped by one or more power buses, and the need for communication may be minimized, and when communication is required, the amount of data that needs to flow between controllers may be reduced by aggregating the data before transmission. The disclosed microgrid control system reduces network bandwidth requirements by sending data only when needed, and reduces the amount of data that needs to be sent.

[0062] Figure 5is a ladder diagram illustrating a process sequence for a microgrid control based on circuit breaker position according to an exemplary embodiment. Although illustrated and described as a series of steps, it is contemplated that the process may be performed in any order or combination and need not include all illustrated steps. It should be understood that the exemplary microgrid may include any suitable number of controllers 107a-n, any suitable number of assets 101a-n, any suitable number of power buses 103a-n, any suitable number of circuit breakers 105a-n, and any suitable number of loads 113a-n. In addition, it should be understood that the number of the above components may be different from each other. In the following description, the same elements may be referenced by their annotation indexes. For example, operations common to all controllers 107a-n may generally refer to controller 107.

[0063] In step 501, the controller 107 may receive individual data in real time or near real time from a plurality of power assets 101. In one example, the individual data may include operating characteristics such as apparent power limits, predetermined, regulated and / or designed minimum load capacity, maximum load capacity, total operating life, current operating life, fuel consumption rate, power output, maintenance cost, replacement cost, etc.

[0064] In step 503, the controller 107 may receive, for example, in real time or near real time, the configuration of the associated power bus 103. For example, the controller 107a may receive the configuration of one or more power buses 103 (e.g., power bus 103a) associated with the controller 107. In one example, the power buses 103 may be connected to their respective power assets 101 and may be electrically interconnected through the circuit breakers 105. In one example, the configuration of the power bus 103 may change based on the position of the circuit breaker 105. In one example, the controller 107 may collectively receive data from multiple power assets 101 and the configuration of the power bus 103. In another example, the power bus 103 may receive data from multiple power assets 101 and may transmit the data to the controller 107.

[0065] In step 505, the controller 107 may receive, for example, in real time or near real time, location information of the circuit breaker 105 used to interconnect the power buses 103. For example, the controller 107a may receive location information from the connected circuit breaker 105a. In one example, the circuit breaker 105 may be opened or closed automatically, manually, on a schedule, on demand, or a combination thereof. In one example, if the circuit breaker 105 is opened, the power buses 103 are not interconnected, thereby preventing power from flowing through the power buses 103. In another example, if the circuit breaker 105 is closed, the power buses 103 are connected, thereby allowing power to flow through the interconnected power buses 103.

[0066] In step 507, the controller 107 may receive data associated with the load 113 in real time or near real time, such as the amount of power required by the load 113. In one example, the controller 107 may process historical information about the load 113 to generate a load forecast that predicts or estimates the amount of power required by the load during, for example, different times of the day, different days of the week, different seasons, different weather or ambient temperature conditions, etc. Any suitable forecasting technique may be used, such as averaging over multiple historical scheduling periods.

[0067] In step 509, the controller 107 can process the information received from the electrical assets 101, the electrical bus 103, the circuit breakers 105, and the loads 113. In one example, the controller 107 can convert the varying measurements from the plurality of electrical assets 101 into a uniform measurement familiar to the controller 107. In one example, the controller 107 can classify and aggregate the data from the electrical assets 101 based at least in part on the data type, the electrical asset type, or a combination thereof.

[0068] In step 511, the controller 107 may broadcast microgrid configuration information to other controllers 107 via a peer-to-peer network, and / or may receive broadcasts of microgrid configuration information from other controllers 107. In one example, the microgrid configuration may include the number or location of circuit breakers 105, the number, state, or load of controllers 107, the number or state of power assets 101, and / or the demand or state of loads 113.

[0069] In step 513, the controller 107 may process the microgrid configuration information to segment the microgrid into independent grids. In one example, the microgrid may be segmented into independent grids based at least in part on the position of the circuit breaker 105 of the interconnected power bus 103. In one example, the controller 107 may assign or identify at least one controller 107 to supervise the power assets 101 of the independent grid. In one example, the assignment or identification of the supervision of the power assets 101 of the independent grid by at least one controller 107 may be based at least in part on the lowest unique ID of the at least one controller 107, capacity information, or a combination thereof.

[0070] In step 515, the supervisor controller 107 may determine, for example, a dispatch command for an individual power asset 101 and / or an aggregated group of power assets 101 and / or a power bus 103 of an isolated power grid it supervises. In one example, the supervisor controller 107 may determine a dispatch command for an aggregated group of power assets 101 and / or a power bus 103 based at least in part on an optimal power dispatch.

[0071] In step 517, the supervisor controller 107 may broadcast the scheduling command of the standalone grid it is supervising to other controllers 107 via the peer-to-peer network.

[0072] In step 519 , the other controllers 107 may determine and / or classify the individual dispatch commands based on the aggregated commands for the electrical asset 101 for which the dispatch commands serve as a handler.

[0073] In step 521 , other controllers 107 may send individual dispatch commands to the respective electrical assets 101 that they are processing.

[0074] In step 523 , electrical asset 101 may provide power to load 113 based at least in part on the dispatch command.

[0075] In some cases, components may be added or removed from the microgrid. In this case, one or more of steps 501-523 may be repeated. In some cases, the method may be performed continuously or periodically in response to a user instruction, in response to detecting a change in the microgrid, etc.

[0076] In some cases, the controller 107 may operate asynchronously. For example, the microgrid configuration may be broadcast from different controllers 107 at different times. In some embodiments, a particular controller 107 (e.g., controller 107a) may proceed through step 511 without waiting to receive microgrid configuration information from any other particular controller 107. In embodiments where the method is performed continuously or periodically, the hysteresis of the microgrid configuration data from one or more other controllers 107 may be considered in the next iteration of the method. In addition, in some embodiments, the controller 107 may be configured to continuously, periodically, and / or passively listen to the broadcast data, and / or may be configured to buffer such received data until the controller 107 reaches the appropriate step in the method. In some cases, such asynchronous operation may improve the efficiency of the microgrid control, for example, by reducing the degree or risk of a lagging controller 107 blocking the method. In some cases, the controller 107 may also operate at different timings or rates, for example, based on the capabilities or capacity of the controller 107. Asynchronous operations such as the aforementioned may facilitate such different operation timings.

[0077] Figure 6600 is a flow chart of a process for a distributed microgrid control system according to an exemplary embodiment. In various embodiments, the controller 107 and / or any of the modules 201-211 may provide means for implementing various portions of the process 600, as well as means for implementing embodiments of other processes described herein in conjunction with other components of the process 600. Although the process 600 is shown and described as a series of steps, it is contemplated that various embodiments of the process 600 may be performed in any order or combination, and need not include all of the steps shown.

[0078] For various reasons, or under various circumstances, as discussed in one or more of the examples above, the configuration of the microgrid may change. For example, the location of circuit breakers, and / or the presence or operability of various components or load demands may change.

[0079] In step 601, the controller 107 may receive a microgrid configuration from a microgrid element processed by the controller 107. In one example, the microgrid configuration information includes location information of the circuit breakers 105. In one example, the microgrid configuration information also includes the number or location of the circuit breakers 105 of the electrically interconnected power bus 103, the number, state or load of the controllers 107, the number or state of the power assets 101, and / or the demand or state of the loads 113.

[0080] In step 603 , controller 107 may broadcast microgrid configuration information received from a microgrid element handled by controller 107 over a peer-to-peer network in which controller 107 is one of a plurality of controllers 107 .

[0081] In step 605 , the controller 107 may receive additional microgrid configuration information from the plurality of controllers 107 via the peer-to-peer network, for example, the information including microgrid configurations for microgrid elements respectively processed by the plurality of controllers 107 .

[0082] In step 607, the controller 107 may assign a corresponding controller 107 of the plurality of controllers 107 as a supervisor for each of the one or more independent microgrids. In one example, the controller 107 may divide the power bus 103 connected to the controller 107 into independent microgrids, and may assign the controller 107 as a supervisor for each independent microgrid. For example, the assignment may be based on the microgrid configuration information and the additional microgrid configuration information. For example, the assignment may be applied according to a predetermined algorithm or technique.

[0083] In step 609, the controller 107 may determine a dispatch command for the power assets associated with the stand-alone microgrid for which the controller acts as a supervisor. In one example, the determined dispatch command may be a command aggregated by asset type and / or load demand. In one example, the determined dispatch command is broadcasted on a peer-to-peer network.

[0084] In step 611 , the controller 107 may broadcast the dispatch command through the peer-to-peer network to the assets 101 in the stand-alone microgrid for which the controller acts as a supervisor.

[0085] In step 613, the controller 107 may receive, via the peer-to-peer network, a dispatch command for an electric asset 101 associated with the electric bus 103 for which the controller 107 acts as a dispatch processor, and may send the dispatch command to the processed electric asset to handle the load demand. In one instance, sending the dispatch command may include determining a separate command based on the aggregate command, and then sending the separate command to the separate asset 101. In one instance, the controller 107 may determine the load demand of the load 113 and the power generation capacity of the electric asset 101 in real time or near real time. For example, the controller 107 may process historical data (e.g., past power generation information) of the electric asset 101 to determine their power generation capabilities. For example, the controller 107 may process historical information of the load 113 to predict or estimate the amount of power required by the load 113. The microgrid 100 may distribute the load on the controller 107 based at least in part on the power generation capacity of the electric asset 101 controlled by the controller 107 to handle the load demand.

[0086] The subject matter disclosed above should be considered illustrative, not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other implementations that fall within the true spirit and scope of the present disclosure. Therefore, to the maximum extent permitted by law, the scope of the present disclosure will be determined by the broadest permissible interpretation of the appended claims and their equivalents, and should not be limited or restricted by the foregoing detailed description. Although various implementations of the present disclosure have been described, it is obvious to those of ordinary skill in the art that more implementations may be within the scope of the present disclosure. This specification and examples are intended to be considered as exemplary only, and the true scope of the present invention is indicated by the appended claims and their equivalents. Therefore, the present invention is not limited except according to the appended claims and their equivalents.

Claims

1. A distributed microgrid (100) control system, comprising: A plurality of controllers (107) connected to each other in a peer-to-peer network, wherein: Each controller (107) of the plurality of controllers (107) is configured to act as a dispatch processor for one or more power buses (103) of a plurality of power buses (103), the plurality of power buses being connected in each case to a respective set of power assets (101) and loads (113); The plurality of controllers (107) are further configured to broadcast microgrid configuration information to each controller (107) via the peer-to-peer network; Each controller (107) is further configured to determine based on the microgrid configuration information: dividing the plurality of power buses (103) into one or more independent microgrids; and assigning a corresponding controller (107) of the plurality of controllers (107) as a supervisor for each of the one or more independent microgrids; The plurality of controllers (107) are further configured such that each controller (107) assigned as the supervisor to an isolated microgrid is configured to determine a dispatch command for an electrical asset (101) associated with the isolated microgrid to handle a load demand, and broadcast the determined dispatch command over the peer-to-peer network; and Each controller (107) is further configured to send the determined dispatch command to an electrical asset (101) electrically connected to the one or more electrical buses (103) for which the controller (107) acts as a dispatch processor to process the load demand.

2. The distributed microgrid (100) control system according to claim 1, wherein the plurality of power buses (103) are electrically interconnected via one or more circuit breakers (105), and wherein the microgrid configuration information includes location information of the one or more circuit breakers (105).

3. The distributed microgrid (100) control system according to any one of the preceding claims, wherein the microgrid configuration information further includes information about one or more of the following: the number or location of one or more circuit breakers (105) that electrically interconnect the plurality of power buses (103); the number, status or load of the plurality of controllers (107); the number or status of the corresponding set of power assets (101); Requirements or states of multiple loads (113).

4. A distributed microgrid (100) control system according to claim 3, wherein in response to changes in the microgrid configuration information, the multiple controllers (107) are also configured to update one or more of the following: (i) based on the changes to the microgrid configuration information, the multiple power buses (103) are divided into the one or more independent microgrids, or (ii) a corresponding controller (107) among the multiple controllers (107) is assigned as a supervisor for each independent microgrid in the one or more independent microgrids.

5. The distributed microgrid (100) control system of claim 4, wherein the peer-to-peer network is a self-organizing network configured to perform the following: adding or removing at least one controller (107), adding or removing at least one power bus (103) and an accompanying set of power assets (101), adding or removing at least one circuit breaker (105), or a combination thereof.

6. A distributed microgrid (100) control system according to any one of the preceding claims, wherein the number of controllers (107) to independent microgrids assigned as the supervisors among the plurality of controllers (107) is equal to the number of independent microgrids, and wherein each of the one or more independent microgrids operates independently and asynchronously.

7. The distributed microgrid (100) control system according to any one of the preceding claims, wherein each controller (107) of the plurality of controllers (107) is further configured to: categorizing the set of electrical assets (101) based at least in part on asset type; Aggregating a group of power assets of the classification (101); determining an optimal power dispatch for the aggregated set of power assets; as well as The dispatch instructions for the electrical assets (101) are determined based at least in part on the optimal power dispatch.

8. The distributed microgrid (100) control system of any one of the preceding claims, wherein the plurality of controllers (107) in the peer-to-peer network are connected in a ring architecture configured to provide network redundancy.

9. The distributed microgrid (100) control system according to any one of the preceding claims, wherein each controller (107) of the plurality of controllers (107) is further configured to: processing historical data for a corresponding set of power assets (101) to determine power generation capabilities, wherein the historical data includes past power generation information; and The power generation capability is broadcasted to the plurality of controllers (107) via the peer-to-peer network to manage power distribution to a plurality of loads (113) connected to the plurality of controllers (107).

10. A distributed microgrid (100) control system according to any of the preceding claims, wherein the set of power assets (101) includes one or more generator sets, energy storage systems, photovoltaic groups, fuel cell groups, grid connections, wind turbines, water turbines, pumped water, or a combination thereof.

Images