The last time I checked, the only 3-D CAD file format Revit could import from SolidWorks was ACIS (*.sat). ACIS files are based on solid modeling format produced by Spatial Technology, Inc. Information about Revit from AutoDesk is available on this link: http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=10275191
· Revit: Import/Export Capabilities - Revit Architecture supports a wide range of industry standards and file formats, including DGN, DWG, DWF™, DXF™, IFC, SAT, SKP, AVI, ODBC, gbXML, BMP, JPG, TGA, and TIF. In addition to transferring standard lines, arcs, and circles, Revit Architecture can also transfer complex 3D model geometry for use in programs such as Autodesk® VIZ or Autodesk® 3ds Max® software. This capability provides opportunities to create stunning photorealistic interior and exterior renderings.
To clarify, export the file from SolidWorks as an ACIS (*.sat) file, then import into Revit.
If you have VectorWorks 2009 onwards, export from SW as parasolid, then export from Vectorworks as IFC.....
Welcome to the great myth of Autodesk interoperability. Revit is being pushed hard as the BIM product of choice, but the import formats are dire. I have no doubt that in a year or two Revit WILL read Inventor files (or more likely Inventor will be able to export the Revit format), but until then......
One thing to watch. If you are exporting the sat files, make sure your SAT options are set to version 7 or less.
Also, you'll probably want to remove a lot of detail from the models before exporting via SAT. Otherwise, the objects in Revit are very heavy and will kill performance. (I got this from an Autodesk whitepaper on transferring Inventor models to Revit.) I just found another tech tip on a independent site stating the same thing.
The best option to export your SolidWorks model to Revit is try the BIMDeX SolidWorks to Revit Exporter. With their product, you can export your SolidWorks model seamlessly to Revit with all parameters and hierarchy maintained. You can export as a native Revit family/ project too. If you still face this problem, you can contact firstname.lastname@example.org. They would be the best to advice on this requirement.
Wow, this is an old thread! Somewhat superceded by the fact that SolidWorks has a fairly decent IFC export capability now. We export to all the AEC applications pretty much on a daily basis.
Prep work in SolidWorks - save assemblies as part files and outside surfaces only. Most (as in 99%) of SolidWorks data that is needed in AEC applications is so that AEC users can integrate a manufactured product into a scheme, or so they can do visuals, or both. So from the manufacturers point of view the models need only show the visible surfaces and the interfaces to the assembly so that the AEC user can introduce it into their model. All the AEC systems are single file modellers, so your exported 500MB model in SolidWorks adds a lot of "weight" to the AEC file. AEC systems are nowhere near as good at "lightweighting" big data sets as MCAD focussed systems yet. Even now we often export our cut down models and the AEC users request DWGs as their systems cannot handle the models.
Assuming they can though, in our experience, the best options for export from SolidWorks to common AEC platforms are:
Revit>ACIS or IFC
VectorWorks>IFC or Parasolid
ArchiCAD>IFC (we have tested this one a lot and IFC works perfectly)
AutoCAD (3D models)>ACIS
AutoCAD (2D)> DWG from drawings sheets (also applies to other 2D systems)
Yes there are lots of add ons that claim to allow mapping of various elements in IFC classes and the like but to be honest (in our experience in the UK at least) the AEC users do not want the added complexity of that and they prefer to organise their models the way they want.
In all the cases above, the SolidWorks data comes into the AEC application at 90 degrees (on its side). This is becuase the SolidWorks "up" axis is Y and most of the rest of the world uses Z! All the AEC user has to do is rotate the model....but you would be surprised how often that creates issues!!
Meant to also add, the ONLY guaranteed way to ensure your data gets into a AEC system intact and as you want it to, is to invest in that system. Fortunately most AEC systems are available on a trial basis so I recommend you trial them all and test the data path into that system. Only then will you really see what your recipient sees. If you do a lot of Revit work, get Revit LT. It imports IFC fine and allows you to prepare the data precisely for the Revit user in a way that now 3rd party plug in can do. I don't know the cost of that Revit SolidWorks plug in but I'd be willing to bet that Revit LT is cheaper.