Family Parameter Requirements
Updated 2 hours ago
by
Jason Earl
Summary
Some EVOLVE features are intended to be used with EVOLVE families, however your custom or existing families can often be modified to work with the various tools EVOLVE offers. Most EVOLVE tools will work with any and all content, if the feature is not listed here then it is safe to assume your family will work with the feature.
Feature: Legacy RFA Trapeze Hanger Geometry Automation
Requirements:
- Family Name starts with one of:
- eE_ASM_HS_Trapeze_...
- eM_ASM_HS_Trapeze_...
- eV_ASM_HS_Trapeze_...
What breaks if not met:
- Hanger rod lengths, strut lengths and additional geometry driving parameters may not be updated.
Feature: Single Hanger RFA Family Compatibility
Current Requirements:
- eVolve_Feature contains Minerallac or Single Hanger.
Legacy Requirements:
- eVolve_CategoryId equals Hangers.
- eVolve_SubCategoryId contains Minerallac or Single Hanger.
What breaks if not met:
- Single hanger families may not be recognized by the hanger placement tool for user selection.
Feature: Trapeze Hanger RFA Family Compatibility
Current Requirements:
- eVolve_Feature contains Hanger and/or Trapeze and/or Supports.
- Trapeze tier auto-detection uses a tier identifier in eVolve_Feature:
- Examples:
1_Tier,2_Tier,3_Tier,4_Tier.
- Examples:
- Multiple values can be stored in one field using semicolon delimiters.
- Example:
Hanger; Trapeze; 2_Tier.
- Example:
- eVolve_Feature must be a Type parameter.
Legacy Requirements:
- eVolve_CategoryId equals Hangers.
- eVolve_SubCategoryId contains Trapeze.
- Type Name contains tier information such as
1_Tier,2_Tier,3_Tier,4_Tier.
What breaks if not met:
- Trapeze families may not be recognized by the hanger placement tool for user selection.
- Auto-tier detection may not work in the hanger placement tool.
Feature: Auto Strap Compatibility
Requirements:
- Primary host identity can come from eVolve_CategoryId containing Strut.
- Family Name contains Nested_ST_Strut and/or Nested_Detection_Window for nested detection logic.
- Parameter 3d_Test must end with a numeric tier value (for example 1, 2, 3).
What breaks if not met:
- Auto Strap may miss valid supports.
- Auto Strap may place straps on the wrong side of struts.
Feature: Seismic Supports Compatibility
Current Requirements:
- eVolve_Seismic_Placement_Family, when used, must match the intended nested bearer family name exactly.
- eVolve_Seismic_Can_Place_On_Edge must be a valid true/false setting.
Legacy Requirements:
- Family Name contains strut and rod for fallback nested bearer/rod matching.
What breaks if not met:
- Seismic support bearer and rod point detection may fail.
- Attachment point selection may fail or use fallback behavior.
Feature: Points and Location Tools Compatibility
Requirements:
- Family Name starts with:
- eV_Point... (point families)
- eV_LBS... (location marker families)
What breaks if not met:
- Point families may not be discovered or processed.
- Location markers may not be recognized by location tools.
Feature: Sleeves Compatibility
Requirements:
- eVolve_SubCategoryId contains auto sleeve (sleeve family detection).
- eVolve_Description contains box out (box-out sleeve detection).
- eVolve_SubCategoryId contains auto sleeve - rectangle (square sleeve detection).
What breaks if not met:
- Sleeve family classification may fail.
- Box-out and shape-specific sleeve logic may fail.
