SAP MII is dead. 300+ forced migrations. No motion to reach them yet.
SAP is sunsetting Manufacturing Integration and Intelligence. Every large MII installation becomes a forced migration with no clean path forward. This is the wedge: intercept the decision before the rip-and-replace, with Rhize as the data layer that makes the migration optional instead of mandatory.
A vendor-imposed deadline. The sharpest trigger in the playbook.
Unlike an AI mandate or a compliance worry, this forcing function is dated and unavoidable. SAP set the clock. The buyer is not browsing.
The Atlas proposal said "token support ends 2027, full support ends 2030." Directionally right, imprecise. Use: mainstream maintenance ends Dec 31, 2027 (no patches/features); paid extended maintenance ends Dec 31, 2030 (security/legal only, requires license activation, not automatic).
Triple EOL on one deadline
MII does not fall alone. The whole shop-floor stack hits end of mainstream maintenance on the same Dec 31, 2027 date: the MII/ME application layer, SAP PCo (Plant Connectivity) at the edge, and NetWeaver 7.5 underneath. One deadline, three simultaneous migrations.
SAP hosted a webinar titled "Avoid the Cliff: Transitioning From ME/MII to SAP DM Before Time Runs Out" (Nov 18, 2025). When the vendor calls your situation a cliff, the urgency is not manufactured.
There is no 1:1 migration path. That is the whole opening.
SAP prescribes SAP Digital Manufacturing (DM) on BTP. SAP and every major SI confirm the same thing: existing MII/ME cannot be lifted and shifted. The "we'll just go to DM" reflex hides a multi-year re-implementation.
What does not survive the move to SAP DM
- MII KPIs, UIs, and reports cannot be reused — confirmed in SAP's own DM integration guidance.
- BLS transactions, xMII queries, SSCE pages must be redesigned by hand, not ported.
- Direct database access is eliminated. DM enforces "clean core," API-only. MII allowed low-level DB access and custom tables. That flexibility is gone.
- Custom on-prem Java logic rebuilds as DM workflows or external microservices.
- OEE regression: DM's standard OEE report covers current day + previous day only. Everything historical rebuilds from scratch in Embedded SAC.
- Edge gap: ProdCon (the PCo replacement) is "still evolving," not as robust for complex/high-frequency/regulated work.
A plant running 21 CFR Part 11 batch records through MII cannot move to SAP DM Cloud — GxP validation policy does not permit cloud MES yet. No clear SAP resolution. The default path is closed for regulated manufacturers, which is exactly where Rhize wins.
Compounding factor: many MII customers are mid-S/4HANA migration (same 2027/2030 deadline). Parallel projects, shared SI capacity, day rates reportedly +20% since 2023 and projected +30–50% by 2026–27. Start late, finish in 2030 at peak resource scarcity.
Two paths open at the deadline. Rhize is the second one.
Full SAP DM migration
Rip MII, rebuild every transaction, KPI, and dashboard in a cloud-only clean-core system. 18–36 months, heavy consulting spend, deeper SAP lock-in (DM's proprietary MDOs are the next lock-in). For pharma, may be blocked entirely by GxP cloud restrictions.
Rhize federation layer
Insert Rhize as the ISA-95-native, GraphQL semantic layer. MII stays running in production during transition (strangler fig, not rip-and-replace). OT data normalizes to ISA-95 regardless of where the execution layer lands. The customer keeps optionality instead of trading MII lock-in for DM lock-in.
The pitch is not "replace your MES." It is: MII was an integration-and-intelligence layer, not a pure MES. Rhize is that same layer rebuilt on open standards. The migration becomes optional, sequenced, and reversible instead of a forced cloud cutover.
SAP DM weaknesses Rhize exploits
The category insight: Rhize is the successor to the "II" in MII
The name is the tell. MII = Manufacturing Integration and Intelligence — two jobs, neither is execution. Integration (federate OT/ERP/historian data into one model) and Intelligence (KPIs, OEE, dashboards, analytics). Execution — running the work order, guiding the operator — was the sibling product, SAP ME. MII sat above the MES, not as one.
The displaced MII shop ends up with two orphans: execution (DM catches it) and integration + intelligence (nothing catches it cleanly). The BLS transactions, xMII queries, custom KPIs, and OEE dashboards are exactly what does not survive the migration — and DM's clean-core, cloud-only, proprietary-MDO model fits the federation job worse than MII did. Rhize is the native successor to that orphaned half.
"Rip out my MES" is a political war and a proof-gap nightmare. Rhize never asks for it — not competing with DM at execution, it coexists and picks up the half DM drops. The BPMN/rules engine gives a land-and-expand path into execution later, but lead with the II wedge; leading with execution re-triggers the rip-out objection. One-liner: SAP kept the ME and abandoned the II. Rhize is the II.
Segment 5 — SAP MII Migration Buyers
Multi-site SAP manufacturers running MII (usually with ME + PCo) now facing a forced, no-1:1-path migration. The clock is running and dated — the single sharpest trigger in the whole playbook.
Profile: process/regulated or complex discrete manufacturer · heavy SAP-ERP dependency (ECC or S/4HANA) · 5+ sites · deep MII customization debt · often mid-S/4HANA concurrently.
Pain stack
- No migration tool exists. Every custom transaction, KPI, OEE dashboard rebuilds by hand. The "just go to DM" assumption hides an 18–36 month re-implementation.
- The 70% discovery tax. Most of the effort is reverse-engineering undocumented BLS logic written by people who left.
- Triple EOL, one deadline. MII + SAP ME + SAP PCo all end mainstream maintenance Dec 31, 2027.
- Cloud-only blocks the regulated. 21 CFR Part 11 batch records can't move to DM Cloud. Pharma is stuck on Path A.
- Resource scarcity compounding. Dual S/4HANA + MII migrations on shared SI capacity at rising rates. Start late, finish in 2030 at peak cost.
Lead with the architect. Sell around Basis.
| Role | Function | Rhize relevance |
|---|---|---|
| Manufacturing IT Director / Plant IT Lead | Owns MII, feels the deadline, runs the RFP | PRIMARY Technical evaluator, closest to pain |
| MES/MOM Manager / Plant Systems Lead | Day-to-day MII operator, knows the custom debt | CHAMPION Most open to a non-SAP data layer |
| OT/IT Architect | Edge, data residency, regulated constraints, UNS/MQTT advocate | CHAMPION Natural ally |
| VP Manufacturing / Operations | Economic buyer, owns production P&L | ECON Lead with timeline risk + ROI, not tech |
| CIO / CDO / Digital Mfg Director | Budget sign-off, cloud governance, architecture | SPONSOR CDO often champions |
| SAP Basis / Architecture Lead | Gatekeeper to S/4HANA, pulls toward DM by reflex | AVOID Threat-neutralizer, informal veto. Do not cold-approach. |
Plant IT surfaces the EOL deadline → Manufacturing IT Director commissions scoping → VP Ops/CIO approve budget → SI shortlisted → cross-functional eval. Basis holds informal veto unless the economic buyer has independent conviction. Frame timeline + data architecture, not product.
MII is invisible to tech-detection. Build the list from signals.
MII runs on-prem NetWeaver inside the plant network — no web fingerprint. BuiltWith and TechSight will not find it. List-building leans on jobs, SI references, and ASUG.
Tier 1 — build now
- LinkedIn job search. Companies posting SAP MII / SAP ME-MII / SAP Digital Manufacturing / DMC / PCo / ProdCon roles. ~85–120 active US postings (Q1 2026). A "DM" posting within 90 days of an "MII" posting = mid-migration, highest receptivity.
- LinkedIn people search. Profiles with "SAP MII" in skills/experience, filtered to Manufacturing IT Director / Plant Systems Manager / OT-IT Architect / Digital Manufacturing Lead.
- SI reference reverse-engineering. Mine named clients + case studies + employee recommendations from the SIs actively selling MII→DM migration. Their pipelines are your list.
- ASUG speaker-list mining. Historical ASUG Mill Products / Pharma / Automotive / Manufacturing sessions featuring SAP MII speakers. Cross-reference company names.
SIs to mine:
Tier 2 — vertical ABM
Top US pharma, Chem Week Top 100, Automotive Tier 1/2, CPG Fortune 500, Paper/Packaging — $500M+ revenue, known SAP ERP, 5+ sites. ~40–60% of complex multi-site SAP process manufacturers ran MII or ME.
Tier 3 — sequencing
Target in order: (1) Manufacturing IT Director / Plant Systems Lead → (2) OT/IT Architect → (3) VP Manufacturing. Never Basis.
Public or strongly-implied MII users
For lookalike list-building and anchor selection. Do not name in cold copy unless first-party public.
| Account | Vertical | Evidence |
|---|---|---|
| Momentive | Advanced materials / chemicals (NY, 9k emp) | Confirmed MII kellton.com, 2024 |
| Beiersdorf | Consumer goods | MII since 2009, smart-factory data hub Trebing+Himstedt |
| Roche | Pharma | SAP xMII shop-floor↔ERP integration |
| BMW | Automotive | MII for production fault detection moderate confidence |
| CertainTeed | Building materials | MII + OSIsoft, ASUG presenter |
| Sappi | Paper / pulp | Confirmed MII sapinsider.org |
| Lion | F&B (56 plants) | MII + S/4HANA IT/OT integration sapinsider.org |
| Arca Continental | Beverage (45 facilities) | Real-time intelligence via MII |
| Festo | Industrial machinery | SAP ME line-worker guidance |
| Milliken | Textiles / chemicals (SC) | Careers-page reference weak — verify |
No published count exists. Don't pretend otherwise.
The proposal's "~300 largest MII installs" is a Rhize-internal target thesis, not a published figure. Defensible as an account-selection thesis, never as a stat in copy.
- No published count of current MII installs exists. No SAP or analyst figure found.
- The "12,000 manufacturing customers" figure (SAP/Lighthammer acquisition, 2005) is SAP's total manufacturing base, not MII deployments. Do not cite it as MII installs.
- Inferred global MII shops: low thousands (~2,000–4,000), several hundred in North America. Pattern inference, uncited.
Who else shows up when the MII shop is forced to move
| Alternative | Why they consider it | Rhize's gap to exploit |
|---|---|---|
| SAP DM default | Basis pulls toward it, no new vendor | Cloud-only, no 1:1 path, rebuild all custom logic, MDO lock-in, immature edge, GxP-blocked. Rhize federates without forcing cloud or a full MES rebuild. |
| Rockwell Plex / FactoryTalk | Auto/F&B strength, cloud MES | Another full re-implementation; OT-centric, weak multi-ERP. Rhize coexists, adds ISA-95 on top. |
| AVEVA MES (Wonderware) | Legacy base, historians in place | Heavy, consultant-dependent, discrete-biased. Rhize lighter, ERP-agnostic, open API. |
| Ignition + custom | Builder-friendly, MQTT-native, cheap | Not a data hub, no ISA-95 out of the box → bespoke 18-month project. Rhize ships what that build produces. |
| Tulip | Fast operator-app deployment | Not a data hub; no multi-site ISA-95 federation. Rhize is the foundation Tulip apps run on. |
| Körber PAS-X | Pharma eBR dominance | Pharma-only, no OT federation. Rhize coexists as the layer under PAS-X. |
| Stay on MII / do nothing | Extended support to 2030 buys time | Dead platform, no features now, rising rates. Paying premium to defer. |
| Custom on BTP | "We'll build it" | Multi-year, skill-scarce, no pre-built ISA-95. Rhize = buy the model, build the apps. |
The four pushbacks and the sharpest rebuttals
"We're already SAP, we'll just go to DM."
No 1:1 path — Concircle, an SAP migration partner, documents this. Every custom transaction rebuilds. DM is cloud-only — fails data-residency and GxP pharma. You still have to solve OT federation; Rhize solves it regardless of execution layer and doesn't force cloud.
"We don't want another vendor."
Rhize isn't replacing MII; it's the data layer that keeps your systems talking. Strangler-fig, not rip-and-replace. You're not adding a vendor, you're adding the foundation that makes migration optional instead of mandatory.
"Rhize isn't an MES — we need execution."
Correct, and that's the point. MII wasn't a pure MES either; it was integration + intelligence. Rhize is that, on ISA-95/GraphQL/MQTT instead of NetWeaver. Keep your MES; Rhize unifies the data underneath so it sees one feed, not 40 integrations.
"We have until 2030."
Mainstream support ends Dec 2027; 2030 is paid extended, not automatic. Migrations run 12–36 months. Start in 2027, finish in 2030 at peak scarcity (+30–50% rates). Start now, lock architecture before the market crowds.
Sourced. Sharpest first.
- The cliff SAP named itself. SAP titled its own Nov 2025 webinar "Avoid the Cliff" for MII/ME customers. Mainstream support ends Dec 31, 2027. sap.com/events
- No migration tool exists. SAP and every major SI confirm there's no 1:1 path from MII to SAP DM — every BLS transaction, KPI, and OEE dashboard rebuilds by hand. 18–36 months. concircle, iiotblog Oct 2025
- The 70% discovery tax. ~70% of MII migration effort is reverse-engineering what the system does — the builders are gone, the docs were never written. Henry Costa/Medium, Oct 2025
- Triple EOL, one deadline. MII, PCo, and SAP ME all hit end of mainstream maintenance Dec 31, 2027. One date, three migrations. ifactoryapp.com
- Pharma hard block. Running 21 CFR Part 11 batch records on MII? SAP DM Cloud isn't available to you — GxP doesn't permit cloud MES yet. ifactoryapp.com
- OEE regression. Your MII OEE dashboards don't survive. DM's standard OEE covers current + prior day only; everything else rebuilds in Embedded SAC. SAP Community Q&A, 2024
SAP is ending mainstream support for MII at the end of 2027. There is no one-to-one path to Digital Manufacturing. Every custom transaction gets rebuilt by hand. Most teams are surprised by the size of it. Worth comparing notes?
Key references
~90 sources across two research passes (June 7, 2026). Primary sources preferred; inference flagged throughout. Confirm the exact SAP Note number for the 2027/2030 dates before citing in any deck.
- Andea — SAP MII End-of-Life: What to Plan Before 2030 (2025)
- iiotblog.com — Is SAP DM a Replacement for SAP MII? (Oct 2025)
- iiotblog.com — MII EOL: What Comes Next for Shop-Floor Connectivity (Dec 2025)
- Concircle — Migrating from SAP MII to SAP Digital Manufacturing
- ifactoryapp.com — SAP MII Migration Complete Guide
- ifactoryapp.com — SAP PCo End-of-Life Migration Guide
- SAP — "Avoid the Cliff" webinar (Nov 2025)
- E3 Magazine — MES and MII Support (DSAG extension) (Aug 2023)
- Henry Costa / Medium — Why Replacing SAP MII Is a Priority (Oct 2025)
- SAP Community — Feasibility of OEE KPI in Digital Manufacturing (2024)
- SAPinsider — Lion MII case study
- Kellton — Momentive MII case study
- Andea — Alternatives to SAP MII for S/4HANA Users
- Rhize — Manufacturing Data Hub as a Legacy Integrator