Model Based Design (MBD)

"MBD is important, because it increases the speed, accuracy, and efficiency of manufacturing complex parts while also reducing the cost of through automation and time-savings"

Capvidia

About 10 years ago, the most common approach to building hardware products was a waterfall process where engineers define requirements, design the system, build it, then turn it over to an operator. This design approach is commonly represented as a Design V. Design processes happened sequentially and information was transferred via documents, checklists or worse, word of mouth. This delayed insight generation until the very end of the design process, making it error prone and time consuming.

MBD (Model Based Development) was introduced to fix this. MBD is a method of designing systems where verification and validation is conducted early and often. It involves modeling a plant using software, testing its performance using simulation tools, and optimizing it before implementation to avoid expensive physical prototype iterations. Testing typically includes functional, cost and performance considerations so organizations can “shift left” their development.

50%+

Reduction in development time using MBD

Why is MBD important for systems design?

Many organizations use models or perform simulations in an ad hoc manner, but the MBD methodology is more encompassing than that. If an organization was to truly adopt MBD, it would mean that digital engineering models are at the center of everything and are the only source of truth used by all stakeholders. All design work is done on the models and models extend to every aspect of an organization. When done well, it can lead to cost savings of up to 30% and development time savings of up to 50% by facilitating:

Better communication across groups: MBD provides a one source of truth directly within the design environment, meaning all stakeholders are looking at the same thing. Data analysis, verification and validation are all conducted on the one model
Product development risk reduction: Engineers following MBD will be able to notice and correct errors earlier in the system’s design, minimizing the time and financial impact of changes made

A shift is underway — are your MBD tools helping or hindering?

Collimator is the only tool that provides a unified environment to design, model, simulate and test performance from systems in the real world allowing you to go from design to production in one place for Model Based Development (MBD)

Unlock the full potential of your engineering team with powerful features

Design

Explore the vast number of possibilities, model to your desired complexity

Simulate

Move faster with speed and agility, get high fidelity insights earlier

Visualize

Analyze your results, increase confidence on your designs, iterate

Deploy

Automatically generate code and deploy code to your target hardware

Collaborate

Integrate your workflows and streamline
collaboration

Traditional Applications

Cannot quickly ingest or export the amounts of data required

Involves extra time, effort and money to run HPC simulation

Difficult to collaborate without being in the same room

Requires extra tools to share results or progress with your team

Seamlessly ingest or export data by directly connecting to your database via API

Quickly test or simulate performance over millions of runs using HPC in the Cloud

Efficiently collaborate with one source of truth and role based access control

Easily create reports to share with system engineers, perception engineers and product teams