Support apparatus, support method, and support program

Abstract

To support efficient collection of data for credit authentication for an activity of contribution to sustainability.SOLUTION: An information management apparatus includes: a storage apparatus for storing attribute information of users who are involved in contribution activities for sustainability; and a processing apparatus which executes a selection process and a data imputation process, the selection process being configured to select, based on the attribute information, one or more second users who are candidates to provide missing data, out of data necessary for a certification body to authenticate the credit for trading environmental values obtained through contribution activities executed by a first user, the data imputation process being configured to receive the missing data input from a second user and transmit the missing data input from the second user to an information processing apparatus related to the first user.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an assistance device, an assistance method, and an assistance program. [Background technology]

[0002] As momentum for realizing a sustainable society grows, sustainable finance such as green bonds or credits is attracting attention. Certification and issuance of credits require the collection of data (e.g., measurement data) on the target clean assets or projects.

[0003] Patent Document 1 discloses a system that aggregates the amount of CO2 reduction in each household and makes it possible to trade on an emissions trading market.

[0004] Patent document 2 discloses a system that distributes rewards to providers of the data and processing services that make up an application, based on the contribution rate to the amount of usage benefit that a user can obtain from the application, for any application that is composed of processing services provided by multiple providers. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2023-103801 [Patent Document 2] Japanese Patent Application Laid-Open No. 2015-99492 Summary of the Invention [Problem to be solved by the invention]

[0006] However, with the above-mentioned techniques, it is difficult to efficiently collect a wide range of data for credit verification in each of the wide variety of projects that aim for sustainability.

[0007] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an assistance device, an assistance method, and an assistance program that can assist in the efficient collection of data for credit authentication for activities that contribute to sustainability. [Means for solving the problem]

[0008] One aspect of the present invention for solving the above problem is an information management device that includes a storage device that stores attribute information of each user involved in each contribution activity to sustainability, and a processing device that executes a selection process that selects, based on the attribute information, one or more second users who are candidate sources of missing data among the data required by a certification body to certify credits for trading environmental value resulting from a contribution activity carried out by a first user, and a data completion process that accepts input of the missing data from the second user and transmits the missing data input by the second user to an information processing device related to the first user. [Effects of the Invention]

[0009] According to the present invention, it is possible to support efficient collection of data for credit authentication for activities that contribute to sustainability. Configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of the configuration of a support system according to an embodiment of the present invention. [Figure 2] FIG. 10 is a diagram illustrating an example of a member attribute information table. [Figure 3] FIG. 10 is a diagram illustrating an example of a data shortage history table. [Figure 4] FIG. 10 is a sequence diagram illustrating the flow of processing performed in the support system. [Figure 5] FIG. 2 is a process flow diagram illustrating an outline of a process performed by the information management device. [Figure 6] FIG. 10 is a process flow diagram illustrating details of the data provider selection process. [Figure 7] FIG. 10 is a diagram showing an example of plotting member attribute information. [Figure 8] FIG. 10 is a diagram illustrating an example of clustering of target members. [Figure 9] FIG. 10 is a diagram illustrating an example of group information. [Figure 10] FIG. 10 is a process flow diagram illustrating details of data complementation processing. [Figure 11] FIG. 10 is a process flow diagram illustrating details of a reward distribution process. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings. In the following explanation, various types of information may be described using expressions such as "table," "list," and "queue," but the various types of information may also be expressed using data structures other than these. To indicate that the information is not dependent on the data structure, "XX table," "XX list," etc. may be referred to as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable. When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted. Furthermore, in the following description, processing performed by executing a program may be described, but the program is executed by a processor (e.g., a CPU or a GPU) to perform the specified processing while appropriately using storage resources (e.g., a memory) and / or interface devices (e.g., a communication port), and therefore the subject of the processing may be the processor. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be any computing unit, and may include a dedicated circuit (e.g., an FPGA or an ASIC) that performs a specific processing. A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0012] <System configuration> FIG. 1 is a diagram showing an example of the configuration of a support system 1 according to this embodiment.

[0013] To certify environmental value, such as CO2 and other emissions reductions achieved through the introduction of energy-saving equipment or the use of renewable energy in sustainability-oriented projects (activities contributing to sustainability), or CO2 and other absorption through appropriate forest management, as tradable "credits" (e.g., emission rights), requires a wide range of data as evidence. Sustainable projects (hereinafter simply referred to as "projects") are corporate initiatives, such as ESG (Environmental Social Governance) or CSR (Corporate Social Responsibility), aimed at achieving sustainability, which combines social and environmental sustainability with economic growth. Credits (a system for trading environmental value) can be voluntary credits issued by private companies or organizations (e.g., carbon credits (a system for buying and selling greenhouse gas emission reductions, including CO2, to achieve carbon offsets)), or government-led environmental certificates.

[0014] For example, in a forest management project, credit certification may require past absorption records and the maintenance of carbon fixation in the future (persistence). Here, we will explain the case where a creator (e.g., a company, organization, or individual) who wishes to create credits is considering purchasing forest land F, which has been repeatedly bought and sold, as a promising piece of land for forest management.

[0015] The creator can calculate the forest area from satellite images of forest land F and obtain a predicted amount of CO2 emission reductions. However, because forest land F has been bought and sold repeatedly, it is difficult for the creator to independently investigate the past use of forest land F (or identify past owners) and obtain past absorption performance. Furthermore, even if the creator wants to ask other users to supplement the necessary data, it is difficult to identify which users have what data, or to identify each user's contact information.

[0016] Furthermore, data providers cannot provide data easily, considering the risk of information leaks, etc. Furthermore, providing data involves costs and burdens, so it is necessary to motivate data providers.

[0017] On the other hand, if credits are approved for a project without sufficient information, the credibility of the credits will decrease and the risk of the credit value exceeding the expected value will increase.

[0018] To solve these problems, the support system 1 in this embodiment makes it possible to easily provide information about forest land F held by past owners of forest land F (e.g., registration information, image data capturing the scenery of forest land F, felling plans, etc.) to a creator who is considering purchasing forest land F. In this way, the support system 1 helps the creator efficiently collect the data necessary for credit authentication.

[0019] 1, the support system 1 includes an information management device 10, a creator-held facility 2, a data provider-held facility 3, and a credit authentication authority system 40. The information management device 10, the creator terminal 20, the data provider terminal 30, and the credit authentication authority system 40 are communicatively connected to each other via a wired or wireless communication network N such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line.

[0020] The creator-owned facility 2 is a facility owned by a creator (e.g., a company, organization, or individual) who wishes to generate credits for a project they are implementing. The creator-owned facility 2 includes a project management system 21 and a creator terminal 20.

[0021] The project management system 21 is an information processing system that manages a project executed by a creator. For example, if the project is a project to reduce CO2 (carbon dioxide) emissions through solar power generation, the project management system 21 is a solar power generation system that manages solar power generation facilities, etc. If the project is a project to reduce CO2 emissions through forest management, the project management system 21 is a system that manages measurement data or prediction data related to the forest. The project management system 21 includes a project database 211 that stores data related to the project. The project management system 21 may also include a control unit that controls facilities related to the project, or a measurement unit that measures data related to the project (for example, the amount of solar power generation, etc.).

[0022] The creator terminal 20 is an information processing device related to the creator who executes the project, such as a personal computer, tablet terminal, or smartphone. The creator terminal 20 is communicably connected to the project management system 21. The creator terminal 20 can access (read or write) data stored in a project database 211. The creator terminal 20 includes a data linking unit 201 that registers data related to the project in the information management device 10 or collects data from the information management device 10, and an application function unit 202 that applies for credits related to the project to a certification organization.

[0023] The data provider-owned facility 3 is a facility owned by a data provider that holds data related to other projects (projects other than the project implemented by the creator). The data provider may be a project implementer implementing another project, or a collaborator of another project. A collaborator is a project participant who cooperates with the project by measuring data related to the project or managing equipment related to the project (e.g., forest patrol work), and receives incentives such as cooperation fees or a portion of credit revenue from the project implementer in return. Since there may be many collaborators for a single project, it is assumed that the number of data providers is sufficiently large. Note that while FIG. 1 illustrates one data provider-owned facility 3, the support system 1 may include multiple data provider-owned facilities 3. The data provider-owned facility 3 includes a data management system 31 and a data provider terminal 30.

[0024] The data management system 31 is an information processing system that manages data on projects related to data providers. The data management system 31 includes a data storage unit 311 that stores data related to projects in which data providers are involved.

[0025] The data provider terminal 30 is an information processing device related to the data provider, such as a personal computer, a tablet terminal, or a smartphone. The data provider terminal 30 is communicably connected to the data management system 31. The data provider terminal 30 can access (read or write) data stored in the data storage unit 311. The data provider terminal 30 includes a data linking unit 301 that provides project-related data to the information management device 10.

[0026] The credit certification authority system 40 is an information processing system related to a certification authority (examination body) that certifies the credits of a project. The credit certification authority system 40 includes a credit certification data management unit 41. The credit certification data management unit 41 receives application data for applying for certification of credits related to a project from the creator terminal 20, and certifies the credits based on the received application data.

[0027] The information management device 10 is an information processing device that supports the efficient collection of data for authenticating project credits for creators who implement projects. The information management device 10 includes a central control device 11 (processing device) such as a CPU (Central Processing Unit), a main storage device 12 configured with memories such as RAM (Random Access Memory) and ROM (Read Only Memory), an auxiliary storage device 13 such as an HDD (Hard Disk Drive) or SSD (Solid State Drive), an output device 14 such as a display or printer, an input device 15 such as a keyboard, mouse, or touch panel, and a communication interface 16 configured with a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like.

[0028] The main storage device 12 stores programs for realizing the functions of the data provider selection unit 121, the data complementation unit 122, and the reward distribution unit 123.

[0029] The data provider selection unit 121 executes a selection process to select a data provider (second user) who is expected to be able to compensate (supplement) missing data (hereinafter referred to as "missing data") among data required for the authentication authority to authenticate credit in a project implemented by the creator (first user), based on member attribute information described later. The data provider corresponds to a candidate provider of the missing data.

[0030] The data complementing unit 122 executes a data complementing process in which it receives input of the missing data from the selected data provider, and transmits the missing data input from the data provider to the creator terminal 20 to provide it to the creator.

[0031] The reward distribution unit 123 executes a calculation process to calculate a reward to be paid (distributed) to the data provider based on the degree to which the missing data input by the data provider contributed to the authentication of the credit (degree of contribution).

[0032] Each function of the information management device 10 is realized by the central control device 11 reading and executing each program that realizes each function, which is stored in the main memory device 12. Note that each program may be pre-recorded in the auxiliary memory device 13 or an external storage medium, or may be installed when needed via a predetermined communication network. Furthermore, each program may be recorded on, for example, a portable or fixed recording medium and distributed.

[0033] The auxiliary storage device 13 stores a member attribute information table D01, a data shortage history table D21 (performance data), and a reward distribution history table D23 that stores the history of rewards distributed to data providers.

[0034] (Member attribute information table) FIG. 2 is a diagram showing an example of a member attribute information table D01. The member attribute information table D01 is a database that manages information about creators and data providers registered in the information management device 10. Hereinafter, creators and data providers may be collectively referred to as "members." A member corresponds to each user involved in each project. The auxiliary storage device 13 stores a member attribute information table D01 for each member (one member attribute information table D01 for each member). That is, the information management device 10 stores as many member attribute information tables D01 as there are registered members. The member attribute information table D01 has data items: attribute name D011, in which the name of the attribute is set; description D012, in which a description of the attribute is set; and attribute value D013, in which the value of the attribute is set. The data stored in each data item of the member attribute information table D01 is member attribute information. The member attribute information includes information about the projects in which each member is involved.

[0035] (Data Missing History Table) 3 is a diagram showing an example of the data deficiency history table D21. The data deficiency history table D21 is a database that manages the track record of missing data that occurred when authenticating credit for each project in which each member is involved. The data deficiency history table D21 has the following data items: a data deficiency case D211 in which a missing item (case) is set; a label D212 in which a label attached to the data deficiency case D211 is set; a member ID D213 in which a member ID that identifies each member is set; and an occurrence date D214 in which the date on which the data deficiency case D211 occurred is set.

[0036] Next, the processing performed by the support system 1 will be described.

[0037] <Processing flow> 4 is a sequence diagram illustrating the flow of processing performed by the support system 1. In this diagram, a project for absorbing CO2 by managing forest land F will be explained as an example.

[0038] First, the creator terminal 20 reads out project information about the project from the project database 211 of the project management system 21, and transmits the read out project information to the information management device 10 (S1). The project information includes a project ID that identifies the project, project attribute information "forest management", data items of sufficient data "forest satellite data" that are satisfied among the data required for the project to receive credit certification, data items of missing data that are insufficient (hereinafter referred to as "missing items"), and the amount of credits to be created by certification (hereinafter referred to as "credit creation amount"). The missing items correspond to the types of missing data.

[0039] The information management device 10 receives the project information and identifies the missing items "history" and "images (e.g., landscape images)" based on the received project information. Then, the information management device 10 executes a data provider selection process to select one or more data providers based on the identified missing items "history" and "images" (S2).

[0040] Next, the information management device 10 executes a data complementing process to complement the data of the missing items "history" and "image" (S3).

[0041] Specifically, first, the information management device 10 multicasts a data completion request (completion recommendation) for the missing items "history" and "image" to the data provider terminals 30 related to all the selected data providers.

[0042] When the data provider terminal 30 receives the completion request, it accepts input of data for the missing items from the data provider. The data provider inputs the completion data to the data provider terminal 30 in order to provide the data for the missing items (hereinafter referred to as "complementary data"). The data provider terminal 30 transmits the completion data for the missing items "history" and "image" input by the data provider to the information management device 10.

[0043] The information management device 10 receives the complementary data for the missing items “history” and “image” from the data provider terminal 30 and transmits the received complementary data to the creator terminal 20 .

[0044] The creator terminal 20 receives the complementary data and links the received complementary data, "history data" and "image data," with the sufficiency data, "forest satellite data," stored in the project database 211 (S4).

[0045] Then, the creator terminal 20 transmits application data for applying for credit certification to the credit certification authority system 40, requesting the certification authority to certify and create the credit (S5). The application data includes supplementary data for the missing items "history" and "image", and the fulfillment data "forest satellite data".

[0046] When the creator terminal 20 receives data indicating the credit authentication result (hereinafter referred to as the “credit authentication result”) from the credit authentication organization system 40, it transmits the received credit authentication result to the information management device 10.

[0047] The information management device 10 receives the credit authentication result from the creator terminal 20, and executes a reward distribution process to distribute rewards to the data provider based on the received credit authentication result (S6). In this embodiment, an example will be described in which project credits are distributed to the data provider as rewards.

[0048] The data provider terminal 30 receives the reward distributed to the data provider (S7), and then the process ends.

[0049] <Processing Overview> 5 is a processing flow diagram illustrating an outline of processing performed by the information management device 10. The processing shown in this diagram is executed, for example, when predetermined data (for example, project information, etc.) is received from the creator terminal 20.

[0050] First, the data provider selection unit 121 registers the member attribute information of the creator (S101). Specifically, the data provider selection unit 121 displays an input screen on the creator terminal 20 for accepting input of the creator's member attribute information, and accepts input of the member attribute information from the creator. Then, the data provider selection unit 121 receives the member attribute information entered by the creator from the creator terminal 20. The data provider selection unit 121 generates a member attribute information table D1 of the creator based on the received member attribute information, and writes and stores the generated member attribute information table D1 in the auxiliary storage device 13.

[0051] Next, the data provider selection unit 121 identifies missing items in the project (data missing cases) based on the project information, and writes and registers the identified missing items in the missing data history table D21 (S102). The data provider selection unit 121 may automatically identify missing items based on the project information, or may receive data indicating the missing items from the creator terminal 20 (accept input of the missing items from the creator).

[0052] Next, the data provider selection unit 121 acquires a data shortage history table D21 that shows the results of missing data in projects involving members other than the creator, and a member attribute information table D01 that shows the member attribute information of other members (S103).

[0053] Next, the data provider selection unit 121 executes a data provider selection process (S2).

[0054] <Data provider selection process> FIG. 6 is a process flow diagram illustrating the details of the data provider selection process S2.

[0055] First, the data provider selection unit 121 acquires an event (data deficiency case) that corresponds to (is the same as or similar to) a missing item in the creator's project from the data deficiency history table D21 (S201). Note that which data deficiency case is similar is set in advance by the user. Below, an example will be described in which a data deficiency case "planting history data" is acquired as an event that corresponds to a missing item.

[0056] Next, the data provider selection unit 121 converts the acquired events (data insufficiency cases) into numerical values and labels them (S202). For example, in the data example shown in Fig. 3, the label "100" is assigned to the data insufficiency case "planting history data".

[0057] Next, the data provider selection unit 121 acquires member attribute information of all target members in the acquired event (data-insufficient case), quantifies (converts into attribute values) the data for each attribute, and plots the data in N dimensions (N is the number of attributes) (S203). In the data example shown in Figures 2 and 3, the data provider selection unit 121 acquires member attribute information of all member IDs corresponding to the data-insufficient case "planting history data," and plots each member in nine dimensions using the attribute values of multiple attribute names: "age (member's age)," "gender (member's gender)," "address (member or forest address)," "business_history (forest age)," "area (forest area area)," "longitude (forest longitude (location))," "latitude (forest latitude (location))," "distance (distance from the nearest station to the forest)," and "rain (forest rainfall)." For example, in the data example shown in Figure 2, the target member is plotted as (age: 69, gender: 1, address: 42, business_history: 48, area: 30, 300h, longitude: 141° 30, latitude: 43° 13, distance: 37km, rain: 328).

[0058] (Plot example) Figure 7 is a diagram showing an example of a plot of member attribute information. For convenience, this diagram shows an example in which each target member is plotted two-dimensionally using the attribute values of the attribute names "business_history" and "area." Each circle plotted in this diagram corresponds to each target member.

[0059] Next, the data provider selecting unit 121 finds the distance between the project creator and each of the plotted target members using the Euclidean distance (S204).

[0060] Next, the data provider selection unit 121 specifies the number K of groupings (clusters) (the number K of clusters) based on the amount of credits created for the project (the amount of credits created by authentication) and the number of target members (S205). As the number of data providers increases, the amount of reward per data provider (per data provider) decreases. Therefore, the data provider selection unit 121 specifies the number K of groupings so that the amount of reward per data provider remains approximately constant (not too low). For example, if the amount of credits created is "300", the number of target members is "100", and the target amount of rewards to be distributed to data providers (the amount of credits to be distributed) is set to "3 or more", the data provider selection unit 121 sets K=3.

[0061] In addition, the data provider selection unit 121 may specify the number of clusters K by feeding back (learning) successful cases (method of calculating K or the number of K) in which the amount of reward (actual value) actually distributed to data providers achieved the target ("3 or more" in the above example).

[0062] Next, the data provider selection unit 121 clusters (groups) the target members into a number K based on the distance from the creator using a clustering method such as the K-means method (S206).

[0063] (Clustering example) Fig. 8 is a diagram showing an example of clustering of target members. This figure shows an example in which target members are clustered into three groups (clusters) A to C based on the distance from creator P1 in the example plot shown in Fig. 7.

[0064] Then, the data provider selecting unit 121 generates group information D13 that represents the results of the clustering.

[0065] (Group information) 9 is a diagram showing an example of group information D13. The group information D13 has the following data items: data-insufficient case D131, label D132, member ID D133, Euclidean distance D134 in which the Euclidean distance to the creator is set, and group D135. The group D135 is set with the clustering results (the group to which the target member belongs). In the example shown, member IDs "7," "3," "10," "5," and "1" belong to group "A," member IDs "8," "2," "6," and "9" belong to group "B," and member ID "4" belongs to group "C."

[0066] Next, the data provider selection unit 121 determines whether there are any remaining items in the missing items of the project (missing items for which members have not been clustered) (S207). If there are any remaining items, the data provider selection unit 121 returns to the process of S201 and executes the processes of S201 to S206 for the remaining items. On the other hand, if there are no remaining items, the data provider selection unit 121 ends this data provider selection process.

[0067] Following the data provider selection process, the data complementing unit 122 executes a data complementing process (S3).

[0068] <Data Complementation> FIG. 10 is a process flow diagram illustrating the details of the data complementation process S3.

[0069] First, the data complementing unit 122 lists information (e.g., email addresses) of target members of the corresponding group for each missing item (data insufficiency case) of the project based on the group information D13 (S301). For example, in the data example shown in Fig. 9, the data complementing unit 122 reads out, from the member attribute information D01, the email address of the member ID of group "A" that has the closest Euclidean distance to creator P1 in the data insufficiency case "planting history data".

[0070] Next, the data complementing unit 122 multicasts a message to the target members of the group to prompt them to complete the missing data items (S302). For example, in the data example shown in Fig. 9, the data complementing unit 122 sends a message to the email addresses of all members of group "A" to prompt them to complete the missing data items (for example, planting history data for a predetermined period) for forest land F, which is the target of the project.

[0071] Next, the data complement unit 122 presents the missing items to the members of the corresponding group and accepts their input (S303). For example, the data complement unit 122 displays an input screen on the data provider terminal 30 for accepting input of data for the missing items. The data provider inputs the data for the missing items on the input screen. At this time, the data provider terminal 30 may read out the data specified by the data provider from the data storage unit 311 of the data management system 31. The data provider terminal 30 transmits the supplementary data input by the data provider on the input screen to the information management device 10.

[0072] The data complementing unit 122 receives the complemented data from the data provider terminal 30 and stores complement history information D11 that associates the project ID, the missing item, the complemented data for the missing item, and the member ID of the data provider who provided the complemented data. Note that the data complementing unit 122 may directly obtain the complemented data specified by the data provider from the data storage unit 311 of the data management system 31.

[0073] Next, the data complementing unit 122 transmits the complemented data input by the data provider to the creator terminal 20 associated with the creator of the project (S304), and ends this data complementing process.

[0074] The creator terminal 20 transmits application data including the received complementary data and fulfillment data to the credit authentication authority system 40, requesting the authentication authority to authenticate and create credits for the project. Then, the creator terminal 20 receives a credit authentication result from the credit authentication authority system 40, and transmits the received credit authentication result to the information management device 10.

[0075] When the reward distribution unit 123 receives the credit authentication result from the creator terminal 20, it executes a reward distribution process (S6).

[0076] <Reward distribution process> 11 is a process flow diagram illustrating the details of the reward distribution process S6. This diagram illustrates an example in which credits are distributed to data providers as rewards.

[0077] First, the reward distribution unit 123 receives and acquires the credit authentication result from the creator terminal 20 (S601). The credit authentication result includes the creator's member ID, whether the credit authentication was approved or rejected, the credit authentication period (the period verified at the time of authentication), the authenticated amount of credit (the amount of credit created), the verification items verified in the credit authentication, and the contents of each verification item (for example, the certificate or evidence used, etc.).

[0078] Next, the reward distribution unit 123 determines whether or not the credit has been authenticated by the data provider's complementation based on the credit authentication result (S602).

[0079] If the credits are not authenticated by complementation (S602: No), the reward distribution unit 123 updates the reward addition coefficient in the member attribute information table D01 of the data provider who provided complementary data to the project (for example, by adding 0.1) (S603), and then ends the reward distribution process.

[0080] The reward addition coefficient is a coefficient that represents the proportion (or ratio) of the reward amount to be distributed to data providers. By adding the reward addition coefficient of data providers who did not contribute to the authentication of credits, the proportion of the reward amount can be increased (surcharged) when distributing the next reward to data providers who did not receive the reward this time. This can improve (motivate) the motivation of data providers to provide data.

[0081] On the other hand, if the credit is authenticated by complementation (S602: Yes), the reward distribution unit 123 extracts the creator's member ID, authentication period, authentication amount, and verification items from the credit authentication result (S604).

[0082] Next, the reward distribution unit 123 acquires the details of the authentication for each verification item (S605). Specifically, the reward distribution unit 123 acquires proof or evidence data of the authentication for each verification item.

[0083] Next, the reward distribution unit 123 identifies the member ID of the data provider who contributed to the authentication of the credit (S606). Specifically, the reward distribution unit 123 refers to the complementation history information D11 to identify the member ID of the data provider who complemented the data of the verification item for which there is proof or evidence.

[0084] Next, the reward distribution unit 123 identifies a period during the authentication period during which the identified data provider contributed to the authentication (S607). For example, if the data provider complements history information or weather information for a predetermined period included in the authentication period based on the content of complementary data provided by the identified data provider, the reward distribution unit 123 identifies the predetermined period as a period during which the data provider contributed to the authentication.

[0085] Next, the reward distribution unit 123 calculates the distribution amount (degree of contribution) corresponding to the identified relevant period (S608). For example, if the total amount of reward (amount of authentication) is 100 and the supplemented relevant period is 20 days out of the total authentication period of 200 days, the reward distribution unit 123 calculates the distribution amount as "10" as 100 / 200*20, which is a contribution of 10.

[0086] Next, the reward distribution unit 123 reads and obtains the reward addition coefficient from the member attribute information table D01 for the member ID of the identified data provider, and calculates the reward amount to be distributed to the data provider (S609). In this embodiment, the reward amount is the amount of credits to be distributed to the data provider (hereinafter referred to as the "distributed credit amount"). For example, if the reward addition coefficient of the data provider is "1.1", the reward distribution unit 123 multiplies the distributed amount of "10" by the reward addition coefficient "1.1" to obtain the distributed credit amount of "11". In this case, the credit amount of the creator is 89 (=100-11), which is obtained by subtracting the distributed credit amount from the authentication amount of "100". In addition, the reward distribution unit 123 associates the project ID, the member ID of the creator, the member ID of the data provider to whom the reward is distributed, and the distributed credit amount (reward amount) and stores them in the reward distribution history table D23.

[0087] Next, the reward distribution unit 123 distributes the determined amount of reward to the data provider (S610). Specifically, the reward distribution unit 123 transmits data for distributing the determined amount of distributed credits, "11", to the data provider terminal 30 related to the identified data provider.

[0088] Next, the reward distribution unit 123 updates the reward addition coefficient of the data provider who did not contribute to the credit authentication (for example, by adding 0.1) in the member attribute information table D01 for that data provider for future rewards (S611). After that, this reward distribution process ends.

[0089] In this embodiment, a case has been described in which credits are distributed to data providers as remuneration, but the remuneration is not limited to credits and may be other incentives such as remuneration money (cash) or points.

[0090] Furthermore, if the data provider-owned equipment 3 is managed by an external traceability system (equipment management system), the data complement unit 122 may automatically identify complementary data for missing items based on address change information, registration information, business operation information, and the like managed in the equipment management system. In this case, the data complement unit 122 transmits data requesting the provision of the identified complementary data to the data provider terminal 30. The data provider terminal 30 receives an input from the data provider indicating whether or not to provide the identified complementary data and transmits the inputted approval or denial to the information management device 10. When the data complement unit 122 receives an input from the data provider indicating approval or denial of the provision of complementary data, it automatically acquires the identified complementary data from the data storage unit 311 of the data management system 31 or the equipment management system and transmits the acquired complementary data to the creator terminal 20. This allows the data provider to automatically provide appropriate complementary data to the creator simply by inputting whether or not the data provider needs the data. This eliminates the need for the data provider to identify and input complementary data for missing items and prevents inappropriate complementary data from being provided due to input errors or the like.

[0091] Furthermore, in this embodiment, the creator terminal 20 applies for credit authentication directly to the credit authentication agency system 40, but this is not limiting and the application for credit authentication may be made via the information management device 10. In this case, the creator terminal 20 transmits application data to the information management device 10. The information management device 10 receives the application data from the creator terminal 20 and transmits the received application data to the credit authentication agency system 40. Meanwhile, the credit authentication agency system 40 returns a credit authentication result based on the application data to the information management device 10. The information management device 10 receives the credit authentication result from the credit authentication agency system 40 and transmits the received credit authentication result to the creator terminal 20, and also executes a reward distribution process based on the received credit authentication result.

[0092] As described above, the information management device 10 of this embodiment stores attribute information (member attribute information) of each user (member) involved in each contribution activity (project) to sustainability, and performs a selection process to select, based on the member attribute information, one or more second users (data providers) who are candidate sources of missing data among the data required for a certification body to certify credits for trading environmental value from a project implemented by a first user (creator), and a data completion process to accept input of missing data from the second user and transmit the missing data input by the second user to an information processing device (creator terminal 20) related to the first user.

[0093] That is, the information management device 10 of this embodiment can select members who are likely to have missing data as data providers and accept data provided by the selected data providers. This allows the creator to more efficiently collect data necessary for credit authentication. For example, it is possible to reduce the burden or costs associated with data measurement, data management, or work. That is, it is possible to support the creator in efficiently collecting data for credit authentication for a project.

[0094] In addition, the member attribute information includes information regarding the project in which the member is involved, and in the selection process, the information management device 10 clusters the members based on the member attribute information and selects as data providers members of clusters whose information regarding the project is closer to the creator than other clusters.

[0095] That is, the information management device 10 of this embodiment can select, as data providers, members who have been involved in projects similar to the project implemented by the creator. This makes it possible to more accurately select data providers who can provide the missing data.

[0096] In addition, in the selection process, the information management device 10 of this embodiment clusters members using multidimensional data in which each of the multiple attributes contained in the member attribute information is quantified, and selects as data providers members from clusters whose member attribute information is closer to the creator than other clusters.

[0097] This makes it possible to perform clustering that takes into account each attribute (feature) related to the project, and to more accurately identify members who have been involved in projects similar to the project being undertaken by the creator.

[0098] In addition, in the selection process, the information management device 10 of this embodiment determines the number of clusters based on the amount of credits created by authentication and the number of members, clusters the members using the determined number of clusters, and selects as data providers users in clusters whose member attribute information is closer to the creator than other clusters.

[0099] This allows the number of data providers to be selected to be approximately constant. For example, the more data providers there are, the smaller the amount of reward per data provider. Therefore, by determining the number of clusters based on the amount of credits created and the number of members, the number of clusters can be set to match the amount of reward. This prevents the amount of reward per data provider from becoming too small.

[0100] In addition, the information management device 10 of this embodiment further stores a data deficiency history table D21 (performance data) that represents the performance of missing data in each project in which each member is involved, and in the selection process, refers to the data deficiency history table D21 to select members involved in projects with the same or similar type of missing data as the project implemented by the creator.

[0101] That is, the information management device 10 of this embodiment can select members involved in projects similar to the creator's project as data providers, thereby enabling more accurate selection of data providers who can provide the creator with the missing data.

[0102] In addition, the information management device 10 of this embodiment executes a calculation process to calculate the reward to be paid to the data provider based on the degree to which the missing data entered by the data provider contributed (contribution degree) to the credit authentication performed by the authentication authority.

[0103] This allows, for example, a data provider who provides data with a higher degree of contribution to receive a higher reward, thereby enabling more efficient collection of data that contributes to credit authentication.

[0104] In addition, the information management device 10 of this embodiment further stores a reward addition coefficient (ratio) for the reward to be paid to each member, and in the calculation process, if the data provided by the data provider contributes to the credit authentication, it calculates the reward to be paid to the data provider based on the reward addition coefficient, and if the data provided by the data provider does not contribute to the credit authentication, it increases the data provider's reward addition coefficient for future rewards to the data provider.

[0105] That is, the information management device 10 of this embodiment increases the reward addition coefficient of a data provider who does not receive a reward this time because the data they provided did not contribute to the authentication of credit, thereby increasing the proportion of reward that the data provider will receive from the next time onwards. This can motivate each member to provide data. In other words, it can prevent a decrease in motivation to provide data.

[0106] In addition, in the data complementation process, the information management device 10 of this embodiment acquires missing data from a system (data management system 31 or an external system) that manages data related to the project in which the data provider is involved, and transmits the acquired missing data to the creator terminal 20.

[0107] That is, the information management device 10 of this embodiment automatically acquires data held by a data provider from an external system, thereby saving the data provider the trouble of inputting missing data.

[0108] In addition, the project of this embodiment is a project that aims to absorb carbon dioxide by managing forests, and the missing data is data that is lacking in order to obtain past carbon dioxide absorption records in forests, and the member attribute information includes at least one of the location of the forest, the age of the forest, the area of the forest, or the rainfall in the forest in the project in which the member is involved.

[0109] This makes it possible to efficiently collect data to obtain past carbon dioxide absorption records in forests, which tend to be insufficient, in projects that aim to absorb carbon dioxide through forest management.

[0110] The present invention is not limited to the above-described embodiments, and can be implemented using any components within the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the characteristics of the invention are not impaired. Furthermore, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of the present invention are also included within the scope of the present invention.

[0111] For example, part of the hardware provided in each device in the above-described embodiments may be provided in another device.

[0112] Furthermore, each program of the information management device 10, creator terminal 20, or data provider terminal 30 may be provided on another device, a program may consist of multiple programs, or multiple programs may be integrated into one program. [Explanation of symbols]

[0113] 1. Support System 10 Information management device 121 Data Provider Selection Department 122 Data Completion Unit 123 Remuneration Distribution Department 2 Equipment owned by the creator 20 Creator Terminal 21 Project Management System 3. Facilities owned by data providers 30 Data provider terminal 31 Data Management System 40 Credit Authorization Authority System D01 Member attribute information table D21 Data Missing History Table D23 Reward distribution history table

Claims

1. a storage device that stores attribute information of each user involved in each sustainability contribution activity; and a selection process for selecting, based on the attribute information, one or more second users who are candidates for providing missing data among the data required for a certification body to certify credits for trading environmental value resulting from a contribution activity carried out by a first user; a data complementation process of receiving input of the missing data from the second user and transmitting the missing data input from the second user to an information processing device related to the first user; An information management device comprising a processing device that executes the above.

2. The attribute information includes information about contribution activities in which the user is involved, The processing device includes: In the selection process, the users are clustered based on the attribute information, and a user in a cluster whose information on contribution activities is closer to the first user than other clusters is selected as the second user. The information management device according to claim 1 .

3. The processing device includes: In the selection process, the users are clustered using multidimensional data in which each of a plurality of attributes included in the attribute information is quantified, and a user in a cluster whose attribute information is closer to that of the first user than to other clusters is selected as the second user. The information management device according to claim 2 .

4. The processing device includes: In the selection process, a number of clusters is determined based on the amount of credits generated by the authentication and the number of users, the users are clustered using the determined number of clusters, and a user in a cluster whose attribute information is closer to that of the first user than to other clusters is selected as the second user. The information management device according to claim 2 .

5. The storage device further stores performance data representing performance of the missing data in each contribution activity in which each of the users is involved; The processing device includes: In the selection process, by referring to the performance data, a user involved in a contribution activity having the same or similar type of missing data as the contribution activity performed by the first user is selected. The information management device according to claim 1 .

6. The processing device includes: a calculation process for calculating a reward to be paid to the second user according to the degree to which the missing data input by the second user contributed to the authentication of the credit performed by the authentication organization; The information management device according to claim 1 , wherein the information management device executes the following:

7. The storage device further stores a percentage of the reward to be paid to each user; The processing device includes: In the calculation process, if the data provided by the second user contributes to the authentication of the credit, the reward to be paid to the second user is calculated based on the ratio, and if the data provided by the second user does not contribute to the authentication of the credit, the ratio of the second user is increased for future rewards to the second user. The information management device according to claim 6.

8. The processing device includes: In the data complementing process, the missing data is acquired from a system that manages data related to contribution activities in which the second user is involved, and the acquired missing data is transmitted to an information processing device related to the first user. The information management device according to claim 1 .

9. The contribution activity is a project to absorb carbon dioxide by managing forests, The missing data is data that is insufficient to obtain a past record of carbon dioxide absorption in the forest, The attribute information includes at least one of the location of the forest, the age of the forest, the area of the forest, and the rainfall of the forest in the project in which the user is involved. The information management device according to claim 1 .

10. an information processing device that stores attribute information of each user involved in each sustainability contribution activity; a selection process for selecting, based on the attribute information, one or more second users who are candidates for providing missing data among the data required for a certification body to certify credits for trading environmental value resulting from a contribution activity carried out by a first user; and executing a data complementing process of receiving an input of the missing data from the second user and transmitting the missing data input from the second user to the information processing device related to the first user. Information management method.

11. An information processing device that stores attribute information of each user involved in each sustainability contribution activity, a selection process for selecting, based on the attribute information, one or more second users who are candidates for providing missing data among the data required for a certification body to certify credits for trading environmental value resulting from a contribution activity carried out by a first user; and executing a data complementing process of receiving an input of the missing data from the second user and transmitting the missing data input from the second user to the information processing device related to the first user. Information Management Program.

Images