Skip to main content

The future of CAAD? Or at least my personal take on it

CAAD is not dead. But the word "Computer Aided Architectural Design" has been used for so many things, that it is hard to not have some kind of preoccupation with the meaning of it. While BIM is currently one of the most interesting approaches, it still is only a subpart of CAAD. Just like parametric design or semantic web can fit into it. But what I really wanted to share with you is a wish list for the future of CAAD.

  • Let us choose any modeling approach and mix them in the amount we want
    • Direct modeling, such as in SketchUp
    • Parametric Modeling, with support for coding and graphical creation/editing, such as in Grasshopper or (to some extent) in Revit
    • Start from measurements, e.g. pointclouds, surveyors data, geo-information, photographs...
    • 2D drafting if you want
  • Let us work on ANY design phase and on ANY scale level in the order we want
    • in short (well, I did a PhD on that): we want to be able to elaborate rough models, but at the same time to be able to look at technical details and go back to the Master plan when we want. Ensure all information is tied and synchronized on all levels.
    • proper approach to define design variants, design phases (programming-sketch-preliminary-construction-management-end-of-life), building phases (existing-demolish-new phases)
  • Everything fits into a BIM workflow
    • objects have semantical meaning
      • a wall is not a scaled Cube with a Boolean subtracted void
      • space are real design objects, not just some attribute or fill. You can model a whole design just with spaces and define enclosing physical elements later, if you want
      • don't limit is to only vertical walls and only horizontal floors. If I want freeform geometry, still ensure that I can embed semantical meaning to it
    • design intent is captured and kept, e.g. relationships between elements are embedded
    • all partners can collaborate on the project model, e.g. with BIM servers
    • No need to ever create a 2D drawing by hand anymore
    • all calculations, simulations, evaluations can be done directly from the information in the building model
  • work directly in Open formats, such as IFC
    • make a DWG or PDF only as output for people needing that
    • reference other formats as underlay/overlay - always up-to-date

Beware, I'm not saying that all of this should be part of a single application or run by a single developer. Let competition exist, give us choice but make everything fit into our workflow. E.g. let people chose a modeling system and combine it with another rendering system and tie it to another simulation system and still collaborate with others who made different choices.

Utopic? Probably. But I'm allowed to dream.

Comments

  1. Good post...CAAD has a long way to go go.. and its increasing popularity in Architectural CAD services is not going to lower down in near future.

    ReplyDelete
  2. You forgot the "computer system running inside a warp bubble" that would allow all this to work in real time too.

    ReplyDelete

Post a Comment

Popular posts from this blog

Improve usage of BIM during early design phases

When I was collecting ideas for a book chapter on BIM (that seemed to never have emerged after that), I collected 10 ideas, which I believe still reflect good recommendations to improve the usage of BIM during the early design phases. These ideas are related to BIM software, but you can apply them in any flavor, as long as you can model with Building Elements, Spaces and have control over representation. Introduction This article gives an overview of several recommendations and tips, to better apply BIM applications and BIM methodologies, in the context of the early design phases. Many of these tips are applicable in any BIM application and they are based on experience gathered from teaching, researching and using BIM software. Sometimes they could help software developers to improve the workflow of their particular BIM implementation. Tip 1 : Gradually increase the amount of information In the early design phases, the architect makes assumptions and lays out the main design in...

Getting BIM data into Unity (Part 0 - Introduction)

This post reflects on work that I carried out, elaborated during my guidance of a few Master thesis students, to better integrate BIM models into Unity. This will be a multi-part post. This makes each article a bit shorter to read, but allows more in-depth information overall. Hope you like it. Please comment with feedback and further improvements. Basic methodology Unity can import geometry from FBX and Collada (DAE) files primarily. There are a few other formats, but these are the preferred ones. When integrating CAD or BIM files into a realtime environment, you have to convert the geometry. During my Unity teaching and the writing of the book Unity for Architectural Visualization ( buy from Packt ), I’ve come up with a basic diagram explaining geometry exchange between CAD and BIM software and Unity. Throughout these posts, we’ll go more into detail. We start with ArchiCAD, but will tackle Revit in a follow-up post. Promised!

PythonOCC : Open Source interactive CAD shell (and how to run it on OSX)

What is PythonOCC? PythonOCC is an Open Source (LGPL) Python-wrapper for OpenCASCADE. So what is OpenCASCADE (OCC)? This is an advanced Open Source (custom license) modeling kernel, comparable to commercial engines, such as ACIS or Parasolid, which are used in quite some commercial CAD programs. When you want to develop CAD software, you could use OCC and write programs in C++. And why using Python? With this wrapper, you can create CAD and geometry scripts in Python, which is an interpreted Object-oriented scripting language. You can write almost "on-the-fly" and seriously reduce the implementation effort, by skipping the compiling-phase. You can even interact with a running program in the Python interpreter. Want to read more about this? The OpenCASCADE official website  (currently Linux and Windows are officially supported) The PythonOCC website/blog  (beware that the core of the actions happen in the development repositories). So far so good. Now the nasty, techn...