JP7674294B2 - Business support device, business support method, and business support program - Google Patents

Description

The present invention relates to a business support device, a business support method, and a business support program.

Nowadays, in industries such as the construction industry where labor costs can be a major cost factor, daily or monthly work reports are often created that record the worker, the date and year of work, the work content, and the working hours, etc., in order to accurately and quickly manage the working hours of workers, etc.

Patent Document 1 (JP Patent Publication 2022-013452 A) discloses a construction management support device that automatically generates a daily work report. This construction management support device has a memory unit that stores worker identification information for recognizing workers, and an acquisition unit that acquires image information of the target construction work captured by an imaging means. The image analysis unit refers to the worker identification information, analyzes the acquired image information, and recognizes the worker. The measurement unit measures the work time of the recognized worker. Then, the display unit displays the recognized worker and work information including the work time associated with the worker. This makes it possible to automatically generate and display a daily work report.

JP 2022-013452 A

The task of creating work reports such as daily or monthly reports is a heavy workload, so it is preferable to be able to create work reports with as simple a process as possible.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that enable the creation of work reports with simple operations.

In order to solve the above-mentioned problems and achieve the object, the business support device of the present invention comprises a calculation method identification unit that identifies a calculation method of work time for each target person for whom a work report is to be created based on a plan type set for each target person for whom a work report is to be created, a calculation unit that calculates the planned work time for each target person for whom a work report is to be created based on the calculation method identified by the calculation method identification unit, and a data generation unit that generates work report planned data including the planned work time calculated by the calculation unit, the cases for which the target people will be working, and the target people for whom they will be working on the cases, and the calculation unit calculates the planned work time for cases for which the target people will be working based on the ratio of the budget amount for each case allocated to the case for each specified period.

In addition, in order to solve the above-mentioned problems and achieve the objective, the business support method of the present invention includes a calculation method identification step in which a calculation method identification unit identifies a calculation method of work time for each person to be created for a work report based on the planned type set for each person to be created for the work report, a calculation step in which a calculation unit calculates the planned work time for each person to be created based on the calculation method identified in the calculation method identification step, and a data generation step in which a data generation unit generates work report planned data including the planned work time calculated in the calculation step, the cases for which the people to be created will be working, and the people to be created who will be working on the cases, and in the calculation step, the planned work time for the cases for which the people to be created will be working is calculated based on the ratio of the budget amount for each case allocated to the case for each specified period.

In addition, in order to solve the above-mentioned problems and achieve the object, the business support program of the present invention causes a computer to function as a calculation method identification unit that identifies a calculation method of work time for each person to be created based on the plan type set for each person to be created for the work report, a calculation unit that calculates the planned work time for each person to be created based on the calculation method identified by the calculation method identification unit, and a data generation unit that generates work report planned data including the planned work time calculated by the calculation unit, the cases for which the people to be created will be working, and the people to be created who will be working on the cases , and when causing the computer to function as the calculation unit, the computer is caused to function so as to calculate the planned work time for cases for which the people to be created will be working based on the ratio of the budget amount for each case allocated to the case for each specified period.

This invention makes it easy to create work reports.

FIG. 1 is a block diagram showing a hardware configuration of a task support device according to an embodiment. FIG. 2 is a diagram illustrating an example of the schedule data management master. FIG. 3 is a diagram for explaining the schedule type. FIG. 4 is a diagram illustrating an example of the association mapping master. FIG. 5 is a diagram illustrating an example of the work hour master. FIG. 6 is a diagram illustrating an example of a worker attribute table. FIG. 7 is a diagram illustrating an example of a work instruction table. FIG. 8 is a diagram illustrating an example of a work performance table. FIG. 9 is a diagram illustrating an example of a budget information table. FIG. 10 is a diagram showing an example of a budget arrangement table. FIG. 11 is a diagram illustrating an example of a budget man-hour table. FIG. 12 is a diagram illustrating an example of a worker-specific case table. FIG. 13 is a diagram illustrating an example of a work schedule table. FIG. 14 is a diagram illustrating an example of an attribute-specific work pattern table. FIG. 15 is a diagram illustrating an example of a work schedule table. FIG. 16 is a diagram illustrating an example of a daily report schedule table. FIG. 17 is a diagram illustrating an example of a daily report table. FIG. 18 is a diagram showing an outline of a daily report creation operation in the task support device according to the embodiment. FIG. 19 is a flowchart showing the flow of the operation of creating worker-specific case data in the task support device according to the embodiment. FIG. 20 is a diagram showing an example of the worker-specific case master screen. FIG. 21 is a flowchart showing the flow of the operation of creating daily schedule data in the task support device according to the embodiment. FIG. 22 is a diagram showing an example of the daily report schedule data creation screen. FIG. 23 is a flowchart showing the flow of the daily report data creation operation in the task support device according to the embodiment.

Below, a business support device according to 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. For example, the business support device 1 according to the embodiment will be described as generating daily report schedule data and daily report data from each element based on a work schedule. However, the business support device 1 according to the embodiment may generate work report data corresponding to other periods, such as generating monthly report schedule data and monthly report data from each element based on a work schedule, or generating annual report schedule data and annual report data.

(Hardware configuration)
FIG. 1 is a block diagram showing a hardware configuration of a business support device 1 according to an embodiment. As an example, the business support device 1 according to the embodiment supports the creation of a daily report, which is a work report for various tasks such as design or on-site work, in the construction industry that constructs buildings and the like. The business support device 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 and an output device 7 are connected to the input/output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television) or a printer that prints the daily report. As the input device 6, a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function can be used.

The communication interface unit 4 is connected to a network 8, which may be a wide area network such as the Internet or a private network such as a LAN (Local Area Network). An accounting server device 9, a procurement server device 10, and a cost server device 11 are connected to the network 8. The accounting server device 9 is provided with a budget management table 12, which is a storage area of the storage unit. The budget management table 12 stores budget data. The business support device 1 of the embodiment acquires this budget data via the network 8 and the communication interface unit 4. Details will be described later.

Similarly, the procurement server device 10 is provided with an order details table 13, which is a storage area of the storage unit. The order details table 13 stores budget arrangement data. The business support device 1 of the embodiment acquires this budget arrangement data via the network 8 and the communication interface unit 4. The cost server device 11 is provided with a man-hour planning table 14, which is a storage area of the storage unit. The man-hour planning table 14 stores budget man-hour data. The business support device 1 of the embodiment acquires this budget man-hour data via the network 8 and the communication interface unit 4. This will be described in more detail later.

In this example, the budget data is acquired from the accounting server device 9, the budget arrangement data is acquired from the procurement server device 10, and the budget labor-hour data is acquired from the cost server device 11. However, the budget management table 12, the order details table 13, and the labor-hour planning table 14 may be provided in the memory unit 2 of the business support device 1 of the embodiment, and the budget data, budget arrangement data, and budget labor-hour data may be acquired from the budget management table 12, the order details table 13, and the labor-hour planning table 14 provided in the memory unit 2.

The storage unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive). The storage unit 2 is provided with a schedule data management master 21, a linkage mapping master 22, a work time master 23, a worker attribute table 24, a work instruction table 25, a work performance table 26, a worker case table 27, a work schedule table 28, an attribute-specific work pattern table 29, a work schedule table 30, a daily report schedule table 31, and a daily report table 32, each of which is a storage area.

The storage unit 2 also stores budget data, budget arrangement data, and budget labor-hour data acquired from the accounting server 9 to the cost server device 11. The storage unit 2 also stores a business support program for supporting the creation of daily report data, which will be described later.

Figure 2 is a schematic diagram showing an example of the schedule data management master 21. As shown in Figure 2, the schedule data management master 21 stores information indicating the schedule type, the storage location of the budget data, the storage location of the budget arrangement data, and the storage location of the budget labor-hour data.

Budget types are divided into "budget," "budget arrangements," "budget man-hours," "budget instructions," and "work results." As shown in Figure 3, the "budget" budget type indicates the construction budget for a project. This "budget" budget type is set up to the budget amount for each construction project by month. With this "budget" budget type, the project is finalized, but the worker, work type, date, and time are not finalized. The project is indicated by the construction number (construction no.), project, order number, etc. The work type is indicated by the process, work content, work type, etc.

The budget type of "budget arrangement" indicates the budget work plan. This budget type of "budget arrangement" is set up to the budget amount for each construction project by month. This budget type of "budget arrangement" has the project confirmed, but the worker, work type, date and time are not confirmed. "Budgeted man-hours" indicates the construction budget. This "budgeted man-hours" is set up to the budget amount for each construction project by month. This "budget arrangement" has the worker and project confirmed, but the work type, date and time are not confirmed.

The "Work instructions" budget type shows the workers and work type confirmed for each day's construction work. Note that with this "Work instructions" budget type, only the actual work time (hours) is unconfirmed; the worker, project, work type, and date are confirmed. "Work results" shows the actual results of the work. With this "Work results," the worker, work type, and date are confirmed; the project and time are unconfirmed.

In the example of Figure 2, the budget management table of the accounting system database (DB) in the server device "TKYSV01" is specified as the storage location of the budget data. This indicates that the budget data is stored in the budget management table 12 of the accounting server device 9 shown in Figure 1. The control unit 3 recognizes the storage location of the budget data by referencing this schedule data management master 21, and accesses the accounting server device 9 to obtain the budget data.

In the example of Figure 2, the order details table of the database (DB) of the procurement system in the server device "NGYSV01" is specified as the storage location of the budget arrangement data. This indicates that the budget arrangement data is stored in the order details table 13 of the procurement server device 10 shown in Figure 1. The control unit 3 recognizes the storage location of the budget arrangement data by referring to this schedule data management master 21, and accesses the procurement server device 10 to obtain the budget arrangement data.

In the example of Figure 2, the labor-hour planning table of the cost system database (DB) in the server device "OSKSV01" is specified as the storage location of the budgeted labor-hour data. This indicates that the budgeted labor-hour data is stored in the labor-hour planning table 14 of the cost server device 14 shown in Figure 1. The control unit 3 recognizes the storage location of the budgeted labor-hour data by referring to this scheduled data management master 21, and accesses the cost server device 11 to obtain the budgeted labor-hour data.

Next, FIG. 4 is a schematic diagram showing an example of the linkage mapping master 22. In this linkage mapping master 22, item names of various data used in systems other than the business support device 1 of the embodiment are stored in association with item names of various data used in the business support device 1 of the embodiment. In the example of FIG. 4, the item "Worker" used in the business support device 1 of the embodiment is associated with the item "Employee" as an item used in other systems.

Similarly, the "department" item used in the business support device 1 of the embodiment is associated with the "division" item as an item used in other systems. Also, the "case" item used in the business support device 1 of the embodiment is associated with the "PJ (project) number" item as an item used in other systems. By referring to this linkage mapping master 22, it is possible to use items from other systems to generate daily report schedule data and daily report data.

Figure 5 is a schematic diagram showing an example of the working hours master 23. As shown in Figure 5, the working hours master 23 stores the prescribed working hours for each job type and department. Specifically, in the example of Figure 5, the working hours of a "worker" in the "construction department" with department code "100" is prescribed as "8 hours/day". In addition, the working hours of a "supervisor" in the "construction department" with department code "100" is prescribed as "7.5 hours/day".

Figure 6 is a schematic diagram showing an example of a worker attribute table 24. As shown in Figure 6, the worker attribute table 24 stores workers, departments, job types, employment status, and the above-mentioned schedule types in association with each other. In the example of Figure 6, "Yamashita-san" with worker code "1001" belongs to the "Construction Department" with department code "100", and his job type is "worker". Furthermore, "Yamashita-san"'s employment status is "full-time employee", and his schedule type is "budget".

In the example of Figure 6, "Kinoshita-san" with worker code "1002" belongs to the "Construction Department" with department code "100" and his job type is "Supervisor". "Kinoshita-san" has an employment status of "Full-time employee" and a planned type of "Budget arrangement". In the example of Figure 6, "Nakagawa-san" with worker code "1003" belongs to the "Construction Department" with department code "100" and his job type is "Assistant". "Nakagawa-san" has an employment status of "Temporary employee" and a planned type of "Budget man-hours".

In the example of Figure 6, "Yoshida-san" with worker code "1004" belongs to the "Construction Department" with department code "100" and his job type is "assistant". Furthermore, "Yoshida-san" has a "temporary worker" employment status and a planned type of "work instructions". In the example of Figure 6, "Kanzaki-san" with worker code "1005" belongs to the "Construction Department" with department code "100" and his job type is "assistant". Furthermore, "Kanzaki-san" has a "temporary worker" employment status and a planned type of "work performance".

Next, FIG. 7 is a schematic diagram showing an example of the work instruction table 25. As shown in FIG. 7, the work instruction table 25 stores cases, work dates, workers, and work content in association with each other. In the example of FIG. 7, it shows that "Yoshida-san" with worker code "1004" is assigned to the "design work" of case "K001" for which work is scheduled to be done (work date) on "April 1, 2021". Similarly, it shows that "Yoshida-san" with worker code "1004" is assigned to the "site survey" work of case "K001" for which work is scheduled to be done (work date) on "April 1, 2021".

The example in Figure 7 also shows that "Yoshida-san" with worker code "1004" is assigned to the "design work" of case "K003" for which work is scheduled to be done (work date) on "April 2, 2021." It also shows that "Yoshida-san" with worker code "1004" is assigned to the "design work" of case "K003" for which work is scheduled to be done (work date) on "April 3, 2021."

Next, FIG. 8 is a schematic diagram showing an example of the work history table 26. As shown in FIG. 8, the work history table 26 stores information indicating work that has been performed in the past. Specifically, the work history table 26 stores the work location, work date, worker, and work content of work that has been performed in the past, each associated with each other. In the case of the example in FIG. 8, it shows that on the work date "April 1, 2021", the work "packing" was performed at the "Tokyo Warehouse" by "Kanzaki-san" with worker code "1005".

Similarly, the example in Figure 8 shows that on the work date of April 1, 2021, "Kanzaki-san" with worker code "1005" performed the work of "shipping" at the "Tokyo Warehouse". Also, the example in Figure 8 shows that on the work date of April 2, 2021, "Kanzaki-san" with worker code "1005" performed the work of "packing" at the "Yokohama Warehouse". Also, the example in Figure 8 shows that on the work date of April 3, 2021, "Kanzaki-san" with worker code "1005" performed the work of "shipping" at the "Yokohama Warehouse".

Next, FIG. 9 is a schematic diagram showing an example of the budget management table 12 of the accounting server device 9 shown in FIG. 1. As shown in FIG. 9, the budget management table 12 stores cases, budget years and months, departments, and budget amounts in association with each other. The example in FIG. 9 shows that a budget amount of "210,000 yen" is set for work to be performed by the "Construction Department" with department code "100" in "April 2021" for a case with case code "K001". Similarly, the example in FIG. 9 shows that a budget amount of "140,000 yen" is set for "May 2021" for a case with case code "K001".

The example in Figure 9 also shows that a budget amount of "35,000 yen" is set for work to be performed by the "Civil Engineering Department" with department code "200" in "April 2021" for a project with project code "K002". Similarly, the example in Figure 9 shows that a budget amount of "90,000 yen" is set for work to be performed by the "Construction Department" with department code "100" in "April 2021" for a project with project code "K003".

Next, FIG. 10 is a schematic diagram showing an example of the order details table 13 of the procurement server device 10 shown in FIG. 1. As shown in FIG. 10, the procurement server device 10 stores the case, the budget year and month, the department, the job type, and the budget amount, each associated with each other. The example in FIG. 10 shows that a budget amount of "70,000 yen" is set for a "worker" performing work by the "construction department" with department code "100" in "April 2021" for a case with case code "K001". Similarly, the example in FIG. 10 shows that a budget amount of "140,000 yen" is set for a "worker" performing work by the "construction department" with department code "100" in "May 2021" for a case with case code "K001".

The example in FIG. 10 also shows that a budget amount of "30,000 yen" has been set for the "supervisor" for work performed by the "Construction Department" with department code "100" in "April 2021" for a case with case code "K002". The example in FIG. 10 also shows that a budget amount of "30,000 yen" has been set for the "supervisor" for work performed by the "Construction Department" with department code "100" in "April 2021" for a case with case code "K003".

Next, FIG. 11 is a schematic diagram showing an example of the man-hour planning table 14 of the cost server device 11 shown in FIG. 1. The example in FIG. 11 shows that a budget amount of "70,000 yen" is set for "Nakagawa-san" with worker code "1003" who will perform "assistant" work in "April 2021" for a case with case code "K001". The example in FIG. 11 also shows that a budget amount of "140,000 yen" is set for "Nakagawa-san" with worker code "1003" who will perform "assistant" work in "April 2021" for a case with case code "K002".

The example in FIG. 11 also shows that a budget amount of "35,000 yen" has been set for "Nakagawa-san" with worker code "1003" who will perform "assistant" work in "May 2021" for a case with case code "K001". The example in FIG. 11 also shows that a budget amount of "30,000 yen" has been set for "Nakagawa-san" with worker code "1003" who will perform "assistant" work in "May 2021" for a case with case code "K002".

Next, FIG. 12 is a schematic diagram showing an example of a worker-specific case table 27. In this worker-specific case table 27, worker, year and month, case, work content, and ratio are stored in association with each other. The "ratio" is set based on the budget amount allocated to each case that the worker is scheduled to work on in that month. The planned work time for each worker for each case is calculated based on this "ratio." This will be described in more detail later.

The example in Figure 12 shows that in April 2021, the proportion of "K001" cases performed by "Yamashita-san" with worker code "1001" is "70%", and that in April 2021, the proportion of "K003" cases performed by "Yamashita-san" is "30%". In other words, this shows that in April 2021, "Yamashita-san" is scheduled to work on "K001" cases and "K003" cases in a ratio of 70:30.

Similarly, the example in Figure 12 shows that in April 2021, the proportion of "K002" cases performed by "Kinoshita-san" with worker code "1002" is "50%, and the proportion of "K003" cases performed by "Kinoshita-san" in April 2021 is "50%". In other words, this shows that "Kinoshita-san" is scheduled to work on "K002" cases and "K003" cases in a 50:50 ratio in April 2021.

Similarly, the example in Figure 12 shows that in April 2021, the proportion of "K001" cases performed by "Nakagawa-san" with worker code "1003" is "33%", and that in April 2021, the proportion of "K002" cases performed by "Nakagawa-san" is "67%". In other words, this shows that "Nakagawa-san" is scheduled to work on "K001" cases and "K002" cases in a ratio of 33:67 in April 2021.

Next, FIG. 13 is a schematic diagram showing an example of the work schedule table 28. As shown in FIG. 13, the work schedule table 28 stores dates, workers, weekday/holiday classifications, and scheduled work times in association with each other. The example in FIG. 13 shows that "Yamashita-san," whose work code is "1001," is scheduled to work "8 hours" on the "weekdays" of "April 1, 2021" and "April 2, 2021." The example in FIG. 13 also shows that "Yamashita-san" is scheduled to work "0 hours" on the "regular holiday" of "April 3, 2021" and the "legal holiday" of "April 4, 2021."

Next, FIG. 14 is a schematic diagram showing an example of an attribute-specific work table 29. As shown in FIG. 14, the attribute-specific work table 29 stores the employment type and work type of workers associated with each job type. Specifically, it shows that a "full-time employee" can be employed as a "worker" who performs the "on-site work" of a project. It also shows that a "full-time employee" can be employed as a "supervisor" who performs the "supervisory work" of a project. It also shows that a "temporary worker" can be employed as an "assistant" who performs the "supporting work" of a project.

Next, FIG. 15 is a schematic diagram showing an example of a work schedule table 30. In this work schedule table 30, cases, the date on which work on the case will be performed, and the worker who will perform the work on the case are stored in association with each other. The example in FIG. 15 shows that a case with case code "T001" scheduled to be worked on on "April 1, 2021" is scheduled to be worked on by "Kanzaki-san" with worker code "1005". The example in FIG. 15 also shows that a case with case code "Y001" scheduled to be worked on on "April 2, 2021" is scheduled to be worked on by "Kanzaki-san" with worker code "1005".

Next, FIG. 16 is a schematic diagram showing an example of a daily report schedule table 31 in which daily report schedule data generated by the business support device 1 of the embodiment is stored. As shown in FIG. 16, the daily report schedule table 31 stores daily report schedule data in which the scheduled work time for each case and each worker scheduled for a specific date is calculated and input based on the above-mentioned "ratio (see FIG. 12)."

The example in Figure 16 shows that on April 1, 2021, "Yamashita-san" with worker code "1001" is scheduled to work on-site for a case with case code "K001" and a case with case code "K003", and that the work time for each case is scheduled to be "5.6 hours" and "2.4 hours" based on the above-mentioned "ratio".

The example in Figure 16 also shows that on April 1, 2021, Kinoshita-san, whose worker code is 1002, is scheduled to supervise the case with case code K002 and the case with case code K003, and that the working hours for each case are scheduled to be 4 hours and 4 hours, based on the above-mentioned ratio.

Next, FIG. 17 is a schematic diagram showing an example of a daily report table 32 in which daily report data generated by the business support device 1 of the embodiment is stored. In the case of the business support device 1 of the embodiment, the daily report data shown in FIG. 17 is displayed via the output device 7 based on the daily report schedule data. If there is an error in the daily report schedule data, the business operator manually corrects it. As a result, corrected daily report data is generated and stored in the daily report table 32.

For example, in the example of Figure 17, the supporting work for case "K001" on "April 1, 2021" was scheduled to be done by "Nakagawa-san", but "Nakagawa-san" worked for "3 hours" and left early, and "Sato-san" worked on supporting work for case "K001" in the afternoon. In this case, the business operator corrects Nakagawa-san's working hours in the morning from "2.6 hours" to "3 hours". The business operator also corrects the worker from "Nakagawa-san" to "Sato-san" whose worker code is "1007", and also corrects the working hours to, for example, "5 hours" worked by Sato-san.

Daily report data corresponding to the daily report schedule data thus corrected is generated and stored in the daily report table 32. Alternatively, if no correction is required, the daily report schedule data is stored as is in the daily report table 32 as daily report data.

(Functional configuration of the business support device)
Next, the control unit 3 of the business support device 1 executes the business support program stored in the memory unit 2, and thereby functions as a communication control unit 41, an acquisition unit 42, a calculation method identification unit 43, a calculation unit 44, a data generation unit 45, and a display control unit 46, as shown in FIG. 1.

The communication control unit 41 communicates with the accounting server device 9, the procurement server device 10, and the cost server device 14 via the communication interface unit 4 and the network 8 to acquire budget data, budget arrangement data, and budget labor-hour data. The acquisition unit 21 imports the budget data, budget arrangement data, and budget labor-hour data acquired from each of the server devices 9 to 11 into the system of the business support device 1.

The calculation method identification unit 43 identifies a calculation method for the planned work time of each worker based on the schedule type of each worker. Specifically, in the case of a worker whose schedule type is "budget," "budget arrangement," or "budget man-hours," the calculation method identification unit 43 identifies the calculation method based on the above-mentioned "ratio" as the calculation method for calculating the planned work time of each worker. In addition, in the case of a "work instruction" schedule type, the calculation method identification unit 43 identifies a calculation method for apportioning the work time for one day based on the number of cases or the number of work types for that day as the calculation method for calculating the planned work time of each worker. In addition, in the case of a "work performance" schedule type, the calculation method identification unit 43 identifies a calculation method for calculating the planned work time of each worker based on the time actually worked on each case (= work performance) as the planned work time of the worker.

The calculation unit 44 calculates the planned work time for each worker's case using the calculation method identified by the calculation method identification unit 43. The data generation unit 45 generates various data to be stored in each of the masters 21-23 and each of the tables 24-32. The display control unit 46 displays a worker-specific case master screen and a daily report schedule data creation screen, which will be described later, via the output device 7.

(Overview of the operation of the business support device)
Next, an outline of the operation of the business support device 1 according to the embodiment is shown in Fig. 18. As shown in Fig. 18, the business support device 1 according to the embodiment generates daily report schedule data including the scheduled work time of the worker for each case based on the work plan data, the order detail data, the work plan data, etc., by using a "daily report registration support function" executed based on the business support program.

The generated daily report schedule data for each worker is acquired in a lump sum (batch processing is executed) and stored as daily report data in the daily report table 32 of the storage unit 2. In addition, the daily report schedule data can be manually modified by the business operator using the "daily report input function", and the modified daily report schedule data is stored as daily report data in the daily report table 32.

That is, the business support device 1 of the embodiment automatically generates daily report schedule data including the predicted working time for each case of each worker based on various data. Then, if this daily report schedule data does not need to be modified, it is stored as is in the daily report table 32 as daily report data. Also, if the daily report schedule data needs to be modified, the business operator manually modifies the daily report schedule data, and the modified daily report schedule data is stored in the daily report table 32 as daily report data. This makes it possible to significantly reduce the input work required by the business operator when creating daily report data.

(Detailed operation of the business support device)
The operation of creating daily report data in the task support device 1 according to the embodiment will be described in detail below.

(Operation of forming a case table by worker)
Prior to generating daily report schedule data and daily report data, the business support device 1 of the embodiment creates an individual worker case table 27 in which the "ratio" shown in Fig. 12 is stored. Fig. 19 is a flowchart showing the flow of the operation of creating the individual worker case table 27. The control unit 3 operates based on the business support program stored in the storage unit 2 to execute each process shown in the flowchart of Fig. 19.

First, when creating the worker-specific case table 27, the business operator operates the input device 6 to specify the display of the worker-specific case master screen. When this display specification operation is performed, the display control unit 46 displays the worker-specific case master screen illustrated in FIG. 20 via the output device 7 (step S1).

When this worker-specific case master screen is displayed, the business operator selects the person in charge (= worker) for whom the "ratio" described above is to be calculated from the selection field for the person in charge (= worker) and specifies the year and month. In the example of Figure 20, "Yamashita-san" is selected as the person in charge, and "April 2021" is specified as the year and month.

When a person in charge is selected in this manner, the acquisition unit 42 acquires the department, job type, and budget type of the selected person in charge by referring to the worker attribute table 24 shown in FIG. 6 (step S2). In the example of FIG. 20, since "Yamashita-san" has been selected as the person in charge, the acquisition unit 42 acquires the worker attribute data of "Yamashita-san" shown in FIG. 6, which are "100: Construction Department" as the department, "Worker" as the job type, and "Budget" as the schedule type. The display control unit 46 displays the acquired department and job type adjacent to the person in charge's name as shown in FIG. 20.

Next, the acquisition unit 42 (and the communication control unit 41) acquires the budget amount that corresponds to the plan type acquired in step S2 and that corresponds to the budget year/month and department (step S3). For example, in the example of FIG. 20, the plan type of the worker "Yamashita-san" is "budget." In this case, the communication control unit 41 communicates with the accounting server device 12 and acquires the budget amount that corresponds to the budget type stored in the budget management table 12 and that corresponds to the budget year/month and department.

In the example of FIG. 20, "April 2021" is specified as the budget year and month, and "100: Construction Department" is specified as the department. Therefore, from the budget data shown in FIG. 9, the communication control unit 41 acquires "210,000 yen", which is the budget amount for the "K001" case that "100: Construction Department" is scheduled to work on in "April 2021", and "90,000 yen", which is the budget amount for the "K003" case. This budget amount is imported into the system by the acquisition unit 42.

Next, the calculation unit 44 calculates the ratio of the work that the worker will perform for each case based on the budget amount for each case that the worker is scheduled to work on, and stores the ratio together with the case in the worker-specific case table 27 shown in FIG. 12 (step S4). In addition, the display control unit 46 displays the "case," "budget amount that was the element used to calculate the ratio," and "ratio calculated by the calculation unit 44" on the worker-specific case master screen, as shown in FIG. 20.

Specifically, the budget amount for project "K001" in "April 2021" for "100: Construction Department" to which "Yamashita-san" belongs is "210,000 yen," and the budget amount for project "K003" is "90,000 yen." Therefore, the calculation unit 44 calculates the work ratio for each of projects "K001" and "K003" that "Yamashita-san" plans to work on in "April 2021" by calculating "K001:K003 = 210,000 yen:90,000 yen = 70%:30%." As shown in FIG. 20, the display control unit 46 displays on the worker-specific case master screen the result of the calculation of the work ratio for case "K001" using "210,000 yen" as the calculation element, which is "70%," and the result of the calculation of the work ratio for case "K003" using "90,000 yen" as the calculation element, which is "30%".

This calculation of the work ratio is repeated for each worker (step S5: Yes). Then, when the calculation of the work ratio for each worker is completed (step S5: No), the worker-specific case table 27 shown in FIG. 12 is formed, and all the processing in the flowchart of FIG. 19 is completed.

(Daily report schedule data creation operation)
When the worker-specific case table 27 is formed in this manner, it becomes possible to create daily report schedule data. Fig. 21 is a flowchart showing the flow of the operation of creating daily report schedule data. Each process in the flowchart of Fig. 21 is executed by the control unit 3 based on the business support program stored in the storage unit 2.

When creating daily scheduled data, the business operator operates the input device 6 to display the daily scheduled data creation screen. When this display operation is performed, the display control unit 46 displays the daily scheduled data creation screen illustrated in FIG. 22 via the output device 7 (step S11).

Next, the business operator operates the department selection field on the daily schedule data creation screen to select the desired department for which to create daily schedule data. The business operator also inputs the period for which the daily schedule data is to be created, and selects the worker code of the worker for whom the daily schedule data is to be created. The example in FIG. 22 is an example in which the construction department with department code "100" is selected as the department. The example in FIG. 22 is also an example in which "April 1, 2021 to April 20, 2021" is entered as the period for which the daily schedule data is to be created. The example in FIG. 22 is also an example in which "1001 (Yamashita-san) to 1003 (Nakagawa-san)" are selected as the worker codes.

Based on the various information selected and input on the daily schedule data creation screen, the calculation unit 44 recognizes the department, period, and worker for which the daily schedule data is to be created (step S12).Then, the calculation unit 44 monitors whether or not the schedule creation button provided on the daily schedule data creation screen is operated (step S13).

When the operation of the schedule creation button is detected (step S13: Yes), the calculation unit 44 calculates the work time for each case for each worker based on the ratio of work for each case for which each worker is scheduled to work, which is stored in the worker-specific case table 27 shown in FIG. 12 (step S14).

Specifically, as shown in FIG. 13, in the work schedule table 28, the "scheduled work time" of "Yamashita-san" on "weekday" of "April 1, 2021" is "8 hours". In addition, in the worker-specific case table 27 shown in FIG. 12, the work ratio of "Yamashita-san" in "April 2021" is "70%" for the "K001" case and "30%" for the "K003" case. Therefore, by performing the following calculation, the calculation unit 44 calculates "5.6 hours", which is "70%", of the 8 hours of work time of "Yamashita-san" on "April 1, 2021" as the planned work time for the "K001" case, and calculates the remaining "2.4 hours", which is "30%," as the planned work time for the "K003" case.

K001 scheduled work hours = 8 hours of work on weekdays x 70% = 5.6 hours K003 scheduled work hours = 8 hours of work on weekdays x 30% = 2.4 hours

As another example, in the case of "Kinoshita-san" on a "weekday" on "April 1, 2021", as shown in FIG. 12, the work ratio for case "K002" is "50%" and for case "K003" is "50%". Therefore, the calculation unit 44 performs the following calculation to calculate "4.0 hours", which is "50%", of the 8 hours of work time of "Kinoshita-san" on "April 1, 2021", as the planned work time for case "K002", and calculates the remaining "4.0 hours", which is "50%," as the planned work time for case "K003".

K002 scheduled work hours = 8 hours of work on weekdays x 50% = 4.0 hours K003 scheduled work hours = 8 hours of work on weekdays x 50% = 4.0 hours

As another example, in the case of "Mr. Nakagawa" on a "weekday" on "April 1, 2021", as shown in FIG. 12, the work ratio for case "K001" is "33%" and for case "K002" is "67%". Therefore, by performing the following calculation, the calculation unit 44 calculates "approximately 2.6 hours", or "33%," of the 8 hours of work time for "Mr. Nakagawa" on "April 1, 2021" as the planned work time for case "K001", and calculates the remaining "approximately 5.4 hours", or "67%," as the planned work time for case "K003".

K001 scheduled work hours = 8 hours of work on weekdays x 33% ≒ 2.6 hours K003 scheduled work hours = 8 hours of work on weekdays x 50% ≒ 5.4 hours

The above explanation was an example of a calculation method that calculates the planned work time for each project based on the "ratio" of work for each project, since the planned type for each worker is "budget," "budget arrangement," or "budget man-hours." In contrast, as shown in Figure 6, the planned type for "Yoshida-san" is "work instructions," and the planned type for "Kanzaki-san" is "work results."

When the planned type is "work instructions" like "Mr. Yoshida", the calculation unit 44 uses a calculation method of dividing the working hours by the number of cases or the number of work types (work contents) for which work is instructed on the specified date to calculate the planned work time. Specifically, in this case, the calculation unit 44 refers to the work instruction table 25 shown in FIG. 7 and detects the number of cases and the work types (work contents) for which work is instructed on the specified date. For example, if work on cases "K001" and "K002" is instructed for "Mr. Yoshida" on "April 1, 2021", the number of cases is "2", so the calculation unit 44 calculates "8 hours ÷ 2 cases = 4 hours". In this case, the planned work time for case "K001" is set to "4 hours", and the planned work time for case "K002" is also set to "4 hours".

Similarly, if "Yoshida" is instructed to perform "design work" and "site investigation" for project "K001" on "April 1, 2021," the number of work types (work contents) is "2," so the calculation unit 44 calculates "8 hours ÷ 2 = 4 hours." In this case, the planned work time for "design work" for project "K001" is set to "4 hours," and the planned work time for "site investigation" is also set to "4 hours."

In contrast, when the planned type is "work performance" like "Kanzaki-san" (see FIG. 6), the calculation unit 44 uses a calculation method in which the actual work time of each task that has already been performed on the specified date, which is recorded in the work performance table 26 shown in FIG. 8, is taken as the planned work time. For example, assume that "Kanzaki-san" performed "packing" work for "5.6 hours" as the first half of "April 1, 2021", and performed "packing" work for "2.4 hours" as the second half of "packing" work. In this case, the calculation unit 44 determines the "5.6 hours" of the first half of "packing" work on "April 1, 2021" as the planned work time, and the "2.4 hours" of the second half of "packing" work as the planned work time.

"Yoshida-san" has specific instructions for the work, and "Kanzaki-san" is a worker with specific work experience. Therefore, the planned work times for "Yoshida-san" and "Kanzaki-san" can be easily detected and calculated by referring to the work instruction table 25 or the work experience table 26.

Next, the data generation unit 45 generates daily report schedule data including the planned work time, date, worker, case, and work type calculated by the calculation unit 44, and stores the data in the daily report schedule table 31 as shown in FIG. 16 (step S15).

The example in FIG. 16 is an example of daily schedule data for "Yamashita-san," "Kinoshita-san," "Nakagawa-san," "Yoshida-san," and "Kanzaki-san" scheduled for "April 1, 2021." For example, in the case of "Yamashita-san" with a schedule type of "budget," "Kinoshita-san" with a schedule type of "budget arrangement," and "Nakagawa-san" with a schedule type of "budget man-hours," the scheduled work time calculated using a "ratio" based on the budget amount of each project described above is stored in the daily schedule table 31. In addition, in the case of "Yoshida-san" with a schedule type of "work instructions," the scheduled work time calculated by apportioning the working hours of each project or each job type is stored in the daily schedule table 31. In addition, in the case of "Kanzaki-san" with a schedule type of "work performance," the time for each type of work performed is stored in the daily schedule table 31.

In the business support device 1 of the embodiment, such daily report schedule data can be automatically created. Therefore, the business operator can create the daily report data described below based on the daily report schedule data, reducing the amount of data that needs to be input and allowing the daily report data to be created with simple tasks. In other words, in the case of the business support device 1 of the embodiment, the daily report schedule data that is the source of the daily report data can be automatically created. By creating the daily report data based on this daily report schedule data, the daily report data can be created with simple tasks.

In addition, within the same company, there are a mixture of workers who are instructed to do specific tasks, such as "Mr. Yoshida" and "Mr. Kanzaki," and workers who simultaneously handle multiple jobs, such as a site supervisor or project manager. However, in the case of the business support device 1 of the embodiment, even for a worker who simultaneously handles multiple jobs, such as a site supervisor or project manager, the planned work time can be calculated based on the "ratio" of the planned work as described above. Therefore, the daily report schedule data and the daily report data described later can be created by treating workers who simultaneously handle multiple jobs, such as a site supervisor or project manager, and workers who are instructed to do specific tasks, such as "Mr. Yoshida" and "Mr. Kanzaki," in the same way (treating all workers in the same company in the same way).

(Daily report data creation operation)
Next, an operation of creating daily report data based on daily report schedule data in the business support device 1 of the embodiment will be described. Fig. 23 is a flowchart showing the flow of the operation of creating daily report data. Each process in the flowchart of Fig. 23 is executed by the control unit 3 based on the business support program stored in the storage unit 2. First, in step S21, the data generation unit 45 monitors whether or not there is an instruction operation by the business operator to instruct the creation of daily report data, and when this instruction operation is detected (step S21: Yes), the display control unit 46 displays the daily report schedule data shown in Fig. 16 via the output device 7 (step S22).

The business operator looks at the displayed daily report schedule data, determines whether there are any deficiencies, and if he or she recognizes an deficiency, performs a correction operation to specify the correction and corrects the relevant portion. In step S23, the data generation unit 45 monitors whether this correction operation has been performed. If a correction operation has not been performed (step S23: No), the data generation unit 45 stores the daily report schedule data as daily report data in the daily report table 32 (step S25), as shown in FIG. 17.

On the other hand, if a correction operation is performed (step S23: Yes), the data generation unit 45 corrects and inputs the relevant part of the daily report schedule data in accordance with the correction operation by the business operator (step S24).

For example, suppose that the supporting work for case "K001" on "April 1, 2021" was scheduled to be done by "Nakagawa-san", but "Nakagawa-san" worked for "3 hours" and then left early, and "Sato-san" worked on supporting work for case "K001" in the afternoon. In this case, as shown in FIG. 17, the business operator corrects Nakagawa-san's morning work hours in the daily report schedule data from "2.6 hours" to "3 hours". The business operator also corrects the worker in the daily report schedule data from "Nakagawa-san" to "Sato-san" whose worker code is "1007", and also corrects the working hours to, for example, "5 hours" worked by Sato-san.

In this way, by making it possible to modify daily report schedule data, it is possible to generate more accurate daily report data.

The data generation unit 45 stores the revised daily report schedule data in the daily report table 32 as daily report data (step S25). This completes the entire process of creating the daily report data shown in the flowchart of FIG. 23.

(Effects of the embodiment)
As is clear from the above description, the business support device 1 according to the embodiment can create daily report schedule data with a certain level of accuracy by combining existing information such as budgets, orders, work plans, etc. This can significantly reduce the administrative workload of business operators who create daily report data for reporting work hours.

Conventionally, cost management has often been performed based on the manager's intuition. However, in the case of the business support device 1 of the embodiment, the complexity of work time management and the administrative workload can be reduced, making it possible to perform cost management with improved accuracy and timeliness. Therefore, not only can the administrative workload be reduced, but the accuracy of profit management can also be improved.

[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 the achievement of SDGs Goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[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 search conditions and other parameters, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

In addition, with regard to the business support device 1, 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 business support device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) 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 business support device 1 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD to work 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 configure the control unit 3.

The business support program of the business support device 1 may also be stored in another server device connected to the business support device 1 via any network, and all or part of it may be downloaded as needed.

The business support 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.

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 structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by working with a separate program, such as an OS. Note that the specific structure and reading procedure for reading a recording medium in the business support device 1 shown in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

The business support device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes 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 function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful for tasks that involve creating daily or monthly work reports, for example in the general construction industry (construction, civil engineering, design, etc.) as well as in industries where labor cost management is important.

LIST OF NUMERALS 1 Business support device 2 Memory unit 3 Control unit 4 Communication interface unit 5 Input/output interface unit 6 Input device 7 Output device 8 Network 9 Accounting server device 10 Procurement server device 11 Cost server device 12 Budget management table 13 Order details table 14 Man-hour plan table 21 Schedule data management master 22 Linkage mapping master 23 Work hour master 24 Worker attribute table 25 Work instruction table 26 Work performance table 27 Worker-specific case table 28 Work schedule table 29 Attribute-specific work pattern table 30 Work schedule table 31 Daily report schedule table 32 Daily report table 41 Communication control unit 42 Acquisition unit 43 Calculation method specification unit 44 Calculation unit 45 Data generation unit 46 Display control unit

Claims (7)

a calculation method specification unit that specifies a calculation method of a work time for each person to be created for a work report based on a schedule type set for the person to be created for the work report;
A calculation unit that calculates a scheduled work time of each of the creation subjects based on the calculation method specified by the calculation method specification unit;
a data generating unit that generates work report planned data including the work planned time calculated by the calculating unit, a case in which the person to be created will work, and the person to be created who will work on the case;
the calculation unit calculates the planned work time for the case in which the creation target person is to perform work, based on a ratio of a budget amount for each of the cases allocated to the cases for each predetermined period;
A business support device comprising : the calculation unit calculates, as the scheduled work time of the case to be performed by the target person, a time obtained by dividing the work time by the number of the cases or the number of work types for which work instructions have been given;
2. The business support device according to claim 1 , the calculation unit calculates the work time that the target person will have as a work result of the project as the planned work time;
3. The business support device according to claim 1 or 2 , the data generation unit generates work report data indicating the person to be created and a work result of a case on which the person to be created has performed work, based on the work report schedule data;
4. The business support device according to claim 1, wherein : the data generation unit generates the work report data by correcting the work report schedule data in response to a correction input operation;
5. The business support device according to claim 4 , a calculation method specifying step of specifying a calculation method of the work time for each person to be created for the work report based on a schedule type set for each person to be created for the work report by a calculation method specifying unit;
A calculation step in which a calculation unit calculates a scheduled work time of each of the creation subjects based on the calculation method identified in the calculation method identification step;
a data generating step of generating work report planned data including the work planned time calculated in the calculating step, a task on which the target person is to work, and the target person who is to work on the task,
In the calculation step, the planned work time for the case to be performed by the subject person is calculated based on a ratio of a budget amount for each of the cases allocated to the cases for each predetermined period;
A business support method comprising : Computer,
a calculation method specification unit that specifies a calculation method of a work time for each person to be created for a work report based on a schedule type set for the person to be created for the work report;
A calculation unit that calculates a scheduled work time of each of the creation subjects based on the calculation method specified by the calculation method specification unit;
a data generating unit that generates work report planned data including the work planned time calculated by the calculation unit, a task for which the target person is to perform work, and the target person who is to perform the work on the task;
When causing the computer to function as the calculation unit, causing the computer to function so as to calculate the planned work time for the case in which the subject person is to perform work, based on a ratio of a budget amount for each of the cases allocated to the cases for each predetermined period;
A business support program that features:

Images