Convert SLDASM to IFC for BIM and plant handover

Converting SLDASM to IFC is what equipment makers do when a customer’s architect or plant engineer wants the machine in Revit, Navisworks, ArchiCAD or Tekla. PDMPublisher writes IFC in the same batch as the STEP files and PDF drawings, from the add-in or a SOLIDWORKS PDM Professional task. The BIM handover becomes part of the release, not a favor asked at the end.

What you get

IFC (ifc) is the Industry Foundation Classes format from buildingSMART, the open standard for BIM. It gives the building side the equipment envelope in the right position and units, ready to place and clash-check against the plant model.

You get one .ifc of the assembly, which is what a BIM coordinator normally wants: the machine or skid as one object. Enable Export references to file formats individually only when sub-assemblies or parts must be placed separately. Convert multiple configurations gives one IFC per configuration, such as left-hand and right-hand layouts. SOLIDWORKS’ current IFC export options apply.

The manual way, and why it doesn’t scale

Open the top-level assembly, File > Save As, pick IFC (*.ifc), name it, save. That’s the active configuration only. Repeat for every part you want as its own file, and again for every configuration.

Fine for one machine. For a 200-component release redone at every revision, it’s a day of clicking and a folder that never matches the BOM. Then the architect asks for the revised layout, and the same export is repeated for every skid in the project.

Convert SLDASM to IFC with the add-in

1. Open the top-level assembly in SOLIDWORKS, references resolved (Get Latest first).
2. On the PDMPublisher tab, select Settings, then Publish.
3. Set Export location: a fixed or UNC folder, or placeholders from the >... menu.
4. Set the Filename pattern, such as (FileNameWithoutExtension)-(Revision); the extension is added for you.
5. Under File formats, tick IFC (ifc); other ticked formats come out in the same pass.
6. Leave Export references to file formats individually off for one file of the whole assembly, or tick it for a .ifc per part and sub-assembly too. No BOM template needed here.
7. Tick Convert multiple configurations with (ConfigurationName) in the filename. The Configuration Filter includes (PROD*) or excludes (*Flat*) by wildcard.
8. Tick STEP as well when the customer’s plant engineers also need a mechanical CAD copy; both come from the same job.
9. Select PDMPublisher > Publish, confirm the review dialog, and check Publishing results afterwards.

In PDMPublisher for SOLIDWORKS, IFC needs Premium. The free Community Edition does PDF, DXF and STEP only, up to 5 references per run.

Automate it as a PDM task

PDMPublisher for PDM Professional runs the same engine as a task, so the assembly becomes IFC on a state change.

1. In PDM Administration, right-click Tasks, select New Task, choose PDMPublisher and name it.
2. On the Options page, set Export Location ((VaultRootFolder)\Exports\IFC, no trailing backslash) and Filename; PDM variables such as ($PartNumber) work here.
3. Under File Formats, tick IFC. Keep Export affected document on so the assembly itself is exported.
4. For the components too, set Template to a PDM BOM layout (name, configuration and quantity columns) and enable Export references to file formats individually.
5. Enable Convert multiple configurations and the Configuration Filter as in the add-in.
6. Pick Use this version of SOLIDWORKS. For release workflows, enable Get latest revision only; it exports the version tied to the newest revision.
7. Attach the task to a workflow transition, leave it in the right-click menu, or run it from Scheduled Items.

Settings that matter for IFC

Setting	What it does	Tip
Export location	Output folder: vault, relative, UNC or outside. Created if missing.	(TopAssemblyFolder)\Exports\(Revision) works; no trailing backslash.
Filename	Static text, placeholders, custom properties or PDM variables.	(ConfigurationName) for configurations, (Revision) for released files.
File formats	Tick IFC (ifc); invalid formats are dropped.	Several formats per job.
Export references to file formats individually	One file per part and sub-assembly, beside the top-level export.	Task: needs a BOM Template with name, configuration and quantity columns.
Convert multiple configurations	Every assembly configuration, not just the active one.	Needs a configuration-specific filename.
Configuration Filter	Include or exclude by name or wildcard.	Pick names from open documents, or type PROD*.

Naming and folders

Placeholders resolve when the job starts, so every file is named the same way:

• (FileNameWithoutExtension)-(Revision): Skid-1200-C.ifc in (TopAssemblyFolder)\Exports\IFC.
• (FileNameWithoutExtension)-(ConfigurationName) with Convert multiple configurations: Skid-1200-LH.ifc, Skid-1200-RH.ifc.
• (VaultRootFolder)\BIM Handover\($ProjectNumber)\(TargetExtension) in the task: an ifc folder per project next to the step folder from the same task.

Customize Location (Premium in the add-in, standard in the task) gives ifc its own folder. IFC usually goes to the customer’s BIM share while STEP and PDF stay in the vault, so give ifc its own location.

Tips and troubleshooting

• IFC needs a Premium key, entered under PDMPublisher > License Key. The PDM task is licensed per vault, 7-day trial, every format included.
• Invalid formats for the source type are dropped; some depend on the SOLIDWORKS version where the job runs.
• Leave Export references to file formats individually off for a typical BIM handover: one IFC is easier to place than dozens of component files.
• Missing references? The job needs local copies of every reference. Get Latest first.
• Can’t see the exported files? You need add and edit permission in the export location. The vault root is usually locked; target a subfolder like (VaultRootFolder)\Exports.

Availability

Available in PDMPublisher for SOLIDWORKS (the add-in) and PDMPublisher for PDM Professional (the task).

Documentation and related features

• Run a Publish Job (PDMPublisher for SOLIDWORKS)
• File Formats option
• SOLIDWORKS assembly documents
• Extension-specific export locations
• Publishing profiles and company settings
• Run as a SOLIDWORKS PDM task
• Convert SLDPRT to IFC
• Convert SLDASM to STEP
• Convert SLDASM to 3D PDF

Frequently asked questions

How do I export a SOLIDWORKS assembly to IFC for Revit?

Tick IFC under File formats, set location and filename, and Publish with the assembly open. You get one IFC of the whole assembly; a PDM task does the same on a workflow transition.

Can I export IFC and STEP of the same assembly in one run?

Yes. Every ticked format comes out in one pass, each to its own folder with Customize Location.

Can I get one IFC per assembly configuration?

Yes. Enable Convert multiple configurations and add (ConfigurationName) to the filename.

Is IFC available in the free Community Edition?

No. Community Edition does PDF, DXF and STEP only. IFC needs Premium in the add-in; the PDM task includes all formats.