PWI Software Documentation Help

Automated Stair Model Standards

Stairs are a very complicated subject. This page is intended to detail and standardize all critical user-defined parameters and features that are included in our automated stair channel models. Defining these here will help ensure consistency and eliminate potential problems as we continue to develop stairways.

Definition of Terms

There are a few terms used in this page that may be unfamiliar. Please refer to this section for clarity.

144

refers to stairs that have no mid landing.

216

refers to stairs that do have a mid landing.

Floor

refers to the ground plane or the mid landing position, based on the context of the part.

PA (Parent Assembly)

is the assembly that directly contains the part.

TA (Top Assembly)

is an assembly that is higher up in the final model tree than the parent assembly. This is often Base.iam.

General Standards

Naming Conventions

File Names

  1. Include a space between words in all file names.

  2. Parts - include the following elements in order:

    1. Side - Right / Left

    2. Part Description - Main Stringer / Mid Landing / Upper Stringer / Top Landing

    3. Profile or Part Type - Channel / Base Plate

    4. Base Plates Only: include a " - " and the channel size (8in, 10 in, etc.)

    5. Stringer Channels Only: for main and upper stringers include “ - No Landing” at the end if the top cut type is square

    6. Examples:

      • Right Upper Stringer Channel.ipt

      • Left Main Stringer Channel - No Landing.ipt

      • Right Base Plate - 8in.ipt

  3. Assemblies - include the following elements in order:

    1. Height Code - 144 / 216

    2. Side - Right / Left

    3. Description - Stringer Assembly

    4. Include “ - No Landing” at the end if there is no top landing

    5. Example: 144 Left Stringer Assembly.iam

Feature Names

  1. Include a space between words in all feature names.

  2. Include these elements in order:

    1. Specific description of use - examples are: Landing Position / Upper Miter

    2. Type of Feature - Plane / Axis / Hole / Pattern / Etc.

      • For extrusions, use the output type (Cut / Join / Intersect / Body)

    3. Examples:

      • Top Landing Plane

      • Upper Miter Cut

  3. Do not include naming elements that describe the part the feature is used in. For example, in the top landing, don’t use “Top Landing Tread Hole”. Instead, just call it “Tread Hole”, since there is only one of that feature in the part.

Parameter Names

  1. If the parameter is used in a modeling feature (not work feature), or used by a sketch.

    1. Start with the name of the feature

    2. Add a qualifier to explain what the parameter is being used for

    3. Examples: TreadHoleFromFront, LegHoleSpacing, etc.

  2. If the parameter is used for something else, be as descriptive and concise as possible so other users can understand what the use is.

    • Examples:

      • FirstPostPosition

      • StairAngleFromFloor

      • TopCutType

      • etc.

  3. If there are other parts that have similar parameters, and those parameters need to be controlled from an assembly, consider adding the “Part Description” element from the file name (see point 1.2.2 above). This may not be possible if there are multiple parts that contain the same parameter and need to be controlled by the same assembly parameter.

    • Example: TopLandingTreadHoleFromFront

Feature Tree Organization

  1. Since work features (work planes, axes, etc.) are inherently more stable, it is best to define as many as possible before you start model sketches.

  2. Always check the “Auto Resize” box.

  3. If adding a work feature hides the feature above it, uncheck the “Consume Inputs” box.

27 December 2023
iLogic Class LibrariesStringer Channels