Collibra Governance Reviews

The primary use case for the solution is the governance of data dictionaries. It is useful for managing and classifying data on a large scale.

The product has significantly improved data governance by providing a centralized platform for managing data assets and ensuring consistent definitions. It has led to better data quality and more efficient compliance with regulatory requirements.

The product's most valuable features are cataloging and classification. 

They could simplify the platform's setup and design process. It requires significant IT involvement and expertise, which can be a barrier for smaller organizations.

We have been using Collibra Governance for approximately five years.

The product is stable and reliable. I rate the stability an eight.

The product is scalable, but the extent to which it scales effectively depends on how well it is designed and implemented. 

I rate the scalability an eight. 

The product's pricing is high, which its comprehensive features and capabilities may justify. However, the cost can be a consideration for smaller organizations or those with limited budgets.

As a data governance advisor, I evaluate various solutions based on their fit for the client's requirements. While I recommend this solution when it meets the organization's needs, there are more than one-size-fits-all solutions.

Integration with it can vary based on the client's IT landscape. For some organizations, integration is straightforward, while for others, it can be quite complex.

Its user interface is generally user-friendly, but it could benefit from some enhancements to improve ease of navigation and customization. While functional, a more intuitive design could help users operate the platform more efficiently.

Its performance can vary depending on how well it is configured and the scale at which it is deployed.

It has strong data privacy and security features, including robust encryption and access controls. It is designed to comply with various data protection regulations, crucial for maintaining data security.

It offers extensive customization, allowing tailored configurations to meet specific organizational needs. However, achieving this level of customization often requires considerable time and technical expertise.

It has strong user adoption and satisfaction due to its comprehensive features and capabilities. However, user experiences can vary based on the organization's specific needs and the solution's implementation.

I rate it a seven out of ten. 

We mostly use Collibra Governance for governance-related tasks like building business glossaries and creating policies.

Collibra Governance comes with a lot of features, and we have used it in one of our projects for metadata management and data lineage. I have used the solution to create governance rules and a centralized repository for business glossaries.

The solution's metadata management is pretty novice and could be improved.

I have been using Collibra Governance for around one year.

I rate Collibra Governance a nine out of ten for stability.

Collibra Governance is more suitable for medium-level and enterprise businesses.

I rate Collibra Governance a nine out of ten for scalability.

The solution's technical support was good, but there was a delay in their response time, possibly because of the time zones.

Positive

The solution’s initial setup is simple.

The solution's deployment will not take more than a week and can be done in five working days.

The solution's pricing is moderate and not very expensive.

Informatica is coming up with some level of data governance. erwin Data Modeler is quickly emerging as a competitor for Collibra in the coming days.

Collibra Governance is deployed on the cloud in our organization.

Overall, I rate Collibra Governance an eight out of ten.

In my company, we use Collibra Governance for data catalog.

Pricing policy of the product is an area with certain shortcomings that needs improvement. I would like to see better pricing in future releases of the product. Collibra Governance needs to develop some new technology, like Atlan, that has been incorporating AI in the automation area of its products.

I have been using Collibra Governance for five years. I have ensured that one of my company's customers uses the solution's latest version. My company has a partnership with Collibra.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

Around 30 people in my organization use the solution.

The solution's technical support is helpful and responsive. I rate the technical support an eight out of ten.

Positive

I have probably worked with most of the products in the market related to data governance and data catalog, including products like Informatica Axon. I still do work with Informatica Axon at times.

The product's deployment phase was straightforward.

The solution is deployed on an AWS Cloud, which is a private cloud.

The deployment process is carried out by Collibra Governance's technical team.

There is definitely a return on investment from using the product, especially if you associate it with a data catalog tool. The return on investments is in terms of optimizing the process of development, data quality improvement, and having a single repository source of information for the metadata of the entire organization.

I don't know the licensing costs of the product since it is a SaaS solution.

I rate the pricing a three on a scale of one to ten, where one is expensive, and ten is cheap.

The maintenance is something that is carried out automatically by Collibra Governance.

I rate the overall solution an eight out of ten.

Our major use case for Collibra Governance involves maintaining lineage, as well as linking business terms and technical terms together. Then, our use revolves around linking policies with actual data, such that we can create data sharing policies within the tool, storing data and quality results.

I am currently working on about 10-12 projects with Collibra Governance using the latest cloud version. It is available on both cloud and on-premises, but currently all our solutions are moving to the cloud.

Workflows is the most valuable feature of Collibra because we will typically use an interface for it and we can customize it as per our needs.

It is also a very user-friendly tool which is easy to navigate and understand right from the start.

Many other tools like Collibra Governance give you the option to actually see the data in the tool, which is not an option in Collibra. If you compare it with Alation, which has the compose data option, you can see the data right there.

Perhaps this is a feature they could include in the future, although I'm not sure if it is in their roadmap or not, because it is just a governance tool for storing metadata, and not for connecting actual data. If they could include some type of data viewing functionality, however, I would appreciate it.

I've been using Collibra Governance for around six years.

It has been a stable tool since I started using it, which was around 2015. We have used their cloud version since about 2019 or so, making that two years of stable cloud use, while the on-premises version has also been stable. I believe it has been in the market from about 2008 and they have made many enhancements over time with regard to stability.

Since our version of Collibra is on the cloud and we essentially only use it as a metadata tool, the best way it can be extended is to increase the cloud database. This is all done by the Collibra team, however.

At the moment, I am working on between 10 and 12 projects with it, so in this sense I can call it scalable.

The tech support is good because they have a dedicated team who will be mobilized to help support you on the aspect that you are struggling with. Usually, you will get a response from a team member who has knowledge of the sort of routine you are asking about, and you will be talking with someone who has good knowledge of the tool. Of course, it may happen that the support team member is new to the job, but they will at least help guide you in the right direction.

There is also a support portal where you can browse and search for articles that explain what you need to know. If you can't find the information you're looking for, then you can just raise a ticket with their support. It is very easy.

Positive

It's a very user-friendly tool and easy to navigate right from the beginning.

We didn't actually need to install anything with the cloud version because the Collibra team maintains the installation and everything related to it. They simply give us a direct URL to access it and the admin team then manages all the other considerations. Usually, the customers buy one, two, or three instances at a time, including instances for QA and development, but the deployment process really depends on the size of the company.

Deployment in general is very easy because they have a built-in migration feature with which we can easily migrate data from one system to another in a direct manner. We can also simply make a complete backup of the environment and then just upload it to another system using the backup option.

Collibra provides you with a license based on the subscription model that you purchase.

I highly recommend this tool to users who want to see the lineage of their data, including technical lineage and business lineage. It is very easy to create lineage views with it, and it supports many technical lineages out of the box.

I would rate Collibra Governance an eight out of ten.

We are focused primarily on the Data Governance Catalog (DGC) for our data dictionary use. We are not using it for information governance in terms of regulatory compliance, etc. We are focused on business glossary, data catalog, data dictionary, and some workflow processes to help with metadata management and other things.

We are fully updated, and we are using its latest version.

One of the workflows that we're just finishing and rolling out is a certification process. Collibra DGC has an attribute in there called "certified," and it is basically a yes/no choice. We wanted a lot more information about the certification of data sets, so I wrote this workflow, which is probably 30 or 40 steps long. We have a series of criteria that we have to meet in order for a data set to be considered certified. I was able to create attributes for all those and create a workflow that goes hand in hand with data set development so that when somebody competes their work, he or she can pop into Collibra and say, "I have finished this." It logs it and it becomes part of a trust score. It is really nice, and it is making our certification process more robust and the documentation easier to collect and maintain.

I like Collibra's flexibility. I like to be able to modify things for our own use. For example, we've chosen to use Collibra also as a knowledge management tool, even though it is not designed to be a knowledge management tool. That's the beauty of it. It can serve as a knowledge management tool by creating some custom assets specifically for knowledge management. I have a knowledge base domain and a knowledge base article asset type- along with a few other things. I really like the flexibility to be able to extend it in those non-traditional ways.

On the flexibility side, I've created some really nice and very useful custom workflows that have really helped with work processes and productivity. They've really helped us do things easier, faster, and better.

The UI is good if you happen to be an administrator and are familiar with the technical side of the administration. If you're a business user, the UI is not good. It is hard to learn. It is hard for those who are administering it to teach to end-users and it can take hours of training to do it. Because it is difficult and non-intuitive, business users resist using it. It is a battle to get them on board and to keep them engaged because of the UI. On the other hand, Collibra just hired a person specifically to revamp the UI. So, they're dealing with it, but it isn't there yet.

They're working on the lineage harvesting for technical lineages. I don't know this for a fact, but my feeling is that this is new to them. So, they're still developing it and it feels awkward.

I have been using this solution for eight months.

Its stability is very good. Out of 10, I'd probably give it a nine. We've had a couple of little glitches where something happened, but they were minor and we were able to create tickets and get issues resolved within a week and usually within just a day or so.

So far, we haven't had any major problems. We're ingesting metadata from AWS Redshift. We've also got connectors built for S3 but we haven't used them yet. We're importing from Oracle and working on lineage harvesting from DBT, Data Services, and few other places. So far, everything has been really good. We're importing metadata from Tableau, and there are no problems there, either.

In terms of the roles of its users, we've got product managers and solution managers. (A solution manager is the IT coordinator who works with the product manager.) We've also got analysts, engineers, reviewers, editors, data stewards, and data coordinators or custodians. We also have technical stewards, admins, and a group of people we call "normal" who are business users that have read-only access.

In terms of Collibra's usage, I would love to have it used 10 times more than it is, but because of the difficult UI, I am getting resistance from the users. It is hard for them to navigate and learn the interface. Once you know it, it is easy to get around and find what you need. It is just about learning the interface and dealing with some poor choices of how to use the screen real estate. So, right now, the user engagement is lower than I would like it to be. 

Their technical support is very good. On a scale of one to 10, I would give them a seven. We've probably had four or five tickets open and were able to get them resolved quickly. 

It feels like they may be sensitive--possibly they've had some bad reviews regarding their customer service--so it seems like they may be going overboard there. For example, they have scheduled a meeting every month for our team to meet with what they call a customer success manager.  I feel like this is too often.  They're responsive about stuff, but it feels like they're trying too hard.

Prior to this and strictly for our data dictionary, I used Dataedo. They are very good at what they do, but have a much more focused solution.

For knowledge management, I used Confluence and really liked it, but we came up against the issue of access levels for for non-registered users; we didn't want to pay license fees for a large number of "read-only" users. Basically, it is either full (paid) access or free access to "the world" and like everyone else, we have information that we don't want to expose to the world.

Setup was really straightforward. Collibra was very good with holding meetings and being responsive to requests. I was pleased with the setup and configuration process. They were really good at the initial stages of learning and understanding what we were doing.

Those of us who are working on this project also have "day jobs" so we were not focused solely on this. The focused time on it among members of the team was probably less than a hundred hours extended over a period of several weeks.

In terms of maintenance, we have a small, three-person team of people who are actually working on the technical maintenance side. All told, the actual time that we spend in administration at this point is very low--perhaps 20 hours a month spread between three people.

We did it in-house with direct interactions with the Collibra team. Our experience with their team was very good. They have an onboarding process and a roadmap they like to follow. We were just one department with a small team working on the actual setup and use case. Several of their steps didn't apply to our use case so we skipped these and even took some of the other steps out of order simply because it made sense for us. The onboarding team at Collibra was 100% supportive of making those changes and doing things the way we needed instead of the way they ordinarily would have done.

It is substantial, and we pay yearly. 

The thing that made our onboarding really simple was that we understood beforehand our use case and our needs. We understood what our roles were and who needed to be involved. We also understood our communities and our setup structure. We had all of that from the beginning. They mentioned several times that we were extremely well-prepared. So we learned that the more users know about the needs of the department or the company, and the more advance prep work they can do, the easier the onboarding process is.

When we started, the Collibra team sent us two huge Excel files that were basically questionnaires that they wanted us to go through to prepare for onboarding. We already had all of that done. It was finished but wasn't in the same format.  We wrote back and asked, "Do you really want us to fill out these Excel sheets? We've already gathered this information." They said, "Oh, great. We will skip the first two steps of onboarding because you've already got it." That really accelerated the process.

I'd give Collibra a nine out of 10. I am really happy with it though there are few things that I wish were different, especially in the UI.

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.

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.

One of the biggest questions that we had was we didn't know what to with the our tons of legacy systems. The company I work for is a fairly old company, it's over 120 years old within the insurance industry. There are lots of systems that have been around for upwards of say 40 or 50 years, so we're trying to consolidate and bring those down to target, to go from say 15 systems down to three. But not knowing what's in those other systems makes it difficult to do that rationalization. It's enabled us to first understand what we have and then to figure out how we get down to the target state architecture with a reduced number of target systems.

Out of box ingestions of technical metadata as well as ease of use for setting up new business metadata for users to represent their business terms

Collibra is very good at talking to modern database systems such as a normal RDBMS (e.g.DB2, SQL server or Oracle). Where it isn't great is with older technologies that you'll typically find in finance or insurance industries (e.g. VSAM or ISAM, or those types of older technologies). It just doesn't connect with them very easily. They do provide an ability to use a separate product called MuleSoft, which they used to license (as a bundle) up until last year until Salesforce bought MuleSoft, and that division is happening in 2021. With this 'bolt-on', you could go and get that data, but you had to write that code and maintain it yourself. It wasn't an out-of-box (OOB) feature, which is what we really liked from the Collibra offering. Our only way to access these older technologies was to create a MuleSoft flow, maintain, and deploy it. This leaves us with technical debt which will need to continually be maintained. In fact, we built all our custom Mulesoft flows using Mule 3.x and will soon be pushed to upgrade to Mule 4.x. This will not be a simple upgrade and will likely result in additional cost to bring in consulting resources more familiar with the technology. Since we do have a lot of older legacy systems, things that aren't greenfield, if you will, it adds a lot more overhead than what we were originally led to believe when we originally purchased the product.

We're not that deep into the Collibra product yet because it's only been a couple of years. We do like their ability to automate the workflows, such that, for example, if somebody comes in to say, "I want to request access to this data," you can build your own workflows to automate the approval process. There are some that are out-of-box, I think they could go a little bit further with some of their out-of-box workflows instead of having to create a workflow manually, get somebody to code it, and implement it. I think they could offer a bit more in that respect.

The second item that I think they could do better at is to have other products, or have things where they have a set of taxonomy per industry that says, "Here's what a policy is. Here's what a customer is," that kind of thing. They don't implement that out-of-box in Collibra, you have to do that yourself, whereas other products bring that to the table. Informatica, I believe, has their own insurance industry or industry specific taxonomy that would come with the product.

It makes adding the new logical constructs to Collibra a more manual workup to take care of. The classification becomes more manual because you don't get that out-of-box to say, "Hey, I recognize that that's a policy, because I know that about that and the taxonomy." You have to manually make that connection.

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

Collibra Governance's stability is quite good. It doesn't take a lot of maintenance to deal with it, it just runs. It doesn't cause a ton of issues and it doesn't require a lot of upgrades (we usually upgrade once/year). In the couple of years we've done, I think, two upgrades on it. The one thing that we're disappointed with is that 5.7.7 is their last on-premise implementation that you can do. You have to go to a SaaS offering by Collibra, after it's just been released end of November.

Being the industry that we're in, we're very risk averse, so our use of SaaS offerings isn't that large, and our company isn't prepared to put a lot into the cloud, especially when it comes to personally identifiable information (PII). We're very nervous about that. With that limitation, we would have preferred that Collibra would have extended the timeline of their on-premise offerings beyond this.

I don't have a lot to say about scalability because we haven't had the system pushed that hard. I think we started out with an initial 25 users, and we might have a couple of hundred now. We haven't had any complaints from end users in terms of not returning information in a timely fashion or the system isn't working as good as I would expect. We haven't had enough experience to comment on that. Our current installation is approximately 175 users with about 15-25 concurrent usage. We went with the vendor recommended VM sizings although we did put all services for Collibra on one VM (except JobServer and Connect as recommended). For larger implementations, Collibra will recommend that you split out services (e.g. DGC, Search, Repository) onto separate VMs to allow performance tuning but our implementation hasn't come to that yet. 

In my experience technical support is pretty good. They're fairly responsive. If I enter a case, I'll usually hear back either later that day, so maybe a five or an eight hour turnaround, or definitely within two business days. I find if it's beyond a basic question, it takes a little bit to get it pushed to another level, to their second level support. Sometimes it takes a while for them to say, "I don't know the answer, now I'll ask second level to assist me with that." Getting past the first level, like most vendors, is a bit difficult because they want the call answered there, but it is not unreasonable in any respect

We previously used the IBM Information Governance Catalog, IGC. We had used that as part of the whole suite (e.g. Information Analyzer, InfoSphere, etc.). We went out and did vendor assessments and had demos from the vendors come in to set a strategic direction. We determined what our strategic platform was going to be in terms of a data catalog. IGC just quite frankly wasn't anywhere in the realm of what Collibra could offer in comparison. It felt like comparing Windows 3.1 to a Windows 95 interface. Collibra is known as the 'Cadillac' offering from a user perspective. There are some things that it is not as technically good for, such as Alation is quite good at crowdsourcing or crowd approval approach. But in our opinion, Collibra offered the most features from one product overall. It's a bit on the pricier end, but when we looked at the Gartner Quadrants and Forrester Waves, it was always consistently either one or two up there with, say, Informatica or other tool sets like that.

That's actually what my role is, as the technical lead. I'm the one who did the installation, and is responsible for patching and that kind of stuff. I'm not an end-user of it as much, I don't go into it every day to do workflows or create the data, but if there's a technical request or something, that's where I would get engaged.

The initial setup is fairly straightforward. I found the Collibra pre-sales and their support pretty helpful. They got back to you in a timely manner to be able to do the setup. It wasn't a difficult implementation by any stretch. It was about what I expected in terms of the timeline that they had provided for us and what we needed to do.

In terms of the actual installation process, it was maybe a couple of days start to finish once the hardware and everything was there. Then you continue to do your configuration as time goes on to connect to different systems and whatnot.

Most of that was put forth on advice from the vendors. We said here's the usage count that we plan to have, here's how many systems we're targeting originally. We looked to Collibra to give us the recommendation as to VM sizing and implementing. We didn't really create our own, we used theirs and customized it slightly for our environments, but it was mostly a vendor-provided plan of implementation.

We used in-house resources to build/deploy the IaaS environment and complete the installation of Collibra. We have used 3rd party firms to develop custom Mulesoft flows for connecting legacy systems and custom workflows

We've had good ROI, because when we look at the amount of time invested, it's not necessarily dollars out the door; it's more about manual work avoidance. Instead of having somebody have to manually enter all of these different systems and characteristics, we can do integrations between our source systems and Collibra to get that automatically and refresh it. As people make changes to source systems as time goes on, we can automatically bring those into Collibra. It has allowed us to do one of the projects that we had on the books for this year, which was to understand what our critical systems were. Not only for disaster recovery, but where is our most important data about our customers? Where does that reside and how can we take that data and join it to understand more about our customers and their needs?

In our scenario, we have different business units with the same customer, but we can't make that realization that it's the same customer in different business units because of the way the systems grew separately over the years. Collibra is the one that's allowing us to tie that together. It opens up additional revenue streams with the ability to say, "Hey, I noticed you bought a product for this business unit from us. Did you know we also sell this product for this other business unit?" It allows us that cross-selling opportunity or upselling if you will (aka Revenue generation). That's a bit difficult to articulate or quantify in hard dollars, because there are so many steps going from a lead all the way to a sale. But we certainly believe that the information that Collibra has been able to provide us has helped or augmented our revenue generation streams. In a way it is a sales enablement tool.

In terms of pricing, it's not bad. You pay more money for the author licenses, which is where you do most of your entry and whatnot. Whereas consumers are basically viewing information and using the tool to say, "Hey, I want to look at this data." I think what we would like to get to eventually might be an enterprise license, rather than having to say, "I'm going to pay for 50 authors or 100 authors." At some point in the future, I could see us wanting an enterprise license.

They may offer that now, but it wasn't at a price that was palatable for our company at this point. Plus, we needed a few years to get uptake in it to justify going to that high level. It's just more money licensing wise, but not unrealistic, in my opinion. The money is well spent for the product and the services we're getting.

We just found that IGC was way behind the times. IBM had not really put any money into their product, it didn't connect with any of the systems that we wanted to do. It simply just didn't fill our needs.

We did look at the Informatica product and we did look at Alation.

I think what we found with Alation is that it was good. The user interface was impeccable, but it was not what we would consider the whole package. It was very good at the catalog portion, but in terms of interconnectivity with different systems, it did not have workflow, which was a key characteristic that we were looking for. Alation was a fairly new company. It was only maybe three or four years old at the time when we looked. There was concern about the staying power for that particular vendor. Not that their product wasn't good, it just wasn't as full a product as we would have had with Collibra but built on something for workflow, which we weren't interested in. We were looking for one product to do that.

The Informatica offering was quite good as well, but in our investigations and interviews with other companies in our industry, Informatica is quite a complex product to get up and running and to maintain. It's not cheap either, but when we looked at what it would take to care and feed our maintenance on the Informatica side of the house, in comparison to what we could do with Collibra, we chose Collibra.

Everything seems to be going the route of software as a service these days. It does take away somewhat your ability to customize like you want. Some products allow you to do that better with their SaaS offering than others. I would say that the data catalog space changes quite rapidly. When we did our investigation a couple of years ago, Alation hadn't been in business that long, they've continued to grow and maybe their offering has become better. Just because we chose something two or three years ago, doesn't mean that we shouldn't re-evaluate that in another couple of years to say, "Is this still the strategic product for us?"

There tends to be a lot of vertical integration going on. We once thought, "Well, let's just buy IBM because everything works with IBM." That doesn't seem to work any more. There seems to be a lot of best of the breed. But when you do that, there can be a lot of interoperability there that just doesn't work out. That people who like the IBM's of the world say, "We'll just buy our product because everything integrates." It truly doesn't in our experience.

You have to do your homework and definitely interview other customers to understand their experience for what is good and bad, because of course, sales isn't going to tell you that. But do your homework and make sure that you're talking to people who have not only installed the system, but have been able to use it for a few years, to see what's good about it, what's bad, and what they might have done differently. We talked to a number of different customers in the insurance field, in Canada, the U.S. and in Europe, and learned different things that we would have never considered on our criteria had we not talked to them.

On a scale of one to ten, I would peg it at a seven and a half, eight. I would put it higher, only except it doesn't connect as well to our legacy systems without additional programming and a separate tool, which they used to license as the whole product, but when MuleSoft got bought out by Salesforce, that business relationship was severed. Now we have to buy that MuleSoft product separately from Collibra. Now we have a data governance product that used to include MuleSoft (but does not now,) and now we have to deal with a second vendor to get that. It was nice when it was all one product. If they're going to say, "Use MuleSoft to get at your legacy systems," fine, sell me that product. But they won't do that anymore because Salesforce owns it.

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.

We have benefited greatly from Collibra's data governance reporting. If we want to know more about a specific data element, we can use Collibra to get a picture of the whole history of it.

For example, who is the business owner for it? Where is the data coming from (especially when you have different sources which come through) and who was all touching it? And if I wanted to add a rule, like a business rule or a data quality rule for that particular data element, how or where do I keep it? It's like one central place, but for all these items.

I like the lineage feature the most because I don't think there's any other tool that actually depicts the data flow from multiple sources and the connectivities between every data element inside those sources.

I don't think there's any other solution where you can view multiple systems and multiple sources and data places and you can just write it down. It's a lot of work to initially organize but there's no other tools to do lineage like Collibra does it.

The connectors are not very sophisticated. They can do, for example, Informatica and Tableau, but the connectors themselves could be improved.

I recently got a subscription for another 600K for Collibra for one more year, so the author licenses are not used much. And they keep changing the UI platform; that can also be improved.

From an administration perspective, I like the white-glove onboarding part of Collibra. That was actually nice and I really liked that. For administration in general, I like that you can use Collibra however you want. It's more raw and easily adaptable.

So you can cook it or you can steam it or you can make changes to it in a lot of different ways, but it would also be nice if there were an already available analytics tools like Tableau at hand. Though it is easily adaptable and you'll have a completed end product which you can really leverage.

I've been using Collibra Governance for five or six years.

In terms of scalability, it's more like adopting; it's more like a shark. You have to keep feeding it and then it will grow. It depends on how many systems you're using. I worked for a union bank earlier when we set up Collibra and we were able to push in 3000, 30,000, 30,000 data elements. It's great when all the data is available because the team had been doing data analysis for more than a year prior to getting onto Collibra.

At my current company, the data analysis started at the same time along with the data governance and I think I hardly have 300 data elements. So it works on however much you feed it.

And if you have a huge data dictionary and business glossary already available, well and good. Instead of putting it in an Excel sheet, you can put it on Collibra and then you can actually walk through it. But if not, then you have to start feeding it, and it might take at least two years until you get proper food for the tool.

The technical support is okay, definitely not bad. I think they have a 24 hour SLA, but again, it's a data governance tool, so if it breaks and it's not available for a day or so, it's not going to create any business loss. It's more of an understanding kind of tool, and if the SLA is a bit delayed it won't be much of a problem.

The only comment I have is that some of the technical support teams in privacy, security, infrastructure, etc., could be more available during US timezones. That would have made our onboarding process easier.

We went through setup with the white-glove onboarding program. I actually gave feedback to Collibra as well, because the process is a little unusual, but I appreciate it.

The one thing I found a bit difficult when properly onboarding with Collibra and setting it up is that some of the Collibra teams we're working with, like in the security, privacy, and infrastructure teams, are in the European timezone and not the US timezone. Because of this, it becomes a little uncomfortable. It would be great if they could change things around so that there's also somebody available in the US.

It's not just one single technical support team when you are setting up Collibra; you have a lot of different puzzle pieces to work with. That's what the white-glove onboarding is all about. So it actually takes five to six weeks to completely set up, from starting with the solution to getting the software installed and all the nodes set up.

Whether it's on-premises or online, in both cases the whole setup takes five to six weeks and in this time frame I also need to have the company-related IT support people available. And it's just hard for me because most of Collibra's support teams are on Europe time. It could even take up to eight weeks.

Regarding implementation, we need to have the role-setting, we need to have the workspace in the UI in the front end, we need to build the communities, the groups, etc. So it's more like a whole structure that you have to build, and it's a lot of work.

It's more raw, so you can change it however you want. But the thing is, there's not much of a guideline and it depends on your company and organization as well. So you have to ask, how do you want to do the structure? Then you first have to find the communities, and you'll have to set up the groups and the UI, and what comes back, and it's just more about adopting the software to your needs.

Our data officer was very interested in doing it. So she's fully on. And we had an administrator, a developer and the business. We had around three or four business owners to set up the first part before we adopted the rest of the businesses. Of course I was there, too, and there was one more project manager. All in all, we implemented Collibra with only about eight people. As for ongoing maintenance, we only require one administrator.

We have not seen ROI yet. Again, it's more like a dictionary. You buy a dictionary at home, so whenever you want it, you use it. What is the value of getting the dictionary? I don't know. It depends on your talent. If your team does not have good talent, then the dictionaries are more useful. It gets easier to navigate. And if you don't have the dictionary, it's going to be hard.

I think they have a trust issue.  I did not like the way they recently went through the process. They were like, "Finish this SOW first, only then will we sign the other SOW." Or, "Finish this code." I didn't like that much.

And they're also very hard. They don't negotiate much: The first price is the first price. We tried our vendor management team contracts that our negotiation people use, but they did not negotiate at all, nothing at all. The very first price they quoted, they almost always stuck to the same price, within 95-98%. Always the same price; hardly anything went down. So that's one thing. They shouldn't do that.

Generally, when all the vendors quote, first they quote and then we start negotiating it. They might then reduce the quote or just provide a different way of getting around. Collibra were very rigid cost-wise, so they should improve that or maybe come up with some plan on how to negotiate.

I think we considered Informatica and one or two others that I can't remember off the top of my head. Informatica was the actual challenger to Collibra before we finalized the cost and everything.

It was cheaper, and it was another good one from an analytics perspective. But we know that, industry-wise, Collibra is number one from a data governance perspective. That's one of the reasons why we went with Collibra, even though the rest of the tools' setup cost and maintenance were cheaper.

It's a very niche product. It's nice to use and easy to promote. You don't have to have all the user licenses - you can also get the author licenses. If you have 10 author licenses, you can get up to 50,000 consumer licenses. It's nice to know you have a mobile component in that regard.

If you're doing a lot of training as well, you need to do proper training with your data team, and with your business team, try to use it as a business tool instead of a technical tool. Employ it as much as you feed it, because then it's that much more useful.

And then having the business rules, the data governance and data quality rules, everything in one place, is nice to have. If you try to utilize it, the data lineage is number one, because there's awesome capability in it. So just try to use it and you'll start loving it.

I would rate Collibra a seven out of ten.