eindhoven universityof technology the netherlands

Eindhoven University of TechnologyThe Netherlands

of TechnologyEindhoven UniversityAID ’98

3

Jos van LeeuwenEindhoven University of Technology

Harry WagterP2-Managers, The Netherlands

Robert OxmanTechnion, Israel

A Features Frameworkfor Architectural

Information

A Features Frameworkfor Architectural

Information


4

Content of the presentationContent of the presentation

• Dynamic Nature of Design

• Evolution of Information models

• Feature-Based Modelling

• Features Framework

• Conclusion & Current work:Design Systems development


5

design as problem solving design as rational decision

making design as information process design as pattern recognition

Yet another (un-)satisfactory paradigm for design thinking?Yet another (un-)satisfactory paradigm for design thinking?

design as a dynamic process

[Cross1998]


6

Design is dynamic because of:

• ill- defined problems,• creative processes in design,

Dynamic Nature of Design(1)Dynamic Nature of Design(1)

• development of designers, and• development of B&C industry.


7

Design = problem solving

concurrent activities of• generating,• manipulating,• interpreting, and• evaluating information.



8

Information is not treated asstatic data:

content and structure are constantly changing.

Information models fordesign supportmust allow

(re-)defining and(re-)structuring information


Evolution of Information ModelsEvolution of Information Models


9

Extensibilityof Information Models

Extensibilityof Information Models

The conceptual model allows for definition of new entities:

• to evolve with a designer’s style,

• for specific building projects,

• for new techniques, methods, materials, or productse.g. industrial construction systems.


10

Flexibilityof Information Models

Flexibilityof Information Models

Flexibility is also required in the instantiated models.

Flexibility is required byextensibility and modifications to the conceptual model.

BricksBricks

WoodWood

Segment2Segment2

BricksBricks

BricksBricks

BricksBricks

Segment1Segment1

BricksBricksBricksBricksWallWall


11

Content of the presentationContent of the presentation

• Dynamic Nature of Design

• Evolution of Information models

• Feature-Based Modelling

• Features Frameworkfor Architecture

• Conclusion & Current work:Design Systems development


12

Feature-Based Modelling (1)Feature-Based Modelling (1)

Developed in mechanical engineering:• group technology codes,

manufacturing process plans, numerical control programming, …

• high level entities of information with a semantic meaning for engineering.


13


Main purpose is to describe the shape of product-parts in Form Features,but classifications also include:• Precision Features,• Material Features,• Assembly Features,• Pattern Features, ...


14

Form Features

Examples of typical Form Featuresin mechanical engineering

ribs

depression

pattern Feature compound Feature:blind hole +through hole


15


Main purpose is to describe the shape of product-parts in Form Features,but classifications also include:• Precision Features,• Material Features,• Assembly Features,• Pattern Features, ...


16


Feature Libraries are not limited sets, but new types of Features can be defined.

The structure of Feature Models is not predefined: relationships are determined during design.


17


In Architecture, a more extensive approach is necessary, including:• physical building parts• non-physical concepts• different levels of abstraction


18

A Features FrameworkA Features Framework

Information infrastructure for:

• evolution of information models along with design

• formalisation of design knowledge by definition of modelling entities

• flexible relationships within the structure of information models


20

Conceptual model of Feature Types

three layered modelthree layered modelA Features FrameworkA Features Framework

Meta Layer:classes of Feature Types &

classes of Feature Instances

Feature Model, describing a particular design in Feature Instances

Generic Feature Types

defines format of

Specific Feature Types

specialisation

instantiated into

instantiatedinto

Type Com ponent

Instance Com ponent

Com ponent

Space

Room

AreaRa re a

Room : Office1

Area: Area1RusableFloorArea

Wall: WallC

enclosingWall[2]

complex Room(Space) {Assoc Wall enclosedBy [0:?];Spec Function function[1:?];

}

complex Room(Space) {Assoc Wall enclosedBy [0:?];Spec Function function[1:?];

}


21

standardisation ofGeneric Feature Types

standardisation ofGeneric Feature Types


Form Features

Physical Features Context Features

Procedural Features

Life-Cycle Features

Morphological Features

Topological Features

Geometrical Features

Compositional Features

Material Features

Composition performance Features

Design conceptual relation Features

Interface Features

Performance dependency Features

Planning Features

Preparation Features

Integration Features

Functionality Features

Operation Features

Maintenance Features

Security Features


22

activities in FBMactivities in FBMA Features FrameworkA Features Framework

domain knowledge

design project knowledge

FeatureType

1

FeatureType

Library

2

Feature Model

4

Feature instance

3

3

3 Instantiation

1 Formalisation

2 Classification

4 Modelling


24

classes of Feature Types& classes of Feature Instancesclasses of Feature Types& classes of Feature Instances


FeatureType (abs)

D ate

Author

Descrip tion

typeDate

typeAuthor

typeDescr3,1[specialisation]

3,2 Handler FeatureType

behaviour S[0:?]

2,1TypeID

typeID

definition of the class FeatureType


25

Subclasses of FeatureTypeSim ple

FeatureType

Enum eration FeatureType

Com plex FeatureType

G eom etric FeatureType

1

BaseType

Unitunit

enumeration L[1:?] Enum eratedItem

STRING

4,1 Com ponent

7,1 Param.Geometry

has S[0:?]

superTypeSuperType 2,1 TypeID

String; Integer;

Real; Boolean

default

3,1 (1)

Constra in t FeatureType

HandlerFeatureType

param.geom etry

Procedure

event

handler3,2 (1)

8,1 ConstraintSolver

solver

EventID

5,2 S impleDomaindomain

6,2 S im pleDefault

6,3 EnumD efault

typeID

5,4 ComplexDomain

5,3 EnumDomaindomain

baseType

6,4 Com plexD efault

domain

default

default

subclasses of the class

FeatureType


26

relationshipsrelationshipsA Features FrameworkA Features Framework

• specialisation

• decomposition

• association

• specification

can be defined at the conceptual level only

may be defined at both conceptual and instance level

All relationships are referencesfor reasons of flexibility.


27

relationshipsrelationshipsA Features FrameworkA Features Framework

Example of ‘shared’ Features.

Space:R oom 21

Space:R oom 22

Space:R oom 23

Function:"O ffice"S

Function:"Assem bly Rm "S

function

function

function

Tem perature:19R

dayTemp

dayTemp

dayTemp


28

instance level relationshipsinstance level relationshipsA Features FrameworkA Features Framework

Escape Routepasses through

fire res.Fire Resist.Fire Door

Escape Route

passes trough

Fire Resist.

fire res.

Door

Hinge Colour

hinges S[0:?]

FireResist.:Res30

fi re re s .

Door:door12

Hinge:h inge12t

Hinge:hinge12b

Colour:green

hinges[1]

hinges[2]

colour


29

Issues being / to be addressedIssues being / to be addressed

approaches to support knowledge formalisation: recognition searching matching

consistency management various ways of reasoning

(e.g. decision support, evaluation, inference) version management and mapping constraint testing & solving ownership & responsibility data exchange standardisation


30

Design & Decision Support Systemsin Architecture & Urban PlanningDesign & Decision Support Systemsin Architecture & Urban Planning

Design Systems developmentDesign Systems development

imulations

nteractive

V R

D I

S

irtual

eality

nformation

ystem

istributedesign

nformation

ystem

esign

imulations

nteractive

istributed


31


InteractiveDesign System

Design support for the total life-cycle of a building

• Consult design knowledge

• Check against standards/rules

• Simulate product behaviour

• Simulate user behaviour

designer

design system

ANSYS structural analysis


32


DistributedInterdisciplinary

Design System• Design system for a

distributed environment

• Design system for a inter-disciplinary design process

• Consistent information handling

• Design management research

designer A

design system

designer B

design system

designer C

design system


33


• VR environment to register the behaviour of users

(building/urban environment)

• Evaluate behaviour and information handling

• Technical infrastructure development

• Tool development

designer A

design system

user X

design system

user Y

design system

InteractiveDistributed

InterdisciplinaryDesign System


34


design system

design system

design system

1

VR Interface for design

2

Feature-based modelling

3

Design Studio of the Future

1 Virtual Reality hardware & software

2 Information modelling techniques

3 Development and testing in education


35

VacanciesVacancies

• Chair at Design Systems group• 5 PhD Student positions in VR and

• construction technique• building physics• urban planning• geometric modelling• validation of VR methods for behaviour

measurement

http://www.ds.arch.tue.nl

eindhoven universityof technology the netherlands

Documents