The Hyper-B Residential Team final assignment of Collaborative workflows seminar Cover the internal collaboration with in the team and cross team interaction that we had with other teams of Hyper-B.
Throughout the term the team worked on the development of living spaces for future residences of the tower. Residential overall role was to create Residential & Leisure Spaces Layout, Model Initial Tower Massing, and Determine Number of Residences within the building, each having a needed input and a resulted output they were part of the cross-team interactions of Hyper-B
Cross Team Interactions with Residential
As we, the Residential Team, advanced with our roles we needed information\ data from other teams and provided back updated data and new geometries to them.
Resulting in a successful collaboration across the board. But you may wonder how the residential team sent these updates across and what went on within the Internal Collaboration of the Residential Team
Internal Collaboration
Team Members \ Roles
First Lets meet the Residential team
The RESIDENTIAL team consists of three members: Khalifa, Daniel, And Pual
Internally we each have our roles that serve our goal of providing healthy living spaces through connecting residence to nature and community
But to be able to collaborate successfully internally and externally we surveyed our availability and preferred communication channels
Looking internally we found challenge within our team as we are in mix of programs : Two being in Sync while the other in Asyn, and mix of time zones: Two being in the United states on Est time zone while the other is in Kuwait on Ast Time zone 8 hours ahead of the rest of the team This resulted in a set meeting time on Tuesday and\or Friday at 5pm Est – 1am Ast Having our communications through Slack and Miro and our file Transfers through Speckle and GDrive
All of that Resulted in us working within collaboration flow that Heavily relied on speckle and Gdrive to communicate internally and externally and be able to achieve our roles with the end of each step updating the designated Speckle model and providing the required inputs to our collaborators across the team
__________________________________________________________________________________________________________________________________________________________________________
Automation of Unit Information Presentation
Through working on this project, we found ourselves limited
Manually transferring geometry, meta data, and creating renders to present became a time-consuming and repetitive process. This manual workflow hinders showcasing ability to a limited set, underutilizing any parametric project.
To us a streamlined approach is needed to automate presentation of any selected unit.
We propose a solution: Implement an automated pipeline using Speckle to synchronize geometry creation software to visualization software like Unreal Engine Then finally to a presentation platform like Google Slides, eliminating the need for manual imports, export, and upload of files and geometry.
However, we see some challenges ahead: Since Unreal Engine Speckle Connector is still in Beta with no plans to further develop it any time soon, we foresee that this may cause issues in transferring geometry and camera setup.
We expect of the application to work by selecting a desired apartment going through the automation process to come out as a full ready slide showcasing the calculated view of the apartment and its data
After having uploaded the shared data into the Residential models in speckle, we are able to pull the unit data and geometry that is structured in the same list format. Thus allowing us to match all our streams in a way that allows for automating some process of linking the data and geometry.
