Information processing method, information processing program, and information processing apparatus

Abstract

The present invention provides an information processing method, an information processing program, and an information processing device for calculating greenhouse gas emissions. [Solution] The information processing method, when acquiring data on activities related to the activities of a business operator that involve other business operators during a predetermined period, adopts data that other business operators have provided in a period prior to the predetermined period, and performs predetermined processing based on the adopted data.

Description

[Technical Field]

[0001] The present invention relates to an information processing method, an information processing program, and an information processing apparatus. [Background Art]

[0002] Patent Document 1 discloses an information processing system capable of grasping the status of greenhouse gas emissions across the entire supply chain. [Prior Art Literature] [Patent Literature]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2024-7513 [Summary of the Invention] [Means for Solving the Problem]

[0004] An information processing method according to one aspect of the present invention, when acquiring data related to an activity involving another business operator related to an activity of a business operator in a predetermined period, adopts data answered by said another business operator in a period before said predetermined period, and performs predetermined processing based on the adopted data.

[0005] In the above information processing method, the data relates to ESG or sustainability, and when an activity amount for calculating greenhouse gas emissions is acquired, the predetermined processing may be processing for calculating said emissions based on the acquired activity amount.

[0006] In the above information processing method, prior to adopting data answered by said another business operator in a period before said predetermined period as the data related to said activity, a confirmation message is output to said another business operator, and when a statement that there is no change to said data is acquired as a reply to said confirmation message, the data answered by said another business operator in the period before said predetermined period may be adopted.

[0007] In the above-described information processing method, the confirmation message may include a request for the updated data if there are any changes to the data, and if the updated data is obtained as a response to the confirmation message, the predetermined processing may be performed based on the updated data.

[0008] In the above information processing method, if multiple data responses are received from one of the aforementioned other businesses, a confirmation message may be sent to the aforementioned other business, and for each of the multiple data, a confirmation message may be obtained from the aforementioned other business indicating that there have been no changes from the data provided in a period prior to the aforementioned period, or the data after the changes.

[0009] In the above information processing method, if the elapsed period from the previous period to the predetermined period exceeds a threshold, the confirmation message may be output to the other business operator.

[0010] An information processing program according to one aspect of the present invention may, when acquiring data relating to the activities of the business operator in which other business operators are involved during a predetermined period, adopt data that other business operators have provided in a period prior to the predetermined period, and perform predetermined processing based on the adopted data.

[0011] An information processing device according to one aspect of the present invention is a calculation device comprising a control unit, wherein, when acquiring data relating to activities of a business operator in which other business operators are involved in the activities of a business operator during a predetermined period, the control unit adopts data that other business operators have responded to in a period prior to the predetermined period, and performs predetermined processing based on the adopted data.

[0012] It should be noted that the above summary of the invention does not enumerate all of its features. Furthermore, subcombinations of these features may also constitute an invention. [Brief explanation of the drawing]

[0013] [Figure 1]It is an explanatory diagram showing a configuration example of an information system. [Figure 2] It is an explanatory diagram showing a hierarchy example of a plurality of enterprises. [Figure 3] It is an explanatory diagram showing an example of an organization hierarchy within an enterprise. [Figure 4] It is an explanatory diagram showing a configuration example of a supply chain. [Figure 5] It is a flowchart showing a procedure example of collection and disclosure work. [Figure 6] It is an explanatory diagram showing an example of an enterprise database. [Figure 7] It is an explanatory diagram showing an example of a base database. [Figure 8] It is an explanatory diagram showing an example of an account database. [Figure 9] It is an explanatory diagram showing an example of an input status database. [Figure 10] It is an explanatory diagram showing an example of an input database. [Figure 11] It is an explanatory diagram showing an example of an approval database. [Figure 12] It is an explanatory diagram showing an example of a confirmation database. [Figure 13] It is an explanatory diagram showing a configuration example of the sustainability ERP system 10. [Figure 14] It is an explanatory diagram showing another configuration example of the sustainability ERP system 10. [Figure 15] It is an explanatory diagram showing another configuration example of the sustainability ERP system 10. [Figure 16] It is a block diagram showing a hardware configuration example of a server. [Figure 17] It is a block diagram showing a hardware configuration of a terminal. [Figure 18] It is an explanatory diagram showing a bill of materials of a monitor in a tree structure. [Figure 19] It is an explanatory diagram showing a bill of materials of a reflector sheet in a tree structure. [Figure 20] It is an explanatory diagram showing an example of a bill of materials. [Figure 21] It is an explanatory diagram showing an example of a product calculation value database. [Figure 22]This is an explanatory diagram showing an example of a parts calculation value database. [Figure 23] This is an explanatory diagram showing an example of a processing calculation value database. [Figure 24] This is an explanatory diagram showing an example of a material calculation value database. [Figure 25] This is an explanatory diagram showing an example of a database for calculating material processing values. [Figure 26] This flowchart shows an example of the calculation process. [Figure 27] This is a flowchart showing an example of the procedure for processing a request. [Figure 28] This is an explanatory diagram showing an example of a request settings screen. [Figure 29] This flowchart shows an example of the verification process. [Figure 30] This is a flowchart showing an example of the response processing procedure. [Figure 31] This flowchart shows other examples of calculation procedures. [Figure 32] This flowchart shows other examples of the verification process. [Figure 33] This is an explanatory diagram showing an example of an inquiry screen. [Figure 34] This is an explanatory diagram showing an example of a screen indicating that the transmission has been completed. [Modes for carrying out the invention]

[0014] The present invention will be described below through embodiments, but these embodiments are not intended to limit the invention as defined in the claims. Furthermore, not all combinations of features described in the embodiments are necessarily essential to the solution of the invention. In this specification, information that is easy for computers to handle but whose meaning and significance are difficult for humans to understand or interpret, such as mere numbers or symbols or combinations thereof, is referred to as data, but this is not limited to such information.

[0015] In recent years, companies and organizations have been required to adopt sustainable management and operations. Sustainable management and operations refer to management and operations that aim for growth and progress from a long-term perspective, rather than simply pursuing short-term profits. Sustainable management and operations require growing and progressing together in cooperation with various stakeholders, and contributing to the improvement or maintenance of the global environment. The following explanation will focus on corporate management, but the same principles apply to the operation of organizations.

[0016] To conduct sustainable business operations, companies need to collect data from many related organizations and groups. For example, timely data collection is necessary to improve operations by implementing the PDCA cycle. To conduct sound business operations, it is essential to receive investment from investors. In particular, whether or not a company can receive investment from institutional investors is important. Therefore, it is a company's responsibility to collect and disclose data in a timely manner so that institutional investors can use it to make investment decisions. And because institutional investors invest globally, global standards have been established for information disclosure. Hereafter, these standards for information disclosure will be referred to as disclosure standards.

[0017] The data that companies should collect includes not only the financial data that has been collected in the past, but also what is called non-financial data. Non-financial data is data related to sustainability. For example, non-financial data is classified into governance, strategy, risk management, metrics, and targets. Metrics and targets include greenhouse gas (GHG: GreenHouse GAS) emissions for each company. Non-financial data is associated with identifying information that uniquely identifies a company, such as a company ID. Another way to classify non-financial data is to divide it into categories: E (Environment), S (Social), and G (Governance).

[0018] Greenhouse gas emissions are calculated by multiplying carbon dioxide emissions and emissions of other gases, methane, nitrous oxide, perfluorinated compounds, chlorofluorocarbons (CFCs), sulfur hexafluoride, and nitrogen trifluoride by the global warming potential to convert them into carbon dioxide equivalents. Hereinafter, carbon dioxide emissions and the values ​​obtained by converting emissions of greenhouse gases other than carbon dioxide into carbon dioxide equivalents will be collectively referred to as carbon dioxide emissions.

[0019] Carbon dioxide emissions include direct emissions, indirect emissions, and other indirect emissions. Carbon dioxide emissions may also be derived by multiplying the amount of electricity, water, oil, and gas used by an emission factor that indicates the amount of emissions per unit of each use.

[0020] As non-financial data, companies may manage information on human rights measures and disaster risk measures related to the products and services they handle. Human rights measures may include, for example, whether measures are in place to prevent child labor in the manufacturing of products (including not only the assembly of the product itself, but also the assembly of components that make up the product, the processing of materials (including raw materials, etc.) that make up each component, and all other processes related to the manufacturing of the product). Disaster risk measures may include whether measures are in place to prevent the manufacturing of products from being affected in the event of a disaster. In addition, as financial or non-financial data, any other information that the end-user company wishes to request from related companies may be included. For example, this may include various types of damage calculation-based environmental impact assessments, environmental information such as product carbon footprints related to climate change, biodiversity, land use, and raw material procurement related to natural resources, hazardous materials, waste management, and waste such as packaging materials and home appliances related to waste disposal, contained chemical substances, air pollutants, water quality, and soil contamination related to environmentally regulated substances, and other environmental information such as technology, energy, noise, vibration, and odor. Furthermore, information regarding society may include human rights related to human resources (child labor, forced labor, working hours, wages, labor rights, discrimination, etc.), labor management and occupational health and safety, human capital, safety and quality related to the safety of products and services, safety of each substance, privacy and data security, community relations, diversity, equity and inclusion, well-being and engagement, compliance and ethics, and other information related to society. In addition, information regarding governance may include ethics and legal compliance related to corporate conduct, anti-corruption, risk management and disaster response, tax transparency, and other information related to governance. Information regarding due diligence may also be included.

[0021] Location information may be included as one of the non-financial data items. An example of location information is coordinate values ​​in a geographic coordinate system (such as the Japanese Geodetic System, Japanese Geodetic System 2000, Japanese Geodetic System 2011, WSG84, etc.). Geographic coordinate values ​​are latitude and longitude. In addition, coordinate values ​​from various projected coordinate systems (plane rectangular coordinate system, UTM coordinate system, Web Mercator coordinate system) may be used as location information. Location information may also include height information, such as elevation, altitude, and sea level. Location information is not limited to coordinate values ​​that indicate a single point, but may also include country names, regional names, administrative division names, telephone area codes, postal codes, building names, etc. Country codes as defined in ISO 3166-1 may be used instead of country names. Regional names in Japan, for example, are Hokkaido, Tohoku, Kanto, Chubu, Kinki, Chugoku / Shikoku, and Kyushu. Administrative division names in Japan, for example, are prefecture names, county / designated city names, and city / ward / town / village names. You may use a prefecture code instead of a prefecture name, or an administrative area code consisting of a prefecture code and a municipal code instead of a city / ward / town / village name.

[0022] Non-financial data may include the following information regarding environmental impact: the amounts of by-products, NOx, SOx, BOD, COD, etc. from each of the above-mentioned usage amounts, the impact areas such as air pollution, air pollution, hazardous chemicals, ozone depletion, acidification, noise, global warming, photochemical oxidants, eutrophication, resource consumption, ecotoxicity, fuel consumption, land use, etc., human health based on damage assessment, social projections, biodiversity, primary production, and other protected entities, and the amounts derived using unit consumption factors.

[0023] Direct emissions refer to carbon dioxide emissions (thousand tons of CO2) that fall under Scope 1 of so-called supply chain emissions. Indirect emissions refer to carbon dioxide emissions indirectly emitted by a company through energy purchases during a specified period (fiscal year, quarter, etc.). Indirect emissions refer to carbon dioxide emissions (thousand tons of CO2) that fall under Scope 2 of supply chain emissions. Other indirect emissions refer to carbon dioxide emissions from company activities that are not included in Scope 1 direct emissions or Scope 2 indirect emissions. Other indirect emissions refer to carbon dioxide emissions (thousand tons of CO2) that fall under Scope 3 of supply chain emissions.

[0024] The amount of carbon dioxide reduction represents the reduction from carbon dioxide emissions during the comparison period. The reduction may be shown separately for direct emissions, indirect emissions, and other indirect emissions. Instead of the reduction from the comparison period, the percentage change in emissions (e.g., a 10% reduction compared to the previous year) may be included in the non-financial data. Furthermore, the reduction contribution, which is the amount of reduction achieved per unit of product or service compared to the current carbon dioxide emissions of the product or service, the results of the LCA (Life Cycle Assessment) at the product or service level, or the carbon dioxide emissions (carbon footprint) at the product or service level may also be included in the non-financial data.

[0025] As explained above, for companies to conduct sustainable business, they need to collect financial and non-financial data and disclose and report it appropriately. The core system that supports sustainable business is the Sustainability ERP (Enterprise Resources Planning) system. Sustainability ERP systems enable companies to collect financial and non-financial data precisely and in a short period of time. As a result, it becomes possible to disclose non-financial data simultaneously with financial data. Furthermore, by having the Sustainability ERP system manage financial and non-financial data, it becomes possible to ensure the reliability of the data that can withstand audits. The Sustainability ERP system and systems that work in conjunction with it will be described below.

[0026] Figure 1 is an explanatory diagram showing an example of the information system configuration. The information system 100 is a system centered around the sustainability ERP system 10, and includes systems that link with the said system. The information system 100 includes the sustainability ERP system 10, user companies 20, information providing organizations 30, linking systems 40, formulation organizations 50, receiving organizations 60, cloud services 70, information sites 80, and stakeholders 90.

[0027] Sustainability ERP System 10 is a computer system that supports user companies in conducting sustainable business operations. Sustainability ERP System 10 collects financial and non-financial data related to user companies and discloses or submits the collected data either as is or after processing.

[0028] User company 20 is a company that uses the sustainability ERP system 10. In Figure 1, User company 20 more precisely refers to the computer or computer system used by User company 20. However, in this specification, the scope of User company 20 is broadly defined, and in addition to the company as an organization, it also includes the company's employees, the computers and computer systems used by the company, and so on. Furthermore, User company 20 may not refer to a single company, but rather to a corporate group including a holding company with many subsidiaries and its subsidiaries.

[0029] Information providers 30 are organizations that provide information necessary for operating the Sustainability ERP System 10. For example, the Ministry of the Environment, which provides emission factors necessary for calculating GHG emissions, is an example of an information provider 30. Similarly, the IDEA Lab of the National Institute of Advanced Industrial Science and Technology (AIST), which creates the LCI (Life Cycle Inventory) database IDEA (Inventory Database for Environmental Analysis) and provides it through agents, is another example of an information provider 30. For convenience, agents providing IDEA are also included in the category of information providers 30.

[0030] Furthermore, information providers 30 are organizations that collect information from user companies 20 and provide the collected information upon request, primarily for a fee. It is assumed that information providers 30 have no conflict of interest with user companies 20. This is because the information collected and provided by information providers 30 must be fair and accurate. For example, credit rating agencies and think tanks are examples of information providers 30. Information providers 30 also include public institutions, NPOs (Nonprofit Organizations), and NGOs (Non-Governmental Organizations) that provide fair and accurate information free of charge or at low cost. The Japan Electric Power Data Management Association is an example of an information provider 30. Similar to user companies 20, information providers 30 refer not only to the organization itself, but also to its employees, computers, and computer systems used by the organization. The Financial Services Agency and EDINET, which is operated by the Financial Services Agency, are examples of information providers 30.

[0031] The linked system 40 communicates with the sustainability ERP system 10 and provides the sustainability ERP system 10 with data it possesses from user companies 20. The linked system 40 also receives data from user companies 20 from the sustainability ERP system 10. Data exchange between the sustainability ERP system 10 and the linked system 40 may be performed as needed via an API (Application Programmable Interface) or periodically via batch processing. Data exchange between the sustainability ERP system 10 and the linked system 40 may also be performed without using a network, by writing data to a recording medium, transporting the recording medium, and reading data from the recording medium. Note that a system provided by an information provider 30 can be the linked system 40. For example, the system that performs the electricity data provision service provided by the Japan Electric Power Data Management Association, which is an information provider 30, corresponds to the linked system 40.

[0032] The 50 regulatory bodies are organizations that develop disclosure standards. Disclosures include not only statutory and timely disclosures, but also disclosures required by non-profit organizations. Examples of the 50 regulatory bodies include the SSBJ (Sustainability Standards Board), the European Financial Reporting Advisory Group (EFRAG) in Europe, the US Securities and Exchange Commission (SEC) in the United States, and international organizations such as the GHG Protocol Initiative, the Global Reporting Initiative (GRI), the Carbon Disclosure Project (CDP), the Task Force on Climate-related Financial Disclosures (TCFD), the Sustainability Accounting Standards Board (SASB), and the International Sustainability Standards Board (ISSB) established by the IFRS Foundation.

[0033] For example, disclosure standards include the SSBJ standards developed by the SSBJ, the ESRS (European Sustainability Reporting Standards) developed by EFRAG, the Climate-related Disclosure Regulations developed by the SEC, the GHG Protocol developed by the GHG Protocol Initiative, the GRI standards developed by the GRI, the TCFD guidance developed by the TCFD, the SASB standards developed by the SASB, and the ISSB standards developed by the ISSB. In addition, the questionnaires prepared by the CDP can also be considered a type of disclosure standard.

[0034] The receiving organization 60 is an organization that receives financial and non-financial data from the user company 20 in accordance with disclosure standards. In addition to indicating the organization itself, the receiving organization 60 also indicates its employees, computers and computer systems used by the organization. The receiving organization 60 may also serve as the information provider 30. For example, the receiving organization 60 may be a CDP or EDINET. For convenience, auditors and audit firms that verify the validity of the financial and non-financial data of the user company 20 before disclosure are also included in the receiving organization 60.

[0035] Cloud services 70 are software and applications provided over the internet. Examples of cloud services 70 include SaaS (Software as a Service), PaaS (Platform as a Service), and IaaS (Infrastructure as a Service). Examples of cloud services 70 include cloud storage for data storage, customer relationship management systems, sales management systems, attendance management systems, accounting systems, and generative AI.

[0036] Information Site 80 is a website that collects information from User Companies 20 and makes that information widely available. Information Site 80 also includes websites, bulletin boards, and blogs operated by news organizations and PR (Public Solutions) companies. The difference between Information Site 80 and Information Providers 30 is that the information it publishes is a mix of reliable and unreliable sources.

[0037] Stakeholders 90 are defined as those stakeholders of User Company 20 who are interested in the information to be disclosed. Examples include shareholders of User Company 20 and institutional investors who have invested in or plan to invest in User Company 20. Local communities that have various influences on User Company 20's business activities are also considered stakeholders. Furthermore, employees of User Company 20 and companies with which User Company 20 has business relationships are also stakeholders.

[0038] Next, we will reiterate the involvement of the supply chain in the collection of non-financial data. As mentioned above, Scope 3 of GHG emissions refers to carbon dioxide emissions from corporate activities that are not included in Scope 1 direct emissions or Scope 2 indirect emissions. Therefore, user company 20, as a member of the supply chain, needs to receive non-financial data from upstream companies in the supply chain and pass on this non-financial data to downstream companies. If upstream and downstream companies use the sustainability ERP system 10 on a limited basis at the request of user company 20, without paying any usage fees, we will include upstream and downstream companies in user company 20.

[0039] Next, we will illustrate the hierarchical structure of corporate groups used in the explanations in this specification. Figure 2 is an explanatory diagram showing an example of a hierarchy of multiple companies. Figure 4 shows a group of companies with A (ESG Trading Co., Ltd.) at the top of the hierarchy. Hierarchy 1 represents the top company of the corporate group. The top company is a company called a holding company. A holding company is the core parent company of a group, established to control multiple corporate groups as a corporate group. It holds shares in each company for the purpose of controlling the corporate groups within the group.

[0040] Tier 2 represents companies directly below Tier 1. Tier 2 consists of two companies: B (Food Sales Co., Ltd.) and C (Industrial Resources Co., Ltd.). Tier 3 represents companies directly below Tier 2. D (ABC Ham) and E (AB Foods) are directly below B (Food Sales Co., Ltd.). F (ABC Metals), G, and H are directly below C (Industrial Resources Co., Ltd.). Tier 4 represents companies directly below Tier 3. I and J are directly below E (ABC Metals).

[0041] Figure 2 shows the hierarchical structure between companies, illustrating relationships such as holding companies, headquarters, subsidiaries, sub-subsidiaries, affiliates, and overseas offices. Note that the hierarchical structure in the Sustainability ERP System 10 may be a convenient structure for data collection and does not necessarily have to perfectly match the dominance relationships between companies, organizations, or groups. In the hierarchical structure, the group directly above a given group is called the parent group, and the group directly below a given group is called the child group.

[0042] Although not shown in Figure 2, the hierarchical structure may include the internal organizational structure of a company (headquarters, business divisions, departments, etc.). It may also show connections between any other organizations (associations, national and local governments, etc.).

[0043] Figure 3 is an explanatory diagram illustrating an example of an organizational hierarchy within a company. Figure 3 shows an example of the organizational hierarchy of ABC Ham. In Figure 2, ABC Ham was located at level 3, so this is followed here. Level 4 shows the head office, sales division, manufacturing division, etc. In organizational charts, there are notations that do not include the head office in level 3, but in this case, the head office is intentionally included in level 4. ABC Ham at level 3 represents the head office department that performs the function of aggregating and managing data collected from all over the company. The head office shown at level 4 is the department that collects data from various head office departments such as the general affairs department, human resources department, and accounting department. At level 5, under the sales division, the Hokkaido / Tohoku branch, Kanto branch, Tokyo sales office, etc., are shown. The Takasaki factory is shown under the manufacturing division.

[0044] Figure 4 is an explanatory diagram illustrating an example of a supply chain structure. It shows that ABC Ham procures raw materials and packaging materials for products such as ham from meat wholesalers, seasoning manufacturers, flavoring manufacturers, packaging material manufacturers, etc. It also shows that ABC Ham sells its products to food wholesalers and supermarket (market) chains. With a supply chain structured as shown in Figure 4, when ABC Ham collects data using the Sustainability ERP System 10, it needs to receive data from downstream companies such as meat wholesalers, seasoning manufacturers, flavoring manufacturers, and packaging material manufacturers. As mentioned above, when a downstream company accesses the Sustainability ERP System 10 and inputs its own data at the request of ABC Ham, the downstream company is considered a user company 20. Also, when an upstream company that requested data from ABC Ham accesses the Sustainability ERP System 10 and refers to ABC Ham's data, the upstream company is considered a user company 20.

[0045] Next, we will explain the procedures for data collection and disclosure using the Sustainability ERP System 10. Here, we assume a process in which non-financial data is entered at each location, the entered non-financial data is aggregated and processed to create a report, and the created report is disclosed. Figure 5 is a flowchart showing an example of the data collection and disclosure procedure. First, the overall administrator or administrator performs the initial setup (Step S1). The initial setup involves setting up the company and location, and creating and managing accounts such as those of data entry personnel. It also involves setting the items (data type, section, item, type, unit) of company and location information to be entered by data entry personnel. Furthermore, the approval flow is set up.

[0046] At each location, data entry personnel enter the data (Step S2). Once data entry is complete, the data entry personnel submit the data. Submission can be done on a per-data-type basis. When the data entry personnel submit the data, the data status changes from "input" to "submitted." The submitted data is reviewed by end-users with review authority (reviewers) and approved by end-users with approval authority (approvers) (Step S3). Reviewers and approvers may be the same person or different. Also, only reviewed data may be approved, or unreviewed data may also be approved. In this case, it is desirable to ensure the accuracy and validity of the data by setting restrictions such as not being able to finalize unreviewed data. If a reviewer or approver finds any deficiencies in the data content and prompts the data entry personnel to review it, they will send it back for review. When data is sent back, the data status temporarily changes to "returned" and then to "input," which allows the data entry personnel to input and correct the data. In the flowchart shown in Figure 5, this returns to Step S2.

[0047] Once the status of all data types is confirmed and approved, the data is finalized and the report is created (Step S4). The report to be created is a report such as an integrated report or a sustainability report. Securities reports, which include financial and non-financial data, are also included in the report. In addition to the content and format of the report to be unique to the user company20, it is desirable that reports conforming to multiple disclosure standards can also be created. Furthermore, a data format that is easy for computers to handle, such as XBRL, can be used for the report.

[0048] Finally, output the completed report (Step S5). Output includes displaying it on the screen, printing it out on paper, submitting it as a printed document to the receiving institution 60, or transmitting it electronically. Simply storing the completed report on a storage device such as a hard disk is also included in output.

[0049] Next, we will describe the database used by the Sustainability ERP System 10. Figure 6 is an explanatory diagram showing an example of a company database. The company database 121 stores information about companies. The company database 121 includes a company ID column, a name column, a hierarchy code column, and a memo column. The company ID column stores a company ID that can uniquely identify a company. The name column stores the name of the company. The hierarchy code column stores a hierarchy code that indicates the hierarchy in which the company is located. For example, the hierarchy code for ABC Ham is . is the company ID for ABC Ham. The slash ( / ) separates the hierarchy to the left, indicating the company one level up, Food Sales Co., Ltd. Further to the left of that, B indicates the company one level up, ESG Trading Co., Ltd. Since there is no code to the left of , it can be seen that ESG Trading Co., Ltd. is at the top level. In this way, by generating a hierarchy code for a company (group) at a certain level, placing the company ID of that company after the hierarchy code of its parent company (parent group), it is possible to generate an infinite number of hierarchies while maintaining the links between companies, excluding physical constraints, etc., and to represent the hierarchy of many companies in a unified manner. The memo column is used to store notes and other information about the company. Note that the hierarchy code is an example of a group ID.

[0050] Figure 7 is an explanatory diagram showing an example of a location database. Location DB122 stores information about locations. Locations are assumed to be branches, sales offices, or factories. Locations are organizations that have a large amount of information about the collected data. Location DB122 includes columns for Location ID, Hierarchy Code, Location Name, Country, Company ID, Business, Area, and Location Type. The Location ID column stores a location ID that can uniquely identify a location. The Hierarchy Code column stores a hierarchy code that indicates the location of the location in the hierarchical structure. The Location Name column stores the name of the location. The Country column stores the name of the country where the location is located. The Country column may also store the country code specified in ISO 3166-1. The Company ID column stores the company ID of the company to which the location belongs. The Business column stores the business type of the location, for example, a business office, a factory, etc. The Area column stores the region where the location is located. In the example shown in Figure 7, Tokyo is not included in the Kanto area, so the area of ​​the Tokyo sales office is Tokyo, not Kanto. The "Location Type" column stores the type of location, such as "directly under headquarters" or "outside headquarters."

[0051] Figure 8 is an explanatory diagram showing an example of an account database. Account DB123 stores account information and end-user information. Account DB123 includes columns for ID, display name, email address, company ID, and permissions. The ID column stores an ID that uniquely identifies the end-user. The display name column stores the account name, such as the end-user's job title or name. The email address column stores the end-user's email address. The company ID column stores the company ID of the company to which the end-user belongs. The permissions column stores the permissions granted to the end-user. For example, permissions may include "Global Management," "Management," "Approval," "Verification," and "Input Only." "Global Management" indicates the authority to manage accounts within a company group and manage the permission roles corresponding to each account. "Management" allows changes to accounts within a company group and changes to the permission roles corresponding to each account. "Management" does not allow adding accounts or permission roles. "Approval" allows approval of collected data. "Verification" allows verification of collected data. "Input Only" refers to an end-user account responsible only for inputting collected data, and the scope of input can be configured. The scope of authority is limited to the end-user's department and its subordinate departments. A range column may be added to account DB123 to explicitly store the scope of authority. For example, possible ranges include "including subsidiaries" and "company only." When combining multiple permissions, or when the scope of permissions does not match the organizational structure, permissions may be set individually. For example, the permission column may store the name of the individual permission, "Role 1." The Role DB (not shown) stores what permissions are granted to the permission named "Role 1."

[0052] Figure 9 is an explanatory diagram showing an example of an input status database. It stores the status of collected data entered at each location. Input Status DB124 includes columns for Location ID, Year, Month, Data Type, Status, and Last Operation Date. The Location ID column stores the location ID. The Year column stores the target year for the collected data. The Month column stores the target month for the collected data. The Data Type column stores the data type. A data type represents a group of multiple data items. The Status column stores the status of the collected data. Statuses include Input, Submitted, Under Review, Reviewed, Approved, etc. The Last Operation Date column stores the last date on which an operation was performed on the data type. Operations include Submission, Review, Approval, Return, etc.

[0053] Figure 10 is an explanatory diagram showing an example of an input database. Input DB 125 stores the collected data entered at each location. Input DB 125 includes columns for Location ID, Year, Month, Data Type, Section, Item, Type, Unit, and Value. The Location ID column stores the Location ID. The Year column stores the target year for the collected data. The Month column stores the target month for the collected data. The Data Type column stores the data type. The Section column stores data classifications below the Data Type. The Item column stores the name that represents the data. The Type column stores the type of the entered value. The Unit column stores the unit of the entered value. The Value column stores the entered value. Records in Input DB 125 are created when an administrator of each company group, or an end user with global management privileges as an account type, sets the data to be collected for each location. When a record is created, the Value column is set to empty.

[0054] Figure 11 is an explanatory diagram showing an example of an approval database. Approval DB 126 stores the approval tasks and approval history of collected data. An approval task for collected data refers to the business of approving the collected data. Approval DB 126 includes columns for location ID, year, month, data type, approval hierarchy, approver ID, approval date and time, and result. The location ID column stores the location ID of the location where the collected data to be approved or approved was entered. The year column stores the target year of the collected data. The month column stores the target month of the collected data. The data type column stores the data type of the collected data. The approval hierarchy column stores the hierarchy code of the hierarchy to be approved or the hierarchy to which approval was performed. The approver ID column stores the user ID of the end user who approved. The approval date and time column stores the date and time of approval. The result column stores the result. When an approver approves, the result column stores the approval. When an approver rejects the data, the result column stores the rejection. For records representing approval tasks, the values ​​in the Approver ID, Approval Date & Time, and Result columns will be blank or fixed values ​​indicating that the task is not approved (e.g., "None" in the example in Figure 11).

[0055] Figure 12 is an explanatory diagram showing an example of the Verification DB 127. The Verification DB 127 stores the verification history. The verification history is a record of whether the contents of the collected data entered at each location were correct. It includes columns for Location ID, Year, Month, Data Type, Verification Hierarchy, Verifier ID, and Verification Date and Time. The Location ID column stores the Location ID of the location where the verified collected data was entered. The Year column stores the target year of the collected data. The Month column stores the target month of the collected data. The Data Type column stores the data type of the collected data. The Verification Hierarchy column stores the hierarchy code of the hierarchy in which the verification was performed. The Verifier ID column stores the User ID of the end user who performed the verification. The Verification Date and Time column stores the date and time of the verification.

[0056] The databases described above are necessary when performing the collection and disclosure operations shown in Figure 5 using the Sustainability ERP System 10, but are not limited to these. For example, if a function implemented in the Sustainability ERP System 10 is removed, unnecessary databases may be created. Also, if the functions implemented in the Sustainability ERP System 10 are changed, the schema of the databases described above may need to be changed. Furthermore, adding functions to the Sustainability ERP System 10 may require new databases other than those described above.

[0057] While the traditional design involves placing the database physically on the server computers that constitute the Sustainability ERP System 10, it is clear that this is not the only option. The database may be distributed and stored across multiple database servers. The database may also be stored in cloud storage. In any case, as long as the database described above is appropriately available within the Sustainability ERP System 10, there are no special constraints regarding its physical placement.

[0058] There are several possible forms of database management privileges, depending on the database management policy. In the following explanation, the term "instance" is used, and in this specification, it refers to the following: An instance is an execution environment that integrates the physical and logical resources of a database and performs database operations. An instance provides a set of processes and resources for accessing and manipulating the data stored in the database. An instance manages access privileges to the database and user authentication. This prevents unauthorized access to and manipulation of data.

[0059] This specification describes three implementation forms of the Sustainability ERP System 10, focusing primarily on the nature of instances: the 2-Tier type, the Global Single Instance type, and the Flexible Global Single Instance type. Figure 13 is an explanatory diagram showing an example of the Sustainability ERP System 10's form. Figure 13 shows the 2-Tier type. In the 2-Tier type, the parent company (holding company) and its subsidiaries each build an ERP system with a database linked to a different instance. Each database is independent, and the database used by the subsidiary is managed and operated by the subsidiary. The parent company is not permitted to freely access the subsidiary's database, and access or data transmission is limited to the extent permitted by mutual agreement. From the perspective of data collection, the parent company prepares a company-wide global template and distributes it to the subsidiaries. Subsidiaries create their own customized templates by adding content for the data they collect to the global template. Since the global template corresponds to the data that the parent company should collect from the subsidiaries, subsidiaries are not permitted to change the content of the global template. Subsidiaries deploy their own templates internally. The subsidiary stores and utilizes the collected data in its own database, and transmits data collected according to a global template to the parent company.

[0060] The advantages of adopting a 2-Tier model are as follows: Subsidiaries can manage the databases they use themselves and customize the templates for collected data, enabling the construction and deployment of highly scalable systems. Furthermore, since the uniqueness of the subsidiary is reflected in the system's form, it is expected to reduce resistance from business personnel and overseas subsidiaries with differing values ​​when the parent company collects various data from the subsidiary via the Sustainability ERP System 10.

[0061] The disadvantages of adopting a 2-Tier model are as follows: The parent company needs to collect data from databases managed by each subsidiary, which increases the processing load for data collection in the parent company's ERP system. In addition, since each subsidiary manages its own database and collects data using its own templates, the sustainability ERP system as a whole will have multiple master data and applications, which is expected to increase management and maintenance costs. Ultimately, a 2-Tier sustainability ERP system is equivalent to operating and maintaining multiple information infrastructures across the entire corporate group, and is therefore considered to have little economies of scale.

[0062] Figure 14 is an explanatory diagram showing another example of the Sustainability ERP System 10. Figure 14 shows the Global Single Instance type. In the Global Single Instance type, the parent company and its subsidiaries access the database using a single common instance. In the Global Single Instance type, the content and format of the collected data are defined by company-wide global requirements (global template) established by the parent company. The parent company also operates and manages the database with a common schema and stores the data collected from multiple subsidiaries in that database. Note that the database may contain multiple tables.

[0063] The advantages of adopting a Global Single Instance (GST) architecture are as follows: Since the entire company uses a database with a common schema, operation and management of data in a single format and a single application are handled, reducing the effort required for operation and management. Because a single information infrastructure is operated and maintained, costs are relatively lower.

[0064] The disadvantages of adopting a Global Single Instance model are as follows: Since the parent company is involved in all aspects of data management and operation, significant resistance is expected from business personnel and overseas subsidiaries with differing values. When the Sustainability ERP System 10 is shut down, it is difficult to partially limit the impact on end users. Therefore, even for maintenance purposes, the number of downtimes must be small and the duration short, making stable operation and the necessary maintenance work difficult. As a system configuration, while the parent company can strengthen governance over its subsidiaries, it is necessary to ensure sufficient independence between companies in terms of technology and operation to prevent excessive interference from the parent company or unnecessary data access between subsidiaries.

[0065] Figure 15 is an explanatory diagram showing other examples of the Sustainability ERP System 10. Figure 15 shows the Flexible Global Single Instance type. The Flexible Global Single Instance type is an extension of the Global Single Instance type. The parent company and subsidiaries use one instance, but it is possible to create a data area in the database that is accessible only to each subsidiary. In terms of data collection, similar to the 2-Tier type, a company-wide global template prepared by the parent company is customized and deployed by the subsidiary. Among the collected data, the subsidiary writes the data collected according to the global template to an area that is also accessible to the parent company. Among the collected data, data collected independently by the subsidiary is stored in a database area accessible only to the subsidiary (hereinafter also referred to as the "proprietary area").

[0066] The advantages of adopting the Flexible Global Single Instance model are as follows: Similar to the Global Single Instance model, the entire company uses a database with a common schema, resulting in a single data format and a single application for operation and management, thus reducing the man-hours required for operation and management. Since a single information infrastructure is operated and maintained, costs are relatively lower. Also, unlike the Global Single Instance model, subsidiaries can store data they collect independently in their own areas, so it is expected that there will be less resistance from overseas subsidiaries with different business personnel and values.

[0067] The disadvantages of adopting the Flexible Global Single Instance type are as follows: Similar to the Global Single Instance type, the number of downtime instances and the duration of downtime must be kept to a minimum, making stable operation and the necessary maintenance work difficult. Since the parent company and subsidiary use a single instance, the parent company's system administrator can change the access rights to the subsidiary's private area, allowing the parent company to access it. While parent company access to the subsidiary's private area contributes to strengthening the parent company's governance, it may undermine the subsidiary's independence. Therefore, changes to access rights should not be permitted in principle and should only be applied in the event of a predetermined emergency.

[0068] Of the three implementation forms of the Sustainability ERP System 10 described above, the choice of which type to select should be determined by the user company 20's specific needs and requirements. This concludes our overview of the Sustainability ERP System 10, which helps user companies 20 to conduct sustainable business practices. Next, we will provide a more detailed explanation of the Sustainability ERP System 10.

[0069] First, let's describe the server 1 and terminal 2, which are components of the sustainability ERP system 10. Server 1 uses the database mentioned above to perform information processing to realize the functions provided by the sustainability ERP system 10. It then transmits the information to terminal 2. Server 1 can consist of a server computer, workstation, PC (Personal Computer), etc. Alternatively, Server 1 may be configured as a multicomputer consisting of multiple computers, a virtual machine virtually constructed by software, or a quantum computer. The functions performed by Server 1 may be distributed among multiple computers. Furthermore, the functions of Server 1 may be implemented as a cloud service.

[0070] Figure 16 is a block diagram showing an example of the hardware configuration of Server 1. Server 1 includes a control unit 11, a storage unit 12, a communication unit 13, and a read unit 14. Each component is connected by bus B.

[0071] The control unit 11 has one or more arithmetic processing units such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit). The control unit 11 reads and executes a program 1P (program product) stored in the storage unit 12, thereby performing various information processing, control processing, etc. related to the server 1 and realizing various functional units.

[0072] The storage unit 12 is composed of SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), flash memory, or a hard disk or SSD (Solid State Drive). The storage unit 12 temporarily stores the data necessary for the control unit 11 to perform calculations. The storage unit 12 also stores the program 1P necessary for the control unit 11 to perform the processing. Some or all of the above-mentioned DB may be stored in the storage unit 12.

[0073] The communication unit 13 communicates with terminal 2 via network N. Alternatively, the control unit 11 may use the communication unit 13 to download program 1P from another computer via network N or the like and store it in the storage unit 12.

[0074] The reading unit 14 reads a portable storage medium 1a, including CD (Compact Disc)-ROM and DVD (Digital Versatile Disc)-ROM. The control unit 11 may read program 1P from the portable storage medium 1a via the reading unit 14 and store it in the storage unit 12. Alternatively, the control unit 11 may download program 1P from another computer via a network N or the like and store it in the storage unit 12. Furthermore, the control unit 11 may read program 1P from a semiconductor memory (not shown).

[0075] Terminal 2 is a terminal used by end users. End users are employees or staff of corporations, organizations, etc. Depending on their role and authority, end users may be referred to as inputters, approvers, verifiers, etc.

[0076] Figure 17 is a block diagram showing the hardware configuration of a terminal. Terminal 2 consists of a notebook computer, panel computer, tablet computer, smartphone, etc. Terminal 2 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, and a display unit 25. Each component is connected by bus B.

[0077] The control unit 21 has one or more arithmetic processing units such as CPUs, MPUs, and GPUs. The control unit 21 provides various functions by reading and executing programs 2P (program products) stored in the storage unit 22.

[0078] The storage unit 22 is composed of SRAM, DRAM, flash memory, or a hard disk or SSD. The storage unit 22 temporarily stores data necessary for the control unit 21 to perform calculations. The storage unit 22 also stores the program 2P and various databases necessary for the control unit 21 to perform processing. The various databases stored in the storage unit 22 may be stored in a database server or cloud storage.

[0079] The communication unit 23 communicates with the server 1 via the network N. Alternatively, the control unit 21 may use the communication unit 23 to download program 2P from another computer via the network N or the like and store it in the storage unit 22.

[0080] The input unit 24 is a keyboard or mouse. The display unit 25 includes a liquid crystal display panel or an organic EL display panel, etc. The display unit 25 displays reports output by the server 1. Alternatively, the input unit 24 and the display unit 25 may be integrated to form a touch panel display. The terminal 2 may also display information on an external display device.

[0081] (Gathering information from suppliers) In recent years, reducing the environmental impact of business activities has become increasingly important. In particular, there is a growing need to evaluate and reduce greenhouse gas emissions across the entire supply chain. In this context, Scope 3 emissions, CFP (carbon footprint), and LCA (life cycle assessment) have become important indicators and methods for companies to understand the environmental impact of their entire supply chain and to achieve reduction targets. Furthermore, in order to advance these efforts, technology is needed to systematically exchange detailed information about products and services traded between companies (hereinafter collectively referred to as "products"), especially information about the environmental and social impacts of those products. Here, information sharing is required not only between the company receiving the product (hereinafter referred to as "our company" or "buyer") and the company providing the product (hereinafter referred to as "supplier"), but also "related companies" such as our own group companies, client companies, and logistics companies. A buyer is an example of a business operator. A supplier is an example of another business operator.

[0082] To accurately calculate Scope 3 emissions, detailed data on emissions from manufacturing processes and raw material procurement from suppliers throughout the supply chain is necessary. This data is particularly essential for calculating the Cost of Performance (CFP), which assesses GHG emissions across the entire lifecycle of a product or service. Life Cycle Assessment (LCA) is a method for comprehensively evaluating the environmental impact across the entire lifecycle of a product or service, including the supply chain, and can capture not only GHG emissions but also energy consumption and resource consumption. To enhance the reliability of LCA, data collection from the entire supply chain is essential, and the quality of data provided by suppliers significantly impacts the accuracy of the evaluation results.

[0083] Therefore, buyers collecting environmental impact data from suppliers in their supply chains plays a crucial role in improving Scope 3 emissions calculations, ensuring the reliability of CFPs, and reducing environmental impacts through LCAs. Furthermore, this initiative can serve as a vital foundation for companies aiming for sustainable management, responding to legal regulations and customer environmental awareness.

[0084] Incidentally, buyers typically deal with multiple suppliers. The products offered by each supplier are generally different and not uniform. Furthermore, it is not currently common for suppliers to disclose GHG emissions for each product. Therefore, the procedure involves the buyer requesting information, and the supplier responding. The buyer extracts the parts they purchase from the bill of materials included in their products. The buyer then requests each of the extracted parts from the manufacturer's supplier.

[0085] GHG emissions are calculated periodically, for example, annually. However, the GHG emissions for all products from suppliers that a buyer purchases as parts do not necessarily change every time (annually). Given this premise, requesting suppliers to perform Scope 3 calculations each time the buyer performs them would place an excessive burden on both the buyer and the suppliers. The following describes an information processing method for calculating product GHG emissions without repeatedly requesting suppliers to perform the calculations.

[0086] (Embodiment 1) First, let's look at an example of a product used in this explanation. The example product is an LCD monitor (hereinafter simply referred to as "monitor") used in connection with a personal computer. Figure 18 is an explanatory diagram showing the bill of materials (BOM) of a monitor in a tree structure. Figure 18 shows the M-BOM (Manufacturing BOM), which includes the manufacturing process, in a tree structure, along with the bill of materials (BOM). A monitor consists of components such as an LCD panel and a backlight. The manufacturing process includes assembling modules from multiple components, inspecting the assembled modules, and final assembly, where the final product, the monitor, is assembled from the modules and components.

[0087] A backlight consists of components such as LED chips, LED substrates, reflector sheets, and light guide plates. The manufacturing process involves assembling modules from multiple components, inspecting the assembled modules, and the final assembly of the backlight from the modules and components.

[0088] For the reflector sheets, which are components of the backlight, there is a sheet molding process that involves cutting the reflector sheets that are wound on a roll. In addition, the light guide plates undergo adjustment processing to adjust their size.

[0089] Figure 19 is an explanatory diagram showing the parts list for a reflector sheet in a tree structure. The parts list shown in Figure 19 is an extended R-BOM (Raw Material BOM) that adds the manufacturing process to the R-BOM (Raw Material BOM) which shows the raw materials, and is shown in a tree structure. Since Figure 19 does not describe each manufacturing process in detail, it is called an extended R-BOM and not an M-BOM (Manufacturing BOM). The main raw materials for the reflector sheet are PET resin, barium titanate, and acrylic adhesive.

[0090] The general manufacturing process is as follows: PET resin is extruded to create a PET film. A reflective material such as barium titanate is coated onto the created PET film. Furthermore, an acrylic adhesive is uniformly applied to form an adhesive layer for attachment to light guide plates and other components. Quality checks are then performed.

[0091] As described above, by referring to various BOMs, it is possible to understand the materials, processing, parts, and processes required to assemble one monitor. In other words, by using the information shown in the various BOMs, it is possible to calculate the amount of GHG emissions when assembling one monitor.

[0092] Next, we will explain the database used to collect information from suppliers. The database described below is stored, for example, in the storage unit 12 of server 1. Figure 20 is an explanatory diagram showing an example of a bill of materials. The bill of materials is managed as a database, and each user (each company) can refer to the parts information of their own products. Figure 20 illustrates the case where the product is a PC monitor. The bill of materials 128 includes columns for part ID, part name, procurement category, and supplier. The part ID column stores the part ID that identifies the part. The part name column stores the name of the part. The procurement category column stores the procurement category of the part. P indicates that it is procured from another company. M indicates that it is procured from our own company. Procurement from parent companies, subsidiaries, affiliates, and group companies is marked as "another company". However, if part information such as part specifications and GHG emissions is shared and GHG emissions can be read as needed, the supplier may be marked as "our own company". The supplier column stores the supplier of the part. In this context, suppliers are assumed to be companies or organizations that have or can provide information on components, such as their GHG emissions.

[0093] Figure 21 is an explanatory diagram showing an example of a product calculation database. Product calculation database 129 stores the calculation results of GHG emissions for all components that make up the product. Product calculation database 129 includes columns for component ID, component name, quantity, emissions, total emissions, and calculation period. The component ID column stores the component ID. The component name column stores the component name. The quantity column stores the number of components required for the product. The emissions column stores the GHG emissions for one component. The unit is kg-CO2e. The total emissions column is the GHG emissions multiplied by the number of components. The unit is kg-CO2e. The calculation period column stores the time when the GHG emissions for each component were calculated. In this specification, assuming that calculations are performed annually, the calculation period column stores the year in which the calculation was performed. It is desirable that the GHG emissions of a product include emissions from manufacturing processes such as the assembly process and inspection process, in addition to the emissions for each component shown in Figure 21.

[0094] Figure 22 is an explanatory diagram showing an example of a parts calculation value database. Parts calculation value DB12A stores the calculation results of GHG emissions for parts. Figure 22 shows an example of a backlight, which is a part of a PC monitor. Hereinafter, when a part is viewed as a product, the part will be called a child part, and the part composed of child parts will be called a parent part. Parts calculation value DB12A includes columns for ID, type, name, material / specification, quantity, emissions, and calculation time. The ID column stores the ID that identifies the child part that makes up the parent part, or the ID that identifies the manufacturing process of the parent part. The type column stores the type of information (record type) that each record stores. If the record stores information about a part, the type column stores the part. If the record stores information about a process, the type column stores the process. The name column stores the part name or process name. If the record type is a part, the material / specification column stores the material and specifications of the child part. If the record type is a process, the material / specification column does not need to store any information. The Quantity column stores the number of child parts required for a parent part if the record type is a part. The Quantity column stores the number of executions if the record type is a process. The Emissions column stores the GHG emissions of the child part or process. The Calculation Time column stores the time when the GHG emissions for the child part or process were calculated. Although not shown in Figure 22, similar to the Product Calculation Value DB129, the Part Calculation Value DB12A may also include a column to store the total emissions for each child part or process.

[0095] Figure 23 is an explanatory diagram showing an example of a processing calculation value DB. Processing calculation value DB12B stores the calculation results of GHG emissions during the processing of parts. Processing calculation value DB12B includes columns for processing ID, processing name, part ID, quantity, emissions, and calculation time. The processing ID column stores a processing ID that identifies the processing process. The processing name column stores the name of the processing process. The part ID column stores the part ID of the part being processed. The quantity column stores the number of times the processing is performed. The emissions column stores the GHG emissions of the processing process. The calculation time column stores the time when the GHG emissions for the process were calculated. Although not shown in Figure 23, processing calculation value DB12B may also include a column to store the total emissions for each process, similar to product calculation value DB129.

[0096] Figure 24 is an explanatory diagram showing an example of a material calculation value database. The material calculation value database 12C stores the GHG emissions for each material used in the manufacture of parts. The material calculation value database 12C includes a material ID column, an item column, a weight per unit column, an emissions per gram column, an emissions column, and a calculation time column. The material ID column stores a material ID that identifies the material. The item column stores the name of the material, etc. The weight per unit column stores the weight of each material required per part. The emissions per gram column stores the emissions per gram of material. The emissions column stores the total emissions for each material. The total emissions are obtained by multiplying the value in the weight per unit column by the value in the emissions per gram column. The calculation time column stores the time when the GHG emissions for the material were calculated. In Figure 24, the emissions of materials are calculated using weight, but this is not the only method. Other quantities, such as volume, may also be used.

[0097] Figure 25 is an explanatory diagram showing an example of a material processing calculation database (DB12D). The material processing calculation database (DB12D) stores the calculation results of GHG emissions during the processing steps for a material. The material processing calculation database (DB12D) includes columns for processing ID, processing name, material ID, quantity, emissions, and calculation time. The processing ID column stores a processing ID that identifies the processing step. The processing name column stores the name of the processing step. The material ID column stores the material ID of the material being processed. The quantity column stores the number of times the processing is performed. The emissions column stores the GHG emissions for the processing step. The calculation time column stores the time when the GHG emissions for the step were calculated. Although not shown in Figure 25, similar to the product calculation database (DB129), the material processing calculation database (DB12D) may also include a column to store the total emissions for each step. Furthermore, since the material processing calculation value DB12D is similar to the processing calculation value DB12B in that it is a database that stores the amount of waste generated during processing, the two databases may be integrated.

[0098] Next, we will explain the process for calculating the GHG emissions of a product. Here, we assume that an end-user of a manufacturer that produces the final product uses the sustainability ERP system 10 to calculate the GHG emissions of the product. Figures 26 and 27 are flowcharts illustrating example procedures for the calculation process. The end-user uses terminal 2 to specify the product for which the GHG emissions are to be calculated. The control unit 21 of terminal 2 obtains the product ID of the specified product (step S11). The control unit 21 sends the product ID to server 1 (calculation device) (step S12). The control unit 11 of server 1 receives the product ID (step S13). The control unit 11 searches the bill of materials database using the product ID as a search key and obtains the bill of materials for the product (step S14). The bill of materials database is stored in a PLM (Product Lifecycle Management) system or ERP system, which is not shown in the diagram. The bill of materials to be obtained is selected from multiple BOMs, such as E-BOM, M-BOM, S-BOM, and P-BOM, as needed. The control unit 11 selects the parts to be processed from the bill of materials (step S15). The control unit 11 checks whether the emission data for the selected parts is stored in the parts calculation value DB12A (step S16). The control unit 11 stores the result of the check (step S17). If the emission data is stored in the parts calculation value DB12A, the control unit 11 retrieves the emission data and stores it in the temporary storage area. If the emission data is not stored in the parts calculation value DB12A, the control unit 11 stores the parts ID in the temporary storage area. The temporary storage area is provided, for example, in the storage unit 12 of the server 1. The control unit 11 also stores the emission data and the parts ID in a way that allows them to be distinguished. The control unit 11 determines whether there are any parts that have not been processed (step S18). If the control unit 11 determines that there are parts that have not been processed (YES in step S18), it returns to step S15 and processes the unprocessed parts. If the control unit 11 determines that there are no parts that have not been processed (NO in step S18), it determines whether or not a request to the supplier is necessary (step S19). The control unit 11 refers to the temporary storage area and determines that a request is necessary if the part ID of a part for which emission data has not been obtained is stored there.If the part ID is not stored in the temporary storage area, it is determined that no request is necessary. If the control unit 11 determines that no request is necessary to the supplier (NO in step S19), it calculates the GHG emissions of the product (step S20). If the control unit 11 determines that a request is necessary to the supplier (YES in step S21), it executes the request process (step S21). The details of the request process will be described later. The control unit 11 creates a screen and sends it to terminal 2 (step S22). If the control unit 11 has calculated the GHG emissions, it creates a screen showing the calculation result. If the control unit 11 has executed the request process, it creates a screen indicating that the request has been completed. The control unit 21 of terminal 2 receives and displays the screen. The control unit 21 terminates the process.

[0099] Figure 27 is a flowchart showing an example of the request processing procedure. The request processing corresponds to step S21 in Figure 26. The control unit 11 selects a part (step S41). The control unit 11 obtains the part ID of the part for which GHG emissions have not been obtained and is stored in the temporary storage area. The control unit 11 determines whether the selected part is a purchased part or not (step S42). If the procurement classification of the part is P, the control unit 11 determines that it is a purchased part. If the procurement classification of the part is M, the control unit 11 determines that it is not a purchased part. If the control unit 11 determines that the part is a purchased part (YES in step S42), it obtains the supplier information (step S43). The control unit 11 temporarily stores the supplier information in association with the part ID (step S44). If the control unit 11 determines that the part is not a purchased part (NO in step S42), it obtains the GHG emissions (step S45). Regarding parts procured from within the company, it is assumed that even if they are not stored in the parts calculation value DB12A, they can be obtained from a database accessible by Server 1. Alternatively, Control Unit 11 may send an input screen to Terminal 2, allowing the end user to input and obtain the GHG emissions. Control Unit 11 temporarily stores the GHG emissions (Step S44). Control Unit 11 determines whether or not there are any parts that have not been processed (Step S46). If Control Unit 11 determines that there are parts that have not been processed (YES in Step S46), it returns to Step S41 and processes the unprocessed parts. If Control Unit 11 determines that there are no parts that have not been processed (NO in Step S46), it creates a request setting screen and sends it to Terminal 2 (Step S47). For example, the request setting screen displays a list of parts requiring a request, including part ID, name, supplier name, contact person name, and email address. Control Unit 21 on Terminal 2 receives and displays the screen (Step S48). The end user checks the displayed content and inputs any missing data or corrects the data. The end user instructs the system to execute the request. The control unit 21 receives the instruction (step S49). The control unit 21 sends the request execution instruction to the server 1 (step S50). The control unit 11 of the server 1 receives the request execution instruction (step S51). The control unit 11 sends the request to the supplier (step S52). For example, the request is sent via email.The email will contain instructions on how to access the sustainability ERP system 10. When a supplier is issued an account to input GHG emissions, the control unit 11 issues the account and sends the user ID in an email. The control unit 11 returns the process to the caller. The control unit 11 executes steps S22 onwards in Figure 26.

[0100] Figure 28 is an explanatory diagram showing an example of a request setting screen. The request setting screen d01 includes a list table d011, an OK button d012, and a Cancel button d013. The list table d011 shows the parts that require a request to be sent to the supplier. The list table d011 includes columns for Part ID, Part Name, Supplier, Contact Person, Email, and Settings. The Part ID column shows the part ID. The Part Name column shows the part name. The Supplier column shows the supplier's name. The Contact Person column shows the supplier's contact person. The Email column shows the supplier's contact email address. Selecting a cell in the Settings column displays a pop-up screen for setting the items to be requested from the supplier. Selecting the OK button d012 sends the request to the supplier via Server 1. Selecting the Cancel button d013 does not send the request, and the request setting screen d01 closes, or returns to the home screen or menu screen.

[0101] This embodiment has the following effect: When a buyer calculates GHG emissions, if they have already received GHG emission data from a supplier (previously), the buyer can calculate the GHG emissions without having to request the supplier to provide the data again. This prevents an excessive burden on the supplier.

[0102] (Embodiment 2) This embodiment relates to a method of inquiring with suppliers about any changes in their GHG emissions. In Embodiment 1, it was assumed that the GHG emissions of the parts supplied by the supplier would not change each time the buyer calculated their GHG emissions. However, suppliers may also reduce the GHG emissions of their parts by taking steps to reduce their own emissions. Therefore, in this embodiment, the buyer only inquires with the supplier about any changes in their GHG emissions. If the supplier responds that there have been changes, the buyer requests the latest calculation results for their GHG emissions.

[0103] Figure 29 is a flowchart showing an example of the confirmation process. The buyer user specifies the target product from the product list displayed on terminal 2. The control unit 21 of terminal 2 obtains the product ID of the specified product (step S61). The control unit 21 sends the product ID to server 1 (step S62). The control unit 11 of server 1 receives the product ID (step S63). The control unit 11 searches the bill of materials database using the product ID as a search key and obtains the bill of materials for the product (step S64). The control unit 11 selects the part to be processed from the bill of materials (step S65). The control unit 11 determines whether the selected part is a purchased part or not (step S66). The determination method is the same as in step S42 described above. If the control unit 11 determines that the part is a purchased part (YES in step S66), it temporarily stores the part ID (step S67). If the control unit 11 determines that the part is not a purchased part (NO in step S66), it proceeds to step S68. The control unit 11 determines whether there are any unprocessed parts (step S68). If the control unit 11 determines that there are unprocessed parts (YES in step S68), it returns to step S65 and processes the unprocessed parts. If the control unit 11 determines that there are no unprocessed parts (NO in step S68), it sends an inquiry to the supplier (step S69). The control unit 11 retrieves the part ID stored in the temporary storage area. The control unit 11 retrieves supplier information using the part ID. The control unit 11 creates an inquiry message for each supplier and sends an email to the supplier's contact person. It is desirable to include a response deadline in the inquiry message (confirmation message). The control unit 11 creates a screen indicating that an inquiry has been made and sends it to terminal 2 (step S70). The control unit 21 of terminal 2 receives and displays the screen (step S71). The control unit 21 terminates processing.

[0104] Figure 30 is a flowchart illustrating an example of the response processing procedure. Response processing is the process performed when a supplier's representative receives an email inquiring whether or not there have been any changes in emissions and responds to the inquiry. For example, the email includes response options such as "no changes" or "changes." Each option has a hyperlink, and the representative selects one of the options by clicking the mouse or similar. Once the representative makes a selection, the control unit 21 of the terminal 2 used by that representative sends the response to the server 1 (step S81). The control unit 11 of the server 1 receives the response (step S82). The control unit 11 determines whether the response is "changes" or not (step S83). If the control unit 11 determines that there are "changes" (YES in step S83), it sends a screen to terminal 2 for inputting the changed emissions (step S84). The control unit 21 of terminal 2 receives and displays the screen (step S85). The representative inputs the changed values ​​according to the screen (step S86). The screen may consist of multiple parts. The control unit 21 acquires the input value (step S86). The control unit 21 sends the input value to the server 1 (step S87). The control unit 11 of the server 1 receives the value (step S88). The control unit 11 stores the received value in the corresponding calculation value database, such as the parts calculation value DB 12A (step S89). The control unit 11 also updates the calculation time. If the control unit 11 determines that there is "no change" (NO in step S83), it stores that there was no change (step S90). It also updates the calculation time in the corresponding calculation value database, such as the parts calculation value DB 12A. The control unit 11 terminates processing.

[0105] Figure 31 is a flowchart illustrating another example of the calculation process. After the buyer user completes the confirmation process, they start the calculation process from terminal 2 once all the supplier responses have been received. The user specifies the target product on terminal 2. The control unit 21 of terminal 2 obtains the product ID of the specified product (step S101). The control unit 21 sends the product ID to server 1 (step S102). The control unit 11 of server 1 receives the product ID (step S103). The control unit 11 searches the bill of materials database using the product ID as a search key and obtains the bill of materials for the product (step S104). The control unit 11 determines whether or not responses from the contacted suppliers have been collected (step S105). If the control unit 11 determines that responses from the suppliers have been collected (YES in step S105), it calculates the emissions (step S106). The control unit 11 creates a screen showing the calculation results and sends it to terminal 2 (step S107). If the control unit 11 determines that a response from the supplier has not yet been collected (NO in step S105), it creates a screen indicating that the calculation cannot be performed yet and sends it to terminal 2 (step S107). The control unit 21 of terminal 2 receives and displays the screen (step S108). The control unit 21 then terminates the process.

[0106] This embodiment offers the following advantages: By inquiring with suppliers each time about whether or not there has been a change in GHG emissions, buyers can accurately incorporate changes in the emissions of goods procured from suppliers. In other words, if GHG emissions decrease due to the supplier's efforts, buyers can reflect this in the calculation of their own products. Furthermore, suppliers whose GHG emissions have not changed only need to respond accordingly, thus reducing the burden on supplier personnel.

[0107] (modified version) This modified version is a modified form of Embodiment 2. In Embodiment 2, suppliers whose GHG emissions have not changed only need to respond to that effect, but even such a task may be burdensome for suppliers. For example, if a supplier is making efforts to reduce GHG emissions but has adopted measures that will take several years to show results, it may cause psychological burden on the person in charge. Also, for suppliers who receive inquiries from multiple buyers every year, even just responding that there has been no change is not a light burden. In this modified version, for a predetermined period, as in Embodiment 1, the buyer performs the calculation without contacting the supplier, and after the predetermined period has elapsed, they contact the supplier as in Embodiment 2. For example, the predetermined period is 3 years.

[0108] Figure 32 is a flowchart showing another example of the verification process. The verification process in this modified example is a variation of the process shown in Figure 29. Some steps common to Figure 29 are omitted in Figure 32. Steps common to Figure 29 in Figure 32 are given the same step numbers as in Figure 29. The buyer user specifies the target product from the product list displayed on terminal 2. This triggers the verification process. Steps S61 to S64 shown in Figure 29 are executed. After executing step S64, the control unit 11 of server 1 selects the part to be processed from the bill of materials (step S65). The control unit 11 determines whether the selected part is a purchased part or not (step S66). If the control unit 11 determines that the part is not a purchased part (NO in step S66), the process proceeds to step S68. If the control unit 11 determines that the part is a purchased part (YES in step S66), it determines whether a predetermined period has elapsed since the last inquiry to the supplier (step S121). It is assumed that the predetermined period is set in advance by the buyer. The control unit 11 calculates the elapsed period based on the calculation time of the calculated value DB and the current date and time at the time of processing execution. The control unit 11 determines whether the elapsed period exceeds the predetermined period. If the control unit 11 determines that the predetermined period has not elapsed (NO in step S121), it proceeds to step S68. If the control unit 11 determines that the predetermined period has elapsed (YES in step S121), it temporarily stores the part ID (step S67). The control unit 11 determines whether there are any parts that have not been processed (step S68). If the control unit 11 determines that there are parts that have not been processed (YES in step S68), it returns to step S65 and processes the unprocessed parts. If the control unit 11 determines that there are no parts that have not been processed (NO in step S68), it executes steps S69 onwards in Figure 29.

[0109] This modified version has the following effect: By setting the predetermined period to an appropriate length, it becomes possible to ensure the accuracy of calculations by buyers while reducing the burden on suppliers.

[0110] While the above assumes that the specified period is uniform, this is not the only option. It may be set individually for each buyer. Alternatively, buyers may set the period individually for each supplier at their discretion.

[0111] Figure 33 is an explanatory diagram showing an example of an inquiry screen. Inquiry screen d02 is the screen displayed on terminal 2 used by the supplier in Embodiment 2. Inquiry screen d02 includes the recipient name d021, target product d022, response time d023, a "no change" button d024, and a "change" button d025. The recipient name d021 displays the supplier's name, the supplier's contact person's name, etc. The target product d022 displays the target product. The response time d023 displays the time when the supplier last responded with GHG emissions. If there is no change in GHG emissions, the contact person selects the "no change" button d024. When the "no change" button d024 is selected, a response indicating that there is no change is sent from terminal 2 to server 1. If there is a change in GHG emissions, the contact person selects the "change" button d025. When the "change" button d024 is selected, a response indicating that there is a change is sent from terminal 2 to server 1.

[0112] Figure 34 is an explanatory diagram showing an example of a transmission completion screen. The transmission completion screen d03 is the screen displayed on terminal 2 used by the buyer in Embodiment 2 - Modified Example. The transmission completion screen d03 includes an explanatory text d031, an external procurement parts list d032, and a close button d033. The explanatory text d031 is an explanation of the "Inquiry" column in the external procurement parts list d032. The external procurement parts list d032 is a list of parts purchased from suppliers. The external procurement parts list d032 includes a part ID column, a part name column, a previous response column, a supplier column, and an inquiry column. The part ID column shows the part ID. The part name column shows the name of the part. The previous response column shows the time when the previous inquiry was made and a response was received from the supplier. The supplier column shows the name of the supplier. The inquiry column shows whether or not an inquiry was made this time. "Not required" indicates that a predetermined period, for example 2 years, has not passed since the previous response, so it has been determined that the inquiry is not required. "Sent" indicates that the inquiry has been sent. Pressing the close button d033 will close the transmission completion screen d03.

[0113] In Embodiment 2 and its modified form, a screen similar to the request setting screen shown in Figure 28 may be displayed before sending an inquiry to the supplier. This screen displays whether or not an inquiry to the supplier is necessary for each part. On this screen, the buyer's representative may be able to change whether or not an inquiry is necessary. The buyer's representative can make an inquiry if they deem it necessary, even if a predetermined period has not elapsed since the last response. Conversely, even if a predetermined period has elapsed, they can omit the inquiry if they deem it unnecessary.

[0114] GHG emissions are calculated by multiplying activity level by emission factor. When buyers recalculate their own products, they tend to treat the GHG emissions for parts (the emission factor for the buyer) as unchanged if there have been no specification changes such as changes in parts since the previous calculation. However, even if the activity level does not change, GHG emissions will change if the emission factor changes. For example, this can happen if there are changes in the secondary data that the emission factor used is referenced from. Therefore, the latest emission factor should be used when calculating. Thus, there is value in focusing on the emission factor as in this case.

[0115] Similarly, in calculating the GHG emissions of a supplier's own products (parts from the buyer's perspective), even if there are no changes to the product specifications, fluctuations in GHG emissions due to updates to emission factors are possible.

[0116] Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various modifications or improvements can be made to the above embodiments. It will be clear from the claims that such modified or improved forms may also be included in the technical scope of the present invention.

[0117] It should be noted that the execution order of operations, procedures, steps, and stages in the apparatus, systems, programs, and methods shown in the claims, specifications, and drawings is not explicitly stated as "before," "prior to," etc., and that these can be implemented in any order unless the output of a previous process is used in a later process. Even if the operation flow in the claims, specifications, and drawings is described using phrases such as "first," "next," etc. for convenience, it does not mean that it is essential to perform the operations in that order.

[0118] Furthermore, aspects of each embodiment can be embodied in whole or in part by a computer. For example, a program installed on such a computer may cause the computer to function as an operation associated with an apparatus according to an embodiment of the present invention, or as one or more "parts" of such apparatus. Alternatively, the program may cause the computer to execute such operation or one or more "parts." The program may cause the computer to execute a process or a stage of such process according to an embodiment of the present invention. Such a program may be executed by the CPU to cause the computer to execute a particular operation associated with some or all of the blocks in the flowcharts and block diagrams described herein. [Explanation of symbols]

[0119] 100: Information Systems 10: Sustainability ERP System 20: User companies 30: Information Providers 40: Integration System 50: Formulation body 60: Receiving Institution 70: Cloud Services 80: Information site 90: Stakeholders 1: Server 11: Control Unit 12: Storage section 121: Corporate DB 122: Branch Database 123: Account DB 124: Input Status DB 125: Input DB 126: Approval DB 127: Confirmation DB 128: Bill of Materials 129: Product calculation value DB 12A: Parts calculation value DB 12B: Machining calculation value DB 12C: Material calculation value DB 12D: Material processing calculation value DB 13: Communications Department 14: Reading section 16: Communications Department 1P: Program 1a: Portable storage medium 2: Terminal 2P: Program 21: Control Unit 22: Storage section 23: Communications Department 24: Input section 25:Display section B: Bus N: Network

Claims

1. When acquiring data on the aforementioned activities involving other businesses related to the activities of a business operator during a specified period, the data provided by the aforementioned other businesses during a period prior to the specified period may be used. Based on the data used, a predetermined process is performed. Information processing methods.

2. The aforementioned data relates to ESG or sustainability, and when activity levels for calculating greenhouse gas emissions are obtained, the predetermined process is the process of calculating the emissions based on the obtained activity levels. The information processing method according to claim 1.

3. As data related to the aforementioned activities, prior to adopting data provided by the aforementioned other business operator during a period prior to the aforementioned period, a confirmation message will be sent to the aforementioned other business operator. If, in response to the aforementioned confirmation message, it is obtained that there are no changes to the aforementioned data, the data provided by the other business operator during a period prior to the aforementioned period will be used. The information processing method according to claim 1.

4. The aforementioned confirmation message shall include a request for the updated data if there are any changes to the data, and if the updated data is obtained as a response to the aforementioned confirmation message, Based on the modified data, perform the predetermined processing. The information processing method according to claim 3.

5. When multiple data responses have been received from the aforementioned other business operator, a confirmation message is sent to the aforementioned other business operator. For each of the aforementioned data sets, the other business operator will either confirm that there has been no change from the data provided in a period prior to the aforementioned period, or obtain the updated data. The information processing method according to claim 1.

6. If the elapsed period from the aforementioned prior period to the aforementioned predetermined period exceeds the threshold, the confirmation message will be output to the other business operator. The information processing method according to claim 3.

7. When acquiring data on the activities of the said business operator in which other businesses are involved during a specified period, the data provided by the other businesses in a period prior to the specified period may be used. Based on the data used, a predetermined process is performed. An information processing program that executes a process.

8. A calculation device comprising a control unit, The control unit, When acquiring data on the activities of other businesses involved in the activities of a business operator during a specified period, the process includes adopting data provided by the other businesses in a period prior to the specified period, Based on the data used, a predetermined process is performed. An information processing device that performs the following actions.

Images