How many more releases until this is turned on?
How many more releases until this is turned on?
(OP)
Hi, So we are at NX 10 now and Feature level update from a SolidWorks file is still not supported. What is the holdup?
thread561-292259: Solid Works
thread561-292259: Solid Works





RE: How many more releases until this is turned on?
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
RE: How many more releases until this is turned on?
The wishlist is simple.
The economic rationale is more difficult.
Siemens never does anything for fun, it's all down to economics.
-If Siemens would implement this feature, what would be the benefit ? [ -for Siemens $ , -for the customer $]
Regards,
Tomas
RE: How many more releases until this is turned on?
hey john,
which version of .net does NX support? the current is at 4.5, but it doesn't support win forms anymore (mentioned here http://m.plm.automation.siemens.com/en_us/Images/4...), as they were deprecated quite some time ago.
RE: How many more releases until this is turned on?
True, Solid works is your competitor, but their users are {i}my[i] suppliers. I've been using NX for 20+ years and as a program I prefer it over Solidworks (we have both in-house). But, if I were buying a new CAD system now, I would probably choose Solidworks over NX simply because it seems to have a much larger installed base. Providing interoperability would remove that hurdle for me and many others. That is the economic benefit to Siemens. Making your customers life easier is rarely the wrong thing to do.
RE: How many more releases until this is turned on?
_________________________________________
NX8.0, Solidworks 2014, AutoCAD, Enovia V5
RE: How many more releases until this is turned on?
Please start a new thread for your question; that will avoid confusing this thread and your question will get more visibility.
www.nxjournaling.com
RE: How many more releases until this is turned on?
Another scenario we have encountered is purchasing other companies that have products developed in Solidworks. Having a way to move those files into NX and retain the model history would be welcomed.
As things stand now, we have several seats of Solidworks that would have been NX seats. Economic loss for Siemens.
RE: How many more releases until this is turned on?
But what you've described is a MIGRATION scenario, which is exactly what I felt is what we should be investing in rather then an environment where competitive systems are expected to co-exist with each other in a way that they can fully access and edit each others data as if it were native to both systems. We don't even do that with Solid Edge, where we own BOTH sides of the equation, why would we do it with a competitor's product?
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
RE: How many more releases until this is turned on?
RE: How many more releases until this is turned on?
Multi-CAD environments do have their purpose but for a design tool internally, you should have one system that is your primary tool. The other systems can be used to interface with outside suppliers who do not utilize the same tool you do. I worked for an aerospace company a few years ago and we standardized on Pro/Engineer as the division's primary CAD tool. Being CAD support, I also had NX, CATIA V5, SW, AutoCad and Inventor on my computer. Yes we did some projects in those other systems due to budget or time constraints, but we also knew that what they produced would never be integrated with a master Pro/E model.
I do agree that when a model is imported into NX, any changes on the model should be reflected in the NX file the next time it is opened. I do think that is how the NX-SE interface works and it should do the same with NX-SW, NX-Creo, NX-Catia, etc. Editting the imported model with features should not be done with assembly importted components. If the decision is made to 'transfer' the design control from one of those other systems to NX, then the NX Migration utility comes into play and now NX has model authority.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: How many more releases until this is turned on?
Also it’s understandable that it will be a very difficult task to keep up with the other software’s path to work with NX’s new developments and additions.
I guess this is why NX offers “Synchronous Modeling”. SWx offers same kind of capability without any specific name.
Who knows? May be NX may consider something similar to DraftSight by Dassault Systems.
Michael Fernando (CSWE)
www.solidCADworks.com
Tool and Die Designer
Siemens NX V9.0 + PDW
SWX 2013 SP3.0 X64
PDMWorks 2013
Logopress3
FastForm Advance
FormatWorks
RE: How many more releases until this is turned on?
If you want real interoparability you not only need the same CAD system you need more than that. You need suppliers/outsources to work the way that makes their data valuable. Otherwise just accept their geometry and add your IP. Anytime we work with suppliers you need to add time to communicate, validate and modify if you want to use the data anyways. Time varies depending on how much you want to use that data inside your process.
We all have reasons for ending up with the CAD systems we have (price, capability, compliance, supply chain, skills available...). That expalins my choices below.
Automotive Tooling
NX 9.0.3, Catia V5 R22, SW2013/2014