Location of Repository

Integrated information model for managing the product introduction process

By Devi Thirupathi

Abstract

The thesis proposes an integrated product introduction (PI) information model for managing the product introduction process in an efficient manner. Through the process of product introduction, ideas and needs are converted to the information from which technical systems and products can be made and sold. Two critical factors for its success are the management of the product introduction activities, and the quality and functionality of its output (i.e. the product) which itself depends on the quality of the PI process. The process is as effective as the decisions made within it, and as efficient as the speed with which the information required for each decision is made available.\ud \ud In order to improve the efficiency of the management of the project in meeting its diverse targets (project time, project cost, product cost and uparrow product functionality), a model that integrates the targets would be essential in relating the activities of the project to their outcomes. Existing information models in related areas such as design, product development, project management, computer aided design and manufacturing consider some of these targets, but not all of them simultaneously. Especially product functionality is not considered along with the other targets of the PI project.\ud \ud The project introduction information includes managerial and technical information and complex associations among these two categories. Its representation places a challenging and novel set of demands on database technology as it is evolving, distributed and heterogeneous. Existing information models do not address the link between the managerial and technical information, and their continual evolution. Based on a detailed analysis of its nature and content, the thesis presents a three dimensional model of the product introduction information from three related but different viewpoints:- (1) entity-relationship or objects, (2) intra-layer integration and (3) evolution, each capturing important aspects of the PI information, but all required for a complete description. The overall three dimensional information model includes the following layers:- from view 1 - product functionality, process or project, product introduction resources, product and information map; from view 2 - node, relationship, and organisation; from view 3 - meta-model, data model, and data. Each model describes one aspect of the product introduction information but contains references to the others. The building blocks of the information model are described using schema definitions

Topics: HF, QA76
OAI identifier: oai:wrap.warwick.ac.uk:2954

Suggested articles

Preview

Citations

  1. (1990). (presenter on behalf of ESPRIT AMICE Consortium),
  2. 1994b, A Functional Data Model For Assemblies,
  3. (1993). A Function-oriented Modeler Prototype, Design for
  4. (1994). A functional data model for assemblies used to verify product design specifications,
  5. (1996). A Guide to the Project Management Body of Knowledge,
  6. (1995). A manufacturing Model to Support Data-Driven Applications for Design and Manufacturing,
  7. (1995). A Methodology for an Integrated Design and Process Planning Based on a Concurrent Engineering Reference Model,
  8. (1990). A Model of New Product Development: An Empirical Test,
  9. (1994). A Model-Based Method for Organising Tasks
  10. (1994). A Multi-Project Management Framework for New Product Development,
  11. (1993). A New View on Function Modeling,
  12. (1994). A process-based approach to computer supported engineering design,
  13. (1993). A product definition model for concurrent design,
  14. (1993). An Analysis of Coordination Problems
  15. (1993). An Application of Extended Function Logic to the Design of a Wearable Computer,
  16. (1992). An Information Sharing System
  17. (1991). An Introduction to Database Systems, Fifth Edition,
  18. (1996). An Introduction to the Design Process,
  19. (1987). Analysis of the Engineering Design Process in an Industrial Context,
  20. (1993). Applied Production and Operations management, Fourth edition,
  21. (1994). Architecture and Methodology for concurrent Engineering,
  22. (1993). Architecture of Integrated Information Systems (ARIS), Information Infrastructure for Manufacturing, Edited by
  23. (1989). Blackboard for Design Evolution, Red book of Functional Specifications for the DICE Architecture, Working draft,
  24. (1994). Business Process Engineering - Reference Models for Industrial Enterprises,
  25. (1990). CIM-OSA - An Illustrative Example of How to Apply the Modelling Framework,
  26. (1989). CIM-OSA: Computer Integrated Manufacturing -Open System Architecture,
  27. (1993). CIMOSA Pilot Implementation for Technology Transfer, Information Infrastructure for Systems Manufacturing, Edited by
  28. (1993). CIMOSA: Enterprise Modelling and Enterprise Integration using a Process-Based Approach, Information Infrastructure for Manufacturing, Edited by
  29. (1998). Conceptual Design Capture,
  30. (1993). Concurrent Engineering - Automation, tools and Techniques,
  31. (1994). Concurrent Engineering Enablers -Engineering Libraries,
  32. (1991). Concurrent Engineering through Product Data Standards,
  33. (1992). Concurrent Engineering Transactions,
  34. (1993). Concurrent Engineering,
  35. (1994). ConcurrentISimultaneous Engineering (Methods, Tools and Case studies),
  36. (1993). Configuration Evaluation and Optimisation of Technical Systems,
  37. (1992). Coordinating a Virtual Team, CERC
  38. (1993). Creative & Systematic Team-Work Using Abstract Concepts and Concrete Entities,
  39. (1994). Critical Parameters These are the control parameters that are critical (or paramount) in their effect on the function. If a critical parameter goes out of the range prescribed to it in the design, then the function is likely to experience a failure (Fox
  40. (1995). D Set of instructions (specifications, drawings, schedules etc. ) necessary to construct an artefact (ý) artefact itself (BS7000:
  41. (1980). Data models in Database Management,
  42. (1996). Design Automation through Knowledge Based Systems,
  43. (1993). Design Management Processes that can be used by Practitioners,
  44. (1994). Design Methodology in Practice,
  45. (1994). Designing for Function, Engineering Designer, Jan/Feb,
  46. (1996). Designing in an interplay with a product model - explained by design units,
  47. (1995). Development A process by which a product is brought to a standard at which it is ready to be manufactured or provided respectively (BS7000:
  48. (1997). Development of a Manufacturing Engineering System for the Motor Industry,
  49. (1998). Development of an Information Model for Concurrent Engineering in Product Introduction,
  50. (1988). Dynamic Manufacturing - Creating the Learning Organization,
  51. (1996). Effective process An effective process is defined as one that results in a product satisfying the actual need (Blessing 1993); in other words, project effectiveness is about meeting product quality or functionality (Hauptman and HirJi
  52. (1992). Effective Product Design and Development - How to Cut Lead time and Increase Customer Satisfaction, (Iflinois : Business One Irwin).
  53. (1993). Efficient process An efficient process is defined as one that is both effective and in which the applied resources do not exceed the planned resources (Blessing
  54. (1993). Engineering and Management for Rapid Product Development,
  55. (1984). Engineering Design, Edited by Wallace K., (London: Design Council).
  56. (1992). Engineering Information Management Systems - Beyond CADICAM to Concurrent Engineering Support,
  57. (1997). Engineering is not enough,
  58. (1976). Entity-Relationship Model - Towards a Unified View of Data,
  59. (1998). Factors affecting the successful development of new products,
  60. (1994). Failure modes A failure mode occurs when the response from a function exceeds (either positively or negatively) the limit expected from the design (Fox
  61. (1997). Form development Is the evolution of components, how they are configured relative to each other and how they are connected to each other (Ullman
  62. (1997). Form The form of the product is roughly defined by the spatial constraints that provide the envelope in which the product operates (Ullman
  63. (1998). Foundation for ObjectlRelational Databases: The Third Manifesto,
  64. (1992). Frameworks for Concurrent Engineering and Rapid Prototyping,
  65. (1991). Function Analysis - Systematic Improvement of Quality and Performance,
  66. (1988). Functional Requirements and Conceptual Design of the Feature-Based Modelling System,
  67. (1994). Functional Understanding of Assembly Modelling,
  68. (1993). GIM (GRAI Integrated Methodology) and its evolutions A methodology to design and specify Advanced Manufacturing Systems, Information Infrastructure Systemsfor Manufacturing, Edited by
  69. (1993). Guidelines for Product Data Model Formulation Using Database Technology,
  70. (1989). How Process Logistics Planning Can Enhance the Effectiveness of Simultaneous Engineering,
  71. (1994). Implementing Total Quality Management,
  72. (1986). Influence of task types on the relationship between communication and performance: the case of software development,
  73. (1994). Information Modelling the EXPRESS way,
  74. (1994). Information Models for use in Product Design:
  75. (1994). Instance An object described by a class. 278 Latitude This is the full range of response as described by the failure modes. In other words, it is the satisfactory working range of the function (Fox
  76. (1995). Integrating Product and Project Management -A New Synergistic Approach,
  77. (1989). Knowledge Integrated Product Modelling for Design and Manufacture,
  78. (1989). Knowledge Management for preliminary Computer-aided mechanical design,
  79. (1993). Managing the Development of New Products - Achieving Speed and Quality Simultaneously Through Multifunctional Teamwork,
  80. (1994). Manufacturing Excellence, the competitive edge,
  81. (1994). Marketing Management and Strategy,
  82. (1993). Meta-modeffing: How, Why and What?,
  83. (1994). Meta-model Information model for the information that can be expressed during modeling Noise factors These are factors (parameters) directly affecting the function which are outside the control of the designer (Fox
  84. (1993). Methodical Product Development - Experience of a Practical Study,
  85. (1993). Model-based Information Access,
  86. (1995). Modelling Evolving Product Data for Concurrent Engineering,
  87. (1994). Modelling Product families in an engineering framework,
  88. (1992). Modelling Product Structures by Generic Bills-ofMaterials,
  89. (1993). Notes On Concurrent Engineering,
  90. (1986). Object-Oriented Development,
  91. (1995). Object-Relational Database Technology, A UniSQL Whitepaper,
  92. (1989). Organising the tasks in
  93. PART 10,1995, British Standard Design Management System, Glossary of terms used in design management,
  94. PART 2,1997, Design Management System: Guide to managing design of manufactured products,
  95. PART 4,1996, Design Management System: Guide to managing design in construction,
  96. (1992). Potentials of Advanced Concurrent Engineering Methods, Manufacturing in the Era of Concurrent Engineering, Edited by Halevi
  97. (1992). Product Development: Success Through Product and Cycle-time Excellence,
  98. (1989). Product Modelling for Design and Production,
  99. (1990). Progress Towards Standards for CIM Architectural Frameworks,
  100. (1996). Project A project is a temporary endeavour undertaken to create a unique product. Temporary means that every project has a definite beginning and definite end. Unique means that the product is different in some distinguishing way from all similar products
  101. (1995). Project DERWENT -A new approach to product definition and manufacture, Rolls-Royce Aerospace group, Research Lecture Hand-out,
  102. (1995). Project Management -A system approach to planning, Scheduling and Controlling,
  103. (1992). Promoting Concurrent Engineering Through Information Sharing,
  104. (1993). Quality through Design - The key to successful product delivery,
  105. (1995). Reengineering Handbook, A step-by-step guide to Business transformation,
  106. (1994). Relationship An association between two constructs in a model. 279 I vas ponses These are the outputs from the function which are measurable. They may be noise factors for the next function within the system (Fox
  107. (1991). Representing and Managing Constraint Data in A ComputerBased Cooperative Product Development Scenario, CERC
  108. (1996). Reviewer's Guide to ISO 10303-221, PDT Solutions,
  109. (1988). Semantic Data Models,
  110. (1993). Simultaneous Engineering in Space Development,
  111. (1992). Software Engineering A Practitioner's Approach,
  112. (1979). Structured Analysis and System Specification,
  113. (1992). Support of Collaborative Engineering through a Shared High Level Product Model - Basic Requirements and Concepts, in:
  114. (1993). Supporting Product Definition Process,
  115. (1994). The development of cognitive models of planning for use in the design of project management systems,
  116. (1993). The Influence of Design Visualisation in Reducing Investment in New Product Development,
  117. (1996). The Influence of Process Concurrency on Project Outcomes in Product Development: An Empirical Study of CrossFunctional Teams,
  118. (1993). The Integrated Product Development Process: Issues and Methods,
  119. (1996). The structuring of products and product prograrnmes,
  120. (1990). Theory of Domains,
  121. (1995). Time Equals Money - But where does it all go?, IEE Colloquium on Concurrent Engineering - Getting it Right First time,
  122. (1995). Total Quality Management., Text with Cases,
  123. (1993). Towards A Theory for Functional Reasoning in Design,
  124. (1997). Towards an Information Model for Concurrent Engineering in Product Introduction,
  125. (1993). Winning at New Products - Accelerating the Process from Idea to Launch, Second Edition,

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.