Model Based Matters

In the previous podcast episode, we discussed the tools that an engineer or system architects might use in their day-to-day operations, which is very familiar to MBSE for changes in the industry. Thus, SysML is one of the components of that methodology.  Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software, discuss what is driving the adoption of MBSE. In the past, UML allowed modeling software elements to reuse functions from a software definition; however, it only met some of the needs of the broader system. Therefore, UML extensions were created as additional profiles, represented through SysML. However, this needs to be more comprehensive, so extensions made in the field, the tools, and even beyond the tools require the customers to extend SysML, leading to proprietary. Subsequently, exchanging information was very difficult. Consequently, OMG, as a standards group, came forward with an updated definition called SysML V2. Rather than being an outgrowth of UML, it is a fresh perspective that said, "What are the needs of systems engineering? How do we get a graphical representation and a textual representation that can be parsed, machine-readable, and has a textual semantic that guarantees that I can exchange across the toolchain without losing any level of detail." The value of what we see in SysML V2 is that it can become interoperability and an authoring language.   What You'll Learn in this Episode: How SysML is one of the components of Model-Based Systems Engineering The value of what we see in SysML V2 is becoming interoperability and an authoring language. The automation and machine readability for sustainability solutions and parsing of understanding is critical to getting more than data scientists onto the solution path.  The concept of early verification involves taking the prior product's digital twin and identifying innovation points related to new requirements. A multifaceted mass adoption of MBSE. Connect with Tim Kinman: LinkedIn Connect with Nicholas Finberg: LinkedIn Hosted on Acast. See acast.com/privacy for more information.

The rapid growth of complexity across the industry pushes many businesses to reevaluate their approaches to developing products and processes. That complexity comes in various business pressures, from increased regulation for autonomous products to the inclusion of carbon footprints to meet sustainability standards. Remaining competitive while tackling these challenges will require a digital solution with model-based systems engineering. Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software, discuss what is driving the adoption of MBSE. In this episode, you will learn about the key drivers pushing the industry towards a more modern development approach. You’ll learn about what makes an MBSE approach better able to handle complex products over a system engineering approach. And you’ll know how this methodology fits into development, as it might be defined today. What You’ll Learn in this Episode: The changes influencing the future of industry (01:18) The nuances of systems engineering vs. model-based systems engineering (03:50) Why reuse is critical to streamlining development (14:45) How the MBSE methodology is applied in development tools (15:50) Connect with Tim Kinman: LinkedIn Connect with Nicholas Finberg: LinkedIn Hosted on Acast. See acast.com/privacy for more information.

The change in the automotive industry’s business model has also impacted pre and after-sales customers interactions. For instance, new car manufacturers are not opening new dealerships to reach their customers and the maintenance process is becoming digitized. For OEMs to remain competitive in this new environment, they have to embrace and embed digitalization beyond the production phase. Today, the hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by three guests from Siemens: Nand Kochhar, Matt Bromley, and Doug Burcicki. In this episode, you’ll learn about the major changes in the automotive industry that have been triggered by the new business model. You’ll also learn about the impact that autonomous vehicles are having on the trucking industry. Additionally, you’ll learn about the role that MBSE can play in helping OEMs navigate the radical changes in the transport industry. What You’ll Learn in this Episode: The changes in the business model within the automotive industry (00:47) The changes in how vehicles are going to be serviced (03:52) The impact that autonomous trucks are having on the industry (10:44) How the MBSE approach can be used to deliver sustainability objectives (14:35) Connect with Matt Bromley:  LinkedIn Connect with Nand Kochhar:  LinkedIn Connect with Doug Burcicki:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

The automotive industry is undergoing a lot of changes necessitated by a shift in customers’ preferences as well the need to be eco-friendly. New customers are more interested in the experience they get than how fast the car goes from 0 to 60 or the type of suspensions installed. All this has introduced a lot of complexity because OEMs now have to essentially build computers on wheels. Today, the hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by three guests from Siemens: Nand Kochhar, Matt Bromley, and Doug Burcicki. In this episode, you’ll learn about the current trends that are taking place in the automotive industry. You’ll also learn about why the changes have necessitated a shift in the business model and attracted technology companies. Additionally, you’ll learn about the complexity that these changes have introduced and what traditional OEMs are doing to remain competitive. What You’ll Learn in this Episode: The current trends in the automotive industry (00:49) The cause of change in the automotive industry’s OEMs business model (04:10) The complexity that emphasis on software has brought to vehicle design (06:44) How traditional OEMs are handling the need for electrification (12:13) Connect with Matt Bromley:  LinkedIn Connect with Nand Kochhar:  LinkedIn Connect with Doug Burcicki:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

In MBSE, testing gives confidence to engineers by confirming that the product they developed works as intended. With virtual hardware-in-the-loop (HIL), the engineers can easily generate the right data to prove their hypothesis as well as improve on the design’s performance. That data can also be used by machine learning models if there is a need for end-product automation. Today’s hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by Michael Baloh and Jan Richter, both from Siemens Digital Industries Software. In this episode, you’ll learn how hardware-in-the-loop simulation works as well as how it fits into the continuous verification process. You’ll also learn about the benefits of a virtual HIL and how it facilitates automation at later stages of development. Lastly, you’ll hear about the best way to utilize the feedback collected from the end-products use. What You’ll Learn in this Episode: How software and loop testing fit into continuous verification (02:27) Recent trends on HIL usage within the automotive design industry (06:50) The difference between virtual HIL and a physical HIL (08:13) Understand how far continuous verification and validation go within the MBSE process (10:35) Connect with Jan Richter:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

Failing as fast as possible has now become a goal while designing new products. This is important because it ensures that the development team is not wasting valuable time and resources on products that won’t work. To implement this strategy, in a cost-effective way, you need to create models that can be continuously verified throughout the development process. Today’s hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by Michael Baloh and Jan Richter, both from Siemens Digital Industries Software. In this episode, you’ll learn about the importance of creating models while designing new products. You’ll also hear about what continuous verification entails and the role it plays in keeping the engineering team on track. Additionally, you’ll learn the difference between product verification and validation. What You’ll Learn in this Episode: What continuous verification entails (02:22) Why one needs to build and analyze models (03:53) How MBSE makes continuous integration and continuous delivery possible (07:57) The different types of models (10:26) The difference between verification and validation (13:09) Connect with Jan Richter:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

Increased electronics complexity has directly impacted all stages of the design and manufacturing processes. This comes at a time when companies are being pushed by market forces to cut the time to market and still make quality products at affordable prices. One of the possible ways to meet these expectations is through the automation of some of the resource-consuming tasks within the design stage. Today’s hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by Mark Malinoski and Matt Bromley from the EDA space to talk about vertical connected development. In this episode, you’ll learn about the challenges that can be solved by automating some tasks within the design process. You’ll also learn about the benefits of continuous verification and how it impacts product design adaptability. Lastly, you’ll hear about what the future holds for MBSE and the role that increased complexity will play in the world of electronics. What You’ll Learn in this Episode: How automation can play an important role in MBSE (00:43) The challenges that stem from a lack of continuous verification in electronics design (05:11) How the supply chain is evolving and the cause of the changes being experienced (08:06) What the future holds for MBSE (12:47) Connect with Matt Bromley:  LinkedIn Connect with Mark Malinoski:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

As electronics become more complex, the task of designing has become more demanding. Improvement of a single component in most cases requires a change of several other components and subsystems. To achieve this, companies have had to shift from the traditional product design approach to a digital approach that allows for e-building and testing before the prototype stage is reached. Today’s hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by Mark Malinoski and Matt Bromley from the EDA space to talk about vertical connected development. In this episode, you’ll learn about the impact that complexity is having on the electronics design process. You’ll also understand how digital twins and digital threads assist in managing collaboration by enhancing traceability and observability. Lastly, you’ll learn about the challenges faced when decomposing down to silicone and then recomposing the system. What You’ll Learn in this Episode: The impact that complexity is having on MBSE (04:10) The challenge of decomposing systems architecture so as to have common context (07:48) Why customers like to get an early architecture that meets specified requirements (10:58) What it looks like as you drill down and refine an electronic systems architecture (14:44) Why complexity increases as you move towards individual domains (21:44) Connect with Matt Bromley:  LinkedIn Connect with Mark Malinoski:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

There is nothing more costly than doing efficiently that which should not be done at all! In today’s market when a shorter time-to-market is demanded, this is a situation that has to be avoided at all costs. This is why most manufacturers are now using digital tools to manage development workflows in a way that keeps all teams focused on doing the right thing. Today’s hosts are Nicholas Finberg of Siemens Global Marketing, and Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are joined by three experts: Piyush Karkare, Global Director for Automotive Industry Solutions at Siemens, Michael Baloh, Control Engineer at Siemens; and Brad McCaskey, Portfolio Executive at Siemens. In this episode, you’ll find out what feature-centric engineering involves and the role that collaboration plays in making it possible. We’ll also discuss the importance of interfaces in making different aspects of the vehicle function together. Lastly, you’ll understand why companies advocate for the reuse of existing features. What You’ll Learn in this Episode: What feature-centric engineering means (02:56) The relationship between electrical, electronic, and software architecture (09:36) The importance of interface definition (12:08) How to apply contracts to interfaces as a way of verifying behaviors (17:00) How features reuse helps lower the cost and speed up the development process (23:39) Connect with Piyush Karkare:  LinkedIn Connect with Brad McCaskey:  LinkedIn Connect with Tim Kinman:  LinkedIn Connect with Michael Baloh: LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.

Requirements-driven design makes it easier to align the product design efforts with the expectations of the end product. Models created from this approach can be efficiently decomposed to allow for collaboration across the engineering departments, the entire business and the supply chain. It is a part of model-based systems engineering (MBSE) that makes it possible to optimize the product by using simulation before the physical product is manufactured. Today’s moderator, Nicholas Finberg of Siemens Global Marketing, is joined by Tim Kinman, Vice President of Trending Solutions and Global Program Lead for Systems Digitalization at Siemens Digital Industries Software. They are also joined by Ryan Wilkins and Tony Komar, two experts who’ll also be contributing to this important topic. They’ll help us understand requirements-driven design and the functional definition in model-based systems engineering. In this episode, you’ll find out what requirements-driven design entails and its application in the automotive industry. We’ll discuss the importance of supplier collaboration and the role it plays in the product development process. Lastly, you’ll learn how agile development complements the goals of MBSE. What You’ll Learn in this Episode: The meaning of requirements-driven design (00:41) How agile development complements MBSE (03:21) How to define functions in MBSE (12:39) The importance of simulation in MBSE (16:30) The importance of supplier collaboration in the early stages of product development (21:20) Connect with Tim Kinman:  LinkedIn Connect with Tony Komar LinkedIn Connect with Ryan Wilkins LinkedIn Connect with Nicholas Finberg:  LinkedIn Hosted on Acast. See acast.com/privacy for more information.