Skip to content

Options Catalog

This page normalizes the repeated recommendations from the eight SOMIC pilot sources into a canonical option set.

How To Read This Catalog

Each section answers what the option means in practice, why SOMIC would care, what RapidDraft capability it depends on, and which source files recommended it.

1. Revision-before-release review session

  • Canonical name: Revision-before-release review session
  • Source aliases: changes between revisions before release, pre-release review, candidate versus released baseline review, revision-before-release demo pack
  • What it means in practice: A structured review flow where RapidDraft accepts a baseline released artifact set and a candidate revision, then drives comparison, checks, findings, and export in one session.
  • Why SOMIC would care: Florian's email topic maps directly to this problem, and SOMIC's modular machines create many change-driven release decisions.
  • What RapidDraft capability it depends on: review session orchestration, revision pairing, file-package comparison workflow
  • Evidence sources: claude_somic_pilot_strategy.docx, deepresearch_report_somic.docx, deepresearch_report_solidworkspdm.docx, gpt_solidworkspdm.md, claude_solidworksPDM.md
  • Key caveat: This is the safest first wedge because it does not require confirmed PDM stack integration.

2. Change summary / revision diff

  • Canonical name: Change summary / revision diff
  • Source aliases: what changed, visual diff, drawing-to-drawing diff, revision comparison, structured change report
  • What it means in practice: RapidDraft highlights added, removed, and modified content between revisions and summarizes the engineering impact in a form reviewers can use quickly.
  • Why SOMIC would care: The core review bottleneck is reconstructing what actually changed across revisions, especially under time pressure.
  • What RapidDraft capability it depends on: artifact differencing, evidence pointers, summary generation, side-by-side or overlay UI
  • Evidence sources: all eight sources
  • Key caveat: Credibility depends on clear evidence anchors; fuzzy diff output will reduce trust quickly.

3. Release-readiness checklist / DraftLint gate

  • Canonical name: Release-readiness checklist / DraftLint gate
  • Source aliases: release blockers, release gate, deterministic checks, drawing readiness, drawing compliance scan
  • What it means in practice: RapidDraft runs a defined checklist on the candidate revision, such as title block consistency, revision table hygiene, missing notes, dangling dimensions, and standards-related drawing checks.
  • Why SOMIC would care: Drawings are high-cost release artifacts for manufacturing, customer documentation, and service.
  • What RapidDraft capability it depends on: deterministic rule checks, DraftLint, severity classification, report integration
  • Evidence sources: claude_somic_pilot_strategy.docx, deepresearch_report_somic.docx, deepresearch_report_solidworkspdm.docx, gpt_solidworkspdm.md, claude_solidworksPDM.md, perplexity_usesolidworkspdm_withrapiddraft.md
  • Key caveat: Best when positioned as a consistency and coverage layer, not as a claim of full engineering correctness.

4. DFM on representative SOMIC parts

  • Canonical name: DFM on representative SOMIC parts
  • Source aliases: DFM on Haag parts, CNC-milled format tool checks, manufacturability checks, geometry-linked findings
  • What it means in practice: Upload one or more representative STEP parts, likely format tools or machined parts, run DFM, and show geometry-linked findings plus a short exportable summary.
  • Why SOMIC would care: SOMIC has in-house precision parts production in Haag and likely values earlier manufacturability feedback on machined components.
  • What RapidDraft capability it depends on: STEP upload, Part Facts, DFM rule execution, viewer-linked findings, report output
  • Evidence sources: claude_somic_pilot_strategy.docx, deepresearch_report_somic.docx, claude_solidworksPDM.md
  • Key caveat: Useful and impressive, but weaker than revision review if presented as the main wedge instead of a supporting layer.

5. One-click report / release evidence packet

  • Canonical name: One-click report / release evidence packet
  • Source aliases: DFM report, release-ready report, exportable packet, PDF or HTML report, documentation package
  • What it means in practice: A clean export that combines change summary, checklist findings, severity overview, and optionally issue status into a release-friendly deliverable.
  • Why SOMIC would care: SOMIC operates in a documentation-heavy world spanning manufacturing, customer approvals, FAT and SAT, and service.
  • What RapidDraft capability it depends on: report assembly, export formatting, change summary integration, checklist results integration
  • Evidence sources: claude_solidworksPDM.md, claude_somic_pilot_strategy.docx, deepresearch_report_solidworkspdm.docx, deepresearch_report_somic.docx, gpt_solidworkspdm.md, Perplexity_SOMIC Packaging deep dive and RapidDraft pilot focus.md, perplexity_usesolidworkspdm_withrapiddraft.md
  • Key caveat: The report should read like an engineering release artifact, not a product screenshot dump.

6. Issue log / review container / closure workflow

  • Canonical name: Issue log / review container / closure workflow
  • Source aliases: review container, findings to issues, issue closure loop, traceable decision log, review memory
  • What it means in practice: Findings can be turned into owned items with assignee, state, rationale, and carry-forward behavior across revisions.
  • Why SOMIC would care: This helps preserve decision context across design, documentation, production, and later service interactions.
  • What RapidDraft capability it depends on: issue model, review session memory, ownership metadata, status transitions
  • Evidence sources: claude_somic_pilot_strategy.docx, deepresearch_report_solidworkspdm.docx, deepresearch_report_somic.docx
  • Key caveat: Valuable as a differentiator, but may not require full implementation in the first demo if a thin slice tells the story clearly.

7. SOMIC 434 / QuickChange / format-variant demo scenario

  • Canonical name: SOMIC 434 / QuickChange / format-variant demo scenario
  • Source aliases: SOMIC-like machine model, format portfolio scenario, variant engineering, QuickChange demo, 434 platform story
  • What it means in practice: Build the demo story around SOMIC's modular packaging platform and show how RapidDraft helps compare or document variant and format changes.
  • Why SOMIC would care: It reflects their actual product language and increases emotional resonance in the meeting.
  • What RapidDraft capability it depends on: scenario framing, representative model choice, change-summary demo, documentation export
  • Evidence sources: Perplexity_SOMIC Packaging deep dive and RapidDraft pilot focus.md, deepresearch_report_solidworkspdm.docx, deepresearch_report_somic.docx, claude_somic_pilot_strategy.docx
  • Key caveat: Strong narrative fit, but can become too broad if it drifts into full configurable machine engineering instead of a focused review workflow.

8. Folder-based or export-based pilot integration

  • Canonical name: Folder-based or export-based pilot integration
  • Source aliases: watched folder, export hook, file-system listener, metadata-only bridge, read-only integration
  • What it means in practice: Engineers export PDFs or STEP files into a known location, and RapidDraft picks them up for comparison and report generation without deep system customization.
  • Why SOMIC would care: It keeps adoption friction low and avoids early dependency on a confirmed vault or PLM API.
  • What RapidDraft capability it depends on: file intake, baseline-candidate pairing logic, output placement, minimal integration glue
  • Evidence sources: claude_solidworksPDM.md, gpt_solidworkspdm.md, deepresearch_report_solidworkspdm.docx
  • Key caveat: This is often the best first integration path when actual customer stack details are still uncertain.

9. PDM task / dispatch integration

  • Canonical name: PDM task / dispatch integration
  • Source aliases: dispatch action, task add-in, workflow-triggered task, run RapidDraft QC on transition
  • What it means in practice: A defined workflow event in PDM launches RapidDraft automatically when a file enters review or release.
  • Why SOMIC would care: It aligns RapidDraft with existing release habits instead of creating a parallel process.
  • What RapidDraft capability it depends on: external trigger contract, background job handling, report callback or storage, stable derivative generation
  • Evidence sources: claude_solidworksPDM.md, gpt_solidworkspdm.md, perplexity_usesolidworkspdm_withrapiddraft.md
  • Key caveat: High practical value if SOMIC is truly on SolidWorks PDM, but it should stay conditional until stack confirmation.

10. Full PDM API / add-in / data-card write-back

  • Canonical name: Full PDM API / add-in / data-card write-back
  • Source aliases: native PDM add-in, vault API integration, workflow-triggered add-in, variable write-back, release blocking
  • What it means in practice: RapidDraft becomes a vault-aware extension that can read versions and references directly, compare them, and write back status or report metadata.
  • Why SOMIC would care: This is the deepest path to making RapidDraft part of the real release gate.
  • What RapidDraft capability it depends on: Windows COM or PDM API integration, vault authentication, metadata mapping, write-back operations
  • Evidence sources: claude_solidworksPDM.md, gpt_solidworkspdm.md, perplexity_usesolidworkspdm_withrapiddraft.md
  • Key caveat: Highest integration depth and greatest stack risk; usually too heavy for the first SOMIC sprint.

11. Store-back of reports into PDM or PLM

  • Canonical name: Store-back of reports into PDM or PLM
  • Source aliases: attach report to revision, store back to vault, attach back to PLM, related document linkage
  • What it means in practice: The export from RapidDraft is persisted next to the candidate or released artifact so it becomes part of the record.
  • Why SOMIC would care: The value of a release packet increases if it lives with the revision it describes.
  • What RapidDraft capability it depends on: output artifact creation, external document linkage, optional metadata write-back
  • Evidence sources: deepresearch_report_solidworkspdm.docx, deepresearch_report_somic.docx, perplexity_usesolidworkspdm_withrapiddraft.md
  • Key caveat: Strong follow-on once stack is known, but not necessary for a first proof of value if exports can be shown manually.

12. Cross-project analytics / reuse / metadata-driven analysis

  • Canonical name: Cross-project analytics / reuse / metadata-driven analysis
  • Source aliases: metadata-driven analysis, search-driven batch review, cross-project insights, family analysis, reuse metrics
  • What it means in practice: Use vault metadata, references, or project context to batch-analyze drawing families, detect inconsistency, or enrich search and reuse patterns.
  • Why SOMIC would care: SOMIC's modular platforms and repeated format structures make family-level reuse analysis potentially valuable.
  • What RapidDraft capability it depends on: metadata ingestion, batch processing, comparison aggregation, reporting over families
  • Evidence sources: Perplexity_solidworks_PDM.md, perplexity_usesolidworkspdm_withrapiddraft.md
  • Key caveat: Interesting strategically, but not a likely first-pilot close driver compared with revision review.

13. Future path: NX-guided drawing generation or deeper PLM coupling

  • Canonical name: Future path: NX-guided drawing generation or deeper PLM coupling
  • Source aliases: NX-guided drawing generation, Teamcenter save-back, deeper PLM integration, product roadmap follow-on
  • What it means in practice: Extend the SOMIC pilot story into a future product capability for controlled drawing generation and tighter PLM persistence.
  • Why SOMIC would care: Valuable only if their confirmed environment or later requirements point in that direction.
  • What RapidDraft capability it depends on: drawing generation stack, template control, PLM integration, save-back semantics
  • Evidence sources: deepresearch_report_somic.docx
  • Key caveat: Keep this clearly separated as roadmap, not current pilot scope.

14. Optional teaser: cost estimation

  • Canonical name: Optional teaser: cost estimation
  • Source aliases: cost estimation teaser, route comparison, rough machining estimate
  • What it means in practice: Show a light estimate or route comparison for one representative machined part.
  • Why SOMIC would care: It can add commercial intrigue when tied to machined format parts or part-production tradeoffs.
  • What RapidDraft capability it depends on: costing logic, manufacturing-route inputs, simple estimate presentation
  • Evidence sources: claude_somic_pilot_strategy.docx
  • Key caveat: This is a teaser only in the corpus. It should not displace the core revision-review story.

Open Questions

  • Which of the medium-consensus options should become explicit demo commitments versus supporting narrative only?
  • Do we want to collapse some of the PDM-heavy options further once SOMIC confirms their real workflow?

Sources