How to make Legend from a Linked Revit Model?

[josemukalel]

We are working with a Project which has 4 Links inside the architectural  like Floors,Interior walls,External walls,Ceiling etc.We linked all files to one annotation files(Master file) to make documentation . Everything is fine ,except Leged .I was trying to make legend for doors which we placed in interior wall file and external wall files.But that door family dosent apper in leged of my annotation files(Master file) .Please give me some solution to solve this issue?

Regards

Jose Mukalel

Mask Group United 

[aghis_no · Accepted solution]

You can import all families (using transfer project standards) from the individual files to the file "combining" them. Then you can create your legends.

If you already have the legends created in the individual files and you do not want to do the job all over again, you can export the legends (from each individual files) in dwg format and then import them in specific “drafting views” in you “combining file” in order to include them in a sheet for example.

However you may have to reconsider your workflow. By separating the elements as you did (exterior walls, interior walls, floors etc.) you lose a lot of Revit’s essential functionality including bidirectional associativity between elements (wall to floors and ceilings etc.), centralized project standards, view specific geometry. Revit is a centralized one file bim solution. The workflow you use corresponds more to AutoCAD Architecture (a distributed file bim solution) where the only way to organize the task assignment and simultaneous access to the model is to separate it to specific individual files combined as xrefs to form the building.

Of course we can split the model in several files in Revit, but it is better reserve that practice to files that are “autonomous”, for example:

• A larger site plan (with no need of documentation) can be separated from the model of the building
• Several buildings of a campus can be developed in different files since you will documents each building separately
• And of course independent specialties can have independent model files linked to your building model (structural engineer model, mechanical engineer model etc.).

I do not know you exact motivation, neither the goals you want to achieve. However, if you wish to separate the model into architectural elements (floors, walls, ceilings) in order to assign tasks to different people you could use worksets and control their ownership and display. It is not late to switch, you can always select the links and "bind" them to the combining file to create one model file that will become a "central file" by enabling work-sharing.

Hope it helps

aghis

[Anonymous]

While I appreciate the 1-file approach, it is not always particularly useful. MOST projects should do fine with a single file, but sometimes you add up enough arguments against having a single file, that it becomes reality. 

Consider a larger project. I work on a hospital project with a several offices working together. The use of a master file to control and streamline drawings and document lists while each office works within a file that corresponds to their discipline is absolutely necessary. If gathered, the file would be monumental. While we can create lists and counts in individual files and retrieve and gather them in the master file, but where the disciplines intersect, documentation becomes a nightmare. Legends dont work well.

Consider a different project. A group of 7 almost identical apartment towers of 14 stories. There are hundreds of general drawings that apply to all the towers as well as hundreds of drawings that are tower specific. The levels of the towers vary so a single file would have 7x14 different levels, making naming and navigation a nightmare. In order to have useful revision control over the entire project, a master file is needed. 

Consider a different project. An old and industrial apartment complex from the 1950's is to be repaired and conserved. The linear grid of the tiles and the ability to manage phases makes Revit useful. But the intricate amount of detailing needed makes the file impossibly heavy. Project is split into several parts making a master file necessary.

Computers become stronger, its true, but we meet tougher demands on how much can be annotated versus modeled. Files grow more complex. Several companies work on the same project. Project complexes are linked with oceans of relevant information between them that you only want a single place. Saying "you do it wrong if you have more than one file - EVERY time" seems naive. Some projects are bonkers.