Collibra Platform Reviews

We use the solution to organize data. The IT team has access to the data and knows where it is stored, but when it comes to legal compliances and various regulations, the business itself does not have control over where the data is stored and how it is stored. Typically, the business wants to have control over where the data is stored, the various data classifications, and data sensitivity. That is the main reason why we use Collibra Governance.

I appreciate the range of features it has. Based on the reviews of some of the other tools we use, we find that the other tools lack in certain areas. If I had to choose a comprehensive tool across all the fields of data governance, I would opt for Collibra Governance.

The most valuable feature is the Technical Lineage. The fact that you can trace the auditability of a particular field or attribute across various systems is very useful.

There are a few things that need improvement. From a usability perspective, customers usually find some areas of the solution a bit complex. It takes a long time for the customers to get used to the UI and the interface. Another thing that the customers complain about when they opt for Collibra is the pricing. There are fees for additional features which mess with the customers' overall budgets.

I've been using Collibra Governance for about two and a half years.

It is a very stable solution. I would give it a nine out of ten. It works very well compared to other solutions on the market.

The scalability of the solution is good. I give it an eight out of ten.

The response time of technical support is typically high.

Nowadays, most customers are looking into Microsoft Stack, so we use Microsoft Purview as well, although Calibra Governance is our preferred choice since it's much more stable than Purview.

Up until now, Collibra Governance has been the market leader and is always the first one to add new features. Purview tries to bring out a lot of features as fast as possible, but those features are not very stable and have a lot of bugs. Purview has the upper hand when it comes to the usability of the app system. It is easier for customers to understand the feature list while using Purview. For example, after using both solutions for a few weeks, they usually have a better grasp of Purview than Callibra Governance.

Since it is a SaaS platform in a way, the solution is deployed on Collibra cloud. The deployment is pretty straightforward since Collibra deploys it on its own. It takes about a week to get the core of the system up and running. After, we configure it to fit the specific needs.

On a scale from one to ten, the simplicity of the setup would be an eight.

Collibra Governance's pricing is based on its features. You get what you pay for. There are other solutions that are cost-effective but lower quality. With Collibra, you get a fair-value product if you pay a bit more.

I would not recommend using the Big Bang approach with Collibra Governance. You should understand the bigger picture of what you want to do. Start off with a few systems and four small modules. Get feedback from the business and then continuously evolve it. It is better to have the implementation spread out over a one-year period than have it crammed down within three to six months while trying to implement everything at once.

I would say that Collibra Governance is suitable for small to medium businesses. 

Overall, I rate the solution a nine out of ten.

I primarily use Collibra Catalog for data management and governance. It lets you build data catalogs, making sure you've got the right definitions for business terms so that everyone's aligned. It also ensures that the correct roles and responsibilities are assigned and the correct data stewards are assigned to the correct data set.

Collibra Catalog's best feature is the data quality checker. It has a functionality that displays a tick when the data set is complete and the data is working and matching properly. This is a good way to validate if the data quality is sufficient.

Ai is a critical thing in today's world, so Collibra Catalog could improve its automation to increase the efficiency of the software.

I've been using Collibra Catalog for four to five months.

I would rate Collibra Catalog's stability eight out of ten.

I would rate Collibra Catalog's scalability eight out of ten.

I would rate the ease of the initial setup seven out of ten. Deployment takes two to three days.

Our ROI from Collibra Catalog is about 15%.

Collibra Catalog is fairly priced - I would rate their pricing seven out of ten.

I would recommend Collibra Catalog as one of the best solutions for data governance. I'd give Collibra Catalog a rating of eight out of ten.

We use this solution for workflows and for specific use cases. For our retail and insurance clients, we meet governance requirements by using all the features that Collibra provides. We do most of the work using workflows and connectors. We build connectors where the data will be extracted from a third party tool and  input in Collibra.

We have 40 to 50 team members using this solution. We have three admins who manage this solution. 

Workflow is very helpful and assessment are good features. I really like the structure of this solution and how it is compartmentalized.

There are certain processes that involve a lot of manual work, specifically when searching for attribute assignments. It would be better if we could do this via APIs. 

In a future release, we would like to have rules. We would like to have Regex Expression that scans data and to monitor quality. 

I have been using this solution for four and a half years. 

This is a stable solution. 

This is a scalable solution. 

We do get most of our support questions answered precisely, but not all of them. We have needed to do some online learning. 

We have previously used Informatica and Alation. 

Collibra has a better workflow while Informatica does not offer automation. We rely on the automation that Collibra offers.

In terms of governance, I prefer Informatica because it offers different tools and data. 

The initial setup is straightforward. 

I would advise others to have a meta model before they get into Collibra so that they can use the features that Collibra provides. They should have a proper architecture design ready before starting implementation. 

I would rate this solution an eight out of ten. 

I have been working on Collibra for a data governance assignment. Along with that, we also use Ataccama for data quality purposes. It is a Collibra/Ataccama mixture that we use.

We would like to have out-of-the-box automation. We have leveraged some of the out-of-the-box workflows. Collibra does have the workflows such as the creation of business assets. We designed tools to tag the sensitivity information in Collibra and embedded scripts into the workflow. We then deployed that workflow so the user can upload a sheet with metadata and the tags will get tagged across those columns.

Collibra's lineage is a very powerful feature. We have integrated Collibra with Azure and ADLS storage and we create lineage diagrams using the two tools.

This solution does not have an out-of-the-box connector for the cloud platform. If a client does not want their data sent out of their own server, it will be very difficult to ensure this. You can install Collibra Jobserver and DGC on your machine, but you cannot install a newer solution. This is a restriction for us. 

We have been using this solution for one and a half years.

This is a stable solution. If you have data sources for which Collibra can provide an out-of-the-box connector, then it is stable. You can schedule your job to pull metadata or data out of your source system, with Collibra as a connector. However, if you have something out-of-the-box which Collibra does not support as a connector, that is a challenge. 

If you have Teradata or Oracle as a system, you can build that lineage into thw Collibra platform but if you want to build something on Azure, there is no direct way to do this because they don't support that.

This is a scalable solution. 

Collibra are very supportive. If you need anything, they have a customer support portal where you can raise a ticket and they reply immediately. 

Positive

Collibra does have its own university so when we started this assignment, we went through the courses. After that, it was quite easy to complete the setup. 

This is a very good tool and they have upgraded many features including an ADF connector and ADLS connector. You can write your own connector and customize it in the workflow.

I would rate this solution a six out of ten.

Collibra Governance can be deployed on-premise and in the cloud. The solutions can be used for lineage data quality, business glossary, and data cataloging.

The most valuable features of Collibra Governance are that it is user-friendly and easy to use.

The price of Collibra Governance could improve.

I have been using Collibra Governance for more than two years.

We have approximately 30 business users. 

The technical support was good from Collibra Governance.

The intial setup for Collibra Governance is mostly straightforward except for the workflows. The workflows are not that straightforward. There is a learning curve.

The full implementation took approximately four months.

We have approximately four people for the deployment and maintenance of Collibra Governance.

There are different levels of licenses. For example, some users can only do read-only licenses, and others have the stewardship license where they can give access to users.

The license for Collibra Governance is expensive.

I would recommend this solution to others. However, I am trying out a new data governance tool very soon. Collibra has bought a new data quality solution, but it is not integrated yet. We are all waiting for the integration of the data quality solution. OwlDQ is the name of the solution they have bought.

All right, sir.

I rate Collibra Governance an eight out of ten.

We use Collibra for IT data governance, specifically for GDPR compliance. Our company is in the banking and financial institution sector and we are customers of Collibra. 

In general, this is a valuable solution for us. Collibra provides a good view of where my data is, the type of data we have across the landscape, how it's getting utilized, the quality in terms of correct calibration, and whether the integrity is uniform across the landscape. Everything is in sync and Collibra is a central repository that provides a good snapshot of understanding along with holding the integrity, confidentiality, and security of our data. 

Data discovery would be the major area that requires improvement across the landscape and I'd also like to see data redundancies. Those are the two areas where improvements could be made. A lot of countries have laws that don't allow most of the data to flow into the cloud. That issue needs to be addressed when it comes to personal data protection laws. Collibra needs to take into consideration the local laws and the concerns of those countries.

 I've been using this solution for well over two years. 

The main technical support is from Collibra which has local partners. It's not a critical application that requires 24/7 support so they're available five days a week during work hours. 

In terms of the tool, the initial set up is not a problem, but there can be many legacy factors in any organization that can affect deployment.  Implementation needs to be understood so that the tool can be aligned to the IT setup of the organization. In that sense, implementation is always a challenge. 

We deployed in-house in consultation with Collibra, and implementation took about eight months. We have about 80 users throughout our organization including CTOs, CIO,s and the board which have become more sensitive to data protection over the years. 

There are other companies with solutions in this field; IBM, Informatica and they provide a lot of competition. I believe Collibra has a good standard and is an early bird in this area, I believe they'll keep that lead as they move forward in line with this constantly evolving field. 

It's important to have a clear understanding of your IT landscape and its features and whether they really match up with the roadmap of governance in terms of compliance. Those issues need to be assessed before choosing a solution. 

This is a cost-effective product and to my mind has all the ingredients to satisfy compliance requirements as well as ease of implementation. I recommend this solution and rate it eight out of 10. 

We use it for compliance and data quality.

It shows how the data was transformed on the way and how the solutions were derived. This is the essence of the tool and why it is so powerful.

Any stakeholder in the company can see a very detailed visualization of the path of the data from the row to the report or the dataset to which machine learning was applied, for example.

Better integration with quality would be good.

Before you can use this solution, you have to make a lot of changes to how you measure your information in your organization, the data governance and policies, and the organizational structures that use them. Many companies believe that if they purchase the licenses for the tool that they have done the job, but this is far from the case with this tool.

It would be great to enhance the recovery feature with some AI. Adding automatic data discovery and classification based on AI algorithms would be good because it is really complex. You need a lot of storage, and it would be helpful if the burden could be diminished by summation.

It is stable, and I've never had any issues with it.

We had no problem at all with tens of thousands of concurrent users.

It's expensive, especially for small companies.

This solution is too expensive for a small company, and it also really needs quite a complex organizational structure. However, for medium top layer and large enterprises, it would be a good fit.

On a scale from one to ten, I would rate this solution at eight.

We use the solution mostly for a client. There are a port catalog and dashboard cataloging features that they use. That said, the principal use case, even though there are a number of use cases, is using it as a business glossary for terms throughout the institution.

We're saving a ton of time. There are complex terms like year to date, et cetera, and defining what university means or what college means, and the validations between certain aspects of the organization allow us to have a single source of truth for agreements on that information pulling from whatever status system. It's basically eliminating any data systems that might have been used previously and eliminating any last-minute scramble or days of back and forth questioning from stakeholders to other analysts, trying to figure out what the single source of truth is. This product creates a central repository for terms in their metadata and provides a platform for further changes and approvals for that.

It's incredibly easy to use. As far as the user-friendly aspect is concerned, it's good. The search function within Collibra for desktop is pretty cool with many hotkeys, and especially for having to build a business glossary, if somebody's confused about a term, they can use the hotkey to pull it up on Collibra for desktop, wherever they are.

With the application installed, you don't necessarily have to go to Collibra to utilize it. 

I do like the workflow customization feature as we're able to customize workflows that give ownership to the stewardship organization rather than have to rely on out-of-the-box workflows. You make it an IT function. The IT department can set it up and then put it in the hand of the stewardship organization through customization and a feedback loop, with the stewards able to make it do what they need.

The tried and true features and functions are solid. These features develop in a very good direction as new releases come through.

The stability is good.

The scalability is there if a company would like to expand. 

There are still some new features being released and unveiled such as the certification workflows or questionnaires for dashboard certification, and stuff like that, that will improve a lot as releases go on. There are just minor things here and there that can change. 

Every time you change or publish a new questionnaire for certification, you have to basically go into the code and update the new version of the questionnaire. Just little things here and there like that will, as features improve, be improved as well. 

Much like other tools, some things can be a little bit immature sometimes.

I'm a little bit limited in some of the features that we have available. It can be a little bit clunky or require extra Windows that aren't necessarily needed. It can get a little bit over-complicated here. It would be nice to have some of the workflow functionalities a bit more usable. There could be more advanced customizations and more added features.

I've used the solution for about six months at this point. 

In general, the stability has been good. there have been no hiccups or issues of any kind. It seems to be reliable. 

The solution seems to be very scalable, from what I have witnessed so far. if a company needs to expand it, it can do so. 

It's my understanding that we have around 200 users on the solution right now. We have several admin users and 200 business users. I'm not sure of the exact size. It may even be more than that at this point. 

It's a solution we're actively using. I'd say we are using it a moderate amount. 

I haven't personally been in touch with technical support. I know my team has, however, I have not heard any feedback. I can't speak to how helpful or responsive they are. 

I wasn't a part of the initial setup process. I can't speak to how simple or complex the process was in terms of implementation.

As I was not a part of the implementation process, I'm not sure if an integrator or consultant was used to assist in the setup process. 

We're partners. 

We're using the most recent version of the solution at this time. What I've been doing is product management on developing features and workflows for the customers or for the stakeholders.

The insight I would have for others considering the solution would be that it's a blank canvas. What makes it effective is understanding the use cases very well with the customer and designing the product to appropriately fill that need. The better you can understand the use case, the better that you can design it in a user-friendly fashion and get feedback from the stakeholders and get by in and organizational and ownership of the data that are you using, the more success you're going to have.

I'd rate the solution at a nine out of ten. I'm satisfied with what we've done so far. And I'm looking forward to working with the solution in the future.

Previously, I was in high-tech, now I'm in healthcare. In both instances, we used this solution to increase data literacy and business literacy. In short, we were building out business glossaries, coming to an agreement on term definitions, understanding what reports mean, what the metrics and calculations mean — essentially getting it all documented in an enterprise-facing view. That was the bulk of the focus in my prior company — along with some reference data. At my current company, we are focused heavily on bringing in data dictionaries, including schema tables and columns, and understanding what data is in which database. We also look at what data is flowing from database to database and how it's used in Tableau reports or in a business or archive.

Currently, we're on-premises, but we're planning on moving to the cloud later this year.

Over the last 12 months, we've had 643 unique new users. Most of our users tend to be what I would call "data geeks". They are the ones that understand the value of and/or the aspect of leadership to catalog their metadata for their data dictionaries, etc. The business users have not had as much adoption at my current company because that's not the particular strategy at this time. At my prior company, that was the singular strategy — to increase business literacy.

In regard to my previous company, for eight years, our primary customers were business users, not technical users. They just wanted to come in and say, "What does it mean? Who do I talk to if I have questions? Where do I go for more information? How does this relate to that, and how do those things affect me in my business world?" That was a fantastic use case at my prior company. In my current company, we're utilizing the tool specifically to support our data management strategy. Our technology risk office is very much supporting us in the effort to do the cataloging of all of the metadata for all of the systems that we're utilizing, cross-functionally.

Maintenance must be defined. As with any software product that exists, there are regular maintenance upgrades that occur that the company pushes out. If you're on-prem, you can choose to do it sooner versus later. In the Cloud, they push it to you unless you state that you wish to wait. From a maintenance perspective, I have talked to other customers who are in a cloud environment. They say that the maintenance has basically dropped to nil. For on-prem customers, it does require a little more maintenance because obviously, you've got to make sure that the servers are up and running, etc. In my prior role at my previous company, I was responsible for the business IT side of it, which meant I kind of managed the platform. I just didn't manage the server.

I took care of the customers, etc. I'm not even a technical person at all, but still, it was not difficult for me. From a maintenance perspective, I don't feel that it is difficult.

If you have custom integrations that have been created, then it will require a little bit more maintenance because those integrations need to be monitored. Some customers require a lot of integration, and some customers don't. It really depends upon the use case. Custom integration is really where it gets more challenging. Depending on whether it's a one-way integration or a two-way data feed, it can get pretty complex. Two-way data feeds are always custom. But that's something that will be on the customer anyway, not Collibra.

We've only just relaunched this solution within the last 15 months. Currently, we only have about 240,000 assets in the tool, but we have a roadmap and plan to onboard a number of our customers. We'll probably double or triple our users over the next 12 months. 

This solution has brought our very diverse cross-functional business teams to one enterprise-facing view, where they can see business glossaries that have been compiled by other teams. From here, they can leverage and understand what reports have been created. If the report exists already, why recreate it? 

Our data management strategy is to start cataloging our data dictionaries and our business glossaries to ensure that we have a common platform across the company. This is helpful when a database is being retired or being converted over to another one. A lot of work goes into documenting what that data attribute means, or what that field name means in regard to a particular report, or in a particular database.

I'm always putting in enhancement requests because we want everything to be perfect for us. We understand that there are thousands of companies that use the tool and many of them use it in different ways. They should allow the customer to have some additional flexibility.

Take Microsoft for example. Sometimes companies do something cool because their software programmer thinks it's cool, but for the user experience, it stinks. Something as simple as "Why did you decrease the font size from 12, down to nine on every page? Now eyes over 40, can't read it". As it relates to this specific software, I think that getting more feedback from users on changes to the software before implementing it would increased value for them. Overall, they're really great. We meet with our Collibra rep every other week. We talk about what's working, and what's not working. They're a fantastic company to collaborate with. Still, when they just go ahead and implement new things, a bunch of new tickets open, wanting it to go back to the way it used to be. 

As far as the functionality of the tool is concerned, it's pretty slick. It's very comprehensive. Still, sometimes they create an interface or an integration without thinking about how the business is going to use it. Virtually all software companies do this. Oracle does it, Informatica does it — every tool does it. They make changes and then they're like, "Oh, I didn't know you were going to use it like that". Why? nine-tenths of their customers use it like that. I think it's a common business challenge that any company has. They're just trying to appeal to a vast audience of customers.

They should consider that what makes a financial institution happy will not necessarily make a healthcare institution happy, which will not necessarily make a high-tech vertical happy either.

There's a lot of things available in their Data Intelligence Cloud that are not available on-premise. For me, if they could boost the search functionality so that if somebody types in a word, it automatically will pull up similar terms first — that would be nice. For business users, instead of what is just the most common volume of content in your tool, now they have a very cool faceted search. It would be very similar to Amazon. You can refine your search down to a fly's eyelash if you'd like. I see a lot of people in the community commenting that this would be a big help.

I have used this solution every day for the last eight years.

It's a pretty stable tool. In the last year, we've only had one time where there was a significant issue. We found out that it was simply because during an upgrade it required more server memory than the prior version did. Overall, that was a minor hiccup and it was quickly resolved.

Collibra has roughly half a dozen different products with which you can buy additional licenses for that will do amazing things. If you're interested in GDPR, you can buy that software — a module. If you're interested in what I would call a significant data lineage, you can buy that product, get a catalog, and it's available for data ingestions automatically. In today's world, this is pretty much essential. There's a lot of capabilities as far as scalability and expanding usage across the business.

It's easy to do that if the business users are being encouraged by their management to use it. I think you might agree that no matter what company you work for, nobody's going to use the tool unless their leadership tells them to — they're comfortable in their own box. It's like, "I'm busy. Don't bother me unless I have to do something." That's the case for what we have done both at the company I'm at now and my prior company. It's that leadership gained, cross-functionally that we have as one enterprise united under one tool. That's a pretty powerful thing to encourage people to do. The implementation of a tool like Collibra is far more effective if you have leadership executive sponsorship. I think that's hands-down, one of the most important things to ensure the healthy adoption of a solution.

Sure, you can use it without embracing it, but the teams that have embraced it are the ones that have leadership that says, "I understand the value of it, let's do this and get creative with it." These are the teams that are the most robust at using it; they have really learned how to use the tool and are constantly pushing the limits of it. From a scalability standpoint, the workloads come out of the box, but a lot of the workflows are made for the most common use case. As such, most customers customize the workflows. From that standpoint, it's very scalable.

I always recommend to anyone who is considering going with Collibra, to ensure that they have someone that will be trained on building the customized workflows — you're going to need them. Sure, you can pay Collibra to do that; you can pay the professional services to do that and they'll do a fantastic job, but it's expensive. It's a lot cheaper to invest in somebody in your own company to get some training. You can really scale quickly if you have somebody in-house that can create customized workflows and manage them.

The technical support is very good. 

As with any vendor, you can get out-of-the-box support, or you can buy additional support. Both at my prior company and at my current company, we have engaged with professional services and we meet with them once a month just to say, "Hey, I've got this weird thing I'm trying to do and I ran into this problem." Although it's not required, if you really want to accelerate the usage of the tool and the adoption of it, I always advise other people to talk with users at other companies and to consider paying for some coaching services or professional services. Even if it's just one call a month for an hour, it's still worth it, especially when you're trying to do very creative things, as most customers want. You gave me Mickey Mouse and I want to make it Donald Duck — a lot of companies do that.

The Collibra Professional Services guides are great — they're fantastic actually. I've never had a bad experience in the eight years I've been using this solution. I've never had a bad experience with their support staff, both on the technical side and on the business side.

The initial setup is not that difficult. I cannot speak to moving to the cloud because we have not done that yet, but I hear that it's not very difficult. It's been a couple of years since I have set up the platform, but as far as upgrading to a major new version, it's actually pretty straightforward. Collibra has actually done a fantastic job over the last few years to make this whole experience a lot easier. Years ago it was not as easy as it is now.

It's matured a tremendous amount over the last few years. absolutely tremendously. The company has been around for over 12 years now. When they first launched, it was a completely different animal. Now, it's a very robust metadata management and data governance tool.

One and a half, full-time employees are required for maintenance. 

I am not sure how long deployment took at our current company. I have heard from other customers who use the platform that it can take anywhere from one to three months, depending upon the complexity and how much testing they want to do. It also depends on the amount of customization they want to do. That's one of the great things about this tool — you can customize the heck out of it. If you go with everything out of the box, it's pretty straightforward and doesn't take very long. I would say deployment takes less than a month.

It's more of a soft benefit versus a hard benefit. What is the value of saving someone time? I did a cost analysis at my previous company. Our CFO used some vocabulary and some acronyms that I had never heard of — and I'd been with the company for 13 years. It took me 20 minutes — and I'm really good at sleuthing — to figure out what those things meant. I added those into our Collibra instance so that other users could quickly find out what those things meant. If you look at it from that standpoint, right after an "all-hands", our usage of our Collibra solution always spiked.

Everybody was like, "What did he mean when he said that? If it took me 20 minutes to find out what X, Y, Z meant, and it took me two minutes to get it into Collibra, then if a hundred people saved time because it took them only two minutes to find out, too — can you put a value on that? Yes. You can say, X dollars per hour, FTE, and how much time that saves. I did that very briefly just for one use case and my boss said, "Nevermind, they get it." 

I think that's the biggest value — how do you save employees time? Because everybody's too busy to waste time.

I think all software is expensive, but that's just me. Still, I would say it's probably in line with what other vendors charge for licensing. I would just say it's probably comparable. I have not done a side-by-side comparison in about three years, so I can't speak as to what's going on currently.

There's a baseline product called Data Governance Center. That is what I would consider their baseline product. You can choose to purchase other licenses, whether it's the data catalog, their privacy module for GDPR, or their Data Lineage modules — there are plenty of different licensing options. Some of them are user-based, and as with any company, the more you buy, the more of a discount you get.

You can buy as little or as much as you want. It just depends upon what your budget is. I've talked to some financial institutions that have just thrown so much money at the tool. It just makes my jaw drop to the floor — it's insane. We're doing almost what they're doing at a third of the cost. It really just depends upon your strategy.

The question is how do you help new users understand and leverage this solution to get people to come in, start using it, and understand what they're doing? Well, we've got three people that help onboard our business users.

Every use case is different because every business team wants to use the tool in a different way. It's all about business consultation, but Collibra doesn't have anything to do with that. I used to run a users meetup group for Collibra in the Bay Area. I've talked to many customers who have used Collibra, and all of them experience the same challenges — how do I get my business users? Even technical users that are on the business side want to know how to get them to onboard and adopt.

That's the piece that will really make or break in your implementation. So, make sure you have some type of stewardship team in place, whether it's on the business side or the technical side, just to help onboard new users. This is absolutely critical because as with any tool, it takes some adoption and some communication and collaboration.

When you first buy the software, you could just buy it and figure it out yourself, or you could buy their Coaching Services and their Quick Start packages. I would strongly recommend investing upfront. There is a Quick Start package, which is basically paying Collibra to help you, whether it's standing it up, whether it's your initial implementation, etc. I think it takes 10 days. I highly encourage taking this route. It will really accelerate your installation and decrease frustration. Make sure you've got leadership or executive support regarding what you're trying to do for your strategy.

The biggest lesson I've learned is that you can never assume what somebody means when they use a word. I've got 35 years of business experience under my belt. I've come to coin the phrase "What's your operational definition of that word?" You can be 45 minutes into a meeting with 10 people using the same word and find out halfway through the meeting that you're talking about four different things or two different things and everybody's frustrated and walks away.

You need to understand the meaning of the vocabulary, whether it's data vocabulary or business vocabulary. Doing so will absolutely accelerate your business and save people so much time. That's one of the things I really like about the Collibra platform. From talking to other companies, other people, and friends of mine, I know that other companies that use tools similar to Collibra — even they say the same thing. You need a data catalog, that will allow your business to quickly find what they're looking for and help you understand what that means in the context of the conversation they're having.

Overall, on a scale from one to ten, I would give Collibra Governance a rating of eight.

I'm not a part of the tech team. I'm definitely part of the master data management, wherein we are providing services with respect to master data. Our services are focused on just the business-specific areas such as pharma commercials and pharma supply chains, and we have also built the lineage in R&D areas.

In some specific use cases, we are mapping the processes, the respective sources and basically using the entire asset model of Collibra, starting from process, to attributes, to data modeling. We are tracking everything in Collibra.

Metadata management is one of the key aspects of the product we really appreciate. 

The lineage is one of the important features as well. We felt the asset model is very good. 

We have tried implementing some of the out-of-the-box workflows of Collibra however, we have also used some customized workflows. Customized workflows in terms of data stewardship, assigning basic roles and responsibilities, for issue management, et cetera. They are very useful in setting up the proper governance. Previously, our metadata and repositories were scattered. Since using Collibra, they're all coming into a centralized location. 

Overall, it is a good tool, due to the fact that, with other tools, in some or other way they are lacking certain capabilities.

There are extract, transform, and load tools wherein you can track the data lineage. You can track technical lineage, though not exactly proper lineage. That said, Collibra is a good tool to track, everything starting from process to the attribute table column level. 

It is user-friendly. I could easily go into the Collibra UI and explore the key features.

The solution has very good online assistance. Collibra University is definitely a great help. There are all of these free resources wherein wherever you are stuck, you can go and check and come back and fix items.

What we have done is, we have internally set up a self-service process. We could set up a self-service process within Collibra wherein business stakeholders can come and they can onboard themselves on Collibra. My team specifically is just educating them and helping them following the best practices of Collibra asset model and community. We are setting up their roles and responsibilities, community managers, the manager stewardship, et cetera. We can set everything up so that users can come and onboard themselves.

Right now, its maturity is at, I would say, a moderate level. The plan is to expand it to use it for full maturity. It cannot be directly integrated as a data quality tool, for example.

Collibra doesn't provide support for integration for SAP Info Steward directly with Collibra. Going forward, we are planning to use Collibra and trying to replace other, I would say, other peripheral tools in the architecture so that we can make it more automated and have proper governance control in that.

In general, the solution isn't quite in a nascent stage, where we are using the data quality rules, business rules, everything we are exploring how to implement and then further integrating it with other platforms and use cases with respect to business areas. 

I haven't used the solution for very long. I joined my organization almost eight to nine months ago, however, I've been using it for the past six or seven months. It's been under a year at this point. 

The solution is stable. We can definitely rely on it. If it's a storage solution, other maintenance, and other cost perspectives come into play. However, we are not using it that way. It does not have storage capability. We are exploring how to better complement that with a Data Modeler. That said, we have no issues with it crashing or freezing and there are no bugs or glitches.

I have not tried to expand the solution and therefore cannot speak to the scalability of the product.

The solution is extensively being used. It's likely that we might increase usage.

Right now it is limited to a few use cases, however, Collibra has been identified as a solution that should be used to scale up. It should basically be used under full maturity. We are trying to basically onboard many, many more businesses. 

For now, for example, we just have a pharma supply chain. However, we are in touch with the other stakeholders. We are trying to convince them by showing them the capability of Collibra, so that they can better manage their data.

The objective is to onboard people on Collibra and no other data governance tool. This is one tool which, will be a place of central governance. There have been some businesses that are using Ataccama or SAP MDM. However, Collibra is the one that is supposed to grow further. There is no plan to stop using it.

Our company is very much in touch with technical support. That said, I am part of the master data management team and therefore I do not contact them directly. However, the core tech team definitely is regularly in touch with the Collibra tech support team. 

I personally have just attended a couple of sessions with Collibra consultants, wherein they provided an overview of what they have done for GSK until now.

My entire team is new, so we had a couple of sessions with Collibra folks. They provided very good support and a very helpful overview.

I was not a part of the initial setup. I joined the company after it was implemented. I cannot speak to the implementation or deployment process. I have no insights into that aspect of the product.

Collibra initiated the implementation somewhere around July 2019.

While I do not have too much insight into the licensing aspect of the solution, I can say that we are not charged monthly. We might have to pay on a yearly basis.

I can't speak to the pricing. I'm unsure as to if it is expensive or reasonably priced. 

We are not a reseller. We are likely only a customer and end-user.

I'm not sure which version of the solution we're currently using. I don't know ht eversion number off-hand. 

I would recommend the solution to other organizations. There are not many competitors in the market for checking the data lineage and there are some data modeling tools. It's just that it's more about how an organization visualizes and how they want to track the lineage. Collibra is definitely a good tool from a governance perspective.

Right now, our plan is to basically use the Collibra lineage entirely, in data lakes, in metadata management, et cetera. Basically, we want to integrate everywhere so that nothing bypasses the governance.

On a scale from one to ten, I would rate the solution at a seven.