Hello Everyone,  

I spoke with SolidWorks R&D recently regarding the next-generation SolidWorks product, SolidWorks Mechanical Conceptual. This product was introduced at SWW2013 and was positioned as a tool for the conceptual designer. It is intended to augment the existing SolidWorks V1 (file-based) solution used throughout the world today. This product is architected much like the existing CATIA V6 solution in that it stores all of its intelligence within a database.  In my talks with R&D, my interest centered around the plans for integration of this product with the SLW-managed SolidWorks V1 solution. The R1 release of this product will only be available as a cloud offering so integration with a existing DS products was not a focus and only import/export capability will be part of the initial solution.  

I will be involved in subsequent discussions regarding the future integrations and synergy that this product will have within ENOVIA and the larger DS product suite. From the perspective of SLW, I see this product as a front-end to SolidWorks V1 that will be accessible quickly and easily from a common ENOVIA environment. SLW will make the perfect conduit for communications between these applications since both modeling tools share the same database. I shared the single slide below with R&D regarding what I saw as the open questions for communication beyond R1. Please feel free to comment on this slide as I want to make sure that I encompass all the appropriate requirements. Please also feel free to markup a copy of the slide and send it directly to me so I may update my posted media as needed. I look forward to your input...

.