Why System Integrators Switch from Kepware: 5 Real Reasons

Kepware is the default for industrial connectivity, and for many projects it's the right choice. But on CNC-heavy integrator projects we hear five specific patterns over and over from teams that started on Kepware and switched away. None of them are about Kepware being a bad product - they're about category mismatch on CNC monitoring scope.

TL;DR: Five Patterns We Hear from Integrators

1. Per-connection pricing erodes margin past 15–20 machines.
2. CNC driver coverage gaps force hardware workarounds for non-standard brands.
3. No built-in analytics - customer sees raw tags, not OEE.
4. Configuration time on multi-machine projects exceeds budget.
5. Customer pressure to demonstrate value within weeks, not quarters.

If you've felt one of these, you're not the first.

Reason 1: Per-Connection Pricing Erodes Margin on Multi-Machine Projects

The first quote looks competitive. The 30th machine quote feels different. By the 60th machine, license fees are eating most of your project margin.

KEPServerEX prices by simultaneous connection count with tiered jumps. Adding the 51st machine bumps you to the 100-connection tier, even if you're using 51. PSP at ~20% per year compounds. On a 50-machine CNC project the connectivity layer alone runs $30,000–$60,000 year-1, which doesn't include dashboards. See Kepware Pricing for CNC for full math.

Integrators with sub-50-machine deals can absorb this. Past that, the numbers stop working - switching to per-machine pricing models recovers 15–30% of project margin. See Per-Machine vs Site Licensing.

Reason 2: Limited Out-of-Box CNC Driver Coverage

Kepware ships drivers for Fanuc Focas, Siemens (S7, OPC UA), and Mitsubishi MELSEC. Comprehensive PLC coverage. Then the CNC story gets thinner:

Older Mazak and Okuma Controllers

Older Mazak Mazatrol without MTConnect: no native path. Either install SmartBox hardware (per-machine cost) or use a generic adapter. Okuma OSP: MTConnect works for current generations; older OSP requires custom or third-party.

Brother, Citizen, Star, Tornos

These specialized brands rarely have first-party Kepware drivers. Brother CNC Net, Citizen Cincom protocols, Tornos integration - usually requires custom adapter work or third-party hardware.

Heidenhain Outside Standard DNC

Standard Heidenhain DNC works. Older iTNC 530 without standard DNC option, or specific data points outside standard DNC - generic and limited compared to specialized CNC platforms.

For pure-Fanuc / pure-Siemens projects, Kepware coverage is fine. For mixed fleets with any specialty brand, you spend hours finding workarounds that a CNC-specialist platform handles natively.

See CNC Connectivity Vendors Matrix for per-brand coverage detail.

Reason 3: No Built-In Analytics - Customer Sees Just Tags

The customer-facing problem: "We installed Kepware. Where's the OEE dashboard?"

Kepware delivers tags. OEE calculation, downtime classification UI, andon screens, shift reports, alert configuration, mobile views - all delivered by something built on top. Power BI, ThingWorx, Grafana, custom React, all viable. All separately priced and separately implemented.

For integrator projects, this means: - 200–600 hours of dashboard build per project. - Customer-side training on a different tool than connectivity layer. - Maintenance burden on two stacks. - Customer paying twice (Kepware + dashboard tool).

CNC-specialist platforms (MDCplus, MachineMetrics, Predator) bundle the analytics layer. Customer sees OEE within days of go-live, not months.

Reason 4: Steep Configuration Curve for Small Teams

KEPServerEX is powerful and configurable. The cost of that flexibility is configuration time.

Tag groups, scan rates, advanced tags, alarms and events, IoT Gateway endpoints, redundancy, security - the full stack takes a real engineer 4–8 weeks to internalize for production work. For an integrator with two or three engineers handling everything from pre-sales to support, that's a meaningful tax.

Specialist platforms with pre-built tag templates and per-brand profiles cut this dramatically. New machine onboarding: 30 minutes vs 4–8 hours.

Reason 5: Customer Pressure to "Show Value" Faster

The biggest deal-killer in 2026 is timeline. Customers committing budget for monitoring expect visible results within weeks, not "after the dashboard build sprints in Q3."

A typical Kepware-based monitoring project: 2 weeks discovery + 2 weeks tag mapping + 4 weeks dashboard build + 2 weeks UAT = 10 weeks before the customer sees OEE. With a CNC-specialist platform: 2 weeks tag mapping + 2 weeks UAT = 4 weeks to OEE.

For competitive deals where another integrator has promised 6 weeks to value, the platform choice has already happened.

What Switching Actually Looks Like (Honest Account)

Switching mid-deployment is not free. Realistic accounting for a 30-machine switch from Kepware to MDCplus: - Discovery and tag inventory: 1 week. - Parallel deployment (both running): 2–3 weeks. - Tag remapping: 1–2 weeks (largely mechanical for standard CNC data). - Customer UAT and acceptance: 1 week. - Decommission Kepware: 1 week.

Total: 6–8 weeks for 30 machines. See Migrate from Kepware to MDCplus for the full method.

Costs include vendor migration support and potential overlap on Kepware PSP if mid-cycle. Net savings typically pay back within 12–18 months on an active project.

What Kepware Still Does Better

To stay balanced - and because this is critical for honest customer conversations:

• Mature, broad ecosystem. 30+ years of references, decades of edge-case support.
• Best-in-class for mixed device fleets. CNC + PLC + drives + sensors + IT systems all under one tag tree.
• Deep PTC integration. If customer is on ThingWorx or Vuforia, Kepware native fit.
• Massive third-party tooling. Custom integrations, niche drivers, community knowledge.
• Enterprise procurement familiarity. IT departments know it; security review is fast.

For projects centered on PLC/SCADA where CNCs are part of a wider scope, Kepware remains the right answer.

Decision Checklist: Should You Switch?

Score each - switch if 4+ apply:

1. Project is >70% CNC machines.
2. Customer wants OEE/dashboards live within 8 weeks.
3. Fleet has any specialty brand (Mazak older, Heidenhain iTNC, Brother, Okuma) Kepware doesn't cover natively.
4. Per-connection licensing is the largest project line item.
5. Internal team is small and dashboard-build hours are a constraint.
6. Customer has explicitly asked "where is the OEE?"
7. Project will expand to 50+ machines or multi-site within 24 months.

Frequently Asked Questions

Is switching always the right answer?

No. For projects where Kepware fits the scope, stay. For projects where the patterns above are eating margin and customer satisfaction, evaluate alternatives.

How long does customer adoption of new platform take?

For operators and supervisors: 1–2 weeks of light training. For administrators: 2–4 weeks. For IT/security review: depends on customer rigour, typically 2–8 weeks.

Can I keep Kepware for PLCs and switch CNCs only?

Yes - common pattern. Kepware on PLCs, MDCplus on CNCs, both feeding the historian or downstream system.

Will I lose data history during migration?

If you plan parallel run with historical data preservation, no. Plan tag-mapping and historian continuity carefully. See Migrate from Kepware to MDCplus.

Do customers usually agree to switch mid-project?

Customers care about outcomes, not platforms. If the conversation is "we can deliver OEE and dashboards in 4 weeks vs 4 months by switching connectivity," most agree. Frame the switch as accelerating their result.

What about Kepware Edge?

Kepware Edge (Linux runtime) doesn't change the underlying CNC-specific issues - same per-connection model, same lack of bundled analytics.

What's the typical financial recovery from switching?

15–30% project margin recovery typical when the switch is from Kepware-plus-custom-dashboard to a CNC-specialized platform with bundled analytics. Verify against your specific project.

Is this just MDCplus marketing?

The patterns are real and apply to any specialized CNC platform - MDCplus, MachineMetrics, Predator, Memex MERLIN. We're MDCplus, but the issues exist regardless of which alternative you pick.

Run a Pilot Switch with MDCplus

If one of these patterns fits your active project, request a demo - we'll discuss whether a partial switch (one cell, one brand) makes sense before committing to full migration. Or try MDCplus free on a single machine.

• CNC Connectivity Software for Integrators (Hub)
• Kepware Alternatives
• MDCplus vs Kepware
• Kepware Pricing for CNC
• Migrate from Kepware to MDCplus
• Why MDCplus

About MDCplus

Our key features are real-time machine monitoring for swift issue resolution, power consumption tracking to promote sustainability, computerized maintenance management to reduce downtime, and vibration diagnostics for predictive maintenance. MDCplus's solutions are tailored for diverse industries, including aerospace, automotive, precision machining, and heavy industry. By delivering actionable insights and fostering seamless integration, we empower manufacturers to boost Overall Equipment Effectiveness (OEE), reduce operational costs, and achieve sustainable growth along with future planning.