Issue

As part of AS-IS process analysis, we've noticed there are more than 10 third party applications related to labelling process in Syensqo. Some of them are actively used in multiple GBUs, such as SAP GLM (Global Label Management) are currently used in Aroma Performance, Composite Materials and Technology Solutions. And others are either only used by one GBU or may not in use any more. 

With transition to SAP S/4HANA, it is a good opportunity to review the approach of labelling process going forward under the principle of standardization and simplification. 

Recommendation

It is recommended to standardize the labelling processes and applications across all the Syensqo businesses by using the approach:

• Inventory: Catalog the current labelling applications (e.g., SAP GLM, Loftware), including understanding the application specific functionalities, roles in regulatory and non-regulatory labelling and the way of integration with SAP.
• Identification: Determine if there are overlapping functions among these applications or if some are underutilized. Also, analyze the labelling requirements to ensure efficient and accurate material handling, tracking, and delivery. 
• Implementation: Implement a centralized labelling system to handle all labelling needs. This could be part of SAP (for example SAP GLM) or an integrated third-party system (for example Loftware).  

An in-depth analysis will be required to inventory the current labeling applications and identify any redundancies. Consequently, the selection of the final labeling solution, whether SAP standard or a third-party application, will be made during the Detailed Design phase, following the completion of the relevant analysis tasks.

Background & Context

The table below describes the overview of the current labelling related applications identified in Syensqo.

Assumptions

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited. 

Constraints

Capture any additional constraints that the chosen alternative (i.e. the decision made) might impose on other parts of the overall design, solution, or processes.

Impacts

Describe the impact of the decision on 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	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