FIELD OF INVENTION 0001 The present invention relates to an integrated enterprise and product design and transformation system. 0002 More particularly, the present invention relates to an integrated system for designing, developing and guiding an enterprise and its products through various phases from inception to discontinuation of use.

BACKGROUND TO INVENTION 0003 U.S. Pat. No. 5,745,895 (Bingham et al) discloses a coherent method for the creating, capturing, and retrieving of ideas, concepts, data, and/or multimedia information. The system establishes a framework in which knowledge can be represented. The system is a computer-based system which utilizes multimedia, databases, and mass storage to implement this framework. It has an architecture and an open-ended-set of functional elements that combine to support knowledge processing. Knowledge is created by uniquely identifying and interrelating heterogeneous datasets located locally on a user's workstation or dispersed across computer networks. 0004 In U.S. Pat. No. 5,418,943 (Borgida et al) there is disclosed an apparatus and a method for integrating a knowledge base management system with a data base system. The knowledge base management system employs compositional descriptions which describe information in terms of concepts. A translation component of the apparatus translates compositional descriptions into data base queries, so that information matching a compositional description may be retrieved from the data base. 0005 U.S. Pat. No. 5,644,686 (Hekmatpour) describes an expert system and processing method employing a three level hierarchical knowledge base that has a plurality of nodes coupled together. 0006 In U.S. Pat. No. 6,236,994 B1 (Swartz et al) there is disclosed a method and apparatus for first integrating the operation of various independent software applications directed to the management of information within an enterprise. The system architecture is, however, an expandable architecture, with built-in knowledge integration features that facilitate the monitoring of information flow into, out of, and between the integrated information management applications so as to assimilate knowledge information and facilitate the control of such information. 0007 It is therefore clear, in particular from the patent specifications referred to above, that various methods and systems have been suggested to manage knowledge and information. However, no disclosure has been made regarding an integrated enterprise and product design and transformation system. 0008 The life cycle of any enterprise or product can be divided into three phases, namely a design phase, a maturity phase and a disposal phase. Most changes are made to the product during the design phase. Relatively few changes to meet the industry's or customers' changing requirements are made during the maturity phase. 0009 The cost of changing the design at any stage in the life cycle of a product increases exponentially with time. In order to keep costs down, all changes must be made as early in the life cycle as possible, i.e. during the design phase. 0010 The expression product as henceforth used in this specification refers to an article, a method or an enterprise. 0011 It is an object of the invention to suggest an integrated enterprise and product design and transformation system to anticipate and effect changes as early as possible. This facilitates the design process and provides a competitive edge as well as related financial advantage.

SUMMARY OF INVENTION 0012 An integrated enterprise and product design and transformation system, includes: 0013 (a) an implementation procedure reference framework for structuring a product development during its design phase, its maturity phase and its disposal phase; 0014 (b) a product information means for supplying and comparing details of a product at any time during all its phases with the implementation procedure reference framework; and 0015 (c) a change effecting means adapted to effect changes to a product as required after comparison with the implementation reference framework. 0016 Also according to the invention, a method of designing and transforming a product through various stages, includes the steps of 0017 (a) setting up an implementation procedure reference frame work for structuring a product development during its design phase, its maturity phase and its disposal phase; 0018 (b) supplying and comparing details of a product at any time during all its phases with the implementation procedure reference framework; and 0019 (c) effecting changes to a product as required after comparison with the implementation reference framework. 0020 The system may be adapted to create a product life cycle and/or an enterprise life cycle. 0021 The product life cycle and the enterprise life cycle may form a framework for capturing information to provide an integrated design frame work about a product design, an enterprise design and interaction between the product design and the enterprise design. 0022 The product life cycle and the enterprise life cycle may be considered in parallel when implementing changes. 0023 The implementation procedure framework may also serve as a re-implementation procedure framework. 0024 The integrated design frame work may include knowledge object examples, design examples and document templates. 0025 The system may be adapted to prompt a user with applicable design objectives and/or performance measures. 0026 The system may include checklists to ensure that all tasks required are completed. 0027 The system may include a data management system for design documentation to facilitate audit trails and re-usability of design related processes. 0028 The system may include web centric and/or intranet facilitated custom design of business processes, products and enterprises. 0029 The system may be adapted to provide system supports, which include: 0030 an implementation support; 0031 training and personnel development support; 0032 cyber database support enterprise design knowledge management; 0033 user group exchange support services. 0034 The cyber database support may include an advanced data administration management system which utilizes publications of technology developments. 0035 The system in accordance with the invention provides a design framework environment, which supports the virtual life cycles of enterprise design and product design concurrently. It further facilitates related life cycles such as process and technology management life cycles and provides a suitable configuration management environment for programmes, such as ISO 9000 implementation. 0036 The design process of a product or an enterprise is normally performed by a design team. This team creates a range of design documentation which documentation is captured in a data management system to facilitate audit trails and re-usability of all design related processes. All information generated during an enterprise design implementation is stored in an enterprise design data management system. 0037 The integrated enterprise and product design and transformation system in accordance with the invention makes use of design objectives, which tell the user towards what goal he is working. Knowledge objects are also incorporated to give examples of what other enterprises have done in that specific field. Every enterprise has a specific structure, the integrated enterprise and product design and transformation system provides for an enterprise design and transformation structure that is based on PERA (Purdue Enterprise Reference Architecture). The current enterprise parameters can then be entered into the design structure. 0038 The integrated enterprise and product design and transformation system implementation procedure framework includes steps to be followed and which are divided into two groups: namely a master plan and a reference framework (also referred to as architecture). 0039 The master planning process, based on a particular reference architecture, provides the user with a methodology for the preliminary investigation, feasibility study and initiation of an enterprise engineering project. Each step in the master plan and reference architecture is defined and described. The information and resources needed to carry out the desired tasks, are listed and the expected outcomes are described. This master planning and reference architecture focuses on re-design, from an as-is to a to-be state.

BRIEF DESCRIPTION OF DRAWINGS 0040 The invention will now be described by way of example with reference to the accompanying schematic drawings. 0041 In the drawings there is shown in: 0042 FIG. 1 a master plan of the integrated enterprise and product design and transformation system in accordance with the invention; 0043 FIG. 2 a reference framework or architecture of the integrated enterprise and product design and transformation system in accordance with the invention; 0044 FIG. 3 a product life cycle and an enterprise life cycle of a manufactured product or service in accordance with the invention; 0045 FIG. 4 design objectives and resolution perspectives in accordance with the invention; 0046 FIG. 5 a diagnostic spider web outlining functionalities in accordance with the invention; 0047 FIG. 6 integration of the enterprise life cycle and the product life cycle in accordance with the invention; and 0048 FIG. 7 integration of software environment, technology awareness dome and consultation, with existing enterprise systems in accordance with the invention.

DETAILED DESCRIPTION OF DRAWINGS

FIGURE 1 0049 Master Plan 0050 In FIG. 1 is shown a master plan which forms an important component of the PERA (Purdue Enterprise Reference Architecture). It provides the user with the necessary preliminary planning and operational guidance to be able to take full advantage of the technologies available. In the design phase the user can go through the steps of the master plan first. The feasibility of the project will then be determined. If it is feasible to continue, the user can follow the steps in the reference architecture (FIG. 2). Note: The acronym EBE stands for Enterprise Business Entity). 0051 Navigator Window (not shown) 0052 The navigator window indicates the position of the user within the integrated enterprise and product design and transformation system with respect to the enterprise life cycle or the product life cycle. It will assist the user to navigate through the entire design process, using both the master plan and reference architecture. It provides a visual guide to the different life cycles and methodologies. It will prompt the user to make certain decisions and will capture these decisions. The ability to capture information relative to a step or region within the navigator aids the enterprise design and transformation process by providing ease of access to the information and by capturing the context within which decisions are made. 0053 Inputs 0054 The generic input information lists what is needed in order to carry out the desired tasks in that phase/step of the master plan. It states the prerequisites to complete the step in the life cycle, for example what documents have to be completed at this stage, what information has to be available, etc. 0055 Output 0056 The generic output information lists what the expected outcomes would be on successful completion of the transformation desired in that phase/step of the master plan. Typical outputs will be documentation, policies and definitions. 0057 Resources 0058 The generic resource information lists which resources have to be committed in order to successfully complete the transformation process to take place in that step of the master plan. Resources are typically the people involved, computer programs or equipment. 0059 Controls 0060 The generic control information lists any information necessary in order to control how the information in that step of the master plan is being put to use. Controls refer to the constraints and feedback parameters within a step. Typical controls include the environment, safety and production requirements.

FIGURE 2 0061 Reference Architecture 0062 A reference architecture for a given domain is shown in FIG. 2, which is a generic architecture from which others can be compared or derived. It is a framework on which enterprise design can be based. It consists of a methodology and a model that focuses on a re-design, from an as-is to a to-be state. An adapted version of the Purdue Enterprise Reference Architecture is implemented in the design method and system. 0063 Each step in the reference architecture is defined and described in an additional information window. The tools, techniques and resources needed to carry out the desired tasks and the expected outcomes are listed. 0064 Resources 0065 The generic resource information describes which resources have to be committed in order to successfully complete the transformation process to take place in each of the reference architecture. 0066 Hereafter various concepts used by the product control system are further explained.

FIGURE 3 0067 Life Cycle 0068 FIG. 3 describes the life cycle concept highlights the repetitive and reiterative nature of the enterprise or product and their design. It is important to realise that the life cycle does not denote a once off exercise, but rather a framework within which the design and re-design can take place. Such design and re-design is achieved by way of R & D (Research and Development) and Innovation. With the system the user follows the virtual life cycle, addressing each phase as required. 0069 Enterprise Life Cycle 0070 The enterprise life cycle represents the sequence of phases characterising the entire existence of an enterprise. These phases include enterprise inception, definition phase, requirements definition, system design and specification, system implementation and it covers all phases through to the disposal phase. 0071 The life cycle has a time-related component as well as a view-related component. This creates a framework within which the user can view specified information. 0072 Product Life Cycle 0073 The product life cycle refers to all the stages that a product undergoesfrom the concept phase to the disposal thereof.

FIGURE 4 0074 Design Objectives 0075 Design objectives are objectives to measure the performance of various product and enterprise entities. This is used to align the design processes and to prompt the design team to keep certain design criteria in mind when doing an enterprise engineering exercise. 0076 FIG. 4 illustrates design objectives views and resolution perspectives. The pyramid indicates the resolution and performance views of the design objectives and knowledge management system. 0077 Category 0078 Category describes the functional area within a company where the design objectives will be applicable. 0079 Resolution 0080 This field tells the user in what resolution the design objectives have an impact. It positions the design objective in the relevant resolution ranging from global to a single process or activity. 0081 Performance Impact 0082 This field tells the user on what area the design objective focuses. It identifies the basic performance parameters influenced by a specific design objective. The four areas where a measurement can have an impact on a company are: cost, quality, assets and time. 0083 Indicator 0084 The indicator contains detail information concerning the design objective. This may include formulas and descriptions. It indicates how to achieve the design objective and is the indicator of performance in a specific step of the design. The design can be evaluated according to these indicators.

FIGURE 5 0085 Functionality Web 0086 In FIG. 5 a functionality web is shown indicating various functions and relevant ratings. 0087 Numbers 1 to 4 in FIG. 5 are applied when implementing the system in an enterprise. They are: 0088 1 Clear design objectives, purpose and goals 0089 2 Roadmaps for each improvement project 0090 3 Best Practice starting points and benchmarking 0091 4 The disciplined use of the integrated document management system. 0092 Numbers 5 to 8 in FIG. 5 are improvements obtained by the system's integration of different systems within the client company. They are: 0093 5 Knowledge Management 0094 6 Business Intelligence 0095 7 Continuous Improvement 0096 8 Decision support.

FIGURE 6 0097 Enterprise/Product Integration 0098 FIG. 6 shows a diagram depicting a product life cycle from concept phase to disposal phase. 0099 As continuous changes in the enterprise life cycle are being made (for example a change of specifications for a product), they are directly linked to the design review stage of the product life cycle roadmap in the system according to the invention. 0100 This ensures alignment of product and enterprise improvement. A design review immediately takes any changes in the enterprise design into account.

FIGURE 7 0101 An integration structure is illustrated in FIG. 7.

EXAMPLES 0102 Each of the steps in the master plan in the reference architecture for the enterprise and that of the product life cycle provides illustrative examples. These are like pigeon holes and expand on the functions to be performed in each step. 0103 The examples give an indication of how the navigator can be applied or implemented in practice. It can either be templates of required documentation, examples of completed templates or other additional information. To retrieve a document the user must double click on the file name. These examples can be dragged to the scratch pad. 0104 Examples are linked to the master plan steps, the product life cycle steps and to products and outputs, method and systems and techniques or resources in the enterprise life cycle reference architecture functions.

Enterprise Design Data Management System (EDDM) 0105 All the data relevant to the specific step in the master plan or reference architecture must be added to the enterprise design data management system. This data is company specific, where the data in the scratch pad can be any data that is collected during the design process. 0106 These files can be of general formats. Word, Excel, Zip, Mpeg and Wav extensions are typical acceptable formats. Documents can be added to the user data by dragging them from Windows Explorer and dropping them into the User Data window. Documents can also be transferred from the Scratch Pad. 0107 After inclusion of the document in the EDDM the program provides a data configuration management environment.

OVERVIEW 0108 Approach 0109 The invention provides for the following: 0110 1. a design objective database which provides design objectives on different levels of resolution and for different objectives such as cost, quality, time and asset utilization; 0111 2. an enterprise design and product design structure with predefined pigeonholes and a methodology for deploying the design process ensures both comprehensiveness and integration of any design; 0112 3. a knowledge management system continuously updating and expanding database of categorized best practice starting points for ensuring good departure points for the different components in the design process; and 0113 4. the design process is deployed in orderly multi-user fashion using a unique integrated enterprise design data management system, which facilitates audit trails, multi-authoring, document security, and sustainability of the design process. 0114 Thus the invention facilitates enterprise design projects and reduces the complexity of multidisciplinary teamwork by providing a user-friendly, scalable knowledge management supported framework, following a four-pronged approach to facilitate enterprise design and redesign as shown above: 0115 The system may include web centric/intranet facilitated custom design of business processes, products and enterprises. It enables multi-disciplinary and intra-disciplinary teams to design quicker and more effectively by ensuring full re-usability and audit trails of the design processes. 0116 The system thus provides for a dynamic environment that introduces the user to knowledge about various techniques, architectures and relevant information assisting the user's specific enterprise engineering and redesign processes. The product will guide the user through the steps to identify his/her needs, set up requirements, and record the user documentation and logic as the user is working on the enterprise engineering process. 0117 The Design Framework 0118 The system utilises virtual product and enterprise life cycle matrices to create a framework within which all the elements of an enterprise can be identified, described, specified, designed, deployed and integrated for operation. In doing so it facilitates and promotes enterprise integration. The framework makes use of various enterprise transformation methodologies such as the Purdue enterprise reference architecture methodology as a generic enterprise life cycle methodology. 0119 Throughout the framework, the user is enabled with best practice information regarding the design and re-design of the enterprise and/or a selected part of it. The full impact of this framework is realized by creating the enterprise design navigator. The system provides a complete roadmap to aid the What and How of the enterprise engineering design process applied to a single enterprise, aligned to produce a series of one or more products. The system guides the user to follow a series of design steps within a methodology providing design objectives, structure procedures, good starting points and a document management system. 0120 Initially the system will guide the user through a complete enterprise transformation exercise. After this initial use of the design method and system, the user will be able to use the product to implement incremental changes in an integrated manner. This is done by considering the life cycles of both the enterprise and the product in parallel, thus giving the user a framework addressing all (or most) factors that would impact on a decision made. 0121 The system provides design objectives to measure the performance of various product and enterprise design projects. This is used to align the design processes and to prompt the design team to keep certain design criteria in mind when doing an enterprise engineering exercise. 0122 Data Management 0123 The system is more than just a structured source of information. It is a system using information as a resource, to assist the user during a decision making process. It will also provide the user with the ability to store his/her own information (relative to or alongside the best practice information). In doing so the user will build up a complete documented model of the knowledge objects describing his/her enterprise being designed or re-designed. This enterprise design data history allows the designer to capture his or her design intent. 0124 The system may include web centric/intranet facilitated custom design of business processes, products and enterprises. 0125 Support Functions 0126 The system may also provide system supports, which may include: 0127 an implementation support; 0128 training and personnel development support; 0129 cyber database support enterprise design knowledge management. 0130 user group exchange support services. 0131 The cyber database support may include an advanced data administration management system which utilizes publications of technology developments. 0132 Value Added to Organisational Practices 0133 The system creates an environment and an opportunity to access relevant enterprise engineering related information. It Will enhance the ability of management to: 0134 Indicate the relative position of the enterprise/parts of the enterprise on the maturity scale. 0135 Identify areas that require change or improvements that are feasible. 0136 Measure enterprise performance. 0137 Provide the necessary change suggestions to assemble an action plan. 0138 Provide a custom made roadmap for the transition process. 0139 Provide continuous support. 0140 Provide purpose and focus for the transition process. 0141 Research and development program. 0142 Product selection criteria. 0143 Some possible factors are: return on investment, risk characteristics, strategic importance.