JP3270705B2 - Delivery planning system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a delivery planning system for planning a delivery schedule based on a product delivery request from a delivery destination so that daily delivery capacity can be fully utilized. Further, if there is a margin in the daily delivery capacity based on the article collection request from the delivery destination, a collection schedule is planned. Alternatively, the present invention relates to a delivery planning system that plans a collection schedule so that collection is performed simultaneously with delivery if a delivery schedule to the same delivery destination as the collection destination is planned.

[0002]

[Prior art]

Conventional example 1. Conventional examples similar to the delivery planning system of the present invention include a "dynamic automatic dispatching device" of "Japanese Patent Laid-Open No. 6-290185", a "distribution system" of "Japanese Patent Application Laid-Open No. 7-53018" and There is a "vehicle allocation planning method". The above-mentioned conventional invention is an invention in which a delivery request of a package is received from a shipper and a vehicle is dispatched to a destination of the package. In particular, the invention of Japanese Patent Laid-Open No. 6-290185 is characterized in that dynamic change information such as road conditions that change with time is input, and a delivery plan is made based on the change information. In addition, in order to prevent the goods received at the distribution center from overflowing to the temporary storage area, the invention disclosed in Japanese Patent Application Laid-Open No. Hei 7-53018 is designed so that the goods are unloaded from the truck and then quickly distributed to the sorting zone. Perform another sorting planning process. In addition, in order to prevent the shipping flat storage area, which is the shipping inspection zone, from being filled with the packing containers or the carts to be shipped, the shipping containers or the carts containing the products should be shipped at the same time as they arrive from the sorting zone. It is characterized in that a vehicle allocation plan is made so that on-board processing for loading on a truck for each direction is performed quickly. In addition, the invention of Japanese Patent Application Laid-Open No. 1-2231200 is characterized in that a vehicle allocation plan is performed in consideration of the restrictions on the combination of the cargos and the restrictions on the types of vehicles that can be used when determining the cargo to be loaded on the vehicle.

Conventional example 2. In addition, the conventional delivery planning system plans to execute delivery on the same day when a delivery request is made. For this reason, if delivery is not possible with the scheduled dispatch, another car is chartered to realize delivery on the same day.

[0004]

SUMMARY OF THE INVENTION The above-mentioned conventional invention is intended to plan how fast delivery can be performed while avoiding congestion,
Planning to load cargo efficiently on trucks,
The company planned to inspect the received goods, sort them by shipping destination, and quickly process the goods before loading them on trucks. For this reason, the above-mentioned conventional invention does not have the concept of the delivery deadline, and has a problem that the number of destinations per day cannot be equalized in consideration of the delivery deadline. In addition, the fact that the leveling cannot be performed means that a delivery schedule that exceeds the scheduled delivery means, for example, the delivery capability by car, is planned. In this case, there is a problem that a delivery means is separately prepared and the delivery cost is increased. Further, in the conventional example, there is no concept of the daily delivery capacity, and if the desired delivery dates from a plurality of delivery destinations overlap, the scheduled delivery will not be able to complete the delivery, so an unscheduled delivery means is separately prepared. As a result, there is a problem that the delivery cost increases. Also, according to the regular delivery cycle, even in the case of a delivery destination that is delivering, there is no concept of a delivery cycle in the conventional example, so delivery is performed on days other than the delivery cycle, and the delivery cost is reduced. There is a problem of becoming high.

[0005] The present invention has been made to solve the above problems, and has the following objects. Considering the delivery deadline, equalize the number of destinations per day. Also,
Consider the daily delivery capacity and plan the delivery schedule within the delivery capacity. Also, a delivery schedule is planned along with a regular delivery cycle.

[0006]

According to the present invention, there is provided a delivery planning system including a delivery request information input section for inputting delivery request information from a delivery destination of an article, and planning a delivery schedule according to the delivery request information. It has the following elements. (A) A delivery cycle information storage unit stores a regular delivery schedule defined for each delivery destination as delivery cycle information, and (b) a delivery plan unit sends the goods delivery request input by the delivery request information input unit. Planning a delivery schedule of the article based on the information and the delivery cycle information stored in the delivery cycle information storage unit; (c) the delivery schedule storage unit stores the delivery schedule planned by the delivery planning unit; d) The delivery schedule output unit extracts and outputs the delivery schedule stored in the delivery schedule storage unit.

A delivery cycle information setting section provided in the delivery planning system sets the delivery cycle information, and stores the set delivery cycle information in the delivery cycle information storage section.

[0008] The article delivery request information is characterized by comprising at least delivery destination information, delivery deadline date, and delivered article information.

In addition, the present invention further includes a delivery request information input section for inputting delivery request information comprising at least delivery destination information, delivery deadline, and delivery item information, and a delivery schedule according to the delivery request information. Is characterized by having the following elements. (A) a deliverable period setting unit previously determines a predetermined number of days as a deliverable period, and (b) a deliverable period storage unit stores the deliverable period determined by the deliverable period setting unit,
(C) The delivery planning unit uses the deliverable period stored in the deliverable period storage unit and the delivery deadline of the article delivery request information to request a predetermined article delivery from the same delivery destination and another article delivery request. And (d) the delivery schedule storage unit stores the delivery schedule planned by the delivery planning unit, and (e) the delivery schedule output unit, The delivery schedule stored in the delivery schedule storage unit is extracted and output.

[0010] Further, a deliverable period calculation unit provided in the delivery planning unit retrieves a deliverable period from the deliverable period storage unit, and sets the delivery deadline based on the deliverable period and the delivery deadline of the article delivery request information. The delivery period is calculated so that the day is included in the delivery period,
The same-day delivery planning unit included in the delivery planning unit compares the delivery possible execution period for a given item delivery request from the same delivery destination obtained by the delivery possible period calculation unit with the delivery possible implementation period for another product delivery request In addition, a predetermined delivery date is obtained by combining the predetermined article and another article to make the number of deliveries one, and the delivery day is used as a delivery date for simultaneous delivery of the above-mentioned predetermined delivery possible day. It is characterized by planning.

The delivery planning system has a predetermined delivery capacity per day, the delivery request input unit inputs goods delivery request information from a plurality of delivery destinations, and the delivery planning unit includes The possible period calculation unit retrieves the deliverable period from the deliverable period storage unit, and calculates the delivery deadline based on the deliverable period and the delivery deadline of the goods delivery request information from the plurality of delivery destinations. The delivery possible implementation period for each delivery destination is obtained so that it is included in the delivery schedule, and the collective delivery planning unit provided in the delivery planning unit compares the delivery possible implementation period for each delivery destination obtained by the delivery possible period calculation unit and overlaps A delivery date to be delivered to a plurality of destinations within a range that does not exceed the delivery capability from the overlapping delivery date.

The unplanned information storage section of the delivery planning system stores article delivery request information that cannot be incorporated in the delivery schedule, and the readjustable period storage section of the delivery planning system stores the delivery possible information. A re-adjustable period for re-adjusting the delivery schedule planned by the planning unit is stored, and a re-adjustable period setting unit included in the delivery planning system sets the re-adjustable period and sets the re-adjustable period. The period is stored in the re-adjustable period storage unit, and the unplanned information output unit provided in the delivery planning unit stores the article delivery request information that cannot be incorporated in the delivery schedule in the unplanned information storage unit. If the delivery re-planning unit included in the delivery planning unit has completed the planning of the delivery schedule and the unplanned delivery request information exists, In the re-adjustable period, a search is made for a day on which there is room in the delivery capacity per day, and the article delivery request information is retrieved from the unplanned information storage unit, and the delivery schedule of the article delivery request information on a day on which there is room in the delivery capacity It is characterized by planning.

Further, the delivery request information input section inputs at least the collection destination information and the collection request date as article collection request information, and the collection planning section provided in the delivery planning section, after finishing the planning of the delivery schedule, A predetermined date on which a delivery schedule of the collection destination is planned after the collection request date is searched, a collection schedule of the article collection request information is planned on the predetermined day, and an unplanned collection provided in the delivery planning system is performed. The information storage unit stores the item collection request information that cannot be incorporated in the collection schedule, and the unplanned collection information output unit provided in the delivery planning unit outputs the item collection request information that cannot be incorporated in the collection schedule. It is stored in a plan collection information storage unit.

The same-day collection and re-planning unit provided in the collection planning unit, when a day that does not exceed the daily delivery capacity after the collection request date occurs, sends an item collection request from the unplanned collection information storage unit. The method is characterized in that information is taken out and a collection schedule of the article collection request information is planned on a day that does not exceed the daily delivery capacity.

Further, when the delivery schedule of the goods to the collection destination is planned on a predetermined date after the collection request date, the uncollected collection information storage unit stores the uncollected collection information. The present invention is characterized in that the article collection request information is taken out and a collection schedule of the article collection request information is planned on the predetermined day.

[0016]

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiment 1 FIG. In the first embodiment, a delivery cycle is determined for each office, and a delivery planning system that plans a delivery schedule based on a delivery cycle and a delivery deadline will be described below.

First, the drawings will be described. FIG. 1 is an example of a system configuration diagram of a delivery planning system according to the first embodiment. In FIG. 1, reference numeral 1 denotes a delivery planning system. 2 is goods delivery request information, and goods delivery request information 2
Is composed of at least delivery destination information, delivery deadline date, and delivered article information. Reference numeral 4 denotes a delivery request information input unit, which inputs the article delivery request information 2 to the delivery planning system 1. Reference numeral 3 denotes delivery cycle information. In the first embodiment, a delivery cycle is determined for each office, and the delivery cycle for each office is input to the delivery planning system 1 as delivery cycle information 3. Reference numeral 6 denotes a delivery cycle information setting unit, and reference numeral 7 denotes a delivery cycle information storage unit. The delivery cycle information setting unit 6 inputs the delivery cycle information 3 to the delivery planning system 1 and stores the input delivery cycle information 3 in the delivery cycle information storage unit 7. Reference numeral 8 denotes a delivery planning section, which plans a delivery schedule based on the article delivery request information 2 input from the delivery request information input section 4 and the delivery cycle information 3 stored in the delivery cycle information storage section 7. A delivery schedule storage unit 9 stores the delivery schedule planned by the delivery planning unit 8. Reference numeral 10 denotes a delivery schedule output unit, and a delivery schedule storage unit 9
Output the delivery schedule stored in. Reference numeral 11 denotes a delivery schedule, and a delivery schedule output unit 10
Output.

FIG. 2 is a network configuration diagram of the delivery planning system according to the first embodiment. In FIG. 2, 2
Reference numeral 00 denotes a delivery center, and the delivery planning system 1 shown in FIG. Also, the distribution center 200 is a business establishment 201,
The B establishment 202 and the C establishment 203 are connected by a network. Each of the business offices 201 to 203 transmits the article delivery request information 2 to the delivery planning system 1 of the delivery center 200. The delivery cycle information 3 is information input in the delivery center 200. Further, the delivery schedule 11 is delivered from the delivery planning system 1 of the delivery center 200 to each of the offices 201 to 203. The delivery cycle of the establishment A 201 is every Monday, the delivery cycle of the establishment B 202 is every Wednesday and Friday, and the delivery cycle of the establishment C 203 is every day. The delivery cycle information storage unit 7 stores the delivery cycles of each of the establishments 201 to 203 described above.

FIG. 3 is a flowchart showing an example of a procedure for planning a delivery schedule according to the first embodiment. FIG.
It is a figure which shows one specific example which performed the conventional planning procedure. FIG. 5 is a diagram showing a specific example of executing the planning procedure of FIG.

Next, a specific example of FIG. 5 will be described with reference to the flowchart of FIG. First, the delivery request information input unit 4
Inputs the goods delivery request information 2 from each of the business establishments 201 to 203 (S1). Then, the delivery planning unit 8 receives the goods delivery request information 2 from the delivery request information input unit 4, refers to the delivery destination information of the goods delivery request information 2, and stores the delivery cycle information of the corresponding business office from the delivery cycle information storage unit 7. Is obtained (S2). For example, it is assumed that the article delivery request information 2 input by the delivery request information input unit 4 is article delivery request information from the B establishment 202. Also, assuming that four pieces of article delivery request information are input, the respective delivery deadlines are October 9 (Wed), October 11 (Fri), and October 16
(Wed) and 10/17 (Thu). Office B 20
The second delivery cycle is weekly / water / gold, as shown in FIG. The delivery planning unit 8 compares the delivery deadline with the delivery cycle and the order receipt date to obtain the latest scheduled delivery date (S3). The order receiving date is the date when the article delivery request information 2 was input to the delivery planning system 1. In the first embodiment, the order receiving date is set to 10/1. October 9 (Wed) and 1
Since the goods delivery request, which is the delivery deadline of 0/11 (Fri) and 10/16 (Wed), matches the delivery cycle, the delivery planning unit 8 sets the delivery schedule to 10/9, 10/11 and 10/16, respectively. Plan your delivery schedule. However, 10/1
Since the article delivery request on 7 (Thu) does not match the delivery cycle, the delivery planning unit 8 searches for a scheduled delivery date that is earlier than the delivery deadline and matches the delivery cycle (S4). As a result, a scheduled delivery date of 10/16 is obtained, and the delivery planning unit 8 responds to the article delivery request, which is the delivery deadline of 10/17, as shown in FIG.
A delivery schedule is planned on October 16 (S5). In the above example, the order receiving date is 10/1. For this reason, there was a considerable number of days from the order receipt date to the delivery deadline date. However, if there is no margin between the order receiving date and the delivery deadline, there may be no date matching the delivery cycle between the delivery closing date and the order receiving date (S4). In this case, the delivery means is separately chartered on the delivery deadline and incorporated into the delivery cycle (S6).

FIG. 4 shows a delivery schedule planned by the conventional delivery planning system. Conventionally, the delivery schedule system does not have the concept of the delivery cycle, so the delivery schedule is planned on the delivery deadline. For this reason,
For an article delivery request for which October 17 is the delivery deadline, a delivery schedule is planned for October 17 as it is. Comparing the two-week delivery schedules of the week of October 7 and the week of October 14 in FIGS. 4 and 5, assuming that one day of delivery is performed by one truck, one truck has conventionally been replaced by four days. I was using. However, in the delivery planning system of the present invention,
Use one truck for 3 days. Therefore, the use rate of the truck can be reduced by 25%.

Embodiment 2 FIG. In the second embodiment, for each item delivery request from the same delivery destination, a period in which delivery can be performed by going back a predetermined number of days from the delivery deadline is obtained.
Then, the delivery feasible periods obtained for each article delivery request are compared, and an overlapping date is obtained. The following describes a delivery planning system that collectively delivers a plurality of articles on a predetermined day on the determined overlapping day. Note that a certain predetermined number of days before the delivery deadline is set as a deliverable period.

FIG. 6 is a configuration diagram of a delivery planning system according to the second embodiment. In FIG. 6, reference numeral 13 denotes deliverable period information. The deliverable period information 13 is information input in the delivery center 200 shown in FIG. In the second embodiment, the same delivery possible period is set for all the establishments. However, the delivery period may be different for each business establishment. If the delivery available period differs for each business establishment, the delivery available period is obtained for each business establishment. In the second embodiment, the deliverable period is set to 5 days for all business establishments (the delivery deadline is also included in the 5 days). Reference numeral 14 denotes a deliverable period setting unit for inputting deliverable period information 13. Reference numeral 15 denotes a deliverable period storage unit, and the deliverable period setting unit 14 stores the input deliverable period information 13 in the deliverable period storage unit 15. Further, the delivery planning unit 8 includes a deliverable period calculation unit 8.
1 and the same day delivery planning unit 82. The deliverable period calculation unit 81 extracts the deliverable period from the deliverable period storage unit 15 and obtains a deliverable execution period for the item delivery request from the delivery deadline of the item delivery request information and the deliverable period. The same-day delivery planning unit 82 compares the deliverable implementation periods of a plurality of goods delivery requests from the same delivery destination, and if there is a day that overlaps even one day, separate delivery requests from the same delivery destination are the same. Plan delivery schedules to deliver in batches per day. The other symbols in FIG. 6 have the same functions as the same symbols in FIG. FIG. 7 is a flowchart showing a planning procedure of a same-day delivery plan in the second embodiment. FIG. 8 is a diagram showing a specific example in which a delivery schedule is planned by a conventional delivery planning system. FIG. 9 is a diagram showing a specific example of executing the planning procedure of FIG. 7 in the second embodiment.

Next, a specific example of FIG. 9 will be described with reference to the flowchart of FIG. In the second embodiment, as in the first embodiment, the delivery planning system has the network configuration shown in FIG. Although not shown in FIG. 2, it is assumed that a plurality of sites are arranged at each of the business establishments 201 to 203. When an article delivery request occurs, the establishment transmits the article delivery request information 2 to the distribution center 200. The delivery request information input unit 4
The article delivery request information is input and transmitted to the delivery planning unit 8.
The deliverable period calculation unit 81 acquires the delivery deadline of the article delivery request information (S10). Next, the delivery plan period is acquired from the deliverable period storage unit 15 (S11). In the second embodiment, the deliverable period is the same for all business establishments. For example, the possible delivery period is five days.
When the deliverable period differs for each business establishment, the deliverable period calculation unit 81 extracts the deliverable period for each business place from the deliverable period storage unit 15 and obtains a deliverable implementation period. The deliverable period calculation unit 81 obtains the start date of the deliverable implementation period and the end date of the deliverable implementation period based on the delivery deadline and the deliverable period (S12). According to FIG.
Article delivery request from the site is October 7 (Mon), October 9
Three (Wed) and 10/11 (Fri) are input as the delivery deadline, respectively. Note that FIG. 9 shows that the article delivery request information is input to the distribution center 200 from the site A. Here, the goods delivery request information is directly input from each site to the distribution center, but the goods delivery request information may be input from each site via the business office to the distribution center. Also, although the delivery possible period can be determined for each business establishment, it can be determined for each site. When the deliverable period is set for each site, the deliverable period calculation unit 81 extracts the deliverable period for each site from the deliverable period storage unit 15 and implements deliverable based on the delivery deadline and the deliverable period. Calculate the period.
The deliverable period calculation unit 81 includes the delivery deadline date,
The delivery possible period is calculated by going back the delivery possible period from the delivery deadline. However, since the Saturdays and Sundays are holidays for the distribution center, business office, and site, the delivery schedule is planned excluding Saturdays and Sundays. According to FIG.
Delivery period is 10/1 (Tue) to 10 /
7 (Mon). The same day delivery plan unit 82 receives the deliverable execution period of the article a from the deliverable period calculation unit 81.
The same-day delivery planning unit 82 checks whether there is an article delivery request with the delivery destination of the site A among the preceding delivery requests (S
13). In this example, since there is no item delivery request to the site A as a delivery destination in the preceding delivery request,
A delivery schedule is planned with (Month) as the scheduled delivery date to the site A (S16).

Subsequently, the delivery request information input section 4 inputs the article delivery request information (article b) with the delivery destination being the site A. The delivery request information input unit 4 sends the article delivery request information to the delivery planning unit 8. The deliverable period calculation unit 81 calculates a deliverable execution period of the article b in the same manner as the article a described above. According to FIG. 9, the delivery possible implementation period of the article b is 1
0/3 (Thu) to 10/9 (Wed). Since there is a delivery request (delivery request for the article a) to the site A as the delivery destination in the preceding delivery request (S13), the delivery available execution period for the article b and the delivery available implementation period for the advance delivery request are compared. (S14). The delivery available period of each of the article a and the article b is 10/3 (Thu) to 10/7 (Mon).
Days overlap. Therefore, in this example, a delivery schedule is planned for the scheduled delivery date of the article a and the article b on October 7 (Monday) (S15). Further, the delivery request information input unit 4 inputs a delivery request for the article c from the site A. The delivery planning unit 8 receives the article delivery request information from the delivery request information input unit 4. The deliverable period calculation unit 81 calculates a deliverable execution period for the article c as well as the article a and the article b. According to FIG. 9, the delivery possible implementation period of the article c is 10/7 (month) to 10/11 (Fri). Since there is a delivery request (delivery request for the article a and the article b) to the site A as the delivery request in the preceding delivery request (S13), the delivery available period for the article c and the delivery time of the preceding article a and the article b are determined. Compare the respective delivery possible implementation periods (S1
4). As a result of comparison, article a, article b, and article c
/ 7 (month) overlaps the delivery possible implementation period. Therefore, the same-day delivery planning unit 82 plans to incorporate the delivery schedule for the articles a, b, and c into 10/7 (month) (S15).

FIG. 8 shows an article a in the conventional delivery planning system.
7 shows the result of planning a delivery schedule when inputting an item delivery request for item b and item c. Since the conventional delivery planning system does not have a concept of a deliverable period, a delivery schedule is planned such that the delivery deadline of each delivery request information is the delivery date. As a result, article a is 10
Delivery schedule is planned on / 7 (Mon), and item b is 1
A delivery schedule is scheduled for 0/9 (Wed) and for the article c on October 11 (Fri). As a result, the delivery to the site A is performed three times. However, in the delivery planning system according to the present invention, since the delivery schedule of the article a, the article b, and the article c is planned to the site A on October 7 (Monday), a plurality of articles requested to be delivered once are provided. Can be delivered at the same time. As described above, by using the delivery planning system of the present invention, the number of deliveries can be reduced, and the use efficiency of delivery means such as trucks can be increased. Further, the use cost of the delivery means can be reduced.

Incidentally, the above-mentioned article a, article b, and article c had dates that overlapped the respective delivery-performing periods. However, for example, when there is no day on which the delivery period of the article c overlaps with the article a or the article b, the same-day delivery planning unit 82 plans the delivery schedule so that delivery is performed on the delivery deadline of the article c.

Embodiment 3 In the third embodiment, the delivery capacity per day is set in advance in the delivery planning system.
Then, after planning the same-day delivery schedule to the same delivery destination (the same-day delivery schedule has been described in the second embodiment), when planning a delivery schedule to different destinations, the number of destinations per day The following describes a delivery planning system that plans within a range that does not exceed the delivery capacity.

FIG. 10 is a configuration diagram of a delivery planning system according to the third embodiment. In FIG. 10, article delivery request information 2 is input with article delivery request information from a plurality of establishments or a plurality of sites. For this reason, the delivery request information input unit 4 also inputs goods delivery request information from a plurality of offices or sites. The delivery plan unit 8 includes a collective delivery plan unit 84 in addition to the deliverable period calculation unit 81. The deliverable period calculation unit 81 calculates a deliverable execution period for each delivery destination because the delivery request information input unit 4 inputs the goods delivery request information from a plurality of offices or a plurality of sites. Note that, in the third embodiment, the deliverable period stored in the deliverable period storage unit 15 stores the same deliverable period for all offices and all sites.
However, the deliverable period may be different for each office or each site. In this case, the deliverable period calculation unit 81 retrieves the deliverable period of the relevant office or site from the deliverable period storage unit 15, and calculates the deliverable execution period based on the deliverable period and the delivery deadline. . The summary delivery planning unit 84 plans a delivery schedule for delivering the goods to a plurality of offices or sites within the range of the daily delivery capacity. The detailed operation of the collective delivery plan unit 84 will be described later. The other reference numerals are the same as those in the second embodiment, and a description thereof will be omitted.

FIG. 11 is a flowchart for explaining a procedure for planning a delivery schedule according to the third embodiment. FIG. 12 to FIG. 16 are diagrams specifically illustrating a delivery schedule planning process according to the third embodiment. FIG. 17 is a diagram showing a delivery schedule planned in the conventional delivery planning system.

Next, the procedure of planning a delivery schedule in the collective delivery planning section will be described with reference to the flowchart of FIG. 11 and FIGS. S20 to S24 in FIG.
Is a process similar to S10 to S14 in FIG. 7 of the second embodiment. FIG. 12 shows a deliverable execution period calculated by the deliverable period calculation unit 81 from the article delivery request information input from the delivery destination. In the third embodiment, the deliverable period is set to 5 days, as in the second embodiment. For example, from the A site, delivery 10/11 with delivery deadline 10
Goods 101 with delivery deadlines 0a and 10/14
The delivery 102a with the delivery deadline of a and 10/10 is input. The deliverable period calculation unit 81 stores the deliverable period (5 days) extracted from the deliverable period storage unit 15 and the articles 100a and 101, as in the second embodiment.
The delivery possible execution period is calculated based on the delivery deadlines a and 102a (S20 to S22). Article 1
The delivery possible execution period for 01a is the period 10 in FIG.
0. The delivery possible execution period for the article 101a is the period 101 in FIG. Further, the article 102
The delivery possible execution period for a is a period 102 in FIG. Hereinafter, similarly, the delivery possible execution period for each article is calculated from the delivery deadline and the deliverable period of the article delivery request information respectively input from the B spot, the C spot, the D spot, and the E spot. Period 10 shown in FIG.
4,105,107,108,109,111,11
2, 114 and 115 are delivery possible execution periods calculated by the delivery possible period calculation unit 81. In addition, the office and each site,
Since Saturday and Sunday are holidays, the delivery possible period is calculated without including Saturday and Sunday in the delivery period.

Next, the collective delivery planning unit 84 checks whether there is an article delivery request from the same delivery destination in the preceding article delivery request (S23). When there is an article delivery request from the same delivery destination, the delivery available period calculated for each article delivery request calculated by the deliverable period calculation unit 81 is compared. As a result of the comparison, if there is an overlapping period, a delivery schedule is planned so that a plurality of goods delivery requests are delivered together in one day in the overlapping period (S24, S2).
5). For example, articles 100a, 101a,
The overlap period of the delivery available execution period for the delivery request of 102a is an overlap period 103. In addition, overlapping period 10
Reference numeral 6 denotes an overlap period in response to a request for goods delivery of the goods 104a and 105a from the site B. Similarly, the overlap period at site C is overlap period 110, the overlap period at site D is overlap period 113, and the overlap period at site E is overlap period 116. Subsequently, the collective delivery planning unit 84 plans a delivery schedule to each site in consideration of the delivery capacity per day (S26). In the third embodiment, the daily delivery capacity is assumed to be one truck per day, and the number of delivery destinations to which one truck can be delivered is three. That is, the maximum number of deliveries per day is three. Therefore, when determining the delivery schedule, the collective delivery planning unit 84 plans so that the number of deliveries per day is within three. If the number of delivery destinations per day becomes three or more during planning, change the delivery schedule date within the overlapping period for each delivery destination.

FIG. 13 shows a delivery schedule to each site before the collective delivery planning unit 84 considers the daily delivery capacity. Taking the site A as an example, FIG.
Met. For this reason, the collective delivery planning unit 84
As shown in (2), the scheduled delivery date 117a to the site A is provisionally determined to be 10/10 (Thursday), which is the last day of the overlapping period. Similarly, as shown in FIG. 13, scheduled delivery dates 118a, 119a, and 1 for the B site, the C site, the D site, and the E site.
20a and 121a are provisionally determined on the last day of the overlap period. Comparing the delivery schedule to each site shown in FIG. 13 with the daily delivery capacity, it is planned that the delivery can be performed within the range of the delivery capacity. However, in FIG.
It is scheduled to be delivered to site B only on Wednesday, September 9. Also, on October 14 (Monday), a delivery schedule is planned only for the E site. By changing the delivery schedule at each site, the number of trucks used can be further reduced. For this reason, the collective delivery plan unit 84 re-plans the delivery schedule in consideration of the delivery capacity per day.

FIG. 14 shows the result of planning the delivery schedule again. According to FIG. 14, on October 9 (Wednesday), a delivery schedule to site A and site B is planned. On October 10 (Thursday), C site, D site, E
Planning a delivery schedule to the site. Comparing the delivery schedules of FIG. 13 and FIG. 14, in FIG. 13, the trucks are used for three days to deliver to the sites A, B, C, D, and E. However, in FIG. 14, the trucks are planned to be used for two days for delivery to the A, B, C, D, and E sites. Also, the delivery schedule after re-planning,
It is planned to be within daily delivery capacity.

Further, article delivery request information from the F site is input to the delivery planning system 1. The delivery deadline of the goods delivery request information from the F site is assumed to be 10/10 (Thursday). The deliverable period calculation unit 81 calculates a deliverable implementation period based on the delivery deadline from the F site and the deliverable period (S20 to S22).

FIG. 15 shows a deliverable execution period for the article 122a at the site F. The deliverable period of the F site is a period 122. Since there is no article delivery request from the site F in the preceding article delivery request information, S24 and S25
Is not performed. The summary delivery planning unit 84 determines a delivery schedule to the F site so that the number of deliveries per day does not exceed three. For example, the delivery deadline of the article delivery request information from the site F is 10/10 (Thursday). Referring to FIG. 14, on October 10 (Thursday), A
There are three delivery schedules planned for the site, site C and site D, and there is no room for delivery capacity. For this reason, the delivery schedule to the F site cannot be incorporated into October 10 (Thursday). The collective delivery planning unit 84 sets the date and time of the
A delivery schedule is planned for one day excluding (Thu). The collective delivery plan unit 84 searches for a delivery schedule that has been planned so far, and searches for a day in which the number of deliveries per day is less than three from 10/4 to 10/9. According to FIG. 14, on October 9 (Wednesday), two delivery schedules are planned to the site A and the site B, and there is room in the delivery capacity. Therefore, the collective delivery plan unit 84 determines the delivery schedule to the F site to be 10/9 (Wed).

FIG. 16 shows a delivery schedule from the site A to the site F planned by the collective delivery planning section 84. FIG.
According to No. 6, both October 9 (Wed) and October 10 (Thu) have three deliveries per day.

FIG. 17 shows a delivery schedule planned by the conventional delivery planning system based on the article delivery requests at the sites A to F. According to FIG.
On / 9 (Wednesday), a delivery schedule to site A and site B is planned. Also, on October 10 (Thu), a delivery schedule to the site C, site D, and site E is planned. Further, when the article delivery request information is input from the F site, the conventional delivery planning system plans a delivery schedule on October 10 (Thursday). However, since the daily delivery capacity is three, delivery to the F site will be made by chartering another truck. For this reason, in the conventional delivery planning system, two trucks are used every 10/10 (Thursday), so that the truck use cost increases. But,
In the delivery planning system according to the present invention, the collective delivery planning unit obtains a delivery possible execution period for each delivery destination, and plans a delivery schedule so as to fall within a range of daily delivery capacity within the delivery possible implementation period. For this reason, the use efficiency of the delivery means, for example, the truck becomes better than before,
Further, the use cost can be reduced.

In the above description, the collective delivery planning section 84 obtains the delivery possible period for each item delivery request information input to the delivery planning system 1, and further plans a delivery schedule to the same delivery destination. If there is, a duplicate delivery possible period is required so that delivery is made to the same destination on the same day within the delivery possible period.
However, this function is a function of the same-day delivery planning unit 82 described in the second embodiment. For this reason, the same-day delivery planning unit 82 may perform the process up to the process of obtaining an overlapping period of the delivery available period at the same delivery destination (the processes of S20 to S22 in FIG. 11).

Embodiment 4 FIG. In the fourth embodiment, after the delivery schedule is planned by the collective delivery planning unit 84 described in the third embodiment, if the number of deliveries per day exceeds the delivery capacity, the goods delivery exceeding the delivery capacity is performed. A delivery planning system for storing requests and re-planning the delivery schedule of an article delivery request exceeding the delivery capacity at a predetermined timing will be described below.

FIG. 18 is a configuration diagram of a delivery planning system according to the fourth embodiment. In FIG. 18, reference numeral 85 denotes an unplanned information output unit. Reference numeral 19 denotes an unplanned information storage unit. The unplanned information output unit 85 is a collective delivery planning unit 84
As a result of the planning of the delivery schedule, the article delivery request information which cannot be incorporated into the delivery schedule due to exceeding the daily delivery capacity is output to the unplanned information storage unit 19. The unplanned information storage unit 19 stores the article delivery request information output by the unplanned information output unit 85. Reference numeral 16 denotes readjustable period information. The re-adjustable period information 16 indicates the delivery plan of the goods delivery request information that could not be incorporated into the delivery schedule because the delivery schedule was planned by the collective delivery planning unit 84 and exceeded the daily delivery capacity. This information specifies a period during which re-planning is possible in order to perform again. A readjustable period setting unit 17 inputs readjustable period information 16. Reference numeral 18 denotes a readjustable period storage unit that stores readjustable period information 16 input by the readjustable period setting unit 17. In the fourth embodiment, there is only one readjustable period information in the delivery planning system.
That is, it is assumed that the same re-adjustable period information is provided for all establishments and all sites. The re-adjustable period information may be set to different periods depending on the establishment or the site. In this case, when re-planning the delivery schedule, the re-adjustable period calculated (target period for re-adjusting the delivery schedule)
Is calculated using the readjustable period information set for each business establishment or each site. 86 is a delivery re-planning unit.
The delivery re-planning unit 86 acquires the re-adjustable period information from the re-adjustable period storage unit 18 when the unscheduled information exists after the delivery schedule is planned by the collective delivery planning unit 84, and performs the readjustment. Find possible period. Then, it is planned to incorporate the unplanned information into the delivery schedule again within the range of the obtained readjustable period. The other reference numerals are the same as those in the third embodiment, and a description thereof will not be repeated.

FIG. 19 is a flowchart showing a procedure for replanning the delivery schedule according to the fourth embodiment. FIG. 20 is a diagram illustrating unplanned information using a specific example. In FIG. 20, reference numeral 130 denotes unplanned information. In the fourth embodiment, as in the third embodiment, the number of trucks held per day is one,
The number of deliverable items per truck is three. Because of this, the number of deliveries on October 10 (Thu) is four,
The item delivery request information of the item becomes unplanned information 130,
It is output to the unplanned information storage unit 19 by the unplanned information output unit 85. FIG. 21 is a diagram specifically illustrating the readjustment period. In the fourth embodiment, the readjustable period information is set to 5 days. The re-adjustable period is a five-day period including the day after the day on which the delivery schedule is readjusted. However, Saturdays and Sundays are not included in the re-adjustable period because the office or site is a holiday. For example, if the day of the re-planning is Tuesday, the re-adjustable period is from Wednesday of the next day to Thursday of the next week. Also,
In the figure, the circles indicate delivery schedules to different offices or different sites. FIG. 22 is a diagram showing a delivery schedule planned in the conventional delivery planning system.

Next, the procedure for re-planning the delivery schedule will be described below with reference to FIGS. 20 and 21 in accordance with the flowchart of FIG. Before starting the process of S30 in FIG. 19, after the delivery schedule is planned by the collective delivery plan unit 84, the article delivery request information that cannot be incorporated in the delivery schedule because the daily delivery capacity is exceeded is:
It is assumed that the unplanned information is stored in the unplanned information storage unit 19 by the unplanned information output unit 85. The delivery schedule planning by the delivery re-planning unit 86 is performed after the process of receiving the article delivery request information 2 from the office and the site is completed.

In FIG. 19, the delivery re-planning unit 86 checks whether there is any unplanned information (S30). If there is no unplanned information, the process ends. If there is unplanned information, re-adjustable period information is obtained from the re-adjustable period storage unit 18 (S31). Then, a readjustment start date and a readjustment end date are calculated based on the obtained readjustable period information and today's date (S32). For example, if today's date is 10/4 (Fri), the re-adjustable period will be 5 days ahead including the next day, so the readjustment start date will be 10/7 (Monday), and the readjustment end date will be 10/11
(Fri). Then, the delivery re-planning unit 86 repeats the processing from S33 to S40 described below every day from the readjustment start date to the readjustment end date. S33
, The delivery re-planning unit 86 acquires the number of deliveries on the readjustment date. If the number of deliveries is smaller than the delivery capacity, it is determined that there is enough delivery capacity on the readjustment date (S34), the unplanned information is extracted from the unplanned information storage unit 19, and a new delivery date on the readjustment date is obtained. Incorporate a schedule. However, when extracting the unplanned information from the unplanned information storage unit 19, the unplanned information whose delivery deadline date has not arrived by the readjustment date is extracted. In particular, if there are multiple pieces of unplanned information whose delivery deadline is after the readjustment date,
The unplanned information with the smallest delivery deadline is preferentially acquired (S35). If unplanned information can be obtained (S
36), a new delivery schedule is added on the readjustment date (S37). Then, the delivery re-planning unit 86 deletes the unplanned information that could be incorporated into the delivery schedule from the unplanned information storage unit 19 (S38). After that, S3 again
Get the number of deliveries on the readjustment date of 3. Here, the delivery schedule acquired immediately before is added to the number of deliveries to be acquired. If the number of deliveries exceeds the delivery capacity, the readjustment date is advanced by one day because there is no room in the delivery capacity (S39). At this time, since Saturday and Sunday are business office or site holidays, in Embodiment 4, the readjustment date is advanced by one day except for Saturday and Sunday. As described above, the processes of S33 to S40 are repeatedly performed until the readjustment date exceeds the readjustment end date (S41). For example, FIG. 21 shows a delivery schedule when the date of the next day when the delivery schedule is readjusted is 10/7 (month). In FIG. 21, since the date of the next day is 10/7, the readjustment start date is 10/7 (month).
And the end date of the readjustment will be October 11 (Fri). Then, the delivery re-planning unit 86 starts from 10/7 and
Until it exceeds 0/11, the processing of S33 to S40 in FIG. 19 is repeatedly performed. On 10/7, which is the readjustment start date, the number of deliveries is the same as the delivery capacity (S34), so the readjustment date is advanced one day ahead to 10/8 (S39). According to FIG. 21, since the number of deliveries in 10/8 is two, there is room in the delivery capacity (S34). For this reason, the delivery re-planning unit 8
6 obtains, from the unplanned information storage unit 19, the article delivery request information whose delivery deadline comes after the readjustment date. For example, the unplanned information 130 is retrieved from the unplanned information storage unit 19 and added to the delivery schedule of 10/8 (Tue) as shown in FIG.

FIG. 22 shows an example of a delivery schedule in a conventional delivery planning system. In FIG. 22, 10/1
The goods delivery request information exceeding the delivery capacity exists at 0 (tree) (in the delivery planning system of the present invention, the goods delivery request information exceeding the delivery capacity is referred to as unplanned information 130).
In the conventional delivery planning system, the unplanned information 130 is obtained by charting a truck as another delivery means.
Plan your delivery schedule to deliver on another chartered truck on Thursday. Therefore, 10
In the case of / 10 (Thu), delivery will be made by two trucks. However, if the delivery planning system according to the present invention is used, the article delivery request information that has become unplanned information is temporarily stored in the unplanned information storage unit, and confirms the delivery capability within the re-adjustable period at a predetermined timing. If there is a day when the delivery capacity is available, the unplanned article delivery request information is incorporated into the delivery schedule on the day when the delivery capacity is available. For this reason, delivery means, for example, trucks can be delivered by one vehicle per day.

FIG. 23 shows another example. As shown in FIG. 23, after the delivery schedule is planned by the collective delivery planning section 84, the unplanned information 131a, 131b, and the 10/10 (Tree) indicates that unplanned information 131c exists. If today is 10/4 (Fri), the re-adjustable period is 10
/ 7 (Monday) to 10/11 (Friday). Delivery replanning unit 8
No. 6 confirms whether there is a day when the delivery capacity has a margin in the re-adjustable period. According to FIG.
It can be seen that there is room in the delivery capacity. Unplanned information 13
For 1a and 131b, the delivery deadline is 10/9 (Wed). In addition, the unplanned information 131c is Thursday, October 10
Is the delivery deadline. The delivery re-planning unit 86 is a delivery deadline date of 10/7 or later from the unplanned information storage unit,
Unplanned information having the delivery deadline closest to 10/7 is acquired. For this reason, the delivery re-planning unit 86 extracts the unplanned information 131a from the unplanned information storage unit 19, and
Is incorporated in the delivery schedule of 10/7 (month). As a result, the number of deliveries of 10/7 becomes three, so that there is no room in the delivery capacity. Then, the next 10/8
When the number of deliveries of (Tue) is confirmed, according to FIG. 23, there is room for one delivery. For this reason, the delivery re-planning unit 86 acquires the unplanned information 131b from the unplanned information storage unit 19, and
Incorporate into the 0/8 delivery schedule. This is 10/8
Since the number of deliveries is three, other delivery schedules cannot be entered. Subsequently, the delivery re-planning unit 86
The number of deliveries per day is checked in the order of October 9, October 10, and October 11. The unplanned information 131c stored in the unplanned information storage unit 19 has room for one case on October 11
Since the delivery deadline is 10/10, the delivery schedule cannot be incorporated on 10/11. Here, the unplanned information 131c is stored in the unplanned information storage unit 19 without being planned. However, before the deadline for delivery is reached, another delivery method is chartered and the delivery is planned.

Embodiment 5 In the fifth embodiment, a description will be given below of a delivery planning system that plans a delivery schedule of articles and a collection schedule of articles.

FIGS. 25 to 28 are configuration diagrams of a delivery planning system according to the fifth embodiment. In FIG.
Reference numeral 20 denotes article collection request information. Goods collection request information 20
Is information input from each office or each site. The article collection request information 20 includes at least collection destination information, collection request date information designating the collection date, and collection article information designating the article desired to be collected. The delivery request information input unit 4 newly inputs the article collection request information 20 in addition to the article delivery request information 2. The article delivery request information 2 and the article collection request information 20 input by the delivery request information input unit 4 are:
Send to delivery planning section 8. A collection planning unit 87 plans a collection schedule based on the article collection request information 20 passed from the delivery request information input unit 4. Reference numeral 88 denotes an unplanned collection information output unit. Reference numeral 21 denotes an unplanned collection information storage unit. The item collection request information 20 for which the collection schedule has not been determined by the collection planning unit 87 is output to the unplanned collection information storage unit 21 by the unplanned collection information output unit 88. The other reference numerals are the same as those described in the fourth embodiment, and a description thereof will not be repeated.

FIG. 25 shows that the delivery planning unit 8 of the delivery planning system described in the fourth embodiment is different from the collection planning unit 87.
FIG. 1 is a configuration diagram of a delivery planning system including an unplanned collection information output unit 88 and a delivery planning system 1 newly including an unplanned collection information storage unit 21. In FIG. 26, the delivery planning unit 8 of the delivery planning system 1 described in the third embodiment includes a collection planning unit 87 and an unplanned collection information output unit 88. FIG. 1 shows a configuration diagram of a delivery planning system provided with 21. Also,
FIG. 27 shows that the delivery planning unit 8 of the delivery planning system 1 described in the second embodiment includes a collection planning unit 87 and an unplanned collection information output unit 88, and the delivery planning system 1 includes the unplanned collection information storage unit 21. 1 shows a configuration diagram of a delivery planning system provided. FIG. 28 shows that the delivery planning unit 8 of the delivery planning system 1 described in the first embodiment includes a collection planning unit 87 and an unplanned collection information output unit 88, and that the delivery planning system 1 includes an unplanned collection information storage unit. FIG. 1 shows a configuration diagram of a delivery planning system provided with 21. Embodiment 5
Now, an example in which the delivery planning system 1 described in the fourth embodiment includes the collection planning unit 87 will be described.
Even when the delivery planning system 1 described in the first to third embodiments includes the collection planning unit 87, the operation of the collection planning unit 87 is the same as the operation of the collection planning unit 87 in FIG. Assumed to be performed. Similarly, the unplanned collection information output unit 88 and the unplanned collection information storage unit 21 of FIG. 26 to FIG.
Perform the same operation as that of the same reference numeral.

FIG. 29 is a flowchart showing a procedure for planning a collection schedule according to the fifth embodiment. FIG. 30 is a diagram illustrating an example of generation of the article collection request information. In FIG. 30, reference numeral 140 denotes an article collection request from location C. Also,
□, △, ○ are the collective delivery planning section 84 and the delivery re-planning section 86
Shows delivery schedules for the places A, B, and C that have already been planned. FIG. 31 is a diagram illustrating an example of a collection schedule planning process performed by the collection planning unit 87. FIG. 31 shows that since the collection request 140 is the location C, the collection can be performed on October 10 (Thursday), which is the same as the delivery schedule to the location C already planned as the delivery schedule.

Next, the procedure of planning the collection schedule will be described with reference to FIGS. 30 and 31 in accordance with the flowchart of FIG. It is assumed that the delivery schedules of □, Δ, and に shown in FIG. 30 have already been planned by the collective delivery planning unit 84 and the delivery re-planning unit 86 before the processing in FIG. 29 is performed. In FIG. 29, first, the article collection request information 20 is input to the delivery planning system 1 from an office or a site (S50). In particular, it is assumed here that a collection request for which a collection date is specified has occurred. However, S5
Although not shown at 0, a collection request for which a collection date is not specified is also input. The delivery request information input section 4 inputs the article collection request information 20 and passes it to the delivery planning section 8. The collection planning unit 87 searches for a delivery schedule that is already planned based on the collection request date information of the article collection request information 20 passed from the delivery request information input unit 4, and retrieves the specified collection request date. The same business office as the collection destination in the delivery schedule,
Alternatively, it is confirmed whether a delivery schedule of the place exists (S51). For example, as shown in FIG.
It is assumed that a collection request in which (Thu) is the collection date has been issued from location C. Looking at the delivery schedule of FIG.
10 (Thu) has a delivery schedule to location C. For this reason, the collection request 140 is incorporated into the schedule so that collection is performed simultaneously with delivery on October 10 (Thursday) (S52). If the delivery schedule of the same collection destination (delivery destination) is not planned on the collection request date in the already planned distribution schedule, a separate delivery means is secured (for example, the delivery means is a truck). , The collection schedule is incorporated into the collection request date on October 10 (Thursday). However, as for the collection of the articles, since the articles can be collected without specifying the collection date, it is also possible to input the article collection request information 20 with no specified collection date to the delivery planning system 1. In this case, the above S5
In 3, in the case of a collection request for which a collection date is not specified, the unplanned collection information output unit 88 causes the unplanned collection information storage unit 21 to store unplanned article collection request information. In S51, if the specified date of collection date is set in the item collection request information, a search is performed to determine whether the same collection destination (delivery destination) exists on the same collection date (delivery date) in the delivery schedule. I was However, if the collection date is not specified, a search is made to see if there is a delivery schedule of the same collection destination (delivery destination) in the delivery schedule on a date in the future from the date on which the item collection request information 20 is received, and the same collection is performed. If there is a delivery schedule for the destination (delivery destination), the collection schedule is incorporated on that day. For example, 1
When a collection request is issued from the place C on 0/7 (Monday) (today is 10/7 (Monday)), the collection planning unit 87
Check future delivery schedules from today. For example, the delivery schedule to the place C from October 7 (Mon) to October 11 (Fri) is not planned, and
If a delivery schedule to place C is planned on (Mon), the collection planning unit 87 collects the collection request received on October 7 (Mon) on October 14 (Mon) as shown in FIG. Plan your schedule.

FIG. 33 shows an example of a planning result of a collection schedule in the conventional delivery planning system. The delivery schedule shown in FIG. 33 is from 10/7 (Mon) to 10
No delivery schedule is planned for location C during the period / 11 (Fri). For example, if a collection request from location C occurs on October 10 (Thu), the collection request 141 is
Although the delivery schedule to location C is not planned at 0 (Thu), the collection schedule of delivery request 141 is planned at 10/10. However, in the delivery planning system according to the present invention, the collection planning unit 87 plans the collection schedule so that the delivery schedule is prioritized over the collection schedule and the collection schedule is also performed on the day when the delivery schedule is planned. For this reason, FIG.
In the delivery planning system according to the present invention, the unplanned collection information output unit 88 stores the unplanned item collection request information 20 in the unplanned collection information storage unit 21 for the collection request generated on October 3 (Thursday) of the third. .

Embodiment 6 FIG. In the sixth embodiment, a delivery planning system that replans the collection schedule of the item collection request information that has become unplanned collection information in the fifth embodiment will be described below. Note that the process of replanning the collection schedule described in the sixth embodiment is performed after the end of one day's work, for example, after the input of the goods delivery request information and the goods collection request information from the business site or the site is completed. Assumed to be performed.

FIG. 34 is a configuration diagram of a delivery planning system according to the sixth embodiment. In FIG. 34, the collection planning unit 87 is the same-day collection re-planning unit 89 and the collection recovery re-planning unit 9
0 is provided. When the delivery schedule of the same collection destination (delivery destination) as the unplanned collection request information is planned, the collective collection re-planning unit 90 becomes unplanned on the same day as the planned delivery schedule. A collection schedule for the required goods collection request information. In addition, the same-day collection re-planning unit 89, if there is a day less than the daily delivery capacity in the already scheduled delivery schedule and collection schedule, unplanned items on the day less than the delivery capacity Plan a collection schedule for collection request information. The other reference numerals are the same as in the fifth embodiment, and a description thereof will not be repeated. In the sixth embodiment, the operation of the collective collection / replanning unit 90 shown in FIG. 34 will be described. The operation of the same day collection / replanning unit 89 will be described in detail in another embodiment. FIG.
33 is a flowchart showing a procedure for replanning a collection schedule in the sixth embodiment. FIG. 36 is a diagram illustrating a process of replanning the collection schedule by the collective collection and replanning unit according to the sixth embodiment. In FIG. 36, 150 and 15
1 indicates a collection request. The collection request date of the collection request 150 is 10/10 (Thu). The collection request date of the collection request 151 is October 11 (Fri). Collection request 15
0,151 is input to the delivery planning system, and a collection schedule is planned by the collection planning unit 87. However, there is no delivery schedule to the same collection destination (delivery destination) before the collection request date, and daily delivery is performed. Since there is no day with sufficient capacity, the information is unplanned collection information, and the collection requests 150 and 151 are stored in the unplanned collection information storage unit 21. Unplanned collection request 150,
151, when a delivery schedule to the same place as the collection destination is planned after a certain period has elapsed, the collection schedule is planned by the collective collection and replanning unit 90. FIG.
FIG. 7 is a diagram showing a result of planning a collection schedule in a conventional delivery planning system.

Next, the collection and re-planning procedure by the collective collection and re-planning unit 90 will be described with reference to FIG. Note that the collection and re-planning by the collective collection and re-planning unit 90 is a process performed after the input of the article delivery request information and the article collection request information from the business office and the site is completed. First, the collective collection and replanning unit 90 refers to the unplanned collection information storage unit 21 and checks whether unplanned collection information exists (S60). If there is no unplanned collection information, the process ends. If there is unplanned collection information, the unplanned collection information storage unit 21 preferentially retrieves the collection request information with a smaller collection request date (S61). For example, in FIG. 36, the collection request 150 and the collection request 151 are stored in the unplanned collection information storage unit 21. Since the collection request date is smaller for the collection request 150, the collective collection and replanning unit 90 takes out the collection request 150 with priority. next,
The collective collection and re-planning unit 90 checks the already-planned delivery schedule and checks whether a delivery schedule to the same collection destination (delivery destination) is planned. Collection request 15
Since 0 is a request for collection at the place C, the collective collection and re-planning unit 90 checks whether the delivery schedule includes a delivery plan to the place C. According to FIG. 36, a delivery schedule to location C is planned on October 7 (Mon) and October 8 (Tue). Assuming that the date on which the collective collection re-planning process is performed is 10/7 (Monday), the collective collection re-planning unit 90 sets the collection request 150 to 10 A collection schedule is planned on / 8 (Tue) (S63). At this time, when calculating the daily delivery capacity, since the request is a collection request to the same delivery destination (collection destination) whose delivery schedule is already planned, the added collection schedule is not added to the number of cases. If the delivery schedule does not include a delivery schedule to the same collection destination (delivery destination), a separate collection (delivery) unit, for example, a charter is scheduled to carry out collection by chartering a truck (S64). Thereafter, the collection request information to which the collection schedule has been added is deleted from the unplanned collection information storage unit 21 (S65). However,
Separately carrying out collection by chartering a delivery means is a collection request in which a collection request date is specified. A collection request for which a collection request date is not specified may be collected at any time. Therefore, the collection request information is stored in the unplanned collection information storage unit 21 until a delivery schedule to the same delivery destination as the collection destination occurs. Keep it. Next, the collective collection re-planning unit 90
Sets the collection schedule of the collection request 151 to S60 to S6.
Re-plan in order of 5. The collection request 151 specifies a collection request date. Since the date of the day when the processing of the collective collection and re-planning is performed is 10/7 (month), it is 10/8
From (Tue) to 10/11 (Fri), check if there is a delivery schedule to place C. On October 8 (Tue), a delivery schedule to place C is planned. Therefore, the collection schedule of the collection request 151 is planned to be 10/8 (Tue). Also, the collection schedule of the collection request 150 was planned on October 8 (Tue), but the delivery schedule to location C has already been planned on October 8 (Tue). Even if is added, three cases remain. In the collection schedule in the conventional delivery planning system shown in FIG.
However, the collection schedule of the collection request 150 is determined to be 10/10 (Thursday) even though there is no delivery schedule to the place C. For this reason, for example, when the delivery capacity per day is three, the collection (delivery) means such as a truck is separately chartered in order to perform the collection request 150,
Recovery must be performed. For this reason, compared with the delivery planning system of the present invention, an extra truck must be owned, and the cost of the collection operation increases.

Embodiment 7 FIG. In Embodiment 7, FIG.
The re-planning procedure of the collection schedule by the same-day collection re-planning unit 89 shown in FIG. FIG. 38 is a flowchart showing a procedure for replanning the collection schedule in the seventh embodiment. FIG. 39 is a diagram illustrating a process of replanning the collection schedule by the same day collection and replanning unit according to the seventh embodiment. In FIG. 39, collection requests 150 and 151 are stored as unplanned collection request information in the unplanned collection information storage unit 21 as in FIG. 36 described in the sixth embodiment. The collection requests 150 and 151 are unplanned because the collection schedule cannot be planned when the collective collection and replanning unit 90 performs the collection and replanning. When confirming that the unplanned collection information storage unit 21 has the unplanned collection request information, the collection and replanning unit 89 on the same day secures the already scheduled delivery schedule and
If there is a day less than the day's delivery capacity, a collection schedule of unplanned collection information is planned on that day.

Next, a procedure for replanning the collection schedule by the same day collection / replanning unit 89 will be described with reference to FIG. The rescheduling of the collection schedule by the same day collection and replanning unit 89 is performed after the input of the goods delivery request information and the goods collection request information from the office and the site is stopped and completed, and the collection by the collective collection and replanning unit 90 is performed. It shall be performed after rescheduling the schedule. First, the same day collection and replanning unit 89 checks whether unplanned collection information exists in the unplanned collection information storage unit 21 (S70).
If there is no unplanned collection information, the process ends.
When there is unplanned collection information, the collection request information is extracted from the unplanned collection information storage unit 21 with priority given to the collection request information with a smaller collection request date. A collection request without a collection date is extracted after the processing of the collection request information with the collection request date is completed (S71). For example, FIG.
9, a collection request 150 and a collection request 151 are stored in the unplanned collection information storage unit 21. In the collection request 150, the collection request date is specified as 10/10 (Thu),
It is assumed that the collection request 151 does not specify a collection request date. On the same day, the collection re-planning unit 89 takes out the collection request 150 from the unplanned collection information storage unit 21 with priority. Next, the same day collection re-planning unit 89 checks whether the collection schedule of the same collection destination as the unplanned collection request is planned in the collection schedule already planned (S72). If a collection schedule for the same collection destination is planned, a collection schedule for another collection request is incorporated on the same day as the planned collection schedule (S73). At this time, when calculating the daily delivery capacity, the newly added collection schedule is not added to the number of cases. In the process of S72, the same collection destination (delivery destination)
If no collection schedule is planned, the same-day collection and re-planning unit 89 determines whether there is a day of the number of deliveries less than the daily delivery capacity in the delivery schedule of the day after the date of the day. Is confirmed (S73). If there are days with the number of deliveries less than the delivery capacity, a collection schedule is planned on a day less than the delivery capacity (S7).
4). For example, the delivery capacity per day is three. The date on the day is the date when the same day delivery re-planning process is performed, and is set to 10/7 (month). Looking at FIG. 39,
On 10/8 (Tue) the next day of the day, there is a day when the number of deliveries is two. Therefore, the same day collection and replanning unit 89
On 0/8 (Tue), a collection schedule for the collection request 150 is planned. Then, the same day collection and replanning unit 89 deletes the collection request information from which the collection schedule can be replanned from the unplanned collection information storage unit 21 (S75).

Next, the same day collection / replanning unit 89 extracts the collection request 151 from the unplanned collection information storage unit 21. Then, since the collection schedule of the collection request 150 was planned on October 8 (Tue) in the processing of S74 and S75, S7
2. The collection schedule of the collection request 151 can be planned to be 10/8 (Tue) by the processing of S73.

As described above, in the seventh embodiment, when the collection schedule is re-planned, first, on the day when the collection schedule to the same collection destination is planned, another unplanned collection request The priority is to incorporate a collection schedule. If a collection schedule is not planned for the same collection destination, the daily delivery capacity is further calculated. To plan. Therefore, as in the example described in FIG.
Since the collection request 150 and the collection request 151 are the same collection destination, after the collection schedule of the collection request 150 is planned first, the collection schedule of the collection request 151 can be planned on the same day. Since the collection destination is the same, for example, two collection operations can be performed by one truck.

[0060]

As described above, according to the delivery planning system of the present invention, a delivery schedule can be planned according to delivery cycle information. For this reason, if the delivery cycle is considered to be delivery by regular flights, there is an effect that the use efficiency of delivery means, for example, trucks, can be improved by adjusting the delivery schedule to the regular flights.

Further, the delivery possible period is obtained based on the delivery possible period, and the delivery schedule to the same delivery destination is set such that the delivery is performed on one overlapping day in the delivery possible period for each item delivery request. To plan. For this reason, the delivery schedules to the same delivery destination are combined into one, so that when performing delivery by delivery means, for example, trucks, the effect of reducing the number of times the trucks are used as compared with the conventional delivery planning system is obtained. is there.

When the delivery planning system has a daily delivery capacity, the delivery schedule to a plurality of delivery destinations may be planned so that the number of deliveries per day is within the delivery capacity within the delivery possible implementation period. it can. For this reason, there is an effect that the use efficiency of a daily delivery means, for example, a truck can be improved.

A delivery request that cannot be incorporated into a once-planned delivery schedule can be stored as an unplanned delivery request. Then, after the delivery schedule is once performed, the delivery schedule can be re-planned in the re-adjustable period after a certain period has elapsed. Further, when re-planning the delivery schedule, a delivery schedule of a delivery request that is unplanned on a day when the delivery capacity is available is planned. Therefore, even if the delivery schedule cannot be determined on the day when the delivery request is received, if a delivery schedule of cancellation or change occurs at a later date, a new delivery schedule can be added based on the change status. For this reason, even if there is a change in the once-scheduled delivery schedule, the delivery status is automatically grasped and the delivery schedule is rescheduled, so that there is an effect that an optimal delivery schedule can always be made.

In addition, a collection schedule is planned together with the delivery schedule. Then, as for the collection schedule, when a delivery schedule is provided at the same collection destination as the collection destination (delivery destination), the collection schedule is planned to perform collection on the same day as the distribution schedule. For this reason, the collection to the same collection destination is performed simultaneously with the delivery operation, so that there is an effect that the use efficiency of the delivery means, for example, the truck can be improved.

Further, when the collection schedule is planned, if there is a collection request that is unplanned because there is no delivery schedule to the same collection destination (delivery destination), once the collection schedule is planned. After that, perform the collection schedule again. In the second collection schedule, a collection schedule is planned on a day when there is room in the delivery capacity. For example, if the collection request date is a collection request that is not specified, collection work may be performed at any time, so if you plan a collection schedule on a day when there is enough delivery capacity,
For example, there is an effect that delivery means such as a truck can be used effectively.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a delivery planning system according to a first embodiment of the present invention.

FIG. 2 is a network configuration diagram of a delivery planning system according to the first embodiment of the present invention.

FIG. 3 is a flowchart illustrating an example of a delivery schedule planning procedure according to the first embodiment of the present invention.

FIG. 4 is a diagram showing a specific example of executing a conventional planning procedure.

FIG. 5 is a diagram showing a specific example of executing the planning procedure of FIG. 3;

FIG. 6 is a configuration diagram of a delivery planning system according to a second embodiment of the present invention.

FIG. 7 is a flowchart showing a planning procedure of a same-day delivery plan according to the second embodiment of the present invention.

FIG. 8 is a diagram showing a specific example of executing a conventional planning procedure.

FIG. 9 is a diagram showing a specific example of executing the planning procedure of FIG. 7;

FIG. 10 is a configuration diagram of a delivery planning system according to a third embodiment of the present invention.

FIG. 11 is a flowchart illustrating a procedure for planning a delivery schedule according to the third embodiment of the present invention.

FIG. 12 is a diagram specifically explaining a planning process of a delivery schedule according to the third embodiment of the present invention.

FIG. 13 is a diagram specifically explaining a planning process of a delivery schedule according to the third embodiment of the present invention.

FIG. 14 is a diagram specifically explaining a planning process of a delivery schedule according to the third embodiment of the present invention.

FIG. 15 is a diagram specifically illustrating a delivery schedule planning process according to the third embodiment of the present invention.

FIG. 16 is a diagram specifically illustrating a process of planning a delivery schedule according to the third embodiment of the present invention.

FIG. 17 is a diagram showing a delivery schedule planned by a conventional delivery planning system.

FIG. 18 is a configuration diagram of a delivery planning system according to a fourth embodiment of the present invention.

FIG. 19 is a flowchart showing a procedure for planning a delivery schedule according to the fourth embodiment of the present invention.

FIG. 20 is a diagram for explaining unplanned information according to a fourth embodiment of the present invention using a specific example.

FIG. 21 is a diagram specifically illustrating a readjustment period according to the fourth embodiment of the present invention.

FIG. 22 is a diagram showing a delivery schedule planned in a conventional delivery planning system.

FIG. 23 is a view for explaining unplanned information according to a fourth embodiment of the present invention using a specific example.

FIG. 24 is a diagram specifically illustrating a readjustable period according to the fourth embodiment of the present invention.

FIG. 25 is a configuration diagram of a delivery planning system according to a fifth embodiment of the present invention.

FIG. 26 is a configuration diagram of a delivery planning system according to a fifth embodiment of the present invention.

FIG. 27 is a configuration diagram of a delivery planning system according to a fifth embodiment of the present invention.

FIG. 28 is a configuration diagram of a delivery planning system according to a fifth embodiment of the present invention.

FIG. 29 is a flowchart showing a procedure for planning a collection schedule according to the fifth embodiment of the present invention.

FIG. 30 is a diagram showing an example of generation of article collection request information according to Embodiment 5 of the present invention.

FIG. 31 is a diagram illustrating an example of a collection schedule planning process by a collection planning unit according to Embodiment 5 of the present invention.

FIG. 32 is a diagram illustrating an example of a collection schedule planning process performed by a collection planning unit according to Embodiment 5 of the present invention.

FIG. 33 is a view showing an example of a result of planning a collection schedule in a conventional delivery planning system.

FIG. 34 is a configuration diagram of a delivery planning system according to a sixth embodiment of the present invention.

FIG. 35 is a flowchart showing a procedure for planning a collection schedule according to the sixth embodiment of the present invention.

FIG. 36 is a diagram for explaining a replanning process by the collective collection and replanning unit according to the sixth embodiment of the present invention.

FIG. 37 is a diagram showing a collection schedule planned in a conventional delivery planning system.

FIG. 38 is a flowchart showing a procedure for planning a collection schedule according to the seventh embodiment of the present invention.

FIG. 39 is a view for explaining a recovery / planning process by the same-day recovery / replanning unit according to the seventh embodiment of the present invention.

[Explanation of symbols]

1 delivery planning system, 2 article delivery request information, 3 delivery cycle information, 4 delivery request information input section, 6 delivery cycle information setting section, 7 delivery cycle information storage section, 8 delivery planning section, 9 delivery schedule storage section, 10 delivery Schedule output unit, 11 delivery schedule, 13 deliverable period information, 14 deliverable period setting unit, 15 deliverable period storage unit, 16 readjustable period information, 17
Readjustable period setting unit, 18 readjustable period storage unit,
19 unplanned information storage unit, 20 article collection request information, 21
Unplanned collection information storage unit, 81 Delivery possible period calculation unit,
82 Same day delivery planning department, 84 Consolidated delivery planning department, 85
Unplanned information output section, 86 Delivery re-planning section, 87 Collection planning section, 88 Unplanned collection information output section, 89 Same-day collection re-planning section, 90 Collective collection re-planning section, 100, 101,
102, 104, 105, 107, 108, 109, 1
11, 112, 114, 115 period, 100a, 10
1a, 102a, 104a, 105a, 107a, 10
8a, 109a, 111a, 112a, 114a, 11
5a Articles, 103, 106, 110, 113, 116
Overlap period 117, 118, 119, 120, 12
1,122 period, 117a, 118a, 119a, 1
20a, 121a, 122a Expected delivery date, 117b,
118b, 119b, 120b, 121b Delivery schedule, 130, 131, 131a, 131b, 131
c Unplanned information, 140, 141, 150, 151 Collection request, 200 distribution center, 201 A establishment, 2
02 B establishment, 203 C establishment.

──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Akihiko Kojima 2-3-2 Marunouchi, Chiyoda-ku, Tokyo Mitsubishi Electric Corporation (72) Inventor Sakae 2-3-2 2-3 Marunouchi, Chiyoda-ku, Tokyo Mitsubishi Electric (72) Inventor Shusuke Ueda 2-6-1, Otemachi, Chiyoda-ku, Tokyo Mitsubishi Electric Building Techno Service Co., Ltd. (72) Isamu Takeda 2-6-1, Otemachi, Chiyoda-ku, Tokyo Mitsubishi Inside Denki Building Techno Service Co., Ltd. (72) Inventor Hiroyuki Mizuno 7-19-1, Arakawa, Arakawa-ku, Tokyo Inside Meltech Business Co., Ltd. (72) Takaichi Shibusawa 7-1-1, Arakawa, Arakawa-ku, Tokyo No. Meltech Business Co., Ltd. (56) References JP-A-6-28369 (JP, A) JP-A-6-263220 (JP, A) JP-A-6-176040 (JP, A) JP-A-5-242121 (JP, A) JP-A-7-210610 (JP, A) JP-A 8-212494 (JP, A) (58) Survey Field (Int.Cl. ⁷ , DB name) G06F 17/60 B65G 1/137 JICST file (JOIS)

Claims (7)

(57) [Claims] [1] At least delivery destination information and delivery deadline
Delivery request information consisting of the delivery information and the delivery information
And a delivery request information input section for inputting
Delivery planning system that plans delivery schedules according to request information
The stem has the following elements:
Delivery planning system (a) Delivery in which a predetermined number of days is determined in advance as a deliverable period
Possible period setting unit, (b) The possible delivery period determined by the possible delivery period setting unit
Delivery period storage unit for storing, delivery available stored in (c) above delivery period storage unit
And the delivery deadline of the goods delivery request information
Request for delivery of a specified product from the same delivery destination and delivery of another product
The delivery schedule so that the number of delivery
Delivery planning unit to plan Joule, the (d) the delivery schedule in which the delivery planning unit had planned serial
Delivery schedule storage unit for憶delivery for storing a storage unit (e) the delivery schedule
Delivery schedule output that extracts and outputs the schedule
Force part. 2. The delivery planning unit retrieves a deliverable period from the deliverable period storage unit,
Deadline for delivery period and delivery request information
Due to the delivery date, the above delivery deadline is
Delivery time period for which delivery time is required to be included
The calculation unit and the predetermined delivery from the same delivery destination determined by the delivery possible period calculation unit
Delivery possible period for goods delivery request of another and another goods
Overlapping delivery available period for delivery request
Find the delivery date and combine a given item with another item
The number of deliveries is reduced to one and duplicate deliveries are possible.
Delivery schedule as a delivery date for simultaneous delivery of a given day
The same day delivery planning department that plans the schedule
The delivery planning system according to claim 1, wherein 3. The delivery planning system according to claim 1, wherein
Store delivery capacity information indicating the number of deliverable deliveries
In the delivery request input section, the
Request information, the delivery planning unit retrieves a deliverable period from the deliverable period storage unit,
Delivery period and delivery of goods from multiple destinations
The delivery deadline above depends on the delivery deadline of the request
Can be delivered to each delivery destination within the above delivery available period
A deliverable period calculation unit for determining an implementation period, and a deliverable actual value for each destination determined by the deliverable period calculation unit.
Comparing the service periods, finding duplicate delivery dates,
Delivery date indicated by the above-mentioned delivery capacity information.
To multiple destinations as long as the number of
It has a summary delivery planning section that plans delivery dates.
2. The delivery planning system according to claim 1, wherein 4. The delivery planning system further includes an article delivery system that cannot be incorporated into the delivery schedule.
Unscheduled information storage unit for storing incoming request information and readjustment of the delivery schedule planned by the delivery planning unit
Re-adjustable to remember the re-adjustable period that can be adjusted
And the re-adjustable period set by setting the re-adjustable period.
The readjustable period setting stored in the readjustable period storage
And a tough, the delivery plan section, the product can not be incorporated into the delivery schedule
Not storing product delivery request information in the unplanned information storage section
Image information output unit, and after completion of the above delivery schedule planning,
If the request information exists, 1
Search for days when there is room for the number of deliverable destinations per day
And retrieves the goods delivery request information from the unplanned information storage section.
There is room for the number of deliverable destinations retrieved and searched
Plan the delivery schedule of the above goods delivery request information on a day
3. A delivery re-planning unit according to claim 3, wherein
On-board delivery planning system. 5. The delivery request information input unit according to claim 1 , wherein
Enter collection destination information and collection request date as item collection request information.
The force, the delivery plan unit, after the planned completion of the delivery schedule, the collection request date more than
Where the delivery schedule of the above collection destination is planned
Search for a specific day and retrieve the goods collection request information on the specific day
A collection planning unit for planning a collection schedule of the collection, and the delivery planning system further includes a collection schedule.
Stores the item collection request information that cannot be incorporated into
Equipped with an empty plan recovery information storage unit that, the delivery planning unit, the article times that can not be incorporated into the collection schedule
Not storing the collection request information in the unplanned collection information storage unit
An image collection information output unit is provided.
4. The delivery planning system according to any one of 4. 6. The collection planning unit, after the collection request date
A day that does not exceed the number of deliverable destinations per day
If an error occurs, the unplanned collection information storage unit
Take out the payment request information, and
On the day that the number of destinations does not exceed
That it has a same-day collection and re-planning department
6. The delivery planning system according to claim 5, wherein: 7. The collection planning unit according to claim 1, wherein
If the delivery schedule of the goods is
If planned on the day, the unplanned collection information storage
The product collection request information is taken out, and the goods
Planning the collection schedule of the collection request information
7. A method according to claim 5, further comprising a planning unit.
A delivery planning system as described.