RMDB vs JobPack: Two Approaches to Job Shop Scheduling
JobPack focuses on machine monitoring and shop floor visibility. RMDB focuses on finite-capacity scheduling depth. Both target US precision shops but the use case overlap is partial.
The short answer
JobPack is strong on machine monitoring and shop floor data capture for CNC environments. RMDB is stronger on finite-capacity scheduling logic, alternate routings, and what-if analysis. For shops needing both, RMDB + EDGEBI covers monitoring; for shops where monitoring is the priority, JobPack is purpose-built.
Why this comparison matters
JobPack has built its reputation on machine monitoring for precision machine shops — capturing run time, idle time, and downtime reasons directly from CNC controllers. Their shop floor visibility module is widely respected in the US machine shop community.
The scheduling side of JobPack is more capacity-loading than finite-capacity APS. It tracks what jobs are loaded on what machines and how long they will take, but it does not handle the constraint-aware sequence optimization that schedulers typically mean by "finite-capacity scheduling." For shops where the scheduling problem is sequencing and constraint management, the JobPack scheduling depth often does not match expectations.
RMDB is built for the scheduling depth specifically — sequence-dependent setup times, alternate work centers, what-if branching, and constraint-aware automatic optimization. The visualization sidekick EDGEBI provides interactive Gantt and machine monitoring. For shops choosing between the two, the question is whether monitoring or scheduling depth is the bigger pain. Often the answer is both — at which point RMDB + EDGEBI is the more complete fit.
Feature-by-feature comparison
An honest side-by-side look at the capabilities buyers ask about most.
| Capability | RMDB | JobPack |
|---|---|---|
Finite-capacity scheduling | ||
Drag-and-drop Gantt | ||
Sequence-dependent setup modeling | ||
Machine monitoring (CNC data capture) RMDB + EDGEBI covers machine monitoring; standalone RMDB does not. | ||
Real-time shop floor dashboards | ||
OEE tracking and reporting | ||
What-if scheduling scenarios | ||
Alternate work center routing | ||
Multi-level BOM and routings | ||
Integrates with existing ERP | ||
Cloud / on-premise options | ||
Pricing model | One-time license | Per-machine + per-user |
Implementation time (typical) | 5 days–4 weeks | 4–10 weeks |
Best for company size | 10–500+ employees | 15–200 employees |
Industry focus | Discrete manufacturing (broad) | Precision CNC machine shops |
Included · Limited or partial · Not available
Pricing comparison
RMDB
From $5,000
One-time license + optional support
JobPack
Custom (per-machine + per-user)
Subscription with per-machine and per-user components
JobPack pricing is custom and scales with machine count and user count. Typical mid-size shop deployments run $25K–$80K first year. Subscription continues annually. RMDB is one-time licensing with no per-machine fee — a critical difference for shops with 20+ machines where JobPack pricing escalates rapidly.
Where each tool wins
RMDB does this better
- Shops where scheduling depth (sequence-dependent setup, what-if, alternate routings) is the bigger pain
- Operations with 20+ machines where JobPack per-machine pricing escalates
- Manufacturers wanting one-time licensing instead of perpetual subscription
- Shops needing scheduling logic that works across non-CNC equipment too
- Companies that want monitoring + scheduling in one toolkit (RMDB + EDGEBI)
JobPack does this better
- Precision CNC shops where machine monitoring is the highest-priority capability
- Operations with deep CNC controller integration requirements (Fanuc, Mazak, Mori)
- Shops valuing JobPack's specific dashboards and visualization style
- Manufacturers preferring per-machine subscription with bundled service
- Smaller precision shops without complex multi-routing scheduling needs
Which one should you pick?
Choose RMDB if…
Precision shops $5M–$200M where scheduling depth (especially setup-dependent and alternate-routing logic) is the actual constraint, and where one-time licensing economics matter over 5+ years.
Choose JobPack if…
Precision CNC shops 15–80 employees where shop floor visibility and machine monitoring is the primary gap, and where scheduling complexity is modest.
Switching from JobPack to RMDB
A practical migration path that most manufacturers complete in days, not months.
- 1
Audit your real scheduling problem
Is machine monitoring or scheduling depth the bigger pain? If monitoring, JobPack is purpose-built. If scheduling, RMDB is the right tool. If both, RMDB + EDGEBI covers both at one-time license economics.
- 2
Pull historical data from JobPack
JobPack data — machine runtime, downtime reasons, job history — can be exported for analysis. Use it to baseline RMDB scheduling assumptions about cycle time and capacity.
- 3
Configure RMDB work centers and constraints
Map machines, operators, shift calendars, and setup time rules into RMDB. The constraint configuration is where RMDB scheduling depth lives.
- 4
Add EDGEBI for monitoring (optional)
If machine monitoring matters, EDGEBI complements RMDB with interactive Gantt and machine data dashboards. Together they cover the scope JobPack provides plus deeper scheduling.
- 5
Parallel run for 2–4 weeks
Compare schedules generated by RMDB vs JobPack outputs. Validate that promise dates align with shop floor reality before cutting over.
Frequently asked questions
Is RMDB + EDGEBI equivalent to JobPack?+
Functionally similar in scope (scheduling + monitoring), but with different depth profiles. RMDB + EDGEBI has deeper finite-capacity scheduling. JobPack has deeper CNC controller integration. The right answer depends on which capability matters more for your shop.
Does RMDB pull data from CNC machines like JobPack does?+
EDGEBI (the visualization add-on) supports machine data capture from MTConnect, OPC-UA, Fanuc Focas, and Modbus. The depth of CNC integration varies — JobPack has invested heavily in this area and has deeper out-of-box support for common controllers.
How does pricing compare for a 30-machine shop?+
JobPack per-machine subscription for 30 machines + 10 users typically runs $50K–$100K first year and continues annually. RMDB at one-time licensing for the same shop is $15K–$30K total. Over 5 years, the gap is substantial.
Can I migrate from JobPack to RMDB while keeping data?+
Yes — JobPack data can be exported and imported into RMDB. Historical job data, routing standards, and capacity assumptions all transfer. The migration typically takes 2–4 weeks of parallel running.
What about reporting and dashboards — how do they compare?+
JobPack has well-respected dashboards specifically for CNC monitoring. EDGEBI provides interactive Gantt-style scheduling visualization plus configurable shop floor dashboards. Different design philosophies — JobPack is monitoring-first; EDGEBI is scheduling-first with monitoring layered in.
See RMDB on your own data
35+ years helping manufacturers move beyond spreadsheets and underpowered cloud tools. Get a live demo with your real production schedule — no slide deck required.