Status

Owner
StakeholdersThe persons consulted or otherwise involved in making this decision. Type @ to mention people by name

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 here:  https://docs.google.com/presentation/d/1fPfP5u_AFSuXtLUswS2qS2NFU-jj82l6/edit?usp=drive_link&ouid=112863035388257143536&rtpof=true&sd=true





Recommendation

We recommend Option 1: keep current MES systems in place. 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

Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.


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

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Option A: Option Title

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


Option B: Option Title

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


Option C: Option Title

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


Option D: Option Title

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


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

(plus)Pro

(minus)Con

(plus)Pro

(plus)Pro

(plus)Pro

(minus)Con

(plus)Pro

(minus)Con

Criterion 2

(plus)Pro

(minus)Con

(minus)Con

(plus)Pro

(plus)Pro

(minus)Con

(minus)Con

Criterion 3(plus)Pro(minus)Con(minus)Con(plus)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