| Status | |
| Owner | |
| Stakeholders | The persons consulted or otherwise involved in making this decision. Type @ to mention people by name |
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

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:
SAP DM-Execution is a modern, fully scalable and Cloud based MES system. Its introduction would allow the usage of advanced functionalities like:
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.
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.
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".
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.
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
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 |
|
|
|
|
| Criterion 2 |
|
|
| |
| Criterion 3 |
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.
