RAM Structural System Help

Overview: The Recommended Sequence of Operations

The majority of models created in the RAM Modeler follow a consistent modeling pattern. There will, however, be times when it will be beneficial to alter this modeling pattern. Once familiar with the RAM Structural System, the engineer will be able to determine the best approach to creating a model. The general approach to modeling is explained below. The Tutorial provides an example that clearly demonstrates model creation. It is highly recommended that the Tutorial be completed to provide the engineer with hands-on modeling experience.

When beginning a new project, a database is created by selecting the File - New command from the RAM Manager. The new database is automatically assigned all of the default settings that were defined in the RAM Defaults Utility (accessible from the RAM Manager’s Tools menu – see the RAM Manager manual for more information). Once the database has been created, the RAM Modeler can be invoked.

Once in the RAM Modeler, the first step is usually to create one or more grid systems. Because the grids and grid systems are the primary reference points for structural members and loading patterns, they should be entered into the model before the other elements. The Grid Systems and their associated Grid Lines are entered into the model using the Layout – Grids – Create/Edit command. Labels can be given to these major grids for easy reference. Additional grid lines and grid systems may be entered at any time during the modeling process as necessary. Additional grid systems may be entered, or existing grid systems modified or deleted at any time during the modeling process.

Next, specify a Layout Type, using the Layout – Type – Select command. Generally, the most typical Layout Type should be specified, selected and modeled first. Eventually all Layout Types will be added to the database.

Once at least one Grid System and one Layout Type are defined, the Layout – Grids – Select command is used to assign one or more grid systems to each floor type.

Columns or walls are usually the first structural members entered into the model. Most columns occur at grid line intersections and can be laid out using the Layout - Columns - Add On-Grid command. When columns occur that are not located on major grid intersections, the Layout - Columns - Add Off-Grid command can be used to model these columns (rather than manually calculating the grid dimensions and defining grid lines for such columns). The RAM Modeler will create SnapTo points at these members allowing other data to be easily placed at these points.

Walls can be added either before or after columns. Walls on major grids can be added using the Layout - Walls - Add On-Grid command. The Layout - Walls - Add Off-Grid command should be used to model walls at off-grid locations.

Tip: Although many modeling commands have options to add members "off – grid", in some cases it may be helpful to add construction grids to create new SnapTo points that can be used to model in members that do no fall on standard grid line intersections.

Beams and Joists build upon the previously placed columns and walls. As with the columns in the model, many of these members will be placed on grid lines; the Layout - <Member Type> - Add On-Grid command is used for modeling these members. Other structural members, such as purlins and cantilevers, don’t necessarily fall on grid lines. Several commands are available for placing these members: Layout - <Member Type> - Add Off-Grid, Layout - <Member Type> - Add Generation and Layout - <Member Type> – Add Cantilever. As with the columns added off the original grid lines, these members will cause SnapTo nodes to be generated.

The slab edge and slab openings must be defined before the deck and surface loads can be placed on the structure. Edges are usually defined as offsets from structural members, but may also be laid down freeform. If there is no deck, or if the deck is not going to be modeled, slab edges and openings are not required and should not be modeled.

Once the slab edges and any slab openings have been defined, the deck can be laid out using the Layout - Slab - Deck Assign command. For slab and deck, the slab or deck properties must first be specified using the PropTable - Decking command.

Loads can then be applied to the structure. Gravity load properties must first be specified using the PropTable - Loads commands.

If RAM Frame will be run, sizes must be assigned to the lateral members. This can either be done manually in the RAM Modeler or in RAM Frame or automatically in the RAM Steel Beam and RAM Steel Column modules (where lateral members will be preliminarily designed for gravity loads only). In the RAM Modeler this can be done in plan mode or elevation mode using the Layout - <Member Type> - Assign Sizes command. Sizes may be assigned to steel gravity beams and columns as well, in which case, if RAM Steel Beam Design or RAM Steel Column Design is run, the beam or column will be analyzed for the size assigned.

If RAM Concrete will be run, sizes must be assigned to all members, both lateral and gravity, prior to running an analysis. Concrete member sizes can be assigned manually in the RAM Modeler or in the RAM Concrete module, however, concrete beam and column section properties must be defined in the RAM Modeler. Steel member sizes can be assigned manually in the RAM Modeler or automatically in the RAM Steel design modules. 'Other' member sizes must be assigned manually in the RAM Modeler.

If RAM Foundation will be run, sizes must be assigned to lateral steel columns and to non-steel gravity columns. If these members do not have sizes assigned, the foundations upon which they are supported will not be designable.

If RAM Frame will be run, member end fixities must be assigned, if different than the default, to the Frame members. This can be done in plan mode or elevation mode using the Layout - <Member Type> - Assign Frame Fixity command or in RAM Frame using the Assign command.

The versatility of the RAM Modeler is seen in the ability to model members in any convenient order. The preceding order is generally that which is followed, but the user is free to create the model in any sequence that would allow the most rapid generation of the database.