1. Improving Design Workflow in Architectural Design Applications Presentation Doctoral Seminar 16/06/2006 Leuven (Belgium)

2. ABCD Overview A – Introduction B – Design Workflow in BIM Software C – An Integrated Design Environment for Architecture D - Implementation of Possible Improvements

3. ABCD A - Introduction 1. Problem Statement 2. Methodology 3. Framework to describe Design Process

4. ABCD 1. Problem Statement –Several commercial architectural design applications –Increasing attention to Building Information Modeling (BIM) –Clear focus on construction documentation –Less support for the design workflow, especially in the early design stages

5. ABCD 2. Methodology –MERODE method for the development of the CORE Object Model –study and teaching of current commercial CAAD applications –database of design applications –participation in online forums and workshops on CAD, BIM and Digital Design –study of data exchange formats –literature study on CAAD research and development

6. ABCD 3. Framework to describe Design Process 3.1 – Conceptual Framework 3.2 – CORE Object Model

7. ABCD 3.1. Conceptual Framework Design Phases Scale Levels Grids Transitions Evaluation Tests

8. ABCD 3.2. CORE Object Model Theoretical framework Class Structure + relationships Entity-Relationship diagrams Object-Event table Graphical Representations

9. ABCD B – Design Workflow in BIM Software 1. Autodesk Architectural Desktop 2. Autodesk Revit 3. Graphisoft ArchiCAD 4. Conclusion

10. ABCD 1. Autodesk Architectural Desktop –uses AutoCAD as CAD-engine –support for different representations –no bi-directional connection between walls and the surrounding spaces –one-way conversion of massing model into building elements –no direct support for building stories

11. ABCD 2. Autodesk Revit –standalone BIM application –allows different representations –massing tools to define ‘freeform’ building volume –mass model creates building elements –one-way update of building elements after modifications to massing model

12. ABCD 3. Graphisoft ArchiCAD –standalone BIM application –different representations –support for scale-sensitive objects –spaces (“Zones”) only partly connected to enclosing building elements

13. ABCD 4. Conclusion support of transitions is limited in current BIM software –architect/designer expects free design exploration –design phase transitions are mostly supported through representations –support for scale level transitions is often not bi-directional example of master plan adjustment

14. ABCD C – An Integrated Design Environment for Architecture 1. Introduction & Concept 2. Building Project Data Structure 3. Representation of Building Data 4. Transitions between Design Phases & Scale Levels 5. Integration of Evaluation Tests 6. Prototype Application

15. ABCD 1. Introduction & Concept storing design decisions –follow the workflow of an architect –using building semantics providing feedback during design –evaluation tests (simulations) –allow design exploration development platform for research –data structure –prototype application

16. ABCD 2. Building Project Data Structure Custom C++ data structure based on CORE Object Model Architectural Design Entities Generic Property System

17. ABCD 3. Representation of Building Data

18. ABCD 4. Transitions between Design Phases and Scale Levels Scale Level Transition –change scope of building –not-chronological –focus on different design elements Design Phase Transition –change detail of elements –chronological –focus on element composition

19. ABCD 5. Integration of Evaluation Tests Extraction Tests –geometric or rendering export –quantity calculation –simple cost estimation Data Generation Tests –using Extended Properties –integrate results in project –cost estimation on different Scale Levels

20. ABCD 6. Prototype Application −Evaluating the data structure −Integration of tests −Exploring representation options −Enabling transitions −Hybrid CAD/3D application −no commercial software application −limited resources of research group −test versions on different platforms SGI IRIX, GLUT, Win32/MFC, Qt/HOOPS

21. ABCD D – Implementation of Possible Improvements 1. Creating a grid of Reference Points 2. Add Classification Information 3. Connect Properties 4. The Resulting Effect on Transitions

22. ABCD 1. Creating a Grid of Reference Points –shared positions between CAAD Entities –moving control points adjust all connected elements –can be split up into: 2D part = XY position (grids often don’t change over floor levels) relative height reference e.g. floor levels, split floors grid adjustment influences the building block height references and point references

23. ABCD 2. Add Classification Information –use ISO 13567 Layer naming standard as attributes of building elements –avoid use of layers (which act as 1D vector of info) –apply BB/SfB classification instead (based on CI/SfB)

24. ABCD 3. Connect Properties –allow custom interdependencies between properties of building elements –could support expressions, to allow more elaborate connections –embed design intent/information into the elements e.g. alignments, equalities, constraints... Example 1 Set Height of Wall 1 = Height of Wall 2 Example 2 Set Start of Wall 1 = Point 2 of Floor 3 Example 3 Set Z-position of Floor 2 = Floorlevel 1 + Height of Wall 1 Example 4 Set # stairs on Stair 1 = roundof( (Floorlevel 2 - Floorlevel 1) / 0.175m ) etc...

25. ABCD 4. The Resulting Effect on Transitions –connect elements from different Scale Levels through grid of Reference Points –control Representations through Element Classification –store element relations through Property Connections –Design Phase transitions through adding element information and adjusting representation –Scale Level transitions through connection of respective Reference Points and generating additional elements Difficulties ? 1.Create Building Elements if required 2.Adapt modifications on all levels 3.Going back and forth during modifications Difficulties ? 1.Going from inf.flat element to element with thickness might require offset or repositioning = not as automatic design decision 2.The reverse transition does not remove information, but rather hides it

26. ABCD Conclusion General Conclusion –Current commercial design applications have limitations in the design workflow –IDEA+ suggests improvements, through enabling Design Phase & Scale Level transitions –This is illustrated with a Prototype Application Future Research –Modre focus on embedding design decisions into Project Data –Integrated aspects from Constraint Modeling and Parametric Design –Apply Prototype in Design Exercises

27. ABCD Thank you for your attention More information on: http://www.asro.kuleuven.be/idea