Teams Collaboration
Version Control: Vault & PDM Integration
In professional engineering, data loss or outdated revisions are catastrophic. Edelweis utilizes a PDM Vault system to act as the "Single Source of Truth," enforcing a strict check-in/check-out environment where every byte of Intellectual Property is versioned and secured.
1. The "Vault" Architecture
Our PDM is a secure database managing relationships between complex CAD files and associated metadata:
Check-In/Out
Files are locked when an engineer is working on them, preventing overwriting conflicts.
Auto Versioning
Every Save creates a minor version; every Approval creates a major revision for instant roll-back.
Metadata Sync
Part numbers and material specs are automatically pushed from CAD to the BOM Structure.
2. Workflow State Management
| State | Permissions | Engineering Goal |
|---|---|---|
| In-Work | Lead Engineer (Write) | Active design and FEA/CFD simulation. |
| Pending Review | Reviewer (Read Only) | Verification against Drawing Standards. |
| Released | Locked (Read Only) | Finalized data for Vendor Communication. |
| Obsolete | Archived | Preserving history while preventing shop floor use. |
3. Change Traceability (The Audit Trail)
Every modification is recorded with a permanent "Digital Fingerprint":
-
•
Engineering Change Orders (ECO): Formal documentation of the who, why, and how of every revision to released parts.
-
•
Where-Used Tracking: Automated identification of every assembly using a specific component to prevent ripple effects.
-
•
Electronic Signatures: Permanent record of accountability for every member and role in the pipeline.
4. Secure External Collaboration
-
•
Automated TDP Export: Vault-triggered generation of TDP packages (PDF, STEP, DXF) upon reaching "Released" state.
-
•
Permissioned Portals: Giving clients view-only access to 3D models and QC Checklists without exposing raw source files.
Technical Directives
| Directive | Protocol |
|---|---|
| Zero Local Saving | Saving files to local desktops is strictly prohibited; all work occurs in the Vault. |
| Mandatory Comments | Every Check-In must include a summary of changes (e.g., "Updated per DFM feedback"). |
| Reference Health | The Vault must perform a "Broken Link" audit daily to ensure Master Modeling integrity. |