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

Description

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

Patent Document 1 discloses a contract information analysis device that can grasp the changes in fixed-term contract data in which sales are recorded periodically and perform discrepancy analysis.

JP 2020-166623 A

However, although Patent Document 1 describes cases in which the fees to be incurred change as a result of changes to the contract contents, it does not describe or suggest that when the work schedule changes within the same contract contents, the reason for the change in the work schedule should be reflected in the billing data.

The present invention has been made in consideration of the above, and aims to provide a business support device, a business support method, and a program that can easily collect and analyze the causes of discrepancies when discrepancies occur between actual work results and plans.

In order to solve the above-mentioned problems and achieve the object, the business support device according to the present invention is a business support device having a control unit, and is capable of accessing contract data storing the contract contents of each task related to the maintenance of a property, and billing data for managing performance data related to billing for each task included in the contract data at each work period, the billing data storing scheduled data to be executed based on the contract contents for each billing, and storing, for each billing, reasons for changes when the scheduled data is changed, and the control unit refers to the contract data to identify the contract contents linked to a specified contract partner and property, and extracts from the billing data the performance data linked to the identified contract contents and the specified work period. and outputting the extracted performance data on a screen, and when a change to the performance data is made on the screen accompanied by inputting a reason for the change, storing the input reason for the change in the billing data and rewriting the performance data to be changed stored in the billing data with the changed performance data displayed on the screen; and output control means that refers to the contract data to identify contract details linked to the specified contracting party and property, extracts from the billing data billing data that satisfies the conditions that it is linked to the identified contract details, that scheduled data includes the specified work time, and that a reason for the change is registered, and outputs the extracted billing data in a manner that allows a comparison between the scheduled and actual billing data.

The business support device according to the present invention is further characterized by having a calculation means for calculating the billing amount for each of the fluctuation reasons during the selected calculation period.

The business support method according to the present invention is a business support method executed by a business support device having a control unit, in which the control unit accesses contract data storing the contract contents of each task related to the maintenance of a property, and billing data for managing performance data related to billing for each task included in the contract data at a work period unit, the billing data storing scheduled data to be executed based on the contract contents for each billing, and storing a reason for change when the scheduled data is changed for each billing, to thereby refer to the contract data and identify the contract contents linked to the specified contract partner and property, and to extract performance data linked to the identified contract contents and the specified work period from the billing data, The system includes a change step of outputting the collected performance data to a screen, and if a change to the performance data is made on the screen accompanied by inputting a reason for the change, storing the input reason for the change in the billing data and rewriting the performance data to be changed stored in the billing data with the changed performance data displayed on the screen; and an output control step of referring to the contract data to identify contract details linked to the specified contracting party and property, extracting from the billing data billing data that satisfies the conditions that it is linked to the identified contract details, that scheduled data includes the specified work time, and that a reason for the change is registered, and outputting the extracted billing data in a manner that allows a comparison between the scheduled and actual billing data.

The program according to the present invention is a program executed by a business support device having a control unit, and causes the control unit to access contract data storing the contract details of each task related to the maintenance of a property, and billing data for managing performance data related to billing for each task included in the contract data at each work period, the billing data storing scheduled data to be executed based on the contract details for each billing, and storing, for each billing, reasons for changes when the scheduled data is changed, thereby referring to the contract data to identify contract details linked to a specified contracting party and property, and extracting performance data linked to the identified contract details and the specified work period from the billing data. The system is characterized by executing a change step in which the result data that has been changed is output to a screen, and when a change to the result data is made on the screen accompanied by input of a reason for the change, the input reason for the change is stored in the billing data, and the result data to be changed that is stored in the billing data is rewritten to the changed result data displayed on the screen; and an output control step in which the contract content linked to the specified contracting party and the property is identified by referring to the contract data, billing data that satisfies the conditions that it is linked to the identified contract content, that scheduled data includes the specified work time, and that a reason for the change is registered is extracted from the billing data, and the extracted billing data is output in a manner that allows a comparison between the scheduled and actual billing data.

The present invention has the advantage that when a difference occurs between the actual work results and the plan, the causes of the difference can be easily compiled and analyzed.

FIG. 1 is a block diagram showing an example of a configuration of a task support device. FIG. 2 is a flowchart showing an example of a flow of a process performed by the task support device. FIG. 3 is a diagram showing an example of the contract data. FIG. 4 is a diagram showing an example of detailed schedule data. FIG. 5 is a diagram showing an example of pre-change billing data. FIG. 6 is a diagram illustrating an example of the performance data. FIG. 7 is a diagram showing an example of the changed billing data. FIG. 8 is a diagram showing an example of a variable input list. FIG. 9 is a diagram showing an example of the tabulation results for each reason for change.

Below, an embodiment of a business support device, a business support method, and a program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Overview]
First, an overview of the task assistance performed by the task assistance device 100 will be described.

The business support device 100, which is an example of an embodiment of the present invention, is used, for example, to support business operations in a building maintenance company. When creating an annual budget, the building maintenance company accumulates monthly planned figures for sales and costs based on contracts that have already been concluded. When comparing the budget and actual results on a monthly basis, discrepancies often occur.

This discrepancy occurs when a discrepancy occurs between the planned work and the actual work that has been performed. For example, "the planned glass cleaning work could not be carried out due to weather, so the cost was not recorded until the following month," "the location where daily work was carried out overlaps with the location where repair work was carried out, so the cost incurred was less than the planned monthly amount," or "work was halted for several months due to the implementation of large-scale construction work," etc.

In this way, the business support device 100, which is an example of an embodiment of the present invention, creates and displays a form called a variable input list 22 (see FIG. 8) that allows the comparison of the plan and actual results for each task when a discrepancy occurs between the plan and actual results.

The specific configuration and operation of the business support device 100 are described below.

2. Configuration
First, the configuration of a task assistance 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 task assistance device 100.

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

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

The communication interface unit 104 communicatively connects the business support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of communicatively connecting the business support device 100 and an in-house PC 200 used by an employee. The network 300 is, for example, the Internet or a LAN (Local Area Network). Employees can use the business support device 100 from their own in-house PC 200 via the network 300.

The input/output interface unit 108 is also connected to an input device 112 and an output device 114. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. Therefore, employees can use the input device 112 and the output device 114 to use the business support device 100. The output device 114 is an example of a screen in this disclosure.

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

In addition to the computer programs described above, the memory unit 106 stores a contract data file 106a, a detailed schedule data file 106b, a pre-change billing data file 106c, a performance data file 106d, and a post-change billing data file 106e.

The contract data file 106a stores, for example, contract data 12 (see Figure 3) that contains the contract details for each task related to the maintenance of the property.

The detailed schedule data file 106b stores detailed schedule data 14 (see FIG. 4) that includes the expected billing amount per work period (e.g., per month) that is generated based on the contract details stored in the contract data file 106a.

The pre-change billing data file 106c stores pre-change billing data 16 (see Figure 5) that includes billing amounts for each work period (e.g., month) that are expected to occur for each task included in the contract data file 106a.

The performance data file 106d stores performance data 18 (see FIG. 6) including the amount actually charged per work period for each task included in the contract data file 106a. Note that the performance data file 106d also includes the reason for any change that may occur, such as a change in the timing of the originally scheduled work.

The changed billing data file 106e stores changed billing data 20 (see FIG. 7) that includes the work content results and the actual billing amount for each work period (e.g., month), which is generated based on the contents of the actual results data file 106d. The changed billing data file 106e also includes the reason for any change that occurs, such as a change in the timing of the work that was originally scheduled.

Details of the specific items contained in the data stored in each data file are explained in [4. Specific examples of processing] below.

The control unit 102 is a CPU or the like that performs overall control of the business support 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 operations based on these stored programs.

The control unit 102 has as its functional parts a contract data creation unit 102a, a detailed schedule data creation unit 102b, a pre-change billing data creation unit 102c, a performance data creation unit 102d, a change reason input unit 102e, a post-change billing data creation unit 102f, a comparison request acceptance unit 102g, a comparison result display unit 102h, a data storage unit 102i, a data reading unit 102j, and a data transmission/reception unit 102k.

The contract data creation unit 102a creates contract data 12 for each property related to the contract based on input operations from the input device 112 or the in-house PC 200.

The detailed schedule data creation unit 102b creates detailed schedule data 14 by tallying up the predicted monthly billing amounts by task and by month based on the contents of the contract data 12.

The pre-change billing data creation unit 102c creates pre-change billing data 16 that predicts the expected monthly billing amount based on the contents of the detailed schedule data.

The performance data creation unit 102d creates performance data 18 by aggregating performance data generated by task and month. The performance data creation unit 102d also accepts input of approval for the created performance data 18.

The change reason input unit 102e accepts input of a change reason when a change occurs in the performance data 18 created by the performance data creation unit 102d from the pre-change billing data 16.

The changed billing data creation unit 102f refers to the contract data 12 to identify the contract details linked to the specified contract partner and property, extracts from the pre-change billing data 16 performance data 18 linked to the identified contract details and the specified work period, outputs the extracted performance data 18 to the output device 114 (screen), and if a change to the performance data 18 is made on the screen accompanied by input of a change reason, stores the input change reason in the changed billing data 20 and rewrites the performance data 18 to be changed that is stored in the pre-change billing data 16 to the changed performance data 18 displayed on the screen. This creates the changed billing data 20. The changed billing data creation unit 102f is an example of a change means in this disclosure.

The comparison request receiving unit 102g receives a request to compare the plan with the actual results.

The comparison result display unit 102h refers to the contract data 12, identifies the contract contents linked to the specified contract partner and property, extracts from the changed billing data 20 changed billing data 20 that is linked to the identified contract contents, that the detailed schedule data 14 includes the specified work time, and that a reason for change is registered in the changed billing data 20, and outputs the extracted changed billing data 20 in a form that allows comparison of the planned and actual billing data. An example of a form that allows comparison of the planned and actual billing data is the variable input list 22 (see FIG. 8) described later. The variable input list 22 will be described in detail later. The comparison result display unit 102h is an example of an output control means in this disclosure.

The data storage unit 102i stores the various data created by each of the above-mentioned units in the memory unit 106.

The data reading unit 102j reads the specified data from the memory unit 106.

The data transmission/reception unit 102k transmits and receives necessary data between the business support device 100 and the in-house PC 200. The flow of the process executed by the business support device 100 is described below in [3. Process flow].

3. Processing Flow
The flow of processing according to this embodiment will be described in detail below with reference to Fig. 2. Fig. 2 is a flowchart showing an example of the flow of processing performed by the task assistance device 100.

First, the contract data creation unit 102a creates contract data 12 for each property related to the contract based on input operations from the input device 112 or the in-house PC 200 (step S11). The data storage unit 102i stores the created contract data 12 in the contract data file 106a.

The detailed schedule data creation unit 102b creates detailed schedule data 14 by tallying up the billing amounts predicted to occur each month for each task and each month (step S12). The data storage unit 102i stores the created detailed schedule data 14 in the detailed schedule data file 106b.

The pre-change billing data creation unit 102c creates pre-change billing data 16 that predicts the billing amount expected to occur each month (step S13). The data storage unit 102i stores the generated pre-change billing data 16 in the pre-change billing data file 106c.

The actual data creation unit 102d creates actual data 18 by tallying up the actual results for each task and month (step S14). At this time, if there is a difference between the pre-change billing data 16 and the actual data 18, the change reason input unit 102e accepts input of the change reason. The data storage unit 102i stores the generated actual data 18 in the actual data file 106d.

The change reason input unit 102e determines whether the actual data 18 has changed from the pre-change billing data 16 (step S15). If it is determined that the actual data 18 has changed from the pre-change billing data 16 (step S15: Yes), the process proceeds to step S16. On the other hand, if it is not determined that the actual data 18 has changed from the pre-change billing data 16 (step S15: No), the process proceeds to step S17.

When it is determined in step S15 that the actual performance data 18 has changed from the pre-change billing data 16, the change reason input unit 102e accepts input of the reason for the change (step S16).

Following step S16, or in step S15, if it is not determined that the performance data 18 has changed from the pre-change billing data 16, the performance data creation unit 102d determines whether the creation of the performance data 18 has been completed (step S17). If it is determined that the creation of the performance data 18 has been completed (step S17: Yes), the process proceeds to step S18. On the other hand, if it is not determined that the creation of the performance data 18 has been completed (step S17: No), the process returns to step S14.

When it is determined in step S17 that the creation of the performance data 18 has been completed, the performance data creation unit 102d determines whether approval for the created performance data 18 has been received (step S18). If it is determined that approval for the performance data 18 has been received (step S18: Yes), the process proceeds to step S19. On the other hand, if it is not determined that approval for the performance data 18 has been received (step S18: No), the process returns to step S14, where the performance data 18 is revised.

If it is determined in step S18 that approval for the performance data 18 has been received, the changed billing data creation unit 102f creates the changed billing data 20 (step S19). The data storage unit 102i stores the generated changed billing data 20 in the changed billing data file 106e.

The comparison request receiving unit 102g determines whether there is a comparison request between the pre-change billing data 16 and the post-change billing data 20 (step S20). If it is determined that there is a comparison request between the pre-change billing data 16 and the post-change billing data 20 (step S20: Yes), the process proceeds to step S21. On the other hand, if it is not determined that there is a comparison request between the pre-change billing data 16 and the post-change billing data 20 (step S20: No), the business support device 100 ends the process in FIG. 2.

When it is determined in step S20 that there is a request for comparison between the pre-change billing data 16 and the post-change billing data 20, the comparison result display unit 102h creates a variable input list 22 that enables comparison of the pre-change billing data 16 and the post-change billing data 20 (step S21).

Next, the comparison result display unit 102h outputs the created variable input list 22 to the output device 114 or the in-house PC 200 (step S22). After that, the business support device 100 ends the process of FIG. 2.

4. Specific examples of processing
A specific example of the process according to this embodiment will be described below with reference to Fig. 3 to Fig. 8. Note that a specific example of the process performed based on a contract for hotel management will be described here.

(Generation of contract data)
3 is a diagram showing an example of the contract data 12. The contract data 12 includes basic contract information data 12a and contract sales detail data 12b.

The contract basic information data 12a is data that stores basic information related to the contract. The contract basic information data 12a stores the contract number 121, the project name 122, the contracting party 123, the property 124, the contract start date 125, and the contract end date 126.

The contract number 121 is a unique identification number assigned to the contract. The project name 122 is, for example, the name of the contract. The contracting party 123 is the party that manages the contracted property. The property 124 is the specific property name. The contract start date 125 is the date on which the contract started. The contract end date 126 is the date on which the contract ends.

Contract sales detail data 12b is data that stores the contract details for each business related to hotel maintenance. Contract sales detail data 12b stores contract number 127, sales detail line 128, business type 129, business 130, unit price 131, quantity 132, unit 133, and billing amount 134.

Contract No. 127 is the same as Contract No. 121 described above. Sales detail line 128 is an identification number uniquely assigned to each task belonging to the contract. Industry 129 is the type of task to which each task belongs. Task 130 is the specific task name. Unit price 131 is the unit price of each task. Quantity 132 is the quantity of each task. Note that for "room cleaning" in sales detail line 3 shown in FIG. 3, no cost is incurred unless a guest uses the hotel. In other words, since the amount of work is not determined, "0" is stored in the contract sales detail data. Unit 133 is the unit of each task. Billing amount 134 is the amount billed per month for each task. In this way, the contract sales detail data 12b registers the detailed information that is billed monthly under the contract.

(Generation of detailed schedule data)
4 is a diagram showing an example of the detailed schedule data 14. The detailed schedule data 14 is data that stores billing amounts that are expected to occur in work period units (e.g., each month). The detailed schedule data 14 is made up of detailed schedule data 14a, 14b, 14c, and 14d for each sales statement line.

Detailed schedule data 14 is data that stores the monthly billing amount for each task registered in contract data 12. Detailed schedule data 14 stores contract number 141, sales detail line 142, work month 143, and billing amount 144.

Contract No. 141 corresponds to contract No. 121 registered in contract data 12. Sales detail line 142 corresponds to sales detail line 128 registered in contract data 12. Work month 143 indicates the year and month in which the work will occur. Billing amount 144 is the billing amount for the corresponding year and month.

For tasks that occur monthly, billing is expected to occur monthly, as shown in detailed schedule data 14a and 14d. For tasks that occur irregularly (e.g., once every six months), billing is expected to occur only in the month and year in which the task is scheduled to occur, as shown in detailed schedule data 14b. For tasks for which the amount completed is not yet determined, the billing amount is stored as "0," as shown in detailed schedule data 14c.

(Generating billing data before changes)
5 is a diagram showing an example of the pre-change billing data 16. The pre-change billing data 16 is data that stores billing amounts for each work period (e.g., month) that are expected to occur for each task included in the contract data 12. The pre-change billing data 16 stores a billing number 161, a contract number 162, a sales statement 163, an industry type 164, a task 165, a work month 166, a unit price 167, a quantity 168, a unit 169, and a billing amount 170. The pre-change billing data 16 also stores a reason for change 171, a pre-change work month 172, a pre-change unit price 173, a pre-change quantity 174, and a pre-change billing amount 175.

Billing No. 161 stores an identification number that is assigned to each task and uniquely identifies the billing item. Contract No. 162 corresponds to Contract No. 121 registered in Contract Data 12. Sales detail line 163 corresponds to Sales detail line 128 registered in Contract Data 12. Industry 164 and task 165 correspond to industry 129 and task 130, respectively, registered in Contract Data 12. Working month 166 is the year and month related to the billing data to be created. Unit price 167, quantity 168, and unit 169 correspond to unit price 131, quantity 132, and unit 133, respectively, registered in Contract Data 12. Billing amount 170 is the billing amount expected to occur for each task during the relevant period.

Furthermore, the reason for change 171 is the reason for the change, which is entered when a change occurs in the timing or content of the work. Details will be described later (see Figure 6). The work month before change 172 is the year and month when each work is expected to be performed. The unit price before change 173 is the unit price if it is assumed that the work is performed as planned. The quantity before change 174 is the quantity that will occur if it is assumed that the work is performed as planned. The invoice amount before change 175 is the invoice amount for each work if it is assumed that the work is performed as planned.

Note that since pre-change billing data 16 is generated before the work is performed, the change reason 171 column is left blank. Also, pre-change work month 172 is equal to work month 166. Pre-change unit price 173 and pre-change quantity 174 are equal to unit price 167 and quantity 168, respectively. And pre-change billing amount 175 is equal to billing amount 170.

(Generation of performance data)
6 is a diagram showing an example of the performance data 18. The performance data 18 is data that stores the amount actually charged per work period for each task included in the contract data 12. The performance data 18 stores a contracting party 181, an object 182, and a work month 183. The performance data 18 also stores an approval column 184, a contract number 185, a sales statement 186, a contracting party 187, an object 188, and a task 189. The performance data 18 also stores a fluctuation category 190, a fluctuation reason 191, a work month 192, a unit price 193, a quantity 194, a unit 195, and a billed amount 196.

Performance data 18 is generated for each object and each month of work. Contractor 181 corresponds to contractor 123 registered in contract data 12. Object 182 corresponds to object 124 registered in contract data 12. Work month 183 is the year and month related to the performance.

The performance data 18 is generated in units of sales detail lines 186. The approval column 184 indicates whether or not each sales detail line of the generated performance data 18 has been approved. The contract number 185 corresponds to the contract number 121 registered in the contract data 12. The sales detail line 186 corresponds to the sales detail line 128 registered in the contract data 12. The contracting party 187 corresponds to the contracting party 123 registered in the contract data 12. The property 188 corresponds to the property 124 registered in the contract data 12. The business 189 corresponds to the business 130 registered in the contract data 12.

The change category 190 is information indicating whether each sales detail line has changed from the detailed plan data 14. Specifically, a change category of "0" indicates that there has been no change from the detailed plan data 14. A change category of "1, 2, 3, ..." indicates that there has been a change from the detailed plan data 14.

The reason for change 191 stores the reason for the change from the detailed schedule data 14. The operator who creates the actual results data 18 inputs the reason for change 191 using the input device 112. In the example shown in FIG. 6, the reason for change 191 is blank in the fourth sales detail line. That is, "Elevator inspection" indicates that it was carried out as scheduled. Also, "Daily inspection" in the first sales detail line indicates that it was not carried out in part due to repair work. "Glass cleaning inspection" in the second sales detail line indicates that the work month was changed due to bad weather. The changed work month is registered in the work month 192 column described below. And "Guest room cleaning" in the third sales detail line indicates that the quantity (for 10 rooms) that has been "confirmed" will be recorded.

The work month 192 is the year and month when the work was performed. The performance data 18 shown in FIG. 6 is data showing the performance in June 2020, but if the work month changes (for example, glass inspection work), the changed work month input by the operator via the input device 112 is stored.

The unit price 193, quantity 194, and unit 195 correspond to the unit price 131, quantity 132, and unit 133 registered in the contract data 12, respectively. The billed amount 196 is the billed amount incurred for the relevant period for each task. Note that if any changes occur in the unit price 131, quantity 132, or billed amount 196, the operator inputs the changed values using the input device 112.

(Generating changed billing data)
7 is a diagram showing an example of changed billing data 20. The changed billing data 20 stores a billing number 201, a contract number 202, a sales statement 203, an industry type 204, a task 205, an operation month 206, a unit price 207, a quantity 208, a unit of measure 209, and a billing amount 210. The changed billing data 20 also stores a fluctuation category 211, a fluctuation reason 212, an operation month before the change 213, a unit price before the change 214, a quantity before the change 215, and a billing amount before the change 216.

The billing number 201 corresponds to the billing number 161 of the billing data 16 before the change. The contract number 202 corresponds to the contract number 121 registered in the contract data 12. The sales detail line 203 corresponds to the sales detail line 128 registered in the contract data 12. The industry 204 and the task 205 correspond to the industry 129 and the task 130, respectively, registered in the contract data 12. The work month 206 is the year and month in which the work related to the billing data to be created occurred. The unit price 207, the quantity 208, and the unit 209 correspond to the unit price 131, the quantity 132, and the unit 133, respectively, registered in the contract data 12. The billing amount 210 is the billing amount actually incurred for each task during the relevant period.

The fluctuation category 211 corresponds to the fluctuation category 190 registered in the performance data 18. The reason for fluctuation 212 corresponds to the reason for fluctuation 191 registered in the performance data 18. The work month before change 213 is the year and month when the work related to the billing data to be created was originally scheduled to occur. The unit price before change 214 and the quantity before change 215 indicate the unit price and quantity of each task that would occur if the work related to the billing data to be created was performed as planned. The billing amount before change 216 is the billing amount that would occur if the work related to the billing data to be created was performed as planned.

(Generating a variable input list)
8 is a diagram showing an example of the variable input list 22. The variable input list 22 is a table that, when a change occurs, extracts and outputs only the data that has changed by comparing the pre-change billing data 16 with the post-change billing data 20. Note that data related to items that have changed can be selected, for example, by extracting only items in which the reason for the change has been entered in the post-change billing data 20.

The comparison result display unit 102h generates the variable input list 22 by specifying the contracting party 221, the property 222, and the pre-change work month 223. By specifying the pre-change work month 223, the pre-change billing data 16 for the same work month can be referenced, allowing a comparison to be made before and after the change.

The variable input list 22 includes billing destination 224, contract number 225, task 226, property 227, previous work month 228, work month 229, plan 230, actual results 231, and reason for change 232.

Billing destination 224 corresponds to contract destination 123 registered in contract data 12. Contract number 225 corresponds to contract number 121 registered in contract data 12. Contract number 225 and task 226 correspond to contract number 121 and task 130, respectively, registered in contract data 12. For convenience, a branch number is assigned to contract number 121 in variable input list 22. Item 227 corresponds to item 124 registered in contract data 12. Pre-change work month 228 is the year and month specified in pre-change work month 223. Work month 229 is the year and month when the selected task was actually performed.

The plan 230 is information based on the pre-change billing data 16. The plan 230 further includes a pre-change quantity 230a, a pre-change unit price 230b, and a pre-change billing amount 230c. The pre-change quantity 230a corresponds to the pre-change quantity 174 registered in the pre-change billing data 16. The pre-change unit price 230b corresponds to the pre-change unit price 173 registered in the pre-change billing data 16. The pre-change billing amount 230c corresponds to the pre-change billing amount 175 registered in the pre-change billing data 16.

Actual results 231 are information based on the changed billing data 20. Actual results 231 further include quantity 231a, unit price 231b, billed amount 231c, and variable amount 231d. Quantity 231a corresponds to quantity 208 registered in changed billing data 20. Unit price 231b corresponds to unit price 207 registered in changed billing data 20. Billed amount 231c corresponds to billed amount 210 registered in changed billing data 20. Variable amount 231d is the difference between pre-change billing amount 230c and billed amount 231c.

The reason for change 232 corresponds to the reason for change 212 stored in the changed billing data 20.

Thus, according to this embodiment, the changed billing data creation unit 102f (change means) included in the control unit 102 of the business support device 100 refers to the contract data 12 to identify the contract contents linked to the specified contracting party and the property. The changed billing data creation unit 102f then extracts performance data 18 linked to the identified contract contents and the specified work period from the pre-change billing data 16, outputs the extracted performance data 18 to the output device 114 (screen), and if the performance data 18 is changed on the screen accompanied by input of a change reason, stores the input change reason in the changed billing data 20 and creates the changed billing data 20 by rewriting the performance data 18 to be changed that is stored in the pre-change billing data 16 to the changed performance data displayed on the screen. The comparison result display unit 102h (output control unit) of the control unit 102 refers to the contract data 12 to identify the contract contents linked to the specified contract partner and the property, extracts from the changed billing data 20 billing data that is linked to the identified contract contents, that the detailed schedule data 14 includes the specified work time, and that a change reason is registered, and outputs the extracted billing data in a form that allows a comparison of the planned and actual billing data. Therefore, since the pre-change billing data 16 stores the pre-change billing amount 175, the pre-change work month 172, and the work month 166 in which the work was actually performed, and the post-change billing data 20 stores the change reason 212, the variable input list 22 can be easily generated. This makes it possible to easily collect and analyze the causes of the difference when a difference occurs between the work results and the plan.

5. Modifications of the Mode for Carrying Out the Invention
The above-described embodiment can be modified into another embodiment. Fig. 9 is a diagram showing an example of the tally result 24 for each reason for change.

The tally result 24 is data showing the tally results of the plan and actual results for the specified tally period. The control unit 102 of the business support device 100 creates the tally result 24 in an tally result creation unit 102l not shown in FIG. 1. That is, the tally result creation unit 102l tally up the pre-change billing data and post-change billing data for each change reason for the selected tally period. The tally result creation unit 102l is an example of a tallying means in this disclosure.

The aggregation result 24 includes an aggregation period 241, a change category 242, a reason for change 243, a total billing amount before the change 244, a total billing amount after the change 245, and a total difference 246.

The aggregation period 241 is the period for which aggregation is performed, specified by the operator. The operator specifies the aggregation period 241 using the input device 112. The fluctuation category 242 corresponds to the fluctuation category 211 registered in the changed billing data 20. The fluctuation reason 243 corresponds to the fluctuation reason 212 registered in the changed billing data 20. The pre-change billing total 244 is the sum of the billing amounts 170 belonging to the same sales detail line 163 registered in the pre-change billing data 16 over the aggregation period 241. The post-change billing total 245 is the sum of the billing amounts 210 belonging to the same sales detail line 203 registered in the changed billing data 20 over the aggregation period 241. The difference total 246 is the value obtained by subtracting the pre-change billing total 244 from the post-change billing total 245.

In this way, according to this embodiment, the tally result creation unit 102l included in the control unit 102 of the business support device 100 tally up the pre-change billing data and post-change billing data for each change reason during the selected tally period. Therefore, the difference between the plan and the actual results can be easily tallied for each change reason.

6. 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, search conditions, and other parameters, 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 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the business support device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that includes 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 100 as necessary. That is, a computer program for giving 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.

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

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

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

The various data stored in the memory unit 106 are storage devices 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.

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

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

The business support device 100 according to the embodiment of the present invention can be particularly useful in companies that perform building maintenance and condominium maintenance, etc.

12 Contract data 14 Detailed schedule data 16 Pre-change billing data 18 Performance data 20 Post-change billing data 22 Variable input list 24 Aggregation results 100 Business support device
102 control unit
102a Contract data creation unit
102b Detailed schedule data creation section
102c Pre-change billing data creation unit
102d Performance data creation section
102e Change reason input section
102f Changed billing data creation unit (changing means)
102g Comparison request reception unit
102h Comparison result display unit (output control means)
102l tally result creation unit (tallying means)
104 Communication interface unit
106 Memory unit
106a Contract data file
106b Detailed schedule data file
106c Pre-change billing data file
106d Performance data file
106e Changed billing data file
108 Input/Output Interface Unit
112 Input device
114 Output device (screen)
200 In-house PCs
300 Network

Claims (4)

A business support device including a control unit,
Contract data that stores the details of each contract for property maintenance,
billing data for managing performance data related to billing for each task included in the contract data, the billing data storing, for each request, scheduled data to be executed based on the contract contents, and storing, for each request, a reason for change when the scheduled data is changed;
is accessible to
The control unit is
a change means for referring to the contract data to specify contract details linked to a specified contracting party and object, extracting from the billing data performance data linked to the specified contract details and a specified work period, outputting the extracted performance data on a screen, and, when a change to the performance data is made on the screen accompanied by inputting a reason for the change, storing the input reason for the change in the billing data and rewriting the performance data to be changed that is stored in the billing data with the changed performance data that is displayed on the screen;
an output control means for referring to the contract data to identify contract details linked to a specified contracting party and object, extracting from the billing data billing data that satisfies the conditions that the billing data is linked to the identified contract details, includes a work time specified in scheduled data, and has a change reason registered, and outputting the extracted billing data in a form that allows a comparison between scheduled and actual billing data;
To have
A business support device comprising: further comprising a counting means for counting the pre-change billing data and the post-change billing data for each of the fluctuation reasons during the selected counting period;
2. The business support device according to claim 1, A business support method executed by a business support device having a control unit,
The control unit:
Contract data that stores the details of each contract for property maintenance,
billing data for managing performance data related to billing for each task included in the contract data, the billing data storing, for each request, scheduled data to be executed based on the contract contents, and storing, for each request, a reason for change when the scheduled data is changed;
By accessing
a modification step of referring to the contract data to identify contract details linked to a specified contracting party and object, extracting from the billing data performance data linked to the identified contract details and the specified work period, outputting the extracted performance data on a screen, and, if a change to the performance data is made on the screen accompanied by inputting a reason for the change, storing the input reason for the change in the billing data and rewriting the performance data to be changed that is stored in the billing data with the changed performance data that is displayed on the screen;
an output control step of referring to the contract data to identify contract details linked to a specified contracting party and object, extracting from the billing data billing data that satisfies the conditions that the billing data is linked to the identified contract details, includes a work time specified in scheduled data, and has a change reason registered, and outputting the extracted billing data in a form that allows a comparison between scheduled and actual billing data;
containing,
A business support method comprising: A program executed by a business support device having a control unit,
The control unit:
Contract data that stores the details of each contract for property maintenance,
billing data for managing performance data related to billing for each task included in the contract data, the billing data storing, for each request, scheduled data to be executed based on the contract contents, and storing, for each request, a reason for change when the scheduled data is changed;
By giving access to
a modification step of referring to the contract data to identify contract details linked to a specified contracting party and object, extracting from the billing data performance data linked to the identified contract details and the specified work period, outputting the extracted performance data on a screen, and, if a change to the performance data is made on the screen accompanied by inputting a reason for the change, storing the input reason for the change in the billing data and rewriting the performance data to be changed that is stored in the billing data with the changed performance data that is displayed on the screen;
an output control step of referring to the contract data to identify contract details linked to a specified contracting party and object, extracting from the billing data billing data that satisfies the conditions that the billing data is linked to the identified contract details, includes a work time specified in scheduled data, and has a change reason registered, and outputting the extracted billing data in a form that allows a comparison between scheduled and actual billing data;
To carry out the
A program characterized by.

Images