JP7122216B2 - Delivery planning system and delivery planning method - Google Patents

Description

TECHNICAL FIELD The present invention relates to a technique for planning a delivery plan in physical distribution.

As a background art, there is a technique of drawing up a delivery plan in physical distribution. For example, in Patent Document 1, when delivering items from multiple delivery sources to multiple delivery destinations, after unloading the delivery items at each delivery destination, other delivery items are loaded and delivered to the next delivery destination However, it is disclosed to create a delivery plan with good transportation efficiency.

JP-A-2005-112609

Patent Literature 1 describes the preparation of a delivery plan in the case of unloading delivery items at each delivery destination and then loading other delivery items and delivering them to the next delivery destination. Moreover, no consideration is given to a delivery plan that makes effective use of resources at multiple sites (for example, return flights of trucks).

SUMMARY OF THE INVENTION It is an object of the present invention to provide a delivery planning system and a delivery planning method that are capable of coping with fluctuations in packages that are not fixed until the very last minute and making effective use of resources at a plurality of bases.

In order to solve the above problems, a delivery planning system according to one aspect of the present invention includes, before delivering a package at a delivery plan creation target base, arrangements necessary for delivering a package from a departure point to a destination at each base. Using the arranged vehicle information processing unit that acquires vehicle information, the delivery plan creation target base, and the scheduled delivery date from the base, the arranged vehicle that lands at the delivery plan creation target base, A resource information processing unit that extracts resources from the acquired information of the arranged vehicle, the extracted resources, priority conditions for resources to be allocated to delivery, and order information of packages at the delivery plan creation target base. and a delivery plan creation unit that creates a delivery plan for the package at the delivery plan creation target base using a delivery plan creation system.

In addition, a delivery plan planning system according to another aspect of the present invention includes a display unit for displaying a screen, and a display unit for delivering a package from a departure point to a destination at each base before delivering the package at the delivery plan creation target base. The resource indicating the arranged vehicle that is extracted from the information on the arranged vehicle that is necessary for , and that lands at the delivery plan creation target base, indicates the resource of its own base, which is the base that is the origin. 1 resources and second resources indicating resources of bases other than the own base, and displaying the classified KPI of the first resource and the KPI of the second resource on the screen. and a control unit.

Further, in another aspect of the present invention, it can also be grasped as a delivery plan planning method performed in the above delivery plan planning system.

According to one aspect of the present invention, it is possible to deal with fluctuations in the number of packages that are not fixed until just before, and to make effective use of resources at a plurality of bases.

It is a figure which shows the structural example of a delivery plan drafting system. FIG. 5 is a diagram showing an example of arranged vehicle information; FIG. 7 is a diagram showing an example of a list of arranged vehicle information; FIG. 4 is a diagram showing an example of resource information; It is a figure which shows the example of order information. It is a figure which shows the example of the master information between bases. It is a figure which shows the example of vehicle master information. FIG. 5 is a diagram showing an example of base master information; It is a figure which shows the example of a delivery plan. It is a flow chart which shows a processing procedure of delivery plan creation processing. It is a figure which shows the example of a delivery plan preparation condition input screen. FIG. 10 is a diagram showing an example of a resource confirmation screen; FIG. 5 is a diagram showing an example of KPI information for each base; It is a figure which shows the example of delivery plan summary information. FIG. 10 is a diagram showing an example of KPI summary information; It is a subflowchart which shows the update process procedure of a data acquisition / plan situation confirmation column. It is a figure which shows the example of a delivery plan reply screen. It is a figure which shows the utilization model of the delivery plan using this system. It is a figure which shows the other utilization model of the delivery plan using this system. FIG. 10 is a diagram showing yet another utilization model of the delivery plan using this system; FIG. 10 is a diagram showing an example of a flowchart of track information collection processing; FIG. 10 is a diagram showing an example of a track information input screen; FIG. 4 is a diagram showing an example of track information;

Hereinafter, embodiments will be described in detail with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will easily understand that the specific configuration can be changed without departing from the idea or gist of the present invention.

In the configuration of the invention described below, the same reference numerals may be used in common for the same parts or parts having similar functions between different drawings, and redundant description may be omitted.

The notations such as “first”, “second”, and “third” in this specification and the like are attached to identify the constituent elements, and do not necessarily limit the number or order. Also, numbers for identifying components are used for each context, and numbers used in one context do not necessarily indicate the same configuration in other contexts. Also, it does not preclude a component identified by a certain number from having the function of a component identified by another number.

The position, size, shape, range, etc. of each configuration shown in the drawings, etc. may not represent the actual position, size, shape, range, etc., in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the positions, sizes, shapes, ranges, etc. disclosed in the drawings and the like.

Elements presented herein in the singular shall include the plural unless the context clearly dictates otherwise.

FIG. 1 is a diagram showing a configuration example of a delivery planning system 1000 in this embodiment. As shown in FIG. 1, the delivery plan drafting system 1000 has an IO (Input/Output) processing section 100, an arithmetic processing section 200, and a storage section 300. FIG. The delivery plan planning system 1000 shown below is realized by an information processing device as one aspect, but for example, the IO processing unit 100, the arithmetic processing unit 200, and the storage unit 300 may be configured by different information processing devices, and the environment may be changed. You may change a structure suitably according to.

The IO processing unit 100 is a processing unit that controls input/output of data required for this system and data processed by this system. As shown in FIG. 1 , the IO processing unit 100 has an output processing unit 101 , an input processing unit 102 , a display processing unit 103 and a communication processing unit 104 . Conventionally known apparatuses and devices may be used as hardware for each of these processing units.

The output processing unit 101 is a processing unit that outputs various results of processing performed in this system. For example, the output processing unit 101 outputs various information processed by this system, such as site-specific KPI (Key Performance Indicator) information (Fig. 13), delivery plan summary information (Fig. 14), and KPI summary information (Fig. 15). . A specific description of these pieces of information will be given later.

The input processing unit 102 is a processing unit that receives input of various information for processing in this system. For example, the input processing unit 102 receives vehicle information (FIG. 2), resource information (FIG. 4), order information (FIG. 5), various kinds of master information (inter-base master information (FIG. 6), vehicle master information (FIG. 7), , site master information (FIG. 8)), delivery plan creation conditions, and other various information processed by this system. A specific description of these pieces of information will be given later.

The display processing unit 103 is a processing unit that displays information output by the output processing unit 101 and information received by the input processing unit 102 on a display device such as a display.

The communication processing unit 104 is a processing unit that transmits/receives various kinds of information for processing in this system via the network N. FIG. For example, the communication processing unit 104 receives dispatched vehicle information (FIG. 2) and order information (FIG. 5) from each base. Next, the arithmetic processing unit 200 will be described.

As shown in FIG. 1 , the arithmetic processing unit 200 has a dispatched vehicle information aggregation processing unit 201 , a delivery plan creation processing unit 202 , a resource information aggregation processing unit 203 , and a KPI aggregation processing unit 204 .

The arranged vehicle information aggregation processing unit 201 is a processing unit that aggregates arranged vehicle information collected from each base.

The delivery plan creation processing unit 202 is a processing unit that creates a delivery plan for each base. For example, the delivery plan creation processing unit 202 creates a delivery plan using resources that arrived the day before for the next day delivery plan.

A resource is an entity (for example, a truck) that is in charge of delivering packages in physical distribution, and an example is an empty truck that is a return flight of an arranged vehicle. Although trucks are exemplified below as resources, the present invention is not limited to this, and can be applied to other vehicles and various moving bodies.

The resource information aggregation processing unit 203 is a processing unit that aggregates the resources for the scheduled delivery dates of the bases for which the delivery plan is to be created.

The KPI totalization processing unit 204 is a processing unit that divides the created delivery plan into own-site resources and other-site resources, totals KPIs, and displays the results. A specific operation of each part of the arithmetic processing unit 200 will be described later using a flowchart. Next, the storage unit 300 will be described.

As shown in FIG. 1, the storage unit 300 includes arranged vehicle information 301, arranged vehicle information list 302, resource information 303, order information 304, base-to-base master information 305, vehicle master information 306, base master Information 307 and delivery plan 308 are stored.

Arranged vehicle information 301 is information indicating an arranged vehicle table at each base. The dispatched vehicle is information related to trucks that are ordered not only at the own site but also externally (for example, a site other than the own site or an external distribution company) in order to deliver the package.

FIG. 2 is a diagram showing an example of the arranged vehicle information 301. As shown in FIG. As shown in FIG. 2, the arranged vehicle information 301 includes a starting point indicating the origin of the truck, a destination indicating the landing of the truck, a vehicle class of the truck, the number of arranged trucks, and the date of departure of the truck. , and the arrival date of the truck are stored in association with each other. FIG. 2 shows, for example, that a large-sized truck with a destination of B, a departure date of July 2nd, and an arrival date of July 3rd is arranged at A site. Similarly, a medium-duty truck with a destination of C, a departure date of July 2, and an arrival date of July 3 is arranged. This indicates that one small truck will be arranged for the 3rd day of the month.

The arranged vehicle information list 302 is information in which the arranged vehicle information 301 of each base is summarized in a list format.

FIG. 3 is a diagram showing an example of the ordered vehicle information list 302. As shown in FIG. As shown in FIG. 3, the ordered vehicle information list 302 stores each item stored in the arranged vehicle information 301 as well as affiliation information indicating the owner of the truck. In FIG. 3, for example, in FIG. 2, the truck with destination B, the truck with destination C, and the truck with destination X are all owned by base A. . As for the base C, the arranged vehicle information 301 and the affiliation are stored in the same way as the base A, and are summarized as one list.

The resource information 303 is information obtained by summarizing the resources (for example, trucks) on the scheduled date used for delivery to the base (for example, B base) for which the delivery plan is created.

FIG. 4 is a diagram showing an example of the resource information 303. As shown in FIG. As shown in FIG. 3, the resource information 303 stores the date indicating the scheduled date for delivery, the affiliation of the resource, the vehicle class of the resource, and the number of resources in association with each other. In FIG. 4, for example, there is a vacancy on July 4, which is the scheduled delivery date (that is, the arrival date is before July 3), and the destination is location B, which is the target of the creation of the delivery plan. It shows that the vehicle 3021 and the arranged vehicle 3022 are extracted from the arranged vehicle information list 302 . Furthermore, FIG. 4 shows that the arranged vehicle information of base B, which is its own base, has two large-sized resources, so it is stored together with the extracted information as resource information.

The order information 304 is information indicating when, from where, to where, how much, and by when a package is to be delivered.

FIG. 5 is a diagram showing an example of the order information 304. As shown in FIG. As shown in FIG. 5, the order information 304 stores the starting point indicating the origin of the package, the destination indicating the destination of the package, the quantity of the package, and the delivery date of the package in association with each other. For example, FIG. 5 shows that an order has been placed to transport a 10-ton package to destination A by July 5, starting from base B, which is the object of creating a delivery plan. Similarly, it shows that an order has been placed to carry a 5-ton package to destination C by July 5th, and an order to carry a 10-ton package to destination X by July 6th.

The base-to-base master information 305 is master information related to the cost for transporting packages between bases.

FIG. 6 is a diagram showing an example of inter-base master information 305. As shown in FIG. As shown in FIG. 6, the base-to-base master information 305 includes an origin indicating a base that is the starting point of a parcel, a destination that indicates the destination of the parcel's arrival, a distance between these bases, It is stored in association with the time required to travel the distance between these bases. FIG. 6 shows that, for example, the distance between A site and B site is 100 km, and it takes four hours to move. In FIG. 6, distance and time are illustrated as examples of costs, but necessary expenses (for example, fuel costs for trucks) may also be included.

The vehicle master information 306 is master information regarding specifications of resources belonging to each base.

FIG. 7 is a diagram showing an example of the vehicle master information 306. As shown in FIG. As shown in FIG. 7, the vehicle master information 306 stores truck class, truck delivery capacity, and truck cost (distance unit price) in association with each other. For example, FIG. 7 shows that, for base A, the maximum load capacity of a truck classified as "large" is 10 tons, and the distance unit price is 1200 yen. Figure 7 shows truck delivery capacity as an example of capacity. It is also possible to use

The base master information 307 is information about bases that receive parcels.

FIG. 8 is a diagram showing an example of the site master information 307. As shown in FIG. As shown in FIG. 8, the base master information 307 stores bases in association with the number of truck berths at the base. FIG. 8 shows that, for example, the A site has five truck berths. In FIG. 8, the number of truck berths is exemplified as the information related to the base, but it may also include the time period during which goods can be received. In this case, it can be determined that the longer the available parcel-receivable time zone is, the larger the total amount of parcels that can be accepted.

The delivery plan 308 is information indicating a package delivery plan at a base for which a delivery plan is created.

FIG. 9 is a diagram showing an example of the delivery plan 308. As shown in FIG. As shown in FIG. 9, the delivery plan 308 includes a starting point indicating a location for which the delivery plan is to be created, a departure time indicating the time at which the truck departs from the starting point, a destination indicating the arrival of the cargo, and the destination of the truck. The arrival time indicating the time of arrival at the destination and the cargo amount indicating the amount of cargo delivered by the truck are stored in association with each other.

For example, FIG. 9 shows that a "large" truck that departs from base B at 14:00 is loaded with 10 tons of cargo and is scheduled to arrive at base A at 18:00. The departure time and arrival time in FIG. 9 may be set by the delivery plan creation processing unit 202, for example, by storing the opening time and closing time of each base in the base master 307 and referring to them as necessary. If a base opens at 10:00 a.m. and closes at 10:00 p.m., the departure time is set to the opening time of 10:00 a.m. (or the arrival time is set to 10:00 p.m., which is the closing time). Departure time and arrival time may be set by referring to inter-base master 305 (FIG. 6). Furthermore, if the arranged vehicle information includes the departure date and arrival date as well as the departure time and arrival time, refer to these times and the base-to-base master 305 (FIG. 6) to set the departure time and arrival time. You may Next, processing performed in this system will be described.

FIG. 10 is a flow chart showing the processing procedure of the delivery plan creation processing performed in this system. Although the case where the delivery plan for base B is planned is described below, other bases can be considered in the same way. In other words, each step (S1002 to S1007) shown below may be repeated for all bases for which a delivery plan is to be created.

As shown in FIG. 10, first, the arranged vehicle information aggregation processing unit 201 aggregates arranged vehicle information collected from each base (step S1001).

Specifically, the arranged vehicle information aggregation processing unit 201 receives the arranged vehicle information 301 (FIG. 2) up to July 3 from the A base, which is one of the bases. Similarly, the arranged vehicle information aggregation processing unit 201 receives arranged vehicle information from all other bases. The arranged vehicle information aggregation processing unit 201 refers to the vehicle master information 306 of all bases, and creates an arranged vehicle information list 302 (Fig. 3 ).

In the following description, the arranged vehicle information aggregation processing unit 201 receives the arranged vehicle information for the day before the delivery plan is created for base B, and outputs the delivery plan for the next day, July 4. As an example, the date and time to be the target of the arranged vehicle information is received for a predetermined period (for example, the arranged vehicle information for the period from the day before the delivery plan to one week before), and the arranged vehicle information for the predetermined period is received. may be aggregated.

In the following description, the arranged vehicle information aggregation processing unit 201 receives the arranged vehicle information from each base at a certain point in time. unit), and may be updated to the latest arranged vehicle information each time it is received. That is, the arranged vehicle information aggregation processing unit 201 acquires the latest arranged vehicle information from each base at a predetermined cycle, and updates the acquired arranged vehicle information. By performing such processing, even if the arranged vehicle information determined at a certain timing is changed afterward, the latest arranged vehicle information can always be used to aggregate the arranged vehicle information of each base.

Subsequently, the delivery plan creation processing unit 202 creates a delivery plan using the trucks that arrived at each base on the previous day for the next day delivery plan (step S1002).

Specifically, the delivery plan creation processing unit 202 displays a condition input screen for accepting input of delivery plan creation conditions via the display processing unit 103, and inputs the conditions via the input processing unit 102. accept.

FIG. 11 is a diagram showing an example of a condition input screen. As shown in FIG. 11, a condition input screen 1101 includes a departure point 1102 for which a delivery plan is to be created, a package delivery date 1103, and when assigning trucks, priority is given to the number of trucks belonging to the own point. a priority condition radio button 1104 (first priority condition) for creating a delivery plan, or a priority condition radio button for creating a delivery plan by prioritizing the efficiency of the delivery cost of resources at each base for which the delivery plan is to be created. 1105 (second priority condition), a priority condition indicating a condition to be prioritized when formulating a delivery plan, a resource confirmation button 1106 for summarizing resources and confirming the result, and a delivery plan for the origin base. A delivery plan creation button 1107 is provided for creating a delivery plan. The first priority condition is a condition that prioritizes the resource utilization efficiency of the own base, which is the origin base (target base for delivery plan creation), and the second priority condition is a target for delivery plan creation. It can be said that this is a condition for creating a delivery plan with priority given to the efficiency of delivery costs between each base.

FIG. 11 shows an example in which a delivery plan is created with priority given to the total number of resources at all bases for resources departing from base B on July 4, for example. In this way, by making it possible to set priority conditions on the condition input screen, users of this system can set resource delivery plans, including trucks at their own base and trucks at other bases, according to these conditions. can do. Here, it is possible to set one of giving priority to own site resources and giving priority to delivery costs, but it is also possible to set the importance of delivery content such as giving priority to delivery quality. This point will be described in the explanation of FIGS.

Next, returning to FIG. 10, when the resource confirmation button 1106 is pressed on the condition input screen 1101, the resource information totalization processing unit 203 totalizes the resources for the scheduled delivery date of the base (step S1003).

Specifically, the resource information aggregation processing unit 203 extracts trucks whose destination is the base B for which the delivery plan is to be created from the arranged vehicle information list 302 shown in FIG. 4) is stored as FIG. 4 shows that two trucks whose destination is the B point shown in FIG. 3 are extracted. Furthermore, FIG. 4 shows that two trucks have been extracted from the own site.

Then, the resource information aggregation processing unit 203 classifies and aggregates the resource information 303 stored in the storage unit 300 for each of its own site and other sites, and displays the result as resource confirmation information on the screen via the display processing unit 103. to display. That is, the resource information aggregation processing unit 203 divides the resources extracted from the list into resources of its own base, which is the origin base (distribution plan creation target base), and resources of other bases, which are bases other than its own base. are aggregated, and resource confirmation information indicating the aggregated result is output to the screen.

FIG. 12 is a diagram showing an example of a resource confirmation screen displaying resource confirmation information. As shown in FIG. 12, the resource confirmation screen 1201 is provided with the originating base 1202, the delivery date 1203, the own base resource information 1204, the other base resource information 1205, and a return button 1206. there is In FIG. 12, the trucks that can depart from base B on July 4 include two “large” trucks at base B, which is its own base, and two “large” trucks at base A, which is another base. , and another base, C base, has one truck with a vehicle class of "medium." When the return button 1206 is pressed, the resource information aggregation processing unit 203 causes the display processing unit 103 to transition to the condition input screen shown in FIG.

As described above, the arranged vehicle information collected from each base may be updated at a predetermined timing. In this case, the resource information aggregation processing unit 203 may aggregate resource information using the updated arranged vehicle information each time it receives updated arranged vehicle information.

Returning to FIG. 10, when the resource information is aggregated, the delivery plan creation processing unit 202 acquires the order information of the bases for which the delivery plan is created (step S1004).

Specifically, the delivery plan creation processing unit 202 reads the order information ( FIG. 5 ) of base B input or received via the input processing unit 102 or the communication processing unit 104 .

Furthermore, the delivery plan creation processing unit 202 reads out inter-base master information 305 (FIG. 6), vehicle master information 306 (FIG. 7), and base master information 307 (FIG. 8) stored in the storage unit 300 (step S1005). ).

The delivery plan creation processing unit 202 uses the resource information aggregated in step S1003, the order information acquired in step S1004, and the various master information acquired in step S1005 to create a delivery plan for base B (Fig. 9 ), the results are output as site-specific KPI information, and displayed via the display processing unit 103 (steps S1006 and S1007). Various conventionally known methods may be used with reference to various indices such as physical distribution KPIs for specific KPI calculations and delivery plan planning methods.

FIG. 13 is a diagram showing an example of KPI information for each site indicating a KPI of a delivery plan creation target site (single site) and a delivery plan. As shown in FIG. 13, a planned delivery plan 1301 includes the originating base 1302, the shipping date 1303, the truck usage status 1304 at the own base, the truck usage status 1305 at other bases, and the planned delivery plan. 1306 (FIG. 9). The truck usage status 1304 of the own base includes the number of operable trucks, the number of scheduled operable trucks, and the operating rate of the own base. .

In FIG. 13, for example, the delivery plan creation processing unit 202 assumes that base B, which is the target of delivery plan creation, is a truck that can depart on July 4, and three of the six resources of base B, which is its own base, are used. Indicates that the truck has been assigned to a dispatch plan. It also shows that the operating rate of the truck at the B site is calculated and the value is 50%. Furthermore, it is shown that 3 trucks out of the 6 resources of the other bases are assigned to the delivery plan, assuming that the B base is a truck that can depart on July 4th. In addition, the average loading rate of the trucks of other bases is calculated, and the value is shown to be 50%.

The screen shown in FIG. 13 has a display unit such as a display for displaying the screen, for example, and the display processing unit 103 controls the delivery of the package from the origin to the destination at each base before the package is delivered to the base for creating the delivery plan. For the resource that indicates the arranged vehicle that is extracted from the arranged vehicle information required to deliver to and that lands at the base for which the delivery plan is created, KPI of the first resource and the KPI of the second resource are classified into a first resource indicating the resource of the own base (base) and a second resource indicating the resource of the base other than the base. can be realized by functioning as a display control unit for displaying on the screen.

In this way, even if the timing for creating a delivery plan for a certain base is just before the delivery date, this system will be able to collect resource information obtained from dispatched vehicle information collected up to that point and from other bases. Then, by using the order information of the base and various master information, it is possible to create a delivery plan for the base in consideration of not only the resources of the own base but also the resources of other bases. Although it will be described later in detail, the arranged vehicle information 301 includes information indicating the affiliation of the resource, and the KPI aggregation processing unit 204 identifies the extracted resource as a base (delivery plan creation target base) that is the origin of the package. ) and other bases that are bases other than the own base, the resource KPIs are aggregated.

Next, returning to FIG. 10, when the delivery plan creation processing unit 202 creates the delivery plans for all delivery plan creation target bases, the KPI aggregation processing unit 204 calculates the delivery schedule for each base including its own base and other bases. The plan summary information is output and displayed via the display processing unit 103 (S1008).

FIG. 14 is a diagram showing an example of delivery plan summary information output by the KPI aggregation processing unit 204. As shown in FIG. As shown in FIG. 14 , the delivery plan summary information 1401 includes a data acquisition/plan status confirmation column 1402 and a delivery plan summary column 1403 .

The data acquisition/plan status confirmation column 1402 is an item for confirming the drafting status of the delivery plan. As shown in FIG. 14, the data acquisition/plan status confirmation field 1402 includes a delivery plan item indicating whether or not the delivery plans for all bases to be created for delivery plan creation have been sent to each base, and A reply item indicating whether or not there is a reply to the request and a requested vehicle information item indicating whether or not the requested vehicle information has been received from each of these bases are associated with each other. For example, FIG. 14 shows that the created delivery plan has already been sent to site A, and a response (OK) has been obtained from site A to the effect that the created delivery plan is acceptable. Also, it indicates that the requested vehicle information has been received from the A site. A specific update method for the data acquisition/plan status confirmation column 1402 will be described later using a sub-flowchart.

In this way, the KPI aggregation processing unit 204, as the summary information of the delivery plan, for all bases for which the delivery plan is created displays the status of responses regarding the validity of the sent delivery plan, so the user of this system can grasp the drafting status of the delivery plan at a glance.

The delivery plan summary column 1403 is an item for confirming the details of the trucks assigned according to the delivery plan created for all bases for which the delivery plan is to be created. As shown in FIG. 14, the delivery plan summary column 1403 displays the breakdown of trucks allocated for inter-base delivery (local-base trucks and other-base trucks) for all bases for which a delivery plan is to be created. . For example, in a delivery R1 originating at the A site and ending at the B site, it is indicated that one truck is assigned to the own site. In addition, for delivery R2 originating at A site and arriving at E site, it is shown that one truck from another site has been allocated. Various display methods, such as different colors and different numerical values, may be used to indicate whether the track is the home base track or the other base track.

In this way, the KPI aggregation processing unit 204 displays, as the summary information of the delivery plan, the details of the trucks used for delivery between all the bases for which the delivery plan is created, including the own base and other bases. System users can grasp the breakdown of trucks used in the delivery plan at a glance. That is, the delivery plan creation processing unit 202 creates a delivery plan for each base, and the KPI aggregation processing unit 204 determines whether the resource assigned to the created delivery plan is the own base or another base. Since the breakdown shown is output for each site, the breakdown can be easily grasped.

Although the number of assigned trucks is displayed in FIG. 14, the KPI aggregation processing unit 204 may further display the breakdown of the number of trucks. For example, in FIG. 14, two trucks from other bases are assigned to delivery R3, which originates from base B and ends at base A. The details of these are displayed together with the delivery plan summary column 1403 or on another screen. , it may be displayed as "1 unit: site B, 1 unit: site C". This makes it possible to easily grasp the breakdown of resources at other bases.

Furthermore, in step S1008, the KPI aggregation processing unit 204 outputs usage status summary information 1501 indicating resource usage statuses for all bases targeted for delivery plan creation separately for the own base and other bases, and the display processing unit 103 view through.

FIG. 15 is a diagram showing an example of KPI summary information. As shown in FIG. 15, the KPI summary information 1501 includes the truck usage status 1502 of the own base for all the bases for which the delivery plan is created, and the truck usage status of other bases for all the bases for which the delivery plan is created. It includes usage status 1503 and empty vehicle information 1504 of trucks at other bases for all bases for which delivery plans are created.

In FIG. 15, for example, the KPI aggregation processing unit 204 determines that there are N1 trucks that can depart from all of the self-bases targeted for delivery plan creation at a certain time (for example, July 4), and N2 trucks of the self-base. Indicates that the truck has been assigned to a dispatch plan. In addition, the KPI aggregation processing unit 204 calculates the operating rate of the trucks at each site, and indicates that the value is 50%, and the average loading rate of the trucks at the own site assigned to the delivery plan is 50%. ing.

Furthermore, for example, on July 4th, there are N3 trucks that can depart from all the other bases for which the delivery plan is to be created, and among them, there are N4 empty trucks. Also, the KPI aggregation processing unit 204 calculates the average loading rate of the trucks at other bases assigned to the delivery plan, and indicates that the value is 50%. Furthermore, the KPI aggregation processing unit 204 determines, as empty vehicle information of other bases, the empty rate of trucks at all other bases for which delivery plans are created, that is, the ratio of the number of empty trucks to the number of operable trucks at other bases is 50%. indicates that there is The empty vehicle rate may be calculated as the number of trucks not assigned to the delivery plan among the trucks at other bases.

In this way, the delivery plans for all bases for which delivery plans are created are aggregated, and for each base, the usage status of trucks at its own base and other bases is output and displayed. It is possible to grasp at a glance the usage status of the trucks allocated in the plan and information on the availability of trucks at other bases. In addition, in FIG. 15, the vacant car information of other bases is displayed, but the vacant car information of the own base may be displayed. With such a display, it is possible to grasp the ratio of the number of unloaded trucks at other bases (or trucks at the own base) at a glance.

In addition, the user of this system can check the truck usage status 1502 of his own base and the truck usage status 1503 of other bases, and adjust the delivery plan in consideration of the overall balance. For example, the higher the operating rate of trucks originating from your own base, the more efficiently you can process the trucks at your base. Dispatch plans can be created that allocate more trucks. Also, for example, a truck originating from another base is a return truck (return trip), and the return trip charge for round-trip delivery is usually cheaper than the one-way charge. Lower cost for the return trip. Therefore, the user of this system can formulate a delivery plan with low cost as a whole. Therefore, if the delivery cost is higher than the assumed value, a delivery plan can be created that allocates more trucks from other bases. As for the empty rate, it is possible to check at a glance how much trucks at other bases are being used, so it is possible to provide judgment materials for considering the number of trucks allocated at other bases. Next, a specific update method for the data acquisition/plan status confirmation field 1402 will be described.

FIG. 16 is a sub-flowchart showing a specific processing procedure for updating the data acquisition/plan status confirmation column 1402 . Since each process of steps S1001 to S1008 in FIG. 16 is the same as that shown in FIG. 10, description thereof will be omitted here, and steps S1601 to S1604 will be described.

As shown in FIG. 16, in step S1007, when the delivery plan creation processing unit 202 outputs the delivery plan for a single base, it determines whether the delivery plan is appropriate for the output delivery plan (FIG. 9). (OK or NG) is added as a delivery plan proposal to the site (for example, B site) that is the target of delivery plan creation. (Step S1601). For example, a computer such as a PC (Personal Computer) used by a person in charge of collecting the arranged vehicle information is provided at the base, and is connected to the delivery planning system 1000 via a network N.

When the computer at the site targeted for delivery plan creation receives the proposed delivery plan for its own site from the delivery plan drafting system 1000, it displays a delivery plan response screen including the proposed delivery plan on the display connected to the computer. (Step S1602).

FIG. 17 is a diagram showing an example of a delivery plan reply screen displayed on the display. As shown in FIG. 17, on a delivery plan response screen 1701, a delivery plan 308 and 1306 created by the delivery plan creation processing unit 202 and a message indicating that the created delivery plan is appropriate (OK) are entered. It includes an answer column 1702 and an answer send button 1703 for sending the answer result to the delivery plan drafting system 1000 .

The input device connected to the computer of the base where the delivery plan is to be created accepts input from the person in charge at the base to check whether each of the delivery plans presented as the draft delivery plan is valid (step S1603). ). FIG. 17 shows that all the delivery plans shown as delivery plan proposals have been checked as valid.

When the input device receives the push of the response transmission button 1703 from the person in charge, the computer at the site for which the delivery plan is to be created receives the delivery plan draft in which the reply about the validity is input as the response result, and sends it to the delivery plan drafting system. 1000 (step S1604). After that, the process advances to step S1008, and the delivery plan creation processing unit 202 outputs the KPI summary information 1501. FIG.

In FIG. 17, an answer column 1702 is an item for inputting that the delivery plan is appropriate (OK). The explanation is based on the premise that it is not valid (NG) if it is not. However, as for the reply method, both of these input fields may be provided, and a field for inputting the reason for the reply may be provided. As a result, the user of this system can grasp the reason for the response from the base side.

Further, in the above description, it is assumed that the processes of steps S1601 to S1604 are executed in parallel with the execution of the process of step S1007. However, at this point, the sub-flow processing does not necessarily have to be completed for all bases. The delivery plan summary information 1401 reflecting the reply may be output.

FIG. 18 is a diagram showing a utilization model of a delivery plan using this system. In FIG. 18, the user of the delivery plan planning system 1000 starts executing the processing of the flowchart shown in FIG. It acquires the arranged vehicle information 301 and the order information 304 from , and transmits the delivery plan (FIG. 9) created for each base to each base. As shown in the subflow, the person in charge at each base operates the computer 1801 to give an answer indicating whether or not the proposed delivery plan is appropriate, and the result is fed back to the delivery plan drafting system 1000. . The user of this system confirms the responses from each site, and when receiving an answer that is not valid, executes the processing of FIG. 10 again for the site and recreates the delivery plan. When all answers are obtained, the KPI aggregation processing unit 204 outputs delivery plan summary information (FIG. 14) and KPI summary information (FIG. 15).

In the examples so far, the case where the delivery plan planning system 1000 provides a centralized center for supervising the delivery plans of each base, and the centralized center creates and transmits a delivery plan to each base has been described. However, each base may independently create a delivery plan in consideration of the resources of other bases without providing a centralized center.

FIG. 19 is a diagram showing another utilization model of the delivery plan using this system. FIG. 19 shows a model in which each base independently creates a delivery plan in consideration of the resources of other bases. For example, at site B, a computer equipped with the delivery planning system 1000 executes the process of FIG. ). In this case, the delivery plan summary information (FIG. 14) and KPI summary information (FIG. 15) do not necessarily have to be aggregated or output.

As yet another example, this system may be applied to a general business operator that supervises distribution companies.

FIG. 20 is a diagram showing still another utilization model of the delivery plan using this system. In FIG. 20, instead of each base, the computer of each distributor and this system are connected by a network N, and the distribution control company that controls the distributors makes a delivery plan. In the case of such a configuration, in FIG. 18, the base should be read as the distributor, and the general center as the center of the general distribution company. In this case, the base includes the distributor.

In the model shown in FIG. 20, a computer provided at the center of the general distribution company may collect track information of each distribution company. The collection of track information may be performed before the process of step S1003 in FIG. The truck information is information indicating specifications and the number of trucks belonging to the distributor.

FIG. 21 is an example of a flowchart of track information collection processing. As shown in FIG. 21, the computer 1801 of each distributor first displays a truck information input screen for registering truck information on the display connected to the computer (step S2101).

FIG. 22 is a diagram showing an example of a track information input screen. As shown in FIG. 22, a truck information input screen 2201 has a company name 2202 indicating a distributor, a truck information input field 2203, and a registration button 2204 for transmitting the input truck information to the delivery plan planning system 1000. include. In FIG. 22, for example, truck company A, which is a logistics company, owns three 5-ton trucks as its own resources, and the unit price for using them is X1 yen. .

The computer 1801 of each distributor transmits the input truck information to the delivery planning system 1000 via the network N when the registration button 2204 on the truck information input screen is pressed. Then, the resource information aggregation processing section 203 of the delivery plan drafting system 1000 registers the track information received from the computer 1801 in the storage section 300 (step S2102).

FIG. 23 is a diagram showing an example of track information registered in the storage unit 300. As shown in FIG. As shown in FIG. 23, truck information 2301 is similar to the truck information input in FIG. remembered. The track information entered in FIGS. 21 and 22 may be included in the vehicle master information 306 shown in FIG. In FIGS. 21 and 22, the distance unit price is shown as a single numerical value on the premise of a round-trip flight. For example, in FIG. 23, the logistics company A has three 10-ton trucks, and the unit price per distance is 1200 yen. The unit price for the round trip may be stored as shown in FIG. In this case, the user of this system can create a delivery plan that considers costs for each of the outbound and return trips.

Furthermore, in FIGS. 21 and 22, track specifications are input as track information, but track quality may be stored as the specifications. For example, as the truck quality, if the truck has specifications with "air suspension", the quality "high" may be stored. Furthermore, information indicating the evaluation of the truck by the distributor may be input. For example, if a truck has had a delivery accident in the last year, the information indicating the evaluation of the truck (e.g., "low", "medium", "high") is entered and the distance unit price is entered. can be reflected in Such information can be input by operating the computer 1801 of each distributor by the person in charge of the distributor.

Furthermore, on the condition input screen shown in FIG. 11, the above quality may be input as a priority condition (third priority condition) indicating a condition that should be prioritized when formulating a delivery plan. Since it is possible to set delivery quality as a priority condition, it is possible to formulate a delivery plan that takes quality into consideration, for example, when delivering packages that require careful handling, such as artworks such as paintings and pottery, and antiques. Become.

As described above, in this system, the arranged vehicle information aggregation processing unit 201 collects the arranged vehicle information 301 necessary for delivering the package from the point of departure to the destination at each base before the package is delivered to the target base for creating the delivery plan. The resource information aggregation processing unit 203 uses the delivery plan creation target base and the scheduled delivery date starting from the base to determine the arranged vehicle that lands at the delivery plan creation target base according to the acquired arrangement. The resource information 303 is extracted from the vehicle information 301, and the delivery plan creation unit 202 creates The information 304 is used to create a package delivery plan at the base for which the delivery plan is to be created, so it is possible to deal with fluctuations in packages that are not fixed until just before and to effectively utilize the resources of a plurality of bases. In other words, for a plurality of packages to be delivered, it is possible to create a delivery plan that optimizes the origin, destination, and transport volume for vehicles at a plurality of bases.

Conventionally, a dispatcher, who is in charge of a base (for example, base B) that is the target of delivery planning, sends the delivery schedule of a package from base A, which is the origin, to base B, which is the destination, just before departure. informed in time. Even if the schedule of the base A can be obtained, it is based on the assumption that there is a human relationship between the dispatchers. Also, conventionally, the resources (cars, etc.) of each base are managed separately for each base. Therefore, it is not assumed to be used on the return trip. Therefore, even though there are packages to be delivered from base B to base A the next day, the truck that arrived the day before must return empty. was not limited. In addition, at base B, which is the destination, the resources of base B are preferentially used in order to increase the utilization rate of the own base vehicle. There was a need to make effective use of it.

By executing the processes described above, this system solves these problems, makes effective use of the resources of each base (for example, improves return trips and truck loading ratios), and reduces the man-hours required for formulating delivery plans. can be realized.

The computer used in the delivery planning system 1000 includes general hardware such as a storage device such as memory and HDD (Hard Disk Drive), and a CPU (Central Processing Unit) that controls each part of the system and executes arithmetic processing. Each of the above processes is realized by the CPU reading the program from the memory and executing it. The program is pre-installed in a ROM or the like, or is a computer-readable recording medium such as a CD-ROM, a CD-R, or a DVD (Digital Versatile Disk) as a file in an installable format or an executable format. may be recorded and provided or distributed. Furthermore, the program may be stored on a computer connected to a network such as the Internet, and provided or distributed by being downloaded via the network.

The present invention is not limited to the above embodiments, includes various modifications, and is not necessarily limited to having all the configurations described. Also, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or add, delete, or replace a part of the configuration of each embodiment with another configuration.

1000 Delivery plan drafting system 100 IO (Input/Output) processing unit 200 Arithmetic processing unit 300 Storage unit 101 Output processing unit 102 Input processing unit 103 Display processing unit 104 Communication processing unit 201 Arranged vehicle information aggregation processing unit 202 Delivery plan creation processing unit 203 Resource information aggregation processing unit 204 KPI aggregation processing unit 301 Arranged vehicle information 302 Arranged vehicle information list 303 Resource information 304 Order information 305 Inter-base master information 306 Vehicle master information 307 Base master information 308 Delivery plan N Network.

Claims (7)

a dispatched vehicle information processing unit that acquires information on a dispatched vehicle necessary for delivering a package from the point of departure to the destination at each site before the package is delivered to the delivery plan creation target site;
Using the delivery plan creation target base and the scheduled delivery date originating from the base, an arranged vehicle having a destination at the delivery plan creation target base is selected as a resource from the acquired information of the arranged vehicle. a resource information processing unit to extract;
A delivery plan creating unit that creates a package delivery plan at the delivery plan creation target base using the extracted resources, the priority conditions of the resources to be assigned to the delivery, and the order information of the packages at the delivery plan creation target base. and
The information on the ordered vehicle includes information indicating the affiliation of the resource,
For each of the own base, which is the origin base, and the other base, which is the base other than the own base, at least inter-base master information related to the cost for transporting packages between bases and belonging to each base a KPI aggregation unit that aggregates the KPI of the resource by calculating the usage status of the resource planned in the delivery plan using the vehicle master information indicating the cost related to the resource to be used;
A delivery planning system characterized by comprising: The delivery plan creation unit creates the delivery plan for each base,
The KPI aggregation unit outputs, for each base, a breakdown indicating whether the resource allocated to the created delivery plan is the own base or the other base.
2. The delivery planning system according to claim 1, characterized by: The delivery plan creation unit has a first priority condition for prioritizing resource usage efficiency of the self-site, which is the site of origin, and priority is given to efficiency of delivery cost between each site for which the delivery plan is created. a second priority condition for creating a delivery plan by using any of the priority conditions to create a delivery plan for the package;
2. The delivery planning system according to claim 1, characterized by: The arranged vehicle information processing unit acquires the latest information on the arranged vehicle from each base in a predetermined cycle, and updates the acquired information on the arranged vehicle.
2. The delivery planning system according to claim 1, characterized by: The resource information processing unit aggregates the resources of the own base, which is the originating base, and the resources of other bases, which are bases other than the own base, for the extracted resources, and indicates the result of the totalization. print resource confirmation information to the screen,
2. The delivery planning system according to claim 1, characterized by: a display unit for displaying a screen;
Prior to the delivery of the package at the delivery plan creation target base, the arranged vehicle extracted from the information of the arranged vehicle necessary for delivering the package from the departure place to the destination at each base, and the delivery plan creation target base. The resources indicating the arranged vehicle to be landed are classified into a first resource indicating the resources of the own base, which is the originating base, and a second resource indicating the resources of bases other than the own base. a display control unit for displaying on the screen the KPI of the first resource and the KPI of the second resource,
The information on the ordered vehicle includes information indicating the affiliation of the resource,
For each of the own base, which is the origin base, and the other base, which is the base other than the own base, at least inter-base master information related to the cost for transporting packages between bases and belonging to each base A KPI aggregation unit that aggregates the KPI of the resource by calculating the usage status of the resource planned in the package delivery plan at the delivery plan creation target base using the vehicle master information indicating the cost related to the resource to be used. has
The display control unit displays the KPI of the first resource and the KPI of the second resource aggregated by the KPI aggregation unit on the screen.
A delivery planning system characterized by: The arranged vehicle information processing unit obtains, before delivering the package at the delivery plan creation target base, information on the arranged vehicle necessary for delivering the package from the departure place to the destination at each base and landing at the delivery plan creation target base. Acquire the information of the arranged vehicle including the information indicating the affiliation of the resource indicating the arranged vehicle,
The resource information processing unit uses the delivery plan creation target base and the scheduled delivery date from the base to determine the arranged vehicle that lands at the delivery plan creation target base based on the obtained arranged vehicle. Extracting resources from information,
A delivery plan creation unit creates a delivery plan for a parcel at the delivery plan creation target base using the extracted resources, priority conditions for resources to be allocated to delivery, and parcel order information at the delivery plan creation target base. When creating
The KPI aggregation unit obtains inter-base master information about at least the cost for transporting packages between bases, for each of the own base, which is the origin base, and other bases, which are bases other than the own base. , summarizing KPI of the resource by calculating the usage status of the resource planned in the delivery plan using vehicle master information indicating the cost of the resource belonging to each base;
A delivery planning method characterized by:

Images