Donate Now Goal amount for this year: 2500 USD, Received: 2164 USD (87%)

Results 1 to 7 of 7

Thread: Best Practice: Create a spin-off interior project from core and shell project

  1. #1
    New Member
    Join Date
    May 12, 2016
    Posts
    3
    Current Local Time
    09:38 PM

    Best Practice: Create a spin-off interior project from core and shell project

    Hi,

    I was wondering what might be the best practice to create a spin-off project from an existing revit project.
    I am doing a core and shell (currently in the construction phase) and I have been hired for parallel planning of some limited interior fit-out. Both are separate contracts, so I would like to keep things cleanly separated.

    What is the best way to set this up?

    I could obviously copy the current file as it is now and start a new project, but then I would have to implement possible late changes to the core and shell into both projects.

    Or would you start a new file and link the existing model? But that might limit my options to make changes to the existing conditions when I am working in the interior file (new wall openings, shafts, etc.)? Also, the interior project is limited to only one floor and linking the model with all floors might make the file unnecessarily heavy?

    Or maybe there are other options that I am not thinking of?

    Any tips how you would handle this are highly appreciated.
    Thank you.

  2. #2
    Mr. Revit OpEd
    Join Date
    December 14, 2010
    Posts
    2,952
    Current Local Time
    02:38 PM
    Assuming that there is only so much a tenant can do to change the core and shell of the building, I'd be inclined to link that model into a new project. I'd build the interior model so the level is at the same elevation as the one in the shell. In other words I'd change Level 1 to be the same elevation...and the floor(s) below/above adjusted accordingly for context in sections or elevations if necessary/useful.

    Avoid modeling things in the core/shell that the tenants can change. If you can't avoid it...just be prepared to modify the core/shell model with Design Options to have a way to keep them but hide them from your interior project. That way the construction process isn't altered but there can be views set to show certain options to eliminate those things from the same area of your interior project using the By Linked Views approach.

  3. #3
    Senior Member Alex Page's Avatar
    Join Date
    December 13, 2010
    Location
    Wellington, New Zealand
    Posts
    657
    Current Local Time
    09:38 AM
    I would go for the link approach. Are you likely to be making changes to the "Shell and/or Core" if its just a interior fitout?
    Even if you do, just create a future phase in the shell/core project and demolish the wall in that phase - that way it won't affect your shell/core projects phase you are working on.
    A little bit of going and froing but should work ok.
    Regarding making the file unnecessarily heavy....if your PC can handle it I wouldn't worry about it. Generally in the past when I've been involved with interior fitouts I quite like presenting an axo showing all the floors below to give the fitout 3d location.
    If really worried about it you could workset your shell and core model by floor and only load in the relevant workset : but that will probably cause more hassle...

  4. #4
    New Member
    Join Date
    May 12, 2016
    Posts
    3
    Current Local Time
    09:38 PM
    Quote Originally Posted by Alex Page View Post
    If really worried about it you could workset your shell and core model by floor and only load in the relevant workset : but that will probably cause more hassle...
    Interesting. I haven't done much linking in the past. Can you link only one workset into a new file? That would be a neat solution to keep the file small.

  5. #5
    Senior Member Ning Zhou's Avatar
    Join Date
    July 20, 2011
    Posts
    852
    Current Local Time
    02:38 PM
    absolutely, demand loading via workset(s) is underused even for experienced users, but be careful in management side as Alex just mentioned.

  6. #6
    Mr. Revit OpEd
    Join Date
    December 14, 2010
    Posts
    2,952
    Current Local Time
    02:38 PM
    Quote Originally Posted by Lehmkuhl
    Interesting. I haven't done much linking in the past. Can you link only one workset into a new file? That would be a neat solution to keep the file small.
    Demand loading (using Specify in the Options of the Open File dialog) of a linked file using Worksets manages the whole linked file, either loaded or not. Once the link is loaded you can however use Manage Worksets (within the Manage Links dialog) to decide which of the linked file's worksets you want to open/close.

  7. #7
    New Member
    Join Date
    May 12, 2016
    Posts
    3
    Current Local Time
    09:38 PM
    Sounds like a good solution. Thanks guys!

Similar Threads

  1. Multiple sessions of revit open causes the little wheel to spin spin spin
    By sdbrownaia in forum Architecture and General Revit Questions
    Replies: 11
    Last Post: March 14th, 2019, 07:19 PM
  2. Large Revit Project set-up - Current best practice and any innovative thoughts
    By chidave in forum Structure - General Questions
    Replies: 1
    Last Post: October 24th, 2014, 10:17 AM
  3. Core + Shell to T.I. Fire Rated Walls Question
    By veuxx in forum Architecture and General Revit Questions
    Replies: 8
    Last Post: April 30th, 2014, 07:56 PM
  4. Replies: 0
    Last Post: August 9th, 2013, 09:15 AM
  5. How to Remove Working Views from your Revit Project with Python Shell
    By dp stuff in forum Third party Add-Ins, API and R&D
    Replies: 0
    Last Post: March 22nd, 2013, 05:23 PM

Tags for this Thread

Posting Permissions

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