Issue link: https://iconnect007.uberflip.com/i/1449048
66 DESIGN007 MAGAZINE I FEBRUARY 2022 and metadata can be shared along its ribbon, increasing the fidelity of the exchange. e digital twin has evolved as well, allowing more complex interactions to be validated, ana- lyzed, and simulated earlier in the design cycle. ese digital models are not limited to design; they continue to be used in manufacturing pro- cesses and even in the matching models of a product in use. rough scalable, multi-domain flows that leverage the digital twin and digital thread framework, companies reap the benefits of reducing the need for expensive, time-con- suming physical prototypes. us, a model-based engineering approach consolidates advanced multi-domain system models, allowing for the definition of a multi- domain solution and early (shi-le) simula- tion at the system level. Importantly, all of this takes place before implementation and while the physical realization comes to fruition. As a result, model-based system engineering supports design, process, and system scaling, addressing exploration, design, verification, validation, and certification of complex elec- tronics functions across all the development domains. erefore, MBE is effective in miti- gating the risks of electronic systems design and manufacture. To enable multi-domain system design through MBE, we leverage the digital thread to integrate the flow from requirements through manufacturing and across multiple design those multi-domain architectures together ear- lier in the product design cycle. at solution requires model-based engineering (MBE). Model-based engineering has been around since Mylar and tape gave way to a revolutionary little thing called computer-assisted design. It's no surprise that what people mean by "MBE" has had a variety of shadings over time. But what do we mean by MBE today in this context? Basically, it starts with a digital model (the digital twin) that's intended to represent some- thing physical. e more we can use digital models throughout the design process, the more we can avoid using paper and handing off non-digital descriptions. In other words, we want to establish a digital thread, which is a communications framework that allows a connected data flow and integrated view of a product's data throughout its lifecycle—span- ning ideation, realization, and utilization. e digital thread allows us to pass digital models from one step, one domain, and one discipline to the next, instead of having to regenerate new digital models with every incarnation of the design. By leveraging the digital thread, the digital twin, and existing modeling capabilities, we can start addressing system design challenges. e digital thread enables continuity between domains and traceability from requirements all the way to manufacturing. As we increase the sophistication of the digital thread, more data Figure 1: Orchestrating MBE for electronic systems require focus on three key areas.