Most product design fail because of communication inconsistency. 25 years ago Scott McNealy did not permit PowerPoint in any meeting at Sun Microsystems. Rumour has it that Jeff Bezos does not permit the use of PowerPoint during meetings at Amazon.
PowerPoint is good for high-level presentations to executives, and folks that do not have to get into the depths. Word documents are good for submission and certification. In today’s world of remote design centers, work-from-home, and language barriers, Word and PowerPoint will not cut it.
This is where the concept of Digital Twin kicks in. A digital twin is a digital representation of an intended or actual real-world physical product. It can be used for requirements gathering, architecture exploration, simulation, integration, testing, monitoring, and maintenance. In the current setup there is no common Digital Twin for all these tasks. For the Twin to be truly effective, there must be a single reference and the reference must start at the earliest stage of development and used throughout the design flow.
Companies are arriving at a Digital Twin from different directions. Each one focuses on one area of the design or one technology. There are solutions from Siemens, Mathworks, Altair and so on.
One company, Mirabilis Design, provides a Digital Twin that can be used from requirements gathering to field testing. This Digital Twin can be used for requirements validation, specification optimization, early validation, replay errors and generate executable documents for communication.
To learn more, watch the video: https://lnkd.in/eewdJ94K
#digitaltwin #technology #electronics #digital #development #communication #design #architecture #productdesign #reference #testing
