JP7100437B2 - Computer program, judgment device and judgment method - Google Patents

Description

The present invention relates to a computer program or the like for determining data reference authority.

Conventionally, a distribution system for distributing a business model has been proposed (Patent Document 1). In addition, a system for commercializing a draft business model has been proposed (Patent Document 2). Further, a system that supports the design of a business model has been proposed (Patent Document 3).

Japanese Unexamined Patent Publication No. 2002-7778 Japanese Unexamined Patent Publication No. 2002-169881 Japanese Unexamined Patent Publication No. 2008-276653

However, in the prior art, the technical elements constituting the business model are not systematized. Therefore, it is difficult to design a new business model by combining known technical elements and new technical elements, or to update an existing business model by incorporating new technical elements. Furthermore, when designing a new business model or updating an existing business model, it is difficult to properly control the reference authority of data related to the business model.

The present invention has been made in view of such circumstances. The purpose is to systematize the structure of the business model and provide a computer program or the like that controls the reference authority for each element constituting the systematized business model.

The computer program according to the present invention receives information on the management resources that can be provided from the recruitment terminal of the recruiter, determines whether or not the first reference authority corresponding to the received management resources is set, and determines whether or not the first reference authority is set. 1 When it is determined that the reference authority is not set, the first default authority is acquired, the acquired first default authority is transmitted to the recruitment terminal, and the recruitment terminal is the first with respect to the first default authority. The instruction is received, the first reference authority is created from the first default authority based on the received first instruction, and the created first reference authority is stored in association with the identification information of the management resource information. Then, from the applicant's application terminal, the registration request of the provision value definition that uses the management resource is received, the second default authority for the information of the provision value definition is acquired, and the second default acquired to the application terminal. The authority is transmitted, the information of the provided value definition and the second instruction for the second default authority are received from the application terminal, the received information of the provided value definition is stored, and the received second instruction is received. The second reference authority is created from the second default authority based on the above, and the created second reference authority is stored in association with the identification information of the information of the provided value definition , and the provided value is stored from the application terminal. If you receive information about a value-providing scheme that includes the products, services, functions, or processes required to construct a definition and requires the management resources to build, it is included in the acquired value-providing scheme. It is determined whether or not the third reference authority corresponding to the product, service, function, or process is set, and if it is determined that the third reference authority is not set, the third default authority is acquired and the above is described. The acquired third default authority is transmitted to the application terminal, the third instruction for the third default authority is received from the application terminal, and based on the received third instruction, the third default authority is changed to the third. 3 Create a reference authority, store the created third reference authority in association with the identification information of the product, service, function, or process included in the value provision scheme, and store the management resource information and the value provision scheme . The correspondence relationship with the information of the above and the correspondence relationship between the information of the provision value definition and the information of the value provision scheme are memorized, and the information of the provision value definition and the provision value definition are configured from the recruitment terminal. A business that links information on a value provision scheme that includes products, services, functions, or processes required for the purpose with information on management resources required to build the value provision scheme. When a request for information is received, the business information is acquired, and the second reference authority for the information of each provided value definition, the third reference authority for the information of each value provision scheme, and the first reference authority for the information of each management resource. Is acquired, it is determined whether or not to output the information of each provision value definition based on the acquired second reference authority, and the information of each value provision scheme is output based on the acquired third reference authority. It is characterized in that a computer is made to perform a process of determining whether or not to output the information of each management resource based on the acquired first reference authority.

In the present invention, it is possible to control the reference authority for each element constituting the systematic business model.

It is explanatory drawing of the configuration example of an open innovation system. It is a block diagram which shows the hardware configuration example of a main server. It is a block diagram which shows the hardware configuration example of a terminal. It is explanatory drawing which shows the hierarchical structure of a business model. It is explanatory drawing which shows the display example of a business model. It is a flowchart which shows the procedure of the idea solicitation type. It is a flowchart which shows the procedure of management resource procurement type. It is explanatory drawing which shows an example of the database which a database server stores. It is explanatory drawing which shows the example of the user master DB. It is explanatory drawing which shows the example of the department master DB. It is explanatory drawing which shows the example of the company master DB. It is explanatory drawing which shows the example of the company business DB. It is explanatory drawing which shows the example of the management resource DB. It is explanatory drawing which shows the example of the resource classification master DB. It is explanatory drawing which shows the example of the tree DB. It is explanatory drawing which shows the example of a node DB. It is explanatory drawing which shows the example of the type code master DB. It is explanatory drawing which shows the example of a node connection DB. It is explanatory drawing which shows the example of the attribute definition master DB. It is explanatory drawing which shows the example of the BM attribute DB. It is explanatory drawing which shows the example of PS attribute DB. It is explanatory drawing which shows the example of the FP attribute DB. It is explanatory drawing which shows the example of the CT technique attribute DB. It is explanatory drawing which shows the example of the idea solicitation DB. It is explanatory drawing which shows the example of the idea application company DB. It is explanatory drawing which shows the example of the resource solicitation DB. It is explanatory drawing which shows the example of the company list DB. It is explanatory drawing which shows the example of the group DB. It is explanatory drawing which shows the example of the access authority DB. It is explanatory drawing which shows the example of the BM authority DB. It is explanatory drawing which shows the example of the PS authority DB. It is explanatory drawing which shows the example of the FP authority DB. It is explanatory drawing which shows the example of the CT authority DB. It is explanatory drawing which shows the example of the management resource authority DB. It is explanatory drawing which shows the example of the BM default DB. It is explanatory drawing which shows the example of PS default DB. It is explanatory drawing which shows the example of the FP default DB. It is explanatory drawing which shows the example of CT default DB. It is explanatory drawing which shows the example of the management resource default DB. It is a flowchart which shows the procedure example of entry processing. It is a flowchart which shows the procedure example of the recruitment information input processing. It is a flowchart which shows the procedure example of a node attribute output processing. It is a flowchart which shows the procedure example of application information input processing. It is a flowchart which shows the procedure example of the primary selection process. Detailed contents It is a flowchart which shows the procedure example of screen output processing. It is a flowchart which shows the procedure example of the selection acceptance processing. It is a flowchart which shows the procedure example of a contract completion process. It is explanatory drawing which shows an example of the basic information input screen. It is explanatory drawing which shows an example of the business information input screen. It is explanatory drawing which shows an example of a tree creation screen. It is explanatory drawing which shows an example of the business model attribute input screen. It is explanatory drawing which shows an example of a function / process input screen. It is explanatory drawing which shows an example of the recruitment information input screen. It is explanatory drawing which shows an example of the application company list screen. It is explanatory drawing which shows an example of the detailed content screen. It is a flowchart which shows the procedure example of the search registration process. It is a flowchart which shows the procedure example of a long list creation process. It is a flowchart which shows the procedure example of a short list creation process. It is a flowchart which shows the procedure example of a proposal making process. It is a flowchart which shows the procedure example of a final selection process. It is explanatory drawing which shows an example of the resource recruitment requirement input screen. It is explanatory drawing which shows an example of the short list creation screen.

Hereinafter, embodiments will be described with reference to the drawings.

FIG. 1 is an explanatory diagram of a configuration example of the open innovation system 100. The open innovation system 100 includes a progress management system 110, as well as a company 120 and an individual inventor 130 participating in the open innovation system 100.

The progress management system 110 includes a main server (determination device) 1, a database server 2, a firewall 3, an operator terminal 4, and a system administrator terminal 5. These are communicably connected to each other by the local network N1. The company 120 and the individual inventor 130 each have a terminal 6 for accessing the progress management system 110. The progress management system 110 can communicate with the terminal 6 of the company 120 and the individual inventor 130 via the local network N1, the firewall 3, and the network N. FIG. 1 shows, but is not limited to, only two companies 120 and one individual inventor 140. The number of companies 120 may be 3 or more, and the number of individual inventors 130 may be 2 or more. The terminals 6 possessed by the company 120 and the individual inventor 130 are not limited to one, and may be two or more.

FIG. 2 is a block diagram showing a hardware configuration example of the main server 1. The main server 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a large-capacity storage unit 14, a communication unit 15, and a reading unit 16. Each configuration is connected by bus B.

The CPU 11 controls each part of the hardware according to the control program (computer program) 1P stored in the ROM 12. The RAM 13 is, for example, a SRAM (Static RAM), a DRAM (Dynamic RAM), or a flash memory. The RAM 13 temporarily stores data generated when the program is executed by the CPU 11.

The large-capacity storage unit 14 is, for example, a hard disk or an SSD (Solid State Drive). The large-capacity storage unit 14 stores various data. The control program 1P may be stored in the large-capacity storage unit 14. The communication unit 15 communicates with the database server 2, the firewall 3, the operator's terminal 4, and the system administrator's terminal 5 via the local network N1. The communication unit 15 communicates with the company 120, the terminal 6 of the individual inventor, and other computers via the local network N1, the firewall 3, and the network N. The reading unit 16 reads a portable storage medium 1a including a CD (Compact Disc) -ROM and a DVD (Digital Versaille Disc) -ROM. The CPU 11 may read the control program 1P from the portable storage medium 1a via the reading unit 16 and store it in the large-capacity storage unit 14. Further, the CPU 11 may download the control program 1P from another computer via the local network N1 or the like and store it in the large-capacity storage unit 14. Furthermore, the CPU 11 may read the control program 1P from the semiconductor memory 1b.

FIG. 3 is a block diagram showing a hardware configuration example of the terminal 6. The terminal 6 includes a CPU 61, a ROM 62, a RAM 63, a communication unit 64, an input unit 65, a display unit 66, a large capacity storage unit 67, and a reading unit 68. Each configuration is connected by bus B.

The CPU 61 controls each part of the hardware according to the control program 6P stored in the ROM 62. RAM 63 is, for example, SRAM, DRAM or flash memory. The RAM 63 temporarily stores data generated when the program is executed by the CPU 61.

The communication unit 64 communicates with the main server 1 and other computers via the network N. The input unit 65 receives data related to the business model input by the user via the keyboard or mouse. The display unit 66 includes an image display device such as a liquid crystal display panel. Like the touch panel display, the input unit 65 and the display unit 66 may be integrated. The large-capacity storage unit 67 is, for example, a hard disk or an SSD. The large-capacity storage unit 67 stores various data. The control program 6P may be stored in the large-capacity storage unit 67. The reading unit 68 reads a portable storage medium 6a including a CD-ROM and a DVD-ROM. The CPU 61 may read the control program 6P from the portable storage medium 6a via the reading unit 68 and store it in the large-capacity storage unit 67. Further, the CPU 61 may download the control program 6P from another computer via the network N or the like and store it in the large-capacity storage unit 67. Furthermore, the CPU 61 may read the control program 6P from the semiconductor memory 6b. The terminal 4 of the operator and the terminal 5 of the system administrator have the same configuration as the terminal 6.

In this embodiment, the business model is represented by a three-layer structure. FIG. 4 is an explanatory diagram showing a hierarchical structure of a business model. The upper layer of the third layer is the business model layer NT that defines the business concept such as the value provided to the customer by the business model (provided value definition), the customer, and the product service. Below the business model hierarchy NT is a process / function hierarchy NM (value provision scheme) in which elements constituting a mechanism for providing value to customers are arranged. In the process / function hierarchy NM, the components (value provision system) of the business model such as products / services, functions / processes, and value chains are arranged. The lower level of the process / function hierarchy NM is the management resource hierarchy NB. The management resource hierarchy NB is not only the source of individual ideas, know-how, intellectual property such as patents, and unique technologies, but also the source of the strength of the business model. Arrange the management resource elements in association with each element of the process / functional hierarchy NM.

FIG. 5 is an explanatory diagram showing a display example of the business model. In FIG. 5, one business model is represented by one tree. That is, one node NT1 is arranged in the business model hierarchy NT. Four nodes NM1 to NM4 are arranged in the process / function hierarchy NM. Nodes NM1 to NM4 are subordinate to node NT1. Therefore, each of the nodes NM1 to NM4 is connected to the node NT1 by an edge. One node NB1 is arranged in the management resource hierarchy NB. Node NB1 is a subordinate of node NM1. Therefore, the node NB1 is connected to the node NM1 by an edge.

The business model shown in FIG. 5 is a call center inbound business consignment business (node NT1). Four functions / processes are shown as the processes / functional hierarchies required for the business model. The four functions / processes are reception processing (node NM1), identity verification inquiry content confirmation (node NM2), response / response (node NM3), and response / post-processing work (node NM4).

PBX / IVR / CTI (node NB1) is shown as a management resource corresponding to the reception process (node NM1). Management resources corresponding to identity verification / inquiry content confirmation (node NM2), response / response (node NM3), and response post-processing work (node NM4) are not described. PBX is an abbreviation for Private Branch eXchange (private branch exchange). IVR is an abbreviation for Interactive Voice Response. IVR is the name of the function, but the device that provides the IVR function may be simply described as IVR. CTI is an abbreviation for Computer Telephony Integration. Like IVR, CTI is the name of the function, but the device that provides the CTI function may be simply referred to as CTI.

As described above, in the present embodiment, since the business model is expressed in a three-layer structure, it is possible to systematically handle all businesses. If it is difficult to express the business model in a simple three-layer structure, such as when there are many elements that make up the business model, or when advanced technology that is a stack of many elemental technologies is used as an element. , Process / function hierarchy NM or management resource hierarchy NB may be nested. Here, the nested structure is a case where the nodes included in the process / functional hierarchy NM or the management resource hierarchy NB represent one tree having a hierarchical structure. When constructing a new business model using an existing business model, the existing business model becomes one node included in the process / functional hierarchy NM or the management resource hierarchy NB. A business model expressed in a three-tiered structure is called a three-tiered model.

Next, the development of a new business by the open innovation system 100 will be described. Here, the process from a plurality of companies forming a collaborative relationship to the development of a new business by the open innovation system 100 will be described. We will explain the process leading up to the development of a new business in two patterns. In the following explanation, in pattern 1, the company calling for cooperation is referred to as a recruiting company. A company that responds to a call for collaboration is called an applicant company. In pattern 2, a company calling for collaboration is called a search company. A company that responds to a call for collaboration is called a proposing company. In pattern 1, the recruiting company solicits business ideas that utilize its own management resources, and the recruiting company commercializes the business ideas gathered from the applicant companies. In pattern 2, a search company having a business model concept solicits the technology and management resources necessary for realization, and completes the business model with the technology and management resources gathered from the proposing company. The exploration company starts a business based on the completed business model. Hereinafter, the commercialization process according to pattern 1 is referred to as an idea solicitation type business creation process or simply an idea solicitation type. Hereinafter, the commercialization process according to pattern 2 is referred to as a management resource procurement type business creation process or simply a management resource procurement type.

FIG. 6 is a flowchart showing an idea solicitation type procedure. The master information is registered in the open innovation system 100 by the companies (recruiting companies and applicant companies) participating in the open innovation system 100 (step S141). In addition to the profile information posted on the homepage, etc., the master information includes an outline of the existing business model and information on management resources that are expected to be provided for collaboration. The recruiting company registers the recruitment requirements for business model idea recruitment in the open innovation system 100 (step S142). The recruitment requirements include recruitment themes, preconditions for recruitment, idea evaluation criteria, and management resources that are expected to be provided. Companies that are considering collaborating with other companies will refer to the application guidelines through the Open Innovation System 100. At this time, it is possible to refer only to the outline of the recruitment requirements by controlling the authority by the open innovation system 100. According to the application guidelines, the application information of the business model idea is registered in the open innovation system 100 by the applicant company (step S143). Regarding the reference of application information by the recruiting company, the authority is controlled by the open innovation system 100, and the recruiting company can refer to the outline of the idea. The applicant company registers the business model idea in the above-mentioned three-layer model. The recruiting company evaluates the submitted business model idea based on the evaluation criteria. The recruiting company selects an applicant company that has applied for an excellent business model idea (step S144). The recruiting company presents the proposal preparation procedure to the selected applicant company (selected company) and requests the preparation of the proposal. The request can be made via the open innovation system 100. The selected company prepares and submits a proposal based on the proposal preparation procedure (step S145). The proposal can be submitted via the open innovation system 100. At this point, the selected company refines and brushes up the business model idea registered in the system in step 3 to complete it. The work can be performed on the open innovation system 100. Among the selected companies, the company (participating company) that submitted the proposal gives a presentation based on the proposal to the recruiting company (step S146). The recruiting company evaluates the business model ideas of the participating companies again based on the contents of the proposal and the presentation, and selects a candidate of the company to collaborate with from the participating companies (step S147). The recruiting company determines the scheme of collaboration and the conditions for collaborating with the selected company (candidate company), and makes a contract (step S148). The recruiting company and the collaborative company (candidate company that has signed a contract) promote the business model development and its commercialization by the collaborative (step S149).

FIG. 7 is a flowchart showing a management resource procurement type procedure. The master information is registered in the open innovation system 100 by the companies (searching companies and proposing companies) participating in the open innovation system 100 (step S151). The process is the same as in step S141 of the idea solicitation type. The recruitment requirements are registered in the open innovation system 100 by the search company (step S152). The recruitment requirements describe the search conditions as detailed as possible, such as technical issues and technical requirements such as required specifications and accuracy, for the management resources to be searched. Enter search keywords and search formulas that can be used for the search in the search conditions. The exploration company registers the business model idea at this point in the open innovation system 100. Regarding the business model idea registered here, it is assumed that the management resource element currently held and the management resource element (missing piece) to be searched for are distinguishable. The open innovation system 100 extracts companies that match the registered search conditions based on the registered search conditions. The open innovation system 100 creates a list and a long list that summarizes the extracted companies into one (step S153). At this point, the database is searched under loose conditions. For example, search by a search expression that combines multiple keywords with the OR operator. If a search expression that combines multiple keywords with the AND operator is specified, the search is performed using a search expression that uses one or two keywords. Although the search is performed under loose conditions, if the number of hits is large, a refined search is performed. Therefore, a company that firmly describes the management resources registered in step S151 is likely to be a hit. The search company selects a company requesting a proposal from the companies listed in the long list (step S154). The selection here is premised on manual operation. In selecting, in addition to the viewpoint of simply narrowing down to companies that more satisfy the search conditions, factors such as corporate culture and human resources that the search company considers important in promoting collaboration may be taken into consideration. A list of companies that narrows down the companies included in the long list is called a short list. The search company should consider the profile of the company in the short list, management resources, etc., and add the request for proposal and the format of the proposal to the recruitment requirements to the RFP (Request for Proposal). create. The search company presents the RFP to the company included in the short list and confirms the intention to propose (step S155). The confirmation can be performed via the open innovation system 100. At this time, it is possible to change the reference authority of the recruitment guidelines to the company that has indicated the intention to make a proposal so that it can refer to more detailed contents. The company (proposal company) that has shown the intention to make a proposal prepares a proposal according to the RFP and submits it to the search company (step S156). The proposal can be submitted via the open innovation system 100. The search company makes the final selection of the proposal company based on the contents of the proposal and the results of interviews. The search company negotiates the conditions and the like when collaborating while narrowing down the candidate companies (step S157). The search company and the search company determine the scheme of collaboration, the conditions for collaboration, and the like, and conclude a contract (step S158). The exploration company and the exploration company promote the business model development and its commercialization through collaboration (step S159).

The open innovation system 100 supports the progress of idea solicitation-type and management resource procurement-type processes. The open innovation system 100 is a system that matches companies looking for a collaborative partner by the above process. When matching companies to each other, the frontage may be widened at first, and many companies may refer to data related to matching. As the process progresses, companies are narrowed down. Therefore, it is necessary to control the authority according to the progress of the process.

The need for privilege control will be explained in detail. In the management resource procurement type and the idea solicitation type, there are multiple companies (applicant companies) applying for one company (recruiting company) calling for collaboration. The recruiting company concludes a contract with one of the applicant companies. The recruiting company does not want to disclose business model information or management resource information to all applicant companies from the beginning so that the purpose of the search can be understood. There is a risk that the strategic intent of what you are trying to do will be leaked. In order to avoid this risk, it is inevitable that as the candidate companies are narrowed down, disclosure will be made only to the narrowed down candidate companies. Then, an NDA (Non-disclosure agreement) will be concluded with the companies that have been selected for the final selection, and final negotiations will be held for the transaction. On the other hand, even though the applicant company has not been selected, it is not possible to expose all the technical materials and know-how from the beginning. Therefore, it is necessary to control the information to be disclosed according to the progress of selection. The above is the background that both recruiting companies and applicant companies need to control detailed information disclosure.

Next, the data handled by the open innovation system 100 and the processing using the data will be described. Some of the databases described below have outlines (columns) and details (columns) for the same name data. By summarizing the data to be widely disclosed and narrowing down the companies that disclose the details, it is possible to prevent unnecessary diffusion of important data in business operations. In the following description, a company is an example of a company.

The database stored in the database server 2 will be described. FIG. 8 is an explanatory diagram showing an example of a database stored in the database server 2. The database server 2 includes a user master DB (DataBase) 21, a department master DB 22, a company master DB 23, a company business DB 24, a management resource DB 25, a resource classification master DB 26, a tree DB 27, a node DB 28, a type code master DB 29, a node connection DB 30, and attributes. The definition master DB 31, BM attribute DB 32, PS attribute DB 33, FP attribute DB 34, CT technology attribute DB 35, idea solicitation DB 36, idea application company DB 37, resource solicitation DB 38, and company list DB 39 are stored. As a database used when controlling access authority, the database server 2 further includes group DB (group information) 40, access authority DB41, BM authority DB42, PS authority DB43, FP authority DB44, CT authority DB45, and management resource authority DB46. , BM default DB47, PS default DB48, FP default DB49, CT default DB50, and management resource default DB51 are stored.

FIG. 9 is an explanatory diagram showing an example of the user master DB 21. The user master DB 21 is a database that stores basic user information. The user master DB 21 includes a user ID column, a name column, an e-mail column, an affiliation ID column, and a type column. The user ID column stores a user ID, which is an ID that can uniquely identify a user. The name column stores the user's name. The email string stores the user's email address. The affiliation ID column stores the ID of the department to which the user belongs. The type column stores the user type. The type is, for example, a user, an operation manager, or a system administrator. The authority to the database differs depending on the type of user. The user is restricted from referencing and editing data other than the data about himself / herself and the data of the organization and group to which he / she belongs. The operation manager can refer to and edit all DBs except the master DB. The operation manager can refer to the master DB, but cannot edit it. The system administrator can refer to and edit all DBs.

FIG. 10 is an explanatory diagram showing an example of the department master DB 22. The department master DB 22 is a database that stores basic information of the department. A department is an organization that belongs to a company (company). The department master DB 22 includes a department ID column, a department name column, and a company ID column. The department ID column stores a value that can uniquely identify the department. The department ID is a unique value through multiple companies (companies). For example, a company ID that can uniquely identify a company is included as a part of the department ID. The department name column stores the name of the department. The company ID column stores the company ID of the company to which the department belongs.

FIG. 11 is an explanatory diagram showing an example of the company master DB 23. The company master DB 23 is a database that stores basic company information. The company master DB23 has a company ID column, a name column, a URL column, a head office address column, a representative column, an establishment date column, a capital column, a sales column, a profit column, a settlement period column, an employee number column, and an industry. Includes industry column. The company ID column stores a company ID that can uniquely identify a company. The name column stores the name of the company. The URL column stores the URL (Uniform Resource Locator) of the Internet homepage related to the company. The head office address column stores the address of the company's head office location. The representative line stores the names of company representatives, such as representative directors. The date of establishment column remembers the date when the company was established. The capital column stores the amount of capital of the company. The sales column stores the amount of sales of the company. The profit column stores the profit amount of the company. The profit column includes the operating profit column, the ordinary profit column, and the net profit column. The operating profit column stores the amount of operating profit of the company. The recurring profit column stores the amount of recurring profit of the company. The net profit column stores the amount of the company's net profit. The closing period column stores the closing period of the company. The employee number column stores the number of employees in the company. The industry / industry column memorizes the industry / industry to which the company belongs.

FIG. 12 is an explanatory diagram showing an example of the company business DB 24. The company business DB 24 is a database that stores basic information about the business performed by the company. The company business DB24 has a company ID column, a business ID column, a name column, a value column to be provided, a main product / service column, a main customer column, a main customer column, a main supplier column, a competitor column, a base column, And the tree ID column. The company ID column stores the company ID. The business ID column stores a business ID that can uniquely identify a business. The name column stores the name of the business. The value column provided stores the value that the company provides to the customer through its business. The main product / service column stores the main products / services in the business. The main customer column remembers the main customers of the business. The main customer line remembers the main customers in the business. The main supplier line remembers the main suppliers in the business. The competitor column remembers the competitors in the business. The base row remembers the bases in the business. The base line includes the research and development line, the production line, the sales line, and the distribution line. The R & D column stores information on R & D bases in the business. The production column stores information on the production base in the business. The sales column stores information on sales bases in the business. The distribution column stores information on distribution bases in the business. When the structure of the business is defined by the above-mentioned three-layer structure, the tree ID stores the tree ID of the corresponding tree. If the structure of the business is not defined in a three-tier structure, the value of the tree ID is null.

FIG. 13 is an explanatory diagram showing an example of the management resource DB 25. The management resource DB 25 is a database that stores the management resources of the company in association with the business. The management resource DB 25 includes a company ID column, a business ID column, a resource ID column, a management resource element column, a classification column, and a search keyword column. The company ID column stores the company ID of the company having the resource. The business ID column stores the business ID of the business corresponding to the resource. The resource ID column stores a resource ID that can uniquely identify a resource. The management resource element column stores the specific contents of the resource. The management resource element column includes a summary column and a detail column. The summary column stores a summary of management resource elements. The detail column stores the details of the management resource element. The classification column stores the classification of management resources. The classification column includes a classification 1 column and a classification 2 column. The classification 1 column stores the process / function to which the management resource element belongs or is associated with in the value chain. The second column of classification stores the contents of management resources selected from preset classifications. Classification 1 and classification 2 are stored as codes. The code will be described later. The searched keyword column stores keywords for management resources. When a management resource is searched by keyword, the searched keyword is the search target, so it is important to set an appropriate keyword.

FIG. 14 is an explanatory diagram showing an example of the resource classification master DB 26. The resource classification master DB 26 is a database that stores the classification of management resources in association with a code. The resource classification master DB 26 includes a classification number string, a classification name string, a sequence number string, and a classification text string. The classification number column stores a number indicating the resource classification. The classification name column stores the name of the resource classification. The sequence number column stores the display order when displaying the resource classification. The classification text string stores the contents of the classification.

FIG. 15 is an explanatory diagram showing an example of the tree DB 27. The tree DB 27 is a database that stores information on the tree that expresses the business model. The tree DB 27 includes a tree ID column, a name column, a step column, and an owner ID column. The tree ID column stores the tree ID that identifies the tree. For the tree ID, for example, the node ID of the root node of the tree is diverted. The name column stores the name of the tree. The step sequence stores the progress of the business model. For example, if you are starting a business that corresponds to your business model, remember the cutover. The owner ID column stores the user ID of the user who registered the data.

FIG. 16 is an explanatory diagram showing an example of the node DB 28. The node DB 28 is a database that stores the nodes that make up the tree. The node DB 28 includes a node ID string and a type code string. The node ID column stores a node ID that can uniquely identify a node. The type code string stores the type code indicating the node type. The type code will be described later.

FIG. 17 is an explanatory diagram showing an example of the type code master DB 29. The type code master DB 29 is a database that stores the node type and the type code string in association with each other. The type code master DB 29 includes a type column and a type code string. The type column stores the node type. The type of node is, for example, a business model, a product / service, a function / process, a core technology, or a management resource.

FIG. 18 is an explanatory diagram showing an example of the node connection DB 30. The node connection DB 30 is a database that stores connection relationships between nodes. The node connection DB 30 includes a tree ID column, a node ID column, an upper node column, a lower node column, a branch number column, and a subtree column. The tree ID column stores the tree ID of the tree including the node. The node ID column stores the node ID. The upper node column stores the node ID of the upper node. The lower node column stores the node ID of the lower node. The branch number column stores the branch number of the node. The branch number is assigned to identify multiple nodes in the same tree when they are included. In principle, only one node is included in the same tree, but it is permissible to describe the same node multiple times in the same tree for the convenience of expression and design. If there are no multiple same nodes in the same tree, the branch number stores 0. The subtree column stores whether or not the node is a node of the subtree. The subtree refers to the tree when the details of the node are represented by a tree. If the node is a node of the subtree, the subtree column stores 1. If the node is not a node in the subtree, the subtree column remembers 0.

FIG. 19 is an explanatory diagram showing an example of the attribute definition master DB 31. The attribute definition master DB 31 stores a database name or the like in which attributes are defined for each node type. The attribute definition master DB 31 includes a type code column, an attribute DB column, an authority DB column, and a default authority DB column. The type code string stores the node type code string. The attribute DB column stores the name of the database in which the attribute corresponding to the type code is defined. The authority DB column stores the name of the database that stores the access authority of the attribute. The default authority DB column stores the name of the database that stores the default access authority of the attribute.

FIG. 20 is an explanatory diagram showing an example of the BM attribute DB 32. The BM attribute DB 32 is a database that stores the attributes of the business model. The BM attribute DB 32 includes a node ID column, a name column, a registration date column, a related field / industry column, a provided value column, a customer / service column, a profit structure model column, a value providing system column, and an owner ID column. The node ID column stores the node ID. The name column stores the name of the business model. The registration date column stores the date when the business model was registered. The open field / industry column memorizes the fields and industries to which the business model is related. The value provided column stores the value provided by the business model. The customer / service column stores the customer / service targeted by the business model. The profit structure model column stores the profit structure of the business model. The value provision system column remembers how the business model provides value. The owner ID column stores the user ID of the user who registered the data. In the BM attribute DB 32, the provided value column, the customer / service column, the profit structure model column, and the value provided system column include a schematic column and a detailed column.

FIG. 21 is an explanatory diagram showing an example of the PS attribute DB 33. The PS attribute DB 33 is a database that stores the attributes of products and services. The PS attribute DB 33 includes a node ID column, a name column, a registration date column, a category / classification column, a feature / performance column, a core technology column, and an owner ID column. The node ID column stores the node ID. The name column stores the names of products and services. The registration date column stores the registration date of the data. The category / classification column stores the classification of the product or service. The feature / performance column stores the feature / performance of the product / service. The core technology column memorizes the core technologies that characterize products and services. The owner ID column stores the user ID of the user who registered the data. In the PS attribute DB 33, the feature / performance column and the core technology column include a schematic column and a detailed column. The content of the core technology column is the same as the content of the idea, which is an attribute of the core technology described later.

FIG. 22 is an explanatory diagram showing an example of the FP attribute DB 34. The FP attribute DB 34 is a database that stores the attributes of functions and processes. The FP attribute DB 34 includes a node ID column, a name column, a registration date column, a function / process classification column, a provision mechanism column, a core technology column, and an owner ID column. The node ID column stores the node ID. The name column stores the name of the function / process. The registration date column stores the registration date of the data. The function / process classification column stores the classification of the function or process. The provision mechanism column stores the mechanism for providing a function or process. The core technology column memorizes the core technologies that characterize functions and processes. The owner ID column stores the user ID of the user who registered the data. In the FP attribute DB 34, the provided mechanism column and core technology column include a schematic column and a detailed column. The content of the core technology column is the same as the content of the idea, which is an attribute of the core technology described later.

FIG. 23 is an explanatory diagram showing an example of the CT technical attribute DB 35. The CT technology attribute DB 35 is a database that stores the attributes of the core technology. The CT technical attribute DB 35 includes a node ID column, a name column, a registration date column, a classification column, an idea content column, an assumed use column, a patent status column, and an owner ID column. The node ID column stores the node ID. The name column stores the name of the core technology. The registration date column stores the registration date of the data. The classification column stores known or new classifications. The idea content column memorizes the content of the idea that is the core of the core technology. The assumed use column stores the assumed use of the core technology. The patent status column stores the status of the patent. The patent status memorizes, for example, unapplied, pending, pending application, applied, awaiting examination, intermediate response, acquired rights, abandoned, and the like. The owner ID column stores the user ID of the user who registered the data. In the CT technique attribute DB 35, the content column of the idea includes a summary column and a detail column.

FIG. 24 is an explanatory diagram showing an example of the idea solicitation DB 36. The idea solicitation DB 36 is a database that stores the contents of the idea solicitation in the idea solicitation type process. The idea solicitation DB 36 includes an idea solicitation ID column, a node ID column, a solicitor ID column, a theme column, a precondition column, an evaluation standard column, a resource ID column, a step column, and an owner ID column. The idea solicitation ID column stores an idea solicitation ID that can uniquely identify the idea solicitation. The node ID column stores node IDs corresponding to functions / processes, management resources, etc. that should be included in the idea. The recruiter ID column stores the company ID of the recruiting company. The theme column remembers the theme of the recruitment. The prerequisite column stores the prerequisites for recruitment. The evaluation criteria column memorizes the criteria for evaluating the submitted ideas. The resource ID column stores the resource ID of the management resource to be provided by the recruiting company. The step sequence stores the progress of the recruitment process. The owner ID column stores the user ID of the user who registered the data. Multiple business model proposals are proposed according to the recruitment theme. These are associated with the idea solicitation ID

FIG. 25 is an explanatory diagram showing an example of the idea application company DB 37. The idea application company DB37 stores the company that applied for the idea solicitation. The idea application company DB 37 includes an idea solicitation ID column, an applicant ID column, a node ID column, a selection result column, and an owner ID column. The idea solicitation ID column stores the idea solicitation ID. The applicant ID column stores the company ID of the company that applied. The node ID column stores the node ID of the root node of the tree corresponding to the submitted idea. The selection result column stores the selection result. The owner ID column stores the user ID of the user who registered the data.

FIG. 26 is an explanatory diagram showing an example of the resource solicitation DB 38. The resource solicitation DB 38 is a database that stores the contents of the management resource solicitation in the management resource procurement type process. The resource solicitation DB 38 includes a resource solicitation ID column, a node ID column, a solicitor ID column, a target ID column, a search condition column, a keyword column, a step column, and an owner ID column. The resource solicitation ID column stores a resource solicitation ID that can uniquely identify the resource solicitation. The node ID column stores the node ID corresponding to the business model in which the recruited resource is used. The recruiter ID column stores the company ID of the recruiting company. The target ID column stores the node ID of the node that is the target of resource solicitation among the nodes constituting the business model. The search condition column stores the search conditions when listing the companies that consult the application. As for the search condition, the description content is analyzed by parsing etc., and a search formula is established based on the analysis result. Perform a search using the established search formula. The keyword column stores the keywords used when listing the companies that consult the application. Keywords are used as they are for searches targeting non-search keywords. The step sequence stores the progress of the recruitment process. The owner ID column stores the user ID of the user who registered the data.

FIG. 27 is an explanatory diagram showing an example of the company list DB 39. The company list DB 39 is a database that stores companies (companies extracted as a long list) that consult for applications for resource solicitation. The company list DB 39 includes a resource solicitation ID column, a company ID column, a short column, and a selection result column. The resource solicitation ID column stores the resource solicitation ID. The company ID column stores the company IDs of the listed companies. The short column remembers whether each company was selected for the short list. For example, in the case of a company selected in the short list, 1 is stored in the short column. In the case of a company not selected in the short list, 0 is stored in the short column. The selection result column stores the selection results of each company. In the selection result column, for example, the selection results after the short list are stored. RFP is stored in the selection result column of the company that requested the proposal but did not submit the proposal. After submitting the proposal, the interview / negotiation is memorized in the selection result column of the company that led to the interview and contract negotiation. After the interview and contract negotiation, the contract conclusion is memorized in the selection result column of the company that has reached the contract conclusion.

FIG. 28 is an explanatory diagram showing an example of the group DB 40. The group DB 40 is a database that stores groups to which access authority is granted. The group DB 40 includes a group ID column, a company ID column, a department ID column, and a user ID column. The group ID column stores a group ID that can uniquely identify the group. The company ID column stores the company ID of the company to be granted to the entire company, that is, when the authority is granted to all those belonging to the company. The department ID column stores the department ID of the department to be granted when the authority is granted for each department. The user ID column stores the user ID of the user to be granted when the authority is granted for each user.

FIG. 29 is an explanatory diagram showing an example of the access authority DB 41. The access authority DB 41 is a database that stores the access authority for each node. The access authority DB 41 includes a node ID column, a resource solicitation ID column, an idea solicitation ID column, a group ID column, and an owner ID column. The node ID column stores the node ID of the node for which the authority is set. The resource solicitation ID column stores the resource solicitation ID. The idea solicitation ID column stores the idea solicitation ID. The group ID column stores the group ID of the group to which the authority is granted. The owner ID column stores the user ID of the user who registered the data. Only one of the resource solicitation ID column and the idea solicitation ID column stores a value, and the other is blank or NULL. The same applies to the following authority DB.

FIG. 30 is an explanatory diagram showing an example of the BM authority DB 42. The BM authority DB 42 is a database that stores the authority of the business model attribute. The BM authority DB 42 includes a node ID column, a resource solicitation ID column, an idea solicitation ID column, a name column, a related field / industry column, a provided value column, a customer / service column, a profit structure model column, and a value providing system column. The node ID column stores the node ID. The resource solicitation ID column stores the resource solicitation ID. The idea solicitation ID column stores the idea solicitation ID. The name column stores the reference authority for the name. The open field / industry column remembers the reference authority for related fields / industries. The offer value column stores the reference authority for the offer value. The customer / service column stores the reference authority for the customer / service. The revenue structure model column stores reference authority to the revenue structure model. The value providing system column stores the reference authority to the value providing system. In the BM authority DB 42, the provision value column, the customer / service column, the profit structure model column, and the value provision system column include a summary column and a detail column.

FIG. 31 is an explanatory diagram showing an example of the PS authority DB 43. The PS authority DB 43 is a database that stores reference authority for product / service attributes. The PS authority DB 43 includes a node ID column, a resource solicitation ID column, an idea solicitation ID column, a name column, a category / classification column, a feature / performance column, and a core technology column. The node ID column stores the node ID. The resource solicitation ID column stores the resource solicitation ID. The idea solicitation ID column stores the idea solicitation ID. The name column stores the reference authority for the name. The category / classification column stores the reference authority for the classification. The feature / performance column stores the reference authority for the feature / performance. The core technology column stores the reference authority for the core technology. In the PS authority DB 43, the feature / performance column and the core technology column include a summary column and a detail column.

FIG. 32 is an explanatory diagram showing an example of the FP authority DB 44. The FP authority DB 44 is a database that stores reference authority for function / process attributes. The FP authority DB 44 includes a node ID column, a resource solicitation ID column, an idea solicitation ID column, a name column, a function / process classification column, a provision mechanism column, and a core technology column. The node ID column stores the node ID. The resource solicitation ID column stores the resource solicitation ID. The idea solicitation ID column stores the idea solicitation ID. The name column stores the reference authority for the name. The function / process classification column stores the reference authority for the classification. The provision mechanism column stores the reference authority for the provision mechanism. The core technology column stores the reference authority for the core technology. In the FP authority DB 44, the provision mechanism column and the core technology column include a summary column and a detail column.

FIG. 33 is an explanatory diagram showing an example of the CT authority DB 45. The CT authority DB 45 is a database that stores the reference authority of the core technical attribute. The CT authority DB 45 includes a node ID column, a resource solicitation ID column, an idea solicitation ID column, a name column, a division column, an idea content column, an assumed use column, and a patent application date column. The node ID column stores the node ID. The resource solicitation ID column stores the resource solicitation ID. The idea solicitation ID column stores the idea solicitation ID. The name column stores the reference authority for the name. The division column stores the reference authority for the division. The idea content column remembers the reference authority for the idea content. The assumed use column stores the reference authority for the assumed use. The patent application date column stores the reference authority for the patent application date. In the CT authority DB 45, the content column of the idea includes a summary column and a detail column.

FIG. 34 is an explanatory diagram showing an example of the management resource authority DB 46. The management resource authority DB 46 is a database that stores the management resource reference authority. The management resource authority DB includes a company ID column, a resource solicitation ID column, an idea solicitation ID column, a business ID column, a resource ID column, a management resource element column, a classification column, and a search keyword column. The company ID column stores the company ID. The resource solicitation ID column stores the resource solicitation ID. The idea solicitation ID column stores the idea solicitation ID. The business ID column stores the business ID. The resource ID column stores the resource ID. The management resource element column stores the reference authority for the management resource element. The management resource element column includes a summary column and a detail column. The summary column stores the reference authority to the summary. The detail column stores the reference authority to the detail. The classification column stores the reference authority for the classification. The classification column includes a classification 1 column and a classification 2 column. The classification 1 column stores the reference authority for classification 1. The classification 2 column stores the reference authority for classification 2. The searched keyword column stores the reference authority for the searched keyword.

Next, in order to facilitate the reference authority setting of the attribute, the default authority DB is introduced. The default authority DB defines the reference authority for each attribute for each development step of the new business. The default privilege DB eliminates the need for the user to set reference privileges for all attributes. The user only has to change where the default permissions set by the default permissions database are deemed inappropriate. In the following description, "~ default DB" is the default authority DB.

The development steps for new businesses are shown in Figures 6 and 7. Since the steps in the default authority DB are different from the steps shown in FIGS. 6 and 7, the correspondence between the two will be described below. In the idea solicitation type procedure, step S141 corresponds to "entry". Step S142 corresponds to "recruitment". Step S143 corresponds to "extraction of candidate companies". Step S144 corresponds to "evaluation / primary selection". Step S145 corresponds to "proposal creation". Steps S146 and S147 correspond to the "final selection". Step S148 corresponds to the "contract". Step S149 corresponds to "collaboration". In the management resource procurement type procedure, step S151 corresponds to "entry". Step S152 corresponds to "recruitment". Step S153 corresponds to "extraction of candidate companies". Steps S154 and S155 correspond to "evaluation / primary selection". Steps S156 and S157 correspond to "final selection". Step S158 corresponds to the "contract". Step S159 corresponds to "collaboration".

FIG. 35 is an explanatory diagram showing an example of the BM default DB 47. The BM default DB 47 is a database that stores the default authority of the business model attribute. The BM default DB 47 includes an ID column, a type column, a type column, a step column, a name column, a related field / industry column, a value provision column, a customer / service column, a profit structure model column, and a value provision system column. The ID column stores an ID that identifies a record. The type column memorizes the type of new business development. In the case of the idea solicitation type, the "idea" is memorized. In the case of management resource procurement type, "management resources" are memorized. The type column remembers the company's position on the recruitment. In the case of a company that is recruiting, "recruitment" is memorized. In the case of a company applying for recruitment, "application" is memorized. The step sequence stores the development steps. The name column remembers the default reference authority for the name. The open field / industry column remembers the default reference authority for related fields / industries. The offer value column stores the default reference authority for the offer value. The customer / service column stores the default reference authority for the customer / service. The revenue structure model column stores the default reference authority to the revenue structure. The value-providing system column stores the default reference authority to the value-providing system. In the BM default DB 47, the value provision column, the customer / service column, the profit structure model column, and the value provision system column include a summary column and a detail column.

FIG. 36 is an explanatory diagram showing an example of the PS default DB 48. The PS default DB 48 is a database that stores the default reference authority of product / service attributes. The PS default DB 48 includes an ID column, a type column, a type column, a step column, a name column, a category / classification column, a feature / performance column, and a core technology column. The ID column stores an ID that identifies a record. The type column stores the type of new business development (“idea” or “management resource”). The type column memorizes the company's position on recruitment (“recruitment” or “application”). The step sequence stores the development steps. The name column remembers the default reference authority for the name. The category / classification column stores the default reference authority for the classification. The feature / performance column stores the default reference authority for the feature / performance. The core technique column stores the default reference authority for the core technique. In the PS default DB 48, the feature / performance column and the core technology column include a schematic column and a detailed column.

FIG. 37 is an explanatory diagram showing an example of the FP default DB 49. The FP default DB 49 is a database that stores the default reference authority for function / process attributes. The FP default DB 49 includes an ID column, a type column, a type column, a step column, a name column, a function / process classification column, a provision mechanism column, and a core technology column. The ID column stores an ID that identifies a record. The type column stores the type of new business development (“idea” or “management resource”). The type column memorizes the company's position on recruitment (“recruitment” or “application”). The step sequence stores the development steps. The name column remembers the default reference authority for the name. The function / process classification column stores the default reference authority for the classification. The provision mechanism column stores the default reference authority for the provision mechanism. The core technique column stores the default reference authority for the core technique. In the FP default DB 49, the provided mechanism column and core technology column include a schematic column and a detailed column.

FIG. 38 is an explanatory diagram showing an example of the CT default DB 50. The CT default DB 50 is a database that stores the default reference authority of core technical attributes. The CT default DB 50 includes an ID column, a type column, a type column, a step column, a name column, a division column, an idea content column, an assumed use column, and a patent status column. The ID column stores an ID that identifies a record. The type column stores the type of new business development (“idea” or “management resource”). The type column memorizes the company's position on recruitment (“recruitment” or “application”). The step sequence stores the development steps. The name column remembers the default reference authority for the name. The indicator column stores the default reference authority for the indicator. The idea content column remembers the default read permission for the idea content. The Expected Usage column stores the default reference authority for the assumed usage. The patent status column stores the default reference authority for patent status. In the CT default DB 50, the content column of the idea includes a summary column and a detail column.

FIG. 39 is an explanatory diagram showing an example of the management resource default DB 51. The management resource default DB 51 is a database that stores the default management resource reference authority. The management resource default DB 51 includes an ID column, a type column, a type column, a step column, a management resource element column, a classification column, and a searched keyword column. The ID column stores an ID that identifies a record. The type column stores the type of new business development (“idea” or “management resource”). The type column memorizes the company's position on recruitment (“recruitment” or “application”). The step sequence stores the development steps. The management resource element column stores the default reference authority for the management resource element. The management resource element column includes a summary column and a detail column. The summary column remembers the default reference authority for the summary. The detail column remembers the default read permission for the detail. The classification column remembers the default reference authority for the classification. The classification column includes a classification 1 column and a classification 2 column. The classification 1 column stores the default reference authority for classification 1. The classification 2 column stores the default reference authority for classification 2. The searched keyword column stores the default reference authority for the searched keyword.

Next, the processing performed by the main server 1 will be described. FIG. 40 is a flowchart showing an example of the procedure for entry processing. The entry process is performed by all companies that are users of the open innovation system 100. The CPU 11 of the main server 1 outputs a basic information input screen (step S1). The CPU 11 determines whether or not the user has selected the input of the business details (step S2). When the CPU 11 determines that the user has selected the input of the business details (YES in step S2), the CPU 11 outputs the business information input screen (step S3). The CPU 11 determines whether or not the user has selected data registration (step S4). When the CPU 11 determines that the user has not selected data registration (NO in step S4), the CPU 11 determines whether or not the library has been selected (step S5). When the CPU 11 determines that the library is not selected (NO in step S5), the process returns to step S1. When the CPU 11 determines that the library has been selected (YES in step S5), the CPU 11 outputs the business model value providing process library screen (step S6). The CPU 11 determines whether or not any pattern in the library is selected (step S7). When the CPU 11 determines that none of the patterns in the library is selected (NO in step S7), the process returns to step S3. When the CPU 11 determines that any pattern in the library has been selected (YES in step S7), the CPU 11 outputs a tree creation screen using the selected pattern (step S8). The CPU 11 determines whether or not the storage of the tree is instructed (step S9). When the CPU 11 determines that the storage of the tree is not instructed (NO in step S9), the process returns to step S3. When the CPU 11 determines that the storage of the tree is instructed (YES in step S9), the CPU 11 stores the tree data (step S10). The CPU 11 returns the process to step S3. When the CPU 11 determines that the user has selected data registration (YES in step S4), the CPU 11 stores the business information input by the user in a temporary storage area provided in the RAM 13 or the like (step S11). The CPU 11 returns the process to step S1. When the CPU 11 determines that the user has not selected the input of the business details (NO in step S2), the CPU 11 stores the basic information (step S12). The CPU 11 determines whether or not the business information is stored in the temporary storage area provided in the RAM 13 or the like (step S13). When the CPU 11 determines that the business information is stored in the temporary storage area (YES in step S13), the CPU 11 stores the detailed information of the business stored in the temporary storage area (step S14), and ends the entry process. When the CPU 11 determines that the business information is not stored in the temporary storage area (NO in step S13), the CPU 11 ends the entry process.

Next, the processing in the idea solicitation type business development will be described. FIG. 41 is a flowchart showing a procedure example of the recruitment information input process. The CPU 11 outputs an input screen for inputting recruitment information (step S21). The CPU 11 acquires the recruitment information input by the user (step S22). The CPU 11 acquires the reference authority information corresponding to the recruitment information (step S23). The CPU 11 stores the acquired recruitment information (step S24). The CPU 11 stores the acquired reference authority information (step S25).

FIG. 42 is a flowchart showing a procedure example of node attribute output processing. The node attribute output process is a process that can be executed when the company planning to apply tries to refer to the recruitment information. It is a process to be executed when a node attribute associated with the recruitment information, for example, a function / process content is requested. The CPU 11 acquires the solicitation ID of the selected solicitation information and the node ID of the node (step S31). The CPU 11 acquires the type code associated with the acquired node ID from the node DB 28 (step S32). The CPU 11 acquires the attribute DB and the authority DB associated with the acquired type code from the attribute definition master DB 31 (step S33). The CPU 11 acquires the attribute information corresponding to the node ID from the acquired attribute DB (step S34). The CPU 11 acquires the reference authority corresponding to the node ID from the acquired authority DB (step S35). The CPU 11 rewrites a non-disclosure item in the attribute information based on the reference authority (step S36). Rewriting means, for example, replacing a non-disclosure item with a character string of "non-disclosure". Undisclosed items Make all characters included in a single character (*, #, etc.) or blank. Make non-disclosure items NULL. The CPU 11 outputs the attribute information (step S37).

FIG. 43 is a flowchart showing a procedure example of the application information input process. The CPU 11 outputs a screen for inputting the contents of the proposed business model (step S41). The CPU 11 determines whether or not tree creation is selected (step S42). When the CPU 11 determines that tree creation has been selected (YES in step S42), the CPU 11 outputs a tree creation screen (step S43). The CPU 11 generates data (node connection data, etc.) associated with the created tree (step S44). The CPU 11 returns the process to step S41. When the CPU 11 determines that tree creation is not selected (NO in step S42), the CPU 11 determines whether or not registration is selected (step S45). When the CPU 11 determines that registration has been selected (YES in step S45), the CPU 11 stores the business model data and the created tree data (step S46). The CPU 11 stores the reference authority (step S47). The CPU 11 ends the application information input process. When the CPU 11 determines that registration is not selected (NO in step S45), the CPU 11 ends the application information input process.

FIG. 44 is a flowchart showing an example of the procedure of the primary selection process. The CPU 11 outputs a list screen of the companies that applied for the recruitment (step S51). The CPU 11 determines whether or not the detailed display button is selected on the list screen (step S52). When the CPU 11 determines that the detail display button has been selected (YES in step S52), the CPU 11 outputs a detail content screen (step S53). The CPU 11 determines whether or not the back button is selected on the detailed content screen (step S54). When the CPU 11 determines that the back button is selected (YES in step S54), the CPU 11 returns the process to step S51. When the CPU 11 determines that the back button is not selected (NO in step S54), the process proceeds to step S55. When the CPU 11 determines that the detail display button is not selected (NO in step S52), the CPU 11 determines whether or not the selection button is selected (step S55). When the CPU 11 determines whether the selection button has been selected (YES in step S55), the CPU 11 stores the selection in the idea application company DB 37 (step S56). When the CPU 11 determines that the selection button is not selected (NO in step S55), the CPU 11 determines whether or not the end button is selected (step S57). When the CPU 11 determines that the end button is not selected (NO in step S57), the process returns to step S51. When the CPU 11 determines that the end button has been selected (YES in step S57), the CPU 11 notifies the selected company (step S58) and ends the primary selection process. Notification to the selected company will be given, for example, by e-mail.

FIG. 45 is a flowchart showing a procedure example of the detailed content screen output process. The CPU 11 acquires the node ID of the business model for which the display of the detailed contents is requested (step S61). The CPU 11 acquires the business model attribute associated with the node ID from the BM attribute DB 32 (step S62). The CPU 11 acquires the reference authority associated with the idea solicitation ID and the node ID from the BM authority DB 42 (step S63). The CPU 11 rewrites a non-disclosure item in the business model attribute based on the acquired reference authority (step S64). Rewriting is the same as described above. The CPU 11 outputs a detailed content screen (step S65).

FIG. 46 is a flowchart showing a procedure example of the selection acceptance process. The CPU 11 outputs a notification screen to the effect that it has been selected (step S71). The CPU 11 determines whether or not the acceptance button has been selected on the notification screen (step S72). When the CPU 11 determines that the acceptance button has been selected (YES in step S72), the CPU 11 changes the reference authority (step S73). The CPU 11 notifies the recruiting company (step S74), and ends the selection acceptance process. Notification to the recruiting company is given, for example, by e-mail. When the CPU 11 determines that the acceptance button is not selected (NO in step S72), the CPU 11 ends the selection acceptance process.

FIG. 47 is a flowchart showing a procedure example of the contract completion process. The CPU 11 outputs a list screen of the selected companies (step S81). The CPU 11 determines whether or not the contract completion button is selected on the list screen (step S82). When the CPU 11 determines that the contract completion button is not selected (NO in step S82), the process returns to step S81. When the CPU 11 determines that the contract completion button has been selected (YES in step S82), the CPU 11 acquires the company (contract company) selected on the list screen (step S83). The CPU 11 stores the contract result in the idea application company DB 37 (step S84). The CPU 11 changes the reference authority (step S85) and ends the contract completion process.

Next, an example of the screen used in the above processing is shown. The screen used in the entry process will be described. FIG. 48 is an explanatory diagram showing an example of the basic information input screen d01. The basic information input screen d01 includes an input field d011, a detail button d012, a registration button d013, a clear button d014, and a cancel button d015. The input field d011 is a field for inputting basic company information such as a company name, a URL of a homepage, and a head office address. The detail button d012 is a button for calling the business information input screen. The registration button d013 is a button for confirming the content and registering it in the database. The clear button d014 is a button for clearing all the input fields d011. The cancel button d015 is a button for canceling the registration of basic information.

FIG. 49 is an explanatory diagram showing an example of the business information input screen d02. The business information input screen d02 includes an input field d021, a library display button d022, a registration button d023, a clear button d024, and a cancel button d025. The input field d021 is a field for inputting character information about the business such as the value to be provided to the customer and the main products / services. The library display button d022 is a button for calling the business model value providing process library. The registration button d023 is a button for confirming the content and registering it in the database. The clear button d024 is a button for clearing all the input fields d021. The cancel button d025 is a button for canceling the registration of business information.

FIG. 50 is an explanatory diagram showing an example of the tree creation screen d03. The tree creation screen d03 includes a toolbar d031, an edit area d032, a save button d033, and an end button d034. Toolbar d031 includes various tools for creating and editing trees. The user creates and edits the tree using the tool. The editing area d032 is an area for creating / editing a tree. When using a tree registered in advance in the business model value providing process library, the selected tree is displayed in the editing area d032. The save button d033 is a button for saving the created / edited tree. The end button d034 is a button for ending the creation / editing of the tree.

FIG. 51 is an explanatory diagram showing an example of the business model attribute input screen d04. The business model attribute input screen d04 includes an input field d041, a disclosure setting field d042, a registration button d043, a clear button d044, and a cancel button d045. The input field d041 is a field for inputting character information of business model attributes such as a name, a related field / industry, and the like. The disclosure setting column d042 is a column for setting disclosure of each item. Non-disclosure indicates that it will not be disclosed to other users. Disclosure indicates that it will be disclosed to other users. If you check the restriction column, you can disclose it only to the users who are limited to the users who have a collaborative relationship. The registration button d043 is a button for confirming the content and registering it in the database. The clear button d044 is a button for clearing all the input fields d041. The cancel button d045 is a button for canceling the registration of the attribute information of the business model. The item that overlaps with the input field d021 of the business information input screen d02 may be input on either the business information input screen d02 or the business model attribute input screen d04. Also, if the overlapping items have been entered on one screen, they will be displayed on the other screen even when creating a new one.

FIG. 52 is an explanatory diagram showing an example of the function / process attribute input screen d05. The function / process attribute input screen d05 includes an input field d051, a disclosure setting field d052, a registration button d053, a clear button d054, and a cancel button d055. The input field d051 is a field for inputting character information of function / process attribute information such as a name and a classification. The disclosure setting column d052 is a column for setting disclosure of each item. The registration button d053 is a button for confirming the content and registering it in the database. The clear button d054 is a button for clearing all the input fields d051. The cancel button d055 is a button for canceling the registration of the attribute information of the function / process. The screen for inputting the attributes of the product / service and the core technology is the same as the function / process attribute input screen d05.

Next, the screen used in the recruitment information input process will be described. FIG. 53 is an explanatory diagram showing an example of the recruitment information input screen d06. The recruitment information input screen d06 includes an input field d061, a management resource setting field d062 that can be provided, a registration button d063, a clear button d064, and a cancel button d065. The input field d061 is a field for inputting recruitment information such as a theme and preconditions. The management resource setting column d062 that can be provided is a column for setting the management resources that are planned to be provided when conducting a new business based on the recruitment. The clear button d064 is a button for clearing all the input fields d061. The cancel button d065 is a button for canceling the registration of recruitment information.

By selecting the management resource element displayed in the management resource setting column d062 that can be provided, it is possible to confirm the contents and set the reference authority. For example, it is assumed that the measurement system having excellent environmental resistance shown in FIG. 53 is registered as a function / process. When the user selects a measurement system having excellent environmental resistance, the function / process attribute input screen d05 shown in FIG. 52 is displayed. At this time, if the reference authority is registered in the FP authority DB44, the disclosure setting field d052 is displayed accordingly. If the reference authority is not registered in the FP authority DB44, the FP default DB49 is referred to, and the disclosure setting field d052 is displayed according to the default reference authority. Here, in the idea solicitation type, the authority setting performed by the soliciting company is the solicitation step. Therefore, in the FP default DB 49 shown in FIG. 37, the record with ID = 2 is referred to. The user uses the function / process attribute input screen d05 to change the reference authority of each item as necessary. The change result is reflected in the FP authority DB44.

Next, the screen used in the application information input process will be described. In the application information input process, the screens used when the user of the applicant company inputs the business model are shown in d03 of the tree creation screen shown in FIG. 50, the business model attribute input screen d04 shown in FIG. 51, and FIG. 52. Function / process attribute input screen d05 and the like. In the application information input process, the user of the applicant company can set the reference authority by using the business model attribute input screen d04 and the function / process attribute input screen d05. Here, in the idea solicitation type, the authority setting performed by the applicant company is the solicitation step. Therefore, on the business model attribute input screen d04, the default value of the disclosure setting follows the record of ID = 12 in the BM default DB 47 shown in FIG. 35. Further, on the function / process attribute input screen d05, the default value of the disclosure setting follows the record of ID = 12 in the FP default DB 49 shown in FIG. 37.

Subsequently, the screen used in the primary selection process will be described. FIG. 54 is an explanatory diagram showing an example of the applicant company list screen d07. The applicant company list screen d07 includes a list d071, a clear button d072, and an end button d073. List d071 displays a list of applicant companies. The list d071 is provided with a selection button d0711 and a check box d0712. The selection button d0711 is a button for displaying the details of the business model proposed by the applicant company. The check box d0712 is for designating the company selected in the primary selection. Check the selected company. The clear button d072 is a button for clearing the checks of all the check boxes d0712. The end button d073 is a button for ending the primary selection. When the end button d073 is selected, the applicant company list screen d07 is closed and the selected company ID is returned.

FIG. 55 is an explanatory diagram showing an example of the detailed content screen d08. The detailed content screen d08 is a screen that opens when the selection button d0711 is selected on the applicant company list screen d07. The detailed content screen d08 includes a display field d081, a tree display button d082, a selection button d083, and a back button d084. The display field d081 displays the attributes of the proposed business model. In the display column d081, the non-disclosure items provided value (details), customer service (details), profit structure model (details), and value provision system (details) are displayed as "non-disclosure". ing. The tree display button d082 is a button for displaying the tree screen. The tree screen is a screen showing the overall structure of the proposed business model. The selection button d083 is a button for selecting the proposed business model. The back button d084 is a button for returning to the applicant company list screen d07. The result of selecting the selection button d083 on the detailed content screen d08 is reflected in the check box d0712 of the list table d071 when the screen returns to the applicant company list screen d07.

The applicant company primaryly selected by the applicant company list screen d07 is requested to indicate that the primary selection has been made and to give a presentation. When the applicant company approves the primary selection, the reference authority of the data of the applicant company that has accepted the primary selection is changed by the selection acceptance process. In the above example, the recruiting company can refer to the value to be provided (details), the customer / service (details), the profit structure model (details), and the value provision system (details) on the detailed content screen d08.

Furthermore, if the applicant company is first selected and then a contract is concluded with the recruiting company through a presentation, the reference authority for the data of the recruiting company will be changed by the contract completion process. For example, the function provision mechanism and the core technology for function provision, which are the attributes of functions and processes, are only disclosed in outline at the application stage, but the company that has signed the contract can also refer to the details of each. ..

Next, the processing in the management resource procurement type business development will be described. In business development of management resource procurement type, it is premised that the recruiting company has designed the business model to some extent. In the following explanation, it is assumed that the recruiting company has designed the business model and has already created a tree showing the overall structure. However, some management resources have been decided to be procured from other companies through collaboration, and the open innovation system 100 is trying to recruit.

FIG. 56 is a flowchart showing a procedure example of the search registration process. The search registration process is started after specifying the target node on the tree display screen of the business model. The CPU 11 acquires the node ID of the designated node (step S91). The CPU 11 outputs an input screen incorporating the attributes of the designated node (step S92). The user inputs a search condition and a search keyword. The CPU 11 acquires the search conditions and search keywords and stores them in the resource solicitation DB 38 (step S93). In step S93, the CPU 11 also stores other items to be stored in the resource solicitation DB 38. The CPU 11 acquires the default reference authority for the target business model from the BM default DB 47 or the like (step S94). Not only the business model but also the default reference authority associated with the products / services, functions / processes, and core technologies that make up the business model are acquired. The CPU 11 stores the acquired default reference authority in the BM authority DB 42 or the like as the reference authority of the target business model (step S95). The CPU 11 ends the search registration process.

FIG. 57 is a flowchart showing a procedure example of the long list creation process. The CPU 11 acquires the search conditions and search keywords related to the solicitation as a control from the resource solicitation DB 38 (step S101). The CPU 11 generates a search formula from the acquired search conditions and search keywords (steps and 102). When the acquired search condition is a sentence, the CPU 11 performs language analysis and generates a search formula. The CPU 11 outputs a search screen in which the generated search formula is embedded (step S103). The user changes the search expression if necessary and gives a search instruction. The CPU 11 performs a search (step S104). The CPU 11 outputs a long list generated from the search results (step S105). The CPU 11 ends the long list creation process.

FIG. 58 is a flowchart showing a procedure example of the short list creation process. The CPU 11 outputs a short list creation screen (step S111). The short list creation screen contains a long list. The CPU 11 determines whether or not the detailed display is selected on the short list creation screen (step S112). When the CPU 11 determines that the detail display button has been selected (YES in step S112), the CPU 11 outputs a detail content screen (step S113). Basic information of the selected company is displayed on the detailed content screen. The detailed content screen is a screen similar to the basic information input screen d01. The CPU 11 determines whether or not the back button is selected on the detailed content screen (step S114). When the CPU 11 determines that the back button is selected (YES in step S114), the CPU 11 returns the process to step S112. When the CPU 11 determines that the back button is not selected (NO in step S114), the process proceeds to step S115. When the CPU 11 determines that the detail display button is not selected (NO in step S112), the CPU 11 determines whether or not the selection button is selected (step S115). When the CPU 11 determines that the selection button has been selected (YES in step S115), the CPU 11 stores the selection in the idea application company DB 37 (step S116). When the CPU 11 determines that the selection button is not selected (NO in step S115), the CPU 11 determines whether or not the end button is selected (step S117). When the CPU 11 determines that the end button is not selected (NO in step S117), the process returns to step S111. When the CPU 11 determines that the end button has been selected (YES in step S117), the CPU 11 changes the reference authority (step S118). The CPU 11 sets the group (step S119). The CPU 11 generates group data including the selected company and stores it in the group DB 40. The CPU 11 sets the group ID of the generated group to the group ID of the record including the resource solicitation ID to be processed in the access authority DB 41. This will give the selected companies access to data on resource solicitation. The CPU 11 ends the short list process.

FIG. 59 is a flowchart showing a procedure example of the proposal creation process. The CPU 11 acquires the node ID of the proposed node (step S121). The CPU 11 outputs an input screen of the proposal content corresponding to the type of the proposal target node (step S122). The CPU 11 acquires the attribute information of the proposal target node, which is the content of the proposal (step S123). The CPU 11 stores the acquired attribute information (step S124). The CPU 11 acquires the default reference authority (step S125). The CPU 11 stores the acquired default reference authority as the reference authority of the attribute information (step S126). The CPU 11 ends the proposal creation process.

FIG. 60 is a flowchart showing an example of the procedure of the final selection process. The CPU 11 outputs the final selection screen (step S131). The final selection screen is a list of companies included in the short list and the companies that created the proposal. As a result of the final selection, the user selects a company to negotiate a contract on the final selection screen. The CPU 11 acquires the ID (company ID) of the company selected by the user (step S132). The CPU 11 acquires the default reference authority (step S133). The CPU 11 stores the reference authority (step S134).

When a contract for collaboration is concluded as a result of negotiations with the companies remaining in the final selection, the CPU 11 performs the contract completion process. The processing procedure and the like are the same as the above-mentioned contract completion processing.

Next, an example of the screen used in the above processing is shown. The screen used in the search registration process will be described. FIG. 61 is an explanatory diagram showing an example of the resource solicitation guideline input screen d09. The resource recruitment guideline input screen d09 includes a recruitment target confirmation field d091, a search condition input field d092, a search keyword input field d093, a registration button d094, a clear button d095, and a cancel button d096. The recruitment target confirmation column d091 is a column in which the management resources to be recruited are displayed. FIG. 61 shows a case where core technology is solicited. As described above, since the search registration process is started after the design of the business model is completed, it is premised that the content displayed in the recruitment target confirmation column d091 does not need to be changed. However, the content may be changed as needed. In the search condition input field d092, technical issues and required specifications / accuracy are described for the management resources to be searched (searched). In the search keyword input field d093, a search keyword for the management resource to be searched (searched) is described. The registration button d094 is a button for registering a search condition and a search keyword. When the content of the recruitment target confirmation column d091 is changed, the change is reflected in the attribute DB by the registration button d094. The clear button d095 is a button for clearing the search condition input field d092 as a search keyword input field d093. The cancel button d096 is a button for canceling the registration of the resource recruitment requirements.

The screen used in the short list creation process will be described. FIG. 62 is an explanatory diagram showing an example of the short list creation screen d10. The short list creation screen d10 includes a list d101, a clear button d102, and an end button d103. The list d101 displays the long list obtained in the long list creation process. The list d101 is provided with a selection button d1011 and a check box d1012. The selection button d1011 is a button for displaying the basic information of the company extracted as a long list. The check box d1012 is for designating the company selected as the short list. Check the selected company. The clear button d102 is a button for clearing the checks of all the check boxes d1012. The end button d103 is a button for ending the short list creation. When the end button d103 is selected, the short list creation screen d10 is closed and the selected company ID is returned. The final selection screen of the final selection process is the same as the short list creation screen d10.

In this embodiment, it is possible to control the information to be disclosed at each step from the recruitment to the conclusion of the contract. As a result, the recruiting company can recruit a collaborative company without unnecessarily disclosing its own information to the partner company. Similarly, the applicant company can apply for a collaborative company without unnecessarily disclosing its information to the partner company.

Further, in the open innovation system 100, the business model is expressed by a multi-layered tree structure. Therefore, it is possible to handle various business models in a unified manner.

The technical features (constituent requirements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed.
The embodiments disclosed this time should be considered to be exemplary in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

100 Open innovation system 110 Progress management system 1 Main server 11 CPU
12 ROM
13 RAM
14 Large-capacity storage unit 15 Communication unit 16 Reading unit 1P control program 1a Portable storage medium 1b Semiconductor memory 2 Database server 21 User master DB
22 Department master DB
23 Company master DB
24 Company Business DB
25 Management resource DB
26 Resource classification master DB
27 Tree DB
28 node DB
29 Type code master DB
30 node connection DB
31 Attribute definition master DB
32 BM attribute DB
33 PS attribute DB
34 FP attribute DB
35 CT Technical Attribute DB
36 Idea recruitment DB
37 Idea application company DB
38 Resource Recruitment DB
39 Company list DB
40 group DB
41 Access authority DB
42 BM authority DB
43 PS authority DB
44 FP authority DB
45 CT authority DB
46 Management resource authority DB
47 BM default DB
48 PS default DB
49 FP default DB
50 CT default DB
51 Management resource default DB
3 Firewall N network N1 local network

Claims (8)

Receive information on management resources that can be provided from the recruitment terminal of the recruiter,
Judge whether the first reference authority corresponding to the received management resource is set, and
If it is determined that the first reference authority is not set, the first default authority is acquired and the first reference authority is acquired.
The acquired first default authority is transmitted to the recruitment terminal,
Receive the first instruction for the first default authority from the recruitment terminal,
Based on the received first instruction, the first reference authority is created from the first default authority, and the first reference authority is created.
The created first reference authority is stored in association with the identification information of the information of the management resource.
Receive the registration request of the provision value definition that uses the above management resources from the applicant's application terminal,
Acquire the second default authority for the information of the provided value definition,
The acquired second default authority is transmitted to the application terminal,
From the application terminal, the information of the provided value definition and the second instruction for the second default authority are received.
Memorize the received information of the provided value definition and
Based on the received second instruction, the second reference authority is created from the second default authority, and the second reference authority is created.
The created second reference authority is stored in association with the identification information of the information of the provided value definition .
When receiving information from the application terminal of a value provision scheme that includes the products, services, functions, or processes required to construct the provision value definition and requires the management resources to construct.
It is determined whether or not the third reference authority corresponding to the acquired product, service, function, or process included in the value provision scheme is set.
If it is determined that the third reference authority is not set, the third default authority is acquired and the third reference authority is acquired.
The acquired third default authority is transmitted to the application terminal,
Upon receiving the third instruction for the third default authority from the application terminal,
Based on the received third instruction, the third reference authority is created from the third default authority, and the third reference authority is created.
The created third reference authority is stored in association with the identification information of the product, service, function, or process included in the value provision scheme.
The correspondence relationship between the management resource information and the value provision scheme information, and the correspondence relationship between the provision value definition information and the value provision scheme information are memorized.
To construct the value provision scheme with the information of the offer value definition, the information of the value provision scheme including the products, services, functions, or processes necessary for constructing the offer value definition from the recruitment terminal. When a request for business information is received that is associated with the information on the management resources required for
Obtain the above business information and
Obtain the second reference authority for the information of each value provision definition, the third reference authority for the information of each value provision scheme, and the first reference authority for the information of each management resource.
Whether or not to output the information of each value provision definition is determined based on the acquired second reference authority, and whether or not to output the information of each value provision scheme based on the acquired third reference authority. A computer program characterized by having a computer perform a process of determining whether or not to output information on each management resource based on the acquired first reference authority. Receives information on the value provision definition and information on the value provision scheme including the products, services, functions, or processes required to configure the provision value definition from the recruitment terminal of the recruiter.
It is determined whether or not the second reference authority corresponding to the received information of the provided value definition is set.
If it is determined that the second reference authority is not set, the second default authority is acquired and the second default authority is acquired.
It is determined whether or not the third reference authority corresponding to the received information of the value provision scheme is set, and it is determined.
If it is determined that the third reference authority is not set, the third default authority is acquired and the third reference authority is acquired.
The acquired second default authority or the third default authority is transmitted to the recruitment terminal.
Receive the second instruction for the second default authority or the third instruction for the third default authority from the recruitment terminal.
Based on the received second instruction, the second reference authority is created from the second default authority, or based on the received third instruction, the third reference authority is created from the third default authority.
The created second reference authority is stored in association with the identification information of the information of the provision value definition , or the created third reference authority is stored in the product, service, function, or process included in the value provision scheme. Stored in association with the identification information
Memorize the correspondence between the information of the value provision definition and the information of the value provision scheme.
Receive a registration request for information on management resources required to build the value provision scheme from the applicant's application terminal.
Acquire the first default authority for the information on the management resources,
The acquired first default authority is transmitted to the application terminal,
From the application terminal, the information on the management resource and the first instruction for the first default authority are received.
Memorize the received information on the management resources
Based on the received first instruction, the first reference authority is created from the first default authority, and the first reference authority is created.
The created first reference authority is stored in association with the identification information of the information of the management resource.
When a request for information on the management resources is received from the recruitment terminal
Obtain information on the above management resources
Obtain the first reference authority for the information of each management resource,
A computer program characterized by having a computer perform a process of determining whether or not to output information on each management resource based on the acquired first reference authority. Obtain recruitment information regarding business information or management resource information,
The computer program according to claim 1 or 2, wherein the third reference authority is changed based on the progress of the recruitment. Obtain the group information corresponding to the above recruitment information and
Whether or not the user who requested the business information corresponding to the recruitment information is the applicant is determined based on the group information.
When it is determined that the user is the applicant, the information of each provision value definition included in the business information, the information of each value provision scheme, and each management resource are based on the first to third reference authority. The computer program according to claim 3, wherein information is output. The first receiver that receives information on the management resources that can be provided from the recruitment terminal of the recruiter,
The first judgment unit that determines whether or not the first reference authority corresponding to the received management resource is set, and
When it is determined that the first reference authority is not set, the first acquisition unit for acquiring the first default authority and the first acquisition unit
The first transmission unit that transmits the acquired first default authority to the recruitment terminal,
A second receiving unit that receives the first instruction for the first default authority from the recruiting terminal, and
Based on the received first instruction, the first creation unit that creates the first reference authority from the first default authority, and
A first storage unit that stores the created first reference authority in association with the identification information of the management resource information, and
From the applicant's application terminal, the third receiver that receives the registration request of the provision value definition that uses the management resources, and
The second acquisition unit that acquires the second default authority for the information of the provided value definition, and
A second transmission unit that transmits the second default authority acquired to the application terminal, and
A fourth receiving unit that receives the information of the provided value definition and the second instruction for the second default authority from the application terminal.
A second storage unit that stores the received information of the provided value definition ,
Based on the received second instruction, the second creation unit that creates the second reference authority from the second default authority, and
A third storage unit that stores the created second reference authority in association with the identification information of the information of the provided value definition , and
When receiving information from the application terminal of a value provision scheme that includes the products, services, functions, or processes required to construct the provision value definition and requires the management resources to construct.
A second determination unit that determines whether or not a third reference authority corresponding to the acquired product, service, function, or process included in the value provision scheme is set.
When it is determined that the third reference authority is not set, the third acquisition unit for acquiring the third default authority and the third acquisition unit
A third transmission unit that transmits the acquired third default authority to the application terminal,
A fifth receiving unit that receives a third instruction for the third default authority from the application terminal, and
Based on the received third instruction, the third creation unit that creates the third reference authority from the third default authority, and
A fourth storage unit that stores the created third reference authority in association with the identification information of the product, service, function, or process included in the value provision scheme.
A fifth storage unit that stores the correspondence between the management resource information and the value provision scheme information, and the correspondence between the provision value definition information and the value provision scheme information.
To construct the value provision scheme with the information of the offer value definition, the information of the value provision scheme including the products, services, functions, or processes necessary for constructing the offer value definition from the recruitment terminal. When a request for business information is received that is associated with the information on the management resources required for
The 4th acquisition department that acquires the business information and
The fifth acquisition department that acquires the second reference authority for the information of each value provision definition, the third reference authority for the information of each value provision scheme, and the first reference authority for the information of each management resource.
Whether or not to output the information of each value provision definition is determined based on the acquired second reference authority, and whether or not to output the information of each value provision scheme based on the acquired third reference authority. A determination device including a third determination unit that determines whether or not to output information on each management resource based on the acquired first reference authority. A first receiver that receives information on the value provision definition and information on the value provision scheme including the products, services, functions, or processes required to configure the provision value definition from the recruitment terminal of the recruiter. ,
The first determination unit that determines whether or not the second reference authority corresponding to the received information of the provided value definition is set, and
When it is determined that the second reference authority is not set, the first acquisition unit for acquiring the second default authority and the first acquisition unit
The second determination unit, which determines whether or not the third reference authority corresponding to the received information of the value provision scheme is set.
When it is determined that the third reference authority is not set, the second acquisition unit for acquiring the third default authority and the second acquisition unit
A first transmission unit that transmits the acquired second default authority or the third default authority to the recruitment terminal.
A second receiving unit that receives a second instruction for the second default authority or a third instruction for the third default authority from the recruitment terminal.
Based on the received second instruction, the second reference authority is created from the second default authority, or the third reference authority is created from the third default authority based on the received third instruction. 1 Creation Department and
The created second reference authority is stored in association with the identification information of the information of the provision value definition , or the created third reference authority is stored in the product, service, function, or process included in the value provision scheme. The first storage unit that stores the identification information in association with it,
A second storage unit that stores the correspondence between the information of the value provision definition and the information of the value provision scheme.
A third receiver that receives a registration request for information on management resources required to build the value provision scheme from the applicant's application terminal, and
The third acquisition department that acquires the first default authority for the information of the management resources, and
A second transmission unit that transmits the first default authority acquired to the application terminal, and
A fourth receiving unit that receives information on the management resources and a first instruction for the first default authority from the application terminal.
A third storage unit that stores the received information on the management resources,
Based on the received first instruction, the second creation unit that creates the first reference authority from the first default authority, and
A third storage unit that stores the created first reference authority in association with the identification information of the management resource information.
When a request for information on the management resources is received from the recruitment terminal
The 4th acquisition department that acquires information on the management resources,
The 5th acquisition department that acquires the 1st reference authority for the information of each management resource,
A determination device including a third determination unit that determines whether or not to output information on each management resource based on the acquired first reference authority. The computer
Receive information on management resources that can be provided from the recruitment terminal of the recruiter,
Judge whether the first reference authority corresponding to the received management resource is set, and
If it is determined that the first reference authority is not set, the first default authority is acquired and the first reference authority is acquired.
The acquired first default authority is transmitted to the recruitment terminal,
Receive the first instruction for the first default authority from the recruitment terminal,
Based on the received first instruction, the first reference authority is created from the first default authority, and the first reference authority is created.
The created first reference authority is stored in association with the identification information of the information of the management resource.
Receive the registration request of the provision value definition that uses the above management resources from the applicant's application terminal,
Acquire the second default authority for the information of the provided value definition,
The acquired second default authority is transmitted to the application terminal,
From the application terminal, the information of the provided value definition and the second instruction for the second default authority are received.
Memorize the received information of the provided value definition and
Based on the received second instruction, the second reference authority is created from the second default authority, and the second reference authority is created.
The created second reference authority is stored in association with the identification information of the information of the provided value definition .
When receiving information from the application terminal of a value provision scheme that includes the products, services, functions, or processes required to construct the provision value definition and requires the management resources to construct.
It is determined whether or not the third reference authority corresponding to the acquired product, service, function, or process included in the value provision scheme is set.
If it is determined that the third reference authority is not set, the third default authority is acquired and the third reference authority is acquired.
The acquired third default authority is transmitted to the application terminal,
Upon receiving the third instruction for the third default authority from the application terminal,
Based on the received third instruction, the third reference authority is created from the third default authority, and the third reference authority is created.
The created third reference authority is stored in association with the identification information of the product, service, function, or process included in the value provision scheme.
The correspondence relationship between the management resource information and the value provision scheme information, and the correspondence relationship between the provision value definition information and the value provision scheme information are memorized.
To construct the value provision scheme with the information of the offer value definition, the information of the value provision scheme including the products, services, functions, or processes necessary for constructing the offer value definition from the recruitment terminal. When a request for business information is received that is associated with the information on the management resources required for
Obtain the above business information and
Obtain the second reference authority for the information of each value provision definition, the third reference authority for the information of each value provision scheme, and the first reference authority for the information of each management resource.
Whether or not to output the information of each value provision definition is determined based on the acquired second reference authority, and whether or not to output the information of each value provision scheme based on the acquired third reference authority. A determination method comprising a process of determining whether or not to output information on each management resource based on the acquired first reference authority. The computer
Receives information on the value provision definition and information on the value provision scheme including the products, services, functions, or processes required to configure the provision value definition from the recruitment terminal of the recruiter.
It is determined whether or not the second reference authority corresponding to the received information of the provided value definition is set.
If it is determined that the second reference authority is not set, the second default authority is acquired and the second default authority is acquired.
It is determined whether or not the third reference authority corresponding to the received information of the value provision scheme is set, and it is determined.
If it is determined that the third reference authority is not set, the third default authority is acquired and the third reference authority is acquired.
The acquired second default authority or the third default authority is transmitted to the recruitment terminal.
Receive the second instruction for the second default authority or the third instruction for the third default authority from the recruitment terminal.
Based on the received second instruction, the second reference authority is created from the second default authority, or based on the received third instruction, the third reference authority is created from the third default authority.
The created second reference authority is stored in association with the identification information of the information of the provision value definition , or the created third reference authority is stored in the product, service, function, or process included in the value provision scheme. Stored in association with the identification information
Memorize the correspondence between the information of the value provision definition and the information of the value provision scheme.
Receive a registration request for information on management resources required to build the value provision scheme from the applicant's application terminal.
Acquire the first default authority for the information on the management resources,
The acquired first default authority is transmitted to the application terminal,
From the application terminal, the information on the management resource and the first instruction for the first default authority are received.
Memorize the received information on the management resources
Based on the received first instruction, the first reference authority is created from the first default authority, and the first reference authority is created.
The created first reference authority is stored in association with the identification information of the information of the management resource.
When a request for information on the management resources is received from the recruitment terminal
Obtain information on the above management resources
Obtain the first reference authority for the information of each management resource,
A determination method characterized by performing a process of determining whether or not to output information on each management resource based on the acquired first reference authority.

Images