SolidWorks PDM Environment Setup
Budget: €250 – €750 EUR
The goal is to build a clean, future-proof CAD workspace inside SolidWorks 3DEXPERIENCE PDM. I need working part, assembly, and drawing templates created first, all tailored for mechanical components and kept intentionally light—only the essential planes, materials, and metadata so new users can start modelling without wading through clutter.
Once the core templates are stable, the project expands into title blocks, a consistent custom-property schema, BOM templates tied to those properties, and a straightforward revision control scheme. A simple, logical part-numbering system must accompany the setup so files, assemblies, and drawings flow naturally through PDM with minimal manual entry.
Deliverables
• Part, assembly, and drawing templates (.prtdot, .asmdot, .drwdot) with basic features and mapped properties
• Editable title blocks linked to the custom‐property list
• Custom property list and guidance on adding future fields
• BOM template synced with the property schema
• Revision table and automated revision control rules inside PDM
• Lightweight document (PDF or DOCX) that summarises folder structure, numbering logic, and template usage steps
Everything should plug straight into 3DEXPERIENCE PDM without breaking existing vault rules, and I’ll validate by opening a new file, saving to the vault, and running a quick ECO cycle. Let’s keep the configuration disciplined yet flexible enough for growth.
Once the core templates are stable, the project expands into title blocks, a consistent custom-property schema, BOM templates tied to those properties, and a straightforward revision control scheme. A simple, logical part-numbering system must accompany the setup so files, assemblies, and drawings flow naturally through PDM with minimal manual entry.
Deliverables
• Part, assembly, and drawing templates (.prtdot, .asmdot, .drwdot) with basic features and mapped properties
• Editable title blocks linked to the custom‐property list
• Custom property list and guidance on adding future fields
• BOM template synced with the property schema
• Revision table and automated revision control rules inside PDM
• Lightweight document (PDF or DOCX) that summarises folder structure, numbering logic, and template usage steps
Everything should plug straight into 3DEXPERIENCE PDM without breaking existing vault rules, and I’ll validate by opening a new file, saving to the vault, and running a quick ECO cycle. Let’s keep the configuration disciplined yet flexible enough for growth.