Imported files in Creo came as Solid but for NX some components came as Surface

[CC_8466609]

I am using Creo Parametric Release 4.0 and DatecodeM100

We exported our projects under Parasolid format (.x_t) and several times customer complain the imported files in NX several time some components are imported as surface and not as solid in Unigraphics and they spent time to solve this issue.
In Creo Parametric the files imported came as solid.

I don't have the Unigraphics Application and also I don't have experience with this application , but can you give us an explanation why do you think when NX when import files came with some components as surface.
Thx,
CC

[tbraxton]

It is pure speculation without some data sets for testing.

It could be related to the accuracy settings in your Creo environment. For the models with an issue are they using relative or absolute accuracy in Creo 4? If you are not using absolute accuracy in Creo you could try changing to absolute accuracy.

Do you have any geometry checks in your Creo models? If so that can also be a cause for translation errors.

Have you tested solid STEP format, Does it have the same issues?

[CC_8466609]

Hi,

we are using in Creo Absolute Accuracy and open in Creo there is no issue.

In NX, not sure what accuracy the customer used it's used to open the file some of the components came as Surface.

Customer complain the issue is from Creo, but from my point I believe is related to the import accuracy from NX.

I don't have the NX application to test and I was thinking if there is somebody that had this issue and to deal with this issues without spending time in NX to solidify the models with issue.

Thx,

CC

[CC_8466609]

Usually this customer want to have only Parasolid format.

Also it’s difficult because we cannot bother them for more investigations and tests.

Somehow we need to do some investigation on our side and be sure the customer when open the files to have them solid,

Or

if I know a clear procedure that can be done on NX in order the models to he solid and Customer satisfied I can tell them.

Thx,

CC

[remy · Accepted solution]

During all my years of CAD data translation software development, this has been the main takeaway: resolving importing issue is pragmatic. 
It's another way of saying it but basically, the situation is trying to reconcile two different parties that pull their interest in opposite directions and there is no one size fits all solution and rather find the proper process for your relationship.

Now practically speaking there's a lot that happens during your process that is invisible to the user. 

First Creo export to NX then NC imports that file.

The fact that Creo can import as solid its own xmt export is good news but does not bring much to your client. 

Siemens or your client can blame our export in the end this will not resolve.
Also the way Creo imports may also rely on a template that does all the job of sewing surface. there can be many reasons for the failure. 

Another option, if you don't mind is sending the Creo files to the customer and leave it to NX to import the Creo files.

Most of the times STEP is format of choice though.

And finally if your customer is eager, he can rely on third party CAD healing software.

[CC_8466609]

Thank you for your feedback.

[remy]

After reading again my reply, i can understand that it is a frustrating one and your situation is not easy.

One or two takeways in regards of what you can actually do are to discussing and negotiating with the customer and re-evaluate your comitement and collaboration. It has more to do with re-thinking the translation process as a whole than its technical aspect.

First there is a need to understand why your client insists on the Parasolid file format. My guess is that he thinks that because NX is Parasolid based, then if Creo outputs a Parasolid file it should be smooth. It is only a guess though. In data translation there is no conviction. Theory exists and then facts.

An analogy to make the client understand is actual languages. All of us speak English and depending on our education, localization, ease with the language, the way we speak can be understood or not, flawlessly or broadly. The same applies to data translation, there are accents, there are holes in sentences where you don't expect them, syntax misuse and many more.

Another strategy is to find a common ground. Let's say instead of speaking English we would decide to write C code. Even then there can be discrepancies as "language structures thought". So if we are to choose STEP which is CAD vendor agnostic in theory, there will be gaps and tores.

That's why data translation is pragmatic pick what works for your situation.

Another combination crossed my mind: did you try Onshape? it is parasolid based like NX. 
The limitation is that a free account leaves your model public.

We could imagine using Onshape as the translator whether on your end of the customer's. That's just a suggestion and I'll leave it there.