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

Compare with Current View Page History

« Previous Version 23 Next »

Status

  Approved

OwnerKUTANI-ext, Karunakar 
Stakeholders

Issue

The purpose of this key design decision document is to evaluate alternative CRM solutions and determine the best path forward for enhancing Syensqo’s customer relationship management functions. This evaluation will consider critical factors such as:

  • System Integration: The ability to seamlessly integrate with Syensqo's existing and future enterprise systems.
  • Scalability and Flexibility: Support for Syensqo's growth trajectory and adaptability to changing business needs.
  • Functionality and User Experience: Comprehensive CRM features and an intuitive user interface that enhances user adoption and productivity.
  • Cost Efficiency: A cost-effective solution that provides a strong return on investment.
  • Risk and Change Management: Identifying and mitigating potential risks associated with transitioning to a new CRM system.

Recommendation

After a thorough evaluation of Syensqo’s current CRM system and a comprehensive analysis of alternative solutions, it is recommended that Syensqo transition from Salesforce to SAP for its customer relationship management needs. This strategic transition will address Syensqo's current challenges, improve customer engagement, and position Syensqo for sustained growth and success.

The key reasons driving this recommendation are:

  • The SAP’s products are already integrated. Salesforce integration would have to be custom developed by Syensqo. In addition, SAP’s future roadmap will deliver more native integration with S4/HANA, resulting in less investment required by Syensqo.
  • SAP option has richer functionalities than Salesforce.
  • Total Cost of Ownership (TCO) of Salesforce solution is expected to be considerably higher than SAP option due to high number of interfaces required for Salesforce.
  • SAP’s user interface “Fiori” enables seamless experience to all users regardless of the SAP application being used.

These points place SAP in a better position to enable the capabilities that Syensqo requires to perform the business processes and experience an unified user-experience across all applications. 

Background & Context

The current customer relationship management business processes at Syensqo are primarily supported by Salesforce, along with a variety of other On-Premises and Cloud applications that often integrate with Salesforce. The diagram below depicts the current application architecture.

The current application architecture is very complex, involving two Salesforce instances and numerous manual and system interfaces that impact the performance of business processes and data integrity.

Key Issues:

  • Double Data Entry: Business processes require manual data entry across multiple systems and manual tasks/interfaces, leading to inefficiencies and errors.
  • System Integration: Limited and complex integration between Salesforce and other applications, such as SAP, results in data structures not being fully replicated in Salesforce. This increases the risk for data integrity issues across systems and adds to ongoing maintenance costs.
  • Ongoing Maintenance Cost: Salesforce is heavily customized to mirror data from other Syensqo’s applications (e.g., Customer Master, Quotations, Contracts, and Sample requests), which impacts future upgrade costs.
  • Customization for Different GBUs: The two Salesforce instances cater to the requirements of different Global Business Units (GBUs), with numerous customizations developed to support current business processes, further complicating the architecture.

Further developments are still required to consolidate information and harmonise data across these applications:

  • Custom Interfaces: Development of custom interfaces to update customer and product data between Salesforce and SAP.
  • Reports/Dashboards: Creation of consolidated reports and dashboards for Customer 360, Opportunities dashboard, etc., across Salesforce, Dynasys, and SAP.
  • Database Consolidation: Consolidation of customer complaint databases (Salesforce) and economizing Gensuite.

“Manage Customer Lifecycle” business process is enabled by the following applications: Salesforce, Pardot, Dynasys, Dataiku, Data Lake. These applications add new layers of issues and complexity to the existing architecture and Syensqo’s business process, for example:

  • Quotation management is custom built with no integration to pricing data that resides in SAP. Additionally, there is no linkage between quotations and orders, making it difficult to track the end-to-end execution of sales processes.
  • Contract profitability reports are not able to be performed as contract execution is not integrated with SAP.
  • Not user-friendly, difficult to navigate, with manual replication of the same information required in multiple areas of the systems.

Similarly, for managing “Manage Issue to Resolution” (Customer Complaints, Customer Request and Samples), four applications are currently in place: Salesforce, Gensuite, Qualtrics, Google. These applications vary in capabilities amongst each other and do not fully integrate with Salesforce, to provide the 360º customer view across various customer complaints, requests and samples. Overall, the same issues highlighted before also occur within this business process:

  • Double data entry to capture customer insights and feedback from applications other than Salesforce.
  • GBU’s have different solutions which creates a challenge to consolidate customer interactions for global customers.
  • Case management and customer feedback processes are managed differently across the GBU’s, which does not allow to report on common KPIs to measure Syensqo’s performance and customer’s satisfaction.

Assumptions

SAP S4/HANA will be the ERP (Enterprise Resource Planning) application that will enable the management and execution of customer records, sales contracts, sales orders, logistics, warehousing, transportation, billing and rebates. The recommended solution must integrate with S4/HANA to ensure seamless business process execution and master data integrity.

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 to ensure they are proficient with SAP

Business Rules


Options considered

Option A: Manage Customer Lifecycle” and “Manage Issue to Resolution” processes enabled by SAP

Option A leverages a full SAP solution to enable the business processes. The key advantage of this solution is the use of standard integration across all SAP products. This reduces the need for double-data entry, misalignment of enterprise structure and master data and streamlines the business processes providing a full traceability and transparency from “Lead to Cash”.

Other advantages:

  1. Integrated Platform: Manage Customer Lifecycle and Issue to Resolution processes integrates seamlessly with SAP S/4HANA, providing a unified platform for CRM and ERP functionalities. This integration can streamline operations and enhance overall business efficiency.

  2. Data Consistency: Having CRM and ERP data on a single platform reduces data silos and ensures real-time data synchronization, leading to better decision-making and operational insights.

  3. Advanced Analytics: Leveraging SAP’s analytics capabilities, including SAP Analytics Cloud and embedded analytics in SAP S/4HANA, allows for sophisticated reporting, predictive analytics, and business intelligence.

  4. Customization and Flexibility: SAP offers robust customization options and scalability, to tailor the system to specific business needs and scale operations as they grow.

  5. Security and Compliance: SAP’s strong focus on security and compliance, along with its extensive experience in enterprise solutions, provides peace of mind for organizations handling sensitive data or operating in regulated industries.

The diagrams below outline the business processes that will be supported by Option 1. 


Option B: “Manage Customer Lifecycle” and “Manage Issue to Resolution” processes enabled by SAP and Salesforce: It includes S4/HANA and Salesforce.


Evaluation



Option A

Option B
Functional Capability

(plus) SAP option is richer in functionality

(plus) Salesforce has better ease of use

Alignment with "Simplification principle"

(plus) SAP roadmap includes additional standard integration between the SAP 
applications. 

(minus) The number of custom developments is significantly higher in the Salesforce option due to complex integration between S4/HANA and Salesforce.

Integration with S4/ HANA

(plus) Standard integration is now available to support Syensqo's business process.

(minus) Salesforce and S4/HANA integration would have to be custom developed regardless.

Implementation Cost

(minus) Change Management and Training costs are higher in SAP, since Salesforce is already in place in most regions.

(minus) Salesforce and S4/HANA integration would have to be custom developed regardless.

License Cost

(plus) Offers an opportunity to lower license 
costs due to Syensqo's Strategy “SAP First”.

(plus) Yet to be confirmed

Infrastructure Cost

(plus) Equally the same, as both leverage a combination of S4/HANA and Cloud applications. 

(plus) Equally the same, as both leverage a combination of S4/HANA and Cloud applications. 

Maintenance Cost

(plus) Leveraging pre-built integration content and unified support structures provided by SAP significantly reduces maintenance cost.

(minus) Higher in Salesforce due to large number of interfaces between S4/HANA and Salesforce. Any updates or changes in one system may necessitate adjustments in the integration setup.

Upgrades

(plus) Upgrades are typically rolled out automatically, with SAP ensuring backward compatibility and minimal disruption 

(minus) Coordinating upgrades and ensuring compatibility between the two systems can be challenging and time-consuming

See also


No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 23) 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
v. 190 Oct 16, 2024 09:32 KUTANI-ext, Karunakar
v. 189 Oct 16, 2024 09:30 KUTANI-ext, Karunakar
v. 188 Oct 16, 2024 09:00 KUTANI-ext, Karunakar
v. 187 Oct 16, 2024 08:21 KUTANI-ext, Karunakar
v. 186 Oct 16, 2024 08:16 KUTANI-ext, Karunakar
v. 185 Oct 16, 2024 07:51 KUTANI-ext, Karunakar
v. 184 Oct 16, 2024 07:22 KUTANI-ext, Karunakar
v. 183 Oct 16, 2024 06:08 WENNINGER-ext, Sascha
v. 182 Oct 16, 2024 05:59 WENNINGER-ext, Sascha
v. 181 Oct 15, 2024 17:09 GONZALVEZ-ext, Antonio
v. 180 Oct 15, 2024 13:55 KUTANI-ext, Karunakar
v. 179 Oct 15, 2024 13:54 KUTANI-ext, Karunakar
v. 178 Oct 15, 2024 13:15 KUTANI-ext, Karunakar
v. 177 Oct 15, 2024 12:54 KUTANI-ext, Karunakar
v. 176 Oct 15, 2024 07:14 KUTANI-ext, Karunakar
v. 175 Oct 15, 2024 07:00 KUTANI-ext, Karunakar
v. 174 Oct 15, 2024 06:41 KUTANI-ext, Karunakar
v. 173 Oct 15, 2024 06:32 KUTANI-ext, Karunakar
v. 172 Oct 15, 2024 06:27 KUTANI-ext, Karunakar
v. 171 Oct 15, 2024 06:24 KUTANI-ext, Karunakar
v. 170 Oct 15, 2024 06:20 KUTANI-ext, Karunakar
v. 169 Oct 15, 2024 06:08 KUTANI-ext, Karunakar
v. 168 Oct 15, 2024 02:59 KUTANI-ext, Karunakar
v. 167 Oct 15, 2024 02:56 KUTANI-ext, Karunakar
v. 166 Oct 15, 2024 02:55 KUTANI-ext, Karunakar
v. 165 Oct 15, 2024 02:53 KUTANI-ext, Karunakar
v. 164 Oct 14, 2024 15:42 KUTANI-ext, Karunakar
v. 163 Oct 14, 2024 15:39 KUTANI-ext, Karunakar
v. 162 Oct 14, 2024 14:57 KUTANI-ext, Karunakar
v. 161 Oct 14, 2024 12:45 KUTANI-ext, Karunakar
v. 160 Oct 14, 2024 12:29 KUTANI-ext, Karunakar
v. 159 Oct 14, 2024 08:42 KUTANI-ext, Karunakar
v. 158 Oct 14, 2024 07:58 KUTANI-ext, Karunakar
v. 157 Oct 14, 2024 07:48 KUTANI-ext, Karunakar
v. 156 Oct 14, 2024 07:24 KUTANI-ext, Karunakar
v. 155 Oct 14, 2024 06:58 KUTANI-ext, Karunakar
v. 154 Oct 11, 2024 10:32 KUTANI-ext, Karunakar
v. 153 Oct 11, 2024 10:30 KUTANI-ext, Karunakar
v. 152 Oct 11, 2024 10:21 KUTANI-ext, Karunakar
v. 151 Oct 11, 2024 10:05 KUTANI-ext, Karunakar
v. 150 Oct 11, 2024 10:00 KUTANI-ext, Karunakar
v. 149 Oct 10, 2024 13:30 KUTANI-ext, Karunakar
v. 148 Oct 10, 2024 12:57 KUTANI-ext, Karunakar
v. 147 Oct 10, 2024 12:01 KUTANI-ext, Karunakar
v. 146 Oct 09, 2024 13:19 KUTANI-ext, Karunakar
v. 145 Oct 09, 2024 13:13 KUTANI-ext, Karunakar
v. 144 Oct 09, 2024 12:28 KUTANI-ext, Karunakar
v. 143 Oct 09, 2024 11:54 KUTANI-ext, Karunakar
v. 142 Sept 27, 2024 09:05 KUTANI-ext, Karunakar
v. 141 Sept 26, 2024 12:35 KUTANI-ext, Karunakar
v. 140 Aug 03, 2024 07:14 KUTANI-ext, Karunakar
v. 139 Jul 23, 2024 14:30 WENNINGER-ext, Sascha
v. 138 Jul 23, 2024 12:10 KUTANI-ext, Karunakar
v. 137 Jul 23, 2024 12:05 KUTANI-ext, Karunakar
v. 136 Jul 23, 2024 12:04 KUTANI-ext, Karunakar
v. 135 Jul 23, 2024 12:02 KUTANI-ext, Karunakar
v. 134 Jul 23, 2024 11:51 KUTANI-ext, Karunakar
v. 133 Jul 23, 2024 11:47 KUTANI-ext, Karunakar
v. 132 Jul 23, 2024 11:45 KUTANI-ext, Karunakar
v. 131 Jul 22, 2024 09:58 KUTANI-ext, Karunakar
v. 130 Jul 22, 2024 09:48 KUTANI-ext, Karunakar
v. 129 Jul 22, 2024 09:47 KUTANI-ext, Karunakar
v. 128 Jul 22, 2024 09:45 KUTANI-ext, Karunakar
v. 127 Jul 20, 2024 04:32 KUTANI-ext, Karunakar
v. 126 Jul 20, 2024 04:30 KUTANI-ext, Karunakar
v. 125 Jul 20, 2024 04:24 KUTANI-ext, Karunakar
v. 124 Jul 20, 2024 04:06 KUTANI-ext, Karunakar
v. 123 Jul 20, 2024 04:05 KUTANI-ext, Karunakar
v. 122 Jul 20, 2024 04:02 KUTANI-ext, Karunakar
v. 121 Jul 20, 2024 04:00 KUTANI-ext, Karunakar
v. 120 Jul 20, 2024 03:58 KUTANI-ext, Karunakar
v. 119 Jul 20, 2024 03:53 KUTANI-ext, Karunakar
v. 118 Jul 19, 2024 17:43 GONZALVEZ-ext, Antonio
v. 117 Jul 19, 2024 17:35 GONZALVEZ-ext, Antonio
v. 116 Jul 19, 2024 13:23 KUTANI-ext, Karunakar
v. 115 Jul 19, 2024 13:17 KUTANI-ext, Karunakar
v. 114 Jul 19, 2024 11:43 KUTANI-ext, Karunakar
v. 113 Jul 19, 2024 11:32 KUTANI-ext, Karunakar
v. 112 Jul 19, 2024 11:12 KUTANI-ext, Karunakar
v. 111 Jul 19, 2024 11:06 KUTANI-ext, Karunakar
v. 110 Jul 19, 2024 10:37 KUTANI-ext, Karunakar
v. 109 Jul 19, 2024 10:32 KUTANI-ext, Karunakar
v. 108 Jul 19, 2024 09:57 KUTANI-ext, Karunakar
v. 107 Jul 19, 2024 09:45 KUTANI-ext, Karunakar
v. 106 Jul 19, 2024 09:43 KUTANI-ext, Karunakar
v. 105 Jul 19, 2024 09:31 KUTANI-ext, Karunakar
v. 104 Jul 19, 2024 09:20 KUTANI-ext, Karunakar
v. 103 Jul 19, 2024 09:11 KUTANI-ext, Karunakar
v. 102 Jul 19, 2024 09:08 KUTANI-ext, Karunakar
v. 101 Jul 19, 2024 08:58 KUTANI-ext, Karunakar
v. 100 Jul 19, 2024 08:55 KUTANI-ext, Karunakar
v. 99 Jul 19, 2024 08:52 KUTANI-ext, Karunakar
v. 98 Jul 19, 2024 08:49 KUTANI-ext, Karunakar
v. 97 Jul 19, 2024 08:38 KUTANI-ext, Karunakar
v. 96 Jul 19, 2024 08:21 KUTANI-ext, Karunakar
v. 95 Jul 18, 2024 10:10 KUTANI-ext, Karunakar
v. 94 Jul 18, 2024 10:02 KUTANI-ext, Karunakar
v. 93 Jul 18, 2024 09:59 KUTANI-ext, Karunakar
v. 92 Jul 18, 2024 09:07 KUTANI-ext, Karunakar
v. 91 Jul 18, 2024 08:53 KUTANI-ext, Karunakar
v. 90 Jul 18, 2024 08:38 KUTANI-ext, Karunakar
v. 89 Jul 18, 2024 08:30 KUTANI-ext, Karunakar
v. 88 Jul 18, 2024 08:25 KUTANI-ext, Karunakar
v. 87 Jul 18, 2024 07:52 KUTANI-ext, Karunakar
v. 86 Jul 18, 2024 07:45 KUTANI-ext, Karunakar
v. 85 Jul 18, 2024 07:42 KUTANI-ext, Karunakar
v. 84 Jul 18, 2024 07:23 KUTANI-ext, Karunakar
v. 83 Jul 17, 2024 17:00 KUTANI-ext, Karunakar
v. 82 Jul 17, 2024 16:40 KUTANI-ext, Karunakar
v. 81 Jul 17, 2024 16:36 KUTANI-ext, Karunakar
v. 80 Jul 17, 2024 16:36 HALL-ext, Simon
v. 79 Jul 17, 2024 13:18 KUTANI-ext, Karunakar
v. 78 Jul 17, 2024 12:02 KUTANI-ext, Karunakar
v. 77 Jul 17, 2024 10:25 KUTANI-ext, Karunakar
v. 76 Jul 17, 2024 10:20 KUTANI-ext, Karunakar
v. 75 Jul 17, 2024 10:13 KUTANI-ext, Karunakar
v. 74 Jul 17, 2024 08:01 KUTANI-ext, Karunakar
v. 73 Jul 17, 2024 08:00 KUTANI-ext, Karunakar
v. 72 Jul 17, 2024 07:30 KUTANI-ext, Karunakar
v. 71 Jul 17, 2024 07:24 KUTANI-ext, Karunakar
v. 70 Jul 17, 2024 07:07 KUTANI-ext, Karunakar
v. 69 Jul 17, 2024 07:03 KUTANI-ext, Karunakar
v. 68 Jul 17, 2024 07:02 KUTANI-ext, Karunakar
v. 67 Jul 17, 2024 05:19 KUTANI-ext, Karunakar
v. 66 Jul 17, 2024 05:06 KUTANI-ext, Karunakar
v. 65 Jul 17, 2024 05:04 KUTANI-ext, Karunakar
v. 64 Jul 17, 2024 05:03 KUTANI-ext, Karunakar
v. 63 Jul 17, 2024 04:51 KUTANI-ext, Karunakar
v. 62 Jul 17, 2024 04:04 KUTANI-ext, Karunakar
v. 61 Jul 16, 2024 18:33 KUTANI-ext, Karunakar
v. 60 Jul 16, 2024 13:33 KUTANI-ext, Karunakar
v. 59 Jul 16, 2024 13:32 KUTANI-ext, Karunakar
v. 58 Jul 16, 2024 13:27 KUTANI-ext, Karunakar
v. 57 Jul 16, 2024 08:05 KUTANI-ext, Karunakar
v. 56 Jul 15, 2024 11:22 KUTANI-ext, Karunakar
v. 55 Jul 15, 2024 11:22 KUTANI-ext, Karunakar
v. 54 Jul 15, 2024 11:09 KUTANI-ext, Karunakar
v. 53 Jul 15, 2024 10:49 GONZALVEZ-ext, Antonio
v. 52 Jul 15, 2024 10:42 GONZALVEZ-ext, Antonio
v. 51 Jul 15, 2024 10:33 KUTANI-ext, Karunakar
v. 50 Jul 15, 2024 08:53 KUTANI-ext, Karunakar
v. 49 Jul 15, 2024 08:37 KUTANI-ext, Karunakar
v. 48 Jul 15, 2024 07:52 KUTANI-ext, Karunakar
v. 47 Jul 15, 2024 07:51 KUTANI-ext, Karunakar
v. 46 Jul 15, 2024 07:40 KUTANI-ext, Karunakar
v. 45 Jul 14, 2024 17:04 KUTANI-ext, Karunakar
v. 44 Jul 14, 2024 04:29 KUTANI-ext, Karunakar
v. 43 Jul 14, 2024 04:25 KUTANI-ext, Karunakar
v. 42 Jul 14, 2024 04:25 KUTANI-ext, Karunakar
v. 41 Jul 13, 2024 16:48 KUTANI-ext, Karunakar
v. 40 Jul 13, 2024 06:40 KUTANI-ext, Karunakar
v. 39 Jul 13, 2024 05:17 KUTANI-ext, Karunakar
v. 38 Jul 12, 2024 13:04 KUTANI-ext, Karunakar
v. 37 Jul 12, 2024 13:01 KUTANI-ext, Karunakar
v. 36 Jul 12, 2024 12:50 KUTANI-ext, Karunakar
v. 35 Jul 11, 2024 16:51 KUTANI-ext, Karunakar
v. 34 Jul 11, 2024 16:47 KUTANI-ext, Karunakar
v. 33 Jul 11, 2024 16:46 KUTANI-ext, Karunakar
v. 32 Jul 11, 2024 16:45 KUTANI-ext, Karunakar
v. 31 Jul 11, 2024 16:34 KUTANI-ext, Karunakar
v. 30 Jul 11, 2024 12:12 KUTANI-ext, Karunakar
v. 29 Jul 11, 2024 12:09 KUTANI-ext, Karunakar
v. 28 Jul 10, 2024 12:00 KUTANI-ext, Karunakar
v. 27 Jul 10, 2024 12:00 KUTANI-ext, Karunakar
v. 26 Jul 08, 2024 11:30 KUTANI-ext, Karunakar
v. 25 Jul 08, 2024 10:44 KUTANI-ext, Karunakar
v. 24 Jul 08, 2024 09:54 KUTANI-ext, Karunakar
v. 23 Jul 08, 2024 09:31 KUTANI-ext, Karunakar
v. 22 Jul 08, 2024 09:05 KUTANI-ext, Karunakar
v. 21 Jul 08, 2024 08:59 KUTANI-ext, Karunakar
v. 20 Jul 08, 2024 07:20 KUTANI-ext, Karunakar
v. 19 Jul 08, 2024 07:17 KUTANI-ext, Karunakar
v. 18 Jul 08, 2024 07:08 KUTANI-ext, Karunakar
v. 17 Jul 05, 2024 18:26 KUTANI-ext, Karunakar
v. 16 Jul 05, 2024 13:31 KUTANI-ext, Karunakar
v. 15 Jul 05, 2024 10:26 KUTANI-ext, Karunakar
v. 14 Jul 05, 2024 10:22 KUTANI-ext, Karunakar
v. 13 Jul 05, 2024 09:15 KUTANI-ext, Karunakar
v. 12 Jul 04, 2024 09:05 KUTANI-ext, Karunakar
v. 11 Jul 04, 2024 08:59 KUTANI-ext, Karunakar
v. 10 Jul 04, 2024 08:58 KUTANI-ext, Karunakar
v. 9 Jul 04, 2024 08:57 KUTANI-ext, Karunakar
v. 8 Jul 04, 2024 08:56 KUTANI-ext, Karunakar
v. 7 Jul 03, 2024 12:13 WENNINGER-ext, Sascha
v. 6 Jul 03, 2024 10:23 KUTANI-ext, Karunakar
v. 5 Jul 03, 2024 09:28 KUTANI-ext, Karunakar
v. 4 Jul 03, 2024 08:32 KUTANI-ext, Karunakar
v. 3 Jul 03, 2024 08:32 KUTANI-ext, Karunakar
v. 2 Jul 03, 2024 07:54 KUTANI-ext, Karunakar
v. 1 Jul 03, 2024 07:31 KUTANI-ext, Karunakar

Workflow history

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

  • No labels