How do I export a proprietary 3D SW Model into a format that Revit can accept but does not allow the person I am sending it to pull information that could compromise the intellectual property in the design?

 

I have proprietary information in the SW model and a customer would like the unit to display in their building model in Revit.


Categories: Import∕Export

Comments
Last comment By: Kevin Chandler   Mon, 19 Mar 2018 22:12:22 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

You may try IFC format which is a standard format for Architectural software exchange. This will effectively export the triangulation of your model.

By: Artem Taturevych  Wed, 14 Mar 2018 01:31:47 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Maybe find a CAD user able to suppress or otherwise fill in detail that you don't want revealed prior to translating.

By: Roland Schwarz  Wed, 14 Mar 2018 01:40:39 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Without owning Revit, is there a way to check whether this will reveal sensitive information? The only software we ever really work with is SolidWorks.

By: Kevin May  Fri, 16 Mar 2018 15:45:30 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Hello,

 

Try a defeature (on a copy) to remove what you don't want to show, but doesn't compromise the model for Revit.

Then do the save as that Artem Taturevych recommends.

 

Cheers,

 

Kevin

By: Kevin Chandler  Fri, 16 Mar 2018 16:44:29 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

It appears that the IFC file is what I am after. I am having problems exporting though.

 

I defeature or suppress (tried both) the parts I want to hide and everything looks correct. I then save as an IFC file and half of the assembly disappears. It does seem to be consistent (the same parts disappear), but depending on the exact process one half of the assembly will disappear or the other will. There are several parts which always transfer well. I do nothing special in the defeature aside from marking a few holes to keep.

 

I tried this with no success: Unable to export as STEP of some assembly files which has the same name as one of its components

I tried modifying export options as well to no avail.

 

Any ideas?

By: Kevin May  Mon, 19 Mar 2018 20:26:48 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Hello,

 

How about exporting the defeatured as an IGES?

 

Cheers,

 

Kevin

By: Kevin Chandler  Mon, 19 Mar 2018 20:33:05 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

IGES seems to be exporting just fine.

 

Virtually 100% of my work is with SW so I am unfamiliar with file exchange. The component I will be sending is primarily sheet metal and ideally I would like the customer to not be able to extract things from it, like dimensions, that would make it easier to recreate. Will the IGES and/or STEP work well enough for this? It is 3D modeling software and that is what it is intended to do, so maybe what I am searching for does not exist? Needless to say I am interested now either way as I am sure this will come up again.

 

Also, forgot to add that when I export to the IFC file it comes with geometry failure in some components. Those that import look fine and I am not to concerned for the end user, but this may contribute to diagnosis.

By: Kevin May  Mon, 19 Mar 2018 20:54:11 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Hello,

 

All export formats that save 3D data will import as 3D fairly close, less what's "lost in translation".

Basically an IGES (STEP, etc.) exports removes the feature tree and all the secret sauce contained within and lumps the opriginal into a blob called "imported geometry".

 

This is why I recommended the defeature. This operation tries to remove stuff you don't want out on the ether.

You can also delete items (like internal components, which defeature can try to do as well) as well from the defeature copy that aren't required for the exported version.

 

Also reimport your exports to see what others will be seeing before you send it out into the world.

 

Cheers,

 

Kevin

 

EDIT: Another thing you can do to your defeatured copy is to add in extrudes to infill/mask detail, which then will become part of the exported blob.

By: Kevin Chandler  Mon, 19 Mar 2018 21:02:30 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Thank you very much for the explanation. That was my general understanding of them just have not used them to often.

 

Reading between the lines, your response implies that the IFC may provide no more "protection" of hidden assets then (such as the sheet metal dimensions)? The different files types are obviously intended for different end uses, but it appears that the end result is more or less the same.

 

Thank you again for all your help (everyone)!

By: Kevin May  Mon, 19 Mar 2018 21:10:08 GMT
Re: Export proprietary 3D SW Model into format Revit accepts but does not a compromise intellectual property in the design?

Hello,

 

I would look into the spec and usages for IFC.

I don't know that much about IFC, but it's my understanding that it's geared toward construction, but it does create additional data outboard of the "translated file".

 

Keep in mind what the importer needs for data. Most just need an accurately sized unit and where to connect for utilities, anchors, lift points, etc.

 

Good luck and cheers,

 

Kevin

By: Kevin Chandler  Mon, 19 Mar 2018 22:12:22 GMT
You are not authorized to view this page No results found! Suggestions: Check spelling, try a different search, or browse topics below.