Status

Owner
Stakeholders

Issue

SAP MII (Manufacturing Integration and Intelligence) will stop being supported by SAP after 2027 (or 2030). it is currently used by the following Syensqo entities:

  • ...
  • ...
  • ...

We need to identify a strategy to address this situation. This KDD document presents the possible options and identifies the best proposal, analyzing the implications and impacts under different points of view: business functionalities, IT perspective, change management, scalability and future proof solution.

Three options are available: 

  • A) continue running on MII after end of official support, managing internally or via a 3rd party provider the product maintenance and adaptations
  • B) substitute MII with the corresponding part of the new SAP Digital Manufacturing
  • C) remove MII and directly connect MES systems to SAP S4 and/or to the StarTek platform


Recommendation

Option B is the recommended solution: substitute MII with the corresponding functionalities of SAP Digital Manufacturing.


Background & Context

MII is used by the following plants:

  • ...
  • ...
  • ...

to connect the following MES systems:

  • ...
  • ...
  • ...


MII acts as a middle-ware to connect the MES systems with the following data flows (not all of them are relevant for all plants/MES systems):

  • process orders from SAP ECC to MES
  • production confirmations from MES to SAP ECC
  • production goods movements from MES to SAP (consumption and goods receipt)
  • ....



Assumptions

  • MII is currently used as middle-ware to connect MES systems in the plants listed in the Issue section, not for further functionalities (like OEE, analytics, reporting, data intelligence, etc.)
  • MES systems in the affected plants won't change and MES functionalities and implementations in the affected plants will remain stable during the ERP Rebuild project
  • other functionalities potentially covered by SAP Digital Manufacturing are not part of this KDD; they are addressed here: https://wiki.syensqo.com/x/-YGMNQ


Constraints



Impacts

Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.


Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 


Options considered

Option A: Keep MII

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly


Option B: substitute MII with Digital Manufactring

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly


Option C: Remove MII and directly interface MES systems to SAP S4 (and/or StarTek suit)

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly


Evaluation

The following Matrix illustrates the evaluation of each option under the considered criteria:


Criteria

Weight 

Option A

Keep MII

Option B

substitute MII with Digital

Manufacturing

Option C

Remove MII and directly interface

MES systems to S4 / Startek

Future Proof and Scalability VHVery LowVery HighVery Low
Best PracticeHVery LowVery HighLow
Functionalities HHighHighHigh
Reduce Change Management LVery HighVery HighVery High
SimplicityHVery HighHighMedium
MaintainabilityVHVery LowVery HighLow
Reduce Project EffortHVery HighLowVery Low

Total 


Medium

High

Medium





Change log

Workflow history