Business management server, business management method, and program
The business management server and method address the challenge of skill mismatch in diverse work environments by matching task requests with support capabilities, enhancing workload distribution and skill development.
Patent Information
- Application Number
- JP2023074119
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-28
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2043-04-28
AI Technical Summary
Existing systems fail to adequately allocate work tasks among employees with diverse skills, particularly in jobs with varied work content, leading to insufficient support for employees who need assistance.
A business management server and method that matches request information from clients with support information from supporters, enabling task allocation and evaluation, with rewards for successful completions.
Facilitates the transfer of tasks from employees with heavy workloads to others with appropriate skills, reducing overtime and improving skill development across the workforce.
Smart Images

Figure 2024158709000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a service management server, a service management method, and a program. [Background technology]
[0002] In recent years, one of the management issues is to promote the work-life balance of employees and improve labor productivity. In order to solve these management issues, it is useful to level out the workload that differs from employee to employee and reduce the total actual working hours of the entire company. In order to level out the workload of employees, a system that assigns tasks to all employees has been developed. For example, Patent Document 1 discloses a system that classifies task personnel into overtime workers and non-overtime workers based on attendance data and task content data, and assigns the tasks of overtime workers to non-overtime workers whose task content includes low-priority tasks. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-8586 A Summary of the Invention [Problem to be solved by the invention]
[0004] The system of Patent Document 1 is based on the premise that all employees engaged in accounting work have accounting skills and can substitute for other employees' work. For this reason, when applied to a job type with a wide range of work content, such as the power industry, there is a problem that employees who are assigned work do not have sufficient skills to perform the assigned work, and support is not provided to employees who truly need support.
[0005] The present invention has been made against this background, and aims to provide a business management server, a business management method, and a program that make it possible to allocate the work of employees with a heavy work burden to other employees, even in jobs with a wide range of work content. [Means for solving the problem]
[0006] In order to achieve the above object, the business management server according to the present invention comprises: An acquisition unit that acquires request information, which is information regarding the content of a request from a client, and support information, which is information regarding the content of a task that can be supported from a supporter; a matching unit that transmits matching information, which is information indicating that matching has been established, to a supporter terminal of a supporter who has input the support information with which matching has been established when the request information and the support information acquired by the acquisition unit match; Equipped with The acquisition unit acquires evaluation information, which is information regarding an evaluation of the support content of the supporter who provided the support, from a client terminal of a client who entered the request content with which matching was established. Effect of the Invention
[0007] According to the present invention, it is possible to provide a task management server, a task management method, and a program that are capable of allocating tasks of an employee with a heavy workload to other employees, even in jobs with a wide range of tasks. [Brief description of the drawings]
[0008] [Figure 1] 1 is a schematic diagram showing a configuration of a business management system according to an embodiment of the present invention; [Diagram 2] 2 is a block diagram showing a hardware configuration of a service management server according to an embodiment of the present invention; FIG. [Diagram 3] FIG. 1A is a diagram showing an example of a data table in a request information storage unit, FIG. 1B is a diagram showing an example of a data table in a support information storage unit, and FIG. 1C is a diagram showing an example of a data table in a remuneration information storage unit. [Figure 4]10 is a flowchart showing a flow of a request registration process according to an embodiment of the present invention. [Diagram 5] 1 is a flowchart showing a flow of a matching process according to an embodiment of the present invention. [Figure 6] 10 is a flowchart showing a flow of a reward granting process according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, a service management server, a service management method, and a program according to an embodiment of the present invention will be described in detail with reference to the drawings. In each drawing, the same or equivalent parts are denoted by the same reference numerals.
[0010] The business management system according to the embodiment is a system that matches the request contents of a requester who wants to request support from others with the support contents that a supporter who wants to support the work of others can provide, and assigns the work related to the request contents of the requester to the supporter with whom a match is made. A supporter who has completed support for a requester is paid a remuneration set by the requester and a special allowance set by the company according to the number of times the company has provided support. The remuneration set by the requester is paid, for example, at the time of monthly salary payment. Requests by requesters may be limited to, for example, once a week, to avoid a concentration of requests from a particular requester.
[0011] The requester and the supporter are employees (staff) belonging to the same company, etc. Companies, etc. include corporations and organizations other than corporate organizations, such as national and local governments, independent administrative agencies, schools, medical corporations, and social welfare corporations. It is preferable that both the requester and the supporter are anonymous. For example, it is assumed that neither the requester nor the supporter can know the information of the other through the display of a terminal, etc.
[0012] By using the business management system according to the embodiment, the client can reduce overtime hours and obtain useful tools that can be used in future work. In addition, when working with a supporter, the client can improve their skills. The supporter can earn additional income by utilizing their own unique skills, which increases their motivation for work. In addition, by supporting the client, the supporter can maintain skills that cannot be directly used in the department to which the supporter currently belongs, such as advanced skills such as 3D-CAD and programming.
[0013] For companies, this will allow the work load to be equalized among employees, reducing total actual working hours and overtime hours. Also, if the support fee is set lower than the overtime pay, the company can reduce labor costs overall. In addition, the supporter's support allows the requester to improve their skills, and the supporter can maintain skills that cannot be directly utilized in their current department, raising the overall technical capabilities of the company.
[0014] 1, the business management system 1 includes a business management server 100, a client terminal 200, and a supporter terminal 300. The business management server 100, the client terminal 200, and the supporter terminal 300 are connected to each other so as to be able to communicate with each other via a communication network such as the Internet or an intranet.
[0015] The requester terminal 200 is a terminal managed by the requester, and may be, for example, a general-purpose computer. The requester operates the requester terminal 200 to input the request details on an input screen (website) and registers the details in the database of the business management server 100. The request details are arbitrary, but may be, for example, data organization, idea generation, problem solving, document correction, or macro bug handling.
[0016] The supporter terminal 300 is a terminal managed by the supporter, and is, for example, a general-purpose computer. The supporter operates the supporter terminal 300 to input the supportable content related to the business that the supporter can support on an input screen (website), and registers it in the database of the business management server 100. The supportable content is arbitrary, but for example, it is the same or similar content as the request content.
[0017] When the service management server 100 judges that the request contents of the client registered in the database match with the support contents that the supporter can provide, it notifies the supporter that the support contents match the request contents of the client. When the supporter judges that it is possible to provide support for the request contents, it notifies the service management server 100 that it will accept the request.
[0018] When the supporter completes the work related to the request, the client judges whether the support provided by the supporter (delivery) matches the request. If the client judges that the support provided by the supporter matches the request, the client gives a positive evaluation, and if the client judges that the support does not match, the client gives a negative evaluation. When the client notifies the business management server 100 of the positive evaluation, the business management server 100 gives a reward to the supporter. The above is an outline of the configuration of the business management system 1.
[0019] Next, a hardware configuration of the service management server 100 according to the embodiment will be described. As shown in Fig. 2, the service management server 100 includes a communication unit 110, a storage unit 120, and a control unit 130. The units of the service management server 100 are connected to each other via an internal bus.
[0020] The communication unit 110 is a communication interface for the service management server 100 to communicate with external devices, for example, the client terminal 200 and the supporter terminal 300. The communication unit 110 communicates with the external devices, for example, via a communication network.
[0021] The storage unit 120 includes, for example, a random access memory (RAM), a read only memory (ROM), a flash memory, and a hard disk. The storage unit 120 stores programs executed by the control unit 130 and various data. The storage unit 120 also temporarily stores various information and functions as a work memory for the control unit 130 to execute processing. The storage unit 120 further includes a request information storage unit 121, a support information storage unit 122, and a remuneration information storage unit 123.
[0022] As shown in FIG. 3(a), the request information storage unit 121 stores request information regarding the request contents by the requester. The request information includes the requester's employee ID (Identification), requesting department, request contents, delivery date, estimated work time, remuneration amount, and flag. In FIG. 3(a), the delivery date, estimated work time, and remuneration amount are omitted. Items other than the flag are set by the requester, and the flag is set by the processing of the business management server 100. The flag will be described later, and includes an acceptance flag and a completion flag. The requesting department is the department to which the requester belongs. Remuneration is given to the supporter when the support contents by the supporter match the request contents of the requester. The remuneration amount is set at the time of the request by the requester and is preferably selectable alternatively. For example, it may be set to 500 yen or 1,000 yen per support. Hereinafter, the employee ID of the requester may be expressed as the requester ID.
[0023] As shown in FIG. 3(b), the support information storage unit 122 stores support information, which is information regarding the support content that a supporter can provide. The support information includes the supporter's employee ID (supporter ID), support department, support content, available support period, supporter's past department, past support content, support title, and flag. In FIG. 3(b), the available support period, supporter's past department, past support content, and support title are omitted. The support department is the department to which the supporter belongs. Hereinafter, the supporter's employee ID may be referred to as the supporter ID.
[0024] Support titles are given according to the number of times a support is provided. There are three support titles: Beginning Supporter, Apprentice Supporter, and Support Master. A "Beginner Supporter" is given once a month, an "Apprentice Supporter" is given three times a six-month period, and a "Support Master" is given 10 times a year. When an "Apprentice Supporter" or "Support Master" is given, a special allowance may be paid by the company, etc. For example, when a "Apprentice Supporter" is given, a special allowance of 1,500 yen may be paid, and when a "Support Master" is given, a special allowance of 5,000 yen may be paid.
[0025] 3(c), the reward information storage unit 123 stores reward information, which is information about rewards given to supporters for supporting clients. The reward information includes a supporter ID, a client ID, a date and time when the reward was given, and a reward amount.
[0026] Returning to Fig. 2, the control unit 130 includes a processor and controls each unit of the service management server 100. The processor is, for example, a CPU (Central Processing Unit). The control unit 130 also executes the programs stored in the storage unit 120 to execute the request registration process of Fig. 4, the matching process of Fig. 5, and the reward granting process of Fig. 6.
[0027] The control unit 130 functionally includes an acquisition unit 131, a matching unit 132, a flag addition unit 133, a flag change unit 134, and a reward granting unit 135. In the control unit 130, each functional configuration is realized by one processor executing a program stored in the storage unit 120.
[0028] The acquisition unit 131 receives request information from the requester terminal 200 and sequentially stores it in the request information storage unit 121, and also receives support information from the supporter terminal 300 and sequentially stores it in the support information storage unit 122. The acquisition unit 131 may read the request information stored in the request information storage unit 121, or may read the support information stored in the support information storage unit 122.
[0029] The acquisition unit 131 also receives from the supporter terminal 300 acceptance information, which is information indicating that the supporter will accept the request content for which matching has been established. In addition, the acquisition unit 131 receives completion information, which is information indicating that the work related to the request content has been completed, from the supporter terminal 300, and transmits this to the requester terminal 200, and also receives evaluation information, which is information regarding the supporter's evaluation of the support content of the supporter, from the requester terminal 200. Note that data transmission from the service management server 100 to the terminal does not only include transmitting data to the terminal to be received, but also includes, for example, storing data to be received by the terminal in the storage unit 120 of the service management server 100, so that the terminal can receive the data when the terminal inquires of the service management server 100.
[0030] When the request information and support information acquired by the acquisition unit 131 match, the matching unit 132 transmits matching information indicating that matching has been established to the supporter terminal 300. The matching information includes, for example, the request information (excluding the requester ID) and support information for which matching has been established. Whether the request information and support information match is determined based on whether at least one item of the request information matches a corresponding item of the support information. It is preferable that the conditions for establishing matching can be set when the supporter inputs the support information.
[0031] For example, if the request content of the request information matches the available support content of the support information, it may be determined that the request information and the support information match. Also, if the request content of the request information matches the available support content of the support information and the available support period of the support information meets the delivery date and the business forecast period of the request information, it may be determined that the request information and the support information match. Whether the request content and the available support content match may be determined, for example, on a word-by-word basis. In addition, for example, a desired remuneration amount may be included in the support information, and if the remuneration amount of the request information is equal to or greater than the desired remuneration amount of the support information, it may be determined that a match is established.
[0032] When there are multiple pieces of support information that are matched, the matching unit 132 may transmit matching information to the supporter terminals 300 that transmitted each piece of support information. The matching unit 132 may transmit information that matching is not matched again to the supporter terminals 300 that transmitted the second or subsequent task information.
[0033] When the acquisition unit 131 acquires the task information, the flag addition unit 133 adds an assignment acceptance flag to each of the request information and support information for which matching has been established, which are stored in the request information storage unit 121 and the support information storage unit 122. In addition, the flag addition unit 133 transmits the task information received from the supporter terminal 300 to the requester terminal 200.
[0034] When the evaluation information acquired by the acquisition unit 131 is a positive evaluation, the flag change unit 134 changes the accepted flag added to each of the request information and support information stored in the request information storage unit 121 and the support information storage unit 122 to a completed flag. In addition, when the received evaluation information is a negative evaluation, the flag change unit 134 deletes the accepted flag added to the request information stored in the request information storage unit 121. After changing or deleting the flag, the flag change unit 134 transmits the evaluation information acquired from the requester terminal 200 to the supporter terminal 300.
[0035] The evaluation information is information regarding the client's evaluation of the support provided by the supporter. The evaluation by the client may be, for example, a multiple choice evaluation or a numerical evaluation. In a multiple choice evaluation, the client may be allowed to select between "good" and "bad." By deleting the assignment acceptance flag added to the request information, matching with other support information can be performed again, and by leaving the assignment acceptance flag added to the support information as it is, it is possible to avoid the same supporter providing the same support.
[0036] The reward granting unit 135 grants a reward to the supporter who provided support when the evaluation information acquired by the acquisition unit 131 is a positive evaluation. Specifically, when support information in which the task acceptance flag has been changed to a completion flag exists in the support information storage unit 122, reward information is generated by associating the supporter ID included in the support information with the requester ID, reward grant date and time, and reward amount included in the request information in which the task acceptance flag has been changed to a completion flag at the same time, and the reward information is stored in the reward information storage unit 123. The configuration of the business management server 100 has been described above.
[0037] (Request registration process) The flow of the request registration process executed by the business management system 1 will be described below with reference to the flowchart in Fig. 4. The request registration process is a process for registering request information input by a requester in the business management server 100. The request registration process is started when the requester operates the requester terminal 200 to open an input screen on the display, and it is assumed that the business management server 100 has already started up at this point.
[0038] First, when a requester operates the requester terminal 200 to input each item of the request information, the requester terminal 200 acquires the request information (step S201) and transmits it to the business management server 100 (step S202). When the acquisition unit 131 of the business management server 100 receives the request information from the requester terminal 200, it stores it in the request information storage unit 121 (step S101). The above is the flow of the request registration process. One or more requesters repeatedly register requests, and thus multiple pieces of request information are stored in the request information storage unit 121.
[0039] (Matching process) The flow of the matching process executed by the business management system 1 will be described below with reference to the flowchart in Fig. 5. The matching process is a process of matching request information and support information registered in the business management server 100, and inquiring of the supporter who registered the support information for which a match has been established as to whether or not they will accept the job. The matching process is started when the supporter operates the supporter terminal 300 to bring up an input screen on the display. Hereinafter, it is assumed that the request registration process is repeated by one or more requesters, and thus multiple pieces of request information have already been stored in the request information storage unit 121.
[0040] First, when the supporter operates the supporter terminal 300 to input each item of support information, the supporter terminal 300 acquires the support information (step S311) and transmits it to the service management server 100 (step S312). When the acquisition unit 131 of the service management server 100 receives the support information from the supporter terminal 300, it stores it in the support information storage unit 122 (step S111).
[0041] Next, the matching unit 132 of the service management server 100 judges whether the request information stored in the request information storage unit 121 matches the support information stored in the support information storage unit 122 (step S112). If it is judged that the request information and the support information match (step S112; Yes), the process proceeds to step S113. On the other hand, if it is judged that the request information and the support information do not match (step S112; No), the process ends.
[0042] If the result of the process in step S112 is Yes, the matching unit 132 transmits matching information indicating that matching has been established to the supporter terminal 300 (step S113). The matching information includes the request information and support information for which matching has been established. When the supporter terminal 300 receives the matching information from the service management server 100, it displays the information on the display (step S313).
[0043] The supporter checks the matching information displayed on the display of the supporter terminal 300, particularly the request details, delivery date, and estimated work period of the request information, and judges whether or not to provide support to the client within the matching period. The matching period is a fixed period of time, for example, one week, from the time the matching is notified. If the supporter decides to provide support to the client, the supporter inputs to the supporter terminal 300 information indicating that the supporter will accept the work related to the request details, and if the supporter decides not to provide support, the supporter inputs to the supporter terminal 300 information indicating that the supporter will not accept the work. The information indicating that the supporter will accept the work includes the request information and support information for which matching has been established.
[0044] The supporter terminal 300 judges whether the job information has been acquired within the matching period (step S314). If it is judged that the job information has been acquired within the matching period (step S314; Yes), the supporter terminal 300 transmits the job information to the business management server 100 (step S315) and ends the process. On the other hand, if it is judged that the job information has not been acquired within the matching period (step S314; No), the process ends.
[0045] When the flag adding unit 133 of the service management server 100 receives the task acceptance information from the supporter terminal 300 (step S114), it adds an acceptance flag to each of the request information stored in the request information storage unit 121 and the support information stored in the support information storage unit 122 (step S115). Next, the flag adding unit 133 of the service management server 100 transmits the task acceptance information to the requester terminal 200 (step S116) and ends the process.
[0046] When the client terminal 200 receives the task information from the service management server 100, it displays it on the display (step S211). The client can check the task information displayed on the display of the client terminal 200 and know which supporter will perform the service related to the request information. The above is the flow of the matching process.
[0047] (Reward Granting Process) Hereinafter, the flow of the reward granting process executed by the business management system 1 will be described with reference to the flowchart in Fig. 6. The reward granting process is a process for determining whether or not to pay a reward to a supporter based on an evaluation of the support content by a client.
[0048] When the supporter creates a deliverable based on the request content, the supporter operates the supporter terminal 300 to input completion information indicating that the work related to the request content has been completed. The completion information includes the request information and support information for which a match has been established, and information regarding the deliverable. When the supporter terminal 300 acquires the completion information (step S321), it transmits it to the service management server 100 (step S322). When the acquisition unit 131 of the service management server 100 receives the completion information from the supporter terminal 300 (step S121), it transmits it to the client terminal 200 (step S122).
[0049] When the requester terminal 200 receives the completion information from the service management server 100, it displays it on the display (step S221). When the requester checks the completion information displayed on the display, he / she checks the contents of the deliverable. Next, the requester judges whether the deliverable is in line with the request made by the requester, and operates the operation unit of the requester terminal 200 to input evaluation information, which is information related to the evaluation of the deliverable, into the requester terminal 200. If the requester judges that the deliverable is in line with the request made by the requester, he / she gives a positive evaluation, and if he / she judges that it is not in line with the request, he / she gives a negative evaluation. When the requester terminal 200 acquires the evaluation information from the requester (step S222), it transmits it to the service management server 100 (step S223), and ends the process.
[0050] When the acquisition unit 131 of the business management server 100 receives the evaluation information from the client terminal 200 (step S123), the flag change unit 134 judges whether or not a positive evaluation has been given to the received evaluation information (step S124). If it is judged that a positive evaluation has been given to the evaluation information (step S124; Yes), the flag change unit 134 changes the accepted flag added to each of the request information and support information stored in the request information storage unit 121 and the support information storage unit 122 to a completed flag (step S125).
[0051] Next, the reward granting unit 135 generates reward information by associating the supporter ID included in the support information in which the accepted flag has been changed to a completed flag by the flag changing unit 134 with the client ID, reward grant date and time, and reward amount included in the request information in which the accepted flag has been changed to a completed flag at the same time, and stores the information in the reward information storage unit 123 (step S126). After the fixed period has ended, the rewards granted within the fixed period for each supporter ID are totaled, and information regarding the total amount is sent to the pay system in association with the supporter ID. When the pay system receives information regarding the total amount of reward associated with the client ID, it executes processing to add the total amount of reward to the monthly salary paid to the client and pay it.
[0052] On the other hand, if it is determined that the received evaluation information has been negatively evaluated (step S124; No), the flag change unit 134 of the business management server 100 deletes the acceptance flag added to the request information stored in the request information storage unit 121 (step S127). By deleting the acceptance flag added to the request information, matching with other support information is performed again in the matching process of FIG. 5.
[0053] After the process of step S126 or step S127 is completed, the flag change unit 134 transmits the evaluation information acquired from the client terminal 200 to the supporter terminal 300 (step S128), and ends the process. When the supporter terminal 300 receives the evaluation information from the business management server 100, it displays it on the display (step S323), and ends the process. The supporter can check the evaluation information displayed on the display and understand the client's evaluation of the deliverable. The above is the flow of the reward granting process.
[0054] As described above, the business management server 100 according to the embodiment includes an acquisition unit 131 that acquires request information, which is information on the request content from a client, and support information on the business content that can be supported from a supporter, and a matching unit 132 that transmits matching information, which is information indicating that matching has been established, to the supporter terminal of the supporter who input the support information with which matching has been established when the request information and support information acquired by the acquisition unit 131 match, and the acquisition unit 131 acquires evaluation information, which is information on the evaluation of the support content of the supporter who provided the support, from the client terminal of the client who input the request content with which matching has been established. Therefore, the supporter can determine whether to accept the request content from the client in consideration of his / her own ability and workload, and can allocate the work of an employee with a large workload to another employee even in a job with a wide range of work contents.
[0055] The present invention is not limited to the above-described embodiment, and the following modifications are possible.
[0056] (Modification) In the above embodiment, the request information and the support information are distinguished by the information of each item, but the present invention is not limited to this. The request information and the support information may be given an individually assigned identification number, and the request information and the support information may be distinguished by the identification number.
[0057] In the above embodiment, the request information and support information stored in the request information storage unit 121 and the support information storage unit 122 are added with the acceptance flag and the completion flag, but the present invention is not limited to this. For example, the storage unit 120 may be provided with a database for storing the request information and support information for which the supporter has completed the acceptance, and a database for storing the request information and support information for which the supporter has completed the support.
[0058] In the above embodiment, matching is performed at the time when the service management server 100 receives the support information, but the present invention is not limited to this. For example, the support information may be stored in the support information storage unit 122, and matching may be performed at the time when the service management server 100 receives the request information. Also, matching may be performed at the time when the service management server 100 receives either the request information or the support information.
[0059] In the above embodiment, the request information is matched with the support information, and the supporter is notified of the matched request information, but the present invention is not limited to this. For example, the supporter may omit the registration of support contents and matching, and the supporter may read and confirm the request information registered in the service management server 100 on the supporter terminal 300 to determine whether to provide support. If the supporter decides to provide support to the requester, the supporter may operate the supporter terminal 300 to send the request information to the service management server 100.
[0060] In the above embodiment, information about the deliverable is included in the completion information, but the present invention is not limited to this. For example, the deliverable may be provided to the client by attaching it to an email sent from the supporter to the client, or by storing it in a USB (Universal Serial Bus) memory.
[0061] In the above embodiment, no upper limit was set for the remuneration paid to each supporter for each requester, but the present invention is not limited to this. An upper limit payable amount may be set for each preset period, the total amount of remuneration paid to each supporter for each requester may be calculated, and the request information of a requester whose calculated total amount of remuneration exceeds the upper limit may not be registered in the business management server 100.
[0062] In the above embodiment, the supporter is given money as a reward, but the present invention is not limited to this. For example, the supporter may be given an item instead of money as a reward. Also, something other than a reward may be given to the supporter. For example, if the client's evaluation of the support provided by the supporter is a positive evaluation, the evaluation may be reflected in the personnel evaluation of the supporter.
[0063] In the above embodiment, various data are stored in the storage unit 120 of the service management server 100, but the present invention is not limited to this. For example, all or part of the various data may be stored in an external control device or processing unit via a communication network.
[0064] In the above embodiment, the service management server 100 operates based on the programs stored in the storage unit 120, but the present invention is not limited to this. For example, the functional configuration realized by the programs may be realized by hardware.
[0065] In the above embodiment, the service management server 100 is, for example, a general-purpose computer, but the present invention is not limited to this. For example, the service management server 100 may be realized by a processing unit provided on a cloud.
[0066] In the above embodiment, the processing executed by the business management server 100 was realized by an apparatus having the above-mentioned physical configuration executing a program stored in the memory unit 120, but the present invention may also be realized as a program or as a storage medium on which the program is recorded.
[0067] In addition, a program for executing the above-mentioned processing operations may be stored and distributed on a non-transitory recording medium readable by a processing unit, such as a flexible disk, a CD-ROM (Compact Disk Read-Only Memory), a DVD (Digital Versatile Disk), or an MO (Magneto-Optical Disk), and an apparatus for executing the above-mentioned processing operations may be configured by installing the program in the processing unit.
[0068] The above-mentioned embodiments are merely examples, and the present invention is not limited to these, and various embodiments are possible within the scope of the invention described in the claims. The components described in the embodiments and modifications can be freely combined. Furthermore, inventions equivalent to the inventions described in the claims are also included in the present invention. In addition, even if the components of the inventions described in the claims have the same names as the components described in the above-mentioned embodiments, they are not limited to the components described in the above-mentioned embodiments themselves, and can be modified and applied as appropriate. [Explanation of symbols]
[0069] 100 Business Management Server 120 Storage section 121 Request information storage unit 122 Support information storage unit 130 Control section 131 Acquisition Department 132 Matching Section 133 Flag Addition Section 134 Flag change section 135 Reward Department 200 Requester terminal 300 Supporter terminal
Claims
1. An acquisition unit that acquires request information, which is information regarding the content of a request from a client, and support information, which is information regarding the content of a task that can be supported from a supporter; a matching unit that transmits matching information, which is information indicating that matching has been established, to a supporter terminal of a supporter who has input the support information with which matching has been established when the request information and the support information acquired by the acquisition unit match; Equipped with The acquisition unit acquires evaluation information, which is information regarding an evaluation of the support content of the supporter who provided the support, from a client terminal of the client who inputs the request content with which matching has been established. Business management server.
2. The service management server further includes a reward providing unit that provides a reward to a supporter who has provided support when the evaluation information acquired by the acquisition unit is a positive evaluation. The business management server according to claim 1 .
3. The matching unit determines that matching between the request information and the support information is established when at least one item included in the request information matches a corresponding item included in the support information.
3. The business management server according to claim 1 or 2.
4. The service management server includes a database for storing request information and support information, the matching unit compares the request information or support information with the support information or request information stored in the database after the acquisition unit acquires the request information or support information, and determines whether the request information and the support information match each other.
3. The business management server according to claim 1 or 2.
5. The business management server includes a database that stores request information and support information; a flag adding unit which, when receiving acceptance information indicating that support for the requested content has been accepted from the supporter terminal to which the matching information has been transmitted by the matching unit, adds an acceptance flag to each of the request information and support information stored in the database and for which matching has been established; and a flag change unit that changes an accepted flag that is stored in the database and added to each of the request information and the support information for which matching has been established to a completed flag when the evaluation information acquired by the acquisition unit is a positive evaluation.
3. The business management server according to claim 1 or 2.
6. When the evaluation information acquired by the acquisition unit is a negative evaluation, the flag change unit deletes the acceptance flag that has been stored in the database and added to each of the request information and the support information for which matching has been established. The business management server according to claim 5 .
7. A business management method executed by a business management server, comprising: A step of acquiring request information, which is information regarding the content of a request from a requester, and support information, which is information regarding the content of a business that can be supported, from a supporter; a step of transmitting matching information, which is information indicating that matching has been established, to a supporter terminal of the supporter who input the support information with which matching has been established, when the acquired request information and support information match; A step of acquiring evaluation information, which is information regarding an evaluation of the support content of the supporter who provided the support, from a requester terminal of the requester who inputted the request content with which matching was established; A method of managing business operations, including
8. Computer, An acquisition means for acquiring request information, which is information relating to the contents of a request from a client, and support information, which is information relating to the contents of a task that can be supported from a supporter; a matching means for transmitting matching information, which is information indicating that matching has been established, to a supporter terminal of the supporter who inputted the support information with which matching has been established when the request information and the support information acquired by the acquisition means match; A program for causing the device to function as a The acquiring means acquires evaluation information, which is information regarding an evaluation of the support content of the supporter who provided the support, from a client terminal of the client who inputs the request content with which matching has been established. program.
Citation Information
Patent Citations
Matching system, information processing device, matching method, and program
WO2016080038A1
Information processing device, work distribution method and program
JP2019008586A
