Their tools¶

How Theegarten-Pactec runs engineering today — the stack we must fit into, not replace.

Stack diagram¶

flowchart LR
    SW[SOLIDWORKS\nMechanical]
    EP[EPLAN\nElectrical]
    CIM[CIM Database\nPLM — system of record]
    SW --> CIM
    EP --> CIM

Tool	Role
SOLIDWORKS	3D models, drawings, mechanical BOM
EPLAN	Electrical schematics, devices, electrical BOM
CIM Database	Released parts, drawings, projects, workflows, audit trail

Packaging machines are built as modules and assemblies. A small mechanical change can affect electrical sensors, BOM lines, and release documents together.

How work should flow (with RapidDraft)¶

flowchart TD
    A[Design in SOLIDWORKS / EPLAN] --> B[Release package in CIM Database]
    B --> C[RapidDraft review]
    C --> D[Findings report]
    D --> E[Engineer approves release]

Engineers do not upload random files to a separate AI website.
RapidDraft reads released data from the PLM side.
CIM Database stays authoritative for status and revisions.

Technical detail: PLM integration

CIM Database (short)¶

CONTACT Software PLM — used to consolidate mechanical and electrical data.

What matters for us:

Drawings and parts live in PLM with revision control
Workflow / release states can trigger a review
Public REST / OpenAPI and Catalyst integration layer exist
Available on-prem or cloud — Theegarten’s mode must be confirmed in discovery

We should not claim full API coverage until CONTACT confirms their tenant. Open questions: PLM integration (bottom of page).

What RapidDraft checks (mechanical focus)¶

Check type	Example
Drawing completeness	Missing dimensions, title block, revision
Drawing ↔ BOM	Part numbers, quantities, phantom lines
Revision discipline	Drawing rev vs BOM vs PLM status
Cross-discipline	Mechanical bracket vs EPLAN sensor tag
Release package	Required documents linked before release

Not in phase 1: automatic EMPB / inspection-plan generation (Quality forms).

Next¶

Release check demo — what we show in the meeting.