Converting STEP to RFA with the right model

Hey Rhinos

We are producing Revit models from our Solidworks STEP files. We are currently producing them with a simple import to Revit and export to RFA with minimal turing steps.

The problem is our models have too much detail. We need a 300 LOD file to create that will have dimensional capability for the architects.

Here is an example of what we are currently doing.
REY1936-100.STEP (9.2 MB)
REY1936-100.rfa (1.2 MB)

Preview attachment REY1936-100.rfa

What would be the workflow to input the STEP to Rhino and export to a better file to import to Revit to then export to RFA. Or better yet, have Rhino export the RFA (a man can dream).

What does LOD 300 mean to you?

the unofficial specification is:

LOD 300 - Precise Geometry

The Model Element is graphically represented within the Model as a specific system, object or assembly in terms of quantity, size, shape, location, and orientation. Non-graphic information may also be attached to the Model Element. The project origin is defined and the element is located accurately with respect to the project origin.

Looking at your file this would take a low level Revit user a short time to draw to that level.

What would you want to Rhino to do in this case? How much detail are you looking to maintain?

How many in the catalog? If there are number of similar then Family Types might be in order.

Well, you got me on the LOD 300 thing. I am a Noob here and just relaying a term I heard from the architects we send our models to. The basic problem is that we have need to send a low level of detail that is dimensional and looks “good”.

Rhino was recommended as an intermediary to create the right model to then input/export from Revit as an RFA.

These fall under Furniture in the Family Type

I have some ideas. I’m going to email privately for more information.

The main priority for manufacturers seeking to have designers incorporate their product families into projects is ensuring these products won’t add unnecessary bloat or cause project issues.

There are a lot of considerations when building quality families.

File Size:

Various aspects of Revit Families
  • Purpose and Usage
    • Level of Detail
    • Targeted view type (Plan, Elevation, 3d, Detail,..)
  • Hosted? Workplane Based, Free Standing
  • Parametric Requirements
    • Type or Instance based
    • Dimensional Constraints / Flexibility
  • Materials, Visibility Parameters, Sub-Categories
  • Shared Parameters
  • Schedules
  • Tagging, Keynotes
  • Annotations
  • File Size
  • Coordination Requirements
    • Clearance Zones / Access
    • Clash Detection
    • Connection Points (MEP, Structural ..)
    • Tolerances
  • Company Standards
  • Product Info
    • Cost Data
    • Asset Management
  • Connections (HVAC, Electrical, Plumbing if applicable)

There is potential to automate various parts of generating.RFA files in via Rhino.Inside - Revit but there isn’t a button that will auto-generate a desirable family. This takes planning based on the considerations above in conjunction with manual processes.