JP2009080861A - Order sales introduction system and order sales introduction method - Google Patents

Abstract

【Task】
Rather than waiting for information from customers to develop information, the target industry is determined based on past performance data, and the latest company information is acquired from the homepage, etc., and product and service information of partner companies is transmitted. And provide a sales order introduction system to increase sales opportunities for partners.
[Solution]
Means for collecting partner company's case information via the network, means for selecting a company's industry to send information from the collected case information, means for collecting company information of a company corresponding to the selected company's industry, Means for selecting the collected company information; and means for transmitting product information for the selected company information.
[Selection] FIG.

Description

The present invention relates to a system for receiving orders for sales and demonstrations via a network and transmitting the information to an arbitrary computer. In particular, the present invention discriminates the information and provides information corresponding to the computer in accordance with the information. About.

Conventionally, as an order sales introduction system that receives orders for sales and demonstrations via a network, and determines the information when sending the information to any computer, and provides information corresponding to the computer, As described in Japanese Patent Application Laid-Open No. 2003-91674, there is known one that guides products based on changes in the natural environment (see Patent Document 1).

JP 2003-91674 A

According to the above prior art, only product guidance that grasps the consumption trend of each season is described.

The purpose of the present invention is to introduce a product or service, acquire order / inquiry information for the product or service, and determine whether sales or service can be provided to each company that provides the product or service that matches the acquired information. The purpose is to provide an order sales introduction system that feeds back information on products and services that have been sold well to each company based on inquiry and each company's response history information.

The second purpose of the present invention is not to wait for information from the customer to develop the information, but to determine the target industry based on the past performance data and obtain the latest company information from the homepage etc. It is to provide a sales order introduction system for transmitting product and service information of a partner company and increasing sales opportunities of the partner.

The third object of the present invention is to select each partner company that has an unscheduled schedule in response to an estimate request from a customer, obtain an estimate from each partner, determine the validity of the estimate content, Another object of the present invention is to provide an order sales introduction system for the purpose of selecting an optimal partner.

  In order to achieve the above object, the present invention provides means for collecting case information of a partner company via a network, means for selecting a business type of a company that transmits information from the collected case information, and the selected business type. Means for collecting company information of the corresponding company, means for selecting the collected company information, and means for transmitting product information to the selected company information.

According to the present invention, by providing information on the best-selling products according to the inquiry status, it is possible to formulate a business plan such as the priority order of products to be focused on by each partner. Since the actual situation can be grasped by evaluation from the corresponding inquiry source, it is possible to take measures to optimize the business strategy. Moreover, in the above-mentioned, the number of partner companies is expanded, and the number of registered products is also increased, so that the demand for introduction information servers is increased and business opportunities can be led.

Further, according to the present invention, it is possible to shift from a PULL type business to a PUSH type business. In addition, regarding the conditions for PUSHing to new customers, it is possible to carry out targeted sales expansion activities because product information is sent by determining the strong industry of each partner.

In addition, the introduction of the SI server has been used to check the validity of the estimate by hand, but since the validity of the estimate can be checked systematically, the customer can quickly answer the estimate. Can be done.

It is a block diagram of an order sales introduction system showing an embodiment of the present invention. It is a block diagram of the introduction information server of FIG. It is a block diagram of the partner analysis server of FIG. It is a flowchart figure which shows the process sequence of the introduction information server of FIG. It is a flowchart figure which shows the process sequence of the partner analysis server of FIG. FIG. 3 is a layout diagram of a table managed by the company information DB of FIG. 2. FIG. 3 is a layout diagram of a table managed by the inquiry information DB of FIG. 2. FIG. 3 is a layout diagram of a table managed by a registered product DB in FIG. 2. FIG. 3 is a layout diagram of a table managed by the partner information DB of FIG. 2. FIG. 3 is a layout diagram of a table managed by the inquiry determination condition DB of FIG. 2. FIG. 3 is a layout diagram of a table managed by a case handling result DB in FIG. 2. FIG. 3 is a layout diagram of a table managed by the external information DB of FIG. 2. FIG. 3 is a layout diagram of a table managed by the inquiry determination result DB of FIG. 2. FIG. 3 is a layout diagram of a table managed by a case record DB in FIG. 2. It is an example of a result notification transmitted for each partner. It is a block diagram of an order sales introduction system showing an embodiment of the present invention. It is a block diagram of the customer analysis server of FIG. It is a block diagram of SI server of FIG. It is a block diagram of the partner company exclusive server of FIG. It is a flowchart figure which shows the process sequence of the customer analysis server of FIG. It is a flowchart figure which shows the process sequence of SI server of FIG. FIG. 18 is a layout diagram of a table managed by the target partner DB of FIG. 17. FIG. 18 is a layout diagram of a table managed in the customer matter DB of FIG. 17. FIG. 18 is a layout diagram of a table managed by the business category classification DB of FIG. 17. FIG. 18 is a layout diagram of a table managed by the target industry DB in FIG. 17. FIG. 18 is a layout diagram of a table managed by the new customer DB of FIG. 17. FIG. 19 is a layout diagram of a table managed by the estimation condition DB of FIG. 18. FIG. 19 is a layout diagram of a table managed by the corresponding partner DB in FIG. 18. FIG. 19 is a layout diagram of a table managed by the partner check condition DB of FIG. 18. FIG. 19 is a layout diagram of a table managed by the estimation result DB of FIG. 18. FIG. 19 is a layout diagram of a table managed by the registered product price DB of FIG. 18. FIG. 20 is a layout diagram of a table managed in the disclosure item DB of FIG. 19. FIG. 20 is a layout diagram of a table managed by the disclosure schedule DB of FIG. 19.

  Embodiments of the present invention will be described below.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a system configuration diagram of an order sales introduction system according to an embodiment of the present invention.
As shown in FIG. 1, an introduction information server 101, a partner analysis server 102, each inquiry computer 103 that transmits inquiry information, and each partner computer 104 that provides introduction information and business information to and obtains each partner. Are configured via the network 105. The inquiry information is shown in detail in FIG. The introduction information and business information are shown in detail in FIG.

The introduction information server 101 in the order sales introduction system shown in FIG. 1 obtains inquiry information from the inquiry computer 103, selects an optimal product from the information, determines inquiry information, selects an optimal partner, and inquires. An answer to the computer 103 and a case response request to the partner computer 104 are sent.

Introductory information server 101 and partner analysis server 1 in the order sales system shown in FIG.
02 can also be operated on the same server.

  A configuration diagram of the introduction information server 101 will be described later with reference to FIG.

The partner analysis server 102 shown in FIG. 1 analyzes inquiry information received from the inquiry server 103, product selection in each inquiry, and performance information on partner selection. This analysis is shown in FIG. The information obtained from the partner computer 104 is compared with the performance information, and the comparison result is provided to the partner computer 104. The comparison results are shown in FIG. A configuration diagram of the partner analysis server 102 will be described later with reference to FIG.

The table layout used in the order sales introduction system shown in FIG. 1 is shown below. The table is created in the introduction information server 101, and the information is also stored in the introduction information server 101. When information is queried from the partner analysis server 102, it is acquired via the network.

FIG. 6 is a layout diagram of a table managed by the company information DB 213. The table includes items of contact information such as a company 601, a person in charge 602, an industry 603, an annual sales 604, an employee number 605, an address 606, a TEL 607, a FAX 608, and an email 609.
Row data as indicated by 610, 611, or 612 is stored.

FIG. 7 is a table layout diagram managed by the inquiry information DB 214. The table includes item No. 701, request date 702, company 703, inquiry category 704, delivery date 705, and budget 7.
There are items such as 06 and other items such as an inquiry condition 707 and remarks 708.
For example, row data such as 709 and 710 is stored.

FIG. 8 is a table layout diagram managed by the registered product DB 215. Table
It has items such as registration No. 801, product name 802, price 803, target 804, and remarks 805, and for example, row data such as 807, 808, and 809 is stored.

FIG. 9 is a table layout diagram managed by the partner information DB 216. The table includes items of a partner name 901, a registration number 902, and a weight 903, for example, 904
And row data such as 905 and 906 are stored. The total weight is 100 for one partner company.

FIG. 10 is a table layout diagram managed by the inquiry determination condition DB 217. The table includes inquiry contents 1001, priority 1 (1002), priority 2 (1003), and priority 3 (10
04), for example, row data such as 1005, 1006, and 1007 are stored.

FIG. 11 is a table layout diagram managed by the case response result DB 218. The table includes items of date 1101, item No. 1102, registration No. 1103, and partner 1104, and for example, row data such as 1105 and 1106 is stored.

FIG. 12 is a table layout diagram managed by the external information DB 219. The table includes items of a partner 1201, a content 1202, a schedule 1203, and a registration number 1204. For example, row data such as 1205, 1206, and 1207 is stored.

FIG. 13 is a table layout diagram managed by the inquiry determination result DB 221. The table includes items such as a case number 1301, a partner 1302, a person in charge 1303, and an availability flag 1304. For example, data such as row 1305 to row 1309 is stored. The same case will continue until the availability is “1”. Further, the determination result “1” means acceptable, and “0” means impossible.

FIG. 14 is a table layout diagram managed by the case record DB 222. The table includes items that occur at the time of an order such as an order date 1404 and an order amount 1405 in addition to the case number 1401, partner 1402, and order acceptance 1403, and further includes a user evaluation 1406 and personnel 1
It has an item of company evaluation value such as 407. For example, row data such as 1408 and 1409 is stored.

FIG. 2 is a configuration diagram of the introduction information server 101. The introduction information server 101 includes an inquiry information receiving unit 201, an inquiry information condition recognition unit 202, a product selection unit 203, a partner selection unit 204, a determination condition determination unit 205, a partner ranking processing unit 206, a corresponding determination processing unit 207, and a reply. The information update unit 208, the response information transmission unit 209, the partner schedule update unit 210, the case request notification unit 211, and the case response result reception unit 212 include a company information DB 213, an inquiry information DB 214, a registered product DB 215, and a partner information DB 216. Inquiry judgment condition DB2
17, the case response result DB 218, the external information DB 219, the partner schedule 220, the inquiry determination result DB 221, and the case result DB 222.

The inquiry information receiving unit 201 receives the inquiry information from the inquiry computer 103, and stores the inquiry source company information in the company information DB 213 and the inquiry information in the inquiry information DB 214.

The product selection unit 203 selects an applicable product from the registered product DB 215 based on the inquiry information.

The partner selection unit 204 selects a partner corresponding to the selected product as the partner information DB 216.
Is selected.

In the determination condition determination unit 205, the determination condition is determined in the inquiry determination condition DB 217 from the information of the inquiry classification 704 shown in FIG.

The partner ranking processing unit 206 extracts a point calculation method (which calculation method of steps 406, 408, and 410 in FIG. 4 is selected) from the inquiry determination condition DB 217 and performs a predetermined calculation. Calculate by method and rank the partners.

The correspondence determination processing unit 207 determines a partner company and a person in charge from the partner schedule 220. For example, information such as the case number “03-0001” in FIG. 13 is determined as the person in charge “Takahashi” of the partner company C.

The response information update unit 208 displays the result of the response determination processing unit 207 as the case response result DB 218.
To store. For example, the case number “03-0001” stores information that the registered company “S-0001” corresponds to the partner company C.

The response information transmission unit 209 returns the response information in the inquiry information to the inquiry computer 103. For example, in the inquiry from ABC company,
Since the registered product “S-0001” is selected and the person in charge “Takahashi” of the partner company C is in charge of the demonstration, information such as “Takahashi” is contacted.

In the partner schedule update unit 210, the partner schedule 220 is updated in order to make a reservation for the person in charge in the selected partner.

The case request notification unit 211 notifies the selected partner computer 104 of the case request. For example, in response to an inquiry from the ABC company to the partner company C, the project number “03-0001”
”Is notified to the person in charge“ Takahashi ”, such as a demonstration request for the registered product“ S-0001 ”, and event information for updating the partner schedule 220.

The case response result receiving unit 212 extracts the response result in the inquiry case from the inquiry computer 103 and stores it in the case response result DB 222.

The company information DB 213 stores detailed information of the inquiry source company. The table configuration is shown in FIG.

The inquiry information DB 214 stores detailed information in addition to the request date, inquiry classification, and budget as information relating to the inquiry. The table configuration is shown in FIG.

The registered product DB 215 stores product detailed information such as product names and prices of registered products. The table configuration is shown in FIG.

The partner information DB 216 stores products that each partner is working on and weights for the products. The table configuration is shown in FIG.

The inquiry determination condition DB 217 stores information for guiding the determination procedure according to the inquiry content. The table configuration is shown in FIG.

The case response result DB 218 stores information on the assigned registered products and selected partners in each inquiry case. The table configuration is shown in FIG.

The external information DB 219 stores information that refers to a specific part of a homepage that is preset by each partner. For example, registration No.
Information such as “S-0008” product seminar will be held on 2003/3/5. The table configuration is shown in FIG.

The partner schedule 220 is a file in which the activity schedule of the person in charge of each partner is input in a format specified at a specified location of each partner computer 104.

The inquiry determination result DB 221 stores history information in partner selection.
For example, in the case No. “03-0001”, when referring to the schedule of Okura of Company A according to the judgment criteria, the specified date is filled and it becomes impossible to deal with, and the history information such that correspondence is possible when Takahashi of Company C is examined next. Stored. The table configuration is shown in FIG.

In the case record DB 222, whether or not an order as a result of introducing a partner with respect to an inquiry and partner evaluation of the inquiry source are stored. For example, in response to an inquiry, after introducing a product or a partner, an order is received, and information such as the person in charge is good and the A evaluation is stored as a staff member of the order. The table configuration is shown in FIG.

  The processing procedure in the introduction information server 101 in FIG. 2 will be described later with reference to FIG.

FIG. 3 is a configuration diagram of the partner analysis server 102. The partner analysis server 102 includes a result information aggregation processing unit 301, a partner information extraction unit 302, a comparison processing unit 303, and a result notification unit 304. The case correspondence result DB 218, the inquiry determination result DB 221, the case result DB 222, and the partner information. Connected to DB 216.

The performance information totaling processing unit 301 extracts information from the case response result DB 218, analyzes the content of the case correspondence information in the inquiry, extracts information from the inquiry determination result DB 221, totals the partner selection history, Information is taken out and the project results after partner determination are compiled.

In the partner information extraction unit 302, the weighting information of the products that each partner is putting effort into is extracted from the partner information DB 216.

In the comparison processing unit 303, the result information output by the performance information totaling processing unit 301 is compared with the result information output by the partner information extracting unit 302. The comparison is calculated on the basis of the results of monthly aggregation, and the actual number of cases and success rate are calculated for the inquiry cases of products that each partner is focusing on. In addition, the number of frauds is calculated for each case. Next, the partner's correspondence evaluation content from the inquiry source is searched. Next, the ranking of the inquiry product by month cumulative is calculated.

The result notifying unit 304 outputs the result output from the comparison processing unit 303 to the designated format shown in FIG. 15 and notifies each partner computer 104 of the result. For example, as a result of a certain month, Partner A increases the weight of S-001 products, but the trend of the market is that the number of inquiries is 40. Product S-002 which is not 70
It can be found that there are cases of inquiries. This will provide data for revising the business action plan and considering reviewing the corresponding products. In addition, based on the response evaluation from the inquiry source, information to consider measures will be provided.

  The processing procedure of the partner analysis server in FIG. 3 will be described later with reference to FIG.

FIG. 4 is a flowchart showing a processing procedure in the introduction information server 101 shown in FIG.
At the end of the description of each process below, the number of each processing unit shown in FIG.

First, the inquired company information and inquiry contents are extracted from the company information DB 213 and the inquiry information DB 214 (401) (201).

The condition of the extracted content is recognized (402). In this process, the business type and annual sales are extracted from the company information DB 213, and the budget and inquiry conditions are extracted from the inquiry information DB 214 (
202).

Next, a product to be applied is selected in the registered product DB 215 from the extracted information (403
). In this process, a condition search and a concept search are used, and a product is selected by searching according to preset conditions (203).

A partner company corresponding to the selected product is searched from the partner information DB 216, and a partner company is selected (404). If a plurality of companies are selected in this process, the plurality of companies are listed (204).

Next, the query classification information is extracted from the query information DB 214, and the query determination condition DB2
From 17, the calculation priority order is determined (405). The inquiry classification information in the inquiry information DB 214 includes a product introduction request, a demo request, and a development work request, and a determination is made based on this information. In the case of a product introduction request, the process proceeds to step 406. If requesting a demo, step 408
Proceed to If it is a development work request, the process proceeds to step 410.

In the case of a product introduction request, first, the external information DB 219 is searched for event information of the product selected by the selected partner. A predetermined point is calculated for the search result (406). Next, the weighting information is extracted from the partner information DB 216, a predetermined point is calculated, and added to the point calculated in step 406 (407).

In the case of a demonstration request, first, the weight information of the selected product is extracted from the partner information DB 216, and a predetermined point is calculated (408). Next, the case response result DB2
From 18, it is searched whether there is a past record in the selected product, and a predetermined point is calculated and added to the point calculated in step 408 (409).

In the case of a development work request, first, in the selected product from the case response result DB 218,
It is searched whether there is a past record, and a predetermined point is calculated (410). Next, the external information DB 219 is searched for the event information of the product selected by the selected partner. A predetermined point is calculated as a search result and added to the point calculated in step 410 (411). Next, the weighting information is extracted from the partner information DB 216, a predetermined point is calculated, and added to the point calculated in step 411 (412) (20
6).

Of the three patterns, priorities are assigned to the partner companies listed in step 404 based on the points calculated by the calculation method indicated by the determination condition (413) (206
).

In the partner company with the highest priority, it is determined from the partner schedule 220 whether the person in charge can handle the requested date (414). If the response is possible, the process proceeds to step 415. If the response is not possible, the process returns to step 413 to determine whether the person in charge can respond to the requested date from the partner schedule 220 in the partner company with the second highest priority.

If the response is not possible, when the process returns to step 413, a process of counting failure is performed for each case according to the inquiry (419). In the counting process of step 419, it is used for counting the number of frauds for each partner (process 501 in FIG. 5). In the above process flow,
In order to make an inquiry to a partner, the schedule is referred to, but this count means the number of times that the schedule is filled and the case is sent to another partner on the desired date of inquiry. The determination contents are updated in the inquiry determination result DB 221 (207).

Next, the partner schedule 220 of respondable persons is updated (415) (210). Information such as the partner company, the person in charge, and the selected product is returned to the inquiry computer 103 (4
16) (208).

Next, the partner company 104 is transmitted (211) and requested (417) (209) to the partner company 104, the information updated in the partner schedule 220 in step 415 and information such as inquiry company information, inquiry contents, and selected products.

After answering the inquiry, information on the result is received from the inquiry computer 103, and the case result D
Update to B222 (418) (212). Thereby, the process is terminated.

FIG. 5 is a flowchart showing the processing procedure of the partner analysis server 102 shown in FIG. At the end of the description of each process below, the number of each processing unit shown in FIG.

First, information is extracted from the case response result DB 218, the inquiry determination result DB 221 and the case result DB 222, and the results information is aggregated by analyzing the inquiry information, totaling the selection results by partner, and totaling the results after introduction by partner (501). (301).

Next, the weight information of the corresponding product is extracted from the partner information DB 216 for each partner (
502) (302).

Compare the totals of results by partner and the weight of products currently supported (503) (3
03) The result is output for each partner (504) (304). As the output information, an arbitrary value is input and output in the standard format shown in FIG. This completes the process.

FIG. 15 is an example of an information screen transmitted from the partner analysis server 102 to the partner company 104. In the input fields 1501, 1502, and 1503, arbitrary values are input. In accordance with the condition of this value, the number of fraudulent times is output in addition to the number of introduction results and the success rate of orders for inquiries about products handled as shown in Table 1504. Further, as shown in Table 1505, the evaluation contents from the inquiry source by the actually corresponding case are output. Further, as shown in Table 1506, the best selling product information is output based on the entire inquiry information generated from the inquiry computer 103.

It is also possible to store a program for executing the order sales introduction method of the present invention described above in a computer-readable storage medium and read it into a memory for execution.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

In the second embodiment, based on the sales performance of the partner company and the like, the type of business that the partner company is good at is determined by a predetermined calculation formula. The purpose is to increase the number of inquiries to the inquiry computer 103 by acquiring the company information for the determined type of business from the homepage of each company and sending the product information to each company.

Further, by automatically performing the processing when an estimate request is made to the inquiry computer systematically, it is possible to make a quick estimate, thereby reducing opportunity loss.

In Example 1, the system is passively waiting for inquiries from companies,
The purpose of the second embodiment is to increase the number of inquiries to the inquiry computer 103 by dynamically determining a target company by a predetermined calculation formula and sending product information to the company.

The table layout used in the second embodiment will be described below. The table is created in the introduction information server 101. Information is exchanged from a server other than the introduction information server 101 via a network.

FIG. 22 is a layout diagram of a table managed by the target partner DB 1707. The table shows the partner company (2201), server address (2202), and target category (220).
3) and inquiry category (2204). A partner with “○” in the target category is a partner to be analyzed or a request partner for quotation. It is possible to determine what kind of inquiry is being made to the partner company dedicated server based on the inquiry classification. For example, 2205, 2206,
Row information such as 2207, 2208, and 2209 is stored. A partner whose target category is “O” and whose query category is “Matter” is an analysis target partner in the customer analysis server, and the current status indicates that it is the query status of the case.

FIG. 23 is a layout diagram of a table managed by the customer matter DB 1708. The table includes a company name (2231), a large classification code (2232), a medium classification code (2233), a small classification code (2234), and a case status (2205). For example, 2306, 2
Row information such as 307, 2308, 2309, and 2310 is stored.

FIG. 24 is a layout diagram of a table managed by the business category classification DB 1709. The table includes a classification type (2401), a classification code (2402), and a classification name (2243). Classification types are classified into large, medium and small. For example, row information such as 2404, 2405, and 2406 is stored.

FIG. 25 is a layout diagram of a table managed by the target industry DB 1710.
The table includes a determination flag (2501) and an industry classification name (2502). As for the storage order, row data is stored as 2503, 2504, 2505 in ascending order of determination flags.

FIG. 26 is a layout diagram of a table managed by the new customer DB 1712. The table includes company name (2601), annual sales (2602), number of employees (2603), and contact name (26
04), a FAX number (2605), and a mail address (2606). For example, 26
Row information is stored as 07, 2608, and 2609.

FIG. 27 is a layout diagram of a table managed by the estimation condition DB 1808. The table includes an estimate number (2701), an estimate row number (2702), a company name (2703), a registered product number (2704), the number of users (2705), an operation time (2706), and an answer delivery date (2707).
) And status (2708). The number of users stores the number of licenses for the registered product No. The answer delivery date stores the estimated answer delivery date. The status consists of acceptance, other decisions, waiting for responses, and responding to customers. For example, row information such as 2709, 2710, and 2711 is stored.

FIG. 28 is a layout diagram of a table managed by the corresponding partner DB 1809. The table shows an estimate number (2801), an estimate line number (2802), and a partner company (2803).
And availability (2804), status (2805), and correspondence (2806). Yes / No (28
"04)" is an item for storing whether or not the case can be handled as a result of inquiring to the partner company dedicated server. The status (2805) stores “in reply” or “answered”.
During reply, indicates that the estimate is being answered. Answered indicates that the estimate has been accepted. The item of correspondence (2806) indicates “○” to the partner who will deal with the case as a result.
"Is attached. For example, row information such as 2807, 2808, 2809, and 2810 is stored.

FIG. 29 is a layout diagram of a table managed by the partner check condition DB 1810. The table shows the partner company (2901), registered product number (2902), and level (2
903), a partition lower limit price (2904), and a corresponding level (2905). level(
2903) stores the level of the corresponding SE. The levels are A, B, and C. In the correspondence level (2905), the level of personnel capable of handling the registered product No. is stored. The levels are A, B, and C. For example, row information such as 2906, 2907, and 2908 is stored.

FIG. 30 is a layout diagram of a table managed by the estimation result DB 1811. The table shows registered product No (3001), estimated amount (3002), start (3003) and end (3
004), corresponding personnel (3005), and skills (3006). In the registered product, the product or SE classification is stored. The start (3003) stores the year and month when the case can be started. In the end (3004), the year and month when the case is scheduled to end is stored. The rank of the corresponding SE is stored in the skill. The ranks are A, B, and C. For example, 3007, 3008
, 3009 are stored.

FIG. 31 is a layout diagram of a table managed by the registered product price DB 1812. The table shows the partner company (3101), registered product number (3102), and number of users (3103).
), SPL (3104), partition lower limit (3105), and applicable level (3106). SPL is the price of the target product or SE cost. For the partition lower limit (3105), the lower limit value of the partition rate for the registered product No. of the partner is stored. Available level (31
06) stores the SE level that needs to be dealt with when the partner company constructs the product of the registered product No. The levels are A, B, and C. For example, 3107, 3108, 3109,
Row information such as 3110 and 3111 is stored.

FIG. 32 is a layout diagram of a table managed by the disclosure item DB 1904. The table includes company name (3201), registered product number (3202), major category (3203), and middle category (
3204), a small classification (3205), and a case status (3206). For example, 32
Row information such as 07, 3208, 3209, 3210, and 3211 is stored.

FIG. 33 is a layout diagram of a table managed by the disclosure schedule DB 1905. The table includes registered product No (3301), pre correspondence (3302), and construction correspondence (3303).
), Correspondence start (3304), and correspondence end (3305). Pre-compatible (330
2) stores the number of pre-sales personnel. In addition, construction is possible (3303
) Stores the number of personnel who can handle system construction. The ready start (3304) stores the date when the system construction work can be started. Available end (3305
) Stores the date on which the system construction work must be completed. For example, row information such as 3306, 3307, and 3308 is stored.

FIG. 16 is a system configuration diagram of the order sales introduction system in the embodiment of the present invention. As shown in FIG. 16, the customer analysis server 1601 is shown in FIG.
, An SI server 1602 and a partner company dedicated server 1603 are added. The customer analysis server 1601 shown in FIG. 16 acquires the case information of each partner company from the partner company dedicated server 1603.

  A method for obtaining the case information will be described later with reference to FIG.

Select the most suitable industry as a new business type from the obtained project information, collect information from each company website for companies belonging to the selected industry, and select companies that are worthy of disseminating information based on company size, annual sales, and number of employees. Select. A method for selecting a business type and a method for selecting a company worthy of information transmission will be described later with reference to FIG.

It has a mechanism to send product information of each partner company to the selected company to be newly developed, and to send information of the company to be newly developed to the partner company.

A configuration diagram of the SI server in FIG. 16 will be described later with reference to FIG. A configuration diagram of the partner company dedicated server 1603 in FIG. 16 will be described later with reference to FIG.

The customer analysis server 1601 and the SI server 1602 in FIG. 16 can be configured on the same server as the introduction information server 101.

FIG. 17 is a configuration diagram of the customer analysis server 1601. In the partner selection processing unit 1701, the user explicitly selects a target partner company from the screen, makes an inquiry to each partner company dedicated server 1603 of the company, and collects case information of the partner company. The matter information to be collected is matter information in the disclosure matter DB 1904 stored in the partner company dedicated server. The table configuration of the disclosure item DB 1904 is shown in FIG.

The collected results are stored in the customer matter DB 1708. The table configuration is shown in FIG. For information on target partner companies, see Partner company DB 1707.
To store. The table configuration is shown in FIG.

The partner case processing unit 1702 combines the customer case DB 1708 and the business category classification DB 1709, and performs a process of adding a weight to the business partner determination flag by weighting the target partner company's case by a predetermined formula. The table configuration of the industry classification DB 1709 is shown in FIG. With regard to weighting, it is possible to determine the types of industries that can demonstrate the strengths of the target partner companies by increasing the weight of the accepted cases.

The target business type selection processing unit 1703 uses the result of the business type determination flag calculated by the partner case processing unit 1702 to determine a business type having a value equal to or greater than a predetermined threshold value. The result of the industry type determination flag is stored in the target industry type DB 1710. The table configuration of the target industry DB 1710 is shown in FIG.

The company Web page search processing unit 1704 performs a keyword search of the company information Web page of each company using the industry type name in the target industry DB 1710 as a keyword. The search result is stored in the new customer DB 1712. The table configuration is shown in FIG.

The new customer information processing unit 1705 selects a company that is stored in the new customer DB 1712 and deserves information transmission by specifying the range of annual sales and the number of employees. The target company size is medium-sized / small-sized companies. As a result of the determination, the target company is stored in the new customer DB 1712.

The information transmission processing unit 1706 acquires the FAX number and the mail address from the company information of the new customer DB 1712, and transmits the product information of the target partner company. Product information and partner company information are collected by combining the company information DB 213, registered product DB 215, and partner information DB. In addition, information on new customers who have transmitted information is transmitted to the target company.

  FIG. 18 is a configuration diagram of the SI server 1602.

The estimate request acceptance processing unit 1801 performs processing for accepting an estimate request from the inquiry computer 103. The received estimate request information is stored in the estimate condition DB 1808. The table configuration is shown in FIG.

In the partner selection processing unit 1802, the registered product DB 215, the partner information DB 216, and the case result DB 222 are combined to acquire a partner company that handles the estimation target product and a partner company that has a track record corresponding to the case. The acquired result is stored in the corresponding partner DB 1809. The table configuration is shown in FIG. In the partner selection processing unit 1802,
An inquiry about the schedule is made to the partner company dedicated server 1603, and a partner that can handle the operation is selected. As a result of the inquiry, information on the partner company having an empty schedule is stored in the corresponding partner DB 1809.

The partner estimate processing unit 1803 transmits an estimate request to the partner company dedicated server 1603. Also, an estimate reply is received from the partner company dedicated server 1603.
The received estimate information is stored in the estimate result DB 1811. The table structure is shown in FIG.
0. Further, the partner estimate processing unit 1803 acquires the estimate condition from the partner from the estimate result DB 1811 for the estimate reply from the partner, and creates the partner check condition DB 1810 according to the condition to determine the validity of the estimate. Partner check condition D
The table configuration of B1810 is shown in FIG. The validity of the estimate is determined by the amount of money and the skills of the corresponding personnel. If it is determined that the estimate is valid, the process proceeds to the next process. N
In the case of G, an estimate request is made again to each partner company dedicated server 1603.

The estimate organizing processing unit 1804 adds the estimate added at the request source department to the estimate from the partner company, and prepares the form as the estimate for the customer. Estimate result DB18
11 is updated. Corresponding partner determination processing unit 1805 selects a corresponding partner based on the estimated amount of stock. The selected partner is stored in the corresponding partner DB 1809.

The result answer processing unit 1806 transmits the estimate of the finally prepared form to the customer. The estimate issuing unit 1807 also has a server 160 dedicated to each partner company that has requested the estimate.
The result (adopted, not adopted) is transmitted to 3.

FIG. 19 is a block diagram of the partner company dedicated server 1603. Schedule processing unit 190
1, a period in which a schedule inquiry from the SI server 1602 can be accepted and handled,
The number of personnel is acquired from the disclosure schedule DB 1905 and reported to the SI server 1602. The table configuration of the public schedule DB 1905 is shown in FIG.

The information reception processing unit 1902 receives information transmission from the customer analysis server 1601 and the SI server 1602. In addition, according to the received contents, a process of delivering information to the schedule transmission unit 1901 or the existing case information processing unit 1903 is performed.

In response to an inquiry from the customer analysis server 1601, the existing case information processing unit 1903 acquires case information from the public case DB 1904 and transmits information to the customer analysis server 1601. The table configuration of the disclosure item DB 1904 is shown in FIG.

FIG. 20 is a flowchart showing a processing procedure in the customer analysis server 1601 shown in FIG. At the end of the description of each process below, each process is performed.
The number of each processing unit shown in () is shown in ().

First, the user explicitly selects a partner to be analyzed from the screen (2001). The range of the partner to be analyzed can be specified (1701).

The server information of the partner company selected in the process 2001 is extracted from the target partner DB 1707, and the inquiry of the case information is executed to each partner company dedicated server 1603. In addition, the acquired information is stored in the customer matter DB 1708 and proceeds to the next processing (2002) (170
2).

Next, weighting is performed according to a calculation formula already determined for the accepted case in the acquired information, the result is added to the determination flag, and the process proceeds to the next process (2003). Among the acquired information, weighting is performed according to an already determined calculation formula for the type of business that is being dealt with and the business that has been lost, and the result is added to the determination flag (2004). The target industry is determined using the determination flag as a result of the completion of the weighting process (2005). Target industries are those that exceed a certain threshold. The threshold value is a value that is already determined internally. If one or more target industries are determined, the process proceeds to processing 2007. When the target industry is 0, the weighting factor of the weight calculation formula already determined is automatically increased, and the process 2003 and process 2004 are performed again to determine the target industry (2006) (1703).
.

In processing 2007, the business category name determined as the target business category is converted into the target business category DB1.
Each company homepage is retrieved using the business category name as a search key. The information to be searched is customer name, annual sales, number of employees, window name, FAX number, e-mail address (2
007). For the company that acquired the information, in process 2008, the new customer DB 1712
(2008) (1704).

Next, it is determined according to the already determined conditions whether the processing company scale is appropriate. The item to be judged is whether it is a medium-sized company with annual sales and the number of employees (2009). If the result of determination is OK, the product information of the target partner company is sent to the customer (2010).
(1706). In addition, the customer information sent to the partner company dedicated server is sent customer information, and the process is terminated (2011) (1705). If the determination is NG, the new customer DB 1712 is updated and the process ends (2012).

FIG. 21 is a flowchart showing a processing procedure in the SI server 1602 shown in FIG. At the end of the description of each process below, the number of each processing unit shown in FIG.

First, an inquiry request information from a customer is received from the inquiry computer 103 (21
01) (1801).

Next, a partner list is created by selecting a partner who can respond from the product information for which an estimate request has been received. The partner selection method is obtained by combining the estimate condition DB 1808 and the registered product DB 215 or the case record DB 222. The acquired result is stored in the corresponding partner DB 1809 (2102).

Next, from the corresponding partner DB 1809, the partner company dedicated server 1603 is inquired of the schedule to obtain a partner who can respond. The corresponding partner DB 1809 is updated based on the acquired result (2103) (1802).

Next, information on the partner that has become available is acquired from the corresponding partner DB 1809, an estimate request is sent to the partner company dedicated server 1603, and the process proceeds to the next process (2104).

In process 2105, an estimate reply from the partner dedicated server 1603 is received. The accepted estimate response result is stored in the estimate result DB 1811. (1803)
In process 2106, the partner condition DB 1810 is created by combining the estimated condition DB 1808, the corresponding partner DB 1809, and the registered product price DB 1812.

Partner check condition DB 1810 partition lower limit price (2804) and estimate result DB 181
If the estimated price of 1 is compared and the price is below the partition lower limit price, it is determined that the estimate is not valid. Also,
Correspondence level (2805) of partner check condition DB 1809 and estimation result DB 181
Compare the skill (3006) in the column where the registered product number 1 (3001) of “1” is “SE”, and if the available level (2805) of the partner check condition DB 1809 is large, it is determined that the estimate is not valid ( 2106).

If it is determined that the estimate is valid, processing such as summing up responses from other partners is performed (2108). If it is determined that the estimate is not valid, a re-estimation request is made (2107). After organizing all quotes, determine the combination with the smallest quote amount,
Proceed to the next processing (2109) (1805).

  In process 2110, estimate information is sent to the customer and the process proceeds to the next process (1807).

Next, processing is performed to send the estimated information submitted to the customer to the partner whose response is OK (2111). Information indicating that it has been determined to another partner is sent to the partner whose response is NG (2112) (1806).

It is also possible to store a program for executing the order sales introduction method of the present invention described above in a computer-readable storage medium and read it into a memory for execution.

DESCRIPTION OF SYMBOLS 101 ... Introduction information server, 102 ... Partner analysis server, 103 ... Inquiry computer, 104 ... Partner company, 105 ... Network, 201 ... Inquiry information receiving part, 202 ... Inquiry Information condition recognition unit, 203 ... Product selection unit, 204 ... Partner selection unit, 205 ... Determination condition determination unit, 206 ... Partner ranking processing unit, 207 ... Correspondence determination processing unit, 208 ... Reply information update unit, 209 ... Reply information transmission unit, 210 ... Partner schedule update unit, 211 ... Case request notification unit, 212 ... Case response result reception unit, 213 ... Company information DB, 214 ... inquiry information DB, 215 ... registered product DB, 216 ... partner information DB, 217 ... inquiry judgment condition DB, 218 ... plan Corresponding result DB, 219 ... External information DB, 220 ... Partner schedule, 221 ... Inquiry determination result DB, 222 ... Case result DB, 301 ... Result information totaling processing unit, 302 ... Partner information retrieval unit, 303 ... comparison processing unit, 304 ... result notification unit, 1601 ... customer analysis server, 1602 ... SI server, 1603 ... partner company dedicated server, partner selection processing unit 1701, Partner project processing unit ... 1702, Target industry selection processing unit ... 1703, Company Web page search processing unit ... 1704, New customer information processing unit ... 1705, Information transmission processing unit ... 1706, quotation request reception processing unit ... 1801, partner selection processing unit ... 1802, partner estimation processing unit ... 1803, estimation adjustment Processing unit ... 1804, Corresponding partner determination processing unit ... 1805, Result reply processing unit ... 1806, Estimate issuing unit ... 1807, Schedule processing unit ... 1901, Information reception processing unit ... 1902, existing case information processing unit 1903

Claims (8)

Means for receiving an order via the network, means for extracting a provision destination corresponding to the accepted order, means for inquiring the provision destination whether or not provision is possible, means for counting the number of inquiries, and as a result of the inquiry, provision is possible Alternatively, the sales order introduction system, characterized in that it has means for counting the number of times it cannot be provided, and means for comparing the count for each destination. Via the network, means for distributing the number of case introductions according to the inquiry for each provider and the comparison result for each provider, and means for distributing the correspondence evaluation from the supplier to the provider for each provider; 2. The order sales introduction system according to claim 1, further comprising means for distributing the current inquiry status to each provider. Means for collecting partner company's case information via the network, means for selecting a company's industry to send information from the collected case information, means for collecting company information of a company corresponding to the selected company's industry, An order sales introduction system comprising: means for selecting collected company information; and means for transmitting product information with respect to the selected company information. Means for accepting an estimate request via the network, means for selecting a corresponding partner company from the received contents, means for judging the validity of an estimate reply from the selected partner company, and an estimate reply from the partner company And a means for selecting a corresponding partner company based on the sorted estimate response. Means for collecting the schedule of each partner company via the network, means for collecting the case information of each partner company, means for accepting an estimate response of each partner company, and means for managing communication of information with each partner An order sales introduction system characterized by having. Collecting case information of partner companies via the network, selecting the type of company that sends information from the collected case information, collecting company information of companies corresponding to the selected type of company, and collecting the collected company information Order sales introduction method, wherein product information is transmitted to the selected company information. Accepting an estimate request via the network, selecting a corresponding partner company from the received content, determining the validity of the estimate answer from the selected partner company, organizing the estimate answer from the partner company, A sales order introduction method characterized by selecting a corresponding partner company based on the arranged estimate responses.   Collects the schedule of each partner company via the network, collects case information of each partner company, accepts estimate responses of each partner company, and communicates information with each partner based on the schedule, case information and estimate answer Order sales introduction method characterized by performing.

Images