Link
Use Load Families & Types for content, Shared Parameters for data fields, CAD/Family tools for geometry conversion, and Join tools for intersections. Start with one type group or element pair in a project copy and inspect the result before expanding scope.
Verification limits are stated for each tool. Dialog captures establish visible controls; created or edited elements require separate checks in the model, Properties and saved RVT.
Logo, Feedback and YouTube actions are explained in the common dialog footer.
Load Familes & Types
Run Transfer processes enabled groups: Multi Tags, Wall Types, Materials, View Templates, View Family Types, Dimensions, Viewport Types, Bar Diameters, Spot Elevation, Families, Rebar Shapes, Other Families. Type/template transfer differs from loading .rfa families. Content must match the Revit version.
Enable one group on a copy, record existing names/counts, run and inspect Project Browser/Type Properties. Repeat to check duplicate-name behavior. A closed dialog does not establish success. Runtime transfer remains pending.
Spot Elevation transfers template Spot Dimension Types whose names contain BS when the project lacks the same name. It adds annotation types, not placed spot elevations. Check the type selector in Spot Elevation afterward. Families / Rebar Shapes / Other Families load their corresponding content folders; already loaded families may be skipped. Run Transfer therefore does not force replacement of all existing families or types.
Enabling any of Families / Rebar Shapes / Other Families can also load editable families from the template before processing the corresponding folders. These checkboxes do not guarantee absolute isolation of every template family. Compare the family/type inventory before and after transfer.
Create Shared Parameters
This button creates/binds BIMSpeed's standard shared parameters. It is separate from the Family Shared Parameter dialog. Source uses bundled definitions and version-specific parameter/category mappings. Some entries are Type parameters, such as BS_TYPENAME and SORTING_ORDER; do not assume every entry is text or instance-based.
On a project copy, record Manage → Project Parameters before running. After completion, verify names, GUIDs, data types, Instance/Type and category bindings. Inspect Type Properties for Type parameters and check custom prefixes. Runtime binding remains unverified; a completion message does not replace these checks.
Project scope and existing beam flags
Shared-parameter preparation may process the whole project, independently of selection. Its beam-specific stage binds definitions in BeamStructural / BeamRebar as Instance parameters for Structural Framing, including BS Secondary Beam, @BS_Beam Group, @BS_RB_Top.L1 and @BS_RB_Stirrup.Middle. Other parameters created by the generic stage may have different categories, data types and Instance/Type bindings.
Existing Yes values of BS Secondary Beam can be reset to No on all Structural Framing FamilyInstances where the parameter exists, is writable and uses Integer/Yes-No storage. Skipping an existing binding does not preserve every existing value. Selecting only a few beams does not restrict this operation.
Before running on a copy, schedule or record IDs and flags of beams currently set to Yes. Check those same IDs afterward, restore intended secondary-beam Yes flags and verify Undo. Create Shared Parameter completed does not prove that every binding succeeded: inspect Manage → Project Parameters, GUID/category, Instance/Type and actual element Properties. The flag effect is documented from the command behavior; a separate runtime readback is identified when exercised.
Diameter Setting
This is the same command as Diameter Setting in Edit Rebar. See that section for every table field and action; the GEN location is not a separate variant.
Cad To Revit
Open CAD to Revit, choose the host branch (Grid, Column, Beam, Wall, Floor, Foundation/Pile), then the relevant CAD/layer and Family/Type. Each branch requires matching geometry; column blocks, beam centre lines and closed floor boundaries are different inputs. Check CAD units and coordinates first.
Create one sample on a copy and inspect category/type, dimensions, level, offset, direction and count. Undo before expanding scope. A suitable educational CAD fixture and branch-by-branch runtime creation remain pending; a schematic preview is not model output.
Family from 2d cad
Create Family From CAD is separate from direct project modeling. Select CAD geometry/layers, Family/Type configuration and the correct family template. Verify the saved family, load it into a test project and place an instance; check dimensions/origin, category, extrusion and units. Runtime family creation/save/load remains pending.
Set family from cad
This menu entry invokes Create Family From CSV, despite its CAD wording. Use the columns required by the loaded dialog and check delimiters, units and source Family/Type. DWG is not a substitute for CSV in this flow. Test one row and inspect the created family/type before processing more. The installed CSV schema and runtime remain unverified; no untested sample CSV is offered.
Join/Unjoin
Auto-join intersecting objects for geometry and quantity processing.
Auto Join: join/unjoin, cut order and scope · Settings reference. Active View and Selection were exercised; Project was not run in the guide. This does not cover the separate Join Advance or Unjoin All commands.
Join Advance
Choose Join / Cut by Void. Join mode offers Join, Unjoin, Switch Join; void mode offers Cut / Uncut. Category/element trees define the sets. Close closes. Switch Join changes cutting order for a joined pair rather than moving hosts or changing all materials.
Test two intersecting elements on a copy. Record volumes/boundaries, inspect cutting order and Undo. Void mode requires a suitable cutting family; JoinGeometry evidence does not verify void cutting. Runtime for both modes remains pending.
Unjoin All
Current source scope is the active view, not merely the selection. It collects visible elements with a parameter named Volume, attempts to unjoin pairs and ignores invalid pairs. There is no scope dialog. The English parameter-name lookup is a locale limitation to verify in the loaded build.
Use a dedicated view and save a model copy. Record joined pairs, volumes and boundaries; run, inspect disconnected pairs and Undo. Ignored pair errors mean that silence does not prove every pair was unjoined. Runtime remains pending.