Equipment management system, equipment management device, equipment management method, and program

Abstract

To provide an equipment management system, an equipment management device, an equipment management method, and a program that enable a user to quickly grasp the occurrence of an abnormality in equipment when the abnormality occurs in the equipment.SOLUTION: An equipment management system includes a terminal device 4 owned by a user, an equipment status acquisition unit 111 that acquires equipment status information indicating the status of each of multiple pieces of equipment 3, an abnormality determination unit 112 that determines that a communication abnormality has occurred between the corresponding equipment 3 when the elapsed time since the equipment status information has been last acquired for each of the multiple pieces of equipment 3 exceeds a predetermined reference time, and an equipment status notification unit 114 that transmits equipment status information indicating the communication abnormality to the terminal device 4 when a communication abnormality has occurred.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to a device management system, a device management apparatus, a device management method, and a program. [Background technology]

[0002] A water heater control device has been proposed that controls the heating operation of multiple storage-type water heaters (see, for example, Patent Document 1). This water heater control device predicts the future total power consumption of electrical devices other than the water heaters in a house in which each of the multiple water heaters is installed, and the amount of hot water used in each house, and generates an operation schedule for each of the multiple water heaters so that the sum of the power consumption of each of the multiple water heaters and the above-mentioned total power consumption is reduced to below a preset power consumption threshold. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-137215 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in a water heater control device such as that described in Patent Document 1, if communication with a water heater is interrupted, it becomes impossible to accurately monitor the power consumption of the water heater, and as a result, there is a risk that the peak power consumption in multiple homes as a whole will greatly exceed the peak expected when the operation schedule was generated. For this reason, there is a demand for monitoring the communication status with the water heater, and if the communication status deteriorates, allowing the administrator to quickly understand this, thereby achieving early recovery of the communication status of the equipment and continuing stable leveling control of the total power consumption of multiple water heaters.

[0005] The present disclosure has been made in consideration of the above-mentioned reasons, and aims to provide an equipment management system, an equipment management device, an equipment management method, and a program that enable a user to quickly grasp the occurrence of an abnormality in an equipment when an abnormality occurs in the equipment. [Means for solving the problem]

[0006] In order to achieve the above object, a device management device according to the present disclosure includes: A first terminal device owned by a user; a device status acquisition unit that acquires device status information indicating a status of each of the plurality of devices; an abnormality determination unit that determines that a communication abnormality has occurred between the corresponding device and each of the plurality of devices when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; and a device status notifying unit that, when the communication abnormality occurs, transmits the device status information indicating the communication abnormality to the first terminal device. Effect of the Invention

[0007] According to the present disclosure, when the time elapsed since the last time the device status information was acquired for each of the plurality of devices exceeds a preset reference time, the abnormality determination unit determines that a communication abnormality has occurred between the corresponding device. Then, when a communication abnormality occurs, the device status notification unit transmits device status information indicating the communication abnormality to a terminal device held by a user. In this way, when a communication abnormality occurs between a device and a device management device, the occurrence of the communication abnormality is promptly transmitted to the terminal device, so that the user can promptly grasp the occurrence of the communication abnormality. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic configuration diagram of a device management system according to a first embodiment of the present disclosure. [Diagram 2] FIG. 1 is a block diagram showing a hardware configuration of a device management system according to a first embodiment. [Diagram 3]FIG. 1 is a block diagram showing a functional configuration of a device management system according to a first embodiment. [Figure 4] FIG. 1A is a diagram showing an example of information stored in a device status storage unit according to the first embodiment, and FIG. 1B is a diagram showing another example of information stored in a device status storage unit according to the first embodiment. [Diagram 5] FIG. 11 is a sequence diagram showing an example of the operation of the device management system according to the first embodiment; [Figure 6] FIG. 13 is a diagram showing an example of a device state notification image displayed on a display unit of a terminal device according to the first embodiment; [Figure 7] FIG. 13 is a diagram showing an example of a device state notification image displayed on a display unit of a terminal device according to the first embodiment; [Figure 8] FIG. 11 is a sequence diagram showing an example of the operation of the device management system according to the first embodiment; [Figure 9] FIG. 1A is a diagram showing an example of a tally result notification image displayed on a display unit of a terminal device according to a first embodiment; FIG. 1B is a diagram showing another example of a tally result notification image displayed on a display unit of a terminal device according to a first embodiment; [Figure 10] FIG. 1A is a diagram showing an example of an abnormality occurrence status detail notification image displayed on a display unit of a terminal device according to the first embodiment, and FIG. 1B is a diagram showing an example of an email viewing image displayed on a display unit of a terminal device according to the first embodiment. [Figure 11] 1 is a flowchart showing an example of the flow of a device management process executed by a cloud server according to the first embodiment. [Figure 12] FIG. 1 is a schematic configuration diagram of a device management system according to a second embodiment of the present disclosure. [Figure 13] FIG. 11 is a block diagram showing a hardware configuration of a device management system according to a second embodiment. [Figure 14] FIG. 11 is a block diagram showing a functional configuration of a device management system according to a second embodiment. [Figure 15] FIG. 13 is a diagram showing an example of information stored in a device state storage unit according to the second embodiment; [Figure 16] FIG. 11 is a sequence diagram showing an example of the operation of the device management system according to the second embodiment. [Figure 17]FIG. 10A is a diagram showing an example of a communication interruption notification image displayed on a display unit of a terminal device according to a second embodiment, and FIG. 10B is a diagram showing an example of a communication status check prompt image displayed on a display unit of a terminal device according to a second embodiment. [Figure 18] FIG. 11 is a sequence diagram showing an example of the operation of the device management system according to the second embodiment. [Figure 19] FIG. 13 is a diagram showing an example of a device state notification image displayed on a display unit of a terminal device according to the second embodiment; [Figure 20] 11 is a flowchart showing an example of the flow of a device management process executed by a cloud server according to a second embodiment. [Figure 21] A flowchart showing an example of a flow of a communication abnormality occurrence location identification process executed by a terminal device according to a second embodiment. [Figure 22] FIG. 11 is a block diagram showing a functional configuration of a device management system according to a third embodiment of the present disclosure. [Diagram 23] FIG. 13 is a diagram showing an example of information stored in a device state storage unit according to the third embodiment; [Figure 24] FIG. 13 is a diagram illustrating an example of information stored in an abnormal device status storage unit according to the third embodiment. [Diagram 25] FIG. 11 is a sequence diagram showing an example of the operation of the device management system according to the third embodiment. [Figure 26] FIG. 13 is a diagram showing an example of a tally result notification image displayed on a terminal device according to the third embodiment; [Figure 27] FIG. 10A is a diagram showing an example of an abnormality occurrence status detail notification image displayed on a display unit of a terminal device according to a third embodiment, and FIG. 10B is a diagram showing an example of an email viewing image displayed on a display unit of a terminal device according to a third embodiment. [Figure 28] FIG. 11 is a sequence diagram showing an example of the operation of the device management system according to the third embodiment. [Figure 29] 11 is a flowchart showing an example of the flow of a device management process executed by a cloud server according to a third embodiment. [Diagram 30] FIG. 1A is a diagram showing an example of a portion of a device status notification image displayed on a display unit of a terminal device according to a modified example; FIG. 1B is a diagram showing another example of a portion of a device status notification image displayed on a display unit of a terminal device according to a modified example; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment 1) Hereinafter, a device management system according to an embodiment of the present disclosure will be described with reference to the drawings. The device management system according to the embodiment includes a first terminal device owned by a user, a device status acquisition unit that acquires device status information indicating the status of each of a plurality of devices, an abnormality determination unit that determines that a communication abnormality has occurred between the corresponding device and each of the plurality of devices when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time, and a device status notification unit that transmits device status information indicating the communication abnormality to the first terminal device when the communication abnormality has occurred.

[0010] The device management system according to the present embodiment is used for an apartment complex B[0], B[1], ...B[j], ...(j is an integer of 0 or more) which is a building constituting a group of dwelling units H[0,0], H[0,1], ..., H[0,i], ...(i is an integer of 0 or more) as shown in FIG. 1. Here, the apartment complex B[j] is, for example, an apartment house which receives power by a high-voltage collective power receiving method. In each dwelling unit H[j,i], a device 3, a communication control device 2 which can communicate with the device 3 via a local network NW2 constructed in each dwelling unit H[j,i], and a broadband router (hereinafter referred to as "BBR") 8 which can communicate with the communication control device 2 via the local network NW2 are installed. The local network NW2 is a wireless LAN (Local Area Network) or a wired LAN. In addition, the BBR 8 is connected to a wide area network NW1 such as the Internet. The device management system according to this embodiment includes a terminal device 4 managed by a so-called aggregator that manages the power supply to the apartment building B[j], and a cloud server 1. The terminal device 4 and the cloud server 1 are capable of communicating with each other via a wide area network NW1. Furthermore, the cloud server 1 and the terminal device 4 are each capable of communicating with a mail server 6 that manages users' mail information, via the wide area network NW1.

[0011] The mail server 6 includes a mail storage unit (not shown) that stores message information included in the mail information of a user and user identification information that identifies the user in association with each other. When the mail server 6 receives mail request information (described later) sent from the terminal device 4, it identifies message information corresponding to the user identification information included in the received mail request information from the message information stored in the mail storage unit, and transmits the mail information including the identified message information to the terminal device 4 that is the sender of the mail request information.

[0012] The device 3 is, for example, an electric device such as an air conditioner, a lighting device, a floor heating system, a refrigerator, an IH (Induction Heating) cooker, a television, etc. The device 3 includes a clock unit (not shown) that measures time, and when it is determined based on the measured time that a preset device status notification time for notifying the device of its own status has arrived, the device 3 generates device status notification information including device status information indicating the device's status, device identification information for identifying the device, and apartment identification information, location identification information, and floor information for identifying the apartment B[j], location, and floor in which the device 3 is installed, and transmits the generated device status notification information to the cloud server 1 via the local network NW2, the communication control device 2, the BBR8, and the wide area network NW1. Here, the device status notification time can be set to arrive periodically at intervals of, for example, several seconds to several minutes. Note that the cycle and timing at which the device status notification time arrives may not be the same for multiple devices 3.

[0013] When the communication control device 2 acquires device status notification information transmitted from the device 3, it adds header information to the acquired device status notification information specifying the cloud server 1 as the destination and its own device as the source, and then transmits the device status notification information to the cloud server 1 via the BBR8 and the wide area network NW1.

[0014] The terminal device 4 is, for example, a general-purpose personal computer, and includes a CPU (Central Processing Unit) 401, a main memory unit 402, an auxiliary memory unit 403, a display unit 404, an input unit 405, and a communication unit 406 as shown in FIG. 2, and is used by a user belonging to the aggregator. Here, the main memory unit 402 is a volatile memory such as a RAM (Random Access Memory), and is used as a working area for the CPU 401. The auxiliary memory unit 403 includes, for example, a ROM (Read Only Memory), a non-volatile memory such as a semiconductor flash memory, an SSD (Solid State Drive), an HDD (Hard Disk Drive), or the like, and stores programs for realizing various functions of the terminal device 4. The display unit 404 is a liquid crystal display, an organic EL (Electro-luminescence) display, or the like, and displays various information. The input unit 405 is, for example, a keyboard, and accepts an operation of a user belonging to the aggregator and outputs information indicating the accepted operation content to the CPU. The communication unit 406 has an interface for connecting to the wide area network NW1.

[0015] The CPU 401 reads out the programs stored in the auxiliary storage unit 403 into the main storage unit 402 and executes them, thereby functioning as a monitoring information acquisition unit 411, an abnormality occurrence status acquisition unit 412, a display control unit 413, an occurrence status detailed notification request unit 414, and an email acquisition unit 415, as shown in Fig. 3. The auxiliary storage unit 403 shown in Fig. 2 also has a device status storage unit 431 and an abnormality occurrence status storage unit 432, as shown in Fig. 3. The device status storage unit 431 stores device status information indicating the status of the device 3 installed in each dwelling unit H[j,i] of each of a plurality of apartment buildings B[j] managed by the aggregator, in association with device identification information of the device 3, location identification information identifying each dwelling unit H[j,i] in which the device 3 is installed, and date and time information indicating the date and time when the cloud server 1 acquired the device status information. In addition, the device status memory unit 431 further stores the device status information of device 3 in association with group information identifying the group to which each dwelling unit [j, i] in which the device 3 is installed belongs, i.e., apartment building identification information identifying the apartment building B[j], and floor information indicating the floor in the apartment building B[j].

[0016] The abnormality occurrence status storage unit 432 stores abnormality occurrence number information and abnormality occurrence ratio information, which indicate the number of abnormal devices 3 and the ratio of abnormal devices 3 among the multiple devices 3 installed in each of the multiple apartment buildings B[j] managed by the aggregator, in association with the apartment building identification information. In addition, the abnormality occurrence status storage unit 432 stores abnormality occurrence number information and abnormality occurrence ratio information for the multiple devices 3 installed on each floor when each of the multiple apartment buildings B[j] is divided into multiple areas, i.e., multiple floors, in association with a combination of abnormality mode information indicating the content of the abnormality, apartment building identification information, and floor information. In addition, when at least one of the number of abnormal devices 3 or the ratio of abnormal devices 3 meets a preset alert standard for alerting users, the abnormality occurrence status storage unit 432 stores alert target information including the apartment building identification information and floor information of the corresponding apartment building B[j].

[0017] When a user performs a device status acquisition operation on the input unit 405 to request the transmission of monitoring information indicating the status of each of the multiple devices 3 managed by the aggregator, the monitoring information acquisition unit 411 accepts the device status acquisition operation, generates monitoring information request information requesting the cloud server 1 to transmit the monitoring information, and transmits the generated information to the cloud server 1. Here, the monitoring information request information includes, for example, apartment building identification information that identifies an apartment building B[j] in which the multiple devices 3 to be managed are installed. Then, when the monitoring information acquisition unit 411 acquires the monitoring information transmitted from the cloud server 1, it extracts the device status information, device identification information, location identification information, floor information, date and time information, and apartment building identification information of each of the multiple devices 3 managed by the aggregator included in the acquired monitoring information, and stores the extracted information in the device status storage unit 431 in association with each other.

[0018] When the user performs an abnormality occurrence status acquisition operation on the input unit 405 to request transmission of abnormality occurrence status information indicating abnormality occurrence status in multiple devices 3 obtained by aggregating device status information of each of the multiple devices 3 managed by the aggregator, the abnormality occurrence status acquisition unit 412 accepts the abnormality occurrence status acquisition operation, generates abnormality occurrence status notification request information requesting transmission of the abnormality occurrence status information from the cloud server 1, and transmits it to the cloud server 1. Here, the abnormality occurrence status notification request information includes, for example, the above-mentioned apartment complex identification information. Then, when the abnormality occurrence status acquisition unit 412 acquires the abnormality occurrence status notification information transmitted from the cloud server 1, it extracts the abnormality occurrence number information and abnormality occurrence ratio information for each of the multiple apartment complexes B[j] included in the acquired abnormality occurrence status information, and the apartment complex identification information, and stores these pieces of information in the abnormality occurrence status storage unit 432 in association with each other. Furthermore, when the acquired abnormality occurrence status notification information includes the abnormality mode information and floor information described above, the abnormality occurrence status acquisition unit 412 extracts the abnormality occurrence number information and abnormality occurrence ratio information, the abnormality mode information, the floor information, and the apartment house identification information contained in the acquired abnormality occurrence status notification information, and stores these pieces of information in association with each other in the abnormality occurrence status storage unit 432. Furthermore, when the acquired abnormality occurrence status notification information includes the above-mentioned attention-call target information, the abnormality occurrence status acquisition unit 412 extracts the attention-call target information and stores it in the abnormality occurrence status storage unit 432.

[0019] When the user performs a device status acquisition operation on the input unit 405 to request transmission of monitoring information indicating the status of each of the multiple devices 3 managed by the aggregator, the display control unit 413 forms a device status notification image notifying the user of the status of each of the multiple devices 3 using the device status information, device identification information, location identification information, floor information, date and time information, and apartment identification information of each of the multiple devices 3 stored in the device status storage unit 431, and displays the image on the display unit 404. Also, when the user performs an abnormality occurrence status acquisition operation on the input unit 405 to request transmission of abnormality occurrence status information indicating abnormality occurrence status in the multiple devices 3 obtained by aggregating the device status information of each of the multiple devices 3 managed by the aggregator, the display control unit 413 forms an abnormality occurrence status notification image notifying the user of the abnormality occurrence status of the multiple devices 3 using the abnormality occurrence number information, abnormality occurrence ratio information, abnormality mode information, floor information, and apartment identification information stored in the abnormality occurrence status storage unit 432, and displays the image on the display unit 404. Here, when the abnormality occurrence status storage unit 432 stores the above-mentioned attention-attention target information, the display control unit 413 forms an abnormality occurrence status notification image including an icon image for calling the attention of the user based on the apartment building information and floor information included in the attention-attention target information, and displays it on the display unit 404. Furthermore, when the mail acquisition unit 415 acquires mail information, the display control unit 413 forms a mail viewing image based on the acquired mail information, and displays it on the display unit 404.

[0020] When the user performs an operation to display details of an abnormality occurrence status on the input unit 405 to display details of an abnormality occurrence status on the display unit 404 for the apartment house B[j] corresponding to the icon image for calling attention described above, the occurrence status detail notification request unit 414 accepts the operation to display details of an abnormality occurrence status, generates occurrence status detail notification request information requesting the cloud server 1 to transmit monitoring information and email information notifying the abnormality occurrence status, and transmits the request information to the cloud server 1. Here, the occurrence status detail request information includes, for example, apartment house identification information for identifying the target apartment house B[j]. When the user performs an email viewing operation on the input unit 405 to view an email message, the email acquisition unit 415 accepts the email viewing operation and transmits email request information including user identification information for identifying the user to the email server 6, thereby acquiring email information transmitted from the email server 6. Here, the email acquisition unit 415 acquires email information by transmitting email request information conforming to a communication protocol such as POP (Post Office Protocol) 3 or IMAP (Internet Message Access Protocol) 4 to the email server 6.

[0021] Returning to FIG. 2, the cloud server 1 is connected to the device 3 via the local network NW2, the communication control device 2, the BBR 8, and the wide area network NW1, and functions as a device management device that manages the device 3. The cloud server 1 is, for example, a computer for server use, and includes a CPU 101, a main memory unit 102, an auxiliary memory unit 103, a communication unit 106, a clock unit 108, and a bus 109 that connects each unit. The CPU 101 is, for example, a multi-core processor. The main memory unit 102 is a volatile memory, and is used as a working area for the CPU 101. The auxiliary memory unit 103 has a non-volatile memory, functions as a ROM and storage, and stores programs for realizing various functions of the cloud server 1. The communication unit 106 communicates with the device 3 via the wide area network NW1, the BBR 8, the communication control device 2, and the local network NW2. The clock unit 108 has, for example, an RTC (Real Time Clock).

[0022] The CPU 101 reads out the programs stored in the auxiliary storage unit 103 into the main storage unit 102 and executes them, thereby functioning as an equipment status acquisition unit 111, an abnormality determination unit 112, an abnormality occurrence status compilation unit 113, an equipment status notification unit 114, an abnormality occurrence status notification unit 115, a warning determination unit 116, an occurrence status detailed notification request acquisition unit 117, an email generation unit 118, and an email transmission unit 119, as shown in Fig. 3. The auxiliary storage unit 103 shown in Fig. 2 also has an equipment status storage unit 131 and an abnormality occurrence status storage unit 132, as shown in Fig. 3. As shown in Fig. 4(A) and Fig. 4(B), the device status storage unit 131 stores device status information indicating the state of the device 3 installed in each dwelling unit H[j,i] of each of the multiple apartment buildings B[j] managed by the aggregator, in association with the device identification information of the device 3, the location identification information identifying each dwelling unit H[j,i] in which the device 3 is installed, and the date and time information indicating the date and time when the cloud server 1 acquired the device status information. The device status storage unit 131 also stores the device status information of the device 3 in association with group identification information identifying the group to which each dwelling unit [j,i] in which the device 3 is installed belongs, that is, the apartment identification information identifying the apartment B[j], and floor information indicating the floor in the apartment B[j]. The example shown in Fig. 4(A) indicates that an abnormality corresponding to "alert 1" has occurred in the device 3 identified by the device identification information IDE[2] installed in the dwelling unit H[0,2] identified by the location identification information IDR[2]. 4B shows an example in which communication with device 3, identified by device identification information IDE[1] and installed in dwelling unit H[0,1] identified by location identification information IDR[1], has been interrupted. Comparing FIGS. 4A and 4B, the device status information of device 3 corresponding to location identification information IDR[1] has not been updated for 30 min or more, so it is determined that a communication anomaly (communication interruption) has occurred, and the device status information is set to "communication interruption."

[0023] Returning to Fig. 3, the abnormality occurrence status storage unit 132 stores the abnormality occurrence number information and abnormality occurrence ratio information for the multiple devices 3 installed in each of the multiple apartment buildings B[j] in association with the apartment building identification information. The abnormality occurrence status storage unit 132 also stores the abnormality occurrence number information and abnormality occurrence ratio information for the multiple devices 3 installed on each floor of each of the multiple apartment buildings B[j] in association with a combination of abnormality mode information indicating the content of the abnormality, apartment building identification information, and floor information. Furthermore, when at least one of the number of devices 3 in which an abnormality has occurred or the ratio of devices 3 in which an abnormality has occurred meets a preset warning criterion for warning the user, the abnormality occurrence status storage unit 132 stores warning target information including the apartment building identification information and floor information of the corresponding apartment building B[j].

[0024] The device status acquisition unit 111 acquires the above-mentioned device status information. Specifically, when the device status acquisition unit 111 acquires the above-mentioned device status notification information transmitted from the device 3, the device status acquisition unit 111 extracts the device status information, device identification information, apartment building identification information, location identification information, and floor information included in the acquired device status notification information. Then, the device status acquisition unit 111 stores the extracted information in the device status storage unit 131 in association with date and time information indicating the date and time when the device status notification information, which is timed by the clock unit 108, was acquired.

[0025] Each time a preset device state determination time for determining the device state arrives, the abnormality determination unit 112 determines whether or not the time elapsed since the device state information was last acquired for each of the multiple devices 3 exceeds a preset reference time based on the date and time information stored in the device state storage unit 131. Here, the length of the reference time is set to, for example, about 30 minutes. Note that this reference time is set to an arbitrary length, and may be set to, for example, 90 minutes or more in consideration of a case where the update of the device state information stored in the device state storage unit 131 is temporarily delayed. Then, when the time elapsed since the device state information was last acquired exceeds the above-mentioned reference time, the abnormality determination unit 112 determines that a communication abnormality has occurred with the corresponding device 3, generates device state information indicating a communication interruption, and updates the device state information of the corresponding device 3 stored in the device state storage unit 131 using the generated device state information.

[0026] When the device status notification unit 114 acquires monitoring information request information transmitted from the terminal device 4, it generates monitoring information including the device status information, device identification information, location identification information, floor information, date and time information and apartment building identification information of each of the multiple devices 3 stored in the device status storage unit 131, and transmits the generated monitoring information to the terminal device 4. Here, when a communication abnormality occurs with a device 3, the device status notification unit 114 generates monitoring information including the device status information of each of the multiple devices 3 including device status information indicating the communication abnormality with the device 3, and transmits it to the terminal device 4.

[0027] The abnormality occurrence status counting unit 113 counts the number of abnormal devices among the multiple devices 3 and the ratio of abnormal devices among the multiple devices 3 for each apartment B[j] based on the device status information of each of the multiple devices 3 stored in the device status storage unit 131. Here, the abnormality occurrence status counting unit 113 stores abnormality occurrence number information indicating the number of abnormal devices 3 and abnormality occurrence ratio information indicating the ratio of abnormal devices 3, which are obtained by counting for each apartment B[j], in the abnormality occurrence status storage unit 132 in association with the apartment identification information. In addition, when the abnormality occurrence status counting unit 113 is notified of the apartment identification information and floor information from the occurrence status detail notification request acquisition unit 117, the abnormality occurrence status counting unit 113 stores abnormality occurrence number information indicating the number of abnormal devices 3 and abnormality occurrence ratio information indicating the ratio of abnormal devices 3, which are obtained by counting for each floor and content of abnormality of each apartment B[j], in the abnormality occurrence status storage unit 132 in association with a combination of abnormality mode information indicating the content of the abnormality, the apartment identification information, and floor information.

[0028] The attention call determination unit 116 determines whether or not at least one of the number of abnormality occurrences and the abnormality occurrence rate meets the above-mentioned attention call criterion by referring to the abnormality occurrence number information and the abnormality occurrence rate information stored in the abnormality occurrence status storage unit 132. Then, when the attention call determination unit 116 determines that at least one of the number of devices 3 in which an abnormality has occurred or the rate of devices 3 in which an abnormality has occurred meets the preset attention call criterion for calling the attention of the user, the attention call determination unit 116 generates attention call target information including the apartment identification information and floor information of the corresponding apartment B[j] and stores it in the abnormality occurrence status storage unit 132.

[0029] When the abnormality occurrence status notification unit 115 acquires abnormality occurrence status notification request information transmitted from the terminal device 4, it generates abnormality occurrence status information including the abnormality occurrence number information and abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132, and transmits the generated abnormality occurrence status information to the terminal device 4. Here, the abnormality occurrence status information also includes the abnormality mode information, apartment house identification information, or floor information described above. Furthermore, when the abnormality occurrence status storage unit 132 stores attention-attention-attention-attention-attention information including the apartment house identification information and floor information, the abnormality occurrence status notification unit 115 generates abnormality occurrence status information including the attention-attention-attention-attention-attention information and transmits it to the terminal device 4.

[0030] When occurrence status detail notification request acquisition unit 117 acquires occurrence status detail notification request information transmitted from terminal device 4, it notifies the abnormality occurrence status compilation unit 113 and email generation unit 118 of the apartment house identification information and floor information contained in the acquired occurrence status detail notification request information. When notified of the apartment house identification information and floor information from occurrence status detail notification request acquisition unit 117, email generation unit 118 generates email information based on the abnormality occurrence number information and abnormality occurrence ratio information stored in abnormality occurrence status storage unit 132, the abnormality mode information, the apartment house identification information, and the floor information. Email transmission unit 119 transmits the generated email information to email server 6.

[0031] Next, the operation of the device management system according to the present embodiment will be described with reference to Fig. 5 to Fig. 10. First, as shown in Fig. 5, when a preset device status notification time arrives, the device 3 generates device status notification information including device status information indicating its own status (step S1), and the generated device status notification information is transmitted from the device 3 to the cloud server 1 (step S2). Meanwhile, when the cloud server 1 acquires the device status notification information, it extracts the device status information, device identification information, apartment building identification information, location identification information, and floor information included in the acquired device status notification information. Then, the cloud server 1 stores the extracted information in the device status storage unit 131 in association with date and time information indicating the date and time when the device status notification information, which is timed by the clock unit 108, was acquired (step S3).

[0032] Next, when a preset device status determination time arrives, the cloud server 1 determines whether or not the time elapsed since the device status information was last acquired for each of the multiple devices 3 exceeds a preset reference time based on the date and time information stored in the device status storage unit 131. Here, it is assumed that the cloud server 1 determines that there is a device 3 whose time elapsed since the device status information was last acquired exceeds the above-mentioned reference time, that is, that a communication abnormality has occurred with the device 3 (step S4). In this case, the cloud server 1 generates device status information indicating a communication interruption, and updates the device status information of the corresponding device 3 stored in the device status storage unit 131 using the generated device status information (step S5).

[0033] Next, the cloud server 1 counts, for each apartment building B[j], the number of devices in which an abnormality has occurred among the multiple devices 3 and the proportion of devices in which an abnormality has occurred, based on the device status information of each of the multiple devices 3 stored in the device status storage unit 131. Then, the cloud server 1 stores, in the abnormality occurrence status storage unit 132, the abnormality occurrence number information indicating the number of devices 3 in which an abnormality has occurred and the abnormality occurrence proportion information indicating the proportion of devices 3 in which an abnormality has occurred, obtained by counting for each apartment building B[j], in association with the apartment building identification information (step S6).

[0034] Thereafter, the cloud server 1 refers to the abnormality occurrence number information and the abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132 and determines that at least one of the abnormality occurrence number and the abnormality occurrence ratio satisfies the above-mentioned warning criterion (step S7). In this case, the cloud server 1 generates warning target information including the apartment identification information and floor information of the corresponding apartment B[j] and stores it in the abnormality occurrence status storage unit 132 (step S8).

[0035] Next, it is assumed that the user performs the above-mentioned device status acquisition operation on the input unit 405 of the terminal device 4. In this case, the terminal device 4 accepts the device status acquisition operation and generates the above-mentioned monitoring status request information (step S9), and the generated monitoring status request information is transmitted from the terminal device 4 to the cloud server 1 (step S10). On the other hand, when the cloud server 1 acquires the above-mentioned monitoring information request information, it generates monitoring information including the device status information, device identification information, location identification information, floor information, date and time information, and apartment identification information of each of the multiple devices 3 stored in the device status storage unit 131 (step S11). Then, the generated monitoring information is transmitted from the cloud server 1 to the terminal device 4 (step S12). On the other hand, when the terminal device 4 acquires the monitoring information, it extracts the device status information, device identification information, location identification information, floor information, date and time information, and apartment identification information of each of the multiple devices 3 managed by the aggregator included in the acquired monitoring information, and stores the extracted information in the device status storage unit 431 in association with each other (step S13). Next, the terminal device 4 uses the device status information, device identification information, location identification information, floor information, date and time information and apartment building identification information of each of the multiple devices 3 stored in the device status memory unit 431 to form a device status notification image that notifies the user of the status of each of the multiple devices 3, and displays it on the display unit 404 (step S14).

[0036] Here, the terminal device 4 forms a device status notification image GA1 as shown in Fig. 6, for example, and displays it on the display unit 404. Here, the device status notification image GA1 includes a message image M11 that displays a MAC address, which is the device status identification information, a message image M12 that displays the room number of the dwelling unit H[j,i] identified by the location identification information, a message image M13 that displays the status of the device 3, and a message image M14 that displays the date and time when the device status notification information was acquired. Alternatively, the terminal device 4 forms a device status notification image GA2 as shown in Fig. 7, for example, and displays it on the display unit 404. Here, the device status notification image GA2 includes icon images GA21, GA22, GA23, and GA24 that represent the respective floors in the apartment building B[j], and icon images GA211, GA221, GA231, and GA241 that represent the respective dwelling units H[j,i] that exist on the respective floors arranged inside the icon images GA21, GA22, GA23, and GA24. An icon image GA2C indicating the status of the device 3 is disposed inside each of the icon images GA211, GA221, GA231, and GA241. The display manner of the device status notification image GA1 is not limited to the example of Fig. 6. For example, the row corresponding to the dwelling unit H[j,i] in which an abnormality has occurred in the device 3 may be colored according to the type of abnormality that has occurred, the color of the text may be changed, the size of the text may be increased, or the text may be made thicker. This makes it easier to visually recognize the dwelling unit H[j,i] in which an abnormality has occurred in the device 3.

[0037] Returning to FIG. 5, when the user performs the abnormality occurrence status acquisition operation on the input unit 405 of the terminal device 4, the terminal device 4 accepts the abnormality occurrence status acquisition operation and generates the abnormality occurrence status notification request information (step S15). Then, the generated abnormality occurrence status notification request information is transmitted from the terminal device 4 to the cloud server 1 (step S16). Meanwhile, when the cloud server 1 acquires the abnormality occurrence status notification request information, it generates abnormality occurrence status information including the abnormality occurrence number information and abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132 (step S17). Thereafter, as shown in FIG. 8, the generated abnormality occurrence status information is transmitted from the cloud server 1 to the terminal device 4 (step S18). Meanwhile, when the terminal device 4 acquires the abnormality occurrence status notification information, it extracts the abnormality occurrence number information and abnormality occurrence ratio information and the apartment identification information for each of the multiple apartment buildings B[j] included in the acquired abnormality occurrence status information, and stores these pieces of information in the abnormality occurrence status storage unit 432 in association with each other (step S19). Next, the terminal device 4 uses the abnormality occurrence number information, abnormality occurrence rate information, abnormality mode information, floor information and apartment building identification information stored in the abnormality occurrence status memory unit 432 to form an abnormality occurrence status notification image to notify the user of the abnormality occurrence status of multiple devices 3, and displays it on the display unit 404 (step S20).

[0038] Here, the terminal device 4 forms an abnormality occurrence status notification image GA31 as shown in FIG. 9(A), for example, and displays it on the display unit 404. Here, the abnormality occurrence status notification image GA31 includes an icon image GA311 representing each of the multiple apartment buildings B[j]. Inside each icon image GA311, a message image M311 representing the number of devices 3 in which an abnormality has occurred and a bar image GA3B whose length changes according to the ratio of devices 3 in which an abnormality has occurred are arranged. In addition, when the abnormality occurrence status storage unit 432 stores the above-mentioned attention-attention target information, the terminal device 4 forms an abnormality occurrence status notification image GA32 as shown in FIG. 9(B), for example, and displays it on the display unit 404. Here, inside the icon image GA311 corresponding to the apartment building B[j] corresponding to the attention-attention target information in the abnormality occurrence status notification image GA32, a mark image GA3M for calling the attention of the user is arranged.

[0039] Returning to FIG. 8, it is assumed that the user performs an abnormality occurrence status detail display operation on the input unit 405 of the terminal device 4 to display details of the abnormality occurrence status on the display unit 404 for, for example, the apartment building B[j] corresponding to the icon image for calling attention described above. In this case, the terminal device 4 generates the above-mentioned occurrence status detail notification request information (step S21), and the generated occurrence status detail notification request information is transmitted from the terminal device 4 to the cloud server 1 (step S22). On the other hand, upon acquiring the occurrence status detail notification request information, the cloud server 1 generates abnormality occurrence status information including the abnormality occurrence number information and abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132 (step S23). Then, the generated abnormality occurrence status information is transmitted from the cloud server 1 to the terminal device 4 (step S24). On the other hand, when the abnormality occurrence status notification information is acquired, the abnormality occurrence number information and abnormality occurrence ratio information, the apartment identification information, and the floor information for each of the multiple apartment buildings B[j] included in the acquired abnormality occurrence status information are extracted, and these pieces of information are stored in the abnormality occurrence status storage unit 432 in association with each other (step S25). After that, the terminal device 4 uses the abnormality occurrence number information, abnormality occurrence ratio information, abnormality mode information, floor information, and apartment identification information stored in the abnormality occurrence status storage unit 432 to form an abnormality occurrence status detail notification image that notifies the user of the abnormality occurrence status of the multiple devices 3, and displays it on the display unit 404 (step S26). Here, the terminal device 4 forms an abnormality occurrence status detail notification image GA4 as shown in FIG. 10(A), for example, and displays it on the display unit 404. Here, the abnormality occurrence status detail notification image GA4 includes message images M41 and M42 that indicate the abnormality occurrence status in the target apartment building B[j].

[0040] Next, the cloud server 1 generates mail information including message information and user identification information for identifying the user of the terminal device 4 based on the abnormality occurrence number information and abnormality occurrence ratio information, abnormality mode information, apartment identification information, and floor information stored in the abnormality occurrence status storage unit 132 (step S27). Then, the generated mail information is transmitted from the cloud server 1 to the mail server 6 (step S28). Meanwhile, when the mail server 6 acquires the mail information, it extracts the message information and the user identification information included in the acquired mail information, and stores the extracted information in the mail storage unit in association with each other (step S29). Then, it is assumed that the user performs a mail viewing operation on the input unit 405 of the terminal device 4 to view the message of the mail. In this case, the terminal device 4 accepts the mail viewing operation, and the above-mentioned mail request information is transmitted from the terminal device 4 to the mail server 6 (step S30). Meanwhile, when the mail server 6 acquires the mail request information, it identifies the message information corresponding to the user identification information included in the acquired mail request information, and generates mail information including the identified message information (step S31). The generated mail information is then transmitted from the mail server 6 to the terminal device 4 (step S32). On the other hand, when the terminal device 4 acquires the mail information, it forms a mail viewing image based on the acquired mail information and displays it on the display unit 404 (step S33). Here, the terminal device 4 forms a mail viewing image GA5 as shown in Fig. 10(B), for example, and displays it on the display unit 404. Here, the mail viewing image GA5 includes message images M51 and M52 that indicate the occurrence of an abnormality in the target apartment building B[j].

[0041] Next, the device management process executed by the cloud server 1 according to the present embodiment will be described with reference to FIG. 11. This device management process is started when a program for executing the device management process is started in the cloud server 1. First, the device status acquisition unit 111 judges whether or not the above-mentioned device status notification information has been acquired (step S101). If the device status acquisition unit 111 judges that the device status notification information has not been acquired (step S101: No), the process of step S103 described later is executed. On the other hand, if the device status acquisition unit 111 judges that the device status notification information has been acquired (step S101: Yes), it extracts the device status information, device identification information, apartment building identification information, location identification information, and floor information included in the acquired device status notification information. Then, the device status acquisition unit 111 stores the extracted information in the device status storage unit 131 in association with date and time information indicating the date and time when the device status notification information measured by the clock unit 108 was acquired (step S102).

[0042] Next, the abnormality determination unit 112 determines whether the above-mentioned device state determination time has arrived (step S103). If the abnormality determination unit 112 determines that the device state determination time has not yet arrived (step S103: No), the process of step S109 described later is executed. On the other hand, if the abnormality determination unit 112 determines that the device state determination time has arrived (step S103: Yes), it determines whether a communication abnormality has occurred (step S104). Here, the abnormality determination unit 112 determines whether the elapsed time from the time when the device state information was last acquired for each of the multiple devices 3 exceeds a preset reference time based on the date and time information stored in the device state storage unit 131. If the abnormality determination unit 112 determines that a device communication abnormality has not occurred (step S104: No), the process of step S109 described later is executed. On the other hand, if the abnormality determination unit 112 determines that a device communication abnormality has occurred (step S104: Yes), it generates device status information indicating a communication interruption, and uses the generated device status information to update the device status information of the corresponding device 3 stored in the device status memory unit 131 (step S105).

[0043] Thereafter, the abnormality occurrence status counting unit 113 counts the number of abnormal devices among the multiple devices 3 and the ratio of abnormal devices among the multiple devices 3 for each apartment house B[j] based on the device status information of each of the multiple devices 3 stored in the device status storage unit 131. Then, the abnormality occurrence status counting unit 113 stores the abnormality occurrence number information indicating the number of abnormal devices 3 and the abnormality occurrence ratio information indicating the ratio of abnormal devices 3, which are obtained by counting for each apartment house B[j], in the abnormality occurrence status storage unit 132 in association with the apartment house identification information (step S106). Next, the attention calling determination unit 116 refers to the abnormality occurrence number information and the abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132 to determine whether or not at least one of the number of abnormality occurrences and the abnormality occurrence ratio meets the above-mentioned attention calling criteria (step S107). Here, if the attention determination unit 116 determines that at least one of the number of times the abnormality occurs and the rate of occurrence of the abnormality does not satisfy the attention criterion (step S107: No), the processing of step S109 described below is executed. On the other hand, if the attention determination unit 116 determines that at least one of the number of times the abnormality occurs and the rate of occurrence of the abnormality satisfies the above-mentioned attention criterion (step S107: Yes), it generates attention target information including the apartment identification information and floor information of the corresponding apartment B[j], and stores it in the abnormality occurrence status storage unit 132 (step S108).

[0044] Next, the device status notifying unit 114 determines whether or not it has acquired monitoring information request information transmitted from the terminal device 4 (step S109). If the device status notifying unit 114 determines that it has not acquired the monitoring information request information (step S109: No), the process of step S111 described below is executed. On the other hand, if the device status notifying unit 114 determines that it has acquired the monitoring information request information (step S109: Yes), it generates monitoring information including the device status information, device identification information, location identification information, floor information, date and time information, and apartment identification information of each of the multiple devices 3 stored in the device status storage unit 131, and transmits the generated monitoring information to the terminal device 4 (step S110).

[0045] Thereafter, the abnormality occurrence status notifying unit 115 judges whether or not it has acquired the abnormality occurrence status notification request information transmitted from the terminal device 4 (step S111). If the abnormality occurrence status notifying unit 115 judges that it has not acquired the abnormality occurrence status notification request information (step S111: No), the process of step S113 described below is executed. On the other hand, if the abnormality occurrence status notifying unit 115 judges that it has acquired the abnormality occurrence status notification request information (step S111: Yes), it generates abnormality occurrence status information including the abnormality occurrence number information and the abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132, and transmits the generated abnormality occurrence status information to the terminal device 4 (step S112).

[0046] Next, the occurrence status detail notification request acquisition unit 117 determines whether or not it has acquired occurrence status detail notification request information transmitted from the terminal device 4 (step S113). If the occurrence status detail notification request acquisition unit 117 determines that it has not acquired occurrence status detail notification request information (step S113: No), the process of step S101 is executed again. On the other hand, if the occurrence status detail notification request acquisition unit 117 determines that it has acquired occurrence status detail notification request information (step S113: Yes), it notifies the abnormality occurrence status compilation unit 113 and the mail generation unit 118 of the apartment house identification information and floor information included in the acquired occurrence status detail notification request information. Then, when the abnormality occurrence status tallying unit 113 is notified of the apartment house identification information and floor information from the occurrence status detail notification request acquisition unit 117, the abnormality occurrence status tallying unit 113 stores the abnormality occurrence number information indicating the number of devices 3 in which an abnormality has occurred and the abnormality occurrence rate information indicating the rate of devices 3 in which an abnormality has occurred, which are obtained by tallying for each floor of the apartment house B[j] and for each type of abnormality, in the abnormality occurrence status storage unit 132 in association with a combination of the abnormality mode information indicating the type of abnormality, the apartment house identification information, and the floor information (step S114). Next, the abnormality occurrence status notification unit 115 generates abnormality occurrence status information including the abnormality occurrence number information and the abnormality occurrence rate information stored in the abnormality occurrence status storage unit 132, and transmits the generated abnormality occurrence status information to the terminal device 4 (step S115). After that, the mail generation unit 118 generates mail information based on the abnormality occurrence number information and the abnormality occurrence rate information stored in the abnormality occurrence status storage unit 132, the abnormality mode information, the apartment house identification information, and the floor information. Then, the mail sending unit 119 sends the generated mail information to the mail server 6 (step S116). Next, the process of step S101 is executed again.

[0047] As described above, according to the device management system of the present embodiment, when the time elapsed since the last acquisition of device status information for each of the multiple devices 3 exceeds a preset reference time, the abnormality determination unit 112 determines that a communication abnormality has occurred between the corresponding device. Then, when a communication abnormality occurs, the device status notification unit 114 transmits device status information for each of the multiple devices, including device status information indicating the communication abnormality, to the terminal device 4 owned by the user. As a result, when a communication abnormality occurs between the device 3 and the cloud server 1, the occurrence of the communication abnormality is promptly transmitted to the terminal device 4, so that the user can promptly grasp the occurrence of the communication abnormality.

[0048] Incidentally, in the case of an apartment house B[j] that adopts a system of receiving high-voltage electricity from a power company in a lump sum, the electricity bill is determined, for example, by the peak value of the power consumption in a year. In an apartment house B[j] that adopts such a so-called high-voltage lump sum power receiving system, for example, if the power consumption is concentrated at night and the peak value of the power consumption at night becomes large, the electricity bill may become higher accordingly. For this reason, in such an apartment house B[j], it is required to level out the power consumption of the entire apartment house B[j] throughout the day. In order to level out the power consumption of the entire apartment house B[j], multiple devices 3 installed in the apartment house B[j] may be centrally managed by a cloud server 1. In this case, if communication between the devices 3 and the cloud server 1 is interrupted due to various reasons, the administrator who manages the apartment house B[j] may not be able to adequately monitor the devices 3, and the administrator may miss a large fluctuation in the power consumption of the entire apartment house B[j]. In contrast, according to the device management system of this embodiment, if a communication abnormality occurs between the device 3 and the cloud server 1, a notification of the communication abnormality is quickly sent to the terminal device 4, allowing the user to quickly grasp the occurrence of the communication abnormality and quickly restore the communication state between the device 3 and the cloud server 1.

[0049] Furthermore, in the cloud server 1 according to the present embodiment, the device status acquisition unit 111 acquires device status information and location identification information for each of the multiple devices 3, and stores the acquired device status information, device identification information, and location identification information in the device status storage unit 131 in association with each other. Then, in the terminal device 4, the display control unit 413 forms a device status notification image having a display mode that associates the status of each of the multiple devices 3 with the dwelling unit H[j,i] identified by the location identification information based on the device status information and location identification information for each of the multiple devices 3 transmitted to the terminal device 4, and displays the image on the display unit 404. This makes it easier for the manager to identify the dwelling unit H[j,i] in which the device 3 with the abnormality is installed in the apartment building B[j] when an abnormality occurs in the device 3, and therefore makes it easier to quickly restore the device 3 with the abnormality.

[0050] Furthermore, the abnormality occurrence status counting unit 113 according to the present embodiment counts the number of devices 3 in which an abnormality has occurred and the ratio of devices 3 in which an abnormality has occurred among the multiple devices 3 based on the device status information of each of the multiple devices 3. Then, when the abnormality occurrence status notifying unit 115 acquires abnormality occurrence status notification request information transmitted from the terminal device 4, it generates abnormality occurrence status information indicating the number of devices 3 in which an abnormality has occurred and the ratio of devices 3 in which an abnormality has occurred among the multiple devices 3, and transmits the information to the terminal device 4. This makes it possible to notify the administrator who owns the terminal device 4 of the number of devices 3 in which an abnormality has occurred and the ratio of devices 3 in which an abnormality has occurred among the multiple devices 3, which is advantageous in that the administrator can easily grasp the abnormality occurrence status in the entire multiple devices 3.

[0051] Moreover, the device status storage unit 131 according to the present embodiment stores device status information of each of the multiple devices 3 in association with location identification information, floor information, and apartment identification information. The device status notification unit 114 transmits the floor information and apartment identification information, together with the device status information and location identification information of each of the multiple devices 3 stored in the device status storage unit 131, to the terminal device 4. Meanwhile, in the terminal device 4, the display control unit 413 forms a device status notification image having a display mode corresponding to the dwelling unit H[j,i] identified by the location identification information, the apartment B[j] to which the dwelling unit H[j,i] belongs, and the floor, based on the device status information, location identification information, apartment identification information, and floor information of each of the multiple devices 3 transmitted to the terminal device 4, and displays the image on the display unit 404. This allows the manager who owns the terminal device 4 to grasp the occurrence status of an abnormality in the device 3 for each apartment B[j] or for each floor of the apartment B[j], which is advantageous in that it becomes easier to guess the cause of the abnormality.

[0052] (Embodiment 2) The device management system according to this embodiment differs from the first embodiment in that it includes a second terminal device capable of communicating with each of the multiple devices 3 via the local network NW2. Here, the second terminal device has a communication status confirmation unit that transmits response request information requesting the multiple devices 3 and the cloud server to transmit response information, and confirms the communication status based on the acquisition status of the response information transmitted from each of the multiple devices 3 and the cloud server after the transmission of the response request information.

[0053] As shown in Fig. 12, the device management system according to this embodiment includes a terminal device 4 managed by an aggregator, a terminal device 2005 owned by a user residing in each dwelling unit H[j,i], and a cloud server 2001. In Fig. 12, the same components as those in the first embodiment are denoted by the same reference numerals as in Fig. 1. The terminal device 2005 can communicate with the device 3 via the local network NW2, and can communicate with the cloud server 1 via the wide area network NW1.

[0054] The terminal device 2005 is, for example, a smartphone, and includes a CPU 501, a main memory unit 502, an auxiliary memory unit 503, a display unit 504, an input unit 505, a local communication unit 561, and a wide area communication unit 562, as shown in FIG. 13, and is used by users residing in each dwelling unit H[j,i]. In FIG. 13, the same components as those in the first embodiment are given the same reference numerals as those in FIG. 2. Here, the main memory unit 502 has a volatile memory used as a working area for the CPU 501, and the auxiliary memory unit 403 has a non-volatile memory such as a ROM (Read Only Memory) or a semiconductor flash memory, and stores programs for realizing various functions of the terminal device 2005. The display unit 504 is a liquid crystal display, an organic EL (Electro-luminescence) display, or the like, and displays various information. The input unit 505 is, for example, a transparent touch pad arranged over the display unit 504, and receives a user's operation and outputs information indicating the received operation content to the CPU 501. The local communication unit 561 has an interface for connecting to the local network NW2, and the wide area communication unit 562 has an interface for connecting to the wide area network NW1.

[0055] The CPU 501 reads out a program stored in the auxiliary storage unit 503 into the main storage unit 502 and executes it, thereby functioning as a communication abnormality occurrence notification acquisition unit 511, a display control unit 512, a communication status confirmation unit 513, and a communication status notification unit 514, as shown in FIG. 14. In FIG. 14, the same components as those in the first embodiment are denoted by the same reference numerals as those in FIG. 3. In addition, the auxiliary storage unit 503 shown in FIG. 13 has a communication status storage unit 531, as shown in FIG. 14. The communication status storage unit 531 stores communication status information indicating the status of communication with the device 3 via the local network NW2 in association with the device identification information of the device 3. In addition, the communication status storage unit 531 also stores communication status information indicating the status of communication with the cloud server 2001 via the wide area network NW1.

[0056] When the communication abnormality occurrence notification acquisition unit 511 acquires the communication abnormality occurrence notification information transmitted from the cloud server 2001, it notifies the acquired communication abnormality occurrence notification information to the display control unit 512 and the communication status confirmation unit 513. When the communication abnormality occurrence notification information is notified from the communication abnormality occurrence notification acquisition unit 511, the display control unit 512 forms a communication abnormality occurrence notification image for notifying the user residing in the dwelling unit H[j,i] that a communication abnormality has occurred, and displays the image on the display unit 504. In addition, when any of the communication status information stored in the communication status storage unit 531 indicates a communication abnormality, the display control unit 512 forms a status confirmation prompt image for prompting the user to check the status of the device 3 or the communication control device 2, and displays the image on the display unit 504.

[0057] The communication status checking unit 513 checks the communication status with the device 3 via the local network NW2 based on the acquisition status of response information transmitted from the device 3 after transmitting, to the device 3, response information requesting the device 3 to transmit response information. Specifically, if the communication status checking unit 513 cannot acquire response information from the device 3 within a preset waiting time after transmitting response request information to the device 3, the communication status checking unit 513 determines that an abnormality has occurred in the communication with the device 3. In addition, the communication status checking unit 513 checks the communication status with the cloud server 2001 via the local network NW2, the communication control device 2, the BBR8, and the wide area network NW1 based on the acquisition status of response information transmitted from the cloud server 2001 after transmitting, to the cloud server 2001, response information requesting the cloud server 2001 to transmit response information via the local network NW2, the communication control device 2, the BBR8, and the wide area network NW1. Specifically, if the communication status checking unit 513 cannot obtain response information from the cloud server 2001 before a preset waiting time has elapsed after transmitting response request information to the cloud server 2001, the communication status checking unit 513 determines that an abnormality has occurred in the communication with the cloud server 2001. Based on the determination result of the status of the communication between the device 3 and the cloud server 2001, the communication status checking unit 513 generates communication status information and stores it in the communication status storage unit 531. The communication status notification unit 514 generates communication status notification information including the communication status information stored in the communication status storage unit 531 and device identification information, and transmits it to the cloud server 2001.

[0058] Returning to Fig. 13, the cloud server 2001 has the same hardware configuration as the cloud server 1. The CPU 101 of the cloud server 2001 reads out a program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby functioning as a device status acquisition unit 111, an abnormality determination unit 2112, an abnormality occurrence status aggregation unit 113, a device status notification unit 114, an abnormality occurrence status notification unit 115, a warning determination unit 116, an occurrence status detailed notification request acquisition unit 117, an email generation unit 118, an email transmission unit 119, a response unit 2120, and a communication status acquisition unit 2121, as shown in Fig. 14. The auxiliary storage unit 103 shown in Fig. 13 also has a device status storage unit 2131, an abnormality occurrence status storage unit 132, and a terminal device information storage unit 2133, as shown in Fig. 14. 15, the device status storage unit 2131 stores device status information indicating the state of the device 3 installed in each dwelling unit H[j,i] and communication anomaly location information indicating the location of the communication anomaly when a communication anomaly occurs, in association with the device identification information of the device 3, location identification information identifying each dwelling unit H[j,i] in which the device 3 is installed, and date and time information indicating the date and time when the cloud server 1 acquired the device status information. In addition, the device status storage unit 2131 stores the device status information and communication anomaly location information of the device 3 in association with the apartment identification information and floor information. The example shown in FIG. 15 indicates that communication with the device 3 identified by device identification information IDE[1] installed in the dwelling unit H[0,1] identified by location identification information IDR[1] has been interrupted due to a communication anomaly occurring in the local network NW2.

[0059] 14, the terminal device information storage unit 2133 stores terminal device identification information for identifying the terminal device 2005 in association with location identification information for identifying the dwelling unit H[j,i] in which the user of the terminal device 2005 resides. As the terminal device identification information, for example, IP address information indicating the IP address assigned to the terminal device 2005 can be adopted.

[0060] The abnormality determination unit 2112 determines whether or not the time elapsed since the time when the device status information was last acquired has exceeded a preset reference time for each of the multiple devices 3 based on the date and time information stored in the device status storage unit 131 each time a preset device status determination time for determining the device status arrives. If the time elapsed since the time when the device status information was last acquired exceeds the above-mentioned reference time, the abnormality determination unit 2112 determines that a communication abnormality has occurred with the corresponding device 3, and notifies the communication status acquisition unit 2121 of location identification information for identifying the dwelling unit H[j,i] in which the device 3 in which the communication abnormality has occurred is installed. When the abnormality determination unit 2112 is notified of the communication notification information from the communication status acquisition unit 2121, the abnormality determination unit 2112 specifies the location of the abnormality based on the notified communication status information. The abnormality determination unit 2112 updates the abnormality location information stored in the device status storage unit 2131 using the abnormality location information indicating the specified location of the abnormality.

[0061] When the communication status acquisition unit 2121 is notified of the location identification information, it generates communication abnormality occurrence notification information and transmits it to the terminal device 2005 identified by the terminal device identification information corresponding to the notified location identification information stored in the terminal device information storage unit 2133. Then, the communication status acquisition unit 2121 acquires the communication status notification information transmitted from the terminal device 2005 after transmitting the communication abnormality occurrence notification information, extracts the communication status information included in the acquired communication status notification information, and notifies the abnormality determination unit 2112 of the communication abnormality occurrence notification information.

[0062] Upon receiving the response request information transmitted from the terminal device 2005, the response unit 2120 transmits the response information in response to the response request information to the terminal device 2005 that is the source of the response request information.

[0063] Next, the operation of the device management system according to the present embodiment will be described with reference to Figs. 16 to 18. In Figs. 16 and 18, the same processes as those in the first embodiment are denoted by the same reference numerals as those in Figs. 5 and 8. First, as shown in Fig. 16, it is assumed that after the processes from steps S1 to S3 are executed, the time for determining the device status arrives and the cloud server 2001 determines that a communication abnormality has occurred with the device 3 (step S4). In this case, the cloud server 2001 generates device status information indicating a communication interruption and updates the device status information of the corresponding device 3 stored in the device status storage unit 131 using the generated device status information (step S5). Next, the cloud server 2001 generates communication abnormality occurrence notification information notifying that a communication abnormality has occurred in the corresponding device 3 (step S2001), and the generated communication abnormality occurrence notification information is transmitted from the cloud server 2001 to the terminal device 2005 (step S2002). On the other hand, when the terminal device 2005 acquires the communication abnormality occurrence notification information, it forms the above-mentioned communication abnormality occurrence notification image and displays it on the display unit 504 (step S2003). Here, the terminal device 2005 displays, for example, a communication abnormality occurrence notification image GA2001 as shown in Fig. 17(A) on the display unit 504. The communication abnormality occurrence notification image GA2001 includes a message image M2001 including a message notifying the user that a communication abnormality has occurred and a message inquiring the user as to whether or not to execute processing for investigating the cause of the communication abnormality, a button image BU2011 that is selected when execution of the processing for investigating the cause is permitted, and a button image BU2012 that is selected when execution is not permitted.

[0064] Here, it is assumed that the user performs an authorization operation to authorize a process for investigating the cause of the communication abnormality while a communication abnormality occurrence notification image is displayed on the display unit 504 of the terminal device 2005. This authorization operation is, for example, an operation in which the user touches a portion of the input unit 505, which is a touch pad, corresponding to the button image BU2011 while the terminal device 2005 is displaying a communication abnormality occurrence notification image GA2001 as shown in Fig. 17(A) on the display unit 504. In this case, as shown in Fig. 16, the terminal device 2005 generates response request information addressed to the device 3 (step S2004), and the generated response request information is transmitted from the terminal device 2005 to the device 3 via the local network NW2 (step S2005). Next, it is assumed that the terminal device 2005 determines that the above-mentioned waiting time has elapsed without acquiring response information from the device 3 (step S2006). In this case, the terminal device 2005 generates communication status information indicating that an abnormality has occurred in communication with the device 3, and stores the communication status information in the communication status storage unit 531 (step S2007). After that, the terminal device 2005 generates response request information addressed to the cloud server 2001 (step S2008), and the generated response request information is transmitted from the terminal device 2005 to the cloud server 2001 via the local network NW2, the communication control device 2, the BBR8, and the wide area network NW1, as shown in Fig. 18 (step S2009). On the other hand, when the cloud server 2001 acquires the response request information, in response thereto, the cloud server 2001 transmits response information to the terminal device 2005 via the wide area network NW1, the BBR8, the communication control device 2, and the local network NW2 (step S2010). On the other hand, when terminal device 2005 receives the response information transmitted from cloud server 2001, it generates communication status information indicating that communication with cloud server 2001 is normal, and stores the information in communication status storage unit 531 (step S2011).

[0065] Next, when any of the communication status information stored in the communication status storage unit 531 indicates that a communication abnormality has occurred, the terminal device 2005 forms a status check prompting image for prompting the user to check the status of the device 3 and the communication control device 2, and displays the image on the display unit 504 (step S2012). Here, the terminal device 2005 displays, for example, a status check prompting image GA2002 as shown in Fig. 17(B) on the display unit 504. The status check prompting image GA2002 includes a message image M2002 including a message prompting the user to check the status of the device 3 and the communication control device 2, and a button image BU2002 selected when deleting the status check prompting image GA2002.

[0066] Returning to FIG. 18, the terminal device 2005 then generates communication status notification information including the communication status information and device identification information stored in the communication status storage unit 531 (step S2013), and the generated communication status notification information is transmitted from the terminal device 2005 to the cloud server 2001 (step S2014). On the other hand, upon acquiring the communication status notification information, the cloud server 2001 extracts the communication status information included in the acquired communication status notification information, and identifies the location of the abnormality based on the extracted communication status information. Then, the abnormality determination unit 2112 updates the abnormality location information stored in the device status storage unit 2131 using the abnormality location information indicating the identified location of the abnormality (step S2015). Thereafter, a series of processes from step S6 onwards are executed.

[0067] Next, assume that the user performs the above-mentioned device status acquisition operation on the input unit 405 of the terminal device 4. In this case, the terminal device 4 accepts the device status acquisition operation and generates the above-mentioned monitoring status request information (step S9), and the generated monitoring status request information is transmitted from the terminal device 4 to the cloud server 1 (step S10). On the other hand, upon receiving the above-mentioned monitoring information request information, the cloud server 1 generates monitoring information including the device status information, device identification information, location identification information, floor information, abnormality location information, date and time information, and apartment identification information of each of the multiple devices 3 stored in the device status storage unit 131 (step S2016). Then, the generated monitoring information is transmitted from the cloud server 1 to the terminal device 4 (step S2017). On the other hand, when the terminal device 4 acquires the monitoring information, it extracts the device status information, device identification information, location identification information, floor information, abnormality occurrence location information, date and time information, and apartment identification information of each of the multiple devices 3 managed by the aggregator contained in the acquired monitoring information, and stores the extracted information in the device status storage unit 431 in association with each other (step S2018). Next, the terminal device 4 uses the device status information, device identification information, location identification information, floor information, date and time information, and apartment identification information of each of the multiple devices 3 stored in the device status storage unit 431 to form a device status notification image that notifies the user of the status of each of the multiple devices 3, and displays the image on the display unit 404 (step S2019).

[0068] 19, for example, and displays it on the display unit 404. Here, the device status notification image GA1 includes a message image M11 displaying a MAC address that is the device status identification information, a message image M12 indicating the room number of the dwelling unit H[j,i] identified by the location identification information, a message image M13 indicating the status of the device 3, a message image M14 indicating the date and time when the device status notification information was acquired, and a message image M2031 indicating the location where the communication abnormality occurred.

[0069] Next, the device management process executed by the cloud server 2001 according to the present embodiment will be described with reference to FIG. 20. In FIG. 20, the same processes as those in the first embodiment are denoted by the same reference numerals as those in FIG. 11. First, after the processes in steps S101 and S102 are executed, the abnormality determination unit 2112 determines whether the above-mentioned device state determination time has arrived (step S103). Here, when the abnormality determination unit 2112 determines that the device state determination time has arrived (step S103: Yes), it determines whether a communication abnormality has occurred (step S104). Here, when the abnormality determination unit 2112 determines that a device communication abnormality has occurred (step S104: Yes), it generates device state information indicating a communication interruption, and updates the device state information of the corresponding device 3 stored in the device state storage unit 131 using the generated device state information (step S105). Next, the abnormality determination unit 2112 notifies the communication status acquisition unit 2121 of the location identification information identifying the dwelling unit H[j,i] in which the device 3 in which the communication abnormality has occurred is installed. Then, upon being notified of the location identification information, the communication status acquisition unit 2121 generates communication abnormality occurrence notification information and transmits it to the terminal device 2005 identified by the terminal device identification information corresponding to the notified location identification information and stored in the terminal device information storage unit 2133 (step S2101).

[0070] Next, the communication status acquisition unit 2121 judges whether or not the communication status notification information transmitted from the terminal device 2005 has been acquired (step S2102). Here, if the communication status acquisition unit 2121 judges that the communication status notification information has not been acquired (step S2102: No), the processing from step S106 onwards is executed as it is. On the other hand, if the communication status acquisition unit 2121 judges that the communication status notification information has been acquired (step S2102: Yes), it extracts the communication status information included in the acquired communication status notification information and notifies the abnormality determination unit 2112. Then, the abnormality determination unit 2112 specifies the abnormality occurrence location based on the communication status information notified from the communication status acquisition unit 2121, and updates the abnormality occurrence location information stored in the device status storage unit 2131 using the abnormality occurrence location information indicating the specified abnormality occurrence location (step S2103). Then, a series of processing from step S106 onwards is executed.

[0071] Next, the communication abnormality occurrence location specification process executed by the terminal device 2005 according to the present embodiment will be described with reference to FIG. 21. First, the communication abnormality occurrence notification acquisition unit 511 judges whether or not the communication abnormality occurrence notification information transmitted from the cloud server 2001 has been acquired (step S201). Here, the communication abnormality occurrence notification acquisition unit 511 repeats the process of step S201 as long as it judges that the communication abnormality occurrence notification information has not been acquired (step S201: No). On the other hand, when the communication abnormality occurrence notification acquisition unit 511 judges that the communication abnormality occurrence notification information has been acquired (step S201: Yes), it notifies the display control unit 512 and the communication status confirmation unit 513 of the communication abnormality occurrence notification information. Then, the display control unit 512 forms the above-mentioned communication abnormality occurrence notification image and displays it on the display unit 504 (step S202). Next, the communication status confirmation unit 513 judges whether or not the permission operation performed by the user on the input unit 505 has been accepted (step S203). Here, if the communication status checking unit 513 determines that the non-permission operation performed by the user on the input unit 505 has been accepted (step S203: No), the process of step S201 is executed again.

[0072] On the other hand, when the communication status check unit 513 determines that the permission operation has been received (step S203: Yes), it generates response request information addressed to the device 3 and transmits it to the device 3 (step S204). Next, the communication status check unit 513 determines whether or not it has acquired response information transmitted from the device 3 (step S205). Here, when the communication status check unit 513 determines that it has acquired response information transmitted from the device 3 (step S205: Yes), it generates communication status information indicating that communication with the device 3 is normal, stores the information in the communication status storage unit 531 (step S206), and then executes the process of step S209 described later. On the other hand, when the communication status check unit 513 determines that it has not acquired response information transmitted from the device 3 (step S205: No), it determines whether or not a preset waiting time has elapsed (step S207). Here, when the communication status check unit 513 determines that the waiting time has not yet elapsed (step S207: No), the process of step S205 is executed again. On the other hand, when the communication status confirmation unit 513 determines that the waiting time has elapsed (step S207: Yes), it generates communication status information indicating that an abnormality has occurred in the communication with the device 3 and stores the information in the communication status memory unit 531 (step S208).

[0073] Thereafter, the communication status check unit 513 generates response request information addressed to the cloud server 2001 and transmits it to the cloud server 2001 (step S209). Next, the communication status check unit 513 judges whether or not response information transmitted from the cloud server 2001 has been acquired (step S210). Here, if the communication status check unit 513 judges that the response information transmitted from the cloud server 2001 has been acquired (step S210: Yes), the communication status check unit 513 generates communication status information indicating that communication with the cloud server 2001 is normal, stores the communication status information in the communication status storage unit 531 (step S211), and then executes the process of step S214 described later. On the other hand, if the communication status check unit 513 judges that the response information transmitted from the cloud server 2001 has not been acquired (step S210: No), the communication status check unit 513 judges whether or not a preset waiting time has elapsed (step S212). Here, if the communication status check unit 513 determines that the waiting time has not yet elapsed (step S212: No), the process of step S210 is executed again. On the other hand, if the communication status check unit 513 determines that the waiting time has elapsed (step S212: Yes), the communication status check unit 513 generates communication status information indicating that an abnormality has occurred in the communication with the cloud server 2001, and stores the communication status information in the communication status storage unit 531 (step S213).

[0074] Next, the display control unit 512 determines whether or not a communication abnormality has occurred based on the communication status information stored in the communication status storage unit 531 (step S214). If the display control unit 512 determines that a communication abnormality has not occurred (step S214: No), the process of step S216 described below is executed. On the other hand, if the display control unit 512 determines that a communication abnormality has occurred (step S214: Yes), the display control unit 512 forms a status check prompting image that prompts the user to check the status of the device 3 or the communication control device 2, and displays the image on the display unit 504 (step S215).

[0075] Thereafter, communication status notification unit 514 generates communication status notification information including the communication status information stored in communication status storage unit 531 and the device identification information, and transmits the communication status notification information to cloud server 2001 (step S216). Next, the process of step S201 is executed again.

[0076] As described above, in the device management system according to the present embodiment, the abnormality determination unit 2112 identifies the location of the abnormality based on the communication status information. Then, the abnormality determination unit 2112 updates the abnormality location information stored in the device status storage unit 2131 using the abnormality location information indicating the identified location of the abnormality. In this way, when a communication abnormality occurs between the device 3 and the cloud server 2001, the cause of the communication abnormality can be identified, and therefore a countermeasure for restoring communication between the device 3 and the cloud server 2001 can be accurately grasped.

[0077] Incidentally, as a method for identifying the cause of a communication abnormality between the device 3 and the cloud server 2001, it is possible to manage the communication history in the communication control device 2, and have the terminal device communicate with the communication control device 2 without going through the local network NW2, acquire log information indicating the communication history transmitted from the communication control device 2, and display the log information on the display unit. However, in this method, when the terminal device acquires the log information by wireless communication with the communication control device 2, the terminal device needs to be located within a distance capable of wireless communication with the communication control device, and therefore the administrator who manages the device 3 or the contractor entrusted by the administrator needs to go to the place where the communication control device 2 is installed, and it takes time to identify the cause of the communication abnormality. In contrast, according to the device management system according to the present embodiment, the administrator can identify the cause of the communication abnormality without going to the place where the communication control device 2 is installed, and therefore the convenience of the administrator of the device 3 can be improved.

[0078] (Embodiment 3) The equipment management system of this embodiment differs from embodiment 1 in that the abnormality occurrence status aggregation unit aggregates at least one of the number of times an abnormality has occurred and the abnormality occurrence cycle for each of multiple devices based on the equipment status information of each of the multiple devices within a previously set aggregation period in the past.

[0079] As shown in FIG. 22, the device management system according to the present embodiment includes a terminal device 4 and a cloud server 3001. In FIG. 22, the same components as those in the first embodiment are denoted by the same reference numerals as those in FIG. 3. The hardware configuration of the cloud server 3001 is the same as that of the cloud server 1 according to the first embodiment. In the description of the present embodiment, the hardware configuration will be described using the same reference numerals as those in FIG. 2 as appropriate. The CPU 101 of the cloud server 3001 reads out a program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby functioning as a device status acquisition unit 111, an abnormality determination unit 112, an abnormality occurrence status aggregation unit 3113, a device status notification unit 114, an abnormality occurrence status notification unit 3115, a warning determination unit 3116, an occurrence status detail notification request acquisition unit 117, an email generation unit 118, and an email transmission unit 119. The auxiliary storage unit 103 also has an appliance status storage unit 3131, an abnormality occurrence status storage unit 132, and an abnormal appliance status storage unit 3133. As shown in Fig. 23 for example, the appliance status storage unit 3131 chronologically stores appliance status information indicating the past status of the appliance 3 installed in each dwelling unit H[j,i] in association with appliance identification information of the appliance 3, location identification information identifying each dwelling unit H[j,i] in which the appliance 3 is installed, and date and time information indicating the date and time when the cloud server 1 acquired the appliance status information. The appliance status storage unit 431 also stores the appliance status information in association with the apartment house identification information and floor information.

[0080] 24, the abnormal device status storage unit 3133 stores occurrence count information indicating the number of times an abnormality occurred in the device 3 in each of a plurality of preset time periods and continuous day information indicating the number of days the abnormality continued to occur, in association with abnormality type information indicating the type of the abnormality that occurred, occurrence time period information, and device identification information of the device 3. The example shown in FIG. 24 indicates that, for the device 3 identified by the device identification information IDE[2], five abnormalities of "alert 1" occurred in the time period "13:00-13:30" and continued for five days. It also indicates that one abnormality of "alert 2" occurred in each of the time periods "13:00-13:30" and "13:30-14:00".

[0081] Returning to FIG. 3, when a preset time for counting abnormality occurrence status arrives, the abnormality occurrence status counting unit 3113 refers to the latest device status information stored in the device status storage unit 131 to determine whether or not there is a device 3 in which an abnormality has occurred. Then, when it is determined that there is a device 3 in which an abnormality has occurred, the abnormality occurrence status counting unit 3113 counts the number of abnormality occurrences and the duration of abnormality occurrences for each of the multiple devices 3, stratified by the content of the abnormality and multiple preset time periods, for each device 3, based on the device status information of each of the multiple devices 3 during a past preset counting period stored in the device status storage unit 131. Then, the abnormality occurrence status counting unit 3113 stores, in the abnormal device status storage unit 3133, the occurrence number information and duration information indicating the number of abnormality occurrences and the duration of abnormality occurrences corresponding to the combination of the content of the abnormality and the time period, in association with the abnormality type information, occurrence time period information, and device identification information indicating the content of the abnormality.

[0082] The attention determination unit 3116 determines whether or not at least one of the number of occurrences of the abnormality indicated by the occurrence count information and the duration of the occurrence of the abnormality indicated by the duration information satisfies a preset attention criterion for alerting the user. Then, when it is determined that at least one of the number of occurrences of the abnormality and the duration of the occurrence of the abnormality satisfies the attention criterion, the attention determination unit 3116 stores attention target information indicating the device identification information of the corresponding device 3 and the location identification information of the corresponding installation location in the abnormality occurrence status storage unit 132.

[0083] When the abnormality occurrence status notification unit 3115 acquires abnormality occurrence status notification request information transmitted from the terminal device 4, if the abnormality occurrence status memory unit 132 stores equipment identification information of equipment 3 for which at least one of the number of abnormalities and the duration of the abnormality occurrence satisfies the warning criterion, and location identification information of the installation location of the equipment 3, the abnormality occurrence status notification unit 3115 generates abnormality occurrence status information including the abnormality occurrence number information and abnormality occurrence rate information stored in the abnormality occurrence status memory unit 132, the occurrence number information and duration information stored in the abnormal device status memory unit 3133, and the warning target information, and transmits the generated abnormality occurrence status information to the terminal device 4.

[0084] Next, the operation of the device management system according to the present embodiment will be described with reference to Fig. 25 to Fig. 27. First, as shown in Fig. 25, when a preset time for counting abnormality occurrence status arrives, the cloud server 3001 refers to the latest device status information stored in the device status storage unit 131 to determine whether or not there is a device 3 in which an abnormality has occurred, and assumes that it has been determined that there is a device 3 in which an abnormality has occurred (step S3001). In this case, the cloud server 3001 identifies the device status information stored in the device status storage unit 131 for the device 3 in which an abnormality has occurred within a past preset counting period (step S3002). Next, the cloud server 3001 counts the number of abnormality occurrences and the duration of the abnormality occurrence for each device 3 in which an abnormality has occurred, stratifying the abnormality by the type of abnormality and a plurality of preset time periods. Then, the cloud server 3001 stores, for each device 3 in which an abnormality has occurred, occurrence count information and duration information indicating the content of the abnormality, the number of times the abnormality has occurred corresponding to the combination of time periods, and the duration of the abnormality, in the abnormal device status memory unit 3133 in association with abnormality type information indicating the content of the abnormality, occurrence time period information, and device identification information (step S3003).

[0085] Next, it is assumed that the cloud server 3001 determines that at least one of the number of occurrences of an abnormality and the duration of the abnormality indicated by the occurrence count information and the duration information stored in the abnormal device status storage unit 3133 satisfies a preset warning criterion for warning a user (step S3004).In this case, the cloud server 3001 generates warning target information including device identification information of the corresponding device and location identification information of the corresponding installation location, and stores the information in the abnormality occurrence status storage unit 132 (step S3005).

[0086] Thereafter, when the user performs the abnormality occurrence status acquisition operation on the input unit 405 of the terminal device 4, the terminal device 4 accepts the abnormality occurrence status acquisition operation and generates the abnormality occurrence status notification request information (step S15). Then, the generated abnormality occurrence status notification request information is transmitted from the terminal device 4 to the cloud server 1 (step S16). Meanwhile, when the cloud server 3001 acquires the abnormality occurrence status notification request information, it generates abnormality occurrence status information including the abnormality occurrence number information, abnormality occurrence ratio information, and attention target information stored in the abnormality occurrence status storage unit 132 (step S17). Next, the generated abnormality occurrence status information is transmitted from the cloud server 1 to the terminal device 4 (step S18). Meanwhile, when the terminal device 4 acquires the abnormality occurrence status notification information, it extracts the abnormality occurrence number information and abnormality occurrence ratio information, the apartment identification information, and the attention target information for each of the multiple apartment buildings B[j] included in the acquired abnormality occurrence status information, and stores these pieces of information in the abnormality occurrence status storage unit 432 in association with each other (step S19). Next, the terminal device 4 uses the abnormality occurrence number information, abnormality occurrence rate information, abnormality mode information, floor information, apartment building identification information, and warning target information stored in the abnormality occurrence status memory unit 432 to form an abnormality occurrence status notification image to notify the user of the abnormality occurrence status of multiple devices 3, and displays it on the display unit 404 (step S20).

[0087] Here, the terminal device 4 forms an abnormality occurrence status notification image GA3003 as shown in FIG. 26, for example, and displays it on the display unit 404. Here, the abnormality occurrence status notification image GA3003 includes an icon image GA311 representing each of the multiple apartment buildings B[j]. Inside each icon image GA311, a message image M311 representing the number of devices 3 in which an abnormality has occurred and a bar image GA3B whose length changes according to the ratio of devices 3 in which an abnormality has occurred are arranged. Here, inside the icon image GA311 corresponding to the apartment building B[j] in which a device 3 in which at least one of the number of times an abnormality has occurred and the duration of the abnormality has met the attention calling criterion in the abnormality occurrence status notification image GA3003, a mark image GA3003M for calling the attention of the user is arranged.

[0088] Returning to FIG. 25, it is assumed that the user performs an abnormality occurrence status detail display operation on the input unit 405 of the terminal device 4 to display details of the abnormality occurrence status on the display unit 404 for, for example, the apartment house B[j] corresponding to the icon image for calling attention described above. In this case, the terminal device 4 generates the above-mentioned occurrence status detail notification request information (step S21), and the generated occurrence status detail notification request information is transmitted from the terminal device 4 to the cloud server 1 (step S22). On the other hand, when the cloud server 1 acquires the occurrence status detail notification request information, it generates abnormality occurrence status information including the abnormality occurrence number information and abnormality occurrence ratio information stored in the abnormality occurrence status storage unit 132, and the above-mentioned occurrence number information and duration information stored in the abnormal device status storage unit 3133 (step S3006). Then, the generated abnormality occurrence status information is transmitted from the cloud server 1 to the terminal device 4 (step S24). On the other hand, when the abnormality occurrence status notification information is acquired, the terminal device 4 extracts the abnormality occurrence number information and abnormality occurrence ratio information, the apartment identification information, the floor information, the number of occurrences information, and the duration information for each of the multiple apartment buildings B[j] included in the acquired abnormality occurrence status information, and stores these pieces of information in the abnormality occurrence status storage unit 432 in association with each other (step S3007). After that, the terminal device 4 uses the abnormality occurrence number information, the abnormality occurrence ratio information, the abnormality mode information, the floor information, the apartment identification information, the number of occurrences information, and the duration information stored in the abnormality occurrence status storage unit 432 to form an abnormality occurrence status detail notification image that notifies the user of the abnormality occurrence status of the multiple devices 3, and displays it on the display unit 404 (step S3008). Here, the terminal device 4 forms an abnormality occurrence status detail notification image GA3004 as shown in FIG. 27(A), for example, and displays it on the display unit 404. Here, the abnormality occurrence status details notification image GA3004 includes a message image M3004 indicating the occurrence status of an abnormality in the target apartment building B[j].

[0089] Next, as shown in FIG. 28, the cloud server 3001 generates mail information including message information and user identification information for identifying the user of the terminal device 4 based on the abnormality occurrence number information and abnormality occurrence ratio information, abnormality mode information, apartment house identification information, and floor information stored in the abnormality occurrence status storage unit 132, and the occurrence number information and duration information stored in the abnormal device status storage unit 3133 (step S3009). Then, the generated mail information is transmitted from the cloud server 1 to the mail server 6 (step S28). On the other hand, when the mail server 6 acquires the mail information, it extracts the message information and the user identification information included in the acquired mail information, and stores the extracted information in the mail storage unit in association with each other (step S29). Then, it is assumed that the user performs a mail viewing operation on the input unit 405 of the terminal device 4 to view the message of the mail. In this case, the terminal device 4 accepts the mail viewing operation, and the above-mentioned mail request information is transmitted from the terminal device 4 to the mail server 6 (step S30). On the other hand, when the mail server 6 acquires the mail request information, it identifies message information corresponding to the user identification information included in the acquired mail request information, and generates mail information including the identified message information (step S31). The generated mail information is then transmitted from the mail server 6 to the terminal device 4 (step S32). On the other hand, when the terminal device 4 acquires the mail information, it forms a mail viewing image based on the acquired mail information and displays it on the display unit 404 (step S33). Here, the terminal device 4 forms a mail viewing image GA3005 as shown in FIG. 27(B), for example, and displays it on the display unit 404. Here, the mail viewing image GA5 includes a message image M3005 that indicates the occurrence of an abnormality in the target apartment building B[j].

[0090] Next, the device management process executed by the cloud server 3001 according to the present embodiment will be described with reference to FIG. 29. In FIG. 29, the same processes as those in the first embodiment are denoted by the same reference numerals as those in FIG. 11. First, after the processes of steps S101 and S102 are executed, the abnormality occurrence status compilation unit 3113 judges whether or not a preset abnormality occurrence status compilation time has arrived (step S3101). Here, if the abnormality occurrence status compilation unit 3113 judges that the abnormality occurrence status compilation time has not yet arrived (step S3101: No), the process of step S103 is executed as is. On the other hand, if the abnormality occurrence status compilation unit 3113 judges that the abnormality occurrence status compilation time has arrived (step S3101: Yes), it refers to the latest device status information stored in the device status storage unit 131 and judges whether or not there is a device 3 in which an abnormality has occurred (step S3102). Here, if the abnormality occurrence status tabulation unit 3113 determines that all devices 3 are normal (step S3102: No), the process of step S103 is executed as is. On the other hand, if the abnormality occurrence status tabulation unit 3113 determines that there is a device 3 in which an abnormality has occurred (step S3102: Yes), it identifies the device status information of each device 3 in which an abnormality has occurred during a past preset tabulation period stored in the device status storage unit 131 (step S3103). Next, based on the device status information of the identified device 3 in which an abnormality has occurred, the abnormality occurrence status tabulation unit 3113 tabulates the number of times an abnormality has occurred and the duration of the abnormality for each device 3, stratified by the type of abnormality and a plurality of preset time periods, for each device 3. Then, the abnormality occurrence status tabulation unit 3113 stores, for each device 3, occurrence count information and duration information indicating the number of occurrences of an abnormality corresponding to the combination of the content of the abnormality and the time period, in the abnormality device status storage unit 3133 in association with the abnormality type information indicating the content of the abnormality, the occurrence time period information, and the device identification information (step S3104). Here, the abnormality occurrence status tabulation unit 113 performs processing to count the number of device status information indicating that an abnormality has occurred in the device 3 (occurrence count) and the number of days (duration) of the abnormality during the tabulation period, for example, by dividing the occurrence time period into 30-minute intervals.The length of each occurrence time period is not limited to 30 minutes, but may be set to any length.

[0091] Next, the attention determination unit 3116 determines whether or not at least one of the number of occurrences of the abnormality indicated by the occurrence number information and the duration of the abnormality indicated by the duration information satisfies a preset attention criterion for alerting the user (step S3105). If the attention determination unit 3116 determines that both the number of occurrences of the abnormality and the duration of the abnormality do not satisfy the attention criterion (step S3105: No), the process of step S103 is executed as is. On the other hand, if the attention determination unit 3116 determines that at least one of the number of occurrences of the abnormality and the duration of the abnormality meets the attention criterion (step S3105: Yes), the attention determination unit 3116 stores attention target information indicating the device identification information of the corresponding device 3 and the location identification information of the corresponding installation location in the abnormality occurrence status storage unit 132 (step S3106). Then, a series of processes from step S103 onwards are executed. Here, the attention determination unit 3116 determines that the attention criteria are met, for example, when there is a time period in which an abnormality in the device 3 occurs four or more times and continues for four or more days. For example, when an abnormality in the device 3 of "alert 1" occurs for five days during the occurrence time period of "13:00-13:30", the attention determination unit 3116 determines that the attention criteria are met. On the other hand, when an abnormality in the device 3 of "alert 2" occurs once during the occurrence time period of "13:30-14:00" on "4 / 28" and once during the occurrence time period of "13:00-13:15" on "5 / 1", the attention determination unit 3116 determines that the attention criteria are not met.

[0092] As described above, according to the device management system of this embodiment, when the attention calling determination unit 3116 determines that at least one of the number of times an abnormality has occurred and the duration of the abnormality has satisfied the attention calling criterion, the attention calling determination unit 3116 stores attention calling target information indicating the device identification information of the corresponding device 3 and the location identification information of the corresponding installation location in the abnormality occurrence status storage unit 132. This makes it possible to notify the user at an early stage of an abnormality that has repeatedly occurred continuously for a relatively long period of time, and therefore makes it possible to normalize the device 3 before the abnormality becomes serious.

[0093] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-mentioned embodiments. For example, the terminal device 4 may display, on the display unit 404, an abnormality occurrence status notification image including an icon image GA4311 representing the apartment house B[j], a message image M311 arranged inside the icon image GA4311, and a bar image GA4003B arranged below the icon image GA4311 and changing in length depending on the proportion of devices 3 in which an abnormality has occurred, as shown in FIG. 30(A). Alternatively, the terminal device 4 may display, on the display unit 404, an abnormality occurrence status notification image including an icon image GA5311 representing the apartment house B[j], a message image M311 arranged inside the icon image GA5311, and a bar image GA5003B arranged so as to fill in the icon image GA5311 from the left end inside the icon image GA4311 and changing in length depending on the proportion of devices 3 in which an abnormality has occurred, as shown in FIG. 30(B).

[0094] In addition, in embodiment 3, the abnormality occurrence status aggregation unit 3113 may aggregate the number of times an abnormality has occurred and the period during which the abnormality occurs for each device 3 based on the device status information of the device 3 in which an abnormality has occurred, stratifying the number of times an abnormality has occurred and the period during which the abnormality occurs for each device 3 according to the type of abnormality.

[0095] In addition, in embodiments 1 to 3, the cloud server 1, 2001, 3001 may generate email information when the warning determination unit 116, 3116 determines that the above-mentioned warning criteria are met, and the email sending unit 119 may send the generated email information to the email server 6, so that the user of the terminal device 4 can receive the email.

[0096] Furthermore, in the first to third embodiments, the device 3 may not include the apartment house identification information, location identification information, and floor information in the device status notification information. That is, the user may register the apartment house identification information, location identification information, and floor information in advance in the cloud server 1, 2001, 3001, and when the cloud server 1, 2001, 3001 acquires the device status notification information, the device status information included in the acquired device status notification information may be stored in the device status storage unit 131, 2131, 3131 in association with the device identification information, and the apartment house identification information, location identification information, and floor information that have been registered in advance.

[0097] In addition, the various functions of the cloud servers 1, 2001, 3001 and the terminal devices 4, 2005 according to the present disclosure may be realized by software, firmware, or a combination of software and firmware. In this case, the software or firmware may be written as a program, and the program may be stored and distributed in a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), and an MO (Magneto-Optical Disc), and the program may be read and installed in a computer to configure a computer capable of realizing each of the above-mentioned functions. In addition, when each function is realized by sharing the work between an OS (Operating System) and an application, or by cooperation between the OS and an application, only the parts other than the OS may be stored in the recording medium.

[0098] Furthermore, each program can be superimposed on a carrier wave and distributed via a network. For example, the program can be posted on a bulletin board (BBS, Bulletin Board System) on the network and distributed via the network. These programs can then be started and run under the control of the OS in the same way as other application programs, thereby enabling the above-mentioned processing to be performed.

[0099] Various aspects of the present disclosure are summarized below as appendices.

[0100] (Appendix 1) A first terminal device owned by a user; a device status acquisition unit that acquires device status information indicating a status of each of the plurality of devices; an abnormality determination unit that determines that a communication abnormality has occurred between the corresponding device and each of the plurality of devices when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; and a device status notifying unit that, when the communication abnormality occurs, transmits the device status information indicating the communication abnormality to the first terminal device. Equipment management system. (Appendix 2) a device status storage unit that stores the device status information of each of the plurality of devices in association with device identification information that identifies the corresponding device; a device status notification unit that transmits the device status information and the device identification information of each of the plurality of devices stored in the device status storage unit to the first terminal device, the device status acquisition unit acquires the device status information and the device identification information for each of the plurality of devices, and stores the acquired device status information and the acquired device identification information in the device status storage unit in association with each other; The first terminal device is A display unit; a display control unit that forms a device status notification image having a display aspect corresponding to the device identification information of each of the plurality of devices based on the device status information and the device identification information of each of the plurality of devices transmitted to the first terminal device, and displays the image on the display unit. 2. An equipment management system as described in claim 1. (Appendix 3) a device status storage unit that stores the device status information of each of the plurality of devices in association with location identification information that identifies an installation location where the corresponding device is installed; a device status notification unit that transmits the device status information and the location identification information of each of the plurality of devices stored in the device status storage unit to the first terminal device, the device status acquisition unit acquires the device status information and the location identification information for each of the plurality of devices, and stores the acquired device status information and the acquired location identification information in the device status storage unit in association with each other; The first terminal device is A display unit; a display control unit that forms a device status notification image having a display aspect that corresponds to a location identified by the location identification information, the device status information of each of the plurality of devices being transmitted to the first terminal device, and displays the image on the display unit. 3. An equipment management system according to claim 1 or 2. (Appendix 4) an abnormality occurrence status tabulation unit that tabulates at least one of the number of devices in which an abnormality has occurred and the ratio of devices in which an abnormality has occurred among the plurality of devices based on the device status information of each of the plurality of devices; and an abnormality occurrence status notifying unit configured to transmit, to the first terminal device, abnormality occurrence status information indicating at least one of the number of abnormal devices and the ratio of abnormal devices among the plurality of devices. 4. An equipment management system according to any one of claims 1 to 3. (Appendix 5) the device status storage unit further stores the device status information of each of the plurality of devices in association with group information indicating a group to which the installation location belongs when the installation location is classified into a plurality of groups set in advance; the device status notification unit transmits the group information together with the device status information and the location identification information of each of the plurality of devices stored in the device status storage unit to the first terminal device; the display control unit forms a device status notification image having a display mode corresponding to the installation location identified by the location identification information and the group to which the installation location belongs, based on the device status information of each of the plurality of devices, the location identification information, and the group information transmitted to the first terminal device, and displays the image on the display unit. 4. An equipment management system as described in Appendix 3. (Appendix 6) the abnormality occurrence status tabulation unit tabulates, for each building in which each of the plurality of devices is installed, at least one of the number of devices in which an abnormality is occurring and the ratio of devices in which an abnormality is occurring among the plurality of devices installed in one building based on the device status information of each of the plurality of devices; The at least one of the devices further includes an attention determination unit that determines whether or not a preset attention standard for calling the attention of a user is satisfied. 5. An equipment management system as described in claim 4. (Appendix 7) the abnormality occurrence status tabulation unit tabulates, for each of a plurality of regions obtained by dividing a building in which each of the plurality of devices is installed into a plurality of pre-defined regions based on the device status information of each of the plurality of devices, at least one of the number of devices in which an abnormality is occurring and the ratio of devices in which an abnormality is occurring among the plurality of devices installed in each of the plurality of devices installed in one of the plurality of regions; The at least one of the devices further includes an attention determination unit that determines whether or not a preset attention standard for calling the attention of a user is satisfied. 5. An equipment management system as described in claim 4. (Appendix 8) a second terminal device capable of communicating with each of the plurality of devices via a local network; a response unit that, when receiving response request information, which is transmitted from the second terminal device and requests transmission of response information, transmits the response information to a transmission source of the response request information via the wide area network; When the plurality of devices receive the response request information transmitted from the second terminal device via the local network, the devices transmit the response information to the second terminal device via the local network; The second terminal device is a communication status confirmation unit that confirms a communication status based on the response information transmitted from each of the plurality of devices and an acquisition status of the response information transmitted from the response unit after the transmission of the response request information, The abnormality determination unit further determines a location where the communication abnormality has occurred based on communication status information indicating the communication status. 3. An equipment management system according to claim 1 or 2. (Appendix 9) an abnormality occurrence status tabulation unit that tabulates at least one of the number of times an abnormality has occurred and the duration of the occurrence of an abnormality for each of the plurality of devices based on the device status information of each of the plurality of devices within a past preset tabulation period; an alert determination unit that determines whether or not at least one of the number of times the abnormality has occurred and the duration of the occurrence of the abnormality satisfies a preset alert criterion for alerting a user; and an abnormality occurrence status notification unit that, when it is determined that at least one of the number of occurrences of the abnormality and the duration of the occurrence of the abnormality satisfies the attention criterion, transmits to the first terminal device abnormality occurrence notification information that notifies that an abnormality has occurred, the abnormality occurrence notification information including attention target information indicating at least one of device identification information that identifies a corresponding device and location identification information that identifies a corresponding installation location. 4. An equipment management system according to any one of claims 1 to 3. (Appendix 10) a device status acquisition unit that acquires device status information indicating a status of each of the plurality of devices; an abnormality determination unit that determines that a communication abnormality has occurred between the corresponding device and each of the plurality of devices when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; and a device status notification unit that, when the communication abnormality occurs, transmits the device status information of each of the plurality of devices, including the device status information indicating the communication abnormality, to a first terminal device held by a user. Equipment management device. (Appendix 11) acquiring device status information indicating a status of each of the plurality of devices; determining that a communication abnormality has occurred between each of the plurality of devices and the corresponding device when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; When the communication abnormality occurs, transmitting the device status information indicating the communication abnormality to a first terminal device held by a user. Equipment management method. (Appendix 12) Computer, a device status acquisition unit that acquires device status information indicating the status of each of the plurality of devices; an abnormality determination unit that determines, for each of the plurality of devices, that a communication abnormality has occurred between the corresponding device and the device when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; a device status notifying unit that, when the communication abnormality occurs, transmits the device status information indicating the communication abnormality to a first terminal device held by a user; A program to function as a [Industrial Applicability]

[0101] The present disclosure is suitable as a hot water supply system that controls hot water heaters installed in each residence in an apartment building that has a bulk power receiving contract with an electric power company. [Explanation of symbols]

[0102] 1,2001,3001 Cloud server, 2 Communication control device, 3 Equipment, 4,2005 Terminal device, 6 Mail server, 8 BBR, 101,401,501 CPU, 102,402,502 Main memory, 103,403,503 Auxiliary memory, 106,406 Communication unit, 108 Timer, 109,409,509 Bus, 111 Equipment status acquisition unit, 112,2112 Abnormality determination unit, 113,3113 Abnormality occurrence status aggregation unit, 114 Equipment status notification unit, 115,3115 Abnormality occurrence status notification unit, 116 Warning determination unit, 117 Occurrence status detailed notification request acquisition unit, 118,3118 Mail generation unit, 119 Mail transmission unit, 131,431,2131,3131 Device status memory unit, 132, 432 Abnormality occurrence status memory unit, 404, 504 Display unit, 405, 505 Input unit, 411 Monitoring information acquisition unit, 412 Abnormality occurrence status acquisition unit, 413, 512 Display control unit, 414 Occurrence status detailed notification request unit, 415 Email acquisition unit, 561 Local communication unit, 562 Wide area communication unit, 511 Communication abnormality occurrence notification acquisition unit, 513 Communication status confirmation unit, 514 Communication status notification unit, 531 Communication status memory unit, 2120 Response unit, 2121 Communication status acquisition unit, 3133 Abnormal device status memory unit, B[0], B[1], B[j] Apartment building, BU2011, BU2012 Button image, GA1, GA2 Device status notification image, GA2C,GA21,GA22,GA23,GA24,GA211,GA221,GA231,GA241 Icon image, GA3B Bar image, GA3M Mark image, GA31,GA32,GA3003 Abnormality notification image, GA2001 Communication abnormality notification image, GA2002 Status confirmation prompt image, H[0,0],H[0,1],H[0,i] Residence, M11,M12,M13,M14,M41,M42,M51,M311,M2001,M2002,M3004 Message image, NW1 Wide area network, NW2 Local network

Claims

1. a first terminal device owned by a user; a device status acquisition unit that acquires device status information indicating a status of each of the plurality of devices; an abnormality determination unit that determines that a communication abnormality has occurred between the corresponding device and each of the plurality of devices when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; and a device status notifying unit configured to, when the communication abnormality occurs, transmit the device status information indicating the communication abnormality to the first terminal device. Equipment management system.

2. a device status storage unit that stores the device status information of each of the plurality of devices in association with device identification information that identifies the corresponding device; a device status notification unit that transmits the device status information and the device identification information of each of the plurality of devices stored in the device status storage unit to the first terminal device, the device status acquisition unit acquires the device status information and the device identification information for each of the plurality of devices, and stores the acquired device status information and the acquired device identification information in the device status storage unit in association with each other; The first terminal device is A display unit; a display control unit that forms a device status notification image having a display aspect corresponding to the device identification information of each of the plurality of devices based on the device status information and the device identification information of each of the plurality of devices transmitted to the first terminal device, and displays the image on the display unit, The device management system according to claim 1 .

3. a device status storage unit that stores the device status information of each of the plurality of devices in association with location identification information that identifies an installation location where the corresponding device is installed; a device status notification unit that transmits the device status information and the location identification information of each of the plurality of devices stored in the device status storage unit to the first terminal device, the device status acquisition unit acquires the device status information and the location identification information for each of the plurality of devices, and stores the acquired device status information and the acquired location identification information in the device status storage unit in association with each other; The first terminal device is A display unit; a display control unit that forms a device status notification image having a display aspect that corresponds to a location identified by the location identification information, the device status information being transmitted to the first terminal device and the location identification information of each of the plurality of devices, and displays the image on the display unit. The device management system according to claim 1 .

4. an abnormality occurrence status tabulation unit that tabulates at least one of the number of devices in which an abnormality has occurred and the ratio of devices in which an abnormality has occurred among the plurality of devices based on the device status information of each of the plurality of devices; and an abnormality occurrence status notifying unit configured to transmit, to the first terminal device, abnormality occurrence status information indicating at least one of the number of devices in which an abnormality has occurred and the ratio of devices in which an abnormality has occurred among the plurality of devices. The device management system according to claim 1 .

5. the device status storage unit further stores the device status information of each of the plurality of devices in association with group information indicating a group to which the installation location belongs when the installation location is classified into a plurality of groups set in advance; the device status notification unit transmits the group information together with the device status information and the location identification information of each of the plurality of devices stored in the device status storage unit to the first terminal device; the display control unit forms a device status notification image having a display mode corresponding to the installation location identified by the location identification information and the group to which the installation location belongs, based on the device status information of each of the plurality of devices, the location identification information, and the group information transmitted to the first terminal device, and displays the image on the display unit. The device management system according to claim 3 .

6. the abnormality occurrence status tabulation unit tabulates, for each building in which each of the plurality of devices is installed, at least one of the number of devices in which an abnormality is occurring and the ratio of devices in which an abnormality is occurring among the plurality of devices installed in one building based on the device status information of each of the plurality of devices; The at least one of the devices further includes an attention determination unit that determines whether or not a preset attention standard for calling the attention of a user is satisfied. The device management system according to claim 4.

7. the abnormality occurrence status counting unit counts, for each of a plurality of regions obtained by dividing a building in which each of the plurality of devices is installed into a plurality of pre-defined regions based on the device status information of each of the plurality of devices, at least one of the number of devices in which an abnormality is occurring and the ratio of devices in which an abnormality is occurring among the plurality of devices installed in one region; The at least one of the devices further includes an attention determination unit that determines whether or not a preset attention standard for calling the attention of a user is satisfied. The device management system according to claim 4.

8. a second terminal device capable of communicating with each of the plurality of devices via a local network; a response unit that, when receiving response request information, which is transmitted from the second terminal device and requests transmission of response information, transmits the response information to a transmission source of the response request information via the wide area network; When the plurality of devices receive the response request information transmitted from the second terminal device via the local network, the devices transmit the response information to the second terminal device via the local network; The second terminal device is a communication status confirmation unit that confirms a communication status based on the response information transmitted from each of the plurality of devices and an acquisition status of the response information transmitted from the response unit after the transmission of the response request information, The abnormality determination unit further determines a location where the communication abnormality has occurred based on communication status information indicating the communication status. The device management system according to claim 1 .

9. an abnormality occurrence status tabulation unit that tabulates at least one of the number of times an abnormality has occurred and the duration of the occurrence of an abnormality for each of the plurality of devices based on the device status information of each of the plurality of devices within a past preset tabulation period; an alert determination unit that determines whether or not at least one of the number of times the abnormality has occurred and the duration of the occurrence of the abnormality satisfies a preset alert criterion for alerting a user; and an abnormality occurrence status notification unit that, when it is determined that at least one of the number of occurrences of the abnormality and the duration of the occurrence of the abnormality satisfies the attention criterion, transmits to the first terminal device abnormality occurrence notification information that notifies that an abnormality has occurred, the abnormality occurrence notification information including attention target information indicating at least one of device identification information that identifies a corresponding device and location identification information that identifies a corresponding installation location. The device management system according to claim 1 .

10. an abnormality occurrence status tabulation unit that tabulates at least one of the number of times an abnormality has occurred and the duration of the occurrence of an abnormality for each of the plurality of devices based on the device status information of each of the plurality of devices within a past preset tabulation period; an alert determination unit that determines whether or not at least one of the number of times the abnormality has occurred and the duration of the occurrence of the abnormality satisfies a preset alert criterion for alerting a user; and an abnormality occurrence status notification unit that, when it is determined that at least one of the number of occurrences of the abnormality and the duration of the occurrence of the abnormality satisfies the attention criterion, transmits to the first terminal device abnormality occurrence notification information that notifies that an abnormality has occurred, the abnormality occurrence notification information including attention target information indicating at least one of device identification information of a corresponding device and location identification information of a corresponding installation location. The device management system according to claim 3 .

11. a device status acquisition unit that acquires device status information indicating a status of each of the plurality of devices; an abnormality determination unit that determines that a communication abnormality has occurred between the corresponding device and each of the plurality of devices when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; and a device status notifying unit that, when the communication abnormality occurs, transmits the device status information indicating the communication abnormality to a first terminal device held by a user. Equipment management device.

12. acquiring device status information indicating a status of each of the plurality of devices; determining that a communication abnormality has occurred between each of the plurality of devices and the corresponding device when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; When the communication abnormality occurs, transmitting the device status information indicating the communication abnormality to a first terminal device held by a user. Equipment management method.

13. Computer, a device status acquisition unit that acquires device status information indicating the status of each of the plurality of devices; an abnormality determination unit that determines, for each of the plurality of devices, that a communication abnormality has occurred between the corresponding device and the device when the elapsed time from the time when the device status information was last acquired exceeds a preset reference time; a device status notifying unit that, when the communication abnormality occurs, transmits the device status information indicating the communication abnormality to a first terminal device held by a user; A program to function as a

Images