Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Switching a company from SW to OS
Anyone know of an easy path to convince a company away from SW and into OS?
I'm helping out some friends who are using SW 2022 and they're buying me a license. I fell out of my chair when I found out the license is over $8k now.
I don't remember buying my OS license and I never spoke to a salesperson at OS. I sent an email to Jon McClaney and it bounced back.
Seems like OS should be aware that Dassault Systèmes changed their pricing structure last year and they should be offering a promo or something.
I'm helping out some friends who are using SW 2022 and they're buying me a license. I fell out of my chair when I found out the license is over $8k now.
I don't remember buying my OS license and I never spoke to a salesperson at OS. I sent an email to Jon McClaney and it bounced back.
Seems like OS should be aware that Dassault Systèmes changed their pricing structure last year and they should be offering a promo or something.
1
Comments
We ended up paying for 1 year subscription and it was way too expensive.
Also there are a lot of people who just flat out do not use dependencies and go bottom up out of an absolute aversion to the complications of trying to use them in a file-based system without PDM. That's less justified IMO, but it's also beating your head against a wall to try and change.
I use Onshape whenever possible for design. But in terms of engineering functionality legacy tools have a long head start.
I'm being dunked back into SW and I'm squealing like a pig. It's changed a lot. Installing SW on an M1 mac hasn't been fun and then my magic mouse won't work properly.
I did buy a bluetooth 3 button mouse yesterday hoping I can rotate the model with ease. I'll figure it out eventually.
I have a Windows desktop machine with a fancy GPU dedicated to Creo that I use once in a blue moon for old CAD work. Maybe I can run it on my M1/2 Mac instead...
There needs to be solid justification to shift primary CAD tools, if it's just for the sake of user preference it will be a very though sale.
What are the pain points and/or cost associated with the current tool?
Does Onshape address all/most of these, does the investment (time,money,effort) make sense...
What are the drawbacks/risks?
As mentioned, Onshape is not perfect and still does not compare in many areas. Will those gaps have impact?
Check this out:
https://www.ptc.com/en/resources/liveworx-on-demand/switching-to-onshape-building-a-business-case
CAD Engineering Manager
I did buy a 3 button, usb C, bluetooth mouse. It works really well and I have both hooked up at the same time. I just have to grab the correct mouse when switching apps. I did have to edit the registry to make the scroll wheel act as "natural". Switching mice and have the scroll wheel not matching was a bit much.
As far as switching... Things are going well, SW changing their pricing structure is helping. My friends are wanting to do production and I just don't feel a file based system with a sql access database running on a local network is going to cut it.