crecos bonjour 12-11-2010-for diffusion

From the architecture of modular products

to the organization of development systems

Eric BONJOURAssociate Professor

University of Franche-Comté - France

CRECOS 2010

November, 12th , 2010

Aalto University, Helsinki

FEMTO-ST / Department AS2M

E. Bonjour - CRECOS - Helsinki - 11-12 November, 2010 2 / 28

Context

Issues

Focus

Further work

Lyon

Besancon

Helsinki


Context

Issues

Focus

Further work

Outline

1. 1. ResearchResearch contextcontext: architectural design: architectural design

4. 4. FurtherFurther researchresearch

2. 2. ResearchResearch issues and issues and relatedrelated contributionscontributions

3. Focus on a 3. Focus on a methodmethod to to propagate product propagate product

architecture decisions onto the project organizationarchitecture decisions onto the project organization


Context

Issues

Focus

Further work

Increasing complexity of products

� from a functional viewpoint (requirements for

high performance, mass customization …)

� difficult to properly specify system

requirements

� from a physical viewpoint (number of

components and interactions)

� difficult to integrate the system

� from a behavioral viewpoint (number of

operating modes and states)

�difficult to predict the system behavior

and to validate it


Context

Issues

Focus

Further work

Increasing complexity of development systems

� functional viewpoint

� � performance of projects (Quality, Cost, Delay)

� � concurrent processes

� physical viewpoint

� � change of organizations, job positions …

� � persons involved in projects (102 or 3)

� � skills (102 or 3) …

� � collaboration and

coordination efforts

� Needs for methods to help managers to

structure product development organizations

Source : UTBM

Architecture

Detailed design

Specification


Context

Issues

Focus

Further work

Architectural design

� Two complementary approaches

1- According to [Pimmler and Eppinger, 1994],

� Description of elements that build the system and the

interactions that link them.

� Aim: handle complexity by decomposing the system into

inter-related "modules":

� functional view: [Stone et al., 2000];

� physical view: [Kusiak, 1996; Whitfield, 2002;

Yassine, 2007; etc.]

9000E5

0906E4

0090E3

0069E2

0000E1

E5E4E3E2E1DSM

(Design Structure

Matrix)

[Warfield 1973] E1

E2

E4

E3

E5

S

E1

E2

E4

E3

E5

S

dependency strength or coupling intensity


Context

Issues

Focus

Further work

Modules and integrative elements

XXXXIIE

XXXH

XXG

XXF

XXXXE

M2

XXXXD

XXC

XXXB

XXA

M1

IHGFEDCBA

An integrative element is interacting with all An integrative element is interacting with all

the modules without belonging to a module the modules without belonging to a module

[Browning, 2001]. [Browning, 2001].

A module is A module is ““a unit whose structural elements are a unit whose structural elements are

powerfully connected among themselves and powerfully connected among themselves and

relatively weakly connected to elements in other relatively weakly connected to elements in other

unitsunits”” [Baldwin and Clark, 2000] [Baldwin and Clark, 2000]

clusteringclustering

algorithmalgorithm



Context

Issues

Focus

Further work


2- Mapping of one view onto another [Ulrich 1995] :

� functional layout,

� mapping of functional elements onto physical

elements,

� specification of the interfaces between physical

elements:

F1

F2 F3

F4 F5

F6

C1

C2

C4

C3

C5

090000C5

309000C4

900600C3

000900C2

000069C1

F6F5F4F3F2F1

DMM, Domain Mapping Matrix[Danilovic et Browning, 2004])

mapping

Physical view

Functional view

Contribution levels of C2 and C3

to the fulfilment of F3


Context

Issues

Focus

Further work

A key job position: system architect

� define (ou adapt) architectures and interfaces,

� define the project organization (project breakdown

into tasks and teams, competency management),

� the aim: efficient development projects

� guarantee that the system be properly integrated,

� study operating / dysfunctioning modes and states of

the system

General issue :

� develop models, methods and tools to support these

technical and organizational activities and their

inter-relationships.


Context

Issues

Focus

Further work

Outline







Context

Issues

Focus

Further work

Research issue: how to handle the global complexity

(at least) 3 themes

� T1: system-product architecture: "optimize" / justify the mapping of functional sets onto physical sets

(selection among different alternatives),

F1

F2 F3

F4 F5

F6

C1

C2

C4

C3

C5

Alternative 1

Functions

Components

C1

C2

C4

C3

C5

F1

F2 F3

F4 F5

F6

Alternative 2

Functions

Components

mapping

Physical view

Functional view


Context

Issues

Focus

Further work


(at least) 3 themes

� T1: system-product architecture

� T2: development system architecture: "optimize"

/ justify the assignment of development tasks to actors,

T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

Alternative 1

T6 T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

Alternative 2

T6

Process

Actors

Process

Actors

mapping

Physical view

Functional view


Context

Issues

Focus

Further work


(at least) 3 themes

� T1: system-product architecture:

� T2: development system architecture:

� T3: mapping / coupling of different project domains

� Since 2007, growing interest

(Eppinger, Sosa, Browning, Danilovic, Lindemann, Aldanondo,…)

T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

development system

T6

Processes

ActorsC1

C2

C4

C3

C5

F1

F2 F3

F4 F5

F6

system-product

Functions

Components

coupling

mapping

Physical view

Functional view


Context

Issues

Focus

Further work

Related contributions� T3: mapping / coupling between different domains

(1) E. Bonjour, S. Deniaud, M. Dulmet, G. Harmel, "A fuzzy

method for propagating functional architecture constraints to

physical architecture", Transactions of ASME, Journal of

Mechanical Design , Vol. 131, N° 6, June, 2009

(2) E. Bonjour, M. Dulmet, S. Deniaud, JP. Micaëlli, "Propagating

product architecture decisions onto the project organization:

a comparison between two methods", International Journal of

Design Engineering, Vol. 2, N° 4, 2009, pp.451–471

F1

F2 F3

F4 F5

F6

C1

C2

C4

C3

C5

Alternative 1

Fonctions

Composants

C1

C2

C4

C3

C5

F1

F2 F3

F4 F5

F6

Alternative 2

Fonctions

Composants

T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

Alternative 1

T6 T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

Alternative 2

T6

Processus

Acteurs

Processus

Acteurs

A1

A2

A4

A3

A5

development system

ActorsC1

C2

C4

C3

C5

F1

F2 F3

F4 F5

F6

system-product

Functions

Components

couplingmapping

Physical view

Functional view

(1)

(2)

DSM an

d DMM


Context

Issues

Focus

Further work

Related contributions� T3: coupling between different domains

(3) JP. Micaëlli, E. Bonjour, "Are Skill Design Structure Matrices

New Tools for Automotive Design Managers?", In "Trends and

Developments in Automotive Engineering", INTECH, 10p., to

appear in 2011.

(4) O. Hlaoittinun, E. Bonjour, M. Dulmet, "Managing the

competencies of team members in design projects through

multi-period task assignment", In IFIP AICT 336, Springer, pp.

338-345, 2010.

T1

T2 T3

T4 T5

T7

development system

T6

Processes

A1

A2

A4

A3

A5

Actors

(3)

(4)

how to structure design skill networks

DMM

�Ski

ll DSM task assignment


Context

Issues

Focus

Further work

Related contributions

� T3: coupling between different domains

(5) E. Bonjour, JP Micaëlli, " Design Core Competence

Diagnosis: A Case from the Automotive Industry ", IEEE

Transactions on Engineering Management , Vol. 57, N°

2, pp. 323 – 337, May 2010

F1

F2 F3

F4 F5

F6

C1

C2

C4

C3

C5

Alternative 1

Fonctions

Composants

C1

C2

C4

C3

C5

F1

F2 F3

F4 F5

F6

Alternative 2

Fonctions

Composants

T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

Alternative 1

T6 T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

Alternative 2

T6

Processus

Acteurs

Processus

Acteurs

T1

T2 T3

T4 T5

T7

A1

A2

A4

A3

A5

development system

T6

Processes

ActorsC1

C2

C4

C3

C5

F1

F2 F3

F4 F5

F6

system-product

Functions

Components

couplingmapping

Physical view

Functional view

Design core competence: structure and evaluation


Context

Issues

Focus

Further work

Outline







Context

Issues

Focus

Further work

A method to propagate product architecture

decisions onto the project organization

� Purpose:

� help system architects to predict potential interactions

between designers that are likely to ensure efficient

system integration since they are identified by

propagating architecture decisions.

� build teams and minimize the coordination efforts (few

interactions between teams).

� Modeling choice:

� Matrix-based models to represent the mapping

between two domains (DMM) and the coupling within a

domain (DSM)


Context

Issues

Focus

Further work

Structure

� capture the Component DSM (C DSM) (coupling between Ci et Cj)

� document the Components vs Organization DMM (C-O DMM)

(Designer Du 's contribution to the design of the component Ci or Cj).

� propagate the product architecture choices through the C-O DMM in

order to generate the Organization DSM (O DSM) � definition of

propagation rules

� identify satisfactory organization structure by applying a clustering

algorithm, interpret the result and if necessary, iterate …

C1 … C i … C j … C n10

1010

1010

1010

Given: C DSM

C1

…C

i…C j

…C

n

X

X

X

D 1 … D u … D v … D mC1

…C…C j

…C n

i

Given: C-O DMM

D1 … D u … D v … D mD1

…D…Dv…Dm

Propagate:O DSM

u ?

Du DvC i C j

?


Context

Issues

Focus

Further work

Axioms

� If Ci and Cj interact, and if (Ci, Du) are linked and (Cj, Dv)

are linked

� The intensity of the coupling between Du and Dv is related

to both the coupling value between (Ci, Cj) and the

mapping values: DMM(Ci, Du) and DMM(Cj, Dv).

� each C is coupled to itself with an intensity of maximum

value, 10.C1 … C i … C j … C n10

1010

1010

1010

Given: C DSM

C1

…C

i…C j

…C

n

X

X

X

D 1 … D u … D v … D mC1

…C…C j

…C n

i

Given: C-O DMM

D1 … D u … D v … D mD1

…D…Dv…Dm

Propagate:O DSM

u ?

� Du and Dv interact.


Context

Issues

Focus

Further work

Input variables: Ci-Cj ; Ci-Du ; Cj-Dv Output variables Du-DvFuzzy rules1. if (Ci-Cj is LOW) and (Ci-Du is not NULL) and (Cj-Dv is not NULL) the n (Du-Dv is WEAK) (1) 2. if (Ci-Cj is MEDI UM) and (Ci-Du is LOW) and (Cj-Dv is not NULL) the n (Du-Dv is WEAK) (1) 3. if (Ci-Cj is MEDI UM) and (Ci-Du is not NULL) and (Cj-Dv is LOW ) then (Du -Dv is WEAK) (1) 4. if (Ci-Cj is MEDI UM) and (Ci-Du is MEDI UM) and (Cj-Dv is MEDI UM) the n (Du-Dv is AVERAGE) (1) 5. if (Ci-Cj is MEDI UM) and (Ci-Du is HIGH) and (Cj-Dv is MEDIUM) then (Du-Dv is STRONG ) (1) 6. if (Ci-Cj is MEDI UM) and (Ci-Du is MEDI UM) and (Cj-Dv is HIGH) then (Du-Dv is STRONG) (1) 7. if (Ci-Cj is MEDI UM) and (Ci-Du is HIGH) and (Cj-Dv is HIGH) then (Du-Dv is STRONG) (1) 8. if (Ci-Cj is HIGH) and (Ci-Du is LOW) and (Cj-Dv is LOW) then (Du-Dv is WEAK) (1) 9. if (Ci-Cj is HIGH) and (Ci-Du is LOW) and (Cj-Dv is MEDIUM) the n (Du-Dv is AVERAGE) (1) 10. if (Ci-Cj is HIGH) and (Ci-Du is MEDIUM) and (Cj-Dv is LOW) then (Du-Dv is AVERAGE) (1) 11. if (Ci-Cj is HIGH) and (Ci-Du is MEDIUM) and (Cj-Dv is MEDIUM) then (Du-Dv is STRONG) (1) 12. if (Ci-Cj is HIGH) and (Ci-Du is HIGH ) and (Cj-Dv is HIGH) then (Du-Dv is STRONG ) (1) 13. if (Ci-Du is NULL) the n (Du-Dv is NULL) (1) 14. if (Cj-Dv is NULL) the n (Du-Dv is NULL) (1) 15. if (Ci-Cj is NU LL) then (Du-Dv is NULL) (1) 16. if (Ci-Cj is HIGH) and (Ci-Du is LOW) and (Cj-Dv is HIGH) then (Du-Dv is AV ERAGE) (1)

aggregatethe Nc O DSM

and filter

for each C, generate

one O DSMwith fuzzy treatment O

DS

M

Proposed method

C-O

DM

M

2 3

C D

SM


Context

Issues

Focus

Further work

Component DSM ISC SYN ACT CLU CIC DIF IMP HBX

Internal shift control ISC (C1) 10 9 9 6 Synchronizer SYN (C2) 9 10 6

Actuator ACT (C3) 9 10 9 6 Clutch CLU (C4) 10 9 6

Clutch internal control CIC (C5) 9 9 10 6 Differential DIF (C6) 10 6 6

Internal mechanical parts IMP (C7) 6 6 6 10 6 Housing box HBX (C8) 6 6 6 6 6 10

Designers – Components C1 C2 C3 C4 C5 C6 C7 C8

Shifting function architect D1 6 6 9 3 3 Internal shift control development leader D2 9 3 3 3

Synchronizer development leader D3 3 9 3 Actuator development leader D4 3 9 6 3 Coupling function architect D5 6 6 9 3 Clutch development leader D6 9 3 3

Clutch internal development leader D7 3 9 3 Power transmission function architect D8 3 3 9 6

Differential development leader D9 9 3 Internal mechanical parts development leader D10 3 9

"Strength flow" function architect D11 6 6 3 9 Housing box development leader D12 3 3 3 6 3 9

Example concerning a robotized gearbox design project

Capture the Component DSM (C DSM) (coupling between Ci et Cj)

� after clustering, gearbox architecture

Document the Components vs Organization DMM (C-O DMM)


Context

Issues

Focus

Further work

� propagate the product architecture choices through the C-O DMM

in order to generate the Organization DSM (O DSM)

� identify satisfactory organization structure by applying a clustering

algorithm, interpret the result

Example concerning a robotized gearbox design project

0 8 9 10 11 12 4 5 6 7 1 2 3 00

8

9

10

11

12

4

5

6

7

1

2

3

0

E1ement

New DSM Matrix; 27-Jun-2008 11:44:31; Total Cost: 38389.0624

Power transmission function architect Differential development leader

Internal mechanical parts development leader architect Strength function leader

Housing box development leader Actuator development

Coupling box development Clutch development leader

Clutch internal development leader Shifting function architect

Internal shift control development leader Synchronizer development leader


Context

Issues

Focus

Further work

Synthesis

� This propagation method is based on the following

assumption: product architectures "mirror" design

organization structures (MacCormack et al., 2008; …).

� It provides a recommended organization architecture.

� It can help managers to steer their attention to

interactions that require special attention to limit the

risks of poor coordination and system integration.

Limit

� it is not possible to constrain the product architecture

by means of organizational choices

(Ex. choice of a supplier for designing a specific module)


Context

Issues

Focus

Further work

Outline







Context

Issues

Focus

Further work

A propagation method should be few sensitive to

estimation errors but sensitive to major changes of

values (i.e. architecture changes).

� test the method when the goal is to propagate

architecture changes

� study the interest for the combination of

matrix-based models and constraint satisfaction

problems to handle the bidirectional propagation


Context

Issues

Focus

Further work

Thanks for your attention.

Questions?

crecos bonjour 12-11-2010-for diffusion

Documents