Company
Industry
Engineering
Headquarters
Website
Listen to Case Summary
From SharePoint to a SolidWorks Vault
Cremmjoy designs and builds soft serve and slush machines. The engineering team runs SolidWorks, managing approx. 2,000-component assembly of custom parts and off-the-shelf hardware across four CAD users, expanding to five. Before Sibe, files lived on SharePoint with no PDM system. Cremmjoy adopted Sibe as it moved from prototype development toward production.
"Previous file management relied on a shared drive without any PDM system, but with so many parts we needed better control as designs transitioned from development to production."
Interviewed for this study
Jason Hugenroth
Jason Hugenroth
Founder and CEO
Outgrowing a Shared Drive
Cremmjoy hit three limits managing a 2,000-part machine in SolidWorks on a shared drive.
No version control
Cremmjoy ran its SolidWorks files on a SharePoint shared drive with no PDM. With four engineers working in the same approx. 2,000-part assembly, there was no reliable way to track versions or prevent one person's work from accidentally overwriting another's.
A team and an assembly that kept growing
Headcount was moving from four CAD users to five, with everyone working on the same design files. A shared folder doesn't lock files or show who has what checked out, so coordination fell on the team instead of the system.
Moving from prototypes to production
As Cremmjoy pushed its next-generation machines toward production, it needed release and revision control, a clear record of what's approved and released, that a shared drive can't offer.
The Solution: Sibe
Native SolidWorks Add-in
CAD Engineers check files in and out directly in SolidWorks while Sibe tracks every version, handles assembly references, and keeps a local cache for offline work. No servers to install, no VPNs required, no SQL software to administer. Everything live in under 20 minutes.
Version and revision control
Every check-in creates a version automatically. When a design is ready, it moves through the revision workflow — In Progress, Pending Approval, Released — with released files automatically locked, so no one edits an released design by accident.
Cloud-based, no infrastructure
Sibe runs in the cloud — no servers to maintain, no SQL licenses to manage, no infrastructure to purchase. The team can work remotely from anywhere, and every file syncs to a single central vault in the cloud.
Performance Benchmarks
Metric | Before Sibe | With Sibe |
|---|---|---|
File management | SharePoint shared drive, no PDM | Cloud platform, every version tracked |
Version control | Manual, error-prone | Built-in on every Check-in |
File access | Shared folder, no check-out | Check files out in SolidWorks; |
Release control | None | Revision workflow with release locking |
Setup | Shared drive, no system | Live in under 20 minutes — no servers or VPNs |
Book a free Demo with Ken to see Sibe in action
Ken Maren
Chief Solutions Architect
SolidWorks Expert with 30+ Years Experience
Our Customer Success team will get back to you within one business day to schedule the demo call.
