claude solidworksPDM

Here's the breakdown of SolidWorks PDM and why it matters for your SOMIC pitch: How SolidWorks PDM Works

The basics: SolidWorks PDM is a file vault that lives on a SQL Server database. Engineers install a Windows Explorer shell extension that replaces their normal file browsing. All SolidWorks files (.sldprt, .sldasm, .slddrw) live in the vault, and the system manages check-in/check-out, versioning, and approval workflows.

Versions vs. Revisions — this is where the confusion lives:

  • A version is created every time someone checks a file back in. Version 1, 2, 3, 4... happens automatically. A part might have 15 versions before anyone approves it.
  • A revision (A, B, C... or 1.0, 1.1...) is a label stamped onto a specific version when it passes through a workflow approval. So Rev A might be version 5, Rev B might be version 12.

Between revisions is a grey zone — all those intermediate versions where the part is being changed but hasn't been formally released yet. This is exactly what Florian's email subject refers to ("Änderungen zwischen Revisionen vor Freigabe"). The Workflow System

PDM uses a state machine: files move through states like "Work In Progress → Under Review → Approved → Released." Transitions between states can trigger actions like incrementing the revision number, notifying approvers, or writing values to drawing title blocks. This is configured per-company by a PDM admin.

A typical SOMIC workflow probably looks like: WIP → Engineering Review → Released (possibly with a manufacturing review gate given their Haag production site). Where PDM Falls Short (Your Opportunity)

Comparing versions is painful. There are three ways to do it, and they're all limited:

  1. Visual inspection via Preview tab — you flip between versions manually in the file explorer. No side-by-side, no highlighting. Just your memory and eyeballs.

  2. History Compare command — PDM Professional only. Opens both versions in tiled windows with some color coding, but for assemblies, comparing geometry checks every single component, so it takes a very long time.

  3. SOLIDWORKS Compare Documents — The best option, but: the drawing comparison tool only compares document properties and not individual dimensions or annotations between drawings. There's a DrawCompare tool for deeper drawing diffs, but they need to be completely separate files for that to work — within PDM, you cannot use DrawCompare to compare two different versions of the same file.

So the practical situation at SOMIC is this: When an engineer changes a module between Rev A and Rev B, and Florian needs to review what changed before release (Freigabe), he's either relying on the engineer telling him what changed, or he's doing manual visual inspection. For drawings specifically, there's no automated way to compare dimension changes between versions of the same file.

Other PDM gaps RapidDraft fills:

  • PDM has zero DFM intelligence. It tracks files and workflows but has no concept of whether a part is manufacturable.
  • PDM has no drawing compliance checking. It can verify that title block variables are filled in, but it can't check if GD&T notation is correct or if dimension styles comply with ISO.
  • PDM doesn't generate reports. It tracks approvals, but there's no structured DFM or review report output.
  • The revision table integration only works for metadata (approved by, date, description) — not for engineering content.

Bottom line for the demo: When you show Florian the revision comparison + DFM findings + DraftLint, you're showing him three capabilities that sit in the exact gap SolidWorks PDM can't fill. Frame it as: "PDM manages where your files are and who approved them. RapidDraft tells you what actually changed and whether it's ready to manufacture."

This is the right question. There are several concrete integration paths, and some are surprisingly easy. How SolidWorks PDM is Accessible

SolidWorks PDM stores everything in two places: a SQL Server database (metadata, versions, workflows, variables) and a file vault archive (the actual files). There are three ways in:Here's the picture. There are three integration levels, from easiest to deepest, and each one adds a layer of value for SOMIC. Level 1: Watched Folder / Export Hook (Build in days, demo-ready)

This is the zero-friction entry point. No PDM API needed.

SOMIC's engineers already export STEP files from SolidWorks for various purposes (quoting, supplier communication, simulation). The simplest integration is a watched folder: a shared directory where engineers drop STEP exports, and RapidDraft automatically picks them up, runs DFM + DraftLint, and produces a report.

You could also build this as a PDM Dispatch action — Dispatch is a built-in PDM add-in that lets admins create custom right-click menu actions. SOMIC's PDM admin could add a "Run RapidDraft Check" action that exports the file to STEP and sends it to your service. This takes their admin maybe an hour to configure and feels native to their existing workflow.

What this gets you: Engineers never leave their SolidWorks + PDM environment. They right-click a part, hit "Run DFM Check," and a report lands back in the vault or pops up in a browser. Level 2: PDM API Integration (Build in weeks, the real differentiator)

The SolidWorks PDM API is a Windows COM library — not REST, not cloud. It provides almost complete access to files, references, variables, and metadata. You authenticate with IEdmVault5, then you can traverse folders, get file versions, read data card variables, and even trigger workflow transitions.

Here's what this unlocks for SOMIC specifically:

Automatic revision comparison. Using the API, RapidDraft can pull two versions of the same part file from the vault (e.g., version 5 = Rev A and version 12 = current WIP), export both to STEP, and run a geometric diff. This is the exact thing PDM can't do well — remember, the drawing comparison tool only compares document properties and not individual dimensions or annotations between drawings, and DrawCompare needs completely separate files, so within PDM you cannot compare two versions of the same file.

RapidDraft can show: "Between Rev A and your current working version, face 23 moved 2.3mm, a new pocket was added, wall thickness on rib #4 dropped below the 1.5mm threshold." That's a revolution compared to what they have now.

Workflow-triggered checks. The PDM API lets you build add-ins that fire when a file transitions between workflow states. So when an engineer submits a part for review (WIP → Under Review), RapidDraft automatically runs DFM checks and attaches findings as a PDF report back into the vault. This becomes a digital Q-Gate — the part can't advance to "Released" without a clean DFM report.

Write findings back to PDM. You can write variables back to the data card using the API. Imagine: the data card shows "DFM Status: 3 Critical, 2 Warning" right next to the part's revision and approval status. The reviewer sees this without opening any external tool.

The constraint: The PDM API only runs on Windows machines with the PDM client installed. This means your integration would be a lightweight Windows service or PDM add-in running on the engineer's machine or on a task host server. This aligns perfectly with your Edge Plane / Connector Agent architecture — this IS the SolidWorks connector agent. Level 3: SolidWorks API Direct (Build in months, maximum depth)

Beyond PDM, the SolidWorks desktop API lets you open .sldprt files programmatically, traverse the feature tree, read dimensions, extract geometry, and even run SolidWorks Costing. This would let RapidDraft read native SolidWorks files without STEP export, preserving feature tree history and parametric intent.

This is the long game, but for the SOMIC demo and pilot, Levels 1 and 2 are more than enough. The Strategic Play for SOMIC

Here's how I'd frame this in the meeting with Florian:

Phase 1 (Pilot, now): "Export a few STEP files from your vault, we run DFM + DraftLint, you tell us if the findings are useful." This is zero integration effort on their side.

Phase 2 (If pilot succeeds): "We build a PDM Dispatch action or add-in so your engineers can right-click any part and get a DFM report without leaving SolidWorks. We also hook into your workflow so checks run automatically when parts are submitted for review."

Phase 3 (Partnership): "We connect directly to your vault API. Every revision comparison, every pre-release check, every DFM report — automated, traceable, attached to the right version in PDM. Your Q-Gates become digital."

This is compelling because it doesn't ask SOMIC to change anything about how they work. It layers on top of SolidWorks PDM, fills the exact gaps PDM can't fill (geometry diff, DFM intelligence, drawing compliance), and gets progressively deeper as trust builds. Florian doesn't need to buy new infrastructure or retrain his team — he just gets better information at the points where he already reviews work.