Skip to content

Source Corpus

This page inventories the current source set for the Webasto pilot section.

Scope Rule

The section now contains two core pilot sources plus one supplemental reverse-engineering addendum copied from:

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots\04_Webasto

Completeness rules used for this section:

  • every source file appears on this page
  • every source file has a digest in Source Digests
  • every normalized option lists one or more evidence sources in Options Catalog
  • every source file appears in Coverage Map

Inventory

File Format Source family Primary theme Classification Notes
RapidDraft Opportunities at Webasto Battery & Thermal Systems.md Markdown Deep research memo Company context, workflow reconstruction, pain mapping, pilot wedge Hybrid Strongest source for grounding the Webasto wedge in public process evidence and for separating immediate pilot from later integration.
Webasto battery and thermal workflows_ where RapidDraft can win fast.docx DOCX Strategy memo Fast-win pilot framing, table extraction wedge, 2-3 day prototype shape Hybrid Strongest source for shaping the demo narrative around change packs, release punchlists, and table extraction.
Reverse-engineering Webasto packaging machinery components for a RapidDraft demo.docx DOCX Reverse-engineering addendum Generic packaging-machine parts and revision scenarios for demo construction Supplemental Useful for building visual packaging-style demo assets, but not evidence that Webasto itself sells these machines.

Reliability Notes

The two sources are directionally aligned and reinforce each other more than they disagree.

  • The markdown report is the stronger evidence document for public workflow reality, especially 3DX, 4PEP, OpenPDM, JT, and 3D PDF.
  • The DOCX report is the stronger tactical document for how to convert that reality into a compelling RapidDraft pilot.
  • The reverse-engineering addendum is useful for asset design, but it should not be treated as customer-fit evidence in the same way as the two core sources.

Cross-Source Agreements

  • Webasto's best near-term wedge is battery and thermal documentation, not roof systems.
  • The first pilot should be artifact-first and should not depend on deep CAD-native integration.
  • Change summary and deterministic release checks are core, not optional.
  • A PLM-attachable report is important because Webasto's approvals span multiple functions.
  • Drawing tables are a structurally important problem because Webasto wants more information moved from drawings into structured PLM data.

Cross-Source Differences

  • The markdown report places more weight on the Standard Battery Pro 40 and variant documentation wedge.
  • The DOCX report places more weight on table extraction as the standout differentiator beyond SOMIC.
  • The markdown report gives more attention to manufacturability and service-document alignment as secondary layers.
  • The DOCX report gives a sharper 2-3 day prototype sequence and stronger caution against leaning into NX-first messaging.
  • The reverse-engineering addendum deliberately leaves Webasto's real product stack and moves into generic packaging-machine archetypes, so it is a demo-asset supplement rather than a strategy source.

Source Handling Notes

  • The canonical raw source files are stored under the local _sources folder in this section.
  • The .docx file was reviewed through pandoc for synthesis, but it remains a canonical raw source rather than a separate third corpus item.
  • The reverse-engineering addendum is included in the corpus because it adds usable demo-part guidance, but it does not override the battery and thermal wedge set by the two core sources.

Sources