Matching support system and matching support method

Abstract

To provide a matching support system and a matching support method for supporting suitable matching between clients and service providers.SOLUTION: A matching support system stores basic information that is information related to each of a plurality of providers of a service, request information that is information related to a request received from a client of the service, a reliability level that is information indicating a level of reliability of each of the plurality of providers, and information indicating an expertise level of each of the providers in relation to the service. The matching support system determines a difficulty level of the request on the basis of the request information, generates first extraction results by extracting candidate providers of the service from the basic information so as to extract providers having higher reliability levels as the difficulty level of the request becomes higher, generates second extraction results by extracting candidate providers of the service from the first extraction results so as to extract providers having higher expertise levels in relation to the service as the difficulty level of the request becomes higher, and presents a user with the candidate providers based on the second extraction results.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a matching support system and a matching support method. [Background technology]

[0002] Conventionally, to those who provide services (hereinafter referred to as "service providers") When a requester (service recipient) requests the provision of a service, the relationship between the requester and the service provider Various mechanisms have been proposed to support matching.

[0003] For example, in Patent Document 1, the level of the teacher is evaluated in advance, and the student is given a lesson that matches the student's level. The educational intermediary processing device that introduces teachers is described. Evaluate the level of teachers recruited through recruitment methods and the level of students recruited through student recruitment methods. The education mediation processing device mediates between teachers and students of the evaluation level corresponding to the teacher. The teacher's level is evaluated according to the results of the test. The intervention processing device extracts teachers with evaluation levels corresponding to the acquired student levels, and Students are allowed to choose the teacher they want from among the teachers.

[0004] For example, Patent Document 2 discloses a method for registering a user in one of a plurality of pre-registered local communities. We match users with supporters who can help them, and we carry out mutual aid activities between users and supporters. The present invention describes an assistance system configured for the purpose of providing assistance. The program is based on multiple approvals approved by the administrator who manages the local community to which the supporter belongs. Manages support registration data including supporter information for each registered supporter and collects support from users. Supporter candidates that match the support request request are selected from multiple approved supporters included in the support registration data. In addition, the support system selects from multiple approved supporters included in the support registration data. , and prioritizes the selection of supporter candidates whose individual reliability is determined by the administrator. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-183487 [Patent Document 2] Japanese Patent Publication No. 2020-170424 Summary of the Invention [Problem to be solved by the invention]

[0006] When a requester makes a request to a service provider, the requester may, for example, "I want to choose an agent who will carry out my work with sincerity," "I want to choose an agent who will handle my work at a reasonable price." "I want to request a service from an agent who is familiar with the field of the service I want to request." On the other hand, the service provider is also required to consider operational efficiency, work distribution, etc. From the perspective of responsibility and education, "if you have little experience (you have not built trust), Wide range of experience in non-specialized (not necessarily specialized) services in the field "By doing so, I want to assess my own expertise and increase my credibility as a service provider," If you have a lot of experience, you can further enhance your expertise by focusing on highly specialized services. "We want to continue to improve our reputation as a service provider and further increase its credibility." Matching between the client and the service provider is not just from the client's perspective, but also from the service provider's perspective. It is desirable to take into consideration the donor's perspective.

[0007] In the above-mentioned patent document 1, the level of the teacher is evaluated in advance, and the teacher who matches the level of the student is selected. In addition, in the above-mentioned Patent Document 2, the user can introduce the experience level and Reliable support candidates are selected based on other information (such as qualifications). Regarding the mechanisms described in the literature, we have taken into consideration the perspectives of the client and the thoughts of the service provider. Then, we match the client (student, user) with the service provider (teacher, potential supporter). It is not intended to provide guidance.

[0008] The present invention supports appropriate matching between clients (service recipients) and service providers. To provide a matching support system and a matching support method that can The purpose is to [Means for solving the problem]

[0009] To achieve the above object, one aspect of the present invention is to provide a service provider that allows a client to A machine that helps match requesters and service providers when requesting services. A switching support system configured using an information processing device having a processor and a storage device. The information is collected from the requester and includes basic information about each of the plurality of providers. request information, which is information about the request, and information indicating the degree of reliability of each of the plurality of providers; and information indicating the expertise of each of the providers in the service. a difficulty level determination unit that determines the difficulty level of the request based on the request information; The service provider is selected so that the higher the reliability of the request, the higher the reliability of the provider is extracted. A second extraction result is generated by extracting candidates from the basic information and describing the extracted results. 1 extraction unit, and the provision of the service in which the degree of difficulty of the request is high extracting candidates for the service provider from the first extraction result so that a candidate for the service provider is extracted, and and a second extraction unit that generates a second extraction result that describes the extracted result.

[0010] Other problems and solutions disclosed in this application are described in the section on the preferred embodiment of the invention, and the drawings. [Effects of the Invention]

[0011] According to the present invention, appropriate matching between a client (service recipient) and a service provider is achieved. can support. [Brief explanation of the drawings]

[0012] [Figure 1] This is an example of a matching support system. [Figure 2] 3 is an example of a function provided in the proxy request support device of the first embodiment. [Figure 3] 10 is an example of a reliability determination table. [Figure 4] 10 is an example of a specialty field determination table. [Figure 5] 10 is an example of a basic information table. [Figure 6] 10 is an example of a proxy history table. [Figure 7] 10 is an example of a request status table. [Figure 8] 10 is a flowchart illustrating a proxy request support process according to the first embodiment. [Figure 9] 10 is a flowchart illustrating an example of a first extraction process. [Figure 10] 10 is a flowchart illustrating an example of a second extraction process. [Figure 11]10 is a flowchart illustrating an example of a reliability determination table generation process. [Figure 12A] 10 is an example of a correspondence table between the number of applications and points. [Figure 12B] This is an example of a table showing the correspondence between acceptance rates and scores. [Figure 12C] 10 is an example of a correspondence table between average client evaluation values and scores. [Figure 13] 10 is a flowchart illustrating an example of a specialty field determination table generation process. [Figure 14A] 10 is an example of a specialty field reception screen. [Figure 14B] 10 is an example of a power information confirmation screen. [Figure 15] 10 is an example of a request evaluation reception screen. [Figure 16] 1 is an example of an information processing device used in configuring a matching support system. [Figure 17] 10 is a diagram illustrating an example of functions provided in a proxy request support device according to a second embodiment. [Figure 18A] FIG. 10 is a diagram showing how a difficulty level determination unit generates a difficulty level determination result. [Figure 18B] 10A and 10B are diagrams illustrating how a workload determination unit generates a workload determination result. [Figure 19] 10 is an example of a work schedule reception screen. [Figure 20] 10 is an example of a workload determination table. [Figure 21] 10 is a flowchart illustrating a proxy request support process according to the second embodiment. [Figure 22] 10 is a flowchart illustrating a third extraction process. [Figure 23] FIG. 10 is a diagram illustrating an outline of the third extraction result generation process. [Figure 24] 10 is a flowchart illustrating a third extraction result generation process. [Figure 25] 10 is a flowchart illustrating a fourth extraction result generation process. [Figure 26] 10 is a diagram illustrating an example of functions provided in a proxy request support device according to a third embodiment. [Figure 27]10 is an example of a desired requester level reception screen. [Figure 28] 10 is an example of a basic information table. [Figure 29] 10 is an example of a requester evaluation table. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The above aspects are merely examples for explaining the present invention, and may be omitted or simplified as appropriate for clarity of explanation. The present invention can be embodied in various other forms.

[0014] In the following explanation, when describing identification information, the terms "identifier," "first name," and "ID" are used. , "number", etc., which can be substituted for each other. In the following explanation, various types of information will be explained using expressions such as "table" and "information." However, various information may be expressed in other data structures. To show that it does not depend on the data structure, "XX table" etc. can be called "XX information". In the following explanation, "database" may be written as "DB." In the following description, duplicated explanations of the same or similar configurations will be omitted. In the following explanation, the letter "S" before the symbol indicates a processing step. This is the meaning of "top".

[0015] [First embodiment] Hereinafter, an information processing system according to one embodiment of the present invention (hereinafter referred to as a "matching support system") will be described. The matching support system 1 is a system that allows a requester to request a service. (hereinafter referred to as "Service Provider") to provide the Service. The matching support system will support matching between the requester and the service provider. The target clients and service providers of System 1 are not necessarily limited. are individuals or companies, and the service provider provides various services to national and local government organizations. A person who provides services to process applications on behalf of others (for example, an agent acting as a lawyer or judge) Let us take the case of a legal scrivener, administrative scrivener, or other professional (hereinafter referred to as "agency"). Reveal.

[0016] When requesting a service from an agent, the client may request, for example, "I want to choose an agency that can provide the service at a reasonable price." "I want to hire an agent who is familiar with the field of the service I want to request." On the other hand, there are also agents who are not experienced (low reliability) Service providers do not necessarily have high expertise in various service fields (expertise is not necessarily required). By having them experience a wide range of services (not required), they will be able to provide services while identifying their own expertise. "I want to increase trust as a donor," "Those with a lot of experience can provide highly specialized services," By having them focus on you, you can further enhance your expertise and increase your credibility as a service provider. The Matching Support System 1 is designed to meet these requests. We provide the services requested by the client, taking into consideration the client's perspective and the agent's wishes. We provide a system that recommends suitable candidates for agents. In this case, the matching support system 1 may, for example, determine the capabilities and reliability of the agent, the requested service, We select recommended agents based on the content of the service, costs, etc. The switching support system 1 is, for example, based on the actual business situation of the agent (diversification of business content, latest Difficulty in tracking information, separation of agents based on their specialties, differences in the difficulty of each task, Consideration should be given to ensuring educational opportunities for unskilled workers to improve the quality of services, and ensuring profits commensurate with the services provided. Select an appropriate agent taking into consideration the

[0017] FIG. 1 shows a schematic configuration of a matching support system 1. As shown in the figure, The switching support system 1 includes an agent request support device 100, a client terminal 200, and an agent The agent request support device 100, the requester terminal 200, and the agent terminal 30 0 are all configured using one or more information processing devices (computers) and are used in communication networks. The communication network 5 is connected in a state where two-way communication is possible. A wired or wireless communication network, such as a LAN (Local Area Network) ), WAN (Wide Area Network), the Internet, various public wireless communication networks, dedicated lines, etc. be.

[0018] The proxy request support device 100 receives information about a proxy request for a service (hereinafter referred to as "request information") from the client terminal 200, and performs the proxy request based on the received request information. depending The proxy request support device 100 then generates information describing the selected proxy service provider (hereinafter referred to as "recommendation information") and transmits it to the requester terminal 200.

[0019] The requester terminal 200 receives the request contents from the requester and writes the received request contents. The requester terminal 200 generates request information and transmits it to the proxy request support device 100. Receives recommendation information from the request support device 100 and sends the received recommendation information to the requester. Present.

[0020] The agent terminal 300 stores information used by the agent request support device 100 when selecting an agent. (hereinafter referred to as "agent information") from the agent, and The information is transmitted to the proxy request support device 100.

[0021] FIG. 2 is a diagram showing the main functions of the proxy request support device 100. As shown in the figure, The proxy request support device 100 includes a request information receiving unit 110, a request content determining unit 115, and a proxy agent. Extraction unit 120, agent organization evaluation unit 125, recommendation unit 130, agent request unit 135 , reliability determination table generation unit 140, specialty field determination table generation unit 145, agent competence Display unit 150, request evaluation registration unit 155, agent competency DB 180, and agent information DB It has 185 functions.

[0022] As shown in the figure, the agent competence DB 180 includes a reliability determination table 1810 and a specialist The agent information DB 185 manages the category determination table 1820. The application history table 1852 and the request status table 1870 are managed.

[0023] Among the above functions, the request information receiving unit 110 receives request information sent from the requester terminal 200. The request information is information that identifies the requester (hereinafter referred to as "requester ID"). ) and information about the specific content of the requested service, various information necessary for the execution of the service Contains information.

[0024] The request content determination unit 115 includes a request field determination unit 1151 and a difficulty determination unit 1152. 1152 Among these, the requested field determination unit 1151 determines the field of the requested service (such as the type of application; hereinafter referred to as the "request field") based on the request information. For example, if the request information includes information indicating the requested field, the requested field determination unit 1151 determines the requested field by using the information. Furthermore, the requested field determination unit 1151 determines the requested field by, for example, applying a category classification algorithm or natural language processing to the description (text data, etc.) included in the request information.

[0025] Difficulty level judgment part 1152 determines the difficulty of the request (the difficulty of the service to be provided in response to the request) based on the request information. The difficulty determination unit 152 determines the difficulty based on, for example, the effort required to provide the service in response to the request, the amount of processing, the complexity of the work, the required period (delivery date), etc. In this embodiment, the difficulty is assumed to be one of "low", "medium", and "high", but the difficulty may also be, for example, a continuous value (the larger the value, the higher the difficulty). Difficulty determination unit 1152 For example, if the request information includes information indicating the difficulty level, the difficulty level is determined using the information. Difficulty level determination section 1152 However, for example, the difficulty level is determined by applying a predetermined algorithm or natural language processing to the description (text data, etc.) included in the request information.

[0026] The agent extraction unit 120 includes a first extraction unit 1201 and a second extraction unit 1202. The first extraction unit 1201 refers to the reliability determination table 1810 and extracts the basic information table 1 Information that lists agents selected from 851 based on their reliability (hereinafter referred to as "first extraction result"). The field determination table 1820 is referenced, and agents are extracted from the first extraction result in terms of expertise. and submit information containing a list of the extracted agents (hereinafter referred to as the "second extraction result"). Generate.

[0027] The agent organization evaluation unit 125 uses the agent competence DB 180 and the agent information DB 185 Based on the content, the organization to which the agent listed in the second extraction result belongs (for example, a lawyer) (hereinafter referred to as "agency organizations"), Information describing the results of the evaluation (hereinafter referred to as "evaluation information") is generated, and the generated evaluation information is The agent organization evaluation unit 125 reflects the information in the request status table 1870. The physical distance between the location of the customer and the location of the agent organization (the closer the two, the more convenient it is). (This will result in a higher rating), fees paid to the agency (unit price, agency commission, other costs) ), evaluate the agent organization based on the reputation of the agent organization. The agent organization evaluation unit 125 may receive the information from the user via an interface, or may It may be generated based on evaluation by a specific algorithm or machine learning model. If there are multiple agents in the organization, the agent organization evaluation unit 125 may, for example, The evaluation information of the agent with the highest evaluation is stored in the request status table as the evaluation information of the agent organization. Register with 1870.

[0028] The recommendation unit 130 recommends the agent group to which the agent listed in the second extraction result belongs. The organization is identified from the basic information table 1851, and the second extraction result and the agency to which each agent belongs are compared. The client terminal 200 transmits information including the evaluation information of the agent organization and each agent. The terminal 200 receives the information from the recommendation unit 130 and presents the received information to the user. In addition, the client terminal 200 receives the designation of an agent from the user and The information identifying the agent (hereinafter referred to as "agent ID") and the designated agent organization The agent organization ID is sent to the agent request support device 100. The recommending unit 130 receives the agent ID and the agent ID sent from the client terminal 200. Receive the vendor organization ID.

[0029] When the agent request unit 135 receives the agent ID from the requester terminal 200, the agent request unit 135 The agent request unit 135 updates the table 1870. The agent terminal 300 of the agent organization to which the agent corresponding to the received agent ID belongs is Information to the effect that the agent is requested (entrusted) to act on your behalf (hereinafter referred to as "Notice of Request for Proxy Action"). When the agent terminal 300 receives the notification of the request for the agent, it sends the following to the agent. The proxy request notification is sent to the requester. The information may include information about the specific content of the service provided.

[0030] The reliability determination table generation unit 140 generates (edits or deletes) the reliability determination table 1810. The details of this processing will be described later.

[0031] The specialty field determination table generation unit 145 is a field-specific experience value calculation unit 1451 and a specialty field candidate. The field-specific experience value calculation unit 1451 calculates the experience value of the agent for each field. The specialty field candidate generation unit 1452 determines the specialty field based on the experience value of the agent for each field. Create (including edit and delete) tables 1820.

[0032] The agent competency display unit 150 includes a reliability determination table 1810 and a specialty field determination table 1811. The agent terminal 300 transmits the contents of 820 to the agent terminal 300. The contents of the cable 1820 are received and presented to the agent.

[0033] The request evaluation registration unit 155 receives the request evaluation from the requester terminal 200 and The evaluation is received and reflected in the application history table 1852.

[0034] 3 shows an example of the reliability determination table 1810. The reliability determination table 1810 includes the following: The reliability of the agent is managed. The reliability determination table 1810 shown in the example is 1811, agent organization ID 1812, and trustworthiness 1813. Each record in the reliability determination table 1810 corresponds to one agent. is doing.

[0035] Among the above items, the agent ID 1811 contains the agent ID (agent name, etc.) The agent organization ID 1812 is the agent organization ID of the organization to which the agent belongs. The ID (office name, etc.) is stored. The reliability 1813 contains information indicating the reliability of the agent. In this example, a value indicating the reliability (maximum value is 100) is stored. The larger the value, the higher the reliability. The details will be described later.

[0036] 4 shows an example of the specialty field determination table 1820. The specialty field determination table 1820 manages information indicating the specialty field and experience level of each agent (information indicating the expertise of each agent). The example specialty field determination table 1820 manages information indicating the specialty field and experience level of each agent (information indicating the expertise of each agent). 1821, an agent organization ID 1822, an area of expertise 1823, and an experience score for each area 1824. One record in the area of expertise determination table 1820 corresponds to one agent.

[0037] Among the above items, the agent ID 1821 stores the agent ID. The organization ID 1822 stores the agent organization ID of the organization to which the agent belongs. The field 1823 stores information indicating the field of expertise of the agent. In the field 1824, information indicating the experience level of the agent in each field is stored. A value indicating the experience level (maximum value is 100) is stored. The higher the value, the more experience you have ( It indicates that the person is an expert or has high skills. Details of the law will be discussed later.

[0038] An example of the basic information table 1850 is shown in FIG. 5. The basic information table 1850 contains the following information: Basic information about the business operator (hereinafter referred to as "basic information") is managed. The basic information table 1850 includes an agent ID 1851, an agent organization ID 1852, and an address. One or more records with each item of 1853, agency fee 1854, and years of service 1855 Each record in the basic information table 1850 corresponds to one agent. .

[0039] Among the above items, the agent ID 1851 contains the agent ID (agent name, etc.) The agent organization ID 1852 is the agent organization of the organization to which the agent belongs. The ID (office name, etc.) is stored. The address 1853 stores the address of the agent organization. The agency fee 1854 includes the fee (basic fee, additional fee) for requesting the agency to act on your behalf. The number of years of service 1855 is the number of years of service in the relevant agency organization of the relevant agency. The number of years of service (years of service) is stored.

[0040] An example of the proxy history table 1860 is shown in FIG. 6. The proxy history table 1860 contains the following information: The example agency history table 1860 manages the agency history of the agency. 861, Agent Organization ID 1862, Request Field 1863, Agent Result 1864, Requester Rating The record includes one or more records having the items of the proxy request date 1865 and proxy request date 1866. One record in the history table 1860 corresponds to one agency history of one agency. .

[0041] Among the above items, the agent ID 1861 contains the agent ID (agent name, etc.) The agent organization ID 1862 is the agent organization of the organization to which the agent belongs. The ID (office name, etc.) is stored. The request field 1863 contains information indicating the field of the proxy request. The proxy result 1864 stores the result of the proxy service provided by the proxy service provider. Information indicating the result (e.g., whether the application documents were "accepted" or "not accepted" by the public institution) ", etc.) is stored. Requester evaluation 1865 stores the information on the proxy requests handled by the proxy service provider. In this example, the value indicating the evaluation (maximum value is 100) is stored. The larger the value, the higher the evaluation. The date on which the person accepted the proxy request is stored.

[0042] An example of the request status table 1870 is shown in FIG. A proxy request received from a customer (a proxy request that has not yet been processed by the proxy service provider after being received) The example request status table 1870 includes a requester ID 1871, a request Request ID 1872, status 1873, request candidate information 1874, request destination information 1875, and one or more records having the items of the request date 1876 to the agent. One record in table 1870 corresponds to one proxy request received from a requester. do.

[0043] Among the above items, the requester ID 1871 is the requester's identifier (the requester's name, etc.). The request ID 1872 stores the accepted proxy request. The status 1873 stores the identifier of the request (hereinafter referred to as the "request ID"). Information indicating the current status of the proxy request (e.g., "Waiting for proxy selection," "Request completed to proxy," etc.) The candidate request destination information 1874 stores one or more candidates narrowed down for the proxy request. Information about the candidate agent for the above request (agent organization name, agent name, agent organization The request destination information 1875 stores the information selected for the proxy request. Information on the agent submitted (agent organization name, agent name, agent organization evaluation information, fee The date of request to the agent 1876 is the date when the agent has processed the request. The date on which the request was made to the supplier is stored.

[0044] Next, various processes performed in the matching support system 1 will be explained in order. .

[0045] FIG. 8 is a flowchart for explaining the process (hereinafter referred to as "proxy request support process S800") performed in the matching support system 1. Hereinafter, the proxy request support process will be described together with FIG. S800 This article explains:

[0046] First, the requester terminal 200 receives request information from a user via a user interface. The proxy request support device 100 then sends the received request information to the proxy request support device 100. The request information receiving unit 110 receives the request information sent from the requester terminal 200 ( S811).

[0047] Next, the request field determination unit 1151 determines the field of the request received from the user based on the request information. The requested field is determined, and the difficulty determination unit 1152 determines the requested field based on the request information. The difficulty of the requested request is determined (S812).

[0048] Next, the first extraction unit 1201 extracts the basic information table based on the reliability determination table 1810. The first extraction result is generated by extracting agents to be recommended from the rule 1851 (S 813).

[0049] FIG. 9 shows the process performed by the first extraction unit 1201 in S813 of FIG. 8 (hereinafter referred to as the “first extraction process”). This is a flowchart for explaining the first extraction process (hereinafter referred to as "processing S813"). The output process S813 will now be described.

[0050] As shown in the figure, first, the first extraction unit 1201 extracts the number of questions according to the difficulty level determined in S812. The subsequent processing is branched (S911).

[0051] If the difficulty level determined in S812 is "high" (S911: high), the first extraction unit 1201 The reliability determination table 1810 determines whether the reliability 1813 is equal to or greater than a first threshold value set in advance. A certain agent is extracted (S912), and a first extraction result including a list of the extracted agents is generated. After that, the process proceeds to S814 in FIG.

[0052] In addition, if the difficulty level determined in S812 is "medium" (S911: medium), the first extraction unit 1 201 is a second threshold value in which a reliability 1813 is set in advance from the reliability determination table 1810. The agents whose number is equal to or greater than the first threshold and less than the first threshold are extracted (S913), and a list of the extracted agents is Then, the process proceeds to S814 in FIG.

[0053] In addition, if the difficulty level determined in S812 is "low" (S911: low), the first extraction unit 1 201 is a second threshold value in which a reliability 1813 is set in advance from the reliability determination table 1810. The agents whose total number of employees is less than 1000 are extracted (S914), and a first extraction result including a list of the extracted agents is generated. Then, the process proceeds to S814 in FIG.

[0054] In this way, in the first extraction process S813, the reliability according to the difficulty of the requested service is calculated. The first extraction result is extracted from the agent. For example, for a service with a high degree of difficulty, Agents with high reliability are extracted, and for services with medium level of difficulty, the reliability is Medium-level agents are extracted, and for services with low difficulty, agents with low reliability are extracted. The vendor is extracted.

[0055] Returning to FIG. 8, the second extraction unit 1202 of the agent extraction unit 120 then extracts the specialty field from the Based on the table 1820, agents are extracted from the first extraction result to generate a second extraction result ( S814).

[0056] FIG. 10 shows the process performed by the second extraction unit 1202 in S814 of FIG. 8 (hereinafter referred to as the “second extraction”). This is a flowchart for explaining the process S814. The extraction process S814 will now be described.

[0057] First, the second extraction unit 1202 branches the subsequent processing depending on the difficulty level determined in S812. (S1011).

[0058] If the difficulty level determined in S812 is "high" or "medium" (S1011: high or medium), The second extraction unit 1202 extracts from the specialty field determination table 1820 the information described in the first extraction result, In addition, the second extraction result is generated by extracting agents whose specialty field 1823 includes the requested field ( After that, the process proceeds to S815 in FIG.

[0059] In addition, if the difficulty level determined in S812 is "low" (S1011: low), the second extraction unit 1202 is a field of expertise determination table 1820, and is described in the first extraction result and is requested The second extraction result is generated by extracting agents whose experience in the field is below a preset threshold. After that, the process proceeds to S815 in FIG.

[0060] In this way, in the second extraction process S814, for services with a difficulty level of "high" or "medium", In this case, from among the agents with a "high" or "medium" reliability extracted as the first extraction result, Agents whose specialty areas include the requested field are extracted. In addition, for services with a "low" level of difficulty, In this case, the service is selected from among the agents with a "low" reliability extracted as the first extraction result. Agents with little experience in the requested field of the service are selected.

[0061] Returning to FIG. 8, the agent organization evaluation unit 125 then determines the organization to which the agent in the second extraction result belongs. The agent organization is identified from the basic information table 1851, and the agent competence DB 180 and the agent Based on the contents of the agent information DB 185, evaluation information of the identified agent organization is generated. In addition, the agent organization evaluation unit 125 reflects the generated evaluation information in the request status table 1870. (S815).

[0062] Next, the recommendation unit 130 recommends the second extraction result, the identified agent organization, and each agent organization. The recommendation information including the evaluation information of the client organization is transmitted to the requester terminal 200. The processing unit 130 updates the status 1873 in the request status table 1870 (S816). .

[0063] The client terminal 200 receives the recommendation information sent from the recommendation unit 130, The received recommendation information is presented to the user. and agent designation from the user, and the accepted agent ID and agent organization ID are The recommendation unit 130 sends the request from the requester terminal 200 to the proxy request support device 100. The agent ID and agent organization ID are received (S817).

[0064] The agent request unit 135 receives the agent organization ID received by the recommendation unit 130. The agent request unit 135 transmits an agent request notification to the agent terminal 300 of the organization. The status 1873 in the request status table 1870 is updated (S818).

[0065] When the agent terminal 300 receives the proxy request notification, it notifies the agent that a proxy request has been made. The agent performs the service specified in the agent request notice (S819). .

[0066] As described above, according to the proxy request support process S800, the difficulty level of the service is "high" or "medium". For services, agents who are highly reliable and have expertise in the requested field (high level of expertise) are selected. Therefore, for services with a "high" or "medium" level of difficulty, we will hire a representative who is familiar with the requested field. An agency organization that meets the needs of clients who want to receive reliable services from agents. In addition, agents can recommend services that they are good at. This will increase the likelihood of receiving requests in areas where you are specialized, allowing you to provide high-quality services. This will increase the satisfaction of the client, and the agent will be able to provide a satisfactory service. You can expect a good return.

[0067] In addition, for services with a "low" level of difficulty, we select agents with low experience from among those with low reliability. Therefore, for services with a low level of difficulty, reasonable Fast and affordable service (we can search widely for agents with ample capacity to provide fast service) In accordance with the needs of the client to receive the service (in the sense of increasing the likelihood of receiving the service) In addition, it is possible for the agency organization and the agency to recommend the agency. , it is possible to effectively utilize human resources (improving work efficiency), and to enhance the careers of inexperienced people. We can expect benefits such as being able to learn more about the subject (educational effect).

[0068] <Generation of reliability judgment table> FIG. 11 shows the reliability determination table generation unit 140 of the proxy request support device 100. The process performed when generating the table 1810 (hereinafter referred to as "reliability determination table generation process S11") 00). The table generation process S1100 will be described. The process S1100 is executed by checking the agent ID (agent ID 185) in the basic information table 1850. 1) is carried out every time.

[0069] First, the reliability determination table generating unit 140 selects the processing target from the basic information table 1850. The basic information of the target agent (hereinafter referred to as the "agent") is acquired (S11 11).

[0070] Next, the reliability determination table generation unit 140 acquires the information of the record of the agent (the agent's agency history) from the agency history table 1860 ( S1112 ).

[0071] Next, the reliability determination table generating unit 140 selects the relevant The experience value of each agent in each field is acquired (S1113).

[0072] Next, the reliability determination table generating unit 140 calculates the reliability of the agent (S1114). The reliability determination table generating unit 140 calculates the reliability based on, for example, the following formula (hereinafter referred to as "Formula 1"). [ formula 1 ] Reliability = Average value of experience for each field of agents in the specialty field determination table +Score based on number of applications + Score based on acceptance rate (= number of acceptances / number of applications submitted so far)

[0073] The reliability determination table generating unit 140 calculates the score based on the number of applications in the second term of the formula 1 as follows: For example, Table 1 shown in FIG. 12A (hereinafter referred to as "application number and point correspondence table 1210"). ) is calculated based on the third term in Equation 1. The score based on the selection rate (= number of selected applications / number of applications submitted up to now) is calculated as shown in Table 2 ( Hereinafter referred to as "Table 1220: Correspondence between Acceptance Rate and Score."

[0074] Next, the reliability determination table generation unit 140 generates a record associating the agent ID of the agent, the agent organization ID of the organization to which the agent belongs, and the reliability calculated in S1214, and stores (registers) the record in the reliability determination table 1810 ( S1115 ).

[0075] <Generating a Specialty Field Judgment Table> FIG. 13 shows the specialty field determination table generation unit 145 of the proxy request support device 100. The process performed when generating the judgment table 1820 (hereinafter referred to as "specialty field judgment table generation process") This is a flowchart for explaining the process of the process of the special field. The judgment table generation process S1300 will be described. S1300 is performed for each agent (agent ID 1851) in the basic information table 1850. can be.

[0076] First, the specialized field determination table generating unit 145 determines the processing from the basic information table 1850. Acquire basic information about the target agent (hereinafter referred to as the "agent") (S1 311).

[0077] Next, the reliability determination table generation unit 140 selects the proxy from the proxy history table 1860. The information on the agent's record (the agent's agency history) is acquired (S1312).

[0078] Next, the reliability determination table generation unit 140 selects the substitute from the reliability determination table 1810. The reliability of the supplier is acquired (S1313).

[0079] Next, the reliability determination table generation unit 140 calculates the experience value of the agent for each field ( S1314 The specialty field determination table generating unit 145 calculates the empirical value for each field based on the following formula (hereinafter referred to as "Formula 2"), for example. [ formula 2 ] Experience in XX field = Points based on the number of applications in the XX field of the agent in the application history table + Score based on the acceptance rate in the field (= number of acceptances / number of applications submitted so far) + Score based on the average client evaluation in the field

[0080] The specialty field determination table generation unit 145 determines the first term in the formula 2 as "in the application history table" For example, the score based on the number of applications in the field of the agent in question is shown in Table 1 (Applications) in Figure 12A. The score is calculated based on the correspondence table 1210 between the number of cases and the score. 5 is the second term in formula 2, "Acceptance rate in the field (= number of accepted applications / number of applications submitted so far)" For example, it is calculated based on Table 2 (table 1220 of correspondence between acceptance rate and score) shown in FIG. 12B. The field determination table generation unit 145 calculates the third term in Equation 2, "the average of the client evaluations in the field of For example, the score based on the client's evaluation is shown in Table 3 in Figure 12C (hereinafter referred to as the "average score and score of the client's evaluation"). The calculation is based on the "Correspondence Table 1230" (hereinafter referred to as "Correspondence Table 1230").

[0081] Next, the specialty field determination table generating unit 145 uses the reliability acquired in S1313 as a It is determined whether the value is equal to or greater than the set threshold value (S1315).

[0082] If the reliability is equal to or greater than a preset threshold (S1315: YES), the specialty field determination table The bull generation unit 145 sends all the field names and the empirical values calculated for each field to the agent terminal 300. The agent terminal 300 receives the request from the agent request support device 100 (S1316). While presenting the names of all fields and the required experience level in each field, the agent will ask you to select the field you want to specialize in. Accepts input of (specialty field) and transmits the accepted field to the proxy request support device 100 ( The specialized field determination table generating unit 145 receives the field from the agent terminal 300. When you send it, the agent ID of the agent, the agent to which the agent belongs, and the agent organization ID of the organization to be identified, the field received from the agent terminal 300, and A record corresponding to the obtained experience value for each field is generated and stored in the field of expertise determination table 1820. The data is stored (registered) (S1317).

[0083] In S1315, if the reliability is less than a preset threshold (S1315: NO) The specialty field determination table generation unit 145 stores the agent's agent information in the specialty field determination table. The agent ID, the agent organization ID of the organization to which the agent belongs, and each Records that correspond to the field experience value (in this case, the field of expertise 1823 is not listed) The generated information is stored (registered) in the specialty field determination table 1820 (S1321).

[0084] In FIG. 14AB, in S1331, the agent terminal 300 selects the field (specialty field) as the agent. The screen displayed when accepting applications from the Here is an example.

[0085] <Processing of Agent Competency Display Section> The agent capability display unit 150 of the agent request support device 100 is managed by the agent capability DB 180. Based on the information being managed (reliability determination table 1810, specialty field determination table 1820), The screen (hereinafter referred to as "ability") lists the agent's capabilities (reliability, area of expertise, experience in each area). A quantity information confirmation screen 1420 is generated and presented to the user.

[0086] FIG. 14B shows an example of the ability information confirmation screen 1420. Note that the agent ability display unit 150 However, the competence information confirmation screen 1420 is sent to the agent terminal 300 so that the agent can refer to it. The agent can check his / her own competence by referring to the competence information confirmation screen 1420. It is possible to check what content is registered in the proxy request support device 100. .

[0087] <Request Evaluation Registration Department> The request evaluation registration unit 155 of the proxy request support device 100 registers the evaluation of the service provided by the proxy agent. The evaluations are received from the requester via the requester terminal 200, and the received evaluations are stored in the proxy history table. This is reflected in the Table 1860.

[0088] FIG. 15 shows a screen (hereinafter, An example of the request evaluation reception screen 1500 is shown below.

[0089] <Example of information processing device> FIG. 16 shows the configuration of the matching support system 1 (the proxy request support device 100 and the requester terminal 2 00, agent terminal 300) This is a configuration example.

[0090] The illustrated information processing device 10 includes a processor 11, a main memory device 12 (memory), an auxiliary memory device The system includes a device 13 (external storage device), an input device 14, an output device 15, and a communication device 16. These are connected to each other so as to be able to communicate with each other via a bus, a communication cable, etc. Examples include personal computers, server devices, smartphones, tablets, and office Examples include computers and general-purpose computers (mainframes).

[0091] The information processing device 10 is provided in whole or in part by, for example, a cloud system. Virtual servers are provided using virtualization technology and process space isolation technology, etc. It may be realized by using general information processing resources. All or part of the functions provided by the cloud system may be provided through API (Application Programming Interface). It may also be realized by a service provided via a Programming Interface (PFI), etc. All or part of the functions provided by the information processing device 10 are provided as SaaS (Software as a Service), for example. ware as a Service), PaaS (Platform as a Service), IaaS (Infrastructure It may be realized by using the Service as a Service.

[0092] The processor 11 may be, for example, a CPU (Central Processing Unit), an MPU (Micro Processor), Processing Unit), GPU(Graphics Processing Unit), FPGA(Field Programmable Gate Array), ASIC (Application Specific Integrated Circuit), AI (Artifi It is constructed using ICT chips, etc.

[0093] The main memory device 12 is a device used by the processor 11 when executing a program. For example, ROM (Read Only Memory), RAM (Random Access Memory), non-volatile memory The proxy request support device 100 and the requester terminal The various functions realized in the agent terminal 300 are executed by the respective processors 11. The programs and data stored in the auxiliary storage device 13 are read into the main storage device 12. This is achieved by extracting and executing the

[0094] The auxiliary storage device 13 is a device for storing programs and data, and is, for example, an SSD (Solid State Drive). lid State Drive), hard disk drive, optical storage device (CD (Compact Disc) , DVD (Digital Versatile Disc), storage systems, IC cards, SD cards Read / write devices for non-transitory recording media such as flash memory cards and optical recording media, and non-transitory cloud servers The auxiliary storage device 13 may be configured with a recording medium reader or Through the communication device 16, the non-transitory recording medium or other information processing device equipped with a non-transitory storage device can be Programs and data can be read from the device. Stored in the auxiliary storage device 13. The programs and data stored in the memory 12 are read into the main memory 12 as needed.

[0095] The input device 14 is an interface that accepts input of information from the outside, for example: Keyboard, mouse, touch panel, card reader, pen input tablet, voice input power devices, etc.

[0096] The output device 15 is an interface that outputs various information such as the process progress and the process results to the outside. The output device 15 is, for example, a display device (liquid crystal monitor, L CD (Liquid Crystal Display), graphic card, etc.), and converting the above various information into audio. devices that convert the above information into text (such as printers) ) For example, the information processing device 10 may exchange information with other devices via the communication device 16. The configuration may be such that the above input and output are performed.

[0097] The input device 14 and the output device 15 are used for interactive processing with the user (receiving information, The user interface is configured to realize the provision of information.

[0098] The communication device 16 is a device that realizes communication with other devices. A wired or wireless communication interface that enables communication with other devices via a network. Interfaces, such as NIC (Network Interface Card) and wireless communication modules , USB modules, etc.

[0099] The information processing device 10 includes, for example, an operating system, a file system, DBMS (DataBase Management System) (relational database, NoSQL, etc.) ), KVS (Key-Value Store), etc. may also be introduced.

[0100] [Second embodiment] In the matching support system 1 of the first embodiment, from the viewpoint of reliability and field (specialty field), The agents recommended to the client were extracted. Matching support system 1 of the second embodiment Furthermore, the second implementation selects agents based on the amount of work required to carry out the service. The form matching support system 1 is a system in which multiple agents share the service for one request. In this way, the matching agent of the second embodiment is selected taking into consideration the case where the matching agent is executed simultaneously. Since the work support system 1 extracts recommended agents taking into account the workload, An agent who cannot secure the required number of people is recommended, and the requester is turned down by the agent. This can reduce the likelihood of such an incident occurring.

[0101] The matching support system 1 of the second embodiment receives request information of a proxy request from a requester. From the information, the amount of work required to carry out the requested service is calculated for each level of difficulty. The matching support system 1 then stores the workload for each difficulty level separately for each agent. Agents are extracted by comparing the amount of work each agent in the trade organization can handle.

[0102] FIG. 17 shows the configuration of the proxy request support device 100 of the matching support system 1 according to the second embodiment. The proxy request support device 100 of the second embodiment is a diagram showing the main functions of the proxy request support device 100 of the first embodiment. Although the basic configuration is the same as that of the proxy request support device 100, the following points are different from those of the first embodiment. The configuration is different from that of the proxy request support device 100.

[0103] First, the process of the difficulty level determination unit 1152 of the request content determination unit 115 is different. The difference is that the determination unit 115 further includes a workload determination unit 1153. The difference is that the first extraction unit 1201 and the second extraction unit 1202 perform processing according to the level of difficulty of the request information. Another difference is that the agent extraction unit 120 further includes a third extraction unit 1203. In addition, the agent capability DB 180 includes a workload determination table 18 used to determine the workload of the service. The difference is that the agent request unit 135 manages the agent 30. The available work time for the agent in the workload determination table 1830 is calculated. The difference is that the time required for the work is reduced by the amount of work required for the work. The configuration differs in that it further includes a proxy request support device 190. This article will focus on the differences from 100.

[0104] The difficulty level determination unit 1152 of the proxy request support device 100 of the second embodiment determines the difficulty level for each element of the service. The difficulty level determination unit 1152 determines the difficulty level for each item of the application form (for example, for each item of the application form). The difficulty level is determined by the user. Alternatively, the difficulty level determination unit 1152 may automatically determine the difficulty level based on the request information. For example, the acceptance rate of past applications (the lower the acceptance rate, the higher the difficulty level), the amount of information written in the application form (the more information written), etc. The more information you provide, the higher the level of difficulty.) The more free-form writing you provide, the higher the level of difficulty. The difficulty level is determined based on the following criteria:

[0105] In FIG. 18A, the difficulty level determination unit 1152 determines the content of the application form 1805 included in the request information. The difficulty level is determined for each element (item) based on the above and the difficulty level determination result 1801 is generated. show.

[0106] Returning to FIG. 17, the workload determination unit 1153 of the proxy request support device 100 determines the workload based on the request information. The workload required to complete the requested service is determined (estimated). 1153 determines the amount of work for the requested service for each difficulty level determined for each element. The workload determination unit 1153 generates and manages (stores) workload determination results that describe the results of the determination. do.

[0107] FIG. 18B shows the workload determination unit 1153 determining the workload for each element and the requested service for each level of difficulty. 18 shows how the workload of a process is determined and a workload determination result 1802 is generated.

[0108] Returning to FIG. 17, the third extraction unit 1203 refers to the workload determination table 1830 and A combination of agents capable of carrying out the requested work is extracted from the second extraction result, and the extracted A third extraction result is generated that describes the results of the above.

[0109] The workload determination table generation unit 190 of the proxy request support device 100 of the second embodiment The agent sends the work schedule (already scheduled work date / time / work period) via the customer terminal 300. The workload determination table 1830 is generated based on the accepted work schedule ( (including editing, deleting, etc.)

[0110] FIG. 19 shows the workload determination table generation unit 190 generating the workload determination table generated by the agent terminal 300 from the agent. A screen displayed when accepting a work schedule (hereinafter referred to as a "work schedule acceptance screen 1900" The work schedule reception screen 1900 may be generated by the agent terminal 300. , the proxy request support device 100 may generate it and send it to the agent terminal 300.

[0111] FIG. 20 shows the work amount determination table generated by the work amount determination table generating unit 190 based on the received work schedule. 18 is an example of the workload determination table 1830. As shown in the figure, the workload determination table 183 0 is the agent ID 1831, agent organization ID 1832, and the amount of work per available work period The workload determination table 183 is composed of one or more records having each of the items 1833. One of the 0 records corresponds to one agent.

[0112] Among the above items, the agent ID 1831 stores the agent ID of the agent in question. The agent organization ID 1832 contains the agent organization ID of the organization to which the agent belongs. The amount of work per available work period 1833 is stored as the amount of work per available work period (hours (h ) units) is stored.

[0113] FIG. 21 shows the process performed in the matching support system 1 of the second embodiment (hereinafter referred to as " 2 is a flowchart illustrating the proxy request support process S2100. The process of S2111 in the support process S2100 is the same as that of the proxy request support process S2111 shown in FIG. S811 of 800 and S2117 to S2119 are the proxy request subsidies shown in Figure 8. The process is the same as S817 to S819 of the support process S800, but the process of S2112 to S2116 is different. This differs from the proxy request support process S800 shown in FIG. 2. The following mainly describes the differences from the first embodiment, along with the same figure, in the proxy request support process S2100 of the second embodiment. We will explain about this.

[0114] In S2112, the request field determination unit 1151 determines the field of the requested service (type of application form) The difficulty level determination unit 1152 determines the difficulty level for each element of the service (for example, The proxy request support device 100 determines the degree of difficulty for each field and The difficulty level for each element is stored as the difficulty level determination result 1801 (S812).

[0115] In S2113, the agent extraction unit 120 (first extraction unit 1201, second extraction unit 1202) However, the difficulty level determination result 1801 is processed for each difficulty level, and the first extraction result and the second extraction result are A process for generating the third extraction process S2113 is performed (hereinafter referred to as "third extraction process S2113").

[0116] FIG. 22 is a flowchart illustrating the third extraction process S2113. The third extraction process S2113 will be explained below. That is, the third extraction process S2113 is executed for each difficulty level.

[0117] As shown in the figure, first, the agent extraction unit 120 extracts the difficulty level determined by the difficulty level determination unit 1152. The amount of work for difficulty level "x" is obtained (S2211).

[0118] Next, the agent extraction unit 120 determines whether the acquired work volume is greater than "0". If the amount of work is not greater than "0" (S2212: NO), the difficulty level is The third extraction process S2113 for the degree is completed. If the amount of work is greater than "0" (S2 212: YES), the process proceeds to S2213.

[0119] In S2213, the first extraction unit 1201 sets the difficulty level to "x" and extracts the first extraction result shown in FIG. An extraction process S813 is performed to generate a first extraction result.

[0120] Next, the second extraction unit 1202 sets the difficulty level to "x" and executes the second extraction process shown in FIG. S814 is performed to generate a second extraction result (S2214).

[0121] Next, the third extraction unit 1203 selects an agent based on the second extraction result while taking into consideration the workload. and generating a third extraction result that describes the extracted results (hereinafter referred to as "third extraction result generation"). This is referred to as "processing S2215".

[0122] FIG. 23 is a diagram for explaining an outline of the third extraction result generation process S2215. In both cases, an overview of the third extraction result generation process S2215 will be explained.

[0123] First, the third extraction unit 1203 extracts the first task with difficulty level "x" from the workload determination table 1830. 2. Extract the record containing the agent ID from the extraction result (S2311). The records of three agents α1 to α3 from agent organization α and two agents α1 to α3 from agent organization β are The records of human agents β1 to β2 are extracted.

[0124] Next, the third extraction unit 1203 extracts the information belonging to the same agent organization (the information having the same agent organization ID). In the example shown in the figure, the records of the agent α are grouped (S2312). Group A1 contains records 1 to α3, and group A2 contains records β1 to β2. They are grouped in various ways.

[0125] Next, the third extraction unit 1203 extracts the level of the combination of ai and the third extraction result of the difficulty level "x". Add a code (S2313). Note that i" is a member of a small group that makes i' in group Ai. When expressed as a number, it represents the number of combination a of small groups consisting of i' people.

[0126] Next, the third extraction unit 1203 extracts all combinations of i' people a1, a2, . . . , ai", . . . , an" in Ai. The number n is the total number of groups A for each agent organization. is the total number of combinations a.

[0127] Next, the third extraction unit 1203 extracts the amount of work of the agent included in ai" within the specified period. The total is calculated (S2315).

[0128] Next, the third extraction unit 1203 assigns the combination of ai" to the third extraction result of difficulty level "x". Pay (S2316).

[0129] In the figure, the difficulty of the requested service is "medium", the amount of work is "30", i' is "2", and the proxy is The available work time of agent α1 is "10", the available work time of agent α2 is "20", and the available work time of agent α3 is "10". In this example, the available work time is "10". For combination "a1" and combination "a2", the total available working time of the agent is Since the amount is "30" or less and the task can be performed, the third extraction unit 1203 selects the difficulty level as "medium." The third extraction result stores the records corresponding to each combination of (α1,α2) and (α2,α3). do.

[0130] FIG. 24 is a flowchart illustrating the third extraction result generation process S2215. The third extraction result generation process S2215 will be described with reference to the same figure.

[0131] First, the third extraction unit 1203 extracts the second extraction result of difficulty level "x", the period, and the creation of difficulty level "x". Obtain the amount of work (S2411).

[0132] Next, the third extraction unit 1203 extracts the second extraction result of difficulty level “x” from the workload determination table. The records containing the agent ID are extracted (S2412).

[0133] Next, the third extraction unit 1203 extracts the extracted records from the same agent organization ID Grouping is performed for each record (generating A1, A2, . . . , Ai, . . . , An) (S241 3).

[0134] Next, the third extraction unit 1203 sets the index i to "1" (S2414).

[0135] Next, the third extraction unit 1203 determines whether i is equal to or less than n (S2415). If i is equal to or less than n (S2415: YES), the process proceeds to S2416. If it is greater than the threshold (S2415: NO), the third extraction result generation process S2215 ends.

[0136] Next, the third extraction unit 1203 acquires the number of people n′ in Ai (total number in Ai) (S2416). .

[0137] Next, the third extraction unit 1203 sets "1" to i' (S2417).

[0138] Next, the third extraction unit 1203 determines whether i' is equal to or less than n (S2418). If it is lower (S2418: YES), the process proceeds to S2419. If the answer is NO (S2418), "1" is added (incremented) to i, and then the process returns to S Return to 2415.

[0139] In S2419, the third extraction unit 1203 extracts all combinations of i' people "a1, a2,..." in Ai. Generate "··, ai", ···, an".

[0140] Next, the third extraction unit 1203 sets "1" to i" and sets the work availability flag to "0 " is set (S2421).

[0141] Next, the third extraction unit 1203 determines whether i" is equal to or less than n" (S2418). If it is equal to or less than that (S2418: YES), the process proceeds to S2423. If it is (S2418: NO), the process proceeds to S2430.

[0142] In S2423, the third extraction unit 1203 extracts the number of the agents included in ai" within the specified period. Calculate the total amount of work to be done.

[0143] Next, the third extraction unit 1203 determines whether the total amount of work is equal to or greater than the amount of work at difficulty level "x" (S2424). :YES On the other hand, if the total workload is less than the workload of difficulty level "x" (S2424: NO), the process proceeds to S2427.

[0144] In S2425, the third extraction unit 1203 adds the combination of ai" to the third extraction result of the difficulty level "x". Add a match.

[0145] Next, the third extraction unit 1203 sets the work possible flag to "1" (S2426).

[0146] Next, the third extraction unit 1203 adds (increments) "1" to i", and then Ri returns to S2418.

[0147] In S2430, the third extraction unit 1203 determines whether the work available flag is "1" or not. If the work availability flag is "1" (S2430: YES), the third extraction unit 1203 sets " 1 is added (incremented) (S2431), and then the process returns to S2415. On the other hand, if the work possible flag is not "1" (S2430: NO), the third extraction unit 1203 ' is incremented by "1" (S2431), and then the process returns to S2418. .

[0148] Returning to FIG. 21, the agent extraction unit 120 then extracts a fourth extraction result based on the third extraction result. 174 (hereinafter referred to as "fourth extraction result generation process S2114"). (S2114).

[0149] FIG. 25 is a flowchart illustrating the fourth extraction result generation process S2114. The fourth extraction result generation process S2114 will be described with reference to the same figure.

[0150] First, the agent extraction unit 120 extracts the third difficulty level of the workload determination result 1802 in FIG. 18B. The extraction results are obtained (S2511).

[0151] Next, the agent extraction unit 120 extracts the agent organization I from the third extraction results of any difficulty level. Records in which D does not exist are deleted from all the third extraction results (S2512).

[0152] Next, the agent extraction unit 120 extracts the third extracted results of each difficulty level for each agent organization. The records corresponding to each combination obtained by selecting agents one by one from The generated record is stored in the fourth extraction result 174 (S2513).

[0153] As described above, the matching support system 1 of the second embodiment performs the service. Therefore, for example, if the amount of work cannot be secured, the agent is selected. Agents are recommended, preventing requests from being rejected. In addition, the matching support system 1 of the second embodiment provides multiple services for one request. A number of agents (who may not belong to the same agency organization) may jointly carry out the It is possible to select agents taking into consideration the case where the transaction is carried out.

[0154] [Third embodiment] When matching between clients and service providers, for example, clients with poor reputations may be excluded. I would prefer not to accept requests from clients who may lead to trouble. If you want the agent to be able to choose who the client is, because you don't want to be asked to do it. In order to meet the needs of such agents, the matching support system of the third embodiment is The system 1 further includes a mechanism for evaluating the requester from the agent. The form matching support system 1 receives the evaluation of the requester from the agent, and the agent For clients who do not meet the level registered in advance, the agency will not be able to provide the services to such clients. Avoid recommending vendors.

[0155] FIG. 26 shows a third embodiment of the proxy request support device 100, which is based on the second embodiment. 1 shows the main functions of the proxy request support device 100 in the matching support system 1. The function of the proxy request support device 100 of the third embodiment is the same as that of the proxy request support device of the second embodiment. The functions and basic configuration of the support device 100 are the same as those of the second embodiment, but the following points are different. The configuration is different from that of the request support device 100.

[0156] First, the proxy request support device 100 of the third embodiment includes a requester information DB 170, a desired requester It further has the functions of a level registration unit 191 and a requester evaluation registration unit 192. The information DB 170 includes a requester evaluation table 1710 in which evaluations of requesters by agents are stored. In addition, the agent information DB 185 of the third embodiment manages the basic information table 1850 indicates the level of the client desired by the agent (hereinafter referred to as the "desired client level"). ) has been added. In addition, the proxy request support device 100 of the third embodiment The recommendation unit 130 recommends that the agent recommend a client who does not meet the desired client level. The agent will not be recommended to the client.

[0157] Among the functions of the proxy request support device 100 of the third embodiment, the desired requester level registration unit 191 The agent receives the desired requester level setting from the agent via the agent terminal 300, and The assigned desired requester level is stored in the basic information table 1850.

[0158] 27, when the desired requester level registration unit 191 accepts the setting of the desired requester level, The screen displayed by the agent terminal 300 (hereinafter referred to as the "desired requester level reception screen 2700") An example of this is shown below.

[0159] FIG. 28 shows an example of a basic information table 1850 according to the third embodiment. In addition to the above-mentioned items, the basic information table 1850 of the third embodiment also includes a desired requester level. It also has 1856 items.

[0160] The requester evaluation registration unit 192 shown in FIG. 26 receives requests from the agent via the agent terminal 300. The system accepts the setting of the evaluation of the requester (hereinafter referred to as the "requester evaluation level") and The details of the request are registered in the requester evaluation table 1710. If the requester has received the request in the past, the agent shall, for example, The average value of the evaluations of the requester obtained through the above evaluations is set as the requester evaluation level.

[0161] An example of the requester evaluation table 1710 is shown in Fig. 29. As shown in the figure, the requester evaluation The table 1710 includes the items of a requester ID 1711 and a requester evaluation level 1712. It consists of one or more records. The requester ID 1711 stores the requester ID. The requester evaluation level 1712 stores the requester evaluation level.

[0162] The recommendation unit 130 of the proxy request support device 100 of the third embodiment stores the basic information table 1 Compare the desired requester level 1856 of 850 with the requester's evaluation in the requester evaluation table 1710 However, even if the agent is extracted by the agent extraction unit 120, the desired requester record of the agent may be For clients who do not meet the above criteria, the agency will not be recommended to them.

[0163] As described above, the matching support system 1 of the third embodiment receives evaluations of clients from agents. If the requester does not meet the level that the agent has registered in advance, The agent will not be recommended to the client. I would prefer not to accept requests from clients, and I would prefer not to accept requests from clients that could lead to trouble. We can respond to the wishes of agents who do not want to accept the request.

[0164] In the above, the proxy request support device 100 of the second embodiment is used as a base to implement the proxy request support device of the third embodiment. The case where the switching support system 1 is configured has been described, but the proxy of the first embodiment can be configured in a similar manner. Even if the matching support system 1 of the third embodiment is configured based on the request support device 100, good.

[0165] Although the embodiments have been described above, the present invention is not limited to the above embodiments. The present invention includes various modifications and is not necessarily limited to those having all the configurations described. In addition, it is not possible to replace a part of the configuration of one embodiment with the configuration of another embodiment. It is also possible to add the configuration of one embodiment to the configuration of another embodiment. Some of the configurations of the embodiments can be added to, deleted from, or replaced with other configurations.

[0166] For example, the service that a client wishes to receive from a service provider may be a financial institution, an infrastructure It may also be a service for utilities (electric power companies, gas companies, telecommunications companies, etc.), hospitals, etc. Services may also be used to, for example, search for and deliver information or services, verify the authenticity of information, This may be for the purpose of confirming consent when using the service, or for eliminating the complexity of various procedures. [Explanation of symbols]

[0167] 1. Matching support system 5. Communication Network 100 Proxy request support device 110 Request information receiving unit 115 Request Content Judgment Department 1151 Request Field Determination Department 1152 Difficulty level judgment section 1153 Work amount judgment section 120 Agency Extraction Department 1201 1st extraction part 1202 Second extraction part 1203 Third extraction part 125 Agency Organization Evaluation Department 130 Recommendation Department 135 Agent Request Department 140 Reliability judgment table generation unit 145 Specialty field determination table generation unit 1451 Field-specific Experience Calculation Department 1452 Specialty Field Candidate Generation Unit 150 Agency competency display section 155 Request Evaluation Registration Department 170 Client Information DB 1710 Requester Evaluation Table 180 Agency competency DB 1801 Difficulty judgment result 1802 Work amount judgment result 1805 Application form 1810 Reliability Judgment Table 1820 Specialty Field Judgment Table 1830 Workload Judgment Table 185 Agency information DB 1850 Basic Information Table 1860 Substitution History Table 1870 Request Status Table 190 Workload determination table generation unit 191 Requester Level Registration Department 192 Client Evaluation Registration Department 200 Requester terminal 2700 Requester Level Reception Screen 300 Agent Terminal

Claims

1. When a requester requests a service provider to provide a service, the requester and the service provider A system for supporting matching between providers, The information processing device includes a processor and a storage device, basic information relating to each of the plurality of providers; Request information, which is information regarding the request received from the requester; A reliability level, which is information indicating the degree of reliability of each of the plurality of providers; and information indicating the expertise of each of the providers in the service; Remember, a difficulty level determination unit that determines the difficulty level of the request based on the request information; The provider having a higher reliability is extracted for the request having a higher degree of difficulty. A first extraction result listing candidates for service providers extracted from the basic information and the extracted results. a first extractor for producing a fruit; The more difficult the request, the more specialized the provider of the service. The service provider candidates are extracted from the first extraction result, and the extracted a second extraction unit that generates a second extraction result that describes the result; A matching support system that includes:

2. The matching support system according to claim 1, The reliability is determined based on the provider's experience in each field of the service, the number of cases in which the service is provided, and other factors. and the success rate of the service, Matching support system.

3. The matching support system according to claim 1, The level of expertise is determined based on the provider's experience in each field of the service, the division of the service, etc. The number of services provided by each field, the client's evaluation of the services provided, and the services received from the provider identified based on at least one of the areas of expertise they have acquired, Matching support system.

4. The matching support system according to claim 1, The provider candidates based on the second extraction result are displayed on the requester via a user interface. Recommendation section to present to customers, A matching support system further comprising:

5. The matching support system according to claim 1, Further storing a schedule of each of the providers' available working times; the difficulty level determination unit determines the difficulty level for each element of the request, a workload determination unit that calculates a workload for each difficulty level of the request; the first extraction unit generates the first extraction result for each of the difficulty levels; the second extraction unit generates the second extraction result for each of the difficulty levels; In the second extraction result for each level of difficulty, which can correspond to the amount of work for each level of difficulty, A third extraction result is generated in which the extracted combinations are described. Further provided is a third extraction unit Matching support system.

6. The matching support system according to claim 5, The provider candidates based on the third extraction result are displayed on the requester via a user interface. Recommendation section to present to customers, A matching support system further comprising:

7. The matching support system according to claim 5, The donors constituting the combination are included in a combination of donors belonging to different organizations. Matching support system.

8. The matching support system according to claim 4, a requester evaluation registration unit that receives and stores evaluations from the provider regarding the requester who has received a request in the past; a desired requester level registration unit that receives and stores a desired requester level, which is an evaluation threshold used to determine a desired requester, from the provider; Further provided with the recommendation unit does not present to the requester any provider that does not meet the desired requester level in the evaluation by the requester among the provider candidates based on the second extraction result; Matching support system.

9. The matching support system according to claim 6, a requester evaluation registration unit that receives and stores evaluations from the provider regarding the requester who has received a request in the past; a desired requester level registration unit that receives and stores a desired requester level, which is an evaluation threshold used to determine a desired requester, from the provider; Further provided with the recommendation unit does not present to the requester any provider that does not meet the desired requester level in the evaluation by the requester among the provider candidates based on the third extraction result. Matching support system.

10. When a requester requests a service provider to provide a service, the requester and the service provider A method for supporting matching between providers, comprising: An information processing device having a processor and a storage device, basic information relating to each of the plurality of providers; Request information, which is information regarding the request received from the requester; A reliability level, which is information indicating the degree of reliability of each of the plurality of providers; and information indicating the expertise of each of the providers in the service; storing the determining the difficulty level of the request based on the request information; The provider having a higher reliability is extracted for the request having a higher degree of difficulty. A first extraction result listing candidates for service providers extracted from the basic information and the extracted results. generating a result; and The more difficult the request, the more specialized the provider for the service is extracted. The service provider candidates are extracted from the first extraction result so that the extracted result generating a second extraction result describing the A matching support method that implements the above.

11. The matching support method according to claim 10, The information processing device displays the provider candidates based on the second extraction result through a user interface. presenting the request to the requester via an interface; A matching support method that further implements the above.

12. The matching support method according to claim 10, The information processing device, further storing a schedule of available working times of each of the providers; A step of determining the difficulty level for each element of the request; Calculating the amount of work for each level of difficulty of the request; generating the first extraction result for each of the difficulty levels; generating the second extraction result for each of the difficulty levels; and In the second extraction result for each level of difficulty, which can correspond to the amount of work for each level of difficulty, A third extraction result is generated in which the extracted combinations are described. a step of forming a A matching support method that further implements the above.

13. The matching support method according to claim 12, The information processing device displays the provider candidates based on the third extraction result through a user interface. presenting the request to the requester via an interface; A matching support method that further implements the above.

14. The matching support method according to claim 11, The information processing device, Accepting and storing evaluations from the provider regarding the requester who has received a request in the past Step, The provider provides a desired requester level, which is an evaluation threshold used to determine the desired requester. receiving and storing steps; Among the candidate providers based on the second extraction result, the evaluation of the requester is a step of not presenting to the requester any provider who does not meet the level of a specialist; A matching support method that further implements the above.

15. The matching support method according to claim 13, The information processing device, Accepting and storing evaluations from the provider regarding the requester who has received a request in the past Step, The provider provides a desired requester level, which is an evaluation threshold used to determine the desired requester. receiving and storing steps; Among the candidate providers based on the third extraction result, the evaluation of the requester is a step of not presenting to the requester any provider who does not meet the level of a specialist; A matching support method that further implements the above.

Images