به سوی یک منبع دانش برای فرآیند طراحی مشترک: تمرکز در مدیریت تعارض
|کد مقاله||سال انتشار||مقاله انگلیسی||ترجمه فارسی||تعداد کلمات|
|26411||2004||16 صفحه PDF||سفارش دهید||6450 کلمه|
Publisher : Elsevier - Science Direct (الزویر - ساینس دایرکت)
Journal : Computers in Industry, Volume 55, Issue 3, December 2004, Pages 335–350
The increasing competition and complexity of products and processes require new organizational concepts for product development. Collaborative design deals with the sharing of various interests and resources among various actors with the aim of reaching a common purpose. This purpose relies on the development of products using knowledge sharing and interactions with some coordination between these varied activities. The research objective is to provide a collaborative design environment which allows inter-skill collaboration to be coordinated by defining a common repository for knowledge management in a collaborative design situation. This paper will focus on the particular situation of conflict management. From a domain analysis of conflict management process, the first elements of a repository are given by identifying involved knowledge (static view) and formalizing protocols driven by actors to resolve conflicts (dynamic view).
Numerous studies have recently reinforced the importance of collaboration in concurrent engineering. Collaborative design refers to various interests and people put together to achieve a common purpose which means developing a product via interaction and knowledge sharing, with a certain degree of coordination of the various implemented activities. This collaboration occurs among actors provided with various expertises, coming from different skill areas in a multi-geographic and sometimes multi-firm environment. The term “skill” refers to knowledge and competence required to successfully perform work-related functions. This paper focuses on the knowledge component, seen as a set of information which is contextualized according to the skill. Various resources set up around design actors describe a real network around the design project . As in any collective work, it is nevertheless important that various actors taking part in the design activity synchronize their representation. Interactions between designers are guided by two complementary objectives: to be synchronized in time and action and to be synchronized at cognitive level . Through coordination activities, temporal-operating synchronization fulfils one operating function (task allocation) and one temporal function (articulation and coordination of tasks). Cognitive synchronization aims at establishing a mutual knowledge context and at building a common operating repository. In , this cognitive synchronization allows ensuring that each actor possesses sufficient knowledge on relevant facts in correlation with the purpose to be reached, in order to assess a global understanding of the situation. De Terssac and Chabaud  show that actors of a work group have to agree on gaps implicitly left by management and on procedures to be set up in order to fill these gaps. They are supposed to gather their skills and finally establish a common understanding, a shared context . These operations constitute a common repository essentially based on verbal and deliberate communication. Following the example of the DMMS project (Design Management and Manufacturing System) , intra-skills relations are regulated by a stable and precisely defined repository. The latter can even be normalized (for example, BASE-PTA, French standard AFNOR for automation specialists) and do not raise any problems. What is actually missing in this collaborative engineering situation is that no common repository formalizing inter-skill relations exists. As Zarifian  called it, this “space of inter-subjectivity”, inside which identity strategies should fit in the direction of a common knowledge project, does not exist today in a multi-field context. Indeed, collaborative tools currently existing on the market, such as CSCW (Computer Supported Collaborative Work) tools, are organized according to three dimensions of a collaborative activity : communication dimension which allows direct exchange of knowledge between collaborating actors, coordination dimension which defines rules of interaction between actors themselves and in a shared work space and production dimension which allows production of shared objects (such as common documents) and management of access to these shared objects. Most of collaborative tools focus on communication (messaging) and coordination features (approval forms, workflow tools, video-conference tools) but few of them deal with collaboration amongst actors. Regarding this feature, besides shared documentary bases, market tools propose forums to facilitate exchange among actors. Such spaces do not formalize inter-skills relationships and do not guide actors towards setting up a common knowledge project. As for research works, they have focused on the development of strong collaborative tools, such as the CORVETTE project  which extended the concept of workflow to take into account new classes of applications (collaborative work, crisis management, etc.) by proposing innovative transactions models. Other works focused on objects sharing in distributed applications, such as David et al. , who proposed a concept of capillary CSCW by integrating the notion of “nomadism” (capacity of accessing particular knowledge from a mobile post, on any platform, which can connect and disconnect to different information sources). Finally, some research works deal with integrating the concepts of malleability and flexibility in collaborative systems, such as the DARE system proposed by Bourguin et al.  and the AMF-C system  based on a multi-facets approach thanks to patterns which formalize typical collaborative behavior. Then, current research projects mainly focus on problems of coordination and access to shared data, problems which are sensitive in collaborative tools development. They quasi-total raise problems of temporal-operating synchronization but poorly tackle the cognitive synchronization aspect. Indeed, they do not formalize inter-skill relationships and do not guide actors towards the setting up of a common knowledge project. In fact, as an increasing number of actors is involved in an integrated design process, more and more knowledge are then shared and taken into account when developing products . The information system is supposed to collect and capitalize this knowledge by collecting the various involved information. This can mean a selection of the most useful ones . Focusing on the latter aspect, this research has therefore consisted in supplying a collaborative design environment which formalizes inter-skill collaboration. The purpose is to define a repository for information and knowledge management in collaborative design. For that purpose, two research experiments within the CRAN laboratory are considered: • The CAMDers (Computer Aided Mechanical Designers) game whose aim is to analyze the behavior of actors while working in a collaborative design project . This game is performed in the framework of a French research network involving academic partners coming from various horizons (mechanical design, sociology, etc.). • An industrial project within Alstom Power Conversions Company, dealing with the collaborative design of stators of wind motors’ generators. The first stage of this research consisted in a domain analysis of these two experiments which allowed identifying actors’ requirements in a cooperative design context, in terms of involved knowledge (static view of the repository) and collaborative work procedures manipulating this knowledge (dynamic view). Then, after formalizing the above requirements, objects which have to exist in an information system supporting cooperative design were specified. To this aim, a succession of UML models  is used to specify the various facets. In the first part of the paper (Section 2) the key elements of the UML approach adopted to specify the cooperative information system is presented. In the second part (Section 3) the results of the domain analysis are presented. First, the collaborative design process is presented (Section 3.1). Then, the particular situation of conflict management process is described (Section 3.2). The static view of the proposed repository is then developed by identifying knowledge involved in collaborative design processes, such as conflict management process (Section 4). Following this, the dynamic view of the repository is developed by identifying the main features expected from the targeted system (in terms of UML use cases), formalizing the interactions composing the identified use cases thanks to UML sequence diagrams and identifying the objects required in the proposed system (UML class diagram) to satisfy users’ expectations (Section 5). Finally, Section 6 illustrates the proposed repository on an effective design project within Alstom Power Conversions Company.
نتیجه گیری انگلیسی
Actors in collaborative product design evolve today in a context requiring increasing interaction, sharing of knowledge and skills as well as the reuse of experiences resulting from previous projects. The objective of this paper was to describe an environment supporting collaborative design. From the characterization of the studied design processes, an identification of the involved knowledge (static view) and a formalization of the various interactions between design participants (dynamic view) were proposed on the most demanding case: “conflict management”. Such specifications constitute the first elements of a knowledge repository dedicated to collaborative design process which contributes to closing the gaps in current PDM systems in terms of collaboration and knowledge capitalization during design process. However, the specification of such a repository has to be completed by structuring the static view (collaborative knowledge), by considering other situations during collaborative design and by taking into account other existing tools. Indeed, the proposed collaborative system is complementary to other software solutions available on the market, aiming at facilitating communication and exchanges between actors. The current repository allows capitalization of knowledge related to recurrent collaborative design problems and enables an organization to keep trace of the design process by storing the various work flows handled during the resolution of a conflict. Such an approach can constitute a basis for a domain ontology for conflicts in product design. As defined by Gruber, an ontology is an explicit specification of a conceptualization . It is a knowledge-based specification that typically describes a taxonomy of the tasks that define the knowledge . The classification proposed by Van Heijst et al.  depicts three types of ontology that are: domain ontologies (specific to a domain: in generator design, this will be stator, rotor, electrical connection, etc.), applicative ontology (specific to a given application: in generator design, the term related to the stator will be diameter, resonance frequency, etc.) and generic ontology (a kind of universal concepts reusable in various domains). The chosen approach can be seen as a tool for promoting the setting up of an ontology specific to an application in product design, since the various iterations on a problem and gathered in the collaborative entity allow the adopted and refused solutions to be matched both with the explanation and the justification so that a context can be built around these solutions. When instantiated, this model can therefore facilitate the access to customized and on-demand solutions for a specific type of problem in the product design. The ontology and its progressive enrichment, defined in a natural language which is that using collaborative knowledge and pre-requisite information, will guide the design actors in further design projects by proposing a content adapted to the problem they are solving. For example, in the stator design problem at Alstom Power Conversion Company, the choice of integrating the cooling system within the stator and the explanation accompanying this solution, plus the rejected solutions (minimizing an external cooling system, reducing the global diameter of the generator) has created ontology for the resonance problems.