Information processing device, method, and program

Abstract

This information processing device comprises a processor and a storage unit. The processor executes: an expected acquisition step for acquiring the expected shipping amount of a transaction object presented from a client; an inventory acquisition step for acquiring inventory information pertaining to the transaction object, the inventory information being used for responding to an order from the client; an assistance information generation step for generating assistance information for assisting in making a determination relating to replenishment of the transaction object on the basis of the expected shipping amount and the inventory information; and an assistance information output step for outputting the assistance information.

Description

Information Processing Apparatus, Method, and Program

[0001] The present disclosure relates to a program, a method, an information processing apparatus, and a system.

[0002] An information processing service for managing inventory is known. Patent Document 1 discloses a technique for performing an inventory plan based on the expected order quantity presented by a supplier.

[0003] Japanese Patent No. 4759544

[0004] There is a problem that the efficiency of inventory management and ordering operations cannot be improved. Therefore, the present disclosure has been made to solve the above problems, and its object is to provide a technique for improving the efficiency of inventory management and ordering operations.

[0005] An information processing apparatus including a processor and a storage unit, wherein the processor executes a step of obtaining an expected shipment quantity of a transaction target presented by a business partner (expected acquisition step), a step of obtaining inventory information of the transaction target for responding to an order from the business partner (inventory acquisition step), a step of generating support information for assisting in making a determination regarding replenishment of the transaction target based on the expected shipment quantity and the inventory information (support information generation step), and a step of outputting the support information (support information output step).

[0006] According to the present disclosure, the efficiency of inventory management and ordering operations can be improved.

[0007] This is a block diagram showing the functional configuration of System 1. This is a block diagram showing the functional configuration of Server 10. This is a block diagram showing the functional configuration of User Terminal 20. This is a diagram showing the data structure of User Table 1012. This is a diagram showing the data structure of Inventory Table 1021. This is a diagram showing the data structure of Incoming Table 1022. This is a diagram showing the data structure of Shipping Table 1023. This is a diagram showing the data structure of Forecast Table 1024. This is a diagram showing the data structure of Order Table 1025. This is a diagram showing the data structure of Transaction Master 1026. This is a flowchart showing the operation of the data import process. This is a flowchart showing the operation of the order recommendation process. This is a flowchart showing the operation of the data linkage process. This is an example screen showing the operation of Data Import Screen D5. This is an example screen showing the operation of Management Table Screen D1. This is an example screen showing the operation of Transaction Summary Screen D3. This is a block diagram showing the basic hardware configuration of Computer 90. This is a functional diagram showing the operation of System 1.

[0008] The embodiments of this disclosure will be described below with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated explanations are omitted. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each drawing is a schematic diagram and is not necessarily a strict illustration.

[0009] <Configuration of System 1> System 1 in this disclosure is an information processing system that comprehensively manages shipment performance information, incoming information, inventory information, and forecast information, and generates suitable order information and forecast information based on this information. System 1 includes an information processing device server 10 and a user terminal 20 connected via a network N. Figure 1 is a block diagram showing the functional configuration of System 1. Figure 2 is a block diagram showing the functional configuration of Server 10. Figure 3 is a block diagram showing the functional configuration of User Terminal 20.

[0010] Figure 18 is a functional diagram showing the operation of System 1 in this disclosure. In Figure 18, Company A (User Company D302) is User Company D302 of Information Processing System 1 related to this disclosure. Information Processing System 1 related to this disclosure is provided when employees belonging to the sales department, etc., of User Company D302, as users, access the information processing service provided by Server 10 related to this disclosure by operating the input device 206 of User Terminal 20. In Figure 18, for illustrative purposes, a configuration is disclosed in which various databases such as shipping tables, order tables, receiving tables, and inventory tables are stored within User Company D302. However, since the actual information service is provided to users in the form of a cloud service (SaaS, Software as a Service), Server 10, which stores the various databases, etc., is under the management of the information processing service operator related to System 1.

[0011] In Figure 18, user company D302 receives information regarding projected orders (customer notification) from company BD301 (higher tier / customer). It also receives orders for trading items from company B and ships / sells those items in accordance with those orders. This information is stored in the shipping table, which will be described later. Furthermore, user company D302 transmits information regarding projected orders (supplier notification) to company CD303 (lower tier / supplier). It also places orders with company C and receives / purchases trading items in accordance with those orders. Information regarding orders is stored in the order table, and information regarding receipts / purchases is stored in the receipt table.

[0012] This allows user company D302 to centrally manage projected and confirmed order information from higher-tier company BD301, and projected and confirmed order information from lower-tier company CD303. Furthermore, it becomes possible to comprehensively grasp the actual shipment and receipt records and inventory status of the relevant transactions using shipment tables, order tables, receipt tables, inventory tables, etc.

[0013] Furthermore, the information processing system 1 described herein can automatically perform tasks such as determining the feasibility of supplying orders from company BD301 and optimizing the estimated order shipment quantity to company CD303 based on this information. For example, based on the estimated order information received from company BD301, the system can determine the feasibility of supplying orders by considering the inventory status recorded in the inventory table and the expected arrival date from company CD303, and automatically adjust the estimated order shipment quantity to company CD303 as necessary.

[0014] As described above, the information processing system 1 disclosed herein enables integrated management of transaction information with higher and lower tiers, thereby improving the efficiency and optimization of order placement and receiving operations. In particular, by centrally managing information from the stages of expected orders and expected purchases, it becomes possible to respond quickly to fluctuations in demand, contributing to the optimization of inventory and improvement of the efficiency of the entire process chain.

[0015] Each information processing device consists of a computer equipped with an arithmetic unit and a memory device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by said hardware configuration will be described later. For each of the server 10 and user terminal 20, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0016] <Configuration of Server 10> Server 10 is an information processing device that provides an information processing service that comprehensively manages shipping performance information, receiving information, inventory information, and forecast information, and generates suitable order information and forecast information based on this information. Server 10 comprises a storage unit 101 and a control unit 104.

[0017] <Configuration of the storage unit 101 of server 10> The storage unit 101 of server 10 includes an application program 1011, a user table 1012, an inventory table 1021, a receiving table 1022, a shipping table 1023, a forecast table 1024, a purchase order table 1025, and a transaction master 1026.

[0018] Application program 1011 is a program that causes the control unit 104 of server 10 to function as various functional units. Application program 1011 includes applications such as a web browser application.

[0019] User Table 1012 is a table that stores and manages information about member users (hereinafter referred to as "users") who use the service. When a user registers to use the service, their information is stored in a new record in User Table 1012. This allows the user to use the service related to this disclosure. In this disclosure, employees, etc., belonging to the sales department, etc., of user company D302 are considered users. The users related to this disclosure may include both individuals such as employees and legal entities such as companies. User Table 1012 is a table with User ID as the primary key and has columns for User ID, User Name, and User Data. Figure 4 is a diagram showing the data structure of User Table 1012.

[0020] The User ID is an item that stores user identification information to identify a user. User identification information is an item that is set to a unique value for each user. The User Name is an item that stores the user's name. The User Name may be set to any string, such as a nickname, instead of a real name. User data includes unique information of the individual user and attribute information related to the user's characteristics and background. Unique information of the user includes unique information of the user such as the user's date of birth (age) and gender. Attribute information of the user includes information such as the user's educational history (highest level of education, major, graduation year), occupation, work history, interests, place of residence, and language. Note that columns not shown may also include information on the tier to which the user (user company) belongs in the supply chain. Tier information is information that indicates the tier level to which the company belongs (Tier 1, Tier 2, Tier 3, etc.), with the final product manufacturer being the highest tier (Tier 0). Tier information may also include company identification information of higher-tier and lower-tier companies with which the company has a direct trading relationship. This allows for a clear understanding of inter-company transaction relationships within the supply chain. Furthermore, user data can include information about the user's role and authority within the company to which they belong. For example, by storing information such as the user's department, job title, scope of work, and system access rights, appropriate access control and work allocation within the company become possible. In this way, by including company and tier information in user data, efficient management and optimization of inter-company transactions throughout the entire supply chain can be achieved.

[0021] The inventory table 1021 is a table for storing and managing information related to inventory (inventory information). The inventory table 1021 has the primary keys of location, supplier, product code, and capacity, and has columns for location, supplier, product code, capacity, actual inventory quantity S1, and predicted inventory quantity S2. Figure 5 shows the data structure of the inventory table 1021.

[0022] The "Storage Location" field stores information to identify the warehouse or location where goods are physically stored. In corporate logistics management, the "Storage Location" field identifies the physical location of inventory. Based on the "Storage Location," the physical location of inventory can be accurately grasped, enabling efficient inventory management. For example, the "Storage Location" field stores strings such as "Tokyo Warehouse Building A," "Osaka Logistics Center 3rd Floor," and "Nagoya Factory Raw Material Storage Area." The "Storage Location" field includes strings such as a "Storage Location Code" indicating the location. The "Supplier" field stores information to identify the company from which goods are purchased. The "Supplier" field functions as an identifier for managing trading relationships with suppliers in the supply chain. The "Supplier" field includes identification information such as the company name, company code, and trading partner code. For example, the "Supplier" field stores company names such as "Yamada Manufacturing Co., Ltd.," "AB Trading Co., Ltd.," and "CD Industries," as well as strings such as "SUP001" and "V00123." The "Supplier" field includes strings such as a "Supplier Code" indicating the supplier. The "Product Code" field stores product code information to uniquely identify the products handled. Product codes (CDs) are used in inventory and transaction management to accurately identify and track individual products. Product codes include identification codes indicating product type, such as rods, coils, and resin pellets, and are assigned according to each company's product labeling rules. For example, product codes may store strings such as "STL-R001" (stainless steel rod), "COP-C100" (copper coil), and "PLA-P202" (plastic pellet). The capacity field stores quantity information indicating the purchase unit of a product. The capacity defines the physical transaction unit of a product and serves as the standard quantity for ordering and inventory management. The capacity indicates the purchase quantity of the product identified by the product code in an appropriate unit according to the product characteristics, and includes information on handling units in logistics, such as packaging. In manufacturing industries such as automotive parts, common transaction units include management by quantity (pieces, pcs) and management by packaging unit (box, case, carton). For example, the capacity may store strings such as "500 pieces / box," "1000 pcs / carton," and "24 pieces / case." Furthermore, large parts and assembled products are managed using storage and transportation units such as "10 sets / pallet" or "5 units / cart."For raw materials, management by weight (kg, ton) is common, and strings such as "500 kg / pallet," "1000 kg / coil," and "25 kg / bag" are stored. Liquid raw materials are also managed by volume (L, kL), and units such as "1000 L / tank" and "200 L / drum" are used. Actual inventory quantity S1 is information that shows the amount of goods held in the warehouse at a specific point in time. Actual inventory quantity S1 is an indicator that represents the current actual holding status in asset management and inventory management. Actual inventory quantity S1 includes quantity information that is confirmed and recorded at the time of inventory counts such as at the end of the month or in the middle of the period. For example, actual inventory quantity S1 stores information such as "Inventory at the end of October: STL-R001 15000 kg" and "Interim inventory in November: COP-C100 8000 kg." Actual inventory quantity S1 also stores information that shows the quantity (number of units) of transaction units according to capacity, such as the number of boxes, cartons, cases, trolleys, and pallets. Actual inventory quantity S1 is stored in association with information indicating the date and time of inventory count, such as the end of the month or mid-year. Forecast inventory quantity S2 is an item that stores information indicating the forecast inventory quantity at a specific point in the future. Forecast inventory quantity S2 is an indicator that represents the future inventory level calculated based on the forecast incoming quantity and forecast outgoing quantity, starting from the current (or a specified day or timing) actual inventory quantity. Forecast inventory quantity S2 is used as a reference value in inventory planning and ordering decisions, and includes forecast information that is updated daily. For example, forecast inventory quantity S2 stores information such as "Forecast for the end of November: STL-R001 12,000 kg" and "Forecast for the middle of December: COP-C100 7,500 kg". Forecast inventory quantity S2 stores information indicating the quantity (number of units) of transaction units according to capacity, such as the number of boxes, cartons, cases, trolleys, and pallets. Actual inventory and projected inventory are fields that store information indicating the quantity (number of units) of a product purchased, as defined by its capacity.

[0023] The Inbound Table 1022 is a table for storing and managing information related to incoming goods (inbound information). The Inbound Table 1022 has the primary keys Location, Supplier, Product Code, and Capacity, and has columns for Location, Supplier, Product Code, Capacity, Actual Inbound Quantity I1, and Forecast Inbound Quantity I2. Figure 6 shows the data structure of the Inbound Table 1022.

[0024] The "Storage Location" field stores information to identify the warehouse or location where the goods are physically stored. The "Supplier" field stores information to identify the company from which the goods are purchased. The "Product Code" is product code information to uniquely identify the products handled. The "Capacity" field is quantity information indicating the purchase unit of the goods. The "Actual Incoming Quantity I1" field indicates the quantity of goods received into the warehouse. The "Actual Incoming Quantity I1" records the actual receipt status of goods and is used for inventory management. The "Actual Incoming Quantity I1" records the incoming quantity of goods identified by the "Product Code" and "Capacity" field and is managed as a history of inventory increases. For example, the "Actual Incoming Quantity I1" field stores information such as "October 1st Incoming: STL-R001 2000kg" and "October 2nd Incoming: COP-C100 5000kg". The "Actual Incoming Quantity I1" field stores information indicating the quantity (number of units) of transactions according to the capacity, such as the number of boxes, cartons, cases, trolleys, and pallets. The Forecasted Incoming Quantity I2 is an item that stores information indicating the planned incoming quantity at a specific point in the future. Forecasted Incoming Quantity I2 includes confirmed incoming quantities based on existing order information (actual order quantities and delivery dates) and future incoming quantities based on new order plans. Forecasted Incoming Quantity I2 records the planned incoming quantity of goods specified by product code and volume, and is used as basic data for future inventory forecasts. For example, Forecasted Incoming Quantity I2 stores information such as "Scheduled for November 15: STL-R001 2000 kg" and "Scheduled for December 1: COP-C100 3000 kg". Forecasted Incoming Quantity I2 stores information indicating the quantity (number of units) of transaction units according to volume, such as the number of boxes, cartons, cases, trolleys, and pallets.

[0025] The shipping table 1023 is a table for storing and managing information related to shipments (shipping information). The shipping table 1023 has a column for actual shipment quantity D1, with storage location, supplier, product code, and capacity as primary keys. Figure 7 shows the data structure of the shipping table 1023.

[0026] The "Storage Location" field stores information to identify the warehouse or location where the goods are physically stored. The "Supplier" field stores information to identify the company from which the goods are purchased. The "Product Code" field stores product code information to uniquely identify the products handled. The "Capacity" field stores quantity information indicating the purchase unit of the goods. The "Actual Shipment Quantity D1" field stores information indicating the quantity of goods actually shipped. The "Actual Shipment Quantity D1" records the actual shipment status of goods and is used for inventory management. The "Actual Shipment Quantity D1" records the shipment quantity of goods identified by the "Product Code" and "Capacity" field and is managed as a history of inventory reduction. For example, the "Actual Shipment Quantity D1" stores information such as "Shipped October 1st: STL-R001 2000kg" and "Shipped October 2nd: COP-C100 5000kg". The "Actual Shipment Quantity D1" field stores information indicating the quantity (number of units) of transactions according to the capacity, such as the number of boxes, cartons, cases, trolleys, and pallets.

[0027] The forecast table 1024 is a table for storing and managing information related to forecasts (forecast information). The forecast table 1024 has the primary keys of location, supplier, product code, and capacity, and has columns for location, supplier, product code, capacity, estimated shipment quantity D2, and scheduled date. Figure 8 shows the data structure of the forecast table 1024.

[0028] The "Storage Location" field stores information to identify the warehouse or location where the goods are physically stored. The "Supplier" field stores information to identify the company from which the goods are purchased. The "Product Code" field stores product code information to uniquely identify the products handled. The "Capacity" field stores quantity information indicating the unit of purchase for the goods. The "Customer Name" field stores information to identify the company to which the goods are sold. The customer name is information used to manage relationships with trading partners in sales management and to accurately grasp sales performance and forecasts. The customer name includes identification information such as the official name or company code of the customer company. For example, the customer name may store strings such as "○○ Industries Co., Ltd.", "△△ Manufacturing Co., Ltd.", "CUS001", or "B00789". The "Expected Shipment Volume D2 (Expected Order, Customer Notification)" field stores information indicating the expected shipment volume for a specified future month (1 month, 3 months, 6 months, etc.) as provided by the customer. The Estimated Shipment Quantity D2 is a forecasting indicator used when formulating production and inventory plans. While not used for sales revenue recognition, Estimated Shipment Quantity D2 includes forecast quantity information (such as forecasts) provided by customers for preparation purposes. For example, Estimated Shipment Quantity D2 stores strings such as "November: 3000 kg," "December: 3500 kg," and "January: 4000 kg." Estimated Shipment Quantity D2 stores information indicating the quantity (number of units) of transactions according to volume, such as the number of boxes, cartons, cases, trolleys, and pallets. Estimated Unit Quantity F (Indicated Unit s) is an indicator showing the planned shipment quantity per cycle (transaction cycle of the transaction target, such as 6 hours, 1 day, or 1 week) calculated based on the forecast information. Estimated Unit Quantity F is calculated by dividing the sum of Estimated Shipment Quantities D2 for a certain future period by the number of days in that period. Estimated Unit Quantity F is used as a future shipment forecast and forms the basis for inventory and ordering plans. For example, the unit forecast F is expressed as information such as "100 kg per cycle calculated from a total forecast of 9,000 kg over three months." Furthermore, when the forecast shipment volume spans multiple months, it is preferable to use a weighted moving average or similar method to weight the most recent forecast shipment volume as more reliable information. The recommended forecast quantity D3 is an item linked to the item stored in the recommended order quantity in the order table 1025 by the trading partner.When a trading partner also uses the information processing service related to this disclosure, and the trading partner's user calculates a recommended order quantity in the order recommendation process, and the recommendation in the order table 1014 is stored in the medium quantity item, the stored value is linked to the recommended forecast quantity D3. This makes it possible to link demand and supply forecast information across the entire supply chain. Specifically, the recommended order quantity calculated by the trading partner is automatically reflected as the company's recommended forecast quantity, ensuring consistency between the trading partner's inventory plan and the company's shipping plan. Furthermore, this linkage reduces the risk of inventory shortages or excess inventory at the trading partner and enables the maintenance of an optimal inventory level across the entire supply chain. In addition, automating information linkage with trading partners contributes to the efficiency of ordering operations and the prevention of human errors. The scheduled date is an item that stores information indicating the scheduled delivery date in the forecast information. The scheduled date is a time indicator for formulating future logistics plans and maintaining appropriate inventory levels. The scheduled date is entered at the end of the month, etc., and indicates the delivery plan for a specific date and time in the future. For example, the scheduled date is stored as a string such as "Delivery on 11 / 15", "Delivery on 12 / 1", or "Delivery on 12 / 15".

[0029] The order table 1025 is a table for storing and managing information related to orders (order information). The order table 1025 has the primary keys of location, supplier, product code, and capacity, and has columns for location, supplier, product code, capacity, actual order quantity O1, delivery date, recommended order quantity O2, and estimated order quantity O3. Figure 9 shows the data structure of the order table 1025.

[0030] The "Storage Location" field stores information to identify the warehouse or location where the goods are physically stored. The "Supplier" field stores information to identify the company from which the goods are purchased. The "Product Code" field stores product code information to uniquely identify the products handled. The "Capacity" field stores quantity information indicating the purchase unit of the goods. The "Actual Order Quantity O1" field indicates the quantity of goods to be ordered from the supplier. The "Actual Order Quantity O1" is managed as future arrival schedule information and is calculated based on lead time and standard inventory index. For example, the "Actual Order Quantity O1" stores strings such as "Order Number A001: STL-R001 2000kg" and "Order Number A002: COP-C100 3000kg". The "Delivery Date" field indicates the delivery deadline for the ordered goods. The "Delivery Date" is a time-based indicator for managing delivery timing in procurement management and maintaining appropriate inventory levels. The "Delivery Date" indicates the expected date of goods arrival from the supplier, set considering lead time, etc. For example, it stores strings such as "Delivery on 11 / 30", "Delivery on 12 / 15", and "Delivery on 12 / 30". Actual Order Quantity O1 stores information indicating the quantity (number of units) of transactions according to volume, such as the number of boxes, cartons, cases, trolleys, and pallets. Specifically, the delivery date is associated with and stored for each Actual Order Quantity O1. Recommended Order Quantity O2 is an item that stores a predicted value indicating the quantity of goods that should be ordered in the future. Recommended Order Quantity O2 is the planned order quantity calculated with the second standard inventory quantity as the upper limit when the predicted inventory quantity falls below the first standard inventory quantity. Recommended Order Quantity O2 is calculated based on lead time and standard inventory index and includes information that forms the basis of future receiving plans. For example, Recommended Order Quantity O2 stores information such as "Recommended order: STL-R001 2500kg" and "Recommended order: COP-C100 3500kg". The recommended order quantity O2 stores information indicating the quantity (number of units) of transactions according to volume, such as the number of boxes, cartons, cases, trolleys, and pallets. The projected order quantity O3 (projected order, supplier notification) is an item that stores information indicating the planned order quantity for a specified future month (1 month, 3 months, 6 months, etc.) to be presented to the supplier. The projected order quantity O3 is an important forecasting indicator for the supplier's production plan and inventory plan formulation.The estimated order quantity O3 includes forecast quantity information (such as forecast) that is communicated in advance to the supplier for preparation purposes, even though the order has not yet been confirmed. For example, the estimated order quantity O3 stores strings such as "November forecast: 2500 kg", "December forecast: 3000 kg", and "January forecast: 3500 kg". Note that the estimated order quantity O3 is equivalent to the estimated shipment quantity D2 for the supplier. The estimated order quantity O3 stores information indicating the quantity (number of units) of the transaction unit according to volume, such as the number of boxes, cartons, cases, trolleys, and pallets.

[0031] Transaction Master 1026 is a table for storing and managing information (product information) about products (transaction items). Transaction Master 1026 is a table with the primary keys Location, Supplier, Product Code, and Capacity, and has columns for Location, Supplier, Product Code, Capacity, Lead Time, and Standard Inventory Index. Figure 10 shows the data structure of Transaction Master 1026.

[0032] The "Storage Location" field stores information to identify the warehouse or location where the goods are physically stored. The "Supplier" field stores information to identify the company from which the goods are purchased. The "Product Code" field stores product code information to uniquely identify the products handled. The "Capacity" field stores quantity information indicating the unit of purchase for the goods. The "Lead Time" field stores the time required from placing an order until the goods are actually received. Lead time is an indicator showing the number of days required from ordering to receiving the goods. Lead time is used as a reference time for making ordering decisions. For example, a period such as 21 days may be stored as the lead time. The "Standard Inventory Index" field stores an indicator showing the appropriate inventory level that should be maintained. The standard inventory index includes two reference periods. Specifically, the standard inventory index includes the first period (an indicator showing the inventory quantity for the first period) and the second period (an indicator showing the inventory quantity for the second period). For example, the first period may be two weeks and the second period may be four weeks. The first standard inventory level L is an indicator that shows the minimum inventory level that should be maintained to prevent inventory shortages. The first standard inventory level L is calculated as the product of the unit estimate F, lead time T, and the standard inventory index for the first period. The first standard inventory level L functions as a lower limit for ordering decisions, and ordering is considered when it is predicted that inventory levels will fall below this level. For example, the first standard inventory level L may be expressed as information such as "2100 kg calculated from a unit estimate of 100 kg, a lead time of 21 days, and a standard inventory index of 1.0". The first standard inventory level L stores information indicating the quantity (number of units) of trading units according to capacity, such as the number of boxes, cartons, cases, trolleys, and pallets. The second standard inventory level U is an indicator that shows the upper limit of the inventory level set to suppress excess inventory. The second standard inventory level U is calculated as the product of the unit estimate F, lead time T, and the standard inventory index for the second period. The second standard inventory quantity U functions as an upper limit when determining the order quantity, and the order quantity is adjusted so that the forecast inventory does not exceed this level. For example, the second standard inventory quantity U may be expressed as information such as "4,200 kg calculated from a unit forecast of 100 kg, a lead time of 21 days, and a standard inventory index of 2.0." Note that the standard inventory index may be omitted (1.0).The second standard inventory quantity U stores information indicating the quantity (number of units) of a transaction unit according to its volume, such as the number of boxes, cartons, cases, trolleys, or pallets.

[0033] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0034] The user registration control unit 1041 processes information of users who wish to use the services related to this disclosure and stores it in the user table 1012. The information stored in the user table 1012 is obtained when a user opens a web page operated by the service provider from any information processing terminal, enters information into a predetermined input form, and sends it to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, and user registration is completed. As a result, users stored in the user table 1012 can use the service. Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined review and restrict whether or not a user can use the service. The user ID may be any string or number that can identify the user, and may be any string or number that the user wishes, or the user registration control unit 1041 may automatically set an arbitrary string or number.

[0035] <Configuration of User Terminal 20> The user terminal 20 is an information processing device operated by a user of the service. The user terminal 20 may be, for example, a mobile device such as a smartphone or tablet, or a stationary PC (Personal Computer) or laptop PC. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The user terminal 20 comprises a storage unit 201, a control unit 204, an input device 206, and an output device 208.

[0036] <Configuration of the storage unit 201 of the user terminal 20> The storage unit 201 of the user terminal 20 includes a user ID 2011 and an application program 2012.

[0037] User ID 2011 is the user's account ID. The user transmits User ID 2011 from the user terminal 20 to the server 10. The server 10 identifies the user based on User ID 2011 and provides the services related to this disclosure to the user. User ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the user terminal 20.

[0038] The application program 2012 may be pre-stored in the memory unit 201, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. The application program 2012 includes applications such as a web browser application. The application program 2012 includes an interpreter-type programming language such as JavaScript® that is executed on the web browser application stored in the user terminal 20.

[0039] <Configuration of the control unit 204 of the user terminal 20> The control unit 204 of the user terminal 20 comprises an input control unit 2041 and an output control unit 2042. The control unit 204 realizes each functional unit by executing the application program 2012 stored in the storage unit 201.

[0040] <Configuration of the input device 206 of the user terminal 20> The input device 206 of the user terminal 20 includes a camera 2061, a microphone 2062, a position information sensor 2063, a motion sensor 2064, and a touch device 2065.

[0041] <Configuration of the output device 208 of the user terminal 20> The output device 208 of the user terminal 20 includes a display 2081 and a speaker 2082.

[0042] <Operation of System 1>The following describes each process of System 1. FIG. 11 is a flowchart showing the operation of the data import process. FIG. 12 is a flowchart showing the operation of the order recommendation process. FIG. 13 is a flowchart showing the operation of the data linkage process. FIG. 14 is an example screen showing the operation of the data import screen D5. FIG. 15 is an example screen showing the operation of the management table screen D1. FIG. 16 is an example screen showing the operation of the transaction summary screen D3.

[0043] <Data Import Process>The data import process is a process of importing shipping performance information, incoming information, inventory information, and estimated information into the system.

[0044] <Overview of Data Import Process>The data import process is a series of processes that import various data from a data source such as an Excel file, define data mapping rules, upload estimated information, and verify the imported data.

[0045] <Details of Data Import Process>The details of the data import process are described below.

[0046] Specifically, the user operates the input device 206 of the user terminal 20, executes a browser application or the like, and opens the data import screen D5 by inputting the URL of a web page (data import page) for executing the data import process. The control unit 204 of the user terminal 20 transmits a request including the user ID 2011 for opening the data import screen D5 to the server 10.

[0047] When the server 10 receives the request, it generates the data import screen D5 and transmits it to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the data import screen D5 on the display 2081 of the user terminal 20. FIG. 14 is an example screen of the data import screen in the data import process. The data import screen D5 is displayed on the display 2081 of the user terminal 20. The data import screen D5 includes a file selection bar D501, a header selection bar D502, and a data structure input bar D503.

[0048] <Data File Reception>In step S101, the control unit 104 of the server 10 executes a step of acquiring order information regarding orders, receipt information regarding receipts, and shipment information regarding shipments for each of a plurality of users. Specifically, on the data import screen D5 displayed on the display 2081 of the user terminal 20, the user selects at least a part of an inventory file, a shipment record file, a receipt file, and a forecast file in the file selection field D501. The user selects files such as an inventory file, a shipment record file, a receipt file, and a forecast file (files in the form of spreadsheet software such as Excel files and CSV files) according to the file selection field D501 and transmits them to the server 10. The control unit 104 of the server 10 receives and accepts the files.

[0049] Execute a step of acquiring shipment information regarding shipments for each of a plurality of users. The control unit 104 of the server 10 executes a step of acquiring order information regarding orders for each of a plurality of users. A user who is a user of the information processing service according to the present disclosure can each transmit (upload) their own inventory file, shipment record file, receipt file, forecast file, etc. to the server 10 in the data import process. That is, each of the trading partners (counterparties) of the trading target can import data into the information processing service according to the present disclosure.

[0050] In step S102, the control unit 104 of the server 10 performs a step of defining mapping rules. Specifically, the user defines the correspondence between the header items of the uploaded file and the items of each table in the system in the header selection field D502. Specifically, the user specifies which header name in the input Excel corresponds to the items stored in the tables of the information processing service related to this disclosure (column names such as location, location code, supplier name, supplier code, product code, product name, capacity, inventory quantity, etc.). Furthermore, in the data structure input field D503, the user specifies data structure patterns such as how to store year and month information in the table and how year and month information is included in the header items. Based on this setting information, the control unit 104 of the server 10 generates data mapping rules.

[0051] In step S103, the control unit 104 of the server 10 performs a process to convert the received data and store it in a table. Specifically, the control unit 104 of the server 10 converts the data of the uploaded file into an appropriate table format according to the defined mapping rules. At this time, the control unit 104 of the server 10 performs the following processes: - Standardization of data format (unification of date format, normalization of numerical values, etc.) - Code conversion (conversion from external code to internal code as needed) - Construction of data relationships (association of primary key items) The control unit 104 of the server 10 stores the converted data in the inventory table 1021, the incoming goods table 1022, the outgoing goods table 1023, the forecast table 1024, or the order table 1025, depending on the type of file.

[0052] In step S104, the control unit 104 of the server 10 executes a process to verify the data stored in the table. Specifically, the control unit 104 of the server 10 performs the following verifications on the data stored in the table: - Data integrity check (presence or absence of required fields, validity of data types) - Validity check based on business rules (checking the range of quantities, logical consistency of dates, etc.) - Consistency check with master data (confirmation of the existence of product codes, customer codes, etc.) - If an error is detected during verification, the control unit 104 of the server 10 displays the error details on the screen and prompts the user to make corrections. Once all verifications are complete and there are no errors, the control unit 104 of the server 10 completes the data import process.

[0053] <Recommended Ordering Process> The recommended ordering process calculates the optimal order quantity based on the various information collected.

[0054] <Overview of the Order Recommendation Process> The order recommendation process is a series of processes that acquire data, acquire lead time, acquire standard inventory index, calculate unit estimate, calculate predicted incoming quantity, calculate recommended order quantity based on standard inventory index and lead time, and present the recommended order quantity along with the timing of the order.

[0055] <Details of Recommended Order Processing> The details of the recommended order processing are explained below.

[0056] Specifically, the user opens the management table screen D1 by operating the input device 206 of the user terminal 20, running a browser application or the like, and entering the URL of a web page (order recommendation page) for executing the order recommendation process. The control unit 204 of the user terminal 20 sends a request to the server 10 that includes the user ID 2011 to open the management table screen.

[0057] When the server 10 receives a request, it generates a management table screen D1 and sends it to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the management table screen D1 on the display 2081 of the user terminal 20. Figure 15 is an example of the management table screen D1 in the order recommendation process. The management table screen D1 is displayed on the display 2081 of the user terminal 20. The management table screen D1 lists inventory information from the inventory table 1021, incoming information from the incoming table 1022, forecast information from the forecast table 1024, and order information from the order table 1025, using the location, supplier, product code (product name), and capacity as the primary keys of the transaction. In this disclosure, the actual inventory information, incoming information, forecast information, and order information as of October are displayed in the September performance list D101 and the October performance list D102. Furthermore, future (November) inventory information, incoming goods information, forecast information, and order information will be displayed in the November forecast list D103. Specifically, the incoming goods column in the September actuals list D101 and the October actuals list D102 will display information indicating the actual amount of goods received from suppliers. On the other hand, the November forecast list D103 will display information indicating the recommended incoming goods quantity (recommended order quantity), which is the amount of goods that should be received. The recommended order quantity is calculated by the order recommendation process. For transactions with a recommended order quantity, the recommendation display D1031 will be displayed along with the recommended order quantity.

[0058] <Data Acquisition> In step S301, the control unit 104 of the server 10 executes an inventory acquisition step to acquire inventory information including the actual inventory quantity of the trading target. The control unit 104 of the server 10 executes an order acquisition step to acquire order information including the actual order quantity to the trading partner of the trading target. The control unit 104 of the server 10 executes an estimate acquisition step to acquire estimate information including the estimated shipment quantity (planned shipment quantity) to the trading partner of the trading target. The control unit 104 of the server 10 executes a shipment acquisition step to acquire shipment information including the actual shipment quantity of the trading target. Specifically, the control unit 104 of the server 10 refers to the incoming table 1022 and acquires the actual incoming quantity I1 and the estimated incoming quantity I2, using the storage location, supplier, product code (product name), and capacity as primary keys. The control unit 104 of the server 10 refers to the outgoing table 1023 and acquires the actual outgoing quantity D1, using the storage location, supplier, product code (product name), and capacity as primary keys. The control unit 104 of server 10 refers to the forecast table 1024 and retrieves the estimated shipment quantity D2 and scheduled date, using the storage location, supplier, product code (product name), and capacity as primary keys. The control unit 104 of server 10 refers to the order table 1025 and retrieves the actual order quantity O1, delivery date, and recommended order quantity O2, using the storage location, supplier, product code (product name), and capacity as primary keys.

[0059] The control unit 104 of server 10 creates a management table screen D1 by associating incoming information, forecast information, and order information for each transaction target, using the location, supplier, product CD (product name), and capacity as the primary key for the transaction target.

[0060] The control unit 104 of the server 10 executes a shipment forecast acquisition step to acquire the shipment forecast quantity, which indicates the future planned shipment quantity of the transaction item presented by the ordering party at a higher level. The control unit 104 of the server 10 also executes an inventory acquisition step to acquire inventory information of the transaction item in order to respond to the ordering party's order. The inventory table 1021, the receiving table 1022, the shipping table 1023, the forecast table 1024, the order table 1025, and the transaction master 1026 are stored independently for each user. Multiple users store inventory information, receiving information, forecast information, order information, and product information in the inventory table 1021, receiving table 1022, shipping table 1023, forecast table 1024, order table 1025, and transaction master 1026 associated with each user. In this disclosure, it is permitted to link inventory information, incoming information, forecast information, order information, and product information associated with each user, thereby linking various types of information among multiple business partners (companies) without data import processing or manual data entry by personnel.

[0061] For example, in this disclosure, we will explain the transaction of automotive parts as an example. The automotive industry's supply chain has a multi-layered structure with the finished vehicle manufacturer at the top. In this structure, each layer is responsible for manufacturing and supplying specific parts and materials, and delivering them to the higher layers. The finished vehicle manufacturer is an automobile manufacturing company. It is located at the top of the supply chain and assembles and sells the final product, the automobile. Tier 1 (first-tier suppliers) are a group of companies that supply parts directly to the finished vehicle manufacturer. They manufacture major systems and modules such as engines, transmissions, and brake systems. At this layer, the finished vehicle manufacturer is the "orderer," and the Tier 1 companies are the "contractors." The orderer and contractors together are called trading partners. Tier 2 (second-tier suppliers) are a group of companies that supply parts and materials to Tier 1. They manufacture individual parts such as pistons, gears, and sensors. At this layer, the Tier 1 companies are the "orderers," and the Tier 2 companies are the "contractors." Tier 3 (Third-Tier Suppliers) are a group of companies that supply raw materials and basic components to Tier 2. They are responsible for basic manufacturing such as metal processing, plastic molding, and electronic components. In this tier, Tier 2 companies are the "orderers," and Tier 3 companies are the "suppliers." Regarding the flow of information, the production plan of the finished vehicle manufacturer is transmitted sequentially from Tier 1 to Tier 2 and then to Tier 3. The order schedules at each tier are created based on forecast information from the higher tiers. The importance of inventory management lies in the fact that each tier needs to maintain appropriate inventory levels in order to respond quickly to orders from higher tiers. In addition, planned order management is required to ensure a stable supply from lower tiers. In this multi-tiered structure, each company functions as a "supplier" to higher tiers and as an "orderer" to lower tiers, depending on the tier in which it is located. Therefore, efficient inventory management and order management are important elements of business operations.

[0062] Automobile manufacturers, Tier 1, Tier 2, and Tier 3 companies each access this system as users. Each user maintains their own inventory table 1021, receiving table 1022, shipping table 1023, forecast table 1024, order table 1025, and transaction master 1026. By linking this data among multiple users, efficient inventory management and order management are achieved. As an example, if a Tier 1 company is the orderer and a Tier 2 company is the orderer, the following linkage takes place. The transaction begins with an order from the Tier 1 company to the Tier 2 company. When the Tier 1 company places an order, the actual order quantity O1 is recorded in the company's order table 1025. Next, the Tier 2 company ships the goods based on the received order. This shipment record is recorded as the actual shipment quantity D1 in the Tier 2 company's shipping table 1023. Then, this actual shipment quantity D1 is automatically reflected as the actual received quantity I1 in the Tier 1 company's receiving table 1022.

[0063] <Forecasting Collaboration> Forecasting information is transmitted sequentially from the finished vehicle manufacturer down to the lower levels. First, Tier 1 companies record the forecast information received from the finished vehicle manufacturer as forecast shipment volume D2 in their own forecast table 1024. This forecast shipment volume D2 is used as future order planning to Tier 2 companies. Tier 2 companies formulate their own production and inventory plans based on this forecast information. Furthermore, this information is also used as basic data when Tier 2 companies formulate order plans to Tier 3 companies. The following effects can be obtained through this inter-company data collaboration. Firstly, data entry and transcription work are eliminated, making data entry more efficient. Secondly, forecast information from higher levels can be directly reflected in order planning at lower levels, enabling more accurate demand forecasting. Thirdly, order information and shipment information are linked immediately, enabling real-time information sharing among stakeholders. In this way, this system achieves efficient inventory management and order management throughout the entire supply chain by linking the individual tables held by each user. Furthermore, since this integration is performed automatically, manual data import and input work, as was done in the past, becomes unnecessary, resulting in a significant improvement in operational efficiency.

[0064] The user selects a transaction item (storage location, supplier, product code (product name), capacity) included in the management table screen D1 by operating the input device 206 of the user terminal 20. The control unit 204 of the user terminal 20 sends a request to the server 10 to display the transaction summary of the selected transaction item. Based on the received request, the control unit 104 of the server 10 acquires inventory information, incoming information, forecast information, and order information for the transaction item, generates a transaction summary screen D3, and sends it to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the transaction summary screen D3 on the display 2081 of the user terminal 20. The transaction summary screen D3 is shown in Figure 16. The transaction summary screen D3 includes a lead time input field D301, a standard inventory index input field D302, a forecast adjustment input field D303, an inventory trend forecast D311, an order plan D312, and a performance display field D313 for actual shipments (sales), forecasts, accuracy rate (score), etc.

[0065] <Lead Time Acquisition> In step S302, the control unit 104 of the server 10 executes a lead time acquisition step to acquire the lead time until the item to be traded arrives. Specifically, the user enters the lead time of the item to be traded into the lead time input field D301 by operating the input device 206 of the user terminal 20.

[0066] <Acquisition of Standard Inventory Index> In step S304, the control unit 104 of the server 10 acquires the standard inventory index, which is an indicator showing the appropriate inventory level to be maintained. The standard inventory index includes the first period and the second period. Specifically, the user enters the lead time of the transaction target into the standard inventory index input field D302 by operating the input device 206 of the user terminal 20.

[0067] The control unit 204 of the user terminal 20 transmits the input lead time and standard inventory index, along with the values ​​of the location, supplier, product code (product name), and capacity of the transaction item, to the server 10. The control unit 104 of the server 10 stores the location, supplier, product code (product name), capacity, lead time, and standard inventory index of the transaction item in the location, supplier, product code, capacity, lead time, and standard inventory index fields of the transaction master 1026, respectively. In this way, the transaction item, lead time, and standard inventory index are stored in association with each other.

[0068] <Calculation of Unit Estimate> In step S304, the control unit 104 of the server 10 executes a unit estimate calculation step to calculate the unit estimate, which is the predicted shipment volume per unit period (cycle), by dividing the planned purchase quantity (planned shipment quantity, estimated shipment volume) included in the forecast information by the planned purchase period (planned shipment period, estimated shipment period). For example, if the total estimated shipment volume for three months is 9,000 units and the period is 90 days, the unit estimate F = 9,000 ÷ 90 = 100 units / day. In addition, a calculation method using a weighted average can be adopted to make a more accurate forecast. When using a weighted average, a unit estimate that more closely reflects the actual situation can be calculated by assigning a larger weight to the estimated shipment volume of the most recent period. For example, if the weight for the first month is 0.5, the second month is 0.3, and the third month is 0.2, the unit estimate F is calculated by dividing the value by the number of days in each month, multiplying by the weight, and summing them up.

[0069] The control unit 104 of the server 10 executes an adjustment acquisition step to acquire forecast adjustment parameters for adjusting the unit forecast value. The unit forecast calculation step includes a step of correcting the unit forecast based on the forecast adjustment parameters. Specifically, the user inputs a forecast adjustment value (forecast adjustment parameter α) into the forecast adjustment input field D303 by operating the input device 206 of the user terminal 20. The forecast adjustment is a decimal value greater than or equal to 0. The control unit 204 of the user terminal 20 transmits the forecast adjustment value to the server 10. The control unit 104 of the server 10 may also store the acquired forecast adjustment value in the transaction master 1026 in association with the target product. The control unit 104 of the server 10 corrects the unit forecast F to F2 by multiplying the calculated unit forecast F by the forecast adjustment parameter α. For example, for customers who are expected (tentatively) to purchase a quantity smaller than the actual quantity, the unit forecast is corrected by multiplying by a forecast adjustment parameter α greater than 1. For example, for customers who are expected to purchase a quantity that is greater than the actual quantity (informal forecast), the unit forecast is adjusted by multiplying it by a forecast adjustment parameter α of less than 1.

[0070] The control unit 104 of the server 10 executes a standard inventory acquisition step to acquire a first standard inventory quantity and a second standard inventory quantity that indicate the appropriate inventory level for the trading target. Specifically, the control unit 104 of the server 10 calculates the first standard inventory quantity L by multiplying the first period n1 included in the standard inventory index acquired in step S103 by the unit forecast F. The control unit 104 of the server 10 calculates the second standard inventory quantity U by multiplying the second period n2 included in the standard inventory index acquired in step S103 by the unit forecast F. In addition, the unit forecast may be the amount obtained by multiplying by the forecast adjustment parameter. First standard inventory quantity L = F × α × n1 Second standard inventory quantity U = F × α × n2

[0071] <Calculation of Forecast Adjustment Parameters> In step S304, the control unit 104 of the server 10 performs a score calculation step to calculate an forecast score indicating the accuracy of the forecast information by comparing the forecast information obtained in the forecast acquisition step with the shipment information. Specifically, the control unit 104 of the server 10 refers to the shipment table 1023 and the forecast table 1024 to obtain the actual shipment volume D1 and the forecast shipment volume D2 for a certain period in the past (for example, the past 6 months). The control unit 104 of the server 10 compares the actual trends of the monthly forecast shipment volume D2 and the actual shipment volume D1 and calculates the forecast score (accuracy rate). The forecast score is calculated by dividing the actual shipment volume D1 by the forecast shipment volume D2 and expressing it as a percentage (forecast score = D1 / D2 × 100). The control unit 104 of the server 10 may also store the calculated forecast score in the transaction master 1026 in association with the transaction target. Furthermore, the control unit 104 of the server 10 may calculate the average value of the estimated scores for the past six months and calculate it as the average estimated score (average correct answer rate). The control unit 104 of the server 10 may also transmit the calculated correct answer rate and average correct answer rate to the user terminal 20. The control unit 204 of the user terminal 20 displays the calculated correct answer rate and average correct answer rate in the actual results display field D313 and presents it to the user. The user may input estimated adjustment parameters in the estimated adjustment input field D303, referring to the correct answer rate and average correct answer rate in the actual results display field D313.

[0072] The control unit 104 of server 10 executes an adjustment calculation step to calculate an adjustment parameter based on the forecast score. The adjustment acquisition step executes a step to acquire the adjustment parameter calculated in the adjustment calculation step. Specifically, the control unit 104 of server 10 automatically sets the adjustment parameter α based on the calculated average forecast score. Specifically, if the average forecast score is less than 100 (when actual results consistently fall below the forecast), it sets the adjustment parameter α to less than 1 according to the deviation rate. For example, if the average forecast score is 80, it sets α = 0.8. Conversely, if the average forecast score is greater than 100 (when actual results consistently exceed the forecast), it sets the adjustment parameter α to greater than 1 according to the excess rate. For example, if the average forecast score is 120, it sets α = 1.2. The control unit 104 of server 10 stores the set adjustment parameter α in the transaction master 1026.

[0073] In step S304, the score calculation step performs the step of calculating an estimated score for each trading partner (trading partner) or the person in charge at that trading partner. Specifically, the control unit 104 of the server 10 aggregates the actual shipment volume D1 and the estimated shipment volume D2 for each trading partner code and person in charge code stored in the shipment table 1023 and the estimated table 1024. The control unit 104 of the server 10 uses the aggregated values ​​to individually calculate the estimated score for each trading partner or person in charge. This makes it possible to quantitatively grasp the trend of the estimated accuracy for each trading partner or person in charge. Furthermore, the control unit 104 of the server 10 stores the calculated individual estimated scores in the transaction master 1026 and uses them as basic data for setting appropriate estimated adjustment parameters α for each trading partner or person in charge. This makes it possible to define the estimated adjustment parameters in more detail for each trading partner and each person in charge at that trading partner. It is possible to calculate the recommended order quantity more accurately by taking into account past actual shipment results.

[0074] <Calculation of Predicted Incoming Quantity I2> In step S305, the control unit 104 of the server 10 executes an incoming quantity calculation step to calculate incoming quantity information, including the predicted incoming quantity of the transaction target, based on the actual order quantity and delivery date included in the order information. Specifically, the control unit 104 of the server 10 calculates the confirmed incoming quantity I2_conf(t+n) from the current time t to future time t+n. The control unit 104 of the server 10 refers to the order table 1025 and extracts the actual order quantity O1 for all order records with a delivery date of time t+n. By summing these actual order quantities O1, the confirmed incoming quantity I2_conf(t+n) at time t+n is calculated. For example, if there are three orders with a delivery date of t+5th day, and their respective actual order quantities O1 are 100, 200, and 300 units, the confirmed incoming quantity I2_conf(t+5) on t+5th day will be 600 units.

[0075] The Inbound Calculation Step calculates inbound information, including the predicted inbound quantity for the second period, which is earlier than the first period, based on the recommended order quantity and lead time calculated in the Order Calculation Step for the first period. The Inbound Calculation Step calculates the recommended order quantity for a predetermined day, using the difference between the second standard inventory quantity and the predicted inventory quantity as the upper limit, if the predicted inventory quantity is lower than the first standard inventory quantity. Specifically, the control unit 104 of the server 10 calculates the predicted inbound quantity I2_pred(t+n) for the second period, which is earlier than the first period, based on the recommended order quantity O2 for the first period and the lead time T obtained from the transaction master 1026. The predicted inbound quantity I2_pred(t+n) is equal to the recommended order quantity O2(t+n-T) n-T days prior. For example, if the recommended order quantity O2(t) is 500 units and the lead time T is 10 days at time t, the predicted inbound quantity I2_pred(t+10) on day t+10 will be 500 units. The control unit 104 of the server 10 adds the calculated confirmed incoming quantity I2_conf(t+n) and the predicted incoming quantity I2_pred(t+n) and calculates the predicted incoming quantity I2(t+n) at time t+n using the following formula: I2(t+n) = I2_conf(t+n) + I2_pred(t+n) This makes it possible to calculate order information that includes future recommended order quantities, taking into account the predicted incoming quantity estimated in line with future recommended order quantities. More accurate order information can be calculated for the distant future. In other words, by treating the recommended order quantity O2 calculated by the order recommendation process as order information to be placed in the future and performing future inventory forecasts, it is possible to calculate recommended order quantities for the more distant future.

[0076] In step S305, the incoming goods calculation step performs the step of calculating incoming goods information, including the predicted incoming quantity, based on the shipping information of other users who trade the same goods. Specifically, the control unit 104 of the server 10 may refer to the shipping information held by other users (trading partners) who trade the same goods and correct the company's own predicted incoming quantity I2(t+n). Specifically, it obtains the actual shipping quantity D1 and the forecast shipping quantity D2 from the trading partner's shipping table 1023 and forecast table 1024. The actual shipping quantity D1 is reflected as the company's actual incoming quantity I1, and the forecast shipping quantity D2 is used as reference information to improve the accuracy of the predicted incoming quantity I2(t+n). This enables more accurate incoming goods forecasting based on information sharing with trading partners. The control unit 104 of the server 10 stores the predicted incoming quantity I2(t) in the predicted incoming quantity I2 item of the incoming goods table 1022. The control unit 104 of the server 10 stores the value of the predicted incoming quantity I2(t) over a predetermined period (e.g., six months to one year) in the predicted incoming quantity I2 item of the incoming quantity table 1022.

[0077] <Calculation of Forecasted Inventory Quantity S2> In step S306, the control unit 104 of the server 10 executes a forecasted inventory quantity calculation step to calculate the forecasted inventory quantity. The control unit 104 of the server 10 sequentially calculates the forecasted inventory quantity S2 from the present time t to a future lead time T days later. For the forecasted inventory quantity S2(t) at the present time t, the control unit 104 of the server 10 sets the actual inventory quantity S1(t) obtained from the inventory table 1021 as is. Next, the control unit 104 of the server 10 sequentially calculates the forecasted inventory quantity from the following day t+1 (a predetermined unit period, a predetermined cycle) onwards. The control unit 104 of the server 10 calculates the forecasted inventory quantity at each point in time by subtracting the unit forecast F from the previous day's forecasted inventory quantity and adding the forecast incoming quantity I2 for that day. The control unit 104 of server 10 calculates the predicted inventory quantity S2(t+1) on day t+1 (a predetermined unit period) by subtracting the unit estimate F from the predicted inventory quantity S2(t) on day t and adding the predicted incoming quantity I2(t+1) on day t+1 (a predetermined unit period). Similarly, the control unit 104 of server 10 calculates the predicted inventory quantity S2(t+2) on day t+2 by subtracting the unit estimate F from the predicted inventory quantity S2(t+1) on day t+1 (a predetermined unit period) and adding the predicted incoming quantity I2(t+2) on day t+2. S2(t) = S1(t) S2(t+1) = S2(t) - F + I2(t+1) S2(t+2) = S2(t+1) - F + I2(t+2) ... S2(t+T) = S2(t+T-1) - F + I2(t+T) The control unit 104 of the server 10 stores the predicted inventory quantity S2(t) in the predicted inventory quantity S2 item of the incoming table 1022. The control unit 104 of the server 10 stores the predicted inventory quantity S2(t) values ​​for a predetermined period (e.g., six months to one year) in the predicted inventory quantity S2 item of the incoming table 1022.

[0078] <Calculation of Recommended Order Quantity O2> In step S307, the control unit 104 of the server 10 executes an order calculation step to calculate the recommended order quantity for the transaction based on inventory information, order information, and forecast information. The order calculation step calculates the forecast inventory quantity after a predetermined period by subtracting the unit forecast from the actual inventory quantity and adding the forecast incoming quantity, and then executes a step to calculate the recommended order quantity based on the forecast inventory quantity. Specifically, the control unit 104 of the server 10 compares the forecast inventory quantity S2(t+T) calculated in step S306 with the first standard inventory quantity L. If the forecast inventory quantity S2(t+T) is less than the first standard inventory quantity L, the control unit 104 of the server 10 calculates the recommended order quantity O2(t). The recommended order quantity O2(t) is calculated as the value obtained by subtracting the forecast inventory quantity S2(t+T) from the second standard inventory quantity U. If the predicted inventory quantity S2(t+T) is equal to or greater than the first standard inventory quantity L, the control unit 104 of the server 10 sets the recommended order quantity O2(t) to 0. This is because it is determined that sufficient inventory is secured. The control unit 104 of the server 10 stores the calculated recommended order quantity O2(t) in the recommended order quantity O2 item of the order table 1025. The control unit 104 of the server 10 stores the value of the recommended order quantity O2(t) for a predetermined period (e.g., six months to one year) in the recommended order quantity O2 item of the order table 1025.

[0079] In step S307, the order calculation step performs the step of calculating the recommended order quantity by subtracting the estimated shipment quantity (planned shipment quantity) from the actual inventory quantity. Specifically, the control unit 104 of the server 10 calculates the estimated future shipment quantity based on the order information of other users (trading partners) who trade the same goods. The control unit 104 of the server 10 obtains future order plan information from the trading partner's order table 1025 and treats this as future forecast information (shipment forecast) for the company. The control unit 104 of the server 10 calculates the future predicted inventory quantity by subtracting the estimated shipment quantity from the current actual inventory quantity S1(t). Based on this predicted inventory quantity, the recommended order quantity O2(t) is determined using the procedure described above. This method makes it possible to create a more accurate order plan that directly reflects the ordering plans of trading partners.

[0080] In step S307, the order calculation step calculates the recommended order quantity based on order information, incoming goods information, and outgoing goods information entered by other users trading the same goods. Specifically, the control unit 104 of the server 10 calculates the recommended order quantity by utilizing transaction information shared among multiple users. The control unit 104 of the server 10 acquires order information from the order table 1025, incoming goods information from the incoming goods table 1022, outgoing goods information from the outgoing goods table 1023, and outgoing goods information from the outgoing goods table 1024, all entered by other users trading the same goods. By combining this information, the movement of goods throughout the entire supply chain is grasped. Specifically, order information from higher-level users is used as a forecast for future outgoing goods, and outgoing goods information from lower-level users is used as a forecast for incoming goods. This makes it possible to forecast supply and demand from a broader perspective that cannot be grasped with information from a single user alone.

[0081] In step S307, the control unit 104 of the server 10 executes a forecast calculation step to calculate forecast information, including the estimated shipment volume of the traded item, based on the order information of other users who trade the same traded item. Specifically, the control unit 104 of the server 10 obtains order information from the order table 1025 of other users (mainly higher-level users) who trade the same traded item, and uses this as forecast information, which is the company's future shipment forecast. The control unit 104 of the server 10 may also calculate a more accurate shipment forecast by taking into account past order patterns and seasonal fluctuations. This estimated shipment volume is recorded in the forecast table 1024 and used in the formulation of inventory plans.

[0082] In step S307, the control unit 104 of the server 10 executes a support information generation step, which generates support information to assist in making decisions regarding the replenishment of the goods being traded, based on the projected shipment quantity and inventory information. Specifically, the control unit 104 of the server 10 comprehensively analyzes the planned order quantity from higher levels and the company's own inventory status (projected future inventory quantity), incoming shipments (projected future incoming quantity), and other goods status information such as production capacity. Based on the results of this analysis, it generates support information that serves as a basis for making decisions regarding maintaining appropriate inventory levels and efficient ordering. The support information includes projected inventory trends, ordering timing, appropriateness of order quantities, and inventory shortage risk warnings. This information is used as an important indicator for managers to make appropriate ordering decisions.

[0083] In step S307, the support information generation step executes the step of generating support information, including recommended order quantities and recommended order timings for business partners (receiving parties). Specifically, the control unit 104 of the server 10 formulates an optimal ordering plan for receiving parties at lower levels. Specifically, based on the trend of the predicted inventory quantity S2(t+T), it calculates the recommended order quantity O2(t) at each point in time and the timing of the order. The recommended order quantity is calculated as the quantity needed to replenish the inventory up to the second standard inventory quantity when the predicted inventory quantity falls below the first standard inventory quantity. The timing of the order is determined considering the lead time of the receiving party and the company's own inventory status. This information is provided as concrete guidelines for ordering personnel to carry out ordering operations efficiently.

[0084] <Recommendation> In step S308, the control unit 104 of the server 10 executes a notification output step in which it outputs notification information if the predicted inventory quantity at the time after the lead time falls below the first standard inventory quantity. Specifically, the control unit 104 of the server 10 calculates the predicted inventory quantity S2(t+T) after lead time T days for the transaction target. If it is predicted that the predicted inventory quantity S2(t+T) will fall below the first standard inventory quantity L(t+T), the control unit 104 of the server 10 generates notification information for the transaction target. The control unit 104 of the server 10 outputs this warning notification to the user terminal 20. The control unit 204 of the user terminal 20 presents it as a recommended display D1031 on the management table screen D1, associated with the recommended order quantity O2. In addition, if the relevant notification information has been generated, the control unit 204 of the user terminal 20 presents it together with the recommended order quantity O2 on the order plan D312 of the transaction summary screen D3. The order plan D312 on the transaction summary screen D3 may be presented in association with the actual order quantity O1. The order plan D312 presents the order status, order date, order quantity, and delivery date in association. The warning notification may include information on the target product (storage location, supplier, product code, capacity), predicted inventory quantity S2, first standard inventory quantity L, second standard inventory quantity U, and the period when inventory shortages are predicted. Furthermore, it is preferable to set the importance of the warning according to the degree of inventory shortage and visually distinguish it using color coding or other means to attract the user's attention.

[0085] In step S308, the control unit 104 of the server 10 executes a recommendation suggestion step, which presents a recommended order quantity based on the recommended order quantity calculated in the order calculation step, in association with the predicted inventory quantity at the point after the lead time in the notification output step. Specifically, the control unit 104 of the server 10 presents information on the recommended order quantity O2(t) for the transaction item along with the warning notification. This recommended order information includes the quantity to be ordered, the recommended ordering timing, and the expected delivery date. The trend of the predicted inventory quantity when an order is placed is visually displayed in the inventory trend forecast D311 using a graph or the like, so that the validity of the ordering decision can be confirmed.

[0086] In step S308, the control unit 104 of the server 10 executes a support information output step that outputs support information for considering replenishment of goods. Specifically, the control unit 104 of the server 10 outputs comprehensive support information for considering replenishment of goods to support the user's ordering decision. This support information includes the following elements. As an analysis of the current inventory situation, the control unit 104 of the server 10 displays indicators such as the current actual inventory quantity S1(t), recent inbound and outbound records, and inventory turnover rate. As a future forecast, it displays the trend of the forecast inventory quantity S2(t+n), the planned forecast incoming quantity I2(t+n), and the shipment forecast based on the estimated outbound quantity D2 in a time series. Furthermore, as support information for ordering decisions, the control unit 104 of the server 10 presents the recommended order quantity O2(t), the optimal ordering timing, and a risk warning of inventory shortage. This information may also be output in an integrated dashboard format that combines tabular data, trend graphs, and warning displays. This enables the user to efficiently execute a series of decision-making processes, from understanding the current situation to future forecasting and considering specific actions.

[0087] <Data Integration Processing> Data integration processing is the process of integrating data with business partners.

[0088] <Overview of Data Integration Process> The data integration process is a series of processes that manage the customer master data, perform product code matching, send data integration requests, verify the data to be integrated, and control the data to be integrated.

[0089] <Details of Data Integration Process> The details of the data integration process are explained below.

[0090] In step S501, the control unit 104 of the server 10 executes a customer identification step. Specifically, the control unit 104 of the server 10 executes a process to identify the customer with whom data exchange will be performed. The control unit 104 of the server 10 refers to the user's hierarchy information (vehicle manufacturer, Tier 1, Tier 2, Tier 3) and identifies higher and lower tier companies with which it has a direct trading relationship. In identifying customer partners, the control unit 104 of the server 10 obtains a combination of supplier code and product code from the transaction master 1026 and identifies the customer system to be linked based on this. For example, the system of a Tier 2 company establishes a link with the system of a higher tier Tier 1 company and the system of a lower tier Tier 3 company.

[0091] In step S502, the control unit 104 of the server 10 executes a data format conversion step. Specifically, the control unit 104 of the server 10 executes a data format conversion process necessary for data exchange with the trading partner identified as the target of the collaboration. If the product code system, date format, etc., used in each company's system are different, the control unit 104 of the server 10 converts the data according to predefined conversion rules. Specifically, it converts order information, receiving information, and shipping information from the format of the company's own system to the format of the collaborating system. At this time, the control unit 104 of the server 10 refers to the transaction master 1026 and performs mutual conversion of product codes and standardization of units.

[0092] In step S503, the control unit 104 of the server 10 executes the linked data transmission step. Specifically, the control unit 104 of the server 10 transmits the data after the conversion process is complete to the linked system. The transmitted data includes the actual order quantity O1 from the order table 1025, the actual shipment quantity D1 and the estimated shipment quantity D2 from the shipment table 1023 and the forecast table 1024, and the actual receipt quantity I1 from the receipt table 1022. In the transmission process, to maintain data integrity, the control unit 104 of the server 10 adds a timestamp and a linked management number to the transmitted data. In addition, to prevent duplicate transmission or data loss, the transmission history is also managed.

[0093] In step S504, the control unit 104 of the server 10 executes a result confirmation step. Specifically, the control unit 104 of the server 10 confirms that the transmitted data has been successfully received and processed by the linked system. The control unit 104 of the server 10 receives a processing result notification sent from the linked system and determines whether the data linkage was successful or not. If an error occurs, the control unit 104 of the server 10 identifies the nature of the error (e.g., inconsistent data format, missing required items) and performs retransmission or correction processing as necessary. The results of the linkage process are also recorded as history and used as reference information in subsequent processing.

[0094] <Basic Hardware Configuration of Computer> Figure 17 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 includes at least a processor 901, main memory 902, auxiliary storage 903, and a communication IF 991 (interface). These are electrically connected to each other by a communication bus 921.

[0095] The processor 901 is hardware for executing the instruction set described in the program. The processor 901 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0096] The main memory 902 is for temporarily storing programs and data processed by programs, etc. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0097] The auxiliary storage device 903 is a storage device for storing data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, semiconductor memory, etc.

[0098] A communication interface (IF991) is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards. The network consists of various mobile communication systems, such as the Internet, LANs, and wireless base stations. For example, networks include 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi®) that can connect to the Internet via designated access points. When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via wired connections, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0099] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0100] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 17) is described below. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

[0101] Furthermore, the functional units of computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 interconnected via a network. The concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.

[0102] The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, loads them into the main memory device 902, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0103] The functions realized by the components described herein may be implemented in a circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the described functions. A processor, including transistors and other circuits, is considered a circuitry or processing circuitry. A processor may be a programmed processor that executes a program stored in memory. In this specification, circuitry, unit, and means are hardware programmed to realize or perform the described functions. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to realize or perform the described functions. If such hardware is a processor that is considered a type of circuitry, then such circuitry, means, or unit is a combination of hardware and software used to constitute such hardware and / or processor.

[0104] The memory unit is implemented by a main memory 902 and an auxiliary memory 903. The memory unit stores data, various programs, and various databases. The processor 901 can also reserve memory areas corresponding to the memory unit in the main memory 902 or the auxiliary memory 903 according to the program. The control unit can also cause the processor 901 to perform addition, update, and deletion operations on data stored in the memory unit according to the various programs.

[0105] The term "database" refers to a relational database, which is used to manage and associate data sets called tables and masters, which are structured in a tabular format defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters. Typically, each table and each master has a primary key column to uniquely identify a record, but setting a primary key for a column is not mandatory. The control unit can cause the processor 901 to add, delete, and update records in specific tables and masters stored in the storage unit according to various programs. Furthermore, by storing data, various programs, and various databases in the storage unit, the information processing device and information processing system described in this disclosure can be considered manufactured.

[0106] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

[0107] The communication unit is implemented by the communication IF 991. The communication unit implements the function of communicating with other computers 90 via the network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 901 to perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0108] <Note> The matters described in each of the above embodiments are noted below.

[0109] (Note 1) An information processing device comprising a processor and a memory unit, wherein the processor performs the following steps: forecast acquisition step (S301) to acquire forecast shipment quantities of items traded presented by a trading partner; inventory acquisition step (S301) to acquire inventory information of items traded in order to respond to orders from trading partners; support information generation step (S307) to generate support information to assist in making decisions regarding the replenishment of items traded based on the forecast shipment quantities and inventory information; and support information output step (S308) to output the support information. This enables efficient inventory management and ordering operations by calculating order information including suitable future recommended order quantities based on inventory, orders, and forecasts (informal announcements). Lower-level trading partners can receive support information including suitable future recommended order quantities according to the support information, enabling efficient inventory management and ordering operations.

[0110] (Note 2) The information processing device according to Note 1, wherein the processor performs an order acquisition step (S301) to acquire order information including actual order quantities to trading partners, the inventory acquisition step (S301) is a step to acquire inventory information including actual inventory quantities to trading partners, the forecast acquisition step (S301) is a step to acquire forecast information including forecast quantities to trading partners, and the support information generation step includes an order calculation step (S307) to calculate a recommended order quantity to trading partners based on inventory information, order information, and forecast information, and a step to generate support information relating to the recommended order quantity calculated in the order calculation step.

[0111] (Note 3) The information processing device described in Note 2, wherein the processor performs a unit forecast calculation step (S304) which calculates a unit forecast, which is the predicted shipment quantity per unit period, by dividing the predicted shipment quantity included in the forecast information by the forecast shipment period, and an arrival calculation step (S305) which calculates arrival information including the predicted arrival quantity of the transaction subject based on the actual order quantity and delivery date included in the order information, and the order calculation step (S307) which calculates the predicted inventory quantity after a predetermined period by subtracting the unit forecast from the actual inventory quantity and adding the predicted arrival quantity, and calculates the recommended order quantity based on the predicted inventory quantity.

[0112] (Note 4) The information processing device described in Note 3, wherein the processor performs a lead time acquisition step (S302) to acquire the lead time until the item to be traded arrives, and the arrival calculation step (S305) is a step in which the device calculates arrival information including the predicted arrival quantity for a second period, which is ahead of the first period, based on the recommended order quantity and lead time for the first period after the first period calculated in the order calculation step. This makes it possible to calculate order information including future recommended order quantities, taking into account the predicted arrival quantity estimated in line with future recommended order quantities. This makes it possible to calculate more accurate order information for the distant future.

[0113] (Note 5) The information processing device described in Note 3, wherein the processor performs a standard inventory acquisition step (S304) to acquire a first standard inventory quantity and a second standard inventory quantity that indicate the appropriate inventory level of the transaction target, and the incoming inventory calculation step (S305) is a step in which, if the predicted inventory quantity falls below the first standard inventory quantity, the recommended order quantity for a predetermined day is calculated with the difference between the second standard inventory quantity and the predicted inventory quantity as the upper limit. As a result, if the inventory quantity falls below the first standard inventory quantity, the recommended order quantity can be calculated so that the inventory quantity becomes the second standard inventory quantity. The inventory quantity can always be kept within the range from the first standard inventory quantity to the second standard inventory quantity. Under-inventory and excess inventory can be avoided.

[0114] (Note 6) The information processing device described in Note 3, wherein the processor performs an adjustment acquisition step (S304) to acquire forecast adjustment parameters for adjusting the unit forecast value, and the unit forecast calculation step (S304) includes a step of correcting the unit forecast based on the forecast adjustment parameters. This makes it possible to calculate the recommended order quantity while taking into account the accuracy of the forecast information (preliminary information). For example, for customers where the purchase quantity is expected (preliminarily indicated) to be less than the actual quantity, the unit forecast is corrected by multiplying it by a forecast adjustment parameter greater than 1. For example, for customers where the purchase quantity is expected (preliminarily indicated) to be more than the actual quantity, the unit forecast is corrected by multiplying it by a forecast adjustment parameter less than 1. This makes it possible to calculate the recommended order quantity more accurately.

[0115] (Note 7) The information processing device described in Note 6, wherein the processor performs a shipment acquisition step (S301) to acquire shipment information including the actual shipment volume of the transaction target, and an adjustment calculation step (S304) to calculate a forecast adjustment parameter based on the reliability of the forecast information by comparing the forecast information acquired in the forecast acquisition step with the shipment information, and the adjustment acquisition step (S304) is a step to acquire the forecast adjustment parameter calculated in the adjustment calculation step. This makes it possible to score the accuracy of the forecast information from trading partners by taking into account past shipment performance. The forecast adjustment parameter can be determined according to the calculated score. The recommended order quantity can be calculated more accurately by taking into account past actual shipment performance.

[0116] (Note 8) The information processing device described in Note 7 is an information processing device that calculates forecast adjustment parameters based on the reliability of forecast information for each trading partner or person in charge at said trading partner, as described in Note 7. This makes it possible to define forecast adjustment parameters in more detail for each trading partner and person in charge at that trading partner. It also makes it possible to calculate recommended order quantities more accurately by taking into account past actual shipment records.

[0117] (Note 9) An information processing device as described in Note 5, wherein the processor performs a notification output step (S308) in which it outputs notification information when the predicted inventory quantity falls below the first standard inventory quantity. As a result, a notification can be received if there is a risk that the predicted inventory quantity of the target product after the lead time will fall below the standard inventory quantity.

[0118] (Note 10) The information processing device described in Note 9, wherein the processor performs a recommendation suggestion step (S308) which suggests a recommended order quantity based on the recommended order quantity calculated in the order calculation step, in association with the predicted inventory quantity in the notification output step. This allows the user to receive a suitable recommended order quantity based on the predicted inventory quantity at a point after the lead time.

[0119] (Note 11) The information processing device described in Note 2, wherein the processor performs the step (S101) of acquiring order information, receiving information, and shipping information for each of multiple users, and the order calculation step (S307) is a step of calculating a recommended order quantity based on order information, receiving information, and shipping information entered by other users who trade the same goods. This enables efficient inventory management and ordering operations by linking order information, receiving information, and shipping information entered by multiple trading partners (users). It also enables more accurate calculation of order information, including suitable future recommended order quantities.

[0120] (Note 12) The information processing device described in Note 3, wherein the processor performs the step (S101) of acquiring shipping information for each of the shipments of multiple users, and the receiving calculation step (S305) is a step of calculating receiving information, including predicted receiving quantities, based on the shipping information of other users who trade the same goods. This enables efficient inventory management and ordering operations by linking order information, receiving information, and shipping information entered by multiple trading partners (users). Order information, including suitable future recommended order quantities, can be calculated more accurately.

[0121] (Note 13) The information processing device described in Note 3, wherein the processor performs the steps of acquiring order information for each of the orders of multiple users (S101), and calculating forecast information including the expected shipment quantity of the traded item based on the order information of other users trading the same traded item (S307), and the order calculation step (S307) is a step of calculating the recommended order quantity by subtracting the expected shipment quantity from the actual inventory quantity. This enables efficient inventory management and ordering operations by linking order information, receiving information, and shipping information entered by multiple trading partners (users). It is possible to calculate order information including the appropriate future recommended order quantity more accurately.

[0122] (Note 14) The information processing device described in Note 1 is an information processing device that generates support information, including recommended order quantities and recommended order timings, for business partners, in the support information generation step (S307). This allows the device to receive and present support information that assists in replenishing goods based on the arrival of goods, inventory status, etc., according to the planned order quantities from higher-level ordering parties.

[0123] (Note 15) A method executed by a computer comprising a processor and a memory unit, wherein the processor performs the following steps: forecast acquisition step (S301) to acquire forecast shipment quantities of goods to be traded presented by a trading partner; inventory acquisition step (S301) to acquire inventory information of goods to be traded in order to respond to orders from trading partners; support information generation step (S307) to generate support information to assist in making decisions regarding the replenishment of goods to be traded based on the forecast shipment quantities and inventory information; and support information output step (S308) to output the support information. This enables efficient inventory management and ordering operations by calculating order information including suitable future recommended order quantities based on inventory, orders, and forecasts.

[0124] (Note 16) A program to be executed by a computer having a processor and a memory unit, wherein the processor executes: a forecast acquisition step (S301) to acquire the forecast shipment quantity of the goods to be traded presented by a trading partner; an inventory acquisition step (S301) to acquire inventory information of the goods to be traded in order to respond to orders from trading partners; a support information generation step (S307) to generate support information to assist in making decisions regarding the replenishment of the goods to be traded based on the forecast shipment quantity and inventory information; and a support information output step (S308) to output the support information. This enables efficient inventory management and ordering operations by calculating order information including suitable future recommended order quantities based on inventory, orders, and forecasts.

[0125] 1 System, 10 Server, 101 Storage Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 User Terminal, 201 Storage Unit, 204 Control Unit, 206 Input Device, 208 Output Device

Claims

1. An information processing device comprising a processor and a memory unit, wherein the processor performs the following steps: forecast acquisition step of acquiring forecast shipment quantities of items to be traded presented by a trading partner; inventory acquisition step of acquiring inventory information of items to be traded in order to respond to orders from trading partners; support information generation step of generating support information to assist in making decisions regarding the replenishment of items to be traded based on the forecast shipment quantities and the inventory information; and support information output step of outputting the support information.

2. The information processing apparatus according to claim 1, wherein the processor performs an order acquisition step of acquiring order information including actual order quantities to trading partners, the inventory acquisition step of acquiring inventory information including actual inventory quantities of trading partners, the forecast acquisition step of acquiring forecast information including forecast quantities to trading partners, the support information generation step of an order calculation step of calculating a recommended order quantity for trading partners based on the inventory information, the order information, and the forecast information, and the support information generation step of generating support information relating to the recommended order quantity calculated in the order calculation step.

3. The information processing apparatus according to claim 2, wherein the processor performs a unit forecast calculation step of calculating a unit forecast, which is the predicted shipment quantity per unit period, by dividing the predicted shipment quantity included in the forecast information by the forecast shipment period, and an arrival calculation step of calculating arrival information including the predicted arrival quantity of the transaction subject based on the actual order quantity and delivery date included in the order information, wherein the order calculation step is a step of calculating the predicted inventory quantity after a predetermined period by subtracting the unit forecast from the actual inventory quantity and adding the predicted arrival quantity, and calculating the recommended order quantity based on the predicted inventory quantity.

4. The information processing apparatus according to claim 3, wherein the processor performs a lead time acquisition step of acquiring the lead time until the item to be traded arrives, and the arrival calculation step is a step of calculating the arrival information, including the predicted arrival quantity for a second period earlier than the first period, based on the recommended order quantity for the first period after the calculation in the order calculation step and the lead time.

5. The information processing apparatus according to claim 3, wherein the processor performs a standard inventory acquisition step of acquiring a first standard inventory quantity and a second standard inventory quantity indicating an appropriate inventory level for the subject of the transaction, and the incoming inventory calculation step is a step of calculating the recommended order quantity on a predetermined day, with the difference between the second standard inventory quantity and the predicted inventory quantity as the upper limit, when the predicted inventory quantity is less than the first standard inventory quantity.

6. The information processing apparatus according to claim 3, wherein the processor performs an adjustment acquisition step of acquiring an estimate adjustment parameter for adjusting the value of the unit estimate, and the unit estimate calculation step includes a step of modifying the unit estimate based on the estimate adjustment parameter.

7. The information processing apparatus according to claim 6, wherein the processor performs a shipment acquisition step of acquiring shipment information including the actual shipment volume of the transaction target, and an adjustment calculation step of calculating an estimate adjustment parameter based on the reliability of the estimate information by comparing the estimate information acquired in the estimate acquisition step with the shipment information, and the adjustment acquisition step is a step of acquiring the estimate adjustment parameter calculated in the adjustment calculation step.

8. The information processing apparatus according to claim 7, wherein the adjustment calculation step is a step of calculating the forecast adjustment parameter based on the reliability of the forecast information for each trading partner or person in charge at said trading partner.

9. The information processing apparatus according to claim 5, wherein the processor performs a notification output step of outputting notification information when the predicted inventory amount falls below a first standard inventory amount.

10. The information processing apparatus according to claim 9, wherein the processor performs a recommendation suggestion step of presenting a recommended order quantity related to the recommended order quantity calculated in the order calculation step, in association with the predicted inventory quantity in the notification output step.

11. The information processing apparatus according to claim 2, wherein the processor performs the steps of obtaining order information, receiving information, and shipping information for each of a plurality of users, and the order calculation step is the step of calculating the recommended order quantity based on the order information, receiving information, and shipping information entered by other users who trade the same transaction item.

12. The information processing apparatus according to claim 3, wherein the processor performs the steps of acquiring shipping information relating to each of the shipments of a plurality of users, and the incoming shipment calculation step is the step of calculating the incoming shipment information, including the predicted incoming shipment quantity, based on the shipping information of other users who trade the same goods.

13. The information processing apparatus according to claim 3, wherein the processor performs the steps of: acquiring order information relating to each of the orders of multiple users; and calculating forecast information including the estimated shipment quantity of the traded item based on the order information of other users trading the same traded item, and the order calculation step is a step of calculating the recommended order quantity by subtracting the estimated shipment quantity from the actual inventory quantity.

14. The information processing apparatus according to claim 1, wherein the support information generation step is a step of generating support information including a recommended order quantity and a recommended order timing for a business partner.

15. A method performed by a computer comprising a processor and a memory unit, wherein the processor performs: an estimate acquisition step of acquiring an estimated shipment quantity of a traded item presented by a trading partner; an inventory acquisition step of acquiring inventory information of a traded item to respond to an order from a trading partner; a support information generation step of generating support information to assist in making decisions regarding the replenishment of the traded item based on the estimated shipment quantity and the inventory information; and a support information output step of outputting the support information.

16. A program to be executed by a computer comprising a processor and a memory unit, wherein the processor executes: an estimate acquisition step of acquiring an estimated shipment quantity of a traded item presented by a trading partner; an inventory acquisition step of acquiring inventory information of a traded item in order to respond to an order from a trading partner; a support information generation step of generating support information to assist in making decisions regarding the replenishment of the traded item based on the estimated shipment quantity and the inventory information; and a support information output step of outputting the support information.

Images