{"id":72973,"date":"2026-04-17T04:33:47","date_gmt":"2026-04-17T08:33:47","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/simcenter\/?p=72973"},"modified":"2026-04-22T06:22:03","modified_gmt":"2026-04-22T10:22:03","slug":"simulation-business-case-chapter3","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/simcenter\/simulation-business-case-chapter3\/","title":{"rendered":"Lost in translation: How one engineer learned to speak CFO – Chapter 3"},"content":{"rendered":"\n
\n
Synopsis<\/summary>\n

Building a simulation business case<\/strong> isn\u2019t only about having the best technology, it\u2019s about explaining its value in a language decision\u2011makers understand. Marcus wasn’t trying to change his company. He just wanted better tools to do his job. A simulation platform that could model the complex thermal-electrical interactions his current software couldn’t handle. The kind of technology that would turn weeks of guesswork into days of certainty.<\/p>\n\n\n\n

He had the technical proof. He had the vendor demos. He even had a business case, at least he thought he had. What he didn’t have was the ability to speak CFO.<\/p>\n\n\n\n

This story follows an engineer who discovered that translating simulation capabilities into financial outcomes like ROI, NPV, and payback period is what turns promising ideas into approved investments.<\/p>\n<\/details>\n\n\n\n

This is a fictional story, with fictional characters working for a fictional company, <\/strong>but it’s built on real experiences. From engineers in various industries including automotive, aerospace, marine, heavy equipment and industrial machinery, and dozens of others who’ve fought the same battle. Engineers who learned that speaking two languages fluently, technical and financial, isn’t selling out.<\/strong><\/p>\n\n\n\n

<\/div>\n\n\n\n

This is chapter 3 in the series Lost in translation: How one engineer learned to speak CFO<\/strong>.
Read here chapter 1<\/a> and chapter 2<\/a><\/em>.<\/p>\n\n\n\n

Chapter 3: The Crisis<\/h1>\n\n\n\n

The third presentation lasted forty-five minutes.<\/p>\n\n\n\n

Marcus walked through five case studies now, he’d added one more in the final days, a vibration analysis that had shown even more dramatic results. He presented data from thirteen engineers across four departments. Elena had built financial projections that extended five years, included sensitivity analyses, and accounted for risks the CFO hadn’t even asked about.<\/p>\n\n\n\n

The NPV: \u20ac694,000. IRR: 264%. Payback period: 4.4 months.<\/p>\n\n\n\n

When he finished, the room was silent.<\/p>\n\n\n\n

The CFO scrolled through the appendix, checking assumptions, testing numbers. Marcus’s engineering director sat beside him, nodding occasionally at questions. Elena had a small smile that she was trying to hide.<\/p>\n\n\n\n

Finally, the CFO looked up. “This is thorough work. You’ve addressed every concern I raised.”<\/p>\n\n\n\n

Marcus waited. He’d learned not to celebrate too early.<\/p>\n\n\n\n

“I’m recommending this to the investment committee,” she continued. “With one condition.”<\/p>\n\n\n\n

“Anything.”<\/p>\n\n\n\n

“You present it. Not me, not your director. You.” She closed her laptop. “You built this case. You ran the experiments. You convinced a dozen engineers to try something new. The committee needs to see that this isn’t a finance initiative or an engineering wish list. It’s a business improvement with an engineer who understands both the technical value and the financial impact.”<\/p>\n\n\n\n

Marcus felt his stomach drop. “I’ve never presented to the investment committee.”<\/p>\n\n\n\n

“I know. That’s why you’re doing it.” She stood. “You have three weeks. Elena will help you prepare. Don’t make me regret this recommendation.”<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n
<\/div>\n\n\n\n

The investment committee met monthly to review capital expenditure requests over \u20ac25,000. Marcus had heard stories about engineers who’d been torn apart for weak assumptions, managers who’d had projects killed in the first five minutes, one memorable case where someone’s entire presentation was dismissed because they couldn’t answer a basic question about market demand.<\/p>\n\n\n\n

Elena tried to be reassuring. “They’re not trying to reject projects. They’re trying to invest company money wisely. Show them you’ve thought it through, and they’ll listen.”<\/p>\n\n\n\n

“What if they ask something I don’t know?”<\/p>\n\n\n\n

“Then you say ‘I don’t know’ and explain how you’d find out.” She pulled up a presentation template. “Confidence without arrogance. Data without drowning them. Story without fluff. You can do this.”<\/p>\n\n\n\n

Marcus spent the next two weeks preparing. He practiced the presentation on Stefan, on Elena, on his director, on his wife. He built backup slides for every question he could imagine. He memorized the financial metrics until he could recite them in his sleep.<\/p>\n\n\n\n

Three days before the committee meeting, his director called him into his office.<\/p>\n\n\n\n

“We have a problem.”<\/p>\n\n\n\n

Marcus felt ice in his chest. “With the business case?”<\/p>\n\n\n\n

“With the project it’s based on.” His director pulled up an email. “The battery thermal management analysis, the one you used as your primary case study. The physical prototype just came back from testing. The results don’t match your simulation.”<\/p>\n\n\n\n

\"\"<\/figure>
\n

Marcus stared at the test data. His simulation had predicted a maximum cell temperature of 42\u00b0C under peak load. The physical test showed 51\u00b0C.<\/p>\n\n\n\n

Nine degrees. In thermal management, that was a canyon.<\/p>\n\n\n\n

“There must be an error in the test setup,” Marcus said, but his voice lacked conviction.<\/p>\n\n\n\n

“They ran it three times. Same result.” His director’s face was grim. “Marcus, your entire business case is built on simulation accuracy. If the committee finds out your flagship example was off by 20%…”<\/p>\n\n\n\n

“I’ll rerun the model. Check my assumptions. There has to be an explanation.”<\/p>\n\n\n\n

“You have three days.”<\/p>\n\n\n\n

\n

“If the committee finds out your flagship example was off by 20%…”<\/p>\nEngineering Director<\/cite><\/blockquote>\n<\/div><\/div>\n\n\n\n

<\/div>\n\n\n\n

Marcus didn’t go home that night. He rebuilt the thermal model from scratch, checking every parameter, every boundary condition, every material property. The simulation still predicted 42\u00b0C.


<\/p>\n\n\n\n

At 2 AM, he called the test engineer who’d run the physical validation.<\/p>\n\n\n\n

“The cooling flow rate,” Marcus asked. “What was the actual measured value?”<\/p>\n\n\n\n

“Uh, hold on…” Papers rustling. “2.1 liters per minute.”<\/p>\n\n\n\n

Marcus’s blood went cold. “The spec calls for 2.5.”<\/p>\n\n\n\n

“Yeah, we had some issues with the pump. Couldn’t hit the full flow rate with the prototype setup. Didn’t think it would matter that much.”<\/p>\n\n\n\n

Marcus ran a new simulation with the reduced flow rate. Maximum cell temperature: 50.8\u00b0C.<\/p>\n\n\n\n

He wanted to scream. He wanted to laugh. The simulation had been right all along! It had just been answering a different question than the test was asking.<\/p>\n\n\n\n

But that didn’t solve his problem. His business case claimed the simulation could predict real-world behavior accurately. Now he had test data that appeared to contradict it, and three days to explain why to a committee that wouldn’t care about the nuances of pump flow rates.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Stefan found him in the lab the next morning, surrounded by printouts and empty coffee cups.<\/p>\n\n\n\n




“You look terrible.”<\/p>\n\n\n\n

“The thermal test results came back. They don’t match the simulation.”<\/p>\n\n\n\n

“I heard.” Stefan sat down. “Also heard you figured out why.”<\/p>\n\n\n\n

“Doesn’t matter. The committee will see ‘predicted 42, measured 51’ and kill the whole business case.” Marcus rubbed his eyes. “Three months of work. Thirteen engineers convinced to try something new. All dead because of a pump that couldn’t hit spec.”<\/p>\n\n\n\n

“So explain it to them.”<\/p>\n\n\n\n

“They won’t care about the technical details. They’ll just see that the simulation was wrong.”<\/p>\n\n\n\n

\"\"<\/figure>
\n

Stefan was quiet for a moment. “Was it wrong?”<\/p>\n\n\n\n

“What?”<\/p>\n\n\n\n

“The simulation. Was it wrong, or was it right about the wrong thing?”<\/p>\n\n\n\n

Marcus looked at the data again. “It was… right. The test setup was different from the simulation conditions.”<\/p>\n\n\n\n

“Then that’s not a simulation failure. That’s a validation of why you need better simulation tools.” Stefan leaned forward. “Think about it. You caught a 20% deviation between predicted and measured results. How? Because you had a detailed model that let you trace back to the root cause. Could you have done that with your old tools?”<\/p>\n\n\n\n

Marcus thought about the separate thermal and electrical models, the manual iteration, the simplified assumptions. “No. We wouldn’t have had the fidelity to identify the flow rate as the issue.”<\/p>\n\n\n\n

“So what looks like a failure is actually proof of concept. The simulation was accurate enough to diagnose a test setup problem.” Stefan stood. “That’s your story. Not ‘my simulation was perfect.’ But ‘my simulation was good enough to find the truth.’<\/p>\n<\/div><\/div>\n\n\n\n

Marcus rewrote his presentation. Instead of hiding the thermal test discrepancy, he led with it.<\/p>\n\n\n\n

He showed the predicted results: 42\u00b0C. The measured results: 51\u00b0C. The committee members shifted in their seats. Here it comes, the collapse.<\/p>\n\n\n\n

Then he showed the investigation. The flow rate deviation. The corrected simulation. The match within 2%.<\/p>\n\n\n\n

“This is why we need better simulation tools,” Marcus said. “Not because they’re always perfect. But because they’re accurate enough to trust, detailed enough to diagnose problems, and fast enough to iterate. With our old approach, we would have seen this 9-degree discrepancy and spent weeks rebuilding physical prototypes trying to fix it. Instead, we spent two hours tracing it to a pump specification issue.”<\/p>\n\n\n\n

The committee chair, a stern woman Marcus had never met, leaned forward. “You’re telling us your simulation failed, and that’s supposed to convince us to buy the software?”<\/p>\n\n\n\n

“I’m telling you the simulation revealed the truth faster and cheaper than any alternative method.” Marcus pulled up the cost comparison. “The traditional approach would have required another prototype iteration: \u20ac12,000 and four weeks. The simulation-based investigation cost us two engineering hours and found the root cause immediately.”<\/p>\n\n\n\n

“And if the simulation had actually been wrong? If it wasn’t a test setup issue?”<\/p>\n\n\n\n

Marcus took a breath. “Then we would have learned something about our modeling assumptions and improved them. That’s the point of validation. But we can only validate what we can model with sufficient detail. Our current tools don’t give us that capability.”<\/p>\n\n\n\n

The room was silent. Marcus couldn’t read the faces around the table.<\/p>\n\n\n\n

The committee chair made a note. “Continue with the rest of your business case.”<\/p>\n\n\n\n

\n

“…and that’s supposed to convince us to buy the software?”<\/p>\nCommittee chair<\/cite><\/blockquote>\n\n\n\n

<\/div>\n\n\n\n

The presentation took an hour. They asked about training costs, software maintenance, scalability to other departments, integration with existing tools. Marcus answered each question, sometimes confidently, twice with “I don’t know, but here’s how we’d find out.”


<\/p>\n\n\n\n

When he reached the financial summary, he walked them through the NPV calculation step by step, showed the IRR sensitivity analysis, explained why the 4.4-month payback period was achievable based on measured data from five different project types.<\/p>\n\n\n\n

When he finished, the committee chair thanked him and asked him to step outside while they deliberated.<\/p>\n\n\n\n

Marcus sat in the hallway, leg bouncing, checking his phone every thirty seconds. Elena had texted: You’ve got this.<\/em> His director: Well done in there.<\/em> Stefan: Told you the pump thing was a feature not a bug.<\/em><\/p>\n\n\n\n

After twenty minutes, the door opened.<\/p>\n\n\n\n

“Marcus, come back in.”<\/p>\n\n\n\n

He walked back to his seat, trying to read the room. Impossible.<\/p>\n\n\n\n

The committee chair spoke. “We’re approving your request.”<\/p>\n\n\n\n

Marcus felt a wave of relief.<\/p>\n\n\n\n

“With a modification.”<\/p>\n\n\n\n

The relief paused mid-wave.<\/p>\n\n\n\n

“Your business case projects \u20ac694,000 NPV based on department-wide adoption across multiple engineering disciplines. That’s compelling, but it’s also projection, not proof.” She pulled up his financial model. “We’re approving one license at \u20ac47,000, plus \u20ac8,000 for training. You have twelve months to demonstrate the utilization and savings you’ve projected. If the actual results support your business case, we’ll revisit expansion at that time.”<\/p>\n\n\n\n

Marcus’s mind raced. One license. Thirteen engineers had participated in the case studies. Five different project types. How was he supposed to\u2026<\/p>\n\n\n\n

“This isn’t a rejection,” the committee chair continued, reading his face. “It’s a staged investment. You’ve convinced us the technology has value. Now prove it scales. Show us the actual NPV after one year, not the projected NPV. If it’s anywhere close to your model, you’ll get the expansion budget.”<\/p>\n\n\n\n

She smiled, the first time he’d seen her smile. “You’ve done excellent work getting this far. Don’t let perfect be the enemy of good.”<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

Marcus walked out of the building into the afternoon sun, pulled out his phone, and called his wife.<\/p>\n\n\n\n

“They approved it,” he said when she answered.<\/p>\n\n\n\n

“That’s wonderful! I’m so proud of you.”<\/p>\n\n\n\n

“One license. Not three. I have to prove it works before they’ll expand.”<\/p>\n\n\n\n

“But they approved it. That’s what you’ve been working toward for three months.”<\/p>\n\n\n\n

Marcus sat on a bench. She was right. Three months ago, he’d been laughed out of a meeting for suggesting this. Now he had budget approval, a license, training funds, and a mandate to prove the concept.<\/p>\n\n\n\n

“You’re right,” he said. “This is a win.”<\/p>\n\n\n\n

“A big win. Come home. We’ll celebrate. Tomorrow you can figure out how to make one license work for thirteen engineers.”<\/p>\n\n\n\n

Marcus laughed. “That’s going to be a problem.”<\/p>\n\n\n\n

“That’s tomorrow’s problem. Tonight, just enjoy this.”<\/p>\n\n\n\n

\n
Continue with chapter 4<\/a><\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n

Ready to build your own simulation business case?<\/strong><\/h2>\n\n\n\n

Marcus’s journey mirrors real transformations happening across the automotive and manufacturing industries. Engineers at real companies like Certia<\/a>, Practicon<\/a>, and Cummins<\/a> have successfully navigated the path from technical vision to CFO approval, and are now reaping the competitive advantages of advanced simulation capabilities.<\/p>\n\n\n\n

<\/div> Read more simcenter-amesim reviews <\/a> <\/div>