Reference RMI's published guidance document, 'Guidelines for the Assessment and Repair or Replacement of Damaged Rack,' as the primary industry reference
Confirm the core rule: damaged rack must be unloaded and isolated immediately upon discovery, and evaluated by a qualified rack engineer before any repair or reload decision
Define 'qualified': per RMI guidance, a rack design professional holding a relevant engineering degree, professional license/certification, or demonstrated equivalent field expertise in rack systems — not general maintenance staff
Explain the repair-vs-replace logic: RMI guidance generally favors replacement (especially with OEM parts) when the manufacturer/model can be identified and damage is structural; repair (OEM parts, engineered repair kits, or engineered field repairs) may be acceptable for limited, well-defined damage when overseen by a qualified engineer
Note that plant maintenance personnel bolting, welding, or straightening damaged components on their own, without engineering evaluation, is explicitly called out as unsafe practice in RMI guidance
Confirm any accepted repair must be documented and, where it changes capacity or configuration, reflected in updated LARC drawings and load plaques
Known gotchas
Field welding or straightening of damaged steel members by uncertified maintenance staff is a commonly cited unsafe practice — cold-formed steel that has yielded generally cannot simply be bent back and treated as structurally sound
'Repair' is only appropriate for a subset of damage types/severities per RMI guidance — don't present it as always equally valid to replacement without engineering judgment
The RMI guidance document is periodically revised (has gone through multiple versions) — check that the specific requirement being cited comes from the current version, not an older one
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?