JP7047436B2 - Information processing systems and programs - Google Patents

Description

The present invention relates to information processing systems and programs.

In Patent Document 1, when the determination result in the device specification determination means is an inappropriate device specification, the device specification change instruction means can give an instruction to change the device specification so that the device specification becomes appropriate. Discloses that the proposal is recreated based on the device specifications instructed by the device specification change instruction means.
In Patent Document 2, information on the operation history of each image processing device already in operation by the customer is aggregated and analyzed, and an alert is generated by applying a predetermined condition to the analysis result, and the alert is generated. An information processing system that automatically generates documents to be presented to a customer based on the above is disclosed.

Japanese Unexamined Patent Publication No. 2006-323555 Japanese Unexamined Patent Publication No. 2015-135663

In an information processing system, for example, a product proposal document relating to a product proposal may be generated. The sales staff may use this product proposal document to carry out sales activities related to selling the product to the customer.
Here, for example, if the function of the proposed product is not useful in solving the business problem of the customer, it is difficult to sell this product to the customer even if the sales activity is performed using the product proposal document of this product. .. In such a case, if the generation of this product proposal document is not restricted, a proposal that does not lead to the purchase of the product may be made.

An object of the present invention is to suppress the creation of a product proposal document that does not lead to the purchase of a product, as compared with a configuration that does not limit the generation of a product proposal document relating to a product whose function is not useful in solving a customer's business problem. It is in.

The invention according to claim 1 is the product by instructing the user to generate a product proposal document for the selected product among the products to be proposed in order to link to the purchase of the product to the customer to be instructed. When the means for requesting the generation of the proposal document, the generation means for generating the product proposal document for which the user has instructed to generate the product proposal document, and the request for generation of the product proposal document are received, the instruction target customer receives the instruction target customer. The generation means includes a determination means for determining whether or not the usefulness condition regarding the usefulness of the function of the selected product is satisfied, and the generation means determines by the determination means that the instruction target customer does not satisfy the usefulness condition. If so, it is an information processing system characterized by limiting the generation of the product proposal document.
The information processing system according to claim 1, further comprising a display means for displaying cause information regarding the restricted cause when the generation of the product proposal document is restricted by the generation means. Is.
The invention according to claim 3 is the information processing system according to claim 2, wherein the cause information is information related to evaluation of a function provided in the equipment used by the referent customer.
According to the fourth aspect of the present invention, even when the generation means determines that the referent customer satisfies the useful condition based on the history of sales activities related to the product to the referent customer. The information processing system according to claim 1, wherein the generation of the product proposal document is restricted.
In the invention according to claim 5, when it is determined that the instruction target customer does not satisfy the useful condition, the generation means gives an instruction to generate the product proposal document after restricting the generation of the product proposal document. On the other hand, if it is determined that the customer subject to the instruction satisfies the useful condition and the generation of the product proposal document is restricted based on the history of the sales activity, the product proposal document after the restriction is restricted. The information processing system according to claim 4, wherein the product proposal document is generated by receiving the generation instruction of the product.
In the invention according to claim 6, the determination means determines whether or not the product satisfies the specific condition of the referent customer regarding the introduction of the product, and the generation means causes the product to satisfy the specific condition. The information processing system according to claim 1, wherein if it is determined that the product is not satisfied, the generation of the product proposal document is restricted even if it is determined that the referent customer satisfies the useful condition. Is.
In the invention according to claim 7, when it is determined that the instruction target customer does not satisfy the useful condition, the generation means gives an instruction to generate the product proposal document after restricting the generation of the product proposal document. On the other hand, if it is determined that the instruction target customer satisfies the useful condition and the product does not satisfy the specific condition, the product after restricting the generation of the product proposal document is not accepted. The information processing system according to claim 6, wherein the product proposal document is generated by receiving an instruction to generate the proposal document.
The invention according to claim 1, wherein the useful condition is determined based on a comparison between the function of the product and the function provided in the equipment used by the referent customer. It is an information processing system.
The invention according to claim 9 further includes an evaluation means for evaluating whether or not the equipment has a problem for each field to which the function provided in the equipment used by the instruction target customer belongs, and the determination means. When the evaluation means evaluates that the equipment has the problem in the field to which the function of the product belongs, it is determined that the customer to be instructed satisfies the useful condition, and the equipment has the problem in the field. The information processing system according to claim 8, wherein when it is evaluated that the customer does not have the above, it is determined that the instruction target customer does not satisfy the useful condition.
The invention according to claim 10 is obtained by instructing a computer to generate a product proposal document for a product selected from among the products that the user intends to propose in order to link to the purchase of the product to the customer to be instructed. , The function of requesting the generation of the product proposal document, the function of generating the product proposal document for which the user has instructed to generate the product proposal document, and the function of generating the product proposal document, and the instruction target when the user receives the request for generation of the product proposal document. The function of determining whether or not the customer satisfies the usefulness condition regarding the usefulness of the function of the selected product , and the generation of the product proposal document when it is determined that the instruction target customer does not satisfy the usefulness condition. It is a program to realize the function to limit.

According to the invention of claim 1 , is it useful in solving the business problem of the customer with respect to the function of the product to be proposed to the customer before the user gives an instruction to generate the product proposal document? Compared to the configuration for determining whether or not a product is used, it is possible to secure the product options to be proposed to the customer and suppress the creation of a product proposal document that does not lead to the purchase of the product.
According to the second aspect of the present invention, it becomes easier for the user to search for a product for which the generation of the product proposal document is not restricted, as compared with the case where the information regarding the cause of the restriction for the generation of the product proposal document is not displayed.
According to the third aspect of the present invention, when the generation of the product proposal document is restricted, the function regarding the equipment used by the referent customer is compared with the case where the information regarding the function provided by the equipment used by the referent customer is not displayed. It makes it easier for users to find products that are useful for.
According to the invention of claim 4, when the referent customer satisfies the useful condition, the product proposal document that does not lead to the purchase of the product is created as compared with the case where the product proposal document is generated regardless of the history of sales activities. Can be suppressed.
According to the invention of claim 5, the creation of the product proposal document that leads to the purchase of the product is compared with the case where the generation instruction of the product proposal document is not accepted after the generation of the product proposal document is restricted based on the history of sales activities. Is suppressed.
According to the invention of claim 6, when the referent customer satisfies the useful condition, the product proposal document is generated regardless of whether the product satisfies the condition of the referent customer regarding the introduction of the product, as compared with the case where the product proposal document is generated. It is possible to suppress the creation of product proposal documents that do not lead to the purchase of products.
According to the invention of claim 7, the purchase of the product is different from the case where the generation instruction of the product proposal document is not accepted after the generation of the product proposal document is restricted because it is determined that the product does not satisfy the unique conditions. Restriction on the creation of linked product proposal documents is suppressed.
According to the invention of claim 8, the contents of useful conditions can be changed according to the referent customer.
According to the invention of claim 9, as compared with the configuration which does not limit the generation of the product proposal document even though the function provided in the equipment of the referent customer does not have a problem in all the fields to which the function of the product belongs. , It is possible to suppress the creation of product proposal documents that do not lead to the purchase of products.
According to the invention of claim 10 , is it useful in solving the business problem of the customer with respect to the function of the product to be proposed to the customer before the user gives an instruction to generate the product proposal document? Compared to the configuration for determining whether or not a product is used, it is possible to secure the product options to be proposed to the customer and suppress the creation of a product proposal document that does not lead to the purchase of the product.

It is a figure which shows the whole structure of the information processing system by this embodiment. It is a figure which shows the functional structure of the management server. It is a figure which shows the functional structure of a client terminal. It is a figure which shows the hardware configuration example of the computer used as a management server and a client terminal. It is a figure which showed the configuration example of the product information management table. It is a figure which showed the configuration example of the customer information management table. It is a figure which showed the reception screen for accepting the generation instruction of the product proposal document by a user. It is a flowchart of a determination process. It is a figure which showed the non-generation screen which is displayed when the product proposal document is not generated. It is a figure which showed the reception screen as a modification of the example which restricts the generation of a product proposal document. It is a figure which showed the configuration example of the sales activity history management table. It is a flowchart of the determination process in 2nd Embodiment. It is a figure which showed the generation restriction screen which is displayed when the referent product has been proposed to the referent customer. It is a figure which showed the structural example of the product information management table in 3rd Embodiment. It is a figure which showed the configuration example of the proposal condition management table. It is a flowchart of the determination process in 3rd Embodiment. It is a figure which showed the generation restriction screen which is displayed when the referent product does not satisfy a proposal condition.

<First Embodiment>
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 is a diagram showing an overall configuration of an information processing system 100 according to the present embodiment. The information processing system 100 of the present embodiment includes a management server 10, a client terminal 20 used for a user to access the management server 10, and a customer server 30 used for a customer to access the management server 10. .. The management server 10 and the client terminal 20, and the management server 10 and the customer server 30 are connected to each other via the network 40.

The management server 10 is a server that manages customer information about a customer held by a user, product information about a product that the user wants to sell to the customer, and the like. The management server 10 generates a product proposal document using customer information and product information. A product proposal document is a document used to propose a purchase of a product to a customer. The product proposal document contains a description of the product that the customer is offered to purchase. Further, as the product proposal document, for example, a data file is used. The management server 10 generates a product proposal document in response to a request from the client terminal 20, and transmits the product proposal document to the client terminal 20.
The management server 10 is realized by, for example, a computer. The management server 10 may be configured by a single computer or may be realized by distributed processing by a plurality of computers.

The client terminal 20 connects to the management server 10 via the network 40, requests the management server 10 to generate a product proposal document (generation request), and acquires the product proposal document generated by the management server 10. It is an information processing device. The client terminal 20 has a display means for displaying the acquired product proposal document.
The client terminal 20 is realized by, for example, a computer, a tablet-type information terminal, or another information processing device.

The customer server 30 is a server that collects and manages information related to the attributes of equipment owned by the customer and information generated by the customer using an information processing device. Equipment includes hardware and software equipment. In addition, the attributes of the equipment include the functions provided in the equipment. Further, the customer server 30 has a function of connecting to the management server 10 via the network 40 and transmitting information managed by the customer server 30 to the management server 10. The information transmitted from the customer server 30 is associated with the information that identifies the customer and is managed by the management server 10.
The customer server 30 is realized by, for example, a computer.

In the present embodiment, the software installed in the information processing device used by the customer generates information about the attributes of the equipment owned by the customer from the information processing device to the customer server 30, and the customer uses the information processing device. Information is sent.

The network 40 is an information communication network that is responsible for communication between the management server 10 and the client terminal 20 and between the management server 10 and the customer server 30. The type of the network 40 is not particularly limited as long as it can transmit and receive data, and may be, for example, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or the like. The communication line used for data communication may be wired or wireless. Further, each device may be connected via a plurality of networks or communication lines.

In the present embodiment, a process of determining whether or not to generate a product proposal document related to the product to be compared based on the comparison between the function provided in the equipment possessed by the customer and the function of the product (hereinafter, determination process). ) Is performed. Then, as a result of the comparison, if it is determined that the function of the product to be compared is not useful in solving the business problem of the customer, the generation of the product proposal document related to this product is restricted. The content of the determination process will be described in detail later.

<Functional configuration of management server>
Next, the functional configuration of the management server 10 will be described. FIG. 2 is a diagram showing a functional configuration of the management server 10.
As shown in FIG. 2, the management server 10 includes a customer information database (DB) 11 and a product information database (DB) 12. Further, the management server 10 includes a transmission / reception unit 13, a determination unit 14, and a generation unit 15.

The customer information DB 11 is a database that holds customer information. The customer information includes the customer name, the attributes of the equipment owned by the customer, and the like.
The product information DB 12 is a database that holds product information of products. Goods include not only goods but also software and services. Further, the product information includes a product name, product attributes, and the like. Product attributes include product type, product selling price, and product function.

The transmission / reception unit 13 is a communication means for transmitting / receiving data to / from an external device. The transmission / reception unit 13 receives a product proposal document generation request from the client terminal 20. Further, the transmission / reception unit 13 transmits a product proposal document and customer information to the client terminal 20. Further, the transmission / reception unit 13 receives the information transmitted from the customer server 30.

The determination unit 14 is a determination means for determining whether or not the customer satisfies the useful condition. The useful condition is a condition used to determine whether or not the function of the product is useful with respect to the business problem of the customer. The useful condition includes a condition used for determining whether or not the function of the product is useful with respect to the equipment owned by the customer. The determination unit 14 compares the function of the product with the function provided in the equipment of the customer, and if the product has a function lacking in the equipment of the customer, the customer satisfies the useful condition regarding the product. Is determined. Further, when the product does not have the function lacking in the customer's equipment, the determination unit 14 determines that the customer does not satisfy the useful condition for the product.

The generation unit 15 is a generation means for generating a product proposal document in response to an instruction from a user who uses the client terminal 20. The user's instruction includes an operation performed by the user on the client terminal 20 in order to generate a product proposal document. When the determination unit 14 determines that the customer satisfies the useful condition for the product, the generation unit 15 generates a product proposal document for the product related to the useful condition. On the other hand, when the determination unit 14 determines that the customer does not satisfy the useful condition regarding the product, the generation unit 15 limits the generation of the product proposal document for the product related to this useful condition. The user is regarded as a user who uses the client terminal.

<Functional configuration of client terminal>
FIG. 3 is a diagram showing a functional configuration of the client terminal 20 of the present embodiment. The client terminal 20 includes a transmission / reception unit 21, an acquisition unit 22, a display unit 23, and an input reception unit 24.
The transmission / reception unit 21 is a communication means for transmitting / receiving data to / from an external device. The transmission / reception unit 21 transmits a product proposal document generation request to the management server 10. Further, the transmission / reception unit 21 receives the product proposal document and the customer information from the management server 10.

The acquisition unit 22 is an acquisition means for acquiring user identification information. When the user inputs the identification information into the client terminal 20 and logs in, the acquisition unit 22 acquires the identification information and authenticates the user based on the acquired identification information.
As the input method of the identification information, for example, the identification information can be read by holding an ID (Identification) card in which different identification information is recorded for each user over an ID card reader (not shown), or registered for each user. It is possible to apply a method in which the user himself / herself inputs the identified identification number and password on the display screen.

The display unit 23 is a display means for displaying a list of products to be sold to customers. In addition, the display unit 23 displays the product proposal document and customer information generated by the generation unit 15 of the management server 10.
The input receiving unit 24 is a receiving means for receiving an operation performed by the user. The input receiving unit 24 accepts a user's operation for requesting the generation of a product proposal document.

<Computer hardware configuration>
FIG. 4 is a diagram showing a hardware configuration example of a computer used as a management server 10 and a client terminal 20. The computer 200 shown in FIG. 4 includes a CPU (Central Processing Unit) 201 which is a calculation means, and a main storage device (main memory) 202 and an external storage device 203 which are storage means. The CPU 201 reads the program stored in the external storage device 203 into the main storage device 202 and executes it. As the main storage device 202, for example, a RAM (Random Access Memory) is used. As the external storage device 203, for example, a magnetic disk device, an SSD (Solid State Drive), or the like is used. Further, the computer 200 includes a communication interface 204 for connecting to a network and a display mechanism 205 for displaying and outputting to a display. Further, the computer 200 includes an input device 206 on which an input operation is performed by the operator of the computer 200. The configuration of the computer 200 shown in FIG. 4 is only an example, and the computer used in the present embodiment is not limited to the configuration example of FIG. For example, the storage device may be configured to include a non-volatile memory such as a flash memory or a ROM (Read Only Memory).

When the management server 10 shown in FIG. 2 is realized by the computer 200 shown in FIG. 4, the customer information DB 11 and the product information DB 12 are realized by, for example, the main storage device 202 or the external storage device 203. The function of the transmission / reception unit 13 is realized by, for example, the communication interface 204. Each function of the determination unit 14 and the generation unit 15 is realized, for example, by the CPU 201 executing a program.

When the client terminal 20 shown in FIG. 3 is realized by the computer 200 shown in FIG. 4, the transmission / reception unit 21 is realized by, for example, the communication interface 204. The acquisition unit 22 is realized, for example, by the CPU 201 executing a program. The display unit 23 is realized by, for example, the display mechanism 205. The input receiving unit 24 is realized by, for example, the input device 206 and the CPU 201.
Further, the program that realizes the embodiment of the present invention can be provided not only by communication means but also by storing it in a recording medium such as a CD-ROM.

<Table held in the management server>
Next, the contents of various data tables held in the management server 10 will be described.
FIG. 5 is a diagram showing a configuration example of the product information management table. The product information management table is held in the product information DB 12.
In the product information management table shown in FIG. 5, the name of the product is shown in the "product name", and the identification number for identifying the product is shown in the "product ID". Further, in the product information management table, the product type is indicated in the "product type". In addition, the function of the product is shown in the "problem solving function". Specifically, the "problem-solving function" indicates the function of the product for solving the business problem of the customer for each field. In the present embodiment, the "problem-solving function" is divided into five fields: "virus countermeasures", "junk mail countermeasures", "personal information protection", "unauthorized intrusion prevention", and "mobile terminal protection". Then, "○" is shown in the field where the product has a function for solving the business problem of the customer, and "-" is shown in the field where the product does not have the function. The content of each field shown in the problem-solving function may be changed according to the type of product.

FIG. 6 is a diagram showing a configuration example of the customer information management table. The customer information management table is held in the customer information DB 11.
In the customer information management table shown in FIG. 6, the name of the customer is shown in the "customer name", and the identification number for identifying the customer is shown in the "customer ID". Further, in the customer information management table, the name of a user (hereinafter referred to as a sales staff) who conducts sales activities related to selling products to customers is indicated in "sales staff". In addition, the "problem level" indicates the magnitude of the customer's business problem. Specifically, the "problem level" indicates the magnitude of the problem that the customer's equipment has in stages. In the present embodiment, the "problem level" is divided into five fields: "virus countermeasures", "junk mail countermeasures", "personal information protection", "unauthorized intrusion prevention", and "mobile terminal protection". That is, the "problem level" is divided into the same fields as the "problem solving function" of the product information management table shown in FIG. Then, "2" is shown in the field where the customer's equipment can fully respond to the customer's business problem, and "1" is shown in the field where the customer's equipment can partially respond. "0" is shown for fields that are shown and cannot be covered by the customer's equipment. That is, the larger the degree of the problem that the customer's equipment has, the smaller the value shown in the "problem level".

In the present embodiment, for example, a problem level for each field is set for each device such as a hardware device or a software device, and the determination unit 14 is a problem of each device provided in the equipment owned by the customer. Based on the cumulative total of levels, the problem level of the customer shown in the customer information management table shown in FIG. 6 is calculated.

FIG. 7 is a diagram showing a reception screen for receiving an instruction (generation instruction) for generating a product proposal document by a user. This reception screen is displayed on the display unit 23 of the client terminal 20. In the present embodiment, for example, when the user inputs the identification information into the client terminal 20 and logs in, the reception screen is displayed on the display unit 23.
On the reception screen shown in FIG. 7, the "customer name" indicates the name of the customer as the sales destination of the product, and the "sales staff" indicates the sales staff in charge of sales activities for the customer. .. Further, the "product name" indicates the name of the product to be sold to the customer, and the "product type" indicates the type of the product. Further, in the "proposal", a product proposal document icon 301 that receives a user's instruction to generate a product proposal document is shown.

As shown in FIG. 7, the user selects the product proposal document icon 301 associated with the "customer name" of "B Co., Ltd." and the "product name" of "security software B" to generate a product proposal document. Upon giving an instruction, the client terminal 20 requests the management server 10 to generate a product proposal document. Specifically, the client terminal 20 requests the management server 10 to generate a product proposal document in which the referent customer is "B Co., Ltd." and the referent product is "security software B". The referent customer is a customer who sells a product using a product proposal document for which a user has given an instruction to generate a product. The referent product is a product to be sold using the product proposal document for which the user has given an instruction to generate the product.
Upon receiving the product proposal document generation request from the client terminal 20, the management server 10 performs determination processing related to the referent customer and the referent product.

<Judgment processing>
FIG. 8 is a flowchart of the determination process. Hereinafter, an example of the determination process when the referent customer is "B Co., Ltd." and the referent product is "security software B" will be described.
First, the determination unit 14 of the management server 10 acquires the product information of the referent product from the product information management table (see FIG. 5) (S (step) 101). In this example, the determination unit 14 acquires the product information of the "security software B" in FIG.
Next, the determination unit 14 acquires customer information of the referent customer from the customer information management table (see FIG. 6) (S102). In this example, the determination unit 14 acquires the customer information of "B Co., Ltd." in FIG.

Subsequently, the determination unit 14 determines whether or not the referent customer satisfies the useful condition regarding the referent product (S103). Specifically, the determination unit 14 compares the product information acquired in step 101 with the customer information acquired in step 102. Then, in the field to which the referent-solving function of the referent product belongs, if the equipment used by the referent customer has a problem, it is determined that the referent customer satisfies the useful condition regarding the referent product, and if the referent does not have a problem, the referent is instructed. Determine that the customer does not meet the useful conditions. If there are multiple fields to which the referent-solving function belongs, and if the equipment used by the referent customer has a problem in any of these fields, the referent customer meets the useful conditions for the referent product. If the equipment used by the referent customer does not have a problem in any of the plurality of fields, it is determined that the referent customer does not satisfy the useful conditions for the referent product.

In the present embodiment, the determination unit 14 evaluates that the equipment used by the referent customer has a problem in the field where the customer's problem level is "0" or "1" in the customer information management table shown in FIG. However, in the field where the customer's problem level is "2", it is evaluated that the equipment used by the referent customer does not have a problem. The determination unit 14 is regarded as an evaluation means for evaluating whether or not the equipment has a problem for each field to which the function provided in the equipment used by the referent customer belongs.

In this example, in the fields of "antivirus", "spam measures", and "personal information protection" where "○" is shown in the problem solving function of the referent product "security software B", the referent customer "B stock" The problem level of the equipment used by the "company" is "2". Therefore, the determination unit 14 evaluates that the equipment used by the referent customer does not have a problem in the field to which the function of the referent product belongs, and determines that the referent customer does not satisfy the useful condition regarding the referent product (S103). NO).

When the referent customer satisfies the useful condition regarding the referent product (YES in S103), the determination unit 14 transmits a request for generating a product proposal document for the referent product regarding the referent customer to the generation unit 15. ..
In response to the request to generate the product proposal document, the generation unit 15 generates a product proposal document for the referent product for the referent customer (S104). The product proposal document is generated by embedding customer information about the referent customer and product information about the referent product in a predetermined electronic form held by the management server 10. The generation unit 15 transmits the generated product proposal document to the display unit 23 of the client terminal 20. The display unit 23 displays the received product proposal document.

On the other hand, when the referent customer does not satisfy the useful condition regarding the referent product (NO in S103), the determination unit 14 does not send the product proposal document generation request to the generation unit 15. In this case, the generation unit 15 does not generate a product proposal document for the referent product for the referent customer (S105). Then, the determination unit 14 transmits the customer information of the referent customer and the product information of the referent product to the display unit 23. The display unit 23 displays a non-generated screen for notifying that the product proposal document cannot be generated (S106).

FIG. 9 is a diagram showing a non-generated screen 302 displayed when the product proposal document is not generated.
As shown in FIG. 9, on the non-generationable screen 302, the non-generated information 303 for notifying that the generation instruction of the product proposal document has not been accepted, and the detailed information 304 regarding the details of the reason why the product proposal document cannot be generated. Is displayed.

In the non-generationable information 303, information regarding the reason why the product proposal document cannot be generated is displayed. Specifically, in the non-generateable information 303, as information for notifying that the referent customer does not have a business problem that can be solved by the referent product, "the customer's equipment related to the problem that can be solved by the selected product is provided. It is not possible to generate a product proposal document because it is "good". Message is displayed.

The detailed information 304 indicates the product name of the referent product, the customer name of the referent customer, and the field to which the problem solving function of the referent product belongs. Further, the detailed information 304 shows an evaluation of the function of the equipment of the referent customer in the field to which the problem-solving function of the referent product belongs. In other words, the detailed information 304 shows the evaluation of the business problem of the referent customer in the field to which the problem-solving function of the referent product belongs. In this embodiment, the equipment of the referent customer has no problem in the fields "antivirus", "spam measures", and "personal information protection" to which the problem solving function of the referent product "security software B" belongs. The word "good" is displayed. That is, as an evaluation of the function provided in the equipment used by the referent customer, information for notifying that the customer's equipment does not have a problem in each field to which the function of the referent product belongs is displayed.
The non-generateable information 303 and the detailed information 304 are taken as cause information regarding the cause of the restriction on the generation of the product proposal document.

As described above, in the present embodiment, it is determined whether or not the referent customer satisfies the useful condition regarding the usefulness of the function of the referent product, and when it is determined that the referent customer does not satisfy the useful condition, the instruction is given. Limit the generation of product proposal documents for the target product.
Here, for example, for a specific product, the customer does not have a business problem that can be solved by the function of the product, and the business problem that the customer has cannot be solved by the function of the product. It may not be useful. In such a case, if the sales activity is performed to the customer using the product proposal document related to the product whose function is not useful, the proposal that does not lead to the purchase of the product by the customer is made, and the opportunity of the sales activity to the customer is wasted. There is a risk of doing so.

On the other hand, when the generation of the product proposal document of the product whose function is not useful in solving the business problem of the customer is restricted as in the present embodiment, the creation of the product proposal document that does not lead to the purchase of the product is suppressed. As a result, the waste of sales activity opportunities for customers is suppressed.

Further, in the present embodiment, useful conditions are determined based on a comparison between the function of the referent product and the function provided in the equipment used by the referent customer.
In such a case, the content of the useful condition can be changed according to the referent customer.

Further, in the present embodiment, when the determination unit 14 evaluates that the equipment of the referent customer has a problem in the field to which the function of the referent product belongs, it is determined that the referent customer satisfies the useful condition regarding the referent product. do. Further, when it is evaluated that the equipment of the referent customer does not have a problem in the field to which the function of the referent product belongs, it is determined that the referent customer does not satisfy the useful condition regarding the referent product.
In such a case, if it is evaluated that the equipment of the referent customer does not have a problem in the field to which the function of the referent product belongs, the generation of the product proposal document for the referent product is restricted. Therefore, in all fields to which the function of the referent product belongs, it is possible to purchase the product as compared with the case where the function provided in the equipment of the referent customer does not have a problem but the generation of the product proposal document is not restricted. Creation of product proposal documents that are not tied is suppressed.

Further, in the present embodiment, when the generation of the product proposal document is restricted, the cause information regarding the restricted cause is displayed on the display unit 23.
In such a case, the user can easily find a product for which the generation of the product proposal document is not restricted by understanding the reason why the generation of the product proposal document is restricted.

Further, in the present embodiment, as the cause information, information regarding the evaluation of the function provided in the equipment used by the referent customer is displayed.
In such a case, the user can easily search for a product having a useful function with respect to the equipment used by the referent customer.

In the present embodiment, the determination unit 14 evaluates whether or not the equipment has a problem for each field to which the function provided in the equipment of the referent customer belongs, but the present invention is not limited to this. For example, an evaluation means for evaluating whether or not this equipment has a problem may be provided in the management server 10 separately from the determination unit 14 for each field to which the function provided in the equipment of the referent customer belongs.
Further, in the present embodiment, the determination unit 14 calculates the degree of the problem of the function provided in the equipment of the referent customer, but the present invention is not limited to this. For example, a calculation means for calculating the degree of the problem of the function provided in the equipment of the referent customer may be provided in the management server 10 separately from the determination unit 14.

Further, in the present embodiment, when the function of the product belongs to a plurality of fields, if the equipment of the referent customer has a problem in any one field, a product proposal document is generated, and the referent customer in any field. If the equipment does not have a problem, it limits the generation of product proposal documents, but it is not limited to this. For example, when the function of a product belongs to a plurality of fields, if the equipment of the referent customer has a problem in a predetermined number (for example, 2) or more of the fields, a product proposal document is generated and the equipment of the referent customer is used. If the number of fields having problems is less than a predetermined number, the generation of product proposal documents may be restricted.

Further, in the present embodiment, the product information management table shown in FIG. 5 indicates whether or not the product has a problem-solving function, but the present invention is not limited to this. For example, the magnitude of the problem-solving function of the product may be indicated step by step, such as "0", "1", "2", and so on. In this case, the higher the stage, the greater the degree of the problem-solving function of the product, and the product solves the problem in the field where the stage higher than the predetermined value (for example, the stage higher than the stage "1") is shown. It may be evaluated as having a function.

Further, in the present embodiment, in the customer information management table shown in FIG. 6, the magnitude of the degree of the problem in the customer's equipment is shown step by step, but the present invention is not limited to this. For example, it may indicate whether or not the customer's equipment has a problem. Specifically, the symbol "○" is shown in the problem-level field where the customer's equipment is evaluated as having a problem, and "○" is shown in the problem-level field where the customer's equipment is evaluated as having no problem. The symbol "x" may be shown.

Further, in the present embodiment, the function of the referent product and the function provided in the equipment of the referent customer are compared for each field to which the function of the referent product belongs, but the present invention is not limited to this.
For example, based on the cumulative total of problem levels for each field in the equipment of the referent customer, the comprehensive evaluation of the customer's business problem in the comprehensive field to which the product type of the referent product belongs is "0", "1", It may be shown step by step like "2" .... In this case, the higher the stage, the smaller the degree of the problem in the equipment of the referent customer, and if the stage is higher than the predetermined value (for example, the stage higher than the stage "1"), the referent customer It may be determined that the equipment does not have a problem, and the generation of the product proposal document for the referent product may be restricted.

Further, in the present embodiment, the determination process of whether or not to generate the product proposal document with one product as the referent product has been described, but the present invention is not limited to this.
For example, a determination process may be performed as to whether or not to generate a product proposal document with two or more products as referent products. In this case, for example, in the product proposal document, the page regarding the referent product regarding the useful conditions satisfied by the referent customer may be generated, and the page regarding the referent product regarding the useful conditions not satisfied by the referent customer may not be generated. .. In this case, among the product proposal documents, the page of the referent product regarding the useful conditions satisfied by the referent customer is generated, and the page of the referent product related to the useful conditions not satisfied by the referent customer is not generated. It can be seen as an example of limiting the generation of.

Further, in the present embodiment, the detailed information 304 of the non-generated screen 302 displays the field to which the function of the referent product belongs and the evaluation of the function provided in the equipment of the referent customer in this field. Not limited to this.
For example, a field to which the function of the referent product belongs and a field to which the function of the referent product does not belong may be displayed so as to be distinguishable. Further, for example, a field in which the equipment of the referent customer has a problem and a field in which the facility does not have a problem may be displayed so as to be distinguishable from each other.

<Explanation of modification>
Next, a modified example of the example of limiting the generation of the product proposal document will be described.
In the present embodiment, when the referent customer does not satisfy the useful conditions, the non-generationable screen 302 is displayed without generating the product proposal document for the referent product, but the mode of limiting the generation of the product proposal document is Not limited to this.
FIG. 10 is a diagram showing a reception screen as a modified example of an example of limiting the generation of a product proposal document.

In this modification, when the determination unit 14 determines that the referent customer satisfies the useful condition, the product proposal document icon 301 of the product related to this useful condition is displayed on the display unit 23. On the other hand, when the determination unit 14 determines that the referent customer does not satisfy the useful conditions, the product proposal document icon is displayed in a manner different from that of the product proposal document icon 301. Specifically, if the referent customer does not satisfy the useful condition, the generation restriction icon 308 suggesting that the product proposal document for the product related to the useful condition cannot be generated is displayed. The generation restriction icon 308 includes an image suggesting that the product proposal document cannot be generated. Even if the generation restriction icon 308 is selected, the generation instruction of the product proposal document is not accepted.
The product proposal document icon 301 is regarded as a reception unit that receives an instruction to generate a product proposal document. In other words, the product proposal document icon 301 is regarded as a reception unit displayed by the first display mode. Further, the generation restriction icon 308 is regarded as a reception unit that does not accept the generation instruction of the product proposal document. In other words, the generation restriction icon 308 is regarded as a reception unit displayed by a second display mode different from the first display mode.

In the modified example, for example, when the reception screen is displayed, it is determined whether or not the referent customer satisfies the useful condition for all the products related to the product name displayed as the product list on the reception screen. Then, when the customer satisfies the useful condition, the product proposal document icon 301 of the product related to the useful condition is displayed on the reception screen. If the customer does not meet the useful conditions, the product generation restriction icon 308 related to the useful conditions is displayed on the reception screen.

When the generation restriction icon 308 is selected, the generation impossible screen 302 may be displayed.
Further, when the generation restriction icon 308 is selected, the product proposal document may be generated. Even in such a case, since the generation restriction icon 308 is displayed in a display mode different from that of the product proposal document icon 301, the creation of the product proposal document that does not lead to the purchase of the product is suppressed.

Further, for example, when the referent customer does not satisfy the useful condition, neither the product proposal document icon 301 nor the generation restriction icon 308 of the product related to the useful condition may be displayed on the reception screen. That is, if the referent customer does not satisfy the useful condition, the instruction to generate the product proposal document of the product related to the useful condition may not be given.

<Second embodiment>
Next, the determination process of the second embodiment will be described.
The second embodiment compares the function of the referent product with the function of the equipment used by the referent customer, and limits the generation of the product proposal document when the referent customer does not meet the useful conditions. It is common with the first embodiment.

On the other hand, the second embodiment is different from the first embodiment in that, in addition to the above processing, it is determined whether or not to limit the generation of the product proposal document by focusing on the history of sales activities for the referent customer. Is a different judgment processing method.
That is, in the second embodiment, it is determined whether or not the sales activity related to the referent product has already been performed for the referent customer. Then, when the sales activity is already carried out, the generation of the product proposal document for the referent product is restricted even if the referent customer satisfies the useful condition.

FIG. 11 is a diagram showing a configuration example of the sales activity history management table. In the present embodiment, the sales activity history management table is held in the customer information DB 11.
In the sales activity history management table shown in FIG. 11, the name of the customer is shown in the "customer name", and the identification number of the customer is shown in the "customer ID". Further, in the sales activity history management table, the date on which the sales activity was performed is shown in the "business activity date". In addition, in the sales activity history management table, the name of the sales staff who performed the sales activity is shown in "Sales staff", and the name of the product proposed to the customer in the sales activity is shown in "Proposed product". There is. Further, the "contract information" shows information on whether or not the customer has purchased the "proposed product". In the present embodiment, when ◯ is shown in the “contract information”, it means that the customer has purchased the “proposal product”. In addition, when x is shown in the "contract information", it means that the customer did not purchase the "proposed product".

FIG. 12 is a flowchart of the determination process in the second embodiment. Hereinafter, an example of the determination process in the case where the referent customer is “D Co., Ltd.” and the referent product is “security software B” will be described.
The determination unit 14 of the management server 10 first acquires the product information of the referent product (S201), and then acquires the customer information of the referent customer (S202). Further, the determination unit 14 acquires information regarding the history of sales activities for the referent customer from the sales activity history management table (see FIG. 11) (S203).

The determination unit 14 determines whether or not the referent customer satisfies the useful condition regarding the referent product (S204). When it is determined that the referent customer does not satisfy the useful condition (NO in S204), the generation unit 15 does not generate the product proposal document for the referent product (S205). Further, the display unit 23 displays the non-generated screen 302 (see FIG. 9) (S206).
In this example, the equipment of the referent customer "D Co., Ltd." (see Fig. 6) in the fields "Junk E-mail Countermeasures" and "Personal Information Protection" to which the function of the referent product "Security Software B" (see Fig. 5) belongs. The problem level is "1", and it is evaluated that the equipment of the referent customer has a problem in these fields. Therefore, the determination unit 14 determines that the referent customer satisfies the useful condition (YES in S204).

When it is determined that the referent customer satisfies the useful condition (YES in S204), the determination unit 14 determines whether or not the referent product has been proposed to the referent customer (S207). Specifically, the determination unit 14 indicates the referent customer when the date is indicated on the "business activity date" in which the referent customer and the referent product are associated in the sales activity history management table shown in FIG. It is determined that the referent product has been proposed, and if the date is not indicated, it is determined that the referent product has not been proposed.
In this example, since the date on which the referent product "Security Software B" is sold to the referent customer "D Co., Ltd." is indicated as "2016/11/20", the determination unit 14 determines. It is determined that the referent product has been proposed to the referent customer (YES in S207).

If the referent product has not been proposed to the referent customer (NO in S207), the generation unit 15 generates a product proposal document for the referent product (S208).
On the other hand, when the referent product has been proposed to the referent customer (YES in S207), the generation unit 15 does not generate the product proposal document for the referent product (S209). Then, the determination unit 14 transmits the history of sales activities for the referent customer to the display unit 23. The display unit 23 displays a generation restriction screen for notifying that the generation of the product proposal document is restricted (S210).

Subsequently, the determination unit 14 determines whether or not to generate a product proposal document for the referent product (S211). In the present embodiment, the user can instruct the generation of the product proposal document on the generation restriction screen displayed on the display unit 23. When the user gives an instruction to generate the product proposal document, the determination unit 14 determines that the product proposal document is generated in response to the generation instruction (YES in S211), and requests the generation unit 15 to generate the product proposal document. conduct. The generation unit 15 receives the generation request from the determination unit 14 and generates a product proposal document (S208). Further, when the user refuses to generate the product proposal document, the determination unit 14 determines that the product proposal document is not generated (NO in S211), and the generation unit 15 does not generate the product proposal document.

FIG. 13 is a diagram showing a generation restriction screen 309 displayed when the referent product has been proposed to the referent customer.
As shown in FIG. 13, the generation restriction screen 309 includes the generation restriction information 310 for notifying that the generation of the product proposal document is restricted, and the detailed information 311 regarding the details of the cause of the restriction on the generation of the product proposal document. Is displayed.

The generation restriction information 310 displays information regarding the cause of the restriction on the generation of the product proposal document. Specifically, the generation restriction information 310 tells the user that the referent product has already been proposed to the referent customer, saying, "The selected product has a history of proposals to the same customer in the past." A message to notify is displayed.

The detailed information 311 displays information regarding the history of sales activities performed on the referent customer. Specifically, the detailed information 311 includes the name of the referent customer, the date when the sales activity was performed, the name of the referent product, and the name of the salesperson who performed the referent product for the referent customer. , And contract information, that is, whether or not the referent customer has purchased the product.

Further, when the user gives an instruction to generate the product proposal document on the generation restriction screen 309, that is, when the generation button 312 of the product proposal document is selected, the product proposal document for the referent product is generated and this product. The proposal document is displayed. On the other hand, when the user refuses to generate the product proposal document, that is, when the refusal button 313 to generate the product proposal document is selected, the product proposal document is not generated.

As described above, in the present embodiment, the product proposal for the referent product is made based on the history of the sales activity of the referent product to the referent customer, even if the referent customer satisfies the useful condition for the referent product. Limit document generation.
If a customer has received a product proposal in the past and purchased this product, even if this customer receives the same product proposal again, he / she does not need this product again. May not be reached. In addition, if a customer receives a product proposal in the past and does not purchase the product because he / she does not need this product, it may be difficult for this customer to purchase this product even if he / she receives the same product proposal again. be. That is, if a product has already been proposed to a customer, even if the same product is proposed to the customer again, it may not lead to the purchase of the product.

Therefore, in the present embodiment, for a product that has already been proposed to a customer, even if the customer meets the useful conditions for this product, the generation of a product proposal document for this product is restricted to make a proposal. Suppress the creation of product proposal documents that are difficult to purchase because of the completion.

Further, in the present embodiment, the user cannot instruct the generation of the product proposal document on the non-generation screen 302 (see FIG. 9) displayed when the referent customer does not satisfy the useful condition. That is, if the referent customer does not satisfy the useful condition, the instruction to generate the product proposal document is not accepted after the generation of the product proposal document for the referent product related to this useful condition is restricted.
On the other hand, on the generation restriction screen 309 (see FIG. 13) displayed when the product to be instructed has been proposed, the user can instruct the generation of the product proposal document. That is, if the referent customer meets the useful conditions and the generation of the product proposal document is restricted based on the history of sales activities, the instruction to generate the product proposal document for the referent product is accepted after this restriction. A product proposal document is generated.

Even if a customer receives a proposal in the past and receives a proposal for a purchased product again, the customer may purchase the same product again due to reasons such as needing this product further. In addition, even if the customer receives a proposal in the past and receives a proposal for a product that he / she did not purchase, the customer will again receive a proposal due to a change in the customer's business environment and the need for the product. You may purchase a product that has been proposed by. That is, if the customer satisfies the useful conditions, even if the product has already been proposed to the customer, the proposal may lead to the purchase of this product.

Therefore, in the present embodiment, when the referent customer satisfies the useful condition, the generation of the product proposal document for the referent product is restricted even if the referent product has already been proposed to the referent customer. It is possible to generate this product proposal document later. In other words, when the referent condition is satisfied for the referent customer and the referent product has been proposed to the referent customer, the referent customer does not satisfy the useful condition, as compared with the case where the referent customer does not satisfy the useful condition. The degree of restriction on the generation of product proposal documents has been relaxed. In this case, it is possible to suppress the restriction on the creation of the product proposal document that leads to the purchase of the product.

In the present embodiment, when the referent customer satisfies the useful condition and the referent product has already been proposed to the referent customer, the referent product is referred to regardless of the proposed result. It limits the generation of product referents, but is not limited to this.
For example, when the referent customer satisfies the useful condition and the referent product proposed to the referent customer is purchased, a product proposal document for the referent product is generated and the referent customer is notified. If the referent product proposed in the above is not purchased, the generation of the referent document for the referent product may be restricted.

Further, for example, when the referent customer satisfies the useful condition and the referent product proposed to the referent customer has not been purchased, a product proposal document for the referent product is generated and the referent customer is notified. On the other hand, when the proposed referent product is purchased, the generation of the referent document for the referent product may be restricted.

In addition, for example, when the referent customer satisfies the useful condition, the referent product is being proposed to the referent customer and it is not reached to conclude whether or not the referent product has been purchased. If a product proposal document is generated and it is concluded whether or not the referent product has been purchased for the referent customer, the generation of the product proposal document for the referent product may be restricted.
In this case, for example, in the "contract information" of the sales activity history management table shown in FIG. 11, it means that the product is being proposed to the referent customer and the conclusion of whether or not to purchase this product has not been reached. The symbol "Δ" may be shown. When the referent customer meets the useful conditions, and if "△" is shown in the "contract information" regarding the history of sales activities performed on the referent customer, the product for the referent product. Proposal documents may be generated, and if "○" or "×" is shown in the "contract information", the generation of product proposal documents for the referent may be restricted.

Further, for example, when the referent customer satisfies the useful condition, it is determined whether or not a predetermined period (for example, 6 months) has elapsed from the date when the referent product was last proposed to the referent customer. May be.
Specifically, when the referent customer meets the useful conditions, the product proposal for the referent product is made when a predetermined period has elapsed from the date when the referent product was last proposed to the referent customer. A document may be generated, and if a predetermined period has not passed, the generation of a product proposal document for the referent may be restricted. In this case, whether or not a predetermined period has elapsed from the date when the referent product was last proposed to the referent customer is determined by, for example, the day when the determination process is performed is the sales activity shown in FIG. Judgment is made based on whether or not a predetermined period has passed from the "business activity date" of the management table.

<Third embodiment>
Next, the determination process of the third embodiment will be described.
In the second embodiment, when the referent customer satisfies the useful condition, it is determined whether or not the referent product has been proposed to the referent customer.
On the other hand, in the third embodiment, when the referent customer satisfies the useful condition, it is determined whether or not the referent product satisfies the condition defined for the introduction of the product by the referent customer.

FIG. 14 is a diagram showing a configuration example of the product information management table according to the third embodiment.
In the product information management table shown in FIG. 14, "product name", "product ID", "product type", and "problem solving function" are shown as in the first embodiment. Further, in the product information management table of the present embodiment, the selling price of the product is shown in the "selling price".

FIG. 15 is a diagram showing a configuration example of the proposed condition management table. The proposal condition management table is held in the customer information DB 11.
In the proposal condition management table shown in FIG. 15, an identification number for identifying a proposal condition for proposing a product to a customer is shown in the "condition ID", and the name of the customer is shown in the "customer name". The customer's identification number is shown in the "customer ID". Further, in the proposal condition management table, whether or not the proposal condition set for the customer exists is indicated in "Presence / absence of proposal condition". Further, the "proposal condition" shown in the proposal condition management table is divided into "item" and "content". The "item" indicates the item to which the content of the proposal condition belongs, and the "content" indicates the content of the proposal condition.

In this embodiment, the proposed conditions are set for D Co., Ltd. Specifically, it is set as a proposal condition that the "selling price" of the product proposed to "D Co., Ltd." is "500,000 yen or less". If the proposal conditions are not set, "-" symbols are shown in "items" and "contents", respectively. The proposed conditions are regarded as the specific conditions of the referent customer regarding the introduction of the product.

The proposal conditions are set based on the customer's request, the attributes of the equipment used by the customer, the history of sales activities, and the like. The attribute of the equipment used by the customer is, for example, the number of employees in the customer. When the proposal condition is set based on the number of employees in the customer, for example, the larger the number of employees in the customer, the higher the upper limit of the selling price in the proposal condition is set. Further, the history of sales activities is, for example, the history of purchases of past products by customers who have received sales activities. When the proposal condition is set based on the purchase history of the customer, for example, the selling price of the highest-priced product among the products purchased by the customer through sales activities is set as the upper limit of the selling price in the proposal condition. ..

FIG. 16 is a flowchart of the determination process according to the third embodiment. Hereinafter, an example of the determination process when the referent customer is "D Co., Ltd." and the referent product is "security software B" will be described.
The determination unit 14 of the management server 10 first acquires the product information of the referent product (S301), and then acquires the customer information of the referent customer (S302). Further, the determination unit 14 acquires the proposal condition associated with the referent customer from the proposal condition management table (S303).

The determination unit 14 determines whether or not the referent customer satisfies the useful condition (S304). When it is determined that the referent customer does not satisfy the useful condition (NO in S304), the generation unit 15 does not generate the product proposal document for the referent product (S305). Further, the display unit 23 displays the non-generated screen 302 (see FIG. 9) (S306).
In this example, as described above, the referent customer "D Co., Ltd." determines that the useful condition for the referent product "security software B" is satisfied (YES in S304).

When it is determined that the referent customer satisfies the useful condition (YES in S304), the determination unit 14 determines whether or not the referent product satisfies the proposal condition associated with the referent customer (S307). Specifically, it is determined whether or not the referent product satisfies the "proposal condition" associated with the referent customer in the referent condition management table shown in FIG. In the present embodiment, when the selling price of the referent product is lower than the selling price shown in the proposal condition associated with the referent customer, it is determined that the referent product satisfies the proposal condition. Further, when the selling price of the referent product is higher than the selling price shown in the proposal condition associated with the referent customer, it is determined that the referent product does not satisfy the proposal condition.

In this example, the referent customer "D Co., Ltd." is set as a proposal condition that the "selling price" of the product is "500,000 yen or less" (see FIG. 15). On the other hand, the "selling price" of the referent product "Security Software B" is "800,000 yen" (see Fig. 14), which is higher than the "selling price" set as the proposal condition of the referent customer "D Co., Ltd." It is expensive. In this case, the determination unit 14 determines that the referent product "security software B" does not satisfy the proposal conditions of the referent customer "D Co., Ltd." (NO in S307).
In the present embodiment, when the proposal condition is not set for the referent customer, the determination unit 14 determines that the referent product satisfies the proposal condition associated with the referent customer.

When the referent product satisfies the proposal condition associated with the referent customer (YES in S307), the generation unit 15 generates a product proposal document for the referent product (S308).
On the other hand, when the referent product does not satisfy the proposal condition associated with the referent customer (NO in S307), the generation unit 15 does not generate the product proposal document for the referent product (S309). Then, the determination unit 14 transmits the product information of the referent product and the proposal conditions associated with the referent customer to the display unit 23. The display unit 23 displays a generation restriction screen for notifying the user that the generation of the product proposal document for the referent is restricted (S310).

Subsequently, the determination unit 14 determines whether or not to generate a product proposal document for the referent product (S311). In the present embodiment, the user can instruct the generation of the product proposal document for the referent product on the generation restriction screen displayed on the display unit 23. When the user gives an instruction to generate the product proposal document, the determination unit 14 determines that the product proposal document is generated (YES in S311), and requests the generation unit 15 to generate the product proposal document. The generation unit 15 receives a generation request from the determination unit 14 and generates a product proposal document (S308). Further, when the user refuses to generate the product proposal document for the referent product, the determination unit 14 determines that the product proposal document is not generated (NO in S311), and the generation unit 15 does not generate the product proposal document.

FIG. 17 is a diagram showing a generation restriction screen 315 displayed when the referent product does not satisfy the proposed conditions.
As shown in FIG. 17, on the generation restriction screen 315, the generation restriction information 316 for notifying that the generation of the product proposal document for the referent is restricted, and the details of the reason why the generation of the product proposal document is restricted. Detailed information about 317 and is displayed.

In the generation restriction information 316, information regarding the cause of the restriction on the generation of the product proposal document is displayed. Specifically, the generation restriction information 316 states that "the selected product does not meet the proposal conditions" as information for notifying that the referent product does not meet the proposal conditions associated with the referent customer. A message is displayed.

In the detailed information 317, the proposal conditions associated with the referent customer and the product information of the referent product are displayed. Specifically, the detailed information 317 includes the name of the referent customer, the name of the referent product, the selling price of the referent product, the name of the salesperson in charge of sales activities for the referent customer, and the referent customer. The associated proposal conditions are shown.

Further, when the user gives an instruction to generate a product proposal document for the product to be instructed on the generation restriction screen 315, that is, when the product proposal document generation button 318 is selected, the product proposal document is generated and this product is generated. The proposal document is displayed. On the other hand, when the user refuses to generate the product proposal document for the referent product, that is, when the refusal button 319 for generating the product proposal document is selected, the product proposal document is not generated.

As described above, in the present embodiment, it is determined whether or not the referent product satisfies the proposal condition of the referent customer, and when it is determined that the referent product does not satisfy the proposal condition, the referent customer sets the useful condition. Even if it is determined that the product is satisfied, the generation of the product proposal document for the referent product is restricted.
As described above, the proposal conditions are set based on the customer's request, the attributes of the equipment used by the customer, etc., and even if a product that does not meet the proposal conditions associated with the customer is proposed, the purchase of this product May not lead to.

Therefore, in the present embodiment, when the referent product does not satisfy the proposal condition associated with the referent customer, the referent product is referred to even if the referent customer satisfies the useful condition regarding the referent product. By limiting the generation of product proposal documents, it is possible to suppress the creation of product proposal documents for products that are difficult to purchase because they do not meet the proposal conditions.

Further, in the present embodiment, when the referent customer does not satisfy the useful condition, the instruction to generate the product proposal document is not accepted after the generation of the product proposal document for the referent product related to the referent is restricted.
On the other hand, on the generation restriction screen 315 (see FIG. 17) displayed when the referent product does not satisfy the proposal conditions associated with the referent customer, the user can instruct to generate a product proposal document for the referent product. .. That is, when it is determined that the referent customer satisfies the useful condition regarding the referent product and the referent product does not satisfy the proposal condition regarding the referent customer, the product proposal document for the referent product After the generation is restricted, the instruction to generate this product proposal document is accepted and the product proposal document is generated.

Even if a product that does not meet the proposal conditions associated with the customer is proposed to the customer, the customer may purchase this product due to changes in the environment in the customer's business or the like.
Therefore, in the present embodiment, when the referent customer satisfies the useful condition regarding the referent product, the referent product is referred to even if the referent product does not satisfy the proposal condition associated with the referent customer. It is possible to generate this product proposal document after limiting the generation of the product proposal document. In this case, it is possible to suppress the restriction on the creation of the product proposal document that leads to the purchase of the product.

In this embodiment, one proposal condition is set for the referent customer, but the present embodiment is not limited to this. For example, two or more proposal conditions may be set for the referent customer. In this case, if the referent product meets all the proposal conditions associated with the referent customer, a product proposal document for the referent product is generated, and if any of the proposal conditions is not met, this product proposal document is generated. Generation may be restricted.

Moreover, the technical scope of the present invention is not limited to the above-described embodiment. Various changes and alternative configurations that do not deviate from the scope of the technical idea of the present invention are included in the present invention. For example, in the above embodiment, the management server 10 is configured to hold and manage the customer information DB 11 and the product information DB 12, but is configured to provide a management server that holds these databases separately from the management server 10. You may.

10 ... Management server, 14 ... Judgment unit, 15 ... Generation unit, 20 ... Client terminal, 21 ... Transmission / reception unit, 22 ... Acquisition unit, 23 ... Display unit, 24 ... Input reception unit, 30 ... Customer terminal

Claims (10)

A means for requesting the generation of a product proposal document by instructing the referent customer to generate a product proposal document for the selected product among the products to be proposed in order to link to the purchase of the product. ,
A generation means for generating the product proposal document for which the user has instructed to generate the product proposal document, and a generation means for generating the product proposal document.
Upon receiving the request to generate the product proposal document, the referent customer determines whether or not the useful condition regarding the usefulness of the function of the selected product is satisfied.
Equipped with
The information processing system is characterized in that the generation means limits the generation of the product proposal document when the determination means determines that the referent customer does not satisfy the useful condition. The information processing system according to claim 1, further comprising a display means for displaying cause information regarding the restricted cause when the generation of the product proposal document is restricted by the generation means. The information processing system according to claim 2, wherein the cause information is information related to evaluation of a function provided in the equipment used by the referent customer. The generation means limits the generation of the product proposal document even when it is determined that the referent customer satisfies the useful condition based on the history of sales activities related to the product to the referent customer. The information processing system according to claim 1, wherein the information processing system is characterized by the above. When it is determined that the instruction target customer does not satisfy the useful condition, the generation means does not accept the instruction to generate the product proposal document after limiting the generation of the product proposal document, while the instruction target customer does not accept the instruction to generate the product proposal document. If it is determined that the usefulness condition is satisfied and the generation of the product proposal document is restricted based on the history of the sales activity, the product proposal is received by receiving the instruction to generate the product proposal document after the restriction. The information processing system according to claim 4, wherein a document is generated. The determination means determines whether or not the product satisfies the specific condition of the referent customer regarding the introduction of the product.
The generation means limits the generation of the product proposal document even when it is determined that the product does not satisfy the specific condition and the referent customer is determined to satisfy the useful condition. The information processing system according to claim 1. When it is determined that the instruction target customer does not satisfy the useful condition, the generation means does not accept the instruction to generate the product proposal document after limiting the generation of the product proposal document, while the instruction target customer does not accept the instruction to generate the product proposal document. If it is determined that the usefulness condition is satisfied and the product does not satisfy the specific condition, the instruction to generate the product proposal document after restricting the generation of the product proposal document is received and the product is concerned. The information processing system according to claim 6, wherein a product proposal document is generated. The information processing system according to claim 1, wherein the useful conditions are determined based on a comparison between the functions of the product and the functions provided in the equipment used by the referent customer. Further, an evaluation means for evaluating whether or not the equipment has a problem is further provided for each field to which the function provided in the equipment used by the referent customer belongs.
When the evaluation means evaluates that the equipment has the problem in the field to which the function of the product belongs, the determination means determines that the referent customer satisfies the useful condition, and the equipment in the field. The information processing system according to claim 8, wherein when it is evaluated that the product does not have the problem, it is determined that the customer to be instructed does not satisfy the useful condition. On the computer
A function to request the generation of the product proposal document by instructing the referent customer to generate a product proposal document for the selected product among the products to be proposed in order to link to the purchase of the product. ,
A function to generate the product proposal document for which the user has instructed to generate the product proposal document, and
Upon receiving the request to generate the product proposal document, the function of determining whether or not the referent customer satisfies the useful condition regarding the usefulness of the function of the selected product , and
When it is determined that the referent customer does not meet the useful conditions, the function of restricting the generation of the product proposal document and the function of limiting the generation of the product proposal document.
A program to realize.

Images