Issue

Different MES systems are used across Syensqo plants. PI by OSISoft and Aspentech MES are the most common ones. Some other plants are running without an MES system, and some plants are using their MES only for a subset of production lines and functionalities.

Within the ERP Rebuild project, there is the opportunity to introduce SAP Digital Manufacturing as MES system and leverage its introduction for further functionalities.

An overview of the SAP DM functionalities can be found in the attached presentation.

Recommendation

We recommend Option A: keep current MES systems in place and interface all MES systems to SAP S4 via SAP BTP Integration Suite. For the plants and production lines currently without an MES, we will define in Detailed Design a Decision Tree, that will contain the following options:

• continue working without MES system and use S4/HANA Fiori Apps to book production actual data
• continue working without MES system and use Mobile devices on Neptune to book production actual data into S4HANA
• roll out one of the current MES systems already used by Syensqo
• implement SAP Digital Manufacturing - Execution on the plant

Background & Context

SAP DM-Execution is a modern, fully scalable and Cloud based MES system. Its introduction would allow the usage of advanced functionalities like:

• Edge points, to allow local plants to work offline in case of connection outages or system maintenance, 
• Insights, to exploit the maximum value of the production data and identify all the bottle-neck and pain point in the current production activiites and put in place corrective actions, then measure the effect of those actions
• Production Process Designer, to define and automate production steps
• Production Connectivity Model, to use the MES system likewise a PCS/BCS system and monitor/change the parameters of the machines in the Shop Floor (e.g. temperature of an oven, speed of flux of a certain material into a reactor, etc.)
• Resource Orchestration: to automatically assign the right people and the right machines and tools to the planned production activities and optimize their utilization
• Operator Dashboard: to provide to each operator

Assumptions

• Changes of the local MES systems have a huge impact on the daily production activities
• Current Star Tek Layer heavily relies on current MES systems
• SAP DM has native integration with the new ERP system S4/HANA

Constraints

• Current Star Tek Layer heavily relies on current MES systems
• Current Star Tek layer pick up data from SAP for several business cases (e.g. plants without MES system, data booked direclty in SAP even in case of plants with MES systems, etc.)

Impacts

• Current interfaces from SAP to Star Tek must be maintained and adapted to S4 to guarantee the continuity of Star Tek functionalities
• Current interfaces of MES data from Star Tek to ECC will be substituted with SAP BTP Integration Suite, direclty from MES to S4.

Business Rules

A Decision tree will be defined in the Detailed Design, to identify the MES solution for each plant currently without MES and for new plants.

Options considered

Option A: keep current MES systems in place and interface all MES systems to SAP S4 via SAP BTP Integration Suite

Option B: define a path to substitute all MES systems with SAP DM

In this option, we consider the possibility to adopt SAP DM as the new Syensqo standard for MES system and production DataLake. 

That means:

• introduce SAP DM-Execution as MES for all plants without an MES system
• progressively substitute current MES systems (PI-OSISoft and Aspentech MES) with SAP DM-Execution
• progressively substitute part of Star Tek functionalities with SAP DM-Insights
• progressively introduce further useful features of SAP DM like PPD and PCM

Despite the undoubted advantages of native integration, scalability and future-proof solution, this option has also significant disadvantages:

• huge impact on the day by day plant activities as the substitution of current MES would be a delicate operation
• very long lead time to achieve the final landscape, as all 65 production plants would be impacted by a MES project along the way
• waste of the investment already done to adapt and optimize the current MES systems
• waste of a relevant part of the investment already done in Star Tek, which would be in part substituted by DM Insights, in part would require adaptations to pik up data from SAP DM-Execution

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

	Option A	Option B	Option C	Option D
Criterion 1	Pro Con	Pro Pro	Pro Con	Pro Con
Criterion 2	Pro Con	Con	Pro Pro	Con Con
Criterion 3	Pro	Con	Con	Pro

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history