JP7542454B2 - Construction performance data management system - Google Patents

Description

The present invention relates to a construction performance data management system that can be applied to disaster prevention measures for buildings.

Conventionally, as a prior art for systems applied to disaster countermeasures, an integrated disaster prevention system is known that integrates various disaster prevention systems installed within a given area, such as a landslide disaster system, a sabo information system, and a seismic intensity information system, and operates and manages the systems while collecting information handled by each disaster prevention system in real time and all at once (see, for example, Patent Document 1). This prior art integrates measurement information such as water levels, rainfall, and seismic intensity collected from multiple measuring means installed within a given area with GIS information and outputs the information. The output integrated information can be used when dynamically formulating disaster prevention plans such as disaster prevention and issuance of evacuation advisories, and can be reflected in future system environment development.

JP 2006-268360 A

The above-mentioned prior art is believed to be of some use in creating disaster prevention plans in areas where existing facilities are located and in developing future system environments.

However, when planning construction on new land, in order to consider a business continuity plan (BCP) or disaster prevention measures for the proposed facility, various disaster risk information based on land information for the proposed construction site must be individually referenced from scratch each time, making existing disaster prevention systems useless.

For example, when planning a new building or other facility, the risk conditions specific to each site are different, so it is necessary to refer to hazard maps and other documents to understand disaster risks, refer to a nearby boring database to understand ground conditions, and consider the necessary disaster prevention works and foundation type. This detailed process is particularly essential when making rough estimates of construction costs. Furthermore, after a facility is constructed in this way, the inspection results and repair records of the facility when it is damaged by a natural disaster, etc., are used for that facility, but they cannot be used systematically for other facilities that are expected to be damaged under similar conditions.

The present invention aims to provide a system that can be applied to disaster prevention measures during construction planning.

The present invention provides a construction performance data management system. This system has the following first to third system configurations.

[First System]
The first system makes it easy to obtain information necessary for rough estimates from a planned construction site. This system has a construction record database that accumulates construction record data held by, for example, construction companies. The construction record data includes at least the location and construction details of the building, and the construction details can include information such as countermeasures taken on the building against disaster risks and construction costs. This system also has a function that enables GIS data, including hazard maps, etc., to be linked with the construction record database for reference. This linking means that data such as the disaster risks corresponding to the locations and countermeasures in the construction record database can be used in conjunction with GIS data such as hazard maps.

When the first system acquires the planned construction site, it can extract disaster risks associated with the planned construction site from GIS data such as hazard maps, and extract construction performance data from the database that includes countermeasures taken against the extracted disaster risks. By outputting the construction performance data extracted in this way, it is possible to easily obtain information that is useful for rough estimates such as what countermeasures are necessary for the land where construction is planned, and how much the countermeasures will cost, making it easier to visualize the total costs required for the construction plan.

According to the first system, past construction records that match multiple conditions, such as facility use, scale (floor height, total floor area, etc.), expected hazard conditions (expected flood depth, type of landslide, expected maximum seismic intensity, etc.), foundation type (pile length, etc.), and zoning, can be automatically extracted, and estimates and design information can be displayed. In addition, inspection results and repair records of facilities that have actually been affected by a similar disaster can be automatically extracted from a construction record database based on the expected hazard information, and presented as a proposed plan.

[Second System]
The second system makes it easier to obtain information necessary for a rough estimate from a specific disaster risk (expected flood depth, expected seismic intensity, liquefaction risk, etc.). The second system also has a construction record database similar to the first system. The second system also has a function that enables linkage with GIS data including hazard maps, etc. In the case of the second system, information on what disaster risks a building to be constructed needs measures against is acquired as a risk requiring measures. Then, construction record data including the construction content of countermeasures taken on land associated with the disaster risk requiring measures on GIS data such as hazard maps is extracted from the database. By outputting the construction record data extracted in this way, it is possible to easily obtain information useful for a rough estimate, such as what countermeasures have been taken on the actual land and how much the countermeasures will cost, simply by assuming the disaster risk of the land requiring measures for the building to be constructed, and it becomes easier to imagine the total cost required for the construction plan.

According to the second system, when a specific disaster risk (expected flood depth, expected seismic intensity, liquefaction risk, etc.) is specified, it is possible to extract construction records on land with that risk. Furthermore, the construction record database can be linked and registered with records of damage suffered after construction and restoration work, making it possible to list damage caused to buildings in actual disasters. As a result, if the planned construction site is determined to be land with a disaster risk, construction records including countermeasures on similar land conditions can be used as conditions for selecting countermeasures, and the adopted countermeasures can be compared with damage records and repair records to determine the optimal countermeasure specifications.

[Third System]
The third system compiles statistics on the construction performance data accumulated so far when disaster prevention works are selected and specified in advance, and presents the results in association with GIS data. The third system has a construction performance database like the first and second systems. In addition, the third system has a function that enables linkage with GIS data including hazard maps. In addition, in the case of the third system, when a selected countermeasure work specified from the countermeasure works necessary for disaster risk is acquired, the construction content related to the selected countermeasure work can be extracted from the database. This makes it easy to check what kind of construction work has actually been adopted as the selected countermeasure work. Furthermore, the third system can display these statistical data (adoption rate of countermeasure work, average countermeasure work cost per square meter, minimum, maximum, and average countermeasure work scale (waterstop height, seismic isolation device specifications, amount of chemical injection, etc.)) on a map in the form of a contour diagram, heat map, etc. This makes it possible to visualize on a map the numerical distribution of construction results, such as the cost of countermeasures and the adoption rate of each type of countermeasure. When selecting potential construction sites in the future, it is possible to estimate the costs required for disaster countermeasures, which can be useful in planning the selection of the most suitable construction site.

The present invention provides a system that can be applied to disaster prevention measures during construction planning.

FIG. 1 is a block diagram showing a configuration of a construction performance data management system 100. 1 is a diagram showing an example of the configuration of construction record data accumulated and recorded in a construction record database 110. FIG. 1 is a flowchart showing an example of a procedure of system processing (1). FIG. 1 is a schematic diagram showing an example of disaster risk extraction. FIG. 13 is a schematic diagram showing an example of item selection and extraction result output. 13 is a flowchart showing an example of a procedure of system processing (2). FIG. 13 is a schematic diagram showing an example of input of risk information requiring measures and output of data extraction results. 13 is a flowchart showing an example of a procedure of system processing (3). This is an overview diagram showing an example of inputting disaster prevention construction information, extracting construction performance data, and outputting statistical data associated with topographical map data.

The following describes an embodiment of the present invention with reference to the drawings. In the following embodiment, a preferred example of a construction performance data management system is given, but the present invention is not limited to the illustrated example.

[System configuration example]
Fig. 1 is a block diagram showing the configuration of a construction record data management system 100. In Fig. 1, elements related to the construction record data management system 100 are also shown together with the block configuration of the construction record data management system 100.

The construction performance data management system 100 has a construction performance database 110. In the construction performance database 110, past construction performance data held by, for example, the construction company that is the owner of this system 100, or the user, operator, manager, etc. of this system 100 is recorded and accumulated in a specified data format. Examples of construction performance data include, but are not limited to, disaster prevention measures adopted in the past, construction costs, facility specifications, countermeasure work specifications, customer satisfaction and evaluations, etc. An example of the configuration of the construction performance database 110 will be described further below using another drawing.

The construction performance data management system 100 can be linked to GIS data 120. The GIS data 120 can be, for example, an external system that is publicly available, or can be constructed independently. In this system 100, data such as a hazard map 122, a use zone 124 in urban planning, and ground information 126 provided by the GIS data 120 can be used. Examples of the available hazard map 122 include a map data representation of the distribution of landslide warning areas, flood inundation expected areas, tsunami inundation expected areas, expected maximum seismic intensity, and liquefaction risk. Examples of the use zone 124 in urban planning include a map data representation of the classification of a first-class low-rise residential area, a first-class medium- and high-rise residential area, a commercial area, a semi-industrial area, and an industrial area. Examples of the ground information 126 include a map data representation of information such as topography classification, boring data, soil quality of the surface ground, landslide topography, old topography, and past land use conditions. Note that the GIS data 120 may also include other data.

The construction performance data management system 100 has, for example, a management control unit 130 in its central part. The management control unit 130 can be, for example, a general-purpose server-type computer, a personal computer, or a workstation-type computer. The management control unit 130 has, as functional elements, an input processing unit 132, an output processing unit 134, a data linking unit 136, a data extraction unit 138, a calculation unit 140, and the like. These functional elements can be realized, for example, by the hardware resources of the management control unit 130, or by software processing using these.

For example, a terminal device 150 is connected to the management control unit 130, and the terminal device 150 is a display device such as a display 152, an input device such as a keyboard 154 and a mouse 156, and an output device 158 such as a printer. Note that if the management control unit 130 is a server-type computer, the terminal device 150 may be a remote client computer.

To give a brief overview of the functional elements of the management control unit 130, the input processing unit 132 processes signals input from the terminal device 150 and provides them for processing within the management control unit 130. Conversely, the output processing unit 134 processes signals output to the terminal device 150 and provides them for processing in the terminal device 150. The data linking unit 136 enables linking with the GIS data 120. In particular, the system 100 can perform processing to associate the construction record database 110 and the GIS data 120 for use. The processing by the data linking unit 136 will be described further below with specific examples.

The data extraction unit 138 performs processing to extract necessary data based on the construction performance database 110 and the GIS data 120 that are associated by the data linking unit 136. The extracted data can be provided, for example, by outputting it from the output processing unit 134 to the terminal device 150, or further provided to the calculation unit 140 within the management control unit 130. The processing by the data extraction unit 138 will be described further below with a specific example.

The calculation unit 140 performs calculation processing using, for example, the data extracted by the data extraction unit 138. The results of the calculation processing can be provided, for example, by outputting them from the output processing unit 134 to the terminal device 150. Note that the processing by the calculation unit 140 will be described further below with a specific example.

[System Update]
The construction record data management system 100 of this embodiment is constructed from the above configuration, and as shown in Fig. 1, this system 100 appropriately updates the construction record database 110 and the GIS data 120. In other words, construction record data is updated and added to the construction record database 110 after the fact. For example, data such as the addition of new construction records, follow-up records for each facility, damage history and damage information after the completion of the facility, maintenance records for each facility, and repair work records after the facility is damaged are appropriately added and updated to the construction record database 110.

The GIS data 120 is updated and supplemented by external organizations, for example. For example, the hazard map 122 is updated and supplemented when the map is redeveloped. The urban planning zoning 124 is updated and supplemented when administrative changes are made to the urban plan. Furthermore, new boring data and the like are added and updated as needed for the ground information 126.

[Construction performance database]
2 is a diagram showing an example of the configuration of the construction record data accumulated and recorded in the construction record database 110. The construction record data management system 100 can be operated by constructing the construction record database 110. In addition, by updating the construction record database 110 as described above, the usefulness can be further improved.

The construction record database 110 is broadly composed of input data DI and automatically calculated data DC, for example. As shown in the left column of FIG. 2, the input data DI includes various data indicating the construction details such as the facility name, location information (latitude and longitude, address), total construction cost, scale, and countermeasure work, of which the scale further includes information on the legal floor area and number of above-ground floors, and the countermeasure work further includes information on the type, construction method/manufacturer, etc., and countermeasure work cost. When building the construction record database 110, construction companies input past construction record data according to these formats.

The automatically calculated data DC includes data on the proportion of countermeasure construction costs, such as the countermeasure construction cost per legal floor area (yen/ ^m2 ), the countermeasure construction cost per number of above-ground floors (billion yen/floor), and the proportion (%) of the countermeasure construction cost in the total construction cost. These automatically calculated data DC are automatically calculated based on the input data DI, and are recorded in the construction performance database 110 in association with the facility name. Alternatively, the automatically calculated data DC may be dynamically calculated using the input data DI at the required timing.

Next, an example of how the construction performance data management system 100 can be used will be described. For example, when a user specifies/inputs some conditions, the construction performance data management system 100 can execute the necessary processing internally and return the results to the user. The management control unit 130 of the construction performance data management system 100 can execute multiple processes listed below according to various usage patterns of users.

[System Processing (1)]
3 is a flowchart showing an example of the procedure of the system process (1) executed by the management control unit 130 of the construction performance data management system 100. This system process (1) can be executed, for example, when the construction planning site where the user plans to construct the facility has been decided. The procedure will be described below along with the example.

Step S100: The management control unit 130 executes a planning condition input process. In this process, information on the construction plan site is acquired, for example, through the terminal device 150. In addition, specifications of the planned facility, such as its use and size, are acquired as appropriate. The terminal device 150 is operated, for example, by a user of the present system 100. The user inputs information on the construction plan site where the facility is to be constructed using the terminal device 150. The information on the construction plan site may be specified, for example, by specifying a position on a map displayed on the display 152 (clicking the mouse 156, specifying a range, etc.), or the address or latitude and longitude may be entered using the keyboard 154. In addition, the specifications of the planned facility may be selected, for example, from options displayed on the screen of the display 152, or entered into an input field using the keyboard 154. In any case, when the planning conditions, such as information on the construction plan site and specifications of the planned facility, are acquired, the management control unit 130 proceeds to the next step S102.

Step S102: The management control unit 130 executes a GIS data reference process. In this process, the data linking unit 136 of the management control unit 130 references the hazard map 122 of the GIS data 120, and extracts information such as the type and degree of risk of disaster (hazard) anticipated at the acquired construction site. For example, if the construction site is "No. XX, C-cho, B-city, A-prefecture," the various disaster risks anticipated at the construction site (flood inundation risk, tsunami inundation risk, landslide risk, etc.) and their degrees of risk are automatically extracted from the hazard map 122.

[Example of disaster risk (hazard) extraction]
4 is a schematic diagram showing an example of disaster risk extraction associated with the execution of step S102. As described above, when the construction site is input from the terminal device 150, the management control unit 130 refers to the GIS data 120 via the data linking unit 136, and extracts various disaster risks and their degrees of danger assumed for the current construction site (shown as "Planned site" in the figure) from the various hazard maps 122a to 122g. In this extraction example, "tsunami inundation risk of 3 to 5 m" is extracted from the tsunami hazard map 122a, "flood inundation risk of 1 to 2 m" is extracted from the flood hazard map 122b, and "no landslide risk" is extracted from the landslide hazard map 122c. Note that from the other hazard maps 122d to 122g, "debris flow risk,""steep slope collapse risk,""landsliderisk,""expected seismic intensity," etc., expected for the proposed construction site may be extracted depending on the land, but these are not shown in the figure as they were not extracted for the proposed construction site this time. Also, although not shown, the management control unit 130 automatically extracts land conditions such as the use zoning and topographical classification of the proposed construction site from the use zoning 124 in the city plan, and then executes step S104.

[Figure 3: System Processing (1) Continued]
Step S104: Next, the management control unit 130 executes an item selection process. In this process, the disaster risk, its hazard level, and land condition information automatically extracted in the previous step S102 are output from the output processing unit 134 to the terminal device 150 and returned, thereby enabling the user to perform any item selection operation. The user can select a desired item from, for example, the specifications of the planned facility displayed on the display 152, the returned disaster risk, hazard level, land condition, etc. Note that the extracted data is returned to the terminal device 150 in the previous step S102, and here, only the input of the item selection operation may be accepted. When the management control unit 130 acquires the selected item from the terminal device 150, it next executes step S106.

Step S106: The management control unit 130 executes a construction performance data extraction process. In this process, when the data linking unit 136 searches the construction performance database 110, the data extraction unit 138 extracts construction performance data that matches the conditions for the items selected in the previous step S104. Note that the search of the construction performance database 110 may be performed by the data extraction unit 138. Then, step S108 is executed.

Step S108: The management control unit 130 executes a data output process. In this process, the results of the construction performance data extracted in the previous step S106 are output to the terminal device 150. In response to this, the terminal device 150 displays the extracted results of the construction performance data on the display 152, so that the user can confirm them. The extracted results can also be printed out from an output device 158 such as a printer.

[Item selection and extraction result output example]
FIG. 5 is a schematic diagram showing an example of the selection of items and the output of the extraction results associated with the execution of steps S104 and S106. As shown in the upper left column in FIG. 5, various disaster risks automatically extracted for the current construction project site can be displayed on the display 152 of the terminal device 150, etc., so that the user can check them. The user can then perform an item selection operation on the display 152 using, for example, the mouse 156. In this example, all of the items of the automatically extracted expected disaster risks, "tsunami inundation risk of 3 to 5 m,""flood inundation risk of 1 to 2 m," and "no landslide risk," are selected (check marks in the figure). In addition, from the registered information of the construction performance database 110 displayed on the display 152, such as "use,""structure,""total construction cost,""scale," etc., the item of the use zoning classification "factory" to which the current construction project site corresponds is selected (check mark in the figure). Although not shown here, if there is an item of topography classification in the land conditions, it is also possible to select that item.

Next, as shown in the right column of Figure 5, the management control unit 130 extracts construction history data that matches the conditions for the selected items. In this extraction example, countermeasures corresponding to the selected item conditions of "tsunami inundation risk of 3-5m," "flood inundation risk of 1-2m," and "no landslide risk" have been carried out in the past, and two examples of construction history data for facilities constructed on land zoning that corresponds to "factory" are extracted (indicated as "OUTPUT" in the figure).

Then, as shown in the lower left column of FIG. 5, the extraction results are output to the terminal device 150 and displayed on the display 152. In this example, "countermeasure construction costs," "damage/repair history," etc. linked to the facilities in the two examples of construction history data are displayed. By using this construction history data as reference information, the user can know the scale of countermeasure construction costs actually adopted in facilities with similar conditions to the facility to be constructed this time. In addition, by appropriately referring to existing estimates, adopted countermeasure construction and technology, design drawings, completion drawings, etc. linked to the construction history data, it can be used as reference information when creating rough estimates and outline plans, allowing efficient construction estimates and plans.

[System Processing (2)]
Next, Fig. 6 is a flowchart showing an example of the procedure of system process (2). This system process (2) can be used, for example, when a user specifies a specific disaster risk in advance and uses the construction performance data as a reference for future construction plans. The procedure will be described below along with the example.

Step S200: The management control unit 130 executes a risk condition input process. In this process, information on risks requiring countermeasures is acquired, for example, via the terminal device 150. The information on risks requiring countermeasures is information on what disaster risk countermeasures are required for a facility (structure) that is planned to be constructed in the future. The information on risks requiring countermeasures can be selected by the user from options displayed on the display 152 (e.g., by clicking the mouse 156), or can be entered into an input field using the keyboard 154. In addition, at this time, the user can also specify the degree of danger in detail for each risk type as information on risks requiring countermeasures. In either case, once the information on risks requiring countermeasures has been acquired, the management control unit 130 proceeds to the next step S202.

Step S202: The management control unit 130 executes a GIS data reference process. In this process, the data linking unit 136 of the management control unit 130 references the hazard map 122 of the GIS data 120, picks out land associated with the acquired types of risks requiring countermeasures and conditions such as the degree of danger for each risk, and proceeds to the next step S206.

Step S206: The management control unit 130 executes a construction history data extraction process. In this process, the data extraction unit 138 searches for construction history data whose construction details include countermeasure work carried out on the land picked up in the previous step S202, and extracts it from the construction history database 110. Then, step S208 is executed.

Step S208: The management control unit 130 executes a data output process. In this process, the results of the construction performance data extracted in the previous step S206 are output to the terminal device 150. In response to this, the terminal device 150 displays the extracted results of the construction performance data on the display 152, so that the user can confirm them. The extracted results can also be printed out from an output device 158 such as a printer.

[Example of information input and extraction result output]
FIG. 7 is a schematic diagram showing an example of input of risk information requiring countermeasures and output of data extraction results associated with execution of system process (2). As shown in the upper left column of FIG. 7, the input of risk information requiring countermeasures can be selected and specified by the user, for example, using the mouse 156, from among options displayed on the display 152 of the terminal device 150. In this example, the assumed risks requiring countermeasures include "flood inundation risk" and "tsunami inundation risk," and the risk level of "flood inundation risk" is selected as "1.0 to 2.0 m," and the risk level of "tsunami inundation risk" is selected as "2.0 to 5.0 m" (check mark in the figure). In this example, "landslide risk" is not selected (no check mark in the figure). Although not shown here, if disaster risks other than those mentioned above and their risk levels are displayed as options, it is also possible to select from such options. The selected risk information is input from the terminal device 150 to the management control unit 130.

Next, as shown in the right column of FIG. 7, the management control unit 130 picks out land that is associated on the GIS data 120 with a disaster risk that corresponds to the input risk information, and extracts construction history data for such land. In this extraction example, three examples of construction history data for land that corresponds to a risk requiring countermeasures on the tsunami hazard map 122a and the flood hazard map 122b are extracted (shown as "OUTPUT (1) to (3)" in the figure). Note that, although the landslide hazard map 122c is not referenced in this example, if the risk requiring countermeasures information includes "landslide risk," the landslide hazard map 122c will also be referenced (the corresponding hazard map will be referenced in the same way if any other type of risk requiring countermeasures is selected).

Then, as shown in the lower left column of FIG. 7, the extraction results are output to the terminal device 150 and displayed on the display 152. In this example, three examples of construction performance data, "(1) XX Factory," "(2) △△ Warehouse," and "(3) XX Center," are displayed as facility names, along with "Legal Floor Area," "Story Height," "Flood Prevention Work," "Construction Costs," "Subsidy Application Documents," "Disaster/Repair History," and so on, linked to each facility. By using this construction performance data as reference information, the user can easily imagine the scale of the countermeasure construction costs actually adopted in a facility where countermeasure construction work has been implemented against the assumed risks, and can efficiently make construction estimates and plans.

In addition, the construction record database can be linked to and registered with records of damage caused after construction and restoration work, making it possible to list damage caused to buildings in actual disasters. This makes it possible to use construction records, including countermeasures on similar land conditions, as a criterion for selecting countermeasures, if the planned construction site is determined to be on land with a risk of disaster. It is also possible to compare adopted countermeasures with past damage records and past repair records, which can be used as a criterion for determining the optimal countermeasure specifications.

[System Processing (3)]
8 is a flowchart showing an example of the procedure of system process (3). For example, when a user selects a disaster prevention work from a list, this system process (3) calculates statistical data such as the adoption rate of the work, the average cost of the work, and the average scale of the work (waterstop height, specifications of the seismic isolation device, amount of chemical solution injected, etc.) according to the expected risk level (e.g. expected flood depth, expected seismic intensity, degree of liquefaction risk, etc.), and can display the data on a map in the form of a contour diagram or heat map. The procedure will be described below along with the example.

Step S300: The management control unit 130 executes a disaster prevention work input process. In this process, information on disaster prevention work is acquired, for example, through the terminal device 150. Information on disaster prevention work is information on what kind of disaster prevention work should be applied to a planned facility, for example, when planning the construction of a facility. Information on disaster prevention work can be selected by the user from options displayed on the display 152 (e.g., by clicking the mouse 156), or can be entered into an input field using the keyboard 154. In addition, at this time, the user can specify in detail the expected risk level conditions for each type of disaster prevention work as information on disaster prevention work. In either case, once the information on disaster prevention work is acquired, the management control unit 130 proceeds to the next step S302.

Step S302: The management control unit 130 executes a construction performance data extraction process. In this process, the data linking unit 136 of the management control unit 130 refers to the construction performance database 110, and the data extraction unit 138 extracts construction performance data in which the disaster prevention work acquired in the previous step S300 has been adopted. Then, the process proceeds to the next step S304.

Step S304: The management control unit 130 executes data statistical processing. In this process, the calculation unit 140 executes statistical processing on the construction performance data extracted in the previous step S302, and calculates the statistical data as described above. Then, step S306 is executed.

Step S306: The management control unit 130 executes a GIS data reference process. In this process, the data linking unit 136 of the management control unit 130 references the GIS data 120 and obtains topographical map data from, for example, the ground information 126. Then, step S308 is executed.

Step S308: The management control unit 130 executes a data output process. In this process, the statistical data calculated in the previous step S304 is associated with the topographical map data and output to the display 152 of the terminal device 150, etc. At this time, the statistical data includes the location and details of the disaster prevention work linked with the construction performance data, so that, for example, the statistical values for the disaster prevention work can be visualized on the topographical map data and displayed in the form of a contour diagram or heat map.

[Examples of information input and data output]
FIG. 9 is a schematic diagram showing an example of input of disaster prevention work information and extraction of construction performance data accompanying execution of system process (3), and output in which statistical data is associated with topographical map data. As shown in the upper left column of FIG. 9, the input of disaster prevention work information can be selected and specified by the user, for example, using the mouse 156, from among options displayed on the display 152 of the terminal device 150. In this example, "flood inundation prevention work" is selected as the disaster prevention work, and "waterstop wall" is selected as the type (check mark in the figure). In this example, the expected risk level (expected inundation depth) condition of "waterstop wall" is not specified, but the user can appropriately specify detailed conditions such as "H = 0.0 to 1.0 m", "H = 1.0 to 3.0 m", and "H = 3.0 m or more" as the expected inundation depth of the expected risk level. In this example, "waterstop wall" is selected, and other measures such as "emergency power supply equipment" and "land raising" are not selected, but these can also be selected by the user as desired.

Although the other conditions "Landslide prevention works", "Tsunami inundation prevention works", and "Earthquake prevention works" have not been selected (no check marks in the figure), the user can select these as well if desired. Although not shown here, if disaster prevention works other than those mentioned above, their types, and risk levels are displayed as options, it is also possible to select from such options. The selected risk information is input from the terminal device 150 to the management control unit 130.

Next, as shown in the lower left column of Figure 9, the management control unit 130 extracts construction history data from the construction history database 110 in which the input disaster prevention work (in this case, "waterstop wall" as a "flood prevention work") has been adopted. The extraction results include construction history data for all facilities that include the construction content of "flood prevention work = waterstop wall", as well as registered information such as the legal floor area, floor height, construction costs, subsidy application documents, damage/repair history, etc. linked to each facility.

The management control unit 130 also performs statistical processing on the construction details that are the results of the extraction described above, and calculates statistical data such as the countermeasure cost per legal floor area and the adoption rate of countermeasure work (waterstop walls). The results of these statistical processing can be output and displayed in the form of image data as a "countermeasure cost contour map per legal floor area" as shown in the upper right column of Figure 9, or as a "countermeasure work (waterstop walls) adoption rate heat map" as shown in the lower right column of Figure 9.

[Statutory floor area countermeasure cost contour map display content]
In the contour diagram shown in the upper right column of Figure 9, the gray dots (circles) on the map represent the locations (distribution) of facilities that use water cutoff walls as disaster prevention construction, and the curves surrounding the dots represent contour lines of the countermeasure costs per legal floor area. The shade of the area surrounded by the contour lines represents the magnitude of the countermeasure costs, with the darker areas representing higher countermeasure costs per legal floor area and the lighter areas representing lower countermeasure costs.

[Heat map showing the adoption rate of countermeasures (waterstop walls)]
The heat map shown in the lower right column of Figure 9 shows the distribution of adoption rates of countermeasure works (waterstop walls) by standard regional mesh on the map. The shade of the mesh color indicates the degree of adoption rate, with darker areas indicating a higher adoption rate and lighter areas indicating a lower adoption rate, and no color (white map) areas indicating that countermeasure works (waterstop walls) have not been adopted.

In this way, by statistically processing construction data on cases where disaster prevention measures have been adopted and visualizing and displaying it in the form of contour diagrams and heat maps, when selecting potential construction sites, the costs required for disaster prevention measures can be easily estimated from the map. This makes it possible to select the optimal construction site according to the cost plan.

According to the construction performance data management system 100 of the above-described embodiment, the following advantages can be obtained.
(1) In the past, construction companies had accumulated data on their construction records, but when planning a new facility such as a building, the disaster risks specific to the proposed construction site were checked using hazard maps, etc., and precedents of construction records were examined before considering the necessary disaster prevention works individually, so the data was not used systematically. In this regard, according to the present system 100, when a proposed construction site is input, the disaster risks associated with the land are automatically determined, and the contents of disaster prevention works corresponding to similar cases can be easily referenced from existing construction records, and information such as the cost of the countermeasures and subsequent maintenance records can also be obtained, making it extremely convenient in that the information necessary for a rough estimate can be easily obtained.

(2) Furthermore, in the past, even if it was known in advance that there was a disaster risk at a planned construction site, there was no indicator of what countermeasures were available and what countermeasures should be considered. However, with this system 100, when a disaster risk is input, the construction details of countermeasures are automatically extracted from the construction history of land with that risk, so countermeasures can be easily selected by referring to the extracted results.

(3) In addition, in the past, when selecting a construction site, there was no information that provided comprehensive information such as the cost of countermeasures against disaster risks on the land or the types of countermeasures that are commonly adopted. However, with this system 100, by simply selecting disaster countermeasures and their details, statistical data such as the cost of countermeasures and adoption rates by region can be visualized and displayed on a map, making it easy to select an appropriate construction site based on a balance of budgets, etc.

The present invention is not limited to the above-described embodiment, and can be implemented in various modified forms.
As already mentioned, the construction record data management system 100 can be constructed on the cloud with the management control unit 130 as a server type. In this case, a user who has been granted the usage authority can access the construction record data management system 100 from a remote location and obtain the output of the extraction result.

The contents of the construction history database 110 may include not only the data shown in FIG. 2, but also other input data DI and its automatically calculated data DC. In addition, the facilities that can be registered in the construction history database 110 may include a variety of buildings, such as commercial facilities, attraction facilities, and detached houses.

In system processing (1), for example, when a construction planning site is input in step S100, steps S102, S106, and S108 may be executed in real time to extract all construction records before item selection (narrowing down). Then, when the user narrows down the conditions by selecting items while checking the extraction results, the output of the extraction results may be updated in real time with the conditions selected in step S104.

In system processing (2), for example, when a major category of risk requiring countermeasures (such as "landslide risk," "flood inundation risk," or "tsunami inundation risk") is specified in step S200, all construction records before the risk level is specified (narrowed down) in detail may be extracted. Then, when the user narrows down the conditions such as risk level by selecting an item while checking the extraction results, the output of the extraction results may be updated in real time according to the conditions selected for the item each time.

In system processing (3), the processing from steps S302 to S308 is updated as needed in response to the input conditions in step S300, and when the user changes the input conditions on the screen of display 152, the display of the contour diagram and heat map may be updated in real time accordingly.

All of the other aspects shown in the figures in the embodiments are merely preferred examples, and it goes without saying that the present invention can be implemented in a suitable manner by adding various elements to the basic aspects or by substituting some parts.

REFERENCE SIGNS LIST 100 Construction record data management system 110 Construction record database 120 GIS data 130 Management control unit 136 Data linking unit 138 Data extraction unit 140 Calculation unit 150 Terminal device

Claims (8)

A construction record database is provided that accumulates construction record data including at least the location and construction details of the building,
A data linking means for linking the GIS data with the construction record database so that the data can be referenced;
a planned site-specific extraction means for extracting disaster risks associated with the planned construction site from the GIS data when the planned construction site is acquired, and extracting construction record data including countermeasure works for the extracted disaster risks from the construction record database;
and an output means for outputting the construction performance data which is the extraction result of the planning site-specific extraction means. In the construction performance data management system according to claim 1,
The planning area extraction means includes:
A construction performance data management system characterized by extracting from GIS data risk conditions including the extracted disaster risk type and hazard level, as well as land conditions including the zoning and topographical classification of the planned construction site, and extracting from the construction performance database construction performance data that matches specified conditions from the extracted risk conditions and land conditions. In the construction performance data management system according to claim 2,
The output means includes:
A construction performance data management system characterized in that risk conditions and land conditions extracted by the planning site extraction means are output prior to output of the construction performance data, thereby making it possible to specify risk conditions and land conditions to the planning site extraction means. A construction record database is provided that accumulates construction record data including at least the location and construction details of the building,
A data linking means for linking the GIS data with the construction record database so that the data can be referenced;
A disaster risk-specific extraction means for extracting, from the construction record database, construction record data including construction details of countermeasure works implemented on land associated on the GIS data with a disaster risk corresponding to the disaster risk requiring countermeasures for a planned construction as a countermeasure-required risk;
and an output means for outputting construction performance data which is the extraction result of the disaster risk-specific extraction means. In the construction performance data management system according to claim 4,
The disaster risk extraction means includes:
A construction history data management system characterized by extracting the risks requiring countermeasures by specifying risk conditions including the type and hazard level of disaster risk, extracting the land associated on GIS data with the disaster risk that meets the risk conditions, and extracting construction history data including countermeasures implemented on the land from the construction history database. A construction record database is provided that accumulates construction record data including at least the location and construction details of the building,
A data linking means for linking the GIS data with the construction record database so that the data can be referenced;
A construction record data management system including a countermeasure work-specific extraction means for extracting construction details related to a selected countermeasure work from the construction record data accumulated in the construction record database when the selected countermeasure work is selected from a plurality of countermeasure works that can be implemented as disaster risk countermeasures. In the construction performance data management system according to claim 6,
The countermeasure work extraction means includes:
A construction performance data management system characterized in that risk conditions including a disaster risk type and a danger level are further specified, and countermeasure works required for the disaster risk are acquired as the selected countermeasure works. In the construction performance data management system according to claim 6 or 7,
A processing means for executing statistical processing on the construction details extracted by the countermeasure work extraction means;
The construction performance data management system further comprises an output means for outputting statistical data on the construction contents, which is a processing result of the processing means, in association with the GIS data.

Images