CDAaD

Intoducing our Computer Driven Automated architectural Design framework. The framework itself is a Python based development, with all the heavy lifting done in the background by demon style Python engines, while using the user's existing and already paid-for software package he/she knows and loves. (such as AutoCAD, ArchiCAD, Excel, Revit)

The point of the framework development is to only "outsource" functions to the new software, which cannot economically be solved by the existing proprietary software, while giving us, developers the freedom to:

• be as flexible as necessary
• also use the already existing features of the CAD or BIM software.

This is a modular development, meaning the client can use it both:

• end-to-end: meaning, he/she enters a minimal amount of information, and receives a complete architectural documentation of his/her choice.
• one module at the time. Engines separate functions can also be called form the CAD software, serving as a traditional plug-in to the CAD software.

Example - as actually developed for my clients:

• an end-to-end use would be to enter a site, and ask for a complete geodome structure, with BoQ, BoM, drawings, details of nodes
• modular use allows a designer to simply use a "Truss" plug-in, to generate a single Pole in 3D according to basic statics data

In principle, the CAD or BIM software serves as UI to the backend development. The proprietary resource receives user inputs, passes it to the Engine and interprets/ processes the answer once returned from/by the Engine. In case of BIM developments, the BIM database serves as the only source of truth thereby avoiding discrepancies arising from possibly ambiguous data.