So, you placed three copies of the same Revit link architecture file on the site? Instead, create three different architecture link files, as they are different buildings with distinct coordinates.
A resposta te ajudou? Não esqueça de curtir e aceitar como solução!
Vitor Bortoncello | Arquiteto | Especialista BIM
Autodesk Certified Professional
My 2 pennies...
The description of what you'd like to accomplish, using one design model with multiple locations, using shared coordinates is at odds with how it works with files of multiple disciplines. It works fine as described in replies for one discipline model.
Revit permits us to iterate through the possible orientations it will be used on site while editing the design model itself. In the discipline design model we can work in only one site location set "current" at a time. If you had four locations like shown in one of the replies you can make any one of those four locations "current" but you can't show all of them in a view at the same time, within the design model.
This means to do realistic documentation for a specific location we probably need to do that in the site model so the actual site conditions are possible to document with multiple views. That can't be done in the individual design file(s) unless you set a location current and print/export..repeat x times, which you'll see in a moment isn't practical.
The discipline files can be linked into each other and the saved named locations can be asserted but they don't respond to each other's Site Location setting. If I work in the Arch model and set Location 2 current. The Mechanical model will be shifted out of position and it will be necessary to change its Site Settings to be Location 2 in order to move it back into alignment. Anyone familiar with the behavior of hosted elements (faced based) will recoil at the idea that their hosted elements may now be orphaned.
I would link both Arch and Mech models in once and place them together at their first location. Then I'd use Publish Coordinates on both of them and rename their Named Location (Location 01 or A for example). Then I'd copy both models together to their second location and use Publish Coordinates again, duplicate/rename the second location and repeat until done. The arch and mech models are now located on site where I've decided they should go. Keeping in mind I can also adjust the elevation by moving them up/down in an elevation or section view and that will also be published to their named locations.
In the Arch model I'd link the Mech model in using Auto - Internal Origin to Origin, since that orientation should be suitable for working through the design and not really affected by site conditions. IF I need to show a different orientation (location) in the architecture model then I can use Site Settings to set one of the Named Locations current. After doing so for the arch model I have to do the same for the mech linked model. As I wrote before, this runs the risk of creating orphans of any hosted content in the models.
The site model can be linked into the individual discipline models using By Shared Coordinates (Default Site) since the site is the site and it doesn't vary, the buildings vary in location on the site and that's what is saved/defined in each named location in them. The site will rotate automatically when the Named Location is changed in the active file but the linked Mechanical model won't because it's location has to be changed manually via its properties Site Settings.
The notion of linking the mechanical file back into the site model via shared coordinates is irrelevant since they were placed in the correct location during the earlier process. We can select each copy of the link and use Site Settings to assign their named location but that isn't really necessary for the site model to work.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
My assumption: I want to create one Arch model to do design work in and then place it in multiple locations on site so we can work out the overall site development. A Mech model is required for this one building design. That means we only need to link Arch model to the Mech model using Internal Origin to Internal Origin since the building model doesn't "know" it is being used in multiple locations on site, nor does it "care".
While working in the Mech model I don't need to see the other orientations of the Arch model because that is only relevant when viewed on Site within one of the copies of the Arch model. I understand there are Mech design elements that are outside the building (condensers/HVAC units) that might need to be visible in the site model so we need a way to place them with the buildings on site.
I don't understand why I would need to see the other locations while working in the Mech model. If I did need to see the SITE elements surrounding my Arch or Mech design then I'd link the Site model into each discipline model. In that situation I'd want to be able to link it by shared coordinates. Then I'd be able to change the Named Location in the Arch or Mech models to see how the SITE changes around my single design, since that's what really changes not the building or my Mech design.
If what I wrote above is consistent with your end goals then what I wrote earlier is appropriate for setting out the project file relationships. A site model with a single A and M model placed at location one, publish to both models, copy models to location 2 and publish, repeat until all locations are defined. Then in the A model or M model you can link the Site model by shared coordinates and use any named location to see how the site changes around your design. In this context the A/M models don't change the site does.
Keep in mind that if your project is hosted by BIM360/ACC then Publish Coordinates is "off the table", not possible. It is necessary to use Acquire Coordinates only. In that circumstance I define all locations in the site model (with a building location marker family) and link the site model to each discipline model and place it in alignment with location 1 and Acquire Coordinates. All the other locations can be cycled through for evaluation in the discipline models too.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
.png){kind=link}
