The present application relates to software and more specifically to software and accompanying methods and user interfaces for facilitating managing development and implementation of innovations, such as product concepts.
Systems and methods for facilitating managing innovation development, e.g., new product development, are employed in various demanding applications, including enterprise development of advanced products and technologies, such as military aircraft, software, and so on. Such applications often demand informative software that can provide insight for making innovation-related decisions that can ultimately impact enterprise profitability and innovation development feasibility.
Insightful innovation management software and methods are particularly important in enterprise applications, where a given enterprise may be developing several products with varying requirements, costs, risks, and so on. Determining which innovations or products to pursue, which requirements to fulfill, and so on, can represent critical business decisions, which demand particularly insightful tools for managing information needed to make the critical decisions.
Conventionally, enterprises may employ business process management software to facilitate managing a development process pertaining to an innovation. However, such process management software generally lacks features, methods, and interfaces for fully informing enterprise decision makers about important factors involved in developing and managing a particular innovation.
Embodiments described herein provide various features for facilitating management of innovations and accompanying constituent concepts. A given innovation, also called overall concept or product herein, may be characterized by a concept structure, which may include a hierarchy of concepts. For example, a new product innovation, e.g., representing a product, may include several parts, wherein each part may represent a concept. In accordance with certain embodiments discussed herein, each concept or group of concepts of a concept structure may be associated with one or more requirements.
A first example embodiment includes various user interface display screen features for illustrating (e.g., generating analysis) information visualizations pertaining to alternative concept structures in association with one or more metrics, such as supply chain risk, cost, compliance, fulfillment, and/or other product objectives or metrics.
A second example embodiment provides various user interface display screen features for facilitating viewing, tracing, and managing relationships or associations between product requirements, concepts, and concept requirement fulfillment status. Concept requirement fulfillment status (also simply called requirement fulfillment status or just fulfillment status) may represent an indication as to whether a given concept is considered by a user (e.g., an engineer) to fulfill a given requirement that is associated with the concept, e.g., product or product component.
A third example embodiment provides various user interface display screen features for visually depicting (e.g., via an information visualization) and facilitating analysis of the health or strength of relationships or associations between ideas, product features, requirements, concept requirement fulfillment status or projected fulfillment status, concept structures (also called conceptual product structures), alternative concept structures, items, components, and portfolios.
A further understanding of the nature and the advantages of particular embodiments disclosed herein may be realized by reference of the remaining portions of the specification and the attached drawings.
Embodiments can provide new innovation management capabilities that enable detailed tracking and analysis of concepts and sub-concepts included in a concept structure characterizing an overall concept, called an innovation herein. Certain capabilities of embodiments discussed herein further enable creation of associations between concepts and concept requirements; determination of and association of metrics, such as cost, weight, status, and other scores, ratings, or values with concept and/or product requirements; graphical illustration of health and/or strength of an association (also called a relationship herein), and so on.
In general, certain embodiments discussed herein may be implemented via Graphical User Interface (GUI) software in communication with a database for storing information about innovations, such as descriptions of sub-concepts, risks associated with sub-concepts, and other related metrics or information, as discussed more fully below. The GUI software and database may be implemented on a single computer or may be distributed among different computers, e.g., on a client device and/or a server device in communication via a network, such as the internet.
For clarity, certain well-known components, such as hard drives, processors, operating systems, power supplies, the Internet, other networks, and so on, have been omitted from the figures. However, those skilled in the art with access to the present teachings will know which components to implement and how to implement them to meet the needs of a given application.
For the purposes of the present discussion, a user interface display screen may be any software-generated depiction presented on a display, such as the touch display 22. Examples of depictions include windows, dialog boxes, displayed tables, and any other graphical user interface features, such as user interface controls, presented to a user via software, such as a browser. User interface display screens may include various graphical depictions, including visualizations, such as graphs, charts, diagrams, tables, and so on.
An innovation may refer to an overall concept, e.g., pertaining to a product, that may include several components. Hence, an innovation may itself represent a concept, and the constituent concepts of an innovation may represent sub-concepts of the innovation. For example, if an innovation pertains to a flying bicycle, the flying bicycle may have sub-components, such as pedals, chain, spokes, lights, handle bars, and so on, each of which may represent sub-concepts or sub-designs of the overall flying bicycle concept or design, which is called an innovation.
The overall concept and constituent sub-components may be associated with certain requirements. For example, the flying bicycle lights may require a certain brightness, a certain color, and so on. Such requirements may be established, for example, by selecting a concept or sub-concept from the concept structure panel 14 and then selecting a requirements user interface control at the bottom of the details panel 16. User selection of the requirements user interface control may trigger display of an additional field or dialog box wherein a user may specify details of a particular requirement or metric to be associated with a sub-concept.
For the purposes of the present discussion, a user interface control may be any displayed element or component of a user interface display screen, which is adapted to enable a user to provide input, view data, and/or otherwise interact with a user interface. Additional examples of user interface controls include buttons, drop down menus, menu items, tap-and-hold functionality, and so on. Similarly, a user interface control signal may be any signal that is provided as input for software, wherein the input affects a user interface display screen and/or accompanying software application associated with the software.
Components of an innovation or overall concept may fit within a hierarchical structure illustrated in the concept structure panel 14. The highest level concept of the concept structure panel 14 corresponds to the innovation. A given innovation may have sub-components called direct child components, which may themselves have sub-components, i.e., direct child components.
The user interface display screen 10 is adapted to facilitate innovation management for an innovation that may incorporate several concepts and that may be characterized by several requirements. Different concepts may be associated with different requirements, as indicated in the requirements panel 12.
For example, the flying bicycle innovation may have a mechanical interface requirement, an electrical interface requirement, a software characteristics requirement, and so on. Furthermore, each requirement may have sub-requirements. For example, the software characteristics requirement may have a sensor software requirement, an operating system requirement, and so on, as indicated in the requirements panel 12.
The details panel section 16 includes various sub-sections, e.g., as indicated by a Cost header, a Physical Attributes header, a Supply risk header, and so on. Such details-subsections provide various user options, e.g., user interface controls for defining, specifying, or modifying metrics and associated parameters. Note that in certain embodiments, user options for removing metrics from the details section 16 for a particular selected concept, sub-concept, or alternate solution category may be provided in corresponding sections of the details section 16. For example, a remove button and an add button for enabling such modifications may appear in each sub-section of the details panel section 16.
Facilitating Analyzing and Juxtaposing Alternate Solution Category Structures with Reference to Concept Metrics, Such as Supply Chain Risk, Cost, and so on
Different alternative concept categories and alternative concept structures associated therewith, can be compared and evaluated relative to each other to facilitate design improvement, as discussed more fully below.
For a given concept structure, different alternative concept categories are user definable. The second example user interface display screen 20 includes a description column 24, which provides fields for enabling a user to enter and/or change or delete a description for a predetermined alternative concept category listed in a name column 26.
The second example user interface display screen 20, also called a Manage Solution Alternative screen, is adapted to enable activation and deactivation of a listed alternative concept category. In particular, a show column 28 provides check boxes for enabling a user to activate or deactivate an alternative concept category by selecting or deselecting, respectively, a corresponding check box adjacent to a named alternative concept category, e.g., as listed in the name column 26.
To change a name of an alternative concept category, a user may select and edit one of the fields of the name column 26. To alter a description of a named alternative concept category, a user may select and edit a description field (of the description column 24) adjacent to the named alternative concept category.
Changes, such as changes to a name, description, and/or activation status, of an alternative concept category may be reflected in a primary attribute group view of an associated concept structure, which may be accessible via a header bar (e.g., via a view menu thereof) of the concept structure panel 14 and which may be displayed in the concept structure panel 14 of
When a user marks a concept as an alternate, additional check boxes 38 appear in the user interface display screen 30 for the concepts corresponding to the checked boxes 38. The additional check boxes 38 represent user options for assigning, i.e., associating concepts 32 with one or more alternate solution categories 34, thereby creating one or more relationships or associations between one or more concepts and one or more alternate solution categories.
The concepts 32 displayed in the user interface display screen 30 may be filtered via a drop down menu 40 to indicate or show only concepts and related information that are part of an alternate solution category selected from the drop down menu 40. Note that the drop-down menu 40 may be accessible via the concept structure panel 14 of
Display of different metrics for different concept solution categories may be via user selection of a filtering user interface control 56. Note that the user interface display screen 50 may include additional functionality and mechanisms for adjusting displayed metrics. For example, a right-click drop-down menu may appear in response to user right-clicking a header (e.g., Score, Cost, etc.). The menu may include additional user options for defining metrics, editing metrics, removing one or more columns pertaining to one or more of the metrics 52, e.g., a score metric, cost metric, and so on. The additional user options may further include a user option for adjusting how a metric, such as a score, is calculated; for filtering displayed metrics based on a user specified or predetermined criterion or criteria, and so on.
For the purposes of the present discussion, a visualization may be any graphical depiction of data.
A comparison may be any juxtaposition of data to be compared. A comparison operation may be any operation or function that acts to juxtapose data to be compared. A juxtaposition may include any simultaneous presentation of or illustration of data to be compared. A juxtaposition may also include a combination of data to be displayed, where the combination shows or illustrates a difference or contrast between the data to be compared. A comparison view may be any user interface display screen that illustrates data for multiple resources to facilitate juxtaposition or comparison of the data.
Examples of metrics illustrated in
Hence, the embodiments of
Note that various additional user interface display screens and accompanying underlying software routines may provide functionality for creating or defining concept metrics; for associating or computing concept metrics with one or more concepts; for aggregating concept metrics for different branches of a concept structure; for rolling up and facilitating juxtaposing aggregated concept metrics, and so on.
An example method that may be implemented via the user interface display screens and underlying software of
Hence, concept components, i.e., sub-concepts, can be assigned to requirements to facilitate determining which requirements should/could be fulfilled by which concept components. Once the definition and/or design of the concept component is mature enough to readily fulfill the requirement, a user can check the fulfilled flag 82 in the requirements table 80 of the concept component details panel (e.g., the details panel 16 of
Subsequently, analysis can readily be performed across the whole concept and accompanying structure or sub-structure to find out how many of the assigned requirements have already been fulfilled by the current product concept or how much more concept design remains to be done.
Hence, the user interface display screens
An example method that may be implemented via the embodiments of
Facilitating Visually Depicting and Analyzing Health and/or Strength (or other Attributes or Characteristics) of Relationships Between Objects Related to an Innovation, Such as Concepts, Alternate Concepts and Associated Structures, Concept Requirements, Ideas, Features, and Portfolios
The example visualization 92 may include any number of nodes corresponding to objects or categories, which each may include various other nodes or categories. For example, the “Fulfilled Requirements” node includes an indicator showing that nine sub-nodes are included within the “Fulfilled Requirements” category.
Selection of the “Fulfilled Requirements” node may trigger display of nine different nodes extending from the “Fulfilled Requirements” node. Each of the resulting newly displayed nodes may be connected to the parent “Fulfilled Requirements” node via a color coded (or otherwise visually coded or made visually distinguishable) link indicating a status or strength/health measurement associated with the relationship, i.e., association between each child node and a parent node. Alternatively, or in addition, different displayed features of a node, such as node outline, node background, node shape, node size, nodes spacing relative to other nodes, and so on, may be adjusted to indicate different information or scores characterizing relationships between the different nodes of the visualization 92.
Furthermore, note that the various nodes 96 are merely illustrative. In certain embodiments, each of the nodes 96 may represent a sub-concept of a concept represented by a parent node, e.g., the “Wheel Flasher” node. In the present example embodiment, the “Wheel Flasher” node may represent an overall concept, i.e., innovation, with various subcategories; may represent a subcomponent or sub-concept of another concept (not shown); and so on.
Hence, the visualization 92 may represent a graphical representation of a method for visually depicting and analyzing the health/strength of one or more relationships between objects, such as between objects representing an idea, feature, requirements, requirement fulfillment (design, test) conceptual product structures (also simply called concept structures), alternative conceptual product structures, items, components, portfolios, and so on.
An example method that may be adapted for use with the embodiment of
Information in the database is user accessible and manipulatable via graphical user interface software 126, which interfaces the display 122 with the database 128 and includes computer code for facilitating rendering user interface display screens 124, accompanying user interface controls, visualizations, and so on.
Although the description has been described with respect to particular embodiments thereof, these particular embodiments are merely illustrative, and not restrictive. For example, while various example user interface display screens illustrate example concepts as physical devices, such concepts may include software or other non-physical products, services, or category of innovation.
Any suitable programming language can be used to implement the routines of particular embodiments including C, C++, Java, assembly language, etc. Different programming techniques can be employed such as procedural or object oriented. The routines can execute on a single processing device or multiple processors. Although the steps, operations, or computations may be presented in a specific order, this order may be changed in different particular embodiments. In some particular embodiments, multiple steps shown as sequential in this specification can be performed at the same time.
Particular embodiments may be implemented in a computer-readable storage medium for use by or in connection with the instruction execution system, apparatus, system, or device. Particular embodiments can be implemented in the form of control logic in software or hardware or a combination of both. The control logic, when executed by one or more processors, may be operable to perform that which is described in particular embodiments.
Particular embodiments may be implemented by using a programmed general purpose digital computer, by using application specific integrated circuits, programmable logic devices, field programmable gate arrays, optical, chemical, biological, quantum or nanoengineered systems, components and mechanisms may be used. In general, the functions of particular embodiments can be achieved by any means as is known in the art. Distributed, networked systems, components, and/or circuits can be used. Communication, or transfer, of data may be wired, wireless, or by any other means.
It will also be appreciated that one or more of the elements depicted in the drawings/figures can also be implemented in a more separated or integrated manner, or even removed or rendered as inoperable in certain cases, as is useful in accordance with a particular application. It is also within the spirit and scope to implement a program or code that can be stored in a machine-readable medium to permit a computer to perform any of the methods described above.
As used in the description herein and throughout the claims that follow, “a”, “an”, and “the” includes plural references unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
Thus, while particular embodiments have been described herein, latitudes of modification, various changes, and substitutions are intended in the foregoing disclosures, and it will be appreciated that in some instances some features of particular embodiments will be employed without a corresponding use of other features without departing from the scope and spirit as set forth. Therefore, many modifications may be made to adapt a particular situation or material to the essential scope and spirit.
This application claims priority from U.S. Provisional Patent Application Ser. No. 61/707,935, entitled INNOVATION MANAGEMENT, filed on Sep. 29, 2012, which is hereby incorporated by reference as if set forth in full in this application for all purposes.
Number | Date | Country | |
---|---|---|---|
61707935 | Sep 2012 | US |