Skip to content

Checks And Feasibility

Status: Technical feasibility + MVP experiment plan Validation status: Candidate checks only; customer pain not confirmed

This page keeps the product honest. A finding is only credible if the required data exists, the extraction is reliable enough, and the false-positive risk is acceptable at a release gate.

Demo-Safety Rule

Open customer relationships with checks that are both useful and robust.

Consistency / completeness Judgment / missing intent
Robust extraction Safe demo. Ship first: revision mismatch, missing file, blank field, package inventory. Introduce only when customer supplies rules and evidence.
Fragile extraction Use carefully on clean inputs: material note vs BOM material, OCR-heavy notes. Dangerous first demo: bearing-seat intent, GD&T semantics, geometry function.

The moat may live in judgment. The first trust-building demo should not.

Data Layers

Layer Example MVP access method Feasibility
Drawing PDF title block, notes, dimensions upload + OCR/vision high for title block, variable for body notes
BOM export part number, quantity, revision CSV/XLSX upload high
File inventory PDF, STEP, BOM, special-process notes uploaded folder/package scan high
Metadata export lifecycle state, owner, release status CSV/API export medium
CAD export STEP, mass, geometry upload/parser medium
Native CAD NX, SolidWorks, Creo CAD API/plugin later
PLM/PDM Teamcenter, Windchill, SolidWorks PDM export/API later
ERP SAP, Dynamics, proALPHA, Business Central export first, writeback later later
Internal standards checklists, specs, product-family rules upload/RAG/rules medium
Historical failures ECOs, supplier questions, NCRs customer-provided corpus hard but valuable

Candidate Check Library

Check ID Name Class MVP-ready False-positive risk Moat level
RR-001 Drawing revision must match BOM revision consistency yes low low
RR-002 Drawing part number must match BOM part number consistency yes low low
RR-003 Mandatory title-block fields must be populated completeness yes low low
RR-004 Supplier package must include PDF, STEP, and BOM completeness yes low low
RR-005 Material note must match BOM material field consistency maybe medium medium
RR-006 Part class requires surface treatment note standards needs customer rule medium medium
RR-007 Bearing seat should include fit/tolerance callout intent no high high if validated
RR-008 Similar past failure exists for this product family historical later medium/high high

Customer-Discovery Check Candidates

Candidate Source signal Required data Feasibility First demo risk
NX drawing setup matrix check Volocopter / Vinicius NX drawing export or validation data + company setup matrix medium low if rules are explicit
Volohammer / Check-Mate companion Volocopter / Vinicius validator report, rule mapping, drawing metadata medium/high if exports exist low if it explains existing validation rather than replacing it
Fastener dimension search Volocopter / Vinicius + Aaron part dimensions, CAD/PLM records, expected query hits medium/high if scoped to fasteners medium because similarity expectations must be clear
NX/PLM/ERP federated search Volocopter / Aaron CAD/PLM identifiers, ERP material data, join keys, read-only exports medium medium/high because integration scope can sprawl
ERP/CAD master-data suggestion Theegarten/Bauer signal CAD metadata, BOM, similar ERP item records, mandatory field schema medium/high low if suggestions stay human-approved
Custom-request to prior-design retrieval Bauer customer request text + design history + metadata/documents medium medium because "similar enough" is subjective
Bauer senior-engineer matching memory Bauer / Wolf Goetze accepted/rejected prior-design matches + senior rationale medium medium because rules must stay human-approved
Theegarten SOLIDWORKS/BOM release check Theegarten / Marcel SOLIDWORKS drawing, BOM export, CIM metadata, release checklist high if exports exist low/medium if checks stay source-linked
Theegarten CIM findings report Theegarten / Marcel CIM Database deployment/API info, report attachment target medium medium because integration details are tenant-specific
Avilus drawing standards/completeness check Avilus / Franz signal drawing standard, sheet-metal drawing, Teamcenter export high for explicit fields, medium for dimensions low/medium if standards are explicit
Avilus sheet-metal bend table check Avilus sheet metal drawing, bend table, material/thickness rules medium/high if rules exist medium because process assumptions must be customer-owned
Deutsche Aircraft stress input readiness Deutsche Aircraft / Jose V. C. input checklist, load/material/geometry sources, analysis package medium/high if sources are text/structured low/medium if it only flags missing evidence
Deutsche Aircraft load provenance check Deutsche Aircraft / Jose V. C. load reports, analysis input table/deck, load IDs, revisions, units medium if load data is extractable medium because wrong unit/source parsing is dangerous
Deutsche Aircraft secure local stress manual search Deutsche Aircraft / Jose V. C. approved stress manual corpus, benchmark questions, deployment boundary high for retrieval, medium for method recommendation low if citation-only, medium if it suggests methods
Deutsche Aircraft drawing completeness before SAP release Deutsche Aircraft / Evgeny CATIA/3DEXPERIENCE drawing, release checklist, SAP/BOM field requirements high if checklist exists low/medium if human-approved
Deutsche Aircraft CAD metadata to BOM handoff Deutsche Aircraft / Evgeny CAD metadata export, BOM export, field mapping rules high for structured fields low/medium if suggestions stay read-only
Requirement/guideline compliance check R&S requirements/guidelines + component/material/area evidence medium medium/high depending on traceability
Rohde & Schwarz material-by-area compliance R&S / Robin material guideline by area + BOM/material list + area map medium/high if structured medium because area mapping may be ambiguous
Rohde & Schwarz component-purpose explanation R&S / Robin schematic/export, net/component context, requirement notes medium medium/high because intent must be confirmed by engineer
Machine-park DFM rule Ulrich part features + machine capability table + quantity medium medium
Material/CO2 review Dennis part volume, material density, route, scrap factor high for basic calculation low if scoped to calculation, medium if judging process choice

Feasibility Table

Finding Required data Feasibility Main risk
Drawing Rev C vs BOM Rev B title block + BOM row high extraction errors in messy title blocks
Missing ERP material group ERP item template/export high template variation
Missing STEP file package inventory high naming convention variation
Material mismatch drawing note + BOM material medium ambiguous material text and OCR
Wrong food-contact material material note + zone map + family spec hard unless rule supplied false positives and missing context
Bearing seat missing fit callout geometry/function context + mating context + rule hard high false-positive risk

MVP One-Check Demo

The first MVP should not prove the full thesis. It should prove that a real buyer cares when RapidDraft catches one real release failure before handoff.

Principle:

  • one real defect
  • one real artifact type
  • one real buyer
  • one measurable consequence

Candidate demo:

Element Choice
Workflow supplier RFQ package readiness for machine-builder drawings and BOM
Input drawing PDF package, BOM Excel export, supplier package folder
Check drawing/BOM revision mismatch plus missing supplier deliverable
Output issue list, evidence crop, handoff checklist, exportable PDF/CSV
Human action user approves finding and fixes package before RFQ/release

Do not build first:

  • PLM writeback
  • ERP writeback
  • full CAD plugin
  • autonomous release approval
  • generic engineering chat
  • eight industry demos
  • full judgment engine

Open Questions

  • Which one check maps to a real pain story first?
  • Is drawing/BOM revision mismatch too boring to sell, or exactly the trust-building opener?
  • Which customer file format gives the fastest credible demo?
  • Is ERP/CAD master-data completion easier to sell than drawing release readiness because the manual field work is more visible?

Sources