Dassault Systemes Customer Conference 2011 – Day 2

Day 2 of the Dassault Systemes Customer Conference started with a general session, a majority of which was dedicated to the DS brands. Jeff Ray, EVP Geographic Operations, introduced the brands and then each brand’s CEO took the stage to showcase their products. SolidWorks CEO Bertrand Sicot was away in Japan and his brand was represented by Key Clayton, VP Sales Worldwide.

Here is a slide from the presentation of the ENOVIA CEO Andy Kalambi which shows all the DS brands closely tied together by the ENOVIA.

Click to enlarge

After lunch I attended a session on CATIA where I hoped to learn more about Dassault Systemes plans for V6, especially since it has become a reality and is being used in production in some large accounts.

Earlier in the brand presentation CATIA CEO Etienne Driot said, “CATIA V6 is not CATIA V5 plus one. V6 adds a whole new dimension to CATIA.” This is what I learned about CATIA V6 today.

Firstly, Dassault Systemes will continue to support CATIA V5 till at least 2020. Yes, that another eight years. Not just that. They will also continue to develop it in sync with CATIA V6. This is because they want to let their customers make the transition from V5 to V6 on their own terms and at their own pace. CATIA V6 changes the way data is stored and shared and DS realizes that not everyone may want to upgrade at the same time.

This decision to develop CATIA V5 and V6 side by side comes with some real nice advantages. One of the features most requested by CATIA customers has been to be able to share their data effectively with users of previous versions of the software. By effectively I mean a V6 user should be able send his model to a V5 user and it should show up in V5 with all the features intact. The V5 user should be able to edit those features, add new ones and send it back to the V6 user with all the features intact. I actually saw a demo of this happening between CATIA V5 and V6 in the session. I hope to post a video sometime later today.

This needs some explanation, which is related to the reason why DS is continuing to develop V5 along with V6. The thing is V5 and V6 use the same modeling kernel. So if DS continues to develop V5 and V6 side by side, they will be able to add the new feature types or parameters to V5 as they add it to V6. This means that they need to release a version of V5 every time they release one for V6. That is precisely the plan. In fact, going forward the new CATIA V5 versions will be called CATIA V5-6R2012, the “5-6” denoting that it is paired with a corresponding V6 release.

So this way a company heavily invested in CATIA V5 can gently add V6 to their workflow without much disruption. The fact that DS will continue to develop V5 in sync with V6 will only give them the confidence that their investment is being taken care of. I think its brilliant.

This round tripping feature is going to be added to the next release of CATIA, the one called “CATIA V6R2012x”. I guess the V5 equivalent will be called “CATIA V5-6R2012x”. Here is a slide explaining the progressive transition from V5 to V6.

Click to enlarge

I wonder what the other CAD vendors who have been predicting the end of CATIA’s dominance have to say about this master stroke. I also wonder what SolidWorks customers think about all this. How will all of this play out when SolidWorks V6 becomes a reality?


  • Pingback: Round Tripping Between CATIA V5 And V6 With Features | Deelip.com()

  • Guest

    Does newer V6 versions have a file system or they store the data in ENOVIA V6 database only, as the older V6 versions?

    • I don’t have access to the software. But from what I hear it V6 doesn’t have a native file format of its own. I think it simply saves to V5, which should not be a problem since the geometry part of V5 and V6 is the same and will go hand in hand.

      • Skum73

        WIth V6 (similar to V5)  you always have the liberty to store the authored data in local file system by declaring your machine as a local host. In that case you do not need to have an ENOVIA V6 host. However in most implementations of CATIA V6 the preffered option is to store in ENOVIA V6 (for obvious reasons!)

  • Pete Yodis


      In a similar vein, is it possible we will see something like a SolidWorks 2013-V6.  Is that what Dassault/SolidWorks means when they say the customers will have the option to decide when they want to make the switch?

    • I don’t know. The idea here is to have a smooth V5 to V6 transition. I not sure whether DS wants to offer a SW to CATIA migration as well. But then, when SW V6 starts using CGM as the modeling kernel then it will open up various possibilities, like the one you mentioned.

      • Pete Yodis

        My question was really about the technical feasibility of a SW-V6 method just like the V5-V6 method.  It sounds like you think it is feasible from a technical standpoint, is that right?  From a business perspective… thats a whole other ball of wax.  I can’t really see them doing it from a business perspective, but if someone else is going to make it easy to suck in and modify SolidWorks files and they begin to take business away (“kill SolidWorks”), then maybe that possibility is in their backpocket.

        • Actually no, it won’t be technically feasible. The current SolidWorks is based on the Parasolid modeling kernel. The reason why DS can do this for CATIA V5 and V6 is because both versions will be based on the same CGM modeling kernel.

          So for DS to do this king of pairing between the current SolidWorks and CATIA, users will first need to move to the SolidWorks V6 that uses CGM and then make the move to CATIA V6, which doesn’t make much sense since they might as well move to CATIA V6 directly.

          • Pete Yodis

            That makes sense.  Thanks Deelip for the explanation.

  • Pascal Turcq, DS

    For information, a new video we posted on youtube just an hour ago with guys talking in the video. Worsth watching this: http://www.youtube.com/watch?v=B6tUuJTBT0s&feature=youtu.be

  • Pingback: Dassault Systemes Offers V6 To V5 Downward Compatibility | Deelip.com()