INSTRUCTION LECTURE 5

EVALUATING AND IMPLEMENTING AND TESTING PRODUCT MODELS

Today
Exam details Feedback on projects Feedback on questions Final contest Appendix
Sheets to be studied for the exam.

1/24/2012

Lecture 1: Introducion to design complexity

Exam details
Date: 03-02-2012 Time: 8:45-10:30 Place: Sportcentrum Studie Materiaal:
Paper: Lecture 2
Paper 1_Context: Read whole paper Paper 5_MID_1: Read Section 1 and Section 5.

Sheets:

G T

Instruction Lecture 1
Paper 3_FBS: Read whole paper. Paper 5_MID_1: Read Section 2

Instruction Lecture 2
Paper 4_DPU: Read whole paper

Instruction Lecture 3
Paper 5_MID_1: Read whole paper Paper 5_MID_2: Read whole paper

EXAM RULES

Exam: Language: Questions in English

Answers in Dutch
Type of questions: Multiple choice 50% Make one DPU 25% Make one FBS 25%

Lecture 1: Introducion to design complexity

1/24/2012

EVALUATION RULES 1

Practica (P): 50% P: 0 ~10 No minimum Theory exam (E): 50% E: 0 ~10

Approve

if G >= 5.5

No minimum
Total grade (G): G = P x 0,5 + E * 0,5

Lecture 1: Introducion to design complexity

1/24/2012

DYSLEXIE RULES UT-IO

You have ever given this information to BOZ I have send this information also BOZ BOZ will let you know about the details, but in summary is: You get 1 extra hour You will make the exam in another room

Lecture 1: Introducion to design complexity

1/24/2012

EVALUATION RULES 2

If you reprove: - You will be given a project - You will have 2 chances, each one of maximum 1 hour, for making me questions - Prior to coming up with questions, you will make an appointment - The deadline will be April the 5th

- If you inscribe for making this project, and you do not deliver your report before the deadline, you will get 0 points, and I will send this grade to BOZ. So, if you inscribe yourself for making the project, you will have to be compromised in doing it. - It is better not to inscribe for the project if you are not sure you will do it.
Lecture 1: Introducion to design complexity 1/24/2012 7

Feedback FBS
All functional decompositions are OK Topology models:
C-relations are only inside one abstraction level.

MOD:
Disciplines have to be incluided It is about the behaviors, not functions or states

FBS:
All good

Analysis:
Declare why you took certain desitions Show intrenersting results: which are the most important issues in your model, did you dixcover important interrelations? Which are the most importan performances/state
1/24/2012 Lecture 1: Introducion to design complexity 8

Feedback DPU
Generally well done Sometimes difficult to read (too many lines) Confusion with differences between scenario and embodiment Analysis method that miss

Projects
Bachelor project on IPad tools:
DPU FBS QFD

1/24/2012

Lecture 1: Introducion to design complexity

10

Feedback MID
In general, well done
Biggest issue:
DPU are not specified: Embodiments, scenario, performance? Not always clear why is that your design strategy.

HAIRDRIER

How complex do you think it is? Can you model it? Can you design one? Which knowledge is involved?

Lecture 1: Introducion to design complexity

1/24/2012

12

Can you model it?

Gather with your group Determine
How does it work? Which are the most important design parameters?

Set you results in the poster

Put your names on the poster This poster is not graded

Appendix
Sheets to be studied for the exam

Lecture 2
Complexity and emergence

1/24/2012

Lecture 1: Introducion to design complexity

15

Behavior emergence sequence

Object with properties Piece of metal

Behavior ruling mechanism

External stimuli

fire

Heat transfer

Change in state properties

Change in temperature

Behavior emergence formula

Object with properties Piece of metal

External stimuli

Behavior ruling mechanism

fire

Het transfer

Change in state properties

Change in temperature

Observations
There a couple of things that are constant to all systems: - Interaction: - there are physical properties - There are external (state, energy related) properties - There are reaction properties (what we perceive as behavior) - There is a inherent mechanism
- A law, or basic principles, which explains the behavior

Conclusions

In order to determine the inherent mechanism, we need to known the ruling principles (determined by the laws of nature) In case of combined effects, we need to understand how the ruling principles are coupled together

Complexity: the concept

Complexity is a property of a system that describes how all the systems properties are connected and interrelated Therefore, complexity can be high or low, but there is always the presence of complexity The more properties that are involved, and the more intercalation between the emergent behaviors the more complex the system is

The concepts of interdisciplinary and multidisciplinary are related to the type of connection between emerging behaviors: are these sequential behaviors or are they parallel behaviors.

Complexity: the concept

multidisciplinary

interdisciplinary

Behavior emergence formula

Object with properties Piece of metal

External stimuli

Behavior ruling mechanism

fire

Heat Transfer

Change in state properties

Change in temperature

Complex product
Energy Energy dissipation dissipation Heat Convection Rotations Rotations Rotations Turbulent flow Heat Transfer Vibrations Vibrations

Heat Heat Conduction Conduction

Chemical Chemical reactions reactions

Laminar flow
Deformantions Deformantions Translations Translations Translations Translations

Complex product
Properties

Behavior

Interfaces

Some conclusions
Complexity
is a property its more than the sum of its parts

Understanding complexity is
Uncovering connection Understanding the meaning of the WHOLE

Managing complexity is
Dealing with all the connections Knowing how to proceed next

Gear belt

Spring

X-Ray material detector

Baggage Handling system

Conclusions
Product complexity is a property of a product This property describes the network of behaviors that rise up the ultimate desired and designed emergent behavior of the product

The big issues here are:

How to uncover the interrelations? How formalize the model? How to deal with the model?

Knowing how to do it is managing PRODUCT COMPLEXITY

AXIOMATIC DESIGN THEORY

Founding axioms: 1. Maintain the independence of the Functional Requirements (FRs) 2. Minimize the information of the Design Parameters (DPs).

24-Jan-12

32

COMPLEXITY IN ADT
Time independent Real Imaginary

1 1 2 = 2 , 1 2 = 1 2 = 1 2 = 1 2 1 2 1 2

This course

This course

Time dependent Real

Not in this course

Imaginary

Not in this course

24-Jan-12 33

Complexity Management
Understanding how relations emerge in product design Create appropriate models that describe an artifacts Correct manipulation of models while designing

THE APPROACH OF THIS COURSE

Use FBS Performances Scenarios Behaviors Modeling principles Topology model

Is used to start organizing the model Is qualitative Allows reasoning order Identifies performances and behaviors

Use DPU to get: Analysis relations Embodiment parameters Scenario parameters Use MID to get: Consistent models Structured models Optimization strategies Design process order

Is used to make parameterized model Is declarative (symbols and equations, no values) Identified quantitative model

Is used to verify model problems Is quantitave Ends design process strategy

Lecture 3
Function Behavior Structure

Theory
1. Section 1: Context and History
2. Section 2: Definitions 3. Section 3: FBS relationships 4. Section 4: Design problem classifications

CONTEXT

The need for a Design Science After second world war Bruce Archer starts in the 60s First conference in 62

Types of methods First, prescriptive methods

No theory explaining rationales of processes

Tell you what to do (e.g. Pahl&Beitz) Later, descriptive methods Are based on cognition, physics and mathematics Based upon models that attempt to describe Design (eg. FBS)

FBS Background
It is a descriptive method Allows describing relationship between functions and design parameters It is not magic, it only held structuring your thought Use FBS to get insights. Modeling in details an artifact using this technique results in a huge model.

FBS Model
Design artifact have 3 representational dimensions Functions, behaviors and structure

These dimensions are interrelated by 2 relational dimensions: States and principles

Structure
Entities and relations among entities connected in a meaningful way. Entities are perceived in the form of their attributes when the system is in operation. Components of artifact Examples:
Dimentions, materials, geometry, topology, positions, color, taste, etc

Topology Diagrams
Is a formalism for representing an artifacts structure Parts:
Components C-relations H-relations

Topology Diagrams

States
States:
Are quantities (numerical or categorical) of the Behavioral domain (e.g. heat transfer, fluid dynamics, psychology). States change with respect to time, implying the dynamics of the system.

State 1: V = 5 km/h State 2: V = 150 km/h

24-Jan-12 Lecture 2 44

State types
Initiators
Drive, ignite a change in the artifact

Followers
Follow from the emergent behavior Two types
Principals: Have the stronghest effect. Are the goal of design Secundary: are usually side effects, not always important, not the goal of the design

State types
States

Initiators

Followers
Principals Secondars

Principles
Principles:
Fundamental law that models quantitative relations of the States variables.

Newtons second law

Heat transfer Conduction

Principles Examples
Heat transfer
conduction, convection, radiation Flotation, Bernoulli's law, flows regimes Frequency responds, kinematics, newton's laws

Fluid Dynamics Mechanics

..

Behaviors
Definitions
Represents the response of the structure when it receives stimuli. The relation between inputs and outputs. The change of an artefact state, or the avoidance of a state transition

Behaviors are quantified by

States Structure variables

Behavior-States relations
Warm up
Translate Rotate

Temperatures
Positions Angles

Electric power supply

Generate Torque

Voltages, Current
Force, Torque

Behavior Principles relations

Warm up conduction, convection, radiation Translate Newton's laws, Carnot cycle, electromagnetism

Rotate

Kinematics, electromagnetism,

Electric power supply

Chemical discharge, electromechanics

Generate Torque

Behavior emergence formula

Structure

Initiators States

Principle Principle Principle

Principal Follower states

Secondary states

Function (Japanese)
Definition
A description of behavior abstracted through recognition of behavior for utilization.

A modeling language by which designers can compose and develop their requirements
Object representation which can connect requirements with objects After construction and deliberation function representation is used to evaluate objects to know how much their intention is satisfied

Function (Japanese)
Parts
Function body
Verb in infinite form Example: to move or carry

Noun entities
Noun in third person Example: spring, wheel, person

Function modifier
Predicate example: fast or precisely)

Function (German - American)

Definition
Transformation of material, energy, signal, information, data, knowledge or money.
IDEF 0 American Definition

Non domain dependent

Describes the transformation but not the transformation procedure

Function (German - American)

Parts
Inputs: items that trigger the activity Controls: guide or regulate the activity Mechanisms: systems, people, equipment used to perform the activity Outputs: results of performing the activity

Functions IDEF0

F-B relationship

FBS: knowledge emergence

FBS: relation among knowledge dimensions

Relationships dependencies
Examples:
Rotation can bring vibrations, which will amplify the effects of forces Temperature will expand which will change stresses Heat is created which changes the stiffness of materials

FBS Example

According to FBS completeness

Routine design
Occurs when all the necessary knowledge is available: Variables, Objectives expressed in terms of those variables Constraints expressed in terms of those variables, The ranges and variables. Routine does not imply that it is not complex; it takes experience and knowledge to come to good design solutions.

24-Jan-12

Lecture 2

63

According to FBS completeness

Innovative design
Occurs when Unexpected values become possible Values for variables are chosen outside the boundaries Introduce unwanted and unexpected behaviour. Additional behavioural knowledge is added. New technologies are added

24-Jan-12

Lecture 2

65

Piston engine Wankel engine

According to FBS completeness

Creative design
Occurs when
The process to create is free The possibility to go out of the box, to add new components or variables is open. Complete new definition of initial model occurs The solution principle is new

24-Jan-12

Lecture 2

69

According to types of behaviors

Depends on family of behaviors
physical, chemical, human, cognitive, physiology, etc

Engineering design:
Behaviors characterized by principles in laws of physics. Mechanical, electrical, chemical, geological, etc.

Human centered design:

Behaviors characterized physiologic, psychological and emotional human reactions. Architectural design and industrial design.
24-Jan-12 Lecture 2 71

Lecture 4
Design Process Units

THE DESIGN PROCESS

simple component

THE DESIGN PROCESS

Question: who decides, when?
Color of the handle? Material of the handle? Material of the container? Cavity size? Number of holes? Steel thickness? Pad size?

Its all different, but connected. And all important!

DPU: TRANSLATES
design model
model
model

behaviors
Pressure, staying time Flow distribution Ergonomics model

Aestethics
model

DPU MODELLING
Starts with a behavior to find the design process model
Parameters Calculations Level of detail

Relations to other components

THEORY
Models Descriptive: describe something Prescriptive: prescribe an activity (a method)
We have 1. Descriptive model: Design Process Unit (DPU) 2. Prescriptive method: how to make a DPU

DESCRIPTIVE MODEL: DPU

requirements Synthesis design scenario Analysis performance 1 Evaluation 3 solution 2 1. promising design 2. new design required 3. acceptable design Adjustment Example

DESCRIPTIVE MODEL: DPU

Definitions Processes
synthesis: create a design analysis: analyse a design to determine performance evaluation: evaluate a design + performance adjustment: adjust a design

Sets of information

DESCRIPTIVE MODEL: DPU

Definitions Processes Sets of information (parameters)
design: you can modify scenario: usage situation performance: the quality of a design
related to behaviours

auxiliary: dependent combinations of the above requirements: all parameters with value or ranges

DESCRIPTIVE MODEL: DPU

requirements Synthesis design scenario Analysis performance 1 Evaluation 3 solution 2 1. promising design 2. new design required 3. acceptable design Adjustment Example

WHY DO WE WANT TO KNOW

If youre new to a company/task:
Boundaries: what are the interfaces? What to do? Steps to take? Information input/output: constraints/specifications? Required level of details: what to take into account? Context: who decides what?

WHY DO WE WANT TO KNOW

To execute
know your task + context + multi-domain interaction know what to do find relevant knowledge

To manage
understand decision making processes define milestones

CONSISTENCY CHECK
Completeness (not: over or under)
all parameters relevant? no parameters misssing?

Consistency
no doubles? specific: a parameter = metric + [unit]

HOW TO MODEL A DPU

Not: fill information set Not: your own ideas But:
start with a performance ( behavior) objective analysis method guard consistency & content be specific

HOW TO MODEL A DPU

Order: 1. performance 2. analysis method 3. design/scenario 4. synthesis knowledge

HOW TO MODEL A DPU

Essential steps: 1. performance 2. analyse method 3. design/scenario
design scenario Analysis performance

HOW TO MODEL A DPU

Essential steps: 1. performance: what is important? 2. analysis: how to calculate the performance? 3. design/scenario: what information do we need?
design scenario Analysis performance

Lecture 5
Model Implementation and Design

Instruction lecture 3
Model Implementation and Design

Models
Parameteres:
Parametrics Shapes Positions Topology Fields

Relations
Algebracic, logic, differential, integral, predicate

Parameters
Variables Get values Different types:

24-Jan-12

Lecture 2

92

Parametric Design
When the design problem does not exhibit complex spatial, topologic and shape requirements All solutions adhere to a common template It is possible to simplify the problem by modeling the artifact by a set of parameters Problem solving is assigning values to parameters Examples:

24-Jan-12

Spring design Gear design Belts ?

Lecture 2 93

Topology
Thee things:
Cardinality: number of elements Connected relations (c-relations): how components are connected Has relations (H-relations): how one component has many others

24-Jan-12

Lecture 2

94

Configurational Design
Known predefined design components Known topologic relation, Problems is Assembling and configuring design elements. Examples
Gear boxes ?
24-Jan-12 Lecture 2 95

Shaping
The problem consists of attributing shape to form

24-Jan-12

Lecture 2

96

Shapes
Geometry

Graph based

Polynomials
24-Jan-12 Lecture 2 97

Examples

Spatial

24-Jan-12

Lecture 2

99

Layout design
Components known They have volumes Have to fit in certain spaces Examples:
Factory layouts Cooling systems injection molding Packaging

24-Jan-12

Lecture 2

100

Fields

24-Jan-12

Lecture 2

101

Topology Optization
Based on fields Out of scope of this course

24-Jan-12

Lecture 2

102

Topology Optimization

Class vs. Instance

Working with classes and instances
Modeling is like playing Lego You learn which are the pieces You know how to put them together You assemble pieces that match your goals

DPU Model Structure

Class
Only Parameters No value known

Instance Solution
Requirements Variables All parameters known

24-Jan-12

105

DPU Phases
Class

Instance

Instance

Solution

Solution

Solution

Solution

24-Jan-12

106

DPU Class
Embodiment Performance and scenario parameters. Models of embodiment and scenario. Analysis method What we learned last week

24-Jan-12

107

DPU Instance
Placed Requirements
Embodiment Performace Scenario

Design Relations
Objective functions Physical coherence constraints

24-Jan-12

108

DPU Instance
Objective functions
Weighted sum of performances

Physical coherence constraints

Any relation constraining the value of embodiment parameters

24-Jan-12

109

DPU Solution
All values known Performances have been calculated Evaluation has been performed

24-Jan-12

110

DPU Model Structure

Specifying your requirements Designing

Class
Only Parameters No value known

Instance Solution
Requirements Variables All parameters known

24-Jan-12

111

Complexity
Model variations
Several types of description models Several types of relations Different quantities are interrelated

Size and connectedness

Many DPUS Many parameters and relations Not clear how to proceed with the design

Dealing with Complexity

Adequacy
at FBS level

FBS based, methods

DPU consistency checks

Completness
At DPU class level

Consistency
At DPU class level

Model variations
At DPU class instance level

Parametrization Solving Applicable

Size and interconnectedness

At DPU instance level

Solving procedures
Model variations
Parametrization

Size and connectedness

Design strategy methods (DPU levels) Design strategy methods (parametric levels)