Collibra Governance Primary Use Case

Chris Allen
Technical Product Lead at a insurance company with 5,001-10,000 employees
Our use cases include connecting a lot of legacy data systems to our logical components. For example, if somebody has a question that they post to us and say, "Tell me everywhere in our organization where we have a policy stored?" the primary use case is to logically define what a policy is, and then we use Collibra to tie that logical construct to a technical implementation. We may have six or eight, however many, different admin systems. We bring in the schemas of the way that those systems look, and then how a policy exists in this database and this table and this column, for example, in that legacy system. The second use case that we implement is the ability to track the provenance or the lineage as to how something changes over time. For example, if we bring data in from a legacy system and we use some tool set (e.g. Azure Data Factory) to extract the data into a Hadoop data lake, and then perform some transformations on it, we want to be able to track it; "It came from the source system here, and this field got changed to this name, and we applied this transformation on this field and it eventually shows up on this report here." We use it to track where a policy exists and also how it got there: it exists on this report and here's how it got on that report, here are all the steps that it took getting through to that particular report from the actual source system itself. Because quite often what we're finding is that our business users will get a report and they'll say, "I think your report's wrong. How did you get that value on that report?" That provenance or lineage is what helps answer those questions. We have data stewards who are the resources that if somebody proposes a new logical asset based on what they think the customer means, these data stewards are the ones that would get together and look at what's being proposed and make sure it works across all of our business units for a generic implementation, or create business unit specific terms if required. They're the ones that say a particular system or term or logical construct is ready for consumption by end users. Another group we have is the end users. We try to have people use Collibra by asking, "Don't tell me what system you want to get access to, tell me what you're looking for in business terms/constructs." In our example, it would be the question, "Tell me about all the policies in our system." They would go to Collibra and "shop" for that data and pick a policy and put it into the shopping cart basket that Collibra provides as part of their interface. Then they would submit that request for approval/access to the underlying data. We also have data stewards who approve the use of new/updated business terminology and end users who are looking for their data to make business decisions. We also have some power users who are the resources who are setting the direction for the application of where we want to go with it, (e.g. new workflows or new functionality within Collibra). For us, the Collibra application is an on-premise installation (although we use IaaS VMs to host it on cloud); it is not their SaaS implementation. View full review »
reviewer1471359
Group Manager at a tech services company with 10,001+ employees
We're a very large pharmaceutical organization so it's difficult to quantify exactly how many users are using Collibra. Within our organization, there is a data governance team that we had set up. I am the person in charge of that team. While working on the data governance processes, we thought of leveraging Collibra for things like data dictionaries, developing data lineage, ensuring that business artifacts like KPI catalogs and board catalogs can be built within Collibra itself. View full review »
SuChatla
Sr Manager - Enterprise Data Office at a healthcare company with 10,001+ employees
I've been working with multiple companies, but with two of the companies we have been using Collibra mostly for data governance. With these companies, our use case is all about metadata governance, lineage, and data-related policy management. We're doing policy management directly inside Collibra and we're also using it for issue management on the analytics side. If someone has a data concern, they just call me in and then put that concern into Collibra as a front-end UI for the data stewards and data scientists, and we start processing them. View full review »
Learn what your peers think about Collibra Governance. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
456,812 professionals have used our research since 2012.
Consultant0176
Consultant II at a tech services company with 51-200 employees
We have a client that was planning to do a digital transformation. They came up with the use cases and they have a couple of departments. They are mainly based on legal systems including corporate trust, etc., that they want the data to govern. Their requirement was basically if any new person is hired, they would have everything in Collibra, including all of the business glossary or the tables or the reports. Basically, everything for their onboarding process was available there. It was also necessary to give that to anyone that wanted to know about their department. View full review »
reviewer1469259
Technology Analyst at a tech services company with 10,001+ employees
I am using it essentially for the GDPR implementation over here in Europe. This is my second project on Collibra. Before that, I have worked on the CCPA part for a US-based project. I have worked on an on-prem solution and a solution on the cloud. I was the one who had created all the components on AWS because our client was not ready to move onto Collibra's cloud solution, but I believe they will be moving to SaaS soon. We are on version 5.7.5. Version 5.7 is the latest, but because we're not on SaaS, it's quite tedious to upgrade each and every environment. We have four environments or five if you include what the developers work on, so it is a bit tedious to upgrade. View full review »
Ankur Agrawal
Data Governance Manager at a tech services company with 10,001+ employees
We use it for metadata management, data lineage, and automated governance processes. I am working on the SaaS deployment, but I have also worked on the on-premise deployment. I am currently using its latest version. View full review »
Narsimha Reddy.Desidi
Solution Architect at a financial services firm with 10,001+ employees
My company, a financial institution, decided to implement data governance for data analytics, et cetera. We designed an entire metadata management system using Collibra. Initially, we designed the metadata management, and then we enabled the receivership at the organization-level and also roles and responsibilities. After that, we created the lineage between the technical and business assets, and we automated the process of insertions and updates. View full review »
reviewer1466991
Manager - Finance at a financial services firm with 10,001+ employees
I worked with this solution a few months ago and the main use case of Collibra was as the central metadata tool for the enterprise. The plan was to have all of our data dictionaries, our business glossary, to expose data lineage through Collibra and show all of the relationships and connections between our various tables and databases and the actual semantic business layer, in Collibra. It was a way to unify our technical metadata with our business metadata and with our actual applications. View full review »
Tom Kilburn
President at TCC
Our clients are typically using it for metadata management. From a broader perspective, Collibra establishes an excellent foundation on which to build an enterprise data governance program. View full review »
Ludmila Kullova
Data Governance Analyst
We are using the product mainly for metadata management as well as some data governance practices such as roles and responsibilities set up. We're also using different workflows - mainly approval workflows or request access workflows where people can actually request access to data. We have use cases based on different teams, based on what they need. It's mainly the glossaries, such as business glossaries, data dictionaries, and report catalogs. View full review »
Andrea Rimoldi
Data Governance Manager at a insurance company with 201-500 employees
The main use case for our organization was to collect and collate information for our business users, such as definitions, business rules, etc. The customers' names were stored in a data warehouse on Oracle, and with this product, you could insert information related to the customer. You could use Excel, for example, to add in data. You'd have all the information you collected from other places on one tool that users could navigate across to see all of the information. View full review »
reviewer1475934
Consultant at a tech services company with 10,001+ employees
I don't use it as an individual. It's basically for my clients. I serve as a consultant for the tool. The typical use cases for the clients that we get is around metadata management and around building lineage. You can create a lineage by modifying out-of-the-box Collibra asset models. View full review »
Guillermo Angulo
Data Analyst at a tech vendor with 10,001+ employees
Our primary use case of this product is for metadata information for our technology assets. We also use it for all the governance dictionaries, and for minutes as well. View full review »
Learn what your peers think about Collibra Governance. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
456,812 professionals have used our research since 2012.