Looking into Scott Marble's Introduction, he states that traditionally, the architect was the author, the sole creator of a design. The tools that were used then had only one purpose of facilitating the need for the designer in terms of accurately drawing by hand. But Scott Marble's experience with experimenting with the popular CNC machine as seen all over architecture schools at the time (which was the 90s) has led to redefining the relationship of architecture from design to production.
Here, we can see that to change from hand drawing to CAD, took 12 years to fully adjust to that form of design to production. However, the time it took for CAD to change to BIM as the new industry standard was 6 years. So you can see how not only is it more streamlined, but more efficient as a design to production process.
In David Benjamin's reading "Beyond Efficiency", he has created a graph through his own proven research into showing the shifts of using BIM and the amount of productivity that resulted. The dotted line labelled 4, shows the least amount of effort over the course of a project once BIM was implemented.
To clarify, Scott Marble has emphasised three specific workflows that are developed around three largely independent themes, and they are:
- Designing Design: which reflects on the procedural issues as well as the logic that is placed between creative thinking and calculated output in order to simulate, analyse and optimize processes producing integrated, parametric Building Information Models.
- Designing Assembly: focuses on the material as architects have direct links to tools and techniques, they have the role of extending beyond the representational towards the instructional process with material properties influencing their design concepts.
and finally,
- Designing Industry: which addresses the multiple disciplines and its drive towards an efficiently integrated process. Organizational models such as BIM and IPD systems become the support and culture of collaboration as the architect is seen as to either manage teams of specialists or a team of architects, engineers and contractors which have become a redefined system of design and production.
Specifically, it was the file-to-fabrication process in Scott Marble's reading that enhanced immediacy that now with the use of digital information formed new complex communication workflows. Architects, engineers, fabricators and builders now communicate digitally which has dramatically altered the way they work as well as the relationship to the tools we use. This has ultimately led to the restructuring of organisations as well as the traditional autonomous processes to integrated collective workflows.
But is this idea of combining technology and design well thought out?

Here, we can see that there are a series of programs and softwares that are interconnected by the requirement of modelling, documentation and fabrication processes in any given project. These include BIM vs CAD vs documentation softwares and rendering softwares, etc. When drawn out as a diagram, we can clearly see that it becomes an organised mess. But this should change. Fabian Scheurer gave a talk recently about the digital workflows just like these that should instead resolve this issue of adapting, and instead believes that everything should be interconnected without having to change file types to increase speed and flexibility. But instead, BIM should become a cloud-based process such as github, which may be the future that provides an easier interoperability between all disciplines in the design to production process. To further emphasise this point, instead of having multiple file types, everything in the one project would be associated with the same file format that is connected parametrically by code and is easily accessible. And for that reason, BIM is seen to be a stepping stone to that possibility.
Furthermore, to continue questioning whether the combination of technology and design is well thought out:
The Pareto Efficiency introduced in David Benjamin's reading, which is mainly associated as an economics concept, suggests that "a society where nobody can be made better off without somebody else being made worse off" is an idea where in design terms means that "An optimal design does not necessarily equal a good design." By relying so heavily on technology, architects may end up struggling to balance the power of computation with the need to maintain control throughout the exploitation or exploration of the design.
The software that architects use are defined by computer scientists which makes it quite limiting to them. But the "sheer fact of using architectural software means already to operate like an engineer". So perhaps this could change, where the architects are now understanding, even authoring some of the algorithms that influence their designs.
Which is why scripting/coding has played a significant role in architectural design. Or in other words: Designing the Design.
Processing as we all know, is an example where designers author their own software.
But is this change from traditional hierarchy to an integrated collaborative approach easy to adjust into? NO.
But why is that? Well in Dominik Holzer's Reading, “BIM’s Seven Deadly Sins”, he introduces 7 ideas that prove that BIM has its many downfalls. And they include:
- Technocentricity (which is to focus on the software instead of the design culture)
- Ambiguity (which is the quality of being open to more than one interpretation) In other words, clients aren't very familiar with the change as well as what it may provide as new costs may be added to the project from using BIM related services. So understanding the difference between 4D, 5D, 6D and 7D BIM
- Elision (which is the idea that you cannot create BIM files towards the end of a project, but rather it must be created in the early stages so that changes are made easier and less costly to accommodate)
- Hypocrisy - the IPD excuse
- Delusion - asking for 2D while requiring 3D work
- Diffidence - denying the need for process change since there are substantial costs for software licenses and training staff
and finally
- Monodisciplinarity - which means that current BIM tools still barely support early design collaboration across various disciplines.
Even though BIM is making strong progress as it is increasing its uptake in the industry, few of the downsides are rooted in misconceptions and the rest is due to the unwillingness for practitioners in design and construction to swiftly adopt the advantages of BIM due to cultural reasons. But it is only through close engagement and collaboration in practice based research is everyone more likely to succeed in managing the challenges ahead of them.
Bibliography:
Holzer, D. (2011). "BIM's Seven Deadly Sins." International Journal of Architectural Computing 9(4): 463-480.
Benjamin, D. (2012). Beyond Efficiency. Digital workflows in architecture: designing design -- designing assembly -- designing industry. S. Marble. Basel, Birkhäuser: 14-25.
Marble, S. (2012). BIM 2.0. Digital workflows in architecture: designing design -- designing assembly -- designing industry. S. Marble. Basel, Birkhäuser: 72-73.