Delivery service usage adjustment system and method

Abstract

To allow for adjusting a utilization method of a delivery service as necessary between a service provider and a service receiver.SOLUTION: A delivery service utilization method adjustment system 4 comprises: a first computer 1 for use in a service receiver 100 to which a delivery service is provided; and a second computer 2 which is connected to the first computer via a communication network CN and is used in a service provider 200 providing the delivery service. If it is predicted that a scheduled delivery date at which an article to be delivered should be delivered to the delivery service will be later than a reference date written in reference rate sheet data, new rate sheet data which allows the scheduled delivery date to be changed is selected.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a system and method for adjusting the method of using a delivery service.

Background Art

[0002] For example, in order to send products from a factory that manufactures products such as cars, construction machines, trains, and industrial machines to various places, transportation means such as trucks, railways, and ships are used. Although airplanes may be used in some cases, they are generally not used for transporting heavy goods.

[0003] Generally, large-scale transportation by ship is carried out at relatively long intervals, such as once every 10 days or once a week, and the departure time cannot be flexible. On the other hand, small-scale and medium-scale transportation by truck is carried out at relatively short intervals, such as once a day. Furthermore, in truck transportation, by paying an additional fee, it is possible to cope with a certain degree of shipping delay, such as several tens of minutes to several hours.

[0004] Here, in the case of large-sized products having a relatively complex structure, such as cars, control panels, power generation equipment, construction machines, trains, and industrial machines, the production schedule may change due to various circumstances, and the shipping preparation may be delayed. Even if the shipping of the product does not meet the truck regular service, it may be in time for the ship's departure. When arranging a truck other than the regular service truck, the required transportation fee increases.

[0005] Patent Document 1 discloses a technique where "a delivery time determination unit determines the delivery time for each piece of luggage, and a delivery fee calculation unit refers to delivery fee data storing the discount rate of the delivery fee corresponding to the delivery time for delivering the luggage, and calculates the delivery fee for each piece of luggage based on the delivery time for delivering each piece of luggage determined by the delivery time determination unit."

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

[0007] Conventional technologies do not link the factory's production management system with the delivery company's delivery planning system. As a result, there is a problem in that it is not possible to efficiently conclude reasonable contracts between the factory and the delivery company in response to delays in product preparation for shipment.

[0008] Therefore, the purpose of this disclosure is to provide a delivery service usage adjustment system and method that enables service providers and service recipients to adjust the method of using delivery services as needed. [Means for solving the problem]

[0009] To solve the above problems, a delivery service usage method adjustment system according to one aspect of the present invention is a delivery service usage method adjustment system that adjusts the usage method of a delivery service that delivers requested goods to a designated location, comprising: a first computer used by a service provider to which the delivery service is provided; and a second computer used by a service provider that provides the delivery service and is connected to the first computer via a communication network, wherein the first computer comprises one or more first processors, one or more first memories and a first communication unit; the second computer comprises one or more second processors, one or more second memories and a second communication unit; and the first processor is responsible for handing over the goods to be delivered to the delivery service. If the scheduled delivery date and time is predicted to be later than the reference date and time stated in the reference price list data set with the second computer, the first communication unit requests the second computer to send new price list data that allows for variation in the scheduled delivery date and time. When the second communication unit receives the request from the first computer, the second processor generates new price list data that includes one or more variation ranges that allow for variation in the scheduled delivery date and time, and the charges for each variation range. The generated new price list data is stored in the second memory and transmitted to the first computer. The first processor then compares the new price list data received from the second computer with predetermined conditions stored in the first memory to determine whether or not to adopt the new price list data. [Effects of the Invention]

[0010] According to the present invention, the method of using the delivery service can be adjusted between the service provider and the service recipient as needed. [Brief explanation of the drawing]

[0011] [Figure 1] An overall diagram of the delivery service usage adjustment system in this embodiment. [Figure 2] Functional configuration diagram of the delivery service usage method adjustment system. [Figure 3] An example of a production planning table. [Figure 4] Example of production performance table. [Figure 5] Example of delivery contract table. [Figure 6] Example of production prediction table. [Figure 7] Example of delivery fee table. [Figure 8] Example of delivery plan table. [Figure 9] Example of delivery performance table. [Figure 10] Example of delivery contract table. [Figure 11] Example of delivery fee table. [Figure 12] Flowchart showing the processing in the production planning system. [Figure 13] Flowchart showing the processing in the delivery planning system. [Figure 14] Flowchart showing the processing for setting a delivery contract. [Figure 15] Example of a screen for displaying production status.

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described based on the drawings. The delivery service usage method adjustment system according to the present disclosure adjusts the usage method of the delivery service by the cooperation of the first computer of the service provider and the second computer of the service provider.

[0013] The service provider is, for example, a factory that produces and ships products (goods). The service provider is a delivery company that transports products using transportation means such as trucks. The first computer is a production planning system that manages the production of the factory. The second computer is a delivery planning system that manages the delivery plans of the delivery company. According to this embodiment, it is possible to realize delivery adjustment and fee setting with a variation range in the start time of collection by truck by cooperating the production planning system on the factory side and the delivery planning system on the delivery company side.

[0014] As an example, the production planning system formulates a production plan based on production results (progress of production). If the completion of the product is likely to be delayed until the collection time of the regular truck shipment, a delivery contract with a margin of variation (new rate table data) is considered. The determination of whether the completion of the product can meet the truck collection time can be made at a timing corresponding to the time required for the production of the product. For example, if the time required for the production of the product is normally two weeks, it is only necessary to determine whether the truck collection can be met two weeks before the initial collection time. By predicting production delays earlier and concluding new agreements with the delivery service provider earlier, the special fees for the delivery service corresponding to the variation in the collection time can be reduced.

[0015] When considering a new delivery contract, the delivery planning system sets an additional fee for the contract with a margin of variation in the delivery time (collection time). The delivery planning system can, for example, prepare the additional fee for the new contract (new rate table data) before the initial collection time (for example, at least about one week before).

[0016] The method for creating a new contract is as follows, for example. When the delivery planning system obtains the predicted result of production delay from the production planning system, it determines the maximum value of the margin of variation based on the maximum value of the delay time. The delivery planning system further divides the margin of variation at arbitrary intervals (e.g., 0.5h, 1h, 1.5h, etc.) and creates new rate table data in which the fees for the delivery service (delivery fees) are set for each margin of variation.

[0017] In the new rate table data that allows a margin of variation, the fee set for each margin of variation is determined based on the resources borne by the delivery service provider with respect to the margin of variation. For example, based on the number of trucks (number of vehicles) that the delivery service provider must secure to respond to changes in the collection time, the number of drivers, and the lost profit when the truck is not put on standby and assigned to other delivery operations, etc., a fee corresponding to the margin of variation is set.

[0018] When the production planning system receives new price list data from the delivery planning system, it decides whether or not to contract for delivery services according to the new price list data, and if so, what price range to select. Hereafter, these decisions may be referred to as "delivery adjustments."

[0019] When coordinating deliveries, the production management system predicts delays in production time based on the production history of the products to be delivered, and calculates a cumulative distribution function F(h) from the predicted delay time h and the probability of the delay. [Examples]

[0020] The first embodiment will be explained using Figures 1 to 15. In this embodiment, a truck 31 is used as the "first means of transport" and a ship 32 is used as the "second means of transport". The delivery service usage method adjustment system 4 delivers the product 30, which is the "goods", to a predetermined delivery destination (in this case, the port where the ship 32 is waiting) by truck 31.

[0021] The delivery service usage adjustment system 4 is configured, for example, by linking the production planning system 1 and the delivery planning management system 2. The production planning system 1 and the delivery planning system 2 may have a one-to-one correspondence, or they may have a many-to-one, one-to-many, or many-to-many correspondence.

[0022] The production planning system 1 is a computer used in factory 100 to manage the production plan for goods 30 produced by factory 100. The production planning system 1 corresponds to the "first computer". The production planning system 1 has various functions, as described below, such as the production plan creation unit 131, the production performance management unit 132, the production status notification unit 133, the delivery contract management unit 134, and the delivery adjustment unit 135. In Figure 1, the name "unit" is omitted from the name, such as showing the production plan creation unit 131 as "production plan creation 131". The same applies to the function names of the delivery planning system 2. The production planning system 1 can also manage multiple factories 100.

[0023] The delivery planning system 2 is a computer used by a delivery company 200 to collect products 30 produced at factory 100 and transport them to a ship 32, and is considered the "second computer." The delivery planning system 2 has the following functions, as will be described later: a delivery plan creation unit 231, a delivery performance management unit 232, a delivery contract management unit 234, a production status display unit 233, and a delivery fee setting unit 235.

[0024] Production planning system 1 and delivery planning system 2 have a standard contract (standard price list data) and arrange for product 30 to be collected by truck 31 at a predetermined collection time agreed upon in advance. At the predetermined collection time, truck 31 arranged by delivery company 200 arrives at factory 100 and loads product 30. Truck 31, loaded with product 30, moves from factory 100 to a port where ship 32 is waiting and hands over product 30 to ship 32. Product 30 is then transported by ship 32 to various locations both domestically and internationally.

[0025] While the time required to produce product 30 is generally fixed, delays may occur due to shortages of various resources necessary for product 30's production, such as the number of parts in stock, the delivery dates of procured parts, the number of workers available for production, maintenance of production equipment, and securing a production site. In particular, it is difficult to predict the completion date in advance for products that are made to order or one-of-a-kind products. Examples of products whose completion dates are difficult to predict include control panels, power generation equipment, large construction machinery, and industrial machinery. Furthermore, in recent years, global supply chains may be disrupted for political reasons or disasters, making it difficult to accurately predict the completion date (shipment date) of product 30.

[0026] Therefore, if the production planning system 1 determines that the completion date and time of product 30 will be delayed, it obtains new price list data from the delivery planning system 2 and determines a collection date and time corresponding to the production delay in cooperation with the delivery planning system 2.

[0027] The delivery planning system 2 monitors the production status of product 30 based on information from the production planning system 1, and dispatches truck 31 to factory 100 when the completion date approaches. Truck 31 picks up product 30 within a time frame adjusted from the pickup time at the factory and departs for the port.

[0028] Figure 2 is a functional configuration diagram of the delivery service usage method adjustment system 4. The delivery service usage method adjustment system 4 includes at least one production planning system 1 and at least one delivery contract. In Figure 2, multiple production planning systems 1,1(2) and multiple delivery planning systems 2,2(2) are connected bidirectionally via a communication network CN. One production planning system 1 can exchange information with multiple delivery planning systems 2. One delivery planning system 2 can exchange information with multiple production planning systems 1. In other words, one factory 100 can conclude delivery contracts with multiple delivery companies 200 and select the appropriate delivery company according to delays in pickup time. One delivery company 200 can conclude delivery contracts with multiple factories 100 and provide delivery services to each factory 100.

[0029] The production planning system 1 will now be described. The production planning system 1 is formed from a computer that includes, for example, a processor 11, a user interface unit (abbreviated as UI in the figure) 12, a storage device 13, and a communication unit (abbreviated as communication IF in the figure) 14.

[0030] The processor 11 implements each of the functions 131-135 by executing a predetermined computer program stored in the memory device 13. The processor 11 may be either a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit). The processor 11 may also utilize dedicated circuits for performing specific calculations.

[0031] The user interface unit 12 is a device that exchanges information between the user of the production planning system 1 and the production planning system 1. The user interface unit 12 may include, for example, a monitor display, printer, keyboard, touch panel, speech synthesis device, speech recognition device, etc.

[0032] The storage device 13 is a device for storing computer programs and data. The storage device 13 includes main memory and auxiliary storage.

[0033] The communication unit 24 is a device that communicates with the delivery planning system 2 via the communication network CN. The communication network CN may be a public network such as the Internet, or a dedicated line. The communication network CN may be a wireless network, a wired network, or a network that combines both wireless and wired networks.

[0034] The functions performed by the computer programs stored in the storage device 13 will now be described. At least some of the following computer programs can also be updated via the storage medium MM1 or the communication network CN.

[0035] The production planning unit 131 has the function of creating a plan for producing product 30 at factory 100 and notifying factory 100. The production performance management unit 132 manages the execution history of production plans and has the function of managing the actual results (time required for completion, cost, etc.) of product 30 produced at factory 100 in the past. The production performance management unit 132 manages the time, cost, man-hours, etc. required for the completion of product 30. The production status notification unit 133 has the function of notifying factory 100 of the production status of product 30. The delivery contract management unit 134 has the function of managing the delivery service contract (delivery contract) concluded between factory 100 and delivery company 200. The delivery adjustment unit 135 has the function of adjusting the contract with delivery company 200 in accordance with delays in the completion of product 30 (in accordance with delays in shipment).

[0036] The storage device 13 stores, for example, a production plan table 136, a production results table 137, a delivery contract table 138, a production forecast table 139, and a delivery fee table 140. In Figure 2, the word "table" has been removed from the names.

[0037] As will be described later, the production plan table 136 stores the production plan. The production results table 137 stores the production results. The delivery contract table 138 stores the delivery contracts. The production forecast table 139 stores the results of forecasts for production delays and their probabilities. The delivery fee table 140 stores the delivery fees for each fluctuation range that have been concluded with each delivery company.

[0038] The storage medium MM1 is connectable to the production planning system 1 and is a device for non-temporarily storing computer programs or data (hereinafter referred to as "computer programs, etc."). Computer programs, etc. stored in the storage medium MM1 can be transferred to the storage device 13 for storage, and computer programs, etc. stored in the storage device 13 can be transferred to the storage medium MM1 for storage. The storage medium MM1 can also be connected to another computer outside the diagram, and computer programs, etc. stored in the storage medium MM1 can be transferred to the storage device of that other computer for storage.

[0039] An example configuration of the delivery planning system 2 is described below. The delivery planning system 2 is formed from a computer including, for example, a processor 21, a user interface unit 22, a storage device 23, and a communication unit 24. The processor 21, user interface unit 22, storage device 23, and communication unit 24 are the same as the processor 11, user interface unit 12, storage device 13, and communication unit 14 described above, so their description is omitted. The storage medium MM2 is a storage device connected to the delivery planning system 2 and can be used in the same way as the storage medium MM1 described above.

[0040] The functions performed by the computer program stored in the memory device 23 will be explained.

[0041] The delivery plan creation unit 231 has the function of creating a delivery plan, including when and how many trucks 31 the delivery company 200 will allocate to which factory. The delivery performance management unit 232 has the function of managing the execution history of the delivery plan. The production status display unit 233 has the function of notifying the delivery planning system 2 of the production status of product 30 at factory 100. The delivery contract management unit 234 has the function of managing the delivery contract concluded between factory 100 and delivery company 200. The delivery fee setting unit 235 has the function of setting delivery fees according to the changes from the initial collection time.

[0042] The storage device 23 stores, for example, a delivery plan table 236, a delivery performance table 237, a delivery contract table 238, and a delivery fee table 239.

[0043] As will be described later, the delivery plan table 236 stores the delivery plan. The delivery results table 237 stores the delivery results. The delivery contract table 238 stores the delivery contracts. The delivery fee table 239 stores the delivery fees.

[0044] Figure 3 shows an example of a production planning table 136. The production planning table 136 manages, for example, product identification information 1360, target completion date and time 1361, and target times for each process 1362, 1363 in association with each other.

[0045] Product identification information (abbreviated as ID in the figure) 1360 is information that identifies product 30 produced at factory 100. The target completion date and time 1361 indicates the target date and time for the completion of product 30. The target times for each process 1362 and 1363 are the target work times for each process in manufacturing product 30. Figure 3 shows two processes P1 and P2, but product 30 may be manufactured from three or more processes.

[0046] Figure 4 shows an example of a production performance table 137. The production performance table 137 manages, for example, product identification information 1370 in association with the performance data for each process 1371, 1372, and 1373.

[0047] Product identification information 1370 is the same as product identification information 1360 described in Figure 3. The actual results for each process 1371, 1372, and 1373 represent the time required to complete the work at each process.

[0048] Figure 5 shows an example of a delivery contract table 138. The delivery contract table 138 manages, for example, the delivery company name 1380, the contracted rate plan 1381, the plan fee 1382, and the next scheduled pickup date 1383, by associating them with each other.

[0049] The delivery company name 1380 is information that identifies each delivery company 200 that the factory 100 has a contract with. The contracted rate plan 1381 is the rate plan currently contracted with each delivery company 200. Rate plans include, for example, "scheduled delivery" and "variable plan". A "scheduled delivery" is a rate plan in which truck 31 collects products 30 at a fixed time, such as 13:00 every day. Because the collection time of a "scheduled delivery" is constant, it can also be called a "fixed plan" or "fixed plan". A "variable plan" is a rate plan that allows for variations in the collection time of products 30. A "variable plan" allows for a predetermined amount of variation from the standard collection time, for example. In Figure 5, "Variable Plan 2h" is a rate plan that allows for delays of up to 2 hours from the standard collection time. If the standard collection time is 13:00, a maximum delay of 15:00 is allowed. The delivery planning system 2 monitors the production status notified by the production planning system 1 using the production status display unit 233, and dispatches a truck 31 to the factory 100 when the product 30 is ready for shipment. The production planning system 1 may also automatically request pickup from the delivery planning system 2.

[0050] Figure 6 shows an example of a production forecast table 139. The production forecast table 139 manages, for example, product identification information 1390 in association with delay probability 1391 and delay forecast time 1392.

[0051] Product identification information 1390 is the same as product identification information 1360 and 1370 described above. Delay probability 1391 is the probability that a delay in product production (delay in collection time) will occur. Delay prediction time 1392 is the predicted delay time. In Figure 6, for product identification information "PID0003", a delay of "5.6" hours is predicted to occur with a probability of "69.6%". The prediction method is not particularly restricted.

[0052] Figure 7 shows an example of a shipping fee table 140. The shipping fee table 140 manages, for example, the shipping company name 1400, the shipping variation range 1401 and its fee 1402, and subsequent other shipping variation ranges 1403 and their fees 1402 in association with each other.

[0053] Delivery company name 1400 is the same as delivery company name 1380 described in Figure 5. The delivery fluctuation range 1401 is set by dividing the period from the standard collection time to the maximum fluctuation range into multiple segments. For example, delivery company "C0001" sets the delivery fluctuation range in 30-minute increments starting from a minimum value of "1" hour. Delivery company "C0002" sets the delivery fluctuation range in 30-minute increments starting from a minimum value of "0.5" hours. Delivery company "C0003" sets the delivery fluctuation range in 1-hour increments starting from a minimum value of "1" hour. Each delivery company sets its own charges (delivery fees) 1401 and 1404 according to the fluctuation range.

[0054] The following diagram 8 of the delivery planning system shows an example of a delivery planning table 236. The delivery planning table 236 manages, for example, the factory name 2360, collection time 2361, cargo weight 2362, and number of vehicles 2363 in association with each other.

[0055] The factory name 2360 is information that identifies each factory managed by the production planning system 1. The collection time 2361 is the collection time at factory 100. The cargo weight 2362 is the total weight of the products 30 collected at factory 100. The number of vehicles 2363 is the number of trucks 31 required for collection. The load capacity of each truck 31 is not shown here, but the number of vehicles can also be managed for each load capacity.

[0056] Figure 9 shows an example of a delivery performance table 237. The delivery performance table 237 manages data by associating, for example, factory name 2370, collection time 2371, package weight 2372, and number of vehicles 2373. Factory name 2370, collection time 2371, package weight 2372, and number of vehicles 2373 are actual values ​​and are the same as those described in Figure 8 (factory name 2360, collection time 2361, package weight 2362, number of vehicles 2363), so their explanation is omitted.

[0057] Figure 10 shows an example of a delivery contract table 238. The delivery contract table 238 manages, for example, the factory name 2380, the contracted rate plan 2381, the plan fee 2382, and the next scheduled pickup date 2383, by associating them with each other.

[0058] The contracted rate plan 2381, plan fee 2382, and next scheduled pickup date 2383 are the same as the factory name 1380, contracted rate plan 1381, plan fee 1382, and next scheduled pickup date 1383 in the delivery contract table 138 described in Figure 5, so their explanation is omitted. The delivery contract table 238 shown in Figure 10 is a table maintained by a single delivery company 200, and it has a factory name 2380 that identifies each factory 100. In contrast, the delivery contract table 138 described in Figure 5 is a table maintained by a single factory 100, and it has a delivery company name 1380 that identifies each delivery company 200.

[0059] Figure 11 shows an example of a shipping fee table 239. The shipping fee table 239 manages, for example, a factory name 2390 in association with multiple shipping fee ranges 2391, 2393 and their corresponding fees 2392, 2394.

[0060] The factory name 2390 is information that identifies each factory 100. The delivery variation ranges 2391 and 2393 are time ranges that show variation from the standard collection time, as described in Figure 7. The charges 2392 and 2394 are the charges for each variation time. The delivery company 200 can set variable charges for each factory 100. For example, for factory name "F001", a charge of 80,000 yen is set for an initial 1-hour delay, and thereafter the charge increases in 30-minute increments. For factory name "F002", a charge of 52,000 yen is set for an initial 30-minute delay, and thereafter the charge increases in 30-minute increments. For factory name "F003", a charge of 100,000 yen is set for an initial 1-hour delay, and thereafter the charge increases in 1-hour increments.

[0061] The flowchart in Figure 12 will be used to explain the process S100 executed by the production planning system 1.

[0062] When the production planning system 1 receives instructions from the user interface unit 12, it starts this process.

[0063] The production planning system 1 formulates a plan for producing product 30 based on the delivery date of product 30 (S101). The production planning system 1 obtains data from the production performance table 137 showing the past production history of product 30 (S102).

[0064] The production planning system 1 generates forecast data based on actual production data and stores the generated forecast data in the production forecast table 139 (S103).

[0065] The production planning system 1 reads the production results table 137 and the production forecast table 139, compares the production results data with the production forecast data, and determines how much the production progress of product 30 deviates from the production forecast data (S104).

[0066] The production planning system 1 determines whether the production of product 30 will be completed by the deadline (S105). If it determines that the production of product 30 will not be completed by the deadline (S105:YES), that is, if it determines that the production of product 30 will not be completed by the standard collection time (the collection time at this facility), it requests each delivery planning system 3 to send a delivery contract (price list data) via the delivery contract management unit 134 (S106). The production planning system 1 obtains the delivery contract from each delivery planning system 2 (S107) and notifies the factory 100 of the production status (S108).

[0067] The production planning system 1 calculates the cumulative distribution function F(h) described above from the delay time and delay probability shown in the production forecast data of the production forecast table 139 (S109). The production planning system 1 accesses the delivery contract table 138 to refer to the charges for each fluctuation range and calculates the economic loss LD caused by the delay and the charge DF required for the delivery contract for the fluctuation range that covers the delay (S110), and evaluates the magnitude of these (S111).

[0068] If the production planning system 1 determines that the loss LD resulting from production delays is greater than the shipping fee DF which is increased according to the range of fluctuation (S111: YES), it enters into a shipping contract with the shipping planning system 2 that allows for fluctuations in the collection time under conditions that maximize the difference (S112).

[0069] The production planning system 1 reads the production results table 137 and the production forecast table 139 and notifies the delivery planning system 2 of the production status of product 30 (S113). The delivery planning system 2 displays the production status of product 30 on the production status display unit 233 and notifies the delivery company 200.

[0070] The production planning system 1 monitors whether the shipment of product 30 has been completed (S114). If product 30 is completed, loaded onto truck 31, and shipped (S114: YES), the production planning system 1 completes this process successfully.

[0071] On the other hand, if it is determined that the production of product 30 is proceeding as planned and no delays will occur (S105: NO), or if it is determined that the shipping fee DF, which is increased according to the range of fluctuations, is greater than or equal to the loss LD due to delays in the production of product 30 (delays in shipment or delays in collection) (S111: NO), the production planning system 1 notifies the factory 100 of the production status (S115) and monitors whether product 30 has been shipped (S116). When the production planning system 1 learns that product 30 has been shipped (S116: YES), it completes this process normally.

[0072] The flowchart in Figure 13 will be used to explain the process S200 executed in the delivery planning system 2.

[0073] When the delivery planning system 2 receives a request from the user via the user interface unit 22, it starts this process and retrieves the current status of the delivery contract from the delivery contract table 238 (S201).

[0074] The delivery planning system 2 determines whether it has received a request for a price table from the production planning system 1, as described in step S106 of Figure 12 (S202).

[0075] If the production planning system 1 requests the delivery planning system 2 to send a price table (price list data) (S202:YES), the delivery planning system 2 obtains the results of the production delay prediction from the production planning system 1 (S203).

[0076] The delivery planning system 2 determines the maximum value and range of the variation in the delivery contract for the variable plan based on the predicted delay time for product 30 production (S204). The delivery planning system 2 sets the delivery fee for each variation range determined in step S204 and generates a fee table (more specifically, a delivery contract including the fee table) corresponding to the variation in collection time (S205). The delivery planning system 2 sends the generated fee table to the production planning system 1 (S206).

[0077] On the other hand, if the production planning system 1 has not requested a price table (S202:NO), the delivery planning system 2 creates a delivery plan based on the delivery contract (S207) and determines whether the product 30 has been collected from factory 100 and the delivery has been completed (S208). If the delivery has not been completed (S208:NO), the system returns to step S201.

[0078] If product 30 is loaded onto truck 31 and delivery to the designated location is completed (S208: YES), the delivery planning system 2 stores the delivery information confirmed in step S208 in the delivery results table 237 (S209). Once the delivery is complete, the delivery planning system 2 updates the delivery contract in the delivery contract table 238 (S210). Then, it returns to step S201.

[0079] Figure 14 is a flowchart of process S300 for setting up a delivery contract. This process is executed by production planning system 1. This process may be executed when production planning system 1 creates a production plan, when requested by a user, or automatically or semi-automatically depending on the progress of the production plan.

[0080] Production planning system 1 obtains the date and time covered by the delivery contract based on instructions from the user (S301). Production planning system 1 selects the type of delivery contract (S302). Examples of delivery contract types include "regular delivery" and "variable plan".

[0081] The production planning system 1 stores the date and time specified in step S301 and the type of delivery contract selected in step S302 (S303). The production planning system 1 determines whether the delivery contract setup is complete (S304). If the delivery contract has not been completed (S304: NO), it returns to step S301. If the delivery contract setup is complete (S304: YES), this process is completed successfully.

[0082] As shown in Figure 14, the production planning system 1 can conclude a delivery contract for the scheduled shipping date (scheduled collection date) of product 30 at any point before or during the start of production of product 30. Alternatively, as described in Figure 12, if the production planning system 1 determines that the production of product 30 is delayed and will not meet the scheduled collection date (scheduled shipping date), it can also conclude a variable plan between the factory 100 and the delivery company 200. Thus, in this embodiment, the production planning system 1 can dynamically conclude a delivery contract according to the production status of product 30, and can also conclude a delivery contract according to the user's instructions.

[0083] Figure 15 shows an example of a screen displaying production status. The production status display unit 233 of the delivery planning system 2 generates a screen G1 as shown in Figure 15 based on information notified from the production status notification unit 133 of the production planning system 1, and provides it to the delivery company 200.

[0084] The production status display result G1 is a screen that displays the production status of product 30 at factory 100 and provides this information to the delivery company 200. Screen G1 includes, for example, a display unit G11 that lists the contract status for each factory and a display unit G12 that lists the production status for each factory.

[0085] Screen G11 displays, for example, the factory name G110, the contracted rate plan G111, the fee G112, and the next scheduled pickup date G113. The factory name G110 is a name used to distinguish each factory 100. The contracted rate plan G111 is the plan (details of the delivery contract or the name of the delivery contract) that factory 100 has contracted with delivery company 200. The fee G112 is the fee. The next scheduled pickup date G113 is the time of the next pickup.

[0086] The display unit G12 includes, for example, the factory name G120, the scheduled completion date and time G121, the production delay G122, the probability of collection delay G123, and the predicted collection delay time G124. The factory name G120 is a name used to identify each factory. The scheduled completion date and time G121 indicates the date and time (scheduled shipping date and time or scheduled collection date and time) when product 30 is scheduled to be completed. The production delay G122 indicates the amount of time that product 30 is behind schedule in the current production situation. The probability of collection delay G123 indicates the probability of a delay occurring when product 30 is completed and is calculated from a cumulative distribution function. The predicted collection delay time G124 is the amount of time that the collection time is predicted to be delayed from the original scheduled date and time.

[0087] For factory "F103," where the probability of collection delays is higher than a predetermined value, a warning is issued, as shown by the thick black frame in the diagram. When a user of delivery company 200 presses button B11, the production status at the warned factory "F103" is displayed.

[0088] If a delivery contract allows for a range of variation, Factory 100 determines the pickup time by a predetermined date and time (for example, the day before dispatch (the day before collection)) and requests it from the delivery company 200. Until the final collection time is determined, the production status at Factory 100 is shared from the production planning system 1 to the delivery planning system 2 and visualized on screen G1 so that the delivery company 200 can get a rough estimate.

[0089] According to this embodiment, the production planning system 1 on the factory 100 side and the delivery planning system 2 on the delivery company 200 side are linked, enabling delivery adjustments and pricing that allow for a range of variation in the start time of pickup by the truck 31.

[0090] According to this embodiment, efficient delivery can be achieved because the delivery service (plan) can be selected as needed based on the production status.

[0091] According to this embodiment, by predicting production delays and concluding new arrangements with delivery companies early on, it is possible to reduce the special charges for delivery services that accommodate fluctuations in pickup times.

[0092] According to this embodiment, the cost of selecting a variable plan to accommodate fluctuations in collection times is compared with the economic loss caused by delays in the collection of product 30. If the economic loss is greater, the variable plan is selected, allowing for the selection of a reasonable pricing plan and improving usability.

[0093] The delivery planning system sets additional charges for contracts that allow for variations in delivery time (pickup time) when considering new delivery contracts. For example, the delivery planning system can prepare additional charges for new contracts (new price list data) before the initial pickup time (for example, at least a week in advance).

[0094] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. For example, the embodiments described above are explained in detail to make the present invention easier to understand, and are not necessarily limited to those having all the configurations described. Furthermore, some or all of the above configurations, functions, processing units, processing means, etc., may be implemented in hardware, for example, by designing them as integrated circuits. Furthermore, each of the above configurations, functions, etc., may be implemented in software by having a processor interpret and execute a program that realizes each function. Information such as programs, tables, files, etc., that realize each function can be stored in memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD. (Note 1) A delivery service usage method adjustment system that adjusts the method of using a delivery service to deliver requested goods to a specified location, A first computer used by the service provider to which the aforementioned delivery service is provided, The system comprises a first computer connected to a second computer via a communication network and used by a service provider that provides the delivery service, The first computer comprises one or more first processors, one or more first memories, and a first communication unit. The second computer comprises one or more second processors, one or more second memories, and a second communication unit. If the first processor predicts that the scheduled delivery date and time for handing over the goods to be delivered to the delivery service will be later than the standard date and time specified in the standard price list data set with the second computer, it requests the second computer, via the first communication unit, to send new price list data that allows for the change in the scheduled delivery date and time. When the second processor receives a request from the first computer at the second communication unit, it generates new price list data including one or more variation ranges that allow for variations in the scheduled delivery date and time, and the charges for each variation range, stores the generated new price list data in the second memory, and transmits it to the first computer. The first processor determines whether or not to adopt the new price list data by comparing the new price list data received from the second computer with predetermined conditions stored in the first memory. A system for adjusting the usage method of delivery services. (Note 2) The predetermined conditions are generated based on the amount of loss incurred due to the delay in the scheduled delivery date and time relative to the reference date and time, and the increase in the delivery service fee due to the new price list data, and the new price list data is adopted when the amount of loss is greater than the increase in the fee, as described in (Appendix 1) of the delivery service usage method adjustment system. (Note 3) The delivery service usage method adjustment system described in (Appendix 2), wherein the first computer causes the first processor to predict the length of the delay time and the probability of its occurrence, and transmits the predicted length of the delay time and the probability of its occurrence to the second computer via the first communication unit. (Note 4) The delivery service usage method adjustment system described in (Appendix 3), wherein the second computer generates new price list data by having the second processor calculate one or more fluctuation ranges and charges for each fluctuation range based on the length of the delay time and the probability of occurrence received from the first computer. (Note 5) The service provider is a factory that produces the goods, and the goods produced at the factory are transported to their destination using a first means of transport and a second means of transport which has a longer transport cycle than the first means of transport. The service provider provides the delivery service using the first means of transport to the factory, as described in (Appendix 4), a delivery service usage method adjustment system. (Note 6) The first computer pre-arranges the standard price list data with the second computer at a timing corresponding to the time required by the factory to produce the goods, as described in (Appendix 5) for the delivery service usage method adjustment system. (Note 7) A method for adjusting the method of using a delivery service, which adjusts the method of using a delivery service to deliver requested goods to a designated location, using a computer system. The aforementioned computer system, A first computer used by the service provider to which the aforementioned delivery service is provided, The system comprises a first computer connected to a second computer via a communication network and used by a service provider that provides the delivery service, If the first computer predicts that the scheduled delivery date and time for handing over the goods to be delivered to the delivery service will be later than the standard date and time specified in the standard price list data set with the second computer, it requests the second computer to send new price list data that allows for the change in the scheduled delivery date and time. When the second computer receives a request from the first computer, it generates new price list data including one or more variation ranges that allow for changes in the scheduled delivery date and time, and the fee for each variation range, and transmits the generated new price list data to the first computer. The first computer determines whether or not to adopt the new price list data by comparing the new price list data received from the second computer with predetermined conditions set in advance. How to use and adjust delivery services. [Explanation of Symbols]

[0095] 1: Production planning system, 2: Delivery planning system, 4: Delivery service usage method adjustment system, 30: Products, 31: Trucks, 32: Ships, 100: Factory, 131: Production planning department, 132: Production performance management department, 133: Production status notification department, 134: Delivery contract management department, 135: Delivery adjustment department, 200: Delivery company, 231: Delivery planning department, 232: Delivery performance management department, 233: Production status notification department, 234: Delivery contract management department, 235: Delivery fee setting department

Claims

1. A delivery service usage method adjustment system that adjusts the method of using a delivery service to deliver requested goods to a specified location, A first computer used by the service provider to which the aforementioned delivery service is provided, The system comprises a first computer connected to a second computer via a communication network and used by a service provider that provides the delivery service, The first computer comprises one or more first processors, one or more first memories, and a first communication unit. The second computer comprises one or more second processors, one or more second memories, and a second communication unit. The first processor generates predictive data based on production performance data, If the first processor predicts, based on the forecast data, that the scheduled delivery date and time for handing over the goods to be delivered to the delivery service will be later than the standard date and time specified in the standard price list data set with the second computer, it requests the second computer, via the first communication unit, to transmit new price list data that allows for the change in the scheduled delivery date and time. When the second processor receives a request from the first computer via the second communication unit, it obtains the result of the production delay prediction from the first computer. The second processor generates new price list data, including one or more variation ranges that allow for variations in the scheduled delivery date and time, and the charges for each variation range, based on the results of predicting the production delay, stores the generated new price list data in the second memory, and transmits it to the first computer. The first processor adopts the new pricing data if, based on the new pricing data received from the second computer and the forecast data, the amount of loss resulting from the delay in the scheduled delivery date and time relative to the reference date and time is greater than the increase in the delivery service fee due to the new pricing data. A system for adjusting the usage method of delivery services.

2. The first computer has the first processor predict the length of the delay time and the probability of its occurrence, and transmits the predicted length of the delay time and the probability of its occurrence to the second computer via the first communication unit. A delivery service usage method adjustment system according to claim 1.

3. Based on the length of the delay time and the probability of occurrence received from the first computer, the second computer has the second processor calculate one or more fluctuation ranges and the charges for each fluctuation range to generate the new price list data. A delivery service usage method adjustment system according to claim 2.

4. The service provider is a factory that produces the goods, and the goods produced at the factory are transported to their destination using a first means of transport and a second means of transport having a longer transport cycle than the first means of transport. The service provider provides the factory with the delivery service using the first means of transport. A delivery service usage method adjustment system according to claim 3.

5. The first computer pre-arranges the standard price list data with the second computer at a timing corresponding to the time required by the factory to produce the goods. A delivery service usage method adjustment system according to claim 4.

6. A method for adjusting the method of using a delivery service, which adjusts the method of using a delivery service to deliver requested goods to a designated location, using a computer system. The aforementioned computer system, A first computer used by the service provider to which the aforementioned delivery service is provided, The system comprises a first computer connected to a second computer via a communication network and used by a service provider that provides the delivery service, The first computer generates forecast data based on production performance data, If the first computer predicts, based on the forecast data, that the scheduled delivery date and time for handing over the goods to be delivered to the delivery service will be later than the standard date and time specified in the standard price list data set with the second computer, it requests the second computer to send new price list data that allows for the change in the scheduled delivery date and time. When the second computer receives a request from the first computer, it obtains the results of the production delay prediction from the first computer. The second computer generates new price list data, including one or more variation ranges that allow for variations in the scheduled delivery date and time, and the charges for each variation range, based on the results of predicting the production delay, and transmits the generated new price list data to the first computer. The first computer adopts the new pricing data if, based on the new pricing data received from the second computer and the forecast data, the amount of loss resulting from the delay in the scheduled delivery date and time relative to the reference date and time is greater than the increase in the delivery service fee due to the new pricing data. How to use and adjust delivery services.

Images