CAD Guardian SolidWorks, PDM, manufacturing, and release-process owners
CAD Guardian logo

Public runnable evaluation kit

SolidWorks and PDM Readiness Quick-Start Kit

Score file references, custom properties, BOM readiness, and release-state ownership before cleanup, migration, or PDM automation expands.

Runs public STEP/SolidWorks package checks, writes a JSON report, and shows the SolidWorks API plus PDM add-in handoff boundary.

Download ZIP Open GitHub Repo Consulting Page
git clone https://github.com/tsmithcode/cadguardian-solidworks-pdm-readiness-proof.git && cd cadguardian-solidworks-pdm-readiness-proof
First paid sliceCustom property, BOM, reference, and release-state readiness
Risk removedVault or migration work before file ownership is visible
Best buyerProduct or manufacturing lead with release cleanup pain

Procurement Fit

CAD Guardian LLC · NAICS 541512 · SIC 7373

Entity

CAD Guardian LLC, Delaware LLC, operates this public evaluation kit and the matching SolidWorks/PDM consulting paths.

Offer fit

Drawing/Document Automation Slice, Implementation Build Slice, and PDM/PLM workflow consulting lane.

Boundary

Public runnable proof kit available; private customer artifacts, vault data, credentials, and estimate notes are not exposed.

Direct-Answer Proof

Best for, proof, send-list, next action

Best for

Product teams, CAD/PDM evaluators, and technical reviewers preparing for SolidWorks cleanup, migration, PDM automation, or release repair.

Decision this proves

Whether one product family is ready for a private-sample readiness pass or needs cleanup, PDM state mapping, or a smaller API adapter first.

Proof to review

File reference, custom property, BOM, release-state checks, native examples, and reports/quickstart-report.json.

What to send

The generated report, product family, required custom properties, BOM fields, release states, owners, and approval gates.

Next action

Run the kit and use the consulting page when the readiness boundary is narrow enough for private SolidWorks/PDM review.

Start With the Download

One ZIP, one report, one decision path
  1. 01Download the ZIP or clone the repo from GitHub.
  2. 02Run npm run doctor, npm run verify, then npm run demo.
  3. 03Open reports/quickstart-report.json and compare it with the included docs.
  4. 04Use the native handoff examples only after the package boundary is clear.
npm run doctor && npm run verify && npm run demo

Why Download This Kit

Highest-return use cases first

Download signal

You need a safe proof before touching production SolidWorks files or a PDM vault.

Download signal

You want reference, custom property, BOM, and release-state concerns in one run.

Download signal

You need a concrete handoff from public fixture checks to native SolidWorks or PDM APIs.

Best First Funded Slice

Small enough to trust, useful enough to buy

Custom property cleanup

Identify the fields that drive quote, manufacturing, and release errors.

BOM and reference readiness

Protect trusted file references before migration or automation changes package behavior.

PDM release-state boundary

Keep vault work focused on ownership, state, and approval instead of broad churn.

STAR Story

Interview-ready and buyer-safe

Situation: A product team wants cleanup, automation, or migration, but file references, custom properties, BOM rows, and release states are not trustworthy yet.

Task: Score readiness before a SolidWorks API or PDM add-in touches production files.

Action: Bundle public STEP/SolidWorks fixtures, validate package metadata, and show COM/API plus PDM add-in scaffolds.

Result: A reviewer can run the kit, inspect readiness, and decide when native SolidWorks or PDM execution becomes justified.

Workflow

From request to accepted output
  1. 01Product family request
  2. 02STEP/SLDPRT fixture inventory
  3. 03Custom property check
  4. 04BOM readiness check
  5. 05PDM state map
  6. 06Release package report
  7. 07Manufacturing review
  8. 08Cleanup or pilot decision

Pareto Checks

The few checks that change the decision

File reference inventory

Stops migration or automation from breaking references users trust.

Custom property and BOM readiness

Finds the few fields that drive quote, manufacturing, and release errors.

PDM release-state boundary

Keeps PDM work focused on ownership, state, and approval instead of broad vault churn.

Native Signals

Vocabulary for the licensed runtime
  • SldWorks
  • IModelDoc2
  • IModelDocExtension
  • CustomPropertyManager
  • IAssemblyDoc
  • IComponent2
  • IEdmAddIn5
  • IEdmVault5
  • IEdmCmd

Public Fixtures

Reusable, public-safe evidence

Acceptance Standard

What the downloader should be able to prove

Run confidence: The scripts complete on public fixtures and produce an inspectable report.

Business confidence: The first automation slice is narrow, named, and tied to a repeated human review cost.

Runtime confidence: Native CAD work starts only where the proof names a real licensed-runtime boundary.

Safety Boundary

Public repo hygiene

This repo uses approved public fixtures only. It does not include client drawings, private opportunity notes, credentials, tokens, proprietary files, or license-uncertain assets.

The native examples are handoff scaffolds for the licensed CAD environment, not a claim that every runtime behavior can be validated outside the product.