December 31, 2030. That's the day SAP turns off support for SAP MII and SAP ME. No more patches, no more security updates, no more SAP help desk. If your discrete plant is running on MII today — connecting CNC machines, tracking OEE, running ISA-95 workflows, feeding S/4HANA from the shop floor — that backbone has roughly four years left to live. SAP's recommended path is to move to SAP Digital Manufacturing on Business Technology Platform. The honest reality: SAP DM is not a direct drop-in replacement. It is a cloud-mandatory rebuild. For discrete manufacturers with deep custom logic, air-gap requirements, or CNC-heavy operations, that may not be the right fit at all. There is a third path that most consultants don't talk about — keep your existing MES + OEE + ISA-95 stack running on-prem AI hardware, behind your firewall, with source code you own. Pilot in 6 to 12 weeks. Book a free demo of SAP MII transition planning software.
The On-Prem Server Stack — Your MES Backbone Without the SAP Cloud Lock-In
Discrete manufacturing data is sensitive. CNC programs, recipes, supplier pricing, ISA-95 process models — the kind of data your IT security, audit, and legal teams want kept inside your perimeter. Three pieces of NVIDIA hardware sit in your control room, never connect to the public internet, and run your full MES + OEE + ISA-95 stack with deeper analytics than MII ever offered. Book a free demo of on-prem MES migration software.
AT THE SHOP FLOOR
NVIDIA Jetson AGX Orin The Shop Floor Connector
JobTalks to CNC, PLC, SCADA — replaces SAP PCo
SpeedReal-time machine data every second
WhereMounts near the production line, on a rail
FormSmall ruggedized box, fits in switchgear cabinet
What it does: Reads machine data straight from Fanuc, Siemens, Mitsubishi, Heidenhain, Mazak controllers. Buffers data when the network blinks. Sends a clean stream to the MES engine. The direct replacement for SAP PCo + the connectivity side of MII.
CONTROL ROOM · THE BRAIN
RTX PRO 6000 Blackwell The MES Engine
JobRuns MES + OEE + ISA-95 workflows in real time
SpeedSub-second response to operator screens
WhereSits in your control room behind your firewall
FormTower computer, fits under a desk
What it does: Runs your full discrete-manufacturing stack — production orders, routings, work instructions, OEE calculations, traceability, quality holds. Pushes work order status back to S/4HANA via standard APIs. Drop-in replacement for MII transactions + custom logic.
ENTERPRISE · FLEET OEE
NVIDIA DGX Station GB300 Ultra · Fleet OEE Brain
JobAggregates OEE + downtime across plants
SpeedCross-plant pattern matching in hours
WhereSits at corporate HQ in a server rack
FormRack-mounted, 24/7 enterprise grade
What it does: Builds the fleet-wide OEE dashboard your COO needs. Surfaces which plant is best at quality, which is best at availability, which one keeps repeating the same downtime causes. AI-driven analytics MII never had.
100%
Stays inside your building · never goes online
$0/mo
No subscription · buy once, own forever
Offline
Works fully air-gapped if your team requires it
Yours
Source code included · modify it freely
The 2026 → 2030 Migration Countdown — Every Decision Window Mapped
Every quarter you delay shrinks your options. By 2027 SAP stops adding features. By 2028 you're paying premium for extended support. By 2030 the platform goes dark. Here's what each window looks like — and what your team should already have done. Sign up free for SAP MII transition planning software.
NOW
2026
PLANNING WINDOW
WHAT TO DO
Audit every custom MII transaction and dashboard
Run a fit-gap analysis: SAP DM vs on-prem AI vs status quo
Identify air-gap, CNC, and ISA-95 dependencies
Lock budget for FY2027 pilot
FREEZE
2027
FEATURE FREEZE · NO NEW FIXES
RISK
SAP stops mainstream maintenance Dec 31, 2027
Bug fixes only via extended support contracts
No new compatibility patches for newer S/4HANA
You should be 6 months into pilot by now
PREMIUM
2028-29
EXTENDED SUPPORT ONLY
COST
Extended SAP support: premium pricing
Your replacement should be in production now
Last window to migrate cleanly with parallel runs
Skill talent for legacy MII becomes scarce
EOL
DEC 2030
SAP MII + ME GO DARK
FINAL DEADLINE
Zero SAP support · zero patches · zero help desk
Running MII past this date = your team owns every bug
Security audit failures and compliance risk
Plants still on MII pay third-party retrofit teams
Three Real Discrete-Plant Scenarios — How the Hardware Solves Each One
Three real migration challenges from real discrete manufacturers — each one walked through in plain language. Same pattern every time: shop floor connector → MES engine → fleet OEE brain. Book a free demo of SAP MII alternative software.
SCENARIO 01
"Our SAP integrator wants $2.4M and 18 months for cloud migration. Our plant runs CNC machines that cannot go on the public internet. Now what?"
THE PROBLEM
Precision engineering plant. 18 CNC machines, 6 robot cells, full ISA-95 work-in-progress tracking on MII today. SAP DM is cloud-only — the IT security policy bans defense-grade CNC programs from leaving the building. The CIO is being quoted $2.4M for a hybrid SAP DM rebuild with custom edge gateways. 18 months. Outcome uncertain. Meanwhile MII is on borrowed time.
HOW THE HARDWARE SOLVES IT
The Shop Floor Connector (Jetson)
Drops in next to existing PCo connections. Reads from Fanuc, Heidenhain, Mazak controllers via OPC-UA. CNC programs never leave the plant network.
The MES Engine (RTX)
Runs the full ISA-95 stack on-prem: work orders, routings, traceability, OEE. Pushes order status back to S/4HANA via standard SAP APIs — same hooks MII used.
Cutover Plan
Parallel run for 6 weeks alongside MII. Validated against MII output. Cut over module by module. Total time: 11 weeks. Total cost: a fraction of the SAP DM quote.
THE RESULT
MII fully replaced in 11 weeks. Zero cloud exposure of CNC programs. $2M+ saved vs SAP DM quote. Security audit passed.
SCENARIO 02
"We have 12 years of custom MII transactions. SAP DM cannot run them. Do we rebuild all of it or find a different path?"
THE PROBLEM
Automotive supplier with 4 plants. 12 years of custom MII workflows — torque verification, traceability, mistake-proofing, downstream supplier portals. SAP DM has a "drag-and-drop" Production Process Designer that does not cover any of it. SAP partner is quoting 24 months and $4.8M to rebuild every custom transaction from scratch. The COO is asking the IT lead to find another option.
HOW THE HARDWARE SOLVES IT
The Shop Floor Connector (Jetson)
Same OPC-UA, Modbus, REST endpoints MII was reading from. No re-wiring needed. Plant connectivity migrated in days, not months.
The MES Engine (RTX) · Source Code Included
Custom transactions ported using the included source code. Your team owns the logic forever. Some transactions retired (cleanup), some ported, none rebuilt from scratch in a vendor's proprietary designer.
Fleet OEE (DGX)
All 4 plants reporting through one fleet OEE dashboard. Cross-plant pattern matching finds quality issues MII could never spot.
THE RESULT
4 plants migrated in 9 months. All custom transactions preserved. $4M+ saved vs SAP DM rebuild. Fleet OEE up 6%.
SCENARIO 03
"Our auditors need ISA-95 compliance documented. SAP DM in the cloud raises data-residency flags. How do we stay compliant?"
THE PROBLEM
Aerospace subassembly plant. ISA-95 compliance audited annually. EU data-residency rules + customer contracts require all process data to stay within national borders. SAP DM runs on hyperscalers — even with regional datacenters, the audit team has flagged it as compliance risk. The plant needs full ISA-95 + AS9100 traceability without sending a single byte off-site.
HOW THE HARDWARE SOLVES IT
The Shop Floor Connector (Jetson)
Reads from PLCs, CMMs, torque tools. Tags every measurement with ISA-95 hierarchy (Enterprise → Site → Area → Line → Cell). Local buffering means no data loss during network maintenance.
The MES Engine (RTX)
Runs the full ISA-95 process model on-prem. Generates as-built genealogy for every part, every batch. Audit trail with cryptographic hashing means no data tampering possible.
Auditor Export
One-click ISA-95 + AS9100 audit packs. All data stays on-prem. EU data-residency rules satisfied. Source code included means the audit team can verify exactly what runs.
THE RESULT
Annual ISA-95 + AS9100 audit passed cleanly. Zero data left the facility. Compliance risk eliminated. Insurance premiums reduced.
$6M+
Combined savings across the three scenarios vs the SAP DM cloud rebuild path — plus ongoing $0/mo subscription savings, source code ownership, and full data sovereignty. The hardware pays for itself before the first SAP DM consulting invoice would have landed.
Plan Your Transition · Pilot in 6-12 Weeks
Don't Wait for Dec 2030. Plan Your MII Exit Strategy Today.
Every quarter you delay shrinks your options. Book a 30-minute call with our team to walk through your current MII footprint, audit custom transactions, and map a 6-to-12-week path off SAP MII onto on-prem AI hardware. Buy it once, own it forever — no monthly fees, source code included.
What You Get — Everything In One Box, Yours Forever
A pre-configured on-prem MES + OEE stack arrives at your control room. Shop floor connectors, MES engine, fleet OEE dashboard, source code, ISA-95 templates — all loaded. Plug in, validate against MII in parallel, cut over module by module. Sign up free for discrete manufacturing MES software.
Buy Once, Own Forever
No monthly fees. No per-user charges. No annual price increases. Pay one price up front.
Your Data Stays Home
CNC programs, recipes, traceability records — all stays inside your perimeter. Audit and compliance approved.
Source Code Included
Port your custom MII transactions, build new workflows, extend the platform. Not locked in to us forever.
Ready Out of the Box
MES + OEE + ISA-95 + S/4HANA connectors — all pre-loaded. No 18-month consulting project.
Frequently Asked Questions
How does this integrate with our existing SAP S/4HANA?
The MES engine pushes work order status, production confirmations, goods movements, and quality data into S/4HANA via the same standard SAP APIs that MII uses today — IDocs, BAPIs, OData services, REST. From S/4HANA's perspective, it sees clean work order updates flowing in. No SAP-side reconfiguration is required for the core flows. For deeper SAP-side integration, the platform also supports SAP Event Mesh and Integration Suite when you need them.
How fast can we migrate off SAP MII?
From the day you sign the order to the day your team is live on the new platform is usually 14 to 22 weeks. The hardware arrives in 4 to 6 weeks already pre-configured. Once on-site, our team connects it to your existing PLCs, CNC controllers, and S/4HANA. We typically run the new platform in parallel with MII for 4 to 6 weeks, validate every output against MII line by line, then cut over module by module. Total migration: 6 to 12 weeks of live operations, vs the 12 to 24 months SAP DM partners typically quote.
Can our 12 years of custom MII transactions be preserved?
Yes — that's a major reason discrete manufacturers choose this path over SAP DM. The platform ships with full source code, so your existing MII transaction logic can be ported as code modules rather than rebuilt in a vendor's proprietary low-code designer. In practice, migrations typically port 60-70% of custom transactions as-is, modernize 20-30% (cleanup of accumulated tech debt), and retire 10-15% that turned out to be redundant. Your team owns the result forever.
Will it talk to our CNC machines, PLCs, and SCADA systems?
Yes. The Jetson edge connector replaces SAP PCo and the connectivity side of MII. It speaks OPC-UA, OPC DA, Modbus TCP, MQTT, REST, and proprietary protocols for major brands — Fanuc, Siemens, Mitsubishi, Heidenhain, Mazak, Allen-Bradley, Beckhoff, and others. For protocols PCo handled, the migration is essentially "swap the gateway, keep the tags." For custom protocols, source code is included to extend the connector library.
What if SAP eventually offers a better DM version? Are we locked in?
No lock-in. Because the platform runs on standard NVIDIA hardware with source code you own, you can always migrate to a different platform later. The data follows standard formats (ISA-95, IEC 62264, OPC-UA). Many customers see this as the opposite of lock-in — SAP DM is a hyperscaler subscription with vendor-controlled cloud and proprietary low-code designers. Owning your stack on-prem is the path with the most future optionality.
4 Years to MII End-of-Life · 6-12 Weeks to Pilot
Stop Watching the 2030 Clock. Start Building Your Replacement.
Book a 30-minute call with our team. Walk through your current MII footprint. Get a migration plan that fits your timeline and budget. Buy it once, own it forever — no monthly fees, source code included.
