KR100743150B1 - Customized and Automated Technology Roadmapping System - Google Patents

Abstract

The present invention relates to a system for automating the creation of a technology roadmap. The present invention proposes a systematic algorithm linking markets, products, and technologies, and in particular, makes decisions on corporate management and technology development by proposing a roadmap in a form suitable for the purpose of the user. It provides an effective system of drawing roadmaps to support

Technical roadmap production system according to the present invention includes a database management module for inputting, modifying, searching for information about technology and products in the enterprise; A roadmap generation module that automatically creates different types of roadmaps according to the purpose of drawing and utilizing existing technologies and product databases; It consists of three modules, a road map search module that can search and modify the road map stored in the database.

The system proposed in the present invention organizes the technical roadmap creation process, proposes 8 standardized roadmaps, and develops algorithms that provide appropriate roadmap templates according to the purpose. It is easy to create and update roadmap, and it helps to share related information actively by web-based characteristics.

Technical Management, Technical Roadmap, Creation Purpose, Customization, Web Based Systems

Description

Technical roadmap automatic generation system according to the purpose of creation {Customized and Automated Technology Roadmapping System}             

1 is a diagram defining the most common product-technology roadmap based on market, product, technology and R & D information.

FIG. 2 is a diagram illustrating a technology roadmap generation process in a market-based future-oriented technology roadmap approach that is most commonly accepted by a company among technology roadmap creation methods.

3 is a view for explaining the configuration of a module for creating a technical road map according to the present invention.

FIG. 4 is a diagram for describing a structural diagram of a technology roadmap preparation system configured to execute the modules of FIG. 3.

FIG. 5 is a diagram illustrating a system configuration for executing description prediction information input in a first database administration module of the module of FIG. 3.

FIG. 6 is a diagram for describing a system configuration for executing technology prediction information update in the first database management module of the module of FIG. 3.

FIG. 7 is a diagram for describing a system configuration for executing technical information and product information search in the first database management module of the module of FIG. 3.

FIG. 8 is a diagram illustrating a system configuration for executing customization according to a creation purpose in a second roadmap generation module of the module of FIG. 3.

FIG. 9 is a diagram illustrating a process of deriving a standardized road map in the process of performing customization in FIG. 8.

FIG. 10 is a diagram illustrating in detail information provided by the standardized roadmap derived from FIG. 9.

FIG. 11 is a diagram showing an algorithm for designing a customized execution system configuration in FIG. 8.

FIG. 12 is a diagram for describing a system configuration for inputting information required for roadmap generation in a second roadmap generation module of the module of FIG. 3.

FIG. 13 is a diagram for describing a system configuration for executing substantial roadmap generation in a second roadmap generation module of the module of FIG. 3.

FIG. 14 is a diagram for describing a system configuration for executing a third roadmap retrieval module among the modules of FIG. 3.

FIG. 15 is a diagram illustrating a process of receiving technical information by an input engine in FIG. 5 and storing the technical information in a technical database.

FIG. 16 is a diagram illustrating a system screen provided to a user for inputting technical information.

FIG. 17 is a diagram illustrating a process of updating and storing information of a database by receiving an update target information from a user by an update engine in FIG. 6.

FIG. 18 is a diagram illustrating a process of a search engine of FIG. 7 searching for target information from a database and outputting the result to a user.

FIG. 19 is a diagram illustrating a process in which a customization engine of FIG. 8 configures an input information user interface for creating a roadmap suitable for the purpose of the roadmap after receiving the purpose of creating the roadmap from the user and storing the input information user interface in the roadmap template database. to be.

FIG. 20 illustrates a process of receiving basic information for constructing a road map by the data-input engine in FIG. 12 when the purpose of creation is selected as “forecasting” in FIG. It is a figure.

FIG. 21 is a diagram illustrating a system screen for receiving basic information from a user by applying the process of FIG. 20.

FIG. 22 is a diagram for inputting basic information, a preparation period, and detailed information for constructing a roadmap by a data-input engine in FIG. 12 when the purpose of creation is selected as “Product Planning” in FIG. 19. A diagram illustrating the process of receiving and storing in a database.

FIG. 23 is a diagram for inputting basic information, a creation period, and detailed information for constructing a road map by a data-input engine in FIG. 12 when the purpose of creation is selected as “forecasting” in FIG. 19. A diagram illustrating the process of receiving and storing in a database.

FIG. 24 is a diagram illustrating a system screen for receiving detailed information about a product and a technology from a user and storing it in a database through the process shown in FIG. 23.

FIG. 25 illustrates a case in which a data-input engine of FIG. 12 receives basic information and a creation period for constructing a roadmap, and stores the data in a database when the purpose of creation is selected as “Administration” in FIG. 19. A diagram illustrating the process.

FIG. 26 is a diagram for describing a process of a build-up engine in FIG. 13 calling information stored in a database, creating a road map, and presenting the result to a user through the process of FIG. 9.

FIG. 27 is a diagram illustrating a system screen outputting a product family map to a user among the standardized road maps of FIG. 9 provided by the authoring engine of FIG. 13.

FIG. 28 is a diagram illustrating a system screen outputting a product driver map of the standardized road map of FIG. 9 provided by the authoring engine of FIG. 13 to a user.

FIG. 29 is a diagram illustrating a system screen for outputting a product roadmap among the standardized roadmaps of FIG. 9 provided by the creation engine of FIG. 13 to a user.

FIG. 30 is a diagram illustrating a system screen outputting a product evolution roadmap to a user among the standardized roadmaps of FIG. 9 provided by the creation engine of FIG. 13.

FIG. 31 is a diagram illustrating a system screen outputting a technology portfolio map to a user among the standardized road maps of FIG. 9 provided by the creation engine of FIG. 13.

FIG. 32 is a diagram illustrating a system screen outputting a technology position map of the standardized road map of FIG. 9 provided by the authoring engine of FIG. 13 to a user.

FIG. 33 is a diagram illustrating a system screen outputting a technology roadmap among the standardized roadmaps of FIG. 9 provided by the authoring engine of FIG. 13 to a user.

FIG. 34 is a diagram illustrating a system screen outputting a technology trend roadmap to a user among the standardized roadmaps of FIG. 9 provided by the creation engine of FIG. 13.

FIG. 35 is a diagram illustrating a process of retrieval engine of FIG. 14 calling a corresponding road map after receiving a type of a search target product, a search period, and a search road map from a user, and visualizing the corresponding road map.

{Description of major symbols in the drawing}

100: database management module 101: input engine

102: Update Engine 103: Search Engine

200: roadmap generation module 201: customization engine

202: data entry engine 203: creation engine

300: Search Module 301: Search Engine

400: Database 401: Technical Database

402: Product Database 403: Roadmap Template Database

404: roadmap database 500: user interface

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for automatically generating technology roadmaps according to a production purpose, and more particularly, to an apparatus that enables technology and business to be connected by creating a technology roadmap.

In the modern society, where the characteristics and structure of the market change frequently, the cycle of technology development is rapidly shortened, and the life cycle of products is significantly reduced, in order to succeed, the market and technology are predicted and based on long-term and strategic changes. You need to plan your technology and products. In particular, with the advent of the information age, knowledge, or technology, has been taken as an important factor for the survival of the enterprise. In this respect, the importance of strategic technology management is emphasized. Techniques and methodologies to support strategic technology management vary widely, including value curves, quality function deployment (QFD), TRIZ, technology tree, and design of experiment (DOE). In recent years, attention has been focused on technology roadmaps, in which not only the technology and business are directly connected, but both the visualization method and the creation process are very flexible approaches. At the industry level, technology roadmaps help predict future technological progress and guide technology development based on an exploratory or normative approach.At the enterprise level, the technology roadmap can be used to track market, product and technology changes over time. Provide graphical means for reviewing and expressing relationships between them. Therefore, it can be said that the technology roadmap preparation system can be usefully used for technology prediction at the industrial level or technology and product planning and management at the enterprise level.

Regarding the technical roadmap, the geometrical form of the technical roadmap currently being presented is very diverse. The technology roadmap can be prepared in various forms such as product-technology roadmap, promising technology roadmap, and issue-related roadmap, depending on the content of the subject. There are numerous roadmaps in addition to the characteristics of individual companies.

1 is the most general form of technical roadmap, which corresponds to most technical roadmaps created at the enterprise level. This is a network chart consisting of time and layer, which consists of three layers: market, product and technology, sometimes including research and development projects. This connects the market with the product, the business and the technology in that it derives the necessary technology that needs to be developed in the context of the product. Network charts can provide useful information by directly connecting markets, products, and technologies, but there are limitations in terms of information quality. In other words, there is a need for a method of processing the same information one step to present a more diverse road map. In fact, companies use various forms of roadmaps depending on the characteristics of individual companies or the purpose of creating roadmaps. However, since the roadmap type design is very qualitative, depending on the judgment of technology planners and managers, it is urgent to provide guidelines for the standardized roadmap type. This system proposes eight standardized roadmaps based on analysis targets, analysis methods, and analysis periods to systematically support technical roadmap types.

FIG. 2 is a diagram illustrating a technology roadmap generation process in a market-based future-oriented technology roadmap approach that is most commonly accepted by a company among technology roadmap creation methods.

In addition to the representation of the roadmap, the way of creating the roadmap is also very flexible. The roadmap creation method can be largely divided into retrospective road mapping, which uses road information to create a road map, and future road mapping, which generates a road map based on predictions and plans. However, the most common method is a market-based future road mapping technique. The market-based future technology road mapping process consists of three phases: preparatory phase, preparation phase and follow-up phase. In the preparatory phase, the prerequisites are identified, work teams and support groups are defined, the objectives and needs of the technical roadmap are defined, and the time frame for the technical roadmap. In the preparation stage, the roadmap report is completed by defining the products to which the roadmap will focus, deriving the product characteristics and related technical areas required to satisfy customer's needs, searching for technical alternatives, and selecting specific technical alternatives. In the follow-up phase, the technical roadmap will be verified, an action plan for obtaining technical alternatives, and the roadmap will be periodically checked and updated. Existing studies on this technology roadmap approach are rather conceptual and abstract, and do not provide practical help to companies seeking to create a technology roadmap for the first time. This system adopts the most general approach among various technical roadmap approaches, organizes them and embodies them so that even companies new to the technical roadmap can easily create and use them.

To date, the creation of technical roadmaps has often depended solely on expert manual work or on simple general-purpose software such as MS Word, MS Power Point, and MS Excel. In this case, not only is it difficult to update the roadmap, but it is also difficult to share information related to the roadmap. There are also risks of errors that can occur in terms of human work, and it is difficult for companies that operate across two or more industries to identify technical relationships that humans cannot find. In other words, in order to spread the technology roadmap technique more widely, it is necessary to develop specialized software that assists in generating, storing, sharing, and updating the roadmap. Of course, simple word processing, spreadsheet or graphic package is enough in the initial stage of roadmap generation, but it is necessary to develop roadmap creation system for the convenience of updating and sharing in the later stage of roadmap creation. Nevertheless, until now, the development of specialized systems that support roadmap creation has been sluggish due to the flexibility of the roadmap creation process. Also, in the process of creating roadmaps, direct communication or coordination between people is inevitable, so the system alone is difficult to produce desirable results. However, due to the volatile market environment and rapidly changing technology environment, product planning and technology planning are complicated and changed, and there is an increasing need for specialized assistive systems that can easily reflect the changes in the roadmap.

Specialized systems for creating technical roadmaps developed and commercialized to date are mainly provided in the form of solutions. In other words, the roadmap expert identifies the industry and business process to which the company belongs and builds a 100% personalized technology roadmap system for the company. However, the introduction of such solutions is expensive and time-consuming, so certain departments in small and medium-sized or large enterprises are unable to adequately support the roadmap. As mentioned above, specialized systems are provided in the form of solutions, so the process of creating a technology roadmap is very flexible depending on the purpose, the industry's characteristics, and the characteristics of the company. It is hard to do. Therefore, it is expected to be useful if the development of a standardized roadmap process is developed, but the specialized software is developed instead of the solution that has the customization function considering the user's needs. To this end, development of algorithms that can standardize and customize the shape of the roadmap must be preceded.

To summarize the problems related to the prior art of the present invention, the research on the road map form and the preparation process is poor, and therefore, there is a limitation in the development of related software systems. The lack of proper level of personalization and standardization presents problems in terms of roadmap creation and utilization efficiency.

An object of the present invention is to devise an algorithm to systematically identify and automate the roadmap creation process, which is designed to solve the above problems, and to provide a system that provides customized functions while suggesting eight standardized roadmap forms. There is.

Another object of the present invention is to propose a form of eight standardized roadmaps by appropriately combining 100% standardized characteristics of existing general-purpose systems and 100% personalized characteristics of existing specialized systems. By proposing an algorithm that creates only some roadmaps, we provide a customized, automated roadmap generation system that can achieve high efficiency with minimal cost and time input.

Another object of the present invention is to simply store the technical information and product information collected in order to create a technical roadmap beyond the technical roadmap to create a technical roadmap, and to manage, search, modify, and share the technical roadmap created in the past. To provide a system.

Another object of the present invention is to provide a road map that provides more useful information by processing collected information, not merely a visual map of technology or a road map that presents a relationship between a market, a product, and a technology. have.

Technical roadmap automatic generation system according to the purpose of the present invention to achieve the above object is a database management module for inputting, modifying, searching for information about technology and products in the enterprise; A roadmap generation module that automatically creates different types of roadmaps according to the purpose of drawing and utilizing existing technologies and product databases; A road map search module for searching and modifying road maps stored in a database; Means for databaseing data generated in association with the database management module, the roadmap generation module, and the roadmap retrieval module; And a user interface unit for interacting with the user.

In the present invention, the database management module comprises: an input engine for inputting required technical information and storing the result in a database; A search engine that searches for and visualizes information desired by a user using a predetermined keyword; And an update engine that calls and visualizes the information from the database, stores the modified information again, and updates the associated roadmap together.

In the present invention, the roadmap generation module includes a customization engine configured to receive a user input of a purpose of creating a technical roadmap, call a corresponding roadmap template from a roadmap template database, and configure a user interface to receive information for creating the roadmap; A data input engine that calls and visualizes a user interface for each purpose of creating a roadmap from a roadmap template database, and receives information necessary for creating a roadmap from a user by calling and visualizing a user interface for each purpose of a roadmap; And a creation engine for calling information entered into the technical database and the product database.

In the present invention, the database means may preferably include a technical database, a product database, a roadmap template database and a roadmap database.

In the present invention, the technical database is preferably established before the roadmap is started.

In the present invention, it is preferable that the technical database can be input and modified by an expert, and only general users can search.

In the present invention, it is preferable that the product database can be modified by an expert and only a general user can search.

Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.

3 is a view for explaining the configuration of a module for creating a technology road map according to the present invention, Figure 4 is a view for explaining a structure diagram of a technology road map preparation system configured to execute the modules of FIG.

In the above embodiment, the automatic roadmap generation system includes a database management module 100, a roadmap generation module 200, and a roadmap retrieval module 300.

According to the purpose of road map creation, it suggests the form of road map suitable for various purposes, provides various information collection templates, and creates and visualizes road map based on the information input from the user. It also allows you to search the collected information and the roadmap you have created. The algorithm of the schematic system is as follows. First, a database 401 for a technology that is closely related to a company's business field is built. A roadmap is created by linking the results retrieved from the technical database 401 with the specific product that the company is planning. In this process, information about product planning is generated and this information is stored in the product database 402. Based on the information stored in the database 400, a specific type of roadmap for a specific product is visualized.

Referring to Figures 3 and 4, there are respective engines for implementing each module, each of which has its own database 400 (technical database 401, product database 402, roadmap database template 403, Road map database 404). In conclusion, the technology roadmap preparation assistance system in the present invention is a web-based software that can be executed on a personal computer, which is composed of three modules, has seven engines internally, and a database 400 related to technology is essential. . In addition, the interaction with the user through the interface 500 is essential in the writing process.

The first module is the database administration module (100). The database management module 100 is a module that stores information for roadmap generation or information generated in a roadmap generation process, and includes a technology database 401 and a product database 402. The technology database 401 includes past trends, current status and future forecasts for key technologies. Descriptive forecasting is based on expert judgment and accesses more and more realistic information over time. The technical database 401 must be established before the roadmap is started, and can be input and modified by experts and searched by general users. On the other hand, since the product database 402 includes information about the products of the enterprise and stores the result of the roadmap creation process, only the modification by the expert and the search by the general user are possible.

The database management module 100 includes an input engine 101, an update engine 102, and a search engine 103.

The input engine 101 is responsible for the input of the technical information, the detailed configuration of which is shown in FIG. When the technical information required according to the input template provided by the input engine 101 is input, the result is stored in the technical database 401.

The update engine 102 is responsible for correcting a change in the technical prediction for a specific technical field, and a detailed configuration thereof is illustrated in FIG. 6. The update engine 102 calls and visualizes the information from the database 400, stores the information modified by the expert, and updates the relevant roadmap together.

The search engine 103 provides information stored in the database 400, and a detailed configuration thereof is illustrated in FIG. 7. The search engine 103 searches and visualizes information desired by a user through a keyword search, a technical field name, a product field name, and the like.

The second module, the roadmap generation module 200 (Roadmap Generation Module), is a core module of the present invention, and assists in creating a roadmap of a suitable type by receiving the purpose of the roadmap creation.

The road map generation module 200 includes a customization engine 201, a data entry engine 202, and a creation engine 203.

The customization engine 201 receives a purpose of creating a technology roadmap from a user, calls a corresponding roadmap template from the roadmap template database 403, and receives a user interface for receiving information for creating the roadmap. The detailed configuration is shown in FIG.

According to the existing research, the technical roadmap is mainly prepared for the purpose of forecasting, R & D planning, product planning, and administration. Thus, the user can choose one of four creation purposes.

As such, in order to assist in the creation of a roadmap customized according to the purpose, the present invention first performed standardization of various types of roadmaps currently used. A total of eight standardized as shown in FIG. 9 by combining three criteria: roadmap target content (technology, product), analysis period of roadmap target content (static, dynamic), and information sources of roadmap target content (internal and external). Roadmaps (family maps, product driver maps, product roadmaps, product evolution roadmaps, technology portfolio maps, technology location maps, technology roadmaps, and technology trends roadmaps) can be constructed.

10 summarizes the information that can be provided by each standardized roadmap. In the present invention, it is desirable to customize the shape of the roadmap in consideration of the characteristics of the purpose of the roadmap creation and the characteristics of the information provided by each roadmap. For example, when a technical roadmap is created for the purpose of technology prediction, a long-term analysis of the technology is required, and thus a roadmap in the form of providing dynamic analysis information in the technical field is required. In addition, product planning requires organizing all the information related to the product and preparing the technical roadmap related to the product line.

Similarly, technology planning needs to organize all the information related to technology, and market-based technology planning requires the preparation of product roadmaps, as well as product release information.

Finally, for management purposes, a roadmap should be created that provides static information about the technology and products at a particular point in time. Customization in the present invention means to assist in creating different types of standardized roadmap combinations according to the purpose of creation, and the customization framework is shown in FIG.

The data-input engine 202 calls and visualizes the user interface 500 for each purpose of roadmap creation from the roadmap template database 403 and receives information necessary for roadmap creation from the user. The configuration is shown in FIG. The combination of standardized roadmaps provided by the system for each purpose is different. Therefore, the information input process and the information input user interface are different for each purpose of writing. The user inputs relevant information and searches the technology database 401 through the input engine 101 to associate the product with the technology, and the generated information is stored in the product database 402.

The creation engine 203 serves to call the information input to the description database 401 and the product database 402, the detailed configuration of which is shown in FIG. After the road map is constructed and visualized based on the called information, when the user confirms and stores the road map, the road map is stored in the road map database 404.

The last module is a roadmap retrieval module 300. The roadmaps generated by the roadmap generation module 200 may be retrieved from the roadmap database 404 through the search engine 301 of FIG. 14. Users can receive the desired type of roadmap information from the system by specifying the product to be searched, the search period, and the roadmap type.

Hereinafter, the operation of the present invention will be described in detail with reference to the accompanying drawings.

15 to 18 are diagrams related to the database management module 100 that manages technical information and product information, which are the basis for roadmap generation and search.

15 illustrates the operation of the input engine 101 in the database management module 100. When the user logs in, a web-based template for inputting technical information is provided through the input engine 101. Technical information refers to historical information, current status, and future forecasts of key technology areas in the enterprise and should be entered based on expert judgment. The input information required by the present invention has a name and a brief description of the technical field and a relative advantage evaluated by the company as shown in FIG. Relative superiority is assessed as leader, middle and inferior. In addition, the technical trend of the corresponding technical field is input in the form of the technical realization point and name. At this time, information about the technology source and the status of the technology development support is input together to support decision-making about technology alternatives in the process of developing a roadmap. Information entered by the user is stored in the technology database 401 when the confirmation button is pressed.

17 is a diagram for explaining the operation process of the update engine 102. First, the engine provides a template for searching for technical information. When a user designates an update target technical information, the engine calls and visualizes corresponding information from the technical database 401. When the user modifies and stores a specific part of the technical information, the update engine 202 changes the technical database 401 and simultaneously retrieves and updates all road maps related to the modified technical field. At this time, if the technology realization time is slower than the product planning time, report the problem to the user and propose to revise the technology planning of the corresponding roadmap. Finally, the technical information correction result is presented to the user.

18 is a diagram illustrating the operation of the search engine 103. Like other search engines, the search engine 103 provides a template for information retrieval, and when a user inputs information to be provided, the search engine 103 retrieves and outputs the corresponding information from the database 400.

19 to 34 are diagrams related to the road map generation module 200 for creating a road map by using the technical information stored in the database management module 100.

The customization engine 201 of FIG. 19 checks whether the user uses the customization function during the roadmap creation process, and receives the purpose of the roadmap creation if the user selects to use the customization function. This is because customization in the present invention means providing different types of roadmaps depending on the purpose of creation. To this end, in the present invention, as shown in Fig. 9, the eight standardizations based on the target content (product, technology), the information source of the target content (internal and external), and the method of analyzing the target content (static analysis, dynamic analysis) Devised a roadmap. 10 lists the characteristics of the information included in each road map. By comparing the characteristics of the information included in the road map and the characteristics of the information required for the purpose of use, the type of road map according to the purpose of the road map can be derived, and the result is shown in FIG. 11. First, technology prediction means trying to grasp the future trend of technology related to a specific product family. Second, product planning intends to plan the characteristics and timing of products to be released in a specific product range. Third, technology planning selects technology alternatives to be applied to products to be released in a specific product category and selects R & D to obtain them. It is what you plan to do. Finally, management means managing information by organizing information about the product portfolio and technology portfolio currently being produced within the enterprise. Therefore, the user can select one of the four objectives of technology prediction, product planning, technology planning, and management, and since the different types of roadmaps are created according to the selected purpose, the configuration of input information required for roadmap creation is also different. The customization engine 201 calls the roadmap template according to the creation purpose selected by the user from the roadmap template database 403 and configures and stores the user interface 500 of the input information.

20 shows the operation of the data entry engine 202 when creating a road map for prediction purposes. When the data input engine 202 calls and presents the user interface 500 for prediction from the roadmap template database 403, the user inputs basic information required. The technical roadmap in the present invention is designed to be drawn up at the product family level. Therefore, the name, brief description, and importance of the product to be created in the basic information input step are entered, and the customer needs and importance related to the names of the main product drivers in the product are inputted, and the technical database 401 is searched for each. Specifies technical areas related to product drivers. Importance is designed to be judged on a 3-point basis.

FIG. 21 shows a system screen for entering basic information about a wireless handset family. The information entered is stored in the product database 402 and utilized to visualize the relevant roadmap.

FIG. 22 illustrates the operation of the data input engine 202 when creating a road map for product planning purposes. The input of basic information is the same as for the purpose of forecasting in FIG. 20, but additionally, the market layer and the product layer are configured by inputting the road map preparation period and detailed information about the market and the product. In the case of the market tier, you enter the target market name, brief description, and target year of the future among the segmented markets related to the target product. In the case of the product layer, information is entered in the form of a name, a brief description, and a target year for a product to be released in the target product range. At this time, the data input engine 202 searches and lists the product names that have been input in the past within the same product family, and if the user selects one of them, the prognostic relationship between the products is established. Of course, if the current product is not an improvement from the past product, it is designed so that it is not necessary to select. Similarly, if a user selects one of the suggested target markets after searching and presenting the target market name previously inputted in the same product line, it is inputted as the target market of the product being created. The input result is stored in the product database 402 and the planning of the products for a specific product line is completed by repeating this process.

FIG. 23 illustrates the operation of the data input engine 202 when creating a road map for the purpose of technical planning. Input of basic information and input of roadmap creation period are the same as the process of creating roadmap for product planning in FIG. 22, but input information about product layer and technology layer, not market layer and product layer in detail information input process. do. In the product layer, information is input in the form of a name, a brief description, and a target year of a product to be released in the target product line, and the previous product may be set as in FIG. 22. In addition, the data input engine 202 retrieves and presents the product drivers inputted in the basic information input step from the product database 402. If the user selects one of them as the target driver, the relevant technical field is searched and the technical information is presented. Of course, the technical field related to the product driver is stored in the product database 402 in the basic information input step, and detailed information on the related technical field is provided by calling from the technical database 401. Therefore, users can easily receive information in the technical field to improve specific product drivers in the product planning process, and based on the information on future trends in the technical field and the relative superiority of the company, the technology source, and the status of technology development. The technical alternative is selected. In the present invention, a number of technical alternatives is designed to be selectable. The input result is stored in the product database 402, and by repeating this process, the technical planning for a specific product group is completed.

24 is a system screen illustrating a process of creating a road map for the purpose of technology planning for the wireless cellular product line from 2002 to 2006. After selecting Battery life as the target driver and pressing the “Select” button, information on the technology trends in the battery, power supply, power amp, radio, and antenna technology fields is displayed on the right screen. If the NIMH-3.6V technology in the battery technology field is selected as an alternative according to various criteria, the product name and technology name are shown on the left screen and the technology layer, and the interrelationships appear. The inputted result is stored in the product database 402 and the technology planning for the specific product line is completed by repeating this process.

25 illustrates the operation of the data entry engine 202 when creating a road map for management purposes. In this case, the operation for inputting the basic information is the same as that for the purpose of prediction in FIG. 20, but repeatedly inputs information on a plurality of product groups instead of one. In addition, instead of creating a roadmap, enter a point in time that requires management. The information entered is stored in the product database 402.

FIG. 26 is a diagram illustrating a process in which information input through the input engine 101 is represented as roadmaps in a form suitable for the purpose through the creation engine 203. The authoring engine 203 calls relevant information from the product database 402 and the technical database 401 to present customized, standardized roadmaps. When the created road map is confirmed, it is stored in the road map database 404.

27 to 35 are screens illustrating the implementation of the authoring engine 203 in the system of the present invention through actual data, and show eight road maps provided by the system.

FIG. 27 is a screen illustrating a product family map, which is a map providing information on all products currently being produced and information on products in the product family. Product family maps allow users to organize their current product portfolio or to infer corporate strategies related to the product.

28 is a screen illustrating a Product Driver Map, which provides information on product drivers related to customer needs. In this map, the relative importance of each product driver is calculated in% based on the input information in the roadmap.

FIG. 29 is a screen showing an example of a product roadmap, which is a typical roadmap created during a product planning process, which includes information on new products to be released over time within a specific product family. Users can use this information to develop marketing plans for specific products or to schedule resources related to future products.

30 is a Product Evolution Roadmap, which provides information on how customer needs change within a particular product family. The target drivers selected for each product in the process of entering the product layer during the roadmap are the function of the product that will be highlighted in particular markets at specific times. Therefore, the evolution of product functions can be inferred through the change of target drivers for each product. Users are expected to be able to use the information provided by the present invention usefully in constructing a new product or a new product.

FIG. 31 is a diagram illustrating a Technology Portfolio Map, which is a map of a portfolio of technologies according to the number and importance of related products. In this map, the Y-axis represents the number of products related to a specific technology field, and the X-axis represents the importance of each technology field calculated as ∑ (relative importance within a company in a specific product group). The technology portfolio map shows technology field names in a two-dimensional plane according to the two values described above, and can be used for the purpose of assisting decision-making related to technology strategy. For example, technical areas in the upper right corner, which have a high number of related products and are important, need to be managed centrally, while those in the lower left corner may be acquired and managed through outsourcing unless they are developed for strategic purposes. It's okay.

32 is a screen illustrating a Technology Position Map, which provides information about strengths and weaknesses of the company's technology related to a specific product line. Similar to the technology portfolio map in FIG. 31, the technology location map derives the importance value of the X-axis through ∑ (relative importance within a company in a specific product group) The relative superiority of the developed technical field is used as the value of the Y axis. The names of each technical field appear in the two-dimensional plane by the two values described above. It is expected that users will be able to support the decision-making that takes place in developing technology strategies by identifying the importance and status of companies in specific technology fields.

FIG. 33 is a technology roadmap, which provides prediction information of a technical field related to a specific product family. The technical fields are sorted by product driver, in order of importance, and the technical trends for each technical field are retrieved from the technical database 401 and displayed on a map. In this case, the font contains information about the status of technical development support, and the font color contains information about the technology source, and since it was developed based on the web, it is designed to receive more detailed information about individual technologies through hyperlinks of technical names. It became.

FIG. 34 is a Technology Trend Roadmap, which provides information on the decline and promising technologies for areas of interest. The basic structure is the same as the technical roadmap in FIG. 33 except that the technical structure is not limited to a specific product family. When a user inputs a specific keyword through the search function, the technical trend of the technical fields related to the keyword is searched from the technical database 401.

35 illustrates a flow of a module for searching for a previously created and stored road map. The search engine 103 suggests a template for searching a roadmap to help a user specify a search target product family, a search period, and a roadmap type. When selecting a roadmap type, the search engine 103 lists only types that have been created in the past, and also lists only roadmaps related to static analysis if the user has designated a search target period as a specific point in time. The user selects a plurality of roadmap types, and when the selection is completed, the search engine 301 calls and visualizes the target roadmap from the roadmap database 404 and provides it. The operation of the search engine 301 is terminated by the user checking or printing the result.

As described above, it has been described with reference to the preferred embodiment of the present invention, but those skilled in the art various modifications and changes of the present invention without departing from the spirit and scope of the present invention described in the claims below I can understand that you can.

As described above, the present invention facilitates the creation, update, and distribution of roadmaps by developing algorithms to automate the technical roadmap creation process and suggesting customized algorithms.

In addition, by establishing a centralized database of technical information and product information, knowledge and strategy can be shared, and roadmaps created by divisions can be integrated to support technology management and product management across the enterprise.

Claims (8)

A database management module for entering, modifying, and searching information about technologies and products in the enterprise; After inputting the purpose of creating the technical roadmap from the user, the user interface is configured to receive the information for creating the roadmap, and the user interface for each roadmap is called to visualize and receive the information necessary for the roadmap creation from the user. A roadmap generation module for calling information entered into a database; A road map search module for searching and modifying road maps stored in a database; And a means for interfacing with the database management module, the roadmap generation module, and the roadmap retrieval module to database the generated data. The system of claim 1, further comprising a user interface unit for interacting with a user. The method of claim 1, wherein the database management module An input engine for inputting required technical information and storing the result in a database; A search engine that searches for and visualizes information desired by a user using a predetermined keyword; And an update engine for visualizing by calling the information from the database, storing the modified information again, and updating the relevant roadmap together. The method of claim 1, wherein the road map generation module A customization engine configured to receive a purpose of creating a technology roadmap from a user, call a corresponding roadmap template from a roadmap template database, and configure a user interface to receive information for creating the roadmap; A data input engine that calls and visualizes a user interface for each purpose of creating a roadmap from a roadmap template database, and receives information necessary for creating a roadmap from a user by calling and visualizing a user interface for each purpose of a roadmap; And a creation engine for calling the information inputted into the technical database and the product database. The method of claim 1, wherein the database means An automatic technology roadmap generation system according to a production purpose, comprising a technology database, a product database, a roadmap template database, and a roadmap database. The system of claim 5, wherein the technology database is established before the roadmap is started. The system of claim 5 or 6, wherein the technical database can be inputted and modified by an expert and only searched by general users. The system of claim 4, wherein the product database is editable by an expert and only searchable by a general user.

Images