Mastering Data Security and Compliance: CoorsTek's Journey With Databricks Unity Catalog

Summary

• Compliance Through Governance: CoorsTek, a government contractor in technical ceramics, leveraged Unity Catalog's RBAC, lineage tracking, and auditing for regulatory compliance.
• Secure Data Handling: Role-based access control, comprehensive data lineage, and robust auditing enable organizations to manage sensitive data and meet stringent compliance standards.
• Operational Efficiency: Modern governance practices reduce manual oversight burden while strengthening security posture and enabling secure data innovation.

Mastering Data Security and Compliance: CoorsTek's Journey With Databricks Unity Catalog

Talk by Anupam Wahi, Chief Business Officer, Tredence ; David Tomlinson, Director of Data and Analytics, CoorsTek
Ensuring data security & meeting compliance requirements are critical priorities for businesses operating in regulated industries, where the stakes are high and the standards are stringent. We will showcase how CoorsTek, a global leader in technical ceramics MFG, partnered with Databricks to leverage the power of UC for addressing regulatory challenges while achieving significant operational efficiency gains. We'll dive into the migration journey, highlighting the adoption of key features such as RBAC, comprehensive data lineage tracking and robust auditing capabilities. Attendees will gain practical insights into the strategies and tools used to manage sensitive data, ensure compliance with industry standards and optimize cloud data architectures. Additionally, we’ll share real-world lessons learned, best practices for integrating compliance into a modern data ecosystem and actionable takeaways for leveraging Databricks as a catalyst for secure and compliant data innovation.
Here’s more to explore:
Unified and open governance for data and AI: https://www.databricks.com/product/unity-catalog
See all the product announcements from Data + AI Summit: https://www.databricks.com/events/dataaisummit-2025-announcements

FAQs

Why did CoorsTek choose Databricks for data security and compliance?

CoorsTek, as a government contractor working with sensitive data, required strong governance and compliance capabilities. Unity Catalog's comprehensive features—RBAC, data lineage tracking, and robust auditing—provided the security and compliance framework needed for regulated industry operations.

What specific compliance challenges did CoorsTek face?

As a technical ceramics company working with the Department of Defense, CoorsTek faced stringent compliance requirements around data handling and access. The company needed to ensure data security, maintain audit trails, and demonstrate compliance with government standards.

How do RBAC and data lineage support compliance?

Role-based access control (RBAC) ensures only authorized users access sensitive data, while comprehensive data lineage tracking shows exactly how data flows through systems. Together, these features enable organizations to meet audit requirements and demonstrate compliance with regulatory standards.

What benefits did CoorsTek gain beyond compliance?

Beyond compliance, CoorsTek achieved operational efficiency gains through automated governance processes and clear visibility into data assets. This enabled the company to innovate confidently while maintaining security, demonstrating that compliance and innovation can work together.

Full transcript

All right. Um, if you just join, grab a seat. Grab a seat. Uh, so thank you very much everyone for coming back after lunch and this talk will be about journey with data bricks unity catalog you know mastering data security and compliance. So I'll hand over to our speakers. We have and Anuam. Over to you. Thank you. Um good afternoon. This session is after lunch. So one of the jobs apart from course tech's journey with unity catalog is to keep it interesting.
Um my name's um Anupam Bahi. Um the chief business officer at Treadens. Um we would spend next 40 minutes or so talk about journey of um why they wanted to go the route of doing Unity catalog in the first place or what were the challenges we faced and what were the outcomes what were the visions what were the pivot points that we wanted to achieve with that obviously there are learnings along the way which we want to share and we also talk about a little bit of technology ology as to why we adopted one technology versus other.
So I'd let introduce himself and then we get right into the content. Towards the end we have some time reserved for Q&A so we would give you a chance to ask questions if any. Perfect. Thank you sir. Uh I am I am the real Tomlinson. We have the AI David Tomlinson up here. Uh my team hates this photo. it looks scary to them which admittedly uh most of the time I have a smile on my face. So uh unless you know my four or six-year-old is misbehaving.
So uh I'm the director of data and analytics at Kors Tech. Uh KStech is a 115year-old company headquartered out of Golden, Colorado. And no matter how many times I tell my family that I don't drive a forklift at the Kors Brewery, they still don't believe me. Um but that is okay. Uh we're a technical ceramics company. We've been around for a really long time. Uh and uh you know a challenge for us with data security is the fact that we actually work with the government and the department of defense.
Uh so there's some additional compliance things that we have to make sure that we're aware of and that we adhere to as we embark on our journey to the cloud. Um that may sound surprising but as a super old manufacturing company we don't have much of a cloud presence. At least we didn't when I came in a couple of years ago or a year ago to Kortech. So on this vision or on this journey, we really decided, hey, it's it's time for us to really make some hard decisions, set some good foundations, and continue to grow our framework of what we need to do uh to provide better analytics and better business value for our customers, our internal customers.
So when we started looking at uh where we were and what we were doing, we pretty much identified right away that we were interested in migrating to Unity catalog. We had the historical hive meta store in place and really we were using data bricks as only a transformation layer within our our data flow. So we had a more of an Azure native solution. We really decided to go with more of a centralized strategy on data bricks and make sure that we were getting all the functionality and all the benefit from the functionality that's out uh in data bricks today.
Uh, another part of this is we had actually created at one point in time at Kortech a physically isolated environment where some of our data existed in one area and was transformed in one specific way and our data then was in other non-regulated areas also managed. Well, this became a huge challenge for us because then you're doing everything at least twice, right? So we're trying to figure out okay is this information ITAR compliant cur compliant who can see it who couldn't and really had a very very physical isolation strategy for that because honestly there wasn't a better solution that existed out in Azure data factory and with Azure at that point in time.
So for us that was important to uh make sure that we were engaging with the community and really understanding what we could do to simplify our our strategy and our framework within Unity Catalog. Uh, additionally, there are some uh there are some things that business didn't have when we were looking at compliance. Uh, and that was the lack of visibility as it says above here. And okay, it's it's it's one thing to say here are the access groups and here are the people in those groups.
It's completely different to tell people this is how they're using it. Here's how they're accessing it. Here's how they're trying to query that information and return results. And that for us was was a really big win and something that we wanted to make sure that we did for our security and our compliance teams. So what we wanted to do is we wanted to look at okay how can we encrypt our data? How can we make sure that we can have masking functionality?
Uh we're a small company. We need to do a lot with a few people right so we didn't have a team of 10 even. Today I have a team underneath me of five. Uh so we have to make it make it work with a little amount of people and so anything we could do to simplify what we were doing and being able to uh help us come up with other options and what we were looking at and how we can support the environment we once again started leaning towards data bricks and unity catalog because for us uh that was the way that we were going to create some level of uh optionality as it says up here or really making sure that we were avoiding some of our Azure lock in right we were really looking at what we were doing with our Azure native solution and we said that is everything and anything in Microsoft shop and they have full control over what we were going to do and the direction we were going to go and that uh is something that can be a little scary if you're a small company and a small team because if they change strategy all of a sudden you're changing strategy and you're reworking things that you don't necessarily need to rework.
Um, additionally, when we were looking at our strategy, uh, before before I came into Krist, we really had a very specific we're going to land all of our data in a SQL managed instance and we were going to use data bricks to just do this light ETL work, but really our data warehouse was going to be just simply a SQL server in the cloud. And that really seemed like we were missing out on a huge opportunity, right? and we wanted to reset and we wanted to make sure hey if we're using Unity catalog and data bricks we want a SQL warehouse that we can rely upon we want to use the ML features with ML flow that are built in and we really want to lean into that Gen AI environment as well especially with AIBI and the Genie workspaces uh those were big for us and uh we really needed to lean that direction and kind of reset where we were going and so for us it was obvious that we needed to go through Unity catalog migration So many of you probably are familiar with this slide and hopefully many of you are familiar already with Unity catalog.
Uh if not then uh you had a bowl over your head or or you're an ostrich with your hole in the ground head in the ground. Um but this is really what you get with Unity Catalog at very basic level right and we were looking at okay we don't have a lot of extra people. So every single time we set up a workspace or every single time that we're trying to align and assign a compute uh there was significant work that had to be done.
And so we were like well that's not not going to scale at all with the amount of people that we have especially considering that with those five people we also have to support all of our legacy environment of SQL Server as well. So how do we go through and how do we really help eliminate some of the duplicity uh in the environment and really help us do something that is simple and easy to understand um and allows us to have a better control over things.
Uh for us we did go with a medallion structure obviously as well with this uh and we went with a human intelligible naming convention when we were doing that instead of bronze, silver and gold which a lot of our business users we knew weren't going to understand what does it mean to be bronze or silver. So we decided with naming conventions that matched their interpretation core this is the core raw data cleansed and analysis.
So that really helps them understand as they're exploring and trying to discover new assets using Unity catalog that they can actually see and understand what they're looking at. So these are some real life screen grabs of our environment uh and the lineage. Many of you may be familiar with this lineage uh these lineage views now. But what you can do is you can now understand and people can now visibly see visually see how the data is related to each other.
That was a huge point for us when we were talking with our security counterparts and with our our global trade team who helps us control our ITAR compliance. That was really important for them to go through and see where the data is going, understand the relationships between data and certify if someone's created an alternate view of something. Because of course, these lineage graphs aren't manually populated, right?
They're automatically populated based on how you're engaging with the platform. So you can go out there and you can see oh well you know in this case we can see uh M and M M Graph uh and I think uh name is probably in there somewhere just further back in the lineage. Um but it allows people to see how everything is connected and how it's being used and that was huge for us in terms of that compliance certification because now they can say who's accessing it, who's using it. the history list table on the far right hand side here.
Uh that also gives you a view of how people are using the data and what queries are running against it. Now you'll see most of these are merge statements and some uh basic data engineering tasks were being done by my team as we're building out and developing this platform. But it shows you any user interaction or query. And that would even include if you had a direct connection to something like PowerBI and people are running reports, it will actually show here as well that they're out there and they're viewing the reports that are querying against the data.
So these were important views for us to understand uh how it was being used, what it was being used for and uh making sure that we can certify that the correct people have the right access to data which of course is is the main reason that we have all the compliance controls we have today. Uh so here we have some really high level examples of some of the things that you can also do with Unity catalog especially when we're talking about masking and offuscation scrambling.
These are different uh types of engagements and different types of masking algorithms if you will uh that you can use. And there's even more of this functionality that's available out there today in Unity catalog with uh with functions and being able to align those functions even with specific tags so that you can make sure as your data comes in that uh it's it's viewable by the right people. And so for our HR teams who are putting PII information out there, uh that's important for them to understand.
How do I make sure how can you certify that people can't see the data that I'm that we're producing or can only see to a certain level of the data. Thank you. Um so at this point right we come in and um we kind of try and figure out some of the challenges that outlined. Um we wanted to bring in technology to do this job as much as possible. We had a lean team like mentioned. Um we also saw that you know uh across the um industries where we've seen clients coming up now where we're talking about data sharing and we're talking about things going on cloud and especially the data bricks um being implemented at scale.
Um compliances and clients questions around how do we govern the data? How do we manage the data? How do we ensure that it is visible to the personas that are only supposed to see it and not others and so on and so forth. A lot of those questions are being answered by um the Unity catalog that we wanted to bring in and those were the technological reasons where we wanted to um provide that kind of benefit to. But the question was that we had to implement this in a in a in a in a way that we were not heavy with the team structure.
We had limited team structure and we also wanted to do it in the right way architecturally designed in a way that we leverage all capabilities functionalities. Um and usually every client situation has a different tech stack. So you need to align your migration strategies, your target architectures and so on and so forth with the tech stack that an individual enterprise um is running and and that's what happened right cooltech had a tech stack coolste had a strategy so like I always say right in these kind of um migrations and these kind of implementations um before we get into the job um the prep that goes in um to kind of pay attention to the nitty-g gritties of how architecturally we are going to implement is um which business groups we're going to effect.
Bring on the business users and bring them on and and kind of have them get a view of what will change for them and in regard to that what benefit they would achieve out of out of that right so that we have their back as we implement this. So a lot of stuff went around core logic was ability to give the um security compliance masking scrambling features which allows us to kind of manage the data from a compliance and governance standpoint.
Now when we come in at this point I also want to introduce a little bit of what credence does right credence has been a core integral part of data bricks journey of the last you know five six years particularly in the last five years we've been there uh partner of the year and so on and so forth consecutively for last five years the reason why we come in and you know alongside data bricks and do these kind of implementations is exactly where um our accelerators come in, right?
And what these accelerators are, these are functional blocks that we've built which kind of help us accelerate these implementations not by just putting more manpower and more capacity from a perspective of uh resources but we bring in these abilities which are predefined accelerators which have their UI and interfaces and so on and so forth and these accelerators are built on data bricks um natively and are designed in a way that you know it can work in any many different tech environments right so KTech has one environment and we decided to bring our accelerator in the mix which we call um Unity go um and once that accelerator comes in you will see that on the next slide we have a small demo architecturally it fits into the schema of how KTE had designed the thought process to do or implement Unity catalog so we brought that in and One of the things that Unity go does is you know a lot of migration that were designed to be done um we had those schemas we had those pre-built um you know schemas and migration capabilities that we need.
So we didn't have to go and do those migrations manually and you know we could bring in Unity Go to accelerate a lot of stuff that was that was needed to be done. I remember when we were putting in the Unity catalog, the Unity Go uh application, we actually had challenges that we had to work through together. Yep. Because when we built our Azure environment many moons ago, uh we actually put a lot of really strict network uh restrictions in place, right?
And so that actually ended up causing a lot of pain initially for our teams. Uh but it was awesome to work with you and your team and to overcome those challenges uh and to get the solution deployed so that we could use it for the migration. Y uh a lot of companies have really really big data bricks workspaces and I can see where this application would significantly accelerate absolutely how how that comes together and for us it was like okay there was that initial hurdle of our network restrictions and getting past that and getting things deployed in the environment.
Uh but once we did it was like snap snap snap. Okay, this is the new environment. We transitioned over to the new cataloges. Uh and it was it was incredible to work with the team to overcode those overcome those initial initial steps because it was uh a worry of ours as as Kortech has experienced multiple partners in multiple different areas in the cloud where we struggled and you guys came in and you were dedicated to helping us overcome those challenges and get the solution in place.
And not to forget that we were an organization where we wanted to do everything onsite. So we could not bring in a lot of resource efficiencies by taking them offshore. So we brought a lot of resources. But thanks to Unity Go, we did not need those many us resources in you know in that migration. So to the point right what does it look like? This is how it looks like. This is the demo screen. So the point that was talking about right the hurdles and challenges that we have.
See these are accelerators which are which are developed as generic accelerators to be deployed in any environment and that's what I was trying to say that different enterprises have different tech stack different regulations how you add these applications when we go into migration so there are teething issues that happen in the beginning but once we are in and these accelerators are there and we understand what is our target architecture which is from two picture and then just you know it's a click click click and like he said right um we're in there so the this is this is where treadance comes in and this is one of 170 accelerators that we have.
So I don't intend to present 170 accelerators but across the life cycle of data engineering data science and so on and so forth alongside data bricks we've built these accelerators uh for different situations different clients unity go happens to be one of them which was applied here going forward when we get into different challenges we can obviously bring in different set of accelerators and the beauty is that these accelerators can solve point problem which in this case was unity go but if it's a complex problem we could bring five different accelerators and connect them together to solve a larger problem as well.
Right? These are just pre-written codes that can be applied on any situation. Um yeah, and before we move on here, the other thing that uh was a challenge for us is we went through and we deployed this application, we got it running in our environment is that in my Azure environment, I can't allow anyone in that's not a US citizen or US persons. So there was a lot of we needed to click the buttons and so we were able to work with the sellable team with some of their folks but also we were able to do screen sharing sessions where they were able to walk us through okay how do what buttons do we need to click and with the one cloud engineer that we have at our company. uh he was able to sit down and work with the team to get this application deployed um and we were able to use it.
But that was another one of the challenges that we had to overcome with my security y model was you just can't you can't send a bunch of people on site or they can't have access to be able to provide additional access. So that's something that we had to also contend with as we were going on this journey. It is a regulated environment with a skinny team. So we had to do what we had to do. But I think uh the point that is making is that it's time where technology is coming in doing things more for us and we need we have teething problems adopting any new technology.
We have our own jitters but once we overcome that I think technology plays and really helps us drive things and accelerate things faster for us. So um finally what outcomes and so on and so forth. Um so we obviously reduced right the the time it takes to uh create the bronze silver in the new nomenclature that you guys decided. Um and this was also about governance remember we spoke about that and once this came in we could reduce the violations by 90%.
Um which is the beauty of how technology came together in the architecture in the manner that we wanted it to come. Um, yeah, and that 90% really comes from us being able to certify very easily and quickly what different workspaces are binded to what cataloges and how do we make sure that the different access models that we have are being applied to the data sets correctly. Historically, we would have to go in to our analysis services model and we would have to do a browse as a person and then we would have to certify what entities or what assets they have access to.
Uh, and that's a very laborious process. But with Unity catalog is it's quick and easy to see uh what workspaces are bound to what uh what what cataloges and making sure uh that people are using it and being able to see what they're supposed to see. Absolutely. And architecturally also right one of the things was that can we drive um or simplify the architecture so they were redundant task that we could get rid of. So 20% kind of saving from those redundant task getting optimized.
Um but from a governance and transparency standpoint would you want to comment more um how organizationally this helped you guys from your management perspective what they wanted to achieve and where did we end up eventually? Yeah absolutely so I mean once again as I said we were on this cloud journey and really we had faltered over this cloud journey and for many years and we had actually reset our our architecture in Azure three separate times over five years.
Uh so when we came in and we said hey we need to go for a more centralized strategy and reduce the complexity in platforms we identified things that were easy to use easy for people to understand and easy to certify uh when it came to our compliances. So when we sat down with our security team, we started talking them through, okay, this is what we're looking at. This is what we're going to do, this is what we want to see, you know, what gaps do you guys have?
They took it away for a couple weeks. Uh, and we were surprised. They came back and they were like, no, this all looks good. Uh, and they gave us the thumbs up and we were able to be uh, CUI and ITAR authorized with our global trade team. Uh, which was once again one of our one of the huge steps forward. Um, but for them, as we continue to move our our environment into user access reviews and other things, they're looking at what we're doing and saying, how can we apply that more consistently across the board?
So, as we look at our SAP environments or if we look at uh our iPass solutions and what data is going between applications, they're thinking about it in the similar way. How can we leverage, you know, the foundations that we've built here so that there's transparency and there's consistency. uh and that was one of the big things that they were expecting from us. Great. Oh, one last thing on that uh on that slide is uh when we look at uh our time to market was uh very lengthy.
We were looking at a metadata driven Azure data factory pipeline framework which is is word salad but hopefully someone in here understands what I'm saying. Uh it was it's very complex and it took a long time to onboard new connections. So, we were working with a partner that was recommending a solution that really didn't have a lot of flexibility and it took forever for us to get new data in. So, it was like, okay, well, okay, we want to turn data around in in a week.
And they're like, ah, week. That's kind of a it's kind of a short time frame. That's going to it's more like a month, right? We're like a month to bring in new data. Like, that is crazy. And that was for new connections, not necessarily new tables, right? But as we continued to expand what we wanted to do in the cloud, winning a month for a new data source coming in uh was not going to help us provide the business value that we needed to.
So having Unity catalog and their federated data connections really helped us accelerate that time for exploratory data analysis and also looking at and bringing data into the environment so that people can see it and they can use it. Uh and that was one of the huge things that we got out of this as well is uh you know I challenged my team to say what if we only had 48 hours to turn new data around in data bricks. Yep.
And we can do that now. We can do that and at times it's even faster than that as the team has developed some uh some IA controls of workspaces and creating new workspaces. They've also uh kind of figured out the easiest path to create new UC federated connections and being able to do that bring that data in quickly and easily uh for people to access. So that was another huge benefit of it as well data onboarding um and also becoming near real time.
I wouldn't say real time yet but the ability to give that data back to the users and onboard the data that was another functionality. So accelerating the implementation was one but one of the big benefits we draw out of this new architecture was ability to get near real value. Yeah, I agree. I agree. Yeah. And then we also were using Fiverr as well to do a small pitch for them. Uh we use Fiverr because of the drag and drop and simplicity of their environment.
Uh we go with their hybrid environment. So what we can have is we have more control over the data and how it moves and how people access it, how that platform uses it just to make sure that once again we're maintaining that compliance for the teams. They want to know what systems are touching the data. What is it doing? What level of data is it seeing? How does it you know interpret a change data capture product? And so when we looked at uh resetting and reusing in the environment, it was you know fiverr is easy and data bricks was was easy.
Unity catalog is is is a great product. Once you once you make the migration and you're using it every day, you really do have a lot of functionality and features that come along with absolutely with the migration with the platform. Absolutely. So, so here things to remember when we're looking at an initiative like this is is for me our company really had lost focus of working on technology for technology sake and not looking at how we're trying to solve a business problem with the technology that we have or the technology that we're trying to evolve to.
So our recommendation is to always talk about and think about uh what what value are you delivering for the company and how does that help them make better decisions and how does that help you set foundations so that you can continue uh on the data bricks journey or on your cloud journey. Uh so start with high risk or high value data sets is is the important message there. If there's something really risky get that moved over sooner rather than later. focus on what the business needs from you as opposed to how you're going to use your technology or playing around with the newest things.
It's it's good to experiment and sandbox, but you also need to stay focused on the fact that uh we're here usually, at least in in my case, I work in the IT department. Uh we're not adding value, if you will, like through the manufacturing process. So, how do we really help accelerate their efficiency and their focus on what they need to do from a business unit perspective? Um, and also don't wait for it to be perfect, right?
Perfect is the enemy of great. You need to make sure that we're not spending too much time on, okay, what every single role can we have? Whatever what kind of attribute control can we put in place? You need to start small. You need to build something that people can understand and that you can articulate and then and then continue to iterate through that and continue to build upon the momentum that you gain. You got to get that ball rolling down the hill though to start with. can't uh you can't wait too long to say well it's coming that was another historical challenge we had at Kortech is we were building this very monolithic thing and it was well it's coming it's coming it's coming well it was 3 years and they the business user had never seen anything right from that platform so uh we decided to say okay how do we uh evangelize the hub and spoke model yep especially with that ability to bind cataloges and to share cataloges across workspaces uh that's going to be a great way for people to start getting involved and contributing to the overall vision.
So, uh also the sense of FOMO is real. People will very much get in contact with you and work with you if they hear someone else is getting to do it, right? So, the fear of missing out is real. We leverage that on a on a regular basis and not in a manipulative way uh but in in a psychological way that we're saying hey people who are engaged or excited they are going to be involved in doing more in the platform. Um and if if you don't have a technical skill set then we need to talk about what kind of upskilling do you need to do and want to do.
Uh and we need to empower those different users as well so that they can go through and they can understand what their role is with the environments. Absolutely. Absolutely. So as I said right planning was essential uh for the success of the program and some of the things that uh we took care when we were doing the planning from this initiative and once they completed the program right some of the practical advises and the lessons that we learned you know along the journey would like to highlight some of those right so medallion architecture obviously um like said right u make it human intelligence right and that's where working closely with the business user groups the governance teams the security teams and figuring out that the architecture is fine but what is it going to change for the user.
How's this architecture going to bring new challenges um in adoption of the new um ways and methods and how would the process change like I said we can't change the manufacturing process but we can help them accelerate some of those stuff so that's one second was unity catalog you know it's not a compliance tool right it's basically a pivot point from where you can do many different things once you have sorted out your architecture once you've built the data pipes and you know unity catalog has given you the ability to manage the data and govern the data with the security compliances that your management puts um as challenge to you.
You can do many different things. So it's kind of a um it's not an endgame for us. It was a game where uh it's an entry point to a new world. So it's a pivot point I would say. So many clients look at you know unity catalog and say hey that's my end goal. I think that's not it. It's just the beginning of your ability to do many different things for your organization with data because you get more control and governance on the data actually.
So that's what Unity catalog is all about. So it's basically a ability to scale right. Um and then the Unity catalog's foundation for I I think I covered most of the part. I think the tooling and um um the toolkits um Fiverr or Unity Go coming in and so on and so forth have lot of packed features. how you bring them together and what features you would want to leverage. Um um simply put for the end user and I think that's an art.
Um and that's the technology team that you know kind of looked at everything that they had in terms of features and capabilities that platform had what was needed for cool tech was adopted. So toolkits do help you but eventually it is how you um leverage those toolkits and features. Um so rather than trying to leverage everything you kind of figure out what capabilities are matching with your business needs and so on and so forth.
Um and finally use governance for unlocking the broader data access. I think we talked about a lot. Is there anything you would like to add here? Yeah, I think it's important also to really leverage your partnerships. That's something we didn't really talk about right uh too much is uh how do you leverage the people that are around you? I have uh I have my account executive that's in here in the room with us and I have uh the director of our SSA team.
Uh and it's it's great to have them here for the solutions architect and the sales enablement part of it to really lean into that and say okay data bricks how can you guys help us scale how can you guys help us do more and challenge them right the company if you guys didn't know this right it's based on your success their success is our success so the more that you can work with them to say hey these are the challenges I need to overcome to drive usage right they're going to be engaged more because they want to admittedly they want to get paid the company wants to make revenue venue, right?
So, how do we leverage that part of the partnership to say, you know, these are the things we want to do. It drives usage. It's good for you guys. It's mutually beneficial for us to focus on that. That is an important part of it. And then, of course, looking at the different partnerships that you can form like ours uh to help us make those migrations and help us get to where we need to go. Uh those are important. So, find find a partner or a set of partners uh that you're working with that can really help drive the value.
That is certainly part of the journey. uh and you should challenge yourself to understand who's out there in the marketplace and what they can do for you because there's lots of lots of good partners that have lots of good tools like we were talking about with Unity Go and with Treatence. So, um that was uh that's another important part of the journey is is leveraging the partnerships that are out there and making sure you're clear on your goals and what you're trying to do.
Absolutely. And last thing on this slide before we move to Q&A is um look I mean like I said right world is changing pretty fast. Um technology is coming in and giving us the ability to do things faster. Um each day I see right there is new technology evolution that is happening. So technology will be there. Technology will evolve fast. The question is how do we tap into the technology and we kind of build um or leverage the technology to do things for us now compared to just kind of putting more and more resources at it right that's where credence comes in and we kind of partner with clients uh and thankfully with he gave us the opportunity to do that and we did we did what we did I think it was a program that was um that had a timeline and that had limitations of resources it had limitations of um what we could do what kind of people could come in and so on and so forth.
What is the location of those people who touch anything that is production? So we had those complexities but as I said right because we were leveraging more technology less people we were able to kind of do things faster and aligned with what was needed to be done. So thank you for partnering with us on this one but questions um happy to take questions and if there are any

Learn more about the Databricks Data and AI platform.