JP2014032599A - Replacement suggestion support system - Google Patents

Abstract

Provided is a list of candidates for replacement proposals at appropriate timing according to customer characteristics, and supports appropriate replacement proposals.
A maintenance information registration processing unit for registering maintenance work information for each product and customer characteristic information for each customer by executing a program in an information processing unit of the server, and product information before and after product replacement Replacement information registration processing section for registering replacement reason information, product replacement results and reasons, maintenance work information summarizing information by type and customer characteristics by type, summary results and customer alarms It has a replacement proposal customer candidate extraction processing unit for extracting customer candidates based on the amount of money. The extraction processing unit provides an appropriate replacement proposal customer candidate for the product according to the customer characteristics by referring to the result totaling by the type-specific customer characteristic totaling processing unit and the status of the product solid being maintained.
[Selection] Figure 1

Description

  The present invention relates to a replacement proposal support system, and in particular, it is difficult to collect a consistent maintenance history, and there is a large difference in replacement timing depending on the customer. The present invention relates to a system for grasping and realizing it.

  In recent years, it has been proposed to manage facility equipment by reading or writing an IC tag storing maintenance management data using an IC tag reader / writer. For example, in Patent Document 1, a display function using a display and an input device for key input are omitted by using a mobile phone, which can be manufactured at low cost, and is advantageous for downsizing. / A facility equipment management system using a writer is disclosed.

  Kitchen facilities are often resold and in some cases may pass through multiple customers before being discarded. For this reason, there is a difference in timing between the replacement proposal timing for a customer who has newly purchased a certain product and the replacement proposal timing for a customer purchased through resale. This difference is often perceived by the person in charge of sales activities with a sense and dealt with individually. As a result, the customers or products that should be replaced are missed, and the appropriate replacement proposal timing is lost.

  Further, Patent Document 2 discloses a life cycle management system that can rationalize judgment and processing procedures when a product or its parts are recycled or discarded. This is for “processing at the time of collection” and “processing for reliability evaluation” of the product or its parts, and does not take into account the replacement timing for each customer characteristic for the product distributed in the market by resale. That is, even when the technique of Patent Document 2 is applied, the problem from the business viewpoint regarding the replacement proposal of the kitchen facility with high resale frequency cannot be solved.

JP 2008-46755 A JP 2000-48066 A

  The object of the present invention is to provide a list of replacement proposal customer candidates at appropriate timing according to customer characteristics based on the shipment information and consistent maintenance information of individual products, and reach the replacement proposal timing required at the time of business. This makes it possible to check the product solids and to enable appropriate replacement proposal support.

The present invention is preferably implemented using a computer system including an information processing unit that executes a program to process information, a server having a database (DB) for storing information, and a terminal connected to the server. In the product replacement proposal support system, the information processing unit
Pre-shipment information registration processing section for registering customer characteristic information and product specific information for each product type, maintenance information registration processing section for registering maintenance work information for each product type and customer characteristic information for each customer, and product replacement A replacement information registration processing unit for registering previous and subsequent product information and replacement reason information, a result and reason for product replacement, and a totaling processing unit for each customer characteristic by type for summarizing maintenance work information by type and customer characteristic; Replacement proposal customer candidate extraction processing unit that extracts customer candidates based on the summation results and customer alarm amount, and replacement proposal customer selection registration processing unit that selects target customers from the extracted customer candidate list and associates sales representatives Have
The extraction processing unit provides an appropriate replacement proposal customer candidate for the product solid according to the customer characteristic by referring to the result total and the maintenance of the product solid under the maintenance by the type-specific customer characteristic totaling processing unit It is configured as a replacement proposal support system characterized by this.

  In a preferred example, the extraction processing unit totals the product standard unit prices of a plurality of products determined to be the replacement proposal timing for each customer, and the total value for each customer uses an alarm amount set in advance for each customer. If the number of customers exceeds, a list of replacement candidate customers is provided.

According to the present invention, the sales staff can easily grasp whether each product individual has reached the replacement proposal timing according to the customer characteristics. As a result, it is possible to reduce oversight of a product solid to be replaced and to propose replacement at an appropriate timing.
In addition, since the customers who have reached the preset alarm amount are listed, the sales representative can grasp the customer of the appropriate replacement proposal amount scale, not the individual product unit. As a result, it is possible to reduce oversight to customers to be replaced and to propose replacement at an appropriate timing.

The figure which shows the whole structure of the replacement proposal assistance system by one Embodiment of this invention. The processing flowchart of the pre-shipment information registration processing unit 103 in one embodiment. The processing flowchart of the maintenance information registration process part 104 in one Embodiment. The processing flowchart of the replacement information registration process part 105 in one Embodiment. The process flowchart of the total process part 106 classified by type customer characteristic in one Embodiment. The processing flowchart of the extraction proposal customer candidate extraction processing unit 107 in one embodiment. The process flowchart of the selection registration process part 108 of the replacement proposal customer in one Embodiment. The figure which shows the table structural example of customer characteristic information DB in one Embodiment. The figure which shows the table structural example of product solid information DB in one Embodiment. The figure which shows the table structural example of customer information DB in one Embodiment. The figure which shows the table structural example of maintenance work information DB in one Embodiment. The figure which shows the table structural example of the replacement information DB in one Embodiment. The figure which shows the table structural example of replacement reason DB in one Embodiment. The figure which shows the table structural example of the maintenance total information DB in one Embodiment. The figure which shows the table structural example of reason summary information DB in one Embodiment. The figure which shows the screen of the replacement proposal customer selection in one Embodiment.

Hereinafter, the best mode for carrying out the present invention will be described in detail with reference to the drawings.
FIG. 1 shows the overall configuration of the replacement proposal support system.
The replacement proposal support system is configured by a computer system including a server 101 and a terminal connected thereto. A replacement proposal support system 102 is constructed in the server 101. The server 101 is connected to a terminal 122 such as a PC (personal computer) used by the product manager of the new product registration / shipment 118 via the WAN / LAN. The server 101 is connected via the Internet to a mobile terminal 123 such as a mobile phone used by the maintenance staff of the maintenance 119 who often contacts the customer, and a terminal 125 used by the sales staff of the replacement proposal 120. . Here, the terminal 123 includes an IC tag reader 124 that reads information (IC tag number / product number, product model name, shipping date (details will be described later)) of the IC tag attached to the product. Transmits the information read by the IC tag reader 124 to the server 101 via the Internet.

The replacement proposal support system 102 includes a database for storing information (hereinafter simply referred to as DB) and an information processing unit that performs information processing.
The information accumulation DB includes a customer characteristic information DB 109 for accumulating customer characteristic information such as the presence / absence of listing, the number of stores, and an average customer unit price, and an IC tag number / product number and product type of an IC tag attached to a product individual Product information DB 110 that stores information for identifying the product, such as name and shipment date, customer information DB 111 that stores information about the customer such as company code, company name, sales representative, maintenance date and maintenance type, Maintenance work information DB 112 that accumulates information related to maintenance work such as maintenance contents, replacement information DB 113 that accumulates replacement performance information such as IC tag numbers / manufactured numbers and replacement dates before and after replacement, and aging Replacement reason information DB 114 for accumulating information on reasons for replacement such as changes in functions, strategy changes, etc., and average number of months elapsed by customer characteristics by model Maintenance summary information DB 115 for accumulating the results of summing up the average maintenance frequency, average maintenance cost, etc., and reason summary information DB 116 for accumulating the results of summarizing the number of aging, function improvement, strategy change, etc. by customer characteristics by model It is configured.

  The information processing unit is a functional unit realized by executing a program on a processing device (CPU) possessed by the server. The pre-shipment information registration processing unit 103 registers customer characteristic information and product individual information for each model. A maintenance information registration processing unit 104 for registering maintenance work information for each product and customer characteristic information for each customer, a replacement information registration processing unit 105 for registering product information before and after replacement and replacement reason information, Results, reasons, and maintenance work information by type and by customer characteristics, and a total processing unit 106 by type and customer characteristics, and a replacement proposal customer candidate extraction process that extracts customer candidates based on the total result and the alarm amount of the customer And a replacement proposal customer selection / registration processing unit 108 for selecting a target customer from the extracted customer candidate list and associating with a sales representative. It is.

Next, configuration examples of the DBs 109 to 116 will be described with reference to FIGS.
The customer characteristic information DB 109 shown in FIG. 8 shows each of the product type that represents the product type to be specified for the customer characteristic, the characteristic item that becomes the customer characteristic, and the item value that can be selected from the characteristic items for each type. Register information. The characteristic item is information indicating the characteristic of the customer, such as presence / absence of stock listing, number of stores, average customer unit price, and the like.

  The product individual information DB shown in FIG. 9 includes an IC tag number / manufacturing number that identifies a product individual, a product model that represents the product model, a shipment date that indicates the date of shipment of the product individual, and a replacement proposal A replacement flag indicating whether or not there is a replacement proposal candidate for a candidate product individual, a company code indicating a company that owns the product individual, a product standard unit price indicating a standard unit price of the product at the time of shipment, and a product individual Each piece of information indicating a discard flag indicating the presence / absence of discard is registered. The replacement flag “1” indicates that there is a replacement candidate, and “0” indicates that there is no replacement candidate. When the discard flag is “1”, it is discarded, and “0” indicates that it is not present.

The customer information DB shown in FIG. 10 includes a company code, a company name / company name indicating a business entity name, presence / absence of listing, the number of stores, an average customer unit price, a replacement flag indicating a candidate for a replacement proposal, An alarm amount indicating the total threshold of the product standard unit price of a product individual with a replacement flag held by the customer, indicating that the sales are determined to be replacement proposal customers from among customers with replacement flags that are replacement proposal customer candidates Each information indicating a proposal flag and a sales representative indicating the sales representative of the customer determined to be a replacement proposal customer is registered.
Here, the presence / absence of listing, the number of stores, and the average customer unit price are selected from the characteristic items of the customer characteristic information DB 109. A proposal flag “1” indicates that there is a proposal, and “0” indicates that there is no proposal.

  The maintenance work information DB shown in FIG. 11 includes an IC tag number / manufactured number, a company code, a maintenance date that indicates the date when the maintenance work was performed, a maintenance type that indicates the type of maintenance work, a maintenance content that indicates the content of the maintenance work, and maintenance. Each piece of information indicating the maintenance cost indicating the amount charged for the work is registered.

  The replacement information DB shown in FIG. 12 includes a replacement number that identifies a replacement, an IC tag number before replacement that identifies a product individual before replacement / manufactured number, a product model before replacement that indicates the model of the product individual before replacement, Each information indicating the IC tag number / product number after replacement for specifying the product individual, the product model after replacement indicating the product model after replacement, and the replacement date indicating the date of replacement is registered.

The replacement reason DB shown in FIG. 13 is a function used to count the number of replacement reasons, the aging flag used for counting the number of replacement reasons, the aging flag used for counting the number of reasons for aging, the reason for aging, and the like. Improvement flag, improvement comment explaining the reason for improvement, strategy change flag used to count the number of reasons for replacement, strategy change comment explaining the reason for strategy change, other flags used to count the number of reasons for replacement, etc. Each piece of information indicating other comments explaining the reason is registered.
Here, each flag “1” indicates that there is target information, and “0” indicates that there is no information.

  The maintenance tabulation information DB shown in FIG. 14 includes the product type, presence / absence of listing, the number of stores, average customer unit price, replacement date, the total number of products that have been shipped, and the average from the beginning of shipment of the products. Each piece of information indicating the average number of elapsed months indicating the number of months, the average number of maintenance times indicating the number of maintenance from the beginning of the product individual, and the average maintenance cost indicating the amount charged for maintenance work is registered.

Here, the product type, the presence / absence of listing, the number of stores, and the average customer unit price are information acquired corresponding to the IC tag / product number in the maintenance work information DB 112. The total number is information calculated based on the IC tag / product number in the maintenance work information DB 112.
The average maintenance count is the number of months calculated from the shipping date of the product individual information DB 110. The average maintenance frequency and average maintenance cost are calculated from the maintenance work information DB 112.

  The reason summary information DB shown in FIG. 15 includes information indicating the product type, listing presence, number of stores, average customer unit price, replacement date, total number of units, number of aging, number of functional improvements, number of strategy changes, and other numbers. Register. These pieces of information are acquired from the replacement information DB 113.

FIG. 2 is a flowchart showing the processing operation of the pre-shipment information registration processing unit 103 for registering customer characteristic information and product individual information by type. This process is executed after a new product is determined and before shipping.
The customer characteristic master registration by model S201 registers information such as the presence / absence of listing, the number of stores, and the average customer unit price in the customer characteristic information DB 109 for each product type.

  The product solid information registration S202 registers information for identifying the product solid, such as the IC tag number / product number, the product model name, and the shipping date, in the product solid information DB 110 before the product solid is shipped. At this time, considering that the kitchen equipment is frequently resold, and that the kitchen equipment may be difficult to identify due to dirt during use and the installation environment, the IC tag is attached to the product body at the time of shipment. At the time of maintenance information registration processing (described later with reference to FIG. 3), the IC tag attached to the product is read by the IC tag reader provided in the portable terminal 123 so that the product solid can be easily identified. It is desirable to keep it.

FIG. 3 is a flowchart showing the processing operation of the maintenance information registration processing unit 104 for registering maintenance work information for each product and customer characteristic information for each customer. This process is executed after arrival at the maintenance staff.
Product specific and customer identification S301 reads the IC tag affixed to the product with the IC tag reader 124 of the portable terminal 123, and holds the corresponding product solid from the information in the customer information DB 111 and product solid information DB 110 and the same. Identify customers.

  In the maintenance work information registration S302, after the maintenance staff arrives at the maintenance site, information related to the maintenance work such as the maintenance date, the maintenance type, and the maintenance content is registered in the maintenance work information DB 112. At this time, if the customer is different from the previous maintenance due to resale or the like, the company code of the customer who owns the product solid at that time is registered in the product solid information DB 110.

  In the customer property information registration S303, the customer property information DB 306 selects the corresponding customer property from the customer property options registered for each product type, and registers them in the customer information DB 309. However, this does not apply if customer characteristics for the customer have already been registered and there is no need to change them.

  FIG. 4 is a flowchart showing the processing operation of the replacement information registration processing unit 105 for registering product information before and after replacement and replacement reason information. This processing is executed after the replacement order is confirmed or after the sales representative acquires information on replacement or disposal of other companies.

A product solid selection S401 selects corresponding product solid information from the product solid information DB 404.
The replacement product information registration S402 registers information regarding replacement results such as IC tag numbers / manufactured numbers and replacement dates before and after replacement for the selected product individual information in the replacement information DB 405. If the product solid is discarded, the presence of a discard flag is registered in the product solid information DB 406.
The replacement reason information registration S403 registers information on the reason for replacement such as aging, function improvement, and strategy change related to the replacement information for the selected product individual information in the replacement reason DB 114.

FIG. 5 is a flowchart showing the processing operation of the type-specific customer characteristic totaling processing unit 106 that totalizes the replacement results, reasons, and maintenance work information by type-specific customer characteristics. This process is executed at a regular timing when the aggregation process is required.
In the acquisition of target period S501, the target period of aggregation set in the system as a parameter is acquired.
The target product type extraction S502 extracts the product type existing in the replacement information DB 517 in the acquired target period.

The process S503 for determining whether there is a product type to be processed determines whether or not there is an unprocessed product type when the extracted product types are processed in order. As long as there is an unprocessed product type as a result of the determination, the processes of S504 to S512 are repeatedly executed.
Extraction of IC tag information of the target period / model S504 extracts from the replacement information DB 519 the model type and replacement date before replacement: IC tag number / product number. At that time, the company code that holds the product solid is also extracted from the product solid information DB 518 using the corresponding IC tag number / product number.

Target customer characteristic extraction S505 uses the extracted company code to extract a customer characteristic pattern comprising a combination of presence / absence of listing, number of stores, and average customer unit price from the customer information DB 520. Furthermore, the summary information of the customer characteristic pattern for each type of replacement year and month that is the target of the processing of S507 to S512 is created from the extraction result.
The process S506 of whether there is a customer characteristic to be processed determines whether or not an unprocessed customer characteristic pattern exists when the summary information of the created customer characteristic pattern is sequentially processed. As long as an unprocessed customer characteristic pattern exists as a result of the determination, the processes of S507 to S512 are repeatedly executed.

The replacement reason extraction S507 extracts an aging flag, a function improvement flag, and a strategy change flag from the replacement reason DB 114 using the extracted IC tag number / product number.
Calculating the number of reasons (aging, function improvement, strategy change) S508 calculates the number of totals, number of aging, number of function improvements, number of strategy changes, and other numbers by customer characteristics by replacement year by type using the extracted flags To do.

The number of reasons (aging, function improvement, strategy change) registration (monthly) S509 is the total number of totals by customer characteristics by replacement year by month, the number of aging, the number of function improvements, the number of strategy changes, the number of others, The record is registered in the corresponding monthly record in the reason summary information DB 116.
Maintenance information extraction S510 extracts maintenance content and maintenance cost from the maintenance work information DB 112 using the extracted IC tag number / product number. Further, the shipping date is extracted from the product solid information DB 110.

The average value calculation S511 of elapsed months, maintenance times, and maintenance costs uses the extracted maintenance and shipping date information to calculate the total number, average elapsed months, average maintenance times, Calculate the average maintenance cost.
The average elapsed months, average number of maintenance times, and average maintenance cost registration (by month) S512 calculates the total number, average elapsed month, average number of maintenance times, and average maintenance cost for each customer type by replacement year by month. Register in the monthly record in the information DB 115.

The calculation of the total number of reasons for each type of customer characteristic S513 is executed after the registration of the number of reasons (aging, function improvement, strategy change) (monthly) to the monthly records in S509 is completed. Here, the monthly records for each type of customer characteristic are extracted from the reason summary information DB 116, and the total number for each type of customer characteristic is calculated from the information.
The registration of the total number of reasons for each customer characteristic by model type S514 is the total record of the calculated customer characteristics by type, the number of aging, the number of function improvement, the number of strategy changes, and the other number in the total record of the reason totaling information DB 116. sign up.

The maintenance average value calculation S515 for each type of customer characteristic is executed after all the registration to the monthly record in S512 is completed in the registration of average elapsed months, average maintenance frequency, average maintenance cost (monthly) S512. Here, a monthly record for each type of customer characteristic is extracted from the maintenance summary information DB 115, and a total value and an average value for each type of customer characteristic are calculated from the information.
In the maintenance average value registration S516 for each customer characteristic for each model, the calculated total number, average number of elapsed months, average number of maintenance times and average maintenance cost for each customer characteristic for each model are registered in the average record of the maintenance total information DB 115. .

FIG. 6 shows a flowchart of the processing operation of the replacement proposal customer candidate extraction processing unit 107 that extracts a customer candidate based on the tabulation result and the alarm amount of the customer. This process is executed after the completion of the process by the type-specific customer characteristic-specific tabulation processing unit 106.
Extraction of product solid information without a discard flag S601 extracts information without a discard flag from the product solid information DB 611. In addition, all information is registered in the product solid information DB 622 as no replacement flag.

The processing target product solid presence S602 determines whether or not there is an unprocessed product individual when sequentially processing the extracted product individual information. As long as there is an unprocessed product as a result of the determination, the processes of S603 to S605 are repeatedly executed.
Calculation of Elapsed Months, Maintenance Counts, and Maintenance Costs by Product Individual In step S603, information on the corresponding product individual is extracted from the maintenance work information DB 112, and the total of the maintenance counts and maintenance costs is calculated. Further, the shipping date is extracted from the product solid-state information DB 110, and the number of elapsed months is calculated.

Maintenance average value exceeded S604 indicates the calculated elapsed month number, maintenance frequency, and maintenance cost of the corresponding product, the average elapsed month number of the average value record for each type of customer characteristic in the maintenance summary information DB 115, and average maintenance. The number of times is compared with the average maintenance cost, and it is determined whether at least one exceeds the average value.
In step S605 for registering a product solid replace flag, the product solid determined to exceed the average value is registered in the product solid information DB 110 as having a replace flag.

In step S606, extraction of customers with flagged product solids, information with a replacement flag is extracted from the product solid information DB 110, and customer information with product solids is extracted from the customer information DB 111. In addition, all information is registered in the customer information DB 111 as no replacement flag.
The processing target customer presence S607 determines whether or not there is an unprocessed customer when the extracted customer information is sequentially processed. As long as there are unprocessed customers, the processes of S608 to S610 are repeatedly executed.

In the total calculation of product standard unit price with flag for each customer S608, the product standard unit price with a replacement flag for each customer is extracted from the product individual information DB 110, and the total for each customer is calculated.
In the alarm amount surplus S609, the calculated unit price total amount is compared with the alarm amount for each customer in the customer information DB 111, and it is determined whether or not the sum is exceeded.
In the customer replacement flag registration S610, the customer information DB 111 is registered with a replacement flag for the customer determined to have exceeded the amount.

FIG. 7 shows a flowchart of the processing operation of the replacement proposal customer selection / registration processing unit 108 that selects a target customer from the extracted customer candidate list and associates sales representatives. This processing is executed after the processing by the replacement proposal customer candidate extraction processing unit 107 is completed. A screen for executing the processing is shown in FIG.
The extraction / display of the customer with the replacement flag and the product solid S701 extracts the customer with the replacement flag from the customer information DB 111 and displays the list on the terminal 125 on the screen. In addition, customer-specific product individual information with a replacement flag is also extracted from the product individual information DB 110 and a list is displayed on the terminal 125 on the screen.

  The extraction / display of the maintenance average value by model and the total number of reasons for replacement S702 is performed for the selected product, the total number of records for averaging and the average number of elapsed months from the maintenance total information DB 115 that match the model and customer characteristics, The average maintenance frequency and average maintenance cost are extracted and displayed on the screen. At the same time, the total number of records for summation, the number of aging, the number of function improvements, the number of strategy changes, and the number of other records are extracted from the reason totaling information DB 116 and displayed on the terminal 125.

Selection of target customer for replacement proposal S703 is based on the information displayed in the extraction / display S701 of customers and product solids with replacement flags, and the maintenance average value by type and extraction / display of the total number of replacement reasons S702. A check mark is added to the customer who is determined to be the target customer of the replacement proposal, and the information is held on the terminal 125 on the screen.
In the sales representative selection step S704, if the sales representative is not associated with the checked customer, the sales representative is selected and the information is stored on the screen.

  In step S705 for registering a proposal flag to a replacement proposal customer, a customer with a check mark registered in the customer information DB 111 with a check mark stored in the selection target customer S703 for replacement proposal is registered in the customer information DB 111. In addition, the sales representative information added in the sales representative selection S704 is also registered.

101: server 102: replacement proposal support system 122, 125: terminal 123: portable terminal 124: IC tag reader 103: pre-shipment information registration processing unit 104: maintenance information registration processing unit 105: replacement information registration processing unit 106: customer characteristics by type Separate aggregation processing unit 107: Extraction processing unit 108: Selection registration processing unit 109: Customer characteristic information DB 110: Product individual information DB 111: Customer information DB
112: Maintenance work information DB 113: Replacement information DB 114: Replacement reason information DB 115: Maintenance total information DB 116: Reason total information DB

Claims (3)

An information processing section for processing information by executing a program, a server having a database (DB) for storing information, and a product replacement proposal support system realized using a computer system including a terminal connected to the server In
The information processing unit executes the program to
Pre-shipment information registration processing section for registering customer characteristic information and product specific information for each product type, maintenance information registration processing section for registering maintenance work information for each product type and customer characteristic information for each customer, and product replacement A replacement information registration processing unit for registering previous and subsequent product information and replacement reason information, a result and reason for product replacement, and a totaling processing unit for each customer characteristic by type for summarizing maintenance work information by type and customer characteristic; Replacement proposal customer candidate extraction processing unit that extracts customer candidates based on the summation results and customer alarm amount, and replacement proposal customer selection registration processing unit that selects target customers from the extracted customer candidate list and associates sales representatives Have
The extraction processing unit provides an appropriate replacement proposal customer candidate for the product solid according to the customer characteristic by referring to the result total and the maintenance of the product solid under the maintenance by the type-specific customer characteristic totaling processing unit A replacement proposal support system characterized by this. The extraction processing unit totals the product standard unit prices of a plurality of products determined to be the replacement proposal timing for each customer, and the total value for each customer exceeds the alarm amount set in advance for each customer. 2. The replacement proposal support system according to claim 1, wherein the customer is provided as a list of replacement proposal customer candidates. As the DB,
A product type representing a product type to be designated for customer characteristics, a customer characteristic information DB for registering information on characteristic items to be customer characteristics,
Product information that identifies product individual, product type that represents product type, time information that indicates when the product was shipped, information about replacement proposals for product candidates that are candidates for replacement, and product individuals A product individual information DB for registering each information indicating company information indicating a company that is operating, a product standard unit price indicating a standard unit price of a product at the time of shipment, and the presence or absence of disposal of the individual product,
Company information, average customer unit price, replacement flag information as a candidate for replacement proposal, alarm amount indicating the total threshold of product standard unit price of individual product regarding replacement flag information owned by customer, replacement as replacement candidate customer candidate Customer information for registering each information indicating proposal information indicating that the sales are customers who are determined to be replacement proposal customers from among the customers related to flag information, and sales representatives indicating sales representatives of customers determined to be replacement proposal customers. DB,
Product information, company information, maintenance time indicating when maintenance work is performed, maintenance type indicating the type of maintenance work, maintenance content indicating the content of maintenance work, and maintenance cost indicating the amount charged for maintenance work , Maintenance work information DB for registering each information indicating,
Replacement information for specifying the replacement, pre-replacement information for specifying the product individual before the replacement, a product model before replacement indicating the model of the product individual before the replacement, post-replacement information specifying the product individual after the replacement, and replacement A place information DB for registering information indicating a product model after replacement indicating a subsequent product model and a replacement time indicating a time of replacement;
Product type, average customer unit price, replacement period, total number of units sold, total number of units shipped, average number of months since the initial shipment of individual products, and initial number of products A maintenance summary information DB for registering each information indicating an average maintenance frequency indicating the maintenance frequency and an average maintenance cost indicating a maintenance work charge amount;
3. The replacement according to claim 1, wherein the extraction processing unit extracts a list of place proposal customer candidates with reference to the product individual information DB, the customer information DB, and the maintenance aggregation information DB. Proposal support system.

Images