Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: One Revit file for Architecture, Structure and MEP - Good idea or ???

  1. #11
    Super Moderator david_peterson's Avatar
    Join Date
    2002-09
    Location
    Madison, WI
    Posts
    5,687
    Login to Give a bone
    0

    Default Re: One Revit file for Architecture, Structure and MEP - Good idea or ???

    Wow this is an old thread.
    I'm not sure what Mr. Cad is talking about either.
    You can create a Revit Template file that can handle all trades. That's not a problem. You just need to create view templates and Filters so you can control who things would be displayed on a sheet.
    This still goes back to my main point. You need to know what you're producing the model for. If you're only project scope is Coordination, then you really don't care about how things are going to be tagged or printed on a sheet. If you're only doing design intent, you may not be as worried about how well coordinated it is. Sometimes MEP folks like drawing Conduit and Pipe spaced further apart than actually needed so it shows up correctly on paper.
    These all go back to LOD (Level of Development. And this Level of Development should be the only LOD you care about. There's also Level of Detail (LOD), Level of Design (LOD) and a few others that people have spread around. All totally different things). If you're using your Revit model to produce shop drawings, your LOD needs to be much higher and the level or care taken to produce also needs to be much higher as you're trying to model it exactly how it going to be built. So it'll need to be fully coordinated. If you're only required to show design intent because the Contractor is responsible for making the design work, you're really only talking about how each system goes together and you really only need to coordinate large items to make sure that the design is feasible and should be able to fit within the space provided.
    Typically the reason you don't put all disciplines together is file size and number of people. If you were doing a large project and had 5 people for Arch, 2 people for Structural, 2 for Mech, 2 for Plumb, 2 for Elect, 2 for FP, 2 for Technology..... you're going to end up with more people in the central model than you really want. (5 or less is ideal, 10 is about the max, 15 works, but you won't be very productive.) There's almost a balanced curve where the more people you have working in the model the less efficient you become, because you'll need to have strict controls on who's modeling what, and where. You really need to compartmentalize the project.
    I've recently completed a 1.4mil Sqft project. Super large project team (almost 150 users) working about 90 models, in separate offices and firms.
    So can you put all your eggs in one basket, sure. Should you? All depends on your workflow.

  2. #12
    Active Member
    Join Date
    2015-01
    Location
    Orlando, Florida
    Posts
    61
    Login to Give a bone
    0

    Default Re: One Revit file for Architecture, Structure and MEP - Good idea or ???

    Putting everyone in one model has limits, sometimes these are Real software limits. In general, there is a difference the number of connected networks being manipulated by each discipline. MEP may model fewer observable objects than Architecture or Structure, but all of their systems are "sticky" with relativity and are constantly recalculating. Here's my cheat sheet for trying to manage A/E in Revit together (caveat - the project size affects any chosen approach):

    Combinations that work well in one Revit model:
    > Architecture + Structure*
    > Architecture + Interiors
    > Architecture + Interiors + Equipment
    > Interiors + Equipment
    > Interiors + Equipment + Electrical / Communications / Fire Alarm*

    Combinations that are okay, but not great:
    > Architecture + Structure* + Interiors + Equipment + Electrical / Communications / Fire Alarm*
    > Architecture + Structure* + Interiors + Equipment + Mechanical + Electrical / Communications / Fire Alarm*
    > Mechanical* + Plumbing / Fire Protection*

    * Disciplines that really want to be in their own Revit models and used as linked RVT files:
    > Structure
    > Plumbing (could be combined with Fire Protection)
    > Fire Protection (could be combined with Plumbing)
    > Mechanical
    > Electrical / Communications / Fire Alarm

    Additional notes about (*) disciplines and why they want to be in their own models: Electrical and Phasing workflows do not always play nicely. There are advantages to keeping Structure as a link to keep the bones of your project from being edited accidentally. MEP all want to be their own models because once you start combining too many editors all working on a bunch of connected networks, the model speed and model sizes become unwieldy. Again, project size affects all of this. And, finally, Plumbing will always be the first discipline voted off the island. Everyone's happier when Plumbing is on its own.

Page 2 of 2 FirstFirst 12

Similar Threads

  1. 2014: Is it a good idea to embed tag/label in REVIT Family?
    By Semi Educated Bum in forum Revit Architecture - Families
    Replies: 2
    Last Post: 2014-02-13, 05:12 PM
  2. I need a good tutorial in Revit Structure
    By ahmed.galal480843 in forum Revit Structure - General
    Replies: 1
    Last Post: 2012-07-18, 12:02 AM
  3. What's a good Revit Structure book?
    By ebordenave in forum Revit Structure - General
    Replies: 1
    Last Post: 2012-02-11, 08:37 AM
  4. structure file can not show right in the architecture section
    By yanyan77 in forum Revit Architecture - General
    Replies: 0
    Last Post: 2010-11-17, 01:35 AM
  5. Opinions on Revit .... moving from AutoCAD 2004 - revit a good idea?
    By cgill in forum Revit Architecture - General
    Replies: 9
    Last Post: 2004-12-16, 09:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •