Create Prefab Package

Sometimes spools are only a piece of the workflow. Whether it's packaging multi-trade racks or entire electrical rooms, often multiple spools need to be packaged and assembled as one. eVolve Prefab Packages makes this process seamless by allowing the user to quickly define multiple spools to a package and create deliverables right from the model. 

Creating a Package

To create a package, click the Create Pre-Fab Package button from the Pre-Fabrication Panel

Once done, enter a starting package name. Note that Dynamic naming is also supported. 

 

Next, it's as simple as selecting the spools to include. 

Note that only assemblies are available to be included. Individual elements are not currently supported.  

Managing Packages

Once created there are a variety of ways to monitor and maintain packages within a model.

All package information is contained within shared parameters that are visible from the Revit Properties Panel. This allows for view filters, as well as Element Filters to quickly be created for finding and displaying package information.

This information is also available within the Spool Manager.

 

Warnings

This product is currently in beta. As such, there are some best practices, and limitations that must be followed for the proper experience.

  1. There can not be multiple types of the same view on a prefab sheet. (i.e. two plan views)
  2. Ensure package parameters are unchecked in any view templates used for prefab views.
    • Attached is a code snippet that can be used to accomplish this for all templates. See the video for more information.
Code Snippet
public void TurnOffPackageParams()
{
var doc = this.Document;
using (var ts = new Transaction(doc, "Prefab Parameters Off"))
{
ts.Start();
var viewTemplates = new FilteredElementCollector(doc)
.OfClass(typeof(View))
.Cast<View>()
.Where(v => v.IsTemplate);
foreach (var viewTemplate in viewTemplates)
{
var packagParmIds = new List<ElementId>();
packagParmIds.AddRange(from Parameter p in viewTemplate.Parameters
where p.Definition.Name.Contains("eV_Package")
select p.Id);
viewTemplate.SetNonControlledTemplateParameterIds(packagParmIds);
}
ts.Commit();
}
}
  1. Ensure there is not default plan view template in the project. This will override the chosen view template from the prefab sheet.
Remember to stretch schedules to match the size needed on the sheet before saving them as a view template


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)