JP2023163780A - Information processing system, information processing method and program - Google Patents

Abstract

To provide an information processing system, an information processing method, and a program capable of appropriately providing services.SOLUTION: The information processing system divides a task requested by a client into a plurality of tasks, assigns a task executor to the task for each task, and manages an execution state of each task, and is equipped with executor adjusting means for assigning the executor to the task and assigning another auxiliary executor to execute the task when the executor cannot execute the task.SELECTED DRAWING: Figure 20

Description

The present invention relates to an information processing system, an information processing method, and a program.

Patent Document 1 describes a system that, in order to provide a delivery service, matches goods to be used to provide the service and workers related to the service based on regional information, and plans movement. The matching system described in Patent Document 1 includes a presentation means, a reception means, a matching means, and a planning means. The presentation means presents services that can be provided based on the local information. The reception means receives the selection of the service presented by the presentation means. The matching means matches one or more processors who process one or more tasks required for providing the service accepted by the reception means. The planning means plans the movement of workers or goods corresponding to each of the one or more tasks based on the matching result by the matching means.

International Publication No. 2019/180942

In the matching system described in Patent Document 1, when a service is provided, a plurality of tasks required for providing the service are processed based on matching details and plans determined in advance. Therefore, there is a problem that, for example, if it becomes difficult to process a task at the stage of providing a service, the service may not be able to be provided appropriately.

SUMMARY OF THE INVENTION Therefore, an object of the present invention is to provide an information processing system, an information processing method, and a program that can appropriately provide services.

One aspect of the present invention provides information for dividing work requested by a requester into a plurality of tasks, assigning an executor of the task to each task, and managing the execution status of each task. The processing system includes performer coordination means. The executor adjustment means assigns the executor to the task, and also assigns another auxiliary executor who executes the task when the executor is unable to execute the task.

One aspect of the present invention provides information for dividing work requested by a requester into a plurality of tasks, assigning an executor of the task to each task, and managing the execution status of each task. This is a processing method. The information processing method includes the steps of assigning the executor to the task, and assigning another auxiliary executor to execute the task if the executor is unable to perform the task.

One aspect of the present invention is to divide work requested by a requester into a plurality of tasks, assign an executor of the task to each task, and manage the execution status of each task. This is a program that causes a computer to perform the next step. The program causes the computer to execute the steps of assigning the executor to the task and assigning another auxiliary executor to execute the task if the executor is unable to perform the task.

According to the information processing system, information processing method, and program of the present invention, services can be provided appropriately.

1 is a block diagram showing a configuration example of an information processing system according to an embodiment of the present invention. FIG. 2 is a schematic diagram showing a configuration example of a task DB according to an embodiment of the present invention. FIG. 2 is a schematic diagram showing a configuration example of a vendor DB according to an embodiment of the present invention. FIG. 2 is a schematic diagram showing a configuration example of a request information DB according to an embodiment of the present invention. It is a schematic diagram showing an example of composition of evaluation DB concerning an embodiment of the present invention. FIG. 2 is a schematic diagram showing an example of the order of execution of tasks according to an embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. 3 is a flowchart showing an example of the operation of the information processing system according to the embodiment of the present invention. FIG. 2 is a schematic diagram for explaining the operation of the information processing system according to the embodiment of the present invention. 1 is a block diagram showing a basic configuration example of an information processing system according to an embodiment of the present invention. 1 is a flowchart illustrating a basic operation example of an information processing system according to an embodiment of the present invention. FIG. 1 is a block diagram showing an example of the basic configuration of a computer according to an embodiment of the present invention.

Embodiments of the present invention will be described below with reference to the drawings. In addition, in each figure, the same reference numerals are used for the same or corresponding components, and the description thereof will be omitted as appropriate.

(Configuration of information processing system)
FIG. 1 is a block diagram showing a configuration example of an information processing system according to an embodiment of the present invention. The information processing system 200 shown in FIG. 1 includes an adjustment system 100, one or more client terminals 3, a counter system 4, and one or more vendor terminals 7. In the present embodiment, the information processing system 200 supports matching of a pesticide spraying requester with a plurality of businesses providing resources related to pesticide spraying in a pesticide spraying business using unmanned aerial vehicles (hereinafter referred to as drones). It is a system. Note that in this embodiment, the trader is a person who executes a task to be described later, and may be an individual or an organization such as a corporation. However, the scope of application of the information processing system according to this embodiment is not limited to this example.

Adjustment system 100 can be configured using one or more computers. The adjustment system 100 includes the following parts as a functional configuration consisting of a combination of one or more computers, programs executed by the computers, software such as files used by the computers, and the like. That is, the coordination system 100 includes a request information DB (database) 5, a vendor coordination section 8, a vendor DB 2, a task DB 1, an evaluation DB 6, a schedule coordination section 9, an execution status management section 10, and a backup coordination section. 11, an incentive management section 12, and an order DB 13. Hereinafter, each component will be explained in order of reference numerals.

FIG. 2 shows an example of the table configuration of the task DB1. The task DB1 shown in FIG. 2 includes task numbers in each record. (number), the type of task, and the unit price of the task. Note that, in this embodiment, a task is a unit of work that is obtained by dividing a series of jobs, works, etc. for performing a pesticide spraying service according to the type of work. Note that the types of work can be classified, for example, according to the types of resources such as people, equipment, and materials. In this embodiment, task No. is a number assigned to identify the type of task. Each task No. uniquely identifies the type of task. The task type is a classification of tasks according to the nature of the task. In this embodiment, the types of tasks are classified into a drone rental task, a drone operation task, a pesticide provision task, a pesticide delivery task to the site, a drone delivery task to the site, a drone recovery task from the site, and the like. Note that the pesticide provision task is further classified according to the type of medicine. The unit price of a task is expressed, for example, as a price (fee) per unit time, a price per unit area for pesticide spraying, or a price per unit travel distance required for delivery or collection. In the example shown in FIG. 2, for example, task No. The type of task of =11 is a drone rental task.

FIG. 3 shows an example of the table structure of the vendor DB2. The vendor DB 2 shown in FIG. 3 includes a vendor ID and a task number in each record. , the vendor name, the vendor's address, the vendor's telephone number, and the vendor's terminal information for contacting the vendor. The vendor ID is a number assigned to identify the vendor. Task No. is the task number of the task that can be handled by the vendor with the corresponding vendor ID. It is. Task No. is common to the task DB1 and the vendor DB2. The vendor terminal information for contacting the vendor is, for example, the vendor's e-mail address. In the example shown in FIG. 3, the vendor with vendor ID=101 has task No. =11 (drone rental task) and task No. =21 (drone operation task) and task No. =51 (drone delivery task) and task no. =61 (drone recovery task).

The client terminal 3 is, for example, a personal computer, a tablet terminal, a smartphone, or the like, and is operated by a client for pesticide spraying. The client terminal 3 accesses the counter system 4 and inputs, for example, the client's name, the client's address, the desired date and time of pesticide spraying, the selection of the type of pesticide, the pesticide spraying address, the pesticide spraying area information, and the counter system 4 Perform propagation to Note that in this embodiment, propagation refers to the transmission and reception of a series of predetermined data between a transmitting side and a receiving side when transmitting predetermined information. In addition, in this embodiment, the requester side inputs information such as the requester's name, the requester's address, the desired date and time of pesticide spraying, the selection of the type of pesticide, the pesticide spraying address, the pesticide spraying area information, etc. when requesting the request contents. The information is called request information. Further, the client terminal 3 displays, for example, consent confirmation information for service provision in the request information received from the counter system 4. Further, the client terminal 3 transmits, for example, information on whether or not to accept the service provision determined by the client based on the consent confirmation information on the service provision to the counter system 4, and also transmits the completion information of the service provision in the request information. Receive.

The counter system 4 is configured, for example, as a Web server using one or more computers. When the counter system 4 receives the request information propagated from the client terminal 3, the counter system 4 selects the request No. The request information is propagated to the adjustment system 100 and stored in the request information DB 5. Request No. is a number given to the request information to identify the request information. Further, the counter system 4 receives the request No. from the adjustment system 100. If you receive information on the possibility of providing the service, please send the request number to confirm the consent to provide the service. The information is propagated to the corresponding client terminal 3. Further, the counter system 4 receives the request No. from the client terminal 3. When receiving information on whether or not to accept the service provision, the information is propagated to the coordination system 100. Further, the counter system 4 receives the request No. from the adjustment system 100. and service provision completion information is received, Request No. The service provision completion information is propagated to the corresponding client terminal 3.

FIG. 4 shows an example of the table configuration of the request information DB 5. The request information DB 5 includes request No. in each record. , request information, service provision status, and each task number. status and each task number. Executor ID and each task number. Executor price and each task number. backup company ID and each task number. It is configured as a table that associates the prices of the backup companies with the prices of the backup companies. In this case, the request information includes the requester's name, the requester's address, the desired date and time of pesticide spraying, the selection of the type of pesticide, the pesticide spraying address, and the pesticide spraying area information. The vendor ID is common to the vendor DB2 and the request information DB5. The service provision status represents information on whether the service can be provided, information on whether or not the service can be accepted (acceptance or cancellation), and information on the completion of the service provision. The status represents task progress information, task completion information, information indicating that the task cannot be executed before or after starting the task, and the like. The execution company ID is the company ID of the company that executes the task. The backup vendor ID is the vendor ID of a vendor who executes the task instead when the vendor with the execution vendor ID becomes unable to execute the task. The executing agent price is the price when the task is executed by the agent having the executing agent ID. The backup vendor price is the price when the vendor with the backup vendor ID executes the task. In addition, in FIG. 4, the status of task #○○ is indicated, but this number "○○" does not represent the execution order of the tasks. In this embodiment, the task execution order is predefined in an order DB 13, which will be described later, based on a combination of tasks. Also, each request no. The number of tasks (“n” in FIG. 4) associated with the task is determined according to the request information.

FIG. 5 shows an example of the table configuration of the evaluation DB 6. The evaluation DB 6 associates a vendor ID with vendor evaluation information in each record. The vendor ID is common to the vendor DB2 and the evaluation DB6. The vendor evaluation information is information representing incentives for the vendor (hereinafter referred to as vendor evaluation information).

In this embodiment, for each task, a trader who executes the task is registered, and a trader who will execute the task if the trader is unable to execute the task is registered in advance as a backup. In this case, in this embodiment, if the task could not be executed, the evaluation represented by the company evaluation information of the company concerned is lowered, and if the task was executed as a backup, the evaluation represented by the company evaluation information of the company concerned is increased. This provides an incentive for vendors to register as backups. Note that in this embodiment, the evaluation represented by the vendor evaluation information affects, for example, the priority of assigning tasks during the next and subsequent work.

The trader terminal 7 is, for example, a personal computer, a tablet terminal, a smartphone, or the like, and is operated by a trader assigned a trader ID who wishes to perform tasks related to agricultural chemical spraying. For example, the vendor terminal 7 receives task No. from the adjustment system 100. and request no. and recruitment information (hereinafter referred to as recruitment information) based on the request information. Further, the vendor terminal 7 may receive a request number specified by the vendor based on recruitment information, for example. and task no. Information (hereinafter referred to as application information) indicating that execution and/or backup support for the task is possible is propagated to the adjustment system 100. Further, the vendor terminal 7, for example, requests request no. and task no. , information on whether or not to accept the service provision, and task start information are received from the coordination system 100 . Further, the vendor terminal 7 may, for example, request request No. after starting the task. Task No. progress status information and task completion information of the task corresponding to , or status information indicating that the task cannot be executed before or after starting the task (hereinafter referred to as task execution impossible information) is propagated to the adjustment system 100.

The vendor adjustment department 8 records the request No. in the request information DB 5. When the request information corresponding to is stored, the vendor evaluation information corresponding to the vendor ID in the evaluation DB 6 is referred to, and the request information is sent to the vendor corresponding to the vendor ID in the vendor DB 2 that is related to at least one highly rated vendor ID. Request No. using the contact information. and the task number of the vendor ID. and recruitment information are preferentially propagated to the vendor terminal 7 corresponding to the vendor ID. Further, when receiving application information from the vendor terminal 7 corresponding to at least one vendor ID, the vendor adjustment unit 8 stores the vendor IDs (hereinafter, task execution vendor IDs) of task executors that can execute tasks in the order received. ) and a vendor ID (hereinafter referred to as backup vendor ID) of a vendor who can execute the task as a backup when the task execution vendor is unavailable (hereinafter referred to as backup vendor ID). Further, the vendor adjustment unit 8 assigns the task execution vendor ID to the request number in the request information DB 5. Task No. corresponding to Stored in the executor ID. Further, the vendor adjustment unit 8 stores the backup vendor ID as the request number in the request information DB 5. Task No. corresponding to Stored in the backup company ID. Further, after all the task execution vendor IDs and backup vendor IDs corresponding to the request information are collected, the vendor adjustment unit 8 stores the service provision possibility information in the service provision status, and stores the service provision possibility information in the service provision status. is propagated to the counter system 4. Further, the vendor adjustment department 8 receives the corresponding request No. from the counter system 4. When receiving the request information DB 5, the service provision status in the request information DB 5 is referred to. Further, if the service provision approval/disapproval information in the service provision status is the service provision approval/disapproval information, the vendor coordination unit 8 determines whether the request No. Task No. At least one task number corresponding to The vendor ID and task number of the executing vendor ID. This information is propagated to the vendor terminal 7 corresponding to the vendor ID using the contact information for the vendor corresponding to the vendor ID in the vendor DB 2 that is related to the vendor ID of the backup vendor ID. Further, the vendor adjustment department 8 receives the corresponding request No. from the counter system 4. When the request No. is received, the service provision status is referred to, and if the service provision disapproval information is received as the service provision approval/disapproval information, the corresponding request No. Task No. At least one task number corresponding to The vendor ID and task number of the executing vendor ID. This information is propagated to the vendor terminal 7 corresponding to the vendor ID using the contact information for the vendor corresponding to the vendor ID in the vendor DB 2 that is related to the vendor ID of the backup vendor ID.

The schedule adjustment unit 9 receives the request No. from the counter system 4. When receiving the request, the service provision status is referred to, and if the service provision is acceptable information, the request number in the request information DB 5 is determined according to the predefined task order shown in FIG. 6. ．． At least one task number corresponding to If there is no status information, refer to the status of the task No. Register task start information in the status. FIG. 6 shows an example of the order of tasks defined in the order DB 13, which will be described later.

The example shown in FIG. 6 is based on a certain request No. Each task corresponds to the task No. described with reference to FIG. is "11", "12", "31", "41", "51", and "61". In the example shown in FIG. 6, task No. After the pesticide provision task (drug A) of =31 is executed, task No. =41 pesticide delivery tasks to the field are executed. Also, task no. After the drone lending task of =11 is executed, task No. =51 drone delivery tasks to the site are executed. And task no. = 41 pesticide delivery tasks to the field and task no. After the drone delivery task to the site of =51 is executed, task No. =12 drone operation tasks are executed and pesticide spraying is carried out. Also, task no. After the drone operation task of =12 is executed, task No. =61 drone recovery tasks are executed. Note that in the example shown in FIG. 6, before starting the task, task No. = Executor ID = "105", "103", "101", "107" for the tasks "11", "12", "31", "41", "51" and "61", respectively. "109" and "111" are registered. Also, before starting a task, task No. = Backup vendor ID = "106", "104", "102", "108" for the tasks "11", "12", "31", "41", "51" and "61" respectively, "110" and "112" are registered.

The schedule adjustment unit 9 also requests request no. At least one or more task No. of the request information DB 5 corresponding to Using the contact information for the vendor corresponding to the vendor ID in the vendor DB2 that is related to the vendor ID of the executing vendor ID, task No. request No. to the vendor terminal 7 of the vendor ID of the executing vendor ID. and task no. and propagate task start information. Also, the schedule adjustment unit 9 selects the task No. When task completion information is registered in the status of , the next task No. is registered in the predefined task order as shown in FIG. At least one or more task No. in the request information DB 5 corresponding to Register the task start to the status. The schedule adjustment unit 9 also requests request no. At least one or more next task No. in the request information DB 5 corresponding to Using the contact information for the vendor corresponding to the vendor ID in the vendor DB2 that is related to the vendor ID of the executing vendor ID, task No. request No. to the vendor terminal 7 of the vendor ID of the executing vendor ID. and task no. and propagate task start information. Further, the schedule adjustment unit 9 selects all the task numbers in the request information DB 5 in the predefined task order as shown in FIG. When task completion information is registered in the status of , the task No. in the corresponding request information DB5 is registered. Register service provision completion information in the service provision status of . The schedule adjustment unit 9 also sends request No. to the counter system 4. and propagate completion information of service provision.

The execution status management unit 10 receives vendor IDs from the vendor terminals 7 corresponding to at least one vendor ID and the request number associated with the recruitment information. Task No. When task completion information corresponding to task number is received, the task number is changed as follows. Register task completion information in the status. That is, the execution status management unit 10 stores the request No. related to the vendor ID. Task No. At least one or more task No. of the request information DB 5 corresponding to The vendor ID or task number of the executing vendor ID. Task No. corresponding to the backup vendor ID of Register task completion information in the status. The execution status management unit 10 also stores the vendor ID of the vendor terminal 7 and the request number. Task No. If the vendor ID of the backup vendor ID matches, request No. and task no. and task no. The backup vendor ID of the backup vendor ID and task completion information (hereinafter referred to as backup execution completion information) are propagated to the incentive management unit 12, which will be described later. Further, the execution status management unit 10 receives the vendor ID from the vendor terminal 7 corresponding to at least one vendor ID and the request number associated with the recruitment information. Task No. When task execution impossible information corresponding to is received, request No. related to the vendor ID is received. Task No. At least one or more task No. in the request information DB 5 corresponding to Task No. corresponding to the vendor ID of the executing vendor ID. Register task execution impossible information in the status. The execution status management unit 10 also handles the request No. and the vendor ID and task number of the vendor terminal 7. and the task execution impossible information is propagated to the backup adjustment unit 11.

The backup adjustment unit 11 receives the request No. from the execution status management unit 10. and the vendor ID and task number of the vendor terminal 7. and task execution impossible information is received, Request No. and task no. Task No. of request information DB5 corresponding to Register backup task start information in the status. In addition, the backup adjustment unit 11 requests request no. and task no. Task No. corresponding to Using the contact information for the vendor corresponding to the vendor ID in the vendor DB 2 that is related to the vendor ID of the backup vendor ID, the task start is propagated to the vendor terminal 7 of the corresponding vendor ID. The backup adjustment unit 11 also receives the request No. received from the execution status management unit 10. and task no. and the vendor ID and task number of the vendor terminal 7. Task No. corresponding to The vendor ID of the backup vendor ID (hereinafter referred to as incentive change information) is propagated to the incentive management unit 12.

The incentive management unit 12 receives the backup execution completion information from the execution status management unit 10 and the incentive change information from the backup adjustment unit 11, and receives the request number of the backup execution completion information and incentive change information. and task no. and task no. Compare the backup vendor IDs of the backup vendor IDs. If the comparison results match, the incentive management unit 12 subtracts the value of the vendor evaluation corresponding to the vendor ID in the evaluation DB 6 that is related to the vendor ID of the vendor terminal 7 that is unable to execute the task of the incentive change information. In addition, if the comparison results match, the incentive management unit 12 selects the task number of the incentive change information. The corresponding vendor evaluation value is added to the vendor ID of the evaluation DB 6 that is related to the vendor ID of the backup vendor ID.

The order DB 13 stores information that defines the order of execution of each task, as described with reference to FIG. 6, for example, for all combinations of multiple types of tasks that can be provided. The order DB 13 includes, for example, task No. = Task No. 31 (pesticide supply task) with different chemicals. =3x tasks, information defining the order similar to the example shown in FIG. 6 is stored.

Note that the vendor adjustment section 8 is an example of the configuration of the executor adjustment means according to the present invention. An executor is an example of an executor. A backup vendor is an example of an auxiliary performer. The incentive management unit 12 is an example of the configuration of incentive management means. The backup adjustment unit 11 is an example of a configuration of a backup adjustment means.

(Example of operation of information processing stem)
An example of the operation of the information processing system 200 according to the embodiment of the present invention described with reference to FIGS. 1 to 6 will be described with reference to FIGS. 7 to 18. 7 to 18 are flowcharts showing operational examples of the information processing system according to the embodiment of the present invention.

As shown in Figures 7 to 18, a client who wishes to provide a pesticide spraying service using a drone uses the client terminal 3 to provide request information (client's name, client's address, pesticide spraying request). (date and time, selection of type of pesticide, pesticide spraying address, pesticide spraying area information, etc.) are propagated to the window system 4 (S101 in FIG. 7).

The counter system 4 stores the received request information and the request number assigned to the request information. is stored in the request information DB5, and the request No. Information indicating that the service provision request has been accepted is stored in the service provision status section of the request information DB 5 corresponding to (S102). The counter system 4 also sends request no. is propagated (S103).

The vendor adjustment department 8 receives the request No. from the counter system 4. (S103), the request No. of the request information DB5 is received. The corresponding service provision status location is referred to (S104). If the service provision status location indicates that the service provision request has been accepted, the vendor adjustment unit 8 refers to the vendor evaluation information location corresponding to the vendor ID in the evaluation DB 6 (S105). The trader adjustment unit 8 refers to the trader terminal 7 information of the trader corresponding to the trader ID in the trader DB 2 related to the trader ID in order of high evaluation value (S106). The vendor adjustment unit 8 sends request numbers to the vendor terminal 7 in order of highest evaluation value. and request no. All task numbers corresponding to the request information in the request information DB5 and the vendor ID in the vendor DB2. is propagated as recruitment information (S107).

At least one or more vendors receive request No. from the vendor coordination department 8 on the vendor terminal 7. and request no. The request information corresponding to the request information DB5 and all the task numbers corresponding to the vendor ID of the vendor DB2. When receiving the task number, the vendor receives the task number. Information (application information) and the corresponding task number whether it is possible to execute the task only for each task, or only as a backup at the time of task execution, or both. and request no. is propagated to the vendor adjustment unit 8 (S108).

The vendor adjustment unit 8 receives request No. from at least one vendor terminal 7. and at least one task number. and at least one task number. When receiving application information corresponding to (S108), request No. Task No. Task No. of request information DB5 corresponding to Executor ID location and task number. (S109 in FIG. 8). After this, the vendor adjustment department 8 issues the request No. Task No. Task No. of request information DB5 corresponding to It is determined whether the vendor ID is not stored in the executor ID section of , and the application information allows only task execution or both. If the vendor adjustment unit 8 does not store the vendor ID and the application information allows only task execution or both, the vendor adjustment unit 8 assigns the corresponding vendor ID to the request number. Task No. Task No. of request information DB5 corresponding to (S110).

In addition, the vendor coordination department 8 requests request no. Task No. Task No. of request information DB5 corresponding to Although the vendor ID is stored in the executor ID section of task No. It is determined whether a vendor ID is not stored in the backup vendor ID location and the application information allows the task to be executed only as a backup, or whether it is possible to perform both tasks. The vendor coordination department 8
If the vendor ID is not stored and the application information can only be used as a backup, or if both can be used, please enter the corresponding vendor ID as the request number. Task No. Task No. of request information DB5 corresponding to (S110).

Furthermore, the vendor coordination department 8 requests request no. Task No. of all tasks in the request information DB5 corresponding to Executor ID location and task number. If the vendor ID is stored in the backup vendor ID location of Request No. The service provision possibility information is stored in the service provision status section of the request information DB 5 corresponding to (S111). Further, the vendor adjustment department 8 sends request No. to the counter system 4. is propagated (S112). Note that the vendor adjustment unit 8 will continue to receive the same request No. from the vendor terminal 7. When application information corresponding to is received, recruitment completion information is propagated to the vendor terminal 7 that received the application information (S113).

The counter system 4 receives request No. from the vendor coordination department 8. (S112), the request No. of the request information DB5 is received. The corresponding service provision status location is referred to (S114 in FIG. 9). In the case of service provision possibility information, the counter system 4 requests request No. The requester information in the request information in the request information DB 5 corresponding to the request information is referred to (S115), and the request No. is sent to the requester terminal 3 based on the requester information. , request information, and information requesting permission to provide the service (information regarding permission to provide the service) are transmitted (S116).

After the client receives the request information and the information on whether or not to accept the provision of the service from the counter system 4 on the client terminal 3, the client terminal 3 receives the result information (service provision (acceptance result information) and its request no. is propagated to the counter system 4 (S117).

The counter system 4 receives request No. from the client terminal 3. and service provision consent result information is received (S117), and if the service provision consent result information is approval, information on whether the service provision can be accepted is received, and if it is cancellation, information on the non-acceptance of the service provision is received. ．． is stored in the service provision status location of the request information DB 5 corresponding to (S118). In addition, the counter system 4 has request no. is propagated to the vendor adjustment unit 8 and schedule adjustment unit 9 (S119).

The vendor adjustment department 8 receives the request No. from the counter system 4. (S119), the request No. of the request information DB5 is received. The corresponding service provision status location is referred to (S120 in FIG. 10).

On the other hand, if the service provision status location is information that allows the service provision to be accepted, the vendor coordination unit 8 selects the request No. At least one or more task No. in the request information DB 5 corresponding to The contractor ID stored in the executor ID section of , and the task number. Refers to the information on the vendor terminal 7 of the vendor corresponding to the vendor ID in the vendor DB 2 that is related to the vendor ID stored in the backup vendor ID section of (S121).

Further, the vendor coordination unit 8 sends the request No. to the vendor terminal 7 along with the information on which the service has been approved. and request no. The request information in the request information DB5 corresponding to the request information and the request No. corresponding to the vendor ID. At least one or more task No. in the request information DB 5 corresponding to Executor ID and task number. Task No. in the backup company ID section. is propagated (S122).

On the other hand, if the service provision status location is the information that the service provision cannot be approved, the vendor coordination unit 8 selects the request No. At least one or more task No. in the request information DB 5 corresponding to The contractor ID stored in the executor ID section of , and the task number. Refers to the vendor terminal 7 of the vendor corresponding to the vendor ID in the vendor DB 2 that is related to the vendor ID stored in the backup vendor ID section of (S121).

Further, the vendor adjustment unit 8 sends request No. 8 to the vendor terminal 7 along with information that the service provision has been cancelled. and request no. The request information in the request information DB5 corresponding to the request information and the request No. corresponding to the vendor ID. At least one or more task No. in the request information DB 5 corresponding to Executor ID and task number. Task No. in the backup company ID section. is propagated (S122).

The schedule adjustment unit 9 receives the request No. from the counter system 4. (S119 in FIG. 9), the request No. in the request information DB5 is received. The corresponding service provision status location is referred to (S123 in FIG. 11). When the service provision status location is the service provision approval information, the schedule adjustment unit 9 selects the predefined task number as described with reference to FIG. According to the order of request No. of request information DB5. At least one task number corresponding to (S124), and if there is no status information, the task No. The task start information is registered in the status field (S125). Thereafter, the schedule adjustment unit 9 selects the request No. in the request information DB 5. At least one task number corresponding to Refer to the contact information for the vendor corresponding to the vendor DB2 vendor ID that is related to the vendor ID in the executor ID section (S126). Also, the schedule adjustment unit 9 selects the task No. The request No. and task no. and propagates task start information (S127).

At the vendor terminal 7, the schedule adjustment section 9 sends request No. and task no. After receiving the task start information, the vendor starts the task and then requests request No. and task no. and task no. As the status information of the task corresponding to , task completion information or information that the task execution becomes impossible before or after starting the task (task execution impossible information) is propagated to the execution status management unit 10 (S128 in FIG. 12).

The execution status management unit 10 requests request no. and task no. and the status information of the task (S128), and request No. of the request information DB5 is received. and task no. Task No. corresponding to The task status information is stored in the status location (S129). After this, the execution status management unit 10 issues the request No. Task No. If task execution impossible information corresponding to request No. 1 is received, request No. and the vendor ID and task number of the vendor terminal 7. and the task execution impossible information is propagated to the backup adjustment unit 11 (S130).

The backup adjustment unit 11 requests request no. and the vendor ID and task number of the vendor terminal 7. If task execution impossible information is received (S130), the request No. of the request information DB5 is received. and task no. Task No. corresponding to Backup task start information is stored in the status location (S131 in FIG. 13). The backup adjustment unit 11 requests request no. and task no. Task No. corresponding to The contact information for the vendor corresponding to the vendor ID in the vendor DB 2 that is related to the vendor ID in the backup vendor ID section is referred to (S132). The backup adjustment unit 11 uses the contact information to send a request No. to the vendor terminal 7 of the corresponding vendor ID. and task no. and propagates the task start (S133). The backup adjustment unit 11 also stores the vendor ID and request number of the vendor terminal 7 that received the task execution impossible information. and task no. and task no. The vendor ID (incentive change information) in the backup vendor ID section is propagated to the incentive management unit 12 (S134).

At the vendor terminal 7, request No. 1 is sent from the backup adjustment section 11. and task no. After receiving the task start information, the vendor requests request No. 1 after starting the task. and task no. and task no. The task completion information of the status information of the task corresponding to is propagated from the vendor terminal 7 to the execution status management unit 10 (S135 in FIG. 14).

The execution status management unit 10 requests request no. and task no. and the status information of the task (S135), and request No. of the request information DB5 is received. and task no. Task No. corresponding to The task status information is stored in the status location (S136). The execution status management unit 10 requests request no. Task No. When task completion information corresponding to is received, the vendor ID of the vendor terminal 7 and the request number of the request information DB 5 are received. Task No. The vendor IDs in the backup vendor ID locations are compared (S137). As a result of the comparison, if the vendor IDs match, the execution status management unit 10 selects the request No. in the request information DB 5. and task no. Task No. corresponding to Backup execution completion information is stored in the status location (S138 in FIG. 15). The execution status management unit 10 also sends the desired number to the incentive management unit 12. and task no. and task no. The vendor ID (backup execution completion information) at the backup vendor ID location is propagated (S139).

When the incentive management unit 12 receives the backup execution completion information from the execution status management unit 10 and the incentive change information from the backup adjustment unit 11 (S134, S139), the incentive management unit 12 sets the request number of each of the backup execution completion information and the incentive change information. and task no. and task no. The backup vendor ID and the backup vendor ID are compared (S140). If they match as a result of the comparison, the incentive management unit 12 subtracts by a predetermined value the value of the vendor evaluation corresponding to the vendor ID of the evaluation DB 6 that is related to the vendor ID of the vendor terminal 7 that is unable to execute the task of the incentive change information. and the task number of the incentive change information. The value of the vendor evaluation corresponding to the vendor ID in the evaluation DB 6 related to the vendor ID of the backup vendor ID is added by a predetermined value (S141).

The schedule adjustment unit 9 selects the task No. of the request information DB 5. If the task completion information is registered in the status of the task, the predefined task number as explained with reference to FIG. Next task No. At least one or more task No. of the request information DB 5 corresponding to The task start is registered in the status of (S142 in FIG. 17). The schedule adjustment unit 9 also selects the request No. in the request information DB 5. At least one or more next task No. corresponding to The contact information for the vendor corresponding to the vendor ID in the vendor DB2 that is related to the vendor ID of the executing vendor ID is referred to (S143). The schedule adjustment unit 9 uses the contact information to determine the task number. request No. to the vendor terminal 7 of the vendor ID of the executing vendor ID. and task no. and task start information is propagated (S144).

The schedule adjustment unit 9 also selects the request No. in the request information DB 5. Task No. corresponding to The information at the location is task completion information and the task number. As explained with reference to FIG. 9, the task number is defined in advance. The last task number in the order. In this case, the corresponding task number. Service provision completion information is stored in the service provision status section of the request information DB 5 (S145 in FIG. 18). The schedule adjustment unit 9 also sends request No. to the counter system 4. and propagates service provision completion information (S146).

The counter system 4 receives the request No. from the schedule adjustment section 9. and service provision completion information is received, Request No. The client information of the request information corresponding to the request information DB 5 is referred to (S147), and the request information and the request number are sent to the client terminal 3. and propagates service provision completion information (S148). The client terminal 3 receives the request information and request number from the counter system 4. and service provision completion information is received (S149), and the client knows that the service provision has been completed.

(Actions and effects of this embodiment)
According to this embodiment, by coordinating and adjusting scheduling between contractors, even if the contractor or equipment that was scheduled to perform the work suddenly becomes unable to respond, backup contractors or backup equipment can be used to meet the request of the client. We can provide services to you. In addition, in this embodiment, a series of jobs is divided into multiple tasks, so even if there is a surplus of personnel, equipment, etc., it is possible to apply for recruitment of contractors, so that the company's assets can be efficiently can be used. Further, as shown in FIG. 19, for example, if pesticide A is not available, pesticide spraying service company A cannot provide a series of services. However, by receiving agricultural chemical A from agricultural chemical company B, the service can be provided to the client. As described above, according to the present embodiment, it is possible to provide a matching service including a backup system when providing a pesticide spraying service using a drone. As described above, according to the information processing system, information processing method, and program of this embodiment, services can be appropriately provided.

(Modified example of embodiment)
The vendor coordination section 8 shown in FIG. By matching the information, the next task may be continuously proposed to the task contractor currently handling the task. In this case, the vendor adjustment unit 8 propagates the recruitment information to the vendor selected based on the matching result. According to this configuration, for example, it is possible to make it as if it is currently being handled. In this case, services can be provided efficiently.

(Minimum configuration of this embodiment)
FIG. 20 is a diagram showing the minimum configuration of the information processing system according to this embodiment. FIG. 21 is a diagram showing the minimum configuration of the information processing method according to this embodiment.

As shown in FIG. 20, the information processing system 300 according to this embodiment only needs to include at least an executor adjustment means 301. The information processing system 300 is an information processing system that divides work requested by a client into multiple tasks, assigns an executor to each task, and manages the execution status of each task. . Executor coordination means 301 assigns an executor to the task, and also assigns another auxiliary executor to execute the task if the executor is unable to perform the task.

Furthermore, as shown in FIG. 21, the information processing method according to this embodiment includes at least step S1. Step S1 divides the work requested by the client into multiple tasks, assigns an executor to each task, and manages the execution status of each task. and assigns another performer to perform the task if the performer is unable to perform the task.

(Computer configuration)
FIG. 22 is a schematic block diagram showing the configuration of a computer according to at least one embodiment. Computer 700 includes a CPU (Central Processing Unit) 710, a main storage device 720, an auxiliary storage device 730, and an interface 740. For example, a nonvolatile storage medium 750 is connected to the interface 740. The above-described information processing system 200, adjustment system 100, counter system 4, client terminal 3, and vendor terminal 7 are implemented in a computer 700. The operations of each processing section described above are stored in the auxiliary storage device 730 in the form of a program. The CPU 710 reads the program from the auxiliary storage device 730, expands it to the main storage device 720, and executes the above processing according to the program. Further, the CPU 710 secures storage areas corresponding to each of the above-mentioned storage units in the main storage device 720 according to the program.

The program may be for implementing part of the functions that the computer 700 performs. For example, the program may function in combination with other programs already stored in the auxiliary storage device 730 or in combination with other programs installed in other devices. Note that in other embodiments, the computer may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to or in place of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, part or all of the functions realized by the CPU 710 may be realized by the integrated circuit.

Examples of the auxiliary storage device 730 include HDD (Hard Disk Drive), SSD (Solid State Drive), magnetic disk, magneto-optical disk, CD-ROM (Compact Disc Read Only Memory), and DVD-ROM (Digital Versatile Disc Read Only). Memory), semiconductor memory, etc. Auxiliary storage 730 may be an internal medium connected directly to the bus of computer 700, or may be an external medium connected to computer 700 via an interface 740 or a communication line. Furthermore, when this program is distributed to the computer 700 via a communication line, the computer 700 that received the distribution may develop the program in the main storage device 720 and execute the above processing. In at least one embodiment, secondary storage 730 is a non-transitory tangible storage medium.

Although the embodiments of the present invention have been described above with reference to the drawings, the specific configuration is not limited to the above-described embodiments, and may include design changes without departing from the gist of the present invention. Furthermore, part or all of the program executed by the computer in the above embodiments can be distributed via a computer-readable recording medium or a communication line.

Part or all of the above embodiments may be described as in the following supplementary notes, but are not limited to the following.

(Additional Note 1) An information processing system that divides work requested by a client into multiple tasks, assigns an executor of the task to each task, and manages the execution status of each task. . An information processing system comprising an executor adjustment unit that assigns the executor to the task and assigns another auxiliary executor to execute the task when the executor is unable to execute the task.

(Supplementary note 2) When the assistant executor executes the task when the executor is unable to execute the task, an incentive to reduce the predetermined value for the executor representing an incentive and increase the predetermined value for the assistant executor The information processing system according to supplementary note 1, further comprising a management means.

(Supplementary Note 3) A backup adjustment means for transmitting information instructing the start of the task to the terminal of the assistant executor when the assistant executor executes the task when the executor is unable to execute the task. The information processing system according to supplementary note 1 or supplementary note 2.

(Supplementary note 4) The executor adjustment means assigns the task to the executor who is executing the other task according to the content of the requested work and the execution status of the other task. ) to (3).

1... Task DB, 2... Vendor DB, 3... Client terminal, 4... Counter system, 5... Request information DB, 6... Evaluation DB, 7... Vendor terminal, 8... Vendor coordination department, 9... Schedule coordination department, 10 ...Execution status management unit, 11...Backup adjustment unit, 12...Incentive management unit, 13...Order DB, 100...Adjustment system, 200...Information processing system

Claims (6)

An information processing system that divides work requested by a requester into a plurality of tasks, assigns an executor of the task to each task, and manages the execution state of each task,
An information processing system comprising: an executor adjustment unit that assigns the executor to the task, and assigns another auxiliary executor to execute the task when the executor is unable to execute the task. Further, incentive management means for reducing a predetermined value for the executor representing an incentive and increasing the predetermined value for the assistant executor when the assistant executor executes the task when the executor is unable to execute the task. The information processing system according to claim 1. Claim 1, further comprising backup adjustment means for transmitting information instructing the start of the task to a terminal of the assistant executor when the assistant executor executes the task when the executor is unable to execute the task. or the information processing system described in 2. The information according to claim 3, wherein the executor adjustment means assigns the task to the executor who is executing the other task according to the content of the requested work and the execution status of the other task. processing system. Divide work requested by a requester into multiple tasks, assign an executor of the task to each task, and manage the execution status of each task;
An information processing method comprising: assigning the executor to the task, and assigning another auxiliary executor to execute the task if the executor is unable to execute the task. When dividing work requested by a client into multiple tasks, assigning an executor to each task, and managing the execution status of each task,
A program that causes a computer to perform the steps of assigning the executor to the task and assigning another auxiliary executor to execute the task if the executor is unable to perform the task.

Images