The present disclosure relates generally to integrated product development management and, in particular, to methods, systems, and computer program products for implementing an end-to-end integrated product development management system.
With an overriding goal of improving quality and being more proactive in product designs, businesses are relying upon various measurement-based strategies that focus on process improvement and variation reduction, e.g., Six Sigma, Design for Six Sigma, Lean Sigma, as well as company-branded methodologies. Some practices are directed to providing incremental improvements in a process or product, whereas others focus on new product/design development. As these individual practices or methodologies are not easily or readily congregated, businesses have not been able to reap the full extent of the benefits associated with each methodology. For example, some companies have demonstrated how to select and when to use the various methodologies for individual company application, yet this practice is not repeatable for other companies. Other companies are using only one approach with questions on how to leverage the other approaches.
Furthermore, when seeking an end-to-end solution, current practices exclude natural extensions of the entire value chain (e.g., tools, suppliers, industry partners, etc.). When considering a business' integrated product development process, e.g., there is a partial exclusion of design for quality analytical techniques and tools. Although some techniques and tools exist in today's environment, there is still a need to bring these tools together in a fashion that supports the entire product/process from concept selection through life-cycle management.
What is needed, therefore, is a unified methodology that integrates various measurement-based strategies with related analytical tools and data sources for facilitating new product development, as well as process improvement and variation reduction, from product conception through lifecycle management.
Exemplary embodiments of the invention include methods for implementing an end-to-end integrated product development management system. A method includes providing a user system with a link to a data source and an analysis tool via a user interface in response to a project opportunity selection for a proposed product. The method also includes receiving results of an analysis performed by the user system in response to implementing the analysis tool, and creating a project record for the project opportunity selection in response to determining an approval of the project opportunity selection. The method further includes creating a project plan by mapping data fields in the project record to corresponding data entries relating to a project phase, project task, project task tool, project task timetable, project task measurement, data source, and project team selected by the user system via the user interface.
Additional embodiments include systems for implementing an end-to-end integrated product development management system. A system includes a host system executing an integrated product development management application. The integrated product development management application implements a method. The method includes providing a user system with a link to a data source and an analysis tool via a user interface of the integrated product development management application in response to a project opportunity selection for a proposed product. The method also includes receiving results of an analysis performed by the user system in response to implementing the analysis tool, and creating a project record for the project opportunity selection in response to determining an approval of the project opportunity selection. The method further includes creating a project plan by mapping data fields in the project record to corresponding data entries relating to a project phase, project task, project task tool, project task timetable, project task measurement, data source, and project team selected by the user system via the user interface.
Further embodiments include computer program products for implementing an end-to-end integrated product development management system. A computer program product includes instructions for causing a computer to implement a method. The method includes providing a user system with a link to a data source and an analysis tool via a user interface in response to a project opportunity selection for a proposed product. The method also includes receiving results of an analysis performed by the user system in response to implementing the analysis tool, and creating a project record for the project opportunity selection in response to determining an approval of the project opportunity selection. The method further includes creating a project plan by mapping data fields in the project record to corresponding data entries relating to a project phase, project task, project task tool, project task timetable, project task measurement, data source, and project team selected by the user system via the user interface.
Other systems, methods, and/or computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, and/or computer program products be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
The detailed description explains the exemplary embodiments of the invention, together with advantages and features, by way of example with reference to the drawings.
In accordance with exemplary embodiments, an end-to-end integrated product development management system and method are provided. The integrated product development management system includes a development methodology that uses proactive and predictive analytical techniques to improve the robustness of product performance to ensure that the end-to-end design to launch activities produce products that lead to the success of a company. In addition, the integrated product development management functions incorporate the use of analytical techniques and statistical tools to solve production related problems and drive continuous product and process improvements.
The exemplary integrated product development management processes manage the business rules and include a web application providing a system-generated methodology for facilitating project planning from conception through end of life. Additionally, the integrated product development management application 100 integrates a variety of tools and data sources with selected business rules for providing integrated product development management functions. The project plans are generated from execution of the business process and the project plans are stored and updated in a tracking database which may be used as a search and reference tool for future project planning activities.
The processes described in
Referring now to
In an exemplary embodiment, the system of
The network 106 may be any type of known network including, but not limited to, a wide area network (WAN), a local area network (LAN), a global network (e.g. Internet), a virtual private network (VPN), and an intranet. The network 106 may be implemented using a wireless network or any kind of physical network implementation known in the art. A user system 102 may be coupled to the host system through multiple networks (e.g., intranet and Internet) so that not all user systems 102 are coupled to the host system 104 through the same network. One or more of the user systems 102 and the host system 104 may be connected to the network 106 in a wireless fashion. In one embodiment, the network is an intranet and one or more user systems 102 execute a web browser to contact the host system 104 through the network 106. In another exemplary embodiment, the user system 102 is connected directly (i.e., not through the network 106) to the host system 104.
The host system 104 may be directly connected to, contain, or otherwise engage in communications with one or more storage devices. As shown in
The host system 104 depicted in
The host system 104 may also operate as an application server. The host system 104 executes one or more computer programs to provide integrated product development management functions (e.g., the integrated product development management application 110). In addition, the host system 104 executes a variety of business and analytical tools, as well as related methodologies in support of the integrated product development management functions, such as, e.g., quality function deployment (QFD), Kano analysis, Triptych®, Affinity® project development, Ishikawa diagrams, Theory of Inventive Problem Solving (TRIZ), Design modeling, Design of Experiments (DOEs), Pugh method, Topsis, Supplier selection, failure mode and effect analyses (FMEAs), statistical software such as Minitab® Statistical Software, Analysis of Variance (ANOVA), Regression analyses, Gauge Repeatability and Reproducibility (Gage R&R), design test and validation, and other similar types of tools. These tools and methodologies are collected referred to herein as project/analysis tools 108. The integrated product development management application 110 and user interface enable customized integration of the project/analysis tools 108, as well as seamless integration of various data repositories (e.g., storage devices 112 and 114). Processing of the integrated product development management application 110 may be shared by the user system 102 and the host system 104 by providing an application (e.g., java applet) to the user system 102. Alternatively, the user system 102 can include a stand-alone software application for performing a portion or all of the processing described herein. As previously described, it is understood that separate servers may be utilized to implement the network server functions and the application server functions. Alternatively, the network server, the firewall, and the application server may be implemented by a single server executing computer programs to perform the requisite functions.
As described above, the integrated product development management application 110 includes a user interface for enabling end users of user systems 102 (e.g., core project team members) to enter data that is processed by the application 110. The user interface includes various screens relating to project opportunity requests and project plans as described further herein.
Turning now to
At the initial concept phase, one or more core team members access the user interface screen 300 shown in
Each core team member may access one of corresponding options 304-314 for analysis and review at step 206. Each of the analyses is implemented by selecting one or more data sources (e.g., 112) and/or tools (e.g., 108) which are mapped to corresponding analysis types at step 204. Results of the analyses performed in step 206 are reviewed by specified core team members at step 208. The results of the analyses are submitted for approval at step 210. Each of the individual analyses will now be described. Each core team member may select one or more options via the user interface screen 300 to initiate an analysis in response to the request for project opportunity. As shown in
In addition, once each of the individual analyses is performed, a collective core project team may analyze/review all of the results of the aforementioned analyses via option 310. The core project team members may determine whether to submit the project opportunity for further review if the results of the analyses are positive (e.g., support the development of a new/improved product). Additional core team members from other departments of the enterprise, e.g., finance specialist, may perform value analysis, such as an economic value added (EVA) analysis by selecting option 312. An EVA analysis results in a financial performance measure of the project opportunity. Again, selecting this option 312 may redirect the finance member to corresponding data/tools that are mapped to this option via the integrated product development management application 110. In addition, there may be several project opportunities that are submitted for review by the finance core team member. If the financial assessment yields positive results, the project opportunity may then be reviewed at the executive level of the enterprise (e.g., an executive-level individual) via option 314. If the project opportunity is not approved at step 212, the results of the analyses performed in steps 202-210 may be stored in a project record in storage device 114 for possible future consideration or review at step 214. For example, results of the QRAS analysis may be stored in QRAS_SCORECARD field 508. Results of the EVA analysis may be stored in EVA field 516.
Otherwise, if the project opportunity is approved at step 212, the executive team member submits the project opportunity by selecting the APPROVE option 316 in
A project plan is created using the project record 500 and user interface screen 400 entries provided by respective core team members at step 218. The approved project opportunity and corresponding project plan may be linked via the project opportunity name/descriptor entered in option 302 and the project option 402, both of which correspond to a PROJECT_ID field 502 and/or PROJECT_DESCRIPTION field 504 in project record 500. For each phase, the integrated product development management application 110 provides a link to project tasks, tools, and data sources via the business rules implemented by the application 110 at step 220. In the initial concept phase, a core team member may select PROJECT CHARTER 404 to enter general data relating to the project definition, stakeholders, etc. A project charter template 600 is shown in
In addition, the concept phase may include business processes for design innovation. Tools selectable for these processes may include Affinity®, Ishikawa, TRIZ, etc. These tools enable the user to identify desirable factors for a product design and for brainstorming ideas. For each task and/or phase selected, a user may select a timetable for implementing the task via option 414 and a measurement tool via option 416 in window 412.
Once completed, the user may go on to select the next phase (e.g., plan) via option 408. Again, various tools, data sources, timetables, measurements, etc., may be selected for a given task. In the plan phase, e.g., a user may select a fault tree analysis (FTA) tool, DOE, Pugh method, Topsis, Supplier selection, measurement analysis (e.g., Gage R&R), as well as templates for providing failure mode effect and analysis data. Exemplary FMEA templates are shown in
By selecting the develop phase via option 408, the user may selects tools, such as FMEA, Minitab® Statistical software, ANOVA, regression analysis, as well as Design tolerance, optimization, Error proofing, capability analysis, reliability analysis, and sensitivity analysis tools and methods. The development phase provides design optimization through statistical data analysis and/or the generation of mathematical models to demonstrate design workability. Timetables and measurement criteria may be selected via window 412 as described above.
By selecting the qualification phase via option 408, the user conducts design validation by selecting one or more of Minitab® statistical software, reliability, sensitivity, an tolerance analysis, error proofing, control plan, and confirmatory testing. The data resulting from this and other phases may be stored in the project record at corresponding data fields for use in researching issues and resolutions from historical project plans. In addition, the data resulting from these phases may be used to identify ongoing issues in the project concept, plan, or development phases that may be adjusted for a current project plan.
By selecting the launch/lifecycle phase via option 408, the user may be prompted to select from one or more Minitab® Statistical Process software, scorecards, control plans, etc. for implementing the project plan and continued monitoring of performance issues relating to the underlying product. This information may be stored in the project record 500 for future research relating to similar projects and/or improvements at step 222.
The data entered for each of the aforementioned phases may be stored in corresponding data fields 510-514 and 518-536 as shown in project record 500 of
As described above, embodiments can be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. In exemplary embodiments, the invention is embodied in computer program code executed by one or more network elements. Embodiments include computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. Embodiments include computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.