SAP Datasphere: Filling the data holes on SAP S/4 HANA Transformation journey by connecting 10 data pillars

[STALANKI]

Background

 

While there is a lot of buzz in SAP world about SAP Datasphere, some of the customers are concerned about their past and future investments in SAP Data Warehouse and SAP Data Intelligence Cloud. According to SAP Datasphere FAQ, SAP Data Intelligence is going to stay until SAP Datasphere is enriched with all features of DATA Intelligence Cloud or may continue as separate product for customers who want a dedicated infrastructure per customer.

Technology vendors and consulting companies claim that data is the renewable fuel and currency, but data has officially become the nightmare and chaos for many customers as data moved from pen drives to metaverse . The problem has quadrupled as software vendors are  releasing a plethora of hybrid structured and semi/unstructured data cloud tools for customers every quarter.

While some customers going on an SAP Cloud Global template roll outs are using S4 Transformation as an opportunity to embed overall enterprise data model initiatives into the business case, many of the customers are still not giving enough importance to data and defining a business outcome driven end to end data strategy across 10 data pillars. We have seen a lot of programmes going into deep red as organizations are not planning and allocating enough time for business to engage and support data activities . Additionally, a lot of SAP transformation programmes are delayed indefinitely as  the the roles and responsibilities between multiple business and data teams are not defined clearly and early.

 

 SAP Data Sphere – Connecting 10 data pillars

While SAP Data Sphere is more focused on sophisticated analytics currently, I think we can extend this product or provide plugins in future for end-to-end data life cycle orchestration.It currently provides plug ins to Collibra, Data Robot, Confluent, Data bricks etc for enabling prescriptive analytics powered by hyper automation but there is more work that we need to do in this space to orchestrate end to end data life cycle and enrich data journey for customers.  In the future, SAP Datasphere can probably bring both business and IT teams on same platform with predefined content to design and deploy end to end SAP Data Life Cycle Services to get data right during interim and target and after target states.

1. Data Discovery and cataloging


2. Data Security, Scrambling and Anonymisation


3. Data Archiving


4. Data Retention and Storage


5. Data Cleansing and Quality


6. Data Migration and Reconciliation


7. Data Governance and Compliance


8. Data Integration leveraging blockchain, graph etc


9. Data Federation, Streaming and Lake house structured and semi/un-structured Analytics


10. Intelligent Data Science Operations powered by ChatGPT

 

Embedding Business Data Fabric

 

Data Lead is often always held hostage and held under the gun point for not delivering within time scale and budget. We have seen a lot of programmes going into deep red as customers neither look at data from end-to-end lens nor there are many architects with broader data skills covering 10 data pillars. The different data teams work under silos without clearly defined roles and responsibilities deliverables and activities between Global and Local Business, SAP Functional, Legacy, Data teams. To add salt to the injury,vendors are releasing new products but not training enough people every quarter across data pillars.  I won’t be surprised if data architects who has broader skills across 10 data pillars across various sap and cloud products charge same salary as the prime minister of our country due to shortage of supply over demand in the future.

As SAP Datasphere matures, we hope that we will be able to embed SAP Datasphere business fabric on cloud transformation projects not just for analytics but also use it to bridge the 10 data pillars and build a data factory that brings end to end data life cycle together across geographies. The below approach and governance model below  provides a foundation view on how we need to bring the 10 data pillars and teams together to design and execute an end-to-end data strategy on S4 HANA journey. It will help customers to start looking at data holistically and creating collaboration and governance bridges between various data teams on projects like the SAP BW Data Bridge and Collibra in the SAP Datasphere.

3 Data Stories to build a business fabric of data

Lastly let’s gets 3 data stories that applies to all 10 data pillars in our hearts and minds to build right and true business fabric:

1. Data is not an IT story; it is a business story and is driven by business. Senior Business Executives should own and take accountability for data story and be executive sponsors for data initiatives and governance boards.


2. There is no perfect data model, plan and data design and data quality. We iterate the plan after every mock load to rank, measure and improve data by business impact and value. We profile and prioritize data cleansing by business impact and value.


3. Data dies and leads to chaos when different data teams work in silos without central orchestration and rhythm, we need to look and connect data from an end to end perspective across 10 data pillars and tie it to a business outcome.

What is your thinking this in space? I like to hear your thoughts on this!