1,146 research outputs found

    Review of research in feature-based design

    Get PDF
    Research in feature-based design is reviewed. Feature-based design is regarded as a key factor towards CAD/CAPP integration from a process planning point of view. From a design point of view, feature-based design offers possibilities for supporting the design process better than current CAD systems do. The evolution of feature definitions is briefly discussed. Features and their role in the design process and as representatives of design-objects and design-object knowledge are discussed. The main research issues related to feature-based design are outlined. These are: feature representation, features and tolerances, feature validation, multiple viewpoints towards features, features and standardization, and features and languages. An overview of some academic feature-based design systems is provided. Future research issues in feature-based design are outlined. The conclusion is that feature-based design is still in its infancy, and that more research is needed for a better support of the design process and better integration with manufacturing, although major advances have already been made

    An assembly oriented design framework for product structure engineering and assembly sequence planning

    Get PDF
    The paper describes a novel framework for an assembly-oriented design (AOD) approach as a new functional product lifecycle management (PLM) strategy, by considering product design and assembly sequence planning phases concurrently. Integration issues of product life cycle into the product development process have received much attention over the last two decades, especially at the detailed design stage. The main objective of the research is to define assembly sequence into preliminary design stages by introducing and applying assembly process knowledge in order to provide an assembly context knowledge to support life-oriented product development process, particularly for product structuring. The proposed framework highlights a novel algorithm based on a mathematical model integrating boundary conditions related to DFA rules, engineering decisions for assembly sequence and the product structure definition. This framework has been implemented in a new system called PEGASUS considered as an AOD module for a PLM system. A case study of applying the framework to a catalytic-converter and diesel particulate filter sub-system, belonging to an exhaust system from an industrial automotive supplier, is introduced to illustrate the efficiency of the proposed AOD methodology

    Integrated product relationships management : a model to enable concurrent product design and assembly sequence planning

    Get PDF
    The paper describes a novel approach to product relationships management in the context of concurrent engineering and product lifecycle management (PLM). Current industrial practices in product data management and manufacturing process management systems require better efficiency, flexibility, and sensitivity in managing product information at various levels of abstraction throughout its lifecycle. The aim of the proposed work is to manage vital yet complex and inherent product relationship information to enable concurrent product design and assembly sequence planning. Indeed, the definition of the product with its assembly sequence requires the management and the understanding of the numerous product relationships, ensuring consistency between the product and its components. This main objective stresses the relational design paradigm by focusing on product relationships along its lifecycle. This paper gives the detailed description of the background and models which highlight the need for a more efficient PLM approach. The proposed theoretical approach is then described in detail. A separate paper will focus on the implementation of the proposed approach in a PLM-based application, and an in-depth case study to evaluate the implementation of the novel approach will also be given

    Ship product modelling

    Get PDF
    This paper is a fundamental review of ship product modeling techniques with a focus on determining the state of the art, to identify any shortcomings and propose future directions. The review addresses ship product data representations, product modeling techniques and integration issues, and life phase issues. The most significant development has been the construction of the ship Standard for the Exchange of Product Data (STEP) application protocols. However, difficulty has been observed with respect to the general uptake of the standards, in particular with the application to legacy systems, often resulting in embellishments to the standards and limiting the ability to further exchange the product data. The EXPRESS modeling language is increasingly being superseded by the extensible mark-up language (XML) as a method to map the STEP data, due to its wider support throughout the information technology industry and its more obvious structure and hierarchy. The associated XML files are, however, larger than those produced using the EXPRESS language and make further demands on the already considerable storage required for the ship product model. Seamless integration between legacy applications appears to be difficult to achieve using the current technologies, which often rely on manual interaction for the translation of files. The paper concludes with a discussion of future directions that aim to either solve or alleviate these issues

    Multiple viewpoint modelling framework enabling integrated product-process design

    Get PDF
    Nowadays, companies have to cope with numerous constraints at organisational and technical levels in order to improve their competitiveness edges such as productivity, efficiency, and flexibility. Integrated product-process design becomes more and more complex to manage because of increasingly customized products related to various stakeholders and concerns geographically distributed. It is still represents a huge challenge, especially in the early phases of product development process. In such a context, the management of information within integrated product-process design highlights needs in a consistent engineering model that enables product lifecycle management (PLM) integration. The paper presents a novel multiple viewpoint framework called multiple viewpoint assembly oriented, considering product design and assembly process domains in the broader context of concurrent engineering and PLM. The proposed framework describes the consistency, the propagation of information change, and mechanisms of views generation among the product lifecycle stages in order to support assembly oriented design philosophy. A new modelling language called System Modeling Language is used to describe the proposed model from a systems engineering point of view. The implementation of the model in a Web-service called PEGASUS as an application for PLM systems is describe

    A Design Environment for Product Knowledge Management and Data Exchange

    Get PDF
    This paper reports on a distributed design environment under development for product knowledge management and information exchange. The system is able to use the company’s existing base of knowledge and to push the manufacturing knowledge higher up into the design chain to reduce the need for costly and time consuming reworks and engineering changes. The design environment uses a knowledge based system ProtĂ©gĂ© and enables data/knowledge exchange through International Standards for Product Model Exchange (ISO STEP) and the Resource Description Framework

    Design: the quintessential business transaction

    Get PDF
    The fundamental structures that underpin business activities must evolve and change in order to equip companies to thrive in a market whose characteristics are increasing competition and instability. The incremental advances in applied computing technology and business methodologies which focus on improving one aspect of company operations ignore the need for an underlying structure and model through which to engage any and all functions in a consistent and integrated fashion. Indeed, many exacerbate the problem through closed architectures, isolationist views of entity data storage and rigid methodologies imposed on the company that employs them. The Product Model proposed fulfils that role. It is a model of the processes and entities that a company uses to conduct its business, at all levels and across all departments. Two other concepts are exposed: product model data and the design history record. Product model data are the values of instances of product model entities and relations, created to represent a particular design, artefact or object. The design history record captures the data and functions used in a transaction and the order and context in which they are used. To exercise these concepts, a software suite was written, the Glasgow Utility for Integrated Design, Guide. It supports the definition of a proud model and its subsequent use in the creation of product model data. Each interaction with the system is recorded, thus capturing the design history record, which can subsequently be processes to various advantageous ends. The major such uses are for re-use of part information in other designs and the extraction of design best practice with which to augment the company's design methodology. It is a comprehensive record, since all business processes are supported by, and can be transacted through Guide. Guide has been used to validate the adequacy of the product model and has established many benefits through its use. Applications in many spheres are possible; engineering has been the primary focus for exemplars and case studies. The development was carried out under the scrutiny of constant validation and testing in live situations with several industrial partners. Guide is built on industry standard tools and uses relational database technology to store frame-based representations of entities, methods and relationships. The design of project plans is carried out on the same platform used to support the project itself; the design data are not dissociated from the project controlling mechanism. Resources, including staff, are engaged according to requirements and audit mechanisms allow for constant re-evaluation of the project development. Control and communication mechanisms support applications in an extended enterprise environment and the distribution of resources that this entails

    Open Standard, Open Source and Peer to Peer Methods for Collaborative Product Development and Knowledge Management

    Get PDF
    Tools such as product data management (PDM) and its offspring product lifecycle management (PLM) enable collaboration within and between enterprises. Large enterprises have invariably been the target of software vendors for development of such tools, resulting in large entralized applications. These are beyond the means of small to medium enterprises (SME). Even after these efforts had been made, large enterprises face numerous difficulties with PLM. Firstly, enterprises evolve, and an evolving enterprise needs an evolving data management system. With large applications, such configuration changes have to be made at the server level by dedicated staff. The second problem arises when enterprises wish to collaborate with a large number of suppliers and original equipment manufacturer (OEM) customers. Current applications enable collaboration using business-to-business (B2B) protocols. However, these do not take into account that disparate enterprises do not have unitary data models or workflows. This is a strong factor in reducing the abilities of large enterprises to participate in collaborative project

    A manufacturing model to support data-driven applications for design and manufacture

    Get PDF
    This thesis is primarily concerned with conceptual work on the Manufacturing Model. The Manufacturing Model is an information model which describes the manufacturing capability of an enterprise. To achieve general applicability, the model consists of the entities that are relevant and important for any type of manufacturing firm, namely: manufacturing resources (e.g. machines, tools, fixtures, machining cells, operators, etc.), manufacturing processes (e.g. injection moulding, machining processes, etc.) and manufacturing strategies (e.g. how these resources and processes are used and organized). The Manufacturing Model is a four level model based on a de—facto standard (i.e. Factory, Shop, Cell, Station) which represents the functionality of the manufacturing facility of any firm. In the course of the research, the concept of data—driven applications has emerged in response to the need of integrated and flexible computer environments for the support of design and manufacturing activities. These data—driven applications require the use of different information models to capture and represent the company's information and knowledge. One of these information models is the Manufacturing Model. The value of this research work is highlighted by the use of two case studies, one related with the representation of a single machining station, and the other, the representation of a multi-cellular manufacturing facility of a high performance company
    • 

    corecore