As a further measure, we examine user behavior, data usage, and data growth in your current SAP BW system using our patented analysis procedure. These parameters are essential for the design of an innovative yet lean and cost-effective analytics architecture, and they enable us to plan your migration reliably.
As a result of the workshop, you will receive an architectural recommendation for your future data warehouse. This not only takes into account the area of SAP data but also other data sources and systems. On the other hand, you will receive a well-thought-out roadmap for the migration to the target architecture.
The specific design of your future data warehouse architecture depends on your individual situation and the planned application scenarios. However, the following three architecture variants are conceivable:
Pure SAP Architecture:
With this architecture, you rely on SAP technology throughout, from the back end to the front end. This includes the BW/4HANA Business Intelligence Suite and the SAP Analytics Cloud. This architecture variant is particularly recommended if you mainly work with SAP data and if there is no long-term need to evaluate data from external systems.
SAP + third-party architecture:
With this hybrid architecture option, your business data is loaded into SAP BW/4HANA for evaluation. In addition, you operate a corporate data lake for aggregating and evaluating mass data from other data sources such as sensor data from production or social media data. This type of data usually does not follow the SAP data model, and its half-life is usually short. Therefore, storing and evaluating data in SAP is neither practical nor cost-effective. A cloud-based data lake offers you more flexibility and moderate costs. The link between your SAP systems and the data lake is the SNP solution GLUE™. This solution automatically transfers relevant SAP data to the data lake, which you can then use to develop innovative applications in the area of automation and AI/ML. Of course, the whole process also works the other way around and without cumbersome or insecure workarounds.
Depending on the individual starting position, it may also make sense to set up a completely independent data warehouse. Platforms such as Microsoft Azure or Snowflake are usually used as backend technology.
Selective migration with near zero downtime
Once your new architecture has been determined, we take over the data migration into your new data warehouse architecture for you. Our selective migration approach combines the advantages of the classic migration approaches greenfield or brownfield to a hybrid model. This means that you initiate a new start where it makes sense, cut off old habits which are no longer needed, and at the same time, retain the tried and tested habits.
"Completing work in the legacy system on Friday and starting seamlessly with the new data warehouse on Monday - our near zero downtime approach makes this possible without any problems."
COO at SNP
It is based on a patented analytical method called HeatMap. We measure the use of your data and can distinguish little used data from frequently used data. Older and no longer actively used data, such as customizing and master data, as well as historical data make up about 80% of the system volume and are migrated weeks before go-live.
Current data such as recently loaded data or new queries, as well as changes to already migrated data are only transferred during the actual go-live. Through a precise measurement of your system and massive parallelization, even the largest systems can be migrated comfortably within one weekend.