Delivery date management support system, delivery date management support method, and program
The delivery date management system addresses the challenge of delayed delivery dates by adjusting promised dates based on plan changes, enhancing customer satisfaction through timely delivery.
Patent Information
- Application Number
- JP2023072729
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-26
- Publication Date
- 2024-11-08
AI Technical Summary
Existing delivery date management systems fail to adjust delivery dates proactively when they are set later than the customer's requested date, leading to potential delays and decreased customer satisfaction.
A delivery date management system that includes an order information storage unit, delivery date information storage unit, and an adjustment unit to adjust promised delivery dates based on changes in plan information, allowing for early adjustment of delivery dates.
Enables proactive adjustment of delivery dates to meet customer requests, improving satisfaction by ensuring timely delivery and reducing the impact of delays.
Smart Images

Figure 2024157991000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a delivery date management support system, a delivery date management support method, and a program. [Background technology]
[0002] There are known delivery date management systems that aim to improve the efficiency of delivery date management. For example, Patent Document 1 discloses a delivery date management system that adds a delivery date compliance rate represented by a risk prediction value and production progress information of purchased items to delivery date information, making it possible to take pre-planned measures to meet delivery dates, such as urging other companies to meet production progress and considering the allocation of other companies' inventory. This delivery date management system compares the scheduled delivery date with the actual result and issues a warning if a delay occurs. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2005-122581 A Summary of the Invention [Problem to be solved by the invention]
[0004] After a delivery date is set with a customer, the date on which the product can be provided to the customer may be earlier than expected. In such a case, particularly when the delivery date is set later than the customer's request, it is desirable to adjust the delivery date with the customer and bring the delivery date forward.
[0005] However, in the technology of Patent Document 1, when the delivery date set with the customer is later than the delivery date requested by the customer, it is difficult to propose an adjustment of the delivery date even if each process is completed earlier than planned. In addition, in Patent Document 1, the occurrence of a delay is identified by comparing the schedule with the actual results, so the delay cannot be identified until the actual results are confirmed. This leads to a slow initial response when the delivery date is delayed, which may lead to a decrease in customer satisfaction. For this reason, support for adjusting the delivery date early is required.
[0006] The present disclosure has been made in consideration of the above-mentioned problems, and aims to provide a delivery date management support system, a delivery date management support method, and a program that provide support for early adjustment of delivery dates. [Means for solving the problem]
[0007] In order to achieve the above object, the delivery date management support system according to the present disclosure includes an order information storage means, a delivery date information storage means, a plan information storage means, and an adjustment means. The order information storage means stores order information. The delivery date information storage means stores delivery date information indicating a promised delivery date agreed upon with a customer for an ordered item or service. The plan information storage means stores plan information indicating a plurality of plans for providing the ordered item or service. The adjustment means proposes adjusting the corresponding promised delivery date for an order whose promised delivery date is later than a customer-requested delivery date included in the order information, when a change in the plan indicated by the plan information stored in the plan information storage means causes the time when the item or service can be provided to be earlier than the promised delivery date. Effect of the Invention
[0008] According to the present disclosure, for an order whose promised delivery date is later than the customer-requested delivery date included in the order information, if a plan is changed, it is proposed to adjust the corresponding promised delivery date. Therefore, it is possible to provide support for early implementation of delivery date adjustment. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram showing a configuration of a delivery date management support system according to a first embodiment. [Diagram 2] FIG. 1 is a diagram showing an example of a functional configuration of a delivery date management device for each of first to fourth layers according to a first embodiment; [Diagram 3] A diagram showing the relationship between the requested delivery date, the reply delivery date, and the promised delivery date [Figure 4] A diagram showing the procedure for replying to delivery dates at each layer [Diagram 5] Flowchart showing delivery date adjustment control processing according to the first embodiment [Figure 6] Flowchart showing a promised delivery date setting process according to the first embodiment [Figure 7] Diagram showing multiple companies in the next tier [Figure 8] Flowchart showing readjustment control processing according to the first embodiment [Figure 9] A diagram showing the relationship between the requested delivery date, the reply delivery date, and the promised delivery date [Figure 10] FIG. 1 is a diagram showing an example of a hardware configuration of a first-layer due date management device according to a first embodiment; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, a delivery date management support system, a delivery date management support method, and a program according to an embodiment of the present disclosure will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals.
[0011] (Embodiment 1) The configuration of a delivery date management support system 100 according to the first embodiment will be described with reference to FIG.
[0012] The delivery date management support system 100 is a system that i) receives order information including the product to be ordered and its quantity, requested delivery date, etc. from a customer, ii) obtains a response delivery date that is a delivery date when the product can be delivered to the customer based on the order information, inventory information, inventory plan information, etc., iii) presents the response delivery date to the customer and sets a promised delivery date that is a delivery date agreed upon through negotiation with the customer, and iv) monitors various plans for delivery of products whose promised delivery date is later than the requested delivery date, and proposes an adjustment of the promised delivery date when a condition that allows the promised delivery date to be brought forward by changing the plan is met. The delivery date management support system 100 supports delivery date management by utilizing inventory information, production plan information, etc. in an organization that handles each preparation process from procuring materials, manufacturing parts, manufacturing products from the parts, and selling them in a supply chain.
[0013] In this embodiment, the organizations that make up the supply chain that supplies products to customers are represented by four layers. For example, the first layer is where companies with sales functions that are the contact points with customers are located, the second layer, which is the layer after the first layer, is where companies with manufacturing functions are located, the third layer, which is the layer after the second layer, is where companies with the function of supplying parts necessary for the manufacture of products are located, and the fourth layer, which is the layer after the third layer, is where companies with the function of supplying materials necessary for the manufacture of parts are located. Hereinafter, the first layer will be referred to as "sales companies", the second layer as "manufacturing companies", the third layer as "parts companies", and the fourth layer as "material companies".
[0014] The delivery date management support system 100 in the first embodiment includes a first-layer delivery date management device 21 representing a device that manages various delivery dates set in the first layer, a second-layer delivery date management device 22 representing a device that manages various delivery dates set in the second layer, a third-layer delivery date management device 23 representing a device that manages various delivery dates set in the third layer, a fourth-layer delivery date management device 24 representing a device that manages various delivery dates set in the fourth layer, an overall management device 10 that overall manages the first-layer delivery date management device 21, the second-layer delivery date management device 22, the third-layer delivery date management device 23, and the fourth-layer delivery date management device 24, a storage device 30 that stores various information for delivery date management, and a user terminal 40 used by a user. Details of delivery dates will be described later with reference to FIG. 3.
[0015] The storage device 30 is configured by a server device, and includes a performance information storage unit 301 that stores performance information indicating various performances, and a management information storage unit 302 that holds information required for adjusting delivery dates.
[0016] The performance information storage unit 301 stores therein order information including products to be ordered by customers, their quantities, requested delivery dates, etc., order performance information indicating past orders in each layer from the first to fourth layers, delivery date information indicating promised delivery dates agreed upon with customers, plan information indicating multiple plans for providing ordered items, quantity performance information indicating shipment and inventory quantities, etc. The performance information storage unit 301 is an example of an order information storage means, delivery date information storage means, and plan information storage means according to the present disclosure.
[0017] The management information storage unit 302 has a function of retaining product numbers, order numbers, purchase order numbers, customer and information on each layer, etc., in order to link each layer and adjust delivery dates across the entire supply chain.
[0018] The storage device 30 is connected to a network NW, and the information is updated as the business progresses. The storage device 30 may be configured as a single device, or may be configured as multiple storage devices that are distributed.
[0019] The first layer delivery date management device 21, the second layer delivery date management device 22, the third layer delivery date management device 23, and the fourth layer delivery date management device 24 are configured by computer devices and have the same functions. Although details will be described later, the first layer delivery date management device 21, the second layer delivery date management device 22, the third layer delivery date management device 23, and the fourth layer delivery date management device 24 manage delivery dates at each layer and adjust delivery dates in cooperation with the layer one level above and the layer one level below. For example, the second layer delivery date management device 22 adjusts delivery dates in cooperation with the first layer delivery date management device 21, which is the layer one level above, and the third layer delivery date management device 23, which is the layer one level below.
[0020] The overall control device 10 is configured by a computer device. The overall control device 10 includes an adjustment unit 11 that calculates reply deadlines for customers, and an overall control device storage unit 18 that holds information required for management. The adjustment unit 11 has a function of linking information about delivery dates between each layer from the first layer to the fourth layer, and calculating a delivery date to be replied to a customer. The overall management device storage unit 18 has a function of retaining information necessary for the linkage management of the first delivery date management device 21 to the fourth delivery date management device 24, including plan information from the first layer to the fourth layer. For example, in the case of the second layer, there is a delivery date between the first layer, which is the layer above, and a delivery date between the third layer, which is the layer below. Details of delivery dates between each layer will be described later.
[0021] The user terminal 40 is configured by a terminal device and has a display device. The user terminal 40 is connected to the overall management device 10 via the network NW. The user terminal 40 outputs information indicating various delivery dates determined by delivery date adjustment and displays it on the display device. In FIG. 1, one user terminal 40 is illustrated as an example for ease of explanation, but the number of user terminals 40 is arbitrary and is usually multiple. In addition, the user terminal 40 may be any terminal that can transmit information to the user, and there are no limitations on the owner, operator, installation location, etc.
[0022] Next, the functional configuration of the first layer delivery date management device 21 to the fourth layer delivery date management device 24 will be described with reference to FIG. The first-layer delivery date management device 21 is communicatively connected to a customer terminal 50 via a network NW. A customer operates the customer terminal 50 to place an order for a product with a sales company corresponding to the first layer. In FIG. 2, one customer terminal 50 is illustrated as an example to make the disclosure easier to understand, but the number of customer terminals 50 is arbitrary and is usually more than one. In addition, the customer terminal 50 may be any terminal that can transmit information to a customer, and there are no limitations on the owner, operator, installation location, etc.
[0023] The second-layer delivery date management device 22 is communicably connected to the first-layer delivery date management device 21 and the third-layer delivery date management device 23 via the network NW. The third layer delivery date management device 23 is communicably connected to the second layer delivery date management device 22 and the fourth layer delivery date management device 24 via the network NW. The fourth-layer due date management device 24 is communicably connected to the third-layer due date management device 23 via the network NW.
[0024] The first layer delivery date management device 21 comprises a first layer order receiving unit 111 that processes orders, a first layer inventory confirmation unit 112 that checks the inventory of products held in the first layer, a first layer plan creation unit 113 that draws up various plans for the first layer, a first layer ordering unit 114 that places orders from the first layer to the second layer, a first layer result management unit 115 that manages results, and a first layer memory unit 116 that stores various information necessary for managing delivery dates in the first layer.
[0025] The first layer order receiving unit 111 receives and processes order information from the customer terminal 50 of the order source. Specifically, the first layer order receiving unit 111 receives order information transmitted from the customer terminal 50. The order information includes information indicating the ordered product and quantity, the customer's desired delivery date, price, packaging, etc. The first layer order receiving unit 111 has a function of processing the order information and processing the customer who placed the order, the ordered product and quantity, the customer's desired delivery date (hereinafter, for distinction, requested delivery date), etc. The customer is specified by the customer name, customer ID (Identification: identification information), etc., and the product is specified by the product name, model number, product ID, etc. The quantity indicates the number or amount of ordered products. The number means the number of pieces, lot number, pallet number, etc., and the amount means the weight, volume, etc. The requested delivery date means the delivery date requested or desired by the customer.
[0026] The first layer inventory confirmation unit 112 has a function of determining whether or not the entire ordered quantity can be shipped in response to an order from a customer using the product inventory held in the first layer, in other words, by the sales company.
[0027] The first layer plan creation unit 113 creates various plans including a sales plan, a purchase plan, and an inventory plan. The sales plan is a plan that indicates the timing and the planned sales quantity to the customer for each product. The purchase plan is a plan that indicates the timing and the purchase quantity from the second layer manufacturing company for each product. The inventory plan is a plan that indicates the timing and the planned inventory quantity for each product. Since the inventory amount decreases by sales and increases by purchase, the inventory plan is linked to the sales plan and the purchase plan. Hereinafter, the sales plan, the purchase plan, the inventory plan, etc. are collectively referred to simply as the plan. Specifically, when the first layer inventory confirmation unit 112 determines that the current product inventory at the sales company is not sufficient to ship orders from customers, the first layer plan creation unit 113 cooperates with the second layer manufacturing company to find out when the missing products can be secured, and creates a new purchase plan and inventory plan.
[0028] The first layer ordering unit 114 transmits the first layer plan to the second layer. Specifically, the first layer plan creation unit 113 transmits to the second layer delivery date management device 22 the purchase plan that is drawn up to purchase the required quantity of products to be shipped to customers at the required time.
[0029] The first-layer result management unit 115 manages the results that are the results of various plans. Specifically, the first-layer result management unit 115 tally and manages the quantity, delivery date, etc. of products delivered from the second layer.
[0030] The first-layer storage unit 116 has a function of holding information necessary for managing delivery dates in the first-layer delivery date management device 21, for example, information necessary for managing delivery dates including inventory information and planning information in the first layer. In addition, information obtained in the first-layer delivery date management device 21 is saved in the first-layer storage unit 116 and is also stored in the storage device 30 and shared.
[0031] The second layer to fourth layer delivery date management devices 22 to 24 basically have the same functions and configurations as the first layer delivery date management device 21. Therefore, the second layer to fourth layer delivery date management devices 22 to 24 will be described below.
[0032] The second layer delivery date management device 22 also includes a second layer order receiving unit 121 that processes orders, a second layer inventory confirmation unit 122 that checks the inventory of products held in the second layer, a second layer plan creation unit 123 that draws up various plans for the second layer, a second layer ordering unit 124 that places orders from the second layer to the third layer, a second layer result management unit 125 that manages results, and a second layer memory unit 126 that stores various information necessary for managing delivery dates in the second layer.
[0033] The second layer order receiving unit 121 processes product orders from the first layer delivery date management device 21. Specifically, the second layer order receiving unit 121 has a function of processing the ordered product and quantity, the first layer requested delivery date, and the like. The second layer inventory confirmation unit 122 has a function of determining whether or not the entire order quantity can be shipped in response to an order from the first layer using the product inventory held by the second layer, in other words, the manufacturing company.
[0034] The second layer plan creation unit 123 creates or modifies various plans including sales plans, production plans, product inventory plans, parts inventory plans, and parts purchasing plans. The sales plan is a plan showing the planned sales timing and planned sales quantity to the first layer for each product. The production plan is a plan showing the production timing and production quantity for each product. The product inventory plan is an inventory plan for the second layer, i.e., the manufacturing company, for each product. The parts inventory plan is a plan for the inventory of parts used to manufacture the product. The parts purchasing plan is a plan for purchasing parts to the third layer, i.e., the parts company, to manufacture the product. Specifically, when the product inventory in the second layer cannot meet the order from the first layer, the second layer plan creation unit 123 formulates a production plan for the product that is insufficient. At this time, the second layer plan creation unit 123 determines whether or not there are enough parts required for production, and modifies the parts purchasing plan and the parts inventory plan as necessary.
[0035] The second layer ordering unit 124 transmits the second layer plan to the third layer.
[0036] The second layer result management unit 125 manages the results that are the results of various plans in the second layer. The second-layer storage unit 126 stores information necessary for managing delivery dates in the second-layer delivery date management device 22, such as inventory information, planning information, and the like in the second layer. The information obtained by the second-layer delivery date management device 22 is stored in the second-layer storage unit 126, and is also stored in the storage device 30 and shared.
[0037] The third layer delivery date management device 23 also includes a third layer order receiving unit 131 that processes orders, a third layer inventory confirmation unit 132 that checks the inventory of parts held in the third layer, a third layer plan creation unit 133 that draws up various plans for the third layer, a third layer ordering unit 134 that places orders from the third layer to the fourth layer, a third layer result management unit 135 that manages results, and a third layer memory unit 136 that stores various information necessary for managing delivery dates in the third layer.
[0038] The third layer order receiving unit 131 processes orders for parts from the second layer delivery date management device 22. Specifically, the third layer order receiving unit 131 processes the ordered parts and quantities, the second layer requested delivery date, and the like. The third layer inventory confirmation unit 132 has a function of determining whether or not the entire order quantity can be shipped in response to an order from the second layer, in other words, with the parts inventory held by the parts company.
[0039] The third layer plan creation unit 133 creates or modifies various plans including sales plans, production plans, parts inventory plans, material inventory plans, and material purchase plans. The sales plan is a plan showing the planned sales timing and planned sales quantity to the second layer for each part. The production plan is a plan showing the production timing and production quantity for each part. The parts inventory plan is an inventory plan for the third layer, i.e., the parts company, for each part. The material inventory plan is a plan for the inventory of materials used to manufacture the parts. The material purchase plan is a plan for the purchase of materials to the fourth layer, i.e., the material company, to manufacture the parts. Specifically, when the parts inventory in the third layer cannot meet the order from the second layer, the third layer plan creation unit 133 creates or modifies a production plan for the parts that are insufficient. At this time, the third layer plan creation unit 133 determines whether or not there is a sufficient amount of materials required for production, and modifies the material purchase plan and the material inventory plan as necessary.
[0040] The third layer ordering unit 134 transmits the third layer plan to the fourth layer.
[0041] The third layer result management unit 135 manages the results that are the results of various plans in the third layer. The third-layer storage unit 136 stores information necessary for managing delivery dates in the third-layer delivery date management device 23, such as inventory information, planning information, and the like in the third layer. The information obtained by the third-layer delivery date management device 23 is saved in the third-layer storage unit 136, and is also stored in the storage device 30 and shared.
[0042] The fourth layer order receiving unit 141 processes orders for materials from the third layer delivery date management device 23. Specifically, the fourth layer order receiving unit 141 processes the ordered materials and quantities, the third layer requested delivery date, and the like. The fourth layer inventory confirmation unit 142 has a function of determining whether or not the entire order quantity can be shipped in response to an order from the third layer using the stock of materials held by the fourth layer, in other words, the materials supplier.
[0043] The fourth layer plan creation unit 143 creates or modifies various plans including sales plans, production plans, purchase plans, and inventory plans. The sales plan is a plan showing the planned sales timing and planned sales quantity to the third layer by material. The production plan is a plan showing the production timing and production quantity by material. The inventory plan is an inventory plan for the fourth layer, i.e., material companies, by material. The purchase plan is a plan for purchasing materials from other companies to manufacture materials. Specifically, when the material inventory in the fourth layer is not enough to fulfill orders from the third layer, the fourth layer plan creation unit 143 creates or modifies a production plan for the shortage of materials. In addition, the fourth layer plan creation unit 143 modifies the purchase plan for materials from other companies as necessary. It also modifies the inventory plan.
[0044] The fourth layer order unit 144 transmits the purchase plan of the fourth layer to other companies. In this embodiment, there are no layers below the fourth layer. Therefore, the fourth layer order unit 144 does not actually function.
[0045] The fourth layer result management unit 145 manages the results that are the results of various plans in the fourth layer. The fourth-layer storage unit 146 stores information necessary for managing delivery dates in the fourth-layer delivery date management device 24, such as inventory information, planning information, and the like in the fourth layer. The information obtained by the fourth-layer delivery date management device 24 is saved in the fourth-layer storage unit 146, and is also stored in the storage device 30 and shared.
[0046] Next, various delivery times in this embodiment will be described with reference to FIG. First, the first-tier sales company receives an order for a product from a customer. At that time, the delivery date presented by the customer is regarded as the customer-requested delivery date. The delivery date presented by the first-tier sales company to the customer regarding the timing of providing the ordered product relative to the customer-requested delivery date is regarded as the responded delivery date. If the customer-requested delivery date and the responded delivery date match, the matched delivery date is regarded as the promised delivery date. In this case, delivery date management is implemented throughout the entire supply chain to ensure that the promised delivery date is met without delay. If the customer-requested delivery date and the responded delivery date do not match, delivery date adjustments are made between the sales company and the customer, and the delivery date agreed upon with the customer is regarded as the promised delivery date. If the promised delivery date is later than the customer-requested delivery date, delivery date management is implemented throughout the entire supply chain, and if the process is progressing quickly and there is a possibility that the delivery date will be earlier than the promised delivery date, and if the difference with the customer-requested delivery date can be shortened even slightly, readjustments are implemented to shorten the delivery date.
[0047] If the product inventory of the sales company in the first layer cannot fulfill the order from the customer, the first layer will order the product from the manufacturing company in the second layer and confirm the delivery date. At that time, a delivery date from the first layer to the second layer is set to meet the customer's requested delivery date. This is called requested delivery date 1. The manufacturing company in the second layer determines whether requested delivery date 1 can be met. If the product inventory in the second layer cannot be met, the manufacturing company in the second layer orders the parts necessary for the production of the product from the parts company in the third layer and requests delivery. The date set at that time is called requested delivery date 2. As with requested delivery date 1, the parts company in the third layer determines whether requested delivery date 2 can be met. If the parts inventory in the third layer cannot be met, the parts company in the third layer orders the materials necessary for the production of the parts from the materials company in the fourth layer and requests delivery. The delivery date set at that time is called requested delivery date 3.
[0048] The material company, which is the fourth layer, judges whether the requested delivery date 3 can be met. When the supply chain is composed of N layers, this confirmation of the delivery date is performed up to the Nth layer. In this embodiment, since the supply chain is composed of four layers, the delivery date confirmed in the fourth layer is transmitted as the answered delivery date 3 from the material company, which is the fourth layer, to the parts company, which is the third layer. Regarding the answered delivery date 3, a delivery date adjustment is performed between the fourth layer and the third layer, and the delivery date as a result of the delivery date adjustment is set as the promised delivery date 3. The delivery date adjustment at this time is set as the delivery date adjustment 3. Similarly, from the third layer to the first layer, delivery date adjustment is performed between each layer, a promised delivery date is set, and the promised delivery date 1 of the first layer is determined. In response to this, the answered delivery date is presented from the first layer to the customer, and the promised delivery date is determined as a result of the delivery date adjustment with the customer.
[0049] Next, the flow of the delivery date adjustment control process will be described with reference to Figures 4 and 5. The delivery date adjustment control process means a control process performed to obtain a promised delivery date for a customer requested delivery date. First, as shown in Fig. 4, a customer orders a product by transmitting order information including the product, quantity, and requested delivery date from the customer terminal 50 to the first-layer delivery date management device 21 of the first-layer sales company (step T11). Then, the first-layer delivery date management device 21 starts the delivery date adjustment control process shown in Fig. 5. In Fig. 4, the delivery date reply procedure is the same even in a multi-layer configuration, so the procedure after the middle of the third layer is omitted.
[0050] The first-layer order receiving unit 111 in the first-layer delivery date management device 21 acquires the requested delivery date presented by the customer (step S101). The acquired requested delivery date corresponds to the customer requested delivery date shown in FIG. 3. The first-layer inventory confirmation unit 112 judges whether the sales company has product inventory that can meet the customer requested delivery date (step S102). If it is judged that the sales company does not have product inventory that can meet the customer requested delivery date (step S102: No), the first-layer plan creation unit 113 judges whether the sales company's inventory plan can meet the customer requested delivery date (step S103).
[0051] If it is determined that the sales company's inventory plan cannot meet the customer's requested delivery date (step S103: No), the first layer plan creation unit 113 creates a new plan (step S104). Specifically, in order to meet the customer's requested delivery date, the first layer plan creation unit 113 sets the customer's requested delivery date as the answered delivery date, and calculates a sales plan for the product to meet this answered delivery date by taking into account the necessary schedule including inspection. For example, for product A, if the customer's requested delivery date is 10 units on April 27, 2023, the answered delivery date is set to 10 units of the product on the same day, April 27, 2023. As a sales plan to meet this answered delivery date, the first layer plan creation unit 113 calculates the quantity and delivery date of the required product from the current product inventory, the required inspection period after the product is purchased, etc. If the result shows that 10 units of the product are required on April 24, 2023, the first plan creation unit 103 sets the requested delivery date 1 to 10 units on April 24, 2023. These obtained plans are sent to and stored in the overall management device 10 and the storage device 30. Note that in FIG. 4, the notation of the creation of a new plan, which corresponds to step S104, is omitted.
[0052] The first layer ordering unit 114 transmits the requested delivery date 1 to the next layer of the sales company, which is the first layer, in other words, the manufacturing company, which is the second layer (step S105). The second layer order receiving unit 121 in the second layer delivery date management device 22 acquires the requested delivery date 1 and accepts the order (step S106). After step S106, the process returns to step S102.
[0053] If it is determined in step S102 that the item is in stock (step S102: Yes), or if it is determined in step S103 that the item can be accommodated in the inventory plan (step S103: Yes), a promised delivery date setting process is executed (step S107).
[0054] The promised delivery date setting process (step S107) means a process for setting a promised delivery date between each layer or between the first layer and a customer. When the promised delivery date setting process starts, the process shown in FIG. 6 is executed. The plan creation unit 113, 123, 133, 143 in each layer obtains an answered delivery date (step S107a). Specifically, the plan creation unit 113, 123, 133, 143 in each layer obtains an answered delivery date for a requested delivery date from the previous layer or a customer based on the inventory status or plan of each layer. The plan creation unit 113, 123, 133, 143 in each layer sends the obtained answered delivery date to the delivery date management device 21, 22, 23 in the previous layer or the customer terminal 50 of the customer. As shown in FIG. 4, for example, in the second layer, when it is determined that there is stock or that it is possible to handle it by the inventory plan, the answered delivery date is obtained, and the obtained answered delivery date is set as the answered delivery date 1.
[0055] The plan creation units 113, 123, 133, 143 of each layer send the answered delivery date to the delivery date management devices 21, 22, 23 of the previous layer or the customer terminal 50 of the customer (step S107b). Based on the delivery date adjustment with the previous layer or the customer, the plan creation units 113, 123, 133, 143 of each layer set the promised delivery date (step S107c). The plan creation units 113, 123, 133, 143 of each layer store the obtained promised delivery date in the memory units 116, 126, 136, 146 of each layer, and also send it to the overall management device 10 and the storage device 30 to share it. The promised delivery date sent to the overall management device 10 is stored in the overall management device memory unit 18. After step S107c, the process proceeds to step S108.
[0056] The adjustment unit 11 in the overall management device 10 determines whether or not the promised delivery date with the customer has been set (step S108). Specifically, the adjustment unit 11 determines whether or not the promised delivery date with the customer has been set based on the promised delivery date stored in the overall management device storage unit 18.
[0057] If it is determined that the promised delivery date with the customer has not been set (step S108: No), the plan creation unit 113, 123, 133, 143 of each layer checks the delivery date from the lower layer (step S109). As a process leading up to the process of step S109, for example, in the second layer, in order to satisfy the requested delivery date 1 from the first layer, the second layer inventory confirmation unit 122 judges whether it is possible to meet the request with the product inventory on hand (step S102). If it is not possible to meet the request with the product inventory on hand (step S102: No), the product inventory plan is checked to determine whether it is possible to meet the request (step S103). If it is not possible to meet the request with the product inventory plan (step S103: No), the second layer plan creation unit 123 plans a new production date (step S104), and if there are any parts that are insufficient, the missing parts are ordered from the third layer delivery management device 23 of the parts company of the third layer with the requested delivery date 2 that meets the new production date (step S105). Thereafter, the second layer plan creation unit 123 sets the promised delivery date 2 in consultation with the third layer based on the responded delivery date 2 from the third layer delivery management device 23 of the third layer parts company. In this example, as the delivery date confirmation process in step S109, the second layer plan creation unit 123 confirms the responded delivery date 2, sets the promised delivery date 2 in consultation with the third layer with reference to the responded delivery date 2, sets a feasible manufacturing date from the set promised delivery date 2, and further sets the responded delivery date 1 to the first layer from the set manufacturing date.
[0058] Next, the plan creation units 113, 123, 133, and 143 of each layer respond with a delivery date (step S110). Specifically, the plan creation units 113, 123, 133, and 143 of each layer transmit the responded delivery date set in step S109 to the customer terminal 50 or the delivery date management devices 21, 22, and 23 of the upper layer. In the case of the above example, the second layer plan creation unit 123 transmits the responded delivery date 1 set in step S109 to the first layer delivery date management device 21 of the first layer. After step S110, the process returns to step S107.
[0059] In step S108, if it is determined that the promised delivery date with the customer has been set (step S108: Yes), the adjustment unit 11 in the overall management device 10 transmits delivery date related information including the requested delivery date, the answered delivery date, and the promised delivery date obtained in each layer to the user terminal 40. The user terminal 40 outputs the delivery date related information received from the overall management device 10 by screen display, audio output, etc. (step S111). Note that the performance management units 115, 125, 135, 145 of each layer tally up and manage the quantities, delivery dates, etc. of products, parts, etc. supplied from the next layer. For example, the first-layer performance management unit 115 tally up and manages the quantities, delivery dates, etc. of products supplied from a manufacturing company, which is the second layer.
[0060] Next, a case where there are multiple companies in the next layer (N+1) for the N layer will be described with reference to FIG. 7. In the example of FIG. 7, a manufacturing company in the second layer has multiple parts required for the production of products ordered by customers, and there are multiple parts companies in the third layer. The manufacturing company sets a requested delivery date 2, which is the delivery date of the parts, for example, taking into account the inspection period, in accordance with the production schedule of the products at the manufacturing company in order to fulfill the orders from the customers. This requested delivery date 2 is transmitted to all parts companies in the third layer for each part. In FIG. 7, the requested delivery date 2-1 and the requested delivery date 2-2 are shown as two companies in the third layer. The delivery date response procedure after receiving an order at the parts company in the third layer is as described in FIG. 4 and FIG. 5, and there are responded delivery date 2-1, responded delivery date 2-2, promised delivery date 2-1, and promised delivery date 2-2. The manufacturing company in the second layer receives the responded delivery dates from all parts companies in the third layer and sets the promised delivery date.
[0061] Next, the readjustment control process will be described with reference to FIG. 8. The readjustment control process refers to a control process for readjusting the delivery date when the set promised delivery date is later than the customer-requested delivery date. The readjustment of the delivery date is performed, for example, when the responded delivery date of the sales company, which is the first layer, is late and as a result the promised delivery date with the customer is later than the customer-requested delivery date, if it is possible to advance the delivery date. Also, when the responded delivery date and the promised delivery date are set according to the customer-requested delivery date presented by the customer to the sales company, if the customer requests to further advance the customer-requested delivery date, the set responded delivery date and the promised delivery date will be later than the new customer-requested delivery date. In such a case, readjustment of the delivery date to advance is performed.
[0062] The readjustment control process is started when a customer promised delivery date is set and the set promised delivery date is later than the customer requested delivery date. When a change in the plan occurs in each layer, the delivery date management device in that layer sends information about the change in the plan to the overall management device 10 and the storage device 30.
[0063] The adjustment unit 11 in the overall management device 10 identifies factors that cause the promised delivery date with the customer to be later than the customer-requested delivery date (step S201). Here, with reference to FIG. 9, an example of a method for identifying factors that cause the promised delivery date with the customer to be later than the customer-requested delivery date will be described. In the example shown in FIG. 9, the customer-requested delivery date is January 29, 2023: 10 units, while the answered delivery date and the promised delivery date are January 31, 2023: 10 units. Therefore, the adjustment unit 11 monitors whether or not it is possible to bring the delivery date forward. Note that FIG. 9 is an example in which multiple companies exist in the same layer, with the third layer being composed of two companies and the fourth layer being composed of three companies.
[0064] In the example of Figure 9, among the material companies in the fourth layer, material company 4-3, which is in the 4-3 layer, needs to set inventory plan 4-3 to 60 units on January 15, 2023 in order to meet the requested delivery date 3-2-3 from the third layer of 60 units on January 18, 2023, but this cannot be achieved, and inventory plan 4-3 becomes 60 units on January 17, 2023, the response delivery date 3-2-3 becomes 60 units on January 20, 2023, and the promised delivery date 3-2-3 becomes 60 units on January 20, 2023. This difference affects parts company 3-2 in the 3-2 layer, manufacturing company in the second layer, and even sales company in the first layer, and the response delivery date to the customer becomes 10 units on January 31, 2023, and the customer requested delivery date of 10 units on January 29, 2023 is not met. Therefore, it can be determined that the inventory plan 4-3 of the material company 4-3 is the cause of not being able to meet the delivery date requested by the customer. For this reason, attention is focused on the inventory plan 4-3 of the material company 4-3 in order to bring forward the delivery date promised to the customer and meet the delivery date requested by the customer.
[0065] The adjustment unit 11 compares the plan identified in step S201 as the cause of the delay with the plan before the change and judges whether the plan has been brought forward (step S202). For example, in the case of Fig. 9, the adjustment unit 11 judges whether the 4-3rd layer delivery date management device corresponding to the material supplier 4-3 has sent information indicating that the inventory plan 4-3 will be advanced, that is, information indicating that the required inventory quantity can be secured early, has been sent.
[0066] In step S202, if it is determined that the delivery date is to be brought forward (step S202: Yes), the adjustment unit 11 obtains a new reply delivery date to the customer and proposes sending the new date to the customer (step S203). In the example of FIG. 9, if the plan 4-3 is brought forward from January 17, 2023, 60 units, the adjustment unit 11 obtains a new reply delivery date to the customer based on the brought forward plan 4-3. If the brought forward plan 4-3 is January 15, 2023, 60 units, the new reply delivery date to the customer will be January 29, 2023, 10 units, and the customer's requested delivery date can be met.
[0067] The first layer delivery date management device 21 sends the new answered delivery date to the customer (step S204). After that, a new promised delivery date to the customer is decided based on the delivery date adjustment between the customer and the first layer. The adjustment unit 11 sets a new promised delivery date to the customer (step S205), and the answered delivery dates of each layer calculated when the new answered delivery date to the customer is obtained are treated as the new answered delivery date and the promised delivery date.
[0068] The adjustment unit 11 judges whether the new promised delivery date to the customer satisfies the customer-requested delivery date (step S206). If it is judged that the customer-requested delivery date is not satisfied (step S206: No), the process returns to step S201, and the adjustment unit 11 identifies factors that determine the new promised delivery date (step S201).
[0069] If it is determined in step S202 that the delivery has not been brought forward (step S202: No), or if it is determined in step S206 that the customer-requested delivery date is met (step S206: Yes), the process proceeds to step S207.
[0070] The adjustment unit 11 judges whether or not there is a delay with respect to the promised delivery date of each layer (step S207). Specifically, the adjustment unit 11 judges whether or not information indicating a delay in the plan of each layer has been sent by the delivery date management devices 21 to 24 of each layer.
[0071] For example, in FIG. 9, we focus on the plan 4-3 of the material company 4-3, which is the 4-3 layer and is the cause of the promised delivery date of 10 units on January 31, 2023. If a delay occurs in this plan 4-3, a delay occurs in the promised delivery date 3-2-3, and this delay causes a delay in the plan 3-2 of the parts company 3-2, which is the 3-2 layer, on January 21, 2023: 30 units. Ultimately, a delay occurs in the promised delivery date agreed upon between the sales company and the customer, which is the 1st layer, on January 31, 2023: 10 units. Therefore, at the stage when a delay occurs in the production plan 4-3, the 4-3 layer delivery date management device transmits information to the adjustment unit 11, and the adjustment unit 11 requests a new answer delivery date. Then, the new answer delivery date is transmitted from the 1st layer delivery date management device 21 to the customer terminal 50, thereby adjusting the promised delivery date with the customer.
[0072] If it is determined that there is a delay with respect to the promised delivery date of each tier (step S207: Yes), the process returns to step S203.
[0073] In step S207, if it is determined that there is no delay with respect to the promised delivery date of each layer (step S207: No), the process returns to step S201. Note that the adjustment unit 11 is an example of the adjustment means according to the present disclosure.
[0074] The hardware configuration of the first-layer delivery date management device 21 will be described with reference to Fig. 10. The hardware configuration of the delivery date management devices of other layers other than the first-layer delivery date management device and the overall management device 10 is similar, so the first-layer delivery date management device 21 will be described as a representative. As shown in Fig. 10, the first-layer delivery date management device 21 includes a temporary storage unit 171, a storage unit 172, a calculation unit 173, an input unit 174, a transmission / reception unit 175, and a display unit 176. The temporary storage unit 171, the storage unit 172, the input unit 174, the transmission / reception unit 175, and the display unit 176 are all connected to the calculation unit 173 via a BUS.
[0075] The calculation unit 173 includes, for example, a CPU (Central Processing Unit). The calculation unit 173 executes the processing of the first-layer schedule creation unit 113 of the first-layer due date management device 21 in accordance with the control program stored in the storage unit 172.
[0076] The temporary storage unit 171 includes, for example, a RAM (Random-Access Memory). The temporary storage unit 171 loads the control program stored in the storage unit 172 and is used as a working area for the calculation unit 173.
[0077] The storage unit 172 includes a non-volatile memory such as a flash memory, a hard disk, a DVD-RAM (Digital Versatile Disc - Random Access Memory), a DVD-RW (Digital Versatile Disc - ReWritable), etc. The storage unit 112 prestores a program for causing the calculation unit 173 to perform the processing of the first-layer delivery date management device 21, and also supplies the data stored by this program to the calculation unit 173 according to an instruction from the calculation unit 173, and stores the data supplied from the calculation unit 173.
[0078] The input unit 174 is an interface device that connects input devices such as a keyboard, a pointing device, and a voice input device to the BUS. Information input by the user is supplied to the calculation unit 173 via the input unit 174. In a configuration in which the user directly inputs performance information to the first-layer delivery date management device 21, the input unit 174 functions as the first-layer order receiving unit 111.
[0079] The transmitting / receiving unit 175 is a network termination device or a wireless communication device that connects to the network, and a serial interface or a LAN (Local Area Network) interface that connects to them. The transmitting / receiving unit 175 functions as the first layer order receiving unit 111 and the first layer ordering unit 114.
[0080] Display unit 176 is a display device such as an LCD (Liquid Crystal Display) or an organic EL (electroluminescence) display.
[0081] The processing of the first-layer order receiving unit 111, the first-layer inventory confirmation unit 112, the first-layer plan creation unit 113, the first-layer ordering unit 114, the first-layer result management unit 115, and the first-layer memory unit 116 of the first-layer delivery date management device 21 shown in FIG. 2 is executed by a control program using a temporary memory unit 171, a memory unit 172, a calculation unit 173, an input unit 174, a transmission / reception unit 175, a display unit 176, etc. as resources.
[0082] As described above, according to the delivery date management support system 100 of the first embodiment, in manufacturing and selling a product, an answered delivery date for a customer-requested delivery date is obtained in cooperation with all related companies. Also, if a promised delivery date determined based on the customer-requested delivery date and the answered delivery date is later than the customer-requested delivery date, a readjustment control process is performed to support readjustment of the delivery date. In the readjustment control process, if the process status of each layer allows for an advance, a new answered delivery date for the customer is obtained and presented to the customer, and a new promised delivery date is set. This improves customer satisfaction.
[0083] In addition, the readjustment control process is repeated to continue judging whether or not there is a delay in the promised delivery date for each layer, and if there is a delay, the factors affecting the delay are identified. Based on the company with the identified factors and the delayed plan, a new response delivery date for the customer is obtained and presented to the customer. Therefore, by detecting delays early and presenting the new response delivery date to the customer, it is possible to help avoid customer complaints about delivery delays.
[0084] (Modification) In this embodiment, the first to fourth layers are composed of companies, but the layers are not limited to companies and may be any type of organization. For example, the layers may be groups.
[0085] In the present embodiment, the overall management device 10, the first delivery date management device 21, the second delivery date management device 22, the third delivery date management device 23, and the fourth delivery date management device 24 are connected via a network, but the present disclosure is not limited to this. The overall management device 10 may also include the first delivery date management device 21, the second delivery date management device 22, the third delivery date management device 23, and the fourth delivery date management device 24. In addition to this, the overall management device 10 may also include a storage device 30.
[0086] In the embodiment, the system executes all the processes, but procedures such as user approval and settings may be involved. For example, a step of approval or editing by the person in charge may be provided before the answered delivery date is presented to a higher level or the customer. Also, when negotiating the promised delivery date based on the answered delivery date, the people in charge may negotiate with each other, and the result of the negotiation may be set as the promised delivery date.
[0087] In the embodiment, the delivery time for providing a product has been described, but the present disclosure is broadly applicable to delivery times for providing goods or services other than products.
[0088] Furthermore, the above hardware configuration and flowchart are merely examples and can be changed or modified as desired.
[0089] The core parts of the first-layer delivery date management device 21, such as the calculation unit 173, temporary storage unit 171, storage unit 172, input unit 174, transmission / reception unit 175, and display unit 176, can be realized by using a normal computer system, not a dedicated system. For example, the first-layer delivery date management device 21 that executes the above-mentioned processes may be configured by distributing a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc - Read Only Memory), or a DVD-ROM (Digital Versatile Disc - Read Only Memory) by storing the computer program for executing the above-mentioned operations, and installing the computer program on a computer. Alternatively, the first-layer delivery date management device 21 may be configured by storing the computer program in a storage device of a server device on a communication network, such as the Internet, and downloading the computer program by a normal computer system.
[0090] In addition, when the functions of the first layer delivery date management device 21 are realized by sharing the functions of an OS (Operating System) and an application program, or by cooperation between the OS and an application program, only the application program portion may be stored in a recording medium or storage device.
[0091] It is also possible to superimpose a computer program on a transport wave and provide it via a communication network. For example, the computer program may be posted on a bulletin board (BBS, Bulletin Board System) on the communication network and provided via the communication network. Then, the computer program may be started and executed under the control of the OS in the same way as other application programs, thereby enabling the above-mentioned processing to be performed.
[0092] Although the preferred embodiments have been described in detail above, the present invention is not limited to the above-described embodiments, and various modifications and substitutions can be made to the above-described embodiments without departing from the scope of the claims.
[0093] Various aspects of the present disclosure are summarized below as appendices.
[0094] (Appendix 1) A system for supporting management of delivery dates for the provision of goods or services, comprising: An order information storage means for storing order information; a delivery date information storage means for storing delivery date information indicating a promised delivery date agreed upon with a customer for an ordered product or service; A plan information storage means for storing plan information indicating a plurality of plans for providing the ordered goods or services; an adjustment means for proposing to adjust the corresponding promised delivery date when a time when an article or service can be provided is earlier than the promised delivery date due to a change in the plan indicated by the plan information stored in the plan information storage means, for an order whose promised delivery date is later than the customer requested delivery date included in the order information; A system comprising: (Appendix 2) the plan information storage means stores plan information for a plurality of plans for providing the goods or services; The adjustment means identifies, based on the plan information, which plan is causing the delivery date included in the order information to not be met. A delivery date management support system as described in Appendix 1. (Appendix 3) When the identified plan is changed, the adjustment means obtains a new delivery date for the customer included in the plan information and transmits the obtained delivery date to a terminal of the customer. A delivery date management support system as described in Appendix 2. (Appendix 4) when it is determined that the promised delivery date, which is set based on the obtained new delivery date for the customer, does not satisfy the delivery date included in the order information, the adjustment means further identifies the cause. A delivery date management support system as described in Appendix 3. (Appendix 5) storing delivery date information indicating a promised delivery date agreed upon with the customer regarding the time of delivery of the ordered goods or services; storing a plurality of plans for the provision of the ordered goods or services; For an order for which the promised delivery date is later than the customer-requested delivery date included in the order information, when a change in plan causes the time to provide the order to be earlier than the promised delivery date, propose adjusting the applicable promised delivery date with the customer. How to support delivery date management. (Appendix 6) On the computer, A process of storing delivery date information indicating a promised delivery date agreed upon with a customer regarding the timing of delivery of the ordered goods or services; storing a plurality of plans for the provision of the ordered goods or services; For an order whose promised delivery date is later than the customer-requested delivery date included in the order information, when a change in plan causes the time when the order can be provided to be earlier than the promised delivery date, a process of proposing to adjust the corresponding promised delivery date with the customer; A program that executes the following. [Explanation of symbols]
[0095] 10 Overall management device, 11 Adjustment unit, 18 Overall management device memory unit, 21 First layer delivery date management device, 22 Second layer delivery date management device, 23 Third layer delivery date management device, 24 Fourth layer delivery date management device, 30 Memory unit, 40 User terminal, 50 Customer terminal, 100 Delivery date management support system, 111 First layer order receiving unit, 112 First layer inventory confirmation unit, 113 First layer plan creation unit, 114 First layer ordering unit, 115 First layer performance management unit, 116 First layer memory unit, 121 Second layer order receiving unit, 122 Second layer inventory confirmation unit, 123 Second layer plan creation unit, 124 Second layer ordering unit, 125 Second layer performance management unit, 126 Second layer memory unit, 131 Third layer order receiving unit, 132 Third layer inventory confirmation unit, 133 Third layer plan creation unit, 134 Third layer ordering unit, 135 Third layer result management section, 136, third layer memory section, 141, fourth layer order receiving section, 142, fourth layer inventory confirmation section, 143, fourth layer plan creation section, 144, fourth layer ordering section, 145, fourth layer result management section, 146, fourth layer memory section, 171, temporary memory section, 172 memory section, 173 calculation section, 174 input section, 175 transmission / reception section, 176 display section, 301, result information memory section, 302, management information memory section.
Claims
1. A delivery date management support system for supporting management of delivery dates for the provision of goods or services, An order information storage means for storing order information; a delivery date information storage means for storing delivery date information indicating a promised delivery date agreed upon with a customer for an ordered product or service; A plan information storage means for storing plan information indicating a plurality of plans for providing the ordered goods or services; an adjustment means for proposing to adjust the corresponding promised delivery date when a time when an article or service can be provided is earlier than the promised delivery date due to a change in the plan indicated by the plan information stored in the plan information storage means, for an order whose promised delivery date is later than the customer requested delivery date included in the order information; A delivery date management support system equipped with:
2. the plan information storage means stores plan information for a plurality of plans for providing the goods or services; The adjustment means identifies, based on the plan information, which plan is causing the delivery date included in the order information to not be met.
2. The delivery date management support system according to claim 1.
3. When the identified plan is changed, the adjustment means obtains a new delivery date for the customer included in the plan information and transmits the obtained delivery date to a terminal of the customer.
3. A delivery date management support system according to claim 2.
4. when it is determined that the promised delivery date, which is set based on the obtained new delivery date for the customer, does not satisfy the delivery date included in the order information, the adjustment means further identifies the cause.
4. The delivery date management support system according to claim 3.
5. storing delivery date information indicating a promised delivery date agreed upon with the customer regarding the time of delivery of the ordered goods or services; storing a plurality of plans for the provision of the ordered goods or services; For an order for which the promised delivery date is later than the customer-requested delivery date included in the order information, when a change in plan causes the time to provide the order to be earlier than the promised delivery date, propose adjusting the applicable promised delivery date with the customer. How to support delivery date management.
6. On the computer, A process of storing delivery date information indicating a promised delivery date agreed upon with a customer regarding the timing of delivery of the ordered goods or services; storing a plurality of plans for the provision of the ordered goods or services; For an order whose promised delivery date is later than the customer-requested delivery date included in the order information, when a change in plan causes the time when the order can be provided to be earlier than the promised delivery date, a process of proposing to adjust the corresponding promised delivery date with the customer; A program that executes the following.
Citation Information
Patent Citations
Delivery time management system
JP2005122581A
