Inspection management device and disaster prevention system

Abstract

To provide inspection management device and system, which enhance execution properties of periodic inspection of a fire alarm device.SOLUTION: In a disaster prevention system comprising a residential fire alarm system, an inspection management server, and a user terminal, an inspection monitoring unit 512 of an inspection management server 102 refers to inspection prompt timing information 523 to retrieve an inspection for which an inspection prompt timing has arrived; when an inspection that has arrived at the inspection prompt timing is extracted, the inspection monitoring unit generates a message to prompt a user to perform the inspection; and the inspection monitoring unit either transmits the generated message to a user terminal device of a fire alarm device, or transmits a signal to the fire alarm device to instruct it to perform a test.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to an apparatus and system for managing routine inspections of fire alarms. [Background technology]

[0002] Conventionally, residential fire alarm systems have been known. For example, Patent Document 1 describes a fire alarm system that uses wireless signals to link multiple fire alarms. Each fire alarm in this fire alarm system has the function of detecting a fire and the function of sounding an alarm. Therefore, when any fire alarm detects a fire, the fire alarm sounds an alarm and transmits information notifying the fire detection (fire detection information) to the other fire alarms by wireless signal. As a result, not only the fire alarm at the source of the fire but also multiple fire alarms link together and sound an alarm at the same time, so that the occurrence of a fire can be notified quickly and reliably. [Prior art documents] [Patent documents]

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

[0004] In order to ensure that such systems operate normally in the event of a fire, periodic inspections are essential, but inspections are optional and some users may forget to perform them. The present invention has been made in consideration of the above circumstances, and has an object to improve the feasibility of regular inspections of fire alarms. [Means for solving the problem]

[0005] In order to solve the above problems, the inspection management device of the present invention is equipped with a transmission unit that, when an inspection of a fire alarm is not performed after the inspection period has passed, sends a message to the terminal device of the user of the fire alarm urging the inspection, or sends a signal to the fire alarm to instruct it to perform a test. Effect of the Invention

[0006] According to the present invention, it is possible to improve the feasibility of carrying out regular inspections of fire alarms. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 shows an example of the configuration of a disaster prevention system 100. [Diagram 2] FIG. 2 shows an example of the configuration of the master unit 106A. [Diagram 3] FIG. 3 shows an example of the configuration of child device 106B. [Figure 4] FIG. 4 shows an example of the configuration of the relay device 107. [Diagram 5] FIG. 5 shows an example of the configuration of the inspection management server 102. [Figure 6] FIG. 6 shows an example of the user information 521. [Figure 7] FIG. 7 shows an example of the recommended inspection frequency information 522. [Figure 8] FIG. 8 shows an example of the inspection prompting time information 523. [Figure 9] FIG. 9 shows an example of the inspection log 524. [Figure 10] FIG. 10 shows an example of linked alarm processing. [Figure 11] FIG. 11 shows an example of the recovery process. [Figure 12] FIG. 12 shows an example of a user registration process. [Figure 13] FIG. 13 shows an example of the inspection monitoring process. [Figure 14] FIG. 14 shows an example of a single test process. [Figure 15] FIG. 15 shows an example of an inspection record process. [Figure 16]FIG. 16 illustrates an example of an inspection monitoring process 1600. [Figure 17] FIG. 17 illustrates an example of an automatic test process 1700. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] 1. First Example A first embodiment of the present invention will now be described.

[0009] 1-1.Configuration FIG. 1 shows an example of the configuration of a disaster prevention system 100. The disaster prevention system 100 includes a residential fire alarm system 101 , an inspection management server 102 , and a user terminal 103 .

[0010] Fire alarm system 101 is installed in a house 105 of a user 104, which is a fire prevention target. This fire alarm system 101 includes a parent fire alarm device 106A (hereinafter simply referred to as “parent device 106A”), a child fire alarm device 106B (hereinafter simply referred to as “child device 106B”), and a relay device 107. The master unit 106A and the slave unit 106B are each an interlocking type fire alarm device. In the following description, these will be collectively referred to as "fire alarm device 106." The relay device 107 is a device for transferring a fire detected by the fire alarm 106 to an external device. The relay device 107 is connected to a communication network 108.

[0011] The inspection management server 102 is a server for managing the inspection of the fire alarm 106. If the inspection of the fire alarm 106 is not performed even after the inspection time has passed, the inspection management server 102 transmits a message to the user terminal 103 to urge the inspection. The inspection management server 102 is connected to a communication network 108. The user terminal 103 is a terminal device used by a user 104. Specifically, the user terminal 103 is a smartphone. The user terminal 103 is connected to a communication network .

[0012] 1, in order to avoid the diagram becoming too complicated, one each of the fire alarm system 101, the user terminal 103, the user 104, and the house 105 is shown. However, the disaster prevention system 100 may include a plurality of each of these components. The main components of the disaster prevention system 100 will be described in more detail below.

[0013] 1-1-1. Master device 106A FIG. 2 shows an example of the configuration of the master unit 106A. The parent unit 106A includes a main memory device 201 such as a RAM, an auxiliary memory device 202 such as a flash memory, a processor 203 such as a CPU, an input device 204 such as a test button, an output device 205 such as an indicator light or speaker, a communication control unit 206 such as a wireless module, a fire detection unit 207, and a power supply unit 208.

[0014] Of these, the fire detection unit 207 detects a fire by detecting smoke and heat that are generated in association with the fire. The power supply unit 208 supplies power from a battery to each component of the master unit 106A. The main memory device 201 stores various programs, and the functions of a linked warning unit 211, a recovery unit 212, and a test unit 213 are realized by the processor 203 executing these programs.

[0015] When the fire detection unit 207 detects a fire or when an interlocking test is instructed by operating the test button (for example, by pressing and holding the button), the interlocking alarm unit 211 blinks an indicator light and outputs an alarm sound from a speaker. In addition, the interlocking alarm unit 211 transmits a fire interlocking signal to the slave device 106B and the relay device 107. Furthermore, when the linked alarm unit 211 receives a fire linkage signal from the child device 106B, it blinks the indicator light and outputs an alarm sound from the speaker. In addition, the linked alarm unit 211 transmits a fire linkage signal to the child device 106B and the relay device 107. This fire linkage signal is intended to ensure the linkage of the devices.

[0016] When the fire detection unit 207 no longer detects a fire and the recovery unit 212 receives a recovery notification from all the slave devices 106B, the recovery unit 212 stops the flashing of the indicator light and the output of the alarm sound. Then, the recovery unit 212 transmits a recovery linkage signal to all the slave devices 106B and the relay device 107.

[0017] When the test button is operated (e.g., pressed briefly), the test unit 213 executes an individual test. This individual test includes checking for dead batteries, sensor abnormalities, and radio wave abnormalities.

[0018] Next, the auxiliary storage device 202 will be described. The auxiliary storage device 202 stores a group ID 221. This group ID 221 is an ID for identifying the fire alarm system 101. This group ID 221 is included in signals transmitted and received within the system, and is used to identify the receiver.

[0019] 1-1-2. Child device 106B FIG. 3 shows an example of the configuration of child device 106B. The slave device 106B includes a main memory device 301 such as a RAM, an auxiliary memory device 302 such as a flash memory, a processor 303 such as a CPU, an input device 304 such as a test button, an output device 305 such as an indicator light or speaker, a communication control unit 306 such as a wireless module, a fire detection unit 307, and a power supply unit 308.

[0020] Of these, the fire detection unit 307 detects a fire by detecting smoke and heat that accompanies a fire. Power supply unit 308 supplies power from a battery to each component of child device 106B. The main memory device 301 stores various programs, and the functions of a linked warning unit 311, a recovery unit 312, and a test unit 313 are realized by the processor 303 executing these programs.

[0021] When the fire detection unit 307 detects a fire or when an interlocking test is instructed by operating the test button (for example, by pressing and holding it), the interlocking alarm unit 311 blinks the indicator light and outputs an alarm sound from the speaker. In addition, the interlocking alarm unit 311 transmits a fire interlocking signal to the other fire alarms 106 and the relay device 107. Furthermore, when the linked alarm unit 311 receives a fire linked signal from another fire alarm device 106, it blinks the indicator light and outputs an alarm sound from the speaker.

[0022] When the fire detection unit 307 no longer detects a fire, the recovery unit 312 transmits a recovery notification to the master unit 106A. After that, when the recovery unit 312 receives a recovery linkage signal from the master unit 106A, the recovery unit 312 stops flashing the indicator light and outputting the alarm sound.

[0023] When the test button is operated (e.g., pressed briefly), the test unit 313 executes an individual test. This individual test includes checking for dead batteries, sensor abnormalities, and radio wave abnormalities.

[0024] Next, the auxiliary storage device 302 will be described. The auxiliary storage device 302 stores a group ID 321. This group ID 321 is an ID for identifying the fire alarm system 101. This group ID 321 is included in signals transmitted and received within the system, and is used to identify the receiver.

[0025] 1-1-3.Relay device 107 The relay device 107 is a device for transferring a fire detected by the fire alarm 106 to an external device. The relay device 107 includes a main memory device 401 such as a RAM, an auxiliary memory device 402 such as a flash memory, a processor 403 such as a CPU, an input device 404 such as an operation button, an output device 405 such as an indicator light, a communication control unit 406 such as a wireless module, and a power supply unit 407.

[0026] Of these, the main memory device 401 stores various programs, and the processor 403 executes these programs to realize the function of a report transfer unit 411 . The notification unit 411 outputs a fire occurrence signal to a predetermined external device when it receives a fire interlocking signal from the fire alarm 106. Furthermore, the notification unit 411 outputs a recovery signal to a predetermined external device when it receives a recovery interlocking signal from the fire alarm 106.

[0027] The predetermined external device to which the signal is output is, for example, a security system installed in the house 105. The security system here is a system that detects theft, forgetting to lock the door, gas leaks, and the like that occur in the house 105 and sounds an alarm or reports the incident to a security company.

[0028] Next, the auxiliary storage device 402 will be described. The auxiliary storage device 402 stores a group ID 421. This group ID 421 is an ID for identifying the fire alarm system 101. This group ID 421 is included in signals transmitted and received within the system, and is used to identify the receiver.

[0029] 1-1-4. Inspection management server 102 The inspection management server 102 is a device for managing the inspection of the fire alarm device 106. FIG. The inspection management server 102 comprises a main memory device 501 such as a RAM, an auxiliary memory device 502 such as a HDD, a processor 503 such as a CPU, an input device 504 such as a keyboard or mouse, an output device 505 such as a display, and a communication control unit 506 such as a network card.

[0030] Of these, the main memory device 501 stores various programs, and the functions of a user registration unit 511, an inspection monitoring unit 512, and an inspection recording unit 513 are realized by the processor 503 executing these programs.

[0031] The user registration unit 511 performs user registration of the user 104. At that time, the user registration unit 511 accepts a request for a user registration screen from the user terminal 103. This request is transmitted by the user 104 reading a specific code with the user terminal 103. The specific code read at that time is specifically a two-dimensional code (e.g., QR code (registered trademark)) described in the instruction manual for the fire alarm 106 or the like.

[0032] When the user registration unit 511 receives the above request from the user terminal 103, it transmits a user registration screen to the terminal. The transmitted user registration screen allows the user to input the name, address, telephone number, email address, model name of the fire alarm 106, installation date of the fire alarm 106, etc. The user registration unit 511 stores the information inputted to this user registration screen in the auxiliary storage device 502 as user information.

[0033] Furthermore, the user registration unit 511 stores inspection prompt time information in the auxiliary storage device 502 based on the input information. The inspection prompt time information stored here includes a recommended inspection time and an inspection prompt time. Of these times, the recommended inspection time is determined according to the installation date of the fire alarm 106, the type of the fire alarm 106 (specifically, the model name), and the type of inspection (in other words, the test type) inputted into the above-mentioned user registration screen. On the other hand, the inspection prompt time is determined by adding a predetermined number of days (in this embodiment, as an example, 7 days) to the recommended inspection time.

[0034] The inspection monitoring unit 512 monitors the inspection status of the fire alarm 106 of the registered user 104. If the fire alarm 106 is not inspected even after the recommended inspection time has passed, the inspection monitoring unit 512 transmits a message to the user terminal 103 of the user 104 to urge the user 104 to inspect it.

[0035] Specifically, the message is sent when the inspection prompt time arrives. The inspection prompt time when this message is sent is updated to the next inspection prompt time once the inspection is performed. Therefore, the inspection monitoring unit 512 does not send a prompt message for an inspection that has already been performed. In other words, the inspection monitoring unit 512 sends a prompt message only for unperformed inspections that have passed the recommended inspection time.

[0036] When an inspection is performed on the fire alarm 106 of a registered user 104, the inspection recording unit 513 records the inspection. At that time, the inspection recording unit 513 receives a request transmitted from the user terminal 103 and transmits an inspection report screen to the terminal. The transmitted inspection report screen includes an inspection completion button. When the user 104 selects this inspection completion button, the inspection recording unit 513 stores an inspection log in the auxiliary storage device 502. The inspection log stored here includes the inspection date of the fire alarm 106.

[0037] Furthermore, in response to the above button selection, the inspection recording unit 513 updates the inspection prompt information stored in the auxiliary storage device 502. Specifically, the information updated here is the recommended inspection time and the inspection prompt time. Of these times, the recommended inspection time is determined according to the inspection date of the fire alarm 106, the type of the fire alarm 106 (specifically, the model name), and the type of inspection (in other words, the test type). On the other hand, the inspection prompt time is determined by adding a predetermined number of days (in this embodiment, as an example, 7 days) to the recommended inspection time.

[0038] Next, the auxiliary storage device 502 will be described. The auxiliary storage device 502 stores user information 521, recommended inspection frequency information 522, inspection prompt timing information 523, and inspection log 524. Each piece of information will be described below.

[0039] FIG. 6 shows an example of the user information 521. The user information 521 is information relating to the user 104. This user information 521 has columns for a user ID 601, a name 602, an address 603, a phone number 604, an email address 605, a model name 606, an installation date 607, and the like. Of these columns, the model name 606 stores the model name of the fire alarm 106 . The installation date 607 stores the date when the fire alarm system 101 was installed in the house 105 .

[0040] FIG. 7 shows an example of the recommended inspection frequency information 522. The recommended inspection frequency information 522 is information that associates the model name and the recommended inspection frequency of the fire alarm 106. This recommended inspection frequency information 522 has columns such as model name 701, test type 702, recommended inspection frequency 703, and the like.

[0041] Of these columns, the model name 701 stores the model name of the fire alarm 106 . A value indicating the type of test is stored in the test type 702. The stored value indicates either a single test or a linked test. A value indicating the recommended inspection frequency is stored in the recommended inspection frequency 703. For example, a stored value of "1 month" indicates that the recommended inspection frequency is once a month. As another example, a stored value of "12 months" indicates that the recommended inspection frequency is once every 12 months.

[0042] FIG. 8 shows an example of the inspection prompting time information 523. The inspection prompt time information 523 is information indicating the time when an inspection is prompted to the user 104. This inspection prompt time information 523 has columns such as a user ID 801, a model name 802, a test type 803, a recommended inspection time 804, and an inspection prompt time 805. Of these columns, the model name 802 stores the model name of the fire alarm 106 . A value indicating the type of test is stored in the test type 803. The value stored indicates either a single test or a linked test.

[0043] FIG. 9 shows an example of the inspection log 524. The inspection log 524 is information related to the inspections performed on the fire alarm 106. This inspection log 524 has columns such as a user ID 901, a test type 902, and an inspection date 903. Among these columns, a value indicating the type of test is stored in the test type 902. The stored value indicates either an independent test or an interlocking test.

[0044] 1-2.Operation The following describes the operation of the disaster prevention system 100. Specifically, the following describes linked alarm processing, recovery processing, user registration processing, inspection monitoring processing, single test processing, linked test processing, and inspection record processing.

[0045] 1-2-1. Linked alarm processing The linked alarm processing is processing executed by the fire alarm system 101 when a fire occurs. An example of this linked alarm processing is shown in Fig. 10. The linked alarm processing 1000 shown in the figure assumes that, of the fire alarm devices 106, the child device 106B detects a fire.

[0046] When a fire occurs within the monitoring area of ​​the child device 106B, the fire detection unit 307 of the child device 106B detects the fire (step 1001). Upon detection of the fire, the linked alarm unit 311 of the child device 106B blinks the indicator light and outputs an alarm sound from the speaker (step 1002). In addition, the linked alarm unit 311 transmits a fire linked signal to the other fire alarm devices 106 and the relay device 107 (step 1003).

[0047] When the linked alarm unit 311 of the other slave device 106B receives this fire linked signal, it blinks the indicator light and outputs an alarm sound from the speaker (step 1004).

[0048] When the report transfer unit 411 of the relay device 107 receives the fire interlocking signal, it outputs a fire occurrence signal to a predetermined external device (step 1005).

[0049] When the linked alarm unit 211 of the master unit 106A receives the fire linkage signal, it blinks the indicator light and outputs an alarm sound from the speaker (step 1006). In addition, the linked alarm unit 211 transmits a fire linkage signal to the slave unit 106B and the relay device 107 (step 1007). The purpose of transmitting this fire linkage signal is to ensure the linkage of the devices. The above is a description of the linked alarm processing 1000.

[0050] As described above, the linked alarm processing 1000 is based on the assumption that the child device 106B detects a fire. However, unlike this assumption, when the parent device 106A detects a fire, the linked alarm unit 211 of the parent device 106A blinks an indicator light and outputs an alarm sound from a speaker. The linked alarm unit 211 then transmits a fire linked signal to the child device 106B and the relay device 107.

[0051] When the linked alarm unit 311 of the slave device 106B receives this fire linked signal, it blinks the indicator light and outputs an alarm sound from the speaker. When the report transfer unit 411 of the relay device 107 receives the fire interlocking signal, it outputs a fire occurrence signal to a predetermined external device.

[0052] 1-2-2. Recovery process The restoration process is a process that is executed after a fire is extinguished by the fire alarm system 101. Figure 11 shows an example of this restoration process.

[0053] When a fire is extinguished in the monitoring area of ​​the slave device 106B, the fire detection unit 307 of the slave device 106B stops detecting the fire (step 1101). When the fire detection unit 307 of the slave device 106B stops detecting the fire, the recovery unit 312 of the slave device 106B transmits a recovery notification to the master device 106A (step 1102).

[0054] When the recovery unit 212 of the master unit 106A receives the recovery notification from all the slave units 106B (but only the slave units 106B that had detected a fire) and its own fire detection unit 207 no longer detects a fire (step 1103), it stops the flashing of its own indicator light and the output of the alarm sound (step 1104).Then, the recovery unit 212 transmits a recovery linkage signal to all the slave units 106B and the relay device 107 (step 1105).

[0055] Upon receiving this restoration linkage signal, restoration unit 312 of slave device 106B stops the flashing of the indicator light and the output of the alarm sound (step 1106).

[0056] When the relay device 107 receives the restoration link signal, the relay device 107 outputs a restoration signal to a predetermined external device (step 1107). The above is an explanation of the recovery process 1100.

[0057] 1-2-3. User registration process The user registration process is a process for registering in the inspection management server 102 that the user 104 is a user of the fire alarm system 101. Fig. 12 shows an example of this user registration process.

[0058] First, the user 104 reads the two-dimensional code written in the instruction manual for the fire alarm 106 with the user terminal 103 (step 1201). The two-dimensional code read here is, for example, a QR code (registered trademark), and is a code for requesting a user registration screen from the inspection management server 102. When the user terminal 103 reads this two-dimensional code, it requests the user registration screen from the inspection management server 102 (step 1202).

[0059] In response to this request, the user registration unit 511 of the inspection management server 102 transmits a user registration screen to the user terminal 103 (step 1203). The user terminal 103 receives and displays the transmitted user registration screen (step 1204). The user 104 inputs the necessary information into the displayed user registration screen (not shown) (step 1205). The necessary information input here includes the name, address, telephone number, email address, model name of the fire alarm 106, and installation date of the fire alarm system 101. After inputting the necessary information, the user 104 selects the send button. In response to this button operation, the user terminal 103 transmits the input information to the inspection management server 102 (step 1206).

[0060] When the user registration unit 511 of the inspection management server 102 receives the input information transmitted from the user terminal 103, it issues a user ID. Then, the user registration unit 511 associates the issued user ID with the input information and stores them as user information in the auxiliary storage device 502 (step 1207).

[0061] The user registration unit 511 also stores inspection prompt time information in the auxiliary storage device 502 based on the issued user ID and the input information (step 1208). The inspection prompt time information stored here includes the user ID, model name, test type, recommended inspection time, and inspection prompt time.

[0062] Among these, the user registration unit 511 refers to the recommended inspection frequency information 522 when specifying the recommended inspection timing. The user registration unit 511 refers to the recommended inspection frequency information 522 to specify the recommended inspection frequency corresponding to the model name of the fire alarm 106 for each test type. For example, the user registration unit 511 specifies "1 month" for the single test and "12 months" for the linked test. Then, the user registration unit 511 adds the specified recommended inspection frequency to the installation date of the fire alarm system 101 to calculate the recommended inspection timing for each test type. For example, the user registration unit 511 adds "1 month" to "2023 / 02 / 01" for the single test to calculate "2023 / 03 / 01", and adds "12 months" to "2023 / 02 / 01" for the linked test to calculate "2024 / 02 / 01".

[0063] Next, when specifying the inspection prompt timing, the user registration unit 511 adds a predetermined number of days (in this embodiment, as an example, 7 days) to the calculated recommended inspection timing to calculate the inspection prompt timing for each test type. For example, the user registration unit 511 adds "7 days" to "2023 / 03 / 01" to calculate "2023 / 03 / 08" for an independent test, and adds "7 days" to "2024 / 02 / 01" to calculate "2024 / 02 / 08" for an interlocking test. This concludes the description of the user registration process 1200.

[0064] 1-2-4. Inspection and monitoring process The inspection monitoring process is a process for urging the user 104 to inspect the fire alarm 106 if the inspection due date has passed. This inspection monitoring process is executed periodically by the inspection management server 102. FIG. 13 shows an example of this inspection and monitoring process.

[0065] First, the inspection monitoring unit 512 of the inspection management server 102 searches for inspections for which the inspection prompt time has arrived by referring to the inspection prompt time information 523 (step 1301). The inspections for which the inspection prompt time has arrived searched for here refer to inspections for which the execution date of this process is the inspection prompt time and inspections for which the execution date of this process is after the inspection prompt time.

[0066] If no inspection is extracted as a result of this search (NO in step 1302), this process ends. On the other hand, if an inspection is extracted as a result of this search (YES in step 1302), the inspection monitoring unit 512 executes step 1303.

[0067] In step 1303, the inspection monitoring unit 512 generates a message to prompt the user 104 to perform the extracted inspection. The generated message includes the user ID of the user 104, the type of inspection to be prompted (in other words, the test type), and a URL for reporting the inspection.

[0068] After creating the message, the inspection and monitoring unit 512 refers to the user information 521 to identify the email address of the user 104. Then, the inspection and monitoring unit 512 sends the created message to the identified email address (step 1304).

[0069] After sending the message, the inspection monitoring unit 512 returns to step 1301 and searches for another inspection for which the inspection prompt time has arrived.

[0070] The message transmitted by the inspection monitoring unit 512 is received by the destination user terminal 103. The user 104 of the user terminal 103 can notice that the recommended time for inspection has arrived by looking at the received message. The user 104 performs an individual test when prompted by the message, and performs an interlocking test when prompted by the message. The above is a description of the inspection monitoring process 1300.

[0071] 1-2-5. Single test processing The individual test process is a process for checking the functionality of the fire alarm 106. This individual test process is executed when the test button of the fire alarm 106 is operated (for example, pressed briefly) by the user 104. An example of this individual test process is shown in Fig. 14. In the following, the individual test process of the master unit 106A of the fire alarm unit 106 will be described.

[0072] First, the test unit 213 of the master unit 106A judges whether the battery is dead (step 1401). At that time, the test unit 213 judges whether the battery voltage value is less than a predetermined operating voltage value. If the result of this judgment is that the battery voltage value is less than the predetermined operating voltage value, the test unit 213 judges that the battery is dead.

[0073] Next, the test unit 213 judges whether or not the sensor is in an abnormal state (step 1402). At that time, the test unit 213 judges whether or not the output value of the fire detection unit 207 is within a predetermined normal range. If the result of this judgment is that the output value of the fire detection unit 207 is outside the predetermined normal range, the test unit 213 judges that the sensor is in an abnormal state.

[0074] Next, the test unit 213 judges whether or not there is a radio wave abnormality (step 1403). At this time, the test unit 213 judges whether or not a test signal has not been received from any child device 106B for a predetermined period or more. If the result of this judgment is that a test signal has not been received from any child device 106B for a predetermined period or more, the test unit 213 judges that there is a radio wave abnormality.

[0075] Finally, the test unit 213 blinks the indicator light and outputs an alarm sound from the speaker according to the determination results of steps 1401 to 1403 (step 1404). Specifically, if the test unit 213 is normal, it blinks the indicator light continuously and outputs a voice saying "normal". If the battery is dead, it blinks the indicator light once and outputs a voice saying "battery is dead". If the sensor is abnormal, it blinks the indicator light three times and outputs a voice saying "abnormal". If the radio wave is abnormal, it blinks the indicator light twice and outputs a voice saying "radio wave abnormal". The user 104 can check the state of the master unit 106A by observing the blinking of the indicator light and listening to the alarm sound. The above is a description of the single test process 1400.

[0076] Although the above description is of the individual test process executed by the parent unit 106A, the process can also be executed by the child unit 106B. When the process is executed by the child unit 106B, in step 1401, the test unit 313 judges whether or not the battery is dead. In step 1402, the test unit 313 judges whether or not the sensor is in an abnormal state based on the output value of the fire detection unit 307. In step 1403, the test unit 313 judges whether or not the radio wave is in an abnormal state. In this case, the test unit 313 judges whether or not the test signal has not been received from the parent unit 106A for a predetermined period of time or more. In step 1404, the test unit 313 blinks an indicator light and outputs an alarm sound from a speaker according to the judgment results of steps 1401 to 1403.

[0077] 1-2-6. Interlocking test processing The interlocking test process is a process for checking the interlocking operation function of the fire alarm 106. This interlocking test process is executed when the user 104 operates (for example, presses and holds) the test button of any of the fire alarms 106.

[0078] This interlocking test process is similar to the interlocking alarm process 1000 described above. Therefore, the interlocking test process will be described with reference to Fig. 10 again. Note that the following description assumes that the test button of the child device 106B is operated (e.g., pressed and held).

[0079] When the test button is operated (e.g., pressed and held), the linked alarm unit 311 of the child device 106B blinks the indicator light and outputs an alarm sound from the speaker (step 1002). In addition, the linked alarm unit 311 transmits a fire linkage signal to the other fire alarm devices 106 and the relay device 107 (step 1003).

[0080] When the linked alarm unit 311 of the other slave device 106B receives this fire linked signal, it blinks the indicator light and outputs an alarm sound from the speaker (step 1004).

[0081] When the report transfer unit 411 of the relay device 107 receives the fire interlocking signal, it outputs a fire occurrence signal to a predetermined external device (step 1005).

[0082] When the linked alarm unit 211 of the master unit 106A receives the fire linkage signal, it blinks the indicator light and outputs an alarm sound from the speaker (step 1006). In addition, the linked alarm unit 211 transmits a fire linkage signal to the slave unit 106B and the relay device 107 (step 1007). The purpose of transmitting this fire linkage signal is to ensure the linkage of the devices. The above is a description of the interlocking test process.

[0083] The user 104 can execute the above-mentioned interlocking test process, observe the flashing of the indicator lights of each fire alarm device 106, and listen to the alarm sounds, thereby confirming that the fire alarm system 101 is operating normally in interlocking mode.

[0084] The above description assumes that the test button of the child device 106B is operated (e.g., pressed and held) as described above. In contrast to this assumption, when the test button of the parent device 106A is operated (e.g., pressed and held), the linked alarm unit 211 of the parent device 106A blinks the indicator light and outputs an alarm sound from the speaker. Then, the linked alarm unit 211 transmits a fire linked signal to the child device 106B and the relay device 107.

[0085] When the linked alarm unit 311 of the slave device 106B receives this fire linked signal, it blinks the indicator light and outputs an alarm sound from the speaker. When the report transfer unit 411 of the relay device 107 receives the fire interlocking signal, it outputs a fire occurrence signal to a predetermined external device. Even if the test button of the master unit 106A is thus operated (eg, pressed and held), the user 104 can confirm that the fire alarm system 101 operates normally in conjunction with the master unit 106A.

[0086] 1-2-7. Inspection record processing The inspection record process is a process for recording the inspection of the fire alarm 106 in the inspection management server 102. This inspection record process is performed after the user 104 inspects the fire alarm 106. FIG. 15 shows an example of this inspection record process.

[0087] First, the user 104 displays the message sent in step 1304 of the above inspection monitoring process 1300, and selects the URL for the inspection report included in the message (step 1501). In response to the selection of the URL, the user terminal 103 requests the inspection report screen from the inspection management server 102 (step 1502).

[0088] In response to the request, the inspection record unit 513 of the inspection management server 102 transmits an inspection report screen to the user terminal 103 (step 1503). The user terminal 103 receives and displays the transmitted inspection report screen (step 1504). The displayed inspection report screen (not shown) includes input fields for the user ID and test type, and an inspection completion button.

[0089] The user 104 inputs the user ID and test type while referring to the above message, and selects the inspection completion button (step 1505). In response to this button selection, the user terminal 103 transmits an inspection completion notification including the input information to the inspection management server 102 (step 1506).

[0090] When the inspection recorder 513 of the inspection management server 102 receives this inspection completion notification, it stores the inspection log in the auxiliary storage device 502 (step 1507). The stored inspection log is composed of the user ID and test type contained in the received inspection completion notification, and the inspection date. Here, the inspection date is the date on which the inspection completion notification was received.

[0091] Next, upon receiving the inspection completion notification, the inspection recording unit 513 updates the inspection prompt information stored in the auxiliary storage device 502 (step 1508). The inspection prompt information to be updated is the inspection prompt information corresponding to the user ID and test type included in the inspection completion notification, in particular the recommended inspection time and the inspection prompt time.

[0092] When updating the recommended inspection time, the inspection record unit 513 refers to the recommended inspection frequency information 522. The inspection record unit 513 refers to the recommended inspection frequency information 522 to identify the recommended inspection frequency corresponding to the model name of the fire alarm 106 of the user 104. Then, the inspection record unit 513 adds the identified recommended inspection frequency to the current recommended inspection time to calculate the updated recommended inspection time. For example, the inspection record unit 513 adds "1 month" to "2023 / 03 / 01" for the single test to calculate "2023 / 04 / 01". As another example, the inspection record unit 513 adds "12 months" to "2024 / 02 / 01" for the linked test to calculate "2025 / 02 / 01". The inspection record unit 513 replaces the current recommended inspection time with the calculated recommended inspection time.

[0093] Next, when updating the inspection prompt time, the inspection record unit 513 calculates the inspection prompt time by adding a predetermined number of days (in this embodiment, as an example, 7 days) to the newly calculated recommended inspection time. For example, the inspection record unit 513 calculates "2023 / 04 / 08" for the independent test by adding "7 days" to "2023 / 04 / 01". As another example, the inspection record unit 513 calculates "2025 / 02 / 08" for the linked test by adding "7 days" to "2025 / 02 / 01". The inspection record unit 513 replaces the current inspection prompt time with the calculated inspection prompt time. The above is a description of the inspection record process 1500.

[0094] According to the first embodiment described above, if the inspection of the fire alarm 106 is not performed even after the inspection time has passed, a message for urging the inspection is transmitted to the user terminal 103. As a result, the feasibility of performing the regular inspection is improved.

[0095] 2. Second Example In the above-described first embodiment, if an inspection is not performed even after the recommended inspection time has passed, the user 104 is prompted to perform an inspection. In this embodiment, it is the user 104 who performs the inspection. In contrast, in the second embodiment described below, the inspection management server 111 automatically performs an individual test. Therefore, according to this embodiment, the user 104 does not need to perform an individual test manually. The following description of the second embodiment focuses on the differences from the first embodiment.

[0096] 2-1.Configuration 2-1-1. Master device 109A In this embodiment, a master unit 109A (not shown) is used instead of the master unit 106A. The master unit 109A differs from the master unit 106A in that it further includes a function called an automatic test unit 214 (not shown).

[0097] When the automatic test unit 214 receives a test command transmitted from the relay device 110, it executes an individual test. This individual test includes checking for dead batteries, sensor abnormalities, and radio wave abnormalities. After executing the individual test, the automatic test unit 214 transmits the test results to the relay device 110.

[0098] 2-1-2. Child device 109B In this embodiment, a child device 109B (not shown) is used instead of the child device 106B. The child device 109B differs from the child device 106B in that it further includes the automatic testing section 214 described above. In the following description, the master unit 109A and the slave unit 109B are collectively referred to as the "fire alarm unit 109."

[0099] 2-1-3. Relay device 110 In this embodiment, a relay device 110 (not shown) is used instead of the relay device 107. This relay device 110 differs from the relay device 107 in that it further includes a function called a test command unit 412 (not shown).

[0100] When the test command unit 412 receives a test instruction from the inspection management server 111, which will be described later, it transmits the test command to all of the fire alarm devices 109. In addition, when the test command unit 412 receives test results from all of the fire alarm devices 109 to which it sent the test command, it transmits a test completion notification to the inspection management server 111. The test completion notification transmitted here includes the test results received from each fire alarm device 109.

[0101] 2-1-4. Inspection management server 111 In this embodiment, an inspection management server 111 (not shown) is used instead of the inspection management server 102. This inspection management server 111 differs from the inspection management server 102 in that it includes an inspection monitoring unit 514 (not shown) instead of the inspection monitoring unit 512, and further includes an inspection recording unit 515 (not shown).

[0102] The inspection monitoring unit 514 monitors the inspection status of the fire alarm 109 of the registered user 104. If the inspection of the fire alarm 109 is not performed even after the recommended inspection time has passed, the inspection monitoring unit 514 transmits a signal to the fire alarm 109 to instruct it to perform a test.

[0103] Specifically, the signal is sent when the inspection prompt time arrives. The inspection prompt time when this signal is sent is updated to the next inspection prompt time once a test has been performed. Therefore, the inspection monitoring unit 514 does not send a test instruction for an inspection that has already been performed. In other words, the inspection monitoring unit 514 sends a test instruction only for inspections that have not yet been performed among those whose recommended inspection time has passed.

[0104] When a test is conducted on the fire alarm 109 of a registered user 104, the inspection recording unit 515 records the test. At that time, the inspection recording unit 515 receives a test completion notification transmitted from the relay device 110 and stores an inspection log in the auxiliary storage device 502. The inspection log stored here includes the inspection date of the fire alarm 109.

[0105] Furthermore, upon receiving the above-mentioned test completion notification, the inspection recording unit 515 updates the inspection prompt information stored in the auxiliary storage device 502. Specifically, the information updated here is the recommended inspection time and the inspection prompt time. Of these times, the recommended inspection time is determined according to the inspection date of the fire alarm 109, the type of the fire alarm 109 (specifically, the model name), and the type of inspection (in other words, the test type). On the other hand, the inspection prompt time is determined by adding a predetermined number of days (in this embodiment, as an example, 7 days) to the recommended inspection time.

[0106] 2-2.Operation In this embodiment, an inspection and monitoring process 1600 is executed instead of the inspection and monitoring process 1300. Also in this embodiment, an automatic test process 1700 is executed instead of the single test process 1400. The inspection and monitoring process 1600 and the automatic test process 1700 will be described below with reference to the drawings.

[0107] 2-2-1. Inspection and monitoring process 1600 The inspection monitoring process 1600 is a process for automatically performing an independent test and prompting the user 104 to perform an inspection in the case where the inspection of the fire alarm 109 has not been performed even after the inspection time has passed. This inspection monitoring process 1600 is periodically executed by the inspection management server 111. FIG. 16 shows an example of this inspection monitoring process 1600.

[0108] First, the inspection monitoring unit 514 of the inspection management server 111 refers to the inspection prompt time information 523 to search for inspections for which the inspection prompt time has arrived (step 1601). The inspections for which the inspection prompt time has arrived searched for here refer to inspections for which the execution date of this process is the inspection prompt time and inspections for which the execution date of this process is after the inspection prompt time.

[0109] If no inspection is extracted as a result of this search (NO in step 1602), this process ends. On the other hand, if an inspection is extracted as a result of this search (YES in step 1602), the inspection monitoring unit 514 executes step 1603.

[0110] In step 1603, the inspection monitoring unit 514 identifies the test type of the extracted inspection. Then, the inspection monitoring unit 514 judges whether the identified test type is a single test or not (step 1604). If the result of this judgment is that the identified test type is not a single test (NO in step 1604), the inspection monitoring unit 514 generates a message to prompt the user 104 to perform the extracted inspection (step 1605). The message generated here includes the user ID of the user 104, the type of inspection to be prompted (in other words, the test type), and a URL for reporting the inspection.

[0111] After creating the message, the inspection monitoring unit 514 refers to the user information 521 to identify the email address of the user 104. Then, the inspection monitoring unit 514 sends the created message to the identified email address (step 1606). After sending the message, the inspection monitoring unit 514 returns to step 1601 and searches for another inspection for which the inspection prompt time has arrived.

[0112] In the determination of step 1604 above, if the identified test type is a single test (YES in step 1604), the inspection monitor unit 514 transmits a test instruction to the relay device 110 of the user 104 (step 1607). The transmitted test instruction includes the user ID of the user 104. After sending the test instruction, the inspection monitoring unit 514 returns to step 1601 and searches for another inspection for which the inspection prompt time has arrived. The above is a description of the inspection monitoring process 1600.

[0113] 2-2-2.Automatic test processing 1700 The automatic test process 1700 is a process for automatically executing a single test. An example of the automatic test process 1700 is shown in FIG.

[0114] First, the inspection monitoring unit 514 of the inspection management server 111 transmits a test instruction to the relay device 110 (step 1701). The transmitted test instruction includes the user ID of the user 104. When the test command section 412 of the relay device 110 receives this test command, it transmits the test command to all the fire alarm devices 109 (step 1702).

[0115] When the automatic testing unit 214 of the fire alarm 109 receives this test command, it executes an individual test. Specifically, the automatic testing unit 214 first judges whether or not the battery is dead (step 1703). At that time, the automatic testing unit 214 judges whether or not the battery voltage value is below a predetermined operating voltage value. If the result of this judgment is that the battery voltage value is below the predetermined operating voltage value, the automatic testing unit 214 judges that the battery is dead.

[0116] Next, the automatic test unit 214 judges whether or not the sensor is in an abnormal state (step 1704). At that time, the automatic test unit 214 judges whether or not the output value of the fire detection unit 207 or 307 is within a predetermined normal range. If the result of this judgment is that the output value of the fire detection unit 207 or 307 is outside the predetermined normal range, the automatic test unit 214 judges that the sensor is in an abnormal state.

[0117] Next, the automatic testing unit 214 judges whether or not there is a radio wave abnormality (step 1705). At this time, the automatic testing unit 214 of the master unit 109A judges whether or not a test signal has not been received from any of the slave units 109B for a predetermined period or more. If the result of this judgment is that a test signal has not been received from any of the slave units 109B for a predetermined period or more, the automatic testing unit 214 judges that there is a radio wave abnormality. On the other hand, the automatic testing unit 214 of the child device 109B judges whether or not it has not received a test signal from the parent device 109A for a predetermined period of time or more. If the result of this judgment is that it has not received a test signal from the parent device 109A for a predetermined period of time or more, the automatic testing unit 214 judges that there is an abnormality in the radio waves.

[0118] Next, the automatic test unit 214 blinks the indicator light and outputs an alarm sound from the speaker according to the determination results of steps 1703 to 1705 (step 1706). Specifically, if the automatic test unit 214 is normal, it blinks the indicator light continuously and outputs a voice saying "Normal". If the battery is dead, it blinks the indicator light once and outputs a voice saying "Battery is dead". If the sensor is abnormal, it blinks the indicator light three times and outputs a voice saying "Abnormal". If the radio wave is abnormal, it blinks the indicator light twice and outputs a voice saying "Radio wave is abnormal".

[0119] Finally, the automatic test section 214 transmits the test result to the relay device 110 in accordance with the determination results of steps 1703 to 1705 (step 1707).

[0120] When the test command unit 412 of the relay device 110 receives the test results from all the fire alarm devices 109, it transmits a test completion notification to the inspection management server 111 (step 1708). The test completion notification transmitted here includes the test results received from each fire alarm device 109 and the user ID of the user 104.

[0121] When the inspection recorder 515 of the inspection management server 111 receives this test completion notification, it stores the inspection log in the auxiliary storage device 502 (step 1709). The stored inspection log is composed of the user ID included in the received test completion notification, the test type "single", and the inspection date. Here, the inspection date is the date on which the test completion notification was received. In addition, in this step, the inspection recording unit 515 may further store the test results included in the test completion notification in the auxiliary storage device 502 as an inspection log.

[0122] Next, upon receiving the above test completion notification, the inspection recording unit 515 updates the inspection prompt information stored in the auxiliary storage device 502 (step 1710). The inspection prompt information to be updated is the inspection prompt information corresponding to the user ID and the test type "single" included in the above test completion notification, in particular the recommended inspection time and the inspection prompt time.

[0123] When updating the recommended inspection timing, the inspection recording unit 515 refers to the recommended inspection frequency information 522. The inspection recording unit 515 refers to the recommended inspection frequency information 522 to identify the recommended inspection frequency that corresponds to the model name of the fire alarm 109 of the user 104. The inspection recording unit 515 then adds the identified recommended inspection frequency to the current recommended inspection timing to calculate the updated recommended inspection timing. The inspection recording unit 515 replaces the current recommended inspection timing with the calculated recommended inspection timing.

[0124] Next, when updating the inspection prompt time, the inspection record unit 515 calculates the inspection prompt time by adding a predetermined number of days (in this embodiment, as an example, 7 days) to the newly calculated recommended inspection time. The inspection record unit 515 replaces the current inspection prompt time with the calculated inspection prompt time. The above is a description of the automatic test process 1700.

[0125] According to the second embodiment described above, if an independent test of the fire alarm 109 has not been performed even after the inspection time has passed, the test is automatically performed. Therefore, according to this embodiment, the feasibility of regular inspection is improved.

[0126] 2. Variations The above embodiment may be modified as follows. The following modifications may be combined with each other. (1) In the above embodiment, the user terminal 103 is a smartphone. However, the user terminal 103 may be a terminal device other than a smartphone. For example, the user terminal 103 may be a smart watch, a tablet terminal, a stationary PC, or the like. Alternatively, the user terminal 103 may be a television that can be connected to the communication network 108.

[0127] (2) In the above user registration process 1200, the user 104 reads a two-dimensional code with the user terminal 103 to request a user registration screen from the inspection management server 102 (see steps 1201 to 1202). However, this method of request is merely one example. As another method, the user 104 may request the user registration screen by manually inputting a specific URL described in the instruction manual for the fire alarm 106 into the user terminal 103. As yet another method, the user 104 may request the user registration screen by searching for and selecting a specific URL on a search site.

[0128] (3) In the above user registration process 1200, inspection record process 1500, and automatic test process 1700, the inspection reminder time is determined based on the model name and test type of the fire alarm 106 or 109 (see steps 1208, 1508, 1710). When making this determination, the address of the user 104 may also be taken into consideration. For example, in areas where the inspection cycle should be set shorter, such as areas with an aging population, cold areas, and areas along the sea or mountains, the inspection reminder time may be set earlier than in other areas.

[0129] (4) In the above inspection record process 1500, an inspection report screen is displayed on the user terminal 103 (step 1504). On this inspection report screen, the user may be able to select whether the inspection is complete or not for each area in the house 105. The areas in the house 105 referred to here include, for example, the kitchen, living room, and stairs. Information on whether inspection is complete / not complete for each area selected on this inspection report screen may be transmitted to the inspection management server 102 together with the user ID and test type, and stored in the auxiliary storage device 502 as an inspection log.

[0130] (5) In the above inspection record process 1500, an inspection report screen is displayed on the user terminal 103 (step 1504). On this inspection report screen, the user may be able to select whether or not to be prompted for the next inspection. When it is selected on this inspection report screen that the user 104 does not need to be prompted for the next inspection, the inspection management server 102 may exclude the user 104 from the inspection monitoring process 1300.

[0131] (6) In the above inspection record process 1500, an inspection report screen is displayed on the user terminal 103 (step 1504). In this inspection report screen, the inspection results may be input. The inspection results here are information such as the presence or absence of an abnormality and the type of abnormality. The inspection results entered on this inspection report screen may be transmitted to the inspection management server 102 together with the user ID and test type, and stored in the auxiliary storage device 502 as an inspection log.

[0132] (7) In the above-described automatic test process 1700, an alarm sound is output from the fire alarm 109 after the individual test (step 1706). At that time, the automatic test unit 214 of the fire alarm 109 may output an alarm sound at a volume lower than the alarm sound output in the individual test process 1400. Alternatively, the automatic test unit 214 may omit outputting an alarm sound. This is because the automatic test process 1700 is an automatically performed process, and therefore there is a possibility that the user 104 may be surprised by outputting an alarm sound that takes the user 104 by surprise.

[0133] (8) The fire alarm 106 is powered by a battery (in other words, an internal power source). However, the fire alarm 106 may be powered by an external power source.

[0134] (9) The recommended inspection frequency constituting the recommended inspection frequency information 522 (see FIG. 5) may be set for each user 104. This allows the user 104 to set the recommended inspection timing for himself / herself. Alternatively, the user 104 may directly input the recommended inspection time.

[0135] (10) In the above-described inspection monitoring process 1300, when the inspection prompting time arrives, the user 104 is prompted to perform an inspection. Instead of such a prompting method, the user 104 may be prompted to perform an inspection when the inspection prompting time arrives and an inspection has not been performed for a period longer than the previous inspection period.

[0136] Here, when an inspection has not been performed for a period longer than the previous inspection cycle, this refers to a case where the period from the previous inspection date to the execution date of this process is longer than the period between the previous inspection date and the inspection date before last. For example, if the inspection date of the previous single test is July 9, 2021, and the inspection date of the single test before last is June 9, 2021, the previous inspection cycle is 30 days. If the period from the inspection date of the previous single test (July 9, 2021) to the execution date of this process is longer than this inspection cycle, the user 104 will be prompted to perform an inspection. Such a prompting method may be adopted.

[0137] (11) In the above-described inspection record processing 1500 and automatic test processing 1700, the recommended inspection frequency is added to the current recommended inspection time to calculate the updated recommended inspection time (see steps 1508 and 1710). In other words, the recommended inspection frequency is added to the current recommended inspection time. However, instead of the current recommended inspection time, the inspection date (in other words, the execution date of the inspection record processing 1500 or automatic test processing 1700) may be used as the target for adding the recommended inspection frequency. This allows inspections to be performed more faithfully to the recommended inspection frequency.

[0138] (12) In the above-described automatic test process 1700, upon receiving a test completion notification, the inspection prompt information is updated (see step 1710). This update of the inspection prompt information may be executed after notifying the user of the test completion. More specifically, the inspection recording unit 515 may transmit a test completion notification to the user terminal 103, and may update the inspection prompt information after receiving an acknowledgment response to this test completion notification from the user terminal 103.

[0139] (13) The relay device 107 according to the first embodiment may be provided with an inspection implementation notification function. This inspection implementation notification function is a function for notifying the inspection management server 102 of the implementation of an inspection. The relay device 107 provided with this function transmits an inspection implementation notification to the inspection management server 102 when a predetermined operation is performed by the user 104 who has completed an individual test or an interlocking test. At this time, the transmitted inspection implementation notification includes the user ID of the user 104 and the type of inspection (test type) that has been performed.

[0140] When the inspection management server 102 receives the inspection notification, the inspection recorder 513 stores the inspection log in the auxiliary storage device 502. The stored inspection log is composed of the user ID, test type, and inspection date included in the received inspection notification. Here, the inspection date is the date on which the inspection notification was received.

[0141] In addition, upon receiving the above-mentioned inspection execution notification, the inspection recording unit 513 updates the inspection prompt information stored in the auxiliary storage device 502. This update step is the same as step 1508 of the above-mentioned inspection recording process 1500.

[0142] After updating the inspection prompt information, the inspection recording unit 513 notifies the user terminal 103 of the next recommended inspection time. This makes it possible to make the user 104 aware of the next inspection.

[0143] (14) The relay device 110 according to the second embodiment may also be provided with an inspection execution notification function. The relay device 110 provided with this inspection execution notification function transmits an inspection execution notification to the inspection management server 111 when a predetermined operation is performed by the user 104 who has completed the individual test. At this time, the transmitted inspection execution notification includes the user ID of the user 104.

[0144] When the inspection recording unit 515 of the inspection management server 111 receives this inspection notification, it stores an inspection log in the auxiliary storage device 502. The stored inspection log is composed of the user ID included in the received inspection notification, the test type "single", and the inspection date. Here, the inspection date is the date on which the inspection notification was received.

[0145] In addition, upon receiving the above-mentioned notification of inspection execution, the inspection record unit 515 updates the inspection prompt information stored in the auxiliary storage device 502. This update step is the same as step 1710 of the automatic test process 1700 described above.

[0146] After updating the inspection prompt information, the inspection recording unit 515 notifies the user terminal 103 of the next recommended inspection time. This makes it possible to make the user 104 aware of the next inspection.

[0147] (15) In the above inspection monitoring process 1600, if the target test is a single test (YES in step 1604), a test instruction is sent to the relay device 110 of the user 104 (step 1607). In this step 1607, before sending the test instruction to the relay device 110, a test request may be received in advance from the user 104.

[0148] Specifically, before transmitting a test instruction, the inspection management server 111 transmits a screen prompting the user terminal 103 to perform an inspection. The transmitted screen includes a test request button.

[0149] When the user terminal 103 displays this screen and the user 104 selects the test request button, the user terminal 103 transmits a test request to the inspection management server 111. When the inspection management server 111 receives this test request, it transmits a test instruction to the relay device 110 of the user 104. In this manner, a test request may be received from user 104 prior to sending the test instruction.

[0150] (16) In the above inspection monitoring process 1300, if the user 104 does not perform an inspection even after being urged to do so, a notification may be sent to people related to the user. The people related to the user are, for example, family members or acquaintances of the user 104 who do not live with the user 104. The notification is, for example, a notification urging the user 104 to confirm his / her safety.

[0151] Specifically, the inspection monitoring unit 512 of the inspection management server 102 counts up the number of times the message has been sent after sending the message to the user 104 (step 1304). At that time, the inspection monitoring unit 512 records the count value for each set of the user ID, model name, test type, and inspection prompting time. Then, after extracting an inspection in step 1302, the inspection monitoring unit 512 judges whether the number of times the message has been sent for the extracted inspection is equal to or greater than a predetermined number. If the result of this judgment is that the number of times the message has been sent is less than the predetermined number, the inspection monitoring unit 512 executes steps 1303 and 1304. That is, the inspection monitoring unit 512 sends a message to the user 104. On the other hand, if the result of the above judgment is that the number of times the message has been sent is equal to or greater than the predetermined number, the inspection monitoring unit 512 generates a message addressed to a person related to the user 104. This message is a message that prompts the user 104 to confirm his / her safety. Then, the inspection monitoring unit 512 identifies the email address of the person related to the user 104. The email address specified here is assumed to be registered in advance as user information 521. Then, inspection monitoring unit 512 transmits the created message to the specified email address. After that, inspection monitoring unit 512 returns to step 1301.

[0152] In this way, if the user 104 does not perform any inspection, relevant parties may be urged to check on the user's safety.

[0153] (17) In the above inspection monitoring process 1600, if the target test is a single test (YES in step 1604), a test instruction is sent to the relay device 110 of the user 104 (step 1607). In this step 1607, before sending the test instruction to the relay device 110, the user 104 may be prompted to perform an inspection.

[0154] Specifically, the inspection management server 111 transmits a screen prompting the user to perform an inspection to the user terminal 103 before transmitting a test instruction. The transmitted screen includes the user ID of the user 104, the type of inspection to be prompted (in other words, the test type), and a URL for an inspection report. If the user 104 performs an independent test in response to this prompt and the above-mentioned inspection record process 1500 is performed, the inspection management server 111 stops transmitting the test instruction. On the other hand, if the user 104 does not perform an independent test even in response to this prompt and the inspection record process 1500 is not performed, the inspection management server 111 transmits a screen prompting the user to perform an inspection to the user terminal 103 at a certain period. The inspection management server 111 counts the number of times the screen is transmitted, and when the number of transmissions reaches a predetermined number or more, it transmits a test instruction to the relay device 110. At that time, the inspection management server 111 may transmit a message prompting a related person of the user 104 to confirm the safety of the user, as in the above-mentioned modified example (16).

[0155] In this way, the user 104 may first be prompted to perform the individual test, and if the user 104 still does not perform the individual test, the inspection management server 111 may automatically perform the individual test.

[0156] (18) Note that the present invention is not limited to the above-described embodiments, and various modifications are included. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0157] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0158] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. The above-described embodiments disclose at least the configurations described in the claims. [Explanation of symbols]

[0159] 101...fire alarm system, 102...inspection management server, 103...user terminal, 104...user, 105...house, 106...fire alarm, 106A...master unit, 106B...slave unit, 107...relay device, 108...communication network, 109...fire alarm, 109A...master unit, 109B...slave unit, 110...relay device, 111...inspection management server, 211...linked alarm unit, 212...recovery unit, 213...test unit, 214...auto dynamic testing section, 221...group ID, 311...linked alarm section, 312...recovery section, 313...testing section, 321...group ID, 411...reporting section, 412...test command section, 421...group ID, 511...user registration section, 512...inspection monitoring section, 513...inspection record section, 514...inspection monitoring section, 515...inspection record section, 521...user information, 522...recommended inspection frequency information, 523...inspection prompt time information, 524...inspection log

Claims

1. An inspection management device that has a transmission unit that, if a fire alarm inspection is not performed within the inspection period, sends a message to a terminal device of a user of the fire alarm urging the inspection, or sends a signal to the fire alarm to instruct it to perform a test.

2. The inspection management device according to claim 1 , further comprising a recording unit that records inspections or tests performed on the fire alarm.

3. The recording unit records the date of inspection or testing performed on the fire alarm, The inspection time is determined based on the recorded date.

3. The inspection management device according to claim 2 .

4. a user registration unit that receives a request transmitted by the user reading a predetermined code with the terminal device and transmits a user registration screen to the terminal device; The inspection time is determined based on the installation date of the fire alarm entered on the user registration screen.

2. The inspection management device according to claim 1 .

5. 2. The inspection management device according to claim 1, wherein the inspection time is determined according to a type of the fire alarm.

6. 2. The inspection management device according to claim 1, wherein the inspection timing is determined according to the type of the inspection or test.

7. A fire alarm installed in a fire prevention object; A relay device that is installed in the fire prevention object and transmits a fire detected by the fire alarm to an external device; an inspection management device that transmits a test instruction to the relay device when the inspection of the fire alarm is not performed even after the inspection time has passed; Equipped with A disaster prevention system characterized in that the relay device receives a test instruction transmitted from the inspection management device and commands the fire alarm to be tested.

Images