Eindhoven University of Technology

2. Eindhoven University of Technology The Netherlands

3. Jos van Leeuwen Eindhoven University of Technology Harry Wagter P2-Managers, The Netherlands A Features Framework for Architectural Information • Robert Oxman • Technion, Israel

4. Content of the presentation • Dynamic Nature of Design • Evolution of Information models • Feature-Based Modelling • Features Framework • Conclusion & Current work:Design Systems development

5. Yet another (un-)satisfactory paradigm for design thinking? • design as problem solving • design as rational decision making • design as information process • design as pattern recognition [Cross1998] • design as a dynamic process

6. Dynamic Nature of Design (1) Design is dynamic because of: • ill-defined problems, • creative processes in design, • development of designers, and • development of B&C industry.

7. Dynamic Nature of Design (2) Design = problem solving concurrent activities of • generating, • manipulating, • interpreting, and • evaluating information.

8. Dynamic Nature of Design (3) 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 Models

9. Extensibility of 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. Bricks Bricks Bricks Bricks Bricks Segment1 Segment2 Wood Bricks Flexibility of Information Models Wall Flexibility is also required in the instantiated models. Flexibility is required byextensibility and modifications to the conceptual model.

11. Content 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) 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. Feature-Based Modelling (2) 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. pattern Feature compound Feature: blind hole + through hole Form Features ribs depression Examples of typical Form Featuresin mechanical engineering

15. Feature-Based Modelling (2) 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-Based Modelling (3) 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. Feature-Based Modelling (4) In Architecture, a more extensive approach is necessary, including: physical building parts • non-physical concepts • different levels of abstraction

18. A 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

19. three layered model defines format of Generic Feature Types specialisation instantiatedinto Specific Feature Types instantiated into A Features Framework Meta Layer:classes of Feature Types &classes of Feature Instances Conceptual model of Feature Types complex Room(Space) { Assoc Wall enclosedBy [0:?]; Spec Function function[1:?];} Feature Model, describing a particular design in Feature Instances

20. A Features Framework standardisation of Generic 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

21. activities in FBM 3 1 FeatureType Feature instance 3 2 4 FeatureTypeLibrary Feature Model A Features Framework domain knowledge design project knowledge 1 Formalisation 2 Classification 3 Instantiation 4 Modelling

22. classes of Feature Types& classes of Feature Instances A Features Framework definition of the class FeatureType

23. Subclasses of FeatureType subclasses of the class FeatureType

24. can be defined at the conceptual level only may be defined at both conceptual and instance level A Features Framework relationships • specialisation • decomposition • association • specification All relationships are references for reasons of flexibility.

25. A Features Framework relationships Example of ‘shared’ Features.

26. A Features Framework instance level relationships

27. Issues 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

28. Design Systems development V R D I S irtual eality esign esign istributed istributed nformation nformation nteractive nteractive ystem ystem imulations imulations Design & Decision Support Systemsin Architecture & Urban Planning Design & Decision Support Systemsin Architecture & Urban Planning

29. Design Systems development design system InteractiveDesign System designer Design support for the total life-cycle of a building • Consult design knowledge • Check against standards/rules • Simulate product behaviour • Simulate user behaviour ANSYS structural analysis

30. Design Systems development design system design system design system Distributed Interdisciplinary Design System designer A • Design system for a distributed environment • Design system for a inter-disciplinary design process • Consistent information handling • Design management research designer C designer B

31. Design Systems development Interactive Distributed Interdisciplinary Design System designer A design system • VR environment to register the behaviour of users • (building/urban environment) • Evaluate behaviour and information handling • Technical infrastructure development • Tool development design system user Y design system user X

32. Design Systems development 1 3 2 design system design system design system 1 Virtual Reality hardware & software 2 Information modelling techniques 3 Development and testing in education Design Studio of the Future Feature-based modelling VR Interface for design

33. Vacancies • 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