Modular Design and the Revit Template

[dradtkeRZNRQ]

Hello All,

Would like to get some thoughts on a template methodology I am currently exploring. I work for a modular construction company and we kick out about 60 homes a year utilizing cold metal framing. That's important to know because that requires us to use a software plugin called MWF which creates the light gauge profiles and sends them to a CNC machine. This software requires that panels be exported from the same file they have been created in, therefore "container files" are out of the question. 

We have about 50 panels that we use on nearly every project; exterior walls, interior walls, floor, ceiling, soffits, etc... These generally do not change and are standardized. They just get put together differently to create 27 different modules. Would it be too much to have all of these panels and modules exist in a template file. The reason I would like to keep it in a template file rather than create a project and simply save as for each new project, is that I would like to keep developing the template file along with the panels and not have two levels of coordination. Also, it just seems cleaner. 
Some people say to keep the template files lean but they're probably working on larger scale projects. Our projects range from 1000sf to 2000sf, so I don't think the project or the template file will get too big to manage. Our goal is to create consistency and efficiency. Anyway, would love to hear your thoughts. Thanks in advance. 

@ToanDN @barthbradley @ralphdenhaan @SteveKStafford @kostask_oionei 

[SteveKStafford]

Whatever file you start projects with is a template. The technical side of a template in software with a different file format and behavior is somewhat irrelevant. It doesn't really matter which kind of file all your required parts are in as long as you and others know that your projects start with "this" file. I wouldn't get hung up on which it is. Obviously if you want worksets enabled then the template file format isn't an option. Otherwise the template file is fine to use for starting projects.

As for what's in the template, it should have everything you normally need and use. The only reason to leave things out is when those "things" are rarely used and you find that you remove them regularly. Resorting to Load Family or hunting for things elsewhere just to get things done that happen on every project is what a good template file is meant to avoid.

File size is the least of your worries in this context...unless it takes an hour for your template file to load 🙂

Trick out your template!

[barthbradley]

Define "panels" and "modules". What are they specifically? Loadable Model Families?   

...if System Families, what do you mean by "standardized"?     

[dradtkeRZNRQ]

Panels = Wall/Floor/Ceiling panels that have metal framing associated with them. Modules = 2 wall panels with a spanning floor and ceiling panel; they also include whatever that module's function might be i.e. kitchen, bedroom, bathroom. The different modules are then connected to create the home. You can check out our website Kinexx Modular to get a better idea. 

[barthbradley]

my question was what they are specifically in Revit.  In your world.  

[dradtkeRZNRQ]

They are system families of walls, floors, and floors posing as ceilings. I then use a plugin called MWF to add the framing to them. Once the framing is applied, that is how they stay. That is how we manufacture them as well; we create a bunch of panels that are placed in a holding bin and then assembled on a manufacturing line. Essentially, I'm trying to reduce the management of files and create a master file that has all of the panel types created. Then when someone wants to design/model a new project, all they have to do is start a new project with the template file and all the panels will be there for whomever to move panels into place and all the shop drawings are completed. All that will be left to do is add exterior finish drop in some dimensions and annotation and they're good to go.

[barthbradley]

Either I'm misunderstanding you or you are designing/modeling in an unconventional way. Sounds like you are saying that when someone opens this template, there are a bunch of "standardized" panels already modeled, and the "design" process is rearranging these panels.  Am I reading you right? 

[SteveKStafford]

@barthbradley FWIW, I read the OP question as one directed toward template content philosophy, not how should I create these standard panels. I read it as, "is there a problem with having all these standard panels loaded up in the template." I didn't read a questions about the how to create the panels themselves, seems to me that isn't their issue.

[barthbradley]

...maybe you mean Model Groups?  

[barthbradley]

Yeah, I get that Steve. I'm just gathering info.  😉

[dradtkeRZNRQ]

Steve is spot on. And you are correct that I am creating a template file that has a kit of parts which my fellow designers will be able to use once they start a project using the template. I was just hoping people would share their experiences with creating templates that have a robust starting point or share the pitfalls they may have encountered.

[barthbradley]

....I mean, there's a heck of a big difference between the size of a template with 50 different System Types defined in the Project Browser and one with a bunch of different "Modules" already modeled using those 50 System Family Types. Additionally, I'm wondering if those "modules" also contain MWF elements. 

...think I'm going down a rabbit hole?  Ha! Maybe I am.  Just killing time until beer-thirty arrives. 😉

[RLY_15]

Lean templating philosophy is based around two grievances:

-There are so many families/family types that you wind up using the search tool to find anything in the project to insert(or if you don't know about the search tool, you scroll on your mousewheel forever), which is annoying. This usually gets reconciled by either keeping the large libraries separate until needed, or by having a very clear naming system for families that facilitates quick searches.

-The families preloaded into the project comprise such a massive file size or have such modelling complexity that even the beginning stages of the project suffers from rendering/computational slowdown...which is annoying. Remedy is to simplify your families. In your case, since this is all based on a plugin with strict use guidelines, the most you can do is take a look at the project size and performance with every module loaded in, and make a judgment call based on the hardware capabilities of your office.

[SteveKStafford]

It is a reasonable bet that their most used panels and components will end up in their active project files. So if most of them are in the template to start with then the template has saved them some start up time. Anything they routinely ignore or end up deleting are eligible for leaving out of the template and added only when something unusual happens.

I'd expect to find a lean small template isn't effective more often than not unless a company does diverse projects and also has container model(s) that they use to add in to a base office wide template to get a project ready to start.

[ToanDN]

Just keep all of them in the template. I am not a fan of RTE because they lose worksets but if that works for you then so be it.