Confirm the core principle: rack load capacity is a function of beam elevation and bay geometry (among other factors) — changing beam height, adding/removing levels, or altering upright spacing changes the engineered capacity, even though the physical components may be reused
Require the original LARC drawing be pulled and reviewed by a qualified rack engineer before any beam relocation is carried out, per RMI guidance
Require the new configuration be evaluated and re-certified by a qualified engineer, with updated LARC drawings re-stamped (where a PE stamp applies) reflecting the new beam elevations and resulting capacity
Require the physical load capacity plaque be replaced to match the new configuration before the rack is reloaded — the old plaque number no longer applies once beam elevations change
Flag that reconfiguration is not just a maintenance task — RMI guidance frames it as requiring the same engineering rigor as original installation, since beam-level changes can either increase or decrease effective capacity depending on the resulting bay height/slenderness
Known gotchas
Facilities commonly move beams to accommodate new inventory without re-engineering — this is explicitly called out by RMI as an unsafe/noncompliant practice, not a minor documentation lapse
A rack can end up either over- or under-rated after an uncontrolled beam move — don't assume the risk only runs toward reduced capacity; incorrect assumptions about capacity increases are equally a hazard
Reusing the old plaque after a configuration change misrepresents the rack's actual current capacity to floor staff and is a direct safety hazard, not just a paperwork technicality
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?