Advising many of my clients, I have found that the majority of Information Technology Senior Executives that I had the privilege to advise them and work for them, in the difficult process of laying out, their SAP HANA Road Maps. The majority of the cases, we are struggling with the difficult decision making process to select what is the best tool between SAP HANA Enterprise and BW on HANA.
Confusion in the market is triggered by the internal pressure generated by their own Business organizations that fairly demand more robust, Business intelligence systems that can react and adapt faster and smarter to the dynamic markets and competition.
An important external factor that contribute to this confusion, is the fact that IT officers in the Industry, are the target of a ruthless Software market war, where the dispute by different vendors, to gain their technologies to be positioned as the dominant force in the markets, bring businesses in between this fight, making the decision process difficult.
There are only two Industries that refer to their “Customers” as “Users”, one is the Software Industry, and the other one, well I let you to think about that one, because it is not considered a legal Industry by any means.
In this article, we will concentrate in the selection between SAP HANA Enterprise and BW on HANA.
I will not discuss other technologies offered by other Software providers.
The selection between SAP HANA Enterprise Edition and BW on HANA, needs to follow a very serious and systematic analysis process. The process has seven (7) steps. We will discuss in this Blog three (3) out of the Seven (7) steps.
STEP 1 – Discover what are the different SAP HANA technology options to adopt into their current Functional and Technical Landscape.
List all your possible implementation options by:
1) Option Name
2) Option Description
The most common options available for the majority of clients are :
a) Migration of BW 7.0 to BW 7.3 on HANA
b) Implementation of HANA Enterprise Edition
c) Implementation of a HANA Hybrid Option. HANA EE + BW on HANA
STEP 2 – Define Key Business Value and Key Implementation Value measures for each HANA Option.
Key Business Value : You can define this Key Value indicators, by interviewing key business users, depending on the size of your company, the scope of your project and the time available, that define the extension of the analysis.
It is in practice, that you will define, who will get the attention, to discover the pain points in your business, to then find the value of the implementation.
As an example, you want to select from the Financial area the following key business users :
Financial areas : Chief Financial Officers, Corporate Controllers.
Example of Key business values are:
Foundational : Information to Manage the Business
Competitive : Information as a Strategic Asset
Differentiating : Information to enable Innovation
Breakaway : Information as a Strategic differentiators
Key Implementation Values :
Implementation values are defined by the Information areas, from the Functional and technical perspectives. You want to define how you will measure from the technical point of view a successful implementation.
Accelerated Development Cycles
Flexibility to model and flexibility to scale the system architecture
Complexities of Data Integration
Risk to Implement
Direction of the Install Base
Time lines, costs to implement
Step 3 : Assign values to each key performance indicator and weight each of your implementation options.
Move out of the emotions, and wonders of the technology, it is time to have a quantitative assessment of your future endeavor.
Those numbers will give you a very clear picture, of what are you and your Company are heading with the investment, will help you to have a more professional approach.
Produce a Pain / Gain Chart.
At this point, you can provide a clear picture, of where the HANA Road map will potentially look like.
It is recommended to have a review meeting with key business stakeholders, Key IT sponsors, to validate the findings, and get a group perspective of the findings.
In the next blog, I will guide you, through the following four (4) steps, to describe how to desing in a high level architecture, the proposed technology solution, and also how to define the goals, and objectives of the SAP HANA proof of concept.