Theegarten-Pactec — start here¶
RapidDraft pilot prep for Theegarten-Pactec (packaging machines, Dresden).
Written for mechanical engineers and engineering leads preparing a customer demo.
In one sentence¶
Before a module is released in CIM Database, RapidDraft checks the drawing + BOM package, flags issues with clear references, and leaves release approval with the engineer.
Read in this order¶
| Step | Page | Why |
|---|---|---|
| 1 | What they need | Marcel’s requirements — what must be true for a “yes” |
| 2 | Use cases & problems | Pain points and use cases from emails & research |
| 3 | Their tools | SOLIDWORKS, EPLAN, CIM Database — how they work today |
| 4 | Release check demo | The 60‑minute story we show in the meeting |
| 5 | PLM integration | How we connect to CIM Database (high level) |
| 6 | Data security | On‑prem / controlled environment — their hard gate |
| 7 | Demo day checklist | Timing, slides, what not to say |
Later / optional: Quality forms · Pilot & next steps · Glossary
Customer leave-behind: Brief (EN) · Kurzfassung (DE)
Internal only: Cerpro comparison · All source files
Demo example (what we walk through)¶
Module: folding unit / sensor bracket assembly (typical packaging-machine change)
- SOLIDWORKS drawing updated
- BOM changed
- EPLAN sensor reference affected
- Package goes to release in CIM Database
- RapidDraft reviews → numbered findings (sheet, zone, BOM line)
- Engineer approves or rejects — PLM stays in charge
Details: Release check demo
Account facts¶
| Company | Theegarten-Pactec GmbH & Co. KG, Dresden |
| Product | Packaging machinery (food / confectionery / non-food) |
| Mechanical CAD | SOLIDWORKS |
| Electrical | EPLAN |
| PLM | CIM Database (CONTACT Software) |
| Key contact | Dr.-Ing. Marcel Eggert (Engineering) |
| LOI date | 26.05.2026 — pilot scope agreed in principle; SOW still to write |
Four things that decide the deal¶
- Controlled deployment — data and AI in their environment, not public cloud by default
- CIM Database fit — not a side tool; works with release workflow
- Drawings + BOMs — concrete checks, not generic chat
- Traceability — every finding points back to a drawing or BOM line; engineer signs off
Expanded checklist: What they need
What this is not¶
- Not a PLM replacement
- Not autonomous release
- Not “AI transformation” slides
- Not supplier EMPB automation as the first demo (that’s phase 2: Quality forms)