Skip to content

Ratings Matrix

This page scores each normalized option under two lenses.

  • Pilot lens: what it takes to show credibly in the next 2-3 days for SOMIC
  • Product lens: what it takes to implement as a stronger reusable capability

Rating Scale

Complexity

  • 1: trivial glue or polish
  • 2: bounded feature work
  • 3: moderate multi-surface work
  • 4: substantial cross-system work
  • 5: deep integration or platform work

Impact

  • 1: low signal for SOMIC
  • 2: nice-to-have
  • 3: useful
  • 4: strong differentiator
  • 5: likely core reason they say yes

Time

  • Pilot lens: <0.5 day, 0.5-1 day, 1-2 days, 2-3 days, >3 days
  • Product lens: days, 1-2 weeks, 2-4 weeks, 1-2 months, 2+ months

Comparison Table

Option Pilot complexity Pilot impact Pilot time Product complexity Product impact Product time Justification
Revision-before-release review session 3 5 1-2 days 3 5 2-4 weeks This is the corpus-wide center of gravity and the cleanest match to Florian's email topic.
Change summary / revision diff 3 5 1-2 days 4 5 2-4 weeks The strongest single feature across the sources; trust hinges on making it evidence-based, not vague.
Release-readiness checklist / DraftLint gate 2 5 0.5-1 day 3 5 1-2 weeks A deterministic gate reads immediately as useful for release discipline and complements the diff story.
DFM on representative SOMIC parts 2 4 0.5-1 day 3 4 1-2 weeks Strong supporting demo, especially with Haag-style machined parts, but still secondary to revision review.
One-click report / release evidence packet 2 5 0.5-1 day 3 5 1-2 weeks Repeatedly recommended and highly leverageable because SOMIC is documentation-heavy.
Issue log / review container / closure workflow 3 4 1-2 days 4 5 2-4 weeks A strong differentiator, but a thin vertical slice may be enough for the first pilot.
SOMIC 434 / QuickChange / format-variant demo scenario 2 4 0.5-1 day 4 4 1-2 months Excellent narrative wrapper for the demo, but not by itself the primary product wedge.
Folder-based or export-based pilot integration 2 4 0.5-1 day 2 4 days Best low-risk integration path when stack certainty is low and time is short.
PDM task / dispatch integration 3 4 1-2 days 4 5 1-2 months Attractive if SOMIC is truly on SolidWorks PDM, but still conditional on customer environment confirmation.
Full PDM API / add-in / data-card write-back 5 3 >3 days 5 5 2+ months Deep integration upside is real, but it is the highest-risk and slowest path in the corpus.
Store-back of reports into PDM or PLM 3 3 1-2 days 4 4 1-2 months Useful for operational embedding, but the pilot does not need this to prove core value.
Cross-project analytics / reuse / metadata-driven analysis 4 2 >3 days 4 4 1-2 months Strategically interesting, but most sources treat it as an extension rather than a first close lever.
Future path: NX-guided drawing generation or deeper PLM coupling 5 2 >3 days 5 4 2+ months Clearly roadmap material in this corpus, not a near-term SOMIC pilot feature.
Optional teaser: cost estimation 2 2 <0.5 day 3 3 1-2 weeks A light teaser can help, but the sources treat it as optional, not central.

Tier 1: build or polish now

  • Revision-before-release review session
  • Change summary / revision diff
  • Release-readiness checklist / DraftLint gate
  • One-click report / release evidence packet

Tier 2: include if they strengthen the story without derailing it

  • DFM on representative SOMIC parts
  • SOMIC 434 / QuickChange / format-variant demo scenario
  • Folder-based or export-based pilot integration
  • Issue log / review container / closure workflow

Tier 3: mention as next step, not first commitment

  • PDM task / dispatch integration
  • Store-back of reports into PDM or PLM
  • Cross-project analytics / reuse / metadata-driven analysis

Tier 4: roadmap only

  • Full PDM API / add-in / data-card write-back
  • Future path: NX-guided drawing generation or deeper PLM coupling
  • Optional teaser: cost estimation

Biggest Practical Tension

The corpus strongly supports deep PDM integration as a differentiator, but it also strongly supports avoiding stack-dependent execution in the first sprint.

That is why this matrix scores:

  • Folder-based or export-based pilot integration high for pilot practicality
  • PDM task / dispatch integration medium-high but conditional
  • Full PDM API / add-in / data-card write-back low for pilot practicality and high for long-term upside

Open Questions

  • Should we keep both the pilot lens and product lens in future target-company pages, or reserve the two-lens model for deeper pilot dossiers?
  • Does SOMIC's next reply justify moving PDM task / dispatch integration up a tier?

Sources