Auto‑Configure

Products › ProcessWorks

Standalone Application

ProcessWorks

ProcessWorks is an independent application for copying or moving multiple SOLIDWORKS models — parts, assemblies and drawings — together with every reference they depend on, accurately, from one location to another. It shows you the full dependency tree before you act, lets you choose exactly what moves, and keeps custom properties consistent on every copy it creates.

Request a demonstration See how it works

The problem it solves

Relocating a SOLIDWORKS model is rarely just one file

A single assembly can reference dozens of parts, sub-assemblies and drawings, each pointing to the others by path. Moving or copying that library by hand, in Windows Explorer or SolidWorks alone, risks leaving a reference behind or pointing it at the wrong location. ProcessWorks is built specifically to prevent that.

  • Maps the complete dependency tree before any file is touched
  • Moves or copies only the models you explicitly select
  • Keeps every reference between parts, assemblies and drawings intact at the destination
  • Applies your organization's standard custom properties to the result automatically
  • Logs every operation, so a broken or unloaded reference can be traced and corrected later

Capabilities

Two sets of tools, working together

ProcessWorks pairs a dependency-aware move/copy engine with a full property management layer, so relocated models are not just intact — they're standardized.

Move & Copy

Accurate relocation, with full visibility

  • Dependency explorer lists every reference a model depends on before any operation runs
  • Select precisely which parts, assemblies and drawings to include from the full tree
  • References between included models are remapped correctly at the new location
  • Built-in viewer previews each part, assembly and drawing without opening SolidWorks
  • Supports both copy, leaving the source untouched, and move operations
  • Logging mechanism records every operation for later review

Properties & Standards

Consistent metadata on every model

  • Property Manager pages show complete model information at a glance
  • Add, update or delete custom properties on any individual model
  • Define standard custom properties, organized into groups, once for the organization
  • Map property groups to the model types or templates they apply to
  • Moved or copied models automatically carry the correct, up-to-date property set
  • Removes the need to re-enter or correct properties by hand after every relocation

How it works

From dependency tree to a clean, standardized copy

  1. 01

    Explore

    Open a model and let ProcessWorks map its full set of dependencies — every referenced part, assembly and drawing.

  2. 02

    Select

    Choose exactly which models from that tree should be included in the move or copy, previewing any of them in the built-in viewer first.

  3. 03

    Standardize

    Apply your defined custom property groups, so the resulting models carry the correct, consistent metadata.

  4. 04

    Move or copy

    Run the operation with references remapped automatically, and a full log recorded for later reference.

Why teams use it

Built for libraries too large to move by hand

  • Eliminates the broken or misdirected references that come from relocating files manually
  • Gives a single, complete view of a model's dependencies before any file is touched
  • Keeps custom properties standardized across every model a team relies on, not just the ones edited by hand
  • Lets a reviewer check a part, assembly or drawing in the built-in viewer without opening SolidWorks itself
  • Turns a broken reference, discovered later, into something traceable and fixable rather than a mystery

Frequently asked

Questions about ProcessWorks

Does ProcessWorks move parts, assemblies and drawings together?

Yes. It follows the full reference tree across all three document types, so a move or copy keeps parts, their assemblies and their drawings correctly linked at the new location.

What happens if a reference is broken or unloaded?

ProcessWorks logs the operation, so a broken or unloaded reference can be identified and corrected in a later pass rather than discovered by accident.

Can we define different property sets for different model types?

Yes. Standard custom properties are organized into groups and mapped to the model types or templates they apply to, so the right set is applied automatically.

Does a copy operation change our source files?

No. A copy operation leaves the source model untouched; properties and reference updates are applied to the new copy. A move operation relocates the source itself.

Can I review a model before moving it?

Yes. The built-in viewer lets you inspect a part, assembly or drawing directly inside ProcessWorks before deciding whether to include it.

See ProcessWorks on your own model library.

Send us a representative assembly and we'll show you its full dependency tree in ProcessWorks.

Request a demonstration