Certified SOLIDWORKS® Solution Partner|Built for SOLIDWORKS and SOLIDWORKS PDM Professional|Free Community Edition, no key needed

Conversion guides

Convert SLDASM to IFC for BIM and plant handover

Convert SLDASM to IFC for BIM and plant handover with PDMPublisher: SOLIDWORKS equipment assemblies as IFC for Revit and Navisworks, add-in or PDM task.

The building side wants the equipment envelope as IFC, in the right position and units, ready to place and clash-check against the plant model. PDMPublisher writes the machine or skid as one IFC, with STEP beside it if they also want a CAD copy, in SOLIDWORKS or as a PDM Professional task.

Quick answer

  • Open the assembly, tick IFC (ifc) under File formats on the PDMPublisher tab, set a filename such as (FileNameWithoutExtension)-(Revision), select Publish.
  • Leave Export references to file formats individually off: a BIM coordinator wants the machine or skid as one object.
  • IFC needs Premium in the add-in (the free Community Edition does PDF, DXF and STEP). The PDM task includes every format.

In SOLIDWORKS: step by step

  1. Open the top-level assembly (in a vault, Get Latest first so references resolve).
  2. On the PDMPublisher tab, select Settings > Publish.
  3. Set Export location and Filename, for example (FileNameWithoutExtension)-(Revision). The .ifc extension is added for you.
  4. Under File formats, tick IFC (ifc). Tick STEP as well if the BIM side also wants a neutral CAD copy.
  5. Leave Export references to file formats individually off. One IFC is easier to place and clash-check than dozens of component files.
  6. For every configuration, tick Convert multiple configurations with (ConfigurationName) in the filename; exclude *Flat* in the Configuration Filter.
  7. Select PDMPublisher > Publish, confirm the review dialog, and check Publishing results.

As a PDM task: on every release

PDMPublisher for PDM Professional runs the same engine as a task, so the export happens when the file changes state, not when somebody remembers.

  1. In PDM Administration, right-click Tasks > New Task, choose PDMPublisher, name it and tick the task hosts.
  2. On the Options page set Export Location, for example (VaultRootFolder)\Exports\IFC (no trailing backslash), and the Filename.
  3. Tick IFC (ifc) under File Formats. 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. For release workflows, enable Get latest revision only, then attach the task to a workflow transition.

Settings that matter

SettingWhat to putWhy
Export references individuallyOff for a normal BIM handoverBeside the top-level file; in the task this needs a BOM Template.
Filename(FileNameWithoutExtension)-(Revision)Conveyor-B cannot be confused with Conveyor-C.
Convert multiple configurationsOn, with (ConfigurationName) in the filenameEvery assembly configuration, not just the active one.
Export location(VaultRootFolder)\Exports\IFC, no trailing backslashCreated if missing; you need add and edit permission there.
PDMPublisher Publish settings page in SOLIDWORKS showing Export location, Filename pattern, File formats selector and the assembly export option checkboxes
Settings > Publish: file formats and the options that control references and configurations.

Naming examples

  • (FileNameWithoutExtension)-(Revision) gives Conveyor-B.ifc.
  • (FileNameWithoutExtension)-(ConfigurationName) gives Conveyor-Short.ifc and Conveyor-Long.ifc.
  • (VaultRootFolder)\Customer Packages\($ProjectNumber)\(TargetExtension) in the task files each format in its own subfolder per project.

If something looks wrong

  • Only the top-level file came out: Export references to file formats individually is off (in the task, the BOM Template is missing).
  • Components are missing: the job needs local copies of every reference. Get Latest first. Suppressed, virtual and excluded-from-BOM components are skipped on purpose.
  • IFC is missing from the results: the add-in is running as Community Edition. Activate a Premium key under PDMPublisher > License Key, or use the PDM task.
  • Nothing in the folder: you need add and edit permission in the export location. Target a subfolder, not the vault root.

Keep going

Documentation

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.

Where to next

PDMPublisher for SOLIDWORKS · PDMPublisher for PDM Professional · All features · Conversion guides · Pricing · Documentation · Contact

The SOLIDWORKS add-in is free to start as the Community Edition. The PDM Professional task comes with a 7-day trial. Download the add-in or start the task trial.