PDX 2025 registration is live! Use code “WBH50” for $50 off registration!

Enter to win one of two free expo passes by filling out the survey.

Welcome to The Wave Engineering Newsletter, your weekly guide to the cutting edge of engineering. Whether you're a seasoned professional, an eager student, or simply curious about innovation, we’re here to inform, inspire, and connect.

More than just a newsletter, we tell the human stories behind the tech—spotlighting the innovators, dreamers, and changemakers shaping our world. Backed by insights from Pipeline Design & Engineering and the Being an Engineer Podcast, we deliver the latest advancements, impactful collaborations, and stories that redefine what’s possible.

Join the conversation at The Wave, where ideas spark, questions find answers, and the engineering community comes together to create the future. Engineering isn’t just about technology—it’s about people. Subscribe and ride the wave of innovation with us.

[Action Required]: Reply to this email answering the following question. Top, thought provoking comments will be featured on The Wave!

What's the biggest barrier preventing your team from moving to a design-first digital approach: technology limitations, cultural resistance, or budget constraints?

I’ve been browsing engineering jobs in the mechanical R&D and manufacturing in various industries. Once thing has stood out: a lot of companies want the typical Solidworks + extensive GD&T experience, but buried in these job descriptions was also mention of experience with coding languages preferred. The first time that I saw it, I figured it was a copy-paste error, but the more it pops up the more I realize that this is a fundamental shift in the industry. Hardware engineers that can code are no longer unicorns, but becoming the norm.

This pattern is hard to ignore. When I talked to professors at local engineering schools, they told me they're scrambling to add programming courses to mechanical engineering curricula because their graduates kept getting turned away from interviews for lacking software skills. Startup founders I know can't build hardware products anymore without significant firmware components, data collection systems, or IoT connectivity. Even traditional manufacturing companies want engineers who can automate their design workflows and build custom analysis tools.

It hit me that we're living through a fundamental shift in what it means to be a hardware engineer. The coolest innovations today - whether it's Tesla's self-updating cars, SpaceX's reusable rockets, or medical devices that learn from patient data - all exist at the intersection of atoms and bits. Pure hardware knowledge isn't enough anymore, but neither is pure software expertise. The future belongs to engineers who can speak both languages fluently.

This isn't just about adding a programming language to your resume. It's about understanding how software is reshaping the entire hardware development process, from initial design through manufacturing and into the field. Over the next four weeks, we're going to explore this convergence from a hardware engineer's perspective - not how to become a software developer, but how to remain a great hardware engineer in a world where the two domains are inseparably linked.

In my first job a decade ago, I worked with an engineer who specialized in CFD simulations for medical devices. Ignorant and freshly out of college, I was mezmorized by what he was able to accomplish through his models. He specialized in modeling hemolysis - red blood cell damage - in medical device blood pumps. He'd make the tiniest adjustments to his digital model, tweaking fluid velocities or impeller blades by a single degree. Then he'd run his simulation overnight, the output data informing our prototyping efforts.

The crazy part? His digital models were almost always exactly right in predicting the hemolysis our prototype would cause when we built physical prototypes. I never heard the term 'digital twin' till recently, but I'm realizing how impactful simulations have become and how much trust digital data is gaining in every industry.

Today, it is well documented that Formula 1 teams run millions of CFD simulations between race weekends, optimizing aerodynamics in virtual wind tunnels. The simulations never sleep so these digital spaces are iterating and evolving these cars faster than physics allows for in the real world.

This transformation extends far beyond specialized simulations. Digital twins aren't just fancy 3D models or monitoring dashboards. The global digital twin market is projected to grow from $17.73 billion in 2024 to $259.32 billion by 2032, exhibiting a CAGR of 40.1%. But more importantly, they're fundamentally changing how we approach engineering problems across every industry.

Consider how SpaceX has revolutionized rocket engine development. The journey from Raptor 1 to Raptor 3 tells the entire story of digital-first engineering. Raptor 3 achieves 51% more thrust compared to Raptor 1 while being 36% lighter. What makes this remarkable isn't just the performance gains-it's that SpaceX engineers have been able to move many external parts inward, consolidating and simplifying the design through extensive digital modeling and additive manufacturing. They're not just improving engines; they're reimagining what's possible when digital simulation drives physical design.

This represents a fundamental shift in engineering workflow. Traditional approaches followed a costly cycle: Design → Build → Test → Fix → Redesign → Build again. Digital twin methodologies have flipped this entirely: Simulate → Validate → Optimize → Build once → Monitor → Improve. That fundamental shift saves more than time and money. It saves careers, companies, and in some cases, lives.

The aviation industry demonstrates this transformation at scale. Rolls-Royce-the airplane engine manufacturer, not the car company-has saved 22 million tons of carbon emissions through their digital twin platform. Let that sink in. Not through lighter materials or more efficient combustion, but through better information. Each of their engines generates about half a gigabyte of data per flight, feeding real-time analytics that predict maintenance needs before failure occurs.

Their platform has helped extend the time between maintenance for some engines by up to 50%, dramatically reducing inventory costs and eliminating unnecessary downtime. Instead of following generic maintenance schedules, they treat each engine as an individual with its own operating history and environmental exposure. The digital twin knows if an engine flew through sandstorms over Qatar or smooth air over the Atlantic. It tracks pilot behavior, understands loading patterns, and builds predictive models that get smarter with every flight hour.

This level of sophistication is enabled by an expanding ecosystem of digital twin technologies. Industrial giants like Ansys Twin Builder and Siemens PLM work alongside cloud platforms like Microsoft Azure Digital Twins and NVIDIA Omniverse. Recent collaborations like Schneider Electric and ETAP's AI Factory digital twin using NVIDIA Omniverse demonstrate integration of thermal, mechanical, networking, and electrical data for enhanced design and operations. These aren't separate tools anymore-they're becoming integrated platforms that speak the same language as your hardware.

But here's where most companies get it wrong. The reality check is that most implementations fail because teams confuse dashboards with twins. A real digital twin requires physics-based models that can predict behavior, not just visualize current state. The difference between a monitoring system and a digital twin is the difference between a rearview mirror and a crystal ball. You're not just watching what happened; you're seeing what will happen.

This distinction matters when building a business case. The path forward isn't about implementing enterprise-scale digital twin platforms on day one. Start with IoT sensors feeding cloud analytics. Identify your most expensive failure modes and build predictive models around those specific scenarios. ROI calculations for management are straightforward: compare the cost of unplanned downtime against the cost of predictive maintenance systems. Industries report up to 40% savings in maintenance costs through digital twin implementations.

The automotive industry shows the clearest model for this approach: design-first digital development followed by continuous learning from deployed assets. BMW Group plans to use digital twin technology in its new iFactory production lines for the upcoming 'Neue Klasse' electric vehicle series, implementing Digital Twins across its 31 production and assembly sites. They're not just building cars; they're building learning systems that get smarter with every vehicle produced.

Reflecting on that CFD engineer from my first job, I realize he taught me something I didn't understand at the time. He wasn't just running simulations-he was having conversations with physics. His digital models weren't approximations of reality; they were reality rendered in code, complete with all the messy complexities that make engineering actually work.

Ten years later, I finally get it. We've crossed a threshold where the digital representation of our hardware has become more reliable than our physical intuition. Your pump, engine, or circuit doesn't just have specifications anymore-it has a software soul that knows its own future better than you do.

The companies that understand this are already winning. They're not building better hardware through better materials or tighter tolerances. They're building better hardware through better information. They've learned to trust the simulation over the prototype, the model over the metal.

The rest are still building expensive prototypes, discovering flaws in week three, and wondering why they're always six months behind schedule. They're treating digital twins like fancy dashboards instead of crystal balls.

Your hardware has always had a soul. We just finally learned how to talk to it.

Engineering is about solving, innovating, and connecting ideas to make a difference. Progress is a collective effort and your curiosity is what drives it forward. Thank you for exploring the dynamic world of engineering with all of us at Pipeline Design & Engineering and The Wave.

If you found value in this newsletter, share it with a friend or colleague who might enjoy it too. Don’t forget to subscribe so you never miss a new perspective, idea, or breakthrough.

“Creativity is just connecting things. When you ask creative people how they did something, they feel a little guilty because they didn’t really do it, they just saw something. It seemed obvious to them after a while.” - Steve Jobs

In collaboration and creativity,
Brad Hirayama
Blueprinting tomorrow, today