on a strong and future proof data platform core Organizational Change › Cross-company collaborations, acquisitions, carve- outs and internal reorganizations ask your data platform to be scalable and open, while secure and governed. › Business is becoming more mature in the field of Data & AI, changing the role of the CDAO (department). Practice (at scale) vs. Theory › Excessive costs due to dedicated DEV-ACC-PROD environments. › Complex operations and loss of speed due to BDP chaining. › Large amount of Data Products due to ‘architectural quantum’ concept. Technology Advances › The offerings of companies like Microsoft, Databricks and Snowflake rapidly develop, driving constant changes in your data platform architecture. › Evolution of AI towards deep learning and generative/agentic AI brings new requirements. Landing Zones How do we rapidly ingest data from external or newly acquired companies/systems? AI How do we make sure AI developments within our company source data from our platform only? Governance How can we provide a smooth user experience while maintaining strict governance? Labs Where do we draw the line between an experiment and an actual analytics workload that requires more formal data productst? Data Streams How tot answer almost ‘operational’ data requests with sufficient speed? Be prepared to ‘kill your darlings’. The world of Data & AI is changing rapidly and requires us to adapt. LEARNINGS
Highly granular SDPs (e.g. 10 different order types) due to ‘architectural quantum’ concept. Multiple BDPs build on top of other BDPs creating deep dependency chains. Medallion architecture per data product causes an ‘overkill’ when logic is simple. Same SDP appearing multiple times in different BDP chains caused by ‘bolted on’ functionality in the chain. Practice (at scale) vs. Theory
DP00015 Installation Projects DP00186 Projects DP00035 Cost Centers DP00143 Company Balance Sheet Units DP00148 Project Specific Branches DP00144 Inventory Branches DP00149 Project Warehouses JDE F0005 JDE F0006 JDE F0010 DP00137 Financial Business Units FINANCE Practice (at scale) vs. Theory
BDP BDP SDP SDP SDP SDP Reduce complexity in the mesh, while keeping complexity in the nodes under control. Maximum depth of tree SDPs can only be succeeded by a maximum of two levels of BDPs. First BDP Layer Has tables and is a full fledged BDP with all logic and projections. Second BDP Layer BDPs on top the first layer of BDPs can only be a view on that data, no dedicated tables or data is stored. Practice (at scale) vs. Theory
Data Product Platform ML/AI Platform Operations Team Core D&A ML/AI CDAO Markets & Solutions Technology Sales Supply Life Cycle Services Finance Human Resources Information Proj. Execution S S L S S M L L M D&A ML/AI Organizational Change
Visualization Specialist Data Engineers (2) Data Scientist Domain Team (L) Product Manager Analytics (0.5) Business Domain Data Steward (0.5) Domain Team (S) Business Domain Owner Product Manager Analytics Business Domain Data Steward Analytics Engineer Domain Team (M) Business Domain Owner Business Domain Owner Analytics Applications Business Data Products Source Data Products Business Object Models Data Governance Franchise Team S M L Landing Zones / AT Layer Organizational Change
on a strong and future proof data platform core Organizational Change › Design your processes with scalability, security and governance in mind. › Accept your central organization changes over time. Encourage developers to move towards the business and replace them with profiles that fit the next phase of your maturing business. Practice (at scale) vs. Theory › Know when to hold on to theory and when to let go. › Not every standard or best practice, should be your standard or is the best practice in your environment. › Be very much open to changing the rules of the game halfway. Technology Advances Be prepared to ‘kill your darlings’. The world of Data & AI is changing rapidly and requires us to adapt. WRAP-UP › Choose one or multiple strong partners in the field of Data & AI and follow their roadmaps. › Prevent ‘shopping’ and the introduction of ‘niche’ vendors by offering a strong and broad toolbox. › Focus on integration with your data platform and existing governance structures. Sander Kerstens [email protected]