Server device, idea management method, and program

Abstract

A server device according to the present disclosure includes: a reception means for receiving a plurality of ideas including a first idea and a second idea; a determination means for determining similarity between the first idea and the second idea; and a first management means for, when it is determined that the first idea and the second idea are similar, managing an idea pair of the first idea and the second idea as a candidate for relationship management.

Description

Server device, idea management method, and program

[0001] The present disclosure relates to a server device, an idea management method, and a program.

[0002] Techniques for issuing tokens for ideas and project proposals are known (for example, Patent Document 1). With such techniques, submitters who submit ideas and projects can obtain a rewarding value, and supporters of such ideas and projects can receive token distributions.

[0003] Japanese Patent Application Laid-Open No. 2022-18769

[0004] However, in the technique of Patent Document 1, since the relationship between ideas is not considered, it may not be possible to distribute benefits among multiple users corresponding to multiple related ideas. That is, there is a need to manage the relationship between ideas.

[0005] An object of the present disclosure is to provide a server device, an idea management method, and a program that can manage the relationship between ideas. It should be noted that this object is only one of the multiple objects that multiple embodiments disclosed in this specification attempt to achieve. Other objects or problems and novel features will be clarified from the description of this specification or the attached drawings.

[0006] The server device according to the present disclosure includes a receiving unit that receives a plurality of ideas including a first idea and a second idea, a determination unit that determines the similarity between the first idea and the second idea, and a first management unit that manages an idea pair of the first idea and the second idea as a candidate for relationship management when it is determined that the first idea and the second idea are similar.

[0007] The idea management method relating to this disclosure is an idea management method executed by a server device, which includes: receiving a plurality of ideas including a first idea and a second idea; determining the similarity between the first idea and the second idea; and, if the first idea and the second idea are similar, managing the idea pair of the first idea and the second idea as a candidate for relationship management.

[0008] The program relating to this disclosure causes a server device to perform the following processes: receiving a plurality of ideas, including a first idea and a second idea; determining the similarity between the first idea and the second idea; and, if the first idea and the second idea are similar, managing the idea pair of the first idea and the second idea as a candidate for relationship management.

[0009] This disclosure provides a server device, an idea management method, and a program that can manage the relationships between ideas.

[0010] This is a block diagram showing an example of the server device in this disclosure. This is a flowchart showing an example of the processing operation of the server device in this disclosure. This is a block diagram showing another example of the server device in this disclosure. This is a diagram showing an example of the input screen in this disclosure. This is a diagram showing an example of the display in this disclosure that asks the poster to approve or disapprove. This is a diagram showing an example of the screen that displays the relationships between ideas in this disclosure. This is a block diagram showing another example of the server device in this disclosure. This is a block diagram showing an example of the system in this disclosure. This is a flowchart showing another example of the processing operation of the server device in this disclosure. This is a diagram used to explain revenue distribution and token management. This is a diagram explaining the flow of a use case. This is a diagram showing an example of the server device configuration.

[0011] Embodiments will be described below with reference to the drawings. In this disclosure, the drawings may be associated with one or more embodiments. Also, each element in the drawings may correspond to one or more embodiments. In embodiments, the same or equivalent elements are denoted by the same reference numerals, and redundant descriptions are omitted. In this disclosure, "apparatus" may consist of one or more devices. Also, in this disclosure, "system" may consist of one or more devices.

[0012] <First Embodiment> <Example of Server Device Configuration> Figure 1 is a block diagram showing an example of a server device according to the present disclosure. In Figure 1, the server device 10 includes a reception unit 11, a similarity determination unit 12, and a relationship management unit (first management unit) 13.

[0013] The reception unit 11 accepts information about each of the multiple ideas. In other words, the reception unit 11 accepts multiple ideas. For example, the submitters may be different for each of the multiple ideas. Here, "idea" refers to a broad concept that includes new business plans, service / product proposals, research and development themes, software designs, etc. In particular, new business plans, service / product proposals, research and development themes, etc., can also be called "business ideas." Here, as examples of multiple ideas, we will give the first idea and the second idea for explanation. For example, the first idea may be an idea that was submitted before the second idea.

[0014] The similarity determination unit 12 determines the similarity between the first idea and the second idea. An example of this similarity determination will be explained in detail later.

[0015] The relationship management unit 13 manages the idea pair of the first idea and the second idea as a "candidate for relationship management" if it determines that the first idea and the second idea are similar. For example, the relationship management unit 13 may manage the first idea, which was submitted earlier than the first idea, as the source idea. The relationship management unit 13 may then manage the second idea, which was submitted later than the first idea, as the destination idea. In other words, the relationship management unit 13 may manage the first idea and the second idea, which are candidates for relationship management, as a hierarchical source idea and a destination idea, respectively. Details of relationship management will be explained in detail later.

[0016] <Example of Server Device Operation> Figure 2 is a flowchart showing an example of the processing operation of the server device of this disclosure.

[0017] The reception unit 11 receives multiple ideas (step S11).

[0018] The similarity determination unit 12 determines the similarity between the first idea and the second idea (step S12).

[0019] If the relationship management unit 13 determines that the first idea and the second idea are similar, it manages the idea pair of the first idea and the second idea as a candidate for relationship management (step S13).

[0020] As described above, according to the first embodiment, the similarity determination unit 12 in the server device 10 determines the similarity between the first idea and the second idea received by the reception unit 11. If the relationship management unit 13 determines that the first idea and the second idea are similar, it manages the idea pair of the first idea and the second idea as a candidate for relationship management.

[0021] This server device 10 configuration allows for the management of relationships between ideas. As a result, revenue can be distributed among multiple users, each corresponding to a multiple idea with relationships.

[0022] <Second Embodiment> Figure 3 is a block diagram showing another example of the server device of the present disclosure. In Figure 2, the server device 20 includes a reception unit 21, a similarity determination unit 22, a relationship management unit (first management unit) 23, and a display control unit 24.

[0023] The reception unit 21 accepts multiple ideas, similar to the reception unit 11. For example, the reception unit 21 may control the display device (not shown) of a device operated by the submitter (hereinafter sometimes referred to as the "user terminal") to display an input screen for entering ideas. The reception unit 21 may then accept the information entered by the user using the input screen as information related to the idea (i.e., the idea itself).

[0024] Figure 4 shows an example of the input screen in this disclosure. In the example input screen in Figure 4, the following can be entered as part of the new idea submission: "Idea Title," "Idea Summary," and "Expected Use Case."

[0025] Similar to the similarity determination unit 12, the similarity determination unit 22 determines the similarity between the first idea and the second idea. For example, the similarity determination unit 22 includes a similarity calculation unit 22A and a determination processing unit 22B.

[0026] The similarity calculation unit 22A calculates the similarity between the first idea and the second idea (i.e., the idea similarity). The idea similarity is a score calculated by comprehensively evaluating factors such as "component similarity," "purpose similarity," and "keyword match rate," and is an indicator of how similar ideas that are related to each other are.

[0027] The determination processing unit 22B determines that the first idea and the second idea are similar if the calculated similarity exceeds a predetermined threshold.

[0028] Similar to the relationship management unit 13, the relationship management unit 23 manages the idea pair of the first idea and the second idea as a "candidate for relationship management" if it determines that the first idea and the second idea are similar.

[0029] The relationship management unit 23 executes control to send a notification signal to a user terminal (not shown) associated with the submitter of the second idea for the relationship management candidate. This notification signal is, for example, an approval request signal asking the submitter of the second idea whether or not to approve designating the relationship management candidate as a formally managed "relationship managed item". When the user terminal (not shown) receives this notification signal, it prompts the submitter to respond by displaying a message on the display device (not shown) asking for approval or disapproval. The user terminal (not shown) then sends a response signal indicating approval or disapproval to the server device 10. If the relationship management unit 23 receives a response signal indicating approval, it manages the relationship management candidate as a formally managed "relationship managed item".

[0030] Furthermore, the relationship management unit 23 may, for example, refer to a "return rate table" to identify a return rate corresponding to the similarity between the ideas of the candidate for relationship management. The return rate table stores, for example, multiple similarity candidates and the corresponding return rate for each similarity candidate.

[0031] Figure 5 shows an example of a display in this disclosure that asks the poster to approve or disapprove. The display shown in Figure 5 may be displayed as a pop-up on the input screen described above.

[0032] The display shown in Figure 5 shows information about the source idea among the candidate idea pairs for relationship management (for example, "Existing Idea A-001" in Figure 5) and the similarity between the source idea and the second idea (i.e., the derived idea) (for example, "70%" in Figure 5). Also, as shown in Figure 5, the display asking the submitter to approve or disapprove may also show the title of the source idea, a list of its main components, etc. Furthermore, the display shown in Figure 5 shows a button to perform an approval operation ("Register as Derived Idea" in Figure 5) and a button to perform a disapproval operation ("Cancel" in Figure 5). Note that the information shown in the display asking the submitter to approve or disapprove may also be included in the notification signal described above.

[0033] The display control unit 24 controls the display on a display device (not shown) the relationships between multiple ideas that are subject to relationship management and are directly or indirectly related by similarity. The display control unit 24 may also perform this display control in response to a request from a user using a user terminal.

[0034] Figure 6 shows an example of a screen displaying the relationships between ideas in this disclosure. In Figure 6, the relationships between ideas are displayed in a tree structure, but this disclosure is not limited to this. For example, the relationships between ideas may be visualized in the form of a graph structure, a matrix, or the like.

[0035] Figure 6 shows the derivation relationships between ideas visualized in a tree structure. A large circle representing the original idea (original node: A-001) is placed at the top center of the screen, and multiple first-generation derived ideas (B-002, C-003, D-004, etc.) are displayed branching downwards. Below the first generation, second-generation derived ideas (E-005, F-006, etc.) are placed. The lines connecting the nodes displayed on the screen represent the connection between the source idea and the derived idea. In addition, each node displays its basic information, such as the idea ID and similarity (percentage). Furthermore, each node may also display basic information such as revenue amount. In the example screen in Figure 6, the revenue return flow is visualized by arrows. The arrows from the derived node (derived idea) to the source node (derived idea) represent the revenue flow (revenue return rate). The extent to which token revenue earned by derivative ideas is returned to the original idea can be visually represented using color coding, arrow thickness, and text display of ratios.

[0036] Furthermore, in the example screen shown in Figure 6, each node may be interactive. For example, when a user clicks on a node, a pop-up window containing detailed information about that idea is displayed. This detailed information may include the idea's title, summary, intended use cases, posting date and time, author information (department, etc.), past revenue performance, and related technical elements. Clicking on an edge connecting nodes may also display specific similarities between the two ideas and a detailed history of revenue sharing. In addition, search filters and sorting functions may be placed at the top of the screen to extract and display idea trees related to a specific period, department, or technology field.

[0037] <Third Embodiment> Figure 7 is a block diagram showing another example of the server device of the present disclosure. In Figure 7, the server device 30 includes a reception unit 21, a similarity determination unit 22, a relationship management unit (first management unit) 23, a display control unit 24, a revenue distribution unit 31, and a record management unit (second management unit) 32.

[0038] The record management unit 32 records information about the idea pairs subject to relationship management on, for example, a blockchain (blockchain node not shown). Furthermore, if a distribution revenue value is calculated for an idea pair subject to relationship management, the record management unit 32 also reflects this distribution revenue value on the blockchain (blockchain node not shown).

[0039] In the following embodiment, the operation of the record management unit 32 will be explained using blockchain as an example. However, the technical architecture used by the record management unit 32 is not limited to blockchain. The record management unit 32 may use various forms of recording media, such as conventional databases or cloud storage.

[0040] The revenue distribution unit 31 calculates the revenue distribution value to be distributed from the revenue obtained from the second idea to the first idea, based on the revenue obtained from the second idea and the distribution ratio according to the similarity. The distribution ratio (i.e., the revenue return rate) is determined by the relationship management unit 23 as described above.

[0041] <4th Embodiment> The 4th embodiment relates to a more specific embodiment. Since the basic configuration of the server device in the 4th embodiment is the same as that of the server device 30 in the 3rd embodiment, it will be described with reference to FIG. 7.

[0042] <Overview of the System> FIG. 8 is a block diagram showing an example of the system of the present disclosure. In FIG. 8, the system 1 includes a server device 30, a user terminal 40, a blockchain node 50, and a database 60. The server device 30, the user terminal 40, the blockchain node 50, and the database 60 are connected so that they can transmit and receive information to and from each other.

[0043] <Explanation of Processing Operations> FIGS. 9 and 10 are flowcharts showing another example of the processing operations of the server device of the present disclosure. FIG. 9 relates to the management of the relationship between ideas. FIG. 10 relates to profit distribution.

[0044] In the flow of FIG. 9, the reception unit 21 receives a new idea submission from the user (step S21). The information regarding the received idea includes metadata such as the outline, purpose, and assumed components of the idea.

[0045] The similarity calculation unit 22A refers to the information of the existing ideas stored in the database 60, and calculates the similarity based on, for example, the number of common keywords, the degree of correspondence between components, and the degree of agreement of purposes between the received idea and the existing ideas, using natural language processing, a machine learning model, etc. (step S22).

[0046] The determination processing unit 22B determines whether the calculated similarity exceeds a predetermined threshold (step S23).

[0047] When the similarity exceeds a predetermined threshold (e.g., 50%) (step S23 YES), the relationship management unit 23 manages the pair of ideas determined to be similar as "relationship management target candidates" (step S24).

[0048] The relationship management unit 23 executes control to transmit an approval request signal to the user terminal 40 associated with the submitter of the new (derived) idea of the relationship management target candidate (step S25). As described above, this approval request signal is a signal for asking the submitter of the new (derived) idea whether to approve the relationship management target candidate as a formal management target, "relationship management target".

[0049] The relationship management unit 23 waits for a response signal (step S26 NO). When a response signal indicating approval is received (step S26 YES, step S27 YES), the relationship management unit 23 manages the relationship management target candidate as a formal management target, "relationship management target" (step S28).

[0050] The record management unit 32 records information regarding the idea pair of the relationship management target in the blockchain (blockchain node 50) (step S29). For example, the record management unit 32 records the association information between both ideas of the idea pair in a tree-like data structure.

[0051] In addition, when the similarity is below the threshold (step S23 NO), or when the response signal indicates disapproval (step S27 NO), the processing flow of FIG. 9 ends.

[0052] The flow of FIG. 10 starts when the derived idea is actually commercialized or projectized, and revenue in the form of tokens such as sales and investments is generated.

[0053] The revenue distribution unit 31 calculates a distributed revenue value to be distributed to the original idea from the revenue obtained based on the derived idea (step S31). The revenue distribution unit 31 reduces tokens for the original idea at a certain ratio. The ratio here is variable based on the similarity, and for example, a calculation formula such as reducing 10 - 15% of the revenue for a similarity of 70% is applied.

[0054] The record management unit 32 writes this reduction process to the blockchain node 50 and records the transaction information in the distributed ledger in a tamper-proof form (step S32).

[0055] Hereinafter, each process in the server device 30 will be specifically described.

[0056] (Specific methods for similarity determination) Similarity determination can be achieved using various technical approaches described below. A basic approach is to analyze the text data of ideas using natural language processing techniques. Specifically, this includes calculating the degree of similarity of important words extracted by morphological analysis, calculating the similarity between word vectors using distributed representations, and calculating inter-document similarity using distributed representations of the entire document. It is also possible to determine similarity while considering context using a pre-trained language model.

[0057] In analyzing structural similarities, methods that decompose ideas into constituent elements and evaluate the correspondences between those elements are effective. Specifically, by representing elements such as technological elements, target users, and business processes as nodes and their relationships as edges in a graph structure, graph similarity algorithms can be applied. It is also possible to define the conceptual hierarchy as an ontology and evaluate similarity based on the distance between concepts. Structural similarities can also be extracted from structured diagrammatic representations such as system design diagrams and Entity Relationship Diagrams (ER diagrams).

[0058] The similarity of the purpose and effects of ideas can be analyzed by classifying the problems to be solved into categories and using quantitative indicators of expected effects. Specifically, this involves evaluating the degree of overlap in target markets and assumed user groups, correlation analysis of expected numerical targets, and structural correspondences in business processes. It is also important to consider time-series elements and evaluate the similarity of the idea's development process and technological evolution patterns. Technical similarity and novelty can also be objectively evaluated by cross-referencing with patent databases and academic paper databases.

[0059] One way to integrate these different evaluation approaches is to appropriately weight multiple similarity metrics and calculate an overall similarity score. It is also possible to predict similarity from multiple features using machine learning models that utilize past evaluation results as training data. Furthermore, it is possible to implement a mechanism that dynamically selects the judgment method by setting different evaluation criteria depending on the field and purpose.

[0060] It is desirable that the results of the similarity determination be provided as multifaceted information, including not only a numerical similarity score, but also the specific content and degree of similarities, identification of parts with potential for derivative or development, and suggestions for complementary elements. Therefore, the similarity determination unit 22 can achieve highly accurate and practical similarity determination by appropriately selecting and combining the existing technologies described above according to the requirements.

[0061] (Idea Input, Approval of Relationship Management) When a user submits an idea, the input screen shown in Figure 4 is displayed on the display unit (not shown) of the user terminal 40. The user uses the input screen to enter the content of the new idea submission, such as the "Idea Title," "Idea Summary," and "Assumed Use Case." When the user presses the submit button, information about the idea is sent from the user terminal 40 to the server device 30.

[0062] If the relationship management unit 23 determines that the first idea and the second idea are similar, it manages the idea pair of the first idea and the second idea as a candidate for relationship management. The relationship management unit 23 then executes a control to send an approval request signal to the user terminal 40 associated with the poster of the second idea (derived idea) of the candidate for relationship management.

[0063] Upon receiving the approval request signal, the user terminal 40 displays a notification on its display unit (not shown) using a pop-up, such as "A 70% similarity to existing idea A-001 has been detected. Do you want to register it as a derivative idea?" (See Figure 5). The poster selects either the "Approve" button or the "Cancel" button. This sends a response signal from the user terminal 40 to the server device 30. If the relationship management unit 23 receives a response signal indicating approval, it manages the candidate for relationship management as a formally managed "relationship managed item". In addition to the similarity, the pop-up may also display the title of the source idea and a list of its main components. This allows the user to confirm the specific similarities before deciding whether to register.

[0064] (Revenue Distribution, Token Management) Figure 11 is a diagram illustrating revenue distribution and token management. When a derived idea node earns token revenue X through, for example, commercialization or investment agreements, the return amount Y is distributed to the original idea node as shown by the arrow representing the revenue flow. The distributed revenue is then recorded on the blockchain node.

[0065] Here, the reduction amount Y can be calculated, for example, using the following formula: Y = X × (similarity / 100) × coefficient K

[0066] For example, if the similarity is 70%, any setting such as K=0.2 is possible. The display unit (not shown) of the user terminal 40 may display a notification such as, "Derived idea B-002 has earned 100 tokens. Original idea A-001 has received 10 tokens back." The display unit (not shown) of the user terminal 40 may also display the transaction ID and date and time of the revenue distribution.

[0067] The revenue distribution unit 31 performs these distribution processes periodically or in real time. The record management unit (second management unit) 32 then writes the token holding balance and transaction history after revenue distribution to the database 60 and the blockchain node 50. This ensures an unalterable audit trail.

[0068] As described above, the reception unit 21 manages new idea submissions, including a user interface and API. The similarity determination unit 22 calculates the similarity between ideas by applying natural language processing, machine learning, rule-based matching, etc. If the similarity exceeds a predetermined threshold, the relationship management unit 23 assigns the ID of the source idea and registers it in the tree structure. The relationship management unit 23 determines the ratio at which tokens obtained from the derived idea are automatically returned to the source idea. The revenue distribution unit 31 calculates the revenue distribution value to be distributed to the source idea from the revenue obtained based on the derived idea. The record management unit 32 writes this return process to the blockchain node 50. This prevents unauthorized modification. By having these functional units work together, a large number of ideas submitted by many users can be efficiently managed, the relationship with the source can be visualized, and the profits of the derived idea can be appropriately returned to the source idea. This makes it possible to realize a system that promotes co-creation and incentives among users.

[0069] (Use Case) The following is an example of a use case in which an information processing device is used to visualize individual contributions through participation in micro-projects within a company and reflect them in performance evaluations and career development. Although the following explanation uses new business development within a company as an example, it can be applied to idea management in various settings such as educational institutions, research institutions, and communities.

[0070] First, the reception unit 21 of the server device 30 (idea management system) installed within the company receives submissions of micro-projects (such as new product idea development, specific function development, and short-term event planning) from various departments and teams within the company. These micro-projects are then managed collectively as "ideas." When a project is submitted, information (metadata) such as the project overview, implementation period, required skills, and expected results is registered.

[0071] The similarity determination unit 22 checks the degree of relevance between new microprojects and existing microprojects to minimize overlap and conflict. When a new microproject is accepted, the relationship management unit 23 manages the derivative relationships with similar projects (such as the technical elements and business concepts of the existing project from which it is derived) as tree-like data. The display control unit 24 visualizes the relationships between ideas. This guides multiple teams within the company to avoid redundant work in similar areas while creating a situation where past knowledge can be utilized.

[0072] Each employee accesses the server device 30 (idea management system) from their user terminal 40, checks the list of microprojects and derived trees, and selects a project that matches their interests and skills. For example, if an engineer in the R&D department finds a new project called "Expanding the Data Analysis Platform," they submit a participation request via the reception unit 21. After approval, the employee performs tasks within the project and reports their results to the system as they occur. Tasks can range from "Developing specific components of an idea" and "Creating verification reports" to "Researching related technology patents." Each result is recorded on the blockchain by the record management unit 32 as contribution and evaluation points. The similarity determination unit 22 examines whether the submitted tasks and deliverables overlap with existing similar projects or whether cross-referencing is possible, and may provide recommendations as needed.

[0073] As a project progresses and achieves its goals, it may generate revenue as a micro-project (such as actual sales, internal evaluation points, or additional allocation of departmental budget). The revenue distribution unit 31 automatically calculates the tokens and evaluation points each individual should receive, taking into account the contribution of each project participant and the similarity to the original project. For example, if the original project provided a "basic data analysis algorithm," then a portion of the results of the new project, if it is an extension of that algorithm, can be set to return a certain number of points to the original project members. This mechanism ensures that original contributors are appropriately evaluated when projects are launched or expanded upon using existing knowledge. The record management unit 32 finally writes the allocated tokens and points to the blockchain.

[0074] The internal HR department can refer to these token and point records to understand each employee's participation in and contribution to micro-projects, as well as their actual demonstration of technical skills. For example, it becomes easier to evaluate employees who not only perform routine tasks but also support new projects across the organization. In performance reviews, an employee's achievements become visible not only in terms of "what projects they worked on" and "what results they achieved," but also in terms of which existing projects they developed as a basis for further business growth. This makes it easier to conduct comprehensive evaluations based on new business development capabilities and collaboration skills. By viewing their project participation history and token acquisition logs, employees can objectively reflect on their past experience and skill set, providing clues for considering future career paths and plans.

[0075] Specifically, if an employee participates in a "data analysis project utilizing AI models" and receives a high evaluation, they can then refer to logs showing that they can then participate in a "project that applies machine learning technology to a more advanced level," thereby developing their skills and accumulating evaluation points. In the future, they can be expected to propose their own ideas, lead micro-projects, and aim to commercialize new businesses by referencing the results, technology patents, and knowledge of other departments. The reception department 21 receives these proposals, the similarity determination department 22 calculates the similarity between the proposal and existing projects and patent information, and the relationship management department 23 manages relationship management targets with high similarity. The revenue distribution department 31 then implements appropriate token distribution for existing knowledge, even when it is utilized. Thus, this system enables both career advancement and the creation of new businesses while reusing the intellectual assets accumulated within the organization.

[0076] Ultimately, if an employee participates in multiple micro-projects and makes a significant contribution, the record of that contribution will be reflected in their performance evaluation, leading to promotions, awards, and bonuses for that employee. For employees, their achievements are visualized on the server device 30 (idea management system), creating an environment where their abilities and results are constantly evaluated. This improves their motivation at work. Furthermore, when considering their career plans, both inside and outside the company, their strengths and areas of expertise become clearer, making it easier to determine the direction for their next project and future skill development. In this way, by using each functional part of this embodiment, it is possible to build a system that revitalizes micro-projects within a company while simultaneously balancing individual employee career development and performance evaluation.

[0077] Figure 12 is a diagram illustrating the flow of a use case. In Figure 12, the specific processing flow within the system within the organization described above is shown as an actor-specific flowchart. Figure 12 shows four implementing entities (actors): "System," "Project Proposer," "Project Participant," and "Human Resources Department."

[0078] First, when a project proposer submits a micro-project idea, the server device 30 (idea management system) automatically determines its similarity to existing projects. If similarity is detected, the server device 30 (idea management system) notifies the proposer, who then reviews the contents of the similar project. Once the proposer approves, the server device 30 (idea management system) registers the new project, including its derivative relationships, in a tree structure.

[0079] Next, the proposer sets the specific requirements for the project (necessary skills, implementation period, etc.) and begins recruiting participants. Project participants then apply to participate based on their skills and interests. Once their participation is approved, participants perform tasks within the project and report their progress and results to the server device 30 (idea management system) as they occur.

[0080] As the project progresses, the server device 30 (idea management system) calculates revenue based on each participant's contribution and the similarity to the original project. The calculated revenue is automatically distributed to the participants and returned to the original project, and all transactions are recorded on the blockchain.

[0081] Finally, the human resources department reviews these activity records and incorporates them into each employee's performance evaluation. In this way, it becomes possible to manage and operate the project in a consistent flow, from idea proposal to implementation and evaluation, with the server device 30 (idea management system) and each actor working together.

[0082] This flowchart visually demonstrates that the server device 30 (idea management system) in this embodiment functions not only for idea management but also as a comprehensive system encompassing project implementation and personnel evaluation. Furthermore, it clearly distinguishes between automated processes and processes requiring human judgment and execution, allowing for a concrete understanding of how this embodiment can be implemented in practice.

[0083] As described above, by using the server device 30 (idea management system) of this embodiment, even when a large number of ideas are submitted simultaneously, the similarity determination function and the hierarchical visualization function of derived ideas allow for the understanding of the relationships between ideas without overlooking any. Furthermore, because there is a mechanism to return the revenue from derived ideas to the original ideas, the value of the original ideas used in later submitted ideas is re-evaluated, increasing the incentive for contributors to cooperate and develop ideas. In addition, since the hierarchical structure of ideas and the revenue distribution status can be seen at a glance on the UI, promising derivative paths can be efficiently explored in business development and research and development situations.

[0084] <Other Embodiments> Figure 13 shows an example of the configuration of a server device. In Figure 13, the server device 100 has a processor 101 and a memory 102. The processor 101 may be, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit). The processor 101 may include multiple processors. The memory 102 is composed of a combination of volatile memory and non-volatile memory. The memory 102 may include storage located away from the processor 101. In this case, the processor 101 may access the memory 102 via an I (Input) / O (Output) interface, which is not shown.

[0085] The server devices 10, 20, and 30 of the first to fourth embodiments can each have the configuration shown in Figure 13. The receiving units 11 and 21, the similarity determination units 12 and 22, the relationship management units 13 and 23, the display control unit 24, the revenue distribution unit 31, and the record management unit 32 of the server devices 10, 20, and 30 of the first to fourth embodiments may be realized by the processor 101 reading and executing a program stored in the memory 102. In other words, the server devices 10, 20, and 30 of the first to fourth embodiments can be realized by software. The program can be stored using various types of non-transitory computer-readable media and supplied to the server devices 10, 20, and 30. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives) and magneto-optical recording media (e.g., magneto-optical disks). Furthermore, examples of non-transitory computer-readable media include CD-ROMs (Read Only Memory), CD-Rs, and CD-R / Ws. Additionally, examples of non-transitory computer-readable media include semiconductor memory. Semiconductor memory includes, for example, mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, and RAMs (Random Access Memory). Programs may also be supplied to server devices 10, 20, and 30 by various types of transient computer-readable media. Examples of transient computer-readable media include electrical signals, optical signals, and electromagnetic waves. Transitory computer-readable media can supply programs to server devices 10, 20, and 30 via wired communication channels such as electric wires and optical fibers, or via wireless communication channels.

[0086] Alternatively, the reception units 11, 21, similarity determination units 12, 22, relationship management units 13, 23, display control unit 24, revenue distribution unit 31, and record management unit 32 of the server devices 10, 20, 30 in the first to fourth embodiments may each be implemented with dedicated hardware. Furthermore, some or all of the components of each device may be implemented by general-purpose or dedicated circuits, processors, etc., or combinations thereof. These may be configured by a single chip or by multiple chips connected via a bus. Some or all of the components of each device may be implemented by a combination of the above-mentioned circuits, etc., and programs. Furthermore, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (field-programmable gate array), quantum processor (quantum computer control chip), etc., can be used as the processor.

[0087] Furthermore, if some or all of the components of the server devices 10, 20, and 30 in the first to fourth embodiments are realized by multiple information processing devices or circuits, these multiple information processing devices or circuits may be centrally located or distributed. For example, the information processing devices or circuits may be realized in a form in which each is connected via a communication network, such as a client-server system or a cloud computing system. Also, the functions of the server devices 10, 20, and 30 in the first to fourth embodiments may be provided in SaaS (Software as a Service) format.

[0088] Although the present invention has been described above with reference to embodiments, the present invention is not limited thereto. Various modifications to the structure and details of the present invention can be made within the scope of the invention as can be understood by those skilled in the art. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0089] Each drawing is merely illustrative to illustrate one or more embodiments. Each drawing may be associated with one or more other embodiments, rather than being associated with only one specific embodiment. As those skilled in the art will understand, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings, for example, to create embodiments not explicitly shown or described. Not all features or steps shown in any one drawing to illustrate an exemplary embodiment are necessarily required, and some features or steps may be omitted. The order of steps described in any of the drawings may be changed as appropriate.

[0090] Some or all of the above embodiments may also be described as follows, but are not limited to the following: (Note 1) A server device comprising: a receiving means for receiving a plurality of ideas including a first idea and a second idea; a determination means for determining the similarity between the first idea and the second idea; and a first management means for managing the idea pair of the first idea and the second idea as a candidate for relationship management when it is determined that the first idea and the second idea are similar. (Note 2) The server device according to Note 1, wherein the determination means comprises: a calculation means for calculating the similarity between the first idea and the second idea; and a determination processing means for determining that the first idea and the second idea are similar when the calculated similarity exceeds a predetermined threshold, and the first management means transmits a notification signal to a device associated with the submitter of the second idea of ​​the candidate for relationship management. (Note 3) The notification signal is an approval request signal asking the poster whether or not to approve making the relationship management candidate a formal relationship management target, as described in Note 2. (Note 4) The first management means manages the first idea and the second idea of ​​the relationship management candidate as a hierarchically related source idea and derived idea, respectively, as described in any one of Notes 1 to 3. (Note 5) The server device according to Note 4, comprising a display control means for displaying the hierarchical relationship. (Note 6) The server device according to Note 2, comprising a revenue distribution means for calculating a revenue distribution value to be distributed from the revenue obtained based on the second idea to the first idea, based on the revenue obtained based on the second idea and a distribution ratio according to the similarity. (Note 7) The server device according to Note 6, comprising a second management means for recording the revenue distribution on the blockchain. (Note 8) The server device described in Note 6 or 7, wherein the aforementioned multiple ideas include new business plans, service plans, product development, or research and development themes, and the aforementioned revenue includes evaluation points, tokens, or operating profits.(Note 9) An idea management method executed by a server device, comprising: receiving a plurality of ideas including a first idea and a second idea; determining the similarity between the first idea and the second idea; and, if the first idea and the second idea are similar, managing the idea pair of the first idea and the second idea as a candidate for relationship management. (Note 10) The idea management method according to Note 9, wherein the determination comprises: calculating a degree of similarity between the first idea and the second idea; and determining that the first idea and the second idea are similar if the calculated degree of similarity exceeds a predetermined threshold, and managing the candidate for relationship management comprises transmitting a notification signal to a device associated with the submitter of the second idea of ​​the candidate for relationship management. (Note 11) The idea management method according to Note 10, wherein the notification signal is an approval request signal asking the submitter whether or not to approve making the candidate for relationship management a formally managed relationship management item. (Note 12) The idea management method according to any one of Notes 9 to 11, wherein managing the candidate for relationship management includes managing the first idea and the second idea of ​​the candidate for relationship management as a hierarchically related source idea and derived idea, respectively. (Note 13) The idea management method according to Note 12, which includes displaying the hierarchical relationship. (Note 14) The idea management method according to Note 10, which includes calculating a distribution revenue value to be distributed from the revenue obtained based on the second idea to the first idea based on the revenue obtained based on the second idea and the distribution ratio according to the similarity. (Note 15) The idea management method according to Note 14, which includes recording a record of the revenue distribution on the blockchain. (Note 16) The idea management method according to Note 14 or 15, wherein the plurality of ideas include a new business plan, a service plan, a product development, or a research and development theme, and the revenue includes evaluation points, tokens, or implementation profits.(Note 17) A program that causes a server device to execute a process that includes: receiving multiple ideas, including a first idea and a second idea; determining the similarity between the first idea and the second idea; and, if the first idea and the second idea are similar, managing the idea pair of the first idea and the second idea as a candidate for relationship management. (Note 18) The program according to Note 17, wherein the determination includes: calculating the similarity between the first idea and the second idea; and determining that the first idea and the second idea are similar if the calculated similarity exceeds a predetermined threshold, and managing the candidate for relationship management includes sending a notification signal to a device associated with the submitter of the second idea of ​​the candidate for relationship management. (Note 19) The program according to Note 18, wherein the notification signal is an approval request signal asking the submitter whether or not to approve making the candidate for relationship management a formally managed relationship management item. (Note 20) The program according to any one of Notes 17 to 19, wherein managing the candidate for relationship management includes managing the first idea and the second idea of ​​the candidate for relationship management as a hierarchically related source idea and derived idea, respectively. (Note 21) The program according to Note 20, wherein the process includes displaying the hierarchical relationship. (Note 22) The program according to Note 18, wherein the process includes calculating a distribution revenue value to be distributed from the revenue obtained based on the second idea to the first idea, based on the revenue obtained based on the second idea and the distribution ratio according to the similarity. (Note 23) The program according to Note 22, wherein the process includes recording a record of the revenue distribution on the blockchain. (Note 24) The program according to Note 22 or 23, wherein the plurality of ideas include new business plans, service plans, product development, or research and development themes, and the revenue includes evaluation points, tokens, or profits from implementation.

[0091] 1 System 10 Server device 11 Reception unit 12 Similarity determination unit 13 Relationship management unit (1st management unit) 20 Server device 21 Reception unit 22 Similarity determination unit 22A Similarity calculation unit 22B Determination processing unit 23 Relationship management unit (1st management unit) 24 Display control unit 30 Server device 31 Revenue distribution unit 32 Record management unit (2nd management unit) 40 User terminal 50 Blockchain node 60 Database

Claims

1. A server device comprising: a receiving means for receiving multiple ideas, including a first idea and a second idea; a determination means for determining the similarity between the first idea and the second idea; and a first management means for managing the idea pair of the first idea and the second idea as a candidate for relationship management when it is determined that the first idea and the second idea are similar.

2. The server device according to claim 1, wherein the determination means comprises: a calculation means for calculating the similarity between the first idea and the second idea; and a determination processing means for determining that the first idea and the second idea are similar if the calculated similarity exceeds a predetermined threshold, and the first management means transmits a notification signal to a device associated with the poster of the second idea of ​​the relationship management candidate.

3. The server device according to claim 2, wherein the notification signal is an approval request signal asking the poster whether or not to approve designating the candidate for relationship management as a formal relationship management target.

4. The server device according to any one of claims 1 to 3, wherein the first management means manages the first idea and the second idea of ​​the relationship management candidate as a hierarchically related source idea and derived destination idea, respectively.

5. The server device according to claim 4, comprising display control means for displaying the hierarchical relationship.

6. The server device according to claim 2, comprising revenue distribution means for calculating a revenue distribution value to be distributed from the revenue obtained based on the second idea to the first idea, based on the revenue obtained based on the second idea and a distribution ratio according to the similarity.

7. The server device according to claim 6, comprising a second management means for recording records of the distribution of the aforementioned revenue on a blockchain.

8. The server device according to claim 6 or 7, wherein the plurality of ideas include new business plans, service plans, product development, or research and development themes, and the revenue includes evaluation points, tokens, or profits from implementation.

9. An idea management method executed by a server device, comprising: receiving a plurality of ideas including a first idea and a second idea; determining the similarity between the first idea and the second idea; and, if the first idea and the second idea are similar, managing the idea pair of the first idea and the second idea as a candidate for relationship management.

10. The idea management method according to claim 9, wherein the determination includes calculating a similarity between the first idea and the second idea, and determining that the first idea and the second idea are similar if the calculated similarity exceeds a predetermined threshold, and the management of the relationship management candidate includes transmitting a notification signal to a device associated with the contributor of the second idea of ​​the relationship management candidate.

11. The idea management method according to claim 10, wherein the notification signal is an approval request signal asking the poster whether or not to approve designating the candidate for relationship management as a formal relationship management item.

12. The idea management method according to any one of claims 9 to 11, wherein managing the candidate for relation management includes managing the first idea and the second idea of ​​the candidate for relation management as a hierarchically related source idea and a derived idea, respectively.

13. The idea management method according to claim 12, further comprising displaying the hierarchical relationships.

14. The idea management method according to claim 10, comprising calculating a revenue distribution value to be distributed to the first idea from the revenue obtained based on the second idea, based on the revenue obtained based on the second idea and the distribution ratio according to the similarity.

15. A program that causes a server device to execute a process that includes: receiving multiple ideas, including a first idea and a second idea; determining the similarity between the first idea and the second idea; and, if the first idea and the second idea are similar, managing the idea pair of the first idea and the second idea as a candidate for relationship management.

16. The program according to claim 15, wherein the determination includes calculating a similarity between the first idea and the second idea, and determining that the first idea and the second idea are similar if the calculated similarity exceeds a predetermined threshold, and the management of the relationship management candidate includes transmitting a notification signal to a device associated with the contributor of the second idea of ​​the relationship management candidate.

17. The program according to claim 16, wherein the notification signal is an approval request signal asking the poster whether or not to approve designating the candidate for relationship management as a formal relationship management target.

18. The program according to any one of claims 15 to 17, wherein managing the candidate for relation management includes managing the first idea and the second idea of ​​the candidate for relation management as a hierarchically related source idea and a derived idea, respectively.

19. The program according to claim 18, wherein the processing includes displaying the hierarchical relationship.

20. The program according to claim 16, wherein the process includes calculating a distribution revenue value to be distributed from the revenue obtained based on the second idea to the first idea, based on the revenue obtained based on the second idea and the distribution ratio according to the similarity.

Images