Construction management system and construction management method

Abstract

This project includes a specific business comprising a plurality of steps. A construction management system (1) is provided with a control unit (111), a display unit (221), and a storage unit (112). The control unit (111) generates a process table for specific traffic. And (221) displaying the process table. A storage unit (112) stores past project information as a project history. The control unit (111) extracts, from the project history, information of past traffic in which the pattern of the process matches the specific traffic. The control unit (111) calculates statistical data of the extracted past traffic information. The statistical data includes delay data in past traffic relating to a delay with respect to the plan. The display unit (221) displays the statistical data including the delay data together with the process table.

Description

Technical Field

[0001] The present disclosure relates to a construction management system and a construction management method. Background Art

[0002] In construction sites such as buildings, in many cases, multiple workers (persons in charge) in charge of the project perform multiple operations in parallel. The construction manager (site agent) who manages the construction needs to understand the load status of each worker's work and the progress status of multiple operations being performed simultaneously. Based on this, the construction manager needs to take measures to maintain the quality of the work and complete all the work safely before the deadline.

[0003] The construction manager understands the load status of the workers by holding morning meetings, listening to the responsible persons for the work, and checking the daily work reports. He also inspects the work site and understands the progress of the work by visual confirmation and checking on-site photos. Based on the status thus understood, the construction manager implements construction management by adding or replacing workers, re-evaluating the work process, etc.

[0004] Prior art literature

[0005] Patent Literature

[0006] Patent Document 1: Japanese Patent Application Publication No. 2020-135098 Summary of the invention

[0007] Problems to be solved by the invention

[0008] In order to be able to appropriately judge whether it is necessary to re-evaluate the work process based on the conditions they know, construction managers need to have a certain degree of performance and experience on site. In the current situation where the construction industry's workforce is decreasing, it is necessary to cultivate construction managers who can make such appropriate judgments and perform construction management. On the other hand, a construction management system is required that allows even inexperienced construction managers to perform construction management efficiently.

[0009] The present disclosure is made to solve such a problem, and an object of the present disclosure is to provide a construction management system and a construction management method that enable even an inexperienced construction manager to efficiently perform construction management.

[0010] Means for solving problems

[0011] The construction management system disclosed in the present invention is a system for managing the construction of a project. This project includes a specific business consisting of multiple processes. The construction management system has a control unit, a display unit, and a storage unit. The control unit generates a process table for the specific business. The display unit displays the process table. The storage unit stores information about past projects as a project history. The control unit extracts information about past businesses whose process patterns are consistent with the specific business from the project history. The control unit calculates statistical data of the extracted information about past businesses. The statistical data includes delay data related to delays relative to the plan in the past business. The display unit displays the statistical data including the delay data together with the process table.

[0012] In addition, the construction management method disclosed in the present invention is a method for managing the construction of a project. This project includes a specific business consisting of a plurality of processes. The construction management method has the following steps: a generation step of generating a process table for the specific business; a display step of displaying the process table; and a storage step of storing information of past projects as a project history. The generation step includes the following steps: extracting information of past businesses whose process patterns are consistent with the specific business from the project history; and calculating statistical data of the extracted information of past businesses. The statistical data includes delay data related to delays relative to the plan in the past business. The display step includes the following steps: displaying the statistical data including the delay data together with the process table.

[0013] Effects of the Invention

[0014] According to the present disclosure, it is possible to infer which operation process may be delayed, and to analyze the cause of the delay or the impact on the process. As a result, it is possible to improve the estimation accuracy of the operation time, improve the prediction accuracy of the project completion date taking into account the operation delay, prevent operation delays caused by following up on operation processes with high delay rates, and perform construction management for strictly adhering to the delivery date. As a result, even inexperienced construction managers can efficiently perform construction management. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a diagram showing the hardware configuration of the construction management system according to the first embodiment.

[0016] Figure 2 This is a diagram showing a functional block diagram in the construction management system.

[0017] Figure 3 This is the main processing flow chart.

[0018] Figure 4 This is a flowchart of the display information generation process.

[0019] Figure 5 This is a diagram showing an example of a process table.

[0020] Figure 6 This is a diagram showing a functional block diagram in the construction management system according to the second embodiment.

[0021] Figure 7 This is the main processing flow chart.

[0022] Figure 8 This is a flowchart of the display information generation process.

[0023] Fig. 9 This is a diagram showing an example of a process table.

[0024] Fig.10 This is a diagram for explaining the calculation of the forecast days.

[0025] Fig.11 is a flowchart of the sorting process.

[0026] Fig.12 This is a diagram showing an example of a process table. DETAILED DESCRIPTION

[0027] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Hereinafter, multiple embodiments will be described, but it has been predetermined from the beginning of the application that the structures described in each embodiment will be appropriately combined. In addition, the same reference numerals are marked for the same or equivalent parts in the figures, and their descriptions will not be repeated.

[0028] <First Embodiment>

[0029] Figure 1 This is a diagram showing a hardware configuration of a construction management system 1 according to the first embodiment. The construction management system 1 is a system for managing construction of a project.

[0030] In this embodiment, it is defined that one project is composed of multiple tasks. By completing these multiple tasks, the project is completed. In addition, it is defined that each task is composed of multiple processes. By completing the operations of these multiple processes, one task is completed.

[0031] For example, in the following Figure 5 In the example, the building project is composed of multiple tasks including "preparation of execution budget", "preparation of construction plan", "preparation of safety and health documents", and "preparation of finished drawings". In addition, in addition to the preparation of these documents, the project also includes operations (tasks) at the construction site.

[0032] In this embodiment, the construction management system 1 generates and displays a process sheet for a task (hereinafter referred to as "specific task") specified by a user operating a terminal in a scheduled project or a project currently being implemented (hereinafter referred to as "this project").

[0033] exist Figure 5 In the example, the user specifies "Execute budget preparation" as a specific task, and the process table of "Execute budget preparation" generated as a result is displayed. The task (specific task) of "Execute budget preparation" is composed of multiple processes such as "Estimate request preparation", "Approval 1", and "Partner company receipt".

[0034] A person in charge (also called "operator") is assigned to each of the above-mentioned multiple processes. The person in charge can instruct the person in charge of each process, or can instruct the process itself. The person in charge (operator) of a process can be one person or multiple people.

[0035] When displaying the process table, statistical data compiled based on past process history are also displayed. The statistical data includes a delay occurrence rate (also referred to as a "delay rate") described later, thereby making it possible to analyze how often delays may occur relative to the plan.

[0036] return Figure 1 The construction management system 1 includes a server 100 and a terminal 200. The server 100 performs processing such as generating a process table. The terminal 200 is a terminal used by a construction manager (also simply referred to as a "manager") who manages the construction of the project. The construction manager grasps each business of the project to be responsible for, the load status of each person in charge in each process, and the progress status of each operation, and manages the site so that the project is completed before the deadline.

[0037] The server 100 includes a control unit 111, a storage unit 112, and a communication unit 113. These are connected via a bus so as to be able to communicate with each other. The control unit 111 is, for example, a CPU (Central Processing Unit). The storage unit 112 includes a ROM (Read Only Memory), a RAM (Random Access Memory), a non-volatile storage device (such as a HDD (Hard Disk Drive) or an SSD (Solid State Drive), etc.). The storage unit 112 stores information on past projects as a project history.

[0038] The control unit 111 reads the program stored in the ROM into the RAM and executes it to realize various functions of the server 100. The ROM stores the program that describes the processing steps of the server 100. The RAM becomes the working area when the control unit 111 executes the program, temporarily storing the program, the data when the program is executed, etc. The server 100 can be connected to the terminal 200 in a wireless or wired manner via the communication unit 113.

[0039] The terminal 200 may be, for example, a mobile terminal such as a smart phone or a tablet, or a personal computer such as a laptop computer or a desktop computer.

[0040] The terminal 200 includes a control unit (CPU) 211, a storage unit 212, a communication unit 213, an input unit 220, and a display unit 221. These are connected via a bus so as to be able to communicate with each other. The storage unit 212 may also be similarly configured to include a ROM, a RAM, and a non-volatile storage device such as a HDD or a SSD.

[0041] The control unit 211 reads the program stored in the ROM into the RAM and executes it, thereby realizing various functions of the terminal 200. The ROM stores a program describing the processing procedures of the terminal 200. The terminal 200 can be connected to the server 100 via the communication unit 213.

[0042] The input unit 220 receives input from the user. The input unit 220 is, for example, a touch panel, but may also be a keyboard or a mouse. The display unit 221 displays various information. The display unit 221 is, for example, a liquid crystal display or a display. The display unit 221 displays the process table generated by the control unit 111, etc.

[0043] The construction management system 1 may be a device that integrates the server 100 and the terminal 200 used by the manager. In this case, the display unit (display) of the device displays the process table generated by the control unit (CPU) of the device.

[0044] Figure 2 1 is a diagram showing a functional block diagram in the construction management system 1. The control unit 111 can execute the processing performed by the extraction unit 121, the statistical unit 122, and the generation unit 123.

[0045] The storage unit 112 stores information of past projects as a project history. In addition, the storage unit 112 stores information of this project as project information.

[0046] Past works are works that were carried out in the past, and each time a work is carried out, information thereof is accumulated in the storage unit 112. This work is a work that is scheduled to be carried out or is being carried out, and is a work for which a process table is generated and displayed by the construction management system 1.

[0047] The construction management system 1 generates a process table for the work (=specific work) designated by the user (manager) using the terminal 200 from the input unit 220 for the current project, and displays the generated process table. Figure 5 In the example, "Execute budget preparation" is equivalent to "specific business".

[0048] The current project information includes the project name, multiple tasks in the project, multiple processes in each task, and the planned days for each task and each process. In the past project history, it also includes delay information such as the actual days relative to the planned days and the presence or absence of delays and the number of days of delay in each process or task. In addition, the delay information can be calculated based on the planned days and the actual days.

[0049] The extraction unit 121 obtains the past project history and the current project information from the storage unit 112, and obtains the information of the specific business specified by the input unit 220. The extraction unit 121 extracts the information of the business whose process pattern is consistent with the specific business (hereinafter referred to as "past business") from the past project history. The statistical unit 122 calculates the statistical data (delay rate, etc.) of the extracted information of the past business. The details of the extraction of the information of the past business and the calculation of the statistical data will be described later.

[0050] The generation unit 123 generates display information (process table, statistical data) based on the current process information and statistical data. The display unit 221 displays the display information. These processes are described in detail below using a flowchart.

[0051] Figure 3 This is a flowchart of the main process. The process shown in this flowchart is started, for example, when a user (manager) designates a specific task from the input unit 220. Hereinafter, a "step" is simply referred to as "S".

[0052] When the main process starts, in S101, the server 100 obtains current construction information and past construction history from the storage unit 112. In S102, the server 100 extracts information of past operations whose process pattern matches the specific operation designated by the user from the past construction history.

[0053] Next, use Figure 5 Provide specific instructions. Figure 5 This is a diagram showing an example of a process table. This project includes "Execution budget preparation", "Construction plan preparation", "Safety and health document preparation" and "Completion drawing preparation" as tasks. The user (manager) specifies (selects) "Execution budget preparation" (specific task) among these tasks and prepares a process table.

[0054] "Executive budget preparation" is implemented through multiple processes. As a process, after the person in charge performs "estimate request preparation", the supervisor performs "approval 1". In addition, after the person in charge performs "instruction preparation" and "drawing preparation", the supervisor performs "approval 2".

[0055] Furthermore, after the supervisor has performed "Approval 1" and "Approval 2", the supplier receives the estimate request, instructions, and drawings (the "received by the supplier" process). The person in charge of the supplier conducts the "site investigation" and then "prepare the estimate". The person in charge of preparing the execution budget receives the estimate from the person in charge of the supplier (the "received estimate" process) and then "prepare the execution budget". After "prepare the execution budget", the supervisor performs "Approval 3", and the "prepare the execution budget" business is completed.

[0056] The server 100 extracts information about past operations that match the above-mentioned process pattern from the past engineering history. Basically, operations that match multiple processes (estimate request document preparation to approval 3) of "executing budget document preparation" can be extracted from the past engineering history, and operations that match a portion of the multiple processes can also be extracted from the past engineering history. For example, it is possible to extract operations that do not match the process pattern. Figure 5 Among the multiple processes shown, the business of "preparing an estimate request form" and the process of "approval 1" and all other processes that match are taken as past business, and the business (process) of only "preparing specifications" that matches can also be extracted as past business.

[0057] return Figure 3 In S103, the server 100 calculates statistical data of the extracted information of past business. The statistical data includes delay data in past business. Delay data is data related to delay relative to the plan. Specifically, the delay data includes the delay occurrence rate (delay rate) of past business and the delay occurrence rate of each process of the past business. Next, in S104, the server 100 sets the planned days for a specific business and the planned days for each process of the specific business.

[0058] exist Figure 5 In the example, the column of "Execute Budget Preparation" (specific business) shows that the calculated delay rate = 3.0% and the set planned days = 19 days (it is planned to complete the processes of estimate request preparation to approval 3 in 19 days). Thus, it is shown that the planned days for executing budget preparation, which is a specific business, is 19 days, and the delay rate of the past business whose process pattern is consistent with the process pattern of executing budget preparation is 3.0%.

[0059] For example, suppose 100 businesses are extracted ( Figure 5 Such an estimate request form is prepared ~ approved 3 such process patterns) as past business. Among them, when 97 businesses were completed within the planned days (19 days) (the actual days were less than the planned days), and 3 businesses were completed beyond the planned days (19 days) (the actual days exceeded the planned days), the delay rate was calculated as 3.0% (= 3 / 100).

[0060] Similarly, the delay rate and the planned days are also displayed in the column of each process of "Executing Budget Preparation" (specific business). For example, the column of the process of "Estimate Commission Preparation" displays the delay rate = 5.0% and the planned days = 3.0 days (scheduled to be completed in 3 days). Thus, it is shown that the planned days for the process of "Estimate Commission Preparation" in the execution of budget preparation are 3.0 days, and the delay rate of estimate commission preparation in past business is 5.0%. For example, among 100 past businesses, when the work is completed within the planned days (3 days) in 95 estimate commission preparations, and the work is completed beyond the planned days (3 days) in 5 estimate commission preparations, the delay rate is calculated to be 5.0% (=5 pieces / 100 pieces).

[0061] In addition, the column of the process "Manufacture of Instructions" shows that the delay rate = 3.0% and the planned days = 2.0 days. This shows that the planned days for the process "Manufacture of Instructions" in the execution of budget preparation is 2.0 days, and the delay rate of the manufacture of instructions in the past business is 3.0%. For example, among 100 past businesses, when the work was completed within the planned days (2 days) in 97 manual productions and completed in more than the planned days (2 days) in 3 manual productions, the delay rate is calculated to be 3.0% (= 3 / 100).

[0062] In addition, as past businesses whose process patterns match those of a specific business, in addition to extracting past businesses that match all or part of the processes of a specific business, past businesses that match only one of the processes of a specific business may also be extracted. Figure 5 In this case, the process of making instructions can be extracted from the past engineering history, and the delay rate of the extracted process of making instructions can be calculated, and displayed in the "Instruction Making" column of the process table. Similarly, for example, past business consistent with "Drawing Making" can be extracted. In this case, the process of making drawings can be extracted from the past engineering history, and the delay rate of the extracted process of making drawings can be calculated, and displayed in the "Drawing Making" column of the process table. In this way, it is also possible to extract from the past engineering history for individual processes such as "approval", "on-site investigation", and "estimate making", and to make statistical data such as delay rates.

[0063] return Figure 3 In S105, the server 100 performs display information generation processing (using Figure 4The server 100 generates display information (statistical data and process table) in step S106, and the main process is terminated. The display unit 221 displays the statistical data (including delay data) together with the process table.

[0064] Figure 4 2 is a flowchart of the display information generation process. When the display information generation process starts, in S201, the server 100 obtains statistical data and current project information.

[0065] In S202, the server 100 sets the display method of the delay rate of past business based on the delay rate (delay occurrence rate) of past business. In S203, the server 100 sets the display method of the delay rate of each process based on the delay rate of the past business.

[0066] Example Figure 5 The display unit 221 displays the delay rate of past operations in different ways according to the delay rate of past operations. The display unit 221 displays the delay rate of each process in past operations in different ways according to the delay rate of the process.

[0067] Specifically, when the delay rate of the past business or each process of the past business is 5% or more, the delay rate is displayed in an emphasized manner. Figure 5 In the example, the delay rates of the processes "Estimate Request Form Preparation" and "Drawings Preparation" are both 5% or more (5%). Therefore, the "Delay Rate: 5.0%" is highlighted by a rectangle surrounding it. Alternatively, the "Delay Rate: 5.0%" can be highlighted by displaying it in red.

[0068] On the other hand, the delay rate of the task of "preparing the budget" and other processes such as "preparing the specification", "approval 1", "approval 2", and "receiving from the partner company" is less than 5%, so this emphasis display is not performed. In this way, it is possible to quickly understand which process is prone to delay based on the past project history.

[0069] return Figure 4 In S204, the server 100 sets an image representing the chronological relationship between processes. Thus, the display unit 221 can display multiple processes of a specific business together with the image representing the chronological relationship between processes in a time sequence. Thus, the relationship between processes can be understood, and it is easy to analyze the impact of a delay in a process on other processes.

[0070] exist Figure 5In the example, for example, an image of an arrow indicating that the process of "Approval 1" is executed after the process of "Estimate Request Form Creation" is displayed. An image indicating that the process of "Approval 2" is executed after the processes of "Instruction Manual Creation" and "Drawing Creation" is displayed. An image indicating that the process of "Partner Company Receipt" is executed after the processes of "Approval 1" and "Approval 2" is displayed.

[0071] return Figure 4 In S205, the server 100 sets the path (also called "critical route") that takes the longest time from the start to the end of the specific business among the multiple paths in the multiple processes of the specific business to be displayed differently from other paths. Thus, the display unit 221 displays the path that takes the longest time (required days) differently from other paths.

[0072] exist Figure 5 In the example of , there are three paths (path 1 to path 3) in the execution of budget preparation (specific business). Path 1 is a path that starts from the preparation of the estimate request and ends at approval 3. Path 2 is a path that starts from the preparation of the specification and ends at approval 3. Path 3 is a path that starts from the preparation of the drawings and ends at approval 3.

[0073] Specifically, route 1 is carried out in the order of preparation of estimate commission, approval 1, receipt by partner, on-site investigation, preparation of estimate, receipt of estimate, preparation of execution budget, and approval 3. Route 2 is carried out in the order of preparation of specification, approval 2, receipt by partner, on-site investigation, preparation of estimate, receipt of estimate, preparation of execution budget, and approval 3. Route 3 is carried out in the order of preparation of attached drawings, approval 2, receipt by partner, on-site investigation, preparation of estimate, receipt of estimate, preparation of execution budget, and approval 3.

[0074] The number of days required for these routes is calculated by accumulating the planned days for each process. The number of days required for route 1 is: 3 days for making an estimate request + 1 day for approval 1 + 1 day for receiving from a partner company + 1 day for on-site investigation + 5 days for making an estimate + 1 day for receiving an estimate + 5 days for making an execution budget + 1 day for approval 3 = 18 days. In the same calculation, the number of days required for route 2 is 17 days. The number of days required for route 3 is 19 days.

[0075] The path (critical route) with the largest number of days required among paths 1 to 3 is path 3 (19 days). If each process is carried out according to the planned days, the number of days required for path 3 = the number of days required to prepare the budget (specific business). Therefore, the total number of planned days for each process of the critical route (path 3) is set for the planned days for the specific business.

[0076] like Figure 5As shown, the path (i.e., path 3) that takes the longest time to execute budget preparation (specific business) from the beginning to the end is displayed in an emphasized manner so that it can be distinguished from other paths. Here, each process from "drawing preparation" to "approval 3" is displayed in an emphasized manner. If a delay occurs in any process in the path that takes the longest time (critical route), there is a high possibility that the specific business as a whole will be delayed. By emphasizing this path, you can pay attention to the path that is greatly affected by the delay.

[0077] return Figure 4 In S206, the server 100 generates display information (a process table including statistical data) and ends the display information generation process.

[0078] As described above, in this embodiment, information about past businesses whose process patterns are consistent with specific businesses included in this project is extracted from past project history, and delay data (delay rate, etc.) calculated based on the information about past businesses is displayed together with the process table. Thus, it is possible to infer in which operation process a delay may occur, and to analyze the cause of the delay or the impact on the process. As a result, it is possible to improve the accuracy of the estimation of the operation time, improve the accuracy of the prediction of the project completion date taking into account operation delays, prevent operation delays caused by follow-up of operation processes with high delay rates, and perform construction management for strictly adhering to the delivery date. Thus, even inexperienced construction managers can efficiently perform construction management.

[0079] <Second Embodiment>

[0080] Figure 6 This is a diagram showing a functional block diagram in the construction management system 1 according to the second embodiment. Hereinafter, description of the parts common to the first embodiment will be omitted.

[0081] In the first embodiment, the user specifies a specific business from the input unit 220. Then, the extraction unit 121 is configured to extract information of past businesses whose process patterns match the specific business from the past engineering history. In the second embodiment, in addition to the specific business, the user can also specify extraction conditions from the input unit 220 to extract information of past businesses.

[0082] Specifically, as extraction conditions for extracting past operations from the project history, the input unit 220 can accept input of one or more conditions of the period when the past operations were performed, the region where the past operations were performed, the climate when the past operations were performed, the constructor of the past operations, the manager of the past operations, and the approver related to the past operations. The extraction unit 121 extracts information on past operations in the project history that match the extraction conditions and whose process pattern matches the specific operations. Thus, the scope of the project history can be narrowed down according to the extraction conditions specified by the user.

[0083] For example, when the user specifies the last two years as "budget preparation" (specific business) and "period when past business was performed" and extracts information about past business, statistical data (delay rate, etc.) related to "budget preparation" for the last two years are calculated. Furthermore, when "Tokyo" is specified as "region where past business was performed", statistical data related to "budget preparation" for the last two years in Tokyo are calculated. By specifying a "period" close to the present, the recent trend of the delay rate can be found. By specifying a "region", the trend of the delay rate in the specified region can be found.

[0084] Regarding the weather when the past business was performed, for example, sunny, rainy, cloudy, snowy, etc. can be specified. This allows the effect of the weather on the delay rate to be known. The contractor of the past business indicates the company to which the person in charge of the process belongs. When the contractor is specified, the past business including the process that the specified contractor is responsible for is extracted.

[0085] For example, suppose that the on-site survey is handled by Company A or Company B. When "Company A" is designated as the contractor, the past work of Company A in handling on-site surveys is extracted. When "Company B" is designated as the contractor, the past work of Company B in handling on-site surveys is extracted. In the former case, the delay rate of on-site surveys is 1%, and in the latter case, the delay rate of on-site surveys is 5%. In this case, it can be seen that delays are more likely to occur when Company B is in charge of on-site surveys.

[0086] When a construction manager of past business is specified, the past business included in the project that the specified construction manager is responsible for is extracted. For example, it is assumed that the construction managers of past business include X and Y. When "X" is specified as the construction manager, the past business of X managing the construction is extracted. When "Y" is specified as the construction manager, the past business of Y managing the construction is extracted. In the former case, the delay rate of the business is 1%, and in the latter case, the delay rate of the business is 5%. In this case, it can be seen that when Y manages the construction, the implementation of specific business is prone to delay.

[0087] As an approver related to past business, for example, Figure 5 The supervisor who approved the approval 1, approval 2, approval 3, etc. can be predicted that the delay rate will be higher when a certain approver is set.

[0088] As described above, by filtering past construction histories according to various extraction conditions to extract past tasks, it is possible to analyze, for example, in what areas, climates, construction managers, construction workers, and approvers delays are likely to occur.

[0089] In the second embodiment, the user can input the actual number of days in each process from the input unit 220. In addition, as statistical data, in addition to the delay rate, the average delay days, the number of delay occurrences, and the predicted number of days are calculated. The display unit 221 displays these statistical data. Figure 7 The following figures provide a detailed description.

[0090] Figure 7 This is a flowchart of the main process. After the main process starts, in S301, the server 100 obtains the current project information and the past project history. In S302, the server 100 obtains the specific business and extraction conditions specified in the current project. In S303, the server 100 extracts the information of the past business in the past project history that matches the extraction conditions and the process pattern matches the specific business. The processing of S302 and S303 is as follows: Figure 6 As described above, the range of past business can be narrowed down by using the extraction conditions.

[0091] In S304, the server 100 calculates statistical data of the extracted past business information. The delay data included in the statistical data includes the average delay days and the number of delays in each process of the past business in addition to the delay rate of the past business and the delay occurrence rate of each process of the past business.

[0092] In S305, the server 100 predicts the predicted days of the specific business based on the planned days and the actual days of each process of the specific business (the specific calculation method uses Fig.10 (described later) In S306, the server 100 sets the planned days for the specific business, the planned days for each process of the specific business, and the actual days with respect to the planned days.

[0093] Thus, the display unit 221 displays the process table including the predicted days for the specific business. In addition, the display unit 221 displays the process table including the planned days for the specific business, the planned days for each process of the specific business, and the actual days relative to the planned days. Thus, it is possible to check the actual actual days relative to the planned days and analyze the impact of delays on processes to be executed in the future.

[0094] Next, use Fig. 9 A specific example will be described. Fig. 9 This is a diagram showing an example of a process table. Figure 5 The process table 91 is a process table of the first embodiment. Fig. 9 The process table 92 is a process table of the second embodiment. Both of them show the process table of "executing budget preparation" (specific business).

[0095] In the second embodiment, the predicted days are also displayed in the selected "Execution Budget Preparation" (specific business). In "Execution Budget Preparation", the delay rate = 3.0%, the planned days = 19 days, and the predicted days = 20 days. Here, the planned days and the predicted days indicate the planned days and the predicted days of this project. In contrast, the delay rate indicates the delay rate of past projects.

[0096] In the second embodiment, the average delay days, the number of delays, and the actual number of days are also displayed in each process. For example, in "Estimate Request Form Creation", the delay rate = 5.0%, the average delay days = 2.0 days, the number of delays = 5, the planned days: 3.0 days, and the actual number of days: 4.0 days.

[0097] For example, if, among 100 past jobs, 95 estimate orders were completed within the planned days (3 days), and 5 estimate orders were completed beyond the planned days (3 days), the calculation is as follows: delay rate = 5.0% (= 5 / 100), and number of delayed jobs = 5. For example, if the actual number of days is 5 days, the delay days are calculated to be 2 days (= 5 days - 3 days) with respect to the planned number of days = 3. The average delay days = 2.0 days means that the average delay days of the 5 delayed jobs is 2.0 days.

[0098] Here, the delay rate, average delay days, and number of delay occurrences indicate the delay rate, average delay days, and number of delay occurrences of past projects. In contrast, the planned days and actual days indicate the planned days and actual days of this project. Regarding the actual days, when this project is in progress, the actual days input from the input unit 220 are reflected in the process table.

[0099] For example, suppose that the actual number of days as a result of executing the process of preparing the estimate request form is 4.0 days. If the user sets 4.0 days as the actual number of days for preparing the estimate request form from the input unit 220, the input actual number of days is reflected in the process table. In addition, for processes for which actual number of days is not input (not implemented), nothing is displayed in the column of actual number of days. In addition, Fig. 9 For simplicity, the columns for average delay days, number of delays, and actual number of days for receipt to approval 3 of the partner company are omitted.

[0100] return Figure 7 In S307, the server 100 executes display information generation processing ( Figure 8 ). In S308, the server 100 outputs the display information (the process table including the statistical data) to the display unit, and ends the main process.

[0101] Figure 8 4 is a flowchart of the display information generation process. After the display information generation process starts, in S401, the server 100 obtains statistical data and the current project information. In S402, the server 100 sets the display method of the delay rate of the past business according to the delay rate (delay occurrence rate) of the past business. In S403, the server 100 sets the display method of the delay rate of each process according to the delay rate of each process of the past business. The processes of S402 and S403 are the same as those of the first embodiment.

[0102] In S404, when the predicted days of the specific business exceed the planned days, the server 100 sets the predicted days of the specific business to a predetermined display mode. In S405, when the actual days of each process of the specific business exceed the planned days, the server 100 sets the actual days to a predetermined display mode.

[0103] Thus, when the predicted duration of a specific task exceeds the planned duration, the display unit 221 displays the predicted duration of the specific task in a predetermined format. When the actual duration of each process of the specific task exceeds the planned duration, the display unit 221 displays the actual duration in a predetermined format.

[0104] Specifically, if Fig. 9 As shown in the figure, the forecasted days (20 days) for "Estimate preparation" (specific business) exceed the planned days (19 days), so the display "Forecast days: 20 days" is highlighted by a rectangle. In addition, for example, the actual days (4.0 days) of the process "Estimate commission preparation" exceed the planned days (3.0 days), so the display "Actual days: 4.0 days" is highlighted by a rectangle. This makes it easy to intuitively understand the occurrence of delays. In addition, it is also possible to highlight the display by displaying characters in red.

[0105] return Figure 8 In S406, the server 100 sets an image representing the causal relationship between processes. In S407, the server 100 sets the path requiring the longest number of days to be displayed differently from other paths. The processing of S406 and S407 is the same as that of the first embodiment. In S408, the server 100 generates display information (statistical data, process table), and ends the display information generation processing.

[0106] Next, use Fig.10 The calculation of forecast days for a specific business is explained. Fig.10 This is a diagram for explaining the calculation of the predicted days. The server 100 predicts the number of days predicted to be required from the start to the end of the specific business as the predicted days for the specific business based on the planned days for each process of the specific business and the actual days relative to the planned days. This will be described in detail below.

[0107] like Fig.10 As shown, in "Estimate Preparation", the planned days for each process of route 3 (critical route) are: drawing preparation: 4 days, approval 2: 1 day, receiving from partner: 1 day, on-site investigation: 1 day, estimate preparation: 5 days, estimate receipt: 1 day, budget preparation: 5 days, approval 3: 1 day. The planned days for "Estimate Preparation" (specific business) = the sum of the planned days for each process of route 3 (critical route) (19 days).

[0108] If any process is not executed, the actual number of days is not set for all processes. In this case, the total number of planned days for each process of route 3 = the estimated number of days (19 days) for "executing budget preparation" (specific business).

[0109] Here, it is assumed that the number of days required for drawing production is 5 days. In this case, 5 days are set as the actual number of days for drawing production. For the process for which the actual number of days is set, the predicted number of days is calculated using the actual number of days. In this example, the sum of the actual number of days for drawing production: 5 days, the planned number of days for approval 2: 1 day, the planned number of days for receipt by the partner: 1 day, the planned number of days for on-site investigation: 1 day, the planned number of days for estimate production: 5 days, the planned number of days for receipt of the estimate: 1 day, the planned number of days for budget production: 5 days, and the planned number of days for approval 3: 1 day = 20 days is set as the predicted number of days for the specific business. In this way, the predicted number of days for the specific business is updated every time the actual number of days is input.

[0110] Furthermore, suppose that approval 2 is performed and the number of days required (actual days) is 1 day. In this case, it matches the planned number of days in approval 2, so the predicted number of days for the specific business is still 20 days. In this way, the actual number of days is updated, and in approval 3, it is assumed that the actual number of days exceeds the planned number of days by 1 day. In this case, the predicted number of days for the specific business increases by 1 day to 21 days.

[0111] In the above, for simplicity, the predicted days for a specific business are calculated based on the planned days and the actual days for path 3. However, in reality, the predicted days for a specific business are also calculated by taking into account the actual days for paths 1 and 2. Fig. 9 In the example, the actual number of days for manual production is 7 days. Fig.10 The actual performance (5 days) of drawing production in the example of exceeds 2 days, so approval 2 is performed after the specification is produced. As a result, the predicted number of days for the specific business = 23 days (21 days + 2 days).

[0112] As described above, by reflecting the actual number of days and updating the predicted number of days for a specific task, it is possible to improve the estimation accuracy of the predicted number of days for a specific task.

[0113] In addition, in this embodiment, the display unit 221 can display each process of a specific business in the order of the delay occurrence rate of each process in the past business from high to low by designation from the user. Fig.11 , 12 Provide explanation.

[0114] Fig.11 2 is a flowchart of the sorting process. The sorting process is executed when there is an instruction from the user to display in descending order of delay occurrence rate. Then, after the sorting process is executed, the display of the display unit 221 is updated.

[0115] After the sorting process starts, in S601, the server 100 obtains the delay rate of each process in the past business. In S602, the server 100 determines the display order of each process of the specific business in descending order of delay rate, and ends the sorting process.

[0116] Next, use Fig.12 Provide specific instructions. Fig.12 is a diagram showing an example of a process table. Fig. 9 According to the display, the delay rate of each process is: Preparation of estimate request: 5.0%, Approval 1: 0.4%, Preparation of manual: 3.0%, Preparation of drawings: 5.0%, Approval 2: 0.4%, Collection by partner: 0.3%, On-site investigation: 0.5%, Preparation of estimate: 2.5%, Collection of estimate: 0.5%, Preparation of execution budget: 2.5%, Approval 3: 0.4%.

[0117] The display unit 221 displays the above contents in the order of delay rate from high to low. Fig.12 As shown, the drawing preparation and estimate request preparation (5.0%) with the highest delay rate is displayed at the top, and the specification preparation (3.0%) with the second highest delay rate is displayed below the drawing preparation and estimate request preparation.

[0118] Similarly, the order of estimate preparation, budget preparation (2.5%), on-site investigation, estimate receipt (0.5%), approval 1, approval 2, approval 3 (0.4%), and receipt from a partner (0.3%) is displayed. This makes it easy to analyze which process is prone to delay.

[0119] In the first embodiment and the second embodiment, the application of Figure 5 , Fig. 9 The process table shown in FIG. 1 is used for explanation. However, the process table is not limited to this, and the process table may be a bar chart process table showing a bar chart, or a network process table, and any process table may be applied. For example, when a bar chart process table is applied, the delay rate, the number of delays, the planned days, and the actual days may be displayed corresponding to the bar chart representing the process.

[0120] As described above, in this embodiment, information such as the number of delays, delay rates, and average delay days based on past project history is added to all processes, and filtering is performed according to extraction conditions. The display can be sorted to facilitate delay analysis, and the actual number of days for this project relative to the planned number of days is displayed, and the predicted number of days for a specific business is updated in real time. This information is displayed at a glance on the process table, and processes with high delay rates and processes with actual number of days exceeding the planned number of days are highlighted. In particular, in this embodiment, it is characterized in that analysis can be performed from two aspects: the actual delay status of this project (predicted number of days, actual number of days) and the delay status of past projects (delay rate, etc.).

[0121] This makes it possible to infer which operation process may be delayed, and analyze the cause of the delay or the impact on the process. As a result, it is possible to improve the accuracy of the estimated operation time, improve the accuracy of the prediction of the project completion date taking into account the operation delay, prevent operation delays caused by following up on operation processes with high delay rates, and perform construction management to strictly adhere to the delivery date. This allows even inexperienced construction managers to efficiently manage construction.

[0122] It is also intended that the various embodiments disclosed this time can be appropriately combined and implemented within the scope of technical non-contradiction. Moreover, the embodiments disclosed this time should be considered to be illustrative in all aspects, rather than restrictive. The technical scope shown in this disclosure is not shown by the description of the above-mentioned embodiments, but by the claims, and is intended to include all changes within the meaning and scope equivalent to the claims.

[0123] Description of symbols

[0124] 1: construction management system; 91-93: process table; 100: server; 111, 211: control unit; 112, 212: storage unit; 113, 213: communication unit; 121: extraction unit; 122: statistics unit; 123: generation unit; 200: terminal; 220: input unit; 221: display unit.

Claims

1. A construction management system that manages the construction of a project, wherein: This project includes a specific business consisting of multiple processes. The construction management system has: A control unit that generates a process table for the specific business; A display unit, which displays the process table; as well as a storage unit that stores information of past projects as a project history, The control unit extracts information of past business whose process pattern matches the specific business from the process history, The control unit calculates statistical data of the extracted past business information, The statistical data includes delay data related to delays relative to a plan in the past operations, The display unit displays the statistical data including the delay data together with the process table.

2. The construction management system according to claim 1, wherein: The delay data includes a delay occurrence rate of the past work and a delay occurrence rate of each process of the past work.

3. The construction management system according to claim 2, wherein: The display unit displays the delay occurrence rate of the past business in a different manner according to the delay occurrence rate of the past business. The display unit displays the delay occurrence rate of each process in different ways according to the delay occurrence rate of the process in the past work.

4. The construction management system according to claim 2 or 3, wherein: The delay data further includes the average delay days and the number of delay occurrences of each process in the past business.

5. The construction management system according to any one of claims 1 to 4, wherein: The display unit displays the process table including the planned days for the specific business, the planned days for each process of the specific business, and the actual days relative to the planned days. When the actual number of days for each process of the specific work exceeds the planned number of days, the display unit displays the actual number of days in a predetermined format.

6. The construction management system according to claim 5, wherein: The control unit predicts the number of days predicted to be required from the start to the end of the specific business as the predicted number of days for the specific business based on the planned number of days for each process of the specific business and the actual number of days relative to the planned number of days, The display unit further displays the process table including the predicted number of days for the specific business. When the predicted number of days for the specific work exceeds the planned number of days, the display unit displays the predicted number of days for the specific work in the predetermined format.

7. The construction management system according to any one of claims 1 to 6, wherein: The display unit displays the plurality of processes in chronological order together with images indicating the causal relationship between the processes. The display unit displays, among the plurality of routes in the plurality of processes, a route requiring the longest number of days from the start to the end of the specific task in a manner different from other routes.

8. The construction management system according to any one of claims 1 to 7, wherein: The construction management system further includes an input unit, which receives input from a user. The input unit is capable of accepting input of one or more conditions of the period when the past business was performed, the region where the past business was performed, the climate when the past business was performed, the constructor of the past business, the manager of the past business, and the approver related to the past business as an extraction condition for extracting the past business from the project history. The past business is a business in the process history that matches the extraction condition and has a process pattern that matches the specific business.

9. The construction management system according to any one of claims 2 to 8, wherein: The display unit displays each process of the specific task in descending order of delay occurrence rate of each process in the past task.

10. A construction management method for managing the construction of a project, wherein: This project includes a specific business consisting of multiple processes. The construction management method comprises the following steps: A generation step is to generate a process table for the specific business; Display step, displaying the process table; and Storage steps, store information of past projects as project history, The generation step comprises the following steps: extracting information of past business whose process pattern is consistent with the specific business from the engineering history; as well as Calculating statistical data of the extracted past business information, The statistical data includes delay data related to delays relative to a plan in the past operations, The display step includes the following steps: displaying the statistical data including the delay data together with the process table.

Images