Landing prediction device, landing prediction method, and landing prediction program

Abstract

To make a forecast while taking into consideration an additional order for a project in progress, the order being not concluded yet but promising.SOLUTION: A forecasting apparatus includes forecasting input means which is configured to: input, for an additional order which is not concluded yet but promising, estimated increase / decrease amount with respect to the amount of contract, approximate budget for each cost accounting title, and future estimated cost, regarding target project identification information and order identification information, in accordance with an operation of an operator on a forecasting screen; and generate project forecasting data including the project identification information, the order identification information, the cost accounting title, the budget, the approximate budget, accumulated incurred cost which is accumulated amount of costs, future estimated cost, and a final estimated forecast amount calculated based on the sum of the accumulated incurred cost and the future estimated cost, by referring to contract information data, project budget data, and project cost detail data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a landing prediction device, a landing prediction method, and a landing prediction program. [Background technology]

[0002] For example, in the construction industry, there are situations where an increase in construction work is already expected, even though no contract has been signed, and work continues even though no purchase order has been received. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-21081 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned Patent Document 1 does not state anything about making a final forecast that takes into account uncontracted orders for an ongoing project when further orders (e.g., additional construction) are expected even though they have not yet been contracted.

[0005] The present invention has been made in consideration of the above, and aims to provide a landing prediction device, a landing prediction method, and a landing prediction program that are capable of making landing predictions taking into account uncontracted orders for an ongoing project when further orders are expected despite uncontracted orders. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention is characterized in that the control unit is configured to be able to access contract information data including project identification information, order identification information, and contract amount, project budget data including project identification information, order identification information, cost item classification, and budget amount, and project cost detail data including voucher number, project identification information, order identification information, cost item classification, and cost amount, and is equipped with an end-of-life forecast input means for inputting, in response to an operator's operation on the end-of-life forecast screen, a planned increase / decrease in the contract amount, an estimated budget amount for each cost item classification, and future planned costs for each project identification information and order identification information in question, when a contract has not yet been signed but further orders are expected, and referring to the contract information data, project budget data, and project cost detail data, creating project end-of-life forecast data including the project identification information, order identification information, cost item classification, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future planned costs, and a final expected end-of-life amount calculated as accumulated incurred costs + future planned costs.

[0007] According to another aspect of the present invention, the project end forecast data may include a difference between the budget amount and the actual amount calculated by subtracting the final end forecast from the budget amount and the estimated budget amount.

[0008] According to another aspect of the present invention, the landing forecast input means may output a profit amount calculated by summing up the contract amount + the expected increase / decrease amount - the final landing forecast.

[0009] According to another aspect of the present invention, the planned increase / decrease amount and the estimated budget amount for each cost item category may be input in a plurality of patterns.

[0010] According to another aspect of the present invention, the planned increase / decrease amount and the estimated budget amount for each cost item category may be configured to allow negative amounts to be input.

[0011] According to one aspect of the present invention, the final forecast input means may create project final forecast estimated budget data including project identification information, order identification information, estimated budget identification information, estimated increase / decrease amount, cost item classification, and estimated budget amount.

[0012] In order to solve the above-mentioned problems and achieve the object, the present invention provides a method for forecasting results executed by an information processing device having a control unit, wherein the control unit is configured to be able to access contract information data including project identification information, order identification information, and contract amount, project budget data including project identification information, order identification information, cost item classification, and budget amount, and project cost detail data including voucher number, project identification information, order identification information, cost item classification, and cost amount, and the control unit executes a forecasting method for a target project in response to an operator's operation on a forecasting screen. For the project identification information and order identification information, when a contract has not yet been signed but further orders are expected, the system may include a final cost forecast input step of inputting the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and the future estimated costs for each cost item category, and creating project final cost forecast data that includes the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future estimated costs, and a final estimated amount calculated as the accumulated incurred costs + future estimated costs, by referring to the contract information data, the project budget data, and the project cost detail data.

[0013] In order to solve the above-mentioned problems and achieve the object, the present invention provides a final forecasting program to be executed by an information processing device having a control unit, wherein the control unit is configured to be able to access contract information data including project identification information, order identification information, and contract amount, project budget data including project identification information, order identification information, cost item classification, and budget amount, and project cost detail data including voucher number, project identification information, order identification information, cost item classification, and cost amount, and the control unit is configured to access target project identification information and The program is characterized by being a final forecast program for executing a final forecast input step that, when there is no contract yet but further orders are expected, inputs the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and the future planned costs for each cost item category, and references the contract information data, the project budget data, and the project cost detail data to create project final forecast data that includes the project identification information, the order identification information, the cost item category, the budget amount, the estimated budget amount, the accumulated incurred costs which are the accumulation of the cost amounts, the future planned costs, and the final forecast amount calculated as the accumulated incurred costs + the future planned costs. [Effects of the Invention]

[0014] According to the present invention, when an ongoing project has not yet been contracted but further orders are expected, it is possible to make a final forecast that takes into account the uncontracted orders. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a landing prediction device according to this embodiment. [Figure 2] FIG. 2 is a flowchart for explaining an outline of the overall processing of the landing prediction device according to this embodiment. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 4]FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 16] FIG. 16 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. [Figure 18]FIG. 18 is a diagram for explaining a specific example of the processing of the control unit of the landing prediction device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0017] [1. Overview] For example, in the construction industry, there are situations where an increase in work is already expected for an ongoing project, even though no purchase order has been received, and work will proceed. Because no purchase order has been received, the order and budget do not take the increase in work into account, but there is also a desire to understand the final amount taking the increase in work into account.

[0018] However, in the past, it was only possible to register forecasts for contracts that had already been ordered and budgeted. This led to issues such as (1) when estimating costs for construction work that has not yet been contracted and has no budget, it is not possible to grasp profits because there is no budget, (2) when managing indirect costs calculated from the contract amount, it is not possible to accurately estimate them because there is no contract, and (3) it is not possible to forecast revenues that take into account orders that have not yet been contracted.

[0019] Therefore, in this embodiment, we propose a system that can predict the final outcome of an ongoing construction project, taking into account the expected increase or decrease in the amount of work and the estimated budget, for example, when an increase in work is already expected but not yet contracted.

[0020] According to the present embodiment of the sales forecasting device, (1) the order amount for uncontracted items can be registered as the expected increase / decrease amount, (2) an estimated budget for the expected increase / decrease amount can be registered, (3) a sales forecast that takes into account the expected increase / decrease amount and the estimated budget can be registered, and (4) multiple patterns of expected increase / decrease amount and estimated budget can be registered. This makes it possible to manage expected costs and forecast income and expenditures, including the amount of orders expected in the future.

[0021] The landing prediction device of this embodiment is widely applicable to industries such as the construction industry and the IT industry.

[0022] [2. Configuration] An example of the configuration of the landing prediction device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the landing prediction device 100.

[0023] The landing prediction device 100 is a commercially available desktop personal computer. Note that the landing prediction device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also 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.

[0024] The landing prediction device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the landing prediction device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0025] The communication interface unit 104 communicably connects the landing prediction 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 a communication line. Here, the network 300 has a function of connecting the landing prediction 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).

[0026] 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 touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0027] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that cooperate with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or 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 stores contract information data, project budget data, project cost breakdown data, project completion forecast data, project completion forecast approximate budget data, etc.

[0028] The contract information data may include project identification information (project number and / or project name), order identification information (order number, line number), department, order date, construction period, and contract amount (e.g., contract amount).

[0029] The project budget data may include project identification information (project number and / or project name), order identification information (order number, line number), registration date, project cost item classification, and budget amount.

[0030] Project cost detail data may include document identification information (document number, line number), project identification information (project number and / or project name), order identification information (order number, line number), accounting date, project cost item classification, and cost amount.

[0031] The project completion forecast data may include project identification information (project number and / or project name), order identification information (order number, line number), project cost item classification, budget amount, estimated budget amount, cumulative incurred costs, future planned costs, final completion forecast, and actual / planned difference.

[0032] The estimated project budget data may include project identification information (project number and / or project name), order identification information (order number, line number), estimated budget identification information (estimated budget name and / or estimated budget code), estimated budget year and month, expected increase / decrease amount, project cost item classification, and estimated budget amount.

[0033] The control unit 102 is a CPU or the like that comprehensively controls the landing prediction 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.

[0034] The control unit 102 is configured to be able to access the contract information data, project budget data, project cost detail data, project end-of-life forecast data, and project end-of-life forecast approximate budget data stored in the storage unit 106. Note that these data may also be stored in other locations (e.g., the server 200) as long as they are accessible by the control unit 102.

[0035] The control unit 102 conceptually includes a contract information input unit 102a, a budget input unit 102b, a cost calculation input unit 102c, a final result forecast input unit 102d, and a screen display control unit 102e.

[0036] The contract information input unit 102a inputs contract information data in response to, for example, an operator's operation on a contract information input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0037] The budget input unit 102b inputs project budget data in response to, for example, an operator's operation on a budget input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0038] The cost accounting input unit 102c inputs project cost detail data in response to, for example, an operator's operation on a cost accounting input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0039] For example, in response to the operator's operations on the forecast arrival list screen and forecast arrival input screen (see Figures 6 to 12) displayed on the monitor 14, the final arrival forecast input unit 102d inputs the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and future planned costs for the target project identification information and order identification information when a contract has not been signed but further orders are expected, and references the contract information data, project budget data, and project cost detail data to create project arrival forecast data including the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the cumulative total of cost amounts, future planned costs, and a final forecast amount calculated as the accumulated incurred costs + future planned costs, and stores this in the memory unit 106.

[0040] The project end result forecast data may include the difference between the actual and forecast amounts, calculated by adding the budget amount to the estimated budget amount and subtracting the final end result forecast.

[0041] The final price forecast input unit 102d may also display and output a profit amount calculated by adding the contract amount + the expected increase / decrease amount - the final price forecast.

[0042] The planned increase / decrease amount and the estimated budget amount for each cost item category may be input in multiple patterns.

[0043] The planned increase / decrease amount and the estimated budget amount for each cost item category may be configured to allow negative amounts to be entered.

[0044] In addition, the final forecast input unit 102d may create project final forecast estimated budget data including project identification information, order identification information, estimated budget identification information, expected increase / decrease amount, cost item classification, and estimated budget amount, and store it in the memory unit 106.

[0045] The screen display control unit 102e controls the display and input of various screens (for example, contract information input screen, budget input screen, cost accounting input screen, estimated arrivals list screen, estimated arrivals input screen, etc.) displayed on the monitor 114.

[0046] [3. Specific Examples] 1 to 18, a specific example of the processing of the control unit 102 of the landing prediction device 100 in this embodiment will be described.

[0047] (3-1. Overall processing) FIG. 2 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the landing prediction device 100 in this embodiment.

[0048] An outline of the overall processing of the control unit 102 of the landing prediction device 100 in this embodiment will be described with reference to Fig. 2. In Fig. 2, the contract information input unit 102a executes contract information input processing (step S1). Specifically, in the contract information input processing, the contract information input unit 102a inputs contract information data in accordance with, for example, an operation by an operator on a contract information input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0049] The budget input unit 102b executes a budget input process (step S2). Specifically, in the budget input process, the budget input unit 102b inputs project budget data in response to, for example, an operator's operation on a budget input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0050] The cost accounting input unit 102c executes a cost accounting input process (step S3). Specifically, in the cost accounting input process, the cost accounting input unit 102c inputs project cost detail data in response to, for example, an operator's operation on a cost accounting input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0051] The final result forecast input unit 102d executes a final result forecast input process (step S4). Specifically, in the final result forecast input process, for example, in response to an operator's operation on the final result forecast list screen and the final result forecast input screen (see FIGS. 6 to 12) displayed on the monitor 14, the final result forecast input unit 102d inputs a planned increase / decrease amount relative to the contract amount, an estimated budget amount for each cost item classification, and a future planned cost for each cost item classification, when a contract has not yet been signed but further orders are expected, for the target project identification information and order identification information, and references the contract information data, project budget data, and project cost detail data to create project final result forecast data including the project identification information, order identification information, cost item classification, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future planned costs, and a final estimated amount calculated by adding the accumulated incurred costs to the future planned costs, and stores the data in the storage unit 106. In addition, the final forecast input unit 102d may create project final forecast estimated budget data including project identification information, order identification information, estimated budget identification information, expected increase / decrease amount, cost item classification, and estimated budget amount, and store it in the memory unit 106.

[0052] In this case, the project end result forecast data may include the difference between the budget amount and the estimated budget amount minus the final end result forecast. The end result forecast input unit 102d may also display and output the profit amount calculated by adding the contract amount + the estimated increase / decrease amount minus the final end result forecast. The estimated increase / decrease amount and the estimated budget amount for each cost item category may be input in multiple patterns. Negative amounts may be input for the estimated increase / decrease amount and the estimated budget amount for each cost item category.

[0053] (3-2. Sample data) 3 to 18 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the landing prediction device 100 in this embodiment. A specific example of the processing by the control unit 102 of the landing prediction device 100 in this embodiment will be explained with reference to FIGS. 3 to 18. In the following explanation, all monetary amounts will be expressed in units of "yen," and the notation thereof will be omitted.

[0054] (S1: Contract information input process) A specific example of the contract information input process will be described with reference to Fig. 3. Project information is registered through the contract information input process. The contract information input unit 102a inputs contract information data in response to, for example, an operator's operation on a contract information input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0055] 3 is a diagram showing an example of contract information data. The contract information data has the following fields: project number, order number, line number, project name, department, order date, construction period, and contract amount (contract price). In the example shown in the figure, the first line contains project number "PJ0001," order number "JU0001," line number "1," project name "New factory B area installation work," department "B001: 1st construction department," order date "2022 / 6 / 1," construction period "2022 / 6 / 1~2024 / 3 / 31," and contract price "10,000,000."

[0056] Regarding this project number "PJ0001", there is currently no contract (no order) in place, but an additional order of "3,000,000" is scheduled for May 1, 2023, and an additional order of "1,000,000" is scheduled for December 1, 2023.

[0057] (S2: Budget input processing) A specific example of the budget input process will be described with reference to Fig. 4. The budget input process is used to register a budget. The budget input unit 102b inputs project budget data in response to, for example, an operator's operation on a budget input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0058] Figure 4 shows an example of project budget data. The project budget data includes the following fields: project number, order number, line number, project name, registration date, project cost item classification, and budget amount. In the example shown in the figure, the first line contains the project number "PJ0001," the order number "JU0001," the line number "1," the project name "Installation work in new factory area B," the registration date "2022 / 6 / 1," the project cost item classification "material costs," and the budget amount "1,000,000." The fifth line contains the project number "PJ0001," the order number "JU0001," the line number "1," the project name "Installation work in new factory area B," the registration date "2022 / 6 / 1," the project cost item classification "indirect costs," and the budget amount "500,000." The budget amount for indirect costs will be automatically calculated as 5% of the contract amount (500,000 = 10,000,000 x 5%).

[0059] (S3: Cost entry processing) A specific example of the cost accounting input process will be described with reference to Figure 5. Costs are accounted for through the cost accounting input process. The cost accounting input unit 102c inputs project cost detail data in response to, for example, an operator's operation on a cost accounting input screen (not shown) displayed on the monitor 14, and stores the data in the storage unit 106.

[0060] Figure 5 shows an example of project cost breakdown data. The project cost breakdown data has the following fields: document number, line number, project number, order number, line number, accounting date, project cost item category, and cost amount. In the example shown in the figure, the first line has the document number "GK001," line number "1," project number "PJ0001," order number "JU0001," line number "1," accounting date "2023 / 2 / 1," project cost item category "material cost," and cost amount "900,000." The fifth line has the document number "GK001," line number "1," project number "PJ0001," order number "JU0001," line number "1," accounting date "2023 / 2 / 1," project cost item category "indirect cost," and cost amount "300,000." The overhead costs of the cost amount are automatically calculated as 60% of the completed amount, out of 5% of the contract amount (300,000 = 10,000,000 x 5% x 60%).

[0061] (S4: Landing cost entry processing) 6 to 18, a specific example of the final cost calculation input process will be described. For example, in response to an operator's operation on the final cost forecast list screen and final cost forecast input screen displayed on the monitor 114, the final cost forecast input unit 102d inputs the planned increase / decrease amount relative to the contract amount, the estimated budget amount for each cost item category, and future planned costs for the target project identification information and order identification information when further orders are expected despite no contract being signed, and references the contract information data, project budget data, and project cost detail data to create project final cost forecast data including the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future planned costs, and a final estimated amount calculated by adding the accumulated incurred costs and the future planned costs, and stores the data in the storage unit 106. In addition, the final forecast input unit 102d creates project final forecast estimated budget data including project identification information, order identification information, estimated budget identification information, expected increase / decrease amount, cost item classification, and estimated budget amount, and stores it in the memory unit 106.

[0062] FIG. 6 is a diagram showing an example of the display of the arrival forecast list screen 400. From the arrival forecast list screen 400, a project for which arrival forecasts will be entered is selected. The arrival forecast list screen 400 includes an extraction condition specification area for specifying extraction conditions such as the fiscal year and month, department, project number, and order number; a project list display area that displays details of projects that meet the extraction conditions; and a display button. The project list display area displays data for the project number, order number, project name, and department. When extraction conditions are specified in the extraction condition specification area and the display button is pressed, contract information data is extracted using the extraction conditions as a key, and data for the project number, order number, project name, and department is displayed in the project list display area. When a target is selected in the project list display area and double-clicked, the arrival forecast input screen 500 is displayed.

[0063] In the example shown in Figure 6, the data shown in the figure is displayed in the project list display area from the contract information data using the accounting year and month "2023 / 3" and department "B001" as keys. The first line displays the project number "PJ0001," order number "JU0001," line number "1," project name "New Factory Area B Installation Work," and department "B001: First Construction Department." Selecting and double-clicking the first line displays the expected completion input screen 500 shown in Figure 7.

[0064] 7 is a diagram showing a display example of the arrival forecast input screen 500. The arrival forecast input screen 500 has a header area 501 that displays the fiscal year and month, project number, order number-line number, and a details area 502 that displays the arrival forecast or rough estimate according to the switching button.

[0065] Figure 7 shows the case where final forecast is selected using the switch button in the details area 502, and displays the final forecast header area 510 with the contract amount, expected increase / decrease amount, and initial amount, as well as the final forecast details area (row number, project cost item classification, budget amount, estimated budget, budget total, cumulative incurred costs, future planned costs, final final forecast, difference between forecast and actual) 511, and the total profit amount.

[0066] Figure 8 shows the case where the estimated forecast is selected using the switch button in the details area 502, and an estimated budget header area 520 containing the estimated budget code, estimated budget name, estimated budget year and month, and expected increase / decrease amount, an estimated budget details area (row number, project cost item classification, estimated budget) 521, and a confirm button are displayed.

[0067] On the landing prediction input screen 500, hatched cells are ones that the operator cannot input (automatic input / display), and non-hatched cells are ones that the operator can input.

[0068] 7, the header area 501 of the arrival forecast input screen 500 displays the fiscal year specified on the arrival forecast list screen 400, and the project number, order number, and line number of the contract information data for the line selected in the project list display area. In the example shown in the figure, the fiscal year and month "2023 / 3", project number "PJ0001", and order number-line number "JU0001-1" are displayed.

[0069] Furthermore, when "Final Results" is selected in the details area 502 shown in FIG. 7, the final results header area 510 displays the contract amount of the contract information data for the row selected in the project list display area. The planned increase / decrease amount is initially displayed as "0 yen." The initial amount displayed is the contract amount + planned increase / decrease amount. In the example shown in the same figure, the contract amount "10,000,000", planned increase / decrease amount "0", and initial amount "10,000,000" are displayed.

[0070] The project cost details area 511 uses the selected project number, order number and line number as keys to reference the project budget data and project cost detail data, and displays the project cost item classification, budget amount, estimated budget amount, budget total (= budget amount + estimated budget amount), accumulated incurred costs, future planned costs, final forecast (= accumulated incurred costs + future planned costs), and actual / budget variance (= total budget - final forecast). The estimated budget amount is set from the data entered in the estimated budget details area 521. The operator enters future planned costs, excluding indirect costs.

[0071] Furthermore, as shown in FIG. 8, when an estimated budget is selected in the details area 502, the same project cost item classification as in the final forecast details area 511 is displayed in the estimated budget details area 521. As shown in FIG. 9, the operator inputs data in the estimated budget header area 520, inputs data on the general budget other than indirect costs in the estimated budget details area 521 (indirect costs are automatically displayed), and presses the confirm button, whereupon the data input in the estimated budget header area 520 and the estimated budget details area 521 is displayed in the confirm area 522 (see FIG. 9). When the reflect button is checked, the estimated increase / decrease amount and estimated budget amount in the confirm area 522 are reflected in the estimated increase / decrease amount in the final forecast header area 510 of the details area 502 and the estimated budget amount in the final forecast details area 511.

[0072] 9, the operator enters the estimated budget code "A," the estimated budget name "Estimated A Angle Height," the estimated budget year and month "2023 / 5," and the planned increase / decrease amount "3,000,000" in the estimated budget header area 520. In addition, in the estimated budget details area 521, the operator enters "800,000," "1,300,000," "500,000," and "200,000" in the project cost item categories "material costs," "subcontract costs," "labor costs," and "expenses," respectively. The overhead cost of "150,000" (calculated as 5% of the planned increase / decrease amount (150,000 = 3,000,000 x 5%) and the total of "2,950,000" are automatically entered (displayed). When the operator presses the Confirm button, the data about the estimated budget "A" entered in the estimated budget header area 520 and estimated budget details area 521 is displayed in the Confirm area 522, as shown in Figure 9.

[0073] Note that multiple patterns of planned increase / decrease amounts and estimated budgets can be registered (input), and multiple patterns of estimated budgets can be set as the estimated budget for the final forecast details. FIG. 10 is a diagram showing an example where multiple patterns of planned increase / decrease amounts and estimated budgets are registered. The example shown in FIG. 10 shows an example where, in addition to estimated budget "A" (planned increase / decrease amount "3,000,000"), estimated budget "B" (planned increase / decrease amount "1,000,000") is registered. As shown in FIG. 10, in the estimated budget header area 520, the operator inputs estimated budget code "B," estimated budget name "Estimate B Angle Height," estimated budget year / month "2023 / 12," and planned increase / decrease amount "1,000,000." Furthermore, in the estimated budget details area 521, the operator enters "200,000," "400,000," "200,000," and "100,000" into the project cost item categories of "material costs," "subcontract costs," "labor costs," and "expenses," respectively. Indirect costs of "50,000" and a total of "950,000" are automatically entered (displayed). When the operator presses the confirm button, the data for the estimated budget "B" entered in the estimated budget header area 520 and estimated budget details area 521 is displayed in the confirmation area 522, as shown in FIG. 10.

[0074] Then, as shown in Figure 12, when the operator checks the reflect button for estimated budget "A," the expected increase / decrease amount of "3,000,000" is reflected in the final result header area 510 of the details area 502, and the estimated budget (cost item categories of "material costs," "subcontract costs," "labor costs," "expenses," and "indirect costs" of "800,000," "1,300,000," "500,000," "200,000," and "150,000," totaling "2,950,000") is reflected in the final result detail area 511, as shown in Figure 11. The total budget (= budget amount + estimated budget) is also updated.

[0075] In Figure 11, the operator enters future planned costs in the final forecast details area 511. In the example shown in Figure 11, the operator enters "1,000,000," "2,800,000," "950,000," and "400,000" into the project cost item categories of "material costs," "subcontract costs," "labor costs," and "expenses," respectively. Indirect costs of "350,000" and a total of "5,500,000" are automatically entered (displayed). Indirect costs are calculated as the final forecast minus the cumulative incurred costs. In this example, the calculation is the final forecast of "650,000 (indirect costs taking into account the estimated budget)" minus the cumulative incurred costs of "300,000 (60% of the budget amount of "500,000")" = 350,000. The final forecast (= cumulative incurred costs + future planned costs), the difference between the budget and actual results (= total budget - final forecast), and the profit amount (= total initial amount - final forecast) are updated. In the example shown in the figure, the difference between the budget and actual results for material costs is updated to "-100,000 (= 1,800,000 - 1,900,000)", and the profit amount is updated to "1,100,000 (= 13,000,000 - 11,900,000)".

[0076] When a registration button (not shown) is pressed, the project arrival forecast data and the project arrival forecast approximate budget data corresponding to the input contents of the arrival forecast input screen 500 are registered in the storage unit 206. In the case of the input contents of Figures 11 and 12, the project arrival forecast data and the project arrival forecast approximate budget data as shown in Figures 13(A) and 13(B) are registered.

[0077] 13(A) is a diagram showing an example of project completion forecast data. The project completion forecast data includes the following fields: project number, order number, line number, project cost item category, budget amount, estimated budget amount, cumulative incurred costs, future planned costs, final projected completion forecast, and budget / actual difference. In the example shown in the figure, the first line contains the project number "PJ0001," order number "JU0001," line number "1," project cost item category "material costs," budget amount "1,000,000," estimated budget amount "800,000," cumulative incurred costs "900,000," future planned costs "1,000,000," final projected completion forecast "1,900,000," and budget / actual difference "-100,000."

[0078] 13B is a diagram showing an example of estimated project budget data. The estimated project budget data includes the following fields: project number, order number, line number, estimated budget name, estimated budget year and month, estimated increase / decrease amount, project cost item classification, and estimated budget amount. In the example shown in the same figure, the first line has the project number "PJ0001," the order number "JU0001," the line number "1," the estimated budget name "Estimated A, angle height," the estimated budget year and month "2023 / 5," the planned increase / decrease amount "3,000,000," the project cost item category "material costs," and the estimated budget amount "800,000." The sixth line has the project number "PJ0001," the order number "JU0001," the line number "1," the estimated budget name "Estimated B, angle height," the estimated budget year and month "2023 / 12," the planned increase / decrease amount "1,000,000," the project cost item category "material costs," and the estimated budget amount "200,000."

[0079] Figure 15 shows the case where the operator checks the reflect button for both estimated budget "A" and estimated budget "B" in the confirmation area 522 of the details area 502. In this case, as shown in Figure 14, the estimated increase / decrease amount of "4,000,000" is reflected in the final result header area 510 of the details area 502 as the sum of estimated budget "A" and estimated budget "B", and the estimated budget amount in the final result detail area 511 is reflected as the cost item categories of "material costs", "subcontract costs", "labor costs", "expenses", and "indirect costs" (1,000,000, "1,700,000", "700,000", "300,000", and "200,000"), totaling "3,900,000". For future planned costs, the same data as in Figure 11 will be entered for "material costs," "subcontract costs," "labor costs," and "expenses," and "400,000 (= final estimated cost of 700,000 - cumulative incurred costs of 300,000)" will be automatically entered for indirect costs. The total budget, final estimated cost, budget / actual variance, and profit amount will also be updated.

[0080] When a registration button (not shown) is pressed, the project arrival forecast data and the project arrival forecast approximate budget data corresponding to the input contents of the arrival forecast input screen 500 are registered in the storage unit 206. In the case of the input contents of Figures 14 and 15, the project arrival forecast data and the project arrival forecast approximate budget data as shown in Figures 16(A) and 16(B) are registered.

[0081] It is possible to input negative amounts for the planned increase / decrease amount and the estimated budget. Figures 17 and 18 are diagrams showing display examples of the details area 502 on the arrival forecast input screen 500 when negative amounts are input for the planned increase / decrease amount and the estimated budget.

[0082] As explained above, according to this embodiment, in response to the operator's operation on the final forecast screen, when further orders are expected although no contract has been signed for the target project identification information and order identification information, the final forecast input unit 102d is provided which inputs the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and future planned costs for each cost item category, in response to the operator's operation on the final forecast screen, and references the contract information data, the project budget data, and the project cost detail data to create project final forecast data including the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future planned costs, and a final forecast amount calculated as accumulated incurred costs + future planned costs.Therefore, when further orders are expected although no contract has been signed for an ongoing project, it is possible to make a final forecast that takes into account uncontracted orders.

[0083] [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 contributing to the achievement of SDGs Goals 8 and 9.

[0084] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0085] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

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

[0087] 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 known methods.

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

[0089] Furthermore, with regard to the landing prediction device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0090] For example, all or any part of the processing functions of the landing prediction device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the landing prediction device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0091] In addition, this computer program may be stored in an application program server connected to the landing prediction device 100 via any network, and all or part of it may be downloaded as needed.

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

[0093] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by working together with other programs, such as an OS. Note that the specific configurations and reading procedures for reading a recording medium in each device shown in the embodiments, as well as the installation procedures after reading, can use well-known configurations and procedures.

[0094] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, 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.

[0095] The landing prediction 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 connected to any peripheral device. The landing prediction device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to realize the processing described in this embodiment.

[0096] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0097] 100 Landing Prediction Device 102 Control section 102a Contract information input section 102b Budget Input Section 102c Cost Accounting Input Section 102d Landing prediction input section 102e Screen display control unit 104 Communication interface unit 106 Storage section 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network 400 Landing forecast list screen 500 Landing prediction input screen 501 Header Area 502 Details area 510 Landing Prediction Header Area 511 Landing forecast details area 520 Estimated Budget Header Area 521 Estimated Budget Details Area 522 Confirmed Area

Claims

1. A landing prediction device equipped with a control unit, The control unit Contract information data including project identification information, order identification information, and contract amount; Project budget data including project identification information, order identification information, cost item classification, and budget amount; Project cost detail data including document number, project identification information, order identification information, cost item classification, and cost amount; It is configured to be accessible to A project completion forecasting device characterized by comprising a project completion forecast input means for inputting the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and future planned costs for the target project identification information and order identification information in response to an operator's operation on the project completion forecast screen when further orders are expected despite no contract being signed, and creating project completion forecast data that includes the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the cumulative total of cost amounts, future planned costs, and a final project completion forecast amount calculated as the accumulated incurred costs + future planned costs, which is the final forecast amount, by referring to the contract information data, the project budget data, and the project cost detail data.

2. 2. The project outcome prediction device according to claim 1, wherein the project outcome prediction data includes a difference between the actual outcome and the budget amount calculated by adding the estimated budget amount to the final outcome prediction.

3. 2. The apparatus for predicting sales price according to claim 1, wherein the means for inputting the prediction of sales price outputs a profit amount calculated by adding the contract amount + the expected increase / decrease amount - the final prediction of sales price.

4. 2. The device for predicting results according to claim 1, wherein a plurality of patterns can be input for the planned increase / decrease amount and the estimated budget amount for each cost item category.

5. 2. The device for predicting a result according to claim 1, wherein negative amounts can be input for the planned increase / decrease amount and the estimated budget amount for each cost item category.

6. The project arrival prediction device described in any one of claims 1 to 5, characterized in that the project arrival prediction input means creates project arrival prediction estimated budget data including project identification information, order identification information, estimated budget identification information, expected increase / decrease amount, cost item classification, and estimated budget amount.

7. A landing prediction method executed by an information processing device having a control unit, The control unit Contract information data including project identification information, order identification information, and contract amount; Project budget data including project identification information, order identification information, cost item classification, and budget amount; Project cost detail data including document number, project identification information, order identification information, cost item classification, and cost amount; It is configured to be accessible to Executed in the control unit: a final forecast input step of inputting the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and future planned costs for the target project identification information and order identification information in response to an operator's operation on the final forecast screen when further orders are expected despite no contract being signed, and creating project final forecast data that includes the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future planned costs, and a final forecast amount calculated as the accumulated incurred costs + future planned costs, which is the final forecast amount, by referring to the contract information data, the project budget data, and the project cost detail data.

8. A landing prediction program to be executed by an information processing device having a control unit, The control unit Contract information data including project identification information, order identification information, and contract amount; Project budget data including project identification information, order identification information, cost item classification, and budget amount; Project cost detail data including document number, project identification information, order identification information, cost item classification, and cost amount; It is configured to be accessible to Executed in the control unit: A final forecast program for executing a final forecast input step that, in response to operator operations on a final forecast screen, inputs the planned increase / decrease in the contract amount, the estimated budget amount for each cost item category, and future planned costs for each project identification information and order identification information in question when a contract has not yet been signed but further orders are expected, and references the contract information data, the project budget data, and the project cost detail data to create project final forecast data that includes the project identification information, order identification information, cost item category, budget amount, estimated budget amount, accumulated incurred costs which are the accumulation of cost amounts, future planned costs, and a final forecast amount calculated as the accumulated incurred costs + future planned costs.

Images