Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Issue

Syensqo currently has over ten different labelling applications across different domains, such as logistics, EHS, warehouse management, QM and transportation etc. Some of them, such as SAP GLM (Global Label Management), are actively used across multiple GBUs, including Aroma Performance, Composite Materials and Technology Solutions etc. Other applications, however, are either used by only one GBU or are no longer in use.  

With the transition to SAP S/4HANA, SAP GLM is not on the roadmap for the future and will be replaced by a partner solution. Refer to SAP Label Management Future Direction & Vision in section See also below.

Therefore, it is important to review the current labelling applications and develop a strategy an approach to help Syensqo streamline the labelling processes, ensure the label consistency, improve the operation operational efficiency, and reduce maintenance costs.


Recommendation

It is recommended to adopt a strategy of standardizing and simplifying standardize and simplify labelling applications across all Syensqo businesses using the following approach:

  • Assessment and Inventory: Identify and catalog the current labelling applications with  understanding understanding the functionalities, user base, and integration points.
  • Requirements Definition: Engage with stakeholders from various GBUs to understand their labelling needs and preferences during detailed design phase. Make sure the requirements are clearly documented, and the labelling aligns with ERP Rebuild solution designs. 
  • Standardization and Simplification: Evaluate how each application is used and its value to different business units. Look for common labelling requirements across different GBUs to standardize Use SAP Partner Label Solution for all ERP Rebuild in-scope labels. Other labelling applications fall outside the scope of the ERP Rebuild Project, as they operate independently of SAP. This approach will standardize labeling processes, reduce complexity, and implement the unified labelling application(s) across Syensqo.  

The selection of the exact labelling application(s) will be made in the Detailed Design phase, following the completion of the relevant analysises and tasks required by the above approach.

  • ensure an unified labelling solution across various business units.
    • Label data, label determination and process integration will be managed in SAP S/4HANA.
    • Label design and printing will be managed through a partner solution, such as Loftware or Eurosoft-Plus, including the integration between the partner solution and S/4HANA. Given Loftware's extensive use across multiple Syensqo operations, it is a strong candidate for the unified labelling solution. However, the final choice of the labelling partner will be determined during the Detailed Design phase, after a thorough analysis.


Background & Context

Based on the information gathered during the As-Is Analysis and follow-up interviews, the table below provides an overview of the current labeling applications within Syensqo. For each identified application, the table details the category and type of labels managed, in scope of ERP Rebuild Project or not, and which GBUs are currently utilizing it.

Note: Some relevant information is still pending. It will continue to be collected through the Detailed Design phase.

ApplicationCategoryLabel TypeIn-Scope Aroma PerformanceComposite Materials

Novecare

Specialty PolymersTechnology Solutions

Background & Context

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

ApplicationScopeMain FunctionalitiesAPCMNCSPTS

SAP GLM

(Global Label Management)

1). Regulatory Label (

EHS - DG1

Product Stewardship)

To generate and print:

2).

Product Safety compliant labels for
  • Dangerous goods
  • Manufactured and semi manufactured products
  • Samples
  • Batches

2). Labels for

  • Storage conditions
  • Customers specifics labels

Custom Labels (Product Stewardship)

Dynamic Label 

YYYYYY
Loftware SpectrumNon Regulatory Label

To print below labels generated by SAP transactions.

  • Production (Intermediates, Finished Goods)
  • Raw material
  • Address
  • Packaging / MRO (Maintenance, Repair and Operations)
  • Pre-Production
  • Storage Unit
  • QA on Hold
  • License plate
  • Customer specific labels
Y

Dynamic Label

Y
YN

Y

(used at key US sites MJS, AQS)

N


Loftware Spectrum Web AccessOne-off Static Text Label

A web portal used to print one-off labels with static text. These labels are not the same ones that are generated by the SAP transactions.

Static Label

N
  • Orientation arrows (i.e. This End Up)
  • Static text like "Do Not Freeze"
  • One or more free text fields that allow the operator to enter any info

    YN

    Loftware Nice Label / Loftware Cloud Zebra Labels and EHS Label

    Used to develop (create and design) the layout of Zebra labels and EHS Label Printing.

    ????

    Dynamic Label

    Y
    ?





    Bartender Customer Labels
    Manage customer labels in supply chain. Bartender is used to print labels for tollers. It uses a license server.

    Dynamic Label

    Y

    Y (EU, US)


    Y (EU, US)

    Y (chang shu site)
    MarkWare  

    MarkWare is a Windows®-based application used to create a variety of labels, signs, tags, pipe markers, and other industrial identification.

    ??N?

     




    N
    ?


    Codesoft  

    RFID and barcode label software.

    ?????

     







    EB-SOFT  
    App is use for printing labels.

     




    N



    Techlink Labelling  
    System used to generate labels in GBU Fibras' Spinning department

     




    N

    Label View  
    Label tool

     




    N

    Labware  

     

    Label tool used in Composite GBU
    Y

    N

    Material Group Labelling  

     

    Material Group Labelling (SBS Material Grouping)

    TBarCode 

    Offers barcode printing for Microsoft® Office users and software developers. 

    N

    Note:

    The abbreviations in the matrix stand for GBUs as per below:

    AP - Aroma Performance, CM - Composite Materials, NC - Novecare, SP - Specialty Polymers, TS - Technology Solutions   

     







    TBarCode





    N

    Adobe IllustratorManual labels

    Dynamic Label,

    Static Label

    Y (Dynamic Label), N (Static Label)


    Y
    OfflineManual labels

    Dynamic Label





    Y
    OfflineStatic labels

    Static Label

    N





    Assumptions

    • Dynamic labels generated using data from SAP, as part of process which sits in scope of ERP Rebuild Project. Others fall outside the scope of the project, as they operate independently of SAP.
    • The standardized labelling application should be closely integrated with SAP S/4HANA. 

    • The standardized labelling application is able to interface with all of the existing label printers, or the printers can be replaced to make them compatible
    • The decision will be made during detailed design phase whether the selected labelling application needs to be integrated with other non-SAP applications.
    • The selected labelling application

    Assumptions

    • The chosen standard solution will closely integrate with SAP S/4HANA.
    • The chosen standard solution

      adheres to regulatory requirements relevant to Syensqo industry, and allows for easy updates to accommodate new regulatory requirements or changes in labelling standards.

    • The selected labelling application will have the flexibility to cater for the required layout, including the special customer requirements such as the specification for labels in Composite business.  
    • For simpler labels, in addition to the selected labelling application, Syensqo might consider using SAP standard tools such as SAP BTP (Business Technology Platform) Forms Service.


    Constraints

    System Limitations: The standardized tool unified labelling application must support all required labeling in-scope labelling functions and features previously covered by various third-party applications. It can be challenge to replicate the same functions.  

    Legacy System Dependencies: Some legacy systems may have customized features or integrations that are not easily replicated in a new system. 

    Regulatory Compliance

    Compliance Risks: Ensuring that the new standardized system

    Therefore, it is important to identify and address any gaps that require custom developments to fill.

    Regulatory Compliance : Ensuring that the unified labelling application meets all regulatory requirements and industry standards is critical.  

    User Adaptation:

    There may be a need to adapt the new system to handle specific regulatory labeling requirements that the old systems managed differently.
      • Functionality

    Users accustomed to different labelling applications may face difficulties adapting to a new, standardized application. Comprehensive training will be necessary to ensure that all users are proficient in the selected labelling application.

    Scalability: Ensure that the standardized labelling solution can scale with future growth and adapt to new requirements or technologies.


    Impacts

    Implementing a standardized and simplified labelling solution in a SAP S/4HANA project involves several potential impacts, both positive and challenging.

    Operational Efficiency

    • A unified labelling solution can streamline labelling processes across different business operations, including logistics, warehouse management, EHS and transportation etc.

    • A unified solution ensures

    Impacts

    • Operational Efficiency

    • Streamlined Processes: Standardization can streamline labeling processes, reducing complexity and redundancy.
    • Consistency: Ensures

      consistency in label formats, designs, and compliance across different departments and locations, which helps reduce redundancy and improve operation efficiency.

      Integration

      System Integration: Standardizing tools can simplify integration with SAP S/4HANA, potentially reducing integration issues and improving data accuracy

    Label Consistency

    • Label formats and structures may vary among different label applications. Mapping and transforming data from these diverse formats into a consistent format for the unified application(s) can be complex.

    • If historical labelling information in multiple applications need to be migrated to the unified application(s), ensure that relevant historical information remains accurate and accessible.

    Cost Implications

    • Initial

      Costs: There may be significant upfront costs associated with transitioning to a new standardized system.
    • Ongoing Costs: Maintenance and support costs could be lower due to reduced number of tools and simpler integration.
    • costs for implementing an unified labelling solution can be significant, including software, integration, and training expenses etc.

    • Over time, standardization and simplification can lead to long-term cost savings through reduced maintenance, support, and licensing fees for multiple applications.

    • To optimize costs, for make-to-order process, the selected labelling application should be able to print labels in required local languages as needed, without having to wait until the shipping stage. For make-to-stock process, re-labelling will be required due to the relevant information will be known only at later stage. 

    Change Management

    • There will

      Change Management

    • Training Requirements: Employees will need to be trained on the new standardized system, which may involve time and resource investment.
    • Adaptation Period: There may

      be a learning curve and adaptation period for

      staff as they adjust to new processes and tools.Training and Documentation: Provide comprehensive training for

      end-users

      on the new standardized labeling process and system. Update

      not only requiring to change over to the unified labelling application, but also for those currently using the selected application. Comprehensive trainings are required as well as updating documentation and standard operating procedures (SOPs) accordingly.

    • Support Structure: Establish a support framework

      Consolidate from multiple applications to an unified system can be disruptive and time-consuming. A support framework should be established to assist users during the transition and address any issues promptly.

    Downtime: The process of implementing and transitioning to a new standardized system may cause temporary disruptions in labeling operations.

    Transition Period: Migrating from multiple tools to a standardized system can be disruptive and time-consuming.

    Future Proofing

    • Scalability: Ensure that the standardized labeling solution can scale with future growth and adapt to new requirements or technologies.
    • Technology Upgrades: Stay informed about advancements in labeling technology and consider periodic reviews to incorporate new capabilities or improvements.

    APIs and Middleware: Ensure that the labeling solution provides APIs or middleware for seamless integration with SAP S/4HANA.

    Business Rules

    • Stay informed about advancements in labelling technology and consider periodic reviews to incorporate new capabilities or improvements.


    Business Rules

    • Labels need to adhere to specific industry standards and containing relevant safety information, such as hazard symbols and safety instructions.
    • Regulatory labels must include regulatory compliance information according to standards such as REACH (Registration, Evaluation, Authorisation and Restriction of Chemicals) in EU and GHS (Globally Harmonized System).
    • Labels must be in the languages required by the regions where the products are manufactured and distributed and use standardized symbols for safety warnings.


    Options Considered

    Option A: Standardized and Simplified Solution

    The approach for the future labelling solution is to Standardize and Simplify by consolidating the company’s current labelling applications.

    Transitioning from multiple labelling applications to an unified solution fully integrated with SAP S/4HANA environment is a significant task that involves careful planning and execution.

    1. Assess and Inventory
      • Define In-Scope: Dynamic labels generated using data from SAP as part of process sits in scope of ERP Rebuild Project. Others fall outside the scope of the project, as they operate independently of SAP.
      • Catalog Existing Applications: Identify and document all in-scope applications, their functionalities, user base, integration point and how each application is used.

    2. Define Requirements
      • Gather Stakeholder Inputs: Engage with stakeholders from various GBUs to understand their in-scope labelling needs and preferences.

      • Document Requirements: Define clear requirements for labelling that align with SAP S/4HANA capabilities and business needs.

    3. Standardize and Simplify Applications

      • Identify Common Needs: Look for common labelling requirements across different GBUs to standardize processes and reduce complexity.
      • Leverage SAP Partner Solutions:

        • Label data, label determination and process integration will be managed in SAP S/4HANA.
        • Label design and printing will be managed through a partner solution, such as Loftware or Eurosoft-Plus, including the integration between the partner solution and S/4HANA.

        • Due to Loftware's current adoption in Syensqo, its advanced design and customization options, and its support of regulatory compliance, it stands out as a strong contender for the unified labelling solution. However, it will be helpful to explore other SAP’s partner solutions to determine the most suitable labelling application for Syensqo. 

    4. Analyze Gaps
      • Compare Existing and Future Capabilities: Perform a gap analysis between the functionalities of current applications and the selected labelling solution.

      • Determine Customization Needs: Identify any gaps that require custom development to fill.

    5. Implement and Deploy Unified Solution

      • Migration: Ensure that data and labels from legacy applications are accurately migrated to the selected labelling solution, including required historical data and current labels. For example, there are some specific format used in current SAP GLM in Aroma business that need to be included in the standardized application. 

      • Go-Live and Post Support: Prepare for a smooth go-live and support teams are ready. Offer ongoing support and address any issues that arise after the transition to ensure stability and user satisfaction.

    Option B: 1 to 1 Migration Solution

    1. Identify all in-scope labelling applications and understand their functionalities, user base, and integration point.

      • In-scope: Dynamic labels generated using data from SAP as part of process sits in scope of ERP Rebuild Project.
    2. Migrate identified applications in future SAP S/4HANA environment. If application requires data from SAP or feed the data back to SAP, consider to establish interface between the labelling applications and SAP.


    Evaluation

    Based on five different criteria, the matrix below compares the pros and cons of the potential options for future Syensqo labelling solution.


    Option A - Standardized and Simplified Solution

    Option B - 1 to 1 Migration Solution

    Operational Efficiency

    (plus) The unified solution reduces the number of tools and eliminates redundant

    Options considered

    Option A: Standardize Labelling Applications Across Company

    Use a single labelling tool for all the labels across company.

    Option B: Standardize by Regulatory Requirements

    Use a central labelling tool for Regulatory Labels and another one for Non-Regulatory Labels

    Option C: Keep All the Active Labelling Applications

    Keep all the labelling tools currently in use.

    Evaluation

    Option A

    Option B
    Efficiency(plus) Reduces the number of tools and

    processes, leading to more streamlined operations and simplified processes .

    Eliminates redundant systems and processes, reducing duplication of effort

    (minus)Con

    (plus)Pro

    (plus)Pro

    Data Accuracy

    (plus) Standardized solution may accelerate the deployment of new labels and changes, enhancing responsiveness.


    (minus) Manage multiple labelling applications increases complexity since it requires overseeing various systems, each with its own setup, updates, and support needs.

    (minus) Overlapping functionalities among applications can lead to inefficiencies and redundancy in system capabilities.

    Standardization and Uniformity

    (plus) Consolidation into a standardized solution

    Single Source of Truth: Consolidation into a single system

    helps ensure data accuracy and consistency across the organization

    .Cost Saving

    (plus) Fewer systems to maintain can lead to lower overall maintenance and support costs.

    Standardizing may reduce the number of software licenses required

    .

    Standardization

    (plus)

    labeling solution provides APIs or middleware for seamless integration with SAP S/4HANA.

    A standardized

    system

    solution can offer better integration with SAP S/4HANA

    , improving data flow and operational efficiency.

    (minus)Con

    (plus)Pro

    (plus)Pro

    Data Synchronization

    (plus) support real-time data synchronization between SAP and the labeling system.

    (minus)Con

    (minus)ConCompliance and Customization(plus) be able to handle compliance requirements and support customization as needed for different types of labels.(minus)ConScalability and Performancecan scale with your business needs and maintain high performanceChange Management Efforts

    Employees accustomed to existing tools may resist transitioning to a new system, affecting productivity initially.

    Transition Period: Migrating from multiple tools to a standardized system can be disruptive and time-consuming.

    Flexibility

    One-Size-Fits-All: A standardized system may not be flexible enough to handle specific or unique labeling requirements that the legacy systems addressed.

    and improve data flow.

    (minus) Different applications may produce labels with varying formats and standards, leading to inconsistencies in label appearance and content, also to Non compliance because CLP regulation for ex. require size and color of the pictograms, minimum font, key data organization in the label.

    (minus) Multiple applications may result in fragmented data management, affecting the quality and accuracy of the information used in labelling.

    Cost Saving

    (minus) Initial costs for implementing a unified labelling solution can be significant, including expenses on software, integration, migration and custom development etc.

    (plus)   Over time, standardization can lead to long-term cost savings through reduced maintenance, support, and licensing fees for multiple applications .

    (plus) Keeping multiple applications utilizes existing investments and allows reduced immediate costs.

    (minus) From long term perspective, each additional labelling application incurs separate maintenance, support and license costs, leading to higher overall expenses.

    Flexibility and Scalability

    (minus) A standardized system may not be flexible enough to handle specific or unique labeling requirements that the legacy systems addressed.

    (plus) A standardized labelling solution simplifies the overall IT architecture, making it easier to adapt to changes in business processes, volume, and complexity, and allowing for more straightforward scalability.

    (plus) Multiple applications offer flexibility to adapt to evolving business requirements or unexpected challenges during the transition.

    (minus) Adapting multiple applications to new processes or changes can be cumbersome and slow.

    Change Management Efforts

    (minus) Users accustomed to existing applications may find difficulties to transiting to a new system, which can affect productivity initially.

    (plus) On an ongoing basis, training users on an unified labelling solution reduces complexity and simplifies scaling training efforts as the organization grows.


    (plus) Users can continue working with familiar applications potentially reducing initial training costs and easing the transition.

    (minus) On an ongoing basis, training users on multiple labelling applications increases the complexity and duration of training sessions.

    (minus) Expertise may be fragmented across different applications, making it harder to resolve issues quickly and effectively.

    As shown in the matrix, standardizing and simplifying the labeling applications helps Syensqo streamline the labelling processes, ensures the label consistency, improves the operation efficiency and reduces maintenance costs. Therefore, adopting standardization and simplification is recommended for the future Syensqo labelling solution.


    See also

    1. SAP Label Management: Future Direction & Vision

    Image Added



    Change log

    Change History
    limit10

    By standardizing the labeling process and applications, Syensqo aligns with the principles of simplification and efficiency, reduce the complexity of your IT landscape, and potentially lower costs while maintaining compliance and improving operational effectiveness.

    See also

    Attachments
    previewfalse
    sortOrderdescending

    Change log

    change-history

    Workflow history

    Workflow Report
    parent@self
    hideheadertrue
    typeapprovals