Construction management system and construction management method

Abstract

In the present invention, current construction includes a specific operation consisting of a plurality of steps. A construction management system (1) comprises a control unit (111), a display unit (221), and a storage unit (112). The control unit (111) generates a project schedule for the specific operation. (221) displays the project schedule. The storage unit (112) stores, as construction history, information pertaining to past construction. The control unit (111) extracts, from the construction history, information pertaining to past operations that match the specific operation in terms of the pattern of steps. The control unit (111) calculates aggregated data of the extracted information pertaining to the past operations. The aggregated data includes delay data pertaining to delays in plans in the past operations. The display unit (221) displays the project schedule and the aggregated data including the delay data.

Description

[Technical field]

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

[0002] In construction work at a building or other construction site, multiple workers (personnel) in charge of the work often carry out multiple tasks in parallel. The construction manager (site agent) who manages the construction needs to understand the workload of each worker and the progress of multiple tasks being carried out simultaneously. On top of that, the construction manager needs to take measures to ensure that all work is completed safely by the deadline while maintaining the quality of the work.

[0003] The construction manager grasps the workload of the workers by holding morning meetings, hearing from the work supervisor, checking the daily work reports, etc., and grasps the progress of the work by patrolling the work site to make visual inspections and checking on-site photos, etc. Based on the situation grasped in this way, the construction manager manages the construction by, in some cases, increasing or replacing the number of workers, reviewing the work process, etc. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-135098 A Summary of the Invention [Problem to be solved by the invention]

[0005] A certain amount of on-site experience is required for construction managers to be able to appropriately judge whether or not it is necessary to review work processes based on the situation they have grasped. In the current situation where the labor force in the construction industry is decreasing, it is necessary to train construction managers who can make such appropriate judgments and manage construction, but there is also a demand for construction management systems that allow even inexperienced construction managers to efficiently manage construction.

[0006] The present disclosure has been made to solve such problems, and the purpose of the present disclosure is to provide a construction management system and a construction management method that allow even inexperienced construction managers to efficiently perform construction management. [Means for solving the problem]

[0007] The construction management system disclosed herein is a system for managing construction work. The current construction work includes a specific task consisting of multiple processes. The construction management system includes a control unit, a display unit, and a memory unit. The control unit generates a schedule for the specific task. The display unit displays the schedule. The memory unit stores information about past construction work as construction history. The control unit extracts information about past tasks whose process patterns match those of the specific task from the construction history. The control unit calculates aggregated data of the extracted information about the past tasks. The aggregated data includes delay data related to delays to plans in the past tasks. The display unit displays the aggregated data including the delay data together with the schedule.

[0008] The construction management method disclosed herein is a method for managing construction work. The current construction work includes a specific task consisting of a plurality of processes. The construction management method includes a step of generating a schedule for the specific task, a step of displaying the schedule, and a step of storing information on past construction work as a construction history. The generating step includes a step of extracting information on past tasks whose process patterns match those of the specific task from the construction history, and a step of calculating aggregated data of the extracted information on the past tasks. The aggregated data includes delay data relating to delays to plans in the past tasks. The displaying step includes a step of displaying the aggregated data including the delay data together with the schedule. Effect of the Invention

[0009] According to the present disclosure, it is possible to estimate which work process may have a delay, and analyze the cause of the delay or the impact on the processes. As a result, it is possible to perform construction management to strictly adhere to delivery deadlines, such as improving the accuracy of estimating work time, improving the accuracy of predicting the completion date of construction taking into account work delays, and preventing work delays by following up on work processes with high delay rates. This allows even inexperienced construction managers to perform construction management efficiently. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing a hardware configuration of a construction management system according to a first embodiment. FIG. [Diagram 2] FIG. 2 is a functional block diagram of the construction management system. [Diagram 3] 13 is a flowchart of a main process. [Figure 4] 13 is a flowchart of a display information generating process. [Diagram 5] FIG. 1 is a diagram showing an example of a process chart. [Figure 6] FIG. 11 is a functional block diagram of a construction management system according to a second embodiment. [Figure 7] 13 is a flowchart of a main process. [Figure 8] 13 is a flowchart of a display information generating process. [Figure 9] FIG. 1 is a diagram showing an example of a process chart. [Figure 10] FIG. 13 is a diagram for explaining calculation of a predicted number of days. [Figure 11] 13 is a flowchart of a sorting process. [Figure 12] FIG. 1 is a diagram showing an example of a process chart. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the drawings. Although several embodiments will be described below, it is planned from the beginning of the application that the configurations described in each embodiment will be appropriately combined. Note that the same or corresponding parts in the drawings are given the same reference numerals, and the description thereof will not be repeated.

[0012] First Embodiment 1 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 that manages the construction of a construction project.

[0013] In this embodiment, a construction project is defined as consisting of multiple tasks. The construction project is completed when these tasks are completed. Furthermore, each task is defined as consisting of multiple processes. The construction project is completed when the tasks in these processes are completed.

[0014] For example, in the example of Figure 5 described later, the construction work for the target building consists of multiple tasks including "creating a working budget," "creating a construction plan," "creating safety and health documents," and "creating completed drawings." In addition to creating these documents, the construction work also includes work (tasks) at the construction site.

[0015] In this embodiment, the construction management system 1 generates and displays a schedule for work specified by the user operating the terminal (hereinafter referred to as "specific work") in a construction project that is scheduled to be carried out or is currently being carried out (hereinafter referred to as "the current construction project").

[0016] In the example of Figure 5, the user has specified "Create execution budget" as a specific task, and the process chart for "Create execution budget" that is generated as a result is displayed. The task of "Create execution budget" (specific task) consists of multiple steps such as "Create request for quotation", "Approval 1", and "Receipt from partner company".

[0017] A person in charge (also called a "worker") is assigned to each of the multiple processes. The person in charge may refer to the person in charge of the contractor who undertakes each process, or may refer to the contractor who undertakes each process itself. There may be one or more people in charge (workers) in charge of one process.

[0018] Furthermore, when the schedule is displayed, aggregated data based on past construction history is also displayed. The aggregated data includes the delay occurrence rate (also called the "delay rate") described later, which allows analysis of how frequently delays are likely to occur against the plan.

[0019] Returning to FIG. 1, the construction management system 1 comprises a server 100 and a terminal 200. The server 100 performs processes such as generating a schedule. The terminal 200 is a terminal used by a construction manager (also simply referred to as "manager") who manages the construction of the construction work. The construction manager manages the site so that the construction work is completed by the deadline while grasping each task of the construction work that he / she is in charge of, the workload of each person in each process, and the progress of each task.

[0020] The server 100 includes a control unit 111, a storage unit 112, and a communication unit 113. These are connected to each other via a bus so that they can 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), and a non-volatile storage device (for example, a HDD (Hard Disk Drive) or an SSD (Solid State Drive)). The storage unit 112 stores information on past construction work as construction history.

[0021] The control unit 111 loads a program stored in the ROM into the RAM and executes it to realize various functions of the server 100. The ROM stores a program in which the processing procedures of the server 100 are written. The RAM serves as a working area when the control unit 111 executes a program, and temporarily stores the program, data for executing the program, and the like. The server 100 can be connected to the terminal 200 wirelessly or via a wire via the communication unit 113.

[0022] The terminal 200 may be, for example, a mobile terminal such as a smartphone or a tablet, or a personal computer such as a notebook computer or a desktop computer.

[0023] 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 to each other via a bus so that they can communicate with each other. Similarly, the storage unit 212 may be configured to include a ROM, a RAM, and a non-volatile storage device such as an HDD or SSD.

[0024] The control unit 211 loads a program stored in the ROM into the RAM and executes it to realize various functions of the terminal 200. The ROM stores a program in which the processing procedures of the terminal 200 are written. The terminal 200 is connectable to the server 100 via the communication unit 213.

[0025] The input unit 220 accepts input from a 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 a process chart generated by the control unit 111, etc.

[0026] 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 device is configured so that the display unit (display) displays the schedule generated by the control unit (CPU) of the device.

[0027] 2 is a functional block diagram of the construction management system 1. The control unit 111 is capable of executing the processes executed by the extraction unit 121, the aggregation unit 122, and the generation unit 123.

[0028] The storage unit 112 stores information on past construction works as construction history, and also stores information on the current construction work as construction information.

[0029] The past construction is construction that has been carried out in the past, and the information is accumulated in the storage unit 112 each time construction is carried out. The current construction is construction that is scheduled to be carried out or is being carried out, and is the construction for which a schedule is generated and displayed by the construction management system 1.

[0030] The construction management system 1 generates a schedule for the work (=specific work) specified by the user (manager) using the terminal 200 from the input unit 220 for the current construction project, and displays the generated schedule. In the example of Fig. 5, "creation of execution budget" corresponds to "specific work".

[0031] The current construction information includes the name of the construction, multiple tasks within the construction, multiple processes within each task, and the planned number of days for each task and each process. Past construction history also includes the actual number of days compared to the planned number of days, and delay information such as whether or not delays occurred in each process or task and the number of days delayed. Note that delay information can be calculated based on the planned number of days and the actual number of days.

[0032] The extraction unit 121 acquires past construction history and current construction information from the storage unit 112, as well as information on the specific task specified by the input unit 220. The extraction unit 121 extracts information on tasks (hereinafter referred to as "past tasks") whose process patterns match those of the specific task from the past construction history. The aggregation unit 122 calculates aggregated data (such as delay rate) of the extracted information on the past tasks. Details regarding the extraction of information on past tasks and the calculation of the aggregated data will be described later.

[0033] The generation unit 123 generates display information (a schedule, aggregated data) based on the current construction information and the aggregated data. The display unit 221 displays the display information. These processes will be specifically described below with reference to a flowchart.

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

[0035] When the main process starts, in S101, the server 100 acquires current construction information and past construction history from the storage unit 112. In S102, the server 100 extracts information on past tasks whose process patterns match the specific task designated by the user from the past construction history.

[0036] A specific explanation will be given below with reference to Fig. 5. Fig. 5 is a diagram showing an example of a schedule. The work for this construction project includes "creating an execution budget," "creating a construction plan," "creating safety and health documents," and "creating completed drawings and drawings." The user (administrator) creates the schedule by specifying (selecting) "creating an execution budget" (specific work) from among these tasks.

[0037] "Preparing a working budget" is carried out in multiple steps. The steps are "Preparing a request for quotation" by the person in charge, followed by "Approval 1" by the supervisor. Also, after the person in charge "Preparing specifications" and "Preparing drawings", the supervisor "Approval 2" is carried out.

[0038] Furthermore, after the superior makes "Approval 1" and "Approval 2", the request for quotation, specifications, and drawings are received by the cooperating company (the "Receiving from Cooperative Company" Step). The person in charge at the cooperating company performs an "on-site investigation" and then "prepares a quotation". The person in charge of preparing the working budget receives the quotation from the person in charge at the cooperating company (the "Receiving Quotation" Step) and then "prepares the working budget". After "preparing the working budget", the superior makes "Approval 3", and the task of "preparing the working budget" is completed.

[0039] Server 100 extracts information on past tasks that match the above-mentioned process patterns from the past construction history. Basically, tasks that match multiple processes (quote request creation to approval 3) of "execution budget creation" may be extracted from the past construction history, or tasks with some of the multiple processes that match may be extracted from the past construction history. For example, of the multiple processes shown in FIG. 5, those that do not include the processes "quote request creation" and "approval 1" and all other processes match may be extracted as past tasks, or tasks (processes) that only match "specification creation" may be extracted as past tasks.

[0040] Returning to FIG. 3, in S103, server 100 calculates aggregated data of the extracted information of the past tasks. The aggregated data includes delay data in the past tasks. The delay data is data related to delays against a plan. Specifically, the delay data includes the delay occurrence rate (delay rate) of the past tasks and the delay occurrence rate of each process of the past tasks. Next, in S104, server 100 sets the planned number of days for the specific task and the planned number of days for each process of the specific task.

[0041] In the example of Figure 5, the "Execution budget creation" (specific task) column displays a calculated delay rate of 3.0% and a set planned number of days of 19 days (the process from creating a request for quotation to approval 3 is planned to be completed in 19 days). This shows that the planned number of days for the execution budget creation, which is a specific task, is 19 days, and also shows that the delay rate of past tasks whose process pattern matches the process pattern of the execution budget creation is 3.0%.

[0042] For example, suppose 100 tasks (process patterns such as creating a request for quotation~approval 3 as shown in Figure 5) are extracted as past tasks. If 97 of these tasks were completed within the planned number of days (19 days) (the actual number of days was less than the planned number of days), and 3 tasks were completed after the planned number of days (19 days) (the actual number of days exceeded the planned number of days), the delay rate would be calculated as 3.0% (= 3 / 100).

[0043] Similarly, the delay rate and planned number of days are displayed in the column for each step of "Create execution budget" (specific task). For example, in the column for the step of "Create quotation request", the delay rate is 5.0% and the planned number of days is 3.0 days (scheduled to be completed in 3 days). This shows that the planned number of days for the "Create quotation request" step in execution budget creation is 3.0 days, and the delay rate of the quotation request creation in the past tasks is 5.0%. For example, in 100 past tasks, if the work was completed within the planned number of days (3 days) for 95 quotation requests and the work was completed after the planned number of days (3 days) for 5 quotation requests, the delay rate is calculated as 5.0% (= 5 / 100).

[0044] Additionally, in the "Specifications Creation" process column, a delay rate of 3.0% and planned days of 2.0 days are displayed. This shows that the planned days for the "Specifications Creation" process in the production budget creation are 2.0 days, and the delay rate of specifications creation in past work is 3.0%. For example, in 100 past work cases, if the work was completed within the planned number of days (2 days) for 97 specifications and the work was completed after the planned number of days (2 days) for 3 specifications, the delay rate is calculated as 3.0% (= 3 cases / 100 cases).

[0045] In addition, as past tasks whose process patterns match the specific task, in addition to extracting past tasks that match all or some of the processes of the specific task, past tasks whose process patterns match only one of the processes of the specific task may be extracted. For example, past tasks that match "specification creation" among the multiple processes of "execution budget creation" in FIG. 5 are extracted. In this case, the process of creating specifications may be extracted from the past construction history, and the delay rate of the process of creating the extracted specifications may be calculated and displayed in the "specification creation" column of the schedule. Similarly, past tasks that match "drawing" may be extracted. In this case, the process of creating drawings may be extracted from the past construction history, and the delay rate of the process of creating the extracted drawings may be calculated and displayed in the "drawing creation" column of the schedule. In this way, individual processes such as "approval," "site inspection," and "quotation creation" may be extracted from the past construction history, and aggregated data such as delay rates may be created.

[0046] 3, in S105, the server 100 executes a display information generation process (described later with reference to FIG. 4) to generate display information (aggregated data and a schedule). In S106, the server 100 outputs the display information to the display unit and ends the main process. The display unit 221 displays the aggregated data (including delay data) together with the schedule.

[0047] 4 is a flowchart of the display information generation process. When the display information generation process starts, the server 100 acquires the aggregated data and the current construction information in S201.

[0048] In S202, the server 100 sets the display mode of the delay rate of the past task according to the delay rate (delay occurrence rate) of the past task. In S203, the server 100 sets the display mode of the delay rate of each process according to the delay rate of the process of the past task.

[0049] An explanation will be given with reference to Fig. 5. The display unit 221 changes the display mode of the delay rate of the past task depending on the delay rate of the past task. The display unit 221 changes the display mode of the delay rate of each step of the past task depending on the delay rate of the step.

[0050] Specifically, if the delay rate of a past task or each process of a past task is 5% or more, the delay rate is displayed in an emphasized manner. In the example of FIG. 5, the delay rates of the processes "Create request for quotation" and "Create drawings" are both 5% or more (5%). For this reason, the display of "Delay rate: 5.0%" is highlighted by enclosing it in a square. Note that "Delay rate: 5.0%" may also be highlighted by displaying it in red.

[0051] On the other hand, the delay rate of the "Create execution budget" task, as well as other processes such as "Create specifications," "Approval 1," "Approval 2," and "Receive from partner companies" is less than 5%, so they are not highlighted in this way. By doing this, it is possible to quickly grasp which processes are likely to experience delays based on past construction history.

[0052] Returning to Fig. 4, in S204, the server 100 sets an image showing the chronological relationship between the processes. This enables the display unit 221 to display a plurality of processes of a specific job in chronological order together with an image showing the chronological relationship between the processes. This makes it easier to grasp the relationship between the processes and analyze the impact of a delay in one process on other processes.

[0053] In the example of Fig. 5, for example, an image of an arrow is displayed indicating that the "Approval 1" Step will be executed after the "Request for quotation" Step. An image is displayed indicating that the "Approval 2" Step will be executed after the "Specifications" and "Drawings" Steps. An image is displayed indicating that the "Receipt from partner company" Step will be executed after the "Approval 1" and "Approval 2" Steps.

[0054] 4, in S205, the server 100 sets the path that takes the longest number of days from the start to the end of the specific task (also called the "critical path") among the multiple paths in the multiple steps of the specific task in a display mode different from the other paths. As a result, the display unit 221 displays the path that takes the longest number of days (number of required days) in a mode different from the other paths.

[0055] In the example of Figure 5, there are three routes (route 1 to route 3) for creating an execution budget (specific task). Route 1 is a route that starts with creating a request for quotation and ends with approval 3. Route 2 is a route that starts with creating specifications and ends with approval 3. Route 3 is a route that starts with creating drawings and ends with approval 3.

[0056] Specifically, route 1 proceeds in the order of creating a request for quotation, approval 1, receipt by the partner company, site investigation, creating a quotation, receiving the quotation, creating a working budget, and approval 3. Route 2 proceeds in the order of creating specifications, approval 2, receipt by the partner company, site investigation, creating a quotation, receiving the quotation, creating a working budget, and approval 3. Route 3 proceeds in the order of creating drawings, approval 2, receipt by the partner company, site investigation, creating a quotation, receiving the quotation, creating a working budget, and approval 3.

[0057] The number of days required for these routes can be calculated by adding up the planned number of days for each process. The number of days required for route 1 is: Request for quotation: 3 days + Approval 1: 1 day + Receipt from partner company: 1 day + Site inspection: 1 day + Estimate preparation: 5 days + Estimate reception: 1 day + Working budget preparation: 5 days + Approval 3: 1 day = 18 days. Calculating in the same way, the number of days required for route 2 is 17 days. The number of days required for route 3 is 19 days.

[0058] Of routes 1 to 3, the route (critical path) with the longest number of days required is route 3 (19 days). If each process proceeds according to the planned number of days, the number of days required for route 3 = the number of days required for creating the execution budget (specific task). For this reason, the planned number of days for the specific task is set to the sum of the planned number of days for each process on the critical path (route 3).

[0059] As shown in Figure 5, the path that takes the most days from start to finish of the execution budget creation (specific task) (i.e., path 3) is displayed in an emphasized manner so that it can be distinguished from the other paths. Here, each process from "drawing creation" to "approval 3" is displayed with emphasis. In the path that takes the most days (critical path), if a delay occurs in any process, there is a high possibility that a delay will occur in the specific task as a whole. By highlighting such paths, it is possible to draw attention to paths that will be greatly affected by delays.

[0060] Returning to FIG. 4, the server 100 generates display information (a process chart including the aggregated data) in S206, and ends the display information generation process.

[0061] As explained above, in this embodiment, information on past tasks whose process patterns match those of the specific tasks included in the current construction project is extracted from the past construction history, and delay data (delay rate, etc.) calculated from the information on the past tasks is displayed in a list along with the construction schedule. This makes it possible to estimate which work process a delay may occur in, and analyze the cause of the delay or the impact it has on processes. As a result, construction management can be performed to strictly adhere to delivery deadlines, such as improving the accuracy of work time estimates, improving the accuracy of forecasting the construction completion date taking into account work delays, and preventing work delays by following up on work processes with high delay rates. This allows even inexperienced construction managers to perform construction management efficiently.

[0062] <Second embodiment> 6 is a functional block diagram of the construction management system 1 according to the second embodiment. Hereinafter, a description of the parts common to the first embodiment will be omitted.

[0063] In the first embodiment, the user specifies a specific task from the input unit 220. The extraction unit 121 is configured to extract information on past tasks whose process patterns match those of the specific task from the past construction history. In the second embodiment, the user can specify extraction conditions from the input unit 220 in addition to the specific task to extract information on past tasks.

[0064] Specifically, the input unit 220 can accept input of one or more conditions from the period when the past work was performed, the area where the past work was performed, the weather when the past work was performed, the contractor of the past work, the manager of the past work, and the approver of the past work as extraction conditions for extracting past work from the construction history. The extraction unit 121 extracts information on past work that matches the specific work and process pattern from the construction history and matches the extraction conditions. This makes it possible to narrow down the construction history using the extraction conditions specified by the user.

[0065] For example, if a user specifies "execution budget creation" (specific task) and the last two years as the "time when past tasks were performed" and information on past tasks is extracted, aggregated data (lateness rate, etc.) for the last two years regarding "execution budget creation" will be calculated. In addition, if "Tokyo" is specified as the "area where past tasks were performed," aggregated data for the last two years regarding "execution budget creation" for Tokyo will be calculated. By specifying a "time" close to the present, it is possible to know the recent trend in lateness rates. By specifying the "area," it is possible to know the trend in lateness rates in the specified area.

[0066] The weather when the past work was performed can be specified as sunny, rainy, cloudy, snowy, etc. This makes it possible to know the effect of weather on the delay rate. The contractor of the past work indicates the company to which the person in charge of the process belongs. When a contractor is specified, past work that includes the process in which the specified contractor is in charge is extracted.

[0067] For example, suppose that on-site inspections are handled by Company A or Company B. If "Company A" is specified as the construction company, past work in which Company A was in charge of on-site inspections will be extracted. If "Company B" is specified as the construction company, past work in which Company B was in charge of on-site inspections will be extracted. If the delay rate for on-site inspections is 1% in the former case and 5% in the latter case, it can be seen that delays are more likely to occur when Company B is in charge of on-site inspections.

[0068] When a construction manager of past work is specified, past work included in the construction work that the specified construction manager is in charge of is extracted. For example, the construction managers of past work include X and Y. When "X" is specified as the construction manager, past work managed by X is extracted. When "Y" is specified as the construction manager, past work managed by Y is extracted. If the delay rate of work is 1% in the former case and 5% in the latter case, it can be seen that delays are likely to occur in the implementation of specific work when Y manages the construction.

[0069] As approvers for past work, for example, it is possible to specify superiors who will approve Approval 1, Approval 2, Approval 3, etc. in Figure 5. This makes it possible to predict which approver will result in a high delay rate.

[0070] As described above, by filtering past construction history using various extraction conditions and extracting past work, it is possible to analyze, for example, what regions, weather conditions, construction managers, contractors, and approvers are likely to cause delays.

[0071] In the second embodiment, the user can input the actual number of days for each process from the input unit 220. In addition to the delay rate, the average number of days of delay, the number of delays, and the predicted number of days are calculated as the aggregated data. The display unit 221 displays these aggregated data. A specific description will be given below with reference to FIG. 7 and subsequent figures.

[0072] FIG. 7 is a flowchart of the main processing. When the main processing starts, in S301, the server 100 acquires the current construction information and past construction history. In S302, the server 100 acquires the specific task and extraction conditions specified for the current construction. In S303, the server 100 extracts information on past tasks from the past construction history whose process patterns match those of the specific tasks and which also match the extraction conditions. The processing of S302 and S303 is as explained using FIG. 6. This makes it possible to narrow down past tasks using the extraction conditions.

[0073] In S304, the server 100 calculates aggregate data of the extracted information of the past tasks. The delay data included in the aggregate data includes the average number of delay days and the number of delay occurrences for each process of the past tasks, in addition to the delay rate of the past tasks and the delay occurrence rate of each process of the past tasks.

[0074] In S305, the server 100 predicts the predicted number of days for the specific task from the planned number of days and the actual number of days for each process of the specific task (a specific calculation method will be described later with reference to FIG. 10). In S306, the server 100 sets the planned number of days for the specific task, the planned number of days for each process of the specific task, and the actual number of days for the planned number of days.

[0075] As a result, the display unit 221 displays the schedule including the predicted number of days for the specific task. The display unit 221 also displays the schedule including the planned number of days for the specific task, the planned number of days for each step of the specific task, and the actual number of days compared to the planned number of days. As a result, it is possible to analyze the impact of delays on steps to be executed in the future while checking the actual number of days compared to the planned number of days.

[0076] A specific example will be described below with reference to Fig. 9. Fig. 9 is a diagram showing an example of a schedule. A schedule 91 in Fig. 5 is a schedule related to the first embodiment, and a schedule 92 in Fig. 9 is a schedule related to the second embodiment. Both show schedules for "creating an execution budget" (specific work).

[0077] In the second embodiment, the selected "Execution Budget Creation" (specific task) also displays the predicted number of days. In "Execution Budget Creation", the delay rate = 3.0%, planned number of days = 19 days, and predicted number of days = 20 days. Here, the planned number of days and predicted number of days indicate the planned number of days and predicted number of days for the current construction work. In contrast, the delay rate indicates the delay rate of past construction works.

[0078] In the second embodiment, the average number of days of delay, the number of delays, and the actual number of days are also displayed for each process. For example, for "Request for quotation creation", the delay rate is 5.0%, the average number of days of delay is 2.0 days, the number of delays is 5, the planned number of days is 3.0 days, and the actual number of days is 4.0 days.

[0079] For example, for 100 past tasks, if 95 requests for quotation were completed within the planned number of days (3 days), and 5 requests for quotation were completed after longer than the planned number of days (3 days), the delay rate would be calculated as 5.0% (= 5 / 100), and the number of delays would be calculated as 5. For example, if the planned number of days was 3 and the actual number of days was 5, the number of delays would be calculated as 2 days (= 5 days - 3 days). Average number of delays = 2.0 days indicates that the average number of delays for the 5 delayed tasks was 2.0 days.

[0080] Here, the delay rate, average number of delay days, and number of delay occurrences indicate the delay rate, average number of delay days, and number of delay occurrences of past construction works. In contrast, the planned number of days and actual number of days indicate the planned number of days and actual number of days of the current construction work. When the current construction work is in progress, the actual number of days input from the input unit 220 is reflected in the schedule.

[0081] For example, assume that the result of executing the process of creating a request for quotation is 4.0 days. When the user sets 4.0 days as the actual number of days for creating a request for quotation from the input unit 220, the input actual number of days is reflected in the process schedule. Note that for processes for which the actual number of days has not been input (not executed), nothing is displayed in the column for the number of actual days. Note that for simplicity, the columns for average number of delay days, number of delays, and actual number of days for the process from receipt by cooperating company to approval 3 are omitted in FIG. 9.

[0082] 7, the server 100 executes a display information generation process (FIG. 8) in S307. In S308, the server 100 outputs the display information (a process chart including the aggregated data) to the display unit, and ends the main process.

[0083] 8 is a flowchart of the display information generation process. When the display information generation process starts, the server 100 acquires the aggregated data and the current construction information in S401. In S402, the server 100 sets the display mode of the delay rate of the past work according to the delay rate (delay occurrence rate) of the past work. In S403, the server 100 sets the display mode of the delay rate of each process of the past work according to the delay rate of the process. The processes of S402 and S403 are the same as those of the first embodiment.

[0084] In S404, if the predicted number of days for a specific task exceeds the planned number of days, the server 100 sets the predicted number of days for the specific task in a predetermined display mode. In S405, if the actual number of days for each process of the specific task exceeds the planned number of days, the server 100 sets the actual number of days in a predetermined display mode.

[0085] As a result, when the predicted number of days for a specific task exceeds the planned number of days, the display unit 221 displays the predicted number of days for the specific task in a predetermined manner. When the actual number of days for each process of the specific task exceeds the planned number of days, the display unit 221 displays the actual number of days in a predetermined manner.

[0086] Specifically, as shown in Figure 9, the predicted number of days (20 days) for "Create execution budget" (specific task) exceeds the planned number of days (19 days), so "Predicted number of days: 20 days" is highlighted by surrounding it with a square. Also, for example, the actual number of days (4.0 days) for the "Create request for quotation" process exceeds the planned number of days (3.0 days), so "Actual number of days: 4.0 days" is highlighted by surrounding it with a square. This makes it easy to intuitively grasp the occurrence of delays. Note that the text may be highlighted in red.

[0087] Returning to Fig. 8, in S406, the server 100 sets an image showing the chronological relationship between processes. In S407, the server 100 sets the route requiring the maximum number of days in a display mode different from the other routes. The processes of S406 and S407 are the same as those of the first embodiment. In S408, the server 100 generates display information (aggregated data, process chart) and ends the display information generation process.

[0088] Next, the calculation of the predicted number of days for a specific task will be explained with reference to Fig. 10. Fig. 10 is a diagram for explaining the calculation of the predicted number of days. The server 100 predicts the number of days that are predicted to be required from the start to the end of a specific task based on the planned number of days for each process of the specific task and the actual number of days for the planned number of days, as the predicted number of days for the specific task. A specific explanation will be given below.

[0089] As shown in Figure 10, in "Preparing the execution budget," the planned number of days for each process on path 3 (critical path) is as follows: Drawing preparation: 4 days, Approval 2: 1 day, Receipt from partner company: 1 day, Site inspection: 1 day, Estimate preparation: 5 days, Estimate reception: 1 day, Preparation of execution budget: 5 days, Approval 3: 1 day. The planned number of days for "Preparing the execution budget" (specific task) = the sum of the planned days for each process on path 3 (critical path) (19 days).

[0090] If none of the steps have been performed, no actual number of days has been set for any of the steps. In this case, the sum of the planned days for each step in Route 3 = the predicted number of days for "Preparing the execution budget" (specific task) (19 days).

[0091] Here, assume that a drawing is created and the required number of days is 5 days. In this case, 5 days is set as the actual number of days for drawing creation. For processes for which actual number of days is set, the actual number of days is used to calculate the predicted number of days. In this example, the predicted number of days for specific tasks is 20 days, which is the sum of actual number of days for drawing creation: 5 days, planned number of days for approval 2: 1 day, planned number of days for receipt from partner company: 1 day, planned number of days for site inspection: 1 day, planned number of days for quotation creation: 5 days, planned number of days for quotation receipt: 1 day, planned number of days for execution budget creation: 5 days, and planned number of days for approval 3: 1 day. In this way, the predicted number of days for specific tasks is updated every time the actual number of days is input.

[0092] Furthermore, suppose that approval 2 is carried out and the number of days required (actual days) is one day. In this case, since this matches the planned number of days for approval 2, the predicted number of days for the specific task remains at 20 days. In this way, the actual number of days is updated, and in approval 3, the actual number of days exceeds the planned number of days by one day. In this case, the predicted number of days for the specific task increases by one day to 21 days.

[0093] In the above, for simplicity, the predicted number of days for a specific task is calculated based on the planned number of days and the actual number of days for path 3, but in reality, the predicted number of days for a specific task is calculated taking into account the actual number of days for paths 1 and 2 as well. For example, in the example of Figure 9, assume that the actual number of days for specification creation = 7 days. In this case, since this exceeds the actual number of days for drawing creation (5 days) in the example of Figure 10 by 2 days, approval 2 will be given after waiting for the specification creation. As a result, the predicted number of days for a specific task = 23 days (21 days + 2 days).

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

[0095] In this embodiment, the display unit 221 can display each step of a specific task in descending order of the delay occurrence rate of each step in past tasks, according to a user's instruction. Hereinafter, the method will be described with reference to FIGS.

[0096] 11 is a flowchart of the sorting process. The sorting process is executed when a command to display in descending order of the delay occurrence rate is received from the user. After the sorting process is executed, the display on the display unit 221 is updated.

[0097] When the sorting process starts, the server 100 acquires the delay rate of each process in the past tasks in S601. The server 100 determines the display order of each process of the specific tasks in descending order of delay rate in S602, and ends the sorting process.

[0098] A specific description will be given below with reference to Fig. 12. Fig. 12 is a diagram showing an example of a process schedule. In the display of Fig. 9, the delay rates of each process are as follows: request for quotation: 5.0%, approval 1: 0.4%, specification creation: 3.0%, drawing creation: 5.0%, approval 2: 0.4%, receipt from partner company: 0.3%, site inspection: 0.5%, quotation creation: 2.5%, quotation receipt: 0.5%, working budget creation: 2.5%, approval 3: 0.4%.

[0099] The display unit 221 displays the above in descending order of delay rate. As shown in Fig. 12, drawing creation and quotation request creation, which have the highest delay rate (5.0%), are displayed at the top. The specification creation, which has the next highest delay rate (3.0%), is displayed below drawing creation and quotation request creation.

[0100] In the same way, the order of delays is displayed as follows: Estimate creation, Execution budget creation (2.5%), Site inspection, Estimate receipt (0.5%), Approval 1, Approval 2, Approval 3 (0.4%), and Partner company receipt (0.3%). By doing this, it becomes easier to analyze which processes are likely to cause delays.

[0101] In the first and second embodiments, examples in which the schedules shown in Fig. 5 and Fig. 9 are applied have been described. However, the present invention is not limited to this, and the schedule may be a bar chart schedule that displays a bar chart, a network schedule, or any other schedule may be applied. For example, when a bar chart schedule is applied, the delay rate, the number of delays, the planned number of days, and the actual number of days may be displayed in association with the bar chart that indicates the process.

[0102] As explained above, in this embodiment, information such as the number of delays, delay rate, and average number of days delayed based on past construction history is added to all processes, filtering is performed based on extraction conditions, the display can be sorted to make delay analysis easier, and the number of actual days for the current construction work compared to the planned number of days is displayed while the predicted number of days for a specific task is updated in real time. This information is displayed in a list on the process chart, and processes with high delay rates and processes whose actual number of days exceeds the planned number of days are highlighted. In particular, this embodiment is characterized by the ability to perform analysis from both the actual delay status of the current construction work (predicted number of days, actual number of days) and the delay status of past construction works (delay rate, etc.).

[0103] This makes it possible to predict which work processes may experience delays, and analyze the causes of delays and their effects on processes. As a result, construction management can be carried out to strictly adhere to delivery deadlines, such as improving the accuracy of work time estimates, improving the accuracy of project completion date predictions that take work delays into account, and preventing work delays by following up on work processes with high delay rates. This allows even inexperienced construction managers to efficiently manage construction.

[0104] The embodiments disclosed herein are also intended to be combined as appropriate within the scope of technical inconsistency. The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The technical scope of the present disclosure is defined by the claims, not the description of the above embodiments, and is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0105] 1 construction management system, 91-93 schedule, 100 server, 111, 211 control unit, 112, 212 memory unit, 113, 213 communication unit, 121 extraction unit, 122 aggregation unit, 123 generation unit, 200 terminal, 220 input unit, 221 display unit.

Claims

1. A construction management system for managing construction work, This construction project includes specific work consisting of multiple processes, A control unit that generates a schedule for the specific task; A display unit that displays the process chart; A storage unit that stores information on past construction work as a construction history, The control unit is Extracting information on past work whose process pattern matches that of the specific work from the construction history; Calculating aggregate data of the extracted past business information; The aggregated data includes delay data regarding delays to plans in the past operations, A construction management system in which the display unit displays the aggregated data including the delay data together with the schedule.

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 display unit is A display mode of the delay occurrence rate of the past work is changed according to the delay occurrence rate of the past work; The construction management system according to claim 2 , wherein a display mode of the delay occurrence rate of each process of the past work is changed depending on the delay occurrence rate of the process.

4. The construction management system according to claim 2 , wherein the delay data further includes an average number of delay days and a number of delay occurrences for each process of the past work.

5. The display unit is displaying the process chart including the planned number of days for the specific task, the planned number of days for each step of the specific task, and the actual number of days for each planned number of days; 2. The construction management system according to claim 1, wherein when the actual number of days for each process of the specific work exceeds the planned number of days, the actual number of days is displayed in a predetermined format.

6. The control unit predicts the number of days that are predicted to be required from the start to the end of the specific task based on the planned number of days for each process of the specific task and the actual number of days for the planned number of days, as the predicted number of days for the specific task; The display unit is Furthermore, the process schedule is displayed including the estimated number of days for the specific task, The construction management system according to claim 5 , wherein, when the predicted number of days for the specific task exceeds the planned number of days, the predicted number of days for the specific task is displayed in the predetermined manner.

7. The display unit is Displaying the plurality of steps in chronological order together with images showing the relationship between the steps; The construction management system according to claim 1 , wherein, among the multiple routes in the multiple processes, the route that requires the longest number of days from the start to the end of the specific task is displayed in a manner different from other routes.

8. further comprising an input unit for receiving an input from a user; the input unit is capable of accepting input of one or more conditions among a time when the past work was performed, an area where the past work was performed, the weather when the past work was performed, a contractor of the past work, a manager of the past work, and an approver of the past work, as extraction conditions for extracting the past work from the construction history; The construction management system according to any one of claims 1 to 7, wherein the past work is a work in the construction history that has a process pattern that matches the specific work and that matches the extraction conditions.

9. The construction management system according to claim 2 , wherein the display unit displays each process of the specific work in descending order of the delay occurrence rate of each process in the past work.

10. A computer-implemented construction management method for managing construction work, comprising: This construction project includes specific work consisting of multiple processes, generating a schedule for the specific task; displaying the schedule; and storing information on past construction work as a construction history; The generating step includes: Extracting information on past work having a process pattern matching that of the specific work from the construction history; and calculating aggregate data of the extracted past business information; The aggregated data includes delay data regarding delays to plans in the past operations, The construction management method, wherein the display step includes a step of displaying the aggregated data including the delay data together with the schedule.

Images