Discovery, Scope and Outcome
Birlasoft , SAP and O.C. Tanner participated in workshops to review their current environment, identify new technologies and build a roadmap for the project. The discovery process included the following tasks:
- Business Challenges & Opportunities Identification
- Develop the Value Hypothesis and Identify Risky Assumptions
- Validate the Hypothesis Seek to Eliminate Risk
- Review with Everyone
There was a lot to do, so O.C. Tanner decided to capture low hanging fruit and closely examine the risky assumptions. They wanted to know if Hybris, CPQ, and ERP; with varying configurations in production order management could really do what they needed it to do with their made-toorder products. If the proposed solution was successful they could replace their custom code and move their resources onto projects that differentiate O.C. Tanner in the marketplace. There was another risky assumption around whether the proposed pricing solution was as robust as they perceived their custom solution to be. The third risky assumption was could SAP work for them out-of-the-box. Over the years they had heavily customized SAP and wanted to see if they could avoid this in the future. The POC proved that they could accomplish 98% of their goals without customizations.
The company was gratified to find that most of what they wanted to was possible with pure configuration instead of customization. They considered this to be a huge boost in agility because configuration takes minutes, hours and sometimes days whereas customization takes weeks, months and in some cases, years.