Demo day checklist¶
60‑minute meeting with Theegarten-Pactec — aligned to their agenda.
← Start here · Story: Release check demo
Before the meeting (15 min prep)¶
- What they need — must-have table
- Use cases & problems — pain ↔ use case map
- Data security — deployment slide
- Release check demo — eight steps
- Skim Cerpro comparison — do not mention unless asked
Minute plan¶
| Min | Topic |
|---|---|
| 0–5 | Intro — release checker for SOLIDWORKS/CIM workflow, not PLM replacement |
| 5–15 | Data security — controlled environment, training boundary |
| 15–20 | PLM — CIM read + findings report diagram |
| 20–45 | Demo — sensor bracket module, live or recorded findings |
| 45–50 | Click finding → drawing zone / BOM line |
| 50–55 | Optional: quality forms teaser (Quality forms) |
| 55–60 | Pilot SOW, next steps, leave Brief (EN) |
Bring¶
- Integration diagram (from PLM integration)
- Sample findings report (fictional module or ZG-2451-A03 example)
- Executive brief EN or DE
- Optional:
quality_templates/TP_QualityDocumentation_TemplatePack_v1.0.xlsx
Ask Marcel¶
- CIM Database on-prem or cloud?
- Any failed AI pilot before — why?
- Who configures PLM workflows?
- Which module family for a real pilot?
- German or English for finding texts?
Do not say¶
| Avoid | Say instead |
|---|---|
| AI chatbot | Release quality check |
| Replace CIM Database | PLM stays in charge |
| Cloud-only | Controlled / on-prem path |
| Auto-release | Engineer approves |
| We do everything in the LOI | Phased pilot: drawings + BOM first |
Pilot success metrics (for SOW)¶
- Fewer release defects caught late
- Shorter review time per change package
- Findings with valid source links
- Engineers rate findings as useful
Details: Pilot & next steps