Procurement business assistance system, procurement business assistance device and procurement business assistance method

Abstract

An ordering plan including the best supplier that satisfies the purchase plan can be formulated. The purchase business support device has: a storage unit that stores order history information that registers past order history, delivery history information that registers past delivery history, and a purchase plan that registers the varieties to be purchased; a delivery expectation index calculation unit that uses the order history information to calculate a delivery expectation index that indicates the ease of delivery for each variety of each supplier; an ordering plan formulation unit that generates delivery expectation index histogram information that indicates the relationship between the delivery expectation index and the delivery rate calculated based on the delivery history information, calculates the delivery expectation index of the variety in the purchase plan, uses the delivery expectation index histogram information to determine the supplier with the highest delivery rate corresponding to the delivery expectation index, and generates ordering plan information including the variety in the purchase plan and the determined supplier; and a communication unit that sends predetermined screen information to the user terminal device, and the user terminal device has a display unit that displays the screen information.

Description

Technical Field

[0001] The present invention relates to a procurement business support system, a procurement business support device, and a procurement business support method. The present invention claims priority to Japanese Patent Application No. 2020-021450 filed on February 12, 2020, and the contents of the application are incorporated into the present application by reference in designated countries where the application is recognized as incorporated by reference. Background Art

[0002] Patent document 1 describes a method for monitoring the production capacity of suppliers, which states that "the production capacity of multiple suppliers is monitored by receiving performance data from at least one of the multiple suppliers, receiving forecast data from the manufacturer, and generating a production capacity risk assessment based on the received performance data and the received forecast data."

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: Japanese Patent Application Publication No. 2008-47117 Summary of the invention

[0006] Problems to be solved by the invention

[0007] Regarding the procurement business, an ordering plan with data on the target supplier, ordering items, delivery date, and quantity is prepared based on a procurement plan indicating the necessary date and quantity for each item according to a production plan or inventory plan. At this time, in order to ensure reliable delivery from the supplier, it is preferred to place an order as early as possible according to the previous procurement plan. However, in the supply chain, procurement plans change all the time as demand changes, so sometimes placing an order at an earlier time becomes a cause of overstocking or stockouts.

[0008] On the other hand, when placing an order based on a procurement plan with a period close to the required date in order to track demand changes, the supplier's preparation period becomes shorter, so the probability of delivery delay increases, which may become a major cause of stockouts. In other words, in order to balance tracking of demand changes and inventory reduction (or avoidance of stockouts), ordering operations that take into account both the supplier's delivery date compliance rate and procurement with a short delivery period are required.

[0009] Here, a technique for monitoring the production capacity of suppliers is disclosed in Patent Document 1. However, the technique in this document does not describe any aspect of considering both the supplier's delivery date compliance rate and procurement with a short delivery date.

[0010] The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to provide a procurement work support system capable of formulating an order plan including the best supplier that satisfies the procurement plan.

[0011] Means for solving problems

[0012] The present application includes a plurality of means for solving at least a part of the above-mentioned problems, and examples thereof are as follows. A purchasing business support system according to one aspect of the present invention for solving the above-mentioned problems is a purchasing business support system having a purchasing business support device and a user terminal device, wherein the purchasing business support device has: a storage unit storing order history information registering past order history, delivery history information registering past delivery history, and a purchasing plan registering items to be purchased; a delivery expectation index calculation unit calculating a delivery expectation index indicating the degree of difficulty of delivery for each item of each supplier using the order history information; an order plan formulation unit generating delivery expectation index histogram information indicating the relationship between the delivery expectation index and the delivery rate calculated based on the delivery history information, calculating the delivery expectation index of the item in the purchasing plan, using the delivery expectation index histogram information, determining the supplier having the highest delivery rate corresponding to the delivery expectation index, and generating order plan information including the item in the purchasing plan and the determined supplier; and a communication unit transmitting predetermined screen information to the user terminal device, wherein the user terminal device has: a display unit displaying the screen information.

[0013] Effects of the Invention

[0014] According to the procurement work support system of the present invention, it is possible to formulate an order plan including the best supplier that satisfies the procurement plan. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a diagram showing an example of a schematic configuration of the procurement work support system according to the first embodiment.

[0016] Figure 2 This is a diagram showing an example of the data structure of supplier master information.

[0017] Figure 3 This is a diagram showing an example of the data structure of order history information.

[0018] Figure 4 This is a diagram showing an example of the data structure of the delivery history information.

[0019] Figure 5 This is information indicating an example of the data structure of the delivery expectation index information.

[0020] Figure 6This is information indicating an example of the data structure of the delivery expectation index histogram information.

[0021] Figure 7 This is a diagram showing an example of the data structure of procurement plan information.

[0022] Figure 8 This is a diagram showing an example of the data structure of order plan information.

[0023] Fig. 9 This is a flowchart showing an example of order plan creation processing.

[0024] Fig.10 This is a diagram showing an example of a delivery expectation index histogram.

[0025] Fig.11 This is a diagram showing an example of an order plan confirmation screen displayed on the user terminal device.

[0026] Fig.12 This is a diagram showing an example of a schematic configuration of a procurement work support system according to the second embodiment.

[0027] Fig.13 This is a diagram showing an example of the data structure of business logic information.

[0028] Fig.14 This is a flowchart showing an example of order plan creation processing according to the second embodiment.

[0029] Fig.15 This is a diagram showing an example of the hardware configuration of the procurement work support device.

[0030] Fig.16 This is a diagram showing an example of the hardware configuration of a user terminal device. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present invention will be described using the drawings.

[0032] <First Embodiment>

[0033] Figure 1 1 is a diagram showing an example of a schematic structure of a procurement business support system 1000 according to the present embodiment. The procurement business support system 1000 includes a procurement business support device 100 and a user terminal device 200. The procurement business support device 100 and the user terminal device 200 are connected to each other via a network N so as to be able to communicate with each other. The network N is, for example, a public network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network).

[0034] The procurement support device 100 is a device that performs various calculations related to procurement. Specifically, the procurement support device 100 generates various information used in procurement, such as index information indicating the difficulty of delivery (in other words, the ease of delivery or ordering), and histogram information using the index information.

[0035] Specifically, the procurement business support device 100 includes a computing unit 110, a storage unit 120, and a communication unit 130. In addition, the computing unit 110 includes an information reading unit 111, a delivery expectation index calculation unit 112, an order plan formulation unit 113, a display information generation unit 114, and a business logic execution unit 115. In addition, the business logic execution unit 115 is one of the functional units in the procurement business support device 100 of the second embodiment described later, and therefore, a detailed description thereof is omitted in this embodiment.

[0036] The information reading unit 111 is a functional unit that reads information stored in the storage unit 120. Specifically, the information reading unit 111 reads various information necessary for the calculation unit 110 to execute a process from the storage unit 120.

[0037] The delivery expectation index calculation unit 112 is a functional unit for calculating the delivery expectation index. Specifically, the delivery expectation index calculation unit 112 uses the predetermined information stored in the storage unit 120 (for example, the supplier master information 121 described later, etc.) to calculate the delivery expectation index indicating the difficulty of delivery, and generates delivery expectation index information in which the calculated value of the delivery expectation index is registered.

[0038] In addition, the difficulty of delivery refers to whether the ordered quantity is easy to deliver within the required delivery period. The value of the delivery expectation index is calculated based on the deviation in the number of days between the order date and the required delivery period (the interval in the number of days) and the change in the last order quantity to the current order quantity.

[0039] The order plan formulation unit 113 is a functional unit for formulating an order plan. Specifically, the order plan formulation unit 113 generates order plan information using predetermined information (e.g., the delivery expectation index histogram information and the procurement plan information described later). More specifically, the order plan formulation unit 113 generates the delivery expectation index histogram information using the delivery expectation index information generated by the delivery expectation index calculation unit 112. In addition, the order plan formulation unit 113 calculates the delivery expectation index for each variety involved in the procurement plan, and determines a supplier with a high delivery rate (easy to comply with delivery) corresponding to the range of the delivery expectation index histogram including the value of the calculated delivery expectation index. In addition, the order plan formulation unit 113 generates order plan information including predetermined information such as the determined supplier and the ordered variety.

[0040] The display information generation unit 114 is a functional unit that generates screen information displayed on the display device. Specifically, the display information generation unit 114 generates screen information of an order plan confirmation screen displayed on the display device of the user terminal device 200.

[0041] The storage unit 120 is a functional unit for storing various information. Specifically, the storage unit 120 stores supplier master information 121, order history information 122, delivery history information 123, and procurement plan information 126. In addition, the storage unit 120 stores delivery expectation index information 124 generated by the delivery expectation index calculation unit 112. In addition, the storage unit 120 stores delivery expectation index histogram information 125 and order plan information 127 generated by the order plan formulation unit 113. In addition, the storage unit 120 stores business logic information 128, but such information is information used by the business logic execution unit 115 of the procurement business support device 100 of the second embodiment described later, and therefore, detailed description is omitted in this embodiment.

[0042] Figure 2 1 is a diagram showing an example of the data structure of the supplier master information 121. The supplier master information 121 is information related to a supplier or a product handled by the supplier. As shown in the figure, the supplier master information 121 has records in which supplier ID 121a, supplier name 121b, product ID 121c, product name 121d, purchase LT (lead time) 121e, and lot size 121f are associated with each other.

[0043] The supplier ID 121a is information that uniquely identifies each supplier. The supplier name 121b is information that indicates the name of the supplier. The product ID 121c is information that uniquely identifies the product to be purchased. The product name 121d is information that indicates the name of the product. The procurement LT (lead time) 121e is information that indicates the time taken from ordering the corresponding product to delivery. The batch size 121f is information that indicates the minimum order unit of the corresponding product.

[0044] Figure 3 1 is a diagram showing an example of the data structure of the order history information 122. The order history information 122 is information related to suppliers and products that the procurement source company has ordered in the past. As shown in the figure, the order history information 122 has records that associate order date 122a, order ID 122b, supplier ID 122c, product ID 122d, required delivery date 122e, and order quantity 122f.

[0045] The order date 122a is information indicating the date on which the corresponding product was ordered from the supplier. The order ID 122b is information uniquely identifying the order content. The supplier ID 122c and the product ID 122d are information common to the supplier ID 121a and the product ID 121c of the supplier master information 121, respectively. The required delivery date 122e is information indicating the required delivery date for the supplier for the corresponding product. The order quantity 122f is information indicating the quantity ordered for the corresponding product.

[0046] Figure 4 1 is a diagram showing an example of the data structure of the delivery history information 123. The delivery history information 123 is information showing the delivery history of the ordered items. As shown in the figure, the delivery history information 123 has records in which the delivery ID 123a, the order ID 123b, the supplier ID 123c, the item ID 123d, the required delivery date 123e, the delivery date 123f, the order quantity 123g, and the delivery quantity 123h are associated with each other.

[0047] Delivery ID 123a is information that uniquely identifies the content of delivery. Order ID 123b, supplier ID 123c, and variety ID 123d are information common to order ID 122b, supplier ID 122c, and variety ID 122d of order history information 122, respectively. In addition, required delivery date 123e and order quantity 123g are information common to required delivery date 122e and order quantity 122f of order history information 122, respectively. Delivery date 123f is information indicating the date on which the corresponding variety is delivered from the supplier. Delivery quantity 123h is information indicating the quantity actually delivered for the corresponding variety. In addition, in the delivery date, even if the delivery is made before the required delivery date, the date that is the same as the required delivery date is registered. That is, for example, even if the required delivery date is "2018 / 6 / 10" and the actual delivery date is "2018 / 6 / 8", the delivery date is registered as the same date as the required delivery date, i.e., "2018 / 6 / 10".

[0048] Figure 5 This is information showing an example of the data structure of the delivery expectation index information 124. The delivery expectation index information 124 is information including an index showing the difficulty of delivery. As shown in the figure, the delivery expectation index information 124 has a record in which an order ID 124a, a delivery expectation index 124b, and a delivery rate 124c are associated with each other. In addition, the delivery expectation index information 124 is generated for each combination of a supplier and a product specified by the order ID.

[0049] The order ID 124a is information common to the order ID 122b of the order history information 122. The delivery expectation index 124b is information indicating the difficulty of delivery. In this example, it is shown that the larger the value of the delivery expectation index is, the easier it is to achieve delivery for the combination of the supplier and the product specified by the corresponding order ID. The delivery rate 124c is information indicating the ratio of the delivery quantity delivered on the required delivery date to the order quantity.

[0050] In addition, the delivery expectation index information 124 is generated by the delivery expectation index calculation unit 112 .

[0051] Figure 6 This is information showing an example of the data structure of the delivery expectation index histogram information 125. The delivery expectation index histogram information 125 is information for generating a delivery expectation index histogram. As shown in the figure, the delivery expectation index histogram information 125 has records that associate the product ID 125a, the supplier ID 125b, the delivery expectation index lower limit 125c, the delivery expectation index upper limit 125d, the frequency 125e, and the average delivery rate 125f.

[0052] Product ID 125a and supplier ID 125b are information common to product ID 121c and supplier ID 121a of supplier master information 121, respectively. Delivery expectation index lower limit 125c and delivery expectation index upper limit 125d are information indicating the upper limit and lower limit of each range when the possible range of the delivery expectation index is divided into a predetermined range width (for example, every 100). Frequency 125e is information indicating the number of order IDs 124a in delivery expectation index information 124 corresponding to the delivery expectation index included in the corresponding range width. Average delivery rate 125f is information indicating the average value of delivery rate 124c in delivery expectation index information 124 corresponding to the delivery expectation index included in the corresponding range width.

[0053] In addition, the delivery expectation index histogram information 125 is generated by the order planning unit 113 .

[0054] Figure 7 1 is a diagram showing an example of the data structure of the procurement plan information 126. The procurement plan information 126 is information related to the items to be procured. Specifically, the procurement plan information 126 has a record in which the item ID 126a, the required date 126b, and the quantity 126c are associated with each other.

[0055] The item ID 126a is information common to the item ID 121c of the supplier master information 121. The required date 126b is information indicating the purchase deadline of the corresponding item, that is, the required delivery date. The quantity 126c is information indicating the purchase quantity of the corresponding item.

[0056] Figure 8 1 is a diagram showing an example of the data structure of the order plan information 127. The order plan information 127 is information related to the order plan of the purchase items. As shown in the figure, the order plan information 127 has a record in which a supplier ID 127a, an item ID 127b, a required delivery date 127c, a quantity 127d, and an average delivery rate 127e are associated with each other.

[0057] The supplier ID 127a and the product ID 127b are information common to the supplier ID 121a and the product ID 121c of the supplier master information 121, respectively. The required delivery period 127c is information common to the required delivery period 122e of the order history information 122, and is equivalent to the required date 126b of the procurement plan information 126. The quantity 127d is information common to the quantity 126c of the procurement plan information 126. The average delivery rate 127e is information indicating the average delivery rate of the corresponding supplier and product.

[0058] return Figure 1 The communication unit 130 is a functional unit that performs information communication with an external device. Specifically, for example, the communication unit 130 obtains a generation instruction of the ordering plan information 127, a display request of the ordering plan confirmation screen, etc. from the user terminal device 200. In addition, the communication unit 130 sends screen information of the ordering plan confirmation screen to the user terminal device 200.

[0059] The functional configuration of the procurement work support device 100 has been described above.

[0060] Next, use Figure 1 An example of the functional configuration of the user terminal device 200 is described. The user terminal device 200 is a device for procurement work. For example, the user terminal device 200 instructs the procurement work support device 100 to generate an order plan, or displays information related to the order plan generated by the procurement work support device 100.

[0061] like Figure 1 As shown, the user terminal device 200 includes an input accepting unit 201 , a display unit 202 , a storage unit 203 , and a communication unit 204 .

[0062] The input accepting unit 201 is a functional unit that accepts, from the user, an instruction to generate the order plan information 127, a request to display an order plan confirmation screen, and the like.

[0063] The display unit 202 is a functional unit for displaying screen information on the display device of the user terminal device 200. For example, the display unit 202 generates screen information for accepting a generation instruction of the order plan information 127 from the user, and displays it on the display device. In addition, the display unit 202 displays screen information of the order plan confirmation screen obtained from the procurement business support device 100 on the display device.

[0064] The storage unit 203 is a functional unit that stores predetermined information related to the processing of the user terminal device 200 .

[0065] The communication unit 204 is a functional unit for performing information communication with an external device. Specifically, the communication unit 204 sends a generation instruction of the order plan information 127 to the procurement work support device 100. In addition, the communication unit 204 obtains screen information of the order plan confirmation screen from the procurement work support device 100.

[0066] The functional configuration of the user terminal device 200 has been described above.

[0067] [Description of the action]

[0068] Next, the order plan generation process executed by the procurement work support device 100 will be described.

[0069] Fig. 9 2 is a flowchart showing an example of order plan generation processing. Such processing is executed by the procurement work support device 100 that has received an instruction to generate the order plan information 127 from the user terminal device 200, for example.

[0070] At the start of the process, the information reading unit 111 reads various information required for generating an order plan from the storage unit 120 in the process of step S100 to step S102. Specifically, the information reading unit 111 reads the supplier master information 121 in the process of step S100, reads the order history information 122 in the process of step S101, and reads the delivery history information 123 in the process of step S102.

[0071] Next, the delivery expectation index calculation unit 112 calculates the delivery expectation index (step S103). Specifically, the delivery expectation index calculation unit 112 uses the supplier master information 121, order history information 122, and delivery history information 123 read by the information reading unit 111 to calculate the delivery expectation index for orders in the same supplier and product combination.

[0072] More specifically, the delivery expectation index calculation unit 112 calculates the delivery expectation index by using a predetermined calculation formula of an interval index and a quantity ratio index, wherein the interval index represents the margin during the period from ordering to the required delivery period, and the quantity ratio index represents the ratio of the change from the most recent order quantity to the current order quantity.

[0073] The calculation of the delivery expectation index is described below by taking the order ID "P001" in the combination of the supplier "SUP001" and the item "ITM-A" as an example.

[0074] First, the delivery expectation index calculation unit 112 calculates the interval index. Specifically, the delivery expectation index calculation unit 112 calculates the number of days "102 days" obtained by subtracting the order date "2018 / 3 / 1" from the required delivery date "2018 / 6 / 10" of the record 122g corresponding to the order ID "P001", the supplier "SUP001" and the product "ITM-A" in the order history information 122.

[0075] Next, the delivery expectation index calculation unit 112 calculates the number of days obtained by subtracting the lead time of such an item from the calculated number of days. Figure 2 In the supplier master information 121, the purchase LT of the item "ITM-A" of the supplier "SUP001" is "30 days", so the delivery expectation index calculation unit 112 calculates "72 days" by subtracting "30 days" from "102 days". Then, the delivery expectation index calculation unit 112 temporarily stores the calculated number of days ("72 days") as the value of the interval index of the order ID "P001" in the storage unit 120.

[0076] Next, the delivery expectation index calculation unit 112 calculates the quantity ratio index. Specifically, the delivery expectation index calculation unit 112 uses the order history information 122 to calculate the ratio of the change from the most recent order quantity (order quantity "50" of order ID "P000") to the current order quantity "10" (order quantity "10" of order ID "P001") for the same product ("ITM-A") of the same supplier ("SUP001") = 10 / 50. In addition, when the current order quantity is less than the most recent order quantity, the delivery expectation index calculation unit 112 multiplies it by "-1" to give a negative sign, and does not multiply it by "-1" when the order quantity increases. In this example, the delivery expectation index calculation unit 112 calculates 10 / 50×(-1)=-0.2 as the quantity ratio index and temporarily stores it in the storage unit 120.

[0077] Next, the delivery expectation index calculation unit 112 calculates the delivery expectation index in the order ID "P001" for the same product ("ITM-A") of the same supplier ("SUP001") using the following calculation formula.

[0078] Calculation formula: Delivery expectation index = (value of interval index) / (value of quantity ratio index)

[0079] When the values ​​of the interval index and the quantity ratio index in this example are substituted into the above calculation formula, the delivery expectation index of the order ID "P001" is 72 / -0.2=-360.

[0080] In addition, the calculation formula used to calculate the delivery expectation index is not particularly limited, as long as it takes into account the margin from the order to the required delivery date and the relationship between the change in the most recent order quantity to the current order quantity for the same supplier and the same product.

[0081] In addition, the delivery expectation index calculation unit 112 calculates the delivery rate of such order ID "P001". Specifically, the delivery expectation index calculation unit 112 identifies the record 123i in which the required delivery date 123e and the delivery date 123f coincide with each other among the records (records 123i and 123j) of the corresponding order ID registered in the delivery history information 123. In addition, the delivery expectation index calculation unit 112 calculates the ratio of the delivery quantity "3" to the order quantity "10" of the identified record 123i as the delivery rate of order ID "P001".

[0082] In addition, the delivery expectation index calculation unit 112 calculates the delivery expectation index and the delivery rate for each order in the same supplier and product combination by the same method as described above, and generates the delivery expectation index information 124 in which the order ID is registered in association with the order ID.

[0083] Next, the order planning unit 113 creates a delivery expectation index histogram (step S104). Specifically, the order planning unit 113 generates the delivery expectation index histogram information 125 using the delivery expectation index information 124, and creates a delivery expectation index histogram for the same supplier and product combination using the delivery expectation index histogram information 125.

[0084] First, the generation of the delivery expectation index histogram information 125 will be described. The order planning unit 113 extracts the order ID from the delivery expectation index information 124 and specifies the supplier ID and item ID associated with the extracted order ID from the order history information 122 .

[0085] In addition, the order planning section 113 divides the possible range of the delivery expectation index in the delivery expectation index information 124 into a predetermined range width, and calculates the delivery expectation index lower limit and the delivery expectation index upper limit. More specifically, the order planning section 113 sets the range between the minimum value and the maximum value of the delivery expectation index in the delivery expectation index information 124 as a possible range, and divides such a range into a predetermined range width (for example, every 100).

[0086] For example, in Figure 5 In the delivery expectation index information 124, the range of the delivery expectation index is between the minimum value "-360" and the maximum value "450". In addition, when the range is divided into a range width of "100", the range widths of the delivery expectation index lower limit 125c and the delivery expectation index upper limit 125d are respectively "-399" to "-300", "-299" to "-200", "-199" to "-100", "-99" to "0", "1" to "100", "101" to "200", and "201" to "300".

[0087] Furthermore, the order planning section 113 calculates the frequency 125e. Specifically, the order planning section 113 counts the number of order IDs 124a of the delivery expectation index information 124 corresponding to the delivery expectation index included between the calculated delivery expectation index lower limit 125c and the delivery expectation index upper limit 125d as the frequency 125e.

[0088] For example, in Figure 5 In the delivery expectation index information 124, the delivery expectation indexes of the three order IDs ("P001", "P100" and "P120") converge to between "-399" and "-300". Therefore, the order planning unit 113 registers the value "3" obtained by adding the number of order IDs ("P001", "P100" and "P120") in the frequency 125e of the record corresponding to the delivery expectation index lower limit 125c and the delivery expectation index upper limit 125d of such a range width.

[0089] In addition, the order planning unit 113 calculates the average delivery rate 125f. Specifically, the order planning unit 113 adds the delivery rates 124c of the order IDs of the delivery expectation index information 124 corresponding to the delivery expectation index included in each range width of the delivery expectation index lower limit 125c and the delivery expectation index upper limit 125d, and divides the sum by the number of frequencies 125e, thereby calculating the average delivery rate 125f for each range width.

[0090] For example, in Figure 5As described above, in the delivery expectation index information 124, the values ​​of the delivery expectation index in the three order IDs ("P001", "P100" and "P120") converge between "-399" and "-300". Therefore, the order planning unit 113 adds the delivery rates "30", "40" and "50" corresponding to these order IDs, respectively, and divides the sum by the frequency "3", thereby calculating the average delivery rate = "40".

[0091] In addition, the order planning section 113 calculates the frequency 125e and the average delivery rate 125f included in each range width of the delivery expectation index lower limit 125c and the delivery expectation index upper limit 125d for the same combination of supplier and product by the same method as described above. In addition, the order planning section 113 generates the delivery expectation index histogram information 125 in which these information are registered.

[0092] Furthermore, the order planning unit 113 creates a delivery expectation index histogram using the generated delivery expectation index histogram information 125 .

[0093] Fig.10 This is a diagram showing an example of a delivery expectation index histogram. The delivery expectation index histogram is a frequency distribution diagram showing the relationship between the delivery expectation index and the average delivery rate at that time. Specifically, in the delivery expectation index histogram, the vertical axis corresponds to the average delivery rate [%], and the horizontal axis corresponds to the delivery expectation index.

[0094] The bar graph visually represents the information in each record of the delivery expectation index histogram information 125. That is, the bar graph has a range width of the delivery expectation index lower limit 125c and upper limit 125d of each record, and the size of the vertical axis represents the height of the average delivery rate 125f of the corresponding record.

[0095] Next, the information reading unit 111 reads the procurement plan information 126 from the storage unit 120 (step S105 ).

[0096] Next, the order planning unit 113 executes plan allocation (step S106 ). Specifically, the order planning unit 113 generates production plan information using the supplier master information 121 , order history information 122 , delivery history information 123 , procurement plan information 126 , and delivery expectation index histogram information 125 .

[0097] First, the order planning unit 113 calculates the delivery expectation index of the product ID 126a included in the predetermined record of the procurement plan information 126 via the delivery expectation index calculation unit 112. Specifically, the delivery expectation index calculation unit 112 extracts the product ID, required date, and quantity included in such a record. In addition, the delivery expectation index calculation unit 112 determines the supplier who can purchase the product with such a product ID and the purchase LT of each supplier based on the supplier master information 121.

[0098] The delivery expectation index calculation unit 112 uses the extracted necessary date as the required delivery date and the scheduled date such as the processing day or a few days later as the order date, and calculates the delivery expectation index for each supplier in the item of such record in the same manner as described above.

[0099] Here, Figure 7 First, the delivery expectation index calculation unit 112 extracts the product ID "ITM-A", the required date "2018 / 7 / 10", and the quantity "70" from the procurement plan information 126, and sets the scheduled date "2018 / 10 / 1" as the order date.

[0100] Furthermore, the delivery expectation index calculation unit 112 specifies suppliers (“A Industry” and “B Seiko”) that can procure item ID “ITM-A” and the procurement LT for each supplier (“30 days” and “7 days”) based on the supplier master information 121 .

[0101] In addition, the delivery expectation index calculation unit 112 calculates the interval index and the quantity ratio index using the order history information 122. Specifically, the delivery expectation index calculation unit 112 calculates the interval index for each supplier by subtracting the purchase LT ("30 days" and "7 days") of the product ID "ITM-A" from the number of days obtained by subtracting the scheduled date "2018 / 10 / 1" from the necessary date "2018 / 7 / 10".

[0102] In addition, the order planning unit 113 calculates the change between the most recent order quantity and the current order quantity of the product ID "ITM-A" in the same manner as described above using the order history information 122. The most recent order quantity of the product ID "ITM-A" is "100" on "2018 / 6 / 20", so the delivery expectation index calculation unit 112 calculates 70 / 100×(-1)=-0.7.

[0103] In addition, the delivery expectation index calculation unit 112 calculates the delivery expectation index for each supplier using the calculated interval index and quantity ratio index and the above-mentioned calculation formula.

[0104] Next, the order planning section 113 identifies a record of a combination of the same item ID and supplier as the calculated delivery expectation index based on the delivery expectation index histogram information 125. In addition, the order planning section 113 generates a delivery expectation index histogram using the identified records of the delivery expectation index histogram information 125, and identifies an average delivery rate corresponding to a range width including the calculated delivery expectation index.

[0105] The order planning section 113 determines the average delivery rate of the product ID for each supplier and selects the supplier with the highest average delivery rate. If there are multiple suppliers with the same average delivery rate, the order planning section 113 may select the supplier with the shorter purchase LT.

[0106] Furthermore, the order planning section 113 performs the same processing on all records of the procurement plan information 126, and specifies a supplier having a high average delivery rate for each item of the procurement target.

[0107] In addition, the ordering plan formulation unit 113 generates ordering plan information 127 that corresponds the product ID of the procurement plan information 126, the required delivery date equivalent to the necessary day, the quantity, the supplier ID of the supplier determined by the product ID, and the average delivery rate of such suppliers and products, and stores it in the storage unit 120, thereby completing the processing of this flow.

[0108] In addition, the ordering plan formulation unit 113 generates screen information (e.g., screen information of an ordering plan confirmation screen described later) for displaying the generated ordering plan information 127 on the user terminal device 200 via the display information generation unit 114. In addition, the ordering plan formulation unit 113 transmits the generated screen information to the user terminal device 200 via the communication unit 130.

[0109] Fig.11 1 is a diagram showing an example of an order plan confirmation screen 300 displayed on the user terminal device 200. On such a screen 300, a supplier 301, an item 302, an estimated delivery date compliance rate (overall) 303, and recommended order information 304 are displayed.

[0110] Here, the recommended order information 304 has a table 305 that associates the recommended order date, the required delivery date, the quantity, and the estimated delivery date compliance rate. The recommended order date of each record is a date obtained by subtracting the procurement lead time of the supplier 301 and the item 302 selected in such a screen 300 from the required delivery date. In addition, the recommended order date may be, for example, the execution date of the order plan formulation process (for example, the date on which the process of step S106 is executed or the scheduled date described above). In addition, the required delivery date and quantity of each record correspond to the required delivery date 127c and the quantity 127d of the order plan information 127, respectively. In addition, the recommended delivery date compliance rate of each record corresponds to the average delivery rate determined based on the delivery expectation index histogram (the average delivery rate 127e registered in the order plan information 127). In addition, the recommended delivery date compliance rate (overall) 303 is the average value of each record of the recommended delivery date compliance rate.

[0111] Input accepting unit 201 of user terminal device 200 accepts user selection of supplier 301 and item 302 from pull-down buttons in order plan confirmation screen 300 via an input device. In this case, display unit 202 displays recommended order information 304 and estimated delivery date compliance rate (overall) 303 corresponding to the selected supplier or item.

[0112] In addition, the structure of the screen 300 displayed by the user terminal device 200 is not particularly limited to Fig.11 For example, the screen information may display all the contents of the order plan information 127. Alternatively, based on the order plan information 127, only suppliers with a high average delivery rate may be displayed for each product.

[0113] Since such a screen 300 is displayed on the user terminal device 200, even when there are multiple suppliers to order from and multiple items are handled, the user can confirm a supplier with a higher delivery rate and place an order on a date closer to the required date of the procurement plan.

[0114] The above is a description of the procurement support system 1000 of the first embodiment. According to such a procurement support system 1000, a supplier with a high delivery rate can be determined for a procurement item based on a delivery expectation index that takes into account the margin of the interval between the order date and the required delivery date and the change in the order quantity. Therefore, the best supplier that meets the procurement plan can be selected.

[0115] <Second Embodiment>

[0116] The procurement work support system 2000 according to the second embodiment regenerates the procurement plan information 126 in consideration of the market situation of the supply chain, and performs order plan creation processing using the regenerated procurement plan information 126 . Fig.12 1 is a diagram showing an example of a schematic structure of a procurement business support system 2000 according to the second embodiment. As shown in the figure, the procurement business support system 2000 includes a procurement business support device 100, a supply chain business support device 400, and a user terminal device 200. In addition, the following description will focus on the structure that is different from the procurement business support system 1000 according to the first embodiment, and the description of the same structure will be omitted.

[0117] The supply chain business support device 400 is a device that processes information related to various business in the supply chain in consideration of the supply chain market conditions. For example, the supply chain business support device 400 generates business logic information that is most suitable for generating the procurement plan information 126 in consideration of the supply chain market conditions, and sends it to the procurement business support device 100.

[0118] Specifically, the supply chain business support device 400 includes a business logic generation unit 401, supplier master information 121, and business logic information 128. The business logic generation unit 401 generates business logic information 128 that is most suitable for generating procurement plan information 126 using predetermined information such as the supplier master information 121. In addition, the technology disclosed in Japanese Patent Application Laid-Open No. 2018-063598 is used for the generation method of such business logic information 128. The business logic generation unit 401 sends the generated business logic information 128 to the procurement business support device 100 via a communication unit (not shown).

[0119] Fig.13 128a, a logic name 128b, and a usage flag 128c. In addition, the business logic ID 128a is information that uniquely identifies the type of business logic. The logic name 128b is information indicating the name of the business logic determined by the corresponding business logic ID 128a. In addition, in the business logic, there are business logics for various ordering methods such as "periodic ordering method", "quantitative ordering method", and "quantitative maintenance method". The usage flag 128c is flag information that indicates whether it is a business logic to be used when the market conditions of the supply chain are taken into consideration, with "0" or "1". Corresponding to the market conditions of the supply chain, the business logic to be used is associated with "1".

[0120] return Fig.12The operation unit 110 of the procurement business support device 100 further includes a business logic execution unit 115 for regenerating the procurement plan information 126 using the business logic information 128 obtained from the supply chain business support device 400. In addition, the business logic information 128 obtained from the supply chain business support device 400 is stored in the storage unit 120. In addition, the procurement business support device 100 and the supply chain business support device 400 can be connected to each other by wired communication or wireless communication via a network such as a communication bus or the Internet.

[0121] Fig.14 This is a flowchart showing an example of the order plan generation process executed by the procurement operation support device 100 of the present embodiment. In addition, step S203 corresponds to steps S100 to S106 in the order plan generation process of the first embodiment, and therefore, detailed description thereof is omitted.

[0122] When such processing starts, the information reading unit 111 reads the business logic information 128 from the storage unit 120 (step S201). Next, the business logic execution unit 115 uses the read business logic information 128 to execute the business logic, and uses the procurement plan information 126 pre-stored in the storage unit 120 to regenerate new procurement plan information 126 that takes into account the market conditions of the supply chain (step S202). Specifically, the business logic execution unit 115 determines the business logic that corresponds to the usage flag of the business logic information 128 and "1" based on the business logic ID 128a or the logic name 128b. Fig.13 In the example, the usage flag corresponding to the business logic of the periodic ordering method is "1", so the business logic execution unit 115 regenerates the procurement plan information 126 according to the periodic ordering method.

[0123] Specifically, the business logic execution unit 115 changes the required date of the procurement plan information 126 to the latest predetermined regular delivery date (for example, 2018 / 7 / 15). In addition, the business logic execution unit 115 changes the quantity of the same item to the added quantity.

[0124] Next, the order plan formulation unit 113 of the procurement work support device 100 executes the process of step S203 (the above-mentioned steps S100 to S106 ) using the procurement plan information 126 regenerated in this way.

[0125] The above is a description of the procurement business support system 2000 of the second embodiment. According to such a procurement business support system 2000, the procurement plan information 126 that takes into account the market conditions of the supply chain can be regenerated. In particular, in the procurement business support system 2000 of this embodiment, the supply chain business support device 400 determines the best business logic corresponding to the market conditions of the supply chain. Therefore, for example, the procurement plan information 126 can be regenerated using the business logic that takes into account the constraints of the warehouse in the supply chain, the transportation lead time of the goods, etc., so that an ordering plan that is more in line with the actual situation can be formulated.

[0126] Hereinafter, an example of the hardware configuration of the procurement work support device 100 , the user terminal device 200 , and the supply chain work support device 400 will be described.

[0127] Fig.15 1 is a diagram showing an example of the hardware configuration of the procurement work support device 100. The procurement work support device 100 is implemented by, for example, a high-performance information processing device such as a server device.

[0128] As shown in the figure, the procurement work support device 100 includes a computing device 501, a main storage device 502, an external storage device 503, a communication device 504, and a bus 505 that electrically connects them to each other.

[0129] The computing device 501 is, for example, a CPU (Central Processing Unit). The main storage device 502 is a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory).

[0130] The external storage device 503 is a nonvolatile storage device such as a so-called hard disk drive (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory that can store digital information.

[0131] The communication device 504 is a wired communication device that performs wired communication via a network cable or a wireless communication device that performs wireless communication via an antenna. The communication device 504 performs information communication with an external device connected to the network.

[0132] In the above, an example of the hardware configuration of the procurement work support device 100 has been described. In addition, the supply chain work support device 400 only needs to have the same hardware configuration as the procurement work support device 100 .

[0133] Fig.16 2 is a diagram showing an example of a hardware configuration of the user terminal device 200. The user terminal device 200 is, for example, an information processing device such as a personal computer.

[0134] As shown in the figure, the user terminal device 200 includes an input device 601, a display device 602, a computing device 603, a main storage device 604, an external storage device 605, a communication device 606, and a bus 607 that electrically connects them to each other.

[0135] The input device 601 is a pointing device such as a keyboard, a mouse, or a touch panel. The display device 602 is, for example, a liquid crystal display or an organic display.

[0136] The computing device 603 is, for example, a CPU. The main storage device 604 is a memory device such as a RAM or a ROM. The external storage device 605 is a nonvolatile storage device such as a so-called hard disk, an SSD, or a flash memory capable of storing digital information.

[0137] The communication device 606 is a wired communication device that performs wired communication via a network cable, or a wireless communication device that performs wireless communication via an antenna. The communication device 606 performs information communication with an external device connected to the network.

[0138] The operation unit 110 of the procurement operation support device 100 is implemented by a program that causes the operation device 501 to perform processing. The program is stored in the main storage device 502 or the external storage device 503, and is loaded into the main storage device 502 when the program is executed, and is executed by the operation device 501. In addition, the storage unit 120 is implemented by the main storage device 502 or the external storage device 503 or a combination thereof. In addition, the communication unit 130 is implemented by the communication device 504.

[0139] In addition, the input receiving unit 201 and the display unit 202 of the user terminal device 200 are implemented by a program that is processed by the computing device 603. The program is stored in the main storage device 604 or the external storage device 605, and is loaded to the main storage device 604 when the program is executed, and is executed by the computing device 603. In addition, the storage unit 203 is implemented by the main storage device 604 or the external storage device 605 or a combination thereof. In addition, the communication unit 204 is implemented by the communication device 606.

[0140] In addition, part or all of the above-mentioned structures, functions, processing parts and processing units of the procurement business support device 100, the user terminal device 200 and the supply chain business support device 400 can also be implemented by hardware, for example, through integrated circuit design. In addition, the above-mentioned structures and functions can also be implemented by software by a processor interpreting and executing programs that implement each function. Information such as programs, tables, files, etc. that implement each function can be placed in a storage device such as a memory, a hard disk, an SSD, or a recording medium such as an IC card, an SD card, and a DVD.

[0141] In addition, the present invention is not limited to the above-mentioned embodiments, and includes various modified examples. For example, the above-mentioned embodiments are described in detail in order to explain the present invention in an easy-to-understand manner, and are not limited to having all the structures described. In addition, a part of the structure of a certain embodiment can be replaced with the structure of other embodiments, and in addition, the structure of other embodiments can be added to the structure of a certain embodiment. In addition, for a part of the structure of each embodiment, other structures can be added, deleted, or replaced.

[0142] In the above description, the control lines and information lines are shown as those considered necessary for the description, and not all the control lines and information lines on the product are shown. In fact, it can be considered that almost all the structures are connected to each other.

[0143] Explanation of symbols

[0144] 1000, (2000) ... procurement business support system, 100 ... procurement business support device, 110 ... calculation unit, 111 ... information reading unit, 112 ... delivery expectation index calculation unit, 113 ... order plan formulation unit, 114 ... display information generation unit, 115 ... business logic execution unit, 120 ... storage unit, 121 ... supplier master information, 122 ... order history information, 123 ... delivery history information, 124 ... delivery expectation index information, 125 ... delivery expectation index histogram information, 126 ... procurement plan information, 127 …ordering plan information, 128…business logic information, 130…communication unit, 200…user terminal device, 201…input acceptance unit, 202…display unit, 203…storage unit, 204…communication unit, 501…computing device, 502…main storage device, 503…external storage device, 504…communication device, 505…bus, 601…input device, 602…display device, 603…computing device, 604…main storage device, 605…external storage device, 606…communication device, 607…bus, N…network.

Claims

1. A procurement business support system having a procurement business support device and a user terminal device, characterized in that: The procurement business assistance device comprises: a storage unit that stores order history information that registers past order history, delivery history information that registers past delivery history, and a procurement plan that registers items to be procured; a delivery expectation index calculation unit that uses the order history information to calculate a delivery expectation index indicating the ease of delivery for each order in the combination of each supplier and the variety, and calculates a delivery rate based on the delivery history information, the delivery rate indicating a ratio of the number of deliveries delivered on the required delivery date to the number of orders; an ordering plan formulation unit, which generates delivery expectation indicator histogram information indicating the relationship between the delivery expectation indicator and the delivery rate, calculates an average delivery rate corresponding to the delivery expectation indicator included in each of a plurality of predetermined ranges into which the range between the minimum value and the maximum value of the delivery expectation indicator is divided, calculates the delivery expectation indicator of the variety in the procurement plan, determines the supplier having the highest average delivery rate corresponding to the delivery expectation indicator using the delivery expectation indicator histogram information, and generates ordering plan information including the variety in the procurement plan and the determined supplier having the highest average delivery rate; as well as a communication unit that transmits predetermined screen information including the generated order plan information to the user terminal device, The user terminal device comprises: A display unit displays the screen information.

2. The procurement business support system according to claim 1, characterized in that: The delivery expectation index calculation unit calculates the delivery expectation index indicating the difficulty of the delivery based on a relationship between a number of days from an order date to a delivery date and a change in the number of orders from a previous order to a current order.

3. The procurement business support system according to claim 1, characterized in that: The order plan information includes the determined supplier, variety, delivery period and quantity of the variety, and the average delivery rate among the supplier and variety.

4. The purchasing business support system according to claim 1, characterized in that: The procurement business support system also has a supply chain business support device. The supply chain business support device comprises: a business logic generating unit, which generates business logic information, wherein the business logic information determines the best business logic corresponding to the market situation of the supply chain, The order planning unit of the procurement operation support device further comprises: A business logic execution unit generates the procurement plan again according to the business logic information.

5. A purchasing business support device, characterized in that: have: a storage unit that stores order history information that registers past order history, delivery history information that registers past delivery history, and a procurement plan that registers items to be procured; a delivery expectation index calculation unit that uses the order history information to calculate a delivery expectation index indicating the ease of delivery for each order in the combination of each supplier and the variety, and calculates a delivery rate based on the delivery history information, the delivery rate indicating a ratio of the number of deliveries delivered on the required delivery date to the number of orders; an ordering plan formulation unit, which generates delivery expectation indicator histogram information indicating the relationship between the delivery expectation indicator and the delivery rate, calculates an average delivery rate corresponding to the delivery expectation indicator included in each of a plurality of predetermined ranges into which the range between the minimum value and the maximum value of the delivery expectation indicator is divided, calculates the delivery expectation indicator of the variety in the procurement plan, determines the supplier having the highest average delivery rate corresponding to the delivery expectation indicator using the delivery expectation indicator histogram information, and generates ordering plan information including the variety in the procurement plan and the determined supplier having the highest average delivery rate; as well as The communication unit transmits predetermined screen information including the generated order plan information to an external device.

6. The purchasing business support device according to claim 5, characterized in that: The delivery expectation index calculation unit calculates the delivery expectation index indicating the difficulty of the delivery based on a relationship between a number of days from an order date to a delivery date and a change in the number of orders from a previous order to a current order.

7. The purchasing business support device according to claim 5, characterized in that: The order plan information includes the determined supplier, variety, delivery period and quantity of the variety, and the average delivery rate among the supplier and variety.

8. The purchasing business support device according to claim 5, characterized in that: The procurement work support device further includes a work logic execution unit that regenerates the procurement plan based on an optimal work logic corresponding to the market situation of the supply chain.

9. A procurement business assistance method performed by a procurement business assistance device, characterized in that: The purchasing business auxiliary device performs the following steps: A storing step of storing order history information registering past order history, delivery history information registering past delivery history, and a procurement plan registering items to be procured; a delivery expectation index calculation step, using the order history information, calculating a delivery expectation index indicating the ease of delivery according to the orders in the combination of each supplier and the variety, and calculating a delivery rate according to the delivery history information, wherein the delivery rate indicates the ratio of the number of deliveries delivered according to the required delivery period to the number of orders; a step of generating delivery expectation index histogram information indicating a relationship between the delivery expectation index and the delivery rate; An ordering plan formulation step, for each of a plurality of predetermined ranges into which a range between a minimum value and a maximum value of the delivery expectation index is divided, calculating an average delivery rate corresponding to the delivery expectation index included in each predetermined range, calculating the delivery expectation index of the variety in the procurement plan, using the delivery expectation index histogram information, determining the supplier having the highest average delivery rate corresponding to the delivery expectation index, and generating ordering plan information including the variety in the procurement plan and the determined supplier having the highest average delivery rate; as well as The communication step transmits predetermined screen information including the generated order plan information to an external device.

Images