𝐌𝐢𝐧𝐢𝐦𝐮𝐦 𝐜𝐨𝐝𝐞 𝐜𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐜𝐚𝐧 𝐛𝐞 𝐚 𝐩𝐨𝐨𝐫 𝐬𝐞𝐢𝐬𝐦𝐢𝐜 𝐝𝐞𝐬𝐢𝐠𝐧 𝐰𝐢𝐭𝐡 𝐥𝐞𝐠𝐚𝐥 𝐜𝐨𝐯𝐞𝐫 Earlier in my career, if the analysis ran, the code checks were green and the minimum detailing clauses were satisfied, I thought I had done my job. For a while I was mainly a user of software and codes, not really doing structural engineering. A while ago I wrote about minimum-code practice and why it can still lead to weak seismic performance. After that, Dr. Subramanian, invited me to develop the idea into a paper for Structural Engineering Digest, the journal of the Indian Association of Structural Engineers, in a special issue on the relevance of codes. I said yes because if we do not talk honestly about the gap between compliance and behaviour, we will keep repeating the same seismic mistakes in new buildings. 𝐖𝐡𝐚𝐭 𝐭𝐡𝐢𝐬 𝐩𝐨𝐬𝐭 𝐢𝐬 𝐚𝐛𝐨𝐮𝐭 This post is about structures where earthquake effects control (or strongly influence) the lateral design. It is not about purely wind-governed buildings. Most of us know this, but it is easy to forget in project work: • Codes are a 𝑚𝑖𝑛𝑖𝑚𝑢𝑚 𝑠𝑎𝑓𝑒𝑡𝑦 𝑏𝑎𝑠𝑒𝑙𝑖𝑛𝑒, mainly for life safety. • They are not a complete design handbook. And that minimum keeps moving as hazard maps, spectra, load factors and detailing rules are updated. 𝐖𝐡𝐲 𝐭𝐡𝐢𝐬 𝐢𝐬 𝐫𝐢𝐬𝐤𝐲 𝐟𝐨𝐫 𝐥𝐨𝐰-𝐝𝐮𝐜𝐭𝐢𝐥𝐢𝐭𝐲 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 For low-ductility structures, the current minimum clauses can still allow things like: • no strong-column–weak-beam check • lap splices in potential plastic hinge regions • unfavourable failure modes like concrete crushing, shear and joint shear not explicitly protected • no explicit capacity design for force-controlled actions All of these can be “code-compliant”, but do we, as the engineers, really know what happens to such buildings at the design-level earthquake and beyond? 𝐖𝐡𝐚𝐭 𝐈 𝐚𝐫𝐠𝐮𝐞 𝐢𝐧 𝐭𝐡𝐞 𝐩𝐚𝐩𝐞𝐫 The paper tries to do three things: • Explain why minimum-code thinking is risky when ductility is limited. • Revisit capacity design and hierarchy of failure as practical tools, not academic ideas. • Encourage younger engineers to design from structural fundamentals and first principles, so their judgement is not locked to a single code or country. For me, that is the difference between being a code user and being an engineer: design from fundamentals first, then use the code to check. Over time you see why clauses exist, where they are conservative or blind, and where you can safely do better. Get the fundamentals right and you can carry that judgement anywhere, even to Mars! Let alone other countries! I have put a few slides with the key ideas in the post. The full paper PDF is in the first comment. If you could remove one “code-compliant” seismic detail from your office tomorrow because you do not trust its performance, what would it be? #StructuralEngineering #EarthquakeEngineering
-
+1