Status

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

Issue

This Key Decision Document (KDD) serves as a comprehensive guide outlining the decisions, considerations, and recommendations essential for the implementation and management of maintenance processes at Syensqo. The document aims to clarify the rationale behind evaluating whether to process maintenance orders using a phase-based approach, determined by predefined order types (Reactive Maintenance and Proactive Maintenance), versus Standard Maintenance Processing across Syensqo plants.

Key areas covered in this document include:

  • Benefits and drawbacks of each solution, including factors such as efficiency, accuracy, safety, and compliance.
  • Overview & Background
  • Design Options 
  • Evaluation
  • Recommendation
  • Business & Project Impacts

The purpose and structure of the KDD ensure clarity, transparency, and accountability throughout the process of adopting and utilizing the chosen maintenance approach within Syensqo.


Recommendation

After thorough evaluation of the maintenance management processes, it is recommended that Syensqo adopts the Phase-Based Maintenance Process. This approach offers a structured and flexible implementation that caters to the diverse needs of Syensqo’s various plant sizes and complexities. By managing maintenance activities according to predefined phases within a complete process, Syensqo can enhance efficiency and operational performance.

This method focuses on core maintenance activities and allows for the inclusion of specialized processes as required. The integration of new Fiori applications and features within the Phase-Based Maintenance Process will facilitate a smoother user experience and enhanced process tracking.

Overall, this comprehensive adoption aligns with Syensqo’s strategic objectives of standardization, simplification, efficiency, and flexibility, ensuring a robust and


Background & Context

Syensqo operates and maintains a diverse number of plants globally, each with different sizes and complexity levels. Maintenance teams are tasked with a wide range of activities to ensure the smooth operation of these plants. The goal is to achieve standardization and simplification across its maintenance processes, enhancing efficiency, reducing downtime, and improving overall operational performance.

The current maintenance system faces challenges in meeting the dynamic and varied needs of different plants, ranging from large, complex operations with extensive maintenance requirements to smaller sites with more straightforward needs. The maintenance activities cover a broad spectrum, including corrective, preventative, emergency, predictive, refurbishment, shutdown, and projects, each with unique demands and complexities.

The organization’s strategic objectives include:

  • Standardization: Creating uniform maintenance processes across all plants to ensure consistency, improve compliance, and facilitate easier management and reporting.
  • Simplification: Streamlining maintenance operations to reduce complexity, enhance usability, and improve efficiency.
  • Efficiency: Optimizing maintenance activities to minimize downtime, reduce costs, and improve asset reliability and performance.
  • Flexibility: Ensuring the maintenance process can adapt to the varied needs of different plants and types of maintenance activities.


Assumptions

Maintenance Activities: All maintenance tasks will be documented in S/4HANA for accountability and traceability.


Constraints

Specialized processes: Refurbishment and Calibration will continue to be managed according to the standard maintenance process.


Impacts

User Training: Extensive training will be required for users to adapt to new systems and business processes. This training will need to cover several key areas to ensure a smooth transition and effective utilization of the new maintenance processes.

Data migration: 

  • Compatibility issues between legacy systems and the new S/4HANA system, requiring data cleansing, transformation and mapping.
  • Testing and validation to confirm that migrated data accurately reflects the original datasets.

Reporting: More efficient tracking, management and reporting of maintenance activities, leading to better decision-making and transparency.

User Experience: Supported by Fiori applications, the system provides a more intuitive and user-friendly interface. It includes customizable dashboards that enable users to quickly access and view relevant information.


Business Rules

Process Alignment

  • Maintenance orders must be classified by their order type to ensure appropriate processing.
  • Phase control codes should be used to manage the progression of orders and prevent unauthorized transitions.
  • User statuses and phase control codes should not be used simultaneously to avoid conflicts.

Additional defined requirements and further updates will be determined during the detailed design phase.


Options considered

Option A: Phase-Based Maintenance Process

The SAP S/4HANA Phase-Based Maintenance Process is a structured approach to managing maintenance activities by implementing the system in clearly defined phases. Each phase targets specific maintenance order types, such as Reactive Maintenance and Proactive Maintenance, allowing for incremental adoption and adaptation. This approach is particularly beneficial for organizations with diverse plant sizes and complexities, as it offers flexibility and scalability. By rolling out the system in phases, Syensqo can systematically address the unique needs of each plant, mitigate risks and ensure a smooth transition with minimal disruption to ongoing operations.

  • An end-to-end process that is structured according to nine phases.
  • The individual phases are divided into subphases.
  • You can track the life cycle of the maintenance processes using phases as an alternative to User Statuses.
  • Track and schedule compliance of the maintenance backlogs according to the phases or subphases in several order list views.
  • Simplified and granular phase management to guide users along the process
  • Supported with new Fiori applications and lots of features

Maintenance orders are classified by their order type, which represents a specific business process and dictates the realization and subsequent processing options for individual orders. The phase-based maintenance process supports Reactive Maintenance and Proactive Maintenance. The associated order types define the relevant process phases that each maintenance order will go through.

Reactive Maintenance: This process enables the maintenance of technical objects in response to breakdowns or failures, minimizing asset downtime and enhancing productivity. It also encompasses processes for Emergency Work and Minor Work to address additional maintenance needs promptly and effectively.

Proactive Maintenance: This process focuses on preventing asset failures by implementing preventive maintenance and proactive measures. It ensures optimal asset utilization and availability, promoting efficient performance and reducing costs associated with breakdowns. 

Phase control codes enable Syensqo to manage the progression of orders from one subphase to another. These codes can be activated at the order header or order operation level to prevent a maintenance order or operation from moving to a designated subphase. In this way, phase control codes function similarly to user statuses. However, it is important to note that phase control codes and user statuses should not be used simultaneously. 

Specialized processes such as refurbishment and calibration are not covered by the Phase-Based Maintenance Process. These processes will instead be managed according to the standard maintenance process. This ensures that specific workflows and requirements for refurbishment and calibration activities are addressed effectively within the organization's maintenance management framework.

Option B: Standard SAP Maintenance Process

The Standard SAP Maintenance Process involves a comprehensive, single-step implementation of the SAP S/4HANA system across all plants within Syensqo. This approach aims to standardize maintenance processes, providing a uniform system that streamlines operations and ensures consistency. By deploying the system all at once, Syensqo can quickly leverage the full capabilities of SAP S/4HANA, enabling immediate utilization of all features and functionalities. This option is designed for organizations that prioritize rapid deployment and uniformity across their operations, aiming to enhance efficiency and reduce complexity in managing maintenance activities.

Benefits:

  • Operational Efficiency: Standardizing processes across all plants enhances efficiency by streamlining workflows and optimizing resource allocation. Real-time data integration facilitates quicker decision-making and improves overall operational performance.
  • Compliance and Risk Management: Ensure compliance with industry standards and regulatory requirements through standardized maintenance practices and data management.
  • Comprehensive Coverage: The standard SAP Maintenance Process accommodates all types of maintenance work and processes, including corrective, preventive, predictive, refurbishment and calibration activities.
  • Enhanced Decision-Making: Access to accurate and timely information enables informed decision-making for maintenance planning and resource allocation.
  • User Adoption:  The streamlined deployment and comprehensive support programs provided during implementation promote user adoption and engagement across the organization. Training and change management initiatives ensure smooth transitions and maximize the utilization of new system capabilities.


Note: There is no direct migration path from the standard maintenance process to the phase-based process if considered at a later stage. For instance, transitioning from corrective maintenance under the standard process to a phased approach like reactive maintenance would require a separate implementation strategy and potentially additional customization to align with new operational needs and configurations. Thus, careful planning and strategic alignment with organizational goals are essential when determining the initial implementation approach.


 Comparison Table 

CriteriaPhase-Based Maintenance ProcessStandard Maintenance Process
Process ApproachStructured: Divided into phases, allowing for incremental adoption and customization per phase.Comprehensive: Implements all maintenance processes simultaneously, ensuring uniformity and immediate system-wide deployment.
Key Functionality CoverageCore-focused: Initially centers on core maintenance activities (corrective, preventive), with flexibility to add specialized processes in later phases.Comprehensive: Covers all maintenance types (corrective, preventive, predictive, refurbishment, calibration) from the outset, supporting comprehensive maintenance operations.
CustomizationFlexible: Allows customization in each phase based on specific plant needs and operational requirements.Limited: Standardized processes may not align with unique operational nuances, minimal customization per plant.
Integration ComplexitySimplified: Due to phased approach, focused implementation allows for gradual system adjustments.Complex: Simultaneous deployment across all plants may pose initial disruption in operations, requires detailed integration planning.
User ExperienceGradual: Adoption with phased training and support facilitates smoother transition and user engagement.Immediate: System-wide adoption with comprehensive training may pose challenges in change management and user acceptance.
Operational EfficiencyEnhanced: Over time as each phase optimizes processes based on feedback and performance metrics.Immediate: Efficiency gains through standardized processes and real-time data integration support quick decision-making.
ScalabilityScalable: Approach suitable for varying plant sizes and complexities, adapts maintenance strategies based on phased implementation.Scalable: Requires additional customization for future adaptations, challenges in uniformity across diverse operational environments.
Maintenance ConsistencyPotential: For transitional inconsistencies in maintenance practices during phased rollout.Consistent: Ensures consistency in maintenance practices across all locations, minimizing operational variations.


Evaluation

Based on the comprehensive evaluation, the Phase-Based Maintenance Process demonstrates a significant alignment with Syensqo’s strategic objectives and operational requirements. This approach excels in operational efficiency, standard configuration options and scalability, making it particularly suitable for Syensqo’s diverse plant sizes and complexities. The structured nature of the Phase-Based Maintenance Process allows for detailed management of maintenance activities, promoting improved asset reliability and reduced downtime. The integration of new Fiori applications and enhanced process tracking features further contribute to a smoother user experience, facilitating better adoption and engagement across the organization.

While the Standard Maintenance Process offers immediate compliance and consistency benefits, it falls short in areas such as flexibility and user experience. The Phase-Based Maintenance Process, on the other hand, provides a more adaptable framework, enabling Syensqo to effectively address the unique needs of each plant. This flexibility is crucial for achieving long-term efficiency and operational performance improvements. Therefore, the Phase-Based Maintenance Process is recommended for implementation as part of Syensqo’s transformation to S/4HANA, ensuring a robust and scalable maintenance management framework that supports the organization’s goals of standardization, simplification, efficiency and flexibility.


CriteriaWeightPhase-Based Maintenance ProcessStandard Maintenance Process
Operational EfficiencyVHVery HighHigh
Compliance and Risk ManagementHHighVery High
CustomizationMVery HighLow
Integration ComplexityMMediumHigh
User ExperienceMHighMedium
ScalabilityMVery HighMedium
Maintenance ConsistencyMHighVery High
Overall
HighMedium

See also

The following section describes relevant documentation:

Document Name

Description




Business Definitions (Glossary)

Acronym / Term

Definition

KDD

Key Design Document





EAM

Enterprise Asset Management 

PM

Plant Maintenance

SyMaxSyensqo Maintenance Excellence


VHVery High
High
MMedium
LLow


Change log

Workflow history