Patent Description:
In recent years, there is provided a management system that includes an equipment and a management device that manages the equipment (for example, Patent Literature <NUM>). The equipment is an electrical appliance such as an air conditioner and a lighting device, and a distributed power source such as a solar cell, a storage battery, and a fuel power generation device. The management device is called, for example, Home Energy Management System (HEMS), Store Energy Management System (SEMS), Building Energy Management System (BEMS), Factory Energy Management System (FEMS), and Cluster/Community Energy Management System (CEMS). Further prior art can be found in document <CIT> disclosing a control device and a control method, or in document <CIT> addressing an energy management system and energy management method.

In order to popularize the management system, the communication standardization between the equipment and the management device is effective, and an attempt to standardize the communication is being made.

The present disclosure provides a management system according to claim <NUM>.

The present disclosure provides a management method according to claim <NUM>.

The present disclosure provides an equipment according to claim <NUM>.

In the following description of the drawings, the portions identical with or similar to each other will be attached with the same or similar symbol.

However, the drawings are schematically illustrated, and a ratio of each dimension may be different from the actual ratio. Therefore, specific dimensions should be determined with reference to the following description. Even in the drawings, there are included portion having a different relation of dimensions and a different ratio.

In the following, a management system according to the embodiment will be described. As illustrated in <FIG>, a management system <NUM> includes a facility <NUM> and an external server <NUM>. The facility <NUM> includes a router <NUM>. The router <NUM> is connected to the external server <NUM> through a network <NUM>. The router <NUM> forms a local area network, and is connected to the respective devices (for example, a communication device <NUM> of a PCS <NUM>, a load <NUM>, an EMS <NUM>, a display device <NUM>, etc.). In <FIG>, the solid line represents a power line, and the dotted line represents a signal line. Further, the invention is not limited to the above configuration, and the power line may transmit a signal.

The facility <NUM> includes a solar cell <NUM>, a storage battery <NUM>, the PCS <NUM>, a distribution board <NUM>, the load <NUM>, the EMS <NUM>, and the display device <NUM>.

The solar cell <NUM> is a device that generates power according to light receiving. The solar cell <NUM> outputs the generated DC power. A power generating amount of the solar cell <NUM> changes according to the amount of insolation irradiated to the solar cell <NUM>. In the embodiment, the solar cell <NUM> is an example of a distributed power source of which the output is can be controlled on the basis of an output control designated from a provider. However, the invention is not limited to the above configuration, and the storage battery <NUM> may be a distributed power source of which the output can be controlled on the basis of the output control designated from the provider.

The storage battery <NUM> is a device that accumulates power. The storage battery <NUM> outputs the accumulated DC power. In the embodiment, the storage battery <NUM> is an example of the distributed power source of which the output can be controlled on the basis of the output control designated from the provider.

The PCS <NUM> is an example of a power conditioning system (PCS) that converts the output power from the distributed power source. In the embodiment, the PCS <NUM> includes a conversion device <NUM> and the communication device <NUM>.

The conversion device <NUM> converts the DC power from the solar cell <NUM> into an AC power, and converts the DC power from the storage battery <NUM> into an AC power. Further, the conversion device <NUM> converts an AC power from a power grid <NUM> into a DC power. The conversion device <NUM> is connected to a trunk power line <NUM> (herein, a trunk power line 10LA and a trunk power line 10LB) connected to the power grid <NUM> through a first distribution board 140A, and connected to both of the solar cell <NUM> and the storage battery <NUM>. The trunk power line 10LA is a power line that connects the power grid <NUM> and the first distribution board 140A. The trunk power line 10LB is a power line that connects the first distribution board 140A and a second distribution board 140B. Further, in this embodiment, the conversion device <NUM> will be described about a hybrid power conditioning system that is connected to the solar cell <NUM> and the storage battery <NUM>, but the power condition system may be connected to each of the solar cell <NUM> and the storage battery <NUM>.

The communication device <NUM> is connected to the conversion device <NUM>, receives various types of messages to the conversion device <NUM>, and transmits various types of messages from the conversion device <NUM>. For the communication between the communication device <NUM> and the conversion device <NUM>, a protocol (for example, unique protocol) applied to the PCS <NUM> is used.

In the embodiment, the communication device <NUM> is connected to the router <NUM> in a wired or wireless manner. The communication device <NUM> is connected to the external server <NUM> through the router <NUM>, and receives an output control message designating the output control of the distributed power source from the external server <NUM>. Secondly, the communication device <NUM> is connected to the EMS <NUM> through the router <NUM>, and communicates with the EMS <NUM> as for a predetermined command of a predetermined format. The predetermined format is not particularly limited, and an ECHONET Lite system, a SEP2. <NUM> system, or a KNX system may be used for example.

As the predetermined format, a format in conformity to the ECHONET Lite system will be described for example. In such a case, the predetermined command may be roughly classified into a request command, a request response command that is a response to the request command, or an information notification command. The request command is, for example, a SET command or a GET command. The request response command is, for example, a SET response command that is a response to the SET command, and a GET response command that is a response to the GET command. The information notification command is, for example, an INF command.

The SET command is a command having a property that instructs a setting or an operation to the PCS <NUM>. The SET response command is a command indicating that the SET command is received. The GET command is a command containing a property indicating a state of the PCS <NUM>, and acquires the state of the PCS <NUM>. The GET response command is a command that contains a property indicating the state of the PCS <NUM>, and contains information requested by the GET command. The INF command is a command that contains a property indicating the state of the PCS <NUM>, and notifies the state of the PCS <NUM>.

The distribution board <NUM> is connected to the trunk power line <NUM>. The distribution board <NUM> includes the first distribution board 140A and the second distribution board 140B. The first distribution board 140A is connected to the power grid <NUM> through the trunk power line 10LA, and connected to the solar cell <NUM> and the storage battery <NUM> through the conversion device <NUM>. In addition, the first distribution board 140A controls the power output from the conversion device <NUM> and the power supplied from the power grid <NUM> to make the power flow to the trunk power line 10LB. The power flowing from the trunk power line 10LB is distributed to the respective equipment (herein, the load <NUM> and the EMS <NUM>) by the second distribution board 140B.

The load <NUM> is an device that consumes the power supplied through the power line. For example, the load <NUM> includes a device such as an air conditioner, a lighting device, a refrigerator, and a television. The load <NUM> may be a single device, or may be a plurality of devices.

The EMS <NUM> is a device (EMS; Energy Management System) that manages power information indicating the power in the facility <NUM>. The power in the facility <NUM> indicates the power flowing into the facility <NUM>, the power received by the facility <NUM>, or the power supplied from the facility <NUM>. Therefore, for example, the EMS <NUM> manages at least the PCS <NUM>.

The EMS <NUM> may control a power generating amount of the solar cell <NUM>, a charging amount of the storage battery <NUM>, and a discharging amount of the storage battery <NUM>. The EMS <NUM> may be configured to be integrally to the distribution board <NUM>. The EMS <NUM> is a device that is connected to the network <NUM>. The function of the EMS <NUM> may be provided by a cloud service through the network <NUM>.

In the embodiment, the EMS <NUM> is connected to the respective equipment (for example, the communication device <NUM> of the PCS <NUM> and the load <NUM>) through the router <NUM>, and communicates with the respective equipment as for a predetermined command of a predetermined format.

The EMS <NUM> is connected to the display device <NUM> through the router <NUM>, and communicates with the display device <NUM>. The EMS <NUM> may communicate with the display device <NUM> as for a predetermined command of a predetermined format. As described above, the predetermined format is a format in conformity to the ECHONET Lite system for example.

The display device <NUM> displays the power information indicating the power in the facility <NUM>. The display device <NUM> is, for example, a smart phone, a tablet, a digital television, or a dedicated terminal. The display device <NUM> is connected to the EMS <NUM> in a wired or wireless manner, and communicates with the EMS <NUM>. The display device <NUM> may communicate with the EMS <NUM> as for a predetermined command of a predetermined format. The display device <NUM> receives data necessary for the displaying of the power information from the EMS <NUM>.

The network <NUM> is a network that connects the EMS <NUM> and the external server <NUM>. The network <NUM> may be the Internet. The network <NUM> may include a mobile communication network. In addition, the network <NUM> may be a dedicated communication line, or may be a general communication line. For example, when the output of the solar cell <NUM> is equal to or more than a predetermined output, a dedicated communication line is used as the network <NUM> so as to perform the output control more reliably.

The external server <NUM> is a server that is managed by the provider such as an electric power provider, a power transmission/distribution provider, or a retailer. For example, the provider designates the output control of the distributed power source. Specifically, the external server <NUM> transmits the output control message to instruct the output control of the distributed power source. The external server <NUM> may transmit a command (DR; Demand Response) that is an instruction to suppress an amount of current from the power grid <NUM> to the facility <NUM>.

The output control message includes a target output control level that indicates a level of the output control of the distributed power source (herein, the solar cell <NUM>). The target output control level is determined according to the output (hereinafter, referred to as an equipment recognition output) that is recognized as the output capability (for example, rated output) of the PCS that controls the distributed power source. The target output control level may be displayed by an absolute value (for example, ∘∘ kW) that is determined according to the equipment recognition output, may be displayed by a relative value (for example, reduction by ∘∘ kW) with respect to the equipment recognition output, or may be displayed by a controlled rate (for example, ∘∘%) with respect to the equipment recognition output. Further, while the description has been made by the equipment recognition output, an equipment recognition capacity [kWh] may be employed.

When the output capability of the distributed power source and the output capability of the PCS are different, the equipment recognition output is set to a small one in these output capabilities. When a plurality of PCSs is provided, the equipment recognition output is a sum of the output capabilities of the plurality of PCSs.

In the embodiment, the output control message includes calendar information that indicates a schedule of the output control of the distributed power source. In the calendar information, the schedule of the output control of the distributed power source can be set at every <NUM> minutes. The calendar information may include a schedule of one day, may include a schedule of one month, or may include a schedule of one year.

In the embodiment, a predetermined period of time may be determined as a maximum period of time when the output control of the distributed power source is performed. For example, the predetermined period of time may be several days in one year (days rule), or may be an accumulated time in one year (accumulated time rule). More specifically, the predetermined period of time may be <NUM> days in one year (<NUM> days rule), or may be <NUM> hours in one year (<NUM> hours rule). However, the predetermined period of time may be not determined (designation rule). These rules represent a type of the output control of the distributed power source according to the output control message.

By the way, the above property includes a property indicating a variable (hereinafter, variable property) that can be changed by the operation of the equipment such as a charging amount setting value and a discharging amount setting value of the storage battery. In the following, the PCS <NUM> will be mainly exemplified as an equipment.

Under such an assumption, a case will be considered where a second command (for example, the GET command) is transmitted after a first command (for example, the SET command) is transmitted, and the EMS <NUM> acquires the variable property from the PCS <NUM>. In such a case, when the PCS <NUM> transmits a variable changed by the operation of the PCS <NUM> according to the second command, it is not possible for the EMS <NUM> to ascertain whether the PCS <NUM> is operating according to the first command transmitted by itself. Therefore, the PCS <NUM> is configured not to change the variable indicated by the variable property until the operation instructed by the first command is completed.

However, the variable is not changed in the process of the PCS <NUM>. Therefore, even when the EMS <NUM> receives the response command to the second command, it is not possible for the EMS <NUM> to ascertain whether the PCS <NUM> is operating according to the first command.

Regarding such a problem, the following management is performed in the embodiment. The EMS <NUM> transmits the first command to the PCS <NUM> to instruct the operation of the PCS <NUM>, and transmits the second command to the PCS <NUM> to request the state of the PCS <NUM>. The PCS <NUM> controls the operation of the PCS <NUM> according to the first command. The PCS <NUM> transmits the response command (for example, GET response command) that has a property indicating the state of the PCS <NUM> according to the second command to the EMS <NUM>. The properties of the first command and the second command include a variable property indicating a variable that is changed according to the operation of the PCS <NUM>. The PCS <NUM> keeps the variable indicated by the variable property without any change until the operation instructed by the first command is completed. The PCS <NUM> transmits the response command containing a specific value as the variable property to specify whether the operation is performed according to the first command. The response command is the request response command that contains the SET response command and the GET response command, or the information notification command that contains the INF command.

Herein, the specific value may include a first specific value indicating that the operation instructed by the first command is completed. In other words, when the operation instructed by the first command is completed, the PCS <NUM> transmits the second command containing the variable property indicating the first specific value to the EMS <NUM>. The first specific value may be different from the value that can be indicated by the variable property contained in the first command. The first specific value may be a value associated with the operation completion, or may be zero.

The specific value may contain a second specific value indicating that the operation instructed by the first command is released by a user. When the operation instructed by the first command is released by the user, the PCS <NUM> transmits the second command containing the variable property indicating the second specific value to the EMS <NUM>. The second specific value may be different to a value that can be indicated by the variable property contained in the first command. The second specific value may be a value associated with the operation release, or may be zero.

The specific value may include a third specific value indicating that the operation instructed by the first command is not operated or that the operation instructed by the first command is suspended. When the operation instructed by the first command is not operated, or when the operation instructed by the first command is suspended, the PCS <NUM> transmits the second command containing the variable property indicating the third specific value to the EMS <NUM>. The third specific value may be different from a value that is indicated by the variable property contained in the first command. The third specific value may be a value associated with the operation inexecution or the operation suspension, or may be zero.

Herein, the first specific value may be a value that is different from the second specific value and the third specific value. However, the first specific value may be the same value as the second specific value and the third specific value. Similarly, the second specific value may be a value different from the first specific value and the third specific value. However, the second specific value may be the same value as the first specific value and the third specific value. Similarly, the third specific value may be a value different from the first specific value and the second specific value. However, the third specific value may be the same value as the first specific value and the second specific value.

In the following, a communication device according to an embodiment will be described. As illustrated in <FIG>, the communication device <NUM> includes a first communication unit 132A, a second communication unit 132B, an interface 132C, and a controller 132D. Herein, the communication device <NUM> (that is, the PCS <NUM>) is an example of the equipment.

The first communication unit 132A receives the output control message instructing the output control of the distributed power source from the external server <NUM>. In the embodiment, the first communication unit 132A receives the output control message from the external server <NUM> without going through the EMS <NUM>.

The second communication unit 132B communicates with the EMS <NUM> as for a predetermined command of a predetermined format. As described above, the predetermined format is a format in conformity to the ECHONET Lite system for example. Herein, the predetermined format used in the communication between the communication device <NUM> (the second communication unit 132B) and the EMS <NUM> may be different from the format used in the communication between the communication device <NUM> (the first communication unit 132A) and the external server <NUM>. In addition, the predetermined format used in the communication between the second communication unit 132B (the second communication unit 132B) and the EMS <NUM> may be different from the format used in the communication between the communication device <NUM> (the interface 132C) and the conversion device <NUM>.

The interface 132C is an interface with respect to the conversion device <NUM>. The interface 132C may be a wired interface, or may be a wireless interface. For the communication between the communication device <NUM> and the conversion device <NUM>, a protocol (for example, unique protocol) applied to the PCS <NUM> is used.

The controller 132D is configured by a memory and a CPU, and controls the communication device <NUM>. For example, the controller 132D controls the conversion device <NUM> using the interface 132C so as to control the distributed power source according to the output control message. The controller 132D acquires the state (for example, a power generating amount of the solar cell <NUM>, a charging amount of the storage battery <NUM>, and a discharging amount of the storage battery <NUM>) of the conversion device <NUM> from the conversion device <NUM> using the interface 132C. The controller 132D generates a command to control the conversion device <NUM> on the basis of the command received from the EMS <NUM>, and outputs the command to the conversion device <NUM> using the interface 132C.

In the following, a management device according to an embodiment will be described. As illustrated in <FIG>, the EMS <NUM> includes a communication unit <NUM> and a controller <NUM>.

The communication unit <NUM> communicates with the communication device <NUM> as for a predetermined command of a predetermined format. As described above, the predetermined format is a format in conformity to the ECHONET Lite system for example.

The controller <NUM> is configured by a memory and a CPU, and controls the EMS <NUM>. The controller <NUM> may control the power generating amount of the solar cell <NUM>, a charging amount of the storage battery <NUM>, and a discharging amount of the storage battery <NUM>.

In the following, a message format according to an embodiment will be described. Herein, the description will be given about a case where the predetermined format is a format in conformity to the ECHONET Lite system.

As illustrated in <FIG>, a SET command M510 includes a header M511, a code M512, and a target property M513. In the embodiment, the SET command M510 is an example of the first command to instruct the operation of the PCS <NUM>, and is a command transmitted from the EMS <NUM> to the PCS <NUM>.

The header M511 is information indicating a destination of the SET command M510. The code M512 is information indicating a type of the message containing the code M512. Herein, the code M512 is information indicating that the message containing the code M512 is a SET command.

The target property M513 contains a property indicating an operation that is instructed to the PCS <NUM> by the EMS <NUM>. Such a property includes a variable property indicating a variable that is changed according to the operation of the PCS <NUM> for example. As the variable property, there is a setting value property that indicates a setting value of the charging/discharging amount of the storage battery <NUM>. The setting value of the charging/discharging amount collectively refers to as the setting value of the charging amount or the setting value of the discharging amount. The setting value of the charging/discharging amount may be either one of these two values or may be both of these two values. The setting value of the charging amount and the setting value of the discharging amount may contain information containing a type of power. The type of power is an alternating current (AC) or a direct current (DC).

The setting value property may be a property that designates a watt hour (Wh) of the charging or the discharging for example, or may be a property that designates a capacity (Ah) of the charging or the discharging. Further, the setting value designated by the setting value property may be an instantaneous power (W) of the charging or the discharging.

As illustrated in <FIG>, a SET response command M520 includes a header M521, a code M522, and a response content M523. In the embodiment, the SET response command M520 is an example of the command transmitted from the PCS <NUM> to the EMS <NUM> according to the command received from the EMS <NUM>.

The header M521 is information indicating a destination of the SET response command M520. The code M522 is information indicating a type of the message containing the code M522. Herein, the code M522 is information indicating that the message containing the code M522 is a SET response command. The response content M523 includes information indicating that the SET command is received. Such information may be a copy of the property contained in the SET command, or may be an acknowledgement (ACK). In addition, such information is not limited, and may be a response (Selective ACK) intending that only some data is correctly received.

As illustrated in <FIG>, a GET command M610 includes a header M611, a code M612, and a target property M613. In the embodiment, the GET command M610 is an example of the second command to request the state of the PCS <NUM>, and an example of the command transmitted from the EMS <NUM> to the PCS <NUM>.

The header M611 is information indicating a destination of the GET command M610. The code M612 is information indicating a type of the message containing the code M612. Herein, the code M612 is information indicating that the message containing the code M612 is the GET command. The target property M613 includes a property that the EMS <NUM> needs to know. Such a property includes the variable property similarly to the SET command for example. As the variable property, there is a setting value property that indicates a setting value of the charging/discharging amount of the storage battery <NUM> similarly to the SET command.

As illustrated in <FIG>, a GET response command M620 includes a header M621, a code M622, and a response content M623. In the embodiment, the GET response command M620 is an example of the command transmitted from the PCS <NUM> to the EMS <NUM> according to the command received from the EMS <NUM>.

The header M621 is information indicating a destination of the GET response command M620. The code M622 is information indicating a type of the message containing the code M622. Herein, the code M622 is information indicating that the message containing the code M622 is the GET response command. The response content M623 includes a property that is requested by the GET command. Such a property includes the variable property similarly to the SET command and the GET command for example. As the variable property, similarly to the SET command and the GET command, there is a setting value property that indicates a setting value of the charging/discharging amount of the storage battery <NUM>.

Herein, as described above, the GET response command includes a specific value as the variable property to specify whether the operation is performed according to the SET command.

In the following, a management method according to the embodiment will be described. Herein, the description will be given about a case where the predetermined format used in the communication between the PCS <NUM> (the communication device <NUM>) and the EMS <NUM> is a format in conformity to the ECHONET Lite system. A case where the SET command and the GET command contain the setting value property will be described.

First, the description will be given about a case where the PCS <NUM> starts the operation instructed by the SET command, and the PCS <NUM> completes the operation instructed by the SET command with reference to <FIG>.

In Step S11, the EMS <NUM> transmits the SET command containing the setting value property to the PCS <NUM>.

In Step S12, the PCS <NUM> transmits the SET response command with respect to the SET command to the EMS <NUM>.

In Step S13, the PCS <NUM> starts the operation instructed by the SET command. Herein, the SET command contains the setting value property, and the PCS <NUM> starts the control of the charging/discharging of the storage battery <NUM>. For example, when the setting value property is a property to instruct the charging amount, the PCS <NUM> starts the charging of the storage battery <NUM>. On the other hand, when the setting value property is a property to instruct the discharging amount, the PCS <NUM> starts the discharging of the storage battery <NUM>. However, the PCS <NUM> keeps the variable indicated by the variable property contained in the SET command without any change until the control of the charging/discharging of the storage battery <NUM> instructed by the SET command is completed.

In Step S14, the EMS <NUM> transmits the GET command containing the setting value property to the PCS <NUM>.

In Step S15, the PCS <NUM> transmits the GET response command with respect to the GET command to the EMS <NUM>. Herein, since the variable indicated by the variable property contained in the SET command is kept without any change, the PCS <NUM> transmits the GET response command containing a copy of the variable indicated by the SET command as the variable property. With this configuration, the EMS <NUM> can ascertain that the PCS <NUM> receives the SET command transmitted in Step S11. However, the EMS <NUM> hardly ascertains whether the PCS <NUM> is actually operated according to the SET command transmitted in Step S11.

In Step S16, the PCS <NUM> completes the operation instructed by the SET command. Herein, the PCS <NUM> completes the control of the charging/discharging of the storage battery <NUM>. Since the control of the charging/discharging of the storage battery <NUM> instructed by the SET command is completed, the variable indicated by the variable property contained in the SET command may be changed by the PCS <NUM>. Herein, the PCS <NUM> transitions from the control state of the charging/discharging to a standby state as the operation instructed by the SET command is completed.

In Step S17, the EMS <NUM> transmits the GET command containing the setting value property to the PCS <NUM>.

In Step S18, the PCS <NUM> transmits the GET response command with respect to the GET command to the EMS <NUM>. The PCS <NUM> transmits the GET response command containing the variable property indicating the first specific value that indicates that the operation instructed by the SET command is completed. The first specific value may be different from a value that is indicated by the variable property contained in the SET command. The first specific value may be a value associated with the operation completion, or may be zero.

Secondly, the description will be given with reference to <FIG> about a case where the PCS <NUM> starts the operation instructed by the SET command, and the operation instructed by the SET command is released or suspended. In <FIG>, the same processes as those of <FIG> will be attached with the same Step symbol. The processes of Steps S11 to S13 are the same as those of <FIG>, and the description thereof will be omitted.

In Step S21, the operation instructed by the SET command is released by the user. For example, the operation release may be an event in which the user releases the operation instructed by the SET command according to a provider's request. Alternatively, the operation instructed by the SET command is suspended. For example, the suspension of the operation may be an event in which an amount of residual charged power of the storage battery <NUM> is greater than a predetermined threshold when the setting value property is a property instructing the charging amount. Alternatively, the suspension of the operation may be an event in which the amount of residual charged power of the storage battery <NUM> is less than the threshold when the setting value property is a property instructing the discharging amount. Alternatively, the suspension of the operation may be failure or maintenance of any one of the storage battery <NUM> and the PCS <NUM>. The suspension of the operation may be a blackout of the power grid <NUM>. Alternatively, the suspension of the operation may be an event in which the operation designated by the SET command is released by the provider.

In Step S22, the EMS <NUM> transmits the GET command containing the setting value property to the PCS <NUM>.

In Step S23, the PCS <NUM> transmits the GET response command with respect to the GET command to the EMS <NUM>. The PCS <NUM> transmits the GET response command containing the variable property indicating the second specific value that indicates that the operation instructed by the SET command is released. The second specific value may be different from a value that is indicated by the variable property contained in the SET command. The second specific value may be a value associated with the operation release, or may be zero. Alternatively, the PCS <NUM> transmits the GET response command containing the variable property indicating the third specific value that indicates that the operation instructed by the SET command is suspended. The third specific value may be different from a value that is indicated by the variable property contained in the SET command. The third specific value may be a value associated with the operation suspension, or may be zero.

Thirdly, the description will be given with reference to <FIG> about a case where the PCS <NUM> does not perform the operation instructed by the SET command. In <FIG>, the same processes as those of <FIG> will be attached with the same Step symbol. The processes illustrated in <FIG> are the same as those of <FIG> except that the processes of Steps S13 and S21 are not performed.

In Step S23, the PCS <NUM> transmits the GET response command with respect to the GET command to the EMS <NUM> similarly to <FIG>. However, in <FIG>, the PCS <NUM> transmits the GET response command containing the variable property indicating the third specific value that indicates that the operation instructed by the SET command is not performed. The third specific value may be different from a value that is indicated by the variable property contained in the SET command. The third specific value may be a value associated with the operation inexecution, or may be zero.

For example, the inexeuction of the operation may be an event in which the operation designated by the SET command is restricted by the user. Alternatively, the inexeuction of the operation may be an event in which the operation designated by the SET command is restricted by the provider. Alternatively, the operation inexecution may be an event in which the operation does not start even though a predetermined period of time elapses after the SET command is received.

In the embodiment, when the properties of the SET command and the GET command include the variable property indicating a variable that can be changed according to the operation of the PCS <NUM>, the PCS <NUM> keeps the variable indicated by the variable property without any change until the operation instructed by the SET command is completed. The PCS <NUM> transmits the GET response command containing a specific value as the variable property to the EMS <NUM> to specify whether the operation is performed according to the SET command. With this configuration, the EMS <NUM> can determine whether the PCS <NUM> is actually operated according to the SET command on the basis of the specific value contained in the GET response command. For example, the EMS <NUM> can determine the operation completion, the operation release, the operation suspension, or the operation inexecution.

In the following, a first modification of the embodiment will be described. In the following, the first modification of the embodiment will be described.

In the first modification, the first command (that is, the SET command) can contain an operation mode property indicating an operation mode of the storage battery <NUM> in addition to the setting value property indicating a setting value of the charging/discharging amount of the storage battery <NUM>. The setting value property is contained in the first command that is transmitted earlier than the first command containing the operation mode property.

In such a case, the PCS <NUM> controls the charging/discharging of the storage battery <NUM> on the basis of the operation mode property after receiving the first command containing the operation mode property without starting the charging/discharging of the storage battery <NUM> even when the first command containing the setting value property is received.

For example, as illustrated in <FIG>, in Step S31, the EMS <NUM> transmits the SET command containing the setting value property to the PCS <NUM>.

In Step S32, the PCS <NUM> transmits the SET response command with respect to the SET command to the EMS <NUM>.

In Step S33, the PCS <NUM> receives the SET command containing the setting value property, but is on standby without starting the charging/discharging of the storage battery <NUM>.

In Step S34, the EMS <NUM> transmits the SET command containing the operation mode property to the PCS <NUM>.

In Step S35, the PCS <NUM> transmits the SET response command with respect to the SET command to the EMS <NUM>.

In Step S36, the PCS <NUM> controls the charging/discharging of the storage battery <NUM> on the basis of the operation mode property. The PCS <NUM> enables the setting value property received in Step S31 on the basis of the operation mode property. The enabling is to perform the charging/discharging of the storage battery <NUM> according to the charging/discharging amount indicated by the setting value property.

However, the PCS <NUM> may ignore the setting value property without enabling when the operation mode property and the setting value property are contradictable similarly to a case where the setting value property indicates the discharging amount in spite of the fact that the operation mode property indicates a charging mode.

In the following, a second modification of the embodiment will be described. In the following, the second modification of the embodiment will be described.

In the second modification, the first command (that is, the SET command) may contain the operation mode property indicating the operation mode of the storage battery <NUM> in addition to the setting value property indicating the setting value of the charging/discharging amount of the storage battery <NUM>. The setting value property is contained in the first command containing the operation mode property.

For example, as illustrated in <FIG>, in Step <NUM>, the EMS <NUM> transmits the SET command that contains the operation mode property and the setting value property to the PCS <NUM>.

In Step S42, the PCS <NUM> transmits the SET response command with respect to the SET command to the EMS <NUM>.

In Step S43, the PCS <NUM> controls the charging/discharging of the storage battery <NUM> on the basis of the operation mode property. Further, the PCS <NUM> performs the charging/discharging of the storage battery <NUM> according to the charging/discharging amount that is indicated by the setting value property.

However, the PCS <NUM> may ignore the setting value property when the operation mode property and the setting value property are contradictable similarly to a case where the setting value property indicates the discharging amount in spite of the fact that the operation mode property indicates a charging mode, and may control the charging/discharging of the storage battery <NUM> on the basis of the operation mode property.

The invention has been described using the above-described embodiment. However, it should be understood that the explanation and drawings representing part of the disclosure do not limit the invention. Various alternative embodiments, examples, and operating techniques may be apparent to a person skilled in the art from the disclosure.

In the embodiment, the description has been described about a case where the predetermined format used in the communication between the communication device <NUM> and the EMS <NUM> is a format in conformity to the ECHONET Lite system. However, the embodiment is not limited to such a configuration. Any format may be used as long as the predetermined format is a standard format used in the facility <NUM>.

In the embodiment, a case where the response command is the request response command containing the GET response command has been exemplified. However, the embodiment is not limited to such a configuration. The response command may be the information notification command containing the INF command. For example, the PCS <NUM> may transmit the information notification command containing the variable property to the EMS <NUM> when a predetermined condition is satisfied. The case where the predetermined condition is satisfied may be a case where the amount of residual charged power of the storage battery <NUM> is greater than a predetermined threshold, or may be a case where the amount of residual charged power of the storage battery <NUM> is less than the predetermined threshold. Further, the case where the predetermined condition is satisfied may be a case where a value indicated by the variable property is rewritten by a third person. For example, when the SET command containing the variable property is received two times, the INF command containing the variable property may be transmitted in response to the second reception of the SET command.

In the embodiment, the PCS <NUM> (multi-PCS) that controls the outputs of the solar cell <NUM> and the storage battery <NUM> has been exemplified. However, the embodiment is not limited to such a configuration. The PCS <NUM> may be a PCS that controls the output of the storage battery <NUM>.

In the embodiment, the PCS has been exemplified that controls the storage battery <NUM> as an equipment. However, the embodiment is not limited to such a configuration. The equipment may be a PCS that controls the output of the distributed power source such as the solar cell <NUM> and a fuel cell. The equipment may be the load <NUM> such as an air conditioner, a lighting device, a refrigerator, and a television. In other words, regardless of the type of the equipment, the properties of the first command and the second command may contain a variable property indicating a variable that can be changed according to the operation of the equipment.

In the embodiment, while not particularly limited, the storage battery <NUM> may be a storage battery provided in the facility <NUM>, or may be a storage battery provided in an electric vehicle (EV).

In the embodiment, the communication device <NUM> forms part of the PCS that controls the storage battery <NUM>, but the embodiment is not limited to the configuration. The communication device <NUM> may be a remote controller that is installed separately from the conversion device <NUM>. The remote controller may be considered to form part of the PCS that controls the storage battery <NUM>. The equipment managed by the management device (the EMS <NUM>) may be a remote controller.

Claim 1:
A management system (<NUM>), comprising:
a management device (EMS <NUM>), and
an equipment (<NUM>, <NUM>), wherein
the management device (EMS <NUM>) is configured to be connected to the equipment (<NUM>, <NUM>) provided in a facility (<NUM>) via a network provided in the facility (<NUM>), the management device (EMS <NUM>) comprising:
a transmitter (<NUM>) configured to transmit a first command to the equipment (<NUM>, <NUM>) to instruct an operation of the equipment (<NUM>, <NUM>), wherein a property included in the first command includes a variable property indicating a variable that can be changed by the operation of the equipment(<NUM>, <NUM>);
the equipment (<NUM>, <NUM>) comprising:
a controller (132D) configured to control the equipment (<NUM>, <NUM>) to start an operation of the equipment (<NUM>, <NUM>) instructed by the first command,
a transmitter (132B) configured to transmit a response command to the management device (EMS <NUM>), the response command containing a specific value as the variable property to specify whether the operation is performed according to the first command,
characterized in that
the controller (132D) is further configured to keep a variable, indicated by the variable property, without change when the operation instructed by the first command is ongoing; and
wherein the specific value is a different value from a value indicated by the variable property contained in the first command.