PLM integration (CIM Database)¶

How RapidDraft connects to CIM Database — for technical discussions with Marcel or IT.

Principles¶

Rule	Why
PLM stays system of record	No second BOM
Read released objects only	Matches engineering process
Write back a review report	Not silent workflow changes in pilot
Run in customer environment	See Data security

Architecture¶

flowchart LR
    CIM[CIM Database]
    RD[RapidDraft]
    SW[SOLIDWORKS] --> CIM
    EP[EPLAN] --> CIM
    CIM -->|trigger + read| RD
    RD -->|findings report| CIM

Trigger: workflow state change (e.g. “ready for release review”) or CONTACT Catalyst event.

Read: part numbers, project, drawing revision, PDF/neutral file from PLM API.

Write: linked document — findings table with IDs, severity, source pointer.

CONTACT integration options (public info)¶

Method	Use
REST / OpenAPI	Parts, projects, CAD documents — CRUD
Catalyst	BOM exchange, engineering changes, events
Cloud webhooks	If they run CIM Database Cloud

BOM and change-object REST names are not fully published — confirm with CONTACT for their tenant.

Open questions for CONTACT¶

Ask before committing to a delivery date:

Full OpenAPI list for their installation?
BOM and engineering changes — REST or Catalyst only?
How to download released PDFs / STEP / neutral formats via API?
Auth: OAuth, API token, or SSO session?
Is API access included in their license?
On-prem vs cloud — which integration path does Theegarten use?

Source: Contact Database Research.md

What to say in the demo¶

“Pilot phase: we read released drawings and BOM metadata from CIM Database and attach a review report. We confirm the exact API map with CONTACT and your IT in week one.”

Honest > promising full workflow automation on day one.