Solidedge and Solidworks - Same Office

[karmoh]

Hi All,

Before you read this is not intended as a thread for SE verse SW.

I’m a long term user of Solidedge (started in 1998) and I’m quite happy with the system. But my company (I’m the owner/operator) is growing at a good rate, which is nice in these present times.
I’m looking at buying Solidworks, this will allow me to grab some of the ever increasing inquiries that I have to let go due to them being specifically for SW.

I haven’t spoken to the local Var yet, as I would like a HONEST opinion of running both systems.

Do or have any of you run SE with SW? (separate projects) but in the same office.

What the best version or is 2010 the only option? (Siemens style)

What is the transition like? How similar or dissimilar are they?

How easy is it to take a SE project and Convert it to SW and vice versa?

From past experience I believe the greatest difference is with draft environments.

Big questions I know, but any feedback regarding this would be greatly appreciated.

 

[ctopher]

I have not used SE, only a demo.
I think SW is a great tool and is more popular than SE, IMO.
My suggestion is have SW come to your company, run a demo with some (import/export) of your files and see first hand how it could work for your company.
Keep SE running as long as possible until you are comfortable with SW, keep both or switch to SW.
How many users, or are you the only one?

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[karmoh]

Hi Ctopher,

Thanks for the prompt reply.

I have 2 other engineers, one is exclusive Autocad for architectural work.
There are 2 seats of SE, but there would be only 1 of SW to begin with, and I would be the predominant user.

 

[ctopher]

Also, to save $, you can upgrade to SolidWorks and use either DraftSight or SolidWorks 2D Editor that comes with the install to replace AutoCAD.

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

I used SE for an "after hours" project a few years ago and found it frustrating. But that was probably because I was still using SW during the day.

Both programs are equally capable, just different in their workflow.

Do you use SEwST much? SW does not have anything like it.

As Chris suggested, arrange a demo with SW (not their canned demmo) and get a trial version for more in-depth testing after the demo.

There will always be some glitches when converting from one program to another, but if I remember correctly, I had very few problems converting between SE to SW.

 

[karmoh]

Ctopher,

Autocad is here to stay part of my business deals with architectural doors and windows. All architects here abouts use only autocad.

CorBlimeyLimey, I have ST2 but do not use it for commerical projects I stick with the more stable Traditional mode.
Although ST is interesting and might be of use in the future. But we deal mainly with sheet metal cabinets and associated parts for the electronics industry. The ST2 sheetmetal env is ropey at best.

 

[ctopher]

I agree, it was an option. If you work with architects, keep ACAD.
Only an on-site working demo will answer most questions. Don't allow the person to trash SE, have him/her step through your questions between the two packages with your own files.
Have a list of questions on hand.

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[KENAT]

karmoh - we are stuck with both, and they are trying to get me to lead a transition to SW as our primary tool (currently SE is primary with SW from some legacy products from an 'acquisition' on SW plus a few renegade folk that refused to use SE).

I have yet to actually use SW in anger, though I'm keen enough to learn it so I can put it on my resume.

SW to SE transition projects that I've seen did not go well. While you can import models your ability to manipulate them are a bit limited - though I guess ST would help some here. Losing the model-drawing link is a pain. I think in the end we redrew & remodeled it into SE & recreated the drawings. Then 'cause they'd done a crummy job I got to spend a bunch of time sorting out the mess.

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​

 

[karmoh]

Thanks Kenat,

It looks like I will go ahead with SW.

My intention initially would be to keep projects separate, SE clients and SW clients.

From initial investigation, the cost is similar in NZ. But it seems that SW has a lot more to offer, I’m talking with a local Var about getting a commercial evaluation period.

I also have a contact, who’s company uses SW and have arranged an afternoons watch ‘n’ learn session.

 

[kellnerp]

I taught SE a while back so I had to go from SW to SE. Here is what I think you will find in the process:

1. SW is a lot more open than SE regarding the steps you take to get a result. What this means if you have a lot of people doing team projects is that you will have to settle on procedures, especially layout and handling the feature tree.

2. For me fixing problem models is a lot easier in SW than in SE. This is a corollary of #1 above.

3. If you used named variables and equations for dimensions in SE, you won't like SW disconnected way of doing things. You will, however like SW design tables.

4. If you do swoopy stuff you may like SW surfacing better.

5. SE assembly creation seemed more sensible, but was also hard for me to get my mind around.

6. I don't know about SE's ability to write out files for previous versions, but with SW you are trapped in a never ending software/hardware upgrade cycle, especially if your customers are driving what version you use. You may have problems with file management if you want to reuse parts across several releases because once a newer release does anything to a part in an older release it can only be read in the newer release.

7. You may not like SW drawing package. I always thought SE was better at making good looking drawings. In class we didn't do anything very complex so I can't say how performance compares in this area especially in large assemblies with sections and details.

That's all I can think of for now. Maybe later more will come to mind. And the highest release of SE I used was 15. Probably pretty old by now.

TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."

 

[karmoh]

Thanks for the input Kellnerp.

The cross over from draft (drawing part of SE) to SW drawing would be the hardest..........I feel!

I'm confident with the modelling side. It's just a matter of wearing two hats.......... ;-)

 

[kellnerp]

Drawings and Assemblies. Just remember the feature tree plays a very important role in SW, maybe more the SE. You have to learn the right mouse menus. They change with context. I'm sure you are familiar with context changes from the ribbon bars.



TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."