Release check demo

The one story for the 60‑minute meeting: AI-assisted release check for a modified machine module.

← Start here · Problems this solves: Use cases & problems

---

Example module

Folding unit / product guide / sensor bracket assembly — typical packaging-machine change (mechanical + electrical + PLM).

---

Eight steps (walk through in this order)

#	What happens
1	Designer updates SOLIDWORKS drawing
2	BOM changes (new bracket line)
3	EPLAN sensor reference affected
4	Package prepared for release in CIM Database
5	RapidDraft reads released drawing + BOM + metadata
6	Findings list — each item links to sheet/zone or BOM line
7	Draft change summary for the release record
8	Engineer approves — PLM status only changes after human sign-off

---

What the mechanical engineer gets

• Missing or unclear dimensions and title-block fields flagged before release
• Drawing revision checked against BOM and PLM status
• GD&T / tolerance issues surfaced as review items (not auto-fixed)
• Every finding: where on the drawing, which rule, what to do

No automatic release. No replacement of SOLIDWORKS.

---

What other disciplines see (same demo)

Role	Benefit
Electrical	Bracket move vs EPLAN device tag mismatch
PLM owner	Incomplete change package before workflow closes
Quality	Inspection-relevant tolerance/datum flags
Shopfloor	Plain-language assembly impact in change summary

---

Roadmap (say once, briefly)

We grow capability in order — not four separate products:

1. Drawings — release checks (this demo)
2. BOMs — consistency across mechanical / electrical / PLM
3. Process — complete change packages
4. Automation — revision text, action lists (later)

Supplier quality forms (EMPB, inspection plans): Quality forms — phase 2.

---

Words to use

Say	Avoid
Release quality check	AI chatbot
Findings with source links	Black box
Engineer approves	Auto-release
Fits CIM Database workflow	Replace PLM

---

Next

Demo day checklist — minute-by-minute agenda.