Explain seismic design requirements for storage racks under ASCE 7 Chapter 15, especially for high-seismic jurisdictions such as California.
domain: asce.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm racks are classified as nonbuilding structures under ASCE 7 Chapter 15, specifically Section 15.5.3 (Steel Storage Racks and Steel Cantilevered Storage Racks in the 2022 edition)
Note steel storage racks over roughly 8 ft are treated as nonbuilding structures with their own response modification factor (R) from ASCE 7 Table 15.4-1, commonly cited as R = 4.0 for steel storage racks — confirm the exact value against the specific ASCE 7 edition in force, since values can differ by rack type/edition
Confirm ANSI MH16.1's own seismic provisions are written to align with the referenced ASCE 7 edition (MH16.1-2023 aligned to ASCE/SEI 7-22) — mismatched editions between the adopted building code and the rack standard used for design is a common error
Note California and other high-seismic jurisdictions may layer additional plan-review/PE-stamp and special-inspection requirements on top of the base ASCE 7 provisions — confirm with the local building department (e.g., CBC amendments) rather than assuming ASCE 7 alone governs
Recommend engaging a PE experienced in rack seismic design for any installation in Seismic Design Category C or higher, since rack seismic calculations require site-specific parameters (Ss, S1, site class) rather than generic assumptions
Known gotchas
R-values and specific section numbers for rack seismic design have changed across ASCE 7 editions (7-10, 7-16, 7-22) — cite the edition, not just 'ASCE 7' generically, when precision matters
California's state-amended building code (CBC) may impose stricter or additional requirements beyond base ASCE 7/IBC — don't assume the generic IBC/ASCE 7 answer applies unmodified in CA
Seismic rack design depends on site-specific seismic parameters, not a single national number — a de-rated or wrongly-sourced Ss/S1 value invalidates the whole calculation
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?