Risk data management device and risk data management method

Abstract

To visualize an accident occurrence risk of an infrastructure facility based on operation factors and work factors, in addition to environmental factors and asset factors.SOLUTION: A risk data management device comprises: a model management unit that creates a risk model which associates environment information of an infrastructure facility, operation information of the infrastructure facility, and work information with respect to the infrastructure facility, with asset information indicating characteristics of the infrastructure facility itself; and a display processing unit that displays the created risk model.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a risk data management device and a risk data management method. [Background technology]

[0002] Electric power companies have large-scale infrastructure facilities such as power transmission facilities. To ensure a stable supply of electricity, electric power companies must maintain their infrastructure facilities in a stable state at all times. Much of this infrastructure is installed outdoors and is directly affected by the natural environment. It is difficult to completely avoid infrastructure accidents caused by changes in the natural environment. However, it is important for electric power companies to predict changes in the natural environment as much as possible and minimize infrastructure accidents. Recently, it has become common for computers to predict the causes of infrastructure accidents.

[0003] The accident cause prediction device of Patent Document 1 uses a combination of locations where power transmission and distribution line accidents have occurred in the past, weather conditions at those locations, and accident causes as learning data to machine-learn a model.The device then inputs any location and weather conditions into the machine-learned model.The machine-learned model then predicts the cause of the accident.

[0004] The information processing device in Patent Document 2 determines the relational expression between the span between transmission towers where an accident has occurred in the past and the relative torsional rigidity. The relative torsional rigidity is the ratio between the span between transmission towers where an accident has occurred in the past and the adjacent span multiplied by a correction value determined according to the wire size (diameter). Then, based on the determined relational expression, the device outputs the risk of snow damage accidents occurring for each span between transmission towers. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2021-68070 [Patent Document 2] International Publication No. 2014 / 006708 Summary of the Invention [Problem to be solved by the invention]

[0006] Accidents involving infrastructure facilities such as power transmission facilities are often influenced by environmental (weather) factors and asset factors such as the physical configuration of the infrastructure. However, other human factors, such as operational factors and work (maintenance) factors, can also play a role. For example, in an accident in which salt in snow adheres to insulators, causing insulation breakdown, the timing of the insulation breakdown is influenced by work factors such as applying water-repellent paint to the insulators or replacing the insulators with a shape that is less susceptible to snow accumulation, as well as operational factors such as operating at a lower voltage.

[0007] However, Patent Document 1 focuses only on environmental factors and ignores driving and work factors, while Patent Document 2 focuses only on asset factors and ignores driving and work factors. Therefore, an object of the present invention is to visualize the risk of accidents occurring in infrastructure facilities based on operational factors and work factors in addition to environmental factors and asset factors. [Means for solving the problem]

[0008] The risk data management device of the present invention comprises: Directly affected by the natural environment Environmental information of infrastructure facilities, operation information of the infrastructure facilities, and work information on the infrastructure facilities The node that indicates , asset information indicating the characteristics of the infrastructure equipment itself; Node showing to via link Association and associating a node showing risk data relating to threats of natural disasters that may cause breakdowns in the infrastructure facilities, the level of the threats, and countermeasures against the threats with the node showing the asset information via a link. a model management unit that creates a risk model based on the risk information; and a display processing unit that displays the created risk model. When the model management unit extracts a portion of the risk model in response to a search request from a user, the display processing unit displays the extracted risk model; when the model management unit creates an asset lifecycle model by chronologically arranging operation information or work information associated with specific asset information included in the risk model, the display processing unit displays the created asset lifecycle model; the display processing unit displays that in the asset lifecycle model, a plurality of infrastructure facilities are continuous assets that are continuously connected, and displays a similar environment area identified by the model management unit from a plurality of surrounding areas located around a designated area in which an asset designated by a user is located, the similar environment area having environmental information closest to the environmental information of the designated area; It is characterized by: Other means will be described in the detailed description of the invention. [Effects of the Invention]

[0009] According to the present invention, the risk of an accident occurring in infrastructure facilities can be visualized based on operational factors and work factors in addition to environmental factors and asset factors. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 2 is a diagram illustrating the configuration of a risk data management device. [Figure 2] FIG. 2 is a functional block diagram of a risk data management device. [Figure 3] FIG. 1 illustrates an example of a data management model. [Figure 4] FIG. 10 is a diagram illustrating an example of a risk model. [Figure 5] FIG. 10 is a diagram illustrating risk data. [Figure 6] FIG. 2 is a diagram illustrating a metrics node. [Figure 7] FIG. 10 is a diagram illustrating an accident response report. [Figure 8] FIG. 1 illustrates an example of an asset lifecycle model. [Figure 9] FIG. 1 illustrates a portion of an asset lifecycle model. [Figure 10] 10 is a flowchart of a processing procedure. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention (referred to as the "present embodiment") will be described in detail with reference to the drawings and the like. In this embodiment, an electric power company manages infrastructure facilities such as power transmission facilities. However, the present invention is generally applicable to facilities that are exposed to the natural environment and operated and maintained by humans. In this embodiment, "property" is synonymous with "infrastructure facilities" and their components. "Property" is also called "asset."

[0012] (term) Infrastructure facilities are large-scale public facilities that form the foundation of human social life and are directly affected by the natural environment. Environmental information is information that indicates the characteristics of the natural environment surrounding infrastructure facilities, such as temperature, humidity, wind speed, wind direction, amount of precipitation, amount of snowfall, etc. Asset information is information that indicates the type and physical characteristics of each piece of infrastructure equipment itself. For example, if the type of infrastructure equipment is a "power transmission line," physical characteristics include the diameter of the power transmission line, the material of the power transmission line, the distance between power transmission lines, the distance between steel towers, etc.

[0013] Work information is information that indicates human intervention in infrastructure facilities at the site, such as the content of work on infrastructure facilities, the timing of work, etc. In many cases, the work is maintenance to maintain the original functionality of the infrastructure facilities. The operating information is the operating conditions such as voltage set by humans for the infrastructure facilities. Risk data is information about threats that could cause infrastructure failures, often natural disasters.

[0014] A model is a group of data having a specific structure, and specifically, is a tree diagram having nodes and links indicating causal relationships, or a relational database. The model base data is data that electric power companies use to create various models, including environmental information, operational information, asset information, work information, and area information indicating the location of infrastructure facilities. In other words, the model base data is data before association is made.

[0015] Generally, electric power companies use the individual pieces of information contained in the model basic data in a model by interrelating them with one another. The specific method of association varies depending on the management objectives for the infrastructure facilities. The management objectives for infrastructure facilities are not limited to investigating and predicting the causes of failures. For example, in accordance with the management objective of checking the layout status of infrastructure facilities by area, area information is used as the primary key (the central item for association) and other information is associated with the area information. In the case where the management objective is to investigate and predict the causes of failures, asset information is used as the primary key and other information is associated with the asset information. Furthermore, risk data is associated with asset information.

[0016] (Model Classification) A data management model is one of the above models in which basic model data is associated in a specific way according to a specific management purpose. The data management model may also be a relational database or a tree diagram as in this embodiment. A risk model is a data management model in which asset information is used as the primary key and environmental, operational, and work information is associated with the asset information, or in which risk data is further associated with the asset information. Such a risk model visualizes the natural or man-made causes of failure indicated by the environmental, operational, and work information for each piece of infrastructure equipment, and further visualizes more specific threats (natural disasters) and their severity indicated by the risk data. An asset life cycle model is a risk model that shows the life cycle of a specific asset in an easy-to-understand manner for users. A life cycle is information that shows the history of installation, operation, work, etc. of a specific asset in chronological order.

[0017] (Configuration of risk data management device) FIG. 1 is a diagram showing the configuration of a risk data management device 1. The risk data management device 1 is a general-purpose computer, and includes a central control device 11, input devices 12 such as a mouse and keyboard, output devices 13 such as a display, a main memory device 14, an auxiliary memory device 15, and a network interface 16. These are interconnected by a bus 18. The auxiliary memory device 15 stores a program 17 (described in detail below). The central control device 11 reads the program 17 from the auxiliary memory device 15 into the main memory device 14, thereby realizing the functions of each program (described in detail below).

[0018] (Function block of risk data management device) 2 is a functional block diagram of the risk data management device 1. Model basic data 20 exists outside the risk data management device 1. The model basic data 20 includes environmental information 21, operation information 22, asset information 23, and work information 24.

[0019] The risk data management device 1 has an environmental information registration unit 101, an operation information registration unit 102, an asset information registration unit 103, a work information registration unit 104, a model management unit 105, a change detection unit 106, and a display processing unit 107. These are programs 17 in FIG. 1.

[0020] The risk data management device 1 has an environmental information storage unit 111, an operation information storage unit 112, an asset information storage unit 113, and a work information storage unit 114. These are partial areas of the auxiliary storage device 15 in Fig. 1. The risk data management device 1 has a model storage unit 115. The model storage unit 115 is also a partial area of ​​the auxiliary storage device 15 in Fig. 1. The model storage unit 115 stores the data management model, risk model, and asset lifecycle model.

[0021] The environmental information registration unit 101 acquires the environmental information 21 via the input device 12 or the network interface 16 in FIG. The driving information registration unit 102 acquires the driving information 22 via the input device 12 or the network interface 16 in FIG. The asset information registration unit 103 acquires asset information 23 via the input device 12 or the network interface 16 in FIG. The work information registration unit 104 acquires the work information 24 via the input device 12 or the network interface 16 in FIG.

[0022] The model management unit 105 acquires environmental information 21, driving information 22, asset information 23, and work information 24 from the environmental information storage unit 111, driving information storage unit 112, asset information storage unit 113, and work information storage unit 114, respectively. Then, the model management unit 105 uses these to create a data management model and stores it in the model storage unit 115.

[0023] In addition, the model management unit 105 extracts (extracts a part of) the necessary parts from the data management model in response to user operations, creates a risk model, and stores it in the model storage unit 115. Furthermore, the model management unit 105 extracts (extracts a part of) the necessary parts from the risk model, or rearranges the information of the risk model in chronological order to create an asset lifecycle model, and stores it in the model storage unit 115.

[0024] The change detection unit 106 detects changed parts of the environmental information 21, driving information 22, asset information 23, and work information 24 from the environmental information storage unit 111, driving information storage unit 112, asset information storage unit 113, and work information storage unit 114, respectively. The change here refers to, for example, the creation of new information (such as countermeasures against threats) and adding it to a risk model. The change detection unit 106 outputs the detected parts to the display processing unit 107.

[0025] The display processing unit 107 outputs the information received from the model management unit 105 and the change detection unit 106 to the external terminal device 2 or the output device 13 (FIG. 1).

[0026] (Data Management Model) FIG. 3 is a diagram showing an example of a data management model 31. The data management model 31 is composed of a plurality of nodes and links between the nodes. Each node is the basic model data described above, and belongs to one of the environmental information 21, operation information 22, asset information 23, work information 24, and area information 29. Note that FIG. 2 omits the area information 29 (described in detail below).

[0027] In the environmental information 21, for example, a weather information node 211 indicating "temperature" is associated by links with a daily data (daily value) node 2111 and an hourly data (hourly value) node 2112. The daily data nodes 2111 are arranged in date order, and the hourly data nodes 2112 are arranged in date and time order. The weather information node 211 is associated by a link with a space ID node 291d in the area information 29.

[0028] In the operation information 22, for example, an operation voltage information node 221 indicating "operating voltage" is arranged in chronological order. information The node 221 is associated with the device information node 231 of the asset information 23 by a link.

[0029] In the asset information 23, a device information node 231 indicating a specific infrastructure facility such as a "power transmission line" is linked to a space ID node 291d in the area information 29. A part information node 232 indicating a specific part that makes up the infrastructure facility, such as an "insulator," is linked to the device information node 231.

[0030] In the work information 24, a maintenance information node 241 indicating a specific maintenance such as "insulator inspection" is linked to a part information node 232 in the asset information 23. A plurality of maintenance information nodes 241 are stored in chronological order. A repair information node 242 indicating a specific repair such as "insulator replacement" is linked to a part information node 232 in the asset information 23. A plurality of repair information nodes 242 are stored in chronological order.

[0031] In the area information 29, space ID nodes 291a, 291b, 291c, and 291d are serially linked. Each of the space ID nodes 291a, etc. has a space ID, which is an identifier that uniquely identifies the space in which infrastructure facilities are located. The links between space ID nodes may be formed by dividing the geographical space into a grid of sections based on latitude and longitude, assigning an integer value as a space ID to each section, and indicating the connection between the sections in the order of the space IDs. Furthermore, the links may indicate the linear connection of infrastructure facilities such as power lines (continuous assets, as described below), or may indicate hierarchical administrative addresses such as prefectures, cities, and towns.

[0032] As described above, the method of associating each node of the data management model 31 (connection of links) can be changed depending on the management purpose.

[0033] (Risk Model) 4 is a diagram showing an example of a data management model 31. The model management unit 105 of the risk data management device 1 can also create another data management model 31 by reconnecting the links between nodes of an existing data management model 31. This other data management model is the risk model 41. Note that hereinafter, "associating by a link" will be simply expressed as "associating."

[0034] The weather information node 211 is directly associated with the device information node 231. Values ​​(e.g., temperature) for each date and time are associated with the weather information node 211. Incidentally, in the data management model 31 (FIG. 3), the weather information node 211 is indirectly associated with the device information node 231 via the space ID node 291d.

[0035] The operating voltage information node 221 is directly associated with the device information node 231. The operating voltage information node 221 is associated with a value for each date and time.

[0036] The maintenance information node 241 is directly associated with the device information node 231. A specific maintenance history is associated with the maintenance information node 241 in chronological order. In the data management model 31 (FIG. 3), the maintenance information node 241 is associated with the part information node 231. node 232 is indirectly associated with the device information node 231. Instead of or in addition to the maintenance information node 241, a repair information node 242 stores device information. node 231.

[0037] The area information 29 in FIG. 4 is an area map showing the actual topography. A position on the area map is directly associated with a device information node 231. As is clear from FIG. 4, the risk model 41 is configured with the device information node 231 included in the asset information as the center (primary key). Furthermore, the device information node 231 is associated with risk data related to the asset. Due to space limitations, the risk data will be explained in FIG. 5.

[0038] (Risk Data) FIG. 5 is a diagram illustrating risk data 51. The asset node 230, which is the root node of the tree diagram in FIG. 5, is the same as the device information node 231 in FIG. 4. The asset node 230 indicates an individual asset that makes up an infrastructure facility. Associated with the asset node 230 are an importance node 2301 and multiple threat type nodes 2303a, 2303b, .... In FIG. 5, all nodes other than the asset node 230 are the risk data described above.

[0039] The importance node 2301 is a value indicating the importance of an asset. The importance may be, for example, the priority for restoring an asset when multiple assets including that asset fail simultaneously, the time required for restoration, the cost required for restoration, etc. The importance node 2301 is associated with an impact node 2302. The impact node 2302 is a value indicating the impact that the asset has on the entire infrastructure facility. The impact is, for example, the number of households that will suffer a power outage if the asset breaks down.

[0040] The threat type nodes 2303a and the like indicate the type of threat. A threat is a natural disaster that can cause an asset to fail, and the type can be, for example, "strong wind," "heavy snow," "tree contact," "lightning," and the like.

[0041] A risk level node 2304 is associated with the threat type node 2303a, etc. When multiple threat type nodes 2303a, etc. are associated with the asset node 230, the risk level node 2304 indicates the risk level, which is the relative degree of threat that a threat poses to the asset. For example, if the risks posed to a power line as an asset are greatest in the order of tree contact > lightning > heavy snow > strong wind, the risk level of the threat type "tree contact" is "4" and the risk level of the threat type "strong wind" is "1." The risk level may be the product of the threat level and vulnerability level, which will be described later.

[0042] The risk level node 2304 is associated with a threat level node 2305 and a vulnerability level node 2306 . The threat level node 2305 indicates the probability of a threat occurring as a natural phenomenon. The threat level may be a normalized number in several stages, such as 1, 2, or 3. The vulnerability level node 2306 indicates the conditional probability that an asset will be affected if a threat as a natural phenomenon actually occurs. The vulnerability level may be a normalized number in several stages, such as 1, 2, or 3.

[0043] A countermeasure node 2307a is associated with the threat level node 2305. The countermeasure node 2307a indicates a countermeasure for lowering the threat level. A countermeasure node 2307b is associated with the vulnerability level node 2306. The countermeasure node 2307b indicates a countermeasure for lowering the vulnerability level. Examples of countermeasures include "water-repellent coating" for the threat type "heavy snow" and "strengthening of power line tension" for the threat type "strong wind."

[0044] A metrics node 2308 is associated with the threat type node 2303a etc. The metrics node 2308 indicates items (described in detail below) that are measured in order to predict the occurrence of a threat.

[0045] (metrics node) FIG. 6 is a diagram illustrating the metrics node 2308. Many detection devices (sensors, cameras, etc.) are installed in or around infrastructure facilities to detect threats such as strong winds, heavy snowfall, tree strikes, and lightning. The detection devices are connected to a device that manages model basic data 20 (especially environmental information 21) via a wireless or wired network. Measurement items A, B, C, etc. represent the types of measurements (current, voltage, wind speed, snowfall, weight on power lines, images of the surrounding area, images of power lines, etc.) detected by each detection device. Of these, for each threat indicated in the threat type node 2303a, the items measured to detect the occurrence of that threat are defined in the metrics node 2308. In the example of FIG. 6, measurement items A, C, D, and F are defined. For example, measurement item A is voltage, measurement item C is wind speed, measurement item D is weight on power lines, and measurement item F is an image of the surrounding area (image analysis results indicating whether trees have fallen).

[0046] Among these measurement items, those that change over time by more than a predetermined standard are distinguished from the others. In the example of FIG. 6, measurement items A, C, D, and F that are changing are displayed (highlighted), and the others are hidden. For example, measurement item A is voltage, measurement item C is wind speed, measurement item D is the weight on the power line, and measurement item F is an image of the surrounding area (image analysis results showing whether or not a tree has fallen). If there are changes in measurement item A (voltage), measurement item C (wind speed), and measurement item D (weight on the power line) that are more than a preset threshold, and measurement item F outputs a result indicating that a tree has fallen, there is a high possibility that a threat type "tree contact" has occurred.

[0047] (Input screen and search screen) 7 is a diagram illustrating an accident response report 2421a. The accident response report 2421a corresponds to an input format 2421b that has the same items as the accident response report 2421a. The input format 2421b has two functions. The first is to function as an input screen for creating a risk model 41 (including risk data 51). The second is to function as a search screen for extracting the part of the created risk model 41 that the user needs.

[0048] The model management unit 105 of the risk data management device 1 accepts the user's input of the details of the accident into the input format 2421b (input screen) via the input device 12. The model management unit 105 stores the input details as an accident response report 2421a in the auxiliary storage device 15, while creating a risk model 41 based on the input data. The display processing unit 107 displays the created risk model 41.

[0049] The model management unit 105 accepts a search keyword input by the user into the input format 2421b (search screen) via the input device 12. The model management unit 105 extracts (cuts out / extracts a portion of) the risk model 41 (including the risk data 51) that is associated with the input search keyword. The display processing unit 107 displays the extracted portion on the output device 13. That is, the model management unit 105 extracts a portion of the risk model 41 in response to a search request from the user.

[0050] A user reporting an accident enters the date of the accident in the accident occurrence date and time field 24211 of the input format 2421b (input screen). Similarly, the user enters the asset where the accident occurred in the accident occurrence equipment field 24212. The user enters the part where the accident occurred in the accident occurrence location field 24213. The user enters the impact in the accident impact field 24214. The user enters the cause of the accident (type of threat) in the accident cause field 24215. The user enters one or more measurement items (metrics) in the occurrence condition field 24216. The user enters countermeasures in the countermeasure content field 24217.

[0051] The model management unit 105 then creates a risk model 41 (including risk data 51) based on the input content. Specifically, the model management unit 105 creates nodes for the information input in one input format 2421b and connects the nodes with links in accordance with predetermined rules. At this time, the model management unit 105 sets the asset (accident occurrence equipment column 24212) as the center (primary key) of the risk model 41 and associates the risk data 51 with that asset.

[0052] As the model management unit 105 repeats this process, the risk model 41 gradually becomes larger and more refined. If a data management model 31 (FIG. 3) already exists, the model management unit 105 may change the node associations based on the input content and use the changed data management model 31 as the risk model 41. The configuration of the input format 2421b in FIG. 7 is merely an example, and any configuration may be used as long as it can result in the creation of a risk model 41.

[0053] On the other hand, a user who wishes to extract and view a portion of the risk model 41 that interests them inputs a search keyword in any field of the input format 2421b (search screen). For example, if the user inputs a specific asset as a search keyword, the model management unit 105 displays a portion of the risk model 41 of a predetermined size that includes the asset (including the risk data 51).

[0054] (Asset Lifecycle Model) 8 is a diagram showing an example of an asset lifecycle model 61. The asset lifecycle model 61 in FIG. 8 is extracted from the original risk model 41 by the model management unit 105 and displayed by the display processing unit 107. The original risk model 41 is also created by the model management unit 105.

[0055] Typical motivations for utilizing an asset lifecycle model 61 include, for example: Motivation 1: I want to know the environmental information history of a specific asset (e.g., a steel tower). <Motivation 2> I want to know the operating and work history of a specific asset. Motivation 3: I want to know what other assets are directly and physically connected to a specific asset. Motivation 4: I want to know about other assets that are located in environments similar to that of a specific asset.

[0056] Among the above, users with motives 1 and 2 want to know the causes of accidents or countermeasures for assets that have actually caused or are likely to cause accidents. Users with motives 3 and 4 want to determine assets that deserve attention from the perspective of accident prevention.

[0057] Looking at the asset lifecycle model 61 in Figure 8, we can see the following: The user inputs a certain asset A as a search keyword into the search screen. The asset information node 611a in the shape of a parallelogram corresponds to asset A. The asset information node 611a is associated in chronological order with an equipment registration node 612a, an operation node 612b, a maintenance node 612c, and an operation node 612d.

[0058] Of the equipment registration node 612a, the operation node 612b, the maintenance node 612c, and the operation node 612d, the maintenance node 612c belongs to the work information 24 (Figure 1), and the equipment registration node 612a, the operation node 612b, and the operation node 612d belong to the operation information 22 (Figure 1).

[0059] The equipment registration node 612a, the operation node 612b, the maintenance node 612c, and the operation node 612d respectively store worker information 613a, 613b, 613c, and 613d. 3 The worker information 613a, 613b, 613c and 61d are associated with each other. 3 d also belongs to the work information 24 (FIG. 1).

[0060] Asset information nodes 611a, 611b, and 611c are serially associated. These assets are "continuous assets." A continuous asset is a group of assets that are connected in series by a power line or the like. A continuous asset may branch off along the way.

[0061] Now, the user has motives 1 and 2. The user thinks that there is a problem with the maintenance (repair) performed in the past on asset A. Therefore, the user moves the cursor 614 to the maintenance node 612c. Then, the display processing unit 107 displays an environmental information icon 615.

[0062] Next, when the user selects the environmental information icon 615 with the cursor 614, the display processing unit 107 displays on the screen the environmental information 21 (FIG. 1) that belongs to a predetermined time period including the time when the maintenance was performed, and that relates to asset A. The data displayed here is, for example, humidity transition 62 around asset A. The reason why the humidity transition 62 around asset A is displayed here is because the environmental information 21 is associated with the asset information (reference numeral 23 in FIG. 1) in the underlying risk model 41. Note that in FIG. 8, an "association" arrow points from the environmental information icon 615 to the maintenance node 612c. This indicates that the humidity transition 62 is the humidity transition related to asset A, particularly the time when the "maintenance" was performed.

[0063] Thereafter, when the user performs a predetermined operation, the display processing unit 107 displays humidity fluctuations 63. The humidity fluctuations 63 indicate the maximum and minimum humidity values ​​for each day of a predetermined time period (for example, one month). A thick frame 64 indicates the period for one week centered on the day on which maintenance was actually performed, and corresponds to the shaded portion of the humidity trend 62.

[0064] Assume that the user begins to have the above-mentioned motives 3 and 4, and furthermore, specifies the asset information node 611b with the cursor 614. Then, the display processing unit 107 displays the environmental information, driving information, and work information associated with the asset information node 611b in chronological order. Fig. 9, which will be described later, is an example of such a display.

[0065] FIG. 9 is a diagram showing a part of the asset lifecycle model 61. When tracing a continuous asset (multiple steel towers connected in series by a power transmission line), the environment of the steel towers clearly changes at a certain position. For example, when a continuous asset crosses a mountain range, the climate on both sides of the mountain range is significantly different. In such a case, the user must change the content of work and operation on both sides.

[0066] The model management unit 105 refers to the area information 29 and the environmental information 21, and acquires environmental information for multiple areas (referred to as "surrounding areas") located around the area where the asset specified by the user is located (referred to as "specified area"). In the example of FIG. 9, two points, point A in a mountainous area and point B in a plain area, are shown as the surrounding areas. Of the environmental information of the acquired surrounding areas, the model management unit 105 identifies the area (referred to as "similar environment area") that has environmental information closest to the environmental information of the specified area.

[0067] The display processing unit 107 displays the following content on the asset lifecycle model 61 or the risk model 41. -Time-series environmental information (temperature, etc.) for the designated area, surrounding areas, and areas with similar environments - Distance between each of the surrounding areas and similar areas and the designated area - Geographical similarity between the designated area and similar environmental areas (plains, mountainous areas, specific river basins, etc.) 9, the display processing unit 107 may display the following comment. This comment may be automatically generated by the program or may be manually input by the user. A comment that point B, a surrounding area farther from the designated area, is an area with a similar environment to the designated area.

[0068] FIG. 10 is a flowchart of the processing procedure. In step S101, the environmental information registration unit 101 etc. of the risk data management device 1 acquires the environmental information 21 etc. Specifically, the environmental information registration unit 101 acquires the environmental information 21 as part of the model basic data 20 from an arbitrary device and stores it in the environmental information storage unit 111. The operation information registration unit 102, asset information registration unit 103 and work information registration unit 104 of the risk data management device 1 also perform similar processing.

[0069] In step S102, the model management unit 105 of the risk data management device 1 creates the data management model 31 (FIG. 3). Specifically, in response to user operation, the model management unit 105 creates the data management model 31 using the model basic data 20 (environmental information 21, etc.) that is distributed and stored in the environmental information storage unit 111, etc., and stores the created data management model 31 in the model storage unit 115. In response to user operation, the display processing unit 107 of the risk data management device 1 displays the data management model 31 on the output device 13 or the terminal device 2.

[0070] In step S103, the model management unit 105 accepts the accident response report 2421a (FIG. 7). Specifically, first, the model management unit 105 displays an input format 2421b (FIG. 7) as an input screen on the output device 13 or the terminal device 2 via the display processing unit 107. Second, the model management unit 105 accepts data input by the user into each field of the input format 2421b. The model management unit 105 may directly receive the completed accident response report 2421a as electronic data or printed matter via the input device 12 or the terminal device 2.

[0071] In step S104, the model management unit 105 creates a risk model 41 (FIG. 4). Specifically, the model management unit 105 creates the risk model 41 (including risk data 51) based on the contents of the accident response report 2421a, using the environmental information 21, operation information 22, asset information 23, work information 24, and area information 29. At this time, the model management unit 105 may create the risk model 41 by modifying the association between nodes of the existing data management model 31.

[0072] In step S105, the model management unit 105 accepts a search keyword. Specifically, first, the model management unit 105 displays an input format 2421b as a search screen on the output device 13 or the terminal device 2 via the display processing unit 107. Second, the model management unit 105 accepts a search keyword input by the user into any field of the input format 2421b. For example, the user inputs "October 15, 2021" into the accident occurrence date and time field 24211 and "tower B" into the accident occurrence equipment field 24212.

[0073] In step S106, the model management unit 105 extracts a relevant portion of the risk model 41. Specifically, first, the model management unit 105 extracts a predetermined range of nodes in the risk model 41 that are directly or indirectly associated with "Tower B." Second, the model management unit 105 further extracts a portion having a date and time within a predetermined range including "October 15, 2021" from the portion extracted in "first" of step S106.

[0074] In step S107, the display processing unit 107 of the risk data management device 1 displays the relevant portion of the risk model 41. Specifically, the display processing unit 107 displays the portion of the risk model 41 extracted in "second" of step S106 on the output device 13 or the terminal device 2. The risk model 41 displayed at this time has "Tower B" at its center (root node), and risk data 51 is associated with the root node.

[0075] In step S108, the model management unit 105 of the risk data management device 1 creates the asset lifecycle model 61. Specifically, the model management unit 105 creates the asset lifecycle model 61 by rearranging in chronological order the nodes (particularly the nodes of the operation information 22 and the work information 24) included in the part of the risk model 41 extracted in the "second" of step S106.

[0076] In step S109, the display processing unit 107 of the risk data management device 1 displays the asset life cycle model 61. Specifically, the display processing unit 107 displays the asset life cycle model 61 created in step S108 on the output device 13 or the terminal device 2. The asset life cycle model 61 displayed at this time displays the details of the operations and work performed on the tower B in chronological order (see reference numeral 61 in FIG. 8).

[0077] Thereafter, when the user places the cursor 614 on any node, the display processing unit 107 will display various information on the screen, as described above in the explanation of Figures 8 and 9. Even while a user is looking at such a screen, the risk model 41 changes from moment to moment. For example, in response to an accident response report 2421a entered by another user, the model management unit 105 may add new countermeasure nodes (reference numerals 2307a and 2307b in Figure 5) to the risk data 51 of the risk model 41. The change detection unit 106 constantly monitors such changes.

[0078] In step S110, the change detection unit 106 of the risk data management device 1 determines whether or not a countermeasure against a threat has been added. Specifically, if the change detection unit 106 detects that a countermeasure has been added to the risk data 51 of the risk model 41 (step S110 "YES"), it proceeds to step S111, and otherwise (step S110 "NO"), it remains in standby.

[0079] In step S111, the change detection unit 106 outputs a warning. Specifically, the change detection unit 108 displays the newly added measures together with the nodes (threats, assets, operations, etc.) associated with the measures on the output device 13 or the terminal device 2. Thereafter, the processing procedure ends.

[0080] In step S110, the change detection unit 106 may monitor the measurement items of the metrics associated with the threats to which countermeasures have already been associated, and if a change in the measurement items is detected, may output the threat in step S111. change The detection unit 106 may output the asset with which the threat is associated and the work and operation associated with the asset in chronological order.

[0081] In step S110, the change detection unit 106 may monitor whether a new task that matches the content of the countermeasure against the threat (for example, the task of applying water-repellent paint to protect against heavy snow) is added. If this is detected, in step S111, change The detection unit 106 may display a message indicating that the risk model may be modified (for example, that the vulnerability level will decrease after the work).

[0082] (Effects of this embodiment) The effects of the risk data management device of this embodiment are as follows. (1) The risk data management device can visualize operation information and work information in association with asset information. (2) The risk data management device can visualize threats to assets and countermeasures against those threats. (3) The risk data management device can display a portion of the risk model requested by the user. (4) The risk data management device can visualize asset operation information and asset work information.

[0083] (5) The risk data management device can visualize natural disasters to infrastructure facilities. (6) The risk data management device can visualize continuously connected infrastructure facilities. (7) The risk data management device can visualize areas that have an environment similar to that of a specific infrastructure facility. (8) The risk data management device can visualize new countermeasures.

[0084] The present invention is not limited to the above-described embodiments, but includes various modifications. 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 described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0085] Furthermore, the above-mentioned configurations, functions, processing units, processing means, etc. may be partly or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-mentioned configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement 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. In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0086] 1. Risk data management device 2. Terminal Device 11 Central control unit 12 Input Devices 13 Output Devices 14 Main memory 15 Auxiliary storage 16 Network Interfaces 17 Programs 20 Basic data for the model 21 Environmental information 22 Operation Information 23 Asset Information 24 Work Information 31 Data Management Model 41 Risk Model 51 Risk Data 61 Asset Lifecycle Model 105 Model Management Department 106 Change detection unit 107 Display processing unit 115 Model Memory Unit

Claims

1. A model management unit that creates a risk model in which nodes showing environmental information of infrastructure equipment that is directly affected by the natural environment, operation information of said infrastructure equipment, and work information on said infrastructure equipment are linked via links to nodes showing asset information that shows the characteristics of said infrastructure equipment itself, and nodes showing risk data regarding threats of natural disasters that may cause failures to said infrastructure equipment, the level of said threats, and countermeasures against said threats are linked via links to nodes showing said asset information; a display processing unit that displays the created risk model; Equipped with When the model management unit extracts a part of the risk model in response to a search request from a user, the display processing unit displays the extracted risk model; When the model management unit creates an asset lifecycle model by chronologically arranging operation information or work information associated with specific asset information included in the risk model, the display processing unit displays the created asset lifecycle model, The display processing unit In the asset lifecycle model, the plurality of infrastructure facilities are indicated as a continuous asset that is continuously connected; displaying a similar environment area having environmental information closest to the environmental information of the designated area, identified by the model management unit from among a plurality of surrounding areas located around the designated area in which the asset designated by the user is located; A risk data management device comprising:

2. A change detection unit is provided which monitors whether a node indicating a new countermeasure is associated via a link with a node indicating the risk data of the risk model, and when it detects that a node indicating a new countermeasure is associated via a link, displays that the countermeasure has been newly associated with the threat; The risk data management device according to claim 1,

3. The model management unit of the risk data management device comprises: A risk model is created in which nodes showing environmental information of infrastructure facilities that are directly affected by the natural environment, operation information of the infrastructure facilities, and work information on the infrastructure facilities are associated via links with nodes showing asset information that shows the characteristics of the infrastructure facilities themselves, and nodes showing risk data related to threats of natural disasters that could cause failures in the infrastructure facilities, the level of the threats, and measures against the threats are associated via links with nodes showing the asset information, The display processing unit of the risk data management device Display the created risk model, When the model management unit extracts a part of the risk model in response to a search request from a user, the display processing unit displays the extracted risk model; When the model management unit creates an asset lifecycle model by chronologically arranging operation information or work information associated with specific asset information included in the risk model, the display processing unit displays the created asset lifecycle model, The display processing unit In the asset lifecycle model, the plurality of infrastructure facilities are indicated as a continuous asset that is continuously connected; displaying a similar environment area having environmental information closest to the environmental information of the designated area, identified by the model management unit from among a plurality of surrounding areas located around the designated area in which the asset designated by the user is located; A risk data management method comprising:

Images