RAM Concept errors and warnings: what they mean and how to fix them
The RAM Concept messages that come up most often on PT and RC slab models, what usually causes them, and the fixes recommended in Bentley’s help, knowledge base and RAM | STAAD forum, grouped by stage of the model.
A RAM Concept warning is often the only sign that part of a slab is not being designed the way you think. Some messages are harmless; others mean a strip, a tendon or a punching check is being ignored. This guide lists the messages we see most often in PT slab models and in models sent to us for PT design review, with the fixes documented by Bentley. Wording is paraphrased and may differ slightly between versions; the numbered references link to the original Bentley pages in the sources list. For modelling habits, see our main RAM Concept tips and tricks.
General rule: read the calc log and warnings after every Calc All, use the coordinates or object numbers in the message to find the problem on the relevant plan, and fix the cause rather than suppressing the message. RAM Concept keeps remeshing on every Calc All while mesh errors remain[1].
Jump to: Meshing · Tendons · Strips and cross sections · Punching · Loads and combinations · Load history · Import and files
1. Meshing errors and warnings
| Message (paraphrased) | Usual cause | Fix |
|---|---|---|
| Two or more slab areas or beams with the same priority overlap at (x,y) | Overlapping objects share a priority | Show priorities in Visible Objects, go to the coordinates, give the thicker object the higher priority[1] |
| Line is too short at (x,y) | Two nodes closer than the minimum element size of about 50 mm (2 in); they are merged | Redraw with snapping so vertices coincide or are clearly apart[1] |
| Feature eliminated at (x,y) | A feature too small to mesh, or small overlaps from unsnapped drawing | Remove the sliver or redraw with snaps[1] |
| Recursion too deep | Three nodes at a very tight angle make a pointy element | Usually not critical, but tidy the geometry; it distorts contour plots[1] |
| Two column elements below the slab are at the same location | Column drawn twice, or copied and pasted without changing the support set to Above | Show column numbers, double-click the duplicate and delete it[1] [2] |
| A column element below the slab is not attached to the slab | Column outside the slab edge or inside an opening | Move the column or extend the slab[1] |
| It is good modelling practice to connect wall centrelines | Wall ends close to, but not on, another wall’s centreline | Use the Fix button to move the wall end onto the centreline[1] |
| Vertical gaps in beam elevation; overlapping beams with conflicting stiffness; different concrete mixes at (x,y) | Inconsistent beam elevations or properties within one member | Make beam elevations, materials and stiffness consistent along the member[1] |
| Concrete density out of range | “Dummy” walls above given an unrealistically low density to avoid self-weight | Keep normal density, use a very small elastic modulus, and switch off self-weight of supports above in Calc Options[3] |
Bentley’s help puts it bluntly: nearly all meshing problems come from not using snapping properly[1]. A clean, snapped mesh input plan saves more time than any other habit.
2. Tendon errors and warnings
| Message (paraphrased) | Usual cause | Fix |
|---|---|---|
| Tendon radius is less than the minimum allowable | Large drape over a short length; can indicate an over-balanced profile | Revise the profile, or confirm the system’s minimum radius in Criteria – Materials with the PT specialist[4] |
| Tendon is harped and violates the minimum radius | Harped segments have a zero radius at the kink | Create a separate “harped” PT system with zero minimum radius and assign it to those tendons[4] |
| A profile point is not on the slab (with a Fix button) | Manual tendon end beyond the slab edge | Use Fix, or stretch the end onto or just inside the edge[4] |
| A profile point is not within the slab vertically / a tendon is out of the slab between profile points | Profile values relative to the soffit at a step, or a step between profile points | Inspect the tendon perspective and move profile points away from steps[4] |
| Tendon elevation conflict (profile point above a soffit step?) | Tendon end placed exactly at a change in slab level | Move the point off the step[4] |
| A tendon has a different number of strands than an adjacent tendon | Strand count changes along a continuous tendon | Use Select Connected Tendons and make counts consistent; drop strands with a separate tendon instead[4] [5] |
| Two connected tendons have inconsistent half span ratios | With generated tendons, a profile polyline crossing a banded polyline close to, but not at, a vertex | Make the profile polyline cross exactly at the vertex; Bentley describes the warning as not critical[6] [4] |
| A tendon is not connected to any jacks | Some tendons on a layer have jacks and others do not | On a layer with jacks, every tendon needs at least one jack[4] |
| Tendon jacked to a stress higher than its yield stress | Jacking force too high for the strand count | Reduce the jack force or increase strands[4] |
| Two jacks on one tendon have different friction coefficients or long-term losses | Jack properties edited separately | Make both jacks identical[4] |
| A non-external tendon is out of a cross section in design strip x | Section trimming or slope limit removed the part of the section the tendon passes through | Check the cross section perspective with tendons visible; revise trimming, strips or tendon position[5] [7] |
Tendon elevations in perspectives are only correct after Analyze All or Calc All, so re-run before judging a profile[5]. If you use both manual and generated tendons, make sure the same tendons are not on both layers[8].
3. Design strip and cross section warnings
- “A reinforcing bar is out of a cross section in 4C-1” (or similar). The label gives the span segment (4-1) and part: C is the column strip, L and R the half-middle strips. Turn on span segment numbers in Visible Objects to find it, then open the cross section perspective with bars displayed[9]. Program-designed bars always fit the trimmed section; user bars can sit outside it, for example bottom bars of a T-beam whose strip is trimmed to a slab rectangle[10].
- Cranked bars at a small step. Bentley’s forum answer: if the bar outside the trimmed section is in the compression zone, ignoring the warning can be reasonable; if it carries tension across the step, split the span segment at the step[9].
- “No concrete remaining at one or more locations”. Trimming or the slope limit has removed the whole section, usually where a strip crosses a step. Simplify the strip layout or change the trimming[7].
- Span segments with no width. With the width calculation set to manual, a span segment has zero width wherever no span boundaries are drawn[11].
- Design status shows ACI 318 clause 18 failures on an RC slab. The span segments are still flagged as post-tensioned; untick “Consider as Post-Tensioned” on both span plans and re-run[12].
- Precompression failure on the design status plan. Plot the gross centroid stress beside the status plan and check the limits set in the strip properties. Fix it by changing tendons (number or elevation) or strips (width or trimming)[13].
- Top bars detailed over the whole span. With manual support widths, “Consider End 1/End 2 as Support” was unticked, so the span detailer found no supports[14].
4. Punching shear messages
| Message (paraphrased) | Usual cause | Fix |
|---|---|---|
| Too many slab shapes intersecting the column shape | Several beams of different depths meet at the column | If beams have enough one-way shear capacity both ways, delete the check; otherwise simplify thickness changes at the column, reduce the search radius or change edge treatment[15] |
| No column critical sections found / no cutoff critical sections found; plot shows “No Calc” | Search radius too small, complex geometry, or the check was left behind when the column moved and the model was remeshed | Re-place the check on the column; review radius and edge treatment[15] |
| Punching critical section has Ix (or Iy) = 0 | A “critical section” that is a single line in plan, e.g. the search circle crosses two opposite slab edges | Reduce the search radius; check one-way shear with a strip or design section instead[15] |
| Check fails although “Design SSR if necessary” is ticked | Demand above the code maximum nominal shear strength, or rails already extend to the search radius | Increase thickness, add a drop panel or head, or raise concrete strength[15] |
| Skewed critical sections and odd stud rail layouts at edge columns | Column centred on the slab edge | Extend the slab to cover the column; consider an equivalent square column for circular columns[16] [15] |
5. Loading and combination warnings
- “Rule set … is being used by load combinations that appear to have load factors set for different purposes”. Combinations were edited away from the code defaults. If that was intended, the warning can be accepted; if not, save, print the current combinations, run Criteria – Rebuild Load Combos and compare[17].
- No live load reduction appears. Check the reduction code in Calc Options (default None), reducible load types, a non-zero maximum reduction on the strips, columns or checks, and that the model is not a mat[17].
- Pattern loading “does nothing”. Standard-context plots show the full pattern; the envelope is in the max/min contexts and the Auditor[18].
6. Load history deflection warnings
- “The floor may have incomplete design strip/cross section coverage …”. Load history needs cross section tributaries over every element with significant force, in two directions. The warning can be ignored in one-way regions where the spanning direction is covered[19].
- “The load history deflection solution did not converge. The expected deflection error is … mm”. Read the load history calc log, look for sections with no equilibrium, check first-order service deflections as a reality check, make sure no slab elements were pre-cracked in mesh input, and make sure every step includes dead load and the balance loading. Adding user reinforcement where runaway cracking occurs is often better than loosening the tolerance[20] [21].
- More on unexpected load history results is in our RAM Concept load history deflection guide.
7. RAM Structural System import and file messages
- Partial failure on import when analysis forces for a load case are close to zero; Bentley says this can be ignored[22].
- Load not on a slab, ignored. Usually a load defined inside an opening in RAM SS[22].
- Wall mesh errors and instability after import. Merged side-by-side openings across a wall leave the wall with no slab. Add a sliver of slab or a beam along the wall, or model two openings in RAM SS[22].
- “No Concept forces” in RAM Concrete Analysis. Columns outside a partial level were excluded from the Concept model[22].
- Transfer load case is empty. The RAM SS model status light must be green for transfer reactions to import[23].
- Two wall elements above the slab are at the same location (mats). A wall crossing the boundary between two mat foundations is imported for both; segment the wall at the boundary, delete the duplicate, or use one mat with openings[24].
- Link to RAM SS must be broken. The RAM SS file was moved, renamed or opened on another computer. Re-sync with File – Sync Ram Structural System – Import and Merge, unticking slabs, beams and openings you have edited[25].
- “External component has thrown an exception” on DWG import. Copy only the floor plan into a clean drawing and import that[26].
Stuck on a RAM Concept warning? Send us the model and drawings for a PT design review, read our RAM Concept tips and tricks, or contact our engineers.
Related PT design guides: RAM Concept tips and tricks, RAM Concept load history deflection, punching shear in PT slabs, tendon profile and layout.
Sources
Bentley Systems pages consulted on 13 November 2026. Content is paraphrased in our own words; RAM Concept is a Bentley Systems product and this guide is not Bentley documentation. Forum answers describe the software at the time they were written, so check behaviour in your version.
- RAM Concept help: Errors and warnings: Meshing
- Bentley Communities wiki: RAM Concept Plans And Printing [FAQ]
- RAM | STAAD Forum: RAM Concept - Dummy Walls Above Slab
- RAM Concept help: Errors and warnings: Tendons
- Bentley Communities wiki: RAM Concept Tendons [FAQ]
- RAM | STAAD Forum: Inconsistent tendon half span ratios
- Bentley Communities wiki: Cross Section Trimming [TN]
- Bentley Communities wiki: Automated Tendon Generation in RAM Concept
- RAM | STAAD Forum: RAM Concept - Reinforcing bar out of cross section
- Bentley Communities wiki: RAM Concept - Reinforcing bar out of cross section
- RAM Concept help: Design strips: miscellaneous tips
- Bentley Communities wiki: RAM Concept Design Strips [TN]
- RAM | STAAD Forum: Precompression Failure
- RAM | STAAD Forum: RAM Concept span detailing
- Bentley Communities wiki: RAM Concept Punching Shear Checks [FAQ]
- RAM | STAAD Forum: RAM Concept Shear Studs Design
- Bentley Communities wiki: RAM Concept Loading [FAQ]
- RAM | STAAD Forum: Issues with pattern loading in RAM Concept
- RAM Concept help: Errors and warnings: Load History Deflections
- RAM | STAAD Forum: RAM Concept - Load History Deflections Not Converging
- Bentley Communities wiki: RAM Concept - Load History Convergence
- Bentley Communities wiki: Common Errors and Warnings When Importing into RAM Concept [TN]
- Bentley Communities wiki: Importing Items into RAM Concept
- RAM | STAAD Forum: Analysis Error - Two wall elements above the slab are at the same location
- Bentley Communities wiki: Unlinking Ram Concept Files from RAM SS
- RAM | STAAD Forum: "External component has thrown an exception" in RAM Concept
Part of our PT design guides. RAM Concept and RAM Structural System are products of Bentley Systems; menu names, defaults and limits vary between versions, so confirm them in the help for your version. Codes are referred to by clause where we are confident of the reference; always check the edition and national annex adopted for your project.
Questions we are asked about this.
Can I ignore RAM Concept warnings?
Some, after checking them. Bentley describes the “inconsistent tendon half span ratios” warning as not critical, an import “partial failure” for near-zero forces as ignorable, and the load history coverage warning as acceptable in one-way regions. Mesh errors, tendons or bars out of cross sections and punching “No Calc” results should be investigated, because they can mean part of the slab is not designed.
What does “reinforcing bar out of a cross section in 1C-1” mean in RAM Concept?
A user bar lies in a part of the cross section removed by trimming or the slope limit, so it is not counted in that section. 1-1 is the span segment number and C the column strip (L and R are the half-middle strips). Display the cross section perspective with bars visible, then revise trimming, strips or the bar.
Why does the RAM Concept punching shear plot show No Calc?
Either no valid critical section was found within the search radius, or the punching check is no longer on its column, typically after a column moved and the model was remeshed. Re-place the check and review the search radius and edge treatment.
How do I fix load history deflections that do not converge in RAM Concept?
Check the load history calc log for sections without equilibrium, review first-order service deflections, make sure dead load and balance loading are in every step and that no elements are pre-cracked in mesh input. Adding reinforcement where cracking runs away is usually better than relaxing the convergence settings.
Why do I get mesh errors after importing from RAM Structural System?
Common causes are side-by-side openings merged across a wall, partial levels that exclude columns, and walls crossing the boundary between two mat foundations. Bentley’s fixes are a sliver of slab along the wall, separate openings in RAM SS, or segmenting the walls.
Technical information only. This article is general engineering information to help you understand the subject. It is not design advice for a specific project, codes and authority requirements change, and worked examples are illustrative. Designs must be prepared and checked by a qualified structural engineer responsible for the project, to the code edition adopted for the project. Disclaimer · Terms of use.
Send the drawings. Get an answer from our engineers.
WhatsApp or email the architectural or structural set, the location and what you need. The reply comes from the engineers who will do the work, with a proposed scope and programme.
- +971 52 118 2569
- Telephone
- +971 52 118 2569
- Office
- Al Warqa 1, Dubai, UAE
- Hours
- Sunday – Thursday, 09:00 – 18:00 GST

