BIM

BIM coordination: What is it really? Is it a matter of drawing blocks or cylinders and calling it a day? Let’s break it down. BIM stands for Building Information Modeling. When someone mentions BIM Coordination they’re referring to a 3D model that will help subcontractors make an educated guess on how to adjust their corresponding trade. Prior to BIM, subcontractors had to coordinate in the field. By doing pre-coordination it helped save time and headaches in the field.

It would be nice if it was possible to crop certain parts of the building or change the transparency of a system in the field to be able to view things but technology isn’t there yet. In this article, we will break down each phase of Coordination. Starting from the creating stage, moving to export/uploading, coordination and clash reporting, and wrapping it up with RFIs.

When a BIM coordination initially begins, all trades agree upon certain standards. For example, minimal pipe sizes, file naming conventions, upload scheduling, meeting scheduling, and project timeline. When detailers start modeling their starting point begins with the contract drawings and submittals. Once the detailers have most of their trade modeled they would export models and upload into an authoring tool (depending on the platform they’re working on).

All trades upload their corresponding models with the file naming convention discussed during the kick-off meeting. Below is an example of what the General Contractor’s BIM Coordinator normally asks for when it comes to model naming. It will vary from GC to GC.

Another thing to look at from the screenshot is the folder structure.  As soon as the coordination team uploads their BIM models into the file repository the GC’S BIM coordinator combines the files.

Once all the BIM data is implemented the coordinator saves the combined file as a federated model in Navisworks or BIM 360 Glue and start generating clash reports.

After running and reviewing the report the coordinator would then either save viewpoints from within Navisworks/BIM 360 Glue (Example 1).

Or they will mark them on the report as “Resolved” “Reviewed” or “Approved” (Example 2).

After the coordinator creates the clashing set the coordination team meets to discuss a plan of action. The team reviews all the clashes and eventually encounter an area where they will require a course of action from the Architect or Engineers. For documentation purposes, the Subcontractor will submit an RFI (Request For Information). See image below.

RFI’s are a crucial aspect of the whole coordination process because it may take the Architects and Engineers some time to come up with a solution or it could be a simple fix. The sooner the RFI is sent out the better, but also make sure to provide enough information (screenshots of a conflicting area, a room location, a very descriptive paragraph of the issue, and possibly some sections if needed). Once the RFI has been answered by the Architect or Engineer, the solution is sent out to the BIM coordination team to implement all changes and the cycle repeats until all clashes are resolved.

Let’s recap all the information we’ve gathered on BIM coordination and the process for it. First, a kick off meeting set standards and agreed upon, which will lead to the modeling process where detailers model their corresponding trades. The detailers will then upload their models into a file repository where the BIM coordinator download the models and assemble a federated model and generate a clash report. Once the BIM coordinator reviews the report the detailers meet to review clashes. If a clash cannot be resolved then an RFI must be sent out to the AE for review.  Afterward, a solution will be sent back that the detailers implement. This cycle continues until the project is fully coordinated and handed off to the Owner.

When creating this type of family you can make both a Polynesian and a Gambrel roof truss with this one model. It can be tricky to create this family, but in the end, it could save you time once this family is finished.
⦁ Open up Revit and create a new Structural Framing – Complex and Trusses
⦁ Open up the front elevation and hide the level in visual graphic (VG).
⦁ Create three vertical Reference plans on each side of the center axis.

⦁ Create two diagonal reference lines to create the slope of the top chord of the truss.
⦁ Add a dimension parameter for the bottom chord span and lock the parameter then equal space between the overhangs with a dimension.
⦁ Add a dimension parameter for the middle span and lock it, then test to see if reference planes change.
⦁ Add an angle dimension parameter to each slope and lock it.
⦁ Add a reference plan for the top of the bottom chord and add a dimension parameter for the height of the bottom chord.
⦁ Add a reference plane at the top of the truss and add a dimension parameter for the truss height.
⦁ Test to make sure things are working correctly.

⦁ Using the extrusion tool create the bottom chord span by using the pick lines and trimming to get the shape, also lock the lines to the reference planes.
⦁ Do the same thing to create the top chords for each side, also add a dimension to control the height of the top chord and make sure you lock it to the reference line.
⦁ Extrude the webs on each side by using the two vertical reference planes on each side, also add a dimension parameter for the web thickness.⦁ Use the extrude tool make middle web member the same way.⦁ Test to make sure things are working correctly.
⦁ Add reference lines for the webs to each side and lock it to the top and bottom chords. Then test for function.⦁ Use the extrusion tool to create the web of the truss in two separate pieces. Center the web around the reference line and dimension the width of the web. ⦁ Test to make sure everything works accordingly.
⦁ Open up the left elevation and create a reference plane for the thickness of the truss and align extrusions to the reference plane. Then test to make sure everything works like its suppose to.

Background

On April 9th, Autodesk released the next generation of cloud worksharing aiming to replace what we currently know as Collaboration for Revit (C4R) and rebranding it as BIM 360 Design. On the technical side, Autodesk argues their services change in order to provide a better experience on Forge based platforms, however, there are some licensing differences as well. Without getting too much into the financials, this tutorial series intends to review and show new workflows using this next generation of tools that we have inherited. This new BIM 360 Docs environment is definitely more powerful, but it will require more set up time for the permission portion until your team finds the right way to share data within your projects.

“Our ability to adapt is amazing. Our ability to change isn’t quite as spectacular. “ —Lisa Lutz

The facts presented here are based on the limited time we had for testing since the release date. Please, let me know if you find any discrepancies. Let’s start!

Introduction

The following graph represents the BIM 360 Team vs the BIM 360 Docs processes.

Notice Revit 2018.3 is the only version that works with the old and new cloud worksharing platform (C4R and BIM 360 Design). The user still has to hit the publish button in order to reflect the latest Revit model changes to BIM 360 Docs (Also, can be done from Docs). After diving into Revit 2019, there is no going back to C4R. Autodesk will continue to provide support for BIM 360 Team. However, Autodesk will do its best to convince your team to use BIM 360 Docs for your next project. With that being said, no migration tool is going to be provided to transfer projects from BIM 360 Team to BIM 360 Docs.

An exciting feature of the new platform are permissions and access levels for company hubs and project members. In addition to this, in the Design Collaboration module, Project Admins can create teams (Services > Design Collaboration) to manage cloud models, allowing another level of control while also avoiding interference with other teams. For this reason, the workflows presented on this tutorial address not only how to get started with a cloud project, but also how to properly add users using multiple methods to filter access levels while facilitating the data and communication flow.

The image below maps the services activated in a project and members’ access/roles assigned.

The Workflow on Video

Disclaimer: If you hear me saying “BIM 360 Ducks”, I mean “BIM 360 Docs” 🙂

• Create a New BIM 360 Docs Project and Activate Services (As Account Admin)

How do I create a project for the new cloud worksharing platform – BIM 360 Design?

• Add Project Members (As Project Admins)

How can I add users/members to my BIM 360 Docs Project?

• Add a project Team for Design Collaboration (As Project Admin)
  

• Collaborate the first model to BIM 360 Document Manager (As Project Admin)

How can I collaborate the first Revit Model and assign members to a Design Collaboration Team?

• Collaborate a model to BIM 360 Document Manager (Access Level: View-Edit)

A user is assigned to a Team to collaborate a model to the cloud.

• Meet the Design Collaboration Module and Create a package

• Adjusting Permission Levels and Sharing Packages

• Reusing Design Collaboration Packages

The “Reuse” command uses the document version of the package we plan to reuse.

The create “New Package” command uses the last version that has been published from Revit or Updated to Latest from Design Collaboration

• Revit: Publish Latest vs. BIM 360 Design: Update to Latest

• Consumed Packages

Decide what shared Revit files link to your Revit Model using the “Consume” command

• Shared vs Consumed Packages

• BIM 360 Docs Permissions

Notice that this workflow also works with Automatically created folders (from Design Collaboration Teams)

Also, the permission level showed below provides almost Admin level power just for that folder that is assigned to.

Big thanks to the person from Autodesk that put the document under references together and to Ignacio Rodriguez and Tony Trinh who helped me with content and video editing. Finally, shoutout to Katie Watton, who is creating more in-depth and relevant learning content about this topic for the CADLearning team.

References

BIM 360 Design – Getting Started

Facts

Most owners don’t build enough buildings to fully understand the process, what all is involved, how long it actually takes, what could go wrong, and the ‘actual’ costs.

Cost overruns are so common that contingency fees average upwards of 5%. Some of these have to do with changes however most are due to:

• Material waste
• Rework
• Poor communication between sub-trades

Therefore, there will be delays due to miscommunication between owners and architects, architects and contractors, and contractors and owners.

So what does the ideal project look like?

Crystal clear communication between all parties:

• Expectations have been defined and clearly communicated
• Everyone knows what to do and are in constant communication

The project schedule is realistic as all parties have a hand in creating it and have signed off on dates for deliverables. Also, only the necessary materials are used as waste is kept to a minimum along with a clean and organized job site.

How we get there

Owners should select their team as early as possible so that communication may begin right away. They could create a virtual mock-up of the project and make this an expectation from the beginning. Besides, a plan should be devised that includes schedules, execution, and development of objects in the virtual model.

A virtual model allows for:

• Visualization
• Identify issues (clash detection)
• Explore “what-if” scenarios much quicker
• Quantify materials
• Run through 4D simulations

Hold collaboration meetings using the models as a tool, and have a cloud-based workspace (not just repository) so:

• Everyone has access to the latest and greatest information
• Minimize upload/download time (i.e. google docs vs ftp)
• Leverage data for downstream uses:
  • Facilities management
  • Future renovation
  • IOT integration

Prefab based off of model components = higher quality, less waste, and controlled environments means less dependency on weather and more on-time completion.

Some people might have this question: Why not just make the architect or general contractors responsible for this?

Because they would not work well together. They have good intentions; however, let’s take a look at the differences:

Architects will focus on design intent. They charge by hours. They are concerned mainly with the design schedule.

Whereas, contractors will focus on buildability which is the easier, the better. They have fixed budget. They are concerned mainly with the construction schedule.

What is needed?

A third-party ‘referee’ that is impartial, that understands and has experience with all  parties:

• Construction
• Design
• Operations

Someone who can facilitate the technology that makes all the communication and collaboration (not to mention dealing with all the different file types and software) possible.

Axoscape consists of experienced architects, engineers, and construction detailers and we will help you:

• Create online workspaces that speak to your specific project and help you manage the organization, users, and permissions.
• Create a living BIM execution plan along with LOD specifications by communicating with all involved that will be the central ‘truth’ for the project.
• Perform daily/weekly coordination meetings to keep the schedule intact and hold all trades accountable.

When creating rafter tails with a beam system, it can be difficult. Also, if you need to have a custom rafter tail end, you will need to modify both ends of the beam to your desired design.

1. Select the structure tab and select the beam tool. Then load the desired structural framing family you would like to use.
   
   
   
2. Now, after selecting your desired beam, switch to the 3D view and before selecting lines to create the beam make sure the “3D Snapping” box is checked.
   
3. Use the “pick lines” select the ridge, hips, valleys, and edges of the roof.
4. Select all of the beams you just placed and isolate the beams using the “isolate element”
5. Go back to the structure tab and select the beam system tool. Make sure the 3D box id checked before selecting the beams. Then using the “pick supports” and select one section of the roof beams.
   
   
   
6. At the bottom corners, you will need to make two straight line so that the rafters are perpendicular to the roof edge. Select one as the “beam direction”
7. Do the exact same thing to the other sides of the roof to continue to have the rafter tail on all sides.
   
8. Un-isolate the roof rafters and beams, and you can see the rafters and beams through the roof. But before we deal with that create a design option called “fascia” so that you can hide the beam that is at the edge of the roof.
   
9. To hide the rafters and beams you will need to modify the roof and make sure that the roof sits on to of the rafters and beams. Make the roof 1” thick (or what the thickness of the desired roof system). And then offset the roof so that it sits on top of the rafters.