SAP Manufacturing Integration and Intelligence (SAP MII) has handled shop floor connectivity for manufacturers across pharma, automotive, aerospace, food and beverage, and industrial machinery for two decades. It was built on Lighthammer’s Collaborative Manufacturing Suite, which SAP acquired in June 2005 to serve its then-installed base of more than 12,000 manufacturing customers. SAP has now officially announced its end of life: version 15.5, released on NetWeaver AS Java 7.5, is the final version, and the SAP Roadmap Explorer shows no plans for any further releases or feature investments. For the production IT teams who built their integration layer on MII, this is not a distant planning item: the mainstream support deadline is 2027, and the decisions made in the next 12 to 18 months will determine whether your migration is orderly or forced.
What Does SAP MII End of Life Actually Mean?
SAP has set the following support roadmap for MII:
- Mainstream support ends in 2027. After this date, SAP will not release new features or standard patches for SAP MII.
- Extended support runs until December 31, 2030. Security and legal maintenance continue, but at a premium cost and with limited scope.
- SAP MII 15.5 is the final version. There is no roadmap beyond it.
Important: Extended Support Is Not Automatic. The December 31, 2030 date applies only if your organization has activated extended support under your SAP licensing agreement. Verify your eligibility with SAP before treating 2030 as your planning deadline.
Why Infrastructure Upgrades Cannot Extend SAP MII’s Life
SAP MII 15.5 runs on NetWeaver 7.5, which shares the same end of mainstream maintenance date in 2027. Upgrading your infrastructure will not extend MII’s support window — the two are tightly coupled. SAP MII end-of-life creates a specific planning trap: teams that treat an infrastructure refresh as a way to buy time will find they have spent budget without extending the support window by a single day.
What Are the Real Risks of Staying on SAP MII Past 2027?
SAP MII end-of-life creates a delay risk that accumulates from the moment mainstream support ends in 2027 — not from 2030. With each year of delay, migration options narrow and execution costs rise.
Before you match criteria to platforms, it helps to know your migration complexity. The 3-minute readiness check gives you a baseline score: ⏱️ SAP ME/MII end of life – 3‑minute readiness check
Compliance and Audit Exposure
In regulated industries — pharma, automotive, food and beverage — SAP MII running past its mainstream support date creates audit findings in regulated environments. After 2027, SAP will release no further fixes, updates, or compliance patches for MII. If your MII instance touches quality-critical data or regulated processes, this is an active risk from the moment mainstream support ends, not a theoretical future concern.
Integration Fragility
SAP MII’s end-of-life leaves its core integration layer — BLS transactions, xMII queries, PCo connections — without SAP investment as the surrounding landscape evolves. Every SAP ERP upgrade after 2027 becomes a potential break point for these custom integrations, with no SAP patch coming to stabilize them. SAP will make no corresponding platform investment in MII to keep pace. Maintenance overhead for custom integration points will grow with each adjacent system release.
Performance Ceilings
SAP MII 15.5 runs as a J2EE web application on NetWeaver AS Java 7.5, an architecture designed for the data volumes and processing patterns of the early 2000s. SAP MII end-of-life confirms that the J2EE architecture constraints will never be resolved. Plants that have expanded sensor coverage, OEE tracking, or real-time analytics workloads have no upgrade path within MII. No 15.6 is coming.
What Is SAP Replacing MII With?
SAP’s official answer is not a single product but a distributed architecture:
- SAP Digital Manufacturing (DM) — cloud-based strategic successor for MES and shop floor execution, running on SAP Business Technology Platform.
- SAP ProdCon (formerly SAP PCo extended) — handles the edge connectivity layer that PCo provided in MII deployments.
- SAP HANA Cloud and SAP Datasphere — absorb historian and central data integration functions built into MII.
Migrating to SAP DM requires a redesign of custom MII workflows. SAP DM follows a clean-core architecture that eliminates direct database access in favor of API interactions. If your MII deployment carries significant custom BLS logic, the migration is a rebuild, not a lift-and-shift. SAP recommends a hybrid coexistence model during transition: SAP DM takes over standard transactions first while MII continues handling shop floor integration during the cutover period.
Is SAP Digital Manufacturing the Right Destination for Every Manufacturer?
SAP DM is SAP’s designated successor and the default path for organizations already deep in the SAP ecosystem. Before committing, three categories of manufacturer should evaluate whether it actually fits their constraints.
Cloud-Constrained Environments
Air-gapped discrete manufacturing plants and facilities with strict data sovereignty requirements face real obstacles with a cloud-native SAP DM deployment. On-premises MES keeps the execution, OEE, and ISA-95 stack inside the firewall — a constraint that cloud-first architecture cannot resolve without significant compromise.
Multi-ERP and Brownfield Environments
SAP DM is optimized for the SAP ERP ecosystem. Manufacturers running SAP alongside Oracle, Infor, or mixed legacy ERPs face integration complexity that the SAP path does not simplify. The clean-core API model requires custom integration work for every non-SAP system in the landscape.
Manufacturers with Complex MES Requirements
SAP DM inherits SAP’s strength in ERP process integration. For multi-site production execution, built-in quality management, component genealogy, and maintenance scheduling, dedicated MES platforms built specifically for manufacturing operations cover these areas as core functionality — not as modules in active development. If your requirements include configurable site-specific workflows, multi-plant genealogy, or regulated-industry traceability, verify current SAP DM feature availability against your requirements before committing to the SAP path.
SAP Digital Manufacturing vs. DELMIA Apriso: Key Differences
| Criterion | SAP Digital Manufacturing | DELMIA Apriso |
|---|---|---|
| Deployment model | Cloud-native (SAP BTP); on-premises limited | Cloud and on-premises — both fully supported |
| ERP integration | Native SAP ERP; multi-ERP requires custom work | Native SAP ERP integration; supports multi-ERP environments |
| Custom logic migration | BLS/xMII logic requires rebuild (clean-core API model) | Process Builder enables configuration without modifying product code — no rebuild required |
| Data sovereignty | Cloud dependency may conflict with air-gapped or regulated-plant requirements | On-premises deployment available for air-gapped facilities |
| MES depth | Strong ERP process integration; dedicated MES modules (production execution, quality, maintenance) in active development on SAP BTP | Full MOM stack: production, quality, maintenance, warehouse, genealogy, T&L — available today across all deployment models |
| Multi-site support | Supported via BTP | Global Manufacturing Suite (GPM) — centralized deployment to all plants |
| Industry verticals | SAP industry cloud | 9 verticals: aerospace & defense, automotive, medical devices, industrial machinery, packaging, high tech, clean energy, cosmetics, food & confectionery |
| Security certification | SAP platform certifications | SOC 2 Type II (AICPA TSC) |
| Partner ecosystem (Andea) | — | 810+ MOM/APS projects, 90+ global manufacturers, 280+ manufacturing sites |
For a detailed comparison of each platform - including DELMIA Apriso, SAP DM, Pillir, and L2L - see the SAP MII alternatives guide for S/4HANA users
Your Options at a Glance
| Criterion | Status Quo (stay on MII) | SAP Digital Manufacturing | DELMIA Apriso |
|---|---|---|---|
| Risk | High — no patches after 2027, audit exposure, every ERP upgrade a break point | Medium — rebuild required for custom BLS logic; cloud dependency for air-gapped plants | Low — Process Builder preserves custom logic; on-premises available |
| Cost driver | Rising maintenance overhead; no SAP investment | Full rebuild of custom logic; multi-ERP integration work | Configuration over rebuild; lower regression risk |
| Timeline | None — until 2027/2030 forces action | 18–36 months depending on BLS complexity | 12–36 months depending on BLS complexity |
| Best for | — | SAP-centric organizations, minimal custom logic, cloud-ready | Multi-ERP environments, air-gapped plants, significant MII customizations, regulated industries |
DELMIA Apriso: The Migration Path That Keeps You in Control
DELMIA Apriso by Dassault Systèmes gives manufacturers running SAP MII a migration destination that works on-premises or in the cloud, handles multi-ERP environments, and preserves custom logic without a full rebuild. It covers the full manufacturing operations management stack:
- production execution, quality management, maintenance scheduling, component genealogy, warehouse operations, and time and labor tracking.
It connects to SAP ERP natively and supports both cloud and on-premises deployment — which matters for manufacturers who cannot move everything to the cloud on SAP’s timeline.
How Process Builder Reduces Migration Risk
The central technical challenge of any SAP MII migration is what to do with custom BLS logic. SAP DM’s clean-core API model requires that logic to be rebuilt from scratch. DELMIA Apriso’s Process Builder takes a different approach: it lets teams configure tailored solutions — including complex, site-specific workflows — without modifying the underlying product code.
In practice, this means a manufacturer with extensive custom BLS transactions can port the logic to Process Builder configurations rather than rewriting it as API integrations. The product code stays intact, which eliminates the regression risk that comes with code-level changes and keeps future upgrades clean. Andea’s experience across 810+ MOM/APS projects consistently shows that organizations with significant MII customizations that migrate to Process Builder avoid the full scope redefinition that a clean-core rebuild requires — a difference that typically translates to months of project time and avoidance of a full regression testing cycle.
Industry Coverage
DELMIA Apriso supports 9 industry verticals with dedicated functionality: aerospace and defense, automotive, medical devices, industrial machinery, packaging, high tech, clean energy, cosmetics, and food and confectionery. Each vertical brings pre-built compliance frameworks and process templates rather than generic MES functionality adapted after the fact.
Regulatory Compliance Frameworks
For manufacturers in regulated industries, DELMIA Apriso provides vertical-specific compliance support built into the platform rather than added on top of it:
| Vertical | Regulatory framework | Scope |
|---|---|---|
| Medical devices / Pharma | 21 CFR Part 11 | Electronic records and electronic signatures — FDA requirement for regulated manufacturing |
| Automotive | IATF 16949 | Quality management system standard for automotive production and service part organizations |
| Aerospace & Defense | AS9100 | Quality management system requirements for aviation, space, and defense organizations |
Security and Compliance Posture
Andea, as the implementing partner, holds a SOC 2 Type II certification under the AICPA Trust Services Criteria — covering security, availability, processing integrity, confidentiality, and privacy. For manufacturers in regulated industries where data handling in deployments and maintenance is subject to audit, this certification is a verifiable control, not a marketing claim.
Andea’s Migration Approach
The migration pattern Andea applies consistently: production execution first, quality and analytics layers in a second wave. This sequencing reduces cutover risk and keeps the shop floor running during transition.
The single most important input before committing to a migration path is an honest inventory of the custom logic your system is carrying — BLS transactions, xMII queries, and integration points. That inventory determines whether your migration timeline is 12 months or 36.
How Long Does Migration Actually Take?
The SAP MII end-of-life timeline leaves between four and nine years of runway depending on when you start — but migration timelines themselves range from 12 to 36 months, driven primarily by one factor: the volume and complexity of custom logic in your current MII deployment.
| Migration profile | Custom logic scope | Indicative timeline |
|---|---|---|
| Simple | Standard MII transactions, minimal BLS customization, single site | 12–18 months |
| Moderate | Custom BLS logic, multiple PCo connections, 2–3 sites | 18–28 months |
| Complex | Extensive custom BLS/xMII, multi-site, multi-ERP, regulated-industry traceability | 28–36 months |
Teams that start their readiness work in 2025 or 2026 will complete migrations before the 2030 deadline with time to stabilize. Teams that wait until 2028 will be executing under time pressure with reduced vendor capacity.
The S/4HANA Precedent. In 2020, SAP extended the S/4HANA deadline from 2025 to 2027 after the pace of migrations made the original date unachievable at scale. By the end of 2024, only 39% of SAP’s 35,000 ECC customers had completed migration, according to Gartner — meaning 61% still face the same deadline pressure today. Consulting fees for S/4HANA specialists have already risen approximately 20% since 2023, according to the Baer Group’s 2025 SAP staffing trends report. Multiple analysts project a further 30–50% increase in specialist rates by 2026–27 as the remaining volume of work compresses into a shrinking window. The SAP MII end-of-life structure is identical: 2027 mainstream cutoff, 2030 extended option. The manufacturers who avoid the capacity crunch are the ones who started before the window narrowed.
What Should You Do Now?
- Inventory your custom MII logic. Catalog BLS transactions, xMII queries, and PCo integration points before engaging any vendor. This inventory drives the migration complexity estimate more than any other single factor.
- Verify your extended support eligibility with SAP. The December 2030 date is not automatic — confirm it applies under your licensing agreement.
- Evaluate your ERP direction independently. If your SAP ERP is also moving to S/4HANA in the next three years, the sequencing of that migration relative to your MES transition matters significantly.
- Run a structured readiness assessment before committing to a path. A readiness assessment tells you how much custom logic you are carrying, what maps cleanly to the target platform, and what needs redesign — inputs that a vendor proposal alone will not give you. The decisions made now determine whether your migration is orderly or forced.
Migration Readiness Assessment by Andea
- Custom logic inventory (BLS, xMII, PCo connections)
- Integration point mapping
- Site and process complexity scoring
- Output: scored readiness profile (Simple / Moderate / Complex) with migration timeline estimate
- Time required: less than one day of your team's time
Learn more at andea.com/delmia-software/ or contact Andea directly to discuss your environment.
Andea is a Dassault Systèmes DELMIA Apriso Silver Partner specializing in manufacturing execution systems and brownfield MES migrations. Founded in 2014, Andea has completed 810+ MOM/APS projects across North America, Europe, South America, and Asia. Andea holds SOC 2 Type II certification under AICPA Trust Services Criteria.