{"id":12812,"date":"2025-09-17T17:21:00","date_gmt":"2025-09-17T21:21:00","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/?p=12812"},"modified":"2026-03-26T12:35:27","modified_gmt":"2026-03-26T16:35:27","slug":"more-perspectives-on-the-shift-left-and-the-comprehensive-digital-twin-with-mike-crist-and-scot-morrison-part-2-transcript","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/more-perspectives-on-the-shift-left-and-the-comprehensive-digital-twin-with-mike-crist-and-scot-morrison-part-2-transcript\/","title":{"rendered":"More Perspectives on the Shift-Left and the Comprehensive Digital Twin with Mike Crist and Scot Morrison \u2013 Part 2 \u2013 Transcript"},"content":{"rendered":"\n<p>The <a href=\"https:\/\/blogs.sw.siemens.com\/podcasts\/category\/transforming-industries-with-dale-tutt\/\">Industry Forward Podcast<\/a> continued with another three part series on the intricacies of shifting-left with the comprehensive Digital Twin.<\/p>\n\n\n\n<p>Dale and I will be talking with Mike Crist, Industry Strategist for Aerospace, Defense, and Transportation at Siemens Digital Industries Software, and, returning, Scot Morrison, Vice President of Shift-Left Software Product Management in the Hardware Assisted Verification Group at Siemens EDA. With Scot returning, the next three episodes are something of a companion to our previous conversation with Doug Burcicki and Scot. We will be getting a new perspective from Mike on some of the same topics as in that previous discussion, and covering some new topics around shifting left with the CDT.<\/p>\n\n\n\n<p>The second part of our conversation with Mike and Scot focuses on how controlling interfaces between systems and sub-systems can help manage complexity, the potential advantages of SysML V2, and the differences between &#8220;little&#8221; and &#8220;big&#8221; MBSE.<\/p>\n\n\n<div class=\"embed-megaphone\">\n<iframe loading=\"lazy\" frameborder=\"0\" height=\"200\" scrolling=\"no\" src=\"https:\/\/playlist.megaphone.fm?e=TLFIE1677730588\" width=\"100%\"><\/iframe>\n<\/div><!-- Megaphone -->\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Conor Peick<\/strong><\/p>\n\n\n\n<p>Hello and welcome in to the Industry Forward Podcast with Dale Tutt. My name is Conor Peick and I am a writer for Siemens Digital Industries Software\u2019s Thought Leadership team and your host for today\u2019s podcast.<\/p>\n\n\n\n<p><strong>Dale Tutt<\/strong><\/p>\n\n\n\n<p>And I\u2019m Dale Tutt, Vice President of the Industry Strategy Team at Siemens Digital Industries Software.<\/p>\n\n\n\n<p><strong>Conor Peick<\/strong><\/p>\n\n\n\n<p>So it\u2019s a new season of the Industry Forward Podcast. In this new series, we are going to be exploring the idea of shifting left with comprehensive digital twin and doing so with the help of several experts with decades of combined experience in automotive, aerospace, semiconductors, software and more.<\/p>\n\n\n\n<p>Today, Dale and I will be talking with Mike Crist, Industry Strategist for Aerospace, Defense, and Transportation at Siemens Digital Industries Software, and, returning, Scot Morrison, Vice President of Shift-Left Software Product Management in the Hardware Assisted Verification Group at Siemens EDA. We are doing something of a companion episode to our last conversation with Doug and Scot, now getting a new perspective from Mike on some of the same topics, and some new topics around shifting left with the CDT. We will revisit the major trends of the software-defined product revolution and how shifting-left can help. Then we will look at the power of systems engineering, a specific look at SysML V2, changing product requirements, and the benefits of virtual testing in the face of growing product complexity. Thanks again for joining us and please enjoy!<\/p>\n\n\n\n<p><strong>Dale Tutt<\/strong><\/p>\n\n\n\n<p>Mike, you know you&#8217;ve been heavily involved with systems engineering over the years as well and we&#8217;ve worked a lot on that. What are your, what are your thoughts?<\/p>\n\n\n\n<p><strong>Mike Crist<\/strong><\/p>\n\n\n\n<p>See, this is where I I&#8217;m gonna have to tell you what some of my philosophy is, because I think that there&#8217;s. No. One good answer, but philosophically I believe that controlling the interface boundaries. Really helps us to. Decompose that system. And decompose the understanding in a way that can be encapsulated. And once we get to that management at the interface boundaries. It effectively establishes a contract for both sides of those interfaces to comply with. And once we established that contract. If we also add in the functionality that&#8217;s expected to be exposed. Or interacted with at that contract boundary. Now we can start bringing in compatibility with hardware and with software and. Having a true understanding of those domains or anything else that interacts across that interface boundary. Now I say this is a philosophy because there&#8217;s probably multiple other ways to deal with that. And like Scott mentioned, this notion of the complexity. I&#8217;m working with the complex Systems Working group to really define what complex means and how to treat it within a system. And to determine whether or not you should deal with complexity in certain areas of the system. One of the things I like to I really like about the working group is the notion that a system itself is not wholly complex. A portion of the system may be complex. There may be many portions of the system that are complex. But if you don&#8217;t treat the complexity. And understand and expect it. Then it may effectively infect other parts of the system to produce unexpected or emergent behavior. So by looking at these interface boundaries and then attempting to control at the interface the unexpectedness within that portion of the system. We now get to a point where we can have. Effective. Methods. Of encapsulating and treating complexity that doesn&#8217;t continue to propagate and run. Rampant through the system.<\/p>\n\n\n\n<p><strong>Conor Peick<\/strong><\/p>\n\n\n\n<p>That&#8217;s a. That&#8217;s a really fascinating perspective that I don&#8217;t think we&#8217;ve heard quite yet, but I love it. I mean, it&#8217;s a really interesting way to look at the problem. I don&#8217;t know that I&#8217;ve ever heard someone describe complexity as almost being like an infection that can spread to other parts of the system, but it&#8217;s so effective, I feel, but. So there&#8217;s this upcoming release of SysML V2, the final specification that I think is supposed to come out this year. How does the new version kind of? Affect this problem that you&#8217;ve been talking about how do you deal with complexity and how you can use systems engineering to sort of facilitate that. That shift left for product development?<\/p>\n\n\n\n<p><strong>Mike Crist<\/strong><\/p>\n\n\n\n<p>I think SysML V2 is being seen by a lot of people. A lot of companies as an evolution of SysML V1. Where you&#8217;re intending to describe the full architecture of the whole system using SysML V2. See Siemens is taking a different approach and this is where I think we&#8217;re unique so far in the industry and in the world where we&#8217;re using SysML V2 as a technology. Yes, it is possible to drive a system architecture and that it was the intended purpose of it. As was brought up in the in another podcast, the architecture does not have to be limited to a system a whole up system. Or your definition of a system. I&#8217;ve heard it put one way. One man&#8217;s system is another man&#8217;s subsystem. So by being able to describe multiple different types of architecture. We can now start to use jargon, specific descriptions of architecture. But using that same V2 technology enabled the cross-domain interconnection of the data. And we also take this unique approach that that&#8217;s one step further.<\/p>\n\n\n\n<p>It says, I don&#8217;t have to be limited necessarily to describe architectures with SysML V2. All the different ways and types of data that can be represented with V2 I should be able to use that as a payload for data exchange and data interoperability across multiple topics, and then you add on top of that the machine readability of this standard and the machine interaction through rest, oslc and others for the repository. Really enables us to use autonomy or automation to interact more with these standard types of use cases, as opposed to building a bunch of custom one-off solutions. The V2 opens up a lot more. Essential for machine-based interaction as well as cross domain and cross industry interaction.<\/p>\n\n\n\n<p><strong>Dale Tutt<\/strong><\/p>\n\n\n\n<p>Yeah, I have to agree with you on that about system LV too. I&#8217;m excited about it and I really liked what you touched on at the end there that that the ability you know making it machine readable, making it, it&#8217;s going to make it a lot easier to automate it. It&#8217;s going to also make it a lot easier to apply some artificial intelligence once you have that great data for. Across all the different elements of your systems, and so I&#8217;m excited about that and what about you, Scott? Are you are you seeing much activity with the system V2 and the systems with respect to the hardware and chip design right now or how are you seeing that affecting and influencing that activity?<\/p>\n\n\n\n<p><strong>Scot Morrison<\/strong><\/p>\n\n\n\n<p>Yeah, we are seeing it the way that I&#8217;m kind of most witnessing it right now is in the kind of system level Digital Twin modeling. It&#8217;s a much richer approach or language that allows us to describe the types of multi behavioral, multi physics systems that we&#8217;re dealing. With. And we have implemented some initial capabilities which are enabling new approaches for new types of analysis, not yet AI. But as you said and it kind of leads in that direction kind of nicely as well. But definitely you know it&#8217;s a richer language kind of broader in its capabilities. And so we&#8217;re already seeing it at the Digital Twin system level Digital Twin level. We&#8217;re being able to use that and to be, you know even slightly more specific, it&#8217;s kind of like as. That kind of export from one tool to another, you know, as we&#8217;re trying to integrate the workflow more effectively for these system level design and analysis problems that our customers have. I mean, it allows us to export in kind of a very kind of comprehensive rich fashion information from one tool and get it into the next tool. So that&#8217;s kind of the the I would say, initial wave or initial phase, so to speak of how we&#8217;re seeing adoption in our area.<\/p>\n\n\n\n<p><strong>Mike Crist<\/strong><\/p>\n\n\n\n<p>And you know, we&#8217;ve got quite a bit of experimentation also going on with electrical and electronics. I think Scot mentioned in the last podcast about the need to thread requirements through the design and through the verification\/validation, we&#8217;ve actually got that threaded requirement set now integrated and interacting with the V2 repository. So as those requirements and parameters are being defined at the system level. You can continue that thread into verification in a threaded fashion.<\/p>\n\n\n\n<p><strong>Dale Tutt<\/strong><\/p>\n\n\n\n<p>Yeah. No, that&#8217;s a really good point. I mean, I think you know that ability to have you know the well connected digital threads and you know the comprehensive Digital Twin. Because once you have those requirements and it&#8217;s being threaded in all the different models that make up the Digital Twin that that, now you&#8217;re actually able to do the code development of the hardware and the software. And so I think that&#8217;s a really is a big part, so. Let&#8217;s dive a little deeper on that. You know, how are the companies maturing? The systems engineering approaches we we&#8217;ve already started to touch a little bit on artificial intelligence and how it&#8217;s helping companies and you know we see great opportunities there. But you know Mike, what are your thoughts is where you&#8217;re seeing companies starting to adopt this technology and what&#8217;s available now?<\/p>\n\n\n\n<p><strong>Mike Crist<\/strong><\/p>\n\n\n\n<p>Quite honestly, I don&#8217;t think that there are very many companies that have established systems engineering practices. That are really expanding their understanding of systems engineering. I think we see a lot of our customers that are struggling. In what we call the difference between little MBSE and big MBSE. And a lot of companies have in their systems engineering practice. And brought it to this little MBSE, where there&#8217;s a focus on architecture and requirements for systems engineering. Our approach is one of the big MBSE that says the practice of systems engineering doesn&#8217;t start or stop with requirements and architecture. And so as we help our customers to understand the big MBSE picture and return to the roots, the practice of systems engineering, we&#8217;re helping them to see that. Of SysML V2 in a much broader fashion, but also with the additional technologies, transformations and interoperability that&#8217;s necessary for the treatment of the whole system.<\/p>\n\n\n\n<p>Now, artificial intelligence helps us in some ways, but I think that a lot of people are stuck in this mindset that artificial intelligence means a large language model, something I can type in a text box and the computer tells me the answer and maybe. Have to refine it through chat. Well, that&#8217;s not all of artificial intelligence. That&#8217;s all the rage right now. But we&#8217;ve already got AI enabled technologies for systems engineering and products like Simcenter Studio we can feed in starter architecture and have the AI generate valid topologies, but also viable topologies that actually meet some requirement or standard or desired attribute of the system. And then, of course, all the post processing tools necessary to help refine that down from, say, 10s of millions of combinations down to the one or two that you want to in that you&#8217;re. Actually interested in. So it&#8217;s not just simply that we can type in and ask for a generation of the of a thing. We see a lot of customers that say I want an AI where I can say make me an architecture that looks like an architecture that I&#8217;ve already made before. And yeah, we&#8217;re working on that. And yeah, SysML V2 helps that. But I think that we need to help our customers to understand that there&#8217;s a lot bigger picture that&#8217;s.<\/p>\n\n\n\n<p><strong>Dale Tutt<\/strong><\/p>\n\n\n\n<p>You know, I think I could. There&#8217;s so many things you said there that were just like I could go dive deeper on, but I&#8217;ll. I&#8217;ll just couple quick comments. One is you know when you talked about big MBSE versus little MBSE and I go back to what Doug was so eloquently stating in the previous episodes about the changing business models and if you don&#8217;t. If you&#8217;re not looking at that, if you&#8217;re not using big MBSE. You&#8217;re not being able to answer that question if you&#8217;re looking at little MBSE and just totally focused on system modeling, you really can&#8217;t satisfy that use case in my opinion. And so I think that&#8217;s such a great distinction. And so, anyway, I liked what I liked what you said about that and just the mindset around systems engineering and the usage of AI.<\/p>\n\n\n\n<p><strong>Conor Peick<\/strong><\/p>\n\n\n\n<p>Hi there this is your host Conor one more time just to say thank you so much for listening to the Industry Forward Podcast with Dale Tutt. If you enjoyed the show, please consider subscribing on Spotify or Apple Podcasts and if you really enjoyed the show, maybe throwing us a rating and a review.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Siemens Digital Industries Software<\/strong>\u00a0helps organizations of all sizes digitally transform using software, hardware and services from the <a href=\"https:\/\/xcelerator.siemens.com\/global\/en.html\" target=\"_blank\" rel=\"noopener\">Siemens Xcelerator<\/a> business platform. Siemens\u2019 software and the comprehensive digital twin enable companies to optimize their design, engineering and manufacturing processes to turn today\u2019s ideas into the sustainable products of the future. From chips to entire systems, from product to process, across all industries.\u00a0<a href=\"http:\/\/www.siemens.com\/software\" target=\"_blank\" rel=\"noreferrer noopener\">Siemens Digital Industries Software<\/a>\u00a0\u2013 Accelerating transformation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Industry Forward Podcast continued with another three part series on the intricacies of shifting-left with the comprehensive Digital Twin&#8230;.<\/p>\n","protected":false},"author":69073,"featured_media":12813,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1,13763],"tags":[194,11,2,8374,4],"industry":[],"product":[],"coauthors":[8377],"class_list":["post-12812","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","category-podcast-transcript","tag-digital-transformation","tag-digital-twin","tag-digitalization","tag-siemens-xcelerator","tag-simulation"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/19\/2026\/01\/DigitalTwin-Visual2024-Overall-Cropped-16x9_medium.jpeg","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/posts\/12812","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/users\/69073"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/comments?post=12812"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/posts\/12812\/revisions"}],"predecessor-version":[{"id":12814,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/posts\/12812\/revisions\/12814"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/media\/12813"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/media?parent=12812"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/categories?post=12812"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/tags?post=12812"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/industry?post=12812"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/product?post=12812"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/thought-leadership\/wp-json\/wp\/v2\/coauthors?post=12812"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}