Synchronizing and Sharing Revit Models with Team Members

This document outlines the process of synchronizing your latest Revit model changes with Central, publishing those updates to the cloud, and sharing them with both internal and external team members. The steps will guide you through ensuring that all changes are communicated effectively and issues are managed within the project workflow.

Step 1

Update your Revit model with your latest changes and prepare to synchronize these updates with Central. This action enables your internal team members to access the most recent model updates, paving the way for external sharing.

Step 2

Perform a quick synchronization with Central. This step does not alter your existing Revit workflow; you continue working and designing while ensuring that your changes are accessible to others.

Step 3

Allow other team members to view your updates after they sync with Central. The workflow remains unchanged, ensuring everyone has the latest version.

Step 4

To transfer your most recent updates to the cloud, initiate the publishing process. You will see notifications indicating when a publish or an update is available. Publishing involves capturing the most current snapshot from Revit.

Step 5

Define what you wish to publish by assembling sets, including 3D views, plan views, and sheets. Specify your preferred set and incorporate these into your publishing selections.

Step 6

Proceed to publish your latest work. If applicable, you can choose to publish with or without linked models. For this instance, conduct a standard publish, which will transfer your content to the cloud. You will notice the process in action.

Step 7

The current version is version four. You can see who updated it. The presence of a square node indicates that the content is published for internal team collaboration.

Step 8

Understand that square nodes represent a publish, while round nodes signify a shared package.

Step 9

Now, conclude the current task and proceed to create a package.

Step 10

Create a package to share with external team members. Include necessary models in the package, save it, and share it under the name "50% CDs."

Step 11

Check the completion status of the structural model. Confirm that it is finalized.

Step 12

As an architect, review the newly shared structural model. Examine it to visualize changes between versions one and two.

Step 13

Note that the references pertain to shared packages. Distinguish the differences within, and observe that it is version four.

Step 14

Version four indicates four publishes from Revit. Packages represent what is shared externally. Identify and track the 23 changes made.

Step 15

Analyze the data indicating two added elements, 15 modifications, and six deletions. Note any adjustments made, such as alterations to connections or beams.

Step 16

With visual insights into changes, verify alterations made within the model. Confirm these adjustments meet the necessary requirements.

Step 17

If any inaccuracies are observed within the structural model, initiate an issue. As an architect, create an issue for the structural engineer citing client feedback.

Step 18

The client requests exposure of a particular column. Assign the issue to the structural engineer and specify a due date for the following Friday, starting from today.

Step 19

Identify the root cause, such as insulation, which is essential for AI data analysis.

Step 20

Ensure that the created issue is accessible to the structural engineer for resolution.

Step 21

Using Revit, the structural engineer can review the issues through the issues plug-in. They can access client feedback directly.

Step 22

Within the Revit model, the structural engineer views the issue from cloud coordination, allowing them to address client requests for the exposed column.

Step 23

The structural engineer can proceed with necessary modifications to retain the column exposure. They can update the status to "in review" to indicate ongoing work.

Step 24

Refresh the file and observe the issue's status change to "in review," with the color changing to purple. This dynamic design review continues within the design collaboration as models are shared externally.