Engineering Standards And Compliance

🧪Engineering Focus: Pipe Sizing & Pressure Drop Calculations 🌡️ Accurate pipe sizing is critical to achieving optimal flow, minimizing pressure loss, and reducing energy consumption in fluid systems. Here’s a streamlined guide with key technical formulas and considerations every engineer should know: 1. Define Flow Rate (Q) Use process data or equipment specifications Common units: m³/hr (cubic meters per hour) LPM (liters per minute) GPM (gallons per minute) 2. Select Design Velocity (V) Recommended velocity ranges (depends on fluid type and application): Water: 1 – 3 m/s Oil: 1 – 2 m/s Steam (low pressure): 20 – 35 m/s Compressed air: 10 – 20 m/s 3. Estimate Pipe Diameter (D) Use the continuity equation: Formula: D = √(4 × Q) / (π × V) Where: D = pipe inner diameter (m) Q = volumetric flow rate (m³/s) V = velocity (m/s) Tip: Convert Q to m³/s if originally in m³/hr or LPM before using this formula. 4. Calculate Pressure Drop (ΔP) Apply the Darcy-Weisbach equation for head loss due to friction: Formula: ΔP = f × (L / D) × (ρ × V² / 2) Where: ΔP = pressure drop (Pa) f = Darcy friction factor (use Moody chart or Colebrook equation) L = pipe length (m) D = pipe diameter (m) ρ = fluid density (kg/m³) V = velocity (m/s) 5. Account for Minor Losses Include pressure losses due to bends, tees, valves, etc. Formula: ΔP_total = ΔP_friction + Σ(K × ρ × V² / 2) Where: K = loss coefficient for each fitting Use standard tables for K-values 🔍Engineering Insight: Oversized pipes = higher material cost, but lower energy loss Undersized pipes = higher velocity, more friction, higher pumping power Smart sizing is about optimizing both CAPEX and OPEX 💬 Have you ever had to redesign a system because the pressure drop exceeded expectations? Let’s connect and exchange ideas on how to get it right the first time! #PipeSizing #PressureDrop #DarcyWeisbach #FluidDynamics #MechanicalEngineering #ProcessDesign #HydraulicCalculations #PipingDesign #EngineeringPrinciples #LinkedInEngineering

Did you know that weak measurement and verification systems can undermine the credibility of entire sustainability and climate programs? Recent analysis by Senken of more than 2,300 carbon projects found that in some categories, fewer than 16% of issued carbon credits corresponded to real emission reductions, highlighting the risks of inadequate monitoring and verification systems. At the same time, global climate finance and carbon markets depend on rigorous Measurement, Reporting, and Verification (MRV) processes; because one verified carbon credit represents one tonne of greenhouse gas emissions reduced or removed, a unit that governments, investors, and institutions rely on to track real progress. These numbers reinforce a simple but critical lesson: credibility in sustainability is built on systems, not promises. In practice, this means investing in robust monitoring frameworks, conducting independent compliance audits, and ensuring that data can withstand scrutiny from regulators, financiers, and stakeholders. Organizations that prioritize these systems are not only better prepared for evolving disclosure requirements, they are also better positioned to attract investment, manage risk, and deliver measurable impact. As sustainability expectations continue to rise globally, the institutions that will lead are those that understand that accountability is not an administrative requirement; it is a strategic asset. Because in sustainability and climate action, what gets measured, verified, and audited is what ultimately builds trust and delivers lasting results.

Electrical Thumb Rules for Equipment Selection 1. Power Cable Selection • Voltage Drop: • Maintain ≤ 3% for feeders • ≤ 5% for branch circuits • Current Carrying Capacity: • Cable should support 1.5–2 times the full load current. • Cable Size: • For 3-phase: 1.5–2.5 mm² per kW • For 1-phase: 1–2 mm² per kW • Cable Insulation Level: • 600V/1000V for LT (Low Tension) systems • 6.6kV/11kV for HT (High Tension) systems 2. Earthing Cable Selection • Earth Fault Current: • Design for 10–20 times the full load current. • Earthing Cable Size: • Select 50–67% of the phase conductor size. • Earth Resistance: • ≤ 1 Ω for LT systems • ≤ 5 Ω for HT systems 3. Motor Selection • Motor Capacity: • Rated power: 1.5–2 times the load HP/kW. • Efficiency: • ≥ 90% for IE2 motors • ≥ 95% for IE3 motors • Power Factor: • Maintain ≥ 0.8 for induction motors. • Starting Current: • Typically 6–8 times the full load current. 4. Generator Selection • Generator Capacity: • Rated power: 1.5–2 times the load KVA/kW. • Efficiency: • Maintain ≥ 90%. • Power Factor: • Maintain ≥ 0.8. • Frequency: • 50/60 Hz depending on the regional standard. 5. Transformer Selection • Transformer Capacity: • Rated power: 1.5–2 times the load kVA. • Efficiency: • ≥ 95% for distribution transformers • ≥ 98% for power transformers • Voltage Regulation: • Maintain ≤ 4%. • Insulation Level: • 600V/1000V for LT • 6.6kV/11kV for HT 6. UPS Selection • UPS Capacity: • Rated power: 1.5–2 times the load kVA/kW. • Efficiency: • Maintain ≥ 95%. • Power Factor: • Maintain ≥ 0.8. • Backup Time: • Design for 15–60 minutes based on application requirements. 7. Inverter Selection • Inverter Capacity: • Rated power: 1.5–2 times the load kW. • Efficiency: • Maintain ≥ 95%. • Power Factor: • Maintain ≥ 0.8. • Frequency: • 50/60 Hz as per regional standards. 8. Other Equipment Selection • Circuit Breakers (CB): • Rated current: 1.5–2 times the full load current. • Contactors: • Rated current: 1.5–2 times the full load current. • Relays: • Rated current: 1–2 times the full load current. • Fuses: • Rated current: 1.5–2 times the full load current. 9. General Guidelines • Derating: • Consider a reduction of: • 20–30% for temperature effects • 10–20% for altitude effects • Overloading Tolerance: • Motors: Allow 10–20% overloading. • Transformers: Allow 5–10% overloading. • Efficiency: • Prioritize high-efficiency equipment for energy conservation. • Redundancy: • For critical systems, design with N+1 redundancy. This structured approach ensures optimal performance, reliability, and safety for electrical systems.

Periodic Table for Quality Engineers (QA/QC) 🎯 Because quality isn’t random — it’s systematic, structured, and scientific. I created this Periodic Table for Quality Engineers to help professionals visualize the key concepts, tools, methods, and standards that drive excellence in Oil & Gas, Construction, Fabrication, and Energy sectors. Each “element” represents a core competency every QA/QC professional should master 👇 📘 F-Series: Foundation QF – Quality Fundamentals SP – Specifications DR – Drawings & Isometrics CS – Codes & Standards MT – Material Traceability DM – Document Management 📏 I-Series: Inspection VI – Visual Inspection DI – Dimensional Inspection FI – Fit-up Inspection WI – Welding Inspection PI – Painting/Coating Inspection HT – Hydrostatic Testing PT – Pneumatic Testing RI – Receiving Inspection 🔧 W-Series: Welding & Fabrication WPS – Welding Procedure Specification PQR – Procedure Qualification Record WPQ – Welder Qualification PN – P-Number FN – F-Number AN – A-Number FE – Filler Metal Selection 🧲 N-Series: NDT Methods VT – Visual Testing PT – Dye Penetrant Testing MT – Magnetic Particle Testing UT – Ultrasonic Testing RT – Radiographic Testing PA – Phased Array ET – Eddy Current HT – Hardness Testing 📚 S-Series: Standards & Codes AS – ASME AW – AWS IS – ISO 9001 OH – ISO 45001 ENV – ISO 14001 API – American Petroleum Institute NB – National Board 📦 T-Series: Quality Tools RCA – Root Cause Analysis 5W1H – Problem Solving FMEA – Failure Mode & Effects Analysis CP – Control Plan QC7 – Seven Quality Tools LSS – Lean Six Sigma CAPA – Corrective & Preventive Action 📝 P-Series: Project Documentation QAP – Quality Plan ITP – Inspection & Test Plan WMS – Work Method Statement MS – Method Statement RFI – Request for Inspection NCR – Nonconformance Report MIR – Material Inspection Request RIR – Receiving Inspection Report 🏗 C-Series: Construction Quality PW – Piping Works SW – Structural Works CW – Civil Works PWG – PWHT / Heat Treatment PTW – Permit to Work CT – Coating / Blasting 🧩 Together, these form the “Periodic Table of Quality Engineering” — a structured map of the skills every modern QA/QC professional needs. If you find it useful, share it to help others in the quality community. ====== Follow me Govind Tiwari,PhD for more QA/QC insights, tools, and frameworks.

𝐀𝐈 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 & 𝐃𝐚𝐭𝐚 𝐏𝐫𝐨𝐭𝐞𝐜𝐭𝐢𝐨𝐧 𝐋𝐚𝐰𝐬 𝐟𝐨𝐫 𝐆𝐞𝐧𝐀𝐈 𝐀𝐩𝐩𝐬 Building GenAI Apps for a Global Audience?  Understanding Regional Data Protection and AI laws is not optional, it is foundational. Here is what you need to know: 1. UNDERSTANDING GLOBAL REGULATORY VARIANCE Building GenAI for a global audience requires understanding regional data protection and AI laws. Key Regulations by Region: • EU AI Act: Risk-based AI obligations for certain AI systems and transparency use cases • GDPR (EU): Transparency & Consent • DPDP (India): Digital Personal Data Protection • PIPL (China): Strict Data Localization • CCPA (California): Data Access & Opt-Out • LGPD (Brazil): Local Compliance Rules 2. IMPACT OF THESE REGULATIONS ON YOUR AI TRAINING DATA To build compliant GenAI apps,  Ensure that data used for training AI models follows the regional rules: Data Collection → Processing → Model Training → Deployment Three Core Requirements: a. User Consent: Obtain explicit consent for data collection and use b. Data Minimization: Collect only necessary data for the intended purpose c. Anonymization: Remove personally identifiable information from training data 3. MITIGATING AI ETHICS AND BIAS RISKS AI systems must be fair and ethical, particularly in high-risk areas: a. Fairness: Ensure your AI models don't discriminate, especially in areas like recruitment or finance. b. Bias Mitigation: Regularly test and adjust your models to reduce bias in the outputs. 4. ENSURING TRANSPARENCY IN AI MODEL DEVELOPMENT Transparency is a cornerstone of compliance, especially when your AI impacts users directly: a. Explainability: Protect data in transit and at rest. b. Consent Management: Collect, track, and manage user consent. c. Privacy by Design: Embed privacy into every system layer. 5. MANAGING CROSS-BORDER DATA FLOW GenAI apps often rely on data from various regions, so it's critical to understand data sovereignty laws: a. Data Sovereignty: Follow local laws on where data is stored and processed. b. Data Transfer Agreements: Use SCCs or BCRs for compliant cross-border transfers. THE COMPLIANCE CHECKLIST Before launching GenAI globally, verify: 1. Regional Compliance: • GDPR for EU? (Transparency & Consent) • DPDP for India? (Data Protection) • PIPL for China? (Data Localization) • CCPA for California? (Access & Opt-Out) • LGPD for Brazil? (Local Rules) 2. Training Data: • User consent obtained? • Data minimized? • PII anonymized? 3. Ethics & Bias: • Fairness tested? • Bias mitigation in place? 4. Transparency: • Explainability documented? • Consent management system? • Privacy by design? 5. Cross-Border: • Data sovereignty compliance? • Transfer agreements (SCCs/BCRs)? Each region has different requirements.  Build for the strictest, adapt for the rest. Which regulation applies to your GenAI app?

Guidance on Climate Transition Plans under ESRS For organisations navigating climate reporting and sustainability compliance, the new guidance on implementing climate transition plans under the European Sustainability Reporting Standards (ESRS) provides valuable support! The guidance provides an approach for organisations to meet the ESRS requirements by detailing disclosure obligations that align with key EU regulations, such as the Corporate Sustainability Due Diligence Directive (CSDDD) and the EU Taxonomy. This alignment helps ensure climate transition activities and sustainability disclosures meet broader European compliance standards, reinforcing their commitment to responsible and sustainable practices in line with EU legislation. 1️⃣ Purpose: Offers non-binding guidance to help organizations create effective transition plans for climate change mitigation. 2️⃣ Compliance: Maps out how ESRS aligns with EU laws like the Corporate Sustainability Due Diligence Directive (CSDDD) and EU Taxonomy, ensuring regulatory alignment 3️⃣ Structure: Covers all aspects of climate disclosure—from European frameworks and disclosure requirements to international standards 4️⃣ Paris Agreement Alignment: Organizations must disclose targets that align with the 1.5°C goal, showing commitment to global climate efforts 5️⃣ Decarbonization: Outlines required emissions reduction actions, including operational changes and product modifications. Organisations are required to outline specific actions, known as "decarbonization levers," which may include operational adjustments, product changes, and other emissions reduction initiatives 6️⃣ Investments: Specifies the need for transparent reporting on investments, including EU Taxonomy-aligned CapEx for sustainable projects 7️⃣ Disclosures: Companies involved in EU Taxonomy activities must show their alignment with taxonomy criteria for sustainable finance 8️⃣ Governance: Transition plans should be embedded within overall corporate strategy, backed by governance bodies to ensure alignment with broader goals 9️⃣ Progress: Regular updates on implementation are required, measuring action effectiveness toward emissions targets 🔟 IROs from climate change mitigation: The guidance stresses the need for organisations to assess and disclose social and environmental impacts, risks, and opportunities linked to their climate transition plans The guidance emphasises that climate transition plans should be fully embedded within a company's overarching strategy and be actively supported by governance bodies. This integration ensures that climate goals are not treated as standalone objectives but are interwoven with long-term corporate planning. By doing so, organisations can align their climate ambitions with their overall business objectives, securing strategic and governance-level commitment to climate action.

🚧 New C&D Waste Management Rules Announced! 🚧 The Ministry of Environment, Forest and Climate Change (MoEF) has released a draft notification for the new Construction and Demolition Waste Management Rules, 2024. Set to come into effect from 1st April 2025, these updated rules aim to enhance sustainability and streamline waste management processes. Silent Features: • Property Developers & Infrastructure Companies: Mandatory on-site waste segregation, minimum 50% recycling rate, and 20% use of recycled materials. • Recyclers: Compliance with environmental standards, capacity enhancement, and advanced technology investment. • State Governments: Policy enactment, infrastructure development, and public awareness campaigns. • Urban Local Bodies (ULBs): Dedicated C&D waste collection systems, facility management, and regulation enforcement. • Extended Producer Responsibility (EPR): Registration on the EPR online portal, 100% waste deposit obligations, EPR certificates, and compliance monitoring. The public is invited to share suggestions or comments on the draft within 60 days. Let’s work together to ensure a greener future for our communities! 📧 Send your feedback to: mishra.vp@gov.in amit.vashishtha@nic.in #Sustainability #WasteManagement #GreenFuture #CircularEconomy

Last week #NIST released three post-#quantum #encryption standards. Why is this significant? Put simply, from a practical standpoint: risk management and compliance. First, on risk management: experts now say that quantum computing is less than a decade away. Quantum computers are expected to have the power to search large keyspaces very quickly, which means they will be able to decrypt current encryption. Moreover, it is entirely plausible that encrypted information recorded today is being stored for decryption when quantum computing becomes available. If you speculatively apply quantum-resistant encryption to your data now, you will reduce the risk of an adversary being able to successfully exploit your data when they have access to quantum computing. Second, on compliance: NIST is the governing body for standards in the USA, and many other nations take their encryption standards from NIST, as they do not have resources at the same scale as NIST. You can be certain that NIST-approved post-quantum algorithms will start being mentioned in various compliance checklists, as is the case currently with algorithms such as AES-256 and SHA-256. Note well that these algorithms have #FIPS numbers associated with them - meaning "Federal Information Processing Standard". Briefly, the approved algorithms are: 🔒 ML-KEM, for encrypted key exchange, as FIPS 203 🔒 ML-DSA, for digital signatures, as FIPS 204 🔒 SLH-DSA, for stateless hash-based digital signatures, as FIPS 205 There is a fourth algorithm, FN-DSA, also used for digital signatures, that is expected to be released in the next year.

The energy transition is a major challenge, requiring not only sustainable power generation but also reliable electricity distribution. 🌱⚡ Any power interruption can disrupt public life, making critical infrastructure availability crucial. Effective security measures, processes, and products are essential to eliminate vulnerabilities and ensure uninterrupted operation. Network technology for use in substations must therefore meet particularly high requirements: Powerful Platform: In substations, the network technology must process a significant amount of data in real-time. Managed switches with high bandwidth, precise time synchronization, and low latency are essential for communication. This is because the management of installed network components quickly becomes extensive and complex. IEC 61850 and IEEE 1613: Compliance with these standards ensures products meet critical infrastructure requirements, including high electromagnetic immunity, a wide temperature range from -40°C to +85°C, and extreme shock and vibration resistance. Cyberattack Protection: In a networked world, cyberattack protection is vital. Network technology must have extensive security features like VLANs for network segmentation, user authentication, and syslog support for reliable monitoring and protection. Let's work together towards a sustainable future in which the energy supply is not only green, but also secure 🔐.  For more information on this topic, visit our website: https://lnkd.in/ewyginNi #cybersecurity #criticalInfrastructure #IEC61850 #industrialcommunication

“I just needed help with a SQL query.” That is what a junior dev said after copying and pasting 200+ real customer records emails, phone numbers, and purchase history straight into ChatGPT. And the only reason anyone caught it was because a security lead walked past his screen. From a security engineering lens, that is not a tiny mistake. That is a textbook data leak to an unapproved third party. Dear junior engineers, if you do not want to end your career over an unintentional security and privacy breach, please understand this: An AI chat window is not your notebook. It is an external system, owned and logged by someone else. Treat it exactly like you would treat sending data to any random vendor. “Just one paste” can easily qualify as: - Unauthorized disclosure of customer data - Violation of internal policy and NDA - Reportable incident under GDPR, HIPAA, PCI, or local privacy law Intent does not matter to the regulator. Impact does. But here, the real problem is bigger than “they used ChatGPT” When a junior can copy live customer records into a browser, the gaps started long before AI. It usually means: - Devs have direct access to production data - No proper dev or test environment with fake data - Weak data classification and DLP controls - No clear AI usage policy, or it exists only as a PDF nobody reads Blocking one website will not fix that. We need a deeper approach. If you are building a serious security program around LLMs, here is the practical pattern I would recommend. 1. Provide a safe, approved AI option - Give people an org owned option: enterprise ChatGPT, Claude, Copilot, or an internal model behind SSO and RBAC. - Tell them clearly: confidential data belongs only in these tools. Otherwise they will use public ones anyway. 2. Block or tightly gate public LLMs - Use CASB or secure browser or proxy to detect and control access to public AI tools. - Use always on VPN so usage from home is still covered. - At minimum, block corporate accounts from using personal AI accounts for work data. 3. Enforce least privilege and environment separation - Junior devs should not touch live customer data. - Limit who can query real PII and under which scenarios. 4. Data classification that AI actually respects - Label sensitive tables, fields, and documents. - AI agents must only see what the logged in user is allowed to see. 5. Clear policy and training - Give concrete examples of what must never be pasted into public AI. - Make AI usage policy part of onboarding, refresh it often, and hold managers responsible. AI is an incredible tool. I use it daily. You should too. It will make you faster at debugging, learning, and designing systems. But “I did not know” will not protect you when your prompt shows up in an incident report. Follow saed ‎for more & subscribe to the newsletter: https://lnkd.in/eD7hgbnk I am now on Instagram: instagram.com/saedctl say hello, DMs are open