WO2024095345A1 - Système de mise en correspondance et procédé de mise en correspondance - Google Patents

Système de mise en correspondance et procédé de mise en correspondance Download PDF

Info

Publication number
WO2024095345A1
WO2024095345A1 PCT/JP2022/040799 JP2022040799W WO2024095345A1 WO 2024095345 A1 WO2024095345 A1 WO 2024095345A1 JP 2022040799 W JP2022040799 W JP 2022040799W WO 2024095345 A1 WO2024095345 A1 WO 2024095345A1
Authority
WO
WIPO (PCT)
Prior art keywords
vendor
customer
matching
vendors
quotation
Prior art date
Application number
PCT/JP2022/040799
Other languages
English (en)
Japanese (ja)
Inventor
明洋 東田
真隆 河邉
Original Assignee
株式会社Fuji
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Fuji filed Critical 株式会社Fuji
Priority to PCT/JP2022/040799 priority Critical patent/WO2024095345A1/fr
Publication of WO2024095345A1 publication Critical patent/WO2024095345A1/fr

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]

Definitions

  • This specification discloses a matching system and a matching method.
  • the person in charge must sort the information and then check each case to find the case information they want. Therefore, depending on the number of cases to be checked after the sorting process, it may be time-consuming to find the case information they want.
  • the main purpose of this disclosure is to reduce the hassle and perform efficient matching.
  • a first matching system of the present disclosure includes: A matching system that supports matching between a customer who wishes to purchase equipment and a plurality of vendors, comprising: a reception unit that receives a request for quotation for equipment from the customer together with information on requirements for the equipment; a distribution unit that distributes the quotation request together with the requirement information to at least one of the plurality of vendors; a presentation unit that receives a quotation response from the vendor in response to the quotation request and presents the quotation response to the customer;
  • customers can make quotation requests without accessing each vendor, eliminating the need to check information about each vendor or input requirements information for each vendor.
  • vendors only need to provide quotations for requests for quotation that they wish to receive, eliminating the need to provide quotations for requests for quotation that they do not wish to receive or to contact vendors to decline requests for quotation. This eliminates the need for time and effort and allows for efficient matching.
  • FIG. 1 is a diagram showing an outline of the configuration of a matching system 10.
  • FIG. 2 is an explanatory diagram showing an outline of the functions of the matching system 10.
  • 11 is a flowchart showing an example of a matching-related process.
  • 11 is a flowchart showing an example of a reception process.
  • 11 is a flowchart showing an example of a distribution process.
  • 11 is a flowchart showing an example of a presentation process.
  • 11 is a flowchart showing an example of a management process.
  • FIG. 11 is an explanatory diagram showing an example of the flow of matching-related processing.
  • FIG. 11 is an explanatory diagram showing an example of the flow of matching-related processing.
  • FIG. 4 is an explanatory diagram showing an example of a label selection screen 60.
  • FIG. 4 is an explanatory diagram showing an example of a vendor selection screen 70.
  • 13 is a flowchart showing a matching-related process according to a modified example.
  • 10 is a flowchart showing a modified example of a reception process.
  • 13 is a flowchart showing a selection process according to a modified example.
  • FIG. 11 is an explanatory diagram showing the flow of a matching-related process according to a modified example.
  • FIG. 1 is a block diagram showing an outline of the configuration of a matching system 10
  • FIG. 2 is an explanatory diagram showing an outline of the functions of the matching system 10.
  • the matching system 10 supports matching between vendors and customers when the customer introduces modules or a work system WS that combines modules from a vendor that provides various equipment.
  • the equipment is used in various tasks in various industries such as manufacturing and transportation, and includes devices and equipment, and is also referred to as a module hereinafter.
  • the matching system 10 includes a management server 20 that manages the entire system.
  • the management server 20 is connected to a vendor terminal 40 and a customer terminal 50 via a network 12.
  • FIG. 1 shows one vendor terminal 40 and one customer terminal 50, in reality, multiple terminals are connected.
  • the management server 20 comprises a control unit 21, a memory unit 25, and a communication unit 27.
  • the control unit 21 has a CPU, ROM, RAM, etc., and controls the entire server, such as exchanging information with the vendor terminal 40 and the customer terminal 50.
  • the matching system 10 also includes a marketplace MP where customers can select and purchase various modules, and the control unit 21 manages the marketplace MP.
  • a trading company or manufacturer is primarily the vendor and a robot SIer (System Integrator) is the customer.
  • the robot SIer is primarily the vendor and the end user is the customer. Note that a robot SIer may also be the vendor that sells modules.
  • the control unit 21 performs a simulation using a model MD (digital twin) of a work system WS that combines various modules.
  • the work system WS can be configured to perform a predetermined task using a robot equipped with a vertical multi-joint type robot arm.
  • An example of the predetermined task is picking up work such as mechanical parts and electronic parts, and may also be welding, deburring, painting, etc.
  • the work system WS that performs the picking task includes, in addition to the robot, an end effector attached to the tip link of the robot arm, a camera that captures images and lighting such as a ring light, a conveyor that transports trays and boards on which the picked work is placed, and a feeder that supplies the work.
  • the equipment and devices for performing various tasks are each called a module.
  • the various tasks may be labor-saving or automated, or may be performed in collaboration with a worker.
  • a customer selects a module from the marketplace MP to request a quote or purchase, or to run a simulation of the work system WS.
  • the work system WS does not have to include a robot as long as it is a system made up of multiple modules.
  • the control unit 21 also manages the matching site MS, which supports matching between customers and vendors. Customers can move from the marketplace MP to matching (matching site MS).
  • the control unit 21 includes a reception unit 21a, a distribution unit 21b, a selection unit 21c, a presentation unit 21d, and a billing unit 21e, as shown in FIG. 2.
  • the reception unit 21a receives requests from customers for modules and the work system WS, such as requests for estimates, orders, and installation.
  • the distribution unit 21b distributes information related to the requests received by the reception unit 21a to the vendors.
  • the selection unit 21c selects the vendors to which the information is to be distributed and selects information to be presented to the customer.
  • the presentation unit 21d presents various information replies from the vendors to the customer.
  • the billing unit 21e performs processing to bill the vendors and customers for fees related to matching.
  • the storage unit 25 is composed of a HDD and stores various application programs and various databases (DB).
  • the storage unit 25 stores a module DB (database) 30, a case DB 33, a vendor DB 35, and a customer DB 37.
  • the module DB 30 stores a plurality of module data by module type.
  • the case DB 33 stores simulation data, specification information, estimates, videos, etc. for each case.
  • the simulation data is a project file of a simulation performed using the model MD, and includes conditions such as various parameters.
  • the specification information includes information such as the vendor, model, size, and quantity of each module that constitutes the work system WS.
  • the estimate includes information such as the price of the module and the work system WS, and the installation costs of the module and the work system WS.
  • the video includes the results of a simulation performed using the model MD, as well as footage of the work system WS actually performing work.
  • the vendor DB35 information about each vendor is registered. For example, as shown in FIG. 2, the name of the certified and registered vendor, a vendor ID unique to each vendor, the location such as an address, the type of business, and other information are registered. In addition, although not shown, information such as capital, number of employees, contact information such as email address, and the type of modules provided by the vendor are also registered. In addition, information labels (hereinafter, labels) that label some information are also registered in the vendor DB35. The labels include, for example, the work content that the modules of the vendor DB35 and the work system WS can handle, the type of business of the vendor DB35, and the areas in which the installation and maintenance of the modules and the work system WS can be handled. In the example of FIG.
  • vendor DB35 registers various numbers for each vendor, such as the number of requests in progress Ka, the number of actual requests Kb, and the number of unbilled requests Kc; details of these will be described later.
  • customer DB37 information about each customer is registered.
  • customer information such as the name of the customer who has been authenticated and registered, a customer ID unique to each customer, contact information such as an email address and an address, and the customer's purchase history is registered for each customer.
  • the communication unit 27 is connected to the network 12, etc., and communicates with the vendor terminal 40, the customer terminal 50, etc.
  • the administrator inputs various instructions to the management server 20 through an input unit 28 such as a keyboard or mouse.
  • the management server 20 also displays various information on a display unit 29 such as a display.
  • the management server 20 is not limited to having a control unit 21 and a memory unit 25 (various DBs), and a data server that stores the memory unit 25 (various DBs) may be configured as a device separate from the management server 20.
  • the vendor terminal 40 comprises a control unit 41 having a CPU, ROM, RAM, etc., a storage unit 43 such as a HDD that stores various application programs and various data, and a communication unit 46 that is connected to the network 12, etc. and communicates with the management server 20, etc.
  • the vendor terminal 40 receives various instructions from the vendor and various information that needs to be registered from an input unit 48 such as a keyboard or mouse.
  • the vendor terminal 40 also displays various screens of the marketplace MP and matching site MS on a display unit 49 such as a display.
  • the customer terminal 50 comprises a control unit 51, a memory unit 53, and a communication unit 56.
  • various instructions from the customer and various information that needs to be registered are inputted via an input unit 58 such as a keyboard or mouse.
  • the customer terminal 50 displays various screens of the marketplace MP and the matching site MS on a display unit 59 such as a display.
  • FIG. 3 is a flow chart showing an example of matching-related processing. This processing is executed by the control unit 21 of the management server 20.
  • the control unit 21 performs a reception process (S100), a distribution process (S110), a presentation process (S120), and a management process (S130).
  • the reception process is a process for receiving requests from customers.
  • the distribution process is a process for distributing the received requests to one or more vendors.
  • the presentation process is a process for presenting responses from vendors to customers.
  • the management process is a process for managing the number of requests Ka, the number of actual requests Kb, the number of unbilled requests Kc, and the like, and for billing fees. Each process will be described in detail below.
  • Figures 4 to 7 are flowcharts showing examples of the reception process, distribution process, presentation process, and management process, respectively.
  • Figures 8 and 9 are explanatory diagrams showing an example of the flow of matching-related processing.
  • the control unit 21 determines whether or not a quotation request (FIG. 8 (1)) has been made by the customer via the request reception screen of the matching site MS displayed on the display unit 59 of the customer terminal 50 (S200), and terminates the reception process if it determines that a quotation request has not been made.
  • the request reception screen includes a quotation request button that allows the customer to request a quotation for a module, a work system WS, etc.
  • a quotation request can be made before the customer has decided on a vendor to which the request will be made.
  • control unit 21 determines in S200 that a quotation request has been made, it displays a guide screen for deciding how to select a destination vendor (S205).
  • the guide screen allows the customer to select, by using radio buttons or the like, either a selection method in which the destination vendor is selected based on a label selected by the customer, or a selection method in which the customer directly selects a vendor.
  • the control unit 21 determines whether the label-based selection method has been selected on the guide screen (S210) or whether the direct selection method has been selected (S215), and if it determines that neither has been selected, it returns to S205. If the control unit 21 determines in S210 that the selection has been selected, it causes the display unit 59 of the customer terminal 50 to display a label selection screen (S220) and waits for the customer to complete the label selection (S225). On the other hand, if the control unit 21 determines in S215 that the selection has been selected, it causes the display unit 59 of the customer terminal 50 to display a vendor selection screen (S230) and waits for the customer to complete the vendor selection (S235).
  • the label selection screen 60 has a work content selection field 61, an industry selection field 62, and an area selection field 63.
  • the work content selection field 61 one or more of a plurality of labels indicating work content, such as "picking”, “deburring”, and “welding”, can be selected.
  • the industry selection field 62 one of a plurality of labels indicating industry, such as “manufacturing", "food”, and “transportation”, can be selected.
  • the area selection field 63 is divided into an upper section and a lower section.
  • one of a plurality of labels indicating relatively large areas such as “Kanto”, “Tokai”, and “Kansai”
  • one of a plurality of labels indicating relatively small areas such as each prefecture included in the area selected in the upper section, can be selected.
  • the customer can confirm the selection by operating the completion button 64, and can return to the guidance screen by operating the back button 65.
  • FIG. 11 is an explanatory diagram showing an example of a vendor selection screen 70.
  • the vendor selection screen 70 has a vendor selection field 71.
  • a number of check boxes 72 for individually selecting each vendor and an information button 73 for viewing information about each vendor are provided for each vendor. If necessary, a customer can operate the information button 73 to view vendor information, or check the check boxes 72 to select one or more vendors from which they wish to receive information. In addition, a customer can confirm their selection by operating the complete button 74, and can return to the guidance screen by operating the back button 75.
  • control unit 21 determines in S225 or S235 that the selection is complete, it saves the selection results made by the customer (S240).
  • the control unit 21 displays an input screen for requirement information such as modules on the display unit 59 of the customer terminal 50 (S245), and waits for the input to be completed (S250).
  • requirement information input screen allows the input of the work content to be performed by the modules and work system WS, the shape and dimensions of the work to be handled, material, installation area, budget, required capacity, desired delivery date, etc., and each item may be selectively input.
  • the control unit 21 determines in S250 that the requirement information has been input, it saves the requirement information (S255) and ends the reception process.
  • the control unit 21 determines whether or not there are any undistributed requests for quotation among the requests for quotation received in the reception process (S300), and terminates the distribution process if it determines that there are no undistributed requests for quotation. If the control unit 21 determines that there are any undistributed requests for quotation, it checks the selection results saved in S240 of the reception process (S305), and determines whether or not a selection method based on labels has been saved (S310).
  • control unit 21 determines that a label-based selection method has been saved, it selects a vendor whose label selected by the customer matches the label stored in the vendor DB 35 (S315).
  • the control unit 21 determines that a direct selection method has been saved instead of a label-based selection method, it selects a vendor selected by the customer (S320).
  • the control unit 21 distributes a quotation request together with the requirement information saved in S255 of the reception process to the vendors selected in S315 and S320 (S325), and ends the distribution process.
  • S315 and S320 one or more vendors are selected according to the saved selection results, and a quotation request is distributed to each vendor in S325 ((2) in FIG. 8). Note that in FIG. 8, a quotation request has not been distributed to vendor D. This is because the label of vendor D did not match the label selected by the customer, or vendor D was not included in the vendors selected by the customer.
  • the quotation request delivered in S325 is assumed to have a deadline for the quotation response.
  • the vendor who received the quotation request checks the requirements information and decides whether or not to create a quotation response. If it is decided to create a quotation response, the vendor selects modules and work systems WS that satisfy the requirements information and creates the quotation response. The vendor transmits the created quotation response from the vendor terminal 40 to the management server 20. Note that if the vendor decides not to create a quotation response, there is no need for the vendor to take any action such as transmitting a notice to the customer or the management server 20 that a quotation response will not be created.
  • the control unit 21 judges whether or not an estimate response (FIG. 8 (3)) to the transmitted request for estimate has been received from a vendor (S400).
  • the vendor C did not respond to the request for estimate, so no estimate response was sent from vendor C.
  • the control unit 21 judges that an estimate response has been received, it stores the estimate response (S405).
  • the control unit 21 judges whether or not it is time to present the estimate response (S410). For example, the control unit 21 judges that the timing for presenting the estimate response is when the deadline for the estimate response has passed. Alternatively, the control unit 21 may judge that the timing for presenting the estimate response is each time the control unit 21 saves the estimate response.
  • control unit 21 judges that it is time to present the estimate response, it presents the estimate response to the customer (S415, FIG. 8 (4)) and ends the presentation process.
  • the estimate response is presented, for example, on the screen of the matching site MS. Therefore, the control unit 21 may notify the customer that the quotation response can be presented and prompt the customer to check it on the screen of the matching site MS. Alternatively, the control unit 21 may attach the quotation response to an email and send it to the customer.
  • the control unit 21 judges whether or not an order request (FIG. 9 (5)) has been received from a customer to whom a quotation response has been submitted (S500).
  • the control unit 21 judges that an order request has been received, it transmits the order request to the requested vendor (S505) and increments the number of requests Ka for that vendor by a value of 1 to update it (S510).
  • the number of requests Ka indicates the number of order requests received from each vendor, and is incremented by 1 each time an order request is received, and is decremented by 1 in the process described below.
  • the vendor that has received the order request contacts the customer directly or via the management server 20, and after determining the requirement information for the case for which the order has been requested, manufactures and arranges for the module and the work system WS.
  • the vendor then completes the process for the order request by delivering and installing the module and the work system WS.
  • the vendor transmits a completion report (FIG. 9 (7)) to the management server 20.
  • the control unit 21 determines whether a completion report has been received from the vendor (S515), and if not, proceeds to S535. On the other hand, if the control unit 21 determines that a completion report has been received, it updates the vendor's number of pending requests Ka by decrementing the value by 1 (S520). The control unit 21 also updates the vendor's number of actual orders Kb by incrementing the value by 1 (S525), and updates the vendor's number of unbilled orders Kc by incrementing the value by 1 (S530). The number of actual orders Kb indicates the cumulative number of order requests for which processing has been completed. The number of unbilled orders Kc indicates the number of orders for which billing to the vendor has not been completed.
  • the billing timing may be, for example, a predetermined timing such as a specific day of each month, or when the number of unbilled items Kc reaches a predetermined number. If the control unit 21 judges that it is not time to bill, it ends the management process. On the other hand, if the control unit 21 judges that it is time to bill, it calculates the fee to be billed to the vendor, such as a system usage fee or a commission fee, based on the number of unbilled items Kc (S540). For example, the control unit 21 calculates the fee by multiplying the number of unbilled items Kc by the fee per item.
  • control unit 21 sends a billing notice to the vendor (S545), resets the number of unbilled items Kc to a value of 0 (S550), and ends the management process. If the control unit 21 judges that it is time to bill multiple vendors in S535, it executes the processes of S540 to S550 for each of the multiple vendors.
  • the control unit 21 may perform a process of debiting the fee from the vendor's registered account, or may perform a process of settling the fee using application software for settling the fee. Alternatively, the vendor who receives the invoice may perform a process of depositing the fee.
  • the control unit 21 (reception unit 21a) that executes S100 of the matching-related process of this embodiment corresponds to the reception unit
  • the control unit 21 (distribution unit 21b) that executes S110 of the matching-related process corresponds to the distribution unit
  • the control unit 21 (presentation unit 21d) that executes S120 of the matching-related process corresponds to the presentation unit.
  • the memory unit 25 (vendor DB 35) of the management server 20 corresponds to the memory unit.
  • the control unit 21 (billing unit 21e) that executes S535 to S545 of the management process corresponds to the billing unit.
  • an example of the matching method of this disclosure is also clarified by explaining the operation of the control unit 21 (matching site MS) of the management server 20.
  • the matching system 10 of this embodiment described above accepts a quotation request from a customer together with requirements information, distributes it to at least one of multiple vendors, and presents the customer with the quotation response from the vendor to the quotation request.
  • This allows the customer to make a quotation request without having to access each vendor individually, saving the trouble of checking the information of each vendor and inputting requirements information for each vendor.
  • vendors since vendors only need to respond with a quotation for requests for quotation that they wish to receive, they can save the trouble of responding with a quotation for requests for quotation that they do not wish to receive or contacting vendors to decline the quotation request. This saves time and effort and allows for efficient matching.
  • the matching system 10 stores information on the work content, industry, and area as labels for each vendor, accepts the customer's selection of a label, and selects a vendor whose stored label matches the label selected by the customer to deliver a quotation request. This allows the customer to easily select a vendor whose work content, industry, and area match their desired content. Furthermore, because a quotation request is made after a vendor has been selected in this way, it is possible to prevent the quotation response from being wasted because the work content, industry, or area does not match the customer's desired content after the quotation response has been received.
  • the matching system 10 accepts a selection of destination vendors from the customer, and distributes the quotation request to the vendor selected by the customer. This reduces the risk of information leakage, as information such as quotation requests and required specifications is not distributed to vendors to which the customer does not want to disclose information.
  • the customer can decide between a label-based selection method or a direct selection method, making it easy to select a vendor in a way that suits the customer.
  • a fee is charged to the vendor based on the successful matching of the customer and vendor, ensuring the profitability of the matching system 10 and enabling stable operation.
  • the destination is determined by either the label-based selection method or the direct selection method, but this is not limited to this, and the destination may be determined by only one method.
  • the customer when accepting the selection of the destination vendor, the customer selects a vendor that is acceptable as the destination, but this is not limited to this, and the customer may select a vendor that is not acceptable as the destination.
  • the destination may be a vendor other than the vendor selected by the customer.
  • the information on the work content, industry, and area is used as the label, but this is not limited to this, and at least any information on the work content, industry, and area may be used as the label.
  • it is not limited to selecting a vendor and distributing it, and the quotation request may be distributed to all vendors.
  • the quotation request may be distributed to a vendor that wishes to receive it.
  • part of the information on the required specifications of the quotation request such as information on the type of module to be quoted, may be made viewable, and the quotation request may be distributed if the vendor who viewed the information wishes to do so.
  • the fee is charged to the vendor based on the number of unbilled items Kc, which indicates the number of items reported as completed, but this is not limited to the above, and the fee may be charged when the customer requests an order from the vendor and a match is made. Furthermore, the fee is not limited to a fee based on the number of items, and may be based on the amount, such as a fee calculated by multiplying the price of the module or work system WS by a specified percentage. Furthermore, a specified system usage fee or system participation fee may be charged separately from these fees.
  • matching between customers and vendors is performed based on a request for quotation, but this is not limited to the above.
  • Matching between customers and vendors may also be performed based on a request for installation of a module or work system WS.
  • An installation request is made, for example, when a module that has been purchased or is to be purchased from a vendor that only sells products is requested to be installed by another vendor. There are no particular restrictions on the seller, and a request for installation of a module that has been purchased or is to be purchased may be made from a vendor other than the matching system 10.
  • the control unit 21 executes the selection processing of S110b (FIG. 14) after the reception processing of S100 (FIG. 13), and executes the presentation processing of S120 and the management processing of S130.
  • the presentation processing and management processing of the modified example are performed in the same manner as in the embodiment. Therefore, in the management processing, the number of requests Ka, the number of actual cases Kb, and the number of unbilled cases Kc are updated in the same manner as in the embodiment, and the fee is billed in the same manner as in the embodiment.
  • the control unit 21 judges whether or not an installation request (FIG. 15(1)) has been made from the customer via the request reception screen of the matching site MS displayed on the display unit 59 of the customer terminal 50 (S200b), and ends the reception process if it judges that an installation request has not been made.
  • the request reception screen includes an installation request button for the customer to make an installation request. If the control unit 21 judges in S200b that an installation request has been made, it displays an area selection screen for the customer to select the area for installation (S220b) and waits for the selection to be completed (S225). Although not shown, the selection screen has an area selection field for the installation target. The area selection field is configured, for example, in the same manner as the area selection field 63 of FIG. 10. If the control unit 21 judges in S225 that the selection has been completed, it saves the selection result made by the customer on the area selection screen (S240).
  • the control unit 21 causes the display unit 59 of the customer terminal 50 to display a track record selection screen that allows the customer to select whether or not to prioritize installation track record when selecting a vendor (S241).
  • the track record selection screen allows the customer to select, by using radio buttons or the like, either "track record priority” which prioritizes the vendor's track record (number of track records Kb), or "track record priority” which does not prioritize the vendor's track record.
  • the control unit 21 determines whether or not "track record priority” has been selected (S242), and if it determines that it has been selected, it saves the fact that "track record priority” has been selected (S243) and ends the reception process. If the control unit 21 determines that "track record priority without” has been selected instead of “track record priority,” it saves the fact that "track record priority without” has been selected (S244) and ends the reception process.
  • the control unit 21 determines whether or not there is an installation request for which a vendor has not been selected among the installation requests received in the reception process (S600), and ends the selection process if it determines that there is no installation request for which a vendor has not been selected. If the control unit 21 determines that there is an installation request for which a vendor has not been selected, it checks the selection result saved in S240 of the reception process of the modified example and the presence or absence of performance priority saved in S243 and S244 (S605). Next, the control unit 21 selects a vendor whose installation area label selected by the customer matches the area label stored in the vendor DB 35 (S610). Next, the control unit 21 determines whether "performance priority" has been saved (S615).
  • control unit 21 determines that "performance priority” has been saved, it sorts the vendors selected in S610 in descending order of the number of performance cases Kb (S620). On the other hand, if the control unit 21 determines that "performance priority” has been saved, it sorts the vendors selected in S610 in ascending order of the number of requests being made Ka (S625). Then, the control unit 21 selects a predetermined number of top vendors from the vendors sorted in S620 and S625 (S630, FIG. 15 (2)), and ends the selection process. In the presentation process of S120 in the modified matching process, the control unit 21 performs a process of presenting the predetermined number of vendors selected in S630 to the customer (FIG. 15 (3)).
  • control unit 21 may present the predetermined number of vendors together with the number of requests Ka and the number of successful requests Kb.
  • the customer can easily decide which vendor to request installation from among the presented vendors, eliminating the need to search for a vendor with a matching installation area. Also, since vendors will not receive installation requests from customers outside their available installation area, they can eliminate the need to contact customers to decline installation requests. This allows for efficient matching while saving time and effort.
  • vendors with a larger number of successful cases Kb can be presented to the customer. This allows the customer to easily request installation from a vendor with a larger number of successful cases without having to check information such as the number of successful cases Kb of each vendor. Also, if "no track record priority" is selected, vendors with fewer requests Ka are presented to the customer, increasing the possibility that installation work will be carried out quickly. Therefore, customers who want early installation can select "no track record priority.”
  • the vendor with the fewer number of requests Ka is presented to the customer, but this is not limited to the above, and multiple vendors with the same area may be presented to the customer without any special sorting.
  • the selection of whether or not to prioritize installation performance is not limited, and it is not necessary to select anything. In other words, multiple vendors with the same area may be presented.
  • the control unit 21 may present them together with the number of requests Ka and the number of successful installations Kb.
  • the control unit 21 may manage the number of achievements Kb of each vendor for each type of module, such as a robot or a conveyor. The control unit 21 may then accept an installation request from a customer along with information on the type of module, and select a vendor with the highest corresponding number of achievements Kb. Alternatively, the control unit 21 may manage the number of achievements Kb of each vendor by distinguishing between a single module, such as a robot, and a work system WS, for example. The control unit 21 may then accept an installation request from a customer by distinguishing between a single module and a work system WS, and select a vendor with the highest corresponding number of achievements Kb.
  • the selection process is performed without distributing the installation request from the customer to the vendor, but this is not limited to this.
  • the control unit 21 performs a distribution process to distribute the installation request from the customer to each vendor with the same installation area, and waits for a response from the vendor as to whether installation is possible. The control unit 21 may then present the vendors who have responded that installation is possible. Alternatively, the control unit 21 may perform the selection process of S110b for the vendors who have responded that installation is possible, and then present them to the customer.
  • the selection process as in the modified example is not performed, but the selection process may be performed.
  • the control unit 21 may perform a selection process based on the number of achievements Kb for multiple vendors that have received quotation responses, similar to S110b in the modified example, and then perform the presentation process of S120.
  • a selection method based on labels and a selection method of direct selection may be used together.
  • the control unit 21 first displays the label selection screen 60 and accepts the selection of a label by the customer, and then selects a vendor whose label selected by the customer matches the label stored in the vendor DB 35.
  • the control unit 21 may display the selected vendor on the vendor selection screen 70 together with a check box, accept the selection of a vendor by the customer, and transmit a quotation request or an installation request to the selected vendor.
  • the customer may be able to leave the selection of the vendor to which the request is to be delivered to the matching system 10.
  • the matching system 10 may select all vendors as distribution destinations, or may select a distribution destination vendor based on various information such as the content of the request and the vendor's busy status.
  • the matching system 10 of the embodiment and modified example may be configured as a system dedicated to matching, without selling modules, etc.
  • the second matching system of the present disclosure is A matching system that supports matching between a customer who wishes to install equipment and a plurality of vendors, comprising: a storage unit that stores, for each vendor, information on an installation area that the vendor can handle; a reception unit that receives a request for installation of equipment from the customer together with information on the installation area of the customer; a selection unit that selects, from among the plurality of vendors, a vendor whose installation area information stored in the storage unit matches installation area information of the customer; a presentation unit that presents the vendor selected by the selection unit to the customer;
  • the gist of the project is to provide the following:
  • customers can easily decide which vendor to request installation from among the presented vendors, eliminating the need to search for vendors with matching installation areas.
  • vendors can avoid the trouble of contacting customers to decline installation requests, since they will not receive installation requests from customers outside their available installation areas. This allows for efficient matching while saving time and effort.
  • This disclosure can be used in technical fields such as matching customers and vendors.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système de mise en correspondance qui aide à mettre en correspondance un client, qui souhaite acheter un équipement, avec une pluralité de vendeurs, et comprend : une unité de réception qui reçoit une demande de cotation d'équipement provenant d'un client conjointement avec des informations d'exigence d'équipement ; une unité de distribution qui distribue la demande de cotation conjointement avec les informations d'exigence à au moins l'un de la pluralité de vendeurs ; et une unité de présentation qui reçoit, en provenance d'un vendeur, une réponse de cotation à la demande de cotation, et présente la réponse de cotation au client.
PCT/JP2022/040799 2022-10-31 2022-10-31 Système de mise en correspondance et procédé de mise en correspondance WO2024095345A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/040799 WO2024095345A1 (fr) 2022-10-31 2022-10-31 Système de mise en correspondance et procédé de mise en correspondance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/040799 WO2024095345A1 (fr) 2022-10-31 2022-10-31 Système de mise en correspondance et procédé de mise en correspondance

Publications (1)

Publication Number Publication Date
WO2024095345A1 true WO2024095345A1 (fr) 2024-05-10

Family

ID=90929961

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/040799 WO2024095345A1 (fr) 2022-10-31 2022-10-31 Système de mise en correspondance et procédé de mise en correspondance

Country Status (1)

Country Link
WO (1) WO2024095345A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001319149A (ja) * 2000-05-10 2001-11-16 Daikin Ind Ltd 商品購入サポート方法及び商品購入サポートシステム
JP2001338093A (ja) * 2000-05-26 2001-12-07 Matsushita Electric Works Ltd 販売情報供給システム
JP2002015187A (ja) * 2000-06-28 2002-01-18 Matsushita Electric Ind Co Ltd 電子ショッピングシステムにおける売買データ処理方法
WO2002052471A1 (fr) * 2000-12-27 2002-07-04 Arkray, Inc. Dispositif de mediation
JP2002230370A (ja) * 2001-01-31 2002-08-16 Hitachi Ltd システム製品販売支援システム及びシステム製品販売支援方法
JP2013073331A (ja) * 2011-09-27 2013-04-22 Nobuyasu Enomoto 商品取引装置および商品取引方法
WO2014142077A1 (fr) * 2013-03-11 2014-09-18 アルシス株式会社 Dispositif de fourniture d'informations, appareil de gestion de constructeur, dispositif de présentation d'informations, programme, système de communication et procédé de fourniture d'informations

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001319149A (ja) * 2000-05-10 2001-11-16 Daikin Ind Ltd 商品購入サポート方法及び商品購入サポートシステム
JP2001338093A (ja) * 2000-05-26 2001-12-07 Matsushita Electric Works Ltd 販売情報供給システム
JP2002015187A (ja) * 2000-06-28 2002-01-18 Matsushita Electric Ind Co Ltd 電子ショッピングシステムにおける売買データ処理方法
WO2002052471A1 (fr) * 2000-12-27 2002-07-04 Arkray, Inc. Dispositif de mediation
JP2002230370A (ja) * 2001-01-31 2002-08-16 Hitachi Ltd システム製品販売支援システム及びシステム製品販売支援方法
JP2013073331A (ja) * 2011-09-27 2013-04-22 Nobuyasu Enomoto 商品取引装置および商品取引方法
WO2014142077A1 (fr) * 2013-03-11 2014-09-18 アルシス株式会社 Dispositif de fourniture d'informations, appareil de gestion de constructeur, dispositif de présentation d'informations, programme, système de communication et procédé de fourniture d'informations

Similar Documents

Publication Publication Date Title
US20030212602A1 (en) Order and inventory management system
US7957990B2 (en) System and method for managing asset installation and evaluation
US6876895B2 (en) Order assembly production system and method
US20210224740A1 (en) Merchandise delivery management system and program
US20080140244A1 (en) Method and apparatus for planning a manufacturing schedule using an adaptive learning process
CN1471680A (zh) 利用数据网络完成用户产品的订货、履行与交付的集成系统
US20030018537A1 (en) System and method of intermediating sales
US20090299794A1 (en) Goods Distribution Management System
US20020052808A1 (en) Book management apparatus
WO2024095345A1 (fr) Système de mise en correspondance et procédé de mise en correspondance
WO2003088115A1 (fr) Systeme et procede de gestion de stock en rayons, programme avec support d'enregistrement
US20040199805A1 (en) Repair worker assisting method, repair worker assisting program, repair worker assisting system, and terminal
KR20190106828A (ko) 물품 보관 배송 서비스 제공방법 및 이를 포함하는 시스템
WO2020178937A1 (fr) Système d'aide à l'introduction d'installation
WO2022190266A1 (fr) Système de mise en correspondance
KR100697781B1 (ko) 거래 지원 시스템 및 거래 지원 방법
US20020161654A1 (en) Information processing apparatus and method for managing order/delivery of components
WO2023067788A1 (fr) Système de marché et procédé de gestion de demande de cotation
JP2005215817A (ja) コンピュータシステム構築の見積システム
WO2020178975A1 (fr) Système d'aide à l'introduction d'une installation
WO2023074004A1 (fr) Système de gestion de l'approvisionnement, programme informatique de système de gestion de l'approvisionnement et procédé de commande de système de gestion de l'approvisionnement
JP2003216749A (ja) 会員管理システム、会員管理方法、会員管理プログラムおよびコンピュータで読み取り可能な記録媒体
JP2003345965A (ja) 顧客接触活動支援システム及び方法
JPH04106657A (ja) 物流システム
JP4182388B2 (ja) 釣具の改良パーツのインターネット受注システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22964367

Country of ref document: EP

Kind code of ref document: A1