You sized members by judgment rather than analysis.
◦ What did you base your first guess on?
I based my member size on the loads I needed. Since my building is 8 floors, I knew the loads would be on the heavier side, so I chose 10x49 W-shaped steel columns.
◦ Why is it safer to guess large and shrink than to guess small and grow?
It is safer to guess larger because it ensures your loads are properly supported. Adding thick members also restricts your space, creating bigger constraints for the design. If you can design around such a major limiting factor, downscaling to make something smaller will be easier. But trying to “find” space to compensate for the lack of members is more difficult and costly.
◦ At what point in a real project does the engineer take over from the guess?
Engineers take over when the design has moved beyond schematics and transitions into a detailed design. At this stage, the model has to be informative about the real-world implementations of the build. Here, more detailed expertise is needed that is not based on guesses. In order to make a detailed model useful, it needs ot be based on knowledge of the systems being designed, which requires an engineer.
Design teams link and share models rather than working in one file.
◦ What are the advantages of linking?
Having shared links allows different people within the design team to work on their aspect of the design without causing interference with others. Since the model will eventually be linked ot the cloud, all members of the team will have the most up-to-date model for continued design development. However, while people are in the moment doing their individual pieces, it minimizes confusion to have local files that can be edited and then eventually linked to the shared cloud model.
◦ What errors does linking make possible that a single model would not?
Errors that can arise are if members of the team accidentally edit parts of the design done by other people. Since there is a link to one cloud model, that model is an accumulation of disciplines on the team. Meaning, a cloud model comes with accountability and responsibility to be intentional with edits being done, to ensure other design considerations are not being accidentally overwritten by another person’s work.
◦ Why is getting shared coordinates right at the start so much cheaper than fixing it later?
As a team goes deeper into implementing a design, decisions become more permanent as the build becomes more complex. It will be costly to have to go back to change certain aspects, from the mechanical to plumbing to electricity, when the entire build, for example, the structural plan, is off from the original building design. Such costs are also seen in person, as different teams will struggle to implement the build on the ground when the different plans coming from structural, architectural, and electrical plans do not align. In addition, time is money.
Not every clash is a problem.
◦ On what basis did you classify a clash as an issue versus not an issue?
Clashes are an issue when they can cause serious complications with the function of the building. For example, if there is a beam protruding, clashes through one of the floor openings where the elevator needs to go. This is a huge issue, as the building cannot have a beam going through the system there, for the building would not be operable. A minor clash is my structural wall penetrating my architectural wall. This will not “make or break” the build and is ok. When it comes ot more internal aspects of the system, such minor details can be worked around.
◦ Who should have authority to close a clash on a real project?
The BIM Manager, as they are the one overseeing the coordinated model. They also have the expertise to determine if such clashes will be detrimental to moving forward with the build, especially when considering pre-construction processes, deadlines, and schedules for the build.