JP2019061471A - Computer program, determining device and determining method - Google Patents

Abstract

To provide a computer program or the like which systematizes a structure of a business model, and controls, for each element that constructs the systematized business model, a reference authority.SOLUTION: A computer program obtains business information that associates information on a providing value definition, information on a value providing scheme including a product, a service, a function or a process necessary to construct the providing value definition, and information on a resource of business necessary to achieve the value providing scheme with one another. Authority information for the information on each providing value definition, the information on each value providing scheme, and the information on each resource of business, and a determination is made on whether or not to output the information on each providing value definition, the information on each value providing scheme, and the information on each resource of business on the basis of the obtained authority information.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a computer program or the like that determines the reference authority of data.

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

JP, 2002-7778, A Japanese Patent Application Laid-Open No. 2002-169881 Unexamined-Japanese-Patent No. 2008-276653

  However, in the prior art, technical elements constituting a business model are not organized. 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 appropriately control the reference authority of data on 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 etc. that controls the reference authority for each of the elements constituting the business model.

  A computer program according to the present invention constructs information of a value provision scheme, information of a provision value definition, information of a value provision scheme including products, services, functions, or processes required to configure the provision value definition, and the value provision scheme. Business information associated with the information of management resources required to obtain the information of each provision value definition, information of each value provision scheme, and authority information for information of each management resource It is characterized by making a computer perform processing which judges whether information on each offer value definition, information on each value offer scheme, and information on each management resource is outputted based on the above-mentioned authority information.

  In the present invention, reference authority can be controlled for each of the elements constituting the organized business model.

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

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

  FIG. 1 is an explanatory view of a configuration example of the open innovation system 100. As shown in FIG. The open innovation system 100 includes a progress management system 110 as well as companies 120 and individual inventors 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, a terminal 4 of an operator and a terminal 5 of a system administrator. These are communicably connected to each other by the local network N1. The enterprise 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 terminals 6 of the enterprise 120 and the individual inventor 130 via the local network N1, the firewall 3 and the network N. Although FIG. 1 shows only two companies 120 and only one individual inventor 140, the present invention is not limited thereto. There may be three or more companies 120 and two or more individual inventors 130. Not only one terminal 2 but also two or more terminals may be provided for each of the terminals 120 owned by the corporation 120 and the individual inventor 130.

  FIG. 2 is a block diagram showing an example of the hardware configuration of the main server 1. The main server 1 includes a central processing unit (CPU) 11, a read only memory (ROM) 12, a random access memory (RAM) 13, a large capacity storage unit 14, a communication unit 15, and a reading unit 16. Each configuration is connected by a bus B.

  The CPU 11 controls each hardware unit in accordance with a control program (computer program) 1P stored in the ROM 12. The RAM 13 is, for example, an SRAM (Static RAM), a DRAM (Dynamic RAM), or a flash memory. The RAM 13 temporarily stores data generated when the CPU 11 executes a program.

  The large-capacity storage unit 14 is, for example, a hard disk or a solid state drive (SSD). The large capacity storage unit 14 stores various data. The control program 1P may be stored in the mass 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 enterprise 120 and 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 1 a including a CD (Compact Disc) -ROM and a DVD (Digital Versatile Disc) -ROM. The CPU 11 may read the control program 1 P from the portable storage medium 1 a via the reading unit 16 and store the control program 1 P in the large-capacity storage unit 14. Alternatively, the CPU 11 may download the control program 1P from another computer via the local network N1 or the like and store the control program 1P 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 an example of the hardware configuration 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 a bus B.

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

  The communication unit 64 communicates with the main server 1 and other computers via the network N. The input unit 65 receives data and the like related to the business model input by the user via the keyboard and the mouse. The display unit 66 includes an image display device such as a liquid crystal display panel, for example. 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 6 a 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 the control program 6P in the large-capacity storage unit 67. In addition, the CPU 61 may download the control program 6P from another computer via the network N or the like and store the control program 6P in the large-capacity storage unit 67. Furthermore, the CPU 61 may read the control program 6P from the semiconductor memory 6b. The operator's terminal 4 and the system administrator's terminal 5 have the same configuration as the terminal 6.

  In the present embodiment, the business model is expressed in a three-tiered structure. FIG. 4 is an explanatory view showing a hierarchical structure of a business model. The upper layer of the three hierarchies is a business model hierarchy NT that defines business concepts such as the value that the business model (provided value definition) provides to the customer, the customer, and the product service. Below the business model hierarchy NT is a process / functional hierarchy NM (value provision scheme) in which elements constituting a mechanism for providing value to customers are arranged. In the process / function hierarchy NM, components (value delivery system) of business models such as products / services, functions / processes, value chains, etc. are arranged. Below the process / function hierarchy NM is a management resource hierarchy NB. The management resource hierarchy NB is not only an individual idea, know-how, intellectual property such as patent, unique technology, but also a source of strength of the business model. A management resource element is arranged in association with each element of the process / function hierarchy NM.

  FIG. 5 is an explanatory view showing a display example of a 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. The nodes NM1 to NM4 are subordinate to the node NT1. Therefore, each of the nodes NM1 to NM4 is edge connected to the node NT1. One node NB1 is disposed in the management resource hierarchy NB. The node NB1 is subordinate to the 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 process / functional hierarchy required for the business model. The four functions / processes are a reception process (node NM1), an identity confirmation inquiry content confirmation (node NM2), a response / answer (node NM3), and an after-treatment work (node NM4).

  PBX, IVR, CTI (node NB1) is shown as a management resource corresponding to the reception process (node NM1). The management resources corresponding to the person confirmation / query content confirmation (node NM2), the response / answer (node NM3), and the post-processing task (node NM4) are not described. PBX is an abbreviation of Private Branch eXchange (private branch exchange). IVR is an abbreviation of Interactive Voice Response (automatic voice response automatic response). IVR is the name of a function, but a device providing the IVR function may be simply referred to as IVR. CTI is an abbreviation of Computer Telephony Integration. Like IVR, CTI is the name of a function, but a device providing 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-tiered structure, any business can be systematically handled. When it is difficult to express a business model with a simple three-tier structure, such as when there are many elements that make up a business model, or when using advanced technology in which many elemental technologies are stacked in multiple stages, etc. The nodes included in the process / function hierarchy NM or the 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 of hierarchical structure. In addition, when constructing a new business model using an existing business model, the existing business model is one node included in the process / functional hierarchy NM or the management resource hierarchy NB. A business model expressed in a three-tier structure is called a three-tier model.

  Subsequently, development of a new business by the open innovation system 100 will be described. Here, by means of the open innovation system 100, a plurality of companies form a cooperative relationship to explain the process leading to the development of a new business. Explaining the development of a new business in two patterns. In the following description, in pattern 1, a company calling for collaboration is called a recruiting company. Companies that respond to the call for collaboration are called applicant companies. In Pattern 2, a company calling for collaboration is called a searching company. A company that responds to a call for collaboration is called a proposed company. In pattern 1, the recruiting company recruits 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 recruits the necessary technology and management resources for realization, and completes the business model using the technology and management resources gathered from the proposal company. The search enterprise starts the business based on the completed business model. Hereinafter, the commercialization process according to pattern 1 is referred to as an idea solicitation business creation process, or simply as an idea solicitation type. Hereinafter, the commercialization process according to pattern 2 is referred to as a business resource procurement business creation process, or simply as a business resource procurement type.

  FIG. 6 is a flowchart showing an idea solicitation type procedure. Master information is registered in the open innovation system 100 by companies (a recruiting company and an application company) participating in the open innovation system 100 (step S141). The master information includes not only profile information posted on websites, etc., but also an outline of the existing business model and information on management resources assumed to be provided for collaboration. A recruitment essential point regarding recruitment of business model ideas is registered in the open innovation system 100 by the recruitment company (step S142). The recruitment guidelines include the recruitment theme and preconditions for recruitment, idea evaluation criteria, and management resources that are expected to be provided. Companies that are considering collaborating with other companies refer to the application guidelines through the open innovation system 100. At this time, by the authority control by the open innovation system 100, it is possible to refer only to the outline of the recruitment requirement. In accordance with the recruitment guidelines, application information of the business model idea is registered in the open innovation system 100 by the application company (step S143). Also about the reference of the application information by the recruitment company, the authority is controlled by the open innovation system 100, and the recruitment company can refer to the outline of the idea. The applicant company registers business model ideas in the above three-tier model. The recruiting company evaluates the submitted business model ideas based on the evaluation criteria. The recruiting company selects the applicant company that has applied for the excellent business model idea (step S144). The recruiting company presents the proposal preparation guidelines to the selected applicant companies (selected companies) and requests them to prepare a proposal. The request can be made through the open innovation system 100. The selected company prepares and submits a proposal based on the proposal preparation procedure (step S145). The submission of the proposal can be performed through the open innovation system 100. At this point, the selected company refines and brush-up the business model idea registered in the system in step 3 and completes it. The work can be performed on the open innovation system 100. Among the selected companies, the company that has submitted the proposal (participating company) 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 a collaborating business from among the participating companies (step S147). The recruiting company determines a scheme of cooperation with the selected company (candidate company), conditions for cooperation, etc., and makes a contract (step S148). The recruiting company and the cooperating company (contracted candidate company) promote the business model development and the commercialization thereof by the collaboration (step S149).

  FIG. 7 is a flowchart showing the procedure of the management resource procurement type. Master information is registered in the open innovation system 100 by a company (a search company and a proposed company) participating in the open innovation system 100 (step S151). The said process is the same as that of step S141 of an idea open type | mold. The recruitment guidelines are registered in the open innovation system 100 by the searching company (step S152). In the recruitment guidelines, search criteria shall be described as detailed as possible, including technical issues and technical requirements such as required specifications and accuracy, for management resources to be searched. As search conditions, search keywords and search expressions that can be used for search are input. The searching company registers the business model idea at this point in the open innovation system 100. In addition, regarding the business model idea registered here, the management resource element currently held and the management resource element (missing piece) to be searched from now shall be distinguishable. The open innovation system 100 extracts a company that matches the search condition based on the registered search condition. The open innovation system 100 creates a long list and a list in which extracted companies are put together into one (step S153). At this point, the database is searched under loose conditions. For example, a search expression in which a plurality of keywords are combined by the disjunction operator is searched. When a search expression in which a plurality of keywords are combined by an AND operator is specified, a search is performed using a search expression in which one or two keywords are wrong. If the search is performed under loose conditions, but the number of hits is large, a narrowing search is performed. Therefore, a company which firmly describes the management resources registered in step S151 is likely to be hit. The searching company selects a company to request a proposal from among the companies listed in the long list (step S154). The selection here is premised on the manual. In the selection, in addition to the viewpoint of simply narrowing down the search condition to more satisfied companies, factors such as corporate culture, human resources, etc. may be taken into consideration as factors that the search company considers important in promoting collaboration. The short list is a list of companies that narrow down the companies included in the long list. A search company takes RFP (Request For Proposal: proposal request form) including the proposal request items and the form of the proposal you want to propose in consideration of the profile and management resources of the companies in the short list. create. The searching company presents the RFP to the companies included in the short list, and confirms the proposal intention (step S155). The confirmation can be performed through 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 shown the intention to propose, and to make it refer to more detailed contents. The company that has shown the intention to make a proposal (the proposal company) creates a proposal in accordance with the RFP and submits it to the search company (step S156). The submission of the proposal can be performed through the open innovation system 100. The search company will make a final selection of the proposal company based on the contents of the proposal and the result of the interview by interview. While searching for candidate companies, the searching company negotiates conditions and the like in the case of collaboration (step S157). The searching company and the searching company determine a scheme of cooperation, conditions for cooperation, etc., and make a contract (step S158). The searching company and the searching company promote business model development and commercialization through collaboration (step S159).

  The open innovation system 100 supports the progress of an idea solicitation type and a management resource procurement type process. The open innovation system 100 is a system for matching companies looking for partners through the above-mentioned process. When matching companies, at first the frontier is expanded, and many companies may refer to data on matching. Companies are narrowed down as the process progresses. Therefore, authority control in accordance with the progress of the process is required.

  Explain the need for authority control in detail. In the case of business resource procurement type and idea solicitation type, there are multiple companies (application companies) who apply for one company (calling company) calling for collaboration. The recruiting company contracts with one of the applicant companies. The recruiting company does not want to disclose business model information and management resource information that would reveal the purpose of the search to all applicant companies from the beginning. It is because there is a risk that the strategic intention leaks what you are trying to do. In order to avoid the risk, it is inevitable that disclosure will be made only to the narrowed candidate companies as the candidate companies are narrowed down. Then, NDA (Non-disclosure agreement) will be concluded with the finalists, and final negotiations for the deal will be made. On the other hand, even for applicant companies, even though they have not been selected, it is impossible to reveal all the technical data and know-how from the beginning. Therefore, it is necessary to control the information to be disclosed according to the progress of screening. The above is the background for which it is necessary to control fine-grained information disclosure for both recruiting companies and applicant companies.

  Next, data handled by the open innovation system 100 and processing using the data will be described. Some of the databases described below have outlines (columns) and details (columns) for the same name data. The data to be released widely is outlined, and by narrowing down the companies that release 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 by the database server 2 will be described. FIG. 8 is an explanatory view showing an example of a database stored by 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. A definition master DB 31, a BM attribute DB 32, a PS attribute DB 33, an FP attribute DB 34, a CT technology attribute DB 35, an idea solicitation DB 36, an idea applicant company DB 37, a resource solicitation DB 38, and a company list DB 39 are stored. The database server 2 further includes a group DB (group information) 40, an access authority DB 41, a BM authority DB 42, a PS authority DB 43, an FP authority DB 44, a CT authority DB 45, and a management resource authority DB 46 as a database used to control the access authority. , BM default DB 47, PS default DB 48, FP default DB 49, CT default DB 50, and management resource default DB 51 are stored.

  FIG. 9 is an explanatory view showing an example of the user master DB 21. As shown in FIG. The user master DB 21 is a database that stores basic information of the user. 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 that is an ID that can uniquely identify the user. The name column stores the user's name. The e-mail string stores the e-mail address of the user. The belonging ID column stores the ID of the department to which the user belongs. The type column stores the type of user. The type is, for example, a user, an operation manager, or a system manager. The authority for the database differs depending on the type of user. Users are restricted from viewing and editing data related to themselves and data other than the data of the organizations and groups to which they belong. The administrator can view and edit all DBs except the master DB. The administrator can refer to the master DB but can not edit it. The system administrator can view and edit all DBs.

  FIG. 10 is an explanatory view showing an example of the department master DB 22. As shown in FIG. The department master DB 22 is a database that stores basic information of departments. The department is an organization that belongs to a company (company). The department master DB 22 includes a department ID column, a department signature column, and a company ID column. The department ID column stores a value that can uniquely identify a department. The department ID has a unique value across multiple companies. For example, a part of a department ID includes a company ID that can uniquely identify a company. The department name string stores the department name. The company ID column stores the company ID of the company to which the department belongs.

  FIG. 11 is an explanatory view showing an example of the company master DB 23. The company master DB 23 is a database that stores basic information of a company. Company master DB 23 includes company ID column, name column, URL column, head office address column, representative column, establishment date column, capital column, sales column, profit column, closing period column, employee number column, and industry Includes industry columns. The company ID column stores a company ID that can uniquely identify a company. The name column stores the name of a company. The URL column stores the URL (Uniform Resource Locator) of the Internet homepage regarding the company. The head office address column stores the address of the office address of the company. The representative column stores names of company representatives, for example, representative directors. The establishment date column stores 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 a company. The profit column stores the profit of the company. The profit column includes the operating income column, the ordinary income column, and the net income column. The operating profit column stores the amount of operating profit of the company. The ordinary income column stores the amount of ordinary income of the company. The net income column stores the amount of net income of the company. The closing period column stores the closing period of the company. The employee number column stores the number of employees in a company. The industry / industry column stores the industry / industry to which the company belongs.

  FIG. 12 is an explanatory view showing an example of the company business DB 24. As shown in FIG. The company business DB 24 is a database for storing basic information on the business conducted by the company. Company business DB 24 includes company ID column, business ID column, name column, value column to be provided, main product / service column, main customer column, main customer column, main vendor column, competitor column, base column, And a tree ID column. The company ID column stores a 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 provided value column stores the value that the company provides to the customer by the business. The main product / service column stores the main products and services in the business. The main customer line stores the main customers of the business. The main customer column stores the main customers in the business. The main supplier row stores the main suppliers in the business. The competitor column remembers competitors in the business. Base column remembers the base in the business. Base columns include R & D columns, production columns, sales columns, and distribution columns. The R & D column stores information on R & D bases in the business. The production column stores information on production bases 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. The tree ID stores the tree ID of the corresponding tree when the structure of the business is defined in the above three-layer structure. If the business structure is not defined in a three-tier structure, the value of the tree ID is null (NULL).

  FIG. 13 is an explanatory view showing an example of the management resource DB 25. As shown in FIG. The management resource DB 25 is a database that stores management resources of a company in association with a 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 searched 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 specific contents of resources. The management resource element row includes a summary row and a detail row. The outline column stores the outline of the management resource element. The detail column stores the details of the business resource element. The classification column stores the classification of management resources. The classification sequence includes classification 1 sequence and classification 2 sequence. The Class 1 column stores the process / function to which the management resource element belongs or is associated with the value chain. The second column of classification stores the contents of management resources selected from preset classifications. Class 1 and Class 2 are stored in code. The code will be described later. The to-be-searched keyword string stores keywords for management resources. When a management resource is subjected to a keyword search, it is important to set an appropriate keyword because a search target keyword is a search target.

  FIG. 14 is an explanatory view showing an example of the resource classification master DB 26. As shown in FIG. The resource classification master DB 26 is a database that stores management resource classifications in association with codes. The resource classification master DB 26 includes a classification number string, a classification name string, a sequential number string, and a classification text string. The classification number sequence stores numbers indicating resource classifications. The classification name column stores the name of the resource classification. The order number sequence stores the display order when displaying the resource classification. The classification text string stores the contents of the classification.

  FIG. 15 is an explanatory view showing an example of the tree DB 27. As shown in FIG. The tree DB 27 is a database that stores information of a tree that expresses a 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 a tree ID specifying a tree. The tree ID uses, for example, the node ID of the root node of the tree. The name column stores the name of the tree. The step sequence stores the progress of the business model. For example, when the business corresponding to the business model is started, the cutover is stored. The owner ID column stores the user ID of the user who registered the data.

  FIG. 16 is an explanatory view showing an example of the node DB 28. As shown in FIG. The node DB 28 is a database that stores nodes that constitute a tree. The node DB 28 includes a node ID sequence and a type code sequence. The node ID column stores a node ID that can uniquely identify a node. The type code string stores a type code indicating the type of node. The type code will be described later.

  FIG. 17 is an explanatory view showing an example of the type code master DB 29. As shown in FIG. The type code master DB 29 is a database that stores the type of node and the type code string in association with each other. The type code master DB 29 includes a type string and a type code string. The type column stores the type of node. 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 view showing an example of the node connection DB 30. As shown in FIG. 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 tree IDs of trees including nodes. The node ID column stores node IDs. The upper node string stores the node ID of the upper node. The lower node string stores node IDs of lower nodes. The branch number sequence stores branch numbers of nodes. Branch numbers are assigned to identify multiple same nodes when they are included in the same tree. Although it is a principle that only one node is included in the same tree, it is possible to describe a plurality of the same node in the same tree for the convenience of expression and the convenience of design. The branch number stores 0 when there are not the same nodes in the same tree. The subtree column stores whether a node is a subtree node. A subtree is a tree in which node details are represented by a tree. If the node is a subtree node, the subtree column stores one. If the node is not a subtree node, the subtree column stores 0.

  FIG. 19 is an explanatory view showing an example of the attribute definition master DB 31. As shown in FIG. The attribute definition master DB 31 stores, for example, a database name in which an attribute is 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 type code string of the node. 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 storing the access authority of the attribute. The default authority DB column stores the name of the database storing the default access authority of the attribute.

  FIG. 20 is an explanatory view showing an example of the BM attribute DB 32. As shown in FIG. The BM attribute DB 32 is a database that stores business model attributes. 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 revenue structure model column, a value providing system column and an owner ID column. The node ID column stores node IDs. 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 association field and industry column memorizes the field and industry to which the business model is related. The provided value column stores the provided value by the business model. The customer / service column stores the customer / service targeted by the business model. The revenue structure model column stores the revenue structure of the business model. The value providing system column stores how a 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 revenue structure model column, and the value providing system column include a summary column and a detail column.

  FIG. 21 is an explanatory view showing an example of the PS attribute DB 33. As shown in FIG. The PS attribute DB 33 is a database that stores product / service attributes. 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 node IDs. The name column stores the names of products and services. The registration date column stores the registration date of data. The category / classification column stores classifications of products or services. The feature / performance column stores the feature / performance of the product / service. The core technology series stores 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 an outline column and a detail column. The contents of the core technology row are the same as the contents of the idea that is an attribute of the core technology described later.

  FIG. 22 is an explanatory view showing an example of the FP attribute DB 34. As shown in FIG. The FP attribute DB 34 is a database for storing 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 node IDs. The name column stores the names of functions and processes. The registration date column stores the registration date of data. The function / process division column stores divisions of functions or processes. The provision mechanism stores the mechanism that provides the function or process. The core technology series stores core technologies that characterize the 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 row and the core technology row include a summary row and a detail row. The contents of the core technology row are the same as the contents of the idea that is an attribute of the core technology described later.

  FIG. 23 is an explanatory view showing an example of the CT technology attribute DB 35. As shown in FIG. The CT technology attribute DB 35 is a database that stores core technology attributes. The CT technology attribute DB 35 includes a node ID column, a name column, a registration date column, a classification column, an idea content column, a supposed application column, a patent status column, and an owner ID column. The node ID column stores node IDs. The name column stores the names of core technologies. The registration date column stores the registration date of data. The classification column stores known or new classifications. The content sequence of ideas stores the content of ideas that are the core of core technology. The postulated application column stores the postulated application of the core technology. The patent status column stores the status of patents. The patent status stores, for example, not filed, under filed, under application preparation, filed, pending examination, in the middle process, granted, etc. The owner ID column stores the user ID of the user who registered the data. In the CT technology attribute DB 35, the content column of the idea includes a summary column and a detail column.

  FIG. 24 is an explanatory view showing an example of the idea solicitation DB 36. As shown in FIG. The idea solicitation DB 36 is a database for storing 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 recruiter ID column, a theme column, a precondition column, an evaluation reference 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 an idea solicitation. The node ID column stores node IDs corresponding to functions / processes and management resources to be included in an idea. The recruiter ID column stores the company ID of the recruiting company. The theme column memorizes the theme of recruitment. The precondition column stores preconditions on recruitment. The evaluation criteria column stores the criteria for evaluating the submitted idea based on what criteria. The resource ID column stores resource IDs of management resources scheduled to be provided by the recruiting company. The step sequence stores the progress status of the recruitment process. The owner ID column stores the user ID of the user who registered the data. Several business model proposals are proposed corresponding to the recruitment theme. These are linked with the idea recruitment ID

  FIG. 25 is an explanatory view showing an example of the idea application company DB 37. As shown in FIG. The idea application company DB 37 stores a company that has applied for an idea solicitation. The idea application company DB 37 includes an idea recruitment 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 an 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 applied idea. The selection result sequence stores the selection results. The owner ID column stores the user ID of the user who registered the data.

  FIG. 26 is an explanatory view showing an example of the resource solicitation DB 38. As shown in FIG. The resource solicitation DB 38 is a database for storing the contents of the management resource solicitation in the management resource procurement type process. The resource recruitment DB 38 includes a resource recruitment ID column, a node ID column, a recruiter ID column, a target ID column, a search condition column, a keyword column, a step column, and an owner ID column. The resource recruitment ID column stores resource recruitment IDs that can uniquely identify resource recruitment. The node ID column stores a node ID corresponding to a business model in which resources to be recruited are used. The recruiter ID column stores the company ID of the recruiting company. The target ID column stores the node ID of the node which is the target of the resource recruitment among the nodes constituting the business model. The search condition column stores search conditions for listing up companies for which an application is to be asked. The search condition is described by analyzing the contents of the description by syntactic analysis or the like, and a search expression is made based on the analysis result. Perform a search based on the set search formula. The keyword column stores keywords used to list up a company that asks for an application. The keywords are used as they are for non-search keywords. The step sequence stores the progress status of the recruitment process. The owner ID column stores the user ID of the user who registered the data.

  FIG. 27 is an explanatory view showing an example of the company list DB 39. As shown in FIG. The company list DB 39 is a database for storing a company (a company extracted as a long list) that asks for an application for resource recruitment. The company list DB 39 includes a resource recruitment ID column, a company ID column, a short column, and a selection result column. The resource recruitment ID column stores resource recruitment IDs. The company ID column stores the company ID of the listed company. The short column stores whether each company has been selected as a short list. For example, in the case of a selected company in the short list, 1 is stored in the short string. In the case of a non-selected company in the short list, 0 is stored in the short string. 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. The RFP is stored in the selection result column of the company that did not submit the proposal for the proposal request. After submission of the proposal, interviews and negotiations will be stored in the selection result of the company that has reached interviews and contract negotiations. Contract conclusion is stored in the selection result column of the company that has reached contract conclusion after interview and contract negotiation.

  FIG. 28 is an explanatory view showing an example of the group DB 40. As shown in FIG. The group DB 40 is a database that stores a group to which an access right is given. 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 a group. The company ID column stores the company ID of the company to be granted when the authority is given to the entire company, ie, all belonging to the company. The department ID column stores the department ID of the department to be assigned when the authority is given in units of departments. The user ID column stores the user ID of the user to be assigned when the authority is granted in units of users.

  FIG. 29 is an explanatory view showing an example of the access authority DB 41. As shown in FIG. The access authority DB 41 is a database storing access authority in node units. The access authority DB 41 includes a node ID column, a resource recruitment ID column, an idea recruitment ID column, a group ID column, and an owner ID column. The node ID column stores the node ID of the authority setting target node. The resource recruitment ID column stores resource recruitment IDs. The idea solicitation ID column stores an idea solicitation ID. The group ID column stores the group ID of the group to which the authority is given. 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 DBs.

  FIG. 30 is an explanatory view showing an example of the BM authority DB 42. As shown in FIG. 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 recruitment ID column, an idea recruitment ID column, a name column, a related field / industry column, a provided value column, a customer / service column, a revenue structure model column, and a value providing system column. The node ID column stores node IDs. The resource recruitment ID column stores resource recruitment IDs. The idea solicitation ID column stores an idea solicitation ID. The name column stores reference authority for the name. The open association field / industry column stores reference authority for related fields / industries. The provided value column stores reference authority for provided value. The customer service column stores reference authority for the customer service. The revenue structure model column stores reference authority for the revenue structure model. The value delivery system column stores reference authority to the value delivery system. In the BM authority DB 42, the provided value column, the customer / service column, the revenue structure model column and the value providing system column include a summary column and a detail column.

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

  FIG. 32 is an explanatory view showing an example of the FP authority DB 44. As shown in FIG. The FP authority DB 44 is a database that stores the reference authority of function and process attributes. The FP authority DB 44 includes a node ID column, a resource recruitment ID column, an idea recruitment ID column, a name column, a function / process classification column, a providing mechanism column, and a core technology column. The node ID column stores node IDs. The resource recruitment ID column stores resource recruitment IDs. The idea solicitation ID column stores an idea solicitation ID. The name column stores reference authority for the name. The function / process division column stores reference authority for the division. The provision mechanism column stores reference authority for the provided mechanism. The core technology row stores reference authority to the core technology. In the FP authority DB 44, the provided mechanism row and the core technology row include a summary row and a detail row.

  FIG. 33 is an explanatory view showing an example of the CT authority DB 45. As shown in FIG. The CT authority DB 45 is a database for storing the reference authority of core technology attributes. The CT authority DB 45 includes a node ID column, a resource recruitment ID column, an idea recruitment ID column, a name column, a classification column, an idea content column, a supposed application column, and a patent application date column. The node ID column stores node IDs. The resource recruitment ID column stores resource recruitment IDs. The idea solicitation ID column stores an idea solicitation ID. The name column stores reference authority for the name. The classification column stores the reference authority for the classification. The content column of an idea stores the reference authority to the content of the idea. The intended use column stores reference authority for the intended use. The patent application date column stores 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 view showing an example of the management resource authority DB 46. As shown in FIG. The management resource authority DB 46 is a database that stores management resource reference authorities. The management resource authority DB includes a company ID column, a resource recruitment ID column, an idea recruitment ID column, a business ID column, a resource ID column, a management resource element column, a classification column, and a searched keyword column. The company ID column stores a company ID. The resource recruitment ID column stores resource recruitment IDs. The idea solicitation ID column stores an idea solicitation ID. The business ID column stores a business ID. The resource ID column stores resource IDs. The management resource element column stores reference authority for the management resource element. The management resource element row includes a summary row and a detail row. The summary column stores the reference authority for the summary. The detail column stores reference authority for details. The classification column stores reference authority for classification. The classification sequence includes classification 1 sequence and classification 2 sequence. The classification 1 column stores reference authority for classification 1. The Class 2 column stores reference authority for Class 2. The to-be-searched keyword string stores reference authority for the to-be-searched keyword.

  Next, in order to facilitate the setting of the reference authority of the attribute, a 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 permission database eliminates the need for the user to set reference permissions for all attributes. The user only needs 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 of the new business 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, two correspondences will be described below. In the idea solicitation type procedure, step S141 corresponds to "entry". Step S142 corresponds to "Recruitment". Step S143 corresponds to "candidate company extraction". Step S144 corresponds to "evaluation · primary selection". Step S145 corresponds to "proposal creation". Steps S146 and S147 correspond to "final selection". Step S148 corresponds to "contract". Step S149 corresponds to "cooperation". In the management resource procurement type procedure, step S 151 corresponds to “entry”. Step S152 corresponds to "Recruitment". Step S153 corresponds to “candidate company extraction”. Steps S154 and S155 correspond to "evaluation and primary selection". Steps S156 and S157 correspond to the "final selection". Step S158 corresponds to "contract". Step S159 corresponds to "cooperation".

  FIG. 35 is an explanatory view showing an example of the BM default DB 47. As shown in FIG. The BM default DB 47 is a database that stores default privileges of business model attributes. 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 provided value column, a customer / service column, a revenue structure model column, and a value providing system column. The ID column stores an ID identifying a record. The type column stores the type of new business development. In the case of the idea solicitation type, "idea" is stored. In the case of management resource procurement type, "management resources" is stored. The type column remembers the company's position on recruitment. In the case of a company that is recruiting, we store "Recruitment". In the case of a company that applies for the recruitment, "application" is stored. The step sequence stores development steps. The name column stores the default reference authority for the name. The open association field / industry column stores the predetermined reference authority for the related field / industry. The provided value column stores the default reference authority for provided value. The customer service column stores a predetermined reference authority for the customer service. The revenue structure model column stores default reference rights to the revenue structure. The Value Delivery System column stores the default reference rights for the value delivery system. In the BM default DB 47, the provided value column, the customer / service column, the revenue structure model column, and the value providing system column include a summary column and a detail column.

  FIG. 36 is an explanatory view showing an example of the PS default DB 48. As shown in FIG. The PS default DB 48 is a database that stores default reference rights of product and 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 identifying a record. The type column stores the type of new business development ("idea" or "management resource"). The type column stores the position ("offer" or "application") of the company for the recruitment. The step sequence stores development steps. The name column stores the default reference authority for the name. The category / classification column stores default reference authority for classification. The feature / performance column stores predetermined reference authority for the feature / performance. The core technology row stores default reference rights to the core technology. In the PS default DB 48, the feature / performance column and the core technology column include a summary column and a detail column.

  FIG. 37 is an explanatory drawing showing an example of the FP default DB 49. As shown in FIG. The FP default DB 49 is a database that stores default reference authority of function and 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 division column, a provision mechanism column, and a core technology column. The ID column stores an ID identifying a record. The type column stores the type of new business development ("idea" or "management resource"). The type column stores the position ("offer" or "application") of the company for the recruitment. The step sequence stores development steps. The name column stores the default reference authority for the name. The function / process division column stores the default reference authority for the division. The provision mechanism column stores the default reference authority for the provided mechanism. The core technology row stores default reference rights to the core technology. In the FP default DB 49, the provided mechanism row and the core technology row include a summary row and a detail row.

  FIG. 38 is an explanatory view showing an example of the CT default DB 50. As shown in FIG. The CT default DB 50 is a database that stores default reference rights of core technology attributes. The CT default DB 50 includes an ID column, a type column, a type column, a step column, a name column, a classification column, an idea content column, a supposed application column, and a patent status column. The ID column stores an ID identifying a record. The type column stores the type of new business development ("idea" or "management resource"). The type column stores the position ("offer" or "application") of the company for the recruitment. The step sequence stores development steps. The name column stores the default reference authority for the name. A partition column stores the default reference authority for the partition. The content column of an idea stores the default reference authority to the content of the idea. The intended use column stores the default reference authority for the intended use. The patent status column stores the predetermined reference authority to the 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 view showing an example of the management resource default DB 51. As shown in FIG. The management resource default DB 51 is a database for storing predetermined 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 identifying a record. The type column stores the type of new business development ("idea" or "management resource"). The type column stores the position ("offer" or "application") of the company for the recruitment. The step sequence stores development steps. The management resource element column stores a predetermined reference authority to the management resource element. The management resource element row includes a summary row and a detail row. The summary column stores the default reference rights to the summary. The Detail column stores the default view rights for the details. The classification column stores the default reference authority for the classification. The classification sequence includes classification 1 sequence and classification 2 sequence. The Class 1 column stores the default reference rights for Class 1. The classification 2 column stores the default reference authority for classification 2. The to-be-searched keyword column stores a predetermined reference authority for the to-be-searched keyword.

  Next, processing performed by the main server 1 will be described. FIG. 40 is a flow chart showing an example of the procedure of the entry process. Entry processing is performed by all companies serving as 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 the user has selected the input of the business details (step S2). When the CPU 11 determines that the user selects the input of the business details (YES in step S2), the CPU 11 outputs a business information input screen (step S3). The CPU 11 determines whether the user has selected data registration (step S4). If the CPU 11 determines that the user has not selected data registration (NO in step S4), the CPU 11 determines whether a library is selected (step S5). If 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 is selected (YES in step S5), the business model value provision process library screen is output (step S6). The CPU 11 determines whether any pattern of the library is selected (step S7). If the CPU 11 determines that any pattern of the library is not selected (NO in step S7), the process returns to step S3. If the CPU 11 determines that any pattern of the library is selected (YES in step S7), the CPU 11 outputs a tree creation screen to be performed using the selected pattern (step S8). The CPU 11 determines whether or not storage of a tree is instructed (step S9). If the CPU 11 determines that storage of a tree is not instructed (NO in step S9), the process returns to step S3. If the CPU 11 determines that storage of a tree is instructed (YES in step S9), the tree data is stored (step S10). The CPU 11 returns the process to step S3. When the CPU 11 determines that the user selects data registration (YES in step S4), the business information input by the user is stored 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 basic information is stored (step S12). The CPU 11 determines whether the business information is stored in a 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 it is determined that the business information is not stored in the temporary storage area (NO in step S13), the CPU 11 ends the entry process.

  Next, I will explain the process of idea development type business development. FIG. 41 is a flow chart showing an example of the procedure of the recruitment information input process. The CPU 11 outputs an input screen for inputting recruitment information (step S21). The CPU 11 acquires recruitment information input by the user (step S22). The CPU 11 acquires 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 flow chart showing an example of a procedure of node attribute output processing. The node attribute output process is a process that can be executed when a company that is planning to apply for refers to recruitment information. This is a process that is executed when requested for the node attribute associated with the recruitment information, for example, the content of the function / process. The CPU 11 acquires the recruitment ID of the selected recruitment 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 an attribute DB and an authority DB associated with the acquired type code from the attribute definition master DB 31 (step S33). The CPU 11 acquires 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 the non-disclosure item in the attribute information based on the reference authority (step S36). Rewriting, for example, replaces a non-disclosure item with the string "non-disclosure". Undisclosed items Make all characters contained in a single character (such as * or #) or blank. Make non-disclosure items NULL. The CPU 11 outputs attribute information (step S37).

  FIG. 43 is a flow chart showing an example of the application information input process. The CPU 11 outputs a screen for inputting the content of the proposed business model (step S41). The CPU 11 determines whether tree creation has been selected (step S42). When the CPU 11 determines that tree creation is selected (YES in step S42), the tree creation screen is output (step S43). The CPU 11 generates data (such as node connection data) attached to the created tree (step S44). The CPU 11 returns the process to step S41. If the CPU 11 determines that tree creation is not selected (NO in step S42), it determines whether registration is selected (step S45). When the CPU 11 determines that the registration is selected (YES in step S45), the data of the business model and the data of the created tree are stored (step S46). The CPU 11 stores the reference authority (step S47). The CPU 11 ends the application information input process. When it is determined that the registration is not selected (NO in step S45), the CPU 11 ends the application information input process.

  FIG. 44 is a flow chart showing an example of the procedure of the primary screening process. The CPU 11 outputs a list screen of companies that have applied for the recruitment (step S51). The CPU 11 determines whether or not the detail display button is selected on the list screen (step S52). If the CPU 11 determines that the detail display button is selected (YES in step S52), the CPU 11 outputs a detail content screen (step S53). The CPU 11 determines whether or not the return button is selected on the detail content screen (step S54). If the CPU 11 determines that the return button is selected (YES in step S54), the process returns to step S51. If the CPU 11 determines that the return 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 the selection button is selected (step S55). When it is determined that the selection button is selected (YES in step S55), the CPU 11 stores the fact that the selection button is selected in the idea application company DB 37 (step S56). If the CPU 11 determines that the selection button is not selected (NO in step S55), the CPU 11 determines whether the end button is selected (step S57). If 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 is selected (YES in step S57), the selected company is notified (step S58), and the primary screening process is ended. Notification to the selected company is performed, for example, by electronic mail.

  FIG. 45 is a flow chart showing an example of the procedure 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 content 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 recruitment ID and the node ID from the BM authority DB 42 (step S63). The CPU 11 rewrites the 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 the detailed content screen (step S65).

  FIG. 46 is a flow chart showing an example of the procedure of the selection compliance process. The CPU 11 outputs a notification screen indicating that it has been selected (step S71). The CPU 11 determines whether the acceptance button is selected on the notification screen (step S72). When the CPU 11 determines that the acceptance button is selected (YES in step S72), the reference authority is changed (step S73). The CPU 11 notifies the recruitment company (step S74), and ends the selection compliance process. Notification to the recruiting company is performed by e-mail, for example. When the CPU 11 determines that the acceptance button is not selected (NO in step S72), the selection acceptance processing is ended.

  FIG. 47 is a flow chart showing an example of the procedure of contract completion processing. The CPU 11 outputs a list screen of the selected company (step S81). The CPU 11 determines whether the contract completion button is selected on the list screen (step S82). If the CPU 11 determines that the contract completion button is not selected (NO in step S82), the process returns to step S81. If the CPU 11 determines that the contract completion button is 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 a screen used in the above-described processing is shown. The screen used in the entry process will be described. FIG. 48 is an explanatory drawing 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. An input field d011 is a field for inputting basic information of a company, such as a company name, a URL of a home page, and a head office address. The detail button d012 is a button for calling a business information input screen. A registration button d013 is a button for confirming the content and registering the content 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 the basic information.

  FIG. 49 is an explanatory drawing 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 d 021 is a field for entering information relating to the business such as the value to be provided to the customer, the main product / service, and the like. A library display button d022 is a button for calling a business model value provision process library. A registration button d 023 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 the business information.

  FIG. 50 is an explanatory drawing showing an example of the tree creation screen d03. The tree creation screen d03 includes a toolbar d031, an editing area d032, a save button d033, and an end button d034. The toolbar d 031 includes various tools for creating and editing a tree. Users create and edit trees using tools. The editing area d032 is an area for creating / editing a tree. In the case of using a tree registered in advance in the business model value provision process library, the selected tree is displayed in the editing area d032. A save button d033 is a button for saving the created / edited tree. The end button d 034 is a button for ending creation / editing of the tree.

  FIG. 51 is an explanatory diagram of 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. An input field d041 is a field for inputting character attribute information of a business model, such as a name, a related field, and an industry. A disclosure setting field d042 is a field for performing disclosure setting of each item. Non-disclosure indicates that it is not disclosed to other users. Disclosure indicates disclosure to other users. If the check box is checked, it can be disclosed only to users who are limited as disclosed to only users who are in a collaborative relationship. A registration button d043 is a button for determining the content and registering the content in the database. The clear button d 044 is a button for clearing all the input fields d 041. A cancel button d045 is a button for canceling the registration of the business model attribute information. An item overlapping with the input field d021 of the business information input screen d02 may be input on any one of the business information input screen d02 and the business model attribute input screen d04. Also, if the items to be overlapped are already input on one screen, they will be displayed on the other screen even in the case of new creation.

  FIG. 52 is an explanatory drawing 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. An input field d051 is a field for inputting character and / or attribute information of functions and processes, such as names and categories. A disclosure setting field d052 is a field for performing disclosure setting of each item. A registration button d053 is a button for determining the content and registering the content in the database. The clear button d054 is a button for clearing all the input fields d051. A cancel button d055 is a button for canceling registration of function / process attribute information. The screen for inputting the attributes of the product / service and core technology is the same as that of 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 drawing showing an example of the recruitment information input screen d06. The recruitment information input screen d06 includes an input field d061, an available management resource setting field d062, a registration button d063, a clear button d064 and a cancel button d065. An input field d061 is a field for entering recruitment information such as a theme and preconditions. The available management resource setting column d062 is a column for setting a management resource scheduled to be provided when performing a new business based on an offer. 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 the recruitment information.

  When the management resource element displayed in the available management resource setting field d062 is selected, the content can be confirmed and the reference authority can be set. For example, it is assumed that the measurement system excellent in environmental resistance shown in FIG. 53 is registered as a function / process. When the user selects a measurement system having excellent environmental resistance, a 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 DB 44, the disclosure setting field d052 is displayed accordingly. If the reference authority is not registered in the FP authority DB 44, the FP default DB 49 is referred to, and the disclosure setting field d052 is displayed according to the predetermined reference authority. Here, in the idea solicitation type, it is the step of recruitment in the authority setting performed by the recruitment company. Therefore, in the FP default DB 49 shown in FIG. 37, the record of 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 DB 44.

  Subsequently, a screen used in the application information input process will be described. In the application information input process, the screen used when the user of the application company inputs a business model is shown in d03 of the tree creation screen shown in FIG. 50, and in business model attribute input screen d04 shown in FIG. 51 and FIG. This is a function / process attribute input screen d05 or the like. In the application information input process, the user of the application company can set the reference authority using the business model attribute input screen d04 and the function / process attribute input screen d05. Here, in the idea solicitation type, it is the step of recruitment in the authority setting performed by the applicant company. Therefore, in the business model attribute input screen d04, the default value of the disclosure setting corresponds to the record of ID = 12 in the BM default DB 47 shown in FIG. Further, in the function / process attribute input screen d05, the default value of the disclosure setting is in accordance with the record of ID = 12 in the FP default DB 49 shown in FIG.

  Subsequently, screens used in the primary screening process will be described. FIG. 54 is an explanatory drawing showing an example of the application company list screen d07. The application company list screen d07 includes a list d071, a clear button d072 and an end button d073. The list d071 displays a list of application companies. In the list d071, a selection button d0711 and a check box d0712 are provided. 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 a company selected in the primary selection. Check the selected company. The clear button d072 is a button for clearing the check of all the check boxes d0712. The end button d073 is a button for ending the primary screening. When the end button d073 is selected, the application company list screen d07 is closed, and the selected company ID is returned.

  FIG. 55 is an explanatory diagram of an example of the detailed content screen d08. The detailed content screen d08 is a screen that is opened when the selection button d0711 is selected in the application 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 attribute of the proposed business model. In the display column d081, items to be provided that are not disclosed (value to be provided (details), customer / service (details), revenue structure model (details) and value provision system (details) are indicated as "not disclosed") ing. The tree display button d082 is a button for displaying a 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 a proposed business model. A back button d084 is a button for returning to the application company list screen d07. When the selection button d083 is selected on the detailed content screen d08, the result is reflected in the check box d0712 of the list d071 when returning to the application company list screen d07.

  The applicant company that has been primarily selected on the application company list screen d07 is requested to make a presentation that the primary selection has been made. When the applicant company accepts the primary selection, the selection compliance process changes the reference authority of the data of the applicant company that has accepted the primary selection. In the above-described example, the recruiting company can refer to the value to be provided (detail), the customer / service (detail), the revenue structure model (detail), and the system for providing the value (detail) in the detailed content screen d08.

  Furthermore, if a contracting company is contracted after the presentation company is first selected after the presentation company is selected, the contract completion process changes the reference authority of data on the company. For example, the mechanism of providing functions and the core technology for providing functions, which are attributes of functions and processes, are only disclosed in outline at the application stage, respectively, but the contracting company can also refer to the details of each. .

  Next, processing in business resource procurement type business development will be described. In business resource procurement type business development, it is premised that the recruiting company has designed the business model to some extent. In the following description, it is assumed that the recruitment company has designed a business model and has also created a tree showing the overall structure. However, with regard to some management resources, it is decided to cooperate with other companies to procure, and the open innovation system 100 is going to recruit.

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

  FIG. 57 is a flow chart showing an example of the procedure of the long list creation process. The CPU 11 acquires the search condition and the search keyword for the recruitment which is the control from the resource recruitment DB 38 (step S101). The CPU 11 generates a search expression from the acquired search condition and search keyword (step 102). When the acquired search condition is a sentence, the CPU 11 analyzes the language and generates a search expression. The CPU 11 outputs a search screen in which the generated search formula is embedded (step S103). The user changes the search formula if necessary and gives a search instruction. The CPU 11 performs a search (step S104). The CPU 11 outputs the long list generated from the search result (step S105). The CPU 11 ends the long list creation process.

  FIG. 58 is a flow chart showing an example of the procedure of short list creation processing. The CPU 11 outputs a short list creation screen (step S111). The short list creation screen includes a long list. The CPU 11 determines whether or not the detail display is selected on the short list creation screen (step S112). When it is determined that the detail display button is selected (YES in step S112), the CPU 11 outputs a detail content screen (step S113). The detailed content screen displays basic information of the selected company. The detailed content screen is a screen similar to the basic information input screen d01. The CPU 11 determines whether or not the return button is selected on the detail content screen (step S114). If the CPU 11 determines that the return button is selected (YES in step S114), the process returns to step S112. If the CPU 11 determines that the return button is not selected (NO in step S114), the process proceeds to step S115. When it is determined that the detail display button is not selected (NO in step S112), the CPU 11 determines whether the selection button is selected (step S115). When it is determined that the selection button is selected (YES in step S115), the CPU 11 stores the fact of 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 the end button is selected (step S117). If 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 is selected (YES in step S117), the reference authority is changed (step S118). The CPU 11 performs group setting (step S119). The CPU 11 generates group data including the selected company, and stores the group data in the group DB 40. The CPU 11 sets the generated group ID of the group in the access authority DB 41 as the group ID of the record including the resource recruitment ID to be processed. This allows selected companies to access data on resource recruitment. The CPU 11 ends the short list process.

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

  FIG. 60 is a flow chart showing an example of the final selection process. The CPU 11 outputs the final selection screen (step S131). The final selection screen is a company included in the short list, and a list of companies that have made a proposal is displayed. 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 a predetermined reference authority (step S133). The CPU 11 stores the reference authority (step S134).

  If a contract for co-operation is concluded as a result of negotiations with a company remaining in final selection, the CPU 11 performs contract completion processing. The processing procedure and the like are the same as the contract completion processing described above.

  Next, an example of a screen used in the above-described processing is shown. The screen used in the search registration process will be described. FIG. 61 is an explanatory diagram of an example of the resource recruitment requirement entry screen d09. The resource recruitment essential item 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 object confirmation column d091 is a column where management resources to be recruited are displayed. FIG. 61 shows the case of recruiting core technologies. As described above, since the search registration process is activated after the design of the business model is finished, it is premised that the contents displayed in the recruitment object confirmation column d091 need not be changed. However, the contents may be changed as needed. In the search condition input field d092, technical issues, required specifications and accuracy are described for management resources to be searched (searched). The search keyword input field d093 describes a search keyword for the management resource to be searched (searched). A registration button d094 is a button for registering search conditions and search keywords. 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 for the search keyword input field d093. The cancel button d 096 is a button for canceling the registration of the resource recruitment guideline.

  The screen used in the short list creation process will be described. FIG. 62 is an explanatory drawing 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 by the long list creation process. A selection button d1011 and a check box d1012 are provided in the list d101. The selection button d1011 is a button for displaying basic information of a company extracted as a long list. The check box d1012 is for designating a company selected as the short list. Check the selected company. The clear button d102 is a button for clearing the check 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 the present embodiment, it is possible to control information to be disclosed at each step from recruitment to contract conclusion. As a result, it is possible for a recruiting company to recruit a collaborating company without unnecessarily disclosing its own information to a partner company. Similarly, the applicant company can apply for a collaboration company without unnecessarily disclosing its own information to the partner company.

  Also, in the open innovation system 100, a business model is represented by a multi-level tree structure. Therefore, it becomes possible to handle various business models in a unified manner.

The technical features (component requirements) described in the respective embodiments can be combined with each other, and by combining, new technical features can be formed.
It should be understood that the embodiments disclosed herein are illustrative in all respects and not restrictive. The scope of the present invention is indicated not by the meaning described above but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the 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 Resources 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 Technology Attribute DB
36 Idea Recruitment DB
37 Idea Application Company DB
38 Resources 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 Resources Authority DB
47 BM default DB
48 PS Default DB
49 FP default DB
50 CT Default DB
51 Management Resources Default DB
3 Firewall N Network N1 Local Network

Claims (5)

Information of provided value definition, information of a value providing scheme including products, services, functions, or processes required to configure the provided value definition, and management resources required to construct the value provided scheme Obtain business information that is associated with the
Obtain information on each provision value definition, information on each value provision scheme, and authority information for each management resource information,
A computer characterized by causing a computer to execute processing of determining whether or not to output information on each provision value definition, information on each value provision scheme, and information on each management resource based on the acquired authority information. program. Acquire recruitment information about the business information,
Set up the authority information based on the progress of recruitment,
Whether to output information on each provision value definition included in the business information, information on each value provision scheme, and information on each management resource to the applicant for the recruitment based on the set authority information The computer program according to claim 1, characterized in that: Get group information corresponding to the recruitment information,
It is determined based on the group information whether the user who requested the business information corresponding to the recruitment information is the applicant or not.
When it is determined that the user is the applicant, information of each provision value definition included in the business information, information of each value provision scheme, and information of each management resource are output based on the authority information. The computer program according to claim 2, characterized by Information of provided value definition, information of a value providing scheme including products, services, functions, or processes required to configure the provided value definition, and management resources required to construct the value provided scheme A first acquisition unit that acquires business information associated with the information of
A second acquisition unit that acquires information on each provision value definition, information on each value provision scheme, and authority information on information on each management resource,
A determination apparatus comprising: a determination unit that determines whether to output information on each provided value definition, information on each value provision scheme, and information on each management resource based on the acquired authority information. . The computer is
Information of provided value definition, information of a value providing scheme including products, services, functions, or processes required to configure the provided value definition, and management resources required to construct the value provided scheme Obtain business information that is associated with the
Obtain information on each provision value definition, information on each value provision scheme, and authority information for each management resource information,
A determination method comprising: determining whether to output information on each provision value definition, information on each value provision scheme, and information on each management resource based on the acquired authority information.

Images