Delivery planning device, delivery planning method, and delivery planning program

Abstract

To provide a delivery planning device capable of creating a cargo delivery plan for realizing a rapid relay delivery by multiple delivery personnel.SOLUTION: A delivery planning device 100 includes a request reception unit 101, a plan creation unit 102, and a notification unit 103. The request reception unit 101 receives a piece of project data 10 including cargo data and area data showing the cargo delivery section. The plan creation unit 102 creates a delivery plan including a delivery person, possible starting time, and possible delivery deadline for each area included in the delivery area based on delivery staff data 20 in which the working possible date and time and working possible area are set for each delivery staff and the project data 10. The notification unit 103 notifies the possible start time of the work and deadline for delivery to the delivery staff corresponding to each section.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to a delivery planning device, a delivery planning method, and a delivery planning program. [Background technology]

[0002] As demand for e-commerce grows, the number of cargo handled in the logistics industry is on the rise, and a shortage of delivery personnel is becoming an issue. For this reason, there is a trend to widely utilize human resources other than logistics companies as delivery personnel. On the other hand, as working styles become more diverse, remote work and remote meetings have become commonplace, and the demand for public transportation is on the decline. For this reason, cargo delivery services that utilize public transportation such as passenger rail are gaining attention. This involves loading cargo into vacant spaces in public transportation and delivering it, and is known as mixed cargo and passenger transport.

[0003] Patent Document 1 and Patent Document 2 disclose a means of implementing a cargo delivery service that utilizes public transportation. These documents suggest that the issue of a shortage of delivery personnel can be addressed by widely recruiting and utilizing human resources that are not logistics companies. In addition, by allowing multiple delivery personnel to use lockers installed at train stations as relay points for delivery, the delivery contract area per person is shortened, making it easier for delivery personnel to undertake deliveries. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2015-003778 A [Patent Document 2] JP 2018-200588 A Summary of the Invention [Problem to be solved by the invention]

[0005] The methods of Patent Document 1 and Patent Document 2 have a problem in that delivery dates are not taken into consideration when creating a cargo delivery plan, and prompt delivery is not guaranteed. Specifically, when a delivery person completes a task, the next delivery person starts work, and so on, and the next task is started based on the delivery completion record. Since a task delivery date is not set for each delivery person, it is not guaranteed that the entire delivery process will be completed quickly. Furthermore, the methods of Patent Documents 1 and 2 do not provide an incentive for individual delivery personnel to speed up delivery work, which is another factor in not guaranteeing speedy delivery.

[0006] An object of the present disclosure is to create a cargo delivery plan that enables rapid relay delivery by multiple delivery personnel. [Means for solving the problem]

[0007] A delivery planning device according to the present disclosure includes: a request receiving unit that receives case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo; a plan creation unit that creates a delivery plan including a delivery person, a time when the delivery person can start work, and a delivery deadline time for each individual section of a plurality of individual sections included in the delivery section, based on delivery person data in which available dates and times when delivery work is possible and available areas which are area information in which delivery work is possible for each delivery person in a list of delivery people in charge of delivery, and the case data; The delivery system further includes a notification unit that notifies a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section. Effect of the Invention

[0008] The delivery planning device according to the present disclosure can create a cargo delivery plan for achieving rapid relay delivery by multiple delivery personnel. [Brief description of the drawings]

[0009] [Figure 1]FIG. 1 is a diagram showing an example of the overall configuration of a delivery planning system according to a first embodiment. [Diagram 2] FIG. 1 is a diagram showing an example of the configuration of a delivery planning device according to a first embodiment. [Diagram 3] FIG. 4 is a diagram showing an operation example of a request receiving process according to the first embodiment. [Figure 4] FIG. 4 is a diagram showing an example of operation of a plan creation process according to the first embodiment. [Diagram 5] FIG. 4 is a diagram showing a detailed operation example of a plan creation process according to the first embodiment. [Figure 6] FIG. 4 is a diagram showing an example of operation of a result receiving process according to the first embodiment. [Figure 7] FIG. 4 is a diagram showing an example of the operation of a reward determination process according to the first embodiment. [Figure 8] FIG. 13 is a diagram showing an example of the configuration of a delivery planning device according to a modified example of the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The present embodiment will be described below with reference to the drawings. In each drawing, the same or corresponding parts are given the same reference numerals. In the description of the embodiment, the description of the same or corresponding parts will be omitted or simplified as appropriate. The arrows in the drawings mainly indicate the flow of data or the flow of processing.

[0011] Embodiment 1 ***Configuration Description*** FIG. 1 is a diagram showing an example of the overall configuration of a delivery planning system 500 according to the present embodiment. The delivery planning system 500 includes a delivery planning device 100, a requester terminal 200, and a deliveryman terminal 300. The delivery planning device 100 is a device realized by a program that runs on a computer. The delivery planning device 100 receives case data 10 as input information from a client terminal 200. Then, the delivery planning device 100 creates a delivery plan, and outputs route information 61, time information 62, and boarding candidates 63 to a delivery staff terminal 300. In addition, the delivery planning device 100 receives delivery records 50 from the delivery staff terminal 300. The case data 10 includes section data 11 and cargo data 12 . The delivery record 50 includes a destination point 51 and a delivery time 52 .

[0012] The requester terminal 200 is a terminal device operated by a delivery requester. For example, the device may be a PC, a tablet, or a smartphone. PC is an abbreviation for Personal Computer. The requester terminal 200 may be a dedicated terminal owned by the requester, or may be a shared terminal that can be used by multiple requesters.

[0013] The deliveryman terminal 300 is a terminal device operated by a deliveryman. For example, it is assumed that the deliveryman can carry the terminal such as a tablet or a smartphone when making a delivery.

[0014] FIG. 2 is a diagram showing an example of a configuration of the delivery planning device 100 according to the present embodiment. The delivery planning device 100 is a computer. The delivery planning device 100 includes a processor 910, and also includes other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to the other hardware via signal lines and controls the other hardware.

[0015] The delivery planning device 100 includes, as functional elements, a request receiving unit 101, a plan creating unit 102, a notification unit 103, a performance receiving unit 104, a remuneration determining unit 105, and a storage unit 106. The storage unit 106 stores case data 10, delivery staff data 20, traffic data 30, remuneration data 40, and delivery performance 50.

[0016] The functions of the request receiving unit 101, the plan creating unit 102, the notifying unit 103, the result receiving unit 104, and the remuneration determining unit 105 are realized by software. The storage unit 106 is provided in the memory 921. The storage unit 160 may be provided in the auxiliary storage device 922, or may be provided separately in the memory 921 and the auxiliary storage device 922.

[0017] The processor 910 is a device that executes a delivery plan program. The delivery plan program is a program that realizes the functions of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determining unit 105. The processor 910 is an IC that performs arithmetic processing. Specific examples of the processor 910 are a CPU, a DSP, and a GPU. IC is an abbreviation for Integrated Circuit. CPU is an abbreviation for Central Processing Unit. DSP is an abbreviation for Digital Signal Processor. GPU is an abbreviation for Graphics Processing Unit.

[0018] The memory 921 is a storage device that temporarily stores data. Specific examples of the memory 921 are SRAM and DRAM. SRAM is an abbreviation for Static Random Access Memory. DRAM is an abbreviation for Dynamic Random Access Memory. The auxiliary storage device 922 is a storage device that stores data. A specific example of the auxiliary storage device 922 is a HDD. The auxiliary storage device 922 may also be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, or a DVD. Note that HDD is an abbreviation for Hard Disk Drive. SD (registered trademark) is an abbreviation for Secure Digital. CF is an abbreviation for CompactFlash (registered trademark). DVD is an abbreviation for Digital Versatile Disk.

[0019] The input interface 930 is a port connected to an input device such as a mouse, a keyboard, or a touch panel. Specifically, the input interface 930 is a USB terminal. The input interface 930 may be a port connected to a LAN. USB is an abbreviation for Universal Serial Bus. LAN is an abbreviation for Local Area Network. Although one input interface 930 is shown in FIG. 2, multiple input interfaces 930 may exist.

[0020] The output interface 940 is a port to which a cable of an output device such as a display is connected. Specifically, the output interface 940 is a USB terminal or an HDMI (registered trademark) terminal. Specifically, the display is an LCD. The output interface 940 is also called a display interface. HDMI (registered trademark) is an abbreviation for High Definition Multimedia Interface. LCD is an abbreviation for Liquid Crystal Display. Although one output interface 940 is illustrated in FIG. 2, multiple output interfaces 940 may exist.

[0021] The communication device 950 has a receiver and a transmitter. The communication device 950 is connected to a communication network such as a LAN, the Internet, a telephone line, or Wi-Fi (registered trademark). Specifically, the communication device 950 is a communication chip or a NIC. NIC is an abbreviation for Network Interface Card.

[0022] The delivery plan program is executed in the delivery planning device 100. The delivery plan program is read into the processor 910 and executed by the processor 910. In addition to the delivery plan program, the OS is also stored in the memory 921. The OS is an abbreviation for Operating System. The processor 910 executes the delivery plan program while executing the OS. The delivery plan program and the OS may be stored in the auxiliary storage device 922. The delivery plan program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. Note that a part or all of the delivery plan program may be incorporated in the OS.

[0023] The delivery planning device 100 may include a plurality of processors that replace the processor 910. These plurality of processors share the execution of the delivery planning program. Each of the processors is a device that executes the delivery planning program, similar to the processor 910.

[0024] Data, information, signal values ​​and variable values ​​used, processed or output by the Dispatch Planning program are stored in memory 921, secondary storage device 922, or in registers or cache memory within the processor 910.

[0025] The "parts" of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determination unit 105 may be read as "circuits," "steps," "procedures," "processing," or "circuitry." The delivery plan program causes a computer to execute a request receiving process, a plan creating process, a notification process, a result receiving process, and a remuneration determination process. The "processing" of the request receiving process, the plan creating process, the notification process, the result receiving process, and the remuneration determination process may be read as "program," "program product," "computer-readable storage medium storing a program," or "computer-readable recording medium recording a program." The delivery planning method is a method performed by the delivery planning device 100 executing the delivery planning program. The delivery planning program may be provided by being stored in a computer-readable recording medium, or may be provided as a program product.

[0026] Next, the function of each functional element will be described. The request receiving unit 101 receives the case data 10 as a delivery request from the requester terminal 200 and stores it in the storage unit 106 . The plan creation unit 102 creates a delivery plan using various data stored in the storage unit 106. The delivery plan includes information on the delivery personnel in charge of delivery and the section in charge of the delivery personnel. The specific contents of the delivery plan and the method of creating the plan will be described later.

[0027] The notification unit 103 notifies the delivery staff terminal 300 carried by the delivery staff in charge of delivery of information necessary for delivery based on the delivery plan created by the plan creation unit 102. The information necessary for delivery includes route information 61, time information 62, and boarding candidate information 63. Details of the notification content will be described later. The record receiving unit 104 receives the delivery record 50 of the delivery person transmitted from the delivery person terminal 300 and stores it in the storage unit 106 . The remuneration determination unit 105 determines the remuneration to be received by each delivery person by using various data stored in the storage unit 106. The specific method of determination will be described later.

[0028] The storage unit 106 stores data including the case data 10, delivery person data 20, traffic data 30, remuneration data 40, and delivery record 50. Note that the storage unit 106 does not necessarily need to be installed in the same place as the delivery planning device 100, and may be installed in a device such as the cloud and implemented in a form that communicates with other devices.

[0029] The case data 10 is information related to a delivery case. The case data 10 includes section data 11 consisting of a delivery departure point and a delivery destination point of the delivery case, and cargo data 12 indicating the weight and volume, which are attributes of the cargo to be delivered in the delivery case.

[0030] The delivery staff data 20 is information about delivery staff who can handle delivery. The delivery staff data 20 includes available dates and times 21 indicating the date and time information when the delivery staff is available for delivery work, and available areas 22 indicating area information where delivery work can be performed, for each delivery staff. An example of the available dates and times 21 is a format in which availability information is registered in one-hour units for each day. Another example may be a format in which the delivery staff is in a state where they can be contracted for delivery at the current time through a dedicated application installed on the delivery staff terminal 300. An example of the available areas 22 is a format in which section information of a specific train station is registered, and delivery is possible within that section. Another example may be a format in which the area where delivery is possible is specified based on the address, such as prefecture, city, ward, town, and village.

[0031] The transportation data 30 is information about public transportation that can be used for delivery. The transportation data 30 includes transportation data 31, route data 32, and timetable data 33. The transportation data 31 is information that identifies transportation that can be used for delivery, such as railroad and bus routes, and when creating a delivery plan, a plan using these transportation is made. The route data 32 is information about the operation route of each transportation. For example, in the case of a railroad, station information on the route is recorded as sequential information from one terminal station to the other terminal station. Similarly, in the case of a bus, information on bus stops is included, and in the case of an airplane or ship, in addition to information on the departure and arrival points of each route, information on the intermediate points is included if there are intermediate points. The timetable data 33 is information that can identify when and which points each transportation will intermediate. Specifically, the timetable data includes the departure and arrival times for each flight and each point.

[0032] The remuneration data 40 is information for determining a standard remuneration amount according to the delivery work contracted by the delivery person. It is assumed that the standard remuneration amount can be determined according to the delivery section and delivery date and time based on the remuneration data 40. However, the actual remuneration is determined by the remuneration determination unit 105. The delivery record 50 is data showing the delivery status of the delivery personnel, and includes a destination 51 and an arrival time 52 at the destination for each delivery personnel.

[0033] ***Explanation of Operation*** Next, the operation of the delivery planning device 100 according to the present embodiment will be described with reference to Fig. 3 to Fig. 7. The operation procedure of the delivery planning device 100 corresponds to a delivery planning method. Also, a program for realizing the operation of the delivery planning device 100 corresponds to a delivery planning program.

[0034] FIG. 3 is a diagram showing an operation example of the request receiving process according to the present embodiment. 4 and 5 are diagrams showing an operation example of the plan creation process according to the present embodiment. FIG. 6 is a diagram showing an example of the operation of the result receiving process according to the present embodiment. FIG. 7 is a diagram showing an operation example of the remuneration determination process according to the present embodiment.

[0035] <Request reception process> 3, the request receiving process is made up of steps S101, S102, and S103. The request receiving process is executed every time a delivery request is received from a delivery requester. In the request receiving process, the request receiving unit 101 receives the case data 10 including the cargo data 12 indicating the attributes of the cargo to be delivered and the section data 11 indicating the delivery section of the cargo. Specifically, the following applies:

[0036] In step S101, a delivery requester makes a delivery request to the delivery planning device 100 through the requester terminal 200. The delivery requester inputs the case data 10 at the time of the request, and places the cargo to be delivered at the delivery departure point. The process proceeds to step S102. Specifically, the following applies:

[0037] For example, when a locker at a train station is specified as the delivery departure point, the delivery requester transports the cargo to the locker and stores the cargo in the locker. Regarding the security of the locker, for example, a PIN-type key is placed on the locker, and the delivery requester sets the PIN when making the request. Any technology can be used, such as a mechanism in which the deliverer refers to the PIN to unlock the locker. A simple terminal may be placed on the locker, and this may function as both the requester terminal 200 and the unlocking device. The delivery starting point may also be any point other than a locker at a station. In this case, the delivery requester transports the cargo to the point in advance so that the cargo can be handed over to the delivery person. For example, the delivery starting point may be set to the requester's home, and the cargo may be handed over directly to the delivery person. Another example is a method of designating a specific store that handles cargo temporary storage and delivery services as the delivery starting point.

[0038] In step S102, the request receiving unit 101 receives the case data 10. The process proceeds to step S103. As described above, the case data 10 includes section data 11 consisting of the delivery departure point and delivery destination point of the delivery case, and cargo data 12 indicating the weight and volume of the cargo to be delivered in the delivery case.

[0039] In step S103, the request receiving unit 101 stores the case data 10 in the storage unit 106. When storing, information that can identify that the case data 10 is unprocessed and the time of receipt of the request are added to the case data 10.

[0040] <Planning process> As shown in Fig. 4, the plan creation process consists of steps S201, S202, S203, S204, and S205. The delivery plan creation process runs periodically at a preset cycle, such as a daily cycle or an hourly cycle. Alternatively, the process may run at any timing manually specified by the person in charge of creating the delivery plan.

[0041] In the plan creation process, the plan creation unit 102 creates a delivery plan including a delivery person, a time when work can start, and a delivery deadline for each of a plurality of individual sections included in the delivery section, based on the delivery person data 20 and the case data 10. The delivery staff data 20 includes available delivery dates 21, which are information on dates and times when delivery work is possible for each delivery staff in the list of delivery staff in charge of delivery, and available areas 22, which are information on areas where delivery work is possible. In addition, the plan creation unit 102 determines the transportation facility to be used for each individual section and the candidate boarding flights based on the transportation data 30 including information on the public transportation facility to be used for delivery, and includes them in the delivery plan.

[0042] The delivery plan includes delivery person information 60, which is information about delivery people in charge of individual sections, and route information 61, which indicates the transportation means and routes to be used for delivery in the individual sections. The delivery plan also includes time information 62, which indicates the delivery deadline time and the available start time for work in the individual sections, and candidate rides 63, which are candidates for the transportation means to be used in the individual sections. Specifically, the following applies:

[0043] In step S201, the plan creation unit 102 acquires the unprocessed case data 10 from the storage unit 106. The process proceeds to step S202. When acquiring the unprocessed case data 10, the plan creation unit 102 may acquire all unprocessed cases, or may limit the number of cases to be acquired in some way. For example, an upper limit may be set for the number of cases to be acquired, and unprocessed cases may be acquired in order of the earliest requested time. As another example, the cases to be acquired may be limited depending on the time period when the cases were requested, such as cases requested in the 10:00-24:00 hours.

[0044] In step S202, the plan creation unit 102 refers to the available delivery dates and times 21 in the delivery person data 20 recorded in the storage unit 106, and acquires a delivery person who can deliver during the time period when the delivery plan is scheduled to be executed. The process proceeds to step S203. As described above, the delivery person data 20 includes, for each delivery person, the available date and time 21 indicating the date and time information when the delivery person is available to perform delivery work, and the available area 22 indicating the area information when the delivery person is available to perform delivery work.

[0045] In step S203, the plan creation unit 102 creates a delivery plan based on the unprocessed job data acquired in step S201, the delivery person acquired in step S202, and the traffic data 30 in the storage unit 106. A delivery plan is created for each job data, that is, for each job. For jobs for which a delivery plan has been created in this step, the unprocessed identification information added in step S103 is deleted. Proceed to step S204. Specifically, the following applies:

[0046] The delivery plan created in step S203 will now be described in detail. The delivery plan includes route information 61, time information 62, candidate vehicles 63, and delivery person information 60 for each job.

[0047] The route information 61 is information about a plurality of individual sections included in the delivery route connecting the delivery starting point and the delivery destination point of the job. The delivery route connecting the delivery starting point and the delivery destination point of the job is composed of a plurality of individual sections. The route information 61 includes information on which transportation means to use for each individual section. For example, if the delivery starting point is Station A and the delivery destination point is Station B, the route information 61 includes information that the individual section from Station A to relay station C is traveled on railway line 1, and the individual section from relay station C to Station B is traveled on railway line 2.

[0048] The time information 62 includes the delivery deadline time and the workable start time for each individual section that constitutes the delivery route. The delivery deadline time is the upper limit of the time by which the delivery of the individual section must be completed. If this time is exceeded, the remuneration of the delivery person in charge is adjusted downward as a penalty. The details of the remuneration determination will be described later. The workable start time is the lower limit of the time that guarantees that the cargo has arrived at the starting point of the individual section. If multiple delivery people are in charge of the case, the next delivery person cannot start delivery work until the delivery of the delivery person in charge of the previous individual section is completed. The workable start time is intended to enable the subsequent delivery person in such a case to determine in advance when they may start preparing for delivery work. The delivery deadline time of a certain individual section must be before the workable start time of the next individual section. Both may be the same time, or may be set with a difference in consideration of allowing for a slack time for relaying.

[0049] The boarding candidate 63 is information indicating what time of day a passenger should board when using a means of transport. The boarding candidate 63 is determined on the assumption that the passenger will definitely make it to the delivery deadline if he or she uses the means of transport indicated in the boarding candidate 63. There may be multiple candidates for one section.

[0050] <<Details on creating a shipping plan>> Details of step S203 will be described with reference to Fig. 5. Step S203 is further divided into steps S2031, S2032, and S2033.

[0051] In step S2031, route information 61 is determined for each case. This step can be realized, for example, by using a normal route search service. In this case, the route search service inputs the transportation data 30 and executes a route search only for the transportation facilities included in the transportation data 30. In this step, each case is divided into a plurality of individual sections. Proceed to step S2032.

[0052] In step S2032, time information 62 and boarding candidates 63 are determined for each individual section of each job determined in step S2031. As a method of implementing this step, the results of a normal route search service may be used, as in step S2031. Alternatively, if there is a need to allow for a leeway in the transit time between consecutive sections, the departure time for each individual section can be delayed by the amount of the transit time to be considered, and a search can be performed again, thereby determining time information 62 and boarding candidates 63 that take the transit time into consideration. Proceed to step S2033.

[0053] In step S2033, a delivery person in charge of each individual section is determined. The delivery person is selected from among those whose areas indicated in the operable area 22 include the individual section. When the operable area 22 includes a plurality of consecutive individual sections, one delivery person may be in charge of the plurality of consecutive individual sections. When there are a plurality of delivery people who can be in charge of an individual section, the delivery person is determined according to an appropriate priority. For example, the narrower the operable area 22, the lower the possibility that the delivery person can be in charge of other individual sections, so such a delivery person is prioritized. As another example, a delivery person who can be in charge of as many consecutive individual sections as possible is prioritized. In the latter example, a job can be handled by a small number of people, so that delivery people who can be assigned to other jobs can have some leeway.

[0054] If delivery personnel cannot be assigned to all individual sections due to a shortage of delivery personnel or other reasons, exception processing is performed. As an example of exception processing, there is a method of not including cases including individual sections to which delivery personnel have not been assigned in the delivery plan, leaving them as unprocessed cases, and carrying them over to the next delivery plan. As another example, there is a method of re-executing step S2033. At this time, a result different from the previous time can be obtained by replacing the priority for selecting delivery personnel with a different index, changing the order of individual sections for which delivery personnel are determined, etc. If delivery personnel cannot be assigned to all individual sections even after a certain number of re-executions, there is a method of not including cases including individual sections to which delivery personnel have not been assigned in the delivery plan, leaving them as unprocessed cases, and carrying them over to the next delivery plan. This is the end of the explanation of step S203.

[0055] Returning to the explanation of Figure 4. The notification unit 103 notifies the delivery person corresponding to each individual section of the possible work start time and the delivery deadline time included in the delivery plan corresponding to the individual section. Furthermore, the notification unit 103 notifies the route information 61 and the boarding candidate 63 included in the delivery plan corresponding to the individual section. Specifically, the following applies:

[0056] In step S204, the notification unit 103 notifies the delivery person terminal 300 carried by the delivery person in charge of the delivery, based on the delivery plan created in step S203, of the route information 61, the time information 62, and the boarding candidates 63 for the individual section in charge of the delivery person. Then, proceed to step S205.

[0057] In step S205, the delivery person who received the delivery information sends a message to the delivery planning device via the delivery person terminal 300 indicating whether or not they will undertake the delivery. If the delivery is rejected or there is no reply for a certain period of time, the process returns to step S203 and the plan is re-created for the undecided individual sections. When delivery persons have been decided for all individual sections, the process ends.

[0058] <Results reception process> Next, the operation of the result reception process will be described with reference to FIG. 6, the delivery record receiving process for receiving a delivery record is made up of steps S301 and S302. The delivery record receiving process is executed every time a delivery person transmits a delivery record. In the result receiving process, the result receiving unit 104 receives the delivery results of the delivery personnel. Specifically, the following applies:

[0059] In step S301, a delivery person in charge of delivery transmits a delivery record 50 to the delivery planning device 100 through the delivery person terminal 300. The delivery record 50 is transmitted when delivery for an individual section is completed. In addition, when delivery is delayed due to unforeseen factors such as a train delay, the delivery person can transmit the delivery record 50 as appropriate in a situation where the delivery person judges it necessary to contact the delivery person. Proceed to step S302.

[0060] In step S302, the record receiving unit 104 receives the delivery record 50 and stores it in the storage unit .

[0061] <Reward determination process> Next, the operation of the remuneration determination process will be described with reference to FIG. 7, the remuneration determination process includes steps S401 and S402. The remuneration determination process is executed after a delivery person completes a delivery as a process for determining the remuneration of the delivery person.

[0062] In the remuneration determination process, the remuneration determination unit 105 determines the remuneration for each delivery person based on the remuneration data 40 and the delivery record. The remuneration data 40 is data for determining a base amount of remuneration according to the delivery work performed by the delivery person. For example, the remuneration determination unit 105 reduces the remuneration of the delivery person in question depending on the degree of delay with respect to the delivery deadline time. For example, if the cargo has not arrived even after the start time when work is possible has passed due to a delay by a delivery person in charge of a previous individual section, the remuneration determination unit 105 may increase the remuneration of that delivery person by accepting the delivery rather than canceling it. For example, when a delivery person in charge of a previous individual section makes up for a delay, the remuneration determination unit 105 may increase the remuneration of that delivery person. Specifically, the following applies:

[0063] In step S401, the remuneration determination unit 105 determines a base remuneration amount for the delivery person based on the delivery section covered by the delivery person and information on the delivery date and time, with reference to the remuneration data 40. The process proceeds to step S402.

[0064] In step S402, the remuneration determination unit 105 determines the difference from the remuneration base amount according to the delivery performance of the delivery person. Several examples of the method of determining the difference will be given. If the delivery person exceeds the delivery deadline, the remuneration is reduced according to the degree of overage. However, in the case of an unexpected delay, such as when the delivery person is on the flight specified in the boarding candidate 63 but is delayed due to circumstances on the transportation side, the remuneration is not reduced. If a delivery person who has once accepted a delivery cancels the delivery, the remuneration is not paid to the delivery person, and instead a penalty fee is collected. However, if the work of the previous delivery person has not been completed by the workable start time notified in advance, no penalty will be incurred even if the delivery is canceled. In such a case, if the delivery is accepted without being canceled, the remuneration is increased. If the delay of the previous delivery person can be made up for, the remuneration is further increased.

[0065] ***Explanation of the Effects of the Present Embodiment*** As described above, the delivery planning device 100 according to the present embodiment includes information about delivery dates in a delivery plan for delivery using public transportation, and includes a method for determining rewards to motivate delivery personnel to comply with the delivery plan. This makes it possible to realize rapid relay delivery by multiple delivery personnel using public transportation.

[0066] In the delivery planning device 100 according to the present embodiment, the plan creation unit and the notification unit can present a delivery plan including time information and boarding candidates to the delivery personnel in charge of delivery. This can increase the feasibility of quick delivery. In addition, the performance receiving unit and the remuneration determination unit can increase or decrease the remuneration according to the delivery performance of the delivery personnel, thereby providing an incentive for the delivery personnel to comply with the time information. In addition, it is expected that each delivery personnel will operate autonomously to achieve quick delivery.

[0067] ***Other configurations*** In this embodiment, the functions of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determining unit 105 are realized by software. As a variation, the functions of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determining unit 105 may be realized by hardware. Specifically, the delivery planning device 100 includes an electronic circuit 909 instead of the processor 910 .

[0068] FIG. 8 is a diagram showing a configuration of a delivery planning device 100 according to a modified example of the present embodiment. The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of the request receiving unit 101, the plan creating unit 102, the notifying unit 103, the result receiving unit 104, and the remuneration determining unit 105. Specifically, the electronic circuit 909 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0069] The functions of the request receiving unit 101, the plan creation unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determination unit 105 may be realized by a single electronic circuit, or may be distributed across multiple electronic circuits.

[0070] As another modification, some of the functions of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determination unit 105 may be realized by electronic circuits, and the remaining functions may be realized by software. Also, some or all of the functions of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determination unit 105 may be realized by firmware.

[0071] Each of the processor and the electronic circuit is also called a processing circuitry. In other words, the functions of the request receiving unit 101, the plan creating unit 102, the notification unit 103, the result receiving unit 104, and the remuneration determining unit 105 are realized by the processing circuitry.

[0072] In the above first embodiment, each unit of the delivery planning device has been described as an independent functional block. However, the configuration of the delivery planning device does not have to be as in the above-mentioned embodiment. The functional blocks of the delivery planning device may have any configuration as long as they can realize the functions described in the above-mentioned embodiment. In addition, the delivery planning device may not be a single device, but may be a system composed of multiple devices. In addition, a plurality of parts of the first embodiment may be combined and implemented. Alternatively, only one part of this embodiment may be implemented. In addition, this embodiment may be combined in any manner as a whole or in part and implemented. That is, in the first embodiment, it is possible to freely combine parts of the embodiments, or to modify any of the components of the embodiments, or to omit any of the components of the embodiments.

[0073] The above-described embodiment is essentially a preferred example, and is not intended to limit the scope of the present disclosure, the scope of application of the present disclosure, and the scope of use of the present disclosure. The above-described embodiment can be modified in various ways as necessary. For example, the procedure described using a flow chart or sequence chart may be modified as appropriate.

[0074] Various aspects of the present disclosure are summarized below as appendices.

[0075] (Appendix 1) a request receiving unit that receives case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo; a plan creation unit that creates a delivery plan including a delivery person, a time when the delivery person can start work, and a delivery deadline time for each individual section of a plurality of individual sections included in the delivery section, based on delivery person data in which available dates and times when delivery work is possible and available areas which are area information in which delivery work is possible for each delivery person in a list of delivery people in charge of delivery, and the case data; a notification unit that notifies a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section; A delivery planning device comprising: (Appendix 2) The plan creation unit Based on the transportation data including information on the public transportation to be used for delivery, route information indicating the transportation to be used and the route, and boarding candidates which are candidates for the bus to be boarded are determined for each individual section, and are included in the delivery plan; The notification unit is A delivery planning device as described in appendix 1, which notifies a delivery person corresponding to the individual section of the route information and the boarding candidates. (Appendix 3) The delivery planning device includes: A performance receiving unit that receives the delivery performance of the delivery person; remuneration data for determining a standard amount of remuneration according to the delivery work performed by the delivery personnel, and a remuneration determination unit for determining remuneration for each delivery personnel based on the delivery performance; 3. The delivery planning device according to claim 1 or 2, comprising: (Appendix 4) The remuneration determination unit, The delivery planning device according to claim 3, wherein the delivery person's remuneration is reduced according to the degree of delay with respect to the delivery deadline. (Appendix 5) The remuneration determination unit, A delivery planning device according to claim 3 or 4, which increases the remuneration of a delivery person by accepting the delivery without canceling it when the cargo has not arrived even after the start time when the delivery person is available for work due to a delay by the delivery person in charge of the previous individual section. (Appendix 6) The remuneration determination unit, The delivery planning device according to claim 3 or 4, which increases the remuneration of a delivery person in charge of a previous individual section when the delivery person makes up for a delay caused by the delivery person. (Appendix 7) A computer receives case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo, A computer creates a delivery plan including a delivery person, a workable time and a delivery deadline for each individual section of a plurality of individual sections included in the delivery section, based on delivery person data in which an available date and time, which is information on the date and time when each delivery person in a list of delivery people in charge of delivery, and an available area, which is information on the area where delivery work can be performed, is set for each delivery person in the list of delivery people in charge of delivery, and the case data; A delivery planning method in which a computer notifies a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section. (Appendix 8) A request receiving process for receiving case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo; A plan creation process for creating a delivery plan including a delivery person, a workable time and a delivery deadline for each individual section included in the delivery section, based on delivery person data in which available dates and times, which are information on dates and times when delivery work can be performed, and available areas, which are information on areas where delivery work can be performed, are set for each delivery person in a list of delivery people in charge of delivery, and the case data; A notification process of notifying a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section; A delivery planning program that causes a computer to execute the above. [Explanation of symbols]

[0076] 10 case data, 11 section data, 12 cargo data, 20 delivery person data, 21 available date and time, 22 available area, 30 traffic data, 31 transportation data, 32 route data, 33 timetable data, 40 reward data, 50 delivery record, 51 arrival point, 52 arrival time, 60 delivery person information, 61 route information, 62 time information, 63 boarding candidate, 100 delivery planning device, 101 request receiving unit, 102 plan creating unit, 103 notification unit, 104 record receiving unit, 105 reward determining unit, 106 memory unit, 200 requester terminal, 300 delivery person terminal, 500 delivery planning system, 909 electronic circuit, 910 processor, 921 memory, 922 auxiliary storage device, 930 input interface, 940 output interface, 950 communication device.

Claims

1. a request receiving unit that receives case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo; a plan creation unit that creates a delivery plan including a delivery person, a time when the delivery person can start work, and a delivery deadline time for each individual section of a plurality of individual sections included in the delivery section, based on delivery person data in which available dates and times when delivery work is possible and available areas which are area information in which delivery work is possible for each delivery person in a list of delivery people in charge of delivery, and the case data; a notification unit that notifies a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section; A delivery planning device comprising:

2. The plan creation unit Based on the transportation data including information on the public transportation to be used for delivery, route information indicating the transportation to be used and the route, and boarding candidates which are candidates for the bus to be boarded are determined for each individual section, and are included in the delivery plan; The notification unit is The delivery planning device according to claim 1 , further comprising: notifying a delivery person corresponding to the individual section of the route information and the boarding candidate.

3. The delivery planning device includes: A performance receiving unit that receives the delivery performance of the delivery person; remuneration data for determining a standard amount of remuneration according to the delivery work performed by the delivery personnel, and a remuneration determination unit for determining remuneration for each delivery personnel based on the delivery performance; The delivery planning device according to claim 1 or 2, comprising:

4. The remuneration determination unit, 4. The delivery planning device according to claim 3, wherein the remuneration of the delivery person is reduced according to the degree of delay with respect to the delivery deadline.

5. The remuneration determination unit, The delivery planning device according to claim 3, wherein if the cargo has not arrived by the start time when work is possible due to a delay by a delivery person in charge of a previous individual section, the delivery person's remuneration is increased by accepting the delivery rather than canceling it.

6. The remuneration determination unit, 4. The delivery planning device according to claim 3, wherein when a delay caused by a delivery person in charge of a previous individual section is made up for, the remuneration of the delivery person is increased.

7. A computer receives case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo, A computer creates a delivery plan including a delivery person, a workable time and a delivery deadline for each individual section of a plurality of individual sections included in the delivery section, based on delivery person data in which an available date and time, which is information on the date and time when each delivery person in a list of delivery people in charge of delivery, and an available area, which is information on the area where delivery work can be performed, is set for each delivery person in the list of delivery people in charge of delivery, and the case data; A delivery planning method in which a computer notifies a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section.

8. A request receiving process for receiving case data including cargo data indicating attributes of cargo to be delivered and section data indicating a delivery section of the cargo; A plan creation process for creating a delivery plan including a delivery person, a workable time and a delivery deadline for each individual section included in the delivery section, based on delivery person data in which available dates and times, which are information on dates and times when delivery work can be performed, and available areas, which are information on areas where delivery work can be performed, are set for each delivery person in a list of delivery people in charge of delivery, and the case data; A notification process of notifying a delivery person corresponding to the individual section of a work start time and a delivery deadline time included in the delivery plan corresponding to the individual section; A delivery planning program that causes a computer to execute the above.

Images