Formalization of an integrated system/project designframework: First models and processes

J. Abeillea,b,c , T. Coudertb É. Vareillesc ,L. Genesteb, M. Aldanondoc and T. Rouxa

a: Pulsar Innovation SARL - Toulouseb : Université de Toulouse - ENI de Tarbesc : Université de Toulouse - Mines d’Albi

CSDM - October 2010

1 / 24

Outline

1 Introduction

2 Background

3 Proposition of an integrated model

4 Proposition of a simple system creation process

5 Conclusion and further studies

2 / 24

Introduction

Outline

1 IntroductionWork situationIndustrial benchmark

2 Background

3 Proposition of an integrated model

4 Proposition of a simple system creation process

5 Conclusion and further studies

3 / 24

Introduction Work situation

The problem to solve

ATLAS project situation:

• many studies about aiding system design,• many studies about aiding project planning,• few studies interested in the interaction between these two processes.

Decisions made in one of the two processes ⇒ a strong impact onthe other.

Aims of the study:propose an integrated tool allowed to support such an integrated processand based on industrialists’ requirements and needs.

4 / 24

Introduction Industrial benchmark

Results

Companies sample:15 enterprises of the world competitiveness cluster Aerospace Valley

Results:• all the interviewed enterprises are confronted to this coupling problem,• but they do not have any specific tools to support it:

• 50% makes integrated decisions during meetings with humaninteractions,

• 22% uses procedures and standards,• 18% uses collaborative tools.

5 / 24

Introduction Industrial benchmark

Integrated coupled design/project environment

Our proposition:

• three actors: project manager, planning manager and design manager,• bijection or one-to-one mapping between system and project,• decomposition, at the same time, of the system and of the project,depending of their complexity.

SystemDesign

ProjectPlanning

DesignManager

PlanningManager

ProjectManager

6 / 24

Background

Outline

1 Introduction

2 BackgroundInteraction between design and planning processes

3 Proposition of an integrated model

4 Proposition of a simple system creation process

5 Conclusion and further studies

7 / 24

Background Interaction between design and planning processes

Axiomatic design

Four interacting domains (Eppinger 1991 and Suh 2001, Steward and Tate 2000: AD and Microsoft project):

• needs, requirements or specifications,• solutions,• tasks and activities,• resources.

(1)Needs

(2)Solutions

(3) (4) Tasks Resources

Design Process Planning Process

8 / 24

Proposition of an integrated model

Outline

1 Introduction

2 Background

3 Proposition of an integrated modelSystem design moduleProject planning moduleCoupling and monitoring module

4 Proposition of a simple system creation process

5 Conclusion and further studies

9 / 24

Proposition of an integrated model System design module

EIA632 - System and concept

System:

• associated to a system concept described by a set of variables to definethe requirements and characterize the solutions (weight, cost, . . . ),

• composed of :• the system requirements,• one or many system alternatives

System SystemAlternatives

SystemRequirements

SystemConcept

1..*11 1

1

1

0..*1

0,2..*

1 1

1

1

1

10 / 24

Proposition of an integrated model System design module

System requirements

System requirements definition:

• associated to a system concept,• composed of :

• needs: expression of the stakeholders’requirements or specificationsstemming from the upper level if it exists,

N1: the component C must be as light as possible

• requirements: translation of the needs to a set of variables (systemconcept or designers’ ones) and unary constraints.

R1: weight of C in [10, 20]grammes

11 / 24

Proposition of an integrated model System design module

System alternative

System alternative definition:

• associated to a system concept,• composed of :

• logical solution: description of the principles of functioning of thesystem and decomposition into sub-systems,

• physical solution: description of of the physical components neededthanks to pairs of variables (system concept or designer’s ones) andvalues.

S1: weight of C_carbon in [10, 12]grammes

12 / 24

Proposition of an integrated model Project planning module

EIA632 - Project and concept

Project:

• associated to a project concept described by a set of variables to definethe requirements and characterize the project (delay, costs, . . . ),

• composed of :• the requirements identification task,• one or many alternatives development tasks

ProjectAlternativesDevelopment

Task

RequirementsIdentification

Task

ProjectConcept

1..*11 1

1

1

0..*1

0,2..*

1 1

1

1

1

13 / 24

Proposition of an integrated model Project planning module

Requirements identification task

Requirements identification task definition:

• associated to a project concept,• composed of :

• recording of the stakeholders’needs and requirements ,• search of the different design alternatives.

14 / 24

Proposition of an integrated model Project planning module

Alternative Development task

Alternative development task definition:

• associated to a project concept,• carried out in two different ways:

• integrated design, if the system is simple enough,• modular design, if the system is decomposed into sub-systems.

15 / 24

Proposition of an integrated model Coupling and monitoring module

Coupling part

Coupling

System SystemAlternatives

SystemRequirements

SystemConcept

1..*11 1

1

1

0..*1

0,2..*

1 1

1

1

1

ProjectAlternativesDevelopment

Task

SystemRequirementsSearch Task

ProjectConcept

1..*11 1

1

1

0..*1

0,2..*

1 1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

16 / 24

Proposition of an integrated model Coupling and monitoring module

Monitoring part: dashboard

Variable Requirement Alternative 1 Alternative 2Weight R1: [10, 20]gr S1: [10, 12]gr S2: 18grDuration d<30 40 60

Project progress 50 40 60System project 60 80 50

17 / 24

Proposition of a simple system creation process

Outline

1 Introduction

2 Background

3 Proposition of an integrated model

4 Proposition of a simple system creation processCreation of the entitiesInvestigation of new alternativesDecomposition of solutions

5 Conclusion and further studies

18 / 24

Proposition of a simple system creation process Creation of the entities

Ex nihilo system creation

Inform appointment

Integratedplatform

Create project

Appointments

Inform appointment

Create planning

Fill in planning

Validate planningInform system

creation

Fill in system

DesignManager

PlanningManager

ProjectManager

19 / 24

Proposition of a simple system creation process Investigation of new alternatives

Addition of alternatives

Integratedplatform

Create alternative development task

Fill in task

Validate planningInform

alternative creation

Fill in alternative

DesignManager

PlanningManager

Ask for adding an alternative

Ask for adding an alternative

20 / 24

Proposition of a simple system creation process Decomposition of solutions

Splitting into sub-entities

Integratedplatform

Appointments

Fill in task

Validate planningInform sub-

system creation

Fill in sub-system

DesignManager

PlanningManager

Ask for decomposing

Ask for decomposing

Sub-DesignManager

Sub-PlanningManager

Inform appointment

Inform appointment

Create sub-planning

21 / 24

Conclusion and further studies

Outline

1 Introduction

2 Background

3 Proposition of an integrated model

4 Proposition of a simple system creation process

5 Conclusion and further studies

22 / 24

Conclusion and further studies

Summary

Synthesis:

• definition of a coupling between design process and planning processbased on state-of-art and industrialists’needs,

• proposition of an architecture able to support such a coupling :• hypothesis: bijection between system and project,• proposition of a UML class diagram,

• illustration of such a coupling on sequence diagram.

Perspectives:

• mock-up under development,• proposition of new coupling types (informational one, exploitingknowledge: past cases and experts’know-how),

• validating industrial example to be done.

23 / 24

Conclusion and further studies

Formalization of an integrated system/project designframework: First models and processes

J. Abeillea,b,c , T. Coudertb É. Vareillesc ,L. Genesteb, M. Aldanondoc and T. Rouxa

a: Pulsar Innovation SARL - Toulouseb : Université de Toulouse - ENI de Tarbesc : Université de Toulouse - Mines d’Albi

CSDM - October 2010

Acknowledgments: The authors wish like to thank their partners in the ATLAS project, theFrench National Research Agency (ANR) and the 7th Strategic Activity Domain (Architectureand Integration) of Aerospace Valley for their involvement in this project.

24 / 24