Community Tip - Need help navigating or using the PTC Community? Contact the community team.
Unite Technology: Open Solid Edge functionality availability.
Currently Creo > File > Open of a Solid Edge file (*.par or *.psm or *.asm for instance) proposes only "Import" option.
The enhancement request is to have OPEN instead the IMPORT option (please refer to the 3rd page Unite Technology document).
I'm asking this enhancement because this functionality will leverage us to move to Creo in a more smooth and efficient way.
It will allow us to incorporate Solid Edge assemblies directly into Creo design and then convert data as needed and when needed.
This is a key functionality to easily re-use the legacy data.
Whirlpool - Indesit
We are migrating from Solid Edge to Creo 6.0 and this functionality is needed urgently to manage the transition and manage the multi-cad environment.
It's a 5 year old product suggestion. I wouldn't hold my breath.
I cannot see PTC doing anything with Creo 6 as it is past its end of life date.
Solid Edge uses Parasolid, so you may be able to export the SE files in a .x_t format and then import that into Creo.
The only thing a File Open of a non-native file does is a 'behind the scenes' export from the other file format and an import into Creo. PTC has just licensed the code to do the export from the other native format. This is then driven by marketing based on perceived market share gained by converting the other CAD data directly to Creo. Obviously, PTC has not seen the demand for Solid Edge data like they have with NX, Solid Works (both Parasolid kernels) and CATIA.
Thanks Ben for some technical insight on the behind the scene working.
The difference between Open and Import from end user and organization perspective is that we can build a true multi-cad assemblies. That means, if we are transitioning from the SE to Creo we can avoid the costly and messy migration upfront. Old designs can leave peacefully in SE and new projects can start in Creo while at the same time sharing some of the common SE designs with Creo projects.
I understand from PTC's market share perspective and technically may not be a big deal, but comes down to solving the real world problems for the customers. We are still in the early phase of the Creo implementation, so we could get rid of Creo all together since we cannot integrate effectively into the product development process without this functionality.
Just curious as to what CAD software seemlessly manages other CAD files? I'm on Creo 4 so we are way behind on what the latest thing is.
I completely understand what you are wanting and why you are wanting it. My company uses Creo, Inventor, Solidworks, NX in different groups. I regularly get or share files with the Solidwoks and Inventor groups.
PTC is trying to use the UNITE technology to bridge this divide. I have not used it.
I see in the Unite brochure where you are talking about the Open vs. Import options.
**I don't think the previous link is still working...https://www.ptc.com/en/products/creo/unite-technology There is a datasheet link.
Unite technology covers NX, Inventor and Solid works to allow Open functionality instead of import, so I think you are covered for that.
The original enhancement request for this thread is close to five years old and from a sizeable company, clearly PTC is in no mood to bring this capability to other CAD systems beside NX, SW, Catia and inventor.
I would agree that it looks as if PTC has decided against incorporating this capability (my opinion). If you are in the drivers seat for the CAD transition, I would thoroughly test other alternatives before implementing any of them. If I was in charge, I would look in to NX since they are both owned by Siemens and may have some interoperability (again, just my opinion)
I was a Unigraphics customer when they bought Intergraph's CAD business, Solid Edge and IEMS.
NX can open a SE file directly as they know how to handle the structure. The first year they owned SE, there was a demo at the User Group meeting showing Unigraphics opening a SE file into an assembly.
Thanks Ben and Stephen for your input. That's a great suggestion. I will look into NX for the compatibility.
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.