Disaster prevention information provision system and disaster prevention information provision method

The disaster prevention information system addresses inefficiencies by integrating multiple observation and communication systems into a unified dashboard, improving work efficiency through visual and auditory alerts.

JP7725278B2Active Publication Date: 2025-08-19KK TOSHIBA
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
JP2021121422
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-07-26
Publication Date
2025-08-19
Estimated Expiration
2041-07-26

AI Technical Summary

Technical Problem

Local governments and the Ministry of Land, Infrastructure, Transport and Tourism face inefficiencies in disaster prevention information management due to the use of separate systems by employees, leading to decreased work efficiency when less skilled staff operate these systems after frequent transfers.

Method used

A disaster prevention information system incorporating a database server and processing server that generates a dashboard screen with icons and tiles based on observation data, changes display formats and outputs alerts, and integrates with various observation and communication systems.

Benefits of technology

Improves business efficiency by providing a unified interface for disaster prevention information, reducing the need for multiple system operations and enhancing staff proficiency through visual and auditory alerts.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007725278000001
    Figure 0007725278000001
  • Figure 0007725278000002
    Figure 0007725278000002
  • Figure 0007725278000003
    Figure 0007725278000003
Patent Text Reader

Abstract

To provide a disaster information provision system and a disaster information provision method contributing to the improvement of business efficiency.SOLUTION: A disaster information provision system includes a database server and a processing server. The database server stores a database including positions of a plurality of observatories on a map, a plurality of observation results corresponding to the observatories, a plurality of tiles corresponding to the observation results so as to display the observation results, and a plurality of thresholds corresponding to the observation results. The processing server generates a dashboard screen including icons corresponding to the observatories and the tiles on the map on the basis of the database, displays the dashboard screen, determines the necessity of an alert output on each one of the observation results on the basis of the thresholds corresponding to the observation results, and controls to change tile display on the dashboard screen into a display form based on the determination result and display the same.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] FIELD An embodiment of the present invention relates to a disaster prevention information providing system and a disaster prevention information providing method. [Background technology]

[0002] Disaster prevention management in Japan is shared between local governments and the Ministry of Land, Infrastructure, Transport and Tourism. Local governments are responsible for collecting local disaster prevention information and sharing it with local residents. The Ministry of Land, Infrastructure, Transport and Tourism has a hierarchical management system with a headquarters that oversees the entire country, several general secretariats under its control, and management offices under those.

[0003] Although the management mechanisms differ, each has a disaster prevention information system that provides various types of disaster prevention information. For example, the disaster prevention information system is configured to have a screen for each type of disaster prevention information, and each screen displays various types of disaster prevention information obtained via the Web.

[0004] The staff member in charge inputs operations to display the disaster prevention information they want to check into the operation unit corresponding to each screen of the disaster prevention information provision system, and each screen of the disaster prevention information provision system displays the disaster prevention information based on the operation input. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 6612523 [Patent Document 2] Japanese Patent Application Laid-Open No. 2016-115059 [Patent Document 3] Japanese Patent Application Laid-Open No. 2016-128960 [Patent Document 4] Japanese Patent Application Laid-Open No. 2003-247238 [Patent Document 5] Japanese Patent Application Laid-Open No. 2015-49199 [Patent Document 6] Japanese Patent Publication No. 2020-16463 [Patent Document 7] Japanese Patent Application Laid-Open No. 2006-234654 [Patent Document 8] Japanese Patent Application Publication No. 2018-194968 Summary of the Invention [Problem to be solved by the invention]

[0006] In addition to the disaster prevention information system mentioned above, local governments and the Ministry of Land, Infrastructure, Transport and Tourism have introduced separate systems for use in various operations and for various resident services. Employees use many different systems to obtain disaster prevention information and report it to relevant departments. Therefore, employees must be familiar with how to use each operation and many different systems. However, in workplaces where employees are transferred to different departments relatively frequently, there are many instances where less skilled employees operate the disaster prevention information system, raising concerns about a decline in work efficiency.

[0007] An object of the present invention is to provide a disaster prevention information providing system and a disaster prevention information providing method that contribute to improving business efficiency. [Means for solving the problem]

[0008] A disaster prevention information provision system according to an embodiment includes a database server and a processing server. The database server stores a database including locations of multiple observation stations on a map, multiple observation results corresponding to the multiple observation stations, multiple tiles corresponding to the multiple observation results and for displaying the multiple observation results, and multiple thresholds corresponding to the multiple observation results. The processing server generates a dashboard screen including icons corresponding to the multiple observation stations and the multiple tiles on the map based on the database, displays the dashboard screen, determines whether an alert needs to be issued for each of the multiple observation results based on the thresholds corresponding to the multiple observation results, and controls the tile display on the dashboard screen to change to a display format based on the determination result. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of connections between systems constituting a disaster prevention system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a schematic configuration of a disaster prevention information providing system according to the first embodiment. [Figure 3] FIG. 3 is a schematic diagram showing each function of the processing server according to the first embodiment. [Figure 4] FIG. 4 is a table diagram illustrating an example of tile information in the database of the DB server according to the first embodiment. [Figure 5] FIG. 5 is a table diagram showing an example of dashboard behavior and operation information in the database of the DB server according to the first embodiment. [Figure 6] FIG. 6 is a table diagram illustrating an example of current timeline information of the DB server according to the first embodiment. [Figure 7] FIG. 7 is a table diagram illustrating an example of timeline operation information in the DB server according to the first embodiment. [Figure 8] FIG. 8 is a table diagram showing an example of observation station information (water level) in the DB server according to the first embodiment. [Figure 9] FIG. 9 is a table diagram showing an example of observation information (water level) of the DB server according to the first embodiment. [Figure 10] FIG. 10 is a table diagram showing an example of observation station information (cameras) in the DB server according to the first embodiment. [Figure 11] FIG. 11 is a table diagram showing an example of camera information (still images) in the DB server according to the first embodiment. [Figure 12] FIG. 12 is a table diagram showing an example of timeline table action item information and timeline table user information of the DB server according to the first embodiment. [Figure 13] FIG. 13 is a table diagram showing an example of current status timeline table action item information and current status timeline table user information of the DB server according to the first embodiment. [Figure 14]FIG. 14 is a table diagram illustrating an example of evacuation shelter information in the DB server according to the first embodiment. [Figure 15] FIG. 15 is a table diagram showing an example of evacuation shelter status operation information in the DB server according to the first embodiment. [Figure 16] FIG. 16 is a table diagram illustrating an example of status report operation information of the DB server according to the first embodiment. [Figure 17] FIG. 17 is a table diagram illustrating an example of user information in the DB server according to the first embodiment. [Figure 18] FIG. 18 is a table diagram showing an example of a dashboard screen displayed by the processing server according to the first embodiment. [Figure 19] FIG. 19 is a flowchart showing an example of processing for changing the tile display color on the dashboard screen by the processing server according to the first embodiment. [Figure 20] FIG. 20 is a diagram showing an example of a condition for changing the display color of a tile on a dashboard screen by the processing server according to the first embodiment. [Figure 21] FIG. 21 is a flowchart showing an example of processing for changing the tile display color and alert sound on the dashboard screen by the processing server according to the first embodiment. [Figure 22] FIG. 22 is a diagram showing an example of conditions for changing the tile display color on the dashboard screen and the alert sound by the processing server according to the first embodiment. [Figure 23] FIG. 23 is a diagram showing an example of screen transitions accompanying one-operation processing via a dashboard screen displayed by the processing server according to the first embodiment. [Figure 24] FIG. 24 is a diagram showing an example of screen transition accompanying one-operation processing via action items displayed by the processing server according to the first embodiment. [Figure 25] FIG. 25 is a flowchart showing an example of screen transitions accompanying one-operation processing via a dashboard screen displayed by the processing server according to the first embodiment. [Figure 26]FIG. 26 is a diagram for explaining external collaboration (another system closed within a local government) by the disaster prevention information provision system according to the second embodiment. [Figure 27] FIG. 27 is a diagram showing the relationship between the input system and the output system in the disaster prevention information provision system according to the second embodiment. [Figure 28] FIG. 28 is a schematic diagram showing each function of a processing server of a disaster prevention information provision system according to the second embodiment. [Figure 29] FIG. 29 is a table diagram showing an example of other system information in the database of the DB server according to the second embodiment. [Figure 30] FIG. 30 is a table diagram showing an example of other system linkage information in the database of the DB server according to the second embodiment. [Figure 31] FIG. 31 is a diagram showing an example of screen transitions related to linkage with other systems accompanying one-operation processing via a dashboard screen displayed by a processing server according to the second embodiment. [Figure 32] FIG. 32 is a diagram showing an example of screen transitions related to linkage with a plurality of other systems in one-operation processing via a dashboard screen displayed by a processing server according to the second embodiment. [Figure 33] FIG. 33 is a flowchart showing an example of a process of linking with a plurality of other systems by a processing server according to the second embodiment. [Figure 34] FIG. 34 is a diagram illustrating a disaster prevention information providing system according to the third embodiment. [Figure 35] FIG. 35 is a diagram showing the relationship between an input system and an output system in a disaster prevention information provision system according to the third embodiment. [Figure 36] FIG. 36 is a schematic diagram showing each function of a processing server of a disaster prevention information provision system according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] The following describes the dashboard screen display and one-operation of the disaster prevention information provision system of this embodiment. The disaster prevention information provision system 1 can be applied as a system for local governments (e.g., cities, towns, and villages), and can also be applied to river offices under the jurisdiction of the Ministry of Land, Infrastructure, Transport and Tourism or prefectures. First Embodiment In the first embodiment, a dashboard screen display and one-operation system for a disaster prevention information providing system of a local government will be described. [Configuration of the first embodiment] FIG. 1 is a diagram showing an example of connections between systems constituting a disaster prevention system according to the first embodiment. As shown in Fig. 1, the disaster prevention system of a local government is centered around a disaster prevention information providing system 1, and is equipped with a camera monitoring system 22, a water level observation system 23, and a rainfall observation system 24 (hereinafter, the camera monitoring system 22, water level observation system 23, and rainfall observation system 24 will be collectively referred to as an observation station) for collecting information within the local government. Furthermore, the disaster prevention system of a local government is equipped with a disaster prevention administrative radio system 21, a social networking service (SNS) system 26, and an emergency alert email system 27 for disseminating information to local residents.

[0011] The disaster prevention information providing system 1 is connected to a disaster prevention administrative radio system 21, a camera monitoring system 22, a water level observation system 23, and a rainfall observation system 24 via an intranet 31. Furthermore, the disaster prevention information providing system 1 is connected to an SNS system 26 and an emergency alert email system 27 via the intranet 31, a firewall 25, and the Internet 32.

[0012] The camera monitoring system 22 takes images of the monitoring area (rivers and their surrounding areas) and transmits the taken images to the disaster prevention information providing system 1. The water level observation system 23 observes the water level of the monitoring area (rivers and their surrounding areas) and transmits the observation results to the disaster prevention information providing system 1. The rainfall observation system 24 observes the rainfall in the monitoring area (rivers and their surrounding areas) and transmits the observation results to the disaster prevention information providing system 1.

[0013] The disaster prevention administrative radio system 21 is a system that can also transmit the disaster prevention information output from the disaster prevention information providing system 1 to residents of the local government.

[0014] The SNS system 26 is an SNS system provided by companies that operate SNSs, and transmits information output from the disaster prevention information providing system 1 to SNS users.

[0015] The emergency alert mail system 27 transmits information output from the disaster prevention information providing system 1 to email addresses registered for the emergency alert mail.

[0016] FIG. 2 is a diagram illustrating an example of a schematic configuration of a disaster prevention information providing system according to the first embodiment. As shown in FIG. 2, the disaster prevention information providing system 1 includes a processing server 11, a DB (database) server 12 including a DB (database) 121, a terminal (PC) 13, and a Web server .

[0017] The processing server 11, DB server 12, and terminal 13 are connected via an intranet 16. The web server 14 is connected to the intranet 16 via a firewall 15. The processing server 11, DB server 12, terminal 13, and web server 14 are also connected to a terminal (smartphone) 281 and a terminal (tablet) 282 via the firewall 15 and the Internet 32.

[0018] The processing server 11 is configured with a general-purpose computer or the like, and includes a processor P1, a memory M1, a storage S1, an input / output interface IF1, and a display D1. The processor P1 corresponds to the central part of the computer that performs various calculations and control processes related to the provision of disaster prevention information by the processing server 11. The processor P1 executes control to realize various functions based on programs such as system software, application software, and firmware stored in the memory M1 or the like. The processor P1 is, for example, a CPU (central processing unit).

[0019] The memory M1 includes a nonvolatile memory and a volatile memory, and the nonvolatile memory stores programs executed by the processor P1. The nonvolatile memory also stores data or various setting values used by the processor P1 when performing various processes. The storage S1 stores various information related to disaster prevention information.

[0020] The input / output interface IF1 communicates with other devices, inputs information from other devices, and outputs information to other devices. The input / output interface IF1 also inputs signals from a mouse and a keyboard.

[0021] The display D1 displays a dashboard screen, an action item list, an enlarged title, etc. The display of the dashboard screen, the action item list, the enlarged title, etc. will be described in detail later.

[0022] The database 121 stored in the DB server 12 includes a map, the positions of multiple river water level observation stations and rainfall observation stations on the map, multiple observation results corresponding to the multiple river water level observation stations and rainfall observation stations, multiple tiles corresponding to the multiple observation results and for displaying these multiple observation results, multiple thresholds corresponding to the multiple observation results, multiple action items corresponding to the multiple river water level observation stations and rainfall observation stations and multiple staff members, and linkage information (including a linkage method) to external systems corresponding to specific tiles. Examples of data stored in the database 121 will be described later.

[0023] FIG. 3 is a schematic diagram showing each function of the processing server according to the first embodiment. The processor P1 of the processing server 11 realizes each function by executing the programs stored in the memory M1. The processor P1 of the processing server 11 has a basic function 111, a common function 112, a screen providing function for PCs 114, a screen providing function for smartphones 115, and a screen providing function for tablets 116.

[0024] The basic functions 111 include a system management function 1111 , a timeline editing function 1112 , a GIS providing function 1113 , and a data accumulation function 1114 . The system management function 1111 is a function for managing the entire system. The timeline editing function 1112 is a function for editing the timeline in accordance with edit inputs for the timeline. The data accumulation function 1114 is a function for managing the accumulation of various data provided from outside.

[0025] The common function 112 includes a dashboard processing function 1121 , a timeline processing function 1122 , an observation information processing function 1123 , a camera information processing function 1124 , an evacuation shelter information processing function 1125 , a situation report function 1126 , and a related information processing function 1127 .

[0026] The dashboard processing function 1121 is a functional unit that generates a dashboard screen and transitions between dashboard screens.

[0027] The timeline processing function 1122 is a functional unit that manages the timeline corresponding to the action item.

[0028] The observation information processing function 1123 is a functional unit that generates tiles based on observation information such as water level, rainfall, etc. Tiles will be explained in detail later.

[0029] The camera information processing function 1124 is a functional unit that analyzes image data sent from the camera monitoring system 22 and outputs disaster prevention information based on the analysis results.

[0030] The evacuation shelter information processing function 1125 is a functional unit that analyzes evacuation shelter information provided from an external system and outputs disaster prevention information based on the analysis results.

[0031] The status reporting function 1126 outputs various status reports. The related information processing function 1127 is a functional unit that processes various related information and outputs the processing results.

[0032] The PC screen providing function 114 is a functional unit that includes a PC screen generating function 1141 .

[0033] The smartphone screen providing function 115 is a functional unit that includes a smartphone screen generating function 1151 .

[0034] The tablet-oriented screen providing function 116 is a functional unit that includes a tablet-oriented screen generating function 1161 . Each of these functions will be explained in detail later.

[0035] [Database of the first embodiment] Returning to FIG. 2, each piece of data stored in the database 121 of the DB server 12 will now be described.

[0036] Fig. 4 is a table diagram showing an example of tile information in the database of the DB server according to the first embodiment. As shown in Fig. 4, the database 121 stores an observation station ID, a current status timeline table action item ID 1-1 (association with an action item), a condition 1-1 (exceeding threshold A, etc.), a current status timeline table action item ID 1-2, and a condition 1-2 (exceeding threshold B, etc.) in association with a tile ID (Identification).

[0037] Fig. 5 is a table diagram showing an example of dashboard action / operation information in the database of the DB server according to the first embodiment. As shown in Fig. 5, the database 121 stores the date and time, user ID, tile ID, trigger ID, and action / operation in association with the dashboard action / operation information ID.

[0038] Fig. 6 is a table diagram showing an example of current status timeline information of the DB server according to the embodiment 1. As shown in Fig. 6, the database 121 stores a name, supplementary information, a timeline table table ID, a current status timeline table table ID, and a stage type in association with a current status timeline ID.

[0039] Fig. 7 is a table diagram showing an example of timeline operation information in the DB server according to the first embodiment. As shown in Fig. 7, the database 121 stores the date and time, the user ID, and the operation item in association with the timeline operation information ID.

[0040] 8 is a table diagram showing an example of observation station information (water level) of the DB server according to the first embodiment. As shown in Fig. 8, the database 121 stores the name, location, threshold A, threshold B, and threshold C in association with the observation station information ID.

[0041] 9 is a table diagram showing an example of observation information (water level) of the DB server according to the first embodiment. As shown in Fig. 9, the database 121 stores the date and time, observation station ID, water level, and threshold excess in association with the observation information ID.

[0042] Fig. 10 is a table diagram showing an example of observation station information (camera) in the DB server according to the first embodiment. As shown in Fig. 10, the database 121 stores the name and location in association with the observation station information ID.

[0043] 11 is a table diagram showing an example of camera information (still images) in the DB server according to the first embodiment. As shown in Fig. 11, the database 121 stores the date and time, the observation station ID, and the image ID in association with the camera information ID.

[0044] FIG. 12 is a table diagram showing an example of timeline table action item information and timeline table user information of the DB server according to the first embodiment. 12, the database 121 stores timeline action item information to which a timeline table ID (AAAAA) is assigned. For example, the database 121 stores timeline action item information including a timeline action item ID, a sequence, a stage type, action items 1 to N, and users 1 to N.

[0045] The database 121 also stores timeline table user information to which a timeline table user table ID (AAAAA01) is assigned. For example, the database 121 stores timeline table user information including a user ID.

[0046] The DB server 12 is a server that manages the timeline table table ID (AAAAA) and the timeline table user table ID (AAAAA01) as a set of tables. The DB server 12 manages a plurality of such sets of tables.

[0047] The flags shown in Fig. 12 are values that specify whether each user is in charge of an action item. For example, a flag "1" indicates a user who acts independently, and a double circle is displayed on the screen corresponding to the flag "1". A flag "2" indicates a user who supports a user who acts independently, and a circle "〇" is displayed on the screen corresponding to the flag "2". A flag "0" indicates a user who is not in charge, and a blank space is displayed on the screen corresponding to the flag "0".

[0048] FIG. 13 is a table diagram showing an example of current status timeline table action item information and current status timeline table user information of the DB server according to the first embodiment. 13, the database 121 stores current timeline table action item information to which a current timeline table table ID (aaaaa) is assigned. For example, the database 121 stores timeline table action item information including a current timeline table action item ID, a sequence, a stage type, action items 1 to N, and users 1 to N.

[0049] Furthermore, the database 121 stores current status timeline table user information to which a current status timeline table user table ID (aaaaa01) is assigned. For example, the database 121 stores current status timeline table user information including a user ID. The DB server 12 manages the current status timeline table table ID (aaaaa) and the current status timeline table user table ID (aaaaa01) as a set of tables. The DB server 12 manages multiple sets of such tables.

[0050] The flags shown in FIG. 13 are values that specify whether each user is in charge of an action item, and values that indicate whether the action has been completed. Flags "1," "2," and "0" are the same as the flags in FIG. 12. Flag "10" indicates that the user with flag "1" has completed the corresponding action. This status is displayed on the screen by processing such as changing the display color in response to flag "10." Also, flag "20" indicates that the user with flag "2" has completed the corresponding action. This status is displayed on the screen by processing such as changing the display color in response to flag "20."

[0051] Fig. 14 is a table diagram showing an example of shelter information in the DB server according to the embodiment 1. As shown in Fig. 14, the database 121 stores the name and location of the shelter in association with the shelter ID.

[0052] Fig. 15 is a table diagram showing an example of shelter status operation information of the DB server according to the embodiment 1. As shown in Fig. 15, the database 121 stores the date and time, user ID, shelter ID, open / close status, opening date and time, closing date and time, and number of evacuees in association with the shelter status operation information ID.

[0053] Fig. 16 is a table diagram showing an example of status report operation information of the DB server according to the embodiment 1. As shown in Fig. 16, the database 121 stores date and time, user ID, text, image ID, and latitude and longitude in association with a status report operation information ID.

[0054] Fig. 17 is a table diagram showing an example of user information of the DB server according to the first embodiment. As shown in Fig. 17, the database 121 stores a name, a login ID, a password, and an authority type (administrator, view only, editable, etc.) in association with a user ID.

[0055] [Operation of the first embodiment (screen display and screen transition)] The processing server 11 generates and displays a dashboard screen based on the data stored in the database 121 using the dashboard processing function 1121 . FIG. 18 is a table diagram showing an example of a dashboard screen displayed by the processing server according to the first embodiment.

[0056] As shown in FIG. 18 , the dashboard screen includes a map, which further includes tiled observation results from each observation station. For example, the map includes multiple icons corresponding to multiple river water level observation stations and rainfall observation stations, and further includes tiles showing observation results from river water level observation stations, tiles showing observation results from rainfall observation stations, and tiles showing other observation results (images from surveillance cameras). The tiles showing the observation results are arranged around the map so as to surround it. The tiles include graph displays showing observation information such as rainfall or water level.

[0057] The tile information table shown in Figure 4 contains multiple settings for each tile, including which observatory is assigned to each tile (observatory ID), which timeline action item is assigned to each tile (current timeline table action item ID), and the activation conditions (e.g., exceeding threshold A).

[0058] The tile display color on the dashboard screen changes in response to the occurrence of an alert, and this process will be explained below. FIG. 19 is a flowchart showing an example of processing for changing the tile display color on the dashboard screen by the processing server according to the first embodiment. FIG. 20 is a diagram showing an example of a condition for changing the display color of tiles on the dashboard screen by the processing server according to the first embodiment.

[0059] The processing server 11 generates a dashboard screen including icons corresponding to multiple river water level observation stations and rainfall observation stations and multiple tiles on a map based on the data stored in the database 121 using the dashboard processing function 1121, etc., and displays the dashboard screen. The processing server 11 also changes the display color of the tiles on the dashboard screen based on the data and observation results stored in the database 121 using the dashboard processing function 1121, etc. That is, the processing server 11 determines whether or not an alert needs to be output for each of the multiple observation results based on the multiple observation results and multiple thresholds corresponding to the multiple observation results, and controls the alert output for each of the multiple observation results based on the determination result.

[0060] For example, as shown in Fig. 19, in S1-1, the processing server 11, using the dashboard processing function 1121 or the like, determines whether the observation value of the observation station ID (00000001) satisfies a first condition that the observation value exceeds threshold A (1.30) and is equal to or less than threshold B (1.50), based on a table stored in the database 121 (for example, the table shown in Fig. 8 and Fig. 9). If the first condition is satisfied, the process transitions to S2-1. If the first condition is not satisfied, the process transitions to S1-2.

[0061] In S2-1, the processing server 11 changes the tile color from the standard color (white) to color A (yellow) by the dashboard processing function 1121 or the like (see FIG. 20). The standard color is a non-alert display format, and color A is an alert display format.

[0062] In S1-2, the processing server 11, using the dashboard processing function 1121 or the like, determines whether the observation value of the observation station ID (00000001) satisfies a second condition that the observation value exceeds threshold B (1.50) and is equal to or less than threshold C (1.70), based on the table stored in the database 121. If the second condition is satisfied, the process transitions to S2-2. If the second condition is not satisfied, the process transitions to S1-3.

[0063] In S2-2, the processing server 11 changes the tile color from color A (yellow) to color B (red) by the dashboard processing function 1121 or the like (see FIG. 20). Color B is an alert display format.

[0064] In S1-3, the processing server 11, using the dashboard processing function 1121 or the like, determines whether or not the observation value of the observation station ID (00000001) satisfies a third condition that exceeds the threshold C (1.70), based on the table stored in the database 121. If the third condition is satisfied, the process transitions to S2-3. If the third condition is not satisfied, the process transitions to S3.

[0065] In S2-3, the processing server 11 changes the tile color from color B (red) to color C (purple) by the dashboard processing function 1121 or the like (see FIG. 20).

[0066] In S3, if the processing server 11 has not finished checking all tiles using the dashboard processing function 1121 or the like, it repeats the above processing, and when all tiles have been checked, it ends the color change processing.

[0067] The dashboard screen of the processing server 11 displays the risk levels of multiple tiled observation results in different colors, allowing personnel in charge to instantly distinguish between multiple observation results and those with a high risk level.

[0068] In the above process, the tile display color is simply changed according to the observed risk level, but an alert sound may also be emitted when the tile color is changed. An example of processing in which an alert sound is issued in conjunction with a change in the tile display color will be described below.

[0069] FIG. 21 is a flowchart showing an example of processing for changing the tile display color and alert sound on the dashboard screen by the processing server according to the first embodiment.

[0070] FIG. 22 is a diagram showing an example of conditions for changing the tile display color and alert sound on the dashboard screen by the processing server according to the first embodiment.

[0071] The processing server 11 uses the dashboard processing function 1121 and the like to change the display color of tiles on the dashboard screen based on the data stored in the database 121, and outputs an alert sound. In S1-1, the processing server 11, using the dashboard processing function 1121 or the like, determines whether the observation value of the observation station ID (00000001) satisfies a first condition that the observation value exceeds threshold A (1.30) and is equal to or less than threshold B (1.50), based on a table stored in the database 121 (for example, the table shown in FIGS. 8 and 9). If the first condition is satisfied, the process transitions to S2-1 and S3-1. If the first condition is not satisfied, the process transitions to S1-2.

[0072] In S2-1, the processing server 11 changes the tile color from the standard color (white) to color A (yellow) by the dashboard processing function 1121 or the like (see FIG. 22). In S3-1, the processing server 11 causes the dashboard processing function 1121 or the like to output an alert sound A (repeated beeps) (see FIG. 22).

[0073] In S1-2, the processing server 11, using the dashboard processing function 1121 or the like, determines whether the observation value of the observation station ID (00000001) satisfies a second condition that the observation value exceeds threshold B (1.50) and is equal to or less than threshold C (1.70), based on the table stored in the database 121. If the second condition is satisfied, the process transitions to S2-2 and S3-2. If the second condition is not satisfied, the process transitions to S1-3.

[0074] In S2-2, the processing server 11 changes the tile color from color A (yellow) to color B (red) by the dashboard processing function 1121 or the like (see FIG. 22). In S3-2, the processing server 11 causes the dashboard processing function 1121 or the like to output an alert sound B (repeated beeps) (see FIG. 22).

[0075] In S1-3, the processing server 11, using the dashboard processing function 1121 or the like, determines whether or not the observation value of the observation station ID (00000001) exceeds the threshold C (1.70), which is a third condition, based on the table stored in the database 121. If the third condition is met, the process transitions to S2-3 and S3-3. If the third condition is not met, the process transitions to S3.

[0076] In S2-3, the processing server 11 changes the tile color from color B (red) to color C (purple) by the dashboard processing function 1121 or the like (see FIG. 22).

[0077] In S3-3, the processing server 11 causes the dashboard processing function 1121 or the like to output an alert sound C (repeated beeps) (see FIG. 22).

[0078] In S3, if the processing server 11 has not finished checking all tiles using the dashboard processing function 1121 or the like, it repeats the above processing, and when all tiles have been checked, it ends the color change processing.

[0079] According to the dashboard screen of the processing server 11, the risk level of multiple tiled observation results is displayed in different colors, and the risk level is also distinguished by the alert sound, so that the person in charge can instantly distinguish the high-risk observation results from the multiple observation results by sight and ear.

[0080] [Operation of the first embodiment] Next, operations performed in response to tiles displayed on the dashboard will be described. FIG. 23 is a diagram showing an example of screen transitions accompanying one-operation processing via a dashboard screen displayed by the processing server according to the first embodiment.

[0081] The processing server 11 displays a dashboard screen (a) using the dashboard processing function 1121, etc. The dashboard screen includes multiple tiles showing the observation results of each observation station. When a responsible staff member selects a specific tile using a mouse or the like of the input / output interface IF1, the processing server 11 switches the dashboard screen (a) to a timeline table (b) or an enlarged tile (c) through cooperation between the dashboard processing function 1121, the timeline processing function 1122, the related information processing function 1127, etc. (hereinafter, each function). The timeline table includes an action item list including specific action items corresponding to the specific tile.

[0082] When the selected tile is associated with an action item based on the tables (for example, the tables shown in FIGS. 4 and 5) stored in the database 121, the processing server 11, through cooperation of each function, displays the timeline table (b) centered on the action item associated with the selected tile. Furthermore, the processing server 11, using the timeline processing function 1122 etc., displays the timeline table (b) based on the tables stored in the database 121, in which the relevant action items are colored A (first display format) and the non-relevant action items are colored B (second display format).

[0083] In addition, through cooperation of each function, the processing server 11 displays an enlarged tile (c) corresponding to the selected tile in the center of the screen based on the table stored in the database 121 if the selected tile is not associated with an action item.

[0084] FIG. 24 is a diagram showing an example of screen transition accompanying one-operation processing via action items displayed by the processing server according to the first embodiment. When the timeline table (b) is displayed and the responsible staff member selects a specific action item using a mouse or the like on the input / output interface IF1, the processing server 11 switches the timeline table (b) to a detailed operation explanation screen (d) through cooperation of the dashboard processing function 1121, timeline processing function 1122, related information processing function 1127, etc. (hereinafter referred to as each function).

[0085] The processing server 11, through cooperation of each function, displays a detailed operation explanation screen (d) including an action summary, a manual, and an action summary of each user associated with the selected action item based on a table stored in the database 121 (for example, the table shown in FIG. 13).

[0086] FIG. 25 is a flowchart showing an example of screen transitions accompanying one-operation processing via a dashboard screen displayed by the processing server according to the first embodiment.

[0087] The processing server 11 displays a dashboard screen using the dashboard processing function 1121, etc. Furthermore, the processing server 11 uses the dashboard processing function 1121, etc. to display an alert on the tile of the dashboard screen based on the data stored in the database 121, and outputs an alert sound.

[0088] In S1, the processing server 11 determines whether a predetermined tile has been selected via the mouse or the like of the input / output interface IF1 by the system management function 1111 or the like. If a predetermined title has been selected, the process proceeds to S2, and if not, the process ends.

[0089] In S2, the processing server 11, through cooperation of the dashboard processing function 1121, the timeline processing function 1122, the related information processing function 1127, etc. (hereinafter referred to as each function), determines whether or not the selected tile is associated with an action item based on tables (for example, the tables shown in FIGS. 4 and 5) stored in the database 121. If there is an association, the process transitions to S3, and if there is no association, the process transitions to S2-1.

[0090] In S2-1, the processing server 11, through cooperation of each function, displays an enlarged tile corresponding to the selected tile in the center of the screen based on the table stored in the database 121.

[0091] In S3, the processing server 11, through cooperation of each function, displays a timeline table centered on the action item associated with the selected tile. Furthermore, through cooperation of each function, the processing server 11 displays a timeline table in which the color of the corresponding action item is changed based on the table stored in the database 121.

[0092] As described above, the disaster prevention information system 1 displays a dashboard screen in which observation results from multiple observation stations of multiple types are tiled, and the dashboard screen can be transitioned with a single operation by the responsible staff member. Furthermore, the disaster prevention information system 1 outputs an alert sound according to the observation results, and also changes the alert sound. The disaster prevention information system 1 can reduce the number of times the responsible staff member has to operate an electronic device (single operation), thereby improving work efficiency.

[0093] <Second embodiment> In the second embodiment, cooperation between a disaster prevention information providing system and an external system will be described. Note that Figures 1 to 25 show common parts with the first embodiment, and explanations of the common parts will be omitted as appropriate, and differences from the first embodiment will be mainly described.

[0094] First, we will explain the integration of other systems in local governments (e.g., cities, towns, and villages) (integration of other systems closed to the local government). In local government disaster prevention responses, the local government's timeline (advance disaster prevention action plan) is formulated and operated on the disaster prevention information system, and the disaster prevention information system plays a part in the local government's disaster prevention response. The absolute number of local government employees is decreasing due to the recent effects of a declining birthrate and aging population. In particular, the current situation is that many local governments have few employees in charge of disaster prevention work, with only one or two people.

[0095] In this situation where the number of response staff is extremely limited, local governments will establish emergency systems when there is a risk of a disaster occurring due to an approaching typhoon, etc. Meanwhile, while a limited number of staff continue to work overnight, and while also handling other duties, staff must constantly pay attention to rising river water levels and rainfall conditions that are important for disaster prevention.

[0096] Furthermore, depending on the situation, disaster prevention information and evacuation instructions will be sent using the disaster prevention administrative radio system, email, SMS, etc., which can lead to inefficient operations such as operating multiple systems and inputting and transmitting the same information into different systems.

[0097] On the other hand, disaster prevention staff are often transferred every three years or so, which means they tend to become less familiar with each system and it is difficult to accumulate operational know-how.Once a typhoon occurs and is predicted to approach, an emergency system is put in place, but it is expected that an extremely complicated situation will arise in which multiple systems will have to be operated.

[0098] In such a situation, the disaster prevention information provision system shown in the second embodiment can use the dashboard screen as a trigger to encourage the responsible staff to take disaster prevention action, and also reduces the number of linking operations to other systems (one operation), supports the operations of less skilled staff, prevents omissions, and improves work efficiency.

[0099] [Configuration of the second embodiment] FIG. 26 is a diagram for explaining external collaboration (another system closed within a local government) by the disaster prevention information provision system according to the second embodiment. 26, the disaster prevention system includes an L Alert system 2. The L Alert system 2 is configured with multiple general-purpose computers. The disaster prevention information providing system 1 is connected to the L Alert system 2 via an intranet 31, a firewall 25, and the Internet 32.

[0100] FIG. 27 is a diagram showing the relationship between the input system and the output system in the disaster prevention information provision system according to the second embodiment. 27, the disaster prevention system includes, as input systems, a camera monitoring system 22, a water level observation system 23, and a rainfall observation system 24. The disaster prevention system also includes, as output systems, an L-alert system 2, a disaster prevention administrative radio system 21, an SNS system 26, and an emergency alert email system 27.

[0101] FIG. 28 is a schematic diagram showing each function of a processing server of a disaster prevention information provision system according to the second embodiment. The processor P1 of the processing server 11 realizes each function by executing the programs stored in the memory M1. The processor P1 of the processing server 11 has a function 113A for linking with other systems within the local government, a function 114 for providing screens for PCs, a function 115 for providing screens for smartphones, a function 116 for providing screens for tablets, and a related department and other system linking function unit 117A.

[0102] The linking function section 113A with other systems within the local government is equipped with a telemetry system linking function 1131, a camera system linking function 1132, a disaster prevention radio linking function 1133, a homepage linking function 1134, an SNS linking function 1135, and an emergency alert email linking function 1136, and realizes linking with other systems within the local government.

[0103] The related department and other system linking function part 117A has a FRICS (River Information Center, Foundation of River & Basin Integrated Communications JAPAN) linking function 1171, a J-Alert (nationwide instantaneous warning system) linking function 1172, an L-Alert linking function 1173, and a prefecture system linking function 1174, and realizes linking with related department and other systems.

[0104] The FRICS linking function 1171 is a function that connects to the server of the River Information Center, transmits information to the connected server, receives information from the connected server, and links with the server of the River Information Center.

[0105] The J-Alert linkage function 1172 is a function that connects to the server of the nationwide instantaneous warning system, transmits information to the connected server, receives information from the connected server, and links with the server of the nationwide instantaneous warning system.

[0106] The L Alert linkage function 1173 is a function that connects to the server of the local disaster information sharing system, sends information to the connected server, receives information from the connected server, and links with the server of the local disaster information sharing system.

[0107] The prefecture system linking function 1174 is a function that connects to a server of the prefecture system, transmits information to the connected server, receives information from the connected server, and links with the server of the prefecture system.

[0108] The PC screen providing function 114 includes a PC screen generating function 1141. The smartphone screen providing function 115 includes a smartphone screen generating function 1151. The tablet screen providing function 116 includes a tablet screen generating function 1161.

[0109] The PC screen generation function 1141 generates a disaster prevention information screen for a user who accesses the disaster prevention information system using a PC.

[0110] The smartphone screen generation function 1151 generates a disaster prevention information screen for a user who accesses the disaster prevention information system using a smartphone.

[0111] The tablet screen generation function 1161 generates a disaster prevention information screen for a user who accesses the disaster prevention information system using a tablet.

[0112] [Database of the second embodiment] Here, a supplementary explanation will be given regarding FIG. 4 explained in the first embodiment. As shown in Figure 4, database 121 stores, in association with a tile ID (Identification), other system ID (association with other systems) 2-1, condition 2-1 (exceeding threshold D, etc.), action 2-1 (launching an application, etc.), other system ID 2-2, condition 2-2 (exceeding threshold X, etc.), and action 2-2 (API (Application Programming Interface) data transfer, etc.).

[0113] Fig. 29 is a table diagram showing an example of other system information in the database of the DB server according to the embodiment 2. As shown in Fig. 29, the database 121 stores the name (Disaster Prevention Unrelated, L Alert, etc.), URL, and supplementary information in association with the other system ID.

[0114] FIG. 30 is a table diagram illustrating an example of other system linkage information in the database of the DB server according to the second embodiment.

[0115] 30, the database 121 stores the date and time, the user ID, and the link content in association with the other system link information ID. The link content includes the link method, and the link method is, for example, application startup or API data transfer.

[0116] The processing server 11 cooperates with other systems based on the information on the operations 2-1, 2-2, and 2-N described in the tile information of FIG.

[0117] The processing server 11 cooperates with other systems such as disaster prevention radio and L alert, based on the information on the operation 2-1, operation 2-2, and operation 2-N described in the tile information of FIG.

[0118] [Operation of the second embodiment (screen display and screen transition)] FIG. 31 is a diagram showing an example of screen transitions related to linkage with other systems accompanying one-operation processing via a dashboard screen displayed by a processing server according to the second embodiment. The processing server 11 displays a dashboard screen (a) using the dashboard processing function 1121, etc. The dashboard screen includes multiple tiles showing the observation results of each observation station. When a responsible employee selects a specific tile using a mouse or the like of the input / output interface IF1, the dashboard processing function 1121 and the related department other system linkage function 117, etc. (hereinafter referred to as each function) work together to switch the dashboard screen (a) to a dialog screen (b) for permission to transfer data to other systems or an enlarged tile (c).

[0119] If the selected tile is associated with another system based on a table stored in the database 121 (for example, information on operations 2-1, 2-2, and 2-N described in the tile information table shown in FIG. 4), the processing server 11, through cooperation of each function, displays a dialog screen (b) for permission to transfer data to the other system associated with the selected tile. When permission to transfer data to the other system (OK) is selected via the dialog screen (b), the processing server 11, through cooperation of each function, cooperates with the other system and transfers data to the other system. For example, the processing server, through each function, transfers data using an API provided by the L-Alert system.

[0120] Furthermore, through cooperation of each function, the processing server 11 displays an enlarged tile (c) corresponding to the selected tile in the center of the screen based on the table stored in the database 121 if the selected tile is not associated with another system.

[0121] FIG. 32 is a diagram showing an example of screen transitions related to linkage with a plurality of other systems in one-operation processing via a dashboard screen displayed by a processing server according to the second embodiment. The processing server 11 displays a dashboard screen (a) by using the dashboard processing function 1121, the related department other system collaboration function 117, etc. (hereinafter referred to as each function), etc. If the selected tile is associated with multiple other systems based on the table stored in the database 121 (for example, information on operation 2-1, operation 2-2, and operation 2-N described in the tile information table shown in FIG. 4), the processing server 11 displays a dialog screen (b) for permitting data transfer to multiple other systems associated with the selected tile.

[0122] For example, if the multiple other systems associated with the selected tile include an L-Alert system, an emergency alert email system, and an SNS system, the dialog screen (b) for permission to transfer data to the multiple other systems will include items for the L-Alert system, the emergency alert email system, and the SNS system. Furthermore, we assume a case where API data transfer is associated with the L-Alert system and application launch is associated with the emergency alert email system based on the information in Operation 2-1, Operation 2-2, and Operation 2-N described in the tile information in Figure 4.

[0123] When an employee selects the Emergency Mail Breaking System item via a mouse or the like of input / output interface IF1, processing server 11, through cooperation of each function, starts the Emergency Mail Breaking System application and displays the Emergency Mail Breaking System screen (d). When an employee selects the L Alert System item via a mouse or the like of input / output interface IF1, processing server 11, through cooperation of each function, transfers data using the API provided by the L Alert System.

[0124] FIG. 33 is a flowchart showing an example of a process of linking with a plurality of other systems by a processing server according to the second embodiment.

[0125] The processing server 11 uses the dashboard processing function 1121 or the like to display a dashboard screen including multiple tiles based on the data stored in the database 121. The processing server 11 also displays an alert for a specific tile that satisfies the alert determination conditions, and also outputs an alert sound.

[0126] In S1, the processing server 11 determines whether or not an alert tile that is the target of an alert display or an alert sound has been selected. If an alert tile has not been selected, the processing ends. If an alert tile has been selected, the processing transitions to S2.

[0127] In S2, the processing server 11 determines whether or not there is another system associated with the tile of the selected alert using the function 113 for linking with other systems within the local government. If there is no other system associated with the tile of the selected alert, the processing transitions to S2-1, and if there is another system associated with the tile of the selected alert, the processing transitions to S3.

[0128] In S2-1, if there is no other system associated with the tile of the selected alert, the processing server 11 displays an enlarged tile corresponding to the tile of the selected alert in the center of the screen.

[0129] In S3, the processing server 11 determines whether or not there are multiple other systems associated with the tile of the selected alert using the function 113 for linking with other systems within the local government. If there are multiple other systems associated with the tile of the selected alert, the process proceeds to S3-1; if there are not multiple other systems, the process proceeds to S4.

[0130] In S3-1, the processing server 11 displays a dialog screen for permission to transfer data to multiple other systems associated with the selected tile. For example, if the multiple other systems associated with the selected tile include an L alert system, an emergency alert email system, and an SNS system, the dialog screen (b) for permission to transfer data to the multiple other systems includes items for the L alert system, the emergency alert email system, and the SNS system.

[0131] In S4, if the processing server 11 determines that the selected other system is associated with API data transfer, the processing transitions to S4-1, and if the selected other system is associated with application launch, the processing transitions to S4-2.

[0132] In S4-1, the processing server 11 transfers data via an API associated with the selected other system.

[0133] At S4-2, the processing server 11 launches the application associated with the selected other system. <Third embodiment> Next, we will explain the case where the disaster prevention information provision system is applied to a river administrator (a river office of the Regional Development Bureau of the Ministry of Land, Infrastructure, Transport and Tourism, or a prefectural office; hereinafter collectively referred to as "river administrator").

[0134] In the third embodiment, a disaster prevention information provision management system will be described when applied to a river administrator.

[0135] River management is divided into national, prefectural, and municipal jurisdictions depending on the river's classification. These river managers formulate and operate timelines for the entire river basin for the rivers they manage, and disaster prevention information systems play a part in the river managers' disaster prevention response. Many organizations participate in river management, including not only local governments in the river basin, but also meteorological stations, prefectural civil engineering offices, fire departments, telecommunications companies, public transportation companies, electric utilities, voluntary disaster prevention organizations, and NPOs, making information sharing between participating organizations extremely complicated. In this case, multiple timelines may be formulated and operated depending on the grouping of management and operation.

[0136] Furthermore, municipalities, prefectures, river offices, etc. may operate multiple systems, which can lead to inefficient operations such as inputting and transmitting the same information into different systems. In addition, disaster prevention staff are often transferred every three years or so, which means they tend to become less familiar with each system and it is difficult to accumulate operational know-how.Once a typhoon occurs and is predicted to approach the river basin, an emergency system is established for the entire river basin, but it is expected that an extremely complicated situation will arise in which multiple systems will have to be operated.

[0137] In such a situation, the disaster prevention information provision system shown in the third embodiment can use the dashboard screen as a trigger to encourage the responsible staff to take disaster prevention action, and also reduces the number of linking operations to other systems (one operation), supports the operations of less skilled staff, prevents omissions, and improves work efficiency.

[0138] [Configuration of the third embodiment] FIG. 34 is a diagram illustrating a disaster prevention information providing system according to the third embodiment. As shown in Figure 34, when applied to a river administrator, the disaster prevention information provision system is centered around the disaster prevention information provision system 1, and is equipped with a camera monitoring system 22, a water level observation system 23, and a rainfall observation system 24 (hereinafter, the camera monitoring system 22, water level observation system 23, and rainfall observation system 24 will be collectively referred to as an observation station) for collecting information within the local government.

[0139] Furthermore, when applied to a river administrator, the disaster prevention information provision system includes an SNS system 26 for providing information. The disaster prevention information provision system 1 is connected to the SNS system 26 via an intranet 31, a firewall 25, and the Internet 32.

[0140] FIG. 35 is a diagram showing the relationship between an input system and an output system in a disaster prevention information provision system according to the third embodiment. 35, the disaster prevention system includes, as input systems, a camera monitoring system 22, a water level observation system 23, and a rainfall observation system 24. The disaster prevention system also includes, as output systems, an SNS system 26, an emergency alert email system 27, and a flood forecasting and warning system 28.

[0141] FIG. 36 is a schematic diagram showing each function of a processing server of a disaster prevention information provision system according to the third embodiment. The processor P1 of the processing server 11 realizes each function by executing the programs stored in the memory M1. The processor P1 of the processing server 11 has a function 113B for linking with other systems in the river office, a function 114 for providing screens for PCs, a function 115 for providing screens for smartphones, a function 116 for providing screens for tablets, and a function 117B for linking with other systems in related departments.

[0142] The linkage function 113B with other systems within the river office includes a telemetry system linkage function 1131, a camera system linkage function 1132, a homepage linkage function 1134, an SNS linkage function 1135, and an emergency alert email linkage function 1136, and realizes linkage with other systems within the river office.

[0143] The related department and other system linking function 117B has an FRICS linking function 1171 and a flood forecasting and warning linking function 1175, and realizes linking with related department and other systems.

[0144] The processing server 11 links to other systems such as an SNS system based on the other system information and other system link information stored in the database 121. The screen display and screen transitions for linking are as already explained, and detailed explanations will be omitted.

[0145] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0146] 1. Disaster prevention information system 2...L Alert System 11...Processing server 12...Database server 13...Terminal (PC) 14...Web server 15...Firewall 16...Intranet 21...Disaster Prevention Administrative Radio System 22...Camera surveillance system 23...Water level observation system 24...Rainfall observation system 25...Firewall 26...SNS system 27...Emergency alert email system 28...Flood Forecasting and Warning System 31...Intranet 32...Internet

Claims

1. a database server that stores a database including positions of a plurality of observation stations on a map, a plurality of observation results corresponding to the plurality of observation stations, a plurality of tiles corresponding to the plurality of observation results and for displaying the plurality of observation results, and a plurality of thresholds corresponding to the plurality of observation results; generating a dashboard screen including icons corresponding to the plurality of observation stations on a map and the plurality of tiles arranged around the map based on the database, and displaying the dashboard screen; determining whether or not an alert needs to be output for each of the plurality of observation results based on thresholds corresponding to the plurality of observation results; a processing server that controls the tile display on the dashboard screen to change the display format based on the determination result; and A disaster prevention information provision system equipped with:

2. The plurality of observation stations stored in the database are water level observation stations that observe the water level of a river and rainfall observation stations that observe rainfall, and the plurality of observation results are observed water level information and rainfall information. The disaster prevention information providing system according to claim 1.

3. the database server stores a plurality of action items corresponding to the plurality of observation stations and the plurality of personnel; the processing server, in response to a selection of a predetermined tile included in the plurality of tiles based on the database, switches the display of the dashboard screen to a display of an action item list including a predetermined action item corresponding to the predetermined tile; The disaster prevention information providing system according to claim 1.

4. the display of the action item list includes the predetermined action item and other action items other than the predetermined action item; the predetermined action item is in a first display format, and the other action items are in a second display format; The disaster prevention information providing system according to claim 3.

5. the database server stores the database including link information to an external system corresponding to a predetermined tile; the processing server cooperates with the external system in response to a selection of a predetermined tile included in the plurality of tiles based on the cooperation information; 5. The disaster prevention information providing system according to claim 1.

6. the database server stores the database including link information to an external system corresponding to a predetermined tile; the link information includes first link information to a first external system corresponding to a first tile and second link information to a second external system corresponding to a second tile; the processing server cooperates with the first external system by the first cooperation information in response to the selection of the first tile, and cooperates with the second external system by the second cooperation information in response to the selection of the second tile; The disaster prevention information providing system according to claim 5.

7. the first link information is activation of a predetermined application, the second link information is data transfer via an API, The disaster prevention information provision system of claim 6, wherein the processing server launches the specified application using the first linkage information in response to selection of the first tile, and transfers data regarding the second tile to the second external system using the API using the second linkage information in response to selection of the second tile.

8. the database server stores a database including the plurality of action items based on a timeline under the jurisdiction of a local government; The disaster prevention information provision system of claim 3, wherein the processing server switches the display of the dashboard screen to a display of an action item list based on the timeline in response to the selection of a predetermined tile included in the plurality of tiles based on the database.

9. the database server stores a database including the plurality of action items based on a timeline of a river basin under the jurisdiction of a river office; The disaster prevention information provision system of claim 3, wherein the processing server switches the display of the dashboard screen to a display of an action item list based on the timeline in response to the selection of a predetermined tile included in the plurality of tiles based on the database.

10. generating a dashboard screen including icons corresponding to the plurality of observation stations on a map and the plurality of tiles arranged around the map based on a database including positions of a plurality of observation stations on a map, a plurality of observation results corresponding to the plurality of observation stations, a plurality of tiles corresponding to the plurality of observation results and for displaying the plurality of observation results, and a plurality of thresholds corresponding to the plurality of observation results, and displaying the dashboard screen; determining whether or not an alert needs to be output for each of the plurality of observation results based on thresholds corresponding to the plurality of observation results; A disaster prevention information providing method that controls the tile display on the dashboard screen to change to a display format based on the determination result.

Citation Information

Patent Citations

  • Information gathering system

    JP2003006381A

  • Sediment disaster risk management system

    JP2003247238A

  • System for providing river information

    JP2006234654A

  • Emergency report distribution system, repeating device, radio communication terminal, and emergency report distribution method

    JP2012147062A

  • Presentation data accumulation system, display device, presentation data providing method, and program

    JP2015049199A