Server device, information processing method and program
The server device facilitates the creation of a product tree by linking product information across companies in a supply chain, ensuring accurate tracking of greenhouse gas emissions by sequentially associating products from downstream to upstream, addressing the challenge of incomplete product tree generation.
Patent Information
- Application Number
- JP2023149148
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-09
- Filing Date
- 2023-09-14
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-07-03
AI Technical Summary
Existing systems struggle to accurately determine the product supply relationships among multiple companies in a supply chain, making it difficult to calculate the total amount of greenhouse gases emitted during the manufacture of a final product, as each company cannot ascertain the completeness of the product tree generation process.
A server device that stores product information from each company in a supply chain and controls the linking of this information across companies, using identification information to facilitate the creation of a product tree by sequentially linking products from downstream to upstream, with status notifications to ensure completeness.
Enables the easy understanding and tracking of product linkage status within a supply chain, allowing for accurate calculation of carbon footprints and greenhouse gas emissions across multiple tiers.
Smart Images

Figure 2024162956000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to supply chains. [Background technology]
[0002] There is known a system for sharing information among a plurality of companies that make up a supply chain. In this regard, for example, Patent Document 1 discloses a system for sharing information among companies included in a supply chain. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2004-171146 A Summary of the Invention [Problem to be solved by the invention]
[0004] The present disclosure aims to make it easier to understand the linking status between products in a supply chain. [Means for solving the problem]
[0005] One aspect of the present disclosure is to 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 operations: receiving a first communication regarding 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 in response to receiving the first communication, executing a process related to the linking operation; 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 that is located further downstream than the downstream company, in association with the first identification information included in the received first communication; the process related to the linking operation includes receiving a second communication regarding 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 the present disclosure is to An information processing method executed by a server device having a storage device that stores product information on each of a plurality of companies included in a supply chain, linked by company, and a control unit, the method including 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 the first communication 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; the process related to the linking operation including 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 the second communication to the account of the upstream company of the target company; The information processing method includes a step of notifying the second identification information in association with the first identification information.
[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 non-transitoryly storing the program. Effect of the Invention
[0008] According to the present disclosure, it is possible to easily grasp the linking status between products included in a supply chain. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram illustrating a supply chain according to an embodiment. [Diagram 2] A diagram explaining the relationships between products supplied by a supply chain. [Diagram 3] FIG. 2 is a diagram showing an overview of processing performed between a company terminal and a server device. [Figure 4] FIG. 2 is a diagram showing an overview of processing performed between a company terminal and a server device in the first embodiment. [Diagram 5] FIG. 2 is a hardware configuration diagram of a server device according to the embodiment. [Figure 6] FIG. 2 is a hardware configuration diagram of a company terminal according to the embodiment. [Figure 7] FIG. 2 is a software configuration diagram of a server device according to the embodiment. [Figure 8] An example of product information generated by a company terminal. [Figure 9] FIG. 13 is a diagram for explaining linking between product information. [Figure 10] A diagram explaining the product tree and the amount of carbon dioxide emitted in each process. [Figure 11] An example of a screen that displays the product tree as an image. [Figure 12] An example of a product tree when products without access permissions are not disclosed. [Figure 13] 5 is a flowchart of a process performed by a server device in the first embodiment. [Figure 14] 5 is a flowchart of a process performed by a server device in the first embodiment. [Figure 15] FIG. 11 is a diagram showing an overview of processing performed between a company terminal and a server device in the second embodiment. [Figure 16] 10 is a flowchart of a process performed by a server device in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] In recent years, there has been a demand 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] Here, 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 to other companies as they are (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 products related to automobiles, the supply chain may be composed 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 supplier may be a company that supplies 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, etc. produced by multiple suppliers are referred to as "products." " and the final product is referred to as the "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 are simply referred to as "companies." Furthermore, each of the multiple tiers in the supply chain is referred to as a "tier." In the following explanation, specific tiers in the supply chain are referred to as Tier N. N represents the hierarchy in the supply chain, with a smaller number indicating a lower downstream 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. 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] In order to clarify the product supply relationships between multiple companies, there is a method of collecting 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 product tree) that indicates 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 (for example, to calculate greenhouse gas emissions). Furthermore, each company can obtain the information generated using the product tree.
[0016] However, when multiple companies in a supply chain are asked to provide information, it is difficult to determine how much information has been gathered to generate a product tree. For example, suppose that a company belonging to a certain Tier (Tier N) provides information indicating the relationship between its own products and products produced by a company belonging to the next higher tier (Tier N+1). Based on such information, the server device determines the supply relationship between products between Tier N and Tier N+1. Similarly, when a company belonging to Tier N+1 provides the relationship between its own products and products produced by a company belonging to Tier N+2, the server device 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 has provided information cannot know how far upstream the process of determining the supply relationships between products has been completed. Unless the supply relationships for all products are determined, the server device cannot generate a product tree, so 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 such a problem.
[0018] A server device according to one aspect of the present disclosure is a server device having a storage device that stores product information relating to products of each of a plurality of companies included in a supply chain, linking the product information to each company, and a control unit. Specifically, 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 transmitting the first communication to the account of the target company; in response to receiving the first communication, executing a process related to the linking operation; 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; and the process related to the linking operation is related to a linking operation for product information of an upstream product to be linked to the product information of the target product. and receiving a second communication including a second identification information from the target company's account and sending the second communication to an upstream company's account of the target company, the second communication including a second identification information, and notifying the status includes notifying the second identification information to the account of the second downstream company in association with the first identification information.
[0019] The target company is a company that produces the target product. The target company is located upstream of the downstream company in the supply chain. Product information is information about 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 operation is an operation for associating product information that has a supply relationship with each other. For example, the control unit performs a process for 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 the manufacture of the first product, or it may be 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 is referred to as a downstream product, and a product located relatively upstream of a certain product is referred to as an upstream product. Furthermore, a company that manufactures a downstream product is referred to as a downstream company, and a company that manufactures an upstream product is referred to as an upstream company. Furthermore, a company located further downstream than a downstream company is referred to as a second downstream company.
[0022] The first message is a message sent from the downstream company to the target company to have the server device perform a linking operation for the target product of the target company. The first message may be, for example, a request to link the downstream product manufactured by the downstream company with the target product. The first message includes first identification information for identifying the first message.
[0023] The server device transmits the first contact received from the downstream company to the account of the target company, and performs processing related to the linking work for the target product based on the result of interaction with the account. The processing related to the linking operation includes the linking operation itself (e.g., processing to associate the target product with a downstream product) as well as sending a second message to the upstream company. The second message may be a request for a linking process for an upstream product that is located upstream of the target product (e.g., processing to associate the target product with the 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 transmits a second message to the upstream company. The second message includes second identification information for identifying the second message. By repeatedly performing this process across multiple tiers, it is possible to link all upstream products (i.e., 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 may notify the account of the second downstream company of the status of the linking work. The second downstream company is a company that is located further downstream than the downstream company in the supply chain. As described above, the process of the linking operation includes linking the target product and sending a second message to the account of the upstream company that is upstream from the target company. Thus, the status notified to the second downstream company may include the status of the linking performed on the target product and the status of the second message sent to the upstream company. For example, the status of the second contact can be "Which company (or which tier) does the person belong to?" "Which product (or which product tier) has been linked in response to the second communication?" The status of the second communication may include information for identifying the second communication.
[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. With this configuration, it is possible to track how far the contact has propagated upstream and how far the linking between the product information has been completed accordingly.
[0026] If the target product is located at the most upstream of the supply chain (also called the end of the product tree), that is, if the target product is at the most upstream of the product tree, the second message cannot be sent 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 that the target product is located at the end (most upstream) of the product tree.
[0027] In addition, the control unit may be configured to, in response to receiving the first communication, send the second communication to the upstream company's account after the linking work to the product information of the target product is completed. In other words, after the relationships between the product information in the downstream direction are determined, a request may be made to link the product information in the upstream direction. With this configuration, a product tree can be 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 drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, and the like described in each embodiment are not intended to limit the technical scope of the disclosure to only those.
[0029] First Embodiment The information processing system according to the present embodiment is a system that provides information about products supplied through a supply chain including a plurality of companies. The information about the products is typically information about traceability. Companies that belong to the supply chain may be appropriately determined according to the attributes of the products, etc.
[0030] First, the structure of the supply chain will be described. FIG. 1 is a diagram for explaining 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 for manufacturing automobiles themselves and products related to automobiles such as batteries 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 the products to a company located one level lower. 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 hierarchical level of the supply chain, the side that delivers the product is referred to as the upstream side, and the side that purchases the product and produces a new product is referred to as the downstream side. In this specification, a company located on the upstream side is referred to as an upstream company, and a company located on the downstream side is referred to as a downstream company. In addition, a product produced by an upstream company is referred to as an upstream product, and a product produced by a downstream company is referred to as a downstream product. Downstream products include upstream products. In this embodiment, the layers in the supply chain are called Tiers. Tier 0 is the lowest layer that assembles the final product (corresponding to the OEM company). As they move from Tier 1 to Tier 2 to Tier 3, they move upstream. 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 differences between "upstream" and "downstream" Definitions may vary from tier to tier. It should be noted that there may be other companies between the upstream company and the downstream company, and there may be other products between the upstream product and the downstream product.
[0032] FIG. 2 is a diagram explaining the relationships between products supplied by 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.... Product A1 is produced by assembling products A11, A12, A13.... 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, the tree diagram relating to a specific final product will be referred to as a product tree.
[0033] The server device 1 according to this embodiment collects information on the products produced by each company (hereinafter, product information) and information for linking the relationships between the product information from the terminals (company terminals 2) corresponding to each company, and generates such a product tree based on these. The product information also includes information on traceability (for example, information on the amount of greenhouse gases emitted during the production of the product; hereinafter, traceability-related information), which can be used to perform processing related to traceability.
[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. In addition, 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 a process related to traceability (typically, a process for calculating the total amount of carbon dioxide emissions, etc.) based on the generated product tree. Also, the server device 1 can transmit the execution result of the process to the company terminal 2.
[0037] Next, an overview of the process in 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 is 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 becomes 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 it produces to the server device 1. In this example, the company terminal 2 corresponding to company A transmits product information related to product A (hereinafter 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 (hereinafter 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] Generate a product tree and perform traceability processing based on the generated product tree. (e.g., CO 2 In order to perform the process of calculating the amount of emissions, the server device 1 needs to link the product information stored in the server device 1 together. Linking refers to associating the supply relationship between products. In the illustrated example, 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. Also, the server device 1 becomes capable of performing calculations related to traceability.
[0040] An 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 at a downstream company (company A) logs into the server device 1 from the company terminal 2 using the downstream company's account, and transmits a request (linking request) for linking downstream products that are the company's products, to the server device 1. The server device 1 transmits the linking request to an upstream company (company B), and causes the upstream company to perform processing for linking the product information. For example, the linking request may include an ID for identifying the linking request (hereinafter, request ID) and an identifier of the downstream product to be linked. The server device 1 that receives the linking request may transmit 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 product information (i.e., product information A and product information B) based on this information.
[0041] In this example, 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, but 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 among the upstream products that it is permitted to access.
[0042] Furthermore, the server device 1 notifies the downstream company (company A) of the linking results (status information) between the product information.
[0043] The process shown in Figure 3 makes it possible to link product information together at a specific level in the supply chain. However, even if the pegging is completed at a certain level, the product tree cannot be completed. For example, in the example in Figure 2, companies belonging to Tier 1 (e.g., companies that manufacture product A1) However, by sending a linking request to the server device 1, it is possible to link products belonging to Tier 1 with products belonging to Tier 2. However, the supply chain in question extends up to Tier 3. Therefore, the product tree cannot be completed unless the linking between the products belonging to Tier 2 and the products belonging to Tier 3 is completed. Therefore, the server device 1 according to the present embodiment repeatedly executes the process described with reference to FIG. 3 between a plurality of Tiers.
[0044] FIG. 4 is a diagram explaining the process. Here, three Tier N, Tier N+1, and Tier N+2 are Illustrate the hierarchy. First, the account of company A belonging to Tier N sends a linking request to server device 1. The server device 1 transmits the linking request to the account of company B, which belongs to Tier N+1. The 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 belonging to Tier N+1) interacts with server device 1. This is done to link the product information (product information for product A belonging to Tier N and product information for product B belonging to Tier N+1).
[0045] Next, the account of company B issues a pegging request to the upstream company from the viewpoint of company B. This pegging request is an example of a "second contact." For example, when company B completes pegging of product A and product B, it issues a pegging request to company C, which belongs to Tier N+2. Issue a strike. Company C's account also interacts with the server device 1 in a similar manner, and executes linking between pieces of product information (product information of product B belonging to Tier N+1 and product information of product C belonging to Tier N+2).
[0046] In this example, since Product C is 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 the end.
[0047] When the company that received the linking request completes the linking of 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, the linking of product B and product C (located at the end of the product tree) has been completed."
[0048] Company B also transmits status information to company A in a similar manner. However, since company B is located 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. 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 the upstream company, company C. 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. Furthermore, the status information transmitted from company B to company A may include the request ID of a matching request issued upstream from company B (for example, the request ID of a matching request issued from company B to company C). This allows company A to recognize the issuance status of matching requests upstream from company B and the status of those requests. In this way, the status information issued by 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 that constitutes the system will be described. 1 is a diagram illustrating an example of a hardware configuration of a server device 1 according to an 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 .
[0052] The server device 1 can be configured as a computer having a processor (CPU, GPU, etc.), a main storage device (RAM, ROM, etc.), and an auxiliary storage device (EPROM, hard disk drive, removable media, etc.). The auxiliary storage device stores an operating system (OS), various programs, various tables, etc., and by executing the programs stored therein, various functions (software modules) that match a predetermined purpose, as described below, can be realized. However, some or all of the functions may be realized as hardware modules by hardware circuits such as ASICs and FPGAs.
[0053] The control unit 11 is a computing unit that executes a predetermined program to realize various functions of the server device 1. The control unit 11 can be realized by a hardware processor such as a CPU. The control unit 11 may also be configured to include a RAM, a ROM (Read Only Memory), a cache memory, and the like.
[0054] The storage unit 12 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 12 stores programs executed by the control unit 11, data used by the programs, etc. A database is also built in the storage unit 12, and product information collected from a plurality of company terminals 2 and account information relating to the company are stored in the database, which will be described in detail 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 (for example, each company terminal 2) via the communication module 13.
[0056] The input / output device 14 is a means for receiving an input operation 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 exemplified one (e.g., an optical drive, etc.) may be added. The server device 1 may 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 a 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, like the server device 1, includes a processor (CPU, GPU, etc.), a main memory device (RAM, ROM, etc.), an auxiliary memory device (EPROM, hard disk drive, removable 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 a predetermined program to realize various functions (software modules) of the company terminal 2. The control unit 11 can be realized by a hardware processor such as a CPU. The control unit 21 may also be configured to include a RAM, a ROM (Read Only Memory), a cache memory, and the like.
[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 the 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 corporate 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 corporate terminal 2 can perform data communication with other computers (for example, the server device 1) via the communication module 23.
[0063] The input / output device 24 is a means for receiving an input operation 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 showing a schematic 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 executing a program stored in the storage unit 12 by the control unit 11 (CPU). Note that the information processing executed by the information collection unit 111, the linking unit 112, and the information provision unit 113 below is synonymous with the information processing executed by the control unit 11.
[0066] The information collecting unit 111 is configured to execute a process of collecting product information from the company terminal 2 and storing the product information in the storage unit 12. FIG. 8 is an example of product information collected by the information collecting 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 an upstream product 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 identifies product information corresponding to the 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 configured to store information for linking products. 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 an upstream product.
[0069] The terminal flag field is configured to store a flag indicating whether the target product is a leaf node, i.e., a node located at the most upstream (end) in the product tree. In this embodiment, since multiple company terminals 2 transmit product information, this flag is used to determine whether a product in the product tree is linked to an additional product on the upstream side or no further linking occurs (whether the target product is located at the most upstream). That is, the terminal flag field is used when the server device 1 determines the linking between products. Basically, at the stage when the product information is generated, the linking relationship of the target product is not determined, so "0 (not currently the terminal)" may be stored in the terminal flag field. Finally, in order to generate the product tree, the product information of each company stored in the server device 1 is set to either a state of "linked to an upstream product" or "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 material (e.g., upstream products) used per production volume of the product, information on the recycling rate of a given raw material, greenhouse gas emissions emitted when producing the product, due diligence-related information, or a combination thereof. The given raw material 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 usage amount and the usage amount of recycled materials. These values correspond to the process for 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 in the production activities of product A. The traceability-related information included in product information A does not include information about the process up to the production of the upstream product (for example, the amount of greenhouse gases emitted up to the production of upstream product B).
[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] Furthermore, the linking unit 112 links product information together by interacting with the account of the company to which the linking request is sent. For example, the linking unit 112 is configured to acquire information for linking the product information with each other from the corporate terminal 2 of the company to which the linking request was sent, by interacting with the corporate terminal 2. Furthermore, the linking unit 112 is 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 in multiple tiers, linking can be performed for all products located upstream of the product of the company that first sent the linking request.
[0075] The linking request includes the ID of the linking request (an example of the "first identification information" or "second identification information"), the company ID of the company that made the request, and the product ID related to the request. The linking request may include the product ID of the product. The product ID is an identifier of the in-house product to be linked. It can also be said that the linking request is a request to link the in-house product with the upstream product corresponding to the in-house product.
[0076] As described above, a company that receives a linking request will send status information to downstream companies once the linking for its products is complete. When the linking unit 112 receives status information from the account of a specific company, 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 of an upstream product (for example, up to which tier the product that has been linked has been completed). The status information may include the ID of a related linking request. This allows the linking unit 112 to recognize the company to which the status information is to be sent.
[0077] The information providing unit 113 is configured to execute 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 associated information), the information providing unit 113 performs processing and provides the information to the company terminal 2. The information processing related to the product tree may include a process of performing a calculation related to traceability for the product tree. Outputting the result of the information processing may include a process of 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 related to 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 into the server device 1 using the account of the corresponding company via the company terminal 2, thereby causing interaction between the server device 1 and the company terminal 2. The account information is information related 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 appropriately selected depending on the embodiment.
[0079] [Processing details] Next, the specific contents of the processes performed by the server device 1 and the company terminal 2 will be described. First, the linking process performed by the linking unit 112 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of a supply chain structure.
[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 the 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 transmitted from a company located downstream in the supply chain, and is transmitted 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] In this example, the account of company A1, which belongs to Tier 1 in Figure 9, sends a linking request to the server equipment. Assume that the linking request was sent to location 1. The linking request includes the ID of the linking request ( The linking request contains the request ID, the ID of the company that sent the linking request, and the product ID of the target product. In the example in Figure 9, Tier 2 has Company B1 (product B1), Company B2 (product B2), and Company B3 (product B4). Since the product A1 belongs to the product B1 and the product B2, the 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] Furthermore, the linking unit 112 of the server device 1 transmits 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 the linking request from the downstream company. In the example of Fig. 9, the linking request is transmitted to the accounts of companies B1, B2, and B3. The company account that receives the linking request interacts with the linking unit 112 and executes linking between the 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 in response, the linking unit 112 may link the product information to each other by updating the stored product information. For example, the company terminal 2 of the target company may allow an operator to select a product linked to the product related to the linking request. For example, if the target company is company B1, the operator of company B1 can input, via the input / output device 24, information indicating that the upstream product of product A1 is product B1. The company terminal 2 may transmit to the linking unit 112 data for identifying the upstream product (product B1) and the downstream product (product A1).
[0086] As described 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 the product information B1 (i.e., the upstream product) in the linking related information held by the product information A1. For example, the linking related information stores an identifier of the upstream product, an identifier of 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, and the like. Through the above-described processing, a part of a tree structure is formed in which the product information of downstream products is the parent node and the product information of upstream products is the child node.
[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 proceed with the linking further upstream. In the example of Figure 9, the account of company B1 will issue a new linking request. The linking request will be sent to a company in Tier 3. The linking request is also assigned a request ID (in this example, "R011").
[0088] Note that a new linking request may be issued upstream if the following conditions are met: (1) The company's product (here, product B1) is registered on server device 1. (2) The linking of the company's product (here, product B1) with the downstream product (here, product A1) is complete.
[0089] Here, if the 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. 9, the server device 1 stores the relationships between R002 and R021, R002 and R022, and R002 and R023. The ID of the association request may be stored by the company terminal 2.
[0090] In this way, the server device 1 (or the corporate terminal 2) stores the relationship between the linking requests that are issued in a chain. In this way, when a process related to linking is executed in a certain Tier, the server device 1 (or the corporate 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 corporate terminal 2) can identify the linking request identified by "R001". This makes it possible for the server device 1 (or the corporate terminal 2) to notify any downstream company of the status of the linking process performed in any Tier. For example, information such as "linking has been completed up to Tier 3 in response to linking request "R001"" can be sent to company A1. This will enable the notification of information.
[0091] In this embodiment, when the linking is completed in 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 be, for example, a notification that linking between product information in the Tier has been completed. If there are multiple Tiers and linking processing is performed sequentially for each Tier, status information may be sent each time, or status information may be sent after linking up to the most upstream is completed.
[0092] The status information may include, for example, any of the following: (A) Notification that the linking of downstream products with our own products has been completed and a linking request has been issued to the upstream company (B) Notification that the linking of downstream products with your own product has been completed and a terminal flag has been set in the product information of your own product (if your own product is at the end of the product tree) (C) Notification that the linkage between the downstream product and your company's product has been completed and that the linkage between your company and the upstream company has been completed (D) Notification that pegging of all products upstream of your 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 notifications (A) to (C) may be combined. The status information may be sent by push notification to the target company's account, or may be sent when the target company's account logs into the system.
[0094] Next, the process performed by the information providing unit 113 will be described with reference to FIGS. The information providing unit 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 a 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 providing unit 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 in a supply chain, as described with reference to Fig. 2. The information providing unit 113 can generate an image representing 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 result.
[0097] Here, the 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, CFP values). FIG. 10 shows a table of a number of products that make up an end product X and carbon dioxide (CO 2 For example, in the process of producing product A12 in the figure, E A12 [g] of carbon dioxide is emitted. The product in question is also assumed to be composed of three upstream products A121 to A123. In this way, upstream products included in a certain product are also called "inclusive products." The total amount of carbon dioxide emitted until a certain target product is produced is calculated by calculating the CO2 emissions associated with upstream products between companies in each of the two adjacent layers, from the most upstream product, which is a leaf node, to the target product, while referring to product information. 2 This can be achieved 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, the CO corresponding to the included products (upstream products A121 to A123) 2 Emissions are calculated as the CO 2 By adding this to the CO2 emissions, we can calculate the total amount of carbon dioxide emitted until the product A12 is produced. That is, the integrated CO 2 The emissions are as follows: I A12 =E A12 +E A121 ×U A121 +E A122 ×U A122 +E A123 ×U A123 [g] Here, E A121 ,E A122 ,E A123 are the CO emissions per unit amount when producing products A121, A122, and A123, respectively. 2 The emission amount is assumed to be U A121 ,U A122 ,U A123are the amounts of materials used in the production of product A12, respectively. These amounts are an example of the amount of materials used per unit of production volume of a product, which is included in the traceability-related information. 2 The amount of emissions can be obtained by sequentially executing 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. That is, the product information corresponding to the product A12 includes the emission amount E A12 and the integrated emissions, I A12 It is also possible to hold both of the above.
[0100] The CFP value after integration is used again when implementing integration for downstream products. By executing this process at each level, starting from the most upstream, the CFP value (e.g., CO 2 Exclusion The CFP value is then passed on to the final product, and the CFP value (for example, the cumulative value of CO 2 The total emission of the
[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. In the above example, carbon dioxide emissions are exemplified as the subject of integration, but the traceability-related information to be integrated may be a recycling rate for a specified raw material, a score related to due diligence, etc. In addition, if the traceability-related information is a numerical value, the integration may be performed by a numerical calculation, and if the traceability-related information is information other than a numerical value (e.g., due diligence-related information), the integration may be simply information collection.
[0102] The information providing unit 113 may output the generated product tree in an image format. At the same time, traceability-related information corresponding to an arbitrary product may be output. FIG. 11 is an example of a screen on which the product tree is output as an image. The illustrated screen includes an image showing the supply relationship of multiple products constituting the final product in a tree diagram. By selecting an arbitrary product, it is possible to view the traceability-related information corresponding to the product, or the integrated result of the traceability-related information corresponding to the entire period up to the production of the product (for example, the total amount of carbon dioxide emissions from the most 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 a company terminal 2 corresponding to a certain company, the information providing unit 113 may perform a process of not disclosing a range for which the company does not have access authority.
[0104] For example, a company in a supply chain may wish to conceal its own product information from other companies. To make this possible, access rights to product information may be granted between companies. For example, a rule may be set such as "access rights to the company's product information are granted only to adjacent companies," and the server device 1 may publish the product tree in accordance with the rule. The access authority for a specific product information may be set by the upstream company when the upstream company responds to the linking request sent from the downstream company. In this case, the server device 1 may determine which information to disclose to which company based on the information on the access authority sent from the upstream company.
[0105] For example, in the example of FIG. 10, it is assumed that the information providing unit 113 receives a request to disclose a product tree from a company terminal 2 corresponding to a company that produces product A12. Here, it is assumed that the company has been granted access authority only for products A121, A122, and A123. In other words, the company 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 is an example of a product tree in the case where products for which there is no access authority are not disclosed. In this example, for undisclosed products, the product tree is displayed with detailed information (or even the existence itself) of the products concealed.
[0107] In addition, in a case where the existence of a product is disclosed, but access rights are not granted to only a specific item in the corresponding product information, the specific item is concealed, as shown by the dotted line in the figure. In the illustrated example, it is indicated that the amount of carbon dioxide emissions in producing product A121 is not disclosed.
[0108] On the other hand, even if a product (or item) to which you do not have access rights exists in the tree, the integration of traceability-related information described above is executed without being affected by this. For example, in the illustrated example, the carbon dioxide emission amount for product A121 is not disclosed, but this does not affect the process of calculating the total carbon dioxide emission amount for product A12.
[0109] The information providing unit 113 may generate a product tree that has not been subjected to the concealment process, and then perform the concealment process 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 one or more pieces of product information that company A is permitted to access, and generate a product tree.
[0110] [Processing flow] Next, the flow of the process executed by the server device 1 will be described with reference to FIGS. FIG. 13 is a flowchart of a process in which the server device 1 links pieces of product information together based on an instruction from the company terminal 2.
[0111] In one example, the interaction between the server device 1 and the company terminal 2 is started when an operator of each company 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 an operator of each company logs in to the server device 1 using the account of their 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 an arbitrary company terminal 2. In this case, the company that sent the linking request in step S11 (the company belonging to Tier N) is referred to as a "downstream company", and the destination of the linking request is A company (a company belonging to Tier N+1) is referred to as the "target company."
[0114] Steps S12 to S15 are steps for linking the product information together in response to the linking request. These steps 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 matching request received in step S11 is stored. If the matching request is generated in response to a matching request sent from another company, the matching unit 112 stores the relationship between the matching requests. This information may be shared with the company to which the matching request was sent.
[0116] In step S13, the linking unit 112 interacts with the target company to identify a product to be linked. In this step, the linking unit 112 transmits the received linking request to the account of the target company and interacts with the target company to identify the product to be linked. Collect information about the placement. The operator of the company that received the linking request responds, via the company terminal 2, for example, with their own 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 made to specify a combination of a downstream product and a product linked to the downstream product. The company terminal 2 of the target company transmits a pair of an identifier of the product that is the linking source (downstream product) and an identifier of the product that is the linking destination to the server device 1. This enables the server device 1 to identify the downstream product and the upstream product that are linked to each other. At this time, the response from the target company may be presented to the downstream company, and the operator of the downstream company may confirm the contents of the linking. Also, if there are multiple products that are candidates for linking, options may be presented to the operator of the downstream company to select one. In addition, in this step, the target company may 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 (identifier, pointer, etc.) about the linked product in the linking related information held by the product information of the downstream product. If the target product information has already been linked to each other at the time step S13 is executed, steps S13 and S14 may be skipped.
[0118] When the linking between the product information is completed, 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 an instruction 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, "binding has been completed for the target Tier (or product)." The status information may also include the ID of the corresponding binding 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 specified based on the ID of the linking request. 9, when matching is performed based on matching request "R001", status information can be sent to company A1. The status information may include the ID of the matching request received from the downstream company (R001) and the ID of the matching request sent to the upstream company in response to the matching request (R011).
[0119] Note that the status information does not necessarily have to be sent to the company that sent the linking request in this step. As mentioned above, when a target company is located in the middle of a supply chain, at the time when the target company links its own products, it is not able to notify downstream companies that linking has been completed up to the end of the product tree. In such a case, the target company may withhold notification to the downstream company until information from upstream is provided (e.g., until status information is sent from the upstream company). In this case, the target company may be triggered to send status information to the downstream company when it receives status information from any upstream company.
[0120] The company to which the status information is to be sent can be specified by the ID of the linking request. For example, in the example of FIG. 9, when linking is performed based on the linking request "R011", the status information can be sent to the company corresponding to the linking request "R001", that is, company A1. In this way, the server device 1 can Since the system stores the relationships between downstream companies, downstream companies related to a given linking request can be identified by tracing the information.
[0121] With this configuration, all companies can recognize that "linking has been completed up to the end of the product tree."
[0122] In step S16, the linking unit 112 determines whether or not the product linked by the linking request is located at the end of the product tree. For example, in the example of Fig. 9, assume that a linking request is sent from company A1 and product A1 is linked to product B1. Since product B1 is located in the middle of the product tree, the determination in this step is negative. On the other hand, consider a case where a linking request is sent from company B1 and product B1 is linked to product C1. Since product C1 is located at the end of the product tree, this step will result in a positive judgment.
[0123] If the determination in step S16 is negative, the process proceeds to step S17, in which a company in the next higher tier issues a linking request. For example, in the example in Figure 9, a linking request is sent from company A1, which belongs to Tier 0, to company B. In this case, the Tier 1 is sent to Tier 1, and product A1 and product B1 are linked. When the linking request is issued by company B1, the process of FIG. 13 is repeated.
[0124] If the determination in step S16 is positive, the process proceeds to step S18, in which the product information of the linked product (the product located in Tier N+1) identified in step S13 is added to the product information of the linked product. Set a flag. For example, in the example in Figure 9, a linking request is sent from company B1, which belongs to Tier 0. It is assumed that product B1 and product C1 are linked. Since product C1 is located at the end of the product tree, no further linking will occur. To indicate this, the server device 1 sets a terminal flag in the product information of product C1 based on an instruction from the 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 most upstream tier," "the linking process has been completed up to the end of the product tree," or "a terminal 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 a process of linking product information together (steps S13 to S14) and a process of 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 related to 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 on 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] The server device 1 (information providing unit 113) that receives the request generates information about the product tree by the above-mentioned process (step S22). At this time, the information providing unit 113 executes a process of integrating the traceability-related information defined in each product information from the most upstream to the most downstream. The result of the integration is reflected in each product information.
[0129] Next, in step S23, a process is executed to conceal information to which the access authority is not granted based on the access authority held by the target company. For example, when the existence of product information of other companies is not disclosed for a certain company, a process is executed to conceal the existence of the product information. Also, when only a specific item included in the product information is not disclosed, a process is executed to conceal the contents of the item. The information on the product tree that has been subjected to the concealment process 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 executes linking between product information based on the linking request. In addition, companies belonging to adjacent tiers issue linking requests in the upstream direction in sequence, so that linking between product information can be performed in a chain reaction from downstream to upstream.
[0132] Furthermore, the server device 1 stores the relationship between multiple linking requests issued in a chain reaction. With this configuration, it is possible to track how far the linking requests have propagated upstream and how much linking between product information has been completed accordingly, and to notify any downstream company 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 of 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] On the other hand, this method has the problem that it is difficult to check the overall linking situation from a bird's-eye view. For example, in the example of Figure 1, the OEM company, company A, and company B each make a linking request. Each company issues a status information table, and each company receives the corresponding status information from the upstream companies in the adjacent tier. However, with this method, the OEM company at the most downstream position cannot grasp the linking status in the upstream direction. For example, even if a company has not performed the operations to link product information with each other, and as a result the product tree is incomplete, the OEM company cannot recognize this. This is because the OEM company only receives status information from company A. When an OEM company is in a position to oversee the supply chain, it is preferable for it to be able to grasp the linking status of multiple upstream companies (for example, whether a linking request has been propagated to the end of the product tree, and whether all linking has been completed in response to this).
[0135] To address this issue, in the second embodiment, when product information is linked in response to a linking request, status information indicating the status of the linking is sent to a specific company, rather than to the company that sent the linking request. The specific company may be a company (second downstream company) located downstream of the company that sent the linking request. In this embodiment, the specific company is an OEM company located at the bottom of the product tree.
[0136] FIG. 15 is a diagram illustrating a transmission destination of status information in the second embodiment. In this embodiment, as in the first embodiment, company A's account sends a linking request to company B's account, and company B's account responds to this request and links the product information together. Company B's account also 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, at the timing when the linking was completed, company B and company C transmitted status information to downstream companies (that is, companies that transmitted linking requests) belonging to adjacent tiers.
[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. The 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 up to the topmost tier, and in response to this, linking between product information has been completed.
[0139] FIG. 16 is a flowchart of a process in which the server device 1 in the second embodiment links pieces of product information together based on an instruction 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 at the timing when the product information is linked to each other in each Tier. The 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 been propagated to the end of the product tree, and in response, that the linking between the product information has been completed.
[0140] In this embodiment, an example is given in which a company (topmost company) at the end of the product tree transmits the status information to the OEM, but the company transmitting the status information does not necessarily have to be the topmost company. For example, one or more companies at an intermediate tier may generate status information indicating that "linking has been completed up to that tier" and transmit it to the OEM. By a company at an intermediate tier transmitting status information to the OEM, the OEM 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 destination of the status information generated in step S15 is the OEM. The status information may include the ID of the linking request received from the downstream company, the ID of the linking request transmitted to the upstream company, and the status of the linking process.
[0141] Furthermore, the destination of the status information is not necessarily the OEM (the lowest The destination of the status information does not have to be a company that is located downstream from the company that sent the linking request.
[0142] (Modification) The above embodiment is merely an example, and the present disclosure may be modified as appropriate without departing from the spirit and scope of the present disclosure. 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 the completion of the linking is transmitted at the timing when the linking is completed, but the status information may be transmitted at the time when the linking is requested. Furthermore, the status information may be transmitted when a change in the linking relationship between the product information in the corresponding Tier is triggered.
[0145] In addition, in the description of the embodiment, the status information includes the ID of the linking request issued from the downstream company to the target company, but the status information may also include the ID of the linking request issued by the target company in the upstream direction. 9, it is assumed that company B1 has performed matching in response to a matching request issued by company A1, and that company B1 has issued a new matching 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 enables company A1 to recognize the status of linking request issuance upstream from company B1.
[0146] Furthermore, the server device 1 may be configured to receive an inquiry about the linking status at any Tier using the ID of the linking request as a key. For example, the server device 1 may receive 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." According to this configuration, the downstream company can grasp the generation status of the product tree by making an inquiry to the server device 1 using the ID of the linking request notified by the status information. Furthermore, the server device 1 may manage previously issued linking requests and the transmission status of status information to downstream companies that sent the linking requests, and may periodically transmit status information to downstream companies as necessary.
[0147] In the embodiment, when a linking request is sent from a certain company, each company relays the linking request to complete the product tree from downstream to upstream. However, linking between product information may be performed individually for each tier without being triggered by a linking request. In this case, any company may send an inquiry request for the linking status to an upstream company as a first contact (second contact). In this case, the upstream company may respond to the inquiry request by replying with the linking status of the tier to which the company belongs or upstream of the company. At this time, if the linking is incomplete, the upstream company may The answer may be given by a question.
[0148] In addition, in the description of the embodiment, an example in which there are three tiers as shown in FIG. 9 has been shown, but the target supply chain may have four or more tiers. In this case, company A1 sends a matching request (first contact) to company B1, which sends another matching request (second contact) to company C1, which sends yet another matching request (third contact) to a further upstream company (e.g., a company located in Tier 4). The server device 1 can relay these linking requests between the companies and link the product information together based on instructions from each company.
[0149] In addition, in the description of the embodiment, 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 form 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 account of the target company." In addition, in the description of the embodiment, the account of each company issues the status information, but the status information may be generated by the server device 1 based on an instruction from the account of each company. This form is also included in "receiving the status of the linking work from the account of the target company."
[0150] In the embodiment, the linking request includes an identifier of the downstream product to be linked, but the linking request may include identifiers of both the downstream product and the upstream product to be linked. If the product to be linked can be specified by the downstream company (by product number, etc.), the downstream company can also specify the upstream product. The server device 1 may interact with the upstream company in advance, acquire information specifying the upstream products that are permitted to be disclosed to the downstream company, and provide the downstream company with a list of the upstream products permitted to be disclosed. The downstream company may refer to the list to generate combinations of downstream products and corresponding upstream products.
[0151] In the description of the embodiment, the linking related information is included in the product information as shown in FIG. 8, but the linking related information, i.e., information that indicates the linking relationship between products, may be stored separately from the product information. For example, data that does not include specific information about the products and only defines the linking relationship 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 specific data included in the product tree may be obtained according to the access authority granted to each company.
[0152] In addition, 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 a plurality of 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 a plurality of 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 certain company's 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 manufacture products. However, the companies included in the supply chain do not necessarily have to be companies that manufacture 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 carry out manufacturing processes, such as trading companies, sales agents, and import agents. A downstream company may receive products from a company one level above it (an upstream company) and deliver products to a company one level below it (a downstream company).
[0154] In addition, in the above embodiment, assuming a supply chain for products related to automobiles, 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 appropriately determined depending on the product, etc. Furthermore, the manufacturing activities performed by each company until the final product is obtained may be appropriately determined 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, storage, etc.
[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 one 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 implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, and any type of medium suitable for storing electronic instructions. [Explanation of symbols]
[0157] 1. Server device 2. Corporate terminals 11,21 Control section 12,22...Storage section 13,23...Communication module 14,24... Input / Output Device
Claims
1. A server device having a storage device that stores product information relating to products of each of a plurality of companies included in a supply chain, the product information being associated with each company, and a control unit, The control unit is receiving a first communication from an account of a downstream company of the target company regarding a linking operation of the target product to product information, the first communication including first identification information, and sending the first communication to the account of the target company; In response to receiving the first contact, executing a process related to the linking operation; receiving a status of the linking work of the target product from the target company's account, 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; Run The process relating to the linking operation includes receiving a second communication relating 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 an account of the target company and sending the second communication to an account of an upstream company of the target company; notifying the status includes notifying the second downstream company's account of the second identification information in association with the first identification information. Server device.
2. If the target product is located at the end of the product tree, The processing related to the linking work includes setting a termination flag in product information of the target product, Notifying the status includes associating information indicating that the termination flag has been set with the first identification information and notifying the account of the second downstream company; If the target product is not at the end of the product tree, The process for the linking operation includes sending the second communication including the second identification information to an account of an upstream company of the target company; notifying the status includes notifying the second downstream company's account of the second identification information in association with the first identification information. The server device according to claim 1 .
3. In response to receiving the first notification, the control unit transmits the second notification to the upstream company's account after completing the linking operation for the product information of the target product.
3. The server device according to claim 1 or 2.
4. the storage device stores the first identification information and the second identification information associated with the first identification information; 3. The server device according to claim 1 or 2.
5. the first contact includes a request to link a downstream product of the downstream company to the target product; The second contact includes a request to link the target product with an upstream product of the upstream company.
3. The server device according to claim 1 or 2.
6. The first contact is a linking status inquiry link for a product located upstream of the target product. Including quests, The server device according to claim 5.
7. The control unit receives a third communication from the account of the upstream company that sent the second communication, the third communication being related to a linking operation of the product information of the upstream product with product information of a further upstream product, the third communication including third identification information, and sends the third communication to an account of a company that is located upstream of the upstream company.
3. The server device according to claim 1 or 2.
8. The product information includes traceability related information; 3. The server device according to claim 1 or 2.
9. The traceability-related information includes at least one of information on greenhouse gas emissions, a recycling rate for a given raw material, and a due diligence score; The server device according to claim 8.
10. An information processing method executed by a server device having a storage device that stores product information relating to products of a plurality of companies included in a supply chain in association with each company, and a control unit, comprising: receiving a first communication from an account of a downstream company of the target company regarding a linking operation of the target product to product information, the first communication including a first identification information, and sending the first communication to the account of the target company; In response to receiving the first contact, executing a process related to the matching operation; receiving a status of the linking process for the target product from the target company's account, 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; Including, The processing related to the linking work includes a step of receiving a second communication related to a linking work 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 an account of the target company, and sending the second communication to an account of an upstream company of the target company; notifying the status includes a step of notifying the second downstream company of the second identification information in association with the first identification information; Information processing methods.
11. If the target product is located at the end of the product tree, The processing related to the linking work includes setting a termination flag in product information of the target product, Notifying the status includes associating information indicating that the termination flag has been set with the first identification information and notifying the account of the second downstream company; If the target product is not at the end of the product tree, The process for the linking operation includes sending the second communication including the second identification information to an account of an upstream company of the target company; notifying the status includes notifying the second downstream company's account of the second identification information in association with the first identification information. The information processing method according to claim 10.
12. In response to receiving the first communication, after the linking operation to the product information of the target product is completed, the second communication is sent to the upstream company's account.
12. The information processing method according to claim 10 or 11.
13. The method further includes a step of storing the first identification information and the second identification information associated with the first identification information in the storage device.
12. The information processing method according to claim 10 or 11.
14. the first contact includes a request to link a downstream product of the downstream company to the target product; The second contact includes a request to link the target product with an upstream product of the upstream company.
12. The information processing method according to claim 10 or 11.
15. The first contact includes a request for an inquiry about a linking status of a product located upstream of the target product. The information processing method according to claim 14.
16. The method further includes a step of receiving a third communication from the account of the upstream company that sent the second communication, the third communication being related to a linking operation of the product information of the upstream product with product information of a further upstream product, the third communication including third identification information, and sending the third communication to an account of a company that is located upstream of the upstream company.
12. The information processing method according to claim 10 or 11.
17. The product information includes traceability related information; 12. The information processing method according to claim 10 or 11.
18. The traceability-related information includes at least one of information on greenhouse gas emissions, a recycling rate for a given raw material, and a due diligence score; 18. The information processing method according to claim 17.
19. A program for causing the server device to execute the information processing method according to claim 10.
Citation Information
Patent Citations
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
Supply chain management apparatus, and method, system, and program of the same
JP2015115016A
Methods and systems for controlling supply chains
JP2015528946A
Information collection management system, computation machine, and information collection management method
JP2021174419A
