Server device, information processing method, and program

The server device and method address the challenge of unclear product supply relationships by linking product information across supply chain tiers, facilitating accurate carbon footprint tracking and product tree generation, ensuring all companies can access necessary information.

WO2024232108A1PCT designated stage expired Publication Date: 2024-11-14TOYOTA JIDOSHA KK

Patent Information

Application Number
PCT/JP2023/026657
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-07-03
Filing Date
2023-07-20
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

In supply chain systems, it is difficult for companies to determine the completeness of product tree generation and track carbon footprints due to unclear product supply relationships between multiple companies, making it challenging to calculate total greenhouse gas emissions accurately.

Method used

A server device and method that stores product information from multiple companies, facilitating communication and linking of product information across the supply chain tiers, enabling the creation of a product tree by associating supply relationships and tracking carbon footprints through traceability-related information.

Benefits of technology

Enables clear understanding and tracking of product relationships within the supply chain, allowing for accurate calculation of carbon footprints and timely generation of product trees, ensuring all companies are aware of the linking status and can access relevant information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023026657_14112024_PF_FP_ABST
    Figure JP2023026657_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a server device that stores product information for each of a plurality of companies included in a supply chain by linking the same to the respective companies. According to the present invention, a first contact relating to a linking operation for linking product information about a target product to an account of a target company is received from an account of a downstream company of the target company, a process pertaining to the linking operation is executed in response thereto, and the status of the linking operation for the target product is reported to an account of a second downstream company positioned further downstream than the downstream company in association with first identification information included in the first contact. The process pertaining to the linking operation includes transmitting a second contact, relating to the linking operation for the product information about an upstream product to be linked to the product information of the target product, to an account of an upstream company of the target company, and the reporting of the status includes reporting second identification information in association with the first identification information.
Need to check novelty before this filing date? Find Prior Art

Description

Server device, information processing method, and program

[0001] The present disclosure relates to supply chains.

[0002] Systems for sharing information among a plurality of companies that make up a supply chain are known. In this regard, for example, Patent Literature 1 discloses a system for sharing information among companies included in a supply chain.

[0003] Japanese Patent Application Laid-Open No. 2004-171146

[0004] The present disclosure aims to make it easier to understand the linking status between products included in a supply chain.

[0005] One aspect of an embodiment of the present disclosure is a server device having a storage device that stores product information for each of a plurality of companies included in a supply chain, linking the product information for each company, and a control unit, wherein the control unit receives a first communication related to a linking operation for product information of a target product from an account of a downstream company of the target company, the first communication including first identification information, and sends the first communication to the account of the target company; and, in response to receiving the first communication, performs processing related to the linking operation; receives a status of the linking operation for the target product from the account of the target company, and notifies the status to an account of a second downstream company that is located further downstream than the downstream company, in association with the first identification information included in the received first communication; the processing related to the linking operation includes receiving a second communication related to a linking operation for product information of an upstream product to be linked to the product information of the target product, the second communication including second identification information, from the account of the target company, and sending the second communication to the account of the upstream company of the target company; and notifying the status includes notifying the account of the second downstream company in association with the first identification information.

[0006] One aspect of an embodiment of the present disclosure is an information processing method executed by a server device having a storage device that stores product information for each of a plurality of companies included in a supply chain, linked by company, and a control unit, the information processing method including the steps of: receiving, from an account of a downstream company of the target company, a first communication related to a linking operation for product information of a target product, the first communication including first identification information, and sending the first communication to the account of the target company; executing processing related to the linking operation in response to receiving the first communication; receiving, from the account of the target company, a status of the linking operation for the target product, and notifying the status to an account of a second downstream company that is located further downstream than the downstream company, in association with the first identification information included in the received first communication;

[0007] Another aspect of the present invention is a program for causing a computer to execute the above-described method, or a computer-readable storage medium that non-transitoryly stores the program.

[0008] According to the present disclosure, it is possible to easily grasp the linking status between products included in a supply chain.

[0009] 1 is a diagram illustrating a supply chain according to an embodiment. A diagram illustrating the relationship between products supplied by the supply chain. A diagram illustrating an overview of processing performed between a company terminal and a server device. A diagram illustrating an overview of processing performed between a company terminal and a server device in the first embodiment. A hardware configuration diagram of a server device according to an embodiment. A hardware configuration diagram of a company terminal according to an embodiment. A software configuration diagram of a server device according to an embodiment. An example of product information generated by a company terminal. A diagram illustrating linking of product information together. A diagram illustrating a product tree and the amount of carbon dioxide emitted in each process. An example of a screen outputting a product tree as an image. An example of a product tree when products for which the user does not have access authority are not disclosed. A flowchart of processing performed by a server device in the first embodiment. A flowchart of processing performed by a server device in the first embodiment. A diagram illustrating an overview of processing performed between a company terminal and a server device in the second embodiment. A flowchart of processing performed by a server device in the second embodiment.

[0010] In recent years, there has been a desire to track the amount of greenhouse gases emitted during the manufacture of products such as automobiles and batteries, that is, to track carbon footprints.

[0011] Consider a case where a product is supplied by a supply chain that includes multiple companies. In one example, at least some of the companies (intermediate suppliers) included in the supply chain may receive parts from one or more upstream companies, produce (including manufacturing) their own products using the received parts, and deliver the produced products to companies in the next process (downstream companies). The most upstream company may directly produce its own products and deliver the produced products to companies in the next process. Some companies in the supply chain may deliver products received from other companies directly to other companies (i.e., be involved in distribution). Multiple companies repeat this process, and the final product is obtained in the final process.

[0012] In the case of obtaining automobile-related products, the supply chain may consist of an OEM manufacturer and multiple suppliers. The OEM manufacturer may be the company that assembles the final product (the most downstream company), and the suppliers may be companies that supply parts, materials, assemblies, etc. to produce the product. The companies included in the supply chain may be determined depending on the product.

[0013] In the following explanation, parts and the like produced by each of the multiple suppliers will be referred to as "products," and the final product will be referred to as "final product." In one example, the final product may be supplied to a consumer. Furthermore, the suppliers and OEM manufacturers included in the supply chain will be simply referred to as "companies." Furthermore, each of the multiple tiers in the supply chain will be referred to as a "tier." In the following explanation, a specific tier in the supply chain will be expressed as a term such as Tier N. N represents the tier in the supply chain, and the smaller the number, the further downstream the position.

[0014] In such a system, for example, in order to calculate the total amount of greenhouse gases emitted in the manufacture of a final product, it is necessary to clarify the product supply relationships between multiple companies. This is because if the relationships between the multiple products that make up the final product are not clear, it is difficult to correctly calculate the total amount of greenhouse gases emitted in multiple processes.

[0015] One method for clarifying the product supply relationships between multiple companies is to collect information indicating the product supply relationships from each company in the supply chain. By collecting such information from all companies, it is possible to generate a tree (hereinafter referred to as a product tree) that shows the supply relationships between the multiple products that make up the final product. Furthermore, the generated product tree can be used to track carbon footprints (e.g., calculate greenhouse gas emissions). Furthermore, each company can obtain the generated information using the product tree.

[0016] However, when multiple companies in a supply chain provide information, it is difficult to determine how much information is needed to generate a product tree. For example, suppose a company in a certain tier (Tier N) provides information indicating the relationship between its own products and the products produced by a company in the next tier above (Tier N+1). Based on this information, the server determines the supply relationship between products between Tier N and Tier N+1. Similarly, when a company in Tier N+1 provides the relationship between its own products and the products produced by a company in Tier N+2, the server determines the supply relationship between products between Tier N+1 and Tier N+2. By repeating this process up to the most upstream tier, the final product tree can be determined.

[0017] However, each company that provided the information cannot know how far upstream the process of determining the supply relationships between products has been completed. Because the server device cannot generate a product tree unless the supply relationships for all products have been determined, each company cannot know when it will be able to obtain information about the product tree from the server device. The server device according to the present disclosure solves this problem.

[0018] A server device according to one aspect of the present disclosure includes a storage device that stores product information for each of a plurality of companies included in a supply chain, the product information being linked to each company, and a control unit. Specifically, the control unit executes the following operations: receiving a first message regarding a linking operation for product information of a target product from an account of a downstream company of the target company, the first message including first identification information, and transmitting the first message to the account of the target company; receiving a status of the linking operation for the target product from the account of the target company, and notifying the status to an account of a second downstream company located further downstream from the downstream company, the status being associated with the first identification information included in the received first message; receiving a second message regarding a linking operation for product information of an upstream product to be linked to the product information of the target product, the second message including second identification information, from the account of the target company, and transmitting the second message to the account of the upstream company of the target company; and notifying the status includes notifying the account of the second downstream company, the second identification information being associated with the first identification information.

[0019] The target company is a company that produces the target product. The target company is located upstream in the supply chain relative to the downstream company. Product information is information about the products produced by each company in the supply chain. The product information may include information for performing calculations related to traceability (traceability-related information). The traceability-related information may include, for example, the amount of greenhouse gases emitted and the amount of energy consumed when producing the target product.

[0020] The linking process is a process of associating product information of two products that have a supply relationship with each other. For example, the control unit performs a process of linking product information of a first product located downstream in the supply chain with product information of a second product located upstream (for example, a product used in manufacturing the first product, or a product included in the first product).

[0021] In the following explanation, a product located relatively downstream of a certain product in a supply chain will be referred to as a downstream product, and a product located relatively upstream of a certain product will be referred to as an upstream product. Furthermore, a company that manufactures a downstream product will be referred to as a downstream company, and a company that manufactures an upstream product will be referred to as an upstream company. Furthermore, a company located further downstream than a downstream company will be referred to as a second downstream company.

[0022] The first message is a message sent from the downstream company to the target company to cause the server device to perform a linking process for the target company's target product. The first message may be, for example, a request to link the target product with a downstream product manufactured by the downstream company. The first message includes first identification information for identifying the first message.

[0023] The server device sends the first message received from the downstream company to the target company's account and performs processing related to the linking operation for the target product based on the results of interaction with the account. The processing related to the linking operation includes not only the linking operation itself (e.g., processing to associate the target product with a downstream product) but also sending a second message to the upstream company. The second message may be a request for linking processing for an upstream product located upstream of the target product (e.g., processing to associate the target product with an upstream product). In this way, the target company that receives the first message uses the server device to link the downstream product with the target product and sends the second message to the upstream company. The second message includes second identification information for identifying the second message. By repeatedly performing this processing for multiple tiers, it is possible to link all upstream products (i.e., to determine the supply relationships between products).

[0024] The target company that receives the first notification may use a server device to perform processing related to the linking work and notify the account of the second downstream company of the status of the linking work. The second downstream company is a company located further downstream than the downstream company in the supply chain. As described above, the processing related to the linking work includes linking the target product and sending a second notification to the account of the upstream company located upstream of the target company. Therefore, the status notified to the second downstream company may include the status of the linking performed for the target product and the status of the second notification sent to the upstream company. Examples of the status related to the second notification include "to which company (or which tier company) the second notification was issued" and "which product (or which tier product) linking was completed in response to the second notification." The status related to the second notification may include information for identifying the second notification.

[0025] Furthermore, the server device may store first identification information for identifying the first contact and second identification information for identifying the second contact related to the first contact. The target company may also notify the status based on the association between the first identification information and the second identification information. This configuration makes it possible to track how far upstream the contact has propagated and, accordingly, how far the linking of product information has been completed.

[0026] If the target product is located at the top of the supply chain (also referred to as the end of the product tree), that is, if the target product is at the top of the product tree, the target company cannot send the second message because there is no upstream company from the target company's perspective. In this case, as a process related to the linking work, a terminal flag may be set in the product information of the target product. The terminal flag is a flag that identifies the target product as being at the end (top of the product tree) of the product tree.

[0027] In addition, the control unit may be configured to, in response to receiving the first notification, send the second notification to the upstream company's account after the linking process for the product information of the target product is completed. That is, after the relationship between product information in the downstream direction is determined, a request may be made to link product information in the upstream direction. With this configuration, a product tree can be sequentially created in a determined state from the downstream direction to the upstream direction.

[0028] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc. described in each embodiment are not intended to limit the technical scope of the disclosure to those configurations.

[0029] First Embodiment An information processing system according to this embodiment is a system that provides information about products supplied through a supply chain that includes multiple companies. The information about the products is typically information about traceability. Companies that belong to the supply chain may be determined appropriately depending on the attributes of the products, etc.

[0030] First, the structure of the supply chain will be described. FIG. 1 is a diagram illustrating an example of a supply chain according to this embodiment. The supply chain shown in FIG. 1 is composed of an OEM company and multiple supplier companies. In the example of FIG. 1, for example, a supply chain that manufactures automobiles themselves, batteries, and other automobile-related products is assumed. The OEM company assembles the final product. Multiple supplier companies (Companies A to C) supply parts, materials, assemblies, etc. for manufacturing the final product. Each of the multiple supplier companies produces one or more products and delivers them to a company one level below. The multiple companies repeat this process, and the final product is obtained in the final process (i.e., the OEM company).

[0031] In this embodiment, in each tier of the supply chain, the side that delivers products is referred to as the upstream side, and the side that purchases the products and produces new products is referred to as the downstream side. In this specification, companies located on the upstream side are referred to as upstream companies, and companies located on the downstream side are referred to as downstream companies. Furthermore, products produced by upstream companies are referred to as upstream products, and products produced by downstream companies are referred to as downstream products. Downstream products include upstream products. In this embodiment, the tiers included in the supply chain are referred to as Tiers. Tier 0 is the lowest tier (corresponding to OEM companies) that assembles final products, and Tiers 1, 2, and 3 transition to the upstream side. Depending on the tier being focused on, a downstream company may become an upstream company. For example, Company B, which belongs to Tier 2, is a downstream company in relation to Tier 3, but an upstream company in relation to Tier 1. In this way, the definitions of "upstream" and "downstream" may vary depending on the tier. Note that other companies may exist between the upstream and downstream companies, and other products may exist between the upstream and downstream products.

[0032] FIG. 2 is a diagram explaining the relationships between products supplied through a supply chain. Here, the supply relationships between multiple products that make up final product X are represented by a tree diagram. In this example, final product X is produced by assembling products A1, B1, C1, D1, etc. Product A1 is produced by assembling products A11, A12, A13, etc. In this way, the relationships between multiple products that make up a final product can be represented by a tree diagram in which each product is a node. Hereinafter, a tree diagram related to a specific final product will be referred to as a product tree.

[0033] The server device 1 according to this embodiment collects information about the products produced by each company (hereinafter referred to as product information) and information for linking the relationships between the product information from terminals (company terminals 2) corresponding to each company, and generates such a product tree based on this information. The product information also includes information about traceability (e.g., information about the amount of greenhouse gases emitted during the production of the product; hereinafter referred to as traceability-related information), which can be used to perform traceability-related processing.

[0034] As shown in FIG. 1 , the information processing system according to this embodiment includes a server device 1 and a plurality of company terminals 2 .

[0035] The company terminal 2 is a terminal corresponding to each of the multiple companies that make up the supply chain. The number of terminals corresponding to each company may be arbitrary. Furthermore, the terminal corresponding to the target company may include a terminal of a company (e.g., an agent company) that performs operations related to the target company.

[0036] The server device 1 collects information for generating a product tree from each of the multiple company terminals 2, and generates a product tree based on the collected information. Furthermore, the server device 1 can execute traceability-related processes (typically, processes for calculating total carbon dioxide emissions, etc.) based on the generated product tree. The server device 1 can also transmit the results of the processes to the company terminals 2.

[0037] Next, an overview of the process by which the server device 1 generates a product tree will be described with reference to Fig. 3. Fig. 3 is a diagram showing an overview of the process performed between the company terminal 2 and the server device 1. In the example of Fig. 3, it is assumed that there are a downstream company A and an upstream company B in an arbitrary hierarchy. It is assumed that company B produces product B and delivers it to company A, and company A produces product A using product B. That is, in the example of Fig. 3, product B is a child node of product A in the product tree.

[0038] The company terminal 2 corresponding to each company transmits information (product information) related to the products that the company produces to the server device 1. In this example, the company terminal 2 corresponding to company A transmits product information related to product A (referred to as product information A) to the server device 1. Similarly, the company terminal 2 corresponding to company B transmits product information related to product B (referred to as product information B) to the server device 1. The product information of each company is stored in the server device 1.

[0039] A product tree is generated, and a traceability process (e.g., CO 2In order to perform the process of calculating the amount of waste generated, the server device 1 needs to link the product information stored in the server device 1 together. Linking refers to associating the supply relationships between products. In the example shown, product A is produced using product B. That is, since there is a supply relationship between product A and product B, product information A and product information B are the targets of linking. By repeating this process for all products, the server device 1 can generate a product tree. Furthermore, the server device 1 becomes able to perform calculations related to traceability.

[0040] The operation for linking the product information stored in the server device 1 is performed by the company terminal 2. In one example, a person in charge of a downstream company (company A) logs in to the server device 1 from the company terminal 2 using the downstream company's account and sends a request (linking request) to the server device 1 to link the downstream products that are the company's products. The server device 1 then sends the linking request to the upstream company (company B) and causes the upstream company to perform processing to link the product information. For example, the linking request may include an ID that identifies the linking request (hereinafter, a request ID) and an identifier of the downstream product to be linked. Upon receiving the linking request, the server device 1 may send a request to the upstream company to have the upstream company respond with a product linked to the product related to the linking request. The server device 1 can link the product information (i.e., product information A and product information B) based on this information.

[0041] Although the example described here shows that the upstream company that receives the linking request replies with the product to be linked, and the server device 1 links the product information together, other methods may be adopted as long as the server device 1 can identify the product information to be linked. For example, the upstream company may reply to the downstream company with its own products that it is permitted to access, and the downstream company may select the product to be linked from the upstream products that it is permitted to access.

[0042] The server device 1 also notifies the downstream company (company A) of the linking results (status information) between the product information.

[0043] The process shown in FIG. 3 allows linking of product information at a specific tier in the supply chain. However, even if linking is completed at a specific tier, the product tree cannot be completed. For example, in the example of FIG. 2, a company belonging to Tier 1 (e.g., a company manufacturing product A1) can link a product belonging to Tier 1 with a product belonging to Tier 2 by sending a linking request to the server device 1. However, since the supply chain extends up to Tier 3, the product tree cannot be completed unless linking between products belonging to Tier 2 and Tier 3 is completed. Therefore, the server device 1 according to this embodiment repeatedly executes the process described with reference to FIG. 3 between multiple tiers.

[0044] FIG. 4 is a diagram illustrating this process. Here, three tiers, Tier N, Tier N+1, and Tier N+2, are illustrated. First, the account of company A, which belongs to Tier N, sends a linking request to server device 1. Server device 1 then sends the linking request to the account of company B, which belongs to Tier N+1. This linking request is an example of a "first contact." The linking request includes an ID (request ID) for identifying the linking request. The account of the upstream company (company B, which belongs to Tier N+1) interacts with server device 1 and links the product information (product information for product A, which belongs to Tier N, and product information for product B, which belongs to Tier N+1).

[0045] Next, company B's account issues a linking request to the upstream company from company B's perspective. This linking request is an example of a "second contact." For example, once company B has completed linking product A and product B, it issues a linking request to company C, which belongs to Tier N+2. Company C's account also similarly interacts with server device 1 and links the product information (product information for product B, which belongs to Tier N+1, and product information for product C, which belongs to Tier N+2).

[0046] In this example, since Product C is at the end of the product tree, Company C cannot issue a linking request any further upstream. Therefore, Company C sets a flag in the product information for Product C to indicate that it is at the end.

[0047] When a company that receives a linking request completes linking for its own product, it sends status information to downstream companies to notify them of the status of the linking process. For example, company C sends status information to company B via server device 1 to notify that "in response to the linking request with the received request ID, linking between product B and product C (located at the end of the product tree) has been completed."

[0048] Company B also sends status information to company A in a similar manner. However, because company B is positioned in the middle of the supply chain, it is unable to notify company A that linking has been completed up to the end of the product tree at the time that it has linked its own products. Therefore, in such a case, company B may withhold notification to company A until status information is sent from upstream (company C). In this case, company B may be triggered to send status information to company A when it receives status information from company C, the upstream company. With this configuration, all companies can recognize that "linking has been completed up to the end of the product tree."

[0049] The status information may be transmitted multiple times. For example, company B may transmit status information to company A to notify the current situation when the linking of its products is completed and when the status information is received from company C.

[0050] The status information may also include the ID (request ID) of a related linking request. For example, the status information sent from company B to company A may include the request ID of a linking request issued from company A to company B. This allows company A to recognize which linking request the received status information corresponds to. The status information sent from company B to company A may also include the request ID of a linking request issued upstream from company B (e.g., the request ID of a linking request issued from company B to company C). This allows company A to recognize the issuance status of linking requests upstream from company B and the corresponding statuses. In this way, the status information issued from company B to company A may include three types of data: (1) the ID of the linking request from company A to company B, (2) the ID of the linking request from company B to company C, and (3) the status of the linking process performed by company B.

[0051] [Hardware Configuration] Next, the hardware configuration of each device constituting the system will be described. Fig. 5 is a diagram schematically illustrating an example of the hardware configuration of the server device 1 according to this embodiment. The server device 1 is configured as a computer having a control unit 11, a storage unit 12, a communication module 13, and an input / output device 14.

[0052] The server device 1 can be configured as a computer having a processor (CPU, GPU, etc.), a main memory device (RAM, ROM, etc.), and an auxiliary memory device (EPROM, hard disk drive, removable media, etc.). The auxiliary memory device stores an operating system (OS), various programs, various tables, etc., and by executing the programs stored therein, various functions (software modules) that meet specific purposes, as described below, can be realized. However, some or all of the functions may be realized as hardware modules using hardware circuits such as ASICs and FPGAs.

[0053] The control unit 11 is a computing unit that executes predetermined programs to realize various functions of the server device 1. The control unit 11 can be realized by, for example, a hardware processor such as a CPU. The control unit 11 may also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0054] The storage unit 12 is a means for storing information and is composed of storage media such as RAM, a magnetic disk, and a flash memory. The storage unit 12 stores programs executed by the control unit 11, data used by the programs, etc. The storage unit 12 also has a database built therein, which stores product information collected from multiple company terminals 2 and account information related to the companies. Details will be described later.

[0055] The communication module 13 is a communication interface for connecting the server device 1 to a network. The communication module 13 may be configured to include, for example, a network interface board, a wireless communication interface for wireless communication, etc. The server device 1 can perform data communication with other computers (e.g., each company terminal 2) via the communication module 13.

[0056] The input / output device 14 is a means for accepting input operations performed by an operator and presenting information to the operator. Specifically, the input / output device 14 includes devices for input such as a mouse and a keyboard, and devices for output such as a display and a speaker. The input / output device may be integrally configured with, for example, a touch panel display.

[0057] The specific hardware configuration of the server device 1 may include omissions, substitutions, and additions of components as appropriate depending on the embodiment. For example, the control unit 11 may include multiple hardware processors. The hardware processor may be configured with a microprocessor, FPGA, GPU, etc. The input / output device 14 may be omitted, or an input / output device other than the example (e.g., an optical drive, etc.) may be added. The server device 1 may also be configured with multiple computers. In this case, the hardware configurations of the computers may or may not be the same.

[0058] 6 is a diagram illustrating an example of the hardware configuration of the company terminal 2 according to this embodiment. The company terminal 2 is configured as a computer having a control unit 21, a storage unit 22, a communication module 23, and an input / output device 24.

[0059] The company terminal 2 can be configured as a computer having a processor (CPU, GPU, etc.), a main memory device (RAM, ROM, etc.), and an auxiliary memory device (EPROM, hard disk drive, removable media, etc.), similar to the server device 1. However, some or all of the functions (software modules) may be realized as hardware modules using hardware circuits such as ASICs and FPGAs.

[0060] The control unit 21 is a computing unit that executes predetermined programs to realize various functions (software modules) of the company terminal 2. The control unit 21 can be realized by a hardware processor such as a CPU. The control unit 21 may also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0061] The storage unit 22 is a means for storing information, and is configured with storage media such as RAM, a magnetic disk, a flash memory, etc. The storage unit 22 stores programs executed by the control unit 21, data used by the programs, etc.

[0062] The communication module 23 is a communication interface for connecting the company terminal 2 to a network. The communication module 23 may be configured to include, for example, a network interface board, a wireless communication interface for wireless communication, etc. The company terminal 2 can perform data communication with other computers (e.g., the server device 1) via the communication module 23.

[0063] The input / output device 24 is a means for receiving input operations performed by an operator and presenting information to the operator. Specifically, the input / output device 24 includes devices for input such as a mouse and a keyboard, and devices for output such as a display and a speaker. The input / output device may be integrally configured with, for example, a touch panel display.

[0064] As with the server device 1, the specific hardware configuration of the company terminal 2 may be such that components are omitted, replaced, or added as appropriate depending on the embodiment.

[0065] [Software Configuration] Next, the software configuration of each device constituting the system will be described. FIG. 7 is a diagram schematically illustrating the software configuration of the server device 1 according to this embodiment. In this embodiment, the control unit 11 is configured to have three software modules: an information collection unit 111, a linking unit 112, and an information provision unit 113. Each software module may be realized by the control unit 11 (CPU) executing a program stored in the storage unit 12. Note that the information processing performed by the information collection unit 111, the linking unit 112, and the information provision unit 113 below is synonymous with the information processing performed by the control unit 11.

[0066] The information collection unit 111 is configured to collect product information from the company terminal 2 and execute a process of storing the product information in the storage unit 12. FIG. 8 is an example of product information collected by the information collection unit 111. The product information may be input via an operator of the company terminal 2. In this embodiment, the product information is configured to have fields for company ID, company name, product ID, and product name. The company ID and company name are the identifier and name of the company that produces the target product (i.e., the company that uses the company terminal 2). The product ID and product name are the identifier and name of the target product.

[0067] Furthermore, the product information is configured to include linking-related information. The linking-related information is information for identifying upstream products that are linked to the target product. In this embodiment, the linking-related information includes fields for "upstream product information" and "termination flag."

[0068] The upstream product information field is configured to store information for identifying product information corresponding to an upstream product linked to the target product (i.e., a product that is necessary to produce the target product and is included in the target product). The upstream product information field is used when the server device 1 links products together. Basically, at the stage when the product information is generated, the target product is not linked to an upstream product, so the upstream product information field does not need to store a value indicating the upstream product.

[0069] The terminal flag field is configured to store a flag indicating whether the target product is a leaf node, i.e., the node located at the most upstream (end) in the product tree. In this embodiment, because multiple company terminals 2 transmit product information, this flag is used to determine whether a product in the product tree is linked to additional products upstream or whether no further linking occurs (whether the target product is located at the most upstream). In other words, the terminal flag field is used when the server device 1 determines the linking between products. Basically, when the product information is generated, the linking relationship of the target product is undetermined, so the terminal flag field may store "0 (not currently the terminal)." Finally, to generate the product tree, the product information of each company stored in the server device 1 is set to either "linked to an upstream product" or "the terminal flag is set to "1."

[0070] Furthermore, the product information is configured to include traceability-related information. In one example, the traceability-related information may include the amount of materials (e.g., upstream products) used per unit production volume of the product, information on the recycling rate of specific raw materials, the amount of greenhouse gases emitted during the production of the product, due diligence-related information, or a combination thereof. The specific raw materials may be, for example, lithium, nickel, cobalt, lead, graphite, etc. The recycling rate may be expressed directly or indirectly, such as a combination of the total amount used and the amount of recycled material used. These values ​​correspond to the process of producing the target product. For example, in the example of FIG. 3 , the traceability-related information included in product information A stores the amount of greenhouse gases emitted during the production activities of product A. The traceability-related information included in product information A does not include information about the process leading up to the production of the upstream product (e.g., the amount of greenhouse gases emitted before upstream product B is produced).

[0071] The information collection unit 111 provides an interface for the operator of the company terminal 2 to input such information, and acquires product information.

[0072] As described above, the linking unit 112 receives a linking request from the account of a company belonging to a specific tier, and transmits the linking request to the account of a company belonging to an adjacent tier in the upstream direction.

[0073] The linking unit 112 also links the product information together by interacting with the account of the company that received the linking request. For example, the linking unit 112 is configured to interact with the company terminal 2 of the company that received the linking request, thereby acquiring information for linking the product information together from the company terminal 2. The linking unit 112 is further configured to execute a process of writing information indicating a linking relationship for the product information stored in the storage unit 12 based on the acquired information.

[0074] By repeating this process at multiple tiers, it is possible to link all products located upstream of the product of the company that first sent the linking request.

[0075] The linking request may include the ID of the linking request (an example of "first identification information" or "second identification information"), the company ID of the company that made the request, and the product ID of the product related to the request. The product ID is an identifier of the company's product to be linked. The linking request can also be said to be a request to link the company's product with an upstream product corresponding to the company's product.

[0076] As described above, a company that receives a linking request transmits status information to downstream companies once linking for its own products is complete. When the linking unit 112 receives status information from a specific company's account, it transmits the status information to the corresponding downstream company's account. The status information may notify the status of the linking process between adjacent tiers, or may notify the status of the linking process for upstream products (e.g., up to which tier products have been linked). The status information may include the ID of the related linking request. This allows the linking unit 112 to recognize the company to which the status information is being sent.

[0077] The information providing unit 113 is configured to perform information processing related to the product tree and output the results of the information processing. When the operator of the company terminal 2 requests the server device 1 to provide a product tree (and accompanying information), the information providing unit 113 performs the processing and provides the information to the company terminal 2. The information processing related to the product tree may include processing for performing calculations related to traceability for the product tree. Outputting the results of the information processing may include processing for providing information related to the generated product tree to the company terminal 2. In one example, the information providing unit 113 is configured to generate information related to the product tree and output the generated information about the product tree.

[0078] The storage unit 12 stores product information and account information transmitted from the company terminal 2. In this embodiment, an operator of each company logs in to the server device 1 via the company terminal 2 using the account of the corresponding company, thereby allowing interaction between the server device 1 and the company terminal 2. The account information is information relating to the account corresponding to each company constituting the supply chain. However, the method of accessing the server device 1 is not limited to this example, and may be selected as appropriate depending on the embodiment.

[0079] [Details of Processing] Next, a description will be given of specific content of the processing performed by the server device 1 and the company terminal 2. First, the linking processing performed by the linking unit 112 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the structure of a supply chain.

[0080] First, the information collection unit 111 of the server device 1 acquires product information from the company terminal 2. In the example of Fig. 9, the supply chain includes eight companies, and each of the eight companies transmits product information from its company terminal 2 to the server device 1. The product information acquired by the server device 1 is stored in the storage unit 12.

[0081] The linking unit 112 of the server device 1 receives a linking request from any of the company terminals 2. The linking request is sent from a company located downstream in the supply chain and is sent to an upstream company via the server device 1. An operator of the upstream company performs processing (such as providing information) to link the product of that company (downstream product) with a product located upstream (upstream product).

[0082] Here, it is assumed that the account of company A1 belonging to Tier 1 in FIG. 9 has sent a linking request to server device 1. The linking request includes the ID of the linking request (request ID), the ID of the company that sent the linking request, and the product ID of the target product. In the example of FIG. 9, company B1 (product B1), company B2 (product B2), and company B3 (product B3) belong to Tier 2, so product A1 is linked to three products. Therefore, in this example, three linking requests are sent.

[0083] The linking unit 112 of the server device 1 stores the received linking request in the storage unit 12. That is, the server device 1 stores the ID of the linking request, the company that sent the linking request, and the product related to the linking request in association with each other.

[0084] The linking unit 112 of the server device 1 also sends the received linking request to the account of the target company. The target company is a company that belongs to a tier one level higher than the downstream company and that performs linking between product information in response to a linking request from the downstream company. In the example of FIG. 9 , linking requests are sent to the accounts of companies B1, B2, and B3. The company accounts that receive the linking requests interact with the linking unit 112 and perform linking between product information. Here, it is assumed that the linking request addressed to company B1 is assigned a request ID of R001, the linking request addressed to company B2 is assigned a request ID of R002, and the linking request addressed to company B3 is assigned a request ID of R003.

[0085] A company that receives a linking request may transmit information for linking the product information to the linking unit 112, and the linking unit 112 may respond by updating the stored product information, thereby linking the product information. For example, the company terminal 2 of the target company may allow an operator to select a product to be linked to the product related to the linking request. For example, if the target company is company B1, the operator of company B1 may input information indicating that the upstream product of product A1 is product B1 via the input / output device 24. The company terminal 2 may transmit data identifying the upstream product (product B1) and the downstream product (product A1) to the linking unit 112.

[0086] As explained with reference to FIG. 8 , the product information has a field (linking-related information) related to the product to be linked. Based on the information transmitted from the target company, the linking unit 112 stores information corresponding to product information B1 (i.e., the upstream product) in the linking-related information contained in product information A1. For example, the linking-related information may store an identifier for the upstream product, an identifier for the company that produces the upstream product, and the like. Note that the linking-related information may also store a pointer to the product information to be linked. Through the process explained above, part of a tree structure is formed, with the product information for downstream products as parent nodes and the product information for upstream products as child nodes.

[0087] If the linked product is not at the end of the product tree, the account of the target company that performed the linking will issue a new linking request to an upstream company in order to further link the product upstream. In the example of Figure 9, the account of company B1 will issue a new linking request. This linking request is directed to a company in Tier 3. A request ID ("R011" in this example) is also assigned to this linking request.

[0088] A new linking request in the upstream direction may be issued when the following conditions are met: (1) The company's product (product B1 in this case) is registered in the server device 1; and (2) the company's product (product B1 in this case) has been linked to a downstream product (product A1 in this case).

[0089] Here, if a newly issued linking request is issued in response to a linking request sent from another company, the linking unit 112 stores the relationship between the linking requests. For example, in this example, a linking request with an ID of R011 is issued in response to a linking request with an ID of R001. The server device 1 associates and stores the ID "R001" (an example of "first identification information") of the linking request sent from company A1 with the ID "R011" (an example of "second identification information") of the linking request sent from company B1. Similarly, in the example of FIG. 9 , the server device 1 stores the relationships between R002 and R021, R002 and R022, and R002 and R023. Note that the IDs of the linking requests may be stored by the company terminal 2.

[0090] In this way, the server device 1 (or the company terminal 2) stores the relationship between the linking requests issued in a chain reaction. In this way, when a linking process is executed in a certain tier, the server device 1 (or the company terminal 2) can identify downstream companies related to the linking. For example, in the example of FIG. 9 , when linking is completed in response to a linking request identified by "R011," the server device 1 (or the company terminal 2) can identify the linking request identified by "R001." This allows the server device 1 (or the company terminal 2) to notify any downstream company of the status of the linking process performed in any tier. For example, it becomes possible to notify company A1 of information such as, "Linking up to Tier 3 has been completed in response to the linking request 'R001'."

[0091] In this embodiment, when linking is completed at a certain tier, the target company's account notifies the downstream company of the status of the linking process (sends status information) based on the ID of the linking request. The status information can be sent via the linking unit 112. The status information may, for example, notify that linking between product information items at that tier has been completed. Note that if there are multiple tiers and the linking process is performed sequentially for each tier, the status information may be sent each time, or the status information may be sent after linking up to the most upstream tier has been completed.

[0092] The status information may include, for example, any of the following: (A) A notification that linking between a downstream product and the company's product has been completed and a linking request has been issued to the upstream company; (B) A notification that linking between a downstream product and the company's product has been completed and a terminal flag has been set in the product information of the company's product (if the company's product is at the end of the product tree); (C) A notification that linking between a downstream product and the company's product has been completed and that linking between the company and the upstream company has been completed; (D) A notification that linking of all products located upstream of the company has been completed.

[0093] In addition to these notifications, the status information may include the ID of the linking request from the downstream company to the target company and the ID of the linking request from the target company to the upstream company. By notifying these request IDs, the above-mentioned notifications (A) to (C) may also be combined. The status information may be sent as a push notification to the target company's account, or may be sent when the target company's account logs in to the system.

[0094] Next, the processing performed by the information provider 113 will be described with reference to Figures 10 and 11. The information provider 113 of the server device 1 generates information about a product tree based on the stored product information and outputs the information about the product tree. Generating information about a product tree refers to the process of generating various information about products (e.g., information about traceability, an image showing the link relationships between products in a tree diagram, etc.) after links between nodes are formed by linking the product information together. This process of generating information about a product tree is an example of information processing about a product tree. In order to generate information about a product tree, it is necessary that all linking between product information has been completed. When such conditions are met, the information provider 113 can appropriately generate the information.

[0095] The product tree in this embodiment is a tree diagram that represents the supply relationships between product information items in a supply chain, as described with reference to Fig. 2. The information providing unit 113 can generate an image that represents the tree diagram based on the product information.

[0096] Furthermore, when generating information related to the product tree, the information providing unit 113 integrates the traceability-related information defined in each piece of product information and outputs the results.

[0097] Here, integration of traceability-related information will be described with reference to FIG. 10. In this example, the traceability-related information includes a value for tracking carbon footprints (hereinafter referred to as CFP values). FIG. 10 shows a table of multiple products that make up final product X and carbon dioxide (CO ) emitted in each process of producing these multiple products.2 For example, in the process of producing product A12 in the figure, A12 It is assumed that the target product is composed of three upstream products A121 to A123. In this way, upstream products included in a certain product are also called "included products." The total amount of carbon dioxide emitted until a certain target product is produced is calculated by referencing product information between companies in each of the two adjacent layers, from the most upstream product, which is a leaf node, to the target product, and calculating the CO2 emissions associated with the upstream products. 2 It can be obtained by repeating the process of passing the emissions on to downstream products.

[0098] In the example of FIG. 10, when the target product is A12, CO corresponding to the included products (upstream products A121 to A123) 2 The CO emissions corresponding to product A12 2 By adding this to the total CO emissions, the total amount of carbon dioxide emitted until the product A12 is produced can be calculated. 2 The emissions are as follows: A12 = E A12 +E A121 ×U A121 +E A122 ×U A122 +E A123 ×U A123 [g] where E A121 , E A122 , E A123 are the CO 2 emissions per unit amount when producing products A121, A122, and A123, respectively. 2 It is assumed that the amount of emissions is A121 , U A122 , U A123 are the amounts of products A121, A122, and A123 used in the production of product A12, respectively. These amounts are examples of the amount of material used per production volume of a product, which is included in the traceability-related information. 2 The amount of emissions can be obtained by sequentially performing the above calculations from the product of the most upstream company to the final product.

[0099] The integrated CFP value may be stored in the storage unit 12 separately from the product information, or may be included as part of the product information. A12 and the integrated emissions, I A12 It is also possible to hold both of these.

[0100] The CFP value after integration is used again when integration is performed for downstream products. By executing this process at each layer starting from the most upstream, the CFP value (for example, CO 2 Finally, the CFP value is passed down to the final product, and the CFP value (for example, the cumulative value of CO emissions) corresponding to the entire period until the final product is produced is obtained. 2 (total emissions) can be obtained.

[0101] In this way, when generating information related to the product tree, the information providing unit 113 repeatedly executes a process of sequentially integrating the CFP values ​​included in each piece of product information from the most upstream to the most downstream. Note that, in the above example, carbon dioxide emissions are used as an example of the information to be integrated, but the traceability-related information to be integrated may also be the recycling rate of a specified raw material, a due diligence score, etc. Note that, if the traceability-related information is numerical, the integration may be performed by numerical calculation, and if the traceability-related information is non-numerical information (e.g., due diligence-related information), the integration may simply be information collection.

[0102] The information provider 113 may output the generated product tree in image format. At the same time, traceability-related information corresponding to a given product may also be output. FIG. 11 shows an example of a screen on which the product tree is displayed as an image. The screen shown includes an image showing the supply relationships of multiple products that make up the final product in the form of a tree diagram. By selecting a given product, the user can view the traceability-related information corresponding to that product, or the integrated results of the traceability-related information corresponding to the entire period leading up to the production of that product (e.g., the total amount of carbon dioxide emissions from the upstream). Such information can be output via the input / output device 14 of the server device 1 based on the operation of the operator of the server device 1.

[0103] Furthermore, the information providing unit 113 may provide the generated product tree to the company terminal 2 in response to a request from the company terminal 2. Note that there are cases where it is not appropriate to disclose the entire product tree to a specific company. Therefore, when providing a product tree to the company terminal 2 corresponding to a certain company, the information providing unit 113 may perform processing to conceal the range for which the company does not have access authority.

[0104] For example, a company in a supply chain may want to keep its product information secret from other companies. To enable this, access rights to product information may be granted between companies. For example, a rule such as "only neighboring companies are granted access rights to its product information" may be set, and the server device 1 may publish the product tree in accordance with this rule. Access rights to specific product information may be set by an upstream company when the upstream company responds to a linking request sent from a downstream company. In this case, the server device 1 may determine which information to publish to which company based on information regarding access rights sent from the upstream company.

[0105] For example, in the example of Figure 10, the information providing unit 113 receives a product tree disclosure request from a company terminal 2 corresponding to a company that produces product A12. Here, it is assumed that the company in question has been granted access authority only for products A121, A122, and A123. In other words, the company in question cannot access product information other than those three products and downstream product A1. In this case, the information providing unit 113 provides the company terminal 2 with a product tree in which information about products for which the company does not have access authority is not disclosed.

[0106] 12 shows an example of a product tree in which products for which the user does not have access rights are not disclosed. In this example, the product tree is displayed with detailed information (or even the existence itself) of the not-disclosed products concealed.

[0107] In addition, in a case where the existence of a product is publicly disclosed, but access rights are not granted to only a specific item in the corresponding product information, confidentiality processing is performed only for that specific item, as indicated by the dotted line in the figure. In the example shown in the figure, it is indicated that the amount of carbon dioxide emissions during the production of product A121 is not disclosed.

[0108] On the other hand, even if there is a product (or item) in the tree for which you do not have access rights, the integration of traceability-related information described above is not affected by this. For example, in the illustrated example, the carbon dioxide emissions for product A121 are not disclosed, but this does not affect the process of calculating the total carbon dioxide emissions for product A12.

[0109] The information providing unit 113 may generate a product tree that has not been subjected to anonymization processing, and then perform anonymization processing for each company based on the access authority granted to each company, or may generate a product tree using the access authority of the relevant company. For example, when a product tree is requested by company A, the information providing unit 113 may extract information about one or more products that company A is permitted to access, and generate a product tree.

[0110] 13 and 14, the flow of processing executed by the server device 1 will be described. Fig. 13 is a flowchart of processing in which the server device 1 links product information together based on instructions from the company terminal 2.

[0111] In one example, the interaction between the server device 1 and the company terminal 2 is initiated when an operator of each company included in the supply chain logs in to the server device 1 using the account of the corresponding company via the company terminal 2. In this example, it is assumed that the operator of each company logs in to the server device 1 using the account of their own company.

[0112] It is assumed that, before starting the illustrated process, each company terminal 2 acquires its own product information via an operator and transmits the acquired product information to the server device 1. The product information transmitted to the server device 1 is received by the information collecting unit 111 and stored in the storage unit 12.

[0113] In step S11, the server device 1 (the linking unit 112) receives a linking request from any company terminal 2. Note that, here, the company that sent the linking request in step S11 (the company belonging to Tier N) is referred to as the "downstream company," and the company to which the linking request is sent (the company belonging to Tier N+1) is referred to as the "target company."

[0114] Steps S12 to S15 are steps for linking product information together in response to a linking request, and are executed based on instructions from the target company that received the linking request.

[0115] First, in step S12, the request ID included in the linking request received in step S11 is stored. If the linking request is generated in response to a linking request sent from another company, the linking unit 112 stores the relationship between the linking requests. This information may be shared with the company to which the linking request was sent.

[0116] In step S13, the linking unit 112 interacts with the target company to identify the product to be linked. In this step, the linking unit 112 sends the received linking request to the target company's account and interacts with the target company to collect information related to the linking. The operator of the company that received the linking request responds, for example, via the company terminal 2, with their own company's products that have a supply relationship with the specified product (the product specified by the downstream company). In this step, the operator of the target company may be prompted to specify a combination of downstream products and products linked to the downstream products. The company terminal 2 of the target company transmits a pair of identifiers of the product to be linked (the downstream product) and the product to be linked to the server device 1. This allows the server device 1 to identify the downstream and upstream products that are linked to each other. At this time, the response from the target company may be presented to the downstream company, allowing the operator of the downstream company to confirm the linking details. Furthermore, if there are multiple candidate products to be linked, the operator of the downstream company may be presented with options and allowed to select one. In this step, the target company may also grant downstream companies access rights to its product information.

[0117] In step S14, the linking unit 112 of the server device 1 updates the stored product information based on the linking request and the response thereto to reflect the linking details between the product information. Linking between product information may be performed by storing information about the linked product (identifier, pointer, etc.) in the linking-related information contained in the product information of the downstream product. Note that if the target product information is already linked when step S13 is executed, the processing of steps S13 and S14 may be skipped.

[0118] Once the linking between the product information is complete, in step S15, the linking unit 112 executes a process of notifying the downstream company of the linking status (sending status information). The status information may be generated by the linking unit 112 based on instructions from the target company's account, or may be generated by the target company's account and received from the company terminal 2. The status information may include, for example, "linking has been completed for the target Tier (or product)." The status information may also include the ID of the corresponding linking request. The destination of the status information is typically the company that sent the linking request in step S11. The destination of the status information may be identified based on the ID of the linking request. For example, in the example of FIG. 9, if linking is performed based on linking request "R001," the status information may be sent to company A1. The status information may include the ID (R001) of the linking request received from the downstream company and the ID (R011) of the linking request sent to the upstream company in response to the linking request.

[0119] Note that sending status information to the company that sent the linking request does not necessarily have to be performed in this step. As mentioned above, if the target company is located in the middle of the supply chain, the target company cannot notify downstream companies that linking to the end of the product tree is complete at the time the target company links its own products. In such a case, the target company may withhold notification to downstream companies until information is received from upstream (for example, until status information is sent from the upstream company). In this case, the target company may send status information to downstream companies when it receives status information from any upstream company.

[0120] The company to which the status information is sent can be identified by the ID of the linking request. For example, in the example of Figure 9, if linking is performed based on linking request "R011," the status information can be sent to the company corresponding to linking request "R001," i.e., company A1. In this way, since the server device 1 stores the relationships between linking requests, by tracing the information, it can identify downstream companies related to a certain linking request.

[0121] With this configuration, all companies can recognize that "linking has been completed all the way to the end of the product tree."

[0122] In step S16, the linking unit 112 determines whether the product linked by the linking request is located at the end of the product tree. For example, in the example of FIG. 9, a linking request is sent from company A1, and product A1 and product B1 are linked. Product B1 is located in the middle of the product tree, so this step results in a negative judgment. On the other hand, consider a case where a linking request is sent from company B1, and product B1 and product C1 are linked. Product C1 is located at the end of the product tree, so this step results in a positive judgment.

[0123] If the determination in step S16 is negative, the process proceeds to step S17, where a company in the next higher tier issues a linking request. For example, in the example of FIG. 9, a linking request is sent from company A1 in Tier 0 to company B1, linking product A1 with product B1. In this case, company B1 in Tier 1 issues a new linking request. When company B1 issues a linking request, the process of FIG. 13 is repeated.

[0124] If the determination in step S16 is affirmative, the process proceeds to step S18, where an end flag is set in the product information of the linked product (the product located in Tier N+1) identified in step S13. For example, in the example of FIG. 9 , a linking request is sent from company B1 belonging to Tier 0, and product B1 and product C1 are linked. Because product C1 is located at the end of the product tree, no further linking occurs. Therefore, to indicate this, the server device 1 sets an end flag in the product information of product C1 based on an instruction from company terminal 2 of company C1. In this case, the status information may include a notification that "the linking request has reached the company in the uppermost tier," "the linking process has been completed up to the end of the product tree," or "an end flag has been set in the product information of the product located at the end of the product tree."

[0125] The processes in steps S13 to S17 are an example of “processing related to the linking work.” That is, the processing related to the linking work includes processing for linking product information together (steps S13 to S14) and processing for sending a further linking request to the upstream company’s account (step S16).

[0126] 14 is a flowchart of a process in which the server device 1 provides information about a product tree. This process is started when the server device 1 receives a request from the company terminal 2.

[0127] First, in step S21, the server device 1 (information provider 113) receives a request for information about the product tree from the company terminal 2. The request includes, for example, an identifier of the target product. The target product may be a final product or another product (intermediate product). If the target product is a final product, the information request may be received from an OEM company, and if the target product is an intermediate product, the information request may be received from a company belonging to an intermediate tier in the supply chain.

[0128] Upon receiving the request, the server device 1 (information provider 113) generates information about the product tree by the process described above (step S22). At this time, the information provider 113 executes a process of integrating the traceability-related information defined in each piece of product information from the most upstream to the most downstream. The integration result is reflected in each piece of product information.

[0129] Next, in step S23, a process is performed to conceal information to which access rights have not been granted, based on the access rights held by the target company. For example, if the existence of product information of other companies has not been made public for a certain company, a process is performed to conceal the existence of that product information. Furthermore, if only specific items contained in the product information have not been made public, a process is performed to conceal the contents of those items. Information related to the concealed product tree is provided to the company terminal 2 and output (step S24).

[0130] The process of step S22 may be executed when the product tree is completed. In this case, the completion of the integration process of the traceability-related information may be notified to each company by status information.

[0131] As described above, in this embodiment, the server device 1 receives a linking request from any company belonging to the supply chain and performs linking between product information items based on the linking request. Furthermore, companies belonging to adjacent tiers can sequentially issue linking requests in an upstream direction, thereby enabling linking between product information items to be performed in a chain reaction from downstream to upstream.

[0132] Furthermore, the server device 1 stores the relationships between multiple linking requests issued in a chain reaction. This configuration makes it possible to track how far upstream the linking requests have propagated and, accordingly, how much of the linking between product information has been completed, and notify any downstream companies of this. This allows downstream companies to know when the product tree has been finalized and to appropriately obtain information about the product tree from the server device 1.

[0133] (Second embodiment) In the first embodiment, a downstream company sent a linking request to the account of a company (upstream company) belonging to an adjacent tier in the upstream direction, and the upstream company's account linked the product information together based on the linking request. Furthermore, when the linking between the product information together was completed, the upstream company's account sent status information to notify the company that sent the linking request of the linking status. That is, in the first embodiment, as shown in FIG. 4, status information was sent and received between companies belonging to adjacent tiers.

[0134] However, this method has the drawback of making it difficult to comprehensively check the linking status of the entire supply chain. For example, in the example shown in FIG. 1, the OEM, Company A, and Company B each issue a linking request, and each company receives corresponding status information from an upstream company in an adjacent tier. However, with this method, the OEM, which is located at the most downstream, cannot grasp the linking status upstream. For example, even if a company has not performed the operations to link product information and the product tree is therefore incomplete, the OEM cannot recognize this because it only receives status information from Company A. For an OEM in a position to oversee the supply chain, it is preferable to be able to grasp the linking status of multiple upstream companies (e.g., whether a linking request has propagated to the end of the product tree and whether all linking has been completed in response to the request).

[0135] To address this issue, in the second embodiment, when product information is linked in response to a linking request, status information indicating the linking status is sent to a specific company, rather than to the company that sent the linking request. The specific company can be a company (second downstream company) located downstream of the company that sent the linking request. In this embodiment, the specific company is the OEM company located at the bottom of the product tree.

[0136] 15 is a diagram illustrating the destination of status information in the second embodiment. In this embodiment, as in the first embodiment, the account of company A sends a linking request to the account of company B, and company B responds to this request and links the product information together. In addition, company B's account sends a linking request to company C's account, and company C's account responds to this request and links the product information together.

[0137] In the first embodiment, upon completion of the linking, Company B and Company C sent status information to downstream companies belonging to adjacent tiers (i.e., the companies that sent the linking requests).

[0138] On the other hand, in the second embodiment, status information is issued only by the company located at the top of the product tree. This status information is sent to the company located at the bottom of the product tree (i.e., the OEM company). The status information sent to the OEM company includes notifications that "linking has been completed up to the product located at the top of the product tree" and "a termination flag has been set in the product information of the product located at the top of the product tree." This allows the OEM company to recognize that the linking request has been propagated to the topmost tier and, in response to this, that linking between product information has been completed.

[0139] 16 is a flowchart of the process in which the server device 1 in the second embodiment links product information together based on instructions from the company terminal 2. In the second embodiment, the process of step S15 in FIG. 13 is omitted. That is, in this embodiment, the process of transmitting status information is not performed when product information is linked together at each Tier. Status information is generated and transmitted when a company located at the end of the product tree sets a terminal flag for the corresponding product information (step S19). This makes it possible to notify the OEM company that the linking request has reached the end of the product tree and, in response to this, that the linking between product information has been completed.

[0140] In this embodiment, an example is given in which a company located at the end of the product tree (the most upstream company) sends status information to the OEM company. However, the company sending the status information does not necessarily have to be the most upstream company. For example, one or more companies located in intermediate tiers may generate status information indicating that "linking up to that tier has been completed" and send it to the OEM company. By having an intermediate tier company send status information to the OEM company, the OEM company can recognize "up to which tier in the product tree linking has been completed." In this case, the server device 1 may execute the flowchart shown in FIG. 13 instead of the flowchart shown in FIG. 18. In this case, the status information generated in step S15 is sent to the OEM company. The status information may include the ID of the linking request received from the downstream company, the ID of the linking request sent to the upstream company, and the status of the linking process.

[0141] Furthermore, the destination of the status information does not necessarily have to be the OEM company (the most downstream company in the product tree). The destination of the status information can be any company located further downstream than the company that sent the linking request.

[0142] (Modifications) The above-described embodiment is merely an example, and the present disclosure may be modified as appropriate within the scope of the gist thereof. For example, the processes and means described in the present disclosure may be freely combined and implemented as long as no technical contradiction occurs.

[0143] Furthermore, in the description of the embodiment, the server device 1 stores the product information in a database, but the product information may be stored by means other than a database.

[0144] In the description of the embodiment, the status information notifying that the linking has been completed is transmitted when the linking is completed, but the status information may be transmitted when the linking is requested. Furthermore, the status information may be transmitted when a change in the linking relationship between product information in the corresponding Tier occurs.

[0145] In the embodiment, the status information includes the ID of the linking request issued by the downstream company to the target company. However, the status information may also include the ID of the linking request issued by the target company in the upstream direction. For example, in the example of FIG. 9 , assume that company B1 performs linking in response to a linking request issued by company A1. Furthermore, assume that company B1 issues a new linking request to company C1. In this case, the status information sent from company B1 to company A1 may include the ID of the linking request issued by company A1 (R001), or may include both the ID of the linking request issued by company A1 (R001) and the ID of the linking request issued by company B1 (R011). This configuration allows company A1 to recognize the issuance status of linking requests upstream from company B1.

[0146] Furthermore, the server device 1 may be configured to accept inquiries about the linking status at any tier using the linking request ID as a key. For example, the server device 1 may accept an inquiry from company A1 such as, "What is the current status of the linking request with ID R011?" In response to this, the server device 1 may provide company A1 with information such as, "Linking has been completed up to the tier immediately before the end of the product tree," or "Linking has been completed up to the end of the product tree." With this configuration, downstream companies can grasp the status of the product tree generation by inquiring of the server device 1 using the linking request ID notified by the status information. Furthermore, the server device 1 may manage previously issued linking requests and the status of status information transmission to downstream companies that sent the linking requests, and periodically transmit status information to downstream companies as needed.

[0147] In the embodiment, in response to a linking request sent from a certain company, each company relays the linking request, completing the product tree from downstream to upstream. However, linking between product information may be performed individually for each tier, without being triggered by the linking request. In this case, any company may send a linking status inquiry request to an upstream company as a first contact (second contact). In this case, the upstream company may respond to the inquiry request by providing the linking status of the tier to which the company belongs or of a tier upstream of the company. In this case, if the linking is incomplete, the upstream company may perform the linking process and then respond.

[0148] Although the embodiment has been described with an example of a three-tier supply chain as shown in FIG. 9 , the target supply chain may have four or more tiers. In this case, company A1 may send a linking request (first contact) to company B1, company B1 may send another linking request (second contact) to company C1, and company C1 may send yet another linking request (third contact) to a further upstream company (e.g., a company located at Tier 4). The server device 1 may relay these linking requests between companies and link product information based on instructions from each company.

[0149] Furthermore, in the description of the embodiment, it is assumed that each company's account issues a linking request (first contact or second contact), but the linking request may be generated by the server device 1 based on instructions from each company's account. This type of configuration is also included in "receiving a first contact from the account of a downstream company of the target company" and "receiving a second contact from the target company's account." Furthermore, in the description of the embodiment, it is assumed that each company's account issues status information, but the status information may be generated by the server device 1 based on instructions from each company's account. This type of configuration is also included in "receiving the status of the linking work from the target company's account."

[0150] In addition, in the description of the embodiment, the linking request includes the identifier of the downstream product to be linked, but the linking request may also include the identifiers of both the downstream product and the upstream product to be linked. If the product to be linked can be identified by the downstream company (by product number, etc.), the downstream company may also specify the upstream product. The server device 1 may interact with the upstream company in advance to obtain information specifying the upstream products that the downstream company is permitted to disclose, and provide the downstream company with a list of the upstream products that are permitted to be disclosed. The downstream company may also refer to the list to generate combinations of downstream products and corresponding upstream products.

[0151] In the embodiment, as shown in FIG. 8, the linking information is included in the product information. However, the linking information, i.e., information representing the linking relationships between products, may be stored separately from the product information. For example, data defining only the linking relationships without including specific product information may be stored separately from the product information. This data may also be accessible to all companies. In other words, only the structure of the product tree may be made public, and the specific data included in the product tree may be obtained according to the access rights granted to each company.

[0152] Furthermore, in the description of the embodiment, the server device 1 completes the product tree, but the role of the server device 1 may be distributed among multiple company terminals 2. For example, product information may be stored in a distributed database using a blockchain platform. In this case, a product information database may be configured by multiple company terminals 2. In this case, a smart contract may be used to execute the processing of each of the above-mentioned phases. For example, the execution of the linking process may be triggered by a company account writing a linking request to the database.

[0153] In the above embodiment, the multiple companies included in the supply chain are described as companies that produce products. However, the companies included in the supply chain do not necessarily have to be companies that produce products. For example, companies that transport, import, store, wholesale, etc. of products may also be included in the companies that make up the supply chain. In one example, some of the multiple companies may be companies that do not perform manufacturing processes, such as trading companies, sales agents, or import agents, and may receive products from companies located one level higher (upstream companies) and deliver them to companies located one level lower (downstream companies).

[0154] In the above embodiment, a supply chain for automobile-related products is assumed, and the OEM manufacturer is described as the most downstream company, and companies that supply parts, materials, assemblies, etc. are described as suppliers. However, the companies belonging to the supply chain are not necessarily limited to this. Companies at each stage may be determined appropriately depending on the product, etc. Furthermore, the manufacturing activities performed by each company until the final product is obtained may be determined appropriately depending on the embodiment, and may include, for example, all activities that may be performed until the final product is obtained, such as excavation, processing, assembly, transportation, and storage.

[0155] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0156] The present disclosure can also be realized by supplying a computer program that implements the functions described in the above embodiments to a computer, and having one or more processors in the computer read and execute the program. Such a computer program may be provided to the computer on a non-transitory computer-readable storage medium connectable to the computer's system bus or via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (e.g., a floppy disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, or any type of medium suitable for storing electronic instructions.

[0157] REFERENCE SIGNS LIST 1... Server device 2... Company terminal 11, 21... Control unit 12, 22... Storage unit 13, 23... Communication module 14, 24... Input / output device

Claims

1. A server device having a storage device that stores product information for each of a plurality of companies included in a supply chain, linking the product information for each company, and a control unit, wherein the control unit executes the following: receiving a first communication related to a linking operation for product information of a target product, the first communication including first identification information, from an account of a downstream company of the target company, and sending the first communication to the account of the target company; and executing a process related to the linking operation in response to receiving the first communication; receiving a status of the linking operation for the target product from the account of the target company, and notifying the status to an account of a second downstream company located further downstream than the downstream company, in association with the first identification information included in the received first communication; wherein the process related to the linking operation includes receiving a second communication related to a linking operation for product information of an upstream product to be linked to the product information of the target product, the second communication including second identification information, from the account of the target company, and sending the second communication to the account of the upstream company of the target company; and notifying the status includes notifying the account of the second downstream company in association with the first identification information.

2. The server device of claim 1, wherein, if the target product is located at the end of a product tree, the processing related to the linking work includes setting a terminal flag in product information of the target product, and notifying the status includes notifying the account of the second downstream company of information indicating that the terminal flag has been set by associating it with the first identification information, and, if the target product is not located at the end of a product tree, the processing related to the linking work includes sending the second communication including the second identification information to the account of an upstream company of the target company, and notifying the status includes notifying the account of the second downstream company of the second identification information by associating it with the first identification information.

3. The server device of claim 1 or 2, wherein the control unit, in response to receiving the first notification, sends the second notification to the upstream company's account after the linking work to the product information of the target product is completed.

4. The server device according to claim 1 or 2, wherein the storage device stores the first identification information and the second identification information associated with the first identification information.

5. A server device as described in claim 1 or 2, wherein the first contact includes a request to link the downstream product of the downstream company with the target product, and the second contact includes a request to link the target product with an upstream product of the upstream company.

6. The server device according to claim 5, wherein the first contact includes a request to inquire about a linking status of a product located upstream of the target product.

7. A server device as described in claim 1 or 2, wherein the control unit receives a third communication from the account of the upstream company that sent the second communication, the third communication including third identification information, regarding the linking work of the product information of the upstream product to product information of a further upstream product, and sends the third communication to the account of a company located upstream of the upstream company.

8. The server device according to claim 1 or 2, wherein the product information includes traceability-related information.

9. The server device according to claim 8, wherein the traceability-related information includes at least one of information regarding greenhouse gas emissions, a recycle rate for a given raw material, and a score regarding due diligence.

10. An information processing method executed by a server device having a storage device that stores product information for each of a plurality of companies included in a supply chain, linked by company, and a control unit, comprising the steps of: receiving a first communication related to a linking operation for product information of a target product, the first communication including first identification information, from an account of a downstream company of the target company, and sending it to the account of the target company; executing a process related to the linking operation in response to receiving the first communication; receiving a status of the linking operation for the target product from the account of the target company, and notifying the status to an account of a second downstream company located further downstream than the downstream company, in association with the first identification information included in the received first communication; wherein the process related to the linking operation includes the steps of receiving a second communication related to a linking operation for product information of an upstream product to be linked to the product information of the target product, the second communication including second identification information, from the account of the target company, and sending it to the account of the upstream company of the target company; and notifying the status includes a step of notifying the account of the second downstream company in association with the first identification information.

11. The information processing method of claim 10, wherein, if the target product is located at the end of a product tree, the processing related to the linking work includes setting a terminal flag in product information of the target product, and notifying the status includes notifying the account of the second downstream company of information indicating that the terminal flag has been set by associating it with the first identification information, and, if the target product is not located at the end of a product tree, the processing related to the linking work includes sending the second communication including the second identification information to the account of an upstream company of the target company, and notifying the status includes notifying the account of the second downstream company of the second identification information by associating it with the first identification information.

12. An information processing method as described in claim 10 or 11, further comprising the step of: in response to receiving the first communication, sending the second communication to the upstream company's account after the linking work to the product information of the target product is completed.

13. The information processing method according to claim 10 or 11, further comprising the step of storing, in the storage device, the first identification information and the second identification information associated with the first identification information.

14. An information processing method as described in claim 10 or 11, wherein the first contact includes a request to link the downstream product of the downstream company with the target product, and the second contact includes a request to link the target product with an upstream product of the upstream company.

15. The information processing method according to claim 14, wherein the first contact includes a request to inquire about the linking status of a product located upstream of the target product.

16. The information processing method of claim 10 or 11, further comprising the step of receiving a third communication from the account of the upstream company that sent the second communication, the third communication including third identification information, regarding the linking work of the product information of the upstream product to product information of a further upstream product, and sending the third communication to the account of a company located upstream of the upstream company.

17. The information processing method according to claim 10 or 11, wherein the product information includes traceability-related information.

18. The information processing method according to claim 17, wherein the traceability-related information includes at least one of information regarding greenhouse gas emissions, a recycle rate for a given raw material, and a due diligence score.

19. A program for causing the server device to execute the information processing method according to claim 10.

Citation Information

Patent Citations

  • Inter-enterprise data communication system and method in multi-stage supply chain

    JP2004171146A

  • Product environmental information sharing management device

    JP2006072404A

  • Traceability information collection method, traceability information collection system, purchase part information input terminal and product information input terminal

    JP2007193525A

  • Contained chemical substance information management system, supplier terminal, contained chemical substance information management method, and contained chemical substance information management program

    JP2009070257A

  • Information collection management system, computation machine, and information collection management method

    JP2021174419A

Cited By

  • Program, information processing method and system related to generation of supply chain tree

    WO2026105827A1