DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
Allowable Subject Matter
Claims 4-9 and 16-17 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1, 3, 10-15, and 18-19 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. The claims do not fall within at least one of the four categories of patent eligible subject matter because the claimed invention is directed to an abstract idea without significantly more.
The claims recite acquiring information and performing a prioritized dispatch operation (see claims 1, 10, 11, 12, 13, 14, 15). The claims further recite evaluating information and distributing loads based on the evaluated information (see claims 3, 18) and generating control signals (see claim 19). The acquiring, performing, evaluating, distributing, and generating, as briefly described above and as recited in claims 1, 3, 10-15, and 18-19, is mental processes (e.g., performing a prioritized dispatch operation as recited in claim 1). Accordingly, claims 1,3, 10-15, and 18-19 recite an abstract idea because the particular limitations, as briefly outlined above, fall into at least one of the groupings of abstract ideas (see MPEP 2106.04(a)).
This judicial exception is not integrated into a practical application because the claim limitations are directed to the generality of performing a prioritized dispatch operation (e.g., see claim 1). In other words, the claim limitations are generally performing a prioritized dispatch operation based on information and these generally applicable claim limitations are not particularly tied to a system. Furthermore, the claim limitations are not directed to an application for any particular system and the application is only nominally directed to an application for various systems (e.g., see paragraph 0001 of the specification as filed). In other words, the claim limitations are not providing meaningful limitations to the controller or method. Finally, the controller and method, as recited in independent claims 1 and 18-19, are merely the field of use of the dispatch planning as the elements are not integrated into the claim limitations. In other words, the microgrid controller and method are no more than a general link to the technology environment and do not provide any meaningful limitations to the claims.
The claims do not include additional elements, individually or in combination, that are sufficient to amount to significantly more than the judicial exception because the microgrid controller, communication interface, energy storage system, non-ESSs, and processors, as recited in claims 1, 3, 10-15, and 18-19, are generic elements. Furthermore, the claim limitations are implemented on these generic elements. In other words, the claim limitations are being implemented on these units and are not specifically liked to these elements.
Accordingly, these claims are rejected under 35 U.S.C. 101.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1-3, 10-15, and 18-20 are rejected under 35 U.S.C. 102(a)(1) as being unpatentable by
U.S. Patent No. 11,782,399 (Buttgenbach).
Claim 1:
The cited prior art describes a microgrid controller of a microgrid, comprising: (Buttgenbach: see the controller 204 as illustrated in figure 2; “A renewable energy source/energy storage system (RES-ESS) may include a renewable energy source (RES) configured to generate power from renewable sources (e.g., solar, wind, etc.) and an energy storage system (ESS), such as a battery bank, configured to store energy. The RES-ESS may be connected to a power grid, and both the RES and the ESS may supply power to the grid. The grid may also supply power to the ESS.” Col. 2, lines 4-11)
a communication interface configured to (Buttgenbach: see the communication interface 234 as illustrated in figure 2)
receive load information corresponding to a plurality of loads connected to the microgrid, (Buttgenbach: “the mode determination module 230 receives a message indicating a high demand for power from the BTM load” col. 9, lines 29-31; “For example, the user interface module 228 may generate a user interface that indicates the measurements from the flow meters 210, information regarding the demand from the grid 306 and the BTM load 314, and other information regarding the RES-ESS 300.” Col. 9, lines 3-7; “For example, the mode determination module 230 may receive information via the communications interface 234 regarding current and expected weather conditions, current and expected power demand from the grid 306 and BTM load 314, the time of day, the time of year, etc.” col. 9, lines 21-26)
receive energy resource information corresponding to a plurality of energy resource systems connected to the microgrid, and (Buttgenbach: “As shown in FIG. 1A, certain embodiments may utilize readily available electric power meters, such as a RES-ESS electrical power meter 32 to measure RES-ESS (e.g., PV+S) facility output, a RES electrical power meter 19 to measure RES output, and an ESS electrical power meter 29 to measure ESS output. Signals from the RES electrical power meter 19 are provided to the RES SCADA controller 12, and signals from the ESS electrical power meter 29 are provided to the ESS controller 22.” Col. 5, lines 23-31)
output control signals for controlling an operation of each energy resource system of the plurality of energy resource systems, (Buttgenbach: “In certain embodiments, a RES-ESS dispatcher unit 36 can control the charge or discharge of the energy storage device 24 (e.g., batteries) by communicating with an ESS controller 22.” Col. 5, lines 1-4; “In brief overview, the components 222-232 may cooperate to control the flow of power between components of the RES-ESS 300 (e.g., the grid 306, the RES 308, the BTM load 314, and the ESS 316). The components 222-232 may receive instructions to deliver power from the RES 308 and/or the grid 306 to the ESS 316 and/or the BTM load 314 or from the RES 308 and/or the ESS 316 to the BTM load 314 and/or the grid 306. The components 222-232 may then operate the flow control equipment 312 to adjust the flow of power between the grid 306, the RES 308, the BTM load 314, and the ESS 316” col. 7, lines 27-38)
wherein the plurality of energy resource systems includes (Buttgenbach: see the energy resources 14, 24A-24N in the facility 11 as illustrated in figure 1B)
a plurality of energy storage systems (ESSs) configured to be charged and discharged, and (Buttgenbach: see the energy storage units 24A-24N as illustrated in figure 1B)
a plurality of non-ESSs, including (Buttgenbach: see the renewable generation 14A-14N as illustrated in figure 1B)
a plurality of unidirectional non-ESSs configured to supply power to the microgrid, and (Buttgenbach: see the wind generation as described in col. 9, lines 35-62; see the renewable generation 14A-14N as illustrated in figure 1B; “The RES 308 may be or may include a solar power plant, a wind turbine power plant, a geothermal power plant, a hydroelectric power plant, or other renewable power plants.” Col. 9, lines 63-65)
a plurality of bidirectional non-ESSs configured to supply power to the microgrid or absorb power from the microgrid; and (Buttgenbach: see the solar generation as described in col. 5, lines 1-22; see the renewable generation 14A-14N as illustrated in figure 1B; “The RES 308 may be or may include a solar power plant, a wind turbine power plant, a geothermal power plant, a hydroelectric power plant, or other renewable power plants.” Col. 9, lines 63-65)
one or more processors configured to perform at least two dispatch operations selected from (Buttgenbach: see the processor 218 as illustrated in figure 2)
a load balance dispatch operation, (Buttgenbach: “In BTM-ESS mode, the system may prioritize supplying power to the BTM load over supplying power to the ESS or the grid and may prioritize supplying power to the ESS over supplying power to the grid.” Col. 2, lines 54-58; see the BTM-ESS mode as illustrated in figure 4 and as described in col. 13, lines 9-28)
an export dispatch operation, or (Buttgenbach: “A Grid-ESS mode may be selected when grid demand is relatively high. In Grid-ESS mode, the system may prioritize supplying power to the grid over supplying power to the ESS or the BTM load and may prioritize supplying power to the ESS over supplying power to the BTM load.” Col. 2, lines 58-63; see the Grid-ESS mode as illustrated in figure 5)
a charge/discharge dispatch operation (Buttgenbach: “Other control modes are possible, such as modes that prioritize supplying power to the ESS over supplying power to the grid and the BTM load.” Col. 3, lines 8-10)
according to a prioritization dispatch scheme, wherein the load balance dispatch operation, the export dispatch operation, and the charge/discharge dispatch operation are assigned different dispatch priorities that define a sequence of dispatch operations of the prioritization dispatch scheme. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 2:
The cited prior art describes the microgrid controller of claim 1,
wherein the one or more processors are configured to, during the load balance dispatch operation, distribute a total load or a portion of the total load among the plurality of unidirectional non-ESSs, (Buttgenbach: “In BTM-ESS mode, the system may prioritize supplying power to the BTM load over supplying power to the ESS or the grid and may prioritize supplying power to the ESS over supplying power to the grid.” Col. 2, lines 54-58; see the BTM-ESS mode as illustrated in figure 4 and as described in col. 13, lines 9-28)
wherein the one or more processors are configured to, during the export dispatch operation, export power from at least one non-ESS or from at least one ESS to at least one bidirectional non-ESS based on any export restrictions placed on the plurality of non-ESSs and the plurality of ESSs, and (Buttgenbach: “A Grid-ESS mode may be selected when grid demand is relatively high. In Grid-ESS mode, the system may prioritize supplying power to the grid over supplying power to the ESS or the BTM load and may prioritize supplying power to the ESS over supplying power to the BTM load.” Col. 2, lines 58-63; see the Grid-ESS mode as illustrated in figure 5)
wherein the one or more processors are configured to, during the charge/discharge dispatch operation, charge or discharge the plurality of ESSs based on any charge restrictions placed on the plurality of non-ESSs. (Buttgenbach: “Other control modes are possible, such as modes that prioritize supplying power to the ESS over supplying power to the grid and the BTM load.” Col. 3, lines 8-10)
Claim 3:
The cited prior art describes the microgrid controller of claim 1, wherein, for the load balance dispatch operation, the one or more processors are configured to:
evaluate priority information defining priority levels for the plurality of non-ESSs, wherein each non-ESS is assigned a different priority level, (Buttgenbach: see the determining the order of power usage 418, 412, 422 for the BTM-ESS mode 402 as illustrated in figure 4)
evaluate a respective power operating level for each non-ESS, (Buttgenbach: see the determine maximum grid power flow and renewable power output as illustrated in figure 4)
calculate a total load based on the load information, and (Buttgenbach: see the determine maximum BTM power flow rate as illustrated in figure 4)
distribute the total load among the plurality of non-ESSs based on the priority levels and respective power operating levels of the plurality of non-ESSs such that the plurality of non-ESSs are dispatched from a highest priority level to a lowest priority level in accordance with the respective power operating levels. (Buttgenbach: see the supply of power to the load based on the various inputs and prioritization as illustrated in figure 4)
Claim 10:
The cited prior art describes the microgrid controller of claim 1, wherein the sequence of dispatch operations includes first performing the load balance dispatch operation followed by performing the export dispatch operation. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 11:
The cited prior art describes the microgrid controller of claim 10, wherein the sequence of dispatch operations includes performing the charge/discharge dispatch operation after performing the export dispatch operation. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 12:
The cited prior art describes the microgrid controller of claim 1, wherein the sequence of dispatch operations includes first performing the export dispatch operation followed by performing the load balance dispatch operation. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 13:
The cited prior art describes the microgrid controller of claim 12, wherein the sequence of dispatch operations includes performing the charge/discharge dispatch operation after performing the load balance dispatch operation. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 14:
The cited prior art describes the microgrid controller of claim 1, wherein the sequence of dispatch operations includes first performing the export dispatch operation followed by performing the charge/discharge dispatch operation. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 15:
The cited prior art describes the microgrid controller of claim 14, wherein the sequence of dispatch operations includes performing the load balance dispatch operation after performing the charge/discharge dispatch operation. (Buttgenbach: “The controller 204 may receive instructions to control the RES-ESS 300 in BTM-ESS mode (e.g., in operation 402 of the method 400) or in Grid-ESS mode (e.g., in operation 502 of the method 500) based on a preset schedule.” Col. 20, lines 34-37; “The mode determination module 230 may determine the most efficient prioritization mode based on various data. The mode determination module 230 may override the scheduled prioritization mode retrieved by the schedule retriever 222 when a more efficient mode is available under current or future conditions.” Col. 9, lines 16-21; “For example, the prioritization schedule may indicate that providing power to an ESS is a higher priority than providing power to a behind-the meter (BTM) load or a power grid. The schedule retriever 222 may retrieve the prioritization schedule from the schedule database 232 (e.g., a relational database) based on the time period of the prioritization schedule. For example, the schedule database 232 may store multiple prioritization schedules for future time periods. Each prioritization schedule may include time stamps indicating the beginning and/or the end of the time period of the respective prioritization schedule. The schedule retriever 222 may identify the beginning time (and/or date) of each schedule and retrieve the schedule with a beginning time closest to the current time. In some embodiments, the prioritization schedules may be sequentially numbered and the schedule retriever 222 may identify and retrieve the prioritization schedule with the lowest (or highest depending on the configuration) sequential value in the schedule database 232, in some cases subsequent to a previously retrieved schedule.” Col. 7, line 50 through col. 8, line 2)
Claim 18:
The cited prior art describes a microgrid controller of a microgrid, comprising: (Buttgenbach: see the controller 204 as illustrated in figure 2; “A renewable energy source/energy storage system (RES-ESS) may include a renewable energy source (RES) configured to generate power from renewable sources (e.g., solar, wind, etc.) and an energy storage system (ESS), such as a battery bank, configured to store energy. The RES-ESS may be connected to a power grid, and both the RES and the ESS may supply power to the grid. The grid may also supply power to the ESS.” Col. 2, lines 4-11)
a communication interface configured to (Buttgenbach: see the communication interface 234 as illustrated in figure 2)
receive load information corresponding to a plurality of loads connected to the microgrid, , (Buttgenbach: “the mode determination module 230 receives a message indicating a high demand for power from the BTM load” col. 9, lines 29-31; “For example, the user interface module 228 may generate a user interface that indicates the measurements from the flow meters 210, information regarding the demand from the grid 306 and the BTM load 314, and other information regarding the RES-ESS 300.” Col. 9, lines 3-7; “For example, the mode determination module 230 may receive information via the communications interface 234 regarding current and expected weather conditions, current and expected power demand from the grid 306 and BTM load 314, the time of day, the time of year, etc.” col. 9, lines 21-26)
receive energy resource information corresponding to a plurality of energy resource systems connected to the microgrid, and (Buttgenbach: “As shown in FIG. 1A, certain embodiments may utilize readily available electric power meters, such as a RES-ESS electrical power meter 32 to measure RES-ESS (e.g., PV+S) facility output, a RES electrical power meter 19 to measure RES output, and an ESS electrical power meter 29 to measure ESS output. Signals from the RES electrical power meter 19 are provided to the RES SCADA controller 12, and signals from the ESS electrical power meter 29 are provided to the ESS controller 22.” Col. 5, lines 23-31)
output control signals for controlling an operation of each energy resource system of the plurality of energy resource systems, , (Buttgenbach: “In certain embodiments, a RES-ESS dispatcher unit 36 can control the charge or discharge of the energy storage device 24 (e.g., batteries) by communicating with an ESS controller 22.” Col. 5, lines 1-4; “In brief overview, the components 222-232 may cooperate to control the flow of power between components of the RES-ESS 300 (e.g., the grid 306, the RES 308, the BTM load 314, and the ESS 316). The components 222-232 may receive instructions to deliver power from the RES 308 and/or the grid 306 to the ESS 316 and/or the BTM load 314 or from the RES 308 and/or the ESS 316 to the BTM load 314 and/or the grid 306. The components 222-232 may then operate the flow control equipment 312 to adjust the flow of power between the grid 306, the RES 308, the BTM load 314, and the ESS 316” col. 7, lines 27-38)
wherein the plurality of energy resource systems includes (Buttgenbach: see the energy resources 14, 24A-24N in the facility 11 as illustrated in figure 1B)
a plurality of energy storage systems (ESSs) configured to be charged and discharged, and (Buttgenbach: see the energy storage units 24A-24N as illustrated in figure 1B)
a plurality of non-ESSs, including (Buttgenbach: see the renewable generation 14A-14N as illustrated in figure 1B)
a plurality of unidirectional non-ESSs configured to supply power to the microgrid, and (Buttgenbach: see the wind generation as described in col. 9, lines 35-62; see the renewable generation 14A-14N as illustrated in figure 1B; “The RES 308 may be or may include a solar power plant, a wind turbine power plant, a geothermal power plant, a hydroelectric power plant, or other renewable power plants.” Col. 9, lines 63-65)
a plurality of bidirectional non-ESSs configured to supply power to the microgrid or absorb power from the microgrid; and (Buttgenbach: see the solar generation as described in col. 5, lines 1-22; see the renewable generation 14A-14N as illustrated in figure 1B; “The RES 308 may be or may include a solar power plant, a wind turbine power plant, a geothermal power plant, a hydroelectric power plant, or other renewable power plants.” Col. 9, lines 63-65)
one or more processors configured to perform at least one dispatch operation, including a load balance dispatch operation, (Buttgenbach: see the processor 218 as illustrated in figure 2; “In BTM-ESS mode, the system may prioritize supplying power to the BTM load over supplying power to the ESS or the grid and may prioritize supplying power to the ESS over supplying power to the grid.” Col. 2, lines 54-58; see the BTM-ESS mode as illustrated in figure 4 and as described in col. 13, lines 9-28)
wherein performing the load balance dispatch operation includes:
evaluating priority information defining priority levels for the plurality of non-ESSs, wherein each non-ESS is assigned a different priority level, (Buttgenbach: see the determining the order of power usage 418, 412, 422 for the BTM-ESS mode 402 as illustrated in figure 4)
evaluating a respective power operating level for each non-ESS, (Buttgenbach: see the determine maximum grid
calculating a total load or a remaining total load based on the load information, and (Buttgenbach: see the determine maximum BTM power flow rate as illustrated in figure 4)
distributing the total load or a remaining total load among the plurality of non-ESSs based on the priority levels and respective power operating levels of the plurality of non-ESSs such that the plurality of non-ESSs are dispatched from a highest priority level to a lowest priority level in accordance with the respective power operating levels. (Buttgenbach: see the supply of power to the load based on the various inputs and prioritization as illustrated in figure 4)
Claim 19:
Claim 19 is substantially similar to claim 1 and is rejected based on the same reasons and rationale.
19. A control method, comprising:
receiving, by a microgrid controller of a microgrid, load information corresponding to a plurality of loads connected to the microgrid;
receiving, by the microgrid controller, energy resource information corresponding to a plurality of energy resource systems connected to the microgrid, wherein the plurality of energy resource systems includes
a plurality of energy storage systems (ESSs) configured to be charged and discharged, and
a plurality of non-ESSs, including
a plurality of unidirectional non-ESSs configured to supply power to the microgrid, and
a plurality of bidirectional non-ESSs configured to supply power to the microgrid or absorb power from the microgrid;
assigning, by the microgrid controller, different dispatch priorities to a plurality of dispatch operations that define a sequence of dispatch operations of a prioritization dispatch scheme;
wherein the plurality of dispatch operations include at least two dispatch operations selected from
a load balance dispatch operation,
an export dispatch operation, or
a charge/discharge dispatch operation,
wherein the load balance dispatch operation, the export dispatch operation, and the charge/discharge dispatch operation are assigned the different dispatch priorities that define the sequence of dispatch operations of the prioritization dispatch scheme; and
generating, by the microgrid controller, control signals for controlling the plurality of energy resource systems based on the prioritization dispatch scheme.
Claim 20:
Claim 20 is substantially similar to claim 2 and is rejected based on the same reasons and rationale.
20. The control method of claim 19, wherein:
during the load balance dispatch operation, distributing a total load or a portion of the total load among the plurality of unidirectional non-ESSs,
during the export dispatch operation, exporting power from at least one non-ESS or from at least one ESS to at least one bidirectional non-ESS based on any export restrictions placed on the plurality of non-ESSs and the plurality of ESSs, and
during the charge/discharge dispatch operation, charging or discharging the plurality of ESSs based on any charge restrictions placed on the plurality of non-ESSs.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
U.S. Patent Application Publication No. 2014/0277797 describes determining optimal scheduling and dispatch of power resources.
U.S. Patent Application Publication No. 2014/0039710 describes optimal planning and real-time control of energy storage systems.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHRISTOPHER E EVERETT whose telephone number is (571)272-2851. The examiner can normally be reached Monday-Friday 8:00 am to 5:00 pm (Pacific).
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Robert Fennema can be reached at 571-272-2748. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/Christopher E. Everett/Primary Examiner, Art Unit 2117
Prosecution Insights