A few weeks ago we were in Los Angeles attending SOLIDWORKS World 2017. As usual, it was an overwhelming whirlwind of people, sights, sounds, and information while it was taking place, but has come into better focus now that some time has transpired for letting all of it sink in and make sense. One of the things I wanted to especially sort out was SOLIDWORKS’ take on model-based definition (MBD), where it stands today, and where it might be headed in the future
The last day of SOLIDWORKS World 2017 I sat down with Oboe Wu, SOLIDWORKS MBD Product Manager, and we discussed several aspects of MBD. Our discussion on SOLIDWORKS MBD centered around the creation and consumption of MBD data (that are tied to customers’ workflows), and the fact that MBD is transitioning from the “why implement” phase to the “how to implement” phase.
In the video below, SOLIDWORKS MBD Product Manager, Oboe Wu, discusses how to eliminate conversion of 3D data to 2D documents and fully leverage 3D design data throughout an organization and partners to reduce redundant tasks. He explains MBD from SOLIDWORKS’ point of view.
What is SOLIDWORKS Model-Based Definition?
He said that MBD is much more than just software applications and requires both process and mindset shifts to be successful. SOLIDWORKS wants to make defining, creating, and consuming MBD data as easy as possible because MBD is such a major process shift.
The consumption side of MBD data showcases the real purpose of MBD – to realize the full potential of downstream, intelligent manufacturing applications provided by the digital thread. The SOLIDWORKS charter is how to better consume MBD data.
According to Wu, time savings on the MBD data creation side is relatively small when compared with the time savings that can be realized on the consumption side. Ideally, data should be created once and consumed numerous times. In other word, the more times that MBD data is consumed, the better the value of creating it in the first place.