5th International Conference On Digital Enterprise Technology , livre ebook

publibook - Alain Bernard

Découvre YouScribe en t'inscrivant gratuitement

Je m'inscris

Obtenez un accès à la bibliothèque pour le consulter en ligne
En savoir plus

884 pages

Français

Vous pourrez modifier la taille du texte de cet ouvrage

Obtenez un accès à la bibliothèque pour le consulter en ligne
En savoir plus

A propos
Informations
Extrait

Description

Digital Enterprise Technology (DET) is more than a concept. Companies are facing new challenges in a context where the references are mostly numerical. Nowadays, digital methods and tools are widely generalized. DET 2008 allowed excellent exchanges about “the collection of systems and methods for the digital modeling and analysis of the global product development and realization process, in the context of lifecycle management”.

Sujets

Techniques

Philosophie et théologie

French frigate Entreprise

Technologie

Digital

Technique

Entreprise

Informations

Publié par	publibook
Date de parution	12 juillet 2012
Nombre de lectures	0
EAN13	9782748384475
Langue	Français
Poids de l'ouvrage	1 Mo

Informations légales : prix de location à la page 0,0165€. Cette information est donnée uniquement à titre indicatif conformément à la législation en vigueur.

Extrait

5th International Conference On Digital Enterprise Technology
Alain Bernard
Publibook

Le Code de la propriété intellectuelle interdit les copies ou reproductions destinées à une utilisation collective. Toute représentation ou reproduction intégrale ou partielle faite par quelque procédé que ce soit, sans le consentement de l’auteur ou de ses ayants cause, est illicite et constitue une contrefaçon sanctionnée par les articles L 335-2 et suivants du Code de la propriété intellectuelle.

Publibook
14, rue des Volontaires
75015 PARIS – France
Tél. : +33 (0)1 53 69 65 55
Keynote speakers

Denis ALLAIN
(Aker Yards France)
Digital and Collaborative Design for Ship Building
Presentation of how Aker Yards manage his IT project in order to build the next generation of tools to support collaborative design in extended enterprise. The main objectives are :
- increasing productivity through the control of the process, the preparation of work (store the know-how for best design,
- reducing non-value added tasks (delete / automation), for control design
- optimizing the trade between AYFr and its network of sub contractors

Patrick GUERIN (Airbus Nantes)
3D measuring application industrialisation from the aircraft digital mockup
In the aeronautic field, the measurement application industrialization follows four steps:
- The aircraft definition (digital mock-up with geometric, dimension and tolerance requirements)
- The choice of the measurement means (accuracy and job environment)
- The software(s)(means driver & measurement results treatment)
- The design of the tooling parts(measure devices and controlled sub-assembly reference)

The choice of the measurement means depends on the design office tolerances and the volume that must be measured. The next step is the tooling specification. For the software, Metrolog is currently used in Airbus Nantes. Finally, the lead time needed to industrialize a measurement application is about 12 months.

Prof. Dr. Ir. Fred J.A.M. van Houten
(University of Twente)

The role of visualization, simulation and serious gaming in collective decision making
Since three years, the department of Design, production and management of the University of Twente has been operating a large scale virtual reality lab. The lab is used for the development and testing of new design methods and tools. Under the national Innovative Research Program "Integrated Product Creation and Realization" several (multi-) PhD projects are carried out. In these projects in the field of Synthetic Environments for Scenario Based Design, Smart Synthesis Tools, Design for usability and Automatic Generation of Control Software for Mechatronic Systems. Apart from these applied fundamental research projects with active industry participation the lab is also used to commercially exploit the results of the research. In cooperation with the Thales company, the Technology Exchange Cell (T-Xchange) is moderating collective decision making sessions for clients from industry and government. The Keynote will elaborate on the individual projects and their relevance for the progress of fundamental design oriented research. Also some typical examples of Effect Based Solution (EBS) sessions of T-Xchange will be discussed.

Chapter 1: Distributed and Collaborative Design
Chairpersons : F. Noël and D. Brissaud

Supporting requirement engineering in complex product design

Maria Claros
Laboratoire G-SCOP
Maria.Claros@g-scop.inpg.fr
Guy Prudhomme
Laboratoire G-SCOP
Guy.prudhomme@g-scop.inpg.fr

Daniel Brissaud
Laboratoire G-SCOP
Daniel.Brissaud@g-scop.inpg.fr
Abstract
Requirement engineering and management has become a complex task in concurrent engineering context. Due to the co-evolutionary design process nature requirements have to be taken into account by all designers as soon as possible and have to dynamically change throughout the design process. The F-Requirement Relation network (FRRN) is proposed as the core element to support the design process. The idea was tested on a complex product design in a French large company. It can be concluded that building such a network can be achieved practically but organisational conditions have to be managed to make it more efficient: the first one is related to the project and its organisation in expertise groups that fix responsibilities; the second one is related to the product, which complexity is pragmatically split into sub-projects that are more expert oriented than project oriented.
keywords
Collaborative design, Requirement, Functional Requirement Relation Network
1. Introduction
This work deals with the impact of the complexity of product designed in complex industrial organisations on the requirement engineering and management.
On the first hand, products became more complex. An industrial product is considered complex when the management of the knowledge handled to understand an existing product is difficult or even sometimes impossible. The first level of complexity is linked to the fundamentals like physics, mechanics, material sciences, thermodynamics, computer sciences, etc, necessary for its behavioural modelling. A second level of complexity is due to the necessary interaction between these fundamentals in the every day life of most products: products which include mechanic and electronic technologies are common examples. In front of this increasing complexity of products, requirement engineering and management have become important tasks of the engineering design process, which impact a lot the product success to meet customers’ desires and engineers’ objectives.
On the other hand the increasing market competition and pressure on quality, cost and lead-time have led to changes in the organizational mode of companies. Indeed, to tackle difficulties coming from competitiveness, the design process has become collective. The aim of this movement is to enable all the life cycle stakeholders to work concurrently. A stakeholder of the design process is a person who is involved in the design process of the product, whatever his task is. In this way, most of industrial organizations have shift from a hierarchical structure to a more transversal one. Concurrent Engineering is a model of this new organizational mode, where the design process of a product is a collective and simultaneous activity. Due to this concurrent engineering context, all the experts involved in the life cycle of the product generate needs and constraints that drive the design process towards the physical solution satisfying all of them.
It is now assumed that the design problem and the adapted solutions simultaneously evolve while designing (Gero, 2002) (Maher, 2003) (Lonchampt, 2006). To manage the product requirements and keep all the features coherent, the F-Requirement Relation network (FRRN) was proposed as the core element to support the design process (Claros-Salinas, 2007). FRRN links external functions and criteria to geometrical and technological product parameters, and therefore supports the activity of designers. The main question of the work presented in this paper is: what is the impact of these complexities on the requirement network, and particularly on means and methods to express design requirements along the design process?
The paper is organised as the following. In section 2, our point of view about the requirement network concept will be defined and then a model of the design process that points out this network proposed. In section 3, this model is implemented in a theoretical framework to highlight how complexity can impact the requirement network characterization. Analysis of observations in a French large company will be presented in section 4. It can be concluded that building such a network can be achieved practically but organisational conditions have to be managed to make it more efficient: the first one is related to the project and its organisation in expertise groups that fix responsibilities; the second one is related to the product, which complexity is pragmatically split into sub-projects that are more expert oriented than project oriented.
2. Requirements and mechanical engineering design
2.1. Requirements
In a Concurrent Engineering context, expectations of each product lifecycle stakeholder have to be considered as soon as possible. Each of them defines his own specifications for the product. The first stakeholder to be considered is the external client, that is to say the one whom the product is developed for. Expectations of the external clients are generally called needs and are often expressed in a natural language. Internal clients are members of the company and bring expert points of view (products design, manufacturing …) from the industrial organization. They formulate what is called constraints. A constraint is a restriction, a limit or a regulation imposed on a product, a project or a process and is generally expressed in the form of criteria to be respected. The literature review (Harwell, 1993) (Jixin, 1996) gave us different definitions about the requirement concept. Our point of view (Claros-Salinas, 2007) is that requirements include all needs and constraints of the product being designed and coming from all the product life cycle stakeholders. Requirements contain the why of the product, the function it must fulfil, and the how the product has to fulfil them, criteria and associated levels which characterise the way these functions have to be respected.
The necessity of a standard language to enable designers to integrate all these needs and constraints in their rationale was assumed. This language should help them to share their points of view about needs and constraints. It is postulated here that functional analysis could be this language. The Functional requirement (or F-requirement) will be used to