Skip to main content
Aug 15, 2014 4:26 PM UTC
Question

Thinking About Switching to Solidworks from Creo?

The product called Solidworks, as folks know it today, has already split into two development streams. Solidworks will stay as it is with the same modeling kernel until and beyond the time when development is halted in the future. For CAD, a modeling kernel is analogous to the engine, drive train, and chassis of a car. Solidworks V6 (now called Solidworks Mechanical/Conceptual and other solutions will be added) will be the new product that will take over Dassault's development efforts and it will be based on Catia's modeling kernel. If they wish to avoid any data disruption, Solidworks users of today will need to continue using today's Solidworks in the future even though there will come a time when there will be little to no further development effort put into the product.

Dassault will give incentives to entice existing Solidworks customers to move to Solidworks "V6" (Mechanical/Conceptual) even though there will not be true data compatibilities. Solidworks "V6" will likely have the ability to open a native Solidworks part, assy, or drawing with Solidworks V6, however, the data will surely be stripped of any intelligence that it once had. They will probably also say that drawings will come over fully associative but there will only be a small amount of truth to that statement (probably just model and drawing at the file level - views, notes, and annotations will need to be "cleaned up" afterwards with significant effort).

You will probably hear from your users something like: "they wouldn't do that to us loyal users." Another comment you might hear is: "they would never do that because they would be shooting themselves in the foot." Well, unfortunately, this kind of thing happens all the time. This is strictly a business decision for Dassault.

The reason why Dassault is doing this is Solidworks was written on the Parasolid modeling kernel. Parasolid is owned by Siemens. As a result, for every seat of software that Solidworks sells, Dassault must pay royalties to Siemens (one of their biggest competitors next to PTC). In addition, Dassault's flagship product is Catia and not Solidworks. They make significantly more revenue on Catia than on Solidworks. The sales of Solidworks will eventually hit a wall as it attempts to enter into Catia-type accounts while also cannibalizing Catia revenue. There will also continue to be technical limitations that exist today in Solidworks for complex parts and very large assemblies. These occur when you don't own the kernel you run on.

Solidworks "V6" is not only in its infancy at this time but is built on the Catia modeling kernel. It is unlikely that existing Solidworks users will adopt V6 for a while. If/when they do, data will most likely not be compatible. Dassault is really hoping that Solidworks customers get to the point where they just simply move to Catia V6 even though it will have data incompatibilities.

http://www10.mcadcafe.com/blogs/jeffrowe/2014/04/10/solidworks-mechanical-conceptual-hits-the-market-but-does-it-hit-the-mark/?interstitial_displayed=Yes

This discussion has been going on for 3 years now:

https://forum.solidworks.com/message/259368

The above information was emailed to be my a PTC Application Engineer Fellow.

12 replies

Aug 15, 2014 4:56 PM UTC

Everytime I read the Solidworks vs (whoever) threads it's like I shiver a little. Because I have flashbacks of the days of getting new customers and asking "What CAD package do you use?" and then thinking "please not solidworks, please not solidworks.". Solidworks! Oh ok cool. Then we jack design time way up because we would know that the parts would need drastic DFM time.

And then there's the Solidworks Certified Trainers that I have modeled parts for because "they couldn't do it".

Aug 15, 2014 5:38 PM UTC

I had the cold call from SW sales. I grilled him on the reality of what was going on in development and he pleaded complete ignorance. Thanks for once again setting the record straight, Steven.

I did find out that SW beats maintenance costs over Creo by nearly 20%! ...and PTC is raising theirs, again, so that will be 25% pretty soon!

Aug 15, 2014 6:49 PM UTC

Dassault is dealing with an internal compatibility problem - Solidworks users are unable to move to Catia or exchange data with Catia users. This means that Solidworks users might just as easily move to Creo or UG as to Catia.

If they fail at the translation, it will give Solidworks users a reason to look elsewhere; perhaps this is where PTC's conversion strategy can come in. However, Dassault should be heavily motivated for that not to happen.

I don't see an insurmountable technical hurdle to changing kernals; other companies have made the transition before. In this case, Dassault is moving to a more capable kernal, so there should be good agreement between functions that are required vs ones that are available.

OT: PTC essentially created the Solidworks business. Not because of a management split, but because they cut off their own VARs**, VARs that built businesses and got good at selling small accounts by busting their butts to do so. When PTC withdrew from the VARs and left the VARs without business they had two choices - starve or sell something else. Guess what the most gratifying sale a CAD VAR, recently thown out by PTC, could make? I'll bet there are still a lot of Solidworks VARs that are bitter from PTC. Whether it made ultimate sense, cutting off the VARs left a stay-in-business motivated force, trained and experienced with Pro/E that had a revenge motive and opportunity to go and sell the daylights out of Solidworks. Nothing sells a customer better than - 'I used to sell PTC, thought PTC was the best, but Solidworks is Better. Much Much Better.'

**Honestly, some VARs were terrible. There's one in my area that sold AutoCad. I went to demo sessions from those guys and from one year to the next the Pro/E demo was unchanged, even though PTC was pumping out upgrades every six months. They also rep'ed IronCAD, but pushed AutoCad because they knew it and had built classes. Even so, there was a lot of energy in the PTC market. This is when PTC/User was created, entirely independently of PTC and unique to Pro/E. At the time PTC direct sales were bad also. I used to get calls 8 to 12 months apart from new sales guys wanting to know more about the business I was working in. The last guy failed to meet his quota and was canned, so the new guy was trying relationship building. I stopped talking with them as they were walking-dead salesmen.

3-Newcomer
Aug 15, 2014 8:02 PM UTC

Dassault has already done this to their customers before. A friend who's an engineer at a major manufacturer who uses Catia related to me the pain of switching from Catia V4 to Catia V5. Models came in essentially as if they were STEP or IGES imports, no feature history. I also seem to remember that there was a significant retraining required as well.

If I was in a company like this and had to abandon our entire database to upgrade, I'd argue hard for reviewing other packages as well. One of the biggest pains with switching CAD systems is legacy data which makes keeping the status quo very attractive. If I'm going through that pain, I might as well look at other products too.

Didn't PTC switch kernals a bunch of years ago? I seem to remember Granite being a big deal, but maybe it was an enhancement of the old kernal and a new name rather than a switch.

Aug 15, 2014 8:46 PM UTC

To be fair "In 1998, V5 was released and was an entirely rewritten version of CATIA with support for UNIX, Windows NT and Windows XP (since 2001)." en.wikipedia.org/wiki/CATIA

This was done with a large customer base. When PTC had the same UNIX to Windows transition it had a much smaller market to deal with. Dassualt probably has a better grip on the process this time.

Also:http://www.3ds.com/press-releases/single/dassault-systemes-to-continue-full-support-for-catia-v4-throughout-the-coming-years-1/

Paris, September 25th, 2009 — Dassault Systèmes (DS) (Euronext Paris: #13065, DSY.PA), a world leader in 3D and Product Lifecycle Management (PLM) solutions, today announced that the company will continue its support for CATIA Version 4 Release 2.5 until December 31st, 2011 for all customers’ current with their standard support charges.

For the past 15 years, CATIA V4 has been a major version used by many customers around the world for major industrial programs. Regulatory reasons in certain industries imply customers to maintain CATIA V4 in operations even if they have standardized with V5 and V6. Therefore, Dassault Systèmes has confirmed its decision to continue the support of CATIA V4 Release 2.5 until December 31st, 2011.

3-Newcomer
Aug 15, 2014 8:55 PM UTC

Wow, I had no idea V5 came out that long ago. I think it was around the end of support in 2011 that his company was making the switch. I suspect they put it off as long as they could.

Still, forcing your customers into starting a completely new databse is a risky move.

Sep 17, 2014 4:11 AM UTC

http://www.youtube.com/watch?v=vPTZJhyqYC8 Solidworks Mechanical/Conceptual

Mar 6, 2015 3:28 PM UTC

I've been a Pro/E-Creo user for about 20 years, and a Solidworks user for more than 10 years. Currently, I work on various engineering design programs using both CAD platforms. To me, Solidworks has clearly surpassed Creo as my tool of preference when considering the software design capabilities, program performance and ease of use. With what I currently view as a step back in performance when Pro/E became Creo, I would highly recommend anyone to consider a switch to Solidworks, NX, or, possibly, Inventor. I would hope that Creo users (such as myself) would keep an open mind about a dynamic moving choice of software tools, realizing that what was once good now may not always remain so. A good example of this is when my CADDS5 associates claimed up until their CAD system's dying days that Computervision would prevail and remain the best system available. Back then, I was an avid user of CADDS5, but could clearly seen then that Pro/E was superior (which it was proven to become). Unfortunately, in my opinion, I believe that PTC's best days are now in the past.