Information processing apparatus and information processing method

Abstract

The invention relates to an information processing apparatus and an information processing method. The information processing apparatus includes a control unit configured to execute the following processes: accepting designation of one or more first platforms that manage a supply chain; accepting input of first information related to a first product including information related to traceability; generating, from the first information, second information corresponding to each of the first platforms by referring to information relating to a rule when information is transmitted to each of the first platforms; and transmitting second information to each of the first platforms through the corresponding connector by referring to information related to the connector corresponding to each of the first platforms, or arranging the second information in a predetermined storage area in a transmittable state.

Description

Technical Field

[0001] The present disclosure relates to an information processing device and an information processing method. Background Art

[0002] A system for sharing information on traded products between supplier companies and customer companies has been proposed (for example, Patent Document 1). This system enables information to be shared between adjacent companies in a supply chain via a common platform.

[0003] Patent Document 1: Japanese Patent Application Laid-Open No. 2004-171146 Summary of the Invention

[0004] An object of the present disclosure is to reduce the trouble of inputting product information.

[0005] One of the technical solutions disclosed herein is an information processing device, wherein:

[0006] The information processing device includes a control unit configured to execute the following processing:

[0007] Accept the designation of more than one first platform for managing the supply chain;

[0008] accepting input of first information related to a first product including information related to traceability;

[0009] generating second information corresponding to each of the first platforms from the first information, referring to information related to rules for sending information to the first platforms respectively; and

[0010] The second information is transmitted to the first platforms through the corresponding connectors, or the second information is arranged in a predetermined storage area in a transmittable state.

[0011] One of the technical solutions disclosed herein is an information processing method, wherein:

[0012] The following processing is performed by a computer:

[0013] Accept the designation of more than one first platform for managing the supply chain;

[0014] accepting input of first information related to a first product including information related to traceability;

[0015] generating second information corresponding to each of the first platforms from the first information, referring to information related to rules for sending information to the first platforms respectively; and

[0016] The second information is transmitted to the first platforms through the corresponding connectors, or the second information is arranged in a predetermined storage area in a transmittable state.

[0017] Furthermore, another technical aspect of the present disclosure is a program for causing a computer to execute the processing in the above-mentioned information processing apparatus, and a storage medium storing the program in a non-transitory manner.

[0018] According to the present disclosure, it is possible to reduce the trouble of inputting product information. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a diagram illustrating an example of the supply chain according to the first embodiment.

[0020] Figure 2 This is a diagram illustrating an example of the relationship between products supplied through a supply chain.

[0021] Figure 3 This is a diagram showing an overview of processing performed between an enterprise terminal and a server device.

[0022] Figure 4 This is a diagram showing the hardware configuration of the server device according to the first embodiment.

[0023] Figure 5 This is a diagram showing the hardware configuration of the enterprise terminal according to the first embodiment.

[0024] Figure 6 This is a software configuration diagram of the server device according to the first embodiment.

[0025] Figure 7 This is a software configuration diagram of the enterprise terminal according to the first embodiment.

[0026] Figure 8 This is an example of product information generated by the product information generation unit.

[0027] Figure 9 This is an example of a screen output by the authority setting section.

[0028] Figure 10 This is an example of permission information generated by the authority setting unit based on the input information.

[0029] Figure 11 This is an example of a user interface including a list of products that are candidates for correspondence creation targets.

[0030] Figure 12 This is a diagram showing an example of a screen output by the second product information generating unit.

[0031] Figure 13 This is a diagram showing an example of the flow of processing executed by the server device.

[0032] Figure 14 This diagram illustrates the product tree and the amount of carbon dioxide emitted in each process.

[0033] Figure 15 This is an example of a screen that outputs a product tree as an image.

[0034] Figure 16 This is an example of a product tree where products without access permissions are set to private.

[0035] Figure 17 This is a flowchart of a process for registering second information on the platform.

[0036] Figure 18 This is a sequence diagram illustrating the processing performed by the server device and the enterprise terminal in the first to third stages.

[0037] Figure 19 This is a sequence diagram illustrating the processing performed by the server device and the enterprise terminal in the fourth stage.

[0038] Figure 20 This is a diagram schematically showing an example of the hardware configuration of the enterprise terminal according to the second embodiment.

[0039] Figure 21 This is a flowchart of a process for registering second information on the platform.

[0040] Figure 22 This is a flowchart of a process for registering second information on the platform.

[0041] Figure 23 This is a diagram showing a schematic configuration of a system in which the second information is generated by a dedicated server device.

[0042] Figure 24 This is a diagram schematically showing an example of the hardware configuration of a dedicated server device according to the fourth embodiment.

[0043] Figure 25 This is a diagram schematically showing the software configuration of the dedicated server device according to the fourth embodiment.

[0044] Figure 26 This is a diagram showing a schematic configuration of a system in which the second information is generated by a server device.

[0045] Figure 27 This is a diagram schematically showing an example of the hardware configuration of the first server device according to the fifth embodiment.

[0046] Figure 28 This is a diagram schematically showing an example of the software configuration of the first server device according to the fifth embodiment.

[0047] Figure 29 This is a diagram showing a schematic configuration of a system in which the second information is provided to a target platform.

[0048] Figure 30 This is a diagram schematically showing an example of the hardware configuration of the second server device according to the sixth embodiment.

[0049] Figure 31 This is a diagram showing an overview of processing executed by a server device and an enterprise terminal when second information is directly transmitted to an enterprise terminal.

[0050] Figure 32 This is a flowchart of the process of registering product metadata in the target platform.

[0051] Figure 33 This is a flowchart of a process of providing second product information to a second enterprise terminal of a target platform. DETAILED DESCRIPTION

[0052] Carbon Footprint (CFP) is a mechanism that converts the amount of greenhouse gas emissions emitted throughout the entire life cycle of a product, from the procurement of raw materials to disposal / recycling, into CO2 and displays it on the product. In order to achieve CFP, it is important to record each supplier involved from the procurement of raw materials to disposal / recycling of the product and to have traceability in a state where the resume can be tracked. On the other hand, when a supplier delivers products to multiple companies, there is a situation where different platforms are used for each delivery party even if the target products are the same. In this case, the supplier is required to enter the same information into each platform, which makes information entry troublesome. In addition, the occurrence of this problem is not limited to the scenario of collecting carbon footprints. For example, this problem may occur in all scenarios where other traceability-related information (for example, the recovery rate of raw materials, due diligence information, etc.), information related to other products (for example, components, identification information, etc.), and other arbitrary information related to the product are collected.

[0053] Furthermore, since each platform may have different input content, user interfaces, and connectors, suppliers must adapt to each platform whenever registering information with it.

[0054] In view of this, an information processing device as one of the technical solutions disclosed in the present invention has a control unit configured to perform the following processing: accepting the designation of one or more first platforms for managing the supply chain; accepting the input of first information related to a first product containing information related to traceability; generating second information corresponding to the above-mentioned first platforms from the above-mentioned first information with reference to information related to rules for sending information to the above-mentioned first platforms respectively; and referring to information related to connectors corresponding to the above-mentioned first platforms respectively, sending the above-mentioned second information to the above-mentioned first platforms through the corresponding connectors, or configuring the above-mentioned second information in a sendable state in a specified storage area.

[0055] The first platform at least manages the relationships between enterprises. The first platform can also manage information related to each enterprise or information related to each enterprise's products. Alternatively, the first platform can manage enterprise metadata. The metadata management platform can include a server and each enterprise's terminals or servers. Multiple enterprises participate in the supply chain. The first product is the product that is subsequently intended to be added to the first platform.

[0056] The first product may be, for example, a material, a single component, an assembly component, or a finished product. The first information of the first product includes information related to traceability. The information related to traceability may include, for example, information related to the amount of greenhouse gases emitted during the manufacturing process of the first product. The second information is information generated from the first information according to the rules set on the first platform. Here, when there are multiple first platforms, there are cases where the items input on each first platform are different. In addition, for example, there may also be cases where the units when inputting mass are different. In view of this, the control unit generates the second information for each first platform according to the rules of the first platform. The rules may be stored in the storage unit of the information processing device, for example, and may be provided from an external server or from each first platform. In addition, the rules may also be composed of a semantic data model and its conversion formula, for example.

[0057] In addition, the control unit refers to the information related to the connectors corresponding to the first platforms. Here, it is also conceivable to use different connectors for each first platform. Information can be sent and received between the first platforms without going through the connectors corresponding to the first platforms. That is, the control unit obtains the information related to the connectors corresponding to the first platforms, and can send the second information to the first platforms via the connectors. In addition, the second information can also be configured in a prescribed storage area in a state that can be sent to the first platforms via the connectors. In this way, the control unit can provide the second information related to the first product to the first platforms. In addition, the supplier can save the trouble of inputting the data corresponding to the first platforms separately.

[0058] The information processing device may be a terminal of the company that produces the first product, or a server that is independent of the platform and provides information obtained from the terminal of the company that produces the first product to the first platform. Alternatively, the information processing device may be a server of a platform different from the first platform.

[0059] Furthermore, the aforementioned predetermined storage area may also contain information regarding rules for sending information to the respective first platforms, as well as information regarding connectors corresponding to the respective first platforms. This allows for rapid access to this information. Alternatively, this information may be obtained via a network.

[0060] In addition, the control unit can refer to the inventory data corresponding to the first platform in response to the existence of information that is insufficient with only the first information, and generate the second information based on the information obtained from the inventory data to supplement the information that is insufficient with only the first information. Here, it is also possible to consider the situation where it is difficult to provide part or all of the data for the items required to be input in each first platform. For example, it is possible to consider the situation where it is difficult to provide data to other countries due to the laws and regulations of each country. In such a case, inventory data is used as data instead of actual data. Inventory data is, for example, data corresponding to each item input as the second information, such as data provided by each first platform. The first information (primary data) is, for example, an actual measured value. On the other hand, inventory data (secondary data) is a reference value used when no actual measured value is obtained. Inventory data can also be, for example, data that specifies the representative value of each item. By using inventory data to supplement the second information, data can be input for all items that are required to be input.

[0061] Furthermore, the control unit may output a warning in response to the presence of insufficient information based solely on the first information regarding the information requested by the first platform. Outputting such a warning can encourage a user to input the insufficient information. Furthermore, outputting a warning when insufficient inventory data is used to replenish the insufficient amount allows the user to be informed of the type of data replenished.

[0062] Furthermore, the control unit may generate the second information by excluding third information designated as non-disclosed in response to the first information including third information designated as non-disclosed. The third information designated as non-disclosed may be, for example, confidential information. The third information may also be user-designated information. By excluding such third information, the disclosure of information that could cause harm to the user can be prevented.

[0063] Furthermore, the control unit may refer to inventory data corresponding to the first platform in response to the inclusion of the third information in the first information, and generate the second information by supplementing the excluded third information with information obtained from the inventory data. In this manner, the inventory data may be used as the input data in place of the third information.

[0064] In addition, the information related to the rules for sending information to the first platform includes information related to the rules related to the fourth information. The fourth information is information that cannot be disclosed based on the location of the terminal that sends information to the first platform. In response to the inclusion of the fourth information in the first information, the control unit can exclude the fourth information to generate the second information. The fourth information is, for example, information that is restricted from disclosure due to laws and regulations. For example, there are situations where the disclosure of information to other countries is restricted depending on the country. In such a case, by excluding the fourth information from generating the second information, the second information can be generated in accordance with the rules corresponding to the location.

[0065] Furthermore, the control unit may refer to inventory data corresponding to the first platform in response to the inclusion of the fourth information in the first information, and supplement the excluded fourth information with information obtained from the inventory data to generate the second information. By excluding the fourth information and supplementing it with the inventory data, the second information can be generated while ensuring traceability.

[0066] Furthermore, the information regarding the rules for transmitting information to each of the first platforms includes information regarding unit rules, and the control unit may generate the second information based on the unit rules corresponding to the first platform. Since the units of data input may differ for each first platform, the second information corresponding to each first platform can be generated by converting the units.

[0067] Furthermore, the first product may be a product related to batteries. In other words, the first product may be a product used in the manufacture of batteries. This ensures traceability related to batteries.

[0068] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. The configurations of the following embodiments are merely illustrative, and the present disclosure is not limited to the configurations of the embodiments. In addition, the following embodiments can be combined as much as possible.

[0069] <First embodiment>

[0070] The system according to this embodiment is a system that provides information about products supplied by a supply chain including a plurality of companies. The information about the products is typically information about traceability.

[0071] First, the structure of the supply chain is explained. In one example, at least some of the companies included in the supply chain (intermediate suppliers) can receive components from one or more upstream companies, use the received components to produce their own products, and deliver the produced products to the companies in the next process (downstream companies). The upstream company can directly produce its own products and deliver the produced products to the companies in the next process. Companies in a part of the supply chain can directly deliver (i.e., participate in the circulation) products received from other companies to other companies. Multiple companies repeat this action, and the final product can be obtained in the final process.

[0072] Figure 1 This is a diagram illustrating an example of a supply chain involved in this embodiment. Figure 1 In the example, we imagine a scenario where we acquire products related to cars. Specifically, Figure 1 The supply chain shown consists of the original equipment manufacturer (OEM) and multiple suppliers. The OEM assembles the final product, while the suppliers (Companies A through C) provide components, materials, and assemblies used to manufacture the final product. Each supplier produces multiple products and delivers them to the next lower level. These operations are repeated by multiple companies, with the final product assembled in the final process.

[0073] In this embodiment, the side that delivers products within a certain hierarchy is referred to as the upstream side, and the side that purchases these products to produce new products is referred to as the downstream side. In this specification, upstream companies are referred to as upstream companies, and downstream companies are referred to as downstream companies. Furthermore, products produced by upstream companies are referred to as upstream products, and products produced by downstream companies are referred to as downstream products. Downstream products include upstream products.

[0074] In this embodiment, the levels included in the supply chain are referred to as tiers. Tier 0 is the lowest level (corresponding to the OEM company) that assembles the final product, and the company moves upstream as it enters Tiers 1, 2, and 3. Depending on the tier of interest, downstream companies may become upstream companies. For example, Company B in Tier 2 is a downstream company in its relationship with Tier 3, but an upstream company in its relationship with Tier 1. Thus, the definitions of upstream and downstream companies vary for each tier.

[0075] Figure 2This is a diagram illustrating an example of the relationship between products supplied by a supply chain. Here, the supply relationship of multiple products that constitute the final product X is represented by a tree diagram. In this example, the 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 relationship between multiple products that constitute the final product can be represented by a tree diagram in which each product becomes a node. Hereinafter, a tree diagram related to a specific final product will be referred to as a product tree. In one example, the final product X is a battery installed in an electric vehicle (BEV: Battery Electric Vehicle). In another example, the final product X may be a car, a car component, or other car-related product.

[0076] The server device 1 involved in this embodiment collects information related to the products produced by each enterprise (hereinafter referred to as product information) and information used to establish a correspondence between product information from the terminal corresponding to each enterprise (enterprise terminal 2), and generates such a product tree based on this information. In addition, the product information includes information related to traceability (for example, information related to greenhouse gas emissions, etc., hereinafter referred to as "traceability-related information"). By tracing the product tree, it is possible to track carbon footprints, etc. Among them, the traceability-related information can include all information that may be the subject of ensuring traceability.

[0077] like Figure 1 As shown, an information processing system involved in an example of this embodiment includes a server device 1 and multiple enterprise terminals 2. The enterprise terminals 2 are terminals corresponding to multiple enterprises that constitute the supply chain. The system can include multiple enterprise terminals 2. The server device 1 collects information for generating a product tree from each of the multiple enterprise terminals 2 and generates a product tree based on this information. In addition, the server device 1 can perform traceability-related processing (typically, processing for calculating carbon dioxide emissions, etc.) based on the generated product tree. In addition, the execution results of the processing can be sent to the enterprise terminal 2.

[0078] Next, use Figure 3 The outline of the process of generating a product tree by the server device 1 will be described. Figure 3 1 is a diagram showing an overview of the processing performed between the enterprise terminal 2 and the server device 1. Figure 3 In the example, assume that there are Company A as a downstream company and Company B as an upstream company in any hierarchy. Imagine that Company B produces Product B and delivers it to Company A, and Company A uses Product B to produce Product A. That is, in Figure 3 In the example above, Product B becomes a child node of Product A in the product tree.

[0079] To generate the product tree, the enterprise terminal 2 corresponding to each enterprise sends information related to the company's products to the server device 1. In this example, the enterprise terminal 2 corresponding to enterprise A sends product information related to product A (referred to as product information A) to the server device 1. Similarly, the enterprise terminal 2 corresponding to enterprise B sends product information related to product B (referred to as product information B) to the server device 1. The server device 1 stores the product information of each enterprise.

[0080] The company terminal 2 performs operations for associating product information stored in the server device 1. In one example, the person in charge of a downstream company logs into the server device 1 from the company terminal 2 using the downstream company's account and selects an upstream product to be associated with the company's downstream product. This allows the downstream product to associate product information with the upstream product. Based on the selection, the server device 1 associates the product information with the downstream product.

[0081] However, if all products included in the supply chain and their related information are presented as options when selecting a product to establish correspondence, the confidentiality of information about companies that make up the supply chain and the products produced by those companies would be compromised. Furthermore, disclosing the entire product tree to a single supplier may not be appropriate.

[0082] In view of this, the server device 1 according to this embodiment pre-grants access rights to product information of upstream products to downstream companies upon request of upstream companies. The server device 1 allows reference from downstream companies within the scope of the granted rights.

[0083] exist Figure 3 In the example, enterprise terminal 2 corresponding to enterprise B, an upstream enterprise, sends a request (information) to server device 1 indicating "granting enterprise A access rights to product information B." Upon receiving a request for establishing a correspondence from enterprise terminal 2 corresponding to enterprise A, server device 1 provides only a list of product information to which enterprise A has been granted access rights, and selects it as the target for establishing the correspondence. Furthermore, if a request for a reference to a product tree is received from enterprise terminal 2 corresponding to enterprise A, server device 1 provides enterprise terminal 2 with a product tree with information other than the information to which enterprise A has been granted access rights concealed. This allows information related to unrelated enterprises and products to be concealed.

[0084] [Hardware composition]

[0085] Next, use Figure 4 The hardware configuration of each device constituting the system will be described. Figure 41 is a diagram schematically showing an example of the hardware configuration of the server device 1 according to the present embodiment. The server device 1 is configured as a computer including a control unit 11 , a storage unit 12 , a communication module 13 , and an input / output device 14 .

[0086] The server device 1 can be configured as a computer having a processor (CPU, GPU, etc.), a primary 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) consistent with the prescribed purpose, as described below, can be implemented. However, some or all of the modules can also be implemented as hardware modules using hardware circuits such as ASICs and FPGAs.

[0087] The control unit 11 is a computing unit that implements various functions of the server device 1 by executing a predetermined program. The control unit 11 can be implemented by a hardware processor such as a CPU. Alternatively, the control unit 11 may include RAM, ROM (Read Only Memory), cache memory, and the like.

[0088] The storage unit 12 is a mechanism for storing information and is composed of storage media such as RAM, a magnetic disk, and flash memory. The storage unit 12 stores programs executed by the control unit 11 and data utilized by these programs. Furthermore, a database is constructed in the storage unit 12 to store product information collected from multiple enterprise terminals 2 and account information related to the enterprises. Details will be described later.

[0089] Communication module 13 is a communication interface for connecting server device 1 to a network. Communication module 13 may include, for example, a network interface board and a wireless communication interface for wireless communication. Server device 1 can communicate data with other computers (e.g., other server devices 1 or enterprise terminals 2) via communication module 13.

[0090] The input / output device 14 receives input from the operator and displays information to the operator. Specifically, the input / output device 14 includes devices for input, such as a mouse and keyboard, and devices for output, such as a display and speakers. The input / output device can also be integrated with, for example, a touch panel display.

[0091] Among them, the specific hardware structure of the server device 1 can appropriately omit, replace, and add components according to the implementation method. For example, the control unit 11 may also include multiple hardware processors. The hardware processor can be composed of a microprocessor, an FPGA, a GPU, etc. The input and output device 14 can be omitted, or an input and output device other than the exemplified device (for example, an optical drive, etc.) can be added. In addition, the server device 1 can be composed of multiple computers. In this case, the hardware structure of each computer may be consistent or inconsistent.

[0092] Figure 5 1 is a diagram schematically showing an example of the hardware configuration of the enterprise terminal 2 according to the present embodiment. The enterprise terminal 2 is configured as a computer including a control unit 21 , a storage unit 22 , a communication module 23 , and an input / output device 24 .

[0093] The enterprise terminal 2, like the server device 1, can be configured as a computer having a processor (CPU, GPU, etc.), a primary storage device (RAM, ROM, etc.), and a secondary storage device (EPROM, hard disk drive, removable media, etc.). However, some or all of the functions (software modules) may be implemented as hardware modules using hardware circuits such as ASICs and FPGAs.

[0094] The control unit 21 is a computing unit that implements various functions (software modules) of the enterprise terminal 2 by executing predetermined programs. The control unit 21 can be implemented, for example, by a hardware processor such as a CPU. Alternatively, the control unit 21 can be configured to include RAM, ROM (Read Only Memory), cache memory, and the like.

[0095] The storage unit 22 is a mechanism for storing information and is composed of storage media such as RAM, a magnetic disk, and flash memory. The storage unit 22 stores programs executed by the control unit 21, data used by these programs, rule information related to product information input rules, and connector information related to connectors compatible with each platform. Details will be described later.

[0096] Communication module 23 is a communication interface for connecting enterprise terminal 2 to a network. Communication module 23 may include, for example, a network interface board and a wireless communication interface for wireless communication. Enterprise terminal 2 can communicate data with other computers (e.g., server device 1) via communication module 23.

[0097] The input / output device 24 receives input from the operator and presents information to the operator. Specifically, the input / output device 24 includes devices for input, such as a mouse and keyboard, and devices for output, such as a display and speakers. The input / output device can also be integrated with, for example, a touch panel display.

[0098] The specific hardware configuration of the enterprise terminal 2 is the same as that of the server device 1 , and components can be omitted, replaced, or added as appropriate according to the embodiment.

[0099] [Software composition]

[0100] Next, use Figure 6 The software configuration of each device constituting the system will be described. Figure 6 This figure schematically illustrates an example of the software configuration of the server device 1 according to this embodiment. In this embodiment, the control unit 11 is configured to include five software modules: an information collection unit 111, a permission setting unit 112, a correspondence establishment unit 113, an information provision unit 114, and a connector unit 115. Each software module is implemented by the control unit 11 (CPU) executing a program stored in the storage unit 12. The information processing performed by the information collection unit 111, permission setting unit 112, correspondence establishment unit 113, information provision unit 114, and connector unit 115 described below is synonymous with the information processing performed by the control unit 11.

[0101] The information collection unit 111 is configured to receive product information transmitted from the enterprise terminal 2 and store the product information in the storage unit 12. The permission setting unit 112 is configured to receive information (hereinafter referred to as permission information) for setting access rights to the product information from the enterprise terminal 2. Furthermore, the permission setting unit 112 is configured to set access rights to the product information stored in the storage unit 12 based on the received information.

[0102] The correspondence establishing unit 113 is configured to obtain information for establishing correspondence between product information from the enterprise terminal 2 by interacting with the enterprise terminal 2. Furthermore, the correspondence establishing unit 113 is configured to execute a process of writing information indicating the correspondence establishment relationship to the product information stored in the storage unit 12 based on the information obtained. In addition, the correspondence establishing unit 113 is configured to receive a request to assign terminal information and, in response thereto, to execute a process of assigning the terminal information to the product information stored in the storage unit 12. A product tree is formed by reflecting the correspondence establishment and the terminal assignment. That is, the product tree is formed by storing the correspondence establishment information and the terminal information in the storage unit 12. The correspondence establishing unit 113 is configured to generate a product tree based on the results of the correspondence establishment and the terminal assignment.

[0103] The information providing unit 114 is configured to perform information processing related to the product tree and output the results of the information processing. The information processing related to the product tree may include performing traceability-related calculations on the product tree. Outputting the results of the information processing may include providing information related to the generated product tree to the corresponding enterprise terminal 2. In one example, the information providing unit 114 is configured to generate information related to the product tree and output the generated information related to the product tree.

[0104] The connector unit 115 includes applications used for platform-related communications. Communication with the enterprise terminal 2 and communication between multiple server devices 1 can be carried out via the connector unit 115. The connector unit 115 can be configured to perform, for example, authentication, encryption of communications, and other processes related to data communication. In addition, the connector unit 115 can be configured to control access to various data based on rules such as laws and regulations and contracts. In one example, the connector unit 115 can be an application used for platform-related communications, such as an IDS (International Data Spaces) connector or an EDC (Eclipse Dataspace Connector).

[0105] In this embodiment, the storage unit 12 is configured to include multiple logical storage areas. Different access permissions can be set for each of the multiple storage areas, such as an area with access permissions granted to company A, an area with access permissions granted to company B, or an area with access permissions granted to both companies A and B. The permission setting unit 112 sets access permissions by storing product information received from the company terminal 2 in the appropriate storage area. The specific processing method will be described later.

[0106] Furthermore, the storage unit 12 stores account information. In this embodiment, interaction between the server device 1 and the enterprise terminal 2 is achieved by an operator at each enterprise logging into the server device 1 via the enterprise terminal 2 using the corresponding enterprise account. Account information is information related to the accounts corresponding to each enterprise constituting the supply chain. Logging in using an account is one example of accessing the server device 1 as the corresponding enterprise. However, the method for accessing the server device 1 is not limited to this example and may be selected as appropriate depending on the embodiment.

[0107] Figure 7This diagram schematically illustrates the software configuration of the enterprise terminal 2 according to this embodiment. In this embodiment, the control unit 21 is configured to include six software modules: a product information generation unit 211, a permission setting unit 212, a correspondence request unit 213, an information acquisition unit 214, a connector unit 215, and a second product information generation unit 216. Each software module can be implemented by the control unit 21 (CPU) executing a program stored in the storage unit 22. The information processing performed by the product information generation unit 211, permission setting unit 212, correspondence request unit 213, information acquisition unit 214, connector unit 215, and second product information generation unit 216 is synonymous with the information processing performed by the control unit 21.

[0108] The product information generating unit 211 is configured to generate information (product information) on products of the enterprise corresponding to the enterprise terminal 2 . Figure 8 This is an example of product information generated by the product information generation unit 211. Product information can also be input by the device operator. In this embodiment, the product information is structured to include 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 using the company terminal 2). The product ID and product name are the identifier and name of the target product.

[0109] Furthermore, the product information is configured to include association information. The association information is information for identifying the upstream product associated with the target product. In this embodiment, the association information includes fields for "upstream product information" and "terminal flag."

[0110] The upstream product information field is configured to store information identifying the product information associated with the upstream product associated with the target product (i.e., a product included in the target product and required for producing the target product). The upstream product information field is used by server device 1 to associate products with each other. Since the target product is not associated with the upstream product at the stage of generating product information, a value representing the upstream product need not be stored in the upstream product information field.

[0111] The terminal flag field is configured to store a flag indicating whether the target product is a leaf node in the product tree, that is, a node located at the most upstream (end). In this embodiment, since multiple enterprise terminals 2 send product information, for products in the product tree, this flag is used to determine whether there is a corresponding product on the upstream side and whether no further corresponding establishment is generated (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 corresponding establishment of products. Since the corresponding establishment relationship of the target product has not been determined basically at the stage of generating product information, "0 (not a terminal now)" can be stored in the terminal flag field. In order to finally generate the product tree, the product information of each enterprise stored in the server device 1 is set to any one of the states of "corresponding to the upstream product" and "the terminal flag is set to "1"".

[0112] 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 product) used per unit production volume of the product, information related to the recovery rate of specified raw materials, the amount of greenhouse gas emissions emitted when the product is produced (CFP value), due diligence-related information, or a combination thereof. The specified raw materials may be, for example, lithium, nickel, cobalt, lead, graphite, etc. The recovery rate may be expressed directly, or may be expressed indirectly, such as a combination of the total utilization and the utilization of recycled materials. These values ​​are values ​​corresponding to the process of producing the target product. For example, in Figure 3 In the example of , the traceability-related information included in product information A stores information such as the amount of greenhouse gases emitted during the production of product A. The traceability-related information included in product information A does not include information about the processes leading up to the production of the upstream product (for example, the amount of greenhouse gases emitted until the production of upstream product B).

[0113] Among them, traceability-related information can be appropriately selected according to the implementation method. In one example, the emission of greenhouse gases (carbon footprint) may include emissions in scope 1, scope 2, and scope 3. Scope 1 may be the direct emission of greenhouse gases involved in itself. Scope 2 may be indirect emissions accompanying the use of electricity, heat, and steam supplied from other companies. Scope 3 may be indirect emissions outside scope 1 and scope 2. In addition, in one example, due diligence-related information may be a technical document indicating the amount of raw materials contained in a product containing target raw materials (e.g., cobalt, natural graphite, lithium, nickel, etc.), indicating the obligation of smelters, etc. to fulfill mineral procurement. In another example, due diligence-related information may include a score indicating the extent to which the above obligations have been fulfilled.

[0114] The authority setting unit 212 is configured to specify downstream companies that are permitted to access the product information transmitted from the company terminal 2 to the server device 1 . Figure 9 This is an example of a screen output by the authority setting unit 212. As shown in the figure, the authority setting unit 212 is configured to accept designation of a downstream company to which access is permitted for any of the company's products. Figure 10 This is an example of permission information generated by the permission setting unit 212 based on the input information. The permission setting unit 212 is configured to send permission information to the server device 1 at any time. Access rights can be set per product information or per item included in the product information ("Permission Item" in the figure). This allows for partial disclosure, such as disclosing the existence of a product but not disclosing specific information such as the materials used and the amount used.

[0115] Among them, Figure 9 The list of companies displayed on the screen can be a list of companies with which the company has had transactions in the past. Therefore, the server device 1 can store data related to past transactions (transaction data) for each company and generate a list of companies based on this transaction data. The transaction data can include, for example, the identifier of the target product, the identifier of the company that produced the product, and the transaction date.

[0116] The association request unit 213 is configured to request the server 1 to establish an association with an upstream product for the company's product information sent to the server 1. In one example, the association request unit 213 first sends the company's company ID and product ID to the server 1 and requests that the product information corresponding to the product ID be associated with the product information. In response, the server 1 generates a user interface containing a list of product information that the target company is permitted to access (i.e., candidate association targets) and provides the generated user interface to the company terminal 2. Figure 11 is an example of a user interface including a list of products that are permitted to be accessed by the target enterprise.

[0117] in, Figure 11 The list of products presented in the can be a list of products that have had transaction records with the company in the past. The server device 1 can also generate this list based on stored transaction data.

[0118] Next, the association request unit 213 is configured to allow the operator to select an upstream product to be associated from the list. Furthermore, the association request unit 213 is configured to send a pair of identifiers for the product (downstream product) serving as the association source and the upstream product (target) serving as the association target to the server 1. Based on these identifiers, the server 1 can associate product information with each other.

[0119] In addition, if there is no upstream product associated with the target product, for example, by checking Figure 11 This situation can be clearly indicated by checking the dotted check box in the . In this case, the product information is not associated with each other.

[0120] The information acquisition unit 214 is configured to request the server device 1 to provide a product tree and output the information transmitted from the server device 1 .

[0121] The connector unit 215 includes applications used for communication. Communication between the enterprise terminal 2 and the server device 1 can be carried out via the connector unit 215. The connector unit 215 can be configured to perform processing related to data communication, such as authentication and encryption of communication. In addition, the connector unit 215 can be configured to control access to various data based on rules such as laws and contracts. In one example, the connector unit 215 can be an application such as an IDS (International Data Spaces) connector or an EDC (Eclipse Dataspace Connector) used for platform-related communication. The connector unit 215 obtains the connector type when communicating with the server device 1 of each platform, and selects a connector corresponding to the obtained connector type. The connector type can be obtained from the server device 1 or stored in the storage unit 22 in advance.

[0122] The second product information generation unit 216 is configured to convert the product information generated by the product information generation unit 211 (hereinafter also referred to as first information) into product information corresponding to each platform (hereinafter also referred to as second information). The second product information generation unit 216 receives a platform designation. The second product information generation unit 216 generates a user interface including a list of platforms to which the product information is to be sent, and presents the generated user interface to the operator of the enterprise terminal 2. Figure 12 This is a diagram showing an example of a screen output by the second product information generating unit 216. Figure 8 After the input of the first product information is completed, it is output. Figure 12 As shown, the second product information generating unit 216 is configured to accept the designation of a platform to which the second information is to be transmitted for any of the company's products. In this case, the designation of multiple platforms can also be accepted.

[0123] Furthermore, the second product information generating unit 216 obtains information (rule information) related to the rules corresponding to the designated platform. This rule information can be obtained from the server device 1, stored in the storage unit 22, or obtained from a server device different from the platform's server device 1. Alternatively, the rule information can be stored on a non-transitory computer-readable storage medium. Furthermore, the rule information can be stored on a NAS (Network Attached Storage). Furthermore, the rule information can consist of, for example, a semantic data model and its transformation formula. Furthermore, the rule information can include information regarding rules related to units. For example, the rule information can include information indicating whether mass is expressed in "g" or "kg." Alternatively, the rule information can include information related to an input template. In this case, for example, the first information can be converted into the second information based on the input template of the designated platform. Alternatively, the rule information can include information related to an input item. For example, an item input to the designated platform can be obtained and extracted from the first information to generate the second information. Alternatively, the second product information generating unit 216 can obtain the second information by transforming the first information using a transformation formula. This second information is generated for each designated platform. In addition, according to the rules of the platform, there may be a case where the first information does not need to be converted. In this case, the first information is directly processed as the second information.

[0124] The second product information generating unit 216 is configured to transmit the second information as product information to the server 1 at an arbitrary timing. The second information is transmitted via the connector 215. The server 1 receiving the second information also receives the second information via the connector 215.

[0125] [Details of the process related to the formation of the product tree]

[0126] Next, the specific contents of the processing performed by the server device 1 and the enterprise terminal 2 will be described. Figure 13 This is a diagram showing an example of a process flow executed by the server device 1 based on a request from the enterprise terminal 2 .

[0127] The processing performed by the server device 1 can be roughly divided into the following four stages.

[0128] (1) The first stage of receiving product information sent from the enterprise terminal 2 and storing the received product information

[0129] (2) The second stage of receiving permission information sent from the enterprise terminal 2 and setting the access rights to the product information based on the received permission information

[0130] (3) The third stage of establishing the correspondence between product information by interacting with the enterprise terminal 2

[0131] (4) The fourth stage of providing information related to the product tree based on the results of the corresponding establishment

[0132] exist Figure 13 In the example, Company A is considered the downstream company, and Company B is considered the upstream company. Furthermore, the product produced by Company A is referred to as Product A, and the product produced by Company B is referred to as Product B. Furthermore, the product information corresponding to Product A is referred to as Product Information A, and the product information corresponding to Product B is referred to as Product Information B.

[0133] In the first stage, the information collecting unit 111 of the server device 1 obtains product information from the product information generating unit 211 of the enterprise terminal 2. Figure 13 In the example shown in FIG1 , server device 1 obtains product information A from enterprise terminal 2 corresponding to enterprise A, and obtains product information B from enterprise terminal 2 corresponding to enterprise B. Information collection unit 111 stores product information A in a storage area (hereinafter referred to as storage area A) to which access rights are granted only to enterprise A. Furthermore, information collection unit 111 stores product information B in a storage area (hereinafter referred to as storage area B) to which access rights are granted only to enterprise B. In this way, information collection unit 111 stores product information sent from any enterprise in a dedicated storage area to which access rights are granted only to that enterprise.

[0134] In the second stage, the authority setting unit 112 of the server device 1 receives permission information from the authority setting unit 212 of the enterprise terminal 2, and sets the access rights to the product information according to the received permission information. Figure 10 As shown, the permission information is information that associates a product with a business that allows access to product information of the product.

[0135] exist Figure 13 In the example, assume that the permission setting unit 212 receives permission information that allows Company A, a downstream company, to access product information B, an upstream company. In this case, the permission setting unit 112 copies product information B stored in storage area B to a storage area (hereinafter referred to as storage area AB) to which access permissions are granted to both Company A and Company B. This allows product information B to be accessed by both Company A and Company B. Furthermore, if access permissions are not set for a specific item included in the product information, that item is excluded from being copied to storage area AB.

[0136] In the following description, a storage area to which access rights are granted only to a specific company is referred to as a "dedicated storage area," and a storage area to which access rights are granted to multiple companies is referred to as a "shared storage area."

[0137] The server device 1 executes the replication of the product information in response to receiving the permission information from the enterprise terminal 2. That is, the enterprise terminal 2 transmits the permission information to the server device 1, causing the server device 1 to execute the operation of replicating the product information identified by the permission information from the dedicated storage area of ​​the target enterprise to the shared storage area accessible from downstream enterprises.

[0138] In the third stage, the association unit 113 of the server device 1 receives the association request from the association request unit 213 of the enterprise terminal 2 and associates the product information based on the received association request.

[0139] First, the correspondence establishing unit 113 receives a correspondence establishing request from the enterprise terminal 2. The correspondence establishing request is sent from the enterprise terminal 2 of the downstream enterprise. Figure 13 In the example, it is assumed that the enterprise terminal 2 of enterprise A sends a correspondence establishment request. The correspondence establishment request includes the enterprise ID and the product ID of the target product. The correspondence establishment unit 113 obtains the product information stored in the storage area accessible from the enterprise and generates a list of the obtained product information. Figure 13 In the example of , the product information B stored in the storage area AB can be accessed from the company A. Therefore, in the company terminal 2 of the company A, the product information B can be selected as the association target.

[0140] The association request unit 213 of the enterprise terminal 2 presents a list to the operator, prompting the operator to select the product to be associated. In this example, products A and B are the targets for association. For example, for product A, the operator inputs information indicating that the upstream product is product B via the input / output device 24. The association request unit 213 sends data (association data) to the association unit 113 for associating the upstream product (product B) with the downstream product (product A).

[0141] As shown Figure 8 As described above, the product information includes a field (correspondence association information) related to the product to be associated. Based on the aforementioned association data, the association unit 113 stores information associated with product information B (i.e., the upstream product) in the association association information included in product information A. For example, the association association information may store the identifier of the upstream product and the identifier of the company that produces the upstream product.

[0142] Furthermore, the association information may include a pointer to the product information being associated. This pointer indicates the address of the product information corresponding to the upstream product. The above-described process forms part of a tree structure with the downstream product's product information as a parent node and the upstream product's product information as a child node.

[0143] At the end of a product tree, no further association is performed. In this case, the association request unit 213 sends data indicating that the product is at the end of the tree, rather than association data. Upon receiving this data, the association unit 113 sets the end flag field of the associated product information to "1." In other words, in the third stage, either the "process of setting the upstream product to be associated" or the "process of setting the end flag" is executed.

[0144] In the fourth stage, the information providing unit 114 of the server device 1 generates information related to the product tree based on the stored product information and outputs the information related to the product tree. Generating information related to the product tree can include processing such as generating various information related to the product (for example, information related to traceability, an image showing the link relationship between products in a tree diagram, etc.) after forming links between nodes by establishing correspondence between the product information. In order to generate information related to the product tree, it is necessary to complete the establishment of all correspondences between the product information and set the terminal flag of all leaf nodes to "1". When such conditions are met, the information providing unit 114 can appropriately generate the corresponding information.

[0145] As reference Figure 2 As described above, the product tree in this embodiment represents the supply relationship between product information in the supply chain using a tree diagram. The information providing unit 114 can generate an image representing the tree diagram based on the product information.

[0146] Furthermore, when generating information related to the product tree, the information providing unit 114 integrates the traceability-related information defined in each product information and outputs the result.

[0147] Here, use Figure 14 , the synthesis of traceability related information is explained. Figure 14 This is a diagram illustrating the amount of carbon dioxide (CO2) emitted in the various processes that make up the final product X and the various products that are produced. For example, in the process of producing product A12 in the diagram, E A12[g] of carbon dioxide. Furthermore, this product is composed of three upstream products A121 to A123. Thus, the upstream products included in a certain product are also referred to as "included products." Here, the total amount of carbon dioxide emitted until a target product is produced can be obtained by repeatedly transferring the CO2 emissions associated with upstream products to downstream products between companies in each of the two adjacent hierarchical levels, from the most upstream product as a leaf node to the target product.

[0148] exist Figure 14 In this example, if the target product is A12, the total amount of carbon dioxide emitted until the production of product A12 can be calculated by summing the CO2 emissions corresponding to the included products (upstream products A121 to A123) to the CO2 emissions corresponding to product A12. Specifically, the total CO2 emissions for product A12 are as follows.

[0149] I A12 =E A12 +E A121 ×U A121 +E A122 ×U A122 +E A123 ×U A123 [g]

[0150] Here, E A121 、E A122 、E A123 are the CO2 emissions per unit volume when producing products A121, A122, and A123, respectively. A121 、U A122 、U A123 These are the usage amounts of products A121, A122, and A123, respectively, used in the production of product A12. This usage amount is an example of the amount of material used per unit production volume of the product included in the traceability-related information. The CO2 emissions of the final product (the product of the most downstream company) can be obtained by performing the above calculations sequentially, from the product of the most upstream company to the final product.

[0151] The same applies when the target product is product A1. In this case, by combining the CO2 emissions corresponding to product A1 with the CO2 emissions corresponding to products A11, A12, A13, and A14, the total amount of carbon dioxide emitted from manufacturing activities leading up to the production of product A1 can be calculated.

[0152] The integrated value can be associated with the product and stored in the storage unit 12, or can be included in a part of the product information. That is, the product information corresponding to the product A12 can be kept as the E of the discharge amount in a separate process.A12 , and as the combined emission I A12 both sides.

[0153] This integrated traceability information is reused when integrating downstream products. By executing this process at each level, starting from the most upstream source, traceability information (e.g., cumulative CO2 emissions) is sequentially transferred downstream. Ultimately, by transferring this traceability information to the final product, traceability information covering the entire period leading up to the final product's production (e.g., total CO2 emissions) can be obtained.

[0154] In this way, when generating information related to the product tree, the information providing unit 114 can repeatedly perform a process of integrating the traceability-related information defined in each product information, from the most upstream to the most downstream. In the above example, carbon dioxide emissions are used as the object of integration, but the traceability-related information that can be integrated can also include recovery rates related to specified raw materials, due diligence scores, and so on. If the traceability-related information is numerical, integration can be performed through numerical calculations. If the traceability-related information is information other than numerical values ​​(for example, due diligence-related information), integration can be performed simply by collecting the information.

[0155] In another example, product information may include information indicating the location of the corresponding product's traceability-related information (hereinafter referred to as "location information," typically an address or pointer). In this case, the traceability-related information may not be included in the product information. Alternatively, integration may involve collecting the location information included in the product information.

[0156] The information providing unit 114 may also output the generated product tree in the form of an image, and may also output traceability-related information corresponding to any product at the same time.

[0157] Figure 15 This is an example of a screen displaying a product tree. The screen depicts a tree diagram showing the supply relationships of multiple products that comprise the final product. Selecting any product allows users to view traceability information related to that product, or a summary of traceability information for the entire period leading up to the product's production (e.g., the total CO2 emissions from the most upstream source). This information can be output via the input / output device 14 of the server 1 based on operations performed by the server 1 operator.

[0158] Furthermore, the information providing unit 114 can provide the generated product tree to the enterprise terminal 2 in response to a request from the enterprise terminal 2 (information acquiring unit 214). However, there are cases where it is not appropriate to disclose the entire product tree to a specific enterprise. Therefore, when providing the product tree to an enterprise terminal 2 corresponding to a particular enterprise, the information providing unit 114 can perform a non-disclosure process for the scope of the product tree that does not have access rights granted by that enterprise.

[0159] For example, in Figure 15 In this example, assume that information provision unit 114 receives a request to disclose a product tree from enterprise terminal 2 corresponding to the enterprise that produces product A12. Assume that this enterprise has been granted access rights only for products A121, A122, and A123. In other words, this enterprise cannot access product information other than those three products and downstream product A1. In this case, information provision unit 114 provides enterprise terminal 2 with a product tree that privately stores information about products for which it does not have access rights.

[0160] Figure 16 This is an example of a product tree when a product without access rights is made private. In this example, the product tree is displayed with detailed information (or the existence itself) of the private product hidden.

[0161] In cases where a product's existence is disclosed but access rights are not granted to a specific item within the corresponding product information, only that specific item is concealed, as indicated by the dotted line in the figure. In the example shown, the amount of carbon dioxide emitted during the production of product A121 is concealed.

[0162] On the other hand, even if there are products (or items) in the tree that do not have access permissions, the above-mentioned integration of traceability-related information is not affected. For example, in the example shown, although the carbon dioxide emissions of product A121 are not public, this does not affect the calculation of the total carbon dioxide emissions of product A12.

[0163] [Processing Flow]

[0164] Next, refer to Figure 17 The flow of processing executed by the enterprise terminal 2 when registering the company's product information through the enterprise terminal 2 will be described. Figure 17 This is a flowchart of the process of registering the second information on the platform. This routine is executed when a predetermined input by an operator is used as a trigger.

[0165] In step S101, the second product information generating unit 216 receives the designation of a platform as a destination for sending product information. Figure 12As described above, the second product information generating unit 216 receives the designation of a platform from the operator. Alternatively, the operator may designate multiple platforms. In this case, the second product information generating unit 216 receives the designation of multiple platforms.

[0166] In step S102, the second product information generating unit 216 references the rule information corresponding to the designated platform. If multiple platforms are designated, the rule information is referenced for each platform. The timing for referencing the rule information is not limited to the timing of executing step S102; it can be referenced at any time before the rule information is used.

[0167] In step S103, the product information generating unit 211 receives the input of the company's product information (first information). Figure 8 As described above, the product information generating unit 211 receives input of product information (first information) from an operator. The first information is typically Figure 8 The information shown is displayed, but the input items are not limited to this. For example, the input items can also be determined according to the designated platform. In addition, when inputting product information, it can be input in any input form, or it can be input in an input form corresponding to the designated platform. In addition, when multiple platforms are specified, it can also be input in an input form corresponding to any platform. Among them, the processing of step S101 and step S103 can be performed in one screen. In addition, the processing of step S101 and step S103 can be performed by the operator selecting from the list on the screen. In addition, the processing of step S103 can also be performed before the processing of step S101.

[0168] The following steps S104 to S107 are repeatedly performed for all platforms specified in step S101. In step S104, the second product information generation unit 216 determines whether the first information is sufficient. Since the information required varies depending on the specified platform, it is determined whether the information required for the specified platform has been input. The information required for each platform is included in the rule information. The second product information generation unit 216 refers to the rule information to determine whether the first information is sufficient. If the second product information generation unit 216 makes an affirmative determination in step S104, it proceeds to step S105. If it makes a negative determination, it proceeds to step S108.

[0169] In step S108, the second product information generating unit 216 outputs a warning indicating insufficient information. This warning is outputted, for example, by displaying an image indicating insufficient information on the screen of the input / output device 24 of the enterprise terminal 2. If the operator inputs a predetermined input in response to this warning, the process returns to step S103 and accepts input of the first information again. Alternatively, the warning may be a warning regarding the generation of the second information while maintaining insufficient information. Once step S108 is complete, the process proceeds to step S105. Alternatively, the process may be configured so that the second information is not generated if insufficient information is present. Furthermore, the processes of steps S104 and S108 may be omitted.

[0170] In step S105, the second product information generation unit 216 generates the second information. The second product information generation unit 216 refers to the rule information and converts the first information into the second information based on the rule information. For example, the second product information generation unit 216 uses a conversion formula included in the rule information to convert the first information into the second information. The generated second information is then transferred to the connector unit 215.

[0171] In step S106, the connector unit 215 refers to the connector. The connector unit 215 selects a connector corresponding to the platform specified in step S101 by referring to the connector information stored in the storage unit 22. If multiple platforms are specified in step S101, the connector unit 215 refers to and selects a connector for each platform.

[0172] In step S107, the connector unit 215 transmits the second information. If multiple platforms are specified, the corresponding second information is transmitted for each platform. Alternatively, instead of the connector unit 215 transmitting the second information, the second product information generation unit 216 may allocate (store) the generated second information in a predetermined storage area of ​​the storage unit 22. The second information allocated to the storage unit 22 can be made public by the connector unit 215 in response to a request from the server device 1 or another enterprise terminal 2.

[0173] Next, refer to Figure 18 and Figure 19 The flow of processing executed by the server device 1 and the enterprise terminal 2 when registering the company's product information through the enterprise terminal 2 will be described. Figure 18 This is a sequence diagram corresponding to the first to third stages described above. This process is executed for each server device 1 that has transmitted the second information.

[0174] In one example, the interaction between the server device 1 and the enterprise terminal 2 is initiated by the operator of each enterprise logging into the server device 1 using the corresponding enterprise account via the enterprise terminal 2. In this example, the operator of each enterprise logs into the server device 1 using the account of the company.

[0175] First, in step S11, the second product information generation unit 216 of the enterprise terminal 2 generates second information. The connector unit 215 of the enterprise terminal 2 transmits the generated second information as product information to the server device 1. The transmitted product information is received by the server device 1 (information collection unit 111) and stored in the storage unit 12 (step S12). At this time, the information collection unit 111 stores the product information in a storage area that is only accessible to the enterprise that produces the corresponding product.

[0176] Next, in step S13, the authority setting unit 212 of the enterprise terminal 2 receives input of information (permission information) specifying the downstream enterprises to be allowed to access the product information sent in step S11 via the operator. Figure 9 The user interface screen is described as such, and a combination of an arbitrary product and a downstream company that is permitted to access the product information is specified. The input permission information is transmitted to the server device 1.

[0177] In step S14, the authority setting unit 112 of the server device 1 grants access rights to the target product information based on the received permission information. Figure 13 As described above, the permission setting unit 112 grants access rights to any product information to any company by copying the target product information to a storage area that has access rights granted to multiple companies. If there is no storage area with appropriate access rights, a new storage area can be created to grant access rights to the appropriate company.

[0178] Next, in step S15, the association request unit 213 of the enterprise terminal 2 sends data (association request) requesting association with the upstream product to the server 1 for the product information sent to the server 1. The association request includes the company ID of the company and the product ID of the target product.

[0179] In step S16, the server device 1 (correspondence establishment unit 113) generates a list of product information that is allowed to be accessed from the target enterprise, and provides the user interface screen containing the list to the enterprise terminal 2. In this step, the server device 1 can provide a reference to the enterprise terminal 2. Figure 11 Then, such a user interface screen is explained, and a combination of an arbitrary product and an upstream product corresponding to the product is specified.

[0180] In step S17, the association request unit 213 of the enterprise terminal 2 receives a designation from the operator regarding a combination of a target product and an upstream product to be associated with the target product. The association request unit 213 generates data indicating the association between the upstream product and the downstream product (association data) and transmits the generated association data to the server device 1.

[0181] In step S18, the association unit 113 of the server device 1 updates the stored product information based on the association data to reflect the association between the product information. The association between the product information can also be performed by storing information related to the upstream product (identifier, pointer, etc.) in the association information of the downstream product's product information.

[0182] If no downstream company exists, steps S13 and S14 can be omitted. Similarly, if no upstream company exists (if no corresponding target exists for the target product), the terminal flag setting process described above can be performed instead of requesting the corresponding product information. In this case, steps S15 to S18 can be omitted.

[0183] Figure 19 This is a sequence diagram corresponding to the fourth stage described above. First, in step S21, the information acquisition unit 214 of the enterprise terminal 2 requests the server device 1 to provide a product tree. This request includes, for example, an identifier of the target product. The target product can be a final product or a product other than the final product (intermediate product).

[0184] Upon receiving the request, the server device 1 (information provider 114) generates information related to the product tree through the above-described process (step S22). At this point, the information provider 114 integrates the traceability-related information defined in each product information from the most upstream to the most downstream. The results of this integration are reflected in each product information.

[0185] Next, in step S23, server device 1 performs processing to conceal information to which access rights are not granted, based on the access rights granted to the target enterprise. For example, for a particular enterprise, server device 1 may conceal the existence of another company's product information, provided that the existence of that product information is not disclosed. Alternatively, if only a specific item included in the product information is not disclosed, server device 1 may conceal the content of that item. Information related to the concealed product tree is provided and output to enterprise terminal 2 (information acquisition unit 214) (step S24).

[0186] As described above, in this embodiment, product information inputted into the enterprise terminal 2 can be converted into second information corresponding to each platform and sent to the server 1. This configuration can save the operator the trouble of inputting information when registering product information.

[0187] <Second embodiment>

[0188] In the second embodiment, when there are insufficient items in the first information, the second information is generated by supplementing it with inventory data. Inventory data is data corresponding to each platform, and is data used as data instead of actual data. Inventory data is, for example, data provided by each first platform. Inventory data can be, for example, data that specifies the representative value of each item. By supplementing the second information with inventory data, data can be input for all items that are required to be input. The inventory data can be obtained in advance by the second product information generation unit 216 from the server device 1 of each platform and stored in the storage unit 22, or it can be obtained from the server device 1 of each platform when generating the second information. In addition, the inventory data can also be provided from a server device different from the server device 1 of each platform.

[0189] Figure 20 This is a diagram schematically showing an example of the hardware configuration of the enterprise terminal 2 according to this embodiment. The storage unit 22 of the enterprise terminal 2 stores inventory data corresponding to each platform. Figure 5 The structures shown are the same, so the description is omitted.

[0190] Next, refer to Figure 21 The flow of processing executed by the enterprise terminal 2 when registering the company's product information through the enterprise terminal 2 will be described. Figure 21 This is a flowchart of the process of registering the second information on the platform. This routine is executed by triggering a predetermined input by the operator. Figure 17 Description of the same processing steps as those in the illustrated routines will be omitted.

[0191] exist Figure 21 In the illustrated routine, if a negative determination is made in step S104, the process proceeds to step S201. In step S201, the second product information generation unit 216 references the inventory data to supplement the first information. The second product information generation unit 216 references the inventory data of the corresponding platform to extract data corresponding to the unentered items among the items required to be entered on the target platform, and adds the extracted data to the first information, thereby supplementing the first information.

[0192] In step S202, the second product information generating unit 216 outputs a warning indicating that the first information has been supplemented with inventory data. This warning output causes, for example, an image indicating that the first information has been supplemented to be displayed on the screen of the input / output device 24 of the enterprise terminal 2. Step S202 can also be omitted.

[0193] As described above, according to this embodiment, even if the first information input by the user is insufficient, it can be supplemented with inventory data, so that traceability can be ensured in the corresponding platform.

[0194] <Third embodiment>

[0195] In the third embodiment, information designated as confidential and information prohibited from disclosure by law are not transmitted to server device 1. Here, there are cases where the first information contains confidential information. Disclosure of confidential information could result in losses for the company. Furthermore, there are cases where the first information contains information prohibited from disclosure by law. In view of this, the items containing such information are deleted and second information is generated. Furthermore, the deleted items can be supplemented with inventory data. Information designated as confidential is an example of third information. Information prohibited from disclosure by law is an example of fourth information.

[0196] Information designated as confidential and information prohibited from disclosure under laws and regulations is included, for example, in the regulatory information. Furthermore, the designation of confidentiality can be made by, for example, the operator of the enterprise terminal 2 or based on rules included in the regulatory information. Furthermore, information prohibited from disclosure under laws and regulations can be determined, for example, based on the location of the enterprise terminal 2. The location of the enterprise terminal 2 can be the location of the target enterprise. Regulatory information is pre-stored in the storage unit 22.

[0197] Next, refer to Figure 22 The flow of processing executed by the enterprise terminal 2 when registering the company's product information through the enterprise terminal 2 will be described. Figure 22 This is a flowchart of the process of registering the second information on the platform. This routine is executed by triggering the specified input made by the operator. Figure 17 Description of the same processing steps as those in the illustrated routines will be omitted.

[0198] exist Figure 22In the illustrated routine, if a positive determination is made in step S104, the process proceeds to step S301; if a negative determination is made, the process proceeds to step S305. In step S301, the second product information generation unit 216 determines whether the first information does not contain any confidentiality-designated items. The second product information generation unit 216 refers to the rule information and determines whether the first information does not contain any items designated as confidential. If a positive determination is made in step S301, the process proceeds to step S303; if a negative determination is made, the process proceeds to step S302. In step S302, the second product information generation unit 216 deletes the information entered into the items designated as confidential.

[0199] In step S303, the second product information generation unit 216 determines whether the first information complies with the laws and regulations of the location where the enterprise terminal 2 is located. The second product information generation unit 216 refers to the regulatory information to determine whether the first information does not include items, such as those prohibited from disclosure by law. If the determination in step S303 is positive, the process proceeds to step S105; if the determination is negative, the process proceeds to step S304. In step S304, the second product information generation unit 216 deletes the information entered for the items that do not comply with the regulations.

[0200] In step S305, the second product information generation unit 216 references the inventory data to supplement the first information. The second product information generation unit 216 references the inventory data of the corresponding platform to extract data corresponding to the unentered items among the items required to be entered on the target platform, and adds the extracted data to the first information, thereby supplementing the first information. Unentered items also include items whose information was deleted in step S302 or step S304. Furthermore, the processing of step S305 can be omitted. In this case, the unentered items can remain unentered and the second information can be generated, or the processing can be terminated without generating the second information.

[0201] In step S306, the second product information generating unit 216 outputs a warning indicating that the first information has been supplemented with inventory data. This warning output causes, for example, an image to be displayed on the screen of the input / output device 24 of the enterprise terminal 2 indicating that the first information has been supplemented. If information was deleted in step S302, an image indicating that confidential information has been deleted may be displayed. Alternatively, if information was deleted in step S304, an image indicating that the information was deleted to comply with regulations may be displayed. Furthermore, the processing of step S306 may be omitted.

[0202] As described above, according to this embodiment, even if the first information input by the user contains confidential information or information that does not comply with regulations, it can be deleted to generate the second information. In addition, because the deleted information can be supplemented with inventory data, traceability can be ensured within the corresponding platform.

[0203] <Fourth embodiment>

[0204] In the fourth embodiment, the second information is generated by a server device configured to generate the second information. Figure 23 3 is a diagram showing a schematic configuration of a system in which the second information is generated by the dedicated server device 3. Figure 23 In the example, the first server 1A, the second server 1B, and the third server 1C are server devices 1 of different platforms. First information is transmitted from the enterprise terminal 2 to the dedicated server 3, and second information is generated in the dedicated server 3. Furthermore, the second information is transmitted from the dedicated server 3 to the first server 1A, the second server 1B, and the third server 1C. Hereinafter, when the first server 1A, the second server 1B, and the third server 1C are not distinguished, they are simply referred to as server devices 1.

[0205] Figure 24 This diagram schematically illustrates an example of the hardware configuration of a dedicated server device 3 according to this embodiment. The dedicated server device 3 is a dedicated server that sends second information to each platform. Furthermore, the dedicated server device 3 can also be configured to perform processing other than sending second information to each platform. The dedicated server device 3 is configured as a computer having a control unit 31, a storage unit 32, a communication module 33, and input / output devices 34. Since these hardware configurations are identical to the control unit 21, storage unit 22, communication module 23, and input / output devices 24 of the enterprise terminal 2, their description will be omitted.

[0206] The specific hardware configuration of the dedicated server device 3 is the same as that of the enterprise terminal 2 , and components can be omitted, replaced, or added as appropriate according to the embodiment.

[0207] Figure 25 This diagram schematically illustrates the software configuration of the dedicated server device 3 according to this embodiment. In this embodiment, the control unit 31 includes two software modules: a connector unit 315 and a second product information generation unit 316. Each software module is implemented by the control unit 31 (CPU) executing a program stored in the storage unit 32. The information processing performed by the connector unit 315 and the second product information generation unit 316 is synonymous with the information processing performed by the control unit 31.

[0208] The connector unit 315 includes applications used for platform-related communications. Communication between the dedicated server device 3 and the server device 1 can be conducted via the connector unit 315. Furthermore, communication between the dedicated server device 3 and the enterprise terminal 2 can be conducted via the connector unit 315 or not. The configuration of the connector unit 315 is similar to the connector unit 215 of the enterprise terminal 2 described in the first embodiment, so its description will be omitted.

[0209] The second product information generating unit 316 is configured to receive the product information (first information) generated by the product information generating unit 211 of the enterprise terminal 2 and convert it into product information (second information) corresponding to each platform. The second product information generating unit 316 receives the platform designation from the enterprise terminal 2. At this time, the second product information generating unit 316 generates a user interface including a list of platforms to which the product information is to be sent, and sends the generated user interface to the enterprise terminal 2. Figure 12 As shown, the second product information generating unit 316 is configured to accept a designation of a platform to transmit the second information for any of the company's products.

[0210] Furthermore, the second product information generating unit 316 acquires information (rule information) related to the rules corresponding to the designated platform. The second product information generating unit 316 obtains the second information by, for example, converting the first information using a conversion formula. This second information is generated for each platform.

[0211] Furthermore, the second product information generating unit 316 is configured to transmit the second information to the server device 1 at an arbitrary timing. The second information is transmitted via the connector unit 315. The server device 1 receiving the second information also receives the second information via the connector unit 115.

[0212] The processing in the case of registering the second information by the dedicated server device 3 can be considered to be the same as Figure 17 The flowchart shown is the same. For example, in step S101, the second product information generation unit 316 receives the designation of a platform to which the second information is to be sent. If the operator specifies a platform on the enterprise terminal 2, information related to the designated platform is transmitted to the dedicated server device 3. Upon receiving this information, the second product information generation unit 316 accepts the platform designation.

[0213] Furthermore, in step S102, the second product information generation unit 316 refers to the rule information corresponding to the designated platform. Furthermore, in step S103, the second product information generation unit 316 receives the product information transmitted from the enterprise terminal 2 and stores it in the storage unit 12. This process accepts the input of the first information. Furthermore, in step S104, the second product information generation unit 316 determines whether the first information is sufficient.

[0214] Furthermore, in step S105, the second product information generation unit 316 generates the second information. For example, the second product information generation unit 316 uses a conversion formula included in the rule information to convert the first information into the second information. The generated second information is then passed to the connector unit 315. In step S106, the connector unit 315 selects a connector. Based on the connector information stored in the storage unit 32, the connector unit 315 selects a connector corresponding to the platform specified in step S101.

[0215] In step S107, the connector unit 315 transmits the second information. Alternatively, instead of the connector unit 315 transmitting the second information, the second product information generating unit 316 may allocate (store) the generated second information in a predetermined storage area of ​​the storage unit 32. Furthermore, in step S108, the second product information generating unit 316 outputs a warning indicating insufficient information.

[0216] In this way, the dedicated server device 3 can convert the first information into the second information corresponding to each platform.

[0217] <Fifth embodiment>

[0218] In the fifth embodiment, the server device 1 of the platform generates the second information. Figure 26 1 is a diagram showing a schematic configuration of a system in which the second information is generated by the server device 1. Figure 26 In the example, the first server 1A, the second server 1B, and the third server 1C are server devices 1 on different platforms. The following describes an example in which the first server 1A converts the first information into the second information. When the first server 1A, the second server 1B, and the third server 1C are not distinguished, they are simply referred to as server devices 1.

[0219] Figure 27This figure schematically illustrates an example of the hardware configuration of a first server device 1A according to this embodiment. The first server device 1A is configured as a computer having a control unit 11, a storage unit 12, a communication module 13, and an input / output device 14. The second server device 1B and the third server device 1C may have the same configuration as the first server device 1A or the same configuration as the server device 1 described in the first embodiment. Since the hardware configuration other than the storage unit 12 is the same as in the first embodiment, its description will be omitted.

[0220] The storage unit 12 is a mechanism for storing information and is composed of storage media such as RAM, magnetic disks, and flash memory. The storage unit 12 stores programs executed by the control unit 11, data used by the programs, and the like. In addition, a database is constructed in the storage unit 12, which stores product information collected from multiple enterprise terminals 2, account information related to the enterprise, rule information related to the rules for inputting product information, connector information related to connectors corresponding to each platform, and the like. The product information and account information are the same as the product information and account information stored in the storage unit 12 of the server device 1 in the first embodiment. In addition, the rule information and connector information are the same as the rule information and connector information stored in the storage unit 22 of the enterprise terminal 2 in the first embodiment.

[0221] Among them, the specific hardware structure of the server device 1 can appropriately omit, replace, and add components according to the implementation method. For example, the control unit 11 may include multiple hardware processors. The hardware processor may be composed of a microprocessor, an FPGA, a GPU, etc. The input and output device 14 can be omitted, or input and output devices other than the exemplified devices (for example, an optical drive, etc.) may be added. In addition, the server device 1 can be composed of multiple computers. In this case, the hardware structure of each computer may be consistent or inconsistent.

[0222] Figure 28 This figure schematically illustrates an example of the software configuration of the first server device 1A according to this embodiment. In this embodiment, the control unit 11 is configured to include six software modules: an information collection unit 111, an authority setting unit 112, a correspondence establishment unit 113, an information provision unit 114, a connector unit 115, and a second product information generation unit 116. Each software module can be implemented by the control unit 11 (CPU) executing a program stored in the storage unit 12. The information processing performed by the information collection unit 111, the authority setting unit 112, the correspondence establishment unit 113, the information provision unit 114, the connector unit 115, and the second product information generation unit 116 described below is synonymous with the information processing performed by the control unit 11.

[0223] The information collecting unit 111 , the authority setting unit 112 , the association establishing unit 113 , the information providing unit 114 , and the connector unit 115 are the same as those in the first embodiment, and thus their description is omitted.

[0224] The product information generating unit 211 of the enterprise terminal 2 according to the present embodiment is configured to obtain the first information via the operator of the enterprise terminal 2 and transmit the first information to the first server device 1A at an arbitrary timing.

[0225] The second product information generating unit 116 is configured to convert the first information received by the information collecting unit 111 into product information (second information) corresponding to each platform. The second product information generating unit 116 receives the platform designation from the enterprise terminal 2. The second product information generating unit 116 generates a user interface including a list of platforms to which the product information is to be sent, and sends the generated user interface to the enterprise terminal 2. Figure 12 As shown, the second product information generating unit 116 is configured to accept a designation of a platform to transmit product information for any of the company's products.

[0226] In addition, the second product information generation unit 116 obtains information (rule information) related to the rules corresponding to the designated platform. This rule information can be obtained from the second server device 1B and the third server device 1C, and can be stored in the storage unit 12, or can be obtained from a server device different from the platform's server device 1. The second product information generation unit 116 obtains the second information by, for example, converting the first information using a conversion formula. This second information is generated for each platform. In addition, when the first product information received by the information collection unit 111 from the enterprise terminal 2 does not satisfy the rules of the first server device 1A, second information corresponding to the first server device 1A can be generated and stored in the storage unit 12 of the first server device 1A.

[0227] The second product information generating unit 116 is configured to transmit the second information to the second server 1B and the third server 1C at an arbitrary timing via the connector 115. The second server 1B and the third server 1C receiving the second information also receive the second information via the connector 115.

[0228] The processing when the second information is registered by the first server device 1A can be considered to be the same as Figure 17 The flowchart shown is the same as the one shown. For example, in step S101, the second product information generation unit 116 receives the designation of a platform to which the second information is to be sent. If the operator specifies a platform on the enterprise terminal 2, information related to the designated platform is transmitted to the first server device 1A. By receiving this information, the second product information generation unit 116 accepts the platform designation.

[0229] Furthermore, in step S102, the second product information generating unit 116 refers to the rule information corresponding to the designated platform. Furthermore, in step S103, the information collecting unit 111 receives the product information transmitted from the enterprise terminal 2 and stores it in the storage unit 12. This process accepts the input of the first information. Furthermore, in step S104, the second product information generating unit 116 determines whether the first information is sufficient.

[0230] Furthermore, in step S105, the second product information generation unit 116 generates the second information. For example, the second product information generation unit 116 converts the first information into the second information using a conversion formula included in the rule information. The generated second information is then passed to the connector unit 115. In step S106, the connector unit 115 selects a connector. Based on the connector information stored in the storage unit 12, the connector unit 115 selects a connector corresponding to the platform specified in step S101.

[0231] In step S107, connector unit 115 transmits the second information. Alternatively, instead of connector unit 115 transmitting the second information, second product information generating unit 116 may allocate (store) the generated second information in a predetermined storage area of ​​storage unit 12. Furthermore, in step S108, second product information generating unit 116 outputs a warning indicating insufficient information.

[0232] In this manner, the server device 1 can also convert the first information into the second information corresponding to each platform.

[0233] <Sixth embodiment>

[0234] In the sixth embodiment, an example is described in which second information is provided to a platform (hereinafter also referred to as "target platform") configured to include a server device and an enterprise terminal that manages metadata of a product (hereinafter also referred to as product metadata). Figure 29 1 is a diagram showing a schematic configuration of a system for providing second information to a target platform. Figure 29 In FIG, the first server device 1A and the second server device 1B are server devices 1 of different platforms.

[0235] In the sixth embodiment, similar to the fifth embodiment, the server device 1 generates the second information. Hereinafter, the server device 1 that generates the second information will be referred to as the "first server device 1A". On the other hand, the server device 1 that belongs to the target platform and manages product metadata will be referred to as the "second server device 1B". In addition, the enterprise terminal 2 that sends the first information to the first server device 1A will be referred to as the "first enterprise terminal 2A". In addition, the enterprise terminal 2 that belongs to the target platform will be referred to as the "second enterprise terminal 2B". Hereinafter, when the first server device 1A and the second server device 1B are not distinguished, they will be referred to as the server device 1. In addition, when the first enterprise terminal 2A and the second enterprise terminal 2B are not distinguished, they will be referred to as the enterprise terminal 2. Herein, the target platform is an example of the first platform.

[0236] Multiple second enterprise terminals 2B belong to the target platform, and the storage unit 22 of each second enterprise terminal 2B stores product information for the company's products. To obtain product information on the target platform, a second enterprise terminal 2B accesses the second server 1B and obtains a URL that allows access to the product information. Accessing this URL allows the product information to be obtained from the second enterprise terminal 2B corresponding to the product. In this manner, product information is exchanged between the second enterprise terminals 2B. The first server 1A according to the sixth embodiment is configured to perform the same operations as the second enterprise terminal 2B on the target platform.

[0237] First server 1A obtains first information from first enterprise terminal 2A, generates product metadata from the first information according to the rules of the target platform, and stores the metadata in storage unit 12. Furthermore, the product metadata is registered with second server 1B of the target platform. Furthermore, first server 1A generates second information from the first information according to the rules of the target platform, and stores the second information in storage unit 12. Furthermore, first server 1A provides the second information in response to a request from second enterprise terminal 2B of the target platform.

[0238] The first server device 1A in the sixth embodiment has the same hardware configuration and software configuration as the first server device 1A in the fifth embodiment. Figure 30This figure schematically illustrates an example of the hardware configuration of a second server device 1B according to the sixth embodiment. The second server device 1B is configured as a computer having a control unit 51, a storage unit 52, a communication module 53, and an input / output device 54. The control unit 51, communication module 53, and input / output device 54 of the second server device 1B are similar to the control unit 11, communication module 13, and input / output device 14 of the first server device 1A in the sixth embodiment. The storage unit 52 of the second server device 1B is an information storage mechanism and is composed of storage media such as RAM, a magnetic disk, and flash memory. The storage unit 52 stores programs executed by the control unit 51 and data utilized by these programs. Furthermore, a database is constructed in the storage unit 52, which stores product metadata collected from multiple enterprise terminals 2 and server devices 1, as well as account information related to the enterprises. Product metadata is metadata related to products and, for example, includes a product ID corresponding to each product and a URL (Uniform Resource Locator) that allows access to product information for each product.

[0239] The first enterprise terminal 2A and the second enterprise terminal 2B have Figure 5 The hardware configuration of the enterprise terminal 2 shown in FIG. 1 is the same as that of the enterprise terminal 2. In addition, it is not necessary to store rule information in the storage unit 22 of the first enterprise terminal 2A and the second enterprise terminal 2B. In addition, the specific hardware configuration of the server device 1 and the enterprise terminal 2 can be appropriately omitted, replaced, or added according to the embodiment. In addition, the software configuration of the first enterprise terminal 2A is the same as that of the enterprise terminal 2A. Figure 7 However, the second product information generating unit 216 can be omitted.

[0240] Figure 31 2 is a diagram showing an overview of the processing performed by the server device 1 and the enterprise terminal 2 when the second information is directly transmitted to the enterprise terminal 2. Figure 31 In the example, the first server 1A and the second server 1B are server devices 1 of different platforms. In addition, the second enterprise terminal 2B belongs to the same target platform as the second server 1B. Thus, when providing the second information to the target platform configured to include the second server 1B and the second enterprise terminal 2B, the first server 1A directly sends the second information to the second enterprise terminal 2B. Figure 31 In the example shown, processing is performed in order from (1) to (9).

[0241] like Figure 31As shown in (1), the second product information generation unit 116 of the first server device 1A accepts the designation of the platform from the first enterprise terminal 2A. The second product information generation unit 116 generates a user interface including a list of platforms to which the product information is to be sent, and sends the generated user interface to the first enterprise terminal 2A. The second product information generation unit 116 is configured to accept the designation of the platform to which the product information is to be sent from the first enterprise terminal 2A. In addition, as another example, the product information generation unit 211 of the first enterprise terminal 2A can generate a user interface including a list of platforms to which the product information is to be sent. The product information generation unit 211 can be configured to obtain the first information via the operator of the first enterprise terminal 2A and send it to the first server device 1A at an arbitrary timing. The first server device 1A and the first enterprise terminal 2A communicate via the connector unit 115 and the connector unit 215.

[0242] like Figure 31 As shown in (2), the information collecting unit 111 of the first server device 1A receives the first information sent from the first enterprise terminal 2A and stores the first information in the storage unit 12. Thus, the first information is obtained. Figure 8 As described, the product information generation unit 211 of the first enterprise terminal 2A accepts the input of product information (first information) via the operator. When inputting product information, it can be input in any input form or in an input form corresponding to the designated platform. In addition, it can be input according to the rules of the designated platform. In addition, when multiple platforms are designated, it can be input in an input form corresponding to any platform. The designation of the platform and the input of the first information can be performed on one screen. The connector unit 215 of the first enterprise terminal 2A sends the first information generated by the product information generation unit 211 of the first enterprise terminal 2A to the first server device 1A. The information collection unit 111 of the first server device 1A obtains the first information via the connector unit 115.

[0243] like Figure 31 As shown in (3), the second product information generation unit 116 of the first server device 1A generates product metadata based on the first information. The second product information generation unit 116 of the first server device 1A obtains information (rule information) related to the rules corresponding to the specified object platform. The rule information can be obtained from the second server device 1B, can be stored in the storage unit 12, or can be obtained from a server device different from the platform's server device 1. Product metadata is generated according to the rules of the object platform. The rules for generating product metadata are included in the rule information. The second product information generation unit 116, for example, generates a URL that can access the second information corresponding to the first information, establishes a correspondence with the product ID to generate product metadata, and stores the product metadata in the storage unit 12.

[0244] like Figure 31 As shown in (4), the connector unit 115 of the first server device 1A registers the product metadata in the target platform by sending the product metadata to the second server device 1B. Thus, when the product metadata is sent to the second server device 1B, it is sent via the connector unit 115. The product metadata includes a URL that can access product information and a product ID. The control unit 51 of the second server device 1B stores the received product metadata in the storage unit 52. In this way, the second information corresponding to the first enterprise terminal 2A can be accessed from the second enterprise terminal 2B in the target platform.

[0245] Next, when the operator of the second enterprise terminal 2B wants to obtain product information corresponding to the first enterprise terminal 2A, the control unit 21 of the second enterprise terminal 2B receives the designation of the product ID via the operator. Figure 31 As shown in (5), the control unit 21 of the second enterprise terminal 2B sends the product ID to the second server device 1B to retrieve the product metadata corresponding to the product ID. If the control unit 51 of the second server device 1B receives the product ID, it refers to the product metadata stored in the storage unit 52 and extracts the URL corresponding to the product ID. Figure 31 As shown in (6), the control unit 51 of the second server device 1B transmits the extracted URL to the second enterprise terminal 2B.

[0246] like Figure 31 As shown in (7), the control unit 21 of the second enterprise terminal 2B, having obtained the URL from the second server 1B, accesses the obtained URL to request product information from the first server 1A. This request is sent via the connector of the second enterprise terminal 2B. The second product information generation unit 116 of the first server 1A accepts this request. When the first server 1A receives the request for product information from the second enterprise terminal 2B, the connector unit 115 receives it. The connector unit 115 forwards the received request to the second product information generation unit 116.

[0247] like Figure 31 As shown in (8), the second product information generating unit 116 of the first server device 1A that receives the request for product information obtains information related to the rules corresponding to the target platform (rule information). The rule information can be obtained from the second server device 1B, can be stored in the storage unit 12, or can be obtained from a server device different from the platform's server device 1. The second product information generating unit 116 obtains the second information by, for example, converting the first information corresponding to the URL using a conversion formula. Moreover, as Figure 31As shown in (9), the connector unit 115 of the first server device 1A sends the second information corresponding to the URL to the second enterprise terminal 2B. In this way, when the second information is sent to the second enterprise terminal 2B, it is sent via the connector unit 115. In this way, the second information is provided to the second enterprise terminal 2B.

[0248] The timing for generating the second information is not limited to after a request for product information is received from the second enterprise terminal 2B. For example, the second information can be generated at any time between the time the first information is received by the first enterprise terminal 2A and the time the second information is provided to the second enterprise terminal 2B. For example, the second information can be generated based on the first information and rule information after the first information is received from the first enterprise terminal 2A and before the product metadata is generated. Furthermore, as described in the first embodiment, the second information can also be generated in the first enterprise terminal 2A. In this case, the second information can be sent from the first enterprise terminal 2A to the first server device 1A, and the second information can be stored in the storage unit 12 of the first server device 1A.

[0249] [Processing Flow]

[0250] Next, refer to Figure 32 and Figure 33 The flow of processing executed in the first server device 1A will be described. Figure 32 This is a flowchart of the process of registering product metadata on the target platform. This routine is executed upon receipt of information related to platform designation from the first enterprise terminal 2A.

[0251] In step S401, the second product information generation unit 116 accepts the designation of a platform to which the second information is to be transmitted. When an operator designates a platform on the first enterprise terminal 2A, information related to the designated platform is transmitted from the first enterprise terminal 2A to the first server device 1A. By receiving this information, the second product information generation unit 116 accepts the designation of the platform.

[0252] Furthermore, in step S402, the second product information generation unit 116 refers to the rule information corresponding to the designated platform. Furthermore, in step S403, the information collection unit 111 receives the product information transmitted from the first enterprise terminal 2A via the connector unit 115 and stores the product information in the storage unit 12. This process accepts the input of the first information. The processes of steps S401 and S403 can be performed simultaneously. In this case, the platform is designated and the first information is transmitted simultaneously from the first enterprise terminal 2A. Alternatively, the process of step S403 can be performed before the process of step S401.

[0253] The following processes from steps S404 to S412 are repeatedly executed for all platforms specified in step S401. In step S404, the second product information generation unit 116 determines whether the first information is sufficient. If a negative determination is made in step S404, the second product information generation unit 116 outputs a warning indicating insufficient information in step S405. If insufficient information is present, inventory data can be used to supplement the information, similar to the second embodiment.

[0254] In step S406, the second product information generation unit 116 determines whether product metadata is required. Specifically, the second product information generation unit 116 determines whether the specified platform is the target platform. If the determination in step S406 is positive, the process proceeds to step S407; if not, the process proceeds to step S410.

[0255] In step S407, the second product information generation unit 116 generates product metadata. The second product information generation unit 116 references the rule information corresponding to the target platform. Furthermore, the product metadata is generated based on the rule information. The generated product metadata is passed to the connector unit 115. In step S408, the connector unit 115 selects a connector. Based on the connector information stored in the storage unit 12, the connector unit 115 selects a connector corresponding to the target platform specified in step S401. In step S409, the connector unit 115 transmits the product metadata to the second server device 1B corresponding to the target platform.

[0256] Furthermore, in step S410, the second product information generation unit 116 generates the second information. For example, the second product information generation unit 116 uses a conversion formula included in the rule information to convert the first information into the second information. The generated second information is then passed to the connector unit 115. In step S411, the connector unit 115 selects a connector. Based on the connector information stored in the storage unit 12, the connector unit 115 selects a connector corresponding to the platform specified in step S401.

[0257] In step S412 , the connector unit 115 transmits the second information. If the target platform is specified, the second product information generating unit 116 arranges (stores) the generated second information in a predetermined storage area of ​​the storage unit 12 .

[0258] Next, Figure 33This is a flowchart of the process of providing second product information to the second enterprise terminal 2B of the target platform. This routine is triggered by receiving a request for product information from the second enterprise terminal 2B. In step S501, the second product information generation unit 116 accepts the request for product information. This request is for sending product information to the second enterprise terminal 2B. This request is executed by the second enterprise terminal 2B accessing the URL corresponding to the product and entering the specified input. The connector unit 115 receives this request and forwards it to the second product information generation unit 116, which then accepts it.

[0259] In step S502, the second product information generation unit 116 extracts the second information allocated to the specified storage area of ​​the storage unit 12. Since the URL accessed by the second enterprise terminal 2B is associated with the product ID, the second product information generation unit 116 extracts the corresponding second information based on the product ID. The extracted second information is then passed to the connector unit 115. In step S503, the connector unit 115 selects a connector. The connector unit 115 selects the connector used when the request was received in step S501. In step S504, the connector unit 115 transmits the second information to the second enterprise terminal 2B. In this way, the first server device 1A can operate similarly to the second enterprise terminal 2B on the target platform and provide product information.

[0260] Among them, Figure 32 In the flowchart shown, the second information for the target platform is generated in step S410 and stored in the storage unit 12 in step S412. However, the timing of generating the second information is not limited to this. For example, Figure 33 The second information is generated in step S502 of the flowchart shown in FIG. That is, the second information may be generated after a request for product information is received from the second enterprise terminal 2B.

[0261] As described above, according to the sixth embodiment, the second server device 1B manages product metadata and can convert the first information into the second information and provide it even on a target platform where product information is exchanged between enterprise terminals 2. Furthermore, in this case, the second information can be provided via a connector compatible with the target platform.

[0262] (Other embodiments)

[0263] The above-described embodiment is merely an example, and the present disclosure can be implemented with appropriate modifications without departing from the spirit of the present disclosure. For example, the processes and mechanisms described in the present disclosure can be implemented in combination as long as no technical contradiction arises.

[0264] In the description of the embodiment, the server device 1 stores the product information in the database, but the product information may be stored in a mechanism other than the database.

[0265] Furthermore, while the description of the embodiment illustrates a method in which the product tree is completed by server device 1 executing stages 1 through 4, the functions of server device 1 can also be distributed across multiple enterprise terminals 2. For example, product information can be stored in a decentralized database utilizing blockchain technology. In this case, the product information database can be composed of multiple enterprise terminals 2. In this case, smart contracts can also be used to execute the processing of each of the aforementioned stages. For example, the execution of the second stage can be triggered by the writing of permission information to the database by a certain enterprise account. Alternatively, the execution of the third stage can be triggered by the writing of a corresponding establishment request to the database by a certain enterprise account.

[0266] Furthermore, while the description of the embodiment separately describes the stage in which the server device 1 receives product information related to an upstream product and the stage in which the server device 1 receives permission information corresponding to the product information, both stages may be received simultaneously. Similarly, while the description of the embodiment separately describes the stage in which the server device 1 receives product information related to a downstream product and the stage in which the server device 1 receives a correspondence establishment request corresponding to the product information, both stages may be received simultaneously.

[0267] In addition, in the above embodiment, access control for each company is achieved by setting up a dedicated storage area and a shared storage area. However, the method of implementing access control is not limited to this example. Any method can be used for access control.

[0268] In addition, in the above embodiment ( Figure 1 ), the multiple enterprises included in the supply chain are described as enterprises that produce products. However, the enterprises included in the supply chain do not necessarily need to be enterprises that produce products. For example, enterprises that transport, import, store, wholesale, etc. products may also be included in the enterprises that constitute the supply chain. In one example, some of the multiple enterprises may be enterprises that do not perform manufacturing processes, such as trading companies, sales agencies, import agencies, etc., and may also receive products from enterprises at the upper level (upstream enterprises) and deliver products to enterprises at the lower level (downstream enterprises).

[0269] Furthermore, in the above embodiment, the supply chain for automotive-related products is described, with the OEM manufacturer as the most downstream enterprise and the enterprises that supply parts, materials, and components as suppliers. However, the enterprises in the supply chain are not limited to this. The enterprises at each stage can be appropriately determined based on the product, etc. Furthermore, the manufacturing activities performed at each enterprise until the final product is obtained can be appropriately determined according to the embodiment; for example, they can include all activities that may be carried out until the final product is obtained, such as excavation, processing, assembly, transportation, and storage.

[0270] Furthermore, in the above embodiment, the server device 1 is configured to perform the information processing in the first through fourth stages. However, the configuration of the server device 1 is not limited to this example. In another example, at least one of the information processing in the first through fourth stages may be omitted from the server device 1. The server device 1 may also be configured to perform any other information processing.

[0271] In addition, in the above embodiment, an example of calculating the CO2 emission (CFP value) is shown. The CFP value can also be calculated according to the following calculation formula.

[0272] Tier N-1's CFP value = Tier N-1's own measured CFP value + Σ k (CFP value of company k (Tier N) × usage u in Tier N-1) k )

[0273] Here, "Tier N-1's CFP value" represents the result of combining the CFP values ​​of the upstream company (company k (Tier N)) and the company's CFP value. The CFP value measured by the company represents the CFP value included in each company's product information. When Tier N is the most upstream company, "Tier N's ​​CFP value" is the CFP value included in that company's product information. In other cases, "Tier N's ​​CFP value" is the result of combining the CFP values ​​of the further upstream company (Tier N+1) with the CFP value included in that company's product information. By setting Tier N to the most upstream company (the terminal company) and repeating the calculation until N = 1, the CFP value of the Tier 0 product (= final product) can be obtained.

[0274] In the above embodiment, the server device 1 may calculate the recovery rate and due diligence (score) in addition to or instead of calculating the CO2 emission amount (CFP value). The recovery rate can be calculated according to the following calculation formula.

[0275] “(Recovery rate of Tier N-1 products for the target substance) = {(Total amount used in Tier N-1) × (Recovery rate in Tier N-1) + Σ k (Total usage in company k (Tier N) × Recycling rate in company k (Tier N) × Usage in Tier N-1 u k )}÷{Total utilization in TierN-1+Σ k (Total usage in company k (Tier N) × usage in Tier N-1 u k )}={recycled material usage in Tier N-1 + Σk(recycled material usage in k company (Tier N) × usage in Tier N-1 u k )}÷{Total usage in TierN-1+Σk(Total usage in company k (TierN)×usage in TierN-1 u k )}”

[0276] The amount of recycled material used represents the amount of recovered material used for the target substance. Similar to the CFP value, by calculating sequentially from the most upstream enterprise (end enterprise), the recovery rate of the target substance in the final product can be calculated. Furthermore, the due diligence score (DD score) can also be synthesized using the same calculations as the CFP value and recovery rate described above. In one example, by replacing the CFP value with the DD score and calculating sequentially from the most upstream enterprise (end enterprise), the DD score (combined result) in the final product can be obtained.

[0277] Furthermore, in the above embodiment, instead of storing the traceability-related information of each company (Tier N-1) other than the most upstream company in a shared storage area with its downstream companies, the combined results of each company (Tier N-1's CFP value and the recovery rate of target substances in Tier N-1 products) can be stored in a shared storage area between each company and its downstream companies (Tier N-2). This allows the traceability-related information (comprehensive results) of the final product to be obtained without disclosing each company's own traceability-related information.

[0278] In addition, in the above embodiment, it is assumed that each enterprise orders a certain material from one company. However, in the above embodiment, the ordering form of each enterprise is not limited to this example. At least part of the enterprises in the supply chain can order the same product from multiple upstream enterprises and selectively use the obtained upstream products for their own products. For example, in the above Figure 14In the example, product A11_1, product A11_2 or product A11_3 of Tier2 can be selectively used in product A1 of Tier1. In this case, the server device 1 can maintain a corresponding establishment relationship according to each model used. In the above example, for product A1 of Tier1, the server device 1 can maintain corresponding establishment information as model 1 "product A11_1, ··· of Tier2", model 2 "product A11_2, ···" and model 3 "product A11_3, ···". Correspondingly, the server device 1 can perform the calculation (integration) of the above traceability association information according to each model. In this case, in one example, the server device 1 can output the calculation result according to each model. In another example, the server device 1 can calculate the statistics such as the maximum value, minimum value, average value, variance, standard deviation, central value of the calculation result based on the calculation result, and output the calculated statistics.

[0279] Furthermore, in the above embodiment, the traceability-related information (particularly the CFP value) may be composed of primary data or secondary data (inventory data). In this case, the calculation (integration) of the traceability-related information may include calculating the ratio of the primary data of the traceability-related information obtained for the final product. The calculation of the primary data ratio may be performed using a simple ratio calculation or a weighted calculation, wherein the CFP value is replaced with the primary data ratio of each company in the CFP value calculation formula and the ratio is calculated sequentially from the most upstream enterprise.

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

[0281] The present disclosure can also be implemented by supplying a computer with a computer program having the functions described in the above-mentioned embodiments installed therein, and having one or more processors of the computer read out and execute the program. Such a computer program can be provided to the computer via a non-temporary computer-readable storage medium that can be connected to the system bus of the computer, or can be provided to the computer via a network. Non-temporary computer-readable storage media include, for example, any type of disk such as a magnetic disk (floppy disk (registered trademark), 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, or any type of medium suitable for storing electronic commands.

[0282] Description of Reference Numerals

[0283] 1…server device; 2…enterprise terminal; 3…dedicated server device; 21…control unit; 22…storage unit; 23…communication module; 24…input / output device; 211…product information generation unit; 212…authority setting unit; 213…corresponding establishment request unit; 214…information acquisition unit; 215…connector unit; 216…second product information generation unit.

Claims

1. An information processing device, wherein: The information processing device includes a control unit configured to execute the following processing: Accept the designation of more than one first platform for managing the supply chain; accepting input of first information related to a first product including information related to traceability; generating second information corresponding to each of the first platforms from the first information, referring to information related to rules for sending information to the first platforms respectively; as well as The second information is transmitted to each of the first platforms via the corresponding connectors with reference to information related to the connectors corresponding to the first platforms, or the second information is arranged in a predetermined storage area in a transmittable state.

2. The information processing device according to claim 1, wherein Information on rules for transmitting information to each of the first platforms and information on connectors corresponding to each of the first platforms are arranged in the predetermined storage area.

3. The information processing device according to claim 1, wherein The control unit refers to inventory data corresponding to the first platform in response to the presence of information that is insufficient based on the first information alone for the information requested by the first platform. The second information is generated based on information obtained from the inventory data to supplement information that is insufficient based on the first information alone.

4. The information processing device according to claim 1, wherein: The control unit outputs a warning in response to the presence of information required by the first platform that is insufficient based on the first information alone. The information processing device according to claim 1 , wherein: In response to third information designated as non-public being included in the first information, the control unit generates the second information by excluding the third information. The information processing apparatus according to claim 5 , wherein: The control unit refers to inventory data corresponding to the first platform in response to the third information being included in the first information. The second information is generated by supplementing the excluded third information with information obtained from the inventory data.

7. The information processing apparatus according to claim 1, wherein: The information related to the rules for sending information to the first platform includes information related to the rules related to fourth information, wherein the fourth information is information that cannot be disclosed depending on the location of the terminal that sends information to the first platform. The control unit generates the second information by excluding the fourth information in response to the fourth information being included in the first information.

8. The information processing apparatus according to claim 7, wherein: The control unit refers to inventory data corresponding to the first platform in response to the fourth information being included in the first information. The second information is generated by supplementing the excluded fourth information with information obtained from the inventory data.

9. The information processing apparatus according to claim 1, wherein: The information related to the rules for sending information to the first platform includes information related to the rules of the unit. The control unit generates the second information according to a rule of the unit corresponding to the first platform.

10. The information processing apparatus according to claim 1, wherein: The first product is a battery-related product.

11. An information processing method, wherein: The following processing is performed by a computer: Accept the designation of more than one first platform for managing the supply chain; accepting input of first information related to a first product including information related to traceability; generating second information corresponding to each of the first platforms from the first information, referring to information related to rules for sending information to the first platforms respectively; as well as The second information is transmitted to each of the first platforms via the corresponding connectors with reference to information related to the connectors corresponding to the first platforms, or the second information is arranged in a predetermined storage area in a transmittable state.

12. The information processing method according to claim 11, wherein: Information on rules for transmitting information to each of the first platforms and information on connectors corresponding to each of the first platforms are arranged in the predetermined storage area.

13. The information processing method according to claim 11, wherein: The computer refers to inventory data corresponding to the first platform in response to the presence of information that is insufficient based on the first information alone for the information requested by the first platform. The second information is generated based on information obtained from the inventory data to supplement information that is insufficient based on the first information alone.

14. The information processing method according to claim 11, wherein: The computer outputs a warning in response to the presence of information required by the first platform that is insufficient based on only the first information.

15. The information processing method according to claim 11, wherein: In response to third information designated as non-public being included in the first information, the computer generates the second information by excluding the third information.

16. The information processing method according to claim 15, wherein: In response to the third information being included in the first information, the computer refers to inventory data corresponding to the first platform. The second information is generated by supplementing the excluded third information with information obtained from the inventory data.

17. The information processing method according to claim 11, wherein: The information related to the rules for sending information to the first platform includes information related to the rules related to fourth information, wherein the fourth information is information that cannot be disclosed depending on the location of the terminal that sends information to the first platform. The computer generates the second information by excluding the fourth information in response to the fourth information being included in the first information.

18. The information processing method according to claim 17, wherein: In response to the fourth information being included in the first information, the computer refers to inventory data corresponding to the first platform. The second information is generated by supplementing the excluded fourth information with information obtained from the inventory data.

19. The information processing method according to claim 11, wherein: The information related to the rules for sending information to the first platform includes information related to the rules of the unit. The computer generates the second information according to a rule of the unit corresponding to the first platform.

20. The information processing method according to claim 11, wherein: The first product is a battery-related product.

Images