You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 165 Next »

Status

  Approved

OwnerKUTANI-ext, Karunakar 
Stakeholders


Issue

Syensqo requires a CRM system as part of its sales lifecycle and uses salesforce.com to satisfy its CRM needs.

The current Syensqo CRM architecture consists of multiple instances of the salesforce.com application (Core CRM and ICARe), which includes the equivalent multi-instance integrations with the relevant backend systems (PRS, PF1, WP1) and point solutions (Dynasys, Gensuite, Qualtrics, Qliksense etc.,). Furthermore, the current CRM solution is built on a heavily customized instance of the salesforce.com environment, with numerous bespoke interfaces and disparate technologies.

This architecture is generating challenges with process/data consistency, scalability, process efficiency, and integration complexity and, therefore, is impeding Syensqo's ability to deliver a standard, consistent, and seamless customer experience. These inefficiencies are increasingly misaligned with Syensqo's strategic objectives of simplification, agility, and innovation.

Recommendation

Aligning with KDD040's recommendation of "Greenfield CRM implementation with Single Instance for all GBU's", we propose implementing Salesforce as the single-instance CRM and CX solution for all GBU's, to deliver a seamless customer experience, efficient processes, and consistent data management through a unified platform.

Recommendation Highlights of Option B: Harmonize Salesforce by unifying Core CRM and ICare, removing non-CRM features, and integrating Salesforce CRM capabilities with SAP S/4HANA

1. Incumbent Advantage: Salesforce's incumbent status leverages Syensqo's existing business and operational expertise. This alignment ensures efficient use of IT resources and infrastructure.

2. Change Management Risk: Adopting a new CX solution would entail high change management risks and disruptions. The unique UX and functional flow would necessitate major process overhauls and retraining efforts.

3. Cost-Effectiveness: Salesforce licenses are less expensive than other CX solutions in the market.

4. Enhanced SAP S/4HANA Integration: Salesforce's native integration with SAP S/4HANA has undergone significant enhancements over time, providing a more seamless and efficient connection. To fully leverage this standard integration, existing custom interfaces will require adjustments, enabling streamlined data exchange and optimized business processes.

5. Seamless Integration with iCertis: The iCertis contract authoring platform integrates effortlessly with Salesforce, providing a streamlined and embedded connection. This integration leverages the full potential of both solutions, enhancing contract management efficiency, accuracy, and visibility.

6. Comprehensive Functionalities: Synesqo's functional requirements are thoroughly met by Salesforce's extensive capabilities. Offering parity to other CX solutions, Salesforce guarantees a feature-rich environment for Synesqo's customer experience initiatives.


Background & Context

Syensqo's current customer relationship management (CRM) processes are supported by a complex architecture that involves multiple applications, including two Salesforce instances, On-Premises and Cloud applications, and various manual and automated system interfaces. The various functions implemented, along with their current challenges, are detailed below.

Core CRM interface provider.pdf

Core CRM interfaces consumer.pdf

  • The management of Customer Master Data is characterized by diverse creation and onboarding processes for corporate groups and customers, which are dispersed across multiple teams, including the transformation centre, data operations teams, and service teams. These processes utilize custom interfaces resulting in inefficiencies and potential data inconsistencies.
  • Although lead and opportunity lifecycles follow established sales cycles, custom logic is applied for lead scoring, lead assignments, revenue projections, and realized net sales tracking.
  • The pricing process is a complex, multi-platform system with varying GBU adoption. It integrates SAP ECC historical data and Dynasys forecasts into BW, generating Integrated Contribution Margin (ICM) insights, Customer Product Combination (CPC) price recommendations, and Contribution Margin improvements via Dataiku. This process utilizes custom objects for reviewing and committing, as well as custom interfaces for replicating prices to backend SAP.
  • OneQuote is a custom application that manages the quotation process, including creation, product configuration, pricing, approvals, and customer communications. However, it has not been adopted by all Global Business Units (GBUs). Quotation validity dates and price validity dates differ; the latter has a longer horizon to minimize the impact of policy changes on customer orders. OneQuote data is not replicated to ECC, its price conditions are replicated, and open orders are adjusted manually during price policy revisions.

The Composites GBU uses the ECC Quotation process, which differs from OneQuote due to material group level differences. The outputs of OneQuote and ECC Quote vary significantly in detail and format across GBUs. For forecasting purposes, quotes from both systems are integrated with Dynasys, but quote reporting is done in different tools. 

  • Complaints follow a guided process that includes registration, investigation, commercial response, customer communication, and closure. This process integrates with Gensuite for root cause analysis and resolution, as well as Qualtrics for customer feedback. However, quality inspections, returns handling, and credit memos are not linked back to the complaint. Custom functions facilitate acknowledgments and communications between internal and external teams, and to connect all related processes.
  • Sample management and tracking is a complex process, with some GBUs having an interface that integrates Salesforce, SAP, and CMC (a third-party sample provider) for automated sample transmission and information sharing. However, this interface needs to be replicated across all GBUs using CMC services for compliance purposes. The sample order process involves manual screening, which results in inefficiencies. Moreover, commercial samples management is entirely manual, relying on emails for inventory management, material records, and transactions, leading to significant communication challenges. A standardized approach is essential for capturing orders, communicating with production and R&I, and managing outbound logistics to end customers (both billable and non-billable).

Given the complexities and challenges identified in Syensqo's current CRM processes - including multiple applications, custom interfaces, and manual intervention - it is clear that a transformation is necessary. This KDD aims to explore potential solutions that will standardize CRM processes, providing a single customer view, efficient workflows, and automated processes. This will lead to improved efficiency, accuracy, and customer satisfaction.

Assumptions

  • SAP S/4HANA will serve as the ERP (Enterprise Resource Planning) application for managing and executing customer records, sales contracts, sales orders, logistics, warehousing, transportation, billing, and rebates.
  • Orders generated globally from ecommerce solutions (Salesforce + SAP) represent only 4% of total orders for 2023.
  • Salesforce also features a custom solution called Convergence, tailored for vendor management and procurement processes. As this capability is not customer-facing, it will be addressed in KDD002
  • A separate KDD052 is created, focusing on pricing strategy, optimization, approval processes, and execution.

Constraints

No constraints identified; further updates may be determined during detailed design phase. 

Impacts

  • Data Mapping: Mapping data fields from Salesforce to SAP accurately to ensure all critical data is transferred correctly.
  • Custom Development: Existing developments in Salesforce need to be reviewed and potentially deploy/enhance standard features in SAP.
  • Interface Redesign: Existing interfaces between Salesforce and other systems may need to be redesigned to work with SAP.
  • Training Programs: Implementing comprehensive training programs for users.

Business Rules

There are currently no known rules identified, but we will revisit and update if any emerge during the detailed design phase.

Options considered

Option A - Transition from Salesforce to SAP CX and integrate with SAP S/4HANA

This option utilizes a comprehensive SAP solution, encompassing the full SAP stack, to empower and streamline business processes. The primary benefit of this approach is that it leverages native/standard integration across all SAP products, thereby eliminating the need for duplicate data entry, ensuring alignment of enterprise structure and master data, and providing end-to-end traceability and transparency from 'Lead to Cash'.

  • The integrated master data management of SAP CX and S/4HANA creates a unified customer platform, delivering a seamless experience through real-time data replication, tailored corporate group management, and GBU segmentation, as well as team assignments, centralized organization management, and enhanced security.
  • The Lead and Opportunity lifecycles are streamlined with guided selling processes and real-time customer insights, providing a unified lead-to-cash cycle. This streamlined approach enables accurate sales revenue tracking and forecasting without the need for multiple system integrations. Moreover, machine learning-based lead intelligence and customer and relationship insights help identify high-quality leads and predict conversion likelihood.
  • The pricing solution with analytics capabilities supports informed pricing decisions, including pricing analysis for customer-product combinations, manufacturing cost analysis, pricing trend identification, order book comparison, blocked order detection, and financial indicator comparison. Additionally, it provides sales, volume, cost, and margin evolution analysis, active contract and flexibility metric display, and enables business users to access and maintain pricing information in S/4HANA for accurate quoting, driving revenue growth and profitability.
  • SAP CX streamlines the quotation process, encompassing guided selling, quotation configuration, pricing, and discounting, as well as approval workflows, customer-specific pricing, quote validity, and quote versioning. By integrating with S/4HANA, sales quotations can access real-time data, automate data synchronization, and simplify order-to-cash processing. This seamless integration ultimately provides a single source of truth for customer, product, and pricing data, increasing efficiency and accuracy throughout the quotation-to-cash process.
  • Contract Management provides a centralized repository for storing and managing contracts, automated workflows for approval and notification processes, and real-time tracking of contract validity periods, product information, and pricing. Additionally, S/4HANA provides advanced analytics and reporting capabilities, enabling real-time insights into contract performance and supporting data-driven decision making.
  • The complaint management process is streamlined by integrating it with sales orders, quality inspections, returns handling, and credit memos. The guided process automates registration, investigation, commercial response, and tracking, as well as customer communication and closure, with automation of acknowledgments and communications between teams. Additionally, SAP CX and S/4HANA integrate with Qualtrics for customer feedback, providing a closed-loop process. 
  • Sales order management standardizes and automates the sample order process, eliminating manual screening and inefficiencies. S/4HANA's inventory management and logistics capabilities will efficiently manage outbound logistics for end customers and distributors.

Option B - Harmonize Salesforce by unifying Core CRM and ICare, removing non-CRM features, and integrating Salesforce CRM capabilities with SAP S/4HANA

This option leverages the Salesforce's CRM platform and capabilities, with the intention of harmonizing the existing multi-tenant landscape into a single Salesforce landscape. Any non-CRM functions that can be migrated to S/4HANA will be migrated to consolidate core ERP functions. This option will require integration between Salesforce and S/4HANA to support a seamless Lead to Cash execution process and enable end-to-end business process execution and reporting capabilities.

  • Streamline master data processes by retaining Prospect creation and Customer conversion in Salesforce, eliminating PRS, and integrating Salesforce with S/4HANA for real-time data replication. Align GBU segmentation with S/4HANA's organizational structure and map team assignments to S/4HANA's business partner concepts, reducing interfaces and enhancing efficiency.

  • Continue using Salesforce for lead and opportunity management, and revenue projection maintenance. However, leverage S/4HANA data for forecasting and realized sales/revenue data, ensuring an accurate view of sales performance.

  • Price setting will continue in Salesforce, integrated with Dataiku for price optimizations. Salesforce will remain the platform for price execution via quotation creation. Once quotations are released, prices will be replicated to S/4HANA. Furthermore, Salesforce quotations will be replicated to S/4HANA to ensure end-to-end Quote-to-Cash process integration. To enhance visibility, Price Transparency dashboards will be implemented using S/4HANA data, covering sales revenue, prices, forward costing, orders, and contract information.

  • Contract management will be centralized in S/4HANA, simplifying processes, reducing errors, and boosting efficiency. S/4HANA will serve as the single source of truth, providing accurate and visible data for informed decision-making. The contract dashboard and KPIs will be driven by S/4HANA data, offering real-time insights and performance metrics. Additionally, necessary metadata required for contract database management will be replicated from S/4HANA to Salesforce.

  • Salesforce will handle case management and approvals, integrating with S/4HANA for quality notifications and corrective actions. S/4HANA will manage investigation outcomes, including returns and settlements, and update Salesforce cases for tracking. Feedback tracking will remain in Qualtrics, with reporting in both Salesforce and S/4HANA for a unified view.

  • Salesforce manages and approves samples, then integrates with S/4HANA for logistics and fulfilment. Third-party integrations remain in Salesforce, with S/4HANA updates flowing in for tracking and monitoring purposes.

Option C - Maintain Salesforce in its current state, retaining Core CRM and ICare, and integrate it with SAP S/4HANA.

This option retains current Salesforce setup, including its custom solutions and third-party application integrations, while establishing integration with S/4HANA. S/4HANA will be utilized as a logistics execution tool, and the existing ECC interfaces will be redesigned to connect with S/4HANA, incorporating necessary modifications for optimal performance.

  • Retain Salesforce for Prospect and Customer conversion and maintain PRS as the central system for corporate master data management, integrating with S/4HANA for data synchronizations. Align GBU segmentation with S/4HANA's organization structure, map team assignments, and retain data governance tools like Mappy and Gridbuddy.

  • Utilize Pardot for lead generation and integrate with Salesforce for nurturing and conversion. Continue using Salesforce for opportunity management, revenue projections, and manual sales tracking using S/4HANA reports. However, leverage S/4HANA for opportunity dashboards and forecasting, providing a unified sales performance view.

  • Implement Price Transparency dashboards in S/4HANA for sales revenue, price analysis, and forward costing, integrating with Dataiku for price optimization. Continue using Salesforce for sales price setting and execution, replicating accepted quotations to S/4HANA for pricing determinations. Update document flow from S/4HANA to Salesforce for Quote to Cash integration.

  • Salesforce will remain the contract management hub, integrating contract data with S/4HANAand reporting tools for comprehensive contract and customer 360 dashboards.

  • Salesforce will handle case management and approvals, while Gensuite tracks corrective and preventive actions. Integrate Salesforce cases with S/4HANA for commercial responses and returns, and manage returns and replacements in S/4HANA, syncing updates back to Salesforce. Feedback tracking will remain in Qualtrics, with reporting visible in both Salesforce and S/4HANA.

  • Salesforce will manage and approve samples, integrating with S/4HANA for logistics and fulfilment. Third-party integrations will remain in Salesforce, with S/4HANA updates flowing in for tracking and monitoring purposes.

Evaluation


Option A - Transition from Salesforce to SAP CX and integrate with SAP S/4HANA

Option B - Harmonize Salesforce by unifying Core CRM and ICare, removing non-CRM features, and integrating Salesforce CRM capabilities with SAP S/4HANA
Option C - Maintain Salesforce in its current state, retaining Core CRM and ICare, and integrate it with SAP S/4HANA.
Alignment with "Simplification principle"

(plus) Moving to SAP CX aligns with simplification, as it unifies processes across SAP platforms, streamlining the technology landscape.

(minus) Removing non-CRM features simplifies Salesforce, but maintaining Salesforce and integrating with SAP S/4HANA adds complexity.

(minus) Maintaining the current system adds complexity, particularly in managing non-CRM features and integration challenges.

Alignment with "Standardization principle"

(plus) Full alignment with SAP S/4HANA, providing standardized processes across the GBU's through a unified platform.

(minus) Salesforce can be standardized to an extent, but the integration with SAP S/4HANA may require custom solutions that reduce standardization.

(minus) Maintaining Salesforce in its current state limits the ability to fully standardize processes across the organization.

System Integration

(plus) High integration with SAP S/4HANA; seamless integration across the entire SAP ecosystem.

(plus) Salesforce's native integration with SAP S/4HANA has undergone significant enhancements over time, providing a more seamless and efficient connection.

(minus) Existing custom integrations may not fully optimize integration with SAP S/4HANA, leading to complexity over time.

Implementation Time

(minus) Transitioning to SAP CX and integrating it with SAP S/4HANA will take time, including data migration, system setup, and full alignment with business processes.

(plus) Harmonizing Salesforce and integrating it with SAP S/4HANA will require less time than a complete system change, but there is still a need for customization.

(plus) Minimal changes to Salesforce, with the focus on integration with SAP S/4HANA.

User Training & Change Management

(minus) Significant training and change management required to transition to SAP CX and adapt to new processes.

(plus) Users need to adjust to the streamlined Salesforce system, but they are already familiar with the platform.

(plus) Minimal user training needed since the system remains largely unchanged. Focused only on integration with SAP S/4HANA.

Cost of Implementation

(minus) Transitioning to SAP CX and deep integration with SAP S/4HANA involves substantial costs (licenses, migration, customization, etc.).

(plus) Lower than a full transition, but still involves costs for system optimization and integration efforts.

(plus) Maintaining Salesforce as-is involves minimal costs, with most expenses related to integration with SAP S/4HANA.

Long-term Scalability

(plus) SAP CX offers excellent scalability, especially when integrated with SAP S/4HANA, allowing for growth in users, data, and complex workflows.

(minus) Salesforce can scale, but integration with SAP S/4HANA may present some limits as complexity grows.

(minus) Maintaining the current system could limit future scalability, particularly when handling large data volumes and complex processes.

Customization Flexibility

(minus) Customizing SAP CX V2 can be more complex compared to Salesforce. Though it provides extensive flexibility, customizing it requires specific SAP expertise and can take more time due to its tight integration with SAP S4HANA and alignment with enterprise-wide processes.

(plus) Salesforce is highly customizable, offering flexibility to align with evolving business needs and complex workflows.

(minus) Maintaining Salesforce in its current form may lead to legacy technical debt, reducing flexibility for future changes.

System Maintenance

(plus) SAP CX, as part of the SAP ecosystem, provides consolidated system maintenance with SAP S/4HANA.

(plus) Harmonizing Salesforce reduces some maintenance complexity but still requires custom integrations.

(minus) As Salesforce is maintained in its current state, technical debt and performance challenges may increase maintenance efforts over time.

Risk of Disruption

(minus) Transitioning to a new system (SAP CX) poses a high risk of operational disruption during implementation.

(plus) Some disruption during the streamlining and integration process, but users remain on Salesforce, reducing the overall risk.

(plus) Minimal disruption, as Salesforce remains unchanged, with integration as the primary focus.

Customer Experience Impact

(plus) SAP CX is continuously evolving, with future-proof capabilities, especially when integrated with SAP S/4HANA.

(minus) Salesforce will evolve, but long-term alignment with SAP S/4HANA may create complexity.

(minus) Retaining the existing system may limit the organization’s ability to take advantage of future technological advancements.

Change log

Version Published Changed By Comment
CURRENT (v. 165) Oct 16, 2024 14:42 KUTANI-ext, Karunakar
v. 199 Oct 16, 2024 14:42 KUTANI-ext, Karunakar
v. 198 Oct 16, 2024 14:41 KUTANI-ext, Karunakar
v. 197 Oct 16, 2024 12:12 WENNINGER-ext, Sascha
v. 196 Oct 16, 2024 12:09 KUTANI-ext, Karunakar
v. 195 Oct 16, 2024 12:07 KUTANI-ext, Karunakar
v. 194 Oct 16, 2024 10:13 KUTANI-ext, Karunakar
v. 193 Oct 16, 2024 10:10 KUTANI-ext, Karunakar
v. 192 Oct 16, 2024 10:08 KUTANI-ext, Karunakar
v. 191 Oct 16, 2024 09:56 KUTANI-ext, Karunakar

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels