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.
Reduction in development time using MBD
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:
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)