1. Update the coordinates in the site model (cloud)
- Open the site model from ACC (as a central model).
- Adjust:
- True North (Manage > Position > Rotate True North)
- Project Base Point / Survey Point as needed:
- Use “Specify Coordinates at Point” or manually set the coordinates at a known reference.
- Save/sync the site model to the cloud.
At this point, the site model has the correct new coordinate system, but the building/basement models still “remember” the old published coordinates.
2. Re-publish coordinates from the site model into each building/basement model
The goal is to re-run the “Publish Coordinates” step, but this time entirely in the cloud environment.
For each building model and the basement model:
- In Revit, open the site model (cloud central).
- Link the building model from ACC:
- Insert > Link Revit > From Autodesk Docs / ACC.
- Use the same link type/origin as before (usually “By Shared Coordinates” or “By Origin”; the important point is to be consistent).
- With the linked building visible and positioned correctly, use:
- Manage > Coordinates > Publish Coordinates
- Select the linked building model.
- When prompted about the named site / shared site:
- Either update the existing shared site definition that you already used for that building, or
- If you use multiple shared sites per building (for the 6 positions), be careful to pick the correct existing site name for each link.
- Sync the site model, then open/sync the linked building model so it can actually accept the updated shared coordinates.
Repeat for:
- Basement model
- Building A model
- Building B model
All of this can be done with cloud-hosted models; you don’t need to “detach and work locally” unless you have performance or permission issues.
Special case: multiple instances of the same typical building
You mentioned each building appears 6 times across the site. There are two standard patterns:
Pattern 1 – Multiple Shared Sites for one building model
- One building model (e.g. Building A.rvt) is used as a link.
- In the site model, you place that same link 6 times.
- For each linked instance, when you “Publish Coordinates,” you create/update a different Shared Site inside the building model (Site_1, Site_2, … Site_6).
In this pattern, when True North / coordinates change:
- You still open site model, re-“Publish Coordinates” to each instance of Building A.
- For each instance, choose the correct one of the 6 shared sites (so the building model’s internal “Site_1…Site_6” definitions get updated).
- Then when someone opens the Building A model directly, they can choose which Shared Site (Site_1, Site_2, etc.) to activate to match the desired position on the site.
Pattern 2 – Single Shared Site + Instancing handled only in site model
- The building model has only one shared site definition.
- Instancing (repetition) is handled purely by how the site model positions the links.
- The building model itself just knows “global coordinates” of one representative location.
In this pattern, updating coordinates is simpler:
- You only need to publish the updated coordinates to that one shared site definition in the building model.
- The six instances just fold that change in automatically, because they all reference the same shared coordinate system.
Best practice for ACC in complex sites:
Pattern 2 is generally more robust and less error-prone. Use multiple link instances in the site file, but keep a single shared coordinate definition inside the building model unless you truly need six internal sites.
