Schedule data generation apparatus, schedule data generation method, and schedule data generation program

Abstract

To provide a schedule data generation apparatus, a schedule data generation method, and a schedule data generation program that improve efficiency of operations relating to calculation of a usage end date and monthly charges in a business operator.SOLUTION: A schedule data generation method includes: (1) calculating a usage end date of a contract target for each order acceptance number and each contract detail number on the basis of a contract period managed in contract detail data and work completion data, and registering, for each order acceptance number and each contract detail number, the usage end date and a usage start date managed in the work completion data into the contract detail data; and (2) executing, for each order acceptance number and each contract detail number, "identification of a usage month," "identification of a sales month on the basis of a deviation classification between the usage month and the sales month," and "calculation of a scheduled sales amount for each sales month in accordance with a daily denominator classification, an initial-month calculation classification, and a final-month calculation classification" on the basis of the contract detail data in which the usage start date and the usage end date have been registered, and generating scheduled sales data in which the calculated scheduled sales amounts are registered for each order acceptance number, each contract detail number, each usage month, and each sales month.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a schedule data generating device, a schedule data generating method, and a schedule data generating program. [Background technology]

[0002] Patent Document 1 discloses a fixed-term contract sales management device that enables sales management up to the end of a contract period by simply inputting the information from order receipt to sales recognition within the contract period of a fixed-term contract product (service) once, thereby improving the operational efficiency of such management. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-250447 Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, when a business operator (such as a line operator, rental operator, or leasing operator; hereinafter simply referred to as "business operator") that provides the subject matter of the contract to a customer enters into a contract with a customer that permits the use (meaning the utilization or use) of a product or service for a certain period of time, and the start date of utilization of the subject matter of the contract is not determined at the time the contract is concluded with the customer, but is determined when the customer is able to utilize the subject matter of the contract (for example, when the work to make the subject matter of the contract available for use is completed), the business operator will calculate the end date of utilization and each month's fees (especially the fees for the first and last months of the contract period) once the start date of utilization has been determined. However, until now, these calculations have been done manually, leaving room for improvement in terms of business efficiency.

[0005] The present invention has been made in consideration of the above, and aims to provide a schedule data generation device, a schedule data generation method, and a schedule data generation program that can streamline the business operator's work related to calculating the end date of use and each month's fees (particularly the fees for the first and last months of the contract period (particularly the expected sales amount)). [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the schedule data generation device of the present invention is capable of accessing contract data for managing information on contracts that license the use of goods or services for a certain period of time, by contract and by contract object, in which calculation rules for calculating the monthly contract amount, contract period, and each expected sales amount for the first and last month of the contract period, and specific information for identifying the month of use and the month of sales, as well as start date data for managing the start date of use of the contract object, by contract and by contract object, which is not determined at the time of concluding a contract with a customer but is determined when the customer becomes able to use the contract object, and the contract period and the schedule data generation device of the present invention are capable of accessing the following: The system is characterized by comprising an end date calculation unit that calculates the end date of use of the contract object for each contract and for each contract object based on the start date data, and registers the calculated end date of use and the start date of use managed by the start date data in the contract data for each contract and for each contract object; and a sales forecast generation unit that (1) based on the contract data in which the start date and end date of use have been registered, (A) identifies the month of use, (B) identifies the month of use and the sales month based on the identified information, and (C) calculates the projected sales amount for each sales month in accordance with calculation rules, for each contract and for each contract object, and (2) generates projected sales data in which the calculated projected sales amount is registered for each contract, for each contract object, for each month of use, and for each sales month.

[0007] In addition, the contract data may further include registered calculation rules for calculating the estimated billing amounts for the first and last months of the contract period and specific information for identifying the billing month from the month of use, and the scheduled data generation device of the present invention may further include a billing schedule generation unit that (1) performs, based on the contract data in which the start date and end date of use are registered, (A) identifies the month of use, (B) identifies the billing month based on the month of use and the specific information, and (C) calculates the estimated billing amount for each billing month in accordance with the calculation rules, for each contract and contract object, and (2) generates scheduled billing data in which the calculated estimated billing amounts are registered for each contract, contract object, month of use, and billing month.

[0008] The calculation rule may also correspond to any of the following calculation criteria: pro rata, free, a certain reduced amount, or full amount.

[0009] The calculation rule for the daily rate may include a condition regarding the denominator when calculating the daily rate.

[0010] The calculation rule may be defined by a combination of master setting values.

[0011] In addition, the calculation rule may be defined as a combination of a master setting value that defines the calculation criteria for the first month, a master setting value that defines the calculation criteria for the last month, and a master setting value that defines the conditions related to the denominator.

[0012] The contracted item may also be provided by a line provider, rental provider, or leasing provider.

[0013] Furthermore, the scheduled data generation method of the present invention is a method of generating scheduled data by a control unit of an information processing device that can access contract data for managing information on contracts that license the use of goods or services for a certain period of time by contract and by contract object, in which a monthly contract amount, a contract period, calculation rules for calculating the expected sales amount for each of the first and last months of the contract period, and specific information for identifying the month of use from the month of sales are registered, and start date data for managing the start date of use of the contract object by contract and by contract object, which is not determined at the time of concluding a contract with a customer but is determined when the customer becomes able to use the contract object, based on the contract period and the start date data managed in the contract data. The method is characterized by executing an end date calculation step in which the utilization end date of the contract object is calculated for each contract and for each contract object, and the calculated utilization end date and the utilization start date managed in the start date data are registered in the contract data for each contract and for each contract object; and (1) based on the contract data in which the utilization start date and utilization end date have been registered, (A) identify the utilization month, (B) identify the sales month based on the utilization month and the specified information, and (C) calculate the estimated sales amount for each sales month in accordance with the calculation rules, for each contract and for each contract object, and (2) generate estimated sales data in which the calculated estimated sales amount is registered for each contract, for each contract object, for each utilization month, and for each sales month.

[0014] The scheduled data generation program of the present invention is contract data for managing information on contracts that license the use of goods or services for a certain period of time by contract and by contract object, in which a monthly contract amount, a contract period, calculation rules for calculating the estimated sales amount for each of the first and last months of the contract period, and specific information for identifying the month of use and the month of sales are registered, and start date data for managing the start date of use of the contract object by contract and by contract object, which is not determined at the time of concluding a contract with a customer but is determined when the customer becomes able to use the contract object, and the contract period and start date data managed in the contract data are stored in a control unit of an information processing device that can access the following: and (2) a sales forecast generation step that (1) based on the contract data in which the start date and end date of use have been registered, (A) identifies the month of use, (B) identifies the month of use and the sales month based on the specified information, and (C) calculates the estimated sales amount for each sales month in accordance with the calculation rules, and (2) generates estimated sales data in which the calculated estimated sales amount is registered by contract, by contract object, by month of use, and by sales month. [Effects of the Invention]

[0015] The present invention has the effect of improving the efficiency of operations related to the calculation of the end date of use and the fees for each month (particularly the fees for the first and last months of the contract period (particularly the expected sales amount)) at the business operator. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a task assistance device 100. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing an example of information stored in the first month calculation division master 106a, the last month calculation division master 106b, and the daily proration denominator division master 106c. [Figure 3]FIG. 3 is a diagram showing an example of the correspondence between the business flow assumed in this embodiment and the system flow using the business support device 100. In FIG. [Figure 4] FIG. 4 is a diagram showing an example of the contract input process and the work completion input process. [Figure 5] FIG. 5 is a diagram showing an example of approval processing including a sales schedule generation processing and a billing schedule generation processing. [Figure 6] FIG. 6 is a diagram showing an example of the sales input process and the billing input process. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, preferred embodiments of a schedule data generating device, a schedule data generating method, and a schedule data generating program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these preferred embodiments.

[0018] [1. Configuration and Processing] An example of the configuration and processing of a task assistance device 100 according to this embodiment (including a schedule data generating device according to the present invention) will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of the task assistance device 100.

[0019] The business support device 100 is used by a business operator (such as a line operator, rental operator, or leasing operator) that concludes a contract with a customer to license the use (meaning utilization or use, hereinafter referred to as "use") of a product or service (hereinafter referred to as "product") for a certain period of time, where the start date of use of the contracted subject is not determined at the time the contract is concluded with the customer, but is determined when the customer is able to use the contracted subject (for example, when the work to make the contracted subject usable is completed). In this embodiment, "use" has the same meaning as "use." The start date of use is the contract start date.

[0020] The business support device 100 is constructed based on a commercially available desktop personal computer. Note that the information processing device 100 is not limited to one constructed based on a stationary information processing device such as a desktop personal computer, but may also be one constructed based on 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.

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

[0022] The communication interface unit 104 communicably 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 connecting the business support device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

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

[0024] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that cooperate with an operating system (OS) to issue commands to a central processing unit (CPU) to perform various processes. The storage unit 106 may be, for example, a memory device such as a random access memory (RAM) or a read-only memory (ROM), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The data stored in the storage unit 106 may be stored in the server 200, for example.

[0025] The memory unit 106 stores a first month calculation category master 106a (see Figure 2), a final month calculation category master 106b (see Figure 2), a daily denominator category master 106c (see Figure 2), contract detail data 106d (see Figures 4 and 5), work completion data 106e (see Figure 4), planned sales data 106f (see Figure 5), planned billing data 106g (see Figure 5), sales data 106h (see Figure 6), and billing data 106i (see Figure 6).

[0026] The key item of the first month calculation category master 106a is the first month calculation category code. The first month calculation category name "Daily Pro-rata → First Month Free, Added Next Month" means that the fee for the first month of the contract period is free, and the fee that would have been charged on a daily basis in the first month is added in the month following the first month. The first month calculation category name "Full Amount → First Month Free, Added Next Month" means that the fee for the first month of the contract period is free, and the fee that would have been charged in full in the first month is added in the month following the first month. The contract period is the contract period determined for each product, and may be automatically renewed unless the customer requests cancellation.

[0027] Furthermore, the key item of the final month calculation category master 106b is the final month calculation category code. The final month calculation category name "Daily Pro-rata → Free in Final Month, Added the Next Month" means that the fee for the final month of the contract period is free, and the fee that would have been charged on a daily basis in the final month is added to the month following the final month. The final month calculation category name "Full Amount → Free in Final Month, Added the Next Month" means that the fee for the final month of the contract period is free, and the fee that would have been charged in full in the final month is added to the month following the final month.

[0028] The key item of the daily denominator category master 106c is the daily denominator category code. The daily denominator category name "Calendar Day" means that the number of days in a calendar month (specifically, 28, 29, 30, or 31) is used as the denominator for the daily calculation.

[0029] Furthermore, the key items of the contract specification data 106d are the order number and the contract specification number. The contract specification data 106d corresponds to the contract data of the present invention. The sales month deviation category "current month" means that the sales month is the same month as the month of use. The sales month deviation category "next month" means that the sales month is the month following the month of use.

[0030] The key items of the work completion data 106e are the order number and the contract specification number. The work completion data 106e corresponds to the start date data of the present invention.

[0031] The key items of the sales forecast data 106f are the order number and the contract specification number. The sales forecast data 106f corresponds to the sales forecast data of the present invention.

[0032] The key items of the billing schedule data 106g are the order number and the contract specification number. The billing schedule data 106g corresponds to the billing schedule data of the present invention.

[0033] The key items of the sales data 106h are the sales number and the row number.

[0034] The key items of the billing data 106i are the billing number and the line number.

[0035] 1, 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.

[0036] In terms of functional concept, the control unit 102 includes a contract input unit 102a, a work completion input unit 102b, an approval unit 102c (including the end date calculation unit, sales forecast generation unit, and billing schedule generation unit of the present invention), a sales input unit 102d, and a billing input unit 102e.

[0037] Typically, the processing units included in the control unit 102 are used in the order shown in the system flow shown in FIG. 3, which corresponds to the business flow.

[0038] The operation of the contract input unit 102a will be described with reference to Figure 4. The contract input unit 102a has an operator input information determined in the contract and registers it in the contract specification data 106d. When the contract is concluded, the operator inputs the product name, contract period, sales month deviation category, billing month deviation category, contract amount, prorated denominator category, first month calculation category, and last month calculation category via a specified input screen (not shown), and instructs registration of the information. When this instruction is given, the contract input unit 102a assigns an order number and contract specification number and registers the information in the contract specification data 106d (see (1) in Figure 4). Note that when the contract is concluded, the usage start date has not been determined, so there is no need to input the usage start date and usage end date.

[0039] The operation of the work completion input unit 102b will be described with reference to FIG. 4. The work completion input unit 102b has an operator input the usage start date, and registers it in the work completion data 106e. When the business receives a report informing the operator of the start of product usage from the worker who was in charge of the work of making the product available, the operator specifies at least the order number via a predetermined input screen (not shown), enters the date of receipt as the usage start date, and instructs the registration of the information. When this instruction is given, the work completion input unit 102b registers the information in the work completion data 106e (see (2) in FIG. 4). Note that although an example of manually registering information has been shown, information may also be registered by batch processing or automatic import linkage.

[0040] The operation of the approval unit 102c will be described with reference to FIG. 5. The approval unit 102c executes a workflow approval process to have a superior confirm and approve that the use start date registered in the work completion data 106e is the same as the date the report was received. The operator (superior) designates at least the order number via a predetermined approval screen (not shown). Once this designation is made, the approval unit 102c displays the use start date registered in the work completion data 106e on the approval screen. The operator (superior) visually checks whether the displayed use start date is different from the date the report was received, and if there is no difference, issues an approval instruction.

[0041] When this instruction is given, the approval unit 102c calculates the end date of use of the product for each order number and contract specification number based on the contract period and work completion data 106e managed in the contract specification data 106d, and registers the calculated end date of use and the start date of use managed in the work completion data 106e in the contract specification data 106d for each order number and contract specification number (see Figure 5). Please refer to Figure 5 for details on how to calculate the end date of use.

[0042] Then, based on the contract detail data 106d (record) in which the usage start date and usage end date have been registered, the approval unit 102c performs the following operations for each order number and contract detail number: "identification of the month of use," "identification of the month of sales based on the discrepancy category between the month of use and the month of sales," and "calculation of the estimated sales amount for each sales month according to the daily denominator category, first month calculation category, and last month calculation category," and generates estimated sales data 106f (record) in which the calculated estimated sales amounts are registered for each order number, contract detail number, month of use, and month of sales (see Figure 5).

[0043] Furthermore, based on the contract detail data 106d (records) in which the usage start date and usage end date have been registered, the approval unit 102c performs the following operations for each order number and contract detail number: "identification of the month of use," "identification of the billing month based on the deviation category between the month of use and the billing month," and "calculation of the estimated billing amount for each billing month according to the daily denominator category, first month calculation category, and last month calculation category," and generates estimated billing data 106g (records) in which the calculated estimated billing amounts are registered for each order number, contract detail number, month of use, and billing month (see Figure 5).

[0044] The operation of the sales input unit 102d will be described with reference to Figure 6. The sales input unit 102d extracts details to be processed (details for the target year and month) from the projected sales data 106f to generate sales data 106h. The target year and month may be specified by an operator via a predetermined input screen (not shown). The sales input unit 102d may also generate the sales data 106h by batch processing or automatic processing using monthly batches.

[0045] The operation of the billing input unit 102e will be described with reference to Fig. 6. The billing input unit 102e extracts the details to be processed (details for the target year and month) from the billing schedule data 106g to generate billing data 106i. The target year and month may be specified by an operator via a predetermined input screen (not shown). The billing input unit 102e may also generate the billing data 106i by batch processing or automatic processing using monthly batches.

[0046] As described above, according to this embodiment, the management of sales amounts and invoice amounts has been automated, making it possible to prevent incorrect invoicing due to calculation errors. Furthermore, according to this embodiment, it has become possible to automatically process product provision to customers, contract management, amount calculations, and sales and invoices in accordance with complex contract conditions that also involve contracts with suppliers (workers (companies) in charge of making products available).

[0047] [2. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

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

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

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

[0051] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

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

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

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

[0055] This computer program may 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.

[0056] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or 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.

[0057] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. 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.

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

[0059] 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 installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.

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

[0061] The present invention is particularly useful for businesses (such as line operators, rental businesses, or leasing businesses) that enter into contracts with customers to license the use of goods or services for a certain period of time, in which the start date of use of the contract subject matter is not determined at the time the contract is concluded with the customer, but is determined when the customer becomes able to use the contract subject matter, and that provide the contract subject matter to the customer. [Explanation of symbols]

[0062] 100 Business support equipment 102 Control section 102a Contract input section 102b Work completion input section 102c Approval Department 102d Sales Input Section 102e Billing entry section 104 Communication interface unit 106 Storage section 106a First month calculation category master 106b Final Month Calculation Category Master 106c Daily Proportion Denominator Master 106d Contract details data 106e Work completion data 106f Sales forecast data 106g Billing schedule data 106h Sales Data 106i Billing Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. The contract data is for managing information about contracts that license the use of goods or services for a certain period of time, by contract and by contract object, and includes the calculation rules for calculating the monthly contract amount, contract period, and estimated sales amount for each of the first and last months of the contract period, as well as specific information for identifying the month of use and the month of sales; and start date data is available for managing the start date of use of the contract object, by contract and by contract object, which is not determined at the time of concluding a contract with a customer but is determined when the customer becomes able to use the contract object; an end date calculation unit that calculates the end date of use of the contract object for each contract and for each contract object based on the contract period and the start date data managed in the contract data, and registers the calculated end date of use and the start date of use managed in the start date data in the contract data for each contract and for each contract object; (1) a sales forecast generation unit that, based on the contract data in which the start date and end date of use have been registered, (A) identifies the month of use, (B) identifies the month of sales based on the month of use and the specified information, and (C) calculates the estimated sales amount for each sales month in accordance with the calculation rules, for each contract and contract object; and (2) generates estimated sales data in which the calculated estimated sales amount is registered for each contract, contract object, month of use, and month of sales. To have A schedule data generating device comprising:

2. The contract data further includes calculation rules for calculating the estimated billing amount for each of the first and last months of the contract period and specific information for identifying the billing month from the month of use, (1) Based on the contract data in which the use start date and use end date have been registered, (A) the use month is identified, (B) the billing month is identified based on the use month and the identification information, and (C) the estimated billing amount for each billing month is calculated in accordance with the calculation rules, for each contract and contract object; and (2) a billing schedule generation unit is further provided which generates billing schedule data in which the calculated estimated billing amount is registered for each contract, contract object, use month, and billing month.

2. The schedule data generating device according to claim 1, wherein:

3. The calculation rule corresponds to one of the calculation standards of daily rate, free, a certain reduced amount, or full amount; 3. The schedule data generating device according to claim 1, wherein:

4. The calculation rule corresponding to the daily rate includes a condition regarding the denominator when calculating the daily rate; 4. The schedule data generating device according to claim 3, wherein:

5. The calculation rule is defined by a combination of master setting values; 5. The schedule data generating device according to claim 4, wherein:

6. The calculation rule is defined by a combination of a master setting value that defines the calculation standard for the first month, a master setting value that defines the calculation standard for the last month, and a master setting value that defines the conditions related to the denominator; 6. The schedule data generating device according to claim 5,

7. The subject of the contract is provided by a line operator, rental operator or leasing operator; 7. The schedule data generating device according to claim 6, wherein:

8. a control unit of an information processing device that can access: contract data for managing information about contracts that license the use of goods or services for a certain period of time by contract and by contract object, in which calculation rules for calculating the monthly contract amount, contract period, and estimated sales amounts for the first and last months of the contract period, and specific information for identifying the month of sales from the month of use, and start date data for managing the start date of use of the contract object by contract and by contract object, which is not determined at the time of concluding a contract with a customer but is determined when the customer becomes able to use the contract object; an end date calculation step of calculating the end date of use of the contract object for each contract and for each contract object based on the contract period and the start date data managed in the contract data, and registering the calculated end date of use and the start date of use managed in the start date data in the contract data for each contract and for each contract object; (1) based on the contract data in which the use start date and use end date have been registered, (A) identify the use month, (B) identify the sales month based on the use month and the specified information, and (C) calculate the expected sales amount for each sales month in accordance with the calculation rules, for each contract and contract object; (2) a sales forecast generation step in which the calculated expected sales amount is generated and registered for each contract, contract object, use month, and sales month; To carry out A method for generating scheduled data, comprising:

9. a control unit of an information processing device that can access: contract data for managing information about contracts that license the use of goods or services for a certain period of time by contract and by contract object, in which calculation rules for calculating the monthly contract amount, contract period, and estimated sales amounts for the first and last months of the contract period, and specific information for identifying the month of sales from the month of use, are registered; and start date data for managing the start date of use of the contract object by contract and by contract object, which is not determined at the time of concluding a contract with a customer but is determined when the customer becomes able to use the contract object; an end date calculation step of calculating the end date of use of the contract object for each contract and for each contract object based on the contract period and the start date data managed in the contract data, and registering the calculated end date of use and the start date of use managed in the start date data in the contract data for each contract and for each contract object; (1) based on the contract data in which the use start date and use end date have been registered, (A) identify the use month, (B) identify the sales month based on the use month and the specified information, and (C) calculate the expected sales amount for each sales month in accordance with the calculation rules, for each contract and contract object; (2) a sales forecast generation step in which the calculated expected sales amount is generated and registered for each contract, contract object, use month, and sales month; A schedule data generation program for executing the above.

Images