JP7705336B2 - Progress management device, progress management method, and progress management program - Google Patents

Description

The present invention relates to a progress management device, a progress management method, and a progress management program.

For example, in the past, when managing the progress of construction work, on-site staff would judge each situation based on figures based on the rate of completion, while accounting and management would grasp the progress of construction work and the income/expense situation based on figures proportional to cost. For example, Patent Document 1 is an example of a conventional system for managing progress.

JP 2017-174241 A

However, Patent Document 1 does not state anything about objectively understanding the progress and balance of construction work.

The present invention has been made in consideration of the above, and aims to provide a progress management device, a progress management method, and a progress management program that can objectively grasp the progress and income/expense status of a project.

In order to solve the above-mentioned problems and achieve the object, the present invention is characterized in that the control unit is provided with a cost processing means for creating a cost-proportional value when a project is accepted, a performance processing means for creating a performance-based value when the project is accepted, and a comparison means for comparing the cost-proportional value with the performance-based value to grasp the progress and income/expense situation of the accepted project.

According to one aspect of the present invention, the cost-proportional figures may include actual costs and actual revenues on a cost-proportional basis, and the volume-based figures may include forecast volume and actual volume on a volume-based basis.

According to one aspect of the present invention, the comparison means may determine the progress of the construction work by comparing the predicted progress and the actual progress, and if the predicted progress - the actual progress is < 0, determine that the project is progressing ahead of schedule, if the predicted progress - the actual progress = 0, determine that the project is progressing at the scheduled pace, and if the predicted progress - the actual progress > 0, determine that the project is behind schedule.

According to one aspect of the present invention, the comparison means may determine the balance situation by comparing the actual revenue and the actual turnover, and if actual revenue - actual turnover < 0, determine that the balance situation is improving, if actual revenue - actual turnover = 0, determine that the balance situation is as planned, and if actual revenue - actual turnover > 0, determine that the balance situation is worsening.

According to one aspect of the present invention, the case may include a construction-related case.

In order to solve the above-mentioned problems and achieve the objective, the present invention is a progress management method executed by an information processing device equipped with a control unit, characterized in that it includes a cost processing step executed by the control unit for creating a cost-proportional value when a case is accepted, a production volume processing step for creating a production volume-based value when the case is accepted, and a comparison step for comparing the cost-proportional value with the production volume-based value to grasp the progress status and income/expense status of the accepted case.

In order to solve the above-mentioned problems and achieve the object, the present invention is characterized in that the progress management program is executed by an information processing device having a control unit, and causes the control unit to execute a cost processing step of creating a cost-proportional value when a case is accepted, a production volume processing step of creating a production volume-based value when the case is accepted, and a comparison step of comparing the cost-proportional value with the production volume-based value to grasp the progress status and income/expense status of the accepted case.

The present invention has the effect of making it possible to objectively grasp the progress and income/expense status of a project.

FIG. 1 is a diagram for explaining the problems that arise when only figures proportional to cost are used. FIG. 2 is a diagram for explaining the problems that arise when only volume-based figures are used. FIG. 3 is a diagram for explaining the improvement method of the present invention. FIG. 4 is a block diagram showing an example of the configuration of the progress management device according to the present embodiment. FIG. 5 is a flowchart for explaining an outline of the overall processing of the control unit of the progress management device according to the present embodiment. FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the progress management device according to the present embodiment. FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the progress management device according to the present embodiment. FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the progress management device according to the present embodiment. FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the progress management device according to the present embodiment. FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the progress management device according to the present embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
For example, in the construction industry, it takes several years to complete a single project, making progress management and revenue forecasting an issue for many companies. In the construction industry, revenue forecasts and progress management are carried out using the cost-proportional method, but if costs are incurred, sales will increase even if work is not progressing, so it can be difficult to make correct judgments depending on the circumstances of cost occurrence. As a method other than the cost-proportional method, there is also a method that uses the volume of work, but although it can accurately grasp the progress status, it is difficult to grasp whether the balance is deteriorating.

In other words, in the past, on-site employees judged each situation based on figures based on the completion rate, while accounting and management understood the progress of construction and the income/expense situation based on figures proportional to cost. However, while the completion rate is suitable for understanding the progress of construction, it is inappropriate for understanding the income/expense situation, and the cost-proportional method sometimes does not accurately represent the current situation in terms of both progress and income/expense understanding.

Therefore, in this embodiment, by comparing figures based on a volume of work and figures based on a cost-proportional basis for construction projects and other such projects, it is possible to objectively, accurately, and easily grasp the progress and income/expense situation of a project.

The background and problems of the present invention will be specifically explained with reference to Figures 1 and 2. With reference to Figure 1, the problems that arise when only cost-proportional figures are used will be explained. Figure 1 is a diagram for explaining the problems that arise when only cost-proportional figures are used. Figure 1(A) is a diagram showing an example of a cost-proportional budget consumption forecast "A". Figure 1(B) is a diagram showing an example of actual costs and actual revenues [B]. In the following explanation, all monetary units are in thousands of yen, and descriptions of these will be omitted.

The following explanation uses an example where the contract amount is "100,000" and the budget amount is "80,000".

In Figure 1 (A), when using cost proportionality, the forecast value is calculated based on the forecast of the budget consumption rate (progress rate). The example shown in Figure 1 (A) shows the consumption rate, consumption amount, and forecast revenue (= contract amount x total consumption amount for the target Q / total budget amount) for 1Q to 4Q, with the cost elements being material costs, subcontract costs, labor costs, and expenses.

For example, the projected revenue for 1Q is the contract amount "100,000" x the total amount spent in 1Q "25,000" ÷ the total budget "80,000" = "31,250".

Figure 1 (B) shows an example of actual costs and actual revenues [B] for the budget consumption forecast based on cost proportion in Figure 1 (A). In Figure 1 (B), the difference from the forecast is that the forecast for 1Q of outsourcing costs is a consumption rate of "20%", a consumption amount of "4,000", and a revenue forecast for 1Q of "31,250", while the actual results for 1Q of outsourcing costs are a consumption rate of "25%, a consumption amount of "5,000", and a revenue actual of "32,250" (= contract amount "100,000" x total consumption amount for 1Q "25,000" ÷ total budget "80,000").

In addition, the forecast for outsourcing expenses in the fourth quarter is a usage rate of 20%, a usage amount of 4,000, and a revenue forecast of 16,250, while the actual outsourcing expenses in the fourth quarter are a usage rate of 15%, a usage amount of 3,000, and a revenue forecast of 15,000.

Looking at the first half revenue up to 2Q, the actual result of 53,750 is higher than the initial forecast of 52,500, so at first glance it looks like things are going well. However, material costs are simply recorded as costs all at once when they are delivered to the materials storage area on-site (1Q and 3Q), and do not indicate whether the work itself is progressing smoothly. In addition, outsourcing costs are higher than initially planned, and it is not possible to determine whether this is due to work being brought forward, such as starting earlier, or whether the work progress has been delayed and more outsourced staff have been added.

The issues that arise when only volume-based figures are used will be explained with reference to Figure 2. Figure 2 is a diagram for explaining the issues that arise when only volume-based figures are used. Figure 2 (A) shows a volume-based forecast [C], and Figure 2 (B) shows volume-based actual results [D].

The example shown in Figure 2 (A) shows the contract details, number of contracts, unit price, and amount, as well as the volume and amount of work completed from Q1 to Q4. Figure 2 (B) shows an example of actual results [D] against the volume-based forecast in Figure 2 (A).

In Figure 2 (B), the differences from the forecast are that for the contract details (steel pipe piles, φ600, t=9-10, L=6.5-13m), the forecast for 1Q was a volume of "25" and a volume amount of "25,000," whereas the actual results for 1Q were a volume of "26" and a volume amount of "26,000," and the forecast for 4Q was a volume of "21" and a volume amount of "21,000," whereas the actual results for 4Q were a volume of "20" and a volume amount of "20,000."

Looking at the first half of the year revenue up to 2Q, the actual result of 53,500 is higher than the initial forecast of 52,500, so at first glance it looks like things are going well. However, because no cost has been taken into account, it is impossible to tell whether the balance is progressing as planned or has deteriorated. In the cost-proportional revenue forecast in (1), first half revenue up to 2Q is 53,750, but on a volume basis it is 53,500, which means that the balance has deteriorated slightly for the first half.

In this way, while a volume-of-production basis is suitable for understanding the progress of construction work, it is inappropriate for understanding the income and expenditure situation, and a cost-proportional basis does not accurately represent the current situation in terms of either progress or income and expenditure.

Figure 3 is a diagram for explaining the improvement method of the present invention. In the present invention, by calculating KPIs for each construction project that combine the numerical values of the above-mentioned actual cost and actual revenue on a cost-proportional basis [B], projected volume on a volume basis [C], and actual volume on a volume basis [D], it is possible to objectively grasp the progress status and income/expense situation. The following describes the 2Q forecast as an example.

(1) The progress of the construction work is judged by comparing the total amount of the forecasted progress [C] and the actual progress [D] based on the amount of work completed.

i) If [C] - [D] < 0, the actual progress is greater than the forecast progress, so it is determined that the construction is progressing ahead of schedule.

ii) If [C] - [D] = 0, the forecasted volume and actual volume are the same, so it is determined that progress is proceeding as planned.

iii) If [C] - [D] > 0, the actual volume is less than the forecast volume, so it is determined that there is a delay in the progress of the construction work.

(2) The income/expense forecast is determined by comparing the total amount of actual revenue [B] based on a cost-proportional basis and actual volume of work [D] based on volume of work.

i) If [B] - [D] < 0, it is determined that the balance of income and expenditure has improved because less costs have been incurred and more output has been achieved than planned.

ii) If [B] - [D] = 0, the increase in output is exactly equivalent to the cost incurred, so it is determined that the income/expense situation is as planned.

iii) If [B] - [D] > 0, it is determined that the income statement is deteriorating because the costs incurred are higher than expected in relation to the volume of work.

For each indicator, the larger the difference, the greater the deviation from the initial plan, which is also effective in identifying projects that require early action.

The progress management device of the present invention can be applied not only to the construction industry, but also to IT vendors who conduct scratch development, etc.

2. Configuration
An example of the configuration of the progress management device according to the present embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the configuration of the progress management device according to the present embodiment.

The progress management device 100 is a commercially available desktop personal computer. Note that the progress management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

The progress management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the progress management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the progress management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the progress management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work with the OS (Operating System) to give commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 also includes a data file 106a and a cost element master 106b.

Data file 106a is a file for storing various data such as order data, budget data, quarterly budget data, cost-proportional budget consumption forecast data, forecast volume data (forecast volume header data, forecast volume detail data), volume-based forecast, cost summary data, actual costs and revenues, actual volume data, volume-based actual results, etc.

The order data may include the construction number and contract amount. The budget data may include data on the construction number, cost element CD, and budget amount. The quarterly budget data may include data on the construction number, cost element CD, fiscal year, quarter, and completion rate.

The cost-proportional budget consumption forecast may include cost elements, budget amount, progress rate for each quarter (Q1-Q4), and consumption amount.

The forecasted volume data may be composed of forecasted volume header data and forecasted volume detail data. The forecasted volume header data may include data on the construction number, SEQ, contract details, number of contracts, unit price, and amount. The forecasted volume detail data may include data on the construction number, SEQ, fiscal year, quarter, and volume.

Volume-based forecasts may include contract details, number of contracts, unit price, amount, and volume and amount of volume for each quarter (1Q to 4Q).

The cost summary data may include data on the construction number, cost element CD, accounting year and month, cost element code, and amount incurred.

The actual cost and revenue may include cost elements, budget amounts, progress rates, amounts consumed, and revenue amounts for each quarter (1Q to 4Q).

The performance data may include the construction number, SEQ, fiscal year, quarter, and amount of work completed. Performance data based on performance may include the contract details, number of contracts, unit price, amount, and amount and amount of work completed for each quarter (1Q to 4Q).

The cost element master 106b can be configured as a table in which cost elements CD and cost element names are associated and registered (see Figure 7). The cost element master 106b is referenced when converting between cost elements CD and cost element names.

The control unit 102 is a CPU or the like that performs overall control of the progress management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. In terms of function and concept, the control unit 102 includes an order registration unit 102a, a cost processing unit 102b, a performance processing unit 102c, a comparison unit 102d, and a screen display control unit 102e.

When an order is received, the order registration unit 102a inputs order data and registers it in the data file 106a, for example, in response to an operator's operation on an order registration screen (not shown) displayed on the monitor 114.

The cost processing unit 102b creates a cost-proportional basis numerical value for the case that is the subject of the order data, for example, in response to an operator's operation on a cost registration screen (not shown) displayed on the monitor 114, and registers the value in the data file 106a. The cost-proportional basis numerical value may include actual costs and actual revenues on a cost-proportional basis.

The volume processing unit 102c creates volume-based figures for the cases that are the subject of the order data, for example, in response to the operator's operations on a volume registration screen (not shown) displayed on the monitor 114, and registers the figures in the data file 106a. The volume-based figures may include volume-based forecast volume and actual volume.

The comparison unit 102d, for example, in response to an operator's operation on a comparison screen (not shown) displayed on the monitor 114, compares the cost-proportional value and the volume-based value for the target project, and displays and outputs the results of the progress and income/expenses judgment.

Specifically, the comparison unit 102d may compare the predicted volume and the actual volume to determine the progress, and if the predicted volume - the actual volume < 0, determine that the project is progressing ahead of schedule, if the predicted volume - the actual volume = 0, determine that the project is progressing at the scheduled pace, and if the predicted volume - the actual volume > 0, determine that the project is behind schedule, and display a message to that effect.

The comparison unit 102d may compare the actual revenue and actual turnover for the income/expense forecast, and if actual revenue - actual turnover < 0, determine that the income/expense situation is improving, if actual revenue - actual turnover = 0, determine that the income/expense situation is as planned, and if actual revenue - actual turnover > 0, determine that the income/expense situation is worsening, and display and output this fact.

The screen display control unit 102e controls the display and input of various screens (e.g., order registration screen, cost registration screen, output registration screen, comparison screen, etc.) displayed on the monitor 114.

3. Specific Examples
A specific example of the processing of the progress management device 100 in this embodiment will be described with reference to Figures 4 to 10. First, an overview of the overall processing of the progress management device 100 in this embodiment will be described with reference to Figure 5. Figure 5 is a diagram showing a flow for explaining the overview of the overall processing of the progress management device 100 in this embodiment.

In FIG. 5, the order registration unit 102a executes the order registration process (step S1). Specifically, in the order registration process, when an order is received, the order registration unit 102a inputs order data and registers it in the data file 106a in response to, for example, an operator's operation on an order registration screen (not shown) displayed on the monitor 114.

The cost processing section 102b executes the budget registration process (step S2). Specifically, in the budget registration process, the cost processing section 102b inputs budget data, quarterly budget data, and a cost-proportional budget consumption forecast for the case that is the subject of the order data, for example, in response to an operator's operation on a cost registration screen (not shown) displayed on the monitor 114, and registers the data in the data file 106a.

The production volume processing unit 102c executes production volume forecast registration processing (step S3). Specifically, in the production volume forecast registration processing, the production volume processing unit 102c inputs forecast production volume header data, forecast production volume detail data, and production volume-based forecasts for the case that is the subject of the order data, for example, in response to an operator's operation on a production volume registration screen (not shown) displayed on the monitor 114, and registers them in the data file 106a.

The cost processing section 102b executes the construction execution process (step S4). Specifically, in the construction execution process, the cost processing section 102b inputs the cost summary data, the actual cost on a cost proportional basis, and the actual revenue for the case that is the subject of the order data, for example, in response to the operator's operation on a cost registration screen (not shown) displayed on the monitor 114, and registers them in the data file 106a.

The production volume processing unit 102c executes the production volume record registration process (step S5). Specifically, in the production volume record registration process, the production volume processing unit 102c inputs production volume record data and production volume-based record data for the case that is the subject of the order data in response to, for example, the operator's operation on the production volume registration screen (not shown) displayed on the monitor 114, and registers them in the data file 106a.

The comparison unit 102d executes a comparison process (step S6). Specifically, in the comparison process, the comparison unit 102d compares the cost-proportional value and the volume-based value for the target project in response to, for example, an operator's operation on a comparison screen (not shown) displayed on the monitor 114, and displays and outputs the results of the progress status and the income/expense status.

In this case, the comparison unit 102d may compare the predicted volume and the actual volume to determine the progress, and if the predicted volume - the actual volume < 0, determine that the project is progressing ahead of schedule, if the predicted volume - the actual volume = 0, determine that the project is progressing at the scheduled pace, and if the predicted volume - the actual volume > 0, determine that the project is behind schedule, and display a message to that effect.

The comparison unit 102d may also compare the actual revenue and actual turnover for the income/expense forecast, and if actual revenue - actual turnover < 0, determine that the income/expense situation is improving, if actual revenue - actual turnover = 0, determine that the income/expense situation is as planned, and if actual revenue - actual turnover > 0, determine that the income/expense situation is worsening, and display and output to that effect.

Next, a specific example of the processing of the control unit 102 of the progress management device 100 in this embodiment will be described with reference to Figures 6 to 10. Figures 6 to 10 are diagrams for explaining a specific example of the processing of the control unit 102 of the progress management device 100 in this embodiment.

(S1: Order registration process)
The order registration process will be described with reference to Fig. 6. Fig. 6 is a diagram for explaining the order registration process. When an order is received, the order registration unit 102a inputs order data in response to an operation by an operator on an order registration screen (not shown) displayed on the monitor 114, and registers the data in the data file 106a.

Figure 6 shows an example of (1) order data. In the example of (1) order data shown in Figure 6, the first line has the construction number "100" and the contract amount "100,000", and the second line has the construction number "101" and the contract amount "200,000". The construction number "100" and the contract amount "100,000" will be explained below.

(S2: Budget registration process)
The budget registration process will be described with reference to Fig. 7. Fig. 7 is a diagram for explaining the budget registration process. The cost processing unit 102b inputs budget data, quarterly budget data, and a cost-proportional budget consumption forecast for a case that is the subject of the order data in response to, for example, an operator's operation on a cost registration screen (not shown) displayed on the monitor 114, and registers the input data in the data file 106a.

Figure 7 (A) shows an example of (2) budget data. In the example of (1) budget data shown in Figure 7 (A), the first line has the construction number "100", cost element CD "100", and budget amount "20,000", the second line has the construction number "100", cost element CD "200", and budget amount "20,000", the third line has the construction number "100", cost element CD "300", and budget amount "20,000", and the fourth line has the construction number "100", cost element CD "400", and budget amount "20,000", with the total cost budget being "80,000".

Figure 7 (B) shows an example of the cost element master 106b. In the example of the cost element master 106b shown in Figure 7 (B), the first line has a cost element CD of "100" and a cost element name of "material cost", the second line has a cost element CD of "200" and a cost element name of "outsourcing cost", the third line has a cost element CD of "300" and a cost element name of "labor cost", and the fourth line has a cost element CD of "400" and a cost element name of "expense". The cost element master 106b is referenced when converting the cost element CD and the cost element name, for example, when converting the cost element CD of the budget data and the quarterly budget data to the "cost element name" of the budget consumption forecast based on a cost proportional basis.

Figure 7 (C) shows an example of budget data by second half of the year. In the example of quarterly budget data shown in Figure 7 (C), the first line contains the construction number "100", cost element CD "100", fiscal year "2020", quarter "1", and completion rate "50".

Figure 7 (D) shows an example of a cost-proportional budget consumption forecast [A]. In the example of a cost-proportional budget consumption forecast [A] shown in Figure 7 (D), the first line shows the following for the cost element "material cost": budget amount "20,000", progress rate for 1Q "50%", consumption amount "10,000", progress rate for 2Q "0%", consumption amount "0", progress rate for 3Q "50%", consumption amount "10,000", progress rate for 4Q "0%", consumption amount "0". Here, the cost elements and budget amount are obtained from (2) budget data. The consumption rate is obtained from the performance rate of the (2) quarterly budget data. The consumption amount is calculated by multiplying (2) budget data by the performance rate (consumption rate) of the (3) quarterly budget data (for example, the consumption amount of material cost for 1Q is 20,000 x 50% = 10,000).

In addition, the forecast revenue is 31,250 for 1Q, 21,250 for 2Q, 31,250 for 3Q, and 16,250 for 4Q. The forecast revenue is calculated by (1) contract data x (3) total amount spent for the corresponding Q in the quarterly budget data ÷ (2) total budget for the budget data. For example, the forecast revenue for 1Q is 100,000 contract amount x 25,000 total amount spent for 1Q ÷ 80,000 total budget = 31,250.

(S3: Production volume forecast registration process)
The production volume forecast registration process will be described with reference to Fig. 8. Fig. 8 is a diagram for explaining the production volume forecast registration process. The production volume processing unit 102c creates forecast production volume header data, forecast production volume detail data, and production volume-based forecasts for the case of the target of the order data in response to, for example, an operator's operation on a production volume registration screen (not shown) displayed on the monitor 114, and registers them in the data file 106a.

Figure 8 (A) is a diagram showing an example of (4) forecasted volume header data. In the example of (4) forecasted volume header data shown in Figure 8 (A), the first line contains the construction number "100", SEQ "1", contract details "Steel pipe pile φ600 t=9-10 L=6.5-13m", number of contracts "95", unit price "1,000", and amount "95,000".

Figure 8 (B) is a diagram showing an example of (5) forecasted progress detail data. In the example of (5) forecasted progress detail data shown in Figure 8 (B), the construction number is "100", SEQ is "1", fiscal year is "2020", quarter is "1", and progress amount is "25".

Figure 8 (C) is a diagram showing an example of a volume-based forecast [C]. In the example of volume-based forecast [C] shown in Figure 8 (C), the first line shows the contract details "Steel pipe piles φ600 t=9-10 L=6.5-13m", number of contracts "95", unit price "1,000", amount "95,000", 1Q volume "25", volume amount "25,000", 2Q volume "25", volume amount "25,000", 3Q volume "24", volume amount "24,000", 4Q volume "21", volume amount "21,000".

Here, the contract details, number of contracts, unit price, and amount are obtained from (4) forecasted volume header data. The volume is obtained from (5) forecasted volume detail data. The volume amount is calculated from (4) forecasted volume header data and (5) forecasted volume detail data.

The total trading volume for 1Q is 27,500, the total trading volume for 2Q is 25,000, the total trading volume for 3Q is 26,500, and the total trading volume for 4Q is 21,000.

(S4: Construction implementation process)
The construction execution process will be described with reference to Fig. 9. The construction execution process will be described with reference to Fig. 9. The cost processing section 102b inputs cost compilation data, actual costs proportional to costs, and actual revenues for the case of the order data in response to, for example, an operator's operation on a cost registration screen (not shown) displayed on the monitor 114, and registers the data in the data file 106a. The cost compilation data is compiled by cost calculation from data such as material purchases and subcontract cost.

Figure 9 (A) is a diagram showing an example of (6) cost summary data. In the example of (6) cost summary data shown in Figure 9 (A), the first line contains the construction number "100", cost element CD "100", accounting year/month "202004", cost element code "100", and incurred amount "3,000".

Figure 9 (B) shows an example of actual costs and actual revenues [B] for the budget consumption forecast based on cost proportion in Figure 7 (D). Here, the cost elements and budget amount are obtained from (2) budget data. The consumption amount is the total amount for each period in (6) cost aggregation data (for example, the material cost for 1Q is 3,000 + 3,000 + 4000 = 10,000). The consumption rate is the consumption amount divided by the budget amount in (2) budget data (for example, the consumption rate for material cost for 1Q is 10,000 ÷ 20,000 = 50%).

In Figure 9 (B), the differences from the forecast are that the forecast for outsourcing costs in 1Q is a consumption rate of 20%, a consumption amount of 4,000, and a forecast for revenue in 1Q of 31,250, while the actual results for outsourcing costs in 1Q are a consumption rate of 25%, a consumption amount of 5,000, and a revenue actual of 32,250 (= contract amount of 100,000 x total consumption amount in 1Q of 25,000 ÷ total budget of 80,000).

In addition, the forecast for outsourcing expenses in the fourth quarter is a usage rate of 20%, a usage amount of 4,000, and a revenue forecast of 16,250, while the actual outsourcing expenses in the fourth quarter are a usage rate of 15%, a usage amount of 3,000, and a revenue forecast of 15,000.

(S5: Production volume record registration process)
The production volume record registration process will be described with reference to Fig. 10. Fig. 10 is a diagram for explaining the production volume record registration process. The production volume processing unit 102c inputs production volume record data and production volume record on a production volume basis for a case that is the subject of the order data in response to, for example, an operator's operation on a production volume registration screen (not shown) displayed on the monitor 114, and registers the data in the data file 106a.

Figure 10 (A) is a diagram showing an example of actual progress data. In the example of actual progress data shown in Figure 10 (A), the first line shows the construction number "100", SEQ "1", year "2020", quarter "1", and progress "26", while the second line shows the construction number "100", SEQ "2", year "2020", quarter "1", and progress "0.5".

Figure 10 (B) shows an example of actual results [D] for the volume-based forecast in Figure 8 (C). Here, the contract details, number of contracts, unit price, and amount are obtained from (4) forecast volume header data. The volume amount is obtained from (7) actual volume data. The volume amount is calculated by multiplying the unit price in (4) forecast volume header data by the volume amount in (7) actual volume data.

In Figure 10 (B), the differences from the forecast are that for the contract details (steel pipe piles, φ600, t=9-10, L=6.5-13m), the forecast for 1Q was a volume of "25" and a volume amount of "25,000," whereas the actual results for 1Q were a volume of "26" and a volume amount of "26,000," and the forecast for 4Q was a volume of "21" and a volume amount of "21,000," whereas the actual results for 4Q were a volume of "20" and a volume amount of "20,000."

(S6: Comparison process)
The comparison unit 102d compares the cost-proportional figures with the volume-based figures for the target project in response to, for example, an operator's operation on a comparison screen (not shown) displayed on the monitor 114, and displays and outputs the results of the progress and income/expense situation.

The comparison unit 102d may compare the predicted volume of work [C] and the actual volume of work [D] to determine the progress status. If the predicted volume of work [C] - the actual volume of work [D] is less than 0, it may determine that the project is progressing ahead of schedule. If the predicted volume of work [C] - the actual volume of work [D] is equal to 0, it may determine that the project is progressing at the planned pace. If the predicted volume of work [C] - the actual volume of work [D] is greater than 0, it may determine that the project is behind schedule, and may display and output this information. Note that the comparison may be made based on the total contract content or on a per-contract content basis.

In the above example (Figures 8 and 10), looking at the first half revenue up to 2Q, the total forecast volume "52,500" - the total actual volume "53,500" is < 0, so for example, the display will show "Regarding progress, projects are moving ahead of schedule up to 2Q."

The comparison unit 102d may also compare the income/expense situation with the actual revenue [B] and the actual turnover [D], and if the actual revenue [B] - actual turnover [D] is less than 0, determine that the income/expense situation is improving, if the actual revenue [B] - actual turnover [D] is equal to 0, determine that the income/expense situation is as planned, and if the actual revenue [B] - actual turnover [D] is greater than 0, determine that the income/expense situation is worsening, and display and output this fact.

In the above example (Figures 9 and 10), looking at the first half revenue up to 2Q, the total actual revenue "53,750" - the total actual volume "53,500" is > 0, so for example, the following message will be displayed: "Regarding the income/expense situation, the income/expense situation has worsened up to 2Q."

As described above, according to this embodiment, there are provided a cost processing unit 102b that creates a cost-proportional value when a project is accepted, a production volume processing unit 102c that creates a production volume-based value when a project is accepted, and a comparison unit 102d that compares the cost-proportional value with the production volume-based value to grasp the progress and income/expense situation of the accepted project, making it possible to objectively grasp the progress and income/expense situation of the project.

[4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to SDGs goals 12, 13, and 15.In addition, this embodiment can contribute to strengthening control and governance, which can contribute to SDGs goal 16.

5. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the progress management device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the progress management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the progress management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the progress management device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The progress management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The progress management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

REFERENCE SIGNS LIST 100 Progress management device 102 Control unit 102a Order registration unit 102b Cost processing unit 102c Output processing unit 102d Comparison unit 102e Screen display control unit 104 Communication interface unit 106 Storage unit 106a Data file 106b Cost element master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (4)

A progress management device including a control unit,
The control unit is
a cost processing means for creating actual costs and actual revenues on a cost-proportional basis when a project is accepted;
a production amount processing means for generating a production amount-based forecast production amount and a performance amount when the job is accepted;
a comparison means for judging the progress of the construction work by comparing the predicted progress with the actual progress, judging that the project is progressing ahead of schedule if the predicted progress - the actual progress < 0, judging that the project is progressing at the planned pace if the predicted progress - the actual progress = 0, and judging that the project is behind schedule if the predicted progress - the actual progress > 0, and judging the balance situation by comparing the actual revenue with the actual progress, judging that the balance situation is improving if the actual revenue - the actual progress < 0, judging that the balance situation is as planned if the actual revenue - the actual progress = 0, and judging that the balance situation is worsening if the actual revenue - the actual progress >0;
A progress management device comprising: The progress management device according to claim 1 , wherein the items include items related to construction work. A progress management method executed by an information processing device having a control unit,
The control unit executes :
A cost processing step for creating actual costs and actual revenues based on a cost-proportional basis when a project is accepted;
a volume processing step for creating a volume-based forecast volume and an actual volume when the order is received;
a comparison process for judging the progress of the construction work by comparing the forecasted progress with the actual progress, judging that the project is progressing ahead of schedule if the forecasted progress - the actual progress is < 0, judging that the project is progressing at the planned pace if the forecasted progress - the actual progress is = 0, judging that the project is delayed if the forecasted progress - the actual progress is > 0, and judging the balance situation by comparing the actual revenue with the actual progress, judging that the balance situation is improving if the actual revenue - the actual progress is < 0, judging that the balance situation is as planned if the actual revenue - the actual progress is = 0, and judging that the balance situation is worsening if the actual revenue - the actual progress is >0;
A progress management method comprising: A progress management program to be executed by an information processing device having a control unit,
The control unit,
A cost processing step for creating actual costs and actual revenues based on a cost-proportional basis when a project is accepted;
a volume processing step for creating a volume-based forecast volume and an actual volume when the order is received;
a comparison process for judging the progress of the construction work by comparing the forecasted progress with the actual progress, judging that the project is progressing ahead of schedule if the forecasted progress - the actual progress is < 0, judging that the project is progressing at the planned pace if the forecasted progress - the actual progress is = 0, judging that the project is delayed if the forecasted progress - the actual progress is > 0, and judging the balance situation by comparing the actual revenue with the actual progress, judging that the balance situation is improving if the actual revenue - the actual progress is < 0, judging that the balance situation is as planned if the actual revenue - the actual progress is = 0, and judging that the balance situation is worsening if the actual revenue - the actual progress is >0;
A progress management program for implementing the above.

Images