Evolve’s Content Product Manager, Lucas Espinosa, shares his expert insights on RFAs and ITMs and how Evolve is implementing increased support for piping RFAs in their latest 8.2 release.

 What are RFAs?

RFAs are Revit family files—the native building blocks of Revit models. There are two types: system RFAs and loadable RFAs. In this conversation, we're primarily referring to system RFAs like pipe and duct (e.g. straight pipe, straight duct, straight conduit).

System RFAs cannot be edited in the Family Editor, but have characteristics within the model. In order for them to work properly, they have routing preferences. These preferences define which fittings are placed automatically when modeling.

The fittings themselves are loadable families, which are editable and customizable, often built using manufacturer data. Practically, when you model a straight piece of pipe and then take a turn, Revit recognizes that an “elbow” needs to be placed and inserts the specified elbow family within the routing preferences.

The new piping fittings we have released with 8.2 are more accurate than Revit's default pipe types and fittings. Additionally, because they are native to the Revit environment, they have seamless integration with Revit design tools and metadata. These traits make them especially useful to design build firms, as these features are essential to their workflows. Finally, if there is a desire to convert them for fabrication, there is always the option to do so with RFA piping.


How are RFAs different from ITMs?

ITMs are native to Autodesk Fabrication, specifically within CADmep and ESTmep. These files are created and managed through a database within those platforms. You can't edit them through Revit. They are effectively transplants to Revit that Autodesk started supporting about ten years ago.

To change and modify ITMs, users must have experience with Fabrication software. Evolve provides a baseline fabrication parts library—our Origin database—which includes a wide range of parts and pieces.

However, because of the way ITMs are built, they are usually more lightweight and purpose built than their RFA equivalents. They are especially geared more heavily towards being able to build and fabricate from drawings. With RFAs, there's a little more work to get done for them to get that point which can often result in families being overbuilt and overcomplex if not built properly.

Why are we implementing RFAs with Evolve 8.2?

We recognized that both RFA and ITM workflows have merits:

• Familiarity and Comfort: Some teams are more accustomed to RFA workflows. 

• No Need for a Fabrication Database Manager: Managing an ITM database requires specialized expertise. For some teams, maintaining and editing their content is easier with RFAs than ITMs. 

We want to empower our customers—both current and future—by supporting both workflows, allowing them to choose the method that best fits their needs. 

However, this does not mean we are abandoning ITMs in any way. In fact, we recently released a new version of our fabrication parts database with updates to over 200 parts to bring them in-line with manufacturer specifications.

Additionally, Autodesk has made significant improvements to ITM support in Revit over the past two releases. Their commitment to bridging the gap between RFAs and ITMs reassures us that both workflows will remain viable.

As an aside to all of this, both of these workflows still rely on equipment or end of line terminals (e.g. floor drains, sinks) to produce a final set of drawings and coordinated model.

We are continuing to put out content that represents those types of elements, equipment and end of line terminals. Those types of RFAs can be used in both workflows. Whether your pipe system modeling is done with an RFA or ITM, you'll still be able to make use of those end of line endpoint RFAs.

What solution or impact will that have for our Evolve users going forward?

Most of our existing mechanical users currently use ITMs. By adding RFA support, we are providing: 

• New Options for ITM Users: Users who have considered moving away from ITMs but lacked the resources to do so can now transition more easily. For example, if a company’s ITM database manager leaves, they may struggle to maintain their ITM library. With Evolve 8.2, they won’t need to build a new RFA library from scratch—we’ll provide a baseline for them. 

• Value for Current ITM Users: The new end-of-line RFAs (e.g. equipment and terminal families) are useful for both ITM and RFA workflows. ITM users can still leverage these families in their existing workflows without making any changes. 

• Opportunities for RFA-Only Customers: For customers who hesitated to adopt Evolve due to concerns about switching to ITMs, we can now assure them: 

“You don’t have to switch to ITMs. If you prefer RFAs, we’ve got you covered.” 

By supporting both workflows, we reduce the switching costs for ITM users and eliminate barriers for RFA users—creating a more inclusive solution for the entire market. 


Lastly, is there any additional information you want users to know about this new Evolve feature?

Sure! This release is absolutely a first pass in our effort to support RFA workflows. We’ve covered many of the core services users rely on daily, but there’s more to come. With subsequent content releases in the near future, we’ll be expanding our RFA offerings with: 

• Additional piping accessories (e.g. in-line pumps, valves) 

• More pipe-focused equipment families 

• Additional piping services 

This is only the beginning. Stay tuned… we have more in the pipeline.


Watch the video: Mechanical RFA Expansion in 8.2
Content Release Notes: View Here
Learn more: Evolve Mechanical Upgrades with User Driven Features in 8.2