Issue

A request was made by the Syensqo Manufacturing excellence team to consider the option of having one Quality system across Syensqo.

Rationale behind the request:

• No Standardized process within and across the GBUs.

• No standardized reports possible within the plants in a GBU and across GBU .
• Currently Labware is configured in a way which the local sites want to define it.
• In Labware / Web LIMS the Samples are generated manually without any trigger from upstream processes, resulting in a lack of control and  process integration.
• In Labware / Web LIMS the operator can freely define whether execute a test or carry over previous results, without any predefined control.

Options available:

Following are the options proposed:

Option 1  – As-Is Approach

Under this approach, each GBUs continues operating its existing Quality Management setup. Different LIMS versions and configurations remain in use across sites, which means data structures, reporting formats, and inspection results will continue to vary.

Option 2 - Hybrid Approach (CM As-Is / P&C and SpP Standardized)

Under this approach, Composites  retains its current configuration (“As-Is”), while other GBU’s  standardize their quality processes and integrate with SAP S/4HANA. This hybrid model promotes partial standardization while reducing disruption to ongoing CM operations. This option will also enable Syensqo to roll out a centralized Quality Management Organization.

Option 3 – Technology Standardization (All GBUs Move to different LabWare systems, no Process changes in Labware)

This option envisions a complete migration where all GBUs (including P&C, SpP, and CM) move to a unified LabWare Technology(One instance for CM and other instance for rest of GBU’s). This option acknowledge the possibility for P&C to unify their plants in the current Labware implementation, removing WEBLIMS.

Option 4 – Full Process Standardization (All GBUs Move to unified Labware Design)

This option envisions a complete migration where all GBUs (including P&C, SpP, and CM) move to a unified LabWare Design (One instance for CM and other instance for rest of GBU’s).. Quality processes would be fully standardized across the enterprise, ensuring consistent data structures, harmonized reporting formats, and a single source of truth for all inspection results. It requires a deep redesign of the Labware implementation.

Background & Context

Current Status and Challenges:

Syensqo currently operates with a distributed Quality Organization, where quality management responsibilities, processes, and systems are spread across multiple business units and sites. Over time, each GBU/plant has implemented its own technology landscape, leading to the coexistence of different Quality Management Systems, LIMS, and data management tools.

• Lack of Standardization Across GBUs and Sites
  • There is no standardized process within or across the Global Business Units (GBUs)
  • Measured values vary because LabWare configurations and test setups differ across sites.
    
    
• Inconsistent Reporting and Configuration
  
  
  • It is not possible to generate standardized reports either within a GBU or across GBUs due to differences in local configurations.

• • LabWare and WebLIMS are currently configured independently by each site, based on local preferences and practices, leading to different data models and test definitions.
    
    
• Lack of Integration and Process Control
  
  
  • In LabWare / WebLIMS, samples can be created manually without any trigger from upstream processes (e.g., production, batch release, or quality notification).
    • This results in a lack of integration and limited traceability between quality results and operational data.
  • Operators can manually decide whether to execute a test or reuse previous results, this step is ad-hoc and without predefined system controls or approval steps.

link: GBU Site wise analysis

link: Equipment list 

Impacts

The Selected approach does not have an impact on the infrastructure, other SAP modules or systems, data migration and cleansing and inflight projects,

It does have an impact on the business processes and the interfaces. 

The Business process models needs to be adjusted based on the recommended option, Interface will be added to scope to connect S4 with Web LIMS and Labware.

Option considered

Option 1  – As-Is Approach

Under this approach, each GBU continues operating its existing Quality Management setup. Different LIMS/Labware versions and configurations remain in use across sites, which means data structures, reporting formats, and inspection results will continue to vary.

This is after carefully considering each options and its impacts to the cost, timelines and change impacts. the options were presented to Steerco on 26th Nov 2025 and the decision was endorsed to go ahead with Option 1.

Evaluation

See also

Change log