Inspection data management device

Abstract

To provide a management device and method for bridge and pier inspection data that can manage inspection data in a tree structure according to different management purposes of each data management worker and simplify data updates for the inspection data.SOLUTION: When a worker sequentially selects and inputs classification items excluding facility name from among classification items such as facility name, installation area, installation year, bridge length, most recent inspection year, judgment category at the time of the most recent inspection, and measure status to search for inspection data, tree formation means 14 forms a desired tree structure in which the classification items are hierarchically arranged in a selected and input order, and inspection data for each classification item of multiple inspection objects that are accepted by acceptance means 12, clustered by clustering means 13, and stored and held in a server 5 is arranged by arrangement means 15 in the formed desired tree structure.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an inspection data management device and a management method for inspecting a plurality of infrastructure structures, which are inspection objects installed in various locations, and managing the inspection data obtained. [Background technology]

[0002] Conventionally, workers have inspected infrastructure structures such as bridges, piers, tunnels, and expressways, which are inspection objects installed in various locations, and compiled the inspection results in reports, etc. However, with the aim of reducing the burden on workers when inspecting inspection objects, a support system has been proposed that displays a screen on the display of a communication terminal for inputting the inspection date and time, inspection results, etc., and creates a report in a specified format based on the information entered on the screen (see, for example, Patent Document 1).

[0003] Reports created by this type of system record inspection data including the inspection date and time, inspection location and position, as well as the inspection results if any abnormalities are found. For example, in the case of a bridge inspection, if a crack is found in the bridge, an inspection image is also recorded, including an image of the cracked area that shows what kind of crack has occurred and where on the bridge. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-26274 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, report formats vary from country to country and local government to local government, and before the inspection data is entered into the required report format, it is temporarily stored in a computer's memory, hard disk, server, etc.; however, it is common practice to set up a folder tree structure to make it easy for workers to search for the desired inspection data, and to store and manage the inspection data in each folder in memory, etc.

[0006] For example, we will explain the conventional method of managing inspection data in the built-in memory of a PC, a hard disk to which a PC can be connected, or a server, corresponding to multiple classification items such as the facility name given to the inspection object, the installation area, the installation year, the bridge length, the most recent inspection year, the judgment category which quantifies the judgment status at the time of the most recent inspection, and the status of measures regarding whether or not repair, maintenance, or renovation measures have been taken.

[0007] When managing inspection data for objects to be inspected throughout Japan using the built-in memory of a PC or a hard disk or server to which a PC can be connected, as shown in Figure 4, for each prefecture or city / ward / town / village that is an administrative region, with the management objective based on the "year in which the most recent inspection was carried out," child trees for each fiscal year (Gregorian calendar year) such as 2014, 2015, ..., 2023 are constructed with the classification item "year in which the most recent inspection was carried out" as a parent tree, and child trees for the "most recent judgment category," for example, three categories I, II, and III, are constructed with each inspection year as a parent tree.

[0008] Furthermore, there is a method for managing the inspection data of multiple inspection objects throughout Japan by using each of the three judgment categories as a parent tree to create child trees for the four "measure status" statuses, for example, preventive maintenance stage, measures completed, measures not yet started, and not subject to investigation, and using each of the four measure statuses as a parent tree to create child trees for each year (Gregorian calendar) of "construction year," such as 1950, 1980, 2010, and over 2010, and setting the names of facilities that are inspection objects corresponding to each "construction year" (for example, Terada Overpass).

[0009] In the tree structure shown in Figure 4, when an inspection data management worker tries to search for inspection data for an inspection object with a desired facility name, the worker can reach the data file for the desired facility name (for example, Terada Overpass) by looking down the tree from "Most recent inspection implementation year" to "Most recent assessment category," "Measures status," and "Erection year."

[0010] However, for inspection data management workers with different management objectives, it may be inconvenient to follow the tree below the "year of most recent inspection" in the tree structure for management objectives based on the "year of most recent inspection" shown in Figure 4, and they may find it convenient to manage inspection data using the tree structure shown in Figure 5, which corresponds to a management objective different from that of Figure 4.

[0011] Therefore, it is also being considered to manage inspection data with a tree structure for a different management purpose, as shown in Figure 5. To explain the tree structure in Figure 5, assuming that bridge lengths are divided into ranges of 10m or less (10m), 50m (10-50m), 100m (50-100m), etc., child trees are constructed for each bridge length, such as 10m, 50m, 100m, etc., with "bridge length" as the parent tree, and child trees are constructed for each bridge length for the three "most recent judgment classification" classifications, namely Class I, Class II, and Class III, with each bridge length as a parent tree.

[0012] Furthermore, with each of the three judgment categories as a parent tree, a child tree of specific city, ward, town, and village names for the classification item "administrative district_city, ward, town, and village name" is constructed, and with each city, ward, town, and village name as a parent tree, a child tree is constructed for each Gregorian year of "construction year" such as 1950, 1980, 2010, and over 2010, and by setting the names of facilities such as the Terada Overpass, which are inspection objects corresponding to each year (Gregorian year) of "construction year," inspection data for multiple inspection objects throughout Japan is managed.

[0013] Furthermore, inspection data management workers who find the tree structure in Figure 5 convenient can arrive at the data file for the desired facility name (for example, Terada Overpass) by looking down the tree from "Bridge Length" to "Most Recent Assessment Category," "Administrative District_City / Ward / Town / Village Name," and "Erection Year."

[0014] Also, with consideration for the convenience of multiple inspection data management operators, it is being considered to manage inspection data in a tree structure that combines the two tree structures shown in Figures 4 and 5, as shown in Figure 6. In this way, inspection data management operators can choose the tree structure that they find most convenient, that is, either the classification item "Year of Most Recent Inspection" or "Bridge Length," and follow the trees at lower levels to arrive at the data file for the desired facility name.

[0015] However, since the one shown in Figure 6 is a combination of two types of tree structures, for example, for Terada Overbridge, data files are stored in the tree of "Most Recent Judgment Classification" III, which is a hierarchical tree under 2023 with "Most Recent Inspection Year" as the parent tree, "Measures Status" under that, and "Erection Year" under that, 1980, and data files are stored in the tree of "Most Recent Judgment Classification" III, which is a hierarchical tree under bridge length 100m with "Bridge Length" as the parent tree, "Administrative District_City / Ward / Town / Village Name" Ube City under that, and "Erection Year" under that, 1980, and the same data file for "Terada Overbridge" is stored in two places. Therefore, when it becomes necessary to update the data file of the inspection data for one facility name "Terada Overbridge", it is necessary to update the data files in two places to update the inspection data for "Terada Overbridge", which causes a problem that the update work becomes complicated and simple data management cannot be performed. Furthermore, when three or more types of tree structures are combined, inspection data for one facility name will require updating data files in three or more places, making the updating work even more complicated.

[0016] The present invention has been made in consideration of the above-mentioned problems, and provides an inspection data management device and method that can manage inspection data for infrastructure structures in a tree structure according to the different management objectives of each inspection data management worker, and can simplify data updates for the inspection data. [Means for solving the problem]

[0017] In order to achieve the above object, an inspection data management device according to the present invention inspects a plurality of infrastructure structures that are inspection objects installed in various locations, and manages the inspection data obtained, the inspection data management device comprising: a reception means for receiving, as the inspection data, information including numerical values ​​input for each of the plurality of inspection objects corresponding to a plurality of classification items such as the facility name, installation area, installation year, bridge length, most recent inspection year, judgment category that quantifies the judgment status at the time of the most recent inspection, and the status of measures regarding the presence or absence of measures such as repair, maintenance, and improvement, which are given to the inspection objects; a storage means for storing and holding the inspection data for the plurality of inspection objects received by the reception means; and a storage means for storing and holding the numerical values ​​of the inspection data corresponding to at least the installation year, the bridge length, the inspection year, and the judgment category, among the inspection data for the plurality of inspection objects stored and held in the storage means, the inspection data for each of the plurality of inspection objects that are accepted in the acceptance step, clustered in the clustering step, and stored and held in the storage means, and a clustering means for clustering the inspection data for each of the plurality of inspection objects, the bridge length, the inspection year, and the judgment category into a plurality of ranges that are set in advance, assigning indexes to the clusters, and storing and holding the clustered data in the storage means; a tree forming means for arranging the classification items in a desired tree configuration in the input order based on the classification items excluding the facility name being selectively input in sequence by an inspection data management operator in order to search for the inspection data; an arranging means for arranging the inspection data for each of the classification items for each of the plurality of inspection objects that are accepted in the acceptance step, clustered in the clustering step, and stored and held in the storage means, in the tree configuration formed by the tree forming means; and a display control means for controlling a display means to display the inspection data arranged in the tree configuration by the arranging means on a display screen.

[0018] Further, the inspection data management method according to the present invention is a method for managing inspection data, which inspects a plurality of infrastructure structures that are inspection objects installed in various locations and manages the inspection data obtained, and includes a receiving step of receiving, as the inspection data, information including numerical values ​​input for each of the plurality of inspection objects corresponding to a plurality of classification items such as the facility name, installation area, installation year, bridge length, most recent inspection year, judgment category that quantifies the judgment status at the time of the most recent inspection, and the measure status regarding the presence or absence of measures such as repair, maintenance, and improvement, which are given to the inspection object; a storage step of storing and holding the inspection data for the plurality of inspection objects received in the receiving step in a storage means; and a storage step of storing and holding the numerical values ​​of the inspection data corresponding to at least the installation year, the bridge length, the inspection year, and the judgment category, among the inspection data for the plurality of inspection objects stored and held in the storage step, for the installation year, the bridge length, the inspection year, and the judgment category, The method includes a clustering process for clustering the bridge length, the inspection year, and the judgment category into a plurality of preset ranges, assigning indexes to the clusters, and storing and holding the indexes in the storage means; a tree forming process for arranging the classification items in a desired tree configuration in the input order based on the classification items excluding the facility name being selectively input in sequence by an inspection data management operator in order to search for the inspection data; an arranging process for arranging the inspection data for each classification item of the plurality of inspection objects that are accepted in the acceptance process, clustered in the clustering process, and stored and held in the storage means, in the tree configuration formed in the tree forming process; and a display control process for controlling a display means to display the inspection data arranged in the tree configuration by the arranging means on a display screen. Effect of the Invention

[0019] According to the present invention, when an inspection data management worker selectively inputs classification items excluding facility names in order to search for inspection data, the classification items are hierarchically arranged in a desired tree structure in the order in which they were input, and the inspection data for each classification item of a plurality of inspection objects stored and held in a storage means, including the clustered and indexed inspection data, is arranged in the desired tree structure. Therefore, inspection data can be managed in a tree structure according to management purposes that differ for each inspection data management worker, and when updating inspection data, it is only necessary to update the inspection data in one storage location, thereby simplifying the update work. [Brief description of the drawings]

[0020] [Figure 1] FIG. 2 is a block diagram of a management device according to an embodiment of the present invention. [Diagram 2] FIG. 4 is a diagram showing an example of inspection data to be managed. [Diagram 3] 2 is a flowchart illustrating the operation of the device shown in FIG. 1. [Figure 4] FIG. 13 is an explanatory diagram of the operation of a conventional example. [Diagram 5] FIG. 13 is an explanatory diagram of the operation of a conventional example. [Figure 6] FIG. 13 is an explanatory diagram of the operation of a conventional example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] An embodiment of a management device for inspection data of bridges and piers according to the present invention will be described in detail with reference to Figures 1 to 3. Note that this embodiment shows a case where an inspection object is a bridge, which is an infrastructure structure.

[0022] <Configuration of management device> First, the configuration of a management device according to an embodiment of the present invention will be described with reference to FIG.

[0023] As shown in FIG. 1, the management device 1 comprises a personal computer or the like, and is connected to an input means, a keyboard 2, a display means 3 comprising an LCD display, a printing means 4 such as various printers, and a storage means 5 comprising a server (hereinafter referred to as the server).

[0024] The management device 1 in this embodiment executes the following functions, and the ROM of the built-in memory 11, which includes a ROM and a RAM (DRAM, SRAM, etc.), stores control programs for executing the following functions, and the following functions are performed by executing the corresponding control programs. The RAM constituting the built-in memory 11 temporarily stores data entered via the keyboard and data for processing operations.

[0025] (1) A function as a reception means 12 that receives information including numerical values ​​input for multiple inspection objects corresponding to multiple classification items such as the facility name given to the inspection object, the administrative district (name of prefecture and name of city, ward, town, or village) in which the object is installed, the year of installation (Gregorian calendar year), the bridge length (unit: meters), the year in which the most recent inspection was carried out (Gregorian calendar year), the judgment category in which the judgment status at the time of the most recent inspection is quantified into I, II, III, etc., and the status of measures regarding the presence or absence of repair, maintenance, etc. (measures not yet started, measures completed, preventive maintenance stage) as inspection data, and stores and retains the information in the server 5, which is a storage means. (2) A function as a clustering means 13 that clusters and indexes the numerical values ​​of the inspection data corresponding to at least the installation year, bridge length, inspection year, and judgment category among the inspection data of the plurality of inspection objects stored in the server 5 into a plurality of ranges previously set for each of the installation year, bridge length, inspection year, and judgment category, and stores and retains the clustered numerical values ​​in the server 5. (3) Function as a tree forming means 14 for forming a desired tree configuration by arranging classification items in the input order based on the classification items excluding facility names being selectively input by the inspection data management operator through operation of the keyboard 2 in order to search for inspection data. (4) A function as an arrangement means 15 that arranges the inspection data for each classification item of multiple inspection objects that have been accepted by the accepting means 12, clustered and indexed by the clustering means 13, and stored in the server 5, in a tree structure formed by the tree forming means 14. (5) A function as a display control means 16 that controls the display means 3 to display the inspection data arranged in a tree structure by the arrangement means 15 on the display screen of the display means 3.

[0026] For example, as shown in FIG. 2, when inspection data including each classification item is entered using keyboard 2 for nine bridges that are inspection objects, with facility names of "Iwaishima Miura No. 3 Bridge," "Iwaishima Miura No. 2 Bridge," "Ejiri Bridge," "Iwaishima Miura B Bridge," "Iwaishima Miura No. 1B Bridge," "Miura No. 1 Bridge," "Hani Bridge," "Tsuruho B Bridge," and "No. 1 Kaminami Bridge," the input inspection data is accepted by reception means 12 as inspection data that corresponds to the facility name and classification item, and includes information including numerical values ​​for multiple inspection objects such as administrative district (name of prefecture and name of city / ward / town / village), year of installation (Gregorian calendar year), bridge length (in meters), etc., and is stored and held in server 5.

[0027] At this time, for example, for the facility name "Iwaishima Miura No. 3 Bridge," when the worker operates keyboard 2 to input Yamaguchi Prefecture as the "administrative district / prefecture name," Kaminoseki Town as the "administrative district / city / ward / town name," 1993 as the "construction year," 2.3 m as the "bridge length," 2019 as the "most recent inspection year," category I as the "most recent assessment category," and "- " indicating not subject to investigation as the "measures status," the inspection data for the facility name "Iwaishima Miura No. 3 Bridge" that was input is accepted by reception means 12 and stored in server 5.

[0028] For example, for the facility name "Ejiri Bridge," when an operator operates keyboard 2 to input Yamaguchi Prefecture as the "administrative district / prefecture name," Yanai City as the "administrative district / city / town name," 1981 as the "construction year," 4.2 m as the "bridge length," 2019 as the "most recent inspection year," category III as the "most recent assessment category," and measures not yet started as the "measures status," these are stored and held in server 5 as shown in Figure 2. Inspection data for inspection objects with other facility names is also stored and held in server 5 in a similar manner.

[0029] At this time, the clustering means 13 clusters and indexes the numerical values ​​of the inspection data corresponding to the installation year, bridge length, inspection year, and judgment category, which are numerical data among the inspection data of multiple inspection objects received by the receiving means 12 and stored in the server 5, for each of multiple ranges previously set for the installation year, bridge length, inspection year, and judgment category, as follows:

[0030] For example, the construction year (Gregorian calendar year) is clustered into decade ranges in 10-year increments, so that if the actual construction year is 1993, it is clustered in the 1990s and indexed as 1990, if it is 1981, it is clustered in the 1980s and indexed as 1980, if it is 1981, it is clustered in the 1980s and indexed as 1980, if it is 2014, it is clustered in the 2010s and indexed as 2010, and if it is over 2020, it is clustered beyond 2010 and indexed as greater than 2010, and these are stored and retained in server 5.

[0031] Further, the bridge length is clustered into length ranges such as less than 10 m, 10 m or more but less than 50 m, 50 m or more but less than 100 m, and 100 m or more, and indexed with 10, 50, 100, and over 100, respectively. The inspection year (Gregorian calendar year) is clustered by Gregorian calendar year such as 2014, 2015, ..., and indexed with the Gregorian calendar years 2014, 2015, ..., and the judgment category is clustered into category I, category II, or category III, and indexed with I, II, or III, and stored and held in the server 5. The judgment categories are classified into category I, category II, or category III by a human being according to predetermined criteria.

[0032] Then, in order to search for inspection data, the inspection data management worker operates the keyboard 2 and selectively inputs classification items excluding the facility name from the multiple classification items mentioned above. The tree forming means 14 then arranges the classification items in a hierarchy in the order in which they were input, forming the tree structure desired by the inspection data management worker. The inspection data for each of the bridges (inspection objects) with the multiple facility names that have been accepted by the accepting means 12 and clustered and indexed by the clustering means 13 and stored and held in the server 5 are then arranged in the formed tree structure and stored and held in the server 5.

[0033] For example, when an inspection data management worker selectively inputs classification items in a desired order to search for "bridges in Ube City with a bridge length of less than 100 m, a most recent judgment category of category III, and a bridge erected before 1980 (corresponding to a bridge age of 30 years)," the tree formation means 14 arranges the above-mentioned classification items, excluding facility names, in the order of "bridge length" as a parent tree, the tree below that as "judgment category," the tree below that as "administrative district / city / ward / town / village name," and the tree below that as "emergency year," forming a tree configuration desired by the inspection data management worker. In this case, the tree configuration based on the search conditions is, for example, as shown in FIG. 5, and the display control means 16 controls the display means 3 to display the tree on the display screen. Here, the display screen of the display means 3 can be printed by the printing means 4 under the control of the management device 1.

[0034] In this way, when the inspection data management operator inputs the search criteria of "bridges in Ube City with a bridge length of less than 100 m, a most recent judgment category of category III, and a bridge erected before 1980 (corresponding to a bridge age of 30 years)", the tree structure shown in Fig. 5 is formed, and the "facility name" corresponding to the data folder name of the inspection data included in the tree of the index in the tree structure of Fig. 5 with "bridge length" of less than 100 m, "most recent judgment category" of category III, "administrative district / city / ward / town / village name" of Ube City, and "emergency year" of 1980 is displayed on the display screen of the display means 3. For example, as shown in Fig. 5, four data files with the file names of the facility names of Katakura Viaduct, Gongen Bridge, Second Nishigaoka Overbridge, and Terada Overbridge are displayed, and by opening any of the data files, the detailed contents of the inspection data are displayed on the display screen of the display means 3. The detailed contents of the inspection data can also be printed by the printing means 4.

[0035] Therefore, for example, if there is a need to update the data on the measures taken in the inspection data for the Terada Overbridge, out of the four bridges with facility names Katakura Viaduct, Gongen Bridge, Second Nishigaoka Overbridge, and Terada Overbridge, as described above, the inspection data management worker can input the search criteria such as "bridges with a bridge length of less than 100 m, a most recent assessment category of Category III, and located in Ube City that were erected before 1980 (equivalent to a bridge age of more than 30 years)," and the desired tree structure based on the input criteria will be formed and displayed on the display means 3. The worker can then follow the displayed tree to open the data file for the Terada Overbridge, and the data content of the "measures taken" in the data file for the Terada Overbridge can be updated, for example, by rewriting the data in one data storage location for the Terada Overbridge.

[0036] Next, a method for managing inspection data will be described with reference to the flowchart of FIG.

[0037] When the inspection data for each of the bridges, which are the inspection objects shown in Figure 2, is input by the inspection data management operator operating the keyboard 2, each of the input inspection data is accepted by the acceptance means 12 (step S1), as shown in Figure 3, temporarily stored in the memory 11, and stored in the server 5 after input is completed.

[0038] Next, when the input of the inspection data is completed, the numerical values ​​of the inspection data corresponding to the installation year, bridge length, inspection year, and assessment category of the multiple bridge inspection data stored in server 5 are clustered into multiple ranges that are pre-set for each of the installation year, bridge length, inspection year, and assessment category (step S2), and these clustered inspection data are indexed and stored in server 5 together with the non-clustered data (step S3).

[0039] Then, for example, for the purpose of updating data or checking the data contents, the data management operator determines whether or not any classification items other than the facility name have been selected and input in order to search for inspection data (step S4). If the result of this determination is NO, the process is repeated until the result of the determination is YES. If the result of the determination is YES, a tree is formed in which the classification items are arranged in the desired tree configuration in the order in which they were input, based on the fact that classification items other than the facility name have been selected and input (step S5).

[0040] Thereafter, the inspection data for each classification item of multiple bridges (inspection objects) that were accepted in the processing of step S1 and clustered and indexed in the processing of step S3 and stored in the server 5 is arranged in a tree structure formed in the processing of step S5 (step S6), and the inspection data arranged in the tree structure (for example, the tree structure in Figure 4 or Figure 5) based on the search conditions entered by the inspection data management operator is displayed on the display screen of the display means 3 (step S7), after which the operation ends.

[0041] Therefore, according to the above-described embodiment, when an inspection data management worker selectively inputs classification items, excluding the facility name, from among the classification items such as the facility name, installation area, installation year, bridge length, year of the most recent inspection, judgment category which quantifies the judgment status at the time of the most recent inspection, and the measure status regarding whether or not repair / maintenance measures have been taken, in order to search for inspection data, a desired tree structure is formed in which the classification items are hierarchically arranged in the input order, and the inspection data for each classification item of each of the multiple inspection objects stored and held in the server 5 is arranged in the desired tree structure that has been formed, so that inspection data can be managed in a tree structure according to management purposes which differ for each worker, and even when updating inspection data, it is only necessary to update the inspection data in the data file which is a single storage location, thereby simplifying the update work.

[0042] Therefore, when an inspection data management worker inputs search criteria such as "bridges located in Ube City with a bridge length of less than 100 m, a most recent assessment category of Category III, and a year of construction before 1980 (corresponding to a bridge age of more than 30 years)," the desired tree structure is formed and displayed on the display means 3, making it possible to easily open the data file for Terada Overbridge, and updating the data content such as "measures status" of the inspection data for the opened Terada Overbridge. This means that only one data file needs to be configured, rather than having to update two data files related to Terada Overbridge as in the past, and data management becomes easier as the update work can be performed easily.

[0043] The present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the spirit of the present invention. For example, the above embodiment has been described with reference to a bridge, which is an infrastructure structure, but the inspection object may be a bridge pier, a tunnel, a highway, etc.

[0044] For example, in the above embodiment, the classification items have been described as facility name, installation area, installation year, bridge length, most recent inspection year, assessment category that quantifies the assessment status at the time of the most recent inspection, and measure status regarding whether or not repair / maintenance measures have been taken, but these classification items are merely examples, and the classification items are not limited to these.

[0045] Furthermore, in the above-described embodiment, the clustering process is not limited to the example in the above-described embodiment.

[0046] The present invention can be widely applied to inspection data management techniques in general, which inspect a plurality of infrastructure structures, which are inspection objects installed in various locations, and manage the inspection data obtained. [Explanation of symbols]

[0047] 1: Management device 2: Keyboard 3:Display means 4:Printing means 5: Server (storage means) 12: Reception method 13: Clustering methods 14: Tree formation means 15: Array method 16: Display control means

Claims

1. An inspection data management device that inspects a plurality of infrastructure structures that are inspection objects installed in various locations and manages the inspection data obtained, A receiving means for receiving, as the inspection data, information including numerical values ​​input for each of the plurality of inspection objects corresponding to a plurality of classification items such as the facility name, installation area, installation year, bridge length, most recent inspection year, evaluation category that quantifies the evaluation status at the time of the most recent inspection, and the status of measures regarding the presence or absence of measures such as repair, maintenance, and improvement, which are given to the inspection object; A storage means for storing and holding the inspection data of the plurality of inspection objects received by the reception means; a clustering means for clustering the numerical values ​​of the inspection data corresponding to at least the installation year, the bridge length, the inspection year, and the judgment category among the inspection data of the plurality of inspection objects stored and held in the storage means into a plurality of ranges previously set for each of the installation year, the bridge length, the inspection year, and the judgment category, and for storing and holding the clustered numerical values ​​in the storage means by assigning indexes to the clustered numerical values; a tree forming means for arranging the classification items in a desired tree structure in the input order based on the classification items, excluding the facility name, being selectively input by an inspection data management operator in order to search for the inspection data; an arrangement means for arranging the inspection data for each of the classification items of the plurality of inspection objects, which are accepted in the accepting step, clustered in the clustering step, and stored and held in the storage means, in the tree configuration formed by the tree forming means; a display control means for controlling a display means to display the inspection data arranged in the tree structure by the arrangement means on a display screen; An inspection data management device comprising:

2. In a method for managing inspection data, a plurality of infrastructure structures, which are inspection objects installed in various locations, are inspected and the inspection data obtained is managed, a receiving process for receiving, as the inspection data, information including numerical values ​​input for each of the plurality of inspection objects corresponding to a plurality of classification items such as the facility name, installation area, installation year, bridge length, most recent inspection year, evaluation category that quantifies the evaluation status at the time of the most recent inspection, and the status of measures regarding the presence or absence of measures such as repair, maintenance, and improvement, which are assigned to the inspection object; a storage step of storing and holding the inspection data of the plurality of inspection objects received in the receiving step in a storage means; a clustering step of clustering the numerical values ​​of the inspection data corresponding to at least the installation year, the bridge length, the inspection year, and the judgment category among the inspection data of the plurality of inspection objects stored and held in the storage step into a plurality of ranges previously set for each of the installation year, the bridge length, the inspection year, and the judgment category, assigning indexes to the clusters, and storing and holding the clusters in the storage means; a tree formation process for arranging the classification items in a desired tree structure in the input order based on the classification items, excluding the facility name, being selectively input in sequence by an inspection data management operator in order to search for the inspection data; an arrangement step of arranging the inspection data for each of the classification items of the plurality of inspection objects, which are accepted in the acceptance step, clustered in the clustering step, and stored and held in the storage means, in the tree configuration formed in the tree formation step; a display control step of controlling a display means to display the inspection data arranged in the tree structure by the arrangement means on a display screen; A method for managing inspection data, comprising:

Images