Our collaborative workflow started through identifying our site location on the federate model which at the beginning, to align with our supporting program “Spiritual,” we chose our site at the top of the hill, where we can explore both elevation and subtractive models.
Here is our early collaborative process workplan where we envision that our speckle streams will be broken down to above and below ground elements. We plan that our expanded components into Revit will be for each stream as shown in the diagram below.
As we progressed through the semester, we further broke down our speckle streams and elements for each component during our Design and Detailing Phase. Given the complexity of our geometries, we did our best to share models as we moved along the process.
Finally, we combined our efforts together which is shown in the final collaborative workflow diagram below. In term of process, we created an uploaded Speckle streams for each layers which are geometries components. In the background, these components got broken down into elements for each components and were linked with Revit and Rhino.Inside/Grasshopper.
Along the way, we also thought of an automation idea to optimize the workflow, the issue with our approach was all hanging on the tunnels simulation which was linked to a voxel grid of 70,000 points. That took forever to compute.
Thereafter, we explored the idea of an automated process that analyses the original state of the critical curves, as we manipulated those curves, that would analyse the number of typical tubes sections as well as quantity of soil dug. If more optimized than the initial state then a webhook bot would activate the script to compute the geometry. That would help us test the design quickly without the grasshopper compute time.
Finally, we uploaded all of our components for the final submission stream as shown below.
