Only 20 years ago most hardware products were designed to be offline. The most common approach to building those products was a waterfall engineering process where engineers define requirements, design the system, build it, then turn it over to an operator. Today, devices that were once hardware only are now orchestrated by software and artificial intelligence. Software provides huge flexibility to these systems and from a user standpoint, it’s like magic - a 3 year old phone can feel new with a software update. This isn't the exception anymore, it is the expectation. For these devices, engineering is never complete. This means that engineers must plan beyond the development phase and think of continuous integration (CI) and continuous deployment (CD) for every new system they design.
speed to deploy gap between high and low performing DevOps teams - DORA/Google Cloud
CI CD is a methodology used within DevOps. DevOps is a software engineering culture and practice that unifies software development (Dev) and software operation (Ops). It is a technique where software can undergo continuous integration (CI) for building, testing and merging, and continuous deployment (CD) into devices in production. Combining MBD with CI/CD creates a thread of accountability for system performance from hardware to software and across the entire lifecycle. It would require companies to use the same model to design the system, generate code, validate performance, and use in production as a digital twin. By making this extension, companies will benefit from both the risk reduction of MBD and the speed of DevOps and allow them to:
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 and unify your MBD with CI/CD