In this next episode of Tech-Driven Business, Mustansir Saifuddin continues the conversation with Hau Ngo of Summerlin Analytics to discuss how to approach data modeling and visualization when using SAP Analytics Cloud (SAC). Hau first joined us for a 6-part series in 2021 to talk about SAC and what it means to enterprises as they move to the cloud. Hau and Mustansir share real-life tips on how to approach this depending on your team and company. Listen in for quick takeaways that you can put in to place today. As the tech industry moves to simpler tools, data modeling plays an even more important role.Hau is an SAP Analytics Architect and an early adopter of SAP Analytics Cloud. In 2017, he helped a technology company in California consolidate global sales reporting across 7 different ERP systems. This effort culminated in one executive dashboard that displayed real-time information, eliminating weeks of manual coordination and data wrangling. Subsequently, Hau has presented his work at conferences such as SAPPHIRE 2019 in Orlando Florida, and has gone onward to help additional customers streamline their reporting processes and visualize the key company metrics. His experience with SAP Analytics Cloud extends to customers with various systems such as SAP Data Warehouse Cloud, BW/4HANA, and S/4HANA. Connect with Us:LinkedIn:Hau NgoMustansir SaifuddinInnovative Solution Partners Twitter: @MmsaifuddinYouTubeor learn more about our sponsor Innovative Solution Partners to schedule a free consultation.  Episode Transcript[Welcome to Tech-Driven Business. Brought to you by Innovative Solution Partners. In this episode, I welcome back Hau Ngo of Summerlin Analytics listen in as he talks about the importance of balancing data modeling with visualization to get the most out of your investment in SAP analytics Cloud or SAC.[Hello Hau, how are you?[I'm doing well, Mustansir, how are you?[Hey, doing great, man. Welcome to Tech-Driven Business. Again, today we will talk about the balancing act they call it, especially when you talk about SAC. And you have so many different variables in terms of the data modeling part, the data visualization, and what is the right balance. That's what I want to talk about today.[Oh, sure, yeah. I think it gets a little bit tricky, I think now with this newer tool because you can do so much with it. Before we used to just do everything in either ABAP or BW and you just have like a table dump either in Excel or an LB grid. But now with SAC, you can still do a little bit of data modeling. You can define calculations so the lines are blurred, like where do you do which things? Right? And I think in terms of what I would suggest for a good data model in this new paradigm, I would try to have all your work done on the back end, meaning you would have all your calculations done in either S/4 or BW or Data Warehouse Cloud, and treat SAC as a read-only layer. So SAC as a reporting layer, just read what you've written and leave that. Now of course there's some give and take, some things are easier in SAC, but I think for the most part, make sure everything is done on the source system and you should be off to a good start.[Interesting. So what seems like a good data model in your example that you just shared? It's almost like do more of the heavy lifting on the back end, which can be either S/4 or Data Warehouse Cloud or any other system for that matter, as long as you can connect to SAC and then use SAC as almost like your reporting layer. But create your stories, but avoid more detailed calculations and modeling in SAC. [Yeah, exactly. Because if you start reading into the technical documentation, SAC explains the technology in this way. Each widget, each table that you see