How Konstru for RAM handles imported elements

Grids:

• Only orthogonal grids are supported by RAM.
• A Konstru grid is created as a grid system with one grid defined.
• Each RAM grid in a grid system is created as a Konstru grid (curve and label).
• Every grid system is assigned to every floor layout type.

Levels:

• Each RAM story is created as a Konstru level (label and elevation).
• When downloading into RAM, Konstru examines all columns, walls, floors, beams, and braces to ensure there are Konstru levels to host those elements. It will create missing levels with the following label prefix followed by the elevation in mm:
• “KonstruCT-“: Column Top (3ft Tolerance)
• “KonstruCB-“: Column Bottom (3ft Tolerance)
• “KonstruWT-“: Wall Top (3ft Tolerance)
• “KonstruWB-“: Wall Bottom (3ft Tolerance)
• “KonstruF-“: Floor (3ft Tolerance)
• “KonstruB-“: Beam (3ft Tolerance)
• “KonstruBS-“: Brace Start (3ft Tolerance)
• “KonstruBE-“: Brace End (3ft Tolerance)
• These automatically created levels are a last resort, as they will most likely create vertical discontinuity in your RAM model. It is best to avoid these and to have a clean model with proper levels to start with.
• If the lowest level’s elevation is above zero, the level elevation is the RAM floor-to-floor height.
• If the lowest level’s elevation is zero or below, the RAM floor-to-floor height is 1.2 inches.
• As RAM does not allow zero floor-to-floor height, to get the level created, the smallest allowed value of 1.2 inches is used.
• Each Konstru level is created as a RAM floor type and story.

Beams:

• Start and end cantilever lengths are stored for intra-exchange within RAM only.
• Maximum combo reactions at start and end points are stored and supported by all platforms.
• Camber and total stud counts are stored for inter-exchange going to Revit only.
• Member end releases are stored for intra-exchange within RAM only.
• Beams are hosted to the nearest story with a 3ft tolerance.
• Off-axis in-fill beams may not be connected even though end-points are landing on supporting beams. This is due to a RAM API limitation.

Columns: 

• Maximum combo reactions at start and end points are stored and supported by all platforms.
• Member end releases are stored for exchange within RAM only.

Floors:

• Floor openings are supported.

Walls:

• Walls are always created with zero bottom offset.