How MJR Woodworks Is Consolidating Three Engineering Programs into One with INNERGY Engineering
"I don’t see any reason to keep it when Engineering is going to have virtually the same tools. And actually even more."
About MJR Woodworks
MJR Woodworks builds and installs custom cabinetry and architectural millwork out of Apopka, Florida, just west of Orlando. Owned by Matthew and Jason Ryan, the shop runs its own fabrication and installation crews.
Engineering at MJR is led by Shawn Hammond, who started on the shop floor laminating parts fifteen years ago and moved into the office a decade back. His stack, until now, has been three separate programs: a legacy CAD/CAM package for standard casework, a standalone CAM tool that holds the post for an older CNC, and a 2D drafting subscription for custom work the primary tool cannot handle.
MJR is implementing INNERGY Engineering as a single replacement for all three. The rollout is deliberately parallel, with go-live gated on a drill-and-dowel machine and the legacy software kept on hand as a backup.
The Challenge:
- Crashes and slow performance on custom work and large jobs
- Only one person at a time in a job file, forcing file splits and end-of-project merges
- A re-cut loop through a single person four to five times a day when the CNC damages a part
- Three overlapping programs to maintain, each covering a gap in the others
The Solution:
- Concurrent editing so more than one person can work a job, with changes visible immediately
- Cloud access so engineering is not tied to one workstation
- Native 3D modeling for the custom geometry that previously required a separate program
- Role-based shop access so a CNC operator can re-cut a part without touching anything else
Early Results:
- A full cabinet cut and assembled through INNERGY Engineering at an on-site Kaizen event
- Product changes shipped in days after the INNERGY team watched Shawn work his real daily process
- Same-day support from named people instead of a ticket queue
- A parallel rollout with no downside risk smaller jobs first, legacy files kept as backup