Challenges in Implementing Engineering Codes

𝗘𝗧𝗔𝗕𝗦 – 𝗦𝗧𝗔𝗔𝗗 – 𝗠𝗜𝗗𝗔𝗦 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀 𝗮𝘀 𝗽𝗲𝗿 𝗜𝗦 𝟭𝟴𝟵𝟯 : 𝟮𝟬𝟮𝟱 Dear All, The release of 𝗜𝗦 𝟭𝟴𝟵𝟯 : 𝟮𝟬𝟮𝟱 𝗶𝘀 𝗮 𝗺𝗮𝗷𝗼𝗿 𝗺𝗶𝗹𝗲𝘀𝘁𝗼𝗻𝗲 for seismic safety in India. It introduces return-period-based, performance-oriented design, which is a welcome and much-needed advancement. However, 𝗴𝗿𝗼𝘂𝗻𝗱-𝗹𝗲𝘃𝗲𝗹 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗯𝗲 𝗮𝗰𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲𝗱 𝗯𝗲𝗳𝗼𝗿𝗲 𝗳𝘂𝗹𝗹-𝘀𝗰𝗮𝗹𝗲 𝗲𝗻𝗳𝗼𝗿𝗰𝗲𝗺𝗲𝗻𝘁. ✏️ 𝟭. 𝗥𝗲𝘁𝘂𝗿𝗻 𝗣𝗲𝗿𝗶𝗼𝗱–𝗕𝗮𝘀𝗲𝗱 𝗔𝗻𝗮𝗹𝘆𝘀𝗶𝘀   • No seamless workflow for 475 / 975 / 2475 / 4975 years   • Structure category ↔ return period mapping missing ✏️ 𝟮. 𝗩𝗲𝗿𝘁𝗶𝗰𝗮𝗹 𝗘𝗮𝗿𝘁𝗵𝗾𝘂𝗮𝗸𝗲 𝗔𝗰𝘁𝗶𝗼𝗻   • Vertical Base Shear (Vbd,v) not auto-generated   • Manual application → scope for inconsistency ✏️ 𝟯. 𝗩𝗲𝗿𝘁𝗶𝗰𝗮𝗹 𝗧𝗶𝗺𝗲 𝗣𝗲𝗿𝗶𝗼𝗱 (𝗧𝘃)   • Modal analysis mandated by code   • Fundamental vertical mode not clearly identified   • Tv not explicitly reported in software outputs ✏️ 𝟰. 𝗢𝘃𝗲𝗿𝘀𝘁𝗿𝗲𝗻𝗴𝘁𝗵 𝗙𝗮𝗰𝘁𝗼𝗿 (Ω)   • Introduced in IS 1893:2025   • R applied globally   • No element-specific Ω for walls, cores & collectors ✏️ 𝟱. 𝗟𝗼𝗮𝗱 𝗖𝗼𝗺𝗯𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗣𝗵𝗶𝗹𝗼𝘀𝗼𝗽𝗵𝘆   • Legacy practice of 1.5 × EQ still prevalent   • New code philosophy generally uses EQ with factor ≈ 1.0 ✏️ 𝟲. 𝗩𝗲𝗿𝘁𝗶𝗰𝗮𝗹 𝗦𝗵𝗲𝗮𝗿 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻   • Floor-weight-based distribution specified by code   • No built-in automation in ETABS / STAAD / MIDAS ✏️ 𝟳. 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗮𝗹 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻   • Normal / Important / Critical / Special   • Software does not auto-link:   • Category,Importance Factor & Return Period ✏️ 𝟴. 𝗗𝗿𝗶𝗳𝘁 & 𝗦𝗲𝗿𝘃𝗶𝗰𝗲𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗖𝗵𝗲𝗰𝗸𝘀   • RP-specific performance checks missing ✏️ 𝟵. 𝗦𝗼𝗶𝗹–𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝗼𝗻   • Code stresses realistic SSI   • Current models largely linear & RP-independent ✏️ 𝟭𝟬. 𝗡𝗼𝗻-𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗮𝗹 𝗘𝗹𝗲𝗺𝗲𝗻𝘁 𝗠𝗼𝗱𝗲𝗹𝗹𝗶𝗻𝗴   • NSE performance emphasized in new code   • Partition walls, facades & services not explicitly modelled   • NSE damage checks mostly manual ✏️𝟭𝟭 . 𝗧𝗶𝗺𝗲 𝗛𝗶𝘀𝘁𝗼𝗿𝘆 𝗔𝗻𝗮𝗹𝘆𝘀𝗶𝘀   • Record selection & scaling for multiple return periods unclear   • Vertical + horizontal combination not standardized   • Output interpretation varies across software ✏️𝟭𝟮 . 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲-𝗕𝗮𝘀𝗲𝗱 𝗗𝗲𝘀𝗶𝗴𝗻 (𝗣𝗕𝗗)   • Code moves towards PBD philosophy   • No Indian-specific automated acceptance criteria. The BIS Codal Committee may consider 𝗲𝘅𝘁𝗲𝗻𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝘁𝗿𝗮𝗻𝘀𝗶𝘁𝗶𝗼𝗻 / 𝗮𝗱𝗼𝗽𝘁𝗶𝗼𝗻 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲 𝗼𝗳 𝗜𝗦 𝟭𝟴𝟵𝟯 : 𝟮𝟬𝟮𝟱 𝘂𝗻𝘁𝗶𝗹 𝗺𝗮𝗷𝗼𝗿 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲s 𝗮𝗿𝗲 𝗳𝘂𝗹𝗹𝘆 𝘁𝗲𝘀𝘁𝗲𝗱, 𝘂𝗽𝗴𝗿𝗮𝗱𝗲𝗱 𝗮𝗻𝗱 𝗮𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗲𝗱 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗻𝗲𝘄 𝘀𝗲𝗶𝘀𝗺𝗶𝗰 𝗽𝗵𝗶𝗹𝗼𝘀𝗼𝗽𝗵𝘆. 𝗞𝗶𝗻𝗱𝗹𝘆 𝘀𝗵𝗮𝗿𝗲 𝘆𝗼𝘂𝗿 𝗶𝘀𝘀𝘂𝗲𝘀/𝘀𝘂𝗴𝗴𝗲𝘀𝘁𝗶𝗼𝗻𝘀/𝗢𝗽𝗶𝗻𝗶𝗼𝗻𝘀.

Lately, I’ve had numerous conversations with clients about implementing IEC 61850 and the challenges they face—not just during design and deployment but also due to gaps in their teams’ knowledge. Both new and experienced technicians often struggle with testing and troubleshooting, making the transition even more complex. While IEC 61850 has been well-established in Europe for over a decade, its adoption among U.S. utilities has only recently gained momentum. New technicians often find it challenging to grasp the basics, navigate its complexity, and transition from familiar protocols like Modbus. Configuration tools such as SCL files and real-time communication methods like GOOSE and Sampled Values add to the learning curve. On top of that, cybersecurity is now a crucial factor that they must understand from the outset. For experienced technicians, the shift is different but equally demanding. Many are used to the comfort of physical wires, test switches, and relays they can see and touch. Now, they’re being asked to troubleshoot networks, analyze packets, and trust that invisible messages are flying through fiber optic cables. Transitioning from hardwired to networked systems with GOOSE messaging requires a whole new troubleshooting mindset. Traditional test sets and clip-on probes don’t cut it anymore, and learning new software-based tools can feel like learning a new language. And let’s not forget cybersecurity—something that wasn’t even on the radar for many veteran technicians but is now a critical part of the job. If you’re involved in a project or planning to integrate IEC-61850 into your system, what challenges are you encountering? So, for those of you involved in training, who do you think is more challenging to teach—the new generation or the old-school experts set in their ways? I’d love to hear your thoughts!

🚫 "But that's not consistent with our existing codebase!" After 10 years in software engineering, I've heard this phrase countless times when trying to introduce better design practices into legacy systems. Here's the uncomfortable truth: Consistency with bad design isn't actually valuable. It's just organised chaos. I've worked in codebases where technical debt runs deep, no polymorphism, code smells everywhere, violations of basic SOLID principles. When you try to introduce proper design patterns, you're often met with resistance disguised as a desire for "consistency." But here's what I've learned: If we keep doing things the wrong way just to maintain consistency, we never improve. The codebase becomes a monument to past mistakes rather than a foundation for future success. The real challenge isn't technical, it's cultural. Teams often resist change because: - They're unfamiliar with better design principles - They fear the learning curve - They mistake "familiar" for "maintainable" My approach: ✅ Start small with isolated improvements in new features ✅ Let results speak louder than theory ✅ Frame changes in business value, not engineering ideals ✅ Invest in team education about design principles Remember: Good design isn't about following trends, it's about writing code that's testable, maintainable, and adaptable to change. Sometimes breaking consistency is exactly what your codebase needs to heal. What's your experience with introducing design improvements in legacy systems? Have you faced similar resistance? #SoftwareEngineering #CleanCode #TechnicalDebt #SoftwareDesign #Programming

🚧 𝐏𝐫𝐞-𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐞𝐝 𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠𝐬 (𝐏𝐄𝐁𝐬) – 𝐀𝐫𝐞 𝐈𝐒 𝐂𝐨𝐝𝐞𝐬 𝐄𝐧𝐨𝐮𝐠𝐡? 🚧 PEBs are the backbone of India’s industrial and logistics boom. Their speed, cost efficiency, and versatility are unmatched. But here’s the challenge: our current IS codes (IS 800, IS 801, IS 875) were never written with modern PEBs in mind. 🔎 Key Gaps in IS Codes for PEBs: 1️⃣ Wind Loads – IS 875 is too simplified; it misses dynamic effects like buffeting and vortex shedding. 2️⃣ Cold-Formed Members – IS 801 (1975) is outdated; it ignores modern Z/C purlin buckling and uplift checks. 3️⃣ Connections – IS 800 assumes rigid/pinned, but PEB joints are mostly semi-rigid. 4️⃣ Advanced Analysis – No guidance for FE, CFD, or wind tunnel integration. ⚡ What engineers can do: ✔ Follow a dual-code approach – IS for compliance, MBMA/AISC/AISI for optimization. ✔ Model semi-rigid connections instead of assuming rigid/pinned. ✔ Prioritize serviceability (deflection, vibration, cladding performance). ✔ Apply advanced analysis selectively and document choices clearly. 👉 Bottom line: IS codes ensure baseline safety, but for true optimization and real-world performance, engineers must combine Indian standards with international best practices. 💡 Future need: A dedicated Indian code for PEBs. #StructuralEngineering #PreEngineeredBuildings #SteelStructures #CivilEngineering #IndianStandards #PEBDesign #StructuralAnalysis #WindEngineering #ConstructionInnovation #EngineeringLeadership

𝗛𝗮𝘃𝗲 𝘆𝗼𝘂 𝗲𝘃𝗲𝗿 𝘄𝗼𝗻𝗱𝗲𝗿𝗲𝗱 𝘄𝗵𝘆 𝘆𝗼𝘂𝗿 𝗽𝗲𝗿𝗳𝗲𝗰𝘁𝗹𝘆 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗱 𝘀𝗼𝗹𝗮𝗿 𝗼𝗿 𝘄𝗶𝗻𝗱 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘀𝘁𝗶𝗹𝗹 𝗴𝗲𝘁𝘀 𝗱𝗲𝗹𝗮𝘆𝗲𝗱 𝗮𝘁 𝘁𝗵𝗲 𝗴𝗿𝗶𝗱-𝗮𝗽𝗽𝗿𝗼𝘃𝗮𝗹 𝘀𝘁𝗮𝗴𝗲? It’s frustrating. You’ve invested months in engineering, only to be told: “Not grid compliant.” But here’s the reality—without strict grid codes, our networks simply cannot survive. Imagine every power producer pushing energy at will, without studying the impact. The result? Unstable voltages, frequency collapse, blackouts. That’s why grid codes exist. What grid codes really mean for us as engineers and developers:   • They ensure that every new plant or industrial load doesn’t harm existing grid operations.   • The Utility defines which planning studies are required—these vary with project size, grid strength, and technology.   • Models matter. PSS®E or PSCAD models are often mandatory so the utility can run transient and stability checks.   • As renewable penetration grows, rules evolve—LVRT, HVRT, ramp-up/ramp-down limits, harmonic limits.   • Point of Connection (POC) compliance is critical. For inverter-based plants, reactive capability is usually required at the POC, not just at generator terminals.   • Large clusters bring shared problems—like harmonics—even if one plant alone seems “clean.” 👉 The bigger picture: grid code compliance isn’t just regulation. It’s about protecting the stability of the system we all depend on. For developers, it’s also the difference between quick approvals and endless disputes. Takeaway: Treat compliance not as a hurdle, but as an engineering discipline. Build it into your design early—it saves time, cost, and reputation later. What’s been your toughest grid compliance challenge—LVRT, harmonics, or reactive power at POC? Let’s discuss. Save time at approval stage—reach out to learn how we build compliance into designs early https://wa.me/919042342912 #powerprojects #gridcode #gridcompliance #renewables #powersystems

I received many messages last week. ↳ Most of them were about ISO 26262 implementation challenges. ↳ Automotive engineers are struggling with this standard. ↳ The complexity is overwhelming many teams. Here's a story that might resonate with you: Last year, I was consulting for a major OEM. Their lead engineer, Sarah, looked exhausted. "We've been trying to implement ISO 26262 for months," she sighed. "It feels like we're drowning in documentation and processes." Sarah's not alone. 72% of automotive companies report significant hurdles in ISO 26262 adoption. Here are the top 10 challenges I've seen: 1. Complexity overload: The standard has 12 parts! 2. Resource intensity: It's a full-time job just to manage. 3. Lack of expertise: Finding qualified personnel is tough. 4. Tool qualification headaches: Validating every tool is tedious. 5. Legacy system integration: Older systems rarely fit easily. 6. Supplier chain complications: Ensuring compliance throughout is a nightmare. 7. Evolving technology: AI and ML don't fit neatly into the standard. 8. Cost implications: Budget overruns are common. 9. Time constraints: It slows down development cycles. 10. Cultural resistance: "We've always done it this way" mentality. But here's the kicker: Companies that successfully implement ISO 26262 see a 35% reduction in safety-related recalls. The payoff is real. It's just a matter of navigating the challenges. What's your experience with ISO 26262? Have you faced similar hurdles? Share this post to help other automotive professionals tackle these challenges. Let's make our roads safer, one compliant system at a time. #AutomotiveSafety #ISO26262 #FunctionalSafety #AutomotiveEngineering