The race towards CAD in the cloud is getting more interesting every day. I’ve been watching SOLIDWORKS World 2015 live streaming this morning. Overall SOLIDWORKS show was very impressive, as usual. I look forward to keep watching it following days.
However, what caught my special attention today is a presentation of a new cloud product – SOLIDWORKS Industrial Design. Couple of interesting facts about new product – works on top of Dassault 3DEXPERIENCE platform (in many aspects, think about it as ENOVIA V6); focus on free design with no traditional CAD constraints; leveraging cloud approach for social connection between users and collaboration. And… it is complimentary for SolidWorks users. Demo of product presented few scenarios in which design flow went between new cloud product and old SolidWorks connected by 3DEXPERIENCE platform. Sounds like a big deal.
The story about new SOLIDWORKS/3DEXPERIENCE product took me back to my comparison of Onshape and Autodesk Fusion360 visions few days ago – Carl Bass and Jon Hirschtick are in agreement about future of CAD. In my view, changes in design world towards distributed teams and ability to work effortlessly on any device without installation and manual upgrades are two main driving factors behind new cloud solutions. The story about Autodesk Fusion360, Onshape and SOLIDWORKS made me think about interesting priorities all creators of cloud CAD are thinking about. It was well articulated during SolidWorks World 2015 first day keynote – supporting any device, information is up to date all the time, users are connected (see picture above).
It makes a perfect sense to me, since it is a great reflection of modern cloud paradigm you can see well developed in products such as Google Apps, Office 365 and others. However, this is a place where complexity of CAD data requires from cloud products to be more sophisticated. Traditionally, CAD project is combined of multiple files – assemblies, parts, drawings, etc. As you start making changes you very quickly end up with a complexity of many-to-many relationships between different versions of parts, assemblies and drawings. Move it to the cloud – the complexity won’t disapear. Therefore, you can see both Autodesk Fusion360 and SolidWorks Industrial Design are trying to solve. I had no chance to see Onshape product yet, but my hunch Onshape will try to solve this problem too.
Autodesk Fusion360: revision control, branching and collaboration
SolidWorks Industrial design: 3DEXPERIENCE collaboration, branches, revision merging
What is my conclusion? In a traditional CAD world, the problem of file revisions, collaboration and data control was part of PDM solution. Historically, CAD vendors were reluctant to solve PDM problems unless it became absolutely necessarily. PDM was complex, required services, special pre-sale process, etc. However, cloud is creating a new demand and constraints for new CAD in the cloud paradigm. With the absence of file system exposed to end user, cloud CAD system will have to solve a PDM problem first. Just my thoughts…
Pingback: How CAD vendors “murdered” PDM business()
Pingback: How CAD vendors “murdered” PDM business | Daily PLM Think Tank Blog()
Pingback: Cloud CAD can solve hardest PDM problem()
Pingback: Cloud CAD can solve hardest PDM problem | Daily PLM Think Tank Blog()
Pingback: How much does it cost to manage CAD data?()
Pingback: How much does it cost to manage CAD data? | Daily PLM Think Tank Blog()
Pingback: How Fusion360 and Onshape are solving fundamental CAD collaboration problem | Daily PLM Think Tank Blog()
Pingback: Beyond PLM (Product Lifecycle Management) Blog » Why cloud CAD is closer to solve some PLM problems than you think()
Pingback: Why cloud CAD is closer to solve some PLM problems than you think | Daily PLM Think Tank Blog()
Pingback: Beyond PLM (Product Lifecycle Management) Blog » Is there a Place in the cloud for Product Data Management (PDM)?()
Pingback: 2.5.1 : CAD, Design data - PLM BookPLM Book()
Pingback: Beyond PLM (Product Lifecycle Management) Blog CAD-PLM integration and microservices architecture - Beyond PLM (Product Lifecycle Management) Blog()