Engineering Standards And Compliance

I asked 25 contractors a simple question: If low‑carbon concrete costs the same, why aren’t we pouring it everywhere? Turns out… ...we can start today. Most projects tested switched to low‑carbon mixes with no cost increase, or a tiny 5% bump, while cutting tens of thousands of tonnes of emissions across 109 pilots. That’s not a moonshot. That’s procurement with a pulse. On big jobs, costs trended lower thanks to scale. Performance concerns were manageable. Access wasn’t the blocker. Old habits were. For leaders in the built environment and real estate, this is the rare win where sustainability, whole‑life carbon, and business performance align. We reduce embodied carbon now. We future‑proof assets against regulation. We open doors to sustainable finance. And we don’t blow the budget. This is not a PR exercise. It’s a margin play with a climate tailwind. Concrete with up to 32% less carbon is available at market rates or close to it. In one multimillion‑dollar project, the “green” premium was under $2,000. If that’s a deal‑breaker, the problem isn’t the concrete. What to do next: ↳ Tell your teams to spec below‑baseline mixes as the default. ↳ Bid with suppliers who provide EPDs and proven low‑carbon options. ↳ Track embodied carbon alongside cost and schedule—every job, every pour. ↳ Start with foundations, slabs, and parking structures, then scale. We’ve waited long enough for perfection. “Good, available, low‑carbon” just lapped “someday tech.” Pour the future now. 🔔 TL;DR: Low‑carbon concrete at no cost or ~5% is here. Cut emissions, meet codes, unlock capital, protect margins. If your projects aren’t using it, that’s a choice, not a constraint. Access the report here: https://lnkd.in/gd_NextA #LowCarbon #Concrete #Construction #RealEstate #BuiltEnvironment #Decarbonization #SustainableFinance #WholeLifeCarbon #CircularEconomy #ClimateAdaptation #CircularEconomy #Sustainability

ISO vs ASME Standards — What’s the Real Difference? In mechanical design and engineering drawings, two major standards dominate globally: 👉 International Organization for Standardization (ISO) 👉 American Society of Mechanical Engineers (ASME) Understanding the difference is not just theory — it directly impacts manufacturing, inspection, and global collaboration. 🌍 ISO (International Organization for Standardization) ✔ Widely used in Europe, Asia, and globally ✔ Based on metric system (mm) ✔ Focus on functional requirements and clarity ✔ Common standards: ISO 1101 (GD&T), ISO 2768 (general tolerances) 👉 Typical use: Automotive, general machinery, global OEMs ASME (American Society of Mechanical Engineers) ✔ Widely used in USA and US-based companies ✔ Uses inch system (primarily) ✔ Highly detailed rule-based GD&T system ✔ Key standard: ASME Y14.5 👉 Typical use: Aerospace, oil & gas, heavy engineering (US clients) ⚠️ Why This Matters 🔹 Mixing ISO & ASME in one drawing = Manufacturing errors 🔹 Wrong interpretation = Tolerance stack-up issues 🔹 Global projects demand clear standard alignment 💡 Pro Tip (From Industry Experience) If you're working with international teams or suppliers: ✔ Always mention the standard clearly in the drawing ✔ Avoid mixing symbols without understanding differences ✔ Train teams on both standards for better collaboration 🔧 Final Thought Standards are not just guidelines — they are the language of engineering. #MechanicalDesign #GDnT #EngineeringStandards #ISO #ASME #DesignEngineering #Manufacturing #CAD

🔍 Saudi Aramco vs ADNOC vs QatarEnergy A Comprehensive Comparison of Engineering Standards Shaping the World's Largest Energy Projects Behind every world-class refinery, LNG terminal, offshore platform, and petrochemical complex lies a robust engineering standards framework that ensures safety, reliability, quality, and long-term operational excellence. Among the most respected owner standards in the global energy industry are those developed by Saudi Aramco, ADNOC, and QatarEnergy. While all three organizations are built upon internationally recognized codes such as ASME, API, ISO, IEC, NFPA, ASTM, and AWS, each has developed its own engineering philosophy to address unique operational, environmental & business requirements. 🇸🇦 Saudi Aramco Known for one of the industry's most comprehensive owner engineering systems, Saudi Aramco's standards place strong emphasis on: ✔ Asset integrity throughout the lifecycle ✔ Standardization across global projects ✔ Extensive material and vendor qualification ✔ Rigorous quality assurance and inspection ✔ Detailed engineering documentation ✔ Conservative design philosophy for long-term reliability 🇦🇪 ADNOC ADNOC combines international best practices with company-specific engineering requirements, focusing on: ✔ Engineering flexibility with strong governance ✔ Risk-based engineering and asset management ✔ Digital transformation and intelligent operations ✔ Efficient EPC project execution ✔ High-quality procurement and supplier qualification ✔ Sustainable and future-ready infrastructure 🇶🇦 QatarEnergy Driven by decades of experience in world-scale LNG developments, QatarEnergy emphasizes: ✔ Operational reliability and maintainability ✔ Performance-based engineering ✔ Project-specific technical requirements ✔ International code compliance ✔ Efficient lifecycle management ✔ High availability for critical energy infrastructure What You'll Find in This Infographic ✅ Engineering standards hierarchy ✅ Design philosophy comparison ✅ Major discipline standards ✅ Materials and welding requirements ✅ Vendor qualification processes ✅ Inspection & testing requirements ✅ Documentation deliverables ✅ Digital engineering initiatives ✅ Process safety and HSE practices ✅ Project execution approach ✅ International code integration 🔑 Key Takeaway Proprietary standards, one common goal: ✅ Safe operations ✅ Reliable performance ✅ Efficient execution ✅ Sustainable, long-life assets Understanding these standards helps ensure: ✔ Technical compliance ✔ Better quality ✔ Reduced project risk ✔ Successful project delivery Essential knowledge for professionals across Oil & Gas, LNG, Petrochemicals & Energy Transition sectors. ✨ Found this helpful? 🔔 Follow me Krishna Nand Ojha, and my mentor Govind Tiwari, PhD, CQP FCQI for insights on Quality Management, Continuous Improvement & Strategic Leadership Let’s grow and lead the quality revolution together! 🌟 #OilAndGas #EngineeringStandards #SaudiAramco #ADNOC #QatarEnergy

Scope 3 is broken... and other things you're afraid to tell your CEO Scope 3 emissions account for 75%-99% of corporate carbon footprints, mostly from upstream supply chains. Our current Scope 3 EIO methods were built for check-the-box compliance reporting, not driving reductions. EIO models are calculated by multiplying your supplier spend times a global or regional industry-wide average emission factor. That cannot account for any actual decarbonization action your supplier takes, not even in theory. Put another way, if a large chunk of your suppliers lowered their corporate emissions by 10% this year, your Scope 3 emissions _would not decrease_. At all. Let that sink in. Deep down, we all know this, that's just the part we never say out loud, and we carry on in collective cognitive dissonance, with vague murmurings about "data challenges". We need to flip Scope 3 on its head. Embodied carbon at the product level should be treated as an objectively measured product specification; so that carbon performance is treated just like other critical product specs; like weight, size, delivery volumes, speed, cost, etc. Imagine if we treated any other performance spec like this... you go to buy a laptop, and when you ask how much storage the laptop has, the seller advises you to build your own science team to _estimate_ the laptop's storage based on global industry averages. Does this sound bonkers to you? It is. But we've all been doing this for so long that we’ve managed to persuade ourselves that it’s completely normal. And we wonder why we've made virtually no global progress reducing the Scope of emissions that dwarfs all others. OK, so how do we change this? How about we start treating embodied carbon as a performance spec that the _seller_ is responsible for calculating and eliminating? That's exactly how every other performance spec works. We have a data standard in ISO 14067, and an emergent standardized methodology in the WBCSD – World Business Council for Sustainable Development PACT framework. And there are a wide and growing variety of Product Carbon Footprint (PCF) providers that use #AI and process-based input data for manufacturing and transportation, to calculate PCFs rapidly, cost-effectively, and at scale. This approach eliminates the need for theoretical abatement cost curves, because now your suppliers can price carbon for you directly when they quote you $X change in price for Y-kg carbon reduction per unit. Procurement can do what it does best, negotiate based on objective performance criteria; and suppliers can do what they do best, engineer products and services objectively optimized to what their buyers want. We all know it's time to fix Scope 3. What specific actions can we take today to ensure our Scope 3 emissions reduction efforts lead to actual decarbonization? Image credit: DeepAI . . . #SustainabilityLeader #Scope3 #GHGemissions #supplychain #energytransition

ASME and ISO are the two most widely used drafting standards in mechanical design, and while they share the same goal of ensuring clarity and consistency in engineering documentation, they differ in conventions, presentation, and regional adoption. ASME standards (primarily ASME Y14 series) are commonly used in North America, especially in the United States and Canada, while ISO standards (ISO 128, ISO 2768, ISO 5459, etc.) are the global benchmark used across Europe, Asia, and many multinational companies. One of the most noticeable differences lies in projection methods. ASME uses third-angle projection, where the object is imagined behind the projection plane, while ISO uses first-angle projection, where the object is placed in front of the projection plane. This affects the placement of views on the drawing sheet — for example, in ASME, the top view is above the front view, whereas in ISO, it’s below. This distinction can cause confusion if not clearly indicated on the title block or projection symbol. Another key difference involves dimensioning and tolerancing. ASME Y14.5 defines Geometric Dimensioning and Tolerancing (GD&T) in a way that emphasizes functional relationships and manufacturability, whereas ISO’s GD&T (based on ISO 1101 and related standards) follows slightly different symbol definitions, modifiers, and datum referencing principles. Although the intent is similar, the details and interpretations can vary, so it’s critical to remain consistent within a project or company. In short, ASME and ISO are both robust, professional standards — but they are not interchangeable. The choice between them typically depends on the target manufacturing region, customer requirements, and established company practices. Clear communication of which standard is being used ensures accuracy, compatibility, and a smooth transition from design to production.

Key comminution trends that will decide whether your mine controls energy costs or loses profitability. With energy costs rising and ore grades declining, the old approach of grinding everything to dust and hoping for the best is quickly turning into a financial liability. Some mines are already optimizing their circuits and slashing power costs.   Others will soon realize the price of inefficiency is about to go up. Let’s break down key trends:   1. Pre-concentration & coarse particle flotation. Mines have long crushed everything, wasting energy on low-value material. New sorting tech removes waste upfront, rejecting 30% of uneconomic ore before milling. The result? Lower energy use, higher throughput—without costly expansions. 2. High-intensity blasting. Smarter blasting beats inefficient grinding. Some mines boost throughput 28% with high-intensity blasting. Break the ore properly at the start = less grinding = lower energy costs. Comminution starts in the pit, not the plant. 3. Dry grinding. Comminution is one of the largest water consumers in mining. Yet few talk about how grinding circuits contribute to this problem. Emerging solutions like HPGR (high-pressure grinding rolls), VRM (vertical roller mill) and air classification are cutting water use while maintaining high recovery rates. 4. The end of one-size-fits-all circuits. The traditional SAG-ball mill-cyclone circuit has been the industry standard for decades. But as energy prices skyrocket, mines are rethinking flowsheets and using: - HPGR-ball mill combinations for better energy efficiency  - Single-stage AG/SAG circuits with pre-crushing to simplify flowsheets  - Autogenous & pebble milling to reduce reliance on grinding media The goal? Extracting maximum value at the lowest possible energy input. 5. AI & real-time process optimization: no more guesswork Comminution is moving from gut feeling to AI-driven control. AI-driven process control systems are now: - Adjusting feed rates, mill speeds, and power inputs in real-time - Eliminating inefficiencies and keeping operations at peak performance - Maximizing throughput without human error In 5 years, top operators will let AI optimize comminution automatically.   6. Grade engineering. Instead of grinding everything, Grade Engineering® optimizes ore processing by: • Blasting for natural size separation • Sorting by actual grade, not assumptions • Using sensor-based bulk sorting to feed only valuable ore to the mill The result? Higher recovery, lower energy use, better margins.   Mines that optimize comminution will be keeping costs low and margins high. Mines ignoring it will be fighting rising energy costs with circuits designed for a past economic reality.   Process smarter – or pay the price for inefficiency.   And it all starts with understanding your ore.   Real-time ore hardness data impacts blasting strategies, mill performance, and overall process efficiency. Want better comminution data? Let’s talk.

DevSecOps shifted security left. But most GRC practices are still standing on the sidelines. While engineering teams are automating everything. From unit tests to container scans to deployment approvals. GRC professionals are still asking for Jira tickets and a “list of changes.” Let’s be honest: that doesn’t work anymore. Modern product teams are shipping hundreds, sometimes thousands, of changes a day. A spreadsheet of changes isn’t scalable. It’s not accurate. And it doesn’t reflect the pace or reality of today’s environments. Here’s the mindset shift: - It’s not about tracking every change. - It’s about trusting the pipeline. What are the processes, controls, and configurations in place to make sure that every change that gets to production meets the organization’s security and risk standards? GRC Engineers should be asking questions like: – What security scans run in our CI/CD pipeline? – Where is that data stored? Can we query it? – Are there manual approvals? Who signs off? – Can we auto-tag and log this data for audit use? – Can this feed into a system like AWS Security Hub or Audit Manager or our GRC tool? We need to stop building our compliance programs around static point-in-time checks. The future of GRC is continuous. When you align your evidence collection with the CI/CD pipeline: – Engineers aren’t disrupted by audit requests – Risk teams get a real-time picture of control health – Compliance becomes a natural byproduct of secure engineering That’s the power of GRC Engineering. I go deep on this in Chapter 9 of my book, GRC Engineering for AWS. Showing a case study on how to ingest scan data, approvals, and artifacts directly into AWS native services for validation, triage, and audit reporting. CI/CD is where security shifted. GRC needs to catch up and GRC Engineers are the ones who can lead the way. #GRCEngineering

“The main change is the Treasury discarded a bright-line 5% test for starting construction of solar projects over 1.5 megawatts and all wind projects in favor of a less clear facts-and-circumstances approach of looking at the amount of physical work done by a factory on custom-made equipment for the project or at the project site.” “The new construction-start rules apply to wind and solar projects on which construction starts on or after September 2, giving developers a short window to try to tidy up any construction-start efforts they have currently underway. Developers starting construction of new solar or wind projects during the period September 2, 2025 through July 4, 2026 will have four years to finish after the year construction starts. Thus, a project on which construction starts in early 2026 will have until the end of 2030 to finish construction.” “Distributed solar developers will still be able to use the 5% test on projects with nameplate capacities of up to 1.5 megawatts. The capacity will be measured at each inverter string. Thus, a large project could qualify in theory, but the IRS will treat multiple inverter strings as a single project if they have "integrated operations." (Strings placed in service in separate tax years are not aggregated.)”

You're Using GRC Engineering to Avoid the Hard Work Your evidence collection script works perfectly. It pulls data from three teams who each define "access review" differently. Congratulations. You've automated chaos at scale. Month 1: "Let's automate quarterly access reviews!" Month 2: Build script, pulls from 5 systems Month 3: Discover each system has different field names, workflows, definitions Month 6: "Why doesn't anyone trust our automation?" Because you automated the mess, not the process. Why we do this: Writing Python is easier than having seventeen conversations with stakeholders who can't agree on what "privileged access" means. Debugging APIs is more comfortable than facilitating the political negotiation between teams who've done things differently for years. Building scripts feels like progress. Standardising processes feels like... meetings. But here's the problem: 3 teams × 4 definitions of "privileged access" × 2 workflows × 5 evidence formats = 120 combinations Multiply by 2.4 cloud providers (enterprise average) = 288 edge cases your script handles. You just turned a process problem into a distributed systems problem. GRC Engineering became the excuse to avoid the hard work. You're building the pipes before you've agreed what flows through them Before writing code, answer: - What does this control actually mean? - Who performs it? (One person or seventeen with different interpretations?) - What does success look like? - Is evidence naturally generated or manufactured for compliance? These require conversations, consensus-building, and coordination. Not code. The blueprint: 1. Define the control (hard: requires alignment) ↓ 2. Document the SOP (hard: exposes disagreements) ↓ 3. Train for consistency (hard: cultural change) ↓ 4. Validate across teams (hard: accountability) ↓ 5. THEN automate (easy: it's just code now) Most teams skip to step 5 because it's the only step that doesn't require stakeholder management. Real example before standardisation: Team A: Quarterly reviews, manager approval, spreadsheets Team B: Monthly reviews, VP approval, Jira Team C: "We email the list around" Your script pulls from all three. What did you automate? Three different processes that share a name. After standardisation: Same cadence, same workflow, same format, same success criteria everywhere. NOW automation works. You're replicating consistency, not reconciling chaos. One thing to keep in mind: The hard part of GRC Engineering isn't the engineering. It's the coordination, consensus-building, and process design that makes automation possible. Code is the easy bit. Humans are the hard bit. Automation amplifies what you have: Chaos → Chaos at scale Inconsistency → Inconsistent data faster Solid process → Sustainable automation Fix the process. Then automate it. #GRCEngineering #ProcessMaturity #Standardisation

Understanding the carbon footprint of products is key to shaping effective climate policies, including and importantly in a global trade friendly way. Earlier this week at #COP29, I presented the Inclusive Forum on Carbon Mitigation Approaches’ (#IFCMA) new report tackling challenges in computing carbon intensity metrics and their application in trade-related climate policies. Carbon intensity metrics play an important role in assessing emissions associated with the volume of production of specific goods or sectors and have many potential applications. These metrics provide insights into progress on decarbonisation and are central to a growing range of trade-related climate policies, including green product standards and border carbon adjustments. The IFCMA’s analysis emphasises the need to address data gaps, prevent fragmentation in global supply chains and provide targeted support to SMEs and firms in developing countries. Our report provides a better shared understanding of these challenges and how they can be addressed to help boost international markets for low-carbon goods while ensuring fair and open trade to promote an inclusive, cost-effective transition. Currently with 59 members and the engagement of many more economies, the IFCMA can play a key role in bringing countries together to support international cooperation on the computation and use of carbon intensity metrics. Read the report here: https://oe.cd/5Ma | #OECDatCOP29